[Bug 2236101] perl-HTML-FormatText-WithLinks for EL8 and EL9

[bugzilla]

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



--- Comment #5 from Fedora Update System  ---
FEDORA-EPEL-2023-31bf677b99 has been pushed to the Fedora EPEL 9 testing
repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-31bf677b99

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


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202236101%23c5
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2236101] perl-HTML-FormatText-WithLinks for EL8 and EL9

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #4 from Fedora Update System  ---
FEDORA-EPEL-2023-6e0bf72d9d has been pushed to the Fedora EPEL 8 testing
repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-6e0bf72d9d

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


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202236101%23c4
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2232889] perl-ORLite-2.00 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-ORLite-2.00-1.fc39 |perl-ORLite-2.00-1.fc39
   |perl-ORLite-2.00-1.fc37 |perl-ORLite-2.00-1.fc37
   ||perl-ORLite-2.00-1.fc38



--- Comment #7 from Fedora Update System  ---
FEDORA-2023-4887bcf496 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202232889%23c7
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2231692] perl-Test-Harness-3.47 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-Test-Harness-3.47-1.fc |perl-Test-Harness-3.47-1.fc
   |40  |40
   ||perl-Test-Harness-3.47-1.fc
   ||38



--- Comment #7 from Fedora Update System  ---
FEDORA-2023-8e73ab98ad has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202231692%23c7
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2233000] perl-Module-CoreList-5.20230820 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-Module-CoreList-5.2023 |perl-Module-CoreList-5.2023
   |0820-1.fc40 |0820-1.fc40
   |perl-Module-CoreList-5.2023 |perl-Module-CoreList-5.2023
   |0820-1.fc38 |0820-1.fc38
   ||perl-Module-CoreList-5.2023
   ||0820-1.fc37



--- Comment #10 from Fedora Update System  ---
FEDORA-2023-c53b6dfe97 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202233000%23c10
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2232889] perl-ORLite-2.00 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Resolution|--- |ERRATA
 Status|ON_QA   |CLOSED
   Fixed In Version|perl-ORLite-2.00-1.fc39 |perl-ORLite-2.00-1.fc39
   ||perl-ORLite-2.00-1.fc37
Last Closed||2023-09-01 01:28:38



--- Comment #6 from Fedora Update System  ---
FEDORA-2023-55ab0f1cd3 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202232889%23c6
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Adding Passim as a Fedora 40 feature?

[Marcus Müller]

Just realized:

- using avahi for local peer discovery, how does this compare to good ole bittorrent with 
Protocol/Message Stream Encryption turned on, and DHT instead of a tracker?


- I guess the "self-signed certificate" discussion stems from the fact that TLS assumes 
you have certificates – which really isn't the case in these peer-to-peer scenarios. All 
you need is a *session key*, which, painting with a broom-sized brush here, can easily be 
agreed on using e.g. Diffie-Hellman/25519 (as implemented in NaCl/libsodium).


Cheers,
Marcus

On 28.08.23 21:55, Richard Hughes wrote:

On Mon, 28 Aug 2023 at 16:27, Leon Fauster via devel
 wrote:

whats the benefit of this "self-signed TLS certificate" (as it does
not provide any "security")? Is this stub for something later ... ?

It's a good question. It provides encryption (so client A can provide
the file to client B without client C being aware what's being sent)
-- and also placates various corporate security teams that say that
HTTP without TLS isn't good enough -- even if it's got two other
layers of protection.

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

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

Re: Adding Passim as a Fedora 40 feature?

[Richard Hughes]

On Thu, 31 Aug 2023 at 22:05, Björn Persson  wrote:
> The document doesn't say what design decisions were made based on the
> assumption of a friendly network.

Well, I can certainly add them -- this discussion was started so I can
add any missing information.

> All of those design decisions need to
> be reconsidered with the assumption that there are attackers on the LAN
> who will abuse Passim any way they can, and that Passim must deal
> reasonably with any and all attacks.

The fallback for being provided with data that doesn't match the
SHA256 checksum is to download the file from the CDN.

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

Re: Adding Passim as a Fedora 40 feature?

[Björn Persson]

Richard Hughes wrote:
> I was thinking of adding Passim as a default-installed and
> default-enabled dep of fwupd in the Fedora 40 release. Before I create
> lots of unnecessary drama, is there any early feedback on what's
> described in https://github.com/hughsie/passim/blob/main/README.md
> please.

I finally read the README, and, oh geez, this thing is even documented
as assuming a friendly network! And it's being proposed to be enabled
by default, which means it will run on laptops that move around between
cafés, hotels, airports and all the hostile environments anyone can
imagine.

The document doesn't say what design decisions were made based on the
assumption of a friendly network. All of those design decisions need to
be reconsidered with the assumption that there are attackers on the LAN
who will abuse Passim any way they can, and that Passim must deal
reasonably with any and all attacks.

Björn Persson


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

Re: Manual step in upgrade process for a FSWC

[Fabio Valentini]

On Thu, Aug 31, 2023 at 11:24 AM Iker Pedrosa  wrote:
>
> Hi,
>
> On Wed, Aug 30, 2023 at 8:46 PM Kevin Fenzi  wrote:
>>
>> On Wed, Aug 30, 2023 at 11:59:18AM +0200, Iker Pedrosa wrote:
>> > Hi,
>> >
>> > I intend to switch pam_userdb's database provider from BerkeleyDB to GDBM
>> > and I'm writing a Fedora System-Wide Change
>> >  for Fedora 40.
>> > The upgrade process would involve a manual procedure where the user needs
>> > to run a conversion tool for the database. Is this acceptable?
>> >
>> > An automation process could be created, but the location of the database is
>> > configurable, which increases its complexity and effort. Especially for a
>> > PAM module that is not widely used. Another option I can think of is to
>> > automate the conversion process for the default location, and leave the
>> > manual conversion for those using a tuned location. Would that be
>> > acceptable?
>>
>> Will the new version emit some kind of error telling users what needs to
>> happen?
>
>
> It'll log an error but it will be generic, like "user_lookup: could not open 
> database `PATH': %m"
>
>>
>>
>> Will that 'fail closed'? ie, no access granted until the db is
>> converted?
>
>
> I don't understand this question.
>
>>
>>
>> I don't suppose it would be possible to just run the convert at runtime?
>> ie, if old db is found at the configured location convert it to the new
>> version?
>
>
> There are several packages relying in BerkeleyDB and the database team is 
> working in a tool to convert them. So I'd like to avoid replicating the code 
> for each and every package, and instead rely on their tool.

When RPM switched from BerkeleyDB to sqlite, the migration happened
upon first boot after upgrade to the new release, and I thought that
was a nice solution for a tricky problem. Maybe you could you do
something similar?

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

Monitizing Desktop/Workstation Linux

[Ryan Bach via devel]

It would be nice if there was that but not just flatpak but rpm, etc as well.

Any thoughts on this topic? Thanks for all the work, hopefully I can pay for it 
so we can have nice things. Free as in freedom(libre) not free as in (free) 
beer.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: firefox builds seem stuck on the farm - pls check

[Kevin Fenzi]

On Thu, Aug 31, 2023 at 09:56:53AM +0200, Marius Schwarz wrote:
> Hi all,
> 
> Am 30.08.23 um 20:54 schrieb Kevin Fenzi:
> > 
> > Perhaps some folks could try building on an x86_64 vm and see if it
> > happens outside of koji?
> > 
> 
> The updates are not in the testing repo. They are now "just build". The
> usual workflow seems to be interrupted somehow.

It seems all working to me.. 

https://bodhi.fedoraproject.org/updates/?search=firefox

The updates are submitted by the maintainer, which he did around
05:30UTC. They are now waiting for the next push to updates-testing
(which happens at 00:14 UTC).

Please do test and provide karma in the updates.

If there's a need to do a out of band push, the maintainer can ask
releng to do so.

kevin


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

Re: Inactive packager policy for the F39 cycle

[Kevin Fenzi]

On Thu, Aug 31, 2023 at 06:45:25AM +, Mattia Verga via devel wrote:
> Il 30/08/23 22:02, Ben Cotton ha scritto:
> > On Wed, Aug 30, 2023 at 2:47 PM Kevin Fenzi  wrote:
> >> Might you be willing to also do the provenpackager one?
> >> ( https://docs.fedoraproject.org/en-US/fesco/Provenpackager_policy/ )
> >>
> > For Mattia (or anyone else who wants to pick this up), you can see my
> > SOP at 
> > https://docs.fedoraproject.org/en-US/program_management/pgm_guide/sop/inactive-provenpackagers/
> >
> Thank you, I'll read the steps above and send the notification ASAP. 
> (not sure I can post to devel-announce, though)

Anyone who is subscribed can submit posts, but 100% of posts are
moderated, so it will hit moderation. :) 

kevin


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

Re: Manual step in upgrade process for a FSWC

[Steve Grubb]

On Wednesday, August 30, 2023 5:59:18 AM EDT Iker Pedrosa wrote:
> Hi,
> 
> I intend to switch pam_userdb's database provider from BerkeleyDB to GDBM
> and I'm writing a Fedora System-Wide Change
>  for Fedora 40.
> The upgrade process would involve a manual procedure where the user needs
> to run a conversion tool for the database. Is this acceptable?

In the past, we had new requirements for bad password lockouts that did not 
fit into pam_tally neatly. So, we created pam_tally2 to let people migrate to 
the version that met requirements back in the day. Then the requirements 
changed again, so we created pam_faillock. This was all to allow people to 
migrate to the new requirements, which had radically different file formats. 
We didn't see a reliable way to move people and just left it to the admin.

Not that you have to do it this way. But I thought I'd mention how we 
navigated changes in the past. The main thing is we didn't want people 
getting locked out by an incompatible change in the pam stack. (Especially 
for remote logins.)

-Steve

> An automation process could be created, but the location of the database is
> configurable, which increases its complexity and effort. Especially for a
> PAM module that is not widely used. Another option I can think of is to
> automate the conversion process for the default location, and leave the
> manual conversion for those using a tuned location. Would that be
> acceptable?



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

Re: Non-schedule for Thursday's FESCo meeting (2023-08-31)

[David Cantrell]

On 8/31/23 11:19, Neal Gompa wrote:

There is nothing new with the "meeting" tag and no progress on the
existing one on incomplete changes. I'll chair the next meeting next
week.

There's also nothing to announce either.



Thanks, Neal.

--
David Cantrell 
Red Hat, Inc. | Boston, MA | EST5EDT
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Non-schedule for Thursday's FESCo meeting (2023-08-31)

[Neal Gompa]

There is nothing new with the "meeting" tag and no progress on the
existing one on incomplete changes. I'll chair the next meeting next
week.

There's also nothing to announce either.

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

Inactive provenpackagers policy for the f39 cycle

[Mattia Verga via devel]

This is a bit late on schedule, but...

In accordance with FESCo policy[1], the following provenpackagers will
be submitted for removal in two weeks based on a lack of Koji builds
submitted in the last six months. If you received this directly, you
can reply off-list to indicate you should still be in the
provenpackager group.

Note that removal from this group is not a "punishment" or a lack of
appreciation for the work you have done. The intent of the process is
to ensure contributors with distro-wide package privileges are still
active and responsive. This process is done regularly at the branch
point in each release.

[1] 
https://docs.fedoraproject.org/en-US/fesco/Provenpackager_policy/#_maintaining_provenpackager_status



Checked 132 provenpackagers
The following 10 provenpackagers have not submitted a Koji build since 
at least 2023-02-23 00:00:00:
puiterwijk
ajax
rdieter
ausil
pjones
hguemar
jwilson
law
wtogami
steve



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

Inactive provenpackagers policy for the f39 cycle

[Mattia Verga]

This is a bit late on schedule, but...

In accordance with FESCo policy[1], the following provenpackagers will
be submitted for removal in two weeks based on a lack of Koji builds
submitted in the last six months. If you received this directly, you
can reply off-list to indicate you should still be in the
provenpackager group.

Note that removal from this group is not a "punishment" or a lack of
appreciation for the work you have done. The intent of the process is
to ensure contributors with distro-wide package privileges are still
active and responsive. This process is done regularly at the branch
point in each release.

[1] 
https://docs.fedoraproject.org/en-US/fesco/Provenpackager_policy/#_maintaining_provenpackager_status



Checked 132 provenpackagers
The following 10 provenpackagers have not submitted a Koji build since 
at least 2023-02-23 00:00:00:
puiterwijk
ajax
rdieter
ausil
pjones
hguemar
jwilson
law
wtogami
steve



___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Fedora 39 compose report: 20230831.n.0 changes

[Fedora Branched Report]

OLD: Fedora-39-20230830.n.0
NEW: Fedora-39-20230831.n.0

= SUMMARY =
Added images:9
Dropped images:  2
Added packages:  0
Dropped packages:0
Upgraded packages:   13
Downgraded packages: 0

Size of added packages:  0 B
Size of dropped packages:0 B
Size of upgraded packages:   92.94 MiB
Size of downgraded packages: 0 B

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

= ADDED IMAGES =
Image: Scientific vagrant-virtualbox x86_64
Path: 
Labs/x86_64/images/Fedora-Scientific-Vagrant-39-20230831.n.0.x86_64.vagrant-virtualbox.box
Image: Scientific_KDE live x86_64
Path: Labs/x86_64/iso/Fedora-Scientific_KDE-Live-x86_64-39-20230831.n.0.iso
Image: Scientific vagrant-libvirt x86_64
Path: 
Labs/x86_64/images/Fedora-Scientific-Vagrant-39-20230831.n.0.x86_64.vagrant-libvirt.box
Image: Kinoite dvd-ostree ppc64le
Path: Kinoite/ppc64le/iso/Fedora-Kinoite-ostree-ppc64le-39-20230831.n.0.iso
Image: KDE live aarch64
Path: Spins/aarch64/iso/Fedora-KDE-Live-aarch64-39-20230831.n.0.iso
Image: i3 live aarch64
Path: Spins/aarch64/iso/Fedora-i3-Live-aarch64-39-20230831.n.0.iso
Image: Astronomy_KDE live x86_64
Path: Labs/x86_64/iso/Fedora-Astronomy_KDE-Live-x86_64-39-20230831.n.0.iso
Image: Security live x86_64
Path: Labs/x86_64/iso/Fedora-Security-Live-x86_64-39-20230831.n.0.iso
Image: Robotics live x86_64
Path: Labs/x86_64/iso/Fedora-Robotics-Live-x86_64-39-20230831.n.0.iso

= DROPPED IMAGES =
Image: Sericea dvd-ostree x86_64
Path: Sericea/x86_64/iso/Fedora-Sericea-ostree-x86_64-39-20230830.n.0.iso
Image: Silverblue dvd-ostree ppc64le
Path: 
Silverblue/ppc64le/iso/Fedora-Silverblue-ostree-ppc64le-39-20230830.n.0.iso

= ADDED PACKAGES =

= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  fwupd-1.9.4-1.fc39
Old package:  fwupd-1.9.3-1.fc39
Summary:  Firmware update daemon
RPMs: fwupd fwupd-devel fwupd-plugin-flashrom 
fwupd-plugin-modem-manager fwupd-plugin-uefi-capsule-data fwupd-tests
Size: 23.44 MiB
Size change:  2.29 MiB
Changelog:
  * Wed Jul 19 2023 Fedora Release Engineering  - 
1.9.3-2
  - Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild

  * Fri Aug 11 2023 Mamoru TASAKA  - 1.9.3-3
  - Rebuild for EVR upgrade path

  * Tue Aug 22 2023 Richard Hughes  - 1.9.4-1
  - New upstream release


Package:  gdm-1:44.1-4.fc39
Old package:  gdm-1:44.1-2.fc39
Summary:  The GNOME Display Manager
RPMs: gdm gdm-devel gdm-pam-extensions-devel
Size: 4.69 MiB
Size change:  -5.67 KiB
Changelog:
  * Tue Aug 29 2023 Ray Strode  - 1:44.1-3
  - Add crash fix, initial-setup fix, and simpledrm fix

  * Tue Aug 29 2023 Ray Strode  - 1:44.1-4
  - Add crash fix, initial-setup fix, and simpledrm fix (other half)


Package:  gnome-control-center-45~rc-2.fc39
Old package:  gnome-control-center-45~beta-1.fc39
Summary:  Utilities to configure the GNOME desktop
RPMs: gnome-control-center gnome-control-center-filesystem
Size: 27.04 MiB
Size change:  23.23 KiB
Changelog:
  * Wed Aug 23 2023 Felipe Borges  - 45~beta-2
  - Fix crash whe creating a new user account

  * Fri Aug 25 2023 Felipe Borges  - 45~rc-1
  - Update to 45.rc

  * Tue Aug 29 2023 Ray Strode  - 45~rc-2
  - Fetch default input sources if not-configured in gsettings


Package:  gnome-desktop3-44.0-7.fc39
Old package:  gnome-desktop3-44.0-3.fc39
Summary:  Library with common API for various GNOME modules
RPMs: gnome-desktop3 gnome-desktop3-devel gnome-desktop3-tests 
gnome-desktop4 gnome-desktop4-devel
Size: 4.76 MiB
Size change:  65.81 KiB
Changelog:
  * Sat Aug 26 2023 Ray Strode  - 44.0-4
  - Add APIs for finding default input sources

  * Sat Aug 26 2023 Ray Strode  - 44.0-5
  - Fix typo (s/langtool/langtable/)

  * Sat Aug 26 2023 Ray Strode  - 44.0-6
  - Improve APIs for finding default input sources

  * Mon Aug 28 2023 Ray Strode  - 44.0-7
  - Still twiddling with the default input sources api


Package:  gnome-initial-setup-45~beta-7.fc39
Old package:  gnome-initial-setup-45~beta-3.fc39
Summary:  Bootstrapping your OS
RPMs: gnome-initial-setup
Size: 2.25 MiB
Size change:  815 B
Changelog:
  * Sat Aug 26 2023 Ray Strode  - 45~beta-4
  - Add keyboard and input method handling fixes

  * Sat Aug 26 2023 Ray Strode  - 45~beta-5
  - Clean up gnome-desktop requires

  * Sat Aug 26 2023 Ray Strode  - 45~beta-6
  - Update to use slightly tweaked default input sources api from gnome-
desktop

  * Mon Aug 28 2023 Ray Strode  - 45~beta-7
  - More keyboard configuration updates


Package:  gnome-shell-45~beta.1-3.fc39
Old package:  gnome-shell-45~beta.1-1.fc39
Summary:  Window management and application launching for GNOME
RPMs: gnome-shell
Size: 6.90 MiB
Size change:  -4.50 KiB
Changelog:
  * Tue Aug 29 2023 Ray Strode  - 1:45~beta.1-1
  - Use input source defaults if not configured in gsettings

  * Tue Aug 29 2023 Ray

Re: Can we squeeze coreutils-9.4 into Fedora 39?

[Frantisek Zatloukal]

On Wed, Aug 30, 2023 at 6:11 PM David Cantrell  wrote:

> I personally agree that this is enough of a change to warrant
> consideration for Fedora 39, but I want Fedora QA to weigh in.  At this
> point we have beta and final blockers and you can use this form to
> propose one:
>
> https://qa.fedoraproject.org/blockerbugs/propose_bug
>
>
>
Or, the most straightforward way would be to wait for 39 Beta (the freeze
ends by the Beta release) , and do a normal package bump to 9.4 in the f39
branch. You wouldn't need any exception or patch cherry pick for this.


-- 

Best regards / S pozdravem,

František Zatloukal
Senior Quality Engineer
Red Hat
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Can we squeeze coreutils-9.4 into Fedora 39?

[David Cantrell]

On 8/30/23 15:45, Adam Williamson wrote:

On Wed, 2023-08-30 at 12:11 -0400, David Cantrell wrote:

On 8/29/23 23:13, Ian Laurie wrote:

coreutils-9.3 brought changes to the behavior of the -v option which
broke some of my automation scripts.

Because of this I have been blocking updates to coreutils in Rawhide and
Fedora 39. and I'm running coreutils-9.2-4.fc39.x86_64.

This change in the -v option has been reverted in 9.4 (released
2023-08-29).  From [1]:

** Changes in behavior

    'cp -v' and 'mv -v' will no longer output a message for each file
skipped
    due to -i, or -u.  Instead they only output this information with
--debug.
    I.e., 'cp -u -v' etc. will have the same verbosity as before
coreutils-9.3.

If it's too late to get 9.4 into 39, is it possible to locally include
this specific reverting patch?

[1] https://github.com/coreutils/coreutils/blob/master/NEWS


I personally agree that this is enough of a change to warrant
consideration for Fedora 39, but I want Fedora QA to weigh in.  At this
point we have beta and final blockers and you can use this form to
propose one:

https://qa.fedoraproject.org/blockerbugs/propose_bug

If you want some help filing this proposal or the process, I am happy to
answer questions here or in chat.  I am dcantrell on IRC and in Matrix chat.


well, the question is not so much how useful is *this* change, but what
*other* changes does coreutils 9.4 introduce. During Beta freeze, it
would be much safer to just backport this specific change.


Agreed.  Recent coreutils releases have done a number of changes similar 
to this and it is not unreasonable to assume 9.4 might have more of 
those as well.  Just taking in this patch makes sense as it restores 
longstanding behavior that users were relying on.



This is clearly not a Beta blocker, but you can propose it as a Beta
FE...


I was on the fence with this classification.  My view is breaking 
longstanding behavior like this in very common commands in a minor 
version update for the software seems like it would lead to a lot of bug 
reports.  But maybe that's just me.  Whatever the appropriate 
classification is for this request is fine with me.


--
David Cantrell 
Red Hat, Inc. | Boston, MA | EST5EDT
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Fedora rawhide compose report: 20230831.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20230830.n.0
NEW: Fedora-Rawhide-20230831.n.0

= SUMMARY =
Added images:4
Dropped images:  4
Added packages:  10
Dropped packages:0
Upgraded packages:   78
Downgraded packages: 0

Size of added packages:  12.21 MiB
Size of dropped packages:0 B
Size of upgraded packages:   1.78 GiB
Size of downgraded packages: 0 B

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

= ADDED IMAGES =
Image: Robotics live x86_64
Path: Labs/x86_64/iso/Fedora-Robotics-Live-x86_64-Rawhide-20230831.n.0.iso
Image: i3 live aarch64
Path: Spins/aarch64/iso/Fedora-i3-Live-aarch64-Rawhide-20230831.n.0.iso
Image: Astronomy_KDE live x86_64
Path: Labs/x86_64/iso/Fedora-Astronomy_KDE-Live-x86_64-Rawhide-20230831.n.0.iso
Image: Sericea dvd-ostree x86_64
Path: Sericea/x86_64/iso/Fedora-Sericea-ostree-x86_64-Rawhide-20230831.n.0.iso

= DROPPED IMAGES =
Image: Silverblue dvd-ostree ppc64le
Path: 
Silverblue/ppc64le/iso/Fedora-Silverblue-ostree-ppc64le-Rawhide-20230830.n.0.iso
Image: LXQt live aarch64
Path: Spins/aarch64/iso/Fedora-LXQt-Live-aarch64-Rawhide-20230830.n.0.iso
Image: Scientific vagrant-virtualbox x86_64
Path: 
Labs/x86_64/images/Fedora-Scientific-Vagrant-Rawhide-20230830.n.0.x86_64.vagrant-virtualbox.box
Image: Scientific vagrant-libvirt x86_64
Path: 
Labs/x86_64/images/Fedora-Scientific-Vagrant-Rawhide-20230830.n.0.x86_64.vagrant-libvirt.box

= ADDED PACKAGES =
Package: flexmark-java-0.64.6-1.fc40
Summary: CommonMark/Markdown Java parser with source level AST
RPMs:flexmark-java flexmark-java-all flexmark-java-ext-abbreviation 
flexmark-java-ext-admonition flexmark-java-ext-anchorlink 
flexmark-java-ext-aside flexmark-java-ext-attributes flexmark-java-ext-autolink 
flexmark-java-ext-definition flexmark-java-ext-emoji 
flexmark-java-ext-enumerated-reference flexmark-java-ext-escaped-character 
flexmark-java-ext-footnotes flexmark-java-ext-gfm-issues 
flexmark-java-ext-gfm-strikethrough flexmark-java-ext-gfm-tasklist 
flexmark-java-ext-gfm-users flexmark-java-ext-gitlab flexmark-java-ext-ins 
flexmark-java-ext-jekyll-front-matter flexmark-java-ext-jekyll-tag 
flexmark-java-ext-macros flexmark-java-ext-media-tags 
flexmark-java-ext-resizable-image flexmark-java-ext-spec-example 
flexmark-java-ext-superscript flexmark-java-ext-tables flexmark-java-ext-toc 
flexmark-java-ext-typographic flexmark-java-ext-wikilink 
flexmark-java-ext-xwiki-macros flexmark-java-ext-yaml-front-matter 
flexmark-java-ext-youtube-embedded flexmark-java-ext-zz 
flexmark-java-html2md-converter flexmark-java-javadoc 
flexmark-java-jira-converter flexmark-java-osgi flexmark-java-test-util 
flexmark-java-tree-iteration flexmark-java-util flexmark-java-util-ast 
flexmark-java-util-builder flexmark-java-util-collection 
flexmark-java-util-data flexmark-java-util-dependency 
flexmark-java-util-experimental flexmark-java-util-format 
flexmark-java-util-html flexmark-java-util-misc flexmark-java-util-options 
flexmark-java-util-sequence flexmark-java-util-visitor 
flexmark-java-youtrack-converter
Size:6.32 MiB

Package: golang-modernc-gc-2-2.3.0-2.fc40
Summary: Package gc is a Go compiler front end. Work in progess
RPMs:golang-modernc-gc-2 golang-modernc-gc-2-devel
Size:2.46 MiB

Package: jetbrains-annotations-24.0.1-1.fc40
Summary: Annotations for JVM-based languages
RPMs:jetbrains-annotations jetbrains-annotations-javadoc
Size:183.23 KiB

Package: python-pyongc-1.0.1-1.fc40
Summary: A python interface for accessing OpenNGC database data
RPMs:python3-pyongc python3-pyongc+data
Size:1.54 MiB

Package: rust-cfonts-1.1.2-1.fc40
Summary: Sexy ANSI fonts for the console
RPMs:cfonts rust-cfonts+default-devel rust-cfonts-devel
Size:1.45 MiB

Package: rust-gix-commitgraph-0.18.1-1.fc40
Summary: Read-only access to the git commitgraph file format
RPMs:rust-gix-commitgraph+default-devel rust-gix-commitgraph+serde-devel 
rust-gix-commitgraph-devel
Size:57.99 KiB

Package: rust-gix-fs-0.4.1-1.fc40
Summary: File system utilities for gix
RPMs:rust-gix-fs+default-devel rust-gix-fs-devel
Size:39.59 KiB

Package: rust-gix-hashtable-0.2.4-1.fc40
Summary: Hashtable based data structures optimized to utilize ObjectId keys
RPMs:rust-gix-hashtable+default-devel rust-gix-hashtable-devel
Size:25.97 KiB

Package: rust-gix-packetline-0.16.4-1.fc40
Summary: Implementation of the the pkt-line serialization format for gix
RPMs:rust-gix-packetline+async-io-devel 
rust-gix-packetline+blocking-io-devel rust-gix-packetline+default-devel 
rust-gix-packetline+futures-io-devel rust-gix-packetline+futures-lite-devel 
rust-gix-packetline+pin-project-lite-devel rust-gix-packetline+serde-devel 
rust-gix-packetline-devel
Size:105.75 KiB

Package: rust-gix-url-0.21.1-1.fc40
Summary: Implementation of parsing and serialization of URLs for gix
RPMs:rust-gix-url+default-devel rust-gix-url+serde-devel rust-gix-url-devel

[Test-Announce] Fedora 39 Branched 20230831.n.0 nightly compose nominated for testing

[rawhide]

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

Notable package version changes:
lorax - 20230824.n.0: lorax-39.4-1.fc39.src, 20230831.n.0: lorax-39.4-2.fc39.src

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

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

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

The individual test result pages are:

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

Thank you for testing!
-- 
Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: zlib-ng as a compat replacement for zlib

[Florian Weimer]

* Richard W. M. Jones:

> On Thu, Aug 31, 2023 at 11:05:55AM +0200, Kevin Wolf wrote:
>> Unfortunately, we seem to build the RHEL packages with --disable-zstd
>> (I suppose just because we tend to disable everything nobody explicitly
>> asked for). Maybe we should check other distros. If zstd is commonly
>> enabled, we could still make it the default upstream (because honestly,
>> it probably does makes sense from an upstream perspective). Of course,
>> for RHEL this would mean that images out there are likely to use zstd
>> soon, so it might need to enable zstd in newer versions, too.
>
> Oh that is bad actually.  We really should enable zstd support in RHEL :-/

The zstd package was added to RHEL 8 only after its release, so it's not
that you had much choice initially.

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

Re: Manual step in upgrade process for a FSWC

[Iker Pedrosa]

Hi,

On Wed, Aug 30, 2023 at 8:46 PM Kevin Fenzi  wrote:

> On Wed, Aug 30, 2023 at 11:59:18AM +0200, Iker Pedrosa wrote:
> > Hi,
> >
> > I intend to switch pam_userdb's database provider from BerkeleyDB to GDBM
> > and I'm writing a Fedora System-Wide Change
> >  for Fedora
> 40.
> > The upgrade process would involve a manual procedure where the user needs
> > to run a conversion tool for the database. Is this acceptable?
> >
> > An automation process could be created, but the location of the database
> is
> > configurable, which increases its complexity and effort. Especially for a
> > PAM module that is not widely used. Another option I can think of is to
> > automate the conversion process for the default location, and leave the
> > manual conversion for those using a tuned location. Would that be
> > acceptable?
>
> Will the new version emit some kind of error telling users what needs to
> happen?
>

It'll log an error but it will be generic, like "user_lookup: could not
open database `PATH': %m"


>
> Will that 'fail closed'? ie, no access granted until the db is
> converted?
>

I don't understand this question.


>
> I don't suppose it would be possible to just run the convert at runtime?
> ie, if old db is found at the configured location convert it to the new
> version?
>

There are several packages relying in BerkeleyDB and the database team is
working in a tool to convert them. So I'd like to avoid replicating the
code for each and every package, and instead rely on their tool.


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


-- 

Iker Pedrosa

Senior Software Engineer, Identity Management team

Red Hat 

Txapela (gorria) buruan eta ibili munduan

(Red) hat on his head and walk the world

Basque proverb

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

Re: zlib-ng as a compat replacement for zlib

[Richard W.M. Jones]

On Thu, Aug 31, 2023 at 11:05:55AM +0200, Kevin Wolf wrote:
> [ Cc: qemu-block ]
> 
> Am 30.08.2023 um 20:26 hat Richard W.M. Jones geschrieben:
> > On Tue, Aug 29, 2023 at 05:49:24PM -, Daniel Alley wrote:
> > > > The background to this is I've spent far too long trying to optimize
> > > > the conversion of qcow2 files to raw files.  Most existing qcow2 files
> > > > that you can find online are zlib compressed, including the qcow2
> > > > images provided by Fedora.  Each cluster in the file is separately
> > > > compressed as a zlib stream, and qemu uses zlib library functions to
> > > > decompress them.  When downloading and decompressing these files, I
> > > > measured 40%+ of the total CPU time is doing zlib decompression.
> > > > 
> > > > [You don't need to tell me how great Zstd is, qcow2 supports this for
> > > > compression also, but it is not widely used by existing content.]
> 
> You make it sound like compressing each cluster individually has a big
> impact. If so, does increasing the cluster size make a difference, too?
> That could be an change with less compatibility concerns.

The issue we're discussing in the original thread is speed of
decompression.  We noted that using zlib-ng (a not-quite drop-in
replacement for zlib) improves decompression speed by 40% or more.

Original thread:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/CDNPJ4SOTRQMYVCDI3ZSY4SP4FYESCWD/
zlib-ng proposed change:
https://src.fedoraproject.org/rpms/zlib-ng/pull-request/3

Size of the compressed file is also a concern, but wasn't discussed.

> > > Independent from the decision to use zlib-ng as a distro-wide zlib
> > > replacement, which is a good idea regardless.
> > >
> > > Are there reasons why Fedora's qcow2 images cannot switch to Zstd
> > > compression?  Zstd support appears to have been added by QEMU 5.1 in
> > > August 2020, and both EL8 and EL9 appear to have newer versions QEMU
> > > available (therefore, they ought to be able to support those
> > > images).
> > 
> > TBH I think the most probable reason is that people don't know about
> > it and it is not obvious that you have to enable it.  To generate a
> > zlib-compressed qcow2 file, you simply add the -c option, easy.  To
> > use zstd compression you have to use this mouthful:
> > 
> >   qemu-img convert -f raw disk.img -O qcow2 disk.qcow2 -c -o 
> > compression_type=zstd
> > 
> > The qemu-img man page doesn't even mention it.
> 
> Good point, that needs to be fixed.
> 
> (Though I don't think that '-o compression_type=zstd' in an unreasonable
> mouthful for enabling a non-standard compression algorithm.)
> 
> > I think all recent qcow2-based tools should be fine with zstd, but I
> > didn't check them all (RHEL 7 is still quite popular so that platform
> > would no longer be compatible).
> 
> So my first thought was that maybe we can just change the default now
> that the option has been there for quite a while. But then it occurred
> to me that it's not a hard dependency. So at least, the default would
> still have to be zlib if zstd isn't even compiled in, which makes it a
> bit less nice in theory. In practice, it depends on what build options
> distros actually use.
> 
> Unfortunately, we seem to build the RHEL packages with --disable-zstd
> (I suppose just because we tend to disable everything nobody explicitly
> asked for). Maybe we should check other distros. If zstd is commonly
> enabled, we could still make it the default upstream (because honestly,
> it probably does makes sense from an upstream perspective). Of course,
> for RHEL this would mean that images out there are likely to use zstd
> soon, so it might need to enable zstd in newer versions, too.

Oh that is bad actually.  We really should enable zstd support in RHEL :-/

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: firefox builds seem stuck on the farm - pls check

[Marius Schwarz]

Hi all,

Am 30.08.23 um 20:54 schrieb Kevin Fenzi:


Perhaps some folks could try building on an x86_64 vm and see if it
happens outside of koji?



The updates are not in the testing repo. They are now "just build". The 
usual workflow seems to be interrupted somehow.


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

Re: CVE: Python-twisted a.o. needs update for F37 due to matrix-synapse security issue

[Marius Schwarz]

Am 30.08.23 um 20:44 schrieb Jonathan Steffan:
On Sat, May 27, 2023 at 3:45 AM Vitaly Zaitsev via devel 
 wrote:


On 26/05/2023 16:22, Marius Schwarz wrote:
> This brings me to the question: whats the main issue for twisted
here?

1. Contact python-twisted maintainers.


Marius,

According to the upstream matrix-synapse pyproject.toml the minimum 
requirement is met in F37: Twisted = {extras = ["tls"], version = 
">=18.9.0"} which is available in F37. Were you able to resolve this?
On the day F38 had the synapse update rdy, I used that package ( without 
a flaw yet ) to upgrade synapse to the f38 version on f37.


This brings up the question, what the really issue on f37 with the 
dependencies was, as those did not change at all. it just worked.


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

[Bug 2236101] perl-HTML-FormatText-WithLinks for EL8 and EL9

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



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


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202236101%23c2
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Inactive packager policy for the F39 cycle

[Mattia Verga via devel]

Il 30/08/23 22:02, Ben Cotton ha scritto:
> On Wed, Aug 30, 2023 at 2:47 PM Kevin Fenzi  wrote:
>> Might you be willing to also do the provenpackager one?
>> ( https://docs.fedoraproject.org/en-US/fesco/Provenpackager_policy/ )
>>
> For Mattia (or anyone else who wants to pick this up), you can see my
> SOP at 
> https://docs.fedoraproject.org/en-US/program_management/pgm_guide/sop/inactive-provenpackagers/
>
Thank you, I'll read the steps above and send the notification ASAP. 
(not sure I can post to devel-announce, though)

Mattia

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