On Thursday, March 23, 2017 at 9:40:57 PM UTC+1, Opal Raava wrote: > On Thursday, March 23, 2017 at 8:23:15 PM UTC+1, Opal Raava wrote: > > On Thursday, March 23, 2017 at 12:11:51 PM UTC+1, Unman wrote: > > > On Thu, Mar 23, 2017 at 03:40:34AM -0700, lokedhs wrote: > > > > On Thursday, 23 March 2017 18:23:30 UTC+8, Opal Raava wrote: > > > > > On Thursday, March 23, 2017 at 3:27:58 AM UTC+1, lok...@gmail.com > > > > > wrote: > > > > > > On Thursday, 23 March 2017 02:45:53 UTC+8, Opal Raava wrote: > > > > > > > > > > > > > Which tells us that we probably really do need version 3.9.0 of > > > > > > > qubes-tools. > > > > > > > > > > > > Where can that version be found? Looking at the latest master of > > > > > > qubes-linux-utils, it only contains version 3.2.3: > > > > > > > > > > > > https://github.com/QubesOS/qubes-linux-utils/blob/master/version > > > > > > > > > Yes, and that is what surprises me as well. The relevant source has > > > > > not been touched in a while. I've looked, but I don't know why the > > > > > build breaks. > > > > > > > > > > All I know for a fact is what you said, it asks for 3.9.0 and > > > > > delivers 3.2.3 at the master branch. And that the relevant source > > > > > files all have not been changed recently. > > > > > > > > The spec file was updated from 2.0.10 to 3.9.0 as of commit > > > > 9780a95a0ad20b63f2da401f108f2dcb3511554b. The interesting thing is that > > > > the commit was on the 17'th December 2015. This is more than half a > > > > year before the most recent ISO images were built. > > > > > > > > I really have no idea what the cause for this could be. > > > > > > > > Regards, > > > > Elias > > > > > > > > > > Finally I understand - you're trying to build a full build of master - > > > I just dont think this works at the moment - you could *try* following > > > my suggestion of NOT building artwork at all - just comment it out. > > > > > > Lots of the devel work on v4 (that's now in master) is in the devs repos > > > - you can see the mysterious 3.9 here: > > > https://github.com/woju/qubes-linux-utils/tree/core3-devel > > > > > > So I think you have to cherry pick from a number of different repos to > > > get something like a working v4 if that's what you want. > > > At least from marmarek and woju. > > > I dont have scope to try this. > > > > > > (You can just build some components as you like - e.g just the manager.) > > > > > > It IS possible to build templates from master, and they seem to work > > > fine with 3.2 :although marek has said that things might break, I haven't > > > seen this as yet.) > > > > > > unman > > > > Ah okay, so all we have to do is specify 'releng3.2' into github or > > something to build the R3.2 branch? > > Ah, problem solved. In the web build documentation it says to: > > cp example-configs/qubes-os-master.conf builder.conf > > if you instead do: > > cp example-configs/qubes-os-r3.2.conf > > you get a better branch. I'm currently trying to build that
I have now a new shiny ISO, so this works. Isn't it a bug in the website documentation that they recommend building from the master branch? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4e763334-d7fc-49da-8b0b-0f4de7a012b3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.