* Guillem Jover <[email protected]>, 2017-10-06, 23:39:
Date: Sat, 01 Apr 2017 00:00:14 +0000 Ftpmaster: Scott Kitterman Suite: unstable Sources: libdc0_0.3.24~svn3121-4 Binaries: libdc-dev_0.3.24~svn3121-4 [amd64, arm64, armel, armhf, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x] libdc5v5_0.3.24~svn3121-4 [amd64, arm64, armel, armhf, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x] Reason: RoQA; unmaintained, dead upstream, low popcon, library with no rdeps Bug: 761989 Date: Sat, 01 Apr 2017 14:22:46 +0000
I'm not sure what happened here, but the code that generated these entries (the remove() function in daklib/rm.py) doesn't look particularly robust. If an exception happened during removal, the separating empty line (or the trailing === thing in the .txt file) would not be written to the log.
Date: sh: 0: getcwd() failed: No such file or directory Sat, 06 May 2017 08:45:30 +0000
This would happen if you ran "dak rm" from non-existent cwd. Should be fixed by this: https://salsa.debian.org/ftp-team/dak/commit/400066ea702d5185 -- Jakub Wilk
