RPM Community Forums

Mailing List Message of <popt-devel>

Re: Long-standing bug in popt with respect to /.popt

From: Marco Atzeri <marco.atzeri@gmail.com>
Date: Thu 15 Jun 2017 - 02:50:24 CEST
Message-ID: <9ce572b1-6e2e-7bbf-b05a-04597623623e@gmail.com>
On 14/06/2017 04:10, Jeffrey Johnson wrote:
>
>> On Jun 10, 2017, at 4:26 PM, Peter Backes <rtc@helen.PLASMA.Xg8.DE
>> <mailto:rtc@helen.plasma.xg8.de>> wrote:
>>
>> Hello,
>>
>> popt ignores /.popt if /etc/popt.d is empty.
>>
>> See https://bugzilla.redhat.com/show_bug.cgi?id=1051685 (you can find a
>> patch there).
>>

> Applied: thanks for the patch!
>
>> When will a new version of popt be released? The most recent version,
>> 1.16, is now over seven years old! The current CVS version seems to be
>> under active development. Please put out a new version of popt.
>>
>
> Yes popt-1.17 is 7+ years from popt-1.16 release.
>
> Yes, I am still actively maintaining popt, going on nearly 20 years now.
> RPM is intimate with
> POPT in very complicated ways, unlike most other applications that link
> POPT.
>
> Meanwhile, please look at reality:
>
>     1) you are the first to post a patch “upstream". The report
> rhbz#1051685 report is dated
> 2014-01-10 16:34:19 EST
> (and your patch to rhbz#1051685 was posted  2017-06-09 19:27 EDT)
>
>      2) Both the original implementor/requestor of POPT globs as well as
> the Fedora maintainer
> are members *@rpm5.org <http://rpm5.org> where POPT is maintained.
> Neither has chosen to “fix” the issue(s),*
> *likely because they have **better things to do these days.*
>
> *I’d suggest that I (as “upstream maintainer”) am not the bottleneck to
> a popt-1.17 release.*
> *
> *
> *I can do a popt-1.17 release (as in preparing the tar ball and pushing
> to http://rpm5.ort/files/popt*
> *within an hour. The due diligence of testing across multiple platforms
> and operating systems*
> *is beyond my means/energy these days, and takes perhaps 2 weeks,
> drudgery setting up*
> *VM’s to explicitly test a POPT release.*
> *

Hi Jeffrey
my 2c$

the usual way should be to put down a release candidate and
ask for feedback.
I expect any distribution package maintainer will run a
test suite, if available, before releasing any binary package;
if they don't do it is their fault.
I doubt there are a lot a package maintainer that tests more then few
systems. No one and usually also no team can cover all the available system.

Thanks for you package and Best regards
Marco
Received on Thu Jun 15 03:08:18 2017
Driven by Jeff Johnson and the RPM project team.
Hosted by OpenPKG and Ralf S. Engelschall.
Powered by FreeBSD and OpenPKG.