On Mon, Feb 6, 2012 at 3:09 PM, Bill Nottingham<notting(a)redhat.com> wrote: > As stated eariler, the following packages have been retired in F-17 (and > therefore rawhide), due to either failing to build, or not having maintainers. > > ... > junit4 > ... Whoa there.. .this one wasn't in any of the previous emails... perhaps it was orphaned very recently? It's a BuildReq for most of the java universe, so probably best to give people one more shot at claiming it, if possible.

As stated eariler, the following packages have been retired in F-17 (and therefore rawhide), due to either failing to build, or not having maintainers. adaptx ario asa autodafe avant-window-navigator avl awn-extras-applets bit blam camstream ccsm compiz compiz-bcop compizconfig-backend-gconf compizconfig-backend-kconfig4 compizconfig-python compiz-fusion-extras compiz-fusion-unsupported compiz-manager conexus dbus-cxx eazykeyboard eclipse-setools eclipse-slide erlang-erlzmq2 expatmm gestikk gget gimpfx-foundry gkrellm-volume gnome-paint gnubversion gpx-viewer higlayout intellij-idea intuitively invulgotracker itaka itools iwak iwidgets jps junit4 kcirbshooter libcompizconfig libdesktop-agnostic libmetalink libnoise libspe2 libsx lifeograph log4c lush maradns mathmap maxr mediawiki-rss memchan metalink mingw32-OpenSceneGraph mingw32-plib mod_perlite monsoon mtkbabel mulk nanoxml ndoutils netbeans netstiff openbios papyrus phpTodo picocontainer pinot plpa podcatcher puritan pyactivemq pyevent pymssql pypar2 python-assets python-elixir python-text_table python-wehjit python-ZSI quadkonsole quotatool rainbow rudecgi rudeconfig snacc specspo spr spu-binutils stgit systemtapguiserver tbcload tclchecker tclcompiler tcldebugger tclhttpd tclparser tclpro tclsoap tcl-thread tkcon tktable tomcat5 transbot ugene vim-perl-tt2 wordtrans xcftools xmldb-api xmlrpc-epi Have a nice day. Bill -- devel mailing list devel(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel

On Sun, Mar 04, 2012 at 17:46:45 +0000, Peter Robinson <pbrobinson(a)gmail.com&gt; wrote: > freetennis-0.4.8-18.fc12 Note that freetennis is waiting on a review of ocaml-calimages. I have tested rebuilding freetennis against my local copy of ocaml-calimages and it worked. I have traded some package maintenance tasks with Hans for getting a review of ocaml-calimages and it will probably be done in a couple of weeks.

On Mon, Mar 05, 2012 at 13:03:09 +0000, "Richard W.M. Jones" <rjones(a)redhat.com&gt; wrote: > > ocaml-camlimages? I've kicked this package out of Fedora because > camlimages has a dead upstream *and* a lengthy history of security > bugs. It contains old C code pasted from various places, and really > shouldn't be used. The right way to do this is to use OCaml bindings > for libpng, libungif etc. (Debian even did some of this work, but > didn't contribute anything back upstream ...) There has been an update since the package was removed. I don't see a lot happening now, but at some time between when it was dropped and now there was activity. (It went from 3.0.2 to 4.0.1.)

On Sun, Mar 04, 2012 at 05:26:02PM -0600, Bruno Wolff III wrote: > On Sun, Mar 04, 2012 at 17:46:45 +0000, >   Peter Robinson <pbrobinson(a)gmail.com&gt; wrote: > > freetennis-0.4.8-18.fc12 > > Note that freetennis is waiting on a review of ocaml-calimages. I have tested > rebuilding freetennis against my local copy of ocaml-calimages and it > worked. > > I have traded some package maintenance tasks with Hans for getting a review > of ocaml-calimages and it will probably be done in a couple of weeks. ocaml-camlimages?  I've kicked this package out of Fedora because camlimages has a dead upstream *and* a lengthy history of security bugs.  It contains old C code pasted from various places, and really shouldn't be used.  The right way to do this is to use OCaml bindings for libpng, libungif etc.  (Debian even did some of this work, but didn't contribute anything back upstream ...) See my previous posting on this subject: https://lists.fedoraproject.org/pipermail/devel/2009-October/039597.html Freetennis has a long, long dead upstream (like 5+ years), and I was fairly certain that I had made it 'dead.package' in the past too, but checking it now, I didn't.  I suggest killing it too.

On Sun, Mar 04, 2012 at 17:46:45 +0000, Peter Robinson <pbrobinson(a)gmail.com&gt; wrote: > leonidas-backgrounds-11.0.0-2.fc12 This one just had an extra newline in the sources file and I have started new builds for f17 and f18. I push the f17 build to testing when they are done.

Since this is only a build issue, I don't think it is worth pushing out updates for F15 or F16.

Peter Robinson (pbrobinson(a)gmail.com) said: > It was my understanding that packages that are FTBFS prior to F-15 (ie > not had a successful build in F-15 or later) It's done off the F15FTBFS bug. If these don't have bugs blocking that, they won't get picked up.

On Mon, Mar 05, 2012 at 06:36:23PM +0000, Peter Robinson wrote: > On Mon, Mar 5, 2012 at 4:13 PM, Bill Nottingham <notting(a)redhat.com&gt; wrote: > > Peter Robinson (pbrobinson(a)gmail.com) said: > >> It was my understanding that packages that are FTBFS prior to F-15 (ie > >> not had a successful build in F-15 or later) > > > > It's done off the F15FTBFS bug. If these don't have bugs blocking that, > > they won't get picked up. > > Right, I did that from koji, not sure how the ftbfs bug was done. At least for aircrack-ng from your list no FTBFS bug has been filed, therefore I do not see any reason to remove it from Fedora. And in case it really does not build, I expect a bug report.

Peter Robinson (pbrobinson(a)gmail.com) said: > > At least for aircrack-ng from your list no FTBFS bug has been filed, > > therefore I do not see any reason to remove it from Fedora. And in case > > it really does not build, I expect a bug report. > > There hasn't been FTBFS bug reports since Matt stopped doing them due > to lack of time, the maintainer would have got failed builds for the > mass rebuild and should have investigated as part of "maintaining" the > package. If there aren't FTBFS bug reports in the future, that's going to make doing FTBFS-blocking tricky. Did you generate your list merely from "things with older dist tags, so they obviously didn't rebuild", or from some more canonical source?

There hasn't been FTBFS bug reports since Matt stopped doing them due to lack of time, the maintainer would have got failed builds for the mass rebuild and should have investigated as part of "maintaining" the package.

From what I understand from this thread and the wiki, it does not all