Summary: | sys-apps/portage: emaint sync creates no log entries in /var/log/emerge.log | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Till Schäfer <till2.schaefer> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | denis.kurz, sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Till Schäfer
2015-07-02 12:49:17 UTC
possible related to Bug 553792 still valid in current stable And still present in 2.2.24. My last rsync was reportedly on "Thu Jan 8" according to genlop -r. I start to wonder if this is intended behaviour, but I don't know how to get the time of my last sync otherwise. I am not expected to write my own postsync hook, am I? still valid for 2.3.44. Any progress here? The issues is that the SyncRepos constructor defaults to emerge_logging=False. If we set it to True then it will work, but we should also add support for EMERGE_LOG_DIR configuration (current support is limited to emerge's run_action function). Any update on this? The Gentoo Wiki mentions that "# emaint sync --auto/-a" is now the command that should be used to sync ebuild repositories (https://wiki.gentoo.org/wiki/Ebuild_repository#Repository_synchronization): > To sync all repositories for which auto-sync=true is set, run emaint sync with the --auto switch (-a for short). This is usually the command that should be run regularly, before system updates and package installation (and is equivalent to using the old emerge --sync command) > The emerge --sync command is now only a compatibility command. Primary control of all sync operations has been moved from emerge to emaint, and emerge --sync now just calls the emaint sync module with the --auto option. Hopefully this will be fixed, "# emaint sync" should write to "/var/log/emerge.log" just like "# emerge --sync" or "# eix-sync". |