rpm -Uhv --oldpackage loses configs

Jeffrey Johnson n3npq at me.com
Wed Jun 8 00:27:38 CEST 2016

... git.rpm5.org ...

*shrug* no idea how to do cut'n'paste reliably on an iPad.

73 de Jeff

Sent from my iPad

> On Jun 7, 2016, at 6:04 PM, Jeffrey Johnson <n3npq at me.com> wrote:
> Sent from my iPad
>>> On Jun 7, 2016, at 2:49 PM, Elan Ruusamäe <glen at pld-linux.org> wrote:
>>> On 07.06.2016 21:31, Jeffrey Johnson wrote:
>>> Next time you can wait for proyvind to give you a patch to
>>> solve whatever rpm problem you report, if that is what you prefer.
>> no i prefer rpm5 modernized it's contribution system, submitting patches to mailing list is so 90s.
> Um I need notification somehow of what you wish integrated upstream.
>> it should have github/gitlab-like system where patch can be submitted as Pull-Request/Merge-Request and appropriate discussion be in that specific thread.
> The @rpm5.org project uses CVS still largely because of lack of resources.
> (aside)
> I spent a week converting the entire @rpm5.org cvs repository to git
> last year at git.rpm.org. There has been exactly zero interest in accessing,
> too little interest to even contemplate switching the repository into
> "production" every day use imho.
>> also pld has dozen of patches collected from the internet which can't be submitted by pld dudes because they have not enough knowledge to validate the patch reasoning and provide test cases. the patches just work for us. why they never landed in rpm5 repo, you already know.
> (aside)
> Having vetted proyvind's patches (some of which I wrote) multiple times, I asked for exactly what you lack:
>      what problem does the patch solve?
>      what is the usage case?
> proyvind was given the choice between launchpad.org (with equivalent to git issues
> to discuss patches) or <rpm-devel at rpm5.org> e-mail, he chose e-mail with a 1-line
> comment.
> There is a public record including my comments so that I don't have to review
> all this crap for the 5th or 10th time.
> I am not the impediment to moderrn github/gitlab merges is the point,
> particularly when issues from 5y ago are explicitly stated as a reason
> to not submit.
> For the record: I vet PLD patches every 9 months or so and integrate
> the patches that seem useful. I have been doing that for more than a decade.
>> also, proyvind did not write patches for pld, pld just took his patches what he had in rpm5 submit queue.
> There is no "submit queue" ... every proyvind patch that was submitted
> has been responded too. Every patch that looked useful was merged, rejected
> patches were responded with comments, both private and public.
> I'm way tired of *driva distro politics from 5+ years ago.
> FYI: I am the current rpm package maintainer in OpenMandriva since being
> asked to help maintain a critical piece of infrastructure through the controversies that follow proyvind everywhere he goes ...
> Meanwhile, thanks for cooking down your %config issue to toy packages
> that might fit into a test harness.
> And if you have patches for (that I have missed or not gotten to or that you think
> should be upstream etc) then you kinda need to tell me before complaining.
> Off to look at the reproducer next few days ...
> 73 de Jeff
>> -- 
>> glen
>> _______________________________________________
>> pld-devel-en mailing list
>> pld-devel-en at lists.pld-linux.org
>> http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
> _______________________________________________
> pld-devel-en mailing list
> pld-devel-en at lists.pld-linux.org
> http://lists.pld-linux.org/mailman/listinfo/pld-devel-en

More information about the pld-devel-en mailing list