Package: reprepro Version: 3.8.2-1 Severity: normal reprepro 3.8 has apparently started to leave lockfiles in place if the previous command ended with errors:
INF: Preparing to add single acpi-support-base binary (0.109-11) INF: Using source package 'acpi-support' dpkg-architecture: warning: Specified GNU system type powerpc-linux-gnu does not match gcc system type x86_64-linux-gnu. Building acpi-support-base_0.109-11em1_all.deb in /opt/reprepro/grip/incoming dpkg-deb: building package `acpi-support-base' in `/opt/reprepro/grip/incoming/acpi-support-base_0.109-11em1_all.deb'. ERROR: '/opt/reprepro/grip/incoming/acpi-support-base_0.109-11em1_all.deb' cannot be included as 'pool/main/a/acpi-support/acpi-support-base_0.109-11em1_all.deb'. Already existing files can only be included again, if they are the same, but: md5 expected: 6b28df4abf8e50f2ed41b4160905cb8b, got: 754b37be5d32b1a22b3944d6b95bdde5 sha1 expected: a44d321331cb940c770c0e89d296c1a90fd98835, got: 19d4cdb48e1c4500e80477d5e0b814f5a721ae37 sha256 expected: 92ded78d200ed98c6e0836c5f3ed8401e3bd73286574e276bd0dedaa899aa432, got: 96b4d9f2bb19c1372e16c58452d0f7926f0252b2b400abb23d98b498af956826 size expected: 4354, got: 4356 There have been errors! INF: cleaning grip incoming directory INF: Adding coreutils INF: Preparing to add single coreutils binary (6.12-2) Building coreutils_6.12-2em1_amd64.deb in /opt/reprepro/grip/incoming dpkg-deb: building package `coreutils' in `/opt/reprepro/grip/incoming/coreutils_6.12-2em1_amd64.deb'. reprepro has locked /opt/reprepro/grip at /usr/bin/em_autogrip line 432 Is this intentional in 3.8? The output comes from the em_autogrip script that tries to update the repository using a filter and emgrip processing. In some cases, errors are expected but reprepro used to handle these cleanly and continue. The presence of a lockfile now makes it difficult to automate multiple reprepro calls because deleting a lock file by brute force is not a particularly good idea but appears necessary. I added the 'die' call specifically to catch this error. For now, I'm having to implement a rm -f against the lockfile if it ever appears during a run and try external methods to ensure that no other reprepro commands are running at the same time. -- 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.6.1-1 Single library to read/write tar, ii libbz2-1.0 1.0.5-1 high-quality block-sorting file co ii libc6 2.9-2 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) ii lzma 4.43-14 Compression method of 7z format in -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
