On 2019-04-14 11:28:59 [+0100], Adam D. Barratt wrote:
> In the interest of keeping things moving, please feel free to go ahead.
thanks, uploaded.
> Adam
Sebastian
Processing control commands:
> tags 919043 + confirmed
Bug #919043 [release.debian.org] stretch-pu: ckermit/302-5.3+deb9u1
Ignoring request to alter tags of bug #919043 to the same tags previously set
--
919043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919043
Debian Bug Tracking System
Control: tags 919043 + confirmed
On Sun, 2019-04-14 at 12:26 +0200, Sebastian Andrzej Siewior wrote:
> On 2019-04-13 22:25:19 [+0100], Adam D. Barratt wrote:
> > On Fri, 2019-02-15 at 00:04 +0100, Sebastian Andrzej Siewior wrote:
> > > I'm proposing this attached debdiff.
> > > For testing I
Processing control commands:
> tags 919043 + confirmed
Bug #919043 [release.debian.org] stretch-pu: ckermit/302-5.3+deb9u1
Added tag(s) confirmed.
--
917485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917485
919043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919043
Debian Bug
On 2019-04-13 22:25:19 [+0100], Adam D. Barratt wrote:
> On Fri, 2019-02-15 at 00:04 +0100, Sebastian Andrzej Siewior wrote:
> > I'm proposing this attached debdiff.
> > For testing I compiled it against libssl1.0-dev 1.0.2j-5 and then
> > upgraded to the version provided by the security
On Fri, 2019-02-15 at 00:04 +0100, Sebastian Andrzej Siewior wrote:
> On 2019-02-02 14:46:54 [+0100], Andreas Beckmann wrote:
> > I'm not going to touch that package, please go ahead with preparing
> > a
> > NMU (or probably rather QA upload if it is gone from sid) to
> > stretch,
> > since you
On 2019-02-02 14:46:54 [+0100], Andreas Beckmann wrote:
> I'm not going to touch that package, please go ahead with preparing a
> NMU (or probably rather QA upload if it is gone from sid) to stretch,
> since you seem to know how to properly fix this bug once and for all :-)
I'm proposing this
On 2019-02-02 11:28, Sebastian Andrzej Siewior wrote:
> I suggest to simply drop that, the symbol based dependecy is enough.
> ckermit was removed from unstable. We should fix this in stretch. Is someone
> working on that or should I prepare a NMU? A am against a binNMU: It will fix
I'm not going
On 2019-01-12 13:25:12 [+0100], Andreas Beckmann wrote:
> For #917485:
> A proper fix to the package should drop this misleading line from the error
> message and tighten the dependencies on libssl1.x.y unless the requirement can
> be softened.
a proper dependecy on libssl1.0-dev does the magic.
On 2019-01-12 11:45, Adam D. Barratt wrote:
>> That's the message from starting kermit in stretch:
>>
>> ?OpenSSL libraries do not match required version:
>> . C-Kermit built with OpenSSL 1.0.2j 26 Sep 2016
>> . Version found OpenSSL 1.0.2q 20 Nov 2018
>> OpenSSL versions prior to 1.0.0
Control: tags -1 + moreinfo
On Sat, 2019-01-12 at 09:29 +0100, Andreas Beckmann wrote:
> since sid already has a +b1 binnmu, but currently FTBFS in sid for
> other reasons, you may need to apply some force to get the newer
> version into stable.
Specifically, if that is still the case at the
Processing control commands:
> tags -1 + moreinfo
Bug #919043 [release.debian.org] nmu: ckermit_302-5.3 (stretch)
Added tag(s) moreinfo.
--
919043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919043
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Followup-For: Bug #919043
Hi,
since sid already has a +b1 binnmu, but currently FTBFS in sid for
other reasons, you may need to apply some force to get the newer
version into stable.
nmu ckermit_302-5.3 2 . ANY . stretch-proposed-updates . -m "Rebuild against
openssl1.0 1.0.2q"
Note that this
13 matches
Mail list logo
