Bug#787530: perl-modules-5.22 : Breaks: perl-modules but 5.20.2-6 is installed.

積丹尼 Dan Jacobson jidanni at jidanni.org
Tue Jun 2 14:40:38 UTC 2015


Package: perl-modules

Is there any way for me to avoid apt(itude) telling me for what will
probably be the next several months:

The following packages have unmet dependencies:
 libversion-perl : Depends: perlapi-5.20.0 which is a virtual package.
 perl-modules-5.22 : Breaks: perl-modules but 5.20.2-6 is installed.
 libxml-libxml-perl : Depends: perlapi-5.20.2 which is a virtual package.
 libfile-fnmatch-perl : Depends: perlapi-5.20.0 which is a virtual package.
 libtext-iconv-perl : Depends: perlapi-5.20.0 which is a virtual package.
 libsocket6-perl : Depends: perlapi-5.20.0 which is a virtual package.
 perl-base : Breaks: perl-modules (< 5.22.0~rc2~) but 5.20.2-6 is installed.
 libcommon-sense-perl : Depends: perlapi-5.20.2 which is a virtual package.
                        Depends: perl (< 5.20.3~) but 5.22.0~rc2-2 is to be installed.
 libhtml-parser-perl : Depends: perlapi-5.20.1 which is a virtual package.
 libuuid-perl : Depends: perlapi-5.20.2 which is a virtual package.
 libyaml-syck-perl : Depends: perlapi-5.20.0 which is a virtual package.
 libapt-pkg-perl : Depends: perlapi-5.20.0 which is a virtual package.
 libunicode-map8-perl : Depends: perlapi-5.20.0 which is a virtual package.
 libnetaddr-ip-perl : Depends: perlapi-5.20.0 which is a virtual package.
 libterm-readkey-perl : Depends: perlapi-5.20.2 which is a virtual package.
 liblocale-gettext-perl : PreDepends: perlapi-5.20.0 which is a virtual package.
 libnet-dns-perl : Depends: perlapi-5.20.1 which is a virtual package.
 libunicode-string-perl : Depends: perlapi-5.20.0 which is a virtual package.
 libcurses-perl : Depends: perlapi-5.20.0 which is a virtual package.
 libnet-ssleay-perl : Depends: perlapi-5.20.2 which is a virtual package.
 libjson-xs-perl : Depends: perlapi-5.20.0 which is a virtual package.

I.e., can you fellows release what ever it is you are releasing in one
step, instead of just releasing half of it first which then causes apt
to give me these messages every time I use it for what I recall is a
full half year each time.

If I use aptitude safe-upgrade instead of full-upgrade, that will
influence how I upgrade other non-perl packages.

If I hold part of perl then I won't know when the logjam is finally
lifted.

I could forbid-version one part of perl but which part? And will it
really clean up all those messages, and what about next time this
happens? Thanks.




More information about the Perl-maintainers mailing list