Re: nodejs-electron

[Andreas Schneider]

On Friday, 25 February 2022 14:02:11 CET Neal Gompa wrote:
> I think this is probably one of those things that would be worth
> forming a SIG on. An Electron SIG could help with Electron and all
> Electron-based applications that come into Fedora.

That would be fine by me. The most obvious application would be Element 
(Matrix). https://element.io/

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

[EPEL-devel] EPEL Office Hours

[Carl George]

The EPEL Steering Committee has implementing monthly office hours for
the EPEL project.  These will be held on the first Wednesday of each
month at 1700 UTC.  The openSUSE Heroes team has agreed to let us host
the meeting on their Jitsi Meet instance.  Please join us at
https://meet.opensuse.org/epel with all your EPEL questions.

https://discussion.fedoraproject.org/t/join-us-for-the-epel-office-hours-every-month/37235

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

[Test-Announce] 2022-02-28 @ 17:00 UTC - Fedora 36 Blocker Review Meeting

[Adam Williamson]

# F36 Blocker Review meeting
# Date: 2022-02-28
# Time: 17:00 UTC
# Location: #fedora-blocker-review on irc.libera.chat

Hi folks! We have 3 proposed Beta blockers, 4 proposed Beta freeze
exception issues, and 5 proposed Final blockers to review, so let's
have a review meeting on Monday.

If you have time this weekend, you can take a look at the proposed or
accepted blockers before the meeting -  the full lists can be found
here: https://qa.fedoraproject.org/blockerbugs/ .

Remember, you can also now vote on bugs outside of review meetings! If
you look at the bug list in the blockerbugs app, you'll see links
labeled "Vote!" next to all proposed blockers and freeze exceptions.
Those links take you to tickets where you can vote.
https://pagure.io/fedora-qa/blocker-review has instructions on how
exactly you do it. We usually go through the tickets shortly before the
meeting and apply any clear votes, so the meeting will just cover bugs
where there wasn't a clear outcome in the ticket voting yet. **THIS
MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!**

We'll be evaluating these bugs to see if they violate any of the 
Release Criteria and warrant the blocking of a release if they're not 
fixed. Information on the release criteria for F36 can be found on the 
wiki [0].

For more information about the Blocker and Freeze exception process, 
check out these links:
 - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
 - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process

And for those of you who are curious how a Blocker Review Meeting 
works - or how it's supposed to go and you want to run one - check out 
the SOP on the wiki:
 - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting

Have a good weekend and see you on Monday!

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

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

[Adam Williamson]

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

Greetings testers!

It's been a while since we met, so let's get together and see where
we're at for Fedora 36 and so on.

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

== Proposed Agenda Topics ==

1. Previous meeting follow-up
2. Fedora 36 status
3. Current criteria / test case proposals
4. Test Day / community event status
5. 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 on the list, report it: 
https://pagure.io/fedora-infrastructure
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

pghmcfc pushed to perl-MCE-Shared (f36). "Update to 1.876 (..more)"

[notifications]

Notification time stamped 2022-02-20 13:54:50 UTC

From a4314a51b9f083bbd4c631ca6162c1ead94d1916 Mon Sep 17 00:00:00 2001
From: Paul Howarth 
Date: Feb 20 2022 13:45:55 +
Subject: Update to 1.876


- New upstream release 1.876
  - Improved suppressing the PDL CLONE warning; piddles should not be naively
copied into new threads

---

diff --git a/perl-MCE-Shared.spec b/perl-MCE-Shared.spec
index 39f81b4..a558bb1 100644
--- a/perl-MCE-Shared.spec
+++ b/perl-MCE-Shared.spec
@@ -1,6 +1,6 @@
 Name:  perl-MCE-Shared
-Version:   1.875
-Release:   2%{?dist}
+Version:   1.876
+Release:   1%{?dist}
 Summary:   MCE extension for sharing data, supporting threads and processes
 License:   GPL+ or Artistic
 URL:   https://metacpan.org/release/MCE-Shared
@@ -93,6 +93,11 @@ make test
 %{_mandir}/man3/MCE::Shared::Server.3*
 
 %changelog
+* Sun Feb 20 2022 Paul Howarth  - 1.876-1
+- Update to 1.876
+  - Improved suppressing the PDL CLONE warning; piddles should not be naively
+copied into new threads
+
 * Fri Jan 21 2022 Fedora Release Engineering  - 
1.875-2
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild
 
diff --git a/sources b/sources
index 48cfa7e..4df096e 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (MCE-Shared-1.875.tar.gz) = 
40eff54c9204543b091dd6805b7f69a903ced9a576e744b436c84cf1d4380994775498acc21ef21ef0c77862f14784ce9446970c300fab198ae7e703288a9399
+SHA512 (MCE-Shared-1.876.tar.gz) = 
dfc167d034a17e08b5315bd0f71a7b4ef6caf98406515be8adb0012730a78d080485938dea0c705c179c0a6b1410da6f02b0768b347ecfdcd8116f2176e3324f



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

pghmcfc pushed to perl-MCE-Shared (rawhide). "Update to 1.876 (..more)"

[notifications]

Notification time stamped 2022-02-20 13:46:46 UTC

From a4314a51b9f083bbd4c631ca6162c1ead94d1916 Mon Sep 17 00:00:00 2001
From: Paul Howarth 
Date: Feb 20 2022 13:45:55 +
Subject: Update to 1.876


- New upstream release 1.876
  - Improved suppressing the PDL CLONE warning; piddles should not be naively
copied into new threads

---

diff --git a/perl-MCE-Shared.spec b/perl-MCE-Shared.spec
index 39f81b4..a558bb1 100644
--- a/perl-MCE-Shared.spec
+++ b/perl-MCE-Shared.spec
@@ -1,6 +1,6 @@
 Name:  perl-MCE-Shared
-Version:   1.875
-Release:   2%{?dist}
+Version:   1.876
+Release:   1%{?dist}
 Summary:   MCE extension for sharing data, supporting threads and processes
 License:   GPL+ or Artistic
 URL:   https://metacpan.org/release/MCE-Shared
@@ -93,6 +93,11 @@ make test
 %{_mandir}/man3/MCE::Shared::Server.3*
 
 %changelog
+* Sun Feb 20 2022 Paul Howarth  - 1.876-1
+- Update to 1.876
+  - Improved suppressing the PDL CLONE warning; piddles should not be naively
+copied into new threads
+
 * Fri Jan 21 2022 Fedora Release Engineering  - 
1.875-2
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild
 
diff --git a/sources b/sources
index 48cfa7e..4df096e 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (MCE-Shared-1.875.tar.gz) = 
40eff54c9204543b091dd6805b7f69a903ced9a576e744b436c84cf1d4380994775498acc21ef21ef0c77862f14784ce9446970c300fab198ae7e703288a9399
+SHA512 (MCE-Shared-1.876.tar.gz) = 
dfc167d034a17e08b5315bd0f71a7b4ef6caf98406515be8adb0012730a78d080485938dea0c705c179c0a6b1410da6f02b0768b347ecfdcd8116f2176e3324f



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

[Bug 2058821] perl-Crypt-OpenSSL-X509-1.913 is available

[bugzilla]

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



--- Comment #2 from Upstream Release Monitoring 
 ---
the-new-hotness/release-monitoring.org's scratch build of
perl-Crypt-OpenSSL-X509-1.913-1.fc34.src.rpm for rawhide failed
http://koji.fedoraproject.org/koji/taskinfo?taskID=83341847


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

[Bug 2058821] New: perl-Crypt-OpenSSL-X509-1.913 is available

[bugzilla]

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

Bug ID: 2058821
   Summary: perl-Crypt-OpenSSL-X509-1.913 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Crypt-OpenSSL-X509
  Keywords: FutureFeature, Triaged
  Assignee: wjhns...@hardakers.net
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: perl-devel@lists.fedoraproject.org,
wjhns...@hardakers.net, xav...@bachelot.org
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 1.913
Current version/release in rawhide: 1.912-1.fc37
URL: http://search.cpan.org/dist/Crypt-OpenSSL-X509/

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


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


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


Based on the information from Anitya:
https://release-monitoring.org/project/2749/


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

[Bug 2058821] perl-Crypt-OpenSSL-X509-1.913 is available

[bugzilla]

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



--- Comment #1 from Upstream Release Monitoring 
 ---
Created attachment 1863392
  --> https://bugzilla.redhat.com/attachment.cgi?id=1863392=edit
Update to 1.913 (#2058821)


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

Re: Devtoolset for epel7 for build in Copr

[Frank Ch. Eigler]

Miroslav Suchý  writes:

> [...] Springdale provides
> devtoolset-3-elfutils there, and it in some strange way badly
> correlates with the initial Copr build environment (even before
> the rpmbuild process starts). Some python2 module cannot find
> libelf.so.1 ... 

I believe what's going on is that the old scl build of elfutils also
happens to include rpmbuild-generated libelf.so() virtual provides.
That tricks yum into sometimes installing that scl elfutils instead of
baseos elfutils to satisfy other packages' dependency on libelf.so.
And it won't satisfy the dependency without a custom LD_LIBRARY_PATH
(or scl enable).

Modern scl builds of elfutils go to some effort to suppress that virtual
rpm-provide.

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

[Bug 2058812] New: perl-DB_File-1.857 is available

[bugzilla]

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

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



Latest upstream release: 1.857
Current version/release in rawhide: 1.856-3.fc36
URL: http://search.cpan.org/dist/DB_File/

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


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


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


Based on the information from Anitya:
https://release-monitoring.org/project/2803/


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

Re: Devtoolset for epel7 for build in Copr

[Sérgio Basto]

On Fri, 2022-02-25 at 02:43 +0300, Dmitry Butskoy wrote:
> Sérgio Basto wrote:
> > On Thu, 2022-02-24 at 21:20 +0300, Dmitry Butskoy wrote:
> > > Miroslav Suchý wrote:
> > > > > Second, the alternate Springdale Linux repo
> > > > > http://springdale.princeton.edu/data/springdale/SCL/7/x86_64/ s
> > > > > ee
> > > > > ms
> > > > > to have all the ones (which are provided in sources by RedHat),
> > > > > but
> > > > > cannot be used in Copr. Springdale provides devtoolset-3-
> > > > > elfutils
> > > > > there, and it in some strange way  badly correlates with the
> > > > > initial
> > > > > Copr build environment (even before the rpmbuild process
> > > > > starts).
> > > > > Some python2 module cannot find libelf.so.1 ...
> > > > 
> > > > That is because it is SCL package. It installs the library to
> > > > 
> > > > /opt/rh/devtoolset-3/root/usr/lib64/libelf.so.1
> > > > 
> > > > You have to run
> > > > 
> > > >    scl enable devtools-3 $COMMAND
> > > > 
> > > But where to run it exactly?
> > > 
> > yes is not easy find an example unfortunately , first line of %build
> 
> %build is in the .spec file. It is readed after the start of the build.
> The start of the build is performed after the "bootstrap" stage. At
> this 
> stage "yum install" creates an initial environment. Probably I'm wrong 
> -- 

Sorry this thread have different topics, after reading it . 

 libelf.so.1: cannot open shared object file: No such file , should we
a mixup of devtools set , you just can Buildrequires one devtool set 

Second llvm-toolset-11.0 is only available on RedHat EL 7 , that is why
koji builds seamonkey which uses RHEL 7 and copr  don't, it uses Centos
7

Third, search on goggle I found that is also available on Scientific
Linux 7
http://rpm.pbone.net/results_srodzaj_1_search_libLLVM-11.so%28%29%2864bit%29.html


> could you pls look at:
> > Start: yum install
> > There was a problem importing one of the Python modules
> > required to run yum. The error leading to this problem was:
> > 
> >     libelf.so.1: cannot open shared object file: No such file or
> > directory
> fragment in the correspond log: 
> https://download.copr.fedorainfracloud.org/results/buc/seamonkey-generic/epel-7-x86_64/03543870-seamonkey/builder-live.log.gz
>  
> ?
> 
> IOW: there is no "yum install" in the .spec file. So where to run 
> "scl-enable ..." to take it effect before that "yum install" ?
> 
> 
> ~buc
> 
> 
> 
> 
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure

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

[EPEL-devel] epel8-playground officially decommissioned

[Troy Dawson]

EPEL Playground was shut down in January 2022

EPEL 8 Playground was a place that developers and maintainers could "play
around" with updated, or changed packages in epel. EPEL Playground never
really worked out and ended up being more of a burden than helpful.

If developers or maintainers want something similar to EPEL Playground we
recommend Fedora COPR[1], which has availability for EPEL builds.

The epel8-playground dnf repo's are still on the mirrors so we don't break
machines that might have them enabled.  They will eventually be archived
and removed.  If you know of any machines that might still be getting
updates from epel8-playground, please disable the repo.

Troy

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

Re: Why I get some random notifications from discourse?

[Tom Hughes via devel]

On 25/02/2022 19:08, Vít Ondruch wrote:
Is that intentional that i get some random notifications from Discourse 
or what is going on? In past month, I was notified about following topics:



* Join us for the EPEL office hours every month [Fedora] epel

* Self-intro glaringgibbon [Fedora] introductions

* It's #FedoraShareYourScreen week [Fedora] events

* Tempted to switch full-time to Fedora, but I got some noob questions 
[Fedora] introductions



And I wonder why? Does Discourse want to be completely muted or what?


Yes I was wondering why I seemed to be subscribed to some random
things as soon as I signed up... I think I've managed to unsubscribe
from them all now after a bit of fiddling but it's not very clear
from the emails which rule exactly has triggered them.

Tom

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

Why I get some random notifications from discourse?

[Vít Ondruch]

Is that intentional that i get some random notifications from Discourse 
or what is going on? In past month, I was notified about following topics:



* Join us for the EPEL office hours every month [Fedora] epel

* Self-intro glaringgibbon [Fedora] introductions

* It's #FedoraShareYourScreen week [Fedora] events

* Tempted to switch full-time to Fedora, but I got some noob questions 
[Fedora] introductions



And I wonder why? Does Discourse want to be completely muted or what?


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

Re: Rpm: provide a static library in package

[Demi Marie Obenour]

On 2/22/22 19:47, Kevin Kofler via devel wrote:
> Denis Fateyev wrote:
>> The "ustl" upstream, for which I maintain the RPM package, has recently
>> switched from providing a shared library to a static library.
> 
> Generally, you do not want to follow such a change, but force the build 
> system to build a shared library instead, even if it is not the upstream 
> default.
> 
> Kevin Kofler

Would uSockets be an exception?  That is designed to be used as a
static library with link-time optimization, so that trivial functions
(such as struct getters) can be inlined into users of the library.
Not doing so is (according to their documentation) a huge performance
hit.  That said, should such a library just be shipped as source code?

-- 
Sincerely,
Demi Marie Obenour (she/her/hers)

OpenPGP_0xB288B55FFF9C22C1.asc
Description: OpenPGP public key


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

Fedora-IoT-36-20220225.0 compose check report

[Fedora compose checker]

No missing expected images.

Failed openQA tests: 1/15 (aarch64)

Old failures (same test failed in Fedora-IoT-36-20220224.0):

ID: 1148427 Test: aarch64 IoT-dvd_ostree-iso iot_clevis@uefi
URL: https://openqa.fedoraproject.org/tests/1148427

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

Old soft failures (same test soft failed in Fedora-IoT-36-20220224.0):

ID: 1148411 Test: x86_64 IoT-dvd_ostree-iso iot_clevis
URL: https://openqa.fedoraproject.org/tests/1148411

Passed openQA tests: 14/15 (aarch64), 15/16 (x86_64)

New passes (same test not passed in Fedora-IoT-36-20220224.0):

ID: 1148429 Test: aarch64 IoT-dvd_ostree-iso iot_zezere_server@uefi
URL: https://openqa.fedoraproject.org/tests/1148429
ID: 1148431 Test: aarch64 IoT-dvd_ostree-iso iot_zezere_ignition@uefi
URL: https://openqa.fedoraproject.org/tests/1148431
ID: 1148436 Test: aarch64 IoT-dvd_ostree-iso release_identification@uefi
URL: https://openqa.fedoraproject.org/tests/1148436
ID: 1148440 Test: aarch64 IoT-dvd_ostree-iso podman@uefi
URL: https://openqa.fedoraproject.org/tests/1148440

Installed system changes in test x86_64 IoT-dvd_ostree-iso 
install_default_upload: 
System load changed from 0.40 to 0.06
Previous test data: https://openqa.fedoraproject.org/tests/1147222#downloads
Current test data: https://openqa.fedoraproject.org/tests/1148412#downloads
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F36 Beta blocker status summary

[Ben Cotton]

Action summary


Accepted blockers
-
1. anaconda — When running anaconda on Wayland with two keyboard
layouts configured, hitting any modifier key with the second layout
selected switches to the first layout — ASSIGNED
ACTION: Maintainers to fix issue

2. anaconda — Some variants are missing /etc/resolv.conf symlink (use
systemd-resolved) — POST
ACTION: Maintainers to package upstream PR 3884

3. fedora-release — fedora-release-identity-cloud says "Cloud
Edition", Cloud has not been an edition for years — ASSIGNED
ACTION: Maintainers to update fedora-release-identity-cloud or
group-with-such-authority to waive this.

4. mlocate — F35 with mlocate installed cannot be upgraded to F36 due
to conflict with plocate — ASSIGNED
ACTION: FESCo to vote on #2765

5. mutter — GNOME doesn't accept input from wireless keyboard if
there's not another "keyboard" input available — ASSIGNED
ACTION: Upstream to fix mutter to support multiple capabilities on a device

6. plasma-discover — Discover does not display applications correctly. — ON_QA
ACTION: QA to check if the behavior reappears

7. sddm — SDDM crashes upon log out from the KDE session. — NEW
ACTION: Maintainers to diagnose and fix issue

Proposed blockers
-

1. firefox — f36 composes still have firefox 96, f34 f35 have firefox 97 — NEW
ACTION: Maintainers to resolve build issues

2. gnome-control-center — After upgrade gnome-control-center to
42~beta-1.fc37 unable to configure VPN connection — NEW
ACTION: Reporter to confirm the behavior exists on F36

3. initial-setup — dnf system-upgrade 35 to 36 fails with various
pipewire wireplumber conflicts — NEW
ACTION: Maintainers to package upstream PR 297 (or find a better fix)


Bug-by-bug detail
=

Accepted blockers
-
1.  anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2016613 — ASSIGNED
When running anaconda on Wayland with two keyboard layouts configured,
hitting any modifier key with the second layout selected switches to
the first layout

adamwill's research shows that this bug has existed since F25, but
became more viisble after KDE switched to Wayland by default. This bug
was deferred to F36 Beta under the "too hard to fix" exception.
There's ongoing discussion trying to come up with a potential fix,
however we still seem to be a long way from that point.

2. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2032085 — POST
Some variants are missing /etc/resolv.conf symlink (use systemd-resolved)

Some variants are not using systemd-resolved as intended. With some
recently-merged changes to Anaconda, this appears to be working
correctly now, at least for ostree variants. Upstream PR has a fix for
F36: https://github.com/rhinstaller/anaconda/pull/3884

3. fedora-release —
https://bugzilla.redhat.com/show_bug.cgi?id=2018271 — ASSIGNED
fedora-release-identity-cloud says "Cloud Edition", Cloud has not been
an edition for years

Waived from F35 final under the "late blocker exception." Cloud WG is
working on a proposal to re-promote Cloud to Edition status, but that
will not happen for F36 release cycle. A ticket is pending with the
Fedora Council, although Cloud could proceed with removing the word
"Edition" for now: https://pagure.io/Fedora-Council/tickets/issue/389

4. mlocate — https://bugzilla.redhat.com/show_bug.cgi?id=2052433 — ASSIGNED
F35 with mlocate installed cannot be upgraded to F36 due to conflict
with plocate

The original change proposal planned for mlocate and plocate to be
parallel available in F36. However, this turns out to be more
challenging than expected. FESCo #2765 requests approval to have
plocate replace mlocate on upgrade.

5. libinput — https://bugzilla.redhat.com/show_bug.cgi?id=2017043 — NEW
GNOME doesn't accept input from wireless keyboard if there's not
another "keyboard" input available

On some hardware, devices with multiple capabilities that include
keyboard do not get registered as a keyboard. Thus they only work if
another keyboard is connected. It seems to mostly (or exclusively)
affect some ARM hardware. This appears to be a design flaw in mutter
and is reported upstream as
https://gitlab.gnome.org/GNOME/mutter/-/issues/2154

6. plasma-discover — https://bugzilla.redhat.com/show_bug.cgi?id=2057531 — NEW
Discover does not display applications correctly.

Discover was only showing Flatpaks, not RPMs. Refreshing appstream
partially helped. In recent composes, the behavior no longer appears.
We'll keep this bug open to keep checking if the bad cache returns.

7. sddm — https://bugzilla.redhat.com/show_bug.cgi?id=2057419 — NEW
SDDM crashes upon log out from the KDE session.

When logging out of a Plasma session, SDDM does not restart, leaving
the user at a terminal. A reboot is required to fix. This may be
specific to Wayland.

Proposed blockers
-

1. firefox — https://bugzilla.redhat.com/show_bug.cgi?id=2057193 — NEW
f36 composes still have firefox 96, f34 f35 have firefox 

Re: CPU does not support x86-64-v2?

[Daniel P . Berrangé]

On Fri, Feb 25, 2022 at 11:41:58AM -0600, Ron Olson wrote:
> Hey all-
> 
> I’m trying to build my packages for EPEL-9 on my up-to-date F35
> machine using Mock. I checked /etc/mock but can’t find any specific
> epel-9 config so I went with centos-stream+epel-next-9. Okay, fine,
> but when I run the job, it fails immediately with the error “Fatal
> glibc error: CPU does not support x86-64-v2”. The machine is a VM
> under ESXi with the following cpu info:

RHEL-9 (and thus EPEL / CentOS) set a new x86_64 baseline

  
https://developers.redhat.com/blog/2021/01/05/building-red-hat-enterprise-linux-9-for-the-x86-64-v2-microarchitecture-level

These CPU uarch baselines are defined in

  
https://gitlab.com/x86-psABIs/x86-64-ABI/-/blob/master/x86-64-ABI/low-level-sys-info.tex

> Architecture:x86_64
>   CPU op-mode(s):32-bit, 64-bit
>   Address sizes: 42 bits physical, 48 bits virtual
>   Byte Order:Little Endian
> CPU(s):  8
>   On-line CPU(s) list:   0-7
> Vendor ID:   GenuineIntel
>   Model name:Intel(R) Xeon(R) CPU   X7350  @ 2.93GHz

According to

  
https://ark.intel.com/content/www/us/en/ark/products/30796/intel-xeon-processor-x7350-8m-cache-2-93-ghz-1066-mhz-fsb.html

This is  "Products formerly Tigerton"  which is one of the oldest
64bit Xeon generations.

Notably it pre-dates the Nehalem generation, which is what the
x86_64-v2 uarch baseline corresponds to.

> CPU family:  6
> Model:   15
> Thread(s) per core:  1
> Core(s) per socket:  4
> Socket(s):   2
> Stepping:11
> BogoMIPS:5851.73
> Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
> mca cmov pat pse36 clflush dts mmx fxsr sse sse2 ht syscall nx lm constant_t
>  sc arch_perfmon pebs bts nopl tsc_reliable 
> nonstop_tsc cpuid aperfmperf tsc_known_freq pni ssse3 cx16 x2apic 
> tsc_deadline_timer h
>  ypervisor lahf_lm pti tsc_adjust dtherm

This is missing at least sse4_1, sse4_2, popcnt 

> I guess there was some CPU requirement change that I didn’t catch;
> is this going to make creating Fedora-based VMs difficult going
> forward? I don’t have the money to upgrade my equipment. :(

Note, the change in CPU uarch baseline only affects RHEL/CentOS/EPEL,
not Fedora yet. Though I imagine Fedora might follow at some point,
there's no current proposal for Fedora to change.

So for now at least, your use of Fedora shouldn't be impacted, only
RHEL-9 family.

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

Re: CPU does not support x86-64-v2?

[Gary Buhrmaster]

On Fri, Feb 25, 2022 at 5:42 PM Ron Olson  wrote:

> I guess there was some CPU requirement change that I didn’t catch;

https://developers.redhat.com/blog/2021/01/05/building-red-hat-enterprise-linux-9-for-the-x86-64-v2-microarchitecture-level

discussed the issue(s), and the x86_64 v2 requirement
was implemented.

> is this going to make creating Fedora-based VMs difficult going forward?

I suppose you could run a v2 system fully emulated,
but that is not going to work especially well :(

> I don’t have the money to upgrade my equipment. :(

A not uncommon issue for individuals.

If your package(s) otherwise meet the Fedora
licensing requirements, you can build them in
Fedora Copr for test purposes, and of course
if they are targeting EPEL9 you can run Koji
scratch builds with your SRPM.  All less easy
than a local mock build (and they use others
resources), but they are options.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: CPU does not support x86-64-v2?

[Florian Weimer]

* Ron Olson:

> I’m trying to build my packages for EPEL-9 on my up-to-date F35
> machine using Mock. I checked /etc/mock but can’t find any specific
> epel-9 config so I went with centos-stream+epel-next-9. Okay, fine,
> but when I run the job, it fails immediately with the error “Fatal
> glibc error: CPU does not support x86-64-v2”. The machine is a VM
> under ESXi with the following cpu info:

We encountered this before.  I believe Vmware has documentation out
addressing this.  Apparently there is a feature called “EVC” that can be
configured at the Core 2 (Merom) CPU level.  You need to switch to the
Nehalem level at least.  Maybe this document is of help:

  VMware EVC and CPU Compatibility FAQ (1005764)
  

Part of the reason of doing this is to flush out misconfigurations like
this.

Changing the hypervisor will also benefit older distributions which can
then start to use optimized string and math functions, particularly if
you move to something that approaches host pass-through (which should
probably be the default anyway unless migration is explicitly enabled).

> I guess there was some CPU requirement change that I didn’t catch; is
> this going to make creating Fedora-based VMs difficult going forward?
> I don’t have the money to upgrade my equipment. :(

Fedora doesn't require this yet.

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

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

[updates]

The following Fedora EPEL 7 Security updates need testing:
 Age  URL
   6  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-dc3bd1f656   
llvm13-13.0.1-1.el7 rust-1.58.1-1.el7
   2  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-18ac3af1c8   
varnish-4.0.5-3.el7
   0  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-af77a11507   
seamonkey-2.53.11-1.el7


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

xrootd-5.4.1-1.el7

Details about builds:



 xrootd-5.4.1-1.el7 (FEDORA-EPEL-2022-94a641c21c)
 Extended ROOT file server

Update Information:

XrootD 5.4.1

ChangeLog:

* Thu Feb 24 2022 Mattias Ellert  - 1:5.4.1-1
- Update to version 5.4.1
- Drop patches accepted upstream
* Mon Jan 31 2022 Mattias Ellert  - 1:5.4.0-5
- Use openssl 3 compatible code on EPEL 9
* Mon Jan 24 2022 Mattias Ellert  - 1:5.4.0-4
- Fix compiler warnings from gcc 12
* Sat Jan 22 2022 Fedora Release Engineering  - 
1:5.4.0-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_36_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 on the list, report it: 
https://pagure.io/fedora-infrastructure

CPU does not support x86-64-v2?

[Ron Olson]

Hey all-

I’m trying to build my packages for EPEL-9 on my up-to-date F35 machine using 
Mock. I checked /etc/mock but can’t find any specific epel-9 config so I went 
with centos-stream+epel-next-9. Okay, fine, but when I run the job, it fails 
immediately with the error “Fatal glibc error: CPU does not support x86-64-v2”. 
The machine is a VM under ESXi with the following cpu info:

Architecture:x86_64
  CPU op-mode(s):32-bit, 64-bit
  Address sizes: 42 bits physical, 48 bits virtual
  Byte Order:Little Endian
CPU(s):  8
  On-line CPU(s) list:   0-7
Vendor ID:   GenuineIntel
  Model name:Intel(R) Xeon(R) CPU   X7350  @ 2.93GHz
CPU family:  6
Model:   15
Thread(s) per core:  1
Core(s) per socket:  4
Socket(s):   2
Stepping:11
BogoMIPS:5851.73
Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts mmx fxsr sse sse2 ht syscall nx lm constant_t
 sc arch_perfmon pebs bts nopl tsc_reliable nonstop_tsc 
cpuid aperfmperf tsc_known_freq pni ssse3 cx16 x2apic tsc_deadline_timer h
 ypervisor lahf_lm pti tsc_adjust dtherm
Virtualization features:
  Hypervisor vendor: VMware
  Virtualization type:   full
Caches (sum of all):
  L1d:   256 KiB (8 instances)
  L1i:   256 KiB (8 instances)
  L2:8 MiB (2 instances)
NUMA:
  NUMA node(s):  1
  NUMA node0 CPU(s): 0-7
Vulnerabilities:
  Itlb multihit: KVM: Mitigation: VMX unsupported
  L1tf:  Mitigation; PTE Inversion
  Mds:   Vulnerable: Clear CPU buffers attempted, no microcode; 
SMT Host state unknown
  Meltdown:  Mitigation; PTI
  Spec store bypass: Vulnerable
  Spectre v1:Mitigation; usercopy/swapgs barriers and __user 
pointer sanitization
  Spectre v2:Mitigation; Full generic retpoline, STIBP disabled, 
RSB filling
  Srbds: Not affected
  Tsx async abort:   Not affected


I guess there was some CPU requirement change that I didn’t catch; is this 
going to make creating Fedora-based VMs difficult going forward? I don’t have 
the money to upgrade my equipment. :(

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

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

[updates]

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

composer-2.2.7-1.el9
kde-settings-35.0-2.el9.1
translate-shell-0.9.6.12-5.el9
xrootd-5.4.1-1.el9

Details about builds:



 composer-2.2.7-1.el9 (FEDORA-EPEL-2022-bbcb08c444)
 Dependency Manager for PHP

Update Information:

**Version 2.2.7** -  2022-02-25* Allow installation together with
composer/xdebug-handler ^3 (#10528)   * Fixed support for packages with no
licenses in `licenses` command output (#10537)   * Fixed handling of `allow-
plugins: false` which kept warning (#10530)   * Fixed enum parsing in classmap
generation when the enum keyword is not lowercased (#10521)   * Fixed author
parsing in `init` command requiring an email whereas the schema allows a name
only (#10538)   * Fixed issues in `require` command when requiring packages
which do not exist (but are provided by something else you require) (#10541)   *
Performance improvement in pool optimization step (#10546)

ChangeLog:

* Fri Feb 25 2022 Remi Collet  - 2.2.7-1
- update to 2.2.7




 kde-settings-35.0-2.el9.1 (FEDORA-EPEL-2022-7a3e95f245)
 Config files for kde

Update Information:

Recommend google-noto-sans-mono-fonts instead of require

ChangeLog:

* Thu Feb 24 2022 Troy Dawson  - 35.0-2.1
- Recommend google-noto-sans-mono-fonts instead of require




 translate-shell-0.9.6.12-5.el9 (FEDORA-EPEL-2022-7d7a75c5f7)
 A command-line online translator

Update Information:

Build for EPEL.

ChangeLog:

* Sat Jan 22 2022 Fedora Release Engineering  - 
0.9.6.12-5
- Rebuilt for https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild
* Fri Jul 23 2021 Fedora Release Engineering  - 
0.9.6.12-4
- Rebuilt for https://fedoraproject.org/wiki/Fedora_35_Mass_Rebuild
* Wed Jan 27 2021 Fedora Release Engineering  - 
0.9.6.12-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild
* Wed Jul 29 2020 Fedora Release Engineering  - 
0.9.6.12-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild
* Mon May 11 2020 Vasiliy N. Glazov  0.9.6.12-1
- Update to 0.9.6.12
* Fri Jan 31 2020 Fedora Release Engineering  - 
0.9.6.11-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild

References:

  [ 1 ] Bug #2057683 - Please branch and build translate-shell in epel9
https://bugzilla.redhat.com/show_bug.cgi?id=2057683




 xrootd-5.4.1-1.el9 (FEDORA-EPEL-2022-510ae83a58)
 Extended ROOT file server

Update Information:

XrootD 5.4.1

ChangeLog:

* Thu Feb 24 2022 Mattias Ellert  - 1:5.4.1-1
- Update to version 5.4.1
- Drop patches accepted upstream


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

[Bug 2055412] perl-File-Find-utf8-0.014 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-File-Find-utf8-0.014-1 |perl-File-Find-utf8-0.014-1
   |.fc36   |.fc36
   |perl-File-Find-utf8-0.014-1 |perl-File-Find-utf8-0.014-1
   |.fc35   |.fc35
   ||perl-File-Find-utf8-0.014-1
   ||.fc34



--- Comment #7 from Fedora Update System  ---
FEDORA-2022-1268123a5b has been pushed to the Fedora 34 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=2055412
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2053914] perl-Dist-Milla-1.0.21 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-Dist-Milla-1.0.21-1.fc |perl-Dist-Milla-1.0.21-1.fc
   |36  |36
   |perl-Dist-Milla-1.0.21-1.fc |perl-Dist-Milla-1.0.21-1.fc
   |35  |35
   ||perl-Dist-Milla-1.0.21-1.fc
   ||34



--- Comment #7 from Fedora Update System  ---
FEDORA-2022-5c726d5437 has been pushed to the Fedora 34 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=2053914
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2055412] perl-File-Find-utf8-0.014 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Resolution|--- |ERRATA
   Fixed In Version|perl-File-Find-utf8-0.014-1 |perl-File-Find-utf8-0.014-1
   |.fc36   |.fc36
   ||perl-File-Find-utf8-0.014-1
   ||.fc35
 Status|ON_QA   |CLOSED
Last Closed||2022-02-25 16:50:43



--- Comment #6 from Fedora Update System  ---
FEDORA-2022-b7f8b51ef2 has been pushed to the Fedora 35 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=2055412
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 2053914] perl-Dist-Milla-1.0.21 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Resolution|--- |ERRATA
 Status|ON_QA   |CLOSED
   Fixed In Version|perl-Dist-Milla-1.0.21-1.fc |perl-Dist-Milla-1.0.21-1.fc
   |36  |36
   ||perl-Dist-Milla-1.0.21-1.fc
   ||35
Last Closed||2022-02-25 16:50:32



--- Comment #6 from Fedora Update System  ---
FEDORA-2022-76a296a3a3 has been pushed to the Fedora 35 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=2053914
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

RE: How long to update and reflash in rpms web

[Miao, Jun]

Hi, Adam,

I am afraid of not to upload successfully, if that I will wait only. 
Thank you very much.

Jun

> -Original Message-
> From: Adam Williamson 
> Sent: Friday, February 25, 2022 3:22 PM
> To: Development discussions related to Fedora 
> Cc: Miao, Jun 
> Subject: Re: How long to update and reflash in rpms web
> 
> On Fri, 2022-02-25 at 07:15 +, Miao, Jun wrote:
> > Hi developers,
> >
> > I just update the tboot from 1.10.3-> 1.10.4 and "fedpkg build" 
> > successfully.
> > Got the email inform "[Fedora Update] [comment] tboot-1.10.4-2.fc37"
> > and a link
> > https://bodhi.fedoraproject.org/updates/FEDORA-2022-df432d9356
> > But from the web the Fedora37 is still xx.fc.36 like this:
> > [cid:image001.png@01D82A5A.87C07570]
> >
> > When the Fedora 37 -> xxx.fc37 
> 
> After the next Rawhide compose completes, plus time for mirrors to sync. There
> is usually one compose per day, completing around 9-10am UTC.
> --
> Adam Williamson
> Fedora QA
> IRC: adamw | Twitter: adamw_ha
> https://www.happyassassin.net
> 

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

unpaper license change

[Petr Pisar]

I was able to rebase unpaper to version 6.1^20220117.gite515408 in Fedora 37
thanks to ffmpeg we now have in a distribution. This new version changed
a license from GPL+ to GPLv2.

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

Fedora-36-20220225.n.0 compose check report

[Fedora compose checker]

No missing expected images.

Failed openQA tests: 12/229 (x86_64), 10/161 (aarch64)

New failures (same test not failed in Fedora-36-20220224.n.0):

ID: 1147714 Test: x86_64 Server-dvd-iso base_services_start
URL: https://openqa.fedoraproject.org/tests/1147714
ID: 1147755 Test: x86_64 Everything-boot-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/1147755
ID: 1147791 Test: x86_64 KDE-live-iso desktop_login
URL: https://openqa.fedoraproject.org/tests/1147791
ID: 1147795 Test: x86_64 KDE-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/1147795
ID: 1147798 Test: x86_64 KDE-live-iso desktop_notifications_postinstall
URL: https://openqa.fedoraproject.org/tests/1147798
ID: 1147801 Test: x86_64 KDE-live-iso desktop_printing_builtin
URL: https://openqa.fedoraproject.org/tests/1147801
ID: 1147840 Test: aarch64 Server-dvd-iso anaconda_help@uefi
URL: https://openqa.fedoraproject.org/tests/1147840
ID: 1147846 Test: aarch64 Server-dvd-iso install_blivet_lvm_ext4@uefi
URL: https://openqa.fedoraproject.org/tests/1147846
ID: 1147848 Test: aarch64 Server-dvd-iso support_server@uefi
URL: https://openqa.fedoraproject.org/tests/1147848
ID: 1147874 Test: aarch64 Server-dvd-iso 
install_repository_nfs_variation@uefi
URL: https://openqa.fedoraproject.org/tests/1147874
ID: 1147997 Test: x86_64 universal install_btrfs@uefi
URL: https://openqa.fedoraproject.org/tests/1147997
ID: 1148099 Test: aarch64 Server-raw_xz-raw.xz 
install_arm_image_deployment_upload@uefi
URL: https://openqa.fedoraproject.org/tests/1148099

Old failures (same test failed in Fedora-36-20220224.n.0):

ID: 1147785 Test: x86_64 KDE-live-iso anaconda_help
URL: https://openqa.fedoraproject.org/tests/1147785
ID: 1147786 Test: x86_64 KDE-live-iso desktop_notifications_live
URL: https://openqa.fedoraproject.org/tests/1147786
ID: 1147818 Test: x86_64 Silverblue-dvd_ostree-iso gnome_text_editor
URL: https://openqa.fedoraproject.org/tests/1147818
ID: 1147909 Test: aarch64 Workstation-raw_xz-raw.xz gnome_text_editor@uefi
URL: https://openqa.fedoraproject.org/tests/1147909
ID: 1147960 Test: aarch64 Workstation-upgrade gnome_text_editor@uefi
URL: https://openqa.fedoraproject.org/tests/1147960
ID: 1147993 Test: x86_64 universal install_asian_language
URL: https://openqa.fedoraproject.org/tests/1147993
ID: 1148061 Test: aarch64 universal install_asian_language@uefi
URL: https://openqa.fedoraproject.org/tests/1148061
ID: 1148089 Test: x86_64 universal install_arabic_language
URL: https://openqa.fedoraproject.org/tests/1148089
ID: 1148090 Test: aarch64 Minimal-raw_xz-raw.xz 
install_arm_image_deployment_upload@uefi
URL: https://openqa.fedoraproject.org/tests/1148090
ID: 1148108 Test: aarch64 universal install_arabic_language@uefi
URL: https://openqa.fedoraproject.org/tests/1148108

Soft failed openQA tests: 15/229 (x86_64), 13/161 (aarch64)
(Tests completed, but using a workaround for a known bug)

Old soft failures (same test soft failed in Fedora-36-20220224.n.0):

ID: 1147779 Test: x86_64 Workstation-live-iso eog
URL: https://openqa.fedoraproject.org/tests/1147779
ID: 1147816 Test: x86_64 Silverblue-dvd_ostree-iso eog
URL: https://openqa.fedoraproject.org/tests/1147816
ID: 1147824 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/1147824
ID: 1147911 Test: aarch64 Workstation-raw_xz-raw.xz eog@uefi
URL: https://openqa.fedoraproject.org/tests/1147911
ID: 1147922 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/1147922
ID: 1147923 Test: x86_64 Workstation-upgrade upgrade_desktop_64bit
URL: https://openqa.fedoraproject.org/tests/1147923
ID: 1147945 Test: aarch64 Workstation-upgrade upgrade_desktop_64bit@uefi
URL: https://openqa.fedoraproject.org/tests/1147945
ID: 1147948 Test: aarch64 Workstation-upgrade eog@uefi
URL: https://openqa.fedoraproject.org/tests/1147948
ID: 1147968 Test: x86_64 universal upgrade_2_desktop_64bit
URL: https://openqa.fedoraproject.org/tests/1147968
ID: 1147969 Test: x86_64 universal upgrade_2_desktop_encrypted_64bit
URL: https://openqa.fedoraproject.org/tests/1147969
ID: 1147970 Test: x86_64 universal upgrade_2_kde_64bit
URL: https://openqa.fedoraproject.org/tests/1147970
ID: 1147978 Test: x86_64 universal upgrade_desktop_encrypted_64bit
URL: https://openqa.fedoraproject.org/tests/1147978
ID: 1147988 Test: x86_64 universal upgrade_server_64bit
URL: https://openqa.fedoraproject.org/tests/1147988
ID: 1147998 Test: x86_64 universal upgrade_2_server_domain_controller
URL: https://openqa.fedoraproject.org/tests/1147998
ID: 1147999 Test: x86_64 universal upgrade_kde_64bit
URL: https://openqa.fedoraproject.org/tests/1147999
ID: 1148000 Test: x86_64 universal upgrade_server_domain_controller
URL: https://openqa.fedoraproject.org/tests/1148000
ID: 1148006 Test: x86_64 

Re: nodejs-electron

[Neal Gompa]

On Fri, Feb 25, 2022 at 4:54 AM Andreas Schneider  wrote:
>
> Hello!
>
> Over the past 8 month, I've been working on getting Electron [1] built on
> Fedora. Yesterday I was finally able to do the first working build for Fedora
> Rawhide [2]. This was possible because we finally have ffmpeg [3] in Fedora.
> My use for Electron is that I want to run signal-desktop [4] on Fedora. You
> can get electron and signal-packages packages for it at [5].
>
> Is there interest to bring nodejs-electron into Fedora and if yes, would
> someone be interested to maintain it? I don't have the time to maintain it but
> I'm happy to help as a co-maintainer.
>

I think this is probably one of those things that would be worth
forming a SIG on. An Electron SIG could help with Electron and all
Electron-based applications that come into Fedora.




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

Fedora 36 compose report: 20220225.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-36-20220224.n.0
NEW: Fedora-36-20220225.n.0

= SUMMARY =
Added images:0
Dropped images:  0
Added packages:  0
Dropped packages:2
Upgraded packages:   50
Downgraded packages: 0

Size of added packages:  0 B
Size of dropped packages:1.32 MiB
Size of upgraded packages:   420.24 MiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   -180.17 KiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =

= DROPPED IMAGES =

= ADDED PACKAGES =

= DROPPED PACKAGES =
Package: perl-HTML-Tidy-1.60-14.fc36
Summary: (X)HTML cleanup in a Perl object
RPMs:perl-HTML-Tidy
Size:201.71 KiB

Package: tidyp-1.02-29.fc36
Summary: Clean up and pretty-print HTML/XHTML/XML
RPMs:libtidyp libtidyp-devel tidyp
Size:1.12 MiB


= UPGRADED PACKAGES =
Package:  bluedevil-5.24.2-1.fc36
Old package:  bluedevil-5.24.1-1.fc36
Summary:  Bluetooth stack for KDE
RPMs: bluedevil
Size: 2.07 MiB
Size change:  426 B
Changelog:
  * Tue Feb 22 2022 Rex Dieter  - 5.24.2-1
  - 5.24.2


Package:  breeze-gtk-5.24.2-1.fc36
Old package:  breeze-gtk-5.24.1-1.fc36
Summary:  Breeze widget theme for GTK
RPMs: breeze-gtk breeze-gtk-common breeze-gtk-gtk2 breeze-gtk-gtk3 
breeze-gtk-gtk4
Size: 318.96 KiB
Size change:  -216 B
Changelog:
  * Tue Feb 22 2022 Rex Dieter  - 5.24.2-1
  - 5.24.2


Package:  grub2-breeze-theme-5.24.2-1.fc36
Old package:  grub2-breeze-theme-5.24.1-1.fc36
Summary:  Breeze theme for GRUB
RPMs: grub2-breeze-theme
Size: 10.03 MiB
Size change:  4.48 KiB
Changelog:
  * Tue Feb 22 2022 Rex Dieter  - 5.24.2-1
  - 5.24.2


Package:  kactivitymanagerd-5.24.2-1.fc36
Old package:  kactivitymanagerd-5.24.1-1.fc36
Summary:  Plasma service to manage user's activities
RPMs: kactivitymanagerd
Size: 1.57 MiB
Size change:  361 B
Changelog:
  * Tue Feb 22 2022 Rex Dieter  - 5.24.2-1
  - 5.24.2


Package:  kde-cli-tools-5.24.2-1.fc36
Old package:  kde-cli-tools-5.24.1-1.fc36
Summary:  Tools based on KDE Frameworks 5 to better interact with the system
RPMs: kde-cli-tools kdesu
Size: 6.00 MiB
Size change:  7.31 KiB
Changelog:
  * Tue Feb 22 2022 Rex Dieter  - 5.24.2-1
  - 5.24.2


Package:  kde-gtk-config-5.24.2-1.fc36
Old package:  kde-gtk-config-5.24.1-1.fc36
Summary:  Configure the appearance of GTK apps in KDE
RPMs: kde-gtk-config
Size: 625.06 KiB
Size change:  -541 B
Changelog:
  * Tue Feb 22 2022 Rex Dieter  - 5.24.2-1
  - 5.24.2


Package:  kdecoration-5.24.2-1.fc36
Old package:  kdecoration-5.24.1-1.fc36
Summary:  A plugin-based library to create window decorations
RPMs: kdecoration kdecoration-devel
Size: 699.36 KiB
Size change:  802 B
Changelog:
  * Tue Feb 22 2022 Rex Dieter  - 5.24.2-1
  - 5.24.2


Package:  kdeplasma-addons-5.24.2-1.fc36
Old package:  kdeplasma-addons-5.24.1-1.fc36
Summary:  Additional Plasmoids for Plasma 5
RPMs: kdeplasma-addons kdeplasma-addons-devel
Size: 7.28 MiB
Size change:  2.36 KiB
Changelog:
  * Tue Feb 22 2022 Rex Dieter  - 5.24.2-1
  - 5.24.2


Package:  kgamma-1:5.24.2-1.fc36
Old package:  kgamma-1:5.24.1-1.fc36
Summary:  A monitor calibration tool
RPMs: kgamma
Size: 1.12 MiB
Size change:  -37 B
Changelog:
  * Tue Feb 22 2022 Rex Dieter  - 1:5.24.2-1
  - 5.24.2


Package:  khotkeys-5.24.2-1.fc36
Old package:  khotkeys-5.24.1-1.fc36
Summary:  Application to configure hotkeys in KDE
RPMs: khotkeys khotkeys-devel
Size: 12.09 MiB
Size change:  661 B
Changelog:
  * Tue Feb 22 2022 Rex Dieter  - 5.24.2-1
  - 5.24.2


Package:  kinfocenter-5.24.2-1.fc36
Old package:  kinfocenter-5.24.1-1.fc36
Summary:  KDE Info Center
RPMs: kinfocenter
Size: 6.41 MiB
Size change:  460 B
Changelog:
  * Tue Feb 22 2022 Rex Dieter  - 5.24.2-1
  - 5.24.2


Package:  kmenuedit-5.24.2-1.fc36
Old package:  kmenuedit-5.24.1-1.fc36
Summary:  KDE menu editor
RPMs: kmenuedit
Size: 5.27 MiB
Size change:  -709 B
Changelog:
  * Tue Feb 22 2022 Rex Dieter  - 5.24.2-1
  - 5.24.2


Package:  kscreen-1:5.24.2-1.fc36
Old package:  kscreen-1:5.24.1-1.fc36
Summary:  KDE Display Management software
RPMs: kscreen
Size: 1.63 MiB
Size change:  3.04 KiB
Changelog:
  * Tue Feb 22 2022 Rex Dieter  - 1:5.24.2-1
  - 5.24.2


Package:  kscreenlocker-5.24.2-1.fc36
Old package:  kscreenlocker-5.24.1-1.fc36
Summary:  Library and components for secure lock screen architecture
RPMs: kscreenlocker kscreenlocker-devel
Size: 1.45 MiB
Size change:  427 B
Changelog:
  * Tue Feb 22 2022 Rex Dieter  - 5.24.2-1
  - 5.24.2


Package:  ksshaskpass-5.24.2-1.fc36
Old package:  ksshaskpass-5.24.1-1.fc36
Summary:  A ssh-add helper that uses kwallet and kpassworddialog
RPMs: ksshaskpass
Size: 245.65 KiB
Size change

Re: Is NetworkManager-wait-online.service necessary by default?

[Benjamin Berg]

On Thu, 2022-02-24 at 10:14 -0500, Colin Walters wrote:
> 
> On Thu, Feb 24, 2022, at 6:17 AM, Benjamin Berg wrote:
> 
> > network-online-waitonly.target with
> >   After=network-online.target
> >   StopWhenUnneeded=yes
> > 
> > which is then used inside iscsi.service
> >   ExecStartPre=/usr/bin/systemctl start network-online-waitonly.target
> 
> No, avoid such things unless absolutely necessary - it makes the
> dependency graph dynamic, which systemd does support but doing so
> brings a vast amount of complexity.

Yeah, we need something dynamic depending on whether a directory is
non-empty.

I must have been blind before, because thinking about it now, this is
exactly what .path units are for. All we should need is iscsi.path
watching for the directory to be non-empty and moving the install
section into the path unit.

With that, we should get exactly what we want at boot time. The only
side effect I see is that it will also trigger the service when the
first node is created. But that may fine, as it just triggers an
automatic login.

> I think instead you can use e.g. a systemd generator:
> https://www.freedesktop.org/software/systemd/man/systemd.generator.html
> The generator (which can be the same binary) can then enable
> iscsi.service only if the directory is non-empty.

True, that is also a possible solution here. Maybe a bit better, though
it does move the logic to be outside of the systemd units, making it a
bit harder to see.

> (Which is making things dynamic, but all dynamic computation happens
> at a well-defined eraly fixed point and is acted on together
> thereafter)
> 
> Now I'd agree this behavior is not obvious, and perhaps systemd
> should gain something like
> EnableConditionDirectoryNotEmpty= that is defined to be evaluated at
> the same time as generators or so, and if the conditions evaluate to
> false then none of the unit dependencies will be pulled in either.

Yeah, that sounds like an elegant solution to have a generic generator
to do the above.

Benjamin

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



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

Re: Possibly unexpcted soname change: liblept.so.5 -> libleptonica.so.5.4.0

[Petr Pisar]

V Fri, Feb 25, 2022 at 07:37:35PM +0900, Mamoru TASAKA napsal(a):
> Petr Pisar wrote on 2022/02/25 19:10:
> > V Fri, Feb 25, 2022 at 10:46:15AM +0900, Mamoru TASAKA napsal(a):
> > > On f37 / f36 leptonica made some packaging change:
> > > https://src.fedoraproject.org/rpms/leptonica/c/e2486ca5bc2578ee629457b854c5e13bb94c1dde?branch=rawhide
> > > 
> > > This caused soname change: liblept.so.5 -> libleptonica.so.5.4.0 , which 
> > > I guess is unexpected.
> > > 
> > There was no soname change:
> > 
> > leptonica-1.81.1-2.fc35.aarch64.rpm provides liblept.so.5()(64bit).
> > "dnf repoquery --whatrequires 'liblept.so.5.4.0()(64bit)'" returns
> > no results in F36 and F37. Where can you see libleptonica.so.5.4.0?
> > 
> > -- Petr
> > 
> 
> 
> leptonica-1.82.0-6.fc37
> https://koji.fedoraproject.org/koji/buildinfo?buildID=1924153
> 
I see. I overlooked liblept changing to leptonica.

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

Re: Possibly unexpcted soname change: liblept.so.5 -> libleptonica.so.5.4.0

[Michael J Gruber]

> On 25.02.22 11:37, Mamoru TASAKA wrote:
> 
> Apologies, my mistake, upstream uses different library names depending 
> on whether you build with autotools or cmake, and when switching to 
> cmake I accidentally only provided the compat symlink for the 
> unversioned link library, but not for the versioned library. I'll 
> rebuild affected packages.
> 
> Sandro

So, is your plan to create the "lept" compat symlink both versioned and 
unversioned? No need to rebuild affected packages then. They have been rebuilt 
during the mass rebuild successfully and FTI now (not FTBFS).

Also, if you do decide to rebuild as a proven packager:
May I ask you to use more descriptive commit messages than "Rebuild 
(tesseract)" and close bugs that you caused (referencing them in the bodhi 
update could help) and maybe correspond with maintainers of affected packages 
in some way (i.e. do it better than the last time this happened)?

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

Re: List of long term FTBFS packages to be retired in March

[Miro Hrončok]

On 25. 02. 22 9:51, Akira TAGOH wrote:

On Tue, Feb 22, 2022 at 3:50 AM Miro Hrončok  wrote:

nim: sil-namdhinggo-fonts, yanone-kaffeesatz-fonts, gfs-decker-fonts,
gfs-didot-fonts, gfs-bodoni-fonts, impallari-dancing-script-fonts,
gfs-didot-display-fonts, typesetit-great-vibes-fonts, sil-charis-compact-fonts,
sil-tagmukay-fonts, uswds-public-sans-fonts, weiweihuanghuang-work-sans-fonts,
ecolier-court-fonts, gfs-solomos-fonts, gfs-jackson-fonts,
catharsis-cormorant-fonts, gfs-neohellenic-fonts, sil-annapurna-fonts,
gfs-neohellenic-math-fonts, sil-andika-new-basic-fonts, gfs-eustace-fonts,
adf-tribun-fonts, gfs-fleischman-fonts, sil-awami-nastaliq-fonts,
sil-dai-banna-fonts, sil-mondulkiri-fonts, vernnobile-nunito-fonts,
gfs-theokritos-fonts, ndiscover-exo-2-fonts, symbian-m-yuppy-gb-fonts,
sil-andika-fonts, gfs-goschen-fonts, ht-alegreya-sans-fonts, gfs-olga-fonts,
gfs-complutum-fonts, gfs-artemisia-fonts, gfs-orpheus-sans-fonts,
gfs-ambrosia-fonts, sil-shimenkan-fonts, wagesreiter-patrick-hand-fonts,
intel-clear-sans-fonts, sil-apparatus-fonts, sil-mondulkiri-extra-fonts,
gfs-garaldus-fonts, vernnobile-oswald-fonts, sil-harmattan-fonts,
gfs-orpheus-classic-fonts, gfs-bodoni-classic-fonts, sil-sophia-nubian-fonts,
kemie-bellota-fonts, sil-tai-heritage-pro-fonts, gfs-pyrsos-fonts,
gfs-baskerville-fonts, sil-andika-compact-fonts, gfs-porson-fonts,
gfs-orpheus-fonts, gfs-gazis-fonts, gfs-philostratos-fonts, gfs-nicefore-fonts,
vernnobile-muli-fonts, gfs-galatea-fonts, gfs-didot-classic-fonts,
sil-gentium-plus-compact-fonts, sil-ezra-fonts, sil-alkalami-fonts,
gfs-ignacio-fonts


I have fixed all the above fonts packages if I'm missing anything.
dunno if there are any chances to get the results of the next run. but
please let me know if any.


Thanks.

I've updated 
https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb


Only the following 4 packages are left:

rubygem-cucumber-rails
rubygem-sup
tmux-top
libicu65



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

Re: Possibly unexpcted soname change: liblept.so.5 -> libleptonica.so.5.4.0

[Sandro Mani]

On 25.02.22 11:37, Mamoru TASAKA wrote:

Petr Pisar wrote on 2022/02/25 19:10:

V Fri, Feb 25, 2022 at 10:46:15AM +0900, Mamoru TASAKA napsal(a):

On f37 / f36 leptonica made some packaging change:
https://src.fedoraproject.org/rpms/leptonica/c/e2486ca5bc2578ee629457b854c5e13bb94c1dde?branch=rawhide 



This caused soname change: liblept.so.5 -> libleptonica.so.5.4.0 , 
which I guess is unexpected.



There was no soname change:

leptonica-1.81.1-2.fc35.aarch64.rpm provides liblept.so.5()(64bit).
"dnf repoquery --whatrequires 'liblept.so.5.4.0()(64bit)'" returns
no results in F36 and F37. Where can you see libleptonica.so.5.4.0?

-- Petr




leptonica-1.82.0-6.fc37
https://koji.fedoraproject.org/koji/buildinfo?buildID=1924153


Apologies, my mistake, upstream uses different library names depending 
on whether you build with autotools or cmake, and when switching to 
cmake I accidentally only provided the compat symlink for the 
unversioned link library, but not for the versioned library. I'll 
rebuild affected packages.


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

Orphaning a set of packages

[Fabian Deutsch]

Hey,

due to the lack of time I'm orphaning the following set of packages:

augeas-vala
clpeak
gimp-fourier-plugin
gocl
python-uinput

Feel free to step up and take them.

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

Re: Possibly unexpcted soname change: liblept.so.5 -> libleptonica.so.5.4.0

[Mamoru TASAKA]

Petr Pisar wrote on 2022/02/25 19:10:

V Fri, Feb 25, 2022 at 10:46:15AM +0900, Mamoru TASAKA napsal(a):

On f37 / f36 leptonica made some packaging change:
https://src.fedoraproject.org/rpms/leptonica/c/e2486ca5bc2578ee629457b854c5e13bb94c1dde?branch=rawhide

This caused soname change: liblept.so.5 -> libleptonica.so.5.4.0 , which I 
guess is unexpected.


There was no soname change:

leptonica-1.81.1-2.fc35.aarch64.rpm provides liblept.so.5()(64bit).
"dnf repoquery --whatrequires 'liblept.so.5.4.0()(64bit)'" returns
no results in F36 and F37. Where can you see libleptonica.so.5.4.0?

-- Petr




leptonica-1.82.0-6.fc37
https://koji.fedoraproject.org/koji/buildinfo?buildID=1924153

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

Re: Possibly unexpcted soname change: liblept.so.5 -> libleptonica.so.5.4.0

[Petr Pisar]

V Fri, Feb 25, 2022 at 10:46:15AM +0900, Mamoru TASAKA napsal(a):
> On f37 / f36 leptonica made some packaging change:
> https://src.fedoraproject.org/rpms/leptonica/c/e2486ca5bc2578ee629457b854c5e13bb94c1dde?branch=rawhide
> 
> This caused soname change: liblept.so.5 -> libleptonica.so.5.4.0 , which I 
> guess is unexpected.
>
There was no soname change:

leptonica-1.81.1-2.fc35.aarch64.rpm provides liblept.so.5()(64bit).
"dnf repoquery --whatrequires 'liblept.so.5.4.0()(64bit)'" returns
no results in F36 and F37. Where can you see libleptonica.so.5.4.0?

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

nodejs-electron

[Andreas Schneider]

Hello!

Over the past 8 month, I've been working on getting Electron [1] built on 
Fedora. Yesterday I was finally able to do the first working build for Fedora 
Rawhide [2]. This was possible because we finally have ffmpeg [3] in Fedora. 
My use for Electron is that I want to run signal-desktop [4] on Fedora. You 
can get electron and signal-packages packages for it at [5].

Is there interest to bring nodejs-electron into Fedora and if yes, would 
someone be interested to maintain it? I don't have the time to maintain it but 
I'm happy to help as a co-maintainer.


Best regards


Andreas


[1] https://www.electronjs.org/
[2] https://build.opensuse.org/package/show/network:im:signal/nodejs-electron
[3] https://src.fedoraproject.org/rpms/ffmpeg/
[4] https://build.opensuse.org/package/show/network:im:signal/signal-desktop
[5] https://download.opensuse.org/repositories/network:/im:/signal/
Fedora_Rawhide/x86_64/

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

Fedora-Cloud-34-20220225.0 compose check report

[Fedora compose checker]

No missing expected images.

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

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

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

Passed openQA tests: 7/8 (x86_64), 7/8 (aarch64)
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora-Cloud-35-20220225.0 compose check report

[Fedora compose checker]

No missing expected images.

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

Old soft failures (same test soft failed in Fedora-Cloud-35-20220224.0):

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

Passed openQA tests: 7/8 (x86_64), 7/8 (aarch64)
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: List of long term FTBFS packages to be retired in March

[Akira TAGOH]

On Tue, Feb 22, 2022 at 3:50 AM Miro Hrončok  wrote:
> nim: sil-namdhinggo-fonts, yanone-kaffeesatz-fonts, gfs-decker-fonts,
> gfs-didot-fonts, gfs-bodoni-fonts, impallari-dancing-script-fonts,
> gfs-didot-display-fonts, typesetit-great-vibes-fonts, 
> sil-charis-compact-fonts,
> sil-tagmukay-fonts, uswds-public-sans-fonts, weiweihuanghuang-work-sans-fonts,
> ecolier-court-fonts, gfs-solomos-fonts, gfs-jackson-fonts,
> catharsis-cormorant-fonts, gfs-neohellenic-fonts, sil-annapurna-fonts,
> gfs-neohellenic-math-fonts, sil-andika-new-basic-fonts, gfs-eustace-fonts,
> adf-tribun-fonts, gfs-fleischman-fonts, sil-awami-nastaliq-fonts,
> sil-dai-banna-fonts, sil-mondulkiri-fonts, vernnobile-nunito-fonts,
> gfs-theokritos-fonts, ndiscover-exo-2-fonts, symbian-m-yuppy-gb-fonts,
> sil-andika-fonts, gfs-goschen-fonts, ht-alegreya-sans-fonts, gfs-olga-fonts,
> gfs-complutum-fonts, gfs-artemisia-fonts, gfs-orpheus-sans-fonts,
> gfs-ambrosia-fonts, sil-shimenkan-fonts, wagesreiter-patrick-hand-fonts,
> intel-clear-sans-fonts, sil-apparatus-fonts, sil-mondulkiri-extra-fonts,
> gfs-garaldus-fonts, vernnobile-oswald-fonts, sil-harmattan-fonts,
> gfs-orpheus-classic-fonts, gfs-bodoni-classic-fonts, sil-sophia-nubian-fonts,
> kemie-bellota-fonts, sil-tai-heritage-pro-fonts, gfs-pyrsos-fonts,
> gfs-baskerville-fonts, sil-andika-compact-fonts, gfs-porson-fonts,
> gfs-orpheus-fonts, gfs-gazis-fonts, gfs-philostratos-fonts, 
> gfs-nicefore-fonts,
> vernnobile-muli-fonts, gfs-galatea-fonts, gfs-didot-classic-fonts,
> sil-gentium-plus-compact-fonts, sil-ezra-fonts, sil-alkalami-fonts,
> gfs-ignacio-fonts

I have fixed all the above fonts packages if I'm missing anything.
dunno if there are any chances to get the results of the next run. but
please let me know if any.

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

Re: Unannounced soname bump: libwebsockets.so.18 -> libwebsockets.so.19

[Petr Pisar]

V Thu, Feb 24, 2022 at 04:23:11PM +0100, Fabio Valentini napsal(a):
> On Tue, Feb 22, 2022 at 3:22 PM Mamoru TASAKA  
> wrote:
> > On f37 / f36 two days ago libwebsockets was updated from 4.2.2 to 4.3.1
> > which causes unannounced soname bump from libwebsockets.so.18 to 
> > libwebsockets.so.19
> >
> > What is strange here is that the committer seems aware of this change:
> > https://src.fedoraproject.org/rpms/libwebsockets/c/ad122ba347b290d1221fe6fee1c4194ac74c2719?branch=rawhide
> 
> Yeah, this is really strange. *Techically*, the soname bump was
> announced, 6 months ago:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/6M5NRYF7EGU62KKG56L72K6WGHWH5V2L/
> But then the announced update to 4.3.0 was never pushed.
> And now 4.3.1 was pushed to F36+ without further warnings,

Hopefully Fedora 36 will get enabled rpmdeplint CI tests which catch breaking
RPM dependencies .

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

Re: F37 Change: Curl-minimal as default (System-Wide Change proposal)

[Panu Matilainen]

On 2/24/22 16:37, Neal Gompa wrote:

On Thu, Feb 24, 2022 at 8:58 AM Richard W.M. Jones  wrote:


On Thu, Feb 24, 2022 at 02:28:08PM +0100, Kamil Dudka wrote:

On Thursday, February 24, 2022 1:35:38 PM CET Richard W.M. Jones wrote:

Did you discuss modularising curl itself upstream?


It was added to their wish list but I do not remember anybody working on it:

 https://github.com/curl/curl/commit/8204844f


That would be a better idea.


Not necessarily.  Each approach has its pros and cons.


I'm intrigued by what you think the cons would be.  AFAICT if curl was
modular in this way already we wouldn't be discussing this proposal at all,
but a different and better one around packaging splits.



It would also avoid the usability nightmare that comes with trying to
trigger switching implementations. This is a very big hammer that
basically tells people that we're crippling curl by default for users
and it has very large network effects across the entire distribution.
It's quite one thing to use curl-minimal for containers where people
expect tools to be broken in the endless pursuit of smaller base
images, but when real people need to use real systems in complex
configurations, having a reduced functionality curl by default is just
going to lead to support nightmares and complaints about random
breakages in applications on Fedora.


+1

Defaulting to a minimal version for the main distro and then arguing 
whether the loss of functionality is acceptable seems a peculiar and 
troubling idea.


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

Re: F37 Change: Curl-minimal as default (System-Wide Change proposal)

[Kamil Dudka]

On Thursday, February 24, 2022 3:37:56 PM CET Neal Gompa wrote:
> On Thu, Feb 24, 2022 at 8:58 AM Richard W.M. Jones  
wrote:
> > On Thu, Feb 24, 2022 at 02:28:08PM +0100, Kamil Dudka wrote:
> > > On Thursday, February 24, 2022 1:35:38 PM CET Richard W.M. Jones wrote:
> > > > Did you discuss modularising curl itself upstream?
> > > 
> > > It was added to their wish list but I do not remember anybody working on 
it:
> > > https://github.com/curl/curl/commit/8204844f
> > > > 
> > > > That would be a better idea.
> > > 
> > > Not necessarily.  Each approach has its pros and cons.
> > 
> > I'm intrigued by what you think the cons would be.  AFAICT if curl was
> > modular in this way already we wouldn't be discussing this proposal at
> > all,
> > but a different and better one around packaging splits.
> 
> It would also avoid the usability nightmare that comes with trying to
> trigger switching implementations. This is a very big hammer that
> basically tells people that we're crippling curl by default for users
> and it has very large network effects across the entire distribution.
> It's quite one thing to use curl-minimal for containers where people
> expect tools to be broken in the endless pursuit of smaller base
> images, but when real people need to use real systems in complex
> configurations, having a reduced functionality curl by default is just
> going to lead to support nightmares and complaints about random
> breakages in applications on Fedora.

Installations that need libcurl-full will have it installed.  There is no 
problem there.  You could hardly find a default that will fit everybody's 
taste.

Kamil

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

Re: F37 Change: Curl-minimal as default (System-Wide Change proposal)

[Kamil Dudka]

On Thursday, February 24, 2022 2:58:10 PM CET Richard W.M. Jones wrote:
> On Thu, Feb 24, 2022 at 02:28:08PM +0100, Kamil Dudka wrote:
> > On Thursday, February 24, 2022 1:35:38 PM CET Richard W.M. Jones wrote:
> > > Did you discuss modularising curl itself upstream?
> > 
> > It was added to their wish list but I do not remember anybody working on 
it:
> > https://github.com/curl/curl/commit/8204844f
> > > 
> > > That would be a better idea.
> > 
> > Not necessarily.  Each approach has its pros and cons.
> 
> I'm intrigued by what you think the cons would be.  AFAICT if curl was
> modular in this way already we wouldn't be discussing this proposal at all,
> but a different and better one around packaging splits.
> 
> Rich.

They key problem is that we would detect fewer problems at build time and more 
problems at run-time.  Users that prefer to use libcurl this way are already 
using it via pycurl or similar binding.  So there is no reason to cripple 
libcurl for users that prefer to use in a more predictable way.

Also environments where libcurl is used (for example Java Virtual Machine) are 
sensitive to the order in which shared libraries are loaded and initialized.  
If we make libcurl load external libraries (e.g. openldap) at run-time, it is 
not going to improve the already complicated situation.

The solution would also paralyze the automatic dependency scanner in rpmbuild, 
which sees only dependencies known at build time.

Fedora packaging guidelines also insist on the unversioned .so being packaged 
in a -devel package.  This complicates versioning of libraries that are loaded 
via dlopen().

Kamil

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