[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Adoption of a package that doesn't need work (yet)

On Thu, 24 May 2007, Manuel García wrote:
> On 5/24/07, François Févotte <francois.fevotte@ensta.org> wrote:
> >Hello mentors,
> >
> >I recently filed ITAs for eukleides[1] and xeukleides[2]. However,
> >since there had been a QA upload[3] not long before, I don't have any
> >"real" work to do on the package yet.
> >
> >I'm not sure how I should actually adopt these packages. Should I make
> >a new package only modifying the maintainer field (and thus cause
> >users to upgrade the package for no visible reason)? Or should I wait
> >for a better occasion to upload an updated package (for example a new
> >upstream version or a bug fix)?
> Yeap, you should modify debian/control to change maintainer field, and
> also modify the debian/changelog (use dch :-) and change the version
> (it should be something like: xxx.xx-x and you have to add xxx.xx-x+1)
> that's all, so, you don't have to wait 'till your package need real
> work to adopt it.

There's no reason to upload unless there's a change to the package
needed, and you definetly shouldn't use version numbers like 1.2-1+1
for your upload, unless you meant 1.2-2.

That said, you should be subscribed to the PTS for the package, and
should make an upload as soon as there is something to fix, even if
it's minor.

You probably should also occasionally email the ITA indicating that
you're still going to adopt the package, and subscribe to the ITA bug
as well, so you'll receive updates to the bug.

Don Armstrong

Never underestimate the power of human stupidity.     
 -- Robert Heinlein

http://www.donarmstrong.com              http://rzlab.ucr.edu

Reply to: