Some packages in Fedora provide shared RPM lua code thats used by other
packages.
It would be nice to have automatic Provides for this code like we have for rpm
macros themselves.
Usecase:
Recently, forge.lua thats used by go-srpm-macros and fonts-srpm-macros
moved out of redhat-rpm-config.
I
Removing `--clearenv`, because bubblewrap 0.4.0 does not support it
You can view, comment on, or merge this pull request online at:
https://github.com/rpm-software-management/rpm/pull/2658
-- Commit Summary --
* Removing --clearenv, because bubblewrap 0.4.0 does not support it
-- File
Making the `os_release` CMake function more strict:
1. Adding = to match pattern, because on Rocky Linux
`/etc/os-release` contains not only `ID=rocky`, but also
`ID_LIKE=rhel centos fedora`
2. Adding `| xargs`, because on Rocky Linux `ID=rocky`
line contains extra quotes
You can view, comment
Fixing the following compiler error on gcc (GCC) 8.5.0 20210514 (RedHat
8.5.0-18):
```
/root/rpm/plugins/dbus_announce.c:69:5: error: a label can only be part of a
statement and a declaration is not a statement
int ignore = dbus_error_has_name(err, DBUS_ERROR_NO_SERVER) ||
^~~
```
You
Also: make it possible to specify a glob instead of a prefix.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2655#issuecomment-1715657632
You are receiving this because you are subscribed to this thread.
Message ID:
@stoecker pushed 1 commit.
95d67ab7f8cd17547e663b0fa621ccc7f7c706a1 strip the unwanted v
--
View it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2609/files/4779c22cca6bf6f1dd08e4d84620f16e31c005e8..95d67ab7f8cd17547e663b0fa621ccc7f7c706a1
You are receiving this because you
Uh/Oh. Actually now I'm a bit lost. I'm sure when I did and tested this there
was no "v". Looking at the cpanspec tool there v is stripped afterwards. So
clearly this is an overlooking the obvious issue...
--
Reply to this email directly or view it on GitHub:
I do not maintain perl in Fedora. CCing current maintainer, @jplesnik.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2586#issuecomment-1715558411
You are receiving this because you are subscribed to this thread.
Message ID:
For the record, we pulled the plug on SemaphoreCI builds on Sep 1st.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2569#issuecomment-1715465780
You are receiving this because you are subscribed to this thread.
Message ID:
Real world usage has revealed various short-comings in the original file
trigger design. With more subject experience under the belt now, the design
needs to be revised, targetting minimal disruption to existing users.
Some of the issues include (to be updated as design is revised)
- Letting
The Perl normalized version starts with letter "v". E.g. "v1.0.0". That will
cause RPM to handle the first number as string. While it preserves an expected
version ordering, do you want it? It also means that any Provides and requires
will carry a dummy "v" now. That means more memory and CPU
Just a quick note here, as @keszybz already noted, there's reproducability and
there's reproducability, and amusingly enough the two are often in direct
conflict. To make it possible to talk about these, lets call this variant
traceability instead.
One recent enhancement (in rpm >= 4.18) is
Oh, that's a nice bonus. Assuming of course it actually works :smile:
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2643#issuecomment-1715127114
You are receiving this because you are subscribed to this thread.
Message ID:
@pmatilai converted this issue into discussion #2654.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2590#event-10342508518
You are receiving this because you are subscribed to this thread.
Message ID:
14 matches
Mail list logo
