Already did yesterday. It’s included in a ML message to the Debian bugtracker
1 Like
We don’t necessarily need an external references always. We can also be self-referential sometimes. If you tested it and wrote so in the forums, then that is a reference. Even just <ref>As tested by...</ref> would do as long we can confirm who made the edit.
Added links to bug reports as references now.
In Onionizing Repositories#Debian_Templates users are instructed to add debian.list to Qubes Debian templates. When following these instructions and running apt-get update I get this output.
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:5 and /etc/apt/sources.list.d/debian.list:5
This happens on Debian templates that are up to date but not on Debian templates that have never been updated.
I also have Qubes repos onionized but I don’t think that is the issue.
1 Like
Not sure - haven’t played there for a while. Hopefully you work it out!
All operating system update stuff fixed (very messy), plus millions of lines of spacing fixes etc.
(We really should have a separate Qubes update template of its own & not “borrow” the non-Qubes-Whonix one, but anyway)
1. DispVM half page half done (we need to watch the {{whonix-ws}} and {{whonix-gw}} code isn’t broken on multiple pages - I already discovered it in AppArmor section and DispVMs, so no doubt it is elsewhere.
2. Template: {{Tor_Browser_Remove_Proxy_Settings}} causes massive whitespace because of the last footnote in it for some reason.
E.g. see footnote 32 (or 33) here:
3. In this section, can’t we just delete the bottom two parts which say the same thing as the first section?
http://www.dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion/wiki/About#Debian_Hosts
4. On this page below, you have: {{Template:Qubes}}, but nothing seems to appear? Delete or fix to get rid of whitespace etc?
http://www.dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion/wiki/Qubes/Update
Where do we report it? I’d like this fixed before they disappear for good (if possible).
2 Likes
That is the issue. Users can’t use both Qubes onion repos and Debian onions. If repos configured like that I’m not sure if any Qubes-Debian packages would be pulled from the http// URI instead of Debian onions? Likely if onions where down.
1 Like
torjunkie:
2. Template: {{Tor_Browser_Remove_Proxy_Settings}} causes massive whitespace because of the last footnote in it for some reason.
E.g. see footnote 32 (or 33) here:
Can’t see issue.
3. In this section, can’t we just delete the bottom two parts which say the same thing as the first section?
http://www.dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion/wiki/About#Debian_Hosts
I am not sure if we compress to much information into one sentence that
could lead to ever fewer users understanding this. While the sentence
may be technically concise, correct, it may still be less understood
than with more redundancy?
Made some changes:
new Debian release: “may”, “depending on deprecation notice” (in theory,
if I can’t make it work on the new release of Debian for some reason or
can’t switch myself for some reason then actually until that time
oldstable has to be used.)
new Whonix release: “will” (because then it’s clear that there is a new
Whonix release that is functional)
sub headline Debian Hosts, sub sub headline “New Whonix, Debian, Qubes
or Qubes-Whonix Release”, here I actually made a mistake. Debian hosts
have nothing to do with Qubes or Qubes-Whonix. Rewritten.
4. On this page below, you have: {{Template:Qubes}}, but nothing seems to appear? Delete or fix to get rid of whitespace etc?
Yes, legacy. Delete please.
Where do we report it? I’d like this fixed before they disappear for good (if possible).
1 Like
Why not?
If repos configured like that I’m not sure if any Qubes-Debian packages would be pulled from the http// URI instead of Debian onions? Likely if onions where down.
I may be misunderstanding something but any onion should be possible to combine with any other onion. When using onions exclusively and Debian onion is offline then one would miss out on Debian package upgrades for sure.
1. Connection schemes and chain descriptions still right in this section?
(confusing to me as they don’t seem consistent, but I’m no expert)
2. Is this line still correct in processor microcode updates template? (just checking)
It is unnecessary to apply these updates in standard Non-Qubes-Whonix and Qubes-Whonix guest VMs, as they do not have the ability to alter the microcode. However, processor microcode updates should always be applied on the host operating system (for processors by Intel or AMD) [3] and baremetal configurations like Physical Isolation. [4]
Everyone happy with the micro-edits? 
Pretty well ready to smash email section down of the ToC now. And there is stuff that really needs work in those sections, to put it mildly.
1 Like
torjunkie:
1. Connection schemes and chain descriptions still right in this section?
(confusing to me as they don’t seem consistent, but I’m no expert)
Looks ok.
2. Is this line still correct in processor microcode updates template? (just checking)
It is unnecessary to apply these updates in standard Non-Qubes-Whonix and Qubes-Whonix guest VMs, as they do not have the ability to alter the microcode. However, processor microcode updates should always be applied on the host operating system (for processors by Intel or AMD) [3] and baremetal configurations like Physical Isolation. [4]
That is correct.
Everyone happy with the micro-edits?
Happy as always. 
1 Like
__NOTITLE__ is broken on a few pages (https://www.whonix.org/w/index.php?search=__NOTITLE__). Planing to repair soonish.
1 Like
__NOTITLE__ should be transformed into a wiki template {{notitle}}. (https://www.whonix.org/wiki/Template:notitle) (If someone gets to it before me.) Mass replace doens’t work.
Empty template (just nothing but a page instead of non-exiting page) for now. Later I’ll add the wiki markup there for HideTitle as soon as I can make that work.
Template {{{title}}} - Whonix seems to work now reliably everywhere. Example:
{{Title|title=
Ways To Contribute
}}
1 Like
Great!
Firejail 0.9.56 still crashes Tor Browser in whonix. “Gah, Tab crashed” etc.
If you can get it working put basic steps here and I’ll add to the wiki.
2 Likes
__NOTITLE__ is not fixable unfortunately. Removed.
Title template however seems to be reliable in all cases. Please use it whenever useful.
{{Title|title=
Ways To Contribute
}}
1 Like
already reported that:-
2 Likes
That protocol-leak-protection page has some good info. @Patrick
I think it should be tidied up, all the long code stuff etc split off into a separate page, and then put somewhere with pride on the main page. Right now it is in a dusty back room & probably not getting many eyeballs.
I’ve been using DisplayTitle to fix a ton of pages. Looks good.
1 Like
Forcing onion has been upated
https://whonix.org/w/index.php?title=Forcing_.onion_on_Whonix.org&oldid=36382&diff=cur
Converting the HTTPS-Everywhere user rules sqlite3 binary file to plain text file for editing, then back to a binary file looked promising in the beginning but turned out to be a dead end. If anyone would like a go at it or could give some advice. The issue is in the last step. Somehow the file is changed when converting from plaintext file back to a sqlite3 binary file
1. Install sqlite
sudo apt-get install sqlite3
2. Dump the https-everywhere rules data base to a plain text file.
sqlite3 storage-sync.sqlite .dump > https_rules.txt
3. Open the plaintext file in a text editor (make any edits)
nano https_rules.txt
4. Delete the old user rules file
rm storage-sync.sqlite
5. Create a new sqlite database with the updated user rule set.
cat https_rules.txt | sqlite3 storage-sync.sqlite
2 Likes
Spotted one mistake.
= License =
- {{License_Amnesia {{FULLPAGENAME}}}}
Why as Amnesia license added? Removed.
1 Like
For most pages {{Footer}} sorts out licensing perfectly.
{{License_Amnesia {{FULLPAGENAME}}}} is only required for a few pages imported from Tails a few years ago. Only pages that already have that which then get moved elsewhere may require it.
Pages that have it such as /Documentation also contains something like:
<!--
The Whonix Documentation wiki page is forked from the Tails Documentation page, from this exact source <http://git.immerda.ch/?p=amnesia.git;a=blob;f=wiki/src/doc.mdwn;hb=920ef988d1e8ed552f4e97d1423e0038e1bfbbf4>.
-->
Since years passed since then the link broke. Keep it anyhow as is. Not worth the effort. Copyright is being complied with. Still has enough information if someone wanted to dig. No one interested in this.
If we move content from such a page elsewhere we’d hack to check how the Tails page looked back then or looks now to see if we have to re-add that notice.
1 Like
Nice. I’ll have a play when I have some time.
Sorry - I had it in my head that was a bigger, badder version of the Whonix license (not Tails). 
Noted - footer is enough.
Seems this formatting will never end, but I think it is starting to look much, much better than the mediawiki crap we had before.
Only issue is sometime very long foonotes (https refs) run over into the second column, but that is pretty trivial.
Another is it would be nice to be able to write:
Something.
INFO/WARNING BOX
Something else.
Without the box being so tight on the text surrounding it (vertically). But other than that it is great.
1 Like
We could have templates such as
{{warning|text=
warning text here
}}
Would that help?