Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #17365
| From | Carsten Schoenert <c.schoenert@t-online.de> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: RFC: python-imgviz: Repository out of sync with Archive |
| Date | 2026-01-16 14:20 +0100 |
| Message-ID | <MdRU6-aZcW-13@gated-at.bofh.it> (permalink) |
| References | <Mdx8Z-aKIJ-1@gated-at.bofh.it> <MdFgd-aQkI-9@gated-at.bofh.it> <MdPyV-aXzp-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Am 16.01.26 um 12:45 schrieb Arian Ott: > Yes, that is what is typically done, unless you can contact the > previous > uploaders and get them to push their changes to the repository. > > > Thanks for the pointers. How would I document it in d/changelog? There > would be a gap. By usually importing every version (by using gpg import-dsc e.g.) that was uploaded to the Debian archive. > $ gbp import-dscs --debsnap python-imgviz > gbp:info: Downloading snapshots of 'python-imgviz' to '/tmp/tmp_zat7ku8'... > /tmp/tmp_zat7ku8/python-imgviz_1.7.6+ds-2.dsc: > Good signature found > validating python-imgviz_1.7.6+ds.orig.tar.xz > validating python-imgviz_1.7.6+ds-2.debian.tar.xz > All files validated successfully. > ... > /tmp/tmp_zat7ku8/python-imgviz_1.1.0+ds-1.dsc: > dscverify: /tmp/tmp_zat7ku8/python-imgviz_1.1.0+ds-1.dsc failed signature check: > gpg: Signature made Tue Jun 16 01:06:18 2020 SAST > gpg: using RSA key 9236557B170C87F8821C0AC3C1E0D92E986F7C7E > gpg: Can't check signature: No public key > Validation FAILED!! > gbp:warning: Version 1.1.0+ds-1 already imported. > gbp:warning: Version 1.2.3+ds-1 already imported. > gbp:warning: Version 1.2.4+ds-1 already imported. > gbp:warning: Version 1.2.5+ds-1 already imported. > gbp:warning: Version 1.2.6+ds-1 already imported. > gbp:warning: Version 1.3.0+ds-1 already imported. > gbp:warning: Version 1.4.0+ds-1 already imported. > gbp:warning: Version 1.4.1+ds-1 already imported. > gbp:warning: Version 1.5.0+ds-1 already imported. > gbp:warning: Version 1.5.1+ds-1 already imported. > gbp:info: Version '1.7.5+ds-1' imported under '/home/carsten/tmp/python-imgviz' > gbp:info: Version '1.7.5+ds-2' imported under '/home/carsten/tmp/python-imgviz' > gbp:info: Version '1.7.6+ds-1' imported under '/home/carsten/tmp/python-imgviz' > gbp:info: Version '1.7.6+ds-2' imported under '/home/carsten/tmp/python-imgviz' > gbp:info: Everything imported under /home/carsten/tmp/python-imgviz The advantage doing it that way is you can later see the delta changes done in every upload. Sometime that is important. Also your "issue" with the gap of changelog entries isn't existing after these imports. -- Regards Carsten
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar
RFC: python-imgviz: Repository out of sync with Archive Arian Ott <arian.ott@ieee.org> - 2026-01-15 16:10 +0100
Re: RFC: python-imgviz: Repository out of sync with Archive Soren Stoutner <soren@debian.org> - 2026-01-16 00:50 +0100
Re: RFC: python-imgviz: Repository out of sync with Archive Arian Ott <arian.ott@ieee.org> - 2026-01-16 11:50 +0100
Re: RFC: python-imgviz: Repository out of sync with Archive Carsten Schoenert <c.schoenert@t-online.de> - 2026-01-16 14:20 +0100
Re: RFC: python-imgviz: Repository out of sync with Archive Arian Ott <arian.ott@ieee.org> - 2026-01-16 16:50 +0100
Re: RFC: python-imgviz: Repository out of sync with Archive Soren Stoutner <soren@debian.org> - 2026-01-17 02:10 +0100
Re: RFC: python-imgviz: Repository out of sync with Archive Arian Ott <arian.ott@ieee.org> - 2026-01-17 19:40 +0100
Re: RFC: python-imgviz: Repository out of sync with Archive Soren Stoutner <soren@debian.org> - 2026-01-17 19:40 +0100
Re: RFC: python-imgviz: Repository out of sync with Archive Arian Ott <arian.ott@ieee.org> - 2026-01-17 19:50 +0100
Re: RFC: python-imgviz: Repository out of sync with Archive Arian Ott <arian.ott@ieee.org> - 2026-01-20 10:50 +0100
csiph-web