Why not to reopen this bug if it hasn't been fixed yet? ;)
In fact, it's fixed in upstream. The reporter confirmed it is fixed.
And all commits for the fix are included in latest stable release of libfm and
pcmanfm (1.1.0).
If reopening this bug gives a possibility for 1.1.0 to come into Wheezy then
why not?
But I hardly doubt it is possible to gather all fixes for the subject and apply
them on ancient libfm 0.1.17.
If you ask me I would never try that, I don't know which side effects will that
cause,
because changing major number of upstream version sure was for reason,
and the diff between 0.1.17 and 1.1.0 is near 4MB while unpacked libfm tarball
takes near 7MB.
May be it is still good for everyone to postpone fix to time after Wheezy
release.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
