Your message dated Tue, 8 Apr 2008 21:33:10 +0100 with message-id <[EMAIL PROTECTED]> and subject line Re: Bug#474615: libgtkol: contains binaries without source code has caused the Debian Bug report #474615, regarding libgtkol: contains binaries without source code to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 474615: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=474615 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems
--- Begin Message --------BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Package: libgtkol Version: 1.4.1 Severity: serious Justification: Policy 2.1, 2.2.1 libgtkol's upstream tarball contains several copies of a binary "xml-reader", md5sum d1c995b3108329099b1976592979785c, which does not appear to come with source code. This is a violation of the DFSG, and probably not legally distributable either (since the package is under the GPL). The upstream tarball also contains: - - config.guess, config.sub, COPYING and ltmain.sh as symlinks instead of plain files - - an assortment of files that should be generated at build time: config.h, config.log, config.status, libgtkol-1.4.pc, Makefile, stamp-h1 It appears that the upstream has just run "make clean" on a build tree and tarred up the result, rather than using "make dist" or (better) "make distcheck". Rather than just stripping the xml-reader binaries from the tarball, it would probably be a good idea to make the replacement tarball using "make dist" or "make distcheck", to make it easier (probably, trivial) to fix #442637 (which is the reason I was looking at this package in the first place). Regards, Simon - -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (101, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -----BEGIN PGP SIGNATURE----- iD8DBQFH+R07WSc8zVUw7HYRAk1iAJ4u5ei6DTlbz2g+hj1pSBHufkJVEgCg5dsI o3Ur19bMRD2iJp9w1QZapmg= =G3xK -----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message --------BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Version: 1.4.1+dfsg1-1 ^ seems you forgot to close the bug in your upload, so, doing that On Mon, 07 Apr 2008 at 10:21:25 +0200, Jonas Smedegaard wrote: > On Sun, Apr 06, 2008 at 10:15:37PM +0100, Simon McVittie wrote: > >I'm in collab-maint already (I have a package in bzr there), but to be > >honest my only interest in libgtkol is that it had a release-goal bug > >that looked easy! I didn't realise at that point that I'd be filing and > >fixing an RC bug as a result... > > Ahh - then you could've just applied your patch directly through SVN. > Why didn't you - especially now after I shoed positive interest in your > work? Committing to the VCS of a package I have no particular involvement or interest in, without any patch review from the maintainer who knows how it works, seemed rather rude (perhaps this is an attitude I've picked up from work, where for QA reasons even the main maintainer for a package doesn't make non-trivial merges to HEAD without someone else reviewing the branch). In collab-maint, in particular, commit access is given out more or less indiscriminately (as a non-DD, I got it by asking if I could put my package there) so just because I'm in the collab-maint group doesn't seem to me to be enough "excuse" to commit to other people's repositories. Perhaps I should have committed my NMU to a branch for your consideration, but svn branches are annoying :-) Anyway. One less release-goal bug, one less RC bug, thanks for your help! Regards, Simon -----BEGIN PGP SIGNATURE----- iD8DBQFH+9aGWSc8zVUw7HYRAqmiAJ9TRA2rZixh/WoBjkq433eAc1O9IQCaA/ll UVoDCkinbC7XJcNWn3O0grA= =vspQ -----END PGP SIGNATURE-----
--- End Message ---
