Bug#815036: marked as done (transition: msgpack-c)
Your message dated Tue, 11 Oct 2016 00:16:36 +0200
with message-id <email@example.com>
and subject line Re: Bug#815036: transition: msgpack-c
has caused the Debian Bug report #815036,
regarding transition: msgpack-c
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 firstname.lastname@example.org
Debian Bug Tracking System
Contact email@example.com with problems
--- Begin Message ---
- To: Debian Bug Tracking System <firstname.lastname@example.org>
- Subject: transition: msgpack-c
- From: James McCoy <email@example.com>
- Date: Wed, 17 Feb 2016 23:46:53 -0500
- Message-id: <firstname.lastname@example.org>
I'd like to start discussion of a msgpack-c (formerly msgpack)
msgpack-c 1.4.0-2 is in experimental and I'm ready to start trying to
get it into unstable & testing. I don't know of any outstanding issues
other than it tickling a possible G++6 bug, but there's a possible
workaround already being looked at upstream.
Although there isn't an ABI bump, the 1.4.0 implements the new version
of the msgpack format and has some related API changes. The old
libmsgpackc2 doesn't understand the new msgpack format, so packages
built against the new library won't run properly if they try to use some
of the newer types.
The libmsgpack3 packge is no longer relevant as the C++ interface is now
I've done some test rebuilds of the reverse depends and here's the
+ #811343 filed with patch
+ New upstream version is needed
+ Will file a bug for this
+ configure script expects the C++ library (libmsgpack) and therefore
+ Trivial patch to remove that expectation leads to a compile failure
due to mixing code with C and C++ linkage
+ No upstream activity in 5+ years
+ Debian maintainer MIA
+ This likely needs a newer version of libdata-messagepack-perl, which
hasn't been uploaded yet
+ Needs to be adapted to new msgpack-c API. I have some patches I can
send in that regard.
I'll update this as I file bugs against the FTBFS packages, but I wanted
to get on the radar and see what feedback the team had.
I'm not quite sure about the Ben file, but I think it should be
sufficient. From what I see, most current packages ended up getting
dependencies on libmsgpack3 so seeing them switch to libmsgpackc2 should
be good enough. I don't think enforcing a minimum version of the
libmsgpackc2 dependency is accurate, since that depends on what part of
the API is being used.
Although it's most likely that anything build depending on
libmsgpack-dev has *some* binary package that will get a dependency on
libmsgpackc2 >= 1.0.0, not necessarily all of their binary packages
will. For example, groonga's groonga-bin package has Depends
libmsgpackc2 (>= 0.5.1) after a rebuild but groonga-plugin-suggest gets
libmsgpackc2 (>= 1.0.0).
title = "msgpack-c";
is_affected = .build-depends ~ "libmsgpack-dev"
is_good = .depends ~ "libmsgpackc2";
is_bad = .depends ~ "libmsgpack3"
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64
Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
- To: James McCoy <email@example.com>
- Cc: firstname.lastname@example.org
- Subject: Re: Bug#815036: transition: msgpack-c
- From: Emilio Pozuelo Monfort <email@example.com>
- Date: Tue, 11 Oct 2016 00:16:36 +0200
- Message-id: <firstname.lastname@example.org>
- In-reply-to: <email@example.com>
- References: <56CB55F0.firstname.lastname@example.org> <20160225012802.GF23132@freya.jamessan.com> <email@example.com> <20160614221731.GD8766@freya.jamessan.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com>
On 25/09/16 14:12, Emilio Pozuelo Monfort wrote:
> On 25/09/16 13:59, James McCoy wrote:
>> On Sun, Sep 25, 2016 at 11:23:43AM +0200, Emilio Pozuelo Monfort wrote:
>>> On 24/09/16 22:52, James McCoy wrote:
>>>> On Sat, Sep 03, 2016 at 02:10:08PM -0400, James McCoy wrote:
>>>>> On Wed, Aug 31, 2016 at 05:01:33PM +0200, Emilio Pozuelo Monfort wrote:
>>>>>> Upload msgpack-c to unstable, then you bump the remaining bugs to RC.
>>>>> Done. The tmate maintainer is going to move the compatible version from
>>>>> experimental to unstable today.
>>>> It looks like everything's transitioned.
>>> Should src:msgpack be removed from the archive now? libmsgpack3 has no rdeps.
>> Yes, it should.
> Then please file an RM bug against ftp.debian.org
That happened. Closing.
--- End Message ---