From: Axel Siebenwirth <axel@pearbough.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Can't bk clone linux-2.5
Date: Thu, 18 Dec 2003 12:25:43 +0100 [thread overview]
Message-ID: <20031218112543.GA10230@neon> (raw)
In-Reply-To: <20031218104348.GA9007@neon>
Hi linux-kernel!
On Thu, 18 Dec 2003, Axel Siebenwirth wrote:
> Hi,
>
> I'm lost. I cannot clone linux-2.5 bk tree.
>
> I am in an empty directory. Then I do:
>
> bk clone http://linux.bkbits.net/linux-2.5 linus-2.5
> Clone http://linux.bkbits.net/linux-2.5
> -> file://usr/local/src/kernel/linus-2.5
> 14 bytes uncompressed to 10, 0.71X expansion
> Looking for, and removing, any uncommitted deltas...
> Set parent to http://linux.bkbits.net/linux-2.5
> Running consistency check ...
> get: couldn't open SCCS/s.ChangeSet
> get: No such file: SCCS/s.ChangeSet
> sfiles: can't init ChangeSet: No such file or directory
> idcache: No such file or directory
> Consistency check failed, repository left locked.
> WARNING: deleting orphan file /tmp/bk_clone2_gdZWv7
> Exit 1
Doing a "bk pull" on an existing repository results in an error as well.
Is it just me?
bk pull
Pull http://linux.bkbits.net/linux-2.5
-> file://usr/local/src/system/kernel/linus-2.5
---------------------- Receiving the following csets -----------------------
1.1533 1.1532 1.1531 1.1530 1.1529 1.1515.1.8 1.1515.1.7
1.1515.1.6 1.1515.1.5 1.1515.1.4 1.1515.1.3 1.1528 1.1527
1.1526 1.1525 1.1524 1.1523 1.1522 1.1521 1.1520 1.1519
1.1518 1.1517 1.1516
----------------------------------------------------------------------------
Expected '== f =='
GOT: # Patch checksum=f8850b70
==============================================================================
186 bytes uncompressed to 227, 1.22X expansion
Exit 1
Regards,
Axel
next prev parent reply other threads:[~2003-12-18 11:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-18 10:43 Can't bk clone linux-2.5 Axel Siebenwirth
2003-12-18 11:25 ` Axel Siebenwirth [this message]
2003-12-18 11:32 ` Tupshin Harper
2003-12-18 16:57 ` Andy Isaacson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031218112543.GA10230@neon \
--to=axel@pearbough.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox