From: Alexey Mishustin <shumkar@shumkar.ru>
To: Gentoo <gentoo-user@lists.gentoo.org>
Subject: Re: [SOLVED] Re: [gentoo-user] Ebuild: How to deal with external repositories properly (best practise)?
Date: Wed, 5 Aug 2020 01:57:07 +0300 [thread overview]
Message-ID: <CAGWFrguiUjTYQNObHT=fXGdjT15xQwQAeBDhbiPFrpjo0k7mpQ@mail.gmail.com> (raw)
In-Reply-To: <AM6P191MB029625063287B39FB88E23A8EF4C0@AM6P191MB0296.EURP191.PROD.OUTLOOK.COM>
вс, 2 авг. 2020 г. в 13:52, Ramon Fischer <Ramon_Fischer@hotmail.de>:
>
> I decided to use "EGIT_COMMIT" to let the ebuild pulling a certain commit.
And even that would not give the sense of security...
Just read in gentoo-dev [1]:
...unannounced serverside change by GitHub, which broke download of
tarballs by git-tree-hash, e.g. previously https://
api.github.com/repos/JuliaLang/MbedTLS.jl/tarball/
2d94286a9c2f52c63a16146bb86fd6cdfbf677c6 would give the tarball for
that tree- hash, while it now gives the tarball for master instead.
[1] - https://archives.gentoo.org/gentoo-dev/message/41d8c5457df392ed0309153651db5b3c
--
Best regards,
Alex
next prev parent reply other threads:[~2020-08-04 22:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 4:47 [gentoo-user] Ebuild: How to deal with external repositories properly (best practise)? Ramon Fischer
2020-07-28 8:53 ` tastytea
2020-07-28 10:02 ` Ramon Fischer
2020-07-28 12:52 ` tastytea
2020-07-28 13:32 ` Ramon Fischer
2020-08-02 10:51 ` [SOLVED] " Ramon Fischer
2020-08-04 22:57 ` Alexey Mishustin [this message]
2020-08-04 23:36 ` Rich Freeman
2020-08-04 23:51 ` tastytea
2020-08-05 0:03 ` Rich Freeman
2020-07-28 10:01 ` Neil Bothwick
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='CAGWFrguiUjTYQNObHT=fXGdjT15xQwQAeBDhbiPFrpjo0k7mpQ@mail.gmail.com' \
--to=shumkar@shumkar.ru \
--cc=gentoo-user@lists.gentoo.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