linux-kernel - Re: linux-next: error while fetching the spi-nor tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 12 Dec 2017 22:24:17 +0100
From:   Cyrille Pitchen <cyrille.pitchen@...ev4u.fr>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: error while fetching the spi-nor tree

Hi Stephen,

I've just added 2 commits about 8 hours ago, nothing special.
Could the issue be explained by an unlikely bad timing?

I don't see anything wrong when fetching the tree or when browsing the
web server:
http://git.infradead.org/l2-mtd.git/shortlog/refs/heads/spi-nor/next

Please, let me know whether it was a spurious error or if it still doesn't
work. Currently, I don't know what's going on.

Anyway, thanks for your report.

Best regards,

Cyrille

Le 12/12/2017 à 21:58, Stephen Rothwell a écrit :
> Hi Cyrille,
> 
> Fetching the spi-nor tree
> (git://git.infradead.org/l2-mtd.git#spi-nor/next) this morning, I get
> theses errors:
> 
> remote: error: Could not read 6e408e3aa1643624ea7da50ad5b27a226a16a654
> remote: fatal: bad tree object 6e408e3aa1643624ea7da50ad5b27a226a16a654
> remote: aborting due to possible repository corruption on the remote side.
> fatal: protocol error: bad pack header
> 
> I wil continue to use the previously fetched tree.
>