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. > 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. Some files are redundant, and this package patches the Distribute control files to ensure those redundant files aren't part of the binary packages. > That's because currently, even if debian/changelog says version 3.7, > there's differences with upstream tarball which makes FTBFS, so I can't > work correctly on the packaging... 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. > 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! -- \ “Experience is that marvelous thing that enables you to | `\ recognize a mistake when you make it again.” —Franklin P. Jones | _o__) | Ben Finney <[email protected]>
signature.asc
Description: Digital signature
