[Debian-olpc-devel] updating package

[David Farning]

> On Fri, Oct 15, 2010 at 10:04 AM, Dipankar Patro <dipankar at seeta.in> wrote:
>> We are currently updating the git repositories at git.debian.org
>> Wish if you could clear a few doubts,
>>
>> Steps followed for updating the repositories:
>>>>>
>>>>> 1. Clone the repo present on git.debian.org.
>>>>> 2. Run command uscan(check for any newer source ball)
>>>>> 3. If present it downloads the new source ball
>>>>> 4. Problem is that -- need command to import the new source ball into
>>>>> the existing package
>>>>>
>>>>> ishan
>>>>>
>>>>>
>> I tried following the link :
>> http://www.debian.org/doc/maint-guide/ch-update.en.html
>> (^^ 9.3 New Upstream Release.)
>>
>>
>> And have the following doubt:
>> - we cannot use git-import-orig in this case for updating I guess, right?
>> - Shall we follow with the command ' uupdate -v newversion
>> ../foo-newversion.tar.gz  ' as mentioned in the link?
>> - Is there anything else except for the debian/changelog we need to
>> change?
Dipankar,

I would suggest that you create a 'checklist' or 'howto' for updating
sugar activities and link to it from http://wiki.debian.org/Sugar (I
think Luke did an activity packaging howto a couple of months ago...
but I can never find it:(

That way, reviewers can review and critique the process you use to
create the packages rather then the packages them selves.

It might take a little time up front, but having checklist will
increase productivity down the road.  Just was we have seen with code
reviews, there is significant value in process reviews.

Incorrect or out of date documentation just seems to propagate the
same set of mistakes.... This documentation should be public, allowing
Jonas, Luke, others to review it to insure that it is correct.

david