February 2018 - openSUSE Build Service

[opensuse-buildservice] Re: [packman] Advance notice of PMBS shutdown from next Weekend on
by Mathias Homann 06 Feb '18

06 Feb '18

Forwarded from the packman mailling list: Am Montag, 22. Januar 2018, 09:04:08 CET schrieb Stefan Botter: > Hi all, > > due to new compliance regulations in our data center I am not allowed > to run systems there without available security updates. > As openSUSE Leap 42.2's support period ends on Jan 26th 2018, and there > is no published openSUSE Leap 42.3 repository for OBS' stable branch, I > cannot update PMBS to openSUSE 42.3, and am thus unable to fulfill the > compliance criteria. > > I will have to shut down PMBS until either > - I find the time and a machine to host PMBS outside of our data > center, or > - a stable branch is published for a supported version of Leap. > > I am sorry for the inconvenience caused, > greetings, > > Stefan so... can we please have a stable repo for 42.3 ASAP? cheers MH -- Mathias Homann Senior Systems Engineer, IT Consultant. IT Trainer Mathias.Homann(a)openSUSE.org http://www.tuxonline.tech gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 6

[opensuse-buildservice] Making a "secretly-built" package be available for buildroots
by Neal Gompa 05 Feb '18

05 Feb '18

Hey, I'm trying to have a package set up so that its sources and binaries + buildlogs are hidden (and isn't published) to be pulled in as a dependency of another package in another project. However, when I set up the project with the secret package that way, it didn't work. Instead, I got unresolvable from packages that pulled a package that depended on the secret package in the secret project. The OBS web UI seems to know it's there. What's going on? I want to be able to have "baz" have sourceaccess and binary download access disabled, and it's in SecretProject, which is hidden. This is pulled in by MainProject's package "foo". Package "bar" depends on "foo" which depends on "baz". OBS says this is unresolvable. What am I supposed to do to make this work? -- 真実はいつも一つ！/ Always, there's only one truth! -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] Beta One of Open Build Service 2.9 Released
by Henne Vogelsang 04 Feb '18

04 Feb '18

People of the Builds! We are happy to announce the first beta release of the upcoming Open Build Service (OBS) version 2.9. There have been many changes since our last major release. Highlights include the Studio Express features, an improved workflow for producing appliance images in OBS. A message bus, supported by RabbitMQ, to help you connect your own tools to what is happening inside the OBS. And a much improved notifications system to keep up to date with OBS. More information ---------------- If you are longing for a deeper look into all the changes this update brings check out the detailed 2.9 Release Notes https://github.com/openSUSE/open-build-service/blob/2.9/ReleaseNotes-2.9 It is also recommended to read these before updating your OBS instance! Try OBS 2.9 Beta One -------------------- 2.9 Beta One is deployed on our reference server you can try it there: https://build.opensuse.org Install 2.9 Beta One -------------------- Please read our setup instructions https://github.com/openSUSE/open-build-service/blob/2.9/README.md#installat… or better yet, use our appliance http://download.opensuse.org/repositories/OBS:/Server:/2.9/images/ Update to 2.9 Beta One ---------------------- We do not recommend this for critical production instances but if you already have a running OBS installation and want to update it to this beta, please read also the README.UPDATERS https://github.com/openSUSE/open-build-service/blob/2.9/dist/README.UPDATERS file about the necessary steps. OBS Appliance users who have setup their LVM http://openbuildservice.org/download/#appliance_config can just replace their appliance image without data loss. The migration will happen automatically. OBS 2.9 Final ------------- We will continue to work on the final release of 2.9 and expect it to be released in the near future. We hope you like this beta and are looking forward to your feedback to it, here on this list, on IRC or by bug reports in github. 💚 Your Open Build Service Team -- Henne Vogelsang http://www.opensuse.org Everybody has a plan, until they get hit. - Mike Tyson -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 6

[opensuse-buildservice] Change Origin in Debian/Ubuntu packages
by Ralf Becker 03 Feb '18

03 Feb '18

To enable automatic update in Debian/Ubuntu the Origin of a package must be specified. Currently the origin of packages created with our private OBS (2.8.2) instance is always: obs://build.opensuse.org/<project-name>/<repo> Using that URL-stylite Origin is not possible for unattended updates. As a workaround you can use a regular expression like "*<project-name>*". Is there a way to override the default Origin in OBS? Ralf -- Ralf Becker EGroupware GmbH [www.egroupware.org] Handelsregister HRB Kaiserslautern 3587 Geschäftsführer Birgit und Ralf Becker Leibnizstr. 17, 67663 Kaiserslautern, Germany Telefon +49 631 31657-0

2 1