Bug#699148: unblock: celery/2.5.3-2

2013-03-01 Thread Christoph Egger
Hi! Michael Fladischer mich...@fladi.at writes: On 2013-02-28 21:27, Adam D. Barratt wrote: Any news on an upload? 2.5.3-3 is prepared in SVN but paravoid (my sponsor on celery) seems to be busy. Uploaded Christoph -- To UNSUBSCRIBE, email to

Bug#699148: unblock: celery/2.5.3-2

2013-03-01 Thread Faidon Liambotis
On Fri, Mar 01, 2013 at 12:13:06AM -0800, Christoph Egger wrote: Michael Fladischer mich...@fladi.at writes: On 2013-02-28 21:27, Adam D. Barratt wrote: Any news on an upload? 2.5.3-3 is prepared in SVN but paravoid (my sponsor on celery) seems to be busy. Uploaded JFYI, r23622 |

Bug#699148: unblock: celery/2.5.3-2

2013-03-01 Thread Julien Cristau
On Sat, Feb 9, 2013 at 10:35:50 +0100, Julien Cristau wrote: On Sat, Feb 9, 2013 at 08:17:44 +0100, Michael Fladischer wrote: Julien Cristau, 02/08/2013 10:48 PM: I guess that should be fine then, but your postrm doesn't seem to delete any logfiles? I'll add this to postrm prior

Bug#699148: unblock: celery/2.5.3-2

2013-03-01 Thread Michael Fladischer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-03-01 11:33, Julien Cristau wrote: Why is that in the if deluser exists block? Because without deluser the user/group would not be removed. So I decided to only remove the logfiles if the user/group are gone, so to to generate a scenario

Bug#699148: unblock: celery/2.5.3-2

2013-03-01 Thread Julien Cristau
On Fri, Mar 1, 2013 at 11:41:26 +0100, Michael Fladischer wrote: On 2013-03-01 11:33, Julien Cristau wrote: Why is that in the if deluser exists block? Because without deluser the user/group would not be removed. So I decided to only remove the logfiles if the user/group are gone, so to

Bug#699148: unblock: celery/2.5.3-2

2013-03-01 Thread Michael Fladischer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-03-01 11:43, Julien Cristau wrote: Removing log files on purge unconditionally doesn't generate such a scenario, so I'm not sure I understand what you're saying. My understanding was that it has to be insured that when a user is removed, I

Bug#699148: unblock: celery/2.5.3-2

2013-03-01 Thread Julien Cristau
On Fri, Mar 1, 2013 at 12:01:01 +0100, Michael Fladischer wrote: On 2013-03-01 11:43, Julien Cristau wrote: Removing log files on purge unconditionally doesn't generate such a scenario, so I'm not sure I understand what you're saying. My understanding was that it has to be insured that

Bug#699148: unblock: celery/2.5.3-2

2013-02-28 Thread Adam D. Barratt
On Sat, 2013-02-09 at 10:35 +0100, Julien Cristau wrote: On Sat, Feb 9, 2013 at 08:17:44 +0100, Michael Fladischer wrote: Also, /usr/share/pyshared/celery as home dir for the user seems kind of weird... Would /var/lib/celery be a better choice? I would be emptpy though. I think

Bug#699148: unblock: celery/2.5.3-2

2013-02-28 Thread Michael Fladischer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-02-28 21:27, Adam D. Barratt wrote: Any news on an upload? 2.5.3-3 is prepared in SVN but paravoid (my sponsor on celery) seems to be busy. Cheers, - -- Michael Fladischer Fladi.at -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12

Bug#699148: unblock: celery/2.5.3-2

2013-02-09 Thread Julien Cristau
On Sat, Feb 9, 2013 at 08:17:44 +0100, Michael Fladischer wrote: Julien Cristau, 02/08/2013 10:48 PM: I guess that should be fine then, but your postrm doesn't seem to delete any logfiles? I'll add this to postrm prior to deleting the user. A `rm -rf /var/log/celery` should be fine I

Bug#699148: unblock: celery/2.5.3-2

2013-02-08 Thread Michael Fladischer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Julien Cristau, 01/30/2013 09:57 PM: How do you make sure no file owned by that user remains on the system? (If you don't, then don't remove the user, it doesn't hurt to keep it around) Thanks for your feedback. The package does not create any

Bug#699148: unblock: celery/2.5.3-2

2013-02-08 Thread Julien Cristau
On Fri, Feb 8, 2013 at 18:49:28 +0100, Michael Fladischer wrote: Julien Cristau, 01/30/2013 09:57 PM: How do you make sure no file owned by that user remains on the system? (If you don't, then don't remove the user, it doesn't hurt to keep it around) Thanks for your feedback. The

Bug#699148: unblock: celery/2.5.3-2

2013-02-08 Thread Michael Fladischer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Julien Cristau, 02/08/2013 10:48 PM: I guess that should be fine then, but your postrm doesn't seem to delete any logfiles? I'll add this to postrm prior to deleting the user. A `rm -rf /var/log/celery` should be fine I guess. Also,

Bug#699148: unblock: celery/2.5.3-2

2013-01-30 Thread Julien Cristau
Control: tag -1 moreinfo On Mon, Jan 28, 2013 at 07:57:36 +0100, Michael Fladischer wrote: diff -Nru celery-2.5.3/debian/python-celery.postrm celery-2.5.3/debian/python-celery.postrm --- celery-2.5.3/debian/python-celery.postrm 1970-01-01 01:00:00.0 +0100 +++

Bug#699148: unblock: celery/2.5.3-2

2013-01-27 Thread Michael Fladischer
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Please unblock package celery 2.5.3-2 fixes #697195 (RC) which was caused by the user celery not being created in postinst. The attached