[prev in list] [next in list] [prev in thread] [next in thread]
List: qubes-devel
Subject: Re: [qubes-devel] Re: Qubes Builder failed Archlinux repository is missing
From: TimW <timwelter () gmail ! com>
Date: 2016-02-01 3:52:24
Message-ID: 43ae839f-e5c9-460f-8c00-c281f5007534 () googlegroups ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Sunday, January 31, 2016 at 11:45:39 AM UTC-5, sudod...@gmail.com wrote:
>
>
>
> Am Samstag, 30. Januar 2016 02:29:42 UTC+1 schrieb TimW:
> >
> >
> >
> > On Thursday, January 28, 2016 at 9:00:51 PM UTC-5, sudod...@gmail.com
> > wrote:
> > >
> > >
> > >
> > > Am Mittwoch, 27. Januar 2016 05:35:06 UTC+1 schrieb TimW:
> > > >
> > > >
> > > >
> > > > On Tuesday, January 26, 2016 at 9:39:30 PM UTC-5, TimW wrote:
> > > > >
> > > > >
> > > > >
> > > > > On Tuesday, January 26, 2016 at 6:56:12 PM UTC-5, TimW wrote:
> > > > > >
> > > > > > Once that is done can you post the build.conf file on here so I can
> > > > > > add it to the doc to replace that huge thing I have in there presently \
> > > > > > lol
> > > > >
> > > > >
> > > > > Yes I really do need that current build file as currently the old one
> > > > > does not work at all now. I can not get past make install-deps or
> > > > > get-sources.
> > > > >
> > > > > I will start to work on copying that install Doc into a fork pull
> > > > > request. FYI its a first for me so I may have some questions if I get
> > > > > stuck.
> > > > >
> > > >
> > > >
> > > >
> > > > What page do we actually want to update with these changes. Right now
> > > > we have the archlinux template page which really is nothing more than a
> > > > place holder with a link taking you to the general template building page
> > > > which is using some basic instructions using archlinux as the example. Its
> > > > all the links at the bottom that really show you how to build it.
> > > >
> > > > My thought is to put these changes in the actual Archlinux template
> > > > page. Unless Qubes plans on making this a supported template with a
> > > > binary package that is always kept current like the Fedora and Debain is.
> > > >
> > > > The other possible situation effecting the above is below:
> > > >
> > > > I wanted to understand is how are older Qubes versions handled?
> > > > How long does Qubes support past version of templates? As these templates
> > > > (archlinux, ubuntu, etc ) are user supported vs Qubes ITL supported are
> > > > there support guidelines it would be preferred to follow in these cases?
> > > > Should someone be able to follow direction and get a working Archlinux
> > > > template for R2? Or are the changes that are being made to get working
> > > > templates for 3.1 and archlinux breaking the process for those on older
> > > > versions? Sorry it may just be my ignorance to how this is already being
> > > > handles and is a non issue. I do not know.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > I'd put the doc on this page:
> > > https://www.qubes-os.org/doc/templates/archlinux/ and remove the other
> > > page (https://www.qubes-os.org/doc/building-archlinux-template/).
> > >
> > > For the different verions: Have a look at
> > > https://groups.google.com/forum/#!searchin/qubes-devel/support/qubes-devel/wySWr9h1QwU/0_IRCZ5TBgAJ
> > >
> > > .
> > > I think there is not enough capacity to guarantee long term support and
> > > we'd better stick to the most current stable release. This is also the Arch
> > > way. Cutting-edge software, rolling release but not really LTS.
> > >
> >
> >
> > Awesome. That is what I thought as well given all the changes. I was
> > thinking it would make it very cluttered or make for too many pages it we
> > started leaving the support for all the past Qubes ver and there issues.
> > Most of the past issues are now all gone with the current.
> >
> > I have finished all but just a few things.
> >
> > It took a bit of time for me to turn the odt and rewrite it into the .md.
> > I had to host all the screen shots. Then I had to learn the formatting
> > and syntax of .md git style files. I ended up finding using a local
> > markdown text editor locally the easiest way. I found ReText to be the
> > best combo of basic and ease of use plus all the functions needed. I
> > posted about it in the documentation thread in the user list.
> >
> >
> > *sudod..*
> >
> > *Can you please post what you current build file is. ( complete).* I
> > need to put that in place of the original ( now not functional) one you
> > posted in the user archlinux thread. I want to get some screenshots of
> > the output of the final template creation.
> >
> >
> >
> >
> > *I also still need someone to test the: XferCommand =
> > http_proxy=10.137.255.254:8082 <http://10.137.255.254:8082> /usr/bin/curl
> > -C - -f %u > %o*
> >
> > Currently it does not work for me and I do not want to include bad
> > instructions. I need to know if this is a overall issue with pacman lack
> > of support for this function or solely a config issue with my personal
> > setup.
> >
> > I think that IF pacman in its default form can work as it should with the
> > qubes proxy service that is what should be documented. But if it can not
> > work then I will include the instructions for setting up powerpill wrapper
> > on pacman to get it to function. So far powerpill is the only way I have
> > been able to get it to function properly thru qubes proxy service without
> > opening up access to other apps there by breaking the proxy's security
> > function
> >
> > You can also see my comments on the error output I have been getting with
> > pacman trying to use the XferCommand in the user list archlinux thread.
> >
> > Those are the only things holding me back from sending the pull request.
> >
> >
> > Cheers,
> >
> >
> > Tim
> >
> >
> >
> My builder.conf has been generated with the 'setup' python script. The
> override.conf is necessary because 'setup' does not add the 'DISTS_VM +=
> archlinux' line to builder.conf.
> Fixing that bug in setup should not be that hard but I didn't yet have a
> closer look at the setup script.
>
Well I see why you guys like to use the builder setup scripts. Way less
work vs manually setting up the builder.conf. I quickly looked thru the
setup script.
After things I noticed:
First I could not find the association for the need to have fc23 checked
off.
Now looking at your builder.conf from ./setup I noticed yours is release
3 not 3.1. I thought you were on 3.1? Not sure how much it matter either
way. I chose the 3.1 choice as it was defaulted in the ./setup choice.
I also found I could not get fc23 unchecked or it would give me the error
saying it was listed by not a chosen template and you either had to go back
and chose it or cancel as you stated. I did uncheck salt as we are not
actually building fc23 and archlinux does not employ it.
Next was the need for override.conf. I created it in the qubes-builder
root and before running ./setup. But I noticed that unlike your
builder.conf mine actually did add the 'DISTS_VM = archlinux' line to my
builder.conf. So I do not think I actually need the override but I am not
sure it hurts anything either.
I ran all the qubes-vm components individually and all finsihed fine.
But I still ran into a issue with the final make template.
It errored with the following:
-------------------------------------------------------------------------------------------------------------
[user@development qubes-builder]$ make linux-template-builder
mkdir -p
/home/user/qubes-builder/qubes-src/linux-template-builder/pkgs-for-template/archlinux/pkgs
for arch_build_dir in archlinux; do\
pkgnames=`cat qubes-src/vmm-xen/$arch_build_dir/PKGBUILD | grep pkgname
> cut -d "=" -f 2 | tr -d '()"'`;\
for pkgname in $pkgnames; do\
ln -f qubes-src/vmm-xen/pkgs/$pkgname-*.pkg.tar.xz
/home/user/qubes-builder/qubes-src/linux-template-builder/pkgs-for-template/archlinux/pkgs/;\
done;\
done;\
mkdir -p
/home/user/qubes-builder/qubes-src/linux-template-builder/pkgs-for-template/archlinux/pkgs
for arch_build_dir in archlinux; do\
pkgnames=`cat qubes-src/core-vchan-xen/$arch_build_dir/PKGBUILD | grep
pkgname | cut -d "=" -f 2 | tr -d '()"'`;\
for pkgname in $pkgnames; do\
ln -f qubes-src/core-vchan-xen/pkgs/$pkgname-*.pkg.tar.xz
/home/user/qubes-builder/qubes-src/linux-template-builder/pkgs-for-template/archlinux/pkgs/;\
done;\
done;\
mkdir -p
/home/user/qubes-builder/qubes-src/linux-template-builder/pkgs-for-template/archlinux/pkgs
for arch_build_dir in archlinux; do\
pkgnames=`cat qubes-src/core-qubesdb/$arch_build_dir/PKGBUILD | grep
pkgname | cut -d "=" -f 2 | tr -d '()"'`;\
for pkgname in $pkgnames; do\
ln -f qubes-src/core-qubesdb/pkgs/$pkgname-*.pkg.tar.xz
/home/user/qubes-builder/qubes-src/linux-template-builder/pkgs-for-template/archlinux/pkgs/;\
done;\
done;\
mkdir -p
/home/user/qubes-builder/qubes-src/linux-template-builder/pkgs-for-template/archlinux/pkgs
for arch_build_dir in archlinux; do\
pkgnames=`cat qubes-src/linux-utils/$arch_build_dir/PKGBUILD | grep
pkgname | cut -d "=" -f 2 | tr -d '()"'`;\
for pkgname in $pkgnames; do\
ln -f qubes-src/linux-utils/pkgs/$pkgname-*.pkg.tar.xz
/home/user/qubes-builder/qubes-src/linux-template-builder/pkgs-for-template/archlinux/pkgs/;\
done;\
done;\
mkdir -p
/home/user/qubes-builder/qubes-src/linux-template-builder/pkgs-for-template/archlinux/pkgs
for arch_build_dir in archlinux; do\
pkgnames=`cat qubes-src/core-agent-linux/$arch_build_dir/PKGBUILD |
grep pkgname | cut -d "=" -f 2 | tr -d '()"'`;\
for pkgname in $pkgnames; do\
ln -f qubes-src/core-agent-linux/pkgs/$pkgname-*.pkg.tar.xz
/home/user/qubes-builder/qubes-src/linux-template-builder/pkgs-for-template/archlinux/pkgs/;\
done;\
done;\
mkdir -p
/home/user/qubes-builder/qubes-src/linux-template-builder/pkgs-for-template/archlinux/pkgs
for arch_build_dir in archlinux; do\
pkgnames=`cat qubes-src/gui-common/$arch_build_dir/PKGBUILD | grep
pkgname | cut -d "=" -f 2 | tr -d '()"'`;\
for pkgname in $pkgnames; do\
ln -f qubes-src/gui-common/pkgs/$pkgname-*.pkg.tar.xz
/home/user/qubes-builder/qubes-src/linux-template-builder/pkgs-for-template/archlinux/pkgs/;\
done;\
done;\
mkdir -p
/home/user/qubes-builder/qubes-src/linux-template-builder/pkgs-for-template/archlinux/pkgs
for arch_build_dir in archlinux; do\
pkgnames=`cat qubes-src/gui-agent-linux/$arch_build_dir/PKGBUILD | grep
pkgname | cut -d "=" -f 2 | tr -d '()"'`;\
for pkgname in $pkgnames; do\
ln -f qubes-src/gui-agent-linux/pkgs/$pkgname-*.pkg.tar.xz
/home/user/qubes-builder/qubes-src/linux-template-builder/pkgs-for-template/archlinux/pkgs/;\
done;\
done;\
-> Building template archlinux (logfile:
build-logs/template-archlinux.log)...
**
*ERROR:pkttyagent.c:155:main: assertion failed:
(polkit_unix_process_get_start_time (POLKIT_UNIX_PROCESS (subject)) >
0)**ERROR:pkttyagent.c:155:main: assertion failed:
(polkit_unix_process_get_start_time (POLKIT_UNIX_PROCESS (subject)) > 0)*
--> Done.
[user@development qubes-builder]$
-----------------------------------------------------------------------------------------------------------------------
I thought it would give me a bit more on the error like a directory or file
not found. Only thing I could find on this with archlinux was dealing with
video driver maybe something on qt?
I am attaching my builder.conf file so you can see:
I am going to rerun and doc the setup script choices I make but not sure
that would have to do with this.
Cheers,
Tim
--
You received this message because you are subscribed to the Google Groups \
"qubes-devel" group. To unsubscribe from this group and stop receiving emails from \
it, send an email to qubes-devel+unsubscribe@googlegroups.com. To post to this group, \
send email to qubes-devel@googlegroups.com. To view this discussion on the web visit \
https://groups.google.com/d/msgid/qubes-devel/43ae839f-e5c9-460f-8c00-c281f5007534%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[Attachment #5 (text/html)]
<div dir="ltr"><br><br>On Sunday, January 31, 2016 at 11:45:39 AM UTC-5, \
sudod...@gmail.com wrote:<blockquote class="gmail_quote" style="margin: \
0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;"><div \
dir="ltr"><br><br>Am Samstag, 30. Januar 2016 02:29:42 UTC+1 schrieb TimW:<blockquote \
class="gmail_quote" style="margin:0;margin-left:0.8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr"><br><br>On Thursday, January 28, 2016 at \
9:00:51 PM UTC-5, <a>sudod...@gmail.com</a> wrote:<blockquote class="gmail_quote" \
style="margin:0;margin-left:0.8ex;border-left:1px #ccc \
solid;padding-left:1ex"><br><br>Am Mittwoch, 27. Januar 2016 05:35:06 UTC+1 schrieb \
TimW:<blockquote class="gmail_quote" \
style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex"><div \
dir="ltr"><br><br>On Tuesday, January 26, 2016 at 9:39:30 PM UTC-5, TimW \
wrote:<blockquote class="gmail_quote" \
style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex"><div \
dir="ltr"><br><br>On Tuesday, January 26, 2016 at 6:56:12 PM UTC-5, TimW \
wrote:<blockquote class="gmail_quote" \
style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex">Once \
that is done can you post the build.conf file on here so I can add it to the doc to \
replace that huge thing I have in there presently \
lol<br></blockquote><div><br><br>Yes I really do need that current build file as \
currently the old one does not work at all now. I can not get past make \
install-deps or get-sources.<br><br>I will start to work on copying that install Doc \
into a fork pull request. FYI its a first for me so I may have some questions \
if I get stuck.<br></div></div></blockquote><div><br><br><br>What page do we actually \
want to update with these changes. Right now we have the archlinux template page \
which really is nothing more than a place holder with a link taking you to the \
general template building page which is using some basic instructions using archlinux \
as the example. Its all the links at the bottom that really show you how to build \
it. <br><br>My thought is to put these changes in the actual Archlinux template \
page. Unless Qubes plans on making this a supported template with a binary package \
that is always kept current like the Fedora and Debain is. <br><br>The other \
possible situation effecting the above is below:<br><br>I wanted to understand is how \
are older Qubes versions handled? How long does Qubes support past version \
of templates? As these templates (archlinux, ubuntu, etc ) are user supported vs \
Qubes ITL supported are there support guidelines it would be preferred to follow in \
these cases? Should someone be able to follow direction and get a working Archlinux \
template for R2? Or are the changes that are being made to get working templates \
for 3.1 and archlinux breaking the process for those on older versions? Sorry it \
may just be my ignorance to how this is already being handles and is a non issue. I \
do not know. <br><br><br><br><br><br><br></div></div></blockquote><div><br>I'd \
put the doc on this page: <a href="https://www.qubes-os.org/doc/templates/archlinux/" \
rel="nofollow" target="_blank" \
onmousedown="this.href='https://www.google.com/url?q\75https%3A%2F%2Fwww.qubes-os. \
org%2Fdoc%2Ftemplates%2Farchlinux%2F\46sa\75D\46sntz\0751\46usg\75AFQjCNE0Yc3Wk1oiW7ZIOAjt57sE5yND2g';return \
true;" onclick="this.href='https://www.google.com/url?q\75https%3A%2F%2Fwww.qubes- \
os.org%2Fdoc%2Ftemplates%2Farchlinux%2F\46sa\75D\46sntz\0751\46usg\75AFQjCNE0Yc3Wk1oiW7ZIOAjt57sE5yND2g';return \
true;">https://www.qubes-os.org/doc/<wbr>templates/archlinux/</a> and remove the \
other page (<a href="https://www.qubes-os.org/doc/building-archlinux-template/" \
rel="nofollow" target="_blank" \
onmousedown="this.href='https://www.google.com/url?q\75https%3A%2F%2Fwww.qubes-os. \
org%2Fdoc%2Fbuilding-archlinux-template%2F\46sa\75D\46sntz\0751\46usg\75AFQjCNEIy2QArMKq0eJxe9c7pG3k1n6NXA';return \
true;" onclick="this.href='https://www.google.com/url?q\75https%3A%2F%2Fwww.qubes- \
os.org%2Fdoc%2Fbuilding-archlinux-template%2F\46sa\75D\46sntz\0751\46usg\75AFQjCNEIy2QArMKq0eJxe9c7pG3k1n6NXA';return \
true;">https://www.qubes-os.org/doc/<wbr>building-archlinux-template/</a>).<br><br>For \
the different verions: Have a look at <a \
href="https://groups.google.com/forum/#!searchin/qubes-devel/support/qubes-devel/wySWr9h1QwU/0_IRCZ5TBgAJ" \
rel="nofollow" target="_blank" \
onmousedown="this.href='https://groups.google.com/forum/#!searchin/qubes-devel/support/qubes-devel/wySWr9h1QwU/0_IRCZ5TBgAJ';return \
true;" onclick="this.href='https://groups.google.com/forum/#!searchin/qubes-devel/support/qubes-devel/wySWr9h1QwU/0_IRCZ5TBgAJ';return \
true;">https://groups.google.com/<wbr>forum/#!searchin/qubes-devel/<wbr>support/qubes-devel/<wbr>wySWr9h1QwU/0_IRCZ5TBgAJ</a>.<br>I \
think there is not enough capacity to guarantee long term support and we'd better \
stick to the most current stable release. This is also the Arch way. Cutting-edge \
software, rolling release but not really \
LTS.<br></div></blockquote><div><br><br>Awesome. That is what I thought as well \
given all the changes. I was thinking it would make it very cluttered or make for \
too many pages it we started leaving the support for all the past Qubes ver and there \
issues. Most of the past issues are now all gone with the current.<br><br>I have \
finished all but just a few things.<br><br>It took a bit of time for me to turn the \
odt and rewrite it into the .md. I had to host all the screen shots. Then I \
had to learn the formatting and syntax of .md git style files. I ended up finding \
using a local markdown text editor locally the easiest way. I found ReText to \
be the best combo of basic and ease of use plus all the functions needed. I \
posted about it in the documentation thread in the user \
list.<br><br><br><b>sudod..</b><br><br><b>Can you please post what you current build \
file is. ( complete).</b> I need to put that in place of the original ( now not \
functional) one you posted in the user archlinux thread. I want to get some \
screenshots of the output of the final template creation. <br><br><br><b>I also \
still need someone to test the: <br><br><span style="color:rgb(0,0,255)">XferCommand \
= http_proxy=<a href="http://10.137.255.254:8082" rel="nofollow" target="_blank" \
onmousedown="this.href='http://www.google.com/url?q\75http%3A%2F%2F10.137.255.254% \
3A8082\46sa\75D\46sntz\0751\46usg\75AFQjCNFzBw6SYzTOumlCu6upB65J0GkwVw';return \
true;" onclick="this.href='http://www.google.com/url?q\75http%3A%2F%2F10.137.255.2 \
54%3A8082\46sa\75D\46sntz\0751\46usg\75AFQjCNFzBw6SYzTOumlCu6upB65J0GkwVw';return \
true;">10.137.255.254:8082</a> /usr/bin/curl -C - -f %u > %o</span></b><span \
style="color:rgb(0,0,255)"><br></span><br>Currently it does not work for me and I do \
not want to include bad instructions. I need to know if this is a overall issue \
with pacman lack of support for this function or solely a config issue with my \
personal setup. <br><br>I think that IF pacman in its default form can work as it \
should with the qubes proxy service that is what should be documented. But if it \
can not work then I will include the instructions for setting up powerpill wrapper on \
pacman to get it to function. So far powerpill is the only way I have been able to \
get it to function properly thru qubes proxy service without opening up access to \
other apps there by breaking the proxy's security function<br><br>You can also \
see my comments on the error output I have been getting with pacman trying to use the \
XferCommand in the user list archlinux thread.<br><br>Those are the only things \
holding me back from sending the pull \
request.<br><br><br>Cheers,<br><br><br>Tim<br><br><br></div></div></blockquote><div><br>My \
builder.conf has been generated with the 'setup' python script. The \
override.conf is necessary because 'setup' does not add the 'DISTS_VM += \
archlinux' line to builder.conf.<br>Fixing that bug in setup should not be that \
hard but I didn't yet have a closer look at the setup \
script.<br></div></div></blockquote><div><br><br>Well I see why you guys like to use \
the builder setup scripts. Way less work vs manually setting up the builder.conf. \
I quickly looked thru the setup script. <br><br>After things I \
noticed:<br><br>First I could not find the association for the need to have fc23 \
checked off.<br><br>Now looking at your builder.conf from ./setup I noticed yours \
is release 3 not 3.1. I thought you were on 3.1? Not sure how much it matter \
either way. I chose the 3.1 choice as it was defaulted in the ./setup \
choice.<br><br>I also found I could not get fc23 unchecked or it would give me the \
error saying it was listed by not a chosen template and you either had to go back and \
chose it or cancel as you stated. I did uncheck salt as we are not actually \
building fc23 and archlinux does not employ it.<br><br>Next was the need for \
override.conf. I created it in the qubes-builder root and before running \
./setup. But I noticed that unlike your builder.conf mine actually did add the \
'DISTS_VM = archlinux' line to my builder.conf. So I do not think I \
actually need the override but I am not sure it hurts anything either.<br><br>I ran \
all the qubes-vm components individually and all finsihed fine.<br><br>But I still \
ran into a issue with the final make template.<br><br>It errored with the \
following:<br>-------------------------------------------------------------------------------------------------------------<br>[user@development \
qubes-builder]$ make linux-template-builder<br>mkdir -p \
/home/user/qubes-builder/qubes-src/linux-template-builder/pkgs-for-template/archlinux/pkgs<br>for \
arch_build_dir in archlinux; do\<br> pkgnames=`cat \
qubes-src/vmm-xen/$arch_build_dir/PKGBUILD | grep pkgname | cut -d "=" -f 2 \
| tr -d '()"'`;\<br> for pkgname in $pkgnames; do\<br> \
ln -f qubes-src/vmm-xen/pkgs/$pkgname-*.pkg.tar.xz \
/home/user/qubes-builder/qubes-src/linux-template-builder/pkgs-for-template/archlinux/pkgs/;\<br> \
done;\<br>done;\<br><br>mkdir -p \
/home/user/qubes-builder/qubes-src/linux-template-builder/pkgs-for-template/archlinux/pkgs<br>for \
arch_build_dir in archlinux; do\<br> pkgnames=`cat \
qubes-src/core-vchan-xen/$arch_build_dir/PKGBUILD | grep pkgname | cut -d \
"=" -f 2 | tr -d '()"'`;\<br> for pkgname in $pkgnames; \
do\<br> ln -f qubes-src/core-vchan-xen/pkgs/$pkgname-*.pkg.tar.xz \
/home/user/qubes-builder/qubes-src/linux-template-builder/pkgs-for-template/archlinux/pkgs/;\<br> \
done;\<br>done;\<br><br>mkdir -p \
/home/user/qubes-builder/qubes-src/linux-template-builder/pkgs-for-template/archlinux/pkgs<br>for \
arch_build_dir in archlinux; do\<br> pkgnames=`cat \
qubes-src/core-qubesdb/$arch_build_dir/PKGBUILD | grep pkgname | cut -d "=" \
-f 2 | tr -d '()"'`;\<br> for pkgname in $pkgnames; do\<br> \
ln -f qubes-src/core-qubesdb/pkgs/$pkgname-*.pkg.tar.xz \
/home/user/qubes-builder/qubes-src/linux-template-builder/pkgs-for-template/archlinux/pkgs/;\<br> \
done;\<br>done;\<br><br>mkdir -p \
/home/user/qubes-builder/qubes-src/linux-template-builder/pkgs-for-template/archlinux/pkgs<br>for \
arch_build_dir in archlinux; do\<br> pkgnames=`cat \
qubes-src/linux-utils/$arch_build_dir/PKGBUILD | grep pkgname | cut -d "=" \
-f 2 | tr -d '()"'`;\<br> for pkgname in $pkgnames; do\<br> \
ln -f qubes-src/linux-utils/pkgs/$pkgname-*.pkg.tar.xz \
/home/user/qubes-builder/qubes-src/linux-template-builder/pkgs-for-template/archlinux/pkgs/;\<br> \
done;\<br>done;\<br><br>mkdir -p \
/home/user/qubes-builder/qubes-src/linux-template-builder/pkgs-for-template/archlinux/pkgs<br>for \
arch_build_dir in archlinux; do\<br> pkgnames=`cat \
qubes-src/core-agent-linux/$arch_build_dir/PKGBUILD | grep pkgname | cut -d \
"=" -f 2 | tr -d '()"'`;\<br> for pkgname in $pkgnames; \
do\<br> ln -f qubes-src/core-agent-linux/pkgs/$pkgname-*.pkg.tar.xz \
/home/user/qubes-builder/qubes-src/linux-template-builder/pkgs-for-template/archlinux/pkgs/;\<br> \
done;\<br>done;\<br><br>mkdir -p \
/home/user/qubes-builder/qubes-src/linux-template-builder/pkgs-for-template/archlinux/pkgs<br>for \
arch_build_dir in archlinux; do\<br> pkgnames=`cat \
qubes-src/gui-common/$arch_build_dir/PKGBUILD | grep pkgname | cut -d "=" \
-f 2 | tr -d '()"'`;\<br> for pkgname in $pkgnames; do\<br> \
ln -f qubes-src/gui-common/pkgs/$pkgname-*.pkg.tar.xz \
/home/user/qubes-builder/qubes-src/linux-template-builder/pkgs-for-template/archlinux/pkgs/;\<br> \
done;\<br>done;\<br><br>mkdir -p \
/home/user/qubes-builder/qubes-src/linux-template-builder/pkgs-for-template/archlinux/pkgs<br>for \
arch_build_dir in archlinux; do\<br> pkgnames=`cat \
qubes-src/gui-agent-linux/$arch_build_dir/PKGBUILD | grep pkgname | cut -d \
"=" -f 2 | tr -d '()"'`;\<br> for pkgname in $pkgnames; \
do\<br> ln -f qubes-src/gui-agent-linux/pkgs/$pkgname-*.pkg.tar.xz \
/home/user/qubes-builder/qubes-src/linux-template-builder/pkgs-for-template/archlinux/pkgs/;\<br> \
done;\<br>done;\<br><br>-> Building template archlinux (logfile: \
build-logs/template-archlinux.log)...<br>**<br><b><span style="color: rgb(0, 0, \
255);">ERROR:pkttyagent.c:155:main: assertion failed: \
(polkit_unix_process_get_start_time (POLKIT_UNIX_PROCESS (subject)) > \
0)<br>**<br>ERROR:pkttyagent.c:155:main: assertion failed: \
(polkit_unix_process_get_start_time (POLKIT_UNIX_PROCESS (subject)) > \
0)</span></b><br>--> Done.<br>[user@development qubes-builder]$ \
<br>-----------------------------------------------------------------------------------------------------------------------<br><br>I \
thought it would give me a bit more on the error like a directory or file not found. \
Only thing I could find on this with archlinux was dealing with video driver maybe \
something on qt?<br><br>I am attaching my builder.conf file so you can see:<br><br>I \
am going to rerun and doc the setup script choices I make but not sure that would \
have to do with this.<br><br>Cheers,<br><br>Tim<br><br><br></div></div>
<p></p>
-- <br />
You received this message because you are subscribed to the Google Groups \
"qubes-devel" group.<br /> To unsubscribe from this group and stop \
receiving emails from it, send an email to <a \
href="mailto:qubes-devel+unsubscribe@googlegroups.com">qubes-devel+unsubscribe@googlegroups.com</a>.<br \
/> To post to this group, send email to <a \
href="mailto:qubes-devel@googlegroups.com">qubes-devel@googlegroups.com</a>.<br /> To \
view this discussion on the web visit <a \
href="https://groups.google.com/d/msgid/qubes-devel/43ae839f-e5c9-460f-8c00-c281f50075 \
34%40googlegroups.com?utm_medium=email&utm_source=footer">https://groups.google.com/d/ \
msgid/qubes-devel/43ae839f-e5c9-460f-8c00-c281f5007534%40googlegroups.com</a>.<br /> \
For more options, visit <a \
href="https://groups.google.com/d/optout">https://groups.google.com/d/optout</a>.<br \
/>
------=_Part_1689_530596425.1454298744557--
["builder.conf" (text/plain)]
# =============================================================================
# CONFIGURATION FILE FOR QUBES-BUILDER
# =============================================================================
#
# THIS CONFIGURATION FILE IS INDENDED TO ONLY BE USED WITH THE `setup` SCRIPT.
# -----------------------------------------------------------------------------
#
# This configuration file (`templates.conf`) will be linked to by `setup` as
# `builder.conf`. (ln -s example-configs/templates.conf builder.conf)
#
# To use the `setup` script, just run `setup` in the qubes-builder root
# directory. A series of dialogs will be presented prompting various
# configuration available and then all build configuration files will
# automatically be generated based on the options selected.
#
# `setup` can be re-run again at any time to change configuration options.
# Previous options selected will be retained to allow quick switching of
# branches, templates to build, etc.
#
# Setup uses the following as markers to indicate where to place configuration
# values:
# [=setup section start=] - Start inserting on the next line
# [=setup section end=] - Stop insert mode
#
# Anything between these markers will be replaced, therefore:
# - do not place any user configurations within these markers, or those
# configurations will be replaced next time setup is run
# - do not remove or modify the markers or setup will be unable to function
#
# -----------------------------------------------------------------------------
# CONFIGURATION FILES INCLUDED WITH THIS CONFIGURATION
# -----------------------------------------------------------------------------
# Other configuration files are also included to offer maximum flexibility. To
# determine which configuration files are actually being included when using
# this configuration file as a base, use the `about` target:
# `make about`
#
# The other configuration files included (if they exist which some of them are
# automatically generated by `setup`) are as follows:
# - example-configs/qubes-os-r2.conf: If RELEASE == 2; Default Release 2
# configuration file
# - example-configs/qubes-os-master.conf: If RELEASE == 3; Default Release 3
# configuration file
# - override.conf: `setup` will also offer to include `override.conf` if one
# exists. More information on `overrides` below.
# - example-configs/extended-rules.conf: Contains extra targets mostly for
# building templates
#
# -----------------------------------------------------------------------------
# ADDITIONAL OVERRIDES
# -----------------------------------------------------------------------------
# Instead of directly modifying this or any other `default` configuration
# file, an override.conf file can be placed in the `qubes-builder` root
# directory. `setup` will offer to include this file if it exists.
#
# The `override.conf` file can contain overrides to most any configuration
# option such as BRANCH, DEBUG, VERBOSE, etc.
#
# If you create `overrides` that are specific to a release version or custom
# branch you are working on, `setup` will also be able to identify overrides
# specific to the release and or branch.
#
# To create release / branch specific `overrides`, create an override
# configuration file and place it in the `example-configs` directory named
# as follows:
# 1) example-configs/r2-feature_branch-override.conf
# example-configs/r3-master-override.conf
#
# 2) example-configs/r3-feature_branch-override.conf
# example-configs/r3-master-override.conf
#
# 3) example-configs/feature_branch-override.conf
# example-configs/master-override.conf
#
# 4) example-configs/override.conf
#
# 5) override.conf
#
# Option 1 above would offer to include the override configuration file if you
# selected to build for Release 2 and are currently in the `feature_branch`
# branch.
#
# Option 2 is the same as Option 1 except for Release 3.
#
# Option 3 would use the same configuration override for both Release 2 and 3
# if you are currently in the `feature_branch` branch.
#
# If there is no release / branch specific override configuration and
# override.conf exists as in options 4, that will be available to select.
#
# Finally, an override.conf file in the `qubes-builder` root directory
# overrides all the above examples.
#
#
# A few additional notes and caveats on overrides:
#
# - The dialog to choose an override configuration is only presented on the
# initial run of `setup`. Once a `builder.conf` file created, there will be
# no further prompts. As indicated above, `setup` initially soft links
# `examples-config/templates.conf` to `builder.conf`. To overcome
# this limitation, simply delete the `builder.conf` soft link and then the
# override prompt will become available again when you re-run `setup`.
#
# - The `setup` script soft links any override configuration within the
# examples-config directory to overrides.conf. It will allow any soft linked
# override to be replaced with a newly selected override option, but will not
# allow an existing `override.conf` regular file to be overwritten that is
# in the `qubes-builder` root directory.
#
# -----------------------------------------------------------------------------
# All lines which begins with "#" are treated as comments
# Assignments can be made with VAR_NAME="VALUE"
# [=setup info start=]
################################################################################
#
# Qubes Release: 3.1
# Source Prefix: marmarek/qubes- (repo)
#
# Master Configuration File(s):
# qubes-os-master.conf templates.conf Makefile
#
# builder.conf copied from:
# /home/user/qubes-builder/example-configs/templates.conf
#
################################################################################
# [=setup info stop=]
RELEASE := 3.1
# SSH_ACCESS is used by `setup` to determine if ssh access mode was selected and
# will re-write the GIT_BASEURL and GIT_PREFIX variables to use ssh mode.
SSH_ACCESS := 0
GIT_BASEURL := https://github.com
GIT_PREFIX := marmarek/qubes-
# A Qubes master configuration file will be included based on selected RELEASE
#
# A copy of BUILDER_PLUGINS will be made and restored since the BUILDER_PLUGIN
# variable gets over-written in qubes-os-master.conf.
_ORIGINAL_BUILDER_PLUGINS := $(BUILDER_PLUGINS)
ifeq ($(RELEASE), 2)
-include example-configs/qubes-os-r2.conf
else ifeq ($(RELEASE), 3)
-include example-configs/qubes-os-r3.0.conf
else
-include example-configs/qubes-os-master.conf
endif
BUILDER_PLUGINS := $(_ORIGINAL_BUILDER_PLUGINS) $(BUILDER_PLUGINS)
# [=setup plugins start=]
# Enabled BUILDER_PLUGINS
BUILDER_PLUGINS :=
BUILDER_PLUGINS += builder-fedora
BUILDER_PLUGINS += builder-archlinux
# [=setup plugins stop=]
DEBUG = 0
VERBOSE = 0
NO_SIGN = 1
DIST_DOM0 ?= fc20
# Only build templates (comment out or set to '0' to build all of Qubes).
TEMPLATE_ONLY ?= 1
################################################################################
# S A L T M A N A G E M E N T O P T I O N S
################################################################################
# MGMT_SALT_ONLY - Build only mgmt-salt COMPONENTS
# Only mgmt-salt components will bw built when issuing 'make qubes[-vm/dom0]
# which is useful for developing.
#
# Set 1 to enable building only salt-mgmt COMPONENTS or clear value to build
# all qubes components including mgmt-salt.
# Default: novalue
#MGMT_SALT_ONLY = 1
# MGMT_SALT_COMPONENTS_USER - Custom mgmt-salt user components
# Add any extra user based mgmt-salt formula components to include in build.
# Default: novalue
#MGMT_SALT_COMPONENTS_USER =
################################################################################
# L I S T O F D I S T V M ' S
################################################################################
# Available template flavors may be added the the template build by appending
# `+flavor_name`
# [=setup dists start=]
ifneq "$(SETUP_MODE)" "1"
# Enabled DISTS_VMs
DISTS_VM :=
DISTS_VM += archlinux
endif
# [=setup dists stop=]
# List of all build template variations that will be offered in the 'setup'
# DISTS_VM dialog to be able to choose from
ifeq "$(SETUP_MODE)" "1"
DISTS_VM :=
DISTS_VM += fc20
DISTS_VM += fc20+minimal
DISTS_VM += fc20+fullyloaded
DISTS_VM += fc21
DISTS_VM += fc21+minimal
DISTS_VM += fc21+fullyloaded
DISTS_VM += fc23
DISTS_VM += fc23+minimal
DISTS_VM += fc23+fullyloaded
DISTS_VM += wheezy
DISTS_VM += wheezy+minimal
DISTS_VM += wheezy+gnome
DISTS_VM += jessie
DISTS_VM += jessie+minimal
DISTS_VM += jessie+gnome
DISTS_VM += stretch
DISTS_VM += stretch+minimal
DISTS_VM += stretch+gnome
DISTS_VM += trusty
DISTS_VM += trusty+desktop
DISTS_VM += utopic
DISTS_VM += utopic+desktop
DISTS_VM += vivid
DISTS_VM += vivid+desktop
endif
################################################################################
# T E M P L A T E A L I A S
################################################################################
# TEMPLATE_ALIAS can be used to choose a shorter name in DISTS_VM that
# include some other TEMPLATE_FLAVORs. A TEMPLATE_LABEL will automatically
# be created if one does not exist that will use the alias name as the
# tempalte name. Plus signs (+) will be converted to hyphens (-).
ifneq (,$(findstring wheezy, $(DISTS_VM))$(findstring jessie, \
$(DISTS_VM))$(findstring stretch, $(DISTS_VM))) TEMPLATE_ALIAS += \
wheezy:wheezy+standard TEMPLATE_ALIAS += wheezy+gnome:wheezy+gnome+standard
TEMPLATE_ALIAS += wheezy+minimal:wheezy+minimal+no-recommends
TEMPLATE_ALIAS += jessie:jessie+standard
TEMPLATE_ALIAS += jessie+gnome:jessie+gnome+standard
TEMPLATE_ALIAS += jessie+minimal:jessie+minimal+no-recommends
TEMPLATE_ALIAS += stretch:stretch+standard
TEMPLATE_ALIAS += stretch+gnome:stretch+gnome+standard
TEMPLATE_ALIAS += stretch+minimal:stretch+minimal+no-recommends
endif
################################################################################
# T E M P L A T E C O N F I G U R A T I O N
################################################################################
# TEMPLATE_LABEL allows control over the final template name. There is a limit
# of 31 characters for the final template name
#
# TEMPLATE_LABE += <DIST_VM name as listed above>:<desired final template name>
TEMPLATE_LABEL ?=
# Location of templates flavors that are not in default location.
# Example: wheezy+whonix-gateway would normally be in
# (Don't Place in {curly} brackets; ending curly gets cut off
# $$SCRIPTSDIR/wheezy+whonix-gateway
# -or- $$SCRIPTSDIR/wheezy
TEMPLATE_FLAVOR_DIR :=
TEMPLATE_FLAVOR_DIR += +gnome:$$SCRIPTSDIR/gnome
TEMPLATE_FLAVOR_DIR += +flash:$$SCRIPTSDIR/flash
TEMPLATE_FLAVOR_DIR += +desktop:$$SCRIPTSDIR/desktop
################################################################################
# T E M P L A T E C O M P O N E N T S
################################################################################
# Contains a list of components when only building templates. Note the build
# order is very important
TEMPLATE :=
TEMPLATE += vmm-xen
TEMPLATE += core-vchan-xen
ifneq ($(RELEASE), 2)
TEMPLATE += core-qubesdb
endif
TEMPLATE += linux-utils
TEMPLATE += core-agent-linux
TEMPLATE += gui-common
TEMPLATE += gui-agent-linux
TEMPLATE += app-linux-split-gpg
TEMPLATE += app-linux-tor
TEMPLATE += app-thunderbird
TEMPLATE += app-linux-pdf-converter
TEMPLATE += app-linux-img-converter
TEMPLATE += app-linux-input-proxy
TEMPLATE += $(MGMT_COMPONENTS)
TEMPLATE += linux-template-builder
################################################################################
# O V E R R I D E B R A N C H L O C A T I O N S
################################################################################
# Not yet available in 'QubesOS' repo
GIT_URL_template_whonix = $(GIT_BASEURL)/marmarek/qubes-template-whonix.git
# Not yet available in 'marmarek' repo
GIT_URL_mgmt_salt = $(GIT_BASEURL)/QubesOS/qubes-mgmt-salt.git
GIT_URL_mgmt_salt_base = $(GIT_BASEURL)/QubesOS/qubes-mgmt-salt-base.git
GIT_URL_mgmt_salt_base_config = \
$(GIT_BASEURL)/QubesOS/qubes-mgmt-salt-base-config.git \
GIT_URL_mgmt_salt_base_overrides = \
$(GIT_BASEURL)/QubesOS/qubes-mgmt-salt-base-overrides.git GIT_URL_mgmt_salt_base_topd \
= $(GIT_BASEURL)/QubesOS/qubes-mgmt-salt-base-topd.git GIT_URL_mgmt_salt_dom0_qvm = \
$(GIT_BASEURL)/QubesOS/qubes-mgmt-salt-dom0-qvm.git GIT_URL_mgmt_salt_dom0_update = \
$(GIT_BASEURL)/QubesOS/qubes-mgmt-salt-dom0-update.git \
GIT_URL_mgmt_salt_dom0_virtual_machines = \
$(GIT_BASEURL)/QubesOS/qubes-mgmt-salt-dom0-virtual-machines.git
################################################################################
# M I S C E L L A N E O U S
################################################################################
# Qubes-builder deps
DEPENDENCIES ?=
DEPENDENCIES += git rpmdevtools rpm-build createrepo
# Additional for debian template
DEPENDENCIES += debootstrap dpkg-dev
# for ./setup
DEPENDENCIES += python-sh dialog
# Uncomment the the following to enable override.conf include. Setup will
# automatically enable it only if an override is available and selected by
# user to enable.
INCLUDE_OVERRIDE_CONF ?= true
ifdef INCLUDE_OVERRIDE_CONF
-include override.conf
endif
.PHONY: about release
about::
@echo "templates.conf"
release:
@echo "$(RELEASE)"
# vim: filetype=make
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic