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

Bug#941793: marked as done (nmu: libimobiledevice_1.2.1~git20181030.92c5462-1)

Your message dated Thu, 6 Feb 2020 11:45:03 +0100
with message-id <d1ddae7e-e600-d04d-489e-63cf59fd414c@debian.org>
and subject line Re: Bug#941793: nmu: libimobiledevice_1.2.1~git20181030.92c5462-1
has caused the Debian Bug report #941793,
regarding nmu: libimobiledevice_1.2.1~git20181030.92c5462-1
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.)


-- 
941793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941793
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: binnmu

nmu libimobiledevice_1.2.1~git20181030.92c5462-1 . ANY . unstable . -m "rebuild against newer libusbmuxd"

Hi,

I recently updated the idevices stack in Debian (libplist, libusbmuxd,
libimobiledevice etc.). Upstream doesn't release packages anymore, so I
do snapshots myselfs, and missed an interface break in libusbmuxd:

https://github.com/libimobiledevice/libusbmuxd/commit/f5a7387a54ae08c9cd1d83a415393e0e909dc6e6#diff-038b1c435b1baca0fc7faaf5e375f401L37

This bug is causing crashes in applications linked against
libimobiledevice (like #941703).

I've uploaded an updated libimobiledevice built against the updated
libusbmuxd, but it's currently sitting in NEW. While a proper solution
should be found long term (and I'll ask upstream about that), for now
would it be possible to rebuild libimobiledevice against the newer
libusbmuxd?

Thanks in advance,
-- 
Yves-Alexis

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (450, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

--- End Message ---
--- Begin Message --- 
Hi Yves-Alexis,

On Fri, 22 Nov 2019 17:34:02 +0100 Yves-Alexis Perez <corsac@debian.org>
wrote:
> On Thu, 2019-10-24 at 11:44 +0200, Emilio Pozuelo Monfort wrote:
>> Just go ahead with the package rename / soname bump, no need to revert it and
>> then do the transition in this case, given the rdeps are going to build fine so
>> there will be little disruption.
> 
> 
> So, upstream went ahead and updated the soname on libusbmuxd (from libusbmuxd4
> to libusbmuxd6) and tagged a new release (2.0.0, along with libplist 2.1.0).
> 
> I'll upload soon, likely this week-end, but NEW processing seems a bit stuck
> so I'm unsure when it'll reach unstable.

Sorry that this bug wasn't handled very nicely, but this all seems to be
settled now in unstable and testing. Hence, I'll close this bug.

Paul

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: