Bug#956467: marked as done (transition: qhull)

["Debian Bug Tracking System" <owner@bugs.debian.org>]

Your message dated Sun, 24 May 2020 10:59:44 +0200
with message-id <20200524085944.GA2270942@ramacher.at>
and subject line Re: Bug#956467: transition: qhull
has caused the Debian Bug report #956467,
regarding transition: qhull
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
956467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956467
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

--- Begin Message ---

• To: submit@bugs.debian.org
• Subject: transition: qhull
• From: Timo Röhling <timo@gaussglocke.de>
• Date: Sat, 11 Apr 2020 19:23:56 +0200
• Message-id: <a289476c-10ef-0ecb-8ec0-b982fb3b7602@gaussglocke.de>

Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition
Control: block -1 by 956460 956461 956462

Dear release team,

I would like to transition qhull 2019.1 after some ABI breaking changes
in upstream. API seems mostly unaffected, except for a deprecated
include path that has been removed. This affects three packages (see below).

The ben tracker looks good to me:
https://release.debian.org/transitions/html/auto-qhull.html

I rebuilt all reverse dependencies (on amd64):

3depict: FTBFS (tracked in bug #956460)
gdal: OK
getfem++: OK
meshlab: OK
octave: OK
pcl: OK
plplot: OK
pymca: FTBFS (tracked in #956462)
ros-geometric-shapes: OK
saga: FTBFS (tracked in #956461)

Thank you,
Timo

--- End Message ---

--- Begin Message ---

• To: Timo Röhling <timo@gaussglocke.de>, 956467-done@bugs.debian.org
• Subject: Re: Bug#956467: transition: qhull
• From: Sebastian Ramacher <sramacher@debian.org>
• Date: Sun, 24 May 2020 10:59:44 +0200
• Message-id: <20200524085944.GA2270942@ramacher.at>
• In-reply-to: <85886ced-68bb-4f40-001b-b4ff5028e326@gaussglocke.de>
• References: <a289476c-10ef-0ecb-8ec0-b982fb3b7602@gaussglocke.de> <fc8c5170-8307-19bc-ce43-3ff736134267@debian.org> <a289476c-10ef-0ecb-8ec0-b982fb3b7602@gaussglocke.de> <85886ced-68bb-4f40-001b-b4ff5028e326@gaussglocke.de>

On 2020-04-29 10:10:45 +0200, Timo Röhling wrote:
> On 29.04.20 10:02, Emilio Pozuelo Monfort wrote:
> > If upstream broke the ABI
> > without bumping the SONAME that's probably the correct solution, but it'd be
> > good if you can convince them to bump it in the next version
> I agree, and I did submit a bugreport [1], but no reply so far.
> 
> > In any case you can go ahead with this.
> Thanks.

Everything migrated, closing.

Cheers
-- 
Sebastian Ramacher

Attachment: signature.asc
Description: PGP signature

--- End Message ---