Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
Not eligible to see or edit group visibility for this bug.
View Bug Activity | Format For Printing | XML | Clone This Bug
Updating Portage cache: 88%!!! Cannot resolve a virtual package name to an ebuild. !!!! This is a bug, please report it. (virtual/x11-6.8) Reproducible: Always Steps to Reproduce: 1. emerge sync 2. wait :-) Actual Results: Portage is incorrect :-( Expected Results: i think you know...
This is not a bug in x11, this is a bug in whatever ebuild depends on a versioned virtual.
(In reply to comment #1) > This is not a bug in x11, this is a bug in whatever ebuild depends on a > versioned virtual. shrug... there's no such ebuild or eclass in portage that would depend on virtual/x11-6.8; so either the user has some crap in overlay or the problem is somewhere else.
I'll give it to the portage guys then. Indeed, I checked: donnie@supernova /usr/local/share/gentoo-x86 $ find ./ -name '*.ebuild' | xargs -n1000 grep virtual/x11-6 donnie@supernova /usr/local/share/gentoo-x86 $
*** Bug 114829 has been marked as a duplicate of this bug. ***
Portage versions prior to 2.0.51.20 (which was released almost 8 months ago) will have this problem.
I had the same problem. For newbies, After the ... wrote 681 bytes read 3358865 bytes 21062.98 bytes/sec total size is 107648311 speedup is 32.04 >>> Updating Portage cache: 88%!!! Cannot resolve a virtual package name to an ebuild. !!! This is a bug, please report it. (virtual/x11-6.8) Do the following #emerge --av portage #emerge --sync This fixes the issue for me as per Jason Stubbs comment. Thanks
*** Bug 114910 has been marked as a duplicate of this bug. ***
*** Bug 114934 has been marked as a duplicate of this bug. ***
(In reply to comment #0) > Updating Portage cache: 88%!!! Cannot resolve a virtual package name to an > ebuild. !!!! This is a bug, please report it. (virtual/x11-6.8) > > Reproducible: Always > Steps to Reproduce: > 1. emerge sync > 2. wait :-) > > Actual Results: > Portage is incorrect :-( > > Expected Results: > i think you know... (In reply to comment #0) > Updating Portage cache: 88%!!! Cannot resolve a virtual package name to an > ebuild. !!!! This is a bug, please report it. (virtual/x11-6.8) > > Reproducible: Always > Steps to Reproduce: > 1. emerge sync > 2. wait :-) > > Actual Results: > Portage is incorrect :-( > > Expected Results: > i think you know... In reply to comment #6 'emerge --av portage' is an invalid option on my system. ??
(In reply to comment #9) > > In reply to comment #6 > > 'emerge --av portage' is an invalid option on my system. ?? Try 'emerge -av portage'. And, yes, upgrading to portage-2.0.51.22-r3 from 2.0.51-r3, then syncing my portage tree fixed the problem for me. :) Thanks, Tom
*** Bug 115104 has been marked as a duplicate of this bug. ***
Re-emerging/updating portage and running emerge --sync did fix the problem for me on a new 2005.1 install. Not sure if I should paste my long forum post with system details: http://forums.gentoo.org/viewtopic-t-410139.html. Here is my emerge --info which I didn't put in the post Portage 2.0.51.22-r3 (default-linux/x86/2005.1, gcc-3.4.4, glibc-2.3.5-r2, 2.6.14-gentoo-r4 i686) ================================================================= System uname: 2.6.14-gentoo-r4 i686 Intel(R) Celeron(R) CPU 2.66GHz Gentoo Base System version 1.6.13 dev-lang/python: 2.3.5-r2, 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.20 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-Os -march=pentium4 -pipe -O3 -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-Os -march=pentium4 -pipe -O3 -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://prometheus.cs.wmich.edu/gentoo http://cudlug.cudenver.edu/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="x86 X acpi alsa apache2 avi berkdb bitmap-fonts bzip2 cdr cdrom chroot crypt divx4linux dvd eds emboss encode expat fortran gdbm gif gstreamer gtk gtk2 imlib jpeg libg++ libwww mad maildir mikmod motif mp3 mpeg mplayer mysql ncurses nls offensive ogg oggvorbis openal opengl oss pam pcap pcre pda pdf pdflib perl php png pthreads python quicktime readline real sdl spell ssl svg tcltk tcpd tiff truetype truetype-fonts type1-fonts udev usb v4l v4l2 vorbis win32codecs xml2 xmms xrandr xv xvid yahoo zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
(In reply to comment #12) > Re-emerging/updating portage and running emerge --sync did fix the problem for sorry...should be it did NOT fix the problem.
Number of files: 131265 Number of files transferred: 16488 Total file size: 107417653 bytes Total transferred file size: 25432340 bytes Literal data: 25432340 bytes Matched data: 0 bytes File list size: 3040640 Total bytes written: 329941 Total bytes read: 29216654 wrote 329941 bytes read 29216654 bytes 245199.96 bytes/sec total size is 107417653 speedup is 3.64 >>> Updating Portage cache: 88%!!! Cannot resolve a virtual package name to an ebuild. !!! This is a bug, please report it. (virtual/x11-6.8)
I found that the /etc/make.profile link was pointing to the wrong place. Should have been (in my case): /etc/make.profile -> /usr/portage/profiles/default-linux/x86/2005.1 (was pointing to /2004.3 or something, I forget now...) This has happened to me before in other system-level upgrades
*** Bug 115325 has been marked as a duplicate of this bug. ***
*** Bug 115343 has been marked as a duplicate of this bug. ***
*** Bug 115457 has been marked as a duplicate of this bug. ***
*** Bug 115534 has been marked as a duplicate of this bug. ***
Are there still issues? There doesn't seem to be...
*** Bug 115936 has been marked as a duplicate of this bug. ***
*** Bug 115942 has been marked as a duplicate of this bug. ***
*** Bug 116065 has been marked as a duplicate of this bug. ***
*** Bug 116060 has been marked as a duplicate of this bug. ***
*** Bug 116168 has been marked as a duplicate of this bug. ***
I just had same problem on a x86 machine I had not updated since quite a long time (~ 6 months ), but with virtual/libstdc++-3.3 . Updating portage (it was 2.0.51.19 I believe) fixed the problem. Is it the same bug or should I file a new one ?
Same bug..
*** Bug 116408 has been marked as a duplicate of this bug. ***
Are all these duplicates coming from people still running earlier than 2.0.51.20?
*** Bug 116461 has been marked as a duplicate of this bug. ***
*** Bug 116522 has been marked as a duplicate of this bug. ***
*** Bug 116544 has been marked as a duplicate of this bug. ***
*** Bug 116556 has been marked as a duplicate of this bug. ***
My duplicate (very embarrasing) is portage 2.0.51.19
*** Bug 116572 has been marked as a duplicate of this bug. ***
*** Bug 116621 has been marked as a duplicate of this bug. ***
*** Bug 116664 has been marked as a duplicate of this bug. ***
*** Bug 116675 has been marked as a duplicate of this bug. ***
*** Bug 116717 has been marked as a duplicate of this bug. ***
*** Bug 116839 has been marked as a duplicate of this bug. ***
*** Bug 116883 has been marked as a duplicate of this bug. ***
*** Bug 116904 has been marked as a duplicate of this bug. ***
*** Bug 116969 has been marked as a duplicate of this bug. ***
*** Bug 117039 has been marked as a duplicate of this bug. ***
*** Bug 117069 has been marked as a duplicate of this bug. ***
*** Bug 117113 has been marked as a duplicate of this bug. ***
*** Bug 117164 has been marked as a duplicate of this bug. ***
*** Bug 117241 has been marked as a duplicate of this bug. ***
*** Bug 117248 has been marked as a duplicate of this bug. ***
*** Bug 117301 has been marked as a duplicate of this bug. ***
*** Bug 117359 has been marked as a duplicate of this bug. ***
I did emerge sync: >>> Updating Portage cache: 90%!!! Cannot resolve a virtual package name to an ebuild. !!! This is a bug, please report it. (virtual/libstdc++-3.3) I was updating a Gentoo (chroot'ed) partition which has not been used since Feb 28, 2005. The /etc/make.profile link was dangling after emerge sync. This one solves after updating portage. Thank you to developers and users for the dialogue on this bug-report.
*** Bug 117404 has been marked as a duplicate of this bug. ***
this bug is fixed, so I will close it. Users: if you hit this you need to emerge -u portage.
*** Bug 117689 has been marked as a duplicate of this bug. ***
*** Bug 117721 has been marked as a duplicate of this bug. ***
*** Bug 117730 has been marked as a duplicate of this bug. ***
emerge -u portage did not work got halfway and stopped, synced again and message saying that: ARCH is not set... Are you missing the /etc/make.profile symlink? !!! Is the symlink correct ? Is your portage tree complete? now emerge does not work at all except by reloading the snapshot off the live CD but that sends me round in circles
*** Bug 117779 has been marked as a duplicate of this bug. ***
*** Bug 117880 has been marked as a duplicate of this bug. ***
*** Bug 117905 has been marked as a duplicate of this bug. ***
*** Bug 118129 has been marked as a duplicate of this bug. ***
*** Bug 118352 has been marked as a duplicate of this bug. ***
*** Bug 118548 has been marked as a duplicate of this bug. ***
*** Bug 118596 has been marked as a duplicate of this bug. ***
*** Bug 118597 has been marked as a duplicate of this bug. ***
*** Bug 118602 has been marked as a duplicate of this bug. ***
*** Bug 118617 has been marked as a duplicate of this bug. ***
*** Bug 118618 has been marked as a duplicate of this bug. ***
*** Bug 118641 has been marked as a duplicate of this bug. ***
*** Bug 116396 has been marked as a duplicate of this bug. ***
*** Bug 116390 has been marked as a duplicate of this bug. ***
*** Bug 118764 has been marked as a duplicate of this bug. ***
Well, for me it's: (I've already corrected the dangling symlink for /etc/make.profile) # emerge --info Portage 2.0.51.19 (default-linux/sparc/sparc64/2005.1, gcc-3.3.5-20050130, glibc-2.3.3.20040420-r2, 2.4.27 sparc64) ================================================================= System uname: 2.4.27 sparc64 sun4u Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Apr 2 2005, 06:26:50)] ccache version 2.3 [enabled] dev-lang/python: 2.3.4-r1 sys-apps/sandbox: [Not Present] sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r7 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.6.8.1-r4 ACCEPT_KEYWORDS="sparc" AUTOCLEAN="yes" CFLAGS="-O2 -mcpu=ultrasparc" CHOST="sparc-unknown-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -mcpu=ultrasparc" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://src.gentoo.pl http://gentoo.inode.at http://gentoo.netnitco.net" LANG="pl_PL" LC_ALL="pl_PL" LINGUAS="pl" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="sparc X aim arts audiofile avi bash-completion berkdb bitmap-fonts bzip2 crypt cups curl dlloader eds encode esd exif expat fbcon font-server foomaticdb fortran gcc64 gdbm gif glut gnome gpm gstreamer gtk gtk2 gtkhtml icq idn imlib innodb jabber java javamail jpeg junit justify kde lcms ldap libwww mad mhash mikmod mime mng motif mozilla mozsvg mozxmlterm mpeg msn mysql ncurses nls nptl ogg oggvorbis opengl oss pam pcre pdflib perl php png postgres python qt readline samba sdl slang soap spell ssl svg tcpd tetex tidy tiff truetype truetype-fonts type1-fonts unicode userlocales vorbis wmf xml2 xmlrpc xmms xpm xsl xv yahoo zlib linguas_pl userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CBUILD, CTARGET, LDFLAGS The following did the trick in my case: # emerge -avu1 --nodeps portage HTH
*** Bug 118843 has been marked as a duplicate of this bug. ***
*** Bug 118944 has been marked as a duplicate of this bug. ***
*** Bug 118949 has been marked as a duplicate of this bug. ***
*** Bug 119011 has been marked as a duplicate of this bug. ***
*** Bug 119044 has been marked as a duplicate of this bug. ***
*** Bug 119157 has been marked as a duplicate of this bug. ***
*** Bug 119207 has been marked as a duplicate of this bug. ***
*** Bug 119225 has been marked as a duplicate of this bug. ***
*** Bug 119681 has been marked as a duplicate of this bug. ***
*** Bug 119834 has been marked as a duplicate of this bug. ***
*** Bug 119922 has been marked as a duplicate of this bug. ***
*** Bug 120060 has been marked as a duplicate of this bug. ***
*** Bug 120124 has been marked as a duplicate of this bug. ***
*** Bug 120251 has been marked as a duplicate of this bug. ***
*** Bug 120424 has been marked as a duplicate of this bug. ***
*** Bug 120594 has been marked as a duplicate of this bug. ***
*** Bug 120755 has been marked as a duplicate of this bug. ***
*** Bug 120786 has been marked as a duplicate of this bug. ***
*** Bug 120804 has been marked as a duplicate of this bug. ***
*** Bug 120886 has been marked as a duplicate of this bug. ***
*** Bug 120909 has been marked as a duplicate of this bug. ***
*** Bug 120944 has been marked as a duplicate of this bug. ***
*** Bug 121070 has been marked as a duplicate of this bug. ***
*** Bug 121072 has been marked as a duplicate of this bug. ***
*** Bug 121096 has been marked as a duplicate of this bug. ***
*** Bug 121227 has been marked as a duplicate of this bug. ***
*** Bug 121304 has been marked as a duplicate of this bug. ***
(In reply to comment #6) I ran "emerge --av portage" and recieved "!!!ERROR: --av is an invalid option" what next?? > I had the same problem. > For newbies, > After the > ... > wrote 681 bytes read 3358865 bytes 21062.98 bytes/sec > total size is 107648311 speedup is 32.04 > >>> Updating Portage cache: 88%!!! Cannot resolve a virtual package name to an > ebuild. > !!! This is a bug, please report it. (virtual/x11-6.8) > Do the following > #emerge --av portage > #emerge --sync > This fixes the issue for me as per Jason Stubbs comment. > Thanks
*** Bug 121323 has been marked as a duplicate of this bug. ***
*** Bug 121472 has been marked as a duplicate of this bug. ***
*** Bug 121627 has been marked as a duplicate of this bug. ***
*** Bug 121677 has been marked as a duplicate of this bug. ***
*** Bug 121691 has been marked as a duplicate of this bug. ***
*** Bug 121748 has been marked as a duplicate of this bug. ***
emerge -av portage fixed it, thanks
*** Bug 121903 has been marked as a duplicate of this bug. ***
*** Bug 122112 has been marked as a duplicate of this bug. ***
*** Bug 122132 has been marked as a duplicate of this bug. ***
*** Bug 122255 has been marked as a duplicate of this bug. ***
*** Bug 122313 has been marked as a duplicate of this bug. ***
*** Bug 122330 has been marked as a duplicate of this bug. ***
*** Bug 122364 has been marked as a duplicate of this bug. ***
*** Bug 122422 has been marked as a duplicate of this bug. ***
*** Bug 122472 has been marked as a duplicate of this bug. ***
*** Bug 122504 has been marked as a duplicate of this bug. ***
*** Bug 122544 has been marked as a duplicate of this bug. ***
*** Bug 122695 has been marked as a duplicate of this bug. ***
*** Bug 122719 has been marked as a duplicate of this bug. ***
*** Bug 122918 has been marked as a duplicate of this bug. ***
*** Bug 122937 has been marked as a duplicate of this bug. ***
*** Bug 122975 has been marked as a duplicate of this bug. ***
*** Bug 123020 has been marked as a duplicate of this bug. ***
*** Bug 123122 has been marked as a duplicate of this bug. ***
*** Bug 123243 has been marked as a duplicate of this bug. ***
*** Bug 123300 has been marked as a duplicate of this bug. ***
*** Bug 123441 has been marked as a duplicate of this bug. ***
*** Bug 123473 has been marked as a duplicate of this bug. ***
*** Bug 123548 has been marked as a duplicate of this bug. ***
*** Bug 123612 has been marked as a duplicate of this bug. ***
*** Bug 123701 has been marked as a duplicate of this bug. ***
*** Bug 123730 has been marked as a duplicate of this bug. ***
*** Bug 123788 has been marked as a duplicate of this bug. ***
*** Bug 123914 has been marked as a duplicate of this bug. ***
*** Bug 124097 has been marked as a duplicate of this bug. ***
*** Bug 124294 has been marked as a duplicate of this bug. ***
*** Bug 124369 has been marked as a duplicate of this bug. ***
*** Bug 124586 has been marked as a duplicate of this bug. ***
*** Bug 124713 has been marked as a duplicate of this bug. ***
*** Bug 124798 has been marked as a duplicate of this bug. ***
*** Bug 125008 has been marked as a duplicate of this bug. ***
*** Bug 125058 has been marked as a duplicate of this bug. ***
*** Bug 125092 has been marked as a duplicate of this bug. ***
*** Bug 125541 has been marked as a duplicate of this bug. ***
*** Bug 125739 has been marked as a duplicate of this bug. ***
*** Bug 126308 has been marked as a duplicate of this bug. ***
*** Bug 126576 has been marked as a duplicate of this bug. ***
*** Bug 126746 has been marked as a duplicate of this bug. ***
*** Bug 126887 has been marked as a duplicate of this bug. ***
*** Bug 126952 has been marked as a duplicate of this bug. ***
*** Bug 127055 has been marked as a duplicate of this bug. ***
*** Bug 127212 has been marked as a duplicate of this bug. ***
*** Bug 127250 has been marked as a duplicate of this bug. ***
*** Bug 127551 has been marked as a duplicate of this bug. ***
*** Bug 127857 has been marked as a duplicate of this bug. ***
*** Bug 127967 has been marked as a duplicate of this bug. ***
*** Bug 127999 has been marked as a duplicate of this bug. ***
*** Bug 128110 has been marked as a duplicate of this bug. ***
*** Bug 128279 has been marked as a duplicate of this bug. ***
*** Bug 128516 has been marked as a duplicate of this bug. ***
*** Bug 128724 has been marked as a duplicate of this bug. ***
*** Bug 128757 has been marked as a duplicate of this bug. ***
*** Bug 128898 has been marked as a duplicate of this bug. ***
*** Bug 129049 has been marked as a duplicate of this bug. ***
*** Bug 129078 has been marked as a duplicate of this bug. ***
*** Bug 129291 has been marked as a duplicate of this bug. ***
*** Bug 129403 has been marked as a duplicate of this bug. ***
*** Bug 129484 has been marked as a duplicate of this bug. ***
*** Bug 129899 has been marked as a duplicate of this bug. ***
*** Bug 130511 has been marked as a duplicate of this bug. ***
*** Bug 131043 has been marked as a duplicate of this bug. ***
*** Bug 131241 has been marked as a duplicate of this bug. ***
*** Bug 131251 has been marked as a duplicate of this bug. ***
*** Bug 131904 has been marked as a duplicate of this bug. ***
*** Bug 132724 has been marked as a duplicate of this bug. ***
*** Bug 132933 has been marked as a duplicate of this bug. ***
*** Bug 132991 has been marked as a duplicate of this bug. ***
*** Bug 133073 has been marked as a duplicate of this bug. ***
*** Bug 120455 has been marked as a duplicate of this bug. ***
*** Bug 120457 has been marked as a duplicate of this bug. ***
*** Bug 133315 has been marked as a duplicate of this bug. ***
*** Bug 133388 has been marked as a duplicate of this bug. ***
*** Bug 133577 has been marked as a duplicate of this bug. ***
*** Bug 134056 has been marked as a duplicate of this bug. ***
*** Bug 134278 has been marked as a duplicate of this bug. ***
*** Bug 134286 has been marked as a duplicate of this bug. ***
*** Bug 119749 has been marked as a duplicate of this bug. ***
*** Bug 134316 has been marked as a duplicate of this bug. ***
*** Bug 134548 has been marked as a duplicate of this bug. ***
*** Bug 134708 has been marked as a duplicate of this bug. ***
Mediawiki-1.6.7 is wrong! >>> Emerging (1 of 1) www-apps/mediawiki-1.6.7 to / >>> checking ebuild checksums ;-) >>> checking auxfile checksums ;-) >>> checking miscfile checksums ;-) >>> checking mediawiki-1.6.7.tar.gz !!! Digest verification failed: !!! /usr/portage/distfiles/mediawiki-1.6.7.tar.gz !!! Reason: Filesize does not match recorded size !!! Got: 2728980 !!! Expected: 12208
(In reply to comment #195) > Mediawiki-1.6.7 is wrong! > > >>> Emerging (1 of 1) www-apps/mediawiki-1.6.7 to / > >>> checking ebuild checksums ;-) > >>> checking auxfile checksums ;-) > >>> checking miscfile checksums ;-) > >>> checking mediawiki-1.6.7.tar.gz > !!! Digest verification failed: > !!! /usr/portage/distfiles/mediawiki-1.6.7.tar.gz > !!! Reason: Filesize does not match recorded size > !!! Got: 2728980 > !!! Expected: 12208 > That has nothing to do with this bug, please file a bug seperately
Oh Shit ^^ Sry :(
*** Bug 139111 has been marked as a duplicate of this bug. ***
*** Bug 139680 has been marked as a duplicate of this bug. ***
*** Bug 140408 has been marked as a duplicate of this bug. ***
Created an attachment (id=92572) [edit] results of emerge --info
Created an attachment (id=92573) [edit] results of uname -a (my sysinfo)
Created an attachment (id=92574) [edit] the error outputted after running emerge --sync
Created an attachment (id=92575) [edit] results of sysctl -a (my sys info)
This bug has been fixed. that means we no longer need any output of if either emerge --info, uname -a, emerge --sync or sysctl -a. It's already done, there's nothing more to do.
*** Bug 141646 has been marked as a duplicate of this bug. ***
*** Bug 144708 has been marked as a duplicate of this bug. ***
*** Bug 145600 has been marked as a duplicate of this bug. ***
*** Bug 145752 has been marked as a duplicate of this bug. ***
*** Bug 145865 has been marked as a duplicate of this bug. ***
*** Bug 147288 has been marked as a duplicate of this bug. ***
*** Bug 147460 has been marked as a duplicate of this bug. ***
*** Bug 149456 has been marked as a duplicate of this bug. ***
Backwards compatability is a wonderful thing, isnt it? Looking at the level of confusion caused and the ammount of dev time wasted by this one, it would be useful to draw some lessons about the benefits of maintaining compatability. Sometimes changes really are unavoidable but it this sort of breakage should be kept to the absolute minimum. ;)
*** Bug 155737 has been marked as a duplicate of this bug. ***
*** Bug 156794 has been marked as a duplicate of this bug. ***
*** Bug 166579 has been marked as a duplicate of this bug. ***
*** Bug 170151 has been marked as a duplicate of this bug. ***
*** Bug 173719 has been marked as a duplicate of this bug. ***
*** Bug 177090 has been marked as a duplicate of this bug. ***
*** Bug 178666 has been marked as a duplicate of this bug. ***
*** Bug 184841 has been marked as a duplicate of this bug. ***
*** Bug 185671 has been marked as a duplicate of this bug. ***
*** Bug 186593 has been marked as a duplicate of this bug. ***
*** Bug 189006 has been marked as a duplicate of this bug. ***
*** Bug 193125 has been marked as a duplicate of this bug. ***
I succeeded in updating portage with: emerge -avu1 --nodeps portage But now whenever I run emerge, I get the following error: emerge -s portage File "/usr/bin/emerge", line 704 for cpv in portdb.match(cp)) ^ SyntaxError: invalid syntax Any advice? Or should this go to a forum or another bug?
(In reply to comment #227) > I succeeded in updating portage with: > emerge -avu1 --nodeps portage --nodeps is dangerous. Maybe you need to update python. Follow these instructions and try again without --nodeps: http://www.gentoo.org/proj/en/portage/doc/manually-fixing-portage.xml
Thanks. The reason I went the nodeps route was because the other suggestions in the comments for updating portage didn't work. Having followed the instructions on the link provided I still get the same syntax error when running any emerge command: emerge --help File "/usr/bin/emerge", line 704 for cpv in portdb.match(cp)) ^ SyntaxError: invalid syntax
(In reply to comment #229) > File "/usr/bin/emerge", line 704 > for cpv in portdb.match(cp)) > ^ > SyntaxError: invalid syntax The portage version that you unpacked is not compatible with your version of python. Try portage-2.1.1.tar.bz2 or even portage-2.0.51.22.tar.bz2 if necessary. If you still can't get it working then you should use an irc client to join #gentoo-portage on irc.freenode.net.
(In reply to comment #230) > (In reply to comment #229) > > File "/usr/bin/emerge", line 704 > > for cpv in portdb.match(cp)) > > ^ > > SyntaxError: invalid syntax > > The portage version that you unpacked is not compatible with your version of > python. Try portage-2.1.1.tar.bz2 or even portage-2.0.51.22.tar.bz2 if > necessary. If you still can't get it working then you should use an irc client > to join #gentoo-portage on irc.freenode.net. > I'm in a big pickle here. I'm getting this error when I try to emerge portage or python. Cannot resolve a virtual package name to an ebuild. !!! This is a bug, please report it. (virtual/libiconv-0) I have portage-2.0.51.19 and python-2.3.4-r2 installed now. Should I just go ahead and emerge them both with nodeps?
Don't use --nodeps. Follow these instructions and pay careful attention the the part about python version compatibility: http://www.gentoo.org/proj/en/portage/doc/manually-fixing-portage.xml
*** Bug 199906 has been marked as a duplicate of this bug. ***
*** Bug 203973 has been marked as a duplicate of this bug. ***
*** Bug 212897 has been marked as a duplicate of this bug. ***
*** Bug 217969 has been marked as a duplicate of this bug. ***
I've run into this bug today. For background only I have a 3 PC MythTV system at my parent's house. I built it back in 2005 I think and haven't touched it since. Finally we wanted to do some updates to it and I ran into this same bug. I agree with a comment earlier in this thread that it would be better if there was *some* level of backward compatibility instead of things just dying. None the less here we are: deleting app-accessibility/brltty/brltty-3.6.1.ebuild deleting app-accessibility/brltty/brltty-3.5.ebuild deleting app-accessibility/at-poke/files/digest-at-poke-0.2.2 deleting app-accessibility/SphinxTrain/files/digest-SphinxTrain-0.9.1-r1 Number of files: 124331 Number of files transferred: 95646 Total file size: 155953991 bytes Total transferred file size: 146299148 bytes Literal data: 146299148 bytes Matched data: 0 bytes File list size: 3029296 Total bytes written: 1913101 Total bytes read: 153638454 wrote 1913101 bytes read 153638454 bytes 237302.14 bytes/sec total size is 155953991 speedup is 1.00 >>> Updating Portage cache: 90%!!! Cannot resolve a virtual package name to an ebuild. !!! This is a bug, please report it. (virtual/ada-1995) myth11 ~ # Unfortunately the problem on this machine goes further as portage has completely removed every profile that was on the system and replaced them with new profiles. There is no overlap! OLD PROFILES BEFORE emerge --sync: myth11 ~ # ls -la /usr/portage/profiles/default-linux/x86/ total 60 drwxr-xr-x 10 root root 4096 Jun 3 2005 . drwxr-xr-x 15 root root 4096 Jun 2 2005 .. drwxr-xr-x 2 root root 4096 Apr 22 2005 2004.0 drwxr-xr-x 3 root root 4096 Apr 22 2005 2004.2 drwxr-xr-x 2 root root 4096 Jun 22 2005 2004.3 drwxr-xr-x 3 root root 4096 Mar 28 2005 2005.0 drwxr-xr-x 3 root root 4096 Jun 3 2005 2005.1 drwxr-xr-x 2 root root 4096 May 9 2005 gcc2 drwxr-xr-x 2 root root 4096 May 9 2005 gcc31 -rw-r--r-- 1 root root 774 May 26 2005 make.defaults -rw-r--r-- 1 root root 563 Apr 28 2005 packages -rw-r--r-- 1 root root 336 May 9 2005 parent -rw-r--r-- 1 root root 539 May 20 2005 use.mask -rw-r--r-- 1 root root 449 Oct 25 2004 virtuals drwxr-xr-x 2 root root 4096 May 9 2005 xbox myth11 ~ # NEW PROFILES AFTER emerge --sync: myth11 ~ # ls -la /usr/portage/profiles/default-linux/x86/ total 88 drwxr-xr-x 9 root root 4096 Apr 25 11:37 . drwxr-xr-x 14 root root 4096 Apr 25 11:37 .. drwxr-xr-x 4 root root 4096 Aug 8 2007 2006.1 drwxr-xr-x 4 root root 4096 Aug 8 2007 2007.0 -rw-r--r-- 1 root root 23874 Apr 21 04:37 ChangeLog drwxr-xr-x 2 root root 4096 Apr 25 11:37 dev drwxr-xr-x 2 root root 4096 Aug 8 2007 gcc2 -rw-r--r-- 1 root root 1145 May 15 2007 make.defaults drwxr-xr-x 2 root root 4096 Apr 25 11:37 no-nptl -rw-r--r-- 1 root root 2940 Apr 21 04:37 package.mask -rw-r--r-- 1 root root 411 Jan 13 15:36 package.use.mask -rw-r--r-- 1 root root 563 Apr 28 2005 packages -rw-r--r-- 1 root root 3 Dec 2 2005 parent -rw-r--r-- 1 root root 1820 Apr 9 23:37 use.mask -rw-r--r-- 1 root root 402 Feb 23 2006 virtuals drwxr-xr-x 3 root root 4096 Mar 30 09:07 vserver drwxr-xr-x 2 root root 4096 Aug 8 2007 xbox myth11 ~ # I suspect that the correct upgrade path is to do the profile change, update the system step by step and slowly get it fixed. I really dislike that portage removes things from my system without warning me. emerge --sync breaks my very old but correctly working system. Off to profile update land.
*** Bug 222579 has been marked as a duplicate of this bug. ***
*** Bug 224631 has been marked as a duplicate of this bug. ***
*** Bug 230029 has been marked as a duplicate of this bug. ***
