Summary: | sys-apps/portage-2.3.21 - questionable list of dependency changes without revision bump | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Carlo <gentoo-bugs> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | bkohler |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Carlo
2018-01-30 21:02:57 UTC
You'll probably want to compare /var/db/pkg/media-libs/libaacs-0.7.1/RDEPEND to the RDEPEND line in $gentoo/metadata/md5-cache/media-libs/libaacs-0.7.1 RDEPEND=>=dev-libs/libgcrypt-1.5.3:0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?] >=dev-libs/libgpg-error-1.12[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]
vs
>=dev-libs/libgcrypt-1.5.3:0[abi_x86_64(-)] >=dev-libs/libgpg-error-1.12[abi_x86_64(-)]
This doesn't make it better.
(In reply to Carlo from comment #2) > RDEPEND=>=dev-libs/libgcrypt-1.5.3:0[abi_x86_32(-)?,abi_x86_64(-)?, > abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?, > abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?] > >=dev-libs/libgpg-error-1.12[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?, > abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?, > abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?] > > vs > > >=dev-libs/libgcrypt-1.5.3:0[abi_x86_64(-)] >=dev-libs/libgpg-error-1.12[abi_x86_64(-)] It looks like this is due to a difference in the way the atoms were evaluated. I'll look into making it normalize them prior to comparison. (In reply to Zac Medico from comment #3) > (In reply to Carlo from comment #2) > > RDEPEND=>=dev-libs/libgcrypt-1.5.3:0[abi_x86_32(-)?,abi_x86_64(-)?, > > abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?, > > abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?] > > >=dev-libs/libgpg-error-1.12[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?, > > abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?, > > abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?] > > > > vs > > > > >=dev-libs/libgcrypt-1.5.3:0[abi_x86_64(-)] >=dev-libs/libgpg-error-1.12[abi_x86_64(-)] > > It looks like this is due to a difference in the way the atoms were > evaluated. I'll look into making it normalize them prior to comparison. If tested and it looks like portage already normalizes these properly, so the change was probably triggered by a changed eclass dependency in DEPEND such as the app-portage/elt-patches dependency added by libtool.eclass. Seems you're right, Zac. I'm back to --dynamic-deps=y. Sorry for the noise. |