https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230379
--- Comment #11 from Kai ---
I can confirm now that multimedia/py-openlp builds also fine on:
10.4- and 11.1-RELEASE on amd64 + i386
But the port seems in a bad shape and that for quite a while:
> $ openlp.py
> Traceback (most recent cal
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230379
--- Comment #12 from Kurt Jaeger ---
(In reply to Kai from comment #11)
The update for openlp simmers in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211665
with no end in sight.
--
You are receiving this mail because:
You are on t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230414
--- Comment #2 from Sergey Akhmatov ---
(In reply to Kubilay Kocak from comment #1)
I see your point. But the approach to use certifi as a wrapper to "system"
trust store is not uncommon. E.g. OpenBSD and Debian is using it by default:
htt
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230414
Sergey Akhmatov changed:
What|Removed |Added
Attachment #195946|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230414
Kubilay Kocak changed:
What|Removed |Added
Flags|maintainer-feedback?(sergey |
|@akhmatov.ru)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211665
Kai changed:
What|Removed |Added
CC||freebsd_po...@k-worx.org
Attachment #195985|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230379
--- Comment #13 from Kai ---
(In reply to Kurt Jaeger from comment #12)
Thanks for the info. I wasn't aware about that PR until yet and I think there
should be an end in sight now.
I attached a patch for bug #211665 that might be committe
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230140
Kubilay Kocak changed:
What|Removed |Added
Keywords||needs-qa
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211665
--- Comment #20 from Kurt Jaeger ---
Testbuilds@work
--
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-python@freebsd.org mailing list
https://lists.freebsd
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230140
--- Comment #9 from Marcelo Araujo ---
(In reply to Kubilay Kocak from comment #8)
I would not mind at all, if you have a patch under the way. you can update
maintainership to python@, otherwise I don't see a reason to do that prior a
patc
10 matches
Mail list logo