Sinking Fund meaning

https://aliceblueonline.com/what-is-a-sinking-fund/ -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct:

[EPEL-devel] Fedora EPEL 7 updates-testing report

The following Fedora EPEL 7 Security updates need testing: Age URL 5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-eca2daf875 chromium-119.0.6045.123-1.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing squidclamav-7.3-1.el7 Details about builds:

[EPEL-devel] Fedora EPEL 8 updates-testing report

The following Fedora EPEL 8 Security updates need testing: Age URL 5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-6b5f919719 tor-0.4.8.9-1.el8 5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-f535d91d21 chromium-119.0.6045.123-1.el8 2

Re: Rust bindings for Python (pyo3 versions <0.19, cpython) broken with Python 3.12

On Mon, Nov 13, 2023 at 07:25:10PM +0100, Fabio Valentini wrote: > > Yup, I've mentioned that in the bug I filed for python-bcrypt - > It might be as simple as bumping the dependency on pyo3 from v0.15 to v0.19. I've made an attempt here:

[EPEL-devel] qbittorrent in EPEL9

Hello, as per the EPEL package request documentation, I am kindly asking if there are any packagers who would like to package and maintain qbittorrent on EPEL. The request has been stalled since February 2023. https://bugzilla.redhat.com/show_bug.cgi?id=2172281

Re: Groff: Revert the mapping of special characters for UTF-8 devices introduced in 1.23.0 version

On Thu, 2023-11-16 at 23:41 +0100, Lukas Javorsky wrote: > > > > I think an upstream only wants to adhere to the language specification > > (groff_char(7)). These small differences became prominent with the advent > > of > > UTF-8 capable terminals. They have always been visible in a PostScript >

Re: Groff: Revert the mapping of special characters for UTF-8 devices introduced in 1.23.0 version

> > I think an upstream only wants to adhere to the language specification > (groff_char(7)). These small differences became prominent with the advent > of > UTF-8 capable terminals. They have always been visible in a PostScript > output. > > Imagine you are the upstream and a user sends you a bug

Planned Outage - pagure.io network switch updates - 2023-11-17 13:00 UTC

Planned Outage - pagure.io network switch updates - 2023-11-17 13:00 UTC There will be an outage starting at 2023-11-17 13:00UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d

Planned Outage - pagure.io network switch updates - 2023-11-17 13:00 UTC

Planned Outage - pagure.io network switch updates - 2023-11-17 13:00 UTC There will be an outage starting at 2023-11-17 13:00UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d

Re: Can we assume all chroots follow UsrMove?

On Thu, Nov 16, 2023 at 10:37 AM John Reiser wrote: > > > Is it safe to assume that this symbolic link [/lib64 -> usr/lib64] > > exists in all chroots? > > This includes the initial ramdisk, recovery environments, and chroots > > for confining services. > > It is unsafe unless prominently

Summary/Minutes from today's FESCo Meeting (2023-11-16)

#info This meeting is cancelled because of lack of quorum. #info Next meeting will be in two weeks (because of Thanksgiving in U.S.) #action zbyszek will chair the next meeting Minutes: https://meetbot.fedoraproject.org/fedora-meeting-2/2023-11-16/fesco.2023-11-16-17.00.html Minutes (text):

Re: F40 Change Proposal: Linker Error on Security Issues (System-Wide)

On Thursday, 16 November 2023 at 09:43, Nick Clifton wrote: > Hi Dominik, > > > Does the `--no-warn-rwx-segments` disable erroring out on both loadable > > rwx segments and tls rwx segments? > > Yes. > > At the time I wrote the feature I did consider having separate options > for the two tests,

[rpms/perl-File-Temp] PR #1: Package tests

jplesnik merged a pull-request against the project: `perl-File-Temp` that you are following. Merged pull-request: `` Package tests `` https://src.fedoraproject.org/rpms/perl-File-Temp/pull-request/1 -- ___ perl-devel mailing list --

Re: Can we assume all chroots follow UsrMove?

Is it safe to assume that this symbolic link [/lib64 -> usr/lib64] exists in all chroots? This includes the initial ramdisk, recovery environments, and chroots for confining services. It is unsafe unless prominently documented in the places that are likely to be seen by affected developers, now

[rpms/perl-File-Temp] PR #1: Package tests

jplesnik opened a new pull-request against the project: `perl-File-Temp` that you are following: `` Package tests `` To reply, visit the link below https://src.fedoraproject.org/rpms/perl-File-Temp/pull-request/1 -- ___ perl-devel mailing list --

[rpms/perl-File-Path] PR #1: Package tests

jplesnik merged a pull-request against the project: `perl-File-Path` that you are following. Merged pull-request: `` Package tests `` https://src.fedoraproject.org/rpms/perl-File-Path/pull-request/1 -- ___ perl-devel mailing list --

[rpms/perl-File-Path] PR #1: Package tests

jplesnik opened a new pull-request against the project: `perl-File-Path` that you are following: `` Package tests `` To reply, visit the link below https://src.fedoraproject.org/rpms/perl-File-Path/pull-request/1 -- ___ perl-devel mailing list --

Re: Summary/Minutes from today's FESCo Meeting (2023-11-09)

On Thu, 16 Nov 2023 at 07:46, Kevin Kofler via devel < devel@lists.fedoraproject.org> wrote: > Zbigniew Jędrzejewski-Szmek wrote: > > This is called "shooting the messenger". > > It is not. See my reply to Fabio. > > > LSB requires various obsolete interfaces, in particular it requires > > Python

Re: Schedule for Thursday's FESCo Meeting (2023-11-16)

On Thu, Nov 16, 2023 at 7:43 AM Major Hayden wrote: > > On Thu, Nov 16, 2023, at 05:59, Zbigniew Jędrzejewski-Szmek wrote: > > Following is the list of topics that will be discussed in the > > FESCo meeting Thursday at 17:00UTC in #fedora-meeting-2 on > > irc.libera.chat. > > I won't be able to

Re: Summary/Minutes from today's FESCo Meeting (2023-11-09)

On 16. 11. 23 13:45, Kevin Kofler via devel wrote: It would be very much possible to support the Python 2 parts of the spec, without even shipping unmaintained software: Package Tauthon 2.8.4, and make both /usr/bin/python and /usr/bin/python2 symlinks to /usr/bin/tauthon. That should have been

Re: HEADS UP: gdal-3.8.0 coming to rawhide

This is now done, there are two unrelated failures: - gazebo: graphviz 9.x incompatibility - vfrnav: broken build dependencies (nothing provides libsundials_sunlinsolklu.so.4.6.1()(64bit) needed by octave-6:8.4.0-1.fc40.x86_64 from build) Sandro On 15.11.23 11:42, Sandro Mani wrote: Hi

Re: Summary/Minutes from today's FESCo Meeting (2023-11-09)

On Thu, Nov 16, 2023 at 01:39:14PM +0100, Kevin Kofler via devel wrote: > Fabio Valentini wrote: > > There's a difference between *claiming* LSB compliance (what you refer > > to as backwards compatibility ?) and actually *achieving* it. > > Claiming it (the thing we objected to) without achieving

Re: Can we assume all chroots follow UsrMove?

On Thu, Nov 16, 2023 at 7:42 AM Florian Weimer wrote: > > A while back, we made /lib64 a symbolic link to /usr/lib64: > > > > Is it safe to assume that this symbolic link exists in all chroots? > This includes the initial ramdisk, recovery

Re: Summary/Minutes from today's FESCo Meeting (2023-11-09)

Zbigniew Jędrzejewski-Szmek wrote: > This is called "shooting the messenger". It is not. See my reply to Fabio. > LSB requires various obsolete interfaces, in particular it requires > Python 2 to be available as /usr/bin/python. Comment [1] contains a > nice listing. We are not going to bring

Re: Schedule for Thursday's FESCo Meeting (2023-11-16)

On Thu, Nov 16, 2023, at 05:59, Zbigniew Jędrzejewski-Szmek wrote: > Following is the list of topics that will be discussed in the > FESCo meeting Thursday at 17:00UTC in #fedora-meeting-2 on > irc.libera.chat. I won't be able to attend today's meeting as I have two other meetings in the same

Can we assume all chroots follow UsrMove?

A while back, we made /lib64 a symbolic link to /usr/lib64: Is it safe to assume that this symbolic link exists in all chroots? This includes the initial ramdisk, recovery environments, and chroots for confining services. If we can assume

Re: Summary/Minutes from today's FESCo Meeting (2023-11-09)

Fabio Valentini wrote: > There's a difference between *claiming* LSB compliance (what you refer > to as backwards compatibility ?) and actually *achieving* it. > Claiming it (the thing we objected to) without achieving it (i.e. the > status quo for many Fedora releases) is a lie that helps nobody.

Fedora rawhide compose report: 20231116.n.0 changes

OLD: Fedora-Rawhide-20231115.n.0 NEW: Fedora-Rawhide-20231116.n.0 = SUMMARY = Added images:1 Dropped images: 3 Added packages: 5 Dropped packages:2 Upgraded packages: 87 Downgraded packages: 0 Size of added packages: 7.11 MiB Size of dropped packages

[Fedocal] Reminder meeting : ELN SIG

Dear all, You are kindly invited to the meeting: ELN SIG on 2023-11-17 from 12:00:00 to 13:00:00 US/Eastern At fedora-meet...@irc.libera.chat The meeting will be about: Source: https://calendar.fedoraproject.org//meeting/10568/ ___ devel

Schedule for Thursday's FESCo Meeting (2023-11-16)

Following is the list of topics that will be discussed in the FESCo meeting Thursday at 17:00UTC in #fedora-meeting-2 on irc.libera.chat. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/UTCHowto or run: date -d '2023-11-16 17:00 UTC' Links to all issues to be

Re: Summary/Minutes from today's FESCo Meeting (2023-11-09)

On Thu, Nov 16, 2023 at 01:28:31AM +0100, Kevin Kofler via devel wrote: > Neal Gompa wrote: > > * AGREED: Fedora explicitly declines to support the LSB 5.0 or > > earlier. Packagers will remove any information that implies > > otherwise. No implementation of an LSB package may expressly state > >

Re: Summary/Minutes from today's FESCo Meeting (2023-11-09)

On Thu, Nov 16, 2023 at 1:30 AM Kevin Kofler via devel wrote: > > Neal Gompa wrote: > > * AGREED: Fedora explicitly declines to support the LSB 5.0 or > > earlier. Packagers will remove any information that implies > > otherwise. No implementation of an LSB package may expressly state > > or

Re: SPDX Statistics - Kristallnacht edition

Am Do., 16. Nov. 2023 um 01:27 Uhr schrieb Kevin Kofler via devel < devel@lists.fedoraproject.org>: > Miroslav Suchý wrote: > > Why Kristallnachte edition? On today's date at 1938, was i Kristallnacht > > (Night of Broken Glass) - a pogrom against Jews in Germany. It was first > > step where

[Bug 2249978] perl-Math-NumSeq-75-5.fc40 FTBFS: t/SqrtDigits.t tests fail perl-Math-BigInt-1:2.0010.00-1.fc40

https://bugzilla.redhat.com/show_bug.cgi?id=2249978 Petr Pisar changed: What|Removed |Added Link ID||CPAN 150469 -- You are receiving this

Re: F40 Change Proposal: Linker Error on Security Issues (System-Wide)

Hi Dominik, > Does the `--no-warn-rwx-segments` disable erroring out on both loadable > rwx segments and tls rwx segments? Yes. At the time I wrote the feature I did consider having separate options for the two tests, but it seemed like overkill, so I decided to go with just a single

[Bug 2249978] perl-Math-NumSeq-75-5.fc40 FTBFS: t/SqrtDigits.t tests fail perl-Math-BigInt-1:2.0010.00-1.fc40

https://bugzilla.redhat.com/show_bug.cgi?id=2249978 Petr Pisar changed: What|Removed |Added Summary|perl-Math-NumSeq-75-5.fc40 |perl-Math-NumSeq-75-5.fc40

[Bug 2249978] perl-Math-NumSeq-75-5.fc40 FTBFS: tests fail

https://bugzilla.redhat.com/show_bug.cgi?id=2249978 Petr Pisar changed: What|Removed |Added Status|NEW |ASSIGNED --- Comment #1 from Petr Pisar

[Bug 2249978] New: perl-Math-NumSeq-75-5.fc40 FTBFS: tests fail

https://bugzilla.redhat.com/show_bug.cgi?id=2249978 Bug ID: 2249978 Summary: perl-Math-NumSeq-75-5.fc40 FTBFS: tests fail Product: Fedora Version: rawhide Status: NEW Component: perl-Math-NumSeq Assignee: