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

Bug#704215: marked as done (unblock: resiprocate - built against newer boost-dev)



Your message dated Fri, 29 Mar 2013 21:23:54 +0000
with message-id <f336eec08ead3aaa34b6bba15a7798ad@mail.adsl.funky-badger.org>
and subject line Re: Bug#704215: unblock: resiprocate - built against newer boost-dev
has caused the Debian Bug report #704215,
regarding unblock: resiprocate - built against newer boost-dev
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.)


-- 
704215: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704215
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal

I've found that one of the binaries, resiprocate-turn-server, needs to
be built again with the latest gcc and boost-dev or it fails to run

The root cause appears to be this issue:

  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654425

and the bug report concerning the impact on my package is:

  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704213

Please confirm if I should do the upload with a new version number
(1.8.5-4), or if there is some other way to force it to be rebuilt for
the existing version?  If I upload a new version, there will be no
changes except a changelog entry.

--- End Message ---
--- Begin Message ---
user release.debian.org@packages.debian.org
usertags 704215 unblock
thanks

On 29.03.2013 14:22, Daniel Pocock wrote:
Package: release.debian.org
Severity: normal

Please either use reportbug or add the relevant usertags yourself.

I've found that one of the binaries, resiprocate-turn-server, needs to
be built again with the latest gcc and boost-dev or it fails to run
[..]
Please confirm if I should do the upload with a new version number
(1.8.5-4), or if there is some other way to force it to be rebuilt for
the existing version?  If I upload a new version, there will be no
changes except a changelog entry.

As several people have pointed out already, there are several "if"s in the above paragraph which were overtaken by the fact that you uploaded in any case.

For future reference, the more appropriate solution would have been a binNMU on whichever architecture your misbuilt upload was made from. As it is, it's too late for that in unstable at least. Your upload has already either built or started building on all architectures, so I've unblocked it.

Regards,

Adam

--- End Message ---

Reply to: