Detlev Brodowski <[EMAIL PROTECTED]> (29/06/2005): > Package: apt-move > Version: 4.2.23 > Severity: important > > -- System Information: > Debian Release: testing/unstable > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: i386 (i686) > Shell: /bin/sh linked to /bin/bash > Kernel: Linux 2.6.12.1-db-gx270 > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) > > Hello, > > please update the package-dependences (rebuild) for the new apt 0.6.
While repackaging, we've got many
"Compatibility levels before 3 are deprecated."
so a:
echo "4" > debian/compat
should be interesting. I'm not aware of packaging problems on other
platforms, but it might be ok on all of them.
Then this line in debian/rules:
$(MAKE) install DESTDIR=`pwd`/debian/tmp
isn't working anymore, please then consider this new one:
$(MAKE) install DESTDIR=$(CURDIR)/debian/apt-move
And the package can be created without any kind of warning.
(I didnt't tried with pbuilder since it's broken by now.)
Lintian reports:
[EMAIL PROTECTED]:/chroot/build/apt-move-4.2.23$ lintian -i -I
../apt-move_4.2.23_i386.deb
E: apt-move: duplicate-conffile /etc/apt-move.conf
(+informations, which leads to the following solution)
Removing this file:
debian/conffiles
makes it lintian-clean.
Sorry if I'm that far away from the bug topic, but I thought that
repackaging should be done as soon and as clean as possible. Then I
suggest an all-in-one repackaging method.
--
Cyril Brulebois
signature.asc
Description: Digital signature
