|Summary:||emerge should show a warning when it is skipping a newer version due to some problem|
|Product:||Portage Development||Reporter:||Pacho Ramos <pacho>|
|Component:||Core - Interface (emerge)||Assignee:||Portage team <dev-portage>|
|Severity:||enhancement||CC:||ansla80, esigra, felipematas|
|Package list:||Runtime testing required:||---|
|Bug Depends on:|
|Attachments:||script that checks all installed slots for new versions|
Description Pacho Ramos 2013-06-03 19:44:05 UTC
I often see how a latest version is being silently skipped because of problems like something missing in IUSE or other problems. Would be nice if it could also show the error message (error message that I can see when forcing it to try to merge affected version using =<category>/<package>-x.x Thanks Reproducible: Always
Comment 1 Zac Medico 2013-06-03 20:12:32 UTC
Currently, warnings are only shown when the new version has a missing dependency or triggers a dependency conflict.
Comment 2 Zac Medico 2013-06-08 23:25:35 UTC
Created attachment 350456 [details] script that checks all installed slots for new versions Until emerge has this built in, you can use this script to check all installed slots for new versions. On my system, I noticed that some updates were being held back by dependencies on specific versions. For example, app-office/libreoffice-22.214.171.124 pulls in these specific atoms: =dev-libs/liborcus-0.5.1 <dev-util/mdds-0.8.0 Should we provide different emerge options to control warnings for different kinds of dependency constraints (version vs. USE constraints)?
Comment 3 Zac Medico 2015-11-22 19:10:15 UTC
*** Bug 566258 has been marked as a duplicate of this bug. ***
Comment 4 Pacho Ramos 2016-02-06 13:33:27 UTC
*** Bug 540474 has been marked as a duplicate of this bug. ***
Comment 5 Zac Medico 2020-03-24 17:45:39 UTC
When an update is skipped due to an optional build time dependency, it can be confusing, since since the skipped update message may not be shown and masking the old version may allow the upgrade to continue.