[opensuse-buildservice] Could this bug be the result of bad mirror handling?
Hi, myself and others have had strange random errors with home project's repositories. see: https://bugzilla.opensuse.org/show_bug.cgi?id=1112615 This has caused me lot's of frustration in bug fixing, in one case I couldn't understand why the reporter was still having problems with the fixed package until I discovered that the reporter wasn't getting the current package but an old one left behind after I had deleted and re branched said package. Thanks Dave P -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Hi there, On Sun, 06 Jan 2019, 12:01:30 +0100, Dave Plater wrote:
Hi, myself and others have had strange random errors with home project's repositories. see: https://bugzilla.opensuse.org/show_bug.cgi?id=1112615 This has caused me lot's of frustration in bug fixing, in one case I couldn't understand why the reporter was still having problems with the fixed package until I discovered that the reporter wasn't getting the current package but an old one left behind after I had deleted and re branched said package.
I read the referenced boo, and now I am not sure if what I see, "works as designed" or if there is a bug. Anyway, when thunderbird60 from Wolfgang Rosenauer's "mozilla" project didn't build for openSUSE_Leap_42.3, I branched it into my subproject home:manfred-h:mozilla and worked on it. When it finally built, I submitted it back to Wolfgang and disabled build and publish in my repo. However, there are still packages available at <http://download.opensuse.org/repositories/home:/manfred-h:/mozilla/openSUSE_Leap_42.3/x86_64/> which I don't know how to finally get rid of (i.e. deleted). And yes, there are no binaries available via osc: $ osc ls -b home:manfred-h:mozilla thunderbird60 openSUSE_Leap_42.3/x86_64 openSUSE_Leap_15.0/x86_64 FWIW, I already ran "osc wipebinaries" for my home project and its subprojects. What can I do to ensure that such packages get actually removed from doo and its mirrors?
Thanks Dave P
TIA, cheers. l8er manfred
On Jan 07 2019, Manfred Hollstein <mhollstein@t-online.de> wrote:
What can I do to ensure that such packages get actually removed from doo and its mirrors?
You need to enable publishing. Or remove the repository from the project. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "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
Hi Andreas, On Mon, 07 Jan 2019, 12:30:11 +0100, Andreas Schwab wrote:
On Jan 07 2019, Manfred Hollstein <mhollstein@t-online.de> wrote:
What can I do to ensure that such packages get actually removed from doo and its mirrors?
You need to enable publishing.
yeah, that would be logical. However, I only disabled publishing after appr. 2 days when disabling build did not result in removing the built binaries from download.opensuse.org, so to say as a last resort...
Or remove the repository from the project.
I'll try that as the next last resort ;) Thanks for your suggestions!
Andreas.
Cheers. l8er manfred
Moin, On Mon, 07 Jan 2019, 13:00:24 +0100, Manfred Hollstein wrote:
On Mon, 07 Jan 2019, 12:30:11 +0100, Andreas Schwab wrote:
Or remove the repository from the project.
I'll try that as the next last resort ;) Thanks for your suggestions!
Update: once I ran "osc wipebinaries --all ..." when all packages which I didn't want to be published got build-disabled (but publish-enabled!), everything seems to be in a consistent shape. This means all the unwanted binaries are gone now from doo. Final remark though: it doesn't happen _immediately_ for the mirror-out process to remove unwanted packages... apparently, as it took some hours before the status became consistent - better not to change anything within the infrastructure before then (such as enabling/disabling other repos, adding/removing packages etc.)... ;) Thanks to Andreas for the ultimate trigger ;)
Andreas.
Cheers. l8er manfred
Hi Manfred, Am 07.01.19 um 13:00 schrieb Manfred Hollstein:
Hi Andreas,
On Mon, 07 Jan 2019, 12:30:11 +0100, Andreas Schwab wrote:
On Jan 07 2019, Manfred Hollstein <mhollstein@t-online.de> wrote:
What can I do to ensure that such packages get actually removed from doo and its mirrors?
You need to enable publishing.
yeah, that would be logical. However, I only disabled publishing after appr. 2 days when disabling build did not result in removing the built binaries from download.opensuse.org, so to say as a last resort...
Or remove the repository from the project.
I'll try that as the next last resort ;) Thanks for your suggestions!
I'll summarize, in case someone will find this thread later in some search engine: 1. disable build 2. osc wipebinaries 3. wait for repo state "published" 4. disable publishing. I'm not sure if step 3 is strictly necessary, but it certainly does not harm (apart from wasting some time). Have fun, -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On 07/01/2019 13:11, Manfred Hollstein wrote:
What can I do to ensure that such packages get actually removed from doo and its mirrors?
A trick that worked with me in the past was use osc meta pkg -e and alter one comment then the package appears again and you can delete it. Dave -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (4)
-
Andreas Schwab -
Dave Plater -
Manfred Hollstein -
Stefan Seyfried