Hi Michael I saw the other emails about this matter but I wanted to comment on this one directly anyway.
On Thu, Jun 08, 2006 at 03:05:50PM +0200, Michael Hanke wrote: > Package: debarchiver > Version: 0.6.1-1 > Severity: normal > > Hi, > > it seems to be impossible to install two packages (in different > distributions) > that share a common orig.tar.gz file at the same time. Is it really? > Example: Two uploads of the same package backported to sarge and etch > > - sarge upload - > psignifit_2.5.6-1.sarge0.apsy.dsc > psignifit_2.5.6.orig.tar.gz > psignifit_2.5.6-1.sarge0.apsy.diff.gz > psignifit_2.5.6-1.sarge0.apsy_i386.deb > psignifit_2.5.6-1.sarge0.apsy_i386.changes > > - etch upload - > psignifit_2.5.6-1.etch0.apsy.dsc > psignifit_2.5.6.orig.tar.gz > psignifit_2.5.6-1.etch0.apsy.diff.gz > psignifit_2.5.6-1.etch0.apsy_i386.deb > psignifit_2.5.6-1.etch0.apsy_i386.changes > > Because both packages deliver the same upstream version they obviously > share a common source tarball, that should go into the source dir of the > etch AND the sarge dists. Yes, and they do not? How do the changes files look like? > But running debarchiver seems to remove the source tarball after the > first > package is processed. If the etch upload remove the sarge version (or vice versa) that is a bug, however it depends on how your changes file look like. > For the remaining package debarchiver complains: > > Message: psignifit_2.5.6.orig.tar.gz owner () do not match > psignifit_2.5.6-1.dapper0.apsy_i386.changes owner (1000). > > Which should be due to the missing source tarball, because the reported > filesize ($size in the verifyChangesFile()) is empty too. So here is my opinion how how it works, or at least how it should work. * Each directory under $rootdir/dists is a separate installation, and should be considered as different releases. * Directories under $rootdir/dists share no files, which means that in your case you should have two different source directories under dists $rootdir/dists/etch/source $rootdir/dists/sarge/source * When you upload etch package(s) you set the target to etch and thus it will be installed under the etch subdir. * When you upload sarge package(s) you set the target to sarge and thus it will be installed under the sarge subdir. What I expect is that you done something wrong when building the packages, so that it actually install it under wrong subdir, or there is a major bug in the package. I can not tell unless you give me the changes files, and give me a listing on where the files were sorted when added to the incoming directory. Your configuration file would help as well. Regards, // Ola > Bye, > > Michael > > -- System Information: > Debian Release: 3.1 > Architecture: i386 (i686) > Kernel: Linux 2.6.8-3-686-smp > Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) > > Versions of packages debarchiver depends on: > ii adduser 3.63 Add and remove users and > groups > ii apt-utils 0.5.28.6 APT utility programs > ii dpkg-dev 1.10.28 Package building tools for > Debian > ii opalmod 0.1.13 A set of Perl modules for > various > > -- no debconf information > > > -- > GPG key: 1024D/3144BE0F Michael Hanke > http://apsy.gse.uni-magdeburg.de/hanke > ICQ: 48230050 -- --------------------- Ola Lundqvist --------------------------- / [EMAIL PROTECTED] Annebergsslingan 37 \ | [EMAIL PROTECTED] 654 65 KARLSTAD | | +46 (0)54-10 14 30 +46 (0)70-332 1551 | | http://www.opal.dhs.org UIN/icq: 4912500 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --------------------------------------------------------------- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
