On Fri, 2 Oct 2020 10:45:32 +0200, n952162 wrote: > Have I successfully updated my system? > > I ran this command: > > emerge \ > -v \ > --verbose-conflicts \ > --deep \ > -update \ > --changed-use \ > --keep-going \ > --with-bdeps=y \ > --changed-deps \ > --backtrack=100 \ > @world > > and got tons of stuff that looks like spurious debugging/tracing info > > parent: (dev-libs/glib-2.64.5:2/2::gentoo, ebuild scheduled for > merge) > child: (virtual/libelf-3:0/1::gentoo, ebuild scheduled for > merge) (runtime_slot_op) > parent: (dev-libs/glib-2.64.5:2/2::gentoo, ebuild scheduled for > merge) > child: (virtual/libelf-3:0/1::gentoo, ebuild scheduled for > merge) (runtime_slot_op) > > and these snippets: > > Total: 869 packages (332 upgrades, 30 new, 10 in new slots, 497 > reinstalls), Size of downloads: 2769158 KiB > Conflict: 1 block > forced reinstall atoms:
Did the emerge complete without error? The answer that question is the same as the answer to yours. It looks like you have gone a long time without updating, so if you hit problems, and you do have one block there, a simple "emerge --ask @system" /may/ be a better place to start. I'd also drop -v from the invocation as it is the main cause of your "spurious debugging/tracing info". emerge is verbose enough on its own and will give you plenty of feedback if something isn't quite right, -v just buries the important information in noise. -- Neil Bothwick Time is an illusion but never so much as when you're using a modem.
pgpnX1vyMiMWq.pgp
Description: OpenPGP digital signature
