From: NP-Hardass <NP-Hardass@gentoo.org>
To: gentoo-dev@lists.gentoo.org,
Lars Wendler <polynomial-c@gentoo.org>,
"Anthony G. Basile" <blueness@gentoo.org>
Subject: Re: [gentoo-dev] Managing updates on many identical Gentoo systems
Date: Thu, 18 Jan 2018 14:22:00 -0500 [thread overview]
Message-ID: <3d934658-11eb-b289-22f0-07885b46f34f@gentoo.org> (raw)
In-Reply-To: <20180118133436.532d5cef@abudhabi.paradoxon.rec>
[-- Attachment #1.1: Type: text/plain, Size: 1205 bytes --]
On 01/18/2018 07:34 AM, Lars Wendler wrote:
> Hi Anthony,
>
[...]
>
> well, I never did anything like that but regarding the dependency
> calculation... how about something like
>
> emerge -1OKanv $(qlist -CISq)
>
> (--oneshot --nodeps --usepkgonly --ask --noreplace --verbose)
>
> which simply omits dependency calculations, only takes into account
> available binary packages and doesn't replace same versions?
> Of course this requires all installed packages really being available as
> binpkgs.
> Since all the installations are the same, as long as you provide a sane
> set of binpkgs, dependency calculation should not matter anyway.
> The only issue I can think of is that a system might become broken if
> the update gets interrupted before all packages have been updated.
>
> Kind regards
>
TTBOMK, this will fail also if there is a slot change. For instance,
with the recent autoconf-2.69 move from :0 to :2.69, dependency
resolution would have resulted softblock, thus removing :0 and then
merging :2.69 automatically. with a --nodeps, :2.69 would attempt to
merge without removing :0 for this package, resulting in an emerge failure.
--
NP-Hardass
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-01-18 19:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 11:46 [gentoo-dev] Managing updates on many identical Gentoo systems Anthony G. Basile
2018-01-18 12:00 ` Joakim Tjernlund
2018-01-18 12:34 ` Lars Wendler
2018-01-18 19:22 ` NP-Hardass [this message]
2018-01-18 12:42 ` Martin Gysel
2018-01-18 15:36 ` [gentoo-dev] " Duncan
2018-01-18 22:13 ` Bill Kenworthy
2018-01-19 14:45 ` Alec Warner
2018-01-19 15:03 ` Anthony G. Basile
2018-01-19 18:13 ` Zac Medico
2018-01-20 15:34 ` Anthony G. Basile
2018-01-20 21:48 ` Zac Medico
2018-01-18 16:13 ` [gentoo-dev] " Alec Warner
2018-01-18 23:01 ` Zac Medico
2018-01-18 22:30 ` Alexander Tsoy
2018-01-18 22:53 ` Alexander Tsoy
2018-01-18 23:00 ` R0b0t1
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=3d934658-11eb-b289-22f0-07885b46f34f@gentoo.org \
--to=np-hardass@gentoo.org \
--cc=blueness@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=polynomial-c@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