Re: netatalk not on bookworm

2024-01-18 Thread Charles Curley
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: netatalk not on bookworm

2023-12-26 Thread john doe
On 12/26/23 21:13, Charles Curley wrote: On Fri, 22 Dec 2023 16:25:11 -0700 Charles Curley wrote: I was able to build from source per the instructions at https://netatalk.sourceforge.io/3.1/htmldocs/intro.html et seq., starting with "git clone https://github.com/Netatalk/netatalk.git;.

Re: netatalk not on bookworm

2023-12-26 Thread Charles Curley
On Fri, 22 Dec 2023 16:25:11 -0700 Charles Curley wrote: > I was able to build from source per the instructions at > https://netatalk.sourceforge.io/3.1/htmldocs/intro.html et seq., > starting with "git clone https://github.com/Netatalk/netatalk.git;. Well, that didn't work. I got two good

Re: netatalk not on bookworm

2023-12-22 Thread Jeffrey Walton
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: netatalk not on bookworm

2023-12-22 Thread Charles Curley
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

netatalk not on bookworm

2023-12-22 Thread Charles Curley
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