Bug#200264: Splitting texdoctk? (was: Bug#200264: tetex-bin upgrade fails: conflict with texdoctk)
On 15.04.04 Frank Küster (frank@debian.org) wrote:
> Hilmar Preusse <hille42@web.de> wrote:
Hi all,
> > We can do the first step into that direction like I suggested in
> > #190721. The patch there² moves a little bit further in direction of
> > #223734 and #223728 than it is actually desired.
>
> Oh, this is a little too much fiddling with pointers for me, I'm not
> sure I get what you want to say. I'll try to say it with my words:
>
> - The splitting as suggested in 223728 (standing for both twins) is
> not desired, at least not currently, perhaps after sarge is
> released.
>
Definitely!
> - Your patch in 190721 would fix our texdoctk problem
>
My patch in 190721 goes a little bit further into the huge split[TM],
than it is actually desirable.
Actually I propose only to split off
/etc/texdoctk/{texdocrc,texdoctk.dat} from tetex-extra and put it
into a separate package. tetex-bin will depend on it.
Problem: in woody /etc/texdoctk/* are conffiles. A Conflicts-field in
tetex-bin will only remove that package, not purge it -- correct?
What will happen, if that "to be created" package will try to
overwrite them?
Further: assume, that tetex-bin conflicts with texdoctk and depends
on that "to be created" package. What will happen first: removal of
texdoctk or install of that package?
> - You would prefer to not do so much splitting as this patch would
> give, because of the same reasons that make the 223728-type
> splitting undesirable.
>
Exactly.
> > If we split only the config-files off tetex-extra we shouldn't
> > break anything.
>
> And this is a suggestion as an alternative to your patch: We could
> create texdoctk-conffiles but leave the rest in tetex-bin, which
> would depend on texdoctk-conffiles and Conflict/Provide/Replace
> texdoctk, right?
>
This is what my patch suggests, except that it splits off texdoctk
from tetex-bin, which I wouldn't do in the moment.
> The last option (only texdoctk-conffiles) looks good for me to
> resolve this bug for sarge. Have you checked whether the patches
> still can be applied somehow?
>
No. Before I will do so, I would like to hear other opinions, if
there could appear other technical issues (see above) etc.
Another possibility was discussed in #190721: put these files in
tetex-base and we're done. That will solve #190721. After that we can
swap over Conflicts: texdoctk etc. to tetex-bin, I just don't know,
if that will solve our upgrade-problems (#200264).
[combination of tetex-bin, tetex-base]
>
> Why not combine them into one tetex_$version.orig.tar.gz and
> creating the same binary packages from there?
>
That will help to solve problems like #190721. Do they occur that
often? On the other hand: It may keep some things more simple.
H.
--
sigmentation fault
Reply to: