https://phabricator.whonix.org/T391#6396

No longer using taksel. Building Whonix templates now with flavor minimal and no-recommends to get better control of the installed packages. Therefore also no more build error.

In T391#6310, @Patrick wrote:

Wild speculation: perhaps the build script killed apt-cacher-ng running on the build VM level?

In T391#6309, @marmarek wrote:

I think those are two totally unrelated issues:

1. Build failure
2. Usage of tasksel (and more generally - default package list for Qubes Debian template) in Whonix template build

I think those are two totally unrelated issues:

1. Build failure
2. Usage of tasksel (and more generally - default package list for Qubes Debian template) in Whonix template build

issue 6:
After upgrade, after "sudo shutdown" and starting the upgraded template, I am unable to start (using "Run command in VM") xterm, konsole and gnome-terminal. Neither any other applications are startable.

issue 5:

Issue 4:
We don't have the upgraded qubes-whonix 11 package for in the repository yet.

issue 3:

For the record, slightly off-topic.
Qubes Q3 RC1, Whonix 10.

In T338#5679, @Patrick wrote:

...

The opt path is deferentially not part of XDG standard, completely opposite. ~/bin /~opt is part of a long time honoured defacto standard.

I will revert the change for now by adding a comment to the configuration file that sets the path.

Yes, please undo for now.

I can revert to use original path although if talking about 'reasonable expectations for uniform default behaviour' and wanting to keep all the Whonix variations similar we may want to consider changing the path for all the other versions as well then since the /home/user/opt is the proper and defacto standard location path to install pre-built personal/private binary applications that are not XDG aware.

This will cause confusion because it goes against users' reasonable expectations for uniform default behavior - opening the door to balkanization of Whonix versions. We also have to be compatible with the expectations of upstream because at some point they will ship an upstream apparmor profile too.

Yes, causing issues.

What ya mean? Is it causing issues? In following standards or defacto standards the ~/opt directory is the correct spot to place pre-built packages that do not adhere to XDG specs.

Can you undo the ~/opt thing please? @nrgaway

Not required. T342 functional.

Dependency is non-ideal because of Qubes (T353).

Done:
https://www.whonix.org/blog/testers-upgrade-10-to-11

Alright. That answers my question. Thanks!

Qubes VMs (currently) does not use grub at all - Xen loads kernel
directly from dom0 filesystem (yes, VM have no influence on kernel
binary and parameters).
So, those files will not be used at all.

Alright.

Had the same issue. The mrux or mrix permissions fix the parsing issue, but I'll have to check if that works in the host. I have not used the VirtualBox profile for a long time, and I'm not sure it's working as is in jessie. Not sure either if we should keep this profile in Whonix.

The upstream profile works with Whonix, and it's probably safer to keep the empty package.