Summary: | emerge uUD --autounmask --autounmask-write sometimes fails to edit /etc/portage/package.unmask when there is an update of other libraries that are needed by applications | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Benjamin Schulz <schulz.benjamin> |
Component: | Core - Dependencies | Assignee: | Portage team <dev-portage> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | esigra, schulz.benjamin, zmedico |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 376695 |
Description
Benjamin Schulz
2024-02-21 17:06:23 UTC
Here is a Here is an example where you can verify this bug easily. Currently, there is a bug in opencolorio. It needs dev-cpp/yaml-cpp-0.8.0:0 But yaml-cpp is now at version 0.8. This is a bug which was acknowledged here. yaml-cpp has to update its ebuild https://bugs.gentoo.org/925174 Now at the moment, i would have to unmask the license linux-fw-redistributable for sys-kernel/linux-firmware-20240220-r1::gentoo because of an update. And this is what portage then does when I use it with --autounmask --autounmask-write: It just does nothing. Instead, it should have updated the license masking... The same happens with useflags and masked packages. Annoying is especially that this happens also when there are just percieved blocks, i.e. that --autounmask write does not do anything for some package just because in some other package there appears to be a block when the package tree has not entirely be computed, i.e when it claims a kdelib cant be installed because it would depend on old kde-apps, which are, however, also updated when the entire tree is taken into account. /home/Benni # emerge -uUD --autounmask --autounmask-write world Calculating dependencies... done! Dependency resolution took 49.91 s (backtrack: 0/20). WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict: dev-cpp/yaml-cpp:0 (dev-cpp/yaml-cpp-0.8.0:0/0.8::gentoo, ebuild scheduled for merge) USE="-test" ABI_X86="(64) -32 (-x32)" conflicts with <dev-cpp/yaml-cpp-0.8.0:= required by (media-libs/opencolorio-2.1.3:0/2.1.1::gentoo, installed) USE="python (-doc) -opengl -test" ABI_X86="(64)" CPU_FLAGS_X86="sse2" PYTHON_SINGLE_TARGET="python3_11 -python3_10" ^ ^^^^^ dev-cpp/yaml-cpp:0/0.7= required by (dev-qt/qt-creator-12.0.1:0/0::gentoo, installed) USE="clang designer help qmldesigner serialterminal svg tracing webengine -doc -test" ABI_X86="(64)" ^^^^^^^ <dev-cpp/yaml-cpp-0.8.0:0/0.7= required by (media-libs/opencolorio-2.1.3:0/2.1.1::gentoo, installed) USE="python (-doc) -opengl -test" ABI_X86="(64)" CPU_FLAGS_X86="sse2" PYTHON_SINGLE_TARGET="python3_11 -python3_10" ^ ^^^^^^^^^^^^ !!! The following updates are masked by LICENSE changes: - sys-kernel/linux-firmware-20240220-r1::gentoo (masked by: || ( ) linux-fw-redistributable license(s)) A copy of the 'linux-fw-redistributable' license is located at '/var/db/repos/gentoo/licenses/linux-fw-redistributable'. For more information, see the MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. (Hopefully you mean package.accept_keywords; package.keywords was deprecated for years and should warn on use.) Hi Greg, Yes I meant package.accept_keywords. I use gentoo a bit longer, but of course my system is up to date. but it is still strange that --autounmask --autounmask-write does not do its job at all, when there is a totally unrelated conflict somewhere else or when there would be a conflict only if the package update tree is not entirely computed. When you are new to portage, i guess this bug can be confusing, since, during my last update of kde, portage just printed out a very very large list of nonsensical blocks that really were not relly there. For a beginner, it could be difficult to imagine that this is a portage bug in --autounmask-write and that he simply has to set some useflags, licenses or maskings manually totally in unrelated packages in order to continue the upgrade of kde... Also confusing is that portage manages to print out the settings that need to be changed, but does not write it despite being told to do so... |