unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: "Artyom V. Poptsov" <poptsov.artyom@gmail.com>, 53148@debbugs.gnu.org
Subject: [bug#53148] [PATCH] gnu: java-snakeyaml: Fix the source URI
Date: Sun, 09 Jan 2022 23:06:41 +0100	[thread overview]
Message-ID: <954ad66792b4088c44ef20091e30037d4ef955a4.camel@telenet.be> (raw)
In-Reply-To: <874k6clhek.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]

Artyom V. Poptsov schreef op ma 10-01-2022 om 00:37 [+0300]:
>                (method url-fetch)
> -              (uri (string-append
> "https://bitbucket.org/asomov/snakeyaml/get/v"
> +              (uri (string-append
> "https://bitbucket.org/snakeyaml/snakeyaml/get/v"
>                                    version ".tar.gz"))
>                (file-name (string-append name "-" version ".tar.gz"))

I compared the result of "guix build --source java-snakeyaml"
before this change with
"guix download https://bitbucket.org/snakeyaml/snakeyaml/get/v1.18.tar.gz".

There are some small differences in the tarball:

│ │┄ Files identical despite different names
│ │   --- asomov-snakeyaml-
97aa6dd6be26/src/test/resources/recursive/with-children-as-set.yaml
│ ├── +++ snakeyaml-snakeyaml-
97aa6dd6be26/src/test/resources/recursive/with-children-as-set.yaml

So it seems like these tarballs are autogenerated.
Seems like we need to switch to git-fetch, and investigate
other tarballs from bitbucket.org as well?

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

      reply	other threads:[~2022-01-09 22:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-09 20:53 [bug#53148] [PATCH] gnu: java-snakeyaml: Fix the source URI Artyom V. Poptsov
2022-01-09 20:57 ` Maxime Devos
2022-01-09 21:13 ` Artyom V. Poptsov
2022-01-09 21:37 ` Artyom V. Poptsov
2022-01-09 22:06   ` Maxime Devos [this message]

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=954ad66792b4088c44ef20091e30037d4ef955a4.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=53148@debbugs.gnu.org \
    --cc=poptsov.artyom@gmail.com \
    /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).