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
libhandy_1: init at 1.0.2 (backport) #106680
Conversation
but no failures are expected since this is only a package rename. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When backporting changes, please follow https://github.com/NixOS/nixpkgs/blob/master/.github/CONTRIBUTING.md#backporting-changes.
Namely, you should be doing git cherry-pick -x <rev>
from a commit that has already landed in master. If the branches have diverged, you may alter the commit or add another commit to ensure that the package is able to still evaluate and build
pkgs/top-level/all-packages.nix
Outdated
libhandy = callPackage ../development/libraries/libhandy { }; | ||
|
||
# Needed for apps that still depend on the unstable verison of the library (not libhandy-1) | ||
libhandy_0 = callPackage ../development/libraries/libhandy/0.x.nix { }; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would do something like this, and then remove all of the fixup commits
libhandy = callPackage ../development/libraries/libhandy { }; | |
# Needed for apps that still depend on the unstable verison of the library (not libhandy-1) | |
libhandy_0 = callPackage ../development/libraries/libhandy/0.x.nix { }; | |
libhandy = libhandy_0; | |
# stable branch | |
libhandy_1 = callPackage ../development/libraries/libhandy { }; | |
# unstable verison of the library (not libhandy-1) | |
libhandy_0 = callPackage ../development/libraries/libhandy/0.x.nix { }; |
also, backports target the |
Result of 32 packages built:
|
@jonringer Oops, my bad. I'll follow accordingly. |
* adapt for the move under the gnome project The gnome team now maintains this * format * cleanup meson flags The auto features are enabled automatically * drop gnome3.gnome-desktop It doesn't seem to be neeeded in meson.build https://gitlab.gnome.org/GNOME/libhandy/-/tags/v0.80.0 https://gitlab.gnome.org/GNOME/libhandy/-/tags/0.81.0 https://gitlab.gnome.org/GNOME/libhandy/-/tags/0.82.0 https://gitlab.gnome.org/GNOME/libhandy/-/tags/0.83.0 https://gitlab.gnome.org/GNOME/libhandy/-/tags/0.84.0 https://gitlab.gnome.org/GNOME/libhandy/-/tags/0.85.0 https://gitlab.gnome.org/GNOME/libhandy/-/tags/0.90.0 https://gitlab.gnome.org/GNOME/libhandy/-/tags/0.91.0 https://gitlab.gnome.org/GNOME/libhandy/-/tags/1.0.0 (cherry picked from commit 431c2c3)
(cherry picked from commit f904737)
(cherry picked from commit 3f857b8)
https://ftp.gnome.org/pub/GNOME/sources/libhandy/1.0/libhandy-1.0.2.news (cherry picked from commit bfadfd5)
d5bdf9b
to
7efacb1
Compare
Result of 1 package built:
|
Ready from my side |
was this ever in master? When backporting changes, please follow https://github.com/NixOS/nixpkgs/blob/master/.github/CONTRIBUTING.md#backporting-changes. Namely, you should be doing |
generally new additions land in master, I'm fine with backporting new packages, but the release branch should always contain packages that have at least existed in master |
@jonringer All cherry picked commits are from The only change I introduced was to point If you are referring to If this is too confusing, I'm happy to make an independent pull request to add |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested building/running shortwave.
I marked this as stale due to inactivity. → More info |
Backport shouldn't be necessary anymore now that a new release is out. |
This commit follows the same naming scheme currently in use in for
libhandy
in the 'master' branch.References to
libhandy
were renamed tolibhandy_0
.Effectively the changes introduced are only meant to allow
libhandy
to be upgraded to 1.x without breaking depending packages.Motivation for this change
cpupower-gui v1.0.0
requires libhandy 1.x .Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)