Re: KDE 3.3.1 for Sarge
* Riku Voipio [Mon, 22 Nov 2004 13:05:00 +0200]:
> On Mon, Nov 22, 2004 at 03:30:03PM +1000, Anthony Towns wrote:
> I agree. In this way, the kde packages have allways been broken. We
> have been so far reluctant to enforce all of kde being the same version,
> since it would seem make testing maigration even harder
and kde in sid uninstallable most of the time, as you pointed me out
in the past. unless one uses a intermediate repository (experimental
or alioth) and the upload to sid was done all at once when all was
ready (which would break builds too, since there is no afaik
intelligent dependency handling; currenty, uploads are made more or
less in buildd order).
> That is the cleanest idea so far. But we would still need to add
> something like:
> Package: kdebase
> Conflicts: kfoo ( << 3.3.0 ), kfoo2 ( << ...
> Provides: kde-api-13
> Since in sid (and sarge) kde packages do not depend on a kde-api virtual
> package. Adding lots of versioned Conflicts was something that was
> strongly discouraged by apt maintainers[1] and the policy...
for dependencies between same source packages, I'm advocating an exact
versioned dependency (= x.y.z-d) for arch:any -> arch:any and arch:all
-> arch:all dependencies, and a restricted one (>> x.y.z, << x.y.z+1)
for arch:any -> arch:all or arch:all -> arch:any dependencies.
I believe that these are less harmful than versioned conflicts, so one
could think of trying a similar approach for dependencies between
different source packages. that is, e.g., make kde-api a real dummy
package (since versioned provides are not possible) and make each kde
package depend on kde-api (>>x.y.z), kde-api (<< x.y.z+1).
but this is going (I guess) off-topic for -release, though I'd be very
pleased to have aj or any RM help us with the issue!
> > That's fine, and it's quite possibly not something you can think
> > through in time for sarge. But it's something you (KDE) guys need
> > to think through, not just blame on the testing scripts and ignore.
Anthony, I didn't mean to blame the testing scripts at all. I've been
quite conscious about the problem since I became involved, and some
discussion has happened in the kde team. still a long way to go,
though.
> If you and the Release maintainers believe, that this in issue that
> must be solved for kde3.3 to enter sarge (despite the fact that
> kde 3.2 is sarge suffers from the same problem), we sould
> probably need to reupload most kde packages, which on the other hand
> will not make it in the time for sarge :-/ Which is kinda demotivating,
> since almost every kde package is valid candinate at the moment..
now, that's really on-topic.
thanks,
--
Adeodato Simó
EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621
If you think nobody cares if you're alive, try missing a couple of car
payments.
-- Earl Wilson
Reply to: