Your message dated Sat, 1 Nov 2014 10:16:08 +0000 with message-id <20141101101607.GD9785@lupin.home.powdarrmonkey.net> and subject line Re: Bug#757575: transition: libgcrypt20 has caused the Debian Bug report #757575, regarding transition: libgcrypt20 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.) -- 757575: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757575 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: transition: libgcrypt20
- From: Andreas Metzler <ametzler@bebt.de>
- Date: Sat, 9 Aug 2014 15:48:10 +0200
- Message-id: <20140809134810.GA25340@downhill.g.la>
Package: release.debian.org Severity: normal User: release.debian.org@packages.debian.org Usertags: transition Hello, I would like to make sure that we only ship one gcrypt version in jessie and am therefore opening the transition tracker now. libgcrypt20 is mostly API compatible to libgcrypt11. The main reason why we have versioned -dev packages is that libgnutls26 is one of the packages which cannot work with the old API. libgnutls26 should not be shipped in jessie so I envision that it should be possible to make major parts of this transition by bin-NMUs since I will be able to make libgcrypt11-dev a dummy package depending on libgcrypt20-dev after libgnutls26 has been dropped. libgcrypt11's upstream support will end on 2016-12-31. I will do some test builds to find out more. Ben file: title = "libgcrypt20"; is_affected = .depends ~ "libgcrypt11" | .depends ~ "libgcrypt20" | .depends ~ "libgcrypt11-dev" | .depends ~ "libgcrypt20-dev" | .depends ~ "libgcrypt-dev"; is_good = .depends ~ "libgcrypt20"; is_bad = .depends ~ "libgcrypt11"; -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
--- End Message ---
--- Begin Message ---
- To: Andreas Metzler <ametzler@bebt.de>, 757575-done@bugs.debian.org
- Subject: Re: Bug#757575: transition: libgcrypt20
- From: Jonathan Wiltshire <jmw@debian.org>
- Date: Sat, 1 Nov 2014 10:16:08 +0000
- Message-id: <20141101101607.GD9785@lupin.home.powdarrmonkey.net>
- In-reply-to: <20140809134810.GA25340@downhill.g.la>
- References: <20140809134810.GA25340@downhill.g.la>
On Sat, Aug 09, 2014 at 03:48:10PM +0200, Andreas Metzler wrote: > I would like to make sure that we only ship one gcrypt version in > jessie and am therefore opening the transition tracker now. > > libgcrypt20 is mostly API compatible to libgcrypt11. The main reason libgcrypt11 left Jessie this morning, and libgcrypt20 successfully migrated. -- Jonathan Wiltshire jmw@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51Attachment: signature.asc
Description: Digital signature
--- End Message ---