| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Signed-off-by: Lucio Sauer <watermanpaint@posteo.net>
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
|
| |
Resolves: https://github.com/pkgcore/pkgdev/issues/188
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
|
|
|
|
|
|
| |
Were broken by [1]. Understanding what and why happened is not trivial.
Many manual tests I've performed show that `pkgdev manifest` still works
as expected. I'm not sure if the tests are broken or the code is broken.
[1] https://github.com/pkgcore/pkgcore/commit/bb7b8ec465060dfc754e9115c6e8a03e040272fd
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
|
| |
Resolves: https://github.com/pkgcore/pkgdev/issues/140
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
|
| |
Resolves: https://github.com/pkgcore/pkgdev/issues/150
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
You can use "--gpg-sign" and "--no-gpg-sign" to enable/disable gpg
signing. If you don't specify any of them, pkgdev will use the value
listed in metadata/layout.conf.
You can also set this in configuration, using `commit.no-gpg-sign=` or
`commit.gpg-sign=`.
Resolves: https://github.com/pkgcore/pkgdev/issues/146
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
|
| |
Fixes: f5b955018af5715bdd72ce6b094bf901be2d8ced
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
|
|
|
|
|
| |
This new tool isn't complete, and any usage should be manually monitored
for failures or incorrect results. This tool will be improved in the
future, but for now it's a good start.
Resolves: https://github.com/pkgcore/pkgdev/issues/113
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
|
|
|
|
|
| |
If 2 or more ebuilds are being modified, and same summary is generated
for both of them, use it for both ebuilds instead of giving up.
Reported-by: Joonas Niilola <juippis@gentoo.org>
Resolves: https://github.com/pkgcore/pkgdev/issues/116
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
|
|
|
|
| |
Fix the test for systems which predefine NOCOLOR, like in case of ebuild
test environment (by epytest).
Follows: 9714e4785e1ffc56a08f042011b5a966c7520a1f
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
| |
For pkgcore we need to run multiple preparations of generating files
before creating sdist or wheel. Flit is a very simple and nice build
backend, much more than setuptools.
Also migrate to use snakeoil.dist sphinx extension for generating man
and html, to remove various logic from `doc/conf.py`.
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
|
|
|
|
|
| |
Even though just passing `-e` works (as it is just passed to git), many
users don't know the existence of this option, so now I publish it in
help.
Closes: https://bugs.gentoo.org/846785
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
|
|
|
|
|
| |
For PYTHON_COMPAT, LUA_COMPAT and USE_RUBY, show the "disable" target
after "enable" only if this target exists. For example, if I enable
py3.11 and disable py3.7 (which is no-op), it will show only "enable
py3.11". If there is no "enable", it will still show "disable py3.7".
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
When passing a `.` path while inside a package directory, it passed to
path restrict generator as a simple path, which resulted in broken
restrict which collected all ebuilds in the repository.
By using `os.path.relpath` to base of repository, we make sure the
correct path is passed and the correct restricts are generated.
Fixes: https://github.com/pkgcore/pkgdev/issues/85
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
|
|
|
|
| |
- add test for using VISUAL instead of EDITOR
- Always unset VISUAL when setting EDITOR
Bug: https://bugs.gentoo.org/871576
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
|
| |
Resolves: https://github.com/pkgcore/pkgdev/issues/89
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
|
|
|
| |
If the header of mask had a break, which looked like `#`, it would fail
to parse, which is somewhat wrong. So add it as exception.
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
|
|
|
| |
Make sign-off off by default, and enable the user to pass if manually
using `--signoff`, or by setting `commit.signoff` in config file.
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
|
| |
Resolves: https://github.com/pkgcore/pkgdev/issues/64
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
|
|
|
|
| |
Restrict targets for manifest to only targets that have uncommitted
modifications.
Resolves: https://github.com/pkgcore/pkgdev/issues/65
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
|
| |
Resolves: https://github.com/pkgcore/pkgdev/issues/36
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
|
| |
Resolves: https://github.com/pkgcore/pkgdev/issues/45
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
|
| |
Resolves: https://github.com/pkgcore/pkgdev/issues/26
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
| |
|
|
|
|
| |
Signed-off-by: Thomas Bracht Laumann Jespersen <t@laumann.xyz>
|
|
|
|
| |
Signed-off-by: Thomas Bracht Laumann Jespersen <t@laumann.xyz>
|
|
|
|
| |
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In commit 303e3bde8a1d273b85395541a7f266d7e4f8a6c0 the behaviour of
"pkgdev commit" was modified to turn single copyright year lines into
year ranges, but the following commit
51c0f9a8ba88b776551057f08a1dc0278d4b1eb3 reverted that behaviour.
This is a simplified version of the date handling where a single year is
turned into a year range when the given year is not the current year.
This mirrors the behaviour of "repoman commit"
Fixes: https://bugs.gentoo.org/835333
Signed-off-by: Thomas Bracht Laumann Jespersen <t@laumann.xyz>
|
|
|
|
|
|
|
| |
This allows for inspecting change attributes to alter potential
mangling. For example, now the entire date range in the copyright header
is replaced for new files instead of keeping the original start date
from the old files they were based on.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
To avoid config settings affecting output.
Note that this forces nonempty repo usage since the HEAD ref isn't valid
on newly initialized git repos, but this shouldn't be an issue in most
cases.
|
| |
|
| |
|
| |
|
| |
|
| |
|