On Thu, Jun 23, 2022 at 09:28:47AM +0200, Kamil Dudka wrote: > On Wednesday, June 22, 2022 7:45:09 PM CEST Kevin Fenzi wrote: > > On Wed, Jun 22, 2022 at 11:09:13AM -0000, Michael J Gruber wrote: > > > > I also think that every package change (including rebuild) must be > > > > tracked in changelog. > > > > > > I think that convolution is at the very heart of the problem: > > > > > > As it is, dist-git tracks "packaging sources", i.e. spec and source hashes > > > or files, and this determines the content of the src.rpm and its version. > > > > > > What you get when you build a binary rpm from that src.spm depends very > > > much on the environment. And that environment is not reflected in the > > > version nor in the built rpm (besides Build Host and Date). > > Well, it's reflected in the requires/provides/contents of the rpm too > > though right? > > > > If I build foo-1.0-1 against libbar-2.0-1 and then again against > > libbar-4.0-1 its going to require different libs at install/run time. > > The problem is that sometimes you build against libbar-4.0-1 vs. libbar-4.0-2 > and you get qualitatively different binary RPMs as the result in each case, > despite you triggered both the builds from the same dist-git commit. This > difference is not always reflected in metadata of the resulting RPMs. That is true. But this is a hard problem to solve: some information about the build environment ends up in the Provides/Requires metadata. We could include more, that'd take up space in each binary rpm. The proposal that started this thread adds a free-form field which obviously is not enough to capture this. Maybe we should generate a JSON file that describes the build root and include it in the -debuginfo or -debugsource package? fedpkg or dnf could then learn how to fetch it nicely. Zbyszek _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
