Re: VirtualBox and HOST kernel-5.17.12 weirdness

[Ian Laurie]

On 6/16/22 06:36, Hans de Goede wrote:

Hi,

On 6/15/22 07:01, Ian Laurie wrote:

On 6/12/22 14:34, Sérgio Basto wrote:

On Sun, 2022-06-12 at 13:59 +1000, Ian Laurie wrote:

On 6/12/22 11:20, Ian Laurie wrote:

On 6/12/22 09:46, Ian Laurie wrote:

On 6/12/22 00:58, Hans de Goede wrote:

Hi,

On 6/11/22 01:02, Alexander G. M. Smith wrote:

On 2022-06-08 15:00, Alexander G. M. Smith wrote:

Ian Laurie wrote on Friday, 3 June 2022 at 11:17 p.m.:

Is anyone else seeing crashes and other strange events in
VirtualBox
6.1.34 (from RPMFusion) with Linux guests when the Linux
host is
running
Fedora 36 with kernel-5.17.12?

[...]
The weird thing is that it works on other CPUs, an AMD
Athlon X2
and an Intel 10th generation i5-10500H.  Just my Ivy Bridge
Intel
i7-4820K has the problem.  I did try the kernel boot
parameter
mitigations=off, in case the Spectre or other workarounds
were
wrong for Ivy Bridge, but it still didn't work.

One more data point.  It fails on an Intel i5-750 too.  Same
broken
data connections and failed checksums.

My go-to test is to use "dnf clean" followed by "dnf upgrade"
running as root in a console (thus no networking is between
keyboard and computer - pipes often fail).  My server
snapshot
fails to get through the complete dnf upgrade on kernel
5.17.13,
works fine if booting the host with the earlier kernel
5.17.11
(using the GRUB boot menu to pick the older OS).

So, should we report this to VirtualBox?  They seem like the
most
appropriate people.  Kernel people would be a possibility?

Found a relevant bug report:
https://www.virtualbox.org/ticket/20976

And a forum discussion:
https://forums.virtualbox.org/viewtopic.php?f=7&t=106071

Though they don't know that it only happens on certain CPUs
(or
motherboards or ?).  I'll add some notes about that there.

Note the rpmfusion VirtualBox packages now include this fix:
https://build.opensuse.org/package/view_file/Virtualization/virtualbox/fixes_for_kernel_5.18.patch?expand=1
  


See:
https://koji.rpmfusion.org/koji/buildinfo?buildID=22655

Which is supposed to fix this.

Regards,

Hans

I'm currently running this version, with the 5.18 fixes, but it's
not
working with kernels 5.17.12/13 or 14.  A person reporting
success
with 5.18.3 reported not having problems with the 5.17 kernels,
so
maybe there are multiple issues (has been suggested it may be
CPU/chipset related).  I have not yet tried it on 5.18 but I
certainly will today.

Ian


If I understand Sérgio's comment #15 correctly, the 5.18 kernel
fixes
don't address the CPU issues possibly created by CVE-2022-1789
fixes,
so there is probably no point in me trying an early 5.18.  So the
CPU
issues are common to both later 5.17 and 5.18.  Sadly all my
hardware
here falls under the broken category:

[1] ASUS G750JS 1 x Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz
Intel Corporation 4th Gen Core Processor Integrated Graphics
Controller (rev 06)
NVIDIA Corporation GK104M [GeForce GTX 870M] (rev a1)
Fedora 36

[2] Intel NUC i7 NUC11PAH 1 x 11th Gen Intel(R) Core(TM) i7-1165G7
@
2.80GHz
Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01)
Fedora 36


Since it was going to cost me nothing but time, I tested
kernel-5.18.3-200.fc36.x86_64 with my existing
VirtualBox-6.1.34-4.fc36.x86_64 (RPMFusion updates-testing) and to my
astonishment it seems to be working.  On both platforms mentioned
above.  So maybe my understanding about the CVE fixes was not
correct.
Or something got fixed between 5.18.2 and 5.18.3 ?  Anyway the 5.18.3
Fedora kernel on Koji with the latest VirtualBox from RPMFusion still
in
testing seems to be working on 2 h/w platforms that were previously
failing from 5.17.12.

thank you for the feedback , yes you understand me well, but I hadn't
made tests with kernel-5.18.x

After read this thread this afternoon , I realize that I also have one
Intel(R) Core(TM), I have the i5-9300H CPU and I noticed have network
issues with  kernel-5.17.12.  so I downgrade the kernel kernel-5.17.9-
200.fc35.x86_64 and I confirmed that I hadn't the issues with network.

So I was also affected by kernel-5.17.12, but just had weird network
issues ...

So now, I not sure anymore if we have 2 issues or if it all the same
i.e. kvm mitigations which was in first place on kernels 5.18, or even
if virtualbox kernel-5.18 patch is unrelated. The important for me is
kernel-5.18 patch for virtualbox don't have regressions .


Sérgio,

Now that 5.18.3 & 5.18.4 are working as VirtualBox hosts, we seem to have 
problems with 5.18.x as a guest.  For me, 5.18.x kernels are not seeing the network 
interface.  I am seeing this with 5.18.3 and 5.18.4 in the guest, regardless of the 
outer host.  In fact I am seeing this on both Linux and Windows 10 hosts.

This is due the e1000 nic driver accidentally being disabled in
the 5.18 kernels. This is fixed in 5.18.4-301 / 5.18.4-201 / 5.18.4-101

Regards,

Hans
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubs

Re: CMake fails to configure when "-S ." source method is used

[Sérgio Basto]

On Mon, 2022-06-13 at 17:42 -0500, Richard Shaw wrote:
> On Sun, Jun 12, 2022 at 1:03 PM Michal Schorm 
> wrote:
> > See:
> > https://bugzilla.redhat.com/show_bug.cgi?id=2079833
> > 
> 
> 
> Whether it's part of the same problem or not, the "-S ." seems to be
> causing issues for projects that "add_subdirectory()" other projects.
> Not everything is propagating into the sub-project.

Hi , 

please tell me what packages you need fix the cmake builds and I will
try to fix it . 

for reference here some possible fixes 
https://bugzilla.redhat.com/show_bug.cgi?id=2057738

Best regards 

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

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

Non-responsive maintainer check for athmane

[Robert Scheck]

Hello,

does somebody know how to contact Athmane Madjoudj? Yes, one of my requests
is for EPEL, but I would be even happy to maintain the EPEL branches myself
in case of a negative response.

 - https://bugzilla.redhat.com/show_bug.cgi?id=1902857#c2
 - https://bugzilla.redhat.com/show_bug.cgi?id=2080682

I also filed https://bugzilla.redhat.com/show_bug.cgi?id=2097520 to follow
the non-responsive maintainer policy.


Regards,
  Robert


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

Re: Fedora elections voting now open

[Ben Cotton]

This is your final reminder that voting is open for the Fedora Linux
36 elections. Go to the Elections app[1] to cast your vote. Voting
closes at 23:59 UTC on Thursday 16 June. Don't forget to claim your "I
Voted" badge when you cast your ballot. Links to candidate interviews
are in the Elections app and on the Community Blog[2].

[1] https://elections.fedoraproject.org/
[2] https://communityblog.fedoraproject.org/f36-elections-voting-now-open/

-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: VirtualBox and HOST kernel-5.17.12 weirdness

[Hans de Goede]

Hi,

On 6/15/22 07:01, Ian Laurie wrote:
> On 6/12/22 14:34, Sérgio Basto wrote:
>> On Sun, 2022-06-12 at 13:59 +1000, Ian Laurie wrote:
>>> On 6/12/22 11:20, Ian Laurie wrote:
 On 6/12/22 09:46, Ian Laurie wrote:
> On 6/12/22 00:58, Hans de Goede wrote:
>> Hi,
>>
>> On 6/11/22 01:02, Alexander G. M. Smith wrote:
>>> On 2022-06-08 15:00, Alexander G. M. Smith wrote:
 Ian Laurie wrote on Friday, 3 June 2022 at 11:17 p.m.:
> Is anyone else seeing crashes and other strange events in
> VirtualBox
> 6.1.34 (from RPMFusion) with Linux guests when the Linux
> host is
> running
> Fedora 36 with kernel-5.17.12?
 [...]
 The weird thing is that it works on other CPUs, an AMD
 Athlon X2
 and an Intel 10th generation i5-10500H.  Just my Ivy Bridge
 Intel
 i7-4820K has the problem.  I did try the kernel boot
 parameter
 mitigations=off, in case the Spectre or other workarounds
 were
 wrong for Ivy Bridge, but it still didn't work.
>>> One more data point.  It fails on an Intel i5-750 too.  Same
>>> broken
>>> data connections and failed checksums.
>>>
>>> My go-to test is to use "dnf clean" followed by "dnf upgrade"
>>> running as root in a console (thus no networking is between
>>> keyboard and computer - pipes often fail).  My server
>>> snapshot
>>> fails to get through the complete dnf upgrade on kernel
>>> 5.17.13,
>>> works fine if booting the host with the earlier kernel
>>> 5.17.11
>>> (using the GRUB boot menu to pick the older OS).
>>>
>>> So, should we report this to VirtualBox?  They seem like the
>>> most
>>> appropriate people.  Kernel people would be a possibility?
>>>
>>> Found a relevant bug report:
>>> https://www.virtualbox.org/ticket/20976
>>>
>>> And a forum discussion:
>>> https://forums.virtualbox.org/viewtopic.php?f=7&t=106071
>>>
>>> Though they don't know that it only happens on certain CPUs
>>> (or
>>> motherboards or ?).  I'll add some notes about that there.
>> Note the rpmfusion VirtualBox packages now include this fix:
>> https://build.opensuse.org/package/view_file/Virtualization/virtualbox/fixes_for_kernel_5.18.patch?expand=1
>>  
>>
>> See:
>> https://koji.rpmfusion.org/koji/buildinfo?buildID=22655
>>
>> Which is supposed to fix this.
>>
>> Regards,
>>
>> Hans
> I'm currently running this version, with the 5.18 fixes, but it's
> not
> working with kernels 5.17.12/13 or 14.  A person reporting
> success
> with 5.18.3 reported not having problems with the 5.17 kernels,
> so
> maybe there are multiple issues (has been suggested it may be
> CPU/chipset related).  I have not yet tried it on 5.18 but I
> certainly will today.
>
> Ian
>
 If I understand Sérgio's comment #15 correctly, the 5.18 kernel
 fixes
 don't address the CPU issues possibly created by CVE-2022-1789
 fixes,
 so there is probably no point in me trying an early 5.18.  So the
 CPU
 issues are common to both later 5.17 and 5.18.  Sadly all my
 hardware
 here falls under the broken category:

 [1] ASUS G750JS 1 x Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz
 Intel Corporation 4th Gen Core Processor Integrated Graphics
 Controller (rev 06)
 NVIDIA Corporation GK104M [GeForce GTX 870M] (rev a1)
 Fedora 36

 [2] Intel NUC i7 NUC11PAH 1 x 11th Gen Intel(R) Core(TM) i7-1165G7
 @
 2.80GHz
 Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01)
 Fedora 36

>>> Since it was going to cost me nothing but time, I tested
>>> kernel-5.18.3-200.fc36.x86_64 with my existing
>>> VirtualBox-6.1.34-4.fc36.x86_64 (RPMFusion updates-testing) and to my
>>> astonishment it seems to be working.  On both platforms mentioned
>>> above.  So maybe my understanding about the CVE fixes was not
>>> correct.
>>> Or something got fixed between 5.18.2 and 5.18.3 ?  Anyway the 5.18.3
>>> Fedora kernel on Koji with the latest VirtualBox from RPMFusion still
>>> in
>>> testing seems to be working on 2 h/w platforms that were previously
>>> failing from 5.17.12.
>> thank you for the feedback , yes you understand me well, but I hadn't
>> made tests with kernel-5.18.x
>>
>> After read this thread this afternoon , I realize that I also have one
>> Intel(R) Core(TM), I have the i5-9300H CPU and I noticed have network
>> issues with  kernel-5.17.12.  so I downgrade the kernel kernel-5.17.9-
>> 200.fc35.x86_64 and I confirmed that I hadn't the issues with network.
>>
>> So I was also affected by kernel-5.17.12, but just had weird network
>> issues ...
>>
>> So now, I not sure anymore if we have 2 issues or if it all the same
>> i.e. kvm mitigations which was in first place on kernels 5.18, or even
>> if virtualbox kernel-

Tip for Reporting Spam on Mailing Lists

[Jeffrey Ollie]

Do not reply to or forward spam emails back to the mailing list. You just
became part of the problem and many/most spam scanning services now
consider YOUR email to be spam. Gmail in particular makes it very difficult
to manage the spam status of individual emails (seems like you can only
report/unreport whole conversations).

-- 
Jeff Ollie
The majestik møøse is one of the mäni interesting furry animals in Sweden.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: PSA: openQA failures in tests using Firefox

[Adam Williamson]

On Wed, 2022-05-25 at 11:42 +0200, Martin Stransky wrote:
> On 5/25/22 08:58, Adam Williamson wrote:
> > and what I think is some kind of odd regression in Firefox 100 which
> > makes typing into some text entry boxes in the Cockpit and FreeIPA web
> > UIs not work reliably (this affects realmd_join_cockpit and
> > upgrade_realmd_client).
> 
> It's a good idea to file a bug at https://bugzilla.redhat.com
> 
> The typing problem may be 
> https://bugzilla.mozilla.org/show_bug.cgi?id=1771104 and I'll backport 
> that to Fedora.

Late follow-up on this - the problem did magically disappear at some
point, so either it was caused by magic elves, or you did backport this
fix and it did the trick. In which case, thanks. :D
-- 
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net

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

Re: Updated criteria proposal: networking requirements

[Adam Williamson]

On Mon, 2022-06-13 at 03:09 +0200, Kevin Kofler via devel wrote:
> Adam Williamson wrote:
> > Using the default network configuration tools for the console and for
> > release-blocking desktops, it must be possible to establish a working
> > connection to common OpenVPN, openconnect-supported and vpnc-supported
> > VPN servers with typical configurations.
> 
> Is "common" a rationale or a restriction? I.e., are all VPN types supported 
> by OpenConnect automatically "common", or which ones are "common"?

It's a restriction. I'm not sure we would actually want to block the
release on absolutely every possible openconnect VPN configuration. I
admit I'm not an expert on the details, which is why it's worded quite
generally. If someone wants to try and write something more specific,
that'd be great.
> 
> (In particular, I care about ocserv.)

DDG tells me that's an open source server intended to be compatible
with openconnect clients, i.e. an open source alternative to the
proprietary CISCO server. So in the case we had a bug that broke
connections to ocserv servers but not connections to the official Cisco
server, we'd have to try and figure out how widely ocserv is used, I
guess.
> 
> > Footnote titled "Supported servers and configurations": As there are
> > many different VPN server applications and configurations, blocker
> > reviewers must use their best judgment in determining whether
> > violations of this criterion are likely to be encountered commonly
> > enough to block a release, and if so, at which milestone. As a general
> > principle, the more people are likely to use affected servers and the
> > less complicated the configuration required to hit the bug, the more
> > likely it is to be a blocker.
> 
> So it is a case by case decision by the reviewer? Then why bother having 
> written criteria at all?

To at least clearly establish that bugs in this area *can* be blockers.
Without this addition, on a strict reading of the criteria you have to
be fairly creative to interpret them as allowing *any* kind of bug in
VPN support to be release-blocking. And they really don't say anything
specific about networking at all. In the past we've accepted complete
networking fails as violations of things like the "browser must work"
or "updates must work" criteria, but that feels quite a lot like a
hack, and it's harder to keep a straight face when applying a hack like
that to a bug which isn't as bad as "networking is completely busted
for a lot of people".

As the guy who writes most of the criteria, what I'd really like to
have is completely objective rules that remove the need for any kind of
subjective evaluation. But experience suggests this is really hard to
do without painting yourself into all sorts of weird corners. It's very
hard (for me, anyway) to imagine every possible proposed blocker
related to VPN or network functionality in general and, ahead of time,
write rules that decide which ones are and are not blockers. But
there's clearly a feeling that, in general, we should not be shipping
Fedora with major bugs in VPN support. So, this is my best effort.

As I wrote above, if you or anyone else can draft some sufficiently
detailed and comprehensive rules for this area which remove or reduce
the need for subjective case-by-case evaluations, that'd be fantastic
and I'd be all in favour. But this was as specific as I could get
myself. It seems like in some areas we just have to go with this
"criterion establishes broad principles / specific issues are evaluated
case-by-case" approach.
-- 
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net

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

Fedora CoreOS Meeting Minutes 2022-06-15

[Dusty Mabe]

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2022-06-15/fedora_coreos_meeting.2022-06-15-16.30.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2022-06-15/fedora_coreos_meeting.2022-06-15-16.30.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2022-06-15/fedora_coreos_meeting.2022-06-15-16.30.log.html
   


#fedora-meeting-1: fedora_coreos_meeting



Meeting started by dustymabe at 16:30:11 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2022-06-15/fedora_coreos_meeting.2022-06-15-16.30.log.html
.



Meeting summary
---
* roll call  (dustymabe, 16:30:18)

* Action items from last meeting  (dustymabe, 16:36:26)
  * jlebon has scheduled a meeting to discuss Fedora CoreOS layering use
cases  (jlebon, 16:37:13)
  * dustymabe scheduled met with jlebon, lucab, saqali this morning to
narrow down changes to discuss  (dustymabe, 16:38:26)
  * ACTION: cverna to open ticket for FCOS as an edition and update
(dustymabe, 16:39:24)

* New Package Request: qemu-user-static  (dustymabe, 16:39:52)
  * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1088
(dustymabe, 16:40:03)
  * AGREED: For now we will include the qemu-user-static-x86 package on
non x86_64 FCOS images to allow "out of the box" access to the large
inventory of containers only built for x86_64. We may revisit this
in the future once CoreOS layering is more mature or if there comes
a time when containers for other architectures are as ubiquitous.
(dustymabe, 17:08:29)

* tracker: Fedora 37 changes considerations  (dustymabe, 17:09:15)
  * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1222
(dustymabe, 17:09:19)

* open floor  (dustymabe, 17:34:59)
  * ACTION: jlebon to open investigation tickets for the IMA/FIDO
changes   (dustymabe, 17:38:27)

Meeting ended at 17:40:01 UTC.




Action Items

* cverna to open ticket for FCOS as an edition and update
* jlebon to open investigation tickets for the IMA/FIDO changes




Action Items, by person
---
* jlebon
  * jlebon to open investigation tickets for the IMA/FIDO changes
* **UNASSIGNED**
  * cverna to open ticket for FCOS as an edition and update




People Present (lines said)
---
* dustymabe (130)
* jlebon (51)
* zodbot (22)
* miabbott (12)
* jdoss (6)
* walters (5)
* jmarrero (4)
* ravanelli (3)
* lorbus (2)
* saqali (1)
* aaradhak[m] (1)
* x3mboy (1)
* mnguyen (1)




Generated by `MeetBot`_ 0.4

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

Re: F37 proposal: Fallback Hostname (System-Wide Change proposal)

[Matthew Miller]

On Wed, Jun 15, 2022 at 02:11:11PM +0200, Kamil Paral wrote:
> I think we currently hardcode all live images to have "localhost-live"
> hostname in the kickstart, because of some x11 bug a long time ago which
> failed with a plain "localhost":
> https://pagure.io/fedora-kickstarts/blob/main/f/fedora-live-base.ks#_207

Oh, _there's_ some irony!

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

srt soname change

[Yanko Kaneti]

Hello,

I've just built srt-1.5.0 in rawhide witch comes with major API
additions and ABI changes. The shared library has a new soname 
libsrt.so.1.5.  Most projects should work with a bump-rebuild (tested
with ffmpeg)

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

Re: Rename Airspy

[Richard W.M. Jones]

On Wed, Jun 15, 2022 at 12:08:19PM -, Buford T. Justice wrote:
> OK.  That makes sense.

Note you don't need to rename the package in order to do what you
want, the maintainer could add:

Provides: airspy = %{version}-%{release}

(assuming there isn't already another package called airspy, nor one
likely to be added in future.)

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

Re: F37 proposal: Fallback Hostname (System-Wide Change proposal)

[Kamil Paral]

On Tue, Jun 14, 2022 at 4:50 PM Michael Catanzaro 
wrote:

> I think we should add this.
>
> However, gnome-initial-setup is a bit late because currently anaconda
> uses hostname to name your btrfs subvolumes. :(
>
> anaconda would perhaps be a better place, but only if it uses hostnamed
> so as to allow spaces, Unicode, etc. We don't want anaconda to use
> stricter rules for hostnames than the installed system does.
>

I think we currently hardcode all live images to have "localhost-live"
hostname in the kickstart, because of some x11 bug a long time ago which
failed with a plain "localhost":
https://pagure.io/fedora-kickstarts/blob/main/f/fedora-live-base.ks#_207

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

Fedora-Rawhide-20220615.n.0 compose check report

[Fedora compose checker]

Missing expected images:

Minimal raw-xz armhfp

Compose FAILS proposed Rawhide gating check!
3 of 43 required tests failed
openQA tests matching unsatisfied gating requirements shown with **GATING** 
below

Failed openQA tests: 24/231 (x86_64), 16/161 (aarch64)

New failures (same test not failed in Fedora-Rawhide-20220614.n.0):

ID: 1298616 Test: x86_64 KDE-live-iso desktop_notifications_live
URL: https://openqa.fedoraproject.org/tests/1298616
ID: 1298635 Test: x86_64 Silverblue-dvd_ostree-iso anaconda_help
URL: https://openqa.fedoraproject.org/tests/1298635
ID: 1298657 Test: x86_64 Cloud_Base-qcow2-qcow2 base_services_start@uefi
URL: https://openqa.fedoraproject.org/tests/1298657
ID: 1298753 Test: x86_64 Workstation-upgrade desktop_login
URL: https://openqa.fedoraproject.org/tests/1298753
ID: 1298770 Test: x86_64 Workstation-upgrade apps_startstop
URL: https://openqa.fedoraproject.org/tests/1298770
ID: 1298862 Test: x86_64 universal install_xfs
URL: https://openqa.fedoraproject.org/tests/1298862
ID: 1298870 Test: aarch64 universal install_blivet_btrfs@uefi
URL: https://openqa.fedoraproject.org/tests/1298870

Old failures (same test failed in Fedora-Rawhide-20220614.n.0):

ID: 1298562 Test: x86_64 Server-dvd-iso server_freeipa_replication_master
URL: https://openqa.fedoraproject.org/tests/1298562
ID: 1298566 Test: x86_64 Server-dvd-iso 
server_role_deploy_domain_controller **GATING**
URL: https://openqa.fedoraproject.org/tests/1298566
ID: 1298571 Test: x86_64 Server-dvd-iso server_realmd_join_kickstart 
**GATING**
URL: https://openqa.fedoraproject.org/tests/1298571
ID: 1298572 Test: x86_64 Server-dvd-iso server_freeipa_replication_replica
URL: https://openqa.fedoraproject.org/tests/1298572
ID: 1298578 Test: x86_64 Server-dvd-iso realmd_join_cockpit
URL: https://openqa.fedoraproject.org/tests/1298578
ID: 1298579 Test: x86_64 Server-dvd-iso realmd_join_sssd **GATING**
URL: https://openqa.fedoraproject.org/tests/1298579
ID: 1298580 Test: x86_64 Server-dvd-iso server_freeipa_replication_client
URL: https://openqa.fedoraproject.org/tests/1298580
ID: 1298624 Test: x86_64 KDE-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/1298624
ID: 1298629 Test: x86_64 KDE-live-iso desktop_login
URL: https://openqa.fedoraproject.org/tests/1298629
ID: 1298632 Test: x86_64 KDE-live-iso desktop_printing
URL: https://openqa.fedoraproject.org/tests/1298632
ID: 1298639 Test: x86_64 Silverblue-dvd_ostree-iso release_identification
URL: https://openqa.fedoraproject.org/tests/1298639
ID: 1298701 Test: aarch64 Server-dvd-iso 
server_role_deploy_domain_controller@uefi
URL: https://openqa.fedoraproject.org/tests/1298701
ID: 1298703 Test: aarch64 Server-dvd-iso 
server_freeipa_replication_master@uefi
URL: https://openqa.fedoraproject.org/tests/1298703
ID: 1298711 Test: aarch64 Server-dvd-iso realmd_join_cockpit@uefi
URL: https://openqa.fedoraproject.org/tests/1298711
ID: 1298712 Test: aarch64 Server-dvd-iso realmd_join_sssd@uefi
URL: https://openqa.fedoraproject.org/tests/1298712
ID: 1298713 Test: aarch64 Server-dvd-iso server_realmd_join_kickstart@uefi
URL: https://openqa.fedoraproject.org/tests/1298713
ID: 1298714 Test: aarch64 Server-dvd-iso 
server_freeipa_replication_replica@uefi
URL: https://openqa.fedoraproject.org/tests/1298714
ID: 1298715 Test: aarch64 Server-dvd-iso 
server_freeipa_replication_client@uefi
URL: https://openqa.fedoraproject.org/tests/1298715
ID: 1298740 Test: aarch64 Workstation-raw_xz-raw.xz gnome_text_editor@uefi
URL: https://openqa.fedoraproject.org/tests/1298740
ID: 1298761 Test: x86_64 Workstation-upgrade desktop_fprint
URL: https://openqa.fedoraproject.org/tests/1298761
ID: 1298785 Test: aarch64 Workstation-upgrade gnome_text_editor@uefi
URL: https://openqa.fedoraproject.org/tests/1298785
ID: 1298818 Test: x86_64 universal install_arabic_language
URL: https://openqa.fedoraproject.org/tests/1298818
ID: 1298869 Test: aarch64 universal install_asian_language@uefi
URL: https://openqa.fedoraproject.org/tests/1298869
ID: 1298872 Test: aarch64 universal install_arabic_language@uefi
URL: https://openqa.fedoraproject.org/tests/1298872
ID: 1298922 Test: x86_64 Server-dvd-iso install_updates_nfs
URL: https://openqa.fedoraproject.org/tests/1298922
ID: 1298927 Test: aarch64 Server-dvd-iso install_updates_nfs@uefi
URL: https://openqa.fedoraproject.org/tests/1298927
ID: 1298929 Test: x86_64 universal support_server
URL: https://openqa.fedoraproject.org/tests/1298929
ID: 1298931 Test: x86_64 universal install_kickstart_nfs
URL: https://openqa.fedoraproject.org/tests/1298931
ID: 1298932 Test: x86_64 universal install_pxeboot
URL: https://openqa.fedoraproject.org/tests/1298932
ID: 1298933 Test: x86_64 universal install_pxeboot@uefi
URL: https://openqa.fedoraproject.org/tests/1298933
ID: 1298934 Test: aarch64 universal support_server@uefi
URL: https://openq

Re: Rename Airspy

[Buford T. Justice]

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

Re: Rename Airspy

[Petr Pisar]

V Wed, Jun 15, 2022 at 07:00:26AM -, Buford T. Justice napsal(a):
> For the regular Airspy (not HF+), why is the package called "airspyone_host"?

Bacause it comes from git repository called "airspyone_host"
. Fedora names packages after
upstream. This upstream named it airspyone_host.

> So it would be nice to simply do:
> 
> sudo dnf install airspy airspyhf
> 
You can request this enhancement at
.

-- Petr


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

Fedora Hatch Cork, Ireland - July 13th & 14th

[Aoife Moloney]

Hi Fedora friends!

In case you missed it, the Fedora Project has granted some funding for a
Hatch event in Cork, Ireland on Wednesday July 13th & Thursday July 14th
2022 - very exciting! For more details on how to attend, some terms and
conditions and what the mini-conference is about, check out the mail that
hit the announce list yesterday here
https://lists.fedoraproject.org/archives/list/annou...@lists.fedoraproject.org/thread/YWJJ5FOUZCTL3AARGXDHNRRRA4GN2UJQ/?sort=date

Feel free to reach out to me too if you have any other questions and it
would be great to see some Fedora-faces in person in Cork next month!


Kindest regards,
Aoife

-- 

Aoife Moloney

Product Owner

Community Platform Engineering Team

Red Hat EMEA 

Communications House

Cork Road

Waterford

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

Fedora rawhide compose report: 20220615.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20220614.n.0
NEW: Fedora-Rawhide-20220615.n.0

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

Size of added packages:  3.68 MiB
Size of dropped packages:0 B
Size of upgraded packages:   1.95 GiB
Size of downgraded packages: 0 B

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

= ADDED IMAGES =

= DROPPED IMAGES =
Image: Silverblue dvd-ostree aarch64
Path: 
Silverblue/aarch64/iso/Fedora-Silverblue-ostree-aarch64-Rawhide-20220614.n.0.iso

= ADDED PACKAGES =
Package: golang-github-cli-gh-0.0.3-1.20220614git9dbbfe2.fc37
Summary: A Go module for interacting with gh and the GitHub API from the 
command line
RPMs:golang-github-cli-gh-devel
Size:40.09 KiB

Package: netplan-0.104-1.fc37
Summary: Network configuration tool using YAML
RPMs:netplan netplan-default-backend-NetworkManager 
netplan-default-backend-networkd netplan-devel netplan-libs
Size:2.02 MiB

Package: python-google-cloud-pubsub-2.13.0-1.fc37
Summary: Google Cloud Pub/Sub API client library
RPMs:python3-google-cloud-pubsub python3-google-cloud-pubsub+libcst
Size:231.97 KiB

Package: python-sklearn-genetic-opt-0.9.0-1.fc37
Summary: Hyperparameters tuning and feature selection
RPMs:python-sklearn-genetic-opt-doc python3-sklearn-genetic-opt
Size:1.39 MiB


= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  annobin-10.76-1.fc37
Old package:  annobin-10.75-1.fc37
Summary:  Annotate and examine compiled binary files
RPMs: annobin-annocheck annobin-docs annobin-plugin-clang 
annobin-plugin-gcc annobin-plugin-llvm
Size: 4.31 MiB
Size change:  -407.93 KiB

Package:  antimicrox-3.2.4-1.fc37
Old package:  antimicrox-3.2.3-1.fc37
Summary:  Graphical program used to map keyboard buttons and mouse controls 
to a gamepad
RPMs: antimicrox
Size: 3.70 MiB
Size change:  -30.07 KiB
Changelog:
  * Tue Jun 14 2022 Gergely Gombos  - 3.2.4-1
  - 3.2.4


Package:  boost-1.78.0-2.fc37
Old package:  boost-1.78.0-0.fc37
Summary:  The free peer-reviewed portable C++ source libraries
RPMs: boost boost-atomic boost-b2 boost-build boost-chrono 
boost-container boost-context boost-contract boost-coroutine boost-date-time 
boost-devel boost-doc boost-doctools boost-examples boost-fiber 
boost-filesystem boost-graph boost-graph-mpich boost-graph-openmpi 
boost-iostreams boost-json boost-locale boost-log boost-math boost-mpich 
boost-mpich-devel boost-mpich-python3 boost-mpich-python3-devel boost-nowide 
boost-numpy3 boost-openmpi boost-openmpi-devel boost-openmpi-python3 
boost-openmpi-python3-devel boost-program-options boost-python3 boost-random 
boost-regex boost-serialization boost-stacktrace boost-static boost-system 
boost-test boost-thread boost-timer boost-type_erasure boost-wave
Size: 286.53 MiB
Size change:  158.51 KiB
Changelog:
  * Mon Jun 13 2022 Python Maint  - 1.78.0-1
  - Rebuilt for Python 3.11

  * Tue Jun 14 2022 Laurent Rineau  - 1.78.0-2
  - Re-add the CMake config file provided by Boost


Package:  brltty-6.5-1.fc37
Old package:  brltty-6.4-6.fc36
Summary:  Braille display driver for Linux/Unix
RPMs: brlapi brlapi-devel brlapi-java brltty brltty-at-spi2 brltty-docs 
brltty-dracut brltty-espeak brltty-espeak-ng brltty-minimal 
brltty-speech-dispatcher brltty-xw ocaml-brlapi python3-brlapi tcl-brlapi
Size: 15.89 MiB
Size change:  470.73 KiB
Changelog:
  * Mon Jun 13 2022 Python Maint  - 6.4-7
  - Rebuilt for Python 3.11

  * Tue Jun 14 2022 Jaroslav ??karvada  - 6.5-1
  - New version
Resolves: rhbz#2095460


Package:  checkpolicy-3.4-2.fc37
Old package:  checkpolicy-3.4-0.rc3.1.fc37
Summary:  SELinux policy compiler
RPMs: checkpolicy
Size: 1.36 MiB
Size change:  2.91 KiB
Changelog:
  * Thu May 19 2022 Petr Lautrbach  - 3.4-1
  - SELinux userspace 3.4 release

  * Wed May 25 2022 Petr Lautrbach  - 3.4-2
  - rebuilt


Package:  dnsdist-1.7.2-1.fc37
Old package:  dnsdist-1.7.1-2.fc37
Summary:  Highly DNS-, DoS- and abuse-aware loadbalancer
RPMs: dnsdist
Size: 7.52 MiB
Size change:  33.63 KiB
Changelog:
  * Mon Jun 13 2022 Fedora Release Monitoring 
 - 1.7.2-1
  - Update to 1.7.2 (#2096239)


Package:  dummy-test-package-gloster-0-9121.fc37
Old package:  dummy-test-package-gloster-0-9104.fc37
Summary:  Dummy Test Package called Gloster
RPMs: dummy-test-package-gloster
Size: 510.36 KiB
Size change:  728 B
Changelog:
  * Tue Jun 14 2022 packagerbot  - 0-9105
  - rebuilt

  * Tue Jun 14 2022 packagerbot  - 0-9106
  - rebuilt

  * Tue Jun 14 2022 packagerbot  - 0-9107
  - rebuilt

  * Tue Jun 14 2022 packagerbot  - 0-9108
  - rebuilt

  * Tue Jun 14 2022 packagerbot  - 0-9109
  - rebuilt

  * Tue Jun 14 2022 packagerbot  - 0-9110
  - rebuilt

  * Tue Jun

Fedora-Cloud-36-20220615.0 compose check report

[Fedora compose checker]

No missing expected images.

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

Old soft failures (same test soft failed in Fedora-Cloud-36-20220614.0):

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

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

Rename Airspy

[Buford T. Justice]

For the regular Airspy (not HF+), why is the package called "airspyone_host"?  
All other distros just call it "airspy":

https://pkgs.org/search/?q=airspy

So it would be nice to simply do:

sudo dnf install airspy airspyhf

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