Re: [Rpm-maint] [rpm-software-management/rpm] rpmsign cannot use Ed25519 keys (#1565)
Yup, one of the thousand internal projects waiting for something else to proceed. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/issues/1565#issuecomment-791377066___ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
Re: [Rpm-maint] [rpm-software-management/rpm] RFE: use fingerprints instead of key IDs internally (#1549)
Yeah, started down this road in 2017 but ran into hidden obstacles or out of steam. Or both. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/issues/1549#issuecomment-791375843___ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
Re: [Rpm-maint] [rpm-software-management/rpm] RFE: make the hdrblob API public (#1538)
Closed #1538. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/issues/1538#event-4413127669___ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
Re: [Rpm-maint] [rpm-software-management/rpm] RFE: make the hdrblob API public (#1538)
NAK, it's specifically the kind of interface that we want to keep internal so we can change freely. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/issues/1538#issuecomment-791369887___ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
[Rpm-maint] [rpm-software-management/rpm] Ensure unique tags for in signature header (#1570)
Currently a bunch of signature tags overlap with the ones in the main header, making eg type checking harder than it should be. These overlaps need to be eliminated and made illegal in v6. * RPMSIGTAG_PGP, RPMSIGTAG_GPG (and RPMSIGTAG_PGP5) are no longer created in >= 4.16 * RPMSIGTAG_MD5 is superceded by payload digest in >= 4.14, just needs to be dropped entirely * RPMSIGTAG_SIZE and RPMSIGTAG_PAYLOADSIZE will go away with #864 * RPMSIGTAG_RESERVEDSPACE is the only thing left. This needs to be rethought, perhaps borrow an idea from rpm5 where the signature header padding was added as a dribble to the header itself, this padding could also serve the same "reserved space" purpose. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/issues/1570___ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
Re: [Rpm-maint] [rpm-software-management/rpm] RPMv6 proposal: require tag data entries in package headers (both main and signature) to be sorted (#1555)
Yeah - always except when buggy. There have been at least two occasions in the past where this was broken, which is why rpm currently has to accept them. v6 would be a good point to break and enforce this from the start, thanks for the suggestion. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/issues/1555#issuecomment-791280456___ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
Re: [Rpm-maint] [rpm-software-management/rpm] Request: Remove -release off of github releases for all new future releases? (#1568)
Closed #1568. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/issues/1568#event-4412278015___ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
Re: [Rpm-maint] [rpm-software-management/rpm] Request: Remove -release off of github releases for all new future releases? (#1568)
Sorry but no, we wont be breaking what is well over a decade-long tradition of release tagging just because some software somewhere can't cope. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/issues/1568#issuecomment-791253474___ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
[Rpm-maint] [rpm-software-management/rpm] Request: Remove -release off of github releases for future releases? (#1568)
So it can properly be used here: https://release-monitoring.org/project/15204/ Thanks in advance. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/issues/1568___ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
