From: Tupshin Harper <tupshin@tupshin.com>
To: doogie@brainfood.com, xen-devel@lists.sourceforge.net
Subject: Re: xen 2.0.x and debian
Date: Sat, 05 Feb 2005 22:54:04 -0800 [thread overview]
Message-ID: <4205BF0C.2030308@tupshin.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0502051829450.5424@gradall.private.brainfood.com>
Adam Heath wrote:
>
> Ok, I've uploaded to debian's experimental tree. This is to make certain it
> doesn't blow up when people install it(even tho I'm using it locally).
>
> The main problem with it is that it doesn't do upgrades from 1.2 at all.
I grabbed all of the 2.0.4-2 debs in that directory and tried to do a
dpkg --install *
I got:
dpkg: error processing xen_2.0.4-2_i386.deb (--install):
trying to overwrite `/usr/share/doc/xen/examples/xmexample1', which is
also in package xen-docs
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Works with force-overwrite, but I assume that shouldn't be necessary
-Tupshin
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
next prev parent reply other threads:[~2005-02-06 6:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-01 3:16 xen 2.0.x and debian Tom Hibbert
2005-02-02 14:47 ` Nuutti Kotivuori
2005-02-05 7:57 ` Adam Heath
2005-02-05 20:01 ` Adam Heath
2005-02-05 22:24 ` Mark Williamson
2005-02-06 0:31 ` Adam Heath
2005-02-06 6:34 ` Travis Newman
2005-02-06 7:11 ` Adam Heath
2005-02-06 8:09 ` Tupshin Harper
2005-02-06 8:11 ` Adam Heath
2005-02-06 10:31 ` Mark Williamson
2005-02-06 6:54 ` Tupshin Harper [this message]
2005-02-06 7:07 ` Adam Heath
-- strict thread matches above, loose matches on Subject: below --
2005-02-01 2:58 James Harper
2005-02-01 3:16 ` Travis Newman
2005-02-05 7:48 ` Adam Heath
2005-01-20 0:47 James Harper
2005-01-20 2:11 ` Adam Heath
2005-01-20 0:39 Adam Heath
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=4205BF0C.2030308@tupshin.com \
--to=tupshin@tupshin.com \
--cc=doogie@brainfood.com \
--cc=xen-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.