Re: [gentoo-user] And thus the emerge spake...

[Alan McKinnon]

On 17/04/2016 14:09, meino.cra...@gmx.de wrote:
> Mick  [16-04-17 14:00]:
>> On Sunday 17 Apr 2016 11:44:50 Alan McKinnon wrote:
>>> On 17/04/2016 11:36, meino.cra...@gmx.de wrote:
 Alan McKinnon  [16-04-17 11:08]:
> On 17/04/2016 05:45, meino.cra...@gmx.de wrote:
>> Hi,
>>
>> ...and the novice was buffled and even the master shifted a little bit
>> after recognizing this words of the eternal being named emerge.
>> I know, that there is a difference in knowing the path and walking the
>> path, but it seems that I am not supposed to understand this:
>>
>>
>> These are the packages that would be merged, in reverse order:
>>
>> Calculating dependencies... done!
>>
>> Total: 0 packages, Size of downloads: 0 KiB
>>
>> WARNING: One or more updates/rebuilds have been skipped due to a
>> dependency conflict:
>>
>> dev-util/boost-build:0
>>
>>   (dev-util/boost-build-1.60.0:0/0::gentoo, ebuild scheduled for merge)
>>   conflicts with>>>   
>> =dev-util/boost-build-1.58* required by
>> (dev-libs/boost-1.58.0-r1:0/1.58.0::gentoo, installed) ^   
>>  ^
>>
>> !!! The following update has been skipped due to unsatisfied
>> dependencies:
>>
>> dev-libs/boost:0
>>
>> !!! All ebuilds that could satisfy "=dev-util/boost-build-1.60*" have
>> been masked. !!! One of the following masked packages is required to
>> complete your request: - dev-util/boost-build-1.60.0::gentoo (masked
>> by: )
>>
>>
>> For me it looks like boost not beeing updated/reinstalled because of
>> another version of boost, which depends on boost.
>>
>> HELP, I need somebody, HELP, not just anybody hee-eee-eelp u!
>>
>> Thanks for any HELP in advance! May the source be with you...
>> Best regards,
>> Meino
>
> Hah! That's one of those blockers that makes little or no sense.
>
>
> boost has this dep:
>
> DEPEND="${RDEPEND}
>
> =dev-util/boost-build-${MAJOR_V}*"
>
> and boost-build does not depend on boost.
>
> So, logically you'd expect boost to want to upgrade to 1.60, notice
> boost-build's dep and upgrade boost-build as well to match. But it
> doesn't, because boost-build-1.60 is masked for  reason.
>
> It really looks and smells like a bug in emerge[1] when updating world
> where it considers boost-build first, fixes the version to use to match
> current boost, and then can't find a way to upgrade boost.
>
> Solution would seem to be to emerge -C either of them and let portage
> get on with it. Or upgrade just upgrade boost-build by itself then do
> world
>
>
> [1] I wouldn't go so far as to call it a "bug" as such, because nothing
> in the spec requires a package manager to guarantee that it will always
> find the best way to upgrade everything. It only needs to keep the
> system consistent with the ebuilds it has.

 Hi Alan,

 thanks for your reply! :)

 ...and I thought it was me being too limited to see the real truth
 behind that what it is The Matrix.

 But it was only a deja-vuoh wait! It was NO deja-vu ... no
 glitch in The Matrix...we had similiar emerge-ncies in the past. ;)

 I will see how far I can go...I was warned to use 060 of boost...

 Best regards,
 Meino
>>>
>>> It reminds me of many years back with two packages that depend on each
>>> other and portage couldn't deal with updating both at the same time.
>>>
>>> emerge -C got a lot of use back then :-)
>>
>> Don't forget to use -1aDv when you emerge boost manually as Alan suggested, 
>> unless for some reason you want boost in your world file.
>>
>> -- 
>> Regards,
>> Mick
> 
> 
> 
> Hi Mick,
> 
> thanks for the warning! Will do so... :)

-1 is fine, but don't use -D in that manual step; you do not want deep here.

That happens later when you do a regular world update


-- 
Alan McKinnon
alan.mckin...@gmail.com

Re: [gentoo-user] And thus the emerge spake...

[Dale]

Neil Bothwick wrote:
> On Sun, 17 Apr 2016 10:32:02 -0500, Dale wrote:
>
>> I might add, I added --oneshot to my make.conf command for emerge a long
>> time ago.  When I really want something in the world file, I add it with
>> the --select y option on the command line, add -n if already installed. 
> Good idea, but you can use -n with packages that aren't installed and
> portage will install them as well as adding them to @world.
>
>

Ahhh.  I didn't know that part.  That's neat too.

Dale

:-)  :-) 

Re: [gentoo-user] And thus the emerge spake...

[Neil Bothwick]

On Sun, 17 Apr 2016 10:32:02 -0500, Dale wrote:

> I might add, I added --oneshot to my make.conf command for emerge a long
> time ago.  When I really want something in the world file, I add it with
> the --select y option on the command line, add -n if already installed. 

Good idea, but you can use -n with packages that aren't installed and
portage will install them as well as adding them to @world.


-- 
Neil Bothwick

Accordion: a bagpipe with pleats.


pgpfYRAl065ys.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] And thus the emerge spake...

[Dale]

meino.cra...@gmx.de wrote:
> Mick  [16-04-17 14:00]:
>> On Sunday 17 Apr 2016 11:44:50 Alan McKinnon wrote:
>>> On 17/04/2016 11:36, meino.cra...@gmx.de wrote:
 Alan McKinnon  [16-04-17 11:08]:
> On 17/04/2016 05:45, meino.cra...@gmx.de wrote:
>> Hi,
>>
>> ...and the novice was buffled and even the master shifted a little bit
>> after recognizing this words of the eternal being named emerge.
>> I know, that there is a difference in knowing the path and walking the
>> path, but it seems that I am not supposed to understand this:
>>
>>
>> These are the packages that would be merged, in reverse order:
>>
>> Calculating dependencies... done!
>>
>> Total: 0 packages, Size of downloads: 0 KiB
>>
>> WARNING: One or more updates/rebuilds have been skipped due to a
>> dependency conflict:
>>
>> dev-util/boost-build:0
>>
>>   (dev-util/boost-build-1.60.0:0/0::gentoo, ebuild scheduled for merge)
>>   conflicts with>>>   
>> =dev-util/boost-build-1.58* required by
>> (dev-libs/boost-1.58.0-r1:0/1.58.0::gentoo, installed) ^   
>>  ^
>>
>> !!! The following update has been skipped due to unsatisfied
>> dependencies:
>>
>> dev-libs/boost:0
>>
>> !!! All ebuilds that could satisfy "=dev-util/boost-build-1.60*" have
>> been masked. !!! One of the following masked packages is required to
>> complete your request: - dev-util/boost-build-1.60.0::gentoo (masked
>> by: )
>>
>>
>> For me it looks like boost not beeing updated/reinstalled because of
>> another version of boost, which depends on boost.
>>
>> HELP, I need somebody, HELP, not just anybody hee-eee-eelp u!
>>
>> Thanks for any HELP in advance! May the source be with you...
>> Best regards,
>> Meino
> Hah! That's one of those blockers that makes little or no sense.
>
>
> boost has this dep:
>
> DEPEND="${RDEPEND}
>
> =dev-util/boost-build-${MAJOR_V}*"
>
> and boost-build does not depend on boost.
>
> So, logically you'd expect boost to want to upgrade to 1.60, notice
> boost-build's dep and upgrade boost-build as well to match. But it
> doesn't, because boost-build-1.60 is masked for  reason.
>
> It really looks and smells like a bug in emerge[1] when updating world
> where it considers boost-build first, fixes the version to use to match
> current boost, and then can't find a way to upgrade boost.
>
> Solution would seem to be to emerge -C either of them and let portage
> get on with it. Or upgrade just upgrade boost-build by itself then do
> world
>
>
> [1] I wouldn't go so far as to call it a "bug" as such, because nothing
> in the spec requires a package manager to guarantee that it will always
> find the best way to upgrade everything. It only needs to keep the
> system consistent with the ebuilds it has.
 Hi Alan,

 thanks for your reply! :)

 ...and I thought it was me being too limited to see the real truth
 behind that what it is The Matrix.

 But it was only a deja-vuoh wait! It was NO deja-vu ... no
 glitch in The Matrix...we had similiar emerge-ncies in the past. ;)

 I will see how far I can go...I was warned to use 060 of boost...

 Best regards,
 Meino
>>> It reminds me of many years back with two packages that depend on each
>>> other and portage couldn't deal with updating both at the same time.
>>>
>>> emerge -C got a lot of use back then :-)
>> Don't forget to use -1aDv when you emerge boost manually as Alan suggested, 
>> unless for some reason you want boost in your world file.
>>
>> -- 
>> Regards,
>> Mick
>
>
> Hi Mick,
>
> thanks for the warning! Will do so... :)
>
> Best regards,
> Meino
>
>

I might add, I added --oneshot to my make.conf command for emerge a long
time ago.  When I really want something in the world file, I add it with
the --select y option on the command line, add -n if already installed. 
My thinking, I have to put in effort to add something to the world file
instead of putting in effort to not do it.  I also don't have to worry
about forgetting to use -1 either.  If I forget to use --select, I'll
see it when I run --depclean.  Y'all do look at the list --depclean
spits out first right?  lol 

Since I did that, my world file has been improved a LOT.  Before that,
it was a train wreck. 

Dale

:-)  :-)

Re: [gentoo-user] And thus the emerge spake...

[Meino . Cramer]

Mick  [16-04-17 14:00]:
> On Sunday 17 Apr 2016 11:44:50 Alan McKinnon wrote:
> > On 17/04/2016 11:36, meino.cra...@gmx.de wrote:
> > > Alan McKinnon  [16-04-17 11:08]:
> > >> On 17/04/2016 05:45, meino.cra...@gmx.de wrote:
> > >>> Hi,
> > >>> 
> > >>> ...and the novice was buffled and even the master shifted a little bit
> > >>> after recognizing this words of the eternal being named emerge.
> > >>> I know, that there is a difference in knowing the path and walking the
> > >>> path, but it seems that I am not supposed to understand this:
> > >>> 
> > >>> 
> > >>> These are the packages that would be merged, in reverse order:
> > >>> 
> > >>> Calculating dependencies... done!
> > >>> 
> > >>> Total: 0 packages, Size of downloads: 0 KiB
> > >>> 
> > >>> WARNING: One or more updates/rebuilds have been skipped due to a
> > >>> dependency conflict:
> > >>> 
> > >>> dev-util/boost-build:0
> > >>> 
> > >>>   (dev-util/boost-build-1.60.0:0/0::gentoo, ebuild scheduled for merge)
> > >>>   conflicts with>>>   
> > >>> =dev-util/boost-build-1.58* required by
> > >>> (dev-libs/boost-1.58.0-r1:0/1.58.0::gentoo, installed) ^   
> > >>>  ^
> > >>> 
> > >>> !!! The following update has been skipped due to unsatisfied
> > >>> dependencies:
> > >>> 
> > >>> dev-libs/boost:0
> > >>> 
> > >>> !!! All ebuilds that could satisfy "=dev-util/boost-build-1.60*" have
> > >>> been masked. !!! One of the following masked packages is required to
> > >>> complete your request: - dev-util/boost-build-1.60.0::gentoo (masked
> > >>> by: )
> > >>> 
> > >>> 
> > >>> For me it looks like boost not beeing updated/reinstalled because of
> > >>> another version of boost, which depends on boost.
> > >>> 
> > >>> HELP, I need somebody, HELP, not just anybody hee-eee-eelp u!
> > >>> 
> > >>> Thanks for any HELP in advance! May the source be with you...
> > >>> Best regards,
> > >>> Meino
> > >> 
> > >> Hah! That's one of those blockers that makes little or no sense.
> > >> 
> > >> 
> > >> boost has this dep:
> > >> 
> > >> DEPEND="${RDEPEND}
> > >> 
> > >> =dev-util/boost-build-${MAJOR_V}*"
> > >> 
> > >> and boost-build does not depend on boost.
> > >> 
> > >> So, logically you'd expect boost to want to upgrade to 1.60, notice
> > >> boost-build's dep and upgrade boost-build as well to match. But it
> > >> doesn't, because boost-build-1.60 is masked for  reason.
> > >> 
> > >> It really looks and smells like a bug in emerge[1] when updating world
> > >> where it considers boost-build first, fixes the version to use to match
> > >> current boost, and then can't find a way to upgrade boost.
> > >> 
> > >> Solution would seem to be to emerge -C either of them and let portage
> > >> get on with it. Or upgrade just upgrade boost-build by itself then do
> > >> world
> > >> 
> > >> 
> > >> [1] I wouldn't go so far as to call it a "bug" as such, because nothing
> > >> in the spec requires a package manager to guarantee that it will always
> > >> find the best way to upgrade everything. It only needs to keep the
> > >> system consistent with the ebuilds it has.
> > > 
> > > Hi Alan,
> > > 
> > > thanks for your reply! :)
> > > 
> > > ...and I thought it was me being too limited to see the real truth
> > > behind that what it is The Matrix.
> > > 
> > > But it was only a deja-vuoh wait! It was NO deja-vu ... no
> > > glitch in The Matrix...we had similiar emerge-ncies in the past. ;)
> > > 
> > > I will see how far I can go...I was warned to use 060 of boost...
> > > 
> > > Best regards,
> > > Meino
> > 
> > It reminds me of many years back with two packages that depend on each
> > other and portage couldn't deal with updating both at the same time.
> > 
> > emerge -C got a lot of use back then :-)
> 
> Don't forget to use -1aDv when you emerge boost manually as Alan suggested, 
> unless for some reason you want boost in your world file.
> 
> -- 
> Regards,
> Mick



Hi Mick,

thanks for the warning! Will do so... :)

Best regards,
Meino

Re: [gentoo-user] And thus the emerge spake...

[Mick]

On Sunday 17 Apr 2016 11:44:50 Alan McKinnon wrote:
> On 17/04/2016 11:36, meino.cra...@gmx.de wrote:
> > Alan McKinnon  [16-04-17 11:08]:
> >> On 17/04/2016 05:45, meino.cra...@gmx.de wrote:
> >>> Hi,
> >>> 
> >>> ...and the novice was buffled and even the master shifted a little bit
> >>> after recognizing this words of the eternal being named emerge.
> >>> I know, that there is a difference in knowing the path and walking the
> >>> path, but it seems that I am not supposed to understand this:
> >>> 
> >>> 
> >>> These are the packages that would be merged, in reverse order:
> >>> 
> >>> Calculating dependencies... done!
> >>> 
> >>> Total: 0 packages, Size of downloads: 0 KiB
> >>> 
> >>> WARNING: One or more updates/rebuilds have been skipped due to a
> >>> dependency conflict:
> >>> 
> >>> dev-util/boost-build:0
> >>> 
> >>>   (dev-util/boost-build-1.60.0:0/0::gentoo, ebuild scheduled for merge)
> >>>   conflicts with>>>   
> >>> =dev-util/boost-build-1.58* required by
> >>> (dev-libs/boost-1.58.0-r1:0/1.58.0::gentoo, installed) ^   
> >>>  ^
> >>> 
> >>> !!! The following update has been skipped due to unsatisfied
> >>> dependencies:
> >>> 
> >>> dev-libs/boost:0
> >>> 
> >>> !!! All ebuilds that could satisfy "=dev-util/boost-build-1.60*" have
> >>> been masked. !!! One of the following masked packages is required to
> >>> complete your request: - dev-util/boost-build-1.60.0::gentoo (masked
> >>> by: )
> >>> 
> >>> 
> >>> For me it looks like boost not beeing updated/reinstalled because of
> >>> another version of boost, which depends on boost.
> >>> 
> >>> HELP, I need somebody, HELP, not just anybody hee-eee-eelp u!
> >>> 
> >>> Thanks for any HELP in advance! May the source be with you...
> >>> Best regards,
> >>> Meino
> >> 
> >> Hah! That's one of those blockers that makes little or no sense.
> >> 
> >> 
> >> boost has this dep:
> >> 
> >> DEPEND="${RDEPEND}
> >> 
> >> =dev-util/boost-build-${MAJOR_V}*"
> >> 
> >> and boost-build does not depend on boost.
> >> 
> >> So, logically you'd expect boost to want to upgrade to 1.60, notice
> >> boost-build's dep and upgrade boost-build as well to match. But it
> >> doesn't, because boost-build-1.60 is masked for  reason.
> >> 
> >> It really looks and smells like a bug in emerge[1] when updating world
> >> where it considers boost-build first, fixes the version to use to match
> >> current boost, and then can't find a way to upgrade boost.
> >> 
> >> Solution would seem to be to emerge -C either of them and let portage
> >> get on with it. Or upgrade just upgrade boost-build by itself then do
> >> world
> >> 
> >> 
> >> [1] I wouldn't go so far as to call it a "bug" as such, because nothing
> >> in the spec requires a package manager to guarantee that it will always
> >> find the best way to upgrade everything. It only needs to keep the
> >> system consistent with the ebuilds it has.
> > 
> > Hi Alan,
> > 
> > thanks for your reply! :)
> > 
> > ...and I thought it was me being too limited to see the real truth
> > behind that what it is The Matrix.
> > 
> > But it was only a deja-vuoh wait! It was NO deja-vu ... no
> > glitch in The Matrix...we had similiar emerge-ncies in the past. ;)
> > 
> > I will see how far I can go...I was warned to use 060 of boost...
> > 
> > Best regards,
> > Meino
> 
> It reminds me of many years back with two packages that depend on each
> other and portage couldn't deal with updating both at the same time.
> 
> emerge -C got a lot of use back then :-)

Don't forget to use -1aDv when you emerge boost manually as Alan suggested, 
unless for some reason you want boost in your world file.

-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] And thus the emerge spake...

[Alan McKinnon]

On 17/04/2016 11:36, meino.cra...@gmx.de wrote:
> Alan McKinnon  [16-04-17 11:08]:
>> On 17/04/2016 05:45, meino.cra...@gmx.de wrote:
>>>
>>> Hi,
>>>
>>> ...and the novice was buffled and even the master shifted a little bit
>>> after recognizing this words of the eternal being named emerge.
>>> I know, that there is a difference in knowing the path and walking the
>>> path, but it seems that I am not supposed to understand this:
>>>
>>>
>>> These are the packages that would be merged, in reverse order:
>>>
>>> Calculating dependencies... done!
>>>
>>> Total: 0 packages, Size of downloads: 0 KiB
>>>
>>> WARNING: One or more updates/rebuilds have been skipped due to a dependency 
>>> conflict:
>>>
>>> dev-util/boost-build:0
>>>
>>>   (dev-util/boost-build-1.60.0:0/0::gentoo, ebuild scheduled for merge) 
>>> conflicts with
>>> =dev-util/boost-build-1.58* required by 
>>> (dev-libs/boost-1.58.0-r1:0/1.58.0::gentoo, installed)
>>> ^ ^
>>>
>>>
>>> !!! The following update has been skipped due to unsatisfied dependencies:
>>>
>>> dev-libs/boost:0
>>>
>>> !!! All ebuilds that could satisfy "=dev-util/boost-build-1.60*" have been 
>>> masked.
>>> !!! One of the following masked packages is required to complete your 
>>> request:
>>> - dev-util/boost-build-1.60.0::gentoo (masked by: )
>>>
>>>
>>> For me it looks like boost not beeing updated/reinstalled because of
>>> another version of boost, which depends on boost.
>>>
>>> HELP, I need somebody, HELP, not just anybody hee-eee-eelp u!
>>>
>>> Thanks for any HELP in advance! May the source be with you...
>>> Best regards,
>>> Meino
>>>
>>>
>>>
>>
>>
>> Hah! That's one of those blockers that makes little or no sense.
>>
>>
>> boost has this dep:
>>
>> DEPEND="${RDEPEND}
>> =dev-util/boost-build-${MAJOR_V}*"
>>
>> and boost-build does not depend on boost.
>>
>> So, logically you'd expect boost to want to upgrade to 1.60, notice
>> boost-build's dep and upgrade boost-build as well to match. But it
>> doesn't, because boost-build-1.60 is masked for  reason.
>>
>> It really looks and smells like a bug in emerge[1] when updating world
>> where it considers boost-build first, fixes the version to use to match
>> current boost, and then can't find a way to upgrade boost.
>>
>> Solution would seem to be to emerge -C either of them and let portage
>> get on with it. Or upgrade just upgrade boost-build by itself then do world
>>
>>
>> [1] I wouldn't go so far as to call it a "bug" as such, because nothing
>> in the spec requires a package manager to guarantee that it will always
>> find the best way to upgrade everything. It only needs to keep the
>> system consistent with the ebuilds it has.
>>
>> -- 
>> Alan McKinnon
>> alan.mckin...@gmail.com
>>
>>
> 
> Hi Alan,
> 
> thanks for your reply! :)
> 
> ...and I thought it was me being too limited to see the real truth
> behind that what it is The Matrix.
> 
> But it was only a deja-vuoh wait! It was NO deja-vu ... no 
> glitch in The Matrix...we had similiar emerge-ncies in the past. ;)
> 
> I will see how far I can go...I was warned to use 060 of boost...
> 
> Best regards,
> Meino
> 
> 
> 

It reminds me of many years back with two packages that depend on each
other and portage couldn't deal with updating both at the same time.

emerge -C got a lot of use back then :-)

-- 
Alan McKinnon
alan.mckin...@gmail.com

Re: [gentoo-user] And thus the emerge spake...

[Meino . Cramer]

Alan McKinnon  [16-04-17 11:08]:
> On 17/04/2016 05:45, meino.cra...@gmx.de wrote:
> > 
> > Hi,
> > 
> > ...and the novice was buffled and even the master shifted a little bit
> > after recognizing this words of the eternal being named emerge.
> > I know, that there is a difference in knowing the path and walking the
> > path, but it seems that I am not supposed to understand this:
> > 
> > 
> > These are the packages that would be merged, in reverse order:
> > 
> > Calculating dependencies... done!
> > 
> > Total: 0 packages, Size of downloads: 0 KiB
> > 
> > WARNING: One or more updates/rebuilds have been skipped due to a dependency 
> > conflict:
> > 
> > dev-util/boost-build:0
> > 
> >   (dev-util/boost-build-1.60.0:0/0::gentoo, ebuild scheduled for merge) 
> > conflicts with
> > =dev-util/boost-build-1.58* required by 
> > (dev-libs/boost-1.58.0-r1:0/1.58.0::gentoo, installed)
> > ^ ^
> > 
> > 
> > !!! The following update has been skipped due to unsatisfied dependencies:
> > 
> > dev-libs/boost:0
> > 
> > !!! All ebuilds that could satisfy "=dev-util/boost-build-1.60*" have been 
> > masked.
> > !!! One of the following masked packages is required to complete your 
> > request:
> > - dev-util/boost-build-1.60.0::gentoo (masked by: )
> > 
> > 
> > For me it looks like boost not beeing updated/reinstalled because of
> > another version of boost, which depends on boost.
> > 
> > HELP, I need somebody, HELP, not just anybody hee-eee-eelp u!
> > 
> > Thanks for any HELP in advance! May the source be with you...
> > Best regards,
> > Meino
> > 
> > 
> > 
> 
> 
> Hah! That's one of those blockers that makes little or no sense.
> 
> 
> boost has this dep:
> 
> DEPEND="${RDEPEND}
> =dev-util/boost-build-${MAJOR_V}*"
> 
> and boost-build does not depend on boost.
> 
> So, logically you'd expect boost to want to upgrade to 1.60, notice
> boost-build's dep and upgrade boost-build as well to match. But it
> doesn't, because boost-build-1.60 is masked for  reason.
> 
> It really looks and smells like a bug in emerge[1] when updating world
> where it considers boost-build first, fixes the version to use to match
> current boost, and then can't find a way to upgrade boost.
> 
> Solution would seem to be to emerge -C either of them and let portage
> get on with it. Or upgrade just upgrade boost-build by itself then do world
> 
> 
> [1] I wouldn't go so far as to call it a "bug" as such, because nothing
> in the spec requires a package manager to guarantee that it will always
> find the best way to upgrade everything. It only needs to keep the
> system consistent with the ebuilds it has.
> 
> -- 
> Alan McKinnon
> alan.mckin...@gmail.com
> 
> 

Hi Alan,

thanks for your reply! :)

...and I thought it was me being too limited to see the real truth
behind that what it is The Matrix.

But it was only a deja-vuoh wait! It was NO deja-vu ... no 
glitch in The Matrix...we had similiar emerge-ncies in the past. ;)

I will see how far I can go...I was warned to use 060 of boost...

Best regards,
Meino

Re: [gentoo-user] And thus the emerge spake...

[Alan McKinnon]

On 17/04/2016 11:00, Alan McKinnon wrote:
> On 17/04/2016 05:45, meino.cra...@gmx.de wrote:
>>
>> Hi,
>>
>> ...and the novice was buffled and even the master shifted a little bit
>> after recognizing this words of the eternal being named emerge.
>> I know, that there is a difference in knowing the path and walking the
>> path, but it seems that I am not supposed to understand this:
>>
>>
>> These are the packages that would be merged, in reverse order:
>>
>> Calculating dependencies... done!
>>
>> Total: 0 packages, Size of downloads: 0 KiB
>>
>> WARNING: One or more updates/rebuilds have been skipped due to a dependency 
>> conflict:
>>
>> dev-util/boost-build:0
>>
>>   (dev-util/boost-build-1.60.0:0/0::gentoo, ebuild scheduled for merge) 
>> conflicts with
>> =dev-util/boost-build-1.58* required by 
>> (dev-libs/boost-1.58.0-r1:0/1.58.0::gentoo, installed)
>> ^ ^
>>
>>
>> !!! The following update has been skipped due to unsatisfied dependencies:
>>
>> dev-libs/boost:0
>>
>> !!! All ebuilds that could satisfy "=dev-util/boost-build-1.60*" have been 
>> masked.
>> !!! One of the following masked packages is required to complete your 
>> request:
>> - dev-util/boost-build-1.60.0::gentoo (masked by: )
>>
>>
>> For me it looks like boost not beeing updated/reinstalled because of
>> another version of boost, which depends on boost.
>>
>> HELP, I need somebody, HELP, not just anybody hee-eee-eelp u!
>>
>> Thanks for any HELP in advance! May the source be with you...
>> Best regards,
>> Meino
>>
>>
>>
> 
> 
> Hah! That's one of those blockers that makes little or no sense.
> 
> 
> boost has this dep:
> 
> DEPEND="${RDEPEND}
> =dev-util/boost-build-${MAJOR_V}*"
> 
> and boost-build does not depend on boost.
> 
> So, logically you'd expect boost to want to upgrade to 1.60, notice
> boost-build's dep and upgrade boost-build as well to match. But it
> doesn't, because boost-build-1.60 is masked for  reason.
> 
> It really looks and smells like a bug in emerge[1] when updating world
> where it considers boost-build first, fixes the version to use to match
> current boost, and then can't find a way to upgrade boost.
> 
> Solution would seem to be to emerge -C either of them and let portage
> get on with it. Or upgrade just upgrade boost-build by itself then do world

turns out that is not sufficient. This seems to work for me:

emerge boost-build
emerge boost

> 
> 
> [1] I wouldn't go so far as to call it a "bug" as such, because nothing
> in the spec requires a package manager to guarantee that it will always
> find the best way to upgrade everything. It only needs to keep the
> system consistent with the ebuilds it has.
> 


-- 
Alan McKinnon
alan.mckin...@gmail.com

Re: [gentoo-user] And thus the emerge spake...

[Alan McKinnon]

On 17/04/2016 05:45, meino.cra...@gmx.de wrote:
> 
> Hi,
> 
> ...and the novice was buffled and even the master shifted a little bit
> after recognizing this words of the eternal being named emerge.
> I know, that there is a difference in knowing the path and walking the
> path, but it seems that I am not supposed to understand this:
> 
> 
> These are the packages that would be merged, in reverse order:
> 
> Calculating dependencies... done!
> 
> Total: 0 packages, Size of downloads: 0 KiB
> 
> WARNING: One or more updates/rebuilds have been skipped due to a dependency 
> conflict:
> 
> dev-util/boost-build:0
> 
>   (dev-util/boost-build-1.60.0:0/0::gentoo, ebuild scheduled for merge) 
> conflicts with
> =dev-util/boost-build-1.58* required by 
> (dev-libs/boost-1.58.0-r1:0/1.58.0::gentoo, installed)
> ^ ^
> 
> 
> !!! The following update has been skipped due to unsatisfied dependencies:
> 
> dev-libs/boost:0
> 
> !!! All ebuilds that could satisfy "=dev-util/boost-build-1.60*" have been 
> masked.
> !!! One of the following masked packages is required to complete your request:
> - dev-util/boost-build-1.60.0::gentoo (masked by: )
> 
> 
> For me it looks like boost not beeing updated/reinstalled because of
> another version of boost, which depends on boost.
> 
> HELP, I need somebody, HELP, not just anybody hee-eee-eelp u!
> 
> Thanks for any HELP in advance! May the source be with you...
> Best regards,
> Meino
> 
> 
> 


Hah! That's one of those blockers that makes little or no sense.


boost has this dep:

DEPEND="${RDEPEND}
=dev-util/boost-build-${MAJOR_V}*"

and boost-build does not depend on boost.

So, logically you'd expect boost to want to upgrade to 1.60, notice
boost-build's dep and upgrade boost-build as well to match. But it
doesn't, because boost-build-1.60 is masked for  reason.

It really looks and smells like a bug in emerge[1] when updating world
where it considers boost-build first, fixes the version to use to match
current boost, and then can't find a way to upgrade boost.

Solution would seem to be to emerge -C either of them and let portage
get on with it. Or upgrade just upgrade boost-build by itself then do world


[1] I wouldn't go so far as to call it a "bug" as such, because nothing
in the spec requires a package manager to guarantee that it will always
find the best way to upgrade everything. It only needs to keep the
system consistent with the ebuilds it has.

-- 
Alan McKinnon
alan.mckin...@gmail.com

Re: [gentoo-user] And thus the emerge spake...

[Meino . Cramer]

Dale  [16-04-17 06:08]:
> meino.cra...@gmx.de wrote:
> > Hi,
> >
> > ...and the novice was buffled and even the master shifted a little bit
> > after recognizing this words of the eternal being named emerge.
> > I know, that there is a difference in knowing the path and walking the
> > path, but it seems that I am not supposed to understand this:
> >
> >
> > These are the packages that would be merged, in reverse order:
> >
> > Calculating dependencies... done!
> >
> > Total: 0 packages, Size of downloads: 0 KiB
> >
> > WARNING: One or more updates/rebuilds have been skipped due to a dependency 
> > conflict:
> >
> > dev-util/boost-build:0
> >
> >   (dev-util/boost-build-1.60.0:0/0::gentoo, ebuild scheduled for merge) 
> > conflicts with
> > =dev-util/boost-build-1.58* required by 
> > (dev-libs/boost-1.58.0-r1:0/1.58.0::gentoo, installed)
> > ^ ^
> >
> >
> > !!! The following update has been skipped due to unsatisfied dependencies:
> >
> > dev-libs/boost:0
> >
> > !!! All ebuilds that could satisfy "=dev-util/boost-build-1.60*" have been 
> > masked.
> > !!! One of the following masked packages is required to complete your 
> > request:
> > - dev-util/boost-build-1.60.0::gentoo (masked by: )
> >
> >
> > For me it looks like boost not beeing updated/reinstalled because of
> > another version of boost, which depends on boost.
> >
> > HELP, I need somebody, HELP, not just anybody hee-eee-eelp u!
> >
> > Thanks for any HELP in advance! May the source be with you...
> > Best regards,
> > Meino
> >
> >
> 
> 
> Notice this line.
> 
> =dev-util/boost-build-1.58* required by 
> (dev-libs/boost-1.58.0-r1:0/1.58.0::gentoo, installed)
> ^ ^
> 
> Note the ^ and the ^ part.  That seems to be the important part. 
> Me, I would check package.* files and see if there is a entry for boost
> in there.  It seems to be pointing out that there is a problem with that
> specific version and a = sign somewhere.  It could be a keyword that
> only applies to that version and it needs a newer version keyworded or
> there could be a entry in package.use that has a version attached to
> it.  I might add, I try not to put versions on packages in package.use. 
> It just seems to lead to trouble.  May want to check package.mask too if
> you find nothing in the other files. 
> 
> Also a -t might help too.  Maybe.
> 
> If that doesn't help, Alan M. will come along with his crystal ball
> soon, I hope.  
> 
> Dale
> 
> :-)  :-) 
> 
> 

Hi Simon, hi Dale,

thanks for your replies ! :)

I will check first for package* occurences of boost, since this may be
the root of all evil.

If nothing helps, I will be back ;)

Best regards
Meino

Re: [gentoo-user] And thus the emerge spake...

[Paul Colquhoun]

On Sun, 17 Apr 2016 05:45:15 meino.cra...@gmx.de wrote:
> Hi,
> 
> ...and the novice was buffled and even the master shifted a little bit
> after recognizing this words of the eternal being named emerge.
> I know, that there is a difference in knowing the path and walking the
> path, but it seems that I am not supposed to understand this:
> 
> 
> These are the packages that would be merged, in reverse order:
> 
> Calculating dependencies... done!
> 
> Total: 0 packages, Size of downloads: 0 KiB
> 
> WARNING: One or more updates/rebuilds have been skipped due to a dependency
> conflict:
> 
> dev-util/boost-build:0
> 
>   (dev-util/boost-build-1.60.0:0/0::gentoo, ebuild scheduled for merge)
> conflicts with =dev-util/boost-build-1.58* required by
> (dev-libs/boost-1.58.0-r1:0/1.58.0::gentoo, installed) ^   
>  ^
> 
> 
> !!! The following update has been skipped due to unsatisfied dependencies:
> 
> dev-libs/boost:0
> 
> !!! All ebuilds that could satisfy "=dev-util/boost-build-1.60*" have been
> masked. !!! One of the following masked packages is required to complete
> your request: - dev-util/boost-build-1.60.0::gentoo (masked by: )
> 
> 
> For me it looks like boost not beeing updated/reinstalled because of
> another version of boost, which depends on boost.
> 
> HELP, I need somebody, HELP, not just anybody hee-eee-eelp u!
> 
> Thanks for any HELP in advance! May the source be with you...
> Best regards,
> Meino


Be careful upgrading boost & boost-build. I updated to 1,60.0 a little while 
ago, and akonadi stopped working until I went back to version 1.58.0

This also stopped anything that depends on akonadi, things like kmail.


-- 
Reverend Paul Colquhoun, ULC. http://andor.dropbear.id.au/
  Asking for technical help in newsgroups?  Read this first:
 http://catb.org/~esr/faqs/smart-questions.html#intro

Re: [gentoo-user] And thus the emerge spake...

[Dale]

meino.cra...@gmx.de wrote:
> Hi,
>
> ...and the novice was buffled and even the master shifted a little bit
> after recognizing this words of the eternal being named emerge.
> I know, that there is a difference in knowing the path and walking the
> path, but it seems that I am not supposed to understand this:
>
>
> These are the packages that would be merged, in reverse order:
>
> Calculating dependencies... done!
>
> Total: 0 packages, Size of downloads: 0 KiB
>
> WARNING: One or more updates/rebuilds have been skipped due to a dependency 
> conflict:
>
> dev-util/boost-build:0
>
>   (dev-util/boost-build-1.60.0:0/0::gentoo, ebuild scheduled for merge) 
> conflicts with
> =dev-util/boost-build-1.58* required by 
> (dev-libs/boost-1.58.0-r1:0/1.58.0::gentoo, installed)
> ^ ^
>
>
> !!! The following update has been skipped due to unsatisfied dependencies:
>
> dev-libs/boost:0
>
> !!! All ebuilds that could satisfy "=dev-util/boost-build-1.60*" have been 
> masked.
> !!! One of the following masked packages is required to complete your request:
> - dev-util/boost-build-1.60.0::gentoo (masked by: )
>
>
> For me it looks like boost not beeing updated/reinstalled because of
> another version of boost, which depends on boost.
>
> HELP, I need somebody, HELP, not just anybody hee-eee-eelp u!
>
> Thanks for any HELP in advance! May the source be with you...
> Best regards,
> Meino
>
>


Notice this line.

=dev-util/boost-build-1.58* required by 
(dev-libs/boost-1.58.0-r1:0/1.58.0::gentoo, installed)
^ ^

Note the ^ and the ^ part.  That seems to be the important part. 
Me, I would check package.* files and see if there is a entry for boost
in there.  It seems to be pointing out that there is a problem with that
specific version and a = sign somewhere.  It could be a keyword that
only applies to that version and it needs a newer version keyworded or
there could be a entry in package.use that has a version attached to
it.  I might add, I try not to put versions on packages in package.use. 
It just seems to lead to trouble.  May want to check package.mask too if
you find nothing in the other files. 

Also a -t might help too.  Maybe.

If that doesn't help, Alan M. will come along with his crystal ball
soon, I hope.  

Dale

:-)  :-) 

Re: [gentoo-user] And thus the emerge spake...

[Simon Thelen]

On 16-04-17 at 05:45, meino.cra...@gmx.de wrote:
[..]
> WARNING: One or more updates/rebuilds have been skipped due to a dependency 
> conflict:
> 
> dev-util/boost-build:0
> 
>   (dev-util/boost-build-1.60.0:0/0::gentoo, ebuild scheduled for merge) 
> conflicts with
> =dev-util/boost-build-1.58* required by 
> (dev-libs/boost-1.58.0-r1:0/1.58.0::gentoo, installed)
> ^ ^
> 
> 
> !!! The following update has been skipped due to unsatisfied dependencies:
> 
> dev-libs/boost:0
> 
> !!! All ebuilds that could satisfy "=dev-util/boost-build-1.60*" have been 
> masked.
> !!! One of the following masked packages is required to complete your request:
> - dev-util/boost-build-1.60.0::gentoo (masked by: )
The problem is that emerge thinks boost is masked for whatever reason
 
> For me it looks like boost not beeing updated/reinstalled because of
> another version of boost, which depends on boost.
I had a similar issue on one of my computers. Running `emerge -1
=dev-util/boost-build-1.60.0 =dev-libs/boost-1.60.0' fixed it.

Only happened on one of my computers and increasing backtracking didn't
help so I'm not sure exactly why it didn't want to update, but
explicitly telling emerge to install it seemed to help for me.

-- 
Simon Thelen