[qubes-users] Re: QubesOS weekly builds

[Frédéric Pierret]

Hi,

Le 3/21/21 à 11:33 PM, Frédéric Pierret a écrit :

Hi,
As some of you may know, months(years?) ago, I've setup a pipeline that is 
automatically PR latest kernels for Qubes OS and more recently, pulseaudio 
headers too. This is done every week.

At some point, I added the build of ISO including kernel-latest for users who 
were having issues with latest hardware. I stopped it quickly because we were 
merging more and more kernel versions thank to the help of automatic PR and 
Qubes point releases.

Due to recent troubles with kernels 5.4.X and 5.10.X, I've decided to add again 
to this weekly pipeline, the build of a fresh Qubes R4.1 ISO. I don't build any 
package or any template. It uses only Qubes OS repositories. The qubes-builder 
conf is: 
https://github.com/QubesOS/qubes-release-configs/blob/master/R4.1/qubes-os-iso-full-online.conf
 and the kickstart can be found here: 
https://github.com/QubesOS/qubes-installer-qubes-os/blob/master/conf/iso-full-online.ks.

Please note that, contrary to my first attempt, I don't include kernel-latest kernels. 
It's a standard R4.1 ISO as if Marek would release one. It is built in a dedicated AppVM 
together with Split GPG. The ISOs are signed by "fepitre-bot" 
1C8714D640F30457EC953050656946BA873DDEC1. Some of you already download latest R4.1 devel 
ISOs in openQA but they are not signed and not necessary built in a safe environment 
because it's only for CI purposes. That's a solution between CI ISOs and R4.1 alpha 
release.

That said, the ISO(s) can be found on my self hosted server: 
https://qubes.notset.fr/iso/.

Best regards,
Frédéric



I've added support to qubes-builder the possibility to build an ISO having the 
installer running kernel-latest and the installed QubesOS too. For 
documentation: 
https://github.com/QubesOS/qubes-builder/blob/master/doc/Configuration.md#iso_use_kernel_latest
 (pretty simple, isn't it?)

I'm pleased to announce you that I've added that to my weekly build pipeline where I will 
still build both versions: the standard and the one with kernel-latest embedded. Same as 
previously, you can find signed ISOs here https://qubes.notset.fr/iso/ and also result of 
openQA tests too (see openqa.qubes-os.org with build tag having -kernel-latest. For 
example: 
https://openqa.qubes-os.org/tests/overview?build=20210610-kernel-latest-4.1=qubesos=4.1=1).

The goal is still the same: providing testing QubesOS images built in a sane 
environment for latest drivers support by Linux until LTS kernels would have 
enough backports for very recent hardware.

A final remark like on the Discourse thread, I do recurrent cleaning for space 
consideration. I keep only ISOs for the current month now.

Best regards,
Frédéric

--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/5068b322-bda1-f92b-cbed-023a9f925692%40qubes-os.org.


OpenPGP_signature
Description: OpenPGP digital signature

Re: [qubes-users] Re: QubesOS weekly builds

[Frédéric Pierret]

Le 3/22/21 à 2:03 AM, Beto HydroxyButyrate a écrit :

Trying to use the info provided to kick off my own ISO build.
This posted links to does not use the `QubesBuilder` approach, as it references 
stuff apparently checked out to ~/qubes-src, rather than 
~/qubes-builder/qubes-src.

Is this different approach to building documented?  What else should  check out to 
~/qubes-src?  How does this fit into the "Development Workflow"?

Per those docs:

/Qubes is split into a bunch of git repos. This are *_all _*contained in the 
qubes-src directory under qubes-builder. Subdirectories there are separate 
components, stored in separate git repositories./
/
/
Just making ~/qubes-src a symbolic link to ~/qubes-builder/qubes-src does not 
fix things as, despite the claim that /this are all contained/  in 
~/qubes-builder/qubes-src, the two new git repos referenced are not contained 
there.



I forgot to mention also that the reference used in builder.conf for 
INSTALLER_KICKSTART=ZZZ is a path under the build chroot and not to your local 
qubes-builder. The build chroot has sources from qubes-builder/qubes-src copied 
to chroot-dom0-fcXX/home/user/qubes-src. The value for the kickstart is then 
used when build is ran under the chroot. That probably deserves a note in the 
doc if it's not the case.

Frédéric

--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/e5620fdb-2379-f1ec-c85b-4ba44bd1d3fb%40qubes-os.org.


OpenPGP_signature
Description: OpenPGP digital signature

Re: [qubes-users] Re: QubesOS weekly builds

[Frédéric Pierret]

Le 3/22/21 à 2:03 AM, Beto HydroxyButyrate a écrit :

Trying to use the info provided to kick off my own ISO build.
This posted links to does not use the `QubesBuilder` approach, as it references 
stuff apparently checked out to ~/qubes-src, rather than 
~/qubes-builder/qubes-src.

Is this different approach to building documented?  What else should  check out to 
~/qubes-src?  How does this fit into the "Development Workflow"?




Due to recent troubles with kernels 5.4.X and 5.10.X, I've decided to add again to this 
weekly pipeline, the build of a fresh Qubes R4.1 ISO. I don't build any package or any 
template. It uses only Qubes OS repositories. The qubes-builder conf is: 
https://github.com/QubesOS/qubes-release-configs/blob/master/R4.1/qubes-os-iso-full-online.conf
 

 and the kickstart can be found here: 
https://github.com/QubesOS/qubes-installer-qubes-os/blob/master/conf/iso-full-online.ks 
.


It's written "qubes-builder" conf. So use this as builder.conf and that's all: 
make iso. The kickstart reference provided is the one used by this conf: 
https://github.com/QubesOS/qubes-release-configs/blob/master/R4.1/qubes-os-iso-full-online.conf#L24.
 Meaning the installer will use the file in installer-qubes-os sources: 
https://github.com/QubesOS/qubes-installer-qubes-os/blob/master/conf/iso-full-online.ks

Frédéric

--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/95429f87-1632-15d3-a7e1-8285407eec56%40qubes-os.org.


OpenPGP_signature
Description: OpenPGP digital signature

[qubes-users] Re: QubesOS weekly builds

[Beto HydroxyButyrate]

Trying to use the info provided to kick off my own ISO build.
This posted links to does not use the `QubesBuilder` approach, as it 
references stuff apparently checked out to ~/qubes-src, rather than 
~/qubes-builder/qubes-src.

Is this different approach to building documented?  What else should  check 
out to ~/qubes-src?  How does this fit into the "Development Workflow"?

Per those docs:

*Qubes is split into a bunch of git repos. This are all contained in the 
qubes-src directory under qubes-builder. Subdirectories there are separate 
components, stored in separate git repositories.*

Just making ~/qubes-src a symbolic link to ~/qubes-builder/qubes-src does 
not fix things as, despite the claim that *this are all contained*  in 
~/qubes-builder/qubes-src, the two new git repos referenced are not 
contained there.

[user@qubes-build qubes-src]$ pwd
/home/user/qubes-builder/qubes-src
[user@qubes-build qubes-src]$ ls qubes-release-configs
ls: cannot access 'qubes-release-configs': No such file or directory
[user@qubes-build qubes-src]$ ls qubes-installer-qubes-os
ls: cannot access 'qubes-installer-qubes-os': No such file or directory
[user@qubes-build qubes-src]$ ls ~/qubes-src
ls: cannot access '/home/user/qubes-src': No such file or directory



On Monday, 22 March 2021 at 09:33:20 UTC+11 Frédéric Pierret wrote:

> Hi,
> As some of you may know, months(years?) ago, I've setup a pipeline that is 
> automatically PR latest kernels for Qubes OS and more recently, pulseaudio 
> headers too. This is done every week.
>
> At some point, I added the build of ISO including kernel-latest for users 
> who were having issues with latest hardware. I stopped it quickly because 
> we were merging more and more kernel versions thank to the help of 
> automatic PR and Qubes point releases.
>
> Due to recent troubles with kernels 5.4.X and 5.10.X, I've decided to add 
> again to this weekly pipeline, the build of a fresh Qubes R4.1 ISO. I don't 
> build any package or any template. It uses only Qubes OS repositories. The 
> qubes-builder conf is: 
> https://github.com/QubesOS/qubes-release-configs/blob/master/R4.1/qubes-os-iso-full-online.conf
>  
> and the kickstart can be found here: 
> https://github.com/QubesOS/qubes-installer-qubes-os/blob/master/conf/iso-full-online.ks
> .
>
> Please note that, contrary to my first attempt, I don't include 
> kernel-latest kernels. It's a standard R4.1 ISO as if Marek would release 
> one. It is built in a dedicated AppVM together with Split GPG. The ISOs are 
> signed by "fepitre-bot" 1C8714D640F30457EC953050656946BA873DDEC1. Some of 
> you already download latest R4.1 devel ISOs in openQA but they are not 
> signed and not necessary built in a safe environment because it's only for 
> CI purposes. That's a solution between CI ISOs and R4.1 alpha release.
>
> That said, the ISO(s) can be found on my self hosted server: 
> https://qubes.notset.fr/iso/.
>
> Best regards,
> Frédéric
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/a09d0823-dc8e-4edf-99d0-cdcc5296a2d4n%40googlegroups.com.