[Zack Weinberg]
> I would rather you did not, as I have almost completed packaging
> work on the new upstream release; I just need to find the time to
> finish testing it. This should happen in no more than a week.
> Thanks for the updated patch though, I will probably use it.
Great to hear. I e
I would rather you did not, as I have almost completed packaging work
on the new upstream release; I just need to find the time to finish
testing it. This should happen in no more than a week. Thanks for
the updated patch though, I will probably use it.
zw
On Thu, Oct 1, 2009 at 12:09 PM, Pett
Here is a more complete patch, to help you get the fix into unstable.
Please let us know if we should not NMU to fix it. :)
diff -ur ../monotone-0.44/debian/monotone-server.monotone.init
../monotone-0.44-pere/debian/monotone-server.monotone.init
--- ../monotone-0.44/debian/monotone-server.monoton
[Zack Weinberg]
> I don't know how to do this; can you point me at instructions?
I can point to you an example. In the latest upload of the lprng
package, I added code like this before the #DEBHELPER# marker to
detect the incorrect setup and remove the broken configuration (before
the correct one
On Tue, Aug 18, 2009 at 1:06 PM, Petter Reinholdtsen wrote:
>
> With dependency based boot sequencing, I discovered what I believe is
> a bug in the init.d script.
Thanks for this bug report. I am going to fix it in the next upload,
but I could use a little help. I've merged your changes to the
Package: monotone-server
Version: 0.43-1
Severity: important
Tags: patch
User: initscripts-ng-de...@lists.alioth.debian.org
Usertags: incorrect-runlevels incorrect-dependency
With dependency based boot sequencing, I discovered what I believe is
a bug in the init.d script. The provides
6 matches
Mail list logo
