Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 686950 - app-admin/perl-cleaner: x11-terms/rxvt-unicode:0 net-irc/weechat:0 sys-apss/ack:0 perl-cleaner had to rebuild this package after the upgrade (Perl 5.26 to 5.28)
Summary: app-admin/perl-cleaner: x11-terms/rxvt-unicode:0 net-irc/weechat:0 sys-apss/a...
Status: RESOLVED CANTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Perl team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: perl-cleaner-rebuild
  Show dependency tree
 
Reported: 2019-05-29 17:27 UTC by trimodephone
Modified: 2019-11-07 22:41 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description trimodephone 2019-05-29 17:27:10 UTC
Upgrading from perl 5.26 to 5.28, running perl-cleaner --all after the upgrade:

* 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:
 *   x11-terms/rxvt-unicode:0 net-irc/weechat:0 sys-apps/ack:0
Comment 1 Ben Kohler gentoo-dev 2019-05-29 17:33:46 UTC
All 3 of these have dev-lang/perl:= in RDEPEND so autorebuilds should have been triggered.  I suspect that emerge may have failed before they were rebuilt, and that's why perl-cleaner picked them up.  Probably nothing to fix here.
Comment 2 Andreas K. Hüttel archtester gentoo-dev 2019-11-07 22:41:27 UTC
(In reply to Ben Kohler from comment #1)
> All 3 of these have dev-lang/perl:= in RDEPEND so autorebuilds should have
> been triggered.  I suspect that emerge may have failed before they were
> rebuilt, and that's why perl-cleaner picked them up.  Probably nothing to
> fix here.

Ack...