public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] packages going stable after sources become unavailable
Date: Sun, 8 Sep 2019 11:51:12 -0400	[thread overview]
Message-ID: <CAGfcS_n4hbtKQtU3tH=MnYkkZhZ7J_b6YMYWP0FWMeFFXDmNNw@mail.gmail.com> (raw)
In-Reply-To: <ql378t$583i$1@blaine.gmane.org>

On Sun, Sep 8, 2019 at 11:38 AM Grant Edwards <grant.b.edwards@gmail.com> wrote:
>
> This seems to happen regularly with Imagemagick.  Version 7.0.8.60
> just went stable today, yet it can't be built because version 7.0.8.60
> sources can no longer be downloaded.
>
> Am I doing something wrong?
>
> Shouldn't there be a requirement that an ebuild actually be
> _buildable_ from scratch when it goes stable?
>

Do you have a working Gentoo distfile mirror in your make.conf?

imagemagic has a mirror:// SRC_URI.  That means there is no upstream
distfile available, and Gentoo is distributing its own file via the
mirrors (this is actually frowned upon these days though I'm not sure
if it is banned offhand - I just avoid doing it this way).  Usually
the better practice is to host the file somewhere (such as the Gentoo
webserver), and it will be mirrored anyway.  These mirror:// files are
manually injected into the mirror system by developers, and then they
stick around as long as some ebuild references them, and then they
just go poof without a trace (which means users with older repos can
have issues).  There has been talk about more robust solutions for
these files (especially patches/etc), but nothing has happened.

If your system isn't configured with a working Gentoo distfile mirror
then for most packages you're probably downloading everything from
upstream, but these mirror:// URIs have no sources other than the
mirrors so if you don't have a working mirror config it simply won't
fetch at all.

In general anything in the tree should be fetchable.  If that isn't
the case it should be quickly spotted and fixed/removed, and it is
always a valid bug, assuming it isn't just a local issue on your
system.  I wouldn't file a bug for this issue - I suspect QA would
have already if it wanted to make it a strict policy.  This sort of
thing is trivially detected with a tinderbox or repoman if desired.

-- 
Rich


  reply	other threads:[~2019-09-08 15:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-08 15:38 [gentoo-user] packages going stable after sources become unavailable Grant Edwards
2019-09-08 15:51 ` Rich Freeman [this message]
2019-09-08 16:21   ` [gentoo-user] " Grant Edwards

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='CAGfcS_n4hbtKQtU3tH=MnYkkZhZ7J_b6YMYWP0FWMeFFXDmNNw@mail.gmail.com' \
    --to=rich0@gentoo.org \
    --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