Description of problem: Popt 1.14 was released on April 6th, 2008 while Fedora Rawhide hangs around at the older 1.13 version. Version-Release number of selected component (if applicable): popt-1.13-3 Expected results: Upgrade to 1.14... ;-)
I already prepared locally a build of popt 1.14, but it currently seems to have a bug which shows up when the locale is not C and the string contains a non- ascii character, see http://rpm5.org/community/popt-devel/0115.html - and so I am waiting for a fix before upgrading the package. The new package then should solve bug #293531.
Ping, any plans on updating popt to a more recent version one of these days (years ;) popt-1.13 is getting a bit long in the tooth...
Panu, is there somebody who could solve the still existing issue mentioned in comment #1, because there's still no fix for it. I'm not really happy to introduce a new version where I already know a regression...
Ugh, character encoding business makes my head hurt :) Probably easier to just backport the fix for bug 293531 instead (which is what I'm mostly interested here). I'll try to have a look at these somewhen...
I'm trying to reproduce the problem on my system, but I'm not able to. Is the bug still present or am I missing something?
FYI: 1.16 was released (long)time ago, see bug 999377
If I am not mistaken, comment #1 is still valid. However I can do an update...
popt-1.16-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/popt-1.16-1.fc20
popt-1.16-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
popt-1.16-2.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/popt-1.16-2.fc19
popt-1.16-2.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.