Hi,
> > Since the libgdchart-gd2 maintainer hasn't responded to your request
> > for more information, let me fill in my best guesses. I think there
> > used to be a package literally called "libgd2-dev", which has since
> > been dropped from the archive; if true, this could explain how the
> > package was able to build before. It appears libgdchart-gd2 replaced
> > the libgd2-dev output, whatever it was, with "libgd2-noxpm-dev |
> > libgd2-xpm-dev" in both -dev packages, so that's probably a
> > reasonable dependency string to use.
>
> Thanks, Daniel, for clarifying this.
>
> And sorry for being so unresponsive. I have been busy with real life,
> and with other issues regarding yaird and linux-26.
>
>
> I agree with Daniel that binary dependency resolving to "libgd2-dev"
> should be adjusted to use "libgd2-noxpm-dev | libgd2-xpm-dev" instead.
Sorry for a slow response, I just noticed.
Thanks for the feedback.
To me, it might just be easier if libgd2-noxpm-dev, libgd2-xpm-dev
had both Provides: and Conflicts: against libgd2-dev.
There is only Conflicts:; is there any reason there is no Provides?
regards,
junichi
--
[EMAIL PROTECTED],netfort.gr.jp} Debian Project
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
