Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

libosmocore: 1.9.2 -> 1.9.3 #318429

Merged
merged 1 commit into from
Jun 18, 2024
Merged

Conversation

r-ryantm
Copy link
Contributor

@r-ryantm r-ryantm commented Jun 9, 2024

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/libosmocore/versions.

meta.description for libosmocore is: Set of Osmocom core libraries

meta.homepage for libosmocore is: https://github.com/osmocom/libosmocore

Updates performed
  • Version update
To inspect upstream changes
Impact

Checks done


  • built on NixOS
  • The tests defined in passthru.tests, if any, passed
  • found 1.9.3 with grep in /nix/store/hpawcr8yjydwm4b1maqh87hfgv6878gp-libosmocore-1.9.3
  • found 1.9.3 in filename of file in /nix/store/hpawcr8yjydwm4b1maqh87hfgv6878gp-libosmocore-1.9.3

Rebuild report (if merged into master) (click to expand)
17 total rebuild path(s)

17 package rebuild(s)

First fifty rebuilds by attrpath

libosmo-netif
libosmo-sccp
libosmoabis
libosmocore
osmo-bsc
osmo-bts
osmo-ggsn
osmo-hlr
osmo-hnbgw
osmo-hnodeb
osmo-iuh
osmo-mgw
osmo-msc
osmo-pcu
osmo-sgsn
osmo-sip-connector
Instructions to test this update (click to expand)

Either download from Cachix:

nix-store -r /nix/store/hpawcr8yjydwm4b1maqh87hfgv6878gp-libosmocore-1.9.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.

Or, build yourself:

nix-build -A libosmocore https://github.com/r-ryantm/nixpkgs/archive/9d7bf348e1a13bbea9ed59cc59af251d9786a7c9.tar.gz

Or:

nix build github:r-ryantm/nixpkgs/9d7bf348e1a13bbea9ed59cc59af251d9786a7c9#libosmocore

After you've downloaded or built it, look at the files and if there are any, run the binaries:

ls -la /nix/store/hpawcr8yjydwm4b1maqh87hfgv6878gp-libosmocore-1.9.3
ls -la /nix/store/hpawcr8yjydwm4b1maqh87hfgv6878gp-libosmocore-1.9.3/bin


Pre-merge build results

We have automatically built all packages that will get rebuilt due to
this change.

This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.

Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

16 packages built:
  • libosmo-netif
  • libosmo-sccp
  • libosmoabis
  • libosmocore
  • osmo-bsc
  • osmo-bts
  • osmo-ggsn
  • osmo-hlr
  • osmo-hnbgw
  • osmo-hnodeb
  • osmo-iuh
  • osmo-mgw
  • osmo-msc
  • osmo-pcu
  • osmo-sgsn
  • osmo-sip-connector

Maintainer pings

cc @mogorman @Janik-Haag for testing.

@NickCao
Copy link
Member

NickCao commented Jun 9, 2024

Should this be updated in accordance with other osmo components?

@Janik-Haag
Copy link
Member

Should this be updated in accordance with other osmo components?

it depends on the update, in this case it should be fine to go ahead and merge the update. In general I'd appreciate if you'd wait a week or so before merging updates for packages I maintain, in the past you were rather trigger happy with some PRs and I didn't have time to take a look before. I was slow with this one because I was sick for the last weeks.

@Janik-Haag Janik-Haag merged commit adee5ed into NixOS:master Jun 18, 2024
26 checks passed
@r-ryantm r-ryantm deleted the auto-update/libosmocore branch June 19, 2024 00:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants