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

2022-11-25 Thread updates
The following Fedora EPEL 7 Security updates need testing:
 Age  URL
   1  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-10049c7b14   
libbsd-0.11.7-1.el7


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

nordugrid-arc6-6.17.0-1.el7

Details about builds:



 nordugrid-arc6-6.17.0-1.el7 (FEDORA-EPEL-2022-cf47663a67)
 Advanced Resource Connector Middleware

Update Information:

AEC 6.17.0

ChangeLog:

* Thu Nov 24 2022 Mattias Ellert  - 6.17.0-1
- Update to version 6.17.0


___
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


[Bug 2148577] New: perl-podlators-5.00 is available

2022-11-25 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2148577

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



Releases retrieved: 5.00
Upstream release that is considered latest: 5.00
Current version/release in rawhide: 4.14-489.fc37
URL: http://search.cpan.org/dist/podlators/

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


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


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


[Test-Announce] 2022-11-28 @ **16:00** UTC - Fedora QA Meeting

2022-11-25 Thread Adam Williamson
# Fedora Quality Assurance Meeting
# Date: 2022-11-28
# Time: **16:00** UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.libera.chat

Greetings testers!

It's time for a first meeting since Fedora 37 was released! Let's get
together to check in on 37 and 38.

Note that clocks have now gone back everywhere that does daylight
savings time, so the meeting will be at 16:00 UTC (I'm almost sure I
got this right this time). If your clocks changed a while back, the
meeting will be at the same local time as always. If your clocks didn't
change, the meeting will be an hour later in your local time than it
was during the summer.

If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.

Note, this may possibly be the last meeting of the year - we may cancel
the meetings in December as a lot of RHers will be on vacation and it's
a pretty slow time of year.

== Proposed Agenda Topics ==

1. Previous meeting follow-up
2. Fedora 37 review, Fedora 38 check-in
3. Test Day / community event status
4. Open floor
-- 
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net

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


Re: Web Assembly on Fedora: interested in a Fedora SIG to work on this?

2022-11-25 Thread Philip Rhoades via devel

Jun,


On 2022-11-26 03:41, Jun Aruga (he / him) wrote:

The Ruby new version 3.2.0 will start to support Web Assembly. It is
planned to release the official version next month.
https://www.ruby-lang.org/en/news/2022/11/11/ruby-3-2-0-preview3-released/
https://github.com/ruby/ruby/blob/master/wasm/README.md



Great news! - I will have a look at that - is there a ruby group with a 
mailing list or forum specifically for this work somewhere?




However, I had to build the necessary tools such as WASI-SDK and
wasmtime from the source to build Ruby as WebAssembly binaries at that
time.



I am not quite sure of level of difficulty of that but I will have a 
look anyway . .




Though I wrote about the situation on the email thread "Packaging a
cross-compilation environment (wasi-libc)" in the past.
I am looking forward to seeing the thrived RPM packages in the Web
Assembly! Thanks guys!



+1

P.
--
Philip Rhoades

PO Box 896
Cowra  NSW  2794
Australia
E-mail:  p...@pricom.com.au
___
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 2144551] Please branch and build perl-Parse-CPAN-Packages in epel9

2022-11-25 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2144551

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



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

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

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=2144551
___
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 2140480] perl-Dist-Zilla-6.029 is available

2022-11-25 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2140480

Upstream Release Monitoring  
changed:

   What|Removed |Added

Summary|perl-Dist-Zilla-6.028 is|perl-Dist-Zilla-6.029 is
   |available   |available



--- Comment #2 from Upstream Release Monitoring 
 ---
Releases retrieved: 6.029
Upstream release that is considered latest: 6.029
Current version/release in rawhide: 6.025-1.fc38
URL: http://search.cpan.org/dist/Dist-Zilla/

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


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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2140480
___
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: F38 proposal: Add Fedora Auto Firstboot Services to desktop variants (System-Wide Change proposal)

2022-11-25 Thread Dan Čermák
Hi,

On November 23, 2022 8:08:59 PM UTC, Ben Cotton  wrote:
>https://fedoraproject.org/wiki/Changes/AutoFirstBootServices
>
>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 ==
>Add {{package|fedora-autofirstboot}} to desktop variants to run a
>predetermined set of tasks on first boot after post installation,
>notably installing codecs and cleaning up installer packages from the
>installed system.
>
>== Owner ==
>* Name: [[User:Ngompa| Neal Gompa]]
>* Email: ngomp...@gmail.com
>
>
>== Detailed Description ==
>{{package|fedora-autofirstboot}} is a collection of scripts that
>invoke on firstboot of a freshly installed system to run a set of
>predetermined tasks. It also provides a framework for third-parties to
>introduce their own firstboot tasks to run through this framework. The
>initial services included are to install OpenH264 and remove Anaconda.
>
>
>== Benefit to Fedora ==
>The main benefit is to smooth out the new user experience for new
>Fedora Linux installations. In particular, we can deal with a
>long-standing sticking point that Anaconda remains installed on the
>user's machine when it is not useful to do so.
>
>== Scope ==
>* Proposal owners:
>** Add {{package|fedora-autofirstboot}} to the desktop kickstarts
>** Add a preset to {{package|fedora-release}} for
>fedora-autofirstboot.service
>
>* Other developers: N/A (not needed for this Change)
>
>* Release engineering: [https://pagure.io/releng/issue/11148 #11148]
>* Policies and guidelines: N/A (not needed for this Change)
>* Trademark approval: N/A (not needed for this Change)
>* Alignment with Objectives: N/A
>
>
>== Upgrade/compatibility impact ==
>This will have no impact on upgraded systems, since the firstboot
>condition is not true in that case.
>
>
>== How To Test ==
>
># Install Fedora Workstation, KDE, etc.
># Reboot into installed environment
># Check to see openh264 is installed and
>anaconda-core is not.
>
>== User Experience ==
>The first boot will be slightly slower because of these tasks running,
>though they should happily run in the background as other services
>start up, so it should not be noticeable.
>
>== Dependencies ==
>The main dependency is {{package|fedora-release}}, though we will need
>to ensure all {{package|udisks2}} plugins get pulled in as
>dependencies for {{package|gnome-disks}} and {{package|blivet-gui}} so
>they don't get uninstalled when Anaconda is.
>
>
>== Contingency Plan ==
>* Contingency mechanism: Remove {{package|fedora-autofirstboot}} from
>the kickstarts
>* Contingency deadline: Final freeze
>* Blocks release? No
>
>
>== Documentation ==
>There is not currently much documentation in
>[https://pagure.io/fedora-autofirstboot the upstream project], though
>contributions are welcome.

This sounds great, but it would be nice if the documentation could be expanded, 
before we flick the switch that makes this the default in Fedora. Especially as 
this sounds like something that could simplify our (=the i3 SIG) kickstart and 
custom scripts.

>
>== Release Notes ==
>Fedora Linux now ships with a framework for setting up first-boot
>services and uses this to install multimedia software and remove the
>installer software from the system after installation.
>
___
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 2148492] perl-IPC-Run3 sources is still in MD5 format

2022-11-25 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2148492

Ralf Corsepius  changed:

   What|Removed |Added

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



--- Comment #1 from Ralf Corsepius  ---
(In reply to Peter Oliver from comment #0)
> I'm trying to build perl-IPC-Run3 for EPEL 9 in Copr
> (https://copr.fedorainfracloud.org/coprs/mavit/perl-Carmel/build/5067472/),
> but the build fails with:
> 
> Invalid entry in sources file: 5a8cec571c51a118b265cf6e24e55761 
> IPC-Run3-0.048.tar.gz
This package builds fine for all Fedoras in Fedora 37's mock.

> I believe this is because Copr no-longer supports the old MD5 format for
> sources files.  Could the sources file be upgraded to SHA-512, please?
I do not see any sense in your proposal, because 100 - if not 1000s of packages
- still use MD5s in their source files.

That said, if RHEL9's tooling is incompatible to Fedora's tooling, something in
RHEL9 should be changed.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2148492
___
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: fedpkg clone fails with Permission denied (publickey).

2022-11-25 Thread Pavlos Orfanidis
> On Sun, Mar 29, 2020 at 12:32:33PM -0500, Richard Shaw wrote:
> 
> Yeah, please try again now. 
> 
> Currently the sync time is really long due to various reasons. 
> I'll try and impove this next week... 
> 
> In the mean time I have done a manual sync. 
> 
> kevin
I cannot connect to fedorapeople ssh due to public key Permission denied. Why 
desn't it sync my public key? (Of course I have added it to my account)
___
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: Web Assembly on Fedora: interested in a Fedora SIG to work on this?

2022-11-25 Thread Fabio Valentini
On Sat, Nov 19, 2022 at 11:13 AM Demi Marie Obenour
 wrote:
>
> IIRC the problematic components were only used in tests and could just
> be stripped.  Could be wrong, though.

They interface definitions are loaded and used to generate Rust code
at build time with "wiggle":
https://github.com/bytecodealliance/wasmtime/tree/main/crates/wasi-common/src/snapshots
So definitely not only used for tests.

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


Re: spin-kickstarts package

2022-11-25 Thread Adam Williamson
On Thu, 2022-11-24 at 13:48 -0800, Kevin Fenzi wrote:
> On Wed, Nov 23, 2022 at 09:33:48PM -0500, Neal Gompa wrote:
> > 
> > Is there a reason we couldn't just automatically update the package
> > once we're in freeze so that it has what we're shipping? By the time
> > we're down to the wire for final freeze, we're not changing the
> > kickstarts that often.
> 
> Thats what we used to do, but it has a bunch of process overhead. 
> 
> Someone has to file a blocker bug on it, it gets voted on and approved,
> then the package update has to be made, submitted, karma and request to
> go stable. 
> 
> A few times in the past we _have_ made kickstart changes during rc's,
> then it means we have to update the package and do all the overhead
> again. 
> 
> I'm just not sure what utility the package has, wouldn't everyone just
> get it from git and make sure they have the latest? 

Yes, I'm +1 to just dropping the package.

I see it as kind of a hangover from the old idea that the release tree
itself should contain everything necessary to reproduce it, but we've
never really completely honored that, so it doesn't seem worth worrying
about.
-- 
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net

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


Re: Web Assembly on Fedora: interested in a Fedora SIG to work on this?

2022-11-25 Thread Fabio Valentini
On Fri, Nov 25, 2022 at 5:41 PM Jun Aruga (he / him)  wrote:
>
> The Ruby new version 3.2.0 will start to support Web Assembly. It is
> planned to release the official version next month.
> https://www.ruby-lang.org/en/news/2022/11/11/ruby-3-2-0-preview3-released/
> https://github.com/ruby/ruby/blob/master/wasm/README.md
>
> However, I had to build the necessary tools such as WASI-SDK and
> wasmtime from the source to build Ruby as WebAssembly binaries at that
> time.
> Though I wrote about the situation on the email thread "Packaging a
> cross-compilation environment (wasi-libc)" in the past.
> I am looking forward to seeing the thrived RPM packages in the Web
> Assembly! Thanks guys!

If you're interested in getting wasmtime packaged for Fedora, note
that the unclear license situation of some sub-components (i.e. the
WebAssembly System Interface WITX files) has still not been resolved:

https://github.com/bytecodealliance/wasmtime/issues/3912
https://github.com/WebAssembly/WASI/issues/182

Once these issues are resolved, I'll gladly resume work on packaging
wasmtime for Fedora. We should be able to re-use some of the work that
was already done, before it was abandoned due to the unclear legal
situation regarding these files.

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


Re: Web Assembly on Fedora: interested in a Fedora SIG to work on this?

2022-11-25 Thread Jun Aruga (he / him)
The Ruby new version 3.2.0 will start to support Web Assembly. It is
planned to release the official version next month.
https://www.ruby-lang.org/en/news/2022/11/11/ruby-3-2-0-preview3-released/
https://github.com/ruby/ruby/blob/master/wasm/README.md

However, I had to build the necessary tools such as WASI-SDK and
wasmtime from the source to build Ruby as WebAssembly binaries at that
time.
Though I wrote about the situation on the email thread "Packaging a
cross-compilation environment (wasi-libc)" in the past.
I am looking forward to seeing the thrived RPM packages in the Web
Assembly! Thanks guys!

-- 
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See  for
the timezone.
___
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 2148492] New: perl-IPC-Run3 sources is still in MD5 format

2022-11-25 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2148492

Bug ID: 2148492
   Summary: perl-IPC-Run3 sources is still in MD5 format
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-IPC-Run3
  Severity: low
  Assignee: rc040...@freenet.de
  Reporter: ma...@mavit.org.uk
QA Contact: extras...@fedoraproject.org
CC: perl-devel@lists.fedoraproject.org,
rc040...@freenet.de
  Target Milestone: ---
Classification: Fedora



I'm trying to build perl-IPC-Run3 for EPEL 9 in Copr
(https://copr.fedorainfracloud.org/coprs/mavit/perl-Carmel/build/5067472/), but
the build fails with:

Invalid entry in sources file: 5a8cec571c51a118b265cf6e24e55761 
IPC-Run3-0.048.tar.gz

I believe this is because Copr no-longer supports the old MD5 format for
sources files.  Could the sources file be upgraded to SHA-512, please?


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2148492
___
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: Web Assembly on Fedora: interested in a Fedora SIG to work on this?

2022-11-25 Thread Michael Dawson
Thanks to everybody who has responded so far, will be waiting for more
responses as I know many people have been out this week.

On Fri, Nov 18, 2022 at 8:03 PM Philip Rhoades  wrote:

> Michael,
>
>
> On 2022-11-19 05:41, Michael Dawson wrote:
> > As Web Assembly (WASM) gains momentum we’d like to create a SIG as a
> > place to collaborate to ensure that Fedora is a great platform to both
> > build and run WASM workloads. This includes looking at the toolchains
> > needed to build WASM as a target and the runtimes needed to run WASM.
> > It will provide a place to bring together efforts across different
> > ecosystems (nodejs, rust, compiler toolchains, etc.) as well as a
> > place where people can provide self-help when building and running
> > WASM workloads.
> >
> > If you are interested in a WASM Sig please let us know.
>
>
> I am definitely interested in the area both because of Rust but
> particularly because of WASM . . I don't have a huge amount of time
> though unfortunately . .
>
> P.
> --
> Philip Rhoades
>
> PO Box 896
> Cowra  NSW  2794
> Australia
> E-mail:  p...@pricom.com.au
>
>
___
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: Potential kTLS issue with TLS-PSK, GnuTLS + Rawhide - how to debug it?

2022-11-25 Thread Simon Farnsworth via devel
On Friday, 25 November 2022 13:57:26 GMT Richard W.M. Jones wrote:
> Turns out this is fixed in upstream gnutls (not the version in
> Rawhide).  The commit which fixes it is:
> 
> commit 67843b3a8e28e4c74296caea2d1019065c87afb3
> Author: Frantisek Krenzelok 
> Date:   Mon Sep 5 13:05:17 2022 +0200
> 
> KTLS: fallback to default
> 
> If an error occurs during setting of keys either initial or key update
> then fallback to default mode of operation (disable ktls) and let the
> user know
> 
> Signed-off-by: Frantisek Krenzelok 
> 
>  lib/handshake.c|  7 ++-
>  lib/tls13/key_update.c | 23 +++
>  2 files changed, 25 insertions(+), 5 deletions(-)
> 
> With full debugging you can see the message caused by this commit:
> 
> nbdkit: null[1]: debug: gnutls: 4: HSK[0x7fc9e00010a0]: TLS 1.3 set read key
> with cipher suite: GNUTLS_CHACHA20_POLY1305_SHA256
 nbdkit: null[1]: debug:
> gnutls: 13: BUF[HSK]: Emptied buffer
> nbdkit: null[1]: debug: gnutls: 13: BUF[HSK]: Emptied buffer
> nbdkit: null[1]: debug: gnutls: 5: REC[0x7fc9e00010a0]: Start of epoch
> cleanup
 nbdkit: null[1]: debug: gnutls: 5: REC[0x7fc9e00010a0]: Epoch #0
> freed nbdkit: null[1]: debug: gnutls: 5: REC[0x7fc9e00010a0]: Epoch #1
> freed nbdkit: null[1]: debug: gnutls: 5: REC[0x7fc9e00010a0]: End of epoch
> cleanup nbdkit: null[1]: debug: gnutls: 1: disabling KTLS: failed to set
> keys 
> Is this because kTLS doesn't support PSK?
> 
kTLS doesn't do key management, so it doesn't know the difference between PSK 
and X.509 (it gets the symmetric keys from userspace after the key exchange is 
done).

However, looking at https://gitlab.com/gnutls/gnutls/-/blob/master/lib/system/
ktls.c, GnuTLS only supports using kTLS with GNUTLS_CIPHER_AES_128_GCM and 
GNUTLS_CIPHER_AES_256_GCM cipher suites, while your debugging output shows 
that this connection is using GNUTLS_CHACHA20_POLY1305_SHA256.

As a result, the upstream fix you point to does the right thing because you 
can't use GnuTLS's kTLS support on this connection (at all), and the only 
thing that makes sense is to disable kTLS.

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/
include/uapi/linux/tls.h suggests that kTLS has some degree of support for 
ciphers other than the two GnuTLS enables it for, but I don't know enough 
about TLS to know whether enabling all the ciphers current kernels support in 
GnuTLS would enable it to be used for this connection.

-- 
Simon Farnsworth

___
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 2144904] perl-App-cpm for EPEL 9

2022-11-25 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2144904

Jitka Plesnikova  changed:

   What|Removed |Added

 Depends On||2148461





Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=2148461
[Bug 2148461] Add perl-CPAN-02Packages-Search to EPEL 9
-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2144904
___
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 kTLS issue with TLS-PSK, GnuTLS + Rawhide - how to debug it?

2022-11-25 Thread Richard W.M. Jones
Turns out this is fixed in upstream gnutls (not the version in
Rawhide).  The commit which fixes it is:

commit 67843b3a8e28e4c74296caea2d1019065c87afb3
Author: Frantisek Krenzelok 
Date:   Mon Sep 5 13:05:17 2022 +0200

KTLS: fallback to default

If an error occurs during setting of keys either initial or key update
then fallback to default mode of operation (disable ktls) and let the
user know

Signed-off-by: Frantisek Krenzelok 

 lib/handshake.c|  7 ++-
 lib/tls13/key_update.c | 23 +++
 2 files changed, 25 insertions(+), 5 deletions(-)

With full debugging you can see the message caused by this commit:

nbdkit: null[1]: debug: gnutls: 4: HSK[0x7fc9e00010a0]: TLS 1.3 set read key 
with cipher suite: GNUTLS_CHACHA20_POLY1305_SHA256
nbdkit: null[1]: debug: gnutls: 13: BUF[HSK]: Emptied buffer
nbdkit: null[1]: debug: gnutls: 13: BUF[HSK]: Emptied buffer
nbdkit: null[1]: debug: gnutls: 5: REC[0x7fc9e00010a0]: Start of epoch cleanup
nbdkit: null[1]: debug: gnutls: 5: REC[0x7fc9e00010a0]: Epoch #0 freed
nbdkit: null[1]: debug: gnutls: 5: REC[0x7fc9e00010a0]: Epoch #1 freed
nbdkit: null[1]: debug: gnutls: 5: REC[0x7fc9e00010a0]: End of epoch cleanup
nbdkit: null[1]: debug: gnutls: 1: disabling KTLS: failed to set keys

Is this because kTLS doesn't support PSK?

Anyway I will file a bug to add this commit to Rawhide.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual machines.  Supports shell scripting,
bindings from many languages.  http://libguestfs.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: Potential kTLS issue with TLS-PSK, GnuTLS + Rawhide - how to debug it?

2022-11-25 Thread Richard W.M. Jones
On Fri, Nov 25, 2022 at 01:43:18PM +0100, Alexander Sosedkin wrote:
> On Fri, Nov 25, 2022 at 1:14 PM Richard W.M. Jones  wrote:
> >
> > Hi Daiki & Frantisek,
> >
> > There's a new error that is appearing in the libnbd test suite when
> > testing TLS-PSK.  Regular TLS (with X.509 certs) works fine.  It seems
> > to have started since I upgraded the kernel on my machine from 5.19.0 ->
> > 6.1.0, and I think it is related to kTLS.
> >
> > You may be able to reproduce it fairly easily in Fedora Rawhide, or in
> > Fedora 37 by upgrading the kernel, nbdkit and libnbd to Rawhide versions.
> >
> >   $ uname -a
> >   Linux pick.home.annexia.org 6.1.0-0.rc6.46.fc38.x86_64 #1 SMP 
> > PREEMPT_DYNAMIC Mon Nov 21 16:07:44 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
> >
> >   $ nbdkit --version
> >   nbdkit 1.33.3 (nbdkit-1.33.3-1.fc38)
> >   $ nbdinfo --version
> >   nbdinfo 1.15.7
> >   libnbd 1.15.7
> >
> > To reproduce it:
> >
> >   $ psktool -u bob -p keys.psk
> >   Generating a random key for user 'bob'
> >   Key stored to keys.psk
> >
> >   $ nbdkit --tls=require --tls-psk=keys.psk null \
> >--run 'nbdinfo "nbds://bob@localhost/?tls-psk-file=keys.psk" '
> >   nbdkit: null[1]: error: gnutls_record_recv: Error in the pull function.
> >   nbdkit: null[1]: error: reading option: conn->recv: Input/output error
> >   nbdinfo: nbd_connect_uri: gnutls_record_recv: Error in the pull function.
> >
> > For lots more debugging, use this command instead:
> >
> >   $ nbdkit -fv --tls=require --tls-psk=keys.psk \
> >-D nbdkit.tls.log=99 -D nbdkit.tls.session=1 null \
> >--run 'LIBNBD_DEBUG=1 nbdinfo 
> > "nbds://bob@localhost/?tls-psk-file=keys.psk" '
> >
> > The reason I believe it is related to kTLS is because if I do:
> >
> >   # modprobe -r tls
> >
> > then the error goes away.  Loading the module makes the error appear
> > again.  (Note that the module appears to be loaded on boot, so this
> > error will happen for all Rawhide users unless they take special
> > action.)
> >
> > Are there ways to debug kTLS?  It seems like there is no kernel output
> > related to the above failure.
> >
> > Are there ways to override GnuTLS automatic detection of kTLS, to
> > temporarily disable it, even when the kernel module is loaded?
> 
> For disabling KTLS, try putting
> ```
> [global]
> ktls = false
> ```
> into `/etc/crypto-policies/local.d/gnutls-no-ktls.config`,
> and follow up with an `update-crypto-policies --set`.

Aha!  Actually I already have:

$ cat /etc/crypto-policies/local.d/gnutls-ktls.config 
[global]
ktls = true

which I must have added a while back and forgotten about.

Removing that file disables kTLS.  So in fact what I said above isn't
right - this will not affect Rawhide users unless they also enable
kTLS explicitly, which is good to know.

Still interested in debugging the kTLS problem.

I've been having a look at straces, and what's interesting is that the
client sends and the server receives the cleartext message
successfully (as we would expect because the kernel is doing the
encryption and decryption below the socket level), but something
(GnuTLS?) believes that there was a socket error, even though there
isn't one.

Rich.

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


[Bug 2148436] Add perl-HTTP-Tinyish to EPEL 9

2022-11-25 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2148436

Jitka Plesnikova  changed:

   What|Removed |Added

  Alias||perl-HTTP-Tinyish-epel9




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2148436
___
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 2144904] perl-App-cpm for EPEL 9

2022-11-25 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2144904

Jitka Plesnikova  changed:

   What|Removed |Added

 Depends On||2148436





Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=2148436
[Bug 2148436] Add perl-HTTP-Tinyish to EPEL 9
-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2144904
___
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 2148436] Add perl-HTTP-Tinyish to EPEL 9

2022-11-25 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2148436

Jitka Plesnikova  changed:

   What|Removed |Added

 Blocks||2144904





Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=2144904
[Bug 2144904] perl-App-cpm for EPEL 9
-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2148436
___
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 2148436] New: Add perl-HTTP-Tinyish to EPEL 9

2022-11-25 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2148436

Bug ID: 2148436
   Summary: Add perl-HTTP-Tinyish to EPEL 9
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-HTTP-Tinyish
  Assignee: emman...@seyman.fr
  Reporter: jples...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: emman...@seyman.fr, jples...@redhat.com,
perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Please branch and build perl-HTTP-Tinyish in epel9. I can take care of the
build if you grant me access. My FAS username is jplesnik.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2148436
___
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 2144904] perl-App-cpm for EPEL 9

2022-11-25 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2144904



--- Comment #2 from Jitka Plesnikova  ---
> owner: jplesnik
> perl-Command-Runner
https://pagure.io/releng/fedora-scm-requests/issue/49347
> perl-Menlo
https://pagure.io/releng/fedora-scm-requests/issue/49345
> perl-Menlo-Legacy
https://pagure.io/releng/fedora-scm-requests/issue/49346
> perl-Module-cpmfile
https://pagure.io/releng/fedora-scm-requests/issue/49344
> perl-Parallel-Pipes
https://pagure.io/releng/fedora-scm-requests/issue/49343
> perl-Carton
https://pagure.io/releng/fedora-scm-requests/issue/49342
> perl-Tie-Handle-Offset
https://pagure.io/releng/fedora-scm-requests/issue/49341
> perl-CPAN-Common-Index
https://pagure.io/releng/fedora-scm-requests/issue/49348
> perl-App-FatPacker
https://pagure.io/releng/fedora-scm-requests/issue/49349

> owner: ppisar
> perl-CPAN-02Packages-Search
> 
> owner: eseyman
> perl-HTTP-Tinyish


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2144904
___
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 2148432] perl-Curses: Feature detection does not work for C99 compilers

2022-11-25 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2148432

Florian Weimer  changed:

   What|Removed |Added

 Status|ASSIGNED|CLOSED
 Resolution|--- |RAWHIDE
   Fixed In Version||perl-Curses-1.41-2.fc38
Last Closed||2022-11-25 13:08:12



--- Comment #2 from Florian Weimer  ---
I contacted the upstream author by email, following the README instructions.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2148432
___
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 2144904] perl-App-cpm for EPEL 9

2022-11-25 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2144904

Jitka Plesnikova  changed:

   What|Removed |Added

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



--- Comment #1 from Jitka Plesnikova  ---
The package is possible build for EPEL 9 now, but not to install. I'll build
it, but it takes some time.

There are missing some dependencies, most of them are mine:

owner: jplesnik
perl-Command-Runner
perl-Menlo
perl-Menlo-Legacy
perl-Module-cpmfile
perl-Parallel-Pipes
perl-Carton
perl-Tie-Handle-Offset
perl-CPAN-Common-Index
perl-App-FatPacker

owner: ppisar
perl-CPAN-02Packages-Search

owner: eseyman
perl-HTTP-Tinyish


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2144904
___
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 kTLS issue with TLS-PSK, GnuTLS + Rawhide - how to debug it?

2022-11-25 Thread Alexander Sosedkin
On Fri, Nov 25, 2022 at 1:14 PM Richard W.M. Jones  wrote:
>
> Hi Daiki & Frantisek,
>
> There's a new error that is appearing in the libnbd test suite when
> testing TLS-PSK.  Regular TLS (with X.509 certs) works fine.  It seems
> to have started since I upgraded the kernel on my machine from 5.19.0 ->
> 6.1.0, and I think it is related to kTLS.
>
> You may be able to reproduce it fairly easily in Fedora Rawhide, or in
> Fedora 37 by upgrading the kernel, nbdkit and libnbd to Rawhide versions.
>
>   $ uname -a
>   Linux pick.home.annexia.org 6.1.0-0.rc6.46.fc38.x86_64 #1 SMP 
> PREEMPT_DYNAMIC Mon Nov 21 16:07:44 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
>
>   $ nbdkit --version
>   nbdkit 1.33.3 (nbdkit-1.33.3-1.fc38)
>   $ nbdinfo --version
>   nbdinfo 1.15.7
>   libnbd 1.15.7
>
> To reproduce it:
>
>   $ psktool -u bob -p keys.psk
>   Generating a random key for user 'bob'
>   Key stored to keys.psk
>
>   $ nbdkit --tls=require --tls-psk=keys.psk null \
>--run 'nbdinfo "nbds://bob@localhost/?tls-psk-file=keys.psk" '
>   nbdkit: null[1]: error: gnutls_record_recv: Error in the pull function.
>   nbdkit: null[1]: error: reading option: conn->recv: Input/output error
>   nbdinfo: nbd_connect_uri: gnutls_record_recv: Error in the pull function.
>
> For lots more debugging, use this command instead:
>
>   $ nbdkit -fv --tls=require --tls-psk=keys.psk \
>-D nbdkit.tls.log=99 -D nbdkit.tls.session=1 null \
>--run 'LIBNBD_DEBUG=1 nbdinfo 
> "nbds://bob@localhost/?tls-psk-file=keys.psk" '
>
> The reason I believe it is related to kTLS is because if I do:
>
>   # modprobe -r tls
>
> then the error goes away.  Loading the module makes the error appear
> again.  (Note that the module appears to be loaded on boot, so this
> error will happen for all Rawhide users unless they take special
> action.)
>
> Are there ways to debug kTLS?  It seems like there is no kernel output
> related to the above failure.
>
> Are there ways to override GnuTLS automatic detection of kTLS, to
> temporarily disable it, even when the kernel module is loaded?

For disabling KTLS, try putting
```
[global]
ktls = false
```
into `/etc/crypto-policies/local.d/gnutls-no-ktls.config`,
and follow up with an `update-crypto-policies --set`.
___
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 2148432] perl-Curses: Feature detection does not work for C99 compilers

2022-11-25 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2148432



--- Comment #1 from Florian Weimer  ---
Created attachment 1927393
  --> https://bugzilla.redhat.com/attachment.cgi?id=1927393=edit
Additional patch to remove implicit ints


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2148432
___
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 2148432] New: perl-Curses: Feature detection does not work for C99 compilers

2022-11-25 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2148432

Bug ID: 2148432
   Summary: perl-Curses: Feature detection does not work for C99
compilers
   Product: Fedora
   Version: rawhide
Status: ASSIGNED
 Component: perl-Curses
  Assignee: fwei...@redhat.com
  Reporter: fwei...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: perl-devel@lists.fedoraproject.org,
steve.tray...@cern.ch
Blocks: 2141798 (PortingToModernCNoUpstream)
  Target Milestone: ---
Classification: Fedora



Created attachment 1927392
  --> https://bugzilla.redhat.com/attachment.cgi?id=1927392=edit
perl-Curses-test-syms-c99.patch

CursesDef.h is not available during feature probing using testsym.c, and the
relevant Curses headers are not included because the macros guarding the
inclusion are not defined. As a result, must of the feature tests fail in C99
mode because the compiler refuses to compile calls to undefined functions.

rt.cpan.org no longer allows me to file tickets, and the upstream author says
in the ticket that they prefer email anyway. So I'm filing this bug as a public
reference.



Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=2141798
[Bug 2141798] Porting Fedora to modern C: Bugs without (referenceable) upstream
-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2148432
___
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-Compress-Bzip2] PR #2: Package tests and update license to SPDX format

2022-11-25 Thread Michal Josef Špaček

mspacek opened a new pull-request against the project: `perl-Compress-Bzip2` 
that you are following:
``
Package tests and update license to SPDX format
``

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


Potential kTLS issue with TLS-PSK, GnuTLS + Rawhide - how to debug it?

2022-11-25 Thread Richard W.M. Jones
Hi Daiki & Frantisek,

There's a new error that is appearing in the libnbd test suite when
testing TLS-PSK.  Regular TLS (with X.509 certs) works fine.  It seems
to have started since I upgraded the kernel on my machine from 5.19.0 ->
6.1.0, and I think it is related to kTLS.

You may be able to reproduce it fairly easily in Fedora Rawhide, or in
Fedora 37 by upgrading the kernel, nbdkit and libnbd to Rawhide versions.

  $ uname -a
  Linux pick.home.annexia.org 6.1.0-0.rc6.46.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC 
Mon Nov 21 16:07:44 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

  $ nbdkit --version
  nbdkit 1.33.3 (nbdkit-1.33.3-1.fc38)
  $ nbdinfo --version
  nbdinfo 1.15.7
  libnbd 1.15.7

To reproduce it:

  $ psktool -u bob -p keys.psk
  Generating a random key for user 'bob'
  Key stored to keys.psk

  $ nbdkit --tls=require --tls-psk=keys.psk null \
   --run 'nbdinfo "nbds://bob@localhost/?tls-psk-file=keys.psk" '
  nbdkit: null[1]: error: gnutls_record_recv: Error in the pull function.
  nbdkit: null[1]: error: reading option: conn->recv: Input/output error
  nbdinfo: nbd_connect_uri: gnutls_record_recv: Error in the pull function.

For lots more debugging, use this command instead:

  $ nbdkit -fv --tls=require --tls-psk=keys.psk \
   -D nbdkit.tls.log=99 -D nbdkit.tls.session=1 null \
   --run 'LIBNBD_DEBUG=1 nbdinfo 
"nbds://bob@localhost/?tls-psk-file=keys.psk" '

The reason I believe it is related to kTLS is because if I do:

  # modprobe -r tls

then the error goes away.  Loading the module makes the error appear
again.  (Note that the module appears to be loaded on boot, so this
error will happen for all Rawhide users unless they take special
action.)

Are there ways to debug kTLS?  It seems like there is no kernel output
related to the above failure.

Are there ways to override GnuTLS automatic detection of kTLS, to
temporarily disable it, even when the kernel module is loaded?

Rich.

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


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

2022-11-25 Thread Michal Josef Špaček

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

Merged pull-request:

``
Update license to SPDX format
``

https://src.fedoraproject.org/rpms/perl-Convert-Base64/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: Should the policy documents better reflect real package maintenance practice?

2022-11-25 Thread Vít Ondruch


Dne 24. 11. 22 v 22:42 Adam Williamson napsal(a):

On Thu, 2022-11-24 at 16:26 -0500, Stephen Smoogen wrote:

On Thu, 24 Nov 2022 at 13:12, Gordon Messmer 
wrote:


On 2022-11-24 03:13, Michael J Gruber wrote:

I guess there's (at least) two ways to understand "stable":

- things don't break
- things don't change


True, but the policy document is explicit about which meaning is
intended, reading, "Updates should aim to fix bugs, and not introduce
features, particularly when those features would materially affect the
user or developer experience"

https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#stable-releases



It has to do with differing opinions on that and in the first part of the
sentence. There is
A) Updates should aim to fix bugs, AND not introduce features.
B) Updates should aim to fix bugs, and not introduce features.

Reason A with a strong logical AND means that things should be backported
for any bug fix. In this case, you are probably never going to see any bug
fixes occur in the distro as most software projects will say that the bug
is only fixed in the latest version which of course added 9 features. Since
this is usually a large amount of work for someone who may only have taken
the package to keep it in for a dependency, you would then just see those
fixes in rawhide (if at all).

Reason B with a weak language 'and' means that you shouldn't do updates
just to introduce new features but in order to fix things. This means that
if the upstream which in the cases of Firefox, Thunderbird, emacs, GIMP,
etc are either a package set they say is LTS OR in the latest.. you are
going to see updates occur.

Whenever I have talked to FESCO members over any large change, they have
said it was the B form they meant and they were ok with updates if it was
the way to fix things.

Thinking it over some more - I think Gordon's right that I hadn't
considered all the language - I think my personal opinion would be that
the policy should be adjusted to be less opinionated on this idea of
"introducing features", and concentrate more on "unexpected changes to
the user experience". There are a lot of cases where introducing
features is entirely benign, after all. If a CLI tool I use grows a
useful extra option while still supporting all the ones it had before
and behaving in the same way when using those, that just does not seem
like something to be concerned about. I'd happily send such an update
to stable.



While I agree with the above, the update on itself is not free. It cost 
time. It cost bandwidth. And it sill might introduce breakage.



Vít




If the update *removes* some existing argument, or changes the
behaviour of one, that's much more significant.

This is really kinda the rule about API/ABI changes, only for
applications, in a way. Adding new functions to a library doesn't
change the API, only removing or changing the behaviour of existing
ones.


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


Fedora rawhide compose report: 20221125.n.0 changes

2022-11-25 Thread Fedora Rawhide Report
OLD: Fedora-Rawhide-20221124.n.0
NEW: Fedora-Rawhide-20221125.n.0

= SUMMARY =
Added images:1
Dropped images:  0
Added packages:  1
Dropped packages:1
Upgraded packages:   77
Downgraded packages: 0

Size of added packages:  16.58 KiB
Size of dropped packages:63.54 KiB
Size of upgraded packages:   5.54 GiB
Size of downgraded packages: 0 B

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

= ADDED IMAGES =
Image: Container_Minimal_Base docker ppc64le
Path: 
Container/ppc64le/images/Fedora-Container-Minimal-Base-Rawhide-20221125.n.0.ppc64le.tar.xz

= DROPPED IMAGES =

= ADDED PACKAGES =
Package: alsa-ucm-asahi-1-3.fc38
Summary: ALSA Use Case Manager configuration (and topologies) for Apple silicon 
devices
RPMs:alsa-ucm-asahi
Size:16.58 KiB


= DROPPED PACKAGES =
Package: go-compilers-1-41.fc37
Summary: Go language compilers for various architectures
RPMs:go-compilers-golang-compiler
Size:63.54 KiB


= UPGRADED PACKAGES =
Package:  4Pane-8.0-1.fc38
Old package:  4Pane-7.0-6.fc37
Summary:  Multi-pane, detailed-list file manager
RPMs: 4Pane
Size: 6.56 MiB
Size change:  53.70 KiB
Changelog:
  * Fri Nov 25 2022 Mamoru TASAKA  - 8.0-1
  - 8.0


Package:  aprsd-2.2.5-15.6.fc38.30
Old package:  aprsd-2.2.5-15.6.fc37.29
Summary:  Internet gateway and client access to amateur radio APRS packet 
data
RPMs: aprsd
Size: 562.56 KiB
Size change:  1.53 KiB
Changelog:
  * Thu Nov 24 2022 Florian Weimer  - 2.2.5-15.6.30
  - Avoid C89 constructs in configure


Package:  arm-trusted-firmware-2.8-1.fc38
Old package:  arm-trusted-firmware-2.7-2.fc37
Summary:  ARM Trusted Firmware
RPMs: arm-trusted-firmware-armv8
Size: 136.90 KiB
Size change:  5.80 KiB
Changelog:
  * Thu Nov 24 2022 Peter Robinson  - 2.8-1
  - Update to 2.8


Package:  arts-8:1.5.10-55.fc38
Old package:  arts-8:1.5.10-54.fc38
Summary:  aRts (analog realtime synthesizer) - the KDE sound system
RPMs: arts arts-devel
Size: 6.01 MiB
Size change:  466 B
Changelog:
  * Thu Nov 24 2022 Florian Weimer  - 8:1.5.10-55
  - Port to C99 (#2147552)


Package:  avr-binutils-1:2.39-2.fc38
Old package:  avr-binutils-1:2.39-1.fc38
Summary:  Cross Compiling GNU binutils targeted at avr
RPMs: avr-binutils
Size: 7.91 MiB
Size change:  4.89 KiB
Changelog:
  * Thu Nov 24 2022 Florian Weimer  - 1:2.39-2
  - Apply patch from binutils-2.39-6.fc38 to avoid C89 constructs


Package:  caja-extensions-1.26.1-2.fc38
Old package:  caja-extensions-1.26.1-1.fc38
Summary:  Set of extensions for caja file manager
RPMs: caja-beesu caja-extensions-common caja-image-converter 
caja-open-terminal caja-sendto caja-sendto-devel caja-share caja-wallpaper 
caja-xattr-tags
Size: 1.09 MiB
Size change:  -18.79 KiB
Changelog:
  * Thu Nov 24 2022 Wolfgang Ulbrich  - 1.26.1-2
  - disable gupnp for sendto-plugin


Package:  chatterino2-2.4.0~beta-1.fc38
Old package:  chatterino2-2.3.5-6.fc38
Summary:  Chat client for https://twitch.tv
RPMs: chatterino2
Size: 12.18 MiB
Size change:  1.58 MiB
Changelog:
  * Thu Nov 24 2022 Artem Polishchuk  2.4.0~beta-1
  - build: Update to 2.4.0-beta


Package:  cockpit-280.1-1.fc38
Old package:  cockpit-280-1.fc38
Summary:  Web Console for Linux servers
RPMs: cockpit cockpit-bridge cockpit-doc cockpit-kdump 
cockpit-networkmanager cockpit-packagekit cockpit-pcp cockpit-selinux 
cockpit-sosreport cockpit-storaged cockpit-system cockpit-tests cockpit-ws
Size: 11.35 MiB
Size change:  4.28 KiB
Changelog:
  * Thu Nov 24 2022 Packit  - 280.1-1
  - Exclude kpatch test on RHEL gating


Package:  crack-attack-1.1.14-48.fc38
Old package:  crack-attack-1.1.14-47.fc37
Summary:  Puzzle action game
RPMs: crack-attack
Size: 3.87 MiB
Size change:  3.10 KiB
Changelog:
  * Thu Nov 24 2022 Florian Weimer  - 1.1.14-48
  - Port configure script to C99


Package:  curl-7.86.0-3.fc38
Old package:  curl-7.86.0-2.fc38
Summary:  A utility for getting files from remote servers (FTP, HTTP, and 
others)
RPMs: curl curl-minimal libcurl libcurl-devel libcurl-minimal
Size: 9.44 MiB
Size change:  3.57 KiB
Changelog:
  * Thu Nov 24 2022 Kamil Dudka  - 7.86.0-3
  - enforce versioned libnghttp2 dependency for libcurl (#2144277)


Package:  deletemail-0.5-31.fc38
Old package:  deletemail-0.5-30.fc37
Summary:  A non-interactive tool for deleting mails
RPMs: deletemail
Size: 187.66 KiB
Size change:  381 B
Changelog:
  * Thu Nov 24 2022 Florian Weimer  - 0.5-31
  - Port configure script to C99


Package:  erlang-25.1.2-2.fc38
Old package:  erlang-25.1.2-1.fc38
Summary:  General-purpose programming language and runtime environment
RPMs: erlang erlang-asn1 erlang-common_test erlang-compiler 
erlang-crypto erlang-debugger

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

2022-11-25 Thread Michal Josef Špaček

mspacek opened a new pull-request against the project: `perl-Convert-Base64` 
that you are following:
``
Update license to SPDX format
``

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


[rpms/perl-Convert-BER] PR #2: Fix test package and BuildRequires

2022-11-25 Thread Michal Josef Špaček

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

Merged pull-request:

``
Fix test package and BuildRequires
``

https://src.fedoraproject.org/rpms/perl-Convert-BER/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


Re: F38 proposal: Reproducible builds: Clamp build mtimes to $SOURCE_DATE_EPOCH (System-Wide Change proposal)

2022-11-25 Thread Miro Hrončok

On 24. 11. 22 19:28, Maxwell G via devel wrote:

On Thu Nov 10, 2022 at 15:23 -0500, Ben Cotton wrote:

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

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 `%clamp_mtime_to_source_date_epoch` RPM macro will be set to `1`.
When an RPM package is built, mtimes of packaged files will be clamped
to `$SOURCE_DATE_EPOCH` which is already set to the date of the latest
`%changelog` entry. As a result, more RPM packages will be
reproducible: The actual modification time of files that are e.g.
modified in the `%prep` section or built in the `%build` section will
not be reflected in the resulting RPM packages. Files in RPM packages
will have mtimes that are independent of the time of the actual build.



Will packagers still be required to use install -p, cp -p, etc. to
preserve mtimes? For some packages, the source archives mtimes will be
lower than $SOURCE_DATE_EPOCH, but e.g. for ancillary Source files (e.g.
systemd units) stored in distgit, using -p won't make a difference,
because the mtimes aren't preserved when Koji clones the distgit
repository.


Yes, that guideline will stay.

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


[Bug 2144551] Please branch and build perl-Parse-CPAN-Packages in epel9

2022-11-25 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2144551

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



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


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