[opensuse-buildservice] No *.repo files in published repositories
Hi, I wonder, where the project.repo files are gone in a local OBS instance? Aren't they generated anymore? My obs is 2.10.7 on 15.1. Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tue, Jun 30, 2020 at 8:59 AM Hans-Peter Jansen
Hi,
I wonder, where the project.repo files are gone in a local OBS instance? Aren't they generated anymore?
My obs is 2.10.7 on 15.1.
At least for me, they've never been generated for private OBS instances, and I started on 2.6 and now on 2.10. -- 真実はいつも一つ!/ Always, there's only one truth! -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am Dienstag, 30. Juni 2020, 15:10:24 CEST schrieb Neal Gompa:
On Tue, Jun 30, 2020 at 8:59 AM Hans-Peter Jansen
wrote: Hi,
I wonder, where the project.repo files are gone in a local OBS instance? Aren't they generated anymore?
My obs is 2.10.7 on 15.1.
At least for me, they've never been generated for private OBS instances, and I started on 2.6 and now on 2.10.
I was under the impression, that they existed before. Let me rephrase the question: what's the easiest way to generate them correctly? Guess, it takes a publish hook. Probably somedoy did the work already, and want to share it? Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Jun 30 2020, Hans-Peter Jansen wrote:
I wonder, where the project.repo files are gone in a local OBS instance? Aren't they generated anymore?
Worksforme. Perhaps a configuration problem? Do you have a valid
On Tue, Jun 30, 2020 at 2:43 PM Andreas Schwab
On Jun 30 2020, Hans-Peter Jansen wrote:
I wonder, where the project.repo files are gone in a local OBS instance? Aren't they generated anymore?
Worksforme. Perhaps a configuration problem? Do you have a valid
in /configuration?
Say what? I didn't know that was a thing... -- 真実はいつも一つ!/ Always, there's only one truth! -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am Dienstag, 30. Juni 2020, 20:43:28 CEST schrieb Andreas Schwab:
On Jun 30 2020, Hans-Peter Jansen wrote:
I wonder, where the project.repo files are gone in a local OBS instance? Aren't they generated anymore?
Worksforme. Perhaps a configuration problem? Do you have a valid
in /configuration?
Well, there's no such gui item, but I found it in /srv/obs/configuration.xml~, while it was missing in /srv/obs/configuration.xml. Supplied that, rebooted OBS, called obs_admin --{re}publish-repository repo arch and forced a rebuild of a package (with osc wipebinaries in order to really trigger a repo update). Still missing. What am I missing? Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Mittwoch, 1. Juli 2020, 00:07:38 CEST wrote Hans-Peter Jansen:
Am Dienstag, 30. Juni 2020, 20:43:28 CEST schrieb Andreas Schwab:
On Jun 30 2020, Hans-Peter Jansen wrote:
I wonder, where the project.repo files are gone in a local OBS instance? Aren't they generated anymore?
Worksforme. Perhaps a configuration problem? Do you have a valid
in /configuration? Well, there's no such gui item, but I found it in /srv/obs/configuration.xml~, while it was missing in /srv/obs/configuration.xml. Supplied that, rebooted OBS, called obs_admin --{re}publish-repository repo arch and forced a rebuild of a package (with osc wipebinaries in order to really trigger a repo update).
Still missing. What am I missing?
there is no other condition, please check your publisher log. Or you need to add some debug code in bs_publish, but I can not really imagine that this gets skipped if you really have a download url configured. -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Mittwoch, 1. Juli 2020, 08:11:09 CEST wrote Adrian Schröter:
On Mittwoch, 1. Juli 2020, 00:07:38 CEST wrote Hans-Peter Jansen:
Am Dienstag, 30. Juni 2020, 20:43:28 CEST schrieb Andreas Schwab:
On Jun 30 2020, Hans-Peter Jansen wrote:
I wonder, where the project.repo files are gone in a local OBS instance? Aren't they generated anymore?
Worksforme. Perhaps a configuration problem? Do you have a valid
in /configuration? Well, there's no such gui item, but I found it in /srv/obs/configuration.xml~, while it was missing in /srv/obs/configuration.xml. Supplied that, rebooted OBS, called obs_admin --{re}publish-repository repo arch and forced a rebuild of a package (with osc wipebinaries in order to really trigger a repo update).
Still missing. What am I missing?
there is no other condition, please check your publisher log.
Or you need to add some debug code in bs_publish, but I can not really imagine that this gets skipped if you really have a download url configured.
ah, maybe you did not restart the publisher after adding the download url to configuration.xml? -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am 01.07.2020 um 08:11 schrieb Adrian Schröter:
ah, maybe you did not restart the publisher after adding the download url to configuration.xml?
He said he rebooted. I assume you need to edit the configuration through osc api and not directly, because the API might update the configuration from database on boot. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Mittwoch, 1. Juli 2020, 08:17:05 CEST wrote Stephan Kulow:
Am 01.07.2020 um 08:11 schrieb Adrian Schröter:
ah, maybe you did not restart the publisher after adding the download url to configuration.xml?
He said he rebooted. I assume you need to edit the configuration through osc api and not directly, because the API might update the configuration from database on boot.
the api is not relevant here if the entry exists in /srv/obs/configuration.xml, which is used by the publisher... -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
I think the root cause of this issue is one of the things I reported,
namely changing the Repotype: to something invalid may break the
publisher permanently,
even if set again to something correct. Solution is to recreate your project.
On Wed, Jul 1, 2020 at 9:17 AM Stephan Kulow
Am 01.07.2020 um 08:11 schrieb Adrian Schröter:
ah, maybe you did not restart the publisher after adding the download url to configuration.xml?
He said he rebooted. I assume you need to edit the configuration through osc api and not directly, because the API might update the configuration from database on boot.
Greetings, Stephan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am Mittwoch, 1. Juli 2020, 08:11:09 CEST schrieb Adrian Schröter:
On Mittwoch, 1. Juli 2020, 00:07:38 CEST wrote Hans-Peter Jansen:
Am Dienstag, 30. Juni 2020, 20:43:28 CEST schrieb Andreas Schwab:
On Jun 30 2020, Hans-Peter Jansen wrote:
I wonder, where the project.repo files are gone in a local OBS instance? Aren't they generated anymore?
Worksforme. Perhaps a configuration problem? Do you have a valid
in /configuration? Well, there's no such gui item, but I found it in /srv/obs/configuration.xml~, while it was missing in /srv/obs/configuration.xml. Supplied that, rebooted OBS, called obs_admin --{re}publish-repository repo arch and forced a rebuild of a package (with osc wipebinaries in order to really trigger a repo update).
Still missing. What am I missing?
there is no other condition, please check your publisher log.
Or you need to add some debug code in bs_publish, but I can not really imagine that this gets skipped if you really have a download url configured.
Some advances thanks to your hints: after reboot and wipe yesterday, today I noticed, that rebuild of wiped package kept hanging in signing state. Consequently, publishing wasn't triggered at all. And indeed, after restarting obssigner.service, the build finished and the repo was created correctly. :thumbs_up: Despite of this, some packages still keep sitting in signing state, most notably kernel-default (which have been in this state before the reboot already, IIRC). Unfortunately, I haven't found a cure for this. Tried `obs_admin -- {deep,force}-check-project` without change. osc wipe_binaries rebuild the successfully built packages again, but the one for TW is still signing. Disabling build for this package resulted in: State needs recalculations, former state was: The repository state is being calculated right now. Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Jul 01 2020, Hans-Peter Jansen wrote:
Despite of this, some packages still keep sitting in signing state, most notably kernel-default (which have been in this state before the reboot already, IIRC).
kernel-default is special because it needs the SSL certificate. Does the project have that? Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am Mittwoch, 1. Juli 2020, 11:55:31 CEST schrieb Andreas Schwab:
On Jul 01 2020, Hans-Peter Jansen wrote:
Despite of this, some packages still keep sitting in signing state, most notably kernel-default (which have been in this state before the reboot already, IIRC).
kernel-default is special because it needs the SSL certificate. Does the project have that?
Yes, both buttons in GPG Keys / SSL Certificate dialog are active. Finally, after disabling build for the stalled kernel-default package, waiting for it to disappear and enabling it again, it seems to be rebuilt now. Will know for sure in a couple of hours but leaving now 'til late this night.. Thanks, Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (6)
-
Adrian Schröter
-
Andreas Schwab
-
Damian Ivanov
-
Hans-Peter Jansen
-
Neal Gompa
-
Stephan Kulow