Hi, I have announced a bug report no. 29525 which error reason I recognized wrongly. I thought, that the errormessage "COUNTER file is missing for sys-devel/gcc-3.2-r1 in /var/db." was caused by a partition running full - but this was not the case. I proofed, that the contents of /var/db/sys-devel/gcc-3.2-r1 haven't changed since 2 backups that I have made. The only difference that might be the reason for the error message is an update to portage v2.0.49-r5 from v2.0.49-r4 I have done at date 2003-09-22. An update to portage from v2.0.49-r5 to v2.0.49-r6 at date 2003-09-24 still shows that bug. The only content of /var/db/pkg/sys-devel/gcc-3.2-r1 is the file CONTENTS. I have updated gcc-3.2-r1 at date 2003-04-05 to gcc-3.2.2-r2 and the log I have made says that gcc-3.2-r1 was protected for erasing. I will upload the log for your information and the logs for the portage update described above, too. IMHO this must be an error at the new portage v2.0.49-r6 or all prior versions didn't check for this circumstance because the emerge logs of portage show no errors but the emerge of software installed after. I'd appreciate an information, if emerging software is safe at this state my system has or if I should wait for an error fix. Reproducible: Always Steps to Reproduce: 1.Having portage v2.0.49-r5 or portage v2.0.49-r6 installed 2.Emerging any software 3. Actual Results: I have errors described above and at the bug no 29525 Expected Results: Having an error free log which I produce by "emerge <package> 2>&1 > tee -a emerge.<package>.<date> see my "emerge info" at bug no 29525
Created attachment 18544 [details] gzipped tarball of the logs I described at my prior posting FYI
Hi, I encounterd, that env-update is involved with one of the two bugs I have described, but the file the error is about, seems to be ok: ---cut-on--- # env-update >>> Regenerating /etc/ld.so.cache... * Caching service dependencies... awk: cmd. line:1: (FILENAME=/etc/init.d/xfs FNR=290) warning: error writing standard output (Broken pipe) awk: cmd. line:1: (FILENAME=/etc/init.d/xfs~ FNR=290) warning: error writing standard output (Broken pipe) # file /etc/init.d/xfs /etc/init.d/xfs: a /sbin/runscript script text executable # /etc/init.d/xfs status * status: stopped # /etc/init.d/xfs start * Scanning font directories... [ ok ] * Indexing font directories... * /usr/X11R6/lib/X11/fonts/75dpi... [ ok ] * /usr/X11R6/lib/X11/fonts/100dpi... [ ok ] * /usr/X11R6/lib/X11/fonts/misc... [ ok ] * /usr/X11R6/lib/X11/fonts/Type1... [ ok ] * /usr/X11R6/lib/X11/fonts/Speedo... [ ok ] * /usr/X11R6/lib/X11/fonts/util... [ ok ] * /usr/X11R6/lib/X11/fonts/truetype... [ ok ] * /usr/X11R6/lib/X11/fonts/TTF... [ ok ] * /usr/X11R6/lib/X11/fonts/cyrillic... [ ok ] * Updating FC cache... [ ok ] * Starting X Font Server... [ ok ] # /etc/init.d/xfs stop * Stopping X Font Server... [ ok ] ---cut-off--- Maybe this helps to get near the error? Any questions I can answer? regards, Sascha
I have the same problem with COUNTER file: petra root # emerge -p clean >>> These are the packages that I would unmerge: ['dev-lang/perl', '5.8.0', 'r10'] ['dev-lang/perl-5.6.1-r12', 'dev-lang/perl-5.8.0-r10', 'dev-lang/perl-5.8.1_rc2', 'dev-lang/perl-5.8.0-r11', 'dev-lang/perl-5.8.0-r12'] !!! COUNTER file is missing for dev-lang/perl-5.8.0-r10 in /var/db. !!! Please run /usr/lib/portage/bin/fix-db.pl or remerge the package. petra root # /usr/lib/portage/bin/fix-db.pl Grabbing db contents... Grabbing mtimes... Sorting... Writing COUNTERs... Writing /var/cache/edb/counter... Done. petra root # emerge -p clean >>> These are the packages that I would unmerge: ['dev-lang/perl', '5.8.0', 'r10'] ['dev-lang/perl-5.6.1-r12', 'dev-lang/perl-5.8.0-r10', 'dev-lang/perl-5.8.1_rc2', 'dev-lang/perl-5.8.0-r11', 'dev-lang/perl-5.8.0-r12'] !!! COUNTER file is missing for dev-lang/perl-5.8.0-r10 in /var/db. !!! Please run /usr/lib/portage/bin/fix-db.pl or remerge the package. I have also tried re-emerging perl, but I get the same problem.
I fixed this on my system by downgrading to perl-5.8.0.
This shouldn't be any issue any longer... And that script will be fixed. Don't report multiple bugs in one report.
