Hey folks! While we're working through fixing this up, I wanted to send
out a note about what's going on.
tl;dr summary: GNOME is broken in Rawhide, and blueberry (Cinnamon's
bluetooth app) may have dep issues temporarily. If you need GNOME to
work, downgrade gnome-shell and mutter. Otherwise, apo
Hello all.
tdlib 1.8.0 will include soversion bump from .1.7.0 to .1.8.0.
--
Sincerely,
Vitaly Zaitsev (vit...@easycoding.org)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Dne 15. 02. 22 v 22:08 Matthew Kenigsberg napsal(a):
It sounds like there's already some effort to make tasks in RPMs like adding
users more
declarative:https://docs.fedoraproject.org/en-US/packaging-guidelines/UsersAndGroups/
Which is still not finished and you still need to call the old scri
On Wed, 2022-02-16 at 09:17 +0100, Miroslav Suchý wrote:
> Dne 15. 02. 22 v 22:08 Matthew Kenigsberg napsal(a):
> > It sounds like there's already some effort to make tasks in RPMs like
> > adding users more
> > declarative:https://docs.fedoraproject.org/en-US/packaging-guidelines/UsersAndGroups/
On 15/02/2022 19:43, Björn Persson wrote:
The packager would then be required to authenticate with their existing
credentials – or prove their identity in some way that does not rely on
ownership of the email address – and set a new email address in their
account.
How? I know only one suitable
On 15/02/2022 22:08, Matthew Kenigsberg wrote:
It sounds like there's already some effort to make tasks in RPMs like adding
users more
declarative:https://docs.fedoraproject.org/en-US/packaging-guidelines/UsersAndGroups/
https://pagure.io/packaging-committee/issue/1158
Do you think it would
On 16/02/2022 09:17, Miroslav Suchý wrote:
* update-desktop-database - which - I believe - has been already
replaced by filetriggers, but it is still used.
update-desktop-database, update-mime-database, ldconfig, update-manpages
and gtk-update-icon-cache should be removed from all Fedora SPE
On 16/02/2022 09:17, Miroslav Suchý wrote:
* update-desktop-database - which - I believe - has been already
replaced by filetriggers, but it is still used.
update-desktop-database, update-mime-database, ldconfig, update-manpages
and gtk-update-icon-cache should be removed from all Fedora SPE
Hi Adam,
I'm not the blueberry maintainer anymore.
This change wont prevent the cinnamon spin from building as blueberry is a
python app.
https://src.fedoraproject.org/rpms/blueberry/blob/rawhide/f/blueberry.spec#_23
I will raise the issue with the team.
Regards,
Leigh
___
Hi,
On Wed, Feb 16, 2022 at 9:18 AM Miroslav Suchý wrote:
>
> Dne 15. 02. 22 v 22:08 Matthew Kenigsberg napsal(a):
>
> It sounds like there's already some effort to make tasks in RPMs like adding
> users more declarative:
> https://docs.fedoraproject.org/en-US/packaging-guidelines/UsersAndGroup
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-35-20220215.0):
ID: 1131435 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://op
On Wed, 2022-02-16 at 08:32 +, Leigh Scott wrote:
> Hi Adam,
>
> I'm not the blueberry maintainer anymore.
> This change wont prevent the cinnamon spin from building as blueberry is a
> python app.
By building I meant it'll probably prevent the *image* from composing,
because blueberry is a
Hello,
is there anybody willing to review python-specfile [1]?
I'd be happy to review a package of similar complexity in return.
Thanks,
Nikola
[1] https://bugzilla.redhat.com/show_bug.cgi?id=2054599
___
devel mailing list -- devel@lists.fedoraproject
On 16. 02. 22 9:43, Aleksandra Fedorova wrote:
Do I understand correctly that there is a general agreement that it is
the right direction to take, and the main reason why we are not there
yet is the size of the effort?
Correct.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
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-34-20220215.0):
ID: 1131451 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://op
On Tue, Feb 15, 2022 at 12:56:50AM +0100, Germano Massullo wrote:
> After having dealt for the n-th time with libvirt dependencies
> messing up [1] with zfs packages installed from ZFS On Linux
> repository, I wondered if we could just include them in Fedora
> repository.
> They are not in the Fedo
Vitaly Zaitsev via devel wrote:
> On 15/02/2022 19:43, Björn Persson wrote:
> > The packager would then be required to authenticate with their existing
> > credentials – or prove their identity in some way that does not rely on
> > ownership of the email address – and set a new email address in the
On Wed, Feb 16, 2022 at 09:43:05AM +0100, Aleksandra Fedorova wrote:
> Hi,
>
> On Wed, Feb 16, 2022 at 9:18 AM Miroslav Suchý wrote:
> >
> > Dne 15. 02. 22 v 22:08 Matthew Kenigsberg napsal(a):
> >
> > It sounds like there's already some effort to make tasks in RPMs like
> > adding users more de
On 15/02/2022 00:56, Germano Massullo wrote:
but since ZFS On Linux provide zfs-dkms package, I think this should
avoid any possible legal trouble between Linux kernel licence and ZFS
licence.
Fedora doesn't allow packaging of any third-party Linux kernel modules.
--
Sincerely,
Vitaly Zaits
On 16/02/2022 11:32, Björn Persson wrote:
Loss of an email address does not imply loss of a FAS passphrase, so in
most cases they would just log in as usual.
We're talking about potentially hacked accounts, right? If the hacker
has the password, they can easily restore this account. That's why
On Wed, Feb 16, 2022 at 10:28:18AM +, Richard W.M. Jones wrote:
> On Tue, Feb 15, 2022 at 12:56:50AM +0100, Germano Massullo wrote:
> > After having dealt for the n-th time with libvirt dependencies
> > messing up [1] with zfs packages installed from ZFS On Linux
> > repository, I wondered if w
On Tue, Feb 15, 2022 at 12:56:50AM +0100, Germano Massullo wrote:
> After having dealt for the n-th time with libvirt dependencies messing up
> [1] with zfs packages installed from ZFS On Linux repository, I wondered if
> we could just include them in Fedora repository.
> They are not in the Fedora
> On Wed, 2022-02-16 at 08:32 +, Leigh Scott wrote:
>
> By building I meant it'll probably prevent the *image* from composing,
> because blueberry is a 'mandatory' package in the group, and its
> dependencies will no longer be satisfied, so liveimage-creator will
> choke on that.
That's easy
Dear maintainers.
Based on the current fail to build from source policy, the following packages
should be retired from Fedora 36 approximately one week before branching.
However, 5 weekly reminders are required and I forgot to start this sooner,
hence the retirement will happen in 5 weeks, i.e.
Dne 16. 02. 22 v 9:43 Aleksandra Fedorova napsal(a):
doesn't say anything about scriptlets being discouraged:
because we are far from using a word "discouraged". But yes, filetriggers and
other similar methods should be prefered.
Miroslav
___
devel
OLD: Fedora-36-20220215.n.0
NEW: Fedora-36-20220216.n.0
= SUMMARY =
Added images:1
Dropped images: 0
Added packages: 4
Dropped packages:0
Upgraded packages: 73
Downgraded packages: 0
Size of added packages: 2.73 MiB
Size of dropped packages:0 B
Size of
On Wed, Feb 16, 2022 at 7:54 AM Miroslav Suchý wrote:
>
> Dne 16. 02. 22 v 9:43 Aleksandra Fedorova napsal(a):
> > doesn't say anything about scriptlets being discouraged:
>
> because we are far from using a word "discouraged". But yes, filetriggers and
> other similar methods should be prefered.
No missing expected images.
Failed openQA tests: 1/16 (x86_64), 2/15 (aarch64)
Old failures (same test failed in Fedora-IoT-36-20220214.0):
ID: 1132002 Test: x86_64 IoT-dvd_ostree-iso release_identification
URL: https://openqa.fedoraproject.org/tests/1132002
ID: 1132014 Test: aarch64 IoT
I have orphaned rubygem-cucumber-rails + rubygem-database_cleaner.
Both package are currently FTBFS. Originally, I attempted to update
rubygem-cucumber-rails, before realizing that it would require more
effort. The fix would ideally involve rebase but also update of
rubygem-database_cleaner, w
No missing expected images.
Failed openQA tests: 16/161 (aarch64), 12/229 (x86_64)
New failures (same test not failed in Fedora-36-20220215.n.0):
ID: 1131728 Test: aarch64 Server-dvd-iso support_server@uefi
URL: https://openqa.fedoraproject.org/tests/1131728
ID: 1131739 Test: aarch64 Ser
No missing expected images.
Failed openQA tests: 4/48 (x86_64)
ID: 1132045 Test: x86_64 Workstation-live-iso gnome_text_editor
URL: https://openqa.fedoraproject.org/tests/1132045
ID: 1132054 Test: x86_64 Workstation-live-iso desktop_printing_builtin
URL: https://openqa.fedoraproject.org/t
Hello,
I don't mean to jump in the midle here, and I am just tossing out an
idea for consideration that doesn't address security issues pointed out
really, but does discuss the non-responsive main maintainer.
I note there is a difficulty in defining the criteria for determining
when an (apparently
* Stephen Snow [16/02/2022 11:21] :
>
> Perhaps the automation should do
> just that, demote primary packager (from owner to co-maintainer) if
> inactive for over a year and promote the main supporter for the year to
> be the owner from co-maintainer.
Can you de
On Wed, 2022-02-16 at 12:06 +, Leigh Scott wrote:
> > On Wed, 2022-02-16 at 08:32 +, Leigh Scott wrote:
> >
> > By building I meant it'll probably prevent the *image* from
> > composing,
> > because blueberry is a 'mandatory' package in the group, and its
> > dependencies will no longer be
https://fedoraproject.org/wiki/Changes/polkit_recommends_pkla_pkexec
== Summary ==
Split `pkexec` from the polkit package and make it a recommended only
sub-package. Similarly, make the polkit-pkla-compat package a
recommended package too. This will enable users and desktop no longer
relying on t
https://fedoraproject.org/wiki/Changes/Silverblue_Kinoite_readonly_sysroot
== Summary ==
This change is about enabling an opt-in ostree feature that re-mounts
`/sysroot` as read only to avoid accidental changes.
Users and administrators are not expected to directly interact with
the content avai
On Wed, 2022-02-16 at 11:21 -0500, Stephen Snow wrote:
> Hello,
> I don't mean to jump in the midle here, and I am just tossing out an
> idea for consideration that doesn't address security issues pointed out
> really, but does discuss the non-responsive main maintainer.
> I note there is a diffic
On Wed, 2022-02-16 at 12:12 -0500, Ben Cotton wrote:
> https://fedoraproject.org/wiki/Changes/polkit_recommends_pkla_pkexec
>
>
> == Summary ==
> Split `pkexec` from the polkit package and make it a recommended only
> sub-package. Similarly, make the polkit-pkla-compat package a
> recommended pac
On Mi, 16.02.22 12:12, Ben Cotton (bcot...@redhat.com) wrote:
> `pkexec` and `pkla-compat`
> ([https://src.fedoraproject.org/rpms/polkit-pkla-compat package]) are
> legacy tools that are no longer needed on a desktop and increase the
> attack surface as they are SetUID binaries (`pkexec`) or not
>
On Wed, 2022-02-16 at 17:38 +0100, Emmanuel Seyman wrote:
> * Stephen Snow [16/02/2022 11:21] :
> >
> > Perhaps the automation should
> > do
> > just that, demote primary packager (from owner to co-maintainer) if
> > inactive for over a year and promote the main
On Wed, 2022-02-16 at 12:12 -0500, Ben Cotton wrote:
> https://fedoraproject.org/wiki/Changes/Silverblue_Kinoite_readonly_sysroot
>
> == Summary ==
>
> This change is about enabling an opt-in ostree feature that re-mounts
> `/sysroot` as read only to avoid accidental changes.
>
> Users and admin
On Wed, 2022-02-16 at 09:13 -0800, Adam Williamson wrote:
> On Wed, 2022-02-16 at 11:21 -0500, Stephen Snow wrote:
> > Hello,
> > I don't mean to jump in the midle here, and I am just tossing out
> > an
> > idea for consideration that doesn't address security issues pointed
> > out
> > really, but
On Wed, Feb 16, 2022, at 12:48 PM, Stephen Snow wrote:
> On Wed, 2022-02-16 at 12:12 -0500, Ben Cotton wrote:
>> https://fedoraproject.org/wiki/Changes/Silverblue_Kinoite_readonly_sysroot
>>
>> == Summary ==
>>
>> This change is about enabling an opt-in ostree feature that re-mounts
>> `/sysroo
> I use Silverblue. How does this affect my ability to modify /etc in the
> opt-in scenario? Does rpm-ostree offer a method to modify /etc in that
> case? What if I want a mutable /var, like I currently have, does this
> change under this proposal? What is the value of this for the normal
> Fedora
Thanks for your clarification Colin.
Stephen
On Wed, 2022-02-16 at 13:16 -0500, Colin Walters wrote:
>
>
> On Wed, Feb 16, 2022, at 12:48 PM, Stephen Snow wrote:
> > On Wed, 2022-02-16 at 12:12 -0500, Ben Cotton wrote:
> > > https://fedoraproject.org/wiki/Changes/Silverblue_Kinoite_readonly_sysr
Very good,
Thank you for further clarification.
Stephen
On Wed, 2022-02-16 at 18:18 +, Timothée Ravier wrote:
> > I use Silverblue. How does this affect my ability to modify /etc in
> > the
> > opt-in scenario? Does rpm-ostree offer a method to modify /etc in
> > that
> > case? What if I want
> Splitting them off but making them Recommended seems odd to me. At that
> point we've got all the work of splitting them but little of the
> benefit, because soft dependencies are included when building images,
> so our default installs are still going to include pkexec.
>
> Why not just not hav
> I find this wording weird... I seriously doubt we should consider
> "pkexec" legacy. It's the much nicer approach to the "sudo"
> problem,
> as mentioned in earlier discussions...
>
> Splitting it off into a separate package might be OK, but claiming
> that the fact that it is a suid binary make
There are some CVE's against KiCad that have been fixed in the latest version,
namely KiCad 6.0.2. I've built that for F36 and Rawhide.
I have not released KiCad 6.0.2 into Fedora 34 and 35, because my understanding is that
by policy, we don't generally allow "major version" updates in stable
On Wed, Feb 16, 2022 at 12:38 PM Lennart Poettering
wrote:
>
> On Mi, 16.02.22 12:12, Ben Cotton (bcot...@redhat.com) wrote:
>
> > `pkexec` and `pkla-compat`
> > ([https://src.fedoraproject.org/rpms/polkit-pkla-compat package]) are
> > legacy tools that are no longer needed on a desktop and increa
On Wed, 16 Feb 2022 13:53:04 -0500
"Steven A. Falco" wrote:
> There are some CVE's against KiCad that have been fixed in the latest
> version, namely KiCad 6.0.2. I've built that for F36 and Rawhide.
>
> I have not released KiCad 6.0.2 into Fedora 34 and 35, because my
> understanding is that
On Mon, Feb 14, 2022 at 07:11:48AM -0500, Steve Cossette wrote:
> It only recently dawned on me that, unlike Windows, Linux distros are
> maintained by the community (duh) so I thought I'd offer to help. One of
> the ways I can help is by helping maintain packages (As a Co-Maintainer).
That's grea
On 2/16/22 01:58 PM, Dan Horák wrote:
On Wed, 16 Feb 2022 13:53:04 -0500
"Steven A. Falco" wrote:
There are some CVE's against KiCad that have been fixed in the latest version,
namely KiCad 6.0.2. I've built that for F36 and Rawhide.
I have not released KiCad 6.0.2 into Fedora 34 and 35, be
Hello Matthew!
Thanks for the reply! Looking forward to contributing in several ways!
Le mer. 16 févr. 2022, à 14 h 08, Matthew Miller
a écrit :
> On Mon, Feb 14, 2022 at 07:11:48AM -0500, Steve Cossette wrote:
> > It only recently dawned on me that, unlike Windows, Linux distros are
> > mainta
Il 14/02/22 20:19, Adam Williamson ha scritto:
> On Mon, 2022-02-14 at 17:48 +, Mattia Verga via devel wrote:
>> As I reported in the Fesco ticket, I've published the script to check
>> packagers activity at https://pagure.io/find-inactive-packagers
>>
>> The latest run showed 274 totally inact
Adam Williamson wrote:
> Since the builds have been in a compose, we can't untag them from
> Rawhide, we can only move forwards.
Why can we not make an exception to this stubborn policy in cases like this?
We did not have this rule a few years ago and things worked out just fine.
And these days,
Minutes:
https://meetbot.fedoraproject.org/fedora-meeting-1/2022-02-16/fedora_coreos_meeting.2022-02-16-16.30.html
Minutes (text):
https://meetbot.fedoraproject.org/fedora-meeting-1/2022-02-16/fedora_coreos_meeting.2022-02-16-16.30.txt
Log:
https://meetbot.fedoraproject.org/fedora-meeting-1/2022
On Thu, Feb 10, 2022 at 5:26 AM Richard W.M. Jones wrote:
> On Wed, Feb 09, 2022 at 08:31:31AM -0700, Jerry James wrote:
> > On Fri, Feb 4, 2022 at 5:24 AM Richard W.M. Jones wrote:
> > > On Thu, Feb 03, 2022 at 08:03:27PM -0700, Jerry James wrote:
> > > > ocaml-tplib
> > >
> > > I think this is
On Thu, Feb 10, 2022 at 11:18 AM Miro Hrončok wrote:
> Action items:
>
> python-random2 -> will investigate more
>
> python-readthedocs-sphinx-ext -> ksurma
> python-sphinx_rtd_theme -> ksurma
>
> python-repoze-sphinx-autointerface -> lbalhar
>
> python-sphinx-copybutton -> churchyard
> python-sph
Hi. I was checking if the scrcpy software [1] could get packaged, but to
continue I need to know how to package an APK package file. For context,
this project consists on a Linux client and an Android server app that is
uploaded as an APK package by the client to an Android device using adb to
shar
Following is the list of topics that will be discussed in the FPC
meeting Thursday at 2022-02-17 17:00 UTC in #fedora-meeting-1 on
irc.libera.chat.
Local time information (via. uitime):
= Day: Thursday ==
2022-02-17 09:00 PST US/Pacific
2022-02-17 12
On Wed, 2022-02-16 at 10:35 +, Richard W.M. Jones wrote:
> Definitely. I have long said that any time there's a scriptlet in an
> RPM package, we should work towards removing it.
>
> BTW I found this F31 change proposal. Did it happen? The bug was
> CLOSED/CURRENTRELEASE.
>
> https://fedor
Hi -
> There really ought to be tested migration scripts or at least instructions
> supplied. [...]
> Could the Change proponents commit to producing transition instructions
> for servers & clients?
Recalling that such commitments were made as a part of the FESCO
approval of this change (and it
On Wed, Feb 16, 2022 at 4:47 PM Frank Ch. Eigler wrote:
>
>
> Recalling that such commitments were made as a part of the FESCO
> approval of this change (and its sibling - the dropping of YP servers),
> is this done yet?
Not as far as I know, but this Change was deferred to F37 today.
--
Ben
Glad to hear there's a lot of interest in this!
I think file triggers would definitely help with optimizing containerization,
but I think it still has some issues. Two properties that would be desirable
for optimizing containerization are:
1. Mergeability. If multiple packages perform the same t
This is the obligatory announcement that the license of the
gi-docgen-doc subpackage of gi-docgen has been corrected from:
(ASL 2.0 or GPLv3+) and CC0 and CC-BY
to:
(ASL 2.0 or GPLv3+) and CC0 and CC-BY-SA
___
devel mailing list -- devel@lists.fedora
On Wed, 2022-02-16 at 14:20 -0500, Steven A. Falco wrote:
> On 2/16/22 01:58 PM, Dan Horák wrote:
> > On Wed, 16 Feb 2022 13:53:04 -0500
> > "Steven A. Falco" wrote:
> >
> > > There are some CVE's against KiCad that have been fixed in the latest
> > > version, namely KiCad 6.0.2. I've built tha
On Wed, 2022-02-16 at 19:49 +, Mattia Verga via devel wrote:
> Il 14/02/22 20:19, Adam Williamson ha scritto:
> > On Mon, 2022-02-14 at 17:48 +, Mattia Verga via devel wrote:
> > > As I reported in the Fesco ticket, I've published the script to check
> > > packagers activity at https://pagu
On Wed, 2022-02-16 at 21:43 +0100, Kevin Kofler via devel wrote:
> Adam Williamson wrote:
> > Since the builds have been in a compose, we can't untag them from
> > Rawhide, we can only move forwards.
>
> Why can we not make an exception to this stubborn policy in cases like this?
> We did not hav
Adam Williamson wrote:
> AFAIK we've always had that rule. It's always been policy that we don't
> untag once a build has been in a successful compose. I don't think this
> changed "a few years ago", unless I'm misremembering.
Not always: The policy that disallows Rawhide going backwards was suppo
On 16. 02. 22 21:57, Jerry James wrote:
On Thu, Feb 10, 2022 at 11:18 AM Miro Hrončok wrote:
Action items:
python-random2 -> will investigate more
python-readthedocs-sphinx-ext -> ksurma
python-sphinx_rtd_theme -> ksurma
python-repoze-sphinx-autointerface -> lbalhar
python-sphinx-copybutton
No missing expected images.
Failed openQA tests: 3/48 (x86_64)
ID: 1132045 Test: x86_64 Workstation-live-iso gnome_text_editor
URL: https://openqa.fedoraproject.org/tests/1132045
ID: 1132337 Test: x86_64 KDE-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/1132337
ID: 1
On 17. 02. 22 1:08, Miro Hrončok wrote:
On 16. 02. 22 21:57, Jerry James wrote:
On Thu, Feb 10, 2022 at 11:18 AM Miro Hrončok wrote:
Action items:
python-random2 -> will investigate more
python-readthedocs-sphinx-ext -> ksurma
python-sphinx_rtd_theme -> ksurma
python-repoze-sphinx-autointer
On Thu, Feb 17, 2022 at 01:21:15AM +0100, Kevin Kofler via devel wrote:
> Adam Williamson wrote:
> > AFAIK we've always had that rule. It's always been policy that we don't
> > untag once a build has been in a successful compose. I don't think this
> > changed "a few years ago", unless I'm misremem
On 2/16/22 18:05, Adam Williamson wrote:
> On Wed, 2022-02-16 at 14:20 -0500, Steven A. Falco wrote:
>> On 2/16/22 01:58 PM, Dan Horák wrote:
>>> On Wed, 16 Feb 2022 13:53:04 -0500
>>> "Steven A. Falco" wrote:
>>>
There are some CVE's against KiCad that have been fixed in the latest
ver
Following this: https://fedoraproject.org/wiki/Netconsole
The debuggee (system with the problem) has wifi. Is netconsole
expected to work over wifi? The module refuses to load during boot,
without error, even if I bake the module into the initramfs. And when
I issue the modprobe command from comma
Hi list,
the recent mimalloc update from 2.0.3 to 2.0.5 has brought a subtle, yet
consequential, soname change (or rather addition) that affects the package's
`Provides:` list.
mimalloc-2.0.3-1 contains the library file
* `/usr/lib64/libmimalloc.so.2.0`
... and thus provides:
* `libmimalloc.so.
77 matches
Mail list logo
