Re: F41 Change Proposal: Replace Redis with Valkey (system-wide)

[Jonathan Wright via devel]

Uh no?  There's nothing headed to any Fedora release that will replace or
touch redis in any way.  The "obsoletes" is commented out in the spec and
non-functional, it's only there for note/intent purposes depending on what
comes of this change proposal.

If I mistakenly pushed something somewhere that would touch redis in any
way please point me to it and I'll fix it immediately.

On Fri, Apr 19, 2024 at 12:01 AM Nathan Scott  wrote:

> On Fri, Apr 19, 2024 at 2:29 PM Maxwell G  wrote:
> > On Fri Apr 19, 2024 at 14:23 +1000, Nathan Scott wrote:
> >
> > The package does not have any Obsoletes, so nothing should happen unless
> > users take explicit action to install valkey.
> >
>
> Yes, that's my point - if someone installs valkey, their redis
> installation is essentially trashed.
>
> I'd say "fair enough" if this was rawhide and we're working on the
> transition still, but this is stable Fedora, EPEL and user's data.
>
> cheers.
>
> --
> Nathan
>
>

-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
--
___
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: Redis will no longer be OSS... now what?

[Jonathan Wright via devel]

On Wed, Apr 17, 2024 at 9:43 AM Leon Fauster via devel <
devel@lists.fedoraproject.org> wrote:

> Am 17.04.24 um 15:59 schrieb Jonathan Wright via devel:
> > Valley 7.2.5 stable was released yesterday.  Builds are in Bodhi and
> > ready for testing/feedback.
> >
> > https://bodhi.fedoraproject.org/updates/?search=valkey-7.2.5-1
> > <https://bodhi.fedoraproject.org/updates/?search=valkey-7.2.5-1>
> >
>
> Thanks for the work on it. I wonder why valkey conflicts with redis,
> redict for instance does not!? Is this a decision for a preferred
> upgrade path? What about leaving this decision to the user (keydb,
> redict, valkey, redis on RHEL, etc) and allowing parallel installation
> for testing, decision making processes and migration.
>
>
It is due to redict renaming some libs, while valkey has opted to retain
"redis" on some lib file names.


> --
> Leon
>
> --
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat <https://chat.almalinux.org/almalinux/messages/@jonathan>
--
___
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: Redis will no longer be OSS... now what?

[Jonathan Wright via devel]

Valley 7.2.5 stable was released yesterday.  Builds are in Bodhi and ready
for testing/feedback.

https://bodhi.fedoraproject.org/updates/?search=valkey-7.2.5-1

On Tue, Apr 9, 2024 at 12:54 PM Jonathan Wright 
wrote:

> Valkey 7.2.4 rc1 was released earlier today.  Package review opened at
> https://bugzilla.redhat.com/show_bug.cgi?id=2274206 which Neal Gompa has
> taken.
>
> Will update again when packages are in Bodhi testing.
>
> On Thu, Mar 28, 2024 at 1:41 PM Carlos Rodriguez-Fernandez <
> carlosrodrifernan...@gmail.com> wrote:
>
>> So, valkey is then the one the AWS employee did.
>>
>> Thank you Jonathan for the work on this.
>>
>> On 3/28/24 11:13, Jonathan Wright via devel wrote:
>> > This is the one previously known as "PlaceHolderKV".
>> >
>> > I forgot to mention but redict is packaged and ready for testing in
>> > Bodhi: https://bodhi.fedoraproject.org/updates/?search=redict-7.3.0~rc
>> > <https://bodhi.fedoraproject.org/updates/?search=redict-7.3.0~rc>
>> >
>> > I'll be packing up valkey as soon as they have a tagged release.
>> >
>> > After following redict and valkey closely for the past week or so I'm
>> > anticipating valkey becoming the defacto replacement for redis in most
>> > places.
>> >
>> > On Thu, Mar 28, 2024 at 1:09 PM Carlos Rodriguez-Fernandez
>> > mailto:carlosrodrifernan...@gmail.com>>
>>
>> > wrote:
>> >
>> > Valkey is another fork, sponsored by the Linux Foundation.
>> >
>> >
>> https://www.linuxfoundation.org/press/linux-foundation-launches-open-source-valkey-community
>> <
>> https://www.linuxfoundation.org/press/linux-foundation-launches-open-source-valkey-community
>> >
>> >
>> > It came out just today.
>> >
>> > On 3/23/24 11:35, Jonathan Wright via devel wrote:
>> >  > KeyDB builds are in Bodhi and ready for testing for all Fedora
>> > versions
>> >  > + EPEL8/9.
>> >  >
>> >  > https://bodhi.fedoraproject.org/updates/?search=keydb-6.3.4-2
>> > <https://bodhi.fedoraproject.org/updates/?search=keydb-6.3.4-2>
>> >  > <https://bodhi.fedoraproject.org/updates/?search=keydb-6.3.4-2
>> > <https://bodhi.fedoraproject.org/updates/?search=keydb-6.3.4-2>>
>> >  >
>> >  > I'm still keeping an eye on, and chatting with the creators of
>> > the other
>> >  > two, redict and the unnamed one from an AWS employee and will
>> > package
>> >  > them when they have official builds.
>> >  >
>> >  > In the meantime I'd welcome any testing on the KeyDB packages in
>> > Bodhi.
>> >  >
>> >  > On Fri, Mar 22, 2024 at 11:10 PM Gary Buhrmaster
>> >  > mailto:gary.buhrmas...@gmail.com>
>> > <mailto:gary.buhrmas...@gmail.com
>> > <mailto:gary.buhrmas...@gmail.com>>> wrote:
>> >  >
>> >  > On Sat, Mar 23, 2024 at 3:22 AM Kevin Kofler via devel
>> >  > > > <mailto:devel@lists.fedoraproject.org>
>> >  > <mailto:devel@lists.fedoraproject.org
>> > <mailto:devel@lists.fedoraproject.org>>> wrote:
>> >  >
>> >  >  > We will see whether that or redict will get the most
>> > attention. Cloud
>> >  >  > companies like Amazon will probably prefer BSD, whereas
>> >  > contributors worried
>> >  >  > about another "Redis, Inc." coming up and taking their
>> > forked code
>> >  >  > proprietary too will most likely prefer the LGPL fork
>> (redict)
>> >  > (unless they
>> >  >  > are unhappy about the use of version 3.0 only of the LGPL
>> > by that
>> >  > fork).
>> >  >
>> >  > "It is hard to make predictions, especially about the
>> future",
>> >  > but it appears that many of the recent non-redis contributors
>> >  > are cloud company entangled (and were previously willing to
>> >  > contribute under the BSD-3-Clause license).
>> >  > --
>> >  > ___
>> >  > devel mailing list -- devel@lists.fedoraproject.org
>> > <mailto:de

Re: Redis will no longer be OSS... now what?

[Jonathan Wright via devel]

Valkey 7.2.4 rc1 was released earlier today.  Package review opened at
https://bugzilla.redhat.com/show_bug.cgi?id=2274206 which Neal Gompa has
taken.

Will update again when packages are in Bodhi testing.

On Thu, Mar 28, 2024 at 1:41 PM Carlos Rodriguez-Fernandez <
carlosrodrifernan...@gmail.com> wrote:

> So, valkey is then the one the AWS employee did.
>
> Thank you Jonathan for the work on this.
>
> On 3/28/24 11:13, Jonathan Wright via devel wrote:
> > This is the one previously known as "PlaceHolderKV".
> >
> > I forgot to mention but redict is packaged and ready for testing in
> > Bodhi: https://bodhi.fedoraproject.org/updates/?search=redict-7.3.0~rc
> > <https://bodhi.fedoraproject.org/updates/?search=redict-7.3.0~rc>
> >
> > I'll be packing up valkey as soon as they have a tagged release.
> >
> > After following redict and valkey closely for the past week or so I'm
> > anticipating valkey becoming the defacto replacement for redis in most
> > places.
> >
> > On Thu, Mar 28, 2024 at 1:09 PM Carlos Rodriguez-Fernandez
> > mailto:carlosrodrifernan...@gmail.com>>
>
> > wrote:
> >
> > Valkey is another fork, sponsored by the Linux Foundation.
> >
> >
> https://www.linuxfoundation.org/press/linux-foundation-launches-open-source-valkey-community
> <
> https://www.linuxfoundation.org/press/linux-foundation-launches-open-source-valkey-community
> >
> >
> > It came out just today.
> >
> > On 3/23/24 11:35, Jonathan Wright via devel wrote:
> >  > KeyDB builds are in Bodhi and ready for testing for all Fedora
> > versions
> >  > + EPEL8/9.
> >  >
> >  > https://bodhi.fedoraproject.org/updates/?search=keydb-6.3.4-2
> > <https://bodhi.fedoraproject.org/updates/?search=keydb-6.3.4-2>
> >  > <https://bodhi.fedoraproject.org/updates/?search=keydb-6.3.4-2
> > <https://bodhi.fedoraproject.org/updates/?search=keydb-6.3.4-2>>
> >  >
> >  > I'm still keeping an eye on, and chatting with the creators of
> > the other
> >  > two, redict and the unnamed one from an AWS employee and will
> > package
> >  > them when they have official builds.
> >  >
> >  > In the meantime I'd welcome any testing on the KeyDB packages in
> > Bodhi.
> >  >
> >  > On Fri, Mar 22, 2024 at 11:10 PM Gary Buhrmaster
> >  > mailto:gary.buhrmas...@gmail.com>
> > <mailto:gary.buhrmas...@gmail.com
> > <mailto:gary.buhrmas...@gmail.com>>> wrote:
> >  >
> >  > On Sat, Mar 23, 2024 at 3:22 AM Kevin Kofler via devel
> >  >  > <mailto:devel@lists.fedoraproject.org>
> >  > <mailto:devel@lists.fedoraproject.org
> > <mailto:devel@lists.fedoraproject.org>>> wrote:
> >  >
> >  >  > We will see whether that or redict will get the most
> > attention. Cloud
> >  >  > companies like Amazon will probably prefer BSD, whereas
> >  > contributors worried
> >  >  > about another "Redis, Inc." coming up and taking their
> > forked code
> >  >  > proprietary too will most likely prefer the LGPL fork
> (redict)
> >  > (unless they
> >  >  > are unhappy about the use of version 3.0 only of the LGPL
> > by that
> >  > fork).
> >  >
> >  > "It is hard to make predictions, especially about the future",
> >  > but it appears that many of the recent non-redis contributors
> >  > are cloud company entangled (and were previously willing to
> >  > contribute under the BSD-3-Clause license).
> >  > --
> >  > ___
> >  > devel mailing list -- devel@lists.fedoraproject.org
> > <mailto:devel@lists.fedoraproject.org>
> >  > <mailto:devel@lists.fedoraproject.org
> > <mailto:devel@lists.fedoraproject.org>>
> >  > To unsubscribe send an email to
> > devel-le...@lists.fedoraproject.org
> > <mailto:devel-le...@lists.fedoraproject.org>
> >  > <mailto:devel-le...@lists.fedoraproject.org
> > <mailto:devel-le...@lists.fedoraproject.org>>
> >  > Fedora Code of Conduct:
> >  > https://docs.fedoraproject.org/en-US/project/code-of-con

Re: convert everything to rpmautospec?

[Jonathan Wright via devel]

-1 as well, for all the reasons already mentioned.

On Mon, Apr 8, 2024 at 8:28 AM Iñaki Ucar  wrote:

> So someone wanted to use rpmautospec and was willing to do the work,
> putting things together as an opt-in feature. Perfect.
>
> Now, I don't see any problem if some time later someone revisits the topic
> and proposes to go further. I don't see anything unfriendly here.
> Everything was set or decided at some point, and nothing could ever be
> changed if we don't allow ourselves to change our minds and be free to make
> new proposals.
>
> That said, we are also free to reject those proposals, and I'm -1 here. As
> of today, I think it's fine as an opt-in feature, and I'm even using it for
> some small uncomplicated packages. But I don't think it should be the
> default with an opt-out.
>
> Iñaki
>
> On Mon, 8 Apr 2024 at 14:56, Emmanuel Seyman  wrote:
>
>> * Zbigniew Jędrzejewski-Szmek [08/04/2024 09:02] :
>> >
>> > Well, you and Kevin see "salami tactics" (whatever that may be),
>>
>> FTR, I have no idea what "salami tactics" is.
>>
>> > while I see normal engineering practice: some new idea is hatched,
>> > it's implemented and used narrowly, them it's applied by default
>> > and more widely, and possibly at the end previous methods are
>> > deprecated.
>>
>> This sounds acceptable but is not at all how these changes are proposed.
>>
>> An proposal is made, stating explicity that it will be opt-in or target
>> a subset of the target audience and never even suggesting that the scope
>> might one day be expanded.
>>
>> It is accepted based on that premise and, after a while, changes are
>> made to make the change default or opt-out, leaving the people who would
>> not have accepted it had they known they would be forced to use it with
>> no recourse.
>>
>> This is unfriendly (thus violating one of Fedora's core principles) at
>> best and deceitful at worst.
>>
>> > The alternative would be to have "grand plans" where we decide that
>> > some technology will be used by default and mandatory before we deploy
>> > it widely and get feedback.
>>
>> Another alternative would be not lie to the target audience by
>> initially claiming that the change is opt-in. Yet another alternative
>> would be to not go back on this claim.
>>
>> > I think that if you think this through, you'll realize that the
>> > "salami tactic" is quite reasonable.
>>
>> I don't but wish to thank you for the condescending tone nonetheless.
>>
>> Emmanuel
>> --
>> ___
>> 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
>>
>
>
> --
> Iñaki Úcar
> --
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
--
___
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: xz backdoor

[Jonathan Wright via devel]

That would be a bit premature.  At this point it looks like one bad actor,
and the other maintainer probably wasn't even aware.  We should wait and
see how this plays out.

On Fri, Mar 29, 2024 at 1:01 PM Kevin Kofler via devel <
devel@lists.fedoraproject.org> wrote:

> Hi,
>
> wow: https://www.openwall.com/lists/oss-security/2024/
>
> I think at this point we clearly cannot trust xz upstream anymore and
> should
> probably fork the project.
>
> Kevin Kofler
> --
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
--
___
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: Redis will no longer be OSS... now what?

[Jonathan Wright via devel]

This is the one previously known as "PlaceHolderKV".

I forgot to mention but redict is packaged and ready for testing in Bodhi:
https://bodhi.fedoraproject.org/updates/?search=redict-7.3.0~rc

I'll be packing up valkey as soon as they have a tagged release.

After following redict and valkey closely for the past week or so I'm
anticipating valkey becoming the defacto replacement for redis in most
places.

On Thu, Mar 28, 2024 at 1:09 PM Carlos Rodriguez-Fernandez <
carlosrodrifernan...@gmail.com> wrote:

> Valkey is another fork, sponsored by the Linux Foundation.
>
>
> https://www.linuxfoundation.org/press/linux-foundation-launches-open-source-valkey-community
>
> It came out just today.
>
> On 3/23/24 11:35, Jonathan Wright via devel wrote:
> > KeyDB builds are in Bodhi and ready for testing for all Fedora versions
> > + EPEL8/9.
> >
> > https://bodhi.fedoraproject.org/updates/?search=keydb-6.3.4-2
> > <https://bodhi.fedoraproject.org/updates/?search=keydb-6.3.4-2>
> >
> > I'm still keeping an eye on, and chatting with the creators of the other
> > two, redict and the unnamed one from an AWS employee and will package
> > them when they have official builds.
> >
> > In the meantime I'd welcome any testing on the KeyDB packages in Bodhi.
> >
> > On Fri, Mar 22, 2024 at 11:10 PM Gary Buhrmaster
> > mailto:gary.buhrmas...@gmail.com>> wrote:
> >
> > On Sat, Mar 23, 2024 at 3:22 AM Kevin Kofler via devel
> >  > <mailto:devel@lists.fedoraproject.org>> wrote:
> >
> >  > We will see whether that or redict will get the most attention.
> Cloud
> >  > companies like Amazon will probably prefer BSD, whereas
> > contributors worried
> >  > about another "Redis, Inc." coming up and taking their forked code
> >  > proprietary too will most likely prefer the LGPL fork (redict)
> > (unless they
> >  > are unhappy about the use of version 3.0 only of the LGPL by that
> > fork).
> >
> > "It is hard to make predictions, especially about the future",
> > but it appears that many of the recent non-redis contributors
> > are cloud company entangled (and were previously willing to
> > contribute under the BSD-3-Clause license).
> > --
> > ___
> > devel mailing list -- devel@lists.fedoraproject.org
> > <mailto:devel@lists.fedoraproject.org>
> > To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> > <mailto:devel-le...@lists.fedoraproject.org>
> > Fedora Code of Conduct:
> > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > <https://docs.fedoraproject.org/en-US/project/code-of-conduct/>
> > List Guidelines:
> > https://fedoraproject.org/wiki/Mailing_list_guidelines
> > <https://fedoraproject.org/wiki/Mailing_list_guidelines>
> > List Archives:
> >
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> <
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> >
> > Do not reply to spam, report it:
> > https://pagure.io/fedora-infrastructure/new_issue
> > <https://pagure.io/fedora-infrastructure/new_issue>
> >
> >
> >
> > --
> > Jonathan Wright
> > AlmaLinux Foundation
> > Mattermost: chat <
> https://chat.almalinux.org/almalinux/messages/@jonathan>
> >
> > --
> > ___
> > 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: Redis will no longer be OSS... now what?

[Jonathan Wright via devel]

KeyDB builds are in Bodhi and ready for testing for all Fedora versions +
EPEL8/9.

https://bodhi.fedoraproject.org/updates/?search=keydb-6.3.4-2

I'm still keeping an eye on, and chatting with the creators of the other
two, redict and the unnamed one from an AWS employee and will package them
when they have official builds.

In the meantime I'd welcome any testing on the KeyDB packages in Bodhi.

On Fri, Mar 22, 2024 at 11:10 PM Gary Buhrmaster 
wrote:

> On Sat, Mar 23, 2024 at 3:22 AM Kevin Kofler via devel
>  wrote:
>
> > We will see whether that or redict will get the most attention. Cloud
> > companies like Amazon will probably prefer BSD, whereas contributors
> worried
> > about another "Redis, Inc." coming up and taking their forked code
> > proprietary too will most likely prefer the LGPL fork (redict) (unless
> they
> > are unhappy about the use of version 3.0 only of the LGPL by that fork).
>
> "It is hard to make predictions, especially about the future",
> but it appears that many of the recent non-redis contributors
> are cloud company entangled (and were previously willing to
> contribute under the BSD-3-Clause license).
> --
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
--
___
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: Redis will no longer be OSS... now what?

[Jonathan Wright via devel]

On Thu, Mar 21, 2024 at 1:28 PM Neal Gompa  wrote:

> On Thu, Mar 21, 2024 at 2:24 PM Scott Williams 
> wrote:
> >
> > >  If we have some clue that a v7 merge/release
> > >  is on the very near horizon for KeyDB
> >
> > This doesn't look promising for v7 in time for Fedora 40 or shortly
> after, unfortunately: https://github.com/Snapchat/KeyDB/issues/420
> >
> > The choice of shipping an ever-stale v7 database versus a maintainable
> v6 one is not a fun one, but leaving it up to Fedora package maintainers to
> have to potentially come up with their own out-of-band patches for CVEs for
> redis-7 seems like the worse choice to me.
>
> I think the immediate fix is pulling in redict once it makes its first
> release: https://codeberg.org/redict/redict


I very much think we should take a wait and see approach for now.  KeyDB,
while slow, has at least published something.  redict is totally unknown.
Maybe it gets a huge following, maybe it doesn't.

We don't have to make any rash decisions since the current versions of
redis are in good shape for the time being.
-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
--
___
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: Redis will no longer be OSS... now what?

[Jonathan Wright via devel]

Anything that was new in Redis 7 is not currently in KeyDB.  This is a
decent list of features I found that would be impacted.

https://www.instaclustr.com/blog/redis-7-new-features/

KeyDB has it on their roadmap to merge in the latest features from Redis 7
but that's not complete yet (nor can I find any published status on that).
EPEL doesn't currently provide Redis for 8/9 because it got pulled in
directly by RH.  RHEL 9 does have a module for redis 7 but the default is
6, so that's easy at least.  There should be no problems with adding KeyDB
to EPEL 8/9 - in fact it doesn't even conflict with redis (though
keydb-devel will conflict with redis-devel as keydb-devel still uses
identical names of some libraries it produces).

Honestly trying to replace redis with KeyDB in Fedora would be a step
backwards and cause headaches so I don't think it's feasible, at least
until redis v7 features are merged into KeyDB.

On Thu, Mar 21, 2024 at 1:05 PM Scott Williams  wrote:

> Assuming KeyDB gets accepted (it looks close from the Bugzilla review), we
> should obsolete redis for KeyDB in Fedora 40+ and consider eventually doing
> likewise with EPEL as well, since we aren't going to be able to ship any
> redis patches moving forward.  I feel less strongly about that for EPEL as
> for Fedora.  As a Fedora redis user, personally, having KeyDB in-place
> replace redis on upgrade to Fedora 40 seems like the best possible route
> moving forward to limit end-user disruption and technical debt for Fedora.
>
> As long as KeyDB's multi-threading isn't enabled out of box, it should
> essentially be equivalent to redis-6 as I understand it.  We're currently
> shipping redis-7.2.4 in Fedora 39.  Are there any potential redis-7
> specific compatibility problems with KeyDB migration?
> --
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
--
___
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: Redis will no longer be OSS... now what?

[Jonathan Wright via devel]

While it may not end up as the right solution to replace Redis, here's the
review for KeyDB:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2270592

On Wed, Mar 20, 2024 at 9:49 PM Kevin Kofler via devel <
devel@lists.fedoraproject.org> wrote:

> Kevin Kofler via devel wrote:
> > Can Microsoft Garnet be a solution?
> >
> https://www.microsoft.com/en-us/research/blog/introducing-garnet-an-open-source-next-generation-faster-cache-store-for-accelerating-applications-and-services/
> > https://microsoft.github.io/garnet/
> > https://github.com/microsoft/garnet/tree/main
> >
> > Released under the MIT license (since 2 days ago) and claims that "Garnet
> > can work with existing Redis clients." And the benchmark results they
> post
> > outperforms all 3 of Redis (soon to become proprietary), KeyDB, and
> > DragonflyDB (already proprietary from the outstart).
>
> Though, Microsoft being Microsoft, they wrote that thing in C#, so it
> drags
> in the dotnet stack. But at least they did test on GNU/Linux:
> https://microsoft.github.io/garnet/docs/getting-started#build-the-project
> "You can use either Linux or Windows; Garnet works equally well on both
> platforms."
>
> Kevin Kofler
> --
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
--
___
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: Redis will no longer be OSS... now what?

[Jonathan Wright via devel]

Is this all a misunderstanding?
https://redis.com/blog/redis-labs-modules-license-changes/ seems to claim
that redis-core which appears to cover redis-server and redis-sentinel will
remain BSD-3.

On Wed, Mar 20, 2024 at 7:38 PM Jonathan Wright 
wrote:

> DragonflyDB is not an option, they do not use an OSI-approved license.  I
> reached out to them a couple of years ago to see if they would swap to one
> and they said they don't have an interest in it.
>
> On Wed, Mar 20, 2024 at 7:13 PM Aaron Rainbolt 
> wrote:
>
>> On 3/20/24 17:19, Neal Gompa wrote:
>>
>> Hey everyone,
>>
>> It looks like Redis, Inc. has announced that future versions of Redis
>> are no longer OSS and will be dual-licensed SSPL and RSAL[1]. Absent a
>> fork of Redis coming up, we will likely need to remove Redis from
>> Fedora.
>>
>> All I can say is... :(
>>
>> [1]: https://redis.com/blog/redis-adopts-dual-source-available-licensing/
>>
>> In addition to KeyDB, there's also DragonflyDB:
>> https://github.com/dragonflydb/dragonfly I mentioned Redis going
>> source-available to the KDE devs and one of them linked this.
>>
>> --
>> Aaron Rainbolt
>> Lubuntu Developer
>> Matrix: @arraybolt3:matrix.org
>> IRC: arraybolt3 on irc.libera.chat
>> GitHub: https://github.com/ArrayBolt3
>>
>> --
>> ___
>> 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
>>
>
>
> --
> Jonathan Wright
> AlmaLinux Foundation
> Mattermost: chat 
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
--
___
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: Redis will no longer be OSS... now what?

[Jonathan Wright via devel]

DragonflyDB is not an option, they do not use an OSI-approved license.  I
reached out to them a couple of years ago to see if they would swap to one
and they said they don't have an interest in it.

On Wed, Mar 20, 2024 at 7:13 PM Aaron Rainbolt  wrote:

> On 3/20/24 17:19, Neal Gompa wrote:
>
> Hey everyone,
>
> It looks like Redis, Inc. has announced that future versions of Redis
> are no longer OSS and will be dual-licensed SSPL and RSAL[1]. Absent a
> fork of Redis coming up, we will likely need to remove Redis from
> Fedora.
>
> All I can say is... :(
>
> [1]: https://redis.com/blog/redis-adopts-dual-source-available-licensing/
>
> In addition to KeyDB, there's also DragonflyDB:
> https://github.com/dragonflydb/dragonfly I mentioned Redis going
> source-available to the KDE devs and one of them linked this.
>
> --
> Aaron Rainbolt
> Lubuntu Developer
> Matrix: @arraybolt3:matrix.org
> IRC: arraybolt3 on irc.libera.chat
> GitHub: https://github.com/ArrayBolt3
>
> --
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
--
___
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: Redis will no longer be OSS... now what?

[Jonathan Wright via devel]

Looking back at my work on KeyDB, it's basically ready for package review
once we do some de-vendoring work.  I was hoping upstream would do it but
over a year and they haven't, so I guess I'll try to tackle it and PR it
back to them.

https://github.com/Snapchat/KeyDB/issues/493

On Wed, Mar 20, 2024 at 5:29 PM Neal Gompa  wrote:

> On Wed, Mar 20, 2024 at 6:26 PM Jonathan Wright via devel
>  wrote:
> >
> > We can potentially look to https://github.com/Snapchat/KeyDB which I've
> been loosely working on packaging anyway.
> >
>
> I'll want to test this for Pagure at least, since we're going to have
> to switch our recommendations around soon because of this.
>
>
>
> --
> 真実はいつも一つ！/ Always, there's only one truth!
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat <https://chat.almalinux.org/almalinux/messages/@jonathan>
--
___
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: Redis will no longer be OSS... now what?

[Jonathan Wright via devel]

We can potentially look to https://github.com/Snapchat/KeyDB which I've
been loosely working on packaging anyway.

On Wed, Mar 20, 2024 at 5:21 PM Neal Gompa  wrote:

> Hey everyone,
>
> It looks like Redis, Inc. has announced that future versions of Redis
> are no longer OSS and will be dual-licensed SSPL and RSAL[1]. Absent a
> fork of Redis coming up, we will likely need to remove Redis from
> Fedora.
>
> All I can say is... :(
>
> [1]: https://redis.com/blog/redis-adopts-dual-source-available-licensing/
>
> --
> 真実はいつも一つ！/ Always, there's only one truth!
> --
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
--
___
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

certbot Update From 2.6.0 to 2.9.0 in EPEL9

[Jonathan Wright via devel]

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 
--
___
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: Problems setting up environment

[Jonathan Wright via devel]

I think you sent this to the wrong list ;)

On Wed, Feb 7, 2024 at 8:03 AM Luis Correia 
wrote:

> Hi,
>
> please excuse my probable clumsiness but I'm having issues while trying to
> get ssh access to a package I'm now co-maintaining on RPM Fusion Free.
>
> I have followed all steps in
> https://rpmfusion.org/Contributors#Co-maintaining_an_existing_package,
> and am pretty sure my ssh key was uploaded correctly.
>
> If I try to clone the repo, I get this
>
> $ rfpkg clone free/mixxx
> Cloning into 'mixxx'...
> luisfcorr...@pkgs.rpmfusion.org: Permission denied (publickey).
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
> Could not execute clone: Failed to execute command.
>
> Thanks in advance!
> Luis
>
> --
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
--
___
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: Mock Configs v39.3 released - DNF5 used for F40+ builds

[Jonathan Wright via devel]

 mock -r fedora-rawhide-x86_64 --scrub=bootstrap did the trick.  Thank you!

On Fri, Dec 1, 2023 at 9:27 AM Pavel Raiskup  wrote:

> On Fri, Dec 1, 2023 at 4:09 PM Jonathan Wright via devel <
> devel@lists.fedoraproject.org> wrote:
>
>> Erm, I do already have dnf5 present within my f39 install where I was
>> trying to run the mockbuild.
>>
>> $ which /usr/bin/dnf5
>> /usr/bin/dnf5
>>
>> Any ideas as to the cause of the error?
>>
>
> I bet the bootstrap chroot is "cached" by Mock on your box.  Can you
> please try:
> $ mock -r fedora-rawhide-x86_64 --scrub=bootstrap  # or --scrub=all
>
> Pavel
>
>
>
>> On Fri, Dec 1, 2023 at 9:06 AM Jonathan Wright 
>> wrote:
>>
>>> This is awesome!
>>>
>>> I grabbed the RPM and then attempted to run a `fedpkg --release rawhide
>>> mockbuild` using it and ran into this error:
>>>
>>> INFO: Package manager dnf5 detected and used (direct choice)
>>> Start: dnf5 update
>>> execv(/usr/bin/dnf5) failed: No such file or directory
>>>
>>> Shouldn't it call dnf5 as a dep if it's going to be using it to make
>>> sure that it is installed?
>>>
>>> On Fri, Dec 1, 2023 at 8:04 AM Pavel Raiskup 
>>> wrote:
>>>
>>>> Hello maintainers!
>>>>
>>>> Let me announce a new release of Mock Core Configs v39.3, aka
>>>> the configuration files for Mock, the chroot build environment manager
>>>> for building RPMs.
>>>>
>>>> The notable change in this release is that we are switching the default
>>>> package_manager from DNF4 to DNF5, according to the F40 change:
>>>> https://fedoraproject.org/wiki/Changes/BuildWithDNF5
>>>> Full release notes:
>>>>
>>>> https://rpm-software-management.github.io/mock/Release-Notes-Configs-39.3
>>>>
>>>> We plan to push this update into Fedora Copr to get some early testing
>>>> next week.  Then, depending on the releng team, we might push this into
>>>> Koji soon. The Bodhi updates links are here:
>>>>
>>>> F39 https://bodhi.fedoraproject.org/updates/FEDORA-2023-0a947db1d0
>>>> F38 https://bodhi.fedoraproject.org/updates/FEDORA-2023-6ef1e12930
>>>> F37 https://bodhi.fedoraproject.org/updates/FEDORA-2023-cd9c489f40
>>>> EL9
>>>> https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-c2c4082053
>>>> EL8
>>>> https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-eab5217f46
>>>>
>>>> Note that we **will not** push these updates into Fedora stable earlier
>>>> than on Monday 2023-12-18 (but very likely we'll wait till the next
>>>> year, depending on the feedback).
>>>>
>>>> Happy (faster) building!
>>>> Pavel
>>>>
>>>>
>>>>
>>>> --
>>>> ___
>>>> 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
>>>>
>>>
>>>
>>> --
>>> Jonathan Wright
>>> AlmaLinux Foundation
>>> Mattermost: chat
>>> <https://chat.almalinux.org/almalinux/messages/@jonathan>
>>>
>>
>>
>> --
>> Jonathan Wright
>> AlmaLinux Foundation
>> Mattermost: chat
>> <https://chat.almalinux.org/almalinux/messages/@jonathan>
>> --
>> ___
>> 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 mail

Re: Mock Configs v39.3 released - DNF5 used for F40+ builds

[Jonathan Wright via devel]

Erm, I do already have dnf5 present within my f39 install where I was
trying to run the mockbuild.

$ which /usr/bin/dnf5
/usr/bin/dnf5

Any ideas as to the cause of the error?

On Fri, Dec 1, 2023 at 9:06 AM Jonathan Wright 
wrote:

> This is awesome!
>
> I grabbed the RPM and then attempted to run a `fedpkg --release rawhide
> mockbuild` using it and ran into this error:
>
> INFO: Package manager dnf5 detected and used (direct choice)
> Start: dnf5 update
> execv(/usr/bin/dnf5) failed: No such file or directory
>
> Shouldn't it call dnf5 as a dep if it's going to be using it to make sure
> that it is installed?
>
> On Fri, Dec 1, 2023 at 8:04 AM Pavel Raiskup  wrote:
>
>> Hello maintainers!
>>
>> Let me announce a new release of Mock Core Configs v39.3, aka
>> the configuration files for Mock, the chroot build environment manager
>> for building RPMs.
>>
>> The notable change in this release is that we are switching the default
>> package_manager from DNF4 to DNF5, according to the F40 change:
>> https://fedoraproject.org/wiki/Changes/BuildWithDNF5
>> Full release notes:
>>
>> https://rpm-software-management.github.io/mock/Release-Notes-Configs-39.3
>>
>> We plan to push this update into Fedora Copr to get some early testing
>> next week.  Then, depending on the releng team, we might push this into
>> Koji soon. The Bodhi updates links are here:
>>
>> F39 https://bodhi.fedoraproject.org/updates/FEDORA-2023-0a947db1d0
>> F38 https://bodhi.fedoraproject.org/updates/FEDORA-2023-6ef1e12930
>> F37 https://bodhi.fedoraproject.org/updates/FEDORA-2023-cd9c489f40
>> EL9
>> https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-c2c4082053
>> EL8
>> https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-eab5217f46
>>
>> Note that we **will not** push these updates into Fedora stable earlier
>> than on Monday 2023-12-18 (but very likely we'll wait till the next
>> year, depending on the feedback).
>>
>> Happy (faster) building!
>> Pavel
>>
>>
>>
>> --
>> ___
>> 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
>>
>
>
> --
> Jonathan Wright
> AlmaLinux Foundation
> Mattermost: chat 
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
--
___
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: Mock Configs v39.3 released - DNF5 used for F40+ builds

[Jonathan Wright via devel]

This is awesome!

I grabbed the RPM and then attempted to run a `fedpkg --release rawhide
mockbuild` using it and ran into this error:

INFO: Package manager dnf5 detected and used (direct choice)
Start: dnf5 update
execv(/usr/bin/dnf5) failed: No such file or directory

Shouldn't it call dnf5 as a dep if it's going to be using it to make sure
that it is installed?

On Fri, Dec 1, 2023 at 8:04 AM Pavel Raiskup  wrote:

> Hello maintainers!
>
> Let me announce a new release of Mock Core Configs v39.3, aka
> the configuration files for Mock, the chroot build environment manager
> for building RPMs.
>
> The notable change in this release is that we are switching the default
> package_manager from DNF4 to DNF5, according to the F40 change:
> https://fedoraproject.org/wiki/Changes/BuildWithDNF5
> Full release notes:
>
> https://rpm-software-management.github.io/mock/Release-Notes-Configs-39.3
>
> We plan to push this update into Fedora Copr to get some early testing
> next week.  Then, depending on the releng team, we might push this into
> Koji soon. The Bodhi updates links are here:
>
> F39 https://bodhi.fedoraproject.org/updates/FEDORA-2023-0a947db1d0
> F38 https://bodhi.fedoraproject.org/updates/FEDORA-2023-6ef1e12930
> F37 https://bodhi.fedoraproject.org/updates/FEDORA-2023-cd9c489f40
> EL9
> https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-c2c4082053
> EL8
> https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-eab5217f46
>
> Note that we **will not** push these updates into Fedora stable earlier
> than on Monday 2023-12-18 (but very likely we'll wait till the next
> year, depending on the feedback).
>
> Happy (faster) building!
> Pavel
>
>
>
> --
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
--
___
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

[Jonathan Wright via devel]

Co-maintainers welcome!  What's your FAS? :D

On Mon, Nov 20, 2023 at 9:39 AM Pete Zaitcev  wrote:

> On Mon, 20 Nov 2023 10:48:58 +0100
> Miro Hrončok  wrote:
>
> > Request package ownership via the *Take* button in he left column on
> > https://src.fedoraproject.org/rpms/
>
> > python-ironicclient   apevec, openstack-sig, orphan0
> weeks ago
>
> I was going to take ironicclient, but it looks like it is no longer
> an orphan. But jonathanspw already has 734 packages. Is everything okay
> down there?
>
> -- P
>
>

-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
--
___
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

[Jonathan Wright via devel]

Shoot those were mine.  I didn't mean to let them orphan :(

On Wed, Oct 4, 2023 at 6:39 PM Aleksei Bavshin 
wrote:

> On Mon, Sep 25, 2023 at 5:00 AM Miro Hrončok  wrote:
> > RBTools   orphan   2
> weeks ago
> > python-pydiffxorphan   2
> weeks ago
>
> Somehow I missed the retirement of these two packages (can we have
> nice 'will be retired in a week' emails for the FTI process as well,
> please?).
> I need to keep these alive, and it took two small patches to fix
> compatibility with python 3.12. Unretirement tickets are already
> filed.
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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 all my packages

[Jonathan Wright via devel]

I've picked up git and paperkey.

On Tue, Oct 3, 2023 at 9:25 AM Todd Zullinger  wrote:

> Hi,
>
> I'm orphaning all my packages (which I effectively did
> months ago).  It's been fun being a maintainer since 2006.
>
> However, I am not interested in contributing to a project
> where the primary sponsor and downstream no longer provides
> source code freely and openly.  It's simply not consistent
> with why I use and contribute to Fedora and Free/Open Source
> Software in general.
>
> I'm a maintainer of the following packages:
>
> cgit
> git
> paperkey
>
> I'm an admin of the following packages:
>
> fail2ban
> rubygem-asciidoctor
>
> I have commit privileges on these additional packages:
>
> asciidoc
> git-filter-repo
> rpmlint
>
> Thanks,
>
> --
> Todd Zullinger
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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: DNF5-5.0.1 has a stable API

[Jonathan Wright via devel]

That would make for somedifficult verbal conversations.  What do you
propose for the phonetic version? :D

On Mon, Jul 24, 2023 at 3:43 PM Chuck Anderson  wrote:

> On Mon, Jul 24, 2023 at 02:08:25PM -0400, Stephen Smoogen wrote:
> > Personally I would have preferred to call this a new tool versus trying
> to
> > use dnf name still. It makes it clearer that the break is going to
> happen.
>
> I propose "qzw".  It's so easy to type on a qwerty keyboard layout.
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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: Restore access to torrent-file-editor package

[Jonathan Wright via devel]

I picked up the package back in December of '22 when it was orphaned.  Ref
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/W5YHD4JSFGJQBZEUWS5KYFJHJSIWPZCD/

I'm happy to re-add you so I've added you back as an admin :)

On Mon, Jul 24, 2023 at 8:31 AM Ivan Romanov via devel <
devel@lists.fedoraproject.org> wrote:

> Hello I'm maintainer of torrent-file-editor package in
> Fedora and author of torrent-file-editor application. My FAS is
> ivanromanov. Some weeks ago I updated app and wanted to update my
> package in Fedora but can't do this. Seems now I haven't access to my
> package. I opened package on
>
> https://packages.fedoraproject.org/pkgs/torrent-file-editor/torrent-file-editor/
> seems now maintainer somebody jonathanspw. I tried to send message to
> torrent-file-editor dash maintainers at fedoraproject dot org but
> didn't get any response. So how to restore access to my package in this
> case?
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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] Re: Orphaning packages

[Jonathan Wright via devel]

Lance,

I can sponsor/mentor you.  I'll reach out to ya via Mattermost.

On Tue, Jun 27, 2023 at 10:51 AM Lance Albertson  wrote:

>
>
> On Thu, Jun 22, 2023 at 9:50 AM Othman Madjoudj 
> wrote:
>
>> Hello,
>>
>> Please note that I've orphaned by packages, list in the end of the
>> message.
>>
>> Best regards
>> -Othman
>>
>>  rpms/mod_limitipconn
>>
>
> I'm interested in maintaining this but I am not a packager yet and would
> need to be onboarded if someone is willing to be a mentor.
>
> Thanks-
>
> --
> Lance Albertson
> Director
> Oregon State University | Open Source Lab
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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: Red Hat Stream ONLY, Orphaning packages

[Jonathan Wright via devel]

If you'll add me as admin/owner on the packages I'll continue to maintain
them.  FAS jonathanspw

Especially interested in remmina since I use it nearly every day.

On Wed, Jun 21, 2023 at 12:27 PM Philip Wyett 
wrote:

> Hi all,
>
> After the announcement below today.
>
> https://www.redhat.com/en/blog/furthering-evolution-centos-stream
>
> I will be in 5 days detaching myself and orphaning all packages I have
> involvement with.
>
> Regards
>
> Phil
>
> --
> *** Playing the game for the games own sake. ***
>
>
> Associations:
>
> * Debian Maintainer (DM)
> * Fedora/EPEL Maintainer.
> * Contributor member of the AlmaLinux foundation.
>
> WWW: https://kathenas.org
>
> Buy Me a Coffee: https://www.buymeacoffee.com/kathenasorg
>
> Twitter: @kathenasorg
>
> Instagram: @kathenasorg
>
> IRC: kathenas
>
> GPG: 724AA9B52F024C8B
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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: Any interest in maintaining spyder (python IDE)?

[Jonathan Wright via devel]

If you can do a review on
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2186056 it will help
unblock the updates.

On Tue, Apr 4, 2023 at 8:46 PM Mukundan Ragavan 
wrote:

>
> On 4/3/23 12:53, Blaise Pabon wrote:
>
> Hi Mukundan, Jonathan,
>
> I have been working on becoming a fedora maintainer and I would love to
> help.
> When I followed the links to the build logs I got a 404.
>
> Blaise
>
>
>
> Hi Blaise,
>
> I will be happy to help you with becoming a packager. I am also happy to
> add you as a collaborator on my COPR.
>
> Build logs may have been deleted since these packages were built sometime
> ago.
>
> Let me know if you would like to be added to COPR.
>
> Mukundan.
>
> --
> GPG Key: E5C8BC67
>
>

-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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: hstr

[Jonathan Wright via devel]

I built it for EPEL9 BTW :)

On Mon, Apr 3, 2023 at 8:49 AM Kamil Paral  wrote:

> On Thu, Mar 30, 2023 at 5:12 PM Jonathan Wright via devel <
> devel@lists.fedoraproject.org> wrote:
>
>> I've grabbed this package.  I'll keep an eye on the GH issue and get an
>> update released once upstream releases patches/updates for the kernel
>> issues.
>>
>
> Thanks, Jonathan. I was a happy hstr user until recently. It's hard to go
> back to the regular Ctrl+r bash history.
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat <https://chat.almalinux.org/almalinux/messages/@jonathan>
___
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: Auto-assign packager sponsors to tickets?

[Jonathan Wright via devel]

Personally I'd not really like this solution.  For some sponsors which have
tons of time and can always take on people to mentor it will be great for
those folks.  For people who get "assigned" to sponsors that don't
necessarily have time and don't update their status to unavailable or
whatever at a given time it will be a bad experience for those seeking
sponsorship.

What about a mailing list for people seeking sponsorship to email into that
would go to all sponsors and the person seeking sponsorship could introduce
themselves, etc. and then available sponsors could perhaps chat back and
forth a bit in that list to find out if it might be a good fit for them.

As was mentioned, sponsorship requires a time commitment but it also needs
to be a good fit between two people for it to be fruitful when they work
together.

On Sun, Apr 2, 2023 at 10:34 AM Jakub Kadlcik  wrote:

> I tried to get some numbers to see how many packagers we sponsor each
> year but FAS tells me only group members but not when they joined the
> group. Do any of you at least have a rough estimate of what number are
> we talking about? I wouldn't propose any auto-assign system for
> package reviews because there is thousand of them each year. That
> would be insane. But how many new contributors that need to be
> sponsored do we have each year? My guess is that not even every
> sponsor would get a ticket within the year.
>
> Jakub
>
> On Sun, Apr 2, 2023 at 5:07 PM Jakub Kadlcik  wrote:
> >
> > > If they wait for months, I think they don't want to be sponsored.
> >
> > I respectfully disagree here, IMHO we communicate a message that a
> > sponsor will find the contributor, not the other way around. Just so I
> > don't repeat the same message in my own words, everything that
> > Miroslav said, sounds true to me.
> >
> > > Please exclude me from such spam.
> >
> > Sure, no problem with me. As I said in my initial proposal, I'd
> > provide an easy way to opt out (probably multiple ways, so it is
> > convenient for everybody).
> >
> > > I don't think it's fair to expect that all sponsors are available to
> do this at any time.
> >
> > Well sure, I agree. Mentoring somebody is a time commitment and nobody
> > has sponsoring people as the #1 priority. But as I said in the
> > proposal "If a sponsor is not able or willing to work on a ticket,
> > they could either set NEEDINFO on another sponsor or just drop
> > themselves. The ticket would then get a new sponsor next week" - to me
> > this sounds very reasonable.
> >
> > Jakub
> >
> > On Sun, Apr 2, 2023 at 4:12 PM Miroslav Suchý  wrote:
> > >
> > > Dne 02. 04. 23 v 11:54 Vitaly Zaitsev via devel napsal(a):
> > >
> > > I'm always willing to review and sponsor new maintainers, but they
> need to show explicit consent by posting on IRC/Matrix/ML or direct email.
> > >
> > > Let me check the history of
> > >
> > >
> https://docs.fedoraproject.org/en-US/package-maintainers/How_to_Get_Sponsored_into_the_Packager_Group/#how_to_find_a_sponsor
> > >
> > > Right now we tell users to:
> > >
> > > Usually, a sponsor finds you through your sponsorship request in
> Bugzilla or the packager sponsors pagure instance. In case you are waiting
> to be sponsored for longer than desirable, take a look at Sponsors page. It
> will help you find the right sponsor for you based on programming language
> preference, domains of interest, native language, and other criteria.
> > >
> > > This is not there for long time. Actually since 2021 when Jakub wrote
> that "Sponsor page". Previously there was:
> > >
> > > If you are submitting a new package for review in Bugzilla,
> > > you can make the review request block the
> > >
> https://bugzilla.redhat.com/show_bug.cgi?id=FE-NEEDSPONSOR[FE-NEEDSPONSOR]
> tracking bug.
> > >
> > > Otherwise, you can file a ticket in the
> > > https://pagure.io/packager-sponsors/[sponsors ticketing system].
> > >
> > > So previously - and even now - we tell newcomers to to block
> FE-NEEDSPONSOR and wait. And only if they wait too long (whatever it means)
> to start looking for sponsors directly.
> > >
> > > I personally think that Jakub's proposal is great and I welcome it.
> Not everyone is brave to initiate a conversation and asks for being
> sponsored. We have to realize it often means that junior developer has to
> reach senior developer and juniors often hesitate to do this step. This
> proposal remove one road blocks for juniors.
> > >
> > > If other people does not find it useful, then I propose to at least
> alter our documentation and tell users to start looking for sponsor
> immediately after blocking FE-NEEDSPONSOR.
> > >
> > > Miroslav
> > >
> > >
> > > ___
> > > 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:
> 

Re: Any interest in maintaining spyder (python IDE)?

[Jonathan Wright via devel]

You added me on it a while back and I haven't done anything with it yet,
but I do still intend to work on it when I get a chance.

On Sun, Apr 2, 2023 at 9:52 AM Mukundan Ragavan 
wrote:

>
> I have been maintaining spyder in Fedora for sometime now. Since the
> time I took up maintaining spyder, the dependencies have expanded
> considerably (I have packaged several of these dependencies in the
> past). Unfortunately, I am not able to devote as much as time as needed
> to maintain this package (at least in working condition) anymore.
>
> I should point out that there are specific version dependencies  for
> certain packages (e.g. ipython) that are not in sync with Fedora. I have
> relaxed the dependencies in the Fedora package (so that spyder continues
> to work, albeit with some issues). I did start updating spyder to 5.4.x
> series. Two more packages need to be packaged. See COPR -
>
> https://copr.fedorainfracloud.org/coprs/nonamedotc/spyder/builds/
>
>
> Is anyone interested in maintaining spyder and potentially its
> dependencies? Some of these dependencies are being maintained by
> python-sig already. I will be happy to continue on as co-maintainer and
> try to help out when I can.
>
> Thanks.
>
> Mukundan.
>
> --
> GPG Key: E5C8BC67
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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.x inches closer

[Jonathan Wright via devel]

I just retired python-acme this morning in F38/39.  It's now built by the
certbot package.

On Thu, Mar 30, 2023 at 11:02 AM Jerry James  wrote:

> On Wed, Mar 1, 2023 at 3:28 PM Jerry James  wrote:
> > The maintainers of the packages I am about to mention are BCCed on this
> email.
>
> And that is true of this email as well.
>
> > A couple of months ago, I talked about updating the fontawesome-fonts
> > package to version 6.x.  I want to give an update on where things
> > stand.  See https://copr.fedorainfracloud.org/coprs/jjames/FontAwesome6/
> > for builds of affected packages.  All changes have been checked into
> > my forks of the affected packages (username "jjames").  Here's a quick
> > rundown of the changes.
>
> The FontAwesome 6 Change proposal was accepted.  I have created a side
> tag, have built both the new backwards compatibility
> fontawesome4-fonts package and  the updated fontawesome-fonts package
> in it.  I will start filing PRs momentarily for the other packages.
> Package maintainers, until the side tag is merged back into Rawhide,
> please use the following command to build the affected packages:
>
> fedpkg build --target=f39-build-side-65584
>
> As a reminder, these are the packages that will need to be changed and
> built:
>
> - cantata
> - dogtag-pki
> - freeipa
> - ipsilon
> - python-acme
> - python-f5-sdk
> - python-nbclassic
> - python-networkx
> - python-pydata-sphinx-theme
> - python-QtAwesome
> - python-sphinx_ansible_theme
> - python-streamlink
> - python-XStatic-Font-Awesome
> - R-fontawesome
> - sympa
> - texlive
>
> Once all builds are complete and the side tag has been merged into
> Rawhide, the fontawesome5-fonts package will be retired.  Let me know
> if you have any questions or concerns.
> --
> Jerry James
> http://www.jamezone.org/
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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: hstr

[Jonathan Wright via devel]

I've grabbed this package.  I'll keep an eye on the GH issue and get an
update released once upstream releases patches/updates for the kernel
issues.

On Thu, Mar 30, 2023 at 5:59 AM Leigh Scott  wrote:

> I have orphaned hstr today.
>
>
> https://src.fedoraproject.org/rpms/hstr
>
> It is currently non-functional due to kernel-6.2 changes, see
>
> https://github.com/dvorka/hstr/issues/478
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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: Certbot 2.2.0 Update

[Jonathan Wright via devel]

2.2.0 will hit F37 and F38 stable repos tonight.

I'm holding EPEL9 back a little bit longer.

On Tue, Mar 21, 2023 at 9:21 AM Alexander Bokovoy 
wrote:

> On ti, 21 maalis 2023, Jonathan Wright via devel wrote:
> >Hi,
> >
> >I've updated Certbot to 2.2.0 in rawhide, f38, f37, and epel9.  I wanted
> to
> >email devel and seek more testing than usual for this release as I've also
> >converted the 10-15 packages to be built from a single spec instead of all
> >broken up as they were prior (ref
> >https://bugzilla.redhat.com/show_bug.cgi?id=2132123)
> >
> >If people could please update their certbot-related packages from
> >epel-testing and provide feedback here and/or karma or comments on the
> >updates in bodhi I'd be extremely grateful.
>
> Thanks. We have certbot tests in FreeIPA upstream. We run them against
> Rawhide weekly.
>
> Here is the one that was run on March 18th:
>
> http://freeipa-org-pr-ci.s3-website.eu-central-1.amazonaws.com/jobs/47908126-c5d5-11ed-84b2-fa163e02831a/report.html
>
> This one ran against certbot 2.1.0, but we'll see this Saturday how the
> tests will behave against 2.2.0.
>
> --
> / Alexander Bokovoy
> Sr. Principal Software Engineer
> Security / Identity Management Engineering
> Red Hat Limited, Finland
>
>

-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat <https://chat.almalinux.org/almalinux/messages/@jonathan>
___
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

Certbot 2.2.0 Update

[Jonathan Wright via devel]

Hi,

I've updated Certbot to 2.2.0 in rawhide, f38, f37, and epel9.  I wanted to
email devel and seek more testing than usual for this release as I've also
converted the 10-15 packages to be built from a single spec instead of all
broken up as they were prior (ref
https://bugzilla.redhat.com/show_bug.cgi?id=2132123)

If people could please update their certbot-related packages from
epel-testing and provide feedback here and/or karma or comments on the
updates in bodhi I'd be extremely grateful.

-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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: Fedora 38 mass rebuild is finished

[Jonathan Wright via devel]

I'm seeing the same errors on rawhide buildroot right now.

On Mon, Jan 23, 2023 at 1:34 PM Artur Frenszek-Iwicki <
s...@fedoraproject.org> wrote:

> I wanted to resubmit one of my failed builds, but the buildroot seems to
> be broken currently:
>
> > Problem 1: package python3-dnf-4.14.0-2.fc38.noarch requires libmodulemd
> >= 2.9.3, but none of the providers can be installed
> >  - package libmodulemd-2.14.0-5.fc38.x86_64 requires
> libglib-2.0.so.0()(64bit), but none of the providers can be installed
> >  - package libmodulemd-2.14.0-5.fc38.x86_64 requires
> libgobject-2.0.so.0()(64bit), but none of the providers can be installed
> >  - package dnf-4.14.0-2.fc38.noarch requires python3-dnf =
> 4.14.0-2.fc38, but none of the providers can be installed
> >  - package glib2-2.74.1-3.fc38.x86_64 requires libgnutls.so.30()(64bit),
> but none of the providers can be installed
> >  - conflicting requests
> >  - nothing provides libunistring.so.2()(64bit) needed by
> gnutls-3.7.8-11.fc38.x86_64
> > Problem 2: package python3-dnf-plugins-core-4.3.1-2.fc38.noarch requires
> python3-dbus, but none of the providers can be installed
> >  - package python3-dbus-1.3.2-2.fc38.x86_64 requires
> libglib-2.0.so.0()(64bit), but none of the providers can be installed
> >  - package dnf-plugins-core-4.3.1-2.fc38.noarch requires
> python3-dnf-plugins-core = 4.3.1-2.fc38, but none of the providers can be
> installed
> >  - package glib2-2.74.1-3.fc38.x86_64 requires libgnutls.so.30()(64bit),
> but none of the providers can be installed
> >  - conflicting requests
> >  - nothing provides libunistring.so.2()(64bit) needed by
> gnutls-3.7.8-11.fc38.x86_64
>
> A.FI.
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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: Bodhi slow with 504 gateway timeouts

[Jonathan Wright via devel]

On Tue, Jan 17, 2023 at 8:21 AM Stephen Smoogen  wrote:

>
>
> On Tue, 17 Jan 2023 at 09:19, Arthur Bols  wrote:
>
>> On 17/01/2023 14:57, Stephen Smoogen wrote:
>> > So bodhi and pagure are at different datacenters with hopefully
>> different
>> > network paths. Could people do some mtr or traceroutes from their
>> locations
>> > so we can see if this can be ironed out. Currently the limited tools we
>> > have in Fedora Infra for checking this all show 'green' so the
>> > 'interconnects' between the services are working.
>> >
>> Fedora infra is usually very slow for me, but Bodhi seemed much slower
>> than usual (taking a full minute to load).
>>
>> After being really slow, I had a bunch of 503's (not 504) for a while,
>> but now it seems to work fine:
>> - /releases takes 10 seconds (and had a 500 error once)
>> - /updates seems fast with 2.2 seconds
>>
>>
> Please note that from other announcements bodhi was updated today to
> 7.0.1. The slowdowns may have been due to that.
>
> However I notice both you and Richard have large packet drops on
> twelve99.net ip addresses. I don't know yet if that is an additional
> problem or not.
>
>

Without packet loss at the endpoint the stuff in the middle doesn't much
matter.  Based on the MTR and trace I'd say this is not network related.


>
>> $ mtr bodhi.fedoraproject.org -r -G
>> Start: 2023-01-17T15:14:31+0100
>> HOST: MarkV   Loss%   Snt   Last   Avg  Best Wrst
>> StDev
>>1.|-- ptr-82pqtg1hqu6kedca1n3.1 90.0%106.0   6.0   6.0 6.0
>> 0.0
>>2.|-- ptr-377wgf58htvrzp7oh0ch. 20.0%10   13.7  15.3  12.7 20.1
>> 2.7
>>3.|-- ???   100.0100.0   0.0   0.0 0.0
>> 0.0
>>4.|-- ???   100.0100.0   0.0   0.0 0.0
>> 0.0
>>5.|-- ???   100.0100.0   0.0   0.0 0.0
>> 0.0
>>6.|-- 2001:730:2302::d52e:a209   0.0%10   16.3  18.0  13.1 24.9
>> 3.5
>>7.|-- 2001:730:2302:1::d52e:a20  0.0%10   17.9  17.4  13.4 20.4
>> 2.7
>>8.|-- prs-bb1-v6.ip.twelve99.ne 10.0%10   61.1  31.3  16.4 62.1
>> 17.8
>>9.|-- ash-bb2-v6.ip.twelve99.ne  0.0%10  105.2 108.7 104.0
>> 118.7   5.0
>>   10.|-- lax-b22-v6.ip.twelve99.ne 90.0%10  160.2 160.2 160.2
>> 160.2   0.0
>>   11.|-- a100-ic325183-las-b24.ip.  0.0%10  175.7 162.1 158.0
>> 175.7   5.2
>>   12.|-- ???   100.0100.0   0.0   0.0 0.0
>> 0.0
>>   13.|-- 2620:107:4000:8006::1260.0%10  182.8 187.3 177.4
>> 199.7   7.1
>>   14.|-- ???   100.0100.0   0.0   0.0 0.0
>> 0.0
>>   15.|-- ???   100.0100.0   0.0   0.0 0.0
>> 0.0
>>   16.|-- ???   100.0100.0   0.0   0.0 0.0
>> 0.0
>>   17.|-- 2620:107:4000:c5e0::f3fd:  0.0%10  188.3 188.2 182.0
>> 192.4   2.8
>>   18.|-- 2620:107:4000:a090::f000:  0.0%10  185.3 185.5 182.5
>> 187.6   1.6
>>   19.|-- 2620:107:4000:cfff::f200:  0.0%10  183.1 185.7 181.9
>> 192.2   3.3
>>   20.|-- ???   100.0100.0   0.0   0.0 0.0
>> 0.0
>>   21.|-- ???   100.0100.0   0.0   0.0 0.0
>> 0.0
>>   22.|-- 2620:107:4000:4205:8000:0  0.0%10  182.8 188.9 182.0 220.5
>> 11.5
>>   23.|-- 2600:1f14:fad:5c02:7c8a:7  0.0%10  188.2 187.1 180.4
>> 210.5   8.5
>>
>>
>> $ traceroute bodhi.fedoraproject.org
>> traceroute to bodhi.fedoraproject.org (8.43.85.67), 30 hops max, 60 byte
>> packets
>>   1  _gateway (192.168.0.1)  6.347 ms  10.770 ms  11.768 ms
>>   2  d51A4C401.access.telenet.be (81.164.196.1)  20.244 ms  22.376 ms
>> 22.311 ms
>>   3  * * *
>>   4  * * *
>>   5  be-dgb01a-rb1-ae-19-0.aorta.net (213.46.162.9)  23.660 ms 23.584
>> ms  27.996 ms
>>   6  be-bru02a-ra1-vl-6.aorta.net (213.46.162.14)  29.026 ms 21.811 ms
>> 18.822 ms
>>   7  prs-bb1-link.ip.twelve99.net (62.115.116.238)  22.234 ms 19.546 ms
>> 25.043 ms
>>   8  ash-bb2-link.ip.twelve99.net (62.115.112.242)  116.324 ms 117.718
>> ms  114.206 ms
>>   9  ash-b2-link.ip.twelve99.net (62.115.123.125)  117.633 ms 117.595
>> ms  117.555 ms
>> 10  viawest-svc073699-ic361683.ip.twelve99-cust.net (213.248.67.199)
>> 117.473 ms  117.424 ms  117.385 ms
>> 11  be23.bbrt01.iad10.flexential.net (66.51.1.148)  129.400 ms 130.492
>> ms  130.451 ms
>> 12  be209.bbrt02.ral01.flexential.net (66.51.5.117)  120.744 ms 120.705
>> ms  120.597 ms
>> 13  * be32.crrt02.ral01.flexential.net (148.66.238.113)  119.944 ms
>> 122.230 ms
>> 14  128.136.224.140 (128.136.224.140)  112.075 ms  111.922 ms 110.807 ms
>> 15  8.43.84.1 (8.43.84.1)  176.779 ms  203.379 ms  205.480 ms
>> 16  8.43.84.3 (8.43.84.3)  122.495 ms  120.608 ms  122.398 ms
>> 17  8.43.84.4 (8.43.84.4)  215.289 ms  215.232 ms  211.599 ms
>> 18  ip-8-43-86-126.foo.bar (8.43.86.126)  124.226 ms  126.584 ms 142.354
>> ms
>> 19  proxy14.fedoraproject.org (8.43.85.67)  134.550 ms !X  116.964 ms
>> !X  121.806 ms !X
>>
>>
>> --
>> Arthur Bols
>> fas/irc: principis
>> 

Re: -D_FORTIFY_SOURCE defined but value is too low [-Werror]

[Jonathan Wright via devel]

Are you by chance running this inside of a rawhide docker container within
GH actions?  If so, I'm in the same boat and haven't figured out how to
force it back to "2", or why it's failing in the first place.

On Mon, Jan 16, 2023 at 12:05 PM Daniel P. Berrangé 
wrote:

> I'm getting the strange error in $SUBJECT in an upstream CI job that
> is targetting Fedora rawhide. I'm guessing it is something related to
> the recent changes to set the  _FOTIFY_SOURCE value to 3 instead of
> 2, but not sure what.
>
> What I'm finding especially bizarre is that I can't reproduce it on
> rawhide myself, despite using the exact same package versions and
> base container.
>
> I can't even figure out which particular component is emitting this
> error message string. My only thought is that perhaps it could be
> ccache related, since upstream CI has ccache enabled and the cache
> is preserved across CI pipelines. That could explain why I can't
> reproduce myself.
>
> My app has a config.h file used by all sources that does
>
>   #if !defined _FORTIFY_SOURCE && defined __OPTIMIZE__ && __OPTIMIZE__
>   # define _FORTIFY_SOURCE 2
>   #endif
>
> but the -D_FORTIFY_SOURCE=3 set by RPM in CFLAGS on the gcc command
> line ought to override this fine.
>
> $ gcc -Ilibvirt-glib/libvirt-glib-1.0.so.0.4000.0.p -Ilibvirt-glib
> -I../libvirt-glib -I. -I.. -I/usr/include/glib-2.0
> -I/usr/lib64/glib-2.0/include -I/usr/include/sysprof-4
> -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch
> -std=gnu99 ...snip many -Wxxx flags... -fexceptions
> -fasynchronous-unwind-tables -fipa-pure-const  -fstack-protector-strong -O2
> -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe
> -U_FORTIFY_SOURCE -Wp,-U_FORTIFY_SOURCE -Wp,-D_FORTIFY_SOURCE=3
> -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1
> -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64
> -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection
> -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -fPIC
> -pthread '-DLOCALEDIR="/usr/share/locale"' '-DDATADIR="/usr/share"'
> -DLIBVIRT_GLIB_BUILD -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_48
> -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_48 -MD -MQ
> libvirt-glib/libvirt-glib-1.0.so.0.4000.0.p/libvirt-glib-error.c.o -MF
> libvirt-glib/libvirt-glib-1.0.so.0.4000.0.p/libvirt-glib-error.c.o.d -o
> libvirt-glib/libvirt-glib-1.0.so.0.4000.0.p/libvirt-glib-error.c.o -c
> ../libvirt-glib/libvirt-glib-error.c
> ../libvirt-glib/libvirt-glib-error.c: error: -D_FORTIFY_SOURCE defined but
> value is too low [-Werror]
> cc1: all warnings being treated as errors
>
> So does anyone know what this error message would be coming from, and more
> importantly how to make it go away :-)
>
> With regards,
> Daniel
> --
> |: https://berrange.com  -o-
> https://www.flickr.com/photos/dberrange :|
> |: https://libvirt.org -o-
> https://fstop138.berrange.com :|
> |: https://entangle-photo.org-o-
> https://www.instagram.com/dberrange :|
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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: Automation of Fedora SCM requests

[Jonathan Wright via devel]

Just got the following error:
https://pagure.io/releng/fedora-scm-requests/issue/50417

I'm pretty sure I've always requested branches as someone with "commit"
access and never had them rejected.

On Thu, Jan 12, 2023 at 3:30 AM Dominik 'Rathann' Mierzejewski <
domi...@greysector.net> wrote:

> On Wednesday, 11 January 2023 at 17:13, Michal Konecny wrote:
> > Hi everyone,
> >
> > all the remaining issues were solved and the bot is now processing
> > tickets as it should. I will watch the SCM request repository for next
> > few days to see if everything is working as it should.
> > Thanks for your patience.
>
> Thank you Michal and the CPE Team. Automating this part is a very
> welcome improvement.
>
> Regards,
> Dominik
> --
> Fedora   https://getfedora.org  |  RPM Fusion  http://rpmfusion.org
> There should be a science of discontent. People need hard times and
> oppression to develop psychic muscles.
> -- from "Collected 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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: Automation of Fedora SCM requests

[Jonathan Wright via devel]

This is incredible, thank you all so much for the work!

On Tue, Jan 10, 2023, 5:26 AM Michal Konecny  wrote:

> Hi everyone,
>
> this automation is now in place and new SCM requests will be processed
> automatically. If you find any issue with the automation, please report it
> to toddlers issue tracker [0].
>
> On behalf of CPE Team,
> Michal
>
> [0] - https://pagure.io/fedora-infra/toddlers/issues
>
> On 08. 12. 22 11:10, Michal Konecny wrote:
>
> Hello everyone,
>
> for some time CPE (Community Platform Engineering) team is working on
> automating Fedora SCM requests [0]. The automation is currently live on
> staging. You can see the output (closed tickets) in Fedora SCM requests
> staging repo [1].
> The automation is done using a plugin in toddlers [2]. We have a
> documentation [3] for the new toddler, if you want to know more about it.
> There is also a ticket [4] tracking this work.
>
> We plan to deploy this in production on *10th January 2023*, after that
> all the Fedora SCM request will be processed automatically and it will ping
> correct people if the manual intervention is needed. This will not change
> anything in user workflow, it will just make the job of Fedora Release
> Engineering Team easier and let them focus on other things.
>
> On behalf of CPE Team,
> Michal
>
> [0] - https://pagure.io/releng/fedora-scm-requests
> [1] - https://stg.pagure.io/releng/fedora-scm-requests
> [2] - https://pagure.io/fedora-infra/toddlers
> [3] - https://pagure.io/fedora-infra/toddlers/blob/main/f/docs
> [4] - https://pagure.io/releng/issue/9274
>
>
> ___
> 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: certbot 2.1.0

[Jonathan Wright via devel]

I have a spec mostly ready to combine all of it back into a single spec
file.  Would you be open to discussing/reviewing that, merging it, then
pushing that to stable?

On Tue, Dec 27, 2022 at 9:17 PM Nick Bebout  wrote:

> I have built certbot 2.1.0 for all supported releases of Fedora and for
> EPEL.  It has been in testing for 2 weeks.  I am getting ready to push it
> to stable in the next few days.
>
> It is a "major" update, but is mostly backwards compatible.  2.0.0 had
> more incompatibilities, but in 2.1.0 they added changes to make most
> plugins still work with the new 2.x series.  The other main change is that
> it will use ECDSA keys by default instead of RSA.
>
> nb
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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

[Jonathan Wright via devel]

I've taken chocolate-doom and gif2png.

On Tue, Nov 29, 2022 at 7:53 AM Rahul Sundaram  wrote:

> Hi
>
> I have orphaned all the packages I used to maintain but haven't had the
> time to keep up with in a long time.  Feel free to pick them up if you
> like.  All the best.
>
> https://src.fedoraproject.org/rpms/chocolate-doom
> https://src.fedoraproject.org/rpms/gif2png
> https://src.fedoraproject.org/rpms/ghasher
> https://src.fedoraproject.org/rpms/wv
> https://src.fedoraproject.org/rpms/python-bottle
> https://src.fedoraproject.org/rpms/python-bottle-sqlite
>
> Rahul
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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: Inactive packagers to be removed after the F37 release

[Jonathan Wright via devel]

I took a few packages.  I'm trying to also take bonnie++ but the take
request is returning a 500 error.

On Mon, Nov 28, 2022 at 12:35 PM Mattia Verga via devel <
devel@lists.fedoraproject.org> wrote:

> Il 28/11/22 19:20, Mattia Verga ha scritto:
> > From your output I made a list of the orphaned packages which I think
> > it's a bit more readable:
> >
> > ...
> > - rpms/celestia
> >
> Taken and added astro-sig as co-maintainer, I'll try to update it to the
> latest version.
> >
> > ...
> > - rpms/python-simplemediawiki.
> >
> Taken as well, as it is needed by Bodhi, until I manage to port it to
> python-pymediawiki.
>
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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: F39 proposal: Replace DNF with DNF5 (System-Wide Change proposal)

[Jonathan Wright via devel]

Constantly changing the name/command of the package manager seems like a
huge annoyance to end users at best, and a point of discouragement at worst.

Think about all the guides that can be found via search engines for how to
do things in a given OS.  If we're constantly changing the package
manager/command, even if syntax is similar or identical, it's raising the
bar of entry for inexperienced users.

For this reason I think it makes far more sense to let "dnf5" eventually
just become "dnf" even if that means some features/flags are simply dropped.

On Wed, Oct 12, 2022 at 10:15 AM Alexander Sosedkin 
wrote:

> On Wed, Oct 12, 2022 at 4:47 PM Stephen Smoogen 
> wrote:
> > On Wed, 12 Oct 2022 at 10:32, Kevin P. Fleming 
> wrote:
> >> On 10/12/22 08:59, Stephen Smoogen wrote:
> >> > Maybe call it the Fedora Update Manager 'FUM' ?
> >>
> >> Unless we're going to call it RUM when it makes its way into RHEL, that
> >> name may not be the best choice :-)
> >
> > Well Red Hat shipped the Yellowdog Update Manager for 2 releases so I am
> sure they can go with FUM or RUM (RPM Update Manager).. I would avoid
> Backup Upgrade Manager though.
>
> Ugh, acronyms, how boring.
> If we stay true to the abbreviation equilibristics
> that gave us DNF coming from DaNdiFied YUM,
> it's only natural to name the ApPoinTed DNF successor APT. =)
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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: Capstone (was: Re: Orphaned packages looking for new maintainers)

[Jonathan Wright via devel]

I have some packages that rely on this so I'm happy to jump on as a
co-maintainer.  Giving someone else a chance to take lead but if no one
else does I'll pick it up.

On Mon, Oct 10, 2022 at 1:57 PM drago01  wrote:

> On Mon, Oct 10, 2022 at 11:11 AM Richard W.M. Jones 
> wrote:
> >
> > On Mon, Oct 10, 2022 at 10:31:24AM +0200, Miro Hrončok wrote:
> > > capstone  orphan, rebus, ret2libc  1
> weeks ago
> >
> > [Affecting lots of packages]
> >
> > This is a disassembly library / framework used by qemu.  It seems like
> > it has two maintainers so I guess it's not really an orphan, but I can
> > take the package if neither of the two existing maintainers wants to
> > become owner.
> >
>
> Its FTBS because of the java bindings (removed deps): see
> https://koji.fedoraproject.org/koji/taskinfo?taskID=92887668 /
>
> https://koji.fedoraproject.org/koji/getfile?taskID=92887668=DEFAULT=mock_output.log=-4000
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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: python-pandas has been orphaned - needs a new primary maintainer.

[Jonathan Wright via devel]

Absolutely.  The more help the merrier.

On Thu, Sep 29, 2022 at 3:01 AM Sandro  wrote:

> On 29-09-2022 03:44, Orion Poplawski wrote:
> > Looks like python-pandas has been orphaned.  Is anyone interested in
> > taking it on?  I've done some drive by work (and have maintained it in
> > EPEL), but I already have too many packages.
>
> Thank you Jonathan (jonathanspw) for adopting python-pandas.
>
> I'll bring this up at the next neuro-sig meeting. They might be willing
> to co-maintain, if you are interested.
>
> -- Sandro
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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: python-pandas has been orphaned - needs a new primary maintainer.

[Jonathan Wright via devel]

I threw my name on it.  Will go through its current state in the next few
days.

On Wed, Sep 28, 2022 at 8:45 PM Orion Poplawski  wrote:

> Looks like python-pandas has been orphaned.  Is anyone interested in
> taking it on?  I've done some drive by work (and have maintained it in
> EPEL), but I already have too many packages.
>
> Thanks,
>Orion
>
> --
> Orion Poplawski
> he/him/his  - surely the least important thing about me
> IT Systems Manager 720-772-5637
> NWRA, Boulder/CoRA Office FAX: 303-415-9702
> 3380 Mitchell Lane   or...@nwra.com
> Boulder, CO 80301 https://www.nwra.com/
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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: Inactive packagers to be removed after the F37 release

[Jonathan Wright via devel]

On Tue, Sep 6, 2022 at 3:52 PM Vitaly Zaitsev via devel <
devel@lists.fedoraproject.org> wrote:

> On 06/09/2022 19:49, Michael Catanzaro wrote:
> > Of course, hardware authenticators would be even more secure, and it
> > sure seems pretty reasonable to expect that people with commit access to
> > Fedora packages are able to purchase a $25 or 30€ security key [1][2].
>
> Having to pay even $25 for a hobby project is not acceptable, IMO. If
> you want to enforce such a policy, find sponsors and buy devices for all
> Fedora contributors.
>
Fedora must be looked at as more than just a "hobby project" even though it
is a hobby for some.

It's an OS that many rely on and $25 is a somewhat trivial cost for
improved security.

With your suggestion of sponsors to cover such devices - how does that work
for new packagers?  It seems pretty impossible to do such a thing and tons
of money would simply be wasted on packagers that did very little to
nothing after becoming a packager.

>
> --
> Sincerely,
>Vitaly Zaitsev (vit...@easycoding.org)
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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

[Jonathan Wright via devel]

I'm happy to help maintain the python packages.

FAS: jonathanspw

On Mon, Sep 5, 2022 at 11:00 AM Ankur Sinha  wrote:

> I've taken a few more (a few for the neuro-sig):
>
> > Depending on: mcpanel (1), status change: 2022-08-30 (0 weeks ago)
> >   eegview (maintained by: aekoroglu, ankursinha, neuro-sig)
> >   eegview-0.0-15.fc37.src requires mcpanel-devel =
> 0.0-15.fc37
> >   eegview-0.0-15.fc37.x86_64 requires
> libmcpanel.so.0()(64bit)
>
> Taken for neuro-sig, co-maintainers welcome
>
> > Depending on: python-aiofiles (5), status change: 2022-08-30 (0 weeks
> ago)
> > 
> >
> >   python-matrix-nio (maintained by: ankursinha)
> >   python-matrix-nio-0.19.0-6.fc38.src requires
> python3dist(aiofiles) = 0.7
> >   python3-matrix-nio-0.19.0-6.fc38.noarch requires
> python3.11dist(aiofiles) = 0.7
>
> Taken for myself, co-maintainers welcome.
>
> > Depending on: python-piexif (3), status change: 2022-08-30 (0 weeks ago)
> >
> >   vimiv-qt (maintained by: ankursinha)
> >   vimiv-qt-0.8.0-7.fc37.x86_64 requires python3-piexif =
> 1.1.3-14.fc37
>
> Taken for myself, co-maintainers welcome.
>
> > Depending on: python-rply (4), status change: 2022-08-30 (0 weeks ago)
> >   python-rnc2rng (maintained by: iztokf)
> >   python-rnc2rng-2.6.6-3.fc37.src requires python3dist(rply)
> = 0.7.8
> >   python3-rnc2rng-2.6.6-3.fc37.noarch requires
> python3.11dist(rply) = 0.7.8
> >
> >   python-citeproc-py (maintained by: ankursinha, ignatenkobrain,
> neuro-sig)
> >   python-citeproc-py-0.6.0-5.fc37.src requires
> python3dist(rnc2rng) = 2.6.6
> >
> >   python-duecredit (maintained by: ankursinha, neuro-sig)
> >   python-duecredit-0.9.1-5.fc37.src requires
> python3dist(citeproc-py) = 0.6
> >   python3-duecredit-0.9.1-5.fc37.noarch requires
> python3.11dist(citeproc-py)
> > = 0.6, python3dist(citeproc-py) = 0.6
> >
> >   python-pybids (maintained by: ankursinha, neuro-sig)
> >   python-pybids-0.13.1-5.fc37.src requires
> python3dist(duecredit) = 0.9.1
>
> Taken for neuro-sig, co-maintainers welcome
>
> > Depending on: rtfilter (2), status change: 2022-08-30 (0 weeks ago)
> >   mcpanel (maintained by: orphan)
> >   mcpanel-0.0-15.fc37.i686 requires librtfilter.so.1
> >   mcpanel-0.0-15.fc37.src requires rtfilter-devel =
> 1.1-16.fc37
> >   mcpanel-0.0-15.fc37.x86_64 requires
> librtfilter.so.1()(64bit)
> >
> >   eegview (maintained by: aekoroglu, ankursinha, neuro-sig)
> >   eegview-0.0-15.fc37.src requires mcpanel-devel =
> 0.0-15.fc37
> >   eegview-0.0-15.fc37.x86_64 requires
> libmcpanel.so.0()(64bit)
>
> Taken for neuro-sig, co-maintainers welcome
>
> --
> Thanks,
> Regards,
> Ankur Sinha "FranciscoD" (He / Him / His) |
> https://fedoraproject.org/wiki/User:Ankursinha
> Time zone: Europe/London
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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: Package review swap: ubdsrv - Userspace block driver server

[Jonathan Wright via devel]

Ah I see you got someone.

On Tue, Aug 30, 2022 at 3:19 PM Jonathan Wright 
wrote:

> I'll trade you for a basic Python package:
> https://bugzilla.redhat.com/show_bug.cgi?id=2121258
>
> On Tue, Aug 30, 2022 at 6:56 AM Richard W.M. Jones 
> wrote:
>
>>
>> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2122605
>>
>> Pretty simple package, just a small library and a single tool.
>>
>> This bug depends on a change to the Rawhide kernel configuration
>> before it will work (https://bugzilla.redhat.com/2122595) but I don't
>> think that needs to get in the way of the review.
>>
>> Will swap for something which isn't _too_ complicated(!)
>>
>> Rich.
>>
>> --
>> Richard Jones, Virtualization Group, Red Hat
>> http://people.redhat.com/~rjones
>> Read my programming and virtualization blog: http://rwmj.wordpress.com
>> libguestfs lets you edit virtual machines.  Supports shell scripting,
>> bindings from many languages.  http://libguestfs.org
>> ___
>> 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
>>
>
>
> --
> Jonathan Wright
> AlmaLinux Foundation
> Mattermost: chat 
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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: Package review swap: ubdsrv - Userspace block driver server

[Jonathan Wright via devel]

I'll trade you for a basic Python package:
https://bugzilla.redhat.com/show_bug.cgi?id=2121258

On Tue, Aug 30, 2022 at 6:56 AM Richard W.M. Jones 
wrote:

>
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2122605
>
> Pretty simple package, just a small library and a single tool.
>
> This bug depends on a change to the Rawhide kernel configuration
> before it will work (https://bugzilla.redhat.com/2122595) but I don't
> think that needs to get in the way of the review.
>
> Will swap for something which isn't _too_ complicated(!)
>
> Rich.
>
> --
> Richard Jones, Virtualization Group, Red Hat
> http://people.redhat.com/~rjones
> Read my programming and virtualization blog: http://rwmj.wordpress.com
> libguestfs lets you edit virtual machines.  Supports shell scripting,
> bindings from many languages.  http://libguestfs.org
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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: Sympy 1.11 (review swaps)

[Jonathan Wright via devel]

I'll start on yours if you'll start on mine, I have a pile of my own :)

https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW=Package%20Review=jonathan%40almalinux.org=1=equals_name=My%20review%20requests_id=12864886=Fedora_based_on=My%20review%20requests_format=advanced

On Thu, Aug 25, 2022 at 8:38 PM Jerry James  wrote:

> I'm working on an update to sympy, to version 1.11.  This version has
> several backwards incompatible changes.  I inspected the consuming
> packages for use of the backwards incompatible APIs and found none.
> Just in case, I did local mock builds of each one, and the builds were
> all successful, including runs of their test suites.  The consuming
> packages are:
>
> - python-boutdata
> - python-brian2
> - python-fiat
> - python-nipy
> - python-pysb
> - python-trimesh
> - sagemath
>
> It is no longer possible to build the sympy documentation, due to
> missing dependencies.  However, I have already noted other packages I
> maintain that need each of these.  That tells me it is time to get
> them into Fedora.  I would like to swap reviews for the following:
>
> - python-sphinx-basic-ng:
> https://bugzilla.redhat.com/show_bug.cgi?id=2121593
> - python-furo: https://bugzilla.redhat.com/show_bug.cgi?id=2121594,
> needs python-sphinx-basic-ng
> - python-uc-micro-py: https://bugzilla.redhat.com/show_bug.cgi?id=2121595
> - python-linkify-it-py:
> https://bugzilla.redhat.com/show_bug.cgi?id=2121596, needs
> python-uc-micro-py
> - python-sphinx-documatt-theme:
> https://bugzilla.redhat.com/show_bug.cgi?id=2121597
> - python-sphinx-reredirects:
> https://bugzilla.redhat.com/show_bug.cgi?id=2121598, needs
> python-sphinx-documatt-theme
>
> Let me know what I can review for you.
> --
> Jerry James
> http://www.jamezone.org/
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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

[Jonathan Wright via devel]

I'm working on some of the deps for mailman3/hyperkitty.

I should have the python-flufl-lock dep solved for you.

On Mon, Aug 22, 2022 at 12:04 PM Michel Alexandre Salim <
sali...@fedoraproject.org> wrote:

> On Mon, Aug 22, 2022 at 01:07:26PM +0200, 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
> >
> > mailman3   infra-sig, orphan, salimma  0
> weeks ago
> > monkeytype orphan  0
> weeks ago
>
> Picked these back up - will try and address the issues this week, sorry
> for the delay.
>
> > rubygem-asciidoctor-pdfabradshaw, ckyriakidou, evgeni, 0
> weeks ago
> >fale, orphan, snecker
> > rubygem-chunky_png mmorsi, orphan, snecker 0
> weeks ago
> > rubygem-css_parser abradshaw, ckyriakidou, evgeni, 0
> weeks ago
> >fale, orphan, snecker
> > rubygem-font-awesome-rails abradshaw, ckyriakidou, evgeni, 0
> weeks ago
> >fale, orphan, snecker
> > rubygem-prawn-icon abradshaw, ckyriakidou, evgeni, 0
> weeks ago
> >fale, orphan, snecker
> > rubygem-prawn-manual_builder   abradshaw, ckyriakidou, evgeni, 0
> weeks ago
> >fale, orphan, snecker
> > rubygem-prawn-svg  abradshaw, ckyriakidou, evgeni, 0
> weeks ago
> >fale, orphan, snecker
> > rubygem-prawn-templatesabradshaw, ckyriakidou, evgeni, 0
> weeks ago
> >fale, orphan, snecker
> ^ these will probably break a lot of documentation builds - one of my
> package (nickle) is affected. Not sure I have the bandwith to help fix
> this though.
>
> Best regards,
>
> --
> Michel Alexandre Salim
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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: Wine/FAudio & self introduction.

[Jonathan Wright via devel]

Welcome to Fedora :)

On Mon, Aug 22, 2022 at 5:53 PM Aaron Stern via devel <
devel@lists.fedoraproject.org> wrote:

> Greetings all.
>
> My name is Aaron, I contribute packages for openSUSE (
> https://build.opensuse.org/users/ukbeast89) and am looking to help bring
> updates to wine and FAudio.
> I have already created a PR for FAudio (
> https://src.fedoraproject.org/rpms/FAudio/pull-request/2) as a way to get
> my feet wet with Fedora's way of packaging.
>
> If anyone has any questions about me or my experience in Linux, please ask.
>
> Regards. Aaron.
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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: Review swap : blueprint-compiler

[Jonathan Wright via devel]

I'm happy to trade for https://bugzilla.redhat.com/show_bug.cgi?id=2118887

On Sun, Aug 21, 2022 at 1:03 PM Lyes Saadi 
wrote:

> Hello devel!
>
> I have new dependency I need to update dialect to 2.0. It's been waiting
> since july, so I'm proposing a review swap. It's the python/meson
> guidelines.
>
> blueprint-compiler : https://bugzilla.redhat.com/show_bug.cgi?id=2106919
>
> Regards,
> Lyes Saadi
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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: nspawn for rawhide?

[Jonathan Wright via devel]

Do it!

On Thu, Aug 18, 2022, 4:01 PM Kevin Fenzi  wrote:

> Greetings everyone.
>
> Many years ago mock introduced and then made default it's isolation to
> use systemd-nspawn instead of chroot. Shortly after the nspawn isolation
> was added, it was used in fedoraproject koji builds, but there were
> issues and since then the fedoraproject koji has defaulted to using
> chroot isolation.
>
> Releng has had a ticket open for a long time to switch
> ( https://pagure.io/releng/issue/6967 )
>
> I think the two items listed there (kernel bind mounts and loop devices)
> have long since been fixed, so I would like to propose we switch rawhide
> to using nspawn and see if any other issues show up.
>
> If everyone is ok with it, I can enable it (just for rawhide) and we can
> look for issues with composes or any other items. At least then we would
> have a good list of things we would like to fix. If it turns out things
> just work ok we can leave it enabled.
>
> I think moving to this will:
> * More closely match developers local test mock builds.
> * Provide better isolation for builds
> * Help with resources as systemd-nspawn is a lot more cgroup aware than
> chroot
> * Allow us to close a 5 year old ticket. ;)
>
> Thoughts?
>
> kevin
> ___
> 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: fedora-create-review error message

[Jonathan Wright via devel]

He's using this:

fedora-review-0.8.0-1.fc36.noarch : Review tool for fedora rpm packages
Repo: updates
Matched from:
Filename: /usr/bin/fedora-create-review

I get the same error.

On Mon, Aug 8, 2022 at 4:15 PM Kevin Fenzi  wrote:

> On Sun, Aug 07, 2022 at 08:27:19PM -0500, Richard Shaw wrote:
> > I'm working on a package review for libphidget22 (rename of libphidget),
> > but after typing in my bugzilla credentials I get the following:
> >
> >  > The method 'Bug.get' is not supported without using API keys and the the
> > authentication header. See
> >
> https://bugzilla.redhat.com/docs/en/html/api/core/v1/general.html#authentication
> > for details on using the 'Authorization' header. at
> > /usr/share/perl5/vendor_perl/SOAP/Lite.pm line 2855.\n">
> >
> > Haven't seen this before, but I haven't submitted a new package in a
> while
> > either.
>
> How are you trying to create the review request?
>
> ie, what are you typing your bugzilla credentials into?
>
> The web page should work:
>
> https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora=fedora-review
> (after logging in)
>
> But it sounds like you might be using some script or tool?
>
> If so, you need to get a api key and use that. scripts are no longer
> allowed to login with username/password.
>
> Go to account -> preferences -> api keys
>
> create a new api key
>
> If you are using python-bugzilla then you should be able to put that api
> key in ~/.config/python-bugzilla/bugzillarc
>
> As so:
>
> [bugzilla.redhat.com]
> api_key=THEAPIKEY
>
> kevin
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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

Non-responsive maintainer check for hguemar

[Jonathan Wright via devel]

Per the unresponsive package maintainer policy I'm checking if anyone has a
way to contact  Haïkel Guémar  (FAS hguemar).

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

Lack of updates to one of his packages, python-pyperclip is holding up
other packages.

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

LinkedIn lists him as a RH employee.  Would anyone have his @redhat.com
address by chance?

-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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

[Jonathan Wright via devel]

I've taken ownership of RBTools, csound, and gpart.

On Tue, Aug 2, 2022 at 4:50 AM 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
>
> Note: If you received this mail directly you (co)maintain one of the
> affected
> packages or a package that depends on one. Please adopt the affected
> package or
> retire your depending package to avoid broken dependencies, otherwise your
> package will fail to install and/or build when the affected package gets
> retired.
>
> Request package ownership via the *Take* button in he left column on
> https://src.fedoraproject.org/rpms/
>
> Full report available at:
> https://churchyard.fedorapeople.org/orphans-2022-08-02.txt
> grep it for your FAS username and follow the dependency chain.
>
> For human readable dependency chains,
> see https://packager-dashboard.fedoraproject.org/
> For all orphaned packages,
> see https://packager-dashboard.fedoraproject.org/orphan
>
> Package (co)maintainers Status Change
> 
> RBTools  orphan3 weeks ago
> csound   orphan0 weeks ago
> evolution-rssmcrha, orphan 3 weeks ago
> ez-pine-gpg  orphan4 weeks ago
> fawkes   orphan, rmattes, timn 2 weeks ago
> gpartdcantrell, orphan 4 weeks ago
> lancer   orphan0 weeks ago
> libnss-pgsql orphan3 weeks ago
> module-macrosorphan4 weeks ago
> python-bigsuds   orphan1 weeks ago
> rpkg-utilorphan4 weeks ago
> sourcetrail  orphan3 weeks ago
> test-interface   orphan0 weeks ago
> topedorphan, tnorth2 weeks ago
> zuul openstack-sig, orphan, zuul   6 weeks ago
>
> The following packages require above mentioned packages:
> Depending on: rpkg-util (1), status change: 2022-07-02 (4 weeks ago)
> copr-rpmbuild (maintained by: copr-sig, dturecek, frostyx,
> praiskup)
> copr-builder-0.60-1.fc37.x86_64 requires rpkg = 3.2-3.fc37
>
> Depending on: test-interface (1), status change: 2022-08-01 (0 weeks ago)
> scalacheck (maintained by: jjames)
> scalacheck-1.16.0-3.fc37.noarch requires
> mvn(org.scala-sbt:test-interface) = 1.0
> scalacheck-1.16.0-3.fc37.src requires
> mvn(org.scala-sbt:test-interface) = 1.0
>
> See dependency chains of your packages at
> https://packager-dashboard.fedoraproject.org/
> See all orphaned packages at
> https://packager-dashboard.fedoraproject.org/orphan
>
> Affected (co)maintainers (either directly or via packages' dependencies):
> copr-sig: rpkg-util
> dcantrell: gpart
> dturecek: rpkg-util
> frostyx: rpkg-util
> jjames: test-interface
> mcrha: evolution-rss
> openstack-sig: zuul
> praiskup: rpkg-util
> rmattes: fawkes
> timn: fawkes
> tnorth: toped
> zuul: zuul
>
> --
> The script creating this output is run and developed by Fedora
> Release Engineering. Please report issues at its pagure instance:
> https://pagure.io/releng/
> The sources of this script can be found at:
> https://pagure.io/releng/blob/main/f/scripts/find_unblocked_orphans.py
>
> Report finished at 2022-08-02 09:27:07 UTC
> ___
> 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
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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

Orphaned package dnstracer takeover

[Jonathan Wright via devel]

Hi,

I'd like to take over the orphaned package dnstracer.  
https://src.fedoraproject.org/rpms/dnstracer

I submitted a ticket with releng for this as there was no "take" button present.

https://pagure.io/releng/issue/10915

My username is jonathanspw
___
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