* Frank Lichtenheld [Sun, 03 Jul 2005 02:37:12 +0200]:
Hello all,
> On Sat, Jul 02, 2005 at 11:37:37PM +0300, Jarkko Suontausta wrote:
> > On Wednesday 08 June 2005 19:54, Itai Seggev wrote:
> > > On Tue, Jun 07, 2005 at 07:24:56PM +0200, Isaac Clerencia wrote:
> > > > On Tuesday, 7 June 2005 18:53, Itai Seggev wrote:
> > > Yes, you're right. It seems the problem was that kdm is only recommend
> > > by, and not depended on, by kdebase, so it wasn't upgraded with the
> > > rest of kdebase. Is there any particular reason for this behaviour? I
> > > would expect that if I installed kdebase, I would get all of it.
> > I second this and have been puzzled as to why kdebase doesn't depend on
> > kdm...
> > there is probably a (historical?) reason for that, but it might be
> > worthwhile
> > to reconsider adding that dependency...
Exactly for this:
> kdebase doesn't depend on kde because it works perfectly without it.
> I have kdebase installed here but I can live fine with my gdm...
> Recommends is really the right choice here and I would suggest to use
> a apt frontend that honors them.
Note, however, that the kdebase Recommends: kdm (>= ${Source-Version}).
I don't think our package management tools honour that at all, but
they could some day, and at least serves as documentation for users.
(The truth is that the experimental packages don't have the
recommendation versioned, but this was just unfortunate timing: it was
removed on May 30th, and reintroduced on Jun 9th after agreeing that
it was best to leave them. kdebase 3.4.1-1 was uploaded on May 31st.)
> The real question is why the kde packages don't conflict with earlier
> kdm versions if they don't work with them... (not that kde had too few
> conflicts, how about a little backwards compatibility anyway?)
This situation is mostly fixed in our SVN since Jun 9, but there has
not been another upload to experimental since then. .oO(Must implement
that svn post-commit hook that tags pending and attachs changelog
entry when closing a bug in SVN, like subversion (the pacakge) does.)
We tightened the kdm dependency on kdebase-bin, which was the one
causing problems. As now kdm Depends: kdebase-bin (= ${Source-Version),
kdm will necessarily get upgraded whenever kdebase is.
This, er, solves the problem after people upgrade to kdm 3.4.1. The
possibility of remaining with an un-upgraded 3.3.2 remains, but I
haven't decided what to do with that yet. Perhaps a one-time versioned
conflicts (kdebase-bin Conflicts: kdm (<< 4:3.4.1-2), what do you
think, Christopher?).
Cheers,
--
Adeodato Simó
EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621
A dream is an answer to a question that we don't know how to ask.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
