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

Bug#910271: marked as done (transition: mbedtls)

Your message dated Tue, 9 Oct 2018 14:17:38 +0100
with message-id <45d1a8d5-e371-4a37-6556-c5004f3afdf7@debian.org>
and subject line Re: transition: mbedtls
has caused the Debian Bug report #910271,
regarding transition: mbedtls
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.)


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

Hi,

mbedTLS needs a transition because upstream bumped the SONAME of
libmbedtls in 2.13 due to some symbol changes. I have also changed the
SONAME of libmbedcrypto to realign it with upstream. Previously upstream
had bumped the SONAME for no reason, so I reverted that change. Since we
now need a transition anyway, it seems sensible to me to use upstream's
SONAME again.

The auto-mbedtls transition tracker looks correct. These packages need
binNMUing:
 bctoolbox
 bibledit
 charybdis
 dislocker
 dolphin-emu
 gatling
 julia
 libgit2
 lief
 mongrel2
 ncbi-blast+
 ncbi-vdb
 neko
 shadowsocks-libev
 sra-sdk

All the packages build fine in a test rebuild except for dolphin-emu
which FTBFS for unrelated reasons which I will fix soon (#910268).

sra-sdk is waiting on this ftpmaster removal bug before it can migrate
to testing: #907266

Thanks,
James

Ben file:

title = "mbedtls";
is_affected = .depends ~ "libmbedcrypto1" | .depends ~ "libmbedtls10" |
.depends ~ "libmbedcrypto3" | .depends ~ "libmbedtls12";
is_good = .depends ~ "libmbedcrypto3" | .depends ~ "libmbedtls12";
is_bad = .depends ~ "libmbedcrypto1" | .depends ~ "libmbedtls10";


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf

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

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message --- 
Hi,

On 04/10/2018 11:19, Emilio Pozuelo Monfort wrote:
> Control: tags -1 confirmed
> 
> On 04/10/2018 11:04, James Cowgill wrote:
>> Package: release.debian.org
>> Severity: normal
>> User: release.debian.org@packages.debian.org
>> Usertags: transition
>>
>> Hi,
>>
>> mbedTLS needs a transition because upstream bumped the SONAME of
>> libmbedtls in 2.13 due to some symbol changes. I have also changed the
>> SONAME of libmbedcrypto to realign it with upstream. Previously upstream
>> had bumped the SONAME for no reason, so I reverted that change. Since we
>> now need a transition anyway, it seems sensible to me to use upstream's
>> SONAME again.
>>
>> The auto-mbedtls transition tracker looks correct. These packages need
>> binNMUing:
>>  bctoolbox
>>  bibledit
>>  charybdis
>>  dislocker
>>  dolphin-emu
>>  gatling
>>  julia
>>  libgit2
>>  lief
>>  mongrel2
>>  ncbi-blast+
>>  ncbi-vdb
>>  neko
>>  shadowsocks-libev
>>  sra-sdk
>>
>> All the packages build fine in a test rebuild except for dolphin-emu
>> which FTBFS for unrelated reasons which I will fix soon (#910268).
>>
>> sra-sdk is waiting on this ftpmaster removal bug before it can migrate
>> to testing: #907266
> 
> Please go ahead.

This transition is complete now. Thanks!

James

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: