All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sven Köhler" <skoehler@upb.de>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] bootstrap stage1 with python2.2
Date: Sun, 29 Feb 2004 15:03:08 +0100	[thread overview]
Message-ID: <c1srf3$vpe$1@sea.gmane.org> (raw)

Hi,

i don't want to report a bug or something like that before i discussed 
it here, but if you bootstrap the old release-stage1 from 20030910, 
python 2.3 will be installed, but python 2.2 won't be uninstalled, but 
python 2.2 isn't listed to be installed. (qpkg -I |grep python only 
shows python2.3, but not python2.2)

bootstrap.sh should somehow upgrade python to the current version, but i 
cannot imagine how that should work. python2.2 cannot be unmerged (since 
qpkg -I doesn't list it), and python2.3 has a lot of dependencies.

I wonder if there are more files like /usr/bin/python2.2/* that don't 
belong to any package listed by "qpkg -I". These files could be recorded 
in the database as a package called "stage1" which can be unmerged after 
the "emerge system".

What do you think?

Thx
   Sven



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

             reply	other threads:[~2004-02-29 14:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-29 14:03 Sven Köhler [this message]
2004-02-29 16:24 ` [uml-devel] Re: bootstrap stage1 with python2.2 Sven Köhler

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='c1srf3$vpe$1@sea.gmane.org' \
    --to=skoehler@upb.de \
    --cc=user-mode-linux-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.