Ray,<div><br></div><div>Is the debug logged saved somewhere ? Because with my setup copying it from the console is going to be tedious...</div><div><br></div><div>++<br><br><div class="gmail_quote">On Sun, Sep 26, 2010 at 10:36 PM, Jerome Martin <span dir="ltr"><<a href="mailto:tramjoe.merin@gmail.com">tramjoe.merin@gmail.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br><br><div class="gmail_quote"><div class="im">On Sun, Sep 26, 2010 at 10:29 PM, Ray Strode <span dir="ltr"><<a href="mailto:halfline@gmail.com" target="_blank">halfline@gmail.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Hi,<br> <div><br> On Sun, Sep 26, 2010 at 3:40 PM, Jerome Martin <<a href="mailto:tramjoe.merin@gmail.com" target="_blank">tramjoe.merin@gmail.com</a>> wrote:<br> <br> > 1) I upgraded to git version, still no luck with the keyboard messup with<br> > init (from sysvinit debian squeeze) when it starts the rc2.d after rcS<br> > execution.<br> </div>Can you post a log booted with plymouth:debug ?<br></blockquote><div><br></div></div><div>Mmmh, I'll try to get that setup back online and do that ASAP.</div><div class="im"><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br> [..snip..]<br> <div>> And the patches themselves in attached file...<br> </div>Most of these changes are script specific, so I'll leave this stuff<br> for Charlie to respond to.<br></blockquote><div><br></div></div><div>OK.</div><div class="im"><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div><br> > the current git version certainly deserves a<br> > proper release and some documentation though ...<br> </div>Right, I was going to do some logging changes before doing a 0.8.4<br> release, but maybe i'll do those changes after the release.<br> <br> Documentation is something very much lacking in plymouth. I want to<br> rectify that before 1.0.<br></blockquote><div><br></div></div><div><nod></div><div class="im"><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div><br> > 5) As a sidenote, I did a quick debian packaging of the git version, but had<br> > to adapt a bit the debian package rules from squeeze because it assumed that<br> > plymouth original sources already had autoconf ran there, when those that I<br> > downloaded had an autogen.sh script ... This is weird, and it is either an<br> > unclean package in debian OR the fact that you released last time with<br> > autogen.sh already ran. Is that the case ?<br> </div>the autogoo model is a little weird here. The version of the source<br> in the tarball contains generated files that aren't checked into<br> version control. When making a release, I do<br> <br> "make distcheck"<br> <br> which creates the tarball and adds the generated files to the tarball.<br> If you're just building a snapshot you can do:<br> <br> "make dist"<br> <br> which does the same thing but skips a bunch of checks and a test<br> compile that take a lot of time.<br></blockquote><div><br></div></div><div>Mmmhh. But against which makefile ? You need to generate it first don't you ?</div><div>So the release from git tree would be ./autogen.sh; ./configure OPTIONS and then your make distcheck ?</div> <div> </div></div>Best,<div>-- <br>Jérôme Martin<br> </div> </blockquote></div><br><br clear="all"><br>-- <br>Jérôme Martin<br> </div>