Greetings Sebastian,
Thank your for your message.
On Thu, Nov 10, 2022 at 11:04:54PM +0100, Sebastian Ramacher wrote:
> Control: tags -1 moreinfo
> Control: forwarded -1 https://release.debian.org/transitions/html/auto-qcustomplot.html
>
> Hi Filippo
>
> On 2022-11-06 15:29:32 +0100, Filippo Rusconi wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian.org@packages.debian.org
> > Usertags: transition
> > X-Debbugs-Cc: lopippo@debian.org, gladk@debian.org, debian-science-maintainers@lists.alioth.debian.org
> >
> > (please explain about the transition: impacted packages, reason, ...
> > for more info see: https://wiki.debian.org/Teams/ReleaseTeam/Transitions)
> >
> > Greetings,
> >
> > Fundamental reason: Qt5 and Qt6 are in the archive.
> >
> > I am requesting a transition from package libqcustomplot2.0 to
> > libqcustomplot2.1. Source package is qcustomplot. The change involves a change
> > in the library name itself, from libqcustomplot2.0 to both libQCustomPlot2.1 and
> > libQCustomPlotQt6.so.2.1.0 (see below).
> >
> > I have prepared the packaging in the following git repos branch:
> >
> > https://salsa.debian.org/science-team/qcustomplot/-/tree/qt5-and-qt6
[...]
> > For the libs under my control, the transition is already prepared and these
> > projects are going to be linking against the Qt6-built library, contrary to all
> > the other packages detailed below.
> >
> > For the other libs listed above, I have already checked that they would build if
> > some modifications were performed. I have already git branches ready for the
> > packages under git VCS. For the others (source deb), I have patches available.
> >
> > The modifications are lean: change -lqcustomplot to -lQCustomPlot for many and
> > also sometimes use the CMake-based configuration involving first
> > find_package(QCustomPlot) and second the QCustomPlot::QCustomPlot formalism for
> > the linker.
> >
> > That is: almost one- or two-liner patches.
>
> Could you please file bugs for those so that maintainers are aware?
Yes, I'll do that. I have already informed them individually of the process and
provided them with the relevant patch.