Upgrading from Qubes 3.1 to 3.2 fail
133 views
Skip to first unread message
donoban
Jul 31, 2016, 7:53:30 AM7/31/16
to qubes-users
Hi,
I tried to do the experimental process for upgrading to Qubes 3.2. I
followed the steps from https://www.qubes-os.org/doc/upgrade-to-r3.2/
All went fine until I rebooted the system (step 7). After rebooting I
had a lot of packages for update on dom0 (more than 1000), and when I
tried to update them it failed because some dependency problems (I
remember some perl packages but maybe there were more packages with
problems).
I didn't extract logs because I needed the computer working ASAP so I
installed it from scratch and restored my backup but I have another
computer on 3.1 which I would like to upgrade to 3.2 and I could try to
do the process again and extract useful information.
I had all my VM's with Debian template, I had indeed fedora template
removed, maybe this could affect to the upgrade process.
Some comments after fresh install 3.2:
- Debian and Whonix-GW seems up to date after install, while fedora-23
and Whonix-WS needed updates. I don't know why...
- I have sys-usb working fine but only with Fedora template, could I
migrate it to Debian?
Well, it looks very nice. Thanks for your work guys.
Regards.
I tried to do the experimental process for upgrading to Qubes 3.2. I
followed the steps from https://www.qubes-os.org/doc/upgrade-to-r3.2/
All went fine until I rebooted the system (step 7). After rebooting I
had a lot of packages for update on dom0 (more than 1000), and when I
tried to update them it failed because some dependency problems (I
remember some perl packages but maybe there were more packages with
problems).
I didn't extract logs because I needed the computer working ASAP so I
installed it from scratch and restored my backup but I have another
computer on 3.1 which I would like to upgrade to 3.2 and I could try to
do the process again and extract useful information.
I had all my VM's with Debian template, I had indeed fedora template
removed, maybe this could affect to the upgrade process.
Some comments after fresh install 3.2:
- Debian and Whonix-GW seems up to date after install, while fedora-23
and Whonix-WS needed updates. I don't know why...
- I have sys-usb working fine but only with Fedora template, could I
migrate it to Debian?
Well, it looks very nice. Thanks for your work guys.
Regards.
Marek Marczykowski-Górecki
Jul 31, 2016, 8:33:07 AM7/31/16
to donoban, qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Sun, Jul 31, 2016 at 01:53:26PM +0200, donoban wrote:
> Hi,
>
> I tried to do the experimental process for upgrading to Qubes 3.2. I
> followed the steps from https://www.qubes-os.org/doc/upgrade-to-r3.2/
>
>
> All went fine until I rebooted the system (step 7). After rebooting I had a
> lot of packages for update on dom0 (more than 1000), and when I tried to
> update them it failed because some dependency problems (I remember some perl
> packages but maybe there were more packages with problems).
Those packages should be already handled in step 4.
> I didn't extract logs because I needed the computer working ASAP so I
> installed it from scratch and restored my backup but I have another computer
> on 3.1 which I would like to upgrade to 3.2 and I could try to do the
> process again and extract useful information.
>
> I had all my VM's with Debian template, I had indeed fedora template
> removed, maybe this could affect to the upgrade process.
Yes, this could affect the upgrade. If that's the case it is a bug we
should fix before final release.
> Some comments after fresh install 3.2:
>
> - Debian and Whonix-GW seems up to date after install, while fedora-23 and
> Whonix-WS needed updates. I don't know why...
This shouldn't matter as it's good practice to update the system after
installation anyway. In a month all the templates will have some updates
pending.
> - I have sys-usb working fine but only with Fedora template, could I migrate
> it to Debian?
What are the problems with Debian template there?
- --
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-----
Version: GnuPG v2
iQEcBAEBCAAGBQJXne/9AAoJENuP0xzK19csiPEH/21rgzz3P1xlDnJeZ2wLs3Iw
n/dCwMqQ665NevJyHhZrtmhUoXsN86/fs9kO76+cQnKRR5WMtzNeRxAK2dcW7O4Y
efGoR6jZnpKbwXSQKt1+sgUS4c46BEF2FqQs0u4hwwY4wmS8wi+UIUlR8fN7800H
E6TtPK9BZfO0gEoDs0W49epXXv3xu64LKYKMOPAPNGi4jmYZvaWluW0m6tl8CwO4
0BnaXYjLnKdxzPK9vRZe4YMs20nCsg5SlPjPQJiO0K21ytwYPpWlxnO04zg0XU9e
2xa6Y4Eo4XxMMsMQ7V2QDMpaTAa3qyiMnHqJVGGOdOTr3S3uHwyg0b1wI3hk0GI=
=bRcX
-----END PGP SIGNATURE-----
Hash: SHA256
On Sun, Jul 31, 2016 at 01:53:26PM +0200, donoban wrote:
> Hi,
>
> I tried to do the experimental process for upgrading to Qubes 3.2. I
> followed the steps from https://www.qubes-os.org/doc/upgrade-to-r3.2/
>
>
> All went fine until I rebooted the system (step 7). After rebooting I had a
> lot of packages for update on dom0 (more than 1000), and when I tried to
> update them it failed because some dependency problems (I remember some perl
> packages but maybe there were more packages with problems).
> I didn't extract logs because I needed the computer working ASAP so I
> installed it from scratch and restored my backup but I have another computer
> on 3.1 which I would like to upgrade to 3.2 and I could try to do the
> process again and extract useful information.
>
> I had all my VM's with Debian template, I had indeed fedora template
> removed, maybe this could affect to the upgrade process.
should fix before final release.
> Some comments after fresh install 3.2:
>
> - Debian and Whonix-GW seems up to date after install, while fedora-23 and
> Whonix-WS needed updates. I don't know why...
installation anyway. In a month all the templates will have some updates
pending.
> - I have sys-usb working fine but only with Fedora template, could I migrate
> it to Debian?
- --
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-----
Version: GnuPG v2
iQEcBAEBCAAGBQJXne/9AAoJENuP0xzK19csiPEH/21rgzz3P1xlDnJeZ2wLs3Iw
n/dCwMqQ665NevJyHhZrtmhUoXsN86/fs9kO76+cQnKRR5WMtzNeRxAK2dcW7O4Y
efGoR6jZnpKbwXSQKt1+sgUS4c46BEF2FqQs0u4hwwY4wmS8wi+UIUlR8fN7800H
E6TtPK9BZfO0gEoDs0W49epXXv3xu64LKYKMOPAPNGi4jmYZvaWluW0m6tl8CwO4
0BnaXYjLnKdxzPK9vRZe4YMs20nCsg5SlPjPQJiO0K21ytwYPpWlxnO04zg0XU9e
2xa6Y4Eo4XxMMsMQ7V2QDMpaTAa3qyiMnHqJVGGOdOTr3S3uHwyg0b1wI3hk0GI=
=bRcX
-----END PGP SIGNATURE-----
donoban
Jul 31, 2016, 9:32:33 AM7/31/16
to qubes-users
El 31 de julio de 2016 14:33:00 CEST, "Marek Marczykowski-Górecki" <marm...@invisiblethingslab.com> escribió:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA256
>
>On Sun, Jul 31, 2016 at 01:53:26PM +0200, donoban wrote:
>> Hi,
>>
>> I tried to do the experimental process for upgrading to Qubes 3.2. I
>> followed the steps from https://www.qubes-os.org/doc/upgrade-to-r3.2/
>>
>>
>> All went fine until I rebooted the system (step 7). After rebooting I
>had a
>> lot of packages for update on dom0 (more than 1000), and when I tried
>to
>> update them it failed because some dependency problems (I remember
>some perl
>> packages but maybe there were more packages with problems).
>
>Those packages should be already handled in step 4.
>
>> I didn't extract logs because I needed the computer working ASAP so I
>> installed it from scratch and restored my backup but I have another
>computer
>> on 3.1 which I would like to upgrade to 3.2 and I could try to do the
>> process again and extract useful information.
>>
>> I had all my VM's with Debian template, I had indeed fedora template
>> removed, maybe this could affect to the upgrade process.
>
>Yes, this could affect the upgrade. If that's the case it is a bug we
>should fix before final release.
>
>> Some comments after fresh install 3.2:
>>
>> - Debian and Whonix-GW seems up to date after install, while
>fedora-23 and
>> Whonix-WS needed updates. I don't know why...
>
>This shouldn't matter as it's good practice to update the system after
>installation anyway. In a month all the templates will have some
>updates
>pending.
>
>> - I have sys-usb working fine but only with Fedora template, could I
>migrate
>> it to Debian?
>
>What are the problems with Debian template there?
Marek Marczykowski-Górecki
Jul 31, 2016, 9:36:44 AM7/31/16
to donoban, qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hash: SHA256
included in default template image.
- --
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-----
Version: GnuPG v2
bm84Uu6K6DHRAPyS28k0eoJ30XsGd03Z5kIc51AlqAW8xDnFXegcx1rutz1JuHzw
Or6y4wypzBPkLzbbJo2jQ9ZdEO57zknRE3qUiQU8sTEM2NHKpNcj9P2dRmk20l1O
VX/0T8TIy+djLqVwQgNYgDF7dMW9FM2tfliaEFedTbLq2lSacXNrCl72KsfbaNCN
Z2fhqf1mgS1T89T36Rakc1OdtCi0UGKpUqlUIbzLK1zoQPqeNt8XtBGf7/5cbXou
C8o9l0VTkcVFbafXPdMLP6EVjrpTPcRl1VNFfP1GyK5eH1+rwoDKBXrqAemuhpQ=
=IJSL
-----END PGP SIGNATURE-----
donoban
Jul 31, 2016, 1:04:57 PM7/31/16
to qubes-users
On 07/31/2016 03:36 PM, Marek Marczykowski-Górecki wrote:
>>> On Sun, Jul 31, 2016 at 01:53:26PM +0200, donoban wrote:
>>>> - I have sys-usb working fine but only with Fedora template, could I
>>> migrate
>>>> it to Debian?
>>>
>>> What are the problems with Debian template there?
>>
>> USB keyboard and mouse doesn't work.
>
> Make sure you have qubes-input-proxy package installed. It is not
> included in default template image.
>
Installed qubes-input-proxy-sender and works fine now, thanks Marek.
>>> On Sun, Jul 31, 2016 at 01:53:26PM +0200, donoban wrote:
>>>> - I have sys-usb working fine but only with Fedora template, could I
>>> migrate
>>>> it to Debian?
>>>
>>> What are the problems with Debian template there?
>>
>> USB keyboard and mouse doesn't work.
>
> Make sure you have qubes-input-proxy package installed. It is not
> included in default template image.
>
raah...@gmail.com
Aug 1, 2016, 12:59:08 PM8/1/16
to qubes-users, don...@riseup.net
I had the same exact issue with the experimental upgrade. I also ended up just doing a fresh install.
donoban
Aug 2, 2016, 5:44:45 AM8/2/16
to qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hash: SHA256
On 07/31/2016 02:33 PM, Marek Marczykowski-Górecki wrote:
> On Sun, Jul 31, 2016 at 01:53:26PM +0200, donoban wrote:
>> Hi,
>
>> I tried to do the experimental process for upgrading to Qubes
>> 3.2. I followed the steps from
>> https://www.qubes-os.org/doc/upgrade-to-r3.2/
>
>
>> All went fine until I rebooted the system (step 7). After
>> rebooting I had a lot of packages for update on dom0 (more than
>> 1000), and when I tried to update them it failed because some
>> dependency problems (I remember some perl packages but maybe
>> there were more packages with problems).
>
> Those packages should be already handled in step 4.
Ok, doing same process on my other computer I've noticed I was
> On Sun, Jul 31, 2016 at 01:53:26PM +0200, donoban wrote:
>> Hi,
>
>> I tried to do the experimental process for upgrading to Qubes
>> 3.2. I followed the steps from
>> https://www.qubes-os.org/doc/upgrade-to-r3.2/
>
>
>> All went fine until I rebooted the system (step 7). After
>> rebooting I had a lot of packages for update on dom0 (more than
>> 1000), and when I tried to update them it failed because some
>> dependency problems (I remember some perl packages but maybe
>> there were more packages with problems).
>
> Those packages should be already handled in step 4.
confused the first time. When I checked the qubes-core-dom0 I though
it said version 3.2.X installed, but it was AVAILABLE. So there the
dependency problem exists already in this step but I didn't notice.
Doing the command with --clean doesn't help. How can I provide an
useful log of this?
Regards.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJXoGuGAAoJEBQTENjj7QilMCUQAJGIJmdPO9vTvcuYzDynqBkx
Version: GnuPG v2
eZIDUvC9AtHeZ8g37PeDmE6OpiDCYqF8Gx7njA2WpWwpVVAxGYZPb1b9gUeUUokN
NRlHNtzbdXvaIdYh6JejS2YuR1M5Iijy3tV6DUSqLTaDowpwdZNm5pBFOtsf1/UO
0n47K5/auLKkNplrgAS3roRFbt6K120hqsIYiWNJw4gNMGebSH9RcFnDlb13j9OD
83eFbfcPywHf8/WlmuKXmBJj70h/UKoVLakR7k0rHupGSzhwYHwY1azjzpb6ZEmR
3FoP9e67gIbJJT83H6qTsH14lqvDvf7BrmtMJAzUOmWDa3rAodkxgfk7M88Yv0gd
mhr3lJmLBR2iUlUucmx5eydTCws7sWAUAwe551f3ZnMnNCvr7+Z2JG/Nzrc/Xf/F
msukG+cMuMVd+G6rrGMF+Tj/5b9PW6XQA8WuMbQT90i3Uz6H21O0QI5H+K1MEQs4
ZYN4bNuoSr9hK+yBmm0m6TD1h39DrQ4RFIn38iIGAVfU52cabsZRPFX89prt8WNv
UVNUqprqbj3XgIA1BIDsxvjrbhkkqTxBoLmQOtZwafIF3s840S5AP1j4Q3RVbSSG
OnITmHqt+ynlXbHfUHBy4V0qI1M2QDmLk8MSlGREFnUi/Ky7VFYU9sn31LCTd4hh
4Jo1rKCPvspFtIQ65HOj
=EMFl
-----END PGP SIGNATURE-----
donoban
Aug 2, 2016, 8:18:24 AM8/2/16
to qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hash: SHA256
On 08/02/2016 11:44 AM, donoban wrote:
>
>
> On 07/31/2016 02:33 PM, Marek Marczykowski-Górecki wrote:
>> On Sun, Jul 31, 2016 at 01:53:26PM +0200, donoban wrote:
>>> Hi,
>
>>> I tried to do the experimental process for upgrading to Qubes
>>> 3.2. I followed the steps from
>>> https://www.qubes-os.org/doc/upgrade-to-r3.2/
>
>
>>> All went fine until I rebooted the system (step 7). After
>>> rebooting I had a lot of packages for update on dom0 (more
>>> than 1000), and when I tried to update them it failed because
>>> some dependency problems (I remember some perl packages but
>>> maybe there were more packages with problems).
>
>> Those packages should be already handled in step 4.
>
> Ok, doing same process on my other computer I've noticed I was
> confused the first time. When I checked the qubes-core-dom0 I
> though it said version 3.2.X installed, but it was AVAILABLE. So
> there the dependency problem exists already in this step but I
> didn't notice.
>
> Doing the command with --clean doesn't help. How can I provide an
> useful log of this?
>
> Regards.
>
I've pasted the update log:
>
>
> On 07/31/2016 02:33 PM, Marek Marczykowski-Górecki wrote:
>> On Sun, Jul 31, 2016 at 01:53:26PM +0200, donoban wrote:
>>> Hi,
>
>>> I tried to do the experimental process for upgrading to Qubes
>>> 3.2. I followed the steps from
>>> https://www.qubes-os.org/doc/upgrade-to-r3.2/
>
>
>>> All went fine until I rebooted the system (step 7). After
>>> rebooting I had a lot of packages for update on dom0 (more
>>> than 1000), and when I tried to update them it failed because
>>> some dependency problems (I remember some perl packages but
>>> maybe there were more packages with problems).
>
>> Those packages should be already handled in step 4.
>
> Ok, doing same process on my other computer I've noticed I was
> confused the first time. When I checked the qubes-core-dom0 I
> though it said version 3.2.X installed, but it was AVAILABLE. So
> there the dependency problem exists already in this step but I
> didn't notice.
>
> Doing the command with --clean doesn't help. How can I provide an
> useful log of this?
>
> Regards.
>
https://paste.debian.net/786543
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJXoI+MAAoJEBQTENjj7QilMNwP/AhUHFQBJYe4jRJeeML9iBFb
Version: GnuPG v2
2Hfrk68Ak5wPoiZMvDCQl/mgLSo2/3UQHtrjNQOVWanDjcJ0H6XQ0DxrEogiytLj
f12g95EmmDK5/Od1sSbfKQkxIup/Ibh4whsHPX26lEA6loUivJIGGkq5FI0jer5E
iPYtiLndRUcMi1OnHuXFUp3eE0bZDeFaZ8NVV1LtporFo6G/cLk/DXyvlinaSffl
iIVudT++hUNrlKPVBEvyo1QMB8KmlbWU3a2jy8MBnedc9u/wTCStRHjgEN5Lit6S
x2/xwrOT/N0JpojRujWnVXduDF1f40/6kfkGGcBuFgNqmWNEoz2dxHDTCV91+UVN
+H7yiUDjaPLxMSPMz3og3H5Pdlyr4SfTYPJ2ZAOBoQLuRRRjE3NlNUzlw9yTEodl
HHBy5XdywFdvDkz69eRbr6socRofvzkhEzD0l/YYA7pKndgo8PvqAqi9hfFMZqOz
JWDKevIhJoeGrZUFCpbtBt63uDP4N86Qq1FHTHzEKj2pKAM54Q9vF33Ni2YVu6MI
t5nOUUSp1+64GtLOJmm1jJN4dxoPeZGDlex5M36OVQW9SQovhc6i25QOeblNd/ux
x9I8gkVKbSgyn6ILN7aN/9g4RujvyTdFxC+SGuMOy2GLsXZdeNVYyeDT4+U/dbLv
jn385ZmZ8DcTv/MonZqm
=QX4D
-----END PGP SIGNATURE-----
Marek Marczykowski-Górecki
Aug 2, 2016, 4:57:50 PM8/2/16
to donoban, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hash: SHA256
On Tue, Aug 02, 2016 at 02:18:20PM +0200, donoban wrote:
>
>
> On 08/02/2016 11:44 AM, donoban wrote:
> >
> >
> > On 07/31/2016 02:33 PM, Marek Marczykowski-Górecki wrote:
> >> On Sun, Jul 31, 2016 at 01:53:26PM +0200, donoban wrote:
> >>> Hi,
> >
> >>> I tried to do the experimental process for upgrading to Qubes
> >>> 3.2. I followed the steps from
> >>> https://www.qubes-os.org/doc/upgrade-to-r3.2/
> >
> >
> >>> All went fine until I rebooted the system (step 7). After
> >>> rebooting I had a lot of packages for update on dom0 (more
> >>> than 1000), and when I tried to update them it failed because
> >>> some dependency problems (I remember some perl packages but
> >>> maybe there were more packages with problems).
> >
> >> Those packages should be already handled in step 4.
> >
> > Ok, doing same process on my other computer I've noticed I was
> > confused the first time. When I checked the qubes-core-dom0 I
> > though it said version 3.2.X installed, but it was AVAILABLE. So
> > there the dependency problem exists already in this step but I
> > didn't notice.
> >
> > Doing the command with --clean doesn't help. How can I provide an
> > useful log of this?
> >
> > Regards.
> >
>
> I've pasted the update log:
>
> https://paste.debian.net/786543
Could you paste also list of packages in dom0 (rpm -qa)? This should
>
>
> On 08/02/2016 11:44 AM, donoban wrote:
> >
> >
> > On 07/31/2016 02:33 PM, Marek Marczykowski-Górecki wrote:
> >> On Sun, Jul 31, 2016 at 01:53:26PM +0200, donoban wrote:
> >>> Hi,
> >
> >>> I tried to do the experimental process for upgrading to Qubes
> >>> 3.2. I followed the steps from
> >>> https://www.qubes-os.org/doc/upgrade-to-r3.2/
> >
> >
> >>> All went fine until I rebooted the system (step 7). After
> >>> rebooting I had a lot of packages for update on dom0 (more
> >>> than 1000), and when I tried to update them it failed because
> >>> some dependency problems (I remember some perl packages but
> >>> maybe there were more packages with problems).
> >
> >> Those packages should be already handled in step 4.
> >
> > Ok, doing same process on my other computer I've noticed I was
> > confused the first time. When I checked the qubes-core-dom0 I
> > though it said version 3.2.X installed, but it was AVAILABLE. So
> > there the dependency problem exists already in this step but I
> > didn't notice.
> >
> > Doing the command with --clean doesn't help. How can I provide an
> > useful log of this?
> >
> > Regards.
> >
>
> I've pasted the update log:
>
> https://paste.debian.net/786543
allow me to reproduce the problem.
- --
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-----
Version: GnuPG v2
iQEcBAEBCAAGBQJXoQlIAAoJENuP0xzK19csAckH/2va8JQ20uY72MLwzymj8qPg
Version: GnuPG v2
PyE1rf2riymZOCJ16DPPgBEzY+n5nhSMeI1Gwm330s5MZwVx5OjufPLwiE3JvqVZ
X1UNoE0WK7s0MtLKGEVwWZ6dPh1M0XLExQoMMglrdGvHOFTWFuIphWX4aYhw14LG
9m7ZL3lw5HhFesO3O80empoZMSf29HQu60o7+Lc7C/N4Tne7gC4g9V1yQvEI+5vS
wXuGAw5J1U8EyT52QISWcrId9Vhev2YMsauHOR5lW5VuyvHkqBpONm16cCRdT/f7
dT2Z3O/BF+hSAp1T36bqSm334scPYgNJ4+1HB0p4DBrDly529fDMk/9FyyGC8Y8=
=NQmN
-----END PGP SIGNATURE-----
raah...@gmail.com
Aug 2, 2016, 11:22:59 PM8/2/16
to qubes-users, don...@riseup.net
donoban
Aug 3, 2016, 3:35:50 AM8/3/16
to qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hash: SHA256
On 08/02/2016 10:57 PM, Marek Marczykowski-Górecki wrote:
>
> Could you paste also list of packages in dom0 (rpm -qa)? This
> should allow me to reproduce the problem.
>
>
Yes Marek! Here is it:
>
> Could you paste also list of packages in dom0 (rpm -qa)? This
> should allow me to reproduce the problem.
>
>
https://paste.debian.net/786712
The only think that I did on both install was installing Xfce after
the default KDE install (or maybe xfce was already installed?), I am
not sure.
I hope it helps.
Regards.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJXoZ7RAAoJEBQTENjj7Qilfc0QAKpIVEqvw7I6OkaWTA3zY2f9
Version: GnuPG v2
kVZ778K5sQJ3JqxU9mtoJ8uwzloUzVJUrFBLlDwsZ9bP1X7stGL+kZulyxlAMGjK
AoX6DcKg6WVVtS1uZ8J6GSnos1IRvALbq5Vo8Gdz3wPtoPYnnMwxBXPpoJ6ON7v2
9dI70eXfzukzwYNzAbhx3x0eKeiMojS4zPtybRCW2I5upKvXyEZOWoQjrXvHnG4Y
kTxU33O7KEyhaM7jmgOTNU6If8ufgvNySONLttTDyUvjqDxc3CAKYoFqQbvVwL+x
oLmTigv5BZ/6Wgld/xlJIMyTocC1rTV21ZzahVkid8DGnvL8/U1H6sAE6a9VJbJ/
LT9jrRPFzN1QzAQ6BfGXdL3ZRmdNUc8tSainNniCO1b96c0qYOPw56lHZabqmLsV
P9MR4L966DL1vhOxgg0QhJI5r4hf72P+VltP9mfeAMUN8GehKiySNUiilNjiOa3C
dHslDgHaQDwwRweFnd3Yr6P10oXYngBfnpbm7oJxQhVCzFCWFFaBRHyjE7Egn6q7
Xse/sZau7+o5ofkQNsllAH/US0/jvRHNq+BdEZdWGoB8hORrCqtr8BrQp5L7FFf8
HEJExwNnRIdsOekktLzEI4SALs0RwB8h0bpC2g0twNRdxNENypEZsL1LFdL6kaXR
8kXswezl6DIz86Q7/lm8
=N4hL
-----END PGP SIGNATURE-----
donoban
Aug 3, 2016, 4:05:57 AM8/3/16
to qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hash: SHA256
On 08/03/2016 09:35 AM, donoban wrote:
> The only think that I did on both install was installing Xfce
> after the default KDE install
>
Ah and I removed the fedora templates -_-
> The only think that I did on both install was installing Xfce
> after the default KDE install
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJXoaXhAAoJEBQTENjj7QiltWIP/0KtMn38RUQDdNnkqT9nyVDX
Version: GnuPG v2
oRcty9OwAbskp/AHAxAuFyGbL5aKibqzn7Z9NL99QC55/wKne90XPVU7WjYcXuIy
2JRxIZvn+dA0X2clpEpxiyL0CyXXxh3u0NGBUgWcufOjVHZ9mF+9XDE/70Bac4A+
ItkLod2aRHVVMAI2x9/K7Fk1GFzLN7KL3FwUp+aGtz2oBVTETN40DNzEk9PvtVCA
YNeQxvXoCdkOiXOhgsymGXCxJEI3RRt7x7HVPaqy/3TKpTaQrTN6IJN4uOYsM8K3
Gokgi3lUEJHEiNq0rsIqSHee7E4VXPTO54LtPMPFSZWaHc45yeViNyPIBGoMQtzs
2mnFO4IEaktBkjuMFJCZ54DjgueiuJPtcQDALCzFhGV32oDMyL/pyGpqTTP2usa9
xGpN7Owtk9F/yLDcWXwHBfCAqUcz/DhTY2qP0dAD7CBHq/liff4rJZHgWXnqwBf9
Lq78KE4Er5/ogQ8bGsn+G9dzT9gZziuvkX9mgI12Z9sl407fQiRQhS3SRim+Pp8K
o+O5sMGgBgU7fo8+2wKGZ1BWeUckt5XIbnOvUSK6UaX7l8QiZ6Qhqp1Jh5OqWcOp
kWhlzAXo0uWuAskTJ1W1JsA8AsbsqEVTcfsWci7+4w5GMErypS8Ny716EJg2aumt
005OaS8W2YMwDQkVqjSK
=eSwx
-----END PGP SIGNATURE-----
Marek Marczykowski-Górecki
Aug 5, 2016, 2:27:10 PM8/5/16
to donoban, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hash: SHA256
On Wed, Aug 03, 2016 at 09:35:45AM +0200, donoban wrote:
> On 08/02/2016 10:57 PM, Marek Marczykowski-Górecki wrote:
> >
> > Could you paste also list of packages in dom0 (rpm -qa)? This
> > should allow me to reproduce the problem.
> >
> >
>
> Yes Marek! Here is it:
> https://paste.debian.net/786712
>
> The only think that I did on both install was installing Xfce after
> the default KDE install (or maybe xfce was already installed?), I am
> not sure.
>
> I hope it helps.
I've added additional step to the instruction[1] for Debian-based UpdateVM:
> On 08/02/2016 10:57 PM, Marek Marczykowski-Górecki wrote:
> >
> > Could you paste also list of packages in dom0 (rpm -qa)? This
> > should allow me to reproduce the problem.
> >
> >
>
> Yes Marek! Here is it:
> https://paste.debian.net/786712
>
> The only think that I did on both install was installing Xfce after
> the default KDE install (or maybe xfce was already installed?), I am
> not sure.
>
> I hope it helps.
If you are using Debian-based VM as UpdateVM (sys-firewall by default),
you need to download few more packages manually, but do not install them
yet:
sudo qubes-dom0-update systemd-compat-libs perl-libwww-perl
perl-Term-ANSIColor perl-Term-Cap gdk-pixbuf2-xlib speexdsp
qubes-mgmt-salt-admin-tools
(...)
Transaction Summary
===============================================================
Install 15 Packages (+ 31 Dependent packages)
Upgrade 4 Packages (+200 Dependent packages)
Total download size: 173 M
Is this ok [y/d/N]: n
Exiting on user command
Your transaction was saved, rerun it with:
yum load-transaction /tmp/yum_save_tx.....
Please let me know if that helps.
[1] https://www.qubes-os.org/doc/upgrade-to-r3.2/
- --
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-----
Version: GnuPG v2
iQEcBAEBCAAGBQJXpNp4AAoJENuP0xzK19csRlYH/1C3pqb5UVcpXSTGKD0QriKf
Version: GnuPG v2
P9QYza6aPFbJkqLXlmNQQpYifO7Le/JGcByQfBWYRWkyz8F0bj6ccUr6VQ4Zf/VM
ZQXE9opp/pDO/UVE7LFuzzkK9coKecdFrlc1cUfHM/RnYc/PQ4Iz1iCdQg849m+M
4HGUmWV7LoDnlama+OOC3cMhBTNfLvqfi1tj/ot1/DRLligu6ylMcjEe+7IkNivq
PdIvkuPjml91AjZ0+Up6OW9upCa0qmjUjDbkUQqghqCLRsdtMLBZbg0ibpYVEJ5H
xOqTXrXxvh7W9Qc+edt1rDTcQTFoPyMgbxlzTRBEh+ewTuJ+1NtwZCRZA16gQz4=
=wR9Q
-----END PGP SIGNATURE-----
Marek Marczykowski-Górecki
Aug 6, 2016, 4:04:10 PM8/6/16
to donoban, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hash: SHA256
about). Also it looks like a template from Qubes 3.0 (qubes-core-agent
3.0.14, qubes-gui-agent 3.0.14), not 3.1 nor 3.2. Keep in mind that
direct 3.0 -> 3.2 upgrade is not supported. While it may work in some
cases, it is safer to upgrade first to 3.1, then to 3.2.
This particular issue looks like a bug in dependencies which was present
some time ago. Should be fixed by "apt-get dist-upgrade" instead of
"apt-get upgrade".
- --
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-----
Version: GnuPG v2
irUdxwERJ9T5hJqhkM4K2+gleYgQisvn92p7A+TFeJ1vBocsyU4e4yg63VFskIxn
1SdbGFXHq21kvLpuJkEbCuMZ7kiH1+eIahKM6Pc+Q1jsDOCYc7V85nJLFp5EGi5J
zz/3p1z1wZw8/HB2Zd4pLeEwlV6LoYusx7hvFHvpHdNLS7h3YIVNDmvWiK5idyRv
9jNlTOeqq2vcjdQxCapsVErtJ97642ctM3Stt3ru4dBLFQHwjodf5SXBPw4MGkBX
5DeNcQEfDv5VQNj58YBdOwN2ppC0kHlZ+/6202q2MW58jd0ALy7NQAWQBb4ABZ0=
=ojus
-----END PGP SIGNATURE-----
donoban
Aug 6, 2016, 5:51:26 PM8/6/16
to Marek Marczykowski-Górecki, qubes...@googlegroups.com
It sounds like I've sent wrong log, I will check it.
donoban
Aug 7, 2016, 5:49:20 AM8/7/16
to qubes...@googlegroups.com
On Sat, 06 Aug 2016 21:51:14 +0000
donoban <don...@riseup.net> wrote:
> It sounds like I've sent wrong log, I will check it.
>
Here is the right log :)donoban <don...@riseup.net> wrote:
> It sounds like I've sent wrong log, I will check it.
>
Marek Marczykowski-Górecki
Aug 7, 2016, 8:40:06 AM8/7/16
to donoban, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hash: SHA256
> on the /boot filesystem
Looks like out of disk space... Try to remove older kernel packages.
> 12:17:23 : YUM: file
> /usr/share/locale/ar/LC_MESSAGES/kactivities5.mo conflicts between
> attempted installs of kf5-kactivities-libs-5.14.0-1.fc23.x86_64 and
> kactivitymanagerd-5.7.2-1.fc23.x86_64
Try to remove kactivitymanagerd before upgrade. But do review package
list needed to remove too - if only a single package, that's ok, but if
almost a whole KDE, you may not want to do this. Unless you want to
switch to Xfce anyway ;)
- --
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-----
Version: GnuPG v2
LcoJqWc753f9kMwaNSYBDbD2SYA2LNXMMNeuE08l9Y2T7N/SOsfbSMJmnMHN9NEF
drMggee+MPgIpK9ge6gxaJwNAZ7gk1T8yLBY3kwKSOMIMg/t6oOtR7C+BGX/kAI3
pEnai3ul89osJAiNYS9MzK/haWoH/Zj+MJ4ONyrwvizkqw5DAVwadTsni+za09YF
yvUszCBMXEPviU4IsnQR3OS6/58njP4gbspP8xSZ29qn21vlhaXMA+N+42Poi3x7
XuXyyfgd2P7LSjc7mFteJGVjwVhYrNEaDN7n6D+t7qlBYN5tXv6OPcvTF96kYdg=
=tQkT
-----END PGP SIGNATURE-----
donoban
Aug 9, 2016, 3:18:44 AM8/9/16
to qubes...@googlegroups.com
On Sun, 7 Aug 2016 14:39:59 +0200
Marek Marczykowski-Górecki <marm...@invisiblethingslab.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On Sun, Aug 07, 2016 at 11:49:04AM +0200, donoban wrote:
> > On Sat, 06 Aug 2016 21:51:14 +0000
> > donoban <don...@riseup.net> wrote:
> >
> > > It sounds like I've sent wrong log, I will check it.
> > >
> >
> >
> > Here is the right log :)
>
> > installing package kernel-1000:4.4.14-11.pvops.qubes.x86_64 needs
> > 17MB on the /boot filesystem
>
> Looks like out of disk space... Try to remove older kernel packages.
>
Ops, sorry Marek I did a too small boot partition and I have to do it
Marek Marczykowski-Górecki <marm...@invisiblethingslab.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On Sun, Aug 07, 2016 at 11:49:04AM +0200, donoban wrote:
> > On Sat, 06 Aug 2016 21:51:14 +0000
> > donoban <don...@riseup.net> wrote:
> >
> > > It sounds like I've sent wrong log, I will check it.
> > >
> >
> >
> > Here is the right log :)
>
> > installing package kernel-1000:4.4.14-11.pvops.qubes.x86_64 needs
> > 17MB on the /boot filesystem
>
> Looks like out of disk space... Try to remove older kernel packages.
>
always when I install a kernel update.
> > 12:17:23 : YUM: file
> > /usr/share/locale/ar/LC_MESSAGES/kactivities5.mo conflicts between
> > attempted installs of kf5-kactivities-libs-5.14.0-1.fc23.x86_64 and
> > kactivitymanagerd-5.7.2-1.fc23.x86_64
>
> Try to remove kactivitymanagerd before upgrade. But do review package
> list needed to remove too - if only a single package, that's ok, but
> if almost a whole KDE, you may not want to do this. Unless you want to
> switch to Xfce anyway ;)
>
however I don't find kactivimanagerd package.
Anyway now I'm only getting this error:
file /usr/sbin/blkdeactivate from install of
device-mapper-1.02.109-2.fc23.x86_64 conflicts with file from package
lvm2-2.02.106-1.fc20.x86_64
And if I try to remove it I get:
Dependencies Resolved
==================================================================================================================================
Package Arch
Version Repository Size
==================================================================================================================================
Removing: lvm2 x86_64
2.02.106-1.fc20 @anaconda/R3.1 1.6 M
Removing for dependencies:
libvirt-daemon-driver-storage
x86_64 1.2.20-4.fc20
@anaconda/R3.1 435 k
libvirt-daemon-xen x86_64
1.2.20-4.fc20 @anaconda/R3.1 0.0
qubes-core-dom0 x86_64
3.1.17-1.fc20 @qubes-dom0-cached/3.1 1.6 M
qubes-core-dom0-linux x86_64
3.1.12-1.fc20 @qubes-dom0-cached/3.1 220 k
qubes-gui-dom0 x86_64
3.1.4-1.fc20 @qubes-dom0-cached/3.1 145 k
qubes-manager x86_64
3.1.3-1.fc20 @qubes-dom0-cached/3.1 4.5 M
qubes-template-debian-8 noarch
3.0.4-201512042202 @anaconda/R3.1 1.8 G
qubes-template-whonix-gw noarch
3.0.4-201512041732 @anaconda/R3.1 2.1 G
qubes-template-whonix-ws noarch
3.0.4-201511301146 @anaconda/R3.1 2.5 G
What should I do?
Marek Marczykowski-Górecki
Aug 9, 2016, 5:31:18 AM8/9/16
to donoban, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hash: SHA256
- --
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-----
Version: GnuPG v2
3ayF1jHhL4G7ajvZ67JvBim9EBzcZ5aFVleJG+lbrUkYh7/Xr3x52Xnk5Rdwl7jY
jLbGy2/l0/4Rk5kf/A78mi7mPYAqTpmudnJzJLrEdjSHSuwSrVjLBj8l776Vwz4J
4iNHs4ww+N06v9O0OdxA+ccRXHsvdcy6aOVHGpZu9o8M7kNPDm4b0Nahq2BsT4dv
1MYKFk3HxKfpQ1BlI32eABYijoxs1/ZXgnLpuCutdwCtVvUIyt7gO5lktMnP74n0
edwXiYaJ9xdhTkEi/zUBYkZKaT9PlD7yySnvEuiyCflRL7pYri3dHrOkTn5J9WY=
=Nr4g
-----END PGP SIGNATURE-----
donoban
Aug 9, 2016, 2:02:33 PM8/9/16
to qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hash: SHA256
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJXqhqrAAoJEBQTENjj7Qil3iIP/0w46Sr6sMsrNi7aZMaOtIYA
Version: GnuPG v2
DnoeE/qTb4zMtvqIfauuEGiB21go0rc7zcGKeMCbZukapaejyyyhv5FqR0SYSZrv
Wh91+3yxCzSCXBr56kO0YGeYDKW1o6KPMpFEjhmp9yG5fs3lwUmE20ZfhfNwHdzF
VOyLLco5uaJCZnSmR/tLzx18MyZBIDsSaxV4k8JJkoCjYXJORnS9YWMS6PUewPBA
FgvmDPGQlwSEOYEQdEQWCE1KSKJTBKKf+YyxlVjEjCD+GdvGtRc8ZLYI6SanzIVk
hCP4REN1VbJUsI26Sb+zLn7u2DsosjeVeCQVgGoJQ/h/jDvapHsXcgd5QZ5G2BxC
ItbVLRC86b4JKpP0yBeLbZx1pz1KGUDwDQG7KwYoXBAPrnsHgCLR6hT91F7a4CA1
mValCuImqdOlP/GeBCqVyTpKgx96B7kHPeZ9N2CtMrENCguojwFrEkmiTQoEV96k
6vCZiQWtMYG2IcbB0fqAaiGyzrytkYYRe1ruXw5B6iNOvB67DH6l8z2sDT5XEc5G
2ljd23HP1QB5Z/LMjIvRtW0K4e6h++iNdnP/N09XhgH41RzXTc3VdzyC9kekxLeG
xXUAR44XUC7UZOUGxHysyZuZJIi+mlCdKiWHhw3+1/qaRnV3E/SO/i8hWcCMEajB
HwLK2BKoGSz7kV6ctxpS
=mSv6
-----END PGP SIGNATURE-----
Reply all
Reply to author
Forward
0 new messages