| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
In order to sign commits with git, you will need Git >=1.7.9 and your
key will have to be configured by `git config user.signingkey key_id`.
Also, the repository will need to have "sign-commits = true" in
metadata/layout.conf. This will fix bug #333687.
|
|
|
|
|
|
|
| |
This check it pretty useless, since there packages don't necessarily
need to have any stable keywords, and nobody relies on this check to
decide when to keyword something. Also, remove references to the
ebuild.nostable which doesn't seem to exist anymore.
|
|
|
|
|
| |
This should help prevent repoman from consuming too much memory when
checking multiple packages or the whole tree.
|
| |
|
| |
|
|
|
|
|
| |
Since commit 11a7448f1d5a0bfb38f8de9d66a8fa8d7118c877, the config
constructor uses portage.const.EPREFIX by default.
|
| |
|
| |
|
|
|
|
|
| |
portage.dbapi.porttree.portdbapi objects. Migrate consumers to repositories
attribute of portage.dbapi.porttree.portdbapi objects.
|
| |
|
|
|
|
|
| |
This is preferred since the bytes type is available in all supported
python versions, while the unicode type is only available in python2.
|
|
|
|
| |
These go along with commit a715b65f7bd36409c1283e6911265d1f4405ab7a.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Use skel.ChangeLog from the repo to create the header of a new ChangeLog
file. Else, we just retain the original header of the ChangeLog. When
no skel.ChangeLog file exists, and this is a new ChangeLog, no header is
used.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Updating the ChangeLog file may be desirable in more repos than just the
one named 'gentoo', like e.g. the Prefix one. Hence, make this default
configurable though metadata/layout.conf.
This commit must go accompanied by a commit to
gentoo-x86/metadata/layout.conf that adds the following bit:
# Bug #337853 - gentoo's council says to enable
# --echangelog by default for the "gentoo" repo
update-changelog = true
|
| |
|
|
|
|
|
| |
Allows forced ChangeLog generation even when the vcs has detected that
the ChangeLog has already been modified.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Instead of calling echangelog, which on its turn has to query the VCS
again, use the existing information on changes made to the current
directory, and update the ChangeLog from Python itself.
This avoids a call to echangelog, and avoids again retrieving the same
VCS information as repoman already did. It makes repoman independent
from external tools it didn't install itself, and should be faster in
general.
|
| |
|
|
|
|
|
|
| |
Also, copy repoman_settings.categories to each individual
profile's dep_settings.categories attribute, in order to ensure
that portdbapi.cp_list() uses the correct category set.
|
| |
|
| |
|
|
|
|
|
| |
We can re-use the vcs_files_to_cps() function from commit
9c9145a9e3c2d8d1bcebf791ce2188add656fee2.
|
|
|
|
| |
Avoid unnecessary nested loops.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This option will call echangelog for each package that has modified
files and does not have a modified ChangeLog. Gentoo's council has
decided that this option will be enabled by default for the "gentoo"
repository. If desired, we can add a metadata/layout.conf setting so
that other repositories can control the default behavior.
|
| |
|
|
|
|
|
|
|
| |
This fixes _getMaskAtom to work correctly with the repo atoms that are
generated by MaskManager, solving the issue reported here:
https://github.com/cschwan/sage-on-gentoo/issues/90#issuecomment-2324953
|
|
|
|
|
|
|
|
| |
If we unconditionally exclude myremoved from myupdates, then removed
files will also be excluded from myheaders. This allows us to avoid
unnecessary separate manifest commits in cases when "myheaders" only
contained files that were being removed. Since our code always uses
myupdates + myremoved, this change in logic doesn't break anything.
|
|
|
|
|
| |
Don't populate the "myheaders" variable when we have thin-manifests
that contain only DIST entries.
|
|
|
|
| |
bug #340475.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This removes a special case where manifests would first be commited
without signatures for category-level or greater commits. This case
behavior wasn't very useful anyway, and would be a problem if the
unsigned manifests got rejected by a commit hook (as may happen in the
near future).
|
|
|
|
|
|
| |
Also, make repoman cache IUSE, since that's required for _match_use to
work effciently. This will eliminate lots of redundant aux_get calls
for repoman, triggered by USE deps.
|
| |
|
|
|
|
| |
This will fix bug #383269.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This allows repos to disable manifest signatures, which is useful if
they want to prevent merge conflicts like those that thin-manifests is
designed to prevent.
|
|
|
|
|
| |
Thin manifests imply reliance on the VCS for file integrity,
which implies that manifest signatures are not needed.
|