Update packaging #2
Conversation
The static validation should run as part of dh_auto_test. The current flake8-based static validation script is not working; we'll have to fix or reimplement it. For the moment let's just stop calling it.
See lintian tag build-depends-on-python-dev-with-no-arch-any.
The boundary between the software being packaged and packaged is very blurred in this case, as the package leverages the autopkgtest definitions under d/tests. Moreover this package specifically targets Ubuntu. Switching to native packaging simplifies maintenance.
|
The changelog is a manually curated list of recent and older changes that were never mentioned anywhere, given that in the part we basically relied on daily PPA builds and Switching to native packaging will help generate meaningful changelogs. For this package I don't think it's useful to use non-native packaging, as it only makes maintenance more difficult. See my rationale here: 2370918. Given that the package currently isn't in the archive the switch from |
|
The package can be tested by running: where the yaml comes from https://launchpad.net/auto-upgrade-testing-specifications. Note that the tool requires write access to |
| python3-pkg-resources, | ||
| python3-retrying, | ||
| Description: Test release upgrades in a virtual environment | ||
| A tool to do QA for release upgrades in ubuntu that performs upgrades |
There was a problem hiding this comment.
I think the description paragraph would read better as "A tool for performing release upgrades in a virtual environment". The existing one seems excessively wordy.
|
This looks good to me, thanks! |
2 participants
Update packaging, switch to format 3.0 (native), prepare Kinetic upload.