September 2014 - openSUSE Build Service

[opensuse-buildservice] RFC: changes in request history
by Adrian Schröter 05 Sep '14

05 Sep '14

Hi, I do currently work on a re-implementation of the history logging of requests. Mainly to tackle the following things: * Currently history entries happen only on state changes, but not on other actions, like added or modified reviews, or changed (upcomming) priority change. * review state changes have no history at all yet * Last but not least, the new history system should be also usable with non-requests like project or package objects. However, I do currently plan some changes in the request xml layout due to this: An old entry looked like this: <history name="new" who="adrian" when="..."> <comment/> </history> The "name" attribute does not make sense always, since no all actions are state changes. Therefore I do plan to replace it with a <description> element instead. This will always contain some readable, but automatic generated text describing the action of the user. For example: <history who="adrian" when="..."> <description>Request got superseded by request 42</description> <comment>I do it always better in my second approach</comment> </history> The <comment> element will become optional, but continues to contain any user specified text. Also the review elements will get history elements in this style. Do you have any opinions about this change? adrian -- Adrian Schroeter email: adrian(a)suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] obs webui feature request: don't clear search field
by Matwey V. Kornilov 05 Sep '14

05 Sep '14

Hi, I have an feature request for OBS WebUI. Please, take a look to the typical project page: https://build.opensuse.org/project/show/openSUSE:Factory:ARM There we have two tabs: "Packages" and "Inherited packages" as well as "Search:" field to filter packages by name. The issue here that user input in search field doesn't survive at tabs switching. Could you please change current behavior to more intuitive one? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 4

[opensuse-buildservice] subscribe
by Juergen Paller 04 Sep '14

04 Sep '14

-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] autosubmits ignore current SRs?
by Greg Freemyer 02 Sep '14

02 Sep '14

I have a feeling the SR auto-submit process is making some double work for the factory review team. In particular I happen to have several SR to factory that are several days old. 4 of them just got a auto-submit from the devel project to factory that caused the outstanding SR to be superseeded. I'm pretty sure there was no actual difference between the outstanding SR and the newly generated SR. As an example: https://build.opensuse.org/request/show/246622 Note that it was created 6 days ago and that the last file change in the project was 7 days ago. Therefore it should have been a submit of the latest and greatest. On the other hand a new autosubmit just superseeded it: https://build.opensuse.org/request/show/247268 As best as I can tell there is no difference between SR 246622 and 247268, yet I assume any ongoing review activity related to the 6 day old SR was lost. fyi: This doesn't impact me, so if this is not causing the factory review team extra work, then there is not a bug from my perspective. Greg -- Greg Freemyer -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] Branching glibc breaks glibc.i686 link
by Andreas Schwab 01 Sep '14

01 Sep '14

Branching the glibc package doesn't properly create the glibc.i686 link, dropping the <patches> part: <patches> <topadd> ExclusiveArch: i586 i686 BuildArch: i686 %{expand:%%global optflags %(echo "%optflags"|sed -e s/i586/i686/) -march=i686 -mtune=generic} </topadd> </patches> This also happens when a maintenance request is accepted, see openSUSE:Maintenance:2977 for example (the source project had the corrected links). Andreas. -- Andreas Schwab, SUSE Labs, schwab(a)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(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] use kiwi result as build-requirement
by Matwey V. Kornilov 01 Sep '14

01 Sep '14

Hi, Is it possible to use kiwi build products as build-requirements for rpm builds? I would like to do the following: get rootfs tar.gz of some kiwi build, repack it into /var/lib/container/myservice and utilize systemd-nspawn. So, effectively, I will get an rpm with the service which I will be able to install, enable and run as following: zypper in myservice systemctl enable systemd-nspawn(a)myservice.service systemctl start systemd-nspawn(a)myservice.service This is only an idea for private use, of course, I am not going to do that with real services. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1