From: Danny Milosavljevic <dannym@scratchpost.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 31247@debbugs.gnu.org
Subject: bug#31247: fetching an svn repository always results in a different hash
Date: Tue, 24 Apr 2018 22:56:41 +0200 [thread overview]
Message-ID: <20180424225641.3ce8e18f@scratchpost.org> (raw)
In-Reply-To: <20180424224014.2f65d462@lepiller.eu>
[-- Attachment #1: Type: text/plain, Size: 925 bytes --]
Hi Julien,
On Tue, 24 Apr 2018 22:40:21 +0200
Julien Lepiller <julien@lepiller.eu> wrote:
> > > I'm trying to use svn-fetch in a new package, but I always get a
> > > different hash when I try to download the sources. I think this is
> > > due to fetching external resources. Here are two adresses that
> > > trigger this bug:
> >
> > Can you try comparing the differences between the downloaded archives?
> > The diffoscope program will be useful.
>
> There are differences in .svn/wc.db. The top .svn directory is removed,
> but there are other .svn directories that are not removed and contain a
> wc.db file. In my case, src/lib/kStuff/.svn is kept intact and differs
> every time.
I think we should change guix/build/svn.scm to also delete the other ".svn"
directories.
Those contain state that is not necessary for the build - and since it's
causing trouble, we can just remove them.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-04-24 20:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 15:44 bug#31247: fetching an svn repository always results in a different hash julien lepiller
2018-04-23 18:41 ` Leo Famulari
2018-04-24 20:40 ` Julien Lepiller
2018-04-24 20:56 ` Danny Milosavljevic [this message]
2019-04-05 12:54 ` Julien Lepiller
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180424225641.3ce8e18f@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=31247@debbugs.gnu.org \
--cc=julien@lepiller.eu \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).