On 1/3/19 12:50 AM, unman wrote:
On Wed, Jan 02, 2019 at 05:08:50PM +0100, gone wrote:
On 1/1/19 10:19 PM, Chris Laprise wrote:
On 01/01/2019 02:37 PM, gone wrote:
Hello, 1st of all, I want to thank all the developers and supporters
for that great stuff called Qubes OS. My first question here after
some hard time of setting up version 4.0, updating it step by step
and studying is the following:
I have a debian-9 template running and for some application to get
installed on it I need Python with Version >= 3.6 as a prerequisite.
Since the preinstalled versions in debian-9 are 2.7 and 3.5 I
attempted to install version 3.6.4 from source as described at
https://www.rosehosting.com/blog/how-to-install-python-3-6-4-on-debian-9/
in order not to run into problems with incompatibilities when
switching to another repo.
Installing the build tools with "sudo apt-get install -y ..." worked
fine but the next step, downloading the source file, with
"wget https://www.python.org/ftp/python/3.6.4/Python-3.6.4.tgz";
brings "... failed: Temporary failure in name resolution.
wget: unable to resolve host address ‘www.python.org’ "
As I am neither an expert nor an experienced from-source-installer I
need some help and hope to get it here. Thanks very much in advance
and all the best for 2019.
Installing from Debian testing is much easier and it has Python 3.7.
Just set the default release as in the following link, then add a line
for "testing" in your /etc/apt/sources.list (and then 'apt update'):
https://www.debian.org/doc/manuals/apt-howto/ch-apt-get.en.html#s-default-version
Thanks Chris for the explanation. Yes, it may be easier to change to the
testing repo, but in general I would like to stay on the stable path with
that template. Switching to the testing repo and 'apt update' would probably
cause trouble with other software running smoothly so far. Or can I use that
only for python install and then fall back?
If you follow the instructions that Chris linked to you should be fine.
apt update just updates the list of available packages. It doesn't in
itself do anything more.
By setting the default release to stable, you ensure that you wont be
"accidentally" installing stuff from testing. That will only happen if
you explicitly specify the testing repo:
apt-get -t testing install foo
I'd strongly recommend aptitude, which does an excellent job of dealing
with packages from different releases, and allows you to explicilt
choose the version you want. It also lets you review in detail what the
consequnces will be , so you are always able to roll back.
And, of course, with Qubes it's trivial to clone the template, try out
your proposed update from testing, and make sure that everything works
fine before you commit your precious qubes to use the new template.
Thanks unman and Chris. Gonna try that at the next opportunity.
--
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/95de63d6-b43e-346a-e2df-1e2a9a5a15fa%40posteo.net.
For more options, visit https://groups.google.com/d/optout.
