public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Divick Kishore <divick.kishore@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: kvm troubles
Date: Sat, 26 Dec 2009 00:20:36 +0300	[thread overview]
Message-ID: <4B352CA4.5070308@msgid.tls.msk.ru> (raw)
In-Reply-To: <4B352655.6040309@msgid.tls.msk.ru>

Michael Tokarev ?????:
> Divick Kishore wrote:
>>> Also I am not sure that as such packages __should__ not be downloaded
>>> from any unknown site but only from trusted debian mirrors. Am I not
>>> open to any security issues in case I install the package downloaded
>>> from www.corpit.ru?
>> Or in fact downloaded from any other site pointed out by someone on
>> the mailing list. Why should / should not trust packages downloaded
>> from non standard debian mirrors?
> 
> Well, it's your choice really.
> 
> I maintained kvm (and later qemu-kvm) package for debian for a long
> time because the one in debian is too old to be usable.  It was a long
> way before I was able to communicate with debian maintainer, and now
> I co-maintain it -- there is qemu-kvm-0.11.1 in -testing now, but it
> depends on many other libraries in -testing.  For over a year kvm in
> debian was unusable - so much for trusted/standard mirrors.

By the way, it's no more risk when you grab any other software
and run it on your machines.  Like for example kvm from official
sources (and compile it) -- did you check for trojan horses and
the like in the source?

> As of the error you've got -- you're the first to report it, apparently
> no one else noticed that it depends on a single package that is not in
> lenny -- it's libgnutls26.  You can install this library from -testing
> or wait till I re-upload new version to www.corpit.ru.

Uploaded, still 0.11.0 - I have no time right now to update to 0.11.1
or 0.12 (and the latter is quite unstable anyway).  But 0.11.0 is a
good version.

Grab
qemu-kvm_0.11.0+dfsg-1tls2_amd64.deb or
qemu-kvm_0.11.0+dfsg-1tls2_i386.deb
depending on your arch.

/mjt


  reply	other threads:[~2009-12-25 21:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-24 11:03 kvm troubles Divick Kishore
2009-12-24 11:27 ` Thomas Mueller
2009-12-24 11:53 ` Avi Kivity
     [not found] ` <4B335045.3040904@chaschperli.ch>
     [not found]   ` <9232def20912250309s64a111cex5d575783d009ced4@mail.gmail.com>
2009-12-25 19:41     ` Divick Kishore
     [not found]     ` <4B349FCD.4020102@chaschperli.ch>
2009-12-25 19:48       ` Divick Kishore
2009-12-25 20:18         ` Michael Tokarev
2009-12-25 20:40           ` Divick Kishore
2009-12-25 20:42             ` Divick Kishore
2009-12-25 20:53               ` Michael Tokarev
2009-12-25 21:20                 ` Michael Tokarev [this message]
2009-12-26  4:23                   ` Divick Kishore

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B352CA4.5070308@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=divick.kishore@gmail.com \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox