Re: [Rpm-maint] [rpm-software-management/rpm] IDENTITY as header tag extension discussion (#426)
Correction: GROUP -- not CHANGELOG* - is the third I18N tag. My only excuse is that I haven't thought seriously about GROUP tag values this century. That hasn't stopped endless discussions however, sigh. -- 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/426#issuecomment-380631840___ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
Re: [Rpm-maint] [rpm-software-management/rpm] IDENTITY as header tag extension discussion (#426)
All of the I18N string tags (SUMMARY/DESCRIPTION/CHANGELOG*) should not be included in IDENTITY because the value returned can depend on an envvar, and/or external files, and/or macros embedded in text. Then there are issues with the stat(2) links, where st_mtime/st_rdev/st_inode tags should not be included, but (perhaps) the st_nlinks tag that is computed from the (dev,Inode) pair should be included in IDENTITY. A preliminary list of tags to include (not tags to exclude) will hep focus on what IDENTITY reproducibility is most useful. -- 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/426#issuecomment-380550777___ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
Re: [Rpm-maint] [rpm-software-management/rpm] IDENTITY as header tag extension discussion (#426)
There are two meanings for "used": instantiated in the header and summed within IDENTITY. Newly defined/added tags will not be part of IDENTITY if positive/inclusive logic is used (as said repeatedly). Tags that were previously present in header/IDENTITY and were dropped will be a change of IDENTITY. -- 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/426#issuecomment-379875492___ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
Re: [Rpm-maint] [rpm-software-management/rpm] IDENTITY as header tag extension discussion (#426)
One of main task to solve: what we should do with tags that were used previously and do not used now, and tags that can be added in the future, but are not present in rpm now. -- 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/426#issuecomment-379855385___ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
Re: [Rpm-maint] [rpm-software-management/rpm] IDENTITY as header tag extension discussion (#426)
Panu pointed out that using the immutable region header instead of the rpmdb header gets rid of all the remapped signature tags and appended tags, thereby shortening the list above considerably. The logic still needs to become positive/inclusive to ensure the IDENTITY tag set is both well known and closed. Yes every package provides its own NEVRA. Meanwhile, filtering requires (for a specific NEVR) will be tricky: there are packages with different NEV (by intent) but common R and there's no easy way to identify requires items that need filtering. -- 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/426#issuecomment-379793931___ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
Re: [Rpm-maint] [rpm-software-management/rpm] IDENTITY as header tag extension discussion (#426)
The previous discussion was [here](http://lists.rpm.org/pipermail/rpm-maint/2018-April/007718.html). Main thought: - compute identity as a digest of filtered iterated pair of tags and its values of immutable header region; - change the awk script that generates the tag table to add a marker (like the array return marker) to identify which tags to include (or exclude); The tags that definitely should be filtered while calculation: - RPMTAG_ARCH; - RPMTAG_ARCHIVESIZE; - RPMTAG_AUTOINSTALLED; - RPMTAG_BUILDHOST; - RPMTAG_BUILDTIME; - RPMTAG_COOKIE; - RPMTAG_DBINSTANCE; - RPMTAG_DISTRIBUTION; - RPMTAG_DISTTAG; - RPMTAG_DISTURL; - RPMTAG_FILESTATES; - RPMTAG_HEADERIMMUTABLE; - RPMTAG_INSTALLCOLOR; - RPMTAG_INSTALLTID; - RPMTAG_INSTALLTIME; - RPMTAG_LONGARCHIVESIZE; - RPMTAG_LONGSIGSIZE; - RPMTAG_LONGSIZE; - RPMTAG_ORIGBASENAMES; - RPMTAG_ORIGDIRINDEXES; - RPMTAG_ORIGDIRNAMES; - RPMTAG_PAYLOADDIGEST; - RPMTAG_RELEASE; - RPMTAG_RSAHEADER; - RPMTAG_SHA1HEADER; - RPMTAG_SHA256HEADER; - RPMTAG_SIGLEMD5_1; - RPMTAG_SIGLEMD5_2; - RPMTAG_SIGMD5; - RPMTAG_SIGPGP; - RPMTAG_SIGSIZE; - RPMTAG_SIZE; -- P.S. Since RPMTAG_RELEASE is supposed to be filtered, there is sense to filter some elemenents of package RPMTAG_PROVIDE* and RPMTAG_REQUIRE* -- 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/426#issuecomment-379756181___ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
