Sure David,<br>I think that will be best to do.<br><br><div class="gmail_quote">On Fri, Oct 15, 2010 at 11:40 PM, David Farning <span dir="ltr"><<a href="mailto:dfarning@ubuntu.com">dfarning@ubuntu.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">> On Fri, Oct 15, 2010 at 10:04 AM, Dipankar Patro <<a href="mailto:dipankar@seeta.in">dipankar@seeta.in</a>> wrote:<br>
</div><div class="im">>> We are currently updating the git repositories at <a href="http://git.debian.org" target="_blank">git.debian.org</a><br>
>> Wish if you could clear a few doubts,<br>
>><br>
>> Steps followed for updating the repositories:<br>
>>>>><br>
>>>>> 1. Clone the repo present on <a href="http://git.debian.org" target="_blank">git.debian.org</a>.<br>
>>>>> 2. Run command uscan(check for any newer source ball)<br>
>>>>> 3. If present it downloads the new source ball<br>
>>>>> 4. Problem is that -- need command to import the new source ball into<br>
>>>>> the existing package<br>
>>>>><br>
>>>>> ishan<br>
>>>>><br>
>>>>><br>
>> I tried following the link :<br>
>> <a href="http://www.debian.org/doc/maint-guide/ch-update.en.html" target="_blank">http://www.debian.org/doc/maint-guide/ch-update.en.html</a><br>
>> (^^ 9.3 New Upstream Release.)<br>
>><br>
>><br>
>> And have the following doubt:<br>
>> - we cannot use git-import-orig in this case for updating I guess, right?<br>
>> - Shall we follow with the command ' uupdate -v newversion<br>
>> ../foo-newversion.tar.gz ' as mentioned in the link?<br>
>> - Is there anything else except for the debian/changelog we need to<br>
>> change?<br>
</div>Dipankar,<br>
<br>
I would suggest that you create a 'checklist' or 'howto' for updating<br>
sugar activities and link to it from <a href="http://wiki.debian.org/Sugar" target="_blank">http://wiki.debian.org/Sugar</a> (I<br>
think Luke did an activity packaging howto a couple of months ago...<br>
but I can never find it:(<br>
<br>
That way, reviewers can review and critique the process you use to<br>
create the packages rather then the packages them selves.<br>
<br>
It might take a little time up front, but having checklist will<br>
increase productivity down the road. Just was we have seen with code<br>
reviews, there is significant value in process reviews.<br>
<br>
Incorrect or out of date documentation just seems to propagate the<br>
same set of mistakes.... This documentation should be public, allowing<br>
Jonas, Luke, others to review it to insure that it is correct.<br>
<font color="#888888"><br>
david<br>
</font><div><div></div><div class="h5"><br>
_______________________________________________<br>
Debian-olpc-devel mailing list<br>
<a href="mailto:Debian-olpc-devel@lists.alioth.debian.org">Debian-olpc-devel@lists.alioth.debian.org</a><br>
<a href="http://lists.alioth.debian.org/mailman/listinfo/debian-olpc-devel" target="_blank">http://lists.alioth.debian.org/mailman/listinfo/debian-olpc-devel</a><br>
</div></div></blockquote></div><br>