[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#795125: marked as done (transition: libassimp3 -> libassimp3v5)

Your message dated Sun, 6 Sep 2015 10:45:18 +0200
with message-id <20150906084518.GA24479@betterave.cristau.org>
and subject line Re: Bug#790980: assimp: library transition to libassimp3v5
has caused the Debian Bug report #790980,
regarding transition: libassimp3 -> libassimp3v5
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.)


-- 
790980: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790980
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition

Due to the gcc-5 transition, the "libassimp3" package from "assimp" has changed
exported symbols and has been renamed to "libassimp3v5".
The SONAME has *not* changed.

I have uploaded "assimp_3.1.1~dfsg-4" to "experimental".
So far the package has built on all architectures already in testing, except for
armel/armhf/mips/mipsel which are still waiting for a buildd to be assigned.
I'm sure that those builds will succeed as well :-)

There are currently 2 packages in Debian that have listed libassimp-dev as
build-dependency, so they need to be rebuilt:
- mrpt
- doomsday

I have built both reverse-dependencies, with the following result:

- "doomsday" builds fine.

- "mrpt" FTBFS with the following error:
    ../../lib/libmrpt-vision.so.1.3.1: undefined reference to `cv::Algorithm::_create(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
this looks very much like an unrelated issue (hinting that libopencv needs to
transition to libopencv*v5 as well).
a quick "rgrep -i assimp ." indicates, that assimp is used in the following
modules of mrpt:
 - apps/SceneViewer3D
 - libs/maps
 - libs/nav
 - libs/opengl
 - libs/slam
i've build all of them manually, and they built fine.
so i think that 'mrpt' is also ready for the libassimp3v5 transition (though it
is blocked by a potential libopencv*v4 transition)


In terms of 'ben' lingo, I think that the transition has the following parameters:

title = "assimp";
is_affected = .depends ~ "libassimp3" | .depends ~ "libassimp3v5";
is_good = .depends ~ "libassimp3v5";
is_bad = .depends ~ "libassimp3";

Please schedule binNMUs for the above mentioned packages on all architectures.

gfmards
IOhannes


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message --- 
On Mon, Aug 10, 2015 at 20:52:45 +0100, Simon McVittie wrote:

> user release.debian.org@packages.debian.org
> usertag 790980 + transition
> block 790980 by 790756
> reassign 790980 release.debian.org
> retitle 790980 assimp: library transition to libassimp3v5
> thanks
> 
> Reopening the bug as a transition tracker and reassigning, as requested
> in the original bug report.
> 
> Release team: the assimp maintainer has added the v5 suffix in experimental
> only. Please Cc the package maintainer when you ask for an upload to unstable.
> 
libassimp3 is no longer in testing, closing.

Cheers,
Julien

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: