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 [email protected]. To post to this group, send email to [email protected]. 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/optout.
