tickets #115667
closedpontifex: Deployment of openSUSE-release-tools-publish-distro from openSUSE:Tools repo
100%
Description
Hello heroes!
we've moved publish_distro from publish_disto.git to openSUSE-release-tools.git on github
https://github.com/openSUSE/publish_distro/pull/21
The idea is to ensure that we consume the publish_distro (nowadays /usr/bin/osrt-publish_distro) tool from rpm.
openSUSE release tools is build within openSUSE:Tools repository from where I'd like to consume it.
https://build.opensuse.org/project/show/openSUSE:Tools
This was previously checkout under the ~mirror/publish_distro.
Waiting for package update to land in Leap via maintenance update would simply take way too much time and people would fallback to consuming tool and configs via git anyway.
Any objection from your side, before I'd add repository https://download.opensuse.org/repositories/openSUSE:/Tools/15.4/openSUSE:Tools.repo
and install openSUSE-release-tools-publish_distro from it?
Thank you
Lubos
Updated by lkocman over 1 year ago
- Status changed from New to Blocked
Blocking on feedback / acknowledgement from others.
Updated by lkocman over 1 year ago
- Category changed from Planet to Core services and virtual infrastructure
Updated by lkocman over 1 year ago
Unless somebody proposes otherwise, I'd enable such way of deployment of package on Friday.
Updated by pjessen over 1 year ago
I don't see any immediate issue, but maybe you could describe what impact this will have.
Updated by cboltz over 1 year ago
No real objection, more a question - will you only need this single package from openSUSE:Tools? If so, osc linkpacing it into the openSUSE:infrastructure repo might be a better idea than adding a repo.
Hello cboltz, that is correct. If team is used to deploy things from the infrastructure repo, then I could linkpac it and add to meta as I'm sure we'll need to be in sync with relevant osclib from the same repo etc.
If that is preferred then I'm fine with that as well.
Updated by lkocman over 1 year ago
Otherwise as far as impact of my original proposal goes, we would newly consume (openSUSE-release-tools-* is not installed) with a non-openSUSE signature from the "Tools repo". The scope of the repository is rather small, so I don't expect any other risks.
I have personally always consumed it from Tools repo.
Updated by andriinikitin over 1 year ago
So as far as I understand - only release team is using these scripts. So, since they have root access anyway - I don't see any disadvantage if a new repository is added. (which doesn't need additional approvals besides the release team).
Updated by lkocman over 1 year ago
- Status changed from Blocked to Workable
Thank you for the feedback. Proceeding with the original plan and openSUSE Tools repository.
Lubos
Updated by lkocman over 1 year ago
pontifex2 (download.o.o):/etc/zypp/repos.d # cat *Tools*.repo
[openSUSE_Tools]
name=openSUSE.org tools
enabled=1
autorefresh=0
baseurl=https://download.opensuse.org/repositories/openSUSE:/Tools/$releasever/
gpgcheck=1
gpgkey=https://download.opensuse.org/repositories/openSUSE:/Tools/$releasever/repodata/repomd.xml.key
pontifex2 (download.o.o):/etc/zypp/repos.d #
Updated by lkocman over 1 year ago
- % Done changed from 0 to 100
pontifex2 (download.o.o):/etc/zypp/repos.d # zypper in openSUSE-release-tools-publish-distro
New repository or package signing key received:
Repository: openSUSE.org tools
Key Fingerprint: FCAD AFC8 1273 B9E7 F184 F2B0 8266 59A9 013E 5B65
Key Name: openSUSE:Tools OBS Project <openSUSE:Tools@build.opensuse.org>
Key Algorithm: RSA 2048
Key Created: Mon Dec 7 10:26:44 2020
Key Expires: Wed Feb 15 10:26:44 2023
Rpm Name: gpg-pubkey-013e5b65-5fce0364
Note: Signing data enables the recipient to verify that no modifications occurred after the data
were signed. Accepting data with no, wrong or unknown signature can lead to a corrupted system
and in extreme cases even to a system compromise.
Note: A GPG pubkey is clearly identified by its fingerprint. Do not rely on the key's name. If
you are not sure whether the presented key is authentic, ask the repository provider or check
their web site. Many providers maintain a web page showing the fingerprints of the GPG keys they
are using.
Do you want to reject the key, trust temporarily, or trust always? [r/t/a/?] (r): a
Building repository 'openSUSE.org tools' cache ....................................................................................................................[done]
Retrieving repository 'Update repository with debuginfo for updates from SUSE Linux Enterprise 15' metadata .......................................................[done]
Building repository 'Update repository with debuginfo for updates from SUSE Linux Enterprise 15' cache ............................................................[done]
Retrieving repository 'Update repository with updates from SUSE Linux Enterprise 15' metadata .....................................................................[done]
Building repository 'Update repository with updates from SUSE Linux Enterprise 15' cache ..........................................................................[done]
Retrieving repository 'repo-update-oss' metadata ..................................................................................................................[done]
Building repository 'repo-update-oss' cache .......................................................................................................................[done]
Loading repository data...
Warning: Repository 'repo-debug-update' appears to be outdated. Consider using a different mirror or server.
Reading installed packages...
Resolving package dependencies...
The following NEW package is going to be installed:
openSUSE-release-tools-publish-distro
1 new package to install.
Overall download size: 241.0 KiB. Already cached: 0 B. No additional space will be used or freed after the operation.
Continue? [y/n/v/...? shows all options] (y): y
Retrieving package openSUSE-release-tools-publish-distro-20220823.34659a46-150400.1.1.noarch (1/1), 241.0 KiB ( 0 B unpacked)
Retrieving: openSUSE-release-tools-publish-distro-20220823.34659a46-150400.1.1.noarch.rpm .........................................................................[done]
Checking for file conflicts: ......................................................................................................................................[done]
(1/1) Installing: openSUSE-release-tools-publish-distro-20220823.34659a46-150400.1.1.noarch .......................................................................[done]
pontifex2 (download.o.o):/etc/zypp/repos.d #
Updated by lkocman over 1 year ago
local commit in: /home/mirror/bin
commit 10a021788e32348824f4e815182d57dd1ed57c68 (HEAD -> master)
Author: opensuse mirror <mirror@pontifex2.infra.opensuse.org>
Date: Fri Aug 26 13:30:49 2022 +0000
Use osrt-publish_distro from /usr/bin
diff --git a/bin/cleanup_factory_leap b/bin/cleanup_factory_leap
index a72af33..e14c600 100755
--- a/bin/cleanup_factory_leap
+++ b/bin/cleanup_factory_leap
@@ -1,4 +1,4 @@
#!/bin/bash
# cleanup both Leap and Factory in the same script to share lock file
withlock -q /home/mirror/var/run/withlock/LOCK-cleanup ~/bin/cleanup_factory
-withlock -q /home/mirror/var/run/withlock/LOCK-cleanup ~/openSUSE-release-tools/publish_distro --cleanup ~/openSUSE-release-tools/publish_distro_conf/publish_leap1522.config
+withlock -q /home/mirror/var/run/withlock/LOCK-cleanup /usr/bin/osrt-publish_distro --cleanup ~/openSUSE-release-tools/publish_distro_conf/publish_leap152.config
diff --git a/bin/publish_factory_leap b/bin/publish_factory_leap
index 1351629..4e6fc33 100755
--- a/bin/publish_factory_leap
+++ b/bin/publish_factory_leap
@@ -2,11 +2,7 @@
# publish both Leap and Factory in the same script to share lock file
withlock -q /home/mirror/var/run/withlock/LOCK-publish ~/bin/publish_factory
-# TODO set PUBLISH_DISTRO to /usr/bin/publish_distro once
-# https://github.com/openSUSE/openSUSE-release-tools/commit/a79aecee3d3d8c7125de35602a194691f42e63c8`
-# was deployed as rpm
-
-PUBLISH_DISTRO="~/openSUSE-release-tools/publish_distro"
+PUBLISH_DISTRO="/usr/bin/osrt-publish_distro"
CONF_DIR="~/openSUSE-release-tools/publish_distro_conf"
### Micro 5.3
Updated by lkocman over 1 year ago
Please close the ticket, I don't have permissions to resolve it.
Thank you!
Updated by lkocman over 1 year ago
Testing my changes by copying lines from the ~/bin/publish_factory_leap
and all seems fine
mirror@pontifex2:~> export PUBLISH_DISTRO="/usr/bin/osrt-publish_distro"
mirror@pontifex2:~> export CONF_DIR="~/openSUSE-release-tools/publish_distro_conf"
mirror@pontifex2:~> withlock -q /home/mirror/var/run/withlock/LOCK-publish $PUBLISH_DISTRO $CONF_DIR/publish_leap-micro53.config
openSUSE-Leap-Micro-5.3-DVD-x86_64-Build13.1-Media.iso already published, skipping isos
nothing to do
Updated by cboltz over 1 year ago
- Tracker changed from communication to tickets
Updated by cboltz over 1 year ago
- Status changed from Workable to Resolved
Hmm, that's interesting. As long as the ticket was under "communication", I also couldn't close it. Moving it to "tickets" makes it close-able, therefore I'll close it as requested.
BTW: Your local commit looks somewhat scary (not the content, but the fact that you have a local commit). It might want to become a config file or an upstream commit ;-)