Re: Support for SysV service scripts deprecated in systemd 255 (was: systemd and timezone)

David Wright composed on 2023-12-23 00:00 (UTC-0600): > On Fri 22 Dec 2023 at 18:52:09 (-0500), Pocket wrote: >> From the email I got from Lennart >> CHANGES WITH 255: >>     Announcements of Future Feature Removals and Incompatible Changes: >>     * Support for split-usr (/usr/ mounte

Re: systemd and timezone

On Fri 22 Dec 2023 at 18:52:09 (-0500), Pocket wrote: > On 12/22/23 18:04, David Wright wrote: > > On Fri 22 Dec 2023 at 16:16:07 (-0500), Greg Wooledge wrote: > > > On Fri, Dec 22, 2023 at 08:59:42PM +0100, Sven Joachim wrote: > > > > 1. https://bugs.debian.org/803144 > > > > 2. https://bugs.debia

Re: systemd and timezone

On Fri 22 Dec 2023 at 14:54:13 (-0500), Greg Wooledge wrote: > On Fri, Dec 22, 2023 at 01:29:09PM -0600, David Wright wrote: > > With the proviso that I don't know what "restorecon" does in > > postinst scripts, this list of .debs has been prefixed by > > c for copy and l for link: > > > > l-tzd

Re: systemd and timezone

On Fri, Dec 22, 2023 at 06:36:55PM -0600, Nate Bargmann wrote: > In Debian releases between Etch and Jessie (inclusive), It's a wiki. I assumed it would be clear in context, due to the paragraphs before and after it, but if you want to change the wording, change it.

Re: systemd and timezone

* On 2023 22 Dec 15:34 -0600, Greg Wooledge wrote: > On Fri, Dec 22, 2023 at 08:59:42PM +0100, Sven Joachim wrote: > > 1. https://bugs.debian.org/803144 > > 2. https://bugs.debian.org/346342 > > Wow, OK. Fascinating historical context in there. > > I've updated

Re: systemd and timezone

On 12/22/23 18:04, David Wright wrote: On Fri 22 Dec 2023 at 16:16:07 (-0500), Greg Wooledge wrote: On Fri, Dec 22, 2023 at 08:59:42PM +0100, Sven Joachim wrote: 1. https://bugs.debian.org/803144 2. https://bugs.debian.org/346342 Wow, OK. Fascinating historical context in there. I've updat

Re: Clarification: public private replies [WAS Re: Formal reminder of Codes of Conduct]

cc. to commun...@debian.org because I'm explaining CT involvment. On Fri, Dec 22, 2023 at 12:47:51PM +, Andy Smith wrote: > Hello, > > On Thu, Dec 21, 2023 at 03:49:13PM -0800, David Christensen wrote: > > On 12/21/23 14:27, Andrew M.A. Cater wrote: > > > Posting well-intentioned private repl

Re: netatalk not on bookworm

On Fri, Dec 22, 2023 at 6:25 PM Charles Curley wrote: > > On Fri, 22 Dec 2023 12:39:21 -0700 > Charles Curley wrote: > > > On upgrading from bullseye to bookwork, my netatalk installation has > > been nuked. The bullseye package (3.1.12~ds-8+deb11u1) is still > > present but no daemon is running

Re: systemd and timezone

On 12/22/23 18:04, David Wright wrote: On Fri 22 Dec 2023 at 16:16:07 (-0500), Greg Wooledge wrote: On Fri, Dec 22, 2023 at 08:59:42PM +0100, Sven Joachim wrote: 1. https://bugs.debian.org/803144 2. https://bugs.debian.org/346342 Wow, OK. Fascinating historical context in there. I've updat

Re: netatalk not on bookworm

On Fri, 22 Dec 2023 12:39:21 -0700 Charles Curley wrote: > On upgrading from bullseye to bookwork, my netatalk installation has > been nuked. The bullseye package (3.1.12~ds-8+deb11u1) is still > present but no daemon is running nor is my Mac making backups to the > server. > > Is there a known

Re: systemd and timezone

On Fri 22 Dec 2023 at 16:16:07 (-0500), Greg Wooledge wrote: > On Fri, Dec 22, 2023 at 08:59:42PM +0100, Sven Joachim wrote: > > 1. https://bugs.debian.org/803144 > > 2. https://bugs.debian.org/346342 > > Wow, OK. Fascinating historical context in there. > > I've updated

Re: systemd and timezone

Jeffrey Walton (12023-12-22): > I've found lack of per-thread timezones and libc's inability to > convert time between timezones a bigger problem than other issues, > like explicitly setting a timezone for a process. Unix API makes an habit of this kind of thing. Often, it is because the feature w

Re: Test

On Fri, Dec 22, 2023 at 4:37 PM Pocket wrote: > > On 12/22/23 16:08, Tixy wrote: > > On Fri, 2023-12-22 at 12:15 -0500, Pocket wrote: > >> This is a test of the emergency broadcast system > > > > Please stop spamming the 1000 or so people subscribed to this list. > > I am not spamming this list I

Re: Test

Pocket writes: > On 12/22/23 16:08, Tixy wrote: >> On Fri, 2023-12-22 at 12:15 -0500, Pocket wrote: >>> This is a test of the emergency broadcast system >> Please stop spamming the 1000 or so people subscribed to this list. > > I am not spamming this list I am trying to determine if my email setu

Re: Test

On 12/22/23 16:08, Tixy wrote: On Fri, 2023-12-22 at 12:15 -0500, Pocket wrote: This is a test of the emergency broadcast system Please stop spamming the 1000 or so people subscribed to this list. I am not spamming this list I am trying to determine if my email setup is working.

Re: systemd and timezone

On Fri, Dec 22, 2023 at 08:59:42PM +0100, Sven Joachim wrote: > 1. https://bugs.debian.org/803144 > 2. https://bugs.debian.org/346342 Wow, OK. Fascinating historical context in there. I've updated . I believe it's correct now, for both current and histor

Re: Test

On Fri, Dec 22, 2023 at 4:08 PM Tixy wrote: > > On Fri, 2023-12-22 at 12:15 -0500, Pocket wrote: > > This is a test of the emergency broadcast system > > Please stop spamming the 1000 or so people subscribed to this list. Would forwarding his message to commun...@debian.org and asking for a one m

Re: Test

On Fri, 2023-12-22 at 12:15 -0500, Pocket wrote: > This is a test of the emergency broadcast system Please stop spamming the 1000 or so people subscribed to this list. -- Tixy

Re: systemd and timezone

On 2023-12-22 11:11 -0500, Greg Wooledge wrote: > On Fri, Dec 22, 2023 at 09:30:23AM -0600, David Wright wrote: >> https://wiki.debian.org/TimeZoneChanges >> >> still says: >> >> "In Debian releases Etch and later, /etc/localtime is a copy of the >> original data file. Check the contents of /

Re: systemd and timezone

On Fri, Dec 22, 2023 at 01:29:09PM -0600, David Wright wrote: > With the proviso that I don't know what "restorecon" does in > postinst scripts, this list of .debs has been prefixed by > c for copy and l for link: > > l-tzdata_2007b-1_all.deb > l-tzdata_2008e-1etch3_all.deb > c-tzdata_2011k-

Re: systemd and timezone

On Fri, Dec 22, 2023 at 8:33 AM wrote: > > On Fri, Dec 22, 2023 at 07:26:37PM +0700, Max Nikulin wrote: > > [...] > > /etc/localtime is a global setting. Its change may affect all users not > > having explicit TZ. Something better than libc is required for an > > application (especially multithre

Re: systemd and timezone

On Fri, Dec 22, 2023 at 07:56:56PM +0100, Arno Lehmann, ITS wrote: > I have Etch running here, and the /etc/localtime file is not a symlink, nor > a hardlink to a zone file: > > TomBombadil:~# ls -lhi /etc/timezone /etc/localtime > 159667 -rw-r--r-- 1 root root 842 2020-11-14 18:27 /etc/localtime

Re: systemd and timezone

On Fri 22 Dec 2023 at 11:11:18 (-0500), Greg Wooledge wrote: > On Fri, Dec 22, 2023 at 09:30:23AM -0600, David Wright wrote: > > https://wiki.debian.org/TimeZoneChanges > > > > still says: > > > > "In Debian releases Etch and later, /etc/localtime is a copy of the > > original data file. Che

netatalk not on bookworm

On upgrading from bullseye to bookwork, my netatalk installation has been nuked. The bullseye package (3.1.12~ds-8+deb11u1) is still present but no daemon is running nor is my Mac making backups to the server. Is there a known fix or workaround for this? -- Does anybody read signatures any more?

Re: systemd and timezone

Hi Greg, Am 22.12.2023 um 17:11 schrieb Greg Wooledge: On Fri, Dec 22, 2023 at 09:30:23AM -0600, David Wright wrote: https://wiki.debian.org/TimeZoneChanges still says: "In Debian releases Etch and later, /etc/localtime is a copy of the original data file. Check the contents of /etc/t

Test

This is a test of the emergency broadcast system

Re: systemd and timezone

On Fri, Dec 22, 2023 at 09:30:23AM -0600, David Wright wrote: > https://wiki.debian.org/TimeZoneChanges > > still says: > > "In Debian releases Etch and later, /etc/localtime is a copy of the > original data file. Check the contents of /etc/timezone to see the > name of the timezone. If th

Re: systemd and timezone

On Fri, Dec 22, 2023 at 08:55:04AM -0500, Greg Wooledge wrote: > On Fri, Dec 22, 2023 at 02:17:47PM +0100, to...@tuxteam.de wrote: > > whereas /etc/timezone [1] is just the > > global default for the (libc) applications to fall back to whenever they > > don't have specified one. > > > > [1] Or wha

Re: systemd and timezone

On Fri 22 Dec 2023 at 08:55:04 (-0500), Greg Wooledge wrote: > On Fri, Dec 22, 2023 at 02:17:47PM +0100, to...@tuxteam.de wrote: > > whereas /etc/timezone [1] is just the > > global default for the (libc) applications to fall back to whenever they > > don't have specified one. > > > > [1] Or whate

Re: Mouse single click handling?

On Thu, 21 Dec 2023, at 13:36, songbird wrote: > i've > already worn some of letters off the keys. :( but, well, i got > it on sale for about $30 so i really can't complain. For years I've used Dymo labels to replace keyboard legends. (Not the 1960s/1970s thick 3d labels, but 'printed' ones).

Re: systemd and timezone

On Fri, Dec 22, 2023 at 02:17:47PM +0100, to...@tuxteam.de wrote: > whereas /etc/timezone [1] is just the > global default for the (libc) applications to fall back to whenever they > don't have specified one. > > [1] Or whatever that thing may be called in systemd-land. Unless I'm gravely mistake

Re: GRUB -- Debian overrides? Or maybe I just don't understand it well...

Mark Fletcher composed on 2023-12-22 06:43 (UTC): > I have just discovered that I > had a typo in my custom.cfg file, and when I fixed it, it worked. :-D > Thanks all for your help with this. :-D -- Evolution as taught in public schools is, like religion, based on faith, not based on s

Re: systemd and timezone

On Fri, Dec 22, 2023 at 07:26:37PM +0700, Max Nikulin wrote: > On 21/12/2023 21:53, to...@tuxteam.de wrote: > > On Thu, Dec 21, 2023 at 09:08:09AM -0500, Dan Ritter wrote: > > > > > > And > > > it is quite possible on a few of those machines to have multiple > > > desktop users, each from a differ

Re: Clarification: public private replies [WAS Re: Formal reminder of Codes of Conduct]

Hello, On Thu, Dec 21, 2023 at 03:49:13PM -0800, David Christensen wrote: > On 12/21/23 14:27, Andrew M.A. Cater wrote: > > Posting well-intentioned private replies back to the list is not > > appropriate. > > Please clarify how the Debian Community Team wishes us to respond to the > following u

Re: systemd and timezone

Hello, On Thu, Dec 21, 2023 at 06:36:34PM -0600, Nicholas Geovanis wrote: > Servers work in groups and log-aggregation and analysis software is normal > in that context. And since your web server fleet, for one example, may be > spread across multiple timezones or multiple continents to reduce lat

Re: systemd and timezone

On 21/12/2023 21:53, to...@tuxteam.de wrote: On Thu, Dec 21, 2023 at 09:08:09AM -0500, Dan Ritter wrote: And it is quite possible on a few of those machines to have multiple desktop users, each from a different TZ. I've sometimes the impression that desktop environments are losing the concept

Re: GRUB -- Debian overrides? Or maybe I just don't understand it well...

On Fri, 22 Dec 2023 at 10:54, Mark Fletcher wrote: > > On Fri, 22 Dec 2023 at 07:41, Anssi Saari > wrote: > > > > Mark Fletcher writes > > > > > The question is, what values are config_directory and prefix set to? > > > > Grub sets config_directory to point to the directory where it's reading >

Re: GRUB -- Debian overrides? Or maybe I just don't understand it well...

On Fri, 22 Dec 2023 at 01:21, David Wright wrote: > > What sort of mess? I would have thought Grub would ignore excess > kernels dropped into /boot. I have a laptop here that has two > bookworm netinst ISOs (release candidates) and a kernel and initrd > (hd-media) for booting the ISOs, and they've

Re: GRUB -- Debian overrides? Or maybe I just don't understand it well...

On Fri, 22 Dec 2023 at 07:41, Anssi Saari wrote: > > Mark Fletcher writes > > > The question is, what values are config_directory and prefix set to? > > Grub sets config_directory to point to the directory where it's reading > it's config from. In other words, /boot. > > But why not just use 40_c

Re: Clarification: public private replies

I'm not Andrew, and can't answer for Andrew or for anyone on the Debian Community Team, but my take on this is: On 21 Dec 2023 15:49 -0800, from dpchr...@holgerdanske.com (David Christensen): > On 12/21/23 14:27, Andrew M.A. Cater wrote: >> Posting well-intentioned private replies back to the lis