Re: [Rpm-maint] [rpm-software-management/rpm] Dynamic Spec generation (#1485)

It would be nice to see some simple example(s) :-) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

[Rpm-maint] [rpm-software-management/rpm] RFE: gathering the release notes (#1683)

I was wondering if it would not be good idea to collate all the recent release notes into one big file (I dunno say `RELEASES`?) which would make checking the rpm change much easier. eg Just now I was trying to work out when `rpmspec` gained support for --with/--without but pretty much gave up

Re: [Rpm-maint] [rpm-software-management/rpm] RFE: gathering the release notes (#1683)

(My guess is that `rpmspec -P --with` support was probably added in 4.15.0?) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [Rpm-maint] [rpm-software-management/rpm] RFE: gathering the release notes (#1683)

Well I just found https://rpm.org/timeline.html which seems close to this. So maybe this rpmspec feature I was looking for just slipped off or didn't make the relnotes... -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [Rpm-maint] [rpm-software-management/rpm] error: invalid version: v"3" (but only in a a complex conditional) (Issue #1883)

I opened https://issues.redhat.com/browse/RHEL-15688 -- Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/issues/1883#issuecomment-1795068331 You are receiving this because you are subscribed to this thread. Message ID:

Re: [Rpm-maint] [rpm-software-management/rpm] error: invalid version: v"3" (but only in a a complex conditional) (Issue #1883)

A backport to 4.16 would be good too -- Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/issues/1883#issuecomment-1794989036 You are receiving this because you are subscribed to this thread. Message ID:

Re: [Rpm-maint] [rpm-software-management/rpm] rpmbuild: default to LANG=C.utf8 ? (Issue #2587)

Thank you, great news! -- Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/issues/2587#issuecomment-1693149523 You are receiving this because you are subscribed to this thread. Message ID: ___ Rpm-maint

[Rpm-maint] [rpm-software-management/rpm] rpmbuild -b prints "RPM build warnings:" to stdout but the warnings to stderr (Issue #2494)

If I run `rpmbuild -bs ...` and have some warnings from my spec file then it ends with `RPM build warnings:` on stdout and then the warnings in stderr, which seems wrong to me: should both go to stderr? ``` $ rpmbuild -bs myspec.spec warning: %patchN is deprecated (1 usages found), use %patch

[Rpm-maint] [rpm-software-management/rpm] rpmbuild: default to LANG=C.utf8 ? (Issue #2587)

It is not unusual for software to require UTF-8 encoding to build these days. It seems rpmbuild still default to LANG=C nowadays. I think most platforms support LANG=C.UTF-8 now so could the default be changed? At least for platforms like Linux where it is available? For example I think mock

[Rpm-maint] [rpm-software-management/rpm] macros.in: ___build_pre_env default to LANG=C.utf8 (PR #2607)

closes #2587 You can view, comment on, or merge this pull request online at: https://github.com/rpm-software-management/rpm/pull/2607 -- Commit Summary -- * macros.in: ___build_pre_env default to LANG=C.utf8 -- File Changes -- M macros.in (2) -- Patch Links --

Re: [Rpm-maint] [rpm-software-management/rpm] rpmbuild -b prints "RPM build warnings:" to stdout but the warnings to stderr (Issue #2494)

I came here to rediscover this issue :) -- Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/issues/2494#issuecomment-1983714671 You are receiving this because you are subscribed to this thread. Message ID: