Bug#791782: More test failures in ruby-patron

2015-08-11 Thread Potter, Tim (Cloud Services) 
I’m trying to rebuild this package from source and it’s also failing, but I get 
a
different set of errors.  Perhaps this will shed some light on what’s happening
to someone:

Running tests for ruby2.2 using debian/ruby-tests.rake ...
RUBYLIB=/Source/pkg-ruby/ruby-patron/debian/ruby-patron/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.2.0:/Source/pkg-ruby/ruby-patron/debian/ruby-patron/usr/lib/ruby/vendor_ruby:.
 ruby2.2 -rrake -e ARGV.unshift\(\-f\,\ \debian/ruby-tests.rake\\)\;\ 
Rake.application.run
/usr/bin/ruby2.2 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb
..FFF.F.F.FFF.FF.FF..

Failures:

  1) Patron::Response should strip extra spaces from header values
 Failure/Error: response = @session.get(/test)
 Patron::TimeoutError:
   Operation timed out after 5001 milliseconds with 0 bytes received
 # ./lib/patron/session.rb:223:in `handle_request'
 # ./lib/patron/session.rb:223:in `request'
 # ./lib/patron/session.rb:126:in `get'
 # ./spec/response_spec.rb:36:in `block (2 levels) in top (required)'

  2) Patron::Response should return an array of values when multiple header 
fields have same name
 Failure/Error: response = @session.get(/repetitiveheader)
 Patron::TimeoutError:
   Operation timed out after 5002 milliseconds with 0 bytes received
 # ./lib/patron/session.rb:223:in `handle_request'
 # ./lib/patron/session.rb:223:in `request'
 # ./lib/patron/session.rb:126:in `get'
 # ./spec/response_spec.rb:42:in `block (2 levels) in top (required)'

  3) Patron::Response should works with non-text files
 Failure/Error: response = @session.get(/picture)
 Patron::TimeoutError:
   Operation timed out after 5002 milliseconds with 0 bytes received
 # ./lib/patron/session.rb:223:in `handle_request'
 # ./lib/patron/session.rb:223:in `request'
 # ./lib/patron/session.rb:126:in `get'
 # ./spec/response_spec.rb:47:in `block (2 levels) in top (required)'

  4) Patron::Session should retrieve a url with :get
 Failure/Error: response = @session.get(/test)
 Patron::TimeoutError:
   Operation timed out after 5003 milliseconds with 0 bytes received
 # ./lib/patron/session.rb:223:in `handle_request'
 # ./lib/patron/session.rb:223:in `request'
 # ./lib/patron/session.rb:126:in `get'
 # ./spec/session_spec.rb:54:in `block (2 levels) in top (required)'

  5) Patron::Session should download content with :get and a file path
 Failure/Error: response = @session.get_file /test, tmpfile
 Patron::TimeoutError:
   Operation timed out after 5002 milliseconds with 0 bytes received
 # ./lib/patron/session.rb:223:in `handle_request'
 # ./lib/patron/session.rb:223:in `request'
 # ./lib/patron/session.rb:132:in `get_file'
 # ./spec/session_spec.rb:61:in `block (2 levels) in top (required)'

  6) Patron::Session should include custom headers in a request
 Failure/Error: response = @session.get(/test, {User-Agent = 
PatronTest})
 Patron::TimeoutError:
   Operation timed out after 5003 milliseconds with 0 bytes received
 # ./lib/patron/session.rb:223:in `handle_request'
 # ./lib/patron/session.rb:223:in `request'
 # ./lib/patron/session.rb:126:in `get'
 # ./spec/session_spec.rb:69:in `block (2 levels) in top (required)'

  7) Patron::Session should merge custom headers with session headers
 Failure/Error: response = @session.get(/test, {User-Agent = 
PatronTest})
 Patron::TimeoutError:
   Operation timed out after 5003 milliseconds with 0 bytes received
 # ./lib/patron/session.rb:223:in `handle_request'
 # ./lib/patron/session.rb:223:in `request'
 # ./lib/patron/session.rb:126:in `get'
 # ./spec/session_spec.rb:76:in `block (2 levels) in top (required)'

  8) Patron::Session should follow redirects by default
 Failure/Error: response = @session.get(/redirect)
 Patron::TimeoutError:
   Operation timed out after 5001 milliseconds with 0 bytes received
 # ./lib/patron/session.rb:223:in `handle_request'
 # ./lib/patron/session.rb:223:in `request'
 # ./lib/patron/session.rb:126:in `get'
 # ./spec/session_spec.rb:89:in `block (2 levels) in top (required)'

  9) Patron::Session should include redirect count in response
 Failure/Error: response = @session.get(/redirect)
 Patron::TimeoutError:
   Operation timed out after 5002 milliseconds with 0 bytes received
 # ./lib/patron/session.rb:223:in `handle_request'
 # ./lib/patron/session.rb:223:in `request'
 # ./lib/patron/session.rb:126:in `get'
 # ./spec/session_spec.rb:97:in `block (2 levels) in top (required)'

  10) Patron::Session should not follow redirects when configured to do so
  Failure/Error: response = @session.get(/redirect)
  Patron::TimeoutError:
Operation timed out after 5002 milliseconds with 0 bytes received
  # ./lib/patron/session.rb:223:in `handle_request'
  #

Bug#793518: [pkg-go] Bug#793518: Bug#793518: FTBFS: TestString fails: ini_test.go:167: Dict cannot be stringified as expected.

2015-08-04 Thread Potter, Tim (Cloud Services) 
On 30 Jul 2015, at 5:08 pm, Michael Stapelberg stapelb...@debian.org wrote:

 On Thu, Jul 30, 2015 at 6:05 AM, Potter, Tim (Cloud Services) 
 timothy.pot...@hp.com wrote:
 On 28 Jul 2015, at 5:14 pm, Michael Stapelberg stapelb...@debian.org wrote:
 
  So, yes, if you could work with upstream on a proper solution and then we 
  could just package a new upstream snapshot, that’d be great.

[…]

 Once upstream accepts your patches, please update the packaging git 
 repository and let me know, I’ll gladly sponsor this upload.
 
 I’m also open to granting you DM upload privileges on individual packages, 
 but I’d like to have a few more interactions with you before that :).

Hi Michael.  Upstream accepted and merged my patches, and I’ve updated the 
packaging on alioth.

Could you please take a look and upload if you think it’s OK?


Thanks,

Tim.

smime.p7s
Description: S/MIME cryptographic signature

Bug#793518: [pkg-go] Bug#793518: Bug#793518: FTBFS: TestString fails: ini_test.go:167: Dict cannot be stringified as expected.

2015-07-29 Thread Potter, Tim (Cloud Services) 
On 28 Jul 2015, at 5:14 pm, Michael Stapelberg stapelb...@debian.org wrote:
 
 So, yes, if you could work with upstream on a proper solution and then we 
 could just package a new upstream snapshot, that’d be great.

I’ve just posted two pull requests on the upstream project.  One to fix the 
occasional test failures, and another to fix another instances of relying
on the ordering of hash keys.

If someone can give me upload access (since I’m only a DM) I’ll upload
the package if/when upstream accepts my patches.  Otherwise I’ll just
pester people on the list for an update.  (-:


Tim.

smime.p7s
Description: S/MIME cryptographic signature

Bug#793518: [pkg-go] Bug#793518: Bug#793518: FTBFS: TestString fails: ini_test.go:167: Dict cannot be stringified as expected.

2015-07-28 Thread Potter, Tim (Cloud Services) 
On 28 Jul 2015, at 5:14 pm, Michael Stapelberg stapelb...@debian.org wrote:
 
 Chris, thanks for the explanation, that makes sense! I totally missed the 
 fact that there were not-yet-uploaded changes in git.
 
 Tim, I just tried packaging the new upstream snapshot, and the fix you got 
 upstream to merge was indeed not enough. My first guess is that exampleStr 
 requires section1 and section2 to be serialized in order, but Dict.format() 
 does not sort the keys when iterating over the map.

Yes that’s correct.  I think that entire test needs to be rewritten - perhaps 
by deserialising the generated string and then making assertions against the 
dict.

 It’s surprising that this hasn’t caused issues elsewhere yet.

It doesn’t happen very often so perhaps the failure is easily missed if the 
tests aren’t run often and automatically.

 So, yes, if you could work with upstream on a proper solution and then we 
 could just package a new upstream snapshot, that’d be great.

OK - I’ll work on that then.


Tim.

 
 On Tue, Jul 28, 2015 at 3:02 AM, Potter, Tim (Cloud Services) 
 timothy.pot...@hp.com wrote:
 On 28 Jul 2015, at 6:35 am, solo-debianb...@goeswhere.com wrote:
 
  On Mon, Jul 27, 2015 at 07:26:10PM +0200, Michael Stapelberg wrote:
  control: tags -1 + unreproducible
 
  Chris, was this an issue on your end? Or am I misinterpreting something?
 
 
  The problem seems to have gone away.  I was running local builds in
  response to errors on the reproducible-builds builder.  Their builder
  has rebuilt sucessfully since then, and I have also just rebuilt
  sucessfully.  Perhaps it was fixed by dependency changes?
 
  Proof I'm not mad: my build log from local:
  https://paste.debian.net/286717/
 
 Hi everyone.  I think this bug is due to this test  relying on the ordering 
 of keys retrieved from
 a hash being the same as they were inserted.  This seems to work most of the 
 time (at
 least on amd64) but occasionally the keys come out in a different order and 
 the test breaks.
 
 I could disable the test so things work and work with upstream for a proper 
 fix.  Would that
 help out some?
 
 
 Tim.
 
 
 
 -- 
 Best regards,
 Michael



smime.p7s
Description: S/MIME cryptographic signature

Bug#793518: [pkg-go] Bug#793518: Bug#793518: FTBFS: TestString fails: ini_test.go:167: Dict cannot be stringified as expected.

2015-07-27 Thread Potter, Tim (Cloud Services) 
On 28 Jul 2015, at 6:35 am, solo-debianb...@goeswhere.com wrote:
 
 On Mon, Jul 27, 2015 at 07:26:10PM +0200, Michael Stapelberg wrote:
 control: tags -1 + unreproducible
 
 Chris, was this an issue on your end? Or am I misinterpreting something?
 
 
 The problem seems to have gone away.  I was running local builds in
 response to errors on the reproducible-builds builder.  Their builder
 has rebuilt sucessfully since then, and I have also just rebuilt
 sucessfully.  Perhaps it was fixed by dependency changes?
 
 Proof I'm not mad: my build log from local:
 https://paste.debian.net/286717/

Hi everyone.  I think this bug is due to this test  relying on the ordering of 
keys retrieved from
a hash being the same as they were inserted.  This seems to work most of the 
time (at 
least on amd64) but occasionally the keys come out in a different order and the 
test breaks.

I could disable the test so things work and work with upstream for a proper 
fix.  Would that
help out some?


Tim.

smime.p7s
Description: S/MIME cryptographic signature

Bug#777857: fsvs: ftbfs with GCC-5

2015-07-26 Thread Potter, Tim (Cloud Services) 
On 26 Jul 2015, at 12:39 am, Philipp Marek phil...@marek.priv.at wrote:
 
 Hello Tim,
 
 I'm sorry about the delay,
 
 Hi Phillip.  I noticed that you committed this fix to the
 branches/fsvs-1.2.x but haven’t released a new version of fsvs
 containing it.
 Would you be interested in cutting a 1.2.6 release containing just the
 gcc5 fix?  I can get it uploaded to Debian as a NMU and this bug
 closed out.
 Done now, 1.2.6 is released, see http://download.fsvs-software.org/.

Great - thanks Philipp!  I’ve prepared a new upload for this release and as
soon as I can find someone to actually upload it, favs 1.2.6 should be part 
of Debian unstable.


Regards,

Tim.

smime.p7s
Description: S/MIME cryptographic signature

Bug#777857: fsvs: ftbfs with GCC-5

2015-07-16 Thread Potter, Tim (Cloud Services) 
On Thu, 12 Feb 2015 12:05:00 +0100 Philipp Marek phil...@marek.priv.at wrote:
 (errors) fixed in r2472, builds with GCC 5.

Hi Phillip.  I noticed that you committed this fix to the branches/fsvs-1.2.x 
but haven’t released a new version of fsvs containing it. 

Would you be interested in cutting a 1.2.6 release containing just the gcc5 
fix?  I can get it uploaded to Debian as a NMU and this bug closed out.


Regards,

Tim.

smime.p7s
Description: S/MIME cryptographic signature

Bug#777916: Fix for ioapps gcc5 build failures

2015-07-15 Thread Potter, Tim (Cloud Services) 
tags 777916 + patch
thanks

Hi there.  Here’s a quick patch to fix the gcc5 build failures for the ioapps 
package.  Since upstream appears to be unmaintained and doesn’t use autoconf 
I’m proposing a patch to modify the Makefile directly.

Patch is attached which appends “-std=gnu89” flag to the CFLAGS to address the 
semantic change in the definition of inline functions in C11.


Regards,

Tim.



777916-gcc5-fixes.patch
Description: Binary data


smime.p7s
Description: S/MIME cryptographic signature

Bug#777856: FTBFS appears to be fixed in freetype 2.5.2-3 or 2.5.2-4

2015-07-15 Thread Potter, Tim (Cloud Services) 
Hi Steve.  Looks like this bug is no longer reproducible in one of the previous 
two uploads that Keith made.

I wasn’t able to reproduce on my gcc5 test system so was wondering if you could 
close out this bug.


Regards,

Tim.

smime.p7s
Description: S/MIME cryptographic signature

Bug#777910: Fix for gcc5 compile failure

2015-07-15 Thread Potter, Tim (Cloud Services) 
tags 488159 + patch
thanks

Ironically, the code that checks for the C99 “restrict” keyword does not 
compile because “restrict” cannot be used as a variable name.  Attached is a 
patch that fixes this by renaming the local variable in this case.

The maintainer has signed up for LowThresholdNMU so I recommend that this 
package be NMU’d with this patch to close this bug.


Thanks,

Tim.


777910-gcc5-fixes.patch
Description: Binary data


smime.p7s
Description: S/MIME cryptographic signature

Bug#777917: Fix for ipgrab FTBFS error with gcc5

2015-07-15 Thread Potter, Tim (Cloud Services) 
tags 777917 + patch
thanks

Hi there.  Here’s a small patch to fix the FTBS with gcc5.  It simply adds 
-std=gnu89 to CFLAGS in debian/rules which is picked up by autoconf.


Regards,

Tim.


777917-gcc5-fixes.patch
Description: Binary data
 

smime.p7s
Description: S/MIME cryptographic signature

Bug#777814: Resend control messages from Matthias

2015-07-12 Thread Potter, Tim (Cloud Services) 
Control: notfound -1 0.94.2-1
Control: tags -1 + patch

this works with ceph from experimental. The link failure goes away once leveldb
is rebuilt using GCC 5.

smime.p7s
Description: S/MIME cryptographic signature

Bug#777814: Build procedure to fix this bug

2015-07-12 Thread Potter, Tim (Cloud Services) 
As mentioned by Matthias think error above is fixed by recompiling leveldb.  I 
added a block on 791086 to reflect this.

My build procedure is:

- install boost packages from experimental

$ apt-get install -t experimental libboost-dev libboost-program-options-dev 
libboost-system-dev libboost-thread-dev

- rebuild leveldb with gcc5

$ apt-get source leveldb
[rebuilt it]
$ dpkg -i libleveldb-dev_1.18-2_amd64.deb  libleveldb1_1.18-2_amd64.deb

- Install systemd from experimental to satisfy other B-D dependencies

$ apt-get install -t experimental systemd

- Apply patch to get test to link (not sure why this didn’t break anything 
before)

Index: ceph-0.94.2/src/test/Makefile-client.am
===
--- ceph-0.94.2.orig/src/test/Makefile-client.am
+++ ceph-0.94.2/src/test/Makefile-client.am
@@ -337,7 +337,7 @@ if LINUX
 ceph_test_librbd_fsx_SOURCES = test/librbd/fsx.c common/dummy.cc
 ceph_test_librbd_fsx_LDADD = \
$(LIBKRBD) $(LIBRBD) $(LIBRADOS) \
-   $(CRYPTO_LIBS) $(PTHREAD_LIBS) -luuid
+   $(CRYPTO_LIBS) $(PTHREAD_LIBS) -luuid -lcommon
 ceph_test_librbd_fsx_CFLAGS = ${AM_CFLAGS}
 bin_DEBUGPROGRAMS += ceph_test_librbd_fsx
 endif

- rebuild (and wait a long time)

smime.p7s
Description: S/MIME cryptographic signature

Bug#777814:

2015-07-07 Thread Potter, Tim (Cloud Services) 
I don’t understand the original failure, but I just rebuilt the package using 
an up-to-date version of unstable the latest version of boost installed from 
experimental as it has been rebuilt with gcc5.

The next error I get is during running the unit tests:

g++ -DHAVE_CONFIG_H -I.  -D__CEPH__ -D_FILE_OFFSET_BITS=64 -D_REENTRANT 
-D_THREAD_SAFE -D__STDC_FORMAT_MACROS -D_GNU_SOURCE 
-DCEPH_LIBDIR=\/usr/lib/x86_64-linux-gnu\ 
-DCEPH_PKGLIBDIR=\/usr/lib/x86_64-linux-gnu/ceph\ -DGTEST_HAS_TR1_TUPLE=0 
-D_FORTIFY_SOURCE=2 -I/usr/include/nss -I/usr/include/nspr   -Wall 
-Wtype-limits -Wignored-qualifiers -Winit-self -Wpointer-arith 
-Werror=format-security -fno-strict-aliasing -fsigned-char -rdynamic 
-ftemplate-depth-1024 -Wnon-virtual-dtor -Wno-invalid-offsetof   
-fno-builtin-malloc -fno-builtin-calloc -fno-builtin-realloc -fno-builtin-free 
-Wstrict-null-sentinel -g -O2 -fPIE -fstack-protector-strong -Wformat 
-Werror=format-security -c -o test/streamtest.o test/streamtest.cc
test/streamtest.cc:190:1: warning: 'virtual int 
ObjectStore::collection_getattr(coll_t, const char*, void*, size_t)' is 
deprecated [-Wdeprecated-declarations]
 }
 ^
In file included from ./os/FileStore.h:31:0,
 from test/streamtest.cc:16:
./os/ObjectStore.h:1996:15: note: declared here
   virtual int collection_getattr(coll_t cid, const char *name,
   ^
test/streamtest.cc:190:1: warning: 'virtual int 
ObjectStore::collection_getattr(coll_t, const char*, ceph::bufferlist)' is 
deprecated [-Wdeprecated-declarations]
 }
 ^
In file included from ./os/FileStore.h:31:0,
 from test/streamtest.cc:16:
./os/ObjectStore.h:2010:15: note: declared here
   virtual int collection_getattr(coll_t cid, const char *name, bufferlist bl)
   ^
test/streamtest.cc:190:1: warning: 'virtual int 
ObjectStore::collection_getattrs(coll_t, 
std::mapstd::__cxx11::basic_stringchar, ceph::buffer::ptr)' is deprecated 
[-Wdeprecated-declarations]
 }
 ^
In file included from ./os/FileStore.h:31:0,
 from test/streamtest.cc:16:
./os/ObjectStore.h:2022:15: note: declared here
   virtual int collection_getattrs(coll_t cid, mapstring,bufferptr aset)
   ^
/bin/bash ../libtool  --tag=CXX   --mode=link g++ -I/usr/include/nss 
-I/usr/include/nspr   -Wall -Wtype-limits -Wignored-qualifiers -Winit-self 
-Wpointer-arith -Werror=format-security -fno-strict-aliasing -fsigned-char 
-rdynamic -ftemplate-depth-1024 -Wnon-virtual-dtor -Wno-invalid-offsetof   
-fno-builtin-malloc -fno-builtin-calloc -fno-builtin-realloc -fno-builtin-free 
-Wstrict-null-sentinel -g -O2 -fPIE -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,--as-needed -latomic_ops -fPIE -pie -Wl,-z,relro 
-Wl,-z,now -Wl,--as-needed -o ceph_streamtest test/streamtest.o libos.la -laio  
 -lleveldb -lsnappy libglobal.la libcommon.la -lpthread -lm -lnss3 -lnssutil3 
-lsmime3 -lssl3 -lplds4 -lplc4 -lnspr4  -luuid -lm  -lrt   -lboost_system
libtool: link: g++ -I/usr/include/nss -I/usr/include/nspr -Wall -Wtype-limits 
-Wignored-qualifiers -Winit-self -Wpointer-arith -Werror=format-security 
-fno-strict-aliasing -fsigned-char -rdynamic -ftemplate-depth-1024 
-Wnon-virtual-dtor -Wno-invalid-offsetof -fno-builtin-malloc 
-fno-builtin-calloc -fno-builtin-realloc -fno-builtin-free 
-Wstrict-null-sentinel -g -O2 -fPIE -fstack-protector-strong -Wformat 
-Werror=format-security -fPIE -pie -Wl,-z -Wl,relro -Wl,-z -Wl,now -o 
ceph_streamtest test/streamtest.o  /usr/lib/libatomic_ops.a -Wl,--as-needed 
./.libs/libos.a -laio -lleveldb -lsnappy ./.libs/libglobal.a 
./.libs/libcommon.a -ldl -lboost_thread -lpthread -lnss3 -lnssutil3 -lsmime3 
-lssl3 -lplds4 -lplc4 -lnspr4 -luuid -lm -lrt -lboost_system
./.libs/libos.a(libos_la-LevelDBStore.o): In function 
`LevelDBStore::do_open(std::ostream, bool)':
/ceph-0.94.2/src/os/LevelDBStore.cc:70: undefined reference to 
`leveldb::DB::Open(leveldb::Options const, std::__cxx11::basic_stringchar, 
std::char_traitschar, std::allocatorchar  const, leveldb::DB**)'
/ceph-0.94.2/src/os/LevelDBStore.cc:73: undefined reference to 
`leveldb::Status::ToString[abi:cxx11]() const'
./.libs/libos.a(libos_la-LevelDBStore.o): In function 
`LevelDBStore::_test_init(std::__cxx11::basic_stringchar, 
std::char_traitschar, std::allocatorchar  const)':
/ceph-0.94.2/src/os/LevelDBStore.cc:100: undefined reference to 
`leveldb::DB::Open(leveldb::Options const, std::__cxx11::basic_stringchar, 
std::char_traitschar, std::allocatorchar  const, leveldb::DB**)'
collect2: error: ld returned 1 exit status
Makefile:11304: recipe for target 'ceph_streamtest' failed
make[5]: *** [ceph_streamtest] Error 1
make[5]: Leaving directory '/ceph-0.94.2/src'
Makefile:20993: recipe for target 'all-recursive' failed
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory '/ceph-0.94.2/src'
Makefile:8907: recipe for target 'all' failed
make[3]: *** [all] Error 2
make[3]: Leaving directory '/ceph-0.94.2/src'
Makefile:465: recipe for target

Bug#778164: Patch for building under gcc5

2015-07-06 Thread Potter, Tim (Cloud Services) 
tags 778164 + patch
thanks

Hi there.  Attached is a small patch to fix the build under gcc5.  The 
visibility of one of the functions in the yacc grammar is increased so the 
program links without error now.


Regards,

Tim.


778164-gcc5-fixes.patch
Description: Binary data


smime.p7s
Description: S/MIME cryptographic signature

Bug#777787: Sorry - probably should not have closed this

2015-07-02 Thread Potter, Tim (Cloud Services) 
Hi - sorry I think I got a bit carried away and closed this bug.  Apologies if 
I overstepped.


Regards,

Tim.

smime.p7s
Description: S/MIME cryptographic signature

Bug#777787:

2015-07-02 Thread Potter, Tim (Cloud Services) 
close 87 5.1.1-1
thanks

Tried to reproduce with the latest version and it builds fine under gcc5 now.

smime.p7s
Description: S/MIME cryptographic signature

Bug#777849: Patch to fix FTBFS error for gcc5

2015-07-01 Thread Potter, Tim (Cloud Services) 
tags 777849 + patch
thanks

Hi there.  I’ve made a small patch to debian/rules for the fhist package to 
build correctly using gcc5.  I’ve also tested with gcc 4.9.2 and there are no 
adverse effects.



Regards,

Tim.


777849-gcc5-ftbfs.patch
Description: Binary data


smime.p7s
Description: S/MIME cryptographic signature

Bug#777819: Partial fix for FTBFS error

2015-06-29 Thread Potter, Tim (Cloud Services) 
tags 777819 + patch
thanks

Hi there.  I’ve made a partial fix for building clementine under GCC5.  The 
patch is attached and it’s a simple rearrangement of operands to prevent an 
error/bug due to operator precedence.  The fix has already made it into the 
master branch of upstream.

This doesn’t completely fix the FTBFS though.  I had to rebuild libprotobuf 
using GCC5 to allow linking using the new C++ ABI but that should fix itself 
over time.  The latest problem is a link problem against TagLib::String::String.

Linking CXX executable ../../clementine-tagreader
cd /root/clementine-1.2.3+dfsg/obj-x86_64-linux-gnu/ext/clementine-tagreader  
/usr/bin/cmake -E cmake_link_script 
CMakeFiles/clementine-tagreader.dir/link.txt --verbose=1
/usr/bin/c++   -DQT_NO_DEBUG_OUTPUT -DQT_NO_WARNING_OUTPUT --std=c++0x 
-U__STRICT_ANSI__   -Wl,-z,relro CMakeFiles/clementine-tagreader.dir/main.cpp.o 
CMakeFiles/clementine-tagreader.dir/tagreaderworker.cpp.o 
CMakeFiles/clementine-tagreader.dir/qrc_data.cxx.o  -o 
../../clementine-tagreader -rdynamic -ltag -lQtCore -lQtNetwork 
../libclementine-common/liblibclementine-common.a 
../libclementine-tagreader/liblibclementine-tagreader.a 
../libclementine-common/liblibclementine-common.a -lprotobuf -ltag -lpthread
../libclementine-tagreader/liblibclementine-tagreader.a(tagreader.cpp.o): In 
function `TagReader::SaveFile(QString const, pb::tagreader::SongMetadata 
const) const':
tagreader.cpp:(.text+0x62e0): undefined reference to 
`TagLib::String::String(std::__cxx11::basic_stringchar, 
std::char_traitschar, std::allocatorchar  const, TagLib::String::Type)'
tagreader.cpp:(.text+0x63c6): undefined reference to 
`TagLib::String::String(std::__cxx11::basic_stringchar, 
std::char_traitschar, std::allocatorchar  const, TagLib::String::Type)'
tagreader.cpp:(.text+0x64ac): undefined reference to 
`TagLib::String::String(std::__cxx11::basic_stringchar, 
std::char_traitschar, std::allocatorchar  const, TagLib::String::Type)'
collect2: error: ld returned 1 exit status
ext/clementine-tagreader/CMakeFiles/clementine-tagreader.dir/build.make:151: 
recipe for target 'clementine-tagreader' failed
make[4]: *** [clementine-tagreader] Error 1
make[4]: Leaving directory '/root/clementine-1.2.3+dfsg/obj-x86_64-linux-gnu'
CMakeFiles/Makefile2:1559: recipe for target 
'ext/clementine-tagreader/CMakeFiles/clementine-tagreader.dir/all' failed
make[3]: *** [ext/clementine-tagreader/CMakeFiles/clementine-tagreader.dir/all] 
Error 2
make[3]: Leaving directory '/root/clementine-1.2.3+dfsg/obj-x86_64-linux-gnu'
Makefile:119: recipe for target 'all' failed
make[2]: *** [all] Error 2
make[2]: Leaving directory '/root/clementine-1.2.3+dfsg/obj-x86_64-linux-gnu'
dh_auto_build: make -j1 returned exit code 2
debian/rules:23: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/root/clementine-1.2.3+dfsg'
debian/rules:8: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
debuild: fatal error at line 1382:
dpkg-buildpackage -rfakeroot -D -us -uc failed

This doesn’t look like an ABI problem and I don’t have a fix yet, but thought I 
would post my work so far.


Regards,

Tim.



777819-fix-gcc5-ftbfs.patch
Description: Binary data


smime.p7s
Description: S/MIME cryptographic signature

Bug#778024: Patch for build failure

2015-06-28 Thread Potter, Tim (Cloud Services) 
tags 778024 + patch
thanks

Hi there.  Here’s a quick patch to fix the build under g++-5.  Not sure whether 
this should be an upstream patch or one in debian/patches.


Regards,

Tim.



778024-gcc5.patch
Description: Binary data


smime.p7s
Description: S/MIME cryptographic signature

Bug#742689: check-mk: more CVE info

2015-03-13 Thread Potter, Tim (Cloud Services) 
On Fri, 09 Jan 2015 12:09:46 -0800 Matt Taggart tagg...@debian.org wrote:

 Most of the links on
  https://security-tracker.debian.org/tracker/CVE-2014-2330
  https://security-tracker.debian.org/tracker/CVE-2014-2331

 don't give any info, the RedHat link is for the full set of things and
 it's not clear to me if they fixed these explicitly. Maybe the brief
 descriptions on the packetstormsecurity will be enough for someone
 on the security team to determine if there is anything to be done.

Hi Matt.  The RedHat link has since been updated to say that CVE-2014-2330 and 
CVE-2014-2331 are cross-site scripting issues and are fixed in versions 1.2.2p3 
and 1.2.3i5.


Tim.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#779112: closed by Tim Potter t...@hp.com (Bug#779112: fixed in jnr-constants 0.8.6-3)

2015-03-05 Thread Potter, Tim (Cloud Services) 
On 6/03/15 6:37 AM, Andreas Beckmann a...@debian.org wrote:

On 2015-03-05 04:21, Debian Bug Tracking System wrote:
* Change dependency on libconstantine-java to Conflicts, from
  Breaks. (Closes: #779112).

No. Breaks should have been sufficient, but you are still missing a
Replaces.

  Selecting previously unselected package libconstantine-java.
  Preparing to unpack .../libconstantine-java_0.8.5-1_all.deb ...
  Unpacking libconstantine-java (0.8.5-1) ...
  dpkg: error processing archive
/var/cache/apt/archives/libconstantine-java_0.8.5-1_all.deb (--unpack):
   trying to overwrite '/usr/share/java/jnr-constants.jar', which is also
in package libjnr-constants-java 0.8.6-3
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libconstantine-java_0.8.5-1_all.deb

Or wait, the changelog wording mislead me. The versioning is wrong:

Replaces: libconstantine-java ( 0.8.5-1)
Provides: libconstantine-java
Conflicts: libconstantine-java ( 0.8.5-1)

In your case you either want unversioned Conflicts+Replaces
or (= 0.8.5) instead.

Nuts - thanks for pointing that out, and sorry for not actually testing my
fix since it's trivially easy to do so.  Changing the versioning as you
describe does the job and I've verified this is the case before uploading
it again.


Regards,

Tim.


smime.p7s
Description: S/MIME cryptographic signature

Bug#768678: no subject

2014-12-09 Thread Potter, Tim (Cloud Services) 
Hi everyone.  Can this bug be closed out?  I don't think marking it as
pending is good enough to fix auto-removed build-dependencies on
ruby-faraday.

I've checked the dependent bug mentioned, 770728, and the two packages
mentioned (ruby-em-hiredis and ruby-em-synchrony) transitioned to testing
in late November.  ruby-faraday is a build dependency for one of my
packages, ruby-elasticsearch, and the QA page still says that it will be
auto removed by this bug.



Regards,

Tim.


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#770648: no subject

2014-12-04 Thread Potter, Tim (Cloud Services) 
Hi everyone.  I'm nervously following along with this bug since its
presence is threatening the removal of a couple of dozen other packages as
you can all probably see from the QA page.

In the spirit of not hassling anyone (-: I was curious whether there was a
plan to close this out?  It sounds like a solution is very near, hopefully
to the satisfaction of both the maintainers and release coordinators.


Regards,

Tim.


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#759736: elasticsearch: CVE-2014-3120

2014-09-01 Thread Potter, Tim (Cloud Services) 
On 30/08/14 5:37 AM, Salvatore Bonaccorso car...@debian.org wrote:

Source: elasticsearch
Severity: grave
Tags: security upstream fixed-upstream

Hi Hilko,

I see elasticsearch entered unstable now. Some time ago the following
vulnerability was published for elasticsearch.

CVE-2014-3120[0]:
| The default configuration in Elasticsearch before 1.2 enables dynamic
| scripting, which allows remote attackers to execute arbitrary MVEL
| expressions and Java code via the source parameter to _search.  NOTE:
| this only violates the vendor's intended security policy if the user
| does not run Elasticsearch in its own independent virtual machine.

If I understand it correctly, the value or this defaults to false,
more references are in Red Hat's Bugzilla[1]. Could you check
elasticsearch for this?

Hi Salvatore.  I've checked the current version in the archive and it
definitely is vulnerable.  I've made a patch and am just running some
build tests now.

I'm hoping that Hilko can make an upload as I'm not on the uploaders list,
and don't really know how anyway.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities  Exposures) id in your changelog entry.

Done.

For further information see:

[0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-3120
https://security-tracker.debian.org/tracker/CVE-2014-3120
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1124252
[2] https://github.com/elasticsearch/elasticsearch/issues/5853
[3] https://github.com/elasticsearch/elasticsearch/commit/81e83cca

These were great resources - thanks for including them in the message.


Tim Potter
Cloud Systems Engineer
HP Cloud Services

timothy.pot...@hp.com
M +61 419 749 832
Hewlett-Packard Australia Pty Ltd

This e-mail may contain confidential and privileged material for the sole
use of the intended recipient. Any review, use, distribution or disclosure
by others is strictly prohibited. If you are not the intended recipient
(or authorised to receive for the recipient), please contact the sender by
reply e-mail and delete all copies of this message.



smime.p7s
Description: S/MIME cryptographic signature

Bug#759736: elasticsearch: CVE-2014-3120

2014-09-01 Thread Potter, Tim (Cloud Services) 
On 2/09/14 2:19 AM, tony mancill tmanc...@debian.org wrote:

 CVE-2014-3120[0]:
 | The default configuration in Elasticsearch before 1.2 enables dynamic
 | scripting, which allows remote attackers to execute arbitrary MVEL
 | expressions and Java code via the source parameter to _search.  NOTE:
 | this only violates the vendor's intended security policy if the user
 | does not run Elasticsearch in its own independent virtual machine.

Hi Salvatore.  I've checked the current version in the archive and it
 definitely is vulnerable.  I've made a patch and am just running some
 build tests now.
 
 I'm hoping that Hilko can make an upload as I'm not on the uploaders
list,
 and don't really know how anyway.

Hi Tim,

Thanks for helping out with this bug.  If you could attach your patch
(the debdiff tool can be helpful here) to the bug report, either Hilko
or I (or any DD) can rebuild and upload.

Attached.  I didn't know about debdiff - what a great tool!

Tim Potter
Cloud Systems Engineer
HP Cloud Services

timothy.pot...@hp.com
M +61 419 749 832
Hewlett-Packard Australia Pty Ltd

This e-mail may contain confidential and privileged material for the sole
use of the intended recipient. Any review, use, distribution or disclosure
by others is strictly prohibited. If you are not the intended recipient
(or authorised to receive for the recipient), please contact the sender by
reply e-mail and delete all copies of this message.




deb.diff
Description: Binary data


smime.p7s
Description: S/MIME cryptographic signature