Your message dated Fri, 27 Jul 2007 15:32:03 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#388830: fixed in blosxom 2.0-15
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: blosxom
Version: N/A
Severity: normal
Hello,
As announced in
http://lists.debian.org/debian-devel/2006/09/msg00630.html, this bug
report is part of a mass bug filing campaign about the "abuse" of
debconf templates of type "note".
First of all, in case you fixed you package in the short timeframe
that happned between my announcement and this bug report, please
accept my apologies and, of course, feel free to ask me to close the
bug report...or just close it yourself.
One or more template(s) has/have been identified in blosxom
debconf templates and an automated analysis mentions that it/they is/are
displayed to users at low or medium priority.
The debconf-devel(7) manpage makes it clear that the "note" type should
be used only for important notes that the user really should see.
On the other hand, the "low" priority is meant for very trivial items
that have defaults that will work in the vast majority of
cases. The "medium" priority is meant for normal items
that have reasonable defaults.
As such, a note should only be used for IMPORTANT stuff, so actually
all debconf notes should be priority high....or should not exist.
Please consider one of the following options:
- move the text of the debconf note to the README.Debian file. The drawback
is that the text will not be translatable anymore, which will be worked
in the future. However, given that your note is very rarely displayed,
this is indeed not a very strong drawback
- move the text to NEWS.Debian. This option should however rather be
reserved for future texts of the same kind as the contents of this file
is only displayed when users upgrade the package
- change the template type to "error" in case this note is meant to be
displayed only in some cases when a problem shows up during execution of
the maintainer's scripts. Please check debconf-devel(7) for details
- raise the priority to "high". This should be the last option to consider.
It should be used only in cases where you judge that the information you
display is VITAL for users of your package and that one could NOT USE IT
if not reading the note.
A dedicated check will be proposed to the lintian and linda package
maintainers so that future uses of low and medium priority note
templates will be discouraged in the future. So, if you wish you
package to be lintian-clean, then you need to fix this..:-)
Template(s) identified in your package:
blosxom -- config:10 blosxom/old_cgi_file
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/dash
Kernel: Linux 2.6.17-2-686
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to fr_FR.UTF-8)
--- End Message ---
--- Begin Message ---
Source: blosxom
Source-Version: 2.0-15
We believe that the bug you reported is fixed in the latest version of
blosxom, which is due to be installed in the Debian FTP archive:
blosxom_2.0-15.diff.gz
to pool/main/b/blosxom/blosxom_2.0-15.diff.gz
blosxom_2.0-15.dsc
to pool/main/b/blosxom/blosxom_2.0-15.dsc
blosxom_2.0-15_all.deb
to pool/main/b/blosxom/blosxom_2.0-15_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Gerfried Fuchs <[EMAIL PROTECTED]> (supplier of updated blosxom package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Fri, 27 Jul 2007 16:53:14 +0200
Source: blosxom
Binary: blosxom
Architecture: source all
Version: 2.0-15
Distribution: unstable
Urgency: low
Maintainer: Gerfried Fuchs <[EMAIL PROTECTED]>
Changed-By: Gerfried Fuchs <[EMAIL PROTECTED]>
Description:
blosxom - light, feature-packed weblog app with plugin extensibility
Closes: 233403 234309 280912 313164 372480 388830 406445 420956 422247 423441
Changes:
blosxom (2.0-15) unstable; urgency=low
.
* The "is it this time of the year again..." release.
* Set myself as lone maintainer.
* Remove debhelper stuff.
* Remove debconf handling for upgrades since before sarge release
(closes: #388830, #313164, #422247, #420956)
* Fixed image URL in cgi script (closes: #406445)
* Pulled fix for xml breakage from new sf.net upstream release
(closes: #280912)
* Fixed postrm (closes: #372480)
* debian/rules: Removed some cruft.
* Use ctime from POSIX instead of Time::localtime which seems to break
localtime()'s $isdst which is needed to fix the timezone handling for
nice_date (closes: #233403)
* Get rid of param("-f") and replace it by more flexible useable
$ENV{BLOSXOM_CONFIG_FILE} (closes: #423441, #234309)
* Add a NEWS.Debian file about these changes.
Files:
7b07e85c28e461588bcff0727d22b522 521 web optional blosxom_2.0-15.dsc
fe36c4be3300d927761c838674eb3361 12269 web optional blosxom_2.0-15.diff.gz
c3d1d9f8c7ed00f3452aea0fef89a328 24706 web optional blosxom_2.0-15_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGqgyrELuA/Ba9d8YRAg4pAKCDXKIX/FVnn6ojJ9TUwkxMQ/A6dACdHWPo
4NpSiQMHT872j7boWb3dEPA=
=KQsk
-----END PGP SIGNATURE-----
--- End Message ---
