suzanne.soy/qubes-doc
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Resolve open issues mentioned on Transifex

Browse Source
This commit is contained in:
Tobias Killer 2021-04-17 10:31:11 +02:00
parent 617330d026
commit 190b740e32
No known key found for this signature in database
GPG Key ID: 2DA5EF6F6E40B328
4 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
developer/building/development-workflow.md
View File

@ -117,7 +117,7 @@ cd ../..
vi series.conf vi series.conf
~~~ ~~~
#### Building RPMS #### Building RPMs
TODO: Is this step generic for all subsystems? TODO: Is this step generic for all subsystems?
@ -130,13 +130,13 @@ distinguish between different versions of the same package.
You might want to take a moment here to review (git diff, git status), commit You might want to take a moment here to review (git diff, git status), commit
your changes locally. your changes locally.
To actually build RPMS, in qubes-builder: To actually build RPMs, in qubes-builder:
~~~ ~~~
make linux-kernel make linux-kernel
~~~ ~~~
RPMS will appear in qubes-src/linux-kernel/pkgs/fc20/x86\_64: RPMs will appear in qubes-src/linux-kernel/pkgs/fc20/x86\_64:
~~~ ~~~
-rw-rw-r-- 1 user user 42996126 Nov 17 04:08 kernel-3.4.18-1debug20121116c.pvops.qubes.x86_64.rpm -rw-rw-r-- 1 user user 42996126 Nov 17 04:08 kernel-3.4.18-1debug20121116c.pvops.qubes.x86_64.rpm
@ -166,7 +166,7 @@ FETCH_HEAD` (in each repo directory). Or `make do-merge` to merge all of them.
When developing it is convenient to be able to rapidly test changes. Assuming When developing it is convenient to be able to rapidly test changes. Assuming
you're developing Qubes on Qubes, you should be working in a special VM for you're developing Qubes on Qubes, you should be working in a special VM for
Qubes and occasionally you will want to transfer code or rpms back to dom0 for Qubes and occasionally you will want to transfer code or RPMs back to dom0 for
testing. testing.
Here are some handy scripts Marek has shared to facilitate this. Here are some handy scripts Marek has shared to facilitate this.

2
developer/building/qubes-builder.md
View File

@ -99,7 +99,7 @@ cp example-configs/qubes-os-master.conf builder.conf
make get-sources make get-sources
# And now to build all Qubes rpms (this will take a few hours): # And now to build all Qubes RPMs (this will take a few hours):
make qubes make qubes

2
developer/general/gsoc.md
View File

@ -332,7 +332,7 @@ immune to altering past entries. See
in files there, no file manager, etc). in files there, no file manager, etc).
- Configure GNOME to not look into external devices plugged in (no auto - Configure GNOME to not look into external devices plugged in (no auto
mounting, device notifications etc). mounting, device notifications etc).
- Package above modifications as rpms, preferably as extra configuration files - Package above modifications as RPMs, preferably as extra configuration files
and/or plugins than overwriting existing files. Exceptions to this rule may and/or plugins than overwriting existing files. Exceptions to this rule may
apply if no other option. apply if no other option.
- Adjust comps.xml (in installer-qubes-os repo) to define package group with - Adjust comps.xml (in installer-qubes-os repo) to define package group with

2
developer/services/dom0-secure-updates.md
View File

@ -44,7 +44,7 @@ The qubes-receive-updates script processes the untrusted input from Update VM: i
Once qubes-receive-updates finished unpacking and verifying the updates, the updates are placed in ``qubes-receive-updates`` directory in Dom0 filesystem. Those updates are now trusted. Dom0 is configured (see /etc/yum.conf in Dom0) to use this directory as a default (and only) [yum repository](https://github.com/QubesOS/qubes-core-admin-linux/blob/release2/dom0-updates/qubes-cached.repo). Once qubes-receive-updates finished unpacking and verifying the updates, the updates are placed in ``qubes-receive-updates`` directory in Dom0 filesystem. Those updates are now trusted. Dom0 is configured (see /etc/yum.conf in Dom0) to use this directory as a default (and only) [yum repository](https://github.com/QubesOS/qubes-core-admin-linux/blob/release2/dom0-updates/qubes-cached.repo).
Finally, qubes-dom0-update runs ``yum update`` that fetches the rpms from qubes-cached repo and installs them as usual. Finally, qubes-dom0-update runs ``yum update`` that fetches the RPMs from qubes-cached repo and installs them as usual.
Security benefit of our update mechanism Security benefit of our update mechanism
---------------------------------------- ----------------------------------------