[Bug 2225676] perl-IO-Compress-2.206 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Resolution|--- |ERRATA
 Status|MODIFIED|CLOSED
   Fixed In Version||perl-IO-Compress-2.206-1.fc
   ||39
Last Closed||2023-07-27 05:57:01



--- Comment #2 from Fedora Update System  ---
FEDORA-2023-923d7497c3 has been pushed to the Fedora 39 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=2225676

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202225676%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

Schedule for Thursday's FESCo Meeting (2023-07-27)

[Tom Stellard]

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-07-27 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 =

Anaconda WebUI for Fedora Workstation by default
https://pagure.io/fesco/issue/3032
APPROVED (+4, 0, -0)

ibus-anthy 1.5.15
https://pagure.io/fesco/issue/3029
APPROVED (+3, 0, 0)

= Followups =
#3039 RFC: Roadmap for DNF5 in Fedora 39 / invoking the Contingency Mechanism
https://pagure.io/fesco/issue/3039

#3035 Change: Build JDKs once, repack everywhere
https://pagure.io/fesco/issue/3035

= 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.
___
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 2224929] perl-Tree-1.16 is available

[bugzilla]

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



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

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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202224929%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

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

[updates]

The following Fedora EPEL 7 Security updates need testing:
 Age  URL
   3  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-76532a12e5   
libopenmpt-0.6.11-1.el7
   1  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-7fdb39245c   
apptainer-1.2.1-1.el7
   1  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-284c34a6cc   
caddy-1.0.5-1.el7


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

libmodsecurity-3.0.10-1.el7

Details about builds:



 libmodsecurity-3.0.10-1.el7 (FEDORA-EPEL-2023-6e6ee7bf77)
 A library that loads/interprets rules written in the ModSecurity SecRules

Update Information:

Update to 3.0.10

ChangeLog:

* Wed Jul 26 2023 Mikel Olasagasti Uranga  - 3.0.10-1
- Update to 3.0.10 rhbz#2225895
* Thu Jul 20 2023 Fedora Release Engineering  - 
3.0.9-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild


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

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

[updates]

The following Fedora EPEL 9 Security updates need testing:
 Age  URL
   3  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-1597f71503   
libopenmpt-0.6.11-1.el9
   1  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-3ee1cfb5ed   
apptainer-1.2.1-1.el9


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

Lmod-8.7.30-1.el9
ctpl-0.3.4-18.el9
geany-plugins-1.38-9.el9
hstr-3.1-1.el9
libkdumpfile-0.5.2-1.el9
libmodsecurity-3.0.10-1.el9
python-damo-1.9.1-1.el9
qperf-0.4.9-26.el9
rust-az-1.2.1-4.el9
rust-futures0.1-0.1.31-4.el9
rust-mio0.7-0.7.14-6.el9

Details about builds:



 Lmod-8.7.30-1.el9 (FEDORA-EPEL-2023-06885915bf)
 Environmental Modules System in Lua

Update Information:

Update to 8.7.30

ChangeLog:

* Tue Jul 25 2023 Orion Poplawski  - 8.7.30-1
- Update to 8.7.30
* Wed Jul 19 2023 Fedora Release Engineering  - 
8.7.29-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild
* Sat Jul 15 2023 Orion Poplawski  - 8.7.29-1
- Update to 8.7.29
* Sat May 27 2023 Orion Poplawski  - 8.7.25-2
- Add fish integration (bz#2196379)
* Thu May 25 2023 Orion Poplawski  - 8.7.25-1
- Update to 8.7.25
* Sat May  6 2023 Orion Poplawski  - 8.7.24-1
- Update to 8.7.24
* Fri Mar 31 2023 Orion Poplawski  - 8.7.23-1
- Update to 8.7.23
* Mon Mar 27 2023 Orion Poplawski  - 8.7.22-1
- Update to 8.7.22




 ctpl-0.3.4-18.el9 (FEDORA-EPEL-2023-3f0ae906c7)
 Template library and engine written in C

Update Information:

This update brings the Geany Plugins to an EPEL9 box near you.

ChangeLog:

* Fri Jun 30 2023 Dominic Hopf  - 0.3.4-18
- initial build for EPEL9
* Thu Jan 19 2023 Fedora Release Engineering  - 
0.3.4-17
- Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild
* Wed Jul 20 2022 Fedora Release Engineering  - 
0.3.4-16
- Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild
* Thu Jan 20 2022 Fedora Release Engineering  - 
0.3.4-15
- Rebuilt for https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild
* Wed Jul 21 2021 Fedora Release Engineering  - 
0.3.4-14
- Rebuilt for https://fedoraproject.org/wiki/Fedora_35_Mass_Rebuild




 geany-plugins-1.38-9.el9 (FEDORA-EPEL-2023-3f0ae906c7)
 Plugins for Geany

Update Information:

This update brings the Geany Plugins to an EPEL9 box near you.

ChangeLog:

* Sun Mar  5 2023 Pete Walter  - 1.38-9
- Rebuild for libgit2 1.6.x
* Fri Jan 27 2023 Pete Walter  - 1.38-8
- Rebuild for libgit2 1.5.x
* Fri Jan 20 2023 Pete Walter  - 1.38-7
- Fix the build with libgit2 1.4.x
* Thu Jan 19 2023 Fedora Release Engineering  - 1.38-6
- Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild
* Thu Jul 21 2022 Fedora Release Engineering  - 1.38-5
- Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild
* Sun Feb 20 2022 Igor Raits  - 1.38-4
- Rebuild for libgit2 1.4.x
* Thu Jan 20 2022 Fedora Release Engineering  - 1.38-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild
* Sun Nov 28 2021 Igor Raits  - 1.38-2
- Rebuild for libgit2 1.3.x
* Sun Oct 10 2021 Dominic Hopf  1.38-1
- New upstream release: Geany-Plugins 1.38
* Wed Jul 21 2021 Fedora Release Engineering  - 1.37-4
- Rebuilt for https://fedoraproject.org/wiki/Fedora_35_Mass_Rebuild




 hstr-3.1-1.el9 (FEDORA-EPEL-2023-469ad72dcc)
 Suggest box like shell history completion

Update Information:

update to 3.1

ChangeLog:

* Wed Jul 26 2023 Jonathan Wright  - 3.1-1
- Update to 3.1
* Thu Jul 20 2023 Fedora Release Engineering  - 3.0-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild

References:

  [ 1 ] Bug #2226672 - hstr 3.1 upstream release is available
https://bugzilla.redhat.com/show_bug.cgi?id=2226672

[Bug 2224929] perl-Tree-1.16 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



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

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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202224929%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

Re: fedora-review workarounds for dnf5

[Sandro]

On 26-07-2023 17:36, Jakub Kadlcik wrote:

Hello Sandro,


I noticed that in f39 builds in Copr the directory containing the
results is now named after the package. Comparing that to the
"traditional" fedora-review directory in f38 builds, I miss the
`licensecheck.txt` file.


It suddenly started happening and I don't know what is to blame yet.
You can follow

https://github.com/FrostyX/fedora-review-service/issues/28
https://pagure.io/FedoraReview/issue/486

I plan to work on it as soon as I can.


Thank you Jakub. I'll be following along. It's not all that urgent by 
any means as long as the file is still there in the stable branches.


-- Sandro
___
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: F39 Change Proposal: Enable fwupd-refresh.timer by default on IoT, CoreOS & Server Editions (Self-Contained)

[Dominik 'Rathann' Mierzejewski]

On Wednesday, 26 July 2023 at 21:11, Björn Persson wrote:
> Vitaly Zaitsev via devel wrote:
> > On 26/07/2023 11:04, Dominik 'Rathann' Mierzejewski wrote:
> > > You could, for example, buy a supported Logitech
> > > Receiver  
> > 
> > I don't recommend anyone to buy this proprietary hardware:
> 
> For years I tried to use Bluetooth mice, thinking a standard would be
> preferable over a proprietary protocol. But Bluetooth never worked
> well for me. It's not just mice. Everything I've tried to do with
> Bluetooth has been unstable and unreliable. Eventually I gave up and
> concluded that Bluetooth in Fedora is not a thing to rely on.
> The mice I've used that connect to Logitech dongles have always been
> responsive and never had any connection problems.

I had issues with mouse cursor freezing or getting jumpy, because
Logitech wireless protocol still operates in the 2.4GHz band and is
still vulnerable to 2.4GHz Wi-Fi and Bluetooth interference. I had to
switch to 5GHz Wi-Fi on devices in the room or move away those that
didn't support 5GHz before my mouse became usable again.

Regards,
Dominik
-- 
Fedora   https://fedoraproject.org
There should be a science of discontent. People need hard times and
oppression to develop psychic muscles.
-- from "Collected Sayings of Muad'Dib" by the Princess Irulan
___
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: F39 Change Proposal: Enable fwupd-refresh.timer by default on IoT, CoreOS & Server Editions (Self-Contained)

[Björn Persson]

Vitaly Zaitsev via devel wrote:
> On 26/07/2023 11:04, Dominik 'Rathann' Mierzejewski wrote:
> > You could, for example, buy a supported Logitech
> > Receiver  
> 
> I don't recommend anyone to buy this proprietary hardware:

For years I tried to use Bluetooth mice, thinking a standard would be
preferable over a proprietary protocol. But Bluetooth never worked well
for me. It's not just mice. Everything I've tried to do with Bluetooth
has been unstable and unreliable. Eventually I gave up and concluded
that Bluetooth in Fedora is not a thing to rely on. The mice I've used
that connect to Logitech dongles have always been responsive and never
had any connection problems.

Mouse cables get in my way and disturb my work. As long as GUIs and web
programs require a mouse, I need a wireless mouse. Since Bluetooth is
out, Logitech is it.

I'd never use a wireless keyboard though. Whether Bluetooth or Logitech,
I'm not going to type passphrases over some iffy radio protocol using a
random number generator of unknown quality.

Alexander Ploumistos wrote:
> And thanks to fwupd and Logitech's embracing it, we had the fix in a
> very short time.

I never knew about it until now, because nothing notified me that a
firmware update was available. I have now enabled fwupd-refresh.timer.
I seem to get notifications only in SSH, not on the console, but that's
something at least. If it had been on by default, then it would probably
have been less than four years before I found out about those
vulnerabilities.

If the firmware files are properly authenticated, then I think
notifications about firmware updates should be enabled on all
installations.

Björn Persson


pgpR2_bpFfGGv.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: List of long term FTBFS packages to be retired in August

[Kevin Fenzi]

On Tue, Jul 25, 2023 at 06:45:41PM +0200, Miro Hrončok wrote:
> IMHO it is what the policy says, quite explicitly:
> 
> From 
> https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs
> 
> """
> Cca six weeks before the Fedora N mass branching, packages that weren’t
> successfully rebuilt at least in Fedora N-2 are collected and weekly
> reminders are sent to affected maintainers and the Fedora devel mailing
> list.
> 
> Cca a week before the Fedora N mass branching, packages that weren’t
> successfully rebuilt at least in Fedora N-2 will be retired assuming there
> have been at least 5 warnings on the devel mailing list. The bug status has
> no effect on this retirement. This can be requested via a releng issue.
> """
> 
> When I included glibc32 in the list, it wasn't successfully rebuilt at least
> in Fedora 37.
> 
> We could argue what "successfully rebuilt" actually means, but when I wrote
> that policy, the spirit was "an actual built shipped to Fedora users" rather
> than "a Koschei rebuild".

Sure, but glibc32 is in fact never shipped to Fedora users. :)

We explicily block it in pungi so it never goes out.
It's a buildsystem implementation detail.

> I see you rebuilt it now, thanks.
> 
> Should I open a releng ticket to include this package in the next mass 
> rebuild?

I suppose we could rebuild it, I don't think that would matter any?
Or would it? Florian?

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: fedora-review workarounds for dnf5

[Michel Alexandre Salim]

On Wed, Jul 26, 2023 at 05:36:04PM +0200, Jakub Kadlcik wrote:
> Hello Sandro,
> 
> > I noticed that in f39 builds in Copr the directory containing the
> > results is now named after the package. Comparing that to the
> > "traditional" fedora-review directory in f38 builds, I miss the
> > `licensecheck.txt` file.
> 
> It suddenly started happening and I don't know what is to blame yet.
> You can follow
> 
> https://github.com/FrostyX/fedora-review-service/issues/28
> https://pagure.io/FedoraReview/issue/486
> 
> I plan to work on it as soon as I can.
> 
> Jakub
> 
Thanks for your work on this Jakub! I'll cut another release once this
is done.

Will try to work on modernizing the build system more, but I'll probably
not get to it for a couple of weeks - need to deal with my Rawhide
FTBFSes first.

Cheers,

-- 
Michel Alexandre Salim
identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2


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

Re: fedora-review workarounds for dnf5

[Michel Alexandre Salim]

On Mon, Jul 24, 2023 at 09:47:32PM -0500, Michel Alexandre Salim wrote:
> Hi all,
> 
> On Mon, Jul 17, 2023 at 10:54:43AM -0600, Jerry James wrote:
> > Like many of you, I have been quite inconvenienced because of
> > dnf5-related breakage of fedora-review.  I've been monkeying with it
> > today and finally got a successful run of fedora-review after making
> > the following changes [*].
> >
> I'm happy (and relieved) to say that a fixed fedora-review is ready for
> testing:
> 
> https://bodhi.fedoraproject.org/updates/?search==fedora-review=pending=testing
> 
fedora-review-0.10.0-1.fc3{7,8} had shebang issues, for those who are
testing please retest fedora-review-0.10.0-2.fc3{7,8} that I just posted
to fix this, thanks!

Turns out we never touched the shebangs and they still had Python
2-isms, and %{py3_shebang_fix} just adds a duplicate -sP which is not
needed -- it's the -tt that was the issue.

-- 
Michel Alexandre Salim
identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2


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

Re: Restricting automounting of uncommon filesystems?

[Eric Sandeen]

On 7/24/23 10:40 PM, Demi Marie Obenour wrote:

On 7/24/23 15:11, Eric Sandeen wrote:

On 7/23/23 7:22 PM, Steve Grubb wrote:

On Saturday, July 22, 2023 2:01:34 AM EDT Matthew Garrett wrote:

A discussion within Debian again brought up the problem that:

1) Automounting of removable media exposes the kernel to a lot of
untrusted input
2) Kernel upstream are not terribly concerned with ensuring that kernel
filesystems are resilient against deliberately malformed filesystems so
are mostly not proactively looking for bugs there
3) Uncommonly used filesystems are less likely to be tested against
adverse input in the real world and so are more likely to contain
exploitable bugs

There are various cases where people do need to make use of uncommon
filesystems, but the majority of them aren't related to removable media.
udisks2 supports setting the UDISKS_AUTO variable to 0 on devices that
shouldn't be automounted, which means something like:

SUBSYSTEM!="block", GOTO="udisks_insecure_fs_end"
ENV{ID_FS_TYPE}=="hfs", ENV{UDISKS_AUTO}="0"
# repeat as necessary for anything else that shouldn't be automounted
LABEL="udisks_insecure_fs_end"

ought to be enough. So:

a) Does this seem like a good idea?
b) If so, is dealing with it via udev rules the right approach? This way
seems desktop-agnostic
c) Where should it ship, and what should the process be for disabling it
for people who need this functionality?

Long-term I'd love to see more work put into having FUSE support for
these and leaving the in-kernel fs to stuff we know is trustworthy, but
that's rather more work.


If "a malicious input can't cause problems" is the threshold for
trustworthy, I'm not sure we have any trustworthy filesystems as this point.

https://syzkaller.appspot.com/upstream/s/ext4
https://syzkaller.appspot.com/upstream/s/xfs
https://syzkaller.appspot.com/upstream/s/btrfs
https://syzkaller.appspot.com/upstream/s/fat


A while back, I wrote the fsfuzzer specifically to find, in a repeatable way,
filesystem bugs so they can be fixed:

https://github.com/stevegrubb/fsfuzzer

It does not support all filesystems, but it is easy to add support through
adding the correct mounter to the scrips. It has found *so* *many* filesystem
bugs over time.


That was awesome, back in the day! syzbot/syzcaller is the new shiny
here though, finding filesystem flaws day after day that (with all due
respect) fsfuzzer could never have reached (think: fuzzing metadata and
then fixing up the checksum so it passes initial validation on read.)

And frankly that is some of my motivation to find an improvement here. A
small cadre of filesystem developers are near the breaking point trying
to keep up with an army of machines running syzkaller.

-Eric


How much of the problem is the C programming language itself?  I’m NOT
suggesting that you rewrite your filesystem in Rust; that would be an
extremely unreasonable request.  I’m merely trying to figure out how
much of this is a case of “filesystems are hard” and how much of this
is C providing essentially no help.


Well, this has been discussed but it's obviously not a short-term 
solution. :) (Nor would Rust be a panacea. Some of the problems may be 
mitigated by a language like Rust, but certainly not all of them.)


I think it's a little bit of both scenarios, tbh.

-Eric
___
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: F39 Change Proposal: Enable fwupd-refresh.timer by default on IoT, CoreOS & Server Editions (Self-Contained)

[Vitaly Zaitsev via devel]

On 26/07/2023 11:24, Alexander Ploumistos wrote:

What Dominik wrote would apply e.g. for an NVMe replacement drive from
Kingston or Samsung (proprietary hardware too, it's a shocker).


None of my 5 Samsung SSDs are supported (3 NVMe and 2 SATA). But they 
can be updated from MS Windows.


I guess only built-in Samsung OEM drives can be updated with fwupd.


And thanks to fwupd and Logitech's embracing it, we had the fix in a
very short time.


It has only been partially fixed. A complete fix would require replacing 
all existing hardware:



Mengs says this vulnerability exists due to an incomplete fix for 
CVE-2016-10761, one of the infamous MouseJack vulnerabilities, and that 
Logitech has no plans on patching this new attack variation.

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

Re: F39 Change Proposal: Enable fwupd-refresh.timer by default on IoT, CoreOS & Server Editions (Self-Contained)

[Leon Fauster via devel]

Am 26.07.23 um 18:00 schrieb Chris Adams:

Once upon a time, Solomon Peachy  said:

None of the other SSDs I have deployed (Samsung and Crucual SATA) are
updatable via LVFS, unfortunately.  But, hilariously, both Samsung and
Crucial's official updaters appear to be self-contained linux ISOs.  So
clearly the technical capability is there...


The difference is often the update method.  fwupd supports a specific
standard way of applying firmware updates, but often things use very
proprietary methods.  Some storage may not support applying updates
while be accessed for example (so have to boot from ISO/etc. to apply
while unmounted).

While there's a standard for updating UEFI firmware, lots of
motherboards still use older custom methods.  Also, many are unable to
carry over config properly, so they reset all settings on a firmware
update (which is problematic and arguably a reason for making it harder
to do).  I think most of the systems I've used that support fwupd UEFI
updates are able to do so without a config reset.

Which... having to have a config reset on a firmware update in this day
is so dumb.  Very rarely do config options change (and even then, it is
typically "new options added", not old options changed), so there's
really no excuse for not storing the config in a forward-compatible way
and restoring those settings after a firmware update.  Dell PowerEdge
servers have managed this for years, why can't they apply it to
everything?

And also, why can't Dell get PowerEdge updates into LVFS? :)



While reading this discussion, I tried it on my local Dell XPS and
was surprised that LVFS suggests a firmware update (bios) for my
model (it says that I'm 4 versions behind), albeit on Dell's support
page such updates are not listed (here I would have already the latest).

Not sure about the integrity / quality of the uploads to LVFS??

Does anyone know how to compare the artifacts on LVFS (.cab) with
the ones on Dell's support page (.exe, .rcv)?


--
Leon
___
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: List of long term FTBFS packages to be retired (and similar reports)

[Frank Dana]

On Tue, Jul 25, 2023, 10:18 AM Miro Hrončok  wrote:

> Dear maintainers.
>
> Based on the current fail to build from source policy, the following
> packages
> should be retired from Fedora 39 approximately one week before branching.
>
> 5 weekly reminders are required, hence the retirement will happen
> approximately in 2 weeks, i.e. around 2023-08-01.
>
> Policy:
>
> https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
>
> The packages in rawhide were not successfully built at least since Fedora
> 36.
>
> This report is based on dist tags.
>
> Packages collected via:
>
> https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb
>
> If you see a package that was built, please let me know.
> If you see a package that should be exempted from the process,
> please let me know and we can work together to get a FESCo approval for
> that.
>
> If you see a package that can be rebuilt, please do so.
>


Apologies if this has been discussed in the past, but...

Perhaps I'm unusual, perhaps not. But the way I typically consume any of
Miro's packaging reports is, I scroll down to the "affected
(co-)maintainers" section, look for my userid to see if there's anything I
need to deal with urgently, and then... Well, depends how much time I have.
Sometimes, that's it. Other times, I look over the rest of the mail to see
if any packages of interest to me are listed. But I always start by looking
for my own name.

So, because the PACKAGER, rather than PACKAGE, names are actually the most
important part of the email (at least for me), I was wondering if it would
make sense to list them second or even first, rather than third / last?
___
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: F39 Change Proposal: Enable fwupd-refresh.timer by default on IoT, CoreOS & Server Editions (Self-Contained)

[Peter Robinson]

On Wed, Jul 26, 2023 at 3:37 PM Ralf Corsépius  wrote:
>
>
>
> Am 26.07.23 um 15:55 schrieb Solomon Peachy via devel:
> > On Wed, Jul 26, 2023 at 09:45:13AM +0200, Ralf Corsépius wrote:
> >> It could be "my bubble", but for me, in all these fwupd is around, it has
> >> never, ever worked on any piece of HW for me.
> >
> > Most of the stuff I have that is updated through fwupd are peripherals
> > [1] that are independent of the system vendor.
> >
> > That said, my two primary systems are a Lenovo laptop and an HP
> > workstation that are fully supported by fwupd/lvfs,
>
> My (older) lenovo laptop and my HPE Micro-Server are obviously not.
>
> > and the UEFI dbx
> > stuff works on all of the remaining physical systems (including servers)
> To my big surprise, for the first time ever, today fwupd installed a dbx
> update on one of my machine - Now, I am still wondering why it didn't do
> so on another, similar machine ;)
>
> > [1] Off the top of my head: Logitech wireless stuff, Jabra conference
> >  speaker, synaptics fingerprint sensor, (Samsung?) NVME storage, and
> This is the second time, somebody mentions Samsung NVMEs were supported.
> Well, what shall I say.
>
> I have several of them (and Samsung SATA SSDs), but so far, I always had
> to resort to other means of updating their firmware (Windows+Magician or
> iso-images), because fwupd would not want to update.

Ultimately being supported and the vendor actually bothering to
publish the firmware updates is two different things, I see this in
linux-firmware too WRT to in particular the various wireless driver
firmware.

From the NVME PoV the firmware update process is standardised as part
of the NVME spec, in most cases I have found, and I've tried a few
different vendors, you can use fwupdmgr to apply the updates from the
vendor's update zip file.

I blogged about it here:
https://nullr0ute.com/2022/06/using-fwupdmgr-to-update-nvme-firmware/
___
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: F39 Change Proposal: Enable fwupd-refresh.timer by default on IoT, CoreOS & Server Editions (Self-Contained)

[Chris Adams]

Once upon a time, Solomon Peachy  said:
> None of the other SSDs I have deployed (Samsung and Crucual SATA) are 
> updatable via LVFS, unfortunately.  But, hilariously, both Samsung and 
> Crucial's official updaters appear to be self-contained linux ISOs.  So 
> clearly the technical capability is there...

The difference is often the update method.  fwupd supports a specific
standard way of applying firmware updates, but often things use very
proprietary methods.  Some storage may not support applying updates
while be accessed for example (so have to boot from ISO/etc. to apply
while unmounted).

While there's a standard for updating UEFI firmware, lots of
motherboards still use older custom methods.  Also, many are unable to
carry over config properly, so they reset all settings on a firmware
update (which is problematic and arguably a reason for making it harder
to do).  I think most of the systems I've used that support fwupd UEFI
updates are able to do so without a config reset.

Which... having to have a config reset on a firmware update in this day
is so dumb.  Very rarely do config options change (and even then, it is
typically "new options added", not old options changed), so there's
really no excuse for not storing the config in a forward-compatible way
and restoring those settings after a firmware update.  Dell PowerEdge
servers have managed this for years, why can't they apply it to
everything?

And also, why can't Dell get PowerEdge updates into LVFS? :)

-- 
Chris Adams 
___
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: Flock CFP: Language SIGs discussion

[Maxwell G]

On Wed Jul 26, 2023 at 14:09 +, Zbigniew Jędrzejewski-Szmek wrote:
> On Wed, Jul 05, 2023 at 01:39:47PM +0200, Fabio Valentini wrote:
> > On Wed, Jul 5, 2023 at 8:23 AM Jens-Ulrik Petersen  
> > wrote:
> > >
> > > I have submitted a Flock proposal to have a common discussion session for 
> > > (modern) Language SIGs. I think for this to be successful we need 
> > > representatives from various Language SIGs to be there (Rust, Haskell, 
> > > OCaml, Golang and of course Python and older ecosystems like Perl, R, TeX 
> > > come to mind immediately - surely there are more). Language packaging 
> > > experts are also welcome of course independently or affiliated to one or 
> > > more language SIGs. Of course I also hope there will be broad attendance 
> > > by interested contributors.
> > 
> > This is a great idea, but I don't think any Rust SIG members will be
> > at Flock this year :(
>
> I'll be there and I hope to join the session.

I wanted to be there to talk about Changes/Mass_Retire_Golang_Leaves and
some of the other work we've been doing in the Go SIG to clean up our
packages, as I think it'd be useful to other SIGs, but I'll only be at
Flock the last two days :(.

-- 
Maxwell G (@gotmax23)
Pronouns: He/They
___
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: fedora-review workarounds for dnf5

[Jakub Kadlcik]

Hello Sandro,

> I noticed that in f39 builds in Copr the directory containing the
> results is now named after the package. Comparing that to the
> "traditional" fedora-review directory in f38 builds, I miss the
> `licensecheck.txt` file.

It suddenly started happening and I don't know what is to blame yet.
You can follow

https://github.com/FrostyX/fedora-review-service/issues/28
https://pagure.io/FedoraReview/issue/486

I plan to work on it as soon as I can.

Jakub

On Wed, Jul 26, 2023 at 1:34 AM Sandro  wrote:
>
> On 25-07-2023 04:47, Michel Alexandre Salim wrote:
> > Once this lands in F38, Fedora Review Service should be fixed, unless
> > I'm missing something.
>
> First of all, thanks for bringing fedora-review back. I rely on it quite
> a bit reviewing my own packages as well as for official reviews.
>
> I noticed that in f39 builds in Copr the directory containing the
> results is now named after the package. Comparing that to the
> "traditional" fedora-review directory in f38 builds, I miss the
> `licensecheck.txt` file.
>
> The contents of the fedora-review directory ($PACKAGE_NAME) in f39 look
> more alike to a local fedora-review, which is fine. But
> `licensecheck.txt` is invaluable for checking licenses of generated
> files. Just now I finished a review using the f38 build, which detected
> two additional licenses in generated files, that went unnoticed by the
> submitter.
>
> Can `licensecheck.txt` be added back to f39 fedora-review runs, please?
>
> -- Sandro
> ___
> 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: Unannounced soname bump: libotf

[Jason L Tibbitts III]

> Gary Buhrmaster  writes:

> I have found that using something like libfoo.so.X{,.*} in the %files
> directive can be a useful reminder (enforcer) to reduce such surprises
> (that particular glob presumes semantic versioning, and that minor and
> patch level updates do not require rebuilds, but that is true much of
> the time).

In fact, excessively wide globbing here is explicitly discouraged by the
packaging guidelines:
https://docs.fedoraproject.org/en-US/packaging-guidelines/#_listing_shared_library_files

Looking at the current spec, it uses "%{_libdir}/*.so.*"; had it
followed this guideline, I believe this issue would not have occurred.

 - J<
___
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: F39 Change Proposal: Enable fwupd-refresh.timer by default on IoT, CoreOS & Server Editions (Self-Contained)

[Solomon Peachy via devel]

On Wed, Jul 26, 2023 at 04:36:13PM +0200, Ralf Corsépius wrote:
> My (older) lenovo laptop and my HPE Micro-Server are obviously not.

The laptop is a T495 (introduced late 2019), but the workstation is an 
older HP Z440 (introduced in late 2014!)

> This is the second time, somebody mentions Samsung NVMEs were supported.
> Well, what shall I say.

I wouldn't go so far as to say _all_ Samsung NVMEs are supported, but 
the unit in my laptop had an update published, though it appears that 
Lenovo was the one that submitted it.

> I have several of them (and Samsung SATA SSDs), but so far, I always had to
> resort to other means of updating their firmware (Windows+Magician or
> iso-images), because fwupd would not want to update.

None of the other SSDs I have deployed (Samsung and Crucual SATA) are 
updatable via LVFS, unfortunately.  But, hilariously, both Samsung and 
Crucial's official updaters appear to be self-contained linux ISOs.  So 
clearly the technical capability is there...

 - Solomon
-- 
Solomon Peachypizza at shaftnet dot org (email)
  @pizza:shaftnet dot org   (matrix)
Dowling Park, FL  speachy (libra.chat)


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

[Bug 2224929] perl-Tree-1.16 is available

[bugzilla]

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



--- Comment #3 from Fedora Update System  ---
FEDORA-2023-8157725a69 has been submitted as an update to Fedora 37.
https://bodhi.fedoraproject.org/updates/FEDORA-2023-8157725a69


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202224929%23c3
___
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 2224929] perl-Tree-1.16 is available

[bugzilla]

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



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


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202224929%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: Unannounced soname bump: libotf

[Gary Buhrmaster]

On Wed, Jul 26, 2023 at 1:56 PM Michal Schorm  wrote:
>
> My apologies !
> I built the new version when cleaning old PRs and I failed to check
> for the soname bump.
> Thank you for cleaning up after me. I will try my best to remember to
> check it next time.

I have found that using something like
   libfoo.so.X{,.*}
in the %files directive can be a useful
reminder (enforcer) to reduce such
surprises (that particular glob presumes
semantic versioning, and that minor
and patch level updates do not require
rebuilds, but that is true much of the time).

To be fair, I have sometimes forgotten to
change the glob when I have intended to
bump the package/soname version in an
update, but at least I did get the intended
reminder!
___
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 2224929] perl-Tree-1.16 is available

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

   Fixed In Version||perl-Tree-1.16-1.fc39
 Status|ASSIGNED|MODIFIED



--- Comment #1 from Petr Pisar  ---
A bug-fix release suitable for all Fedoras.


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202224929%23c1
___
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: F39 Change Proposal: Enable fwupd-refresh.timer by default on IoT, CoreOS & Server Editions (Self-Contained)

[Ralf Corsépius]

Am 26.07.23 um 15:55 schrieb Solomon Peachy via devel:

On Wed, Jul 26, 2023 at 09:45:13AM +0200, Ralf Corsépius wrote:

It could be "my bubble", but for me, in all these fwupd is around, it has
never, ever worked on any piece of HW for me.


Most of the stuff I have that is updated through fwupd are peripherals
[1] that are independent of the system vendor.

That said, my two primary systems are a Lenovo laptop and an HP
workstation that are fully supported by fwupd/lvfs,


My (older) lenovo laptop and my HPE Micro-Server are obviously not.


and the UEFI dbx
stuff works on all of the remaining physical systems (including servers)
To my big surprise, for the first time ever, today fwupd installed a dbx 
update on one of my machine - Now, I am still wondering why it didn't do 
so on another, similar machine ;)



[1] Off the top of my head: Logitech wireless stuff, Jabra conference
 speaker, synaptics fingerprint sensor, (Samsung?) NVME storage, and
This is the second time, somebody mentions Samsung NVMEs were supported. 
Well, what shall I say.


I have several of them (and Samsung SATA SSDs), but so far, I always had 
to resort to other means of updating their firmware (Windows+Magician or 
iso-images), because fwupd would not want to update.


Ralf
___
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: Macros in side-tag

[Zbigniew Jędrzejewski-Szmek]

On Wed, Jul 26, 2023 at 04:19:05PM +0200, Ralf Corsépius wrote:
> 
> 
> Am 26.07.23 um 13:46 schrieb Vít Ondruch:
> 
> > I think that Perl folks are using something aka %perl_bootstrap. Not
> > sure if this is just for historic reasons and they could eventually
> > migrate to regular bootstrap method.
> 
> No, it's not historical. Perl has cyclic dependencies. To break them, some
> perl modules are built twice.

The question is why it's %perl_bootstrap instead of %_with_bootstrap,
which is the documented macro for bootstrapping (and which also has
automatic support in %dist, etc.).

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

Re: Macros in side-tag

[Ralf Corsépius]

Am 26.07.23 um 13:46 schrieb Vít Ondruch:

I think that Perl folks are using something aka %perl_bootstrap. Not 
sure if this is just for historic reasons and they could eventually 
migrate to regular bootstrap method.


No, it's not historical. Perl has cyclic dependencies. To break them, 
some perl modules are built twice.


Ralf
___
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 2226782] perl-TAP-Formatter-HTML-0.13 is available

[bugzilla]

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

Paul Howarth  changed:

   What|Removed |Added

 Resolution|--- |RAWHIDE
   Doc Type|--- |If docs needed, set a value
   Fixed In Version||perl-TAP-Formatter-HTML-0.1
   ||3-1.fc39
 Status|NEW |CLOSED
Last Closed||2023-07-26 14:18:41



--- Comment #2 from Paul Howarth  ---
Already built in Rawhide


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202226782%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

[Bug 2224929] perl-Tree-1.16 is available

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

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




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2224929
___
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: Flock CFP: Language SIGs discussion

[Zbigniew Jędrzejewski-Szmek]

On Wed, Jul 05, 2023 at 01:39:47PM +0200, Fabio Valentini wrote:
> On Wed, Jul 5, 2023 at 8:23 AM Jens-Ulrik Petersen  
> wrote:
> >
> > I have submitted a Flock proposal to have a common discussion session for 
> > (modern) Language SIGs. I think for this to be successful we need 
> > representatives from various Language SIGs to be there (Rust, Haskell, 
> > OCaml, Golang and of course Python and older ecosystems like Perl, R, TeX 
> > come to mind immediately - surely there are more). Language packaging 
> > experts are also welcome of course independently or affiliated to one or 
> > more language SIGs. Of course I also hope there will be broad attendance by 
> > interested contributors.
> 
> This is a great idea, but I don't think any Rust SIG members will be
> at Flock this year :(

I'll be there and I hope to join the session.

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

[Bug 2226087] perl-Parallel-Prefork: FTBFS in Fedora rawhide/f39

[bugzilla]

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



--- Comment #6 from Ralf Corsepius  ---
(In reply to Jitka Plesnikova from comment #5)
> I didn't find the source of failure. I just tried to re-run the build and it
> passed.

Thanks.

My guess: Fedora's befamed notorious s390x buildsys (in-) stability:

cf. https://kojipkgs.fedoraproject.org//work/tasks/8362/103658362/hw_info.log
CPU info:
Architecture:s390x

I've seen too many of these s390x build-failures, to waste more words.


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202226087%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

[Bug 2226782] New: perl-TAP-Formatter-HTML-0.13 is available

[bugzilla]

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

Bug ID: 2226782
   Summary: perl-TAP-Formatter-HTML-0.13 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-TAP-Formatter-HTML
  Keywords: FutureFeature, Triaged
  Assignee: p...@city-fan.org
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: p...@city-fan.org, perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 0.13
Upstream release that is considered latest: 0.13
Current version/release in rawhide: 0.12-1.fc39
URL: http://search.cpan.org/dist/TAP-Formatter-HTML/

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://docs.fedoraproject.org/en-US/package-maintainers/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/3358/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/perl-TAP-Formatter-HTML


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202226782%23c0
___
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 2226782] perl-TAP-Formatter-HTML-0.13 is available

[bugzilla]

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



--- Comment #1 from Upstream Release Monitoring 
 ---
Scratch build failed. Details below:

BuilderException: Build failed:
Command '['git', 'commit', '-a', '-m', 'Update to 0.13 (#2226782)']' returned
non-zero exit status 1.

StdOut:
On branch rawhide
Your branch is up to date with 'origin/rawhide'.

nothing to commit, working tree clean


Traceback:
  File
"/usr/local/lib/python3.11/site-packages/hotness/use_cases/package_scratch_build_use_case.py",
line 56, in build
result = self.builder.build(request.package, request.opts)
 ^
  File "/usr/local/lib/python3.11/site-packages/hotness/builders/koji.py", line
185, in build
raise BuilderException(

If you think this issue is caused by some bug in the-new-hotness, please report
it on the-new-hotness issue tracker:
https://github.com/fedora-infra/the-new-hotness/issues


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202226782%23c1
___
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: F39 Change Proposal: Enable fwupd-refresh.timer by default on IoT, CoreOS & Server Editions (Self-Contained)

[Solomon Peachy via devel]

On Wed, Jul 26, 2023 at 11:48:36AM +0300, Alexander Ploumistos wrote:
> That would require people volunteering to potentially brick their
> machines in order to test the updates. If something goes wrong, the
> equipment (and the knowledge) necessary to reprogram a chip is rather
> scarce. I'm afraid the way forward is to _convince_ vendors to make
> use of the service, starting with those who already have test
> accounts.

I've been debating contributing some code to fwupd to handle several 
different vendors' families of printers, but there's a snowball's chance 
in hell that said vendors will ever embrace lvfs given that they 
steadfastly refuse to publicly acknowledge that Linux exists, despite 
invariably selling a Linux-based print server appliance of some sort.

 - Solomon
-- 
Solomon Peachypizza at shaftnet dot org (email)
  @pizza:shaftnet dot org   (matrix)
Dowling Park, FL  speachy (libra.chat)


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: libarrow (Apache Arrow) soname bump in Rawhide

[Kaleb Keithley]

The update to 13.0.0 is on hold due to FTBFS on s390x.

Waiting for a fix from the devs.

On Thu, Jul 20, 2023 at 10:06 AM Kaleb Keithley  wrote:

>
>
> On Mon, May 1, 2023 at 8:01 AM Kaleb Keithley  wrote:
>
>>
>>
>> Now Apache Arrow 12.0.0 has been released.
>>
>> Rebase landing soon in Rawhide.
>>
>
> Apache Arrow (libarrow) 13.0.0 has been released.
>
> At least within Fedora, only Ceph (ceph-common, ceph-radosgw, ceph-test,
> librgw2) depends on libarrow.
>
> I know of a couple of external consumers that are using it.
>
> Rebase landing shortly in Rawhide.
>
> --
>
> Kaleb
>


-- 

Kaleb
___
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: Macros in side-tag

[Zbigniew Jędrzejewski-Szmek]

On Wed, Jul 26, 2023 at 03:45:32PM +0200, Vít Ondruch wrote:
> 
> Dne 26. 07. 23 v 13:13 Zbigniew Jędrzejewski-Szmek napsal(a):
> > On Wed, Jul 26, 2023 at 12:30:00PM +0200, Vít Ondruch wrote:
> > > Hi,
> > > 
> > > Koji has grown new functionality to enable setting macros in side-tag:
> > > 
> > > https://pagure.io/releng/issue/11254
> > > 
> > > I have asked FeSCo to approve to use them:
> > > 
> > > https://pagure.io/fesco/issue/3046
> > > 
> > > My immediate use case is to improve the package bootstrapping experience.
> > I made a proposal in the ticket to allowlist %_with_bootstrap.
> > 
> > I was wondering though: what about other macros? Would/should users
> > set %_with_tests or other macros in this way?
> 
> 
> Thinking about this, we could probably update `%{dist}` macro and leverage
> similar mechanism for mass rebuilds. Saving all the commits which don't
> provide too much value IMHO.

Commits for mess rebuilds are already empty (when %autorelease and
%autochangelog are used). But I think we do want the information that
the package was rebuilt for the mess rebuild to be present in the
changelog, so we need the empty commit.

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

Re: F39 Change Proposal: Enable fwupd-refresh.timer by default on IoT, CoreOS & Server Editions (Self-Contained)

[Solomon Peachy via devel]

On Wed, Jul 26, 2023 at 09:45:13AM +0200, Ralf Corsépius wrote:
> It could be "my bubble", but for me, in all these fwupd is around, it has
> never, ever worked on any piece of HW for me.

Most of the stuff I have that is updated through fwupd are peripherals 
[1] that are independent of the system vendor.

That said, my two primary systems are a Lenovo laptop and an HP 
workstation that are fully supported by fwupd/lvfs, and the UEFI dbx 
stuff works on all of the remaining physical systems (including servers) 
I still have deployed.  Things will only get better from here.

[1] Off the top of my head: Logitech wireless stuff, Jabra conference 
speaker, synaptics fingerprint sensor, (Samsung?) NVME storage, and 
probably more..

 - Solomon
-- 
Solomon Peachypizza at shaftnet dot org (email)
  @pizza:shaftnet dot org   (matrix)
Dowling Park, FL  speachy (libra.chat)


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: Unannounced soname bump: libotf

[Michal Schorm]

My apologies !
I built the new version when cleaning old PRs and I failed to check
for the soname bump.
Thank you for cleaning up after me. I will try my best to remember to
check it next time.

Michal

--

Michal Schorm
Software Engineer
Core Services - Databases Team
Red Hat

--

On Wed, Jul 26, 2023 at 3:02 PM Scott Talbert  wrote:
>
> On Tue, 25 Jul 2023, Scott Talbert wrote:
>
> >> libotf was just bumped from libotf.so.0 to libotf.so.1.
> >>
> >> $ dnf repoquery --whatrequires 'libotf.so.0()(64bit)' --disablerepo='*'
> >> --enablerepo=rawhide
> >> emacs-1:28.2-6.fc39.x86_64
> >> emacs-lucid-1:28.2-6.fc39.x86_64
> >> libotf-devel-0:0.9.13-22.fc38.x86_64
> >> m17n-lib-tools-0:1.8.2-1.fc39.x86_64
> >>
> >> Please announce soname bumps in advance and coordinate rebuilds in side
> >> tags. :)
> >
> > It looks like m17n-lib needs to be rebuilt first and then emacs can be
> > rebuilt.
> >
> > @mfabian, can you please take care of m17n-lib?
>
> Thanks @besser82 for taking care of these!
>
> Scott
>
___
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: Macros in side-tag

[Vít Ondruch]

Dne 26. 07. 23 v 13:13 Zbigniew Jędrzejewski-Szmek napsal(a):

On Wed, Jul 26, 2023 at 12:30:00PM +0200, Vít Ondruch wrote:

Hi,

Koji has grown new functionality to enable setting macros in side-tag:

https://pagure.io/releng/issue/11254

I have asked FeSCo to approve to use them:

https://pagure.io/fesco/issue/3046

My immediate use case is to improve the package bootstrapping experience.

I made a proposal in the ticket to allowlist %_with_bootstrap.

I was wondering though: what about other macros? Would/should users
set %_with_tests or other macros in this way?



Thinking about this, we could probably update `%{dist}` macro and 
leverage similar mechanism for mass rebuilds. Saving all the commits 
which don't provide too much value IMHO.



Vít




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


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

Re: Unannounced soname bump: libotf

[Scott Talbert]

On Tue, 25 Jul 2023, Scott Talbert wrote:


libotf was just bumped from libotf.so.0 to libotf.so.1.

$ dnf repoquery --whatrequires 'libotf.so.0()(64bit)' --disablerepo='*' 
--enablerepo=rawhide

emacs-1:28.2-6.fc39.x86_64
emacs-lucid-1:28.2-6.fc39.x86_64
libotf-devel-0:0.9.13-22.fc38.x86_64
m17n-lib-tools-0:1.8.2-1.fc39.x86_64

Please announce soname bumps in advance and coordinate rebuilds in side 
tags. :)


It looks like m17n-lib needs to be rebuilt first and then emacs can be 
rebuilt.


@mfabian, can you please take care of m17n-lib?


Thanks @besser82 for taking care of these!

Scott
___
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: Flock CFP: Language SIGs discussion

[Jens-Ulrik Petersen]

On Thu, Jul 13, 2023 at 6:11 PM Miroslav Suchý  wrote:

> Dne 13. 07. 23 v 10:45 Florian Festi napsal(a):
> > As it is relevant for this meeting may be someone that attended my
> > workshop can give a 3 or 5 minute summary of the new Dynamic Spec
>
> I can volunteer. I was on your workshop and I will be at Flock.


Sure, thank you - that would be useful :up:

Jens
___
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: F39 Change Proposal: Enable fwupd-refresh.timer by default on IoT, CoreOS & Server Editions (Self-Contained)

[Neal Gompa]

On Wed, Jul 26, 2023 at 8:40 AM Chris Adams  wrote:
>
> Once upon a time, Vitaly Zaitsev  said:
> > On 26/07/2023 08:48, Dominik 'Rathann' Mierzejewski wrote:
> > >Define small. 
> >
> > Only Dell, HP and Lenovo laptops are fully supported:
> > https://fwupd.org/lvfs/devices/
> >
> > fwupd is a great tool on laptops but completely useless on desktops
> > since no motherboard vendors support it.
>
> It also works on Dell and I think HP desktops... which represent a
> significant chunk of the desktop PC market.

Framework is in the process of onboarding its firmware updates through
LVFS: https://community.frame.work/t/framework-firmware-on-the-lvfs/4466/14

Star Labs offers firmware through LVFS:
https://us.starlabs.systems/pages/why-choose-us

System76 offers firmware through LVFS: https://fwupd.org/lvfs/vendors/#system76

I don't know the state of TUXEDO Computers or SLIMBOOK for LVFS, but
both are listed as having test accounts on LVFS.

So there's a decent amount of adoption of LVFS even by Linux laptop vendors.



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

[Bug 2226087] perl-Parallel-Prefork: FTBFS in Fedora rawhide/f39

[bugzilla]

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



--- Comment #5 from Jitka Plesnikova  ---
This error is in build.log:

#   Failed test 'wait_all_children does not block'
#   at t/07-wait-all-children-does-not-block.t line 22.
# Looks like you failed 1 test of 1.
t/07-wait-all-children-does-not-block.t .. 
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/1 subtests 

I didn't find the source of failure. I just tried to re-run the build and it
passed.
It is not  possible to reproduce the failure now.


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202226087%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

Re: Flock CFP: Language SIGs discussion

[Jens-Ulrik Petersen]

On Fri, Jul 14, 2023 at 12:56 AM Ron Olson  wrote:

> There isn’t a SIG, and I don’t know if there’s any interest really, but
> I’d be happy to tell my tales of packaging Swift for Fedora. :\
>

Sure, such perspectives are definitely also welcome - this will be a broad
discussion.
In many cases the hurdles are even bigger with the newest developing
languages, where typically one finds that even the core/compiler's
buildsystem etc even does not cater well to distro needs in my experience.


Btw this cross-SIG community roundtable discussion has been scheduled

for the first morning and I'm really looking forward to a good vigorous
conversation with broad participation.
Do reach out to me by reply or chat if you want to help out and be more
involved.

Jens
___
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: F39 Change Proposal: Enable fwupd-refresh.timer by default on IoT, CoreOS & Server Editions (Self-Contained)

[Chris Adams]

Once upon a time, Vitaly Zaitsev  said:
> On 26/07/2023 08:48, Dominik 'Rathann' Mierzejewski wrote:
> >Define small. 
> 
> Only Dell, HP and Lenovo laptops are fully supported:
> https://fwupd.org/lvfs/devices/
> 
> fwupd is a great tool on laptops but completely useless on desktops
> since no motherboard vendors support it.

It also works on Dell and I think HP desktops... which represent a
significant chunk of the desktop PC market.
-- 
Chris Adams 
___
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: compilation of vdr-epgfixer on rawhide fails

[Martin Gansser]

i only changed the position of %make_install in the spec file [1], now it 
builds [2] again on rawhide.

[1] 
https://src.fedoraproject.org/rpms/vdr-epgfixer/blob/rawhide/f/vdr-epgfixer.spec

[2] https://koji.fedoraproject.org/koji/taskinfo?taskID=103947222

Regards
Martin
___
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: compilation of vdr-epgfixer on rawhide fails

[Yanko Kaneti]

Hello,

On Wed, 2023-07-26 at 08:36 +, Martin Gansser wrote:
> Hi,
> 
> the compilation of the package vdr-epgfixer fails on rawhide with the message 
> [1]
> ...
> install -D libvdr-epgfixer.so 
> /builddir/build/BUILDROOT/vdr-epgfixer-0.3.1-26.20180416git354f28b.fc39.x86_64/usr/lib64/vdr/libvdr-epgfixer.so.2.6.3
> install -D -m644 po/fi_FI.mo 
> /builddir/build/BUILDROOT/vdr-epgfixer-0.3.1-26.20180416git354f28b.fc39.x86_64/usr/share/locale/fi_FI/LC_MESSAGES/vdr-epgfixer.mo
> install -D -m644 po/pl_PL.mo 
> /builddir/build/BUILDROOT/vdr-epgfixer-0.3.1-26.20180416git354f28b.fc39.x86_64/usr/share/locale/pl_PL/LC_MESSAGES/vdr-epgfixer.mo
> cp: not replacing 
> '/builddir/build/BUILDROOT/vdr-epgfixer-0.3.1-26.20180416git354f28b.fc39.x86_64/etc/vdr/plugins/epgfixer/blacklist.conf'
> cp: not replacing 
> '/builddir/build/BUILDROOT/vdr-epgfixer-0.3.1-26.20180416git354f28b.fc39.x86_64/etc/vdr/plugins/epgfixer/charset.conf'
> cp: not replacing 
> '/builddir/build/BUILDROOT/vdr-epgfixer-0.3.1-26.20180416git354f28b.fc39.x86_64/etc/vdr/plugins/epgfixer/epgclone.conf'
> cp: not replacing 
> '/builddir/build/BUILDROOT/vdr-epgfixer-0.3.1-26.20180416git354f28b.fc39.x86_64/etc/vdr/plugins/epgfixer/regexp.conf'
> make: *** [Makefile:132: install-conf] Error 1
> 
> How can i fix this ?
> [1] https://kojipkgs.fedoraproject.org//work/tasks/2669/103932669/build.log

This looks to be caused by the recent coreutils behavior change for 
cp --no-clobber (-n)   which now errors out on existing target.

cp -pn is in the project Makefile and called on %make_install

One way to replicate the old --no-clobber behavior is to change the 
-n to --update=none

--
Yanko


___
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 2226087] perl-Parallel-Prefork: FTBFS in Fedora rawhide/f39

[bugzilla]

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



--- Comment #4 from Ralf Corsepius  ---
Jitka, what was the cause of this FTBFS?

I haven't a chance to look into this, and you closed this BZ without giving any
rationale.


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202226087%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

Re: Macros in side-tag

[Vít Ondruch]

Dne 26. 07. 23 v 13:13 Zbigniew Jędrzejewski-Szmek napsal(a):

On Wed, Jul 26, 2023 at 12:30:00PM +0200, Vít Ondruch wrote:

Hi,

Koji has grown new functionality to enable setting macros in side-tag:

https://pagure.io/releng/issue/11254

I have asked FeSCo to approve to use them:

https://pagure.io/fesco/issue/3046

My immediate use case is to improve the package bootstrapping experience.

I made a proposal in the ticket to allowlist %_with_bootstrap.

I was wondering though: what about other macros? Would/should users
set %_with_tests or other macros in this way?



I think that Perl folks are using something aka %perl_bootstrap. Not 
sure if this is just for historic reasons and they could eventually 
migrate to regular bootstrap method.


Other than that, I can imagine this being useful for use cases such as 
SCL / modularity. But I guess these are out of scope for the moment.


So yeah, I also wonder what other macros folks would find useful.


Vít




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

[Bug 2226087] perl-Parallel-Prefork: FTBFS in Fedora rawhide/f39

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 CC||jples...@redhat.com
   Doc Type|--- |If docs needed, set a value
 Resolution|--- |RAWHIDE
 Status|NEW |CLOSED
   Fixed In Version||perl-Parallel-Prefork-0.18-
   ||23.fc39
Last Closed||2023-07-26 11:38:27




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2226087
___
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 2203073] perl-PPI-Tester: FTBFS: No package found for: perl(inc::Module::Install::DSL) >= 0.86

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|NEW |CLOSED
 Resolution|--- |RAWHIDE
   Fixed In Version||perl-PPI-Tester-0.15-28.fc3
   ||9
Last Closed||2023-07-26 11:18:51




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2203073
___
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 2196756] perl-Class-Autouse-2.01-34.fc39 FTBFS: Can't locate inc/Module/Install/DSL.pm

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

   Fixed In Version||perl-Class-Autouse-2.01-36.
   ||fc39
 Status|NEW |CLOSED
 Resolution|--- |RAWHIDE
Last Closed||2023-07-26 11:17:19




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2196756
___
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: Macros in side-tag

[Zbigniew Jędrzejewski-Szmek]

On Wed, Jul 26, 2023 at 12:30:00PM +0200, Vít Ondruch wrote:
> Hi,
> 
> Koji has grown new functionality to enable setting macros in side-tag:
> 
> https://pagure.io/releng/issue/11254
> 
> I have asked FeSCo to approve to use them:
> 
> https://pagure.io/fesco/issue/3046
> 
> My immediate use case is to improve the package bootstrapping experience.

I made a proposal in the ticket to allowlist %_with_bootstrap.

I was wondering though: what about other macros? Would/should users
set %_with_tests or other macros in this way?

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

Re: compilation of vdr-epgfixer on rawhide fails

[Martin Gansser]

no changes on the spec file.
issue only happens on rawhide, see f38 logfile
https://koji.fedoraproject.org/koji/taskinfo?taskID=103942043

Regards
Martin
___
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 2218904] TRIAGE-CVE-2023-31484 perl: CPAN.pm before 2.35 does not verify TLS certificates when downloading distributions over HTTPS [fedora-all]

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

  Component|perl|perl-CPAN




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2218904
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[rpms/perl-File-MimeInfo] PR #3: Add gating.yaml file

[Jitka Plesnikova]

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

Merged pull-request:

``
Add gating.yaml file
``

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

[rpms/perl-DateTime-Format-ISO8601] PR #3: Add gating.yaml file

[Michal Josef Špaček]

mspacek merged a pull-request against the project: 
`perl-DateTime-Format-ISO8601` that you are following.

Merged pull-request:

``
Add gating.yaml file
``

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

[rpms/perl-Lingua-EN-Syllable] PR #5: Add gating.yaml file

[Michal Josef Špaček]

mspacek merged a pull-request against the project: `perl-Lingua-EN-Syllable` 
that you are following.

Merged pull-request:

``
Add gating.yaml file
``

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

[rpms/perl-Lingua-EN-Fathom] PR #6: Add gating.yaml file

[Michal Josef Špaček]

mspacek merged a pull-request against the project: `perl-Lingua-EN-Fathom` that 
you are following.

Merged pull-request:

``
Add gating.yaml file
``

https://src.fedoraproject.org/rpms/perl-Lingua-EN-Fathom/pull-request/6
___
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 2225676] perl-IO-Compress-2.206 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #1 from Fedora Update System  ---
FEDORA-2023-923d7497c3 has been submitted as an update to Fedora 39.
https://bodhi.fedoraproject.org/updates/FEDORA-2023-923d7497c3


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202225676%23c1
___
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: packager-dashboard not updating koschei build status

[Mikel Olasagasti]

Thanks František, works fine now!

Hau idatzi du Frantisek Zatloukal (fzatl...@redhat.com) erabiltzaileak
(2023 uzt. 25(a), ar. (18:59)):
>
> Hey,
>
> Thanks for raising the issue. It has been addressed and all the dashboards 
> should now contain up2date data from koschei.
>
> Longer answer: The problem was the enablement of EPEL 9 Next in koschei, 
> oraculum (the backend for the Packager Dashboard) isn't ready for these kinds 
> of releases and I had to add filtering of it: 
> https://pagure.io/fedora-qa/oraculum/c/aba10ef932ba894c2000851f4028f4402d6bbcdc?branch=master
>  .
>
> On Tue, Jul 25, 2023 at 12:54 AM Mikel Olasagasti  
> wrote:
>>
>> Hi all,
>>
>> I've multiple reports of FTBFS in the packager-dashboard, but I can
>> see many of the packages are being built fine in koschei/koji.
>>
>> Is there a known issue on refreshing koschei data?
>>
>> Kind regards,
>> Mikel
>> ___
>> 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
>
>
>
> --
>
> 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

Macros in side-tag

[Vít Ondruch]

Hi,

Koji has grown new functionality to enable setting macros in side-tag:

https://pagure.io/releng/issue/11254

I have asked FeSCo to approve to use them:

https://pagure.io/fesco/issue/3046

My immediate use case is to improve the package bootstrapping experience.


Vít



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

[rpms/perl-LDAP] PR #2: Add gating.yaml file

[Jitka Plesnikova]

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

Merged pull-request:

``
Add gating.yaml file
``

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

[Bug 2224551] Upgrade perl-Net-OpenSSH to 0.84

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Resolution|--- |ERRATA
 Status|MODIFIED|CLOSED
   Fixed In Version||perl-Net-OpenSSH-0.84-1.fc3
   ||9
Last Closed||2023-07-26 10:27:02



--- Comment #2 from Fedora Update System  ---
FEDORA-2023-828e926140 has been pushed to the Fedora 39 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=2224551

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202224551%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

[Bug 2224551] Upgrade perl-Net-OpenSSH to 0.84

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #1 from Fedora Update System  ---
FEDORA-2023-828e926140 has been submitted as an update to Fedora 39.
https://bodhi.fedoraproject.org/updates/FEDORA-2023-828e926140


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202224551%23c1
___
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 2224551] Upgrade perl-Net-OpenSSH to 0.84

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

   Assignee|steve.tray...@cern.ch   |jples...@redhat.com
 Status|NEW |ASSIGNED




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2224551
___
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: Potential changes to systemd RPM macros

[Andrea Bolognani]

On Wed, Jul 26, 2023 at 07:15:42AM +, Zbigniew Jędrzejewski-Szmek wrote:
> On Tue, Jul 25, 2023 at 10:45:30AM -0400, Andrea Bolognani wrote:
> > On Tue, Jul 25, 2023 at 10:51:04AM +, Zbigniew Jędrzejewski-Szmek wrote:
> > > I think it'd be more effiecient to go with the (slightly ugly, no
> > > disagreement here) seven line %trigger scriptlet. And and then work
> > > with upstream to implement a generic solution that can be used by all
> > > packages. It seems to me that the work put into implementing a custom
> > > solution in libvirt would be wasted if you want to work with upstream
> > > on a completely different general solution soon after.
> >
> > Another way to look at it is that I *already* put all that work in,
> > and the solution I've proposed for libvirt has been tested quite
> > thoroughly in a number of install and upgrade scenarios. In order to
> > adopt the %trigger based solution, I will have to spend more time on
> > developing and testing another implementation.
>
> That's fine. I only saw some links to emails, and it didn't know that
> those have already been applied and tested. My goal was to minimize
> overall effort, not to increase it ;)

They've been tested and, as of yesterday, fully reviewed, but not yet
applied.

If I understand correctly and you have no strong objections to them
being merged, I think I will stick to my original plan of addressing
the immediate issue in libvirt by pushing those patches, and work on
a more long-term solution that lives in systemd as a follow-up
instead of investigating the %trigger route further.

The lack of strong objections on the Fedora side will hopefully
assuage Daniel's concerns as well.

> > I feel that having packages call systemctl directly instead of going
> > through the %systemd_* macros is an anti-pattern that shouldn't be
> > encouraged.
>
> That's a valid point.
>
> > The current set of macros already includes both %systemd_postun and
> > %systemd_postun_with_restart, so adding %systemd_postun_with_reload
> > or something along those lines doesn't seem like a stretch.
>
> → https://github.com/systemd/systemd/pull/28521

Neat!

-- 
Andrea Bolognani / Red Hat / Virtualization
___
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: F39 Change Proposal: Anaconda WebUI for Fedora Workstation by default (System-Wide)

[Jiri Konecny]

Dne 02. 07. 23 v 23:54 Demi Marie Obenour napsal(a):

On 6/26/23 12:00, Aoife Moloney wrote:

https://fedoraproject.org/wiki/Changes/AnacondaWebUIforFedoraWorkstation

This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive
community feedback. This proposal will only be implemented if approved
by the Fedora Engineering Steering Committee.


== Summary ==
The new PatternFly-based UI has been developed by the Anaconda team
for some time now and we would like to make it available for users of
Fedora to enhance and modernize installation experience. As the first
step in this user adoption process, we are targeting Fedora
Workstation only.

== Owner ==

* Name: Anaconda team ([[User:jkonecny| Jiří Konečný]])

* Email: jkone...@redhat.com
* Name: Fedora Workstation SIG
* Email: desk...@lists.fedoraproject.org


== Detailed Description ==
The Anaconda team has been working on a new web-based UI for the OS
installer for some time. We would like to give users the fruits of our
work and get feedback so that we know what we need to improve or where
we should focus.
To make the adoption as painless as possible, the Fedora Workstation
was chosen as the first target so we have better control over the
environment and can have a focus. Also, Fedora Workstation has a
smaller featureset than other installation media. The adoption for the
other media later is planned too, but the exact date will be based on
feedback and our capacity allowance.

What is the reason for using a web-based UI instead of continuing to use
GTK?

Hi,

the reasons are mainly these:
- faster development (we don't have to reboot the machine for each 
change but just reload a page)
- great CI support from the cockpit team (pixel tests support and we use 
their test suite with their infrastructure)
- consistency with the other projects who use Pattern Fly (mainly around 
RHEL but not only) as Cockpit, Image Builder and more

- possibility to share modules and code with the Cockpit project
- great support from the Cockpit team
- great support from the Pattern Fly team

In overall these benefits should allow us better cooperation between 
teams, better integration and more stable product at the end.


Best Regards,
Jirka
___
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: Fedora 39 Mass Rebuild

[Zbigniew Jędrzejewski-Szmek]

On Tue, Jul 25, 2023 at 05:24:20PM -0400, Ben Cotton wrote:
> On Tue, Jul 25, 2023 at 3:58 PM Fabio Valentini  wrote:
> >
> > As far as I can tell, the toolchain proposal was announced on the devel / 
> > devel-announce lists on July 7 but never submitted to FESCo for a vote. 
> > Looks like the process broke down somewhere along the way.
> 
> I think it was actually a couple of days before that, but no matter.
> In either case it was announced more than a week after it was
> submitted (which happened to be the date of the deadline). So the
> problem is two-fold:
> 
> 1. It sat in "ChangeReadyForWrangler" for a week during a rather
> time-critical part of the cycle
> 2. It never made it to FESCo
> 
> I could be salty about this, but I'll refrain. The point is that
> altering the schedule wouldn't make a difference here because the
> schedule isn't the problem. It's that there's not someone whose actual
> job is wrangling Change proposals. amoloney has done a great job
> picking up many of my former duties while also doing her full time
> job, but as that sentence implies, there are capacity issues. Of
> course, earlier submission is better when possible but I don't know if
> it was possible in this case and it's not clear it would have helped
> this specific issue.

I submitted
https://pagure.io/fesco/issue/3043 Change: Migrate NetworkManager ifcfg 
profiles to keyfile 
https://pagure.io/fesco/issue/3044 Change: IBus 1.5.29
https://pagure.io/fesco/issue/3045 Change: GNU Toolchain Update (gcc 13.2, 
binutils 2.40, glibc 2.38, gdb 13.2)
to push things through fesco. But I did not very well, e.g. I didn't
update the categories in the wiki.

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

Re: compilation of vdr-epgfixer on rawhide fails

[Michael J Gruber]

Am Mi., 26. Juli 2023 um 10:36 Uhr schrieb Martin Gansser
:
>
> Hi,
>
> the compilation of the package vdr-epgfixer fails on rawhide with the message 
> [1]
> ...
> install -D libvdr-epgfixer.so 
> /builddir/build/BUILDROOT/vdr-epgfixer-0.3.1-26.20180416git354f28b.fc39.x86_64/usr/lib64/vdr/libvdr-epgfixer.so.2.6.3
> install -D -m644 po/fi_FI.mo 
> /builddir/build/BUILDROOT/vdr-epgfixer-0.3.1-26.20180416git354f28b.fc39.x86_64/usr/share/locale/fi_FI/LC_MESSAGES/vdr-epgfixer.mo
> install -D -m644 po/pl_PL.mo 
> /builddir/build/BUILDROOT/vdr-epgfixer-0.3.1-26.20180416git354f28b.fc39.x86_64/usr/share/locale/pl_PL/LC_MESSAGES/vdr-epgfixer.mo
> cp: not replacing 
> '/builddir/build/BUILDROOT/vdr-epgfixer-0.3.1-26.20180416git354f28b.fc39.x86_64/etc/vdr/plugins/epgfixer/blacklist.conf'
> cp: not replacing 
> '/builddir/build/BUILDROOT/vdr-epgfixer-0.3.1-26.20180416git354f28b.fc39.x86_64/etc/vdr/plugins/epgfixer/charset.conf'
> cp: not replacing 
> '/builddir/build/BUILDROOT/vdr-epgfixer-0.3.1-26.20180416git354f28b.fc39.x86_64/etc/vdr/plugins/epgfixer/epgclone.conf'
> cp: not replacing 
> '/builddir/build/BUILDROOT/vdr-epgfixer-0.3.1-26.20180416git354f28b.fc39.x86_64/etc/vdr/plugins/epgfixer/regexp.conf'
> make: *** [Makefile:132: install-conf] Error 1
>
> How can i fix this ?
>
> [1] https://kojipkgs.fedoraproject.org//work/tasks/2669/103932669/build.log

You are installing the same files twice: once manually (install), once
via make (%make_install).

Was there a spec or package change, or is it the underlying tooling
which changed? Does this happen on rawhide only or on all releases?

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

[rpms/perl-Net-Server] PR #7: Add gating.yaml file

[Michal Josef Špaček]

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

Merged pull-request:

``
Add gating.yaml file
``

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

[rpms/perl-DateTime-Format-ISO8601] PR #3: Add gating.yaml file

[Michal Josef Špaček]

mspacek opened a new pull-request against the project: 
`perl-DateTime-Format-ISO8601` that you are following:
``
Add gating.yaml file
``

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

[rpms/perl-File-MimeInfo] PR #3: Add gating.yaml file

[Michal Josef Špaček]

mspacek opened a new pull-request against the project: `perl-File-MimeInfo` 
that you are following:
``
Add gating.yaml file
``

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

[rpms/perl-LDAP] PR #2: Add gating.yaml file

[Michal Josef Špaček]

mspacek opened a new pull-request against the project: `perl-LDAP` that you are 
following:
``
Add gating.yaml file
``

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

[rpms/perl-Lingua-EN-Syllable] PR #5: Add gating.yaml file

[Michal Josef Špaček]

mspacek opened a new pull-request against the project: 
`perl-Lingua-EN-Syllable` that you are following:
``
Add gating.yaml file
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Lingua-EN-Syllable/pull-request/5
___
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 2225678] perl-IO-Socket-IP-0.42 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version||perl-IO-Socket-IP-0.42-1.fc
   ||39
 Status|MODIFIED|CLOSED
 Resolution|--- |ERRATA
Last Closed||2023-07-26 09:27:01



--- Comment #2 from Fedora Update System  ---
FEDORA-2023-2256370c61 has been pushed to the Fedora 39 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=2225678

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202225678%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

[rpms/perl-Lingua-EN-Fathom] PR #6: Add gating.yaml file

[Michal Josef Špaček]

mspacek opened a new pull-request against the project: `perl-Lingua-EN-Fathom` 
that you are following:
``
Add gating.yaml file
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Lingua-EN-Fathom/pull-request/6
___
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: F39 Change Proposal: Enable fwupd-refresh.timer by default on IoT, CoreOS & Server Editions (Self-Contained)

[Alexander Ploumistos]

On Wed, Jul 26, 2023 at 12:14 PM Vitaly Zaitsev via devel
 wrote:
>
> On 26/07/2023 11:04, Dominik 'Rathann' Mierzejewski wrote:
> > You could, for example, buy a supported Logitech
> > Receiver
>
> I don't recommend anyone to buy this proprietary hardware:
>
> > The vulnerabilities allow attackers to sniff on keyboard traffic, but also 
> > inject keystrokes (even into dongles not connected to a wireless keyboard) 
> > and take over the computer to which a dongle has been connected.
> https://www.zdnet.com/article/logitech-wireless-usb-dongles-vulnerable-to-new-hijacking-flaws/

And thanks to fwupd and Logitech's embracing it, we had the fix in a
very short time.

What Dominik wrote would apply e.g. for an NVMe replacement drive from
Kingston or Samsung (proprietary hardware too, it's a shocker).
___
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

[rpms/perl-Net-Server] PR #7: Add gating.yaml file

[Michal Josef Špaček]

mspacek opened a new pull-request against the project: `perl-Net-Server` that 
you are following:
``
Add gating.yaml file
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Net-Server/pull-request/7
___
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: F39 Change Proposal: Enable fwupd-refresh.timer by default on IoT, CoreOS & Server Editions (Self-Contained)

[Vitaly Zaitsev via devel]

On 26/07/2023 11:04, Dominik 'Rathann' Mierzejewski wrote:

You could, for example, buy a supported Logitech
Receiver


I don't recommend anyone to buy this proprietary hardware:


The vulnerabilities allow attackers to sniff on keyboard traffic, but also 
inject keystrokes (even into dongles not connected to a wireless keyboard) and 
take over the computer to which a dongle has been connected.

https://www.zdnet.com/article/logitech-wireless-usb-dongles-vulnerable-to-new-hijacking-flaws/

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

Re: F39 Change Proposal: Enable fwupd-refresh.timer by default on IoT, CoreOS & Server Editions (Self-Contained)

[Dominik 'Rathann' Mierzejewski]

On Wednesday, 26 July 2023 at 10:49, Vitaly Zaitsev via devel wrote:
> On 26/07/2023 10:32, Daniel P. Berrangé wrote:
> > Those devices which do support fwupd have a large enough market share
> > that it is justifiable to enable it, even if there are many machines
> > which can't support it.
> 
> Maybe Anaconda should only enable it if the device is supported?
> 
> This information can be easily extracted from "fwupdmgr get-devices --json"
> output.

That only covers devices physically connected or otherwise available at
installation time. You could, for example, buy a supported Logitech
Receiver later and you wouldn't get firmware updates notification if
fwupdmgr-refresh was not enabled because no supported devices were found
at installation time.

Regards,
Dominik
-- 
Fedora   https://fedoraproject.org
There should be a science of discontent. People need hard times and
oppression to develop psychic muscles.
-- from "Collected Sayings of Muad'Dib" by the Princess Irulan
___
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: F39 Change Proposal: Enable fwupd-refresh.timer by default on IoT, CoreOS & Server Editions (Self-Contained)

[Vitaly Zaitsev via devel]

On 26/07/2023 10:32, Daniel P. Berrangé wrote:

Those devices which do support fwupd have a large enough market share
that it is justifiable to enable it, even if there are many machines
which can't support it.


Maybe Anaconda should only enable it if the device is supported?

This information can be easily extracted from "fwupdmgr get-devices 
--json" output.


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

Re: F39 Change Proposal: Enable fwupd-refresh.timer by default on IoT, CoreOS & Server Editions (Self-Contained)

[Alexander Ploumistos]

On Wed, Jul 26, 2023 at 10:59 AM Vitaly Zaitsev via devel
 wrote:
>
> Only Dell, HP and Lenovo laptops are fully supported:
> https://fwupd.org/lvfs/devices/

Not just laptops, desktops/workstations too. In the last six years,
I've had five different models provided by my employers and they were
all fully supported through fwupd.


> fwupd is a great tool on laptops but completely useless on desktops
> since no motherboard vendors support it.

While most custom-built computers don't get full UEFI/BIOS updates,
some hardware manufacturers provide firmware files for components used
by other vendors in their boards. It's a far cry from being on par
with windows, but calling it completely useless is not true either.


> Maybe fwupd should start packaging UEFI BIOS images for desktop
> motherboards without vendor assistance? Images in BIN format can be
> easily downloaded from official websites or extracted from MS Windows
> packages.

That would require people volunteering to potentially brick their
machines in order to test the updates. If something goes wrong, the
equipment (and the knowledge) necessary to reprogram a chip is rather
scarce. I'm afraid the way forward is to _convince_ vendors to make
use of the service, starting with those who already have test
accounts.
___
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: DNF5-5.0.1 has a stable API

[Sandro]

On 26-07-2023 09:35, Zbigniew Jędrzejewski-Szmek wrote:

On Wed, Jul 26, 2023 at 09:05:08AM +0200, Miroslav Suchý wrote:

Dne 24. 07. 23 v 22:43 Chuck Anderson napsal(a):

I propose "qzw".  It's so easy to type on a qwerty keyboard layout.


English qwerty layout. Because on Czech layout "z" and "y" are swapped. :)


Isn't that called qwertz?


But wait, there's more... :)

https://en.wikipedia.org/wiki/Keyboard_layout#Latin-script_keyboard_layouts

For the inquisitive mind.
___
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

compilation of vdr-epgfixer on rawhide fails

[Martin Gansser]

Hi,

the compilation of the package vdr-epgfixer fails on rawhide with the message 
[1]
...
install -D libvdr-epgfixer.so 
/builddir/build/BUILDROOT/vdr-epgfixer-0.3.1-26.20180416git354f28b.fc39.x86_64/usr/lib64/vdr/libvdr-epgfixer.so.2.6.3
install -D -m644 po/fi_FI.mo 
/builddir/build/BUILDROOT/vdr-epgfixer-0.3.1-26.20180416git354f28b.fc39.x86_64/usr/share/locale/fi_FI/LC_MESSAGES/vdr-epgfixer.mo
install -D -m644 po/pl_PL.mo 
/builddir/build/BUILDROOT/vdr-epgfixer-0.3.1-26.20180416git354f28b.fc39.x86_64/usr/share/locale/pl_PL/LC_MESSAGES/vdr-epgfixer.mo
cp: not replacing 
'/builddir/build/BUILDROOT/vdr-epgfixer-0.3.1-26.20180416git354f28b.fc39.x86_64/etc/vdr/plugins/epgfixer/blacklist.conf'
cp: not replacing 
'/builddir/build/BUILDROOT/vdr-epgfixer-0.3.1-26.20180416git354f28b.fc39.x86_64/etc/vdr/plugins/epgfixer/charset.conf'
cp: not replacing 
'/builddir/build/BUILDROOT/vdr-epgfixer-0.3.1-26.20180416git354f28b.fc39.x86_64/etc/vdr/plugins/epgfixer/epgclone.conf'
cp: not replacing 
'/builddir/build/BUILDROOT/vdr-epgfixer-0.3.1-26.20180416git354f28b.fc39.x86_64/etc/vdr/plugins/epgfixer/regexp.conf'
make: *** [Makefile:132: install-conf] Error 1

How can i fix this ?

[1] https://kojipkgs.fedoraproject.org//work/tasks/2669/103932669/build.log

Regards
Martin
___
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: F39 Change Proposal: Enable fwupd-refresh.timer by default on IoT, CoreOS & Server Editions (Self-Contained)

[Daniel P . Berrangé]

On Wed, Jul 26, 2023 at 09:59:26AM +0200, Vitaly Zaitsev via devel wrote:
> On 26/07/2023 08:48, Dominik 'Rathann' Mierzejewski wrote:
> > Define small. 
> 
> Only Dell, HP and Lenovo laptops are fully supported:
> https://fwupd.org/lvfs/devices/
> 
> fwupd is a great tool on laptops but completely useless on desktops since no
> motherboard vendors support it.

Merely enabling the fwupd to check for available updates has negligible
downside for machines which can't be updated. It'll merely find no updates
available, so the cost is an extra service running periodically and its
network download data usage.

Those devices which do support fwupd have a large enough market share
that it is justifiable to enable it, even if there are many machines
which can't support it.

With regards,
Daniel
-- 
|: https://berrange.com  -o-https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o-https://fstop138.berrange.com :|
|: https://entangle-photo.org-o-https://www.instagram.com/dberrange :|
___
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: F39 Change Proposal: Enable fwupd-refresh.timer by default on IoT, CoreOS & Server Editions (Self-Contained)

[Vitaly Zaitsev via devel]

On 26/07/2023 08:48, Dominik 'Rathann' Mierzejewski wrote:

Define small. 


Only Dell, HP and Lenovo laptops are fully supported:
https://fwupd.org/lvfs/devices/

fwupd is a great tool on laptops but completely useless on desktops 
since no motherboard vendors support it.


Maybe fwupd should start packaging UEFI BIOS images for desktop 
motherboards without vendor assistance? Images in BIN format can be 
easily downloaded from official websites or extracted from MS Windows 
packages.


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

[rpms/perl-SGMLSpm] PR #1: Update license to SPDX format

[Jitka Plesnikova]

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

Merged pull-request:

``
Update license to SPDX format
``

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

Re: F39 Change Proposal: Enable fwupd-refresh.timer by default on IoT, CoreOS & Server Editions (Self-Contained)

[Tomasz Torcz]

On Wed, Jul 26, 2023 at 09:45:13AM +0200, Ralf Corsépius wrote:
> 
> 
> Am 26.07.23 um 08:48 schrieb Dominik 'Rathann' Mierzejewski:
> > On Wednesday, 26 July 2023 at 06:23, Ralf Corsépius wrote:
> > > Am 23.07.23 um 00:39 schrieb Neal Gompa:
> > > > Actually, why wouldn't this be used everywhere?
> > > 
> > > Because fwupd only works on a small set of machines?
> > 
> > Define small. :)
> 
> Almost none?
> 
> It could be "my bubble", but for me, in all these fwupd is around, it has
> never, ever worked on any piece of HW for me.

  I had fwupdmgr successfuly update firmware on:
  - few ThinkPad laptops
  - ThinkStation desktop PC
  - Logi wireless mouse dongle
  - Lenovo USB-C docking station
  - Samsung NVMe drive

 fwupdmgr also have opt-in reporting 
(https://lvfs.readthedocs.io/en/latest/telemetry.html),
but I'm not aware if update success/failure statistics are reported anywhere.

-- 
Tomasz TorczTo co nierealne – tutaj jest normalne.
to...@pipebreaker.pl  Ziomale na życie mają tu patenty specjalne.
___
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: F39 proposal: Perl 5.38 (System-Wide Change proposal)

[Petr Pisar]

V Thu, Jul 20, 2023 at 12:34:30PM -, Xiaojie Chen napsal(a):
> I am interesting in the upgrading of perl.

As a Fedora user, simply upgrade your system to Fedora Rawhide, or to Fedora 39 
when it
it is released.

> Where can I find the detailed process of upgrading and building Perl,
> including the entire build steps,

.


> the list of built RPM packages,

.

> and the building order of Perl module packages?

That's complicated. We use tools from perl-Fedora-Rebuild RPM package. They
compute the order as the packages are being built. Logs and configuration from
the rebuild has jplesnik who performed the rebuild. Try asking her for them.

-- Petr


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: F39 Change Proposal: Enable fwupd-refresh.timer by default on IoT, CoreOS & Server Editions (Self-Contained)

[Ralf Corsépius]

Am 26.07.23 um 08:48 schrieb Dominik 'Rathann' Mierzejewski:

On Wednesday, 26 July 2023 at 06:23, Ralf Corsépius wrote:

Am 23.07.23 um 00:39 schrieb Neal Gompa:

Actually, why wouldn't this be used everywhere?


Because fwupd only works on a small set of machines?


Define small. :)


Almost none?

It could be "my bubble", but for me, in all these fwupd is around, it 
has never, ever worked on any piece of HW for me.


Ralf
___
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: DNF5-5.0.1 has a stable API

[Zbigniew Jędrzejewski-Szmek]

On Wed, Jul 26, 2023 at 09:05:08AM +0200, Miroslav Suchý wrote:
> Dne 24. 07. 23 v 22:43 Chuck Anderson napsal(a):
> > I propose "qzw".  It's so easy to type on a qwerty keyboard layout.
> 
> English qwerty layout. Because on Czech layout "z" and "y" are swapped. :)

Isn't that called qwertz?

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

[Bug 2225676] perl-IO-Compress-2.206 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2225676
Bug 2225676 depends on bug 2225675, which changed state.

Bug 2225675 Summary: perl-Compress-Raw-Bzip2-2.206 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2225675

   What|Removed |Added

 Status|MODIFIED|CLOSED
 Resolution|--- |ERRATA




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2225676
___
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 2225674] perl-Compress-Raw-Zlib-2.206 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Blocks||2225676





Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=2225676
[Bug 2225676] perl-IO-Compress-2.206 is available
-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2225674
___
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 2225675] perl-Compress-Raw-Bzip2-2.206 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Blocks||2225676





Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=2225676
[Bug 2225676] perl-IO-Compress-2.206 is available
-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2225675
___
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 2225676] perl-IO-Compress-2.206 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Depends On||2225674, 2225675





Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=2225674
[Bug 2225674] perl-Compress-Raw-Zlib-2.206 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2225675
[Bug 2225675] perl-Compress-Raw-Bzip2-2.206 is available
-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2225676
___
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 2225675] perl-Compress-Raw-Bzip2-2.206 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|CLOSED
   Fixed In Version||perl-Compress-Raw-Bzip2-2.2
   ||06-1.fc39
 Resolution|--- |ERRATA
Last Closed||2023-07-26 07:30:02



--- Comment #2 from Fedora Update System  ---
FEDORA-2023-6c04ecb215 has been pushed to the Fedora 39 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=2225675

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202225675%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

[Bug 2225674] perl-Compress-Raw-Zlib-2.206 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Resolution|--- |ERRATA
 Status|MODIFIED|CLOSED
   Fixed In Version||perl-Compress-Raw-Zlib-2.20
   ||6-1.fc39
Last Closed||2023-07-26 07:24:07



--- Comment #2 from Fedora Update System  ---
FEDORA-2023-197fc20eb8 has been pushed to the Fedora 39 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=2225674

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202225674%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