[qubes-users] sys-net won't start, wireless PCI device cannot be assigned - no IOMMU?

[ultimatevert]

Qubes OS version:

R4.0
Affected component(s):

Intel Wireless N 1000
Steps to reproduce the behavior:

I installed QubesOS R4.0 and made it to the installation configuration page 
(where the system finishes installing, reboots, and then you are prompted with 
the config finishing installer) and I received this error

https://user-images.githubusercontent.com/39247961/50731397-6d84cc00-1131-11e9-94f2-d9bf852283de.jpg

I also get this error message when I log into my QubesOS user and try to start 
sys-net as my WiFi does not work and the little Network applet on the panel is 
nowhere to be found.

This is what comes up when I check the log,

https://user-images.githubusercontent.com/39247961/50731447-a07b8f80-1132-11e9-9d4d-d6c061e0497d.jpg

And I have tried to run the command to force attach the wireless card but I get 
this

https://user-images.githubusercontent.com/39247961/50731449-ab362480-1132-11e9-9694-d3f6e34bd3b4.jpg

So I try the commands

"sudo qvm-prefs sys-net virt_mode hvm"

But I still get the same error as above.

Any ideas? I installed qubesOS on this machine back in 2017 and simply kept 
updating it up to R3.2 (I think) and it always worked wonderfully. However R4.0 
has this issue so I tried installing R3.2 and my WiFi card also did not work, 
R3.0 as well, but if I try Xubuntu 18.04/18.04 or any other distro my WiFi 
works fine. So idk what it is.

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/c172ba22-ac38-4c13-a6ed-23ffcc33c51b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: fed29 templates/upgrade

[John S.Recdep]

On 1/4/19 2:34 AM, unman wrote:
> dnf repoquery --qf "%{name}" --userinstalled

this works then using the grep command

of interesting note is that of the few packages found is pulseaudio-qubes

which I think I accidentally autoremoved and had to reinstall so maybe
it got a new name or package name, but doesn't mean I must install it
again in fed-29 template

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/7bf1bd60-986f-2823-e963-1d0b5dfd8427%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: fed29 templates/upgrade

[John S.Recdep]

On 1/5/19 12:26 AM, 799 wrote:
> Hello,
> 
> Am Sa., 5. Jan. 2019, 05:01 hat John S.Recdep 
> 
> geschrieben:
> 
>> [...]
>> BTW all: no luck with the suggested methods of determining what extra
>> packages I may have installed in the fedora-28 Template . but I'll
>> just live with the fresh fedora-29 template
> 
> 
> I had the same problem and that's why I am setting up my templates only via
> scripts which I can run from dom0.
> This improves speed to rebuild templates and also I know exactly what I
> have installed.
> 
> What you can do to get the differences between two templates:
> 
> 1) run "dnf list installed > packagelist1.txt
> Do the same in the other VM
> 
> 2) compare both lists:
> grep -Fxv -f packagelist1.txt packagelist2.txt
> 
> - O
> 

I'm running this in fed-28 terminal and fed-29 template terminal ; mv
file2 to the other template  but your grep cmd is just showing a list of
all packages, maybe because of the version update numerical changes ...
guess I can look back at previous post of how to remove the version
change numbers, if it might matter

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/46304afe-f53d-1c09-6849-d0edd4cfeb1a%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] qvm-restart

[Stuart Perkins]

On Sat, 5 Jan 2019 15:43:25 +0100
haaber  wrote:

>> On 1/5/19 1:13 AM, 799 wrote:  
>>>
>>> The restart-function is available in the right-click-menue of a vm in
>>> the Qube Manager. Could this also be provided for the CLI as a
>>> "qvm-restart" command?
>>>
>>> You can easily write a script yourself:
>>>
>>> #!/bin/bash
>>> qvm-shutdown --wait $1 && qvm-start $1
>>>  
>
>This won't work non sys-net, sys-firewall ... for example.  You might 
>want to
>
>1) first find appVMs that use $1 as netvm
>2) set their netvm to "none"
>3) then qvm-shutdown $1
>4) then qvm-start $1
>5) then reset netvm's to back to $1.
>
>steps 3 &4 are clear (see above). Step 1 can be done using Chris' 
>"findpref" command (see https://github.com/tasket/Qubes-scripts ) :
>
>findpref --pref sysnet $1  | cut -f5 -d" "
>
>will output all appVM's that use $1 as sys-net. I am not a real 
>bash-champion, but I'd try
>
> APPVMS=`findpref --pref sysnet $1  | cut -f5 -d" "`
>
>to store the concerned APPVMS in step one in a string. Then I would try
>
>for APPVM in APPVMS; do  findpref --pref sysnet $APPVM none; done
>
>to do step 2  and
>
>for APPVM in APPVMS; do  findpref --pref sysnet $APPVM $1; done
>
>to set them back. So all together:
>
>
>#!/bin/bash
>allAPPVMS=`findpref --pref sysnet $1  | cut -f5 -d" "`
>for eachAPPVM in allAPPVMS; do  findpref --pref  sysnet  $eachAPPVM 
>none; done
>qvm-shutdown --wait $1 && qvm-start $1
>for eachAPPVM in allAPPVMS; do  findpref --pref sysnet $eachAPPVM $1; done
>
>
>I did not test this, spo please re-read the findpref usage first!  Is 
>there some improvement by the community ??   Bernhard
>

I have created several scripts in dom0 for my Qubes 3.2 machine.  I have one 
which stops "most" of the running VM's in order to shut everything down BUT 
dom0.  This is to allow me to leave my machine running without it doing 
unnecessary processing as I have mother board issues which prevent a reliable 
reboot for now.  I have a motherboard on the way and will be doing the surgery 
to replace it then...

Anyway, the stopmost.sh script uses qvm-ls with some sed and grep commands to 
first issue qvm-shutdown for all running appVMs.

It polls the qvm-ls for running appVMs and when it finds they have all stopped, 
it then does the system VM's in order.  It uses one called stopvm.sh which 
detects if the specified VM is running, and if so issues qvm-shutdown for it 
then polls every few seconds until it is "Halted", then it exits.  This allows 
the stopmost.sh script to do...

stopvm.sh sys-whonix
stopvm.sh sys-firewall
stopvm.sh sys-net

without issues, as each stop waits to complete before the next one tries.  If a 
vm is NOT running, it merely echoes that it is Halted and goes on.  I don't 
bother error checking to ensure that a valid VM name is given, but I'm the only 
one using it...

It would be an easy thing to do a "restart" for me by calling the stopvm.sh 
first then issuing qvm-start on the target. 

The stopvm.sh script is...

TARGET=${1}
if [ X${TARGET} == X ]
then exit
fi
STATUS=`qvm-ls|awk -F\| '{print $1 " " $3}'|grep -i ${TARGET}|head -1|awk  
'{print $2 }'`
echo ${TARGET} is ${STATUS}
if [ ${STATUS} != Running ]
then exit
fi
qvm-shutdown ${TARGET}
while [ ${STATUS} != Halted ] 
do
sleep 5
STATUS=`qvm-ls|awk -F\| '{print $1 " " $3}'|grep -i ${TARGET}|head 
-1|awk  '{print $2 }'`
echo ${TARGET} is ${STATUS}
done

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20190105124649.28b51037%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Thanks and howto install Python version >= 2.6.4 on debian-9 template?

[unman]

On Sat, Jan 05, 2019 at 03:08:19PM +0100, gone wrote:
> On 1/5/19 2:21 AM, unman wrote:
> > On Fri, Jan 04, 2019 at 06:40:08PM -0500, Chris Laprise wrote:
> > > On 01/04/2019 04:18 PM, gone wrote:
> > > 
> > > > Thanks again, unman.
> > > > 
> > > > I think I've understood all the steps up to 5. and executed them. Then
> > > > with Step 6 it went different to what you predicted. No output about
> > > > mgmt-salt (btw. what is that?) and unfortunately no option to "say NO":
> > > > 
> > > > user@debian-9-mix:~$ sudo apt-get install python3.7
> > > > Reading package lists... Done
> > > > Building dependency tree
> > > > Reading state information... Done
> > > > Some packages could not be installed. This may mean that you have
> > > > requested an impossible situation or if you are using the unstable
> > > > distribution that some required packages have not yet been created
> > > > or been moved out of Incoming.
> > > > The following information may help to resolve the situation:
> > > > 
> > > > The following packages have unmet dependencies:
> > > >    python3.7 : Depends: python3.7-minimal (= 3.7.2~rc1-1) but it is not
> > > > going to be installed
> > > >    Depends: libpython3.7-stdlib (= 3.7.2~rc1-1) but it is 
> > > > not
> > > > going to be installed
> > > > E: Unable to correct problems, you have held broken packages.
> > > > 
> > > > Is that problematic? Would you propose to go on with step 7 or do
> > > > something else first?
> > > > 
> > > 
> > > I think you need to include the '-t buster' option for apt-get install.
> > > Otherwise it won't look for newer dependencies in the buster repo and so
> > > won't be able to find them.
> > > 
> > 
> > If you look at my instructions, you'll see I didnt suggest setting the
> > Default-Release until *after* you'd installed Python3.7.
> > My guess is that you've pinned to stretch already, so you have to
> > specify buster for the install, as Chris says.
> > If you do, you'll see the warning - mgmt-salt-vm-connector is the backend
> > that allows for salt control of qubes. The new update tool uses this to
> > run updates so you'll wont be able to use it on the new template.
> > 
> 
> Fine, I performed Step 6 with the -t buster option, got the warning and said
> NO.
> 
> Same done in Step 7 apt tells, that the qubes-* packages are already the
> newest version and set to manually installed. But after that still the
> warning appears:
> 
> The following packages will be REMOVED:
>   libqt5designer5 libqt5gui5 libqt5help5 libqt5printsupport5 libqt5svg5
> libqt5widgets5
>   python3-pyqt5 qt5-gtk-platformtheme qubes-mgmt-salt-vm-connector
> qubes-vm-recommended
>   salt-common salt-ssh
> The following NEW packages will be installed:
>   libboost-iostreams1.67.0 libboost-system1.67.0 libdrm-common
> libevent-2.1-6 libicu63
>   libpcre2-16-0 libpython3.7 libpython3.7-dev libpython3.7-minimal
> libpython3.7-stdlib
>   libunbound8 libwebpmux3 libzstd1 python3-distutils python3-lib2to3
> python3.7
>   python3.7-dev python3.7-minimal uuid-dev
> 
> 
> I'm not sure. Will they really be removed or rather not because before they
> will get set to manually installed? Or in different words: Should I say yes
> here?
> 

It's always difficult troubleshooting someone else's problems without
knowing exactly what the setup is, or exactly what commands they are
running.
I've installed all those packages, and when I run step7 I
DONT see that note about removing these packages. (As I've explained
qubes-vm-recommended, salt-common and salt-ssh have to go.)
This makes me think that you have a range of packages installed, some of
which are dependencies of the packages in the REMOVED list, and that
they are incompatible with python3.7 or ITS dependencies. Obviously I
don't know what they might be.

You haven't commented on whether you followed my instructions or whether
you set the Default before starting out. If you did then I would start
from a fresh clone and NOT set the default. (One reason for this is that
you may not want to restrict yourself to buster which is what '-t
buster' is doing.) If you do this then DONT use the -t option as that
will FORCE apt to install everything from testing. 

If you want those named packages to be retained, then try adding them
to the list of packages to be installed, or use aptitude which will help
you to see exactly what is going on with these particular versions.

There really isn't anything to be lost (assuming you are working in a
cloned template.) 

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20190105163921.2jtg3yfylrfelkf6%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/opto

Re: [qubes-users] qvm-restart

[haaber]

On 1/5/19 1:13 AM, 799 wrote:


The restart-function is available in the right-click-menue of a vm in
the Qube Manager. Could this also be provided for the CLI as a
"qvm-restart" command?

You can easily write a script yourself:

#!/bin/bash
qvm-shutdown --wait $1 && qvm-start $1



This won't work non sys-net, sys-firewall ... for example.  You might 
want to


1) first find appVMs that use $1 as netvm
2) set their netvm to "none"
3) then qvm-shutdown $1
4) then qvm-start $1
5) then reset netvm's to back to $1.

steps 3 &4 are clear (see above). Step 1 can be done using Chris' 
"findpref" command (see https://github.com/tasket/Qubes-scripts ) :


   findpref --pref sysnet $1  | cut -f5 -d" "

will output all appVM's that use $1 as sys-net. I am not a real 
bash-champion, but I'd try


APPVMS=`findpref --pref sysnet $1  | cut -f5 -d" "`

to store the concerned APPVMS in step one in a string. Then I would try

   for APPVM in APPVMS; do  findpref --pref sysnet $APPVM none; done

to do step 2  and

for APPVM in APPVMS; do  findpref --pref sysnet $APPVM $1; done

to set them back. So all together:


#!/bin/bash
allAPPVMS=`findpref --pref sysnet $1  | cut -f5 -d" "`
for eachAPPVM in allAPPVMS; do  findpref --pref  sysnet  $eachAPPVM 
none; done

qvm-shutdown --wait $1 && qvm-start $1
for eachAPPVM in allAPPVMS; do  findpref --pref sysnet $eachAPPVM $1; done


I did not test this, spo please re-read the findpref usage first!  Is 
there some improvement by the community ??   Bernhard


--
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/82338765-257f-1f73-ef20-a556321cde05%40web.de.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Thanks and howto install Python version >= 2.6.4 on debian-9 template?

[gone]

On 1/5/19 2:21 AM, unman wrote:

On Fri, Jan 04, 2019 at 06:40:08PM -0500, Chris Laprise wrote:

On 01/04/2019 04:18 PM, gone wrote:


Thanks again, unman.

I think I've understood all the steps up to 5. and executed them. Then
with Step 6 it went different to what you predicted. No output about
mgmt-salt (btw. what is that?) and unfortunately no option to "say NO":

user@debian-9-mix:~$ sudo apt-get install python3.7
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
   python3.7 : Depends: python3.7-minimal (= 3.7.2~rc1-1) but it is not
going to be installed
   Depends: libpython3.7-stdlib (= 3.7.2~rc1-1) but it is not
going to be installed
E: Unable to correct problems, you have held broken packages.

Is that problematic? Would you propose to go on with step 7 or do
something else first?



I think you need to include the '-t buster' option for apt-get install.
Otherwise it won't look for newer dependencies in the buster repo and so
won't be able to find them.



If you look at my instructions, you'll see I didnt suggest setting the
Default-Release until *after* you'd installed Python3.7.
My guess is that you've pinned to stretch already, so you have to
specify buster for the install, as Chris says.
If you do, you'll see the warning - mgmt-salt-vm-connector is the backend
that allows for salt control of qubes. The new update tool uses this to
run updates so you'll wont be able to use it on the new template.



Fine, I performed Step 6 with the -t buster option, got the warning and 
said NO.


Same done in Step 7 apt tells, that the qubes-* packages are already the 
newest version and set to manually installed. But after that still the 
warning appears:


The following packages will be REMOVED:
  libqt5designer5 libqt5gui5 libqt5help5 libqt5printsupport5 libqt5svg5 
libqt5widgets5
  python3-pyqt5 qt5-gtk-platformtheme qubes-mgmt-salt-vm-connector 
qubes-vm-recommended

  salt-common salt-ssh
The following NEW packages will be installed:
  libboost-iostreams1.67.0 libboost-system1.67.0 libdrm-common 
libevent-2.1-6 libicu63
  libpcre2-16-0 libpython3.7 libpython3.7-dev libpython3.7-minimal 
libpython3.7-stdlib
  libunbound8 libwebpmux3 libzstd1 python3-distutils python3-lib2to3 
python3.7

  python3.7-dev python3.7-minimal uuid-dev


I'm not sure. Will they really be removed or rather not because before 
they will get set to manually installed? Or in different words: Should I 
say yes here?


--
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/e6404cdb-7a8c-4f83-fe08-f90d742b3ce1%40posteo.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] qvm-restart

[gone]

On 1/5/19 1:13 AM, 799 wrote:



Am Fr., 4. Jan. 2019, 22:46 hat gone > geschrieben:


The restart-function is available in the right-click-menue of a vm in
the Qube Manager. Could this also be provided for the CLI as a
"qvm-restart" command?


You can easily write a script yourself:

#!/bin/bash
qvm-shutdown --wait $1 && qvm-start $1

- O



Thank you @799 for these two lines.

--
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/9f162416-ead0-c520-b45f-f0d809e6887e%40posteo.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Installing: Missing features: IOMMU/VT-d/AMD-Vi, Interrupt Remapping

[LefC]

Τη Τετάρτη, 2 Ιανουαρίου 2019 - 11:37:53 μ.μ. UTC+2, ο χρήστης steve.coleman 
έγραψε:
> On 1/2/19 11:41 AM, LefC wrote:
> > Τη Τετάρτη, 2 Ιανουαρίου 2019 - 5:06:31 μ.μ. UTC+2, ο χρήστης steve.coleman 
> > έγραψε:
> >> On 1/2/19 9:12 AM, LefC wrote:
> >>> Hi, i'm trying to install Qubes for the first time, i am a total newb but 
> >>> eager to learn more about this interesting OS.
> >>> So i attempted an installation to my old wiped laptop and got this message
> >>>
> >>> Missing features: IOMMU/VT-d/AMD-Vi, Interrupt Remapping
> >>>
> >>> And the warning that Qubes might not work properly. Does that mean that 
> >>> my machine is not able to run Qubes at all?? Is there anything that i may 
> >>> can do to make it work somehow?
> >>> To be honest, i did proceed with the installation, which completed 
> >>> normally without any issue but then the system was and is not able to 
> >>> boot Qubes. It leads to some Fail/error messages while booting. Is it 
> >>> because of the lacking hardware?
> >>> Is there any hope for my laptop and Qubes?
> >>>
> >>
> >> Before giving up, go check your BIOS settings for the required features
> >> listed above. In all likelihood you may actually have the necessary
> >> hardware but have them disabled in BIOS by default.
> >>
> >> Without knowing *exactly* what system processor and chipset you have we
> >> can not give you any better advice than to check these settings.
> >>
> >> Try enabling those settings in BIOS, and then try to install again.
> >> Failing that, you might check to see if you have the latest vendor BIOS
> >> update.  Take notes on what it says about your specific hardware, and
> >> let us know what happens.
> > 
> > Thanks for the answer,
> > Well, the laptop is a samsung model NP300V5A
> > 
> > Intel Core i5 2410M / 2.30 GHz ( Dual-Core )
> > with a GeForce GT 520M
> > 
> > I looked up the BIOS settings as you suggested, there's nowhere something 
> > like the missing features. Only VT-x which says 'Supported'. Its Phoenix 
> > BIOS v.08F1
> > Not sure how to update this, i must look it up and ask again. Also most of 
> > its options seem to be locked by the manufacturer
> > 
> 
> Well you can take a look here:
> https://www.samsung.com/us/support/owners/product/np300v5a
> 
> I didn't see VT-d listed anywhere on the spec page. There is a BIOS 
> installer ver 1.0.0.2 listed, but from way back in 2011. If you don't 
> have the VT-d hardware there isn't much point to installing Qubes.

Thank you, unfortunately looks like this laptop can't run qubes.

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/5c2c350a-2c89-4036-9312-2c477d13726a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: dom0 update: sys-whonix: command failed with code: 1

[qubes-fan]

Thank you!


Jan 2, 2019, 1:37 PM by a...@qubes-os.org:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 1/1/19 10:10 PM, > 22...@tutamail.com >  wrote:
>
>> Same thing here...no answers/solutions but your not alone!
>>
>
> The fix is already in testing:
>
> https://github.com/QubesOS/qubes-issues/issues/4616 
> 
>
> - -- 
> Andrew David Wong (Axon)
> Community Manager, Qubes OS
> https://www.qubes-os.org 
>
> -BEGIN PGP SIGNATURE-
>
> iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlwssIIACgkQ203TvDlQ
> MDA0Jg/7Bk2KUHRMDuxIWFPrxgeOulc9Q2UdmApl6fgp9PU8BPkY4GISdi39uixH
> Yu9Af2GU/MWfDu3j0zqYcyIQYY6qnVa038ZNYd3BSwjhk1K4sqPY27T7+HAzF3Uy
> W1CGQWmLh+ry7uCisiPbbBTaT8IGP/Fohzp+vr0UhtR/vrXU5gzc+R8fw6vBDaPY
> Inv8D1+Tl/+z3oumAFxb2eWn0rRTSdwILLVo2bR4Rd2RpSszENaCBQvChB94MHw8
> SLRn0YiDJZM6UXMGlpunHVrihbv9Irue75LFcpSUa2SWIlTNoINv8VpcugnhybuD
> WjuCqiuuNCD8KZEtYrZg8L+zX+uuo0p/rcfDFoaEHQTrCXQW/cZRpqIaGOySBuQS
> x1P/vDX3YwAJjpXeJALVFZzndd8HqpxlL45qgLI0xD7eGa0lqsD1DpSfDt6S08oU
> y8yZdCPnlOWvRRF7Xb7OA2y94ClRoHzoOW1tJgDQeZ462/I3qXtHIwTfYDhO9B3/
> UJoB5zniVh5CKvCuYYr4miL98NIa92xoH5Vgj80A32Qz+ih7S2iraL4lIiqozXet
> Db6X4e5V6miQULpix6LDXs/am44O6hKjHpPf3iCvcfdybW2oF7+O04Uu7K4nT96B
> i7DCdAzuw/nLK/7yalez9ADM9xh60DF5XK2UqF1t90PRhGOiPQc=
> =EiKP
> -END PGP SIGNATURE-
>
> -- 
> 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 post to this group, send email to > qubes-users@googlegroups.com 
> > .
> To view this discussion on the web visit > 
> https://groups.google.com/d/msgid/qubes-users/7828b6e0-8d82-ea10-11c1-8fe9eafc3...@qubes-os.org
>  
> >
>  .
> For more options, visit > https://groups.google.com/d/optout 
> > .
>

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/LVSokl2--3-1%40tutanota.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: fed29 templates/upgrade

[Stuart Perkins]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256



On Fri, 4 Jan 2019 21:00:56 -0600
Andrew David Wong  wrote:

>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA512
>
>On 1/4/19 1:13 PM, John S.Recdep wrote:
>> On 1/4/19 1:37 AM, Andrew David Wong wrote:  
>>> On 1/3/19 11:31 PM, John S.Recdep wrote:  
 On 1/3/19 2:51 PM,
 22rip-2xk3N/kkaK1Wk0Htik3J/w...@public.gmane.org wrote:  
> Thanks 799...I learned something!
> 
> Similar to 799 but less hardcore...I always download a fresh 
> template(vs upgrade). In my case I ran with a full/fresh 
> Fedora-29 after the Fedora-28 hplip issues, and added any
> new software from fresh:
> 
> https://www.qubes-os.org/doc/templates/
>   
>>> 
>>>   
 hmm, ok let's say I just use the new fresh 29 template, is
 there some way that I can know what non-stock software I
 installed on my Fedora-28 template, as I can't remember all
 that I may have installed   
>>> 
>>> 
>>> This is more of a Fedora question than a Qubes question. As far
>>> as I know, there isn't a clean way to do this. Following Marek's
>>> advice from years ago, I just keep a list of the packages that I
>>> install in each of my templates.
>>> 
>>>   
 So, no advice on upgrading from my 28 template at this time? I
 find it strange that the template is in the dom0 updates
 available, but I see no notice  in the news section on qubes
 website nor here ..  
>>> 
>>> 
>>> See:
>>> 
>>> https://github.com/QubesOS/qubes-issues/issues/4223
>>> 
>>> and
>>> 
>>> https://github.com/QubesOS/qubes-doc/pull/739  
>> 
>> So, Andrew does this mean that although the Fedora-29 Template is 
>> available via sudo qubes-dom0-update  that it still has issues and
>> hence it is not officially advisable to use it ? ( whether via
>> 'fresh' d/l nor 'upgrades' ? )
>> 
>> Forgive me, am just a layman, not sure what I would expect to
>> interpret from the github links (perhaps the fact that there are
>> any issues provides the answer?)
>> 
>> My repos are just the default qubes 4.0+ versions
>>   
>
>Well, you said you found it strange that there was no documentation or
>announcement for the Fedora 29 template. These links show why: the
>documentation is still being worked on, and the necessary steps prior to
>the announcement have not yet been completed. (In fact, at the time of
>this writing, the issue still indicates that the template has not yet
>migrated to the stable repo, which appears to be false.)
>
>In order to avoid this sort of confusion in the future, perhaps we
>should refrain from migrating new templates to the stable repo until
>documentation and an announcement are ready to be published, then do
>it all simultaneously. What do you think, Marek?
>
>- -- 
>Andrew David Wong (Axon)
>Community Manager, Qubes OS
>https://www.qubes-os.org
>
>-BEGIN PGP SIGNATURE-
>
>iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlwwHc0ACgkQ203TvDlQ
>MDC3vxAAojbKj36me1TyU3iC+++fzvbV3Cz0NBideZaLmQkXXkydgmM8XFgVgLrT
>4dgLsSBsg0M9x3FtzVzz653kvPYm/2n1YGjEboNiq19DbByqfvqCeKhEvxPXGwS4
>XP/bFzvtQ9fG/kqRWU03npdqBes9qlhiBOzn2Qnhfc3KNuZvX4U1i5IPTZnipuh+
>FSCqYdbbOq8dnjhu3zChq9A4GFD74f/jnx+bvP9NV0GWjGIFQQ/Y+Iza6HhlcO+y
>gAFLOR3shPFz4PAfJztSKzdaINavIWYqJtU07WIKVb4GJS1dnoU7B0NPyB73wdoa
>2iSKoZkr8Yb2ZamdqvAaZP4JUnyG6QeakpW7fG4xtDWTpJnuKw1BvTxqTFAybJ3F
>sz2A807BmI/ie8znIU7BDCTihFnqw3oXAic550crMhh0WSjR8sYKTc8c3Nmpbv0V
>y9V0p12h+HuljaPQk8AXGa1QA2wviVS3r9gjN1VNKls8R2QwIqjohkitr5v9j9i/
>Hz1X/ctZ9o64h9v8laVwpkLeWeNKjMWxLhD/a0FEqDeVkIxD+sS85uf5x2hkJyaD
>mUaxgax/WduElTaZW5unLPub8ZUOD7nLSjDrz9WZw3iDnuZl4CcG2qUNHBQPl6RT
>eh/Hb3mPTKSp4M+hB1msXa/FaCLy5OI3EiryRE6yXLu3xsx1c6g=
>=mpOV
>-END PGP SIGNATURE-
>

No job is complete until the paperwork is done..  :)
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEg3cTCwPFs8wewas+M1E7j4SmKVQFAlwwl8AACgkQM1E7j4Sm
KVQVVwf/RuriwEawNv4BoIpReNUu4weMmZtFWfekwwy+Z9df1yzNeV0tEnvuveoS
zY9an0s98m0yBRRWRZUcUYj52m/GtRR8SuzPRSlwui4aq+8tFPT+VLwn8jELFxnL
VGZJHsOSxtIauDJZB7i5n1q0aJR6gTRmSt259HUr1H9bxqEL+EoktxxiWLxgXSLO
Z2ttSg62LHguBPpm/Wx3cptFokOVPLHaAO7IOH4fN2i4J9VVMSG6LiHpEnI2PbQU
oDu6vsuNIc+BoAg76YbqdwjyDm6QCgCoJhTH44m/+SICaHjuzRl9Zt7lZdAVE4PQ
E+zoQTDS3ZR7D++1z4aHMJXDvjGL2w==
=Iypo
-END PGP SIGNATURE-

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20190105054047.703c3184%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: fed29 templates/upgrade

[799]

Hello,

Am Sa., 5. Jan. 2019, 05:01 hat John S.Recdep 
geschrieben:

> [...]
> BTW all: no luck with the suggested methods of determining what extra
> packages I may have installed in the fedora-28 Template . but I'll
> just live with the fresh fedora-29 template


I had the same problem and that's why I am setting up my templates only via
scripts which I can run from dom0.
This improves speed to rebuild templates and also I know exactly what I
have installed.

What you can do to get the differences between two templates:

1) run "dnf list installed > packagelist1.txt
Do the same in the other VM

2) compare both lists:
grep -Fxv -f packagelist1.txt packagelist2.txt

- O

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CAJ3yz2uDUr-1-wHkDDFbaKapT06pv5ObA536O6SVben6XdK4pQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.