Re: Picking up protobuf

[Neil Hanlon]

On 18.04.2024 12:42, Michel Lind wrote:

Hi Neil,

On 4/18/24 06:37, Neil Hanlon wrote:

thanks Michel!

I'd be happy to help maintain if you would like assistance.


There are 3 previous maintainers, plus the EPEL bugzilla is overridden to Peter 
Lemenkov (cc:ed) who is not in the ACL yet.

So I'd rather take things slow and not make unilateral ACL changes. Any PR 
welcome though! (And I'll try and sort out
existing issues and PRs in between conference prep).


100% agree. I'll keep an eye on the progress and feel free to ping if you need 
a hand with anything.

--Neil


Best regards,

--
_o) Michel Lind
_( ) identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2








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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Picking up protobuf

[Neil Hanlon]

thanks Michel!

I'd be happy to help maintain if you would like assistance.


On Wed, Apr 17, 2024, 22:52 Michel Lind  wrote:

> Hi all,
>
> protobuf was recently orphaned without any announcement to this list.
>
> I've picked it up since et depends on it.
>
> Best regards,
>
> --
>  _o) Michel Lind
> _( ) identities:
> https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2
> --
> ___
> 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
>
--
___
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: [EPEL-devel] certbot Update From 2.6.0 to 2.9.0 in EPEL9

[Neil Hanlon]

thanks, Jonathan!

On Sat, Mar 9, 2024, 13:06 Jonathan Wright via epel-devel <
epel-de...@lists.fedoraproject.org> wrote:

> Hello,
>
> I'm updating certbot from 2.6.0 to 2.9.0 in EPEL9 [1].  This contains one
> minor, potentially breaking changes though I don't expect it to impact
> anyone:
>
> NamespaceConfig now tracks how its arguments were set via a dictionary,
> allowing us to remove a bunch
> of global state previously needed to inspect whether a user set an
> argument or not.
>
> Full release notes are available at
> https://github.com/certbot/certbot/releases
>
> This update is being done per the permanent upgrade policy exception
> granted by FESCo. [1]
>
> As a side note I plan to update certbot in EPEL8 as far as dependencies
> will allow, in the near future.
>
> 1. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-226fa082a4
> 2.
> https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#_other_packages
>
> --
> Jonathan Wright
> AlmaLinux Foundation
> Mattermost: chat 
> --
> ___
> epel-devel mailing list -- epel-de...@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-de...@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
--
___
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: looking for a maintainer for package remind

[Neil Hanlon]

Hey Kurt,

It took a bit, but `remind` should be coming back to Fedora shortly -- I 
submitted an update for f39 last week:

https://bodhi.fedoraproject.org/updates/FEDORA-2024-459cdffd98

Best,
Neil

On 26.10.2023 18:34, Kurt Keller wrote:

Hi Neil,

Thanks a lot, much appreciated.

Kurt

On Wed, Oct 25, 2023 at 2:04 PM Neil Hanlon  wrote:


Hi Kurt,

I'd be happy to help maintain this with you. I've actually been looking
for something like Remind for a while now!

Best,
Neil


On Wed, Oct 25, 2023, 07:33 Kurt Keller 
wrote:


Remind (https://dianne.skoll.ca/projects/remind/) is a terminal based
reminder utility (with optional Tk GUI frontend). It's kind of a
supercharged version of the calendar utility.

Remind has been in the fedora packages for many years, but the last
update to it has happened in fc24 and after fc29 it got orphaned and
disappeared. Installing the fc29 RPM on current fedora versions still works
flawlessly but is, by now, somewhat out of date.

I'd like to see the package back in the software channels and have
updated the SPEC file for fc38 and version 04.02.06 of remind and created a
pull request (https://src.fedoraproject.org/rpms/remind/pull-request/2).

A request to unretire the package has been made (
https://pagure.io/releng/issue/11740). Doing so I learnt a bit more
about the fedora software package world. I'm happy to help and support a
package maintainer keeping things up to date and learn more along the way,
but taking on the role as maintainer of the package is over the top of my
head and my current abilities. So I'd like to ask if somebody was willing
to take over the role as official maintainer for the remind package.

Thanks,

Kurt

PS:
An update to the recently released version 04.02.07 is already waiting in
my fork:

https://src.fedoraproject.org/fork/kkeller/rpms/remind/commits/remind_04.02.07-0.fc38
but unless somebody is willing to take over maintainership I don't see much
use creating another pull request.
___
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


___
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



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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[EPEL-devel] Re: Orphaning python-mistune on EPEL

[Neil Hanlon]

On 11.01.2024 11:23, Miro Hrončok wrote:



On 10. 01. 24 22:16, Michel Lind wrote:

Hi Miro,

On Wed, Jan 10, 2024 at 02:51:33PM +0100, Miro Hrončok wrote:

Hello,

I recently took python-mistune in Fedora.
I am not interested in maintaining it in EPEL.

It is branched for epel7, epel8 and epel9.

@epel-packagers-sig is a collaborator so I assume somebody built this in
epel9 without taking responsibility.

There is a low impact CVE: https://bugzilla.redhat.com/show_bug.cgi?id=2112231

If somebody want to maintain it, let me know and I'll make you the epel
point of contact.


Please mark me as the EPEL POC.


Already marked Neil.

Neil, let me know if I should change it.


No worries -- Michel and I discussed this in the EPEL steering committee 
meeting yesterday and will be working on this
together. I think since EPEL-Packagers-SIG already has access, this should be 
sufficient.

Thank you!
--Neil


--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok



signature.asc
Description: PGP signature
--
___
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: Orphaning python-mistune on EPEL

[Neil Hanlon]

On Wed, Jan 10, 2024, 08:51 Miro Hrončok  wrote:

> Hello,
>
> I recently took python-mistune in Fedora.
> I am not interested in maintaining it in EPEL.
>
> It is branched for epel7, epel8 and epel9.
>
> @epel-packagers-sig is a collaborator so I assume somebody built this in
> epel9
> without taking responsibility.
>
> There is a low impact CVE:
> https://bugzilla.redhat.com/show_bug.cgi?id=2112231
>
> If somebody want to maintain it, let me know and I'll make you the epel
> point
> of contact.
>

I'll take this one for epel.

Thanks!

Neil

>
> --
> Miro Hrončok
> --
> Phone: +420777974800
> IRC: mhroncok
> --
> ___
> 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 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: unicorn on s390x

[Neil Hanlon]

Hey Mike,

I've forwarded this over to the Linux Distros working group [1] at the Open 
Mainframe Project and am also going to take
a look to see what the deal is.

Best,
Neil

[1] 
https://openmainframeproject.org/our-projects/working-groups/linux-distributions/

On 16.12.2023 16:20, W. Michael Petullo wrote:

I maintain Fedora's unicorn package. This package will not presently
build on s390x, and I am not certain why. The problem seems to have to
do with 128-bit instructions.

I have a tracker bug in Bugzilla:

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

I have also added some commentary to a bug upstream:

https://github.com/unicorn-engine/unicorn/issues/1840

It seems that Ubuntu's package does build on s390x, but I do not see any
patches in their package description that might describe why theirs
builds and ours does not:

https://packages.ubuntu.com/mantic/libunicorn-dev

This leaves me wondering if our s390x build host lacks features present
in the Ubuntu one. I know little about s390x, so this is a stab in the
dark.

Does anyone with s390x experience know what might be going on?

--
Mike

:wq
--
___
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


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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: packaging of nix

[Neil Hanlon]

I would also be happy to help. I use nix fairly often and it'd be nice
to have it in Fedora directly.

Best,
Neil

On Sun, Nov 26, 2023 at 2:58 PM Michel Lind  wrote:
>
> I'd love to comaintain. I'm interested in Nix and Guix, but the latter really 
> needs us to revamp our Guile packaging guidelines to package properly.
>
> Best,
>
> --
> Michel Lind
> --
> ___
> 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
--
___
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: Orphaned packages looking for new maintainers

[Neil Hanlon]

On 20.11.2023 06:21, Neil Hanlon wrote:

On 20.11.2023 12:37, Dominik 'Rathann' Mierzejewski wrote:

On Monday, 20 November 2023 at 10:48, Miro Hrončok 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



   Package  (co)maintainers   Status Change


[...]

python-etcd   orphan   0 weeks ago
python-ironicclient   apevec, openstack-sig, orphan0 weeks ago


It looks like samba depends on these two. Needless to say, a lot of
stuff depends on samba.

python-etcd seems to have no co-maintainers.


I've taken python-etcd, but am looking into what's going on with this package. 
aiui, this should be replaced with
etcd3gw, probably. The upstream for python-etcd hasn't updated in some time, 
save for some spurious updates a few weeks
ago.



python-ironicclient seems to have Alan Pevec and OpenStack SIG as
co-maintainers, so hopefully they will pick it up.


I'm not sure I follow this--where are you seeing that ironicclient is a dep for 
samba? I would imagine that it would be
the other way around.


Oops. I see it now. Nevermind :) -- samba <- gluster <- pcs <- ... <- 
python-ironicclient

I am willing to help with ironicclient if needed.

--Neil


Best,
--Neil


Regards,
Dominik
--
Fedora   https://fedoraproject.org
Deep in the human unconscious is a pervasive need for a logical universe that
makes sense. But the real universe is always one step beyond logic.
  -- from "The Sayings of Muad'Dib" by the Princess Irulan
--
___
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





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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

[Neil Hanlon]

On 20.11.2023 12:37, Dominik 'Rathann' Mierzejewski wrote:

On Monday, 20 November 2023 at 10:48, Miro Hrončok 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



Package  (co)maintainers   Status Change


[...]

python-etcd   orphan   0 weeks ago
python-ironicclient   apevec, openstack-sig, orphan0 weeks ago


It looks like samba depends on these two. Needless to say, a lot of
stuff depends on samba.

python-etcd seems to have no co-maintainers.


I've taken python-etcd, but am looking into what's going on with this package. 
aiui, this should be replaced with
etcd3gw, probably. The upstream for python-etcd hasn't updated in some time, 
save for some spurious updates a few weeks
ago.



python-ironicclient seems to have Alan Pevec and OpenStack SIG as
co-maintainers, so hopefully they will pick it up.


I'm not sure I follow this--where are you seeing that ironicclient is a dep for 
samba? I would imagine that it would be
the other way around.

Best,
--Neil


Regards,
Dominik
--
Fedora   https://fedoraproject.org
Deep in the human unconscious is a pervasive need for a logical universe that
makes sense. But the real universe is always one step beyond logic.
   -- from "The Sayings of Muad'Dib" by the Princess Irulan
--
___
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


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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: looking for a maintainer for package remind

[Neil Hanlon]

Hi Kurt,

I'd be happy to help maintain this with you. I've actually been looking for
something like Remind for a while now!

Best,
Neil


On Wed, Oct 25, 2023, 07:33 Kurt Keller 
wrote:

> Remind (https://dianne.skoll.ca/projects/remind/) is a terminal based
> reminder utility (with optional Tk GUI frontend). It's kind of a
> supercharged version of the calendar utility.
>
> Remind has been in the fedora packages for many years, but the last update
> to it has happened in fc24 and after fc29 it got orphaned and disappeared.
> Installing the fc29 RPM on current fedora versions still works flawlessly
> but is, by now, somewhat out of date.
>
> I'd like to see the package back in the software channels and have updated
> the SPEC file for fc38 and version 04.02.06 of remind and created a pull
> request (https://src.fedoraproject.org/rpms/remind/pull-request/2).
>
> A request to unretire the package has been made (
> https://pagure.io/releng/issue/11740). Doing so I learnt a bit more about
> the fedora software package world. I'm happy to help and support a package
> maintainer keeping things up to date and learn more along the way, but
> taking on the role as maintainer of the package is over the top of my head
> and my current abilities. So I'd like to ask if somebody was willing to
> take over the role as official maintainer for the remind package.
>
> Thanks,
>
> Kurt
>
> PS:
> An update to the recently released version 04.02.07 is already waiting in
> my fork:
>
> https://src.fedoraproject.org/fork/kkeller/rpms/remind/commits/remind_04.02.07-0.fc38
> but unless somebody is willing to take over maintainership I don't see much
> use creating another pull request.
> ___
> 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
>
___
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: New contributor interested in taking maintainership of SWORD, Xiphos, and Bibletime

[Neil Hanlon]

Welcome to Fedora! Glad to have you here.

On 29.09.2023 13:10, Aaron Rainbolt wrote:

Hello, and thanks for your time.

I am a former (and possibly future) Ubuntu and Lubuntu Developer who 
recently started using Fedora on some of my systems. I have about a 
year of experience in Linux distro development from my previous work 
with Lubuntu and Ubuntu. After trying Fedora, I liked it so much I 
decided I wanted to contribute to it, and discovered that the SWORD 
package had become orphaned and retired due to a bug in its Python 
bindings. As I use SWORD and programs it depends on in my day-to-day 
work, I decided I'd like to try to fix SWORD and become its 
maintainer.


Over the last few days I've worked to get the SWORD package into a 
usable and policy-compliant state, including:


* Fixing the Python-related bug
* Updating the packaging to comply with the current Fedora Packaging 
Guidelines

* Doing a full license audit of the SWORD code
* Clarifying the licensing of various files with upstream
* Asking for one non-free component to be relicensed under a 
Fedora-compatible license (a request which was granted)

* Repacking the upstream tarball to remove optional non-free components

After discussion with the SWORD developers, I found that the original 
maintainer of SWORD in Fedora also maintained Xiphos and Bibletime, 
two applications which depend on SWORD and are closely related to it. 
For this reason, I would like to become the maintainer of all three 
ultimately, though for the moment I'm only actively pursuing 
maintainership of SWORD since it's the only package that needs help at 
the moment.


Depending on how things go, I also am interested in assisting with the 
development of Fedora LXQt Spin, as it is quite similar to Lubuntu, a 
project I worked closely with for about a year.


I hope I can be valuable to the Fedora community! Thanks for your 
help, and have a great day!

___
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


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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaning packages

[Neil Hanlon]

I've found some folks interested in libmodsecurity and friends. They are not a 
packager yet but I will work on mentoring
and getting them sponsored.

On 23.06.2023 00:27, Neil Hanlon wrote:

I've taken aria2 and thc-ipv6.

Thank you for your contributions, Othman!

--Neil

On 22.06.2023 18:48, Othman Madjoudj wrote:

Hello,

Please note that I've orphaned by packages, list in the end of the message.

Best regards
-Othman


rpms/aria2
rpms/hydra
rpms/libmodsecurity
rpms/lynis
rpms/mod_limitipconn
rpms/mod_qos
rpms/mod_ruid2
rpms/mod_security3
rpms/mod_security_crs
rpms/python-paramiko
rpms/thc-ipv6
rpms/unhide



___
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







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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[EPEL-devel] Re: Orphaning packages

[Neil Hanlon]

I've found some folks interested in libmodsecurity and friends. They are not a 
packager yet but I will work on mentoring
and getting them sponsored.

On 23.06.2023 00:27, Neil Hanlon wrote:

I've taken aria2 and thc-ipv6.

Thank you for your contributions, Othman!

--Neil

On 22.06.2023 18:48, Othman Madjoudj wrote:

Hello,

Please note that I've orphaned by packages, list in the end of the message.

Best regards
-Othman


rpms/aria2
rpms/hydra
rpms/libmodsecurity
rpms/lynis
rpms/mod_limitipconn
rpms/mod_qos
rpms/mod_ruid2
rpms/mod_security3
rpms/mod_security_crs
rpms/python-paramiko
rpms/thc-ipv6
rpms/unhide



___
devel mailing list -- de...@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/de...@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue







signature.asc
Description: PGP signature
___
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: What is Fedora?

[Neil Hanlon]

On Fri, Jun 23, 2023, 18:41 Josh Boyer  wrote:

>
>
> On Fri, Jun 23, 2023, 3:20 PM Michael Catanzaro 
> wrote:
>
>> On Fri, Jun 23 2023 at 01:27:24 PM -0400, Josh Boyer
>>  wrote:
>> > Which means equivalent fixes are in CentOS Stream and anyone wanting
>> > to recreate exactly what is in RHEL is welcome to backport that code
>> > from CentOS Stream or upstream.
>>
>> Yes, but that's going to be pretty hard to do if you cannot see what
>> needs to be backported because you don't have a Customer Portal
>> subscription. :)
>>
>
> Yes, the work you do is not easy.
>
> In this particular case, there are two CVEs fixed somewhere in the
>> middle of maybe 100 other upstream changes, and the correspondence
>> between CVE vs. upstream commit is intentionally not public to
>> discourage distros from backporting individual security fixes. (It's
>> not a smart idea. Only 5% of WebKit security bugs get CVEs. I sometimes
>> do security backports for RHEL anyway for regulatory rather than
>> security reasons.) Anyway, to figure out what to backport in order to
>> match what's in RHEL, you'd have to either somehow get access to the
>> RHEL SRPM, or else email me and ask what to do.
>>
>
> Or build up a knowledge of the code base that allows one to do it
> themselves.
>
> I don't really have any strong opinion about this change. Just pointing
>> out that it's going to be effectively impossible to reverse-engineer
>> RHEL from CentOS Stream. Let's not pretend that's realistic. Rebuilders
>> are going to need to get copies of the RHEL SRPMs somehow if they want
>> to match RHEL, and they do.
>>
>
> I don't think it's impossible.  I think it requires work, skill, and
> investment.
>

if only that time, skill, and investment wasn't doing useless re-work, and
could be spent on contributing to Stream.


> josh
> ___
> 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
>
___
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: Orphaning packages

[Neil Hanlon]

I've taken aria2 and thc-ipv6.

Thank you for your contributions, Othman!

--Neil

On 22.06.2023 18:48, Othman Madjoudj wrote:

Hello,

Please note that I've orphaned by packages, list in the end of the message.

Best regards
-Othman


rpms/aria2
rpms/hydra
rpms/libmodsecurity
rpms/lynis
rpms/mod_limitipconn
rpms/mod_qos
rpms/mod_ruid2
rpms/mod_security3
rpms/mod_security_crs
rpms/python-paramiko
rpms/thc-ipv6
rpms/unhide



___
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




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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[EPEL-devel] Re: Orphaning packages

[Neil Hanlon]

I've taken aria2 and thc-ipv6.

Thank you for your contributions, Othman!

--Neil

On 22.06.2023 18:48, Othman Madjoudj wrote:

Hello,

Please note that I've orphaned by packages, list in the end of the message.

Best regards
-Othman


rpms/aria2
rpms/hydra
rpms/libmodsecurity
rpms/lynis
rpms/mod_limitipconn
rpms/mod_qos
rpms/mod_ruid2
rpms/mod_security3
rpms/mod_security_crs
rpms/python-paramiko
rpms/thc-ipv6
rpms/unhide



___
devel mailing list -- de...@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/de...@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue




signature.asc
Description: PGP signature
___
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

Orphaned Package - whatsup

[Neil Hanlon]

Hi all,

As per the orphaned project process, I am notifying the list that I will be 
claiming `whatsup`[1] as it is a requirement
for an open bugzilla[2] for providing pdsh[3] in EPEL 9. While I am primarily 
interested in EPEL 9, I'll work to keep it
updated and working in Fedora, as well.

Best,
Neil

[1] https://src.fedoraproject.org/rpms/whatsup
[2] https://bugzilla.redhat.com/show_bug.cgi?id=2188195
[3] https://bugzilla.redhat.com/show_bug.cgi?id=2070427


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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: F38 proposal: Rpmautospec by Default (System-Wide Change proposal)

[Neil Hanlon]

On Mon, Feb 6, 2023, 12:44 Vít Ondruch  wrote:

> I have just learned the hard way that `fedpkg import` does not work with
> `rpmautospec` and that is show stopper for me. I have reported ticket here:
>
> https://pagure.io/rpkg/issue/655


I ran into this myself and found its a bit less of an issue than it seems.
If you build the srpm with mock, the srpm will work with fedpkg import.

Confusingly, srpms resulting from fedpkg mockbuild are not built with mock,
but with rpmbuild directly, which results in this error.


>
> And won't try rpmautospec again until this is resolved.


>
> Vít
>
>
> Dne 30. 12. 22 v 20:01 Ben Cotton napsal(a):
> > https://fedoraproject.org/wiki/Changes/Rpmautospec_by_Default
> >
> > This document represents a proposed Change. As part of the Changes
> > process, proposals are publicly announced in order to receive
> > community feedback. This proposal will only be implemented if approved
> > by the Fedora Engineering Steering Committee.
> >
> > == Summary ==
> > Rpmautospec (`%autorelease` and `%autochangelog`) is recommended as
> > the default approach.
> > Packaging Guidelines and other documentation are adjusted to describe
> > this approach first.
> > Various tools that provide spec file templates are adjusted.
> >
> > == Owner ==
> > * Name: [[User:Nphilipp| Nils Philippsen]], [[User:Zbyszek| Zbigniew
> > Jędrzejewski-Szmek]]
> > * Email: nphilipp - at - redhat.com, zbyszek - at - in.waw.pl
> >
> >
> > == Detailed Description ==
> >
> > {{admon/note|Brief reminder about rpmautospec|
> > The spec file contains:
> > 
> > Version: 1.2.3
> > Release: %autorelease
> > ...
> > %changelog
> > %autochangelog
> > 
> > Rpmautospec uses git history. Whenever the package is built
> > (`.src.rpm` is generated), rpmautospec tooling will replace the
> > `%autorelease` macro with the number of commits since the last commit
> > that changed the `Version` field, and the `%autochangelog` macro with
> > a text generated from `git log`.
> > For details see the
> > [https://docs.pagure.org/fedora-infra.rpmautospec/principle.html
> > docs].
> > }}
> >
> > Rpmautospec has been deployed in Fedora since F35
> > ([[Changes/rpmautospec]]), and 3423/23045 packages use it (15%).
> > But it is still a "second-class citizen": most documentation doesn't
> > mention it, and many packagers know that it exists but don't use it in
> > their packages. We think that it's reasonable to switch to
> > `%autorelease`+`%autochangelog` for almost all packages and that
> > Packaging Guidelines and various packaging howtos should recommend
> > that approach to packagers. The "traditional" approach of
> > manually-managed `Release` and `%changelog` will remain valid and will
> > be documented as a fallback.
> >
> > This change is targeted at Fedora 38, but it will actually apply to
> > all releases. The goal is to update the Packaging Guidelines and other
> > prominent documentation and tools now, and other docs and tools
> > possibly at a later time. Changing packages is out of scope.
> >
> > It is worth mentioning that `rust2rpm` uses
> > `%autorelease`+`%autochangelog` since a few releases, so most rust
> > packages have switched. (Generally, rust spec files are recreated
> > using the generator for each new version, so the switch would happen
> > whenever a new version is packaged unless the packager opts out.)
> >
> > == Feedback ==
> >
> > * Thread on fedora-devel in August 2022:
> > [
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/T6J2WGIMRCTW77QTH4D7HPNS6KUGDQOQ/
> > rpmautospec by default]
> > ** open issues: a bunch have been fixed.
> > ** maintenance: Nils will add some co-maintainers.
> > ** compatibility with rpmdevtools, fedpkg/rpkg, fedora-review: see
> > Scope section.
> >
> > == Benefit to Fedora ==
> > Various packaging workflows become smoother for packagers and
> contributors:
> >
> > * packagers don't need to touch the `Release` field on updates
> > * packagers describe changes just once in the git commit message, the
> > `%changelog` entry is autogenerated
> > * patches to the spec file can be cherry-picked between branches
> > without trivial conflicts
> > * pull requests on src.fedoraproject.org can be merged without trivial
> conflicts
> > * in workflows that regenerate the spec file (rust2rpm, pip2rpm, …)
> > `%changelog` section doesn't need to be copied over
> >
> > == Scope ==
> > * Proposal owners:
> > ** provide pull requests to Packaging Guidelines and other docs to
> > make `%autorelease`+`%autochangelog` the default
> > ** implement fixes for issues reported by packagers
> > ** make semi-regular releases of rpmautospec
> > ([
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/K5EA5OGRX2BCZ353C7S4MQVZTSH2BH63/
> > 0.3.1 was released on November 17th, and should be deployed to
> > production in about two weeks])
> >
> > * Other developers:
> > ** provide pull requests to other docs as appropriate
> > ** accept the 

Self Introduction: Neil Hanlon

[Neil Hanlon]

Hi folks!

My name is Neil Hanlon and I was recently sponsored into the packager's group 
by Michel Salim, adding python-sdnotify
[1] to Fedora and EPEL. sdnotify is a dependency for some other packages I hope 
to contribute to Fedora.

I began working with Linux in my teens and over the past decade or so have been 
contributing to open source in some
manner. In 2020, I got involved with the Rocky Linux project doing 
infrastructure work and slowly learning how to
_really_ package RPMs (i.e., not with fpm [2] ;) ). 


In the past I've used and contributed a bit to projects like Foreman and 
Katello, and currently work to maintain Rocky
Linux in the OpenStack-Ansible projects. My interests are mostly around 
infrastructure and cloud/performance, but I have
a background in Networking and like to think of myself as an IPv6 zealot^W 
enthusiast.

I'm looking forward to getting to know more of the Fedora community, and am 
thankful for the warm welcome I've received
so far. I'll also be at CentOS Connect and FOSDEM next week, so if you're 
there, it would be great to meet folks in
person :)

Best,
Neil

[1] https://bugzilla.redhat.com/show_bug.cgi?id=2152757
[2] https://github.com/jordansissel/fpm

--
GPG fingerprint: 0xEE8842F529546560


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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: F38 proposal: Shorter Shutdown Timer (System-Wide Change proposal)

[Neil Hanlon]

if you have persistent Journaling enabled, you'll find them in your last
boot log

On Fri, Dec 23, 2022, 08:55 Mattia Verga via devel <
devel@lists.fedoraproject.org> wrote:

> Il 23/12/22 15:48, Zbigniew Jędrzejewski-Szmek ha scritto:
> >
> > Yeah. We added printing of a lot of information in
> >
> https://github.com/systemd/systemd/commit/3889fc6fc347f0e12070f7b873d065508c8df816
> :
> >
> > Example output:
> >
> >   Stopping user@1000.service...
> > [  OK  ] Stopped dracut-shutdown.service.
> > [  OK  ] Stopped systemd-logind.service.
> > [  OK  ] Stopped systemd-logind.service - User Login Management.
> > [* ] Job user@1000.service/stop running (2s / 2min): (1 of 2) User
> job slowstop.service/stop running (1s / 1min 30s)...
> > [***   ] Job user@1000.service/stop running (3s / 2min): (2 of 2) User
> job slowstop2.service/stop running (2s / 1min 30s)...
> > [   ***] Job user@1000.service/stop running (4s / 2min): (1 of 2) User
> job slowstop.service/stop running (4s / 1min 30s)...
> > [ *] Job user@1000.service/stop running (5s / 2min): (1 of 2) User
> job slowstop.service/stop running (5s / 1min 30s)...
> > [   ***] Job user@1000.service/stop running (6s / 2min): (2 of 2) User
> job slowstop2.service/stop running (6s / 1min 30s)...
> > [***   ] Job user@1000.service/stop running (8s / 2min): (1 of 2) User
> job slowstop.service/stop running (7s / 1min 30s)...
> > [***   ] Job user@1000.service/stop running (10s / 2min): (2 of 2) User
> job slowstop2.service/stop running (9s / 1min 30s)...
> > [  *** ] Job user@1000.service/stop running (11s / 2min): (1 of 2) User
> job slowstop.service/stop running (10s / 1min 30s)...
> > [ *] Job user@1000.service/stop running (12s / 2min): (2 of 2) User
> job slowstop2.service/stop running (12s / 1min 30s)...
> > [   ***] Job user@1000.service/stop running (13s / 2min): (1 of 2) User
> job slowstop.service/stop running (13s / 1min 30s)...
> > [***   ] Job user@1000.service/stop running (15s / 2min): (2 of 2) User
> job slowstop2.service/stop running (14s / 1min 30s)...
> > [* ] Job user@1000.service/stop running (15s / 2min): (2 of 2) User
> job slowstop2.service/stop running (14s / 1min 30s)...
> > [***   ] Job user@1000.service/stop running (16s / 2min): User job
> slowstop.service/stop running (16s / 1min 30s)...
> > [   ***] Job user@1000.service/stop running (18s / 2min): User job
> slowstop.service/stop running (17s / 1min 30s)...
> > [ *] Job user@1000.service/stop running (19s / 2min): User job
> slowstop.service/stop running (18s / 1min 30s)...
> > [   ***] Job user@1000.service/stop running (20s / 2min): User job
> slowstop.service/stop running (19s / 1min 30s)...
> > [* ] Job user@1000.service/stop running (22s / 2min): User job
> slowstop.service/stop running (22s / 1min 30s)...
> > [**] Job user@1000.service/stop running (30s / 2min): User job
> slowstop.service/stop running (29s / 1min 30s)...
> > [   ***] Job user@1000.service/stop running (32s / 2min): User job
> slowstop.service/stop running (31s / 1min 30s)...
> > [ *] Job user@1000.service/stop running (33s / 2min): User job
> slowstop.service/stop running (32s / 1min 30s)...
> > [   ***] Job user@1000.service/stop running (34s / 2min): User job
> slowstop.service/stop running (33s / 1min 30s)...
> > [**] Job user@1000.service/stop running (37s / 2min): User job
> slowstop.service/stop running (36s / 1min 30s)...
> > [  *** ] Job user@1000.service/stop running (41s / 2min): User job
> slowstop.service/stop running (41s / 1min 30s)...
> > [  OK  ] Stopped user@1000.service - User Manager for UID 1000.
> >   Stopping user-runtime-dir@1000.service - User Runtime
> Directory /run/user/1000...
> > [  OK  ] Unmounted run-user-1000.mount - /run/user/1000.
> > [  OK  ] Stopped user-runtime-dir@1000.service - User Runtime Directory
> /run/user/1000.
> >
> > Futher ideas how to improve things are welcome… But I think that right
> now we
> > report enough to narrow things down to system or user service that is
> blocking
> > shutdown.
> >
> > Zbyszek
>
> Is that output available in any log at the next system startup? I
> usually hit the power button and then run away, but I would like to
> check if anything went slow when I restart my PC.
>
> Mattia
>
> ___
> 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
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: