[opensuse] Dependency Nightmare!
I recall mentioning not too long ago about the dependency errors which keep coming up in 13.1 - but I don't remember in which list I mentioned it nor do I remember what the answer (if any) was. I raise the issue again because I just cannot fathom what the heck I am supposed to do to resolve these dependency problems which YaST keeps spitting out at me. I am trying to get VLC to play not only Blu-ray files but now I found out that it won't even play files downloaded from YouTube. All files are playable in 12.3 but NOT in 13.1 - and I cannot figure out why. Below is a list of the repositories which I have in my 13.1 installation (on a Desktop): http://susepaste.org/78522541 and here is a list of the dependency errors which YaST so graciously shows me (but doesn't tell me which option to choose): http://susepaste.org/44273137 Can anyone, please, tell me which options I should choose to rid myself of these dependency hassles? (BTW, running zypper shows me that many files "will not be updated" which appear to be ones which are shown in the YaST list above.) BC -- Using openSUSE 13.1, KDE 4.12.0 & kernel 3.12.6-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 OC 2GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/30/2013 01:29 PM, Basil Chupin wrote:
I recall mentioning not too long ago about the dependency errors which keep coming up in 13.1 - but I don't remember in which list I mentioned it nor do I remember what the answer (if any) was.
I raise the issue again because I just cannot fathom what the heck I am supposed to do to resolve these dependency problems which YaST keeps spitting out at me. I am trying to get VLC to play not only Blu-ray files but now I found out that it won't even play files downloaded from YouTube. All files are playable in 12.3 but NOT in 13.1 - and I cannot figure out why.
I don't know for blu-ray and youtube, but this is what I did. I only added this VideoLan repo: http://download.videolan.org/pub/videolan/vlc/SuSE/13.1/ Please note that I had to completely uninstall all VLC packages before installing them from the VideoLan repo anew. Otherwise, yast would have run into similar dependency issues. Have a nice day, Berny -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Montag 30 Dezember 2013, 13:47:03 schrieb Bernhard Voelker:
On 12/30/2013 01:29 PM, Basil Chupin wrote:
I recall mentioning not too long ago about the dependency errors which keep coming up in 13.1 - but I don't remember in which list I mentioned it nor do I remember what the answer (if any) was.
I raise the issue again because I just cannot fathom what the heck I am supposed to do to resolve these dependency problems which YaST keeps spitting out at me. I am trying to get VLC to play not only Blu-ray files but now I found out that it won't even play files downloaded from YouTube. All files are playable in 12.3 but NOT in 13.1 - and I cannot figure out why.
I don't know for blu-ray and youtube, but this is what I did. I only added this VideoLan repo: http://download.videolan.org/pub/videolan/vlc/SuSE/13.1/
Please note that I had to completely uninstall all VLC packages before installing them from the VideoLan repo anew. Otherwise, yast would have run into similar dependency issues.
You can do this without prior uninstalling: zypper dup --from 'SuSE (13.1)' Here 'SuSE (13.1)' is the default name of the videolan repo. They should have taken something more specific name -- and use openSUSE instead of SuSE ;-) You have to use the name you have chosen when you have changed it. While using "zypper dup" in general is dangerous, it may be useful with the from option. So some days ago the libvpx1 has been added to packman and wasn't pulled in automatically by "zypper up" But beware: when using videolans repo you should not use packman, too. Mixing both is calling for trouble. If you do need other packages from packman, you better use vlc from there instead of videolans repo. Many problems with openSUSE come from improper mixing repositories or installing video drivers from NVIDIA or AMD without using provided rpms. Even when it seems to work for the first time, it can give trouble later. Good luck! Herbert -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 31/12/13 00:46, Herber Graeber wrote:
Am Montag 30 Dezember 2013, 13:47:03 schrieb Bernhard Voelker:
On 12/30/2013 01:29 PM, Basil Chupin wrote:
I recall mentioning not too long ago about the dependency errors which keep coming up in 13.1 - but I don't remember in which list I mentioned it nor do I remember what the answer (if any) was.
I raise the issue again because I just cannot fathom what the heck I am supposed to do to resolve these dependency problems which YaST keeps spitting out at me. I am trying to get VLC to play not only Blu-ray files but now I found out that it won't even play files downloaded from YouTube. All files are playable in 12.3 but NOT in 13.1 - and I cannot figure out why. I don't know for blu-ray and youtube, but this is what I did. I only added this VideoLan repo: http://download.videolan.org/pub/videolan/vlc/SuSE/13.1/
Please note that I had to completely uninstall all VLC packages before installing them from the VideoLan repo anew. Otherwise, yast would have run into similar dependency issues. You can do this without prior uninstalling:
zypper dup --from 'SuSE (13.1)'
Here 'SuSE (13.1)' is the default name of the videolan repo. They should have taken something more specific name -- and use openSUSE instead of SuSE ;-) You have to use the name you have chosen when you have changed it. While using "zypper dup" in general is dangerous, it may be useful with the from option. So some days ago the libvpx1 has been added to packman and wasn't pulled in automatically by "zypper up"
Sheesh! No wonder 13.1 has problems! How is ANYONE to know what you just stated?! Thank you for what your wrote. I installed 'libvpx1' to my existing installation of vlc and I can now at least view the downloaded YouTube videos which I couldn't view before. I have yet to try out viewing a Bd movie - will report the result. Sorry to say that a whole application collapses and becomes useless simply because of *one* tiny (1.7MB) file?!
But beware: when using videolans repo you should not use packman, too. Mixing both is calling for trouble. If you do need other packages from packman, you better use vlc from there instead of videolans repo.
Many problems with openSUSE come from improper mixing repositories or installing video drivers from NVIDIA or AMD without using provided rpms. Even when it seems to work for the first time, it can give trouble later.
Good luck! Herbert
Thanks for the advice. I shall configure that I only use one of these repos and no other. BC -- Using openSUSE 13.1, KDE 4.12.0 & kernel 3.12.6-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 OC 2GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/31/2013 01:23 AM, Basil Chupin wrote:
I installed 'libvpx1' to my existing installation of vlc and I can now at least view the downloaded YouTube videos which I couldn't view before. I have yet to try out viewing a Bd movie - will report the result.
Sorry to say that a whole application collapses and becomes useless simply because of *one* tiny (1.7MB) file?!
Basil, To get around this problem I used to set the priority of the videolan repository and the kde3 repo slightly lower than default (99). Like this: # zypper mr -p 90 videolan I was able to avoid packman/videolan conflicts. Apparently the zypper magic gives priority to repos with lower priority numbers. So if you have packman at 99 and vidolan at 90, then zypper logic should use the videolan packages -- as long as they have the same name as the packman packages (rpm logic should handle any conflict if the spec files were correctly written) I cannot recall if setting 'solver.allowVendorChange = true' is required in /etc/zypp/zypp.conf to have priority function correctly, but it is something that I have always done. Others will have to chime in on this issue. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 31/12/13 18:45, David C. Rankin wrote:
On 12/31/2013 01:23 AM, Basil Chupin wrote:
I installed 'libvpx1' to my existing installation of vlc and I can now at least view the downloaded YouTube videos which I couldn't view before. I have yet to try out viewing a Bd movie - will report the result.
Sorry to say that a whole application collapses and becomes useless simply because of *one* tiny (1.7MB) file?!
Basil,
To get around this problem I used to set the priority of the videolan repository and the kde3 repo slightly lower than default (99). Like this:
# zypper mr -p 90 videolan
I was able to avoid packman/videolan conflicts. Apparently the zypper magic gives priority to repos with lower priority numbers. So if you have packman at 99 and vidolan at 90, then zypper logic should use the videolan packages -- as long as they have the same name as the packman packages (rpm logic should handle any conflict if the spec files were correctly written)
I cannot recall if setting 'solver.allowVendorChange = true' is required in /etc/zypp/zypp.conf to have priority function correctly, but it is something that I have always done. Others will have to chime in on this issue.
Thank you David. I usually have these priorities set in the manner you suggest (but not this time - with the exception of the kernel repo - as the list of my repos shows). What is really the bottom line in regards to this is that- (1) a new user of openSUSE and YaST and zypper wouldn't have a damn clue about this priority-thingie and not to mention the inane fact that the LOWER the number the HIGHER the priority!; (2) it has already been mentioned here, or in another oS list, that one of the problems is that some files may have the same "build" number but be different in their contents; and (3) for some mysterious reason when I did my usual morning routine of 'zypper refresh>zypper patch>zypper up' and one (I think) patch was downloaded and installed, things dramatically changed: a short time later I had to go into YaST to check on a file and decided to do the "Upgrade Packages if new ones available" and guess what? -- NO dependency problems, not a single one, clean as a whistle...... and there were 3 files which needed updating, and they were without a hitch. Go figure! The only thing I can think of re (3) is that one does not install a version of openSUSE if it is released at the end of the year when the festive season is fast approaching........ (Which raises the question of what were earlier versions of oS which were realeased in November and December? (See list here: https://en.wikipedia.org/wiki/Opensuse ) BC -- Using openSUSE 13.1, KDE 4.12.0 & kernel 3.12.6-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 OC 2GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Dienstag, 31. Dezember 2013, 18:23:26 schrieb Basil Chupin:
On 31/12/13 00:46, Herber Graeber wrote: [...]
So some days ago the libvpx1 has been added to packman and wasn't pulled in automatically by "zypper up"
Sheesh! No wonder 13.1 has problems!
How is ANYONE to know what you just stated?!
Hubert Mantel mailed on the packman mailing list, that the mythtv packages don't pull in the right libvpx1. That was because of the vendor change from openSUSE to packman. I changed the mythtv packages to use an explicit "Requires: libvpx1 >= 1.3.0" to fix that issue.
Thank you for what your wrote.
I installed 'libvpx1' to my existing installation of vlc and I can now at least view the downloaded YouTube videos which I couldn't view before. I have yet to try out viewing a Bd movie - will report the result.
Nice to hear that my statement helped. Writing these I originally feared I could be overly verbose. I was not...
Sorry to say that a whole application collapses and becomes useless simply because of *one* tiny (1.7MB) file?!
It looks like some other packages on packman need the above mentioned explicit requirement, too. The problem for those building packages on packman is, that the libvpx1-1.3.0 suddenly appeared on packman and the packagers depending of libvpx1-1.2.0 don't notice that they have to prepare to force an explicit vendor change. Automatic generation of dependencys by rbmbuild is not enough here. The rule for users of those packages is: If you use some application from packman, take all libraries this application depends on from packman, too. And be prepared, that the set of libraries may change later. Sure, it would be better this would be forced by the packages itself, but unfortunately that's not always to case.
[...]
Herbert -- If privacy is outlawed, only outlaws will have privacy. Phil Zimmermann -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 31/12/2013 13:04, Herbert Graeber a écrit :
Sure, it would be better this would be forced by the packages itself, but unfortunately that's not always to case.
thanks both to the one that reported and to you who fixed the problem. it's like this that things advances jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-12-31 13:04, Herbert Graeber wrote:
The rule for users of those packages is: If you use some application from packman, take all libraries this application depends on from packman, too. And be prepared, that the set of libraries may change later.
Ah, but that's not practical. All libraries? Surely glibc not. At some point you have to decide to take libraries from openSUSE instead. It is difficult for us users to know which libraries should come from the distribution and which should come from packman instead.
Sure, it would be better this would be forced by the packages itself, but unfortunately that's not always to case.
Right... -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" (Elessar)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/01/14 02:21, Carlos E. R. wrote:
On 2013-12-31 13:04, Herbert Graeber wrote:
The rule for users of those packages is: If you use some application from packman, take all libraries this application depends on from packman, too. And be prepared, that the set of libraries may change later.
Ah, but that's not practical. All libraries? Surely glibc not. At some point you have to decide to take libraries from openSUSE instead. It is difficult for us users to know which libraries should come from the distribution and which should come from packman instead.
+1
Sure, it would be better this would be forced by the packages itself, but
unfortunately that's not always to case.
Right...
BC -- Using openSUSE 13.1, KDE 4.12.0 & kernel 3.12.6-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 OC 2GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 31/12/13 23:04, Herbert Graeber wrote:
Am Dienstag, 31. Dezember 2013, 18:23:26 schrieb Basil Chupin:
On 31/12/13 00:46, Herber Graeber wrote: [...]
So some days ago the libvpx1 has been added to packman and wasn't pulled in automatically by "zypper up" Sheesh! No wonder 13.1 has problems!
How is ANYONE to know what you just stated?! Hubert Mantel mailed on the packman mailing list, that the mythtv packages don't pull in the right libvpx1. That was because of the vendor change from openSUSE to packman.
Sheesh! How could I have missed that! :-D Everybody reads what Hubert writes on the packman mailing list, right? Silly me..... :-) .
I changed the mythtv packages to use an explicit "Requires: libvpx1 >= 1.3.0" to fix that issue.
Thank goodness that at least you read that mailing list. Most grateful to you.
Thank you for what your wrote.
I installed 'libvpx1' to my existing installation of vlc and I can now at least view the downloaded YouTube videos which I couldn't view before. I have yet to try out viewing a Bd movie - will report the result. Nice to hear that my statement helped. Writing these I originally feared I could be overly verbose. I was not...
Sorry to say that a whole application collapses and becomes useless simply because of *one* tiny (1.7MB) file?! It looks like some other packages on packman need the above mentioned explicit requirement, too.
The problem for those building packages on packman is, that the libvpx1-1.3.0 suddenly appeared on packman and the packagers depending of libvpx1-1.2.0 don't notice that they have to prepare to force an explicit vendor change. Automatic generation of dependencys by rbmbuild is not enough here.
The rule for users of those packages is: If you use some application from packman, take all libraries this application depends on from packman, too. And be prepared, that the set of libraries may change later.
Sure, it would be better this would be forced by the packages itself, but unfortunately that's not always to case.
I used to use the package manager called 'smart' and with which Pascal Blesser had a role to play. Smart is a very intelligent package manager and I wonder if it is still active and available for use with openSUSE? BC -- Using openSUSE 13.1, KDE 4.12.0 & kernel 3.12.6-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 OC 2GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
[01.01.2014 07:28] [Basil Chupin]:
Smart is a very intelligent package manager and I wonder if it is still active and available for use with openSUSE?
According to the very low traffic on its mailing list it is. I used smart myself, but since about oS 11.3, I converted to zypper - it works better. Smart is absolutely awesome if the only other means of package management is apt(itude), but I do not see advantages over zypper. Werner -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 31/12/13 18:23, Basil Chupin wrote:
On 31/12/13 00:46, Herber Graeber wrote:
Am Montag 30 Dezember 2013, 13:47:03 schrieb Bernhard Voelker:
On 12/30/2013 01:29 PM, Basil Chupin wrote:
I recall mentioning not too long ago about the dependency errors which keep coming up in 13.1 - but I don't remember in which list I mentioned it nor do I remember what the answer (if any) was.
I raise the issue again because I just cannot fathom what the heck I am supposed to do to resolve these dependency problems which YaST keeps spitting out at me. I am trying to get VLC to play not only Blu-ray files but now I found out that it won't even play files downloaded from YouTube. All files are playable in 12.3 but NOT in 13.1 - and I cannot figure out why. I don't know for blu-ray and youtube, but this is what I did. I only added this VideoLan repo: http://download.videolan.org/pub/videolan/vlc/SuSE/13.1/
Please note that I had to completely uninstall all VLC packages before installing them from the VideoLan repo anew. Otherwise, yast would have run into similar dependency issues. You can do this without prior uninstalling:
zypper dup --from 'SuSE (13.1)'
Here 'SuSE (13.1)' is the default name of the videolan repo. They should have taken something more specific name -- and use openSUSE instead of SuSE ;-) You have to use the name you have chosen when you have changed it. While using "zypper dup" in general is dangerous, it may be useful with the from option. So some days ago the libvpx1 has been added to packman and wasn't pulled in automatically by "zypper up"
Sheesh! No wonder 13.1 has problems!
How is ANYONE to know what you just stated?!
Thank you for what your wrote.
I installed 'libvpx1' to my existing installation of vlc and I can now at least view the downloaded YouTube videos which I couldn't view before. I have yet to try out viewing a Bd movie - will report the result.
OK, as promised I have now tried several Bd discs having added/installed libvpx1 to my existing installation of vlc (from packman). Oh, there was at least one update performed either late last night or this morning, but whatever here is the result: (1) Bd discs are now (sorta) playable: but they STUTTER - 5 seconds 'on' 1 second 'pause' ad finitum...... Sounds very much like something we had years ago when the UDMA was not being recognised and therefore not set correctly and one had to fiddle with a control file to get the kernel to set the correct UDMA; must look up my notes to see what was done at that time; and (2) When vlc is started and the option to play a Bd disc is selected (Media>Open Disc>Blu-ray), vlc decides that it wants to open (the default) /dev/dvd1 where it thinks that the Bd is supposed to be - and then it comes back with an error message that the path to the Bd disc is wrong. Manually changing '/dev'dvd1' to 'dev/sr0' will begin the playing of the Bd disc. Annoying but not fatal. Is there a way to make vlc recognise the correct device name (sr0) instead of 'dvd1'? BTW, re (1): this also occurs when one only plays the movie m2ts file using either VLC or Dolphin - ie, the file 'stutters'; this does not happen in openSUSE 12.3
Sorry to say that a whole application collapses and becomes useless simply because of *one* tiny (1.7MB) file?!
But beware: when using videolans repo you should not use packman, too. Mixing both is calling for trouble. If you do need other packages from packman, you better use vlc from there instead of videolans repo.
Many problems with openSUSE come from improper mixing repositories or installing video drivers from NVIDIA or AMD without using provided rpms. Even when it seems to work for the first time, it can give trouble later.
Good luck! Herbert
Thanks for the advice. I shall configure that I only use one of these repos and no other.
BC
BC -- Using openSUSE 13.1, KDE 4.12.0 & kernel 3.12.6-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 OC 2GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 30/12/13 23:47, Bernhard Voelker wrote:
On 12/30/2013 01:29 PM, Basil Chupin wrote:
I recall mentioning not too long ago about the dependency errors which keep coming up in 13.1 - but I don't remember in which list I mentioned it nor do I remember what the answer (if any) was.
I raise the issue again because I just cannot fathom what the heck I am supposed to do to resolve these dependency problems which YaST keeps spitting out at me. I am trying to get VLC to play not only Blu-ray files but now I found out that it won't even play files downloaded from YouTube. All files are playable in 12.3 but NOT in 13.1 - and I cannot figure out why. I don't know for blu-ray and youtube, but this is what I did. I only added this VideoLan repo: http://download.videolan.org/pub/videolan/vlc/SuSE/13.1/
Please note that I had to completely uninstall all VLC packages before installing them from the VideoLan repo anew. Otherwise, yast would have run into similar dependency issues.
Have a nice day, Berny
Thanks Berny. As you would have seen I do have the videolan repo enabled - but I had the wrong name for it according to your msg. Now this is "funny" because until today YaST or zypper did not have any problems in updating the info for this repo (the name of which I had is shown in the URL I provided in my OP). But never mind.....strange things are happening in this installation of 13.1..... (I installed 13.1 on my ThinkPad without a problem and then I added my wife as a User on the system. Both my wife and I use the same apps [like Firefox, Thunderbird,...] and play the same games. However, 2 of the games we play come up with an error message that "suitable font was not found" in her home directory while the exact same games are work perfectly OK for me. Eh, openSUSE is becoming more and more like...... I won't mention the name......) BC -- Using openSUSE 13.1, KDE 4.12.0 & kernel 3.12.6-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 OC 2GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-12-31 08:11, Basil Chupin wrote:
(I installed 13.1 on my ThinkPad without a problem and then I added my wife as a User on the system. Both my wife and I use the same apps [like Firefox, Thunderbird,...] and play the same games. However, 2 of the games we play come up with an error message that "suitable font was not found" in her home directory while the exact same games are work perfectly OK for me. Eh, openSUSE is becoming more and more like...... I won't mention the name......)
font directory on home? -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" (Elessar)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 31/12/13 22:02, Carlos E. R. wrote:
On 2013-12-31 08:11, Basil Chupin wrote:
(I installed 13.1 on my ThinkPad without a problem and then I added my wife as a User on the system. Both my wife and I use the same apps [like Firefox, Thunderbird,...] and play the same games. However, 2 of the games we play come up with an error message that "suitable font was not found" in her home directory while the exact same games are work perfectly OK for me. Eh, openSUSE is becoming more and more like...... I won't mention the name......)
font directory on home?
<FX: Puzzled look on face> A clean install of 13.1, correct process of adding the second user, same fonts in /usr/share/fonts/... and in /etc/X11/...., same games........ so why shouldn't the fonts in the home directory be the same? Tell all :-) . BC -- Using openSUSE 13.1, KDE 4.12.0 & kernel 3.12.6-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 OC 2GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-01-01 07:35, Basil Chupin wrote:
On 31/12/13 22:02, Carlos E. R. wrote:
On 2013-12-31 08:11, Basil Chupin wrote:
(I installed 13.1 on my ThinkPad without a problem and then I added my wife as a User on the system. Both my wife and I use the same apps [like Firefox, Thunderbird,...] and play the same games. However, 2 of the games we play come up with an error message that "suitable font was not found" in her home directory while the exact same games are work perfectly OK for me. Eh, openSUSE is becoming more and more like...... I won't mention the name......)
font directory on home?
<FX: Puzzled look on face>
A clean install of 13.1, correct process of adding the second user, same fonts in /usr/share/fonts/... and in /etc/X11/...., same games........ so why shouldn't the fonts in the home directory be the same? Tell all :-) .
Nope. I simply wonder, I ask, whether you have fonts also on your home path. Some people do. That would explain why on the same computer one user sees different than another user. That's one possible explanation. Another is that they belong to different groups. -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" (Elessar)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-12-30 13:29, Basil Chupin wrote:
(BTW, running zypper shows me that many files "will not be updated" which appear to be ones which are shown in the YaST list above.)
If you concoct a command that lists the packages installed from packman, I'll give you my list. :-) -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" (Elessar)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-12-30 14:03, Carlos E. R. wrote:
On 2013-12-30 13:29, Basil Chupin wrote:
(BTW, running zypper shows me that many files "will not be updated" which appear to be ones which are shown in the YaST list above.)
If you concoct a command that lists the packages installed from packman, I'll give you my list. :-)
I used this: rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \ %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \ | sort | cut --fields="2-" | grep -i packman | tee rpmlist | less -S which produced (edited): gpg-pubkey 1abd1afb-4c97c60c (none)(none)PackMan Project (signing key) libopencore-amrnb0 0.1.3-4.2 x86_64 http://packman.links2linux.de libopencore-amrwb0 0.1.3-4.2 x86_64 http://packman.links2linux.de libx264-135 0.135svn20130723-2.2 x86_64 http://packman.links2linux.de libavutil50 0.7.16-2.4 x86_64 http://packman.links2linux.de libmp3lame0 3.99.5-1013.2 x86_64 http://packman.links2linux.de librtmp1 2.4.git20131007-2.2 x86_64 http://packman.links2linux.de libxvidcore4 1.3.2-2.2 x86_64 http://packman.links2linux.de libpostproc50 0.7.16-2.4 x86_64 http://packman.links2linux.de libswscale0 0.7.16-2.4 x86_64 http://packman.links2linux.de libavcodec52 0.7.16-2.4 x86_64 http://packman.links2linux.de gstreamer-0_10-plugins-ffmpeg 0.10.13-2000.1 x86_64 http://packman.links2linux.de libavfilter1 0.7.16-2.4 x86_64 http://packman.links2linux.de libavformat52 0.7.16-2.4 x86_64 http://packman.links2linux.de pulseaudio-equalizer 2.7rev4-1.1 noarch http://packman.links2linux.de libfaad2 2.7-13.2 x86_64 http://packman.links2linux.de libtwolame0 0.3.13-2.2 x86_64 http://packman.links2linux.de libvlccore7 2.1.2-186.10 x86_64 http://packman.links2linux.de liba52-0 0.7.5svn-8.2 x86_64 http://packman.links2linux.de libdca0 0.0.5-3.4 x86_64 http://packman.links2linux.de libavutil52 2.1.1-3.1 x86_64 http://packman.links2linux.de libvpx1 1.3.0-7.1 x86_64 http://packman.links2linux.de libvlc5 2.1.2-186.10 x86_64 http://packman.links2linux.de libmad0 0.15.1b-1.2 x86_64 http://packman.links2linux.de libmpeg2-0 0.5.1-2.2 x86_64 http://packman.links2linux.de libvo-aacenc0 0.1.2-3.2 x86_64 http://packman.links2linux.de libpostproc52 2.1.1-3.1 x86_64 http://packman.links2linux.de npapi-vlc 2.0.2_git201206081001-1.3 x86_64 http://packman.links2linux.de libxine2 1.2.3-89.2 x86_64 http://packman.links2linux.de libxine2-directfb 1.2.3-89.2 x86_64 http://packman.links2linux.de libxine2-pulse 1.2.3-89.2 x86_64 http://packman.links2linux.de libxine2-sdl 1.2.3-89.2 x86_64 http://packman.links2linux.de libavcodec55 2.1.1-3.1 x86_64 http://packman.links2linux.de libavformat55 2.1.1-3.1 x86_64 http://packman.links2linux.de vlc-noX 2.1.2-186.10 x86_64 http://packman.links2linux.de xine-skins 1.0.3-2.2 noarch Packman libxine2-codecs 1.2.3-89.2 x86_64 http://packman.links2linux.de vlc 2.1.2-186.10 x86_64 http://packman.links2linux.de vlc-codecs 2.1.2-186.10 x86_64 http://packman.links2linux.de vlc-qt 2.1.2-186.10 x86_64 http://packman.links2linux.de vlc-noX-lang 2.1.2-186.10 noarch http://packman.links2linux.de libtsmux0 0.3.0-2.1 i586 http://packman.links2linux.de libfaac0 1.28-9.2 x86_64 http://packman.links2linux.de libvo-amrwbenc0 0.1.2-3.1 x86_64 http://packman.links2linux.de libmjpegutils-2_0-0 2.0.0-57.2 x86_64 http://packman.links2linux.de libavresample1 2.1.1-3.1 x86_64 http://packman.links2linux.de libswscale2 2.1.1-3.1 x86_64 http://packman.links2linux.de gstreamer-0_10 0.10.36-14.16 x86_64 http://packman.links2linux.de lame 3.99.5-1013.2 x86_64 http://packman.links2linux.de libgmyth0 0.7.1-11.3 x86_64 http://packman.links2linux.de libslv2-9 0.6.6-3.10 x86_64 http://packman.links2linux.de libaudio2 1.9.4-1.1 x86_64 http://packman.links2linux.de libswresample0 2.1.1-3.1 x86_64 http://packman.links2linux.de lame-doc 3.99.5-1013.2 x86_64 http://packman.links2linux.de libbml0 0.6.1-2.2 x86_64 http://packman.links2linux.de libgstreamer-1_0-0 1.2.1-3.5 x86_64 http://packman.links2linux.de libgstreamer-0_10-0-32bit 0.10.36-14.16 x86_64 http://packman.links2linux.de libffmpegthumbnailer4 2.0.8-3.2 x86_64 http://packman.links2linux.de libavfilter3 2.1.1-3.1 x86_64 http://packman.links2linux.de gstreamer 1.2.1-3.5 x86_64 http://packman.links2linux.de libgstreamer-0_10-0 0.10.36-14.16 x86_64 http://packman.links2linux.de libgstapp-0_10-0-32bit 0.10.36-12.28 x86_64 http://packman.links2linux.de libgstinterfaces-0_10-0-32bit 0.10.36-12.28 x86_64 http://packman.links2linux.de gstreamer-0_10-plugins-fluendo_mpegmux 0.10.4-46.1 i586 http://packman.links2linux.de gstreamer-0_10-doc 0.10.36-18.16 x86_64 http://packman.links2linux.de gstreamer-0_10-utils 0.10.36-14.16 x86_64 http://packman.links2linux.de libgstbuzztard0 0.6.0-9.24 x86_64 http://packman.links2linux.de ffmpegthumbnailer 2.0.8-3.2 x86_64 http://packman.links2linux.de ffmpeg-tools 2.1.1-3.1 x86_64 http://packman.links2linux.de libavdevice55 2.1.1-3.1 x86_64 http://packman.links2linux.de libgstsignalprocessor-0_10-23 0.10.23-24.14 x86_64 http://packman.links2linux.de gstreamer-lang 1.2.1-3.5 noarch http://packman.links2linux.de gstreamer-0_10-plugins-base 0.10.36-12.28 x86_64 http://packman.links2linux.de libgstcodecparsers-0_10-23 0.10.23-24.14 x86_64 http://packman.links2linux.de libgstegl-1_0-0 1.2.1-5.22 x86_64 http://packman.links2linux.de libgstphotography-0_10-23 0.10.23-24.14 x86_64 http://packman.links2linux.de libgstphotography-1_0-0 1.2.1-5.22 x86_64 http://packman.links2linux.de gstreamer-doc 1.2.1-2.6 x86_64 http://packman.links2linux.de gstreamer-utils 1.2.1-3.5 x86_64 http://packman.links2linux.de libgstvideo-1_0-0 1.2.1-2.9 x86_64 http://packman.links2linux.de libgstcodecparsers-1_0-0 1.2.1-5.22 x86_64 http://packman.links2linux.de libgstmpegts-1_0-0 1.2.1-5.22 x86_64 http://packman.links2linux.de libgsttag-1_0-0 1.2.1-2.9 x86_64 http://packman.links2linux.de libgstapp-0_10-0 0.10.36-12.28 x86_64 http://packman.links2linux.de libgstinterfaces-0_10-0 0.10.36-12.28 x86_64 http://packman.links2linux.de ffmpeg2theora 0.29-2.6 x86_64 http://packman.links2linux.de ffmpeg 2.1.1-3.1 x86_64 http://packman.links2linux.de gstreamer-plugins-base 1.2.1-2.9 x86_64 http://packman.links2linux.de gstreamer-0_10-plugin-gnomevfs 0.10.36-12.28 x86_64 http://packman.links2linux.de gstreamer-0_10-plugins-base-doc 0.10.36-12.28 x86_64 http://packman.links2linux.de gstreamer-0_10-plugins-base-lang 0.10.36-12.28 noarch http://packman.links2linux.de libgstbasevideo-0_10-23 0.10.23-24.14 x86_64 http://packman.links2linux.de libgstvdp-0_10-23 0.10.23-24.14 x86_64 http://packman.links2linux.de gstreamer-0_10-plugins-good-lang 0.10.31-16.4 noarch http://packman.links2linux.de libgstaudio-1_0-0 1.2.1-2.9 x86_64 http://packman.links2linux.de libgstpbutils-1_0-0 1.2.1-2.9 x86_64 http://packman.links2linux.de gstreamer-0_10-plugin-esd 0.10.31-16.4 x86_64 http://packman.links2linux.de gstreamer-0_10-plugins-good 0.10.31-16.4 x86_64 http://packman.links2linux.de gstreamer-0_10-plugins-good-doc 0.10.31-16.4 x86_64 http://packman.links2linux.de libgstbasecamerabinsrc-0_10-23 0.10.23-24.14 x86_64 http://packman.links2linux.de gstreamer-plugins-base-lang 1.2.1-2.9 noarch http://packman.links2linux.de libgstapp-1_0-0 1.2.1-2.9 x86_64 http://packman.links2linux.de libgstriff-1_0-0 1.2.1-2.9 x86_64 http://packman.links2linux.de libgstsdp-1_0-0 1.2.1-2.9 x86_64 http://packman.links2linux.de libgstbasecamerabinsrc-1_0-0 1.2.1-5.22 x86_64 http://packman.links2linux.de gst123 0.3.3-1.5 x86_64 http://packman.links2linux.de gstreamer-plugins-base-doc 1.2.1-2.9 x86_64 http://packman.links2linux.de libgstallocators-1_0-0 1.2.1-2.9 x86_64 http://packman.links2linux.de libgstfft-1_0-0 1.2.1-2.9 x86_64 http://packman.links2linux.de libgstrtp-1_0-0 1.2.1-2.9 x86_64 http://packman.links2linux.de libgstrtsp-1_0-0 1.2.1-2.9 x86_64 http://packman.links2linux.de typelib-1_0-GstTag-1_0 1.2.1-2.9 x86_64 http://packman.links2linux.de typelib-1_0-GstVideo-1_0 1.2.1-2.9 x86_64 http://packman.links2linux.de gstreamer-plugins-libav 1.2.1-2.2 x86_64 http://packman.links2linux.de gstreamer-plugins-good 1.2.1-2.3 x86_64 http://packman.links2linux.de typelib-1_0-GstAudio-1_0 1.2.1-2.9 x86_64 http://packman.links2linux.de typelib-1_0-GstPbutils-1_0 1.2.1-2.9 x86_64 http://packman.links2linux.de gstreamer-plugins-good-doc 1.2.1-2.3 x86_64 http://packman.links2linux.de gstreamer-plugins-good-lang 1.2.1-2.3 noarch http://packman.links2linux.de gstreamer-0_10-plugins-fluendo_mpegdemux 0.10.71-2.2 i586 http://packman.links2linux.de gstreamer-0_10-plugins-good-extra 0.10.31-16.4 x86_64 http://packman.links2linux.de gstreamer-plugins-bad 1.2.1-5.22 x86_64 http://packman.links2linux.de gstreamer-plugins-good-extra 1.2.1-2.3 x86_64 http://packman.links2linux.de gstreamer-0_10-plugins-buzztard 0.6.0-9.24 x86_64 http://packman.links2linux.de gstreamer-0_10-plugins-ugly 0.10.19-12.2 x86_64 http://packman.links2linux.de gstreamer-plugins-ugly 1.2.1-2.2 x86_64 http://packman.links2linux.de gstreamer-0_10-plugins-bad 0.10.23-24.14 x86_64 http://packman.links2linux.de gstreamer-plugins-bad-doc 1.2.1-5.22 x86_64 http://packman.links2linux.de gstreamer-plugins-bad-lang 1.2.1-5.22 noarch http://packman.links2linux.de gstreamer-0_10-plugins-ugly-lang 0.10.19-12.2 noarch http://packman.links2linux.de gstreamer-plugins-ugly-lang 1.2.1-2.2 noarch http://packman.links2linux.de gstreamer-plugins-ugly-doc 1.2.1-2.2 x86_64 http://packman.links2linux.de gstreamer-plugins-ugly-orig-addon 1.2.1-2.2 x86_64 http://packman.links2linux.de gstreamer-plugins-bad-orig-addon 1.2.1-5.22 x86_64 http://packman.links2linux.de gstreamer-0_10-plugins-ugly-doc 0.10.19-12.2 x86_64 http://packman.links2linux.de gstreamer-0_10-plugins-ugly-orig-addon 0.10.19-12.2 x86_64 http://packman.links2linux.de gstreamer-0_10-plugins-bad-lang 0.10.23-24.14 noarch http://packman.links2linux.de gstreamer-0_10-plugins-bad-orig-addon 0.10.23-24.14 x86_64 http://packman.links2linux.de gstreamer-0_10-plugins-bad-doc 0.10.23-24.14 x86_64 http://packman.links2linux.de xfwpcnm 1-2.3 x86_64 http://packman.links2linux.de Doing this allowed me to find 3 errors in my configs, packages of the 32 bit version instead of the 64: gstreamer-0_10-plugins-fluendo_mpegdemux - Fluendo GStreamer plug-in for MPEG demuxing gstreamer-0_10-plugins-fluendo_mpegmux - Fluendo GStreamer plug-in for MPEG Transport Stream muxing libtsmux0 - Library for muxing of MPEG Transport Streams This other query finds them: Elessar:~ # rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \ %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \ | sort | cut --fields="2-" | grep i586 | tee rpmlist | less -S Elessar:~ # which produces: master-boot-code 1.22-14.1.2 i586 skype 4.2.0.11-suse121 i586 gstreamer-0_10-plugins-gl 0.10.3-7.1.3 i586 of which only gstreamer needs replacing. These are the last corrections:
Mon Dec 30 2013 Sun Oct 13 2013 libtsmux0 0.3.0-2.1 x86_64 http://packman.links2linux.de packman@links2linux.de == Essentials / openSUSE_13.1 (none) Mon Dec 30 2013 Mon Dec 16 2013 gstreamer-0_10-plugins-fluendo_mpegdemux 0.10.71-2.2 x86_64 http://packman.links2linux.de packman@links2linux.de == Essentials / openSUSE_13.1 (none) Mon Dec 30 2013 Sat Sep 28 2013 liboil 0.3.17-18.1.3 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 13.1 (none) Mon Dec 30 2013 Sun Oct 13 2013 gstreamer-0_10-plugins-fluendo_mpegmux 0.10.4-46.1 x86_64 http://packman.links2linux.de packman@links2linux.de == Essentials / openSUSE_13.1 (none) Mon Dec 30 2013 Sat Sep 28 2013 gstreamer-0_10-plugins-gl 0.10.3-7.1.3 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 13.1 (none) Mon Dec 30 2013 Sat Sep 28 2013 libgstgl-0_10-1 0.10.3-7.1.3 x86_64 openSUSE http://bugs.opensuse.org == openSUSE 13.1 (none)
But in any case, I had multimedia working. The other thing to take into account, is that packman had recently build problems, not every package was available or build correctly - most of my files were installed earlier than those problem and I hesitate to update them yet. -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" (Elessar)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/30/2013 08:03 AM, Carlos E. R. pecked at the keyboard and wrote:
On 2013-12-30 13:29, Basil Chupin wrote:
(BTW, running zypper shows me that many files "will not be updated" which appear to be ones which are shown in the YaST list above.)
If you concoct a command that lists the packages installed from packman, I'll give you my list. :-)
zypper se -is -r <name or # of repo> -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-12-30 15:29, Ken Schneider - openSUSE wrote:
On 12/30/2013 08:03 AM, Carlos E. R. pecked at the keyboard and wrote:
If you concoct a command that lists the packages installed from packman, I'll give you my list. :-)
zypper se -is -r <name or # of repo>
Elessar:~ # zypper lr | grep -i packman 1 | EXT_Packman | Packman Repository | Yes | Yes Elessar:~ # zypper se -is -r EXT_Packman Loading repository data... Reading installed packages...
S | Name | Type | Version | Arch | Repository --+------------------------------------------+---------+---------------------------+--------+------------------- i | ffmpeg2theora | package | 0.29-2.6 | x86_64 | Packman Repository i | gstreamer-0_10-plugins-fluendo_mpegdemux | package | 0.10.71-2.2 | x86_64 | Packman Repository i | gstreamer-0_10-plugins-fluendo_mpegmux | package | 0.10.4-46.1 | x86_64 | Packman Repository i | gstreamer-0_10-plugins-ugly | package | 0.10.19-12.2 | x86_64 | Packman Repository i | gstreamer-0_10-plugins-ugly-doc | package | 0.10.19-12.2 | x86_64 | Packman Repository i | gstreamer-0_10-plugins-ugly-lang | package | 0.10.19-12.2 | noarch | Packman Repository i | gstreamer-0_10-plugins-ugly-orig-addon | package | 0.10.19-12.2 | x86_64 | Packman Repository i | gstreamer-plugins-libav | package | 1.2.1-2.2 | x86_64 | Packman Repository i | gstreamer-plugins-ugly | package | 1.2.1-2.2 | x86_64 | Packman Repository i | gstreamer-plugins-ugly-doc | package | 1.2.1-2.2 | x86_64 | Packman Repository i | gstreamer-plugins-ugly-lang | package | 1.2.1-2.2 | noarch | Packman Repository i | gstreamer-plugins-ugly-orig-addon | package | 1.2.1-2.2 | x86_64 | Packman Repository i | libbml0 | package | 0.6.1-2.2 | x86_64 | Packman Repository i | libfaac0 | package | 1.28-9.2 | x86_64 | Packman Repository i | libfaad2 | package | 2.7-13.2 | x86_64 | Packman Repository i | libgmyth0 | package | 0.7.1-11.3 | x86_64 | Packman Repository i | libmad0 | package | 0.15.1b-1.2 | x86_64 | Packman Repository i | librtmp1 | package | 2.4.git20131007-2.2 | x86_64 | Packman Repository i | libtsmux0 | package | 0.3.0-2.1 | x86_64 | Packman Repository i | libxvidcore4 | package | 1.3.2-2.2 | x86_64 | Packman Repository i | npapi-vlc | package | 2.0.2_git201206081001-1.3 | x86_64 | Packman Repository i | pulseaudio-equalizer | package | 2.7rev4-1.1 | noarch | Packman Repository i | xfwpcnm | package | 1-2.3 | x86_64 | Packman Repository Elessar:~ #
The list seems incomplete, compared with my other list. -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" (Elessar)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 30/12/2013 15:48, Carlos E. R. a écrit :
The list seems incomplete, compared with my other list.
zypper se -i -r "Packman Repository" gives 100 line for me jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Пн, 30/12/2013 в 15:48 +0100, Carlos E. R. пишет:
The list seems incomplete, compared with my other list.
Which simply means that some packages are no more contained in packman repository (too old, too new, obsolete, whatever). I.e. they are orphaned ... bor@opensuse:/tmp/binaries> LC_ALL=C zypper se -is -r home:duwe:crosstools Warning: Specified repository 'home:duwe:crosstools' is disabled. Loading repository data... Reading installed packages... No packages found. bor@opensuse:/tmp/binaries> LC_ALL=C zypper pa -io Loading repository data... Reading installed packages... S | Repository | Name | Version | Arch --+------------+----------------------------------+-------------+------- i | @System | cross-arm-linux-gnueabi-binutils | 2.21.1-11.1 | x86_64 i | @System | cross-arm-linux-gnueabi-gcc | 4.5.3-21.1 | x86_64 i | @System | cross-arm-linux-gnueabi-glibc | 2.13-24.1 | noarch bor@opensuse:/tmp/binaries> rpm -qi cross-arm-linux-gnueabi-binutils | grep Distribution Distribution: home:duwe:crosstools / openSUSE_12.3 bor@opensuse:/tmp/binaries> -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-12-30 16:26, Andrey Borzenkov wrote:
В Пн, 30/12/2013 в 15:48 +0100, Carlos E. R. пишет:
The list seems incomplete, compared with my other list.
Which simply means that some packages are no more contained in packman repository (too old, too new, obsolete, whatever). I.e. they are orphaned ...
No, no, impossible. This partition is a freshly installed one, all packman packages were installed this month. For example, these two, according to an rpm query:
Sat Dec 21 2013 Mon Dec 16 2013 libopencore-amrnb0 0.1.3-4.2 x86_64 http://packman.links2linux.de packman@links2linux.de == Essentials / openSUSE_13.1 (none) Sat Dec 21 2013 Mon Dec 16 2013 libopencore-amrwb0 0.1.3-4.2 x86_64 http://packman.links2linux.de packman@links2linux.de == Essentials / openSUSE_13.1 (none)
are not installed according the "zypper se ..." query. But they are, they came from packman, and were installed 9 days ago. Of course, packman has rebuilt those packages and now they are other version... -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" (Elessar)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 31/12/13 00:03, Carlos E. R. wrote:
On 2013-12-30 13:29, Basil Chupin wrote:
(BTW, running zypper shows me that many files "will not be updated" which appear to be ones which are shown in the YaST list above.)
If you concoct a command that lists the packages installed from packman, I'll give you my list. :-)
Nah......you show me yours first and then I will show you mine....... :-) BC -- Using openSUSE 13.1, KDE 4.12.0 & kernel 3.12.6-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 OC 2GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-12-31 07:07, Basil Chupin wrote:
On 31/12/13 00:03, Carlos E. R. wrote:
On 2013-12-30 13:29, Basil Chupin wrote:
(BTW, running zypper shows me that many files "will not be updated" which appear to be ones which are shown in the YaST list above.)
If you concoct a command that lists the packages installed from packman, I'll give you my list. :-)
Nah......you show me yours first and then I will show you mine.......
:-)
I did already :-) -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" (Elessar)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 31/12/13 22:06, Carlos E. R. wrote:
On 2013-12-31 07:07, Basil Chupin wrote:
On 31/12/13 00:03, Carlos E. R. wrote:
On 2013-12-30 13:29, Basil Chupin wrote:
(BTW, running zypper shows me that many files "will not be updated" which appear to be ones which are shown in the YaST list above.)
If you concoct a command that lists the packages installed from packman, I'll give you my list. :-)
Nah......you show me yours first and then I will show you mine.......
:-)
I did already :-)
But I blinked........ :-) . BC -- Using openSUSE 13.1, KDE 4.12.0 & kernel 3.12.6-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 OC 2GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 30/12/2013 13:29, Basil Chupin a écrit :
I recall mentioning not too long ago about the dependency errors which keep coming up in 13.1 - but I don't remember in which list I mentioned it nor do I remember what the answer (if any) was.
I think you have too many repos. I had similar problem recebntly and asked for help, and receive it. result: http://dodin.info/wiki/index.php?n=Doc.QuelPaquetDansQuelD%e9pot this allows to know what repo do what my zypper lr (below). debug can be ommitted and tumbleweed do nothing (only git and gvim). I was often said to don't use own vlc repo, mine is from packman jdd 1 | Tumbleweed | Tumbleweed | Oui | Oui 2 | ftp.gwdg.de-suse | Packman Repository | Oui | Oui 3 | isv:ownCloud:community | isv:ownCloud:community | Oui | Oui 4 | isv:ownCloud:desktop | isv:ownCloud:desktop | Oui | Oui 5 | multimedia:apps | multimedia:apps | Oui | Oui 6 | multimedia:libs | multimedia:libs | Oui | Oui 7 | openSUSE-13.1-1.10 | openSUSE-13.1-1.10 | Non | Non 8 | opensuse-guide.org-repo | libdvdcss repository | Oui | Oui 9 | repo-debug | openSUSE-13.1-Debug | Non | Oui 10 | repo-debug-update | openSUSE-13.1-Update-Debug | Non | Oui 11 | repo-debug-update-non-oss | openSUSE-13.1-Update-Debug-Non-Oss | Non | Oui 12 | repo-non-oss | openSUSE-13.1-Non-Oss | Oui | Oui 13 | repo-oss | openSUSE-13.1-Oss | Oui | Oui 14 | repo-source | openSUSE-13.1-Source | Non | Oui 15 | repo-update | openSUSE-13.1-Update | Oui | Oui 16 | repo-update-non-oss | openSUSE-13.1-Update-Non-Oss | Oui | Oui -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-12-30 14:13, jdd wrote:
I was often said to don't use own vlc repo, mine is from packman
No, VLC is fine, I believe, just don't use VLC and Packman at the same time. -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" (Elessar)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 30/12/2013 14:44, Carlos E. R. a écrit :
On 2013-12-30 14:13, jdd wrote:
I was often said to don't use own vlc repo, mine is from packman
No, VLC is fine, I believe, just don't use VLC and Packman at the same time.
do you have vlc in the community list? I don't anymore jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-12-30 15:25, jdd wrote:
Le 30/12/2013 14:44, Carlos E. R. a écrit :
On 2013-12-30 14:13, jdd wrote:
I was often said to don't use own vlc repo, mine is from packman
No, VLC is fine, I believe, just don't use VLC and Packman at the same time.
do you have vlc in the community list? I don't anymore
Dunno. [...] No, it is not listed. -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" (Elessar)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Montag, 30. Dezember 2013, 23:29:23 schrieb Basil Chupin:
Can anyone, please, tell me which options I should choose to rid myself of these dependency hassles?
bluedevil: Either you can have bluedevil ( including bluedevil-lang) installed. This is nonfunctional because 13.1 uses bluez5 bluetooth stack. Or install the still experimental bluedevil-bluez5 package ( without extra lang package) Kdelibs/kdm: The kdelibs/kdm-branding-openSUSE-13.1 packages seem to have a dependency on kde-4.11. But you have the kde-4.12 repo configured. Don't install these packages,if you want to run kde-4.12. vlc: you have to decide, where you get vlc from : Either packman (version 2.1.2-186.14) or vlc repo. Choose one repo, disable the other and in yast switch system packages to that repo. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
[30.12.2013 14:15] [Markus Koßmann]:
vlc: you have to decide, where you get vlc from : Either packman (version 2.1.2-186.14) or vlc repo. Choose one repo, disable the other and in yast switch system packages to that repo.
I do not completely agree with the second paragraph :-) I installed the VLC software from the VLC repo, and PackMan is still enabled. YaST or zypper do not mix up the packages, because I never ever use "zypper dup" unless I really want to upgrade to another version of openSUSE. In my /etc/zypp/zypp.conf, the variable solver.allowVendorChange is commented out, which means it has its default value, false. So no "zypper up" will pull vlc from Packman repo after I installed the packages from the VLC repo. After adding the VLC repo, I chose (in YaST) Software Management -> View -> Repositories, chose the VLC repo and clicked upon the "Switch system packages" link, hardly visible in the black bar above the package list. This caused some downgrading of some packages, but now I am sure that VLC and all software it depends on are installed from the same source. And it works up to now *knockonwood* :-) Just my experience (built up in the last years, not just now) Werner -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 30/12/2013 20:35, Werner Flamme a écrit :
-> Repositories, chose the VLC repo and clicked upon the "Switch system packages" link, hardly visible in the black bar above the package list.
oh, yes, didn't know this option. I beg "system" is for "installed system", not "core system"? I don't exactly understand neither what is the repo priority doing respective to changing repos: if I set vlc repo with a lower nice will it be pulled by zypper up? thanks jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* jdd <jdd@dodin.org> [12-30-13 14:44]:
Le 30/12/2013 20:35, Werner Flamme a écrit :
-> Repositories, chose the VLC repo and clicked upon the "Switch system packages" link, hardly visible in the black bar above the package list.
oh, yes, didn't know this option.
I beg "system" is for "installed system", not "core system"?
I don't exactly understand neither what is the repo priority doing respective to changing repos: if I set vlc repo with a lower nice will it be pulled by zypper up?
only for packages installed from "vlc repo". priorities only make sense when more than one source exists and "zypper up" will not cross sources, ie: you do not need to use priorities in this particular case. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 31/12/13 07:12, Patrick Shanahan wrote:
* jdd <jdd@dodin.org> [12-30-13 14:44]:
Le 30/12/2013 20:35, Werner Flamme a �crit :
-> Repositories, chose the VLC repo and clicked upon the "Switch system packages" link, hardly visible in the black bar above the package list. oh, yes, didn't know this option.
I beg "system" is for "installed system", not "core system"?
I don't exactly understand neither what is the repo priority doing respective to changing repos: if I set vlc repo with a lower nice will it be pulled by zypper up? only for packages installed from "vlc repo".
priorities only make sense when more than one source exists and "zypper up" will not cross sources, ie: you do not need to use priorities in this particular case.
....and in any other cases where the name of the day of the week ends with the letter "y" and the moon is on the wane while being in the ascendency in the constellation Orion and just before low tide on the east coast of Iceland at the very exact time of the Summer Solstice. Or whichever comes first..... Put simply: the whole damn thing is CONFUSING! BC -- Using openSUSE 13.1, KDE 4.12.0 & kernel 3.12.6-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 OC 2GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
[31.12.2013 07:29] [Basil Chupin]:
On 31/12/13 07:12, Patrick Shanahan wrote:
* jdd <jdd@dodin.org> [12-30-13 14:44]:
Le 30/12/2013 20:35, Werner Flamme a �crit :
-> Repositories, chose the VLC repo and clicked upon the "Switch system packages" link, hardly visible in the black bar above the package list. oh, yes, didn't know this option.
I beg "system" is for "installed system", not "core system"?
I don't exactly understand neither what is the repo priority doing respective to changing repos: if I set vlc repo with a lower nice will it be pulled by zypper up? only for packages installed from "vlc repo".
priorities only make sense when more than one source exists and "zypper up" will not cross sources, ie: you do not need to use priorities in this particular case.
....and in any other cases where the name of the day of the week ends with the letter "y" and the moon is on the wane while being in the ascendency in the constellation Orion and just before low tide on the east coast of Iceland at the very exact time of the Summer Solstice. Or whichever comes first.....
Put simply: the whole damn thing is CONFUSING!
Aye. That's why I do not care about repo priorities :-). For me, it's enough to know that in my setup zypper does not pull across repos as long as solver.allowVendorChange = false. So, when a package moves e.g. from KDE:Release to KDE:Extras, it will still be updated, since in both cases the "Vendor" is KDE. But if a newer version of a KDE package is available on PackMan, this newer version will not be applied automatically, since PackMan != KDE. Werner -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 31/12/2013 08:07, Werner Flamme a écrit :
So, when a package moves e.g. from KDE:Release to KDE:Extras, it will still be updated, since in both cases the "Vendor" is KDE.
thanks, you just learned me something. Nevr know what the ":" was for :-) jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 31/12/2013 07:29, Basil Chupin a écrit :
Put simply: the whole damn thing is CONFUSING!
yes. We are too rich :-) and have to sort things thanks jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-12-30 20:35, Werner Flamme wrote:
[30.12.2013 14:15] [Markus Koßmann]:
vlc: you have to decide, where you get vlc from : Either packman (version 2.1.2-186.14) or vlc repo. Choose one repo, disable the other and in yast switch system packages to that repo.
I do not completely agree with the second paragraph :-)
I installed the VLC software from the VLC repo, and PackMan is still enabled. YaST or zypper do not mix up the packages, because I never ever use "zypper dup" unless I really want to upgrade to another version of openSUSE.
Yes, that's correct. If you install VLC and all its dependencies from the videolan repo, and different things from packman, it works. The problem is when the toolchain is mixed. -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" (Elessar)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Montag, 30. Dezember 2013, 22:54:41 schrieb Carlos E. R.:
On 2013-12-30 20:35, Werner Flamme wrote:
[30.12.2013 14:15] [Markus Koßmann]:
vlc: you have to decide, where you get vlc from : Either packman (version 2.1.2-186.14) or vlc repo. Choose one repo, disable the other and in yast switch system packages to
that repo.
I do not completely agree with the second paragraph :-)
I installed the VLC software from the VLC repo, and PackMan is still enabled. YaST or zypper do not mix up the packages, because I never ever use "zypper dup" unless I really want to upgrade to another version of openSUSE.
Yes, that's correct. If you install VLC and all its dependencies from the videolan repo, and different things from packman, it works. The problem is when the toolchain is mixed.
But then the question is, if everything installed from packman will work... Herbert -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 31/12/13 09:40, Herbert Graeber wrote:
Am Montag, 30. Dezember 2013, 22:54:41 schrieb Carlos E. R.:
On 2013-12-30 20:35, Werner Flamme wrote:
[30.12.2013 14:15] [Markus Ko�mann]:
vlc: you have to decide, where you get vlc from : Either packman (version 2.1.2-186.14) or vlc repo. Choose one repo, disable the other and in yast switch system packages to
that repo. I do not completely agree with the second paragraph :-)
I installed the VLC software from the VLC repo, and PackMan is still enabled. YaST or zypper do not mix up the packages, because I never ever use "zypper dup" unless I really want to upgrade to another version of openSUSE. Yes, that's correct. If you install VLC and all its dependencies from the videolan repo, and different things from packman, it works. The problem is when the toolchain is mixed. But then the question is, if everything installed from packman will work...
Herbert
A good question. I have everything from packman installed and vlc doesn't work :-( . My personal take on this is that once Pascal Bleser left a great void was created - and there is too much reliance on 'community support' which in reality consists of only one "supporter" and if s/he gets run over by a bus then the whole 'operation' relating to that one vital cog in the wheel collapses. I put the Tumbleweed project in this category. If Larry falls under a bus then Tumbleweed is no more as far as I am able to determine. I am not hexing Larry in any way- Heaven forbid! - but is there anyone to take his place - Patrick perhaps? Ignoring the above scenarios, what happens if some malcontent who has a grudge against openSUSE or Linux in general starts contributing as a member of "the community"? OK, the kernel is pretty safe but what about other apps used in openSUSE? Yep, I am being paranoid - but I am expressing a genuine concern in light of my hassles with vlc in openSUSE 13.1 and what has been stated so far re the dependency errors between enabled repos from packman, openSUSE, videolan. BC -- Using openSUSE 13.1, KDE 4.12.0 & kernel 3.12.6-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 OC 2GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
[31.12.2013 07:57] [Basil Chupin]:
On 31/12/13 09:40, Herbert Graeber wrote:
Am Montag, 30. Dezember 2013, 22:54:41 schrieb Carlos E. R.:
On 2013-12-30 20:35, Werner Flamme wrote:
[30.12.2013 14:15] [Markus Ko�mann]:
vlc: you have to decide, where you get vlc from : Either packman (version 2.1.2-186.14) or vlc repo. Choose one repo, disable the other and in yast switch system packages to
that repo. I do not completely agree with the second paragraph :-)
I installed the VLC software from the VLC repo, and PackMan is still enabled. YaST or zypper do not mix up the packages, because I never ever use "zypper dup" unless I really want to upgrade to another version of openSUSE. Yes, that's correct. If you install VLC and all its dependencies from the videolan repo, and different things from packman, it works. The problem is when the toolchain is mixed. But then the question is, if everything installed from packman will work...
Herbert
A good question.
I have everything from packman installed and vlc doesn't work :-( .
That is what happened to me years ago (VLC 0.9.something). PackMan provides bleeding edge (at least in this case), while videolan.org themselves will rather provide running versions :-)
Ignoring the above scenarios, what happens if some malcontent who has a grudge against openSUSE or Linux in general starts contributing as a member of "the community"?
OK, the kernel is pretty safe but what about other apps used in openSUSE?
Do you really think the NSA is not involved yet? :-)
Yep, I am being paranoid - but I am expressing a genuine concern in light of my hassles with vlc in openSUSE 13.1 and what has been stated so far re the dependency errors between enabled repos from packman, openSUSE, videolan.
Those dependencies can be cleaned up, even if it's a hairy mess. One possibility is to use VLC from videolan.org only, everything else regarding multimedia from PackMan instead of openSUSE (because of the fewer codecs in openSUSE due to legal issues), and the rest from openSUSE. Btw, I currently have 62 repos available, 6 of them are disabled, and no dependency hell :-) Werner -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 31/12/2013 07:57, Basil Chupin a écrit :
I have everything from packman installed and vlc doesn't work :-( .
*this* is odd, because I have the same and use it all the day...
Yep, I am being paranoid - but I am expressing a genuine concern in light of my hassles with vlc in openSUSE 13.1 and what has been stated so far re the dependency errors between enabled repos from packman, openSUSE, videolan.
we all depends on some people doing the job. it's life. but right now most things works so we should go back to understand why your VLC do not works... jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (12)
-
Andrey Borzenkov -
Basil Chupin -
Bernhard Voelker -
Carlos E. R. -
David C. Rankin -
Herber Graeber -
Herbert Graeber
-
jdd -
Ken Schneider - openSUSE -
Markus Koßmann -
Patrick Shanahan -
Werner Flamme