OBS Uyuni Master Repo Updates
Hello, 1. can you please update the project config to contain these lines for AlmaLinux at https://build.opensuse.org/projects/systemsmanagement:Uyuni:Master/prjconf ExpandFlags: module:squid-4 # Required for spacewalk-proxy-installer FileProvides: /usr/sbin/semanage policycoreutils-python policycoreutils-python-utils (Note that the FileProvides line is an update to an existing entry) 2. Also please disable these packages for AlmaLinux as they are not required: - golang-github-prometheus-node_exporter - grafana - python-gzipstream - spacewalk-abrt - susemanager-branding-oss - system-user-grafana - zypp-plugin-spacewalk Thank you and best wishes, Stefan
On lunes, 27 de septiembre de 2021 14:13:17 (CEST) Stefan Bluhm wrote:
Hello,
1. can you please update the project config to contain these lines for AlmaLinux at https://build.opensuse.org/projects/systemsmanagement:Uyuni:Master/prjconf
ExpandFlags: module:squid-4 # Required for spacewalk-proxy-installer
FileProvides: /usr/sbin/semanage policycoreutils-python policycoreutils-python-utils
(Note that the FileProvides line is an update to an existing entry)
Done.
2. Also please disable these packages for AlmaLinux as they are not required:
- golang-github-prometheus-node_exporter
This is required by the server and the proxy, so both can be monitored by a prometheus service installed any client.
- grafana
In fact it's not needed for Server/Proxy on Leap either. This is there just so it can be linked for some client tools. I just disable it.
- python-gzipstream
This one is at Leap, and it was removed from Git some months ago, so I am removing it.
- spacewalk-abrt
I see it as part of the CentOS6 and CentOS7 client tools. Michael, I seem to remember we deprecated or something? If not, I will disable it, as this comes from Git and is then linked at the CentOS client tools.
- susemanager-branding-oss
Are you sure? This is one is required for the Server prioduct definition. Michael, what was this used for?
- system-user-grafana
Same as grafana. Disabled.
- zypp-plugin-spacewalk
Are you sure? This is part of the Proxy product definition. Michael, what was this used for? -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com
Thank you!
- golang-github-prometheus-node_exporter
that is included in the base OS for Alma.
- spacewalk-abrt Was told not to use it anymore. otherwise I have a fix to make it build.
- susemanager-branding-oss I might have removed it then at some stage as I was told that it is not required (or so I think).
- zypp-plugin-spacewalk Isn't that the plugin for zypper and/or reposync? Dnf has its own plugin
Note, I am only talking about disabling for AlmaLinux. Best wishes, Stefan ----- Ursprüngliche Mail ----- Von: "Julio Gonzalez" <jgonzalez@suse.com> An: "devel" <devel@lists.uyuni-project.org> CC: "Stefan Bluhm" <opensuse.org@bluhm-de.com> Gesendet: Montag, 27. September 2021 14:37:20 Betreff: Re: OBS Uyuni Master Repo Updates On lunes, 27 de septiembre de 2021 14:13:17 (CEST) Stefan Bluhm wrote:
Hello,
1. can you please update the project config to contain these lines for AlmaLinux at https://build.opensuse.org/projects/systemsmanagement:Uyuni:Master/prjconf
ExpandFlags: module:squid-4 # Required for spacewalk-proxy-installer
FileProvides: /usr/sbin/semanage policycoreutils-python policycoreutils-python-utils
(Note that the FileProvides line is an update to an existing entry)
Done.
2. Also please disable these packages for AlmaLinux as they are not required:
- golang-github-prometheus-node_exporter
This is required by the server and the proxy, so both can be monitored by a prometheus service installed any client.
- grafana
In fact it's not needed for Server/Proxy on Leap either. This is there just so it can be linked for some client tools. I just disable it.
- python-gzipstream
This one is at Leap, and it was removed from Git some months ago, so I am removing it.
- spacewalk-abrt
I see it as part of the CentOS6 and CentOS7 client tools. Michael, I seem to remember we deprecated or something? If not, I will disable it, as this comes from Git and is then linked at the CentOS client tools.
- susemanager-branding-oss
Are you sure? This is one is required for the Server prioduct definition. Michael, what was this used for?
- system-user-grafana
Same as grafana. Disabled.
- zypp-plugin-spacewalk
Are you sure? This is part of the Proxy product definition. Michael, what was this used for? -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com
On lunes, 27 de septiembre de 2021 14:47:28 (CEST) Stefan Bluhm wrote:
Thank you!
- golang-github-prometheus-node_exporter
that is included in the base OS for Alma.
What version? We should use the same version for all OS.
- spacewalk-abrt
Was told not to use it anymore. otherwise I have a fix to make it build.
@mcalmer? I see we still have it at the Git repository. Time to remove it from there, and from the OBS projects?
- susemanager-branding-oss
I might have removed it then at some stage as I was told that it is not required (or so I think).
@mcalmer?
- zypp-plugin-spacewalk
Isn't that the plugin for zypper and/or reposync? Dnf has its own plugin Note, I am only talking about disabling for AlmaLinux.
Could be this is only required for traditional proxies? Michael? If so we don't need it for neither Leap or CentOS.
Best wishes,
Stefan
----- Ursprüngliche Mail ----- Von: "Julio Gonzalez" <jgonzalez@suse.com> An: "devel" <devel@lists.uyuni-project.org> CC: "Stefan Bluhm" <opensuse.org@bluhm-de.com> Gesendet: Montag, 27. September 2021 14:37:20 Betreff: Re: OBS Uyuni Master Repo Updates
On lunes, 27 de septiembre de 2021 14:13:17 (CEST) Stefan Bluhm wrote:
Hello,
1. can you please update the project config to contain these lines for AlmaLinux at https://build.opensuse.org/projects/systemsmanagement:Uyuni:Master/prjconf
ExpandFlags: module:squid-4 # Required for spacewalk-proxy-installer
FileProvides: /usr/sbin/semanage policycoreutils-python policycoreutils-python-utils
(Note that the FileProvides line is an update to an existing entry)
Done.
2. Also please disable these packages for AlmaLinux as they are not required:
- golang-github-prometheus-node_exporter
This is required by the server and the proxy, so both can be monitored by a prometheus service installed any client.
- grafana
In fact it's not needed for Server/Proxy on Leap either. This is there just so it can be linked for some client tools. I just disable it.
- python-gzipstream
This one is at Leap, and it was removed from Git some months ago, so I am removing it.
- spacewalk-abrt
I see it as part of the CentOS6 and CentOS7 client tools. Michael, I seem to remember we deprecated or something?
If not, I will disable it, as this comes from Git and is then linked at the CentOS client tools.
- susemanager-branding-oss
Are you sure? This is one is required for the Server prioduct definition. Michael, what was this used for?
- system-user-grafana
Same as grafana. Disabled.
- zypp-plugin-spacewalk
Are you sure? This is part of the Proxy product definition. Michael, what was this used for?
-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com
Hi Am Montag, 27. September 2021, 14:53:48 CEST schrieb Julio Gonzalez:
On lunes, 27 de septiembre de 2021 14:47:28 (CEST) Stefan Bluhm wrote:
Thank you!
- golang-github-prometheus-node_exporter
that is included in the base OS for Alma.
What version? We should use the same version for all OS.
- spacewalk-abrt
Was told not to use it anymore. otherwise I have a fix to make it build.
@mcalmer? I see we still have it at the Git repository. Time to remove it from there, and from the OBS projects?
I think we can remove it from Head now. in 4.2 we still need it as it is still supported in 4.1 and all client tools currently come from 4.2 branch. We still have 3 month to go with 4.1 when we released 4.3, but in worst case we submit from 4.2 branch.
- susemanager-branding-oss
I might have removed it then at some stage as I was told that it is not required (or so I think).
@mcalmer?
This package has the SUMA EULA and is not available for Uyuni. We do not have it in Uyuni:Master . But we need it for SUSE Manager.
- zypp-plugin-spacewalk
Isn't that the plugin for zypper and/or reposync? Dnf has its own plugin Note, I am only talking about disabling for AlmaLinux.
Could be this is only required for traditional proxies? Michael? If so we don't need it for neither Leap or CentOS.
It is required for traditional clients in general. As we do not support traditional clients in Uyuni, we could remove it from there. For SUSE Manager this is still needed. Regards Michael
----- Ursprüngliche Mail ----- Von: "Julio Gonzalez" <jgonzalez@suse.com> An: "devel" <devel@lists.uyuni-project.org> CC: "Stefan Bluhm" <opensuse.org@bluhm-de.com> Gesendet: Montag, 27. September 2021 14:37:20 Betreff: Re: OBS Uyuni Master Repo Updates
On lunes, 27 de septiembre de 2021 14:13:17 (CEST) Stefan Bluhm wrote:
Hello,
1. can you please update the project config to contain these lines for AlmaLinux at https://build.opensuse.org/projects/systemsmanagement:Uyuni:Master/prjconf
ExpandFlags: module:squid-4 # Required for spacewalk-proxy-installer
FileProvides: /usr/sbin/semanage policycoreutils-python policycoreutils-python-utils
(Note that the FileProvides line is an update to an existing entry)
Done.
2. Also please disable these packages for AlmaLinux as they are not required:
- golang-github-prometheus-node_exporter
This is required by the server and the proxy, so both can be monitored by a prometheus service installed any client.
- grafana
In fact it's not needed for Server/Proxy on Leap either. This is there just so it can be linked for some client tools. I just disable it.
- python-gzipstream
This one is at Leap, and it was removed from Git some months ago, so I am removing it.
- spacewalk-abrt
I see it as part of the CentOS6 and CentOS7 client tools. Michael, I seem to remember we deprecated or something?
If not, I will disable it, as this comes from Git and is then linked at the CentOS client tools.
- susemanager-branding-oss
Are you sure? This is one is required for the Server prioduct definition. Michael, what was this used for?
- system-user-grafana
Same as grafana. Disabled.
- zypp-plugin-spacewalk
Are you sure? This is part of the Proxy product definition. Michael, what was this used for?
-- Regards Michael Calmer -------------------------------------------------------------------------- Michael Calmer SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg T: +49 (0) 911 74053 0 F: +49 (0) 911 74053575 - e-mail: Michael.Calmer@suse.com -------------------------------------------------------------------------- SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer (HRB 36809, AG Nürnberg)
On martes, 28 de septiembre de 2021 9:32:44 (CEST) Michael Calmer wrote:
Hi
Am Montag, 27. September 2021, 14:53:48 CEST schrieb Julio Gonzalez:
On lunes, 27 de septiembre de 2021 14:47:28 (CEST) Stefan Bluhm wrote:
Thank you!
- golang-github-prometheus-node_exporter
that is included in the base OS for Alma.
What version? We should use the same version for all OS.
- spacewalk-abrt
Was told not to use it anymore. otherwise I have a fix to make it build.
@mcalmer? I see we still have it at the Git repository. Time to remove it from there, and from the OBS projects?
I think we can remove it from Head now. in 4.2 we still need it as it is still supported in 4.1 and all client tools currently come from 4.2 branch. We still have 3 month to go with 4.1 when we released 4.3, but in worst case we submit from 4.2 branch.
OK, I will take care.
- susemanager-branding-oss
I might have removed it then at some stage as I was told that it is not required (or so I think).
@mcalmer?
This package has the SUMA EULA and is not available for Uyuni. We do not have it in Uyuni:Master . But we need it for SUSE Manager.
We do have it, as it's submitted from the Git repo. But I will disable the build for EL, as Stefan requested.
- zypp-plugin-spacewalk
Isn't that the plugin for zypper and/or reposync? Dnf has its own plugin Note, I am only talking about disabling for AlmaLinux.
Could be this is only required for traditional proxies? Michael? If so we don't need it for neither Leap or CentOS.
It is required for traditional clients in general. As we do not support traditional clients in Uyuni, we could remove it from there. For SUSE Manager this is still needed.
We do support Traditional for SLE12/15, but not for the proxies, so it can get disabled for systemsmanager:Uyuni:Master and removed from the Uyuni proxy definition. I will take care.
Regards
Michael
----- Ursprüngliche Mail ----- Von: "Julio Gonzalez" <jgonzalez@suse.com> An: "devel" <devel@lists.uyuni-project.org> CC: "Stefan Bluhm" <opensuse.org@bluhm-de.com> Gesendet: Montag, 27. September 2021 14:37:20 Betreff: Re: OBS Uyuni Master Repo Updates
On lunes, 27 de septiembre de 2021 14:13:17 (CEST) Stefan Bluhm wrote:
Hello,
1. can you please update the project config to contain these lines for AlmaLinux at https://build.opensuse.org/projects/systemsmanagement:Uyuni:Master/prj conf
ExpandFlags: module:squid-4 # Required for spacewalk-proxy-installer
FileProvides: /usr/sbin/semanage policycoreutils-python policycoreutils-python-utils
(Note that the FileProvides line is an update to an existing entry)
Done.
2. Also please disable these packages for AlmaLinux as they are not required:
- golang-github-prometheus-node_exporter
This is required by the server and the proxy, so both can be monitored by a prometheus service installed any client.
- grafana
In fact it's not needed for Server/Proxy on Leap either. This is there just so it can be linked for some client tools. I just disable it.
- python-gzipstream
This one is at Leap, and it was removed from Git some months ago, so I am removing it.
- spacewalk-abrt
I see it as part of the CentOS6 and CentOS7 client tools. Michael, I seem to remember we deprecated or something?
If not, I will disable it, as this comes from Git and is then linked at the CentOS client tools.
- susemanager-branding-oss
Are you sure? This is one is required for the Server prioduct definition. Michael, what was this used for?
- system-user-grafana
Same as grafana. Disabled.
- zypp-plugin-spacewalk
Are you sure? This is part of the Proxy product definition. Michael, what was this used for?
-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com
On martes, 28 de septiembre de 2021 11:40:35 (CEST) Julio Gonzalez wrote:
On martes, 28 de septiembre de 2021 9:32:44 (CEST) Michael Calmer wrote:
Hi
Am Montag, 27. September 2021, 14:53:48 CEST schrieb Julio Gonzalez:
On lunes, 27 de septiembre de 2021 14:47:28 (CEST) Stefan Bluhm wrote:
Thank you!
- golang-github-prometheus-node_exporter
that is included in the base OS for Alma.
What version? We should use the same version for all OS.
- spacewalk-abrt
Was told not to use it anymore. otherwise I have a fix to make it build.
@mcalmer? I see we still have it at the Git repository. Time to remove it from there, and from the OBS projects?
I think we can remove it from Head now. in 4.2 we still need it as it is still supported in 4.1 and all client tools currently come from 4.2 branch. We still have 3 month to go with 4.1 when we released 4.3, but in worst case we submit from 4.2 branch.
OK, I will take care.
I will create a card for this. There are mentions to abrt at the java code, spacecmd code, doc... So my guess is that this goes beyond removing spacewalk- abrt from the repository.
- susemanager-branding-oss
I might have removed it then at some stage as I was told that it is not required (or so I think).
@mcalmer?
This package has the SUMA EULA and is not available for Uyuni. We do not have it in Uyuni:Master . But we need it for SUSE Manager.
We do have it, as it's submitted from the Git repo. But I will disable the build for EL, as Stefan requested.
- zypp-plugin-spacewalk
Isn't that the plugin for zypper and/or reposync? Dnf has its own plugin Note, I am only talking about disabling for AlmaLinux.
Could be this is only required for traditional proxies? Michael? If so we don't need it for neither Leap or CentOS.
It is required for traditional clients in general. As we do not support traditional clients in Uyuni, we could remove it from there. For SUSE Manager this is still needed.
We do support Traditional for SLE12/15, but not for the proxies, so it can get disabled for systemsmanager:Uyuni:Master and removed from the Uyuni proxy definition.
I will take care.
Regards
Michael
----- Ursprüngliche Mail ----- Von: "Julio Gonzalez" <jgonzalez@suse.com> An: "devel" <devel@lists.uyuni-project.org> CC: "Stefan Bluhm" <opensuse.org@bluhm-de.com> Gesendet: Montag, 27. September 2021 14:37:20 Betreff: Re: OBS Uyuni Master Repo Updates
On lunes, 27 de septiembre de 2021 14:13:17 (CEST) Stefan Bluhm wrote:
Hello,
1. can you please update the project config to contain these lines for AlmaLinux at https://build.opensuse.org/projects/systemsmanagement:Uyuni:Master/p rj conf
ExpandFlags: module:squid-4 # Required for spacewalk-proxy-installer
FileProvides: /usr/sbin/semanage policycoreutils-python policycoreutils-python-utils
(Note that the FileProvides line is an update to an existing entry)
Done.
2. Also please disable these packages for AlmaLinux as they are not required:
- golang-github-prometheus-node_exporter
This is required by the server and the proxy, so both can be monitored by a prometheus service installed any client.
- grafana
In fact it's not needed for Server/Proxy on Leap either. This is there just so it can be linked for some client tools. I just disable it.
- python-gzipstream
This one is at Leap, and it was removed from Git some months ago, so I am removing it.
- spacewalk-abrt
I see it as part of the CentOS6 and CentOS7 client tools. Michael, I seem to remember we deprecated or something?
If not, I will disable it, as this comes from Git and is then linked at the CentOS client tools.
- susemanager-branding-oss
Are you sure? This is one is required for the Server prioduct definition. Michael, what was this used for?
- system-user-grafana
Same as grafana. Disabled.
- zypp-plugin-spacewalk
Are you sure? This is part of the Proxy product definition. Michael, what was this used for?
-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com
On martes, 28 de septiembre de 2021 13:23:03 (CEST) Julio Gonzalez wrote:
On martes, 28 de septiembre de 2021 11:40:35 (CEST) Julio Gonzalez wrote:
On martes, 28 de septiembre de 2021 9:32:44 (CEST) Michael Calmer wrote:
Hi
Am Montag, 27. September 2021, 14:53:48 CEST schrieb Julio Gonzalez:
On lunes, 27 de septiembre de 2021 14:47:28 (CEST) Stefan Bluhm wrote:
- spacewalk-abrt
Was told not to use it anymore. otherwise I have a fix to make it build.
@mcalmer? I see we still have it at the Git repository. Time to remove it from there, and from the OBS projects?
I think we can remove it from Head now. in 4.2 we still need it as it is still supported in 4.1 and all client tools currently come from 4.2 branch. We still have 3 month to go with 4.1 when we released 4.3, but in worst case we submit from 4.2 branch.
OK, I will take care.
I will create a card for this. There are mentions to abrt at the java code, spacecmd code, doc... So my guess is that this goes beyond removing spacewalk- abrt from the repository.
We already had one so I asked our PO to give it some priority. Until that moment, we better keep spacewalk-abrt broken. Disabling could break things because of the references at spacecmd, java, etc. Such references should probably get removed. -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com
On martes, 28 de septiembre de 2021 13:27:46 (CET) Julio Gonzalez wrote:
On martes, 28 de septiembre de 2021 13:23:03 (CEST) Julio Gonzalez wrote:
On martes, 28 de septiembre de 2021 11:40:35 (CEST) Julio Gonzalez wrote:
On martes, 28 de septiembre de 2021 9:32:44 (CEST) Michael Calmer wrote:
Hi
Am Montag, 27. September 2021, 14:53:48 CEST schrieb Julio Gonzalez:
On lunes, 27 de septiembre de 2021 14:47:28 (CEST) Stefan Bluhm wrote:
> - spacewalk-abrt
Was told not to use it anymore. otherwise I have a fix to make it build.
@mcalmer? I see we still have it at the Git repository. Time to remove it from there, and from the OBS projects?
I think we can remove it from Head now. in 4.2 we still need it as it is still supported in 4.1 and all client tools currently come from 4.2 branch. We still have 3 month to go with 4.1 when we released 4.3, but in worst case we submit from 4.2 branch.
OK, I will take care.
I will create a card for this. There are mentions to abrt at the java code, spacecmd code, doc... So my guess is that this goes beyond removing spacewalk- abrt from the repository.
We already had one so I asked our PO to give it some priority. Until that moment, we better keep spacewalk-abrt broken. Disabling could break things because of the references at spacecmd, java, etc. Such references should probably get removed.
@Stefan: this is done now. We kept the references at spacecmd, as we need it for a few more months, but `spacewalk-abrt` is gone from systemsmanagement:Uyuni:Master and the Git repository. -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com
On lunes, 27 de septiembre de 2021 14:47:28 (CEST) Stefan Bluhm wrote:
- golang-github-prometheus-node_exporter
that is included in the base OS for Alma.
What version? We should use the same version for all OS.
EPEL has golang-github-prometheus-node-exporter-1.2.2-1.el8.x86_64 Uyuni:Master has 1.1.2 So we should keep the Uyuni:Master one instead?
On martes, 28 de septiembre de 2021 11:52:55 (CEST) Stefan Bluhm wrote:
On lunes, 27 de septiembre de 2021 14:47:28 (CEST) Stefan Bluhm wrote:
- golang-github-prometheus-node_exporter
that is included in the base OS for Alma.
What version? We should use the same version for all OS.
EPEL has golang-github-prometheus-node-exporter-1.2.2-1.el8.x86_64 Uyuni:Master has 1.1.2
So we should keep the Uyuni:Master one instead?
That's EPEL, not AlmaLinux. I guess we should update our node exporter, but anyway: are we requiring EPEL to install Uyuni on top of Alma Linux8? Because EPEL still breaks salt, AFAIK. -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com
- golang-github-prometheus-node_exporter
that is included in the base OS for Alma.
What version? We should use the same version for all OS.
EPEL has golang-github-prometheus-node-exporter-1.2.2-1.el8.x86_64
That's EPEL, not AlmaLinux.
Yepp correct, ignored that fact....
I guess we should update our node exporter, but anyway: are we requiring EPEL to install Uyuni on top of Alma Linux8? Because EPEL still breaks salt, AFAIK.
Yes, EPEL is definitely required. Salt is installed from the Uyuni:Master. EPEL does not provide salt. What is the breakage? I never noticed anything. Best wishes, Stefan
On martes, 28 de septiembre de 2021 13:13:05 (CEST) Stefan Bluhm wrote:
- golang-github-prometheus-node_exporter
that is included in the base OS for Alma.
What version? We should use the same version for all OS.
EPEL has golang-github-prometheus-node-exporter-1.2.2-1.el8.x86_64
That's EPEL, not AlmaLinux.
Yepp correct, ignored that fact....
I guess we should update our node exporter, but anyway: are we requiring EPEL to install Uyuni on top of Alma Linux8? Because EPEL still breaks salt, AFAIK. Yes, EPEL is definitely required. Salt is installed from the Uyuni:Master. EPEL does not provide salt. What is the breakage? I never noticed anything.
A conflict with python-zeromq. Maybe that's already fixed for EPEL8, but I can clearly remember we had it for EPEL7. Several issues were created, including https://github.com/uyuni-project/uyuni/issues/3135 However if we require EPEL, are you sure we do not get any other unwanted dependencies that can cause problems?
Best wishes,
Stefan
-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com
Carrying on the conversation under a new subject.
Because EPEL still breaks salt, AFAIK. Yes, EPEL is definitely required. Salt is installed from the Uyuni:Master. EPEL does not provide salt. What is the breakage? I never noticed anything.
A conflict with python-zeromq. Maybe that's already fixed for EPEL8, but I can clearly remember we had it for EPEL7. Several issues were created, including https://github.com/uyuni-project/uyuni/issues/3135
However if we require EPEL, are you sure we do not get any other unwanted dependencies that can cause problems?
pythonX-zeromq is not in EPEL8. The linked issue sounds interesting. There might be conflicts with zeromq itself as that is included. There must be (more or less) nice workarounds to get that sorted. For now, I have been using EPEL for my tests and haven't encountered any issues. Seems that testing needs to be extended. Let me also repeat the above use case at a (much) later time. Previously we discussed picking/copying required packages from EPEL for a Uyuni release. Maybe this could still be an option although it sounds like some significant maintenance activity. My strategy (for now) would be to keep EPEL running and fix any identified issues along the way. @juliogonzalez/@mcalmer: On that note, is there any chance to enable Publishing of the AlmaLinux packages on Uyuni:Master? That way, I can get the required packages directly "from source". Best wishes, Stefan
On martes, 28 de septiembre de 2021 14:43:50 (CEST) Stefan Bluhm wrote:
Carrying on the conversation under a new subject.
Because EPEL still breaks salt, AFAIK.
Yes, EPEL is definitely required. Salt is installed from the Uyuni:Master. EPEL does not provide salt. What is the breakage? I never noticed anything.
A conflict with python-zeromq. Maybe that's already fixed for EPEL8, but I can clearly remember we had it for EPEL7. Several issues were created, including https://github.com/uyuni-project/uyuni/issues/3135
However if we require EPEL, are you sure we do not get any other unwanted dependencies that can cause problems?
pythonX-zeromq is not in EPEL8. The linked issue sounds interesting. There might be conflicts with zeromq itself as that is included. There must be (more or less) nice workarounds to get that sorted. For now, I have been using EPEL for my tests and haven't encountered any issues. Seems that testing needs to be extended. Let me also repeat the above use case at a (much) later time.
Previously we discussed picking/copying required packages from EPEL for a Uyuni release. Maybe this could still be an option although it sounds like some significant maintenance activity.
Do we have numbers or a list of the packages you are taking from EPEL as of today?
My strategy (for now) would be to keep EPEL running and fix any identified issues along the way.
For now it's OK, but the danger I see is that EPEL can work now, but can get a new package in the future (or a version bump) that breaks the server or the proxy. In the end EPEL is less restrictive than RHEL/CentOS/Alma/Rocky for such things :-)
@juliogonzalez/@mcalmer: On that note, is there any chance to enable Publishing of the AlmaLinux packages on Uyuni:Master? That way, I can get the required packages directly "from source".
OK, done. https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Master/ AlmaLinux_8/ is available now. But IIRC I will need to disable publishig *and* wipe the repositories when I am going to promote the next Uyunui version. Otherwise the promotion mechanism doesn't work and we don't really want to bump to Stable now.
Best wishes,
Stefan
-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com
Do we have numbers or a list of the packages you are taking from EPEL as of today?
If my current install is correct/complete, these are 36 packages only. I assumed much more :). But will be increasing as I am trying to include more packages there. Am wondering if we should create an "Uyuni" module with the relevant versions. That would make installation a lot more consistent. cobbler.noarch 3.2.0-2.module_el8+10474+71f42bad @epel-modular google-gson.noarch 2.8.2-4.el8 @epel libgsasl.x86_64 1.8.0-8.el8 @epel libntlm.x86_64 1.6-1.el8 @epel libsodium.x86_64 1.0.18-2.el8 @epel libtomcrypt.x86_64 1.18.2-5.el8 @epel libtommath.x86_64 1.1.0-1.el8 @epel libunwind.x86_64 1.3.1-3.el8 @epel mod_xsendfile.x86_64 0.12-23.el8 @epel openpgm.x86_64 5.2.122-21.el8 @epel perl-Net-LibIDN.x86_64 0.12-35.el8 @epel python-django3-bash-completion.noarch 3.1.7-1.el8 @epel python2-psutil.x86_64 5.6.3-6.el8 @epel python3-asgiref.noarch 3.2.10-1.el8 @epel python3-cheetah.x86_64 3.2.3-2.el8 @epel python3-cheroot.noarch 8.5.2-1.el8 @epel python3-cherrypy.noarch 18.4.0-1.el8 @epel python3-django3.noarch 3.1.7-1.el8 @epel python3-future.noarch 0.18.2-2.el8 @epel python3-jaraco.noarch 6.2-6.el8 @epel python3-jaraco-functools.noarch 2.0-4.el8 @epel python3-ldap3.noarch 2.8.1-2.el8 @epel python3-more-itertools.noarch 7.2.0-3.el8 @epel python3-msgpack.x86_64 0.6.2-1.el8 @epel python3-pam.noarch 1.8.4-6.el8 @epel python3-portend.noarch 2.6-1.el8 @epel python3-pyvmomi.noarch 7.0.2-1.el8 @epel python3-simplejson.x86_64 3.17.0-2.el8 @epel python3-sqlparse.noarch 0.2.4-6.el8 @epel python3-tempora.noarch 1.14.1-5.el8 @epel python3-tornado.x86_64 6.0.2-1.el8 @epel python3-trustme.noarch 0.6.0-4.el8 @epel python3-zc-lockfile.noarch 2.0-2.el8 @epel python3-zmq.x86_64 19.0.0-1.el8 @epel tomcat-native.x86_64 1.2.23-1.el8 @epel zeromq.x86_64 4.3.4-2.el8 @epel
But IIRC I will need to disable publishig *and* wipe the repositories when I am going to promote the next Uyunui version. Otherwise the promotion mechanism doesn't work and we don't really want to bump to Stable now.
Ah, that was the reason.
participants (3)
-
Julio Gonzalez -
Michael Calmer -
Stefan Bluhm