Package: reprepro Version: 4.17.1-1 Hi,
(bug reported against 4.17.1, I'm actually using the jessie-backports version 4.17.0, but since there's no significant change in 4.17.1 I guess it still applies) I'm using reprepro and created a shell script to migrate packages from sid to testing via the "pull" command. Basically it searches for all dsc files in Sid, and builds a list of all files older than 10 days, for each one, writes a line in the form "sourcename = <version>" in a file referenced by FilterSrcList in conf/pulls. Recently I noticed that testing had leftovers from the previous version of a source package which were renamed, or from binary packages no longer built (I stumbled upon those leftovers with the reportcruft command). For example, one of my source packages builds several binaries and some of them were dropped between two versions; sid (which got the package via processincoming) had correctly removed those binary packages as expected, but testing (which got the packages via pull from sid) still kept the N-1 version of those removed binary packages, alongside version N of the source and (remaining) binary packages. Likewise, one of my source packages was renamed, but still built a binary (transitional) package with the same name as the old source/binary, and testing kept the N-1 version of this source package (with no binary package associated) alongside version N of the new source package and its binaries (including the one named like the old source). I'm not sure if it's a bug or if it's intended behavior, if it is actually the intended behavior, of course feel free to close the bug (but maybe this should be documented somewhere in the manual page). Also, it makes me ask, is the "pull" command (+FilterSrcList) the right one to migrate packages from sid to testing, or is the "copysrc" command better for this usage ? Regards, -- Raphaël Halimi
signature.asc
Description: OpenPGP digital signature