Bug#822519: bobcat: FTBFS: /usr/bin/yodl indicates failure

2016-04-25 Thread Frank B. Brokken
Dear Martin Michlmayr, you wrote:
> 
> Package: bobcat
> Version: 4.01.04-1
> Severity: serious
> 
> Hi Frank, here's a build failure of bobcat.  I don't know if it's a
> regression in yodl or if something has to change in bobcat, but in any
> case, bobcat fails to build from source in unstable (FTBFS):

Thanks again! I overlooked your e-mail, but I was informed by Tony about
it. It's the same issue as with bisonc++, and right now I'm preparing a fix,
which should be ready within the hour. 

Cheers,

-- 
Frank B. Brokken
Center for Information Technology, University of Groningen
(+31) 50 363 9281 
Public PGP key: http://pgp.surfnet.nl
Key Fingerprint: DF32 13DE B156 7732 E65E  3B4D 7DB2 A8BE EAE4 D8AA


signature.asc
Description: PGP signature


Bug#821100: [debian-mysql] Bug#821100: MySQL 5.5.49 for Oracle April 2016 CPU

2016-04-25 Thread Salvatore Bonaccorso
Hi Robie,

On Mon, Apr 25, 2016 at 05:40:50PM +0100, Robie Basak wrote:
> Hi Salvatore,
> 
> On Mon, Apr 25, 2016 at 04:54:03PM +0200, Salvatore Bonaccorso wrote:
> > On Fri, Apr 22, 2016 at 09:52:44AM +0100, Robie Basak wrote:
> > > On Thu, Apr 21, 2016 at 07:13:34PM +0200, Salvatore Bonaccorso wrote:
> > > > Do you have any status-update for this for us?
> > > 
> > > Struggling to find an available and willing sponsor, sorry. Lars has had
> > > his tree ready for a while.
> > > 
> > > I am DM for src:mysql-5.6, but not for src:mysql-5.5 (that's just a
> > > technicality, I could be added I suppose) but I think you said that this
> > > needs a DD?
> > > 
> > > Unfortunately this means that Lars passes his work to me for review, and
> > > then I pass it to a sponsor for upload, so it's a bit slow.
> > > 
> > > My usual sponsoring DD for MySQL is also an Ubuntu dev and is busy this
> > > week (it being Ubuntu release week) so hasn't been able to spare any
> > > time for me on this. I'll continue to seek a sponsor.
> > > 
> > > If anyone else can help please, the trees are at:
> > > 
> > > http://anonscm.debian.org/cgit/pkg-mysql/mysql-5.5.git/log/
> > > http://anonscm.debian.org/cgit/pkg-mysql/mysql-5.5.git/log/?h=debian/wheezy
> > > 
> > > In my judgement (as a DM for mysql-5.6), Lars' work here is correct and
> > > ready to upload.
> > 
> > Did you got a reply from your sponsor? Btw, please not that by now --
> > since wheezy security support will end tomorrow, and then handled over
> > to the LTS team, we can only handle the jessie-security upload via the
> > DSA.
> 
> Sorry, I missed your email on Friday. I saw it earlier today so prepared
> the signed source packages. I spent some time doing some further testing
> and uploaded the signed source packages to:
> 
> http://people.canonical.com/~rbasak/mysql-5.5/
> 
> In addition to the dep8 tests (not present in wheezy), I've also done a
> quick smoke by hand. I understand that you may not be able to upload
> wheezy but I figured that at least it's here for the LTS team if they
> want to take it.

Thank you! I'm starting with jessie-security one, might be that I can
as well then do the wheezy one, but will first focus on jessie.

Regards,
Salvatore



Bug#822410: marked as done (bisonc++: FTBFS: failure of system call / usage: ...)

2016-04-25 Thread Debian Bug Tracking System
Your message dated Tue, 26 Apr 2016 03:34:54 +
with message-id 
and subject line Bug#822410: fixed in bisonc++ 5.00.01-1
has caused the Debian Bug report #822410,
regarding bisonc++: FTBFS: failure of system call / usage: ...
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.)


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

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> Yodl: including file algorithm/ruleprec.yo
> Yodl: including file algorithm/condep.yo
> Yodl: including file algorithm/reduce.yo
> usage: [-a] [-N] [-n] [-s] [-t] [-S] [-T] marker file
> See also: `man yodlverbinsert'
> Yodl: including file algorithm/mysterious.yo
> Yodl: including file error.yo
> Yodl: including file error/intro.yo
> Yodl: including file error/syntactical.yo
> Yodl: including file error/recovery.yo
> Yodl: including file error/semantical.yo
> Yodl: including file invoking.yo
> Yodl: including file invoking/options.yo
> Yodl: including file invoking/usage.yo
> 
> If a message about a failing NOEXPANDINCLUDE is shown, create the file 
> `usage' in documentation/manual/invoking containing the latest usage info
> 
> Error(s) detected
> /usr/bin/yodl indicates failure!
> Fatal: system - failure of system call (status 256)
> debian/rules:41: recipe for target 'build-indep' failed
> make: *** [build-indep] Error 1

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: bisonc++
Source-Version: 5.00.01-1

We believe that the bug you reported is fixed in the latest version of
bisonc++, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 822...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Frank B. Brokken  (supplier of updated bisonc++ package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 25 Apr 2016 15:52:57 +0530
Source: bisonc++
Binary: bisonc++ bisonc++-doc
Architecture: source amd64 all
Version: 5.00.01-1
Distribution: unstable
Urgency: low
Maintainer: Frank B. Brokken 
Changed-By: Frank B. Brokken 
Description:
 bisonc++   - Bison-style parser generator for C++
 bisonc++-doc - Bison-style parser generator for C++ documentation
Closes: 822410
Changes:
 bisonc++ (5.00.01-1) unstable; urgency=low
 .
   * Upstream fixed errors in the manual's .yo files introduced by yodl 3.07.01
 (Closes: #822410)
 .
   * Updated yodl's dependency (3.07.01) in 'debian/control'
Checksums-Sha1:
 0b9b42711c9e4515d7b29058b96e346fb635001e 2058 bisonc++_5.00.01-1.dsc
 d3c11d94139c6dceec43b10f28b0ca68b773719e 484420 bisonc++_5.00.01.orig.tar.gz
 be19946a65fa8d95950067088b0335db0e8da828 11960 bisonc++_5.00.01-1.debian.tar.xz
 4b6797a2e4d7e056a8e16ce483cd8e3827b2cd90 20156726 
bisonc++-dbgsym_5.00.01-1_amd64.deb
 8885489eed7a5703ce00b3c0e33169023d73ec95 218004 bisonc++-doc_5.00.01-1_all.deb
 9f483b369336e96786fddc866f1929d4630d922c 213874 bisonc++_5.00.01-1_amd64.deb
Checksums-Sha256:
 2daad67921a3d28db258f8e37114c0e3c9fc69789ea835e19c48da787c1d9c2e 2058 
bisonc++_5.00.01-1.dsc
 96395af80d5e124cd2c0e7886866d5d06c27908c0aa149a98748669bf3fce284 484420 
bisonc++_5.00.01.orig.tar.gz
 98ba353ab438b1c2a9f891d6a52eb1bb2e9b2873795ba62daa43e4b28365b487 11960 
bisonc++_5.00.01-1.debian.tar.xz
 bf2176b39d8dbc4091f6c27277048451b0ba4e0831fe691134db0ba0f3fb98c8 20156726 
bisonc++-dbgsym_5.00.01-1_amd64.deb
 0936de2dd0ea683d22189e0651cfde1bc483e1981cca3883009e22fce0cc1a3a 218004 
bisonc++-doc_5.00.01-1_all.deb
 c1f03f174cccf0251bcf8c916a9fa339ca402dddebc0b5c204f42498b714298c 213874 
bisonc++_5.00.01-1_amd64.deb
Files:
 6a74b7ee8a0cbc8ed1387bf79822527a 2058 devel optional bisonc++_5.00.01-1.dsc
 361373ace6b7e9234ae929adf5fa97b7 484420 devel optional 
bisonc++_5.00.01.orig.tar.gz
 049e4196b6159bfd7eb8a5d3f8954b41 11960 devel optional 
bisonc++_5.00.01-1.debian.tar.xz
 32338047918c84fdaffa3a31cdc3d6d6 

Processed: severity of 822651 is important

2016-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 822651 important
Bug #822651 [src:linux] linux-image-4.5.0-1-amd64: Spews into /dev/kmsg, 
causing unresponsive journald
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
822651: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822651
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#822651: linux-image-4.5.0-1-amd64: Spews into /dev/kmsg, causing unresponsive journald

2016-04-25 Thread Ben Longbons
Package: src:linux
Version: 4.5.1-1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

Apologies for not following the instructions to run the kernel while
reporting the bug, but the system was barely responsive enough for me to
extract any info.

Whenever my system is started with the 4.5 kernel, systemd-journald uses
about 120% CPU and still complains about dropping messages.

The 4.4 kernel works properly.

I managed to get coredumps of journald every 10 seconds for the whole
3-minute period it was allowed to run, but I doubt it will be useful
given the `dmesg` output.

-- Package-specific info:
** Kernel log: (manually saved from previous boot, limited lines because
just running `dmesg` would never stop).
[ 1686.225851] ACPI Error: No handler or method for GPE 13, disabling event 
(20160108/evgpe-790)
[ 1686.226059] ACPI Error: No handler or method for GPE 11, disabling event 
(20160108/evgpe-790)
[ 1686.226270] ACPI Error: No handler or method for GPE 11, disabling event 
(20160108/evgpe-790)
[ 1686.226289] ACPI Error: No handler or method for GPE 13, disabling event 
(20160108/evgpe-790)
[ 1686.226308] ACPI Error: No handler or method for GPE 15, disabling event 
(20160108/evgpe-790)
[ 1686.226317] ACPI Error: No handler or method for GPE 16, disabling event 
(20160108/evgpe-790)
[ 1686.226327] ACPI Error: No handler or method for GPE 17, disabling event 
(20160108/evgpe-790)
[ 1686.226346] ACPI Error: No handler or method for GPE 00, disabling event 
(20160108/evgpe-790)
[ 1686.226355] ACPI Error: No handler or method for GPE 01, disabling event 
(20160108/evgpe-790)
[ 1686.226364] ACPI Error: No handler or method for GPE 02, disabling event 
(20160108/evgpe-790)
[ 1686.226383] ACPI Error: No handler or method for GPE 04, disabling event 
(20160108/evgpe-790)
[ 1686.226401] ACPI Error: No handler or method for GPE 06, disabling event 
(20160108/evgpe-790)
[ 1686.226409] ACPI Error: No handler or method for GPE 07, disabling event 
(20160108/evgpe-790)
[ 1686.226427] ACPI Error: No handler or method for GPE 11, disabling event 
(20160108/evgpe-790)
[ 1686.226437] ACPI Error: No handler or method for GPE 12, disabling event 
(20160108/evgpe-790)
[ 1686.226456] ACPI Error: No handler or method for GPE 14, disabling event 
(20160108/evgpe-790)
[ 1686.226465] ACPI Error: No handler or method for GPE 15, disabling event 
(20160108/evgpe-790)
[ 1686.226473] ACPI Error: No handler or method for GPE 16, disabling event 
(20160108/evgpe-790)
[ 1686.226505] ACPI Error: No handler or method for GPE 00, disabling event 
(20160108/evgpe-790)
[ 1686.226514] ACPI Error: No handler or method for GPE 01, disabling event 
(20160108/evgpe-790)
[ 1686.226521] ACPI Error: No handler or method for GPE 02, disabling event 
(20160108/evgpe-790)
[ 1686.226528] ACPI Error: No handler or method for GPE 03, disabling event 
(20160108/evgpe-790)
[ 1686.226535] ACPI Error: No handler or method for GPE 04, disabling event 
(20160108/evgpe-790)
[ 1686.226555] ACPI Error: No handler or method for GPE 07, disabling event 
(20160108/evgpe-790)
[ 1686.226572] ACPI Error: No handler or method for GPE 11, disabling event 
(20160108/evgpe-790)
[ 1686.226587] ACPI Error: No handler or method for GPE 13, disabling event 
(20160108/evgpe-790)
[ 1686.226611] ACPI Error: No handler or method for GPE 16, disabling event 
(20160108/evgpe-790)
[ 1686.226639] ACPI Error: No handler or method for GPE 00, disabling event 
(20160108/evgpe-790)
[ 1686.226679] ACPI Error: No handler or method for GPE 04, disabling event 
(20160108/evgpe-790)
[ 1686.227005] ACPI Error: No handler or method for GPE 11, disabling event 
(20160108/evgpe-790)
[ 1686.227014] ACPI Error: No handler or method for GPE 12, disabling event 
(20160108/evgpe-790)
[ 1686.227022] ACPI Error: No handler or method for GPE 13, disabling event 
(20160108/evgpe-790)
[ 1686.227031] ACPI Error: No handler or method for GPE 14, disabling event 
(20160108/evgpe-790)
[ 1686.227051] ACPI Error: No handler or method for GPE 16, disabling event 
(20160108/evgpe-790)
[ 1686.227060] ACPI Error: No handler or method for GPE 17, disabling event 
(20160108/evgpe-790)
[ 1686.227082] ACPI Error: No handler or method for GPE 00, disabling event 
(20160108/evgpe-790)
[ 1686.227091] ACPI Error: No handler or method for GPE 01, disabling event 
(20160108/evgpe-790)
[ 1686.227098] ACPI Error: No handler or method for GPE 02, disabling event 
(20160108/evgpe-790)
[ 1686.227105] ACPI Error: No handler or method for GPE 03, disabling event 
(20160108/evgpe-790)
[ 1686.227125] ACPI Error: No handler or method for GPE 06, disabling event 
(20160108/evgpe-790)
[ 1686.227131] ACPI Error: No handler or method for GPE 07, disabling event 
(20160108/evgpe-790)
[ 1686.227148] ACPI Error: No handler or method for GPE 11, disabling event 
(20160108/evgpe-790)
[ 1686.227155] ACPI Error: No handler or method for GPE 12, disabling event 
(20160108/evgpe-790)
[ 1686.227171] ACPI Error: No handler 

Bug#822650: openmsx: FTBFS: error: no matching function for call to 'begin...

2016-04-25 Thread Martin Michlmayr
Package: openmsx
Version: 0.12.0-1
Severity: serious

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> Compiling RTScheduler.cc...
> g++ \
>-MP -MMD -MF derived/x86_64-linux-debian/dep/RTScheduler.d \
>   -o derived/x86_64-linux-debian/obj/RTScheduler.o  -g 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -O3   -m64 -pipe -std=c++11 -Wall -Wextra -Wundef 
> -Wno-invalid-offsetof -Wunused-macros -Wdouble-promotion 
> -Wmissing-declarations -Wno-missing-field-initializers -Isrc -Isrc/cassette 
> -Isrc/commands -Isrc/config -Isrc/console -Isrc/cpu -Isrc/debugger 
> -Isrc/events -Isrc/fdc -Isrc/file -Isrc/ide -Isrc/input -Isrc/laserdisc 
> -Isrc/memory -Isrc/resource -Isrc/security -Isrc/serial -Isrc/settings 
> -Isrc/sound -Isrc/thread -Isrc/utils -Isrc/video -Isrc/video/ld 
> -Isrc/video/scalers -Isrc/video/v9990 -Iderived/x86_64-linux-debian/config 
> -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/SDL 
> -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/tcl8.5-c src/RTScheduler.cc
> src/RTScheduler.cc: In member function 'bool 
> openmsx::RTScheduler::isPending(const openmsx::RTSchedulable&) const':
> src/RTScheduler.cc:33:38: error: no matching function for call to 
> 'begin(const openmsx::SchedulerQueue&)'
>   return std::find_if(std::begin(queue), std::end(queue),
>   ^
> In file included from /usr/include/c++/5/utility:75:0,
>  from /usr/include/c++/5/algorithm:60,
>  from src/utils/MemBuffer.hh:7,
>  from src/SchedulerQueue.hh:4,
>  from src/RTScheduler.hh:4,
>  from src/RTScheduler.cc:1:
> /usr/include/c++/5/initializer_list:89:5: note: candidate: template _Tp> constexpr const _Tp* std::begin(std::initializer_list<_Tp>)
>  begin(initializer_list<_Tp> __ils) noexcept
>  ^
> /usr/include/c++/5/initializer_list:89:5: note:   template argument 
> deduction/substitution failed:
> src/RTScheduler.cc:33:38: note:   
> 'openmsx::SchedulerQueue' is not derived from 
> 'std::initializer_list<_Tp>'
>   return std::find_if(std::begin(queue), std::end(queue),
>   ^
> src/RTScheduler.cc:33:55: error: no matching function for call to 'end(const 
> openmsx::SchedulerQueue&)'
>   return std::find_if(std::begin(queue), std::end(queue),
>^
> In file included from /usr/include/c++/5/utility:75:0,
>  from /usr/include/c++/5/algorithm:60,
>  from src/utils/MemBuffer.hh:7,
>  from src/SchedulerQueue.hh:4,
>  from src/RTScheduler.hh:4,
>  from src/RTScheduler.cc:1:
> /usr/include/c++/5/initializer_list:99:5: note: candidate: template _Tp> constexpr const _Tp* std::end(std::initializer_list<_Tp>)
>  end(initializer_list<_Tp> __ils) noexcept
>  ^
> /usr/include/c++/5/initializer_list:99:5: note:   template argument 
> deduction/substitution failed:
> src/RTScheduler.cc:33:55: note:   
> 'openmsx::SchedulerQueue' is not derived from 
> 'std::initializer_list<_Tp>'
>   return std::find_if(std::begin(queue), std::end(queue),
>^
> src/RTScheduler.cc:34:72: error: no matching function for call to 'end(const 
> openmsx::SchedulerQueue&)'
>   EqualRTSchedulable(schedulable)) != std::end(queue);
> ^
> In file included from /usr/include/c++/5/utility:75:0,
>  from /usr/include/c++/5/algorithm:60,
>  from src/utils/MemBuffer.hh:7,
>  from src/SchedulerQueue.hh:4,
>  from src/RTScheduler.hh:4,
>  from src/RTScheduler.cc:1:
> /usr/include/c++/5/initializer_list:99:5: note: candidate: template _Tp> constexpr const _Tp* std::end(std::initializer_list<_Tp>)
>  end(initializer_list<_Tp> __ils) noexcept
>  ^
> /usr/include/c++/5/initializer_list:99:5: note:   template argument 
> deduction/substitution failed:
> src/RTScheduler.cc:34:72: note:   
> 'openmsx::SchedulerQueue' is not derived from 
> 'std::initializer_list<_Tp>'
>   EqualRTSchedulable(schedulable)) != std::end(queue);
> ^
> build/main.mk:527: recipe for target 
> 'derived/x86_64-linux-debian/obj/RTScheduler.o' failed
> make[2]: *** [derived/x86_64-linux-debian/obj/RTScheduler.o] Error 1
> make[2]: Leaving directory '/<>'

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise



Bug#822498: marked as done (sysdig: FTBFS: error: 'log10' was not declared in this scope)

2016-04-25 Thread Debian Bug Tracking System
Your message dated Tue, 26 Apr 2016 00:49:46 +
with message-id 
and subject line Bug#822498: fixed in sysdig 0.9.0-1
has caused the Debian Bug report #822498,
regarding sysdig: FTBFS: error: 'log10' was not declared in this scope
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.)


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

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> cd /<>/obj-x86_64-linux-gnu/userspace/libsinsp && /usr/bin/c++   
> -DHAS_CAPTURE -DK8S_DISABLE_THREAD -DPLATFORM_NAME=\"Linux\" 
> -I/<>/userspace/libsinsp/. 
> -I/<>/userspace/libsinsp/../../common 
> -I/<>/userspace/libsinsp/../libscap -I/usr/include/jsoncpp 
> -I/usr/include/luajit-2.0  -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time 
> -D_FORTIFY_SOURCE=2  -Wall -ggdb --std=c++0x   -o 
> CMakeFiles/sinsp.dir/mesos_event_data.cpp.o -c 
> /<>/userspace/libsinsp/mesos_event_data.cpp
> /<>/userspace/libsinsp/filterchecks.cpp: In member function 
> 'virtual uint8_t* sinsp_filter_check_event::extract(sinsp_evt*, uint32_t*)':
> /<>/userspace/libsinsp/filterchecks.cpp:2768:40: error: 'log10' 
> was not declared in this scope
>  double llatency = log10((double)lat);
> ^
> /<>/userspace/libsinsp/cursesspectro.cpp: In member function 
> 'uint32_t curses_spectro::mkcol(uint64_t)':
> /<>/userspace/libsinsp/cursesspectro.cpp:237:53: error: 'log10' 
> was not declared in this scope
>   uint32_t col = log10((int)val * refresh_per_sec + 1) / log10(1.6);
>  ^
> /<>/userspace/libsinsp/cursesspectro.cpp: In member function 
> 'void curses_spectro::draw_axis()':
> /<>/userspace/libsinsp/cursesspectro.cpp:268:45: error: 'pow' 
> was not declared in this scope
> uint64_t aval = (uint64_t)pow(10, curtime);
>  ^
> /<>/userspace/libsinsp/cursesspectro.cpp: In member function 
> 'uint64_t curses_spectro::latency_from_coordinate(uint32_t)':
> /<>/userspace/libsinsp/cursesspectro.cpp:678:34: error: 'pow' 
> was not declared in this scope
>   return (uint64_t)pow(10, curtime);
>   ^

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: sysdig
Source-Version: 0.9.0-1

We believe that the bug you reported is fixed in the latest version of
sysdig, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 822...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Harlan Lieberman-Berg  (supplier of updated sysdig 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 25 Apr 2016 20:32:25 -0400
Source: sysdig
Binary: sysdig sysdig-dkms
Architecture: source amd64 all
Version: 0.9.0-1
Distribution: unstable
Urgency: medium
Maintainer: Evgeni Golov 
Changed-By: Harlan Lieberman-Berg 
Description:
 sysdig - system-level exploration and troubleshooting tool
 sysdig-dkms - system-level exploration and troubleshooting tool - kernel source
Closes: 822498
Changes:
 sysdig (0.9.0-1) unstable; urgency=medium
 .
   * New upstream release.
   * Add patch to fix FTBFS. (Closes: #822498)
   * Change email address to @debian.org.
   * Update d/copyright to reflect new OpenSSL exception
   * Bump S-V; no changes required.
Checksums-Sha1:
 4abaeda21fe9237d21f560a6eab57ae0500e2cfa 2261 sysdig_0.9.0-1.dsc
 aedcb2f892d91db35f2667e05e9c29e504270fb5 587404 sysdig_0.9.0.orig.tar.gz
 73077b0df0ec6064dede65223160b0caa64e86d8 5672 sysdig_0.9.0-1.debian.tar.xz
 40a3a7fa1deb67e9a0ca6346bf2802583aa4a074 18813890 
sysdig-dbgsym_0.9.0-1_amd64.deb
 60562eae456cb0763f854a758ba52805e4f47115 67314 sysdig-dkms_0.9.0-1_all.deb
 93b8848bf14d5c3edb10a472f689103a5508efbd 685004 sysdig_0.9.0-1_amd64.deb

Bug#807735: marked as done (gmpc-plugins: FTBFS: libmpd-internal.h:210:10: error: expected identifier or '(' before '__extension__')

2016-04-25 Thread Debian Bug Tracking System
Your message dated Tue, 26 Apr 2016 00:49:08 +
with message-id 
and subject line Bug#807735: fixed in gmpc-plugins 11.8.16-2.1
has caused the Debian Bug report #807735,
regarding gmpc-plugins: FTBFS: libmpd-internal.h:210:10: error: expected 
identifier or '(' before '__extension__'
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.)


-- 
807735: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807735
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gmpc-plugins
Version: 11.8.16-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

gmpc-plugins fails to build from source in unstable/amd64:

  [..]

  libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -pthread 
-I/usr/include/gmpc -I/usr/include/gtk-2.0 
-I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ 
-I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
-I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 
-I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/freetype2 
-I/usr/include/libxml2 -I/usr/include/libmpd-1.0/ -I./ 
-DDATA_DIR=\"/usr/share/gmpc/plugins/jamendo/\" -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -c jamendo.c  -fPIC -DPIC -o 
.libs/jamendoplugin_la-jamendo.o
  In file included from /usr/include/string.h:634:0,
   from jamendo.c:21:
  /usr/include/libmpd-1.0/libmpd/libmpd-internal.h:210:10: error: expected 
identifier or '(' before '__extension__'
   char *   strndup (const char *s, size_t n);
^
  jamendo.c: In function 'jamendo_db_load_data':
  jamendo.c:326:46: warning: pointer type mismatch in conditional expression
   (image != NULL)?image:""); 
^
  Makefile:479: recipe for target 'jamendoplugin_la-jamendo.lo' failed
  make[4]: *** [jamendoplugin_la-jamendo.lo] Error 1
  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20151212101533.VCTTVWszV2/gmpc-plugins-11.8.16/gmpc-jamendo/src'
  Makefile:428: recipe for target 'all-recursive' failed
  make[3]: *** [all-recursive] Error 1
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20151212101533.VCTTVWszV2/gmpc-plugins-11.8.16/gmpc-jamendo'
  Makefile:360: recipe for target 'all' failed
  make[2]: *** [all] Error 2
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20151212101533.VCTTVWszV2/gmpc-plugins-11.8.16/gmpc-jamendo'
  Makefile:416: recipe for target 'all-recursive' failed
  make[1]: *** [all-recursive] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151212101533.VCTTVWszV2/gmpc-plugins-11.8.16'
  dh_auto_build: make -j1 returned exit code 2
  debian/rules:9: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


gmpc-plugins.11.8.16-2.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: gmpc-plugins
Source-Version: 11.8.16-2.1

We believe that the bug you reported is fixed in the latest version of
gmpc-plugins, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 807...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Antoine Beaupré  (supplier of updated gmpc-plugins package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 15 Apr 2016 18:20:01 -0400
Source: gmpc-plugins
Binary: gmpc-plugins gmpc-plugins-dbg
Architecture: source amd64
Version: 11.8.16-2.1
Distribution: unstable
Urgency: medium
Maintainer: Etienne Millon 
Changed-By: Antoine Beaupré 
Description:
 gmpc-plugins - Plugins for the GNOME Music Player Client
 gmpc-plugins-dbg - Plugins 

Processed (with 1 error): Re: chromium-browser: Missing build dependency libgraphite2-dev

2016-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 822480
Bug #822480 [src:chromium-browser] chromium-browser: Missing build dependency 
libgraphite2-dev
Marked Bug as done
> merge 822480 822432
Bug #822480 {Done: Witold Baryluk } 
[src:chromium-browser] chromium-browser: Missing build dependency 
libgraphite2-dev
Unable to merge bugs because:
severity of #822432 is 'grave' not 'normal'
package of #822432 is 'libharfbuzz-dev' not 'src:chromium-browser'
severity of #822464 is 'grave' not 'normal'
package of #822464 is 'libharfbuzz-dev' not 'src:chromium-browser'
Failed to merge 822480: Did not alter merged bugs.

> stop
Stopping processing here.

Please contact me if you need assistance.
-- 
822432: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822432
822464: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822464
822480: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822480
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#822489: armhf ABI detection crashing ldconfig on arm64

2016-04-25 Thread Steve McIntyre
On Mon, Apr 25, 2016 at 09:57:00AM +0200, Aurelien Jarno wrote:
>On 2016-04-25 00:30, Steve McIntyre wrote:
>> Package: libc6-bin
>> Severity: serious
>> Version: 2.22-7
>> Tags: patch
>> 
>> Hi folks,
>> 
>> Steev has reported some crashing using ldconfig on arm64 systems with
>> armhf added as a secondary architecture - he's using this config in
>> Kali, for example.
>> 
>> Working through the problem with him on #debian-arm, I can see that
>> it's a problem with our/my patch for ARM ABI detection. On older
>> binaries that predate the new ABI flags in the ELF header, we're still
>> parsing the ARM attributes. That works fine on armel/armhf, but on
>> arm64 this code is being built wrongly using native (ELF64)
>> types. This patch is the obvious fix - enforce using ELF32 types for
>> all arches.
>
>You have the same code in unsubmitted-ldconfig-cache-abi.diff, so I
>guess it also have to be patched?

Ah, yes - good point. I'd not considered that yet. Hmmm, pondering
some more...

No, we're safe here. In *that* case, we're running inside the armhf
(or armel) version of ld.so, *not* in the arm64 version. There's no
problem there. Does that make sense to you?

>> It seems that we still have some older packages without the ABI flags
>> attached - libshout3 is one such. :-(
>
>Frankly we are keeping "temporary" hacks for quite too long on armhf. I
>would like to drop the following patches after the Stretch release:
>
>- local-soname-hack.diff

Can go away easily I think, yes. The old soname should already be
history now.

>- unsubmitted-ldconfig-cache-abi.diff

Should go away after stretch, agreed.

>- unsubmitted-ldso-abi-check.diff
>- unsubmitted-ldso-multilib.diff

U. I don't think these two can go away *at all* without breaking
multi-arch on ARM.

The first one could do with updating to use the new ARM ABI float
flags in preference to the old, slow ARM attributes scan (as an
optimisation), but the concept isn't going to change.

The second one is also necessary to deal with finding two different
float ABIs in the ld.so cache.

>Could you please ensure that all the binaries in the archive that still
>needs these patches are rebuilt?

I'll look again for broken/old stuff. I thought you'd already pushed
binNMUs for everything outstanding, though??

Also: the 

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Is there anybody out there?



Bug#817954: Keep Firefox out of Debian releases

2016-04-25 Thread Francesco
Source: firefox
Followup-For: Bug #817954

Dear Maintainer,

If possible it would be nice to have firefox (release version,
not esr) in stretch/testing without adding unstable repository;
maybe can be added a section in the repository used for stable too.



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)



Bug#822474: marked as done (mira: FTBFS: error: 'accumulate' is not a member of 'std')

2016-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2016 22:29:49 +
with message-id 
and subject line Bug#822474: fixed in mira 4.9.5-6
has caused the Debian Bug report #822474,
regarding mira: FTBFS: error: 'accumulate' is not a member of 'std'
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.)


-- 
822474: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822474
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mira
Version: 4.9.5-5
Severity: serious

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> g++ -DPACKAGE_NAME=\"mira\" -DPACKAGE_TARNAME=\"mira\" 
> -DPACKAGE_VERSION=\"4.9.5_2\" -DPACKAGE_STRING=\"mira\ 4.9.5_2\" 
> -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"mira\" 
> -DVERSION=\"4.9.5_2\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 
> -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 
> -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 
> -DENABLE64=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DYYTEXT_POINTER=1 
> -DSTDC_HEADERS=1 -DHAVE__BOOL=1 -DHAVE_STDBOOL_H=1 -Drestrict=__restrict 
> -DHAVE_STDLIB_H=1 -DHAVE_MALLOC=1 -DHAVE_STDLIB_H=1 -DHAVE_REALLOC=1 
> -DLSTAT_FOLLOWS_SLASHED_SYMLINK=1 -DHAVE_STRFTIME=1 -DHAVE_MEMSET=1 
> -DHAVE_FSEEKO=1 -DHAVE_ISBLANK=1 -DHAVE_BOOST=/\*\*/ 
> -DHAVE_BOOST_THREAD=/\*\*/ -DHAVE_BOOST_REGEX=/\*\*/ 
> -DHAVE_BOOST_SYSTEM=/\*\*/ -DHAVE_BOOST_FILESYSTEM=/\*\*/ 
> -DHAVE_BOOST_IOSTREAMS=/\*\*/ -DHAVE_LIBRT=1 -DHAVE_GZOFFSET=1 
> -DBOUNDTRACKFLAG=1 -DBUGTRACKFLAG=1 -I.  -I../../src  -Wdate-time 
> -D_FORTIFY_SOURCE=2  -D
> PUBLICQUIET -DAJ_Linux64 -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security  -I/usr/include -O3 -funroll-loops -pthread 
> -I/usr/include -I/usr/include -Werror=uninitialized -Werror=return-type 
> -Werror=parentheses -Werror=unused-value -std=c++14 -c -o parameters.o 
> parameters.C
> read.C: In member function 'void Read::dumpAsReadname(std::ostream&)':
> read.C:1262:33: warning: format '%x' expects argument of type 'unsigned int', 
> but argument 3 has type 'Read*' [-Wformat=]
>sprintf(buffer, "%x", this) ;
>  ^
> read.C: In member function 'void Read::dumpAsFASTA(std::ostream&, bool, bool, 
> bool)':
> read.C:1293:33: warning: format '%x' expects argument of type 'unsigned int', 
> but argument 3 has type 'Read*' [-Wformat=]
>sprintf(buffer, "%x", this) ;
>  ^
> read.C: In member function 'void Read::dumpAsFASTQ(std::ostream&, bool, bool, 
> bool)':
> read.C:1377:33: warning: format '%x' expects argument of type 'unsigned int', 
> but argument 3 has type 'Read*' [-Wformat=]
>sprintf(buffer, "%x", this) ;
>  ^
> read.C: In member function 'void Read::dumpAsFASTAQual(std::ostream&, bool, 
> bool, bool)':
> read.C:1478:33: warning: format '%x' expects argument of type 'unsigned int', 
> but argument 3 has type 'Read*' [-Wformat=]
>sprintf(buffer, "%x", this) ;
>  ^
> read.C: In member function 'void Read::dumpAsCAF(std::ostream&)':
> read.C:1550:33: warning: format '%x' expects argument of type 'unsigned int', 
> but argument 3 has type 'Read*' [-Wformat=]
>sprintf(buffer, "%x", this) ;
>  ^
> read.C: In member function 'void Read::dumpAsMAF(std::ostream&)':
> read.C:1968:33: warning: format '%x' expects argument of type 'unsigned int', 
> but argument 3 has type 'Read*' [-Wformat=]
>sprintf(buffer, "%x", this) ;
>  ^
> contig_consensus.C: In member function 'void 
> Contig::makeIntelligentConsensus(std::__cxx11::string&, std::vector char>&, std::vector*, int32, int32, int32, int32, base_quality_t, char, 
> bool, bool, bool)':
> contig_consensus.C:2144:22: error: 'accumulate' is not a member of 'std'
>auto 
> sumcounts=std::accumulate(countsofpossiblebases.begin(),countsofpossiblebases.end(),0);
>   ^
> g++ -DPACKAGE_NAME=\"mira\" -DPACKAGE_TARNAME=\"mira\" 
> -DPACKAGE_VERSION=\"4.9.5_2\" -DPACKAGE_STRING=\"mira\ 4.9.5_2\" 
> -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"mira\" 
> -DVERSION=\"4.9.5_2\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 
> -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 
> -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 
> -DENABLE64=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DYYTEXT_POINTER=1 
> -DSTDC_HEADERS=1 

Bug#822242: marked as done (libgd2: CVE-2016-3074: Signedness vulnerability causing heap overflow)

2016-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2016 22:19:39 +
with message-id 
and subject line Bug#822242: fixed in libgd2 2.0.36~rc1~dfsg-6.1+deb7u2
has caused the Debian Bug report #822242,
regarding libgd2: CVE-2016-3074: Signedness vulnerability causing heap overflow
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.)


-- 
822242: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822242
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgd2
Version: 2.1.1-4
Severity: grave
Tags: security upstream patch fixed-upstream

Hi,

the following vulnerability was published for libgd2.

CVE-2016-3074[0]:
Signedness vulnerability causing heap overflow

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-3074
[1] 
https://github.com/libgd/libgd/commit/2bb97f407c1145c850416a3bfbcc8cf124e68a19

Please adjust the affected versions in the BTS as needed.

Salvatore
--- End Message ---
--- Begin Message ---
Source: libgd2
Source-Version: 2.0.36~rc1~dfsg-6.1+deb7u2

We believe that the bug you reported is fixed in the latest version of
libgd2, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 822...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated libgd2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 23 Apr 2016 11:39:20 +0200
Source: libgd2
Binary: libgd-tools libgd2-xpm-dev libgd2-noxpm-dev libgd2-xpm libgd2-noxpm
Architecture: source amd64
Version: 2.0.36~rc1~dfsg-6.1+deb7u2
Distribution: wheezy-security
Urgency: high
Maintainer: GD team 
Changed-By: Salvatore Bonaccorso 
Description: 
 libgd-tools - GD command line tools and example code
 libgd2-noxpm - GD Graphics Library version 2 (without XPM support)
 libgd2-noxpm-dev - GD Graphics Library version 2 (development version)
 libgd2-xpm - GD Graphics Library version 2
 libgd2-xpm-dev - GD Graphics Library version 2 (development version)
Closes: 822242
Changes: 
 libgd2 (2.0.36~rc1~dfsg-6.1+deb7u2) wheezy-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * CVE-2016-3074: Signedness vulnerability causing heap overflow
 (Closes: #822242)
Checksums-Sha1: 
 619c3503f0e67cc84665423e1dc7169f99bdfec0 2411 
libgd2_2.0.36~rc1~dfsg-6.1+deb7u2.dsc
 090329d88b9b028f5ab65f9c92f7b96daa8f5ab7 28717 
libgd2_2.0.36~rc1~dfsg-6.1+deb7u2.debian.tar.gz
 8d681d996b1a1606b8f80e895e94f5ec23648845 169556 
libgd-tools_2.0.36~rc1~dfsg-6.1+deb7u2_amd64.deb
 70f5628e1247004304f36fb07a2e52e8120a7fa3 374904 
libgd2-xpm-dev_2.0.36~rc1~dfsg-6.1+deb7u2_amd64.deb
 7d3da06d94fa42160c5beb99b6c81572ff5a2d4c 372156 
libgd2-noxpm-dev_2.0.36~rc1~dfsg-6.1+deb7u2_amd64.deb
 2c038c10404b049adc852c84575b2feba7d7b337 233568 
libgd2-xpm_2.0.36~rc1~dfsg-6.1+deb7u2_amd64.deb
 868001e4c47528bfcfebd11ccaf45a206b5064e7 231158 
libgd2-noxpm_2.0.36~rc1~dfsg-6.1+deb7u2_amd64.deb
Checksums-Sha256: 
 8c3d01be1f7528a164efe063c8df17e869a9a6b3c9ca0e786f3671d09100ea8d 2411 
libgd2_2.0.36~rc1~dfsg-6.1+deb7u2.dsc
 f32001406f86bda78f5a194457c9d7107ad7a4a141d3305067448918653c05d5 28717 
libgd2_2.0.36~rc1~dfsg-6.1+deb7u2.debian.tar.gz
 43f80cf1a9b9b11df62609b2ad95932f61dbee6614adb483dbccca72d12f2e13 169556 
libgd-tools_2.0.36~rc1~dfsg-6.1+deb7u2_amd64.deb
 552f54c73b0037cbabb36eb86d235dd968e140affeb10010f629b06d6aaf7c8d 374904 
libgd2-xpm-dev_2.0.36~rc1~dfsg-6.1+deb7u2_amd64.deb
 ee8500868c8d83ba49454b9439a73654e188d030cb3880745bab33483b34ba6a 372156 
libgd2-noxpm-dev_2.0.36~rc1~dfsg-6.1+deb7u2_amd64.deb
 1eb39b4cfbf297fe7cc6276ef03d9eb1ed642c21e38335067ee8478a7f7ca184 233568 
libgd2-xpm_2.0.36~rc1~dfsg-6.1+deb7u2_amd64.deb
 eb0a541721592ca50f585883db003c5e9b27b5207c62b66110ed5fcedc72397a 231158 
libgd2-noxpm_2.0.36~rc1~dfsg-6.1+deb7u2_amd64.deb
Files: 
 3b496b087c4391d947191bad5db23f9a 2411 graphics optional 
libgd2_2.0.36~rc1~dfsg-6.1+deb7u2.dsc
 

Bug#822369: xfsprogs: FTBFS: error: redefinition of 'struct fsxattr'

2016-04-25 Thread Dave Chinner
On Sat, Apr 23, 2016 at 02:08:31PM -0700, Martin Michlmayr wrote:
> Package: xfsprogs
> Version: 4.3.0+nmu1
> Severity: serious
> 
> This package fails to build in unstable:
> 
> > sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
> ...
> > [CC] fiemap.o
> > In file included from ../include/xfs.h:58:0,
> >  from io.h:19,
> >  from fiemap.c:24:
> > ../include/xfs/xfs_fs.h:42:8: error: redefinition of 'struct fsxattr'
> >  struct fsxattr {
> > ^
> > In file included from fiemap.c:22:0:
> > /usr/include/linux/fs.h:155:8: note: originally defined here
> >  struct fsxattr {
> > ^
> > ../include/buildrules:59: recipe for target 'fiemap.o' failed
> > make[3]: *** [fiemap.o] Error 1
> > include/buildrules:35: recipe for target 'io' failed

Kernel uapi change in 4.5 caused it. Upgrade to xfsprogs 4.5.0.

Cheers,

Dave.
-- 
Dave Chinner
da...@fromorbit.com



Bug#822518: closing 822518

2016-04-25 Thread Laurent Bigonville
close 822518 2.5-1
thanks

Hi,

This seems fixed with the latest version of libsemanage.

This was probably related to the upload of libsepol 2.5

Closing this bug.

Cheers,

Laurent Bigonville



Processed: closing 822518

2016-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 822518 2.5-1
Bug #822518 [libsemanage] libsemanage: FTBFS: error: too many arguments to 
function 'cil_userprefixes_to_string'
There is no source info for the package 'libsemanage' at version '2.5-1' with 
architecture ''
Unable to make a source version for version '2.5-1'
Marked as fixed in versions 2.5-1.
Bug #822518 [libsemanage] libsemanage: FTBFS: error: too many arguments to 
function 'cil_userprefixes_to_string'
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
822518: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#820531: marked as done (yafc: FTBFS: m4/glib-gettext.m4:39: error: m4_copy: won't overwrite defined macro: glib_DEFUN)

2016-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2016 21:52:45 +
with message-id 
and subject line Bug#820531: fixed in yafc 1.3.7-2
has caused the Debian Bug report #820531,
regarding yafc: FTBFS: m4/glib-gettext.m4:39: error: m4_copy: won't overwrite 
defined macro: glib_DEFUN
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.)


-- 
820531: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820531
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yafc
Version: 1.3.7-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

yafc fails to build from source in unstable/amd64:

  [..]

  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'yafc-build-deps' in 
'../yafc-build-deps_1.3.7-1_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package yafc-build-deps.
  (Reading database ... 22985 files and directories currently installed.)
  Preparing to unpack yafc-build-deps_1.3.7-1_all.deb ...
  Unpacking yafc-build-deps (1.3.7-1) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
autoconf-archive comerr-dev krb5-multidev libbsd-dev libedit-dev libedit2
libelf1 libglib2.0-bin libglib2.0-data libglib2.0-dev libgssrpc4
libkadm5clnt-mit9 libkadm5srv-mit9 libkdb5-8 libkrb5-dev libpcre16-3
libpcre3-dev libpcre32-3 libpcrecpp0v5 libssh-4 libssh-dev libssl-dev
libtext-unidecode-perl libtinfo-dev libxml-libxml-perl
libxml-namespacesupport-perl libxml-sax-base-perl libxml-sax-perl pkg-config
tex-common texinfo ucf zlib1g-dev
  Suggested packages:
doc-base krb5-doc libglib2.0-doc krb5-user libssh-doc texlive-base
texlive-latex-base texlive-generic-recommended texinfo-doc-nonfree
  Recommended packages:
libssl-doc libxml-sax-expat-perl
  The following NEW packages will be installed:
autoconf-archive comerr-dev krb5-multidev libbsd-dev libedit-dev libedit2
libelf1 libglib2.0-bin libglib2.0-data libglib2.0-dev libgssrpc4
libkadm5clnt-mit9 libkadm5srv-mit9 libkdb5-8 libkrb5-dev libpcre16-3
libpcre3-dev libpcre32-3 libpcrecpp0v5 libssh-4 libssh-dev libssl-dev
libtext-unidecode-perl libtinfo-dev libxml-libxml-perl
libxml-namespacesupport-perl libxml-sax-base-perl libxml-sax-perl pkg-config
tex-common texinfo ucf zlib1g-dev
  0 upgraded, 33 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 14.7 MB of archives.
  After this operation, 56.7 MB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 autoconf-archive all 
20150925-1 [688 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 
libtext-unidecode-perl all 1.27-1 [103 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 
libxml-namespacesupport-perl all 1.11-1 [14.8 kB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 libxml-sax-base-perl 
all 1.07-1 [23.1 kB]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 ucf all 3.0036 [70.2 
kB]
  Get:6 http://httpredir.debian.org/debian sid/main amd64 libxml-sax-perl all 
0.99+dfsg-2 [68.3 kB]
  Get:7 http://httpredir.debian.org/debian sid/main amd64 libxml-libxml-perl 
amd64 2.0123+dfsg-1+b1 [340 kB]
  Get:8 http://httpredir.debian.org/debian sid/main amd64 tex-common all 6.05 
[564 kB]
  Get:9 http://httpredir.debian.org/debian sid/main amd64 texinfo amd64 
6.1.0.dfsg.1-5 [1263 kB]
  Get:10 http://httpredir.debian.org/debian sid/main amd64 libbsd-dev amd64 
0.8.2-1 [177 kB]
  Get:11 http://httpredir.debian.org/debian sid/main amd64 libedit2 amd64 
3.1-20150325-1+b1 [85.2 kB]
  Get:12 http://httpredir.debian.org/debian sid/main amd64 libtinfo-dev amd64 
6.0+20160319-1 [77.6 kB]
  Get:13 http://httpredir.debian.org/debian sid/main amd64 libedit-dev amd64 
3.1-20150325-1+b1 [101 kB]
  Get:14 http://httpredir.debian.org/debian sid/main amd64 libelf1 amd64 
0.165-3 [169 kB]
  Get:15 http://httpredir.debian.org/debian sid/main amd64 libglib2.0-data all 
2.48.0-1 [2494 kB]
  Get:16 http://httpredir.debian.org/debian 

Bug#818033: marked as done (Useless in Debian)

2016-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2016 21:49:48 +
with message-id 
and subject line Bug#818033: fixed in php-nette 2.3.10-1
has caused the Debian Bug report #818033,
regarding Useless in Debian
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.)


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


[ Filled as an RC-bug by the maintainer to see the package auto-removed
  from testing, and not let it block the PHP 7.0 transition. ]

I packaged php-nette as used by php-apigen in order to build
php-opencloud(-doc), as used by owncloud, but owncloud is going away,
see #816376 (so is php-apigen, see #816796). There is a priori little
point to ship php-apigen in the next Debian stable release.

I intend to follow up with an RM request in a few months if nobody
objects (but feel free to beat me to it).

Regards

David


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: php-nette
Source-Version: 2.3.10-1

We believe that the bug you reported is fixed in the latest version of
php-nette, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 818...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Florian Schlichting  (supplier of updated php-nette package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 25 Apr 2016 22:47:15 +0200
Source: php-nette
Binary: php-nette
Architecture: source all
Version: 2.3.10-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: Florian Schlichting 
Description:
 php-nette  - Nette Framework
Closes: 818033 821599
Changes:
 php-nette (2.3.10-1) unstable; urgency=medium
 .
   * Import Upstream version 2.3.10
   * Refresh patch
   * Update to PHP7.0 dependencies (Closes: #821599, LP: #1544352)
   * Use secure VCS URIs
   * Add myself to Uploaders and remove David as requested (Closes: #818033)
   * Declare compliance with Debian Policy 3.9.8
   * Update upstream changelog
Checksums-Sha1:
 97e595c7ce301a86a081477c9d52091d2ab1c8ca 1910 php-nette_2.3.10-1.dsc
 2809bbdcd0c72054e31c7b9ac3558e983141ef99 406154 php-nette_2.3.10.orig.tar.gz
 0792b9a58e3dc77e90ca2ef9e4c36b32ccfe1baa 30724 php-nette_2.3.10-1.debian.tar.xz
 e41164a55cebf4e97cc3e71a2ad159ba70d8d88d 348650 php-nette_2.3.10-1_all.deb
Checksums-Sha256:
 6ee96b76b3a35316318d42ffd2eaf41b16bf73eac56c506b40d1c59fec5225b8 1910 
php-nette_2.3.10-1.dsc
 63e03badd2bcf42a261b9352b465dddcacb531793362d2bcfd6b11e499db6db9 406154 
php-nette_2.3.10.orig.tar.gz
 faf904bd26ee873d619ddc991d08d292d3eb759a214b976cf25487e570fa0d23 30724 
php-nette_2.3.10-1.debian.tar.xz
 ea6e51e37b270685919efd289572769087f03b4f2470c50356ef85207d664978 348650 
php-nette_2.3.10-1_all.deb
Files:
 00552eb540d41580db4acc6c2f166b48 1910 php optional php-nette_2.3.10-1.dsc
 9e545856bdd5127842b74831cb8462a2 406154 php optional 
php-nette_2.3.10.orig.tar.gz
 2248d6a5d6076773c5b2ad7dd68f843a 30724 php optional 
php-nette_2.3.10-1.debian.tar.xz
 246d29ea1311724b28229cd6910de758 348650 php optional php-nette_2.3.10-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXHoLzAAoJEBKXO25y3Ae1+ikP/RePdJH7W4tdW93L9/GjnATr
yWLrQg/iErvCOYWS+UINDCa/crGYe10THScvi4vR3BZ97EwbAixtFnmx63o+aJ0i
fxw84yK60kj0F3v4Pr/54iXfy9rJuliSNrW6qRnQQaRKePoJvr5TcnspxbOgd6X2
ks92jjKjUxHqKoE133PNkKM3gLvsJTOnpQ4O3Mge+eihVEoDYlSum86sVUmHqbLU
HEUpY9AuUwwlNP9xsgmE/sDsqtJ7eH+2kA6crFLG0xQHfFG7Jva9BRqwX+7V5Zr2
69e9PJX1lesQGLYyMtwUzTy5K6tE2VcvuKWBlHEmhFwoztC0KIy+DbQBYUrF9pUu
89qsEI1TU5UuwppY4Uv7RxLAefQmlugWFzY3Zb7az9DSWGXtOC3GhGFRW24YBvVK
+fH6FFafvMl1HXBb8QixjPL4oQ+f9EevNd6LIbpmr0UGuLuC6wiMJg64s/eIOdjS
llol0gaa1jYsOEWVJV7Yid8YBGlu0Sjzcy9HoEsqfQV3aOR0b8X75otHdEWsKdw4
319iaB5hQrEg+04mapVqwjEhJRAhQhBfBZ74f1yXwVVDTgsKdJVMojKr6Kng5NW4
/fj+KQrC17bNWyPa1R0AMgdbxcj++Yd4aLc5y2qMw4NG2tNeuw7xZf4hWJsAmUjx
ATFrRf8JAsk+Qbh71vc7
=90nk
-END PGP SIGNATURE End Message ---


Bug#822397: FTBFS: configure: error: "Some plugins are missing dependencies

2016-04-25 Thread Sebastian Harl
Hi,

On Sat, Apr 23, 2016 at 06:35:37PM -0700, Martin Michlmayr wrote:
> This package fails to build in unstable:

Thanks for reporting this!

> > iptables  . . . . . . no (dependency error)
> 
> ^

Here's the underlying problem (from config.log):

  configure:21357: checking libiptc/libiptc.h usability
  configure:21357: x86_64-linux-gnu-gcc -c -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wno-error=deprecated-declarations 
-Wdate-time -D_FORTIFY_SOURCE=2 -I/<>/debian/include -UCONFIGFILE -
  DCONFIGFILE='"/etc/collectd/collectd.conf"'  conftest.c >&5
  In file included from /usr/include/libiptc/ipt_kernel_headers.h:13:0,
   from /usr/include/libiptc/libiptc.h:6,
   from conftest.c:230:
  /usr/include/linux/if.h:71:2: error: redeclaration of enumerator 'IFF_UP'
IFF_UP= 1<<0,  /* sysfs */
^
  /usr/include/net/if.h:44:5: note: previous definition of 'IFF_UP' was here
   IFF_UP = 0x1,  /* Interface is up.  */

This is one of the usual sort of kernel header problems :-/
Not sure yet what the right solution would be.

Cheers,
Sebastian

-- 
Sebastian "tokkee" Harl +++ GnuPG-ID: 0x2F1FFCC7 +++ http://tokkee.org/

Those who would give up Essential Liberty to purchase a little Temporary
Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin



signature.asc
Description: Digital signature


Bug#822397: FTBFS: configure: error: "Some plugins are missing dependencies

2016-04-25 Thread Martin Michlmayr
* Sebastian Harl  [2016-04-25 23:06]:
>   /usr/include/linux/if.h:71:2: error: redeclaration of enumerator 'IFF_UP'
> IFF_UP= 1<<0,  /* sysfs */
> ^
>   /usr/include/net/if.h:44:5: note: previous definition of 'IFF_UP' was here
>IFF_UP = 0x1,  /* Interface is up.  */
> 
> This is one of the usual sort of kernel header problems :-/
> Not sure yet what the right solution would be.

I filed some other bugs about this issue.  I asked if someone can
investigate, so you could just monitor the other bugs, and possibly
reassign yours when they do. :)

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822396#10

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise



Bug#822637: uninstallable in sid, incompatible with GNOME 3.20

2016-04-25 Thread Sébastien Villemot
Package: gnome-shell-timer
Version: 0.3.12+20140924-3
Severity: serious

Dear Maintainer,

gnome-shell-timer is currently uninstallable in sid, since it depends on
gnome-shell << 3.19. It should be made compatible with GNOME 3.20.

In my experience, it is just a matter of updating the dependencies (the applet
works fine otherwise).

Thanks!

-- 
 .''`.Sébastien Villemot
: :' :Debian Developer
`. `' http://sebastien.villemot.name
  `-  GPG Key: 4096R/381A7594


signature.asc
Description: PGP signature


Processed: Re: Bug#718309: python-irclib: duplicate of python-irc

2016-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 718309 ftp.debian.org
Bug #718309 [python-irclib] python-irclib: duplicate of python-irc
Bug reassigned from package 'python-irclib' to 'ftp.debian.org'.
No longer marked as found in versions python-irclib/0.4.8-1.1.
Ignoring request to alter fixed versions of bug #718309 to the same values 
previously set
> retitle 718309 RM: python-irclib: Obsolete
Bug #718309 [ftp.debian.org] python-irclib: duplicate of python-irc
Changed Bug title to 'RM: python-irclib: Obsolete' from 'python-irclib: 
duplicate of python-irc'.
> severity 718309 normal
Bug #718309 [ftp.debian.org] RM: python-irclib: Obsolete
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
718309: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718309
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#718309: python-irclib: duplicate of python-irc

2016-04-25 Thread Moritz Mühlenhoff
reassign 718309 ftp.debian.org
retitle 718309 RM: python-irclib: Obsolete
severity 718309 normal
thanks

On Thu, Aug 08, 2013 at 03:40:03PM +0200, Margarita Manterola wrote:
> Hi,
> 
> On Tue, Jul 30, 2013 at 12:27 AM, Oxan van Leeuwen
>  wrote:
> > This package is an old version of the python-irc package.
> 
> Indeed, this seems to be the case.  However, I don't think it was
> intentional.  Upstream was renamed from irclib to irc, and I think
> it's likely that it was not noticed by the maintainer of python-irc
> that python-irclib was actually the old version of the same package.
> 
> > Given that the other package is actively maintained and this package hasn't
> > received a single maintainer upload since 2008, I suggest this package is
> > dropped from Debian once all reverse depends are updated to use python-irc.
> 
> Right.  For this to happen, we need to file bugs against each of the
> packages that depend on python-irclib:
> 
> jabber-irc: jabber-irc
> python-cobe: python-cobe
> xpilot-ng: xpilot-ng-common
> 
> All these packages require bugs in order to get fixed and only then
> can python-irclib get removed.

The reverse dependencies have been fixed or removed. Reassigning to
ftp.debian.org for removal.

Cheers,
Moritz



Bug#822513: marked as done (bochs: FTBFS: fatal error: gtk/gtk.h: No such file or directory)

2016-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2016 13:53:33 -0700
with message-id <20160425205333.gd13...@jirafa.cyrius.com>
and subject line Working now
has caused the Debian Bug report #822513,
regarding bochs: FTBFS: fatal error: gtk/gtk.h: No such file or directory
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.)


-- 
822513: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822513
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bochs
Version: 2.6-5
Severity: serious

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -I.. -I./.. -I../iodev -I./../iodev 
> -I../instrument/stubs -I./../instrument/stubs -Wall -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -pthread
> -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT 
> -I/usr/lib/x86_64-linux-gnu/wx/include/gtk2-unicode-3.0 -I/usr/include/wx-3.0 
> -D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__ -pthread  
> gtk_enh_dbg_osdep.cc -o gtk_enh_dbg_osdep.o
> gtk_enh_dbg_osdep.cc:19:21: fatal error: gtk/gtk.h: No such file or directory
> compilation terminated.
> Makefile:105: recipe for target 'gtk_enh_dbg_osdep.o' failed
> make[2]: *** [gtk_enh_dbg_osdep.o] Error 1
> make[2]: Leaving directory '/<>/gui'

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
This was caused by a bug in harfbuzz which got fixed in the meantime.

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise--- End Message ---


Bug#803835: libextractor: diff for NMU version 1:1.3-3.1

2016-04-25 Thread Sebastian Ramacher
Hi Bertrand

On 2016-04-25 22:40:47, Bertrand Marc wrote:
> Hello,
> 
> Thank you for your work. I also prepared a new version, with a patch
> taken from upstream (attached). I should be able to prepare the package
> tomorrow, but I will only upload it to mentors since I don't have
> uploading rights.
> 
> Please consider sponsoring my forthcoming upload.

Feel free to send me a link to the dsc once the package is ready.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature


Bug#803835: libextractor: diff for NMU version 1:1.3-3.1

2016-04-25 Thread Bertrand Marc
Hello,

Thank you for your work. I also prepared a new version, with a patch
taken from upstream (attached). I should be able to prepare the package
tomorrow, but I will only upload it to mentors since I don't have
uploading rights.

Please consider sponsoring my forthcoming upload.

Regards,
Bertrand

Le 25/04/2016 19:40, Sebastian Ramacher a écrit :
> Control: tags 803835 + pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for libextractor (versioned as 1:1.3-3.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
> 
> Regards.
> 

Description: update to new API in FFmpeg 2.9, fix FTBS
Origin: upstream
Applied-Upstream: commit: r35548:r35549 and r36975
--- a/src/plugins/thumbnailffmpeg_extractor.c
+++ b/src/plugins/thumbnailffmpeg_extractor.c
@@ -59,6 +59,20 @@
 #include 
 #endif
 
+#if USE_JPEG
+#ifdef PIX_FMT_YUVJ420P
+#define PIX_OUTPUT_FORMAT PIX_FMT_YUVJ420P
+#else
+#define PIX_OUTPUT_FORMAT AV_PIX_FMT_YUVJ420P
+#endif
+#else
+#ifdef PIX_FMT_RGB24
+#define PIX_OUTPUT_FORMAT PIX_FMT_RGB24
+#else
+#define PIX_OUTPUT_FORMAT AV_PIX_FMT_RGB24
+#endif
+#endif
+
 /**
  * Set to 1 to enable debug output.
  */ 
@@ -153,7 +167,7 @@
 static size_t 
 create_thumbnail (int src_width, int src_height, 
 		  int src_stride[],
-		  enum PixelFormat src_pixfmt, 
+		  enum AVPixelFormat src_pixfmt, 
 		  const uint8_t * const src_data[],
 		  int dst_width, int dst_height,
 		  uint8_t **output_data, 
@@ -189,7 +203,8 @@
   if (NULL == 
   (scaler_ctx =
sws_getContext (src_width, src_height, src_pixfmt,
-		   dst_width, dst_height, PIX_FMT_RGB24, 
+		   dst_width, dst_height,
+		   PIX_OUTPUT_FORMAT, 
 		   SWS_BILINEAR, NULL, NULL, NULL)))
 {
 #if DEBUG
@@ -199,7 +214,12 @@
   return 0;
 }
 
-  if (NULL == (dst_frame = avcodec_alloc_frame ()))
+#if LIBAVCODEC_VERSION_INT >= AV_VERSION_INT(55,28,1)
+  dst_frame = av_frame_alloc ();
+#else
+  dst_frame = avcodec_alloc_frame();
+#endif
+  if (NULL == dst_frame)
 {
 #if DEBUG
   fprintf (stderr,
@@ -209,18 +229,24 @@
   return 0;
 }
   if (NULL == (dst_buffer =
-	   av_malloc (avpicture_get_size (PIX_FMT_RGB24, dst_width, dst_height
+	   av_malloc (avpicture_get_size (PIX_OUTPUT_FORMAT,
+  dst_width, dst_height
 {
 #if DEBUG
   fprintf (stderr,
"Failed to allocate the destination image buffer\n");
 #endif
-  av_free (dst_frame);
+#if LIBAVCODEC_VERSION_INT >= AV_VERSION_INT(55,28,1)
+  av_frame_free (_frame);
+#else
+  avcodec_free_frame (_frame);
+#endif
   sws_freeContext (scaler_ctx);
   return 0;
 }
   avpicture_fill ((AVPicture *) dst_frame, dst_buffer,
-  PIX_FMT_RGB24, dst_width, dst_height);
+  PIX_OUTPUT_FORMAT,
+  dst_width, dst_height);
   sws_scale (scaler_ctx,
  src_data, 
  src_stride,
@@ -236,7 +262,11 @@
"Failed to allocate the encoder output buffer\n");
 #endif
   av_free (dst_buffer);
-  av_free (dst_frame);
+#if LIBAVCODEC_VERSION_INT >= AV_VERSION_INT(55,28,1)
+  av_frame_free (_frame);
+#else
+  avcodec_free_frame (_frame);
+#endif
   sws_freeContext (scaler_ctx);
   return 0;
 }
@@ -249,13 +279,17 @@
 #endif
   av_free (encoder_output_buffer);
   av_free (dst_buffer);
-  av_free (dst_frame);
+#if LIBAVCODEC_VERSION_INT >= AV_VERSION_INT(55,28,1)
+  av_frame_free (_frame);
+#else
+  avcodec_free_frame (_frame);
+#endif
   sws_freeContext (scaler_ctx);
   return 0;
 }
   encoder_codec_ctx->width = dst_width;
   encoder_codec_ctx->height = dst_height;
-  encoder_codec_ctx->pix_fmt = PIX_FMT_RGB24;
+  encoder_codec_ctx->pix_fmt = PIX_OUTPUT_FORMAT;
   opts = NULL;
   if (avcodec_open2 (encoder_codec_ctx, encoder_codec, ) < 0)
 {
@@ -263,10 +297,14 @@
   fprintf (stderr,
"Failed to open the encoder\n");
 #endif
-  av_free (encoder_codec_ctx);
+  avcodec_free_context (_codec_ctx);
   av_free (encoder_output_buffer);
   av_free (dst_buffer);
-  av_free (dst_frame);
+#if LIBAVCODEC_VERSION_INT >= AV_VERSION_INT(55,28,1)
+  av_frame_free (_frame);
+#else
+  avcodec_free_frame (_frame);
+#endif
   sws_freeContext  (scaler_ctx);
   return 0;
 }
@@ -295,9 +333,13 @@
 cleanup:
   av_dict_free ();
   avcodec_close (encoder_codec_ctx);
-  av_free (encoder_codec_ctx);
+  avcodec_free_context (_codec_ctx);
   av_free (dst_buffer);
-  av_free (dst_frame);
+#if LIBAVCODEC_VERSION_INT >= AV_VERSION_INT(55,28,1)
+  av_frame_free (_frame);
+#else
+  avcodec_free_frame (_frame);
+#endif
   sws_freeContext (scaler_ctx);
   *output_data = encoder_output_buffer;
 
@@ -406,18 +448,23 @@
   fprintf (stderr,
 	   "Failed to open image codec\n");
 #endif
-  av_free (codec_ctx);
+  avcodec_free_context (_ctx);
   return;
 }
   av_dict_free 

Bug#822473: marked as done (gnome-software: FTBFS: static declaration of 'as_app_has_compulsory_for_desktop' follows non-static declaration)

2016-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2016 22:41:47 +0200
with message-id 

and subject line Re: Bug#822473: gnome-software: FTBFS: static declaration of 
'as_app_has_compulsory_for_desktop' follows non-static declaration
has caused the Debian Bug report #822473,
regarding gnome-software: FTBFS: static declaration of 
'as_app_has_compulsory_for_desktop' follows non-static declaration
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.)


-- 
822473: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822473
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-software
Version: 3.18.3-3
Severity: serious

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> -pthread -I/usr/include/libsoup-2.4 -I/usr/include/libxml2 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
> -I/usr/include/fwupd-1 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/Limba 
> -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" 
> -DGS_MODULESETDIR=\"/usr/share/gnome-software/modulesets.d\" 
> -DG_LOG_DOMAIN=\"GsPlugin\" -DLIBDIR=\"/usr/lib\" -DLOCALSTATEDIR=\"/var\" 
> -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\"/etc\" 
> -DTESTDATADIR=\"../../data/tests\" -I../../src -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wall -Wstrict-prototypes -Wnested-externs 
> -Werror=missing-prototypes -Werror=implicit-function-declaration 
> -Werror=pointer-arith -Werror=init-self -Werror=format-security 
> -Werror=format=2 -Werror=missing-include-dirs -Werror=return-type 
> -Wmissing-declarations -Wcast-align -Wwrite-strings -Wreturn-type 
> -Wformat-nonliteral -Wmissing-format-attribute -Wclobbered -Wempty-body 
> -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized 
> -Waggregate-return -Wdeclaration-after-statement -Wshadow 
> -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -c 
> gs-plugin-appstream.c  -fPIC -DPIC -o 
> .libs/libgs_plugin_appstream_la-gs-plugin-appstream.o
> In file included from ../../src/gs-plugin.h:30:0,
>  from gs-plugin-appstream.c:27:
> ../../src/gs-app.h:109:1: warning: 'AsIdKind' is deprecated: Use AsAppKind 
> instead [-Wdeprecated-declarations]
>  AsIdKind  gs_app_get_id_kind  (GsApp  *app);
>  ^
> In file included from /usr/include/libappstream-glib/as-app.h:32:0,
>  from /usr/include/libappstream-glib/appstream-glib.h:27,
>  from gs-plugin-appstream.c:25:
> /usr/include/libappstream-glib/as-enums.h:49:14: note: declared here
>  typedef enum {
>   ^
> In file included from ../../src/gs-plugin.h:30:0,
>  from gs-plugin-appstream.c:27:
> ../../src/gs-app.h:111:8: warning: 'AsIdKind' is deprecated: Use AsAppKind 
> instead [-Wdeprecated-declarations]
> AsIdKind  id_kind);
> ^
> In file included from /usr/include/libappstream-glib/as-app.h:32:0,
>  from /usr/include/libappstream-glib/appstream-glib.h:27,
>  from gs-plugin-appstream.c:25:
> /usr/include/libappstream-glib/as-enums.h:49:14: note: declared here
>  typedef enum {
>   ^
> gs-plugin-appstream.c:54:1: error: static declaration of 
> 'as_app_has_compulsory_for_desktop' follows non-static declaration
>  as_app_has_compulsory_for_desktop (AsApp *app, const gchar 
> *compulsory_for_desktop)
>  ^
> In file included from /usr/include/libappstream-glib/appstream-glib.h:27:0,
>  from gs-plugin-appstream.c:25:
> /usr/include/libappstream-glib/as-app.h:340:11: note: previous declaration of 
> 'as_app_has_compulsory_for_desktop' was here
>  gboolean  as_app_has_compulsory_for_desktop (AsApp *app,
>^
> gs-plugin-appstream.c: In function 'gs_plugin_refine_item':
> gs-plugin-appstream.c:473:3: warning: 'as_app_get_id_kind' is deprecated: Use 
> 'as_app_get_kind' instead [-Wdeprecated-declarations]
>if (as_app_get_id_kind (item) == AS_ID_KIND_SOURCE) {
>^
> In file included from /usr/include/libappstream-glib/appstream-glib.h:27:0,
>  from gs-plugin-appstream.c:25:
> /usr/include/libappstream-glib/as-app.h:480:11: note: declared here
>  AsIdKind  as_app_get_id_kind  (AsApp  *app)
>^
> gs-plugin-appstream.c:598:3: warning: 'as_app_get_id_kind' is deprecated: Use 
> 'as_app_get_kind' instead [-Wdeprecated-declarations]
>gs_app_set_id_kind (app, as_app_get_id_kind (item));
>^
> In file 

Bug#822516: marked as done (lostirc: FTBFS: Package requirements (gtkmm-2.4 gdkmm-2.4 atkmm-1.6 pangomm-1.4) were not met)

2016-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2016 13:30:10 -0700
with message-id <20160425203010.gc13...@jirafa.cyrius.com>
and subject line Working now
has caused the Debian Bug report #822516,
regarding lostirc: FTBFS: Package requirements (gtkmm-2.4 gdkmm-2.4 atkmm-1.6 
pangomm-1.4) were not met
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.)


-- 
822516: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lostirc
Version: 0.4.6-4.1
Severity: serious

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> checking pkg-config is at least version 0.9.0... yes
> checking for GLIBMMDEPS_CFLAGS... -std=c++11 -I/usr/include/glibmm-2.4 
> -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sigc++-2.0 
> -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include
> checking for GLIBMMDEPS_LIBS... -lglibmm-2.4 -lgobject-2.0 -lglib-2.0 
> -lsigc-2.0
> checking for GTKMMDEPS_CFLAGS... 
> checking for GTKMMDEPS_LIBS... 
> configure: error: Package requirements (gtkmm-2.4 gdkmm-2.4 atkmm-1.6 
> pangomm-1.4) were not met.
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
> 
> Alternatively you may set the GTKMMDEPS_CFLAGS and GTKMMDEPS_LIBS environment 
> variables
> to avoid the need to call pkg-config.  See the pkg-config man page for
> more details.
> debian/rules:27: recipe for target 'configure-stamp' failed
> make: *** [configure-stamp] Error 1

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
This was caused by a bug in harfbuzz which got fixed in the meantime.
-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise--- End Message ---


Processed: libavg: diff for NMU version 1.8.1-2.1

2016-04-25 Thread Debian Bug Tracking System
Processing control commands:

> tags 803833 + pending
Bug #803833 [libavg] libavg: FTBFS with FFmpeg 2.9
Added tag(s) pending.

-- 
803833: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803833
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#822515: marked as done (surf: FTBFS: fatal error: gtk/gtk.h: No such file or directory)

2016-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2016 13:28:58 -0700
with message-id <20160425202858.gb13...@jirafa.cyrius.com>
and subject line Re: Bug#822515: surf: FTBFS: fatal error: gtk/gtk.h: No such 
file or directory
has caused the Debian Bug report #822515,
regarding surf: FTBFS: fatal error: gtk/gtk.h: No such file or directory
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.)


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

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> Package 'graphite2', required by 'harfbuzz', not found
> CC   = cc
> CC surf.c
> cc -c -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security 
> -std=c99 -pedantic -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -DVERSION=\"0.7\" 
> -D_DEFAULT_SOURCE -I. -I/usr/include -I/usr/X11R6/include  surf.c
> surf.c:8:21: fatal error: gtk/gtk.h: No such file or directory
> compilation terminated.
> Makefile:18: recipe for target 'surf.o' failed
> make[1]: *** [surf.o] Error 1
> make[1]: Leaving directory '/<>'
> dh_auto_build: make -j30 returned exit code 2

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
* Reiner Herrmann  [2016-04-25 18:39]:
> I just tried to reproduce your build failure, but wasn't able to.
> I used an up-to-date pbuilder with unstable on amd64, and also verified
> on the reproducible builds infrastructure that it builds fine [1] [2].

> > Package 'graphite2', required by 'harfbuzz', not found

This was caused by a bug in harfbuzz which got fixed yesterday.
Sorry, I was going to close this bug report but you were faster.

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise--- End Message ---


Bug#803833: libavg: diff for NMU version 1.8.1-2.1

2016-04-25 Thread Sebastian Ramacher
Control: tags 803833 + pending

Dear maintainer,

I've prepared an NMU for libavg (versioned as 1.8.1-2.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
Sebastian Ramacher
diff -Nru libavg-1.8.1/debian/changelog libavg-1.8.1/debian/changelog
--- libavg-1.8.1/debian/changelog	2015-08-31 00:16:24.0 +0200
+++ libavg-1.8.1/debian/changelog	2016-04-25 22:26:13.0 +0200
@@ -1,3 +1,12 @@
+libavg (1.8.1-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Andreas Cadhalpun ]
+  * Fix build against ffmpeg 3.0. (Closes: #803833)
+
+ -- Sebastian Ramacher   Mon, 25 Apr 2016 22:26:12 +0200
+
 libavg (1.8.1-2) unstable; urgency=medium
 
   * Apply patch from Reiner Herrmann for reproducible builds. (Closes: #797440)
diff -Nru libavg-1.8.1/debian/patches/ffmpeg_2.9.patch libavg-1.8.1/debian/patches/ffmpeg_2.9.patch
--- libavg-1.8.1/debian/patches/ffmpeg_2.9.patch	1970-01-01 01:00:00.0 +0100
+++ libavg-1.8.1/debian/patches/ffmpeg_2.9.patch	2016-04-25 19:29:46.0 +0200
@@ -0,0 +1,314 @@
+Description: Replace deprecated FFmpeg API
+Author: Andreas Cadhalpun 
+Last-Update: <2015-11-02>
+
+--- libavg-1.8.1.orig/src/player/VideoWriterThread.cpp
 libavg-1.8.1/src/player/VideoWriterThread.cpp
+@@ -35,7 +35,7 @@ using namespace std;
+ namespace avg {
+ 
+ const unsigned int VIDEO_BUFFER_SIZE = 40;
+-const AVPixelFormat STREAM_PIXEL_FORMAT = ::PIX_FMT_YUVJ420P;
++const AVPixelFormat STREAM_PIXEL_FORMAT = ::AV_PIX_FMT_YUVJ420P;
+ 
+ VideoWriterThread::VideoWriterThread(CQueue& cmdQueue, const string& sFilename,
+ IntPoint size, int frameRate, int qMin, int qMax)
+@@ -95,7 +95,7 @@ void VideoWriterThread::close()
+ 
+ av_free(m_pOutputFormatContext);
+ av_free(m_pVideoBuffer);
+-av_free(m_pConvertedFrame);
++av_frame_free(_pConvertedFrame);
+ av_free(m_pPictureBuffer);
+ sws_freeContext(m_pFrameConversionContext);
+ m_pOutputFormatContext = 0;
+@@ -174,7 +174,7 @@ void VideoWriterThread::open()
+ }
+ 
+ m_pFrameConversionContext = sws_getContext(m_Size.x, m_Size.y, 
+-::PIX_FMT_RGB32, m_Size.x, m_Size.y, STREAM_PIXEL_FORMAT, 
++::AV_PIX_FMT_RGB32, m_Size.x, m_Size.y, STREAM_PIXEL_FORMAT,
+ SWS_BILINEAR, NULL, NULL, NULL);
+ 
+ m_pConvertedFrame = createFrame(STREAM_PIXEL_FORMAT, m_Size);
+@@ -234,7 +234,7 @@ AVFrame* VideoWriterThread::createFrame(
+ {
+ AVFrame* pPicture;
+ 
+-pPicture = avcodec_alloc_frame();
++pPicture = av_frame_alloc();
+ 
+ int memNeeded = avpicture_get_size(pixelFormat, size.x, size.y);
+ m_pPictureBuffer = static_cast(av_malloc(memNeeded));
+--- libavg-1.8.1.orig/src/video/AudioDecoderThread.cpp
 libavg-1.8.1/src/video/AudioDecoderThread.cpp
+@@ -134,7 +134,7 @@ void AudioDecoderThread::decodePacket(AV
+ #if LIBAVCODEC_VERSION_INT >= AV_VERSION_INT(53, 25, 0)
+ int gotFrame = 0;
+ AVFrame* pDecodedFrame;
+-pDecodedFrame = avcodec_alloc_frame();
++pDecodedFrame = av_frame_alloc();
+ #endif
+ while (pTempPacket->size > 0) {
+ int bytesDecoded = AVCODEC_MAX_AUDIO_FRAME_SIZE;
+@@ -192,7 +192,7 @@ void AudioDecoderThread::decodePacket(AV
+ }
+ av_free(pDecodedData);
+ #if LIBAVCODEC_VERSION_MAJOR > 53
+-avcodec_free_frame();
++av_frame_free();
+ #elif LIBAVCODEC_VERSION_INT >= AV_VERSION_INT(53, 25, 0)
+ delete pDecodedFrame;
+ #endif
+--- libavg-1.8.1.orig/src/video/FFMpegFrameDecoder.cpp
 libavg-1.8.1/src/video/FFMpegFrameDecoder.cpp
+@@ -119,29 +119,29 @@ void FFMpegFrameDecoder::convertFrameToB
+ switch (pBmp->getPixelFormat()) {
+ case R8G8B8X8:
+ case R8G8B8A8:
+-destFmt = PIX_FMT_RGBA;
++destFmt = AV_PIX_FMT_RGBA;
+ break;
+ case B8G8R8X8:
+ case B8G8R8A8:
+-destFmt = PIX_FMT_BGRA;
++destFmt = AV_PIX_FMT_BGRA;
+ break;
+ case R8G8B8:
+-destFmt = PIX_FMT_RGB24;
++destFmt = AV_PIX_FMT_RGB24;
+ break;
+ case B8G8R8:
+-destFmt = PIX_FMT_BGR24;
++destFmt = AV_PIX_FMT_BGR24;
+ break;
+ case YCbCr422:
+-destFmt = PIX_FMT_YUYV422;
++destFmt = AV_PIX_FMT_YUYV422;
+ break;
+ default:
+ AVG_ASSERT_MSG(false, (string("FFMpegFrameDecoder: Dest format ") +
+ toString(pBmp->getPixelFormat()) + " not supported.").c_str());
+-destFmt = PIX_FMT_BGRA;
++destFmt = AV_PIX_FMT_BGRA;
+ }
+ AVCodecContext const* pContext = m_pStream->codec;
+-if (destFmt == PIX_FMT_BGRA && (pContext->pix_fmt == PIX_FMT_YUV420P || 
+-pContext->pix_fmt == PIX_FMT_YUVJ420P))
++if (destFmt == AV_PIX_FMT_BGRA && (pContext->pix_fmt == AV_PIX_FMT_YUV420P ||
++

Bug#798167: camitk and vtk/itk transitions

2016-04-25 Thread Emmanuel Promayon


On 24/04/16 18:30, Mattia Rizzolo wrote:

On Sun, Apr 24, 2016 at 05:56:00PM +0200, Emmanuel Promayon wrote:
> I checked Gianfranco's experimental branch and his work is great!
> There is few build-depend packages that can be removed (and I noticed
> the problem with the pixmaps), but this would be my pleasure to fix
> that very soon.

cool!
If you could fine some minutes to trimmer the build-deps, etc would be
awesome.



I managed to do some work on polishing the package, and once Gianfranco 
has agree, I will pull everything to the "experimental" branch.


From there I am not quite sure how to ask for an upload using the 
"experimental" branch (or should experimental be first merged to master?)


Thanks to Gianfranco tip, I used
gbp buildpackage --git-debian-branch=experimental --git-ignore-new

I used a docker sid image (which might not be the best, but was at hand 
on my machine)... and the packages were build.
All the 441 post-build tests passed as well. I also updated the 
autopkgtest script, and it should work as well (although I could not run 
adt-run or puiparts in docker)


Lintian still gives two types of warnings (repeated multiple times):
1) libcamitk4-data: package-contains-timestamped-gzip
For these ones, I think the best is to redo the gzip upstream (and 
therefore wait for the next upstream to clean this)

2) debug-file-with-no-debug-symbols for all *-dbgsym package
For this one, I am a bit puzzled. I am not sure at all what causes this 
error. Is it because the package is build using the "--builddirectory" 
option:

dh $@ --builddirectory=camitk-build
and all the .debug files end up in another (non default) directory?

Note: I tried to use dh $@ with the --parallel option in d/r, but gbp 
buildpackage seemed oblivious to it.



> I agree that the display bug, although a priority for upstream,
> should not delay any debian cleaning up.

everything started by wanting to remove libpng12.  And then we noticed
in how such a bad state unstable was wrt cruft.
For some reason or the other, camitk is entangled in *all* of them; we
have a pad where we are tracking everything, and camitk is on all the
sections :\


Wooah... No pressure then!
Your explanation has accelerated the process and put this packaging task 
on top of my urgent task list... Hope this will help remove camitk from 
the bad books...



> Therefore, I hereby declare that what Gianfranco did is great and
> blessed! Thanks you very much!
> If Gianfranco and everyone else is ok with it (I did not have time to
> check the packaging here), it would be great if it can be uploaded
> directly in unstable.

\o/

Great!  One of us will get to it very soon :)
(guess Gianfranco, as he did most/all of the work)


OK. I will wait to Gianfranco agreement before I pull my commits to the 
experimental branch (I asked him if he was ok with it).



> In the next few weeks, hopefully upstream 4.0.1 will solve the display
> bug and I can polish the packaging.

In the meantime I'll file a RC bug for it, so it'll stay out of testing,
and all the involved parties can notice this version is partially not
working.


Great! Thanks.


> Thanks you again all for your work, it is amazing how every time
> there is something new to learn!

There is still more ;)



:-)




smime.p7s
Description: S/MIME Cryptographic Signature


Bug#819198: Missing libapache2-mod-auth-radius on Debian 8.3 mirrors.

2016-04-25 Thread Jonas Crescencio
It is not on the stable mirrors, there is no
pool/main/liba/libapache-mod-auth-radius/
directory on Jessie. It is on Wheezy, Stretch and Sid, but it is not on
Jessie.


Wheezy -
https://buildd.debian.org/status/package.php?p=libapache-mod-auth-radius=wheezy

Stretch -
https://buildd.debian.org/status/package.php?p=libapache-mod-auth-radius=stretch

Sid -
https://buildd.debian.org/status/package.php?p=libapache-mod-auth-radius=sid


Will it be released on this stable version (Jessie 8.x)? Or it will only be
released on the next Debian 9.x ?

I am asking this, because I need so much this package on the current
official stable version mirrors (Debian 8) and if it will not be released
on a soon upgrade, I will try another method of apache authentication,
because this package is missing.

Thank you.

2016-04-24 16:58 GMT-03:00 Josip Rodin :

> reassign 819198 www.debian.org
> thanks
>
> On Thu, Mar 24, 2016 at 03:49:28PM -0300, Js wrote:
> > Package: libapache2-mod-auth-radius
> > Version: 1.5
> > Severity: serious
> > Tags: upstream
> > Justification: fails to build from source (but built successfully in the
> past)
> >
> > The package libapache2-mod-auth-radius is not on Debian mirrors. I did
> not
> > find why this package was excluded from mirrors.
>
> It is on the mirrors, you can check the
> pool/main/liba/libapache-mod-auth-radius/ directory I guess?
>
> The package just got back into testing a couple of months ago, putting it
> on
> track to be released with Debian 9.x, and now this bug report removed it
> again :)
>
> I do find it strange that the website search brings up nothing:
> https://packages.debian.org/search?keywords=libapache2-mod-auth-radius
>
> It's supposed to show the one in unstable at least...
>
> https://packages.qa.debian.org/liba/libapache-mod-auth-radius.html
>
>
> https://buildd.debian.org/status/package.php?p=libapache-mod-auth-radius=unstable
>
> --
>  2. That which causes joy or happiness.
>


Processed: Re: ngspice: FTBFS with nonexistant $HOME

2016-04-25 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending patch
Bug #813119 [src:ngspice] ngspice: FTBFS with nonexistant $HOME
Added tag(s) pending.

-- 
813119: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813119
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#813119: ngspice: FTBFS with nonexistant $HOME

2016-04-25 Thread Andreas Beckmann
Followup-For: Bug #813119
Control: tag -1 pending patch

Hi,

I just uploaded a NMU fixing the FTBFS to DELAYED/10. Please let me
know, if I should delay it longer.

I also plan to backport this fix to jessie.


Andreas
diff -Nru ngspice-26/debian/changelog ngspice-26/debian/changelog
--- ngspice-26/debian/changelog	2014-07-05 23:49:29.0 +0200
+++ ngspice-26/debian/changelog	2016-04-25 20:51:09.0 +0200
@@ -1,3 +1,11 @@
+ngspice (26-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Run lyx with a temporary -userdir to not rely on $HOME, thanks to
+Johann Klammer.  (Closes: #813119)
+
+ -- Andreas Beckmann   Mon, 25 Apr 2016 20:50:13 +0200
+
 ngspice (26-1) unstable; urgency=low
 
   * New upstream release (Closes: #706821)
diff -Nru ngspice-26/debian/rules ngspice-26/debian/rules
--- ngspice-26/debian/rules	2014-07-05 23:49:29.0 +0200
+++ ngspice-26/debian/rules	2016-04-25 19:30:19.0 +0200
@@ -33,6 +33,7 @@
 	#cp -f /usr/share/misc/config.sub build/ngspice/doc/config.sub
 	#cp -f /usr/share/misc/config.guess build/ngspice/doc/config.guess
 	cp -a manual build/
+	mkdir -p build/manual/.lyx
 	# Make build dir for tclspice
 	mkdir -p build/tclspice
 	cp -Rl `ls . |grep -v build|grep -v debian` build/tclspice
@@ -77,9 +78,9 @@
 build-indep: config.status
 	# Build documentation
 	dh_testdir
-	#cd build/manual && lyx --export ps manual.lyx 
-	cd build/manual && lyx --export pdf2 manual.lyx 
-	cd build/manual && lyx --export html manual.lyx 
+	#cd build/manual && lyx -userdir ./.lyx -batch --export ps manual.lyx 
+	cd build/manual && lyx -userdir ./.lyx -batch --export pdf2 manual.lyx 
+	cd build/manual && lyx -userdir ./.lyx -batch --export html manual.lyx 
 	touch $@
 
 clean:


Bug#749257: marked as done (python-jswebkit: depends on python-webkit which is deprecated)

2016-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2016 19:44:41 +
with message-id 
and subject line Bug#822421: Removed package(s) from unstable
has caused the Debian Bug report #749257,
regarding python-jswebkit: depends on python-webkit which is deprecated
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.)


-- 
749257: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749257
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-jswebkit
Version: 0.0.3-2
Severity: important
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs python-webkit webkit1

Hi,

python-jswebkit depends on python-webkit, which is deprecated and
going to be removed from the archive. python-jswebkit should switch
to using the GObject Introspection bindings for webkit, ideally
gir1.2-webkit2-3.0 for Webkit2 and gtk+3 as upstream has already
dropped WebKit1 (so gir1.2-webkit-1.0 and gir1.2-webkit-3.0 are
likely to be dropped from Debian in the near future). This would mean
switching to GObject Introspection for other bindings as well, e.g.
GLib and GTK+, so making the switch to GTK+ 3 at the same time would
make a lot of sense.

For more information on GObject Introspection see [1] and [2].

If you have any question don't hesitate to ask.

Emilio

[1] https://wiki.gnome.org/action/show/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/action/show/Projects/PyGObject 
--- End Message ---
--- Begin Message ---
Version: 0.0.3-2+rm

Dear submitter,

as the package python-jswebkit has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/822421

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---


Bug#822500: marked as done (brlaser: FTBFS: 'string' is not a member of 'std')

2016-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2016 19:34:29 +
with message-id 
and subject line Bug#822500: fixed in brlaser 3-5
has caused the Debian Bug report #822500,
regarding brlaser: FTBFS: 'string' is not a member of 'std'
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.)


-- 
822500: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822500
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: brlaser
Version: 3-4
Severity: serious

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> g++ -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -std=gnu++11  -Wall 
> -c -o src/brdecode.o src/brdecode.cc
> src/brdecode.cc: In function 'int main(int, char**)':
> src/brdecode.cc:177:3: error: 'string' is not a member of 'std'
>std::string out_prefix;
>^
> src/brdecode.cc:181:5: error: 'out_prefix' was not declared in this scope
>  out_prefix = argv[2];
>  ^
> src/brdecode.cc:184:5: error: 'out_prefix' was not declared in this scope
>  out_prefix = argv[1];
>  ^
> src/brdecode.cc:187:5: error: 'out_prefix' was not declared in this scope
>  out_prefix = "page";
>  ^
> src/brdecode.cc:207:7: error: 'string' is not a member of 'std'
>std::string out_filename = out_prefix
>^
> src/brdecode.cc:209:30: error: 'out_filename' was not declared in this scope
>FILE *out_file = fopen(out_filename.c_str(), "wb");
>   ^
> Makefile:735: recipe for target 'src/brdecode.o' failed
> make[3]: *** [src/brdecode.o] Error 1
> make[3]: Leaving directory '/<>'

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: brlaser
Source-Version: 3-5

We believe that the bug you reported is fixed in the latest version of
brlaser, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 822...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Didier Raboud  (supplier of updated brlaser package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 25 Apr 2016 21:28:24 +0200
Source: brlaser
Binary: printer-driver-brlaser
Architecture: source
Version: 3-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Printing Team 
Changed-By: Didier Raboud 
Description:
 printer-driver-brlaser - printer driver for (some) Brother laser printers
Closes: 822500
Changes:
 brlaser (3-5) unstable; urgency=medium
 .
   [ Peter Spiess-Knafl ]
   * Add patch to add missing #include  (Closes: #822500)
 .
   [ Didier Raboud ]
   * Bump S-V to 3.9.8 without changes needed
   * Add debian/gbp.conf to cope with the new git branches
Checksums-Sha1:
 5c3aab72b4c6d211fa9ea4875d75291c7d79effb 1768 brlaser_3-5.dsc
 e746eccd27cb1d6d658f5975aa9e6555169023cd 3872 brlaser_3-5.debian.tar.xz
Checksums-Sha256:
 0e412bf06f6e7aad287a86743629b941f037cfc213bce77c12150ed6974c5743 1768 
brlaser_3-5.dsc
 668a3c90c651564b50db93c1dbc4ab52d6ad900313b9be5fee0c90ecef94f3a3 3872 
brlaser_3-5.debian.tar.xz
Files:
 22a6184cd484020ea92be93ecdec2a2b 1768 text optional brlaser_3-5.dsc
 badfb6164cc15b3a56e8a5c3069dc5c5 3872 text optional brlaser_3-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQGcBAEBCgAGBQJXHm/4AAoJEIvPpx7KFjRVye4L/j/LbxKzI04eFLt+hHfkp6nE
gXMgWbEmi1ynzApB8ysoBg2uXaly94nQK/ctBSFdLU9kIqXosLpR2nt0gjVAQTR1
7pe2aHNxiFu4PIoVKKFPnmR+AlFo6NFC/Bj63DHqlcUwktpWiCajHGz4Wv3rokRH
8ST9rRi8RvtCFfaxjcfwkCgscpjD8r8OE0kKtQFPPLhjuozqsC8JG1FMBT01B6CS
5QK/NLQqNX275RtvQFT2ZoGqOGrXyqMOHEbbvfglzblIfM6jKBsdqD1au7zVcKQu
2A4wJ4MDrhmeYderHojrbE0Xl8tEM7uO4RK8LTFnYw/Yw4pwR4lM6xXLQfmbISoy
KOpGFC7bGrmE7G+XYPabNOQNnsUk/TtnFXrw3VuOk5B9ZEnXbACOrBsK6KvgNaEn
3oI8jYPKHGIXKibfon7lXoVLFRdS+rC+afkKG/LI4FW0+pc1CRSHEdZZZUkhN+7Z
dePsmnGLUTVp/1JVu4NhcS0QoSmaY7A0gHiA1px/gQ==
=Vs/4
-END PGP SIGNATURE End Message ---


Bug#816980: [Pkg-julia-devel] Bug#816980: julia: FTBFS in testing

2016-04-25 Thread Peter Colberg
Hi Santiago,

On Mon, Apr 25, 2016 at 09:24:51PM +0200, Santiago Vila wrote:
> Question: Why should this package be the only one which does not work
> with eatmydata? Are there good reasons for the build system to be
> incompatible with eatmydata? Could julia be made compatible with
> eatmydaya again? I'm building a lot of packages and this is a real
> time saver.

I had the same issue with eatmydata causing segmentation faults:

https://github.com/JuliaLang/julia/issues/14033

You can still use eatmydata by diverting dpkg inside the sbuild chroot

dpkg-divert --rename /usr/bin/dpkg

and putting the following script in its place:

#!/bin/sh
exec /usr/bin/eatmydata /usr/bin/dpkg.distrib "$@"

Regards,
Peter



Bug#822500: Patch for FTBFS

2016-04-25 Thread Didier 'OdyX' Raboud
Le lundi, 25 avril 2016, 15.13:54 Peter Spiess-Knafl a écrit :
> A quick "#include " did the trick.
> (…)
> I also forwarded it upstream:
> https://github.com/pdewacht/brlaser/pull/9

Uploaded, credited to you. Thanks!

-- 
Cheers,
OdyX

signature.asc
Description: This is a digitally signed message part.


Bug#822496: marked as done (rr: FTBFS: error: 'floor' was not declared in this scope)

2016-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2016 19:24:09 +
with message-id 
and subject line Bug#822496: fixed in rr 4.2.0-2
has caused the Debian Bug report #822496,
regarding rr: FTBFS: error: 'floor' was not declared in this scope
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.)


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

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> [ 43%] Building CXX object CMakeFiles/rr.dir/src/Scheduler.cc.o
> /usr/bin/c++   -DRR_VERSION=\"4.2.0\" -I/<>/include 
> -I/<>/build  -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -D__USE_LARGEFILE64 
> -D__STDC_LIMIT_MACROS -D__STDC_FORMAT_MACROS -std=c++0x -pthread -O0 -g3 
> -Wall -Wextra -Werror -o CMakeFiles/rr.dir/src/Scheduler.cc.o -c 
> /<>/src/Scheduler.cc
> /<>/src/Scheduler.cc: In function 'void sleep_time(double)':
> /<>/src/Scheduler.cc:262:30: error: 'floor' was not declared in 
> this scope
>ts.tv_sec = (time_t)floor(t);
>   ^
> /<>/src/Scheduler.cc: In member function 'void 
> Scheduler::maybe_reset_high_priority_only_intervals(double)':
> /<>/src/Scheduler.cc:293:65: error: 'pow' was not declared in 
> this scope
>pow(high_priority_only_duration_step_factor, duration_step);
>  ^
> /<>/src/Scheduler.cc: In member function 'bool 
> Scheduler::in_high_priority_only_interval(double)':
> /<>/src/Scheduler.cc:313:56: error: 'fmod' was not declared in 
> this scope
>  high_priority_only_intervals_period);
> ^
> /<>/src/Scheduler.cc: In member function 'double 
> Scheduler::interrupt_after_elapsed_time() const':
> /<>/src/Scheduler.cc:484:53: error: 'floor' was not declared in 
> this scope
>   high_priority_only_intervals_period) +
>  ^
> CMakeFiles/rr.dir/build.make:1041: recipe for target 
> 'CMakeFiles/rr.dir/src/Scheduler.cc.o' failed
> make[3]: *** [CMakeFiles/rr.dir/src/Scheduler.cc.o] Error 1
> make[3]: Leaving directory '/<>/build'
> CMakeFiles/Makefile2:11120: recipe for target 'CMakeFiles/rr.dir/all' failed
> make[2]: *** [CMakeFiles/rr.dir/all] Error 2
> make[2]: Leaving directory '/<>/build'
> Makefile:163: recipe for target 'all' failed
> make[1]: *** [all] Error 2

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: rr
Source-Version: 4.2.0-2

We believe that the bug you reported is fixed in the latest version of
rr, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 822...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated rr package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 25 Apr 2016 21:06:50 +0200
Source: rr
Binary: rr
Architecture: source
Version: 4.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Stephen Kitt 
Changed-By: Stephen Kitt 
Description:
 rr - application execution recorder, player and debugger
Closes: 822496
Changes:
 rr (4.2.0-2) unstable; urgency=medium
 .
   * Include math.h in Scheduler.cc (closes: #822496).
   * Standards-Version 3.9.8, no change required.
Checksums-Sha1:
 862813ca6c83cf000bb41c2396f9dcf91ee1b37e 1880 rr_4.2.0-2.dsc
 319eed318e8603b4b020a36c3f43dae9f4ff8378 7704 rr_4.2.0-2.debian.tar.xz
Checksums-Sha256:
 c5e637ef09f557c11a9bd83fb6e973bf830ef35f1739f41a9e3fd403a5cbc823 1880 
rr_4.2.0-2.dsc
 e2e0a720f80f98cb78a1e9538b2a18be31c57cab4cbbb0065fe18a3a18c28c8b 7704 
rr_4.2.0-2.debian.tar.xz
Files:
 357080ab76d3a79fe5d921bdaad8fbe8 1880 devel optional rr_4.2.0-2.dsc
 559aeee8b4a9f78acbc9f86bcedb9aeb 7704 devel optional rr_4.2.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG 

Bug#816980: julia: FTBFS in testing

2016-04-25 Thread Santiago Vila
retitle 816980 julia: FTBFS in testing
thanks

Ok, there seems to be some kind of incompatibility between julia and
eatmydata. My /etc/schroot/chroot.d/stretch file for sbuild was like
this:

[stretch]
type=directory
description=Debian stretch
directory=/chroot/stretch
groups=sbuild
root-groups=sbuild
preserve-environment=true
command-prefix=eatmydata

If I drop the last line, the "Segmentation fault" errors disappear,
but the build still fails:


Exception running test replcompletions :
On worker 12:
LoadError: SystemError: mkdir: File exists
 in mkdir at ./file.jl:42
while loading /<>/test/replcompletions.jl, in expression starting 
on line 467
ERROR: LoadError: Some tests exited with errors.
 in anonymous at /<>/test/runtests.jl:64
while loading /<>/test/runtests.jl, in expression starting on line 
13
Makefile:9: recipe for target 'all' failed
make[2]: *** [all] Error 1
make[2]: Leaving directory '/<>/test'
debian/rules:74: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
debian/rules:63: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2


Question: Why should this package be the only one which does not work
with eatmydata? Are there good reasons for the build system to be
incompatible with eatmydata? Could julia be made compatible with
eatmydaya again? I'm building a lot of packages and this is a real
time saver.

Anyway, without eatmydata, the package still FTBFS in testing, so the
bug remains. Please try to reproduce in testing, which is what the
subject of the bug says.

The full build log is attached.

Thanks.

julia_0.4.5-3_amd64-20160425-2037.gz
Description: application/gzip


Processed: Re: Bug#816980: julia: FTBFS in testing

2016-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> retitle 816980 julia: FTBFS in testing
Bug #816980 [src:julia] julia: FTBFS in testing (signal (11): Segmentation 
fault)
Changed Bug title to 'julia: FTBFS in testing' from 'julia: FTBFS in testing 
(signal (11): Segmentation fault)'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
816980: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816980
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems




Bug#814183: [Debichem-devel] Bug#816590: Bug#814183: openmpi 1.10.2 is broken on powerpc

2016-04-25 Thread Graham Inggs
Please see #816101 [1].  It seems the powerpc and mipsel issues are
closely related.
The PETSc package maintainer conditionally disabled the 2 process MPI
tests on powerpc and mipsel in order to work around the problem.


[1] https://bugs.debian.org/816101



Processed: tagging 822496

2016-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 822496 + pending
Bug #822496 [rr] rr: FTBFS: error: 'floor' was not declared in this scope
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
822496: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822496
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#798174: marked as done (viper: depends on vtk 5)

2016-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2016 17:46:34 +
with message-id 
and subject line Bug#822543: Removed package(s) from unstable
has caused the Debian Bug report #798174,
regarding viper: depends on vtk 5
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.)


-- 
798174: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798174
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: viper
Version: 1.0.0-1
Severity: serious
Tags: sid stretch
Control: block 798164 with -1

Hi,

your package depends on vtk 5.x, which should not be in stretch.  Please
switch to vtk 6.x or drop the dependency.

Thanks,
Julien


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 1.0.0-1+rm

Dear submitter,

as the package viper has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/822543

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---


Bug#803835: libextractor: diff for NMU version 1:1.3-3.1

2016-04-25 Thread Sebastian Ramacher
Control: tags 803835 + pending

Dear maintainer,

I've prepared an NMU for libextractor (versioned as 1:1.3-3.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
Sebastian Ramacher
diff -Nru libextractor-1.3/debian/changelog libextractor-1.3/debian/changelog
--- libextractor-1.3/debian/changelog	2015-11-15 17:13:37.0 +0100
+++ libextractor-1.3/debian/changelog	2016-04-25 19:36:15.0 +0200
@@ -1,3 +1,12 @@
+libextractor (1:1.3-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Andreas Cadhalpun ]
+  * Fix build against ffmpeg 3.0. (Closes: #803835)
+
+ -- Sebastian Ramacher   Mon, 25 Apr 2016 19:36:14 +0200
+
 libextractor (1:1.3-3) unstable; urgency=medium
 
   * Update long description to list the supported formats.
diff -Nru libextractor-1.3/debian/patches/ffmpeg_2.9_pixfmt.patch libextractor-1.3/debian/patches/ffmpeg_2.9_pixfmt.patch
--- libextractor-1.3/debian/patches/ffmpeg_2.9_pixfmt.patch	1970-01-01 01:00:00.0 +0100
+++ libextractor-1.3/debian/patches/ffmpeg_2.9_pixfmt.patch	2016-04-25 19:35:47.0 +0200
@@ -0,0 +1,51 @@
+Description: Replace deprecated FFmpeg API
+Author: Andreas Cadhalpun 
+Last-Update: <2015-11-28>
+
+--- libextractor-1.3.orig/src/plugins/thumbnailffmpeg_extractor.c
 libextractor-1.3/src/plugins/thumbnailffmpeg_extractor.c
+@@ -153,7 +153,7 @@ seek_cb (void *opaque,
+ static size_t 
+ create_thumbnail (int src_width, int src_height, 
+ 		  int src_stride[],
+-		  enum PixelFormat src_pixfmt, 
++		  enum AVPixelFormat src_pixfmt,
+ 		  const uint8_t * const src_data[],
+ 		  int dst_width, int dst_height,
+ 		  uint8_t **output_data, 
+@@ -189,7 +189,7 @@ create_thumbnail (int src_width, int src
+   if (NULL == 
+   (scaler_ctx =
+sws_getContext (src_width, src_height, src_pixfmt,
+-		   dst_width, dst_height, PIX_FMT_RGB24, 
++		   dst_width, dst_height, AV_PIX_FMT_RGB24,
+ 		   SWS_BILINEAR, NULL, NULL, NULL)))
+ {
+ #if DEBUG
+@@ -214,7 +214,7 @@ create_thumbnail (int src_width, int src
+   return 0;
+ }
+   if (NULL == (dst_buffer =
+-	   av_malloc (avpicture_get_size (PIX_FMT_RGB24, dst_width, dst_height
++	   av_malloc (avpicture_get_size (AV_PIX_FMT_RGB24, dst_width, dst_height
+ {
+ #if DEBUG
+   fprintf (stderr,
+@@ -229,7 +229,7 @@ create_thumbnail (int src_width, int src
+   return 0;
+ }
+   avpicture_fill ((AVPicture *) dst_frame, dst_buffer,
+-  PIX_FMT_RGB24, dst_width, dst_height);
++  AV_PIX_FMT_RGB24, dst_width, dst_height);
+   sws_scale (scaler_ctx,
+  src_data, 
+  src_stride,
+@@ -272,7 +272,7 @@ create_thumbnail (int src_width, int src
+ }
+   encoder_codec_ctx->width = dst_width;
+   encoder_codec_ctx->height = dst_height;
+-  encoder_codec_ctx->pix_fmt = PIX_FMT_RGB24;
++  encoder_codec_ctx->pix_fmt = AV_PIX_FMT_RGB24;
+   opts = NULL;
+   if (avcodec_open2 (encoder_codec_ctx, encoder_codec, ) < 0)
+ {
diff -Nru libextractor-1.3/debian/patches/series libextractor-1.3/debian/patches/series
--- libextractor-1.3/debian/patches/series	2015-11-15 14:53:19.0 +0100
+++ libextractor-1.3/debian/patches/series	2016-04-25 19:35:47.0 +0200
@@ -1,2 +1,3 @@
 libgiflib5.1.patch
 ffmpeg2.9.patch
+ffmpeg_2.9_pixfmt.patch


signature.asc
Description: PGP signature


Processed: libextractor: diff for NMU version 1:1.3-3.1

2016-04-25 Thread Debian Bug Tracking System
Processing control commands:

> tags 803835 + pending
Bug #803835 [libextractor] libextractor: FTBFS with FFmpeg 2.9
Added tag(s) pending.

-- 
803835: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803835
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#774954: marked as done (ha: CVE-2015-1198: directory traversal vulnerabilities)

2016-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2016 17:35:51 +
with message-id 
and subject line Bug#822512: Removed package(s) from unstable
has caused the Debian Bug report #774954,
regarding ha: CVE-2015-1198: directory traversal vulnerabilities
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.)


-- 
774954: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774954
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: ha
Version: 0.999p+dfsg-5
Tags: security

ha is susceptible to directory traversal vulnerabilities. While 
extracting an archive, it will happily use absolute and relative paths 
taken from the archive. This can be exploited by a malicious archive to 
write files outside the current directory.


ha seems to store file names separately from their paths. Directory 
traversals are possible through both of the parts.


1. Through file name part.

A sample archive could be prepared in following way:

$ touch XtmpXabs XXXrel
$ ha a test.ha XtmpXabs XXXrel
$ sed -i 's|XtmpXabs|/tmp/abs|g;s|XXXrel|../rel|g' test.ha
$ rm XtmpXabs XXXrel

Then check it works:

$ ls /tmp/abs ../rel
ls: cannot access /tmp/abs: No such file or directory
ls: cannot access ../rel: No such file or directory

$ ha lf test.ha
HA 0.999� Copyright (c) 1995 Harri Hirvola

Archive : test.ha (2 files)

  filenameoriginalcompressed   rate datetime   m
 CRC-32path
 attr
===
  /tmp/abs0   0   100.0 %   2015-01-09  15:24  CPY
   (none)
 -rw-r--r--
---
  ../rel  0   0   100.0 %   2015-01-09  15:24  CPY
   (none)
 -rw-r--r--
===
  2   0   0   100.0 %

$ ha x test.ha
HA 0.999� Copyright (c) 1995 Harri Hirvola

Archive : test.ha (2 files)

Unpacking CPY 100 %  /tmp/abs
Unpacking CPY 100 %  ../rel

$ ls /tmp/abs ../rel
../rel  /tmp/abs

2. Through path part.

A sample archive could be prepared in following way:

$ mkdir Xtmp/ XX/
$ touch Xtmp/abs XX/rel
$ ha a test.ha Xtmp/abs XX/rel
$ sed -i 's|Xtmp|/tmp|g;s|XX|..|g' test.ha
$ rm -r Xtmp/ XX/

Then check it works:

$ ls /tmp/abs ../rel
ls: cannot access /tmp/abs: No such file or directory
ls: cannot access ../rel: No such file or directory

$ ha lf test.ha
HA 0.999� Copyright (c) 1995 Harri Hirvola

Archive : test.ha (2 files)

  filenameoriginalcompressed   rate datetime   m
 CRC-32path
 attr
===
  abs 0   0   100.0 %   2015-01-09  15:29  CPY
   /tmp/
 -rw-r--r--
---
  rel 0   0   100.0 %   2015-01-09  15:29  CPY
   ../
 -rw-r--r--
===
  2   0   0   100.0 %

$ ha x test.ha
HA 0.999� Copyright (c) 1995 Harri Hirvola

Archive : test.ha (2 files)

Unpacking CPY 100 %  /tmp/abs
Unpacking CPY 100 %  ../rel

$ ls /tmp/abs ../rel
../rel  /tmp/abs

--
Alexander Cherepanov
--- End Message ---
--- Begin Message ---
Version: 0.999p+dfsg-5+rm

Dear submitter,

as the package ha has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/822512

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---


Bug#724387: marked as done (Please stop build depending on automake1.9)

2016-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2016 17:34:12 +
with message-id 
and subject line Bug#822510: Removed package(s) from unstable
has caused the Debian Bug report #724387,
regarding Please stop build depending on automake1.9
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.)


-- 
724387: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724387
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gwhere
Version: 0.2.3.dfsg.1-4
Severity: wishlist
Usertags: automake-cleanup-2013

As documented in
http://lists.debian.org/debian-devel/2013/05/msg01459.html, I will be
removing automake1.4, automake1.9 and automake1.10 from the archive.
Your package has a build dependency on one (or more) of these
packages.

In many cases these dependencies are unnecessary as there is typically
no build time dependency on automake for most packages. If it is
required, you should update the dependency to "automake" or
"automake1.11". If you need any assistance with making your package
work with a newer version of automake, please let me know, but it
should be relatively painless for the most part.

I plan to ask for the removal of automake1.4, automake1.9 and
automake1.10 in approximately one month. Once they removed this bug's
severity will be upgraded to "serious".
--- End Message ---
--- Begin Message ---
Version: 0.2.3.dfsg.1-4+rm

Dear submitter,

as the package gwhere has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/822510

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---


Bug#820602: marked as done (indicator-session: FTBFS: accounts-service-client.h:53:1: error: 'org_freedesktop_Accounts_list_cached_users_async' defined but not used [-Werror=unused-function])

2016-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2016 17:32:49 +
with message-id 
and subject line Bug#822508: Removed package(s) from unstable
has caused the Debian Bug report #820602,
regarding indicator-session: FTBFS: accounts-service-client.h:53:1: error: 
'org_freedesktop_Accounts_list_cached_users_async' defined but not used 
[-Werror=unused-function]
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.)


-- 
820602: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820602
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: indicator-session
Version: 0.3.96-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

indicator-session fails to build from source in unstable/amd64:

  [..]

  gcc -DHAVE_CONFIG_H -I. 
-I/home/lamby/temp/cdt.20160410134704.HJpE3M18fx.indicator-session/indicator-session-0.3.96/./src
 -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -pthread 
-I/usr/include/libdbusmenu-gtk-0.4 -I/usr/include/libdbusmenu-glib-0.4 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/libindicator-0.4 -I/usr/include/gtk-2.0 
-I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ 
-I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
-I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng16 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/pango-1.0 
-I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/freetype2 
-I/usr/include/PackageKit -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include  
-DLIBEXECDIR=\"/usr/lib/indicator-session\" -Wall -Werror 
-DG_LOG_DOMAIN=\"Indicator-Session\" -I/usr/include/gudev-1.0 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include  -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wall 
-Wno-error=deprecated-declarations -c -o 
indicator_session_service-users-service-dbus.o `test -f 'users-service-dbus.c' 
|| echo 
'/home/lamby/temp/cdt.20160410134704.HJpE3M18fx.indicator-session/indicator-session-0.3.96/./src/'`users-service-dbus.c
  In file included from 
/home/lamby/temp/cdt.20160410134704.HJpE3M18fx.indicator-session/indicator-session-0.3.96/./src/users-service-dbus.c:36:0:
  
/home/lamby/temp/cdt.20160410134704.HJpE3M18fx.indicator-session/indicator-session-0.3.96/./src/accounts-service-client.h:53:1:
 error: 'org_freedesktop_Accounts_list_cached_users_async' defined but not used 
[-Werror=unused-function]
   org_freedesktop_Accounts_list_cached_users_async (DBusGProxy *proxy, 
org_freedesktop_Accounts_list_cached_users_reply callback, gpointer userdata)
   ^
  
/home/lamby/temp/cdt.20160410134704.HJpE3M18fx.indicator-session/indicator-session-0.3.96/./src/accounts-service-client.h:67:1:
 error: 'org_freedesktop_Accounts_find_user_by_id' defined but not used 
[-Werror=unused-function]
   org_freedesktop_Accounts_find_user_by_id (DBusGProxy *proxy, const gint64 
IN_id, char** OUT_user, GError **error)
   ^
  
/home/lamby/temp/cdt.20160410134704.HJpE3M18fx.indicator-session/indicator-session-0.3.96/./src/accounts-service-client.h:91:1:
 error: 'org_freedesktop_Accounts_find_user_by_id_async' defined but not used 
[-Werror=unused-function]
   org_freedesktop_Accounts_find_user_by_id_async (DBusGProxy *proxy, const 
gint64 IN_id, org_freedesktop_Accounts_find_user_by_id_reply callback, gpointer 
userdata)
   ^
  
/home/lamby/temp/cdt.20160410134704.HJpE3M18fx.indicator-session/indicator-session-0.3.96/./src/accounts-service-client.h:105:1:
 error: 'org_freedesktop_Accounts_find_user_by_name' defined but not used 
[-Werror=unused-function]
   org_freedesktop_Accounts_find_user_by_name (DBusGProxy *proxy, const char * 
IN_name, char** OUT_user, GError **error)
   ^
  
/home/lamby/temp/cdt.20160410134704.HJpE3M18fx.indicator-session/indicator-session-0.3.96/./src/accounts-service-client.h:129:1:
 error: 'org_freedesktop_Accounts_find_user_by_name_async' defined but not used 
[-Werror=unused-function]
   org_freedesktop_Accounts_find_user_by_name_async (DBusGProxy *proxy, const 
char * IN_name, org_freedesktop_Accounts_find_user_by_name_reply callback, 
gpointer userdata)
   ^
  
/home/lamby/temp/cdt.20160410134704.HJpE3M18fx.indicator-session/indicator-session-0.3.96/./src/accounts-service-client.h:143:1:
 error: 'org_freedesktop_Accounts_create_user' defined but not used 
[-Werror=unused-function]
   org_freedesktop_Accounts_create_user 

Bug#724918: marked as done (gwhere: FTBFS with make 3.82: Makefile:206: *** missing separator. Stop.)

2016-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2016 17:34:12 +
with message-id 
and subject line Bug#822510: Removed package(s) from unstable
has caused the Debian Bug report #724918,
regarding gwhere: FTBFS with make 3.82: Makefile:206: *** missing separator.  
Stop.
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.)


-- 
724918: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724918
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gwhere
Version: 0.2.3.dfsg.1-4
Severity: important
User: schep...@debian.org
Usertags: ftbfs-make3-82

>From my pbuilder build log, using a chroot image with make 3.82-1 from
experimental installed:

...
configure complete, type 'make' to compile GWhere

touch debian/stamp-autotools
/usr/bin/make  -C .  
make[1]: Entering directory `/tmp/buildd/gwhere-0.2.3.dfsg.1'
cd . && /bin/bash /tmp/buildd/gwhere-0.2.3.dfsg.1/missing --run autoheader
rm -f stamp-h1
touch config.h.in
cd . && /bin/bash ./config.status config.h
config.status: creating config.h
config.status: config.h is unchanged
/usr/bin/make  all-recursive
make[2]: Entering directory `/tmp/buildd/gwhere-0.2.3.dfsg.1'
Making all in slackware
make[3]: Entering directory `/tmp/buildd/gwhere-0.2.3.dfsg.1/slackware'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/tmp/buildd/gwhere-0.2.3.dfsg.1/slackware'
Making all in doc
make[3]: Entering directory `/tmp/buildd/gwhere-0.2.3.dfsg.1/doc'
Making all in license
make[4]: Entering directory `/tmp/buildd/gwhere-0.2.3.dfsg.1/doc/license'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory `/tmp/buildd/gwhere-0.2.3.dfsg.1/doc/license'
Making all in man
make[4]: Entering directory `/tmp/buildd/gwhere-0.2.3.dfsg.1/doc/man'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory `/tmp/buildd/gwhere-0.2.3.dfsg.1/doc/man'
make[4]: Entering directory `/tmp/buildd/gwhere-0.2.3.dfsg.1/doc'
make[4]: Nothing to be done for `all-am'.
make[4]: Leaving directory `/tmp/buildd/gwhere-0.2.3.dfsg.1/doc'
make[3]: Leaving directory `/tmp/buildd/gwhere-0.2.3.dfsg.1/doc'
Making all in intl
make[3]: Entering directory `/tmp/buildd/gwhere-0.2.3.dfsg.1/intl'
Makefile:206: *** missing separator.  Stop.
make[3]: Leaving directory `/tmp/buildd/gwhere-0.2.3.dfsg.1/intl'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/tmp/buildd/gwhere-0.2.3.dfsg.1'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/tmp/buildd/gwhere-0.2.3.dfsg.1'
make: *** [debian/stamp-makefile-build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

(It does build fine with a vanilla pbuilder chroot, with make 3.82-8.2
installed.)
-- 
Daniel Schepler
--- End Message ---
--- Begin Message ---
Version: 0.2.3.dfsg.1-4+rm

Dear submitter,

as the package gwhere has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/822510

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---


Bug#685814: marked as done (phpgacl: prompting due to modified conffiles which were not modified by the user)

2016-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2016 17:34:55 +
with message-id 
and subject line Bug#822511: Removed package(s) from unstable
has caused the Debian Bug report #685814,
regarding phpgacl: prompting due to modified conffiles which were not modified 
by the user
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.)


-- 
685814: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685814
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: phpgacl
Version: 3.3.7-7.3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed the piuparts
upgrade test because dpkg detected a conffile as being modified and then
prompted the user for an action. As there is no user input, this fails.
But this is not the real problem, the real problem is that this prompt
shows up in the first place, as there was nobody modifying this conffile
at all, the package has just been installed and upgraded...

This is a violation of policy 10.7.3, see
http://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3,
which says "[These scripts handling conffiles] must not ask unnecessary
questions (particularly during upgrades), and must otherwise be good
citizens."

http://wiki.debian.org/DpkgConffileHandling should help with figuring
out how to do this properly.

In http://lists.debian.org/debian-devel/2009/08/msg00675.html and
followups it has been agreed that these bugs are to be filed with
severity serious.

>From the attached log (scroll to the bottom...):

  Setting up phpgacl (3.3.7-7.3) ...
  
  Configuration file `/etc/phpgacl/gacl.ini.php'
   ==> Modified (by you or by a script) since installation.
   ==> Package distributor has shipped an updated version.
 What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
   The default action is to keep your current version.
  *** gacl.ini.php (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing phpgacl 
(--configure):
   EOF on stdin at conffile prompt
  Errors were encountered while processing:
   phpgacl

This was observed during an upgrade from testing to sid.


cheers,

Andreas
--- End Message ---
--- Begin Message ---
Version: 3.3.7-7.3+rm

Dear submitter,

as the package phpgacl has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/822511

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---


Bug#820785: transmission: FTBFS: m4/glib-gettext.m4:39: error: m4_copy: won't overwrite defined macro: glib_DEFUN

2016-04-25 Thread Chris Lamb
> Chris, do you have an idea how many packages are affected?

Sorry, no.

> Have you done a full archive rebuild since 23 Mar 2016, when glib20
> 2.48.0-1 was uploaded to unstable?

I have not.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-



Bug#741798: marked as done (indicator-messages: FTBFS: indicator-messages.c:435:2: error: 'gtk_widget_get_style' is deprecated: Use 'gtk_widget_get_style_context' instead [-Werror=deprecated-declarati

2016-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2016 17:33:28 +
with message-id 
and subject line Bug#822509: Removed package(s) from unstable
has caused the Debian Bug report #741798,
regarding indicator-messages: FTBFS: indicator-messages.c:435:2: error: 
'gtk_widget_get_style' is deprecated: Use 'gtk_widget_get_style_context' 
instead [-Werror=deprecated-declarations]
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.)


-- 
741798: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741798
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: indicator-messages
Version: 0.6.0-1.1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140315 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
> -I/«PKGBUILDDIR»/./src -I..   -D_FORTIFY_SOURCE=2 -pthread 
> -I/usr/include/gtk-3.0 -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 
> -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
> -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz 
> -I/usr/include/freetype2 -I/usr/include/pixman-1 -I/usr/include/libpng12 
> -I/usr/include/libdrm -I/usr/include/libdbusmenu-glib-0.4 
> -I/usr/include/libdbusmenu-gtk3-0.4 -I/usr/include/libindicator3-0.4 
> -I/usr/include/libindicate-0.7-Wall -Wl,-Bsymbolic-functions -Wl,-z,defs 
> -Wl,--as-needed -Werror -DG_LOG_DOMAIN=\"Indicator-Messages\" -g -O2 
> -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security 
> -Wall -c -o libmessaging_la-indicator-messages.lo `test -f 
> 'indicator-messages.c' || echo '/«PKGBUILDDIR»/./src/'`indicator-messages.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I/«PKGBUILDDIR»/./src -I.. 
> -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/gtk-3.0 -I/usr/include/atk-1.0 
> -I/usr/include/at-spi2-atk/2.0 -I/usr/include/pango-1.0 
> -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
> -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz 
> -I/usr/include/freetype2 -I/usr/include/pixman-1 -I/usr/include/libpng12 
> -I/usr/include/libdrm -I/usr/include/libdbusmenu-glib-0.4 
> -I/usr/include/libdbusmenu-gtk3-0.4 -I/usr/include/libindicator3-0.4 
> -I/usr/include/libindicate-0.7 -Wall -Wl,-Bsymbolic-functions -Wl,-z,defs 
> -Wl,--as-needed -Werror -DG_LOG_DOMAIN=\"Indicator-Messages\" -g -O2 
> -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security 
> -Wall -c /«PKGBUILDDIR»/./src/indicator-messages.c  -fPIC -DPIC -o 
> .libs/libmessaging_la-indicator-messages.o
> /«PKGBUILDDIR»/./src/indicator-messages.c: In function 
> 'application_triangle_draw_cb':
> /«PKGBUILDDIR»/./src/indicator-messages.c:435:2: error: 
> 'gtk_widget_get_style' is deprecated (declared at 
> /usr/include/gtk-3.0/gtk/deprecated/gtkstyle.h:672): Use 
> 'gtk_widget_get_style_context' instead [-Werror=deprecated-declarations]
>   style = gtk_widget_get_style (widget);
>   ^
> /«PKGBUILDDIR»/./src/indicator-messages.c:464:2: error: 
> 'gtk_widget_get_state' is deprecated (declared at 
> /usr/include/gtk-3.0/gtk/gtkwidget.h:678): Use 'gtk_widget_get_state_flags' 
> instead [-Werror=deprecated-declarations]
>   cairo_set_source_rgb (cr, 
> style->fg[gtk_widget_get_state(widget)].red/65535.0,
>   ^
> /«PKGBUILDDIR»/./src/indicator-messages.c:465:28: error: 
> 'gtk_widget_get_state' is deprecated (declared at 
> /usr/include/gtk-3.0/gtk/gtkwidget.h:678): Use 'gtk_widget_get_state_flags' 
> instead [-Werror=deprecated-declarations]
> 
> style->fg[gtk_widget_get_state(widget)].green/65535.0,
> ^
> /«PKGBUILDDIR»/./src/indicator-messages.c:466:28: error: 
> 'gtk_widget_get_state' is deprecated (declared at 
> /usr/include/gtk-3.0/gtk/gtkwidget.h:678): Use 'gtk_widget_get_state_flags' 
> instead [-Werror=deprecated-declarations]
> 
> style->fg[gtk_widget_get_state(widget)].blue/65535.0);
> ^
> /«PKGBUILDDIR»/./src/indicator-messages.c: In function 'numbers_draw_cb':
> /«PKGBUILDDIR»/./src/indicator-messages.c:535:2: error: 
> 'gtk_widget_get_style' is deprecated (declared at 
> /usr/include/gtk-3.0/gtk/deprecated/gtkstyle.h:672): Use 
> 'gtk_widget_get_style_context' instead [-Werror=deprecated-declarations]
>   style = 

Processed: [bts-link] source package libsoup2.4

2016-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package libsoup2.4
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #821274 (http://bugs.debian.org/821274)
> # Bug title: libsoup2.4-1: 2.54 upgrade breaks caldav/webdav support in 
> evolution
> #  * http://bugzilla.gnome.org/show_bug.cgi?id=765222
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 821274 + fixed-upstream
Bug #821274 {Done: Michael Biebl } [libsoup2.4-1] 
libsoup2.4-1: 2.54 upgrade breaks caldav/webdav support in evolution
Added tag(s) fixed-upstream.
> usertags 821274 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: status-RESOLVED resolution-FIXED.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
821274: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821274
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#659390: marked as done (semanticscuttle: config.default.php not found)

2016-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2016 17:32:09 +
with message-id 
and subject line Bug#822507: Removed package(s) from unstable
has caused the Debian Bug report #659390,
regarding semanticscuttle: config.default.php not found
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.)


-- 
659390: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659390
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: semanticscuttle
Version: 0.98.3+dfsg-5
Severity: important


The browser addressed to host with semanticscuttle shows this error message:

No default configuration file config.default.php found. This is really, really 
strange


-- System Information:
Debian Release: 6.0.4
  APT prefers stable
  APT policy: (900, 'stable'), (850, 'testing'), (500, 'stable-updates')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-0.bpo.1-486
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages semanticscuttle depends on:
ii  apache2-mpm-prefork  2.2.16-6+squeeze6   Apache HTTP Server - traditional n
ii  dbconfig-common  1.8.47+nmu1 common framework for packaging dat
ii  debconf [debconf-2.0 1.5.36.1Debian configuration management sy
ii  libjs-jquery-ui  1.8.ooops.17+dfsg-1 JavaScript UI library for dynamic 
ii  mysql-client-5.1 [my 5.1.58-1MySQL database client binaries
ii  php-gettext  1.0.10-1read gettext MO files directly, wi
ii  php5 5.3.3-7+squeeze7server-side, HTML-embedded scripti
ii  php5-mysql   5.3.9-1 MySQL module for php5
ii  thttpd [httpd]   2.25b-11tiny/turbo/throttling HTTP server
ii  wwwconfig-common 0.2.1   Debian web auto configuration

semanticscuttle recommends no packages.

Versions of packages semanticscuttle suggests:
ii  mysql-server-5.1 [mysql-serve 5.1.58-1   MySQL database server binaries and

-- Configuration Files:
/etc/semanticscuttle/config.php [Errno 2] File o directory non esistente: 
u'/etc/semanticscuttle/config.php'

-- debconf information:
  semanticscuttle/mysql/method: unix socket
  semanticscuttle/remote/port:
  semanticscuttle/dbconfig-reinstall: false
  semanticscuttle/db/dbname: semanticscuttle
  semanticscuttle/remote/host:
  semanticscuttle/upgrade-backup: true
  semanticscuttle/dbconfig-upgrade: true
  semanticscuttle/webserver:
  semanticscuttle/database-type: mysql
  semanticscuttle/db/app-user: semanticscuttle
  semanticscuttle/remove-error: abort
  semanticscuttle/upgrade-error: abort
  semanticscuttle/install-error: retry
  semanticscuttle/internal/skip-preseed: false
  semanticscuttle/passwords-do-not-match:
  semanticscuttle/mysql/admin-user: root
  semanticscuttle/remote/newhost:
  semanticscuttle/internal/reconfiguring: false
  semanticscuttle/missing-db-package-error: abort
* semanticscuttle/dbconfig-install: true
  semanticscuttle/dbconfig-remove:
  semanticscuttle/purge: false


--- End Message ---
--- Begin Message ---
Version: 0.98.5+dfsg-1+rm

Dear submitter,

as the package semanticscuttle has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/822507

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---


Bug#821274: marked as done (libsoup2.4-1: 2.54 upgrade breaks caldav/webdav support in evolution)

2016-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2016 17:24:13 +
with message-id 
and subject line Bug#821274: fixed in libsoup2.4 2.54.0.1-2
has caused the Debian Bug report #821274,
regarding libsoup2.4-1: 2.54 upgrade breaks caldav/webdav support in evolution
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.)


-- 
821274: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821274
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsoup2.4-1
Version: 2.54.0.1-1
Severity: important

Hi,

it seems that the 2.54 upload of libsoup broke evolution caldav support
here. I'm using caldav support for calendar, addressbooks and memos, and
with the 2.54 upgrade the connections just timeout, and actually no
packet leaves the interface.

I've tried downgrading the packages to 2.52 and it does fix the problem.
It might be an issue in evolution requiring a binNMU or even a patch, no
idea, so feel free to reassign if needed.

If you need more information, please ask.

Regards,

-- 
Yves-Alexis

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable'), (450, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-1-grsec-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libsoup2.4-1 depends on:
ii  glib-networking   2.48.0-1
ii  libc6 2.22-6
ii  libcomerr21.43~WIP.2016.03.15-2
ii  libglib2.0-0  2.48.0-1
ii  libgssapi-krb5-2  1.13.2+dfsg-5
ii  libk5crypto3  1.13.2+dfsg-5
ii  libkrb5-3 1.13.2+dfsg-5
ii  libsqlite3-0  3.12.1-1
ii  libxml2   2.9.3+dfsg1-1

libsoup2.4-1 recommends no packages.

libsoup2.4-1 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libsoup2.4
Source-Version: 2.54.0.1-2

We believe that the bug you reported is fixed in the latest version of
libsoup2.4, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 821...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated libsoup2.4 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 25 Apr 2016 18:35:49 +0200
Source: libsoup2.4
Binary: libsoup2.4-dev libsoup2.4-1 libsoup-gnome2.4-1 libsoup-gnome2.4-dev 
libsoup2.4-doc gir1.2-soup-2.4
Architecture: source
Version: 2.54.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Michael Biebl 
Description:
 gir1.2-soup-2.4 - GObject introspection data for the libsoup HTTP library
 libsoup-gnome2.4-1 - HTTP library implementation in C -- GNOME support library
 libsoup-gnome2.4-dev - HTTP library implementation in C -- GNOME support 
development fil
 libsoup2.4-1 - HTTP library implementation in C -- Shared library
 libsoup2.4-dev - HTTP library implementation in C -- Development files
 libsoup2.4-doc - HTTP library implementation in C -- API Reference
Closes: 821274
Changes:
 libsoup2.4 (2.54.0.1-2) unstable; urgency=medium
 .
   * Fix SoupAuthClass size to undo ABI break with 2.54.0. Patch cherry-picked
 from upstream Git. (Closes: #821274)
Checksums-Sha1:
 73dcd8d52d8f86d2dc8065fabdd96411e24efd36 2778 libsoup2.4_2.54.0.1-2.dsc
 f68b9d448c919f2c0beb22f1dcf2caaad159ae03 15784 
libsoup2.4_2.54.0.1-2.debian.tar.xz
Checksums-Sha256:
 cffa7af307ebc86ead7a2c4a6322ba530701a9bbbe4c3d1d672ef68872933a0f 2778 
libsoup2.4_2.54.0.1-2.dsc
 ccfdbd05f99a413f01ed9df0763f34128e36d0c43fb75b879a650cb0aa70c74a 15784 
libsoup2.4_2.54.0.1-2.debian.tar.xz
Files:
 d2cd508313e496ec20e84ed1d245e7ba 2778 devel optional libsoup2.4_2.54.0.1-2.dsc
 b0d11c40ebdc7a351270a25faa9ed4a8 15784 devel optional 
libsoup2.4_2.54.0.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXHkeDAAoJEGrh3w1gjyLcpa0P/RhfVH/Y5Q1zKKx8YcA4HaR7

Bug#816780: marked as done (roundup: CVE-2014-6276: information leak)

2016-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2016 17:23:18 +
with message-id 
and subject line Bug#822335: Removed package(s) from unstable
has caused the Debian Bug report #816780,
regarding roundup: CVE-2014-6276: information leak
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.)


-- 
816780: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816780
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: roundup
Version: 1.4.20-1
Severity: grave
Tags: security upstream fixed-upstream wheezy jessie stretch sid

Hi

https://www.debian.org/security/2016/dsa-3502:
|Ralf Schlatterbeck discovered an information leak in roundup, a
|web-based issue tracking system. An authenticated attacker could use
|it to see sensitive details about other users, including their hashed
|password.

The purpose of this bug is to have a RC bug for roundup. roundup has
long seen any new upstream releases. 

>From Kai Storbeck it looks the way forward would be to have roundup
removed for unstable and stretch. Kai can you confirm that this is
still the plan vs. update to new upstream releases?

If so can you fill afer discussion with the Python App team a removal
request?

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Version: 1.4.20-1.1+deb8u1+rm

Dear submitter,

as the package roundup has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/822335

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---


Bug#821209: marked as done (codec2: non-free files)

2016-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2016 17:21:32 +
with message-id 
and subject line Bug#821209: fixed in codec2 0.5.1-1
has caused the Debian Bug report #821209,
regarding codec2: non-free files
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.)


-- 
821209: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821209
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: codec2
Version: 0.5-3
Severity: serious
Usertags: dfsg

File "src/golay23.c" contains the following copyright notice:


 This computer program is free for non-commercial purposes.
 You may implement this program for any non-commercial application. You may
 also implement this program for commercial purposes, provided that you
 obtain my written permission. Any modification of this program is covered
 by this copyright.


-- 
Regards,
 Dmitry Smirnov
 GPG key : 4096R/53968D1B


signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Source: codec2
Source-Version: 0.5.1-1

We believe that the bug you reported is fixed in the latest version of
codec2, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 821...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
A. Maitland Bottoms  (supplier of updated codec2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 25 Apr 2016 09:54:12 -0400
Source: codec2
Binary: codec2 codec2-examples libcodec2-0.4 libcodec2-dev
Architecture: source amd64 all
Version: 0.5.1-1
Distribution: unstable
Urgency: medium
Maintainer: A. Maitland Bottoms 
Changed-By: A. Maitland Bottoms 
Description:
 codec2 - command line tools for handling Codec2 data
 codec2-examples - Codec2 sample data and examples
 libcodec2-0.4 - Codec2 runtime library
 libcodec2-dev - Codec2 library development files
Closes: 821209
Changes:
 codec2 (0.5.1-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #821209)
 rewritten src/golay23.c (Thanks Tomas)
Checksums-Sha1:
 11c6bd12a312e5771d1020fdbccd7bc35a7c0847 2039 codec2_0.5.1-1.dsc
 dcac0544048787a07a891e71c77fbf9ae3d78aca 7862968 codec2_0.5.1.orig.tar.xz
 b659f62faf8903a6389659f8554feeaf83bf18a5 31544 codec2_0.5.1-1.debian.tar.xz
 ea419b9b7dbc22d62b684db251d8355d8e34179e 58710 codec2-dbgsym_0.5.1-1_amd64.deb
 d1ecfc7f1854f27c9badae60e97f60f827183509 5221182 
codec2-examples_0.5.1-1_all.deb
 9f1e0a4d13500037d93de7af16477bd2457a5483 37660 codec2_0.5.1-1_amd64.deb
 c578ec128beffab66bdc3b12fa327b58ce427821 103454 
libcodec2-0.4-dbgsym_0.5.1-1_amd64.deb
 d11074979c9267b7bcba890a3ed076f1c1d9eebb 118084 libcodec2-0.4_0.5.1-1_amd64.deb
 ec85c75d559b282e1bbb04a852bf39782934aaf1 18104 libcodec2-dev_0.5.1-1_amd64.deb
Checksums-Sha256:
 4944cc49d5b92497df2da96fe60a119893e8169cc309d501439db1d531d8e5af 2039 
codec2_0.5.1-1.dsc
 f7cf14b02763ffdcd231027f9811b06862790bf76d900ba9443d2a57f4ce7b38 7862968 
codec2_0.5.1.orig.tar.xz
 f444d1023c03fb2dce23ef85c6701ee02964a6c21c513ba3d12ae956282a266b 31544 
codec2_0.5.1-1.debian.tar.xz
 d4e88d1092fdfd70014899862b6dbf49eee2bbb3166fb8620cf72c4d56a9b10a 58710 
codec2-dbgsym_0.5.1-1_amd64.deb
 deae176699c8f92cc580f3aa9a9a5e01ae9ba2f6adbe386aeb7550ded4f3e79d 5221182 
codec2-examples_0.5.1-1_all.deb
 903dd6f718822802680185e1232234fe86b7f56744a6b3355fc1fd7b9da7e2ce 37660 
codec2_0.5.1-1_amd64.deb
 b44ed48f18c731dbc6f9729a2a8ce052fcb64cc43c5856d93d49ed00fdfd5b0a 103454 
libcodec2-0.4-dbgsym_0.5.1-1_amd64.deb
 b5e08b64fd20a023c270ce5bdfb77c7991a1041c0ca0df0954c5b9351c32d2f3 118084 
libcodec2-0.4_0.5.1-1_amd64.deb
 09ffdc8d48f18f759258a53d62080ab25889bb465d5bdca5f1f3d2c77da9 18104 
libcodec2-dev_0.5.1-1_amd64.deb
Files:
 980cfda6a41956d6b3d49cd605b390c2 2039 sound optional codec2_0.5.1-1.dsc
 1f62f89f7e5f60ea7b02024808e51bf6 7862968 sound optional 
codec2_0.5.1.orig.tar.xz
 3763fe9972adf8dd505da3bfe39903ef 31544 sound optional 
codec2_0.5.1-1.debian.tar.xz
 18aec92558fcf587e5da3962bcf5db4d 58710 debug extra 
codec2-dbgsym_0.5.1-1_amd64.deb
 6ee1c197ed8f68196c93884533e22725 5221182 sound optional 

Bug#820785: transmission: FTBFS: m4/glib-gettext.m4:39: error: m4_copy: won't overwrite defined macro: glib_DEFUN

2016-04-25 Thread Michael Biebl
This was apparently triggered by a change in libglib2.0-dev.

Chris, do you have an idea how many packages are affected?
Have you done a full archive rebuild since 23 Mar 2016, when glib20
2.48.0-1 was uploaded to unstable?

Regards,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Bug#822617: Missing symlinks to match locales

2016-04-25 Thread Gunnar Hjalmarsson
Package: libreoffice-dictionaries
Version: 1:5.1.2-1
Severity: grave

Forwarding the Ubuntu bug .

Several dictionaries are installed under names which don't specify the
country codes. Examples:

/usr/share/hunspell/es_ANY.dic
/usr/share/hyphen/hyph_sv.dic

In those cases LibreOffice does not recognize them as available.
Symlinks seem to be needed; please see example in the Ubuntu bug.

-- 
Gunnar Hjalmarsson
https://launchpad.net/~gunnarhj



Bug#812096: marked as done (smc: FTBFS: configure: error: Package requirements (CEGUI-OPENGL >= 0.7.2) were not met:)

2016-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2016 17:17:54 +
with message-id 
and subject line Bug#822169: Removed package(s) from unstable
has caused the Debian Bug report #812096,
regarding smc: FTBFS: configure: error: Package requirements (CEGUI-OPENGL >= 
0.7.2) were not met:
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.)


-- 
812096: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812096
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: smc
Version: 1.9+git20121121-1.2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

smc fails to build from source in unstable/amd64:

  [..]

  cd . &&   CFLAGS="-g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wall" CXXFLAGS="-g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -Wall" CPPFLAGS="-Wdate-time 
-D_FORTIFY_SOURCE=2" LDFLAGS="-Wl,-z,relro -lboost_system" 
/home/lamby/temp/cdt.20160120150439.uTPv8ahNyp/smc-1.9+git20121121/./configure 
--build=x86_64-linux-gnu  --prefix=/usr --includedir="\${prefix}/include" 
--mandir="\${prefix}/share/man" --infodir="\${prefix}/share/info" 
--sysconfdir=/etc --localstatedir=/var --libexecdir="\${prefix}/lib/smc" 
--srcdir=. --disable-maintainer-mode --disable-dependency-tracking 
--disable-silent-rules   
--prefix=/home/lamby/temp/cdt.20160120150439.uTPv8ahNyp/smc-1.9+git20121121/debian/tmp//usr
 --bindir=/usr/games --datadir=/usr/share/games 
  configure: WARNING: unrecognized options: --disable-maintainer-mode
  checking build system type... x86_64-pc-linux-gnu
  checking host system type... x86_64-pc-linux-gnu
  checking for a BSD-compatible install... /usr/bin/install -c
  checking whether build environment is sane... yes
  checking for a thread-safe mkdir -p... /bin/mkdir -p
  checking for gawk... no
  checking for mawk... mawk
  checking whether make sets $(MAKE)... yes
  checking whether make supports nested variables... yes
  checking whether make supports nested variables... (cached) yes
  checking for g++... g++
  checking whether the C++ compiler works... yes
  checking for C++ compiler default output file name... a.out
  checking for suffix of executables... 
  checking whether we are cross compiling... no
  checking for suffix of object files... o
  checking whether we are using the GNU C++ compiler... yes
  checking whether g++ accepts -g... yes
  checking for style of include used by make... GNU
  checking dependency style of g++... none
  checking for pkg-config... /usr/bin/pkg-config
  checking pkg-config is at least version 0.9.0... yes
  checking for main in -lboost_filesystem... yes
  checking for main in -lboost_thread... yes
  checking for main in -lboost_system... yes
  checking for main in -lX11... yes
  checking for main in -lGL... yes
  checking for main in -lGLU... yes
  checking for SDL... yes
  checking for png_init_io in -lpng... yes
  checking for IMG_LoadPNG_RW in -lSDL_image... yes
  checking for IMG_Init in -lSDL_image... yes
  checking for Mix_OpenAudio in -lSDL_mixer... yes
  checking for TTF_Init in -lSDL_ttf... yes
  checking for CEGUI_OPENGL... no
  configure: error: Package requirements (CEGUI-OPENGL >= 0.7.2) were not met:
  
  No package 'CEGUI-OPENGL' found
  
  Consider adjusting the PKG_CONFIG_PATH environment variable if you
  installed software in a non-standard prefix.
  
  Alternatively, you may set the environment variables CEGUI_OPENGL_CFLAGS
  and CEGUI_OPENGL_LIBS to avoid the need to call pkg-config.
  See the pkg-config man page for more details.
  /usr/share/cdbs/1/class/autotools.mk:42: recipe for target 
'debian/stamp-autotools' failed
  make: *** [debian/stamp-autotools] Error 1

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


smc.1.9+git20121121-1.2.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Version: 1.9+git20121121-1.2+rm

Dear submitter,

as the package smc has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/822169

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that 

Bug#816440: openjdk-9-jdk: file conflict jawt.h, jawt_md.h

2016-04-25 Thread Andreas Beckmann
Followup-For: Bug #816440
Control: found -1 9~b115-2

Hi,

that problem is still here ...

  Selecting previously unselected package openjdk-9-jdk:amd64.
  (Reading database ... 
(Reading database ... 16970 files and directories currently installed.)
  Preparing to unpack .../openjdk-9-jdk_9~b115-2_amd64.deb ...
  Unpacking openjdk-9-jdk:amd64 (9~b115-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/openjdk-9-jdk_9~b115-2_amd64.deb (--unpack):
   trying to overwrite 
'/usr/lib/jvm/java-9-openjdk-amd64/include/linux/jawt_md.h', which is also in 
package openjdk-9-jdk-headless:amd64 9~b115-2
  Errors were encountered while processing:
   /var/cache/apt/archives/openjdk-9-jdk_9~b115-2_amd64.deb

According to the Contents file, 
these two files are shipped by both packages:

  usr/lib/jvm/java-9-openjdk-amd64/include/jawt.h
  usr/lib/jvm/java-9-openjdk-amd64/include/linux/jawt_md.h


Andreas



Processed: Re: openjdk-9-jdk: file conflict jawt.h, jawt_md.h

2016-04-25 Thread Debian Bug Tracking System
Processing control commands:

> found -1 9~b115-2
Bug #816440 {Done: Matthias Klose } [openjdk-9-jdk] 
openjdk-9-jdk: file conflict jawt.h
Marked as found in versions openjdk-9/9~b115-2 and reopened.

-- 
816440: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816440
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#778599: marked as done (Vulnerabilities in nanohttp)

2016-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2016 17:11:04 +
with message-id 
and subject line Bug#822079: Removed package(s) from unstable
has caused the Debian Bug report #778599,
regarding Vulnerabilities in nanohttp
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.)


-- 
778599: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778599
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcsoap1
Version: 1.1.0-17.2

Per discussion on debian-security -

A number of vulnerabilities exist in nanohttp, a lightweight webserver
included in the libcsoap package. Patches are provided below against
1.1.0-17.2 (unstable).

* Remote buffer overflow
If the server is misconfigured, a remote user can trigger a buffer
overflow by requesting a resource of a certain length.
http://patrick.ld.net.au/libcsoap/nanohttp-buffer-1.patch

* Remote null pointer dereference
A remote user can cause a null pointer dereference by sending a
malformed Authorization: header.
http://patrick.ld.net.au/libcsoap/nanohttp-nullp-1.patch

If you require any further information, don't hesitate to let me know.

Cheers,

Patrick
--- End Message ---
--- Begin Message ---
Version: 1.1.0-17.2+rm

Dear submitter,

as the package libcsoap has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/822079

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---


Bug#821274: libsoup2.4-1: 2.54 upgrade breaks caldav/webdav support in evolution

2016-04-25 Thread Michael Biebl
Am 17.04.2016 um 19:16 schrieb Alban Browaeys:
> Package: libsoup2.4
> Version: 2.54.0.1-1
> Followup-For: Bug #821274
> 
> Dear Maintainer,
> There caldav is broken too. 
> 
> "CALDAV_DEBUG=all /usr/lib/evolution/evolution-calendar-factory" , when I 
> enable a caldav source back in the evolution UI, gives:
> "
> (evolution-calendar-factory-subprocess:11633): GLib-GObject-WARNING **: 
> specified class size for type 'ESoupAuthBearer' is smaller than the parent 
> type's 'SoupAuth' class size
> 
> (evolution-calendar-factory-subprocess:11633): GLib-CRITICAL **: 
> g_once_init_leave: assertion 'result != 0' failed
> "
> 
> To me this points to a change in libsoup.
> Likely 
> https://git.gnome.org/browse/libsoup/commit/libsoup/soup-auth.h?id=6a8826f0d25459c943719b88f22619f22b81c547

Thanks a lot Alban,for investigating and forwarding it upstream.
I've cherry-picked the fix and uploaded -2

Regards,
Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Bug#816980: [Pkg-julia-devel] Bug#816980: julia: FTBFS in testing (signal (11): Segmentation fault)

2016-04-25 Thread Santiago Vila
On Mon, Apr 25, 2016 at 09:15:35AM -0700, Tony Kelman wrote:
> Probably because the Debian build isn't using the stable, tested,
> recommended and supported version of LLVM for that branch of Julia. LLVM
> makes significant breaking changes to all of their API's between minor
> versions, so removing old versions from Debian means downstream users of
> LLVM end up broken or with serious performance and memory regressions.

Well, this is Debian testing and unstable what we are talking about.

If the Debian maintainers of Julia decided to use the latest LLVM compiler,
not the stable version that you recommend, I guess it's because they are
willing to help Debian as a whole to discover and fix any remaining LLVM
bugs (for example, this one if it were a LLVM bug) before the current
Debian testing becomes the next Debian stable.

In principle, this should be good for Debian and also good for Julia,
because it is this way that you will be able to recommend, say, LLVM 3.8,
when all of the bugs have been fixed and it's as stable as the older
LLVM versions.

Also, please note that I'm not speaking as an "end user" here. I'm just
a Debian maintainer with some interest on QA issues.

Thanks.



Processed: Bug#822489 marked as pending

2016-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tag 822489 pending
Bug #822489 [libc-bin] armhf ABI detection crashing ldconfig on arm64
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
822489: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822489
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#822489: marked as pending

2016-04-25 Thread Aurelien Jarno
tag 822489 pending
thanks

Hello,

Bug #822489 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://git.debian.org/?p=pkg-glibc/glibc.git;a=commitdiff;h=1148270

---
commit 11482702e09348848c8b18d754a8f4341a2549bc
Author: Aurelien Jarno 
Date:   Mon Apr 25 18:40:29 2016 +0200

patches/arm/unsubmitted-ldconfig-cache-abi.diff: apply fix from Steve 
McIntyre to fix an armhf ABI detection crash in ldconfig on arm64. Closes: 
#822489.

diff --git a/debian/changelog b/debian/changelog
index ce7dd9d..a5099dc 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -9,6 +9,9 @@ glibc (2.22-8) UNRELEASED; urgency=medium
   [ Aurelien Jarno ]
   * patches/kfreebsd/local-sysdeps.diff: update to revision 6015 (from
 glibc-bsd) to fix FTBFS.
+  * patches/arm/unsubmitted-ldconfig-cache-abi.diff: apply fix from Steve
+McIntyre to fix an armhf ABI detection crash in ldconfig on arm64.
+Closes: #822489.
 
  -- Samuel Thibault   Tue, 19 Apr 2016 23:28:29 +0200
 



Processed: Re: Bug#822515: surf: FTBFS: fatal error: gtk/gtk.h: No such file or directory

2016-04-25 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + moreinfo
Bug #822515 [surf] surf: FTBFS: fatal error: gtk/gtk.h: No such file or 
directory
Added tag(s) moreinfo.

-- 
822515: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822515
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#822515: surf: FTBFS: fatal error: gtk/gtk.h: No such file or directory

2016-04-25 Thread Reiner Herrmann
Control: tags -1 + moreinfo

Hi Martin,

I just tried to reproduce your build failure, but wasn't able to.
I used an up-to-date pbuilder with unstable on amd64, and also verified
on the reproducible builds infrastructure that it builds fine [1] [2].

> Package 'graphite2', required by 'harfbuzz', not found
> CC   = cc
> CC surf.c
> cc -c -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security 
> -std=c99 -pedantic -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -DVERSION=\"0.7\" 
> -D_DEFAULT_SOURCE -I. -I/usr/include -I/usr/X11R6/include  surf.c
> surf.c:8:21: fatal error: gtk/gtk.h: No such file or directory
> compilation terminated.
> Makefile:18: recipe for target 'surf.o' failed
> make[1]: *** [surf.o] Error 1
> make[1]: Leaving directory '/<>'
> dh_auto_build: make -j30 returned exit code 2

There are quite a few flags missing, which are obtained by pkg-config.
Can you please provide a complete build log, including the installation
of dependencies?

Kind regards,
  Reiner

[1]: https://tests.reproducible-builds.org/rb-pkg/unstable/amd64/surf.html
[2]: 
https://tests.reproducible-builds.org/rbuild/unstable/amd64/surf_0.7-1.rbuild.log


signature.asc
Description: Digital signature


Bug#821100: [debian-mysql] Bug#821100: MySQL 5.5.49 for Oracle April 2016 CPU

2016-04-25 Thread Robie Basak
Hi Salvatore,

On Mon, Apr 25, 2016 at 04:54:03PM +0200, Salvatore Bonaccorso wrote:
> On Fri, Apr 22, 2016 at 09:52:44AM +0100, Robie Basak wrote:
> > On Thu, Apr 21, 2016 at 07:13:34PM +0200, Salvatore Bonaccorso wrote:
> > > Do you have any status-update for this for us?
> > 
> > Struggling to find an available and willing sponsor, sorry. Lars has had
> > his tree ready for a while.
> > 
> > I am DM for src:mysql-5.6, but not for src:mysql-5.5 (that's just a
> > technicality, I could be added I suppose) but I think you said that this
> > needs a DD?
> > 
> > Unfortunately this means that Lars passes his work to me for review, and
> > then I pass it to a sponsor for upload, so it's a bit slow.
> > 
> > My usual sponsoring DD for MySQL is also an Ubuntu dev and is busy this
> > week (it being Ubuntu release week) so hasn't been able to spare any
> > time for me on this. I'll continue to seek a sponsor.
> > 
> > If anyone else can help please, the trees are at:
> > 
> > http://anonscm.debian.org/cgit/pkg-mysql/mysql-5.5.git/log/
> > http://anonscm.debian.org/cgit/pkg-mysql/mysql-5.5.git/log/?h=debian/wheezy
> > 
> > In my judgement (as a DM for mysql-5.6), Lars' work here is correct and
> > ready to upload.
> 
> Did you got a reply from your sponsor? Btw, please not that by now --
> since wheezy security support will end tomorrow, and then handled over
> to the LTS team, we can only handle the jessie-security upload via the
> DSA.

Sorry, I missed your email on Friday. I saw it earlier today so prepared
the signed source packages. I spent some time doing some further testing
and uploaded the signed source packages to:

http://people.canonical.com/~rbasak/mysql-5.5/

In addition to the dep8 tests (not present in wheezy), I've also done a
quick smoke by hand. I understand that you may not be able to upload
wheezy but I figured that at least it's here for the LTS team if they
want to take it.

Robie



Bug#822578: marked as done (poppler: CVE-2015-8868: heap buffer overflow)

2016-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2016 16:32:25 +
with message-id 
and subject line Bug#822578: fixed in poppler 0.38.0-3
has caused the Debian Bug report #822578,
regarding poppler: CVE-2015-8868: heap buffer overflow
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.)


-- 
822578: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822578
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: poppler
Version: 0.38.0-2
Severity: important
Tags: security upstream patch fixed-upstream

Hi,

the following vulnerability was published for poppler.

CVE-2015-8868[0]:
heap overflow

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2015-8868
[1] 
https://cgit.freedesktop.org/poppler/poppler/commit/?id=b3425dd3261679958cd56c0f71995c15d2124433
[2] https://bugs.freedesktop.org/show_bug.cgi?id=93476

Please adjust the affected versions in the BTS as needed. Only source
for poppler in unstable has been checked by now.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: poppler
Source-Version: 0.38.0-3

We believe that the bug you reported is fixed in the latest version of
poppler, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 822...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pino Toscano  (supplier of updated poppler package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 25 Apr 2016 16:51:07 +0200
Source: poppler
Binary: libpoppler57 libpoppler-dev libpoppler-private-dev libpoppler-glib8 
libpoppler-glib-dev libpoppler-glib-doc gir1.2-poppler-0.18 libpoppler-qt4-4 
libpoppler-qt4-dev libpoppler-qt5-1 libpoppler-qt5-dev libpoppler-cpp0v5 
libpoppler-cpp-dev poppler-utils poppler-dbg
Architecture: source
Version: 0.38.0-3
Distribution: unstable
Urgency: medium
Maintainer: Loic Minier 
Changed-By: Pino Toscano 
Description:
 gir1.2-poppler-0.18 - GObject introspection data for poppler-glib
 libpoppler-cpp-dev - PDF rendering library -- development files (CPP interface)
 libpoppler-cpp0v5 - PDF rendering library (CPP shared library)
 libpoppler-dev - PDF rendering library -- development files
 libpoppler-glib-dev - PDF rendering library -- development files (GLib 
interface)
 libpoppler-glib-doc - PDF rendering library -- documentation for the GLib 
interface
 libpoppler-glib8 - PDF rendering library (GLib-based shared library)
 libpoppler-private-dev - PDF rendering library -- private development files
 libpoppler-qt4-4 - PDF rendering library (Qt 4 based shared library)
 libpoppler-qt4-dev - PDF rendering library -- development files (Qt 4 
interface)
 libpoppler-qt5-1 - PDF rendering library (Qt 5 based shared library)
 libpoppler-qt5-dev - PDF rendering library -- development files (Qt 5 
interface)
 libpoppler57 - PDF rendering library
 poppler-dbg - PDF rendering library -- debugging symbols
 poppler-utils - PDF utilities (based on Poppler)
Closes: 822578
Changes:
 poppler (0.38.0-3) unstable; urgency=medium
 .
   * Backport upstream commit b3425dd3261679958cd56c0f71995c15d2124433 to fix
 a crash on invalid files, reported also as CVE-2015-8868; patch
 upstream_Do-not-crash-on-invalid-files.patch. (Closes: #822578)
   * Update Vcs-* fields.
   * Bump Standards-Version to 3.9.8, no changes required.
Checksums-Sha1:
 3f09f64ac3c83b820ac750490c0afe8052e228bc 3268 poppler_0.38.0-3.dsc
 7539e98e216f2e1379ba452ef053effc56b54b5b 30180 poppler_0.38.0-3.debian.tar.xz
Checksums-Sha256:
 ba0347c59eb51c3c850e5828d2295ac7ffcc65e737ead405f06f128ce8ce0473 3268 
poppler_0.38.0-3.dsc
 50ca62202170f746a00ecd9489a2ac8771261d5367aa1c7317dc59af97d6cf85 30180 
poppler_0.38.0-3.debian.tar.xz
Files:
 a50fd7e7001498e88e9746abe5fe8e1a 3268 devel optional poppler_0.38.0-3.dsc
 864909d398c7035db1c47be8b3d1cbb2 30180 devel optional 
poppler_0.38.0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1


Bug#822552: marked as done (ketm: fails to install: touch: cannot touch '/var/games/ketm.scores': No such file or directory)

2016-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2016 16:24:57 +
with message-id 
and subject line Bug#822552: fixed in ketm 0.0.6-24
has caused the Debian Bug report #822552,
regarding ketm: fails to install: touch: cannot touch '/var/games/ketm.scores': 
No such file or directory
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.)


-- 
822552: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822552
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ketm
Version: 0.0.6-23
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package ketm.
  (Reading database ... 
(Reading database ... 8065 files and directories currently installed.)
  Preparing to unpack .../ketm_0.0.6-23_amd64.deb ...
  Unpacking ketm (0.0.6-23) ...
  Setting up ketm (0.0.6-23) ...
  touch: cannot touch '/var/games/ketm.scores': No such file or directory
  dpkg: error processing package ketm (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   ketm


cheers,

Andreas


ketm_0.0.6-23.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ketm
Source-Version: 0.0.6-24

We believe that the bug you reported is fixed in the latest version of
ketm, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 822...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated ketm package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 25 Apr 2016 15:35:25 +0200
Source: ketm
Binary: ketm ketm-data
Architecture: source
Version: 0.0.6-24
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Description:
 ketm   - old school 2D-scrolling shooter
 ketm-data  - graphics and audio data for ketm
Closes: 822552
Changes:
 ketm (0.0.6-24) unstable; urgency=medium
 .
   * Team upload.
   * ketm.postinst: Create /var/games directory in postinst script
 in case it does not exist.
 Thanks to Andreas Beckmann for the report. (Closes: #822552)
Checksums-Sha1:
 00eafcf25691ab7963c1f03f1813e9a10d4e8c1c 2135 ketm_0.0.6-24.dsc
 433b8d9c84b1b136fd3003155be7e4185330edcf 96380 ketm_0.0.6-24.debian.tar.xz
Checksums-Sha256:
 8cd0299d9bc3aa4d025da34fab8c2e05f147539ac6cf34430c09e71c69809d01 2135 
ketm_0.0.6-24.dsc
 0fc9bec9be92e2f19c2dff39bd49cf6f6a71fffc1b05db95109a74fd408450fa 96380 
ketm_0.0.6-24.debian.tar.xz
Files:
 01ef41dbb23bc7a11fcdeba93920527d 2135 games optional ketm_0.0.6-24.dsc
 bed437e5b075cb1335bb3bf9f5b2523d 96380 games optional 
ketm_0.0.6-24.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJXHh/vXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBQ0YzRDA4OEVGMzJFREVGNkExQTgzNUZE
OUFEMTRCOTUxM0I1MUU0AAoJENmtFLlRO1HkQBoQAK0U7pKgsmF9wrNtXZSoAUaU
ucgbjAhTjsj4v2lAjAJY29wndkXuaWWTyNdfa2eXeKhI87hWJapCEYqXzREn3rA/
GU4p9whokQRPQqaIQU/mPIqRE1MuxCz0g4sVi0OiKcPHnCTFWmiUGxrn6tzRGzT7
TTzoxL7b+BUCcpJn4iXy47TK2LJU/xE40XxLG2LkhWnu4lsITbz6IOI3z3vb4yx1
IGVFRu3H4NEkWU4vvxbkG+jiXnYP0bJ7mShiy0CnG2B+8BcLww0asPRG6Z/6jGSY
q57KNG0EllqxWllk8qzZWTx5JvvA98z+B7748prtrvE0o0FAh5G4XI7joQkOKwaY
OshZAfo96ffSfdbehkoFYlplPdS3Rn5UVs9MxcjqtnbZ/xPO0x+OcArveDgjG100
7a2iv/TQd1qkJZUDsg2dJ0snmYITbbeJP1l+2woLKYEZYuNFgcIZwkO5nsYACIfE
nrt6sI888e5hK/s4GrqCm9XwF2/S+N4RFpgZ8hKpWSjpUkbOqz92xNqC0oP16Yf+
cJdJotP9rF+o1vkjPfRQ1NDwoCcragn6X7YLSWsQsSnu/rJbeVnsvExXGdvpNFP4
Ky5FwVaivaEd1G1Fn0sLR6rrI2h2ZbadehZteAGO1KhwIGCjYdOcDEGpovYiQYMw
J7puviWxPQs1L4Y1uuxK
=N6ma
-END PGP SIGNATURE End Message ---


Bug#816980: [Pkg-julia-devel] Bug#816980: julia: FTBFS in testing (signal (11): Segmentation fault)

2016-04-25 Thread Tony Kelman
Probably because the Debian build isn't using the stable, tested,
recommended and supported version of LLVM for that branch of Julia. LLVM
makes significant breaking changes to all of their API's between minor
versions, so removing old versions from Debian means downstream users of
LLVM end up broken or with serious performance and memory regressions.
On Apr 25, 2016 9:10 AM, "Viral Shah"  wrote:

> I routinely build Julia on my 8GB Macbook Pro, and it comfortably builds
> with a bunch of other stuff running.
>
> Tony, Elliot - either of you have any ideas?
>
> -viral
>
>
>
> > On 25-Apr-2016, at 8:17 PM, Santiago Vila  wrote:
> >
> > severity 816980 serious
> > thanks
> >
> > I rented a virtual machine with 16 GB RAM and 16 GB swap.
> > It failed again. The build log is attached.
> >
> > While it was working, "top" showed this:
> >
> >  PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+
> COMMAND
> > 8453 sanvila   20   0 9209844 504260  66120 R  99.7  6.2   2:42.93 julia
> > 8677 sanvila   20   0 9002012 272516  62216 R 100.3  3.3   0:54.40 julia
> > 7954 sanvila   20   0 9105584 163172  56504 S   0.0  2.0   0:09.03 julia
> >
> > Do I need 27 GB of RAM to build this now?
> >
> > If not: How much swap do I need, why does julia overcommit so much,
> > and why this didn't happen in version 0.3.11 or 0.3.12?
> >
> >
> Thanks.___
> > Pkg-julia-devel mailing list
> > pkg-julia-de...@lists.alioth.debian.org
> > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-julia-devel
>
>


Bug#816980: [Pkg-julia-devel] Bug#816980: julia: FTBFS in testing (signal (11): Segmentation fault)

2016-04-25 Thread Viral Shah
I routinely build Julia on my 8GB Macbook Pro, and it comfortably builds with a 
bunch of other stuff running. 

Tony, Elliot - either of you have any ideas?

-viral



> On 25-Apr-2016, at 8:17 PM, Santiago Vila  wrote:
> 
> severity 816980 serious
> thanks
> 
> I rented a virtual machine with 16 GB RAM and 16 GB swap.
> It failed again. The build log is attached.
> 
> While it was working, "top" showed this:
> 
>  PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
> 8453 sanvila   20   0 9209844 504260  66120 R  99.7  6.2   2:42.93 julia
> 8677 sanvila   20   0 9002012 272516  62216 R 100.3  3.3   0:54.40 julia
> 7954 sanvila   20   0 9105584 163172  56504 S   0.0  2.0   0:09.03 julia
> 
> Do I need 27 GB of RAM to build this now?
> 
> If not: How much swap do I need, why does julia overcommit so much,
> and why this didn't happen in version 0.3.11 or 0.3.12?
> 
> Thanks.___
> Pkg-julia-devel mailing list
> pkg-julia-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-julia-devel



Bug#822517: marked as done (topmenu-gtk: FTBFS: Package 'graphite2', required by 'harfbuzz', not found)

2016-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2016 09:06:36 -0700
with message-id <20160425160636.ga15...@jirafa.cyrius.com>
and subject line Bug in harfbuzz
has caused the Debian Bug report #822517,
regarding topmenu-gtk: FTBFS: Package 'graphite2', required by 'harfbuzz', not 
found
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.)


-- 
822517: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822517
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: topmenu-gtk
Version: 0.2.1+git20151210.8c6108f-3
Severity: serious

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> checking whether to build static libraries... no
> checking for pkg-config... /usr/bin/pkg-config
> checking pkg-config is at least version 0.9.0... yes
> checking for GTK... no
> configure: error: Package requirements (gtk+-x11-2.0) were not met:
> 
> Package 'graphite2', required by 'harfbuzz', not found
> 
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
> 
> Alternatively, you may set the environment variables GTK_CFLAGS
> and GTK_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
> /usr/share/cdbs/1/class/autotools.mk:42: recipe for target 
> 'debian/stamp-autotools' failed
> make: *** [debian/stamp-autotools] Error 1
> dpkg-buildpackage: error: debian/rules build gave error exit status 2

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Emilio Pozuelo Monfort: "This was a bug in harfbuzz, fixed in
1.2.6-2."

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise--- End Message ---


Processed: found 822578 in 0.26.5-1

2016-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> found 822578 0.26.5-1
Bug #822578 [src:poppler] poppler: CVE-2015-8868: heap buffer overflow
Marked as found in versions poppler/0.26.5-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
822578: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822578
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#821273: marked as done (gqrx-sdr: gqrx crashes at start)

2016-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2016 17:00:30 +0200
with message-id <571e310e.10...@spiessknafl.at>
and subject line 
has caused the Debian Bug report #821273,
regarding gqrx-sdr: gqrx crashes at start
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.)


-- 
821273: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821273
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gqrx-sdr
Version: 2.5.1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I installed the latest version in testing of gqrx-sdr.

When I tried to start it, the console throw the following error message:

$> gqrx
linux; GNU C++ version 5.3.1 20160323; Boost_105800; UHD_003.009.003-0-unknown

Controlport disabled
No user supplied config file. Using "default.conf"
gr-osmosdr 0.1.4 (0.1.4) gnuradio 3.7.9
built-in source types: file osmosdr fcd rtl rtl_tcp uhd miri hackrf bladerf
rfspace airspy redpitaya
Using Volk machine: sse4_2_64_orc
FM demod gain: 1.52789
IQ DCR alpha: 1.04166e-05
terminate called after throwing an instance of
'boost::exception_detail::clone_impl'
  what():  send_to: Operation not permitted
[1]31789 abort  gqrx


I hope this is sufficient to fix the problem.

Greetings
Peter



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (200, 'unstable'), (100, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gqrx-sdr depends on:
ii  libboost-program-options1.58.0  1.58.0+dfsg-5+b1
ii  libboost-system1.58.0   1.58.0+dfsg-5+b1
ii  libc6   2.22-5
ii  libgcc1 1:6-20160205-1
ii  libgnuradio-analog3.7.9 3.7.9.1-2+b1
ii  libgnuradio-audio3.7.9  3.7.9.1-2+b1
ii  libgnuradio-blocks3.7.9 3.7.9.1-2+b1
ii  libgnuradio-digital3.7.93.7.9.1-2+b1
ii  libgnuradio-fft3.7.93.7.9.1-2+b1
ii  libgnuradio-filter3.7.9 3.7.9.1-2+b1
ii  libgnuradio-osmosdr0.1.40.1.4-8
ii  libgnuradio-pmt3.7.93.7.9.1-2+b1
ii  libgnuradio-runtime3.7.93.7.9.1-2+b1
ii  libpulse0   8.0-2
ii  libqt5core5a5.5.1+dfsg-16
ii  libqt5gui5  5.5.1+dfsg-16
ii  libqt5network5  5.5.1+dfsg-16
ii  libqt5svg5  5.5.1-2
ii  libqt5widgets5  5.5.1+dfsg-16
ii  libstdc++6  6-20160205-1
ii  libvolk1.1  1.2.1-2
ii  pulseaudio  8.0-2

gqrx-sdr recommends no packages.

gqrx-sdr suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Dear Maintainer!

I figured out what the problem was.

If you have the entry "::1 localhost" in your /etc/hosts, the program
crashes.

A more detailed discussion can be seen here:

https://github.com/csete/gqrx/issues/369#issuecomment-214376754

Greetings
Peter--- End Message ---


Bug#822578: marked as pending

2016-04-25 Thread Pino Toscano
tag 822578 pending
thanks

Hello,

Bug #822578 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://git.debian.org/?p=pkg-freedesktop/poppler.git;a=commitdiff;h=7b76a0c

---
commit 7b76a0cf5b66508c6a89b199b024c5269a882451
Author: Pino Toscano 
Date:   Mon Apr 25 16:37:13 2016 +0200

fix a crash on invalid files; CVE-2015-8868 (#822578)

backport upstream commit b3425dd3261679958cd56c0f71995c15d2124433

diff --git a/debian/changelog b/debian/changelog
index cc47829..d7f7942 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,5 +1,8 @@
 poppler (0.38.0-3) UNRELEASED; urgency=medium
 
+  * Backport upstream commit b3425dd3261679958cd56c0f71995c15d2124433 to fix
+a crash on invalid files, reported also as CVE-2015-8868; patch
+upstream_Do-not-crash-on-invalid-files.patch. (Closes: #822578)
 
  -- Pino Toscano   Mon, 25 Apr 2016 16:29:19 +0200
 



Processed: Re: Bug#816980: julia: FTBFS in testing (signal (11): Segmentation fault)

2016-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 816980 serious
Bug #816980 [src:julia] julia: FTBFS in testing (signal (11): Segmentation 
fault)
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
816980: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816980
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: tagging 822578

2016-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 822578 + pending
Bug #822578 [src:poppler] poppler: CVE-2015-8868: heap buffer overflow
Ignoring request to alter tags of bug #822578 to the same tags previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
822578: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822578
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: Bug#822578 marked as pending

2016-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tag 822578 pending
Bug #822578 [src:poppler] poppler: CVE-2015-8868: heap buffer overflow
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
822578: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822578
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#821100: [debian-mysql] Bug#821100: MySQL 5.5.49 for Oracle April 2016 CPU

2016-04-25 Thread Salvatore Bonaccorso
Hi Robie,

On Fri, Apr 22, 2016 at 09:52:44AM +0100, Robie Basak wrote:
> On Thu, Apr 21, 2016 at 07:13:34PM +0200, Salvatore Bonaccorso wrote:
> > Do you have any status-update for this for us?
> 
> Struggling to find an available and willing sponsor, sorry. Lars has had
> his tree ready for a while.
> 
> I am DM for src:mysql-5.6, but not for src:mysql-5.5 (that's just a
> technicality, I could be added I suppose) but I think you said that this
> needs a DD?
> 
> Unfortunately this means that Lars passes his work to me for review, and
> then I pass it to a sponsor for upload, so it's a bit slow.
> 
> My usual sponsoring DD for MySQL is also an Ubuntu dev and is busy this
> week (it being Ubuntu release week) so hasn't been able to spare any
> time for me on this. I'll continue to seek a sponsor.
> 
> If anyone else can help please, the trees are at:
> 
> http://anonscm.debian.org/cgit/pkg-mysql/mysql-5.5.git/log/
> http://anonscm.debian.org/cgit/pkg-mysql/mysql-5.5.git/log/?h=debian/wheezy
> 
> In my judgement (as a DM for mysql-5.6), Lars' work here is correct and
> ready to upload.

Did you got a reply from your sponsor? Btw, please not that by now --
since wheezy security support will end tomorrow, and then handled over
to the LTS team, we can only handle the jessie-security upload via the
DSA.

Regards,
Salvatore



Processed: bug 822578 is forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=93476, tagging 822578

2016-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 822578 https://bugs.freedesktop.org/show_bug.cgi?id=93476
Bug #822578 [src:poppler] poppler: CVE-2015-8868: heap buffer overflow
Set Bug forwarded-to-address to 
'https://bugs.freedesktop.org/show_bug.cgi?id=93476'.
> tags 822578 + fixed-upstream
Bug #822578 [src:poppler] poppler: CVE-2015-8868: heap buffer overflow
Ignoring request to alter tags of bug #822578 to the same tags previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
822578: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822578
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: severity of 822578 is grave

2016-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 822578 grave
Bug #822578 [src:poppler] poppler: CVE-2015-8868: heap buffer overflow
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
822578: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822578
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#820785: (no subject)

2016-04-25 Thread Peter Spiess-Knafl
Gentoo claims to have fixed it like this:

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c13b5e88c6e9c7bd2698d844cb5ed127ed809f7e

Greetings
Peter



Bug#818155: (no subject)

2016-04-25 Thread Peter Spiess-Knafl
Since there is no activity on this bug, and I cannot fix it on my own. I
raised an issue upstream about that:

https://github.com/jm/toml/issues/43

Greetings
Peter



Processed (with 5 errors): Patch for FTBFS

2016-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 822500 + patch
Bug #822500 [brlaser] brlaser: FTBFS: 'string' is not a member of 'std'
Added tag(s) patch.
> Hi!
Unknown command or malformed arguments to command.
> A quick "#include " did the trick.
Unknown command or malformed arguments to command.
> You can ignore of course the the changelog entry if you like, it is just
Unknown command or malformed arguments to command.
> to make debdiff work.
Unknown command or malformed arguments to command.
> I also forwarded it upstream: https://github.com/pdewacht/brlaser/pull/9
Unknown command or malformed arguments to command.
Too many unknown commands, stopping here.

Please contact me if you need assistance.
-- 
822500: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822500
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#822500: Patch for FTBFS

2016-04-25 Thread Peter Spiess-Knafl
tags 822500 + patch

Hi!

A quick "#include " did the trick.

You can ignore of course the the changelog entry if you like, it is just
to make debdiff work.

I also forwarded it upstream: https://github.com/pdewacht/brlaser/pull/9


Greetings
Peter
diff -Nru brlaser-3/debian/changelog brlaser-3/debian/changelog
--- brlaser-3/debian/changelog	2016-02-25 19:39:28.0 +0100
+++ brlaser-3/debian/changelog	2016-04-25 15:06:20.0 +0200
@@ -1,3 +1,10 @@
+brlaser (3-5) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add patch to fix FTBFS (Closes: #822500)
+
+ -- Peter Spiess-Knafl   Mon, 25 Apr 2016 15:04:45 +0200
+
 brlaser (3-4) unstable; urgency=medium
 
   * Import upstream patch to add support for Brother DCP-7055
diff -Nru brlaser-3/debian/patches/fix-ftbfs-missing-include.patch brlaser-3/debian/patches/fix-ftbfs-missing-include.patch
--- brlaser-3/debian/patches/fix-ftbfs-missing-include.patch	2016-04-25 14:55:35.0 +0200
+++ brlaser-3/debian/patches/fix-ftbfs-missing-include.patch	2016-04-25 15:04:41.0 +0200
@@ -1,3 +1,9 @@
+Description: Fix FTBFS due to missing include
+Author: Peter Spiess-Knafl 
+Bug: 822500
+Forwarded: https://github.com/pdewacht/brlaser/pull/9
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
 --- a/src/brdecode.cc
 +++ b/src/brdecode.cc
 @@ -21,6 +21,7 @@


Processed: severity of 820295 is grave

2016-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 820295 grave
Bug #820295 {Done: Michael Biebl } [network-manager-pptp] 
network-manager-pptp: pppd segfaults when NM tries to establish PPTP connection 
since 1.1.92-1
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
820295: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820295
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#822503: marked as done (mia: FTBFS: error: 'accumulate' was not declared in this scope)

2016-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2016 11:24:13 +
with message-id 
and subject line Bug#822503: fixed in mia 2.2.7-4
has caused the Debian Bug report #822503,
regarding mia: FTBFS: error: 'accumulate' was not declared in this scope
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.)


-- 
822503: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822503
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mia
Version: 2.2.7-3
Severity: serious

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> cd /<>/obj-x86_64-linux-gnu/addons/tiff && ln -sf 
> /<>/obj-x86_64-linux-gnu/addons/tiff/2dimage-io-tiff.mia 
> /<>/obj-x86_64-linux-gnu/plugintest//usr/lib/x86_64-linux-gnu/mia-2.2/plugins/2dimage/io/
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> [  4%] Built target 2dimage-io-tiff_test_link
> In file included from /<>/mia/core/testplugin.cc:33:0:
> /<>/mia/core/testplugin.hh:55:35: warning: type attributes 
> ignored after type is already defined [-Wattributes]
>  extern template class EXPORT_CORE TPluginHandler;
>^
> /<>/mia/core/waveletslopeclassifier.cc: In constructor 
> 'mia::CWaveletSlopeClassifierImpl::CWaveletSlopeClassifierImpl(const 
> Columns&, bool, float)':
> /<>/mia/core/waveletslopeclassifier.cc:241:103: error: 
> 'accumulate' was not declared in this scope
>float low_freq = accumulate(e.begin() + low_energy_start_idx, e.begin() + 
> movement_idx-skip_idx, 0.0); 
>   
>  ^
> mia/core/CMakeFiles/miacore.dir/build.make:1697: recipe for target 
> 'mia/core/CMakeFiles/miacore.dir/waveletslopeclassifier.cc.o' failed
> make[3]: *** [mia/core/CMakeFiles/miacore.dir/waveletslopeclassifier.cc.o] 
> Error 1
> make[3]: *** Waiting for unfinished jobs
> [  4%] Linking CXX executable test-vector
> cd /<>/obj-x86_64-linux-gnu/gsl++ && /usr/bin/cmake -E 
> cmake_link_script CMakeFiles/test-vector.dir/link.txt --verbose=1
> /usr/bin/c++   -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -std=c++11 
> -fvisibility=hidden   -Wl,-z,relro -Wl,--as-needed -fvisibility=hidden 
> CMakeFiles/test-vector.dir/test_vector.cc.o  -o test-vector -rdynamic 
> libmiagsl-2.2.so.4.0.3 -lboost_unit_test_framework -lgsl -lgslcblas -lm 
> -Wl,-rpath,/<>/obj-x86_64-linux-gnu/gsl++ 
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: mia
Source-Version: 2.2.7-4

We believe that the bug you reported is fixed in the latest version of
mia, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 822...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gert Wollny  (supplier of updated mia package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 25 Apr 2016 10:19:45 +
Source: mia
Binary: libmia-2.2-4 libmia-2.2-dev libmia-2.2-doc libmia-2.2-4-dbg mia-tools 
mia-tools-doc mia-tools-dbg
Architecture: source
Version: 2.2.7-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Gert Wollny 
Description:
 libmia-2.2-4 - library for 2D and 3D gray scale image processing
 libmia-2.2-4-dbg - Debug information for the MIA library
 libmia-2.2-dev - library for 2D and 3D gray scale image processing, 
development fi
 libmia-2.2-doc - library for 2D and 3D gray scale image processing, 
documentation
 mia-tools  - Command line tools for gray scale image processing
 mia-tools-dbg - Debugging information for the MIA command line tools
 mia-tools-doc - Cross-referenced documentation of the MIA command line tools
Closes: 822503
Changes:
 mia (2.2.7-4) unstable; urgency=medium
 .
   * d/p/02: Add patch for stricter includes Closes: #822503

Processed: fixed 818797 in 0.15.5+dfsg-4

2016-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> # build failure was intermittent
> fixed 818797 0.15.5+dfsg-4
Bug #818797 {Done: Joachim Breitner } [src:haskell-shake] 
haskell-shake: FTBFS on powerpc: timed out
Marked as fixed in versions haskell-shake/0.15.5+dfsg-4.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
818797: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818797
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: fixed 818797 in 0.15.5+dfsg-6

2016-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> fixed 818797 0.15.5+dfsg-6
Bug #818797 {Done: Joachim Breitner } [src:haskell-shake] 
haskell-shake: FTBFS on powerpc: timed out
Marked as fixed in versions haskell-shake/0.15.5+dfsg-6.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
818797: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818797
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: libnginx-mod-http-perl: fails to upgrade from 'testing' - trying to overwrite /usr/lib/x86_64-linux-gnu/perl5/5.22/nginx.pm

2016-04-25 Thread Debian Bug Tracking System
Processing control commands:

> affects -1 + nginx-extras
Bug #822553 [libnginx-mod-http-perl] libnginx-mod-http-perl: fails to upgrade 
from 'testing' - trying to overwrite 
/usr/lib/x86_64-linux-gnu/perl5/5.22/nginx.pm
Added indication that 822553 affects nginx-extras

-- 
822553: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822553
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#822553: libnginx-mod-http-perl: fails to upgrade from 'testing' - trying to overwrite /usr/lib/x86_64-linux-gnu/perl5/5.22/nginx.pm

2016-04-25 Thread Andreas Beckmann
Package: libnginx-mod-http-perl
Version: 1.9.14-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + nginx-extras

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package libnginx-mod-http-perl.
  Preparing to unpack .../libnginx-mod-http-perl_1.9.14-1_amd64.deb ...
  Unpacking libnginx-mod-http-perl (1.9.14-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libnginx-mod-http-perl_1.9.14-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/perl5/5.22/nginx.pm', which 
is also in package nginx-extras 1.9.10-1

cheers,

Andreas


nginx-extras_1.9.14-1.log.gz
Description: application/gzip


Bug#799322: marked as done (pocl: FTBFS: (gcc5 related?) symbols mismatches + test failures)

2016-04-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Apr 2016 10:24:55 +
with message-id 
and subject line Bug#799322: fixed in pocl 0.11-1
has caused the Debian Bug report #799322,
regarding pocl: FTBFS: (gcc5 related?) symbols mismatches + test failures
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.)


-- 
799322: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799322
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:pocl
Version: 0.10-10
Severity: serious
Control: found -1 0.10-12
Control: block 794935 with -1

The binNMU of pocl for the llvm-toolchain-3.5 transition 
(https://buildd.debian.org/status/fetch.php?pkg=pocl=amd64=0.10-10%2Bb1=1442439767) 
failed with symbols mismatches, at least some of which look gcc-5 
related (though I haven't checked whether they all are, and pocl does 
have a history of symbols issues), e.g.


- 
(optional=templinst)_ZN4llvm12hash_combineINS_9hash_codeESsEES1_RKT_RKT0_@Base 
0.10

[...]
+#MISSING: 0.10-10+b1# 
(optional=templinst)_ZN4llvm12hash_combineINS_9hash_codeENS_9StringRefEEES1_RKT_RKT0_@Base 
0.10
+ 
_ZN4llvm12hash_combineINS_9hash_codeENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcES1_RKT_RKT0_@Base 
0.10-10+b1


Also, nearly all the tests failed: the build treats this as non-fatal, 
but it should probably be investigated.


A local build of 0.10-12 from experimental had far fewer (but not no) 
test failures, but still FTBFS with the symbols issue.
--- End Message ---
--- Begin Message ---
Source: pocl
Source-Version: 0.11-1

We believe that the bug you reported is fixed in the latest version of
pocl, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 799...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated pocl package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 25 Apr 2016 09:49:29 +0200
Source: pocl
Binary: pocl-opencl-icd libpocl1-common libpocl1 libpoclu1 libpoclu-dev 
libpocl-dev
Architecture: source
Version: 0.11-1
Distribution: experimental
Urgency: medium
Maintainer: Debian OpenCL Maintainers 
Changed-By: Andreas Beckmann 
Description:
 libpocl-dev - development files for the pocl library
 libpocl1   - Portable Computing Language library
 libpocl1-common - common files for the pocl library
 libpoclu-dev - development files for the pocl utility library
 libpoclu1  - utility library for writing OpenCL programs
 pocl-opencl-icd - pocl ICD
Closes: 775844 787686 795321 799322 803652
Changes:
 pocl (0.11-1) experimental; urgency=medium
 .
   [ Vincent Danjean ]
   * New upstream version  (Closes: #795321)
   * Switch to llvm-3.6  (Closes: #803652)
   * Fix "FTBFS on arm64" by targeting llvm arch to cortex-a53 on arm64
 (Closes: #787686)
   * Fix "vcs-browser field does not work" by fixing URL in debian/control
 (Closes: #775844)
 .
   [ Andreas Beckmann ]
   * Use a temporary, writable $HOME while running the testsuite.
   * Show the full tests/testsuite.log on testsuite failures.
   * Drop the -dbg package in favor of autogenerated -dbgsym packages.
   * Update symbols files for amd64 and i386.
   * llvm-config --system-libs is only needed with static llvm.
   * Fix detection of image and sampler arguments, thanks to James Price.
 (Closes: #799322)
   * Put package under "Debian OpenCL Maintainers" team maintenance.
   * Add Vincent Danjean and myself to Uploaders.
   * Bump Standards-Version to 3.9.8 (no changes needed).
Checksums-Sha1:
 72fa0393403bb8a5bac766141db9a3cb19e1a676 2424 pocl_0.11-1.dsc
 33c8980dc198d48d85edccec43829378b05408e3 1561743 pocl_0.11.orig.tar.gz
 173802754ac2f09ceec79b5ffe0ab124fc882d69 118168 pocl_0.11-1.debian.tar.xz
Checksums-Sha256:
 6eb547ecff62877cf6a2ceafd1ead70e35cd341a599523bcdce28bdd52b45a94 2424 
pocl_0.11-1.dsc
 24bb801fb87d104b66faaa95d1890776fdeabb37ad1b12fb977281737c7f29bb 1561743 
pocl_0.11.orig.tar.gz
 3e98d3b638dbacb5fed1376099af35ab09514538954978a2b84690060565daff 118168 
pocl_0.11-1.debian.tar.xz
Files:
 1f012094e6d614606e5fc9d0a90d49f5 2424 libs 

Bug#822552: ketm: fails to install: touch: cannot touch '/var/games/ketm.scores': No such file or directory

2016-04-25 Thread Andreas Beckmann
Package: ketm
Version: 0.0.6-23
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package ketm.
  (Reading database ... 
(Reading database ... 8065 files and directories currently installed.)
  Preparing to unpack .../ketm_0.0.6-23_amd64.deb ...
  Unpacking ketm (0.0.6-23) ...
  Setting up ketm (0.0.6-23) ...
  touch: cannot touch '/var/games/ketm.scores': No such file or directory
  dpkg: error processing package ketm (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   ketm


cheers,

Andreas


ketm_0.0.6-23.log.gz
Description: application/gzip


Bug#822548: nuitka: FTBFS: [test failed] Comparing output of 'ParameterErrors.py'

2016-04-25 Thread Chris Lamb
Source: nuitka
Version: 0.5.20+ds-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

nuitka fails to build from source in unstable/amd64:

  [..]

  Unpacking sgml-base (1.26+nmu4) ...
  Selecting previously unselected package xml-core.
  Preparing to unpack .../xml-core_0.13+nmu2_all.deb ...
  Unpacking xml-core (0.13+nmu2) ...
  Selecting previously unselected package docutils-common.
  Preparing to unpack .../docutils-common_0.12+dfsg-1_all.deb ...
  Unpacking docutils-common (0.12+dfsg-1) ...
  Selecting previously unselected package python-docutils.
  Preparing to unpack .../python-docutils_0.12+dfsg-1_all.deb ...
  Unpacking python-docutils (0.12+dfsg-1) ...
  Selecting previously unselected package python-pdfrw.
  Preparing to unpack .../python-pdfrw_0.2-2_all.deb ...
  Unpacking python-pdfrw (0.2-2) ...
  Selecting previously unselected package python-pygments.
  Preparing to unpack .../python-pygments_2.1+dfsg-1_all.deb ...
  Unpacking python-pygments (2.1+dfsg-1) ...
  Selecting previously unselected package python-reportlab-accel:amd64.
  Preparing to unpack .../python-reportlab-accel_3.3.0-1+b1_amd64.deb ...
  Unpacking python-reportlab-accel:amd64 (3.3.0-1+b1) ...
  Selecting previously unselected package python-reportlab.
  Preparing to unpack .../python-reportlab_3.3.0-1_all.deb ...
  Unpacking python-reportlab (3.3.0-1) ...
  Selecting previously unselected package python-simplejson.
  Preparing to unpack .../python-simplejson_3.8.2-2_amd64.deb ...
  Unpacking python-simplejson (3.8.2-2) ...
  Selecting previously unselected package python-setuptools.
  Preparing to unpack .../python-setuptools_20.7.0-1_all.deb ...
  Unpacking python-setuptools (20.7.0-1) ...
  Selecting previously unselected package rst2pdf.
  Preparing to unpack .../rst2pdf_0.93-4_all.deb ...
  Unpacking rst2pdf (0.93-4) ...
  Selecting previously unselected package libpng16-16:amd64.
  Preparing to unpack .../libpng16-16_1.6.21-4_amd64.deb ...
  Unpacking libpng16-16:amd64 (1.6.21-4) ...
  Selecting previously unselected package libfreetype6:amd64.
  Preparing to unpack .../libfreetype6_2.6.3-3+b1_amd64.deb ...
  Unpacking libfreetype6:amd64 (2.6.3-3+b1) ...
  Selecting previously unselected package libjpeg62-turbo:amd64.
  Preparing to unpack .../libjpeg62-turbo_1%3a1.4.2-2_amd64.deb ...
  Unpacking libjpeg62-turbo:amd64 (1:1.4.2-2) ...
  Selecting previously unselected package liblcms2-2:amd64.
  Preparing to unpack .../liblcms2-2_2.7-1_amd64.deb ...
  Unpacking liblcms2-2:amd64 (2.7-1) ...
  Selecting previously unselected package libjbig0:amd64.
  Preparing to unpack .../libjbig0_2.1-3.1_amd64.deb ...
  Unpacking libjbig0:amd64 (2.1-3.1) ...
  Selecting previously unselected package libtiff5:amd64.
  Preparing to unpack .../libtiff5_4.0.6-1_amd64.deb ...
  Unpacking libtiff5:amd64 (4.0.6-1) ...
  Selecting previously unselected package libwebp5:amd64.
  Preparing to unpack .../libwebp5_0.4.4-1+b2_amd64.deb ...
  Unpacking libwebp5:amd64 (0.4.4-1+b2) ...
  Selecting previously unselected package libwebpdemux1:amd64.
  Preparing to unpack .../libwebpdemux1_0.4.4-1+b2_amd64.deb ...
  Unpacking libwebpdemux1:amd64 (0.4.4-1+b2) ...
  Selecting previously unselected package libwebpmux1:amd64.
  Preparing to unpack .../libwebpmux1_0.4.4-1+b2_amd64.deb ...
  Unpacking libwebpmux1:amd64 (0.4.4-1+b2) ...
  Selecting previously unselected package python-pil:amd64.
  Preparing to unpack .../python-pil_3.2.0-1_amd64.deb ...
  Unpacking python-pil:amd64 (3.2.0-1) ...
  Selecting previously unselected package python-imaging.
  Preparing to unpack .../python-imaging_3.2.0-1_all.deb ...
  Unpacking python-imaging (3.2.0-1) ...
  Selecting previously unselected package scons.
  Preparing to unpack .../archives/scons_2.5.0-1_all.deb ...
  Unpacking scons (2.5.0-1) ...
  Selecting previously unselected package libpython3.5:amd64.
  Preparing to unpack .../libpython3.5_3.5.1-11_amd64.deb ...
  Unpacking libpython3.5:amd64 (3.5.1-11) ...
  Selecting previously unselected package libpython3.5-dev:amd64.
  Preparing to unpack .../libpython3.5-dev_3.5.1-11_amd64.deb ...
  Unpacking libpython3.5-dev:amd64 (3.5.1-11) ...
  Selecting previously unselected package libpython3-dev:amd64.
  Preparing to unpack .../libpython3-dev_3.5.1-3_amd64.deb ...
  Unpacking libpython3-dev:amd64 (3.5.1-3) ...
  Selecting previously unselected package libpython3-all-dev:amd64.
  Preparing to unpack .../libpython3-all-dev_3.5.1-3_amd64.deb ...
  Unpacking libpython3-all-dev:amd64 (3.5.1-3) ...
  Selecting previously unselected package python3-all.
  Preparing to unpack .../python3-all_3.5.1-3_amd64.deb ...
  Unpacking python3-all (3.5.1-3) ...
  Selecting previously unselected package python3.5-dev.
  Preparing to unpack .../python3.5-dev_3.5.1-11_amd64.deb ...
  Unpacking python3.5-dev (3.5.1-11) ...
  

Bug#822547: pngtools: diff for NMU version 0.4-1.3

2016-04-25 Thread Gianfranco Costamagna
Package: pngtools
Version: 0.4-1.2
Severity: serious
Justification: autoconf don't use libpng anymore, due to an API change.
Tags: patch pending

Dear maintainer,

I've prepared an NMU for pngtools (versioned as 0.4-1.3) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.


(I'll close this bug in changelog)

Regards.
diff -u pngtools-0.4/debian/changelog pngtools-0.4/debian/changelog
--- pngtools-0.4/debian/changelog
+++ pngtools-0.4/debian/changelog
@@ -1,3 +1,16 @@
+pngtools (0.4-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Switch to autoreconf
+  * Bump compat level to 9
+  * Drop cdbs
+  * Refactor rules file, fixing a build failure
+with as-needed flags.
+  * Patch configure.in following png rename of
+api.
+
+ -- Gianfranco Costamagna   Sun, 24 Apr 2016 22:47:36 +0200
+
 pngtools (0.4-1.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u pngtools-0.4/debian/compat pngtools-0.4/debian/compat
--- pngtools-0.4/debian/compat
+++ pngtools-0.4/debian/compat
@@ -1 +1 @@
-7
+9
diff -u pngtools-0.4/debian/control pngtools-0.4/debian/control
--- pngtools-0.4/debian/control
+++ pngtools-0.4/debian/control
@@ -2,8 +2,8 @@
 Section: graphics
 Priority: optional
 Maintainer: Nelson A. de Oliveira 
-Build-Depends: cdbs, debhelper (>= 7), libpng-dev
-Standards-Version: 3.8.3
+Build-Depends: debhelper (>= 9), dh-autoreconf, libpng-dev
+Standards-Version: 3.9.8
 Homepage: http://www.stillhq.com/pngtools/
 
 Package: pngtools
diff -u pngtools-0.4/debian/rules pngtools-0.4/debian/rules
--- pngtools-0.4/debian/rules
+++ pngtools-0.4/debian/rules
@@ -3,5 +3,4 @@
-include /usr/share/cdbs/1/rules/debhelper.mk
-include /usr/share/cdbs/1/class/autotools.mk
+export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
-DEB_INSTALL_DOCS_ALL := chunks.txt
-DEB_INSTALL_MANPAGES_pngtools := debian/*.1
+%:
+	dh $@ --with autoreconf
only in patch2:
unchanged:
--- pngtools-0.4.orig/configure.in
+++ pngtools-0.4/configure.in
@@ -19,7 +19,7 @@
 AC_CHECK_LIB(m, atan)
 
 dnl -lpng:
-AC_CHECK_LIB(png, png_libpng_ver)
+AC_CHECK_LIB(png, png_get_libpng_ver)
 
 dnl STDC checks for stdlib.h stdarg.h string.h and float.h
 AC_HEADER_STDC
only in patch2:
unchanged:
--- pngtools-0.4.orig/debian/docs
+++ pngtools-0.4/debian/docs
@@ -0,0 +1 @@
+chunks.txt
only in patch2:
unchanged:
--- pngtools-0.4.orig/debian/manpages
+++ pngtools-0.4/debian/manpages
@@ -0,0 +1 @@
+debian/*.1


  1   2   >