Miro Hrončok wrote:
> Anyway, I've closed NEW bugs with successful builds after the mass
> rebuild.
Can you please post an updated list with that done?
Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an e
Charalampos Stratakis wrote:
>> From: "Vít Ondruch"
>> 1) Apparently, there is some work which needs to be done on the
>> toolchain. Applying workarounds just hides the issues and we won't move
>> forward ever.
>
> I think it's more reasonable to do a small SPEC change in Python to
> achieve a 27
On Thu, 2019-11-07 at 21:25 +0100, Nicolas Mailhot via devel wrote:
> Le jeudi 07 novembre 2019 à 18:32 +0100, Sheogorath via devel a écrit
> :
> > The talk is right on many points, but I think it dismisses the most
> > essential point DoH does right: DNS is a decision of the device
> > owner.
>
>
On 08. 11. 19 20:40, Fabio Valentini wrote:
(Side note: I wouldn't even have objected to this being a
Self-Contained Change, since it basically only affects one package -
albeit an important one (python3)
Doing this as a system wide change was my decision, Harris (Charalampos) wanted
to do thi
On 08. 11. 19 23:13, John M. Harris Jr wrote:
What about packages that are Python 2 and have no interest to move to Python
3? How do we keep these?
By getting the FESCo exception.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailin
On 08. 11. 19 20:29, David Kaufmann wrote:
Remember to set the bugzilla to ASSIGNED when you actually work towards
fixing the build failure.
Is this meant to be done by the maintainer only may I do that, if I
intend to get the package to a fixed state?
If you do set the bugzilla to ASSIGNED,
On Friday, November 8, 2019 3:20:33 PM MST Daniel Walsh wrote:
> On 11/8/19 5:16 PM, John M. Harris Jr wrote:
>
> > On Tuesday, November 5, 2019 12:09:55 PM MST Martin Kolman wrote:
> >
> >> On Tue, 2019-11-05 at 19:41 +0100, Kevin Kofler wrote:
> >>
> >>
> >>
> Python 3 traditionally in Fed
On 11/8/19 5:16 PM, John M. Harris Jr wrote:
> On Tuesday, November 5, 2019 12:09:55 PM MST Martin Kolman wrote:
>> On Tue, 2019-11-05 at 19:41 +0100, Kevin Kofler wrote:
>>
Python 3 traditionally in Fedora was built with a shared library
libpython3.?.so and the final binary was dynamical
On Wednesday, November 6, 2019 9:06:33 PM MST Kevin Kofler wrote:
> Pierre-Yves Chibon wrote:
>
> > Symbiotic is, I think, the best way to describe the Red Hat/Fedora
> > relationship.
>
>
> Well, a symbiosis has to go both ways. In this case, I unfortunately get the
> feeling that this feature
On Tuesday, November 5, 2019 12:09:55 PM MST Martin Kolman wrote:
> On Tue, 2019-11-05 at 19:41 +0100, Kevin Kofler wrote:
>
> > > Python 3 traditionally in Fedora was built with a shared library
> > > libpython3.?.so and the final binary was dynamically linked against
> > > that shared library. T
On Tuesday, October 29, 2019 8:24:02 AM MST Miro Hrončok wrote:
> Dear maintainers,
> here is a list of packages that (transitively, at build or run time) require
>
Python 2 and have not yet got a FESCo exception to do so.
> If you were bcced on this e-mail, it affects one or more of your package
On Wednesday, November 6, 2019 8:48:15 PM MST Kevin Kofler wrote:
> Josh Boyer wrote:
>
> > What you call unfair, I call open source winning in the industry.
> > Does it create an imbalance between funded vs. unfunded work? Yes.
> > That is the reality of the software landscape today though, and
On Fri, Nov 08, 2019 at 01:14:14PM +, Ankur Sinha wrote:
> On Fri, Nov 08, 2019 13:16:21 +0100, Miro Hrončok wrote:
> > zathura-cb
> > zathura-djvu
> > zathura-pdf-mupdf
> > zathura-pdf-poppler
> > zathura-ps
>
> These are zathura plug-ins, and will break the `zathura-plugins-all`
> package th
Hi everybody,
Following the policy for non-responsive package maintainers [0], I'm
asking here if anybody knows how to contact dwalluck. David, if you're
reading this, and are still interested in maintaining hamcrest, please
respond.
His one package (hamcrest) is pretty outdated, and this is star
Hi everybody,
Following the policy for non-responsive package maintainers [0], I'm
asking here if anybody knows how to contact weli. Weinan, if you're
still interested in maintaining your packages, please respond.
Some of his packages are broken on fedora 31+ due to retired Java
dependencies, and
Hi,
(repost as I forgot to cc Eric)
I'm trying to contact Eric Smith (FAS: brohaha).
I have started the nonresponsive maintainer process because I'm trying to
update the WeasyPrint package which requires updating/fixing a few other
packages maintained by Eric.
This is mostly about:
- python-c
Hi everybody,
Following the policy for non-responsive package maintainers [0], I'm
asking here if anybody knows how to contact rfenkhuber. Roman, if
you're still interested in maintaining your packages, please respond.
Some of his packages are broken on fedora 31+ due to retired Java
dependencies
Hi everyone,
Welcome to the CPE team weekly project update mail!
Background:
The Community Platform Engineering group is the Red Hat team combining
IT and release engineering from Fedora and CentOS. Our goal is to keep
core servers and services running and maintained, build releases, and
othe
On 06/11/2019 21:15, Miro Hrončok wrote:
Package (co)maintainers
Status Change
WindowMaker orphan 0
weeks ago
WindowMaker-
Hi folks! I'm proposing we cancel the QA meeting for Monday. We got
through a lot of business the last couple of weeks and I don't have
anything significant for this week, criteria changes are moving ahead
nicely. There also won't be a blocker review meeting as we don't have
enough proposed blocker
On Fri, Nov 8, 2019 at 6:01 PM Charalampos Stratakis
wrote:
>
>
>
> - Original Message -
> > From: "Vít Ondruch"
> > Cc: devel@lists.fedoraproject.org
> > Sent: Friday, November 8, 2019 10:01:47 AM
> > Subject: Re: Fedora 32 System-Wide Change proposal: Build Python 3 to
> > statically l
On Fri, Nov 08, 2019 at 01:16:21PM +0100, Miro Hrončok wrote:
> vdirsyncer
I've contacted the maintainer via email, but if that does not work in
time I'd like to take up the issue.
> Remember to set the bugzilla to ASSIGNED when you actually work towards
> fixing the build failure.
Is this meant
Am 08.11.19 um 20:24 schrieb Ankur Sinha:
Sure, but what does one do here? Unset and reset the review flag? Can I
do that given that Petr reviewed and approved it already?
Yes. (both questions)
Felix
___
devel mailing list -- devel@lists.fedoraprojec
On Fri, Nov 08, 2019 19:15:27 +0100, J. Scheurich wrote:
> > Would anyone like to swap reviews please? I'd like to vimiv-qt reviewed:
> > https://bugzilla.redhat.com/show_bug.cgi?id=1770278
> I could review it in exchange of a review of vcglib:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=16779
Would anyone like to swap reviews please? I'd like to vimiv-qt reviewed:
https://bugzilla.redhat.com/show_bug.cgi?id=1770278
I could review it in exchange of a review of vcglib:
https://bugzilla.redhat.com/show_bug.cgi?id=1677989
This has been already reviewed, but the review is too old to be u
On 08. 11. 19 17:15, Miro Hrončok wrote:
On 08. 11. 19 16:04, Vitaly Zaitsev via devel wrote:
On 08.11.2019 13:16, Miro Hrončok wrote:
kf5-baloo
kf5-frameworkintegration
kf5-kactivities
kf5-kactivities-stats
kf5-kbookmarks
kf5-kcmutils
kf5-kconfigwidgets
kf5-kdeclarative
kf5-kded
kf5-kdelibs4s
On Fri, Nov 8, 2019 at 11:54 AM wrote:
>
> I agree with you in general but I don't like the `brief` wording here.
> What that means exactly?
> I would rather go with specifying a strong freeze. Meaning that the
> freeze will continue until compose is available.
>
By "brief" I mean "only as long as
- Original Message -
> From: "Vít Ondruch"
> Cc: devel@lists.fedoraproject.org
> Sent: Friday, November 8, 2019 10:01:47 AM
> Subject: Re: Fedora 32 System-Wide Change proposal: Build Python 3 to
> statically link with libpython3.8.a for better
> performance
>
>
> Dne 07. 11. 19 v 23:
On Fri, Nov 8, 2019 at 1:17 PM Miro Hrončok wrote:
> python-pyopencl
Fixed, FTBFS bug closed: https://bugzilla.redhat.com/show_bug.cgi?id=1736526
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists
On Fri, 2019-11-08 at 07:20 -0800, Kevin Fenzi wrote:
> On Thu, Nov 07, 2019 at 08:43:44PM +0100, Miro Hrončok wrote:
> > On 07. 11. 19 18:35, Ben Cotton wrote:
> > > Here's the link to the Community Blog post that looks at the
> > > schedule options:
> > > https://communityblog.fedoraproject.org/a
On 08. 11. 19 16:04, Vitaly Zaitsev via devel wrote:
On 08.11.2019 13:16, Miro Hrončok wrote:
kf5-baloo
kf5-frameworkintegration
kf5-kactivities
kf5-kactivities-stats
kf5-kbookmarks
kf5-kcmutils
kf5-kconfigwidgets
kf5-kdeclarative
kf5-kded
kf5-kdelibs4support
kf5-kdesignerplugin
kf5-kdesu
kf5-k
Hello,
Would anyone like to swap reviews please? I'd like to vimiv-qt reviewed:
https://bugzilla.redhat.com/show_bug.cgi?id=1770278
It is an image viewer with Vim like key-bindings. It was recently
re-written in Qt. It obsoletes the vimiv package which was gtk based.
--
Thanks,
Regards,
Ankur S
On Thu, Nov 7, 2019 at 7:02 AM Petr Viktorin wrote:
> jsmith
>asterisk
> (→ PY2)
> asterisk-* (→ asterisk → PY2)
>
Asterisk has very few dependencies on Python (just some contributed scripts
for use in debugging reference counters in the code, if I recall
correctly). That being sa
- Original Message -
> From: "Vitaly Zaitsev via devel"
> To: devel@lists.fedoraproject.org
> Cc: "Vitaly Zaitsev"
> Sent: Friday, November 8, 2019 10:04:57 AM
> Subject: Re: Will orphan packages with NEW F31FTBFS bugs tomorrow
>
> On 08.11.2019 13:16, Miro Hrončok wrote:
>
~snip~
>
On Thu, Nov 07, 2019 at 08:43:44PM +0100, Miro Hrončok wrote:
> On 07. 11. 19 18:35, Ben Cotton wrote:
> > Here's the link to the Community Blog post that looks at the schedule
> > options:
> > https://communityblog.fedoraproject.org/accommodating-flock-in-the-release-schedule/
>
> From the post:
On 08.11.2019 13:16, Miro Hrončok wrote:
> kf5-baloo
> kf5-frameworkintegration
> kf5-kactivities
> kf5-kactivities-stats
> kf5-kbookmarks
> kf5-kcmutils
> kf5-kconfigwidgets
> kf5-kdeclarative
> kf5-kded
> kf5-kdelibs4support
> kf5-kdesignerplugin
> kf5-kdesu
> kf5-kdewebkit
> kf5-kemoticons
> kf
I am looking to get python-rsa and python-ruamel-yaml built for EPEL-8
so I can finish building python-kubernetes and python-openshift for
EPEL-8. I've managed to get in contact with maintainers for most of the
dependencies and builds are completed, but so far with these two I have
been unable.
On Fri, Nov 08, 2019 13:16:21 +0100, Miro Hrončok wrote:
> zathura-cb
> zathura-djvu
> zathura-pdf-mupdf
> zathura-pdf-poppler
> zathura-ps
These are zathura plug-ins, and will break the `zathura-plugins-all`
package that requires them:
https://src.fedoraproject.org/rpms/zathura/blob/master/f/zat
According to the policy for packages that fail to build from source:
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
I plan to orphan packages with NEW Fedora 31 Fail To Build From Source bugzillas
tomorrow.
By doing so, we notify the dependent package
On Wed, 2019-11-06 at 17:10 -0500, Randy Barlow wrote:
> On Wed, 2019-11-06 at 21:32 +0100, Miro Hrončok wrote:
> > Is there any good way to get notified about this sort of problems in
> > timely manner prior to the update being pushed? This is currently not
> > optimal.
>
> I'm not familiar with
> OTOH I would like to not be bothered with the EPEL branch requests.
> There used to be a way to state that I don't mind people creating EPEL
> branches for my packages, because I personally don't care. I am aware
> about option to do so.
Yes, but when that happened the person requesting the bran
Eric: I suspect you are still interested in participating in Fedora and I
appreciate that. May I suggest that you give full "admin" co-maintainership
much faster. That would enable me an others to resolve many of the bugs. :-)
Felix
___
devel mailing li
On 11/7/19 5:24 PM, Peter Lemenkov wrote:
Hello All,
We have a set of macros for Erlang libraries rpm building. Some of
these macros evaliated before actual build (if I understand RPM build
process correctly) and their actual value depends on a type of a
package - arch-dependent or noarch.
Previ
On 08. 11. 19 8:38, Felix Schwarz wrote:
Hey,
thunderbird-enigmail was retired in rawhide after being orphaned for more than
6 weeks. However F30+F31 still have the RPM but it does not work at all due to
Thunderbird changes.
I'm not interested in taking over the master branch but I'd like to en
On 08. 11. 19 9:21, Felix Schwarz wrote:
Hi,
I'm trying to contact Eric Smith (FAS: brohaha).
I have started the nonresponsive maintainer process because I'm trying to
update the WeasyPrint package which requires updating/fixing a few other
packages maintained by Eric.
This is mostly about:
Hi
34 year old Swedish national here.
I have just filed a review request for an nts client that some friends of
mine have made.
https://bugzilla.redhat.com/show_bug.cgi?id=1770147
I'm hoping to do my best to become a Fedora package maintainer, or at least
experience the review process.
For thi
On 11/8/19 12:37 AM, Tom Hughes wrote:
On 08/11/2019 07:38, Felix Schwarz wrote:
(Obviously I'm not too keen on applying the whole un-retirement
process which
involves a potentially very long package review.)
No it doesn't - that package has only been retired for 22 days and a
review is only
I think that the basic problem is that the "broken dependencies" emails
are not sent anymore even for Rawhide. This is big loss.
Vít
Dne 06. 11. 19 v 21:32 Miro Hrončok napsal(a):
> Hello,
>
> it repeatedly happened to me that I'm notified by Koschei that dozens
> of my packages suddenly fail t
OTOH I would like to not be bothered with the EPEL branch requests.
There used to be a way to state that I don't mind people creating EPEL
branches for my packages, because I personally don't care. I am aware
about option to do so.
Vít
Dne 07. 11. 19 v 11:12 Peter Robinson napsal(a):
> Hi,
>
>
Orion Poplawski wrote:
> I find the global exclusion of packages built but not shipped in an
> enabled module baffling and makes it very hard to provide
> updates/alternatives to those packages.
[snip]
> Beyond the horrible UX above, this seems so counter to the idea that we
> are building a platfo
Dne 07. 11. 19 v 23:08 Florian Weimer napsal(a):
> * Vít Ondruch:
>
>> Dne 07. 11. 19 v 16:05 Tom Hughes napsal(a):
>>> On 07/11/2019 14:59, Victor Stinner wrote:
>>>
I cannot explain why PLT is needed when a libpython function calls a
libpython function.
>>> Because an exported symbol i
On 08/11/2019 07:38, Felix Schwarz wrote:
(Obviously I'm not too keen on applying the whole un-retirement process which
involves a potentially very long package review.)
No it doesn't - that package has only been retired for 22 days and a
review is only needed if it has been more than 8 weeks:
Hi,
I'm trying to contact Eric Smith (FAS: brohaha).
I have started the nonresponsive maintainer process because I'm trying to
update the WeasyPrint package which requires updating/fixing a few other
packages maintained by Eric.
This is mostly about:
- python-cairocffi
- python-pyphen
Bugzil
53 matches
Mail list logo
