I'm getting this all of a sudden:
:; cd linux-2.4
:; bk parent
Parent repository is bk://linux.bkbits.net/linux-2.4
:; bk pull
---------------------- Receiving the following csets -----------------------
1.652 1.651 1.650 1.649 1.648
----------------------------------------------------------------------------
ChangeSet fnext: No such file or directory
=================================== ERROR ====================================
takepatch: missing checksum line in patch, aborting.
==============================================================================
666 bytes uncompressed to 1222, 1.83X expansion
:; cd ../linux-2.5
:; bk parent
Parent repository is bk://linux.bkbits.net/linux-2.5
:; bk pull
---------------------- Receiving the following csets -----------------------
1.684 1.683 1.681.1.1 1.682 1.681 1.680 1.679 1.678 1.677
1.676 1.675 1.674 1.673 1.672 1.671 1.670 1.669 1.668 1.667
1.666
----------------------------------------------------------------------------
ChangeSet fnext: No such file or directory
=================================== ERROR ====================================
takepatch: missing checksum line in patch, aborting.
==============================================================================
344 bytes uncompressed to 710, 2.06X expansion
Is this a bkbits issue or something wrong on my side?
-JimC
I get this error, too. I then rm -rf the repository and did a fresh clone
from bkbits which went fine. I was also able to successfully pull from the
new local repository to another local repository. But trying to push back
to bkbits gave me an error:
Applying 4 revisions to arch/ppc64/Makefile get: getdiffs temp file early EOF
========================== ERROR ========================
unable to create diffstakapatch: patch left in PENDING/2002-07-24.03
========================== ERROR ========================
I tried three times... All the same error.
So must be something wrong with bkbits...
Best regards,
Anton
At 09:24 24/07/02, James H. Cloos Jr. wrote:
>I'm getting this all of a sudden:
>
>:; cd linux-2.4
>:; bk parent
>Parent repository is bk://linux.bkbits.net/linux-2.4
>:; bk pull
>---------------------- Receiving the following csets -----------------------
>1.652 1.651 1.650 1.649 1.648
>----------------------------------------------------------------------------
>ChangeSet fnext: No such file or directory
>
>=================================== ERROR ====================================
>takepatch: missing checksum line in patch, aborting.
>==============================================================================
>
>666 bytes uncompressed to 1222, 1.83X expansion
>:; cd ../linux-2.5
>:; bk parent
>Parent repository is bk://linux.bkbits.net/linux-2.5
>:; bk pull
>---------------------- Receiving the following csets -----------------------
>1.684 1.683 1.681.1.1 1.682 1.681 1.680 1.679 1.678 1.677
>1.676 1.675 1.674 1.673 1.672 1.671 1.670 1.669 1.668 1.667
>1.666
>----------------------------------------------------------------------------
>ChangeSet fnext: No such file or directory
>
>=================================== ERROR ====================================
>takepatch: missing checksum line in patch, aborting.
>==============================================================================
>
>344 bytes uncompressed to 710, 2.06X expansion
>
>
>
>Is this a bkbits issue or something wrong on my side?
>
>-JimC
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to [email protected]
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
--
"I've not lost my mind. It's backed up on tape somewhere." - Unknown
--
Anton Altaparmakov <aia21 at cantab.net> (replace at with @)
Linux NTFS Maintainer / IRC: #ntfs on irc.openprojects.net
WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/
We ran out of disk space, it's fixed. Thanks for the message.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
On Wed, Jul 24, 2002 at 06:13:39AM -0700, Larry McVoy wrote:
> We ran out of disk space, it's fixed. Thanks for the message.
While we are at it, could you please push the Linus tree
(http://linus.bkbits.net/linux-2.5) to the Linux tree
(http://linux.bkbits.net/linux-2.5) manualy again.
/me really wonders if this couldn't be automated somehow...
Thanks,
Stelian.
--
Stelian Pop <[email protected]>
Alcove - http://www.alcove.com
On Wed, Jul 24, 2002 at 04:09:39PM +0200, Stelian Pop wrote:
> While we are at it, could you please push the Linus tree
> (http://linus.bkbits.net/linux-2.5) to the Linux tree
> (http://linux.bkbits.net/linux-2.5) manualy again.
Done.
> /me really wonders if this couldn't be automated somehow...
It isn't because I'm lame, fixing it right now.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
On Wed, 2002-07-24 at 16:09, Stelian Pop wrote:
> On Wed, Jul 24, 2002 at 06:13:39AM -0700, Larry McVoy wrote:
>
> > We ran out of disk space, it's fixed. Thanks for the message.
>
> While we are at it, could you please push the Linus tree
> (http://linus.bkbits.net/linux-2.5) to the Linux tree
> (http://linux.bkbits.net/linux-2.5) manualy again.
>
> /me really wonders if this couldn't be automated somehow...
Why two trees ?
On Wed, Jul 24, 2002 at 09:26:50PM +0200, Kenneth Johansson wrote:
> On Wed, 2002-07-24 at 16:09, Stelian Pop wrote:
> > On Wed, Jul 24, 2002 at 06:13:39AM -0700, Larry McVoy wrote:
> >
> > > We ran out of disk space, it's fixed. Thanks for the message.
> >
> > While we are at it, could you please push the Linus tree
> > (http://linus.bkbits.net/linux-2.5) to the Linux tree
> > (http://linux.bkbits.net/linux-2.5) manualy again.
> >
> > /me really wonders if this couldn't be automated somehow...
>
> Why two trees ?
Because nobody pulls from Linus' tree so it is never locked. He can push
to that and then it's up to yours truly to push it up and wait for locks.
It's actually a non-problem these days, it was a problem right after the
linux.bkbits.net trees went up because people were cloning them over modems
and they were locked forever. Linus was already less than thrilled with
our locking approach and this was just too lame for him to deal with so
I set up the extra tree. It could probably go away but since it works
and the point of BK wrt Linux was to offload Linus, I'm not going to go
yank his chain.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm