Trying to do an in-place upgrade from 3.1.17 to 3.2
104 views
Skip to first unread message
Richard
Oct 30, 2016, 1:00:08 PM10/30/16
to qubes-users
I'm trying to upgrade my Qubes 3.1.17 to 3.2 I've followed the steps outlined here: https://www.qubes-os.org/doc/upgrade-to-r3.2/ However, when I run...
sudo qubes-dom0-update --releasever=3.2 qubes-release
I receive:
Loaded plugins: yum-qubes-hooks
Nothing to do
No packages downloaded
file:///var/lib/qubes/updates/repodata/repomd.xml: [Errno 14] curl#37 - "Couldn't open file /var/lib/qubes/updates/repodata/repomd.xml"
Trying other mirror.
Nothing to do
So of course running... sudo qubes-dom0-update --clean also provides a similar error:
Errno 14] curl#7 - "Failed to connect to pubmirror1.math.uh.edu port 443: No route to host"
Trying other mirror.
No new updates available
No updates avaliable
Is anybody able to advise me what I need to do to be able to do an in-place upgrade to 3.2?
Thanks,
Richard
Richard
Nov 2, 2016, 11:26:18 AM11/2/16
to qubes-users
Just wondering if anyone has any ideas as I would really like to do an in-place upgrade to 3.2.
Holger Levsen
Nov 4, 2016, 8:51:01 PM11/4/16
to qubes-users, Richard
Hi,
On Wed, Nov 02, 2016 at 08:26:18AM -0700, Richard wrote:
> On Sunday, October 30, 2016 at 12:00:08 PM UTC-5, Richard wrote:
> > I'm trying to upgrade my Qubes 3.1.17 to 3.2 I've followed the steps outlined here: https://www.qubes-os.org/doc/upgrade-to-r3.2/ However, when I run...
> >
> > sudo qubes-dom0-update --releasever=3.2 qubes-release
> >
> > I receive:
> > Loaded plugins: yum-qubes-hooks
> > Nothing to do
> > No packages downloaded
> > file:///var/lib/qubes/updates/repodata/repomd.xml: [Errno 14] curl#37 - "Couldn't open file /var/lib/qubes/updates/repodata/repomd.xml"
> > Trying other mirror.
> > Nothing to do
> >
> > So of course running... sudo qubes-dom0-update --clean also provides a similar error:
> >
> > Errno 14] curl#7 - "Failed to connect to pubmirror1.math.uh.edu port 443: No route to host"
> > Trying other mirror.
> > No new updates available
> > No updates avaliable
> >
> > Is anybody able to advise me what I need to do to be able to do an in-place upgrade to 3.2?
I stumbled upon the issue, when upgrading a 3.0 system to 3.1 and then
to 3.2 - did you do the same?
I believe I also found a workaround:
sudo qubes-dom0-update enablerepo=qubes-dom0-current-testing --releasever=3.2 qubes-release
sudo qubes-dom0-update enablerepo=qubes-dom0-current --releasever=3.2
but then sadly my system crashed during the upgrade (not sure whether
this was hardware fault or bad software which didnt cope with me using
qubes-manager during the dom0 upgrade) and now I'm stuck between 3.1
and 3.2 and the UI doesnt work anymore, so I cannot finish the upgrade
of dom0, as I also could't start sys-net and sys-firewall
manually on the shell :/
(yum-complete-transaction also didnt help, I thought all the packages
were downloaded already and this was supposed to work?)
What way is there to recover the system now?
(The system is just a test system, so I could and probably soon will
just reinstall, and I know I could copy the VMs over… but… I'm curious
how to bring this installation back to life… :)
--
cheers,
Holger
p.s./btw: https://www.qubes-os.org/doc/upgrade-to-r3.1/ advices one to
install qubes-mgmt-salt-admin-tools but this package does not exist?!
On Wed, Nov 02, 2016 at 08:26:18AM -0700, Richard wrote:
> On Sunday, October 30, 2016 at 12:00:08 PM UTC-5, Richard wrote:
> > I'm trying to upgrade my Qubes 3.1.17 to 3.2 I've followed the steps outlined here: https://www.qubes-os.org/doc/upgrade-to-r3.2/ However, when I run...
> >
> > sudo qubes-dom0-update --releasever=3.2 qubes-release
> >
> > I receive:
> > Loaded plugins: yum-qubes-hooks
> > Nothing to do
> > No packages downloaded
> > file:///var/lib/qubes/updates/repodata/repomd.xml: [Errno 14] curl#37 - "Couldn't open file /var/lib/qubes/updates/repodata/repomd.xml"
> > Trying other mirror.
> > Nothing to do
> >
> > So of course running... sudo qubes-dom0-update --clean also provides a similar error:
> >
> > Errno 14] curl#7 - "Failed to connect to pubmirror1.math.uh.edu port 443: No route to host"
> > Trying other mirror.
> > No new updates available
> > No updates avaliable
> >
> > Is anybody able to advise me what I need to do to be able to do an in-place upgrade to 3.2?
to 3.2 - did you do the same?
I believe I also found a workaround:
sudo qubes-dom0-update enablerepo=qubes-dom0-current-testing --releasever=3.2 qubes-release
sudo qubes-dom0-update enablerepo=qubes-dom0-current --releasever=3.2
but then sadly my system crashed during the upgrade (not sure whether
this was hardware fault or bad software which didnt cope with me using
qubes-manager during the dom0 upgrade) and now I'm stuck between 3.1
and 3.2 and the UI doesnt work anymore, so I cannot finish the upgrade
of dom0, as I also could't start sys-net and sys-firewall
manually on the shell :/
(yum-complete-transaction also didnt help, I thought all the packages
were downloaded already and this was supposed to work?)
What way is there to recover the system now?
(The system is just a test system, so I could and probably soon will
just reinstall, and I know I could copy the VMs over… but… I'm curious
how to bring this installation back to life… :)
--
cheers,
Holger
p.s./btw: https://www.qubes-os.org/doc/upgrade-to-r3.1/ advices one to
install qubes-mgmt-salt-admin-tools but this package does not exist?!
Marek Marczykowski-Górecki
Nov 4, 2016, 8:57:49 PM11/4/16
to qubes-users, Richard
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
What exactly do you mean? Some X server startup error? Do you have any
logs?
> so I cannot finish the upgrade
> of dom0, as I also could't start sys-net and sys-firewall
> manually on the shell :/
>
> (yum-complete-transaction also didnt help, I thought all the packages
> were downloaded already and this was supposed to work?)
>
> What way is there to recover the system now?
What exactly do you get when trying to start sys-net and sys-firewall
from shell? `qvm-start sys-firewall` should work just fine from text
console. Of course you'll not get GUI there, but qvm-run should work.
> (The system is just a test system, so I could and probably soon will
> just reinstall, and I know I could copy the VMs over… but… I'm curious
> how to bring this installation back to life… :)
- --
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
iQEcBAEBCAAGBQJYHS6LAAoJENuP0xzK19csTEgH/2w4hSi+nU6eWvothb6aP1wJ
J9uRvrYMufZFVfZcZqx/+1AUC7VGqnTrmT8MKuWz3TWopRx9UFbAaDH6YIsJf63T
yTs0UK1GM2r9wx0Nf2Ua6/V13IEE7LrVmwmss6cB5GGErYJ6Ge27KmuTV5xE7W4R
aMvFb7dOHaaucLq+ft8JTKmTWDi5xC8PJrA7kyniIp069xuuHYEcJbdK3/CGOXrh
dK9z/p9yxZMjQO6zIlIavUtlHiZqbmEA5G8YSff0It2ZN7iCahycyj46bRwKkvJv
lUfVuPgJqcLIKOL21Mq+c8DdpM4xupt+GtdHJVDLc5hOx//pbbqwM2AES8uZG64=
=w64B
-----END PGP SIGNATURE-----
Hash: SHA256
logs?
> so I cannot finish the upgrade
> of dom0, as I also could't start sys-net and sys-firewall
> manually on the shell :/
>
> (yum-complete-transaction also didnt help, I thought all the packages
> were downloaded already and this was supposed to work?)
>
> What way is there to recover the system now?
from shell? `qvm-start sys-firewall` should work just fine from text
console. Of course you'll not get GUI there, but qvm-run should work.
> (The system is just a test system, so I could and probably soon will
> just reinstall, and I know I could copy the VMs over… but… I'm curious
> how to bring this installation back to life… :)
> p.s./btw: https://www.qubes-os.org/doc/upgrade-to-r3.1/ advices one to
> install qubes-mgmt-salt-admin-tools but this package does not exist?!
That's interesting, this step should be in 3.1->3.2 instruction...
> install qubes-mgmt-salt-admin-tools but this package does not exist?!
- --
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
iQEcBAEBCAAGBQJYHS6LAAoJENuP0xzK19csTEgH/2w4hSi+nU6eWvothb6aP1wJ
J9uRvrYMufZFVfZcZqx/+1AUC7VGqnTrmT8MKuWz3TWopRx9UFbAaDH6YIsJf63T
yTs0UK1GM2r9wx0Nf2Ua6/V13IEE7LrVmwmss6cB5GGErYJ6Ge27KmuTV5xE7W4R
aMvFb7dOHaaucLq+ft8JTKmTWDi5xC8PJrA7kyniIp069xuuHYEcJbdK3/CGOXrh
dK9z/p9yxZMjQO6zIlIavUtlHiZqbmEA5G8YSff0It2ZN7iCahycyj46bRwKkvJv
lUfVuPgJqcLIKOL21Mq+c8DdpM4xupt+GtdHJVDLc5hOx//pbbqwM2AES8uZG64=
=w64B
-----END PGP SIGNATURE-----
Holger Levsen
Nov 4, 2016, 9:16:31 PM11/4/16
to qubes-users
Hi Marek,
> What exactly do you mean? Some X server startup error? Do you have any
> logs?
X crashed or the system shut down.
(It was late at night and due to other hardware problems (using external
monitor which at this moment I didnt use anymore since an hour) I had
experienced many unexpected sudden poweroffs before so I dont really
recall whether just X crashed or the hw…)
> What exactly do you get when trying to start sys-net and sys-firewall
> from shell? `qvm-start sys-firewall` should work just fine from text
> console. Of course you'll not get GUI there, but qvm-run should work.
ERROR: ERROR: Failed to connect to qmemman: [Errno 2] No such file or
directory
> > p.s./btw: https://www.qubes-os.org/doc/upgrade-to-r3.1/ advices one to
> > install qubes-mgmt-salt-admin-tools but this package does not exist?!
> That's interesting, this step should be in 3.1->3.2 instruction...
ah. so I guess I should send a patch for qubes-doc tomorrow… (gn8 ;)
--
cheers,
Holger
On Sat, Nov 05, 2016 at 01:57:44AM +0100, Marek Marczykowski-Górecki wrote:
> > I believe I also found a workaround:
> > sudo qubes-dom0-update enablerepo=qubes-dom0-current-testing --releasever=3.2 qubes-release
> > sudo qubes-dom0-update enablerepo=qubes-dom0-current --releasever=3.2
does that make sense?
> > I believe I also found a workaround:
> > sudo qubes-dom0-update enablerepo=qubes-dom0-current-testing --releasever=3.2 qubes-release
> > sudo qubes-dom0-update enablerepo=qubes-dom0-current --releasever=3.2
> What exactly do you mean? Some X server startup error? Do you have any
> logs?
(It was late at night and due to other hardware problems (using external
monitor which at this moment I didnt use anymore since an hour) I had
experienced many unexpected sudden poweroffs before so I dont really
recall whether just X crashed or the hw…)
> What exactly do you get when trying to start sys-net and sys-firewall
> from shell? `qvm-start sys-firewall` should work just fine from text
> console. Of course you'll not get GUI there, but qvm-run should work.
directory
> > p.s./btw: https://www.qubes-os.org/doc/upgrade-to-r3.1/ advices one to
> > install qubes-mgmt-salt-admin-tools but this package does not exist?!
> That's interesting, this step should be in 3.1->3.2 instruction...
--
cheers,
Holger
Joonas Lehtonen
Nov 5, 2016, 6:11:07 AM11/5/16
to qubes-users
Richard:
> I'm trying to upgrade my Qubes 3.1.17 to 3.2 I've followed the steps outlined here: https://www.qubes-os.org/doc/upgrade-to-r3.2/ However, when I run...
>
> sudo qubes-dom0-update --releasever=3.2 qubes-release
>
> I receive:
> Nothing to do
>
> sudo qubes-dom0-update --releasever=3.2 qubes-release
>
> I receive:
>
I'm also following steps in
https://www.qubes-os.org/doc/upgrade-to-r3.2/
but having the same problem ("Nothing to do.").
Maybe because there are simply no packages in
http://yum.qubes-os.org/r3.2/current/dom0/fc20/rpm/
?
There is a package here
http://yum.qubes-os.org/r3.2/current-testing/dom0/fc20/rpm/
(as mentioned by Holger)
(just in http://yum.qubes-os.org/r3.2/current/dom0/fc23/rpm/)
What are the recommended steps?
Will the package in r3.2/current-testing move one day into r3.2/current?
thanks,
Joonas
Marek Marczykowski-Górecki
Nov 5, 2016, 10:58:24 AM11/5/16
to qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hash: SHA256
On Sat, Nov 05, 2016 at 01:16:25AM +0000, Holger Levsen wrote:
> Hi Marek,
> On Sat, Nov 05, 2016 at 01:57:44AM +0100, Marek Marczykowski-Górecki wrote:
> > > I believe I also found a workaround:
> > > sudo qubes-dom0-update enablerepo=qubes-dom0-current-testing --releasever=3.2 qubes-release
> > > sudo qubes-dom0-update enablerepo=qubes-dom0-current --releasever=3.2
>
> does that make sense?
Oh, indeed qubes-release were only in testing repository for "fc20" base
> Hi Marek,
> On Sat, Nov 05, 2016 at 01:57:44AM +0100, Marek Marczykowski-Górecki wrote:
> > > I believe I also found a workaround:
> > > sudo qubes-dom0-update enablerepo=qubes-dom0-current-testing --releasever=3.2 qubes-release
> > > sudo qubes-dom0-update enablerepo=qubes-dom0-current --releasever=3.2
>
> does that make sense?
distribution - which is the case in the first stage of in-place upgrade.
Fixed.
> > What exactly do you mean? Some X server startup error? Do you have any
> > logs?
>
> X crashed or the system shut down.
>
> (It was late at night and due to other hardware problems (using external
> monitor which at this moment I didnt use anymore since an hour) I had
> experienced many unexpected sudden poweroffs before so I dont really
> recall whether just X crashed or the hw…)
>
> > What exactly do you get when trying to start sys-net and sys-firewall
> > from shell? `qvm-start sys-firewall` should work just fine from text
> > console. Of course you'll not get GUI there, but qvm-run should work.
>
> ERROR: ERROR: Failed to connect to qmemman: [Errno 2] No such file or
> directory
> > > p.s./btw: https://www.qubes-os.org/doc/upgrade-to-r3.1/ advices one to
> > > install qubes-mgmt-salt-admin-tools but this package does not exist?!
> > That's interesting, this step should be in 3.1->3.2 instruction...
>
> ah. so I guess I should send a patch for qubes-doc tomorrow… (gn8 ;)
- --
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
V3WgQo8Y91yvCw/q+RsfbiERYfv1FLIRSmJnk844T/tuRl9XaFOwaM1+gIsghIH6
WFQcqMAfItev0mBjMSkPMMHRHZA+sgLyfchAepbIm+qkgPD1HjXRK00Nq7daU390
YFWfyUAaxxNowz8l8E14Bt4MXyyTetaU8UbpuRPuMNVODD7V+VzhdCs+BNhwtRZZ
YL6uAruU3D2oGnpj6Vs4zGdQ2VJePZh7odaTCoYynQ1tBjklBeVyOjthWeX7xaq2
GTOlDG/IoJOzOoJqicZ7sCRqeZRu3j7PbbFiwJGmEq+pjqLlnWKBwG4wyVixjEI=
=jykO
-----END PGP SIGNATURE-----
Holger Levsen
Nov 5, 2016, 11:22:20 AM11/5/16
to qubes-users
On Sat, Nov 05, 2016 at 03:58:21PM +0100, Marek Marczykowski-Górecki wrote:
> Oh, indeed qubes-release were only in testing repository for "fc20" base
> distribution - which is the case in the first stage of in-place upgrade.
> Fixed.
so that means the docs are correct now?
> Oh, indeed qubes-release were only in testing repository for "fc20" base
> distribution - which is the case in the first stage of in-place upgrade.
> Fixed.
> Check status of qubes-qmemman service.
> > ah. so I guess I should send a patch for qubes-doc tomorrow… (gn8 ;)
> That would be great ;)
--
cheers,
Holger
Marek Marczykowski-Górecki
Nov 5, 2016, 11:38:17 AM11/5/16
to qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hash: SHA256
On Sat, Nov 05, 2016 at 03:22:15PM +0000, Holger Levsen wrote:
> On Sat, Nov 05, 2016 at 03:58:21PM +0100, Marek Marczykowski-Górecki wrote:
> > Oh, indeed qubes-release were only in testing repository for "fc20" base
> > distribution - which is the case in the first stage of in-place upgrade.
> > Fixed.
>
> so that means the docs are correct now?
Yes.
> On Sat, Nov 05, 2016 at 03:58:21PM +0100, Marek Marczykowski-Górecki wrote:
> > Oh, indeed qubes-release were only in testing repository for "fc20" base
> > distribution - which is the case in the first stage of in-place upgrade.
> > Fixed.
>
> so that means the docs are correct now?
> > Check status of qubes-qmemman service.
>
> not running & couldnt start it…
> > > ah. so I guess I should send a patch for qubes-doc tomorrow… (gn8 ;)
> > That would be great ;)
>
> ok, will do!
>
>
- --
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
iQEcBAEBCAAGBQJYHfzmAAoJENuP0xzK19csA2UH/2719ReG5U/m0fZOLMaSncxe
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
qilZOs4WF2v45H8tgnjInOgu5bgItv0fxN4NenCg+YrBG9poka+4Jdm9GxGQYkG7
GnzC1VJJWWionMwtQF6dS3E5d/McgaTzTQ4Bq2xQ3+OT30kEL7OZkW3e/ZdbXP4G
A2ZyA5wbvzDslcLkXOsUyBbfhuupLzX2Ixzwt8VAUl+ux1y8enG75lxqlVRo2W5j
FhzjIWLA28ULM1YzTuTT5bEwVA+9vF3C58t0OOU73sFk1F+RSNNGeEUynjaK+jZi
1Z5akPjPKbURgaymyacnbG3lQjvynNgsivJ9YSUNWgif5McRHVRbGyOAnvxvui0=
=4n2W
-----END PGP SIGNATURE-----
Marek Marczykowski-Górecki
Nov 5, 2016, 12:20:36 PM11/5/16
to Holger Levsen, qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Sat, Nov 05, 2016 at 04:13:19PM +0000, Holger Levsen wrote:
Hash: SHA256
> On Sat, Nov 05, 2016 at 04:38:11PM +0100, Marek Marczykowski-Górecki wrote:
> > > so that means the docs are correct now?
> > Yes.
>
> cool!
> > > so that means the docs are correct now?
> > Yes.
>
>
> > Did you get any error on its startup (and shown by systemctl status)?
>
> see attached screenshot :)
> > Did you get any error on its startup (and shown by systemctl status)?
>
Looks like it can't connect to syslog/journald. Does /dev/log exist?
Does anyone listen on it (netstat -nlpx)? On my system it's a symlink to
/run/systemd/journal/dev-log.
- --
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
ueWAk69BKHqgRQW+RCQXCjS43t8dtKkTgQ2/b4Vz0jjw5HTmsImQVapgHrw5Dt+a
eMXtWpXazoZOmLNblDuMSIVAi2VpAvWYvteRYMGfMfVL7akU6nKjMa5tq4nVcJbo
DGFs8MxACx8B+oCaJSYsH8oMvPlLyjONX4HYZ36jl1OZ2AA1QFUmLMiqNgCsNcEK
LwXKWM0G3oq4rLk3pei/fGfc0CDFX5bbTBTP6zdYlw9hNT933GKjkBiYY0ikgL5o
ifWWKmUx5JCwmb1OTBESzUiEGZPGhOWsj/ntqvCFbqcB56NJXalByUy8rWVhlqg=
=ZRsV
-----END PGP SIGNATURE-----
Holger Levsen
Nov 5, 2016, 12:26:59 PM11/5/16
to qubes-users
On Sat, Nov 05, 2016 at 05:20:32PM +0100, Marek Marczykowski-Górecki
wrote:
> Does anyone listen on it (netstat -nlpx)?
netstat is not installed.
>On my system it's a symlink to
> /run/systemd/journal/dev-log.
/run/systemd/journal/dev-log is also shown in purple. nothing else in
/etc, /dev nor /root is shown in purple?!
perms of both directories are
srw-rw-rw- owned by root:root
--
cheers,
Holger
wrote:
> Looks like it can't connect to syslog/journald. Does /dev/log exist?
yes, but it's color is purple?!
> Does anyone listen on it (netstat -nlpx)?
>On my system it's a symlink to
> /run/systemd/journal/dev-log.
/etc, /dev nor /root is shown in purple?!
perms of both directories are
srw-rw-rw- owned by root:root
--
cheers,
Holger
Marek Marczykowski-Górecki
Nov 5, 2016, 12:45:09 PM11/5/16
to qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hash: SHA256
On Sat, Nov 05, 2016 at 04:26:55PM +0000, Holger Levsen wrote:
> On Sat, Nov 05, 2016 at 05:20:32PM +0100, Marek Marczykowski-Górecki
> wrote:
> > Looks like it can't connect to syslog/journald. Does /dev/log exist?
>
> yes, but it's color is purple?!
Should be - it's a socket.
> On Sat, Nov 05, 2016 at 05:20:32PM +0100, Marek Marczykowski-Górecki
> wrote:
> > Looks like it can't connect to syslog/journald. Does /dev/log exist?
>
> yes, but it's color is purple?!
> >On my system it's a symlink to
> > /run/systemd/journal/dev-log.
>
> /run/systemd/journal/dev-log is also shown in purple. nothing else in
> /etc, /dev nor /root is shown in purple?!
/run/systemd/journal/dev-log. Maybe this is the part that was
interrupted.
- --
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
ZMGakw/8K0/BG7r2QO04G3QJ8xq8+fdnP0DC4HHcOjjOiW8eiuFonq7wE9Y48elh
EJxIyxt9qRhAZj9+R6+8g6fh82NXVpE75CzM40vEGjZIhK10WqgzTYFldQYWPU3f
PjKKcHMKuaw+oWXL0HBUVvwprvJnRczWgk09n+uiRpFc+wWsSyzEHWah0g3Gu3DF
1PRkqFSg2/9bO6JaB6316hVl/vDsZZsyYho0grgBDYMXaoCK9Exk4ypXKbojpo8x
J4AUhtkNW8qH9gxaTw8ulcrJkrCzElrd2N119SSZYaT8E0NsRuJmT1M0m7wqKBI=
=P+8P
-----END PGP SIGNATURE-----
Holger Levsen
Nov 5, 2016, 1:10:49 PM11/5/16
to qubes-users
On Sat, Nov 05, 2016 at 05:45:05PM +0100, Marek Marczykowski-Górecki wrote:
> > yes, but it's color is purple?!
> Should be - it's a socket.
ah
> > yes, but it's color is purple?!
> Should be - it's a socket.
> Ok, lets try to replace /dev/log with a symlink to
> /run/systemd/journal/dev-log. Maybe this is the part that was
> interrupted.
also didnt help :(
I guess I'll just go with a reinstall…
Thanks for your help so far!
--
cheers,
Holger
Holger Levsen
Nov 19, 2016, 9:34:01 AM11/19/16
to qubes-users
On Sat, Nov 05, 2016 at 03:58:21PM +0100, Marek Marczykowski-Górecki wrote:
> > > > p.s./btw: https://www.qubes-os.org/doc/upgrade-to-r3.1/ advices one to
> > > > install qubes-mgmt-salt-admin-tools but this package does not exist?!
> > > That's interesting, this step should be in 3.1->3.2 instruction...
> > ah. so I guess I should send a patch for qubes-doc tomorrow… (gn8 ;)
> That would be great ;)
just two weeks later instead of tomorrow, but here is
> > > > install qubes-mgmt-salt-admin-tools but this package does not exist?!
> > > That's interesting, this step should be in 3.1->3.2 instruction...
> > ah. so I guess I should send a patch for qubes-doc tomorrow… (gn8 ;)
> That would be great ;)
https://github.com/QubesOS/qubes-doc/pull/223
granted, it's a lame commit, but every journey starts with small steps…
:)
--
cheers,
Holger
Reply all
Reply to author
Forward
0 new messages