Hi.
Perl packages family use extremely annoying dependency definition.
See example below.
The question is "what is the correct way to solve this dependency conflict?". I
don't like to add all "conflicts" into install list in cli. Is there a way to
force update of all this "perl sh.t/stuff"? A
emerge -uDNavq world is runs without errors:
Nothing to merge; quitting.
Before running "emerge --depclean"
I try to double check with: emerge --update --newuse --deep @world
and run into conflict:
WARNING: One or more updates/rebuilds have been skipped due to a dependency
conflict:
sys-lib
On Fri, Sep 30, 2016 at 11:32 AM, Dmitry Bogun wrote:
> Hi.
>
> Perl packages family use extremely annoying dependency definition.
>
> See example below.
>
> The question is "what is the correct way to solve this dependency conflict?".
> I don't like to add all "conflicts" into install list in cl
On Fri, 30 Sep 2016 11:32:18 +0300, Dmitry Bogun wrote:
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild U ] app-shells/bash-4.3_p46-r1 [4.3_p42-r1]
> [ebuild R] dev-lang/perl-5.20.2
>
> WARNING: One or more updates/rebuilds have
On Wed, 10 Jan 2024 at 03:36, wrote:
> The error messages indicate that there are conflicting versions and USE flags
> for these packages.
> Any hint how to resolve it?
The messages say that python requires USE=berkdb on sys-libs/gdbm,
while hylafaxplus requires an older version of media-libs/ti
On 1/9/24 23:44, Arve Barsnes wrote:
On Wed, 10 Jan 2024 at 03:36, wrote:
The error messages indicate that there are conflicting versions and USE flags
for these packages.
Any hint how to resolve it?
The messages say that python requires USE=berkdb on sys-libs/gdbm,
while hylafaxplus require
Howdy,
I can't figure out a way around this one. Usually keywording, maybe
that should be unkeywording, a newer version works but doesn't seem to
in this case. This started as part of a emerge -uvaDN world.
Error I get:
WARNING: One or more updates/rebuilds have been skipped due to a
depende
On 14/06/2014 23:23, Dale wrote:
> Howdy,
>
> I can't figure out a way around this one. Usually keywording, maybe
> that should be unkeywording, a newer version works but doesn't seem to
> in this case. This started as part of a emerge -uvaDN world.
>
> Error I get:
>
> WARNING: One or more
Alan McKinnon wrote:
> Look closely at the deps. You don't have a blocker, you have a
> conflict. Your version of openjpeg is OK, the sub-slot operators are
> not. What's the result of "eix openjpeg"?
I get this:
root@fireball / # eix openjpeg
[U] media-libs/openjpeg
Available versions:
On 06/14/2014 05:12 PM, Dale wrote:
media-libs/openjpeg:0
(media-libs/openjpeg-1.5.1:0/0::gentoo, ebuild scheduled for merge)
conflicts with
>=media-libs/openjpeg-1.3-r2:0[abi_x86_64(-)] required by
(media-video/ffmpeg-2.2.3-r1:0/52.55.55::gentoo, installed)
The multilib stuff is a wo
John Campbell wrote:
> On 06/14/2014 05:12 PM, Dale wrote:
>>
>> media-libs/openjpeg:0
>>
>>(media-libs/openjpeg-1.5.1:0/0::gentoo, ebuild scheduled for merge)
>> conflicts with
>> >=media-libs/openjpeg-1.3-r2:0[abi_x86_64(-)] required by
>> (media-video/ffmpeg-2.2.3-r1:0/52.55.55::gentoo,
On 06/14/2014 07:10 PM, Dale wrote:
I don't have a env directory in /etc/portage and there is no
openjpeg-1.3-r2 available in the tree. I sort of think I know what you
are talking about tho. I need to create that directory structure for
openjpeg-1.4-r1 and put ABI_X86="32 x32" in the file.
S
John Campbell wrote:
> On 06/14/2014 07:10 PM, Dale wrote:
>
>> I don't have a env directory in /etc/portage and there is no
>> openjpeg-1.3-r2 available in the tree. I sort of think I know what you
>> are talking about tho. I need to create that directory structure for
>> openjpeg-1.4-r1 and put
On 06/14/2014 10:10 PM, Dale wrote:
John Campbell wrote:
On 06/14/2014 07:10 PM, Dale wrote:
I don't have a env directory in /etc/portage and there is no
openjpeg-1.3-r2 available in the tree. I sort of think I know what you
are talking about tho. I need to create that directory structure fo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 15/06/14 16:13, John Campbell wrote:
> On 06/14/2014 10:10 PM, Dale wrote: Yes, you can skip the version number.
> It should be just like the package.* directories but for env(ironment)
> variables. It wouldn't suprise me if someone renamed it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 15/06/14 16:40, wraeth wrote:
> Please, feel free to correct me if i'm wrong.
Looks like I *was* wrong - i was testing with something that seemingly wasn't
being overridden. Actually testing with PORTAGE_TMPDIR (something more global
to portage
On Sun, 15 Jun 2014 00:10:41 -0500, Dale wrote:
> Ahh. I was curious and thought about that. That version is mentioned
> in the error tho so I wasn't sure. I wonder tho, can I add that file
> and not have a version at all? Sort of like I do in package.keywords
> etc etc.
You can, but you jus
John Campbell wrote:
> On 06/14/2014 10:10 PM, Dale wrote:
>
>> Well, I have 16Gbs here. I'm not lacking for memory. If memory prices
>> were to drop a bit, I could upgrade some more. I'd have to swap out
>> what I have tho. Old mobo would only take 4GB sticks and this new one
>> will take 8GB
Neil Bothwick wrote:
> On Sun, 15 Jun 2014 00:10:41 -0500, Dale wrote:
>
>> Ahh. I was curious and thought about that. That version is mentioned
>> in the error tho so I wasn't sure. I wonder tho, can I add that file
>> and not have a version at all? Sort of like I do in package.keywords
>> et
On Sun, 15 Jun 2014 03:59:25 -0500, Dale wrote:
> > Though I would prefix the atom with ~ instead of = to cover patch
> > level updates.
> I have looked for a place where it is documented how to do that. I know
> there is a lot of ways to add packages to those files with <=> and such
> in front
Neil Bothwick wrote:
> On Sun, 15 Jun 2014 03:59:25 -0500, Dale wrote:
>
>>> Though I would prefix the atom with ~ instead of = to cover patch
>>> level updates.
>> I have looked for a place where it is documented how to do that. I know
>> there is a lot of ways to add packages to those files with
On 06/14/2014 10:23 PM, Dale wrote:
> Howdy,
>
> I can't figure out a way around this one. Usually keywording, maybe
> that should be unkeywording, a newer version works but doesn't seem to
> in this case. This started as part of a emerge -uvaDN world.
>
> Error I get:
>
> WARNING: One or more
thegeezer wrote:
>
> yay i just had the same thing happen
> i tried the ABI keyword as suggested further in the thread but it just
> made the error shorter and odder.
> in the end i just emerge -C ffmpeg openjpeg then add them all back one
> at a time.
> it's a bit of a pita but otherwise not reall
John Campbell wrote:
> On 06/14/2014 05:12 PM, Dale wrote:
>>
>> media-libs/openjpeg:0
>>
>>(media-libs/openjpeg-1.5.1:0/0::gentoo, ebuild scheduled for merge)
>> conflicts with
>> >=media-libs/openjpeg-1.3-r2:0[abi_x86_64(-)] required by
>> (media-video/ffmpeg-2.2.3-r1:0/52.55.55::gentoo,
Dale wrote:
> OK. First, corrected the version and then tried with no version at all
> as shown below. Going to start here since well, this is where this
> suggestion started. I created the files in env and deeper but either it
> isn't seeing it for some reason OR it isn't a option to change. I
25 matches
Mail list logo
