Re: PDC replacement proposal

[Tomas Hrcka]

Ok, now we are on the same page.

On Wed, Sep 13, 2023 at 8:04 PM Adam Williamson 
wrote:

> On Wed, 2023-09-13 at 16:49 +0200, Tomas Hrcka wrote:
> > I thought this was exactly the JSON blob we will implement, If you look
> at
> > the model of PDC
> >
> https://product-definition-center.github.io/product-definition-center/_images/overview.svg
> >
> > Those endpoints are covered by relations Release, Compose, RPM through
> some
> > others.
> > The PDC approach is more or less a normalized RDBMS model.
> > This should be replaceable by a much simpler denormalized approach and
> > create one entry for each compose with all the data in one place.
>
> That's missing the 'composes' endpoint use (#1 in my list below). Not
> sure if that's your fault or mine, sorry if I left it out of a previous
> list.
>
> Does your replacement plan cover the "previous_release" use case, where
> we need a list of all the composes for each release in the order they
> happened?
>
>
Yes idea was to have the compose_id as a document root since it is unique
for each compose.
something like this:

Fedora-Rawhide-20230913.n.0:{
compose_related_metadata:[metadata0:metadata,metadata1:metadata]
rpms:[nvr:other_rdata,nvr1:other_rdata1]
images:{Fedora-Sway-Live-x86_64-Rawhide-20230913.n.0.iso:"some metadata"}
}

If we store the data in the correct format for fedfind use case we can
minimize the number of operations that are needed compared to REST API.

I will start working on this on the 15th. My idea is to start with the data
format, Once that is sorted out.

Just a friendly reminder we will not drop PDC suddenly. The plan is to
implement the new solution and have it running in parallel with PDC for a
while,
Once we are sure everything is working we will start to sunset PDC.


> Thanks!
> --
> Adam Williamson (he/him/his)
> Fedora QA
> Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org
> https://www.happyassassin.net
>
>
>
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>


-- 
Tomas Hrcka
fas: humaton
libera.CHAT: jednorozec
___
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 2238633] perltidy-20230912 is available

[bugzilla]

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



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

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


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

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

[Bug 2238025] perltidy-20230909 is available

[bugzilla]

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



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

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


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

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

[Bug 2235322] perl-Crypt-CBC-3.04 of RHEL9 can not decrypt ciphertext created with 'header' => 'randomiv'

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-Crypt-CBC-3.04-13.el9  |perl-Crypt-CBC-3.04-13.el9
   |perl-Crypt-CBC-3.04-13.fc37 |perl-Crypt-CBC-3.04-13.fc37
   ||perl-Crypt-CBC-3.04-13.fc38



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


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202235322%23c11
___
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 2235322] perl-Crypt-CBC-3.04 of RHEL9 can not decrypt ciphertext created with 'header' => 'randomiv'

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-Crypt-CBC-3.04-13.el9  |perl-Crypt-CBC-3.04-13.el9
   ||perl-Crypt-CBC-3.04-13.fc37



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


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

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

[Bug 2238875] New: perl-MCE-1.889 is available

[bugzilla]

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

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



Releases retrieved: 1.889
Upstream release that is considered latest: 1.889
Current version/release in rawhide: 1.888-2.fc39
URL: http://search.cpan.org/dist/MCE/

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


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


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202238875%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 2235322] perl-Crypt-CBC-3.04 of RHEL9 can not decrypt ciphertext created with 'header' => 'randomiv'

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Resolution|--- |ERRATA
 Status|ON_QA   |CLOSED
   Fixed In Version||perl-Crypt-CBC-3.04-13.el9
Last Closed||2023-09-14 00:31:56



--- Comment #9 from Fedora Update System  ---
FEDORA-EPEL-2023-2af18ec68f has been pushed to the Fedora EPEL 9 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=2235322

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202235322%23c9
___
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: F40 Change Proposal: KDE Plasma 6 (System Wide)

[Adam Williamson]

On Wed, 2023-09-13 at 19:48 -0400, Neal Gompa wrote:
> On Wed, Sep 13, 2023 at 7:45 PM Ian Laurie  wrote:
> > 
> > On 9/14/23 05:58, František Šumšal wrote:
> > > I second this as well. I tried to use Wayland with Plasma, but there's
> > > a weird issue where with a multi-monitor setup, switching focus from
> > 
> > I have repeatedly tried Plasma on Wayland as VirtualBox guests and it
> > simply doesn't work.  There is a weird 10 to 20 pixel offset between the
> > visible mouse pointer and  what the GUI thinks is being pointed at...
> > which makes the GUI unusable.  I've reported this problem in the deep
> > dark past somewhere but nothing was done about it.  I've seen the
> > problem as recently as F38 during its beta period.  Plasma on X11 works
> > as expected.
> > 
> > I'm an Xfce user so my care factor is minimal.  I've not tried Plasma on
> > Wayland in the 39 branch yet but I do intend to.
> > 
> 
> Would you please report this to bugs.kde.org if it shows up in Fedora
> 39 KDE Beta? 
> https://bugs.kde.org/enter_bug.cgi?product=kwin=wayland-generic

There is https://bugs.kde.org/show_bug.cgi?id=427060 and
https://bugs.kde.org/show_bug.cgi?id=449331 which is marked as a dupe
of it. Later comments on 427060 indicate some folks still have issues
with this.

My personal bugbear that I'd really like fixed is:
https://bugzilla.redhat.com/show_bug.cgi?id=2016563
https://gitlab.freedesktop.org/spice/linux/vd_agent/-/issues/26

not being able to copy from or paste into KDE VMs is extremely
annoying, especially for testing.
-- 
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org
https://www.happyassassin.net



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

[Bug 2238870] New: perl-Test2-Suite-0.000156 is available

[bugzilla]

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

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



Releases retrieved: 0.000156
Upstream release that is considered latest: 0.000156
Current version/release in rawhide: 0.000155-3.fc39
URL: http://search.cpan.org/dist/Test2-Suite/

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


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


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202238870%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: F40 Change Proposal: KDE Plasma 6 (System Wide)

[Ian Laurie]

On 9/14/23 09:48, Neal Gompa wrote:

On Wed, Sep 13, 2023 at 7:45 PM Ian Laurie  wrote:

I'm an Xfce user so my care factor is minimal.  I've not tried Plasma on
Wayland in the 39 branch yet but I do intend to.



Would you please report this to bugs.kde.org if it shows up in Fedora
39 KDE Beta? 
https://bugs.kde.org/enter_bug.cgi?product=kwin=wayland-generic


I'll try to do this Saturday my time.  I'll also report results here.

--
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: F40 Change Proposal: KDE Plasma 6 (System Wide)

[Neal Gompa]

On Wed, Sep 13, 2023 at 7:45 PM Ian Laurie  wrote:
>
> On 9/14/23 05:58, František Šumšal wrote:
> > I second this as well. I tried to use Wayland with Plasma, but there's
> > a weird issue where with a multi-monitor setup, switching focus from
>
> I have repeatedly tried Plasma on Wayland as VirtualBox guests and it
> simply doesn't work.  There is a weird 10 to 20 pixel offset between the
> visible mouse pointer and  what the GUI thinks is being pointed at...
> which makes the GUI unusable.  I've reported this problem in the deep
> dark past somewhere but nothing was done about it.  I've seen the
> problem as recently as F38 during its beta period.  Plasma on X11 works
> as expected.
>
> I'm an Xfce user so my care factor is minimal.  I've not tried Plasma on
> Wayland in the 39 branch yet but I do intend to.
>

Would you please report this to bugs.kde.org if it shows up in Fedora
39 KDE Beta? 
https://bugs.kde.org/enter_bug.cgi?product=kwin=wayland-generic



-- 
真実はいつも一つ！/ 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: F40 Change Proposal: KDE Plasma 6 (System Wide)

[Scott Talbert]

On Wed, 13 Sep 2023, Neal Gompa wrote:


On Wed, Sep 13, 2023 at 7:02 PM Steven A. Falco  wrote:


On 9/13/23 05:23 PM, Neal Gompa wrote:

Right. And I want to stress we are not dropping support for X11
applications. Anything running as an X client in a desktop should work
as it has before.


I'm not convinced KiCad will work in that scenario, so please let me summarize 
what I've read here, and please correct me if I have any of this wrong.

The thing being removed is "Plasma(X11)", which is a native X11 stack; i.e. no 
Wayland or Xwayland is involved when using Plasma(X11).  This mode is well supported by 
KiCad, and additionally it works well with my multi-monitor setup.

Should the change proposal be accepted, "Plasma(X11)" will be removed, leaving 
"Plasma(Wayland)" as the only available KDE mode.  Also, all X11 applications will then 
be forced to use XWayland rather than X11, at least under KDE.

Assuming my summary is correct, here are my personal problems:

Problem 1: The KiCad team says they don't support XWayland (nor do they support 
pure Wayland) because of bugs.



From what I've read through the issues, the ultimate problem is in
GTK, not wxWidgets, as there is in fact a supported Wayland protocol
for mouse warping[1]. Does this issue exist when using wxQt instead of
wxGTK? Admittedly, I'm not sure of the state of things with wxWidgets
and the backends...

[1]: https://wayland.app/protocols/pointer-constraints-unstable-v1


wxQt port is experimental at this point.  I'm not aware of it being used 
widely.


wxWidgets would be glad to support cursor warping on Wayland.  It just 
needs someone who knows how do it to implement it, if GTK isn't going to 
offer an API.


Does QCursor::setPos() work on Wayland?

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

Re: F40 Change Proposal: KDE Plasma 6 (System Wide)

[Ian Laurie]

On 9/14/23 05:58, František Šumšal wrote:

I second this as well. I tried to use Wayland with Plasma, but there's
a weird issue where with a multi-monitor setup, switching focus from


I have repeatedly tried Plasma on Wayland as VirtualBox guests and it
simply doesn't work.  There is a weird 10 to 20 pixel offset between the
visible mouse pointer and  what the GUI thinks is being pointed at...
which makes the GUI unusable.  I've reported this problem in the deep
dark past somewhere but nothing was done about it.  I've seen the
problem as recently as F38 during its beta period.  Plasma on X11 works
as expected.

I'm an Xfce user so my care factor is minimal.  I've not tried Plasma on
Wayland in the 39 branch yet but I do intend to.

--
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: F40 Change Proposal: KDE Plasma 6 (System Wide)

[Steven A. Falco]

On 9/13/23 07:16 PM, Neal Gompa wrote:

On Wed, Sep 13, 2023 at 7:02 PM Steven A. Falco  wrote:


On 9/13/23 05:23 PM, Neal Gompa wrote:

Right. And I want to stress we are not dropping support for X11
applications. Anything running as an X client in a desktop should work
as it has before.


I'm not convinced KiCad will work in that scenario, so please let me summarize 
what I've read here, and please correct me if I have any of this wrong.

The thing being removed is "Plasma(X11)", which is a native X11 stack; i.e. no 
Wayland or Xwayland is involved when using Plasma(X11).  This mode is well supported by 
KiCad, and additionally it works well with my multi-monitor setup.

Should the change proposal be accepted, "Plasma(X11)" will be removed, leaving 
"Plasma(Wayland)" as the only available KDE mode.  Also, all X11 applications will then 
be forced to use XWayland rather than X11, at least under KDE.

Assuming my summary is correct, here are my personal problems:

Problem 1: The KiCad team says they don't support XWayland (nor do they support 
pure Wayland) because of bugs.




From what I've read through the issues, the ultimate problem is in

GTK, not wxWidgets, as there is in fact a supported Wayland protocol
for mouse warping[1]. Does this issue exist when using wxQt instead of
wxGTK? Admittedly, I'm not sure of the state of things with wxWidgets
and the backends...

[1]: https://wayland.app/protocols/pointer-constraints-unstable-v1


Problem 2: Plasma(Wayland) doesn't work with my multi-monitor setup.



Do you have a bug report filed at bugs.kde.org about your setup? The
KDE folks can take a look and we can try to have things fixed in
Plasma (in Plasma 5 today or Plasma 6 when it lands).


Conclusion: If there are remaining Fedora desktops using X11, I might be able 
to continue using Fedora, and I might be able to continue supporting KiCad, 
_assuming_ I'm willing to switch to another desktop.  Of course, after having 
used KDE for 20+ years, switching is not very appealing, nor is it very likely, 
frankly.



Part of the reason for filing this Change is to shake out these cases
and make sure we can get them covered. For what it's worth, I want you
to have a good experience on Plasma Wayland, and I'm happy to help try
to facilitate that however I can.


Thanks, I appreciate that.  I'll give Plasma(Wayland) another try soon and 
write some bugs.

Steve

___
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: F40 Change Proposal: KDE Plasma 6 (System Wide)

[Neal Gompa]

On Wed, Sep 13, 2023 at 7:02 PM Steven A. Falco  wrote:
>
> On 9/13/23 05:23 PM, Neal Gompa wrote:
> > Right. And I want to stress we are not dropping support for X11
> > applications. Anything running as an X client in a desktop should work
> > as it has before.
>
> I'm not convinced KiCad will work in that scenario, so please let me 
> summarize what I've read here, and please correct me if I have any of this 
> wrong.
>
> The thing being removed is "Plasma(X11)", which is a native X11 stack; i.e. 
> no Wayland or Xwayland is involved when using Plasma(X11).  This mode is well 
> supported by KiCad, and additionally it works well with my multi-monitor 
> setup.
>
> Should the change proposal be accepted, "Plasma(X11)" will be removed, 
> leaving "Plasma(Wayland)" as the only available KDE mode.  Also, all X11 
> applications will then be forced to use XWayland rather than X11, at least 
> under KDE.
>
> Assuming my summary is correct, here are my personal problems:
>
> Problem 1: The KiCad team says they don't support XWayland (nor do they 
> support pure Wayland) because of bugs.
>

From what I've read through the issues, the ultimate problem is in
GTK, not wxWidgets, as there is in fact a supported Wayland protocol
for mouse warping[1]. Does this issue exist when using wxQt instead of
wxGTK? Admittedly, I'm not sure of the state of things with wxWidgets
and the backends...

[1]: https://wayland.app/protocols/pointer-constraints-unstable-v1

> Problem 2: Plasma(Wayland) doesn't work with my multi-monitor setup.
>

Do you have a bug report filed at bugs.kde.org about your setup? The
KDE folks can take a look and we can try to have things fixed in
Plasma (in Plasma 5 today or Plasma 6 when it lands).

> Conclusion: If there are remaining Fedora desktops using X11, I might be able 
> to continue using Fedora, and I might be able to continue supporting KiCad, 
> _assuming_ I'm willing to switch to another desktop.  Of course, after having 
> used KDE for 20+ years, switching is not very appealing, nor is it very 
> likely, frankly.
>

Part of the reason for filing this Change is to shake out these cases
and make sure we can get them covered. For what it's worth, I want you
to have a good experience on Plasma Wayland, and I'm happy to help try
to facilitate that however I can.


-- 
真実はいつも一つ！/ 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: F40 Change Proposal: KDE Plasma 6 (System Wide)

[Steven A. Falco]

On 9/13/23 05:23 PM, Neal Gompa wrote:

Right. And I want to stress we are not dropping support for X11
applications. Anything running as an X client in a desktop should work
as it has before.


I'm not convinced KiCad will work in that scenario, so please let me summarize 
what I've read here, and please correct me if I have any of this wrong.

The thing being removed is "Plasma(X11)", which is a native X11 stack; i.e. no 
Wayland or Xwayland is involved when using Plasma(X11).  This mode is well supported by 
KiCad, and additionally it works well with my multi-monitor setup.

Should the change proposal be accepted, "Plasma(X11)" will be removed, leaving 
"Plasma(Wayland)" as the only available KDE mode.  Also, all X11 applications will then 
be forced to use XWayland rather than X11, at least under KDE.

Assuming my summary is correct, here are my personal problems:

Problem 1: The KiCad team says they don't support XWayland (nor do they support 
pure Wayland) because of bugs.

Problem 2: Plasma(Wayland) doesn't work with my multi-monitor setup.

Conclusion: If there are remaining Fedora desktops using X11, I might be able 
to continue using Fedora, and I might be able to continue supporting KiCad, 
_assuming_ I'm willing to switch to another desktop.  Of course, after having 
used KDE for 20+ years, switching is not very appealing, nor is it very likely, 
frankly.

Steve

___
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 2238862] New: perl-GD-Barcode-2.00 is available

[bugzilla]

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

Bug ID: 2238862
   Summary: perl-GD-Barcode-2.00 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-GD-Barcode
  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
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 2.00
Upstream release that is considered latest: 2.00
Current version/release in rawhide: 1.15-44.fc39
URL: http://search.cpan.org/dist/GD-Barcode/

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


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


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202238862%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: The new Change discussion process is painful

[Kevin Kofler via devel]

Chris Adams wrote:
> Do we really need to keep re-litigating decisions that some people don't
> agree with?

FESCo has set a precedent showing how effective that can be:
https://pagure.io/fesco/issue/2923

So complain to them if you have an issue with decisions getting rehashed for 
rediscussion.

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: The new Change discussion process is painful

[Chris Adams]

Once upon a time, Kevin Kofler  said:
> Matthew Miller wrote:
> > Even if you don't want to follow Fedora Discussion in general, to follow
> > changes, you can go subscribe to just those by email.
> 
> But I do not want to get the messages by e-mail.

Do we really need to keep re-litigating decisions that some people don't
agree with?
-- 
Chris Adams 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: F40 Change Proposal: KDE Plasma 6 (System Wide)

[Kevin Kofler via devel]

Neal Gompa wrote:
> Right. And I want to stress we are not dropping support for X11
> applications. Anything running as an X client in a desktop should work
> as it has before.

Should. But that does not necessarily mean it actually does.

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: F40 Change Proposal: KDE Plasma 6 (System Wide)

[Kevin Kofler via devel]

Fabio Valentini wrote:
> I doubt that the intention is to drop X11 sessions entirely and make
> "Plasma Wayland" the only session available on Fedora *in general*,
> but rather that the "Plasma X11" session will be dropped, and that
> "Plasma Wayland" will be the only *Plasma* session available.

Even that is not going to happen. I do not see how they want to stop me from 
shipping a plasma-x11 package.

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: The new Change discussion process is painful

[Kevin Kofler via devel]

Matthew Miller wrote:
> Even if you don't want to follow Fedora Discussion in general, to follow
> changes, you can go subscribe to just those by email.

But I do not want to get the messages by e-mail. I want to use the one 
protocol actually designed for discussions, NNTP. Gmane allows following 
mailing lists with that protocol. It works great. But it only works with 
real mailing lists, not with the Discourse developers' attempts at emulating 
the user experience.

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: F40 Change Proposal: KDE Plasma 6 (System Wide)

[Neal Gompa]

On Wed, Sep 13, 2023 at 5:24 PM Fabio Valentini  wrote:
>
> On Wed, Sep 13, 2023 at 11:19 PM Steven A. Falco  
> wrote:
> >
> > A question about this - the removal of X11 is listed on a change proposal 
> > for KDE.  Does the removal just apply to KDE or would it be distribution 
> > wide; i.e. affecting all desktops?
>
> I assume the following is not meant literally:
>
> """
> For Fedora Linux, the
> transition to KDE Plasma 6 will also include dropping support for the
> X11 session entirely, leaving only Plasma Wayland as the sole offered
> desktop mode.
> """
>
> I doubt that the intention is to drop X11 sessions entirely and make
> "Plasma Wayland" the only session available on Fedora *in general*,
> but rather that the "Plasma X11" session will be dropped, and that
> "Plasma Wayland" will be the only *Plasma* session available.
>

Yes! Sorry if it's ambiguous, it's hard to write this to account for
all the ways it can be interpreted. This is scoped to the KDE Plasma
solution stack.

Other desktops can and will make their own choices on the transition to Wayland.




--
真実はいつも一つ！/ 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: F40 Change Proposal: KDE Plasma 6 (System Wide)

[Neal Gompa]

On Wed, Sep 13, 2023 at 2:46 PM David Edmundson
 wrote:
>
> > will also include dropping support for the X11 session entirely
> > I'm more than a bit concerned about dropping X11
>
> It's important that we separate dropping an X11 session and dropping
> X11 (xwayland). They're two very different topics and you two might be
> talking past each other.
>
> > [xwayland] is an emulation mode and issues arising while using this mode
>
> I would not describe xwayland as an emulation mode. Kwin talks with
> via X11 protocols directly to the client. We certainly aim to support
> it upstream for a long time. If Kicad is best in xwayland, then we
> should run Kicad in xwayland.
>

Right. And I want to stress we are not dropping support for X11
applications. Anything running as an X client in a desktop should work
as it has before.



-- 
真実はいつも一つ！/ 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: F40 Change Proposal: KDE Plasma 6 (System Wide)

[Fabio Valentini]

On Wed, Sep 13, 2023 at 11:19 PM Steven A. Falco  wrote:
>
> A question about this - the removal of X11 is listed on a change proposal for 
> KDE.  Does the removal just apply to KDE or would it be distribution wide; 
> i.e. affecting all desktops?

I assume the following is not meant literally:

"""
For Fedora Linux, the
transition to KDE Plasma 6 will also include dropping support for the
X11 session entirely, leaving only Plasma Wayland as the sole offered
desktop mode.
"""

I doubt that the intention is to drop X11 sessions entirely and make
"Plasma Wayland" the only session available on Fedora *in general*,
but rather that the "Plasma X11" session will be dropped, and that
"Plasma Wayland" will be the only *Plasma* session available.

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

Re: F40 Change Proposal: KDE Plasma 6 (System Wide)

[Steven A. Falco]

On 9/13/23 12:10 PM, Steven A. Falco wrote:

On 9/13/23 11:53 AM, Aoife Moloney wrote:

Wiki  https://fedoraproject.org/wiki/Changes/KDE_Plasma_6



== Summary ==
KDE Plasma 6 is successor to KDE Plasma 5 created by the KDE
Community. It is based on Qt 6 and KDE Frameworks 6 and brings many
changes and improvements over previous versions. For Fedora Linux, the
transition to KDE Plasma 6 will also include dropping support for the
X11 session entirely, leaving only Plasma Wayland as the sole offered
desktop mode.


I'm more than a bit concerned about dropping X11.  I am the packager for KiCad 
on Fedora.  The upstream KiCad team has stated [1] that they won't support 
Wayland issues unless they can be recreated on X11, meaning that I'll be left 
with no way to support the Fedora KiCad packages.

For convenience, here is the relevant part of the KiCad position:

  It is known that KiCad does not work well under Wayland. There are a 
number of known issues with wxWidgets and Wayland. See the wxWidgets bug 
tracker for details [2].  KiCad requests the XWayland compatibility layer when 
starting, however this is an emulation mode and issues arising while using this 
mode need to be recreated under X11 before they will be addressed.  At the 
moment, Wayland has no support for cursor warping, which means that the KiCad 
features of centering the cursor when zooming, and continuously panning the 
canvas, are broken on Wayland systems.

 Steve

[1] https://www.kicad.org/help/known-system-related-issues/
[2] https://github.com/wxWidgets/wxWidgets/labels/Wayland


A question about this - the removal of X11 is listed on a change proposal for 
KDE.  Does the removal just apply to KDE or would it be distribution wide; i.e. 
affecting all desktops?

Steve

___
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 2238849] New: perl-Starman-0.4017 is available

[bugzilla]

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

Bug ID: 2238849
   Summary: perl-Starman-0.4017 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Starman
  Keywords: FutureFeature, Triaged
  Assignee: emman...@seyman.fr
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: emman...@seyman.fr, perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 0.4017
Upstream release that is considered latest: 0.4017
Current version/release in rawhide: 0.4016-3.fc39
URL: http://search.cpan.org/dist/Starman/

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


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


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202238849%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: The new Change discussion process is painful

[Matthew Miller]

On Wed, Sep 13, 2023 at 04:32:34PM -0300, Tulio Magno Quites Machado Filho 
wrote:
> I've been trying this, but Discourse reverted part of my settings without
> any warnings after a few months.
> 
> I raised the issue here:
> https://discussion.fedoraproject.org/t/discourse-dropped-an-email-address-from-my-preferences-today/89614
> 
> I still do not understand what happened 2 days ago.

Sorry, I missed that -- the infrastructure team doesn't actually handle
Discourse. I'll respond to you there.

-- 
Matthew Miller

Fedora Project Leader
___
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: F40 Change Proposal: KDE Plasma 6 (System Wide)

[František Šumšal]

On 9/13/23 21:50, Sérgio Basto wrote:

On Wed, 2023-09-13 at 19:52 +0200, Kevin Kofler via devel wrote:

For Fedora Linux, the transition to KDE Plasma 6 will also include
dropping support for the X11 session entirely, leaving only Plasma
Wayland
as the sole offered desktop mode.


Huh?! Why?! KDE upstream is still supporting X11 in Plasma 6. I see
no
reason to force Wayland upon all users. I do not want Wayland on my
desktop
(it is already enough of a pain that it is forced upon us by Plasma
Mobile
on the PinePhone) and I will have to switch to another distribution
and
orphan all my packages if this happens.



+1 , I still not use wayland , it just crash all the time , smplayer
and I think many other apps simple doesn't work with wayland. other
packages we cann see Exec=env QT_QPA_PLATFORM=xcb /usr/bin/foo [1].
Also packages based on vnc , libvnc, x11vnc I think doesn't support
wayland, xpra also I think that still doesn't work with wayland. I
don't see why we want move to wayland if X11 works very well .


I second this as well. I tried to use Wayland with Plasma, but there's
a weird issue where with a multi-monitor setup, switching focus from
a window on the first monitor to a running Firefox on the second one
would cause random clicks in Firefox that would switch tabs/click on
links on the current page, which was driving me insane. Unfortunately,
I still haven't got around to properly debug that and use X11 instead.
___
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: F40 Change Proposal: KDE Plasma 6 (System Wide)

[Sérgio Basto]

On Wed, 2023-09-13 at 19:52 +0200, Kevin Kofler via devel wrote:
> > For Fedora Linux, the transition to KDE Plasma 6 will also include
> > dropping support for the X11 session entirely, leaving only Plasma
> > Wayland
> > as the sole offered desktop mode.
> 
> Huh?! Why?! KDE upstream is still supporting X11 in Plasma 6. I see
> no 
> reason to force Wayland upon all users. I do not want Wayland on my
> desktop 
> (it is already enough of a pain that it is forced upon us by Plasma
> Mobile 
> on the PinePhone) and I will have to switch to another distribution
> and 
> orphan all my packages if this happens.
> 

+1 , I still not use wayland , it just crash all the time , smplayer
and I think many other apps simple doesn't work with wayland. other
packages we cann see Exec=env QT_QPA_PLATFORM=xcb /usr/bin/foo [1].
Also packages based on vnc , libvnc, x11vnc I think doesn't support
wayland, xpra also I think that still doesn't work with wayland. I
don't see why we want move to wayland if X11 works very well .  


[1]
https://pkgs.rpmfusion.org/cgit/free/ppsspp.git/tree/ppsspp-qt.desktop


>     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

-- 
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: The new Change discussion process is painful

[Tulio Magno Quites Machado Filho]

Matthew Miller  writes:

> Everything is a balance.
>
> Even if you don't want to follow Fedora Discussion in general, to follow
> changes, you can go subscribe to just those by email. 
>
> 1. Sign in you with your Fedora account
>
> 2. Complete creating a Discussion account if you haven't already
>
> 3. Go to https://discussion.fedoraproject.org/my/preferences/tracking
>
> 4. Remove everything from all of the Categores and Teams & Tags dropdowns
>that you don't want. (A few things are populated as defaults.)
>
> 5. Under Categories, add "Change Proposals" to either Watched (which will
>send a notification for every post) or Watching First Post (which does
>what it says).
>
> 6. Go to https://discussion.fedoraproject.org/my/preferences/emails
>
> 7. Change "Send me email when I have a notification" to "always", if it
>isn't already.
>
> 8. Optional: notification messages will set a List-Id corresponding to the
>Change Proposals category. You can set up your mail filters to do what
>you like with those.
>
> 9. To interact, you can either come to the Discussion web interface, or
>just reply to the email notifications.

I've been trying this, but Discourse reverted part of my settings without
any warnings after a few months.

I raised the issue here:
https://discussion.fedoraproject.org/t/discourse-dropped-an-email-address-from-my-preferences-today/89614

I still do not understand what happened 2 days ago.

-- 
Tulio Magno
___
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: An update on RHEL moving to issues.redhat.com

[Neal Gompa]

On Wed, Sep 13, 2023 at 1:45 PM Matthew Miller  wrote:
>
> On Mon, Sep 11, 2023 at 09:20:09AM -0700, Adam Williamson wrote:
> > IIRC it was a condition of that proposal that we wind up on a hosted
> > version of the *open source* release of gitlab, which is something we
> > managed to talk gitlab into doing for us. IMBW, though, it was a while
> > ago.
>
> Short version is: yes, we did talk them into that with an informal plan, and
> then someone higher up at gitlab pulled the plug on the idea.
>
> At this point, we need to step back and re-evaluate all of our options. I'm
> open to the idea of a revitalized pagure as one of the possibilities, but
> before I'd personally back that, I'd like to see it _really_ revitalized...
> it needs to be more than a heroic effort by a few people. Otherwise, we'll
> be back in the same place in few years.
>

It's slow-going, but the community building is happening again. It's
going to be a lot easier to push that further along once the cleanups
that Dominik and I have planned are done and 6.0 is out.



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

[Bug 2238817] perl-Data-Visitor for EL9

[bugzilla]

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

Paul Howarth  changed:

   What|Removed |Added

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



--- Comment #1 from Paul Howarth  ---
https://pagure.io/releng/fedora-scm-requests/issue/56296 (perl-Tie-ToObject)
https://pagure.io/releng/fedora-scm-requests/issue/56297 (perl-Data-Visitor)

I'll do these but you're welcome to co-maintain if you like.


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

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

[Bug 2238831] New: perl-Term-Table-0.017 is available

[bugzilla]

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

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



Releases retrieved: 0.017
Upstream release that is considered latest: 0.017
Current version/release in rawhide: 0.016-7.fc39
URL: http://search.cpan.org/dist/Term-Table/

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


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


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202238831%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: The new Change discussion process is painful

[Stephen Smoogen]

On Wed, 13 Sept 2023 at 14:14, Adam Williamson 
wrote:

> On Wed, 2023-09-13 at 20:07 +0200, Kevin Kofler via devel wrote:
> > Adam Williamson wrote:
> > > From there, it's up to people where they see and respond to them.
> >
> > But every single announcement gets a reply on the mailing list (which is
> not
> > properly threaded in KNode/Gmane, by the way) saying something like:
> >
> > > The discussion thread to provide feedback for this change proposal can
> be
> > > found here https://yaddayadda.example.com/blablabla
> >
> > With this kind of wording, is it any wonder that people take that as
> > mandatory and discussion on the mailing list has almost entirely drowned
> > out? (The only Change that gets any discussion here seems to be the
> Plasma 6
> > one, and only because it contains a completely outrageous
> downstream-only
> > change hidden in the fine print, silently killing Plasma X11 support.)
>
> No, per Matt's reply, you were right and I was wrong, the intent is to
> direct discussion to Discourse. I was confused because I was just
> following the process documentation (silly me!) which doesn't explain
> any of this.
>
>
The changes to  how discussions were to go to discourse happened around the
same time as Ben was laid off. I think the documentation not getting
updated is just one of ... many things left undone.


-- 
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: The new Change discussion process is painful

[Adam Williamson]

On Wed, 2023-09-13 at 20:07 +0200, Kevin Kofler via devel wrote:
> Adam Williamson wrote:
> > From there, it's up to people where they see and respond to them.
> 
> But every single announcement gets a reply on the mailing list (which is not 
> properly threaded in KNode/Gmane, by the way) saying something like:
> 
> > The discussion thread to provide feedback for this change proposal can be 
> > found here https://yaddayadda.example.com/blablabla
> 
> With this kind of wording, is it any wonder that people take that as 
> mandatory and discussion on the mailing list has almost entirely drowned 
> out? (The only Change that gets any discussion here seems to be the Plasma 6 
> one, and only because it contains a completely outrageous downstream-only 
> change hidden in the fine print, silently killing Plasma X11 support.)

No, per Matt's reply, you were right and I was wrong, the intent is to
direct discussion to Discourse. I was confused because I was just
following the process documentation (silly me!) which doesn't explain
any of this.
-- 
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org
https://www.happyassassin.net



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

[Bug 2238817] New: perl-Data-Visitor for EL9

[bugzilla]

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

Bug ID: 2238817
   Summary: perl-Data-Visitor for EL9
   Product: Fedora EPEL
   Version: epel9
Status: NEW
 Component: perl-Data-Visitor
  Assignee: p...@city-fan.org
  Reporter: xav...@bachelot.org
QA Contact: extras...@fedoraproject.org
CC: iarn...@gmail.com, mspa...@redhat.com,
p...@city-fan.org, perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Hi,

Could you please branch and build perl-Data-Visitor for EPEL 9 ?
I can take care of this if you don't want to. My FAS is xavierb.

Regards,
Xavier


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202238817%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: The new Change discussion process is painful

[Adam Williamson]

On Wed, 2023-09-13 at 13:32 -0400, Matthew Miller wrote:
> On Wed, Sep 13, 2023 at 12:19:05PM +0200, Sandro wrote:
> > On 13-09-2023 08:09, Adam Williamson wrote:
> > > From there, it's up to people where they see and respond to them. If
> > > more people are responding in discourse than on the mailing list, that
> > > would seem to suggest that there*is*  a reason to announce things
> > > there...
> > 
> > I'm quite sure Matthew (mattdm) would disagree with above statement.
> > The idea was/is, iirc, to only announce on both channels, but have
> > the discussion take place on Discourse.
> > 
> > So, making this pick & mix is definitely not the intention and it
> > has already proven futile in a previous mishap.
> 
> Right -- I really don't want to split the conversation. With the telemetry
> change, I didn't ask moderators here to take a heavy hand, because people
> had a lot they wanted to say and I didn't want to squash that.

Ah. Well this hasn't worked out great with the loss of Ben, then,
because none of this new process is actually captured in the docs we're
following to try and keep this process together in the absence of an
official Change wrangler.

https://docs.fedoraproject.org/en-US/program_management/pgm_guide/sop/changes-announce/
doesn't actually mention announcing to Discourse at all, and it
certainly doesn't say anything about e.g. linking to the discourse
thread from the devel-announce@ mail and asking for discussion to be
directed there.
-- 
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org
https://www.happyassassin.net



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

Re: The new Change discussion process is painful

[Adam Williamson]

On Wed, 2023-09-13 at 10:46 +0200, Vít Ondruch wrote:
> Dne 13. 09. 23 v 9:08 Remi Collet napsal(a):
> > Le 13/09/2023 à 08:09, Adam Williamson a écrit :
> > > On Wed, 2023-09-13 at 05:51 +0200, Kevin Kofler via devel wrote:
> > > > Hi,
> > > > 
> > > > it is really a pain that the Change discussion is now hidden in a 
> > > > web forum
> > > > behind a web link, instead of happening right here in this mailing 
> > > > list. It
> > > > was promised that Discourse would NOT replace the mailing lists, but 
> > > > that is
> > > > effectively no longer the case. Can this "Discourse for Change 
> > > > discussion"
> > > > experiment please be stopped? It has no advantages and only adds a 
> > > > useless
> > > > layer of indirection.
> > > 
> > > I don't really understand what you mean. AFAICT, every Change that has
> > > been announced at
> > > https://discussion.fedoraproject.org/c/project/changes/89 has also been
> > > announced at
> > > https://lists.fedoraproject.org/archives/list/devel-announce%40lists.fedoraproject.org/
> > >  
> > > 
> > > , so nothing has been replaced.
> > 
> > Sadly it seems there is some email issues
> > 
> > For a few days, tons of messages are lost
> > so, I also don't receive any of the recent change announcements
> 
> 
> If nothing else, the announcements were previously send to 
> devel-announce with devel in CC, while the CC is not included anymore. 
> IOW can we have devel back in CC, please?

Ah. There's an issue at the moment in that sometimes folks are self-
announcing Changes because we do not have an official change wrangler
ATM (that job went with the program manager position - Aoife and I are
sort of trying to fill in, but it's neither of our actual jobs), and
folks doing that may not know to CC devel@.

Are devel-announce mails not being also sent to devel@ ATM?
Historically they always were. I think we have this issue with test@
and test-announce@, but I didn't realize it also affects devel/devel-
announce.

CCing devel@ is mentioned in
https://docs.fedoraproject.org/en-US/program_management/pgm_guide/sop/changes-announce/
, which I've been directing folks to when they're self-announcing, but
maybe it's easy to miss, and it looks like Aoife forgot it in the round
she announced on Monday.
-- 
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org
https://www.happyassassin.net



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

Re: The new Change discussion process is painful

[Kevin Kofler via devel]

Adam Williamson wrote:
> From there, it's up to people where they see and respond to them.

But every single announcement gets a reply on the mailing list (which is not 
properly threaded in KNode/Gmane, by the way) saying something like:

> The discussion thread to provide feedback for this change proposal can be 
> found here https://yaddayadda.example.com/blablabla

With this kind of wording, is it any wonder that people take that as 
mandatory and discussion on the mailing list has almost entirely drowned 
out? (The only Change that gets any discussion here seems to be the Plasma 6 
one, and only because it contains a completely outrageous downstream-only 
change hidden in the fine print, silently killing Plasma X11 support.)

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 2238816] New: Perl-HTTP-Server-Simple for EL9

[bugzilla]

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

Bug ID: 2238816
   Summary: Perl-HTTP-Server-Simple for EL9
   Product: Fedora EPEL
   Version: epel9
Status: NEW
 Component: perl-HTTP-Server-Simple
  Assignee: spo...@gmail.com
  Reporter: xav...@bachelot.org
QA Contact: extras...@fedoraproject.org
CC: perl-devel@lists.fedoraproject.org, spo...@gmail.com
  Target Milestone: ---
Classification: Fedora



Hi,

Could you please branch and build Perl-HTTP-Server-Simple for EPEL9 ?
I can take care of this if you don't want to. My FAS is xavierb.

Regards,
Xavier


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

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

[Adam Williamson]

On Wed, 2023-09-13 at 16:49 +0200, Tomas Hrcka wrote:
> I thought this was exactly the JSON blob we will implement, If you look at
> the model of PDC
> https://product-definition-center.github.io/product-definition-center/_images/overview.svg
> 
> Those endpoints are covered by relations Release, Compose, RPM through some
> others.
> The PDC approach is more or less a normalized RDBMS model.
> This should be replaceable by a much simpler denormalized approach and
> create one entry for each compose with all the data in one place.

That's missing the 'composes' endpoint use (#1 in my list below). Not
sure if that's your fault or mine, sorry if I left it out of a previous
list.

Does your replacement plan cover the "previous_release" use case, where
we need a list of all the composes for each release in the order they
happened?

Thanks!
-- 
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org
https://www.happyassassin.net



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

Re: F40 Change Proposal: KDE Plasma 6 (System Wide)

[Kevin Kofler via devel]

Kevin Kofler via devel wrote:

>> For Fedora Linux, the transition to KDE Plasma 6 will also include
>> dropping support for the X11 session entirely, leaving only Plasma
>> Wayland as the sole offered desktop mode.
> 
> Huh?! Why?! KDE upstream is still supporting X11 in Plasma 6. I see no
> reason to force Wayland upon all users. I do not want Wayland on my
> desktop (it is already enough of a pain that it is forced upon us by
> Plasma Mobile on the PinePhone) and I will have to switch to another
> distribution and orphan all my packages if this happens.

PS: I would also like to know how the KDE SIG wants to prevent me or other 
interested people from shipping kwin-x11, plasma-x11 or similar packages, 
and how such a dictate would be compatible with the Fedora "Features" and 
"Friends" goals.

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: F40 Change Proposal: KDE Plasma 6 (System Wide)

[Kevin Kofler via devel]

> For Fedora Linux, the transition to KDE Plasma 6 will also include
> dropping support for the X11 session entirely, leaving only Plasma Wayland
> as the sole offered desktop mode.

Huh?! Why?! KDE upstream is still supporting X11 in Plasma 6. I see no 
reason to force Wayland upon all users. I do not want Wayland on my desktop 
(it is already enough of a pain that it is forced upon us by Plasma Mobile 
on the PinePhone) and I will have to switch to another distribution and 
orphan all my packages if this happens.

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: An update on RHEL moving to issues.redhat.com

[Matthew Miller]

On Mon, Sep 11, 2023 at 09:20:09AM -0700, Adam Williamson wrote:
> IIRC it was a condition of that proposal that we wind up on a hosted
> version of the *open source* release of gitlab, which is something we
> managed to talk gitlab into doing for us. IMBW, though, it was a while
> ago.

Short version is: yes, we did talk them into that with an informal plan, and
then someone higher up at gitlab pulled the plug on the idea.

At this point, we need to step back and re-evaluate all of our options. I'm
open to the idea of a revitalized pagure as one of the possibilities, but
before I'd personally back that, I'd like to see it _really_ revitalized...
it needs to be more than a heroic effort by a few people. Otherwise, we'll
be back in the same place in few years.


-- 
Matthew Miller

Fedora Project Leader
___
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: The new Change discussion process is painful

[Matthew Miller]

On Wed, Sep 13, 2023 at 09:08:57AM +0200, Remi Collet wrote:
> Sadly it seems there is some email issues
> 
> For a few days, tons of messages are lost
> so, I also don't receive any of the recent change announcements
> 
> BTW, I agree this dual channel is terrible for discussion
> 
> I personally don't follow discussion.fpo
> too much tools kills simplicity

Everything is a balance.

Even if you don't want to follow Fedora Discussion in general, to follow
changes, you can go subscribe to just those by email. 

1. Sign in you with your Fedora account

2. Complete creating a Discussion account if you haven't already

3. Go to https://discussion.fedoraproject.org/my/preferences/tracking

4. Remove everything from all of the Categores and Teams & Tags dropdowns
   that you don't want. (A few things are populated as defaults.)

5. Under Categories, add "Change Proposals" to either Watched (which will
   send a notification for every post) or Watching First Post (which does
   what it says).

6. Go to https://discussion.fedoraproject.org/my/preferences/emails

7. Change "Send me email when I have a notification" to "always", if it
   isn't already.

8. Optional: notification messages will set a List-Id corresponding to the
   Change Proposals category. You can set up your mail filters to do what
   you like with those.

9. To interact, you can either come to the Discussion web interface, or
   just reply to the email notifications.

-- 
Matthew Miller

Fedora Project Leader
___
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: The new Change discussion process is painful

[Matthew Miller]

On Wed, Sep 13, 2023 at 12:19:05PM +0200, Sandro wrote:
> On 13-09-2023 08:09, Adam Williamson wrote:
> > From there, it's up to people where they see and respond to them. If
> >more people are responding in discourse than on the mailing list, that
> >would seem to suggest that there*is*  a reason to announce things
> >there...
> 
> I'm quite sure Matthew (mattdm) would disagree with above statement.
> The idea was/is, iirc, to only announce on both channels, but have
> the discussion take place on Discourse.
> 
> So, making this pick & mix is definitely not the intention and it
> has already proven futile in a previous mishap.

Right -- I really don't want to split the conversation. With the telemetry
change, I didn't ask moderators here to take a heavy hand, because people
had a lot they wanted to say and I didn't want to squash that.

-- 
Matthew Miller

Fedora Project Leader
___
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: The new Change discussion process is painful

[Maxwell G]

On Wed Sep 13, 2023 at 12:19 +0200, Sandro wrote:
> On 13-09-2023 08:09, Adam Williamson wrote:
> >  From there, it's up to people where they see and respond to them. If
> > more people are responding in discourse than on the mailing list, that
> > would seem to suggest that there*is*  a reason to announce things
> > there...
>
> I'm quite sure Matthew (mattdm) would disagree with above statement. The 
> idea was/is, iirc, to only announce on both channels, but have the 
> discussion take place on Discourse.

Right, people were asked not to comment on the mailing list and some
people just ignored that and replied anyways. That doesn't necessarily
mean that people that followed that request wouldn't have participated
if it was only announced on the mailing list.

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

Re: The new Change discussion process is painful

[Eduard Lucena]

Hello team,

I don't want to enter a terrain where I don't belong, but I want to express
my opinion. Since I understand that you don't want to and don't like the
discourse interface, please take into account community participation in
discussions. And my example is going to be the controversial
"Privacy-preserving Telemetry for Fedora Workstation", on ML, we have 99
comments, but in discourse we are over 500. Maybe it's bad on my part to
assume that you want to actual listen to community feedback and not only to
devs and packager feedback. The process is experimental and needs to be
adjusted, yes; e.g: I propose to don't split discussion in different topics.

I hope you don't drop the discourse, and if you do I will try to keep the
pace a put the proposals into discourse to make them more visible to the
community (adding that the discussion is happening in the ML).


Best regards,
-- 
Eduard Lucena
Móvil: +56962318010
GNU/Linux User #589060
Ubuntu User #8749
Fedora Marketing Representative
___
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: F40 Change Proposal: KDE Plasma 6 (System Wide)

[Neal Gompa]

On Wed, Sep 13, 2023 at 12:12 PM Steven A. Falco  wrote:
>
> On 9/13/23 11:53 AM, Aoife Moloney wrote:
> > Wiki  https://fedoraproject.org/wiki/Changes/KDE_Plasma_6
>
> > == Summary ==
> > KDE Plasma 6 is successor to KDE Plasma 5 created by the KDE
> > Community. It is based on Qt 6 and KDE Frameworks 6 and brings many
> > changes and improvements over previous versions. For Fedora Linux, the
> > transition to KDE Plasma 6 will also include dropping support for the
> > X11 session entirely, leaving only Plasma Wayland as the sole offered
> > desktop mode.
>
> I'm more than a bit concerned about dropping X11.  I am the packager for 
> KiCad on Fedora.  The upstream KiCad team has stated [1] that they won't 
> support Wayland issues unless they can be recreated on X11, meaning that I'll 
> be left with no way to support the Fedora KiCad packages.
>
> For convenience, here is the relevant part of the KiCad position:
>
>   It is known that KiCad does not work well under Wayland. There are a 
> number of known issues with wxWidgets and Wayland. See the wxWidgets bug 
> tracker for details [2].  KiCad requests the XWayland compatibility layer 
> when starting, however this is an emulation mode and issues arising while 
> using this mode need to be recreated under X11 before they will be addressed. 
>  At the moment, Wayland has no support for cursor warping, which means that 
> the KiCad features of centering the cursor when zooming, and continuously 
> panning the canvas, are broken on Wayland systems.
>

It looks like the cursor warping is supported in all major compositors
with the cursor-constraints protocol:
https://wayland.app/protocols/pointer-constraints-unstable-v1

Beyond that, I think it's probably a good idea to get a bug filed with
KDE upstream to get this tracked and figured out with the wxWidgets
folks. Of all the folks involved in the Wayland protocols development,
they are by far the easiest to work with.

There's also a Matrix room about KDE Wayland stuff if you would like
to talk to developers directly about these things:
https://matrix.to/#/#kde-wayland-goal:kde.org




--
真実はいつも一つ！/ 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: The new Change discussion process is painful

[Florian Weimer]

* Pierre-Yves Chibon:

> On Wed, Sep 13, 2023 at 10:46:04AM +0200, Vít Ondruch wrote:
>> If nothing else, the announcements were previously send to devel-announce
>> with devel in CC, while the CC is not included anymore. IOW can we have
>> devel back in CC, please?
>
> I'm pretty sure devel is subscribed to devel-announce, so email sent to
> devel-announce will/should land on devel as well.

This doesn't work with Gmail because it will eat one of the copies.  If
you filter into different folders based on To: addresses, you get the
message only into two folders if the subscription isn't implicit, or
maybe the message to the devel list arrives before the one to
devel-announce for some reason.

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: F40 Change Proposal: KDE Plasma 6 (System Wide)

[Steven A. Falco]

On 9/13/23 11:53 AM, Aoife Moloney wrote:

Wiki  https://fedoraproject.org/wiki/Changes/KDE_Plasma_6



== Summary ==
KDE Plasma 6 is successor to KDE Plasma 5 created by the KDE
Community. It is based on Qt 6 and KDE Frameworks 6 and brings many
changes and improvements over previous versions. For Fedora Linux, the
transition to KDE Plasma 6 will also include dropping support for the
X11 session entirely, leaving only Plasma Wayland as the sole offered
desktop mode.


I'm more than a bit concerned about dropping X11.  I am the packager for KiCad 
on Fedora.  The upstream KiCad team has stated [1] that they won't support 
Wayland issues unless they can be recreated on X11, meaning that I'll be left 
with no way to support the Fedora KiCad packages.

For convenience, here is the relevant part of the KiCad position:

 It is known that KiCad does not work well under Wayland. There are a 
number of known issues with wxWidgets and Wayland. See the wxWidgets bug 
tracker for details [2].  KiCad requests the XWayland compatibility layer when 
starting, however this is an emulation mode and issues arising while using this 
mode need to be recreated under X11 before they will be addressed.  At the 
moment, Wayland has no support for cursor warping, which means that the KiCad 
features of centering the cursor when zooming, and continuously panning the 
canvas, are broken on Wayland systems.

Steve

[1] https://www.kicad.org/help/known-system-related-issues/
[2] https://github.com/wxWidgets/wxWidgets/labels/Wayland
___
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: F40 Change Proposal: KDE Plasma 6 (System Wide)

[Aoife Moloney]

The discussion thread to provide feedback for this change proposal can be found 
here 
https://discussion.fedoraproject.org/t/f40-change-proposal-kde-plasma-6-system-wide/89794/1
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: F40 Change Proposal: KDE Plasma 6 (System Wide)

[Aoife Moloney]

The discussion thread to provide feedback for this change proposal can be found 
here 
https://discussion.fedoraproject.org/t/f40-change-proposal-kde-plasma-6-system-wide/89794/1
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

F40 Change Proposal: KDE Plasma 6 (System Wide)

[Aoife Moloney]

Wiki  https://fedoraproject.org/wiki/Changes/KDE_Plasma_6

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



== Summary ==
KDE Plasma 6 is successor to KDE Plasma 5 created by the KDE
Community. It is based on Qt 6 and KDE Frameworks 6 and brings many
changes and improvements over previous versions. For Fedora Linux, the
transition to KDE Plasma 6 will also include dropping support for the
X11 session entirely, leaving only Plasma Wayland as the sole offered
desktop mode.

== Owner ==
* Name: [[User:Ngompa|Neal Gompa]], [[User:Marcdeop|Marc Deop]],
[[User:Justinz|Justin Zobel]], [[User:Siosm|Timothy Ravier]],
[[User:Tdawson|Troy Dawson]], [[User:Jgrulich|Jan Grulich]]
* Email: ngomp...@gmail.com, marcd...@fedoraproject.org,
justin.zo...@gmail.com, trav...@redhat.com, tdaw...@redhat.com,
jgrul...@redhat.com


== Detailed Description ==
KDE Plasma 6 is a new major version of the user experience environment
from the KDE community. It includes both desktop and mobile
environments. While there are some user experience improvements over
KDE Plasma 5, the majority of the work is under the hood. Notably, the
whole stack is now built on Qt 6. Qt 6 brings significant upgrades to
QML and Qt Quick as well as support for Vulkan (in addition to OpenGL
and OpenGL ES support introduced in Qt 5).

[https://pointieststick.com/2023/09/06/september-plasma-6-update/ KDE
Plasma 6.0 is expected to release in early February 2024]. The
frameworks (KDE Frameworks), shells (Plasma Desktop and Plasma
Mobile), and applications (KDE Gear)
[https://mail.kde.org/pipermail/kde-devel/2023-September/002008.html
are all expected to be ported to Qt 6 as part of the KDE Plasma 6
release]. However, some applications may not make it in time and will
be updated later.

This upgrade is also notable that for Fedora Linux (and Fedora Extra
Packages for Enterprise Linux 10, once that materializes), KDE Plasma
will '''not''' offer an X11 session. Fedora KDE has been fully Wayland
by default from login ([[Changes/WaylandByDefaultForSDDM|since Fedora
Linux 38]]) to desktop ([[Changes/WaylandByDefaultForPlasma|since
Fedora Linux 34]]), and the SIG is confident in the quality and
development around the Plasma Wayland experience to stand fully behind
it.

== Feedback ==

 Why drop the X11 session? 

Three reasons for this removal:

* 
[https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/9.0_release_notes/deprecated_functionality#JIRA-RHELPLAN-121048
The Xorg server is deprecated since RHEL 9.0] and will be dropped in
"a future major RHEL release".
* Graphics fallback modes are Wayland-friendly now with
[[Changes/ReplaceFbdevDrivers|SimpleDRM enabled since Fedora Linux
36]].
* NVIDIA drivers (since v495~v515) support GBM for Wayland instead of
EGLStreams. Wayland is fully supported on current NVIDIA drivers.

This will drastically reduce our support burden and give us the
ability to focus on quality for the KDE Plasma stack and continue our
feature-forward nature. The Fedora KDE SIG will maintain a single code
stream for all supported distribution targets (Fedora Linux 40+,
Fedora Extra Packages for Enterprise Linux 10+).

This also does not mean that X11 applications will not work in Plasma
6, as we will still support Xwayland for running X11 applications on
Plasma Wayland.

 Could we keep Plasma 5 for X11? 

No. The KDE Plasma stack is fairly large and comprehensive. The SIG
does not have the resources to maintain the KDE Plasma 5 stack beyond
the lifetime of upstream's focus. It would also be fairly complex to
do so, requiring a lot of downstream patching to resolve the conflicts
between Plasma 5 and Plasma 6. The intent upstream is that KDE Plasma
5 will be EOL shortly after the release of KDE Plasma 6, so it would
be very difficult to support ourselves.

 Will Plasma 6 be available for older Fedora and EPEL releases? 

No. This major version upgrade is not getting backported. Some
portions (KDE Frameworks and KDE Gear) may get backported as part of
regular upgrades if Qt 5-based versions are not maintained upstream,
but the Plasma Desktop and Plasma Mobile software will not. Notably,
KDE Plasma 5 for older Fedora Linux releases (and Fedora Extra
Packages for Enterprise Linux 9) are on Plasma 5.27 and will stay
there.

== Benefit to Fedora ==
KDE Plasma is a very popular platform used as the basis for the Fedora
KDE Spin, Fedora Kinoite, and the flagship Fedora Asahi Remix
experiences. By bringing KDE Plasma 6 into Fedora, we demonstrate our
leadership and commitment to bring the latest and greatest
technologies from the KDE community to the world.

== Scope ==
* Proposal owners:
** Import Plasma 6 stack into F40/Rawhide (tracked as

F40 Change Proposal: KDE Plasma 6 (System Wide)

[Aoife Moloney]

Wiki  https://fedoraproject.org/wiki/Changes/KDE_Plasma_6

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



== Summary ==
KDE Plasma 6 is successor to KDE Plasma 5 created by the KDE
Community. It is based on Qt 6 and KDE Frameworks 6 and brings many
changes and improvements over previous versions. For Fedora Linux, the
transition to KDE Plasma 6 will also include dropping support for the
X11 session entirely, leaving only Plasma Wayland as the sole offered
desktop mode.

== Owner ==
* Name: [[User:Ngompa|Neal Gompa]], [[User:Marcdeop|Marc Deop]],
[[User:Justinz|Justin Zobel]], [[User:Siosm|Timothy Ravier]],
[[User:Tdawson|Troy Dawson]], [[User:Jgrulich|Jan Grulich]]
* Email: ngomp...@gmail.com, marcd...@fedoraproject.org,
justin.zo...@gmail.com, trav...@redhat.com, tdaw...@redhat.com,
jgrul...@redhat.com


== Detailed Description ==
KDE Plasma 6 is a new major version of the user experience environment
from the KDE community. It includes both desktop and mobile
environments. While there are some user experience improvements over
KDE Plasma 5, the majority of the work is under the hood. Notably, the
whole stack is now built on Qt 6. Qt 6 brings significant upgrades to
QML and Qt Quick as well as support for Vulkan (in addition to OpenGL
and OpenGL ES support introduced in Qt 5).

[https://pointieststick.com/2023/09/06/september-plasma-6-update/ KDE
Plasma 6.0 is expected to release in early February 2024]. The
frameworks (KDE Frameworks), shells (Plasma Desktop and Plasma
Mobile), and applications (KDE Gear)
[https://mail.kde.org/pipermail/kde-devel/2023-September/002008.html
are all expected to be ported to Qt 6 as part of the KDE Plasma 6
release]. However, some applications may not make it in time and will
be updated later.

This upgrade is also notable that for Fedora Linux (and Fedora Extra
Packages for Enterprise Linux 10, once that materializes), KDE Plasma
will '''not''' offer an X11 session. Fedora KDE has been fully Wayland
by default from login ([[Changes/WaylandByDefaultForSDDM|since Fedora
Linux 38]]) to desktop ([[Changes/WaylandByDefaultForPlasma|since
Fedora Linux 34]]), and the SIG is confident in the quality and
development around the Plasma Wayland experience to stand fully behind
it.

== Feedback ==

 Why drop the X11 session? 

Three reasons for this removal:

* 
[https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/9.0_release_notes/deprecated_functionality#JIRA-RHELPLAN-121048
The Xorg server is deprecated since RHEL 9.0] and will be dropped in
"a future major RHEL release".
* Graphics fallback modes are Wayland-friendly now with
[[Changes/ReplaceFbdevDrivers|SimpleDRM enabled since Fedora Linux
36]].
* NVIDIA drivers (since v495~v515) support GBM for Wayland instead of
EGLStreams. Wayland is fully supported on current NVIDIA drivers.

This will drastically reduce our support burden and give us the
ability to focus on quality for the KDE Plasma stack and continue our
feature-forward nature. The Fedora KDE SIG will maintain a single code
stream for all supported distribution targets (Fedora Linux 40+,
Fedora Extra Packages for Enterprise Linux 10+).

This also does not mean that X11 applications will not work in Plasma
6, as we will still support Xwayland for running X11 applications on
Plasma Wayland.

 Could we keep Plasma 5 for X11? 

No. The KDE Plasma stack is fairly large and comprehensive. The SIG
does not have the resources to maintain the KDE Plasma 5 stack beyond
the lifetime of upstream's focus. It would also be fairly complex to
do so, requiring a lot of downstream patching to resolve the conflicts
between Plasma 5 and Plasma 6. The intent upstream is that KDE Plasma
5 will be EOL shortly after the release of KDE Plasma 6, so it would
be very difficult to support ourselves.

 Will Plasma 6 be available for older Fedora and EPEL releases? 

No. This major version upgrade is not getting backported. Some
portions (KDE Frameworks and KDE Gear) may get backported as part of
regular upgrades if Qt 5-based versions are not maintained upstream,
but the Plasma Desktop and Plasma Mobile software will not. Notably,
KDE Plasma 5 for older Fedora Linux releases (and Fedora Extra
Packages for Enterprise Linux 9) are on Plasma 5.27 and will stay
there.

== Benefit to Fedora ==
KDE Plasma is a very popular platform used as the basis for the Fedora
KDE Spin, Fedora Kinoite, and the flagship Fedora Asahi Remix
experiences. By bringing KDE Plasma 6 into Fedora, we demonstrate our
leadership and commitment to bring the latest and greatest
technologies from the KDE community to the world.

== Scope ==
* Proposal owners:
** Import Plasma 6 stack into F40/Rawhide (tracked as

Re: Non-responsive maintainer mkulik

[Mattia Verga via devel]

Il 13/09/23 11:58, Filip Janus ha scritto:

> Hi all,
> mkulik is the main admin of pg_auto_failover component, and I can't reach 
> him. So I would like to start the process of moving the main admin role to 
> me(I am an admin now but the default assignee is mkulik due to the main admin 
> role).
> Here is the mandatory BZ:
> https://bugzilla.redhat.com/show_bug.cgi?id=2238708
>
> -Filip-

Note that there's also an ongoing ticket for the inactive packagers policy:

https://pagure.io/find-inactive-packagers/issue/1673

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

[Test-Announce] [Now Playing] Toolbx Test Day 2023-09-14

[Sumantro Mukherjee]

Hey Folks,

Toolbx as a blocker for Fedora Workstation was declared as part of
Fedora Linux 39 changes process.
The idea for test week is for testers is to install latest version of
Toolbx and install Fedora and any other OS as well. The wiki[0] has
all the necessary details. Come join us and make Fedora better!

[0] https://fedoraproject.org/wiki/Test_Day:2023-09-14_Toolbx
-- 
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Will noarch packages "inherit" ExcludeArch from another noarch package

[Dan Horák]

On Wed, 13 Sep 2023 08:51:16 -0600
Jerry James  wrote:

> On Tue, Sep 12, 2023 at 10:02 PM Jerry James  wrote:
> > I looked at blueprint-compiler tonight, and found 2 bugs with the
> > handling of bitfields.  Sadly, fixing those still doesn't make the
> > test suite pass, so there is at least one more bug lurking somewhere.
> > Still, I think the package is probably fixable.  If you can wait just
> > a little longer, I will try to find the next bug tomorrow.
> 
> Bug 3 was on the line right next to bug 2. :-)  I have opened
> https://gitlab.gnome.org/jwestman/blueprint-compiler/-/merge_requests/143.
> That patch does not apply cleanly to version 0.6.0, but the attached
> version does.

as usually, great job, Jerry, thanks a lot


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: Will noarch packages "inherit" ExcludeArch from another noarch package

[Jerry James]

On Tue, Sep 12, 2023 at 10:02 PM Jerry James  wrote:
> I looked at blueprint-compiler tonight, and found 2 bugs with the
> handling of bitfields.  Sadly, fixing those still doesn't make the
> test suite pass, so there is at least one more bug lurking somewhere.
> Still, I think the package is probably fixable.  If you can wait just
> a little longer, I will try to find the next bug tomorrow.

Bug 3 was on the line right next to bug 2. :-)  I have opened
https://gitlab.gnome.org/jwestman/blueprint-compiler/-/merge_requests/143.
That patch does not apply cleanly to version 0.6.0, but the attached
version does.
-- 
Jerry James
http://www.jamezone.org/
--- blueprint-compiler-v0.6.0/blueprintcompiler/gir.py.orig	2022-11-26 16:14:49.0 -0700
+++ blueprint-compiler-v0.6.0/blueprintcompiler/gir.py	2023-09-13 08:32:20.150427956 -0600
@@ -603,8 +603,8 @@ class Repository(GirNode):
 return self.lookup_namespace(ns).get_type(dir_entry.DIR_ENTRY_NAME)
 
 def _resolve_type_id(self, type_id: int):
-if type_id & 0xFF == 0:
-type_id = (type_id >> 27) & 0x1F
+if type_id & (0xFF if sys.byteorder == "little" else 0xFF00) == 0:
+type_id = ((type_id >> 27) if sys.byteorder == "little" else type_id) & 0x1F
 # simple type
 if type_id == typelib.TYPE_BOOLEAN:
 return BoolType()
--- blueprint-compiler-v0.6.0/blueprintcompiler/typelib.py.orig	2022-11-26 16:14:49.0 -0700
+++ blueprint-compiler-v0.6.0/blueprintcompiler/typelib.py	2023-09-13 08:47:24.479850483 -0600
@@ -61,7 +61,14 @@ class Field:
 def __init__(self, offset, type, shift=0, mask=None):
 self._offset = offset
 self._type = type
-self._shift = shift
+if not mask or sys.byteorder == "little":
+self._shift = shift
+elif self._type == "u8" or self._type == "i8":
+self._shift = 7 - shift
+elif self._type == "u16" or self._type == "i16":
+self._shift = 15 - shift
+else:
+self._shift = 31 - shift
 self._mask = (1 << mask) - 1 if mask else None
 self._name = f"{offset}__{type}__{shift}__{mask}"
 
@@ -160,7 +167,7 @@ class Typelib:
 OBJ_FINAL = Field(0x02, "u16", 3, 1)
 OBJ_GTYPE_NAME = Field(0x08, "string")
 OBJ_PARENT = Field(0x10, "dir_entry")
-OBJ_GTYPE_STRUCT = Field(0x14, "string")
+OBJ_GTYPE_STRUCT = Field(0x12, "string")
 OBJ_N_INTERFACES = Field(0x14, "u16")
 OBJ_N_FIELDS = Field(0x16, "u16")
 OBJ_N_PROPERTIES = Field(0x18, "u16")
@@ -241,7 +248,11 @@ class Typelib:
 return self._typelib_file[loc:end].decode("utf-8")
 
 def _int(self, size, signed):
-return int.from_bytes(self._typelib_file[self._offset:self._offset + size], sys.byteorder)
+return int.from_bytes(
+self._typelib_file[self._offset:self._offset + size],
+sys.byteorder,
+signed=signed,
+)
 
 
 class TypelibHeader(Typelib):
___
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: PDC replacement proposal

[Tomas Hrcka]

I thought this was exactly the JSON blob we will implement, If you look at
the model of PDC
https://product-definition-center.github.io/product-definition-center/_images/overview.svg

Those endpoints are covered by relations Release, Compose, RPM through some
others.
The PDC approach is more or less a normalized RDBMS model.
This should be replaceable by a much simpler denormalized approach and
create one entry for each compose with all the data in one place.

It is also mentioned in the arc docs
https://fedora-arc.readthedocs.io/en/latest/pdc/users.html#fedoraqa-fedfind


On Tue, Sep 12, 2023 at 2:18 AM Adam Williamson 
wrote:

> On Mon, 2023-09-11 at 09:40 -0700, Kevin Fenzi wrote:
> > These are the things that fedfind/qa users? Do we have examples of this
> > data?
>
> Okay, here is (again) a list of the stuff fedfind uses. You can see
> sample data for each compose in the web UI itself, PDC actually has a
> rather good interactive API view.
>
> 1. WHAT: https://pdc.fedoraproject.org/rest_api/v1/composes/
>HOW: ?release=fedora-NN_label=label
> ?compose_id=cid
>WHY: To find a compose's compose ID from its label, or a compose's
> label from its compose ID. These functions are used on various paths.
> The most important one in real life is probably when we are creating
> and updating validation event pages for candidate composes, between the
> time the compose exists and the time it is synced to alt.fp.o - during
> this time wikitcms may need to look the compose up by label, but for
> fedfind to actually find it, cid_from_label has to work, because it can
> only 'natively' find a compose by label if it's been synced to
> alt.fp.o; if the compose has not yet been synced, the only way fedfind
> can find the compose is to use cid_from_label then locate it on
> kojipkgs under its compose ID.
>WORKAROUND: it would be difficult to work around this if we did not
> have the ability. For wikitcms we could try 'embedding' the compose ID
> in the event pages somehow. For some other less important uses there is
> probably no workaround.
>
> 2. WHAT: https://pdc.fedoraproject.org/rest_api/v1/compose-images/
>HOW: compose-images/(composeid)
>WHY: To provide image metadata for nightly composes that have been
> garbage-collected, and releases in the mirror system after they have
> been split across directories and their metadata stripped
>WORKAROUND: if there is no store of metadata by compose ID then
> fedfind just can't do this any more. It's not critical functionality to
> anything important I'm aware of, though - it's just a nice feature that
> can be used to e.g. run long-term analysis of image size changes across
> multiple releases, stuff like that. If this goes away I will just drop
> this feature from fedfind and you will no longer be able to find the
> real metadata for these composes (it would provide synthesized metadata
> for mirrored releases, but not garbage-collected nightlies). Note,
> retrieving the original metadata for mirrored releases depends on the
> cid_from_label feature (see 1).
>
> 3. WHAT: https://pdc.fedoraproject.org/rest_api/v1/releases/
>HOW: ?version=39=Fedora (for e.g.)
>WHY: To find the compose that was "previous" to any given compose.
> The first result for this PDC query for any given release is a dict
> with a handy 'compose_set' key whose value is a list of all the
> composes for that release, in reverse order by date. So we can easily
> find the compose that came 'before' any given compose. This is, I
> *think*, only used by the 'check-compose' script which sends out those
> "compose check report" emails.
>WORKAROUND: fedfind has a hideous alternative implementation of this
> which involves just blindly trying possible decrements and seeing if
> they exist. e.g. if you ask for the compose previous to Fedora-39-
> 20230911.n.1, it will try 20230911.n.0, if that doesn't exist, it will
> try 20230910.n.5 (we start counting backwards from 5 because, hey,
> gotta start somewhere, and doing more than 5 composes on one day is
> unlikely), then 20230910.n.4, and so on, until it hits something that
> exists. So, if we can't get a nice data set like this any more...we'll
> just have to use that. Bleh. We might also just drop check-compose and
> kill the feature, I suppose. I don't pay as much attention to those
> reports as I used to.
>
> 4. WHAT: https://pdc.fedoraproject.org/rest_api/v1/rpms/
>HOW: ?compose=cid=src=^package1$=^package2$
>WHY: To get the NEVR (name, epoch, version, release) for a given set
> of packages from a compose. This can be used by relvalconsumer (the
> thing that creates the wiki validation events) to decide whether any
> "important" packages changed between the last tested compose and the
> compose it's currently deciding whether to create a validation event
> for: if it's been more than 3 days but less than 14 days since the last
> event, it will create a new event *if* any important package's version
> 

[rpms/perl-Module-CPANfile] PR #1: Package tests; Modernize spec

[Jitka Plesnikova]

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

Merged pull-request:

``
Package tests; Modernize spec
``

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

[rpms/perl-Module-CPANfile] PR #1: Package tests; Modernize spec

[Jitka Plesnikova]

jplesnik opened a new pull-request against the project: `perl-Module-CPANfile` 
that you are following:
``
Package tests; Modernize spec
``

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

[Bug 2228397] CVE-2023-31486 perl:5.34/perl-HTTP-Tiny: http-tiny: insecure TLS cert default [fedora-all]

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|NEW |CLOSED
 Resolution|--- |WONTFIX
Last Closed||2023-09-13 13:51:37



--- Comment #2 from Jitka Plesnikova  ---
The module perl:5.34 is not supported since 2023-06-01.


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

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

[Bug 2228396] CVE-2023-31486 perl:5.32/perl-HTTP-Tiny: http-tiny: insecure TLS cert default [fedora-all]

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|NEW |CLOSED
Last Closed||2023-09-13 13:50:45



--- Comment #2 from Jitka Plesnikova  ---
The module perl:5.32 is not supported since 2022-06-01.


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

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

Re: Questions about %pyproject_buildrequires

[Scott Talbert]

On Wed, 13 Sep 2023, Miro Hrončok wrote:


On 13. 09. 23 5:03, Scott Talbert wrote:

Hi all,


Hi Scott.

First, is it possible to use this macro if the pyproject.toml isn't in the 
root directory of the package?  There doesn't seem to be an option to 
specify a path, so I tried cd'ing into a path and running it, but it seemed 
to run into an odd error like it was trying to include my directory as a 
package.



You can do this, but you MUST NOT put anything to the standard output.
E.g. if you do this:

 %generate_buildrequires
 cd subdir
 %pyproject_buildrequires

It'll work properly. However, if you do:

 %generate_buildrequires
 cd subdir
 %pyproject_buildrequires
 cd -

It will generate a dependency on something like 
/builddir/build/BUILD/pkg-1.2.3 because that is what `cd -` prints to 
standard output.

Same with pushd and popd.

The solution is to use >&2 when runnign such commands in 
%generate_buildrequires. For example:


 %generate_buildrequires
 pushd pkg1 >&2
 %pyproject_buildrequires
 popd >&2
 pushd pkg2 >&2
 %pyproject_buildrequires
 popd >&2

Second, can %pyproject_buildrequires (and the other %pyproject_ macros) be 
used multiple times in a package?  I have a package that has multiple 
pyproject.toml files in it (but that's mostly a legacy thing, so I could 
probably separate them into multiple RPMs).


Yes, but %pyproject_insatll SHOULD only be used once (it will install 
everything, running it multiple times is redundant) and %pyproject_save_files 
will not work at all.


 %build
 pushd pkg1
 %pyproject_wheel
 popd
 pushd pkg2
 %pyproject_wheel
 popd

 %install
 # this will install both wheels:
 %pyproject_install
 # we cannot use %%pyproject_save_files here
 # because mixing files from multiple wheels is not supported


Perfect, thanks Miro!

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

Fedora 39 compose report: 20230913.n.0 changes

[Fedora Branched Report]

OLD: Fedora-39-20230912.n.0
NEW: Fedora-39-20230913.n.0

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

Size of added packages:  0 B
Size of dropped packages:21.53 KiB
Size of upgraded packages:   998.16 MiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   155.70 KiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: KDE live aarch64
Path: Spins/aarch64/iso/Fedora-KDE-Live-aarch64-39-20230913.n.0.iso

= DROPPED IMAGES =
Image: i3 live aarch64
Path: Spins/aarch64/iso/Fedora-i3-Live-aarch64-39-20230912.n.0.iso

= ADDED PACKAGES =

= DROPPED PACKAGES =
Package: python-pytest-virtualenv-1.7.0-16.fc38
Summary: Virtualenv fixture for py.test
RPMs:python3-pytest-virtualenv
Size:21.53 KiB


= UPGRADED PACKAGES =
Package:  gnome-initial-setup-45~beta-25.fc39
Old package:  gnome-initial-setup-45~beta-7.fc39
Summary:  Bootstrapping your OS
RPMs: gnome-initial-setup
Size: 2.24 MiB
Size change:  -16.10 KiB
Changelog:
  * Thu Sep 07 2023 Ray Strode  - 45~beta-8
  - Fix keyboard page next button that can't be buttoned

  * Fri Sep 08 2023 Ray Strode  - 45~beta-9
  - Don't let language page proceed until it has committed its changes

  * Fri Sep 08 2023 Ray Strode  - 45~beta-10
  - drop unused patches

  * Sat Sep 09 2023 Ray Strode  - 45~beta-11
  - Select US by default on Russian keyboards

  * Sat Sep 09 2023 Ray Strode  - 45~beta-12
  - Add missing patches

  * Mon Sep 11 2023 Ray Strode  - 45~beta-13
  - Fix crash in new user mode

  * Tue Sep 12 2023 Michael Catanzaro  - 45~beta-14
  - Revert "Fix crash in new user mode"

  * Tue Sep 12 2023 Michael Catanzaro  - 45~beta-15
  - Revert "Add missing patches"

  * Tue Sep 12 2023 Michael Catanzaro  - 45~beta-16
  - Revert "Select US by default on Russian keyboards"

  * Tue Sep 12 2023 Michael Catanzaro  - 45~beta-17
  - Revert "drop unused patches"

  * Tue Sep 12 2023 Michael Catanzaro  - 45~beta-18
  - Revert "Don't let language page proceed until it has committed its
changes"

  * Tue Sep 12 2023 Michael Catanzaro  - 45~beta-19
  - Revert "Fix keyboard page next button that can't be buttoned"

  * Tue Sep 12 2023 Michael Catanzaro  - 45~beta-20
  - Revert "More keyboard configuration updates"

  * Tue Sep 12 2023 Michael Catanzaro  - 45~beta-21
  - Revert "Update to use slightly tweaked default input sources api from
gnome-desktop"

  * Tue Sep 12 2023 Michael Catanzaro  - 45~beta-22
  - Revert "Clean up gnome-desktop requires"

  * Tue Sep 12 2023 Michael Catanzaro  - 45~beta-23
  - Revert "Add keyboard and input method handling fixes"

  * Tue Sep 12 2023 Michael Catanzaro  - 45~beta-24
  - Revert "Add liveuser mode and switch vendor.conf to accomodate it"

  * Tue Sep 12 2023 Michael Catanzaro  - 45~beta-25
  - Reverted all downstream F39 changes to gnome-initial-setup


Package:  kernel-6.5.2-301.fc39
Old package:  kernel-6.5.2-300.fc39
Summary:  The Linux kernel
RPMs: kernel kernel-core kernel-debug kernel-debug-core 
kernel-debug-devel kernel-debug-devel-matched kernel-debug-modules 
kernel-debug-modules-core kernel-debug-modules-extra 
kernel-debug-modules-internal kernel-debug-uki-virt kernel-devel 
kernel-devel-matched kernel-doc kernel-modules kernel-modules-core 
kernel-modules-extra kernel-modules-internal kernel-uki-virt
Size: 937.05 MiB
Size change:  17.90 KiB
Changelog:
  * Mon Sep 11 2023 Justin M. Forbes  [6.5.2-301]
  - Revert "misc: rtsx: judge ASPM Mode to set PETXCFG Reg" (Justin M. Forbes)
  - Config updates for 6.5.3 (Justin M. Forbes)
  - Fix up buildReqs for UKI (Justin M. Forbes)


Package:  libvirt-9.7.0-1.fc39
Old package:  libvirt-9.6.0-1.fc39
Summary:  Library providing a simple virtualization API
RPMs: libvirt libvirt-client libvirt-client-qemu libvirt-daemon 
libvirt-daemon-common libvirt-daemon-config-network 
libvirt-daemon-config-nwfilter libvirt-daemon-driver-interface 
libvirt-daemon-driver-libxl libvirt-daemon-driver-lxc 
libvirt-daemon-driver-network libvirt-daemon-driver-nodedev 
libvirt-daemon-driver-nwfilter libvirt-daemon-driver-qemu 
libvirt-daemon-driver-secret libvirt-daemon-driver-storage 
libvirt-daemon-driver-storage-core libvirt-daemon-driver-storage-disk 
libvirt-daemon-driver-storage-gluster libvirt-daemon-driver-storage-iscsi 
libvirt-daemon-driver-storage-iscsi-direct 
libvirt-daemon-driver-storage-logical libvirt-daemon-driver-storage-mpath 
libvirt-daemon-driver-storage-rbd libvirt-daemon-driver-storage-scsi 
libvirt-daemon-driver-storage-zfs libvirt-daemon-driver-vbox libvirt-daemon-kvm 
libvirt-daemon-lock libvirt-daemon-log libvirt-daemon-lxc 
libvirt-daemon-plugin-lockd libvirt-daemon-plugin-sanlock libvirt-daemon-

Re: The new Change discussion process is painful

[Pierre-Yves Chibon]

On Wed, Sep 13, 2023 at 10:46:04AM +0200, Vít Ondruch wrote:
> 
> Dne 13. 09. 23 v 9:08 Remi Collet napsal(a):
> > Le 13/09/2023 à 08:09, Adam Williamson a écrit :
> > > On Wed, 2023-09-13 at 05:51 +0200, Kevin Kofler via devel wrote:
> > > > Hi,
> > > > 
> > > > it is really a pain that the Change discussion is now hidden in
> > > > a web forum
> > > > behind a web link, instead of happening right here in this
> > > > mailing list. It
> > > > was promised that Discourse would NOT replace the mailing lists,
> > > > but that is
> > > > effectively no longer the case. Can this "Discourse for Change
> > > > discussion"
> > > > experiment please be stopped? It has no advantages and only adds
> > > > a useless
> > > > layer of indirection.
> > > 
> > > I don't really understand what you mean. AFAICT, every Change that has
> > > been announced at
> > > https://discussion.fedoraproject.org/c/project/changes/89 has also been
> > > announced at
> > > https://lists.fedoraproject.org/archives/list/devel-announce%40lists.fedoraproject.org/
> > > 
> > > , so nothing has been replaced.
> > 
> > Sadly it seems there is some email issues
> > 
> > For a few days, tons of messages are lost
> > so, I also don't receive any of the recent change announcements
> 
> 
> If nothing else, the announcements were previously send to devel-announce
> with devel in CC, while the CC is not included anymore. IOW can we have
> devel back in CC, please?

I'm pretty sure devel is subscribed to devel-announce, so email sent to
devel-announce will/should land on devel as well.


Pierre


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

[Bug 2238733] New: perl-HTML-Template-Expr for EL8 and EL9

[bugzilla]

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

Bug ID: 2238733
   Summary: perl-HTML-Template-Expr for EL8 and EL9
   Product: Fedora
   Version: rawhide
OS: Linux
Status: NEW
 Component: perl-HTML-Template-Expr
  Severity: medium
  Assignee: emman...@seyman.fr
  Reporter: xav...@bachelot.org
QA Contact: extras...@fedoraproject.org
CC: emman...@seyman.fr,
perl-devel@lists.fedoraproject.org, st...@silug.org
  Target Milestone: ---
Classification: Fedora



Hi,

Could you please branch and build perl-HTML-Template-Expr for EL8 and EL9 ?
I can take care of this if you don't want to. My FAS is xavierb.

Regards,
Xavier

Reproducible: Always


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202238733%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: The new Change discussion process is painful

[Ralf Corsépius]

Am 13.09.23 um 12:19 schrieb Sandro:

On 13-09-2023 08:09, Adam Williamson wrote:

 From there, it's up to people where they see and respond to them. If
more people are responding in discourse than on the mailing list, that
would seem to suggest that there*is*  a reason to announce things
there...


I'm quite sure Matthew (mattdm) would disagree with above statement. The 
idea was/is, iirc, to only announce on both channels, but have the 
discussion take place on Discourse.


And I could not disagree more with this.

So, making this pick & mix is definitely not the intention and it has 
already proven futile in a previous mishap.


I think, discourse should be dropped, ASAP. It isn't helpful.

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

Fedora rawhide compose report: 20230913.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20230912.n.0
NEW: Fedora-Rawhide-20230913.n.0

= SUMMARY =
Added images:2
Dropped images:  2
Added packages:  9
Dropped packages:17
Upgraded packages:   97
Downgraded packages: 1

Size of added packages:  4.94 MiB
Size of dropped packages:4.78 MiB
Size of upgraded packages:   12.31 GiB
Size of downgraded packages: 385.56 KiB

Size change of upgraded packages:   577.13 MiB
Size change of downgraded packages: -75.52 KiB

= ADDED IMAGES =
Image: Sericea dvd-ostree x86_64
Path: Sericea/x86_64/iso/Fedora-Sericea-ostree-x86_64-Rawhide-20230913.n.0.iso
Image: Workstation live aarch64
Path: 
Workstation/aarch64/iso/Fedora-Workstation-Live-aarch64-Rawhide-20230913.n.0.iso

= DROPPED IMAGES =
Image: Kinoite dvd-ostree ppc64le
Path: Kinoite/ppc64le/iso/Fedora-Kinoite-ostree-ppc64le-Rawhide-20230912.n.0.iso
Image: Kinoite dvd-ostree x86_64
Path: Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-Rawhide-20230912.n.0.iso

= ADDED PACKAGES =
Package: mvfst-2023.09.11.00-1.fc40
Summary: An implementation of the QUIC transport protocol
RPMs:mvfst mvfst-devel
Size:4.53 MiB

Package: python-httpx-socks-0.7.7-2.fc40
Summary: Proxy (HTTP, SOCKS) transports for httpx
RPMs:python3-httpx-socks
Size:32.93 KiB

Package: rust-deranged-0.3.8-1.fc40
Summary: Ranged integers
RPMs:rust-deranged+alloc-devel rust-deranged+default-devel 
rust-deranged+num-devel rust-deranged+quickcheck-devel rust-deranged+rand-devel 
rust-deranged+serde-devel rust-deranged+std-devel rust-deranged-devel
Size:72.10 KiB

Package: rust-faster-hex-0.8.1-2.fc40
Summary: Fast hex encoding
RPMs:rust-faster-hex+alloc-devel rust-faster-hex+default-devel 
rust-faster-hex+serde-devel rust-faster-hex+std-devel rust-faster-hex-devel
Size:48.09 KiB

Package: rust-gix-config-value-0.12.5-1.fc40
Summary: Parser for gix-config values
RPMs:rust-gix-config-value+default-devel rust-gix-config-value+serde-devel 
rust-gix-config-value-devel
Size:46.81 KiB

Package: rust-minus-5.4.0-1.fc40
Summary: Asynchronous data feedable terminal paging library for Rust
RPMs:rust-minus+default-devel rust-minus+dynamic_output-devel 
rust-minus+regex-devel rust-minus+search-devel rust-minus+static_output-devel 
rust-minus-devel
Size:108.75 KiB

Package: rust-peg-macros0.6-0.6.3-1.fc40
Summary: Procedural macros for rust-peg
RPMs:rust-peg-macros0.6+default-devel rust-peg-macros0.6+trace-devel 
rust-peg-macros0.6-devel
Size:41.28 KiB

Package: rust-peg-runtime0.6-0.6.3-1.fc40
Summary: Runtime support for rust-peg grammars
RPMs:rust-peg-runtime0.6+default-devel rust-peg-runtime0.6-devel
Size:18.74 KiB

Package: rust-peg0.6-0.6.3-1.fc40
Summary: Simple Parsing Expression Grammar (PEG) parser generator
RPMs:rust-peg0.6+default-devel rust-peg0.6+trace-devel rust-peg0.6-devel
Size:49.35 KiB


= DROPPED PACKAGES =
Package: php-doctrine-doctrine-bundle2-2.7.2-2.fc38
Summary: Symfony Bundle for Doctrine
RPMs:php-doctrine-doctrine-bundle2
Size:99.97 KiB

Package: php-nrk-Predis-1.1.10-4.fc38
Summary: PHP client library for Redis
RPMs:php-nrk-Predis
Size:183.30 KiB

Package: php-phpdocumentor-reflection-3.0.1-13.fc38
Summary: Reflection library to do Static Analysis for PHP Projects
RPMs:php-phpdocumentor-reflection
Size:29.11 KiB

Package: php-phpmyadmin-twig-i18n-extension-3.0.0-7.fc39
Summary: Internationalization support for Twig via the gettext library
RPMs:php-phpmyadmin-twig-i18n-extension
Size:14.97 KiB

Package: php-pragmarx-google2fa-qrcode-1.0.3-8.fc38
Summary: QR Code package for Google2FA
RPMs:php-pragmarx-google2fa-qrcode
Size:12.71 KiB

Package: php-swiftmailer-5.4.12-10.fc38
Summary: Free Feature-rich PHP Mailer
RPMs:php-swiftmailer
Size:189.20 KiB

Package: php-twig2-2.15.5-2.fc39
Summary: The flexible, fast, and secure template engine for PHP
RPMs:php-twig2
Size:202.53 KiB

Package: php-twig3-3.6.1-2.fc39
Summary: The flexible, fast, and secure template engine for PHP
RPMs:php-twig3
Size:134.64 KiB

Package: python-azure-mgmt-automanage-1.0.0-5.fc39
Summary: Microsoft Azure Auto Manage Management Client Library for Python
RPMs:python3-azure-mgmt-automanage
Size:105.55 KiB

Package: python-azure-mgmt-azurestackhci-6.0.0-8.fc39
Summary: Microsoft Azure AzureStack HCI Management Client Library for Python
RPMs:python3-azure-mgmt-azurestackhci
Size:57.77 KiB

Package: python-azure-mgmt-dashboard-1.0.0-5.fc39
Summary: Microsoft Azure Dashboard Management Client Library for Python
RPMs:python3-azure-mgmt-dashboard
Size:84.80 KiB

Package: python-azure-mgmt-deploymentmanager-1:0.2.0-12.fc39
Summary: Microsoft Azure Deployment Manager Client Library for Python
RPMs:python3-azure-mgmt-deploymentmanager
Size:67.06 KiB

Package: python-azure-mgmt-fluidrelay-1.0.0-5.fc39
Summary: Microsoft Azure Fluid Relay Management Client Library for Python
RPMs

Re: The new Change discussion process is painful

[Sandro]

On 13-09-2023 08:09, Adam Williamson wrote:

 From there, it's up to people where they see and respond to them. If
more people are responding in discourse than on the mailing list, that
would seem to suggest that there*is*  a reason to announce things
there...


I'm quite sure Matthew (mattdm) would disagree with above statement. The 
idea was/is, iirc, to only announce on both channels, but have the 
discussion take place on Discourse.


So, making this pick & mix is definitely not the intention and it has 
already proven futile in a previous mishap.


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

Non-responsive maintainer mkulik

[Filip Janus]

Hi all,
mkulik is the main admin of pg_auto_failover component, and I can't reach
him. So I would like to start the process of moving the main admin role to
me(I am an admin now but the default assignee is mkulik due to the main
admin role).
Here is the mandatory BZ:
https://bugzilla.redhat.com/show_bug.cgi?id=2238708

-Filip-
___
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 2238633] perltidy-20230912 is available

[bugzilla]

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



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


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

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

Re: Questions about %pyproject_buildrequires

[Miro Hrončok]

On 13. 09. 23 5:03, Scott Talbert wrote:

Hi all,


Hi Scott.

First, is it possible to use this macro if the pyproject.toml isn't in the root 
directory of the package?  There doesn't seem to be an option to specify a 
path, so I tried cd'ing into a path and running it, but it seemed to run into 
an odd error like it was trying to include my directory as a package.



You can do this, but you MUST NOT put anything to the standard output.
E.g. if you do this:

  %generate_buildrequires
  cd subdir
  %pyproject_buildrequires

It'll work properly. However, if you do:

  %generate_buildrequires
  cd subdir
  %pyproject_buildrequires
  cd -

It will generate a dependency on something like /builddir/build/BUILD/pkg-1.2.3 
because that is what `cd -` prints to standard output.

Same with pushd and popd.

The solution is to use >&2 when runnign such commands in 
%generate_buildrequires. For example:


  %generate_buildrequires
  pushd pkg1 >&2
  %pyproject_buildrequires
  popd >&2
  pushd pkg2 >&2
  %pyproject_buildrequires
  popd >&2

Second, can %pyproject_buildrequires (and the other %pyproject_ macros) be used 
multiple times in a package?  I have a package that has multiple pyproject.toml 
files in it (but that's mostly a legacy thing, so I could probably separate 
them into multiple RPMs).


Yes, but %pyproject_insatll SHOULD only be used once (it will install 
everything, running it multiple times is redundant) and %pyproject_save_files 
will not work at all.


  %build
  pushd pkg1
  %pyproject_wheel
  popd
  pushd pkg2
  %pyproject_wheel
  popd

  %install
  # this will install both wheels:
  %pyproject_install
  # we cannot use %%pyproject_save_files here
  # because mixing files from multiple wheels is not supported

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

[Bug 2238633] perltidy-20230912 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|CLOSED
 Resolution|--- |ERRATA
   Fixed In Version||perltidy-20230912-1.fc40
Last Closed||2023-09-13 09:22:35



--- Comment #4 from Fedora Update System  ---
FEDORA-2023-e11290c566 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=2238633

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

[Bug 2238633] perltidy-20230912 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|NEW |MODIFIED



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


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

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

Re: The new Change discussion process is painful

[Vít Ondruch]

Dne 13. 09. 23 v 9:08 Remi Collet napsal(a):

Le 13/09/2023 à 08:09, Adam Williamson a écrit :

On Wed, 2023-09-13 at 05:51 +0200, Kevin Kofler via devel wrote:

Hi,

it is really a pain that the Change discussion is now hidden in a 
web forum
behind a web link, instead of happening right here in this mailing 
list. It
was promised that Discourse would NOT replace the mailing lists, but 
that is
effectively no longer the case. Can this "Discourse for Change 
discussion"
experiment please be stopped? It has no advantages and only adds a 
useless

layer of indirection.


I don't really understand what you mean. AFAICT, every Change that has
been announced at
https://discussion.fedoraproject.org/c/project/changes/89 has also been
announced at
https://lists.fedoraproject.org/archives/list/devel-announce%40lists.fedoraproject.org/ 


, so nothing has been replaced.


Sadly it seems there is some email issues

For a few days, tons of messages are lost
so, I also don't receive any of the recent change announcements



If nothing else, the announcements were previously send to 
devel-announce with devel in CC, while the CC is not included anymore. 
IOW can we have devel back in CC, please?



Vít




BTW, I agree this dual channel is terrible for discussion

I personally don't follow discussion.fpo
too much tools kills simplicity


Remi



 From there, it's up to people where they see and respond to them. If
more people are responding in discourse than on the mailing list, that
would seem to suggest that there *is* a reason to announce things
there...

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/

List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


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

[Bug 2238688] New: perl-Plack-Middleware-Deflater-0.12-28.fc40 FTBFS: tests fail

[bugzilla]

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

Bug ID: 2238688
   Summary: perl-Plack-Middleware-Deflater-0.12-28.fc40 FTBFS:
tests fail
   Product: Fedora
   Version: rawhide
   URL: https://koschei.fedoraproject.org/package/perl-Plack-M
iddleware-Deflater?collection=f40
Status: NEW
 Component: perl-Plack-Middleware-Deflater
  Assignee: robinlee.s...@gmail.com
  Reporter: ppi...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: perl-devel@lists.fedoraproject.org,
robinlee.s...@gmail.com
Blocks: 2231791 (F40FTBFS,RAWHIDEFTBFS)
  Target Milestone: ---
Classification: Fedora



perl-Plack-Middleware-Deflater-0.12-28.fc40 fails to build in Fedora 40 because
all tests fail like this:

#   Failed test at t/content_type.t line 23.
#  got: undef
# expected: 'Hello World'
#   Failed test at t/content_type.t line 38.
#  got: undef
# expected: 'Hello World'
# Looks like you failed 2 tests of 6.
t/content_type.t  
Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/6 subtests 

A difference between passing and failing build roots is at
.



Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=2231791
[Bug 2231791] Fedora 40 FTBFS Tracker
-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2238688

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202238688%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: F40 Change Proposal:PHP 8.3 (Self Contained)

[Remi Collet]

Le 11/09/2023 à 19:12, Aoife Moloney a écrit :

The discussion thread to provide feedback on this proposed change can be found 
here 
https://discussion.fedoraproject.org/t/f40-change-proposal-php-8-3-self-contained/89611/1


Please don't use above link

Please use this ML for questions/feedback


Remi
___
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: The new Change discussion process is painful

[Remi Collet]

Le 13/09/2023 à 08:09, Adam Williamson a écrit :

On Wed, 2023-09-13 at 05:51 +0200, Kevin Kofler via devel wrote:

Hi,

it is really a pain that the Change discussion is now hidden in a web forum
behind a web link, instead of happening right here in this mailing list. It
was promised that Discourse would NOT replace the mailing lists, but that is
effectively no longer the case. Can this "Discourse for Change discussion"
experiment please be stopped? It has no advantages and only adds a useless
layer of indirection.


I don't really understand what you mean. AFAICT, every Change that has
been announced at
https://discussion.fedoraproject.org/c/project/changes/89 has also been
announced at
https://lists.fedoraproject.org/archives/list/devel-announce%40lists.fedoraproject.org/
, so nothing has been replaced.


Sadly it seems there is some email issues

For a few days, tons of messages are lost
so, I also don't receive any of the recent change announcements

BTW, I agree this dual channel is terrible for discussion

I personally don't follow discussion.fpo
too much tools kills simplicity


Remi



 From there, it's up to people where they see and respond to them. If
more people are responding in discourse than on the mailing list, that
would seem to suggest that there *is* a reason to announce things
there...

___
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: The new Change discussion process is painful

[Adam Williamson]

On Wed, 2023-09-13 at 05:51 +0200, Kevin Kofler via devel wrote:
> Hi,
> 
> it is really a pain that the Change discussion is now hidden in a web forum 
> behind a web link, instead of happening right here in this mailing list. It 
> was promised that Discourse would NOT replace the mailing lists, but that is 
> effectively no longer the case. Can this "Discourse for Change discussion" 
> experiment please be stopped? It has no advantages and only adds a useless 
> layer of indirection.

I don't really understand what you mean. AFAICT, every Change that has
been announced at
https://discussion.fedoraproject.org/c/project/changes/89 has also been
announced at
https://lists.fedoraproject.org/archives/list/devel-announce%40lists.fedoraproject.org/
, so nothing has been replaced.

From there, it's up to people where they see and respond to them. If
more people are responding in discourse than on the mailing list, that
would seem to suggest that there *is* a reason to announce things
there...
-- 
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org
https://www.happyassassin.net



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