Your message dated Sun, 17 May 2026 13:17:39 +0200 with message-id <[email protected]> and subject line Re: dak: `dak rm -b ${package}` does not work if source of ${package} already gone has caused the Debian Bug report #1025502, regarding dak: `dak rm -b ${package}` does not work if source of ${package} already gone 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.) -- 1025502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025502 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: ftp.debian.org `dak rm -b ${package}` or other variants do not when when `${package}`'s source is already removed. This happened with lostirc (bug #1024341). The cause is likely the SQL queries in dak/rm.py that include +--- | JOIN newest_source on s.source = newest_source.source AND su.id = newest_source.suite +---[ dak/rm.py ] which then results in an empty set if `${package}`'s source is no longer in the suite. Ansgar
--- End Message ---
--- Begin Message ---On Mon, 05 Dec 2022 23:19:32 +0100 Ansgar wrote: > `dak rm -b ${package}` or other variants do not when when `${package}`'s > source is already removed. This happened with lostirc (bug #1024341). This should be fixed by https://salsa.debian.org/ftp-team/dak/-/commit/f3cbb1d69f08717ddf2015e2b94118c2532b12a4 Ansgar
--- End Message ---
