Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 73970 - Invalid atom in /usr/portage/profiles/default-linux/x86/2005.0/packages
Summary: Invalid atom in /usr/portage/profiles/default-linux/x86/2005.0/packages
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High normal
Assignee: Chris Gianelloni (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-09 19:04 UTC by Alok Singhal
Modified: 2004-12-10 07:05 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alok Singhal 2004-12-09 19:04:30 UTC
I upgraded my portage profile to 2005.0 by making /etc/make.profile -> ../usr/portage/profiles/default-linux/x86/2005.0 link.

Now, whenever I use emerge, I get a bunch of error messages:

--- Invalid atom in /usr/portage/profiles/default-linux/x86/2005.0/packages: >=linux-headers-2.5
--- Invalid atom in /usr/portage/profiles/default-linux/x86/2005.0/packages: >=xbox-sources-2.5
--- Invalid atom in /usr/portage/profiles/default-linux/x86/2005.0/packages: >=win4lin-sources-2.5
--- Invalid atom in /usr/portage/profiles/default-linux/x86/2005.0/packages: >=vanilla-sources-2.5
--- Invalid atom in /usr/portage/profiles/default-linux/x86/2005.0/packages: >=usermode-sources-2.5
--- Invalid atom in /usr/portage/profiles/default-linux/x86/2005.0/packages: >=uclinux-sources-2.5
--- Invalid atom in /usr/portage/profiles/default-linux/x86/2005.0/packages: >=rsbac-sources-2.5
--- Invalid atom in /usr/portage/profiles/default-linux/x86/2005.0/packages: >=openmosix-sources-2.5
--- Invalid atom in /usr/portage/profiles/default-linux/x86/2005.0/packages: >=hardened-sources-2.5
--- Invalid atom in /usr/portage/profiles/default-linux/x86/2005.0/packages: >=grsec-sources-2.5
--- Invalid atom in /usr/portage/profiles/default-linux/x86/2005.0/packages: >=gentoo-sources-2.5
--- Invalid atom in /usr/portage/profiles/default-linux/x86/2005.0/packages: >=ck-sources-2.5
--- Invalid atom in /usr/portage/profiles/default-linux/x86/2005.0/packages: >=ac-sources-2.5


The file should list >=sys-kernel/packagename instead of >=packagename.

Reproducible: Always
Steps to Reproduce:
1. Upgrade your profile to 2005.0
2. Try to use emerge: emerge info, emerge sync
3.

Actual Results:  
emerge complains about "invalid atoms"

Expected Results:  
should not complain

emerge info output:

Portage 2.0.51-r8 (default-linux/x86/2005.0, gcc-3.4.3, glibc-2.3.4.20041102-r0,
2.6.9-gentoo-r9 i686)
=================================================================
System uname: 2.6.9-gentoo-r9 i686 Intel(R) Pentium(R) M processor 1500MHz
Gentoo Base System version 1.6.7
Python:              dev-lang/python-2.3.4 [2.3.4 (#1, Jun  8 2004, 05:38:36)]
dev-lang/python:     2.3.4
sys-devel/autoconf:  2.59-r6, 2.13
sys-devel/automake:  1.8.5-r2, 1.5, 1.4_p6, 1.6.3, 1.7.9, 1.9.3
sys-devel/binutils:  2.15.92.0.2-r1
sys-devel/libtool:   1.5.2-r7
virtual/os-headers:  2.6.8.1-r1
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-march=pentium-m -O3 -pipe"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3/share/config /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="-march=pentium-m -O3 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms"
GENTOO_MIRRORS="http://gentoo.mirrors.pair.com http://gentoo.oregonstate.edu
http://www.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.us.gentoo.org/gentoo-portage"
USE="X Xaw3d a52 aac aalib acpi acpi4linux alsa async audiofile avi berkdb
bitmap-fonts bonobo cddb cdr cdrom codecs crypt cups curl dga directfb dv dvd
dvdread encode f77 faac faad fam fame fbcon fftw flac font-server foomaticdb
fortran freetype ftp gb gd gdbm gif gimp gimpprint ginac gmail gmp gmtfull
gmthigh gmtsuppl gmttria gnome gnomedb gphoto2 gpm gsl gstreamer gtk gtk2
gtkhtml guile hal i8x0 imagemagick imap imlib imlib2 java javascript jpeg
kerberos krb4 lcms ldap libcaca libg++ libgda libwww live lzo mad mbox mdb
mikmod mime mjpeg motif moznocompose moznoirc moznomail mozsvg mp3 mpeg mpeg4
mplayer msn ncurses netcdf network nogcj noplugin numarray offensive oggvorbis
opengl oss pam pcap pcmcia pdflib perl plotutils png pnp portaudio posix ppds
python quicktime radeon rage128 readline real rplay rtc samba sasl sdk sdl snmp
sox speex spell sse sse2 ssl stroke svg svga sysvipc tcltk tcpd tetex tga theora
tiff transcode truetype truetype-fonts trusted unicode usb uudeview v4l v4l2
vcdimager vim-with-x wmf wxwin wxwindows x86 xine xml xml2 xmms xosd xpm xrandr
xv xvid xvmc yahoo yv12 zlib"
Comment 1 Chris Gianelloni (RETIRED) gentoo-dev 2004-12-10 04:42:28 UTC
GO BACK TO 2004.3 OR FACE THE WRATH OF THE GODS!!!

I really have no desire to work with this, since you are using a profile that will not only change *constantly* between now and 2005.0, but one that is known not to work due to still being in development.

Quit trying to be so damn bleeding edge.  You know that 2004.3 is the current stable profile.  What even gave you the idea that 2005.0 would work?  At the time I commited that, it was simply to give dsd an idea of what it would be like and for him to verify that I had all of the proper packages for our eventual kernel moves.  It is known to be wrong.  I hav efixed it now, just so I don't get any more of these "bugs" reported.

Unfortunately, there is no way for us to mark a profile as "unstable" or anything.  I guess I just need to mark it deprecated.

Anyway... the solution is for you to quit using this profile.
Comment 2 Alok Singhal 2004-12-10 07:05:33 UTC
Oops, sorry.  I don't know what I was thinking when I did that "upgrade".  Have gone to 2004.3 now.

Thanks,
Alok