Re: [qubes-users] Re: Building Qubes 4rc4 iso from source

2018-02-04 Thread Tim W
On Sunday, February 4, 2018 at 10:42:05 PM UTC-5, Tim W wrote:
> On Sunday, February 4, 2018 at 8:51:45 PM UTC-5, Unman wrote:
> > On Mon, Feb 05, 2018 at 01:44:10AM +, Unman wrote:
> > > On Sat, Feb 03, 2018 at 06:52:12PM -0800, Tim W wrote:
> > > > Also when I ran setup script it required PyYaml and that was also shown 
> > > > in https://www.qubes-os.org/doc/qubes-builder/ Building Qubes From 
> > > > Scratch 
> > > > 
> > > > Then you have the build directions that there is notes to follow the 
> > > > Archlinux directions for using the builder tools and they do not have 
> > > > them but then it includes python.sh rather than python2.sh .  The 
> > > > latter is definitely needed.
> > > > 
> > > > Then finally in the README.md file in the qubes-builder which you are 
> > > > directed to read it has you install perl-open but not dpkg-dev 
> > > > debootstrap and a few others.  So we are basically given directions to 
> > > > go to at least 3 different places that all have from slightly different 
> > > > to completely different instructions for building qubes.
> > > > 
> > > > IMHO for the advanced user who wants to build qubes from source the 
> > > > ./setup script is by far the easiest to follow as it being a all 
> > > > inclusive script handles many steps for you in a nice basic gui.  Issue 
> > > > is we need to have some very basic steps of what will work with each OS 
> > > > version.  It would only take 10-15 min to update a markup page for each 
> > > > os.  Everything is there except what works with what OS and frankly 
> > > > that's all in terms of instructions that should have to change ever in 
> > > > qubes current xen based format.  If a dev could even just post a list 
> > > > of what templates work with the version in the group I or others can 
> > > > easily update the doc page.  I have helped in that area before as its 
> > > > one area IMO any and all qubes users can help out with and give back to 
> > > > the project. 
> > > > 
> > > 
> > > afaik the current instructions on the website are targeted to Fedora 26,
> > > the currently supported version, and should be complete.
> > > The archlinux instructions are quite out of date and the README definitely
> > > needs to be updated.
> > > I'm not sure what you mean by OS version, or most of your last
> > > paragraph. Can you clarify?
> > 
> > Sorry, I've gone back to your original post and it's clearer.
> > You should be able to build all the templates referenced in the setup
> > program. If you can't, then (barring network problems) it's a bug.
> > Its a moot point whether you should be building some of the older,
> > eol templates, and whether they should be available to build.
> 
> I just added Centos 7 Standard template with the ones that had already built 
> correct and as before it errored out with the following:
> ---
> Building core-admin-client (rpm_spec/qubes-core-admin-client.spec) for 
> centos7 vm (logfile: build-logs/core-admin-client-vm-centos7.log)
> --> build failed!
> reading sources... [ 92%] manpages/qvm-tags
> reading sources... [ 96%] manpages/qvm-unpause
> reading sources... [100%] manpages/qvm-volume
> 
> /home/user/qubes-src/core-admin-client/doc/manpages/qvm-features.rst:91: 
> ERROR: Unknown interpreted text role "py:pbj".
> /home/user/qubes-src/core-admin-client/doc/manpages/qvm-firewall.rst:73: 
> WARNING: Bullet list ends without a blank line; unexpected unindent.
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... 
> /home/user/qubes-src/core-admin-client/doc/manpages/index.rst:: WARNING: 
> document isn't included in any toctree
> done
> writing... qvm-backup-restore.1 { } Checking arguments for 
> 'qvm-backup-restore'
> 
> Exception occurred:
>   File "/usr/lib64/python2.7/importlib/__init__.py", line 37, in import_module
> __import__(name)
>   File 
> "/home/user/qubes-src/core-admin-client/qubesadmin/tools/qvm_backup_restore.py",
>  line 4
> SyntaxError: Non-ASCII character '\xc3' in file 
> /home/user/qubes-src/core-admin-client/qubesadmin/tools/qvm_backup_restore.py 
> on line 4, but no encoding declared; see 
> http://www.python.org/peps/pep-0263.html for details
> The full traceback has been saved in /tmp/sphinx-err-JOw4sG.log, if you want 
> to report the issue to the developers.
> Please also report this if it was a user error, so that a better error 
> message can be provided next time.
> Either send bugs to the mailing list at 
> ,
> or report them in the tracker at 
> . Thanks!
> make: *** [man] Error 1
> make: Leaving directory `/home/user/qubes-src/core-admin-client/doc'
> error: Bad exit status from /var/tmp/rpm-tmp.Hd675A (%build)
> ---
> 
> 
> Any ideas?

Next I guess I will try the fully loaded versions of FC26 and Stretch as they 
have the most likelihood of working with

Re: [qubes-users] Re: Building Qubes 4rc4 iso from source

2018-02-04 Thread Tim W
On Sunday, February 4, 2018 at 8:51:45 PM UTC-5, Unman wrote:
> On Mon, Feb 05, 2018 at 01:44:10AM +, Unman wrote:
> > On Sat, Feb 03, 2018 at 06:52:12PM -0800, Tim W wrote:
> > > Also when I ran setup script it required PyYaml and that was also shown 
> > > in https://www.qubes-os.org/doc/qubes-builder/ Building Qubes From 
> > > Scratch 
> > > 
> > > Then you have the build directions that there is notes to follow the 
> > > Archlinux directions for using the builder tools and they do not have 
> > > them but then it includes python.sh rather than python2.sh .  The latter 
> > > is definitely needed.
> > > 
> > > Then finally in the README.md file in the qubes-builder which you are 
> > > directed to read it has you install perl-open but not dpkg-dev 
> > > debootstrap and a few others.  So we are basically given directions to go 
> > > to at least 3 different places that all have from slightly different to 
> > > completely different instructions for building qubes.
> > > 
> > > IMHO for the advanced user who wants to build qubes from source the 
> > > ./setup script is by far the easiest to follow as it being a all 
> > > inclusive script handles many steps for you in a nice basic gui.  Issue 
> > > is we need to have some very basic steps of what will work with each OS 
> > > version.  It would only take 10-15 min to update a markup page for each 
> > > os.  Everything is there except what works with what OS and frankly 
> > > that's all in terms of instructions that should have to change ever in 
> > > qubes current xen based format.  If a dev could even just post a list of 
> > > what templates work with the version in the group I or others can easily 
> > > update the doc page.  I have helped in that area before as its one area 
> > > IMO any and all qubes users can help out with and give back to the 
> > > project. 
> > > 
> > 
> > afaik the current instructions on the website are targeted to Fedora 26,
> > the currently supported version, and should be complete.
> > The archlinux instructions are quite out of date and the README definitely
> > needs to be updated.
> > I'm not sure what you mean by OS version, or most of your last
> > paragraph. Can you clarify?
> 
> Sorry, I've gone back to your original post and it's clearer.
> You should be able to build all the templates referenced in the setup
> program. If you can't, then (barring network problems) it's a bug.
> Its a moot point whether you should be building some of the older,
> eol templates, and whether they should be available to build.

I just added Centos 7 Standard template with the ones that had already built 
correct and as before it errored out with the following:
---
Building core-admin-client (rpm_spec/qubes-core-admin-client.spec) for centos7 
vm (logfile: build-logs/core-admin-client-vm-centos7.log)
--> build failed!
reading sources... [ 92%] manpages/qvm-tags
reading sources... [ 96%] manpages/qvm-unpause
reading sources... [100%] manpages/qvm-volume

/home/user/qubes-src/core-admin-client/doc/manpages/qvm-features.rst:91: ERROR: 
Unknown interpreted text role "py:pbj".
/home/user/qubes-src/core-admin-client/doc/manpages/qvm-firewall.rst:73: 
WARNING: Bullet list ends without a blank line; unexpected unindent.
looking for now-outdated files... none found
pickling environment... done
checking consistency... 
/home/user/qubes-src/core-admin-client/doc/manpages/index.rst:: WARNING: 
document isn't included in any toctree
done
writing... qvm-backup-restore.1 { } Checking arguments for 'qvm-backup-restore'

Exception occurred:
  File "/usr/lib64/python2.7/importlib/__init__.py", line 37, in import_module
__import__(name)
  File 
"/home/user/qubes-src/core-admin-client/qubesadmin/tools/qvm_backup_restore.py",
 line 4
SyntaxError: Non-ASCII character '\xc3' in file 
/home/user/qubes-src/core-admin-client/qubesadmin/tools/qvm_backup_restore.py 
on line 4, but no encoding declared; see 
http://www.python.org/peps/pep-0263.html for details
The full traceback has been saved in /tmp/sphinx-err-JOw4sG.log, if you want to 
report the issue to the developers.
Please also report this if it was a user error, so that a better error message 
can be provided next time.
Either send bugs to the mailing list at 
,
or report them in the tracker at 
. Thanks!
make: *** [man] Error 1
make: Leaving directory `/home/user/qubes-src/core-admin-client/doc'
error: Bad exit status from /var/tmp/rpm-tmp.Hd675A (%build)
---


Any ideas?

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

Re: [qubes-users] Re: Building Qubes 4rc4 iso from source

2018-02-04 Thread Tim W
On Sunday, February 4, 2018 at 8:51:45 PM UTC-5, Unman wrote:
> On Mon, Feb 05, 2018 at 01:44:10AM +, Unman wrote:
> > On Sat, Feb 03, 2018 at 06:52:12PM -0800, Tim W wrote:
> > > Also when I ran setup script it required PyYaml and that was also shown 
> > > in https://www.qubes-os.org/doc/qubes-builder/ Building Qubes From 
> > > Scratch 
> > > 
> > > Then you have the build directions that there is notes to follow the 
> > > Archlinux directions for using the builder tools and they do not have 
> > > them but then it includes python.sh rather than python2.sh .  The latter 
> > > is definitely needed.
> > > 
> > > Then finally in the README.md file in the qubes-builder which you are 
> > > directed to read it has you install perl-open but not dpkg-dev 
> > > debootstrap and a few others.  So we are basically given directions to go 
> > > to at least 3 different places that all have from slightly different to 
> > > completely different instructions for building qubes.
> > > 
> > > IMHO for the advanced user who wants to build qubes from source the 
> > > ./setup script is by far the easiest to follow as it being a all 
> > > inclusive script handles many steps for you in a nice basic gui.  Issue 
> > > is we need to have some very basic steps of what will work with each OS 
> > > version.  It would only take 10-15 min to update a markup page for each 
> > > os.  Everything is there except what works with what OS and frankly 
> > > that's all in terms of instructions that should have to change ever in 
> > > qubes current xen based format.  If a dev could even just post a list of 
> > > what templates work with the version in the group I or others can easily 
> > > update the doc page.  I have helped in that area before as its one area 
> > > IMO any and all qubes users can help out with and give back to the 
> > > project. 
> > > 
> > 
> > afaik the current instructions on the website are targeted to Fedora 26,
> > the currently supported version, and should be complete.
> > The archlinux instructions are quite out of date and the README definitely
> > needs to be updated.
> > I'm not sure what you mean by OS version, or most of your last
> > paragraph. Can you clarify?
> 
> Sorry, I've gone back to your original post and it's clearer.
> You should be able to build all the templates referenced in the setup
> program. If you can't, then (barring network problems) it's a bug.
> Its a moot point whether you should be building some of the older,
> eol templates, and whether they should be available to build.

Correct on the older templates.  The oldest I would consider is fc25 and wheezy 
etc..   for it to be working correctly without bug I would expect to be able to 
choose all none EOL templates together and have it build.  Would need 100+ gigs 
but it  should work.   That is what I am working towards.

My original issue with setup script might have been part network and part gpg 
sig issue.   Just would like to know and then update the offical Doc etc pages 
with correct info where needed.

The issue with archlinux is it is referenced at least twice in other docs as to 
being the most uptodate instructions for building qubes and templates.  
Basically much of the docs are a mess as they have conflicting missing dif info.

-- 
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/234ee664-b03f-4df9-bff6-628fb956efb8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Building Qubes 4rc4 iso from source

2018-02-04 Thread Unman
On Mon, Feb 05, 2018 at 01:44:10AM +, Unman wrote:
> On Sat, Feb 03, 2018 at 06:52:12PM -0800, Tim W wrote:
> > Also when I ran setup script it required PyYaml and that was also shown 
> > in https://www.qubes-os.org/doc/qubes-builder/ Building Qubes From Scratch 
> > 
> > Then you have the build directions that there is notes to follow the 
> > Archlinux directions for using the builder tools and they do not have them 
> > but then it includes python.sh rather than python2.sh .  The latter is 
> > definitely needed.
> > 
> > Then finally in the README.md file in the qubes-builder which you are 
> > directed to read it has you install perl-open but not dpkg-dev debootstrap 
> > and a few others.  So we are basically given directions to go to at least 3 
> > different places that all have from slightly different to completely 
> > different instructions for building qubes.
> > 
> > IMHO for the advanced user who wants to build qubes from source the ./setup 
> > script is by far the easiest to follow as it being a all inclusive script 
> > handles many steps for you in a nice basic gui.  Issue is we need to have 
> > some very basic steps of what will work with each OS version.  It would 
> > only take 10-15 min to update a markup page for each os.  Everything is 
> > there except what works with what OS and frankly that's all in terms of 
> > instructions that should have to change ever in qubes current xen based 
> > format.  If a dev could even just post a list of what templates work with 
> > the version in the group I or others can easily update the doc page.  I 
> > have helped in that area before as its one area IMO any and all qubes users 
> > can help out with and give back to the project. 
> > 
> 
> afaik the current instructions on the website are targeted to Fedora 26,
> the currently supported version, and should be complete.
> The archlinux instructions are quite out of date and the README definitely
> needs to be updated.
> I'm not sure what you mean by OS version, or most of your last
> paragraph. Can you clarify?

Sorry, I've gone back to your original post and it's clearer.
You should be able to build all the templates referenced in the setup
program. If you can't, then (barring network problems) it's a bug.
Its a moot point whether you should be building some of the older,
eol templates, and whether they should be available to build.


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


Re: [qubes-users] Re: Building Qubes 4rc4 iso from source

2018-02-04 Thread Unman
On Sat, Feb 03, 2018 at 06:52:12PM -0800, Tim W wrote:
> Also when I ran setup script it required PyYaml and that was also shown 
> in https://www.qubes-os.org/doc/qubes-builder/ Building Qubes From Scratch 
> 
> Then you have the build directions that there is notes to follow the 
> Archlinux directions for using the builder tools and they do not have them 
> but then it includes python.sh rather than python2.sh .  The latter is 
> definitely needed.
> 
> Then finally in the README.md file in the qubes-builder which you are 
> directed to read it has you install perl-open but not dpkg-dev debootstrap 
> and a few others.  So we are basically given directions to go to at least 3 
> different places that all have from slightly different to completely 
> different instructions for building qubes.
> 
> IMHO for the advanced user who wants to build qubes from source the ./setup 
> script is by far the easiest to follow as it being a all inclusive script 
> handles many steps for you in a nice basic gui.  Issue is we need to have 
> some very basic steps of what will work with each OS version.  It would only 
> take 10-15 min to update a markup page for each os.  Everything is there 
> except what works with what OS and frankly that's all in terms of 
> instructions that should have to change ever in qubes current xen based 
> format.  If a dev could even just post a list of what templates work with the 
> version in the group I or others can easily update the doc page.  I have 
> helped in that area before as its one area IMO any and all qubes users can 
> help out with and give back to the project. 
> 

afaik the current instructions on the website are targeted to Fedora 26,
the currently supported version, and should be complete.
The archlinux instructions are quite out of date and the README definitely
needs to be updated.
I'm not sure what you mean by OS version, or most of your last
paragraph. Can you clarify?

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


[qubes-users] Re: Building Qubes 4rc4 iso from source

2018-02-03 Thread Tim W
Also when I ran setup script it required PyYaml and that was also shown 
in https://www.qubes-os.org/doc/qubes-builder/ Building Qubes From Scratch 

Then you have the build directions that there is notes to follow the Archlinux 
directions for using the builder tools and they do not have them but then it 
includes python.sh rather than python2.sh .  The latter is definitely needed.

Then finally in the README.md file in the qubes-builder which you are directed 
to read it has you install perl-open but not dpkg-dev debootstrap and a few 
others.  So we are basically given directions to go to at least 3 different 
places that all have from slightly different to completely different 
instructions for building qubes.

IMHO for the advanced user who wants to build qubes from source the ./setup 
script is by far the easiest to follow as it being a all inclusive script 
handles many steps for you in a nice basic gui.  Issue is we need to have some 
very basic steps of what will work with each OS version.  It would only take 
10-15 min to update a markup page for each os.  Everything is there except what 
works with what OS and frankly that's all in terms of instructions that should 
have to change ever in qubes current xen based format.  If a dev could even 
just post a list of what templates work with the version in the group I or 
others can easily update the doc page.  I have helped in that area before as 
its one area IMO any and all qubes users can help out with and give back to the 
project. 

-- 
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/a8035610-fee7-42e8-90aa-a25ebfb337d7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.