From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] data/gentoo-news:master commit in: 2021-07-20-perl-5_34-upgrade/
Date: Tue, 20 Jul 2021 21:36:13 +0000 (UTC) [thread overview]
Message-ID: <1626816967.aea5de7393dc86decef3b34cf0f908b764beac34.sam@gentoo> (raw)
commit: aea5de7393dc86decef3b34cf0f908b764beac34
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Jul 19 21:48:25 2021 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Jul 20 21:36:07 2021 +0000
URL: https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=aea5de73
2021-07-20-perl-5_34-upgrade: add news item
Bug: https://bugs.gentoo.org/802639
Signed-off-by: Sam James <sam <AT> gentoo.org>
.../2021-07-20-perl-5_34-upgrade.en.txt | 43 ++++++++++++++++++++++
1 file changed, 43 insertions(+)
diff --git a/2021-07-20-perl-5_34-upgrade/2021-07-20-perl-5_34-upgrade.en.txt b/2021-07-20-perl-5_34-upgrade/2021-07-20-perl-5_34-upgrade.en.txt
new file mode 100644
index 0000000..c6abd4f
--- /dev/null
+++ b/2021-07-20-perl-5_34-upgrade/2021-07-20-perl-5_34-upgrade.en.txt
@@ -0,0 +1,43 @@
+Title: Perl 5.34 upgrade now stable
+Author: Sam James <sam@gentoo.org>
+Posted: 2021-07-20
+Revision: 1
+News-Item-Format: 2.0
+
+The Perl project in Gentoo has begun stabilisation of Perl 5.34 [0]
+which is the latest stable version released upstream.
+
+While the package manager usually handles this upgrade cleanly,
+there are some bugs [1][2][3] which affect Portage's dependency resolution
+that sometimes mean rebuilds occur in the wrong order - this is
+exacerbated by the packaging model used for Perl (but not its fault).
+
+We therefore recommend the following procedure for users:
+1. Sync your tree:
+# emerge --sync
+
+2. Perform a full world upgrade, e.g.:
+# emerge -a -uvDU @world --keep-going=y
+
+3. If any failures occur, please run perl-cleaner --all, then try again:
+# perl-cleaner --all
+
+4. Perform a world upgrade again.
+
+5. Once complete, depclean:
+# emerge -a --depclean
+
+Rarely, it may be necessary to perform a one-off installation of a package,
+but usually `perl-cleaner` will resolve the issue. If an error message occurs
+after running perl-cleaner, try e.g. for a fictional package dev-perl/foo:
+# emerge -a --oneshot --verbose dev-perl/foo
+
+If you have any issues, please consult the standard support channels [4]
+(such as our forums or IRC channels) and we will do our best to get your
+system working well again.
+
+[0] https://bugs.gentoo.org/802639
+[1] https://bugs.gentoo.org/592880
+[2] https://bugs.gentoo.org/793992
+[3] https://bugs.gentoo.org/199856
+[4] https://www.gentoo.org/support/
next reply other threads:[~2021-07-20 21:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 21:36 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-20 21:42 [gentoo-commits] data/gentoo-news:master commit in: 2021-07-20-perl-5_34-upgrade/ Sam James
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=1626816967.aea5de7393dc86decef3b34cf0f908b764beac34.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@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