|
»
Orphaning my packages...
|
View:
New views
6 Messages
—
Rating Filter:
Alert me
|
 |
Orphaning my packages...
by Kevin B. McCarty-3
::
Rate this Message:
Hi all,
I unfortunately don't have the free time at the moment to do much for the Debian Project, so I'm orphaning my packages. If anyone wants to stake a claim to any of the following, please go ahead and say so, otherwise I'll file the orphaning bugs within a couple days. (Follow-ups set to debian-devel.) Cernlib-related (Cernlib is a huge, mostly obsolete set of physics libraries and tools) packages. These all have corresponding wnpp ITO bugs that can be changed to ITA / closed as desired. Note, Francois Niedercorn (in CC) has first dibs on these if he wants them. Francois, if you still do, please reply to debian-devel. cernlib - #508413 cfortran - #508500 geant321 - #508496 mclibs - #508498 mn-fit - #508501 paw - #508495 Other packages: feynmf viewglob best regards, -- Kevin B. McCarty <kmccarty@...> WWW: http://www.starplot.org/ WWW: http://people.debian.org/~kmccarty/ GPG: public key ID 4F83C751 |
|
|
|
|
|
Re: Orphaning my packages...
by Andreas Tille-5
::
Rate this Message:
On Wed, Sep 30, 2009 at 12:04:16PM +0200, francois.niedercorn2@... wrote:
> Yes, I'm (I hope) ready to take over the packages. I'm interested (if > possible) in team maintainership under the umbrella of the Debian > Science team. Because I still feel I will need guidance. You might like to read Debian Science policy manual. [1] > Now, the first step I've to do is to answer every of these bug reports > (cernlib - #508413, cfortran - #508500,geant321 - #508496, mclibs - > #508498, mn-fit - #508501, paw - #508495) by changing the subject with > ITA, am I right ? Yes. > For the second step : "upload the packages with my name in its > Maintainer: field, I'd rather suggest: Maintainer: Debian Science Team <debian-science-maintainers@...> Uploaders: <your name> to put it effectively under group maintenance. > and put something like | * New maintainer (Closes: > #bugnumber) | in the changelog of the package in order to automatically > close this bug once the package has been installed." Yes. > I can't upload the > packages, so I need to ask to debian-mentors-list (or debian-science) to > find a sponsor for the upload, is this correct ? Yes. In this case I would also strongly recommend: DM-Upload-Allowed: yes to enable you upload permissions once you become a Debian Maintainer. > But I don't know the procedure for a comaintainership package, or for a > team maintainership, if somebody can explain me the extra steps ? See above. Use the Debian Science SVN or Git (at your preference) to store the packaging stuff (as described in policy[1]). > I also need to correct outstanding bugs affecting the packages. > > bug #348065 affecting cernlib is not yet > corrected (I've basically no experience on bsd, I can't give it a try > now, but as the severity is "wishlist" perhaps I didn't have to correct > it before uploading cernlib ?) Even if also wishlist bugs should be fixed in the future there is no need to fix all bugs in the first run. Just declaring the new maintainership and fixing the more burning bugs would be a reasonable aproach. > bug#374978 affecting paw seems to be > corrected, so I've basically nothing to do (?) Make sure that it gets close din your upload (I havn't looked at the bug - perhaps this advise is nonsense). > bug #507429 affecting cfortran didn't > seem to be corrected (yes ?), but I could apply the correction that is > suggested in the last mail. Sounds reasonable to apply any patch and test whether it fixes the problem (I havn't looked at the bug as well - just guessing from your question). > bug #249483 affecting cfortran, it is a > wishlist also. There is no shame in ignoring it for now and working on it later. > Thanks a lot in advance, Hope this helps Andreas. [1] http://debian-science.alioth.debian.org/debian-science-policy.html -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-science-request@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
"DM-Upload-Allowed: yes" on first uploads
by David Bremner-4
::
Rate this Message:
At Wed, 30 Sep 2009 13:22:22 +0200, Andreas Tille wrote: > > I can't upload the packages, so I need to ask to > > debian-mentors-list (or debian-science) to find a sponsor for the > > upload, is this correct ? > > Yes. In this case I would also strongly recommend: > > DM-Upload-Allowed: yes > > to enable you upload permissions once you become a Debian Maintainer. Just for information, that might not be so well received on -mentors. See for example, http://lists.debian.org/debian-mentors/2009/06/msg00232.html and others in the same thread. Cheers, d -- To UNSUBSCRIBE, email to debian-science-request@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
Re: Orphaning my packages...
by Kevin B. McCarty-3
::
Rate this Message:
Hi Francois,
On Wed, Sep 30, 2009 at 3:04 AM, francois.niedercorn2@... <francois.niedercorn2@...> wrote: > Now, the first step I've to do is to answer every of these bug reports > (cernlib - #508413, cfortran - #508500,geant321 - #508496, mclibs - > #508498, mn-fit - #508501, paw - #508495) by changing the subject with > ITA, am I right ? Yes. (By the way, if you don't use all of those packages, you aren't obligated to adopt every single one! I know that mn-fit and mclibs, at least, have really low popcon numbers, so if you don't have any use for them, feel free to leave them orphaned.) > For the second step : "upload the packages with my name in its > Maintainer: field, and put something like | * New maintainer (Closes: > #bugnumber) | in the changelog of the package in order to automatically > close this bug once the package has been installed." I can't upload the > packages, so I need to ask to debian-mentors-list (or debian-science) to > find a sponsor for the upload, is this correct ? Yes. However, take note that some of the source packages are quite large, and it is a little hard on the buildd machines to make a new upload solely for the purpose of changing the maintainer name/email. I'd suggest also doing at least some cleanup of Lintian warnings prior to a new upload. (But really, you're free to do whatever you like as long as someone will sponsor it :-) > But I don't know the procedure for a comaintainership package, or for a > team maintainership, if somebody can explain me the extra steps ? > > I also need to correct outstanding bugs affecting the packages. It's perfectly OK to take over packages and make a new upload without fixing every outstanding bug ... some bugs are hard or impossible to fix, while some are wishlist and not really necessary to implement. (Bugs in both those categories are often best pushed upstream, except that none of these packages really have an active upstream anymore.) > bug #348065 affecting cernlib is not yet > corrected (I've basically no experience on bsd, I can't give it a try > now, but as the severity is "wishlist" perhaps I didn't have to correct > it before uploading cernlib ?) This is likely one of those "hard or impossible" bugs except maybe for an Imake / BSD expert. > bug#374978 affecting paw seems to be > corrected, so I've basically nothing to do (?) It's been corrected at least for the immediate problem that was initially reported ... in my opinion the cause of this symptom is a bug itself, but it's a systemic bug in the architecture of Paw that would be very difficult to fix. So I agree that there isn't much to be done here... maybe either leave the bug open and tag "wontfix", or just close it. > bug #507429 affecting cfortran didn't > seem to be corrected (yes ?), but I could apply the correction that is > suggested in the last mail. Please feel free. > bug #249483 affecting cfortran, it is a > wishlist also. Right, it was something I didn't feel I had the wherewithal to tackle. > For bug #497023 (affecting cfortran) I > think it may be corrected... Right, although before uploading a cfortran package that fixes this, it would be good to make sure that all the dependent packages still build. Finally, just wanted to double-check that you saw my other email to debian-science at http://lists.debian.org/debian-science/2009/09/msg00066.html in case you also wanted to adopt the "Cernlib on Debian" web pages. best regards, -- Kevin B. McCarty <kmccarty@...> WWW: http://www.starplot.org/ WWW: http://people.debian.org/~kmccarty/ GPG: public key ID 4F83C751 -- To UNSUBSCRIBE, email to debian-science-request@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
Re: "DM-Upload-Allowed: yes" on first uploads
by Charles Plessy-12
::
Rate this Message:
Le Wed, Sep 30, 2009 at 11:38:16AM -0300, David Bremner a écrit :
> At Wed, 30 Sep 2009 13:22:22 +0200, > Andreas Tille wrote: > > Yes. In this case I would also strongly recommend: > > > > DM-Upload-Allowed: yes > > > > to enable you upload permissions once you become a Debian Maintainer. > > Just for information, that might not be so well received on -mentors. > > See for example, > http://lists.debian.org/debian-mentors/2009/06/msg00232.html and > others in the same thread. Hi David, I think that there are multiple ways to regulate DM upload: - The package is DM-Upload-Allowed: yes, but the DM is not yet uploader, - The DM is uploader but the package is not yet DM-Upload-Allowed: yes. - The pakage is DM-Upload-Allowed: yes, the maintainer is uploader, but not DM. In all these three scenarios, the DM will not get upload rights by accident. People on -mentors tend to be more conservative because they are worried that once upload rights are given, the maintainer will isolate and not seek advices anmore, but in the case of our team-maintained package, there is much more control, and many pairs of eyes can see on the commit mailing lists if something wrong is happening. Have a nice day, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-science-request@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
signature.asc (268 bytes) 
| Free embeddable forum powered by Nabble | Forum Help |
