IceStorms
(usa openSUSE)
Enviado em 19/12/2018 - 18:18h
Outra coisa que estava esquecendo.
Depois que usei o emerge-webrsync, vieram duas notícias (eselect news read), uma delas segue abaixo.
Aparentemente existe um conflito e para solucionar o problema ele manda usar "sync-allow-hardlinks = no" no repos.conf. Entretanto não entendi direito o que deve ser feito.
For users of the rsync tree, beginning with sys-apps/portage-2.3.42,
the default behavior for sync operations will use hardlinks in order
to ensure that a repository remains in a valid state if something
goes wrong [1]. For example, if signature verification fails during a
sync operation, the new hardlink behavior will preserve the previous
state of the repository.
The new behavior may conflict with configurations that restrict the
use of hardlinks, such as overlay filesystems. Therefore, users will
have to set "sync-allow-hardlinks = no" in repos.conf if they have
a configuration that restricts the use of hardlinks, but this should
not be very common:
[DEFAULT]
sync-allow-hardlinks = no
Note that it is possible to sync more efficiently using git [2]
instead of rsync, though git consumes an increasing amount of disk
space over time unless shallow pull is enabled via the sync-depth
option in repos.conf [3] (requires sys-apps/portage-2.3.42 or later).
[1]
https://bugs.gentoo.org/660410 sys-apps/portage: use rsync
--link-dest to implement atomic repository updates (and abort if
signature verification fails)
[2]
https://wiki.gentoo.org/wiki/Portage_Security#git-mirror_repo
[3]
https://bugs.gentoo.org/552814 sys-apps/portage: support shallow
git pull by setting sync-depth = 1 in repos.conf
Será que isso tem alguma ligação com esse problema que estou tendo?
________________________________________
Sabayon Linux. Fedora. Debian.
Linux Mint. Mageia. FreeBSD.
¨¨¨¨¨¨¨¨¨
LinuxCounter - Registered Linux user since 2006:
https://www.linuxcounter.net/cert/438332.png
