[opensuse] How to Remove Packman
I received a security update for Lame, but it wouldn't install due to vendor change. I decided to remove Packman as I only use it for playing MP3 and it doesn't seem to be necessary for that anymore. So I went into yast2 sw_single and selected the repository view, and selected Packman and then selected Delete all packages in this list. I had to resolve dependencies which I did by selecting downgrade or de-installation in every case. One of the things it removed was Chromium. I then disabled Packman, and re-installed Chromium. But this seemed to re-install libmp3lame from Packman even though it was disabled. So I removed it again and then removed Packman, then re-installed Chromium. This time it installed libmp3lame0 from openSUSE-Leap-42.3-Update. So what is the correct procedure for doing this, and why does yast2 install software from disabled repositories? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2018-02-26 a las 09:50 -0000, Richmond escribió:
I received a security update for Lame, but it wouldn't install due to vendor change. I decided to remove Packman as I only use it for playing MP3 and it doesn't seem to be necessary for that anymore.
So I went into yast2 sw_single and selected the repository view, and selected Packman and then selected Delete all packages in this list. I had to resolve dependencies which I did by selecting downgrade or de-installation in every case. One of the things it removed was Chromium.
I then disabled Packman, and re-installed Chromium. But this seemed to re-install libmp3lame from Packman even though it was disabled. So I removed it again and then removed Packman, then re-installed Chromium. This time it installed libmp3lame0 from openSUSE-Leap-42.3-Update. So what is the correct procedure for doing this, and why does yast2 install software from disabled repositories?
Huh. The first move is to, on the packman repo view, "disable switch to this repo" if it appears. Next is disable the packman repo. (If something was reinstalled from packman, it means you did not disable it, or that you have it twice. YaST can not enable itself a repo) So the after pacman is disabled, go to the oss repo and click "switch system packages to this repo". Then go to to the @system repo, select the unmaintained packages view, then force all of those to update even if it means repository change. Find any package that came from packman and upgrade or delete it, solving any dep in the road. - -- Cheers Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlqUE+EACgkQja8UbcUWM1ytQAEAhLiQ4ebhw+BnzZkMf23Qsozr Zlgqeil4V76GKBHGVs8A/iPqqD5MGdyxEcTzecLTbwbwgC2ArFJszfRay5KuZ5xA =6dlU -----END PGP SIGNATURE-----
Carlos E. R. wrote:
The first move is to, on the packman repo view, "disable switch to this repo" if it appears.
I am not sure where that is, but I didn't see it.
Next is disable the packman repo.
(If something was reinstalled from packman, it means you did not disable it, or that you have it twice. YaST can not enable itself a repo)
I did disable the packman repo, and it was not there twice. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Richmond
Carlos E. R. wrote:
The first move is to, on the packman repo view, "disable switch to this repo" if it appears.
I am not sure where that is, but I didn't see it.
Next is disable the packman repo.
(If something was reinstalled from packman, it means you did not disable it, or that you have it twice. YaST can not enable itself a repo)
I did disable the packman repo, and it was not there twice.
do: ls -la /etc/zypp/repos.d/ and see if there is a file with packman or Packman in the name. if so, do: sudo mv /etc/zypp/repos.d/<file-name> /etc/zypp/repos.d/save.<file-name> substitute the name of the file you found in the first step in <file-name> then yast will no longer find the packman repo. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/26/2018 01:10 PM, Richmond wrote:
Carlos E. R. wrote:
The first move is to, on the packman repo view, "disable switch to this repo" if it appears.
I am not sure where that is, but I didn't see it.
Next is disable the packman repo.
(If something was reinstalled from packman, it means you did not disable it, or that you have it twice. YaST can not enable itself a repo)
I did disable the packman repo, and it was not there twice.
The other question is WHY does Opensuse still have crippled mp3 packages when all mp3 patents have expired and every other distro includes them out of the box? -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/27/2018 02:24 AM, John Andersen wrote:
On 02/26/2018 01:10 PM, Richmond wrote:
Carlos E. R. wrote:
The first move is to, on the packman repo view, "disable switch to this repo" if it appears.
I am not sure where that is, but I didn't see it.
Next is disable the packman repo.
(If something was reinstalled from packman, it means you did not disable it, or that you have it twice. YaST can not enable itself a repo)
I did disable the packman repo, and it was not there twice.
The other question is WHY does Opensuse still have crippled mp3 packages when all mp3 patents have expired and every other distro includes them out of the box?
Which packages are still crippled? Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/01/2018 05:48 AM, Dave Plater wrote:
On 02/27/2018 02:24 AM, John Andersen wrote:
On 02/26/2018 01:10 PM, Richmond wrote:
Carlos E. R. wrote:
The first move is to, on the packman repo view, "disable switch to this repo" if it appears.
I am not sure where that is, but I didn't see it.
Next is disable the packman repo.
(If something was reinstalled from packman, it means you did not disable it, or that you have it twice. YaST can not enable itself a repo)
I did disable the packman repo, and it was not there twice.
The other question is WHY does Opensuse still have crippled mp3 packages when all mp3 patents have expired and every other distro includes them out of the box?
Which packages are still crippled?
Dave P
Ask the thread starter. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op donderdag 1 maart 2018 18:19:51 CET schreef John Andersen:
On 03/01/2018 05:48 AM, Dave Plater wrote:
On 02/27/2018 02:24 AM, John Andersen wrote:
On 02/26/2018 01:10 PM, Richmond wrote:
Carlos E. R. wrote:
The first move is to, on the packman repo view, "disable switch to this repo" if it appears.
I am not sure where that is, but I didn't see it.
Next is disable the packman repo.
(If something was reinstalled from packman, it means you did not disable it, or that you have it twice. YaST can not enable itself a repo)
I did disable the packman repo, and it was not there twice.
The other question is WHY does Opensuse still have crippled mp3 packages when all mp3 patents have expired and every other distro includes them out of the box?
Which packages are still crippled?
Dave P
Ask the thread starter. Why? No mention of crippled packages in his post. You're the one popping the question.
-- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team Linux user #548252 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2018-03-01 at 09:19 -0800, John Andersen wrote:
On 03/01/2018 05:48 AM, Dave Plater wrote:
On 02/27/2018 02:24 AM, John Andersen wrote:
On 02/26/2018 01:10 PM, Richmond wrote:
Carlos E. R. wrote:
The first move is to, on the packman repo view, "disable switch to this repo" if it appears.
I am not sure where that is, but I didn't see it.
Next is disable the packman repo.
(If something was reinstalled from packman, it means you did not disable it, or that you have it twice. YaST can not enable itself a repo)
I did disable the packman repo, and it was not there twice.
The other question is WHY does Opensuse still have crippled mp3 packages when all mp3 patents have expired and every other distro includes them out of the box?
Which packages are still crippled?
Ask the thread starter.
No, the thread starter knows that they are not crippled, and for that reason he removed packman, no longer needed. R> I received a security update for Lame, but it wouldn't install due to R> vendor change. I decided to remove Packman as I only use it for playing R> MP3 and it doesn't seem to be necessary for that anymore. - -- Cheers, Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlqYQ90ACgkQtTMYHG2NR9UgAACbBShrOx2hh42tcYJ1RDDZMjtZ fYUAnjvJ3NSjulcxb4byO0xnnDlY1yrz =nG58 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* John Andersen
On 03/01/2018 05:48 AM, Dave Plater wrote:
On 02/27/2018 02:24 AM, John Andersen wrote:
On 02/26/2018 01:10 PM, Richmond wrote:
Carlos E. R. wrote:
The first move is to, on the packman repo view, "disable switch to this repo" if it appears.
I am not sure where that is, but I didn't see it.
Next is disable the packman repo.
(If something was reinstalled from packman, it means you did not disable it, or that you have it twice. YaST can not enable itself a repo)
I did disable the packman repo, and it was not there twice.
The other question is WHY does Opensuse still have crippled mp3 packages when all mp3 patents have expired and every other distro includes them out of the box?
Which packages are still crippled?
Dave P
Ask the thread starter.
but you are the *only* one mentioning "crippled" packages, re: <quote> The other question is WHY does Opensuse still have crippled mp3 packages when all mp3 patents have expired and every other distro includes them out of the box? </quote> -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2018-02-26 at 21:10 -0000, Richmond wrote:
Carlos E. R. wrote:
The first move is to, on the packman repo view, "disable switch to this repo" if it appears.
I am not sure where that is, but I didn't see it.
See photos I sent to your private email. - -- Cheers, Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlqVUUMACgkQtTMYHG2NR9UW6QCeO/NeI7CAercWuhMBup5DcrWh Lr4AoJC0nAhQbVnSmeIHTp+EJCrkzZl2 =by8q -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Monday, 2018-02-26 at 21:10 -0000, Richmond wrote:
Carlos E. R. wrote:
The first move is to, on the packman repo view, "disable switch to this repo" if it appears.
I am not sure where that is, but I didn't see it.
See photos I sent to your private email.
Thanks. I don't remember what that was set to, but I think it was quite likely set to get system packages from Packman, because I now find that html5 video is broken. So that would explain why Chromium got removed when I removed the Packman repo. I seem to have gone around in a circle and discovered my own foot prints. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2018-02-27 at 17:20 -0000, Richmond wrote:
Carlos E. R. wrote:
On Monday, 2018-02-26 at 21:10 -0000, Richmond wrote:
Carlos E. R. wrote:
The first move is to, on the packman repo view, "disable switch to this repo" if it appears.
I am not sure where that is, but I didn't see it.
See photos I sent to your private email.
Thanks. I don't remember what that was set to, but I think it was quite likely set to get system packages from Packman, because I now find that html5 video is broken. So that would explain why Chromium got removed when I removed the Packman repo.
I seem to have gone around in a circle and discovered my own foot prints.
:-) Well, html5 may use a multitude of codecs, it is not a single one. - -- Cheers, Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlqWpSYACgkQtTMYHG2NR9XroQCeL0Ml3y4OD8SA239b6ACVBA/V 9lsAn2bc7JtDZBBDdkO8l476kWpL789B =eSzD -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op maandag 26 februari 2018 10:50:43 CET schreef Richmond:
I received a security update for Lame, but it wouldn't install due to vendor change. I decided to remove Packman as I only use it for playing MP3 and it doesn't seem to be necessary for that anymore.
So I went into yast2 sw_single and selected the repository view, and selected Packman and then selected Delete all packages in this list. I had to resolve dependencies which I did by selecting downgrade or de-installation in every case. One of the things it removed was Chromium.
I then disabled Packman, and re-installed Chromium. But this seemed to re-install libmp3lame from Packman even though it was disabled. So I removed it again and then removed Packman, then re-installed Chromium. This time it installed libmp3lame0 from openSUSE-Leap-42.3-Update. So what is the correct procedure for doing this, and why does yast2 install software from disabled repositories?
Remove the repo, run zypper dup and accept the vendor changes suggested by zypper. Package deletion just like that will probably bring a loss of funtionality. -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team Linux user #548252 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Knurpht - Gertjan Lettink
Op maandag 26 februari 2018 10:50:43 CET schreef Richmond:
I received a security update for Lame, but it wouldn't install due to vendor change. I decided to remove Packman as I only use it for playing MP3 and it doesn't seem to be necessary for that anymore.
So I went into yast2 sw_single and selected the repository view, and selected Packman and then selected Delete all packages in this list. I had to resolve dependencies which I did by selecting downgrade or de-installation in every case. One of the things it removed was Chromium.
I then disabled Packman, and re-installed Chromium. But this seemed to re-install libmp3lame from Packman even though it was disabled. So I removed it again and then removed Packman, then re-installed Chromium. This time it installed libmp3lame0 from openSUSE-Leap-42.3-Update. So what is the correct procedure for doing this, and why does yast2 install software from disabled repositories?
Remove the repo, run zypper dup and accept the vendor changes suggested by zypper. Package deletion just like that will probably bring a loss of funtionality.
his problem is with yast2 sw_single. he is probably unaware of zypper and the repos and the command line and the reason for packman. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Carlos E. R. -
Dave Plater -
John Andersen -
Knurpht - Gertjan Lettink -
Patrick Shanahan -
Richmond