Summary: | =dev-libs/leatherman-1.3.0 - stablereq | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Matthew Thode ( prometheanfire ) <prometheanfire> |
Component: | Stabilization | Assignee: | Matthew Thode ( prometheanfire ) <prometheanfire> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | idl0r, idl0r |
Priority: | Normal | Keywords: | STABLEREQ |
Version: | unspecified | Flags: | stable-bot:
sanity-check+
|
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: |
=dev-libs/leatherman-1.3.0
|
Runtime testing required: | --- |
Bug Depends on: | |||
Bug Blocks: | 622158 |
Description
Matthew Thode ( prometheanfire )
![]() ![]() ![]() ![]() amd64 and x86 marked stable it seems like dev-ruby/facter requires leatherman < 1.x # grep is_fixednum -r /var/tmp/portage/dev-libs/leatherman-0.12.1/image/usr /var/tmp/portage/dev-libs/leatherman-0.12.1/image/usr/include/leatherman/ruby/api.hpp: bool is_fixednum(VALUE value) const; # dev-libs/leatherman-1.0.0 # grep is_fixednum $(equery f leatherman) 2>/dev/null # So that bool has been removed. We either need to adjust the dependencies or that bool usage needs to be fixed, as it brakes stable packages. Not sure if others are affected as well. newer facters need the newer leatherman, the bug this blocks updates the stable facter so the dependency issue isn't valid. Up to at least 3.6.4, which is still the highest stable, it needs leatherman <1.x. They should have been stabilized together at best but now there's already ~1mo difference. ya, 3.7.1 is now stable amd64 and x86 updating version... ppc64 stable ppc stable commit b9566eec89e732db935db19b0065bf8167f1c4b1 Author: Matthew Thode <prometheanfire@gentoo.org> Date: Mon Oct 16 20:39:17 2017 -0500 dev-libs/leatherman: 1.3.0 stable amd64 and x86 Package-Manager: Portage-2.3.8, Repoman-2.3.3 ppc64 stable ppc stable re-cc'ing ppc(64) arche(s) sparc stable (thanks to Rolf Eike Beer) hppa stable (thanks to Rolf Eike Beer) ppc64 stable ppc stable Last arch. Closing. |