[arch-dev-public] pending devtools issues

[Eric Belanger]

On Thu, 4 Oct 2007, Aaron Griffin wrote:

> On 10/4/07, Andreas Radke <a.radke at arcor.de> wrote:
>> extrapkg issue:
>>
>> [andyrtr at workstation64 icu]$ extrapkg -l 60
>> andyrtr at gerolde.archlinux.org's password:
>> icu-3.8-1-x86_64.pkg.tar.gz                                100% 6684KB   7.4KB/s   15:00
>> andyrtr at gerolde.archlinux.org's password:
>> File integrity okay.
>> ===> Uploaded /home/daten/arch64/packages/testing/icu-3.8-1-x86_64.pkg.tar.gz
>> cvs commit: Examining .
>> andyrtr at cvs.archlinux.org's password:
>> cvs commit: Up-to-date check failed for `PKGBUILD'
>> cvs [commit aborted]: correct above errors first!
>> Cancelled
>> [andyrtr at workstation64 icu]$
>>
>>
>>
>> The speedlimit worked well. but it seems to break the -m comment for cvs commit.
>
> That error looks more like the commit failed. The -m argument is for
> the commit message, this error is different. It means there's a
> conflict in CVS.
>
> cvs commit: Up-to-date check failed for `PKGBUILD'
> cvs [commit aborted]: correct above errors first!
>
>
>> Beside that i have a big problem with the strict order to first upload
>> the package and then commit/tag it.
>> OpenOffice.org needs me 4 hours to upload. When I will not sit in front of the pc
>> when it comes to commit/tag the server will reject me due to a timeout. Any idea
>> if/how this can be solved?
>
> Well, we could do it in reverse, I don't see a big problem with
> that... anyone else?
>

That can be solved by using ssh keys. If you also use keygen, you just 
need to enter your passphrase ounce per session and it won't ask for any password 
afterwards.  I find it much more convenient too.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.