Summary: | dev-cpp/glibmm-2.78.1 installs files into unexpected paths | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Agostino Sarubbo <ago> |
Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | esigra |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build.log |
Description
Agostino Sarubbo
2021-12-18 07:04:49 UTC
Created attachment 759521 [details]
build.log
build log and emerge --info
ci has reproduced this issue with version 2.72.1 - Updating summary. ci has reproduced this issue with version 2.74.0 - Updating summary. ci has reproduced this issue with version 2.76.0 - Updating summary. # equery b /usr/include/glibmm-2.68/glibmm/variant_basictypes.h * Searching for /usr/include/glibmm-2.68/glibmm/variant_basictypes.h ... dev-cpp/glibmm-2.78.0 (/usr/include/glibmm-2.68/glibmm/variant_basictypes.h) (In reply to Erik from comment #5) > # equery b /usr/include/glibmm-2.68/glibmm/variant_basictypes.h > * Searching for /usr/include/glibmm-2.68/glibmm/variant_basictypes.h ... > dev-cpp/glibmm-2.78.0 (/usr/include/glibmm-2.68/glibmm/variant_basictypes.h) Please explain why that's a problem. The QA warning here is for docs. (In reply to Sam James from comment #6) > (In reply to Erik from comment #5) > > # equery b /usr/include/glibmm-2.68/glibmm/variant_basictypes.h > > * Searching for /usr/include/glibmm-2.68/glibmm/variant_basictypes.h ... > > dev-cpp/glibmm-2.78.0 (/usr/include/glibmm-2.68/glibmm/variant_basictypes.h) > > Please explain why that's a problem. It just looks like someone made a new package version but forgot to update the install path. Someone encountering any problem will start to investigate and encounter this. I'm not sure how you reached that conclusion. The QA warning here is unrelated to slotting or anything like that - it's an FP/issue with gnome packages. The api version upstream for this package is the same for previous versions per meson.build. Please state explicitly what you're thinking and why. I did not see any QA warning. Just the output of equery. It shows that version 2.78.0 of the package installed a file in a path containing the version number 2.68. Any ordinary user who encounters some problem will notice it and start investigating whether that may be the cause of the problem. A user would expect version 2.78.0 to install into a path containing "2.78", not "2.68". I posted here because the subject (except for the version number) matched what I stumbled upon. gcc14_tinderbox has reproduced this issue with version 2.78.0 - Updating summary. ci has reproduced this issue with version 2.78.1 - Updating summary. |