I went through most of our FC6 patches, and for each of them, checked whether they would still be needed in rawhide, re-based them, and submitted them to the upstream project (for non-packaging related patches) and/or to RH bugzilla.
All RH BZs have been linked to the ARM tracker bug, which is here:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=245418
The following patches are no longer needed for current rawhide: NetworkManager-0.6.4-5.fc6 apr-1.2.7-10 cdrtools-2.01-10 compat-db-4.2.52-5.1 kdesdk-3.5.6-0.1.fc6 libdrm-2.3.0-1.fc6 libgcrypt-1.2.3-1 liboil-0.3.8-2.1 mesa-6.5.1-9.fc6 w3m-0.5.1-15.fc6 xorg-x11-drivers-7.1-3 xorg-x11-drv-acecad-1.1.0-2.1 xorg-x11-drv-aiptek-1.0.1-2 xorg-x11-drv-ati-6.6.3-1.fc6 xorg-x11-drv-calcomp-1.1.0-1.1 xorg-x11-drv-cirrus-1.1.0-2.fc6 xorg-x11-drv-citron-2.2.0-1.1 xorg-x11-drv-digitaledge-1.1.0-1.1 xorg-x11-drv-dmc-1.1.0-2 xorg-x11-drv-dummy-0.2.0-2.1 xorg-x11-drv-dynapro-1.1.0-2 xorg-x11-drv-elo2300-1.1.0-1.1 xorg-x11-drv-elographics-1.1.0-1.1 xorg-x11-drv-evdev-1.1.2-2.1 xorg-x11-drv-fbdev-0.3.0-2 xorg-x11-drv-fpit-1.1.0-1.1 xorg-x11-drv-glint-1.1.1-4.1 xorg-x11-drv-hyperpen-1.1.0-2 xorg-x11-drv-jamstudio-1.1.0-1.1 xorg-x11-drv-joystick-1.1.0-1.1 xorg-x11-drv-keyboard-1.1.0-2.1 xorg-x11-drv-magellan-1.1.0-1.1 xorg-x11-drv-magictouch-1.0.0.5-2.1 xorg-x11-drv-mga-1.4.5-2.fc6 xorg-x11-drv-microtouch-1.1.0-1.1 xorg-x11-drv-mouse-1.2.1-1.fc6 xorg-x11-drv-mutouch-1.1.0-2 xorg-x11-drv-nv-1.2.0-4.fc6 xorg-x11-drv-palmax-1.1.0-1.1 xorg-x11-drv-penmount-1.1.0-2.1 xorg-x11-drv-spaceorb-1.1.0-1.1 xorg-x11-drv-summa-1.1.0-1.1 xorg-x11-drv-tdfx-1.3.0-2.fc6 xorg-x11-drv-tseng-1.1.0-3.1 xorg-x11-drv-ur98-1.1.0-1.1 xorg-x11-drv-vesa-1.2.1-4 xorg-x11-drv-vga-4.1.0-2.1 xorg-x11-drv-void-1.1.0-3.1 xorg-x11-drv-voodoo-1.1.0-3.1 xorg-x11-proto-devel-7.1-9.fc6
These patches were rebased, submitted to bugzilla, and merged: redhat-rpm-config-8.0.45-9.fc6 #243523
These patches were merged without bugzilla entry: anaconda-11.1.1.3-1 applied xorg-x11-server-1.1.1-47.8.fc6 applied yum-3.0.6-1.fc6 applied
These patches were rebased, submitted to bugzilla, and have not yet been merged: SDL-1.2.11-1.fc6 #245411 attr-2.4.32-1.1 #245415 authd-1.4.3-9 #245436 binutils-2.17.50.0.6-2.fc6 #243516 db4-4.3.29-9.fc6 #245416 gmp-4.1.4-9.fc6 #245456 g-wrap-1.9.6-7.1 #245461 openssl-0.9.8b-8.3.fc6 #245417 pcmciautils-014-5 #245441 pm-utils-0.19-3 #245463 smartmontools-5.37-1.1.fc6 #245442 star-1.5a75-1 #245465 subversion-1.4.3-2.fc6 #245467
These patches have been rebased and submitted upstream (or had previously been submitted upstream), applied upstream, and will be automatically picked up when the corresponding Fedora package will be rebased to a newer upstream version: e2fsprogs-1.39-7.fc6 http://thunk.org/hg/e2fsprogs/?rev/d22a0a6fcd7e ekiga-2.0.5-3.fc6 http://mail.gnome.org/archives/ekiga-devel-list/2007-June/msg00024.html rpm-4.4.2-33.fc6 https://lists.dulug.duke.edu/pipermail/rpm-maint/2007-June/000400.html
These patches have been submitted upstream but are not merged yet: util-linux-2.13-0.46.fc6
These patches disable java/mono bindings (as we don't have gcj nor mono at this time.) I'm not sure what to do with them. avahi-0.6.16-4.fc6 disable mono bindings gettext-0.14.6-4.fc6 disable java bindings subversion-1.4.3-2.fc6 disable java build vnc-4.1.2-9.fc6 disable .jar build
These patches fix real issues, and have been submitted to their respective upstream projects, but as they don't fix all the issues that we see on the ARM platform, I haven't BZ'ed them yet: firefox-1.5.0.10-5.fc6 firefox still goes into 100% CPU loop nspr-4.6.6-0.6.0.fc6 https://bugzilla.mozilla.org/show_bug.cgi?id=385583
There's about a dozen patches left that I'm hoping to be able to get rid of in the next couple of days.
Lennert Buytenhek wrote:
I went through most of our FC6 patches, and for each of them, checked whether they would still be needed in rawhide, re-based them, and submitted them to the upstream project (for non-packaging related patches) and/or to RH bugzilla.
That's awesome. I think we need to begin our integration with Koji build system -- the sooner the better. It is still early in the F8 release cycle, and so I would like for us to get things done before the release pressure starts hitting everyone.
So, the question is -- what does it take to do this integration. My (limited) understanding is:
1. There were some changes being made to Koji to support secondary architectures and bootstrapping. I have cc'ed Denis and Prarit, who, as I understand, were working on it.
2. I think it would be useful to have a branch in CVS to (hopefully temporarily) hold our patches, so that we can build in Koji. Is it possible to get that done and provide CVS access to Lennert? Are there any issues with that?
3. What access is needed for us to do the builds under Koji?
Anything else?
Thanks Manas