This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author neologix
Recipients Federico.Schwindt, neologix, nicm, rpointel, trent, vstinner
Date 2013-04-09.10:04:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1365501882.3.0.603967094028.issue12181@psf.upfronthosting.co.za>
In-reply-to
Content
>> If you could fill a separate issue for that, it would be great.
>
> I will but once this is committed. It'd make things easier.

No problem.

>> BTW, there are other OpenBSD-specific issues on the report, and we
>> don't have that many contributors (AFAICT noone): so if you can have a
>> look at them, that would be great (especially since our OpenBSD
>> buildbots have all been down for some time now).
>
> On this report or you mean in general?

typo: s/on the report/on the tracker.

> I don't mind looking if time permits.

That would be great (I try to fix NetBSD/OpenBSD issues myself, but since I don't have any installed machines with those OSes it's obviously much more complicated).

> Why are the OpenBSD buildbots down? Can we do anything about it?
> Having a buildbot slave up will definitely help here.

All the OpenBSD buildbots we have are provided by SnakeByte, and they're all offline: http://buildbot.python.org/all/builders
Maybe Trent has more info.
History
Date User Action Args
2013-04-09 10:04:42neologixsetrecipients: + neologix, vstinner, nicm, trent, rpointel, Federico.Schwindt
2013-04-09 10:04:42neologixsetmessageid: <1365501882.3.0.603967094028.issue12181@psf.upfronthosting.co.za>
2013-04-09 10:04:42neologixlinkissue12181 messages
2013-04-09 10:04:41neologixcreate