OBS Mailing List Summary, Week 47

by Nathan Cutler posted on 22nd Nov 2013

Here is a summary of activity on the opensuse-buildservice mailing list during week 47:

§§§

From November 13-16, the mailing list denizens helped Axel Theilmann iron out an issue with his prjconf which was causing macro-related errors at build-time.

§§§

Another user, Roger Oberholtzer, was bitten by the “branched project stalled” bug. The scenario: he enabled openSUSE 13.1 as a build target for his projects/packages in OBS, but the builds were not triggered.

  • Dimstar noted that this is because the architectures are not automatically added to the project metadata. Until the bug is fixed, the metadata can be edited manually – either using osc meta -e prj or via the web UI.
  • Hans-Peter Jansen posted exact instructions for adding the missing architectures.
  • Full “branched project stalled” thread: http://lists.opensuse.org/opensuse-buildservice/2013-11/msg00087.html

§§§

Kevin Cox wrote to the list about how he was unable to login to the OBS web UI.

§§§

Darin Perusich reported a bug where he created an SR (#207488) and the web UI says the SR is “Superseded by 207488” – he is wondering how an SR could be superseded by itself.

§§§

Matthew Drobnak posted about a problem he has been having with disabled packages not wanting to stay disabled. He tried various things, like unpublishing, deleting, disabling the build. But the package keeps coming back.

§§§

Andrey Borzenkov posted to the list concerning some rendering issues (with IE and an old version of Firefox) they’ve been having with the web UI. Coolo referred them to Github.

§§§

Matthew Drobnak wrote about an issue he was having when trying to build two or more versions of the same package, within a single project.

  • Andreas Schwab and Jan Engelhardt responded, noting that this is simply how the OBS works. A given package name can map only to a single RPM file. Or, said another way, the repository where packages are fetched from (see osc ls -b [project_name] doesn’t distinguish between different versions of the same package. It will carry the version that was built last.
  • The solution to the problem, then, is to either build the different versions in different projects, or use different names.
  • Read the whole thread: http://lists.opensuse.org/opensuse-buildservice/2013-11/msg00135.html

§§§

Greg Freemyer wrote that he has several packages in the security project that build fine against 13.1, but just started failing for tumbleweed. The build log shows failed build dependencies (missing libraries). This is puzzling: since the libraries in question are in 13.1, why would they be missing in tumbleweed?

§§§

Darin Perusich asked the list for advice on how to handle a situation in which he needs to make a Perl package available in server:monitoring. Normally he would just set up an _aggregate link, but this particular package has a large number of dependencies from devel:languages:perl that need to be available also.

  • Jan Engelhardt replied that the ideal way is to have all the dependencies in Factory. This obviates the need for crosslinking. But this only helps for the Factory builds. If one needs to build for multiple distributions, such a case probably calls for a distinct subproject in the Build Service.
  • Read the whole thread: http://lists.opensuse.org/opensuse-buildservice/2013-11/msg00044.html

§§§

Darin Perusich asked the list for advice on how to handle a situation in which he needs to make a Perl package available in server:monitoring. Normally he would just set up an _aggregate link, but this particular package has a large number of dependencies from devel:languages:perl that need to be available also.

  • Jan Engelhardt replied that the ideal way is to have all the dependencies in Factory. This obviates the need for crosslinking. But this only helps for the Factory builds. If one needs to build for multiple distributions, such a case probably calls for a distinct subproject in the Build Service.
  • Read the whole thread: http://lists.opensuse.org/opensuse-buildservice/2013-11/msg00044.html

§§§

Marguerite Su posted with an issue she was having with Hermes. In the ensuing discussion, it came to light that she was experiencing two separate issues: first, she was getting duplicate emails (this was due to her being subscribed twice: once as packager and another time as repo maintainer); second, emails were arriving with a time lag (hours or even days). The time lag was confirmed by other list members, and Coolo worked on it. At the time of this writing, he appears to be close to a solution.