| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
when installed with "pip install gbp" it will be installed as version "0.0"
because the released version doesn't have a debian/changelog file, so it will
be installed with a warning:
balabit-bbos-tools 1.0.0 has requirement gbp==0.9.8, but you'll have gbp 0.0 which is incompatible.
and will cause an Exception when using gbp from a setuptools entrypoint script:
File "/home/walkman/stew/projects/platform/source/balabit-os-tools/.venv/lib/python3.6/site-packages/pkg_resources/__init__.py", line 574, in _build_master
ws.require(__requires__)
File "/home/walkman/stew/projects/platform/source/balabit-os-tools/.venv/lib/python3.6/site-packages/pkg_resources/__init__.py", line 892, in require
needed = self.resolve(parse_requirements(requirements))
File "/home/walkman/stew/projects/platform/source/balabit-os-tools/.venv/lib/python3.6/site-packages/pkg_resources/__init__.py", line 783, in resolve
raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (gbp 0.0 (/home/walkman/stew/projects/platform/source/balabit-os-tools/.venv/lib/python3.6/site-packages), Requirement.parse('gbp==0.9.8'), {'requiresgbp'})
This is because pkg_resources checks every dependency version and if it doesn't
match with the egg-info, it raises this Exception.
Instead, we try to parse the debian/changelog first, then load the version, or
if the debian/changelog file doesn't exists (this is the case at pip install)
we read the gbp/version.py and parse the version from it.
There is a "round trip check", which means the parsed version is written, then
it will be read back immediately to see if there is any problem.
|
|
|
|
|
|
| |
This is consistent with --git-post-export and unbreaks
tests/component/rpm/test_buildpackage_rpm.py:TestGbpRpm.test_hook_options
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Sometimes it is necessary to perform operations before preparing the
tarballs and exporting to the build directory.
One such case is when having to handle extremely large binary assets in
the orig tarball and at the same time complex packaging code, which
makes it desirable to separate the two into different repositories for
easier handling.
A pre-export hook allows to ensure that the tarball repository is
present and checked out at the correct branch.
Closes: #909266
Signed-off-by: Luca Boccassi <bluca@debian.org>
|
|
|
|
|
|
| |
See also
https://docs.python.org/3/whatsnew/3.6.html#deprecated-python-behavior
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With flake8's other warnings this doesn't make much sense since
indentation accoding to https://hg.python.org/peps/rev/3857909d7956
does not work. It triggers
- 'W503 line break before binary operator'
- 'E129 visually indented line with same indent as next logical line'
If one want to align the operators one hits
- 'E127 continuation line over-indented for visual indent'
So let's leave things as is for the moment.
|
|
|
|
|
|
| |
to make flake8 happy
Gbp-Dch: Ignore
|
| |
|
|
|
|
| |
Gbp-Dch: Ignore
|
| |
|
|
|
|
| |
Gbp-Dch: Ignore
|
|
|
|
|
|
|
|
|
|
|
|
| |
Merge behaviour in newer git versions (> v2.16) is slightly different.
This broke one test with an error something like:
Traceback (most recent call last):
File "tests/component/rpm/test_import_orig_rpm.py", line 243, in test_misc_options
eq_(len(repo.get_commits(until='pack')), 3)
AssertionError: 2 != 3
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
|
|
|
|
|
|
| |
Use the workaround from
https://github.com/travis-ci/travis-ci/issues/9815
since Python 3.7 is not yet supported by the default image.
|
|
|
|
|
|
| |
Traceback format has changed in recent python-dateutil.
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
|
|
| |
Pseudo headers are now moved to the top of the patch.
|
|
|
|
|
|
| |
If there are any non-git DEP-3 header fields, put them at the top of
the body text, regardless of whether Description or Subject is used.
Also put a blank line between them and the rest of the message body.
|
|
|
|
| |
Closes: #905934
|
| |
|
|
|
|
|
| |
Currently the extra DEP-3 headers may end up as trailers instead of
should be pseudo-headers.
|
|
|
|
| |
Closes: #741148
|
|
|
|
| |
This reverts commit 3384a0f7a763144e5d627c454d7d76c2841e553b.
|
| |
|
|
|
|
| |
gbp-dch uses sensible-editor.
|
|
|
|
| |
Gbp-Dch: Ignore
|
|
|
|
|
|
|
|
| |
using git"
This reverts commit 1592882c38fcbb107332d9a0a63b8da4e0bf8a48.
It's not ready yet.
|
|
|
|
| |
Gbp-Dch: Ignore
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When there is a merge commit in this branch, we currently get the
warning:
gbp:warning: Unknown compression type of Merge branch 'pristine-tar' into 'pristine-tar', assuming gzip
because we're grepping the commit logs to find out the compression type
of the tarballs in there.
For now, we can just use `git log ... --no-merges' to not see these
commits.
Signed-off-by: Guido Günther <agx@sigxcpu.org>
Closes: #906331
|
|
|
|
|
|
| |
If the remote branch does not exist at all that's currently not fatal.
Closes: #882187
|
|
|
|
| |
If the remote branch does not exist at all that's currently not fatal.
|
|
|
|
| |
Gbp-Dch: Ignore
|
|
|
|
| |
Gbp-Dch: Ignore
|
|
|
|
| |
Gbp-Dch: Ignore
|
| |
|
|
|
|
|
|
| |
urllib.parse did not get imported in packaegs without changelog.
Signed-off-by: Guido Günther <agx@sigxcpu.org>
|
|
|
|
|
|
|
|
| |
Fall back to iso8859-1 when opening the changelog. Helps when importing
old versions.
Closes: #900841
Signed-off-by: Guido Günther <agx@sigxcpu.org>
|
|
|
|
|
|
|
|
| |
Point to the manpages for usage examples.
Closes: #900606
Signed-off-by: Guido Günther <agx@sigxcpu.org>
|
|
|
|
| |
Gbp-Dch: Ignore
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Push of tag and or branch can be skipped by setting
--{upstream,debian}-{branch,tag}='' .
Closes: #899234
|
|
|
|
|
|
| |
Fix the docstring for _sanitize_version() and _unsanitize_version()
Signed-off-by: Guido Günther <agx@sigxcpu.org>
|
|
|
|
|
|
| |
Fix the docstring for create_pristine_tar_commits()
Signed-off-by: Guido Günther <agx@sigxcpu.org>
|
| |
|
|
|
|
| |
Closes: #898613
|
|
|
|
| |
Gbp-Dch: Ignore
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
setuptools cannot handle non-ascii characters in files declared in
"scripts".
$ python setup.py develop
[snip]
File "setuptools/command/easy_install.py", line 726, in process_distribution
self.install_egg_scripts(dist)
File "setuptools/command/develop.py", line 188, in install_egg_scripts
self.install_script(dist, script_name, script_text, script_path)
File "setuptools/command/easy_install.py", line 805, in install_script
self.write_script(script_name, _to_ascii(script_text), 'b')
File "setuptools/command/easy_install.py", line 108, in _to_ascii
return s.encode('ascii')
UnicodeEncodeError: 'ascii' codec can't encode character '\xfc' in position 785: ordinal not in range(128)
Commit 4424008f6aaa7ce93d02f0c4948ad50542284ece fixed this, and
23874c2c50ebd57426797d38f4f9c6c40dc336ec added the umlaut back in. Take
it out again so "setup.py develop" and "setup.py install" succeeds
again.
See https://github.com/pypa/setuptools/issues/761
Signed-off-by: Guido Günther <agx@sigxcpu.org>
|
|
|
|
|
| |
This is more in line with what `git config` does and eases usage in
scripts.
|
|
|
|
| |
Closes: #896654
|
| |
|
|
|
|
| |
spotted by lintian
|