[packman] mingw32 packages in Multimedia
joerg.lorenzen at ki.tng.de
Fri May 23 00:06:31 CEST 2014
I know that publishing sometimes is really slow when
there are a lot of build activities on the servers.
But e.g. package kid3 was updated to new version 3.1 24 days ago
and x86_64 binaries for openSUSE 13.1 were published today first time.
This is a really long time for publishing, I hope you're right that
mingw-endless-loops will stop with new obs version.
Am 22.05.2014 22:06, schrieb Stefan Botter:
> Hi JÃ¶rg,
> On Tue, 20 May 2014 21:15:49 +0200
> JÃ¶rg Lorenzen <joerg.lorenzen at ki.tng.de> wrote:
>> I've a question about packages mingw32-cross-binutils,
>> mingw32-cross-gcc, mingw32-filesystem, mingw32-headers and
>> mingw32-runtime. Why are they located in project Multimedia?
> I don't know, but they are there for several months now, and I am sure,
> Pascal put them there on purpose.
>> Since days they prevent publishing of all current builds e.g. for
>> opensuse 13.1,
>> because their build status hangs in a loop (scheduled -> finished ->
>> succeeded -> blocked -> scheduled ...).
>> I don't exactly know if I'm right, but I think puplishing won't be
>> done as long the repository build status is "build jobs exists".
>> These loops are repeated within a few minutes, may be because these
>> packages are aggregates
>> of repository "openSUSE.org:windows:mingw:win32".
> I saw these, too, but nevertheless Multimedia/13.1 has been published in
> the past days (May 19th and 21st), and I am sure the publishing is slow
> due to our limited build power and fast incoming upstream updates. I do
> not know, how the aggregates work, but if anyone is willing to dig in
> deeper, please feel free to ask on the buildservice mailing list.
> I will try to update PMBS to the latest obs 2.5.3 during the next few
> days, perhaps a full restart resolves the mingw-endless-loop.
> Packman mailing list
> Packman at links2linux.de
More information about the Packman