Hi Dann, Thanks for the reply but i am not sure i have the skills for maintaining an official Debian package. However, i will try to progress on that point and maybe in few months i will be able to be more involve in the systemimager-debian project (by systemimager-debian i mean all the Debian related task associated to SystemImager).
Actually, i took the time to summarize various points that should be checked and/or fixed (all these points need to be double-checked): - The configuration variable NET_BOOT_DEFAULT of systemimager is set by default to "net" and not "local" so systemimager_server_netbootmond fails when we try to install the package on a fresh Debian installation. - More generally, all the daemons (including systemimager_server_netbootmond) fails when we try to stop the daemon if the daemon is already stopped. It results in a lot of issues if the daemon is manually stopped and then the package removed/updated. Again, this is only few notes from my latest tests. These two points need to be investigated before to be considered as bugs. I will also try to have a look to the files related to the Debian package available in the SystemImager trunk. Thanks, Le lundi 8 octobre 2007 16:14, dann frazier a écrit : > On Sat, Oct 06, 2007 at 10:25:06PM +0200, [EMAIL PROTECTED] wrote: > > Hi Dann, > > > > I said few months ago that i will try to work on the Debian packages > > again, starting by the creation of a todo list. Unfortunately, i had to > > focus on some other stuff even if i have this list somewhere in my > > office. I am very sorry about that. > > > > I still want to work on the Debian version of SystemImager but at the > > same time, i am not an official Debian developer so it seems it will be > > difficult for me to become the official maintainer of the Debian > > packages. > > hey Geoffroy, > No problem. Actually, its quite easy to be a maintainer of a package > w/o being a debian developer - there's a process called sponsorship > that lets you do so. There's no requirement that you be a Debian > Developer in order to maintain a package, though it does help. > > However, maintaining (or at least, *properly maintaining*) > SystemImager packages is still a fairly timeconsuming job. Besides the > obvious work of keeping up with upstream changes, there's also > tracking the Debian kernel, dealing with toolchain compatability > issues (since SI compiles a significant amount of userspace), > architecture issues, and the one that always bit me: testing. > Team maintenance seems like a much better approach than expecting a > single person to handle all of this. Either way, I expect/hope that > any future contributions you make will be welcomed by the future > maintainer(s). -- Geoffroy ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ sisuite-devel mailing list sisuite-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-devel
