| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
| |
The enabled flags must be consistent with implicit IUSE, in order to
avoid potential inconsistencies in USE dep matching (see bug #453400).
|
|
|
|
|
|
| |
This will fix bug #453400, which was triggered by inconsistency
between the enabled USE and the effective missing_disabled set used
in matching logic, due to implicit IUSE.
|
|
|
|
|
| |
We can't rely on the internal config instance from the given package
instance, since it does not refer to the correct profile.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
For repoman, if the package has an effective stable keyword that
intersects with the effective ACCEPT_KEYWORDS for the current
profile, then consider it stable.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
http://git.overlays.gentoo.org/gitweb/?p=proj/gentoolkit.git;a=commit;h=01d40ffed91033119bae05dac5c9cea86b94aa2e
|
|
|
|
|
|
|
|
| |
analyse utility to gentoolkit
svn path=/trunk/gentoolkit/; revision=751
http://git.overlays.gentoo.org/gitweb/?p=proj/gentoolkit.git;a=commit;h=2f90a4b9ceff920f793541376da21d313af083d9
|
|
|
|
|
|
| |
svn path=/trunk/gentoolkit/; revision=703
http://git.overlays.gentoo.org/gitweb/?p=proj/gentoolkit.git;a=commit;h=acdf616efa73b77936963eaa8b5c715db97646d2
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug 281101: Fix a backtrace introduced in r647. in getminupgrade the
rValue variable was still leftover and was used in a check when
glsa-check was run in --emergelike mode and more than one upgrade atoms
existed.
Also, update the API documentation to reflect changes back then.
svn path=/trunk/gentoolkit/; revision=671
http://git.overlays.gentoo.org/gitweb/?p=proj/gentoolkit.git;a=commit;h=2419943820ac8fb90bdf9bb5d2064a6ccdfec804
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There is no reason applied GLSAs must be stored in a checkfile. In the
current glsa-check GUI this will make it impossible to determine whether
the system is still affected by the GLSA (e.g. by re-emerging, or when a
GLSA is changed afterwards).
The current place for the checkfile (/var/cache) is not persistent per
FHS, meaning that people might clean out the contents of their injected
GLSAs. Since glsa.py is moving to portage anyway, we can use
/var/lib/portage as a place to store the injected GLSAs. Documentation
has been updated accordingly.
Note that the old checkfile should not be moved to the previous location
on upgrade since this will cause false negatives due to the above
arguments. A message should appear on upgrade (pkg_postinst or similar).
svn path=/trunk/gentoolkit/; revision=649
http://git.overlays.gentoo.org/gitweb/?p=proj/gentoolkit.git;a=commit;h=4138f5b1b6dbcf1042663a45b3eae1e652bfc9be
|
|
|
|
|
|
|
|
|
|
| |
Store "vulnerable" and "upgrade" packages in a table, and use that
data to determine which packages cannot be upgraded, and which
packages actually cause upgrades
svn path=/trunk/gentoolkit/; revision=648
http://git.overlays.gentoo.org/gitweb/?p=proj/gentoolkit.git;a=commit;h=b6a2a23926d54ccfa9a1ce331c1bc97dbe2c73d1
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows to differentiate between situations where
the system is unaffected and unexistance of an upgrade path.
Previously, the glsa-check would treat GLSAs that had no
upgrade path (such as mask glsas) as not affecting the system.
svn path=/trunk/gentoolkit/; revision=647
http://git.overlays.gentoo.org/gitweb/?p=proj/gentoolkit.git;a=commit;h=ef38a394c5c2f5901173a53914705730850f9b3f
|
|
|
|
|
|
| |
svn path=/trunk/gentoolkit/; revision=646
http://git.overlays.gentoo.org/gitweb/?p=proj/gentoolkit.git;a=commit;h=10e55d71bd5914fc7c9082adadf7bde2bec14ae3
|
|
|
|
|
|
|
|
| |
StringIO
svn path=/trunk/gentoolkit/; revision=645
http://git.overlays.gentoo.org/gitweb/?p=proj/gentoolkit.git;a=commit;h=88c18ffe936e602c45dcaa7500961623c49697ca
|
|
|
|
|
| |
Avoid "TypeError: keywords must be strings" issue triggered
by unicode_literals: http://bugs.python.org/issue4978
|
|
|
|
|
| |
This helps to ensure consistent results, regardless of whether we're
using Python 2 or Python 3.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This helps to minimize ResourceWarning triggered by ^C with python3.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For example, the current licensing error message looks like:
The following license changes (package.license) are necessary to proceed:
#required by quake3-bin (argument)
>=games-fps/quake3-bin-1.32c-r1 GPL-2 Q3AEULA
If you don't know much about licensing issues, this error message
doesn't help. Instead, give references to the man page so people
can easily delve further. Now it looks like:
The following license changes are necessary to proceed:
(see package.license in the portage(5) man page for more details)
#required by quake3-bin (argument)
>=games-fps/quake3-bin-1.32c-r1 GPL-2 Q3AEULA
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
|
| |
|
|
|
|
| |
Also, remove deprecated code from doebuild (with hardcoded pipe fd).
|
|
|
|
|
|
|
| |
By using allocated file descriptors for keys in fd_pipes, we naturally
avoid interference with callers such as FileDigester and MergeProcess.
See the _setup_pipes docstring for more benefits of this allocation
approach.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This fixes a random collision that can occur with FileDigester,
triggering malfunction and a KeyError.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This reverts commit 9e37cca4f54260bd8c45a3041fcee00938c71649.
As noted in bug #448858, comment #14, dlclose is not called
automatically, so we may as well cache our library handles.
In order to protect ourselves, we use a fork since commit
7ebb2f54877edb28621c33e380f8777b1b1dc201.
|
| |
|
|
|
|
|
| |
Override things that may be unavailable, or may have portability
issues when running tests in exotic environments.
|
| |
|
| |
|