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

Bug#962173: marked as done (wsjtx: hard-codes boost 1.67)

Your message dated Fri, 5 Jun 2020 15:33:08 +0200
with message-id <20200605133308.GA2645777@msg.df7cb.de>
and subject line Re: Bug#962173: wsjtx: hard-codes boost 1.67
has caused the Debian Bug report #962173,
regarding wsjtx: hard-codes boost 1.67
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.)


-- 
962173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962173
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: wsjtx
Version: 2.2.0+repack-1
Severity: serious
User: team+boost@tracker.debian.org
Usertags: boost1.71
Control: block 961995 by -1

wsjtx hard-codes he boost version Build-Depends. Since the transition to
boost 1.71 is currently ongoing, please switch to the the unversioned
packages (libboost-dev) or at least replace it with liboost1.71-dev.

Cheers
-- 
Sebastian Ramacher

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
Version: 2.2.0+repack-2

Re: Sebastian Ramacher
> Source: wsjtx
> Version: 2.2.0+repack-1
> Severity: serious
> User: team+boost@tracker.debian.org
> Usertags: boost1.71
> Control: block 961995 by -1
> 
> wsjtx hard-codes he boost version Build-Depends. Since the transition to
> boost 1.71 is currently ongoing, please switch to the the unversioned
> packages (libboost-dev) or at least replace it with liboost1.71-dev.

Fixed in the last upload, but I forgot to mention the bug number in
the changelog.

Thanks for spotting!

Christoph

--- End Message ---
Reply to: