Re: NMU of libdb4.0 for prio:standard
On Tue, 15 Apr 2003, Colin Watson wrote:
> All these priority mismatch bugs are a waste of time, IMHO. The
> ftpmasters have to modify the override file anyway in order for anything
> to happen, and it's perfectly possible for them to do so in the absence
> of any change to the package (so NMUs for such bugs are not only
> overkill but useless). Furthermore, in the absence of filed RC bugs
> priority mismatches do not affect migration into testing, regardless of
> what debcheck.php may say, so the entire premise of the bug was wrong.
>
Are there others? I haven't checked yet. Perhaps at least a comment about
this should be made to any other such bugs. debcheck.php should probably
document that priority mismatches do not affect migration to reduce these
kinds of bugs.
Does debcheck.php incorrectly not check overrides?
> In any case, if you look closely, you'll find that libdb4.0 was always
> Priority: standard in its debian/control file, so this must have been
> due to overrides in the first place, which now say that libdb4.0 is
> Priority: standard:
[...]
>
> So this bug should just be closed.
>
By who and when? Should this bug be downgraded first? I could see this bug
being filed again so perhaps a downgrade and a wontfix tag until an upload
is done fixing the Priority field and debcheck.php doesn't mislead people
about this?
http://ftp.debian.org/debian/pool/main/d/db4.0/db4.0_4.0.14-1.2.diff.gz
says:
[...]
+Package: libdb4.0-dev
+Section: devel
+Priority: extra
+Conflicts: libdb2-dev, libdb1-dev, libdb-dev, libdb3-dev
+Provides: libdb-dev
+Depends: libdb4.0 (= ${Source-Version})
+Suggests: db4.0-doc
+Architecture: any
+Description: Berkeley v4.0 Database Libraries [development]
+ This is the development package which contains headers and static
+ libraries for the Berkeley v4.0 database library.
[...]
Drew Daniels
Reply to: