Hi,
> > * debian/control{.sdk}.in, debian/rules, debian/libreoffice-dev-doc.links:
> > - stop moving the SDK docs into libreoffice-devs /usr/share/doc (and
> > move
> > the stuff installed into /usr/share/doc/libreoffice/sdk in
> > libreoffice-dev
> > to /usr/share/doc/libreoffice-dev, too) and conflict against
> > libreoffice-dev / libreoffice-dev-doc (<= 1:5.0.3~rc1-2) where needed
> > (closes: #803272, #803306)
>
> Conflicts + Replaces (haven't checked) won't fix the symlink to
> directory transition on upgrades.
True, but if you checked the scripts there *IS* a dir_to_symlink. Done
by with a previous bug before.
See
libreoffice (1:5.0.3~rc1-2) unstable; urgency=medium
* debian/*.maintscript: add loads of dir_to_symlink calls to packages
moving dir->symlink due to dh_installdocs --link-doc (closes: #801753)
* debian/control.in:
- make -gnome only recommend -gtk. it doesn't need -gtks libs
-- Rene Engelhard <r...@debian.org> Mon, 19 Oct 2015 00:01:06 +0200
Bug by you, I guess.
Just that this didn't work as - as you said - stuff installed "over the symlink"
then is still there.
> > Yes, I know, but a strtech->sid upgrade is a problem here, especially when
> > you have already -dev or -dev-doc installed.
> >
> > A stable->stretch and stable->sid upgrade works. And strech->sid is
> > development->dxevelopment, so breakage can happen...
>
> Not supporting stretch-> sid upgrades means not supporting a clean
> upgrade path within stetch once the new package migrated.
> Is this really what you want?
Did you read the reports above?
I don't see a proper way out of this. As said, the dir_to_symlink calls
_are_ there. If you can tell me a way which works for both cases, please
tell me. (#debian-devel wasn't able to, instead of recommending to move
the files and doing the Conflicts/Replaces for the order.)
And yes, this is a development->development upgrade _and_ for libreoffice-dev
which "normal" users won't have installed that often (as they don't develop
for LibreOffice).
So yes, I can live with that.
Regards,
Rene
