Bug#739056: RFS: cwm/5.1-1 [ITP] -- Lightweight and efficient window manager for X11
I have packaged the new version of cwm, 5.5, available at:
dget -x http://mentors.debian.net/debian/pool/main/c/cwm/cwm_5.5-1.dsc
It may be necessary to modify this bug to reflect that.
On 24 February 2014 14:09, Jakub Wilk <jwilk@debian.org> wrote:
> It would be better to use dpkg-buildflags instead of hardcoding the flags in
> debian/rules.
Done, thanks for the tip.
> 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. It doesn't seem to like a .asc
file.
> FWIW, you could use this in the override instead:
> dh_auto_install -- PREFIX=/usr
Done, thanks.
> The whole EXAMPLE CONFIGURATION section looks like something that should be
> copy-pasteable, so it should use minuses.
>
> These two needs fixing, too:
> * "The modifier keys come first, followed by a ‘‐’."
> * "The ‘‐’ should be followed by either a keysym name,"
The new version has a modified manual page, so I've updated the patch
for that. I think I replaced all of them.
>> 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'm not sure if you ask about politics or technicalities. I'll assume it's
> about both. :)
The politics more than the technicalities :)
I will speak to upstream and try to resolve this. To my mind something
like openbsd-cwm or calmwm would make sense.
> Use mv(1). :P
Thanks :P
Cheers,
James
Reply to: