Dependency not found (because installed via portage)

Anything that pertains to Entropy, Equo or Sulfur

Moderator: Moderators

Dependency not found (because installed via portage)

Postby toster » Thu Jan 16, 2014 14:22

I did use portage to build a package with different use flags before, but this is the first time I have run into any problems with it:

I need the -mpi flag with sci-libs/fftw, so I followed the instructions from the wiki.
I edited /etc/portage/package.use and added the following:

Code: Select all
# 19. Sep. 2013: Add fftw with mpi support
sci-libs/fftw mpi

I then built fftw by running

Code: Select all
# emerge sci-libs/fftw

After that, I added the following lines to /etc/entropy/packages/package.mask:

Code: Select all
# 19. Sept. 2013: Add fftw with mpi support
sci-libs/fftw

Finally, I ran

Code: Select all
# equo rescue spmsync --ask

As you can see, this was some time ago. Last weekend, when I wanted to update my system, I got the following error:

Code: Select all
# sudo equo upgrade
╠  @@ Calculating System Updates:
╠  @@ Calculating dependencies...
☢  @@ Dependencies not found:
☛  !!! Every package matching >=sci-libs/fftw-3.3.3-r1[abi_x86_32] is masked.
☛     # Masking reason: user package.mask
☛      <> atom: sci-libs/fftw-3.3.3-r3 in sabayon-weekly
☛  !!! Every package matching >=sci-libs/fftw-3[abi_x86_32,abi_x86_64] is masked.
☛     # Masking reason: user package.mask
☛      <> atom: sci-libs/fftw-3.3.3-r3 in sabayon-weekly

I'm assuming this is because of the edit to package.mask, but wasn't equo rescue spmsync intended to prevent this kind of thing from happening? I'm not really an expert with equo/portage.

I thought that maybe I need to update fftw via portage before I can update the rest of my packages via equo, so I did

Code: Select all
# emerge --sync
# emerge sci-libs/fftw

This did update fftw, but the error when trying to update with equo is still there.

Do I need to do anything special to make equo realize that fftw is already installed and the dependency is satisfied?
toster
Baby Hen
 
Posts: 6
Joined: Tue May 21, 2013 10:18

Re: Dependency not found (because installed via portage)

Postby Stupot » Thu Jan 16, 2014 17:53

After you updated fftw did you do

Code: Select all
#equo rescue spmsync --ask


again?
Stupot
Sagely Hen
 
Posts: 1545
Joined: Wed Feb 14, 2007 3:44
Location: St. Louis, MO, USA

Re: Dependency not found (because installed via portage)

Postby sabayonino » Thu Jan 16, 2014 20:59

don't mask package

simply keep the portage version and run "equo rescue spmsync".

make sure to recompile the package if update is request by entropy

Code: Select all
# equo unmask sci-libs/fftw
User avatar
sabayonino
Sagely Hen
 
Posts: 2537
Joined: Sun Sep 21, 2008 1:12
Location: Italy

Re: Dependency not found (because installed via portage)

Postby Stupot » Thu Jan 16, 2014 21:12

I think it's ok to mask to the package from entropy. Just make sure to run 'equo rescue spmsync' each time you update the package via portage. It would certainly make it much easier to keep track of when you need to upgrade it if it's masked by entropy.
Stupot
Sagely Hen
 
Posts: 1545
Joined: Wed Feb 14, 2007 3:44
Location: St. Louis, MO, USA

Re: Dependency not found (because installed via portage)

Postby sabayonino » Thu Jan 16, 2014 22:26

you've compiled sci-libs/fftw-3.3.3-r1

entropy needs >=sci-libs/fftw-3.3.3-r3 and you had masked all the versions.

compile sci-libs/fftw-3.3.3-r3 (need sync)
Code: Select all
# emerge --sync   or eix-sync

Code: Select all
# emerge ">= sci-libs/fftw-3.3.3-r3"

Code: Select all
# equo rescue spmsync


don't need to mask any package after equo rescue spmsync basically if entropy package has the same version
User avatar
sabayonino
Sagely Hen
 
Posts: 2537
Joined: Sun Sep 21, 2008 1:12
Location: Italy

Re: Dependency not found (because installed via portage)

Postby Stupot » Thu Jan 16, 2014 22:36

sabayonino, I'm not the one with the issue, not sure why you're replying to me.

And he should still keep the package masked, or else the next time there's an upgrade, entropy will install over it. It's better, in my opinion, for entropy to tell you to upgrade the package via portage (by saying it can't because of the mask), then to overwrite it without asking.
Stupot
Sagely Hen
 
Posts: 1545
Joined: Wed Feb 14, 2007 3:44
Location: St. Louis, MO, USA

Re: Dependency not found (because installed via portage)

Postby toster » Fri Jan 17, 2014 9:22

Thanks for your suggestions, but unfortunately I had done them already and they didn't help. Just to be sure I did

Code: Select all
# emerge sci-libs/fftw

again, and it clearly showed that it was compiling sci-libs/fftw-3.3.3-r3

then I did

Code: Select all
# equo rescue spmsync
╠  @@ These packages were added:
╠     # sci-libs/fftw-3.3.3-r3
╠  +++  (1/1) sci-libs/fftw-3.3.3-r3
╠  @@ Update complete

# equo upgrade
╠  @@ Calculating System Updates:
╠  @@ Calculating dependencies...
☢  @@ Dependencies not found:
☛  !!! Every package matching >=sci-libs/fftw-3.3.3-r1[abi_x86_32] is masked.
☛     # Masking reason: user package.mask
☛      <> atom: sci-libs/fftw-3.3.3-r3 in sabayon-weekly
☛  !!! Every package matching >=sci-libs/fftw-3[abi_x86_32,abi_x86_64] is masked.
☛     # Masking reason: user package.mask
☛      <> atom: sci-libs/fftw-3.3.3-r3 in sabayon-weekly


And I still get the same error. If I interpret the error correctly it looks more like equo needs -r1 or greater, but -r3 is there and masked.
toster
Baby Hen
 
Posts: 6
Joined: Tue May 21, 2013 10:18

Re: Dependency not found (because installed via portage)

Postby Stupot » Fri Jan 17, 2014 17:01

Did you try as Sabayonino suggested and removed the mask from entropy?

That should get everything to install, but you might have to recompile fftw afterwards in case entropy replaces it.
Stupot
Sagely Hen
 
Posts: 1545
Joined: Wed Feb 14, 2007 3:44
Location: St. Louis, MO, USA

Re: Dependency not found (because installed via portage)

Postby batvink » Sat Jan 18, 2014 12:44

hm, somehow that Wiki-article is changed.
equo rescue spmsync is only useful if you change your client.conf.
It should be mentioned in the article, but got removed.
open "/etc/entropy/client.conf"
and change the line that says:
Code: Select all
# ignore-spm-downgrades =

into
Code: Select all
ignore-spm-downgrades = enable

Please remember that once you've manually changed client.conf
everytime you upgrade the system wants to revert it back, by asking you to "equo conf update"
And when invoking "equo rescue spmsync" , please use the --ask flag.
User avatar
batvink
Old Dear Hen
 
Posts: 495
Joined: Sun Oct 28, 2007 11:44
Location: the netherlands

Re: Dependency not found (because installed via portage)

Postby batvink » Sat Jan 18, 2014 13:20

Normally you don't need to mask the package in Entropy.
The above setting in client.conf together with "equo rescue spmsync" only prevents Entropy to not downgrade.
However, if Entropy has a new version, it WILL be overwritten, with default flags, predefined by Entropy,
and you will lose the flags you've defined.
It's nice to mix Entropy and Portage, and it can be done., but you must really know what you are doing.
A good knowledge of both package managers is advised.
As for both package managers, i also would advise you to always use --ask., and never blindly upgrade the system.
"emerge -a packagename" for Portage
and "equo i packagename --ask" for Entropy
User avatar
batvink
Old Dear Hen
 
Posts: 495
Joined: Sun Oct 28, 2007 11:44
Location: the netherlands

Next

Return to Entropy|Equo|Rigo Package Managers

Who is online

Users browsing this forum: No registered users and 2 guests

cron