Bug#471805: openoffice.org-core: spurious conflicts against older openoffice.org components
tag 471805 - wontfix
severity 471805 minor
retitle 471805 openoffice.org-core: spurious conflicts against older openoffice.org components
thanks
Hi,
Sven Joachim wrote:
> On 2008-03-20 11:11 +0100, Rene Engelhard wrote:
>
> > Sven Joachim wrote:
> >> In the last few updates of openoffice.org I noticed that
> >> openoffice.org-core was always temporarily removed, it seems because it
> >
> > Because I don't upload i386 and the i386 buildd sometimes takes time...
>
> I don't quite understand that. Both -core and -calc are architecture
> dependent, after all. And all packages were upgraded in that aptitude
You forgot that those binary-arch things conflict against the old
-common...
> run.
So there's no problem, is there?`(Except that apt *temporarily* removes
a package)
> > * debian/control.in:
> > - fix logic error, we of course should conflict against old
> > openoffice.org-calcs in the new common, not the other way around
> > (really closes: #464544).
> > Go safe for the future; make -common Conflicts: against all the modules
> > (<< ${base-version})
> >
> > Read the bug to see what too lax depends can cause....
>
> I've read it, but it does not really seem related, it is about -common,
> not -core. And the removals of -core predate this change, just run
See above.
> > Which is normal modus operandi of apt. Nothing to worry about.
>
> I certainly won't lose sleep over that, but is generally safer to upgrade
> packages rather than remove and reinstall them. In the former case dpkg
> can roll back the upgrade in case something goes wrong during unpacking,
> in the latter you are left with a broken package.
I am not the author of apt/dpkg.
> > [1] Because if you have the new -core, you also have the new -calc, if
> > not, you have the old versions there.
>
> This is perfectly achieved by the versioned depends -calc has on -core.
> The additional conflicts of -core on -calc is redundant.
Ah, that was your goal to point out...
> See also bug #409411 for a similar instance in other packages.
I see. Although still, this is a working upgrade patch, the temporary
rremoval does not do harm.
Will have a look again...
Regards,
Rene
Reply to: