-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 10/11/2013 07:00 AM, Ben Finney wrote: > On 10-Oct-2013, Thomas Goirand wrote: >> FYI, I'm currently working on the package. I'm having a hard time with >> bzr, though... > > I'd be happy to help with this. Either in this bug report conversation, or > one-to-one with you.
It's ok, I'm now using git-remote-bzr from /usr/share/doc/git/contrib/remote-helpers/, which works damned well! :) >> Just one thing that would help me a lot: could you please add what I >> attached to the debian/rules to generate a dfsg orig file, run it, and >> then put the generated content instead of what is currently in the BZR >> repository? > > The upstream source isn't in the packaging VCS repository at all. The > packaging is applied on top of upstream's released tarball, with patches > applied from ‘debian/patches/’. > > For this, I use ‘bzr-buildpackage --source --merge’, which builds a Debian > source package from the pristine upstream tarball and the Debian changes. > > There's no need to re-package the upstream tarball, since its contents are > all DFSG-free already. I don't agree with this view, and neither does the FTP masters. If you look closely in the attachment of the email I sent to debian-python@l.d.o, you will see that my debian/rules target is deleting some minimized javascripts. These are considered non-free in Debian. > Some files are redundant, and this package patches > the Distribute control files to ensure those redundant files aren't part of > the binary packages. Sure, and that's good, but that's not enough. The minified javascripts really need to go away. > What differences are you seeing? The upstream files are not part of the > packaging repository, since (apart from VCS control files) that repository > contains *only* the ‘debian/’ subdirectory. I can see that now that I use git-remote-bzr. In fact, I think I got the old tarball unpacked when using debcheckout. Sorry for that. >> Then when done, I'll be able to test it more, and see if I can sponsor >> it. I'll be very happy if we can tackle this one package which I need to >> be ready for next week. > > Me too, and thank you for your work to move this along! I'll let you know when I'm satisfied with my changes! :) Cheers, Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBCAAGBQJSV1x9AAoJENQWrRWsa0P+okoP+QHqwyDk4g2aQKQyRPegHfYR IIlOg2HMz3KdwGnQZhL8W5kYesfSaMw6EzsbplAAE2WiH2quh7dULfpnKw1dUfPb Zfht+RZxsIapeRv49x8wcxVCmWNoAHuB6kyogkv9CH5zqgEVtldWIZYh5ExgUViH Q3eq11hLFI9ppdpR5XrORi6L7fuIZE/rMSRBN+uTo/IzZBH/+h4tRUPznCc4NQlj 6XB9LKYVa+ub+WfprFvWF11SLdp+az61jUHQ/IgL/5rAgvi0F/Uq8eQu9ICjxzGv QSq081mAwSIVGEICxxhzyIScvCe6/x332e7zTWtjduwZq+RxCycNI40O9xhYnoq0 dimwn2tuthB3yjkSCg1rYO+bz1N+SSeQCsDPlBr7QzusKevbpXnKkEgNh+cur8p+ +1OHEkd7gB0WjTkGaiuQN8LSGe3vAC59JH59pC3Q50gbqyPrnKYHmFRDGhTZjT3t gGwuz9/AKqTfKdMLIaCDRh2pCulc2arYbTIGvWSuqGsBTAnMjrewRM/CVBAv78Wm 7rIHyTA5QUfcwLNqIma8QyNxjVT++0hPBqTPxJ2VYu5GxEJX9bmJMqIuto0OsEsV y/UljWh4lR46bZY7BumfC2AFns7Tewuz1XA6W++slmrjwTLg6X20jhoSwAj9hCeP xmS22K7Qx/euvuTYSS6R =B9tm -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
