On Tue, Apr 29 2025 at 11:56:15 AM -05:00:00, Michael Catanzaro
wrote:
For context on this, see: https://pagure.io/releng/issue/12617
And also:
https://github.com/cisco/openh264/security/advisories/GHSA-m99q-5j7x-7m9x
--
___
devel mailing list
Too bad dnf does not tell us *why* there are "conflicting requests."
On Tue, Apr 29 2025 at 11:00:18 AM -05:00:00, Chris Adams
wrote:
I'm asking because there's a high-priority CVE on openh264 for months
that doesn't seem like it's progressing towards getting resolved in
Fedora.
For context
On Thu, Apr 17 2025 at 10:28:21 AM +02:00:00, Vitaly Zaitsev via devel
wrote:
Sorry, but I'm still skeptical about this change. I don't see any real
benefits for Fedora. I only see additional pain for maintainers.
Hmm, but it is one-time pain. If you use a nonstandard variable, your
package w
On Tue, Apr 15 2025 at 05:40:43 PM +01:00:00, Richard W.M. Jones
wrote:
I've no argument that Webex is hot proprietary garbage, just saying
that it was once noted as being a blocker.
Let's agree that anything we cannot fix also cannot be a blocker.
Third-party proprietary software has had two
On Tue, Apr 15 2025 at 12:31:48 PM -04:00:00, Neal Gompa
wrote:
This is rude and uncalled for. The Flatpak is an unsupported way to
use Steam since it has issues with gamepads, can't access game drives,
and messes with the built-in sandbox provided by Steam.
OK, but we surely cannot block i
On Tue, Apr 15 2025 at 05:18:06 PM +01:00:00, Richard W.M. Jones
wrote:
What about Webex, the awful video conferencing software? I've no
desire to investigate this, but ISTR it linked to system i686 libs.
Irrelevant. Webex has a web UI. Use that instead. Continuing to build
i686 packages jus
On Tue, Apr 15 2025 at 12:23:06 AM +02:00:00, Frantisek Zatloukal
wrote:
I've opened a PR which restores gdm/X11 support at:
https://src.fedoraproject.org/rpms/gdm/pull-request/28#
It builds, I'll be able to test it in a few hours, but anybody is
free and welcome to give it a try once the
I think the practical effect of the lightweight process will be: new
contributor likely becomes the de facto maintainer of the package,
while bug reports continue to be assigned to the non-responsive main
admin.
Maybe it's better to just rip the band-aid off and acknowledge that
when a main
On Tue, Apr 15 2025 at 01:19:10 AM +02:00:00, Fabio Valentini
wrote:
The non-responsive maintainer process requires that the maintainer is
*entirely unresponsive*,
which is a much higher bar than for this proposed, less-consequential
process.
If the maintainer is not unresponsive, why can't y
So on the one hand, it seems a little petty for Fedora to disable X11
support in gdm before upstream does. It's notably still enabled by
default in upstream GNOME 48 and in git master.
On the other hand, if we're confident upstream is likely going to
remove the X11 support relatively soon, t
On Wed, Apr 9 2025 at 05:51:00 PM -07:00:00, Kevin Fenzi
wrote:
If you aren't using gnome and want X11 sessions, you should have
switched to another display manager long ago. When gdm switched to
being a gnome session in the greeter... I'm not sure how many years
ago
that was now.
I think th
On Mon, Mar 31 2025 at 08:09:49 PM +00:00:00, Zbigniew
Jędrzejewski-Szmek wrote:
OK, I guess I need to work on my English. You're the second person who
read the abovequoted part in the exact opposite way to what I
intended :(
Hm, well I misread. You didn't write the wrong thing.
But honestly
On Mon, Mar 31 2025 at 10:53:54 AM +00:00:00, Zbigniew
Jędrzejewski-Szmek wrote:
This is only "SHOULD", because sometimes the git tarball is too large
or has other deficiencies. Another reason is that the "upstream
tarball" may be signed, and that'd be preferred to the unsigned "raw"
archive. B
Fabio is going to handle builds. Thank you, Fabio!
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/cod
It seems nothing except GStreamer has been rebuilt.
--
___
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/co
It's been more than one week. Are we ready to land this side tag?
--
___
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
I'm pretty concerned that we have no automation to catch these
problems. Would we have even noticed if not for you manually checking
and complaining here on devel@?
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an e
On Sat, Mar 8 2025 at 06:27:19 AM -08:00:00, Neal Gompa
wrote:
If I'm answering that question for myself, I would say that the
biggest feature gap that we have from a modern build system like the
Open Build Service is that we as packagers have to do dependency
resolution for building groups of p
On Mon, Mar 10 2025 at 11:11:33 AM +00:00:00, Richard W.M. Jones
wrote:
Thanks for this link. The instance is:
https://konflux.apps.kfluxfedorap01.toli.p1.openshiftapps.com/application-pipeline
I played around for about 3 minutes and am very confused. The overview
page looks like an adverti
Hi, I am wondering if it is possible to use 'fedpkg mockbuild' to
easily build for a side tag.
I know that it's possible by using 'koji mock-config' and then 'fedpkg
mockbuild --mock-config' but this is not easy since it requires
creating a local mock configuration file. Would be nice if it we
The new noopenh264 is now available in the side tag. Packagers, please
start your builds!
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https:/
On Tue, Mar 4 2025 at 02:46:12 PM -00:00:00, Leigh Scott
wrote:
You will need to update noopenh264 to match openh264
Yes, noopenh264 is what packages are actually built against. We'll need
to do a new noopenh264 build using f43-build-side-106953 first, then
once that's finished other maintai
On Mon, Feb 24 2025 at 01:54:15 PM -05:00:00, Neal Gompa
wrote:
Didn't we already do this? I adapted KDE Plasma, MiracleWM, LXQt, and
COSMIC for this in F42 already.
And now GNOME is switching back to regular JPEG, see:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6886#note_2360630
htt
On Tue, Jan 21 2025 at 05:13:07 AM -05:00:00, Neal Gompa
wrote:
We know it's possible because this is how openSUSE works today. They
never schedule mass builds because they always happen automatically
with the right conditions, so it's a non-event. This is the direction
we should be going, but b
Guess: is it caused by -Wl,as-needed? You could try this workaround in
the spec file and see if that helps:
%undefine _ld_as_needed
The proper fix is surely to link libcore.so to everything that it needs
(glib, cairo, and the libcommon which provides
spectre_tiling_params_invalid) but this
On Fri, Nov 29 2024 at 08:09:20 PM -05:00:00, Neal Gompa
wrote:
Indeed. This stuff should work out of the box. It is unacceptable to
break it like this.
Looks like it's fixed by pkcs11-provider-0.6-2, which is a sabotage
update to turn off pkcs11-provider until the problem can be fixed
prope
On Wed, Nov 20 2024 at 04:03:27 PM +01:00:00, Clemens Lang
wrote:
That was the case with openssl-pkcs11 (the package that contains the
OpenSSL PKCS#11 ENGINE) for years.
The use of PKCS#11 tokens is not very common. I don’t think it’s
too much to ask to install an additional package if you want
On Wed, Nov 20 2024 at 11:09:05 AM +01:00:00, Clemens Lang
wrote:
The idea here was to auto-enable pkcs11-provider when it is
installed, which still makes sense to me. The issue here I think is
that many people ended up with pkcs11-provider installed because of a
recommendation. We should remo
On Thu, Nov 7 2024 at 02:41:08 PM +01:00:00, Vojtěch Polášek
wrote:
Any idea what I am doing wrong?
Probably nothing. dconf is a lower layer than gsettings. You've changed
the default value in gsettings, which is what you're supposed to do. I
suggest you just forget about dconf; that's an ir
On Thu, Nov 7 2024 at 04:40:07 PM +01:00:00, Vojtěch Polášek
wrote:
I can't find much documentation, but how to properly override
relocatable schema?
A, OK, so that's the problem. If it worked, then the syntax would
be:
[schema:path]
e.g.
[org.gnome.settings-daemon.plugins.media-keys.
On Mon, Nov 4 2024 at 10:52:18 AM -05:00:00, Stephen Gallagher
wrote:
For the sake of keeping the conversation in one place, I do ask that
you reply on the Discussion thread, rather than on Fedora Devel,
please.
Heh, that was a good joke!
--
___
de
On Fri, Nov 1 2024 at 05:13:49 PM +01:00:00, Leon Fauster via devel
wrote:
Ok, thanks. Following questions arised here now:
- An explanation, why its bad would bring some light into this.
Dconf is not the only possible GSettings backend. E.g. if your RPM gets
used to build a Flatpak app, t
On Fri, Nov 1 2024 at 03:13:21 PM +01:00:00, Leon Fauster via devel
wrote:
I had the impression that globally installed configurations
(e.g. /etc/dconf/db/local.d/) should be "committed" with
# dconf update
No, don't do this. For the same reason you never package dconf
overrides, you also nev
On Fri, Nov 1 2024 at 11:04:51 AM +01:00:00, Vojtěch Polášek
wrote:
Hello Michael,
this seems to be what I am searching for.
But any idea how to package this properly?
Is it enough to install the file and mention it in the %files section?
Yes.
Or do I have to run some %post command?
On Fri, Oct 25 2024 at 10:01:02 AM +02:00:00, Vojtěch Polášek
wrote:
I would like to customize some keybindings because they are not set
from
the start. I think the best would be to use dconf overrides.
dconf overrides are intended for system administrators and should never
be packaged.
Yo
On Mon, Oct 21 2024 at 02:51:56 PM +02:00:00, Lennart Poettering
wrote:
I know you don't like systemd-resolved, but maybe you can at least
acknowledge that is does exist.
The nice thing about IPC APIs is it's easy to reimplement them however
you please, similar to how elogind reimplements man
If anybody has any grand ideas, we also don't know what's wrong in this
issue:
https://bugzilla.redhat.com/show_bug.cgi?id=2316066
My best guess is that some component is looking at wall clock time when
monotonic time is required, causing D-Bus calls or systemd service
activation to time out.
On Thu, Oct 10 2024 at 05:36:25 PM +02:00:00, Lennart Poettering
wrote:
I wished Fedora would focus more on making Measured Boot by default a
thing (other distros are working towards that, for example SUSE has
been investing in that), but Fedora is not precisely leading in this
effort right now.
On Thu, Oct 10 2024 at 11:25:30 AM +02:00:00, Alexander Sosedkin
wrote:
Don't Panic.
https://src.fedoraproject.org/rpms/firefox lists 131.0-2 in all
branches,
https://koji.fedoraproject.org/koji/packageinfo?packageID=37 lists a
dozen of 131.0-2 builds as well.
Sent from a
$ rpm -q firefox
fir
On Mon, Oct 7 2024 at 12:59:46 PM -04:00:00, Simo Sorce
wrote:
Changing a default like this is not something to do lightly IMHO.
I'm interested in systemd-homed because we currently have no other
plausible path towards encryption of user data by default [1] (since
use of LUKS full-disk encry
On Tue, Sep 17 2024 at 07:19:23 AM -04:00:00, Neal Gompa
wrote:
Amberol[2]
I've been using Amberol as my primary audio player for half a year, and
I don't think it's a good choice. I would focus on Decibels.
--
___
devel mailing list -- devel@lis
On Mon, Sep 2 2024 at 07:56:58 AM +02:00:00, Alexander Ploumistos
wrote:
Michael, if you still feel this should be reported upstream, there is
this bug in Debian Sid - our systems haven't filed an FTBFS bug yet:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078386
I'd say the return ty
We should probably revert that. If you have a GNOME GitLab account,
feel free to create an issue report. Otherwise, I can do so.
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproje
On Sun, Aug 11 2024 at 04:47:17 PM -00:00:00, Javier Jardón via devel
wrote:
I guess updating in f40 would require additional processes?
Yeah. Just don't. :)
The alternative would be to create buildstream2 as a compat package and
introduce it into F40 as a new package. I don't see much point
On Wed, Jul 31 2024 at 09:23:12 AM -07:00:00, Kevin Fenzi
wrote:
Some possible ones I'll toss out there:
avahi-daemon
cups
rsyslog
dovecot
cockpit
Maybe gnome-remote-desktop?
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscrib
On Sun, Jul 28 2024 at 11:37:15 AM +02:00:00, Arthur Bols via devel
wrote:
Aside that this does not contribute to the discussion at all, I
believe
it is reasonable to assume that the default firewall rules are strict
enough to not open all ports above 1024... That being said, it's an
example, a
On Wed, Jul 24 2024 at 09:41:16 AM -04:00:00, Stephen Smoogen
wrote:
1. There are some subset of people who use Fedora because they thought
it was a privacy focused distribution. Their concerns did not seem to
be taken into account or it needs to be made clearer that is not what
the project a
On Mon, Jul 8 2024 at 08:51:58 PM +00:00:00, Zbigniew
Jędrzejewski-Szmek wrote:
Does the table store counts or separate entries? I would guess that if
it just stores disaggregated values, then the values repeat often, and
it's natural to store the count in the table. And then the order
doesn'
On Mon, Jul 8 2024 at 02:28:09 PM -05:00:00, Michael Catanzaro
wrote:
Good question! I *think* timestamps are no longer a problem. It does
store precise timestamps alongside a hash of the full submission, but
it doesn't actually store the full submission itself anymore, and the
firs
On Mon, Jul 8 2024 at 01:51:07 PM -04:00:00, Przemek Klosowski via
devel wrote:
At the same time, I ask the proponents to confirm that there will be
no
way to re-aggregate the data by any means (timestamps, Fedora account
cookies, load factor on the server, etc).
Good question! I *think* time
On Mon, Jul 8 2024 at 11:31:20 AM -05:00:00, Michel Lind
wrote:
Do the metrics really need to be kept separate?
I think so. Fedora Workstation is a completely different product from
Fedora KDE Plasma Desktop. We surely don't want to consider other
Fedora variants when making decisions that a
On Mon, Jul 8 2024 at 09:03:50 AM -04:00:00, Neal Gompa
wrote:
My biggest issue with this is that it's only useful for Fedora
Workstation. As it is currently designed, nobody else can benefit from
it. I would have preferred a design that allows all Fedora variants to
be able to offer this so tha
On Sun, Jul 7 2024 at 10:49:36 PM +02:00:00, Marc Deop i Argemí
wrote:
Let's say "possibly" instead of "probably". Regardless, that is a
very weak
argument. The fact that some information might be leaked while
browsing the
web has absolutely no weight on whether I would like to see even
*more*
On Sun, Jul 7 2024 at 03:43:15 AM +00:00:00, Gary Buhrmaster
wrote:
Do you have a proposed wording for the
question that does not, itself, exhibit any
bias?
We don't have proposed wording yet. We should of course be reasonable
and not write something misleading, but I think the question shoul
Hi, please see:
https://fedoraproject.org/wiki/Changes/Metrics#Who_will_have_access_to_metrics_data
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
On Wed, Jul 3 2024 at 09:32:45 AM +02:00:00, Vitaly Zaitsev via devel
wrote:
The apps should dlopen() it and if this library is not installed they
will be able to disable all telemetry functionality.
dlopen is the best option for this.
It's possible, but that's annoying. There is really no
On Tue, Jul 2 2024 at 07:14:46 PM +02:00:00, Vitaly Zaitsev via devel
wrote:
Please use a weak dependency on eos-metrics to allow its removal too.
But it's a library that applications will link to, so this won't work.
See my answer on Discourse:
https://discussion.fedoraproject.org/t/f42-ch
Added links:
https://fedoraproject.org/wiki/Changes/Metrics#Metrics_system_components
One more thing: the eos-metrics-instrumentation project is going to
need a lot of work. The change proposal envisions only collecting
metrics that are approved by Fedora, and many of those metrics probably
won
On Tue, Jul 2 2024 at 11:04:25 AM -04:00:00, Stephen Smoogen
wrote:
I don't see where this open source code is mentioned in the proposal
or the FAQ or the other notes. The wording of the documents led me to
believe the code was going to be written in the future. Could that be
added so people
Well the entire metrics system is open source, so I'd encourage
interested developers to study how it works. The database is just not
structured to associate unrelated data points together. We are not
interested in doing that.
There are some things we need to fix before deployment, though. E
On Tue, Jul 2 2024 at 04:05:11 PM +02:00:00, Ralf Corsépius
wrote:
Is this the same cheat as with Fedora's "installation ids" and
Firefox's
"phone home" features?
This stuff is activated by default, which means at the point a user
deactivates them, he already is "collected".
This metrics sys
On Tue, Jul 2 2024 at 12:04:48 PM +02:00:00, Vitaly Zaitsev via devel
wrote:
Because Red Hat is based in the US. It can be used against users from
countries and regions that the US does not like (e.g. sanctions,
export
policies, etc.).
Please remember the data collected will be anonymous and
On Sun, May 26 2024 at 08:13:52 AM +00:00:00, Byoungchan Lee via devel
wrote:
From what I understand, even with noopenh264, Chromium and WebRTC's
codebase will still need modification to use Fedora's OpenH264 or
noopenh264 package.
What do you think?
I'm not familiar with Chromium or libwebrt
On Sun, May 26 2024 at 06:09:06 AM +00:00:00, Mattia Verga via devel
wrote:
I see you have created noopenh264 just for wrapping openh264, would
it worth to use ffms2 (which wraps more codecs) instead?
The two things we care about are gstreamer1-plugin-openh264 and
mozilla-openh264, neither of
On Sat, May 25 2024 at 12:55:05 PM +00:00:00, Byoungchan Lee via devel
wrote:
Is my understanding correct?
Yes!
That said, we're considering adding the Firefox plugin as well [1] so
we can finally make Firefox support OpenH264 without requiring user
intervention [2].
[1] https://gitlab
Hi,
The link to Sumantro's interview is wrong here:
https://fedoraproject.org/wiki/Council/Nominations#Candidate_Nominations
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.or
On Wed, May 15 2024 at 08:52:28 AM +00:00:00, Ian McInerney via devel
wrote:
What if I don't use GNOME search? I don't use the GNOME desktop, so I
don't want to have a random Firefox process running on my machine
that is doing absolutely nothing and just hogging resources. Is this
process only
On Mon, May 13 2024 at 08:50:04 PM +02:00:00, Fabio Valentini
wrote:
Just out of curiosity, would glycin be a better mechanism than
gdk-pixbuf for loading "untrusted" images / "unsafe" image formats?
Its loaders are sandboxed via SECCOMP and support for most image
formats is implemented in Rust
Hi,
gdk-pixbuf 2.42.11 has dropped support for several uncommon image
formats. This is causing several applications to crash in Fedora
rawhide [1][2]. (The change also got backported to F40 and F39, but
I've reverted it there.)
Benjamin Gilbert has proposed reenabling the removed loaders [3]
On Fri, Apr 19 2024 at 11:11:33 AM -07:00:00, Kevin Fenzi
wrote:
There are none. This proposal was withdrawn.
It may be adjusted and submitted for consideration again, but that has
not yet happened.
Well, yes, but I'm planning to do this soonish.
--
__
On Thu, Apr 18 2024 at 05:53:14 PM +00:00:00, Igor Kerstges
wrote:
How much data is to be expected to be sent over my dataplan on
monthly basis? When using Fedora Workstations as a graphics
workstation (including regular office applications) during office
hours and extensive internet research
On Tue, Apr 2 2024 at 06:18:31 PM -07:00:00, Adam Williamson
wrote:
I mean, we really don't need to speculate about this much. We did an
entire overhaul of the project - Fedora.next - which was explicitly
based around making it much more focused and less of a
choose-your-own-
adventure, spe
On Mon, Apr 1 2024 at 10:25:16 AM -07:00:00, Adam Williamson
wrote:
Oh, ISWYM. Well, I suppose yes, that does happen to be true. We could
communicate that if it's done very carefully and made really clear
that
it's about the *time frame*, nothing to do with the repositories.
It's been brough
On Mon, Apr 1 2024 at 10:12:55 AM -07:00:00, Adam Williamson
wrote:
This is not really correct, or at least at all relevant. The bug
wasn't
in F40 Beta simply because the update never made it to 'stable'. Only
'stable' packages go into *composes*. However, saying that is not
really useful becau
On Sun, Mar 31 2024 at 06:52:53 PM +00:00:00, Christopher Klooz
wrote:
"Fedora Linux 40 branched users (i.e. pre-Beta) likely received the
potentially vulnerable 5.6.0-2.fc40 build if the system updated
between March 2nd and March 6th. Fedora Linux 40 Beta users only
using stable repositories
On Sun, Mar 31 2024 at 09:56:04 AM -05:00:00, Michael Catanzaro
wrote:
I'm really frustrated with our communication regarding this issue.
Does anybody know who can fix this?
The Fedora Magazine article has been fixed (thanks!).
--
___
devel ma
On Sun, Mar 31 2024 at 07:15:42 AM -04:00:00, Neal Gompa
wrote:
Well, an easy solution is to make it so "dnf update" is coerced to
"dnf distro-sync" for development releases. Then it doesn't matter. We
could make that happen for Fedora 41 with the DNF 5 transition
(there's already code to make t
On Sun, Mar 31 2024 at 12:55:23 PM +00:00:00, Christopher Klooz
wrote:
In case someone from the Fedora Magazine is in the devel mailing list
and reads this:
I'm really frustrated with our communication regarding this issue. Does
anybody know who can fix this?
If we don't know who can fix Fe
On Sat, Mar 30 2024 at 02:55:21 PM +00:00:00, Zbigniew
Jędrzejewski-Szmek wrote:
CMake for many years fought against pkgconf and pushed people towards
copying those scripts into sources. It is still very common for
projects
using CMake to come with a whole directory of badly written detection
On Sat, Mar 30 2024 at 09:45:06 AM -05:00:00, Michael Catanzaro
wrote:
No, that is not correct, as explained by [1] and [2].
I pasted the wrong link for [2]. I meant to paste:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/GRMSYVY6AM7OZBGQCQWIKRAF7DEMOKJM
On Sat, Mar 30 2024 at 12:26:48 PM +00:00:00, Christopher Klooz
wrote:
If I got Rich right, the malicious code is likely to be broken on
F40,
No, that is not correct, as explained by [1] and [2]. We have already
asked Red Hat to investigate and fix the blog post. This is still an
evolving s
On Sat, Mar 30 2024 at 09:37:44 AM +00:00:00, Richard W.M. Jones
wrote:
In the xz case this wouldn't have been enough, it turns out we would
also have to delete m4/build-to-host.m4, which then autoreconf
regenerates. I don't fully understand why that is.
I agree that running autoreconf on our
On Fri, Mar 29 2024 at 04:10:53 PM -05:00:00, Michael Catanzaro
wrote:
OK, I am going to ask Product Security to edit their blog post to
remove the incorrect information. I will CC you on that request.
Or maybe I should rephrase this as a "request for clarification,"
because maybe
On Fri, Mar 29 2024 at 08:16:55 PM +00:00:00, Richard W.M. Jones
wrote:
These are the exact builds which were vulnerable. Note the tags are
all empty because Kevin untagged them last night, so you'll probably
need to cross-reference these with bodhi updates.
OK, I am going to ask Product Secu
On Fri, Mar 29 2024 at 07:44:12 PM +01:00:00, Mikel Olasagasti
wrote:
Do we know if GH release tarballs are safe?
The tarballs generated by GitHub that just include the contents of the
git repo should be safe (at least from this particular issue), but the
Fedora package is not built from tho
On Fri, Mar 29 2024 at 07:56:49 PM +00:00:00, Richard W.M. Jones
wrote:
secalert are already well aware and have approved the update. Kevin
Fenzi, myself and others were working on it late last night :-(
Sorry, I linked to the wrong article. I meant to link to [1] which says
that "At this ti
On Fri, Mar 29 2024 at 06:46:59 PM +00:00:00, Christopher Klooz
wrote:
Yes, F40 beta is affected, along with rawhide, but not F38/F39.
Unless I'm misunderstanding something, it looks xz-5.6.0-1.fc40 and
5.6.0-2.fc40 are backdoored, yes? Then rjones unknowingly broke the
backdoor in two diffe
On Fri, Mar 22 2024 at 02:44:33 PM +01:00:00, Kevin Kofler via devel
wrote:
Once concern I have with this is the use of LGPL 3.0 *only*. This
will not
be compatible with a GPL 4 or newer. (The upgrade clause in the
LGPLv2 that
allowed that was unfortunately dropped in the LGPLv3, now you have t
On Wed, Feb 21 2024 at 05:38:00 PM +01:00:00, Jun Aruga (he / him)
wrote:
ImportError: /lib64/libdnf.so.2: undefined symbol:
g_once_init_enter_pointer
https://bugzilla.redhat.com/show_bug.cgi?id=2265336
This means dnf was built against a newer version of glib than is
available at runtime. Li
On Wed, Feb 14 2024 at 09:38:39 PM +00:00:00, Sérgio Basto
wrote:
I found "cc1plus: out of memory allocating 603 bytes after a total
of 86921216 bytes"
Thanks. This was a big help.
--
___
devel mailing list -- devel@lists.fedoraproject.org
To u
I checked the build log for
https://koji.fedoraproject.org/koji/taskinfo?taskID=113473592 but
unfortunately I don't actually see any error message. I searched for
"error:" (indicating a compiler error) and I also searched for "Killed"
(indicating OOM).
No doubt something is wrong somewhere
Hi,
If you're interested in name resolution or mDNS, please review this bug
report:
Default authselect profiles break `hostname --fqdn`
https://bugzilla.redhat.com/show_bug.cgi?id=2257197
We are looking for feedback on whether to move nss-myhostname, and
possibly also nss-mdns4_minimal.
I
On Wed, Jan 31 2024 at 06:53:25 PM +01:00:00, Milan Crha
wrote:
Evo itself doesn't use any seccomp or such, these things can be used
by
the WebKitGTK. A quick grep revealed:
https://github.com/WebKit/WebKit/blob/main/Source/WebKit/UIProcess/Launcher/glib/ProcessLauncherGLib.cpp#L258
but that
On Wed, Jan 31 2024 at 04:42:08 PM +01:00:00, Clemens Lang
wrote:
Throwing some ideas out there, is it possible that evolution runs
with a seccomp filter or other BPF program configured to kill the
process on violation, and that’s what’s happening here?
I don't think so. flatpak does use secc
SIGKILL is almost always sent by systemd-oomd (or the kernel OOM
killer). That's the most likely explanation. Theoretically it could
also be sent by systemd if a service didn't quit quickly enough
following a SIGTERM. Maybe it could also be sent by mutter if a program
is unresponsive?
WebKitG
Thank you!
--
___
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://fe
Unfortunately this is causing gating tests to fail for rawhide builds,
e.g.:
https://artifacts.dev.testing-farm.io/081ad2a3-76cd-4aa0-b95e-e870ff75a65c/
Hardened: /usr/bin/pkcon: FAIL: cf-protection test because
.note.gnu.property section did not contain the necessary flags
I'm not sure wh
On Wed, Dec 20 2023 at 04:33:22 PM +01:00:00, Vojtěch Polášek
wrote:
Is it possible to somehow insert a different string in the dconf file
depending on locale of the environment where the package is installed?
So first of all, dconf overrides are for system administrators, not
distro packager
On Mon, Dec 18 2023 at 01:17:43 PM -05:00:00, Steve Grubb
wrote:
So, what should I do to remove the patch? Do I push the new release
into
rawhide without the patch or does this need to go through the Fedora
Change
Process? And if so, self-contained or system wide?
Just remove it in rawhide.
On Tue, Nov 14 2023 at 08:16:39 AM -0500, Christopher
wrote:
I think for the sake of security, it'd be better if this were on by
default, and you just had to specify the --nogpgcheck
For convenience, the error message should probably say "Error: GPG
check FAILED (try again with '--nogpgcheck' to
1 - 100 of 1042 matches
Mail list logo
