Re: [Rpm-maint] [rpm-software-management/rpm] RPM v6 package format, first public draft for commenting (Discussion #2374)

2023-02-23 Thread Demi Marie Obenour
You’re welcome. What about padding between one tag and the next? Personally, I think that using a dribble for the padding is a fine, _provided_ that: 1. No other tags are allowed in the dribble. 2. Regions are checked to be consistent. 3. The padding is _required_ to be in the dribble. 4. The

Re: [Rpm-maint] [rpm-software-management/rpm] RPM v6 package format, first public draft for commenting (Discussion #2374)

2023-02-23 Thread Stephen Smoogen
No problem. I just didn't know if I should subscribe to a list like the old rpm list. I can track this ticket. -- Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/discussions/2374#discussioncomment-5087569 You are receiving this because you are

Re: [Rpm-maint] [rpm-software-management/rpm] Collapse %patchN warnings into one (Issue #2383)

2023-02-23 Thread Panu Matilainen
Closed #2383 as completed via #2388. -- Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/issues/2383#event-8590664390 You are receiving this because you are subscribed to this thread. Message ID: ___

Re: [Rpm-maint] [rpm-software-management/rpm] Issue %patchN deprecation warning just once (PR #2388)

2023-02-23 Thread Panu Matilainen
Merged #2388 into master. -- Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/pull/2388#event-8590664143 You are receiving this because you are subscribed to this thread. Message ID: ___ Rpm-maint

Re: [Rpm-maint] [rpm-software-management/rpm] Issue %patchN deprecation warning just once (PR #2388)

2023-02-23 Thread Panu Matilainen
Seems as simple as it's going to get :laughing: -- Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/pull/2388#issuecomment-1441616478 You are receiving this because you are subscribed to this thread. Message ID:

Re: [Rpm-maint] [rpm-software-management/rpm] Issue %patchN deprecation warning just once (PR #2388)

2023-02-23 Thread Michal Domonkos
How about this one? -- Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/pull/2388#issuecomment-1441612623 You are receiving this because you are subscribed to this thread. Message ID: ___ Rpm-maint

Re: [Rpm-maint] [rpm-software-management/rpm] Issue %patchN deprecation warning just once (PR #2388)

2023-02-23 Thread Michal Domonkos
@dmnks pushed 1 commit. ec34dba06c97d2b17263c91fc7af43f45f050271 Don't repeat %patchN deprecation warning -- View it on GitHub: https://github.com/rpm-software-management/rpm/pull/2388/files/37c84fae30c7a5a2985e2a50f090a0e5ab8f68c6..ec34dba06c97d2b17263c91fc7af43f45f050271 You are receiving

Re: [Rpm-maint] [rpm-software-management/rpm] RPM v6 package format, first public draft for commenting (Discussion #2374)

2023-02-23 Thread Panu Matilainen
I'm all for properly supporting multi-arch in packages (the multiarch deps are even mentioned in the v6 spec here), but getting rid of "arch" is likely to be, uh, complicated. Even if rpm itself could, the repodata and every single depsolver out there has very deeply wired assumptions about

Re: [Rpm-maint] [rpm-software-management/rpm] RPM v6 package format, first public draft for commenting (Discussion #2374)

2023-02-23 Thread Panu Matilainen
I was about to say that checking for those zeros seems more a matter of implementing as the spec already requires it, BUT. I'm moderately surprised .. scratch that, shocked that the padding between the signature and main header is not even *mentioned* in the LSB