Hello On Mon, Aug 01, 2005 at 01:13:54PM +0800, Andrew Lee wrote: > > True, does any better way that other package maintainers do? > > > >> Either make sure it get to unstable/testing or if it is really serious > >> to stable. If we can debug this further and make good fix for it it > >> may be possible to get it to stable as well. > > Seems I should test it in testing an unstable, all my vserver machine > are running sarge.
If you want to have better features you have to wait until I have uploaded a fixed version of vserver-debiantools to unstable or you have to upgrade both vserver-debiantools and util-vserver to the ones in unstable. It can be a bit problematic. Expect a fix for that in the next few days. > > Is this bug big enough for to put an fix into stable release? > > > > > >> Possibly. But first we have to determine the exact cause of the failure. > > # dpkg -l vserver-debiantools > Desired=Unknown/Install/Remove/Purge/Hold > | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed > |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: > uppercase=bad) > ||/ Name Version Description > +++-==============-==============-============================================ > ii vserver-debian 0.1.10 Tools to manage debian virtual servers > > # grep util-vserver-vars /usr/sbin/newvserver > if [ -r /etc/vservers/util-vserver-vars ] ; then > . /etc/vservers/util-vserver-vars As I told you in the previous mail you should use the other configuration file instead. > > > >> Because the file util-vserver-vars should NOT be in /etc... It was > >> removed from there becuase it is changed to frequently (on every upgrade > >> actually) > >> and therefor it is not suitable to have there. > > > >> I'll see if I can reproduce it at my server, but if you have time to > >> debug it further that would be really great! > > I guess I found the problem but I am not sure, because not enough > information in the README.Debian to told me what should vserver works > like? I guess legacy method is not you expected. Legacy mode is what is expected in sarge. The other method was not tested enough to be allowed to go into stable. > All of my vserver are still running in lagacy method, I made them by > newvserver script after I copied the util-vserver-vars to /etc/vservers. This should not be a problem, but if you want to use the new method you have to use the new method. Regards, // Ola > - -Andrew > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.1 (GNU/Linux) > > iD8DBQFC7a+RnQYz4bYlCYURAmwTAJ9qgSsHg6Jssm2MICxd0i6Y3+yaEwCeMLm1 > 6GYRJySsJFJr4BdXYAWyClo= > =Lqo0 > -----END PGP SIGNATURE----- > > -- --------------------- Ola Lundqvist --------------------------- / [EMAIL PROTECTED] Annebergsslingan 37 \ | [EMAIL PROTECTED] 654 65 KARLSTAD | | +46 (0)54-10 14 30 +46 (0)70-332 1551 | | http://www.opal.dhs.org UIN/icq: 4912500 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --------------------------------------------------------------- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
