[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Packages Removed from Hamm (!)

> > I have no idea who set it to grave or why.  You should have gotten
> > mail sent to you when the severity was changed, though.
> The submittor doesn't get mail when the severity of the bug is
> changed.

Are you sure?  When I send messages to control@bugs.debian.org, the
maintainers of all affected packages are copied on the result message.
Here is an example:

  Subject:	Processed: change severity
     Date:	Fri, 22 May 98 08:18 CDT
     From:	owner@bugs.debian.org (Ian Jackson)
       To:	Brian White <bcwhite@verisim.com>
       CC:	Bdale Garbee <bdale@gag.com> (gzip #22354 #22385)

  Processing commands for control@bugs.debian.org:

  > severity 22354 normal
  Bug#22354: gzip: gzip in bo depends on debianutils >= 1.6
  Bug#22385: [debian-1.3.1.r7] gzip 1.2.4-26.1 dependency problems
  Severity set to `normal'.

  > --
  Stopping processing here.

  Please contact me if you need assistance.

  Ian Jackson
  (administrator, Debian bugs database)

> > It's still a problem, even with "--force-overwrite" set
> We *have* to turn --force-overwrite back on as default in a new dpkg
> before release anyway because of #20250 and the mass of unresolved
> conflicts between hamm and bo versions of packages.

I'm didn't mean to imply differently.  It's just that setting this will
not fix the problem in its entirety.

                                 ( bcwhite@verisim.com )

     measure with micrometer, mark with chalk, cut with axe, hope like hell

To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reply to: