Before we branch for Fedora 18, as is custom, we will block currently orphaned packages and packages that have failed to build since Fedora 16.
The following packages are currently orphaned, or fail to build. If you have a need for one of these packages, please pick them up. If no one claims any of these packages, they will be blocked before we branch for Fedora 18. We will block these packages on Monday, August 06.
Note that if you're receiving this mail directly, it's because you are a co-maintainer of one of these packages. Please work with your comaintainers to take up maintenance.
Package UnihanDb (fails to build) Package apache-commons-launcher (fails to build) Package archmage (orphan) Package autoarchive (fails to build) Package boolstuff (orphan) Package boolstuff (orphan) Package cmucl (orphan) comaintained by: green Package eboard (fails to build) Package eclipse-collabnet-merge (fails to build) Package eclipse-emf-query (fails to build) Package eclipse-emf-transaction (fails to build) Package eclipse-emf-validation (fails to build) Package eclipse-m2m-qvtoml (fails to build) Package eclipse-mdt-ocl (fails to build) Package eclipse-mdt-uml2 (fails to build) Package ext3grep (fails to build) Package ezmorph (fails to build) Package fillmore-lombard (fails to build) comaintained by: salimma Package freenx-client (fails to build) Package gant (fails to build) Package gconf-cleaner (fails to build) Package globalplatform (orphan) Package gnofract4d (orphan) comaintained by: firewing Package gnome-do-docklets (fails to build) Package gooddata-cl (fails to build) Package gpshell (orphan) Package gtkmm-utils (orphan) Package gtkmm-utils (orphan) Package hamster-applet (orphan) Package hartke-aurulent-sans-fonts (orphan) Package ibus-table-code (fails to build) Package ibus-table-others (fails to build) comaintained by: nkumar Package jpoker (fails to build) Package json (orphan) Package json-lib (fails to build) Package k12linux-quick-start-guide (orphan) Package kadu (fails to build) comaintained by: gajownik radekl Package komparator (fails to build) Package krecipes (fails to build) Package ksplice (fails to build) Package libcrystalhd (fails to build) comaintained by: kwizart Package libgdbus (fails to build) Package libgtkhotkey (orphan) Package libgtksourceviewmm (fails to build) Package libharu (fails to build) Package libhid (fails to build) Package libkml (fails to build) Package libqttracker (fails to build) comaintained by: jreznik Package libsoup22 (orphan) Package libsoup22 (orphan) Package man-pages-it (orphan) Package man-pages-ko (orphan) Package metapixel (fails to build) Package mimetic (fails to build) Package mingw-libp11 (orphan) comaintained by: rjones Package mingw-opensc (orphan) comaintained by: rjones Package mod_scgi (fails to build) Package munipack (fails to build) Package natus (fails to build) Package ntfs-config (fails to build) Package nvi (orphan) Package perl-Nagios-Plugin-Beanstalk (orphan) Package pfqueue (orphan) Package pianobooster (fails to build) Package pino (fails to build) Package pngcrush (fails to build) Package polyester (orphan) Package polyester3 (orphan) Package printoxx (fails to build) Package putty (fails to build) comaintained by: tremble Package pxe-kexec (fails to build) Package python-chm (orphan) Package python-modjkapi (fails to build) Package python-pywt (fails to build) Package python-remoteobjects (orphan) Package python-typepad (orphan) Package qalculate-kde (fails to build) Package ragel (fails to build) Package raul (fails to build) Package scite (fails to build) Package selenium-core (fails to build) Package selenium-remote-control (fails to build) Package sofsip-cli (fails to build) comaintained by: itamarjp Package specto (fails to build) Package subcommander (fails to build) Package svnkit (fails to build) Package tesseract (fails to build) Package torque (orphan) Package tritonus (orphan) comaintained by: bsjones Package typepad-motion (orphan) Package upstart (orphan) Package winwrangler (orphan) Package wmfire (fails to build) Package xaos (fails to build) Package xdrawchem (fails to build) Package xesam-glib (fails to build)
List of deps left behind by packages which are orphaned or fail to build:
Removing: freenx-client kdenetwork requires pkgconfig(nxcl) = 1.0
Removing: ksplice fedora-ksplice requires ksplice = 0.9.9-2.fc15
Removing: libgtkhotkey synapse requires libgtkhotkey.so.1
Removing: libharu EMBOSS requires libhpdf-2.1.0.so EMBOSS requires libharu-devel = 2.1.0-3.fc15 EMBOSS-libs requires libhpdf-2.1.0.so libeplplot requires libhpdf-2.1.0.so perl-PDF-Haru requires libhpdf-2.1.0.so perl-PDF-Haru requires libharu-devel = 2.1.0-3.fc15
Removing: libsoup22 libopensync-plugin-syncml requires libsoup22-devel = 2.2.105-9.fc15 libsyncml requires libsoup-2.2.so.8 libsyncml requires libsoup22-devel = 2.2.105-9.fc15
Removing: pngcrush gimp-help requires pngcrush = 1.6.10-7.fc15
Removing: printoxx fotoxx requires printoxx = 2.8.1-2.fc15
Removing: python-chm chm2pdf requires python-chm = 0.8.4-12.fc18
Removing: python-modjkapi taboot-func requires python-modjkapi = 0.1.2.28-7.fc15
Removing: python-remoteobjects django-typepad requires python-remoteobjects = 1.1-5.fc18
Removing: python-typepad django-typepad requires python-typepad = 1.1.2-5.fc18
Removing: ragel rubygem-hpricot requires ragel = 6.6-3.fc15
Removing: selenium-core perl-Test-WWW-Selenium requires selenium-core = 1.0.2-0.5.20100324svn.fc15 selenium-remote-control requires selenium-core = 1.0.2-0.5.20100324svn.fc15
Removing: selenium-remote-control perl-Alien-SeleniumRC requires selenium-server = 1.0.3-8.20100318svn.fc15
Removing: svnkit eclipse-subclipse requires eclipse-svnkit = 1.3.4-2.fc15
Removing: tesseract tucan requires tesseract = 3.00-2.fc15
Removing: torque pbstop requires torque-client = 3.0.4-1.fc17 pdsh requires torque-devel = 3.0.4-1.fc17 pdsh-mod-torque requires torque = 3.0.4-1.fc17 pdsh-mod-torque requires libtorque.so.2 perl-PBS requires libtorque.so.2 perl-PBS requires libtorque-devel = 3.0.4-1.fc17 python-pbs requires torque-devel = 3.0.4-1.fc17 python-pbs requires libtorque.so.2 python3-pbs requires libtorque.so.2
Removing: tritonus freecol requires tritonus = 0.3.7-0.13.20101108cvs.fc17 vorbisspi requires tritonus = 0.3.7-0.13.20101108cvs.fc17
Removing: upstart clamav-milter-upstart requires /sbin/initctl clamav-scanner-upstart requires /sbin/initctl dhcp-forwarder-upstart requires /sbin/initctl ip-sentinel-upstart requires /sbin/initctl milter-greylist-upstart requires /sbin/initctl tor-upstart requires /sbin/initctl
The script that generated this page can be found at https://fedorahosted.org/rel-eng/browser/scripts/find-unblocked-orphans.py There you can also report bugs and RFEs.
Bill Nottingham notting@redhat.com writes:
Before we branch for Fedora 18, as is custom, we will block currently orphaned packages and packages that have failed to build since Fedora 16.
The following packages are currently orphaned, or fail to build. If you have a need for one of these packages, please pick them up. If no one claims any of these packages, they will be blocked before we branch for Fedora 18. We will block these packages on Monday, August 06.
Note that if you're receiving this mail directly, it's because you are a co-maintainer of one of these packages. Please work with your comaintainers to take up maintenance.
still there's no orphaned iptraf
Nikola Pajkovsky (npajkovs@redhat.com) said:
Bill Nottingham notting@redhat.com writes:
Before we branch for Fedora 18, as is custom, we will block currently orphaned packages and packages that have failed to build since Fedora 16.
The following packages are currently orphaned, or fail to build. If you have a need for one of these packages, please pick them up. If no one claims any of these packages, they will be blocked before we branch for Fedora 18. We will block these packages on Monday, August 06.
Note that if you're receiving this mail directly, it's because you are a co-maintainer of one of these packages. Please work with your comaintainers to take up maintenance.
still there's no orphaned iptraf
Please follow the procedure at:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Thanks, Bill
Whoops, sorry about the reply to all (dang gmail)... I'll repost just to the devel mailing list (I canceled the original).
On Tue, Jul 31, 2012 at 12:11 PM, Bill Nottingham notting@redhat.com wrote:
Before we branch for Fedora 18, as is custom, we will block currently orphaned packages and packages that have failed to build since Fedora 16.
The following packages are currently orphaned, or fail to build. If you have a need for one of these packages, please pick them up. If no one claims any of these packages, they will be blocked before we branch for Fedora 18. We will block these packages on Monday, August 06.
Will the FTBFS packages be orphaned prior to being blocked? It would seem a grace period would be a good idea so people can pick them up if the current owner is non-responsive.
Thanks, Richard
Richard Shaw (hobbes1069@gmail.com) said:
Whoops, sorry about the reply to all (dang gmail)... I'll repost just to the devel mailing list (I canceled the original).
On Tue, Jul 31, 2012 at 12:11 PM, Bill Nottingham notting@redhat.com wrote:
Before we branch for Fedora 18, as is custom, we will block currently orphaned packages and packages that have failed to build since Fedora 16.
The following packages are currently orphaned, or fail to build. If you have a need for one of these packages, please pick them up. If no one claims any of these packages, they will be blocked before we branch for Fedora 18. We will block these packages on Monday, August 06.
Will the FTBFS packages be orphaned prior to being blocked? It would seem a grace period would be a good idea so people can pick them up if the current owner is non-responsive.
Not directly. But if you have a fix and can get a proven packager to apply and build it, they won't be blocked.
Bill
On Tue, Jul 31, 2012 at 11:11 AM, Bill Nottingham notting@redhat.com wrote:
Package gnofract4d (orphan) comaintained by: firewing
I have taken ownership of this one.
On Tue, Jul 31, 2012 at 12:11 PM, Bill Nottingham notting@redhat.com wrote:
Before we branch for Fedora 18, as is custom, we will block currently orphaned packages and packages that have failed to build since Fedora 16.
The following packages are currently orphaned, or fail to build. If you have a need for one of these packages, please pick them up. If no one claims any of these packages, they will be blocked before we branch for Fedora 18. We will block these packages on Monday, August 06.
Note that if you're receiving this mail directly, it's because you are a co-maintainer of one of these packages. Please work with your comaintainers to take up maintenance.
Package freenx-client (fails to build)
Fixed.
Package pngcrush (fails to build)
Fixed.
Package tritonus (orphan)
Taken.
-J
On Tue, Jul 31, 2012 at 2:32 PM, Jon Ciesla limburgher@gmail.com wrote:
On Tue, Jul 31, 2012 at 12:11 PM, Bill Nottingham notting@redhat.com wrote:
Before we branch for Fedora 18, as is custom, we will block currently orphaned packages and packages that have failed to build since Fedora 16.
The following packages are currently orphaned, or fail to build. If you have a need for one of these packages, please pick them up. If no one claims any of these packages, they will be blocked before we branch for Fedora 18. We will block these packages on Monday, August 06.
Note that if you're receiving this mail directly, it's because you are a co-maintainer of one of these packages. Please work with your comaintainers to take up maintenance.
Package freenx-client (fails to build)
Fixed.
Package pngcrush (fails to build)
Fixed.
Package tritonus (orphan)
Taken.
-J
Too many recipients. . .
-J
-- http://cecinestpasunefromage.wordpress.com/
in your fear, seek only peace in your fear, seek only love
-d. bowie
I'm looking into these:
Bill Nottingham wrote:
Package komparator (fails to build) Package krecipes (fails to build) Package qalculate-kde (fails to build) Package tesseract (fails to build)
but since the build.log files are no longer available, I need to run new builds first, so it's going to take a while. :-(
Are those build.log files really so large that they cannot be kept for longer? :-( It's so annoying to see those build failures and to have no idea why the builds failed.
I also really dislike the way FTBFS are handled now. In the past, bugs were filed for the build failures and they were all tracked on a tracking bug in Bugzilla, so it was always possible to see what needed fixing, and it was possible for provenpackagers to work on that in a coordinated fashion. These days, we get surprised with the failures at the last moment when they have actually been happening for 2 or 3 releases (depending on whether they would have built on F16 had there been a mass rebuild there)! We really need to track those failures in Bugzilla again.
Kevin Kofler
On Tue, Jul 31, 2012 at 9:42 PM, Kevin Kofler kevin.kofler@chello.at wrote:
I'm looking into these:
Bill Nottingham wrote:
Package komparator (fails to build) Package krecipes (fails to build) Package qalculate-kde (fails to build) Package tesseract (fails to build)
but since the build.log files are no longer available, I need to run new builds first, so it's going to take a while. :-(
Are those build.log files really so large that they cannot be kept for longer? :-( It's so annoying to see those build failures and to have no idea why the builds failed.
There's 3 per build (src,i686,x64) and they do get pretty big, just look at the size of a kernel, qt or libreoffice build.
I also really dislike the way FTBFS are handled now. In the past, bugs were filed for the build failures and they were all tracked on a tracking bug in Bugzilla, so it was always possible to see what needed fixing, and it was possible for provenpackagers to work on that in a coordinated fashion. These days, we get surprised with the failures at the last moment when they have actually been happening for 2 or 3 releases (depending on whether they would have built on F16 had there been a mass rebuild there)! We really need to track those failures in Bugzilla again.
That's being worked on as discussed in one of these threads, previously it was done by Matt Domsch with access large amounts of enterprise HW, there was a request for someone to step up to expedite the process if you have time. That said every build gets failure emails sent out so you could setup some form of rules to highlight the problem or write a script to query koji on occasion for your failed builds to email you a list of current non builds.
Peter
On 07/31/2012 02:03 PM, Peter Robinson wrote:
On Tue, Jul 31, 2012 at 9:42 PM, Kevin Kofler kevin.kofler@chello.at wrote:
Are those build.log files really so large that they cannot be kept for longer? :-( It's so annoying to see those build failures and to have no idea why the builds failed.
There's 3 per build (src,i686,x64) and they do get pretty big, just look at the size of a kernel, qt or libreoffice build.
Are they at least stored compressed?
As such logs are highly repetitive, they're ideal for compression. I tried a kernel build.log with bzip2, and it went from 3.9M to 211K. And qt is better, from 20M to 294k!
Josh
Kevin Kofler kevin.kofler@chello.at writes:
I'm looking into these: Bill Nottingham wrote:
Package komparator (fails to build) Package krecipes (fails to build) Package qalculate-kde (fails to build) Package tesseract (fails to build)
but since the build.log files are no longer available, I need to run new builds first, so it's going to take a while. :-(
The tesseract issue is documented at bz 843275.
In general, I wish people would be closing out the relevant bugs when they fix these packages ...
I also really dislike the way FTBFS are handled now.
Agreed, this shouldn't be nearly so ad-hoc. See recent threads.
regards, tom lane
Tom Lane wrote:
The tesseract issue is documented at bz 843275.
In general, I wish people would be closing out the relevant bugs when they fix these packages ...
Well, that bug was filed only a week ago, and neither the tracker nor the individual bugs were referenced in any way from the nagmail, so how was I expected to know about them?
Anyway, I closed the 4 bugs for the FTBFS issues I fixed.
Kevin Kofler
I wrote:
I'm looking into these:
Bill Nottingham wrote:
Package komparator (fails to build) Package krecipes (fails to build) Package qalculate-kde (fails to build) Package tesseract (fails to build)
I fixed these 4 packages now.
Note that krecipes and tesseract both have newer upstream versions available: * krecipes: - current in Fedora: 1.0-beta2 (kdelibs3) - current upstream: 2.0-beta2 (kdelibs4) Note that this will need significant packaging changes, being a KDE Platform 4 app now (whereas the current Fedora specfile is for the old kdelibs3 version). * tesseract: - current in Fedora: 3.00 - current upstream: 3.01 (new features, bugfixes etc.) It looks like they both could use a new (co)maintainer.
For komparator and qalculate-kde, the respective kdelibs3-based versions currently in Fedora are the latest (last?) upstream versions though. :-(
Kevin Kofler
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
El Wed, 01 Aug 2012 00:36:43 +0200 Kevin Kofler kevin.kofler@chello.at escribió:
I wrote:
I'm looking into these:
Bill Nottingham wrote:
Package komparator (fails to build) Package krecipes (fails to build) Package qalculate-kde (fails to build) Package tesseract (fails to build)
I fixed these 4 packages now.
Note that krecipes and tesseract both have newer upstream versions available:
- krecipes:
Note that this will need significant packaging changes, being a KDE Platform 4 app now (whereas the current Fedora specfile is for the old kdelibs3 version).
- current in Fedora: 1.0-beta2 (kdelibs3)
- current upstream: 2.0-beta2 (kdelibs4)
- tesseract:
- current in Fedora: 3.00
- current upstream: 3.01 (new features, bugfixes etc.)
It looks like they both could use a new (co)maintainer.
I've orphaned krecipes since i've not used it in years
Dennis
On Qua, 2012-08-01 at 00:36 +0200, Kevin Kofler wrote:
I wrote:
I'm looking into these:
Bill Nottingham wrote:
Package komparator (fails to build) Package krecipes (fails to build) Package qalculate-kde (fails to build) Package tesseract (fails to build)
I fixed these 4 packages now.
Note that krecipes and tesseract both have newer upstream versions available:
- krecipes:
Note that this will need significant packaging changes, being a KDE Platform 4 app now (whereas the current Fedora specfile is for the old kdelibs3 version).
- current in Fedora: 1.0-beta2 (kdelibs3)
- current upstream: 2.0-beta2 (kdelibs4)
- tesseract:
- current in Fedora: 3.00
- current upstream: 3.01 (new features, bugfixes etc.)
It looks like they both could use a new (co)maintainer.
For komparator and qalculate-kde, the respective kdelibs3-based versions currently in Fedora are the latest (last?) upstream versions though. :-(
Hi,
repoquery -q qalculate-kde komparator komparator-0:0.9-5.fc15.x86_64 qalculate-kde-0:0.9.7-3.fc15.x86_64
Since komparator and qalculate-kde was not rebuild in F17. Shouldn't we also update F17 ? at least.
Thanks,
On Ter, 2012-07-31 at 22:42 +0200, Kevin Kofler wrote:
I'm looking into these:
Bill Nottingham wrote:
Package komparator (fails to build)
can't resolve this fail
g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/kde -I/usr/lib64/qt-3.3/include -I. -DQT_THREAD_SUPPORT -D_REENTRANT -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -c -o kdatecombo.o kdatecombo.cpp g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/kde -I/usr/lib64/qt-3.3/include -I. -DQT_THREAD_SUPPORT -D_REENTRANT -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -c -o kfileitemext.o kfileitemext.cpp g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/kde -I/usr/lib64/qt-3.3/include -I. -DQT_THREAD_SUPPORT -D_REENTRANT -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -c -o klistviewitemdups.o klistviewitemdups.cpp g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/kde -I/usr/lib64/qt-3.3/include -I. -DQT_THREAD_SUPPORT -D_REENTRANT -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -c -o klistviewitemsingle.o klistviewitemsingle.cpp kdatecombo.cpp:17:26: fatal error: kdatecombo.moc: No such file or directory compilation terminated. make[2]: *** [kdatecombo.o] Error 1
Package krecipes (fails to build) Package qalculate-kde (fails to build) Package tesseract (fails to build)
but since the build.log files are no longer available, I need to run new builds first, so it's going to take a while. :-(
Are those build.log files really so large that they cannot be kept for longer? :-( It's so annoying to see those build failures and to have no idea why the builds failed.
I also really dislike the way FTBFS are handled now. In the past, bugs were filed for the build failures and they were all tracked on a tracking bug in Bugzilla, so it was always possible to see what needed fixing, and it was possible for provenpackagers to work on that in a coordinated fashion. These days, we get surprised with the failures at the last moment when they have actually been happening for 2 or 3 releases (depending on whether they would have built on F16 had there been a mass rebuild there)! We really need to track those failures in Bugzilla again.
Kevin Kofler
Sérgio Basto wrote:
On Ter, 2012-07-31 at 22:42 +0200, Kevin Kofler wrote:
I'm looking into these:
Bill Nottingham wrote:
Package komparator (fails to build)
can't resolve this fail
g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/kde -I/usr/lib64/qt-3.3/include -I. -DQT_THREAD_SUPPORT -D_REENTRANT -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -c -o kdatecombo.o kdatecombo.cpp g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/kde -I/usr/lib64/qt-3.3/include -I. -DQT_THREAD_SUPPORT -D_REENTRANT -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -c -o kfileitemext.o kfileitemext.cpp g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/kde -I/usr/lib64/qt-3.3/include -I. -DQT_THREAD_SUPPORT -D_REENTRANT -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -c -o klistviewitemdups.o klistviewitemdups.cpp g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/kde -I/usr/lib64/qt-3.3/include -I. -DQT_THREAD_SUPPORT -D_REENTRANT -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -c -o klistviewitemsingle.o klistviewitemsingle.cpp kdatecombo.cpp:17:26: fatal error: kdatecombo.moc: No such file or directory compilation terminated. make[2]: *** [kdatecombo.o] Error 1
My Koji Rawhide build succeeded just fine.
Kevin Kofler
----- Original Message -----
Before we branch for Fedora 18, as is custom, we will block currently orphaned packages and packages that have failed to build since Fedora 16.
The following packages are currently orphaned, or fail to build. If you have a need for one of these packages, please pick them up. If no one claims any of these packages, they will be blocked before we branch for Fedora 18. We will block these packages on Monday, August 06.
Note that if you're receiving this mail directly, it's because you are a co-maintainer of one of these packages. Please work with your comaintainers to take up maintenance.
Package libqttracker (fails to build) comaintained by: jreznik
I'm inclined to let it die but I'll take a look. It's leftover after unsuccessful MeeGo packaging efforts.
R.
The script that generated this page can be found at https://fedorahosted.org/rel-eng/browser/scripts/find-unblocked-orphans.py There you can also report bugs and RFEs.
----- Original Message -----
----- Original Message -----
Before we branch for Fedora 18, as is custom, we will block currently orphaned packages and packages that have failed to build since Fedora 16.
The following packages are currently orphaned, or fail to build. If you have a need for one of these packages, please pick them up. If no one claims any of these packages, they will be blocked before we branch for Fedora 18. We will block these packages on Monday, August 06.
Note that if you're receiving this mail directly, it's because you are a co-maintainer of one of these packages. Please work with your comaintainers to take up maintenance.
Package libqttracker (fails to build) comaintained by: jreznik
I'm inclined to let it die but I'll take a look. It's leftover after unsuccessful MeeGo packaging efforts.
Let it die in Fedora too - upstream is dead. It was part of Maemo 6, and as Nokia killed it, nobody is working anymore on it. It's needed for Qt Mobility but only on Maemo 6/MeeGo platform. No dependencies in Fedora.
R.
R.
The script that generated this page can be found at https://fedorahosted.org/rel-eng/browser/scripts/find-unblocked-orphans.py There you can also report bugs and RFEs.
-- Jaroslav Řezník jreznik@redhat.com Engineering Program Manager
Office: +420 532 294 275 Mobile: +420 602 797 774 Red Hat, Inc. http://www.redhat.com/
On 07/31/2012 10:41 PM, Bill Nottingham wrote:
Removing: libgtkhotkey synapse requires libgtkhotkey.so.1
CC'ing Michel Alexandre Salim, synapse maintainer
Ideally the synapse maintainer should own this as well but since I use synapse, I am going to take ownership of this for now to rescue synapse from being removed.
Michel, if you want to maintain it, feel free to ask.
Rahul
Bill Nottingham wrote, at 08/01/2012 02:11 AM +9:00:
Before we branch for Fedora 18, as is custom, we will block currently orphaned packages and packages that have failed to build since Fedora 16.
The following packages are currently orphaned, or fail to build. If you have a need for one of these packages, please pick them up. If no one claims any of these packages, they will be blocked before we branch for Fedora 18. We will block these packages on Monday, August 06.
Note that if you're receiving this mail directly, it's because you are a co-maintainer of one of these packages. Please work with your comaintainers to take up maintenance.
Package ragel (fails to build) Package xaos (fails to build) Package xdrawchem (fails to build)
Fixed these.
Regards, Mamoru
Le 31/07/2012 19:11, Bill Nottingham a écrit :
Package libgtksourceviewmm (fails to build)
retired, since nobody claimed it.
Package nvi (orphan)
Package torque (orphan)
Both taken and co-maintainers are very welcome !
best regards, H.
Bill Nottingham notting@redhat.com writes:
Package man-pages-ko (orphan)
I have taken ownership of this one.
Regards,
2012/7/31 Bill Nottingham notting@redhat.com:
Before we branch for Fedora 18, as is custom, we will block currently orphaned packages and packages that have failed to build since Fedora 16.
The following packages are currently orphaned, or fail to build. If you have a need for one of these packages, please pick them up. If no one claims any of these packages, they will be blocked before we branch for Fedora 18. We will block these packages on Monday, August 06.
Note that if you're receiving this mail directly, it's because you are a co-maintainer of one of these packages. Please work with your comaintainers to take up maintenance.
...
Package libcrystalhd (fails to build) comaintained by: kwizart
Hi have a fix ready for primary arches, and finally succeeded to do runtime test with the hardware. Now I cannot fix it because I'm not really a co-maintainer yet as I'm still in the 'awating review' state https://admin.fedoraproject.org/pkgdb/acls/name/libcrystalhd
The bugzilla where the FTBFS was discussed is here: https://bugzilla.redhat.com/show_bug.cgi?id=716154
What is the process I can follow to take over maintenance of the package ?
Thx
Nicolas (kwizart)
Hi,
On 08/03/2012 11:27 AM, Nicolas Chauvet wrote:
2012/7/31 Bill Nottingham notting@redhat.com:
Before we branch for Fedora 18, as is custom, we will block currently orphaned packages and packages that have failed to build since Fedora 16.
The following packages are currently orphaned, or fail to build. If you have a need for one of these packages, please pick them up. If no one claims any of these packages, they will be blocked before we branch for Fedora 18. We will block these packages on Monday, August 06.
Note that if you're receiving this mail directly, it's because you are a co-maintainer of one of these packages. Please work with your comaintainers to take up maintenance.
...
Package libcrystalhd (fails to build) comaintained by: kwizart
Hi have a fix ready for primary arches, and finally succeeded to do runtime test with the hardware. Now I cannot fix it because I'm not really a co-maintainer yet as I'm still in the 'awating review' state https://admin.fedoraproject.org/pkgdb/acls/name/libcrystalhd
The bugzilla where the FTBFS was discussed is here: https://bugzilla.redhat.com/show_bug.cgi?id=716154
What is the process I can follow to take over maintenance of the package ?
If you can send me a git format-patch formatted patch for master (*), I can use my proven packager rights to at least fix it for now, that way it won't get blocked and you save a significant amount of work to get it unblocked later.
Regards,
Hans
*) Or some other way I can make the changes without needing to think too much :)
Hi,
On 07/31/2012 07:11 PM, Bill Nottingham wrote:
Before we branch for Fedora 18, as is custom, we will block currently orphaned packages and packages that have failed to build since Fedora 16.
The following packages are currently orphaned, or fail to build. If you have a need for one of these packages, please pick them up. If no one claims any of these packages, they will be blocked before we branch for Fedora 18. We will block these packages on Monday, August 06.
Note that if you're receiving this mail directly, it's because you are a co-maintainer of one of these packages. Please work with your comaintainers to take up maintenance.
<snip>
Package libhid (fails to build)
I've fixed the FTBFS for libhid.
Regards,
Hans
Here is an updated list:
Package boolstuff (orphan) Package cmucl (orphan) comaintained by: green Package globalplatform (orphan) Package gpshell (orphan) Package gtkmm-utils (orphan) Package hamster-applet (orphan) Package hartke-aurulent-sans-fonts (orphan) Package json (orphan) Package k12linux-quick-start-guide (orphan) Package krecipes (orphan) Package libsoup22 (orphan) Package luakit (orphan) Package man-pages-it (orphan) Package mingw-libp11 (orphan) comaintained by: rjones Package mingw-opensc (orphan) comaintained by: rjones Package nzbget (orphan) Package perl-Nagios-Plugin-Beanstalk (orphan) Package pfqueue (orphan) Package polyester (orphan) Package polyester3 (orphan) Package python-chm (orphan) Package rubygem-archivist (orphan) comaintained by: vondruch jzigmund Package typepad-motion (orphan) Package upstart (orphan)
List of deps left behind by packages which are orphaned or fail to build:
Removing: libsoup22 libopensync-plugin-syncml requires libsoup22-devel = 2.2.105-9.fc15 libsyncml requires libsoup-2.2.so.8 libsyncml requires libsoup22-devel = 2.2.105-9.fc15
Removing: python-chm archmage requires python-chm = 0.8.4-12.fc18 chm2pdf requires python-chm = 0.8.4-12.fc18
Removing: upstart clamav-milter-upstart requires /sbin/initctl clamav-scanner-upstart requires /sbin/initctl dhcp-forwarder-upstart requires /sbin/initctl ip-sentinel-upstart requires /sbin/initctl milter-greylist-upstart requires /sbin/initctl tor-upstart requires /sbin/initctl
Till Maas wrote:
Package krecipes (orphan) Package man-pages-it (orphan)
I picked up these 2 because somebody needs to own them, but if anybody else is interested in maintaining or comaintaining them, I'll be glad to hand them over. (I don't really use either of those myself.)
Kevin Kofler
On 31 July 2012 18:11, Bill Nottingham notting@redhat.com wrote:
Package apache-commons-launcher (fails to build) Package eclipse-collabnet-merge (fails to build)
Fixed these two.
Package eclipse-emf-query (fails to build) Package eclipse-emf-transaction (fails to build) Package eclipse-emf-validation (fails to build) Package eclipse-m2m-qvtoml (fails to build) Package eclipse-mdt-ocl (fails to build) Package eclipse-mdt-uml2 (fails to build)
Working on these...
Something with "[ACTION REQUIRED] [FINAL NOTICE]" in the subject line should probably go to devel-announce list.
Best regards, Christoph