Everytime I ran "emerge -Davut world", I got the following error message: ------------------- Calculating world dependencies !!! Problems have been detected with your world file !!! Please run emaint --check world ------------------- However, when I run "emaint --check world", I got the following error message: ------------------- Checking world for problems 'x11-misc/transset' has no ebuilds available 'games-emulation/dosbox' has no ebuilds available 'net-fs/ncpfs' has no ebuilds available 'dev-java/sun-java3d-bin' has no ebuilds available 'net-misc/httptunnel' has no ebuilds available 'dev-tcltk/tclreadline' has no ebuilds available 'media-fonts/mathematica-fonts' has no ebuilds available 'dev-tex/tex4ht' has no ebuilds available 'dev-util/valgrind' has no ebuilds available 'app-emulation/qemu' has no ebuilds available 'sci-biology/phylip' has no ebuilds available 'app-portage/flagedit' has no ebuilds available 'games-emulation/advancemame' has no ebuilds available 'games-emulation/dboxfe' has no ebuilds available 'media-libs/win32codecs' has no ebuilds available 'dev-tcltk/itk' has no ebuilds available 'media-video/mplayer-bin' has no ebuilds available 'media-fonts/texcm-ttf' has no ebuilds available 'net-www/mod_auth_pam' has no ebuilds available 'dev-lang/fpc' has no ebuilds available 'media-sound/audacity' has no ebuilds available 'dev-java/sun-jdk' has no ebuilds available 'dev-java/swt' has no ebuilds available 'dev-java/blackdown-java3d-bin' has no ebuilds available ---------------- But this is strange since I checked all these packages are still there. Workaround: ACCEPT_KEYWORDS="~amd64" emaint --check world yield no errors whatsoever Reproducible: Always Steps to Reproduce: 1. emerge -Davut world 2. emaint --check world Expected Results: Should be no errors
Do you have ~amd64 in ACCEPT_KEYWORDS in /etc/make.conf? Or appropriate entries for those packages in /etc/portage/package.keywords?
Separated masked and unavailable ebuilds into separate categories and notify that package.{keywords,unmask} can be used to manually fix the issue(s).
Yeah, I guess that Portage's comments could be improved a little bit to notify the users.
I did my weekly --sync, then had message advising to emerge an upgrade of portage before anything else. Ran # emerge -av portage Portage emerged with no errors and only one etc file to be updated, which I did with 'etc-update'. When I ran 'emerge -avuD world' I got the same 'emaint' message as yours. My conclusion was to re-sync. Didn't work. My next conclusion was it is something to do with 'portage' as that is the only package I have updated when this problem appeared.
(In reply to comment #1) > Do you have ~amd64 in ACCEPT_KEYWORDS in /etc/make.conf? > > Or appropriate entries for those packages in /etc/portage/package.keywords? I already had '~x86' for most of my "missing" packages and when I tried package.unmask for any of them, it failed to change the problem. emaint --fix world only deletes the packeges from the db.
Can you give an example of such a package? What version do you have installed? What is your ACCEPT_KEYWORDS? What do you have in package.keywords and package.unmask for it?
(In reply to comment #6) > Can you give an example of such a package? What version do you have installed? > What is your ACCEPT_KEYWORDS? What do you have in package.keywords and > package.unmask for it? > Package is Gnome Volume Manager Current Version Installed 1.5.4 Gnome-2.12.1 (make.conf) ACCEPT_KEYWORDS="x86" (package.keywords) gnome-base/gnome-volume-manager ~x86
That package shouldn't appear at all. $ grep KEYWORDS *.ebuild gnome-volume-manager-1.2.1.ebuild:KEYWORDS="amd64 ia64 ppc ppc64 x86" gnome-volume-manager-1.2.2.ebuild:KEYWORDS="amd64 ia64 ppc ppc64 ~sparc x86" gnome-volume-manager-1.5.1.ebuild:KEYWORDS="~amd64 ~ppc ~sparc ~x86" gnome-volume-manager-1.5.3.ebuild:KEYWORDS="~amd64 ~ppc ~ppc64 ~sparc ~x86" gnome-volume-manager-1.5.4.ebuild:KEYWORDS="~amd64 ~ia64 ~ppc ~ppc64 ~sparc ~x86" Nothing in profiles/package.mask. Do you happen to have it in /etc/portage/package.mask?
(In reply to comment #8) > That package shouldn't appear at all. > > $ grep KEYWORDS *.ebuild > gnome-volume-manager-1.2.1.ebuild:KEYWORDS="amd64 ia64 ppc ppc64 x86" > gnome-volume-manager-1.2.2.ebuild:KEYWORDS="amd64 ia64 ppc ppc64 ~sparc x86" > gnome-volume-manager-1.5.1.ebuild:KEYWORDS="~amd64 ~ppc ~sparc ~x86" > gnome-volume-manager-1.5.3.ebuild:KEYWORDS="~amd64 ~ppc ~ppc64 ~sparc ~x86" > gnome-volume-manager-1.5.4.ebuild:KEYWORDS="~amd64 ~ia64 ~ppc ~ppc64 ~sparc > ~x86" > > Nothing in profiles/package.mask. > > Do you happen to have it in /etc/portage/package.mask? > I don't have a package.mask in /etc/portage. Only package.keywords/use/unmask and it is in none of those. I have many gnome packages that are the same as this one, none of those have shown up in emaint --check. I still reckon this is a problem with the upgraded portage.
Have re-emerged portage-2.0.51.22-r3 and problem not there. Also 'emaint' has disappeared, was that in the new portage? I think I may leave upgrading portage until this has been fixed
Err, eh? What exactly is the issue? You seem to be saying that emaint isn't showing a package that has no problem.
Also, you are the only one that has had an issue other than masked packages not being shown separately to packages that are not available. Waiting for the issue to be fixed without your input will just lead to you never upgrading again...
(In reply to comment #12) > Also, you are the only one that has had an issue other than masked packages not > being shown separately to packages that are not available. Waiting for the > issue to be fixed without your input will just lead to you never upgrading > again... > Yesterday I ran (as I do once a week or so) ---- rob rob # emerge --sync (there was new version of portage) ---- rob rob # emerge -av portage These are the packages that I would merge, in order: Calculating world dependencies ...done! [ebuild N ] app-misc/pax-utils-0.1.4 -caps 44 kB [ebuild U ] sys-apps/portage-2.0.53 [2.0.51.22-r3] -build (-selinux) 229 kB Total size of downloads: 0 kB Do you want me to merge these packages? [Yes/No] y ---- rob rob # etc-update Scanning Configuration files... Automerging trivial changes in: etc-update.conf Automerging trivial changes in: make.conf.example Exiting: Nothing left to do; exiting. :) ---- rob rob # emerge -av portage Calculating world dependencies !!! Problems have been detected with your world file !!! Please run emaint --check world ---- rob rob # emaint --check world Checking world for problems 'net-im/skype' has no ebuilds available 'gnome-base/gnome-volume-manager' has no ebuilds available Finished ---- ---- Skype is emerged stable and gnome-volume-manager is emerged as stated in message above. This all the input I have, I am not a coder, can only try things if asked. I did look at doing "emaint --fix world" but found from comment on forums this only deletes those entries from the world. Every comment seems to talking about masks and keywords, but I know only enough to be dangerous, so I decided to downgrade portage to the last version. It seems that emaint is part of the new portage, or perhaps it only works with that version as I now am unable to call that program. I tried "find / -name emaint" but had no returns on the query.
> Exiting: Nothing left to do; exiting. :) > ---- > rob rob # emerge -av portage > > Calculating world dependencies > !!! Problems have been detected with your world file > !!! Please run emaint --check world > ---- > OOPS, that should read ---- rob rob # emerge -avuD world Calculating world dependencies !!! Problems have been detected with your world file !!! Please run emaint --check world ---- Middle click doesn't work from console to gui ;-(
There is only one skype ebuild available and it is ~x86. Adding it to package.keywords should fix that one. As for gnome-volume-manager, I'm a bit confused. What does the following give? # python -c 'import portage; print portage.portdb.xmatch("match-visible", "gnome-base/gnome-volume-manager")' On my system, I get: ['gnome-base/gnome-volume-manager-1.2.1', 'gnome-base/gnome-volume-manager-1.5.3', 'gnome-base/gnome-volume-manager-1.2.2', 'gnome-base/gnome-volume-manager-1.5.1', 'gnome-base/gnome-volume-manager-1.5.4'] If emaint is complaining about that package, you should get [].
> > If emaint is complaining about that package, you should get []. > Nope, got the same as you listed all ebuilds from 1.2.1 to 1.5.4. After that have re-emerged portage to the newer version again and now emaint returns "skype" and "hal-device-manager" with no ebuilds, no mention of gnome-volume-manager. Is there something wrong with my db? Or did it just mistep before. I double checked, the console (#2) still has "gnome-volume-manager" from yesterday on it and the new message is definitely "hal-device-manager" on console (#3) Haven't rebooted at all, should I? Quietly going crazy here :-)
hal-device-manager has two versions, both of which are ~arch. If that and skype are both not in package.keywords then the warnings are valid (though cryptic). gnome-volume-manager? Don't know. Perhaps something in the environment. If it can't be reproduced though...
(In reply to comment #17) > hal-device-manager has two versions, both of which are ~arch. If that and skype > are both not in package.keywords then the warnings are valid (though cryptic). > > gnome-volume-manager? Don't know. Perhaps something in the environment. If it > can't be reproduced though... > Does this mean the bug is not with the program, but with packages having their keywords changed in later ebuilds?
Not dealing with ebuilds much, I'm having trouble following the ChangeLogs. However, it doesn't appear that the versions you have installed were ever stabled...
>>Middle click doesn't work from console to gui ;-( True, but it does if run your cli from xterm ;) Generally on this bug , please anticipate problems and issue useful msgs. Cryptic/inappropriate error messages waste everyone's time. cf * no longer being valid syntax in package.mask. You know this will throw errors on a lot of systems, why not detect it and give an example instead of "invalid item" and let everyone sort out the mess on the forums? Gentoo needs too much maintaining because of this sort of thing. Please spare a thought for usablility. Thx
(In reply to comment #20) > Generally on this bug , please anticipate problems and issue useful msgs. > Cryptic/inappropriate error messages waste everyone's time. Something about being in the eye of the beholder... > cf * no longer being valid syntax in package.mask. You know this will throw > errors on a lot of systems, why not detect it and give an example instead of > "invalid item" and let everyone sort out the mess on the forums? Err.. What are you talking about? > Gentoo needs too much maintaining because of this sort of thing. > > Please spare a thought for usablility. Omnipresence is quite difficult to achieve, but I'll give it a try.
To reword the last comment, these issues all existed before but portage just ignored them. Bringing them into the light so that users can better maintain there systems is a move forward in usability. To comments such as yours, there's only one thing to be said: "If you want a job done right, you have to do it yourself."
(In reply to comment #20) > >>Middle click doesn't work from console to gui ;-( > True, but it does if run your cli from xterm ;) > Explaining typo, sorry if too simple for your complex mind !! > Generally on this bug , please anticipate problems and issue useful msgs. > Cryptic/inappropriate error messages waste everyone's time. > Real smart-arse aren't you? > cf * no longer being valid syntax in package.mask. You know this will throw > errors on a lot of systems, why not detect it and give an example instead of > "invalid item" and let everyone sort out the mess on the forums? > I too have no idea what you are talking about there. > Gentoo needs too much maintaining because of this sort of thing. > > Please spare a thought for usablility. > Thx > I am, that is why I have elected to try and help with this, even though it will only be as a test bed. By the way, if you are so good, why haven't you fixed the problem being displayed?
Keep it civil (regardless of your views of the person your responding to)- applies to everyone.
Released in 2.1_pre2.
The fix at 2.1_pre2 has a message of "Masked ebuilds can be manually unmasked with package.keywords or package.unmask". However, this message appears vertically. Like this: M a s k e d e b u i l d s (and so forth). Should I file a new bug about this?
It seems to be fixed in portage 2.1_pre3-r1