Install abcde (a better cd encoder)

Hello,

i would love to install abcde for ripping my records and noticed is in omv repos, but i am unable to install it due to many dependencies missing

was anybody able to install it?

Logs… logs… :wink:

eccoci

Problema: conflicting requests
  - package abcde-2.9.3-2.x86_64 from cooker-x86_64-extra requires perl(WebService::MusicBrainz), but none of the providers can be installed
  - package abcde-2.9.3-2.x86_64 from release-x86_64-extra requires perl(WebService::MusicBrainz), but none of the providers can be installed
  - package perl-WebService-MusicBrainz-1.0.6-1.noarch from cooker-x86_64-extra requires perl(Mojo::Base), but none of the providers can be installed
  - package perl-WebService-MusicBrainz-1.0.6-1.noarch from cooker-x86_64-extra requires perl(Mojo::URL), but none of the providers can be installed
  - package perl-WebService-MusicBrainz-1.0.6-1.noarch from cooker-x86_64-extra requires perl(Mojo::UserAgent), but none of the providers can be installed
  - package perl-WebService-MusicBrainz-1.0.6-1.noarch from cooker-x86_64-extra requires perl(Mojo::Util), but none of the providers can be installed
  - package perl-WebService-MusicBrainz-1.0.6-1.noarch from release-x86_64-extra requires perl(Mojo::Base), but none of the providers can be installed
  - package perl-WebService-MusicBrainz-1.0.6-1.noarch from release-x86_64-extra requires perl(Mojo::URL), but none of the providers can be installed
  - package perl-WebService-MusicBrainz-1.0.6-1.noarch from release-x86_64-extra requires perl(Mojo::UserAgent), but none of the providers can be installed
  - package perl-WebService-MusicBrainz-1.0.6-1.noarch from release-x86_64-extra requires perl(Mojo::Util), but none of the providers can be installed
  - package perl-Mojolicious-9.38-1.noarch from cooker-x86_64-extra requires perl(EV) >= v4.320.0, but none of the providers can be installed
  - package perl-Mojolicious-9.38-1.noarch from release-x86_64-extra requires perl(EV) >= v4.320.0, but none of the providers can be installed
  - package perl-Mojolicious-8.180.0-1.noarch from rock-x86_64 requires perl(EV) >= 4.0.0, but none of the providers can be installed
  - nothing provides libperl.so.5.32()(64bit) needed by perl-EV-4.270.0-1.x86_64 from cooker-x86_64-extra
  - nothing provides libperl.so.5.38()(64bit) needed by perl-EV-4.34-1.x86_64 from cooker-x86_64-extra
  - nothing provides libperl.so.5.32()(64bit) needed by perl-EV-4.270.0-1.x86_64 from release-x86_64-extra
  - nothing provides libperl.so.5.38()(64bit) needed by perl-EV-4.34-1.x86_64 from release-x86_64-extra
1 Like

uh, maybe i have to disable some repo?are packaging conflicting here?is not really clear…

Why repo cooker?
What iso is it?

What a mess…
Do
sudo dnf clean all;dnf clean all;dnf repolist
post console output

Don’t use Discover to manage your repos. Support for upgrading with it is also experimental. I would suggest using Software Repository Selector for your repos and Software Update for your updates. For everything else, use

sudo dnf in <package_name>

where <package_name> is the package you want to install. You can see if the package is in our repos using

dnf search <package_name>

Based on licensing, some may be in the extra or non-free repos and may not show up in a search until you enable those repos.

6.0 stable, gnome spin, i think i enabled two more repos in tears of mandriva, but now that i think of i should probably disable cooker, cooker is the rolling right?

I’m on the gnome spin, and i’m using yum extender, since also packagekit is broken, and yum extender is just a gui for what you said :slight_smile:

anyway, i don’t know why three repos, i didn’t mess up with any configuration

will have a look

No.
Useful reading:
Repository Policies

Also:
How to get better results when posting about problems

Please fill in the requirements in all your support requests, they are there for a reason :wink:

supportrequir

The most important info are OM version and Desktop. The more you provide, the less boring repetitive questions we’ll ask you (because yes, be sure that good willing people trying to help will ask you them)

Now, if you wish we to guide you on repair the repository mess please post the console output.
If instead you prefer to try by your own (for your fun and/or satisfaction) then do, and tell us what you did step by step.

i was just going to check on tears of mandriva, i checked and there you can enable free, restricted and nonfree repositories, i don’t think these have something to do with cooker, unless clicking the “enable all repos” button enable every repos from mandriva, in which case is a bit misleading as one might think it just enables all listed repos in one click (free, non free, restricted)
and as i said, i did not mess up with the system at all, apart from removing some app after installation, that’s what i found in the basic gnome installation :slight_smile:

anyway

sudo dnf clean all

21 files removed

dnf clean all

21 files removed

(again?weird)

dnf repolist

cooker-x86_64-extra          OpenMandriva Cooker - Extra - x86_64
cooker-x86_64-non-free       OpenMandriva Cooker - Non-free - x86_64
cooker-x86_64-restricted     OpenMandriva Cooker - Restricted - x86_64
release-updates-x86_64-extra OpenMandriva 6.0 - Extra - x86_64 - Updates
release-x86_64-extra         OpenMandriva 6.0 - Extra - x86_64
rock-updates-x86_64          OpenMandriva Rock - x86_64 - Updates
rock-x86_64                  OpenMandriva Rock - x86_64

No, expected.

^^ These are the only ones by default in a fresh install rock/6.0 system.
We’ll see about the others later.

Go to /etc/yum.repos.d/

edit the files:
openmandriva-cooker-x86_64.repo
openmandriva-release-x86_64.repo

Replace all the instances enabled=1 to enabled=0
Save, close.

Do
sudo dnf clean all;dnf clean all;dnf repolist
post console output

here it is, i suppose we did it

rock-updates-x86_64        OpenMandriva Rock - x86_64 - Updates
rock-x86_64                OpenMandriva Rock - x86_64

by the way, did disabling repos with gnome software would have been the same?

ok so, here it is

after having only the rock repositories left, i tried installing abcde again and to my surprise it was not found at all

so i tried enabling that “extra” repository again and it was there, i was able to install it

did a repolist after that, and noticed i had release repository enabled, so tried also enabling restricted and non free, and i had both cooker repos, so now we know where all my repos came from

i reverted anything to rock repositories only after having installed abcde but i find it weird that such an old application is not available in base repository…

Perfect.

I don’t know, and would not care tbh.

So, next time you need to enable/disable repository you want to use Software Repository Selector (om-repo-picker). That’s the only safe tool to manage repository in OM.

A short note about /testing repo:
the packages built for rolling and rock won’t go straight to the usual repository, our policy is that they are published to the relevant /testing repo first.
The testers can then (guess what? :stuck_out_tongue: ) test the packages and provide feedbacks.
Common user should not have it enabled by default.

Sometimes we suggest to install from /testing stuff that have been required, or so.
In this case either you temporarily enable it (om-repo-picker) or you use the command we’ll give you.

i enabled those repository via this page in tears of mandriva, which was already provided and i suppose it’s a mandriva official application

i don’t have any repo picker in gnome but since this section of the app has the same things you mentioned in repo picker i assume it’s the same but for gtk

anyway, i have no problem at all having cooker repositories enabled as soon as they are safe to use (as in not conflicting with base repositories too much)

1 Like

If you are on Rock, all your repos MUST be Rock. You can’t just mix and match repos. It will break your system. Right now, it wasn’t a big deal as we had just released Rock 6.0 and it was in cooker until just before the release. The more time goes on, the more different they will be and the more dangerous that would become.

are you saying that if i want to avoid conflicts i should disable extra, restricted and non-free (which seems to be all cooker)?

and yes i am in rock now

Just to make sure, please post the output.

sudo dnf clean all;dnf clean all;dnf repolist

All the repos should have Rock in the name. Every one of them.

ok, so i suppose that if i want to install an app which is in cooker and not in rock i need to wait until is in it, right?

No. Picture Rock as a huge rock, the size of your car. It doesn’t move. That is why we call it “stable” and it won’t change until the next release in a year or so.