Your message dated Fri, 27 Jul 2007 15:32:03 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#313164: 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: 2.0-13
Severity: wishlist
Tags: l10n, patch
While translating the file blosxom, I encountered the following
typos, which I thought you might like to eliminate in a future release.
_________________
1.
po:3
auto: ⑤ Type: note
auto: ⑤ Description
reference: ⑤ ../templates:4
Original: ⌘0
Previous versions of this package did not separate configuration
variables
from the cgi-script itself. This current installation may therefore
overwrite configuration values. To safe these settings, a copy of the
old
blosxom script has been copies to /root for your convenience.
Two tiny errors: you need to use "save" and "copied":
"To save these settings, a copy of the old
blosxom script has been copied to /root for your convenience."
"safe" is the adjective: this is a safe procedure.
"save" is the verb: the script will save a copy.
"copies" is the present tense: this program copies data to /root on
startup.
"copied" is the past tense: your script has been copied to another disk.
2.
po:4
auto: ⑤ Type: note
auto: ⑤ Description
reference: ⑤ ../templates:4
Original: ⌘0
Going forward, this will not be necessary as the configuration in the
file /
etc/blosxom/blosxom.conf is preserved during upgrades.
"Going forward" is used for physical movement, not for talking about
the future. We would use "In future versions".
3.
po:5
auto: ⑤ Type: note
auto: ⑤ Description
reference: ⑤ ../templates:15
Original: ⌘0 This update of blosxom will most propably break your
setup
"probably"
To remember this word, think of "probability", all those "b"s!
_________________
I hope this is useful. :)
submitted by:
Clytie Siddall, Vietnamese localization team / nhóm Việt hóa
our mailing list / hộp thư chung của nhóm chúng tôi:
[EMAIL PROTECTED]
--- 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 ---
