Re: unstable: directory pulse in root directory : /pulse where from?

2019-12-17 Thread Jörg-Volker Peetz
Stephan Seitz wrote on 16/12/2019 20:50: > On Mo, Dez 16, 2019 at 08:32:01 +0100, Jörg-Volker Peetz wrote: >> Does anybody else see such a /pulse directory? > > Yes, here as well (two testing systems). > > Shade and sweet water! > > Stephan > Thanks for confirming this. Are you using

Re: unstable: directory pulse in root directory : /pulse where from?

2019-12-17 Thread Jörg-Volker Peetz
Jörg-Volker Peetz wrote on 16/12/2019 20:32: > Greg Wooledge wrote on 16/12/2019 17:29: >> On Sat, Dec 14, 2019 at 10:04:34AM +0100, Jörg-Volker Peetz wrote: >>> $ dpkg -S /pulse >>> dpkg-query: no path found matching pattern /pulse >>> >>> fails to give any clue. >>> The directory is generated at

Re: unstable: directory pulse in root directory : /pulse where from?

2019-12-16 Thread Cindy Sue Causey
On 12/14/19, Andrei POPESCU wrote: > On Sb, 14 dec 19, 10:04:34, Jörg-Volker Peetz wrote: >> Brian wrote on 13/12/2019 21:29: >> > On Fri 13 Dec 2019 at 20:26:32 +0100, Jörg-Volker Peetz wrote: >> >> >> >> does anybody know which package generates the directory /pulse ? This >> >> is a bug >> >>

Re: unstable: directory pulse in root directory : /pulse where from?

2019-12-16 Thread Stephan Seitz
On Mo, Dez 16, 2019 at 08:32:01 +0100, Jörg-Volker Peetz wrote: Does anybody else see such a /pulse directory? Yes, here as well (two testing systems). Shade and sweet water! Stephan -- |If your life was a horse, you'd have to shoot it.|

Re: unstable: directory pulse in root directory : /pulse where from?

2019-12-16 Thread Jörg-Volker Peetz
Greg Wooledge wrote on 16/12/2019 17:29: > On Sat, Dec 14, 2019 at 10:04:34AM +0100, Jörg-Volker Peetz wrote: >> $ dpkg -S /pulse >> dpkg-query: no path found matching pattern /pulse >> >> fails to give any clue. >> The directory is generated at boot-time. But I wasn't able to find any hint >> in

Re: unstable: directory pulse in root directory : /pulse where from?

2019-12-16 Thread Greg Wooledge
On Sat, Dec 14, 2019 at 10:04:34AM +0100, Jörg-Volker Peetz wrote: > $ dpkg -S /pulse > dpkg-query: no path found matching pattern /pulse > > fails to give any clue. > The directory is generated at boot-time. But I wasn't able to find any hint in > systemd or udev conf-files. Well, the first

Re: unstable: directory pulse in root directory : /pulse where from?

2019-12-14 Thread Brian
On Sat 14 Dec 2019 at 10:04:34 +0100, Jörg-Volker Peetz wrote: > Brian wrote on 13/12/2019 21:29: > > On Fri 13 Dec 2019 at 20:26:32 +0100, Jörg-Volker Peetz wrote: > > > >> Hello, > >> > >> does anybody know which package generates the directory /pulse ? This is a > >> bug > >> in unstable I

Re: unstable: directory pulse in root directory : /pulse where from?

2019-12-14 Thread Andrei POPESCU
On Sb, 14 dec 19, 10:04:34, Jörg-Volker Peetz wrote: > Brian wrote on 13/12/2019 21:29: > > On Fri 13 Dec 2019 at 20:26:32 +0100, Jörg-Volker Peetz wrote: > >> > >> does anybody know which package generates the directory /pulse ? This is a > >> bug > >> in unstable I think, but I can't find which

Re: unstable: directory pulse in root directory : /pulse where from?

2019-12-14 Thread Jörg-Volker Peetz
Brian wrote on 13/12/2019 21:29: > On Fri 13 Dec 2019 at 20:26:32 +0100, Jörg-Volker Peetz wrote: > >> Hello, >> >> does anybody know which package generates the directory /pulse ? This is a >> bug >> in unstable I think, but I can't find which package is the culprit. > >

Re: unstable: directory pulse in root directory : /pulse where from?

2019-12-13 Thread Brian
On Fri 13 Dec 2019 at 20:26:32 +0100, Jörg-Volker Peetz wrote: > Hello, > > does anybody know which package generates the directory /pulse ? This is a bug > in unstable I think, but I can't find which package is the culprit. https://www.debian.org/distrib/packages -- Brian.

unstable: directory pulse in root directory : /pulse where from?

2019-12-13 Thread Jörg-Volker Peetz
Hello, does anybody know which package generates the directory /pulse ? This is a bug in unstable I think, but I can't find which package is the culprit. Regards, Jörg.