I suppose it is possible Zed. The configs aren't big the build log is though and that is where you see the error report.
Anyway I have fixed it now and installed a minimal Jessie MATE onto my little emachine netbook. Your suggestion about Github is excellent. My project is already on Github so I will use that next time. Cheers. On 5 October 2014 10:26, Zed <z...@lilypadmudlib.com> wrote: > Maybe copying and pasting has included some characters that are causing > issues (that are not exactly visible). I have comments all over the place > and they have not caused any issues (begging. Middle, and end of configs) > and I am running 4.0.1-1 and 4.0.2 without issues. I’d try to recreate the > config files maybe. > > Also, if your configs are so long, you could always put your project on > GitHub so we can see the configs and then you don’t have to worry about > length of messages. Just a thought. > > Z > > From: "Michael ." <keltoi...@gmail.com> > Date: Sun, 5 Oct 2014 08:58:01 +1100 > To: "debian-live@lists.debian.org" <debian-live@lists.debian.org> > Subject: Re: Failure to build Jessie with MATE > Resent-From: <debian-live@lists.debian.org> > Resent-Date: Sat, 4 Oct 2014 21:58:17 +0000 (UTC) > > That was the problem. I built an iso and am now about to test it to see if > it will install. > Why does Live Build no longer see comments at the beginning of a file? > > On 4 October 2014 21:35, Michael . <keltoi...@gmail.com> wrote: > >> I think I have just figured it out, only because of having to copy and >> paste configs over. >> My package lists are derived from my 3.x configs and at the top of the >> file is a line that >> starts with "# /usr/share/live/build/package-lists/". This must have been >> from when 3.x >> in development (when I first started using Live Build) and I have not >> removed it. >> >> It seems Live Build 4.x doesn't recognise # as a comment, even though >> Live Build 3.x did, >> so it reads the file as is and expects a file path to actually lead to a >> file even though the line >> is commented out. >> >> In the morning I will remove that line, start a totally new build and see >> what happens. >> >> You may wonder why I haven't sent this with the configs etc inline as you >> suggested. This >> email was huge with all the configs and the build log. Well in excess of >> 5000 lines, I have >> been able to attach files before but have never had to attach anything so >> big. It may help >> if the list software allowed larger attachments. >> >> On 4 October 2014 20:41, Ben Armstrong <sy...@sanctuary.nslug.ns.ca> >> wrote: >> >>> On 04/10/14 12:26 AM, Michael . wrote: >>> > There should be 8 files in the previous message. >>> > Please let me know if they are there, if they aren't I'll link to them >>> > in my dropbox. >>> >>> There is no previous message. As I said, include them inline and you >>> won't have this problem. >>> >>> Ben >>> >>> >> >
