[Bug 2270514] perl-CPAN-Perl-Releases-5.20240321 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-CPAN-Perl-Releases-5.2 |perl-CPAN-Perl-Releases-5.2
   |0240321-1.fc41  |0240321-1.fc41
   ||perl-CPAN-Perl-Releases-5.2
   ||0240321-1.fc40



--- Comment #9 from Fedora Update System  ---
FEDORA-2024-1d89caddb4 (perl-CPAN-Perl-Releases-5.20240321-1.fc40) has been
pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2270514

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202270514%23c9
--
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2270521] perl-Module-CoreList-5.20240320 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-Module-CoreList-5.2024 |perl-Module-CoreList-5.2024
   |0320-1.fc41 |0320-1.fc41
   ||perl-Module-CoreList-5.2024
   ||0320-1.fc40



--- Comment #8 from Fedora Update System  ---
FEDORA-2024-054b591230 (perl-Module-CoreList-5.20240320-1.fc40) has been pushed
to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2270521

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202270521%23c8
--
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[rpms/perl-Module-Build-WithXSpp] PR #1: Convert to %autorelease and %autochangelog

[Miro Hrončok]

churchyard merged a pull-request against the project: 
`perl-Module-Build-WithXSpp` that you are following.

Merged pull-request:

``
Convert to %autorelease and %autochangelog
``

https://src.fedoraproject.org/rpms/perl-Module-Build-WithXSpp/pull-request/1
--
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[rpms/perl-Wx-GLCanvas] PR #3: Convert to %autorelease and %autochangelog

[Miro Hrončok]

churchyard merged a pull-request against the project: `perl-Wx-GLCanvas` that 
you are following.

Merged pull-request:

``
Convert to %autorelease and %autochangelog
``

https://src.fedoraproject.org/rpms/perl-Wx-GLCanvas/pull-request/3
--
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[rpms/perl-ExtUtils-Typemaps-Default] PR #1: Convert to %autorelease and %autochangelog

[Miro Hrončok]

churchyard merged a pull-request against the project: 
`perl-ExtUtils-Typemaps-Default` that you are following.

Merged pull-request:

``
Convert to %autorelease and %autochangelog
``

https://src.fedoraproject.org/rpms/perl-ExtUtils-Typemaps-Default/pull-request/1
--
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[rpms/perl-Growl-GNTP] PR #1: Convert to %autorelease and %autochangelog

[Miro Hrončok]

churchyard merged a pull-request against the project: `perl-Growl-GNTP` that 
you are following.

Merged pull-request:

``
Convert to %autorelease and %autochangelog
``

https://src.fedoraproject.org/rpms/perl-Growl-GNTP/pull-request/1
--
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[rpms/perl-ExtUtils-CppGuess] PR #2: Convert to %autorelease and %autochangelog

[Miro Hrončok]

churchyard merged a pull-request against the project: `perl-ExtUtils-CppGuess` 
that you are following.

Merged pull-request:

``
Convert to %autorelease and %autochangelog
``

https://src.fedoraproject.org/rpms/perl-ExtUtils-CppGuess/pull-request/2
--
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Non-responsive maintainer landgraf for package aunit.

[Björn Persson]

Pavel Zhukov wrote:
> I see you have received review of the MR .  Emails have been answered by 
> Bjorn too.

If you don't have time to maintain Aunit, then please give me or Dennis
access to the package so we can take care of it.

Björn Persson


pgpFCmfiDkSCT.pgp
Description: OpenPGP digital signatur
--
___
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: Non-responsive maintainer landgraf for package aunit.

[Dennis van Raaij]

Hi Pavel,

Thanks for your response.

> I see you have received review of the MR .

Yes, indeed. I'm grateful that Bjorn was willing to have look at the PR despite 
not being a co-maintainer of the package.

> Emails have been answered by Bjorn too.

Yes, but I got no reply from you as the sole maintainer of package aunit.

So, would you be willing to have a look at the PR and consider it for updating 
the package?

- Dennis
--
___
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: Non-responsive maintainer landgraf for package aunit.

[Pavel Zhukov]

I see you have received review of the MR .  Emails have been answered by Bjorn 
too.

--
Pavel


On Thu, Mar 28, 2024, at 20:17, Dennis van Raaij wrote:
> Hi,
> 
> I've been trying to contact package maintainer Pavel Zhukov (landgraf).
> 
> I submitted a proposal to update package 'aunit' some months ago [1] but
> received no response from its maintainer, Pavel Zhukov. This proposal 
> supersedes
> an earlier one for which I received no response either. I tried to contact him
> by email [2] but did not receive a reply.
> 
> As I have no other way to get in contact, and as the PR has been open for
> months, I've decided to submit a bug [3] and post here as per Fedora 
> guidelines
> on non-responsive maintainers.
> 
> - Dennis
> 
> [1] https://src.fedoraproject.org/rpms/aunit/pull-request/2
> [2] https://accounts.fedoraproject.org/user/landgraf/?
> [3] https://bugzilla.redhat.com/show_bug.cgi?id=2272094
> --
> ___
> 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

Non-responsive maintainer landgraf for package aunit.

[Dennis van Raaij]

Hi,

I've been trying to contact package maintainer Pavel Zhukov (landgraf).

I submitted a proposal to update package 'aunit' some months ago [1] but
received no response from its maintainer, Pavel Zhukov. This proposal supersedes
an earlier one for which I received no response either. I tried to contact him
by email [2] but did not receive a reply.

As I have no other way to get in contact, and as the PR has been open for
months, I've decided to submit a bug [3] and post here as per Fedora guidelines
on non-responsive maintainers.

- Dennis

[1] https://src.fedoraproject.org/rpms/aunit/pull-request/2
[2] https://accounts.fedoraproject.org/user/landgraf/?
[3] https://bugzilla.redhat.com/show_bug.cgi?id=2272094
--
___
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?

[Carlos Rodriguez-Fernandez]

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 



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
 


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

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

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

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

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

[Carlos Rodriguez-Fernandez]

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 



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

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


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

Heads up: planning to retire libgee06

[Michel Lind]

Dear all,

Just a heads up that the legacy libgee06 package is FTBFS for
F40/F41:

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

and only has one dependent, libfep:

```
❯ fedrq whatrequires libgee06-devel
libfep-0.1.0-24.fc40.src

❯ fedrq whatrequires libgee06-devel -b f39
libfep-0.1.0-22.fc39.src

❯ fedrq whatrequires libfep-devel -b f39
ibus-fep-1.4.4-23.fc39.src
libskk-1.0.4-12.fc39.src
```

Since libfep itself has dependents, I checked and it looks like it does
not actually need libgee06 (or libgee) - or not anymore - and rebuilding
it with the BR dropped succeeds with virtually the same Requires and
Provides in the generated RPMs:

https://src.fedoraproject.org/rpms/libfep/pull-request/1

I'm cc:ing the libfep maintainers; if I don't hear back in a few days
I'll merge and build this and retire the package.

Best regards,

-- 
Michel Lind
identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2


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

Re: Feedback wanted: Kvantum 1.1.0 spec changes

[Neal Gompa]

On Thu, Mar 28, 2024 at 10:33 AM Arthur Bols  wrote:
>
> On 28/03/2024 12:22, Neal Gompa wrote:
> > On Thu, Mar 28, 2024 at 6:11 AM Arthur Bols  wrote:
> > This seems reasonable to me. Do we have any packaged themes that need
> > to be adjusted alongside it?
> Thanks for taking a look!
>
> I don't think so. There is nothing breaking in the changelog for themes
> and everything still works fine on my systems. Themes should require the
> kvantum package and put their files in /usr/share/Kvantum, so
> packaging-wise everything stays the same.
>

Then I say let's do it. :)



-- 
真実はいつも一つ！/ 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

Re: Feedback wanted: Kvantum 1.1.0 spec changes

[Arthur Bols]

On 28/03/2024 12:22, Neal Gompa wrote:

On Thu, Mar 28, 2024 at 6:11 AM Arthur Bols  wrote:
This seems reasonable to me. Do we have any packaged themes that need
to be adjusted alongside it?

Thanks for taking a look!

I don't think so. There is nothing breaking in the changelog for themes 
and everything still works fine on my systems. Themes should require the 
kvantum package and put their files in /usr/share/Kvantum, so 
packaging-wise everything stays the same.


--
Arthur Bols
fas/irc: principis
--
___
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

Heads-up: Updating python-keyring to 25.0.0 in F41/Rawhide

[Ben Beasley]

In one week (2024-04-04), or slightly later, I plan to update the 
python-keyring package to 25.0.0 in F41/Rawhide[1]. Upstream reports[2]:


v25.0.0
===

Deprecations and Removals
-

- Removed check for config in XDG_DATA_HOME on Linux systems. (#99)
- In platform config support, remove support for Windows XP, now 10 years 
sunset.

All dependent packages rebuilt successfully in a COPR impact check[3], 
except yubikey-manager, which can be fixed by removing an upper-bound on 
the version of typer[4]. If there is no response to that PR by 
2024-04-04, I will use provenpackager privileges to merge and build it 
along with the python-keyring update.


[1] https://src.fedoraproject.org/rpms/python-keyring/pull-request/26

[2] https://github.com/jaraco/keyring/blob/v25.0.0/NEWS.rst#v2500

[3] https://copr.fedorainfracloud.org/coprs/music/python-keyring/packages/

[4] https://src.fedoraproject.org/rpms/yubikey-manager/pull-request/5
--
___
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

Fedora rawhide compose report: 20240328.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20240327.n.0
NEW: Fedora-Rawhide-20240328.n.0

= SUMMARY =
Added images:1
Dropped images:  1
Added packages:  2
Dropped packages:0
Upgraded packages:   76
Downgraded packages: 0

Size of added packages:  6.72 MiB
Size of dropped packages:0 B
Size of upgraded packages:   2.62 GiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   9.83 MiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: Workstation live aarch64
Path: 
Workstation/aarch64/iso/Fedora-Workstation-Live-aarch64-Rawhide-20240328.n.0.iso

= DROPPED IMAGES =
Image: Silverblue ociarchive ppc64le
Path: 
Silverblue/ppc64le/images/Fedora-Silverblue-Rawhide.20240327.n.0.ociarchive

= ADDED PACKAGES =
Package: redict-7.3.0~rc1-1.fc41
Summary: A persistent key-value database
RPMs:redict redict-devel
Size:6.50 MiB

Package: tpm2-openssl-1.2.0-2.fc41
Summary: Provider for integration of TPM 2.0 to OpenSSL 3.0
RPMs:tpm2-openssl
Size:225.84 KiB


= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  PDAL-2.7.1-1.fc41
Old package:  PDAL-2.7.0-1.fc41
Summary:  Point Data Abstraction Library
RPMs: PDAL PDAL-devel PDAL-doc PDAL-libs
Size: 45.36 MiB
Size change:  -23.30 KiB
Changelog:
  * Wed Mar 27 2024 Sandro Mani  - 2.7.1-1
  - Update to 2.7.1


Package:  asciigraph-0.6.0-1.fc41
Old package:  asciigraph-0.5.6-5.fc40
Summary:  Makes lightweight ASCII line graphs
RPMs: asciigraph golang-github-guptarohit-asciigraph-devel
Size: 2.47 MiB
Size change:  4.39 KiB
Changelog:
  * Wed Mar 27 2024 Major Hayden  - 0.6.0-1
  - Update to 0.6.0 rhbz#2271407


Package:  buildah-1.35.2-2.fc41
Old package:  buildah-1.35.0-1.fc41
Summary:  A command line tool used for creating OCI Images
RPMs: buildah buildah-tests
Size: 159.50 MiB
Size change:  290.30 KiB
Changelog:
  * Mon Mar 18 2024 Packit  - 1.35.1-1
  - [packit] 1.35.1 upstream release

  * Tue Mar 26 2024 Packit  - 1.35.2-1
  - [packit] 1.35.2 upstream release

  * Wed Mar 27 2024 Ed Santiago  - 1.35.2-2
  - Gating tests: require slirp4netns


Package:  cabal-rpm-2.2.0-1.fc41
Old package:  cabal-rpm-2.1.5-4.fc40
Summary:  RPM packaging tool for Haskell Cabal-based packages
RPMs: cabal-rpm
Size: 42.74 MiB
Size change:  41.95 KiB
Changelog:
  * Wed Mar 27 2024 Jens Petersen  - 2.2.0-1
  - https://hackage.haskell.org/package/cabal-rpm-2.2.0/changelog
  - spec: generate manpage for optparse-applicative programs
  - spec: add %{?haskell_setup}


Package:  cairo-dock-plug-ins-3.5.0-4.fc41
Old package:  cairo-dock-plug-ins-3.5.0-3.fc41
Summary:  Plug-ins files for Cairo-Dock
RPMs: cairo-dock-plug-ins cairo-dock-plug-ins-base 
cairo-dock-plug-ins-common cairo-dock-plug-ins-dbus cairo-dock-plug-ins-kde 
cairo-dock-plug-ins-unstable cairo-dock-plug-ins-webkit 
cairo-dock-plug-ins-xfce cairo-dock-python3 cairo-dock-ruby cairo-dock-vala 
cairo-dock-vala-devel
Size: 17.40 MiB
Size change:  3.03 KiB
Changelog:
  * Wed Mar 27 2024 Mamoru TASAKA  - 3.5.0-4
  - Fix invalid SPDX tag


Package:  caribou-0.4.21-39.fc41
Old package:  caribou-0.4.21-38.fc40
Summary:  A simplified in-place on-screen keyboard
RPMs: caribou caribou-antler caribou-devel caribou-gtk2-module 
caribou-gtk3-module python3-caribou
Size: 1.25 MiB
Size change:  1.14 KiB
Changelog:
  * Wed Mar 27 2024 Leigh Scott  - 0.4.21-39
  - Fix buildrequires


Package:  clover2-11.0.0-7.fc41
Old package:  clover2-11.0.0-6.fc41
Summary:  Yet another compiler language
RPMs: clover2 clover2-devel clover2-libs
Size: 3.68 MiB
Size change:  32.12 KiB
Changelog:
  * Wed Mar 27 2024 Mamoru TASAKA  - 11.0.0-7
  - Remove unneeded subpackge License tag


Package:  cockpit-machines-310-1.fc41
Old package:  cockpit-machines-309-1.fc41
Summary:  Cockpit user interface for virtual machines
RPMs: cockpit-machines
Size: 1.11 MiB
Size change:  2.28 KiB
Changelog:
  * Wed Mar 27 2024 Packit  - 310-1
  - Bug fixes and performance improvements


Package:  cockpit-ostree-1:201-1.fc41
Old package:  cockpit-ostree-1:200-1.fc41
Summary:  Cockpit user interface for rpm-ostree
RPMs: cockpit-ostree
Size: 473.56 KiB
Size change:  -10.86 KiB
Changelog:
  * Wed Mar 27 2024 Packit  - 1:201-1
  - Show OCI container origin


Package:  cockpit-podman-86-1.fc41
Old package:  cockpit-podman-85-1.fc41
Summary:  Cockpit component for Podman containers
RPMs: cockpit-podman
Size: 680.73 KiB
Size change:  1.42 KiB
Changelog:
  * Wed Mar 27 2024 Packit  - 86-1
  - Bug fixes and performance improvements


Package:  crun-1.14.4-5.fc41
Old package:  crun-1.14.4-1.fc41
Summary:  OCI runtime written in C
RPMs: crun crun-krun crun-wasm
Size: 964.03 KiB
Size change:  -35.26 KiB
Changelog:
  * Tue Mar 05 2024 Giuseppe Scrivano

Heads-up: updating flatbuffers to 24.3.25 in F41/Rawhide

[Ben Beasley]

I know, we just did flatbuffers 24.3.7, but there is a bugfix update, 
24.3.25, and the ABI and SONAME version always break, so here we go again!


In one week (2024-04-04), or slightly later, I plan to update the 
flatbuffers package to 24.3.25 in F41/Rawhide[1]. As usual, this 
includes an SONAME version bump. Upstream follows calendar versioning 
and does not attempt to keep the ABI stable across releases.


Unless a maintainer asks me to do otherwise, I will use provenpackager 
privileges to rebuild the dependent packages in a side tag:


    - hyperhdr

    - onnxruntime

    - qdigidoc

All of these are expected to rebuild successfully in a COPR impact 
check[2], currently in progress.


[1] https://src.fedoraproject.org/rpms/flatbuffers/pull-request/9

[2] https://copr.fedorainfracloud.org/coprs/music/flatbuffers/packages/

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

Fedora 40 compose report: 20240328.n.0 changes

[Fedora Branched Report]

OLD: Fedora-40-20240327.n.0
NEW: Fedora-40-20240328.n.0

= SUMMARY =
Added images:1
Dropped images:  1
Added packages:  1
Dropped packages:0
Upgraded packages:   141
Downgraded packages: 0

Size of added packages:  4.18 MiB
Size of dropped packages:0 B
Size of upgraded packages:   1.49 GiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   66.70 MiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: Workstation live aarch64
Path: 
Workstation/aarch64/iso/Fedora-Workstation-Live-aarch64-40-20240328.n.0.iso

= DROPPED IMAGES =
Image: i3 live aarch64
Path: Spins/aarch64/iso/Fedora-i3-Live-aarch64-40-20240327.n.0.iso

= ADDED PACKAGES =
Package: ofono-2.5-1.fc40
Summary: Open Source Telephony
RPMs:ofono ofono-devel
Size:4.18 MiB


= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  0ad-0.0.26-21.fc40
Old package:  0ad-0.0.26-20.fc40
Summary:  Cross-Platform RTS Game of Ancient Warfare
RPMs: 0ad
Size: 26.48 MiB
Size change:  -30.53 KiB
Changelog:
  * Tue Mar 19 2024 Dominik Mierzejewski  - 0.0.26-21
  - Rebuild for gloox 1.0.28


Package:  GAPDoc-1.6.7-2.fc40
Old package:  GAPDoc-1.6.6-9.fc40
Summary:  GAP documentation tool
RPMs: GAPDoc GAPDoc-doc GAPDoc-latex
Size: 1.32 MiB
Size change:  21.98 KiB
Changelog:
  * Fri Mar 15 2024 Jerry James  - 1.6.7-1
  - Version 1.6.7

  * Fri Mar 15 2024 Jerry James  - 1.6.7-2
  - Do not use the github sources, which lack tests


Package:  Lmod-8.7.37-1.fc40
Old package:  Lmod-8.7.32-3.fc40
Summary:  Environmental Modules System in Lua
RPMs: Lmod
Size: 1.03 MiB
Size change:  6.65 KiB
Changelog:
  * Mon Mar 18 2024 Orion Poplawski  - 8.7.37-1
  - Update to 8.7.37


Package:  anaconda-40.22.3-1.fc40
Old package:  anaconda-40.22.2-2.fc40
Summary:  Graphical system installer
RPMs: anaconda anaconda-core anaconda-dracut anaconda-gui 
anaconda-install-env-deps anaconda-install-img-deps anaconda-live anaconda-tui 
anaconda-widgets anaconda-widgets-devel
Size: 17.59 MiB
Size change:  -175.95 KiB
Changelog:
  * Mon Mar 25 2024 Packit  - 40.22.3-1
  - Disable preexec for vtActivate() (mkolman)
  - Lower permissions for kickstart logs in /tmp (jkonecny)
  - Copy /etc/resolv.conf to system only if there is no systemd-resolved
(rvykydal)
  - Revert "Do not copy /etc/resolv.conf to chroot before installation"
(rvykydal)
  - Do not use systemd-resolved in installer environment on RHEL (rvykydal)
  - Do not write LVM devices file during image installation (vtrefny)


Package:  azure-cli-2.58.0-1.fc40
Old package:  azure-cli-2.57.0-1.fc40
Summary:  Microsoft Azure Command-Line Tools
RPMs: azure-cli python3-azure-cli-core python3-azure-cli-telemetry 
python3-azure-cli-testsdk
Size: 12.88 MiB
Size change:  -242.27 KiB
Changelog:
  * Wed Mar 06 2024 Jeremy Cline  - 2.58.0-1
  - Bump to v2.58


Package:  btrfs-progs-6.8-1.fc40
Old package:  btrfs-progs-6.7.1-1.fc40
Summary:  Userspace programs for btrfs
RPMs: btrfs-progs btrfs-progs-devel libbtrfs libbtrfsutil 
python3-btrfsutil
Size: 6.66 MiB
Size change:  2.61 KiB
Changelog:
  * Tue Mar 26 2024 Neal Gompa  - 6.8-1
  - Update to 6.8


Package:  buildah-1.35.1-1.fc40
Old package:  buildah-1.35.0-1.fc40
Summary:  A command line tool used for creating OCI Images
RPMs: buildah buildah-tests
Size: 159.14 MiB
Size change:  -30.37 KiB
Changelog:
  * Mon Mar 18 2024 Packit  - 1.35.1-1
  - [packit] 1.35.1 upstream release


Package:  cepces-0.3.9-1.fc40
Old package:  cepces-0.3.8-3.fc40
Summary:  Certificate Enrollment through CEP/CES
RPMs: cepces cepces-certmonger cepces-selinux python3-cepces
Size: 164.34 KiB
Size change:  657 B
Changelog:
  * Tue Mar 19 2024 Andreas Schneider  - 0.3.9-1
  - Update to version 0.3.9
* https://github.com/openSUSE/cepces/releases/tag/v0.3.9


Package:  compiz-1:0.8.18-13.fc40
Old package:  compiz-1:0.8.18-12.fc40
Summary:  OpenGL window and compositing manager
RPMs: compiz compiz-devel
Size: 5.91 MiB
Size change:  2.47 KiB
Changelog:
  * Tue Mar 19 2024 Jaroslav ??karvada  - 1:0.8.18-13
  - Fixed compatibility with libxml-2.12
Resolves: rhbz#2269943


Package:  compiz-manager-0.7.0-21.fc40
Old package:  compiz-manager-0.7.0-20.fc40
Summary:  A wrapper script to start compiz with proper options
RPMs: compiz-manager
Size: 17.75 KiB
Size change:  84 B
Changelog:
  * Tue Mar 19 2024 Jaroslav ??karvada  - 0.7.0-21
  - Fixed xfwm4 command name
Related: rhbz#2269943
  - Converted license tag to SPDX


Package:  conmon-2:2.1.10-1.fc40
Old package:  conmon-2:2.1.8-4.fc40
Summary:  OCI container runtime monitor
RPMs: conmon
Size: 209.65 KiB
Size change:  1.68 KiB
Changelog:
  * Fri Jan 26 2024 Lokesh Mandvekar  - 2:2.1.10-

SPDX Statistics - Comenius edition

[Miroslav Suchý]

Hot news:

    The last phase https://fedoraproject.org/wiki/Changes/SPDX_Licenses_Phase_4 
has been approved with FESCO.

Two weeks ago we had:


* 23821spec files in Fedora

* 30463license tags in all spec files

* 11091 tags have not been converted to SPDX yet

* 4996 tags can be trivially converted using `license-fedora2spdx`

* Progress: 63,59% ░░ 100%

ELN subset:

105 out of 2411 packages are not converted yet (progress 95.64%)



Today we have:

* 23849spec files in Fedora

* 30493license tags in all spec files

* 11026 tags have not been converted to SPDX yet

* 5004 tags can be trivially converted using `license-fedora2spdx`

* Progress: 63,84% ░░ 100%

ELN subset:

100 out of 2395 packages are not converted yet (progress 95.82%)

Graph of these data with the burndown chart:

https://docs.google.com/spreadsheets/d/1QVMEzXWML-6_Mrlln02axFAaRKCQ8zE807rpCjus-8s/edit?usp=sharing

The list of packages needed to be converted is here:

https://pagure.io/copr/license-validate/blob/main/f/packages-without-spdx-final.txt

List by package maintainers is here

https://pagure.io/copr/license-validate/blob/main/f/packages-without-spdx-final-maintainers.txt

List of packages from ELN subset that needs to be converted:

https://pagure.io/copr/license-validate/blob/main/f/eln-not-migrated.txt

New version of fedora-license-data has been released. With:
    3 new licenses (plus two public domain declarations).
    14 licenses are waiting to be review by SPDX.org (and then to be added to fedora-license-data) 
https://gitlab.com/fedora/legal/fedora-license-data/-/issues/?label_name%5B%5D=SPDX%3A%3Ablocked


Legal docs and especially

https://docs.fedoraproject.org/en-US/legal/allowed-licenses/

was updated too.

License analysis of remaining packages: 
http://miroslav.suchy.cz/fedora/spdx-reports/


New projection when we will be finished is 2025-03-11 (+16 days from last 
report).  Pure linear approximation.

If your package does not have neither git-log entry nor spec-changelog entry mentioning SPDX and you know your license 
tag matches SPDX formula, you can put your package on ignore list


https://pagure.io/copr/license-validate/blob/main/f/ignore-packages.txt

Either pull-request or direct email to me is fine.


Why Comenius edition? On today's date at 1592 Jan Amos Komensky was born. He was Moravian philosopher and pedagogue who 
is considered the father of modern education. He was first to define school year, school week, school leave. What are 
the requirements for a classroom. He set up school organization - from kindergarten to academia (university). Most of 
his principles are still valid. And some principles are still not yet achieved by some schools: Put everything into 
practice. Teaching should be fun. The pupil should be the teacher at the same time...


https://en.wikipedia.org/wiki/John_Amos_Comenius

https://en.wikipedia.org/wiki/Great_Didactic

https://en.wikipedia.org/wiki/Orbis_Pictus

https://en.wikipedia.org/wiki/Janua_linguarum_reserata


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

[Test-Announce] Fedora 40 Branched 20240328.n.0 nightly compose nominated for testing

[rawhide]

Announcing the creation of a new nightly release validation test event
for Fedora 40 Branched 20240328.n.0. Please help run some tests for this
nightly compose if you have time. For more information on nightly
release validation testing, see:
https://fedoraproject.org/wiki/QA:Release_validation_test_plan

Notable package version changes:
anaconda - 1.10: anaconda-40.22.2-2.fc40.src, 20240328.n.0: 
anaconda-40.22.3-1.fc40.src

Test coverage information for the current release can be seen at:
https://openqa.fedoraproject.org/testcase_stats/40

You can see all results, find testing instructions and image download
locations, and enter results on the Summary page:

https://fedoraproject.org/wiki/Test_Results:Fedora_40_Branched_20240328.n.0_Summary

The individual test result pages are:

https://fedoraproject.org/wiki/Test_Results:Fedora_40_Branched_20240328.n.0_Installation
https://fedoraproject.org/wiki/Test_Results:Fedora_40_Branched_20240328.n.0_Base
https://fedoraproject.org/wiki/Test_Results:Fedora_40_Branched_20240328.n.0_Server
https://fedoraproject.org/wiki/Test_Results:Fedora_40_Branched_20240328.n.0_Cloud
https://fedoraproject.org/wiki/Test_Results:Fedora_40_Branched_20240328.n.0_Desktop
https://fedoraproject.org/wiki/Test_Results:Fedora_40_Branched_20240328.n.0_Security_Lab

Thank you for testing!
-- 
Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer
--
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-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/test-annou...@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: [SPDX] Mass license change: Intro and change of "Bitstream Vera" to "Bitstream-Vera"

[Miroslav Suchý]

Dne 28. 03. 24 v 10:59 dop. Zbigniew Jędrzejewski-Szmek napsal(a):

I also think the conversion should only be done if the full License string can 
be converted. Partial conversion is confusing, and there is not much value, 
since trivial conversion is, well, trivial, and whoever will eventually need to 
take a look at the nontrivial parts can easily handle it then.

I'd add a "me too": I think if we have mixed spdx and callaways strings,
this will make later automatic processing even harder.
I that is possible, I think you should just do the full conversion for
those packages, even if that requires some manual introspection.


Ack. There is clear winner - not to mix the spdx and callaway.

I will do the change only for:

./bitstream-vera-fonts.spec:License: Bitstream Vera
./bpg-fonts.spec:License:   Bitstream Vera
./bpg-fonts.spec:License:   Bitstream Vera
./bpg-fonts.spec:License:   Bitstream Vera
./bpg-fonts.spec:License:   Bitstream Vera
./bpg-fonts.spec:License:   Bitstream Vera
./bpg-fonts.spec:License:   Bitstream Vera
./bpg-fonts.spec:License:   Bitstream Vera
./bpg-fonts.spec:License:   Bitstream Vera
./R-fontBitstreamVera.spec:License:  Bitstream Vera

--
Miroslav Suchy, RHCA
Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys
--
___
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: Feedback wanted: Kvantum 1.1.0 spec changes

[Neal Gompa]

On Thu, Mar 28, 2024 at 6:11 AM Arthur Bols  wrote:
>
> Hi all,
>
> Kvantum 1.1.0 has been released and changed the default compilation to
> Qt6. Due to this change, I would like to change the packaging such that
> the base package is Qt6 and a subpackage provides the Qt5 plugin. This
> causes major changes to the spec and resulting packages, so I would like
> some feedback on that. I also removed the dependency on the base package
> for the data subpackage. The circular dependency was a bit strange, and
> separating it allows installing kvantum-qt5 and kvantum-data separately.
>
> Attached is the patch outlining these changes. Your feedback would be
> greatly appreciated.
>

This seems reasonable to me. Do we have any packaged themes that need
to be adjusted alongside it?



-- 
真実はいつも一つ！/ 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

Feedback wanted: Kvantum 1.1.0 spec changes

[Arthur Bols]

Hi all,

Kvantum 1.1.0 has been released and changed the default compilation to 
Qt6. Due to this change, I would like to change the packaging such that 
the base package is Qt6 and a subpackage provides the Qt5 plugin. This 
causes major changes to the spec and resulting packages, so I would like 
some feedback on that. I also removed the dependency on the base package 
for the data subpackage. The circular dependency was a bit strange, and 
separating it allows installing kvantum-qt5 and kvantum-data separately.


Attached is the patch outlining these changes. Your feedback would be 
greatly appreciated.


Kind regards,
Arthur Bols
fas/irc: principisFrom 2d7a2c39be4baee14bc830c9e7fbf0d7480095bf Mon Sep 17 00:00:00 2001
From: Arthur Bols 
Date: Mon, 18 Mar 2024 11:49:52 +0100
Subject: [PATCH] Update to 1.1.0 (fedora#2269918)

---
 .gitignore   |  1 +
 kvantum.spec | 84 ++--
 sources  |  2 +-
 3 files changed, 51 insertions(+), 36 deletions(-)

diff --git a/.gitignore b/.gitignore
index 65200b2..7422abf 100644
--- a/.gitignore
+++ b/.gitignore
@@ -23,3 +23,4 @@
 /kvantum-1.0.7.tar.gz
 /kvantum-1.0.9.tar.gz
 /kvantum-1.0.10.tar.gz
+/kvantum-1.1.0.tar.gz
diff --git a/kvantum.spec b/kvantum.spec
index b403bc3..d2d47c8 100644
--- a/kvantum.spec
+++ b/kvantum.spec
@@ -1,8 +1,8 @@
 %global _vpath_srcdir Kvantum
-%bcond_without  qt6
+%bcond_without  qt5
 
 Name:   kvantum
-Version:1.0.10
+Version:1.1.0
 Release:%autorelease
 Summary:SVG-based theme engine for Qt, KDE and LXQt
 
@@ -15,26 +15,35 @@ BuildRequires:  cmake
 BuildRequires:  make
 BuildRequires:  pkgconfig(x11)
 BuildRequires:  pkgconfig(xext)
+BuildRequires:  pkgconfig(Qt6Core)
+BuildRequires:  pkgconfig(Qt6Gui)
+BuildRequires:  pkgconfig(Qt6Linguist)
+BuildRequires:  pkgconfig(Qt6Svg)
+BuildRequires:  pkgconfig(Qt6Widgets)
+%if 0%{?fedora} >= 40
+BuildRequires:  cmake(KF6WindowSystem)
+%endif
+%if %{with qt5}
 BuildRequires:  pkgconfig(Qt5)
 BuildRequires:  pkgconfig(Qt5Designer)
 BuildRequires:  pkgconfig(Qt5Svg)
 BuildRequires:  pkgconfig(Qt5X11Extras)
 BuildRequires:  cmake(KF5WindowSystem)
-%if %{with qt6}
-BuildRequires:  pkgconfig(Qt6Core)
-BuildRequires:  pkgconfig(Qt6Gui)
-BuildRequires:  pkgconfig(Qt6Svg)
-BuildRequires:  pkgconfig(Qt6Widgets)
 %endif
 BuildRequires:  desktop-file-utils
 BuildRequires:  kde-filesystem
-Requires:   %{name}-data
+
 Requires:   hicolor-icon-theme
+Requires:   %{name}-data = %{version}-%{release}
 
-%if %{with qt6}
-Recommends: (%{name}-qt6 if qt6-qtbase-gui)
+%if %{with qt5}
+Recommends: (%{name}-qt5 if qt5-qtbase-gui)
 %endif
 
+# Qt6 is default since 1.1.0
+Provides:  kvantum-qt6 = %{version}-%{release}
+Obsoletes: kvantum-qt6 < 1.1.0
+
 %description
 Kvantum is an SVG-based theme engine for Qt, tuned to KDE and LXQt, with an
 emphasis on elegance, usability and practicality.
@@ -50,22 +59,21 @@ Qt widgets.
 Kvantum also comes with many other themes that are installed as root and can
 be selected and activated by using Kvantum Manager.
 
-%if %{with qt6}
-%package qt6
-Summary:   SVG-based theme engine for Qt6
-Requires:  %{name}-data
+%if %{with qt5}
+%package qt5
+Summary:   SVG-based theme engine for Qt5
+Requires:  %{name}-data = %{version}-%{release}
 
-%description qt6
+%description qt5
 Kvantum is an SVG-based theme engine for Qt, tuned to KDE and LXQt, with an
 emphasis on elegance, usability and practicality.
 
-This package contains the Qt6 integration plugin.
+This package contains the Qt5 integration plugin.
 %endif
 
 %package data
 Summary:SVG-based theme engine for Qt5, KDE and LXQt
 BuildArch:  noarch
-Requires:   kvantum
 
 %description data
 Kvantum is an SVG-based theme engine for Qt, tuned to KDE and LXQt, with an
@@ -77,22 +85,28 @@ This package contains the data needed Kvantum.
 %autosetup -n Kvantum-%{version}
 
 %build
-%if %{with qt6}
-%global _vpath_builddir %{_target_platform}-qt6
-%cmake -DENABLE_QT5:BOOL=OFF
-%cmake_build
-%endif
+%if %{with qt5}
 %global _vpath_builddir %{_target_platform}-qt5
 %cmake -DENABLE_QT5:BOOL=ON
 %cmake_build
+%endif
 
-%install
-%if %{with qt6}
 %global _vpath_builddir %{_target_platform}-qt6
-%cmake_install
+%cmake \
+-DENABLE_QT5:BOOL=OFF \
+%if 0%{?fedora} < 40
+-DWITHOUT_KF=ON
 %endif
+%cmake_build
+
+%install
+%if %{with qt5}
 %global _vpath_builddir %{_target_platform}-qt5
 %cmake_install
+%endif
+
+%global _vpath_builddir %{_target_platform}-qt6
+%cmake_install
 
 # desktop-file-validate doesn't recognize LXQt
 sed -i "s|LXQt|X-LXQt|" %{buildroot}%{_datadir}/applications/kvantummanager.desktop
@@ -105,23 +119,23 @@ desktop-file-validate %{buildroot}%{_datadir}/applications/kvantummanager.deskto
 %doc Kvantum/ChangeLog Kvantum/NEWS Kvantum/README.md
 %{_bindir}/kvantummanager
 %{_bindir}/kvantumpreview
-%{_qt5_plugindir}/styles/libkvantum.so
-
-%if %{with qt6}
-%files qt6
-%license Kvantum/COPYING
 

Re: [SPDX] Mass license change: Intro and change of "Bitstream Vera" to "Bitstream-Vera"

[Zbigniew Jędrzejewski-Szmek]

On Wed, Mar 27, 2024 at 08:32:41PM +0200, Otto Liljalaakso wrote:
> 
> 27. maaliskuuta 2024 12.59.11 GMT+02:00 Petr Pisar  
> kirjoitti:
> >V Tue, Mar 26, 2024 at 02:52:50PM +0100, Miroslav Suchý napsal(a):
> >> I have no strong opinion how to process with the case of  "MIT and BSD and
> >> Bitstream Vera and OFL". I think that converting it to " MIT and BSD and
> >> Bitstream-Vera and OFL" is probably best option. I.e. the License tag will
> >> become mixture of Callaway and SPDX. It will not make it valid SPDX formula
> >> so it will still pop up as package to be fixed, but at least some work will
> >> be done.
> >
> >In other words, it will be a regression. Invalid by either system:
> >
> >$ license-validate 'MIT AND BSD AND Bitstream-Vera and OFL'
> >Not a valid license string
> >Run with -v option to see more information.
> >$ license-validate --old 'MIT AND BSD AND Bitstream-Vera and OFL'
> >Not a valid license string
> >Run with -v option to see more information.
> >
> >I wouldn't do it.
> >
> >If you want to hint the packager, then open a pull request with the partial
> >conversion.
> >
> >-- Petr
> 
> I also think the conversion should only be done if the full License string 
> can be converted. Partial conversion is confusing, and there is not much 
> value, since trivial conversion is, well, trivial, and whoever will 
> eventually need to take a look at the nontrivial parts can easily handle it 
> then.

I'd add a "me too": I think if we have mixed spdx and callaways strings,
this will make later automatic processing even harder.
I that is possible, I think you should just do the full conversion for
those packages, even if that requires some manual introspection.

Zbyszek
--
___
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: Non-responsive maintainer check for dagostinelli

[Arthur Bols]

On 27/03/2024 14:28, Andreas Schneider wrote:

Hi,

I'm trying to reach the maintainer of fswatch [1]. fswatch will be a
dependency of neovim 0.10 and I would like to get it updated to be prepared
for the release. It looks like the maintainer is unresponsive. I've open the
bugs [2] and [3]. [3] is the bug for this non-responsive maintainer check for
dagostinelli.

I can also (co-)maintain the package as it is a dependency of neovim soon.


Best regards


Andreas


[1] https://src.fedoraproject.org/rpms/fswatch
[2] https://bugzilla.redhat.com/show_bug.cgi?id=2270266
[3] https://bugzilla.redhat.com/show_bug.cgi?id=2271832

--
___
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 haven't seen him, adding CC to their email.

--
Arthur Bols
fas/irc: principis
--
___
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: %pyproject_buildrequires -r/-x: Attempt to read runtime dependencies from pyproject.toml?

[Miro Hrončok]

On 27. 03. 24 23:15, Maxwell G wrote:

One way to mitigate would be to make the proposed behavior opt-in only,
with the possibility to either build wheel with -w option (already
existing) or e.g. -p (now-proposed: reading from pyproject.toml) in case
backend doesn't have prepare_metadata_for_build_wheel.

Yeah, I think -p (for *p*yproject) is good flag name choice.


Or even for [*p*roject] table. It is double good.


I guess I will throw something out there, but I am not convinced it is a
great idea: what about making the `-p` flag fail if
`prepare_metadata_for_build_wheel` is available? In my opinion, this
should only be a last resort for backends that do not implement the hook.


I am not particularly keen on this.

This means that once the backend starts supporting it, all the spec files using 
-p need to drop it. And if the backend only supports it in rawhide, the spec 
files need to diverge and/or %if-guard the flag.


If the backend followed PEP 621 before adding the hook and now it added the 
hook, it is unlikely the PEP 621 support was dropped.


OTHO if the backed was changed (e.g. meson -> poetry), this *could* happen. So 
I am not entirely opposed for this guard.


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

Non-responsive maintainer check for dagostinelli

[Andreas Schneider]

Hi,

I'm trying to reach the maintainer of fswatch [1]. fswatch will be a 
dependency of neovim 0.10 and I would like to get it updated to be prepared 
for the release. It looks like the maintainer is unresponsive. I've open the 
bugs [2] and [3]. [3] is the bug for this non-responsive maintainer check for 
dagostinelli.

I can also (co-)maintain the package as it is a dependency of neovim soon.


Best regards


Andreas


[1] https://src.fedoraproject.org/rpms/fswatch
[2] https://bugzilla.redhat.com/show_bug.cgi?id=2270266
[3] https://bugzilla.redhat.com/show_bug.cgi?id=2271832

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