Context:
- Trouble in packaging at least swh-loader-svn, swh-loader-debian
- Latest debian testing.
- Used swh-loader-debian as reference because nothing changed on it
P97 for details
Description
Description
Related Objects
Related Objects
- Mentioned In
- rDLDBASEcc8975d1054c: d/changelog: Fix default initial changelog breaking packaging
rDLDSVN837fbc1e3db0: d/changelog: Fix default initial changelog breaking packaging
rDLDDEBda9ec5b6de20: d/changelog: Fix default initial changelog breaking packaging - Mentioned Here
- P97 Pb in debian packaging on latest testing...
Event Timeline
Comment Actions
I have found the culprit, our initial changelog if of the form:
<module-name> (0.0.1-1) unstable; urgency=low * -- AUTHOR-NAME <AUTHOR-EMAIL> <UTC-DATE>
When we build a package, it prepends a real changelog entry but does not touch the old one.
This was alright until recently.
Here is the list of the multiple potential broken packages:
swh-loader-core/debian/changelog: -- AUTHOR-NAME <AUTHOR-EMAIL> <UTC-DATE> swh-loader-debian/debian/changelog: -- AUTHOR-NAME <AUTHOR-EMAIL> <UTC-DATE> swh-objstorage/debian/changelog: -- AUTHOR-NAME <AUTHOR-EMAIL> <UTC-DATE> swh-py-template/debian/changelog: -- AUTHOR-NAME <AUTHOR-EMAIL> <UTC-DATE>
Comment Actions
I left the template alone and fixed the 3 modules referenced in the grep output.
I used the v0.0.1 tag's timestamp and author information as the initial changelog timestamp.
I checked that the make-package build routine worked (as dev).
So this can be closed now.