View previous topic :: View next topic |
Author |
Message |
Spargeltarzan Guru
Joined: 23 Jul 2017 Posts: 317
|
Posted: Fri Dec 15, 2017 8:30 pm Post subject: [SOLVED] Emaint check all log path output |
|
|
Hi Community,
Recently the output of emaint --check all has changed to more than 3000 log entries, attached an extract of it. What does it mean? emerge --fix all didn't fix it, it says "no failed emerges found"
Code: |
emaint --check all
Emaint: check binhost 100% [============================================>]
Emaint: check cleanconfmem 100% [============================================>]
Emaint: check cleanresume 100% [============================================>]
.
.
.
/var/log/portage/app-emulation:qemu-2.10.1:20171201-172739.log
/var/log/portage/dev-python:pycups-1.9.73-r1:20171201-192821.log
/var/log/portage/app-arch:gnome-autoar-0.2.2:20171201-233910.log
/var/log/portage/media-libs:libvisio-0.1.5-r1:20171201-205600.log
/var/log/portage/dev-libs:libsigc++-2.10.0:20171201-181643.log
/var/log/portage/dev-perl:Encode-Locale-1.30.0-r1:20171201-195247.log
/var/log/portage/dev-perl:Net-SSLeay-1.810.0:20171205-224042.log
/var/log/portage/net-dns:bind-tools-9.11.1_p3:20171201-205155.log
/var/log/portage/app-crypt:gpgme-1.8.0-r3:20171202-014017.log
/var/log/portage/media-libs:libsdl2-2.0.4:20171201-234522.log
/var/log/portage/dev-lang:python-2.7.14:20171205-214820.log
/var/log/portage/virtual:perl-Digest-MD5-2.540.0-r3:20171201-175522.log
/var/log/portage/app-text:docbook-dsssl-stylesheets-1.79:20171201-174547.log
/var/log/portage/virtual:mta-1:20171201-175717.log
/var/log/portage/sys-power:acpid-2.0.28:20171201-172717.log
/var/log/portage/dev-util:xdelta-3.0.11:20171201-173915.log
/var/log/portage/virtual:perl-File-Temp-0.230.400-r5:20171205-224141.log
.
.
.
Emaint: check merges 100% [============================================>]
Emaint: check movebin 100% [============================================>]
Emaint: check moveinst 100% [============================================>]
Emaint: check world 100% [============================================>]
|
Thanks in Advance! _________________ ___________________
Regards
Spargeltarzan
Notebook: Lenovo YOGA 900-13ISK: Gentoo stable amd64, GNOME systemd, KVM/QEMU
Desktop-PC: Intel Core i7-4770K, 8GB Ram, AMD Radeon R9 280X, ZFS Storage, GNOME openrc, Dantrell, Xen
Last edited by Spargeltarzan on Fri Dec 15, 2017 11:01 pm; edited 1 time in total |
|
Back to top |
|
|
ian.au Guru
Joined: 07 Apr 2011 Posts: 592 Location: Australia
|
Posted: Fri Dec 15, 2017 9:10 pm Post subject: |
|
|
Perhaps you ran emerge -e around a week ago, everything went fine and now emaint wants to purge the logs? |
|
Back to top |
|
|
Spargeltarzan Guru
Joined: 23 Jul 2017 Posts: 317
|
Posted: Fri Dec 15, 2017 10:00 pm Post subject: |
|
|
Yes, I did it, but believe these logs weren't directly after the emerge -e, but anyway, why it doesn't purge it?
ADD: Cleaning logs is not part of --fix, use --clean instead _________________ ___________________
Regards
Spargeltarzan
Notebook: Lenovo YOGA 900-13ISK: Gentoo stable amd64, GNOME systemd, KVM/QEMU
Desktop-PC: Intel Core i7-4770K, 8GB Ram, AMD Radeon R9 280X, ZFS Storage, GNOME openrc, Dantrell, Xen |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|