Before adding a reverse dependency to the list, through library
metadata in _generate_reverse_dependency_tree(), take into consideration
all the available library providers.
The generation of the list of conflicting packages must also take
auto-conflicts into consideration, as the dependency calculation
code does. (This solves systemd vs openrc-settingsd when the former
doesn't say anything about the latter).
Together with the "enabled=" repository configuration option inside repository
configuration files, the same ones can be in a disabled state if they are prefixed
with "_<file prefix>" (where <file prefix> is entropy_ at this time).
using /tmp as TMPDIR is a no go, since on modern systems, /tmp is on
tmpfs with a very limited amount of fs size assigned. Use /var/tmp/entropy
(or /var/tmp as fallback) instead.
using /tmp as TMPDIR is a no go, since on modern systems, /tmp is on
tmpfs with a very limited amount of fs size assigned. Use /var/tmp/entropy
(or /var/tmp as fallback) instead.
It happened that __get_library_breakages only handled library bumps and
not also another important case: new library dependencies. This check is
very important at runtime, because it helps coping with unsatisfied
library dependencies (that might be satisfied at the package dependencies
level).
For instance, upgrading udev may fail because the new udevadm depends
against libblkid.so.1, which is a new dependency, while the util-linux
dependency metadatum is not enforcing the new version well enough.
This commit partially reverts commit d6b7a21314.
Package revision is no longer incremented across package moves.
This has two advantages:
- much less traffic generated on the mirror infrastructure
- less updates for sabayon-limbo users when packages are moved to main
Bumping the revision was required by sabayon-weekly, which had the problem
that some package files were replaced during normal activity on
sabayonlinux.org and sabayon-limbo on the mirror. This generated checksum
errors, thus adding the checksum in the package file name ensures that
Entropy Server will never overwrite package file names unless the checksum
also matches.
Having a SHA1 checksum in the file name is also good for security, and
we may even want to create a SHA1 from the GPG signature in future.
Fabio Erculiani