Community OBS - Refurbished and re-floated

This is great news, looking forward to taking advantage of it.

2 Likes

Thanks ol - that’s much appreciated

2 Likes

OBS update: I did a lot of OS upgrades (about 48!) over the weekend and then updated the OBS software. After some struggles with DB migrations and importing SFOS things are looking good. I’ve still got to get the actual builders to work and that may happen later today - depends if I have the right kind of sacrificial animal I guess. Hmmm. I wonder why my cats are hiding?

Oh logins are mainly disabled but I need to enable them from time to time to do work. Please don’t try use the system until I announce it is good to go as it makes watching the logs and debugging a bit harder - thanks

6 Likes

While i don’t have experience in SW i can say a thing or two about the correct way of sacrificing an animal. Felines don’t work. You need a pig or cow. Parts of it also work. Also you will need some charcoal and a grill. Preparation (marinades rubbings etc) doesn’t matter much. You can do as you please. The only thing that needs to be done is the smoke of the animal burning on the grill to reach the sky.

After consuming the animal -with some beer or wine- everything will work as it should.

6 Likes

Great news. If it matters to the guys above who actually write the hard apps, it matters to me!

https://build.sailfishos.org/ is running again :partying_face:

Older SFOS releases aren’t yet available but 4.0.1.48 is there … with aarch64 :partying_face:

We also have a ‘Chum’ repository which was intended to be a place for developers to release apps for the community to install from. (For those of you who remember maemo-extras and maemo-extras-testing)

The intention is that apps built on the OBS can also be built in Chum and users just add the one repo to be able to install any of the apps.

11 Likes

cool. 3.4 planned? I’m still on unsupported hardware… and we ask you if we need credentials?

yes, I need to figure out how but I’m sure I can get the old versions up eventually.

For access you need a merproject bugzilla account and just ask me for that via irc msg or pm on here.
I need an email and the account name you’d like to use.

But signing up will not be opened, will it? I suppose there’s no motivation in doing so.

You mean different sign up methods apart from pinging @lbt?

Oh, I can ping lbt of course :slight_smile:

Signup is still open and hasn’t changed for the last several years … I’m just a one-man captcha machine!!! :rofl:

(We were hoping to merge with sailfishos logins but that idea has been shelved)

3 Likes

PSA: 4.1.0.24 is now operational on the OBS. Please let me know of any issues :slight_smile:

6 Likes

How do we get an account for OBS for use in SailfishOS’ OBS?

Assuming we go through OpenSUSE’s Portal?

No. msg me with the username you want and an email and then you use the old Mer bugzilla to setup a password
Username is 2-20 characters long and only use A-Z a-z 0-9 and _

1 Like

Is there any reading about how to use sailfish OBS other than http://openbuildservice.org/help/manuals/ ?

(For example “Click the Repositories tab, then the Add from a Distribution link” is not present and I don’t know how to add a sailfishos release to a build. Plain “Add repository” only lists a “SailfishOS latest” which resolves to sailfish_latest_armv7hl.)

1 Like

I will put somethng together :slight_smile:

If you want to explore look here: Show home:lbt:apps / harbour-dice - SailfishOS Open Build Service

You’ll need a git repo that contains an rpm/ dir and your source. SDK stuff should work fine

Login and you will have a home project (link at the top right of the obs pages)

Edit the Advanced/Meta and add entries just like mine:
https://build.sailfishos.org/project/meta/home:lbt:apps

Go to the Users ‘tab’ and add ‘cibot’ as a maintainer so she’ll be able to update your src when a git tag happens.

Then create a package with your app name (there’s a link)

Create a file called _service locally and upload it to that package

I made one like this: (edit to make xml visible!)

<services>
  <service name="webhook">
  <param name="repourl">https://github.com/lbt/harbour-roll.git</param>
  <param name="branch">harbour-dice</param>
  </service>
</services>

Note that the OBS will update that file and add another section to it

That’s it.

Now if you add https://webhook.sailfishos.org/webhook/ to your github/lab webhook setup : https://github.com/lbt/harbour-roll/settings/hooks then whenever you tag on the branch in the webhook it will build

Click on repositories in the OBS and “go to download repository” and you’ll see your rpms and the repodata etc

Quick and dirty because I’m off to a BBQ so more later :smiley:

(harbour-dice is my pure openGL/physics dice simulator btw)

9 Likes

Well thank you very much @lbt - this is one of the fastest tracks I’ve read!
I assume the git repo and branch are in an XML, I’ll let you edit when you have time - enjoy the bbq!

(For the curious, I’ve managed to build a patchmanager version that should work with busybox and did not manage yet to build irremote)

One of the issues with updating an existing app from the obs repos that I’ve seen (other than no signature):

There is an update candidate for ‘patchmanager’ from vendor ‘meego’, while the current vendor is ‘’

1 Like

you spelt _service with a trailing s in the irremote package :slight_smile:

I never implemented signing for the community OBS but I think that may happen at some point.

The vendor change is deliberately part of libzypp (I think) and is intended to avoid accidentally switching packages if two repos provide it

1 Like