When i attempt to install software [viz: Chromium, Skype … etc] that require files from Index of /suse/12.3/ i get the following messages:
Using CL:
[packman-x86_64|http://packman.inode.at/suse/12.3/] Can’t provide file ‘./Essentials/x86_64/libgstapp-0_10-0-32bit-0.10.36-9.36.x86_64.rpm’ from repository ‘packman-x86_64’
History:
Can’t provide ./Essentials/x86_64/libgstapp-0_10-0-32bit-0.10.36-9.36.x86_64.rpm
or using YaST:
[packman-x86_64|http://packman.inode.at/suse/12.3/] Can’t provide file ‘./Essentials/x86_64/libgstapp-0_10-0-32bit-0.10.36-9.36.x86_64.rpm’ from repository ‘packman-x86_64’
and yet as can be seen from screenshot below, i have the ‘packman’ repository registered:
I am sure I have used this repository previously … What might i be doing wrong???
Thanks,
OpenSUSE 12.3-64 / Gnome Version 3.6.2
PS: the above outputs were from attempting to install Skype by following Skype - openSUSE Wiki … but similar feedback was forthcoming when trying to install Chromium
then you will notice that packman and oss are in a bit of a “war” with some packages
one day packman has newer versions
a day or two later oss has the same packages but with a bit higher minor version numbers
if you do not lock down the rpms from packman and turn off " vender change "
the two will be in a " tug of war "
also ** turn off the install dvd !!! **
and SET the priority !!!
99 is the default
if you are using packman set it to 90
and the google-chrome repo to 80
Well … could not answer “Why not?” … i think that repo was put there when i had a go at replacing google-chrome with chromium … but can’t be abs sure. At any rate i did not manually add it.
Nevertheless … i made it ‘auto refresh’ and can now install both Chromium [from Repos] and Skype via these instructions. However i could not get Skype to make a successful test call … thought it might have something to do with the Multi Media files i have installed … so started afresh and used your Multimedia Guide caf, to see if it might solve the prob … but not … will attend to that later.
Right now i would like to sort out my list of Repositories …
because after following instructions in the MM Guide, i had expected mine might look something like this???
Clearly i am over my depth here … but if my Repository setup is acceptable then i will ‘lock-it-in’ … if not would much appreciate some advice of where to go from here.
> robin_listas;2573820 Wrote:
>> I’m surprised packman works at all these days
>>
> Well, the Packman Build Service was down (it’s working again since last week).
> But the repo was there and working all the time.
AFAIK, they are trying to build everything, and having problems. Not
everything has built and published yet.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))
Of course during the Build Service downtime, packages could not be updated/fixed or rebuilt.
But the repo was fine.
The only problems right now that I am aware of are caused by the update of ffmpeg to 2.0, which causes other packages’ build to fail (k3b-codecs, vlc-codecs and mediastreamer2 at least). So those still require the older ffmpeg libraries (1.0.6) which are not in the repo anymore.
But you can just keep the older ffmpeg packages installed as well for now if you already have them installed. (and this isn’t the first time something like this happened; ffmpeg keeps changing its interface all the time, rather drastic sometimes)
Okay … thnx for that! Removed “packman-x86_64” as suggested but then found i had to ‘switch’ again to “packman” … and on doing so had a whole heap of updates … as in:-
… as an ‘aside’ … started to work on my Skype no audio issue … and out of curiosity looked it up in Software Manager only to find that its version was also highlighted in red??
Has this got anything to do with my ‘no audio’ issue … do you think? … or is the ‘red’ highlight highlighting some other issue … like that i installed it outside of repos perhaps???
Has this got anything to do with my ‘no audio’ issue … do you think? … or is the ‘red’ highlight highlighting some other issue … like that i installed it outside of repos perhaps???
If you installed a .rpm that you downloaded manually, then that is why it is red.
@wolfi323
Just wondering why they pushed ffmpeg in there until the issues were sorted. It just causes a catastrophic mess of dependencies that will only serve to confuse people.
caf4926 wrote:
>
> Just wondering why they pushed ffmpeg in there until the issues were
> sorted. It just causes a catastrophic mess of dependencies that will
> only serve to confuse people.
>
>
They do it all the time and I just wait for a few days till the
dependency issues go away. Their approach is probably to break it and
then fix it.
caf4926 wrote:
> Wouldn’t that be better done on a local level?
depends on whether their OBS implementation will complain about
dependencies when building packages. It is also possible that they
don’t have separate test and live environments.