Bug#832132: /etc/init.d/radicale start does not work

2018-05-16 Thread Karl Heisenberg
Hi,
the init.d script works after changing permissions.In my case I have solved by
chown -R radicale:adm /etc/radicale


BestRoberto

Bug#832132: /etc/init.d/radicale start does not work

2017-04-13 Thread Jonas Smedegaard
Quoting Slavko (2017-04-13 11:01:31)
> On Fri, 07 Apr 2017 23:27:36 +0200 Jonas Smedegaard  
> wrote:
> 
> > When you sidestep the init script then it is your responsibility to 
> > ensure that the environment is aligned with however you want to use 
> > the package.
> > 
> > This bugreport concerns the issue of init script provided as part of 
> > the package not working correctly - deliberately avoiding the init 
> > script is not this bug (and is not a bug at all).
> 
> I consider creating hardcoded logdir in initscript as bad idea,

Please discuss that at  - not here.

Please only post to this email address if you have something to 
contribute to _this_ bugreport: A regression of Radicale previously 
working but init script failing to work after a package update (or 
possible after enabling systemd).

For other issues/suggestions *not* related to _this_ bug, please file 
_separate_ bugreports.

Your input is appreciated - when not cluttering input of others :-)


Thanks,

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature


Bug#832132: /etc/init.d/radicale start does not work

2017-04-07 Thread Jonas Smedegaard
Hi Slavko,

Quoting Slavko (2017-04-07 20:18:13)
> On Mon, 1 Aug 2016 21:04:02 +0100 D McA  wrote:
> > I am also affected by this bug. I installed Radicale with apt-get 
> > and did not suppress any package recommendations.

> today i install stretch's radicale in virtualbox:
> 
> dpkg -l radicale
> ii  radicale  1.1.1+20160115-3
> 
> and because i want to play with config i run it from console (not as
> daemon) without any config change yet:
[...]
> And yes, there is missing /var/log/radicale/ directory. I am not sure, 
> if it is original poster problem too, but it seems as some small 
> packaging mistake, because there is a logrotate's config for radicale 
> to work with logs in this directory:

When you sidestep the init script then it is your responsibility to 
ensure that the environment is aligned with however you want to use the 
package.

This bugreport concerns the issue of init script provided as part of the 
package not working correctly - deliberately avoiding the init script is 
not this bug (and is not a bug at all).

Thanks for your input anyway.  Hope you got it working the way you 
wanted.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature


Bug#832132: /etc/init.d/radicale start does not work

2016-08-01 Thread D McA
I am also affected by this bug. I installed Radicale with apt-get and 
did not suppress any package recommendations.




Bug#832132: /etc/init.d/radicale start does not work

2016-07-23 Thread Stephen Paul Weber
> Did you edit /etc/radicale/config and /etc/default/radicale?

Yes. I enabled in the defaults (though in my experience with other packages 
since moving to jessie, systemd tends to ignore /etc/defaults in many of them). 
I am fairly certain this is a regression in my setup and that it used to start 
fine.

> Did you suppress some package recommendations on your system?

Possibly. Which would you suggest trying to install in this case?



Bug#832132: /etc/init.d/radicale start does not work

2016-07-23 Thread Jonas Smedegaard
Hi Stephen,

Quoting Stephen Paul Weber (2016-07-22 19:16:03)
> If I run `radicale -d` as root myself, it works fine.  But if I run 
> `/etc/init.d/radicale start` as root, it claims to be using a systemd 
> service file and then does nothing.  I cannot find said systemd 
> service file -- can it be that it was not created and so that is why 
> it is not starting?

Thanks for your bugreport!

Did you edit /etc/radicale/config and /etc/default/radicale?

Did you suppress some package recommendations on your system?


Regards,

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature


Bug#832132: /etc/init.d/radicale start does not work

2016-07-22 Thread Stephen Paul Weber

Package: radicale
Version: 0.9-1+deb8u1

If I run `radicale -d` as root myself, it works fine.  But if I run 
`/etc/init.d/radicale start` as root, it claims to be using a systemd 
service file and then does nothing.  I cannot find said systemd service file 
-- can it be that it was not created and so that is why it is not starting?


Thanks,

--
Stephen Paul Weber, @singpolyma
See  for how I prefer to be contacted
edition right joseph


signature.asc
Description: Digital signature