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

Re: Processed: merging 400768 and 466643



severity 466643 important
thanks

Quoting Debian Bug Tracking System (owner@bugs.debian.org):
> Processing commands for control@bugs.debian.org:
> 
> > severity 400768 grave
> Bug#400768: apt: Returns "E: Wow, you exceeded the number of versions this APT is capable of"
> Severity set to `grave' from `important'
> 
> > forcemerge 400768 466643
> Bug#400768: apt: Returns "E: Wow, you exceeded the number of versions this APT is capable of"
> Bug#466643: please increase number of package names
> Forcibly Merged 400768 466643.

I don't think that playing with bug severities without a preliminary
discussion is pretty exxagerated:

  grave
          makes the package in question unusable or mostly so, or causes
          data loss, or introduces a security hole allowing access to the
          accounts of users who use the package.

That bug fits the definition of "important" is one is paranoid enough:

   important
          a bug which has a major effect on the usability of a package,
          without rendering it completely unusable to everyone.

(note that the last bug reporter himself, who is anything but an
inexperienced DD, just set the severity to "normal")

The reported problem happens when users have entries in their
sources.list file which trigger a lot of packages and versions to be
tracked...which is currently still uncommon. So, while I agree that
the bug should be dealt with in order to avoid further bigger problems
when the size of the Debian archive will grow, this is not urgent as
of now. In short: precisely the definition of "important".


Attachment: signature.asc
Description: Digital signature


Reply to: