Packages in VCS - how to indicate status on task page?
Hello, There are a few packages I once uploaded to our VCS that I know will not make it into a shape for them to be ready to be uploaded to our distribution. There are different reasons to that. Sometimes my focus has shifted away from it as a user. And at other times I found that it is too much work to e.g. get all Java dependencies into our distribution first. And there are packages for which I have just forgotten why the process has stalled. :o) And there are a few packages for which I could be motivated to complete the packaging, but would like to know if there is ongoing progress with the package by the uploader, not necessarily wanting to ask by email at an early stage screening our packages list. Should indicate how much the packaging has proceeded such that we could show that in our task list? I have recently started to mention any issues in the debian/changelog file. Would it be preferable to have anything directly stated in the package description? Or should find a debian/TODO file be shown in our task pages/linked from there? Cheers, Steffen
Re: Debian Med Badge - just like Conda has it?
Le sam. 15 sept. 2018 à 21:30, Steffen Möller a écrit : > > https://bioconda.github.io/_static/badge-generator/ Not as pretty but we have those ones: https://badges.debian.net/ Dylan
Sponsored upload: odil 0.10.0-1
Dear all, I've updated the Salsa repository of Odil to the latest upstream version (0.10.0), with the benefit of closing #914144 (boost-python is not a dependency anymore). The packages build correctly on sid, and lintian reports neither warnings nor errors. Could I get a sponsored upload for this? Cheers, -- Julien signature.asc Description: OpenPGP digital signature
Re: Packages in VCS - how to indicate status on task page?
Hi Steffen, thanks for bringing this up since it make sense if every team member follows the same (or at least as similar) strategy. On Tue, Nov 27, 2018 at 10:35:37AM +0100, Steffen Möller wrote: > There are a few packages I once uploaded to our VCS that I know will not > make it into a shape for them to be ready to be uploaded to our > distribution. There are different reasons to that. Sometimes my focus has > shifted away from it as a user. And at other times I found that it is too > much work to e.g. get all Java dependencies into our distribution first. And > there are packages for which I have just forgotten why the process has > stalled. :o) And there are a few packages for which I could be motivated to > complete the packaging, but would like to know if there is ongoing progress > with the package by the uploader, not necessarily wanting to ask by email at > an early stage screening our packages list. > > Should indicate how much the packaging has proceeded such that we could show > that in our task list? I think the best way to do so is to add a Remark field inside the tasks file. > I have recently started to mention any issues in the > debian/changelog file. This is what I do usually in d/changelog: * ... TODO: what needs to be done > Would it be preferable to have anything directly > stated in the package description? Rather not. As I said the Remark field exists and will seprately the description of the software from some packaging information. > Or should find a debian/TODO file be > shown in our task pages/linked from there? Probably also not the best idea. Just inventing another file and parsing the data is something I'd consider overkill for a resolved problem (Remark field). Kind regards Andreas. -- http://fam-tille.de
Re: Sponsored upload: odil 0.10.0-1
Hi Julien,
On Tue, Nov 27, 2018 at 12:47:00PM +0100, Julien Lamy wrote:
> Dear all,
> I've updated the Salsa repository of Odil to the latest upstream version
> (0.10.0), with the benefit of closing #914144 (boost-python is not a
> dependency anymore). The packages build correctly on sid, and lintian
> reports neither warnings nor errors.
>
> Could I get a sponsored upload for this?
Uploaded.
I did two changes:
1. In pristine-tar branch a wrong name for the new archive was
used ('v' prefix in front of version). Please make sure you
import correct name next time.
2. Spelling error in copyright (which lintian in -I mode claimed
about.
Thanks for your work on the package
Andreas.
--
http://fam-tille.de
