Re: F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)

[Naheem Zaffar]

On Tue, 8 Nov 2022, 19:22 Vitaly Zaitsev via devel, <
devel@lists.fedoraproject.org> wrote:

> On 08/11/2022 19:53, Naheem Zaffar wrote:
> > Has there been any consideration to turn on frame pointers for atleast
> > dev releases?
>
>
> Fedora has no dev releases. Mass rebuild is a huge pain for maintainers
> due to FTBFS issues, and doing it multiple times is unacceptable.
>
I think I explained the idea poorly.

Not all builds in rawhide are release builds. You will get for instance the
whole gnome stack beta releases and rc releases during development.

This isnt limited to gnome, most software will go into rawhide first to
stabilise.

It is almost never intended for these builds to end up in the final
release  ll, but they are useful and necessary parts of the development
cycle. Theywill be replaced before general availability, all without a mass
rebuild.

It's not a silver bullet solution but atleast it starts things off on a
path where profiling can be done in a limited manner compared to the other
proposed alternatives where the tooling doesnt exist and will likely not
ever be written.

>
>
___
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: CVE Tracking Bugs

[Ian McInerney via devel]

On Wed, Sep 7, 2022 at 7:45 PM Ben Cotton  wrote:

> On Wed, Sep 7, 2022 at 2:05 PM Maxwell G via devel
>  wrote:
> >
> > Does anyone know how to reach prodsec about this?
>
> I'll reach out to the people I know and see what the best way to get
> them in this conversation is.
>
>
Has this conversation been started yet? Because the CVE reporting system
doesn't seem to have been improved at all - in fact a recent CVE bug (
https://bugzilla.redhat.com/show_bug.cgi?id=2141029) was filed, had over
179 people added to the CC list, and there is no mention at all of which
applications were identified as being affected or any other tracking bugs
filed for those affected applications. So as a maintainer, I am then unsure
why I was CC'd on the bug and which application prod sec wants me to
examine for the vulnerability (especially since to my knowledge, none of
the packages I maintain even use electron in any way or have its code
contained inside of them).

-Ian


> --
> Ben Cotton
> He / Him / His
> Fedora Program Manager
> Red Hat
> TZ=America/Indiana/Indianapolis
> ___
> 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: F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)

[Demi Marie Obenour]

On 11/8/22 18:46, Frank Ch. Eigler wrote:
> Demi Marie Obenour  writes:
> 
>> Three other options I can think of:
>> [...]
> 
> Another one:
> 
>   4. Speed up out-of-context backtracer(s), possibly consuming
>  kernel-perf-ringbuffer stack dumps, or possibly using another
>  event source to trigger and work via ptrace and /proc/$pid/mem
> 
> - FChE

Kernel stack dumps will not work for programs (such as OCaml 5.0)
that use segmented stacks.  A userspace ptracer might work if it
is only woken up when absolutely necessary, but I suspect it would
be slow due to syscall overhead.  That is why I suggested the vDSO
dumper: it would run from the process’s own context.
-- 
Sincerely,
Demi Marie Obenour (she/her/hers)
___
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 37 compose report: 20221108.n.0 changes

[Adam Williamson]

On Wed, 2022-11-09 at 07:47 +1100, Ian Laurie wrote:
> On 11/9/22 01:18, Fedora Rawhide Report wrote:
> > OLD: Fedora-37-20221107.n.0
> > NEW: Fedora-37-20221108.n.0
> [big snip]
> 
> This seems to have all the gnome fixes, plus a load of KDE fixes, and 
> the 6.0.7 kernel shouldn't this be a release candidate?

Nightlies and candidate composes are separate streams. A nightly is
built (or attempted, at least) every day, with whatever is "in stable"
(i.e. tagged 'f37'), regardless. Candidate composes are triggered by
hand in response to compose requests which QA (usually me) file:

https://pagure.io/releng/issue/11094

candidate composes contain everything "in stable", plus any specific
blocker/FE fixes listed in the compose request. Their configuration
differs slightly - they are a different compose "type" so far as Pungi
is concerned, which has several consequences; they have a label (which
means the artifacts have different filenames from those in a nightly
compose), and some metadata is set differently, which (for instance)
means the label identifying the image as PRE-RELEASE/TEST does not
appear in anaconda. For these reasons, a nightly compose can *never* be
the thing we actually release.

The RC-1.7 compose already had all the things that were "new" in the
20221108.n.0 compose. During the freeze, we would never push packages
that weren't in the last candidate to stable unless we were sure we
would need to build another candidate. Right now RC-1.7 looks
"releasable", so we will not push anything stable that wasn't in it.
-- 
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)

[Frank Ch. Eigler]

Demi Marie Obenour  writes:

> Three other options I can think of:
> [...]

Another one:

  4. Speed up out-of-context backtracer(s), possibly consuming
 kernel-perf-ringbuffer stack dumps, or possibly using another
 event source to trigger and work via ptrace and /proc/$pid/mem

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

Re: F38 proposal: MobilityPhoshImage (Self-Contained Change proposal)

[Kevin Fenzi]

On Tue, Nov 08, 2022 at 03:09:46PM -0500, Ben Cotton wrote:
> On Tue, Nov 8, 2022 at 1:34 PM Kevin Fenzi  wrote:
> >
> > Yeah, was going to try and work it out with them (which I have not yet
> > done). Where's the best place to engage with them these days?
> 
> I'd start with either Discussion[1] or chat[2]. There are a couple of
> Pagure repos as well, but the new work is being done in GitLab, so
> depending on where the content ends up, the repo may change.
> 
> [1] https://discussion.fedoraproject.org/c/project/websites/66
> [2] https://chat.fedoraproject.org/#/room/#websites:fedoraproject.org

https://discussion.fedoraproject.org/t/fitting-the-new-f38-mobile-phosh-spin-lab-in-websites/43887

Everyone welcome to follow along/chime in there. 

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: Help understanding Fedora CI failure wrt RPM Sequoia

[Miro Hrončok]

On 08. 11. 22 20:45, Adam Williamson wrote:

On Tue, 2022-11-08 at 08:11 -0800, Adam Williamson wrote:

On Tue, 2022-11-08 at 13:32 +0200, Panu Matilainen wrote:


But I don't know the slightest thing about ansible, beyond a very rough
idea of what kind of tool it is. Just understanding what exactly it's
trying to do here would go a long way, I think. But either it's not in
the logs, or I don't know how to read them.


well, to expand on my previous answer, it gets a bit interesting. At
this point in the process the CI system has installed the packages to
be tested and verified that they're installed, which implies RPM does
at least basically work or else that would have failed. you can see
this in these logs:

https://artifacts.dev.testing-farm.io/700d486d-d409-44fe-b7c3-01634243558e/guest-setup-554c73be-c472-4007-9f14-23eea462c69d/artifact-installation-554c73be-c472-4007-9f14-23eea462c69d/

then it hands off to ansible to actually 'run the tests', and that's
when the error happens. I believe it happens here in ansible's code:

https://github.com/ansible/ansible/blob/devel/lib/ansible/modules/dnf.py#L1366

so that may help you figure it out. I'd look further but I have to run
out right now...


well, I'm back now. Looking into it a bit further, I think the codepath
we're on compresses to this, where `self.base` is a DNF base object:

self.base.upgrade_all()
try:
 self.base.resolve(allow_erasing=self.allowerasing)
 [cut internal stuff that couldn't raise a DNF error]
 for package in self.base.transaction.install_set:
 fail = False
 gpgres, gpgerr = self.base._sig_check_pkg(package)
 [cut more stuff that couldn't raise the error]
 self.base.do_transaction()
except dnf.exceptions.Error as e:
 failure_response['msg'] = "Unknown Error occurred: 
{0}".format(to_native(e))
 self.module.fail_json(**failure_response)

I'm pretty sure that's the path we're on, and "An rpm exception
occurred: package not installed" is the text of a dnf.exceptions.Error
exception that's raised by one of those actions that actually involves
the DNF base object (I cut stuff that doesn't involve it, and one
branch where we'd do something different if we hit a
dnf.exceptions.Error). Next step would be to see why dnf is throwing
that error, I guess. It'd be nice if it said *what* package it thinks
is "not installed"...


See also https://src.fedoraproject.org/rpms/rpm/pull-request/29

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

Re: Help understanding Fedora CI failure wrt RPM Sequoia

[Maxwell G via devel]

On Tue Nov 8, 2022 at 12:13 +0200, Panu Matilainen wrote:
> Hey,
>
> Thought I'd try to get on with the times and do the Sequoia change via a
> PR instead of just pushing as we've traditionally done. So far so good,
> but it throws up an error which I have no idea how to debug:
>
> https://artifacts.dev.testing-farm.io/700d486d-d409-44fe-b7c3-01634243558e/
>
>  > Unknown Error occured: An rpm exception occurred: package not installed
>
> Okay, something failed, and it appears to be related to this very change
> as the tests pass with a "no-op" PR. And in that case, a good thing it
> got caught. But how on earth to debug this? I don't see anything even
> remotely relevant in the accompanying logs, nor did I find any obvious
> way to run this stuff locally.
>
> Help, Obi-Wan KenoCI.
>
>   - Panu -

I did some debugging in [1]. See my comment in that PR for more
information.

[1]: https://src.fedoraproject.org/rpms/rpm/pull-request/29

--
Best,

Maxwell G (@gotmax23)
Pronouns: He/Him/His


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: Fedora 37 compose report: 20221108.n.0 changes

[Ian Laurie]

On 11/9/22 01:18, Fedora Rawhide Report wrote:

OLD: Fedora-37-20221107.n.0
NEW: Fedora-37-20221108.n.0

[big snip]

This seems to have all the gnome fixes, plus a load of KDE fixes, and 
the 6.0.7 kernel shouldn't this be a release candidate?


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

Non-responsive maintainer check for guidograzioli

[Richard Shaw]

Looking here, I don't see any activity in the last year:

https://src.fedoraproject.org/user/guidograzioli

I have not gotten any response to BZs for yaml-cpp.

Does anyone know how to contact them?

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

Re: F38 proposal: MobilityPhoshImage (Self-Contained Change proposal)

[Ben Cotton]

On Tue, Nov 8, 2022 at 1:34 PM Kevin Fenzi  wrote:
>
> Yeah, was going to try and work it out with them (which I have not yet
> done). Where's the best place to engage with them these days?

I'd start with either Discussion[1] or chat[2]. There are a couple of
Pagure repos as well, but the new work is being done in GitLab, so
depending on where the content ends up, the repo may change.

[1] https://discussion.fedoraproject.org/c/project/websites/66
[2] https://chat.fedoraproject.org/#/room/#websites:fedoraproject.org

-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
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: Help understanding Fedora CI failure wrt RPM Sequoia

[Adam Williamson]

On Tue, 2022-11-08 at 08:11 -0800, Adam Williamson wrote:
> On Tue, 2022-11-08 at 13:32 +0200, Panu Matilainen wrote:
> > 
> > But I don't know the slightest thing about ansible, beyond a very rough 
> > idea of what kind of tool it is. Just understanding what exactly it's 
> > trying to do here would go a long way, I think. But either it's not in 
> > the logs, or I don't know how to read them.
> 
> well, to expand on my previous answer, it gets a bit interesting. At
> this point in the process the CI system has installed the packages to
> be tested and verified that they're installed, which implies RPM does
> at least basically work or else that would have failed. you can see
> this in these logs:
> 
> https://artifacts.dev.testing-farm.io/700d486d-d409-44fe-b7c3-01634243558e/guest-setup-554c73be-c472-4007-9f14-23eea462c69d/artifact-installation-554c73be-c472-4007-9f14-23eea462c69d/
> 
> then it hands off to ansible to actually 'run the tests', and that's
> when the error happens. I believe it happens here in ansible's code:
> 
> https://github.com/ansible/ansible/blob/devel/lib/ansible/modules/dnf.py#L1366
> 
> so that may help you figure it out. I'd look further but I have to run
> out right now...

well, I'm back now. Looking into it a bit further, I think the codepath
we're on compresses to this, where `self.base` is a DNF base object:

self.base.upgrade_all()
try:
self.base.resolve(allow_erasing=self.allowerasing)
[cut internal stuff that couldn't raise a DNF error]
for package in self.base.transaction.install_set:
fail = False
gpgres, gpgerr = self.base._sig_check_pkg(package)
[cut more stuff that couldn't raise the error]
self.base.do_transaction()
except dnf.exceptions.Error as e:
failure_response['msg'] = "Unknown Error occurred: {0}".format(to_native(e))
self.module.fail_json(**failure_response)

I'm pretty sure that's the path we're on, and "An rpm exception
occurred: package not installed" is the text of a dnf.exceptions.Error
exception that's raised by one of those actions that actually involves
the DNF base object (I cut stuff that doesn't involve it, and one
branch where we'd do something different if we hit a
dnf.exceptions.Error). Next step would be to see why dnf is throwing
that error, I guess. It'd be nice if it said *what* package it thinks
is "not installed"...
-- 
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)

[Vitaly Zaitsev via devel]

On 08/11/2022 19:53, Naheem Zaffar wrote:
Has there been any consideration to turn on frame pointers for atleast 
dev releases?



Fedora has no dev releases. Mass rebuild is a huge pain for maintainers 
due to FTBFS issues, and doing it multiple times is unacceptable.


If someone needs extended profiling, they can do mass rebuilds on their 
side as many times as they need.


--
Sincerely,
  Vitaly Zaitsev (vit...@easycoding.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: F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)

[Daniel P . Berrangé]

On Tue, Nov 08, 2022 at 06:53:46PM +, Naheem Zaffar wrote:
> Has there been any consideration to turn on frame pointers for atleast dev
> releases?
> 
> AFAIK the kernel already has a separate configuration during the
> development phase of the distro-cycle

This practice already causes problems for people trying to use rawhide
because the debug config options massively slowdown the rawhide kernel
resulting in timeouts for various test/build processes:

  
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/HRJT4UF35MRJ7C4ZXVHBFXB4BTW64YSO/#ZPU2TZ72D5SP7I4AVTBV2NXXBEBQ7HD6

> Can this be extended for rebuilds of alpha and beta releases in rawhide to
> turn on frame pointers as an interim solution until everything else is
> figured out?

IMHO if something isn't good enough for release, we shouldn't put
it in rawhide either, as it undermines the usability of rawhide.

With regards,
Daniel
-- 
|: https://berrange.com  -o-https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o-https://fstop138.berrange.com :|
|: https://entangle-photo.org-o-https://www.instagram.com/dberrange :|
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)

[Naheem Zaffar]

Has there been any consideration to turn on frame pointers for atleast dev
releases?

AFAIK the kernel already has a separate configuration during the
development phase of the distro-cycle

Can this be extended for rebuilds of alpha and beta releases in rawhide to
turn on frame pointers as an interim solution until everything else is
figured out?
___
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: F38 proposal: MobilityPhoshImage (Self-Contained Change proposal)

[Kevin Fenzi]

On Tue, Nov 08, 2022 at 10:21:43AM -0500, Ben Cotton wrote:
> On Tue, Nov 8, 2022 at 10:10 AM Ben Cotton  wrote:
> >
> > Initial images are produced for x86_64 and aarch64 mobile devices
> > using the Phosh desktop.
> 
> Is the plan to add these images to an existing website or a new one?

The new one I would think?

> Or are you going to work that out with the Websites & Apps team? (Note
> that they're targeting F38 for the launch of a reconfigured getfedora,
> so it's good to engage with them early on this.)

Yeah, was going to try and work it out with them (which I have not yet
done). Where's the best place to engage with them these days?

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

Summary/Minutes from today's FESCo Meeting (2022-11-08)

[Zbigniew Jędrzejewski-Szmek]

Meeting was cancelled due to lack of quorum. I'll chair the next meeting.

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting/2022-11-08/fesco.2022-11-08-17.00.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting/2022-11-08/fesco.2022-11-08-17.00.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting/2022-11-08/fesco.2022-11-08-17.00.log.html

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: Help understanding Fedora CI failure wrt RPM Sequoia

[Adam Williamson]

On Tue, 2022-11-08 at 13:32 +0200, Panu Matilainen wrote:
> 
> But I don't know the slightest thing about ansible, beyond a very rough 
> idea of what kind of tool it is. Just understanding what exactly it's 
> trying to do here would go a long way, I think. But either it's not in 
> the logs, or I don't know how to read them.

well, to expand on my previous answer, it gets a bit interesting. At
this point in the process the CI system has installed the packages to
be tested and verified that they're installed, which implies RPM does
at least basically work or else that would have failed. you can see
this in these logs:

https://artifacts.dev.testing-farm.io/700d486d-d409-44fe-b7c3-01634243558e/guest-setup-554c73be-c472-4007-9f14-23eea462c69d/artifact-installation-554c73be-c472-4007-9f14-23eea462c69d/

then it hands off to ansible to actually 'run the tests', and that's
when the error happens. I believe it happens here in ansible's code:

https://github.com/ansible/ansible/blob/devel/lib/ansible/modules/dnf.py#L1366

so that may help you figure it out. I'd look further but I have to run
out right now...
-- 
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Help understanding Fedora CI failure wrt RPM Sequoia

[Adam Williamson]

On Tue, 2022-11-08 at 13:32 +0200, Panu Matilainen wrote:
> On 11/8/22 13:05, Miro Hrončok wrote:
> > On 08. 11. 22 11:13, Panu Matilainen wrote:
> > > Hey,
> > > 
> > > Thought I'd try to get on with the times and do the Sequoia change via 
> > > a PR instead of just pushing as we've traditionally done. So far so 
> > > good, but it throws up an error which I have no idea how to debug:
> > > 
> > > https://artifacts.dev.testing-farm.io/700d486d-d409-44fe-b7c3-01634243558e/
> > > 
> > >  > Unknown Error occured: An rpm exception occurred: package not 
> > > installed
> > > 
> > > Okay, something failed, and it appears to be related to this very 
> > > change as the tests pass with a "no-op" PR. And in that case, a good 
> > > thing it got caught. But how on earth to debug this? I don't see 
> > > anything even remotely relevant in the accompanying logs, nor did I 
> > > find any obvious way to run this stuff locally.
> > > 
> > > Help, Obi-Wan KenoCI.
> > 
> > I am far from being a jeCI master,
> > 
> > but considering the tests there were added by me, for 
> > pyproject-rpm-macros, I decided to have a look.
> > 
> > The STI tests are at 
> > https://src.fedoraproject.org/rpms/rpm/blob/rawhide/f/tests/tests.yml
> > 
> > They more or less start with:
> > 
> >    tasks:
> >      - dnf:
> >      name: "*"
> >      state: latest
> > 
> > And the logs you link to say:
> > 
> >    TASK [dnf] 
> > *
> >    fatal: [sut]: FAILED! => {
> >    "changed": false,
> >    "failures": [],
> >    "rc": 1,
> >    "results": []
> >    }
> > 
> >    MSG:
> > 
> >    Unknown Error occured: An rpm exception occurred: package not installed
> > 
> > This means the problem you hit is that ansible is unable to run the DNF 
> > task.
> 
> Yep, that much I understood: something dnf related is failing. And that 
> something looks like a situation where dnf thinks a package should be 
> installed but isn't.
> 
> Now, such a scenario could occur in this very context if there are 
> packages with SHA1 signatures involved: a previously installed package 
> would seem uninstalled as the header just became unaccessible due to the 
> bad signature. Or other similar scenarios revolving around this. But 
> what package is that?
> 
> > I know how to reproduce the actual tests locally without ansible, but 
> > that would avoid this problem. I suggest not trying to reproduce the 
> > tests, but reproducing the ansible failure in isolation. My ansible 
> > skills are limited, I knwo how to edit the YAML, but I have no idea how 
> > to actually try this out.
> > 
> 
> Okay, a good point - this quite obviously is *not* related to the python 
> %generate_requires tests, so trying to reproduce that in itself is not 
> useful.
> 
> But I don't know the slightest thing about ansible, beyond a very rough 
> idea of what kind of tool it is. Just understanding what exactly it's 
> trying to do here would go a long way, I think. But either it's not in 
> the logs, or I don't know how to read them.
> 
> Thanks for trying to help.

All that task means is "ensure all packages are updated". It basically
means ansible will run 'dnf -y update' and expect it to succeed.

There should be logs *somewhere* showing what happened when it did
that.
-- 
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: F38 proposal: MobilityPhoshImage (Self-Contained Change proposal)

[Ben Cotton]

On Tue, Nov 8, 2022 at 10:10 AM Ben Cotton  wrote:
>
> Initial images are produced for x86_64 and aarch64 mobile devices
> using the Phosh desktop.

Is the plan to add these images to an existing website or a new one?
Or are you going to work that out with the Websites & Apps team? (Note
that they're targeting F38 for the launch of a reconfigured getfedora,
so it's good to engage with them early on this.)

-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
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

F38 proposal: MobilityPhoshImage (Self-Contained Change proposal)

[Ben Cotton]

https://fedoraproject.org/wiki/Changes/MobilityPhoshImage

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


== Summary ==
Phosh is a wayland shell for mobile devices based on Gnome. The
mobility SIG has packaged up Phosh and related packages into a
'phosh-desktop' package group and would like to start making x86_64
and aarch64 images for mobile devices.


== Owner ==
* Name: [[User:Kevin| Kevin Fenzi]], [[User:Torbuntu| Torrey Sorensen]]


== Detailed Description ==
There's a number of x86_64 and aarch64 tablets and other mobile
devices that could use a more mobile centric interface/desktop than
traditional Fedora desktops/labs/spins. Having Fedora images for these
devices will make it easier to install and use them. Having a image
will also help remix efforts, allowing them to reuse userspace
packages and metadata (kickstarts, etc) with a modified kernel.

Note: Plasma Mobile is also being packaged and will be requested in
another change

Note: Pinephone and Pinephone Pro are eventual targets for these
images, but more kernel patches must be upstreamed before these
devices will boot and function.


== Benefit to Fedora ==
These images will spread Fedora to mobile devices and bring more users
into the Fedora community as well as showcasing upstream work to
provide a 100% open source phone interface for devices once they are
workable from vanilla kernels.


== Scope ==
* Proposal owners: Create kickstarts and other configuration needed to
produce aarch64 and x86_64 images. Fix bugs related to phosh-desktop
group and associated packages.

* Other developers: Help test images and groups

* Release engineering: Review kickstarts and pungi configutation,
produce images.

* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives:


== Upgrade/compatibility impact ==


== How To Test ==
Install the produced image to a suitable x86_64 or aarch64 device with
arm-image-installer or dd
Boot the image and confirm it comes up to a phosh desktop
Use various desktop functions and report issues.


== User Experience ==


== Dependencies ==


== Contingency Plan ==
* Contingency mechanism: (What to do?  Who will do it?) N/A (not a
System Wide Change)
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? N/A (not a System Wide Change), Yes/No


== Documentation ==
N/A (not a System Wide Change)

== Release Notes ==
Initial images are produced for x86_64 and aarch64 mobile devices
using the Phosh desktop.


-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
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

NeuroFedora review swap: python-formulaic

[Ankur Sinha]

Hi folks,

Would someone like to swap reviews please? I'd like to get
python-formulaic reviewed and included in Fedora[1]. It's required to
update python-pybids to the latest version[2]

It should be a straightforward review. Unofficial reviews from candidate
package maintainers looking for review practice are also most welcome.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=2140295
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1996270

-- 
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) | 
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London


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

Schedule for Tuesday's FESCo Meeting (2022-11-08)

[Zbigniew Jędrzejewski-Szmek]

Following is the list of topics that will be discussed in the
FESCo meeting Tuesday at 17:00UTC in #fedora-meeting on
irc.libera.chat.

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

or run:
  date -d '2022-11-08 17:00 UTC'


Links to all issues to be discussed can be found at: 
https://pagure.io/fesco/report/meeting_agenda


= Discussed and Voted in the Ticket =

#2885 Change: Modernize Live Media
https://pagure.io/fesco/issue/2885
APPROVED (+5,0,-0)

#2886 Updates Policy exception: Ansible 7 in Fedora 37
https://pagure.io/fesco/issue/2886
APPROVED (+7, 0, 0)


= Followups =

#2883 Change: Ostree Native Container (Phase 2, stable)
https://pagure.io/fesco/issue/2883

#2887 move IMA RPM file-signature change to F38?
https://pagure.io/fesco/issue/2887

#2817 Change proposal: Add -fno-omit-frame-pointer to default compilation flags
https://pagure.io/fesco/issue/2817


= New business =


= Open Floor = 

For more complete details, please visit each individual
issue.  The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda

If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, e-mail me directly, or bring it
up at the end of the meeting, during the open floor topic. Note
that added topics may be deferred until the following meeting. 
___
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 37 compose report: 20221108.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-37-20221107.n.0
NEW: Fedora-37-20221108.n.0

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

Size of added packages:  656.34 KiB
Size of dropped packages:0 B
Size of upgraded packages:   3.04 GiB
Size of downgraded packages: 0 B

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

= ADDED IMAGES =
Image: Container_Base docker aarch64
Path: 
Container/aarch64/images/Fedora-Container-Base-37-20221108.n.0.aarch64.tar.xz

= DROPPED IMAGES =

= ADDED PACKAGES =
Package: kpipewire-5.26.2-1.fc37
Summary: Set of convenient classes to use PipeWire in Qt projects
RPMs:kpipewire kpipewire-devel
Size:656.34 KiB


= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  analitza-22.08.2-1.fc37
Old package:  analitza-22.08.1-1.fc37
Summary:  Library of mathematical features
RPMs: analitza analitza-devel
Size: 2.95 MiB
Size change:  -1.29 KiB
Changelog:
  * Fri Oct 14 2022 Marc Deop  - 22.08.2-1
  - 22.08.2


Package:  artikulate-22.08.2-1.fc37
Old package:  artikulate-22.08.1-1.fc37
Summary:  Improve your pronunciation by listening to native speakers
RPMs: artikulate artikulate-libs
Size: 5.25 MiB
Size change:  -38 B
Changelog:
  * Fri Oct 14 2022 Marc Deop  - 22.08.2-1
  - 22.08.2


Package:  baloo-widgets-22.08.2-1.fc37
Old package:  baloo-widgets-22.08.1-1.fc37
Summary:  Widgets for Baloo
RPMs: baloo-widgets baloo-widgets-devel
Size: 913.82 KiB
Size change:  -170 B
Changelog:
  * Fri Oct 14 2022 Marc Deop  - 22.08.2-1
  - 22.08.2


Package:  blinken-22.08.2-1.fc37
Old package:  blinken-22.08.1-1.fc37
Summary:  Memory Enhancement Game
RPMs: blinken
Size: 9.28 MiB
Size change:  446 B
Changelog:
  * Fri Oct 14 2022 Marc Deop  - 22.08.2-1
  - 22.08.2


Package:  bluedevil-5.26.2-1.fc37
Old package:  bluedevil-5.25.5-1.fc37
Summary:  Bluetooth stack for KDE
RPMs: bluedevil
Size: 2.71 MiB
Size change:  827.80 KiB
Changelog:
  * Sat Sep 17 2022 Marc Deop  - 5.25.90-1
  - 5.25.90

  * Thu Oct 06 2022 Marc Deop  - 5.26.0-1
  - 5.26.0

  * Tue Oct 18 2022 Marc Deop  - 5.26.1-1
  - 5.26.1

  * Wed Oct 26 2022 Marc Deop  - 5.26.2-1
  - 5.26.2


Package:  bovo-22.08.2-1.fc37
Old package:  bovo-22.08.1-1.fc37
Summary:  Five in a row game
RPMs: bovo
Size: 1.35 MiB
Size change:  100 B
Changelog:
  * Fri Oct 14 2022 Marc Deop  - 22.08.2-1
  - 22.08.2


Package:  breeze-gtk-5.26.2-1.fc37
Old package:  breeze-gtk-5.25.5-1.fc37
Summary:  Breeze widget theme for GTK
RPMs: breeze-gtk breeze-gtk-common breeze-gtk-gtk2 breeze-gtk-gtk3 
breeze-gtk-gtk4
Size: 407.72 KiB
Size change:  -5.24 KiB
Changelog:
  * Sat Sep 17 2022 Marc Deop  - 5.25.90-1
  - 5.25.90

  * Thu Oct 06 2022 Marc Deop  - 5.26.0-1
  - 5.26.0

  * Tue Oct 18 2022 Marc Deop  - 5.26.1-1
  - 5.26.1

  * Wed Oct 26 2022 Marc Deop  - 5.26.2-1
  - 5.26.2


Package:  breeze-icon-theme-5.99.0-1.fc37
Old package:  breeze-icon-theme-5.98.0-1.fc37
Summary:  Breeze icon theme
RPMs: breeze-icon-theme breeze-icon-theme-rcc
Size: 11.40 MiB
Size change:  -44.05 KiB
Changelog:
  * Fri Oct 14 2022 Marc Deop  - 5.99.0-1
  - 5.99.0


Package:  cantor-22.08.2-1.fc37
Old package:  cantor-22.08.1-1.fc37
Summary:  KDE Frontend to Mathematical Software
RPMs: cantor cantor-R cantor-devel cantor-julia cantor-libs
Size: 6.47 MiB
Size change:  -9.51 KiB
Changelog:
  * Fri Oct 14 2022 Marc Deop  - 22.08.2-1
  - 22.08.2


Package:  cervisia-22.08.2-1.fc37
Old package:  cervisia-22.08.1-1.fc37
Summary:  CVS frontend
RPMs: cervisia
Size: 10.06 MiB
Size change:  2.18 KiB
Changelog:
  * Fri Oct 14 2022 Marc Deop  - 22.08.2-1
  - 22.08.2


Package:  dolphin-22.08.2-1.fc37
Old package:  dolphin-22.08.1-1.fc37
Summary:  KDE File Manager
RPMs: dolphin dolphin-devel dolphin-libs
Size: 17.81 MiB
Size change:  -749 B
Changelog:
  * Fri Oct 14 2022 Marc Deop  - 22.08.2-1
  - 22.08.2


Package:  dolphin-plugins-22.08.2-1.fc37
Old package:  dolphin-plugins-22.08.1-1.fc37
Summary:  Dolphin plugins for revision control systems
RPMs: dolphin-plugins
Size: 2.40 MiB
Size change:  15.49 KiB
Changelog:
  * Fri Oct 14 2022 Marc Deop  - 22.08.2-1
  - 22.08.2


Package:  dragon-22.08.2-1.fc37
Old package:  dragon-22.08.1-1.fc37
Summary:  Media player
RPMs: dragon
Size: 8.88 MiB
Size change:  269 B
Changelog:
  * Fri Oct 14 2022 Marc Deop  - 22.08.2-1
  - 22.08.2


Package:  elisa-player-22.08.2-1.fc37
Old package:  elisa-player-22.08.1-1.fc37
Summary:  Elisa music player
RPMs: elisa-player
Size: 9.73 MiB
Size change:  -5.44 KiB
Changelog:
  * Sat Oct 15 2022 Marc Deop i Argem??  22.08.2-1

Re: SPDX Change update

[David Cantrell]

On Tue, Nov 08, 2022 at 09:45:57AM +, Richard W.M. Jones wrote:
> Should new package reviews (for Rawhide) now be rejected if they don't
> have SPDX tags?

Yes, new packages going forward should use SPDX expressions in the License
tag.

-- 
David Cantrell 
Red Hat, Inc. | Boston, MA | EST5EDT
___
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: python-pgspecial 2.0.1 coming to Rawhide

[Ben Beasley]

In one week (2022-11-15), or slightly later, I will update python-pgspecial 
from 1.13.1 to 2.0.1[1] in Rawhide. The new version switches from psycopg2 to 
psycopg3, which is a breaking change. The sole dependent package is pgcli. I 
have coordinated with its maintainer and will update it to 3.5.0[2] at the same 
time using a side tag.

– Ben Beasley (FAS music)

[1] https://src.fedoraproject.org/rpms/python-pgspecial/pull-request/1
[2] https://src.fedoraproject.org/rpms/pgcli/pull-request/4

___
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: 20221108.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20221107.n.0
NEW: Fedora-Rawhide-20221108.n.0

= SUMMARY =
Added images:1
Dropped images:  2
Added packages:  8
Dropped packages:2
Upgraded packages:   121
Downgraded packages: 0

Size of added packages:  1.30 MiB
Size of dropped packages:1.06 MiB
Size of upgraded packages:   3.97 GiB
Size of downgraded packages: 0 B

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

= ADDED IMAGES =
Image: Container_Minimal_Base docker s390x
Path: 
Container/s390x/images/Fedora-Container-Minimal-Base-Rawhide-20221108.n.0.s390x.tar.xz

= DROPPED IMAGES =
Image: Cloud_Base qcow2 ppc64le
Path: Cloud/ppc64le/images/Fedora-Cloud-Base-Rawhide-20221107.n.0.ppc64le.qcow2
Image: Cloud_Base raw-xz ppc64le
Path: Cloud/ppc64le/images/Fedora-Cloud-Base-Rawhide-20221107.n.0.ppc64le.raw.xz

= ADDED PACKAGES =
Package: golang-github-charmbracelet-bubbles-0.14.0-1.fc38
Summary: TUI components for Bubble Tea
RPMs:golang-github-charmbracelet-bubbles-devel
Size:60.76 KiB

Package: golang-github-geoffgarside-ber-1.1.0-1.fc38
Summary: Fork of golang pkg `encoding/asn1` to support the Basic Encoding Rules
RPMs:golang-github-geoffgarside-ber-devel
Size:29.09 KiB

Package: golang-github-hirochachacha-smb2-1.1.0-1.fc38
Summary: SMB2/3 client library written in Go
RPMs:golang-github-hirochachacha-smb2-devel
Size:144.64 KiB

Package: golang-github-hokaccha-prettyjson-0-0.1.20220921git0474bc6.fc38
Summary: JSON pretty print for Golang
RPMs:golang-github-hokaccha-prettyjson-devel
Size:13.86 KiB

Package: nagios-plugins-systemd-2.3.1-6.fc38
Summary: Nagios Plugin - check_systemd
RPMs:nagios-plugins-systemd
Size:139.50 KiB

Package: perl-Tickit-0.73-1.fc38
Summary: Perl bindings for Tickit
RPMs:perl-Tickit perl-Tickit-tests
Size:869.66 KiB

Package: python-colcon-alias-0.0.2-2.fc38
Summary: Extension for colcon to create and modify command aliases
RPMs:python3-colcon-alias
Size:33.10 KiB

Package: python-pyclip-0.7.0-1.fc38
Summary: Cross-platform Clipboard module for Python with binary support
RPMs:python3-pyclip
Size:42.31 KiB


= DROPPED PACKAGES =
Package: golang-github-jackc-pgmock-0-0.5.20210110git4fe30f7.fc36
Summary: Mock a PostgreSQL server
RPMs:golang-github-jackc-pgmock-devel
Size:14.59 KiB

Package: golang-sigs-k8s-kustomize-kyaml-0.13.3-5.fc38
Summary: Customization of kubernetes YAML configurations
RPMs:golang-sigs-k8s-kustomize-kyaml-devel
Size:1.04 MiB


= UPGRADED PACKAGES =
Package:  CubicSDR-0.2.7-7.fc38
Old package:  CubicSDR-0.2.7-6.fc37
Summary:  Cross-Platform Software-Defined Radio Panadapter
RPMs: CubicSDR
Size: 4.47 MiB
Size change:  4.74 KiB
Changelog:
  * Mon Nov 07 2022 Richard Shaw  - 0.2.7-7
  - Rebuild for hamlib 4.5.


Package:  R-littler-0.3.17-1.fc38
Old package:  R-littler-0.3.16-1.fc38
Summary:  littler: R at the Command-Line via 'r'
RPMs: R-littler R-littler-examples
Size: 457.26 KiB
Size change:  588 B
Changelog:
  * Mon Nov 07 2022 Mattias Ellert  - 0.3.17-1
  - New upstream release 0.3.17


Package:  annobin-10.92-1.fc38
Old package:  annobin-10.91-1.fc38
Summary:  Annotate and examine compiled binary files
RPMs: annobin-annocheck annobin-docs annobin-libannocheck 
annobin-plugin-clang annobin-plugin-gcc annobin-plugin-llvm
Size: 4.87 MiB
Size change:  -9.12 KiB
Changelog:
  * Mon Nov 07 2022 Nick Clifton   - 10.92-1
  - Annocheck: Try harder not to run mutually exclusive tests.


Package:  arts-8:1.5.10-54.fc38
Old package:  arts-8:1.5.10-53.fc37
Summary:  aRts (analog realtime synthesizer) - the KDE sound system
RPMs: arts arts-devel
Size: 6.01 MiB
Size change:  179.70 KiB
Changelog:
  * Tue Nov 08 2022 Kevin Kofler  - 8:1.5.10-54
  - Disable LTO because it breaks ALSA versioned symbol use, crashing (#1910437)


Package:  awscli-1.27.3-1.fc38
Old package:  awscli-1.27.2-1.fc38
Summary:  Universal Command Line Environment for AWS
RPMs: awscli
Size: 3.24 MiB
Size change:  1 B
Changelog:
  * Mon Nov 07 2022 Gwyn Ciesla  - 1.27.3-1
  - 1.27.3


Package:  baresip-2.9.0-3.fc38
Old package:  baresip-2.9.0-1.fc38
Summary:  Modular SIP user-agent with audio and video support
RPMs: baresip baresip-aac baresip-alsa baresip-av1 baresip-codec2 
baresip-ctrl_dbus baresip-devel baresip-g722 baresip-g726 baresip-gst 
baresip-gtk baresip-jack baresip-mpa baresip-mqtt baresip-opus baresip-plc 
baresip-portaudio baresip-pulse baresip-sdl baresip-snapshot baresip-sndfile 
baresip-tools baresip-v4l2 baresip-vp8 baresip-vp9 baresip-x11
Size: 6.38 MiB
Size change:  20.73 KiB
Changelog:
  * Mon Nov 07 2022 Richard Shaw  - 2.9.0-2
  - Rebuild for updated codec2.

  * Tue Nov 08 2022 Robert Scheck  2.9.0-3
  - Added upstream patch to fix GTK+ dial segfault regression

Re: Help understanding Fedora CI failure wrt RPM Sequoia

[Panu Matilainen]

On 11/8/22 13:05, Miro Hrončok wrote:

On 08. 11. 22 11:13, Panu Matilainen wrote:

Hey,

Thought I'd try to get on with the times and do the Sequoia change via 
a PR instead of just pushing as we've traditionally done. So far so 
good, but it throws up an error which I have no idea how to debug:


https://artifacts.dev.testing-farm.io/700d486d-d409-44fe-b7c3-01634243558e/

 > Unknown Error occured: An rpm exception occurred: package not 
installed


Okay, something failed, and it appears to be related to this very 
change as the tests pass with a "no-op" PR. And in that case, a good 
thing it got caught. But how on earth to debug this? I don't see 
anything even remotely relevant in the accompanying logs, nor did I 
find any obvious way to run this stuff locally.


Help, Obi-Wan KenoCI.


I am far from being a jeCI master,

but considering the tests there were added by me, for 
pyproject-rpm-macros, I decided to have a look.


The STI tests are at 
https://src.fedoraproject.org/rpms/rpm/blob/rawhide/f/tests/tests.yml


They more or less start with:

   tasks:
     - dnf:
     name: "*"
     state: latest

And the logs you link to say:

   TASK [dnf] 
*

   fatal: [sut]: FAILED! => {
   "changed": false,
   "failures": [],
   "rc": 1,
   "results": []
   }

   MSG:

   Unknown Error occured: An rpm exception occurred: package not installed

This means the problem you hit is that ansible is unable to run the DNF 
task.


Yep, that much I understood: something dnf related is failing. And that 
something looks like a situation where dnf thinks a package should be 
installed but isn't.


Now, such a scenario could occur in this very context if there are 
packages with SHA1 signatures involved: a previously installed package 
would seem uninstalled as the header just became unaccessible due to the 
bad signature. Or other similar scenarios revolving around this. But 
what package is that?


I know how to reproduce the actual tests locally without ansible, but 
that would avoid this problem. I suggest not trying to reproduce the 
tests, but reproducing the ansible failure in isolation. My ansible 
skills are limited, I knwo how to edit the YAML, but I have no idea how 
to actually try this out.




Okay, a good point - this quite obviously is *not* related to the python 
%generate_requires tests, so trying to reproduce that in itself is not 
useful.


But I don't know the slightest thing about ansible, beyond a very rough 
idea of what kind of tool it is. Just understanding what exactly it's 
trying to do here would go a long way, I think. But either it's not in 
the logs, or I don't know how to read them.


Thanks for trying to help.

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

Re: [Test-Announce] Help test backlight control changes on old laptops in the upcoming kernel

[Dominik 'Rathann' Mierzejewski]

Hi!

On Monday, 07 November 2022 at 21:12, Hans de Goede wrote:
[...]
> If you want to help test please run the tests from the second blogpost:
> 
> https://hansdegoede.livejournal.com/27130.html
> 
> which is about trying to re-introduce the 6.1 change in a different
> form. Note you can run the requested tests with any recent(ish)
> kernel.
> 
> The 6.2 changes will most likely affect only really old laptops (from
> around 2005), so if possible please run the tests on older laptops.
> 
> So far only one laptop is known to be affected by the planned 6.2
> changes and that is a laptop from 2003, for which I will add a DMI
> quirk to avoid that specific model from regressing in 6.2.

This is really cool! I'll try to set aside some time to test on an
ancient Dell XPS (pre-UEFI model) and on one Sony Vaio that has a
backlight flicker issue at low battery level[1].

[1] https://gitlab.freedesktop.org/drm/intel/-/issues/6325

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: Building two conflicting binaries from the same source

[Simon Farnsworth via devel]

On Tuesday, 8 November 2022 09:43:40 GMT Richard W.M. Jones wrote:
> On Fri, Nov 04, 2022 at 01:44:41PM +0100, Petr Menšík wrote:
> 
> > If there are binaries with different build results, I think some
> > code should be refactored out of the binary itself. The common parts
> > can remain, but hardware specific parts should be moved to
> > dynamically loaded *.so files. The correct files should be loaded
> > depending on hardware found on the system. If auto-detection is
> > wrong, manual configuration via configuration file should be used
> > instead.
> 
> 
> I think this is right.  In particular you cannot assume that "the
> hardware" is a thing which remains stable for the lifetime of a Fedora
> install.
> 
> Sure, if you install Fedora on your laptop then the hardware is
> unlikely to change.  But if you install Fedora on a VM then it can be
> moved and booted on a VM with different (virtual) hardware.  And
> there's also the template case where someone prepares a disk image on
> one set of hardware (maybe virtual or physical) and then the disk
> image is used as a template to clone multiple systems from.
> 
> Having autodetection at run time deals with this, having different
> hardware-specific RPMs installed does not.
> 
> Rich.
> 
Even on a laptop or desktop, hardware may change underneath you. For example, 
early Intel Alder Lake CPUs would expose AVX-512 in CPUID if you turned off all 
the Efficiency cores, and just left the Performance cores; a later microcode 
update stopped this working, and force-disabled AVX-512.

There's also been efforts to bring mainframe-style "upgradeable silicon" down 
to the consumer market, like the Intel Upgrade Service[0]. For laptops, this 
has great appeal to manufacturers - you can build a bunch of machines with a 
soldered down Celeron CPU, and upgrade them to Core i3/i5/i7 during pre-sale 
provisioning, allowing you to reduce your stock needs. Once you can do that, 
why not also sell the upgrade keys to people who bought the cheap Celeron, 
making a profit on up-selling them to the i7 later?

[0] https://en.wikipedia.org/wiki/Intel_Upgrade_Service
-- 
Simon Farnsworth

___
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: Help understanding Fedora CI failure wrt RPM Sequoia

[Miro Hrončok]

On 08. 11. 22 11:13, Panu Matilainen wrote:

Hey,

Thought I'd try to get on with the times and do the Sequoia change via a PR 
instead of just pushing as we've traditionally done. So far so good, but it 
throws up an error which I have no idea how to debug:


https://artifacts.dev.testing-farm.io/700d486d-d409-44fe-b7c3-01634243558e/

 > Unknown Error occured: An rpm exception occurred: package not installed

Okay, something failed, and it appears to be related to this very change as the 
tests pass with a "no-op" PR. And in that case, a good thing it got caught. But 
how on earth to debug this? I don't see anything even remotely relevant in the 
accompanying logs, nor did I find any obvious way to run this stuff locally.


Help, Obi-Wan KenoCI.


I am far from being a jeCI master,

but considering the tests there were added by me, for pyproject-rpm-macros, I 
decided to have a look.


The STI tests are at 
https://src.fedoraproject.org/rpms/rpm/blob/rawhide/f/tests/tests.yml


They more or less start with:

  tasks:
- dnf:
name: "*"
state: latest

And the logs you link to say:

  TASK [dnf] 
*
  fatal: [sut]: FAILED! => {
  "changed": false,
  "failures": [],
  "rc": 1,
  "results": []
  }

  MSG:

  Unknown Error occured: An rpm exception occurred: package not installed

This means the problem you hit is that ansible is unable to run the DNF task.
I know how to reproduce the actual tests locally without ansible, but that 
would avoid this problem. I suggest not trying to reproduce the tests, but 
reproducing the ansible failure in isolation. My ansible skills are limited, I 
knwo how to edit the YAML, but I have no idea how to actually try this out.


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

Help understanding Fedora CI failure wrt RPM Sequoia

[Panu Matilainen]

Hey,

Thought I'd try to get on with the times and do the Sequoia change via a 
PR instead of just pushing as we've traditionally done. So far so good, 
but it throws up an error which I have no idea how to debug:


https://artifacts.dev.testing-farm.io/700d486d-d409-44fe-b7c3-01634243558e/

> Unknown Error occured: An rpm exception occurred: package not installed

Okay, something failed, and it appears to be related to this very change 
as the tests pass with a "no-op" PR. And in that case, a good thing it 
got caught. But how on earth to debug this? I don't see anything even 
remotely relevant in the accompanying logs, nor did I find any obvious 
way to run this stuff locally.


Help, Obi-Wan KenoCI.

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

Re: SPDX Change update

[Petr Pisar]

V Mon, Nov 07, 2022 at 06:46:26PM +0100, Miroslav Suchý napsal(a):
> 8.
> 
>After you migrate your SPEC file, please add the string “SPDX” to the 
> entry of the packages’ %changelog. This is the
>easiest way to detect the migration has been done. The second best option 
> is to add it to the dist-git commit message.
> 
I did not do that when it was clear from the license syntax.

> 9.
> 
>The list of packages that do not mention “SPDX” neither in %changelog nor 
> in dist-git log is here
>
> https://pagure.io/copr/license-validate/blob/main/f/packages-without-spdx-in-distgit-changelog.txtIf
>you see there some false positives, please let me know (privately) and I 
> will adjust my scripts.
> 
Could you remove from the listing spec files whose License tag contains
capitalized SPDX conjunctions (OR AND WITH)? Cf. perl-Alien-Build.

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

Re: SPDX Change update

[Richard W.M. Jones]

Should new package reviews (for Rawhide) now be rejected if they don't
have SPDX tags?

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: Building two conflicting binaries from the same source

[Richard W.M. Jones]

On Fri, Nov 04, 2022 at 01:44:41PM +0100, Petr Menšík wrote:
> If there are binaries with different build results, I think some
> code should be refactored out of the binary itself. The common parts
> can remain, but hardware specific parts should be moved to
> dynamically loaded *.so files. The correct files should be loaded
> depending on hardware found on the system. If auto-detection is
> wrong, manual configuration via configuration file should be used
> instead.

I think this is right.  In particular you cannot assume that "the
hardware" is a thing which remains stable for the lifetime of a Fedora
install.

Sure, if you install Fedora on your laptop then the hardware is
unlikely to change.  But if you install Fedora on a VM then it can be
moved and booted on a VM with different (virtual) hardware.  And
there's also the template case where someone prepares a disk image on
one set of hardware (maybe virtual or physical) and then the disk
image is used as a template to clone multiple systems from.

Having autodetection at run time deals with this, having different
hardware-specific RPMs installed does not.

Rich.


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