[arch-dev-public] pending devtools issues

Aaron Griffin aaronmgriffin at gmail.com
Thu Oct 4 17:28:07 EDT 2007


On 10/4/07, Jason Chu <jason at archlinux.org> wrote:
> On Thu, Oct 04, 2007 at 02:49:16PM -0500, 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?
>
> I didn't want to commit (mostly tag) until after the package was available
> on the server.  Once a package has been tagged, we'll start seeing errors
> because it's not in the staging dir when you run db-extra.
>
> We could still commit first, but you'd probably run into the same timeout
> issue if we just tag though.

Yeah, I was afraid there was something I was forgetting.

In all honesty, I think Eric's solution is the best here.

We're uploading/committing in a certain order because it's the proper
way, but the issue here is specific to your machine, so we should
solve this on your machine.

Would someone mind writing up a quick HOWTO in the dev wiki for using
ssh keys on gerolde - for those that haven't done it yet?




More information about the arch-dev-public mailing list