Hi Joromir

On Thu, Dec 06, 2012 at 11:57:42PM +0100, Jaromir Hradilek wrote:
> On 12/06/2012 07:33 PM, Salvatore Bonaccorso wrote:
> >Package: blazeblogger
> >Version: 1.2.0-3
> >Severity: minor
> >
> >-----BEGIN PGP SIGNED MESSAGE-----
> >Hash: SHA512
> >
> >Hi Angel
> >
> >Running blazeblogger 1.2.0-3 in wheezy produces the following e.g on
> >blaze edit,
> >
> >$ blaze edit --help
> >"my" variable $head masks earlier declaration in same scope at 
> >/usr/bin/blaze-edit line 336.
> >Usage: blaze-edit [-fpqCPV] [-b DIRECTORY] [-E EDITOR] ID
> >        blaze-edit -h|-v
> >
> >   -b, --blogdir DIRECTORY     specify a directory in which the BlazeBlogger
> >                               repository is placed
> >   -E, --editor EDITOR         specify an external text editor
> >   -p, --page                  edit a page
> >   -P, --post                  edit a blog post
> >   -f, --force                 create an empty source file in case it does
> >                               not already exist
> >   -C, --no-processor          disable processing the blog post or page with
> >                               an external application
> >   -q, --quiet                 do not display unnecessary messages
> >   -V, --verbose               display all messages
> >   -h, --help                  display this help and exit
> >   -v, --version               display version information and exit
> >$
> >
> >Not futher looked at it.
[...]
> 
> Hi Salvatore,
> 
> Thank you very much for taking the time to report this issue. This
> is actually fixed upstream in commit ea748e5 (that is, in the
> development version of the tool). Is there any way I can help with
> releasing an updated version of the blazeblogger package with this
> issue fixed? Would it help Debian packagers if I released an
> upstream bug fix update with this patch applied?

Thank you for the fast reply, Jaromir, haven't looked at upstream git
if this was already fixed.

Regarding an update: We are quite late in the stage of the freeze for
the upcoming wheezy release and the Release Team has strengtened the
rules for the unblock requests, see [1].

Saying that means, an update would only be allowed if the issue is at
least important and would be done via unstable (in this case it's
possible).

Am I right that blaze edit still works, and only issues this warning?
Or ist there something I'm missing right now?

 [1]: http://release.debian.org/wheezy/freeze_policy.html

Regards,
Salvatore

Attachment: signature.asc
Description: Digital signature

Reply via email to