Re: rawhide build errors on i686

[Matthias Runge]

On 02/07/2023 17:51, Matthias Runge wrote:

Hi there

in one of my recent builds, I came across this error on i686 [1].

Transaction test succeeded.
Running transaction
warning: /etc/hosts created as /etc/hosts.rpmnew

Error unpacking rpm package shadow-utils-2:4.13-7.fc39.i686
error: unpacking of archive failed on file /usr/bin/newgidmap;64a19767: 
cpio: cap_set_file failed - Value too large for defined data type

error: shadow-utils-2:4.13-7.fc39.i686: install failed


I do believe this failure has nothing to do with my package build (some 
golang package). Who could debug this further, or is the issue already 
known?


The issue seems to be transient, [2] just passed, I found a related 
thread on the infrastructure list[3].



Matthias



Matthias

[1] 
https://kojipkgs.fedoraproject.org//work/tasks/7079/102847079/mock_output.log

[2] https://koji.fedoraproject.org/koji/taskinfo?taskID=102847771
[3] 
https://lists.fedoraproject.org/archives/list/infrastruct...@lists.fedoraproject.org/thread/HX7RPWZGULSWEHVQ4GBCZQNIZUCNLA7A/


--
Matthias Runge 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

rawhide build errors on i686

[Matthias Runge]

Hi there

in one of my recent builds, I came across this error on i686 [1].

Transaction test succeeded.
Running transaction
warning: /etc/hosts created as /etc/hosts.rpmnew

Error unpacking rpm package shadow-utils-2:4.13-7.fc39.i686
error: unpacking of archive failed on file /usr/bin/newgidmap;64a19767: 
cpio: cap_set_file failed - Value too large for defined data type

error: shadow-utils-2:4.13-7.fc39.i686: install failed


I do believe this failure has nothing to do with my package build (some 
golang package). Who could debug this further, or is the issue already 
known?


Matthias

[1] 
https://kojipkgs.fedoraproject.org//work/tasks/7079/102847079/mock_output.log

--
Matthias Runge 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: FontAwesome 6

[Matthias Runge]

On 31/10/2022 19:23, Jerry James wrote:

Hi all,




One hurdle is that the current fontawesome-fonts maintainer doesn't
seem to have time to work on the package:
https://bugzilla.redhat.com/show_bug.cgi?id=1857488#c9.  I'm willing
to help out with that, but would prefer to see somebody with more font
experience step into the main admin role.

Another hurdle is that you have to work a little to get the backwards
compatibility features for 4.x and 5.x.  It isn't just a drop-in
replacement.  I've started a COPR to work through the issues:
https://copr.fedorainfracloud.org/coprs/jjames/FontAwesome6/.  This
shows both the python-pydata-sphinx-theme update I mentioned at the
top, and a patch for cantata to use 6.x natively.

Packages that need work:
- cantata (see the COPR for a possible solution)
- freeipa
- ipsilon
- python-XStatic-Font-Awesome [1]




Footnotes:
[1] Is this package needed?  Nothing in Fedora seems to consume it.
It looks like it is just a bundled copy of the fonts, which also means
that its Requires on fontawesome-fonts and fontawesome-fonts-web are
wrong, since it contains the fonts.



Hi,

thank you for bringing this up!

As a former contributor to those packages, your assumption is correct. 
python-XStatic-Font-Awesome can go away; I'll sync with Radomir on that 
note.


If someone relies on fontawesome-fonts, they should step up. The 
question is, how to get out of this, since there were incompatible 
changes between major package releases. Three options:


- just update fontaweseome-fonts; that'll unblock folks who are waiting 
for the update; unfortunately packages may not be ready for 
fontawesome-6 and may have to be fixed (or removed)
- provide a compatibility package; that would require to touch more 
packages; ideally the versioned compatibility package would carry the 
old version; all packages requiring FA 4 would have to depend on the 
compat package

- ignore the issue and move on

Personally, I would prefer the first option. That being said, I don't 
have any spare time to work on this.


Matthias

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[EPEL-devel] Re: [CentOS-devel] [Messaging] RabbitMQ for EPEL 9

[Matthias Runge]

On 21/09/2022 12:49, Alfredo Moralejo Alonso wrote:



good question, and sorry to keep you waiting for this long time without
an answer. I changed roles in my job, leading to less and less time to
contribute. The messaging SIG did not attract the contributors I hoped
it would. I am looking for volunteers! Otherwise we should admit the
failure here and just close the SIG.


I'm sorry to contradict you but in the rabbitmq-server side of the SIG 
we have contributors taking care of updating rabbitmq server:


https://cbs.centos.org/koji/packageinfo?packageID=398 



You can simply:

# sudo dnf install -y centos-release-rabbitmq-38
#sudo dnf install -y rabbitmq-server

Best regards,



Thank you Alfredo. This is encouraging to hear! Thank you Peter for 
doing the build(s)!


Matthias
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[EPEL-devel] Re: [Messaging] RabbitMQ for EPEL 9

[Matthias Runge]

On 03/09/2022 20:32, Robby Callicotte via epel-devel wrote:

Hello all,

I recently stumbled onto this bugzilla issue[1].  It has gone a couple of
months without a response from the assignee.  I know that the stalled package
request procedures can be started now, but I also see that RabbitMQ was built
by the Messaging SIG in the past.  So... Where should this get routed?  Is the
messaging SIG still active?  I see some info[2] saying that it is, but the
lack of response leads me to think that it may not be.


Thanks!


[1]  https://bugzilla.redhat.com/show_bug.cgi?id=2105791
[2] https://wiki.centos.org/SpecialInterestGroup/Messaging



Hi,

good question, and sorry to keep you waiting for this long time without 
an answer. I changed roles in my job, leading to less and less time to 
contribute. The messaging SIG did not attract the contributors I hoped 
it would. I am looking for volunteers! Otherwise we should admit the 
failure here and just close the SIG.


Matthias
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: planning to orphan python-django (and a couple of dependent packages) + potentially more

[Matthias Runge]

On 06/07/2022 13:55, Ali Erdinc Koroglu wrote:

Hello, I can take the rest thank you.

FAS: aekoroglu



Thank you!

I did not hand all packages over, such as python-django-nose, or 
python-django-piston because they should already be retired, but it 
still looks somewhat existing in pkgdb. Upstreams were gone for a couple 
of years, like django-piston had approx. the last commit 9 years ago.



Matthias




On 06/07/2022 11:50, Simon de Vlieger wrote:
you may or may not know, I have been maintaining python-django for 
quite

some time in the past, some time as part of my job. My role changed and
I really can not dedicate Django the time it deserves. I am looking for
someone or persons willing to take

- python-django
- python-django-angular
- python-django-appconf
- python-django-authority
- python-django-compressor
- python-django-contact-form
- python-django-debug-toolbar
- python-django-haystack
- python-django-mptt
- python-django-nose
- python-django-notification
- python-django-pagination
- python-django-pipeline
- python-django-piston
- python-django-pyscss
- python-django-rest-framework
- python-django-reversion
- python-django-robots
- python-django-tables2
- python-django-tagging


I'm going to orphan the packages mid July. Ideally we'd find takers 
before?

If you are interested and able to maintain (any) of these packages,
please send me your FAS name and package(s) to maintain.
I don't know if I can apply as I am a relatively new maintainer but 
I'd like to

help out by taking over the following packages:

- python-django-robots
- python-django-pagination
- python-django-contact-form

My FAS username is: `supakeen`.


-
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki Business Identity Code: 
0357606 - 4 Domiciled in Helsinki

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/

List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: planning to orphan python-django (and a couple of dependent packages) + potentially more

[Matthias Runge]

On 06/07/2022 10:50, Simon de Vlieger wrote:



I don't know if I can apply as I am a relatively new maintainer but I'd like to
help out by taking over the following packages:

- python-django-robots
- python-django-pagination
- python-django-contact-form

My FAS username is: `supakeen`.


Hi Simon,

thank you for stepping up! I just handed these packages over.

Matthias
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: planning to orphan python-django (and a couple of dependent packages) + potentially more

[Matthias Runge]

On 19/04/2022 15:00, Matthias Runge wrote:

Hello there,



Re-iterating on this email, also including de...@lists.fp.o

you may or may not know, I have been maintaining python-django for quite 
some time in the past, some time as part of my job. My role changed and 
I really can not dedicate Django the time it deserves. I am looking for 
someone or persons willing to take


- python-django
- python-django-angular
- python-django-appconf
- python-django-authority
- python-django-compressor
- python-django-contact-form
- python-django-debug-toolbar
- python-django-haystack
- python-django-mptt
- python-django-nose
- python-django-notification
- python-django-pagination
- python-django-pipeline
- python-django-piston
- python-django-pyscss
- python-django-rest-framework
- python-django-reversion
- python-django-robots
- python-django-tables2
- python-django-tagging



I'm going to orphan the packages mid July. Ideally we'd find takers before?
If you are interested and able to maintain (any) of these packages, 
please send me your FAS name and package(s) to maintain.


Thank you,
Matthias
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: planning to orphan python-django (and a couple of dependent packages) + potentially more

[Matthias Runge]

On 19/04/2022 15:00, Matthias Runge wrote:

Hello there,



Re-iterating on this email, also including de...@lists.fp.o

you may or may not know, I have been maintaining python-django for quite 
some time in the past, some time as part of my job. My role changed and 
I really can not dedicate Django the time it deserves. I am looking for 
someone or persons willing to take


- python-django
- python-django-angular
- python-django-appconf
- python-django-authority
- python-django-compressor
- python-django-contact-form
- python-django-debug-toolbar
- python-django-haystack
- python-django-mptt
- python-django-nose
- python-django-notification
- python-django-pagination
- python-django-pipeline
- python-django-piston
- python-django-pyscss
- python-django-rest-framework
- python-django-reversion
- python-django-robots
- python-django-tables2
- python-django-tagging



I'm going to orphan the packages mid July. Ideally we'd find takers before?
If you are interested and able to maintain (any) of these packages, 
please send me your FAS name and package(s) to maintain.


Thank you,
Matthias
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

planning to orphan python-django (and a couple of dependent packages)

[Matthias Runge]

Hello there,

you may or may not know, I have been maintaining python-django for quite 
some time in the past, some time as part of my job. My role changed and 
I really can not dedicate Django the time it deserves. I am looking for 
someone or persons willing to take


- python-django
- python-django-angular
- python-django-appconf
- python-django-authority
- python-django-compressor
- python-django-contact-form
- python-django-debug-toolbar
- python-django-haystack
- python-django-mptt
- python-django-nose
- python-django-notification
- python-django-pagination
- python-django-pipeline
- python-django-piston
- python-django-pyscss
- python-django-rest-framework
- python-django-reversion
- python-django-robots
- python-django-tables2
- python-django-tagging


Matthias
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Non-responsive packagers: anoopcs, gtiwari, msehnout, sebix, vanessa_kris

[Matthias Runge]

> Am 20.01.2022 um 09:57 schrieb Pierre-Yves Chibon :
> 
> Good Morning Everyone,
> 
> The packagers listed here have been receiving a daily email asking them to
> either adjust their bugzilla or their FAS account so the email address in FAS
> matches an existing bugzilla account.
> 
> Having a bugzilla account is mandatory per:
> https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Create_a_Bugzilla_Account
> 
> 
> 
> - sebix contacted since December 4th
> 
> sebix is maintainer of rpms/lockfile-progs
> sebix has a bugzilla override on rpms/lockfile-progs
> sebix is maintainer of rpms/logcheck
> sebix has a bugzilla override on rpms/logcheck
> 
> 
> Thanks,
> 
> Pierre
> 

I have cc’d sebix to this email.

Sebastian, could you please take a look?

Thank you,
Matthias
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F36 Change: Django 4.0 (Self-Contained Change proposal)

[Matthias Runge]

On Wed, Jan 05, 2022 at 11:25:42AM -0500, Ben Cotton wrote:
> https://fedoraproject.org/wiki/Changes/Django4.0
> 
> == Summary ==
> Update Django to version 4.0.
> 
> == Owner ==
> * Name: [[User:mrunge| Matthias Runge]]
> * Email: mru...@redhat.com
> 
> 
> == Detailed Description ==
> 
> The Django project has regular releases about every 9 months. Django
> 4.0 is a major milestone, and this Change will
> bring the Fedora included version to the latest version.
> 
> The immediate step is to bump the python-django package to version
> 4.0. It is expected, that dependent packages will be
> updated as well, or retired, if they haven't seen an update for long time.

The pull request to bump the version is here [1].

In my understanding, there is no real (workable) alternative to the
update right now. If we'd delay it, the next bump will be to 4.1. If
a dependent package was not updated for 4.0, the step for the upgrade
to django-4.1 will be even bigger.

Matthias

[1] https://src.fedoraproject.org/rpms/python-django/pull-request/23
-- 
Matthias Runge 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Orphaned packages looking for new maintainers

[Matthias Runge]

On Wed, Jan 12, 2022 at 04:50:07PM -0800, Michel Alexandre Salim wrote:
> On Mon, Jan 10, 2022 at 06:57:34PM +0100, Miro Hrončok wrote:
> >  Package   (co)maintainers Status 
> > Change
> > 
> > python-selenium  mrunge, orphan0 weeks 
> > ago
> 
> I wonder if we should make ownership automatically fall to the next
> admin/committer in line, in these situations?
> 
> That being said, as I co-maintain Django and a bunch of packages we need
> for Hyperkitty, and monkeytype, that all depend on Django and thus
> selenium, I can pick it up for now.
> 
> cc mrunge, happy to pass it back to you if you want to own this
> 
> Thanks,

Thank you for stepping up! You're more than welcome to either become a
co-maintainer here or to take this package over. It has been low
maintenance in the past, where it required updates from time to time.

Ah, now that I opened up the package on src.fp.o, I see you are already
there. Awesome!

Matthias
-- 
Matthias Runge 


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Upgrade to Django 4.0.x for F36

[Matthias Runge]

On Wed, Jan 05, 2022 at 10:17:29AM -0500, Ben Cotton wrote:
> On Wed, Jan 5, 2022 at 10:12 AM Neal Gompa  wrote:
> >
> > Uhh, I think something is wrong here. How did this article get
> > namespaced like that? Maybe Ben could help fix it if you don't know
> > how that happened...
> 
> Fixed.

Thank you.
-- 
Matthias Runge 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Upgrade to Django 4.0.x for F36

[Matthias Runge]

On Wed, Jan 05, 2022 at 05:19:24AM -0500, Neal Gompa wrote:
> > As hinted in the previous paragraph, I am not involved in any
> > development connected to Django for some time now. This is a cry for
> > help. The whole Django stack in Fedora could use more helping hands.
> > Upstream is very good at providing insights, timelines etc and also
> > keeps it secured. That also means, there are regular updates.
> >
> 
> It's fine to do. We haven't branched yet. You should file a
> Self-Contained Change for it. The deadline for those is January 18.
> So, go for it!

Done: https://fedoraproject.org/wiki/Fedora_Project_Wiki:Changes/Django4.0

Thanks!
-- 
Matthias Runge 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Upgrade to Django 4.0.x for F36

[Matthias Runge]

Hey there,

would it be too late to upgrade Django for Fedora 36 to version 4.0.x?
It may require some more package updates, not just Django itself.

The releasenotes are here[1], We have version 3.2 in Fedora 35, which
is a long-term supported release (until 2024)[2].

Unfortunately, I am not able to answer the question of "what would
break?". However, not shipping a newer release would show Fedora as
outdated software.

As hinted in the previous paragraph, I am not involved in any
development connected to Django for some time now. This is a cry for
help. The whole Django stack in Fedora could use more helping hands.
Upstream is very good at providing insights, timelines etc and also
keeps it secured. That also means, there are regular updates.

Matthias


[1] https://www.djangoproject.com/weblog/2021/dec/07/django-40-released/
[2] https://www.djangoproject.com/download/
-- 
Matthias Runge 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: The great Mailman 3 / Hyperkitty upgrade: bumping flufl-lock and mistune?

[Matthias Runge]

> On Sun, 26 Dec 2021 at 23:32, Reon Beon via devel 
>  wrote:
> Update?
> https://pagure.io/fedora-infrastructure/issue/8455
> 
> 
> I am going to be overly blunt here. Messages like this do NOT help. 
> 1. Most of the people who are paid to work on this are on break for 1/2 of 
> December and some are taking off parts of January too. They are also NOT paid 
> to only work on this, but mainly to help volunteers cover parts that 
> volunteers run out of time to do. If there are no volunteers then those 
> people paid are filling out many other jobs. In the many places Fedora has 
> volunteers, the months of November, December, January, February are usually a 
> lot of family time activities with various New Year and Soltice and other 
> regional holidays. 
> 2. Messages without extra contact sound like a Boss demanding status updates 
> because they don't feel like they are getting enough work out of people. It 
> instead demotivates the people working on it (whther they are a volunteer or 
> a paid person) and makes them less inclined to a) give an update or b) 
> actually finish the project.
> 3. This is a major project. 
> a) There are multiple python packages which need to be make into rpms which 
> no one has done. These are packages which need dedicated volunteers on them 
> to keep them up to date and working. This is about a month or 2 of work 
> because packagers aren't a free resource.
> b) Once those packages are built, then a staging instance needs to be 
> deployed and the current databases imported into this. This is going to be a 
> tricky problem and there will be multiple imports and blow away and redeploy 
> because very few Databases travel well without some manual intervention. Once 
> those those tricks are figured out..
> c) you take down the live deployment and roll out the new deployment. You 
> work out all the bugs and go live.

Thank you Stephen for stating what should have been said earlier. Messages as 
those in the thread above help me to adjust email filters.

Personally, I am not paid for working on Django. This is my free time with the 
family, and I am rarely checking emails. Threads like this one reminds me not 
to bother with such issues when I’m off.

If anyone wants to see more progress, then please contribute! If you don’t, 
just shut up; you don’t have any right to request anything from volunteers.

Thank you.
Matthias
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Retire unused nose plugins?

[Matthias Runge]

On 03/08/2021 01:41, Miro Hrončok wrote:

Hello,

python-nose is deprecated in Fedora since F32:

https://fedoraproject.org/wiki/Changes/DeprecateNose

The following nose plugins appear unused in Fedora:

python-django-nose
python-nose-exclude
python-nose-progressive
python-nose-testconfig
python-nose_fixes

Should we retire them?



Hi,

yes!

I still vaguely remember some packages used either python-django-nose or 
python-nose-exclude, but with python-nose being deprecated, it doesn't 
make any sense to keep them.


Matthias
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Updating sources file using fedpkg

[Matthias Runge]

On Thu, Jun 17, 2021 at 01:57:03PM +0200, Ewoud Kohl van Wijngaarden wrote:
> Hello everyone,
> 
> As someone who just got started, I'm looking for some help.
> 
> I'd like to update packages. I'm used to git, so my typical flow is to make
> sure I have some clean branch to start working from (clone is just for
> completeness):
> 
> fedpkg clone mypackage
> cd mypackage
> git checkout -b rawhide-update-to-new-version
> rpmdev-bumpspec -n 1.2.3 mypackage.spec
> 
> Now comes the part I'm not sure about. To fetch the new sources I usually
> perform:
> 
> spectool -g mypackage.spec
> 
> After that, I'm looking for a command to update the sources file with new
> checksums so I can run:

fedpkg new-sources

This should push the new sources (compressed tarball, whatever), defined
under SOURCE* in the spec file to the cache storing the sources.
For just local builds, this step is not necessary. You could run

fedpkg mockbuild

Hope that helps,
Matthias
-- 
Matthias Runge 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: can't install package pipewire-jack-audio-connection-kit

[Matthias Runge]

On 31/12/2020 16:10, Martin Gansser wrote:

this means that jack-audio-connection-kit  has been replaced by 
pipewire-jack-audio-connection-kit ?



   - package pipewire-jack-audio-connection-kit-0.3.13-4.fc33.i686 conflicts 
with jack-audio-connection-kit provided by 
jack-audio-connection-kit-1.9.14-5.fc33.x86_64



This messes with i686 and x86_64? Usually that means, something else is 
broken.
Personally, I'd try to get rid of the 32bit binary as quickly as 
possible. Either by rpm -e --nodeps  && dnf install 

to get the 64 bit version instead of 32 bit.

Matthias
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: python-testresources version weirdness...

[Matthias Runge]

On 09/12/2020 15:38, Scott Talbert wrote:

On Wed, 9 Dec 2020, Scott Talbert wrote:

I'm working on test builds of OpenColorIO 2.0 in a COPR[1] and one of 
the

requirements to build the documentation is python-testresources.
The problem is it's looking for version 2.0+ but only 1.0 is in 
Fedora[2].

But I can't even find where that exists as a release!

More strangely, when you go to the PyPi page[3] it does show the current
version is 2.0.1, but when you go to the testresources homepage on
launchpad[4], the latest is 0.2.4 released in 2010.

Is PyPi correct that 2.0.x exists? Who's lying?


PyPi is probably correct.  Looks like they just stopped putting 
release tarballs on Launchpad.  You can see (somewhat recent) 
development in their VCS on Launchpad.


See also:
https://src.fedoraproject.org/rpms/python-testresources/pull-request/2


Hi,

thank you for pointing this out. It seems I completely missed this. It's 
building now.


Matthias
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org

Re: unbound pkgs ?

[Matthias Runge]

On 04/12/2020 12:01, PGNet Dev wrote:

unbound upstream release version is now a 1.13

Fedora packages

   https://src.fedoraproject.org/rpms/unbound

are several versions behind.

no response from maintainer in months, re updates, @

   https://bugzilla.redhat.com/show_bug.cgi?id=1860887

anyone know what's up with unbound pkgs status/plans/support in Fedora?

otherwise, it's YA-trivial DIY build ...


Thank you for looking into this. Since you already did the work,
would you mind to propose a patch here, especially, if it's trivial?

https://src.fedoraproject.org/rpms/unbound

Matthias

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: REAR and Fedora | Non-responsive maintainer

[Matthias Runge]

On 22/09/2020 09:21, Andrea Perotti wrote:
> Hi,
>     is anyone in contact with Gratien D'Haese?
> 
> I'm opening this thread and this bugzilla[0] as per policy [1].
> 
> I've noticed that on Fedora `rear` package is stuck at 2.4, while
> upstream released rear 2.6 [2].
> 
> Also you can see there's no interaction since 24 months at least from
> the official maintainer on the downstream packages [3][4], and bugzillas
> are not closed but abandoned [5].
> 
> [0] https://bugzilla.redhat.com/show_bug.cgi?id=1881221
> [1]
> https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/
> [2] https://github.com/rear/rear/releases/tag/rear-2.6
> [3] https://src.fedoraproject.org/rpms/rear/commits/master
> [4] https://koji.fedoraproject.org/koji/packageinfo?packageID=8114
> [5]
> https://bugzilla.redhat.com/buglist.cgi?classification=Fedora=rear_id=11371090=Fedora_format=advanced_desc=rear_desc_type=allwordssubstr

Hi,

if you take a look at [3], you see the package is orphaned, and I would
assume, (a) it is free to take and (b) the former maintainer has either
no time or no interest anymore.

Gratien is marked as admin for the package, but not as main contact.

Matthias
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: CPE Git Forge Decision

[Matthias Runge]

On 30/03/2020 17:41, Pavel Raiskup wrote:

> The only problem of GitLab is that Fedora - for years - was not able to
> package it.  I'm not a able to judge where the packaging problem is/was,
> any more info?  Are we going invest into packaging it?
> 
> Please make us 100% confident we are not going to be locked-in.  If we
> aren't able to package it reasonably well, it means that we have no option
> to decide to self-host GitLab in future.
> 

Self-hosting was not desired. You could, if you are trusting

curl
https://packages.gitlab.com/install/repositories/gitlab/gitlab-ee/script.rpm.sh
| sudo bash

(taken from https://about.gitlab.com/install/#centos-8 )


You can also export "most of your data" from hosted solutions, see
https://about.gitlab.com/pricing/
(there is an faq "Can I export my data")

The link is
https://docs.gitlab.com/ee/user/project/settings/import_export.html
where it says:

The following items will NOT be exported:

- Build traces and artifacts
- Container registry images
- CI variables
- Webhooks
- Any encrypted tokens
- Merge Request Approvers
- Push Rules
- Awards


Matthias
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: CPE Git Forge Decision

[Matthias Runge]

On 30/03/2020 16:23, Till Maas wrote:

 For transparency, we have published the full User Story list which is
 linked within the blog and for ease of searching is here:
 https://hackmd.io/@My419-DISUGgo4gcmO1D6A/HJB74lcL8

> https://lists.fedoraproject.org/archives/list/council-disc...@lists.fedoraproject.org/thread/OEPDGVKYAJIQ6YYZU5J3XT3LHXFROFI5/
> 
> In the hackmd story list, there are is only infosec, RH Legal Rep, RH
> Infocsec Rep, RH Developer, RHEL engineer and general users, project
> contributor, CPE team member. Nothing really maps to the user groups I
> mentioned. There is only
> 
> | 41
> | As a General User
> | I want groups and group membership and management
> | to allow me create access control on a suite of repositories
> 
> but this is very vague.


Comparing the two lists Ben posted and the one on hackmd.io differ quite
a bit. Was the list of requirements changed during the process?


Matthias
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Orphaning tinymce

[Matthias Runge]

On 15/02/2020 21:12, Kevin Fenzi wrote:
> Greetings. 
> 
> I was (probibly poorly) maintaining tinymce for a while because we used
> it for askbot. We no longer do need it so I am going to orphan it and
> hope someone out there has more time and energy to give it the love it
> needs. 
> 
> There's currently some CVE's filed against it. 
> 
> It's on versuon 4.5.1 and 5.0 is current. 
> 

Thank you for keeping it alive for so long. I don't have any use for
tinymce (anymore), and from my perspective, it can get removed.


Matthias



signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Self Introduction: Dakota Williams

[Matthias Runge]

On 08/12/2019 02:52, Dakota Williams via devel wrote:
> Hi all!
> 
> I'm working on bringing cutelyst to Fedora for my personal project.
> Formally, I'm a C/C++ developer, but have a strong interest in RPM
> packaging.
> 
> I've had some packaging experience through work by backporting glib2,
> udisks2, and libmount to el6, as well as making pamixer and playerctl
> openSUSE packages. I've also authored a patch to gnutls30 in el6[1][2]
> to fix usage with libidn2. Through work, I'm the current maintainer of
> dattobd[3], which is a kernel module for snapshotting core filesystems
> (ext2/3/4, xfs, etc).
> 
> Looking forward to making cool stuff!
> 
> Dakota
> 

Hi Dakota,

welcome to Fedora! It looks you are already on the way getting much more
involved here.

Best,
Matthias
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: RFC: Branch requests from non-maintainers

[Matthias Runge]

On 02/12/2019 14:37, Daniel P. Berrangé wrote:

> IIUC, effectively "new branches" means "EPEL branches" since normal
> Fedora branches are all created automatically.
> 
> So to rephrase this
> 
>   * Should someone who is not the maintainer be able to declare
> that the maintainer must accept EPEL branches & the extra
> work that involves thereafter.
> 
> AFAIK, there's no requirement that Fedora package maintainers have
> to provide EPEL branches, its upto each maintainer if they want that
> work.
> 
...
> 
> So if the maintainer doesn't want to maintain the EPEL branches, the
> only long term viable option is to find willing co-maintainers to join,
> who can then request the branch & do builds, triage bugs, etc. 
> 
> IOW, I struggle to see a reason to allow someone who is a not a
> (co-)maintainer to request new branches in general. I'm not convinced
> that provenpackagers should be able to do this either, unless they
> want to volunteer to be the explicitly co-maintainer too, in which
> case the question doesn't arise.
> 

Yes! Several times. I've recently had this with some of "my" packages,
where someone could create branches and even kicked in builds for EPEL8.

Half of them are broken, and for a user, it just looks bad; users also
have the expectation that I'd fix those issues. I am currently thankful
for every bit I don't have to care about. I am assuming the best intent,
but if there's a chance for it, I'd rather forbid branch requests from
non-maintainers.

Matthias
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Defining the future of the packager workflow in Fedora

[Matthias Runge]

On 27/09/2019 00:04, Miro Hrončok wrote:

On 26. 09. 19 22:06, Jason L Tibbitts III wrote:

"C" == Christopher   writes:


C> With version-controlled package sources, changelogs in SPEC seem so
C> obsolete to me. They are already problematic today when they conflict
C> due to changes in multiple branches.

It's important to note that the RPM changelog is rather a different
thing from a list of commits made to the specfile.  If I went and
re-indented the spec, that would of course get a commit message but has
no relevance to the end user and should not result in a changelog
entry.  Often I make several commits to the spec, and then update the
%changelog section with a summary of user-relevant changes only when I'm
ready to bump the release.

It seems that generating %changelog from git commits would require
something like magic tags in the commit messages, which seems like
something of a pain.


Or, as said elsewhere in this thread, we could use annotated tags.



The other possibility would be to squash commits into a single one.
Especially doing PR style makes me see commit messages like "another 
fix" or "fix typo" a lot more often compared to squashed commits, where 
one is working on a feature to be submitted as one commit (unlike 50 
commits).


Matthias
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Unresponsive maintainer: mflobo

[Matthias Runge]

On Thu, May 23, 2019 at 06:40:34PM +0200, Alfredo Moralejo Alonso wrote:
> On Wed, May 22, 2019 at 9:37 AM Didier Fabert 
> wrote:
> 
> > Le 21/05/2019 à 15:13, Alfredo Moralejo Alonso a écrit :
> > > Hello,
> > >
> > > I've been trying to contact mflobo in order to get some packages updated
> > > but didn't get any response:
> > >
> > > https://bugzilla.redhat.com/show_bug.cgi?id=1711394
> > > https://bugzilla.redhat.com/show_bug.cgi?id=1711395
> > >
> > > Output of fedora_active_user.py:

I believe, I am Marcos sponsor; thus I went ahead and merged the PRs.

IIRC, he moved on to something unrelated to OpenStack, thus I'd make
sense to at least grant commit access to the OpenStack related packages.

Matthias

-- 
Matthias Runge 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Attempting to contact unresponsive maintainers: dkaspar flaper87

[Matthias Runge]

On Wed, May 08, 2019 at 07:47:20AM +1000, Nathan Scott wrote:
> Hi Kevin,
> 
> On Wed, May 8, 2019 at 7:18 AM Kevin Fenzi  wrote:
> > [...]
> > flaper87:
> >
> > "redis": "flaper87",
> 
> I've been doing the Redis Fedora and EPEL updates for a few years now,
> I'm happy to take this one on.

Yes, I sponsored Flavio a while back, but I'm sure he won't have the
time to dedicate the necessary love to his packages.

Matthias
-- 
Matthias Runge 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Packages BuildRequiring python2-sphinx AND python3-devel

[Matthias Runge]

On Mon, Apr 29, 2019 at 10:58:45PM +0200, Miro Hrončok wrote:
> python-case  mrunge

Thank you for pointing this out, it is fixed in rawhide.

Matthias
-- 
Matthias Runge 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: python-cherrypy vs python3-cherrypy - can we keep just one?

[Matthias Runge]

On Thu, Feb 14, 2019 at 11:24:51PM +0100, Felix Schwarz wrote:
> Am 14.02.19 um 23:15 schrieb Ken Dreyer:
> > In that case, we can retire python3-cherrypy and move all development
> > to python-cherrypy, right?
> 
> We could, sure. But why bother?
> I don't have strong feelings about either solution but I don't really see the
> point. (We will have more and more "python3-" package names in the future when
> new libraries are packaged.)

With that, I'm looking for co-maintainers for python-cherrypy. The
package is severely outdated and it seems there hasn't been any
significant contribution to this over the past 4 years. I may have been
too optimistic with my available time for this.

Any interests?

Matthias
-- 
Matthias Runge 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: python-pep8 is orphaned

[Matthias Runge]

On Tue, Jan 29, 2019 at 08:40:51AM +0100, Miro Hrončok wrote:
> On 29. 01. 19 5:07, iliana weller wrote:
> > Hello,
> > 
> > I've orphaned python-pep8. pep8 was renamed to pycodestyle in 2016; it
> > received its last release in 2017. It should be removed from Fedora in a
> > future release.
> > 
> > I unfortunately don't have time to proceed with the full retirement
> > process myself. If somebody would like to pick it up:
> > https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers#Claiming_Ownership_of_an_Orphaned_Package
> > 
> > $ dnf repoquery --whatrequires python2-pep8
> > python2-autopep8-0:1.2.4-9.fc29.noarch
> > python2-pytest-pep8-0:1.0.6-15.fc29.noarch
> > python2-spyder-0:3.3.1-3.fc29.noarch
> > $ dnf repoquery --whatrequires python3-pep8
> > python3-autopep8-0:1.2.4-9.fc29.noarch
> > python3-hacking-0:1.1.0-3.fc29.noarch
> > python3-pytest-pep8-0:1.0.6-15.fc29.noarch
> > python3-spyder-0:3.3.1-3.fc29.noarch
> > 
> > See also https://bugzilla.redhat.com/show_bug.cgi?id=1667200's dependent
> > bugs.
> 
> I would like to see the package retired.
> 
> python-autopep8, python-pytest-pep8, spyder, python-hacking:
> 
> Would you mind switching to pycodestyle?

autopep8 now uses pycodestyle. I should update autopep8 over the
next few days.

For hacking, it looks like I missed the commit, which dropped the
requirement for pep8, pyflakes, and mccabe. I'll update as well.

Matthias
-- 
Matthias Runge 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: prevent accidentally creating branches in dist-git

[Matthias Runge]

On Wed, Nov 21, 2018 at 09:34:14AM -0600, Jason L Tibbitts III wrote:
> >>>>> "DM" == Dusty Mabe  writes:
> DM> I personally think this should be the default for all projects but I
> DM> don't know if there is a way to easily make that happen when a
> DM> project gets created.

> I'm sure there could be.  But I'd go further and say that we should set
> that on all existing repositories and then let folks opt out if they
> wish.

Yes,

that is a good suggestion. It'd prevent some unexpected things to happen
otherwise.

Best,
Matthias
-- 
Matthias Runge 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Attempting to contact unresponsive maintainers: sross, ryansb, mpreisle

[Matthias Runge]

On 11/11/2018 21:19, Kevin Fenzi wrote:

Greetings, we've been told that the email addresses for these package
maintainers are no longer valid. I'm starting the unresponsive
maintainer policy to find out if they are still interested in
maintaining their packages (and if so, have them update their email
addresses in FAS).

If they're not interested in maintaining or we can't locate them in 1
week, I'll have FESCo orphan the packages so that others can take them
over.

If you have a way to contact these maintainers, please let them know
that we'd appreciate knowing what to do with their packages. Thanks!

sross:

rpms/novnc
rpms/python-websockify


I've forwarded this to the nova team.

Thanks,
Matthias
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Requesting updated contact info for Matthias Runge (mrunge)

[Matthias Runge]

On 04/10/2018 14:43, Neal Gompa wrote:

Hey all,

I've been trying to get in touch with Matthias Runge (mrunge) over the
last couple of days (for getting python-celery into EPEL7 for Pagure
5). However, his email address listed in FAS bounces with "unable to
connect" errors.

Does anyone know of another email address or method to get in touch with him?

Thanks in advance!

I'm not sure how you tried to contact me. mru...@fedoraproject.org 
should work, but I haven't seen a message there.


Anyways, I've been away from the keyboard, and postfix on my mail server 
decided to die.


I'm still here and alive.

If you want to have celery in epel, I won't get into your way, but I 
don't have interest to maintain it there.



Matthias
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Packages with cicku as admin or with commit access

[Matthias Runge]

On 20/09/2018 21:30, Jonathan Underwood wrote:

On Thu, 20 Sep 2018 at 18:17, Jonathan Underwood



In the process of orphaning a few packages lately, I noticed that the
user "cicku" (Christopher Meng) still had commit or admin privelidges
on the package. That user hasn't been active for a couple of years,
and I vaguely remember packages that he owned being orphaned. But, it
seems like packages where he was co-maintainer had no changes.

Is this desirable for inactive developers? What if their account
became compromised? Would it be better if the inactive maintainer
process removed priviliges across all packages, rather than only
orphaning the packages they own?



I forgot to add this ticket for the relevant non-responsive maintainer
ticket: https://pagure.io/fesco/issue/1542


Yeah, cicku has been inactive for some time, his last build succeeded 
more than two years ago.


However, the ticket suggests, that the non-responsive maintainer process 
has not been followed correctly.


Anyways, there was the FESCO decision to orphan his packages [1], it 
seems that didn't happen completely?


Matthias



[1] 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/4LK26PNK22QTNVSZ26KWIFA5G4SXUHWC/

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Nonresponsive maintainer: Björn Esser (besser82)

[Matthias Runge]

On Fri, Aug 17, 2018 at 03:48:12PM +0200, Bob Mauchin wrote:
> On Fri, Aug 17, 2018, 12:53 Leigh Scott 
> wrote:
> 
> > Besser82 hasn't answered  any of my emails for months.
> >
> 
> I saw him back in May for a couple of reviews, maybe he's in holidays.
> 

I briefly contacted Björn, and he promised to get back here.

Matthias
-- 
Matthias Runge 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Intent to upgrade Django in f29 to 2.1

[Matthias Runge]

On Wed, Aug 22, 2018 at 11:51:34AM +0200, Miro Hrončok wrote:
> On 22.8.2018 10:59, Matthias Runge wrote:
> > Hello,
> > 
> > sorry for the late notice; Django 2.1 was recently released, and
> > I intend to update Django in F29 to version 2.1.
> > 
> > Apparently, all depending packages still build, all the details
> > in https://bugzilla.redhat.com/show_bug.cgi?id=1611025
> 
> 2 packages don't. Sorry if that was confusing. They only build in f29 (that
> is without Django 2.1).

Ah, sorry, I've misread the comment.

Django-avatar: seems to be failing, according to the classifiers, it
doesn't support Django-2.0 either, although commits hint something else.
This year already saw 2 commits to upstream, nothing connected to 2.1.

django-countries: has seen more commits upstream this year.

However, these packages would be broken by the upgrade :(

Thoughts?
-- 
Matthias Runge 
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org/message/MIXAWORFHNZIUQRIWLLG4THLP5V2ZO4D/

Re: Intent to upgrade Django in f29 to 2.1

[Matthias Runge]

On Wed, Aug 22, 2018 at 11:51:34AM +0200, Miro Hrončok wrote:
> On 22.8.2018 10:59, Matthias Runge wrote:
> > Hello,
> > 
> > sorry for the late notice; Django 2.1 was recently released, and
> > I intend to update Django in F29 to version 2.1.
> > 
> > Apparently, all depending packages still build, all the details
> > in https://bugzilla.redhat.com/show_bug.cgi?id=1611025
> 
> 2 packages don't. Sorry if that was confusing. They only build in f29 (that
> is without Django 2.1).

Ah, sorry, I've misread the comment.

Django-avatar: seems to be failing, according to the classifiers, it
doesn't support Django-2.0 either, although commits hint something else.
This year already saw 2 commits to upstream, nothing connected to 2.1.

django-countries: has seen more commits upstream this year.

However, these packages would be broken by the upgrade :(

Thoughts?
-- 
Matthias Runge 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/MIXAWORFHNZIUQRIWLLG4THLP5V2ZO4D/

Intent to upgrade Django in f29 to 2.1

[Matthias Runge]

Hello,

sorry for the late notice; Django 2.1 was recently released, and
I intend to update Django in F29 to version 2.1.

Apparently, all depending packages still build, all the details
in https://bugzilla.redhat.com/show_bug.cgi?id=1611025

If I don't hear anything against it until Monday, I'll merge rawhide into
F29.

Matthias
-- 
Matthias Runge 
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org/message/SRFRSTSGHTBO5IZSFASVYPMBAQWPSPTV/

Intent to upgrade Django in f29 to 2.1

[Matthias Runge]

Hello,

sorry for the late notice; Django 2.1 was recently released, and
I intend to update Django in F29 to version 2.1.

Apparently, all depending packages still build, all the details
in https://bugzilla.redhat.com/show_bug.cgi?id=1611025

If I don't hear anything against it until Monday, I'll merge rawhide into
F29.

Matthias
-- 
Matthias Runge 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/SRFRSTSGHTBO5IZSFASVYPMBAQWPSPTV/

orphaning/retiring some packages

[Matthias Runge]

Hello,

I'm intending to either orphan or better retire the following
packages.

python-wordpress-xmlrpc
python-mozbase
pymunin
feedstail

All of them can be considered dead upstream, and haven't seen
a release for loong time.

Takers? Otherwise I'll retire them in a week.

Matthias
-- 
Matthias Runge 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/PYXX52VQLHJFFJKQNQ4KQNYUDX2OKLZA/

Re: Making Fedora secure - Package exit policy for security

[Matthias Runge]

On Tue, Jul 31, 2018 at 09:09:58AM +0530, Huzaifa Sidhpurwala wrote:
> Hi All,
> 
> I was asked to bring this issue[1] to the developer community before
> FESCO makes a decision.
> 
> In several instances[2] there exists packages in Fedora, in which
> package-maintainers did not patch security issues, for multiple reasons
> including 1. non-responsive maintainer 2. issue hard to patch 3. no one
> cares?
> 
> This is a risk for the distribution, our users and community as a whole
> and not to mentioned bad PR :)
> 
> I would like to propose the following:
> 
> 
> 1. If a CRITICAL or IMPORTANT security issue is open against a package
> in Fedora-X and by the time X is EOL and the issue is not addressed,
> proactively remove the package from X+1
> 2. If a MODERATE or LOW security issue is open against a package in
> Fedora -X and by the time X+! is EOL, the issue is not addressed, remove
> it from X+2
> 
> Note:
> 1. Once pkg is patches, it can be rebuild and re-introduced into the distro
> 2. X/X+1 is the best boundary to remove the insecure packages imo, since
> inbetween removals are not possible due to the way mirrors work.
> 3. Maintain a list somewhere (automated maybe) of the list of packages
> removed and why.
> 4. Have a list of critical pkg, which cannot be removed which will break
> the distro.
> 
> The above is not set in stone, but is open for discussion. Let me know
> what you guys think!

Hello,

first of all, I really like a more formal approach. However:

what about an old version of package p in Fedora release X-1 with a CVE;
if upstream does not fix it, you'd be expecting to fix this by the
package maintainer; that'd require either backporting to an older
branch, or upgrading the package to a newer version, possibly breaking
packages being dependencies of pkg in an old (or at least released)
Fedora version. Not ideal :-/

> 
> In the end, i would like you leave you all with this parting link:
> https://sensorstechforum.com/arch-linux-aur-repository-found-contain-malware/

This is a different issue. While we can not be sure this won't happen in
Fedora, I'd like to focus on one question/issue per thread.

Matthias

-- 
Matthias Runge 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/6CGHEU3PI4BW3Q46PHJNZNKCRPZ7H7A2/

Re: dokuwiki packagers unresponsive

[Matthias Runge]

On Mon, Jul 30, 2018 at 11:07:21PM +0200, Peter 'Pessoft' Kolínek wrote:
> I've already submitted a pull request for dokuwiki circa a month ago:
> https://src.fedoraproject.org/rpms/dokuwiki/pull-request/2
> Also for topdog's other package ike 10 days ago:
> https://src.fedoraproject.org/rpms/ike/pull-request/1
> 
> @Matthias, Sérgio: Do you know at which month approximately you had a
> response from topdog?
> On fedmsg I can see last entries invoked by topdog 11 months ago.

Ok, great!

Unfortunately, I don't remember anymore the time of contact. It has
probably been more than 12 months.

Matthias
-- 
Matthias Runge 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/HNVZEANLZI5OHMS4VK3YYJCIZXL5UMW5/

Re: dokuwiki packagers unresponsive

[Matthias Runge]

On Fri, Jul 27, 2018 at 02:51:25AM +0100, Sérgio Basto wrote:
> On Thu, 2018-07-26 at 21:43 -0400, Solomon Peachy wrote:
> > On Thu, Jul 26, 2018 at 09:09:25PM +0200, Peter 'Pessoft' Kolínek
> > wrote:
> > > I'd like to fix some issues (including security problems) which are
> > > for
> > > a long time present in dokuwiki package. Maintainers of the
> > > dokuwiki
> > > however seem unresponsive. 
> > 
> > It's worth stating that "some issues" is a euphamism for "the 
> > package has been fundamentally broken since Fedora 24."
> > 
> >   https://bugzilla.redhat.com/show_bug.cgi?id=1372948
> 
> 
> The main admin (togdog) usually give permission to commit if you ask
> him , at least did to me . 

Right, I can second that. It worked for me as well.

With pagure in place, you could also submit pull requests to improve
the situation.

Matthias
-- 
Matthias Runge 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/2ROT7CN7RZ2BEIVBABZJZKR6ZRIVOUEX/

Intend to retire python-openstack-nose-plugin

[Matthias Runge]

Hello,
the subject says it, I'm intending to retire
python-openstack-nose-plugin. It is old,
very old. Last commit upstream was 2012.

Any takers, otherwise I'd retire it in a week.

Matthias
-- 
Matthias Runge 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/OQAQNMVZNRML6BGEKUUGKL4IZDK323DB/

Re: iptables rules dont copy to vsphere template

[Matthias Runge]

On Wed, Apr 25, 2018 at 11:59:46AM -, Elham Sadat Azarian wrote:
> Hi
> I set a rule in iptables(firewall-cmd) and try to clone a template from my 
> server with vsphere. but my template didnt inherit this rules!
> whats the problem?
> thanks

Elham,

this list is for Fedora contributors and developers. For usage
questions, please use us...@lists.fedoraproject.org

When asking a question there, please include more input:

- what did you do, how did you...
- what went wrong, what was expected


Thank you,
Matthias
-- 
Matthias Runge <mru...@matthias-runge.de>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: DNSSEC, DoH, dnscrypt-proxy 1 vs 2

[Matthias Runge]

On Mon, Apr 09, 2018 at 10:01:21AM +0200, Martin Sehnoutka wrote:
> > Restarted Firefox and then also the whole laptop. Doesn't work. But
> > then I'm in Fedora 28 so it may be a bug. Anyway, getting this to work
> > for me isn't really the point of the thread. I'm wondering about
> > something that works out of the box for everyone, what that looks
> > like, and it seems like dnscrypt-proxy 2 can support either DNSSEC or
> > DNS-over-HTTP.
> 
> I've been playing with dnssec-trigger for a while and I would not enable
> it by default. If you have a single connection with ISP provided
> resolvers or public DNS, it is fine, but it gets harder to configure
> when you have multiple connections like Wi-Fi and corporate or
> university VPNs where each provides some forward zones and needs reverse
> zones for correct behavior.

Same here, I' cusious if anyone has been able to get it working
properly? In best case, has someone written about it?

I'm fiddling around with adding/removing unbound forwards depending on
connected networks here and there, but it's still quite hacky.

Matthias
-- 
Matthias Runge <mru...@matthias-runge.de>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: F28 Self Contained Change: Django 2.0

[Matthias Runge]

On Tue, Dec 12, 2017 at 06:06:46PM +0100, Jan Kurik wrote:
> = Proposed Self Contained Change: Django 2.0 =
> https://fedoraproject.org/wiki/Changes/Django20

For curious folks, there is a copr[1] with django 2.0 builds to try out.

I'm going to strip current Django-1.11 builds down to remove the python3
package and will provide that through the copr as well.

Best,
Matthias

[1] https://copr.fedorainfracloud.org/coprs/mrunge/Django2/
-- 
Matthias Runge <mru...@matthias-runge.de>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: MASS CHANGE announcement: python2- prefix renaming, part 2

[Matthias Runge]

On 24/12/17 09:58, Zbigniew Jędrzejewski-Szmek wrote:
> Hi,
> 
> I did the rebuilds yesterday.
> 
> totpcgi, python-django-dynamite, libappindicator failed to rebuild for
> unrelated reasons, bugs have been filed:
> https://bugzilla.redhat.com/show_bug.cgi?id=1528774,
> https://bugzilla.redhat.com/show_bug.cgi?id=1528798,
> https://bugzilla.redhat.com/show_bug.cgi?id=1528799.
> 
> Let me know if you encounter any problems with the rebuilds I did.
> 
> Zbyszek
> 

Django-dynamite has seen its last release on Jan 26 2012. I haven't much
looked into the code yet. I would just drop it.

The build failure looks like a packaging issue, which is probably
related to changes in Django over the time and now requiring a database
connection specified for running tests.

Matthias
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: What to I have to do....

[Matthias Runge]

On Fri, Dec 08, 2017 at 08:30:20PM +0100, Matthias Runge wrote:
> Now this has gone back and forth. The system worked more or less ok.
> Maybe it is more about the changes (and communication) of a
> specific provenpackager?

After sleeping a night over this, I should have put it in different
words:

My questionis are here:
- do we have an issue at all?
- do we have an issue with a single provenpacker
- do we have an issue of attitude or with a group of people?

The consensus of this long thread was: no, the system works mostly ok.
That makes me believe, we don't have a generic issue.

It's not my intention to blame anyone here, I'm still assuming best
intentions.

Nevertheless, since people are different, and not everybody can be
friends with each other, maybe it's a good idea to make communication
mandatory, in cases where proven packagers touch others packages? For
mass changes, there is/should always be an announcement to the
devel mailing list.

Matthias
-- 
Matthias Runge <mru...@matthias-runge.de>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: What to I have to do....

[Matthias Runge]

On Fri, Dec 08, 2017 at 11:46:03AM -0500, Steve Dickson wrote:
> 
> 
> On 12/08/2017 11:21 AM, Charalampos Stratakis wrote:
> > The kernel is actually blacklisted from proven packager access, you can't 
> > make changes there.
> This is good to know... how do you get on that list? ;-) 
> > 
> > Apart from that though, I don't really see any reasons for creating this 
> > thread.
> > 
> > Proven packagers do trivial and non-trivial cleanups all the time. While I 
> > agree that a PR would be better,
> > when dealing with changes on a vast amount of packages that should be 
> > ideally done in a timely manner, waiting for a
> > timely response from every single maintainer of the respective packages is 
> > just not realistic.
> I understand the need to make massive changes... I no problem with that...
> The problem is random people are making non-critical, non-massive 
> changes because they "feel" its the right thing to do. Those
> changes should go through the maintainer. 

Now this has gone back and forth. The system worked more or less ok.
Maybe it is more about the changes (and communication) of a
specific provenpackager?

There has been a recent thread "stop messing with other people packages",
and Iwonder who the mentioned proven packager was in that case.

I had once a case, where even a bug was filed by the pp, the change
submitted and bug closed after. I was online and reading emails at
that time, but I didn't had the chance to react. I asked the pp to
wait for my reaction in a reasonable time before doing that again.

Unfortunately, some time later, the same proven packager changed
something else. It was just a cosmetic change, and he didn't even
try to contact me, neither via irc, nor email or bugzilla.

So, maybe this is just caused by the behaviour of a single person?

Matthias
-- 
Matthias Runge <mru...@matthias-runge.de>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Django 2.0 released, and what it means to you

[Matthias Runge]

On Wed, Dec 06, 2017 at 10:26:11AM +0100, Matthias Runge wrote:
> On Wed, Dec 06, 2017 at 09:56:28AM +0100, Lumir Balhar wrote:
> > On 12/05/2017 04:27 PM, Miro Hrončok wrote:
> > > Maybe a Fedora Change coordinating this would be nice?
> 
> probably a good idea.

To follow-up on this, I'm drafting a change[1]. Since my
responsibilities changed, this has a quite low priority for me.
Any help is greatly appreciated!

Best,
Matthias
[1] https://fedoraproject.org/wiki/User:Mrunge/Django20
-- 
Matthias Runge <mru...@matthias-runge.de>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Django 2.0 released, and what it means to you

[Matthias Runge]

On Wed, Dec 06, 2017 at 09:56:28AM +0100, Lumir Balhar wrote:
> On 12/05/2017 04:27 PM, Miro Hrončok wrote:
> > Maybe a Fedora Change coordinating this would be nice?

probably a good idea.

> > Those are packages that require python(2)-django and are themselves not
> > prefixed with python(2)-django:
> > 
> > cobbler-web
> > fts-monitoring
> > gramps-webapp
> > graphite-web
> > kobo-admin
> > kobo-django
> > kobo-hub
> > pony
> > pulp-server
> > 
> > I suggest we go trough them and see. At least the kobo thing is probably
> > being ported to 3 by Lumír (CC'ed)

graphite-web requires Django <= 1.11.99, but has been ported to python3.

> Kobo is currently tested with Django 1.6 and 1.8. The codebase is ported to
> Python 3 but it needs to be modified to support Django >= 1.11. There are
> some issues but I don't know Django well enough to fix them.
> 
> I am not a maintainer nor a user of Kobo but I think that Kobo will need
> python2-django in Fedora.
> > 
> > Even if we and up having python2-django, I suggest we remove all the
> > unneeded python2-django-wahtnots anyway and only keep the ones used by
> > the apps.
Yes, this makes sense.

Going the safe route, we should add the python2 package based on
django-1.11.x and current apps would continue to work.

Thoughts?

Best,
Matthias
-- 
Matthias Runge <mru...@matthias-runge.de>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Django 2.0 released, and what it means to you

[Matthias Runge]

On Tue, Dec 05, 2017 at 10:45:54AM +0100, Petr Viktorin wrote:
> > Django 2.0 was released quite recently. While it is mostly compatible with
> > earlier versions, the SIGNIFICANT change is, to drop support for Python 2.
> > 
> > I'm intending to update Django in Rawhide to 2.0 in 2 weeks. If you're
> > maintaining a package depending on Django, please make sure to disable
> > the python2 subpackage. Please keep in mind, you'll also need proper
> > obsoletes.
> > 
> > If there is any bug, blocker, whatever connected to this change,
> > please make also sure to report it in bugzilla and
> > make your bug a blocker for[1].
> 
> Hi,
> Another option is to create a new "python2-django" package containing the
> latest Django 1.x code (which is still supported upstream as LTS). That
> would mean dependent packages would have until April 2020 to drop Python 2.
> If that would help, let me know and I'll package it.

Interesting idea, but how would you handle the mandatory python2 package
for it then? Would that require some FPC decision?

I would expect the python3-django would get upgraded at least a few
times until 2020.

Matthias
-- 
Matthias Runge <mru...@matthias-runge.de>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Django 2.0 released, and what it means to you

[Matthias Runge]

Hello,

tl;dr if you're not maintaining/using a Django related package,
you can safely skip this message.


Django 2.0 was released quite recently. While it is mostly compatible with
earlier versions, the SIGNIFICANT change is, to drop support for Python 2.

I'm intending to update Django in Rawhide to 2.0 in 2 weeks. If you're
maintaining a package depending on Django, please make sure to disable
the python2 subpackage. Please keep in mind, you'll also need proper
obsoletes.

If there is any bug, blocker, whatever connected to this change,
please make also sure to report it in bugzilla and
make your bug a blocker for[1].

Thank you,
Matthias

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1494761
-- 
Matthias Runge <mru...@matthias-runge.de>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: COPR strategy

[Matthias Runge]

On Tue, Aug 22, 2017 at 05:17:56AM +0200, Michal Novotny wrote:
> Hello,
> 
> we will have soon a planning meeting that should determine a more long-term
> strategy and bring us to a team agreement on what COPR currently is and
> what it should be in half a year or so.
> 
> I would like to kindly ask for some input here on the devel list to find
> out what the actual expectations of COPR are and if there are any ideas
> about what could COPR bring to the game.

So, as a starter, what I really like about copr is:

- it is actually a incubator, a tool to get packages or collections of
  packages built. One can easily experiment without actually disturbing
  other users. Copr lowers the entry barrier for new pacakgers.

- the ability to directly upload srpms; that is, one can store spec
  files etc. on the local machine. I'm undecided, if integrating a
  distgit on copr would solve any issues or would introduce more, like
  diverging specs.

- the ability to include external repositories, like the one from CentOS
  project.

What I would like to see:

- maybe a easy possibility to build packages triggered by upstream
  source changes. This is comparable to delorean[1]. I'm not sure if it
  needs to be re-implemented.

- prioritization of manually uploaded tasks vs. automatic builds. If
  that really lowers the waiting time for builds it to be discussed.
  Maybe adding a "bulk" flag to tag builds as: build it, when a builder
  is available, but it's not a priority. Send a message once the build
  is done.

- it would be great, if there is a possibility to trigger rebuilds on
  dependent packages, like rebuild required packages after ABI bump.


Thanks,
Matthias

[1] https://www.rdoproject.org/what/dlrn/
-- 
Matthias Runge <mru...@matthias-runge.de>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Review Swaps

[Matthias Runge]

On Tue, Feb 21, 2017 at 12:09:18PM -0600, Greg Hellings wrote:
> Hi, everyone.
> 
> I have three outstanding package reviews that I'd be happy to swap with
> anyone who is willing and also in need.  Listed in my order of need, they
> are:
> 
> python-beaker: https://bugzilla.redhat.com/show_bug.cgi?id=1410594
I'll take this one, could you please have a look at this here?

https://bugzilla.redhat.com/show_bug.cgi?id=1402319

Thank you

-- 
Matthias Runge <mru...@matthias-runge.de>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: unheeded ACL requests

[Matthias Runge]

On Sun, Feb 12, 2017 at 03:05:04AM +, Globe Trotter wrote:
> Hello, 
> 
> For a long time (almost 2 years), dilo (and a number of packages) have not 
> been updated. So, I decided to request commit privileges. But the request has 
> sat unheeded for the last several months. Unfortunately, this is not true 
> only for dillo, but also for a bunch of other packages (eg: revelation, 
> xplanet, spacefm, etc). Is there a way to get things to move at all? 
> Thanks a lot for any suggestions!

I would also send a mail to the package owner, explaining why you'd want
commit access to this or that repository.

In my experience, that always helps; as a personal preference, I tend
to ignore requests from someone without context.

Matthias
-- 
Matthias Runge <mru...@matthias-runge.de>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: review swap

[Matthias Runge]

On 27/12/16 22:02, Matthias Runge wrote:
> Hello,
> 
> I have 2 easy Python reviews up for swapping
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1408869
> https://bugzilla.redhat.com/show_bug.cgi?id=1408868
> 
> One depends on the other, both are easy picks.
> Matthias
Second one was finished already, any takers for

https://bugzilla.redhat.com/show_bug.cgi?id=1408869 ?
It's a (missing) dependency for kombu-4.0.x in rawhide.

Thanks,
Matthias
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Packages FTBFS with Python 3.6

[Matthias Runge]

On Fri, Dec 23, 2016 at 02:33:29PM -0700, Pete Zaitcev wrote:
> On Wed, 21 Dec 2016 00:18:47 +0100
> Miro Hrončok <mhron...@redhat.com> wrote:
> 
> > I've attached the list of failed packages (failed.txt). You can search 
> 
> python-ceilometerclient
> python-keystoneclient
> python-manilaclient
> python-swiftclient
> 
> These are victims of python-oslo-sphinx, needs a new release:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1408503
> 
I just went ahead and pushed a fix Pete.

Matthias
-- 
Matthias Runge <mru...@matthias-runge.de>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

review swap

[Matthias Runge]

Hello,

I have 2 easy Python reviews up for swapping

https://bugzilla.redhat.com/show_bug.cgi?id=1408869
https://bugzilla.redhat.com/show_bug.cgi?id=1408868

One depends on the other, both are easy picks.
Matthias
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

orphaning python-ladon

[Matthias Runge]

Hello,

due to lack of time, and because I don't use it any more, I'm hereby
orphaning python-ladon. It's a low maintenance package.

Feel free to pick it up.

Matthias
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[EPEL-devel] Re: Django stable RPMs

[Matthias Runge]

On 08/11/16 16:31, Brian Bouterse wrote:
> I believe the future of Django in EPEL is a topic that is being
> discussed on the EPSCO meetings last week and this week (18:00 UTC on
> Wednesdays in #fedora-meeting, iirc).
> 
> I'm hoping that even if a newer, 1.8 based Django package is added to
> EPEL6, that the existing one named Django14 can be kept for legacy
> usage. The Django14 package having that unconventional name would allow
> a new package to use the more conventional python-django name which is
> convenient.

I believe I can shed a light here:
- Django14 followed the old Django naming scheme in Fedora. Django was
renamed to python-django there.
- Django-1.4 was the old long term supported version and works with
pythons up to python 2.6
- Django14 should be retired IMO
- Django-1.8 (current long term supported version) requires python 2.7.
That means, we can not have a recent Django in EPEL6 with system python.
- The main reason not updating to Django-1.8 in EPEL7 is reviewboard. (I
don't know the state of askbot currently, Fedora has ask.fedoraproject.org).
- Maintaining a django version, which was retired upstream becomes more
and more a pain, esp. if it's not part of your job to keep it alive.

Matthias
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org

[EPEL-devel] Re: nodejs update

[Matthias Runge]

On 23/08/16 03:48, Stephen Gallagher wrote:
>> On Mon, Aug 22, 2016 at 4:23 PM, Stephen Gallagher 
>> >
>> Let me (or open a rel-eng ticket) when you want a epel7-nodejs6 side
>> tag to build it into. Will make it easier so you don't need to deal
>> with a billion build overrides etc.
>>
> 
> I'm not sure that will be strictly necessary; we figured out during the 
> Fedora process that once we moved to the bundled NPM, we only had about a 
> dozen packages that actually needed a rebuild to support Node.js 6.x (just 
> the ones that build a native, archful module).
> 
> But yes, I'll make sure to let you know if we decide it needs a side-tag.


Nodejs 6 bundles openssl 1.0.2.h, where RHEL/CentOS have a much older
version. That hasn't been an issue in Fedora; For CentOS, there is a
build for Node.js 4 in cbs, including a patch to unbundle openssl and to
make it work with the way older lib.

Unless we have a comparable patch (if possible) for Node version 6,
maybe we should stick with version 4?

Matthias
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/epel-devel@lists.fedoraproject.org

Re: [Python-SIG] Self-Introduction: Tim Orling

[Matthias Runge]

On 15/08/16 16:06, Petr Viktorin wrote:

> 
> Then there are always things others would like help with in their quest
> to make Fedora better. For example, in the Python 3 effort, there's a
> tracking bug for cases where the packager doesn't have time to do the
> Python3 port. Some of the bugs there need expert skills, for some it's
> just that the packager doesn't have time:
> https://bugzilla.redhat.com/show_bug.cgi?id=1333765
> If you'd just like to help others but don't know where to start, this
> list is a good place to ask.
> 

Welcome Tim,

that bug contains a some links to spec files, which are in need of a
patch. But that being said, there are quite a few spec files following
some older recommendation and are now in need of modernization. Patches
are welcome there as well, I'd assume.

If you're looking for other pointers, where to help,
http://fedora.portingdb.xyz/ is another resource.

Best,
Matthias
___
python-devel mailing list
python-devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/python-devel@lists.fedoraproject.org

license change python-gevent-websocket

[Matthias Runge]

Hello,

license for python-gevent-websocket changed from BSD to ASL 2.0.
As additional note, upstream changed their repository, the author stayed
the same.

Matthias
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: Attempting to contact unresponsive maintainer - ndipanov

[Matthias Runge]

On Mon, Apr 25, 2016 at 09:11:40PM +0200, Haïkel wrote:
> 2016-04-25 18:00 GMT+02:00 Kevin Fenzi <ke...@scrye.com>:
> > Greetings, we've been told that the email addresses
> > for this package maintainer is no longer valid.  I'm starting the
> > unresponsive maintainer policy to find out if they are still interested
> > in maintaining their packages (and if so, have them update their email
> > addresses in FAS).  If they're not interested in maintaining or we
> > can't locate them I'll have FESCo orphan the packages so that others
> > can take them over.
> >
> > If you have a way to contact this maintainer, please let them
> > know that we'd appreciate knowing what to do with their packages.
> > Thanks!
> >
> > * ndipanov - former email ndipa...@redhat.com
> >
> > Point of contact:
> >
> > rpms/python-autopep8 -- The package autopep8 formats Python code based 
> > on the output of the pep8 utility ( master f24 f23 f22 )
> >
> > Co-maintainer:
> >
> > rpms/novnc -- VNC client using HTML5 (Web Sockets, Canvas) with 
> > encryption support ( master f24 f23 f22 epel7 )
> > rpms/openstack-glance -- OpenStack Image Service ( f23 f22 )
> > rpms/openstack-nova -- OpenStack Compute (nova) ( f23 f22 )
> > rpms/python-oslo-config -- OpenStack common configuration library ( 
> > master f24 f23 f22 )
> > rpms/python-oslo-messaging -- OpenStack common messaging library ( 
> > master f24 f23 f22 )
> > rpms/python-websockify -- WSGI based adapter for the Websockets 
> > protocol ( master f24 f23 f22 epel7 el6 )
> >
> > kevin
> >
> 
> Nikola recently left Red Hat, just reassign whatever packages he had to me.
> 
> Regards,
> H.

Thank you Haikel.

I sponsored Nikola. I can take his packages as well.

Best,
Matthias

-- 
Matthias Runge <mru...@matthias-runge.de>
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

[EPEL-devel] Re: EPEL Meeting 2016-03-08

[Matthias Runge]

On 09/03/16 20:33, Kevin Fenzi wrote:

>>  -b- We re-review Django14 and put it in. However there are 4+
>> security problems which can't be fixed without a major version move.
>> Because of this , the package may not pass review.

Because it has been retired upstream, I'm not sure if anyone really
looked at that, if there are 2 or really 4 security issues. The most
recent two might have fixes to be even backportable.

For reference, the request for re-review
is here: https://bugzilla.redhat.com/show_bug.cgi?id=1316068
> 
> We actually don't need to review it... if it's been retired less than 2
> weeks, we can just unretire it. We do need someone(s) to take over
> point of contact though. 
> 
> I guess I could do it, but is anyone else willing first? :) 

Actually, I made the mistake and did not retire it in f22-f24; it
doesn't make sense there at all. Could we consider the package as not
being retired at all?

Once the EPEL6 situation is solved, I should retire it on the previously
named branches.
> 
>>  -c- We skip re-review in this case and put the package back in. We do
>> so with an explicite end of life of 180 days (or 7.3 if that is
>> sooner) with either -a- happening or a python27 is packaged AND a
>> django 1.8 AND the packages requiring 1.4 are updated to 1.8.
> 
> Yeah, a time limit might be nice, but not sure how long all the various
> projects need + how long it will take to bring up a python27 + django1.8
> 
> Are any folks willing to work on this?
> 

Bringing in python2.7 and Django-1.8 would be the safest bet (in terms
of future stability), but that requires a bit of work, and just bringing
in python2.7 and Django-1.8 is the smallest portion here.

Matthias
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/epel-devel@lists.fedoraproject.org

Re: Orphaning python-django-haystack and python-django-pipeline in Fedora

[Matthias Runge]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 24/02/16 17:08, Stephen Gallagher wrote:
> I no longer need these packages in Fedora (they were there to
> support Review Board which is now only in EPEL due to Django
> incompatibilities), so I've orphaned them.
> 
> I will continue to maintain them on EPEL 7. --

Taken.

Stephen, thanks a lot for keeping them in your good hands.

Co-maintainers are always welcome.

Best,
Matthias
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWzgdhAAoJEBdpskgc9eOLBrgP/AgURuxhqblwmCt6d4fmJZeu
XO99YXoNQ0jou3fpApuA67NY0FDaXXy3TYRDfNbD292mr3bMhZ6ecUXUWPY0Tekv
2c0Ywx4lLkldNB1QOHohilzs3Fln/WDB6xjnO8XyJD/B+Zt74UQfLLSzut5dZd8F
DzJ/C/bKto00XUb2WVt+gZ9YeanE7kvmgP3CTx65JjA9LUUYuV/H+vm/li2wTa7Y
lWeaECbTrQ8ItL09AtAvQxa8tUa6A3SGk8tAWgnyiOy+uI8PS65Yz0bNHL5H2vdO
v0+V1UYsNEGxaYOCUNbwlHQo0JaOfueucPOC1o/AqUSuXT8Zp4raP4uDgImAC4bO
3B13c419DvVYiwLs5f6EoNiv1ANBEoImWivTBM1+gBLv6P7bmoVc/5Vzle/uL0LX
cK/2RFoUyWIUgqNpoV3pt/NV68yWvuwP2+InGEKksl5/E31/stqc35i7yxEqcEyz
0c0IHUM2FyfSsA+w0hWqSodWWYJL6NLKTroqlD4D1NHjllk6bdWy/X0P8S7svWF4
CYMMC4FnhNkrHWm02v+4+kvT0fkubY1LwzQFMQxGv5f3TGsw1/MtKXRGV1FTeJj6
+kh8A9K/KNbn27qbMuqsawPU4QlSeMwLbwR7epKjNQVhxwpDlOYeGzOZlVW7lntj
kyVO7BByLSkdQdaL1rkU
=MSg5
-END PGP SIGNATURE-
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Intend to upgrade Django to 1.9.2+ in rawhide

[Matthias Runge]

Hello,

Django-1.9 was released some time ago, currently we have
Django-1.8 in rawhide, f23 and f22.

It makes sense to upgrade, if we want fedora to stay a development platform.

A scratch-build to test can be found here:
http://koji.fedoraproject.org/koji/taskinfo?taskID=12944336

Best,
Matthias
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: Xulrunner - intent to remove from Fedora 24

[Matthias Runge]

On 26/01/16 14:10, Mikolaj Izdebski wrote:

> pencil
> 
pencil did not had any release for a longer time (although they directly
recommend downloading a fedora 19 package, the latest build made by the
package maintainer was 2 years ago for f20.

Maybe it's time to retire it completely?

Matthias
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: python-mongoengine maintainer absent

[Matthias Runge]

On 15/12/15 15:07, Randy Barlow wrote:
> Hello!
> 
> I've been attempting to contact the python-mongoengine
> maintainers, Yohan Graterol and Eduardo Javier Echeverria Alvarado,
> for some time with no response[0]. In addition to the two bugs I've
> filed, I've written e-mail to Yohan twice (on 2015-11-21 and
> 2015-11-30) and to Eduardo once (2015-11-30). It has been 24 days
> since I first attempted to contact Yohan.

Eduardo participated at the latam-ambassadors-meeting a few days
ago[1]. His nickname is echevemaster.


He might also be able to contact Yohan.

[1]
https://meetbot.fedoraproject.org/fedora-meeting-2/2015-12-12/fedora_latam_ambassadors.2015-12-12-22.58.html


Matthias
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: Orphaned Packages in rawhide (2015-09-21)

[Matthias Runge]

On Mon, Sep 21, 2015 at 11:35:30AM +, opensou...@till.name wrote:
> The following packages are orphaned and will be retired when they
> are orphaned for six weeks, unless someone adopts them. If you know for sure
> that the package should be retired, please do so now with a proper reason:
> https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
> tinymceorphan, mrunge, ngompa, rhe   0 weeks ago   
> tinymce-spellchecker   orphan, mrunge, ngompa, rhe   0 weeks ago   
...
> Depending on: tinymce (1), status change: 2015-09-20 (0 weeks ago)
>   python-django-tinymce (maintained by: yuwang, mrunge)
>   python-django-tinymce-1.5.2-2.fc21.noarch requires tinymce = 
> 3.5.10-3.fc23

Those 3 package should imho just go away.

Any takers? Otherwise I'd retire them in 2 weeks.
-- 
Matthias Runge <mru...@matthias-runge.de>
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Copr for FeedReader

[Matthias Runge]

On 03/09/15 02:51, Pete Walter wrote:
> On 09/02/2015 01:00 PM, Vít Ondruch wrote:

>>> I was advised to ask on this list for help regarding setting up a copr
>>> repository.
>>
>> Why Copr and not Fedora official package? Is there something which
>> conflicts with Fedora's Packaging Guidelines [1]? Otherwise I can't see
>> Copr to be less maintenance effort then official package (except the
>> initial review).
> 
> I posted a review request at 
> https://bugzilla.redhat.com/show_bug.cgi?id=1259532 to include it in Fedora 
> proper, but I am not a packager yet and would need a sponsor.
> 
Pete,

thank you for putting this up. Ideally, you'd collaborate with Jan. It's
possible, that there are issues with the package, which require changes
in upstream code.

Matthias
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Sponsors - who does (not) work on FE-NEEDSPONSOR tickets

[Matthias Runge]

On Mon, Aug 17, 2015 at 09:14:34AM +0200, Miroslav Suchý wrote:
  I don't know if this has changed in he new age of having crazy human
  coding machines, but the last time i looked it was extremely difficult
  to see someone's sponsor and to generate statistics on sponsorship
  activities.  I had some tooling a very long time ago which was used to
  stir up a whole pile of flames surrounding the handling of inactive
  sponsors.
 
 Although I think too, that right way is to sponsor somebody via Package 
 Review, I enhanced my script to show direct
 sponsorship - which means that this information is available in FAS :)
 Mind that this information is not (yet?) linked to that BZ reviews, so I show 
 BZ reviews *and* independently sponsorship
 in FAS. Without information if this was result of some Package Review.

There is this process to become a co-maintainer. I think this is quite
useful:
The way this is intended (IMHO), is, to get an upstream
developer becoming a package maintainer for the specific component. That
person at first might not be the best person to maintain an rpm package.
But this person knows the software quite well.
-- 
Matthias Runge mru...@matthias-runge.de
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: [ACTION REQUIRED] FTBFS Packages in rawhide (2015-07-11)

[Matthias Runge]

On 11/07/15 17:24, Haïkel wrote:

I fixed python-autopep8 as provenpackager.

Thank you! I had it on my plate and wanted to look at it today, 
observing it was fixed already :D


Matthias


--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Orphaning python-xhtml2pdf

[Matthias Runge]

Hello,

I'm orphaning python-xhtml2pdf. It has been more or less dead upstream 
for years.


Matthias

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: F22 System Wide Change: Django 1.8

[Matthias Runge]

On Thu, Feb 26, 2015 at 02:20:35PM +0100, Zbigniew Jędrzejewski-Szmek wrote:
  Strictly speaking[1], I don't need a permission to do so. Still, I would 
  like to ask for opinions here.
 It will not be pushed until after alpha release unless it gets an exception.
 
  [1] https://fedoraproject.org/wiki/Updates_Policy#Pre_Beta
 See https://fedoraproject.org/wiki/Updates_Policy#Milestone_freezes :)

Yeah, but that wouldn't really help in testing this.

If I would build it now, and it get's submitted way later, it may be too
late in the game to land this feature.

Matthias
-- 
Matthias Runge mru...@matthias-runge.de
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Packages

[Matthias Runge]

On 26/02/15 19:06, Rahul Sundaram wrote:
 Hi
 
 I would like to give away as many packages as I can to others who are
 interested.  My current job keeps me pretty busy and I have been hanging
 on to them in hopes of finding the elusive free time that I don't get
 much of anymore.  So if you to be a comaintainer or want to take over
 anything that I am the point of contact, feel free to drop a request in
 pkgdb and send me a note off list as well.   Thanks for those who have
 stepped in from time to time.
 
 The list of packages is at
 
 https://admin.fedoraproject.org/pkgdb/packager/sundaram/
 
 Rahul
 
 

Congrats to the new job!

I'd take
* python-kombu
- which I maintained for the past years
* python-gdata
- which is a dependency on one or the other of my packages
* python-billiard
- I looked after that for a longer time

* django-* packages should be all become retired.

Matthias
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: F22 System Wide Change: Django 1.8

[Matthias Runge]

On Tue, Jan 27, 2015 at 01:33:57PM +0100, Matthias Runge wrote:
 On 27/01/15 11:51, Miloslav Trmač wrote:
  Hello,
  ** A build containing latest Django will be pushed to f22 branch late in 
  dev
  cycle. If we decide not to push Django-1.8, nothing will be broken.
  ** Django 1.8 final release is expected around April 1st, 2015: [2]

A bit late, yesterday Django-1.8 beta was released. A package is
available for rawhide. I would like to push it to f22, too.

Strictly speaking[1], I don't need a permission to do so. Still, I would 
like to ask for opinions here.

Thanks,
Matthias


[1] https://fedoraproject.org/wiki/Updates_Policy#Pre_Beta
-- 
Matthias Runge mru...@matthias-runge.de
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: New Upstream Release Monitoring Systems

[Matthias Runge]

On Fri, Feb 20, 2015 at 03:36:11PM -0500, Ralph Bean wrote:
 I'm proud to announce that the Infrastructure team has finished deploying the
 first iteration of our replacement for the older, wiki-based Upstream Release
 Monitoring tools this week.  You can read about the details of the trio of
 systems[1] now used to coordinate upstream release monitoring on the same old
 wiki page.
 
 Names of systems:
 
 - pkgdb is the familiar Fedora Package DB 
 https://admin.fedoraproject.org/pkgdb
   It provides some flags used by the other systems.
 - anitya is the web app running at https://release-monitoring.org
   It is responsible for scraping upstream release sites looking for new
   releases.
 - the-new-hotness is a backend daemon that responds to fedmsg messages about
   upstream releases.

This is very cool! Thank you and congrats to the new release!

Matthias
-- 
Matthias Runge mru...@matthias-runge.de
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: [EPEL-devel] el7 liblockfile

[Matthias Runge]

On Mon, Feb 16, 2015 at 10:25:41PM +, Peter Robinson wrote:
 On Mon, Feb 16, 2015 at 10:09 PM, Chuck Anderson c...@wpi.edu wrote:
  liblockfile is installed with CentOS 7 and it gets updated by EPEL 7.
  Is that supposed to happen?
 
 No it's not. Added the maintainer [1] who requested it to cc: so he
 can outline why but I'm not sure why our requests are just being
 approved by the process-git-requests process.
 
 Peter
 
 [1] https://bugzilla.redhat.com/show_bug.cgi?id=601577

Ugh. Good catch! It looks like liblockfile was added to EPEL7 by
accident.

I opened a ticket[1].

Since that package didn't change for a long time, I wouldn't expect any
real difference between those two.

Matthias

[1] https://fedorahosted.org/rel-eng/ticket/6107
-- 
Matthias Runge mru...@matthias-runge.de
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel

Re: F22 System Wide Change: Django 1.8

[Matthias Runge]

On 27/01/15 11:51, Miloslav Trmač wrote:
 Hello,
 ** A build containing latest Django will be pushed to f22 branch late in dev
 cycle. If we decide not to push Django-1.8, nothing will be broken.
 ** Django 1.8 final release is expected around April 1st, 2015: [2]
 
 Note that the “Change checkpoint: completion deadline (testable)” is on Feb 
 24; do you plan to have a beta version built by then?
 Mirek
 
According to schedule[1], the beta is planned for Feb 16th.

[1] https://code.djangoproject.com/wiki/Version1.8Roadmap

So: yes!

Matthias

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Flash plugin 0-day vulnerability in the wild

[Matthias Runge]

On 23/01/15 16:59, Andrew Lutomirski wrote:


 sandbox -X will also add more protection.
 
 Unless I'm mistaken, sandbox -X hasn't worked in almost a year.
 
I gave it a try;

sandbox -X
/usr/bin/sandbox:
/usr/sbin/seunshare is required for the action you want to perform.


Sadly, a naive (and not so naive) dnf reporequery, repoquery and yum
search did not show the right dep.

Wild guessing solved it for me:
dnf install policycoreutils-sandbox

And it works (for me) now.

I would expect at least a dependency here added.

Matthias
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: amending the new package process

[Matthias Runge]

On 22/01/15 15:17, Zbigniew Jędrzejewski-Szmek wrote:
 On Thu, Jan 22, 2015 at 03:08:28PM +0100, Mathieu Bridon wrote:
 On Thu, 2015-01-22 at 14:49 +0100, Zbigniew Jędrzejewski-Szmek wrote:
 Unfortunately review swaps don't work for new packagers, before they are
 sponsored. They are encouraged to do informal reviews, but those reviews
 don't carry formal weight. I propose to change this, and allow non-sponsored
 packagers to do formal reviews, except that an actual packager with review
 rights has to ack the review.

 This is exactly what informal reviews are.
 I have never seen it work like that. If it wasn't clear, I think the
 (official) packager should be able to just say: I approve this review.
 If the review is bothed, the onus should fall on both parties. Currently
 the (offical) packager takes all the responsibility.
 
I think, this is an misconception.

We should encourage people, to do more informal reviews. The thing is,
it's not that easy to dive deep into material here. Simply running
fedora-review and copy/pasting stuff into bz is a starter.

Each informal review helps to identify potential issues with a package.
On the other side, they will serve as learning material for the new
packager. Reading others code helps to improve your own.

About responsibility: both are responsible now. Of course, the package
owner or point of contact is the person getting bz emails etc, but the
reviewer is the person letting issues get into SCM.

Matthias
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: amending the new package process

[Matthias Runge]

On 21/01/15 11:49, Nikos Mavrogiannopoulos wrote:

 I don't have a solution to bring extra resources to reviewing (which
 will be the ideal), but I'd like to propose an amendment to allow
 bringing packages even if no reviewers are available (the typical case).
 
 Step 6: ... If the proposed package is not reviewed for 2 months, the
 package must be reviewed by the submitter, and a git module with the
 master branch will be approved.
 
Ugh,

thank you for trying to address our way-too-long review queue.

I agree, the submitter should review their own submission, but this
review should be ideally done before sending a package up for review
through a second pair of eyes.

Let's make an example, a submitter puts up a review containing
copyrighted material; this should be caught during review process. Due
the submitter will think, everything is alright, he will check that
material into SCM and we'll start distributing that.

Matthias


-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Unresponsive maintainer : kanarip

[Matthias Runge]

On 09/01/15 08:40, Yanko Kaneti wrote:
 

 - I beleive this package is not suitable for an LTS release, so I'll 
 block it - is just hubris.

There are some fast moving packages out there, which are not suitable
for long running releases.

Of course, you're welcome to continue to support them after upstream
stopped bug fixing and security fixes. Backporting of bug fixes from
newer releases included.

Matthias


-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: How many users does Fedora have?

[Matthias Runge]

On 01/12/14 13:10, Alec Leamas wrote:

 So we come back to the question: is any number better than no number
 at all?
 Even to get a trend?

 Yes, I think so. Even a bad number can be used for trends and comparisons.
 
 That said, let's not limit this discussion to the download counter
 concept. There are other approaches, perhaps some kind of reporting app
 which send reports on installed sw to a central server, like the abrt
 thing. Or something else, which I cannot imagine.

In the old days, we used to have a service like smolt, to collect
hardware data. The installer asked for participation in this service
after install. IMHO that was a service, reporting every month or so.

Debian has popcon[1], to collect statistics.

One could even argue: when fedora already knows, what I have installed,
it may be nice to get a reminder to update packages, when there is a
known security issue. Of course, that needs to be opt-in, but it may be
a nice service.

Matthias


[1] http://popcon.debian.org/
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: How many developers Fedora has

[Matthias Runge]

On Sat, Nov 29, 2014 at 11:56:27AM +, Pádraig Brady wrote:
 On 29/11/14 09:44, Ali AlipourR wrote:
  Hi
  Is there any statistics about How many developers Fedora has?
 
 Considering just packages:
 https://www.openhub.net/p/fedora-packages
 
 Of course there are many more behind the scenes of the programs themselves.

Interesting, although I believe, we had more than 35 contributors in
September or 39 in October.

For example, I made am listed with 78 commits all time[1]. I believe, based
on badges.fp.o[2], I have more than 400 SCM commits. If something like a
package build, or package review counts as well, those figures must be
about factor 10 too small.

The last numbers I remember is, we have around 1200 packagers, some
more, some less active[3].
When someone wants to follow, what's going on in fedora, one could watch
fedmsg[4].

[1]
https://www.openhub.net/p/fedora-packages/contributors/17250736446977
[2] https://badges.fedoraproject.org/user/mrunge
[3] https://admin.fedoraproject.org/pkgdb/stats/
[4] https://apps.fedoraproject.org/datagrepper/raw
 -- 
 devel mailing list
 devel@lists.fedoraproject.org
 https://admin.fedoraproject.org/mailman/listinfo/devel
 Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

-- 
Matthias Runge mru...@matthias-runge.de
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Removing packages that have broken dependencies in F21 tree

[Matthias Runge]

On 13/11/14 14:33, Richard W.M. Jones wrote:
 On Thu, Nov 13, 2014 at 03:20:03PM +0200, Kalev Lember wrote:
 ocaml-pa-do
 
 This package was rewritten upstream.  I've not tried to package the
 new version.  The version packaged in Fedora Rawhide is orphaned, so I
 guess you may as well remove the F21 package too (unless someone else
 wants to jump in and fix this).
 
 transifex
 
 Huh??  If this is the package I'm thinking of, it's pretty important
 to many other packages.
yes, that's the package. But IMHO transifex became closed source, and
last code change was about 2 years ago; since then, django changed quite
a bit.

Matthias
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Suspend/resume broken on Lenovo laptops (Fedora 21 beta)

[Matthias Runge]

On 12.11.2014 19:12, valent.turko...@gmail.com wrote:


I'm also using luksCrypt! So this is the crucial info! How did you
resolv your issue? Is there a quick fix for now and what needs to be
fixed in Fedora so that Fedora 21 has this issue fixed out of the
box?


I am using lukscrypt as well, but it works for me.

Are you using it docked, suspend, undock, and resume afterwards?
I see a blank screen after switching between external and internal 
screens. IMHO it's already a reported issue.


Matthias
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Attempting to contact unresponsive maintainer - jomara

[Matthias Runge]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mon, Nov 10, 2014 at 10:23:35AM -0700, Kevin Fenzi wrote:
 If you have a way to contact this maintainer, please let them
 know that we'd appreciate knowing what to do with their packages.
 Thanks!
 
 * jomara - former email address jom...@redhat.com
   https://admin.fedoraproject.org/pkgdb/packager/jomara/
 
 Point of contact:
 
 openstack-tuskar -- A service for managing OpenStack deployments
 ( master f21 f20 epel7 ) 
 
 openstack-tuskar-ui -- The UI component for Tuskar ( master f21 f20
 epel7 ) 
 
 python-soaplib -- A python library for writing and calling soap web
 services ( master f21 f20 f19 el6 ) 
 
 python-tuskarclient -- Python client for the Tuskar API ( master f21
 f20 epel7 ) Co-maintainer:
 
 python-flask-babel -- Adds i18n/l10n support to Flask applications
 ( epel7 ) 
 python-pyghmi -- Python General Hardware Management Initiative (IPMI
 and others) ( epel7 )

Oh yes!

Accidentally, we didn't solve this earlier.

The plan, discussed with jomara was, Jason Rist (FAS: jrist) should take
over these packages (and probably python-soaplib as well). I sponsored him
some time ago for exactly that reason and will help him through cliffs and
shallow waters here as best as I can.

I added myself as co-maintainer to openstack-tuskar, openstack-tuskar-ui
and python-tuskarclient.

 If we don't hear anything in a week, we will be setting the point of
 contact on these packages to orphan. 

I don't see a reason, why we need to wait for a week here, and I think,
we can solve this situation immediately.

Matthias

- -- 
Matthias Runge mru...@matthias-runge.de
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJUYRkUAAoJEOnz8qQwcaIWSXEH/3eK+tJ+elWynT8E8WkE02rD
K1WZ6bFqhwdJHnBxc6QfJHy+H1oinetZyagePVZ4cRMkqpYQMdQ1VQNpe00Pv/Q4
fmuWSKjZYDBeo9PYDCQDHJ8FEzzroU1j2S+expR0yMIcyfNTH5dYXQi9H1nrA6go
fSPuzyLFLgpdoIs0DjUvNn+Ajx7ga9zvKOey4C++DztCH1KMQSdmJWVL6wuCjeK8
wjlew3gWIyADAKHcKiaQ/t55EJ2K4PBF1PhizoA35YDzDI5fmu6AEnT4CfnnYKHP
rdlffo/uskfsc4EHyjbDodRqNAPl+SQ0AznSXAIyFj443yRRUwXq5Roir1PSSZ0=
=5upU
-END PGP SIGNATURE-
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Django-1.7 for Fedora 21

[Matthias Runge]

On 16/10/14 15:32, Stephen Gallagher wrote:

 There are no Django applications that are part of the install sets of
 any of the Products or Spins so far as I am aware, so the risk to the
 Project deliverable dates would be minimal. I'd suggest bringing it to
 FESCo for a more complete risk-analysis, but I'd argue that we'd be
 better off shipping python-django as 1.7 and also the python-django16
 package in Fedora 21.

I opened a ticket:

https://fedorahosted.org/fesco/ticket/1357

Matthias
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Django-1.7 for Fedora 21

[Matthias Runge]

Hello,

in Fedora 21, we have Django-1.6. Django-1.7 was released a few weeks
ago. As we're in feature freeze, but still pre-beta. I'd like to ask for
opinions, if an upgrade to Django-1.7 would be still acceptable.

I have a copr available containing Django-1.7 [1]

Thoughts?

Matthias

[1] https://copr.fedoraproject.org/coprs/mrunge/django-1.7/
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Django-1.7 for Fedora 21

[Matthias Runge]

On 16/10/14 14:25, Rahul Sundaram wrote:
 Hi
 
 On Thu, Oct 16, 2014 at 7:37 AM, Matthias Runge wrote:
 
 Hello,
 
 in Fedora 21, we have Django-1.6. Django-1.7 was released a few weeks
 ago. As we're in feature freeze, but still pre-beta. I'd like to ask for
 opinions, if an upgrade to Django-1.7 would be still acceptable.
 
 I have a copr available containing Django-1.7 [1]
 
 Thoughts?
 
 
 Does it bring any substantial benefits?  Does it break existing apps?
 
Two things to be considered:

- Django-1.6 will get out of maintenance when F21 is still released
(probably in March 2015)

- when running an app, the following lines in your wsgi file need to be
placed or replaced:

from django.core.wsgi import get_wsgi_application
application = get_wsgi_application()

instead of whatever was there earlier to define the application.


Matthias
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Broken dependencies in F21

[Matthias Runge]

On 16/10/14 14:40, Kalev Lember wrote:
 Hi all,
 
 We seem to have a number of broken dependencies in F21 that have gone
 unfixed for a quite some time. Not sure what's up with them; the
 maintainers are supposed to get daily notifications to make sure these
 don't go unnoticed.
 
 Does anyone have ideas how to deal with these packages?
 
 I wonder if it would make sense to just drop them before F21. Having
 broken dependencies basically means that the packages are completely
 broken and cannot be installed at all. Not much point in shipping those
 in the repositories ...
 
 Any ideas how to deal with this?
 
openslides:
Needs an update to latest version, and a few reviews for currently
unpackaged deps. I didn't had the time for it

django-recaptcha:
I'm not the maintainer here. IMHO we just can drop it right now.

pipelight-selinux:
a leftover from pipelight removal. Should be dropped ASAP.

python-askbot-fedmsg:
askbot was retired, so should this one.

Matthias
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: EPEL Deprecated Django 1.5 in

[Matthias Runge]

On Wed, Oct 01, 2014 at 01:28:04PM +0300, Dionysis Grigoropoulos wrote:
 Hello,
 
 as far as I can see, EPEL 7 currently provides packages `python-django`
 and `python-django15` being versions 1.6.5 and 1.5.6 respectively. EPEL
 6 provides `python-django15` and `Django14` being 1.5.6 and 1.4.14.
 
 According to the Django documentation [1], since version 1.7 was
 released, version 1.5 won't receive security updates anymore. Wouldn't
 it be better to remove python-django15 from both repos and add 1.4
 (current LTS which will be supported at least until March of 2015) to
 EPEL 7 and 1.6 to epel 6?

Thank you for the heads-up.

I recently retired python-django15 from Fedora 21+, and I should do the
same ASAP for EPEL6 and EPEL7 as well.

(THIS IS THE ANNOUNCEMENT ABOUT REMOVAL in about two weeks.)

About adding Django14 to EPEL7: Since there is currently Django-1.6,
which is supported until March 2015 as well, I don't see any pro to add
another Django version. The other reason is: having two versions in the
same release is just a pain; I'd try to avoid this; they need to be
installable in parallel. We had that, it didn't work very well.

Does this make any sense?
Matthias
-- 
Matthias Runge mru...@matthias-runge.de
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel