Reopened #2470.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2470#event-12354300211
You are receiving this because you are subscribed to this thread.
Message ID:
___
Rpm-maint mailing list
Not so fast it seems, I just got this:
```
+++ /srv/rpmtests.dir/at-groups/353/stderr 2024-04-04 08:40:58.419002150
+
@@ -1,2 +1,2 @@
-error: Illegal char '*' (0x2a) in: *
+error: failed to write all data to /tmp/bad.req: Broken pipe
```
But at least it's now hinting at the problem.
--
Let the floodgates open!
You can view, comment on, or merge this pull request online at:
https://github.com/rpm-software-management/rpm/pull/3016
-- Commit Summary --
* Bump version to 5.99.90 to begin a new devel cycle
-- File Changes --
M CMakeLists.txt (2)
M tests/pinned/rpmsigd
Merged #3016 into master.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/3016#event-12354439990
You are receiving this because you are subscribed to this thread.
Message ID:
___
Rpm-maint mail
Closed #2988.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2988#event-12355359872
You are receiving this because you are subscribed to this thread.
Message ID:
___
Rpm-maint mailing list
Rpm
Here we go. Details in commits, and this is obviously nowhere near complete,
the v6 work will be on-going throughout the year.
You can view, comment on, or merge this pull request online at:
https://github.com/rpm-software-management/rpm/pull/3017
-- Commit Summary --
* Start a v6 format dr
Merged #3017 into master.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/3017#event-12355437943
You are receiving this because you are subscribed to this thread.
Message ID:
___
Rpm-maint mail
Closed #2368 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2368#event-12355469187
You are receiving this because you are subscribed to this thread.
Message ID:
___
Rpm-maint m
Done in #3017
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2368#issuecomment-2036746689
You are receiving this because you are subscribed to this thread.
Message ID: ___
Rpm-maint mailing
Done in #3017
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/864#issuecomment-2036747341
You are receiving this because you are subscribed to this thread.
Message ID: ___
Rpm-maint mailing l
Closed #864 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/864#event-12355475047
You are receiving this because you are subscribed to this thread.
Message ID:
___
Rpm-maint mai
Obsolete crypto tags are gone from v6 packages in #3017 , what remains to be
done is disabling validation on those by default.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/1292#issuecomment-2036758478
You are receiving this because
The tag conflicts between signature and header are gone as of #3017, what
remains is to error out if tags >= 1000 are found in v6 signature header.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/1570#issuecomment-2036760091
You are rec
Details in the commit messages (GH didn't populate the description
automatically for some reason).
You can view, comment on, or merge this pull request online at:
https://github.com/rpm-software-management/rpm/pull/3018
-- Commit Summary --
* Rename script->args to script->prog
* Replace
As mentioned above, this is indeed expected behavior; when the trigger source
is part of the transaction, the trigger is also activated, and is fed *all* the
matching prefixes. It's analogous to *all* the packages shipping files in the
`/` prefix being part of the transaction.
That said, I can
How about defaulting to Zstd compression as opposed to Gzip?
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/discussions/2919#discussioncomment-9014566
You are receiving this because you are subscribed to this thread.
Message ID:
@pmatilai As a behavioral change, perhaps this is suitable for RPM v6? (as in
v6 of the tool, not v6 of the format)
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/1939#issuecomment-2038570348
You are receiving this because you are sub
Uh? This would be just an extra option, not replace any existing functionality.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/1939#issuecomment-2038983260
You are receiving this because you are subscribed to this thread.
Message ID: _
It's not a bad idea. Gzip is getting a bit long in the tooth, and I guess all
distros moved to something better 10-15 years ago.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/discussions/2919#discussioncomment-9017177
You are receiving this
19 matches
Mail list logo
