Re: [midgard-user] OffTopic: Installation on Debian Potato

[Torben Nehmer, Linksystem Muenchen GmbH]

Hi.

On Wed, 11 Jul 2001, Emiliano wrote:
> > Potato works fine as a server. The few packages that are missing are
> > easily either selfcompiled or used from testing.
>
> I want something that upgrades easily and smoothly, so I'll only
> deviate from packages where there's absolutely no alternative (Midgard
> comes to mind :| ). Specifically, apt-get update/dist-upgrade must remain
> to work.

Right of course. On my server it is exactly Midgard and expat, which
doesn't come out of the archive (apart from Qmail...) I can live with
that, to be honest.

What we could do would be providing our own small Debian archive where we
provide our packages. I could imagine finding some maintainers for the
different debian distibutions that keep our Midgard packages up to date
there. This way our Debian users just have to add another line to their.
apt sources.


> > The upgrade of my system from potato to sid went fine (more or less). I
> > had some problems with broken dependencies, but after a littlebit fixing
> > and testing (a boot floppy can be _very_ valuable there) it worked without
> > problems.
>
> I'd expect (and got) dependency problems while going from potato to sid
> on my workstation. I hadn't expected them at all for stable -> testing. I
> installed stable (from CD), aded the testing sources.list lines, apt-get
> update, apt-get dist-upgrade, and spent about 4 hours with dpkg -r,
> dpkg -i --force-conflicts and (apt-get -f install, dist-upgrade) x way-too-much
> to get it back in order. It works now, but as far as the upgrade procedure
> is concerned, it might easily have looked like a -> Sid upgrade to a
> bystander. Frustrating, as I had just been exhalting the smooth Debian
> upgrade procedure to the victim^[bCowner.

It wasn't that bad here. Mainly I had two package in the unstable tree
that were really broken. One messed up with the dependency tree, which I
could fix by removing the Package (with apt-get) and some of its
dependencies. The other one was lilo ... which "forgot" to cleanly update
my boot sector :-/.

About testing, testing is still not considered stable. Although they've
begun code-freeze, that doesn't mean that the Distribution will fit in
niceley yet.

Besides: Imagine you'd have to update the same system on an RPM basis ...
I won't have any problem checking some not 100% correct dependencies if
99% of the update runs smoothly.


Torben

-- 
Linksystem Muenchen GmbH                          [EMAIL PROTECTED]
Schloerstrasse 10                           http://www.link-m.de
80634 Muenchen                              Tel. 089 / 890 518-0
We make the Net work.                       Fax 089 / 890 518-77


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]