Your message dated Tue, 2 Jun 2015 15:54:34 +0100 with message-id <[email protected]> and subject line Re: Bug#787530: perl-modules-5.22 : Breaks: perl-modules but 5.20.2-6 is installed. has caused the Debian Bug report #787530, regarding perl-modules-5.22 : Breaks: perl-modules but 5.20.2-6 is installed. to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 787530: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787530 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---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.
--- End Message ---
--- Begin Message ---On Tue, Jun 02, 2015 at 10:40:38PM +0800, 積丹尼 Dan Jacobson wrote: > Package: perl-modules There's no bug here; closing. > 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. [...] As far as I know the only reason you would be getting those message is because you've explicitly chosen to install perl 5.22 from experimental (if not, that's probably a bug in aptitude). Packages from experimental are not guaranteed to work[1] and very much not recommended for general use. > 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. We need to use experimental to stage the perl transition, and that necessarily takes several months. > 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. I strongly recommend not using perl (or any) package from experimental unless you're happy to live with the breakage. Cheers, Dominic. [1] <https://www.debian.org/doc/manuals/debian-faq/ch-ftparchives.en.html>
--- End Message ---
