I rejected titantools with a message saying that because of a bug in dak, we are unable to easily handle non-sourceful uploads that move a package from main to non-free. As we are bogged down with other stuff, the quickest way to get titantools through new is going to be making a sourceful upload.
My suggestion is to build with the same .orig.tar.gz but with an artificial version bump in order to make it appear to be a new upstream version. so perhaps 4.0.11+notdfsg0 or something (creating a 4.0.11+notdfsg0-1 debian version). Sorry for the inconvenience. stew On Wed, 22 Sep 2010 17:55:50 +0200, "Didier 'OdyX' Raboud" <did...@raboud.com> wrote: > tags 584383 -pending > thanks > > Hi dear titantools maintainers, > > From what I could gather from the "NEW" log, it seems that there was "once" a > "titantools 4.0.11-7" in NEW, that was supposed to fix this RC bug: > > * Makefile.linux: Do not build noshell as a static binary as this > does not gain anything and leads to a FTBFS in amd64 (Closes: 584383) > > My RSS tells me that "titantools 4.0.11-7 left NEW" on 04.09.2010 02:00, but > I > can't get a trace of that anywhere on the packages.qa.d.o, on the buildd or > on > the archive (CC'ing ftpmaster to get a enlightening on that). > > So #584383 is still to be fixed. > > Cheers, OdyX > -- > Didier Raboud, proud Debian Maintainer (DM). > CH-1020 Renens > did...@raboud.com -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
