Your message dated Mon, 30 Dec 2013 11:13:35 +0100
with message-id <52c1474f.5020...@pocock.com.au>
and subject line Re: Bug#733343: reconserver FTBFS on all architectures
has caused the Debian Bug report #733343,
regarding reconserver FTBFS on all architectures
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 ow...@bugs.debian.org
immediately.)


-- 
733343: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: reconserver
Version: 0.9.1-1
Severity: serious

Hi,

your package FTBFS on all architectures where it had been tried:
| configure: WARNING: unrecognized options: --disable-maintainer-mode
|    dh_auto_build -a -O--builddirectory=.
| make[1]: Entering directory `/«PKGBUILDDIR»'
| g++ -DPACKAGE_NAME=\"reConServer\" -DPACKAGE_TARNAME=\"reconserver\" 
-DPACKAGE_VERSION=\"0.9.1\" -DPACKAGE_STRING=\"reConServer\ 0.9.1\" 
-DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"reconserver\" 
-DVERSION=\"0.9.1\" -I.   -D_FORTIFY_SOURCE=2 -DRESIP_FIXED_POINT 
-I/usr/include/sipxtapi -D__pingtel_on_posix__ -D_linux_ -D_REENTRANT 
-D_FILE_OFFS -DDEFAULT_BRIDGE_MAX_IN_OUTPUTS=20 -DRESIP_TOOLCHAIN_GNU 
-DUSE_CARES -DUSE_SSL -DUSE_IPV6  -g -O2 -Wformat -Werror=format-security 
-fpermissive -c -o reConServer.o reConServer.cxx
| In file included from /usr/include/recon/UserAgent.hxx:4:0,
|                  from reConServer.cxx:41:
| /usr/include/recon/ConversationManager.hxx:12:31: fatal error: 
resip/stack/Uri.hxx: No such file or directory
|  #include <resip/stack/Uri.hxx>
|                                ^
| compilation terminated.
| make[1]: *** [reConServer.o] Error 1
| make[1]: Leaving directory `/«PKGBUILDDIR»'
| dh_auto_build: make -j1 returned exit code 2
| make: *** [build-arch] Error 2
| dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2


Can you please build your package in a clean chroot before upload
(i.e. in a chroot where nothing except build-essential and
build-dependencies are installed)?



Andi

--- End Message ---
--- Begin Message ---
On 29/12/13 01:41, Ivo De Decker wrote:
> Control: reassign -1 reconserver 0.9.1-1
>
> Hi Daniel,
>
> On Sat, Dec 28, 2013 at 11:31:18PM +0100, Daniel Pocock wrote:
>> reassign 733343 librecon-1.9-dev 1.9.0~beta8-1
>> fixed 733343 1.9.0~beta8-2
>> stop
>>
>> reconserver is not really at fault here, I believe librecon-1.9-dev
>> should depend on the related libresiprocate-1.9-dev and so the bug is
>> being reassigned there, fix is being uploaded.
> Not really. The new resiprocate upload just gets you to the next error:
> https://buildd.debian.org/status/fetch.php?pkg=reconserver&arch=i386&ver=0.9.1-1&stamp=1388277038

That was also an error with reSIProcate dev package dependencies

>
> I added a block hint to make sure this version of reconserver can't migrate to
> testing (even if this bug gets reassigned). Please let me know when the issues
> has been dealt with for real, and I will remove the block hint.

All the issues in reSIProcate have been fixed and the reConServer
package is now building fine


>> What is the best way to force another attempt at building reconserver
>> after the new librecon-1.9-dev is available in unstable?
> In normal circumstances (when the new upload of a build-dep would fix the
> issue for real), you could do a new upload with a versioned build-dependency
> on the new library you uploaded, or you could ask
> debian-wb-t...@lists.debian.org for a rebuild (in this case, with added
> 'dep-wait' on the new lib). I happened to notice this bug by chance (because
> aba mentioned it on irc), but normally, you should explicitly ask for
> rebuilds on the mailing list.

I want to avoid a versioned build dependency because it is quite
possible for somebody to build a local version of the reconserver
package with an older resiprocate library, they just have to install the
build dependencies manually

--- End Message ---

Reply via email to