Re: Take 1 minute to help with Infra & Releng Team with a decision

[Michal Konecny]

On 08. 02. 23 18:54, Chuck Anderson wrote:

On Wed, Feb 08, 2023 at 06:43:02PM +0100, Eike Rathke wrote:

Hi Michal,

On Tuesday, 2023-02-07 16:24:16 +0100, Michal Konecny wrote:


[0] - https://forms.gle/J2HWDkw1UNuj8HYD8

Don't be surprised if you don't get the number of answers you hoped for,
on

a) a Google form
b) that requires a Google account
c) to be logged in

b) and c) are not true.  A private-browsing FF window worked fine for me.
The form was created without the requirements for google account or 
e-mail. It is just a tool in this case.



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

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

Risc-V SIG?

[Zbigniew Jędrzejewski-Szmek]

Hi,

to return to the recent thread [1] "RISC-V — are we ready for more,
and what do we need to do it?": should we have a RISC-V SIG group to
coordinate and make it easier to find the resources?

This is primarily a question to people who are working on this already
(David A., Richard J., others?), what would be useful for you.

(I got my hands on a small risc-v board (StarFive VisionFive 2) and was
trying to get a new installation of Fedora running on it. It can be made
to work, but the docs are really scattered and partially outdated…
I was wondering how to get involved, and it's not clear at all.)

[1] 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/Z2RR2OE5TAQH5CVJ5VB5T3R7OM5ULYPQ/#O7IC6ZOH2RWWHG6F2UY4JGOU6HHMVFS5

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

Re: Risc-V SIG?

[Richard W.M. Jones]

On Thu, Feb 09, 2023 at 10:38:38AM +, Zbigniew Jędrzejewski-Szmek wrote:
> Hi,
> 
> to return to the recent thread [1] "RISC-V — are we ready for more,
> and what do we need to do it?": should we have a RISC-V SIG group to
> coordinate and make it easier to find the resources?
> 
> This is primarily a question to people who are working on this already
> (David A., Richard J., others?), what would be useful for you.
> 
> (I got my hands on a small risc-v board (StarFive VisionFive 2) and was
> trying to get a new installation of Fedora running on it. It can be made
> to work, but the docs are really scattered and partially outdated…
> I was wondering how to get involved, and it's not clear at all.)
> 
> [1] 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/Z2RR2OE5TAQH5CVJ5VB5T3R7OM5ULYPQ/#O7IC6ZOH2RWWHG6F2UY4JGOU6HHMVFS5

I just got a VF2 as well (as in, yesterday).  I'm still waiting on
some bits and pieces before I try to make it work.

I support creating a SIG.  However note there are some existing
resources available aleady (which need to be updated):

https://fedoraproject.org/wiki/Architectures/RISC-V

and the #fedora-riscv channel on Libera and an interlinked one on Matrix.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-p2v converts physical machines to virtual machines.  Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
http://libguestfs.org/virt-v2v
___
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: Risc-V SIG?

[Richard W.M. Jones]

[Adding DJ]

On Thu, Feb 09, 2023 at 10:38:38AM +, Zbigniew Jędrzejewski-Szmek wrote:
> Hi,
> 
> to return to the recent thread [1] "RISC-V — are we ready for more,
> and what do we need to do it?": should we have a RISC-V SIG group to
> coordinate and make it easier to find the resources?
> 
> This is primarily a question to people who are working on this already
> (David A., Richard J., others?), what would be useful for you.
> 
> (I got my hands on a small risc-v board (StarFive VisionFive 2) and was
> trying to get a new installation of Fedora running on it. It can be made
> to work, but the docs are really scattered and partially outdated…
> I was wondering how to get involved, and it's not clear at all.)
> 
> [1] 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/Z2RR2OE5TAQH5CVJ5VB5T3R7OM5ULYPQ/#O7IC6ZOH2RWWHG6F2UY4JGOU6HHMVFS5
> 
> Zbyszek

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

Re: Risc-V SIG?

[Richard W.M. Jones]

On Thu, Feb 09, 2023 at 10:55:50AM +, Richard W.M. Jones wrote:
> On Thu, Feb 09, 2023 at 10:38:38AM +, Zbigniew Jędrzejewski-Szmek wrote:
> > Hi,
> > 
> > to return to the recent thread [1] "RISC-V — are we ready for more,
> > and what do we need to do it?": should we have a RISC-V SIG group to
> > coordinate and make it easier to find the resources?
> > 
> > This is primarily a question to people who are working on this already
> > (David A., Richard J., others?), what would be useful for you.
> > 
> > (I got my hands on a small risc-v board (StarFive VisionFive 2) and was
> > trying to get a new installation of Fedora running on it. It can be made
> > to work, but the docs are really scattered and partially outdated…
> > I was wondering how to get involved, and it's not clear at all.)
> > 
> > [1] 
> > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/Z2RR2OE5TAQH5CVJ5VB5T3R7OM5ULYPQ/#O7IC6ZOH2RWWHG6F2UY4JGOU6HHMVFS5
> 
> I just got a VF2 as well (as in, yesterday).  I'm still waiting on
> some bits and pieces before I try to make it work.
> 
> I support creating a SIG.  However note there are some existing
> resources available aleady (which need to be updated):
> 
> https://fedoraproject.org/wiki/Architectures/RISC-V
> 
> and the #fedora-riscv channel on Libera and an interlinked one on Matrix.

Oh and I should add that we're even more interested in a CentOS SIG.
Whether or not this should be related to the Fedora SIG I don't know,
although they are very likely to contain the same group of people!

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html
___
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: Take 1 minute to help with Infra & Releng Team with a decision

[Eike Rathke]

Hi,

On Wednesday, 2023-02-08 12:54:17 -0500, Chuck Anderson wrote:

> > a) a Google form
> > b) that requires a Google account
> > c) to be logged in
> 
> b) and c) are not true.  A private-browsing FF window worked fine for me.

Oh, so

"
Sign in to Google to save your progress. Learn more
*Required
"

is just another dark pattern.

Shrug,
  Eike

-- 
GPG key 0x6A6CD5B765632D3A - 2265 D7F3 A7B0 95CC 3918  630B 6A6C D5B7 6563 2D3A


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

Re: Risc-V SIG?

[Zbigniew Jędrzejewski-Szmek]

On Thu, Feb 09, 2023 at 10:55:50AM +, Richard W.M. Jones wrote:
> On Thu, Feb 09, 2023 at 10:38:38AM +, Zbigniew Jędrzejewski-Szmek wrote:
> I just got a VF2 as well (as in, yesterday).  I'm still waiting on
> some bits and pieces before I try to make it work.

FWIW, it seems to work fine with just a shared USB power supply and an
ethernet cable. It warms up to ~64C when running all 4 cores, so I
just ordered a rpi heatsink to glue on top.

> I support creating a SIG.

I'll wait for some more replies and then see what paperwork is needed.
IIRC, it's mostly a question of creating a page with a short intro
and a list of names.

> However note there are some existing
> resources available aleady (which need to be updated):
> 
> https://fedoraproject.org/wiki/Architectures/RISC-V

Yep, I was using that.

> and the #fedora-riscv channel on Libera and an interlinked one on Matrix.

I joined the channel.

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

Re: Risc-V SIG?

[Richard W.M. Jones]

On Thu, Feb 09, 2023 at 11:03:27AM +, Zbigniew Jędrzejewski-Szmek wrote:
> On Thu, Feb 09, 2023 at 10:55:50AM +, Richard W.M. Jones wrote:
> > On Thu, Feb 09, 2023 at 10:38:38AM +, Zbigniew Jędrzejewski-Szmek wrote:
> > I just got a VF2 as well (as in, yesterday).  I'm still waiting on
> > some bits and pieces before I try to make it work.
> 
> FWIW, it seems to work fine with just a shared USB power supply and an
> ethernet cable. It warms up to ~64C when running all 4 cores, so I
> just ordered a rpi heatsink to glue on top.

From some reports on https://forum.rvspace.org/ it seems as if not all
M.2 SSDs work properly unless you use sufficient USB power.

I ordered a WD SSD and a passive heatsink, I already have a 60W USB-C
power supply spare that I can use.

> > I support creating a SIG.
> 
> I'll wait for some more replies and then see what paperwork is needed.
> IIRC, it's mostly a question of creating a page with a short intro
> and a list of names.
> 
> > However note there are some existing
> > resources available aleady (which need to be updated):
> > 
> > https://fedoraproject.org/wiki/Architectures/RISC-V
> 
> Yep, I was using that.
> 
> > and the #fedora-riscv channel on Libera and an interlinked one on Matrix.
> 
> I joined the channel.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html
___
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: Risc-V SIG?

[Neal Gompa]

On Thu, Feb 9, 2023 at 5:57 AM Richard W.M. Jones  wrote:
>
> On Thu, Feb 09, 2023 at 10:55:50AM +, Richard W.M. Jones wrote:
> > On Thu, Feb 09, 2023 at 10:38:38AM +, Zbigniew Jędrzejewski-Szmek wrote:
> > > Hi,
> > >
> > > to return to the recent thread [1] "RISC-V — are we ready for more,
> > > and what do we need to do it?": should we have a RISC-V SIG group to
> > > coordinate and make it easier to find the resources?
> > >
> > > This is primarily a question to people who are working on this already
> > > (David A., Richard J., others?), what would be useful for you.
> > >
> > > (I got my hands on a small risc-v board (StarFive VisionFive 2) and was
> > > trying to get a new installation of Fedora running on it. It can be made
> > > to work, but the docs are really scattered and partially outdated…
> > > I was wondering how to get involved, and it's not clear at all.)
> > >
> > > [1] 
> > > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/Z2RR2OE5TAQH5CVJ5VB5T3R7OM5ULYPQ/#O7IC6ZOH2RWWHG6F2UY4JGOU6HHMVFS5
> >
> > I just got a VF2 as well (as in, yesterday).  I'm still waiting on
> > some bits and pieces before I try to make it work.
> >
> > I support creating a SIG.  However note there are some existing
> > resources available aleady (which need to be updated):
> >
> > https://fedoraproject.org/wiki/Architectures/RISC-V
> >
> > and the #fedora-riscv channel on Libera and an interlinked one on Matrix.
>
> Oh and I should add that we're even more interested in a CentOS SIG.
> Whether or not this should be related to the Fedora SIG I don't know,
> although they are very likely to contain the same group of people!
>

There's already an existing Alternative Architectures SIG in CentOS
that could be revived for this purpose:
https://wiki.centos.org/SpecialInterestGroup/AltArch

It is moribund at the moment, but Pablo Greco is the "last man
standing" and would be the person to reach out to for reusing it for
CentOS RISC-V.

But I wouldn't even consider contemplating this until you can get a
clean Fedora build on RISC-V first.




--
真実はいつも一つ！/ 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

[Fedocal] Reminder meeting : ELN SIG

[sgallagh]

Dear all,

You are kindly invited to the meeting:
   ELN SIG on 2023-02-10 from 12:00:00 to 13:00:00 US/Eastern
   At fedora-meet...@irc.libera.chat

The meeting will be about:



Source: https://calendar.fedoraproject.org//meeting/10437/

___
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: Risc-V SIG?

[Richard W.M. Jones]

On Thu, Feb 09, 2023 at 06:31:21AM -0500, Neal Gompa wrote:
> On Thu, Feb 9, 2023 at 5:57 AM Richard W.M. Jones  wrote:
> >
> > On Thu, Feb 09, 2023 at 10:55:50AM +, Richard W.M. Jones wrote:
> > > On Thu, Feb 09, 2023 at 10:38:38AM +, Zbigniew Jędrzejewski-Szmek 
> > > wrote:
> > > > Hi,
> > > >
> > > > to return to the recent thread [1] "RISC-V — are we ready for more,
> > > > and what do we need to do it?": should we have a RISC-V SIG group to
> > > > coordinate and make it easier to find the resources?
> > > >
> > > > This is primarily a question to people who are working on this already
> > > > (David A., Richard J., others?), what would be useful for you.
> > > >
> > > > (I got my hands on a small risc-v board (StarFive VisionFive 2) and was
> > > > trying to get a new installation of Fedora running on it. It can be made
> > > > to work, but the docs are really scattered and partially outdated…
> > > > I was wondering how to get involved, and it's not clear at all.)
> > > >
> > > > [1] 
> > > > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/Z2RR2OE5TAQH5CVJ5VB5T3R7OM5ULYPQ/#O7IC6ZOH2RWWHG6F2UY4JGOU6HHMVFS5
> > >
> > > I just got a VF2 as well (as in, yesterday).  I'm still waiting on
> > > some bits and pieces before I try to make it work.
> > >
> > > I support creating a SIG.  However note there are some existing
> > > resources available aleady (which need to be updated):
> > >
> > > https://fedoraproject.org/wiki/Architectures/RISC-V
> > >
> > > and the #fedora-riscv channel on Libera and an interlinked one on Matrix.
> >
> > Oh and I should add that we're even more interested in a CentOS SIG.
> > Whether or not this should be related to the Fedora SIG I don't know,
> > although they are very likely to contain the same group of people!
> >
> 
> There's already an existing Alternative Architectures SIG in CentOS
> that could be revived for this purpose:
> https://wiki.centos.org/SpecialInterestGroup/AltArch
> 
> It is moribund at the moment, but Pablo Greco is the "last man
> standing" and would be the person to reach out to for reusing it for
> CentOS RISC-V.
> 
> But I wouldn't even consider contemplating this until you can get a
> clean Fedora build on RISC-V first.

David is building Fedora 37+ for RISC-V:

http://fedora.riscv.rocks/koji/

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual machines.  Supports shell scripting,
bindings from many languages.  http://libguestfs.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Strange RPM "recognition of file" error in f38 and f39 build

[Eike Rathke]

Hi,

Building Thunderbird for f38 and f39 now bails out with an RPM build
error

Recognition of file 
"/builddir/build/BUILDROOT/thunderbird-102.7.2-1.fc39.aarch64/usr/lib64/thunderbird/libxul.so"
 failed: mode 100755 , dynamically linked, 
BuildID[sha1]=633a0656d9de96c14d0960117d1029f4846c34ae Note section size too 
big (121835212 > 67108864) (Invalid argument)

See build.log of
https://koji.fedoraproject.org/koji/taskinfo?taskID=97288572
https://koji.fedoraproject.org/koji/taskinfo?taskID=97303047

Builds for f36 and f37 are fine, as was an earlier build of the previous
release for f38 last week.

Assumption is, something changed in libmagic.

  Eike

-- 
GPG key 0x6A6CD5B765632D3A - 2265 D7F3 A7B0 95CC 3918  630B 6A6C D5B7 6563 2D3A


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

Re: Risc-V SIG?

[Neal Gompa]

On Thu, Feb 9, 2023 at 8:01 AM Richard W.M. Jones  wrote:
>
> On Thu, Feb 09, 2023 at 06:31:21AM -0500, Neal Gompa wrote:
> > On Thu, Feb 9, 2023 at 5:57 AM Richard W.M. Jones  wrote:
> > >
> > > On Thu, Feb 09, 2023 at 10:55:50AM +, Richard W.M. Jones wrote:
> > > > On Thu, Feb 09, 2023 at 10:38:38AM +, Zbigniew Jędrzejewski-Szmek 
> > > > wrote:
> > > > > Hi,
> > > > >
> > > > > to return to the recent thread [1] "RISC-V — are we ready for more,
> > > > > and what do we need to do it?": should we have a RISC-V SIG group to
> > > > > coordinate and make it easier to find the resources?
> > > > >
> > > > > This is primarily a question to people who are working on this already
> > > > > (David A., Richard J., others?), what would be useful for you.
> > > > >
> > > > > (I got my hands on a small risc-v board (StarFive VisionFive 2) and 
> > > > > was
> > > > > trying to get a new installation of Fedora running on it. It can be 
> > > > > made
> > > > > to work, but the docs are really scattered and partially outdated…
> > > > > I was wondering how to get involved, and it's not clear at all.)
> > > > >
> > > > > [1] 
> > > > > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/Z2RR2OE5TAQH5CVJ5VB5T3R7OM5ULYPQ/#O7IC6ZOH2RWWHG6F2UY4JGOU6HHMVFS5
> > > >
> > > > I just got a VF2 as well (as in, yesterday).  I'm still waiting on
> > > > some bits and pieces before I try to make it work.
> > > >
> > > > I support creating a SIG.  However note there are some existing
> > > > resources available aleady (which need to be updated):
> > > >
> > > > https://fedoraproject.org/wiki/Architectures/RISC-V
> > > >
> > > > and the #fedora-riscv channel on Libera and an interlinked one on 
> > > > Matrix.
> > >
> > > Oh and I should add that we're even more interested in a CentOS SIG.
> > > Whether or not this should be related to the Fedora SIG I don't know,
> > > although they are very likely to contain the same group of people!
> > >
> >
> > There's already an existing Alternative Architectures SIG in CentOS
> > that could be revived for this purpose:
> > https://wiki.centos.org/SpecialInterestGroup/AltArch
> >
> > It is moribund at the moment, but Pablo Greco is the "last man
> > standing" and would be the person to reach out to for reusing it for
> > CentOS RISC-V.
> >
> > But I wouldn't even consider contemplating this until you can get a
> > clean Fedora build on RISC-V first.
>
> David is building Fedora 37+ for RISC-V:
>
> http://fedora.riscv.rocks/koji/
>

If I remember rightly, this still doesn't build straight from Fedora
Dist-Git as not all the RISC-V enablement patches have been upstreamed
into Fedora packages.



-- 
真実はいつも一つ！/ 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: Risc-V SIG?

[Richard W.M. Jones]

On Thu, Feb 09, 2023 at 08:06:33AM -0500, Neal Gompa wrote:
> On Thu, Feb 9, 2023 at 8:01 AM Richard W.M. Jones  wrote:
> > David is building Fedora 37+ for RISC-V:
> >
> > http://fedora.riscv.rocks/koji/
> >
> 
> If I remember rightly, this still doesn't build straight from Fedora
> Dist-Git as not all the RISC-V enablement patches have been upstreamed
> into Fedora packages.

A small number of packages need to be patched for RISC-V.  You can
find the dist-git sources for those here (only packages with
"main-riscv64" branches matter):

http://fedora.riscv.rocks:3000/explore/repos

The aim is to get everything upstream / into Fedora.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual machines.  Supports shell scripting,
bindings from many languages.  http://libguestfs.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Fedora rawhide compose report: 20230209.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20230208.n.0
NEW: Fedora-Rawhide-20230209.n.0

= SUMMARY =
Added images:2
Dropped images:  2
Added packages:  6
Dropped packages:0
Upgraded packages:   85
Downgraded packages: 0

Size of added packages:  267.64 MiB
Size of dropped packages:0 B
Size of upgraded packages:   1.64 GiB
Size of downgraded packages: 0 B

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

= ADDED IMAGES =
Image: Mate live x86_64
Path: Spins/x86_64/iso/Fedora-MATE_Compiz-Live-x86_64-Rawhide-20230209.n.0.iso
Image: Kinoite dvd-ostree x86_64
Path: Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-Rawhide-20230209.n.0.iso

= DROPPED IMAGES =
Image: Container_Minimal_Base docker aarch64
Path: 
Container/aarch64/images/Fedora-Container-Minimal-Base-Rawhide-20230208.n.0.aarch64.tar.xz
Image: Phosh raw-xz aarch64
Path: Spins/aarch64/images/Fedora-Phosh-Rawhide-20230208.n.0.aarch64.raw.xz

= ADDED PACKAGES =
Package: glab-1.24.1-1.fc38
Summary: A GitLab CLI tool bringing GitLab to your command line
RPMs:glab golang-gitlab-org-cli-devel
Size:23.10 MiB

Package: google-noto-sans-cjk-fonts-1:2.004-1.fc38
Summary: Google Noto Sans CJK Fonts
RPMs:google-noto-sans-cjk-fonts
Size:80.95 MiB

Package: google-noto-sans-cjk-vf-fonts-1:2.004-1.fc38
Summary: Google Noto Sans CJK Variable Fonts
RPMs:google-noto-sans-cjk-vf-fonts
Size:28.16 MiB

Package: google-noto-serif-cjk-fonts-1:2.001-1.fc38
Summary: Google Noto Serif CJK Fonts
RPMs:google-noto-serif-cjk-fonts
Size:115.51 MiB

Package: google-noto-serif-cjk-vf-fonts-1:2.001-1.fc38
Summary: Google Noto Serif CJK Variable Fonts
RPMs:google-noto-serif-cjk-vf-fonts
Size:19.85 MiB

Package: perl-Text-QRCode-0.05-4.fc38
Summary: Perl module to generate text base QR Code
RPMs:perl-Text-QRCode
Size:74.87 KiB


= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  NsCDE-2.2-2.fc38
Old package:  NsCDE-2.1-2.fc37
Summary:  Modern and functional CDE desktop based on FVWM
RPMs: NsCDE NsCDE-data NsCDE-doc
Size: 28.42 MiB
Size change:  167.68 KiB
Changelog:
  * Wed Jan 18 2023 Fedora Release Engineering  - 
2.1-3
  - Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild

  * Wed Feb 08 2023 Michel Alexandre Salim  - 2.2-1
  - Update to 2.2
  - backport fix for fvwm2 freezing due to recent Xorg bug
  - update license to use SPDX
  - drop install-time gettext dependency to gettext-runtime

  * Wed Feb 08 2023 Michel Alexandre Salim  - 2.2-2
  - Gate gettext-runtime use to Fedora > 36


Package:  OpenLP-3.0.2-1.fc38
Old package:  OpenLP-3.0.1-2.fc38
Summary:  Open source Church presentation and lyrics projection application
RPMs: OpenLP
Size: 4.38 MiB
Size change:  -5.61 KiB
Changelog:
  * Wed Feb 08 2023 Release 3.0.2  - 3.0.2-1
  - Rebuilt for Release 3.0.2


Package:  R-gmp-0.7.1-1.fc38
Old package:  R-gmp-0.6.6-2.fc38
Summary:  Multiple Precision Arithmetic
RPMs: R-gmp
Size: 1.61 MiB
Size change:  37.32 KiB
Changelog:
  * Wed Feb 08 2023 Tom Callaway  - 0.7.1-1
  - update to 0.7-1


Package:  R-pdftools-3.3.3-1.fc38
Old package:  R-pdftools-3.3.0-3.fc38
Summary:  Text Extraction, Rendering and Converting of PDF Documents
RPMs: R-pdftools
Size: 496.38 KiB
Size change:  -9.79 KiB
Changelog:
  * Wed Feb 08 2023 Tom Callaway  - 3.3.3-1
  - update to 3.3.3


Package:  R-webfakes-1.1.7-1.fc38
Old package:  R-webfakes-1.1.4-2.fc38
Summary:  Fake Web Apps for HTTP Testing
RPMs: R-webfakes
Size: 2.48 MiB
Size change:  18.54 KiB
Changelog:
  * Wed Feb 08 2023 Tom Callaway  - 1.1.7-1
  - update to 1.1.7


Package:  SDL2-2.26.3-1.fc38
Old package:  SDL2-2.26.2-1.fc38
Summary:  Cross-platform multimedia library
RPMs: SDL2 SDL2-devel SDL2-static
Size: 10.13 MiB
Size change:  -955 B
Changelog:
  * Wed Feb 08 2023 Tom Callaway  - 2.26.3-1
  - update to 2.26.3


Package:  SDL2_ttf-2.20.2-1.fc38
Old package:  SDL2_ttf-2.20.1-2.fc38
Summary:  TrueType font rendering library for SDL2
RPMs: SDL2_ttf SDL2_ttf-devel
Size: 312.26 KiB
Size change:  -442 B
Changelog:
  * Wed Feb 08 2023 Tom Callaway  - 2.20.2-1
  - update to 2.20.2


Package:  aardvark-dns-1.5.0-4.fc38
Old package:  aardvark-dns-1.5.0-3.fc38
Summary:  Authoritative DNS server for A/ container records
RPMs: aardvark-dns
Size: 3.80 MiB
Size change:  -407 B
Changelog:
  * Wed Feb 08 2023 Lokesh Mandvekar  - 1.5.0-4
  - Discontinue i686


Package:  aprsdigi-3.5.1-23.fc38
Old package:  aprsdigi-3.5.1-22.fc38
Summary:  AX.25 Automatic Position Reporting System
RPMs: aprsdigi
Size: 338.12 KiB
Size change:  -234 B
Changelog:
  * Wed Feb 08 2023 Florian Weimer  - 3.5.1-23
  - C99 compatibility fixes


Package:  bygfoot-2.3.5-1.fc38
Old package:  bygfoot-2.3.4-4.fc38
Summ

Re: Strange RPM "recognition of file" error in f38 and f39 build

[Vincent Mihalkovic]

Hi,

bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2167964
fix: https://src.fedoraproject.org/rpms/file/pull-request/22

This will be fixed as soon as possible!

vincent

On Thu, Feb 9, 2023 at 2:02 PM Eike Rathke  wrote:

> Hi,
>
> Building Thunderbird for f38 and f39 now bails out with an RPM build
> error
>
> Recognition of file
> "/builddir/build/BUILDROOT/thunderbird-102.7.2-1.fc39.aarch64/usr/lib64/thunderbird/libxul.so"
> failed: mode 100755 , dynamically linked,
> BuildID[sha1]=633a0656d9de96c14d0960117d1029f4846c34ae Note section size
> too big (121835212 > 67108864) (Invalid argument)
>
> See build.log of
> https://koji.fedoraproject.org/koji/taskinfo?taskID=97288572
> https://koji.fedoraproject.org/koji/taskinfo?taskID=97303047
>
> Builds for f36 and f37 are fine, as was an earlier build of the previous
> release for f38 last week.
>
> Assumption is, something changed in libmagic.
>
>   Eike
>
> --
> GPG key 0x6A6CD5B765632D3A - 2265 D7F3 A7B0 95CC 3918  630B 6A6C D5B7 6563
> 2D3A
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Strange RPM "recognition of file" error in f38 and f39 build

[Dominik 'Rathann' Mierzejewski]

On Thursday, 09 February 2023 at 14:02, Eike Rathke wrote:
> Hi,
> 
> Building Thunderbird for f38 and f39 now bails out with an RPM build
> error
> 
> Recognition of file 
> "/builddir/build/BUILDROOT/thunderbird-102.7.2-1.fc39.aarch64/usr/lib64/thunderbird/libxul.so"
>  failed: mode 100755 , dynamically linked, 
> BuildID[sha1]=633a0656d9de96c14d0960117d1029f4846c34ae Note section size too 
> big (121835212 > 67108864) (Invalid argument)
> 
> See build.log of
> https://koji.fedoraproject.org/koji/taskinfo?taskID=97288572
> https://koji.fedoraproject.org/koji/taskinfo?taskID=97303047
> 
> Builds for f36 and f37 are fine, as was an earlier build of the previous
> release for f38 last week.
> 
> Assumption is, something changed in libmagic.

According to koschei, this might be correct:
https://koschei.fedoraproject.org/build/14741264

file package was updated from 5.42 to 5.44. I suspect it is this commit:
https://github.com/file/file/commit/e1233247bbe4d2d66b891224336a23384a93cce1
which is present in 5.43 and later.

Regards,
Dominik
-- 
Fedora   https://getfedora.org  |  RPM Fusion  http://rpmfusion.org
There should be a science of discontent. People need hard times and
oppression to develop psychic muscles.
-- from "Collected Sayings of Muad'Dib" by the Princess Irulan
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Strange RPM "recognition of file" error in f38 and f39 build

[Mamoru TASAKA]

Eike Rathke wrote on 2023/02/09 22:02:

Hi,

Building Thunderbird for f38 and f39 now bails out with an RPM build
error

Recognition of file 
"/builddir/build/BUILDROOT/thunderbird-102.7.2-1.fc39.aarch64/usr/lib64/thunderbird/libxul.so"
 failed: mode 100755 , dynamically linked, 
BuildID[sha1]=633a0656d9de96c14d0960117d1029f4846c34ae Note section size too big (121835212 
> 67108864) (Invalid argument)

See build.log of
https://koji.fedoraproject.org/koji/taskinfo?taskID=97288572
https://koji.fedoraproject.org/koji/taskinfo?taskID=97303047

Builds for f36 and f37 are fine, as was an earlier build of the previous
release for f38 last week.

Assumption is, something changed in libmagic.

   Eike




Looks like due to this change:
https://github.com/file/file/commit/e1233247bbe4d2d66b891224336a23384a93cce1

and the above change seems related to:
https://bugs.astron.com/view.php?id=372

which seems to avoid some ASAN errors, however maybe this issue should not be
handed in the way in the commit.

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

Re: Tenacity

[Scott Talbert]

On Wed, 8 Feb 2023, Brandon Nielsen via devel wrote:


On 2/8/23 9:30 PM, Reon Beon via devel wrote:

wxGTK should have that...


It should, and they fixed it, but the fix never made it to the 3.1.X series 
as far as I can tell. 3.2.1 in F37 at least builds, but for some reason 
liblibnyquist.so is missing. F38 / Rawhide has some lisp issue with the 
libnyquist stuff.


Let me know if you want that bug fixed in F36 wxGTK.  Looks like it should 
be pretty easy to cherry-pick.


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: List of long term FTBFS packages to be retired next week

[Arun SAG]

On Thu, 9 Feb 2023 at 08:56, Arun SAG  wrote:
>
>
> >
> >  Package(co)maintainers
> > ==
> > ArpON   fab, sagarun
>
>
> There has been no activity on this package since 2016. This package
> should be retired.
>

Looks like there is interest in keeping this package around. A patch
has been posted to the bugzilla to fix the issue. I am retaking
ownership of this package and starting a koji build. Thanks and sorry
for the noise.


-- 
Arun S A G
http://zer0c00l.in/
___
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: Tenacity

[Ian McInerney via devel]

On Thu, Feb 9, 2023 at 2:30 PM Scott Talbert  wrote:

> On Wed, 8 Feb 2023, Brandon Nielsen via devel wrote:
>
> > On 2/8/23 9:30 PM, Reon Beon via devel wrote:
> >> wxGTK should have that...
> >
> > It should, and they fixed it, but the fix never made it to the 3.1.X
> series
> > as far as I can tell. 3.2.1 in F37 at least builds, but for some reason
> > liblibnyquist.so is missing. F38 / Rawhide has some lisp issue with the
> > libnyquist stuff.
>
> Let me know if you want that bug fixed in F36 wxGTK.  Looks like it should
> be pretty easy to cherry-pick.
>

The entire file dialog customization system was added in 3.1.7 right before
the 3.2.0 release, so the header file mentioned doesn't exist in 3.1.5, nor
any of the core code it needs to actually work. That change is a change to
the API of the file dialog methods, so it is IMO not cherry pickable to F36
because it would require cherry-picking this entire PR:
https://github.com/wxWidgets/wxWidgets/pull/22476.

If upstream tenacity wants to use the file dialog customizations, then they
need to update their required versions to be 3.2.0+ only and not claim
3.1.5 compatibility.


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

Re: List of long term FTBFS packages to be retired this week and orphaned now

[Jun Aruga (he / him)]

Hi Miro,

Sorry I will fix and rebuild the packages below on the rawhide asap.

> bowtie  jaruga, verdurin
...
> simde   jaruga

-- 
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See  for
the timezone.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Tenacity

[Scott Talbert]

On Thu, 9 Feb 2023, Ian McInerney via devel wrote:


On Thu, Feb 9, 2023 at 2:30 PM Scott Talbert  wrote:
  On Wed, 8 Feb 2023, Brandon Nielsen via devel wrote:

  > On 2/8/23 9:30 PM, Reon Beon via devel wrote:
  >> wxGTK should have that...
  >
  > It should, and they fixed it, but the fix never made it to the
  3.1.X series
  > as far as I can tell. 3.2.1 in F37 at least builds, but for
  some reason
  > liblibnyquist.so is missing. F38 / Rawhide has some lisp issue
  with the
  > libnyquist stuff.

  Let me know if you want that bug fixed in F36 wxGTK.  Looks like
  it should
  be pretty easy to cherry-pick.


The entire file dialog customization system was added in 3.1.7 right before
the 3.2.0 release, so the header file mentioned doesn't exist in 3.1.5, nor
any of the core code it needs to actually work. That change is a change to
the API of the file dialog methods, so it is IMO not cherry pickable to F36
because it would require cherry-picking this entire PR:
https://github.com/wxWidgets/wxWidgets/pull/22476.

If upstream tenacity wants to use the file dialog customizations, then they
need to update their required versions to be 3.2.0+ only and not claim 3.1.5
compatibility.


Ooops.  What Ian said.  :)

Upgrading to 3.2.0 in F36 is probably a non-starter as it involves an 
soname bump.


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: Risc-V SIG?

[David Abdurachmanov]

On Thu, Feb 9, 2023 at 2:24 PM Richard W.M. Jones  wrote:
>
> On Thu, Feb 09, 2023 at 08:06:33AM -0500, Neal Gompa wrote:
> > On Thu, Feb 9, 2023 at 8:01 AM Richard W.M. Jones  wrote:
> > > David is building Fedora 37+ for RISC-V:
> > >
> > > http://fedora.riscv.rocks/koji/
> > >
> >
> > If I remember rightly, this still doesn't build straight from Fedora
> > Dist-Git as not all the RISC-V enablement patches have been upstreamed
> > into Fedora packages.
>
> A small number of packages need to be patched for RISC-V.  You can
> find the dist-git sources for those here (only packages with
> "main-riscv64" branches matter):
>
> http://fedora.riscv.rocks:3000/explore/repos
>
> The aim is to get everything upstream / into Fedora.

Apologies for the slow reply. We do have a dist-git "overlay" that
holds various changes as we build things, or if we need to bump NVR to
rebuild something. We typically add ".X.riscv64" into Release: field
before %{?dist}.

There are two generic issues in Fedora that keep popping up:
- Wrong assumption about valgrind. Those are easy to fix, but are in a
number of places. Note that valgrind upstreaming will happen
relatively soonish too.
- Broken *.pc files in a number of packages. Somehow meson comes up
with wrong paths if *.pc is wrong on riscv64. That's not the case on
other architectures, and might be related to our symlink situations
(/usr/lib64/lpd64 points to /usr/lib64).

There is also an issue in how sub-word atomics are being handled in
riscv64 today. This basically means that packages like to fail
building somewhat sporadically. Basically you must link to libatomic
and GCC SPEC will do that if -pthread is used (this covers most of the
cases, but not all). Also a number of packages don't use -pthread and
just -lpthread. There are patches to improve this, but that's more
likely GCC 14 material now. A quick "fix" (not the best) would be
remove -pthread check and let GCC to attempt linking to libatomic in
all cases (--as-needed -latomic).

/* Because RISC-V only has word-sized atomics, it requries libatomic where
   others do not.  So link libatomic by default, as needed.  */
#undef LIB_SPEC
#ifdef LD_AS_NEEDED_OPTION
#define LIB_SPEC GNU_USER_TARGET_LIB_SPEC \
  " %{pthread:" LD_AS_NEEDED_OPTION " -latomic " LD_NO_AS_NEEDED_OPTION "}"
#else
#define LIB_SPEC GNU_USER_TARGET_LIB_SPEC " -latomic "
#endif

There are other bits like the audit library that so far the upstream
maintainer didn't want to merge.

It would be nice to handle dist-git stuff this year, especially in
Fedora 38 / 39 timeframe.

We also deviate from the original Fedora too. We are using newer
binutils versions compared to what's in Fedora proper. Our Fedora 37
was built binutils 2.39. Fedora no longer updates GCC/binutils/glibc
all in one go.

There are future questions that need to be discussed too as we are
finally approaching RISC-V profiles (RVA{20,22,23}). Optimized
packages or/and full repositories and disk images.

Today most communication/announcements happen in Fedora RISC-V Matrix
/ IRC channels.

Cheers,
david

>
> Rich.
>
> --
> Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
> Read my programming and virtualization blog: http://rwmj.wordpress.com
> libguestfs lets you edit virtual machines.  Supports shell scripting,
> bindings from many languages.  http://libguestfs.org
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Tenacity

[stan via devel]

On Wed, 8 Feb 2023 09:51:37 -0700
stan via devel  wrote:

> lot of (any?) sound editing anymore.  Just for the challenge.  Maybe
> not. :-)

I see lots of other people have taken up the challenge, and reported
issues they found, but I thought I would update with my unsuccessful
results.

I downloaded the wxWidgets code from their site, and compiled it using
their instructions on f37.  Compiled easily, with only a warning about
missing midi support.  I installed it in /usr/local

When I tried to get tenacity to use it, though, I hit a dead end.  Even
though I set the environment variable WX_CONFIG to point to it, cmake
find_program kept finding the system version 3.0.4.  I assume it looks
there first, and once it finds it, it stops.  I tried the alternative of
building it as a subprogram with the tenacity source (the tenacity
build instructions helpfully pointed to this), but it was compiled as
3.0 compatible, and tenacity complained about too old a version of some
constructs.  I then gave up.

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

Planned Outage - s390x builders - 2023-02-10 08:00 UTC -> 22:00 UTC

[Stephen Smoogen]

Planned Outage - s390x builders - 2023-02-10 08:00 UTC

There will be an outage starting at 2023-02-11 08:00 UTC,
which will last approximately 12 to 24 hours. Systems will be powered off
and then power to the facility will be dropped. After electrical work is
completed work on some network equipment may extend the outage due to a
different planned outage.

To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:

date -d '2023-02-10 08:00UTC'

Reason for outage:

The facility that houses the Fedora s390x builders will be taking down
power and network in order to troubleshoot current state and problems of
the power infrastructure there. This data will hopefully allow
fixes/solutions to make the power distribution there most robust and
reliable. After power is restored, there are additional network upgrades
and replacements which are planned to occur but have been delayed due to
the other work.

Affected Services:

s390x koji builders. Jobs will queue up, but not be processed until the
builders are back online. Maintainers are urged to just avoid submitting
builds just before and during this outage.

Ticket Link:

https://pagure.io/fedora-infrastructure/issue/11082

Please join #fedora-admin or #fedora-noc on irc.libera.chat
or add comments to the ticket for this outage above.

-- 
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: Tenacity

[Alec Leamas]

Hi Stan,

On 09/02/2023 16:55, stan via devel wrote:


I downloaded the wxWidgets code from their site, and compiled it using
their instructions on f37.  Compiled easily, with only a warning about
missing midi support.  I installed it in /usr/local

When I tried to get tenacity to use it, though, I hit a dead end.  Even
though I set the environment variable WX_CONFIG to point to it, cmake
find_program kept finding the system version 3.0.4.  I assume it looks
there first, and once it finds it, it stops.  I tried the alternative of
building it as a subprogram with the tenacity source (the tenacity
build instructions helpfully pointed to this), but it was compiled as
3.0 compatible, and tenacity complained about too old a version of some
constructs.  I then gave up.


Using several wxWidgets version is indeed a bit painful, been there, 
done that. One quick fix is to configure alternatives to use the new 3.2 
version version of wx-config instead of the default 3.0.


There is no need to actually build, just running "wx-config --version" 
reveals the version currently selected by alternatives.


There are other options including hard-wiring wx-config to an absolute 
path. However, it's IMHO more complicated and with some traps.



HTH
--alec
___
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

FIXED: Planned Outage - s390x builders - 2023-02-10 08:00 UTC

[Stephen Smoogen]

Planned Outage - s390x builders - 2023-02-10 08:00 UTC

There will be an outage starting at 2023-02-10 08:00 UTC,
which will last approximately 12 to 24 hours. Systems will be powered off
and then power to the facility will be dropped. After electrical work is
completed work on some network equipment may extend the outage due to a
different planned outage.

To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:

date -d '2023-02-10 08:00UTC'

Reason for outage:

The facility that houses the Fedora s390x builders will be taking down
power and network in order to troubleshoot current state and problems of
the power infrastructure there. This data will hopefully allow
fixes/solutions to make the power distribution there most robust and
reliable. After power is restored, there are additional network upgrades
and replacements which are planned to occur but have been delayed due to
the other work.

Affected Services:

The s390x koji builders will be unavailable. This will cause nearly all
rpmbuilds in koji to queue up until the s390x builders are back online.

Maintainers are urged to just avoid submitting builds just before and
during this outage.

Ticket Link:

https://pagure.io/fedora-infrastructure/issue/11082

Please join #fedora-admin or #fedora-noc on irc.libera.chat
or add comments to the ticket for this outage above.

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

[Kaleb Keithley]

On Tue, Nov 29, 2022 at 10:54 AM Kaleb Keithley  wrote:

> Hi,
>
> Apache Arrow 10.0.0 has been released.
>
> At present nobody is using libarrow except Ceph. (Which I am the
> maintainer of.)
>
> I will be rebasing libarrow to 10.0.0 within the next couple of days.
>

And now Apache Arrow 11.0.0 has been released. (Two weeks ago actually.)

I will be rebasing to 11 shortly.

-- 

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

Heads-up: OpenSSL update

[Dmitry Belyavskiy]

Dear colleagues,

I've just pushed updates of OpenSSL to the 3.0.8 version to f36/37.
I will also push to f38 and rawhide later today.

This is a security release, it fixes 8 MODERATE CVEs
(https://www.openssl.org/news/secadv/20230207.txt)

I kindly ask you to test the version so it could be rolled up earlier.

Many thanks in advance!

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

Re: Risc-V SIG?

[Kevin Fenzi]

On Thu, Feb 09, 2023 at 11:03:27AM +, Zbigniew Jędrzejewski-Szmek wrote:
> On Thu, Feb 09, 2023 at 10:55:50AM +, Richard W.M. Jones wrote:
> > On Thu, Feb 09, 2023 at 10:38:38AM +, Zbigniew Jędrzejewski-Szmek wrote:
> > I just got a VF2 as well (as in, yesterday).  I'm still waiting on
> > some bits and pieces before I try to make it work.
> 
> FWIW, it seems to work fine with just a shared USB power supply and an
> ethernet cable. It warms up to ~64C when running all 4 cores, so I
> just ordered a rpi heatsink to glue on top.
> 
> > I support creating a SIG.
> 
> I'll wait for some more replies and then see what paperwork is needed.
> IIRC, it's mostly a question of creating a page with a short intro
> and a list of names.

Yep. Sigs exist because they say they do. ;) 

The risc-v sig has been around for a while, but I guess a sig wiki page
was never made. :( 

So, sure, we should setup a page and point to the discussion topic and
irc/matrix rooms. :)

If you could do that it would be great... otherwise I will try and do
so.

kevin


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

Re: Heads-up: OpenSSL update

[Paul Wouters]

On Thu, 9 Feb 2023, Dmitry Belyavskiy wrote:


I've just pushed updates of OpenSSL to the 3.0.8 version to f36/37.
I will also push to f38 and rawhide later today.


Why is f36/f37 the playground for f38/rawhide? Shouldn't this be done
in the reverse order?


This is a security release, it fixes 8 MODERATE CVEs
(https://www.openssl.org/news/secadv/20230207.txt)

I kindly ask you to test the version so it could be rolled up earlier.


I really would hope that testing happens in rawhide before it is pushed
into f36/f37 :(

Paul
___
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: Heads-up: OpenSSL update

[Dmitry Belyavskiy]

Dear Paul

On Thu, Feb 9, 2023 at 6:56 PM Paul Wouters  wrote:
>
> On Thu, 9 Feb 2023, Dmitry Belyavskiy wrote:
>
> > I've just pushed updates of OpenSSL to the 3.0.8 version to f36/37.
> > I will also push to f38 and rawhide later today.
>
> Why is f36/f37 the playground for f38/rawhide? Shouldn't this be done
> in the reverse order?

In fact all the updates landed simultaneously.

> > This is a security release, it fixes 8 MODERATE CVEs
> > (https://www.openssl.org/news/secadv/20230207.txt)
> >
> > I kindly ask you to test the version so it could be rolled up earlier.
>
> I really would hope that testing happens in rawhide before it is pushed
> into f36/f37 :(

As there are many vulnerabilities, I preferred to push the releases ASAP.
Previously I was blamed for pushing only CVE fixes instead of updating.

I don't expect any regressions, speaking frankly.

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

Re: Heads-up: OpenSSL update

[Michel Alexandre Salim]

Hi Dmitry,

On Thu, 2023-02-09 at 18:02 +0100, Dmitry Belyavskiy wrote:
> Dear colleagues,
> 
> I've just pushed updates of OpenSSL to the 3.0.8 version to f36/37.
> I will also push to f38 and rawhide later today.
> 
> This is a security release, it fixes 8 MODERATE CVEs
> (https://www.openssl.org/news/secadv/20230207.txt)
> 
> I kindly ask you to test the version so it could be rolled up
> earlier.
> 
Thanks for the heads-up! Will test and rebase the openssl3 package in
EPEL8 too.

Best regards,

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


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

Re: [Fedocal] Reminder meeting : ELN SIG

[Stephen Gallagher]

On Thu, Feb 9, 2023 at 7:00 AM  wrote:
>
> Dear all,
>
> You are kindly invited to the meeting:
>ELN SIG on 2023-02-10 from 12:00:00 to 13:00:00 US/Eastern
>At fedora-meet...@irc.libera.chat
>
> The meeting will be about:

We will hold an Open Floor meeting this week.
___
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 Linux 38 branched

[Tomas Hrcka]

Hi All,

Fedora Linux 38 has now been branched, please be sure to do a git pull
--rebase to pick up the new branch, as an additional reminder
rawhide/f39 has been completely isolated from previous releases, so
this means that anything you do for f38 you also have to do in the
rawhide branch and do a build there. There will be a Fedora Linux 38 compose
and it'll appear in
http://dl.fedoraproject.org/pub/fedora/linux/development/38/ once
complete.

Bodhi is currently enabled in the f38 branch like it is for rawhide,
with automatic update creation. At the hit Beta change freeze point
in the Fedora Linux 38 schedule[1] updates-testing will be enabled and
manual bodhi updates will be required as in all stable releases.

Two things to remember:

1. The modules will be built for a new platform:f39
2. F38/branched release is frozen right now until we get a successful
compose, expect that your f38 builds won't be available immediately.

Thanks for understanding.
Tomas Hrcka
Fedora Release Engineering

[1] https://fedorapeople.org/groups/schedule/f-38/f-38-key-tasks.html
___
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: Fedora 38 mass rebuild is finished

[Dan Horák]

On Wed, 8 Feb 2023 17:37:09 +0100
Dan Horák  wrote:

> On Wed, 08 Feb 2023 15:24:47 +
> Sérgio Basto  wrote:
> 
> > On Tue, 2023-01-31 at 12:03 +, Zbigniew Jędrzejewski-Szmek wrote:  
> > > On Mon, Jan 30, 2023 at 04:45:37PM -0800, Kevin Fenzi wrote:
> > > > On Tue, Jan 24, 2023 at 09:42:10AM +, Zbigniew Jędrzejewski-
> > > > Szmek wrote:
> > > > > On Mon, Jan 23, 2023 at 06:52:30PM -0800, Kevin Fenzi wrote:
> > > > > > On Mon, Jan 23, 2023 at 10:26:18PM +, Sérgio Basto wrote:
> > > > > > > 
> > > > > > > I found more 5 with
> > > > > > > https://koji.fedoraproject.org/koji/tasks?owner=releng&state=active&view=tree&method=all&order=-id
> > > > > > > 
> > > > > > > 96481236 build (f38-rebuild,
> > > > > > > /rpms/yaksa.git:528d57e3c954abfedba6f530f5ac09abaa9170fa)
> > > > > > > 
> > > > > > > 96474133 build (f38-rebuild, /rpms/trace-
> > > > > > > cmd.git:d9631ac81ad4f30b7ca5ed8a7d3b57131c545080)
> > > > > > > 
> > > > > > > 96404064 build (f38-rebuild, /rpms/perl-
> > > > > > > SDL.git:347cf3fb5ac90e14b96381722bc335744077e967)
> > > > > > > 
> > > > > > > 96383273 build (f38-rebuild,
> > > > > > > /rpms/octave.git:93e5fb4a813805c66ec7107da26be2d52039106d
> > > > > > > 
> > > > > > > 96368979 build (f38-rebuild,
> > > > > > > /rpms/libtracecmd.git:121d11cfd26c3a0d61671b83f32b0be1ec75f1f
> > > > > > > f)
> > > > > > 
> > > > > > Yes, I have canceled all those now. 
> > > > > 
> > > > > I started builds for all of those now.
> > > > 
> > > > All of them have hung again after running since you started them. 
> > > > 
> > > > I think someone is going to need to try and build them in local
> > > > mock and
> > > > see where they are getting stuck. 
> > > > 
> > > > Can you cancel them again? Or would you like me to try and look and
> > > > see
> > > > what they are hung on?
> > > 
> > > I cancelled them now. All five were still hung.
> > > It's up to the maintainers to figure out what is going.
> > > E.g. yaksa was hanging in tests…
> > 
> > Any news about these packages that hang on koji ? we may include opencv
> > package on this list.
> > 
> > Last lines of build opencv on ppc64le are [1] and after we got 55385703
> > (55 millions) of lines with "mashing detected" message,  the log file
> > have 2,30G ! 
> > 
> > Also I see "buffer overflow detected ***: terminated cat: /symlink2-
> > fakechroot: No such file or directory " on fakechroot  
> 
> this looks weird, I am trying a local build

and they confirm the observation from koji, both a small and a big
machine produce tons of the error messages, but the build itself
finishes successfully. I will keep looking further.


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

Heads up: lua-posix 36.1 headed to Rawhide

[Michel Alexandre Salim]

Dear all,

Now that F38 is branched, it's probably a good time to upgrade lua-
posix from 35.1 to 36.1.

Packages potentially affected:

❯ rpmdistro-repoquery fedora rawhide --whatrequires lua-posix
Last metadata expiration check: 0:02:18 ago on Thu Feb  9 13:15:29
2023.
Lmod-0:8.7.18-1.fc38.x86_64
copy-jdk-configs-0:4.1-2.fc38.noarch
lua-readline-0:3.2-2.fc38.x86_64

There are some breaking changes in 36.0, so I'm going to only update in
Rawhide and we can revisit if we need to update in 38 and stable
branches later, but I tend towards keeping them at 35.1 unless there's
a major issue we can't fix without upgrading.

https://github.com/luaposix/luaposix/releases

Incompatible Changes

posix.spawn always returns integer, string whether fork fails
immediately, or whatever waiting for the spawned process reports. When
the second result value is "exited", the first is the exit status; for
"killed" or "stopped" second value, the first is the signal number that
caused it; otherwise first the errno error number, followed by the
associated error string.

The documentation for posix.spawn has always been wrong up until
now, but this small change to simplify the returned results will
require checking whether the second result value is "exited", "killed",
"stopped" or any other string before interpreting the first result...
which was also necessary in prior versions too, but now the
interpretion of non-zero status by clients is less messy and somewhat
compatible with the happy path of using previous releases.

Argument type errors for posix.sys.msg.msgctl,
posix.sys.resource.setrlimit, posix.sys.socket.bind,
posix.sys.socket.connect, posix.sys.socket.getaddrinfo,
posix.sys.socket.sendto and posix.time.nanosleep all use "integer" in
full rather than "int".

Best regards,

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


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

Re: Risc-V SIG?

[Jeff Law]

On 2/9/23 08:49, David Abdurachmanov wrote:


There are two generic issues in Fedora that keep popping up:
- Wrong assumption about valgrind. Those are easy to fix, but are in a
number of places. Note that valgrind upstreaming will happen
relatively soonish too.
Yea, but I don't have a high degree of confidence in that code.  I was 
looking at it a couple weeks ago and it's just not in that good of 
shape.I certainly hope they're able to fix things and get it working 
on real code rather than just trivial tests as valgrind is the biggest 
missing piece in the tools world as I narrowly define it :-)






There is also an issue in how sub-word atomics are being handled in
riscv64 today. This basically means that packages like to fail
building somewhat sporadically. Basically you must link to libatomic
and GCC SPEC will do that if -pthread is used (this covers most of the
cases, but not all). Also a number of packages don't use -pthread and
just -lpthread. There are patches to improve this, but that's more
likely GCC 14 material now. A quick "fix" (not the best) would be
remove -pthread check and let GCC to attempt linking to libatomic in
all cases (--as-needed -latomic).
subword atomics are a pain point.  RIght or wrong, they got pulled into 
the largeer atomics issues in the risc-v space.   Basically neither GCC 
nor LLVM actually implement the atomics correctly and there's some 
belief that we need to fix that first, then we can add the inline 
subword atomics.


Jeff
___
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

Should python-mysql be retired in Fedora and EPEL?

[Michel Alexandre Salim]

Dear fellow Fedorans,

It seems that python-mysqlclient will now transparently upgrade python-
mysql since 2.1.1-2 (for Fedora):
https://src.fedoraproject.org/rpms/python-mysqlclient/c/1da9400c1c9c8eb8b044f6976e1a07f06226ed3e?branch=rawhide
and 1.4.6-6 (EPEL 8)
https://src.fedoraproject.org/rpms/python-mysqlclient/c/cc24faae44f40898ba87e93f9dfefbc9a7fb09e1?branch=epel8

(python-mysql was never in EPEL9)

The two upstreams are the same (python-mysql points to
https://github.com/PyMySQL/mysqlclient-python but that just redirects
to https://github.com/PyMySQL/mysqlclient)

However it seems that python-mysql itself is not retired -- should it?
Seems like there's no release in which trying to install it won't just
install python-mysqlclient instead anyway.

The maintainers don't seem to overlap:
- python-mysql maintained by mschorm and hobbes1069
- python-mysqlclient maintained by fab

(the changes to make mysqlclient obsolete mysql are made by non-
maintainers)

Best regards,

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


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

Re: Should python-mysql be retired in Fedora and EPEL?

[Michel Alexandre Salim]

cc-ing the epel-devel list too

On Thu, 2023-02-09 at 14:39 -0600, Michel Alexandre Salim wrote:
> Dear fellow Fedorans,
> 
> It seems that python-mysqlclient will now transparently upgrade
> python-
> mysql since 2.1.1-2 (for Fedora):
> https://src.fedoraproject.org/rpms/python-mysqlclient/c/1da9400c1c9c8eb8b044f6976e1a07f06226ed3e?branch=rawhide
> and 1.4.6-6 (EPEL 8)
> https://src.fedoraproject.org/rpms/python-mysqlclient/c/cc24faae44f40898ba87e93f9dfefbc9a7fb09e1?branch=epel8
> 
> (python-mysql was never in EPEL9)
> 
> The two upstreams are the same (python-mysql points to
> https://github.com/PyMySQL/mysqlclient-python but that just redirects
> to https://github.com/PyMySQL/mysqlclient)
> 
> However it seems that python-mysql itself is not retired -- should
> it?
> Seems like there's no release in which trying to install it won't
> just
> install python-mysqlclient instead anyway.
> 
> The maintainers don't seem to overlap:
> - python-mysql maintained by mschorm and hobbes1069
> - python-mysqlclient maintained by fab
> 
> (the changes to make mysqlclient obsolete mysql are made by non-
> maintainers)
> 
> Best regards,
> 
> ___
> 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

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


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

Re: Heads-up: OpenSSL update

[Michel Alexandre Salim]

Hi Dmitry,

On Thu, 2023-02-09 at 18:02 +0100, Dmitry Belyavskiy wrote:
> Dear colleagues,
> 
> I've just pushed updates of OpenSSL to the 3.0.8 version to f36/37.
> I will also push to f38 and rawhide later today.
> 
> This is a security release, it fixes 8 MODERATE CVEs
> (https://www.openssl.org/news/secadv/20230207.txt)
> 
> I kindly ask you to test the version so it could be rolled up
> earlier.
> 
Would you happen to have any insight into why some tests are failing
when rebuilt on EPEL 8?

This is with a scratch build of EPEL 8's openssl3 (which is just a
rebuild of openssl but renamed and with some subpackages removed)
https://koji.fedoraproject.org/koji/taskinfo?taskID=97314920

The errors are all identical, so to be doubly sure I rebuilt the centos
9 srpm (only on x86_64), just slightly modified to change the g++ BR to
gcc-c++, and it failed identically
https://koji.fedoraproject.org/koji/taskinfo?taskID=97318473

# The following symbols are missing in libcrypto.so.3:
#   OPENSSL_strcasecmp
#   OPENSSL_strncasecmp
# The following symbols are extra in libcrypto.so.3:
#   BIO_dgram_is_sctp
#   BIO_dgram_sctp_msg_waiting
#   BIO_dgram_sctp_notification_cb
#   BIO_dgram_sctp_wait_for_dry
#   BIO_new_dgram_sctp
#   BIO_s_datagram_sctp
not ok 2 - check that there are no missing symbols in libcrypto.so.3
# -
-03-test_internal_modes.t ... ok
03-test_internal_namemap.t . ok
03-test_internal_curve448.t  ok
03-test_internal_poly1305.t  ok
# Looks like you failed 1 test of 4.01-test_symbol_presence.t
.. 
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/4 subtests 
02-test_lhash.t ...

Thanks,

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


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

Re: Hoping to disable i686 and 32-bit arm for Podman and related tools for existing Fedora releases

[Michel Alexandre Salim]

On Wed, 2023-02-08 at 22:24 -0500, Demi Marie Obenour wrote:
> On 2/7/23 07:52, Peter Robinson wrote:
> > On Tue, Feb 7, 2023 at 12:36 PM Lokesh Mandvekar
> >  wrote:
> > > 
> > > On Tue, Feb 7, 2023 at 5:56 PM Peter Robinson
> > >  wrote:
> > > 
> > > > There are still active users of Fedora IoT 36 on armhfp using
> > > > containers so I suspect they may be unhappy of they go away
> > > > before the
> > > > F-36 EOL in the late May/early June timeframe.
> > > 
> > > I see. I guess we could leave armhfp be until then. Btw, just
> > > curious
> > > what happens to IoT on armhfp once f36 goes EOL.
> > > Would users have to pick something else?
> > 
> > Basically yes.
> 
> Not sure if Debian supports armhfp, but in the long term the answer
> is
> going to be to find a distro that cross-compiles everything.
> 
But of course: https://wiki.debian.org/SupportedArchitectures

It also supports mips (both 32- and 64-bit) because... 

Cheers,

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


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

running code for whatever arch (was: Re: Hoping to disable i686 and 32-bit arm for Podman and related tools for existing Fedora releases)

[Roberto Ragusa]

On 2/8/23 15:43, Stephen Gallagher wrote:


More generally podman can run containers of foreign architectures using
qemu-user emulation, albeit with an obvious speed penalty. Still this
has been useful for testing issues on non-x86_64 arches where hardware
access is hard to come by.


Hold up, this is a really useful tip buried in this thread. Is there a
good howto or example of how to do this? This deserves a Fedora
Magazine or CommBlog article!


Well, I was just left amazed just a couple of days ago when mounting the
microSD of my raspberry on Fedora.
The idea was to just fsck the filesystem, then I mounted it,
played a bit around and then realized that there might have been
updates available for some packages.
So, by habit more than thinking, I've just "chroot" into the
mounted filesystem and run "apt update; apt upgrade".
And while the commands were working I realized "wait a moment,
this is supposed to be arm code, but it is running fine!".
Quick "ps", wow, so they are using qemu transparently.
Don't tell me that they are supporting...
... yes they are.
An absolutely obscure gem feature deserving much more publicity.

# ls /proc/sys/fs/binfmt_misc/
kshcomp  qemu-hexagon   qemu-mips64 qemu-ppc  qemu-sh4  
qemu-xtensaeb
qemu-aarch64 qemu-hppa  qemu-mips64el   qemu-ppc64qemu-sh4eb
register
qemu-aarch64_be  qemu-m68k  qemu-mipsel qemu-ppc64le  qemu-sparc
status
qemu-alpha   qemu-microblazeqemu-mipsn32qemu-riscv32  
qemu-sparc32plus  windows
qemu-arm qemu-microblazeel  qemu-mipsn32el  qemu-riscv64  qemu-sparc64  
windowsPE
qemu-armeb   qemu-mips  qemu-or1k   qemu-s390xqemu-xtensa

Best regards.

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

Re: Risc-V SIG?

[Jun Aruga (he / him)]

> Yep. Sigs exist because they say they do. ;)
>
> The risc-v sig has been around for a while, but I guess a sig wiki page
> was never made. :(
>
> So, sure, we should setup a page and point to the discussion topic and
> irc/matrix rooms. :)
>
> If you could do that it would be great... otherwise I will try and do
> so.

I hope someone will add the RISC-V SIG's page link to the page below,
after someone creates the page.
https://fedoraproject.org/wiki/Category:SIGs

-- 
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See  for
the timezone.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Should python-mysql be retired in Fedora and EPEL?

[Gary Buhrmaster]

On Thu, Feb 9, 2023 at 8:40 PM Michel Alexandre Salim
 wrote:
>
> Dear fellow Fedorans,
>
> It seems that python-mysqlclient will now transparently upgrade python-
> mysql since 2.1.1-2 (for Fedora):
> https://src.fedoraproject.org/rpms/python-mysqlclient/c/1da9400c1c9c8eb8b044f6976e1a07f06226ed3e?branch=rawhide
> and 1.4.6-6 (EPEL 8)
> https://src.fedoraproject.org/rpms/python-mysqlclient/c/cc24faae44f40898ba87e93f9dfefbc9a7fb09e1?branch=epel8
>
> (python-mysql was never in EPEL9)

However, as I recall, since the python-mysqlclient
in EPEL9 does not include the obsoletes/requires
on python-mysql, spec files (or applications) that
have a BR/R of python-mysql will not get the
updated python-mysqlclient auto-upgraded.

The EPEL9 python-mysqlclient build should
probably be updated with those obsoletes/requires
tags to minimize surprises.
___
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: Heads-up: OpenSSL update

[Paul Wouters]

On Thu, 9 Feb 2023, Dmitry Belyavskiy wrote:


I've just pushed updates of OpenSSL to the 3.0.8 version to f36/37.
I will also push to f38 and rawhide later today.


Why is f36/f37 the playground for f38/rawhide? Shouldn't this be done
in the reverse order?


In fact all the updates landed simultaneously.


Ahh okay, no worries then :)

Thanks for the updates!

Paul
___
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