Re: [qubes-users] Re: Building Qubes from source, strange error.

2017-03-27 Thread Elias Mårtenson 
On 27 March 2017 at 18:19, Andrew David Wong  wrote:

They won't be identical until we achieve reproducible builds:
>
> https://github.com/QubesOS/qubes-issues/issues/816


The builds are significantly different. The main difference that I noted
was that while the image I can download from the Qubes site is
approximately 4 GB in size, the one I built from source is 2.3 GB.

Also, using the home-built image, the graphics is incredibly slow, taking
several seconds to repaint the screen on the laptop on which I am doing my
tests. The official image doesn't have that issue. These two facts alone
suggests to me that there are some major components missing from the image
that I built.

Finally, I have to report that I can't get the network running on the Dell
Latitude 7480 even with a home-built image. Thus, I have to conclude that
until a new release (3.2.1 or 4.0), this machine can't be used with Qubes.
This is sad, since hardware-wise it'd be a perfect machine for the purpose.

Regards,
Elias

-- 
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/CADtN0W%2Bfs96-2uv62R2axNwaxCVt_wVYncms-Q2bWJCpk3MWXQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Building Qubes from source, strange error.

2017-03-26 Thread Unman 
On Sun, Mar 26, 2017 at 12:50:12PM -0600, Reg Tiangha wrote:
> On 03/26/2017 12:30 PM, Opal Raava wrote:
> > On Saturday, March 25, 2017 at 3:43:37 PM UTC+1, lok...@gmail.com wrote:
> >> On Friday, 24 March 2017 19:34:47 UTC+8, Opal Raava  wrote:
> >>  
>  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?
> >> I'm building it myself at the moment. I'm wondering if what I'll be 
> >> getting is something identical to the release image that you can download?
> >>
> >> My goal with all of this is to build an image that contains the most 
> >> recent release in the image, so that I might be able to escape the 
> >> Catch-22 situation where I need the network in order to download the 
> >> update so I can use the network.
> > The build procedure does not give an identical iso:
> >
> > $ sha256sum ../Qubes-R3.2-x86_64.iso Qubes-DVD-x86_64-20170324.iso
> > 6b998045a513dcdd45c1c6e61ace4f1b4e7eff799f381dccb9eb0170c80f678a  
> > ../Qubes-R3.2-x86_64.iso
> > b51b6aa9e468eacf279b6932d4a1b615495ae38fe458b92143be98ddd57c84ac  
> > Qubes-DVD-x86_64-20170324.iso
> >
> It probably wouldn't because when generating the iso, it'll pull in the
> latest versions of the packages available (I believe; correct me if I'm
> wrong) rather than the ones that were shipped on the original iso. So
> the included kernel will be the latest 4.4 version available (4.4.55
> rather than 4.4.14), all of the FC23 packages will be their final
> versions (since FC23 is now EOL), the various templates will include the
> latest versions of their own packages as well, etc.
> 
> I rather like this approach since you can spin isos on demand to have
> the newest packages (assuming it works; it failed for me yesterday
> trying to symlink to a non-existent Qubes package, but I didn't have
> time to troubleshoot it so I gave up), but I get the security concern as
> well. I suppose it'd be nice to have a "create a CD based on the one
> available on the website" option, but I think it would require
> hardcoding all the package versions to freeze them at what they were at
> release time or something like that? I'm not sure if that's worth it.
> 

Yes, you're quite right: you can see this by running 'make
switch-branch', and looking at the output. You will see that many of the
Qubes tools are from master.

The build process itself is designed to check and validate the source,
so this mitigates the security concern you speak of.

-- 
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/20170326231158.GC25127%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Building Qubes from source, strange error.

2017-03-26 Thread Reg Tiangha 
On 03/26/2017 12:30 PM, Opal Raava wrote:
> On Saturday, March 25, 2017 at 3:43:37 PM UTC+1, lok...@gmail.com wrote:
>> On Friday, 24 March 2017 19:34:47 UTC+8, Opal Raava  wrote:
>>  
 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?
>> I'm building it myself at the moment. I'm wondering if what I'll be getting 
>> is something identical to the release image that you can download?
>>
>> My goal with all of this is to build an image that contains the most recent 
>> release in the image, so that I might be able to escape the Catch-22 
>> situation where I need the network in order to download the update so I can 
>> use the network.
> The build procedure does not give an identical iso:
>
> $ sha256sum ../Qubes-R3.2-x86_64.iso Qubes-DVD-x86_64-20170324.iso
> 6b998045a513dcdd45c1c6e61ace4f1b4e7eff799f381dccb9eb0170c80f678a  
> ../Qubes-R3.2-x86_64.iso
> b51b6aa9e468eacf279b6932d4a1b615495ae38fe458b92143be98ddd57c84ac  
> Qubes-DVD-x86_64-20170324.iso
>
It probably wouldn't because when generating the iso, it'll pull in the
latest versions of the packages available (I believe; correct me if I'm
wrong) rather than the ones that were shipped on the original iso. So
the included kernel will be the latest 4.4 version available (4.4.55
rather than 4.4.14), all of the FC23 packages will be their final
versions (since FC23 is now EOL), the various templates will include the
latest versions of their own packages as well, etc.

I rather like this approach since you can spin isos on demand to have
the newest packages (assuming it works; it failed for me yesterday
trying to symlink to a non-existent Qubes package, but I didn't have
time to troubleshoot it so I gave up), but I get the security concern as
well. I suppose it'd be nice to have a "create a CD based on the one
available on the website" option, but I think it would require
hardcoding all the package versions to freeze them at what they were at
release time or something like that? I'm not sure if that's worth it.


-- 
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/ob92gu%24etb%241%40blaine.gmane.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Building Qubes from source, strange error.

2017-03-26 Thread Opal Raava 
On Saturday, March 25, 2017 at 3:43:37 PM UTC+1, lok...@gmail.com wrote:
> On Friday, 24 March 2017 19:34:47 UTC+8, Opal Raava  wrote:
>  
> > > 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?
> 
> I'm building it myself at the moment. I'm wondering if what I'll be getting 
> is something identical to the release image that you can download?
> 
> My goal with all of this is to build an image that contains the most recent 
> release in the image, so that I might be able to escape the Catch-22 
> situation where I need the network in order to download the update so I can 
> use the network.

The build procedure does not give an identical iso:

$ sha256sum ../Qubes-R3.2-x86_64.iso Qubes-DVD-x86_64-20170324.iso
6b998045a513dcdd45c1c6e61ace4f1b4e7eff799f381dccb9eb0170c80f678a  
../Qubes-R3.2-x86_64.iso
b51b6aa9e468eacf279b6932d4a1b615495ae38fe458b92143be98ddd57c84ac  
Qubes-DVD-x86_64-20170324.iso

-- 
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/a18a0015-cd32-459f-bbdf-1a7de6e7b722%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Building Qubes from source, strange error.

2017-03-25 Thread Reg Tiangha 
On 2017-03-25 8:43 AM, loke...@gmail.com
wrote:
> On Friday, 24 March 2017 19:34:47 UTC+8, Opal Raava  wrote:
>  
>>> 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?
> 
> I'm building it myself at the moment. I'm wondering if what I'll be getting 
> is something identical to the release image that you can download?
> 
> My goal with all of this is to build an image that contains the most recent 
> release in the image, so that I might be able to escape the Catch-22 
> situation where I need the network in order to download the update so I can 
> use the network.
> 

Let us know if this works. It'd be great to build an ISO on-demand that
could pull in the latest kernel in order to support installations on
newer hardware. Although now I'm curious if this could also be used to
re-base R3.2 dom0 on say FC24 or FC25 or anything else that already has
Qubes template support. I get that I'd then be responsible for compiling
Qubes-specific dom0 updates on my own and manually installing them
whenever they become available, but it'd be nice to see if an updated X
stack as well would help with some graphical glitches I've noticed pop
up every once in a while (nothing a reboot doesn't solve, though).

-- 
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/ob66gf%24kt5%241%40blaine.gmane.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Building Qubes from source, strange error.

2017-03-25 Thread lokedhs 
On Friday, 24 March 2017 19:34:47 UTC+8, Opal Raava  wrote:
 
> > 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?

I'm building it myself at the moment. I'm wondering if what I'll be getting is 
something identical to the release image that you can download?

My goal with all of this is to build an image that contains the most recent 
release in the image, so that I might be able to escape the Catch-22 situation 
where I need the network in order to download the update so I can use the 
network.

-- 
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/2289c69a-121a-44ef-a1ef-d4f797e3f6c7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Building Qubes from source, strange error.

2017-03-24 Thread Opal Raava 
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.

Re: [qubes-users] Re: Building Qubes from source, strange error.

2017-03-23 Thread Opal Raava 
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

-- 
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/5152be38-7dfd-492b-ba2b-e6eae6557c57%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Building Qubes from source, strange error.

2017-03-23 Thread Opal Raava 
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?

-- 
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/42a95c9e-55a9-4ac7-b5e3-5727f83c7225%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Building Qubes from source, strange error.

2017-03-23 Thread Unman 
On Thu, Mar 23, 2017 at 03:40:34AM -0700, loke...@gmail.com 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


-- 
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/2017032348.GA7814%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Building Qubes from source, strange error.

2017-03-23 Thread lokedhs 
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

-- 
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/08b31cd7-630b-4e7c-8310-66706fd3b302%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Building Qubes from source, strange error.

2017-03-23 Thread Opal Raava 
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:
> 
> > Ok that build did not work. I'm getting the following error:
> > 
> > ../../bin/mkpadlock.py -s 36 -c 0xcc devices/appvm-red.png
> > Traceback (most recent call last):
> >   File "../../bin/mkpadlock.py", line 25, in 
> > import qubesimgconverter
> > ImportError: No module named qubesimgconverter
> > ../Makefile.common:39: recipe for target 'devices/appvm-red.png' failed
> > make[2]: *** [devices/appvm-red.png] Error 1
> > make[2]: Leaving directory '/home/user/qubes-src/artwork/icons/36x36'
> > Makefile:4: recipe for target 'all' failed
> > make[1]: *** [all] Error 1
> > 
> > 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
> 
> Regards,
> Elias

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.

-- 
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/d2ca4d3c-e12c-47ee-b540-7324b734bcea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Building Qubes from source, strange error.

2017-03-22 Thread lokedhs 
On Thursday, 23 March 2017 02:45:53 UTC+8, Opal Raava  wrote:

> Ok that build did not work. I'm getting the following error:
> 
> ../../bin/mkpadlock.py -s 36 -c 0xcc devices/appvm-red.png
> Traceback (most recent call last):
>   File "../../bin/mkpadlock.py", line 25, in 
> import qubesimgconverter
> ImportError: No module named qubesimgconverter
> ../Makefile.common:39: recipe for target 'devices/appvm-red.png' failed
> make[2]: *** [devices/appvm-red.png] Error 1
> make[2]: Leaving directory '/home/user/qubes-src/artwork/icons/36x36'
> Makefile:4: recipe for target 'all' failed
> make[1]: *** [all] Error 1
> 
> 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

Regards,
Elias

-- 
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/6ef47e73-d96f-421a-9f7d-870a3309e24d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Building Qubes from source, strange error.

2017-03-22 Thread Opal Raava 
On Wednesday, March 22, 2017 at 6:47:48 PM UTC+1, Opal Raava wrote:
> On Wednesday, March 22, 2017 at 6:45:12 PM UTC+1, Opal Raava wrote:
> > On Wednesday, March 22, 2017 at 12:01:53 PM UTC+1, lok...@gmail.com wrote:
> > > I'm trying to build Qubes from source, but when following the 
> > > instructions (https://www.qubes-os.org/doc/qubes-builder/), the build 
> > > fails with the message below. Does anyone have any advice?
> > > 
> > > Regards,
> > > Elias
> > > 
> > > make[1]: Leaving directory '/home/emartenson/qubes-builder'
> > > make[1]: Entering directory '/home/emartenson/qubes-builder'
> > > -> Building core-admin-linux (rpm_spec/core-dom0-linux.spec) for fc23 
> > > dom0 (logfile: build-logs/core-admin-linux-dom0-fc23.log)
> > > --> Done:
> > >   
> > > qubes-src/core-admin-linux/pkgs/fc23/x86_64/qubes-core-dom0-linux-3.2.12-1.fc23.x86_64.rpm
> > >   
> > > qubes-src/core-admin-linux/pkgs/fc23/x86_64/qubes-core-dom0-linux-debuginfo-3.2.12-1.fc23.x86_64.rpm
> > >   
> > > qubes-src/core-admin-linux/pkgs/fc23/x86_64/qubes-core-dom0-linux-kernel-install-3.2.12-1.fc23.x86_64.rpm
> > > -> Building core-admin-linux (rpm_spec/core-dom0-vaio-fixes.spec) for 
> > > fc23 dom0 (logfile: build-logs/core-admin-linux-dom0-fc23.log)
> > > --> Done:
> > >   
> > > qubes-src/core-admin-linux/pkgs/fc23/x86_64/qubes-core-dom0-vaio-fixes-1.6.1-1.fc23.x86_64.rpm
> > > make[1]: Leaving directory '/home/emartenson/qubes-builder'
> > > make[1]: Entering directory '/home/emartenson/qubes-builder'
> > > make[1]: Leaving directory '/home/emartenson/qubes-builder'
> > > -> Building core-agent-linux (rpm_spec/core-vm.spec) for fc23 vm 
> > > (logfile: build-logs/core-agent-linux-vm-fc23.log)
> > > --> Done:
> > >   
> > > qubes-src/core-agent-linux/pkgs/fc23/x86_64/python2-dnf-plugins-qubes-hooks-3.2.16-1.fc23.x86_64.rpm
> > >   
> > > qubes-src/core-agent-linux/pkgs/fc23/x86_64/python3-dnf-plugins-qubes-hooks-3.2.16-1.fc23.x86_64.rpm
> > >   
> > > qubes-src/core-agent-linux/pkgs/fc23/x86_64/qubes-core-vm-3.2.16-1.fc23.x86_64.rpm
> > >   
> > > qubes-src/core-agent-linux/pkgs/fc23/x86_64/qubes-core-vm-debuginfo-3.2.16-1.fc23.x86_64.rpm
> > >   
> > > qubes-src/core-agent-linux/pkgs/fc23/x86_64/qubes-core-vm-systemd-3.2.16-1.fc23.x86_64.rpm
> > >   
> > > qubes-src/core-agent-linux/pkgs/fc23/x86_64/qubes-core-vm-sysvinit-3.2.16-1.fc23.x86_64.rpm
> > > -> Building core-agent-linux (rpm_spec/core-vm-doc.spec) for fc23 vm 
> > > (logfile: build-logs/core-agent-linux-vm-fc23.log)
> > > --> Done:
> > >   
> > > qubes-src/core-agent-linux/pkgs/fc23/noarch/qubes-core-vm-doc-3.2.16-1.noarch.rpm
> > > make[1]: Entering directory '/home/emartenson/qubes-builder'
> > > -> Building linux-kernel (kernel.spec) for fc23 dom0 (logfile: 
> > > build-logs/linux-kernel-dom0-fc23.log)
> > > --> Done:
> > >   
> > > qubes-src/linux-kernel/pkgs/fc23/x86_64/kernel-4.4.55-11.pvops.qubes.x86_64.rpm
> > >   
> > > qubes-src/linux-kernel/pkgs/fc23/x86_64/kernel-devel-4.4.55-11.pvops.qubes.x86_64.rpm
> > >   
> > > qubes-src/linux-kernel/pkgs/fc23/x86_64/kernel-qubes-vm-4.4.55-11.pvops.qubes.x86_64.rpm
> > > make[1]: Leaving directory '/home/emartenson/qubes-builder'
> > > make[1]: Entering directory '/home/emartenson/qubes-builder'
> > > -> Building artwork (qubes-artwork.spec) for fc23 dom0 (logfile: 
> > > build-logs/artwork-dom0-fc23.log)
> > > --> build failed!
> > > make[2]: Entering directory '/home/emartenson/qubes-builder'
> > > /home/emartenson/qubes-builder/qubes-src/builder-fedora//update-local-repo.sh
> > >  fc23
> > > sudo BACKEND_VMM=xen chroot /home/emartenson/qubes-builder/chroot-fc23 sh 
> > > -c 'cd /home/user/qubes-src/artwork; dnf  --refresh -y update'
> > > Dependencies resolved.
> > > Nothing to do.
> > > Complete!
> > > sudo BACKEND_VMM=xen chroot /home/emartenson/qubes-builder/chroot-fc23 sh 
> > > -c 'cd /home/user/qubes-src/artwork; dnf builddep --allowerasing --best  
> > > -y qubes-artwork.spec'
> > > Package ImageMagick-6.9.2.7-1.fc23.x86_64 is already installed, skipping.
> > > Package netpbm-progs-10.75.99-1.fc23.x86_64 is already installed, 
> > > skipping.
> > > No matching package to install: 'qubes-utils >= 3.9.0'
> > > Not all dependencies satisfied
> > > Error: Some packages could not be found.
> > > /home/emartenson/qubes-builder/qubes-src/builder-fedora/Makefile.fedora:106:
> > >  recipe for target 'dist-build-dep' failed
> > > make[2]: *** [dist-build-dep] Error 1
> > > make[2]: Leaving directory '/home/emartenson/qubes-builder'
> > > Makefile.generic:147: recipe for target 'packages' failed
> > > make[1]: *** [packages] Error 1
> > > make[1]: Leaving directory '/home/emartenson/qubes-builder'
> > > Makefile:221: recipe for target 'artwork-dom0' failed
> > > make: *** [artwork-dom0] Error 1
> > 
> > There is a version issue here. The current qubes repo produces a 
> > qubes-utils-3.2.3 rpm (qubes-utils is built by the component 'linux-utils' 
> > which is

Re: [qubes-users] Re: Building Qubes from source, strange error.

2017-03-22 Thread Unman 
On Wed, Mar 22, 2017 at 10:47:48AM -0700, Opal Raava wrote:
> On Wednesday, March 22, 2017 at 6:45:12 PM UTC+1, Opal Raava wrote:
> > On Wednesday, March 22, 2017 at 12:01:53 PM UTC+1, lok...@gmail.com wrote:
> > > I'm trying to build Qubes from source, but when following the 
> > > instructions (https://www.qubes-os.org/doc/qubes-builder/), the build 
> > > fails with the message below. Does anyone have any advice?
> > > 
> > > Regards,
> > > Elias
> > > 
> > > make[1]: Leaving directory '/home/emartenson/qubes-builder'
> > > make[1]: Entering directory '/home/emartenson/qubes-builder'
> > > -> Building core-admin-linux (rpm_spec/core-dom0-linux.spec) for fc23 
> > > dom0 (logfile: build-logs/core-admin-linux-dom0-fc23.log)
> > > --> Done:
> > >   
> > > qubes-src/core-admin-linux/pkgs/fc23/x86_64/qubes-core-dom0-linux-3.2.12-1.fc23.x86_64.rpm
> > >   
> > > qubes-src/core-admin-linux/pkgs/fc23/x86_64/qubes-core-dom0-linux-debuginfo-3.2.12-1.fc23.x86_64.rpm
> > >   
> > > qubes-src/core-admin-linux/pkgs/fc23/x86_64/qubes-core-dom0-linux-kernel-install-3.2.12-1.fc23.x86_64.rpm
> > > -> Building core-admin-linux (rpm_spec/core-dom0-vaio-fixes.spec) for 
> > > fc23 dom0 (logfile: build-logs/core-admin-linux-dom0-fc23.log)
> > > --> Done:
> > >   
> > > qubes-src/core-admin-linux/pkgs/fc23/x86_64/qubes-core-dom0-vaio-fixes-1.6.1-1.fc23.x86_64.rpm
> > > make[1]: Leaving directory '/home/emartenson/qubes-builder'
> > > make[1]: Entering directory '/home/emartenson/qubes-builder'
> > > make[1]: Leaving directory '/home/emartenson/qubes-builder'
> > > -> Building core-agent-linux (rpm_spec/core-vm.spec) for fc23 vm 
> > > (logfile: build-logs/core-agent-linux-vm-fc23.log)
> > > --> Done:
> > >   
> > > qubes-src/core-agent-linux/pkgs/fc23/x86_64/python2-dnf-plugins-qubes-hooks-3.2.16-1.fc23.x86_64.rpm
> > >   
> > > qubes-src/core-agent-linux/pkgs/fc23/x86_64/python3-dnf-plugins-qubes-hooks-3.2.16-1.fc23.x86_64.rpm
> > >   
> > > qubes-src/core-agent-linux/pkgs/fc23/x86_64/qubes-core-vm-3.2.16-1.fc23.x86_64.rpm
> > >   
> > > qubes-src/core-agent-linux/pkgs/fc23/x86_64/qubes-core-vm-debuginfo-3.2.16-1.fc23.x86_64.rpm
> > >   
> > > qubes-src/core-agent-linux/pkgs/fc23/x86_64/qubes-core-vm-systemd-3.2.16-1.fc23.x86_64.rpm
> > >   
> > > qubes-src/core-agent-linux/pkgs/fc23/x86_64/qubes-core-vm-sysvinit-3.2.16-1.fc23.x86_64.rpm
> > > -> Building core-agent-linux (rpm_spec/core-vm-doc.spec) for fc23 vm 
> > > (logfile: build-logs/core-agent-linux-vm-fc23.log)
> > > --> Done:
> > >   
> > > qubes-src/core-agent-linux/pkgs/fc23/noarch/qubes-core-vm-doc-3.2.16-1.noarch.rpm
> > > make[1]: Entering directory '/home/emartenson/qubes-builder'
> > > -> Building linux-kernel (kernel.spec) for fc23 dom0 (logfile: 
> > > build-logs/linux-kernel-dom0-fc23.log)
> > > --> Done:
> > >   
> > > qubes-src/linux-kernel/pkgs/fc23/x86_64/kernel-4.4.55-11.pvops.qubes.x86_64.rpm
> > >   
> > > qubes-src/linux-kernel/pkgs/fc23/x86_64/kernel-devel-4.4.55-11.pvops.qubes.x86_64.rpm
> > >   
> > > qubes-src/linux-kernel/pkgs/fc23/x86_64/kernel-qubes-vm-4.4.55-11.pvops.qubes.x86_64.rpm
> > > make[1]: Leaving directory '/home/emartenson/qubes-builder'
> > > make[1]: Entering directory '/home/emartenson/qubes-builder'
> > > -> Building artwork (qubes-artwork.spec) for fc23 dom0 (logfile: 
> > > build-logs/artwork-dom0-fc23.log)
> > > --> build failed!
> > > make[2]: Entering directory '/home/emartenson/qubes-builder'
> > > /home/emartenson/qubes-builder/qubes-src/builder-fedora//update-local-repo.sh
> > >  fc23
> > > sudo BACKEND_VMM=xen chroot /home/emartenson/qubes-builder/chroot-fc23 sh 
> > > -c 'cd /home/user/qubes-src/artwork; dnf  --refresh -y update'
> > > Dependencies resolved.
> > > Nothing to do.
> > > Complete!
> > > sudo BACKEND_VMM=xen chroot /home/emartenson/qubes-builder/chroot-fc23 sh 
> > > -c 'cd /home/user/qubes-src/artwork; dnf builddep --allowerasing --best  
> > > -y qubes-artwork.spec'
> > > Package ImageMagick-6.9.2.7-1.fc23.x86_64 is already installed, skipping.
> > > Package netpbm-progs-10.75.99-1.fc23.x86_64 is already installed, 
> > > skipping.
> > > No matching package to install: 'qubes-utils >= 3.9.0'
> > > Not all dependencies satisfied
> > > Error: Some packages could not be found.
> > > /home/emartenson/qubes-builder/qubes-src/builder-fedora/Makefile.fedora:106:
> > >  recipe for target 'dist-build-dep' failed
> > > make[2]: *** [dist-build-dep] Error 1
> > > make[2]: Leaving directory '/home/emartenson/qubes-builder'
> > > Makefile.generic:147: recipe for target 'packages' failed
> > > make[1]: *** [packages] Error 1
> > > make[1]: Leaving directory '/home/emartenson/qubes-builder'
> > > Makefile:221: recipe for target 'artwork-dom0' failed
> > > make: *** [artwork-dom0] Error 1
> > 
> > There is a version issue here. The current qubes repo produces a 
> > qubes-utils-3.2.3 rpm (qubes-utils is built by the component 'linux-utils' 
> > which is indeed

[qubes-users] Re: Building Qubes from source, strange error.

2017-03-22 Thread Opal Raava 
On Wednesday, March 22, 2017 at 6:45:12 PM UTC+1, Opal Raava wrote:
> On Wednesday, March 22, 2017 at 12:01:53 PM UTC+1, lok...@gmail.com wrote:
> > I'm trying to build Qubes from source, but when following the instructions 
> > (https://www.qubes-os.org/doc/qubes-builder/), the build fails with the 
> > message below. Does anyone have any advice?
> > 
> > Regards,
> > Elias
> > 
> > make[1]: Leaving directory '/home/emartenson/qubes-builder'
> > make[1]: Entering directory '/home/emartenson/qubes-builder'
> > -> Building core-admin-linux (rpm_spec/core-dom0-linux.spec) for fc23 dom0 
> > (logfile: build-logs/core-admin-linux-dom0-fc23.log)
> > --> Done:
> >   
> > qubes-src/core-admin-linux/pkgs/fc23/x86_64/qubes-core-dom0-linux-3.2.12-1.fc23.x86_64.rpm
> >   
> > qubes-src/core-admin-linux/pkgs/fc23/x86_64/qubes-core-dom0-linux-debuginfo-3.2.12-1.fc23.x86_64.rpm
> >   
> > qubes-src/core-admin-linux/pkgs/fc23/x86_64/qubes-core-dom0-linux-kernel-install-3.2.12-1.fc23.x86_64.rpm
> > -> Building core-admin-linux (rpm_spec/core-dom0-vaio-fixes.spec) for fc23 
> > dom0 (logfile: build-logs/core-admin-linux-dom0-fc23.log)
> > --> Done:
> >   
> > qubes-src/core-admin-linux/pkgs/fc23/x86_64/qubes-core-dom0-vaio-fixes-1.6.1-1.fc23.x86_64.rpm
> > make[1]: Leaving directory '/home/emartenson/qubes-builder'
> > make[1]: Entering directory '/home/emartenson/qubes-builder'
> > make[1]: Leaving directory '/home/emartenson/qubes-builder'
> > -> Building core-agent-linux (rpm_spec/core-vm.spec) for fc23 vm (logfile: 
> > build-logs/core-agent-linux-vm-fc23.log)
> > --> Done:
> >   
> > qubes-src/core-agent-linux/pkgs/fc23/x86_64/python2-dnf-plugins-qubes-hooks-3.2.16-1.fc23.x86_64.rpm
> >   
> > qubes-src/core-agent-linux/pkgs/fc23/x86_64/python3-dnf-plugins-qubes-hooks-3.2.16-1.fc23.x86_64.rpm
> >   
> > qubes-src/core-agent-linux/pkgs/fc23/x86_64/qubes-core-vm-3.2.16-1.fc23.x86_64.rpm
> >   
> > qubes-src/core-agent-linux/pkgs/fc23/x86_64/qubes-core-vm-debuginfo-3.2.16-1.fc23.x86_64.rpm
> >   
> > qubes-src/core-agent-linux/pkgs/fc23/x86_64/qubes-core-vm-systemd-3.2.16-1.fc23.x86_64.rpm
> >   
> > qubes-src/core-agent-linux/pkgs/fc23/x86_64/qubes-core-vm-sysvinit-3.2.16-1.fc23.x86_64.rpm
> > -> Building core-agent-linux (rpm_spec/core-vm-doc.spec) for fc23 vm 
> > (logfile: build-logs/core-agent-linux-vm-fc23.log)
> > --> Done:
> >   
> > qubes-src/core-agent-linux/pkgs/fc23/noarch/qubes-core-vm-doc-3.2.16-1.noarch.rpm
> > make[1]: Entering directory '/home/emartenson/qubes-builder'
> > -> Building linux-kernel (kernel.spec) for fc23 dom0 (logfile: 
> > build-logs/linux-kernel-dom0-fc23.log)
> > --> Done:
> >   
> > qubes-src/linux-kernel/pkgs/fc23/x86_64/kernel-4.4.55-11.pvops.qubes.x86_64.rpm
> >   
> > qubes-src/linux-kernel/pkgs/fc23/x86_64/kernel-devel-4.4.55-11.pvops.qubes.x86_64.rpm
> >   
> > qubes-src/linux-kernel/pkgs/fc23/x86_64/kernel-qubes-vm-4.4.55-11.pvops.qubes.x86_64.rpm
> > make[1]: Leaving directory '/home/emartenson/qubes-builder'
> > make[1]: Entering directory '/home/emartenson/qubes-builder'
> > -> Building artwork (qubes-artwork.spec) for fc23 dom0 (logfile: 
> > build-logs/artwork-dom0-fc23.log)
> > --> build failed!
> > make[2]: Entering directory '/home/emartenson/qubes-builder'
> > /home/emartenson/qubes-builder/qubes-src/builder-fedora//update-local-repo.sh
> >  fc23
> > sudo BACKEND_VMM=xen chroot /home/emartenson/qubes-builder/chroot-fc23 sh 
> > -c 'cd /home/user/qubes-src/artwork; dnf  --refresh -y update'
> > Dependencies resolved.
> > Nothing to do.
> > Complete!
> > sudo BACKEND_VMM=xen chroot /home/emartenson/qubes-builder/chroot-fc23 sh 
> > -c 'cd /home/user/qubes-src/artwork; dnf builddep --allowerasing --best  -y 
> > qubes-artwork.spec'
> > Package ImageMagick-6.9.2.7-1.fc23.x86_64 is already installed, skipping.
> > Package netpbm-progs-10.75.99-1.fc23.x86_64 is already installed, skipping.
> > No matching package to install: 'qubes-utils >= 3.9.0'
> > Not all dependencies satisfied
> > Error: Some packages could not be found.
> > /home/emartenson/qubes-builder/qubes-src/builder-fedora/Makefile.fedora:106:
> >  recipe for target 'dist-build-dep' failed
> > make[2]: *** [dist-build-dep] Error 1
> > make[2]: Leaving directory '/home/emartenson/qubes-builder'
> > Makefile.generic:147: recipe for target 'packages' failed
> > make[1]: *** [packages] Error 1
> > make[1]: Leaving directory '/home/emartenson/qubes-builder'
> > Makefile:221: recipe for target 'artwork-dom0' failed
> > make: *** [artwork-dom0] Error 1
> 
> There is a version issue here. The current qubes repo produces a 
> qubes-utils-3.2.3 rpm (qubes-utils is built by the component 'linux-utils' 
> which is indeed built before artwork gets built.
> But somehow the artwork .spec file requires qubes-utils >= 3.9.0 (that arwork 
> spec file is qubes-builder/qubes-src/artwork-qubes-artwork.spec)
> 
> So I changed that to >= 3.2.3 and started a fresh build. I'll post

[qubes-users] Re: Building Qubes from source, strange error.

2017-03-22 Thread Opal Raava 
On Wednesday, March 22, 2017 at 12:01:53 PM UTC+1, lok...@gmail.com wrote:
> I'm trying to build Qubes from source, but when following the instructions 
> (https://www.qubes-os.org/doc/qubes-builder/), the build fails with the 
> message below. Does anyone have any advice?
> 
> Regards,
> Elias
> 
> make[1]: Leaving directory '/home/emartenson/qubes-builder'
> make[1]: Entering directory '/home/emartenson/qubes-builder'
> -> Building core-admin-linux (rpm_spec/core-dom0-linux.spec) for fc23 dom0 
> (logfile: build-logs/core-admin-linux-dom0-fc23.log)
> --> Done:
>   
> qubes-src/core-admin-linux/pkgs/fc23/x86_64/qubes-core-dom0-linux-3.2.12-1.fc23.x86_64.rpm
>   
> qubes-src/core-admin-linux/pkgs/fc23/x86_64/qubes-core-dom0-linux-debuginfo-3.2.12-1.fc23.x86_64.rpm
>   
> qubes-src/core-admin-linux/pkgs/fc23/x86_64/qubes-core-dom0-linux-kernel-install-3.2.12-1.fc23.x86_64.rpm
> -> Building core-admin-linux (rpm_spec/core-dom0-vaio-fixes.spec) for fc23 
> dom0 (logfile: build-logs/core-admin-linux-dom0-fc23.log)
> --> Done:
>   
> qubes-src/core-admin-linux/pkgs/fc23/x86_64/qubes-core-dom0-vaio-fixes-1.6.1-1.fc23.x86_64.rpm
> make[1]: Leaving directory '/home/emartenson/qubes-builder'
> make[1]: Entering directory '/home/emartenson/qubes-builder'
> make[1]: Leaving directory '/home/emartenson/qubes-builder'
> -> Building core-agent-linux (rpm_spec/core-vm.spec) for fc23 vm (logfile: 
> build-logs/core-agent-linux-vm-fc23.log)
> --> Done:
>   
> qubes-src/core-agent-linux/pkgs/fc23/x86_64/python2-dnf-plugins-qubes-hooks-3.2.16-1.fc23.x86_64.rpm
>   
> qubes-src/core-agent-linux/pkgs/fc23/x86_64/python3-dnf-plugins-qubes-hooks-3.2.16-1.fc23.x86_64.rpm
>   
> qubes-src/core-agent-linux/pkgs/fc23/x86_64/qubes-core-vm-3.2.16-1.fc23.x86_64.rpm
>   
> qubes-src/core-agent-linux/pkgs/fc23/x86_64/qubes-core-vm-debuginfo-3.2.16-1.fc23.x86_64.rpm
>   
> qubes-src/core-agent-linux/pkgs/fc23/x86_64/qubes-core-vm-systemd-3.2.16-1.fc23.x86_64.rpm
>   
> qubes-src/core-agent-linux/pkgs/fc23/x86_64/qubes-core-vm-sysvinit-3.2.16-1.fc23.x86_64.rpm
> -> Building core-agent-linux (rpm_spec/core-vm-doc.spec) for fc23 vm 
> (logfile: build-logs/core-agent-linux-vm-fc23.log)
> --> Done:
>   
> qubes-src/core-agent-linux/pkgs/fc23/noarch/qubes-core-vm-doc-3.2.16-1.noarch.rpm
> make[1]: Entering directory '/home/emartenson/qubes-builder'
> -> Building linux-kernel (kernel.spec) for fc23 dom0 (logfile: 
> build-logs/linux-kernel-dom0-fc23.log)
> --> Done:
>   
> qubes-src/linux-kernel/pkgs/fc23/x86_64/kernel-4.4.55-11.pvops.qubes.x86_64.rpm
>   
> qubes-src/linux-kernel/pkgs/fc23/x86_64/kernel-devel-4.4.55-11.pvops.qubes.x86_64.rpm
>   
> qubes-src/linux-kernel/pkgs/fc23/x86_64/kernel-qubes-vm-4.4.55-11.pvops.qubes.x86_64.rpm
> make[1]: Leaving directory '/home/emartenson/qubes-builder'
> make[1]: Entering directory '/home/emartenson/qubes-builder'
> -> Building artwork (qubes-artwork.spec) for fc23 dom0 (logfile: 
> build-logs/artwork-dom0-fc23.log)
> --> build failed!
> make[2]: Entering directory '/home/emartenson/qubes-builder'
> /home/emartenson/qubes-builder/qubes-src/builder-fedora//update-local-repo.sh 
> fc23
> sudo BACKEND_VMM=xen chroot /home/emartenson/qubes-builder/chroot-fc23 sh -c 
> 'cd /home/user/qubes-src/artwork; dnf  --refresh -y update'
> Dependencies resolved.
> Nothing to do.
> Complete!
> sudo BACKEND_VMM=xen chroot /home/emartenson/qubes-builder/chroot-fc23 sh -c 
> 'cd /home/user/qubes-src/artwork; dnf builddep --allowerasing --best  -y 
> qubes-artwork.spec'
> Package ImageMagick-6.9.2.7-1.fc23.x86_64 is already installed, skipping.
> Package netpbm-progs-10.75.99-1.fc23.x86_64 is already installed, skipping.
> No matching package to install: 'qubes-utils >= 3.9.0'
> Not all dependencies satisfied
> Error: Some packages could not be found.
> /home/emartenson/qubes-builder/qubes-src/builder-fedora/Makefile.fedora:106: 
> recipe for target 'dist-build-dep' failed
> make[2]: *** [dist-build-dep] Error 1
> make[2]: Leaving directory '/home/emartenson/qubes-builder'
> Makefile.generic:147: recipe for target 'packages' failed
> make[1]: *** [packages] Error 1
> make[1]: Leaving directory '/home/emartenson/qubes-builder'
> Makefile:221: recipe for target 'artwork-dom0' failed
> make: *** [artwork-dom0] Error 1

There is a version issue here. The current qubes repo produces a 
qubes-utils-3.2.3 rpm (qubes-utils is built by the component 'linux-utils' 
which is indeed built before artwork gets built.
But somehow the artwork .spec file requires qubes-utils >= 3.9.0 (that arwork 
spec file is qubes-builder/qubes-src/artwork-qubes-artwork.spec)

So I changed that to >= 3.2.3 and started a fresh build. I'll post my results 
because I'm not sure if this fixes anything.

-- 
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