Re: Scythe in Debian Med Git
Hi Kevin, please note that I'm forwarding my answer to the list. I would always advise to send questions like yours to the list since it enhances your chances to get an answer more quickly. Please always remember that Debian Med is a team and not a single person. On Mon, May 11, 2015 at 02:11:41PM +1000, Kevin Murray wrote: To build a Debian package you need a *.orig.tar.gz. *That* is what you should import as pristine-tar. It would be great if you can get this from upstream. If not please provide a get-orig-source target to create such a tarball and import it as pristine-tar. I've added a get-orig-source rule to d/rules, which wgets a tarball using the github API. This tarball is specific to the git SHA hash of upstream's current master, which defined version 0.994 (i.e., will always download the same content, even if upstream's master changes). I hope this is acceptable. As a temporary solution until upstream might be convinced to do proper releases this is OK. It also serves for others as documentation how we obtained the tarball. Do I need to add wget as a build-dependency? And/or use cURL instead? No extra Build-Dependency needed since it is not needed to actually build the package. To the package itself: I did a couple of minor changes and commited these. It would have been more work to describe what you should do than doing it quickly myself. Please check the log thoroughly. There is one remaining issue: You are creating the manpage at build time but the result is quite poor regarding line spacing etc. It also adds a ruby build-dependency. Could you please preprocess the manpage and commit it right to the debian/ dir after checking that the syntax is OK? Kind regards and thanks for your work on this Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150511061825.ga17...@an3as.eu
Re: Scythe in Debian Med Git
Hi Kevin, thanks for your quick reply. On Mon, May 11, 2015 at 05:26:33PM +1000, Kevin Murray wrote: As a temporary solution until upstream might be convinced to do proper releases this is OK. It also serves for others as documentation how we obtained the tarball. OK, I'll leave it as is until Vince gets back to me about tagging a released version. That's fine. To the package itself: I did a couple of minor changes and commited these. It would have been more work to describe what you should do than doing it quickly myself. Please check the log thoroughly. There is one remaining issue: You are creating the manpage at build time but the result is quite poor regarding line spacing etc. It also adds a ruby build-dependency. Could you please preprocess the manpage and commit it right to the debian/ dir after checking that the syntax is OK? OK, I have made a new and improved d/scythe.1 and removed the ronn-based system (including from build-depends, and d/rules). I'll check this out and will probably upload soon. Is it worth doing something similar with the README.html which we now generate, to avoid a build-dep on python-markdown? The problem was not only the extra build dependency but also the poor result we get from it. So I think it is OK as it is now. Thanks again for your work on this Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150511073359.gb17...@an3as.eu
Re: Scythe in Debian Med Git
Hi Andreas, On 08:18 11/05, Andreas Tille wrote: Hi Kevin, please note that I'm forwarding my answer to the list. I would always advise to send questions like yours to the list since it enhances your chances to get an answer more quickly. Please always remember that Debian Med is a team and not a single person. Apologies, I absent-mindedly replied to you personally again. I'll endeavour to group-reply in future. snip I've added a get-orig-source rule to d/rules, which wgets a tarball using the github API. This tarball is specific to the git SHA hash of upstream's current master, which defined version 0.994 (i.e., will always download the same content, even if upstream's master changes). I hope this is acceptable. As a temporary solution until upstream might be convinced to do proper releases this is OK. It also serves for others as documentation how we obtained the tarball. OK, I'll leave it as is until Vince gets back to me about tagging a released version. snip To the package itself: I did a couple of minor changes and commited these. It would have been more work to describe what you should do than doing it quickly myself. Please check the log thoroughly. There is one remaining issue: You are creating the manpage at build time but the result is quite poor regarding line spacing etc. It also adds a ruby build-dependency. Could you please preprocess the manpage and commit it right to the debian/ dir after checking that the syntax is OK? OK, I have made a new and improved d/scythe.1 and removed the ronn-based system (including from build-depends, and d/rules). Is it worth doing something similar with the README.html which we now generate, to avoid a build-dep on python-markdown? Cheers, Kevin --- Kevin Murray GPG pubkey: http://www.kdmurray.id.au/static/A4B4EE6A.asc FPR: 656C 0632 1EAB 2C3F 3837 9767 17C2 8EB1 A4B4 EE6A -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150511072633.ga2...@klaptop.kdmurray.id.au
Re: Scythe in Debian Med Git
Hi Kevin, On Sun, May 10, 2015 at 09:00:06PM +1000, Kevin Murray wrote: thanks for commiting scythe to Git. Could you please commit also a pristine-tar branch? Feel free to ask for details if you have no idea what I'm talking about. I've contacted upstream (Vince Buffalo) about tagging a release and pushing the tag to GitHub. My understanding is that this is a prerequisite of making a pristine-tar branch. As i understand it, I then add the contents of that tarball to an entirely new branch? Or can I simply point the branch 'pristine-tar' at the exact commit of the tag and hence tarball (having imported the git tree into the Debian repository)? I'm still a little confused about the process, given that the upstream source is in the form of a git repository. To build a Debian package you need a *.orig.tar.gz. *That* is what you should import as pristine-tar. It would be great if you can get this from upstream. If not please provide a get-orig-source target to create such a tarball and import it as pristine-tar. Hope this helps Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150510175017.ga2...@an3as.eu
