#3685 Temporarily tagging gcc-4.4.4-1.fc13 into dist-f13-override
Closed: Fixed None Opened 11 years ago by jakub.

Would it be possible to temporarily tag this gcc into dist-f13-override, so that associated libtool can be built?
I'd like to get this gcc still into f13, because it fixes quite severe unwind info generation bug Roland discovered recently.

oh boy, ok, but tagging this in makes me nervous.

maybe we can make a separate koji tag/target? (it'll take a little longer, but is safer). any objections?

The difference between gcc-4.4.3-18.fc13 and 4.4.4-1.fc13 is smaller than between say 4.4.3-16.fc13 and 4.4.3-18.fc13, the upstream release branch has been deeply frozen for more than a week and the only changes in there have been the gcc/BASE_VER bump plus ChangeLog updates.
The rest of the changes are just a couple of bugfixes backported to it.

ok, I'm sold tagging...

(purposely leaving this one as new so all rel-eng'ers see status, updates)

libtool-2.2.6-20.fc13 built successfully, so this can be untagged from dist-f13-override now. Thanks.
I'll file a bodhi ticket for the gcc + libtool combo later on.

Metadata Update from @jakub:
- Issue set to the milestone: Fedora 13 Final

4 years ago

Login to comment on this ticket.