Hi! On 04/08/2014 02:57 PM, Mark Brown wrote: > On Tue, Apr 08, 2014 at 02:10:30PM +0200, John Paul Adrian Glaubitz wrote: > >> In particular, xemacs21 still hasn't properly made the libpng >> transition, the piuparts bug which showed xemacs21-nomule removing >> files which belong to xemacs21-support is still present and several >> other issues in the control file have to be fixed. > > Could you be more specific as to what you believe the issues in the > control file are? Is it just the hard coded architectures thing, that's > the only reported issue and there's nothing terribly obvious to > inspection?
xmeacs21 is still missing the libpng transition which is something very important you should have done with the first upload. Further things I can find: - standards version is still 3.8.4 - package still uses dpatch - debhelper version is 5 - missing Vcs-* fields - missing homepage fields Many of these issues are reflected in the lintian report [1]. Running lintian locally with "-i -E -I --pedantic" options will probably reveal even more. >> Please, for the sake of Debian's quality, re-open all bugs which >> have not been fixed or have the package removed from testing. > > There doesn't seem to be any particularly useful way of discovering what > they might be, and I rather suspect that 90% of them are just never > going to be looked at usefully anyway - there's no point in having so > many old things nobody cares about floating around and obscuring the > listings, it's a similar problem to things like KDE. There are at least two bugs which result in xemacs21 crashing or freezing [2] [3]. Do you really want people to continue using xemacs21 knowing that these issues exist? >> xemacs21 should not be released under these circumstances. > > That seems like a substantial overreaction, we only have the one RC > issue that I wasn't able to find in the closed bugs for some reason I am having trouble believing that. It took me around half an hour to dig up all these bugs. xemacs21 was accepted by the FTP team under the premise that you would take proper care of the package and addressing those issues, yet the vast majority of them are still present. > (which TBH looks to have been present for something like a decade > without anyone caring outside of explicit testing). Just because a bug has been there for a long time doesn't mean it shouldn't be fixed. We have high quality standards in Debian and I am working very hard to keep these standards up. Packages like xemacs21 which slip through the testing make us look bad. These issues are there and the bugs should therefore still be open and the high severity should prevent xemacs21 from entering testing. Adrian > [1] http://lintian.debian.org/maintainer/[email protected]#xemacs21 > [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589138 > [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542492 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - [email protected] `. `' Freie Universitaet Berlin - [email protected] `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
