Licensing guidelines for AppStream project_license

[Otto Urpelainen]

I asked this question a while ago on the packaging mailing list [0], but 
did not receive any replies. Let me try again here on devel with more 
subscribers:


During the package review of qvge [1], the following question came up: 
Are the any requirements placed on the contents of AppStream metadata, 
particularly the field project_license [2]? It feels natural that is 
MUST be the same (modulo differences in notation) as specfile License, 
since both have the same meaning. However, I cannot find anything in 
Licensing Guidelines about this.


In my experience, this comes up quite often, since upstreams often have 
bundled dependencies or other copy-pasted code with different license 
than upstream's own code, yet AppStream metadata, LICENSE file, README 
and so only list upstream's own license.


[0]: 
https://lists.fedoraproject.org/archives/list/packag...@lists.fedoraproject.org/thread/HMDNWXRVTW37E5TOY6SU2BJ24KFJNZLY/

[1]: https://bugzilla.redhat.com/show_bug.cgi?id=1913870
[2]: 
https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-project_license


Otto
___
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: EPEL build target in COPR

[Pavel Raiskup]

On Wednesday, May 19, 2021 1:57:17 AM CEST Leon Fauster wrote:
> Dear all, the EPEL build target in COPR build packages based on
> CentOS Linux 8. What happens at EOL of CentOS Linux 8?  Any clues?

Copr just uses `mock-core-configs` package, and the `epel-*.cfg` files
there.

I believe that anyone who will need to do local builds (including Fedora
Copr) will be able to get the appropriate subscription [1], and so we'll
be able to change the epel-8 config from centos+epel to rhel+epel in
mock-core-configs.  Btw. there already are some `rhelepel-*` configs
(feel free to try them, as that's what will be in epel-*, see also [2]).

I also believe that we'll be able to have some subscription for
Fedora Copr builders that will allow us to continue using
mock-core-configs in default variant.

Cross-arch builds (--forcearch) will stop working till bz#1912847 is fixed, and
this would affect Copr.

> BTW, I assume that EPEL stuff are build on RHEL.

EPEL content is built in Koji _against_ RHEL+EPEL repos.

> RHEL8.4 is out now and new EPEL builds would be done on EL8.4 while COPR
> is bounded to CL8.3 ... mmh?

I thought that this is normal situation (8.4 release is fresh), and that
CentOS 8 is supported till the end of this year - so please correct me if
I'm wrong but CentOS 8 should still get the 8.4 update?

[1] 
http://miroslav.suchy.cz/blog/archives/2021/02/08/how_to_activate_no-cost_rhel_subscription/index.html
[2] https://github.com/rpm-software-management/mock/wiki/Feature-rhelchroots

Pavel

> --
> Leon



___
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: Package review #1961174

[Robert-André Mauchin]

On 5/18/21 3:19 PM, Antonio T. sagitter wrote:

Hi all.

I have a new package in review (rhbz#1961174) that will obsolete 'mld2p4'

Please, take a look if you can; i'll review one in exchange.

Thanks.


I have started the review. In exchange could you review jpegxl:
https://bugzilla.redhat.com/show_bug.cgi?id=1922638
The dependency highway has just been pushed to Rawhide, maybe use Koji,s 
local repo for review.


Thanks.

Robert-André
___
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: Fedora CoreOS stable stream now rebased to Fedora 34

[Tomasz Torcz]

Dnia Tue, May 18, 2021 at 03:37:27PM -0400, Dusty Mabe napisał(a):
> Over the next two days we're rolling out the first Fedora 34 based
> Fedora CoreOS into the `stable` stream. 
>  
> - systemd-resolved is still enabled but not used yet [1]

  This was Fedora 33 feature.

> - Move to cgroup v2 by default [5].

  This was Fedora 31 feature.

  I was wondering: Fedora CoreOS actively undoes distribution-wide
changes (at least the two above, I remember lagging with iptables-nft
around Fedora 32).  End user may confused, seeing the list of changes
for the release X, but receiving only few of them with edition CoreOS X.

  Should such divergence be allowed?  Should Fedora CoreOS use the same
version number while not containing all the changes from main Fedora Linux?

-- 
Tomasz Torcz  “If you try to upissue this patchset I shall be 
seeking
to...@pipebreaker.pl   an IP-routable hand grenade.”  — Andrew Morton (LKML)
___
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: RPMLint 2.0 released!

[Michal Schorm]

This sounds terrific !
I too can't wait till Fedora adopts it.

> * RPMLint includes _many more checks_! Nearly all of the generally
However I always have a hard time understanding what the issue caught
by RPMLint actually is.
I would like to see some library of the checks with the explanation of
what it is, why it is important and usual examples of bad / correct
code and how to fix it. Something like CWEs (e.g. [1])
Is there something like it already by any chance ?

There is a long way between an error / warning being reported by
RPMLint with maintainer just ignoring it, and the maintainer to
understand the value and importance of having it fixed (as well as
knowledge how to fix it)

[1] https://cwe.mitre.org/data/definitions/416.html

--

Michal Schorm
Software Engineer
Core Services - Databases Team
Red Hat

--

On Tue, May 18, 2021 at 2:01 PM Neal Gompa  wrote:
>
> Hey all,
>
> Nearly four years and *754 commits* since rpmlint 1.10, we are
> releasing rpmlint 2.0.0!
>
> This new release has a _lot_ of new features, but here are the most notable:
>
> * RPMLint now is a "normal" Python application and now supports being
> imported like a standard Python module! This means that all the normal
> use-cases for RPMLint are still supported, but now you can make it a
> part of larger Python-based applications or services.
> * RPMLint uses a declarative TOML-based syntax for configuring RPMLint
> policy instead of Python code.
> * RPMLint now has an override system for the descriptions shown for
> various checks, so that distributions who want to give specific policy
> information can do so without patching the code.
> * RPMLint includes _many more checks_! Nearly all of the generally
> useful checks created by the openSUSE community have been merged into
> the tree, so distributions can now benefit from a wider offering of
> checks to implement policy enforcement.
> * RPMLint is Python 3 only and now supports Python 3.6 and newer.
> * RPMLint is now built and installed like a standard Python
> application using setuptools.
>
> I want to specifically thank Tomáš Chvátal, Martin Liska, Kristyna
> Streitova, Dirk Mueller, Miroslav Suchý, Ondřej Súkup, thisisshub, and
> Miro Hrončok as top contributors to make this release happen!
>
> Full author list with number of commits:
>
>309  Tomáš Chvátal
>197  Martin Liska
> 47  Dirk Mueller
> 26  Kristyna Streitova
> 24  Neal Gompa (ニール・ゴンパ)
> 24  marxin
> 21  Neal Gompa
> 21  Ondřej Súkup
> 14  thisisshub
> 11  Miro Hrončok
>  9  Kristýna Streitová
>  8  Miroslav Suchý
>  6  Markéta Calábková
>  5  Ville Skyttä
>  4  Ben Greiner
>  4  Frank Schreiner
>  4  Van de Bugger
>  3  David Greaves
>  3  Matwey V. Kornilov
>  2  Daniel Mach
>  2  Matthias Gerstner
>  1  Cathy Hu
>  1  Ludwig Nussel
>  1  MeggyCal
>  1  Petr Menšík
>  1  Stefan Brüns
>  1  Steve Kowalik
>  1  Werner Fink
>  1  Wolfgang Stöggl
>  1  Yanko Kaneti
>  1  tpgxyz
>
> --
> 真実はいつも一つ！/ 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
___
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] EPEL build target in COPR

[Leon Fauster]

Dear all, the EPEL build target in COPR build packages based on
CentOS Linux 8. What happens at EOL of CentOS Linux 8?  Any clues?

BTW, I assume that EPEL stuff are build on RHEL. RHEL8.4 is out now
and new EPEL builds would be done on EL8.4 while COPR is bounded to 
CL8.3 ... mmh?



--
Leon
___
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 1905190] biber FTBFS in Rawhide (F34): tests fail on different \field{sortinithash} values

[bugzilla]

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



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

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.
___
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] Fedora EPEL 7 updates-testing report

[updates]

The following Fedora EPEL 7 Security updates need testing:
 Age  URL
  11  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-680600d10f   
python-impacket-0.9.22-3.el7
   6  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-352a65d3bc   
djvulibre-3.5.25.3-23.el7
   4  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-c44d955770   
prosody-0.11.9-1.el7
   1  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-113abf45ca   
composer-1.10.22-1.el7
   1  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-4ab96a9920   
wordpress-5.1.10-1.el7


The following builds have been pushed to Fedora EPEL 7 updates-testing

highway-0.12.0-1.20210518git376a400.el7
ipv6calc-3.1.0-52.el7
ne-3.3.1-1.el7
qpid-dispatch-1.16.0-1.el7
rpki-client-7.1-1.el7
scitokens-cpp-0.6.0-2.el7
upx-3.96-9.el7

Details about builds:



 highway-0.12.0-1.20210518git376a400.el7 (FEDORA-EPEL-2021-fb5cae13e6)
 Efficient and performance-portable SIMD

Update Information:

Initial RPM

ChangeLog:


References:

  [ 1 ] Bug #1906980 - Review Request: highway - Efficient and 
performance-portable SIMD
https://bugzilla.redhat.com/show_bug.cgi?id=1906980




 ipv6calc-3.1.0-52.el7 (FEDORA-EPEL-2021-803f5347d3)
 IPv6 address format change and calculation utility

Update Information:

Final release 3.1.0

ChangeLog:

* Tue May 18 2021 Peter Bieringer  - 3.1.0-52
- Final release 3.1.0




 ne-3.3.1-1.el7 (FEDORA-EPEL-2021-48b875cd5a)
 ne, the nice editor

Update Information:

First release

ChangeLog:


References:

  [ 1 ] Bug #1952927 - Review Request: ne - ne, the nice editor
https://bugzilla.redhat.com/show_bug.cgi?id=1952927




 qpid-dispatch-1.16.0-1.el7 (FEDORA-EPEL-2021-e92fa734f6)
 Dispatch router for Qpid

Update Information:

Rebase to 1.16.0.

ChangeLog:

* Tue May 18 2021 Irina Boverman  - 1.16.0-1
- Rebased to 1.16.0




 rpki-client-7.1-1.el7 (FEDORA-EPEL-2021-ecd58b58fb)
 RPKI validator to support BGP Origin Validation

Update Information:

rpki-client 7.1 ===   * Add keep-alive support to the HTTP client
code for RRDP  * Reference-count and delete unused files synced via RRDP, as far
as possible  * In the JSON output, change the AS Number from a string ("AS123")
to an integer ("123") to make processing of the output easier  * Add an
`expires` column to CSV & JSON output, based on certificate and CRL validity
times. The `expires` value can be used to avoid route selection based on stale
data when generating VRP sets, when faced with loss of communication between
consumer and valdiator, or validator and CA repository  * Make the runtime
timeout (`-s` option) also triggers in child processes  * Improved RRDP support,
upstream encourages testing of RRDP with the `-r` option so that RRDP can be
enabled by default in a future release; please report any RRDP issues found, if
possible, directly to upstream  In the portable version,   * Improve support for
older libressl versions (although the latest stable release is recommended)  *
Add missing compat headers in release packages so they build on Alpine Linux and
macOS

ChangeLog:

* Tue May 18 2021 Robert Scheck  7.1-1
- Upgrade to 7.1 (#1961870)

References:

  [ 1 ] Bug #1961870 - 

[Bug 1905190] biber FTBFS in Rawhide (F34): tests fail on different \field{sortinithash} values

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #12 from Fedora Update System  ---
FEDORA-2021-c82dc9bfab 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-2021-c82dc9bfab`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-c82dc9bfab

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.
___
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] Fedora EPEL 8 updates-testing report

[updates]

The following Fedora EPEL 8 Security updates need testing:
 Age  URL
  13  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-e393e03d96   
screen-4.6.2-12.el8
  10  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-80b9d6d879   
python-impacket-0.9.22-3.el8
   8  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-4f73cb65d7   
cacti-1.2.17-1.el8 cacti-spine-1.2.17-1.el8
   5  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-7f3c561cd8   
radare2-5.2.1-2.el8
   4  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-86c73cc3af   
prosody-0.11.9-1.el8


The following builds have been pushed to Fedora EPEL 8 updates-testing

gdal-3.0.4-7.el8
highway-0.12.0-1.20210518git376a400.el8
ipv6calc-3.1.0-52.el8
ne-3.3.1-1.el8
qpid-dispatch-1.16.0-1.el8
rpki-client-7.1-1.el8
scitokens-cpp-0.6.0-2.el8
sparse-0.6.3-2.el8
upx-3.96-9.el8

Details about builds:



 gdal-3.0.4-7.el8 (FEDORA-EPEL-2021-c056b5408f)
 GIS file format library

Update Information:

Rebuild

ChangeLog:

* Tue May 18 2021 Sandro Mani  - 3.0.4-7
- Rebuild
* Tue May 18 2021 Sandro Mani 
- Rebuild

References:

  [ 1 ] Bug #1950024 - Rebuild for Centos Stream and RHEL 8.4
https://bugzilla.redhat.com/show_bug.cgi?id=1950024




 highway-0.12.0-1.20210518git376a400.el8 (FEDORA-EPEL-2021-acd6b0882a)
 Efficient and performance-portable SIMD

Update Information:

Initial RPM

ChangeLog:


References:

  [ 1 ] Bug #1906980 - Review Request: highway - Efficient and 
performance-portable SIMD
https://bugzilla.redhat.com/show_bug.cgi?id=1906980




 ipv6calc-3.1.0-52.el8 (FEDORA-EPEL-2021-228dd519e5)
 IPv6 address format change and calculation utility

Update Information:

Final release 3.1.0

ChangeLog:

* Tue May 18 2021 Peter Bieringer  - 3.1.0-52
- Final release 3.1.0




 ne-3.3.1-1.el8 (FEDORA-EPEL-2021-d7232656c7)
 ne, the nice editor

Update Information:

First release

ChangeLog:


References:

  [ 1 ] Bug #1952927 - Review Request: ne - ne, the nice editor
https://bugzilla.redhat.com/show_bug.cgi?id=1952927




 qpid-dispatch-1.16.0-1.el8 (FEDORA-EPEL-2021-3e8d725ea3)
 Dispatch router for Qpid

Update Information:

Rebase to 1.16.0.

ChangeLog:

* Tue May 18 2021 Irina Boverman  - 1.15.0-1
- Rebased to 1.16.0




 rpki-client-7.1-1.el8 (FEDORA-EPEL-2021-f5c94f8b87)
 RPKI validator to support BGP Origin Validation

Update Information:

rpki-client 7.1 ===   * Add keep-alive support to the HTTP client
code for RRDP  * Reference-count and delete unused files synced via RRDP, as far
as possible  * In the JSON output, change the AS Number from a string ("AS123")
to an integer ("123") to make processing of the output easier  * Add an
`expires` column to CSV & JSON output, based on certificate and CRL validity
times. The `expires` value can be used to avoid route selection based on stale
data when generating VRP sets, when faced with loss of communication between
consumer and valdiator, or 

[Bug 1947703] Fix broken call to perl.prov when filenames contain spaces

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
   Fixed In Version|perl-generators-1.13-1.fc35 |perl-generators-1.13-1.fc35
   ||perl-generators-1.13-1.fc33
 Resolution|--- |ERRATA
Last Closed||2021-05-19 01:30:28



--- Comment #5 from Fedora Update System  ---
FEDORA-2021-f07429afc3 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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: How to replace the rpm-build package with my own in a mock container

[Mikhail Gavrilov]

On Mon, 17 May 2021 at 01:30, Mikhail Gavrilov
 wrote:
> Once again tried rebuilt rpm-build and updated the local metadata and it 
> worked.
> I was just confused that even though there is a mention of the
> rpm-build package in the root.log on line 218 [1]
> But nowhere is it written where this package is installed from.
> In any case, I achieved my goal and was able to replace
> /usr/lib/rpm/brp-strip during build.
>
> Thanks to all.
>
> [1] https://pastebin.com/aU20Bdhq
>

I think I understood what was the matter.
To increase the version, I added the letter b to the release version
(the full name turned out to be
rpm-4.16.90-0.git15395.8b.fc35.src.rpm).
Strangely, the host system considered this change significant and
installed my version, but in the mock container this change was
ignored and the usual version of rpm-build was installed.

# dnf info rpm-build
Last metadata expiration check: 0:08:19 ago on Wed 19 May 2021 02:23:04 AM +05.
Installed Packages
Name : rpm-build
Version  : 4.16.90
Release  : 0.git15395.8b.fc35
Architecture : x86_64
Size : 148 k
Source   : rpm-4.16.90-0.git15395.8b.fc35.src.rpm
Repository   : @System
From repo: local-repo
Summary  : Scripts and executable programs used to build packages
URL  : http://www.rpm.org/
License  : GPLv2+
Description  : The rpm-build package contains the scripts and
executable programs
 : that are used to build packages using the RPM Package Manager.

Available Packages
Name : rpm-build
Version  : 4.16.90
Release  : 0.git15395.8b.fc35
Architecture : i686
Size : 66 k
Source   : rpm-4.16.90-0.git15395.8b.fc35.src.rpm
Repository   : local-repo
Summary  : Scripts and executable programs used to build packages
URL  : http://www.rpm.org/
License  : GPLv2+
Description  : The rpm-build package contains the scripts and
executable programs
 : that are used to build packages using the RPM Package Manager.



-- 
Best Regards,
Mike Gavrilov.
___
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: i686 build OOMing

[Jeff Law]

On 5/18/2021 4:44 PM, David Airlie wrote:

https://kojipkgs.fedoraproject.org//work/tasks/3814/68223814/build.log

cd 
/builddir/build/BUILD/Vulkan-ValidationLayers-sdk-1.2.176.1/i686-redhat-linux-gnu/layers
&& /usr/bin/g++ -DAPI_NAME=\"Vulkan\" -DVK_ENABLE_BETA_EXTENSIONS
-DVK_USE_PLATFORM_WAYLAND_KHR -DVK_USE_PLATFORM_WAYLAND_KHX
-DVK_USE_PLATFORM_XCB_KHR -DVK_USE_PLATFORM_XCB_KHX
-DVK_USE_PLATFORM_XLIB_KHR -DVK_USE_PLATFORM_XLIB_KHX
-DVK_USE_PLATFORM_XLIB_XRANDR_EXT -DVkLayer_khronos_validation_EXPORTS
-I/builddir/build/BUILD/Vulkan-ValidationLayers-sdk-1.2.176.1/layers
-I/builddir/build/BUILD/Vulkan-ValidationLayers-sdk-1.2.176.1/layers/generated
-I/usr/include/glslang -I/usr/include/spirv/include
-I/builddir/build/BUILD/Vulkan-ValidationLayers-sdk-1.2.176.1/i686-redhat-linux-gnu
-I/builddir/build/BUILD/Vulkan-ValidationLayers-sdk-1.2.176.1/i686-redhat-linux-gnu/layers
-O2 -flto=auto -ffat-lto-objects -fexceptions -g1
-grecord-gcc-switches -pipe -Wall -Werror=format-security
-Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS
-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1
-fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1
-m32 -march=i686 -mtune=generic -msse2 -mfpmath=sse -mstackrealign
-fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection
-Wpointer-arith -Wno-unused-function -Wno-sign-compare -DNDEBUG -fPIC
-Wall -Wextra -Wno-unused-parameter -Wno-missing-field-initializers
-fno-strict-aliasing -fno-builtin-memcmp -fvisibility=hidden
-Wimplicit-fallthrough=0 -std=gnu++11 -MD -MT
layers/CMakeFiles/VkLayer_khronos_validation.dir/generated/chassis.cpp.o
-MF CMakeFiles/VkLayer_khronos_validation.dir/generated/chassis.cpp.o.d
-o CMakeFiles/VkLayer_khronos_validation.dir/generated/chassis.cpp.o
-c 
/builddir/build/BUILD/Vulkan-ValidationLayers-sdk-1.2.176.1/layers/generated/chassis.cpp
cc1plus: out of memory allocating 65536 bytes after a total of 3310292992 bytes

We already use -g1 to try and reduce memory usage, and I tried not
doing parallel jobs in case it was too much? any suggestions, is this
LTO?


Not likely LTO since this isn't a link phase AFAICT.

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

Re: Orphaned packages looking for new maintainers

[Ian McInerney]

> emacs-auctex  orphan   1 weeks
> ago
>
>  This one is going to break some non-emacs packages as well because the
spec actually provides a "tex-preview" package that is just preview.sty and
is used by several packages to do tex rendering and preview:
$ repoquery --repo=rawhide{,-source} --whatrequires tex-preview
Last metadata expiration check: 0:02:29 ago on Tue 18 May 2021 11:25:34 PM
BST.
R-tikzDevice-0:0.12.3.1-4.fc34.src
R-tikzDevice-0:0.12.3.1-4.fc34.x86_64
dot2tex-0:2.11.3-9.fc34.noarch
emacs-auctex-0:12.1-9.fc33.noarch
gnuplot-latex-0:5.2.8-7.fc34.noarch
ktikz-0:0.13.1-2.fc34.x86_64
latex2html-0:2020.2-3.fc34.noarch
psi4-1:1.3.2-10.fc35.src
python-matplotlib-0:3.4.2-1.fc35.src
python-mplcairo-0:0.4-1.fc35.src
python-networkx-0:2.5.1-2.fc35.src
qtikz-0:0.13.1-2.fc34.x86_64
sdcc-0:4.0.0-5.fc34.src
texlive-collection-latexextra-9:svn54851-38.fc35.noarch
texstudio-0:3.1.1-1.fc35.x86_64

I have no need for the emacs portion of this package and only need the
preview.sty portion for texstudio, so I really don't want to take it on as
a full package. I can see three options for this:
1) Someone adopts the full package and maintains it (it was orphaned for
FTBFS: https://bugzilla.redhat.com/show_bug.cgi?id=1923372)
2) It gets retired and I have to introduce a new package just for the tex
file
3) The texlive-preview subpackage gets renabled in the main texlive
distribution and provides this instead (since CPAN also contains this file
and includes it inside upstream texlive technically, but we just don't
package it there).

My preference is either 1 or 3 happens, since I think it would be bad to
have a standalone package maintained independently for just that tex file.

Does anyone use the emacs plugin this provides (auctex) and would be
willing to take on this package?

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

i686 build OOMing

[David Airlie]

https://kojipkgs.fedoraproject.org//work/tasks/3814/68223814/build.log

cd 
/builddir/build/BUILD/Vulkan-ValidationLayers-sdk-1.2.176.1/i686-redhat-linux-gnu/layers
&& /usr/bin/g++ -DAPI_NAME=\"Vulkan\" -DVK_ENABLE_BETA_EXTENSIONS
-DVK_USE_PLATFORM_WAYLAND_KHR -DVK_USE_PLATFORM_WAYLAND_KHX
-DVK_USE_PLATFORM_XCB_KHR -DVK_USE_PLATFORM_XCB_KHX
-DVK_USE_PLATFORM_XLIB_KHR -DVK_USE_PLATFORM_XLIB_KHX
-DVK_USE_PLATFORM_XLIB_XRANDR_EXT -DVkLayer_khronos_validation_EXPORTS
-I/builddir/build/BUILD/Vulkan-ValidationLayers-sdk-1.2.176.1/layers
-I/builddir/build/BUILD/Vulkan-ValidationLayers-sdk-1.2.176.1/layers/generated
-I/usr/include/glslang -I/usr/include/spirv/include
-I/builddir/build/BUILD/Vulkan-ValidationLayers-sdk-1.2.176.1/i686-redhat-linux-gnu
-I/builddir/build/BUILD/Vulkan-ValidationLayers-sdk-1.2.176.1/i686-redhat-linux-gnu/layers
-O2 -flto=auto -ffat-lto-objects -fexceptions -g1
-grecord-gcc-switches -pipe -Wall -Werror=format-security
-Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS
-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1
-fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1
-m32 -march=i686 -mtune=generic -msse2 -mfpmath=sse -mstackrealign
-fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection
-Wpointer-arith -Wno-unused-function -Wno-sign-compare -DNDEBUG -fPIC
-Wall -Wextra -Wno-unused-parameter -Wno-missing-field-initializers
-fno-strict-aliasing -fno-builtin-memcmp -fvisibility=hidden
-Wimplicit-fallthrough=0 -std=gnu++11 -MD -MT
layers/CMakeFiles/VkLayer_khronos_validation.dir/generated/chassis.cpp.o
-MF CMakeFiles/VkLayer_khronos_validation.dir/generated/chassis.cpp.o.d
-o CMakeFiles/VkLayer_khronos_validation.dir/generated/chassis.cpp.o
-c 
/builddir/build/BUILD/Vulkan-ValidationLayers-sdk-1.2.176.1/layers/generated/chassis.cpp
cc1plus: out of memory allocating 65536 bytes after a total of 3310292992 bytes

We already use -g1 to try and reduce memory usage, and I tried not
doing parallel jobs in case it was too much? any suggestions, is this
LTO?

Dave.
___
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 1961865] perl-Net-CIDR-Lite: Incorrect handling of IP address with leading zeros in IP octets

[bugzilla]

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

Tomas Hoger  changed:

   What|Removed |Added

 Blocks||1961866
 Depends On||1961867




-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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 1961865] New: perl-Net-CIDR-Lite: Incorrect handling of IP address with leading zeros in IP octets

[bugzilla]

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

Bug ID: 1961865
   Summary: perl-Net-CIDR-Lite: Incorrect handling  of IP address
with leading zeros in IP octets
   Product: Security Response
  Hardware: All
OS: Linux
Status: NEW
 Component: vulnerability
  Keywords: Security
  Severity: medium
  Priority: medium
  Assignee: security-response-t...@redhat.com
  Reporter: tho...@redhat.com
CC: p...@city-fan.org, perl-devel@lists.fedoraproject.org,
pzhu...@redhat.com, st...@silug.org
  Target Milestone: ---
Classification: Other



It was discovered that the perl Net-CIDR-Lite module did not correctly handle
IP addresses with IP octets containing leading zeros.  Leading zeros were
ignored, while the underlying system can treat such octets as octal numbers and
interpret them differently.  For example, IP address of 010.0.0.1 was
considered by Net-CIDR-Lite to be the same address as 10.0.0.1, while system
may consider it to be IP address 8.0.0.1.

Reference:

https://blog.urth.org/2021/03/29/security-issues-in-perl-ip-address-distros/#net-cidr-litehttpsmetacpanorgreleasenet-cidr-lite

This issue was fixed in Net-CIDR-Lite version 0.22 via this change:

https://metacpan.org/diff/file?target=STIGTSP/Net-CIDR-Lite-0.22/Lite.pm=DOUGW%2FNet-CIDR-Lite-0.21%2FLite.pm

An example of a potentially vulnerable use case can be found in the
SpamAssassin's URILocalBL plugin:

https://svn.apache.org/viewvc/spamassassin/tags/spamassassin_release_3_4_6/lib/Mail/SpamAssassin/Plugin/URILocalBL.pm?view=markup

It allows checking URLs extracted from emails against locally defined blacklist
of IP ranges.  IP addresses to check are typically obtained by resolving host
names used in URLs.  However, URLs with IP addresses can be used directly. 
Hence, this issue could potentially lead to a bypass of the defined blacklist. 
Note that this plugin does not seem to be affected due to the use of a strict
regular expression used to determine if URL contains host name or IP address. 
That regular expression does not consider addresses with leading zeros as valid
IP addresses and performs their resolution, translating the IP string to how
system interprets it.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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: Orphaned packages looking for new maintainers

[Miro Hrončok]

On 19. 05. 21 0:17, Kaleb Keithley wrote:



On Tue, May 18, 2021 at 4:15 PM Miro Hrončok > wrote:



Full report available at:
https://churchyard.fedorapeople.org/orphans-2021-05-18.txt

grep it for your FAS username and follow the dependency chain.


rubygem-maruku?


Indeed.

If I'm reading your report correctly it's saying that it's pcs which depends on 
rubygem-maruku. (And glusterfs, or more specifically, glusterfs-ganesha depends 
on pcs.)


That is also correct.

I took the dummy's way out (rather than simply trust the report) and installed 
pcs (and a bunch of other things before I realized what the report was saying) 
on both my f34 and f35/rawhide boxes. In both cases rubygem-maruku was _not_ 
installed.


The problematic dependency is a transitive build dependency. Your test only 
verifies runtime dependencies.



Also `rpm -q --requires pcs` did not list rubygem-maruku.


Similarly, this only queries direct runtime dependencies.



From the full linked report:


Depending on: rubygem-maruku (43), status change: 2021-05-06 (1 weeks ago)
rubygem-tilt (maintained by: valtri, vondruch)
rubygem-tilt-2.0.10-4.fc34.src requires rubygem(asciidoctor) = 
2.0.15, rubygem(maruku) = 0.7.2

pcs (maintained by: cfeist, idevat, mlisik, omular, tojeline)
pcs-0.10.8-1.fc34.src requires rubygem-tilt = 2.0.10-4.fc34
pcs-0.10.8-1.fc34.x86_64 requires rubygem-tilt = 2.0.10-4.fc34



So, technically:

 - Once rubygem-maruku is retired, rubygem-tilt fails to build.
 - Iff rubygem-tilt is not fixed, it will be orphaned and retired eventually.
 - Once rubygem-tilt is retired, pcs fails to build and fails to install.
 - When pcs fails to install, so does glusterfs-ganesha.


The script creating this output is run and developed by Fedora
Release Engineering. Please report issues at its pagure instance:
https://pagure.io/releng/ 


Should I file a report? ;-)


If you know how to present the information in a less confusing way, please do 
file a report.


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

[Bug 1961842] New: perl-HTTP-Message-6.32 is available

[bugzilla]

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

Bug ID: 1961842
   Summary: perl-HTTP-Message-6.32 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-HTTP-Message
  Keywords: FutureFeature, Triaged
  Assignee: mspa...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: mspa...@redhat.com,
perl-devel@lists.fedoraproject.org, ppi...@redhat.com
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 6.32
Current version/release in rawhide: 6.31-1.fc35
URL: http://search.cpan.org/dist/HTTP-Message/

Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.


Based on the information from anitya:
https://release-monitoring.org/project/2977/


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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: Orphaned packages looking for new maintainers

[Miro Hrončok]

On 18. 05. 21 22:24, Marek Polacek wrote:

On Tue, May 18, 2021 at 10:14:41PM +0200, Miro Hrončok wrote:

The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life

Note: If you received this mail directly you (co)maintain one of the affected
packages or a package that depends on one. Please adopt the affected package or
retire your depending package to avoid broken dependencies, otherwise your
package will fail to install and/or build when the affected package
gets retired.

Request package ownership via the *Take* button in he left column on
https://src.fedoraproject.org/rpms/

Full report available at:
https://churchyard.fedorapeople.org/orphans-2021-05-18.txt
grep it for your FAS username and follow the dependency chain.

For human readable dependency chains,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan

mpolacek: shrinkwrap, jboss-modules


This looks like a mistake, these are Java packages that I've never
had anything to do with.  But I guess that means I'm fine with them
being unmaintained.


It might like a mistake, but it is not a mistake:

gcc (maintained by: aoliva, jakub, law, mpolacek)
gcc-11.1.1-1.fc35.src requires systemtap-sdt-devel = 4.5-1.fc35

	systemtap (maintained by: amerey, drsmith2, fche, jistone, lberk, mcermak, 
mjw, scox, smakarov, wcohen)

systemtap-runtime-java-4.5-1.fc35.x86_64 requires byteman = 
4.0.11-4.fc34

byteman (maintained by: jerboaa, jhuttana)
		byteman-4.0.11-4.fc34.src requires mvn(org.jboss.modules:jboss-modules) = 
1.5.2.Final


jboss-modules (maintained by: java-maint-sig, mizdebsk, orphan)
		jboss-modules-1.5.2-13.fc34.src requires 
mvn(org.jboss.shrinkwrap:shrinkwrap-impl-base) = 1.2.6


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

opam (was: Re: Orphaned packages looking for new maintainers)

[Richard W.M. Jones]

(I've added a few opam devs to CC)

On Tue, May 18, 2021 at 10:14:41PM +0200, Miro Hrončok wrote:
> opam  orphan   1 weeks ago

I didn't notice that opam had been orphaned.  This package is the tool
used for source packaging of OCaml packages under $HOME
(https://opam.ocaml.org/).

I don't especially like language-specific tools for managing packages,
because of the usual problems that have been widely discussed
elsewhere and it's not profitable to rehash them again.  This is my
personal view.

The question is if we want to keep this in Fedora or not?  ie. As an
official Fedora package versus something that opam maintainers would
provide themselves as a download.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html
___
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 1207174] perl-IO-Socket-INET6-2.72-3.fc23 FTBFS sometimes: Can't use an undefined value as a symbol reference at t/io_multihomed6.t line 116.

[bugzilla]

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

Michal Josef Spacek  changed:

   What|Removed |Added

 CC||mspa...@redhat.com



--- Comment #11 from Michal Josef Spacek  ---
I created patch to fix error message in this case.
https://src.fedoraproject.org/rpms/perl-IO-Socket-INET6/pull-request/1

After patching in testing cycle this bug seems like as:
> listen on ::1 port 54577: Address already in use at t/io_multihomed6.t line 
> 104.
Port isn't closed properly before new run of test.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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

Building for EPEL-8 and CMake (again)

[Ron Olson]

Hey all-

Awhile back I asked about the status of CMake in CentOS so I could build my 
packages for EPEL-8; they require a version of CMake that is greater than 
3.11.4 which is currently available. CentOS Stream has a later version, as does 
RHEL 8.4. I get that CentOS Stream is the future of CentOS, but when I run a 
koji build for EPEL 8 it uses CentOS 8, not CentOS Stream and thus all my 
builds fail.

TL;DR: How can I build anything for EPEL 8 with CMake if the package is too old?


Thanks!

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

Re: Orphaned packages looking for new maintainers

[Miro Hrončok]

On 18. 05. 21 22:04, Miro Hrončok wrote:
*Warning*: Affected package maintainers were not bcc'ed becasue I've recently 
migrated to Gmail and it doesn't let me bcc nearly 500 email addresses. I'll 
try to figure out what to do next.


I've managed to re-send the bcc'ed message via Gmail web interface. 
Unfortunately, it doesn't let me set Reply-To header :/


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

Orphaned packages looking for new maintainers

[Miro Hrončok]

*Warning*: Affected package maintainers were not bcc'ed becasue I've recently 
migrated to Gmail and it doesn't let me bcc nearly 500 email addresses. I'll 
try to figure out what to do next.


The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life

Note: If you received this mail directly you (co)maintain one of the affected
packages or a package that depends on one. Please adopt the affected package or
retire your depending package to avoid broken dependencies, otherwise your
package will fail to install and/or build when the affected package gets 
retired.

Request package ownership via the *Take* button in he left column on
https://src.fedoraproject.org/rpms/

Full report available at:
https://churchyard.fedorapeople.org/orphans-2021-05-18.txt
grep it for your FAS username and follow the dependency chain.

For human readable dependency chains,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan

Package  (co)maintainers   Status Change

Inventor  orphan   1 weeks ago
aespipe   orphan   1 weeks ago
ant-contrib   java-maint-sig, mizdebsk,3 weeks ago
  orphan
aopalliance   java-maint-sig, mizdebsk,3 weeks ago
  orphan
apache-ivyjava-maint-sig, mizdebsk,3 weeks ago
  orphan
arduino   elxreno, orphan, patches,3 weeks ago
  thozza
args4jjava-maint-sig, mizdebsk,3 weeks ago
  orphan
cajun-jsonapi orphan   4 weeks ago
cal10njava-maint-sig, mizdebsk,3 weeks ago
  orphan
cgdcbxd   orphan   3 weeks ago
clang9.0  jistone, orphan, tstellar5 weeks ago
coffee-script nodejs-sig, orphan, patches, 1 weeks ago
  vjancik
dain-snappy   java-maint-sig, mizdebsk,3 weeks ago
  orphan
dayjournalorphan   1 weeks ago
disruptor java-maint-sig, mizdebsk,3 weeks ago
  orphan
dropwatch orphan   3 weeks ago
dssi-vst  orphan   5 weeks ago
emacs-auctex  orphan   1 weeks ago
emacs-haskell-modeorphan   1 weeks ago
emacs-lookup  orphan   1 weeks ago
erlang-eper   filabrazilska, orphan1 weeks ago
fasterxml-oss-parent  java-maint-sig, orphan   3 weeks ago
fbreader  orphan   5 weeks ago
fedora-jam-backgroundsorphan   5 weeks ago
fedora-jam-kde-theme  jvlomax, orphan  5 weeks ago
flannel   eparis, go-sig, gscrivano,   1 weeks ago
  linville, lsm5, orphan, vbatts
fluidsynth-dssi   orphan   5 weeks ago
freight-container orphan   3 weeks ago
freight-tools orphan   3 weeks ago
freqtweak orphan   5 weeks ago
geronimo-osgi-support mizdebsk, orphan 1 weeks ago
gnome-desktop alexl, caolanm, fmuellner,   5 weeks ago
  gnome-sig, orphan, rhughes
gnome-guitar  orphan   5 weeks ago
gocompletego-sig, logic, orphan4 weeks ago
google-gson   java-maint-sig, mizdebsk,3 weeks ago
  orphan
gtk-nodoka-engine orphan   5 weeks ago
hamcrest2 java-maint-sig, orphan   3 weeks ago
hexter-dssi   orphan   5 weeks ago
hsqldbfnasser, mizdebsk, orphan3 

Orphaned packages looking for new maintainers

[Miro Hrončok]

*Warning*: Affected package maintainers were not bcc'ed becasue I've recently 
migrated to Gmail and it doesn't let me bcc nearly 500 email addresses. I'll 
try to figure out what to do next.


The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life

Note: If you received this mail directly you (co)maintain one of the affected
packages or a package that depends on one. Please adopt the affected package or
retire your depending package to avoid broken dependencies, otherwise your
package will fail to install and/or build when the affected package gets 
retired.

Request package ownership via the *Take* button in he left column on
https://src.fedoraproject.org/rpms/

Full report available at:
https://churchyard.fedorapeople.org/orphans-2021-05-18.txt
grep it for your FAS username and follow the dependency chain.

For human readable dependency chains,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan

Package  (co)maintainers   Status Change

Inventor  orphan   1 weeks ago
aespipe   orphan   1 weeks ago
ant-contrib   java-maint-sig, mizdebsk,3 weeks ago
  orphan
aopalliance   java-maint-sig, mizdebsk,3 weeks ago
  orphan
apache-ivyjava-maint-sig, mizdebsk,3 weeks ago
  orphan
arduino   elxreno, orphan, patches,3 weeks ago
  thozza
args4jjava-maint-sig, mizdebsk,3 weeks ago
  orphan
cajun-jsonapi orphan   4 weeks ago
cal10njava-maint-sig, mizdebsk,3 weeks ago
  orphan
cgdcbxd   orphan   3 weeks ago
clang9.0  jistone, orphan, tstellar5 weeks ago
coffee-script nodejs-sig, orphan, patches, 1 weeks ago
  vjancik
dain-snappy   java-maint-sig, mizdebsk,3 weeks ago
  orphan
dayjournalorphan   1 weeks ago
disruptor java-maint-sig, mizdebsk,3 weeks ago
  orphan
dropwatch orphan   3 weeks ago
dssi-vst  orphan   5 weeks ago
emacs-auctex  orphan   1 weeks ago
emacs-haskell-modeorphan   1 weeks ago
emacs-lookup  orphan   1 weeks ago
erlang-eper   filabrazilska, orphan1 weeks ago
fasterxml-oss-parent  java-maint-sig, orphan   3 weeks ago
fbreader  orphan   5 weeks ago
fedora-jam-backgroundsorphan   5 weeks ago
fedora-jam-kde-theme  jvlomax, orphan  5 weeks ago
flannel   eparis, go-sig, gscrivano,   1 weeks ago
  linville, lsm5, orphan, vbatts
fluidsynth-dssi   orphan   5 weeks ago
freight-container orphan   3 weeks ago
freight-tools orphan   3 weeks ago
freqtweak orphan   5 weeks ago
geronimo-osgi-support mizdebsk, orphan 1 weeks ago
gnome-desktop alexl, caolanm, fmuellner,   5 weeks ago
  gnome-sig, orphan, rhughes
gnome-guitar  orphan   5 weeks ago
gocompletego-sig, logic, orphan4 weeks ago
google-gson   java-maint-sig, mizdebsk,3 weeks ago
  orphan
gtk-nodoka-engine orphan   5 weeks ago
hamcrest2 java-maint-sig, orphan   3 weeks ago
hexter-dssi   orphan   5 weeks ago
hsqldbfnasser, mizdebsk, orphan3 

Fedora CoreOS stable stream now rebased to Fedora 34

[Dusty Mabe]

Over the next two days we're rolling out the first Fedora 34 based
Fedora CoreOS into the `stable` stream. 
 
Some notable issues/configurations:

- Very old systems (Fedora 32 and earlier) may not be able to update [0]
- systemd-resolved is still enabled but not used yet [1]

Here are some highlights of recently added features in Fedora CoreOS:

- The `/boot` partition is now mounted read-only.
- This continues the work to protect more of the OS from accidental damage.
- It is now possible to configure boot disk RAID 1 mirroring via Ignition [2].
- Better introspection into the state of Zincati (the update agent) from 
`rpm-ostree status`.
- Better support for disk encryption.
- Initial (non-automatic) support for updating the bootloader. [3]

Here are some new features landing in the coming months:

- Support for specifying kernel arguments via Ignition [4].
- Move to cgroup v2 by default [5].
- DNF Count Me support for Fedora CoreOS [6].

Thanks to everyone who participated in the test day [7] and to everyone that
run the `testing` and `next` streams to help us identify and fix issues
before they get to `stable`.

Dusty Mabe, for the Fedora CoreOS team

[0] 
https://github.com/coreos/fedora-coreos-tracker/issues/749#issuecomment-843446996
[1] https://github.com/coreos/fedora-coreos-tracker/issues/834
[2] 
https://docs.fedoraproject.org/en-US/fedora-coreos/storage/#_reconfiguring_the_root_filesystem
[3] https://docs.fedoraproject.org/en-US/fedora-coreos/bootloader-updates/
[4] https://github.com/coreos/ignition/issues/1168
[5] https://github.com/coreos/fedora-coreos-tracker/issues/292
[6] https://github.com/coreos/fedora-coreos-tracker/issues/717
[7] https://testdays.fedoraproject.org/events/113
___
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: F35 Change: Replace SDL 1.2 with sdl12-compat using SDL 2.0 (Self-Contained Change proposal)

[Jan Drögehoff]

On 5/18/21 9:17 PM, Jan Drögehoff wrote:
It uses the exact same code as SDL 1.2 which has a version for i386 
systems with inline assembly so that might need some eyes looking at it.


Actually scratch that

I had misinterpreted a contributors response to the issue and it has a 
completely fresh implementation


apologies

___
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: F35 Change: Replace SDL 1.2 with sdl12-compat using SDL 2.0 (Self-Contained Change proposal)

[Jan Drögehoff]

On 5/18/21 12:45 PM, Kevin Kofler via devel wrote:


Ben Cotton wrote:

This Change proposes to replace SDL 1.2 with sdl12-compat, which uses SDL
2.0.

FYI, it took me just a few minutes of casually browsing commits to spot a
memory corruption bug in this code:
https://github.com/libsdl-org/sdl12-compat/commit/4c5e3b22593c4b48ac8129ae2096af5c00569dd4#commitcomment-50963635


Opened an issue for it[1] and was correctly shortly after[2]

It uses the exact same code as SDL 1.2 which has a version for i386 
systems with inline assembly so that might need some eyes looking at it.



[1] https://github.com/libsdl-org/sdl12-compat/issues/56

[2] 
https://github.com/libsdl-org/sdl12-compat/commit/dacb4cf935ba3a6faee53c67d8973e2b375a3fe9


___
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

Planned Outage - s390x builders - 2021-06-04 22:00 UTC

[Kevin Fenzi]

Planned Outage - s390x builders - 2021-06-04 22:00 UTC

There will be an outage starting at 2021-06-04 22:00 UTC,
which will last approximately 36 hours.

To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:

date -d '2021-06-04 22:00UTC'

Reason for outage:

The facility hosting the fedora s390x builders has a site wide power outage 
scheduled for June 4th to June 6th. We will be powering off these builders at 
22UTC on 2021-06-04. It's likely that they will be back sometime late in the 
day of 2021-06-05, but it could be they are not back until 2021-06-06. During 
this time any builds that build against s390x will stall in 'free' state until 
the builders are back. No rawhide composes will be done in the outage window.

Affected Services:

koji builds needing to build on s390x will queue up and wait for the builders 
to return.

Ticket Link:

https://pagure.io/fedora-infrastructure/issue/9960

Please join #fedora-admin or #fedora-noc on irc.freenode.net
or add comments to the ticket for this outage above.



signature.asc
Description: PGP signature
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-annou...@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

Planned Outage - s390x builders - 2021-06-04 22:00 UTC

[Kevin Fenzi]

Planned Outage - s390x builders - 2021-06-04 22:00 UTC

There will be an outage starting at 2021-06-04 22:00 UTC,
which will last approximately 36 hours.

To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:

date -d '2021-06-04 22:00UTC'

Reason for outage:

The facility hosting the fedora s390x builders has a site wide power outage 
scheduled for June 4th to June 6th. We will be powering off these builders at 
22UTC on 2021-06-04. It's likely that they will be back sometime late in the 
day of 2021-06-05, but it could be they are not back until 2021-06-06. During 
this time any builds that build against s390x will stall in 'free' state until 
the builders are back. No rawhide composes will be done in the outage window.

Affected Services:

koji builds needing to build on s390x will queue up and wait for the builders 
to return.

Ticket Link:

https://pagure.io/fedora-infrastructure/issue/9960

Please join #fedora-admin or #fedora-noc on irc.freenode.net
or add comments to the ticket for this outage above.



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

aom soname bump

[Robert-André Mauchin]

Hi,

AOM AV1 version 3 has been published a while ago and I am planning to 
update it in Fedora. Due to a CVE affecting versions prior to 2021-04-07 
(CVE-2021-30473), I plan to push this update to ALL STABLE RELEASES:


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

I intend to wait until 3.1.1 which fix a few compilation bugs, and wait 
 for jpeg-xl to be packaged to benefit from the new butteraugli tuning.


Affected packages as follows:

avidemux rpmfusion-free
cinelerra-gg rpmfusion-free
ffmpeg rpmfusion-free
go-avif fedora (should be retired)
gstreamer1-plugins-bad-free fedora
libavif fedora
libheif rpmfusion-free
rust-aom-sys fedora
seamonkey fedora
vlc rpmfusion-free
xine-lib rpmfusion-free


I will rebuild the affected packages using my PP.

Best regards,

Robert-André

p.s.: Leigh, I might need your help not to fuck up the repo in rpmfusion 
like last time (if you explain me your process to keep the branches in 
sync it would be nice).


___
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 1960392] Upgrade perl-File-Which to 1.27

[bugzilla]

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

Tom "spot" Callaway  changed:

   What|Removed |Added

 Status|NEW |CLOSED
 Resolution|--- |RAWHIDE
Last Closed||2021-05-18 14:28:33



--- Comment #1 from Tom "spot" Callaway  ---
1.27 in rawhide.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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

Summary/Minutes from today's FESCo Meeting (2021-05-18)

[Miro Hrončok]

===
#fedora-meeting: FESCO (2021-05-18)
===


Meeting started by mhroncok at 17:00:35 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting/2021-05-18/fesco.2021-05-18-17.00.log.html
.



Meeting summary
---
* init process  (mhroncok, 17:00:40)

* #2609 F35 Change: Perl 5.34  (mhroncok, 17:04:11)
  * AGREED: APPROVED fast-track (+7,0,-0)  (mhroncok, 17:05:57)

* Next week's chair  (mhroncok, 17:06:09)
  * ACTION: mhroncok will chair next meeting  (mhroncok, 17:08:33)

* Open Floor  (mhroncok, 17:08:41)

Meeting ended at 17:11:26 UTC.




Action Items

* mhroncok will chair next meeting




Action Items, by person
---
* mhroncok
  * mhroncok will chair next meeting
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* mhroncok (24)
* zodbot (14)
* Eighth_Doctor (6)
* dcantrell (6)
* zbyszek (5)
* nirik (4)
* decathorpe (3)
* ignatenkobrain (0)
* Conan_Kudo (0)
* sgallagh (0)
* cverna (0)
* Sir_Gallantmon (0)
* King_InuYasha (0)
* Son_Goku (0)
* Pharaoh_Atem (0)
___
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

Disable annobin on 32 bit Arm while an issue is investigated?

[Arjun Shankar]

Hello, devel and arm lists!

We recently ran into a testsuite failure when building glibc for
Rawhide on armv7hl:
https://bugzilla.redhat.com/show_bug.cgi?id=1951492

The test program experienced a hang after a thread was cancelled.

So far, it appears that either annobin generated notes or the way in
which the static linker interprets them lead to incorrect unwind
information in 32 bit Arm binaries.

While in this case only a glibc testsuite failure was caught, there is
a chance that building with annobin can lead to incorrect unwind
information and associated problems for any armv7hl Rawhide package
built this way.

With this in mind, I would like to know how the Fedora-Arm developer
community feels about disabling annobin when building RPMs only on
armv7hl until this issue is investigated and the root cause fixed.
This should be possible with a change to the redhat-rpm-config.

Cheers,
Arjun
___
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 1837988] CVE-2020-10878 perl: corruption of intermediate language state of compiled regular expression due to integer overflow leads to DoS

[bugzilla]

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



--- Comment #29 from errata-xmlrpc  ---
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2021:1678 https://access.redhat.com/errata/RHSA-2021:1678


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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 1837975] CVE-2020-10543 perl: heap-based buffer overflow in regular expression compiler leads to DoS

[bugzilla]

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



--- Comment #27 from errata-xmlrpc  ---
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2021:1678 https://access.redhat.com/errata/RHSA-2021:1678


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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: RPMLint 2.0 released!

[Miroslav Suchý]

Dne 18. 05. 21 v 17:05 Susi Lehtola napsal(a):

On 5/18/21 8:13 AM, Neal Gompa wrote:

On Tue, May 18, 2021 at 8:10 AM Miro Hrončok  wrote:

Awesome! What is the plan for Fedora? Shall we migrate to rpmlint 2 in
rawhide? I recall Mirek Suchý had some WIP Fedora config.


https://github.com/rpm-software-management/rpmlint/tree/main/configs/Fedora

there are still some FIXME, some things which are commented out and we should 
decide whether we want them or not.



Yes, please! The new rpmlint is *way* better than what we have now,
and the rpmlint-1.x branch is basically dead now. Nobody is working on
that codebase anymore.


True. But...


If that's the case, it might not be a bad idea to push the new version
in the stable releases, too, no?


The new rpmlint is different. Better, but different. Going through rawhide only 
is better.

It would be great if somebody provided Copr project for stable release.

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

Re: Bodhi critpath package updates now gated on openQA results

[Adam Williamson]

On Tue, 2021-05-18 at 10:55 -0500, Justin Forbes wrote:
> On Tue, May 18, 2021 at 08:38:29AM -0700, Adam Williamson wrote:
> > On Tue, 2021-05-18 at 08:26 -0500, Michael Catanzaro wrote:
> > > You reported my complaints as: 
> > > https://github.com/fedora-infra/bodhi/issues/4219. Thanks!
> > > 
> > > I'm going to go ahead and ask that the gating be turned off until it's 
> > > fixed. If it doesn't display accurate test results, it's not even close 
> > > to being ready yet. Good gating is good, but bad gating is worse than 
> > > no gating.
> > 
> > I don't really think this is necessary? It's not really 'displaying'
> > anything inaccurate at any point. Just not totally clear. When the
> > tests aren't yet run it shows that some results are missing, which is
> > true. When they are finished it shows the correct status and gates
> > correctly. What is it that you're saying is actually not accurate?
> 
> I don't think it needs to be turned off, but the issue does need to be
> addressed.  The first time I got a failure message, I had to go and
> investigate.  Took a minute to figure out what was going on. Now that I
> know that it is the issue, I am ignoring those messages.  I haven't seen
> a real failure yet on anything I submitted, but I would assume the
> message looks the same, and I likely won't notice until I go into bodhi
> to do something with the update. 
> As for now, I think the gating is probably more valuable than the flawed
> output of the tool. Leave it on, but perhaps add some priority to fixing
> the issue?

I'm already planning to work on it today.
-- 
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

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

[tdawson]

Dear all,

You are kindly invited to the meeting:
   EPEL Steering Committee on 2021-05-19 from 16:00:00 to 17:00:00 US/Eastern
   At fedora-meet...@irc.freenode.net

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

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

[tdawson]

Dear all,

You are kindly invited to the meeting:
   EPEL Steering Committee on 2021-05-19 from 16:00:00 to 17:00:00 US/Eastern
   At fedora-meet...@irc.freenode.net

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://apps.fedoraproject.org/calendar/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

Re: Bodhi critpath package updates now gated on openQA results

[Justin Forbes]

On Tue, May 18, 2021 at 08:38:29AM -0700, Adam Williamson wrote:
> On Tue, 2021-05-18 at 08:26 -0500, Michael Catanzaro wrote:
> > You reported my complaints as: 
> > https://github.com/fedora-infra/bodhi/issues/4219. Thanks!
> > 
> > I'm going to go ahead and ask that the gating be turned off until it's 
> > fixed. If it doesn't display accurate test results, it's not even close 
> > to being ready yet. Good gating is good, but bad gating is worse than 
> > no gating.
> 
> I don't really think this is necessary? It's not really 'displaying'
> anything inaccurate at any point. Just not totally clear. When the
> tests aren't yet run it shows that some results are missing, which is
> true. When they are finished it shows the correct status and gates
> correctly. What is it that you're saying is actually not accurate?

I don't think it needs to be turned off, but the issue does need to be
addressed.  The first time I got a failure message, I had to go and
investigate.  Took a minute to figure out what was going on. Now that I
know that it is the issue, I am ignoring those messages.  I haven't seen
a real failure yet on anything I submitted, but I would assume the
message looks the same, and I likely won't notice until I go into bodhi
to do something with the update. 
As for now, I think the gating is probably more valuable than the flawed
output of the tool. Leave it on, but perhaps add some priority to fixing
the issue?

Justin
___
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: Bodhi critpath package updates now gated on openQA results

[Adam Williamson]

On Tue, 2021-05-18 at 08:26 -0500, Michael Catanzaro wrote:
> You reported my complaints as: 
> https://github.com/fedora-infra/bodhi/issues/4219. Thanks!
> 
> I'm going to go ahead and ask that the gating be turned off until it's 
> fixed. If it doesn't display accurate test results, it's not even close 
> to being ready yet. Good gating is good, but bad gating is worse than 
> no gating.

I don't really think this is necessary? It's not really 'displaying'
anything inaccurate at any point. Just not totally clear. When the
tests aren't yet run it shows that some results are missing, which is
true. When they are finished it shows the correct status and gates
correctly. What is it that you're saying is actually not accurate?
-- 
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

[rpms/perl-IO-Socket-INET6] PR #1: Patch for bad code in test

[Michal Josef Špaček]

mspacek opened a new pull-request against the project: `perl-IO-Socket-INET6` 
that you are following:
``
Patch for bad code in test
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-IO-Socket-INET6/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

Re: RPMLint 2.0 released!

[Susi Lehtola]

On 5/18/21 8:13 AM, Neal Gompa wrote:
> On Tue, May 18, 2021 at 8:10 AM Miro Hrončok  wrote:
>> Awesome! What is the plan for Fedora? Shall we migrate to rpmlint 2 in
>> rawhide? I recall Mirek Suchý had some WIP Fedora config.
>>
> 
> Yes, please! The new rpmlint is *way* better than what we have now,
> and the rpmlint-1.x branch is basically dead now. Nobody is working on
> that codebase anymore.
> 
> Someone please do it, pretty please! 

If that's the case, it might not be a bad idea to push the new version
in the stable releases, too, no?
-- 
Susi Lehtola
Fedora Project Contributor
jussileht...@fedoraproject.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

Schedule for Tuesdays's FESCo Meeting (2021-05-18)

[Miro Hrončok]

Following is the list of topics that will be discussed in the
FESCo meeting Tuesday at 17:00UTC in #fedora-meeting on
irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2021-05-18 17:00 UTC'


Links to all issues to be discussed can be found at:
https://pagure.io/fesco/report/meeting_agenda

= Discussed and Voted in the Ticket =

Clarification on default service start guidelines
https://pagure.io/fesco/issue/2575
"presets for third-party services may be provided by Fedora packages"
APPROVED (+3, 0, -0)

Non responsive maintainer: nando
https://pagure.io/fesco/issue/2601
APPROVED (+1, 0, -0)

F35 Change: Compiler Policy Change
https://pagure.io/fesco/issue/2603
APPROVED (+3, 0, -0)

F35 Change: Node.js 16.x by default
https://pagure.io/fesco/issue/2605
APPROVED (+6, 0, -0)

= New business =

#2609 F35 Change: Perl 5.34
https://pagure.io/fesco/issue/2609

= Open Floor =

For more complete details, please visit each individual
issue.  The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda

If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, e-mail me directly, or bring it
up at the end of the meeting, during the open floor topic. Note
that added topics may be deferred until the following meeting.

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

[EPEL-devel] Re: intent to retire roundcubemail in epel7

[Troy Dawson]

On Tue, May 18, 2021 at 4:20 AM Stephen John Smoogen 
wrote:

>
>
> On Mon, 17 May 2021 at 18:14, Kevin Fenzi  wrote:
>
>> On Mon, May 17, 2021 at 08:56:06PM +0100, Nick Howitt wrote:
>> >
>> >
>> > On 17/05/2021 19:32, Kevin Fenzi wrote:
>> > > roundcubemail in epel7 is very old at this point, and can never be
>> > > upgraded because epel7 has too old a php.
>> > >
>> > > It's got 10 CVEs open against it.
>> > >
>> > > I'm planning on retiring it later today.
>> > >
>> > > I can mail epel-announce about it...
>> > >
>> > > kevin
>> > >
>> > What is the PHP issue? Roundcube 1.4 requires PHP >= 5.4.1 -
>> > https://roundcube.net/about/#features. Current PHP is php-5.4.16-48.
>> There
>> > is also 1.3.16 and the LTS 1.2.13 = https://roundcube.net/download/.
>>
>> Currently epel7 has 1.2.12. We could update to 1.2.13, which fixes 2 of
>> the CVE's... but that leaves 8 more. I don't really think they are going
>> to be doing any more 1.2.x releases now that 1.5 is almost out.
>>
>> Sorry I wasn't being exact there, it's not php itself, it's various php
>> related things. Like php-pear version 1.10.1 is needed and rhel7 has
>> 1.9.4 and so on.
>>
>> If you would like to try and get 1.4.x working on epel7 that would be
>> great! Of course the 1.2 -> 1.4 jump would be pretty major for
>> users, but such things happen.
>>
>>
> I am wondering if we need a different way to announce reasons for this:
>
> [ ] I no longer use RHEL-7 so can not test
> [ ] I found that there are too many package updates needed that I do not
> have time for.
> [ ] The following RHEL packages are too old for this package to be updated
> [ ] The upstream is dead and I can not fix
> ...
>

Or maybe instead of saying it's retiring, do Fedora's Orphaning format.
Announce they are orphaning the package, and if a package is orphaned for a
certain amount of time, and has all the orphan annoucements, it get's
removed.
But I do like your checkbox way for announcing the reasons for
retiring/orphaning.

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

Re: Bodhi critpath package updates now gated on openQA results

[Michael Catanzaro]

You reported my complaints as: 
https://github.com/fedora-infra/bodhi/issues/4219. Thanks!


I'm going to go ahead and ask that the gating be turned off until it's 
fixed. If it doesn't display accurate test results, it's not even close 
to being ready yet. Good gating is good, but bad gating is worse than 
no gating.


___
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

Package review #1961174

[Antonio T. sagitter]

Hi all.

I have a new package in review (rhbz#1961174) that will obsolete 'mld2p4'

Please, take a look if you can; i'll review one in exchange.

Thanks.
--
---
Antonio Trande
Fedora Project
mailto: sagit...@fedoraproject.org
GPG key: 0x29FBC85D7A51CC2F
GPG key server: https://keys.gnupg.net/


OpenPGP_0x29FBC85D7A51CC2F.asc
Description: OpenPGP public key


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 1905190] biber FTBFS in Rawhide (F34): tests fail on different \field{sortinithash} values

[bugzilla]

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



--- Comment #11 from Fedora Update System  ---
FEDORA-2021-d5916963ae has been submitted as an update to Fedora 33.
https://bodhi.fedoraproject.org/updates/FEDORA-2021-d5916963ae


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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 1905190] biber FTBFS in Rawhide (F34): tests fail on different \field{sortinithash} values

[bugzilla]

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



--- Comment #10 from Fedora Update System  ---
FEDORA-2021-c82dc9bfab has been submitted as an update to Fedora 34.
https://bodhi.fedoraproject.org/updates/FEDORA-2021-c82dc9bfab


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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: RPMLint 2.0 released!

[Neal Gompa]

On Tue, May 18, 2021 at 8:10 AM Miro Hrončok  wrote:
>
> On 18. 05. 21 14:00, Neal Gompa wrote:
> > Hey all,
> >
> > Nearly four years and *754 commits* since rpmlint 1.10, we are
> > releasing rpmlint 2.0.0!
> >
> > This new release has a _lot_ of new features, but here are the most notable:
> >
> > * RPMLint now is a "normal" Python application and now supports being
> > imported like a standard Python module! This means that all the normal
> > use-cases for RPMLint are still supported, but now you can make it a
> > part of larger Python-based applications or services.
> > * RPMLint uses a declarative TOML-based syntax for configuring RPMLint
> > policy instead of Python code.
> > * RPMLint now has an override system for the descriptions shown for
> > various checks, so that distributions who want to give specific policy
> > information can do so without patching the code.
> > * RPMLint includes _many more checks_! Nearly all of the generally
> > useful checks created by the openSUSE community have been merged into
> > the tree, so distributions can now benefit from a wider offering of
> > checks to implement policy enforcement.
> > * RPMLint is Python 3 only and now supports Python 3.6 and newer.
> > * RPMLint is now built and installed like a standard Python
> > application using setuptools.
>
> Awesome! What is the plan for Fedora? Shall we migrate to rpmlint 2 in
> rawhide? I recall Mirek Suchý had some WIP Fedora config.
>

Yes, please! The new rpmlint is *way* better than what we have now,
and the rpmlint-1.x branch is basically dead now. Nobody is working on
that codebase anymore.

Someone please do it, pretty please! 

> > I want to specifically thank Tomáš Chvátal, Martin Liska, Kristyna
> > Streitova, Dirk Mueller, Miroslav Suchý, Ondřej Súkup, thisisshub, and
> > Miro Hrončok as top contributors to make this release happen!
>
> I've barely made it :D
>

But you did, and that's what matters! :)




--
真実はいつも一つ！/ 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: RPMLint 2.0 released!

[Miro Hrončok]

On 18. 05. 21 14:00, Neal Gompa wrote:

Hey all,

Nearly four years and *754 commits* since rpmlint 1.10, we are
releasing rpmlint 2.0.0!

This new release has a _lot_ of new features, but here are the most notable:

* RPMLint now is a "normal" Python application and now supports being
imported like a standard Python module! This means that all the normal
use-cases for RPMLint are still supported, but now you can make it a
part of larger Python-based applications or services.
* RPMLint uses a declarative TOML-based syntax for configuring RPMLint
policy instead of Python code.
* RPMLint now has an override system for the descriptions shown for
various checks, so that distributions who want to give specific policy
information can do so without patching the code.
* RPMLint includes _many more checks_! Nearly all of the generally
useful checks created by the openSUSE community have been merged into
the tree, so distributions can now benefit from a wider offering of
checks to implement policy enforcement.
* RPMLint is Python 3 only and now supports Python 3.6 and newer.
* RPMLint is now built and installed like a standard Python
application using setuptools.


Awesome! What is the plan for Fedora? Shall we migrate to rpmlint 2 in 
rawhide? I recall Mirek Suchý had some WIP Fedora config.



I want to specifically thank Tomáš Chvátal, Martin Liska, Kristyna
Streitova, Dirk Mueller, Miroslav Suchý, Ondřej Súkup, thisisshub, and
Miro Hrončok as top contributors to make this release happen!


I've barely made it :D

--
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: RPMLint 2.0 released!

[Neal Gompa]

On Tue, May 18, 2021 at 8:00 AM Neal Gompa  wrote:
>
> Hey all,
>
> Nearly four years and *754 commits* since rpmlint 1.10, we are
> releasing rpmlint 2.0.0!
>

Oh whoops, I forgot to include the release URL:
https://github.com/rpm-software-management/rpmlint/releases/tag/2.0.0



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

RPMLint 2.0 released!

[Neal Gompa]

Hey all,

Nearly four years and *754 commits* since rpmlint 1.10, we are
releasing rpmlint 2.0.0!

This new release has a _lot_ of new features, but here are the most notable:

* RPMLint now is a "normal" Python application and now supports being
imported like a standard Python module! This means that all the normal
use-cases for RPMLint are still supported, but now you can make it a
part of larger Python-based applications or services.
* RPMLint uses a declarative TOML-based syntax for configuring RPMLint
policy instead of Python code.
* RPMLint now has an override system for the descriptions shown for
various checks, so that distributions who want to give specific policy
information can do so without patching the code.
* RPMLint includes _many more checks_! Nearly all of the generally
useful checks created by the openSUSE community have been merged into
the tree, so distributions can now benefit from a wider offering of
checks to implement policy enforcement.
* RPMLint is Python 3 only and now supports Python 3.6 and newer.
* RPMLint is now built and installed like a standard Python
application using setuptools.

I want to specifically thank Tomáš Chvátal, Martin Liska, Kristyna
Streitova, Dirk Mueller, Miroslav Suchý, Ondřej Súkup, thisisshub, and
Miro Hrončok as top contributors to make this release happen!

Full author list with number of commits:

   309  Tomáš Chvátal
   197  Martin Liska
47  Dirk Mueller
26  Kristyna Streitova
24  Neal Gompa (ニール・ゴンパ)
24  marxin
21  Neal Gompa
21  Ondřej Súkup
14  thisisshub
11  Miro Hrončok
 9  Kristýna Streitová
 8  Miroslav Suchý
 6  Markéta Calábková
 5  Ville Skyttä
 4  Ben Greiner
 4  Frank Schreiner
 4  Van de Bugger
 3  David Greaves
 3  Matwey V. Kornilov
 2  Daniel Mach
 2  Matthias Gerstner
 1  Cathy Hu
 1  Ludwig Nussel
 1  MeggyCal
 1  Petr Menšík
 1  Stefan Brüns
 1  Steve Kowalik
 1  Werner Fink
 1  Wolfgang Stöggl
 1  Yanko Kaneti
 1  tpgxyz

--
真実はいつも一つ！/ 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 1905190] biber FTBFS in Rawhide (F34): tests fail on different \field{sortinithash} values

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

  Flags|needinfo?(extras-orphan@fed |
   |oraproject.org) |




-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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 1869114] biber-2.16 is available

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

 Status|ASSIGNED|CLOSED
   Fixed In Version||biber-2.16-1.fc35
 Resolution|--- |RAWHIDE
Last Closed||2021-05-18 11:46:15




-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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: intent to retire roundcubemail in epel7

[Stephen John Smoogen]

On Mon, 17 May 2021 at 18:14, Kevin Fenzi  wrote:

> On Mon, May 17, 2021 at 08:56:06PM +0100, Nick Howitt wrote:
> >
> >
> > On 17/05/2021 19:32, Kevin Fenzi wrote:
> > > roundcubemail in epel7 is very old at this point, and can never be
> > > upgraded because epel7 has too old a php.
> > >
> > > It's got 10 CVEs open against it.
> > >
> > > I'm planning on retiring it later today.
> > >
> > > I can mail epel-announce about it...
> > >
> > > kevin
> > >
> > What is the PHP issue? Roundcube 1.4 requires PHP >= 5.4.1 -
> > https://roundcube.net/about/#features. Current PHP is php-5.4.16-48.
> There
> > is also 1.3.16 and the LTS 1.2.13 = https://roundcube.net/download/.
>
> Currently epel7 has 1.2.12. We could update to 1.2.13, which fixes 2 of
> the CVE's... but that leaves 8 more. I don't really think they are going
> to be doing any more 1.2.x releases now that 1.5 is almost out.
>
> Sorry I wasn't being exact there, it's not php itself, it's various php
> related things. Like php-pear version 1.10.1 is needed and rhel7 has
> 1.9.4 and so on.
>
> If you would like to try and get 1.4.x working on epel7 that would be
> great! Of course the 1.2 -> 1.4 jump would be pretty major for
> users, but such things happen.
>
>
I am wondering if we need a different way to announce reasons for this:

[ ] I no longer use RHEL-7 so can not test
[ ] I found that there are too many package updates needed that I do not
have time for.
[ ] The following RHEL packages are too old for this package to be updated
[ ] The upstream is dead and I can not fix
...


-- 
Stephen J Smoogen.
I've seen things you people wouldn't believe. Flame wars in
sci.astro.orion. I have seen SPAM filters overload because of Godwin's Law.
All those moments will be lost in time... like posts on  BBS... time to
reboot.
___
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 1905190] biber FTBFS in Rawhide (F34): tests fail on different \field{sortinithash} values

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

 Status|NEW |MODIFIED
   Fixed In Version||biber-2.16-1.fc35
   Assignee|extras-orphan@fedoraproject |ppi...@redhat.com
   |.org|




-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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/biber] PR #2: Tests

[Petr Pisar]

ppisar merged a pull-request against the project: `biber` that you are 
following.

Merged pull-request:

``
Tests
``

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

[Bug 1961543] perl-Encode-3.10 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

   Fixed In Version|perl-Encode-3.10-1.fc35 |perl-Encode-3.10-460.fc35




-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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: F35 Change: Replace SDL 1.2 with sdl12-compat using SDL 2.0 (Self-Contained Change proposal)

[Kevin Kofler via devel]

Ben Cotton wrote:
> This Change proposes to replace SDL 1.2 with sdl12-compat, which uses SDL
> 2.0.

FYI, it took me just a few minutes of casually browsing commits to spot a
memory corruption bug in this code:
https://github.com/libsdl-org/sdl12-compat/commit/4c5e3b22593c4b48ac8129ae2096af5c00569dd4#commitcomment-50963635

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

Re: F35 Change: Replace SDL 1.2 with sdl12-compat using SDL 2.0 (Self-Contained Change proposal)

[Kevin Kofler via devel]

Vitaly Zaitsev via devel wrote:

> On 17.05.2021 16:19, Ben Cotton wrote:
>> In order to help move SDL 1.2 games into the modern world, let's
>> replace SDL 1.2 with sdl12-compat, which uses SDL 2.0.
> 
> What about third-party **proprietary** games from Steam for example?

sdl12-compat claims to be binary-compatible with SDL 1.2, so this should in 
principle not be a problem. Subtle behavioral differences or bugs (or even 
fixed bugs) could cause problems though.

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

Fedora-Cloud-32-20210518.0 compose check report

[Fedora compose checker]

No missing expected images.

Soft failed openQA tests: 1/8 (x86_64), 1/8 (aarch64)
(Tests completed, but using a workaround for a known bug)

Old soft failures (same test soft failed in Fedora-Cloud-32-20210517.0):

ID: 889272  Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/889272
ID: 889280  Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/889280

Passed openQA tests: 7/8 (x86_64), 7/8 (aarch64)
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
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/biber] PR #2: Tests

[Petr Pisar]

ppisar opened a new pull-request against the project: `biber` that you are 
following:
``
Tests
``

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

Re: F35 Change: Replace SDL 1.2 with sdl12-compat using SDL 2.0 (Self-Contained Change proposal)

[Jan Drögehoff]

On 5/17/21 9:53 PM, Vitaly Zaitsev via devel wrote:
> On 17.05.2021 20:50, Jan Drögehoff wrote:
>> the Steam runtime ships its own SDL 1.2 so I don't think anything
>> will change on that front
>
> Steam was just an example. There are lots of other proprietary
> applications and games without their own runtime.
>
Well in the case an application depends on the system libraries I would
assume sdl12-compat to be a drop in solution.

Back in 2019[1] Ryan Gordon showed that the original Unreal Tournament
2004 runs fine under the compatibility layer so I would assume the same
for everything that doesn't depend on quirks or bugs.


[1] https://youtu.be/3uVmUCuJpF4

___
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 1961543] perl-Encode-3.10 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|ASSIGNED|CLOSED
   Fixed In Version||perl-Encode-3.10-1.fc35
 Resolution|--- |RAWHIDE
Last Closed||2021-05-18 09:41:21




-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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-Encode] PR #1: 3.10 bump

[Jitka Plesnikova]

jplesnik merged a pull-request against the project: `perl-Encode` that you are 
following.

Merged pull-request:

``
3.10 bump
``

https://src.fedoraproject.org/rpms/perl-Encode/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-Encode] PR #1: 3.10 bump

[Jitka Plesnikova]

jplesnik opened a new pull-request against the project: `perl-Encode` that you 
are following:
``
3.10 bump
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Encode/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

Fedora-Cloud-34-20210518.0 compose check report

[Fedora compose checker]

No missing expected images.

Failed openQA tests: 1/8 (x86_64)

Old failures (same test failed in Fedora-Cloud-34-20210517.0):

ID: 889256  Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/889256

Soft failed openQA tests: 1/8 (aarch64)
(Tests completed, but using a workaround for a known bug)

Old soft failures (same test soft failed in Fedora-Cloud-34-20210517.0):

ID: 889264  Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/889264

Passed openQA tests: 7/8 (x86_64), 7/8 (aarch64)
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
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: F35 Change: More flexible use of SSSD fast cache for local users (System-Wide Change proposal)

[Sumit Bose]

Am Tue, May 18, 2021 at 07:18:50AM + schrieb Zbigniew Jędrzejewski-Szmek:
> On Mon, May 03, 2021 at 10:47:37AM -0400, Ben Cotton wrote:
> > https://fedoraproject.org/wiki/Changes/FlexibleLocalUserCache
> > 
> > == Summary ==
> > Allow to switch SSSD’s fast cache for local users on and off at runtime.
> 
> Could you please also amend the summary to say how the default will change?
> 
> > changes to
> > ''/etc/nsswitch.conf'' required a reboot because long running
> > processes were not aware of the changes because ''/etc/nsswitch.conf''
> > was read only once during the first lookup (it might be sufficient to
> > restart all long running processes but a reboot is typically easier).
> > With ''glibc'' version 2.33, available since Fedora 34,
> > ''/etc/nsswitch.conf'' will be reread automatically for the next
> > lookup if it was modified (timestamp changed).
> 
> That's a very nice feature!
> 
> > The SSSD maintainers will enable the needed changes to the SSSD
> > packages and create pull-requests for the changes to authselect and
> > the modified default /etc/nsswitch.conf file.
> 
> Hmm, could you please explicitly say in the Change page how
> /etc/nsswitch.conf is modified (so people don't have to follow the pull
> requests to figure it out)?

Hi,

thank you for your comments, I've updated the page accordingly.

bye,
Sumit

> 
> Zbyszek
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam 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 1961543] perl-Encode-3.10 is available

[bugzilla]

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

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.
___
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 1961543] New: perl-Encode-3.10 is available

[bugzilla]

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

Bug ID: 1961543
   Summary: perl-Encode-3.10 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Encode
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: jples...@redhat.com, mspa...@redhat.com,
perl-devel@lists.fedoraproject.org, ppi...@redhat.com
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 3.10
Current version/release in rawhide: 3.09-1.fc35
URL: http://search.cpan.org/dist/Encode/

Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.


Based on the information from anitya:
https://release-monitoring.org/project/2849/


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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

Fedora-Cloud-33-20210518.0 compose check report

[Fedora compose checker]

No missing expected images.

Soft failed openQA tests: 1/8 (x86_64), 1/8 (aarch64)
(Tests completed, but using a workaround for a known bug)

Old soft failures (same test soft failed in Fedora-Cloud-33-20210517.0):

ID: 889128  Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/889128
ID: 889136  Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/889136

Passed openQA tests: 7/8 (x86_64), 7/8 (aarch64)
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
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: intent to retire roundcubemail in epel7

[Nick Howitt]

On 17/05/2021 23:14, Kevin Fenzi wrote:

On Mon, May 17, 2021 at 08:56:06PM +0100, Nick Howitt wrote:



On 17/05/2021 19:32, Kevin Fenzi wrote:

roundcubemail in epel7 is very old at this point, and can never be
upgraded because epel7 has too old a php.

It's got 10 CVEs open against it.

I'm planning on retiring it later today.

I can mail epel-announce about it...

kevin


What is the PHP issue? Roundcube 1.4 requires PHP >= 5.4.1 -
https://roundcube.net/about/#features. Current PHP is php-5.4.16-48. There
is also 1.3.16 and the LTS 1.2.13 = https://roundcube.net/download/.


Currently epel7 has 1.2.12. We could update to 1.2.13, which fixes 2 of
the CVE's... but that leaves 8 more. I don't really think they are going
to be doing any more 1.2.x releases now that 1.5 is almost out.

Sorry I wasn't being exact there, it's not php itself, it's various php
related things. Like php-pear version 1.10.1 is needed and rhel7 has
1.9.4 and so on.

If you would like to try and get 1.4.x working on epel7 that would be
great! Of course the 1.2 -> 1.4 jump would be pretty major for
users, but such things happen.

kevin


Let me first say I run ClearOS7 which is a Centos7 clone and we 
generally use EPEL - it is enabled by default. However, in this case, we 
do not use the EPEL version of Roundcube - I think ours is set up 
slightly differently with Sieve and the Global Address Book. However it 
is not regularly maintained so is often out of date. Our version history is:

1.0.5
1.1.3
1.2.3
1.3.9

I don't know the EPEL packaging but in ClearOS, going from 1.2 -> 1.3 
had a few changes to the spec file - capitalisation on the Global 
Address Book file name and, in the %files section, a load of changes 
specifying individual files instead of whole directories under plugins. 
(I am not sure why that was done), but, for the users, the upgrade 
process was seamless each time.


Nick
___
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: F35 Change: More flexible use of SSSD fast cache for local users (System-Wide Change proposal)

[Zbigniew Jędrzejewski-Szmek]

On Mon, May 03, 2021 at 10:47:37AM -0400, Ben Cotton wrote:
> https://fedoraproject.org/wiki/Changes/FlexibleLocalUserCache
> 
> == Summary ==
> Allow to switch SSSD’s fast cache for local users on and off at runtime.

Could you please also amend the summary to say how the default will change?

> changes to
> ''/etc/nsswitch.conf'' required a reboot because long running
> processes were not aware of the changes because ''/etc/nsswitch.conf''
> was read only once during the first lookup (it might be sufficient to
> restart all long running processes but a reboot is typically easier).
> With ''glibc'' version 2.33, available since Fedora 34,
> ''/etc/nsswitch.conf'' will be reread automatically for the next
> lookup if it was modified (timestamp changed).

That's a very nice feature!

> The SSSD maintainers will enable the needed changes to the SSSD
> packages and create pull-requests for the changes to authselect and
> the modified default /etc/nsswitch.conf file.

Hmm, could you please explicitly say in the Change page how
/etc/nsswitch.conf is modified (so people don't have to follow the pull
requests to figure it out)?

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

[Bug 1869114] biber-2.16 is available

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
 CC||ppi...@redhat.com
   Assignee|extras-orphan@fedoraproject |ppi...@redhat.com
   |.org|
   Doc Type|--- |If docs needed, set a value



--- Comment #7 from Petr Pisar  ---
2.15 breaks compatibility (datasource globbing is turned off by default now).
Suitable for Rawhide only.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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