reopen 369257 severity 369257 serious thanks Don Armstrong writes: > reassign 369257 general > severity 369257 normal > thanks > > On Sun, 28 May 2006, Matthias Klose wrote: > > this bug is fixed for 4.1; with these changes you invalidate the > > information kept in the Debian BTS. Please fix it, or stop it. > > This has nothing to do with bugs.debian.org or the BTS at all. Talk to > the btslink implementer instead, please. [Reassigning to general > instead of closing outright in case there is a better place; otherwise > it should be closed.]
with the very same logic you could close bugs filed against ftp.debian.org about changing overrides or removing packages from the archive. you can fix it by not processing the mails affecting some packages, so it's appropriate to file against bugs.debian.org. Steve Langasek writes: > On Sun, May 28, 2006 at 06:50:21PM +0200, Matthias Klose wrote: > > Package: bugs.debian.org > > Severity: serious > > > this bug is fixed for 4.1; with these changes you invalidate the > > information kept in the Debian BTS. Please fix it, or stop it. > > > If you do want to do it correct, you have to keep information, which > > package is built from which branch. > > I'm pretty sure this bug doesn't belong to bugs.debian.org, given that it's > not the BTS admins making these changes? sorry, no. A bug tracking system doesn't track responsibilities, but problems. That is a problem with the information in the BTS. It doesn't matter if the changes can be done by the BTS admins or others. Or would you suggest a severity grave because of data loss/corruption? Please don't suggest that it's still possible to track down these changes following each control mail. Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
