On Wed, 2023-10-25 at 20:51 -0400, Jeffrey Walton wrote:
> On Wed, Oct 25, 2023 at 7:33 PM Adam Williamson
> wrote:
> >
> > On Wed, 2023-10-25 at 22:02 +, Zbigniew Jędrzejewski-Szmek wrote:
> > > On Fri, Oct 20, 2023 at 04:55:57PM -0700, Adam Williamson wrote:
> > > > 6. distribution - https:
On Wed, 2023-10-25 at 22:02 +, Zbigniew Jędrzejewski-Szmek wrote:
> On Fri, Oct 20, 2023 at 04:55:57PM -0700, Adam Williamson wrote:
> > 6. distribution - https://bugzilla.redhat.com/2242759 - NEW: anyone at
> > all to come up with a genius fix, otherwise we'll likely have to
> > document this
On Fri, Oct 20, 2023 at 04:55:57PM -0700, Adam Williamson wrote:
> 6. distribution - https://bugzilla.redhat.com/2242759 - NEW: anyone at
> all to come up with a genius fix, otherwise we'll likely have to
> document this
Happy to oblige ;--]
Zbyszek
___
On Fri, Oct 20, 2023, 16:56 Adam Williamson wrote:
> We're still kinda kicking around ideas for "fixing" this, but I think
> if push comes to shove, we'll wind up revoting or waiving it as not
> practically fixable.
How about something of the form of an ExecStartPre expression
(or script) that t
On Sat, Oct 21, 2023 at 4:08 PM Chris Adams wrote:
> Certainly - I was just looking for a more general solution to non-RTC
> systems going forward. Ideally, there could be something triggered by a
> lack of an RTC, but it looks like systemd path units cannot work based
> on a path (e.g. /dev/rtc
Once upon a time, Gary Buhrmaster said:
> Personally, I have been using systemd-timesyncd for
> quite some time on the vast majority of my systems
> and am quite satisfied with it, but I believe that
> changing from chrony to systemd-timesyncd was
> considered too big of a last minute change since
On Sat, Oct 21, 2023 at 8:12 AM Adam Williamson
wrote:
>
> On Sat, 2023-10-21 at 11:34 +0200, Tomasz Torcz wrote:
> > On Fri, Oct 20, 2023 at 08:40:43PM -0500, Chris Adams wrote:
> > > Once upon a time, Adam Williamson said:
> > > > 6. distribution - https://bugzilla.redhat.com/2242759 - NEW
> >
On Sat, 2023-10-21 at 11:34 +0200, Tomasz Torcz wrote:
> On Fri, Oct 20, 2023 at 08:40:43PM -0500, Chris Adams wrote:
> > Once upon a time, Adam Williamson said:
> > > 6. distribution - https://bugzilla.redhat.com/2242759 - NEW
> > > dnf system-upgrade fails on some RPi4 due to system boot date th
On Sat, Oct 21, 2023 at 9:35 AM Tomasz Torcz wrote:
> We already have systemd-timesyncd. On startup, it syncs the time to
> the mtime of:
> - /var/lib/systemd/timesync/clock file; or
> - /usr/lib/clock-epoch file; or
> - a time derived from the source tree at build time
>
> timesyncd is mention
On Fri, Oct 20, 2023 at 08:40:43PM -0500, Chris Adams wrote:
> Once upon a time, Adam Williamson said:
> > 6. distribution - https://bugzilla.redhat.com/2242759 - NEW
> > dnf system-upgrade fails on some RPi4 due to system boot date that pre-
> > dates gpg key
> >
> > We're still kinda kicking ar
Once upon a time, Adam Williamson said:
> 6. distribution - https://bugzilla.redhat.com/2242759 - NEW
> dnf system-upgrade fails on some RPi4 due to system boot date that pre-
> dates gpg key
>
> We're still kinda kicking around ideas for "fixing" this, but I think
> if push comes to shove, we'll
Hi folks! We're still trying to get F39 done, so time for another
status update...
Action summary
==
Accepted blockers
-
1. kexec-tools - https://bugzilla.redhat.com/2243068 - VERIFIED: releng
to push the fix stable
2. mutter - https://bugzilla.redhat.com/2241632 - A
Hi folks! We're still trying to get F39 done, so time for another
status update...
Action summary
==
Accepted blockers
-
1. curl - https://bugzilla.redhat.com/2243182 - ON_QA: QA to test and
karma https://bodhi.fedoraproject.org/updates/FEDORA-2023-0f8d1871d8
2. dist
Hi folks! We're into Final freeze, so it's time for a blocker status
mail. The current Final target date is 2023-10-17, meaning we'd need a
release candidate by, er, Monday, so get your skates on everyone :)
Action summary
==
Accepted blockers
-
1. anaconda - https://
14 matches
Mail list logo
