Package: reprepro Version: 3.5.2-6 Severity: normal The manpage for conf/distributions is correct but it should warn that if conf/distributions is setup wrongly for Suite and Codename, untold pain can ensue in the future.
I've got a few repositories where, inadvertently, different people made the same error in configuration, setting Suite as lenny and Codename as testing. This results in the following layout: lrwxrwxrwx 1 emdebian emdebian 6 Jun 23 2008 etch -> stable drwxrwxr-x 3 emdebian emdebian 4096 Jan 26 08:00 experimental lrwxrwxrwx 1 emdebian emdebian 7 Jun 23 2008 lenny -> testing drwxrwxr-x 3 emdebian emdebian 4096 Jan 26 08:00 oldstable lrwxrwxrwx 1 emdebian emdebian 10 Jun 23 2008 sarge -> oldstable/ lrwxrwxrwx 1 emdebian emdebian 9 Jun 23 2008 sid -> unstable/ drwxrwxr-x 3 emdebian emdebian 4096 Feb 13 03:10 stable drwxrwxr-x 3 emdebian emdebian 4096 Feb 13 03:11 testing drwxrwxr-x 3 emdebian emdebian 4096 Feb 12 20:35 unstable What should have happened is that etch, lenny, sarge and sid were the real directories and oldstable, stable, testing and unstable were the symlinks. drwxrwsr-x 3 codehelp emdebian 4096 Feb 13 15:04 lenny drwxrwsr-x 3 codehelp emdebian 4096 Feb 13 15:02 sid lrwxrwxrwx 1 codehelp emdebian 5 Jan 4 02:59 testing -> lenny lrwxrwxrwx 1 codehelp emdebian 3 Jan 4 02:59 unstable -> sid However, trying the simple, obvious approach of simply swapping things around in the filesystem causes reprepro to get confused and switching the values in conf/distributions causes reprepro to prevent any further operations completely. If nothing is changed, reprepro itself carries on without apparent problems. So far, I've only fixed up one of these wrongly configured repositories and it took hours of pain and a mass rebuild of some packages. (Debian installer refuses to use the repository if the Suite and Codename are wrongly configured). Is there a safe, reliable way of reprepro getting out of the resulting mess? If not, can the manpage be made very explicit that getting these the wrong way around is a really, really, REALLY bad idea? -- System Information: Debian Release: 5.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages reprepro depends on: ii libarchive1 2.4.17-2 Single library to read/write tar, ii libbz2-1.0 1.0.5-1 high-quality block-sorting file co ii libc6 2.7-18 GNU C Library: Shared libraries ii libdb4.6 4.6.21-13 Berkeley v4.6 Database Libraries [ ii libgpg-error0 1.4-2 library for common error values an ii libgpgme11 1.1.8-2 GPGME - GnuPG Made Easy ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime Versions of packages reprepro recommends: ii apt 0.7.20.2 Advanced front-end for dpkg Versions of packages reprepro suggests: ii gnupg-agent 2.0.9-3.1 GNU privacy guard - password agent pn inoticoming <none> (no description available) -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
