Bug#805424: in apt marked as pending
reassign 806378 bugs.debian.org thanks David, what kind of software are you using to make these reports? Please mention it on bug 806378 and Cc me. Thanks! I see the package name was listed, but the bug title is not. > "DK" == David Kalnischkieswrites: DK> Control: tag 805424 pending DK> Hello, DK> Bug #805424 in apt reported by you has been fixed in the Git repository. You can DK> see the commit message below, and you can check the diff of the fix at: DK> https://anonscm.debian.org/cgit/apt/apt.git/diff/?id=15c0a78 DK> --- DK> commit 15c0a78ce78d395586254d9685d0189714d0db2e DK> Author: David Kalnischkies DK> Date: Thu Nov 19 16:19:15 2015 +0100 DK> ignore lost+found in private directory cleanup DK> In ce1f3a2c we started warning about failing unlinking, which we DK> consistently do for directories. That isn't a problem as directories DK> usually aren't in the places we do want to clean up – with the potential DK> exeception of "lost+found", so lets ignore it like we ignore our own DK> partial/ subdirectory. DK> Closes: 805424
Bug#805424: in apt marked as pending
On Sat, 2015-11-28 at 01:32 +0800, 積丹尼 Dan Jacobson wrote: > reassign 806378 bugs.debian.org > thanks Why? None of the messages that you're discussing are produced by the BTS. Regards, Adam
Bug#805424: Bug#806378: Re: Bug#805424: in apt marked as pending
[oops; adding CC to #806378] On Fri, 2015-11-27 at 18:47 +, Adam D. Barratt wrote: > On Sat, 2015-11-28 at 01:32 +0800, 積丹尼 Dan Jacobson wrote: > > reassign 806378 bugs.debian.org > > thanks > > Why? None of the messages that you're discussing are produced by the > BTS. > > Regards, > > Adam
Bug#805424: in apt marked as pending
> "JAK" == Julian Andres Klodewrites: JAK> There's no point reassigning 806378 to bugs.debian.org Any better place to reassign it? Even if they are generated differently, when they get to the user they look like they are coming from the same software.
Bug#805424: in apt marked as pending
On Sat, Nov 28, 2015 at 02:01:50AM +0800, 積丹尼 Dan Jacobson wrote: > > "JAK" == Julian Andres Klodewrites: > > JAK> There's no point reassigning 806378 to bugs.debian.org > > Any better place to reassign it? > Even if they are generated differently, > when they get to the user they look like they are coming from the same > software. Sorry, no. You can file a support request on https://alioth.debian.org/tracker/?func=add_id=1=21 to at least get the default script in /usr/local/bin changed though. I'm thinking about merging both ways (changelog and commit message) into one script, with an option to switch between the two, and then get that installed into alioth's /usr/local/bin Then everyone could hopefully switch to one script. -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. When replying, only quote what is necessary, and write each reply directly below the part(s) it pertains to (`inline'). Thank you.
Bug#805424: in apt marked as pending
On Sat, Nov 28, 2015 at 01:32:09AM +0800, 積丹尼 Dan Jacobson wrote: > reassign 806378 bugs.debian.org > thanks > > David, what kind of software are you using to make these reports? > Please mention it on bug 806378 and Cc me. Thanks! > I see the package name was listed, but the bug title is not. Almost everyone uses a different script. The default script is installed as /usr/local/bin/git-post-receive-tag-pending on Alioth, for example. We use a custom variant that works on commit messages instead of changelog entries and has some more tweaks like including the package name in the subject and the body of the email: http://anonscm.debian.org/cgit/apt/aliothscripts.git/tree/git-post-receive-tag-pending (and some other tweaks inherited from the copy used by dpkg) In contrast to everyone else, we include the package name in both subject and title. You are right that it would make sense to include the bug title in the subject (if that's what you were trying to say), but this seems slightly complicated, although possible. It also means that any push mentioning bugs will take 800 ms longer. Not sure if that's worth it. There's no point reassigning 806378 to bugs.debian.org -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. When replying, only quote what is necessary, and write each reply directly below the part(s) it pertains to (`inline'). Thank you.
Bug#805424: in apt marked as pending
> "JAK" == Julian Andres Klodewrites: >> JAK> There's no point reassigning 806378 to bugs.debian.org >> >> Any better place to reassign it? >> Even if they are generated differently, >> when they get to the user they look like they are coming from the same >> software. JAK> Sorry, no. You can file a support request on JAK> https://alioth.debian.org/tracker/?func=add_id=1=21 JAK> to at least get the default script in /usr/local/bin changed JAK> though. JAK> I'm thinking about merging both ways (changelog and commit JAK> message) into one script, with an option to switch between the JAK> two, and then get that installed into alioth's /usr/local/bin JAK> Then everyone could hopefully switch to one script. OK. I tried to register for an account there, but it said Unix name already taken (jidanni). I pressed password recovery, and it said username doesn't exist. I would rather like to leave that machine to be the territory of developers, and just wish to relay my feedback to you and have you guys take care of the rest.