Re: [gentoo-user] Re: emerge conflict
On Tue, 20 Sep 2016 08:41:56 +0200, Kai Krakow wrote: > > What makes you think I didn't use -p? I have a cron job that runs > > emerge -pXXX @world after syncing and mails me the output, and I > > always use -a when running emerge in a shell. > > You could also try porticron... ;-) I could but I've been running this script on several machines for many years and it does just what I want and has evolved along with portage. I may take a look at porticron to see if there's anything else I want but didn't know it ;-) -- Neil Bothwick Physics is like sex: sure, it may give some practical results, but that's not why we do it.Richard Feynman pgpzjJBb4IrBf.pgp Description: OpenPGP digital signature
[gentoo-user] Re: emerge conflict
Am Mon, 19 Sep 2016 21:17:36 +0100 schrieb Neil Bothwick : > On Mon, 19 Sep 2016 13:01:39 -0400, Philip Webb wrote: > > > > I'm surprised you needed to jump through such hoops. > > > I updated 2 stable systems to perl 5.22 last week > > > and emerge @world took care of all blockers, > > > although I did need to run perl-cleaner afterwards. > > > > I never run 'emerge world' without '-p' : > > it's the lazy way to manage a Gentoo system & asks for trouble. > > What makes you think I didn't use -p? I have a cron job that runs > emerge -pXXX @world after syncing and mails me the output, and I > always use -a when running emerge in a shell. > > The point is that, whether I used -p, -a or neither, portage handled > it all for me. You could also try porticron... ;-) -- Regards, Kai Replies to list-only preferred. pgpxj7jnFAFko.pgp Description: Digitale Signatur von OpenPGP
Re: [gentoo-user] Re: emerge conflict
On Mon, 19 Sep 2016 13:01:39 -0400, Philip Webb wrote: > > I'm surprised you needed to jump through such hoops. > > I updated 2 stable systems to perl 5.22 last week > > and emerge @world took care of all blockers, > > although I did need to run perl-cleaner afterwards. > > I never run 'emerge world' without '-p' : > it's the lazy way to manage a Gentoo system & asks for trouble. What makes you think I didn't use -p? I have a cron job that runs emerge -pXXX @world after syncing and mails me the output, and I always use -a when running emerge in a shell. The point is that, whether I used -p, -a or neither, portage handled it all for me. -- Neil Bothwick Half of being smart is knowing what you're dumb at. pgp9_DxARBVmS.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Re: emerge conflict
160919 Neil Bothwick wrote: > On Sun, 18 Sep 2016 19:53:10 -0400, Philip Webb wrote: >> I got around the problem by using : >> emerge --backtrack=30 -pvtD perl perl-Archive-Tar perl-Carp >> perl-Compress-Raw-Zlib perl-CPAN-Meta-Requirements perl-Data-Dumper >> perl-ExtUtils-CBuilder perl-ExtUtils-Install perl-ExtUtils-MakeMaker >> perl-ExtUtils-Manifest perl-ExtUtils-ParseXS perl-File-Spec >> perl-Getopt-Long perl-IO perl-Locale-Maketext perl-Perl-OSType >> perl-Scalar-List-Utils perl-Test-Harness perl-Text-ParseWords > I'm surprised you needed to jump through such hoops. > I updated 2 stable systems to perl 5.22 last week > and emerge @world took care of all blockers, > although I did need to run perl-cleaner afterwards. I never run 'emerge world' without '-p' : it's the lazy way to manage a Gentoo system & asks for trouble. >> Perl can stay where it is till LO 5.2 arrives in Portage : >> in fact, isn't it a bit slow appearing ? > 5.2.1.2 has been in testing for a couple of days, > but it appears that 5.1.4.2 is the only ebuild in stable, > so that may be the reason for your downgrade. Actually, it wb an upgrade from 5.1.2.2 . Anyway, the problem is resolved & I can decide when/how to proceed. -- ,, SUPPORT ___//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT`-O--O---' purslowatchassdotutorontodotca
Re: [gentoo-user] Re: emerge conflict
On 19/09/16 15:28, Neil Bothwick wrote: > On Sun, 18 Sep 2016 19:53:10 -0400, Philip Webb wrote: > >> I got around the problem by using : >> >> emerge --backtrack=30 -pvtD perl perl-Archive-Tar perl-Carp >> perl-Compress-Raw-Zlib perl-CPAN-Meta-Requirements perl-Data-Dumper >> perl-ExtUtils-CBuilder perl-ExtUtils-Install perl-ExtUtils-MakeMaker >> perl-ExtUtils-Manifest perl-ExtUtils-ParseXS perl-File-Spec >> perl-Getopt-Long perl-IO perl-Locale-Maketext perl-Perl-OSType >> perl-Scalar-List-Utils perl-Test-Harness perl-Text-ParseWords > > I'm surprised you needed to jump through such hoops, I updated 2 stable > systems to perl 5.22 last week and emerge @world took care of all > blockers, although I did need to run perl-cleaner afterwards. > >> It wants to remerge Exiftool Imagemagick Cups-filters Graphite2 >> & also some further Perl pkgs & it wants to downgrade (G)Vim. >> That much wb ok, but it also wants to update Poppler & therefore LO >> & I don't feel like doing the last at the moment ( 65 min last time). >> >> What you suggested is fairly standard & I've done it in the past, >> but thanks for prompting me. Thanks to the other respondents too. >> >> Perl can stay where it is till LO 5.2 arrives in Portage : >> in fact, isn't it a bit slow appearing ? > > 5.2.1.2 has been in testing for a couple of days, but it appears that > 5.1.4.2 is the only ebuild in stable, so that may be the reason for your > downgrade. > > I had only one machine fail - perl itself had to be brute forced with --nodeps, perl-cleaner fixed the rest after I fixed some g-cpan failures (wrong case - been around for a long while) - but for that perl-cleaner would have picked it all up. BillK
Re: [gentoo-user] Re: emerge conflict
On Sun, 18 Sep 2016 19:53:10 -0400, Philip Webb wrote: > I got around the problem by using : > > emerge --backtrack=30 -pvtD perl perl-Archive-Tar perl-Carp > perl-Compress-Raw-Zlib perl-CPAN-Meta-Requirements perl-Data-Dumper > perl-ExtUtils-CBuilder perl-ExtUtils-Install perl-ExtUtils-MakeMaker > perl-ExtUtils-Manifest perl-ExtUtils-ParseXS perl-File-Spec > perl-Getopt-Long perl-IO perl-Locale-Maketext perl-Perl-OSType > perl-Scalar-List-Utils perl-Test-Harness perl-Text-ParseWords I'm surprised you needed to jump through such hoops, I updated 2 stable systems to perl 5.22 last week and emerge @world took care of all blockers, although I did need to run perl-cleaner afterwards. > It wants to remerge Exiftool Imagemagick Cups-filters Graphite2 > & also some further Perl pkgs & it wants to downgrade (G)Vim. > That much wb ok, but it also wants to update Poppler & therefore LO > & I don't feel like doing the last at the moment ( 65 min last time). > > What you suggested is fairly standard & I've done it in the past, > but thanks for prompting me. Thanks to the other respondents too. > > Perl can stay where it is till LO 5.2 arrives in Portage : > in fact, isn't it a bit slow appearing ? 5.2.1.2 has been in testing for a couple of days, but it appears that 5.1.4.2 is the only ebuild in stable, so that may be the reason for your downgrade. -- Neil Bothwick You know it's cold when you spot a lawyer with his hands in his own pockets. pgp8fb0kZB4Hq.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Re: emerge conflict
On Sun, Sep 18, 2016 at 7:53 PM, Philip Webb wrote: > 160918 Kai Krakow wrote: >> Try ... adding vim and other packages to the list: >> # emerge -1Dpuv perl >> # emerge -1Dpuv perl vim ... > > I got around the problem by using : > > emerge --backtrack=30 -pvtD perl I suspect that you could have gotten away with just emerge --backtrack=30 -puDvt @world. Or if you want less than that then just grab all the perl stuff out of your world, which it looks like you already did. Without increasing the backtrack setting I suspect it can't get past the blockers. -- Rich
Re: [gentoo-user] Re: emerge conflict
160918 Kai Krakow wrote: > Try ... adding vim and other packages to the list: > # emerge -1Dpuv perl > # emerge -1Dpuv perl vim ... I got around the problem by using : emerge --backtrack=30 -pvtD perl perl-Archive-Tar perl-Carp perl-Compress-Raw-Zlib perl-CPAN-Meta-Requirements perl-Data-Dumper perl-ExtUtils-CBuilder perl-ExtUtils-Install perl-ExtUtils-MakeMaker perl-ExtUtils-Manifest perl-ExtUtils-ParseXS perl-File-Spec perl-Getopt-Long perl-IO perl-Locale-Maketext perl-Perl-OSType perl-Scalar-List-Utils perl-Test-Harness perl-Text-ParseWords It wants to remerge Exiftool Imagemagick Cups-filters Graphite2 & also some further Perl pkgs & it wants to downgrade (G)Vim. That much wb ok, but it also wants to update Poppler & therefore LO & I don't feel like doing the last at the moment ( 65 min last time). What you suggested is fairly standard & I've done it in the past, but thanks for prompting me. Thanks to the other respondents too. Perl can stay where it is till LO 5.2 arrives in Portage : in fact, isn't it a bit slow appearing ? -- ,, SUPPORT ___//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT`-O--O---' purslowatchassdotutorontodotca
[gentoo-user] Re: emerge conflict
Am Sat, 17 Sep 2016 19:12:40 -0400
schrieb Philip Webb :
> Starting my regular Sat system update, 'eix-sync' told me
> (equivalent) :
>
> root:524 ~> eix ^perl$
> [U] dev-lang/perl
> Available versions: 5.20.2(0/5.20) ~5.20.2-r1(0/5.20)
> ~5.22.0(0/5.22) ~5.22.1(0/5.22) 5.22.2(0/5.22) ~5.24.0(0/5.24)
> ~5.24.0-r1(0/5.24) {berkdb debug doc gdbm ithreads} Installed
> versions: 5.20.2([2015-10-04 11:34:10])(gdbm -berkdb -debug -doc
> -ithreads)
>
> So I tried 'emerge -pv perl' & was told the current version of (G)Vim
> required the earlier installed version of Perl.
> After updating to the latest testing version of (G)Vim, I tried
> again :
>
> root:522 ~> emerge -pv perl
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild R] dev-lang/perl-5.20.2:0/5.20::gentoo USE="-berkdb
> -debug -doc gdbm -ithreads" 0 KiB
>
> Total: 1 package (1 reinstall), Size of downloads: 0 KiB
>
> WARNING: One or more updates/rebuilds have been skipped due to a
> dependency conflict:
[...]
Try running "emerge -C $(qlist -IC virtual/perl-) first, then run a
deep update. If that fails, add vim and other packages to the list:
# emerge -1Dpuv perl
# emerge -1Dpuv perl vim ...
Also check your world file if it accidentally includes perl
dependencies. If deps need to be removed by emerge during an updates,
it will only do it if it is absent in the world file. That is, remove
"virtual/perl-*" and "perl-core/*" from the world file unless you added
them on purpose.
--
Regards,
Kai
Replies to list-only preferred.
[gentoo-user] Re: emerge conflict
Am Sat, 17 Sep 2016 19:12:40 -0400
schrieb Philip Webb :
> Starting my regular Sat system update, 'eix-sync' told me
> (equivalent) :
>
> root:524 ~> eix ^perl$
> [U] dev-lang/perl
> Available versions: 5.20.2(0/5.20) ~5.20.2-r1(0/5.20)
> ~5.22.0(0/5.22) ~5.22.1(0/5.22) 5.22.2(0/5.22) ~5.24.0(0/5.24)
> ~5.24.0-r1(0/5.24) {berkdb debug doc gdbm ithreads} Installed
> versions: 5.20.2([2015-10-04 11:34:10])(gdbm -berkdb -debug -doc
> -ithreads)
>
> So I tried 'emerge -pv perl' & was told the current version of (G)Vim
> required the earlier installed version of Perl.
> After updating to the latest testing version of (G)Vim, I tried
> again :
>
> root:522 ~> emerge -pv perl
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild R] dev-lang/perl-5.20.2:0/5.20::gentoo USE="-berkdb
> -debug -doc gdbm -ithreads" 0 KiB
>
> Total: 1 package (1 reinstall), Size of downloads: 0 KiB
>
> WARNING: One or more updates/rebuilds have been skipped due to a
> dependency conflict:
[...]
Try running "emerge -C $(qlist -IC virtual/perl-) first, then run a
deep update. If that fails, add vim and other packages to the list:
# emerge -1Dpuv perl
# emerge -1Dpuv perl vim ...
Also check your world file if it accidentally includes perl
dependencies. If deps need to be removed by emerge during an updates,
it will only do it if it is absent in the world file. That is, remove
"virtual/perl-*" and "perl-core/*" from the world file unless you added
them on purpose.
--
Regards,
Kai
Replies to list-only preferred.
