#695295 blazeblogger: "my" variable $head masks earlier declaration in same scope at /usr/bin/blaze-edit line 336.

#695295#5
Date:
2012-12-06 18:33:10 UTC
From:
To:
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.

Regards,
Salvatore

- -- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
iQIcBAEBCgAGBQJQwOTiAAoJEHidbwV/2GP+prgQANOJks6ghEjOpd1+0ch5ycxJ
g/RACwnNx80O7qcdlTjULNNpTEuDU9OH4JDNAM7tIGw89uXafJVZ2FMIMTrvME5o
trN5bOs0+XLnELtlgY4yrXyxSapv7/bbW+AuUHIG6p+lw5zko3E52KRXTkWwVlym
o8wcMbGvZKYYfvcSOZstUSs65q/Q6O3mSt86DZEzGz0xIhU1CGdIMbBmf0H4q5EZ
NvvcOBxWtI4zNl5lHGK3oCyIhgchLZgTlwx3vngACWSXeFjkTHOEN5vfh4VaUqEv
nG8Je9y1epQgKQlbvVj7TFYn+L+WpXOikWWroO2AmbfViUqSoVhXKnpw+JX1ZHGQ
yu99XrZJVGVVKqG6/5MZUY4h0TYW+YMhrPr5Mv/KjnCZFk3bicWlJuCeCZ2JR8Rh
S/H57dxsniDP64NvRM4KSpnxOV1fo/ilRvpRCTLzQWdVJpGpRNdRBUURqmKb/IbK
CAcbc1GVXbaeNIUU3/MuN3WE0D7uIrya3hpeqkDsz3zY/ny+WcQa5L3TjEymZqM1
9V6TxPz/O9zDS9sAeDvsOBBjouKJwWSZHLeXSUYYQnYIuA09PYOdA+E5LJFLIH7e
pzFfM5V4qcr25KTzsIK3AfLOqwuStglp0ORXxPPtfCwdkPQxEqB/bESjqOJD8e8H
YJF4ZCFjEwcgaQEpmxpL
=c3Jn
-----END PGP SIGNATURE-----

#695295#10
Date:
2012-12-06 22:57:42 UTC
From:
To:
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,
Jaromir

#695295#15
Date:
2012-12-06 22:57:42 UTC
From:
To:
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,
Jaromir

#695295#20
Date:
2012-12-07 07:17:56 UTC
From:
To:
Hi Joromir
[...]
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

#695295#27
Date:
2012-12-08 02:15:55 UTC
From:
To:
warning is absolutely harmless. The fix is to rename one of the
variables to avoid this collision.

#695295#32
Date:
2012-12-11 08:37:28 UTC
From:
To:
2012/12/8 Jaromir Hradilek <jhradilek@gmail.com>



Thank you both for your emails, I was on a little 4 days vacation.

Jaromir, do you plan to release new version soon?

Greetings!

#695295#37
Date:
2012-12-13 17:39:22 UTC
From:
To:
Hi Angel,

I intend to make a bug fix release later this month or shortly after New
Year, partly to resolve this and few other minor issues users may
experience with the current version, partly to reassure the users that
BlazeBlogger is not a dead project. After that, I would like to finally
start working on the next major release: I have a very clear idea of
what I want to accomplish and I can't wait to see it implemented.

Kind regards,
Jaromir

#695295#42
Date:
2012-12-26 22:53:45 UTC
From:
To:
Hi Jaromir

Thanks! That's great to hear!

Regards,
Salvatore