Re: howto find out why dist-upgrade wants to remove a package?
- To: email@example.com
- Subject: Re: howto find out why dist-upgrade wants to remove a package?
- From: Daniel Burrows <firstname.lastname@example.org>
- Date: Mon, 14 Jul 2008 20:08:32 -0700
- Message-id: <20080715030832.GA29563@alpaca>
- In-reply-to: <email@example.com>
- References: <firstname.lastname@example.org> <20080713213615.GE10272@think.homelan> <20080714022238.GA16859@alpaca> <email@example.com> <20080714140638.GA17848@alpaca> <firstname.lastname@example.org> <20080714152020.GC4366@osamu.debian.net> <email@example.com>
On Mon, Jul 14, 2008 at 11:50:39AM -0500, Hugo Vanwoerkom <firstname.lastname@example.org> was heard to say:
> Osamu Aoki wrote:
>> On Mon, Jul 14, 2008 at 09:45:04AM -0500, Hugo Vanwoerkom wrote:
>>> It may be obsolete, but its replacement causes problems for that
>>> plugin, which is no longer supported BTW.
>>> In the meanwhile aptitude keeps insisting on removing that package no
>>> matter what I pin preferences to :-(
>> If this is your objective, pin is wrong long term solution if you want
>> to run newer distribution. You should create chroot and run old
>> distribution within it just for mysql.
> Very complicated to run mysql-server, apache and WordPress in chroot and
> the rest, including the rest of X, not.
You probably only need to run the bits that need php4-mysql in the
chroot. I think that would be WordPress and maybe apache (unless you
can tell apache to chroot before spawning the php module). MySQL
connects over a standard network socket, so WordPress can access it
regardless of whether it's chrooted or not.
Disclaimer: I have never run WordPress on my computer and I know very
little about PHP or MySQL.