-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello Ola,
Ola Lundqvist wrote:
> Restarting rebootmgr.
> Stopping the reboot manager
> Starting the reboot manager
>
>
>> Seems like you have upgraded from an earlier release. I do not think
>> the reboot manager is here still.
Do you mean this reboot manager:
# ls /etc/init.d/rebootmgr -l
- -rwxr-xr-x 1 root root 1421 May 25 04:22 /etc/init.d/rebootmgr
It exist in all of my other machines too.
>> Then you must have this file as a symlink...
>
>> zircone:~# ls -l /usr/lib/util-vserver/util-vserver-vars
>> -rw-r--r-- 1 root root 4398 May 22 21:21
>> /usr/lib/util-vserver/util-vserver-vars
>> It would be nice if you could check if the
>> /usr/lib/util-vserver/util-vserver-vars is a file or symlink. If it
>> points wrong we have the answer there. But if it don't we have some
>> other issue. Possibly with just the sarge version and I must get
>> an update into the stable relase.
It is a normal file:
# ls -l /usr/lib/util-vserver/util-vserver-vars
- -rw-r--r-- 1 root root 4200 May 25 04:22
/usr/lib/util-vserver/util-vserver-vars
>> I can add backports to my own archive. That is not a problem but
>> users will not find it that easy. :)
True, does any better way that other package maintainers do?
I've looked at debian-policy, it mentioned:
_stable_
This is the current "released" version of Debian GNU/Linux.
Once the distribution is _stable_ only security fixes and other major
bug fixes are allowed. When changes are made to this distribution, the
release number is increased (for example: 2.2r1 becomes 2.2r2 then
2.2r3, etc).
Is this bug big enough for to put an fix into stable release?
Regards,
- -Andrew
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFC51ninQYz4bYlCYURAsM8AKDh+mlY/SxIc4awbLT5AV5u4DVAigCfWW1e
ufXg8XTNF1PzMqV+XrLm/8c=
=n92B
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
