On Sun, 4 Jun 2023 22:21:54 +0200, Arve Barsnes wrote:
> > Doing my updates, most things updated but some still have conflicts.
> > Emerge is trying to tell me but I use Konsole and I think it messes up
> > the ^ bit and points to the wrong thing. I'm thinking this is a
> > USE flag problem b
Jack wrote:
> On 2023.06.04 17:22, Dale wrote:
>> Jack wrote:
>> > On 2023.06.04 15:56, Dale wrote:
>> >
>> >> Doing my updates, most things updated but some still have conflicts.
>> >> Emerge is trying to tell me but I use Konsole and I think it messes
>> >> up the ^ bit and points to the wro
On 2023.06.04 17:22, Dale wrote:
Jack wrote:
> On 2023.06.04 15:56, Dale wrote:
>
>> Doing my updates, most things updated but some still have
conflicts.
>> Emerge is trying to tell me but I use Konsole and I think it messes
>> up the ^ bit and points to the wrong thing.
> I suspect the ^
Jack wrote:
> On 2023.06.04 15:56, Dale wrote:
>
>> Doing my updates, most things updated but some still have conflicts.
>> Emerge is trying to tell me but I use Konsole and I think it messes
>> up the ^ bit and points to the wrong thing.
> I suspect the ^ assumes a fixed width font.
>
>
Arve Barsnes wrote:
> On Sun, 4 Jun 2023 at 21:56, Dale wrote:
>> Howdy,
>>
>> Doing my updates, most things updated but some still have conflicts.
>> Emerge is trying to tell me but I use Konsole and I think it messes up
>> the ^ bit and points to the wrong thing. I'm thinking this is a USE
On 2023.06.04 15:56, Dale wrote:
Doing my updates, most things updated but some still have conflicts.
Emerge is trying to tell me but I use Konsole and I think it messes
up the ^ bit and points to the wrong thing.
I suspect the ^ assumes a fixed width font.
On Sun, 4 Jun 2023 at 21:56, Dale wrote:
>
> Howdy,
>
> Doing my updates, most things updated but some still have conflicts.
> Emerge is trying to tell me but I use Konsole and I think it messes up
> the ^ bit and points to the wrong thing. I'm thinking this is a USE
> flag problem but I can'
Howdy,
Doing my updates, most things updated but some still have conflicts.
Emerge is trying to tell me but I use Konsole and I think it messes up
the ^ bit and points to the wrong thing. I'm thinking this is a USE
flag problem but I can't tell for sure. Anyone else recognize this and
make
On Sat, 17 Sep 2016 19:12:40 -0400, Philip Webb wrote:
> 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
>
> Tota
I went through the list of conflicts and made a temporary @set of packages
for emerge to re-install. Worked like a charm. A number of the conflicts
are things that should be in a "preserved libraries" type of list, they are
actually quite able to rebuild with the new perl version.
I have, however,
It doesn't look like just vim - it looks like exiftool, graphite2,
> cups-filters, gvim, and imagemagick all are blocking.
>
> I'd guess that these packages need a version bump or you need to unmask
> one of the newer builds (most likely they haven't been stabilized yet.)
>
Agree - my amd64 syste
On 09/17/2016 04:12 PM, Philip Webb wrote:
> 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-r
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
Alan McKinnon wrote:
On Friday 13 August 2010 15:36:23 Daniel Wagener wrote:
This script is hopefully not the hack, that is said to be a problem in
the future?
http://blog.flameeyes.eu/2010/06/29/stable-users-libpng-update
When flameyes says to do something X in regard to a build, a
On Friday 13 August 2010 15:36:23 Daniel Wagener wrote:
> This script is hopefully not the hack, that is said to be a problem in
> the future?
>
> http://blog.flameeyes.eu/2010/06/29/stable-users-libpng-update
When flameyes says to do something X in regard to a build, and someone else
says to d
On Friday 13 August 2010 15:36:23 Daniel Wagener wrote:
> On Fri, 13 Aug 2010 15:17:50 +0200
>
> "J. Roeleveld" wrote:
> > On Friday 13 August 2010 14:15:59 Alan McKinnon wrote:
> > > On Friday 13 August 2010 16:04:53 Frank Schwidom wrote:
> > > > Hi
> > > >
> > > > i get the error:
> > > >
> >
On Fri, 13 Aug 2010 15:17:50 +0200
"J. Roeleveld" wrote:
> On Friday 13 August 2010 14:15:59 Alan McKinnon wrote:
> > On Friday 13 August 2010 16:04:53 Frank Schwidom wrote:
> > > Hi
> > >
> > > i get the error:
> > >
> > > {
> > > !!! Multiple package instances within a single package slot hav
On Friday 13 August 2010 14:15:59 Alan McKinnon wrote:
> On Friday 13 August 2010 16:04:53 Frank Schwidom wrote:
> > Hi
> >
> > i get the error:
> >
> > {
> > !!! Multiple package instances within a single package slot have been
> > pulled
> > !!! into the dependency graph, resulting in a slot co
On Fri, Aug 13, 2010 at 7:04 AM, Frank Schwidom wrote:
> Hi
>
> i get the error:
>
> {
> !!! Multiple package instances within a single package slot have been
> pulled
> !!! into the dependency graph, resulting in a slot conflict:
>
> media-libs/libpng:0
>
> ('ebuild', '/', 'media-libs/libpng-1.4
On Friday 13 August 2010 16:04:53 Frank Schwidom wrote:
> Hi
>
> i get the error:
>
> {
> !!! Multiple package instances within a single package slot have been
> pulled
> !!! into the dependency graph, resulting in a slot conflict:
>
> media-libs/libpng:0
>
> ('ebuild', '/', 'media-libs/libpn
Hi
i get the error:
{
!!! Multiple package instances within a single package slot have been
pulled
!!! into the dependency graph, resulting in a slot conflict:
media-libs/libpng:0
('ebuild', '/', 'media-libs/libpng-1.4.3', 'merge') pulled in by
>=media-libs/libpng-1.2.43-r2:0 required by
21 matches
Mail list logo
