-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Sat, Mar 21, 2020 at 02:09:22PM -0700, altaway wrote:
> Hello Marek,
>
> How your builder.conf file looks like? Especially those entries:
> > - DIST_DOM0
> > - USE_QUBES_VERISON_REPO
> > - RELEASE
> >
>
> DIST_DOM0 ?= fc31
> USE_QUBES_REPO_VERSION = $(RELEASE)
I would also add "USE_QUBES_REPO_TESTING = 1", as many packages for R4.1
are still in testing repository only.
Yes.
> I
> did not iniclude pykickstart in COMPONENTS before. I was trying to buld the
> minimal version to save time. Maybe that's the reason. If I add pykickstart
> to COMPONENTS and then run "make iso" (after running "make qubes"), it says
> there is no rule to make target 'iso.copy-rpms.pykickstart'. There is no
> mention of pykickstart in the makefile.
After modifying COMPONENTS, you need to execute 'make get-sources'
again, to fetch it.
> > This actually may be related to the first issue - dnf can't
> > find the repository so it downloads package from elsewhere.
> > How have you dealt with "mount issue"? Those mounted directories are
> > needed...
> >
> Yes, "make clean-chroot" did exactly what I needed.
>
>
> > > But the kickstart only has six lines. Do I need to install any python
> > > module?
> > >
> > > Putting the errors aside, I have noticed there is build support for
> > debian
> > > as well. Also, the documentation mentions that CI uses ubuntu for final
> > > deployment. In addition to debian, I would like to add support for
> > > archlinux, which I think doesn't take too much. At the moment, I am using
> > > both fedora 31 and arch (I have a qubes install available as well for
> > > testing something). I personally think it is a lot simpler to run and
> > > resolve something on archlinux than it is on any of the deb or rpm based
> > > distributions. What do you say?
> >
> > This all already exists, take a look here:
> >
https://www.qubes-os.org/doc/templates/
> >
> I was talking about the makefile. For example, there is a rule named
> install-deps.rpm (RPM based) and one named install-deps.dpkg (debian
> based), but there isn't one named install-deps.pacman (archlinux based) or
> something like that. Maybe you didn't include it for a reason.
Ah, I see. That makes sense to add. But in fact that part is just a
sanity check - if basic build tools are installed. Starting with empty
one for Arch and simply installing required packages[1] by hand should
be enough to get it working. In theory. In practice, there will be
probably some subtle issues to fix, like stuff being in /usr/bin,
instead of /usr/sbin.
[1]
https://www.qubes-os.org/doc/qubes-builder/
- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAl58GgwACgkQ24/THMrX
1yzJHwf/Ws5EIoYPhVb68BtGsbdcY1U0g0DnqJnMIU9wCLMuhWqqlEPVy2qFvp+Z
ZC4Cf9UCtJrkEdN7haGWmeVKvWwaK79sgdZ/sp3ZFVzbgjnJDTVRUEqfCNqc/urL
AOLLN3MbOOlBqi1Fx3xCVR3LYaRHxm92zfwIbV4jIO4EddRlYFxvRGALj3DXt/g8
Gy2EfoSdozP0kx9aubxhcNZ223BHM4NoXq133utD6PzLQlBtRAI+uhdOQGEvUmZC
hk6EDM9/mG4x0fBOdmytYpdcvA1mvtVuATu4vjmKm4bjJW2K1kZg14VVmioLMHdY
hWqQbpN4XfPc6Mx8x6hDqG2p4f0/tw==
=9p9S
-----END PGP SIGNATURE-----