Package: qa.debian.org Severity: normal User: qa.debian....@packages.debian.org Usertags: debsources
Currently, archive.debian.org suites are imported manually into Debsources (using bin/debsources-suite-archive), and not watched periodically by the cron job using bin/debsources-update. This poses a problem at release time: when oldstable is removed from the mirror network (more precisely: when stable becomes the new oldstable), debsources-update will notice and remove all (old) oldstable packages from its database. Those packages will have to be reimported manually using debsources-suite-archive, when the archive suite shows up on archive.d.o. A proper solution for the underlying problem requires automating the watching of archive.d.o suites, which might need a separate bug report. In the meantime, we should add an import command to debsources-suite-archive, that allows to import manually, before the next stable->oldstable->archive rotation, a currently live suite as an archive.d.o suite (AKA sticky suite), inhibiting its deletion. To implement that, it might be enough to simply set sticky=True on all packages belonging to that suite. But some reflection is needed about what might happen during debsources-update runs, in the interim between the import and the disappearing of the imported suite from the mirror network. Cheers. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141026110915.15459.66522.reportbug@timira.takhisis.invalid