-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
I manually added repository packman on Leap 15.0 (by URL). I then tried to change priority from 99 to 98. Yast warned:
Repository 'Ext_Packman' is managed by service". Your manual changes might be reset by the next service refresh!
What on earth is that!?
Note: The string «service".», I guess that '"' was '"', but I can not actually make it out what it was, too tiny.
- -- Cheers
Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
01.07.2018 00:25, Carlos E. R. пишет:
Hi,
I manually added repository packman on Leap 15.0 (by URL). I then tried to change priority from 99 to 98. Yast warned:
Repository 'Ext_Packman' is managed by service". Your manual changes might be reset by the next service refresh!What on earth is that!?
What "zypper ls -d" says?
Note: The string «service".», I guess that '"' was '"', but I can not actually make it out what it was, too tiny.
-- Cheers
Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 2018-07-01 06:40, Andrei Borzenkov wrote:
01.07.2018 00:25, Carlos E. R. пишет:
Hi,
I manually added repository packman on Leap 15.0 (by URL). I then tried to change priority from 99 to 98. Yast warned:
Repository 'Ext_Packman' is managed by service". Your manual changes might be reset by the next service refresh!What on earth is that!?
What "zypper ls -d" says?
I only added a local directory as plain rpm dir repo, and packman.
Legolas:~ # zypper ls -d # | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI ---+---------------------------------+-----------------------------------------+---------+-----------+---------+----------+----------+----------------------------------------------------------------------------------------- 1 | LocalRepo | LocalRepo | Yes | ( p) Yes | No | 99 | plaindir | dir:///root/LocalRepo 2 | download.opensuse.org-non-oss | Main Repository (NON-OSS) | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/distribution/leap/15.0/repo/non-oss/ 3 | download.opensuse.org-non-oss_1 | Update Repository (Non-Oss) | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.0/non-oss/ 4 | download.opensuse.org-oss | Main Repository (OSS) | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/distribution/leap/15.0/repo/oss/ 5 | download.opensuse.org-oss_1 | Main Update Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.0/oss 6 | openSUSE-Leap-15.0-1 | openSUSE-Leap-15.0-1 | No | ---- | ---- | 99 | rpm-md | hd:///?device=/dev/disk/by-id/usb-TOSHIBA_TransMemory_379964DED201CD9191D8BD3E-0:0-part2 7 | openSUSE_Leap_15.0 | Ext_Packman | Yes | (r ) Yes | Yes | 98 | rpm-md | http://ftp.gwdg.de/pub/linux/packman/suse/openSUSE_Leap_15.0/ 8 | repo-debug | openSUSE-Leap-15.0-Debug | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/distribution/leap/15.0/repo/oss/ 9 | repo-debug-non-oss | openSUSE-Leap-15.0-Debug-Non-Oss | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/distribution/leap/15.0/repo/non-oss/ 10 | repo-debug-update | openSUSE-Leap-15.0-Update-Debug | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/update/leap/15.0/oss/ 11 | repo-debug-update-non-oss | openSUSE-Leap-15.0-Update-Debug-Non-Oss | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/update/leap/15.0/non-oss/ 12 | repo-source | openSUSE-Leap-15.0-Source | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/source/distribution/leap/15.0/repo/oss/ 13 | repo-source-non-oss | openSUSE-Leap-15.0-Source-Non-Oss | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/source/distribution/leap/15.0/repo/non-oss/ Legolas:~ #
Right after adding the packman repo it said it was type "YUM".
Hello,
On Sat, 30 Jun 2018, Carlos E. R. wrote:
I manually added repository packman on Leap 15.0 (by URL). I then tried to change priority from 99 to 98. Yast warned:
Repository 'Ext_Packman' is managed by service". Your manual changes might be reset by the next service refresh!
What on earth is that!?
$ ls -l /etc/zypp/services.d/ $ man -P'less +/Services' zypper
HTH, -dnh
On 2018-07-01 20:36, David Haller wrote:
Hello,
On Sat, 30 Jun 2018, Carlos E. R. wrote:
I manually added repository packman on Leap 15.0 (by URL). I then tried to change priority from 99 to 98. Yast warned:
Repository 'Ext_Packman' is managed by service". Your manual changes might be reset by the next service refresh!
What on earth is that!?
$ ls -l /etc/zypp/services.d/
Legolas:~ # ls -l /etc/zypp/services.d/ total 0 Legolas:~ #
$ man -P'less +/Services' zypper
What do you expect me to read there? I have not added any service, I added Packman repo.
I did try to add packman from the community list, but it was not there. I had to type the URL myself instead.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Saturday, 2018-06-30 at 23:25 +0200, Carlos E. R. wrote:
Hi,
I manually added repository packman on Leap 15.0 (by URL). I then tried to change priority from 99 to 98. Yast warned:
Repository 'Ext_Packman' is managed by service". Your manual changes might be reset by the next service refresh!What on earth is that!?
Happened again now, when adding google-chrome.
- -- Cheers, Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" at Telcontar)
Op zaterdag 14 juli 2018 12:05:39 CEST schreef Carlos E. R.:
On Saturday, 2018-06-30 at 23:25 +0200, Carlos E. R. wrote:
Hi,
I manually added repository packman on Leap 15.0 (by URL). I then tried to
change priority from 99 to 98. Yast warned: Repository 'Ext_Packman' is managed by service". Your manual changes might be reset by the next service refresh!
What on earth is that!?
Happened again now, when adding google-chrome.
-- Cheers, Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" at Telcontar)
It is like it said, priorities in YaST for maintaining repositories do not work anymore/have no meaning. They should be removed from the table.
On 2018-07-14 12:12, Freek de Kruijf wrote:
Op zaterdag 14 juli 2018 12:05:39 CEST schreef Carlos E. R.:
On Saturday, 2018-06-30 at 23:25 +0200, Carlos E. R. wrote:
Hi,
I manually added repository packman on Leap 15.0 (by URL). I then tried to
change priority from 99 to 98. Yast warned: Repository 'Ext_Packman' is managed by service". Your manual changes might be reset by the next service refresh!
What on earth is that!?
Happened again now, when adding google-chrome.
It is like it said, priorities in YaST for maintaining repositories do not work anymore/have no meaning. They should be removed from the table.
It doesn't say that. It says that "they are managed by service". What is "service"? I don't have any service listed.
Why have them no meaning?
Doc for that? Announcement? There is nothing about this in the release notes.
Le 14/07/2018 à 13:07, Carlos E. R. a écrit :
Doc for that? Announcement? There is nothing about this in the release notes.
we was said, long time ago not to use priorities in YaST. Dunno why they are still there if of no use :-(
jdd
On 2018-07-14 13:12, jdd@dodin.org wrote:
Le 14/07/2018 à 13:07, Carlos E. R. a écrit :
Doc for that? Announcement? There is nothing about this in the release notes.
we was said, long time ago not to use priorities in YaST. Dunno why they are still there if of no use :-(
who said that? Of course they are useful. We have been using priorities since years.
Op zaterdag 14 juli 2018 13:07:35 CEST schreef Carlos E. R.:
On 2018-07-14 12:12, Freek de Kruijf wrote:
Op zaterdag 14 juli 2018 12:05:39 CEST schreef Carlos E. R.:
On Saturday, 2018-06-30 at 23:25 +0200, Carlos E. R. wrote:
Hi,
I manually added repository packman on Leap 15.0 (by URL). I then tried to
change priority from 99 to 98. Yast warned: Repository 'Ext_Packman' is managed by service". Your manual changes might be reset by the next service refresh!
What on earth is that!?
Happened again now, when adding google-chrome.
It is like it said, priorities in YaST for maintaining repositories do not work anymore/have no meaning. They should be removed from the table.
It doesn't say that. It says that "they are managed by service". What is "service"? I don't have any service listed.
Why have them no meaning?
Doc for that? Announcement? There is nothing about this in the release notes.
YaST in this area uses zypper, so read the zypper documentation about what a service in zypper is.
On 2018-07-14 13:50, Freek de Kruijf wrote:
Op zaterdag 14 juli 2018 13:07:35 CEST schreef Carlos E. R.:
On 2018-07-14 12:12, Freek de Kruijf wrote:
Op zaterdag 14 juli 2018 12:05:39 CEST schreef Carlos E. R.:
On Saturday, 2018-06-30 at 23:25 +0200, Carlos E. R. wrote:
Hi,
I manually added repository packman on Leap 15.0 (by URL). I then tried to
change priority from 99 to 98. Yast warned: Repository 'Ext_Packman' is managed by service". Your manual changes might be reset by the next service refresh!
What on earth is that!?
Happened again now, when adding google-chrome.
It is like it said, priorities in YaST for maintaining repositories do not work anymore/have no meaning. They should be removed from the table.
It doesn't say that. It says that "they are managed by service". What is "service"? I don't have any service listed.
Why have them no meaning?
Doc for that? Announcement? There is nothing about this in the release notes.
YaST in this area uses zypper, so read the zypper documentation about what a service in zypper is.
False. WE use YaST, not zypper.
I have no services.
Legolas:~ # ls -l /etc/zypp/services.d/ total 0 Legolas:~ #
14.07.2018 13:05, Carlos E. R. пишет:
On Saturday, 2018-06-30 at 23:25 +0200, Carlos E. R. wrote:
Hi,
I manually added repository packman on Leap 15.0 (by URL). I then tried to change priority from 99 to 98. Yast warned:
Repository 'Ext_Packman' is managed by service". Your manual changes might be reset by the next service refresh!What on earth is that!?
Happened again now, when adding google-chrome.
What is the content of this repository definition file?
On 2018-07-14 14:05, Andrei Borzenkov wrote:
14.07.2018 13:05, Carlos E. R. пишет:
On Saturday, 2018-06-30 at 23:25 +0200, Carlos E. R. wrote:
Hi,
I manually added repository packman on Leap 15.0 (by URL). I then tried to change priority from 99 to 98. Yast warned:
Repository 'Ext_Packman' is managed by service". Your manual changes might be reset by the next service refresh!What on earth is that!?
Happened again now, when adding google-chrome.
What is the content of this repository definition file?
There are two - something created another:
/etc/zypp/repos.d/google-chrome.repo:
[google-chrome] name=google-chrome enabled=1 autorefresh=1 baseurl=http://dl.google.com/linux/chrome/rpm/stable/x86_64 type=rpm-md keeppackages=0
/etc/zypp/repos.d/x86_64.repo - created 4 minutes later
[x86_64] name=google-chrome enabled=1 autorefresh=1 baseurl=http://dl.google.com/linux/chrome/rpm/stable/x86_64 path=/ type=rpm-md priority=105 keeppackages=0
I suppose that google is up to their antics: they installed a cron script that adds another repo, but that was _after_ I installed the package I wanted, not at the time I had this yast message.
The previous issue was with packman:
/etc/zypp/repos.d/openSUSE_Leap_15.0.repo
[openSUSE_Leap_15.0] name=Ext_Packman enabled=1 autorefresh=1 baseurl=http://ftp.gwdg.de/pub/linux/packman/suse/openSUSE_Leap_15.0/ path=/ type=rpm-md priority=98 keeppackages=0
Legolas:~ # zypper lr --details Repository priorities in effect: (See 'zypper lr -P' for details) 98 (raised priority) : 1 repository 99 (default priority) : 7 repositories 105 (lowered priority) : 1 repository
# | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service ---+---------------------------------+-----------------------------------------+---------+-----------+---------+----------+----------+------------------------------------------------------------------------------------------+-------- 6 | google-chrome | google-chrome | Yes | (r ) Yes | Yes | 99 | rpm-md | http://dl.google.com/linux/chrome/rpm/stable/x86_64 |
8 | openSUSE_Leap_15.0 | Ext_Packman | Yes | (r ) Yes | Yes | 98 | rpm-md | http://ftp.gwdg.de/pub/linux/packman/suse/openSUSE_Leap_15.0/ |
16 | x86_64 | google-chrome | Yes | ( p) Yes | Yes | 105 | rpm-md | http://dl.google.com/linux/chrome/rpm/stable/x86_64 |
As you can see, they have different priories.
14.07.2018 15:55, Carlos E. R. пишет:
On 2018-07-14 14:05, Andrei Borzenkov wrote:
14.07.2018 13:05, Carlos E. R. пишет:
On Saturday, 2018-06-30 at 23:25 +0200, Carlos E. R. wrote:
Hi,
I manually added repository packman on Leap 15.0 (by URL). I then tried to change priority from 99 to 98. Yast warned:
Repository 'Ext_Packman' is managed by service". Your manual changes might be reset by the next service refresh!What on earth is that!?
Happened again now, when adding google-chrome.
What is the content of this repository definition file?
There are two - something created another:
/etc/zypp/repos.d/google-chrome.repo:
[google-chrome] name=google-chrome enabled=1 autorefresh=1 baseurl=http://dl.google.com/linux/chrome/rpm/stable/x86_64 type=rpm-md keeppackages=0
/etc/zypp/repos.d/x86_64.repo - created 4 minutes later
[x86_64] name=google-chrome enabled=1 autorefresh=1 baseurl=http://dl.google.com/linux/chrome/rpm/stable/x86_64 path=/ type=rpm-md priority=105 keeppackages=0
Well, none of them has "service" keyword which as far as I can tell is the only reason to display this warning. You should really open bug report.
On 2018-07-14 16:41, Andrei Borzenkov wrote:
14.07.2018 15:55, Carlos E. R. пишет:
Well, none of them has "service" keyword which as far as I can tell is the only reason to display this warning. You should really open bug report.
Thanks, will do.
-
Andrei Borzenkov -
Carlos E. R. -
David Haller -
Freek de Kruijf -
jdd＠dodin.org