* James McDonald <[email protected]>, 2014-03-14, 12:01:
It would be better to use dpkg-buildflags instead of hardcoding the
flags in debian/rules.
Done, thanks for the tip.
An unintended side-effect of passing CFLAGS to make is that now warnings
(except -Wformat) are no longer enabled. :/
Perhaps upstream could fix their makefile, so that they honour CFLAGS
from environment? It's a bit odd that they do it with CPPFLAGS and
LDFLAGS, but not with CFLAGS.
gpg doesn't grok ASCII-armored keyrings. uscan can unarmor them, but
it does it only if the extension is ".asc". So now the verification
fails:
I replaced it with a binary key. I had called it .php with an armoured
key because that made lintian happy.
Nice typo! *giggle*
It doesn't seem to like a .asc file.
Lintian doesn't know about ASCII-armoured keyrings yet; this is bug
#736711.
As regards the name /usr/bin/cwm, is there a reference for the
correct or recommended way to rename files in the event of such
collisions?
[...]
I will speak to upstream and try to resolve this. To my mind something
like openbsd-cwm or calmwm would make sense.
Great, thanks.
I wonder if extracting upstream changelog automatically from README
wouldn't be a better strategy than manually maintaining a patch.
I'd prefer if Debian changelog for initial release contained only a
single entry.
--
Jakub Wilk
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: https://lists.debian.org/[email protected]
