On 4/9/07, Thorsten Leemhuis <fedora@xxxxxxxxxxxxx> wrote:
Christopher Stone schrieb: > On 4/9/07, Thorsten Leemhuis <fedora@xxxxxxxxxxxxx> wrote: >> Christopher Stone schrieb: >>> On 4/7/07, Thorsten Leemhuis <fedora@xxxxxxxxxxxxx> wrote: >>>> Christopher Stone schrieb: >>>>> On 4/6/07, Thorsten Leemhuis <fedora@xxxxxxxxxxxxx> wrote: >>>>>> I also plan to remove disttags from those of my packages that update >>>>>> seldom, as I think it's just utterly confusing if there are packages in >>>>>> FC7 that still have a disttag ".fc6" in it. >>>>> huh? How is this even physically possible? >>>>> /me am confused. >>>> You mean "Packages in FC7 that have .fc6 as disttag"? Easy: That happens >>>> if a packages was never rebuild during a devel cycle. And that happens >>>> quite often: >>> So in other words, when the release team branches devel to F7 they >>> don't do a rebuild on all packages like they should? >>> >>> This seems just a little dangerous to me. All packages should be >>> rebuilt on branches. >> /me is nor sure if Christopher means the devel branch before or after >> branching for F7 (in this case). > > Well, what makes most sense to me is to branch devel to F7. Then do a > rebuild on all the packages in F7. This should be done at the time > when you freeze stuff (that is only bug fixes go in). This way > package maintainers can put big changes in devel and bug fixes in F7. devel currently gets branched to F7 when F7 is ready (e.g. the rawhide is (nearly) identical to F7 then). Nobody would want to rebuild everything at that point of time ;-) So your idea *with the current branching procedure* is a no go. >>> I am really quite surprised that this is not >>> already done. There are already automatic rebuilding scripts, why not >>> just kick off a shell script? >> Because some packagers dislike that? To avoid that users have to >> download new packages just because they were rebuild? There are probably >> more reasons that don't come to my mind yet. > Why would you have to download a new package? You arent bumping the > release tag or changing the spec file at all. All you are doing is > firing off a build of the current package in a new branch. Example: synaptics-0.14.4-8.fc6 in rawhide and FC-6 now; gets rebuild for F7, so new package is named synaptics-0.14.4-8.fc7. Yum/Anaconda will download and update the new package.
Ah I see. So, what is this yum-presto package I've seen recently and delta rpms? I don't know much about it, but it sounds like a solution to this "problem". -- Fedora-packaging mailing list Fedora-packaging@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-packaging
