From: Andrew Savchenko <bircoph@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] perl-cleaner output
Date: Mon, 24 Oct 2016 17:22:59 +0300 [thread overview]
Message-ID: <20161024172259.7bcb530a4c2a6dd202a31e0d@gentoo.org> (raw)
In-Reply-To: <bdfa2092-67ae-b552-248a-1204eb85a764@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1292 bytes --]
On Fri, 7 Oct 2016 09:30:01 -0700 Daniel Frey wrote:
> So, I was upgrading several machines, and as a habit I always run
> perl-cleaner. Every machine gave me an output like so with somewhat
> different package lists:
>
>
> *
> * It seems like perl-cleaner had to rebuild some packages.
> *
> * If you have just updated your major Perl version (e.g. from 5.20.2 to
> 5.22.0)
> ,
> * and have run perl-cleaner _after_ that update, then this means most likely
> * that these packages are buggy. Please file a bug on
> http://bugs.gentoo.org/ and
> * report that perl-cleaner needed to reinstall the following list:
> * sys-apps/texinfo:0
> dev-perl/libintl-perl:0
> dev-perl/Text-Unidecode:0
> dev-perl/Locale-gettext:0
> dev-perl/Unicode-EastAsianWidth:0
> dev-perl/XML-Parser:0
>
>
>
> I'm happy to file a bug but what should I file it against? perl-cleaner?
> perl itself? All of these were triggered after the upgrade to 5.22.0.
No, bugs should be file for each package listed:
dev-perl/libintl-perl:0
dev-perl/Text-Unidecode:0
dev-perl/Locale-gettext:0
dev-perl/Unicode-EastAsianWidth:0
dev-perl/XML-Parser:0
Of course, you should check if such bugs already exist or packages
are already fixed.
Best regards,
Andrew Savchenko
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-10-24 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 16:30 [gentoo-user] perl-cleaner output Daniel Frey
2016-10-24 14:22 ` Andrew Savchenko [this message]
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=20161024172259.7bcb530a4c2a6dd202a31e0d@gentoo.org \
--to=bircoph@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