Your message dated Sun, 28 Mar 2010 13:44:47 +0200
with message-id <[email protected]>
and subject line Re: Bug#575664: /usr/bin/dpkg-source: absolute paths in .pc
directory of 3.0 (quilt) packages don't work well with moving and copying
has caused the Debian Bug report #575664,
regarding /usr/bin/dpkg-source: absolute paths in .pc directory of 3.0 (quilt)
packages don't work well with moving and copying
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
575664: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575664
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dpkg-dev
Version: 1.15.5.6
Severity: normal
File: /usr/bin/dpkg-source
Hi,
when dpkg-source creates the .pc directory for 3.0 (quilt) packages, the
..quilt_patches and .quilt_series are populated with absolute paths.
quilt itself uses paths relative to the current directory (that would be
debian/patches and debian/patches/series for a 3.0 (quilt) package).
The problem with absolute paths is that they break when the extracted
and patched source is moved or copied, where it's more problematic in
the latter case because you manipulate patches outside debian/patches
without noticing.
If there is no reason that requires absolute paths, I'd like too see
this changed. Otherwise (or additionally) dpkg-source should check that
the .quilt_* files in .pc still refer to a location inside the tree and
throw warnings/errors otherwise.
Andreas
-- System Information:
Debian Release: squeeze/sid
APT prefers stable
APT policy: (800, 'stable'), (700, 'testing'), (600, 'unstable'), (130,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages dpkg-dev depends on:
ii base-files 5.1 Debian base system miscellaneous f
ii binutils 2.20.1-2 The GNU assembler, linker and bina
ii bzip2 1.0.5-4 high-quality block-sorting file co
ii dpkg 1.15.5.6 Debian package management system
ii libtimedate-perl 1.2000-1 collection of modules to manipulat
ii lzma 4.43-14 Compression method of 7z format in
ii make 3.81-7 An utility for Directing compilati
ii patch 2.6-2 Apply a diff file to an original
ii perl [perl5] 5.10.1-11 Larry Wall's Practical Extraction
ii perl-modules 5.10.1-11 Core Perl modules
ii xz-utils 4.999.9beta+20100307-1 XZ-format compression utilities
Versions of packages dpkg-dev recommends:
ii build-essential 11.4 Informational list of build-essent
ii fakeroot 1.14.4-1 Gives a fake root environment
ii gcc [c-compiler] 4:4.4.2-3 The GNU C compiler
ii gcc-4.2 [c-compiler] 4.2.4-6 The GNU C compiler
ii gcc-4.3 [c-compiler] 4.3.4-8 The GNU C compiler
ii gcc-4.4 [c-compiler] 4.4.3-5 The GNU C compiler
ii gnupg 1.4.10-2 GNU privacy guard - a free PGP rep
ii gpgv 1.4.10-2 GNU privacy guard - signature veri
Versions of packages dpkg-dev suggests:
ii debian-keyring [debian-mainta 2009.11.04 GnuPG (and obsolete PGP) keys of D
-- no debconf information
--- End Message ---
--- Begin Message ---
Raphael Hertzog wrote:
> On Sun, 28 Mar 2010, Andreas Beckmann wrote:
>> when dpkg-source creates the .pc directory for 3.0 (quilt) packages, the
>> ..quilt_patches and .quilt_series are populated with absolute paths.
...
> I write "debian/patches" and "series". The version 1.15.5.6 that you're
> using is simply not creating those files (1.15.6 does). That means that it's
> quilt itself that created them. But dpkg-source is not calling quilt
> anymore...
>
> So somehow you must have done something wrong. Waiting your confirmation
> before
> closing this bug.
Uups, bug reported from the wrong machine, otherwise I could have
noticed it while reporting. The machine where the problem occurred had
an outdated version of dpkg-dev installed (package was put on hold for
whatever reason). And I was so damned sure I'm running current
squeeze/sid there ...
Sorry for bothering.
Andreas
--- End Message ---
