Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

[Kilian Hanich via devel]

Am 09.02.24 um 18:28 schrieb Neal Gompa:

On Fri, Feb 9, 2024 at 12:16 PM Roy Bekken  wrote:


On fredag 9. februar 2024 17:41:33 CET Neal Gompa wrote:

On Fri, Feb 9, 2024 at 11:06 AM Roy Bekken  wrote:




On fredag 9. februar 2024 04:04:04 CET Steve Cossette wrote:


I am not gonna reply to all of that because all we are doing at this
point
is repeating the same thing. But we are NOT stopping you from using
x11.
You can either build it yourself and put it on a copr (it’s not like
neal
is using voodoo in his copr), use the copr we provide or …




This is extremely hostile towards new people trying linux for the very
first time, asking them to add a copr repo if they have problems with
wayland  to try X11, its unlikely they ever heard this stuff before.



Most likely they are trying out Fedora on a live media.





And they're not going to get an X11 experience on live media even now.
Wayland has been used for all environment modes since Fedora 36.

I am aware if this. So you are saying that its perfectly fine that someone new
to linux boot into a desktop that microstutters when they move windows around?


No, it's not fine. Just like it's not fine to get random
tear/corruption snow when moving things around or opening windows on
X11.

The difference is that we can actually do something about those issues
with Plasma Wayland when people report them. *Tons* of these kinds of
issues were fixed over the past 3 years, and Plasma 6 brings a huge
upgrade around this stuff too. And the whole graphics pipeline is
fully under the control of KDE Plasma, so we can do things we've never
done before. That's why we can do VRR, HDR, VR, mixed-DPI, fractional
scaling, and so much more.

We can do things that even other Wayland desktops can't do because our
architecture is flexible enough to do it. With Plasma X11, our necks
are hanging to the dying albatross that is the X server and our hands
are tied behind our backs when we want to actually do something to
improve the experience. These are not issues with Plasma Wayland.

Because Plasma Wayland... is just KDE Plasma.





Quite a bit of topic from my part, but is your pipeline for Wayland
flexible enough to turn off any kind of display sync (even in windowed
mode) if the user wants that?

Sure, it has its downside (e.g. tearing can happen), but I rather have
that than the added latency (even if very minimal) of such a sync (and
yes, that includes VRR which has a considerable smaller one than normal
V-SYNC).
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: exiv2 and protobuf hard to do soname bump without turbulence

[Sérgio Basto]

On Fri, 2024-02-09 at 16:53 +, Gary Buhrmaster wrote:
> On Fri, Feb 9, 2024 at 4:23 PM Sérgio Basto 
> wrote:
> > 
> > Hi,
> > 
> > I'd like to bring to your attention that Fedora would benefit with
> > update of exiv2 [1] and  protobuf [2] but these packages have lots
> > of
> > dependencies and the update of the dependent packages is not
> > trivial .
> > tips, ideas and opinions ? to do these soname updates
> > 
> 
> While understandably annoying, last I knew the patent
> issue IRT BMFF was not yet resolved for exiv2 (waiting
> on RH legal).  As I understand it, once the issue is raised,
> one is required to wait for a formal decision to be made,
> and there no time frame for that to occur.
> 
> If you are willing to strip the sources of the BMFF support
> until such time as a decision as to whether to allow it
> to be included is made that should be a way forward
> more quickly.

"In order to update Exiv2, we need to know if this is okay to enable
BMFF support. Patents have theorically expired and it is enabled by
default in the latest version."

until isn't clear by legal it should be disabled , if default is enable
,we should disable it and move on , it is not a show stopper 


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

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

[Kevin Kofler via devel]

Neal Gompa wrote:
> Because Plasma Wayland... is just KDE Plasma.

But in the real world, users use applications that are not KDE or even Qt 
applications (or ones that use old versions of Qt that will never natively 
support Wayland, or old versions of other toolkits in the same situation, 
such as GTK 2, for that matter). Even if they use the most recent version 
of, say, GTK, there will always be differences in interpretation of the 
Wayland specifications which lead to interoperability problems (e.g., both 
GTK and GNOME Shell deliberately refusing to support server-side window 
decorations on Wayland, but also genuine interoperability bugs that can take 
a long time to get fixed such as this touch input bug: 
https://bugs.kde.org/show_bug.cgi?id=452967 that was finally fixed 1½ years 
after having been initially filed and sent back and forth between KDE and 
GTK bug trackers). So in the real world, there ARE interoperability problems 
that you just cannot argue away. What real users (will) use is NOT "just KDE 
Plasma".

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

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

[Kevin Kofler via devel]

Neal Gompa wrote:

> On Fri, Feb 9, 2024 at 11:06 AM Roy Bekken wrote:
>> If Fedora is so great then why do I find stuff like this?
>> https://github.com/Zer0CoolX/Fedora-KDE-Minimal-Install-Guide
>>
>> 15 Forks and 167 Stars btw
> 
> That is not a particularly good indication of popularity. Also, it's 4
> years out of date.

That is what happens when users have to rely on such self-help HOWTOs to 
work around distribution deficiencies. Those HOWTOs invariably tend to grow 
out of date.

By the way, what that link does not mention when it talks about "multiple 
packages for the same thing" is browsers / web engines. The Spin ships 
several applications using QtWebEngine, e.g., KMail, so that engine is not 
going away. But in addition to one or two browsers using that, which add 
little to no overhead size-wise, it still ships the duplicate application 
Firefox that bundles its own, completely different web engine. See: 
https://bugzilla.redhat.com/show_bug.cgi?id=1920298 . (The main argument has 
always been market share, which at 2% market share and steadily decreasing 
does not sound relevant anymore.)

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

[Bug 2263591] New: perl-Software-License-0.104006 is available

[bugzilla]

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

Bug ID: 2263591
   Summary: perl-Software-License-0.104006 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Software-License
  Keywords: FutureFeature, Triaged
  Assignee: emman...@seyman.fr
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: emman...@seyman.fr, iarn...@gmail.com,
p...@city-fan.org, perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 0.104006
Upstream release that is considered latest: 0.104006
Current version/release in rawhide: 0.104005-3.fc40
URL: https://metacpan.org/dist/Software-License

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


More information about the service that created this bug can be found at:
https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


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


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


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


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

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

[Bug 2263590] New: perl-Business-ISBN-Data-20240209.001 is available

[bugzilla]

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

Bug ID: 2263590
   Summary: perl-Business-ISBN-Data-20240209.001 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Business-ISBN-Data
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: jples...@redhat.com, ka...@ucw.cz, mspa...@redhat.com,
p...@city-fan.org, perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 20240209.001
Upstream release that is considered latest: 20240209.001
Current version/release in rawhide: 20240206.001-1.fc40
URL: https://metacpan.org/dist/Business-ISBN-Data/

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


More information about the service that created this bug can be found at:
https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


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


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


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


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

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

Re: Does splint work for anyone?

[Ian Laurie]

On 2/10/24 05:06, Stephen Smoogen wrote:


I was trying out the splint program on some code and found that it
doesn't seem to work on any recent release due to changes in various
header files

I tried using splint many years ago in connection with embedded
programming, and even though the GCC based embedded compiler I was using
was several major version numbers behind what was natively in Fedora, I
found splint to be hopelessly behind the times and utterly unusable.  I
don't know why it is even packaged in Fedora.

I wish I had the skills necessary to bring it up to date but I don't.

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

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

[Neal Gompa]

On Fri, Feb 9, 2024 at 2:25 PM Roy Bekken  wrote:
>
> On fredag 9. februar 2024 18:28:15 CET Neal Gompa wrote:
> > The difference is that we can actually do something about those issues
> > with Plasma Wayland when people report them. *Tons* of these kinds of
> > issues were fixed over the past 3 years, and Plasma 6 brings a huge
> > upgrade around this stuff too. And the whole graphics pipeline is
> > fully under the control of KDE Plasma, so we can do things we've never
> > done before. That's why we can do VRR, HDR, VR, mixed-DPI, fractional
> > scaling, and so much more.
> >
> Nobody is saying that this is not awesome stuff but as of today, on some
> hardware, Wayland is not a great experience.
>
> I just booted Fedora-KDE-Live-x86_64-Rawhide-20240207.n.0.iso
> First impression is great but I’ll start moving(fast) the welcome center
> window around and the desktop randomly freezes from 30sec to 90ses.
>
> This is on a 1080 with nouveau, im not sure if its better with the proprietary
> drivers.
>

It will definitely be better with the proprietary drivers. One of the
members of Fedora KDE has the same graphics card and daily drives
Plasma Wayland with the proprietary drivers.

GTX 16, RTX 20, RTX 30, and RTX 40 series GPUs will hopefully work
much better out of the box starting with tonight's compose since we
will have the new nouveau driver stack fully enabled for those cards.
Sadly, that doesn't help folks with older GPUs (like my GTX 960 or
your GTX 1080), but it'll still be an improvement overall.


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

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

[Roy Bekken]

On fredag 9. februar 2024 18:28:15 CET Neal Gompa wrote:
> The difference is that we can actually do something about those issues
> with Plasma Wayland when people report them. *Tons* of these kinds of
> issues were fixed over the past 3 years, and Plasma 6 brings a huge
> upgrade around this stuff too. And the whole graphics pipeline is
> fully under the control of KDE Plasma, so we can do things we've never
> done before. That's why we can do VRR, HDR, VR, mixed-DPI, fractional
> scaling, and so much more.
> 
Nobody is saying that this is not awesome stuff but as of today, on some 
hardware, Wayland is not a great experience.

I just booted Fedora-KDE-Live-x86_64-Rawhide-20240207.n.0.iso
First impression is great but I’ll start moving(fast) the welcome center 
window around and the desktop randomly freezes from 30sec to 90ses.

This is on a 1080 with nouveau, im not sure if its better with the proprietary 
drivers.

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

[Bug 2263535] perl-URI-5.27 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Resolution|--- |ERRATA
   Fixed In Version||perl-URI-5.27-1.fc40
 Status|MODIFIED|CLOSED
Last Closed||2024-02-09 19:00:05



--- Comment #2 from Fedora Update System  ---
FEDORA-2024-0fa8fbb4d0 (perl-URI-5.27-1.fc40) has been pushed to the Fedora 40
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=2263535

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

Does splint work for anyone?

[Stephen Smoogen]

I was trying out the splint program on some code and found that it doesn't
seem to work on any recent release due to changes in various header files
```
[ssmoogen@toolbox phytool (fix_asprintf)]$ splint +posixlib phytool.c
Splint 3.1.2 --- 22 Jul 2023

/usr/include/asm-generic/int-ll64.h:20:24: Parse Error:
Suspect missing struct or union keyword: __signed__ :
int. (For help on parse errors, see splint -help parseerrors.)
*** Cannot continue.
```

I haven't figured out a set of flags to get past this to make the tool
work. I looked upstream and the site has a 'we are no longer working on
this tool'. So I am not sure if the software 'works', 'how to fix the
software', or 'did I miss something obvious and everyone else knows this
one trick'.

Thanks for any help.

-- 
Stephen Smoogen, Red Hat Automotive
Let us be kind to one another, for most of us are fighting a hard battle.
-- Ian MacClaren
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: [Fedocal] Reminder meeting : ELN SIG

[Stephen Gallagher]

On Thu, Feb 8, 2024 at 9:18 AM Stephen Gallagher  wrote:
>
> On Thu, Feb 8, 2024 at 7:00 AM  wrote:
> >
> > Dear all,
> >
> > You are kindly invited to the meeting:
> >ELN SIG on 2024-02-09 from 12:00:00 to 13:00:00 US/Eastern
> >At fedora-meet...@irc.libera.chat
> >
> > The meeting will be about:
>
> * The status of and assigning tasks for the EL10 fork
>
> > Source: https://calendar.fedoraproject.org//meeting/10568/
> >


=
# #meeting:fedoraproject.org: eln
=

Meeting started by @sgallagh:fedora.im at 2024-02-09 17:01:06



Meeting summary
---
* TOPIC: Init Process (@sgallagh:fedora.im, 17:01:48)
* TOPIC: Forking EL 10 (@sgallagh:fedora.im, 17:06:54)
* INFO: As previously announced, Tuesday February 13th marks the
end of Fedora ELN syncing to CentOS Stream 10 (@sgallagh:fedora.im,
17:08:29)
* LINK: https://docs.fedoraproject.org/en-US/eln/branching/
(@sgallagh:fedora.im, 17:09:48)
* LINK: https://github.com/fedora-eln/eln/issues/180
(@sgallagh:fedora.im, 17:11:20)
* LINK: https://github.com/fedora-eln/eln/issues/179
(@sgallagh:fedora.im, 17:11:36)
* LINK: https://github.com/fedora-eln/eln/issues/176
(@sgallagh:fedora.im, 17:11:57)
* ACTION: Neil Hanlon to look into gtk-doc (@sgallagh:fedora.im, 17:22:15)
* TOPIC: RHEL-like Koji Builders (@sgallagh:fedora.im, 17:31:01)
* TOPIC: Open Floor (@sgallagh:fedora.im, 17:35:30)
* TOPIC: OpenSSL 3.2 (@sgallagh:fedora.im, 17:49:39)
* TOPIC: Next Meeting (@sgallagh:fedora.im, 17:55:53)
* INFO: There will be no meeting on Feb. 23rd. We may have an
out-of-schedule meeting on Mar. 1 if interest is high.
(@sgallagh:fedora.im, 18:00:49)

Meeting ended at 2024-02-09 18:01:03

Action items

* Neil Hanlon to look into gtk-doc

People Present (lines said)
---
* @sgallagh:fedora.im (61)
* @yselkowitz:fedora.im (23)
* @smooge:fedora.im (16)
* @nhanlon:beeper.com (5)
* @tdawson:fedora.im (4)
* @zodbot:fedora.im (4)
* @meetbot:fedora.im (2)
* @jonathanspw:fedora.im (1)
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

[Neal Gompa]

On Fri, Feb 9, 2024 at 12:16 PM Roy Bekken  wrote:
>
> On fredag 9. februar 2024 17:41:33 CET Neal Gompa wrote:
> > On Fri, Feb 9, 2024 at 11:06 AM Roy Bekken  wrote:
> >
> > >
> > >
> > > On fredag 9. februar 2024 04:04:04 CET Steve Cossette wrote:
> > >
> > > > I am not gonna reply to all of that because all we are doing at this
> > > > point
> > > > is repeating the same thing. But we are NOT stopping you from using
> > > > x11.
> > > > You can either build it yourself and put it on a copr (it’s not like
> > > > neal
> > > > is using voodoo in his copr), use the copr we provide or …
> > > >
> > > >
> > >
> > > This is extremely hostile towards new people trying linux for the very
> > > first time, asking them to add a copr repo if they have problems with
> > > wayland  to try X11, its unlikely they ever heard this stuff before.
> > >
> > >
> > >
> > > Most likely they are trying out Fedora on a live media.
> > >
> > >
> >
> >
> > And they're not going to get an X11 experience on live media even now.
> > Wayland has been used for all environment modes since Fedora 36.
> I am aware if this. So you are saying that its perfectly fine that someone new
> to linux boot into a desktop that microstutters when they move windows around?

No, it's not fine. Just like it's not fine to get random
tear/corruption snow when moving things around or opening windows on
X11.

The difference is that we can actually do something about those issues
with Plasma Wayland when people report them. *Tons* of these kinds of
issues were fixed over the past 3 years, and Plasma 6 brings a huge
upgrade around this stuff too. And the whole graphics pipeline is
fully under the control of KDE Plasma, so we can do things we've never
done before. That's why we can do VRR, HDR, VR, mixed-DPI, fractional
scaling, and so much more.

We can do things that even other Wayland desktops can't do because our
architecture is flexible enough to do it. With Plasma X11, our necks
are hanging to the dying albatross that is the X server and our hands
are tied behind our backs when we want to actually do something to
improve the experience. These are not issues with Plasma Wayland.

Because Plasma Wayland... is just KDE Plasma.



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

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

[Roy Bekken]

On fredag 9. februar 2024 17:41:33 CET Neal Gompa wrote:
> On Fri, Feb 9, 2024 at 11:06 AM Roy Bekken  wrote:
> 
> >
> >
> > On fredag 9. februar 2024 04:04:04 CET Steve Cossette wrote:
> > 
> > > I am not gonna reply to all of that because all we are doing at this
> > > point
> > > is repeating the same thing. But we are NOT stopping you from using
> > > x11.
> > > You can either build it yourself and put it on a copr (it’s not like
> > > neal
> > > is using voodoo in his copr), use the copr we provide or …
> > >
> > >
> > 
> > This is extremely hostile towards new people trying linux for the very
> > first time, asking them to add a copr repo if they have problems with
> > wayland  to try X11, its unlikely they ever heard this stuff before.
> >
> >
> >
> > Most likely they are trying out Fedora on a live media.
> >
> >
> 
> 
> And they're not going to get an X11 experience on live media even now.
> Wayland has been used for all environment modes since Fedora 36.
I am aware if this. So you are saying that its perfectly fine that someone new 
to linux boot into a desktop that microstutters when they move windows around?
> 
> 
> > > With the change proposal, fedora (as a distro) the kde sig has proposed
> > > to
> > > move away from packaging x11 for plasma 6, and by accepting the
> > > proposal,
> > > fedora (as an entity) agreed.
> > >
> > >
> > >
> > > Fedora has a reputation of moving forwards, not going backwards.
> > >
> > >
> > 
> > Moving so fast forward that they are leaving the users behind.
> >
> >
> >
> > If Fedora is so great then why do I find stuff like this?
> > https://github.com/Zer0CoolX/Fedora-KDE-Minimal-Install-Guide
> >
> >
> >
> > 15 Forks and 167 Stars btw
> >
> >
> 
> 
> That is not a particularly good indication of popularity. Also, it's 4
> years out of date.
Just like the majority of Fedora users don’t read the devel mailing lists, the 
majority don’t give stars when they download from gh.

Yeah its 4 years old, I don’t know what happens but im gonna take a wild guess 
and assume that person gave up.


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

[Bug 2263535] perl-URI-5.27 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|NEW |MODIFIED



--- Comment #1 from Fedora Update System  ---
FEDORA-2024-0fa8fbb4d0 (perl-URI-5.27-1.fc40) has been submitted as an update
to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-0fa8fbb4d0


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

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

Re: exiv2 and protobuf hard to do soname bump without turbulence

[Gary Buhrmaster]

On Fri, Feb 9, 2024 at 4:23 PM Sérgio Basto  wrote:
>
> Hi,
>
> I'd like to bring to your attention that Fedora would benefit with
> update of exiv2 [1] and  protobuf [2] but these packages have lots of
> dependencies and the update of the dependent packages is not trivial .
> tips, ideas and opinions ? to do these soname updates
>

While understandably annoying, last I knew the patent
issue IRT BMFF was not yet resolved for exiv2 (waiting
on RH legal).  As I understand it, once the issue is raised,
one is required to wait for a formal decision to be made,
and there no time frame for that to occur.

If you are willing to strip the sources of the BMFF support
until such time as a decision as to whether to allow it
to be included is made that should be a way forward
more quickly.
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: exiv2 and protobuf hard to do soname bump without turbulence

[Michael J Gruber]

Am Fr., 9. Feb. 2024 um 17:23 Uhr schrieb Sérgio Basto :
>
> Hi,
>
> I'd like to bring to your attention that Fedora would benefit with
> update of exiv2 [1] and  protobuf [2] but these packages have lots of
> dependencies and the update of the dependent packages is not trivial .
> tips, ideas and opinions ? to do these soname updates
>
> thank you
>
>
> [1]
> https://src.fedoraproject.org/rpms/exiv2/pull-request/6
>
> [2]
> https://src.fedoraproject.org/rpms/protobuf/pull-request/26

Is the legal question around bff solved?

I guess some time before the mass rebuild would have been a good time
for a major change ...

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

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

[Neal Gompa]

On Fri, Feb 9, 2024 at 11:06 AM Roy Bekken  wrote:
>
> On fredag 9. februar 2024 04:04:04 CET Steve Cossette wrote:
> > I am not gonna reply to all of that because all we are doing at this point
> > is repeating the same thing. But we are NOT stopping you from using x11.
> > You can either build it yourself and put it on a copr (it’s not like neal
> > is using voodoo in his copr), use the copr we provide or …
> >
> This is extremely hostile towards new people trying linux for the very
> first time, asking them to add a copr repo if they have problems with wayland
> to try X11, its unlikely they ever heard this stuff before.
>
> Most likely they are trying out Fedora on a live media.
>

And they're not going to get an X11 experience on live media even now.
Wayland has been used for all environment modes since Fedora 36.

> > With the change proposal, fedora (as a distro) the kde sig has proposed to
> > move away from packaging x11 for plasma 6, and by accepting the proposal,
> > fedora (as an entity) agreed.
> >
> > Fedora has a reputation of moving forwards, not going backwards.
> >
> Moving so fast forward that they are leaving the users behind.
>
> If Fedora is so great then why do I find stuff like this?
> https://github.com/Zer0CoolX/Fedora-KDE-Minimal-Install-Guide
>
> 15 Forks and 167 Stars btw
>

That is not a particularly good indication of popularity. Also, it's 4
years out of date.



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

exiv2 and protobuf hard to do soname bump without turbulence

[Sérgio Basto]

Hi,

I'd like to bring to your attention that Fedora would benefit with
update of exiv2 [1] and  protobuf [2] but these packages have lots of
dependencies and the update of the dependent packages is not trivial .
tips, ideas and opinions ? to do these soname updates 

thank you


[1]
https://src.fedoraproject.org/rpms/exiv2/pull-request/6

[2]
https://src.fedoraproject.org/rpms/protobuf/pull-request/26
-- 
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

[Roy Bekken]

On fredag 9. februar 2024 04:04:04 CET Steve Cossette wrote:
> I am not gonna reply to all of that because all we are doing at this point
> is repeating the same thing. But we are NOT stopping you from using x11.
> You can either build it yourself and put it on a copr (it’s not like neal
> is using voodoo in his copr), use the copr we provide or …
>
This is extremely hostile towards new people trying linux for the very 
first time, asking them to add a copr repo if they have problems with wayland 
to try X11, its unlikely they ever heard this stuff before.

Most likely they are trying out Fedora on a live media.

> With the change proposal, fedora (as a distro) the kde sig has proposed to
> move away from packaging x11 for plasma 6, and by accepting the proposal,
> fedora (as an entity) agreed.
> 
> Fedora has a reputation of moving forwards, not going backwards.
> 
Moving so fast forward that they are leaving the users behind.

If Fedora is so great then why do I find stuff like this?
https://github.com/Zer0CoolX/Fedora-KDE-Minimal-Install-Guide

15 Forks and 167 Stars btw


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

Re: dnf-4.19.0 without filelists in Rawhide soon

[Miroslav Suchý]

Dne 09. 02. 24 v 16:29 Florian Weimer napsal(a):

What's the impact on mock and older chroots?  Just use bootstrap chroot?


Yes, in rawhide if you build package for older chroot, you will have to use bootstrap chroot. It is enabled by default. 
You will have problems if you disabled it manually.


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

[heads up] update to sg3_utils-1.48 with soname bump in rawhide

[Dan Horák]

Hi, 

I am in process of updating sg3_utils to the latest 1.48 version that
brings a soname bump. The dependent packages will be rebuilt in a
sidetag. All the deps build fine in my testing.

sudo dnf --repoid=rawhide repoquery --whatrequires sg3_utils-libs
ddpt-0:0.97-8.fc40
ledmon-0:0.97-4.fc40
libgpod-0:0.8.3-50.fc40
lsvpd-0:1.7.15-3.fc40
udisks-0:1.0.5-25.fc40


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

Re: dnf-4.19.0 without filelists in Rawhide soon

[Jan Kolarik]

Hi Florian,

What's the impact on mock and older chroots?  Just use bootstrap chroot?


I don't expect any issues with existing environments. If the filelists
metadata is already present on the system, DNF simply won't load them by
default now. Or are you referring to something else?

Regards,
Jan

On Fri, Feb 9, 2024 at 4:29 PM Florian Weimer  wrote:

> * Jan Kolarik:
>
> > From a Fedora user perspective, there won't be any changes in the way
> > you operate the DNF package manager. The only difference is that
> > typically there will be less metadata downloaded.  Since all packages
> > in Fedora should have already eliminated file dependencies requiring
> > filelists metadata, no issues with official repositories are
> > anticipated.
>
> What's the impact on mock and older chroots?  Just use bootstrap chroot?
>
> Thanks,
> Florian
>
>
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2263535] New: perl-URI-5.27 is available

[bugzilla]

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

Bug ID: 2263535
   Summary: perl-URI-5.27 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-URI
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: jples...@redhat.com, ka...@ucw.cz, mspa...@redhat.com,
p...@city-fan.org, perl-devel@lists.fedoraproject.org,
rhug...@redhat.com, rstr...@redhat.com
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 5.27
Upstream release that is considered latest: 5.27
Current version/release in rawhide: 5.26-1.fc40
URL: https://metacpan.org/dist/URI/

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


More information about the service that created this bug can be found at:
https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


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


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


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


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

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

Re: dnf-4.19.0 without filelists in Rawhide soon

[Florian Weimer]

* Jan Kolarik:

> From a Fedora user perspective, there won't be any changes in the way
> you operate the DNF package manager. The only difference is that
> typically there will be less metadata downloaded.  Since all packages
> in Fedora should have already eliminated file dependencies requiring
> filelists metadata, no issues with official repositories are
> anticipated.

What's the impact on mock and older chroots?  Just use bootstrap chroot?

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

Re: Unresponsive maintainer: petersen / Pandoc package not updated since June 2023: Security vulnerability, CVE-2023-35936 (medium)

[Jens-Ulrik Petersen]

I should also have added there's an increasing amount of technical debt
with the pandoc packaging - I guess I need to beg people to help with
package reviews: also reminded of our packaging (review) streamlining
discussion from Flock last year.

Jens

On Fri, 9 Feb 2024, 23:23 Jens-Ulrik Petersen,  wrote:

> Hello I am here - thanks for contacting me.
>
> I was hoping to cover this as part of my F40 Change, but unfortunately I
> haven't gotten to it, so the Change is now at risk of being deferred to F41.
>
> Nevertheless I will see what I can do about this for F40: maybe a backport
> can also be done for F39.
>
> Next time you could also comment on the relevant bug:
> https://bugzilla.redhat.com/show_bug.cgi?id=1996301 - that would be
> appreciated.
>
> Thanks, Jens
>
> PS Special thanks to Neal Gompa for pinging me in Matrix. 
>
>
> On Fri, 9 Feb 2024, 20:05 Christopher Klooz,  wrote:
>
>> I cannot reach the maintainer petersen (see mail below): The package
>> "pandoc" remains at 3.1.3 in Fedora, but pandoc is already at 3.1.11.1.
>> Among the updates since 3.1.3, there have been two security-critical
>> (including the medium CVE-2023-35936. Security fixes are in 3.1.4 & 3.1.6).
>>
>> The actual risk is limited, but these should be updated nevertheless.
>>
>> Does anyone know how to reach him by other means?
>>
>> Regards,
>> Chris
>>
>>
>>  Forwarded Message 
>> Subject: Fedora package "pandoc" outdated and contains security
>> vulnerability
>> Date: Thu, 1 Feb 2024 15:55:09 +0100
>> From: py0...@posteo.net
>> To: peter...@fedoraproject.org
>>
>> Hi petersen,
>>
>> I am reaching out because of the package "pandoc", which you maintain.
>>
>> I have seen that the package is still at version 3.1.3 [1] when I tried
>> to install it with dnf, whereas the current version is 3.1.11.1 [2]: is
>> this intended or an accident?
>>
>> It has to be noted that the updates that have been added in the meantime
>> contain fixes for security vulnerabilities (at least CVE-2023-35936; I have
>> just roughly skimmed the changelogs). So at the moment, it seems the Fedora
>> build can be exploited by attackers in some circumstances [3] [4] because
>> it is still at 3.1.3.
>>
>> Regards & thanks for maintaining,
>>
>> Chris
>>
>> [1] https://koji.fedoraproject.org/koji/packageinfo?packageID=11560
>>
>> [2] https://hackage.haskell.org/package/pandoc &
>> https://github.com/jgm/pandoc
>>
>> [3] https://github.com/jgm/pandoc/releases?page=1
>>
>> [4] https://github.com/jgm/pandoc/releases?page=2
>>
>> --
>> ___
>> devel mailing list -- devel@lists.fedoraproject.org
>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>> Fedora Code of Conduct:
>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
>> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>> Do not reply to spam, report it:
>> https://pagure.io/fedora-infrastructure/new_issue
>>
>
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Unresponsive maintainer: petersen / Pandoc package not updated since June 2023: Security vulnerability, CVE-2023-35936 (medium)

[Jens-Ulrik Petersen]

Hello I am here - thanks for contacting me.

I was hoping to cover this as part of my F40 Change, but unfortunately I
haven't gotten to it, so the Change is now at risk of being deferred to F41.

Nevertheless I will see what I can do about this for F40: maybe a backport
can also be done for F39.

Next time you could also comment on the relevant bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1996301 - that would be
appreciated.

Thanks, Jens

PS Special thanks to Neal Gompa for pinging me in Matrix. 


On Fri, 9 Feb 2024, 20:05 Christopher Klooz,  wrote:

> I cannot reach the maintainer petersen (see mail below): The package
> "pandoc" remains at 3.1.3 in Fedora, but pandoc is already at 3.1.11.1.
> Among the updates since 3.1.3, there have been two security-critical
> (including the medium CVE-2023-35936. Security fixes are in 3.1.4 & 3.1.6).
>
> The actual risk is limited, but these should be updated nevertheless.
>
> Does anyone know how to reach him by other means?
>
> Regards,
> Chris
>
>
>  Forwarded Message 
> Subject: Fedora package "pandoc" outdated and contains security
> vulnerability
> Date: Thu, 1 Feb 2024 15:55:09 +0100
> From: py0...@posteo.net
> To: peter...@fedoraproject.org
>
> Hi petersen,
>
> I am reaching out because of the package "pandoc", which you maintain.
>
> I have seen that the package is still at version 3.1.3 [1] when I tried to
> install it with dnf, whereas the current version is 3.1.11.1 [2]: is this
> intended or an accident?
>
> It has to be noted that the updates that have been added in the meantime
> contain fixes for security vulnerabilities (at least CVE-2023-35936; I have
> just roughly skimmed the changelogs). So at the moment, it seems the Fedora
> build can be exploited by attackers in some circumstances [3] [4] because
> it is still at 3.1.3.
>
> Regards & thanks for maintaining,
>
> Chris
>
> [1] https://koji.fedoraproject.org/koji/packageinfo?packageID=11560
>
> [2] https://hackage.haskell.org/package/pandoc &
> https://github.com/jgm/pandoc
>
> [3] https://github.com/jgm/pandoc/releases?page=1
>
> [4] https://github.com/jgm/pandoc/releases?page=2
>
> --
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: OpenSSL 3.2.1 available in rawhide

[Jaroslav Prokop]

On 2/9/24 14:47, Tom Hughes via devel wrote:

On 09/02/2024 13:34, Jarek Prokop wrote:

Since the error from the scratch build says "invalid CA certificate" 
I thought to use some openssl "verification" command,

this one seems like I'm on the right path.

I have tried more permutations of the command with certificates 
available in the `spec/ssl/` directory, including using `-untrusted` 
with various certs, all seem to fail the same.


Any idea what's up or how to fix it?


As you say it doesn't like the CA certificate:

% openssl verify -verbose -CAfile ca-cert.pem server-cert.pem
CN=ca_mysql2gem
error 79 at 1 depth lookup: invalid CA certificate
error server-cert.pem: verification failed

That CA certificate doesn't have the CA:TRUE constraint set
which might be the problem?


Seems to have been exactly that.

When I add `-addext basicConstraints=critical,CA:TRUE,pathlen:1` to the 
ca-cert.pem generation command,

the tests and the verify command then work!

Seems that magic did the trick, thanks.

Jarek



Tom


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

Re: OpenSSL 3.2.1 available in rawhide

[Tom Hughes via devel]

On 09/02/2024 13:34, Jarek Prokop wrote:

Since the error from the scratch build says "invalid CA certificate" I 
thought to use some openssl "verification" command,

this one seems like I'm on the right path.

I have tried more permutations of the command with certificates 
available in the `spec/ssl/` directory, including using `-untrusted` 
with various certs, all seem to fail the same.


Any idea what's up or how to fix it?


As you say it doesn't like the CA certificate:

% openssl verify -verbose -CAfile ca-cert.pem server-cert.pem
CN=ca_mysql2gem
error 79 at 1 depth lookup: invalid CA certificate
error server-cert.pem: verification failed

That CA certificate doesn't have the CA:TRUE constraint set
which might be the problem?

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

Re: OpenSSL 3.2.1 available in rawhide

[Jarek Prokop]

On 2/9/24 10:26, Dmitry Belyavskiy wrote:

Dear Yaakov,



On Fri, Feb 9, 2024 at 4:51 AM Yaakov Selkowitz  
wrote:


On Thu, 2024-02-08 at 20:37 +0100, Sahana Prasad wrote:
> Hello everyone,
> OpenSSL 3.2.1 is now available in rawhide [1].
> There are no API/ABI changes in comparison with the last version in
> rawhide
> (3.1.4).
> This version (3.2.0 onwards) supports PQ algorithms that can be
> loaded
> through
> the OQS provider.
> A few tests that needed some downstream tweaks have been
disabled and
> being
> worked on.
> Other than this issue [2] upstream, we did not see any new
> failures/breakages.
>
> If you observe any new issues with this new version, kindly report a
> bug.

Would this be related to openssl 3.2.1?

https://koji.fedoraproject.org/koji/taskinfo?taskID=113198856

The tests pass locally in mock with openssl 3.1.4.


I can imagine the situation where upgrading to 3.2 could cause this 
failure but the logs are too vague.
Could you please provide more details (e.g. openssl low-level 
diagnostics) or even better a minimal reproducer for diagnostics?


Hi,

I am not that well versed in openssl but I think I got it quite minimal, 
as I can reproduce the error message using `openssl` command itself.
And I confirmed, at least locally, that the error started happening once 
I introduce Openssl 3.2.1 into buildroot, whether that's all to that 
story, I do not know.


As a result I have ruled out mariadb version update as the cause.

rubygem-mysql2 has a few tests that test SSL connection. Keys and certs 
are in upstream: https://github.com/brianmario/mysql2/tree/master/spec/ssl


However, we regenerate all certificates using `gen_certs.sh`: 
https://github.com/brianmario/mysql2/blob/master/spec/ssl/gen_certs.sh
In our repo: 
https://src.fedoraproject.org/rpms/rubygem-mysql2/blob/rawhide/f/rubygem-mysql2.spec#_94


Above the line in the file I linked from Fedora set CN to localhost as 
we expect connecting through that host.


Now, with the certs regenerated in mock I execute following:
```
$ openssl verify -CAfile ca-cert.pem client-cert.pem
CN=ca_mysql2gem
error 79 at 1 depth lookup: invalid CA certificate
error client-cert.pem: verification failed
```
Since the error from the scratch build says "invalid CA certificate" I 
thought to use some openssl "verification" command,

this one seems like I'm on the right path.

I have tried more permutations of the command with certificates 
available in the `spec/ssl/` directory, including using `-untrusted` 
with various certs, all seem to fail the same.


Any idea what's up or how to fix it?

Regards,
Jarek Prokop



As for now we don't see any significant regressions in our downstream 
tests.


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

[heads up] update to jpegxl-0.9.2 with soname bump in rawhide

[Sérgio Basto]

Hi, 
I will start a mass rebuild [1] in a side-tag, very soon , the goal is
finish and merge it before branch of Fedora 40, please let me know we
have any objection that prevent to proceeding.

Best regards,

[1]
dnf repoquery --disablerepo=* --enablerepo={rpmfusion-{non,}free-,}rawhide 
--whatrequires "libjxl*"  --qf "%{repoid} %{sourcerpm}" | pkgname  
rawhide ImageMagick
rawhide aom
rawhide darktable
rawhide efl
rawhide ffmpeg
rawhide geeqie
rawhide gimp
rawhide gthumb
rawhide imlib2
rawhide jpegxl
rawhide kf5-kimageformats
rawhide kf6-kimageformats
rawhide krita
rawhide seamonkey
rawhide vips
rawhide webkit2gtk4.0
rawhide webkitgtk
rawhide xine-lib
-- 
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[rpms/cpanspec] PR #3: Preparation of new build

[Michal Josef Špaček]

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

Merged pull-request:

``
Preparation of new build
``

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

dnf-4.19.0 without filelists in Rawhide soon

[Jan Kolarik]

Hello everyone,

Just a heads up that a new DNF version (4.19.0) is on its way to Rawhide
and is expected to land within the next several hours. This update
brings a system-wide
change 
related to not downloading filelists metadata by default.

>From a Fedora user perspective, there won't be any changes in the way you
operate the DNF package manager. The only difference is that typically
there will be less metadata downloaded. Since all packages in Fedora should
have already eliminated file dependencies requiring filelists metadata, no
issues with official repositories are anticipated.

If you encounter any problems while resolving a transaction with a
third-party package that doesn't align with the Fedora Packaging
Guidelines, DNF will provide a hint to the user. In such cases, you can
manually fix the situation by explicitly requesting the filelists metadata
using the `--setopt=optional_metadata_types=filelists` CLI parameter.

Wishing everyone smooth and faster updates!

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

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

[Sérgio Basto]

On Fri, 2024-02-09 at 13:21 +0100, Marc Deop i Argemí wrote:
> On Friday, 9 February 2024 11:53:01 CET Sérgio Basto wrote:
> > so you agree that are giving the overhead to us (the people who
> > want
> > keep X11 as it is )
> 
> Yes!!! OF COURSE!
> 
> If you wanna maintain something you need to handle the overhead! Not
> the other 
> way around!

ah ok, you can give overhead to others because is not your problem, but
others can't maintain X11 because gives overhead to you. 

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

Re: Fwd: Unresponsive maintainer: petersen / Pandoc package not updated since June 2023: Security vulnerability, CVE-2023-35936 (medium)

[Christopher Klooz]

Thanks! :)

On 09/02/2024 13.18, Luna Jernberg wrote:

CCed his work email in case he looks there

-- Forwarded message -
Från: Christopher Klooz 
Date: fre 9 feb. 2024 kl 13:05
Subject: Unresponsive maintainer: petersen / Pandoc package not updated
since June 2023: Security vulnerability, CVE-2023-35936 (medium)
To: Development discussions related to Fedora https://koji.fedoraproject.org/koji/packageinfo?packageID=11560

[2] https://hackage.haskell.org/package/pandoc &
https://github.com/jgm/pandoc

[3] https://github.com/jgm/pandoc/releases?page=1

[4] https://github.com/jgm/pandoc/releases?page=2

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


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

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

[Marc Deop i Argemí]

On Friday, 9 February 2024 11:53:01 CET Sérgio Basto wrote:
> so you agree that are giving the overhead to us (the people who want
> keep X11 as it is )

Yes!!! OF COURSE!

If you wanna maintain something you need to handle the overhead! Not the other 
way around!

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

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

[Marc Deop i Argemí]

On Friday, 9 February 2024 04:15:17 CET Kevin Kofler via devel wrote:
> Well, then kwin-x11 will also no longer depend on kwin 

YE

> and your argument
> that it is a problem because it introduces a hard version lock will be moot.

Well, there would be no argument to be "moot" because there would be no 
problem, would it?

;-)

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

Fwd: Unresponsive maintainer: petersen / Pandoc package not updated since June 2023: Security vulnerability, CVE-2023-35936 (medium)

[Luna Jernberg]

CCed his work email in case he looks there

-- Forwarded message -
Från: Christopher Klooz 
Date: fre 9 feb. 2024 kl 13:05
Subject: Unresponsive maintainer: petersen / Pandoc package not updated
since June 2023: Security vulnerability, CVE-2023-35936 (medium)
To: Development discussions related to Fedora 


I cannot reach the maintainer petersen (see mail below): The package
"pandoc" remains at 3.1.3 in Fedora, but pandoc is already at 3.1.11.1.
Among the updates since 3.1.3, there have been two security-critical
(including the medium CVE-2023-35936. Security fixes are in 3.1.4 & 3.1.6).

The actual risk is limited, but these should be updated nevertheless.

Does anyone know how to reach him by other means?

Regards,
Chris


 Forwarded Message 
Subject: Fedora package "pandoc" outdated and contains security
vulnerability
Date: Thu, 1 Feb 2024 15:55:09 +0100
From: py0...@posteo.net
To: peter...@fedoraproject.org

Hi petersen,

I am reaching out because of the package "pandoc", which you maintain.

I have seen that the package is still at version 3.1.3 [1] when I tried to
install it with dnf, whereas the current version is 3.1.11.1 [2]: is this
intended or an accident?

It has to be noted that the updates that have been added in the meantime
contain fixes for security vulnerabilities (at least CVE-2023-35936; I have
just roughly skimmed the changelogs). So at the moment, it seems the Fedora
build can be exploited by attackers in some circumstances [3] [4] because
it is still at 3.1.3.

Regards & thanks for maintaining,

Chris

[1] https://koji.fedoraproject.org/koji/packageinfo?packageID=11560

[2] https://hackage.haskell.org/package/pandoc &
https://github.com/jgm/pandoc

[3] https://github.com/jgm/pandoc/releases?page=1

[4] https://github.com/jgm/pandoc/releases?page=2

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

Unresponsive maintainer: petersen / Pandoc package not updated since June 2023: Security vulnerability, CVE-2023-35936 (medium)

[Christopher Klooz]

I cannot reach the maintainer petersen (see mail below): The package 
"pandoc" remains at 3.1.3 in Fedora, but pandoc is already at 3.1.11.1. 
Among the updates since 3.1.3, there have been two security-critical 
(including the medium CVE-2023-35936. Security fixes are in 3.1.4 & 3.1.6).


The actual risk is limited, but these should be updated nevertheless.

Does anyone know how to reach him by other means?

Regards,
Chris



 Forwarded Message 
Subject: 	Fedora package "pandoc" outdated and contains security 
vulnerability

Date:   Thu, 1 Feb 2024 15:55:09 +0100
From:   py0...@posteo.net
To: peter...@fedoraproject.org



Hi petersen,

I am reaching out because of the package "pandoc", which you maintain.

I have seen that the package is still at version 3.1.3 [1] when I tried 
to install it with dnf, whereas the current version is 3.1.11.1 [2]: is 
this intended or an accident?


It has to be noted that the updates that have been added in the meantime 
contain fixes for security vulnerabilities (at least CVE-2023-35936; I 
have just roughly skimmed the changelogs). So at the moment, it seems 
the Fedora build can be exploited by attackers in some circumstances [3] 
[4] because it is still at 3.1.3.


Regards & thanks for maintaining,

Chris

[1] https://koji.fedoraproject.org/koji/packageinfo?packageID=11560

[2] https://hackage.haskell.org/package/pandoc & 
https://github.com/jgm/pandoc


[3] https://github.com/jgm/pandoc/releases?page=1

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

[rpms/cpanspec] PR #3: Preparation of new build

[Michal Josef Špaček]

mspacek opened a new pull-request against the project: `cpanspec` that you are 
following:
``
Preparation of new build
``

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

[rpms/cpanspec] PR #2: Use `dnf repoquery --whatprovides`, not `dnf whatprovides`

[Michal Josef Špaček]

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

Merged pull-request:

``
Use `dnf repoquery --whatprovides`, not `dnf whatprovides`
``

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

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

[Sérgio Basto]

On Thu, 2024-02-08 at 22:04 -0500, Steve Cossette wrote:
> I
> On Thu, Feb 8, 2024 at 9:51 PM Sérgio Basto 
> wrote:
> > On Thu, 2024-02-08 at 20:43 +0100, Fabio Valentini wrote:
> > > On Thu, Feb 8, 2024 at 12:33 PM Sérgio Basto 
> > > wrote:
> > > > 
> > > > On Wed, 2024-02-07 at 16:03 +0100, Marc Deop i Argemí wrote:
> > > > > We are not banning nor deleting anything. We are not
> > > > > _supporting_
> > > > > it.
> > > > 
> > > > 
> > > > you are removing X11 from the builds deliberately , when
> > > > many people , members of Fedora on devel mailing list, express
> > > > that
> > > > they want have X11 , in fact we have many people that defend
> > > > keep
> > > > X11 .
> > > 
> > > One thing that seems to be overlooked in many of the posts on
> > > this
> > > thread:
> > > 
> > > Nobody can *force* the KDE Plasma maintainers to do *anything*,
> > > just
> > > like nobody can force *any* packager to do anything. 
> > 
> > nobody can force me use wayland , we volunteer maintain KDE Plasma
> > X11
> > , why do you think, we want force someone to do anything ? they are
> > force us do a new packages, they remove X11 without consensus, they
> > can
> > leave the packages alone . 
> > 
> > > Fedora a
> > > volunteer-run project. We're mostly doing this "for fun" (or at
> > > least,
> > > some definition of "fun"). So if the KDE Plasma maintainers / the
> > > KDE
> > > SIG decides that they do not want to keep supporting the Plasma /
> > > X11
> > > session, that is their choice. However, I am not sure whether I
> > > like
> > > it or not that there's an ongoing effort to add this
> > > functionality
> > > back with separate packages.
> > > 
> > > For me, the only acceptable way to do this would be in a way that
> > > does
> > > in no way make maintaining the Plasma / Wayland packages more
> > > difficult or burdensome, since the original intent of dropping
> > > the
> > > Plasma / X11 session was to *lower* the maintenance burden.
> > 
> > It is a false excuse and not true, is not more difficult nor
> > burdensome, we had many burdensome with the default be wayland and
> > hundreds of bugs opened and never fixed with crashes only on
> > wayland
> > session .  
> > 
> > >   Adding
> > > back the Plasma / X11 session with separate packages might cause
> > > additional overhead for the KDE SIG (for example, needing to
> > > update
> > > kwin-x11 whenever there is a kwin update). 
> > 
> > is the opposite, KDE SIG are causing additional overhead to who
> > want
> > use X11 and the package maintainer forcing use of wayland and why
> > does
> > the will of KDE SIG have to prevail? 
> > 
> > I also maintain many KDE packages and I had a overhead with wayland
> > crashes 
> > 
> > > That would be the "usual"
> > > way to handle this according to Fedora policies.
> > > 
> > 
> > The usual is, if someone want maintain the package , they can
> > maintain
> > it, no one complains about an hypothetical burden
> > 
> > > However, that would be counter to the original purpose of
> > > dropping
> > > the
> > > functionality from the packages maintained by the KDE SIG. But
> > > again,
> > > nobody can *force* package maintainers to support something they
> > > don't
> > > want to support. 
> > 
> > They don't have support X11 , they have the work of keep the
> > removal of
> > X11 in their packages  .
> > 
> > Other thing that KDE SIG misses , is how testing , let says, as
> > usual,
> > some app crash , and we ask have you wayland session or X11
> > session, if
> > you have wayland try X11 , if it runs at X11 and crash on wayland ,
> > this fact can help find the problem and not the opposite . 
> > 
> > also in kde-wayland you can run in x11 envoirment with env
> > QT_QPA_PLATFORM=xcb 
> > 
> > So just thinking removing this part of the functionalities on KDE ,
> > IMHO is lack of knowledge of graphics and bad for Fedora. IMHO the
> > future is have both technologies and not replace it 
> > 
> > 
> > Is very sad read that some people think in remove it and force
> > people
> > use an technology that they think that don't have some important
> > features and issues in his opinions , is less important than false
> > argumentation , that will give burden . when they are burned to who
> > want use X11 
> > 
> > 
> > 
> > 
> > > So in this case, I think it would be good to have
> > > something like a clarification to the Updates Policy (and / or
> > > other
> > > policies, as necessary) for this case to resolve the
> > > contradiction -
> > > something like "updates for KDE Plasma packages are not required
> > > to
> > > be
> > > coordinated with packages for the Plasma / X11 session".
> > > 
> > > I'm also unsure how handling bug reports would best work in this
> > > situation. People *will* report bugs against the wrong
> > > components,
> > > causing additional work for the KDE SIG. (Hell, I'm getting bug
> > > reports filed against elementary / Pantheon packages, and there's
> > > not
> > > even a usable Pantheon 

Re: [heads up] mass rebuild for opencv 4.9.0 with soname bump on rawhide

[Frantisek Zatloukal]

On Fri, Feb 9, 2024 at 2:16 AM Sérgio Basto  wrote:

> MLT built [1] (with one workaround for GCC for x86_64).
>
> [1]
> https://bodhi.fedoraproject.org/updates/FEDORA-2024-7b5199d4f6
>
>
Thanks a lot, krita rebuilt:
https://bodhi.fedoraproject.org/updates/FEDORA-2024-324af7694e

-- 

Best regards / S pozdravem,

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

Unresponsive packagers: yangrr

[Pierre-Yves Chibon]

Good Morning Everyone,

Since January 17th, we have been emailing daily the following user to notify
that the email they have set in FAS does not correspond to a valid bugzilla
account.
This is a requirement for Fedora packagers.

Does someone know how to contact yangrr?

yangrr is watching rpms/0x
yangrr is watching rpms/hstr
yangrr is maintainer of rpms/kexec-tools


Thanks for your help,

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

Unresponsive packagers: nknazeko

[Pierre-Yves Chibon]

Good Morning Everyone,

Since November 1st, we have been emailing daily the following user to notify
that the email they have set in FAS does not correspond to a valid bugzilla
account.
This is a requirement for Fedora packagers.

Does someone know how to contact nknazeko?

nknazeko is maintainer of rpms/selinux-policy


Thanks for your help,

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

Re: OpenSSL 3.2.1 available in rawhide

[Dmitry Belyavskiy]

Dear Yaakov,



On Fri, Feb 9, 2024 at 4:51 AM Yaakov Selkowitz  wrote:

> On Thu, 2024-02-08 at 20:37 +0100, Sahana Prasad wrote:
> > Hello everyone,
> > OpenSSL 3.2.1 is now available in rawhide [1].
> > There are no API/ABI changes in comparison with the last version in
> > rawhide
> > (3.1.4).
> > This version (3.2.0 onwards) supports PQ algorithms that can be
> > loaded
> > through
> > the OQS provider.
> > A few tests that needed some downstream tweaks have been disabled and
> > being
> > worked on.
> > Other than this issue [2] upstream, we did not see any new
> > failures/breakages.
> >
> > If you observe any new issues with this new version, kindly report a
> > bug.
>
> Would this be related to openssl 3.2.1?
>
> https://koji.fedoraproject.org/koji/taskinfo?taskID=113198856
>
> The tests pass locally in mock with openssl 3.1.4.


I can imagine the situation where upgrading to 3.2 could cause this failure
but the logs are too vague.
Could you please provide more details (e.g. openssl low-level diagnostics)
or even better a minimal reproducer for diagnostics?

As for now we don't see any significant regressions in our downstream tests.

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