Re: [gentoo-user] Is perl broken?

[Peter Humphrey]

On Sunday 05 April 2015 21:05:15 Andreas K. Huettel wrote:
 Am Sonntag, 5. April 2015, 19:03:43 schrieb Peter Humphrey:
  On Sunday 05 April 2015 18:29:05 Andreas K. Huettel wrote:
   Do you see anything that is actually broken?
  
  Apart from perl-cleaner and portage? Emerge exiting silently after being
  given a list of packages to emerge doesn't exactly seem like normal
  behaviour to me. It was told emerge -v1 ...[list of packages] as in
  perl- cleaner's usual behaviour. No ifs, no buts - just do it.
 
 Very strange. Portage does to my best knowledge not use perl and not even
 depend on it.

After a bit more thought I remember that GCC was upgraded last week, and the 
change log referred to many bug fixes. (That's what my memory tells me, 
anyway, but I can't see where I found it now.) So I decided to emerge -e 
world, which I did in two passes: first emerge -eB world, then boot to a 
minimal system and emerge -eK world. Then etc-update and reboot, compile the 
kernel again (gentoo-sources-3.18.9) and a final reboot.

Maybe something went wrong in the middle of that, so I've set off the same 
process again. It'll take a few hours, so I'm off to bed again meanwhile - 
it's 04:30 here.

-- 
Rgds
Peter.

Re: [gentoo-user] This nite's switch to full multilib

[Fernando Rodriguez]

On Friday, April 03, 2015 8:52:18 AM Stroller wrote:
 
 On Thu, 2 April 2015, at 4:37 pm, Grant Edwards grant.b.edwa...@gmail.com 
wrote:
  
  I prefer it this way.  I do not want all the nice easy-to read/edit
  configuration stuff in /etc/portage encrypted some Windows Registry
  break-alike.
 
 What's bad about the Windows registry is that its proprietary file format is 
both poorly constructed (or, rather lacking design) and obscure, and its 
reputation was for brittleness was built when it was stored on FAT file systems 
and corrupted when Windows crashed and had to be hard rebooted.

And that it became a central repository for *everything*, it wasn't too bad as 
just a COM registry on Windows 3.11. Microsoft's been pushing developers to 
use config files for years but they themselves keep using the registry poorly. 
Install the latest visual studio, then uninstall it and search your registry. 
You will find over 20,000 registry entries left behind.

 If you want to store a lot of stuff, then databases are a valid solution. If 
there's something wrong with sqlite or BerkeleyDB then argue against them, but 
don't base your objections on a strawman.

I agree that a binary db for portage is a good idea, only because it's 
ridiculous how long it takes portage to resolve dependencies. It could be just 
a cache that gets rebuilt after syncing or updating config files.

-- 
Fernando Rodriguez

Re: [gentoo-user] Is perl broken?

[Peter Humphrey]

On Sunday 05 April 2015 12:24:20 Mick wrote:

---8

 and then portage proceeds in emerging them.  So something must not be
 right with your circumstances, but I am not sure what ...

It has me scratching my head too. Thanks for the report.

-- 
Rgds
Peter.

Re: [gentoo-user] Re: How to poweroff the system from user?

[Rich Freeman]

On Sun, Apr 5, 2015 at 3:27 AM, Dale rdalek1...@gmail.com wrote:
 Neil Bothwick wrote:
 On Sat, 04 Apr 2015 14:41:12 +0200, lee wrote:

 On Linux now there's the Magic SysRq Key feature for that.
 I always can't remember which keys to press with that, so I have it
 disabled.
 BUSIER backwards.

 And when the keyboard is unresponsive, it won't work.
 It usually does. The kernel sees the Magic key events directly, so even
 if your X server has crashed, it will still respond to Alt-SysReq.



 I used that on a few puters.  I don't recall this ever not working.  X
 may not see the keyboard but the kernel does.  It's a life saver at
 times too.  At least you can sync and unmount cleanly.


If you're dealing with a kernel panic of some kind (which you
inevitably are when you are doing this sort of thing), all bets are
off.  I'll agree that usually the magic sysrq works.  However, there
are certainly going to be cases where it doesn't, or at least where
parts of it don't work.  In my case the part that usually fails for me
right now is btrfs, so unmounting won't work anyway (though I guess it
will take care of the ext4 backup partition that is only rarely
touched anyway).

-- 
Rich

Re: [gentoo-user] This nite's switch to full multilib

[Neil Bothwick]

On Sun, 5 Apr 2015 07:21:01 -0400, Rich Freeman wrote:

  It's like being a teenager again, the longer you leave tidying your
  room, the longer it takes when your mum makes you do it :)
   
 
 Don't want to harp on it, but I almost never have to clean my world
 file, and when I do I don't need any tools at all to make it happen.
 This is because the world file revolves around me and my true
 requirements, and not an endless list of hints to try to get the
 package manager to do what I want it to do.

We're talking about /etc/portage/package.* here. not @world. I too rarely
need to touch world.

 I think we need to get away from solutions that clutter up
 configuration in the first place.  I'm not under any illusions that
 this will ever be perfect, but I do think we can do better.

Agreed, but this is about managing the options we have now. Like it or
not, we need to put extra entries in package.use and eix-test-obsolete is
the best current way of removing them when they're no longer needed, as
portage's autounmask facility only adds to the file, it never cleans up
after itself.


-- 
Neil Bothwick

Oxymoron: Reagan memoirs.


pgpFz9I_H24Yh.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] This nite's switch to full multilib

[Rich Freeman]

On Sun, Apr 5, 2015 at 8:09 AM, Neil Bothwick n...@digimed.co.uk wrote:

 Or leave /etc/portage full of cruft and crap and fix any problem it may
 cause later on, when you have even less time ;-)


Hmm, have an hour of free time now, at the cost of maybe having an
hour less of free time a year from now, maybe.  That's a hard choice.
:)

-- 
Rich

Re: [gentoo-user] Is perl broken?

[Mick]

On Sunday 05 Apr 2015 10:50:53 Peter Humphrey wrote:
 Hello list,
 
 Today's routine update included dev-lang/perl-5.20.2 and two perl virtuals.
 Since emerging those portage has stopped working: perl-cleaner gives it a
 list of 71 packages to emerge but portage does nothing with them - it just
 exits silently. Then perl-cleaner lists some hundreds of files that it
 can't do anything with.
 
 What's going on here?
 
 I've restored from last week's backup and added the offending perl packages
 to package.mask, but is that the right thing to do?

This sounds odd.  I emerged virtual/perl-Compress-Raw-Bzip2-2.64.0 yesterday, 
but haven't sync'ed today.  perl-cleaner gives me this:

=
# perl-cleaner --reallyall
 * Removing perl-core packages from world file
 *emerge --deselect  perl-core/Data-Dumper perl-core/File-Temp perl-
core/Module-Build perl-core/libnet 
 No matching atoms found in world favorites file...
 * Updating installed Perl virtuals
 *emerge -u1  virtual/perl-Archive-Tar virtual/perl-CPAN-Meta 
virtual/perl-CPAN-Meta-YAML virtual/perl-Compress-Raw-Bzip2 virtual/perl-
Compress-Raw-Zlib virtual/perl-Data-Dumper virtual/perl-Digest-MD5 
virtual/perl-Digest-SHA virtual/perl-Encode virtual/perl-ExtUtils-CBuilder 
virtual/perl-ExtUtils-Install virtual/perl-ExtUtils-MakeMaker virtual/perl-
ExtUtils-Manifest virtual/perl-ExtUtils-ParseXS virtual/perl-File-Spec 
virtual/perl-File-Temp virtual/perl-Getopt-Long virtual/perl-IO virtual/perl-
IO-Compress virtual/perl-JSON-PP virtual/perl-MIME-Base64 virtual/perl-Module-
Build virtual/perl-Module-Metadata virtual/perl-Parse-CPAN-Meta virtual/perl-
Perl-OSType virtual/perl-Scalar-List-Utils virtual/perl-Storable virtual/perl-
Test-Harness virtual/perl-Test-Simple virtual/perl-Text-ParseWords 
virtual/perl-Time-Local virtual/perl-libnet virtual/perl-version 
Calculating dependencies... done!
 Auto-cleaning packages...

 No outdated packages were found on your system.

 * Beginning a clean up of .ph files
 * Excluding files for 0.0.0 and 0.0.0/x86_64-linux from cleaning

 * Locating ph files for removal

 * Updating ph files.
 * Ignore all No such file... messages!
Can't open machine/ansi.h: No such file or directory
Can't open sys/_types.h: No such file or directory
Can't open gnu/stubs-x32.h: No such file or directory
Can't open gnu/stubs-x32.h: No such file or directory
Can't open gnu/stubs-x32.h: No such file or directory
Can't open gnu/stubs-x32.h: No such file or directory

 * Locating packages for an update
 * Locating ebuilds linked against libperl
 *   Adding to list: perl-core/libnet:0
 *   virtual/perl-libnet:0
 *   Adding to list: perl-core/File-Temp:0
 *   virtual/perl-File-Temp:0
 *   Adding to list: perl-core/Data-Dumper:0
 *   virtual/perl-Data-Dumper:0
 *   Adding to list: perl-core/Module-Build:0
 *   virtual/perl-Module-Build:0
 *   Adding to list: x11-terms/rxvt-unicode:0
 *   Adding to list: dev-vcs/git:0
 *   Adding to list: net-irc/irssi:0
 *   Adding to list: dev-perl/HTML-Parser:0
 *   Adding to list: dev-perl/File-BaseDir:0
 *   Adding to list: dev-perl/IO-Socket-SSL:0
 *   Adding to list: dev-perl/XML-LibXML:0
 *   Adding to list: dev-perl/File-Listing:0
 *   Adding to list: dev-perl/Encode-Locale:0
 *   Adding to list: dev-perl/File-MimeInfo:0
 *   Adding to list: dev-perl/XML-SAX:0
 *   Adding to list: dev-perl/DateManip:0
 *   Adding to list: dev-perl/HTTP-Negotiate:0
 *   Adding to list: dev-perl/XML-SAX-Base:0
 *   Adding to list: dev-perl/WWW-RobotRules:0
 *   Adding to list: dev-perl/Archive-Zip:0
 *   Adding to list: dev-perl/Locale-gettext:0
 *   Adding to list: dev-perl/File-DesktopEntry:0
 *   Adding to list: dev-perl/URI:0
 *   Adding to list: dev-perl/libwww-perl:0
 *   Adding to list: dev-perl/HTTP-Daemon:0
 *   Adding to list: dev-perl/Net-HTTP:0
 *   Adding to list: dev-perl/Error:0
 *   Adding to list: dev-perl/XML-Parser:0
 *   Adding to list: dev-perl/Net-SMTP-SSL:0
 *   Adding to list: dev-perl/Authen-SASL:0
 *   Adding to list: dev-perl/LWP-Protocol-https:0
 *   Adding to list: dev-perl/XML-NamespaceSupport:0
 *   Adding to list: dev-perl/HTML-Tagset:0
 *   Adding to list: dev-perl/LWP-MediaTypes:0
 *   Adding to list: dev-perl/Net-SSLeay:0
 *   Adding to list: dev-perl/Digest-HMAC:0
 *   Adding to list: dev-perl/HTTP-Message:0
 *   Adding to list: dev-perl/JSON:0
 *   Adding to list: dev-perl/XML-Simple:0
 *   Adding to list: dev-perl/HTTP-Cookies:0
 *   Adding to list: dev-perl/HTTP-Date:0
 *   Adding to list: media-libs/exiftool:0
 * emerge -v1 --backtrack=100 perl-core/libnet:0 virtual/perl-libnet:0 perl-
core/File-Temp:0 virtual/perl-File-Temp:0 perl-core/Data-Dumper:0 
virtual/perl-Data-Dumper:0 perl-core/Module-Build:0 virtual/perl-Module-
Build:0 x11-terms/rxvt-unicode:0 dev-vcs/git:0 net-irc/irssi:0 dev-perl/HTML-
Parser:0 dev-perl/File-BaseDir:0 dev-perl/IO-Socket-SSL:0 dev-perl/XML-

Re: [gentoo-user] Is perl broken?

[Alan McKinnon]

On 05/04/2015 11:50, Peter Humphrey wrote:
 Hello list,
 
 Today's routine update included dev-lang/perl-5.20.2 and two perl virtuals. 
 Since emerging those portage has stopped working: perl-cleaner gives it a 
 list of 71 packages to emerge but portage does nothing with them - it just 
 exits silently. Then perl-cleaner lists some hundreds of files that it can't 
 do anything with.
 
 What's going on here?
 
 I've restored from last week's backup and added the offending perl packages 
 to package.mask, but is that the right thing to do?
 


When I occasionally run into bizarre weirdness like this, I usually wait
one hor, re-sync and try again. If it still fails, then go looking further.

Significant updates to the CVS tree are not atomic and every now and
then you can do a sync while a dev is making his own updates. Especially
in the light that it all works fine for Mick.

If you use a third party tree mirror, you can also update against the
master at rsync.gentoo.org to get the very latest tree.

-- 
Alan McKinnon
alan.mckin...@gmail.com

Re: [gentoo-user] portage summary logs not rotated any more

[Alexander Kapshuk]

On Sun, Apr 5, 2015 at 10:50 AM, Mick michaelkintz...@gmail.com wrote:

 On Sunday 05 Apr 2015 06:39:31 Alexander Kapshuk wrote:
  On Sun, Apr 5, 2015 at 1:18 AM, Mick michaelkintz...@gmail.com wrote:
   On Saturday 04 Apr 2015 20:35:31 Alexander Kapshuk wrote:
My portage summary logs don't seem to be rotated any more.
   
ls -lt `pwd`/summary.log*
-rw-rw-r-- 1 portage portage 96581 Apr  3 19:47
/var/log/portage/elog/summary.log
-rw-rw-r-- 1 portage portage  5927 Jan 10 07:50
/var/log/portage/elog/summary.log-20150112
-rw-rw-r-- 1 portage portage  2281 Jan  4 21:14
/var/log/portage/elog/summary.log-20150104.gz
-rw-rw-r-- 1 portage portage   565 Dec 26 20:53
/var/log/portage/elog/summary.log-20141228.gz
-rw-rw-r-- 1 portage portage  1842 Dec 22 17:52
/var/log/portage/elog/summary.log-20141222.gz
   
grep Messages summary.log | sed '1h;$!d;x;G;q'
   
 Messages generated by process 3399 on 2015-01-13 17:47:47 EET for
   
package dev-python/reportlab-3.1.8-r2:
 Messages generated by process 4080 on 2015-04-03 19:47:54 EEST
 for
   
package net-print/hplip-3.14.1:
   
grep Messages summary.log-20150112 | sed '1h;$!d;x;G;q'
   
 Messages generated by process 2637 on 2015-01-04 22:02:00 EET for
   
package app-office/libreoffice-4.2.8.2:
 Messages generated by process 3483 on 2015-01-10 07:50:04 EET for
   
package dev-libs/openssl-1.0.1k:
   
cat /etc/logrotate.d/elog-save-summary
# Copyright 1999-2011 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# Rotate the log created by the save_summary elog module.
   
/var/log/portage/elog/summary.log {
   
su portage portage
missingok
nocreate
delaycompress
   
}
   
/etc/logrotate.conf:6,8
# rotate log files weekly.
weekly
#daily
   
What could be wrong here? Or am I misreading something?
   
Thanks.
  
   Is your logrotate running regularly as expected?  What do you get when
  
   from:
grep logrotate /var/log/cron.log
  
   --
   Regards,
   Mick
 
  Thanks for your response.
 
  I'm afraid I don't have the cron logging set up. I should probably go
 ahead
  and do it, shouldn't I?
 
  grep logrotate /var/log/cron.log
  grep: /var/log/cron.log: No such file or directory
 
  The cron daemon is running though.
 
  ps auxwww|grep '[c]ron'
  root  2418  0.0  0.1   5464  1868 ?Ss   08:33   0:00
  /usr/sbin/crond
 
  Thanks.

 Ah! I must have set this up myself.  In /etc/syslog-ng/syslog-ng.conf I
 have
 among other settings:

 destination cron { file(/var/log/cron.log); };
 filter f_cron { facility(cron); };
 log { source(src); filter(f_cron); destination(cron); };

 This is not necessary though.  You can search /var/log/messages for
 logrotate.

 --
 Regards,
 Mick



Understood. Thanks.

Messages doesn't seem to have anything out of the ordinary to say about
logrotate though.
sed '/logrotate/!d' /var/log/messages
Jan 13 17:50:02 localhost run-crons[7443]: (root) CMD
(/etc/cron.daily/logrotate)
Jan 14 18:00:02 localhost run-crons[4576]: (root) CMD
(/etc/cron.daily/logrotate)
Jan 15 18:10:02 localhost run-crons[1692]: (root) CMD
(/etc/cron.daily/logrotate)
Jan 16 18:20:01 localhost run-crons[4448]: (root) CMD
(/etc/cron.daily/logrotate)

An observation I've made, is that my log rotation seems to have effected
all other logs in /var/log as well. It seems to have stopped working around
January this year.

ls -lt /var/log/messages*
-rw--- 1 root root 9986127 Apr  5 16:10 /var/log/messages
-rw--- 1 root root  173843 Jan 12 10:20 /var/log/messages-20150112.gz
-rw--- 1 root root  277867 Jan  4 22:00 /var/log/messages-20150104.gz
-rw--- 1 root root  132157 Dec 28 20:30 /var/log/messages-20141228.gz
-rw--- 1 root root  142911 Dec 22 19:30 /var/log/messages-20141222.gz

sed '1h;$!d;x;G;q' /var/log/messages
Jan 12 10:20:02 localhost syslog-ng[2321]: Configuration reload request
received, reloading configuration;
Apr  5 16:10:01 box1 CROND[2265]: pam_unix(crond:session): session closed
for user root

ls -lt /var/log/|sort -k9
total 16064
drwxr-xr-x 2 rootroot   4096 Feb 15 00:42 ConsoleKit
-rw-r--r-- 1 rootsasha 33914 Apr  5 08:34 Xorg.0.log
-rw-r--r-- 1 rootsasha 34515 Apr  4 23:17 Xorg.0.log.old
-rw-r--r-- 1 rootsasha 28290 Sep 22  2014 Xorg.1.log
drwxr-xr-x 2 rootroot   4096 Jan 12 10:20 chrony
drwxr-xr-x 2 rootroot   4096 Feb  7 12:26 cups
-rw-r- 1 rootroot  50378 Apr  5 08:33 dmesg
-rw-rw 1 portage portage6268 Apr  1 19:35 emerge-fetch.log
-rw-rw 1 portage portage 2687784 Apr  5 09:04 emerge.log
-rw-r--r-- 1 rootroot 292292 Apr  5 08:34 lastlog
-rw--- 1 rootroot9986127 Apr  5 16:10 messages
-rw--- 1 rootroot 142911 Dec 22 19:30 messages-20141222.gz
-rw--- 1 rootroot 132157 Dec 28 20:30 messages-20141228.gz
-rw--- 1 root

Re: [gentoo-user] portage summary logs not rotated any more

[Mick]

On Sunday 05 Apr 2015 14:19:16 Alexander Kapshuk wrote:
 On Sun, Apr 5, 2015 at 10:50 AM, Mick michaelkintz...@gmail.com wrote:
  On Sunday 05 Apr 2015 06:39:31 Alexander Kapshuk wrote:
   On Sun, Apr 5, 2015 at 1:18 AM, Mick michaelkintz...@gmail.com wrote:
On Saturday 04 Apr 2015 20:35:31 Alexander Kapshuk wrote:
 My portage summary logs don't seem to be rotated any more.
 
 ls -lt `pwd`/summary.log*
 -rw-rw-r-- 1 portage portage 96581 Apr  3 19:47
 /var/log/portage/elog/summary.log
 -rw-rw-r-- 1 portage portage  5927 Jan 10 07:50
 /var/log/portage/elog/summary.log-20150112
 -rw-rw-r-- 1 portage portage  2281 Jan  4 21:14
 /var/log/portage/elog/summary.log-20150104.gz
 -rw-rw-r-- 1 portage portage   565 Dec 26 20:53
 /var/log/portage/elog/summary.log-20141228.gz
 -rw-rw-r-- 1 portage portage  1842 Dec 22 17:52
 /var/log/portage/elog/summary.log-20141222.gz
 
 grep Messages summary.log | sed '1h;$!d;x;G;q'
 
  Messages generated by process 3399 on 2015-01-13 17:47:47 EET
  for
 
 package dev-python/reportlab-3.1.8-r2:
  Messages generated by process 4080 on 2015-04-03 19:47:54 EEST
  
  for
  
 package net-print/hplip-3.14.1:
 
 grep Messages summary.log-20150112 | sed '1h;$!d;x;G;q'
 
  Messages generated by process 2637 on 2015-01-04 22:02:00 EET
  for
 
 package app-office/libreoffice-4.2.8.2:
  Messages generated by process 3483 on 2015-01-10 07:50:04 EET
  for
 
 package dev-libs/openssl-1.0.1k:
 
 cat /etc/logrotate.d/elog-save-summary
 # Copyright 1999-2011 Gentoo Foundation
 # Distributed under the terms of the GNU General Public License v2
 # Rotate the log created by the save_summary elog module.
 
 /var/log/portage/elog/summary.log {
 
 su portage portage
 missingok
 nocreate
 delaycompress
 
 }
 
 /etc/logrotate.conf:6,8
 # rotate log files weekly.
 weekly
 #daily
 
 What could be wrong here? Or am I misreading something?
 
 Thanks.

Is your logrotate running regularly as expected?  What do you get
when

from:
 grep logrotate /var/log/cron.log

--
Regards,
Mick
   
   Thanks for your response.
   
   I'm afraid I don't have the cron logging set up. I should probably go
  
  ahead
  
   and do it, shouldn't I?
   
   grep logrotate /var/log/cron.log
   grep: /var/log/cron.log: No such file or directory
   
   The cron daemon is running though.
   
   ps auxwww|grep '[c]ron'
   root  2418  0.0  0.1   5464  1868 ?Ss   08:33   0:00
   /usr/sbin/crond
   
   Thanks.
  
  Ah! I must have set this up myself.  In /etc/syslog-ng/syslog-ng.conf I
  have
  among other settings:
  
  destination cron { file(/var/log/cron.log); };
  filter f_cron { facility(cron); };
  log { source(src); filter(f_cron); destination(cron); };
  
  This is not necessary though.  You can search /var/log/messages for
  logrotate.
  
  --
  Regards,
  Mick
 
 Understood. Thanks.
 
 Messages doesn't seem to have anything out of the ordinary to say about
 logrotate though.
 sed '/logrotate/!d' /var/log/messages
 Jan 13 17:50:02 localhost run-crons[7443]: (root) CMD
 (/etc/cron.daily/logrotate)
 Jan 14 18:00:02 localhost run-crons[4576]: (root) CMD
 (/etc/cron.daily/logrotate)
 Jan 15 18:10:02 localhost run-crons[1692]: (root) CMD
 (/etc/cron.daily/logrotate)
 Jan 16 18:20:01 localhost run-crons[4448]: (root) CMD
 (/etc/cron.daily/logrotate)
 
 An observation I've made, is that my log rotation seems to have effected
 all other logs in /var/log as well. It seems to have stopped working around
 January this year.
 
 ls -lt /var/log/messages*
 -rw--- 1 root root 9986127 Apr  5 16:10 /var/log/messages
 -rw--- 1 root root  173843 Jan 12 10:20 /var/log/messages-20150112.gz
 -rw--- 1 root root  277867 Jan  4 22:00 /var/log/messages-20150104.gz
 -rw--- 1 root root  132157 Dec 28 20:30 /var/log/messages-20141228.gz
 -rw--- 1 root root  142911 Dec 22 19:30 /var/log/messages-20141222.gz
 
 sed '1h;$!d;x;G;q' /var/log/messages
 Jan 12 10:20:02 localhost syslog-ng[2321]: Configuration reload request
 received, reloading configuration;
 Apr  5 16:10:01 box1 CROND[2265]: pam_unix(crond:session): session closed
 for user root
 
 ls -lt /var/log/|sort -k9
 total 16064
 drwxr-xr-x 2 rootroot   4096 Feb 15 00:42 ConsoleKit
 -rw-r--r-- 1 rootsasha 33914 Apr  5 08:34 Xorg.0.log
 -rw-r--r-- 1 rootsasha 34515 Apr  4 23:17 Xorg.0.log.old
 -rw-r--r-- 1 rootsasha 28290 Sep 22  2014 Xorg.1.log
 drwxr-xr-x 2 rootroot   4096 Jan 12 10:20 chrony
 drwxr-xr-x 2 rootroot   4096 Feb  7 12:26 cups
 -rw-r- 1 rootroot  50378 Apr  5 08:33 dmesg
 -rw-rw 1 portage portage6268 Apr  1 19:35 emerge-fetch.log
 -rw-rw 1 portage portage 2687784 Apr  5 09:04 emerge.log
 -rw-r--r-- 1 rootroot 

Re: [gentoo-user] Re: How to poweroff the system from user?

[Dale]

Rich Freeman wrote:
 On Sun, Apr 5, 2015 at 3:27 AM, Dale rdalek1...@gmail.com wrote:
 Neil Bothwick wrote:
 On Sat, 04 Apr 2015 14:41:12 +0200, lee wrote:

 On Linux now there's the Magic SysRq Key feature for that.
 I always can't remember which keys to press with that, so I have it
 disabled.
 BUSIER backwards.

 And when the keyboard is unresponsive, it won't work.
 It usually does. The kernel sees the Magic key events directly, so even
 if your X server has crashed, it will still respond to Alt-SysReq.


 I used that on a few puters.  I don't recall this ever not working.  X
 may not see the keyboard but the kernel does.  It's a life saver at
 times too.  At least you can sync and unmount cleanly.

 If you're dealing with a kernel panic of some kind (which you
 inevitably are when you are doing this sort of thing), all bets are
 off.  I'll agree that usually the magic sysrq works.  However, there
 are certainly going to be cases where it doesn't, or at least where
 parts of it don't work.  In my case the part that usually fails for me
 right now is btrfs, so unmounting won't work anyway (though I guess it
 will take care of the ext4 backup partition that is only rarely
 touched anyway).



That is true but it seems to work most of the time for the usual
failures.  Ask some old timers on this list, hitting reset or having to
pull the plug from the wall really gets on my nerve, every single one of
them and in a hurry.  Dare I think about hal and what a mess it caused
for me. 

Dale

:-)  :-) 

Re: [gentoo-user] This nite's switch to full multilib

[Rich Freeman]

On Sun, Apr 5, 2015 at 5:07 AM, Neil Bothwick n...@digimed.co.uk wrote:
 It's like being a teenager again, the longer you leave tidying your room,
 the longer it takes when your mum makes you do it :)


Don't want to harp on it, but I almost never have to clean my world
file, and when I do I don't need any tools at all to make it happen.
This is because the world file revolves around me and my true
requirements, and not an endless list of hints to try to get the
package manager to do what I want it to do.

I think we need to get away from solutions that clutter up
configuration in the first place.  I'm not under any illusions that
this will ever be perfect, but I do think we can do better.

-- 
Rich

Re: [gentoo-user] This nite's switch to full multilib

[Neil Bothwick]

On Sun, 05 Apr 2015 04:41:33 -0500, Dale wrote:

  I got into that situation once, you just need to bite the bullet and
  work through the output. It's not as bad as it looks as the same
  entry can cause multiple reports, so once you clean up a couple of
  entries the output can get significantly shorter.
 
  It's like being a teenager again, the longer you leave tidying your
  room, the longer it takes when your mum makes you do it :)
 
   
 
 Well, just for giggles I ran it.  Ain't no way I got time to go through
 all that right now.  Heck, it took several minutes for it to just to go
 through all that stuff.  O_O 

Then don't. Just clean up the output from one of the tests, the one with
the shortest output if you prefer.

Or leave /etc/portage full of cruft and crap and fix any problem it may
cause later on, when you have even less time ;-)


-- 
Neil Bothwick

Secret hacker rule #11: hackers read manuals.


pgpHBFazrP12V.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] This nite's switch to full multilib

[Neil Bothwick]

On 5 April 2015 14:27:27 BST, Rich Freeman ri...@gentoo.org wrote:
 On Sun, Apr 5, 2015 at 8:09 AM, Neil Bothwick n...@digimed.co.uk
 wrote:
 
  Or leave /etc/portage full of cruft and crap and fix any problem it
 may
  cause later on, when you have even less time ;-)
 
 
 Hmm, have an hour of free time now, at the cost of maybe having an
 hour less of free time a year from now, maybe.  That's a hard choice.
 :)
 
 -- 
 Rich

Give up 20 minutes when I can afford it or maybe lose a couple of hours and my 
remaining hair if it goes tits up later,  that's an interesting gamble :) 
-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

Re: [gentoo-user] Re: How to poweroff the system from user?

[Dale]

Neil Bothwick wrote:
 On Sat, 04 Apr 2015 14:41:12 +0200, lee wrote:

 On Linux now there's the Magic SysRq Key feature for that.  
 I always can't remember which keys to press with that, so I have it
 disabled.
 BUSIER backwards.

 And when the keyboard is unresponsive, it won't work.
 It usually does. The kernel sees the Magic key events directly, so even
 if your X server has crashed, it will still respond to Alt-SysReq.



I used that on a few puters.  I don't recall this ever not working.  X
may not see the keyboard but the kernel does.  It's a life saver at
times too.  At least you can sync and unmount cleanly. 

Dale

:-)  :-) 

Re: [gentoo-user] This nite's switch to full multilib

[Neil Bothwick]

On Sun, 05 Apr 2015 02:24:13 -0500, Dale wrote:

  It seems you can't win with that thing.  LOL   
  You can win, by running it reasonably often and actually doing
  something about the output. Ignore a few lines and they soon become a
  few more, and then a few more still...

 Thing is, it seems to grow faster than I can clean up.  I'm scared to
 even run it now.  It would likely take me a week to get a clean output. 
 ROFL  It's been a long time since I ran it.  I may be better off to move
 the files, see what emerge wants to change and add stuff back.  Just
 saying. 

I got into that situation once, you just need to bite the bullet and work
through the output. It's not as bad as it looks as the same entry can
cause multiple reports, so once you clean up a couple of entries the
output can get significantly shorter.

It's like being a teenager again, the longer you leave tidying your room,
the longer it takes when your mum makes you do it :)


-- 
Neil Bothwick

Member, National Association For Tagline Assimilators (NAFTA)


pgpiLLVguGyOj.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] This nite's switch to full multilib

[Dale]

Neil Bothwick wrote:
 On Sat, 04 Apr 2015 07:33:06 -0500, Dale wrote:

 eix-test-obsolete   
 Many thanks, it certainly seems to.

 It seems to do a bit more besides, unruly in its verboseness, but I
 won't bother trying to interpret the rest of its output.
 It's one reason I don't use it much.  It spits out so much, it's about
 overwhelming.  Then again, it is usually pointing out the stuff that is
 no longer needed in some file somewhere.  Also, the longer you wait
 between runs, the more it spits out. 

 It seems you can't win with that thing.  LOL 
 You can win, by running it reasonably often and actually doing something
 about the output. Ignore a few lines and they soon become a few more, and
 then a few more still...



Thing is, it seems to grow faster than I can clean up.  I'm scared to
even run it now.  It would likely take me a week to get a clean output. 
ROFL  It's been a long time since I ran it.  I may be better off to move
the files, see what emerge wants to change and add stuff back.  Just
saying. 

One thing tho, having fewer stuff in those files may speed emerge up
just a tiny amount.  ;-) 

Dale

:-)  :-)

Re: [gentoo-user] portage summary logs not rotated any more

[Mick]

On Sunday 05 Apr 2015 06:39:31 Alexander Kapshuk wrote:
 On Sun, Apr 5, 2015 at 1:18 AM, Mick michaelkintz...@gmail.com wrote:
  On Saturday 04 Apr 2015 20:35:31 Alexander Kapshuk wrote:
   My portage summary logs don't seem to be rotated any more.
   
   ls -lt `pwd`/summary.log*
   -rw-rw-r-- 1 portage portage 96581 Apr  3 19:47
   /var/log/portage/elog/summary.log
   -rw-rw-r-- 1 portage portage  5927 Jan 10 07:50
   /var/log/portage/elog/summary.log-20150112
   -rw-rw-r-- 1 portage portage  2281 Jan  4 21:14
   /var/log/portage/elog/summary.log-20150104.gz
   -rw-rw-r-- 1 portage portage   565 Dec 26 20:53
   /var/log/portage/elog/summary.log-20141228.gz
   -rw-rw-r-- 1 portage portage  1842 Dec 22 17:52
   /var/log/portage/elog/summary.log-20141222.gz
   
   grep Messages summary.log | sed '1h;$!d;x;G;q'
   
Messages generated by process 3399 on 2015-01-13 17:47:47 EET for
   
   package dev-python/reportlab-3.1.8-r2:
Messages generated by process 4080 on 2015-04-03 19:47:54 EEST for
   
   package net-print/hplip-3.14.1:
   
   grep Messages summary.log-20150112 | sed '1h;$!d;x;G;q'
   
Messages generated by process 2637 on 2015-01-04 22:02:00 EET for
   
   package app-office/libreoffice-4.2.8.2:
Messages generated by process 3483 on 2015-01-10 07:50:04 EET for
   
   package dev-libs/openssl-1.0.1k:
   
   cat /etc/logrotate.d/elog-save-summary
   # Copyright 1999-2011 Gentoo Foundation
   # Distributed under the terms of the GNU General Public License v2
   # Rotate the log created by the save_summary elog module.
   
   /var/log/portage/elog/summary.log {
   
   su portage portage
   missingok
   nocreate
   delaycompress
   
   }
   
   /etc/logrotate.conf:6,8
   # rotate log files weekly.
   weekly
   #daily
   
   What could be wrong here? Or am I misreading something?
   
   Thanks.
  
  Is your logrotate running regularly as expected?  What do you get when
  
  from:
   grep logrotate /var/log/cron.log
  
  --
  Regards,
  Mick
 
 Thanks for your response.
 
 I'm afraid I don't have the cron logging set up. I should probably go ahead
 and do it, shouldn't I?
 
 grep logrotate /var/log/cron.log
 grep: /var/log/cron.log: No such file or directory
 
 The cron daemon is running though.
 
 ps auxwww|grep '[c]ron'
 root  2418  0.0  0.1   5464  1868 ?Ss   08:33   0:00
 /usr/sbin/crond
 
 Thanks.

Ah! I must have set this up myself.  In /etc/syslog-ng/syslog-ng.conf I have 
among other settings:

destination cron { file(/var/log/cron.log); };
filter f_cron { facility(cron); };
log { source(src); filter(f_cron); destination(cron); };

This is not necessary though.  You can search /var/log/messages for logrotate.

-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.

Re: [OT] Re: [gentoo-user] Question of quantum computer

[Neil Bothwick]

On Sun, 5 Apr 2015 00:52:30 -0400, Boricua Siempre wrote:

 Geentoo power first quantum super computer in 2101 and power all
 galactic cofederation computers.
 It was first supercomputer to crack secret of time travel in 2307 and
 become self conchious in 2402.

Add this to /usr/portage/profile/packahe.mask now!

# Masked due to megalomaniacal bugs
app-misc/skynet


-- 
Neil Bothwick

Favorite Windoze game: Guess what this icon does?


pgpZniiVnmyKn.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] This nite's switch to full multilib

[Dale]

Neil Bothwick wrote:
 On Sun, 05 Apr 2015 02:24:13 -0500, Dale wrote:

 It seems you can't win with that thing.  LOL   
 You can win, by running it reasonably often and actually doing
 something about the output. Ignore a few lines and they soon become a
 few more, and then a few more still...
 Thing is, it seems to grow faster than I can clean up.  I'm scared to
 even run it now.  It would likely take me a week to get a clean output. 
 ROFL  It's been a long time since I ran it.  I may be better off to move
 the files, see what emerge wants to change and add stuff back.  Just
 saying. 
 I got into that situation once, you just need to bite the bullet and work
 through the output. It's not as bad as it looks as the same entry can
 cause multiple reports, so once you clean up a couple of entries the
 output can get significantly shorter.

 It's like being a teenager again, the longer you leave tidying your room,
 the longer it takes when your mum makes you do it :)



Well, just for giggles I ran it.  Ain't no way I got time to go through
all that right now.  Heck, it took several minutes for it to just to go
through all that stuff.  O_O 

Maybe one day.  Maybe. 

Dale

:-)  :-) 

[gentoo-user] Is perl broken?

[Peter Humphrey]

Hello list,

Today's routine update included dev-lang/perl-5.20.2 and two perl virtuals. 
Since emerging those portage has stopped working: perl-cleaner gives it a 
list of 71 packages to emerge but portage does nothing with them - it just 
exits silently. Then perl-cleaner lists some hundreds of files that it can't 
do anything with.

What's going on here?

I've restored from last week's backup and added the offending perl packages 
to package.mask, but is that the right thing to do?

-- 
Rgds
Peter.

Re: [gentoo-user] portage summary logs not rotated any more

[Mick]

On Sunday 05 Apr 2015 16:31:43 Alexander Kapshuk wrote:

 I guess I have to figure out what the error message shown below is all
 about:
 501 Not authorised --- Reply not authenticated

This is most likely chrony:

http://www.gossamer-threads.com/lists/gentoo/user/289231

If logrotate works as expected when run manually, the question remains why 
cronjobs don't run more regularly.

-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] portage summary logs not rotated any more

[Alexander Kapshuk]

On Sun, Apr 5, 2015 at 7:49 PM, Alex Corkwell i.am.the.mem...@gmail.com
wrote:

 On Sun, Apr 05, 2015 at 06:31:43PM +0300, Alexander Kapshuk wrote:
  On Sun, Apr 5, 2015 at 5:36 PM, Mick michaelkintz...@gmail.com wrote:
 
  On Sunday 05 Apr 2015 14:19:16 Alexander Kapshuk wrote:
   On Sun, Apr 5, 2015 at 10:50 AM, Mick michaelkintz...@gmail.com
 wrote:
   An observation I've made, is that my log rotation seems to have
 effected
   all other logs in /var/log as well. It seems to have stopped
 working
  around
   January this year.
  
   ls -lt /var/log/messages*
   -rw--- 1 root root 9986127 Apr  5 16:10 /var/log/messages
   -rw--- 1 root root  173843 Jan 12 10:20
 /var/log/messages-20150112.gz
   -rw--- 1 root root  277867 Jan  4 22:00
 /var/log/messages-20150104.gz
   -rw--- 1 root root  132157 Dec 28 20:30
 /var/log/messages-20141228.gz
   -rw--- 1 root root  142911 Dec 22 19:30
 /var/log/messages-20141222.gz
 
  It seems to me that logrotate stopped rotating your logs back in
 Jan.  Did
  you
  change something in its configuration back then?
 
  This is what I have in /etc/cron.daily/logrotate:
  
  #!/bin/sh
 
  /usr/sbin/logrotate /etc/logrotate.conf
  EXITVALUE=$?
  if [ $EXITVALUE != 0 ]; then
  /usr/bin/logger -t logrotate ALERT exited abnormally with
 [$EXITVALUE]
  
  fi
  exit 0
  =
  I then went ahead and ran logrotate by hand, which resulted in the
 following
  output:
 
  /usr/sbin/logrotate /etc/logrotate.conf
  501 Not authorised --- Reply not authenticated
  501 Not authorised --- Reply not authenticated
  # echo $?
  0
 
  I guess I have to figure out what the error message shown below is all
 about:
  501 Not authorised --- Reply not authenticated
 
 

 I don't know about the 501 Not authorised, but I remember having a
 similar issue with logrotate not running beginning around the same time
 (the last rotated log was the week of 20141221). I can't remember
 exactly what I did, but I believe around then Gentoo (and my system)
 switched from vixie-cron to cronie as default. If I remember correctly,
 it was anacron that caused the problem.

 Take a look at these lines from the default (at least, on my system) for
 /etc/crontab:

 # check scripts in cron.hourly, cron.daily, cron.weekly and cron.monthly
 # if anacron is not present
 59  *  * * *root[ ! -x /etc/cron.hourly/0anacron ]  rm -f
 /var/spool/cron/lastrun/cron.hourly
 9  3  * * * root[ ! -x /etc/cron.hourly/0anacron ]  rm -f
 /var/spool/cron/lastrun/cron.daily
 19 4  * * 6 root[ ! -x /etc/cron.hourly/0anacron ]  rm -f
 /var/spool/cron/lastrun/cron.weekly
 29 5  1 * * root[ ! -x /etc/cron.hourly/0anacron ]  rm -f
 /var/spool/cron/lastrun/cron.monthly
 */10  *  * * *  root[ ! -x /etc/cron.hourly/0anacron ]  { test -x
 /usr/sbin/run-crons  /usr/sbin/run-crons ; }

 Essentially, cron.{hourly,daily,weekly,monthly} only get run if
 /etc/cron.hourly/0anacron is not executable. On my system, if I remember
 correctly, /etc/cron.hourly/0anacron had the executable bit set after I
 emerged cronie, but I never set up anacron. I don't know if it properly
 runs all the cron.* scripts regularly by default, but after a quick
 chmod -x /etc/cron.hourly/0anacron logrotate returned to running
 regularly.

 I really don't know what's going on with the 501, but I hope that helps
 with getting it to run regularly (at least, unless you actually know how
 to use anacron, in which you probably know whether or not this makes
 some sense).


That was it. Thanks a lot for the tip.

Re: [gentoo-user] amavisd: running or not running???

[Urs Schütz]

On 04/05/15 14:57, Jarry wrote:

Hi Gentoo-users,

I have this strange problem: I can not start amavisd because
it is running, and at the same time I can not stop amavisd
because it is not running. How's that possible?

vs4 ~ # /etc/init.d/amavisd start
  * WARNING: amavisd has already been started
vs4 ~ # /etc/init.d/amavisd stop
  * Stopping amavisd-new ...
The amavisd daemon is not running   [ !! ]
  * ERROR: amavisd failed to stop
vs4 ~ # /etc/init.d/amavisd start
  * WARNING: amavisd has already been started
vs4 ~ # ps -e | grep amavis
vs4 ~ #

How can I fix this mess?

Jarry



/etc/init.d/amavisd zap

Urs

Re: [gentoo-user] portage summary logs not rotated any more

[Alexander Kapshuk]

  50378 Apr  5 08:33 dmesg
  -rw-rw 1 portage portage6268 Apr  1 19:35 emerge-fetch.log
  -rw-rw 1 portage portage 2687784 Apr  5 09:04 emerge.log
  -rw-r--r-- 1 rootroot 292292 Apr  5 08:34 lastlog
  -rw--- 1 rootroot9986127 Apr  5 16:10 messages
  -rw--- 1 rootroot 142911 Dec 22 19:30 messages-20141222.gz
  -rw--- 1 rootroot 132157 Dec 28 20:30 messages-20141228.gz
  -rw--- 1 rootroot 277867 Jan  4 22:00 messages-20150104.gz
  -rw--- 1 rootroot 173843 Jan 12 10:20 messages-20150112.gz
  drwxr-xr-x 2 rootroot   4096 Dec 22  2013 openconnect
  -rw-r--r-- 1 rootroot 188788 Apr  5 08:34 pm-powersave.log
  -rw-r--r-- 1 rootroot   4837 Sep 30  2014
  pm-powersave.log-20141001.gz
  -rw-r--r-- 1 rootroot785 Oct 31 07:35
  pm-powersave.log-20141101.gz
  -rw-r--r-- 1 rootroot848 Dec  1 17:00
  pm-powersave.log-20141201.gz
  -rw-r--r-- 1 rootroot  67852 Jan  1 18:34
 pm-powersave.log-20150101
  drwxrwsr-x 3 portage portage4096 Oct 29  2013 portage
  -rw-r--r-- 1 rootroot 660096 Apr  5 08:33 rc.log
  -rw-r--r-- 1 rootroot   2705 Dec 22 17:37 rc.log-20141222.gz
  -rw-r--r-- 1 rootroot   2493 Dec 28 08:33 rc.log-20141228.gz
  -rw-r--r-- 1 rootroot   4003 Jan  4 19:51 rc.log-20150104.gz
  -rw-r--r-- 1 rootroot   3026 Jan 12 08:57 rc.log-20150112.gz
  drwxrwx--- 2 rootportage4096 Oct 29  2013 sandbox
  -rw--- 1 rootroot  64064 Apr  5 08:34 tallylog
  -rw-rw-r-- 1 rootutmp1792896 Apr  5 10:30 wtmp
  -rw-rw-r-- 1 rootutmp  32029 Dec 25 17:04 wtmp-20141225.gz
 
  Any input on how to fix this would be much appreciated.

 It seems to me that logrotate stopped rotating your logs back in Jan.  Did
 you
 change something in its configuration back then?

 This is what I have in /etc/cron.daily/logrotate:
 
 #!/bin/sh

 /usr/sbin/logrotate /etc/logrotate.conf
 EXITVALUE=$?
 if [ $EXITVALUE != 0 ]; then
 /usr/bin/logger -t logrotate ALERT exited abnormally with
 [$EXITVALUE]
 fi
 exit 0
 =


 PS. I leave previous message content untrimmed in case someone else spots
 something of significance on what you have posted to date and can chime in
 with a solution.

 --
 Regards,
 Mick


The contents of my logrotate cron job file seems to be the same as yours.

cat /etc/cron.daily/logrotate
#!/bin/sh

/usr/sbin/logrotate /etc/logrotate.conf
EXITVALUE=$?
if [ $EXITVALUE != 0 ]; then
/usr/bin/logger -t logrotate ALERT exited abnormally with [$EXITVALUE]
fi
exit 0

On further troubleshooting, I found that running logrotate in debugging
mode did not reveal anything amiss with the logrotate configuration as far
as I could tell.

/usr/sbin/logrotate -dv /etc/logrotate.conf
reading config file /etc/logrotate.conf
including /etc/logrotate.d
reading config file chrony
reading config file consolekit
reading config file elog-save-summary
reading config file openconnect
reading config file openrc
reading config file pm-utils
reading config file rsyncd
reading config file syslog-ng

Handling 10 logs

rotating pattern: /var/log/chrony/*.log  weekly (4 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/chrony/measurements.log
  log needs rotating
considering log /var/log/chrony/statistics.log
  log needs rotating
considering log /var/log/chrony/tracking.log
  log needs rotating
rotating log /var/log/chrony/measurements.log, log-rotateCount is 4
dateext suffix '-20150405'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
rotating log /var/log/chrony/statistics.log, log-rotateCount is 4
dateext suffix '-20150405'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
rotating log /var/log/chrony/tracking.log, log-rotateCount is 4
dateext suffix '-20150405'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
renaming /var/log/chrony/measurements.log to
/var/log/chrony/measurements.log-20150405
creating new /var/log/chrony/measurements.log mode = 0644 uid = 0 gid = 0
renaming /var/log/chrony/statistics.log to
/var/log/chrony/statistics.log-20150405
creating new /var/log/chrony/statistics.log mode = 0644 uid = 0 gid = 0
renaming /var/log/chrony/tracking.log to
/var/log/chrony/tracking.log-20150405
creating new /var/log/chrony/tracking.log mode = 0644 uid = 0 gid = 0
running postrotate script
running script with arg /var/log/chrony/*.log : 
PASSWORD=`awk '$1 ~ /^1$/ {print $2; exit}'
/etc/chrony/chrony.keys`
cat  EOF | /usr/bin/chronyc | sed '/^200 OK$/d'
password $PASSWORD
cyclelogs
EOF

compressing log with: /bin/gzip
removing old log /var/log/chrony/measurements.log-20141222.gz
compressing log with: /bin/gzip
removing old log /var/log/chrony/statistics.log-20141222.gz
compressing log with: /bin/gzip
removing old log /var/log

Re: [gentoo-user] Is perl broken?

[Andreas K. Huettel]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Am Sonntag, 5. April 2015, 11:50:53 schrieb Peter Humphrey:
 Hello list,
 
 Today's routine update included dev-lang/perl-5.20.2 and two perl virtuals. 
 Since emerging those portage has stopped working: perl-cleaner gives it a 
 list of 71 packages to emerge but portage does nothing with them - it just 
 exits silently. Then perl-cleaner lists some hundreds of files that it can't 
 do anything with.
 

Do you see anything that is actually broken?

Minor updates (5.x.y - 5.x.y+1) do not need any rebuilds or reinstallations of 
modules.

Not 100% sure what perl-cleaner does when you run it anyway. Maybe it 
reinstalls all, but it's not necessary.

[Side note, your information on what perl-cleaner does is very vague, I can't 
distll anything useful out of it.]


- -- 

Andreas K. Huettel
Gentoo Linux developer 
dilfri...@gentoo.org
http://www.akhuettel.de/

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0

iQJ8BAEBCgBmBQJVIWLRXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ0RkJDMzI0NjNBOTIwMDY5MTQ2NkMzNDBF
MTM4NkZEN0VGNEI1Nzc5AAoJEOE4b9fvS1d5G8kP/RZuTdZbi+lB8Ts4khQcVMKr
7snXkSV+yfV5tWnMu9loJI9HEq3T3kr9WKdsR+YCcNlozT20n6h7kDfmOwbRem9V
QZCOKsMLh4ITlJ6c1cGOe7g1TAuMc2othQn3y0OgymDAWGELhYrs5JynDcAWWZxY
kJSHbu7RRBmaxklIkRD5BevFDSwCgXvFK1qGjEtU1NRqJ3vHlKU7WcLclYKVCVqQ
qzsgQkwxthjCTCQfPx0ffCBxarKkp1DdENNpPpuRnHhrlf0GxNnea4iVcrqMaMdL
Hepc1fpro2z/mc3VcmneP+Oe9vXKDzIVMYd3Q3d6jjsL2dPLjDHMDeguCIUgtnVj
yoHAYQAiaFphtgQmo4aKKO5le4dyBO9aDf5PcYPAIQ0KgUH9rFPfDeCtJb2ztjcD
gxiLAQaDvmgLYGo6wi7tjifHh7Kgo0qIF1sQNsPWxAk0dy/zAX3V6BXFAeh5UmCZ
PPN78GbvlsVvKW2kHIZf4D6qYROiR3ncDwOiw+LGVkiMeO7dui7UtKXo1Czv09Fr
bLn4ORVjARyF/cfr5CD6pe+p8iEUbLogcKnaHnGcaOiI+S0D5ihxFoKXpSqe8GpI
aSExy1rVqmOSd+rXwdznM5ZgHOSXFZGaYfRj2IwzWsxst0wJScP49ZU7q4Q0lWTB
O4JIj+FE1mpY0m4p9GVk
=AGGJ
-END PGP SIGNATURE-

Re: [gentoo-user] portage summary logs not rotated any more

[Alex Corkwell]

On Sun, Apr 05, 2015 at 06:31:43PM +0300, Alexander Kapshuk wrote:
 On Sun, Apr 5, 2015 at 5:36 PM, Mick michaelkintz...@gmail.com wrote:
 
 On Sunday 05 Apr 2015 14:19:16 Alexander Kapshuk wrote:
  On Sun, Apr 5, 2015 at 10:50 AM, Mick michaelkintz...@gmail.com wrote:
  An observation I've made, is that my log rotation seems to have effected
  all other logs in /var/log as well. It seems to have stopped working
 around
  January this year.
 
  ls -lt /var/log/messages*
  -rw--- 1 root root 9986127 Apr  5 16:10 /var/log/messages
  -rw--- 1 root root  173843 Jan 12 10:20 
 /var/log/messages-20150112.gz
  -rw--- 1 root root  277867 Jan  4 22:00 
 /var/log/messages-20150104.gz
  -rw--- 1 root root  132157 Dec 28 20:30 
 /var/log/messages-20141228.gz
  -rw--- 1 root root  142911 Dec 22 19:30 
 /var/log/messages-20141222.gz
 
 It seems to me that logrotate stopped rotating your logs back in Jan.  Did
 you
 change something in its configuration back then?
 
 This is what I have in /etc/cron.daily/logrotate:
 
 #!/bin/sh
 
 /usr/sbin/logrotate /etc/logrotate.conf
 EXITVALUE=$?
 if [ $EXITVALUE != 0 ]; then
     /usr/bin/logger -t logrotate ALERT exited abnormally with 
 [$EXITVALUE]
 
 fi
 exit 0
 =
 I then went ahead and ran logrotate by hand, which resulted in the following
 output:
 
 /usr/sbin/logrotate /etc/logrotate.conf
 501 Not authorised --- Reply not authenticated
 501 Not authorised --- Reply not authenticated
 # echo $?
 0
 
 I guess I have to figure out what the error message shown below is all about:
 501 Not authorised --- Reply not authenticated
 
 

I don't know about the 501 Not authorised, but I remember having a
similar issue with logrotate not running beginning around the same time
(the last rotated log was the week of 20141221). I can't remember
exactly what I did, but I believe around then Gentoo (and my system)
switched from vixie-cron to cronie as default. If I remember correctly,
it was anacron that caused the problem.

Take a look at these lines from the default (at least, on my system) for
/etc/crontab:

# check scripts in cron.hourly, cron.daily, cron.weekly and cron.monthly
# if anacron is not present
59  *  * * *root[ ! -x /etc/cron.hourly/0anacron ]  rm -f
/var/spool/cron/lastrun/cron.hourly
9  3  * * * root[ ! -x /etc/cron.hourly/0anacron ]  rm -f
/var/spool/cron/lastrun/cron.daily
19 4  * * 6 root[ ! -x /etc/cron.hourly/0anacron ]  rm -f
/var/spool/cron/lastrun/cron.weekly
29 5  1 * * root[ ! -x /etc/cron.hourly/0anacron ]  rm -f
/var/spool/cron/lastrun/cron.monthly
*/10  *  * * *  root[ ! -x /etc/cron.hourly/0anacron ]  { test -x
/usr/sbin/run-crons  /usr/sbin/run-crons ; }

Essentially, cron.{hourly,daily,weekly,monthly} only get run if
/etc/cron.hourly/0anacron is not executable. On my system, if I remember
correctly, /etc/cron.hourly/0anacron had the executable bit set after I
emerged cronie, but I never set up anacron. I don't know if it properly
runs all the cron.* scripts regularly by default, but after a quick
chmod -x /etc/cron.hourly/0anacron logrotate returned to running
regularly.

I really don't know what's going on with the 501, but I hope that helps
with getting it to run regularly (at least, unless you actually know how
to use anacron, in which you probably know whether or not this makes
some sense).


signature.asc
Description: PGP signature

Re: [gentoo-user] Is perl broken?

[Peter Humphrey]

On Sunday 05 April 2015 13:44:25 Alan McKinnon wrote:

 When I occasionally run into bizarre weirdness like this, I usually wait
 one hour, re-sync and try again. If it still fails, then go looking
 further.
 
 Significant updates to the CVS tree are not atomic and every now and
 then you can do a sync while a dev is making his own updates. Especially
 in the light that it all works fine for Mick.

Nope. Didn't help. I re-synced 11 hours later but got the same result.

-- 
Rgds
Peter.

[gentoo-user] amavisd: running or not running???

[Jarry]

Hi Gentoo-users,

I have this strange problem: I can not start amavisd because
it is running, and at the same time I can not stop amavisd
because it is not running. How's that possible?

vs4 ~ # /etc/init.d/amavisd start
 * WARNING: amavisd has already been started
vs4 ~ # /etc/init.d/amavisd stop
 * Stopping amavisd-new ...
The amavisd daemon is not running   [ !! ]
 * ERROR: amavisd failed to stop
vs4 ~ # /etc/init.d/amavisd start
 * WARNING: amavisd has already been started
vs4 ~ # ps -e | grep amavis
vs4 ~ #

How can I fix this mess?

Jarry

--
___
This mailbox accepts e-mails only from selected mailing-lists!
Everything else is considered to be spam and therefore deleted.

Re: [gentoo-user] Is perl broken?

[Peter Humphrey]

On Sunday 05 April 2015 18:29:05 Andreas K. Huettel wrote:

 Do you see anything that is actually broken?

Apart from perl-cleaner and portage? Emerge exiting silently after being 
given a list of packages to emerge doesn't exactly seem like normal 
behaviour to me. It was told emerge -v1 ...[list of packages] as in perl-
cleaner's usual behaviour. No ifs, no buts - just do it.

 Minor updates (5.x.y - 5.x.y+1) do not need any rebuilds or
 reinstallations of modules.
 
 Not 100% sure what perl-cleaner does when you run it anyway. Maybe it
 reinstalls all, but it's not necessary.

I just ran it to see what it'd do. I got more than I'd bargained for.

 [Side note, your information on what perl-cleaner does is very vague, I
 can't distll anything useful out of it.]

The two virtuals were perl-File-Spec-3.480.100 and perl-Storable-2.490.100. 
I hope you don't want me to list the hundreds of files it can't handle.

-- 
Rgds
Peter.

Re: [gentoo-user] Is perl broken?

[Andreas K. Huettel]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Am Sonntag, 5. April 2015, 19:03:43 schrieb Peter Humphrey:
 On Sunday 05 April 2015 18:29:05 Andreas K. Huettel wrote:
 
  Do you see anything that is actually broken?
 
 Apart from perl-cleaner and portage? Emerge exiting silently after being 
 given a list of packages to emerge doesn't exactly seem like normal 
 behaviour to me. It was told emerge -v1 ...[list of packages] as in perl-
 cleaner's usual behaviour. No ifs, no buts - just do it.

Very strange. Portage does to my best knowledge not use perl and not even 
depend on it.

- -- 

Andreas K. Huettel
Gentoo Linux developer 
dilfri...@gentoo.org
http://www.akhuettel.de/

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0

iQJ8BAEBCgBmBQJVIYdxXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ0RkJDMzI0NjNBOTIwMDY5MTQ2NkMzNDBF
MTM4NkZEN0VGNEI1Nzc5AAoJEOE4b9fvS1d5SaQP/0/l39fTkrn7tLGu7Z2OYub9
q8OCBQQg6Vhde6A5d8gZf0OsWpP2FpNmdHudAXGXJdfntiCEUWiZ+BA2yBGQLxP1
gifiToD8ACOUEiN9KZzI5o+0yr12//AE1le5QHgBEA0cPOor6vsuLPxeeT9DB806
crB2WB7cHS+Tg/Szan5Px/sm4AUNitgRsHfJH19MLP9cK5Y/8SEfcv8c4qeBVwIN
UPKI6Gp9NdvQAOLNMFWbO2Hr727l49VzayqAUktZF6lwIWrOnc1SBWJTkwwgteTM
wfopfk82z2llaAqfrYPmfLxjLgXjyXBjmsXngXR8fHjQWFWPF+ww1JuRLTojXjXW
kB9RUvg3a8tY25uwfFmtnaRMll0DgA7piJKjgUnj/oxqvu9zGdHULZZHFwW94lDu
xB5SId0QYsHOAXdd3xJ13slODGlZxrgUUcrDyW97mwUwFN79g5O0uxt/TuiDCu5o
lr8TGqJ1NohLDFH8k7t9B5vBO16sgWa713HayR7kEif6gOOoxyNBfx/blJkcOBC2
aXmABGany+jaPVmTHir/Y9pa2UgpyitYp/Qei+nCrekuM1ifMVtm572AArVK/pf2
vM+Flg13lxqLk1jGC5glfDUTwmQB42QYhTdltMDOxRDNwHwwFQjw2f25+vyB0OqZ
a3WfNAnqplT6rRLqsA7v
=WYbK
-END PGP SIGNATURE-

[gentoo-user] Re: Is perl broken?

[Martin Vaeth]

Andreas K. Huettel dilfri...@gentoo.org wrote:

 Minor updates (5.x.y - 5.x.y+1) do not need any rebuilds
 or reinstallations of modules.

This is at most partially correct:
At least, after the update, the install directories change;
here from

/usr/lib/perl5/{vendor_perl,}/5.20.1
to
/usr/lib/perl5/{vendor_perl,}/5.20.2

So, at least, perl-cleaner wants to rebuild, and it is sane
to do this (for various reasons: avoiding confusion with
mixed directories, compitability with binary packages,
omitting redundant directories).
Moreover, I didn't check before the rebuild, but after
the rebuild there is no 5.20.1 in @INC.
(So it might be even the case that the rebuild is *necessary*).

I suggest to either use the same 5.x directory for all
5.x versions, or to include 5.x.y into the subslot name
to avoid the above mentioned minor inconsistencies.

After all, the final aim is to use subslots instead of
perl-cleaner, isn't it?

Re: [gentoo-user] Re: Is perl broken?

[Andreas K. Huettel]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Am Sonntag, 5. April 2015, 21:53:35 schrieb Martin Vaeth:

 Moreover, I didn't check before the rebuild, but after
 the rebuild there is no 5.20.1 in @INC.
 (So it might be even the case that the rebuild is *necessary*).
 

Sure about this?

huettel@pinacolada ~/Gentoo/office/app-text/writerperfect $ perl -V
Summary of my perl5 (revision 5 version 20 subversion 2) configuration:
[...]
 Built under linux
  Compiled at Feb 14 2015 23:56:45
  @INC:
/etc/perl
/usr/local/lib64/perl5/5.20.2/x86_64-linux-thread-multi
/usr/local/lib64/perl5/5.20.2
/usr/lib64/perl5/vendor_perl/5.20.2/x86_64-linux-thread-multi
/usr/lib64/perl5/vendor_perl/5.20.2
/usr/local/lib64/perl5
/usr/lib64/perl5/vendor_perl/5.20.1/x86_64-linux-thread-multi
/usr/lib64/perl5/vendor_perl/5.20.1
/usr/lib64/perl5/vendor_perl
/usr/lib64/perl5/5.20.2/x86_64-linux-thread-multi
/usr/lib64/perl5/5.20.2
.



- -- 

Andreas K. Huettel
Gentoo Linux developer 
dilfri...@gentoo.org
http://www.akhuettel.de/

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0

iQJ8BAEBCgBmBQJVIZW8XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ0RkJDMzI0NjNBOTIwMDY5MTQ2NkMzNDBF
MTM4NkZEN0VGNEI1Nzc5AAoJEOE4b9fvS1d5QasQAIovcx6dpeqqsraW5Uss2tUu
udWdBAKfDtztMjRvzKdIQT1JO84g8oB3FhnmoWAgzeHUIWfsormJ/6EbIPEmb+eF
Dct9daFa3wEQhUBEV4Wr3YVSnOl6LMZ1ZOPtlkAqgmGMEz73yvTMrwwNMjhSAy5u
7KXooNfM5pvagfCUyWkXY/uUcCC3FhT6RaLzddJcFL4dikTD6lrKLdizwclnrbNJ
YK9ZRETwsJjhyfYCoZxq5MpLMJrlstZVV++RPBv94tRbUPGdeWiie34XYG+GVQ34
lQ7oc0xDFNL9kT672uEd6ZJi7U5icM7DlruTNXNoYT3bZeo9+yKxqsvbxWzsppVS
ekjKVkCjfEGW+Swk8wQDWZCLvjm+9Pz/RPR33Dk+sI5q/Xj/3jrSieANMGlpEEkF
titj8peF/Z8Rmd9EAmPwx1j2fssXPDZLwYlJq5lTwtyVl2/lkCpeMesbf0wFMeJd
TTveTkS17PT+Dde9ok6cQ4Z2e4lc6DxuQLWw2paCrYqnwirlWyXv3OD8p7VDc7+Q
sCkgl3OcYtcRXkDjnqBmfWZdi8khAXu78NNqDpNxh1d/LqKX6kV3rxVvt1oS1pcA
ViMMBMQXJvBSfhh7dfYLtrLz5ZqHXqvBJ+vcG2BkPcGwbhPD8iH1VvI/Q/JyBRNb
NFtPsQjMud43SYTOVU8z
=TpDv
-END PGP SIGNATURE-

[gentoo-user] Re: This nite's switch to full multilib

[James]

Neil Bothwick neil at digimed.co.uk writes:


  I think we need to get away from solutions that clutter up
  configuration in the first place.  I'm not under any illusions that
  this will ever be perfect, but I do think we can do better.

Amen.


 Agreed, but this is about managing the options we have now. Like it or
 not, we need to put extra entries in package.use and eix-test-obsolete is
 the best current way of removing them when they're no longer needed, as
 portage's autounmask facility only adds to the file, it never cleans up
 after itself.

And Amen, brother. As stated before, it reminds one of parenting where
teenagers must take responsibility to clean up after themselves. GLEP 64
will go a long way to providing the framework for tool/code creation
to clean up many, many errant files on gentoo. In fact if one were
to desire building a system that is fully verified, you'd need something
like GLEP-64 as the beginning or organization and tracking of what
it's installed. Granted EAPI-5 is moving in the right direction, and it
looks like we are moving to make that a requirement for all packages on gentoo.

 On my journey to learn more deeply about gentoo, I have looked closely
at dozens and dozens of packages, maybe over 100. It is a freaking mess.
Little consistency or structure or requirements from long ago, still
have their remnants of effects.

I find eix-test-obsolete (ETO) only produces valid things to address, at the
lower end of the 20% mark. There is no way to 'tame the best' on it's sputum
so I do not use it.  The best ETO can do is suggest a list of things to look
at (manually) for possible need of attention. If folks  are really concerned
about efficiency; it is quite easy to prune portage manually.  I use
scripts based on size or date, when I feel the need. Remove something
important?: just --sync and download again; no worries. After all one can
--sync to get something back if it is lost and of value.  As I find
attachment to codes that I want some permanency, I just replicate them into
/usr/local/portage. I  often like to keep old codes around (a very valid
reason for 2T drives) to look at various codes and how they evolved. The
various eclasses one package uses versus the eclasses chosen by another dev
to package up a code. ETO thinks old codes and old kernels are cruft. I
think the myriad of files spewed when some ebuilds are installed are cruft
and they are often not accounted for when packages are removed. 

So let's all get behind GLEP-64 so folks can build some real tools
for cleaning up and maintaining gentoo based systems.  If you
really want to get up on this issue, read up on Directed Graphs,
particularly DAGs, and you'll begin to understand  what is possible
if GLEP-64 is *pushed* via the user base as a demand for those motivated
devs to move us to a GLEP-64 compliant gentoo. 

Currently, unless you manually groom your gentoo system(s), you end up with
a pig_sty as remnants of  codes, installs, configs etc etc just pile up and
it takes a one off inspection to filter many files as to should I stay or
should I go now (old punk lyrics).


It is way past time for gentoo to offer robust tools for monitoring
and cleaning out cruft. What is cruft, needs to definable by the system
owner. So the codes and tools will need to be flexible to fit the needs and
desires of the user base, and therein we have much work to do, imho.


hth,
James