From: Grant Edwards <grant.b.edwards@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] packages going stable after sources become unavailable
Date: Sun, 8 Sep 2019 15:38:05 -0000 (UTC) [thread overview]
Message-ID: <ql378t$583i$1@blaine.gmane.org> (raw)
I've noticed on several occasions in the past few months that by the
time some packages are marked stable, the version is old enough that
sources are no longer available -- so the emerge fails because sources
can no longer be downloaded. If I'm lucky I may have a copy of the
sources on another machine. If I'm not lucky, I just wait until the
next time a new version goes stable and hope that it's not been
obsoleted.
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?
--
Grant
next reply other threads:[~2019-09-08 15:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-08 15:38 Grant Edwards [this message]
2019-09-08 15:51 ` [gentoo-user] packages going stable after sources become unavailable Rich Freeman
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='ql378t$583i$1@blaine.gmane.org' \
--to=grant.b.edwards@gmail.com \
--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