On Friday, December 23, 2022 1:34:48 PM EST Alexander Ploumistos wrote:
> On Fri, Dec 23, 2022 at 7:21 PM Steve Grubb wrote:
> > This is nice, but all I ever seen is a black screen and a spinning
> > circle. No text of any kind. If something were written to the console,
> > how do you see it?
>
The following Fedora EPEL 7 Security updates need testing:
Age URL
6 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-c57a51c195
rxvt-unicode-9.30-2.el7
2 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-8362ddfe7c
trafficserver-9.1.4-1.el7
The following builds
I've refreshed the packaging and fixed bugs.
https://src.fedoraproject.org/fork/adetiste/rpms/apt-cacher-ng :
-> this integrate and builds on Frédéric Pierret's fixes.
https://copr.fedorainfracloud.org/coprs/adetiste/apt-cacher-ng/build/5178188/
(I need it for RHEL 8, so I'll need to backport
> So you can do
> $ eval `rpm -E '%set_build_flags'`
> in a script to set the flags that RPM uses.
Another solution could be something like:
$ gcc $(rpm -E '%optflags') ... $(rpm -E '%build_ldflags')
A.FI.
___
devel mailing list --
On Fri, Dec 23, 2022 at 1:21 PM Vít Ondruch wrote:
>
> Working with upstream on one issue [1], it seems that the culprit is in
> the Fedora compiler options. Is there some convenient way to set them
> up? Of course I can copy them from log, or somehow put together from the
> RPM macros, but I'd
On Fri, Dec 23, 2022 at 7:21 PM Steve Grubb wrote:
>
> This is nice, but all I ever seen is a black screen and a spinning circle. No
> text of any kind. If something were written to the console, how do you see
> it?
Have you tried hitting "Esc" when that happens?
Working with upstream on one issue [1], it seems that the culprit is in
the Fedora compiler options. Is there some convenient way to set them
up? Of course I can copy them from log, or somehow put together from the
RPM macros, but I'd appreciate if there was some easier way. Can we e.g.
Hello,
On Friday, December 23, 2022 9:48:22 AM EST Zbigniew Jędrzejewski-Szmek
wrote:
> On Fri, Dec 23, 2022 at 08:09:56AM +0100, Tomasz Torcz wrote:
> > On Thu, Dec 22, 2022 at 05:22:09PM -0500, Steve Grubb wrote:
> > > On Thursday, December 22, 2022 1:29:29 PM EST Adam Williamson wrote:
> > >
On Fri, Dec 23, 2022, at 12:56 AM, Demi Marie Obenour wrote:
> Why cache mode unsafe? How big a performance win is it?
Huge. In effect fsync is ignored. So if the host dies, write order is not
guaranteed and can toast the guest file system.
The guest dying shouldn't pose a problem because
Hello,
On Friday, December 23, 2022 6:52:02 AM EST Tom Hughes via devel wrote:
> On 23/12/2022 11:45, Naheem Zaffar wrote:
> > On Fri, 23 Dec 2022 at 08:26, Vitaly Zaitsev via devel
> > mailto:devel@lists.fedoraproject.org>>
> > wrote:
> > On 23/12/2022 09:20, Mattia Verga via devel wrote:
if you have persistent Journaling enabled, you'll find them in your last
boot log
On Fri, Dec 23, 2022, 08:55 Mattia Verga via devel <
devel@lists.fedoraproject.org> wrote:
> Il 23/12/22 15:48, Zbigniew Jędrzejewski-Szmek ha scritto:
> >
> > Yeah. We added printing of a lot of information in
> >
Il 23/12/22 15:48, Zbigniew Jędrzejewski-Szmek ha scritto:
>
> Yeah. We added printing of a lot of information in
> https://github.com/systemd/systemd/commit/3889fc6fc347f0e12070f7b873d065508c8df816:
>
> Example output:
>
> Stopping user@1000.service...
> [ OK ] Stopped
Hi
I'll be landing tesseract 5.3.0 in rawhide, building it in the
f38-build-side-61405 side tag, along with the following dependent packages:
ffmpeg
gimagereader
mupdf
opencv
python-PyMuPDF
qpdfview
R-tesseract
zathura-pdf-mupdf
Thanks
Sandro
___
On Thu, Dec 22, 2022 at 12:35:54PM -0500, Ben Cotton wrote:
> https://fedoraproject.org/wiki/Changes/Shorter_Shutdown_Timer
>
> This document represents a proposed Change. As part of the Changes
> process, proposals are publicly announced in order to receive
> community feedback. This proposal
On Fri, Dec 23, 2022 at 08:09:56AM +0100, Tomasz Torcz wrote:
> On Thu, Dec 22, 2022 at 05:22:09PM -0500, Steve Grubb wrote:
> > On Thursday, December 22, 2022 1:29:29 PM EST Adam Williamson wrote:
> > > 15 seconds feels very aggressive to me. I can think of some cases, like
> > > libvirtd
On Thu, Dec 22, 2022 at 10:40:23PM +0100, allan2016--- via devel wrote:
> På Thu, 22 Dec 2022 10:29:29 -0800
> Adam Williamson skrev:
> > On Thu, 2022-12-22 at 18:44 +0100, Tomasz Torcz wrote:
> > > On Thu, Dec 22, 2022 at 12:35:54PM -0500, Ben Cotton wrote:
> > > >
On Do, 22.12.22 11:00, Neal Gompa (ngomp...@gmail.com) wrote:
> > OK, so what's left is exactly one issue you had: you tried to enroll 3
> > UEFI certs via mokutil and what exactly happened then? machine
> > bricked how precisely?
>
> The UEFI environment failed to import without reporting
On Fr, 23.12.22 08:51, Fedora Development ML (devel@lists.fedoraproject.org)
wrote:
> On 22/12/2022 21:29, Chris Murphy wrote:
> > This is a rare but real problem.
>
> I don't think so. Power outage is a very common problem in some countries.
>
> I still remember how unreliable FAT32 was in the
On Fr, 23.12.22 09:01, Fedora Development ML (devel@lists.fedoraproject.org)
wrote:
> On 22/12/2022 21:18, Chris Murphy wrote:
> > XBOOTLDR in practice needs to be FAT. I don't like it. But I like
> > it better than choosing batshit as the alternative, and having a
> > bunch of signed efifs
On Thu, 22 Dec 2022 at 10:24, Elizabeth K. Joseph
wrote:
> > This might not be as niche as you might think. I'm one of the
> > Linux kernel maintainers for s390. Many of us do the vast majority of
> > their development work natively on s390 systems via SSH from Fedora
> > laptops.
>
> I first
On 23/12/2022 11:45, Naheem Zaffar wrote:
On Fri, 23 Dec 2022 at 08:26, Vitaly Zaitsev via devel
mailto:devel@lists.fedoraproject.org>>
wrote:
On 23/12/2022 09:20, Mattia Verga via devel wrote:
> I know this is way harder, but the right approach would be having
a way
> to
On Fri, 23 Dec 2022 at 08:26, Vitaly Zaitsev via devel <
devel@lists.fedoraproject.org> wrote:
> On 23/12/2022 09:20, Mattia Verga via devel wrote:
> > I know this is way harder, but the right approach would be having a way
> > to tell systemd what processes can be killed and what other processes
OLD: Fedora-Rawhide-20221222.n.0
NEW: Fedora-Rawhide-20221223.n.0
= SUMMARY =
Added images:1
Dropped images: 0
Added packages: 3
Dropped packages:0
Upgraded packages: 71
Downgraded packages: 0
Size of added packages: 30.67 MiB
Size of dropped packages:0 B
> On Thu, Dec 22, 2022 at 12:42:38PM -0600, Dennis Gilmore wrote:
> Different architectures have different boot loaders. In particular, s390x and
> ppc64el are very different. The proposal is to add support for UKIs in grub2,
> so
> that we will cover UEFI and non-UEFI machines that use grub2.
> On 22/12/2022 21:29, Chris Murphy wrote:
>
> I don't think so. Power outage is a very common problem in some countries.
>
> I still remember how unreliable FAT32 was in the Windows 9x era. You
> needed to run a scandisk check after every power failure or pressing the
> reset button. And
> On 12/22/22 12:00, Luca Boccassi wrote:
>
> As Neal mentioned earlier, these mechanisms are often broken. Not only
> does some firmware wind up bricking the machine when they are used, they
> also may not support removing the key used to sign Windows. If the
> attacker can boot Windows and
Announcing the creation of a new nightly release validation test event
for Fedora 38 Rawhide 20221223.n.0. Please help run some tests for this
nightly compose if you have time. For more information on nightly
release validation testing, see:
https://fedoraproject.org/wiki
On 12/20/22 21:27, Simo Sorce wrote:
Finally, unless this proposal harms Fedora I do not see why oppose it.
If, as you fear, it won't work ... then it won't and we'll try
something else.
You do realize that the day that Lenovo started to sell it's hardware
with Fedora pre-installed ( as it
On 23/12/2022 09:20, Mattia Verga via devel wrote:
I know this is way harder, but the right approach would be having a way
to tell systemd what processes can be killed and what other processes
must not be forced off in any case, then display a user friendly message
which inform the user that the
Il 22/12/22 18:35, Ben Cotton ha scritto:
> https://fedoraproject.org/wiki/Changes/Shorter_Shutdown_Timer
>
I think this is not the right approach to solve the problem. Basically,
we're saying "I don't know what's going on, just pull the plug, I don't
care about data corruption", which is going to
On Thu, Dec 22, 2022 at 12:42:38PM -0600, Dennis Gilmore wrote:
> On Thu, Dec 22, 2022 at 5:25 AM Zbigniew Jędrzejewski-Szmek
> wrote:
> >
> > On Wed, Dec 21, 2022 at 11:56:32AM -0600, Dennis Gilmore via devel wrote:
> > > In my case, I have Network Manager config files included in my initrd
> >
On 22/12/2022 18:35, Ben Cotton wrote:
A downstream configuration change to reduce the systemd unit timeout
from 2 minutes to 15 seconds.
+1 for this change. I've already reduced this timeout both on my desktop
and laptop to even 10 seconds.
--
Sincerely,
Vitaly Zaitsev
On 22/12/2022 21:18, Chris Murphy wrote:
XBOOTLDR in practice needs to be FAT. I don't like it. But I like it better
than choosing batshit as the alternative, and having a bunch of signed efifs
drivers on the ESP per distro sounds like batshit to me. And not in the good
way.
I don't think
33 matches
Mail list logo
