Recently (well, o.k. a while ago) I upgraded qt-3 to qt-3.3.8. Upon my next world upgrade, paludis indicated that qt-3.3.8 was to be downgraded to 3.3.6. Being the resourceful kind of guy that I am, I simply added the following to the package_mask.conf file:
<x11-libs/qt-3.3.8 Viola! My issues went away. A bit further down the road, qt-3.3.8-r1 (and later -r2) appeared in the update list. After the -r1 upgrade, the next world upgrade indicated that qt-3.3.8-r1 was to be downgraded to qt-3.3.8. Ah, I thought. I'll simply change my package mask to: <=x11-libs/qt-3.3.8 Although this does prevent the downgrade, it also elicits loads of warnings from various components which depend on qt-3.3.8. i.e.: [EMAIL PROTECTED]: [WARNING] In program paludis -pi world --dl-new-slots as-needed: ... When performing install action from command line: ... When executing install task: ... When adding PackageDepSpec 'net-irc/konversation': ... When adding installed package 'net-irc/konversation-1.0.1-r1::installed': ... Ignoring run dependencies due to exception 'Error searching for '=|=|=|=|=|=|=|=|=|=|=|=|=|=|=|=|=|=|=|=|=|=|=|=|=|=|=|=|=|=|=|=|=|=|=|=|=|=|=|=|=|=|=|=|=|=|=|=|=x11-libs/qt-3.3.8,3.3.6-r5,3.3.6-r4,3.3.6-r3,3.3.6-r2,3.3.6-r1,3.3.6,3.3.5-r1,3.3.5,3.3.4-r9,3.3.4-r8,3.3.4-r7,3.3.4-r6,3.3.4-r5,3.3.4-r4,3.3.4-r3,3.3.4-r2,3.3.4-r1,3.3.4,3.3.3-r3,3.3.3-r2,3.3.3-r1,3.3.3,3.3.2,3.3.1-r2,3.3.1-r1,3.3.1,3.3.0-r1,3.3.0,3.2.3-r1,3.2.3,3.2.2-r1,3.2.2,3.2.1-r2,3.2.1-r1,3.2.1,3.2.0,3.1.2-r4,3.1.2-r3,3.1.2-r2,3.1.2-r1,3.1.2,3.1.1-r2,3.1.1-r1,3.1.1,3.1.0-r3,3.1.0-r2,3.1.0-r1,3.1.0': no available versions' (paludis::AllMaskedError) This even though net-irc/konversion-1.0.1-r1 is not being updated or installed at this time. WTF? It would seem as though once we've made the jump from a version of software to a higher version of software that a downgrade would only occur if the higher version of software were package masked or something. I know there is ongoing debate about how the standards for versioning are and/or have been implemented/enforced. Is my understanding of the process correct or am I just being thick? How can I achieve peaceful paludis world upgrades without changing package masks and/or having to see all of the warnings every time? Regards, Bob P.S. I also saw the error below. Someone should be beaten repeatedly about the head and shoulders for this even making it into the tree: [EMAIL PROTECTED]: [WARNING] In program paludis -pi world --dl-new-slots as-needed: ... When performing install action from command line: ... When executing install task: ... When adding PackageDepSpec 'media-video/mplayer': ... When fetching versions of 'media-video/mplayer' in gentoo: ... When loading versions for 'media-video/mplayer' in gentoo: ... Skipping entry '/var/paludis/repositories/gentoo/media-video/mplayer/mplayer-1.0_rc2_pre20070321-r4.ebuild' for 'media-video/mplayer' in repository 'gentoo' due to exception 'Name '1.0_rc2_pre20070321-r4' is not a valid version spec: unexpected trailing text 're20070321-r4'' (paludis::BadVersionSpecError)' Let's see: Fourth recompile of Release Candidate 2 of Version 1.0 released before 2007-03-21 WTF is this???????? _______________________________________________ Paludis-user mailing list [email protected] https://lists.berlios.de/mailman/listinfo/paludis-user
