[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opensuse-buildservice
Subject:    Re: [opensuse-buildservice] Repository publishing broken on b.o.o ?
From:       Julio Gonzalez <jgonzalez () suse ! com>
Date:       2019-08-02 17:52:13
Message-ID: 3977673.ppYJZVZO35 () juliogonzalez ! hispa-net ! com
[Download RAW message or body]

Hi Fritz,

I finally managed to get the problem solved for my Ubuntu repositories, so I 
guess your problem could be the same.

In my case, I was trying to publish a rebuild of a package, but sadly the 
Debian packaged we had, didn't increase the build number at the control files.

By having a look at https://download.opensuse.org/repositories/home:/felfert/
Fedora_29/x86_64/ehs-devel-1.5.1-173.fc29.x86_64.rpm

I think it's the same. Is "-173" coming from your SPEC and you are trying to 
publish a rebuild?

If that's the case, I have to be honest (if mls is reading me): I didn't 
understand 100% the explanation of why it's happening (I should stop 
multitasking one day), but I understood that the solution is increasing the 
release number.

In your case that could be fixed by adding a suffix to -173 that gets 
increased each time the package rebuilds.

If I am not wrong, adding this to your Project Config:

Release: <SPEC_REL>.<B_CNT> 

And launching a rebuild of the project

osc rebuild -a <YOUR_PROJECT>

Should fix your issues.

I can't find anything about this a the official doc:
https://openbuildservice.org/help/manuals/obs-user-guide/
cha.obs.prjconfig.html

But I know for a fact that you can change the Release like that, as we use 
something similar at Uyuni (for RPMs), and I had a look at this issue:
https://github.com/openSUSE/open-build-service/issues/536

Let us know if your problem gets fixed.

On jueves, 1 de agosto de 2019 16:56:29 (CEST) Fritz Elfert wrote:
> On 01.08.19 15:14, Julio Gonzalez wrote:
> > And it seems it's happening again, now with another package:
> > 
> > 15:11:57 ERROR: Download failed:
> > https://download.opensuse.org/repositories/
> > systemsmanagement:/Uyuni:/Master:/Ubuntu1604-Uyuni-Client-Tools/xUbuntu_1
> > 6.04/ all/salt-ssh_2019.2.0+ds-1_all.deb - Target file isn't valid.
> > Checksum should be
> > b119694c43a2f0a5cd0501772bfcd4b5ce7da5c4fdb6e5e3fcbd0a00296f7d4f
> > (sha256).. 15:11:57 2/7 : salt-ssh_2019.2.0+ds-1_all.deb (failed)
> > 
> > @Fritz, was it fixed in your case?
> 
> Nope. And here it starts with other packages too :-(
> The current mirror situation is quite desolate:
> 
> *None* of the suggested mirrors for my location (DE) has correct
> packages. The suggested mirrors for my location are:
> 
> ftp.gwdg.de
> ftp.lysator.liu.se
> provo-mirror.opensuse.org
> 
> To me, this smells like the master (staging?) has problems and cannot be
> reached by the mirrors, but of course, without having rsync access to
> that one I cannot be shure.
> 
> Apparently, *some* resync attempt has been made, because I see *old*
> binaries with a newer timestamp on the mirror though. Still, the newer
> binaries that should be there, are not.
> 
> Also:
> My ticket #54605 that I submitted 8 days ago to admin@opensuse.org is
> still untouched (nobody assigned, Done: 0%)
> 
> Frustrated
>  -Fritz


-- 
Julio González Gil
Release Engineer, SUSE Manager and Uyuni
jgonzalez@suse.com
["signature.asc" (application/pgp-signature)]
-- 
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org


[prev in list] [next in list] [prev in thread] [next in thread]