Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 18987 - all emerge log files are empty
Summary: all emerge log files are empty
Status: RESOLVED FIXED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Unclassified (show other bugs)
Hardware: All Linux
: High major (vote)
Assignee: Nicholas Jones (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-04-08 13:32 UTC by Axxackall
Modified: 2011-10-30 22:22 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 Axxackall 2003-04-08 13:32:02 UTC
after upgradiging Portage to 2.0.47-r10 the logging functionality is broken:
after every emerge I can see new files appearing in /var/log/emerge, but all are
empty (zero file length). 

Before 2.0.47-r10 al logging was functioning fine.

Reproducible: Always
Steps to Reproduce:
Comment 1 Martin Holzer (RETIRED) gentoo-dev 2003-04-08 13:38:44 UTC
could you please try -r13 and see if it's fixed
Comment 2 Axxackall 2003-04-08 22:30:30 UTC
yes, upgrade portage to 2.0.47-r13 has fixed the log problem.

Now I am eager to see -r13 unmasked :)
Comment 3 Axxackall 2003-04-09 16:33:30 UTC
I've just dobe "emerge rsync" on the other box and found that all portage revisions but r10 and r16 are disaapered. Well, I'll upgraded portage to r16 on that box and then did etc-update as advised. 

It works strange with log files, solving only problem on installation files, leaving the emty-log problem unsolved on uninstallation: 

  -rw-rw-r--    1 root     portage         0 Apr  9 16:28 1058-gzip-1.3.3.log 
  -rw-rw-r--    1 root     portage     13516 Apr  9 16:28 1057-gzip-1.3.3-r1.log 
  -rw-rw-r--    1 root     portage         0 Apr  9 16:25 1057-less-378-r2.log 
  -rw-rw-r--    1 root     portage      8933 Apr  9 16:25 1056-less-381.log 


Comment 4 Axxackall 2003-04-09 16:34:45 UTC
Speaking about r16, it makes very strange first time (after portage upgrade) running of etc-update.When first time I run etc-update I had to wait 20 minutes or so and I've got very strange output:

Performing Global Updates: /usr/portage/profiles/updates/1Q-2003
!!! Cannot update binary: Destination exists.
!!! sys-apps/bash-2.05b-r3 -> app-shells/bash-2.05b-r3
!!! Cannot update binary: Destination exists.
!!! sys-devel/perl-5.8.0-r9 -> dev-lang/perl-5.8.0-r9
!!! Cannot update binary: Destination exists.
!!! sys-apps/iptables-1.2.7a-r3 -> net-firewall/iptables-1.2.7a-r3
!!! Cannot update binary: Destination exists.
!!! net-wireless/gkrellmwireless-2.0.1 -> x11-plugins/gkrellmwireless-2.0.1
***************************************************************************
***************************************************************************
***************************************************************************
***************************************************************************
***************************************************************************
***************************************************************************
***************************************************************************
***************************************************************************
**************
 /usr/portage/profiles/updates/3Q-2002
***************************************************************************
***************************************************************************
***************************************************************************
***************************************************************************
***************************************************************************
***************************************************************************
***************************************************************************
***************************************************************************
**************
Performing Global Updates:
 /usr/portage/profiles/updates/4Q-2002
@**************************************************************************
***************************************************************************
***************************************************************************
***************************************************************************
***************************************************************************
***************************************************************************
***************************************************************************
***************************************************************************
***************
Scanning Configuration files...
Exiting: No files to work on!
Comment 5 Axxackall 2003-04-09 16:37:08 UTC
One problem with r16: it expects the portage tree to have new digests (Manifest). So, until the tree will be regenerated I have to go back to r10 (as r13 is not in the Portage tree anymore and I don't want to regenerate manually all digests for the whole tree) untill the new-digest log-fixed portage is arrived. 
Comment 6 Axxackall 2003-04-09 20:39:30 UTC
I mean "one *more* problem" with r16 in my last comment. Sorry for typo.
Comment 7 Nicholas Jones (RETIRED) gentoo-dev 2003-04-28 04:18:06 UTC
All fixed for >=48_pre3