Red Hat Bugzilla – Bug 1476839
Fedora Packaging Guideline cleanups for glibc.spec
Last modified: 2017-08-17 14:32:44 EDT
Summary changes (copy from %changelog):
* Mon Jul 31 2017 Tomasz Kłoczko <firstname.lastname@example.org> - 2.25.90-31
- added execute /sbin/ldcofig in %%transfiletriggerin and
%%transfiletriggerpostun and removed %%post/%%postun with /sbin/ldconfig
executions as those scripttlets are no longer needed
%%verify(not md5 size mtime) if %%ghost is used
- remove in %%files redundant %%config(missingok,noreplace) and
%%verify(not md5 size mtime) if %%ghost is used
- remove Group, %%defatr and %%clean (official Fedora Packaging Policy)
- remove redundant %%ifing
* With introduction %%transfiletriggerin and %%transfiletriggerpostun will be possible dramatically reduce number of scrip lets executed during multiple packages installation or upgrade. Every package which installs/upgrades/removes some libraries are executing /sbin/ldconfig in %post and %postun. With %triggers all those execution can be removed and post install/upgrade/remove %trigger package will be executed at the end of the whole sequence of packages changes.
- reduce overall time of packages installation/upgrades/removes
- reduce number of dependencies from /sbin/ldconfig
If this patch will be commited it can be added massive change in all packages (on trunk only) to start remove execution /sbin/ldconfig in %post/postun.
In mean time this will no generate any conflicts with any packages which will be executing ldconfig in those scriptlets.
* None of the spec file subpackages headers needs to be surrounded by %f .. %endif if those packages are conditional. Only exact packages %files sections needs to be withing %if .. %endif
* %ghost disables checking content of the file because such content and digest is not included in the binary package. By this weakening file verification policy by add %%verify(not md5 size mtime) is completely redundant because %ghost disables this by default. Fragments from rpm source code from lib/verify.c:
if (fileAttrs & RPMFILE_GHOST)
flags &= ~(RPMVERIFY_FILEDIGEST | RPMVERIFY_FILESIZE |
RPMVERIFY_MTIME | RPMVERIFY_LINKTO);
The same is %%config(missingok,noreplace).
Attached patches are generated from my cloned git repo.
Created attachment 1307159 [details]
Created attachment 1307160 [details]
Created attachment 1307170 [details]
Created attachment 1307175 [details]
*** Bug 1476840 has been marked as a duplicate of this bug. ***
This is not as simple as making the change.
*** This bug has been marked as a duplicate of bug 1380878 ***
Please have look on other changes because I've intentionally provided all this ticket changes in separated patches.
Change about use triggers is only one of those changes.
(In reply to Tomasz Kłoczko from comment #7)
> Please have look on other changes because I've intentionally provided all
> this ticket changes in separated patches.
> Change about use triggers is only one of those changes.
Your other changes have nothing to do with this bug description. Please do not file multiple bugs in a single bug.
You have two options:
(1) Post your patches to Fedora glibc list to discuss changes and get your patches accepted:
(2) File another bug about glibc.spec file cleanup.
I do appreciate the cleanup help, particularly the Fedora Packaing guideline does say not to use Group, so the removal is particularly relevant.
So moment .. you are not glibc package maintainer?
(In reply to Tomasz Kłoczko from comment #9)
> So moment .. you are not glibc package maintainer?
I am the glibc package maintainer.
(In reply to Carlos O'Donell from comment #10)
> (In reply to Tomasz Kłoczko from comment #9)
> > So moment .. you are not glibc package maintainer?
> I am the glibc package maintainer.
Sorry, to put it more clearly: The Fedora glibc is maintained by a *team* of developers. I am the steward for that team.
So could you please be so kind and forward to the group my ticket?
(In reply to Tomasz Kłoczko from comment #12)
> So could you please be so kind and forward to the group my ticket?
Certainly. Posted with review.
(In reply to Carlos O'Donell from comment #13)
> (In reply to Tomasz Kłoczko from comment #12)
> > So could you please be so kind and forward to the group my ticket?
> Certainly. Posted with review.
From you email:
- Remove specific %config and %verify in the presence of %ghost.
I'm rejecting this patch because it relies on what appears to be implementation
dependent behaviour of %ghost, specifically that it ignores certain changes.
While it seems logical that %ghost should ignore certain changes I would rather
leave the belt-and-suspenders check with %verify, and %config."
Seems you do not understand how %ghost is working. If %ghost is specified in generated binary package description there is no file mtime, md5sum. Specify %verify is pointless/redundant because those rules are part of the %ghost.
In other words you are rejecting how %ghost is working and applies how you are thinking that this token is working.
"The way to achieve this, is to use the %ghost directive. By adding this directive to the line containing a file, RPM will know about the ghosted file, but <b>will not add it to the package</b>. However it still needs to be in the buildroot. Here's an example of %ghost in action."
Why do you want disable verification of the files which are physically not included in the package!!!!????
%ghost file as well cannot be replaced by new file because:
a) new file will never will be installed by package because it is %ghost file
b) even if file could be installed it is not possible to find out is file with new content because there is not in package description size, mtime and md5sum.
If you do not understand how %ghost is working just try to make short experiment with test package with only one file marked those tokens.
"I am rejecting patch #1 outright, the %if'ing I find a matter of taste.
The NEVRA change always happens anyway."
Do you know what it is Ockham razor or KISS principle?
(In reply to Tomasz Kłoczko from comment #14)
> If you do not understand how %ghost is working just try to make short
> experiment with test package with only one file marked those tokens.
(In reply to Tomasz Kłoczko from comment #15)
> Do you know what it is Ockham razor or KISS principle?
Please continue this discussion on the Fedora glibc mailing list.
I plan to close this bug once I have integrated the accepted suggetions.
Sorry if you have no time to work on the package please do not ask me to waste my time on convincing bunch of people who don't know enough about rpm packaging (those people already approved change which completely does not make any sense!!!).
Do what you want but I'm more and more convinced already that trying contribute to the Fedora is pointless.
(In reply to Tomasz Kłoczko from comment #17)
> Sorry if you have no time to work on the package please do not ask me to
> waste my time on convincing bunch of people who don't know enough about rpm
> packaging (those people already approved change which completely does not
> make any sense!!!).
> Do what you want but I'm more and more convinced already that trying
> contribute to the Fedora is pointless.
I'm sorry you feel that way. My suggestion to send your comments to the mailing list is so that we can continue the discussion more naturally via email, rather than back and forth on this particular bug. Your contributions are not pointless, several of your suggestions are good, and I'll include them in a glibc.spec update. Thank you for that.
Look .. in discussion people are using arguments. You've already refused one of the patches because "I find a matter of taste".
How can we continue discussion if you are refusing arguments and sending me to /dev/tree? (sign to mailing list on which people approved completely pointless patch)
glibc.spec is one of the scariest spec I've ever seen. It uses 100% generating %files lists in %install making content of the packages completely not unreadable. Amount of the code in %install is few times larger than what is possible to have in case straight listing what needs to be in each subpackages.
Again: if you are going to discourage anyone who will be sending you patches you are doing very good job.
I'm not going to do your job convincing group of people on the glibc mailing list if it is part of the process,
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle.
Changing version to '27'.
This is now fixed in rawhide.
Author: Tomasz Kłoczko <email@example.com>
Date: Thu Aug 17 14:14:18 2017 -0400
- Remove 'Buildroot' tag, 'Group' tag, and '%clean' section, and don't
remove the buildroot in %install, all per Fedora Packaging Guidelines
(In reply to Tomasz Kłoczko from comment #19)
> Look .. in discussion people are using arguments. You've already refused one
> of the patches because "I find a matter of taste".
That's just one part of the patch.
> How can we continue discussion if you are refusing arguments and sending me
> to /dev/tree? (sign to mailing list on which people approved completely
> pointless patch)
I don't follow. I'm not refusing any arguments. I'm refusing to apply certain patches that don't match my own tastes, particularly when the patch isn't technical in nature but just a cleanup. Similarly I would refuse patches that remove large block quote comments in the spec file because I like such comments.
> glibc.spec is one of the scariest spec I've ever seen. It uses 100%
> generating %files lists in %install making content of the packages
> completely not unreadable. Amount of the code in %install is few times
> larger than what is possible to have in case straight listing what needs to
> be in each subpackages.
Yes, we could probably switch to a static list of files, but the list of headers changes when the kernel changes, and some files vary by architecture, so in the end it is simpler from a maintenance perspective to have a fully 100% automatically generated %files list.
If you have an interest in converting glibc to a static file list I'd be interested in seeing the consequences on the glibc.spec file and the %ifarch variances you'd need to maintain the list.
This sounds fairly low priority given how many other things there are to work on in the project, and we already have the existing method working without problems.
> Again: if you are going to discourage anyone who will be sending you patches
> you are doing very good job.
I apologize, my intent was not to discourage. My intent was to move this discussion to a mailing list where we can have an easier time communicating instead of in bugzilla.
> I'm not going to do your job convincing group of people on the glibc mailing
> list if it is part of the process,
This is a community project, you always have to convince other people. The glibc team draws from a variety of volunteers, including contributors from IBM, Intel, Red Hat, and Linaro. I want you to email the list so I can have additional help reviewing your patch, and perhaps getting broader input on the changes.
Again, in summary, please keep sending patches. Not all of them will be accepted, but some will, and that's positive progress.
Thanks again for the patches to cleanup the Fedora packaging policy violations.