Re: Is it okay to use /usr/bin/python again?

2022-01-04 Thread Vitaly Zaitsev via devel

On 05/01/2022 08:46, Nico Kadel-Garcia wrote:

Can you point to where that is forbidden?


https://docs.fedoraproject.org/en-US/packaging-guidelines/#_shebang_lines


env, /bin/env and /usr/bin/env MUST NOT be used. The interpreter used to run 
packaged applications cannot depend upon what the user has in their personal 
$PATH.


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


[Bug 2036310] perl-Math-BigInt-1.999829 is available

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036310

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
 CC|jples...@redhat.com,|
   |mspa...@redhat.com, |
   |ppi...@redhat.com   |
   Doc Type|--- |If docs needed, set a value




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036310
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Is it okay to use /usr/bin/python again?

2022-01-04 Thread Nico Kadel-Garcia
On Wed, Jan 5, 2022 at 2:34 AM Vitaly Zaitsev via devel
 wrote:
>
> On 04/01/2022 19:36, Nico Kadel-Garcia wrote:
> > #!/usr/bin/env python3
>
> Forbidden by Python guidelines too.

Can you point to where that is forbidden? Because it remains quite
popular for various working environments with multiple python
releases, such as RHEL 7 supported through EPEL.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Is it okay to use /usr/bin/python again?

2022-01-04 Thread Vitaly Zaitsev via devel

On 04/01/2022 19:36, Nico Kadel-Garcia wrote:

#!/usr/bin/env python3


Forbidden by Python guidelines too.

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


[Bug 2036122] Please branch and build perl-HTML-TreeBuilder-XPath for EPEL-8

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036122



--- Comment #2 from Paul Howarth  ---
perl-XML-XPathEngine-0.14-23.el9 has been built now.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036122
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2036122] Please branch and build perl-HTML-TreeBuilder-XPath for EPEL-8

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036122



--- Comment #1 from Paul Howarth  ---
perl-XML-XPathEngine-0.14-23.el8 has been built now.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036122
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: File collision advice

2022-01-04 Thread Elliott Sales de Andrade
On Tue, 4 Jan 2022 at 23:04, Jerry James  wrote:
>
> I would like some advice on this bug:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=2036438
>
> There are a number of packages with names of the form
> python-sphinxcontrib-foo, which install their files into
> %{python3_sitelib}/sphinxcontrib/foo/.  The issue is that at least two
> of these, python-sphinxcontrib-asyncio and
> python-sphinxcontrib-zopeext, install a file named
> %{python3_sitelib}/sphinxcontrib/__init__.py, and the files are not
> identical.
>

I think these packages are wrong upstream. The `sphinxcontrib`
directory is provided by python3-sphinx, and it specifically doesn't
have `__init__.py` there. Those extensions should not be adding one,
so as to keep the implicit namespace package nature of that directory:
https://packaging.python.org/en/latest/guides/packaging-namespace-packages/#native-namespace-packages

By the contents of the files, it appears they are trying to force it
to be a pkg_resources-style namespace package:
https://packaging.python.org/en/latest/guides/packaging-namespace-packages/#pkg-resources-style-namespace-packages

But since Sphinx didn't do that in the first place, there's no
guarantee that other packages will contain `__init__.py` (and indeed
most do not).

> Any thoughts on how this should be dealt with are welcome.  I
> suggested in the bug that we could introduce a package named simply
> python-sphinxcontrib that owns both the sphinxcontrib directory and
> the __init__.py file.  The other python-sphinxcontrib-* packages would
> depend on it, and would not install any such __init__.py file.  There
> is no such upstream package; this would be a Fedora construct simply
> to deal with the file collision.  Perhaps we could even make that a
> subpackage of python-sphinx.
>
> Other ideas are welcome, especially if they mean less work for me. :-)
> --
> Jerry James
> http://www.jamezone.org/

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


XEmacs retirement

2022-01-04 Thread Jerry James
I intend to retire the following packages soon:

neXtaw
xemacs
xemacs-packages-base
xemacs-packages-extra

I believe all of the dependencies on these packages have been removed
in Rawhide.  Some of the affected packages have made the necessary
change in git, but have not been rebuilt yet.  The dependencies should
all disappear in the mass rebuild.

To avoid Rawhide breakage, I will wait until just before the mass
rebuild starts to retire these packages.  If anybody wants to keep
these packages, let me know soon and I will give them to you.  Be
aware, though, that upstream is dead for all of them.

Regards,
-- 
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Review swaps

2022-01-04 Thread Jerry James
On Sat, Jan 1, 2022 at 7:46 PM Jerry James  wrote:
> Happy New Year!
>
> I am in need of some package reviews to update parts of the OCaml stack:
>
> - ocaml-bos: https://bugzilla.redhat.com/show_bug.cgi?id=2031160
> - ocaml-odoc-parser: https://bugzilla.redhat.com/show_bug.cgi?id=2036395
> - ocaml-mdx: https://bugzilla.redhat.com/show_bug.cgi?id=2036396
> - ocaml-stdcompat: https://bugzilla.redhat.com/show_bug.cgi?id=2036398
> - ocaml-pyml: https://bugzilla.redhat.com/show_bug.cgi?id=2036399
>
> Let me know what I can review for you.  Regards,

I am still in need of these reviews.  If you don't need a package
reviewed, I am willing to swap for something else.  Let me know what I
can do 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 on the list, report it: 
https://pagure.io/fedora-infrastructure


File collision advice

2022-01-04 Thread Jerry James
I would like some advice on this bug:

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

There are a number of packages with names of the form
python-sphinxcontrib-foo, which install their files into
%{python3_sitelib}/sphinxcontrib/foo/.  The issue is that at least two
of these, python-sphinxcontrib-asyncio and
python-sphinxcontrib-zopeext, install a file named
%{python3_sitelib}/sphinxcontrib/__init__.py, and the files are not
identical.

Any thoughts on how this should be dealt with are welcome.  I
suggested in the bug that we could introduce a package named simply
python-sphinxcontrib that owns both the sphinxcontrib directory and
the __init__.py file.  The other python-sphinxcontrib-* packages would
depend on it, and would not install any such __init__.py file.  There
is no such upstream package; this would be a Fedora construct simply
to deal with the file collision.  Perhaps we could even make that a
subpackage of python-sphinx.

Other ideas are welcome, especially if they mean less work for me. :-)
-- 
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2036661] Please branch and build perl-Scope-Upper for EPEL-9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036661

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
FEDORA-EPEL-2022-117c0c382b has been pushed to the Fedora EPEL 9 testing
repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-117c0c382b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036661
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2036506] Please branch and build perl-XML-Dumper for EPEL-9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036506

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
FEDORA-EPEL-2022-f2b758df21 has been pushed to the Fedora EPEL 9 testing
repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-f2b758df21

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036506
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2036491] Please branch and build perl-Test-Refcount for EPEL-9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036491

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #4 from Fedora Update System  ---
FEDORA-EPEL-2022-4b3e70787e has been pushed to the Fedora EPEL 9 testing
repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-4b3e70787e

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036491
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2036494] Please branch and build perl-CSS-Tiny for EPEL-9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036494

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
FEDORA-EPEL-2022-4b3e70787e has been pushed to the Fedora EPEL 9 testing
repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-4b3e70787e

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036494
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2036498] Please branch and build perl-Parallel-Iterator for EPEL-9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036498

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
FEDORA-EPEL-2022-0cf8bddb9b has been pushed to the Fedora EPEL 9 testing
repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-0cf8bddb9b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036498
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2036225] Please branch and build perl-Test-Portability-Files for EPEL-9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036225

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
FEDORA-EPEL-2022-898852af3c has been pushed to the Fedora EPEL 9 testing
repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-898852af3c

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036225
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2036508] Please branch and build perl-Data-Taxi for EPEL-9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036508

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
FEDORA-EPEL-2022-4b3e70787e has been pushed to the Fedora EPEL 9 testing
repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-4b3e70787e

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036508
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2036922] Please branch and build perl-Devel-Refcount for EPEL 9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036922

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #4 from Fedora Update System  ---
FEDORA-EPEL-2022-9821de3579 has been pushed to the Fedora EPEL 9 testing
repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-9821de3579

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036922
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2036900] Please branch and build perl-Net-LibIDN2 for EPEL 9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036900

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
FEDORA-EPEL-2022-8ef56d94b2 has been pushed to the Fedora EPEL 9 testing
repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-8ef56d94b2

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036900
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2036509] Please branch and build perl-Data-Denter for EPEL-9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036509

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
FEDORA-EPEL-2022-4b3e70787e has been pushed to the Fedora EPEL 9 testing
repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-4b3e70787e

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036509
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2036500] Please branch and build perl-B-Debug for EPEL-9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036500

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
FEDORA-EPEL-2022-df8248f4fc has been pushed to the Fedora EPEL 9 testing
repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-df8248f4fc

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036500
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2036504] Please branch and build perl-Exporter-Tidy for EPEL-9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036504

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
FEDORA-EPEL-2022-96e018404b has been pushed to the Fedora EPEL 9 testing
repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-96e018404b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036504
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2036665] Please branch and build perl-Digest-SHA3 for EPEL-9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036665

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
FEDORA-EPEL-2022-152e901adb has been pushed to the Fedora EPEL 9 testing
repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-152e901adb

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036665
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2036497] Please branch and build perl-Dir-Self for EPEL-9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036497

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
FEDORA-EPEL-2022-8215b3ffdc has been pushed to the Fedora EPEL 9 testing
repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-8215b3ffdc

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036497
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2034172] EPEL9 branch of perl-File-Find-Rule-Perl

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2034172

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #5 from Fedora Update System  ---
FEDORA-EPEL-2022-0afad54106 has been pushed to the Fedora EPEL 9 testing
repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-0afad54106

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2034172
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2031799] perl-FCGI-ProcManager for EPEL 9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2031799

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
FEDORA-EPEL-2022-4b3e70787e has been pushed to the Fedora EPEL 9 testing
repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-4b3e70787e

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2031799
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2036663] Please branch and build perl-IO-CaptureOutput for EPEL-9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036663

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #4 from Fedora Update System  ---
FEDORA-EPEL-2022-5f555e8624 has been pushed to the Fedora EPEL 9 testing
repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-5f555e8624

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036663
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2036507] Please branch and build perl-PHP-Serialization for EPEL-9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036507

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
FEDORA-EPEL-2022-ad290a5a20 has been pushed to the Fedora EPEL 9 testing
repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-ad290a5a20

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036507
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2036118] Please branch and build perl-XML-XPathEngine for EPEL-8

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036118

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
FEDORA-EPEL-2022-5cdc4a7136 has been pushed to the Fedora EPEL 8 testing
repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-5cdc4a7136

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036118
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: New tool - license-validate

2022-01-04 Thread Miroslav Suchý

Dne 04. 01. 22 v 21:33 David Cantrell napsal(a):


I feel like I'm missing something, but rpminspect has been doing what
license-validate does for years now.  It's ready for SPDX expressions.
Results show up for Fedora builds in Zuul.  Or you can run it locally. 


Here is my motivation:

We are automating packing - hundred thousands libraries to be automatically packaged. But some of them have restrictive 
license. For that we need **simple** tool.


rpminspect is big beast for that. I learned that I can run

rpminspect-fedora-Fjson-Tlicense foo.src.rpm

But I need something which can evaluate just the string.

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


Self Introduction: Malcolm Inglis (mcinglis)

2022-01-04 Thread Inglis, Malcolm via devel
Hi Fedora developers,

I’m looking to join your ranks  I’ve made 
a 
few 
PRs already, and had mistakenly skipped this important step of introducing 
myself.

I’m a senior software engineer on the Amazon Linux team at AWS. I’m working on 
the infrastructure and tooling we use for AL packaging, and on maintenance of 
our user-space packages. I joined the AL team in Q3 2021 with much excitement 
for our direction regarding 
AL22 and Fedora collaboration, 
and am continuing to support that direction internally. I’ve been at Amazon 
since 2016, having worked in internal developer tools organization for the 
majority of that time, specifically on the massive internal build system and on 
enabling AWS deployments for Amazon’s developers. Prior to Amazon, I’ve worked 
on software for solar power system logging and control, and on CRUD web 
development projects. I studied software engineering and mathematics at the 
University of Queensland for several years.

I’ve ran Fedora (Silverblue) as my daily driver on my laptop since at least 
2011, though I experiment and dual boot various other distros on other machines 
(big fan of Guix, Alpine and OpenBSD). Fedora’s always been my trusty 
workhorse, though, and I’m ashamed that it’s taken me this long to start 
contributing to the project that I’ve gotten so much value from. Better late 
than never!

I live in Newcastle, WA, USA, and have lived in the Seattle area for the past 
six years. I’m originally from Brisbane, Australia. I have a 
website that’s been gathering dust, but am hoping to get 
around to that soon. Outside of software which I read and nerd about perhaps 
too much, I love going places and doing things with my family. I enjoy reading 
science fiction and history. I am interested in futurism, space exploration and 
human-scale urban design, and appreciate good coffee and dry wine.

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


Re: New tool - license-validate

2022-01-04 Thread Miroslav Suchý

Dne 04. 01. 22 v 21:03 David Cantrell napsal(a):

One of the difficult things with the Fedora abbreviations is that
tokens can have spaces in them.  For example, the Apache 2.0 license
in Fedora is called "ASL 2.0".  This makes it really hard to work with
in software.

Likewise, we have historically allowed full expressions through that
contain otherwise forbidden licenses.  For example, many Perl module
packages use the License tag "GPL+ or Artistic" so in a way that
entire expression is treated as a token.

This information is currently captured in this JSON file (not the
original author, but I make use of the file):

https://github.com/rpminspect/rpminspect-data-fedora/blob/master/licenses/fedora.json

rpminspect's license check uses this data to validate the License tag
in RPM headers based on the rules as they exist in the packaging
guidelines plus the assorted expressions we have historically allowed
through that would not otherwise validate.


*nod*

The string

 'GPL+ or Artistic or MIT'

evaluates license-validate as correct, while rpminspect results that as bad 
license.

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


[Bug 2022551] perl-HTTP-Message-6.35 is available

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2022551



--- Comment #5 from Fedora Update System  ---
FEDORA-2022-5bb8ca4ef4 has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
--advisory=FEDORA-2022-5bb8ca4ef4`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2022-5bb8ca4ef4

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2022551
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2022551] perl-HTTP-Message-6.35 is available

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2022551

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #4 from Fedora Update System  ---
FEDORA-2022-6b7c00e649 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
--advisory=FEDORA-2022-6b7c00e649`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2022-6b7c00e649

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2022551
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: F36 Change: %set_build_flags for %build and %check (System-Wide Change proposal)

2022-01-04 Thread Tom Stellard

On 12/20/21 12:39, Florian Weimer wrote:

* Ben Cotton:


This change will be implemented by updating the %__spec_build_pre and
%__speck_check_pre macros in redhat-rpm-config to include
%set_build_flags.  This will set these environment variables
automatically before the %build and %check sections.  See the proposed
[https://src.fedoraproject.org/fork/tstellar/rpms/redhat-rpm-config/c/a39741bbebd645c46e5d675920b4bffe390c95bb?branch=set-build-flags-build-check
implementation] for more details.


Would you please add a clear opt-out mechanism, and document the
behavior and the mechanism in buildflags.md?



Ok, I made this change: 
https://src.fedoraproject.org/rpms/redhat-rpm-config/pull-request/166

-Tom


I can't tell right now how much is going to break because of this, but I
think it's worth a try.

Thanks,
Florian


___
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


[rpms/perl-Browser-Open] PR #1: Import EPEL9 package from rawhide

2022-01-04 Thread Michal Josef Špaček

mspacek merged a pull-request against the project: `perl-Browser-Open` that you 
are following.

Merged pull-request:

``
Import EPEL9 package from rawhide
``

https://src.fedoraproject.org/rpms/perl-Browser-Open/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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[rpms/perl-Browser-Open] PR #1: Import EPEL9 package from rawhide

2022-01-04 Thread Michal Josef Špaček

mspacek opened a new pull-request against the project: `perl-Browser-Open` that 
you are following:
``
Import EPEL9 package from rawhide
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Browser-Open/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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2036118] Please branch and build perl-XML-XPathEngine for EPEL-8

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036118

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #2 from Fedora Update System  ---
FEDORA-EPEL-2022-5cdc4a7136 has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-5cdc4a7136


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036118
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: New tool - license-validate

2022-01-04 Thread Robbie Harwood
Neal Gompa  writes:

> On Tue, Jan 4, 2022 at 3:10 PM Robbie Harwood  wrote:
>>
>> Neal Gompa  writes:
>>
>> > On Tue, Jan 4, 2022 at 2:25 PM Robbie Harwood  wrote:
>> >>
>> >> Neal Gompa  writes:
>> >>
>> >> > SPDX expression logic is identical to Fedora's, so that will not
>> >> > change.
>> >>
>> >> I don't believe that's correct.
>> >>
>> >> For instance, for the LGPL, SPDX uses "LGPL-2.0-only" and
>> >> "LGPL-2.0-or-later", while Fedora currently uses "LGPLv2" and "LGPLv2+".
>> >>
>> >> (From https://spdx.org/licenses/ and
>> >> https://fedoraproject.org/wiki/Licensing:Main )
>> >>
>> >
>> > Those are the identifiers, not the *logic*. SPDX and Fedora both use
>> > the same boolean logic terms ("and"/"or"/"with") and support
>> > parenthetical expressions. Fedora mandates lowercase, SPDX doesn't
>> > care, but examples historically are uppercase. Fedora will retain its
>> > expression logic system, complete with lowercase terms (since that
>> > makes the expressions more readable).
>>
>> Fine, but that's misleading in this context.  Right now the tool flags
>> (and therefore bugs have been filed for) the identifiers as well.
>
> Yes, and those should still happen.

I don't see why that would be the case, given that as Matthew Miller
mentioned upthread the plan is to move to SPDX identifiers in the
distro.  That seems like useless churn and waste of maintainer time.

Be well,
--Robbie


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


Re: New tool - license-validate

2022-01-04 Thread David Cantrell

On Tue, Jan 04, 2022 at 03:21:20PM -0500, Neal Gompa wrote:

On Tue, Jan 4, 2022 at 3:10 PM Robbie Harwood  wrote:


Neal Gompa  writes:

> On Tue, Jan 4, 2022 at 2:25 PM Robbie Harwood  wrote:
>>
>> Neal Gompa  writes:
>>
>> > SPDX expression logic is identical to Fedora's, so that will not
>> > change.
>>
>> I don't believe that's correct.
>>
>> For instance, for the LGPL, SPDX uses "LGPL-2.0-only" and
>> "LGPL-2.0-or-later", while Fedora currently uses "LGPLv2" and "LGPLv2+".
>>
>> (From https://spdx.org/licenses/ and
>> https://fedoraproject.org/wiki/Licensing:Main )
>>
>
> Those are the identifiers, not the *logic*. SPDX and Fedora both use
> the same boolean logic terms ("and"/"or"/"with") and support
> parenthetical expressions. Fedora mandates lowercase, SPDX doesn't
> care, but examples historically are uppercase. Fedora will retain its
> expression logic system, complete with lowercase terms (since that
> makes the expressions more readable).

Fine, but that's misleading in this context.  Right now the tool flags
(and therefore bugs have been filed for) the identifiers as well.


Yes, and those should still happen. I'm saying that what
license-validate *does* and the code written for it will be useful
with SPDX identifiers or Fedora ones, because the meat of the tool
(the logical parsing and handling) would be the same.


I feel like I'm missing something, but rpminspect has been doing what
license-validate does for years now.  It's ready for SPDX expressions.
Results show up for Fedora builds in Zuul.  Or you can run it locally.

Thanks,

--
David Cantrell 
Red Hat, Inc. | Boston, MA | EST5EDT
___
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


[Bug 2036118] Please branch and build perl-XML-XPathEngine for EPEL-8

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036118

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
   Doc Type|--- |If docs needed, set a value



--- Comment #1 from Jitka Plesnikova  ---
https://pagure.io/releng/fedora-scm-requests/issue/40429


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036118
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: buildroot size growth

2022-01-04 Thread Adam Williamson
On Tue, 2022-01-04 at 14:57 +0100, Vít Ondruch wrote:
> It seems that Rawhide buildroot has grown some dependencies between 10th 
> and 23rd of December.
> 
> The last official build of Ruby I did [1] installs  152 packages:
> 
> ~~~
> 
> DEBUG util.py:446:  Install  152 Packages
> DEBUG util.py:446:  Total download size: 59 M
> DEBUG util.py:446:  Installed size: 231 M
> 
> ~~~
> 
> 
> While scratch build [2] done by Koschei on Dec 23 already installs 169 
> packages:
> 
> 
> ~~~
> 
> DEBUG util.py:446:  Install  169 Packages
> DEBUG util.py:446:  Total download size: 65 M
> DEBUG util.py:446:  Installed size: 250 M
> 
> ~~~
> 
> 
> One of the packages which caught my attention and previously was not 
> installed is systemd (there always were just systemd-libs). So is 
> systemd to blame or is it something else?

I think the difference is that authselect is now pulled in. authselect
pulls in authselect-libs, which pulls in systemd, which I think pulls
in the other things.

The reason authselect gets pulled in is that pam now requires it:

https://src.fedoraproject.org/rpms/pam/c/ff21ecd19213fce0570d448831d21f66db6abc2c?branch=rawhide

that change landed in Rawhide in pam-1.5.2-8.fc36, which was built late
on December 9th, and so likely appeared in the December 10th compose.
-- 
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net

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


Re: New tool - license-validate

2022-01-04 Thread Neal Gompa
On Tue, Jan 4, 2022 at 3:10 PM Robbie Harwood  wrote:
>
> Neal Gompa  writes:
>
> > On Tue, Jan 4, 2022 at 2:25 PM Robbie Harwood  wrote:
> >>
> >> Neal Gompa  writes:
> >>
> >> > SPDX expression logic is identical to Fedora's, so that will not
> >> > change.
> >>
> >> I don't believe that's correct.
> >>
> >> For instance, for the LGPL, SPDX uses "LGPL-2.0-only" and
> >> "LGPL-2.0-or-later", while Fedora currently uses "LGPLv2" and "LGPLv2+".
> >>
> >> (From https://spdx.org/licenses/ and
> >> https://fedoraproject.org/wiki/Licensing:Main )
> >>
> >
> > Those are the identifiers, not the *logic*. SPDX and Fedora both use
> > the same boolean logic terms ("and"/"or"/"with") and support
> > parenthetical expressions. Fedora mandates lowercase, SPDX doesn't
> > care, but examples historically are uppercase. Fedora will retain its
> > expression logic system, complete with lowercase terms (since that
> > makes the expressions more readable).
>
> Fine, but that's misleading in this context.  Right now the tool flags
> (and therefore bugs have been filed for) the identifiers as well.

Yes, and those should still happen. I'm saying that what
license-validate *does* and the code written for it will be useful
with SPDX identifiers or Fedora ones, because the meat of the tool
(the logical parsing and handling) would be the same.



-- 
真実はいつも一つ!/ 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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2036665] Please branch and build perl-Digest-SHA3 for EPEL-9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036665

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #2 from Fedora Update System  ---
FEDORA-EPEL-2022-152e901adb has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-152e901adb


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036665
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2036661] Please branch and build perl-Scope-Upper for EPEL-9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036661

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #2 from Fedora Update System  ---
FEDORA-EPEL-2022-117c0c382b has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-117c0c382b


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036661
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2036506] Please branch and build perl-XML-Dumper for EPEL-9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036506

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #2 from Fedora Update System  ---
FEDORA-EPEL-2022-f2b758df21 has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-f2b758df21


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036506
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2036504] Please branch and build perl-Exporter-Tidy for EPEL-9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036504

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #2 from Fedora Update System  ---
FEDORA-EPEL-2022-96e018404b has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-96e018404b


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036504
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: New tool - license-validate

2022-01-04 Thread Robbie Harwood
Neal Gompa  writes:

> On Tue, Jan 4, 2022 at 2:25 PM Robbie Harwood  wrote:
>>
>> Neal Gompa  writes:
>>
>> > SPDX expression logic is identical to Fedora's, so that will not
>> > change.
>>
>> I don't believe that's correct.
>>
>> For instance, for the LGPL, SPDX uses "LGPL-2.0-only" and
>> "LGPL-2.0-or-later", while Fedora currently uses "LGPLv2" and "LGPLv2+".
>>
>> (From https://spdx.org/licenses/ and
>> https://fedoraproject.org/wiki/Licensing:Main )
>>
>
> Those are the identifiers, not the *logic*. SPDX and Fedora both use
> the same boolean logic terms ("and"/"or"/"with") and support
> parenthetical expressions. Fedora mandates lowercase, SPDX doesn't
> care, but examples historically are uppercase. Fedora will retain its
> expression logic system, complete with lowercase terms (since that
> makes the expressions more readable).

Fine, but that's misleading in this context.  Right now the tool flags
(and therefore bugs have been filed for) the identifiers as well.

Be well,
--Robbie


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


[Bug 2036498] Please branch and build perl-Parallel-Iterator for EPEL-9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036498

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #2 from Fedora Update System  ---
FEDORA-EPEL-2022-0cf8bddb9b has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-0cf8bddb9b


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036498
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: New tool - license-validate

2022-01-04 Thread David Cantrell

On Tue, Jan 04, 2022 at 02:40:06PM -0500, Neal Gompa wrote:

On Tue, Jan 4, 2022 at 2:25 PM Robbie Harwood  wrote:


Neal Gompa  writes:

> SPDX expression logic is identical to Fedora's, so that will not
> change.

I don't believe that's correct.

For instance, for the LGPL, SPDX uses "LGPL-2.0-only" and
"LGPL-2.0-or-later", while Fedora currently uses "LGPLv2" and "LGPLv2+".

(From https://spdx.org/licenses/ and
https://fedoraproject.org/wiki/Licensing:Main )



Those are the identifiers, not the *logic*. SPDX and Fedora both use
the same boolean logic terms ("and"/"or"/"with") and support
parenthetical expressions. Fedora mandates lowercase, SPDX doesn't
care, but examples historically are uppercase. Fedora will retain its
expression logic system, complete with lowercase terms (since that
makes the expressions more readable).


One of the difficult things with the Fedora abbreviations is that
tokens can have spaces in them.  For example, the Apache 2.0 license
in Fedora is called "ASL 2.0".  This makes it really hard to work with
in software.

Likewise, we have historically allowed full expressions through that
contain otherwise forbidden licenses.  For example, many Perl module
packages use the License tag "GPL+ or Artistic" so in a way that
entire expression is treated as a token.

This information is currently captured in this JSON file (not the
original author, but I make use of the file):


https://github.com/rpminspect/rpminspect-data-fedora/blob/master/licenses/fedora.json

rpminspect's license check uses this data to validate the License tag
in RPM headers based on the rules as they exist in the packaging
guidelines plus the assorted expressions we have historically allowed
through that would not otherwise validate.

If your License tag fails the check in rpminspect, it will report the
unapproved token based on the fedora.json file it read.

All of this is to say that the ongoing effort to permit SPDX
expressions in the License is to make this inspection more predictable
and Fedora's License tags more useful.

Thanks,

--
David Cantrell 
Red Hat, Inc. | Boston, MA | EST5EDT
___
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


[Bug 2036225] Please branch and build perl-Test-Portability-Files for EPEL-9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036225

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #2 from Fedora Update System  ---
FEDORA-EPEL-2022-898852af3c has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-898852af3c


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036225
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2036497] Please branch and build perl-Dir-Self for EPEL-9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036497

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #2 from Fedora Update System  ---
FEDORA-EPEL-2022-8215b3ffdc has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-8215b3ffdc


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036497
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: New tool - license-validate

2022-01-04 Thread Neal Gompa
On Tue, Jan 4, 2022 at 2:25 PM Robbie Harwood  wrote:
>
> Neal Gompa  writes:
>
> > SPDX expression logic is identical to Fedora's, so that will not
> > change.
>
> I don't believe that's correct.
>
> For instance, for the LGPL, SPDX uses "LGPL-2.0-only" and
> "LGPL-2.0-or-later", while Fedora currently uses "LGPLv2" and "LGPLv2+".
>
> (From https://spdx.org/licenses/ and
> https://fedoraproject.org/wiki/Licensing:Main )
>

Those are the identifiers, not the *logic*. SPDX and Fedora both use
the same boolean logic terms ("and"/"or"/"with") and support
parenthetical expressions. Fedora mandates lowercase, SPDX doesn't
care, but examples historically are uppercase. Fedora will retain its
expression logic system, complete with lowercase terms (since that
makes the expressions more readable).


-- 
真実はいつも一つ!/ 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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: New tool - license-validate

2022-01-04 Thread Robbie Harwood
Neal Gompa  writes:

> SPDX expression logic is identical to Fedora's, so that will not
> change.

I don't believe that's correct.

For instance, for the LGPL, SPDX uses "LGPL-2.0-only" and
"LGPL-2.0-or-later", while Fedora currently uses "LGPLv2" and "LGPLv2+".

(From https://spdx.org/licenses/ and
https://fedoraproject.org/wiki/Licensing:Main )

Be well,
--Robbie


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


[Bug 2036900] Please branch and build perl-Net-LibIDN2 for EPEL 9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036900

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #2 from Fedora Update System  ---
FEDORA-EPEL-2022-8ef56d94b2 has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-8ef56d94b2


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036900
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[rpms/perl-Net-LibIDN2] PR #1: Import package to EPEL9 from rawhide

2022-01-04 Thread Michal Josef Špaček

mspacek merged a pull-request against the project: `perl-Net-LibIDN2` that you 
are following.

Merged pull-request:

``
Import package to EPEL9 from rawhide
``

https://src.fedoraproject.org/rpms/perl-Net-LibIDN2/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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[rpms/perl-Net-LibIDN2] PR #1: Import package to EPEL9 from rawhide

2022-01-04 Thread Michal Josef Špaček

mspacek opened a new pull-request against the project: `perl-Net-LibIDN2` that 
you are following:
``
Import package to EPEL9 from rawhide
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Net-LibIDN2/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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2036500] Please branch and build perl-B-Debug for EPEL-9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036500

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #2 from Fedora Update System  ---
FEDORA-EPEL-2022-df8248f4fc has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-df8248f4fc


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036500
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Is it okay to use /usr/bin/python again?

2022-01-04 Thread Nico Kadel-Garcia
On Tue, Jan 4, 2022 at 8:11 AM Miro Hrončok  wrote:
>
> On 04. 01. 22 13:57, Vitaly Zaitsev via devel wrote:
> > On 04/01/2022 11:09, Florian Weimer wrote:
> >> We have some scripts that are dual Python 2/Python 3, and Fedora tooling
> >> forced us to carry a downstream-only patch to replace /usr/bin/python
> >> with /usr/bin/python3.  I'd like to remove this patch.
> >
> > It is forbidden.
> >
> > You should switch your SPEC to modern 201x-era guidelines
>
> 202x-era
>
> > and all shebangs will
> > be handled automatically with the %pyproject_install macro.
>
> That is only happening for files installed to /usr/bin, not to files you use
> during builds.

It confuses the heck out of building Fedora. "/ur/bin/python" may not
be python3 on a remote system, especially a legacy system. Please,
explicitly use "#!/usr/bin/python3" or "#!/usr/bin/env python3".
___
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


[rpms/perl-B-Debug] PR #1: Import epel9 version from rawhide

2022-01-04 Thread Michal Josef Špaček

mspacek merged a pull-request against the project: `perl-B-Debug` that you are 
following.

Merged pull-request:

``
Import epel9 version from rawhide
``

https://src.fedoraproject.org/rpms/perl-B-Debug/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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2036508] Please branch and build perl-Data-Taxi for EPEL-9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036508

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #2 from Fedora Update System  ---
FEDORA-EPEL-2022-4b3e70787e has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-4b3e70787e


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036508
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2036509] Please branch and build perl-Data-Denter for EPEL-9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036509

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #2 from Fedora Update System  ---
FEDORA-EPEL-2022-4b3e70787e has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-4b3e70787e


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036509
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2036494] Please branch and build perl-CSS-Tiny for EPEL-9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036494

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #2 from Fedora Update System  ---
FEDORA-EPEL-2022-4b3e70787e has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-4b3e70787e


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036494
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2031799] perl-FCGI-ProcManager for EPEL 9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2031799

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #2 from Fedora Update System  ---
FEDORA-EPEL-2022-4b3e70787e has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-4b3e70787e


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2031799
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2036491] Please branch and build perl-Test-Refcount for EPEL-9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036491

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #3 from Fedora Update System  ---
FEDORA-EPEL-2022-4b3e70787e has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-4b3e70787e


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036491
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2036922] Please branch and build perl-Devel-Refcount for EPEL 9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036922

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #3 from Fedora Update System  ---
FEDORA-EPEL-2022-9821de3579 has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-9821de3579


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036922
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2036663] Please branch and build perl-IO-CaptureOutput for EPEL-9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036663

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #3 from Fedora Update System  ---
FEDORA-EPEL-2022-5f555e8624 has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-5f555e8624


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036663
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Rust Stack Spring Cleaning (in Winter)

2022-01-04 Thread Josh Stone
Thank you for working on this, Fabio!

On Mon, Dec 20, 2021 at 6:32 AM Fabio Valentini 
wrote:

> Hello Rust packagers,
>
> (I'm sending this email to the devel and rust lists, and I've added all
> directly
> affected package maintainers in Bcc - because adding them all to the "To"
> or
> "CC" fields would make the lists reject this message, I believe.)
>
> I have been working on and preparing some more clean-ups in the Rust
> stack, and
> I came across a large-ish number of Rust packages that were imported to
> Fedora,
> but the recommended "initial setup" for them was never finished.
>
> I have started by adding them all "rust-*" packages to koschei, which
> makes it
> way easier for me to see at a glance whether there are any broken packages
> in
> our Rust stack at any point in time.
>
> I will also make sure all those packages are correctly set up with anitya /
> release-monitoring.org, so that we actually get notifications for new
> versions
> of all those crate packages.
>
> Additionally, I would ask of all of you to make sure all your packages
> have been
> added to the @rust-sig group on src.fedoraproject.org (at least with
> "commit"
> access). Without that, it makes it very hard for us to keep the Rust stack
> up-to-date and in working order, because the "rust-sig" list / bugzilla
> account
> does not get CC'd on new bugs that way, and your bugs do not show up in our
> BugZilla queries.
>
> For example, I have been working on packaging and updating the RustCrypto
> stack of crates, and found that most of the already existing
> (security-sensitive!) crates are not "completely" set up, and are now out
> of
> date, just because I didn't even know about those packages (and some were
> also
> not set up with release-monitoring.org).
>
> In the interest of keeping the Rust stack in Fedora in a good state, please
> add "@rust-sig" group to all you Rust packages on src.fedoraproject.org,
> unless
> there is a very good reason not to do so (and if that is the case for a
> particular package in this list, I'd be interested in knowing the reason,
> as
> well).
>
> If you want a scripted way of adding "@rust-sig" group to many packages,
> you
> can generate an API token on src.fedoraproject.org (with "Modify an
> existing
> project") access level, and use the simple Python script from this GitHub
> gist:
>
> https://gist.github.com/decathorpe/9d128982cb00e2d345d9e397372538ec
>
> Below is the list of "incompletely set-up" packages, in alphabetic order,
> and
> at the bottom, there is a list of packages per affected package maintainer.
>
> Thanks,
> Fabio
>
> ===
>
> - rust-arrayvec0.5: eclipseo
> - rust-asn1: cheimes
> - rust-asn1_derive: cheimes
> - rust-assert-impl: dcavalca
> - rust-aws-nitro-enclaves-cose: pbrobinson
> - rust-benfred-read-process-memory: dcavalca
> - rust-biscuit: orphan
> - rust-bitfield: ignatenkobrain
> - rust-block-cipher: ignatenkobrain
> - rust-blsctl: javierm
> - rust-btrd: dcavalca
> - rust-bytelines: ignatenkobrain
> - rust-clap_generate: eclipseo
> - rust-clap_generate_fig: eclipseo
> - rust-clircle: eclipseo
> - rust-combine: dcavalca
> - rust-console0.13: ignatenkobrain
> - rust-cryptoki: pbrobinson
> - rust-cryptoki-sys: pbrobinson
> - rust-cty: nickblack
> - rust-dbus-codegen: pbrobinson
> - rust-dbus-crossroads: pbrobinson
> - rust-derivative: pbrobinson
> - rust-directories-next: jbtrystram
> - rust-dirs2: ignatenkobrain
> - rust-elf: dcavalca
> - rust-enumflags2: ignatenkobrain, pbrobinson
> - rust-env_proxy: dcavalca
> - rust-epoll: slp
> - rust-event-listener: dcavalca
> - rust-fasteval: zbyszek
> - rust-hostname-validator: ignatenkobrain
> - rust-inferno: dcavalca
> - rust-itertools0.9: ignatenkobrain
> - rust-josekit: pbrobinson
> - rust-js-sys: pbrobinson
> - rust-keccak: pbrobinson
> - rust-log-panics: salimma
> - rust-mbox: ignatenkobrain, pbrobinson
> - rust-navi: jbtrystram
> - rust-netlink-packet-core: cathay4t, ffmancera
> - rust-netlink-packet-route: cathay4t, ffmancera
> - rust-netlink-packet-utils: cathay4t, ffmancera
> - rust-netlink-proto: cathay4t, ffmancera
> - rust-netlink-sys: cathay4t, ffmancera
> - rust-num-format: dcavalca
> - rust-oauth2: ctron, jbtrystram
> - rust-oid: pbrobinson
> - rust-openat-ext: walters
> - rust-pam-sys: eneville
> - rust-parsec-client: pbrobinson
> - rust-parsec-interface: pbrobinson
> - rust-picky-asn1: pbrobinson
> - rust-picky-asn1-der: pbrobinson
> - rust-picky-asn1-x509: pbrobinson
> - rust-psa-crypto: pbrobinson
> - rust-pkcs11: pbrobinson
> - rust-pleaser: eneville
> - rust-process_control: atim, petersen
> - rust-proc-maps: dcavalca
> - rust-prost: pbrobinson
> - rust-prost-build: pbrobinson
> - rust-prost-derive: pbrobinson
> - rust-prost-types: pbrobinson
> - rust-psa-crypto-sys: pbrobinson
> - rust-qstring: ctron, jbtrystram
> - rust-rand0.7: ignatenkobrain
> - rust-rand_chacha0.2: ignatenkobrain
> - rust-rand_core0.5: ignatenkobrain
> - rust-rand_pcg0.2: ignatenkobrain
> - rust-rbspy-ruby-structs: dcavalca
> - 

[rpms/perl-B-Debug] PR #1: Import epel9 version from rawhide

2022-01-04 Thread Michal Josef Špaček

mspacek opened a new pull-request against the project: `perl-B-Debug` that you 
are following:
``
Import epel9 version from rawhide
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-B-Debug/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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2034172] EPEL9 branch of perl-File-Find-Rule-Perl

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2034172

Fedora Update System  changed:

   What|Removed |Added

 Status|NEW |MODIFIED



--- Comment #4 from Fedora Update System  ---
FEDORA-EPEL-2022-0afad54106 has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-0afad54106


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2034172
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 1757009] perl-Qt 4.14.3 missing for EPEL8

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1757009



--- Comment #4 from Troy Dawson  ---
My opinion, yes.
Bugs about qt4 in RHEL/EPEL8 can be closed.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1757009
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[EPEL-devel] [Fedocal] Reminder meeting : EPEL Steering Committee

2022-01-04 Thread tdawson
Dear all,

You are kindly invited to the meeting:
   EPEL Steering Committee on 2022-01-05 from 16:00:00 to 17:00:00 US/Eastern
   At fedora-meet...@irc.libera.chat

The meeting will be about:
This is the weekly EPEL Steering Committee Meeting.

A general agenda is the following:

#meetingname EPEL
#topic Intros
#topic Old Business
#topic EPEL-7
#topic EPEL-8
#topic EPEL-9
#topic Openfloor
#endmeeting




Source: https://calendar.fedoraproject.org//meeting/9854/

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


[Bug 2036507] Please branch and build perl-PHP-Serialization for EPEL-9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036507

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #2 from Fedora Update System  ---
FEDORA-EPEL-2022-ad290a5a20 has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-ad290a5a20


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036507
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2037002] New: Please branch and build perl-Convert-Bencode_XS for EPEL 9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2037002

Bug ID: 2037002
   Summary: Please branch and build perl-Convert-Bencode_XS for
EPEL 9
   Product: Fedora EPEL
   Version: epel9
Status: NEW
 Component: perl-Convert-Bencode_XS
  Assignee: jples...@redhat.com
  Reporter: p...@city-fan.org
QA Contact: extras...@fedoraproject.org
CC: iarn...@gmail.com, jples...@redhat.com,
perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Could you please branch and build perl-Convert-Bencode_XS for EPEL 9 ?

If you like you could add me (FAS: pghmcfc) as a committer to the package and
I'll do it myself.

Override is in place for Devel::Leak.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2037002
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2035898] perl-bignum-0.64 is available

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2035898

Jitka Plesnikova  changed:

   What|Removed |Added

 Resolution|--- |RAWHIDE
   Fixed In Version||perl-bignum-0.64-1.fc36
 Status|ASSIGNED|CLOSED
Last Closed||2022-01-04 15:42:00




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2035898
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[EPEL-devel] Re: Packages disappearing from the EPEL 9 buildroot

2022-01-04 Thread Troy Dawson
On Wed, Dec 29, 2021 at 7:15 AM Stephen John Smoogen 
wrote:

>
>
> On Wed, 29 Dec 2021 at 06:29, Mattias Ellert 
> wrote:
>
>> Hi!
>>
>> Two packages I built for EPEL 9 are now reported by koschei as having
>> missing build dependencies.
>>
>> https://koschei.fedoraproject.org/package/davix?collection=epel9
>>
>> https://koschei.fedoraproject.org/package/uglify-js?collection=epel9
>>
>> The EPEL 9 builds were built using the following build dependencies
>> according to the root.log files:
>>
>> rapidjson-devel-1.1.0-19.el9
>>
> Looks like this is a RHEL buildroot only package, thus can just be built
in EPEL9.
 https://docs.fedoraproject.org/en-US/epel/epel-package-request/


>> web-assets-devel-5-15.el9
>>
> Although web-assets is built in RHEL9, they are only releasing
web-assets-filesystem
Thus, we are missing web-assets-devel and web-assets-httpd
https://docs.fedoraproject.org/en-US/epel/epel-faq/#rhel_8_has_binaries_in_the_release_but_is_missing_some_corresponding__devel_package._how_do_i_build_a_package_that_needs_that_missing__devel_package


> nodejs-packaging-2021.01-5.el9
>>
> Looks like this is a buildroot only package, thus can just be built in
EPEL9.
Definitely something we need.  I believe I can take that.


>> These can no longer be found in the koji buildroot. There are no
>> expired buildroot overrides for these builds, which could explain the
>> disappearance.
>>
>> I can't find these builds in EPEL's koji, so I guess they where
>> provided by RHEL, but now are no longer? Did RHEL dop these?
>>
>>
> OK there was a period in the EPEL-9 startup where the buildroot was
> pointing to a copy of the CentOS Stream-9 koji build root. This was done to
> help kickstart things, but it had the issue that packages that RHEL is not
> going to ship to customers were available also. About 2-3 weeks ago, the
> EPEL steering committee decided to move the buildroot to the properly
> shipped chain of packages in CentOS Stream versus the buildroot. This
> removed a bunch of packages that were 'available' but not going to be
> shipped. These packages will need to be made into epel-only packages or
> some other solution. I am fuzzy on this myself as I am from a different
> philosophy school of building and shipping packages.
>
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: F36 Change: Hunspell Dictionary dir change (System-Wide Change proposal)

2022-01-04 Thread Caolán McNamara
On Thu, 2021-12-30 at 09:21 +, Zbigniew Jędrzejewski-Szmek wrote:
> On Wed, Dec 29, 2021 at 10:01:49AM -0500, Ben Cotton wrote:
> > == How To Test ==
> > 1. Check if default installed dictionary path is
> > `/usr/share/hunspell/` instead of `/usr/share/myspell/`
> 
> Would it be possible to symlink /usr/share/myspell → hunspell
> so that applications which try to use the old path still work?

IIRC replacing a dir with a symlink needs special care
https://docs.fedoraproject.org/en-US/packaging-guidelines/Directory_Replacement/
___
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


[Bug 2031907] [RFE:EPEL9] EPEL9 branch for perl-Parse-EDID

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2031907

Pat Riehecky  changed:

   What|Removed |Added

   Doc Type|--- |If docs needed, set a value



--- Comment #1 from Pat Riehecky  ---
Will you be able to branch and build perl-Parse-EDID in epel9?


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2031907
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[EPEL-devel] Re: GIMP future in RHEL-9

2022-01-04 Thread Josef Řídký
Basically all those
https://gitlab.gnome.org/GNOME/gimp/-/issues?milestone_title=3.0 should be
done to be able to release GIMP 3 (the blockers are minimum)

Best regards

Josef Ridky
Senior Software Engineer
Core Services Team
Red Hat Czech, s.r.o.


On Tue, Jan 4, 2022 at 3:29 PM Patrick Riehecky  wrote:

> Exciting news, is there a link to the ticket(s) the GIMP folks need
> help with?  Odds are I'm not qualified but I'd be happy to look.
>
> Pat
>
> On Mon, 2022-01-03 at 10:46 +0100, Josef Řídký wrote:
> > Hi folks,
> >
> > just want to send some heads up info about the GIMP package in the
> > RHEL-9 release.
> >
> > As some of you might notice, the GIMP package is missing in RHEL-9.
> > The reason for this is it's requirement of Python 2, which isn't
> > supported in RHEL-9 any more.
> >
> > During the RHEL-9 prep phase, I gave the information that GIMP
> > authors are working on a new GIMP 3 release, which is going to use
> > Python 3 and once the GIMP 3 is released, the GIMP package will
> > appear in RHEL-9 again.
> >
> > Carrying this in mind I would like to ask you - *don't* create a gimp
> > branch for EPEL9 as it would create additional problems later once
> > the GIMP 3 is available.
> >
> > Thank you for your understanding and wish you all the best in 2022.
> >
> > Best regards
> >
> > Josef Ridky
> > Senior Software Engineer
> > Core Services Team
> > Red Hat Czech, s.r.o.
> > ___
> > epel-devel mailing list -- epel-devel@lists.fedoraproject.org
> > To unsubscribe send an email to
> > epel-devel-le...@lists.fedoraproject.org
> > Fedora Code of Conduct:
> >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.fedoraproject.org_en-2DUS_project_code-2Dof-2Dconduct_=DwIGaQ=gRgGjJ3BkIsb5y6s49QqsA=OAMtP0DWou0nlXG7Kmxo2enjXJfwb1DXS9fwcaESuTE=aY3yyEdKnq6EEFYxpw5EqiYzGUDlKKnpxlBW9-YKs0wQcHNEcWGdJ_MmQaOuyG0c=Q7CFNH_zj_nG0lJyEfHOJWx6HpNzA_jvcSP9cPtO9fE=
> >
> > List Guidelines:
> >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__fedoraproject.org_wiki_Mailing-5Flist-5Fguidelines=DwIGaQ=gRgGjJ3BkIsb5y6s49QqsA=OAMtP0DWou0nlXG7Kmxo2enjXJfwb1DXS9fwcaESuTE=aY3yyEdKnq6EEFYxpw5EqiYzGUDlKKnpxlBW9-YKs0wQcHNEcWGdJ_MmQaOuyG0c=67A9RrSpbyiE9v1wz_1q-Td7xCJdj9G90SeqHvErlOw=
> >
> > List Archives:
> >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.fedoraproject.org_archives_list_epel-2Ddevel-40lists.fedoraproject.org=DwIGaQ=gRgGjJ3BkIsb5y6s49QqsA=OAMtP0DWou0nlXG7Kmxo2enjXJfwb1DXS9fwcaESuTE=aY3yyEdKnq6EEFYxpw5EqiYzGUDlKKnpxlBW9-YKs0wQcHNEcWGdJ_MmQaOuyG0c=kAl4lCo-mXAXsVWRiOErhqNwEAGEw2hyrRrAzWRqUyI=
> >
> > Do not reply to spam on the list, report it:
> >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__pagure.io_fedora-2Dinfrastructure=DwIGaQ=gRgGjJ3BkIsb5y6s49QqsA=OAMtP0DWou0nlXG7Kmxo2enjXJfwb1DXS9fwcaESuTE=aY3yyEdKnq6EEFYxpw5EqiYzGUDlKKnpxlBW9-YKs0wQcHNEcWGdJ_MmQaOuyG0c=hTghf8KHuuL0GMLfuyqZWdV4_xylLjUOuuFDLsS1QY0=
> >
>
> ___
> epel-devel mailing list -- epel-devel@lists.fedoraproject.org
> To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


[EPEL-devel] Re: Status of python-gevent in EL9

2022-01-04 Thread Neal Gompa
On Tue, Jan 4, 2022 at 9:45 AM Troy Dawson  wrote:
>
>
>
> On Wed, Dec 29, 2021 at 7:30 AM Stephen John Smoogen  wrote:
>>
>>
>>
>> On Wed, 29 Dec 2021 at 10:19, Orion Poplawski  wrote:
>>>
>>> Can someone shed light on the status of python-gevent in EL9?  It seems
>>> to have been built for CS9:
>>>
>>> https://kojihub.stream.centos.org/koji/packageinfo?packageID=3414
>>>
>>> (though perhaps not tagged?)
>>>
>>> but builds for EPEL9 fail to find it:
>>>
>>> https://koji.fedoraproject.org/koji/taskinfo?taskID=80607754
>>>
>>
>> This is a RHEL/CentOS Stream buildroot only package. It is only available in 
>> the koji buildroot and will not be shipped. An equivalent package will need 
>> to be built in EPEL to make builds work.
>
>
> I'm not even sure it's in the buildroot.
> One quick thing to look at is the tags of the builds.
> If you look at both of the builds, you will see that they have no tags.
> This is an indication that at some point the package was built for RHEL9, but 
> has been taken out.
>

python-gevent was retired months ago:
https://gitlab.com/redhat/centos-stream/rpms/python-gevent/-/commit/73165a8ecd3da98543292a9aa4f6924029a1d651



-- 
真実はいつも一つ!/ Always, there's only one truth!
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


[EPEL-devel] Re: Status of python-gevent in EL9

2022-01-04 Thread Troy Dawson
On Wed, Dec 29, 2021 at 7:30 AM Stephen John Smoogen 
wrote:

>
>
> On Wed, 29 Dec 2021 at 10:19, Orion Poplawski  wrote:
>
>> Can someone shed light on the status of python-gevent in EL9?  It seems
>> to have been built for CS9:
>>
>> https://kojihub.stream.centos.org/koji/packageinfo?packageID=3414
>>
>> (though perhaps not tagged?)
>>
>> but builds for EPEL9 fail to find it:
>>
>> https://koji.fedoraproject.org/koji/taskinfo?taskID=80607754
>>
>>
> This is a RHEL/CentOS Stream buildroot only package. It is only available
> in the koji buildroot and will not be shipped. An equivalent package will
> need to be built in EPEL to make builds work.
>

I'm not even sure it's in the buildroot.
One quick thing to look at is the tags of the builds.
If you look at both of the builds, you will see that they have no tags.
This is an indication that at some point the package was built for RHEL9,
but has been taken out.

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


[Fedocal] Reminder meeting : Fedora Source-git SIG

2022-01-04 Thread csomh
Dear all,

You are kindly invited to the meeting:
   Fedora Source-git SIG on 2022-01-05 from 14:30:00 to 15:30:00 GMT
   At meet.google.com/mic-otnv-kse

The meeting will be about:
Meeting of the Fedora source-git SIG

Agenda:
https://pagure.io/fedora-source-git/sig/issues?tags=meeting=Open

SIG Info:
https://fedoraproject.org/wiki/SIGs/Source-git


Source: https://calendar.fedoraproject.org//meeting/10101/

___
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


[EPEL-devel] Re: GIMP future in RHEL-9

2022-01-04 Thread Patrick Riehecky
Exciting news, is there a link to the ticket(s) the GIMP folks need
help with?  Odds are I'm not qualified but I'd be happy to look.

Pat

On Mon, 2022-01-03 at 10:46 +0100, Josef Řídký wrote:
> Hi folks,
> 
> just want to send some heads up info about the GIMP package in the
> RHEL-9 release.
> 
> As some of you might notice, the GIMP package is missing in RHEL-9.
> The reason for this is it's requirement of Python 2, which isn't
> supported in RHEL-9 any more.
> 
> During the RHEL-9 prep phase, I gave the information that GIMP
> authors are working on a new GIMP 3 release, which is going to use
> Python 3 and once the GIMP 3 is released, the GIMP package will
> appear in RHEL-9 again.
> 
> Carrying this in mind I would like to ask you - *don't* create a gimp
> branch for EPEL9 as it would create additional problems later once
> the GIMP 3 is available.
> 
> Thank you for your understanding and wish you all the best in 2022.
> 
> Best regards
> 
> Josef Ridky
> Senior Software Engineer
> Core Services Team
> Red Hat Czech, s.r.o.
> ___
> epel-devel mailing list -- epel-devel@lists.fedoraproject.org
> To unsubscribe send an email to
> epel-devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.fedoraproject.org_en-2DUS_project_code-2Dof-2Dconduct_=DwIGaQ=gRgGjJ3BkIsb5y6s49QqsA=OAMtP0DWou0nlXG7Kmxo2enjXJfwb1DXS9fwcaESuTE=aY3yyEdKnq6EEFYxpw5EqiYzGUDlKKnpxlBW9-YKs0wQcHNEcWGdJ_MmQaOuyG0c=Q7CFNH_zj_nG0lJyEfHOJWx6HpNzA_jvcSP9cPtO9fE=
>  
> List Guidelines:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__fedoraproject.org_wiki_Mailing-5Flist-5Fguidelines=DwIGaQ=gRgGjJ3BkIsb5y6s49QqsA=OAMtP0DWou0nlXG7Kmxo2enjXJfwb1DXS9fwcaESuTE=aY3yyEdKnq6EEFYxpw5EqiYzGUDlKKnpxlBW9-YKs0wQcHNEcWGdJ_MmQaOuyG0c=67A9RrSpbyiE9v1wz_1q-Td7xCJdj9G90SeqHvErlOw=
>  
> List Archives:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.fedoraproject.org_archives_list_epel-2Ddevel-40lists.fedoraproject.org=DwIGaQ=gRgGjJ3BkIsb5y6s49QqsA=OAMtP0DWou0nlXG7Kmxo2enjXJfwb1DXS9fwcaESuTE=aY3yyEdKnq6EEFYxpw5EqiYzGUDlKKnpxlBW9-YKs0wQcHNEcWGdJ_MmQaOuyG0c=kAl4lCo-mXAXsVWRiOErhqNwEAGEw2hyrRrAzWRqUyI=
>  
> Do not reply to spam on the list, report it:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__pagure.io_fedora-2Dinfrastructure=DwIGaQ=gRgGjJ3BkIsb5y6s49QqsA=OAMtP0DWou0nlXG7Kmxo2enjXJfwb1DXS9fwcaESuTE=aY3yyEdKnq6EEFYxpw5EqiYzGUDlKKnpxlBW9-YKs0wQcHNEcWGdJ_MmQaOuyG0c=hTghf8KHuuL0GMLfuyqZWdV4_xylLjUOuuFDLsS1QY0=
>  

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


Re: F36 Change: Default To Noto Fonts (System-Wide Change proposal)

2022-01-04 Thread Kevin Kofler via devel
Kevin Kofler via devel wrote:
> I see in this table that there are still a bunch of languages using
> non-Noto fonts where there appears to be a Noto equivalent available,
> e.g., https://fonts.google.com/noto shows me Devanagari, Bengali, and
> Tamil on the first page whereas your table indicates that Lohit fonts will
> continue to be used there. What is the reason for that? Are the Noto fonts
> for those scripts incomplete? I think using Noto wherever possible would
> lead to a more consistent experience.

Another case is the math symbols: Should the default sans-serif math font be 
changed to Noto Sans Math? STIX is a serif font, so it probably makes sense 
to keep as the serif math font (also considering that there is, at least at 
this time, no Noto Serif Math). For cases where the distinction matters, 
see, e.g., the summation sign (clearly visible serifs), the integral sign 
(dots at the ends that are a form of serifs), or the partial derivative sign 
(constant stroke thickness in Noto Sans Math vs. variable in STIX).

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


buildroot size growth

2022-01-04 Thread Vít Ondruch
It seems that Rawhide buildroot has grown some dependencies between 10th 
and 23rd of December.


The last official build of Ruby I did [1] installs  152 packages:

~~~

DEBUG util.py:446:  Install  152 Packages
DEBUG util.py:446:  Total download size: 59 M
DEBUG util.py:446:  Installed size: 231 M

~~~


While scratch build [2] done by Koschei on Dec 23 already installs 169 
packages:



~~~

DEBUG util.py:446:  Install  169 Packages
DEBUG util.py:446:  Total download size: 65 M
DEBUG util.py:446:  Installed size: 250 M

~~~


One of the packages which caught my attention and previously was not 
installed is systemd (there always were just systemd-libs). So is 
systemd to blame or is it something else?



Vít



[1] 
https://kojipkgs.fedoraproject.org//packages/ruby/3.0.3/155.fc36/data/logs/x86_64/root.log


[2] https://kojipkgs.fedoraproject.org//work/tasks/3061/80383061/root.log




OpenPGP_signature
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2036922] Please branch and build perl-Devel-Refcount for EPEL 9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036922

Paul Howarth  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED



--- Comment #2 from Paul Howarth  ---
(In reply to Robin Lee from comment #1)
> Ownership is passed to you.

Many thanks.

https://pagure.io/releng/fedora-scm-requests/issue/40411


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036922
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Copr success but no packages?

2022-01-04 Thread Steven A. Falco

On 1/4/22 04:28 AM, Vitaly Zaitsev via devel wrote:

On 03/01/2022 22:25, Steven A. Falco wrote:

The builder-live.log in the F35 dir shows that the rpms were written, but they 
are missing from the dir.


Too aggressive web cache on COPR side. I've seen this issue several times too.


Thanks for all the replies.  It is unfortunate, but now that I have a 
work-around I can live with it.

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


use of kernel/yama/ptrace_scope in rpm scriptlets

2022-01-04 Thread Marius Schwarz

Happy New Year everyone,

noticed on device: Pinephone

At least since early last year, most likely much longer, rpm scriptlets 
report this message:


Couldn't write '0' to 'kernel/yama/ptrace_scope', ignoring: No such file 
or directory


Can the one responsible please add some sort of check to the scriptlet:

if [ -e "..kernel/yama/ptrace_scope" ]; then
  echo "0" > ..kernel/yama/ptrace_scope
fi

or, as it seems to be an irrelevant message, use > /dev/null ?

I would really like to help out with such small stuff, when I'm allowed 
in the maintaier/packager gang ;)



best regards,
Marius

___
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


[Bug 2036922] Please branch and build perl-Devel-Refcount for EPEL 9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036922

Robin Lee  changed:

   What|Removed |Added

   Assignee|robinlee.s...@gmail.com |p...@city-fan.org




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036922
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2036922] Please branch and build perl-Devel-Refcount for EPEL 9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036922

Robin Lee  changed:

   What|Removed |Added

   Doc Type|--- |If docs needed, set a value



--- Comment #1 from Robin Lee  ---
(In reply to Paul Howarth from comment #0)
> Could you please branch and build perl-Devel-Refcount for EPEL 9 ?
> 
> If you like you could add me (FAS: pghmcfc) as a committer to the package
> and I'll do it myself.

Ownership is passed to you.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036922
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Is it okay to use /usr/bin/python again?

2022-01-04 Thread Miro Hrončok

On 04. 01. 22 13:57, Vitaly Zaitsev via devel wrote:

On 04/01/2022 11:09, Florian Weimer wrote:

We have some scripts that are dual Python 2/Python 3, and Fedora tooling
forced us to carry a downstream-only patch to replace /usr/bin/python
with /usr/bin/python3.  I'd like to remove this patch.


It is forbidden.

You should switch your SPEC to modern 201x-era guidelines


202x-era

and all shebangs will 
be handled automatically with the %pyproject_install macro.


That is only happening for files installed to /usr/bin, not to files you use 
during builds.


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


Re: Is it okay to use /usr/bin/python again?

2022-01-04 Thread Vitaly Zaitsev via devel

On 04/01/2022 11:09, Florian Weimer wrote:

We have some scripts that are dual Python 2/Python 3, and Fedora tooling
forced us to carry a downstream-only patch to replace /usr/bin/python
with /usr/bin/python3.  I'd like to remove this patch.


It is forbidden.

You should switch your SPEC to modern 201x-era guidelines and all 
shebangs will be handled automatically with the %pyproject_install macro.


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


[Bug 2036922] Please branch and build perl-Devel-Refcount for EPEL 9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036922

Paul Howarth  changed:

   What|Removed |Added

 Blocks||2032430





Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=2032430
[Bug 2032430] perl-Type-Tiny for EPEL 9
-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036922
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2032430] perl-Type-Tiny for EPEL 9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2032430

Paul Howarth  changed:

   What|Removed |Added

 Depends On||2036922



--- Comment #11 from Paul Howarth  ---
Ah, I see. I remember going through the optional test modules a while back to
see which ones were available in Fedora but that must have been when
Test::Refcount still pulled in Devel::Refcount so I didn't notice it.



Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=2036922
[Bug 2036922] Please branch and build perl-Devel-Refcount for EPEL 9
-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2032430
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2036922] New: Please branch and build perl-Devel-Refcount for EPEL 9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036922

Bug ID: 2036922
   Summary: Please branch and build perl-Devel-Refcount for EPEL 9
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Devel-Refcount
  Assignee: robinlee.s...@gmail.com
  Reporter: p...@city-fan.org
QA Contact: extras...@fedoraproject.org
CC: kwiz...@gmail.com, perl-devel@lists.fedoraproject.org,
robinlee.s...@gmail.com
  Target Milestone: ---
Classification: Fedora



Could you please branch and build perl-Devel-Refcount for EPEL 9 ?

If you like you could add me (FAS: pghmcfc) as a committer to the package and
I'll do it myself.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036922
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2022551] perl-HTTP-Message-6.35 is available

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2022551



--- Comment #3 from Fedora Update System  ---
FEDORA-2022-6b7c00e649 has been submitted as an update to Fedora 34.
https://bodhi.fedoraproject.org/updates/FEDORA-2022-6b7c00e649


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2022551
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2022551] perl-HTTP-Message-6.35 is available

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2022551

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #2 from Fedora Update System  ---
FEDORA-2022-5bb8ca4ef4 has been submitted as an update to Fedora 35.
https://bodhi.fedoraproject.org/updates/FEDORA-2022-5bb8ca4ef4


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2022551
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


RE: F36 Change: DIGLIM (System-Wide Change proposal)

2022-01-04 Thread Roberto Sassu via devel
> From: Panu Matilainen [mailto:pmati...@redhat.com]
> Sent: Tuesday, January 4, 2022 12:27 PM
> On 1/4/22 10:41, Roberto Sassu via devel wrote:
> > Hi everyone
> >
> > in the FESCo meeting yesterday, Zbigniew asked what is
> > the relationship between this feature and
> > https://fedoraproject.org/wiki/Changes/FsVerityRPM.
> > I try to explain here.
> >
> > Both features aim at providing reference values, i.e.
> > values of software fingerprint certified by the software
> > vendor, in order to enforce an integrity policy.
> >
> > The main difference between the features is the
> > granularity at which the vendor certifies the software
> > fingerprints. DIGLIM adopts the current scheme of RPMs,
> > and verifies with one signature all the files contained in
> > the RPM. Since this data format is not suitable for use
> > by the Linux kernel, for enforcing the integrity policy,
> > DIGLIM extracts the digests and adds them in a hash
> > table stored in kernel memory. Enforcement (it would
> > be better to say security decision) is achieved by doing
> > a lookup in the hash table.
> >
> > The main advantage is that DIGLIM can achieve its
> > objective, providing reference values, without any
> > change to existing RPMs. It could support fsverity
> > digests, in addition to file digests, to achieve the same
> > objective of the FsVerityRPM feature. This would
> > require introducing a new RPM header section similar
> > to RPMTAG_FILEDIGESTS.
> >
> > The FsVerityRPM feature, on the other hand, similarly
> > to the IMA file signature approach, re-signs all (or the
> > desired subset of) files, and adds the signatures in a
> > dedicated section of the RPM header, with increased
> > size overhead.
> >
> > The advantage of FsVerityRPM and the IMA file
> > signatures approach is that the data format is already
> > suitable for enforcement by fsverity and IMA.
> 
> I haven't looked at the details at all, but from a rpm POV birds-eye
> perspective: applauds for the approach!

Thanks Panu! I appreciate it.

Roberto

HUAWEI TECHNOLOGIES Duesseldorf GmbH, HRB 56063
Managing Director: Li Peng, Zhong Ronghua

> Besides not bloating up RPMs with seriously expensive per-file data,
> this side-steps the other issues associated with both IMA and fs-verity:
> both require separate signing steps for the file signatures which is a
> non-trivial cost and complexity, and unlike those the file hashes are
> covered (and thus protected) by normal rpm-level signatures too.
> 
>   - Panu -
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-
> of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it: https://pagure.io/fedora-
> infrastructure
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2032430] perl-Type-Tiny for EPEL 9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2032430



--- Comment #10 from Ralf Corsepius  ---
(In reply to Paul Howarth from comment #9)
> I don't see where the dependency on Devel::Refcount comes from.

The testsuite uses it:

Type-Tiny-1.012004/Makefile.PL: Devel::Refcount
Type-Tiny-1.012004/t/20-unit/Type-Registry/refcount.t:use Test::Requires
'Devel::Refcount';
Type-Tiny-1.012004/t/20-unit/Type-Registry/refcount.t:use Devel::Refcount
'refcount';
Type-Tiny-1.012004/t/20-unit/Type-Tiny/refcount.t:use Test::Requires
'Devel::Refcount';
Type-Tiny-1.012004/t/20-unit/Type-Tiny/refcount.t:use Devel::Refcount
'refcount';


If you remove BR: perl(Devel::Refcount) from the *.spec, the testsuite
complains about it:
t/20-unit/Type-Tiny/refcount.t  skipped: Test
requires module 'Devel::Refcount' but it's not found


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2032430
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


[Bug 2036900] Please branch and build perl-Net-LibIDN2 for EPEL 9

2022-01-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2036900

Michal Josef Spacek  changed:

   What|Removed |Added

   Doc Type|--- |If docs needed, set a value
 Status|NEW |ASSIGNED



--- Comment #1 from Michal Josef Spacek  ---
Branch requested: https://pagure.io/releng/fedora-scm-requests/issue/40409


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036900
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


  1   2   >