Bug#871332: [Pkg-opencl-devel] Bug#871332: beignet: FTBFS: dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -

[Rebecca N. Palmer]

Control: tags -1 pending

Fixed in Alioth, ready for upload.

On 07/08/17 16:47, Lucas Nussbaum wrote:

Source: beignet
Version: 1.3.0-4
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 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):

make[3]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Building CXX object CMakeFiles/cmTC_62e05.dir/feature_tests.cxx.o
/usr/bin/c++-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DGBE_DEBUG=1-std=c++98 -o 
CMakeFiles/cmTC_62e05.dir/feature_tests.cxx.o -c 
/<>/obj-x86_64-linux-gnu/CMakeFiles/feature_tests.cxx
Linking CXX executable cmTC_62e05
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_62e05.dir/link.txt 
--verbose=1
/usr/bin/c++  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-DGBE_DEBUG=1   -Wl,-z,relro -Wl,-z,now  -rdynamic 
CMakeFiles/cmTC_62e05.dir/feature_tests.cxx.o  -o cmTC_62e05
make[3]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
make[2]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'


 Feature record: CXX_FEATURE:0cxx_aggregate_default_initializers
 Feature record: CXX_FEATURE:0cxx_alias_templates
 Feature record: CXX_FEATURE:0cxx_alignas
 Feature record: CXX_FEATURE:0cxx_alignof
 Feature record: CXX_FEATURE:0cxx_attributes
 Feature record: CXX_FEATURE:0cxx_attribute_deprecated
 Feature record: CXX_FEATURE:0cxx_auto_type
 Feature record: CXX_FEATURE:0cxx_binary_literals
 Feature record: CXX_FEATURE:0cxx_constexpr
 Feature record: CXX_FEATURE:0cxx_contextual_conversions
 Feature record: CXX_FEATURE:0cxx_decltype
 Feature record: CXX_FEATURE:0cxx_decltype_auto
 Feature record: CXX_FEATURE:0cxx_decltype_incomplete_return_types
 Feature record: CXX_FEATURE:0cxx_default_function_template_args
 Feature record: CXX_FEATURE:0cxx_defaulted_functions
 Feature record: CXX_FEATURE:0cxx_defaulted_move_initializers
 Feature record: CXX_FEATURE:0cxx_delegating_constructors
 Feature record: CXX_FEATURE:0cxx_deleted_functions
 Feature record: CXX_FEATURE:0cxx_digit_separators
 Feature record: CXX_FEATURE:0cxx_enum_forward_declarations
 Feature record: CXX_FEATURE:0cxx_explicit_conversions
 Feature record: CXX_FEATURE:0cxx_extended_friend_declarations
 Feature record: CXX_FEATURE:0cxx_extern_templates
 Feature record: CXX_FEATURE:0cxx_final
 Feature record: CXX_FEATURE:0cxx_func_identifier
 Feature record: CXX_FEATURE:0cxx_generalized_initializers
 Feature record: CXX_FEATURE:0cxx_generic_lambdas
 Feature record: CXX_FEATURE:0cxx_inheriting_constructors
 Feature record: CXX_FEATURE:0cxx_inline_namespaces
 Feature record: CXX_FEATURE:0cxx_lambdas
 Feature record: CXX_FEATURE:0cxx_lambda_init_captures
 Feature record: CXX_FEATURE:0cxx_local_type_template_args
 Feature record: CXX_FEATURE:0cxx_long_long_type
 Feature record: CXX_FEATURE:0cxx_noexcept
 Feature record: CXX_FEATURE:0cxx_nonstatic_member_init
 Feature record: CXX_FEATURE:0cxx_nullptr
 Feature record: CXX_FEATURE:0cxx_override
 Feature record: CXX_FEATURE:0cxx_range_for
 Feature record: CXX_FEATURE:0cxx_raw_string_literals
 Feature record: CXX_FEATURE:0cxx_reference_qualified_functions
 Feature record: CXX_FEATURE:0cxx_relaxed_constexpr
 Feature record: CXX_FEATURE:0cxx_return_type_deduction
 Feature record: CXX_FEATURE:0cxx_right_angle_brackets
 Feature record: CXX_FEATURE:0cxx_rvalue_references
 Feature record: CXX_FEATURE:0cxx_sizeof_member
 Feature record: CXX_FEATURE:0cxx_static_assert
 Feature record: CXX_FEATURE:0cxx_strong_enums
 Feature record: CXX_FEATURE:1cxx_template_template_parameters
 Feature record: CXX_FEATURE:0cxx_thread_local
 Feature record: CXX_FEATURE:0cxx_trailing_return_types
 Feature record: CXX_FEATURE:0cxx_unicode_literals
 Feature record: CXX_FEATURE:0cxx_uniform_initialization
 Feature record: CXX_FEATURE:0cxx_unrestricted_unions
 Feature record: CXX_FEATURE:0cxx_user_literals
 Feature record: CXX_FEATURE:0cxx_variable_templates
 Feature record: CXX_FEATURE:0cxx_variadic_macros
 Feature record: CXX_FEATURE:0cxx_variadic_templates
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
-DLLVM_INSTALL_DIR=/usr/lib/llvm-4.0/bin -DENABLE_OPENCL_20=1 returned exit 
code 1
debian/rules:26: recipe for target 'override_dh_auto_configure' failed
make[1]: *** 

Bug#871415: debian-dug-kosovo mailing list creation

[Daniel Pocock]

Package: lists.debian.org
Severity: wishlist

This is a request for a new mailing list

Name: debian-dug-kosova

Rationale: local users and visitors to Kosovo

Short description: Discussion list for the Kosovo Debian community

Long description:
"Discussing user queries, events and other local topics for Debian in Kosovo"

Language used on this list: English and Shqip

Category: misc / user / dug

Subscription Policy: open

Post Policy: open to list subscribers

Web Archive: yes

Bug#867736: [fbpanel] fbpanel crashes with default config

[Will Brokenbourgh]

On 08/07/2017 12:24 PM, Dererk wrote:

tags 867736 +unreproducible +moreinfo

thanks


Hi Will.

I'm unable to reproduce the mentioned behavior. Just to go through it
step-by-step on this, what do you get at the end of the process?

$  mkdir ~/.config/fbpanel && cp /usr/share/fbpanel/default
~/.config/fbpanel/default

$  fbpanel


Cheers,

Dererk


Greetings Dererk,

This bug appears to be resolved as it is no longer crashing on Stretch.  
I had already performed the steps you suggested before filing this 
report, but it appears a dependency was changed since I filed the report 
which has fixed the crashing behavior.


Thanks!

Will Brokenbourgh
Pacific Northwest, USA

Sent from my Linux desktop

Bug#707275: Ansible causes noise in server logs

[Lee]

Hi Carlos,

I'm closing this bug as wontfix. The reason is that upstream has little
motivation of changing the behaviour, and there is a workaround available
(filtering out those message via syslog).

Regards,
Lee

Bug#869665: libgit2-dev: please update version in Debian unstable and do a library transition

[Russell Sim]

On 1 August 2017 at 14:47, Ximin Luo  wrote:

> Ximin Luo:
> > Russell Sim:
> >>> [..]
> >>>
> >>> $ echo $(aptitude search --disable-columns -F "%p" '~Dlibgit2-24
> ~rnative
> >>> !~e^libgit2$')
> >>> eeshow fritzing geany-plugin-git-changebar gnome-builder gnuastro kate
> >>> kup-backup libgit2-glib-1.0-0 libgnuastro1 libgnuastro2
> libkf5texteditor5
> >>> lua-gall python-pygit2 python3-pygit2 ruby-rugged
> >>>
> >>> [..]
> >>
> >> Thanks for the info, I'll follow the document as described.
> >>
> >> I think i may get some time on Monday to start building and testing the
> >> rdepends.  In the meantime could you please upload 0.26.0+dfsg.1-1 to
> >> experimental, I've pushed it to the collab-maint git.
> >>
> >
> > I've uploaded that to experimental. I made a minor tweak in git which
> will take effect for the next version, you can revert it if you want, see
> the commit message for details.
> >
> > I can help with the rebuilds [..]
> >
>
> I've rebuilt the packages above (except eeshow which is only in
> experimental, and libgnucastro1 since it was replaced by *2). The following
> packages fail:
>
> fritzing_0.9.3b+dfsg-4.dsc
> gnome-builder_3.22.4-1.dsc
> gnuastro_0.3.33-1.dsc
> kate_16.08.3-1.dsc
> libgit2-glib_0.24.4-1.dsc
> python-pygit2_0.24.2-2.dsc
> ruby-rugged_0.24.0+ds1-3.dsc
>
> Build logs are here if you'd like to investigate:
> https://people.debian.org/~infinity0/libgit2/
>
> I'll file bugs to those packages in the next few days, or feel free to
> jump in ahead. (I'll be travelling tomorrow to go to DebConf, so it might
> be a while before I get around to it.)
>
> X
>
> --
> GPG: ed25519/56034877E1F87C35
> GPG: rsa4096/1318EFAC5FBBDBCE
> https://github.com/infinity0/pubkeys.git
>

Thanks, for doing all that.

I'm happy to lodge the bugs, I'll wait for the package to clear the new
queue and then send out the emails.

I have had a look over the package build logs you posted, it appears that
most of them have failed because the package defines a hard dependency on
the libgit2 dev version.  Which makes sense.

Enjoy DebConf :)

-- 
Cheers,
Russell Sim

Bug#871279: libdolfin2016.2: requires rebuild against GCC 7 and symbols/shlibs bump

[Mattia Rizzolo]

On Tue, Aug 08, 2017 at 02:29:48AM +0800, Drew Parsons wrote:
> It's been sitting in NEW for a month, so it would have been gcc-6 I
> think.  But the upload is to experimental.  I figure we can ignore
> anything in experimental, the symbols will get reset for the new ABI
> when we drop it into unstable.

Right, that would be fine.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#871414: visp: build with -ffloat-store on i386 for IEEE-conformant fp math

[Steve Langasek]

Package: visp
Version: 3.0.1-2
Severity: important
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu artful ubuntu-patch

Dear maintainers,

When rebuilding visp for the libgsl transition in Ubuntu, we found that the
package FTBFS on i386 with a test failure:

 19/196 Test  #19: testColVector 
.***Failed0.01 sec
[...]
regular_sumSquare=3.654335195e+10 ; sse_sumSquare=3.654335195e+10
t_regular=0.1711152792 ms ; t_sse=0.06501948833 ms
Speed-up: 2.631753703X
Problem when computing v.sumSquare()!

  
https://launchpad.net/ubuntu/+source/visp/3.0.1-2build2/+build/13205544/+files/buildlog_ubuntu-artful-i386.visp_3.0.1-2build2_BUILDING.txt.gz

The displayed value for each of the calculations is identical, but the
actual floating point values clearly differ by a quantity greater than the
tolerance.

Floating point is always a bit dodgy on i386, and in this case the problem
with non-IEEE results (whether that's due to a change in gsl or in gcc - I
haven't checked which) is fixed by building with -ffloat-store as in the
attached patch.

It's worth noting that the visp package also FTBFS in Debian already, but
with a different set of failures pointing to SIGILL.  visp appears to be
doing a lot of SSE math, which is not part of the ISA that's guaranteed to
be present for the i386 port in Debian (or in Ubuntu); so while I think this
patch is correct, I do not expect it to fix the Debian build failure on its own.

Hope that helps,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru visp-3.0.1/debian/rules visp-3.0.1/debian/rules
--- visp-3.0.1/debian/rules 2017-02-13 08:52:30.0 -0800
+++ visp-3.0.1/debian/rules 2017-08-07 11:29:52.0 -0700
@@ -16,6 +16,10 @@
   CMAKE_ARCH_FLAGS = -DUSE_DC1394=OFF -DUSE_V4L2=OFF -DUSE_OIS=OFF
 endif
 
+ifeq ($(DEB_HOST_ARCH),i386)
+  CXXFLAGS += -ffloat-store
+endif
+
 # freenect is not available on hurd.
 ifeq ($(DEB_HOST_ARCH_OS),hurd)
   CMAKE_ARCH_FLAGS += -DUSE_LIBFREENECT=OFF

Bug#870698: [Debian-science-sagemath] Possible fix for fplll/fpylll issue with default strategy path

[Ximin Luo]

Ximin Luo:
> Ximin Luo:
>> Julien Puydt:
>>> Hi,
>>>
>>> I just pushed to fplll's Debian git repository a tentative 5.1.0-3 which
>>> would fix the recently reported issue with fpylll : I rewrote the patch
>>> for the default strategies path changes.
>>>
>>> I'm a bit at loss on how to check if that really fixes anything : I
>>> tried to build fpylll (success), but then trying to "import fpylll" in
>>> python gave:
>>> RuntimeError: You must get the file local/bin/sage-maxima.lisp
>>>
>>> so I can't really test seriously...
>>>
>>
>> I can reproduce this, it works if you uninstall sage (but of course we have 
>> to fix it properly).
>>
>> The underlying issue is caused by the fact that Sage sets things like 
>> SAGE_LOCAL outside of python itself, so that one gets e.g.:
>>
>> $ python -c 'from sage.env import DOT_SAGE, SAGE_SCRIPTS_DIR; 
>> print(SAGE_SCRIPTS_DIR)'
>> $SAGE_LOCAL/bin
>> $ sage -c 'from sage.env import DOT_SAGE, SAGE_SCRIPTS_DIR; 
>> print(SAGE_SCRIPTS_DIR)'
>> /usr/share/sagemath/bin
>>
>> I would guess that this also affects upstream Sage, but perhaps the issue is 
>> hidden somehow (Debian uses a different "sage-env" shell script).
>>
> 
> So for example this works, with sage installed:
> 
> $ SAGE_LOCAL=/usr SAGE_SCRIPTS_DIR=/usr/share/sagemath/bin python -c "import 
> fpylll"
> # no errors, exit code 0
> 
> Now the question is, does Sage always expect that itself should be run via 
> the "sage" program, with particular envvars set? 
> 
> If yes, then fpylll should run the "sage" version of itself after detecting 
> the presence of these envvars - a simple "try: import sage; except 
> ImportError" is not enough.
> 

I've pushed a slightly simpler fix to our git and opened a PR here: 
https://github.com/fplll/fpylll/pull/97

Also have built+uploaded fplll/fpylll to deb-sci-sage. Please upload them to 
sid & close this bug report when you are ready!

> If no (i.e. "import sage" etc should work in a plain python program), then 
> sage should put its own "sage-env" shell script logic, into the "sage.env" 
> python module instead, so that it gets run properly when things like "from 
> sage.env import *" are done by third-party libs/programs. (And we in Debian 
> would patch this logic for Debian paths.)
> 
> In both cases, this should be documented somewhere upstream in the Sage 
> source code / documentation.
> 
> François & Jeroen (and any other Sage devs here), what do you think? Shall I 
> file an upstream trac ticket about this?
> 
> (In any case, I think the fplll/fpylll bug is fixed, and we can upload + 
> close #870698).
> 
X

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Bug#870874: support sound on ltsp clients with pulseaudio

[Holger Levsen]

On Mon, Aug 07, 2017 at 09:31:41PM +0200, Wolfgang Schweer wrote:
> > thanks for this list, done in git now, please review. (Especially the 
> > part about removing the diverts…)
> Seems to be ok; maybe the changelog entry could be reworded a bit. 

thanks! & feel free to tweak directly in git.
  
> > Also: should we remove gtick now from education-music?
> No, it works.

yup, also tried it on qubes which uses pulseaudio for sound on the VMs and it
worked here as well.


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#732445: debian-policy should encourage verification of upstream cryptographic signaturse

[Russ Allbery]

Holger Levsen  writes:
> On Mon, Aug 07, 2017 at 09:40:22AM -0700, Russ Allbery wrote:

>> In an ideal world, we would have a documented set of metadata for
>> finding upstream releases, of which uscan is just one implementation,
>> and document that in Policy.  This patch doesn't attempt to do that; it
>> tries to find a compromise between the current Policy language
>> ("include a watch file for uscan") and specifying the location of the
>> upstream signing keys, while deferring all of the details to the uscan
>> documentation.

>> I decided to keep this all in the uscan section rather than adding a
>> new section for the upstream signing key location, since right now this
>> is all closely linked to uscan functionality (and to avoid renumbering
>> sections or having a section weirdly separated from the uscan
>> description).

>> How does this look to everyone?

> looks good to me and the reasoning as well. happy to second if you think
> it's ready.

Yup, I think it's ready, as long as dkg is happy with this!

-- 
Russ Allbery (r...@debian.org)   

Bug#870874: support sound on ltsp clients with pulseaudio

[Wolfgang Schweer]

On Mon, Aug 07, 2017 at 05:23:47PM +, Holger Levsen wrote:
> On Sun, Aug 06, 2017 at 10:45:25PM +0200, Wolfgang Schweer wrote:
> > IMO the remaining cleanup things still to do are:
> > 
> > (1) drop /usr/share/debian-edu-config/tools/debian-edu-ltsp-audiodivert 
> > because gtick (metronome) is the only program listed but doesn't 
> > need to be diverted as /dev/dsp isn't used anymore.

Should have been more detailed…

Actually gtick still uses /dev/dsp but 
depends on oss-compat, provided by osspd which itself depends on 
osspd-pulseaudio. So /dev/dsp isn't visibly used anymore for the user 
and debian-edu-ltsp-audiodivert isn't needed as osspd-pulseaudio does 
this job.

> thanks for this list, done in git now, please review. (Especially the 
> part about removing the diverts…)

Seems to be ok; maybe the changelog entry could be reworded a bit. 
 
> Also: should we remove gtick now from education-music?

No, it works.

Wolfgang


signature.asc
Description: PGP signature

Bug#867736: [fbpanel] fbpanel crashes with default config

[Dererk]

tags 867736 +unreproducible +moreinfo

thanks


Hi Will.

I'm unable to reproduce the mentioned behavior. Just to go through it
step-by-step on this, what do you get at the end of the process?

$  mkdir ~/.config/fbpanel && cp /usr/share/fbpanel/default
~/.config/fbpanel/default

$  fbpanel


Cheers,

Dererk


On 08/07/17 23:50, Will Brokenbourgh wrote:
> Package: fbpanel
> Version: 7.0-3
> Severity: serious
>
> When fbpanel is run with the default config file
> (/usr/share/fbpanel/default) it crashes without displaying any GUI.
>
> The crash output from the terminal follows:
> - - -
> *** Error in `fbpanel': double free or corruption (out):
> 0x558a947cda10 ***
> === Backtrace: =
> /lib/x86_64-linux-gnu/libc.so.6(+0x70bcb)[0x7f4d4469bbcb]
> /lib/x86_64-linux-gnu/libc.so.6(+0x76f96)[0x7f4d446a1f96]
> /lib/x86_64-linux-gnu/libc.so.6(+0x777de)[0x7f4d446a27de]
> /usr/lib/x86_64-linux-gnu/libX11.so.6(XFree+0x9)[0x7f4d44f38699]
> fbpanel(get_utf8_property_list+0x141)[0x558a94308e71]
> /usr/lib/fbpanel/libtaskbar.so(+0x453c)[0x7f4d3da7f53c]
> /usr/lib/fbpanel/libtaskbar.so(taskbar_constructor+0x4c0)[0x7f4d3da812f0]
> fbpanel(plugin_start+0xd8)[0x558a9430aee8]
> fbpanel(main+0xdbe)[0x558a943041ce]
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f4d4464b2b1]
> fbpanel(_start+0x2a)[0x558a9430468a]
> === Memory map: 
> 558a942fb000-558a9431 r-xp  08:24
> 1194991/usr/bin/fbpanel
> 558a9450f000-558a9451 r--p 00014000 08:24
> 1194991/usr/bin/fbpanel
> 558a9451-558a94511000 rw-p 00015000 08:24
> 1194991/usr/bin/fbpanel
> 558a94726000-558a9488d000 rw-p  00:00
> 0  [heap]
> 7f4d3000-7f4d30022000 rw-p  00:00 0
> 7f4d30022000-7f4d3400 ---p  00:00 0
> 7f4d3400-7f4d34021000 rw-p  00:00 0
> 7f4d34021000-7f4d3800 ---p  00:00 0
> 7f4d3800-7f4d38021000 rw-p  00:00 0
> 7f4d38021000-7f4d3c00 ---p  00:00 0
> 7f4d3d643000-7f4d3d659000 r-xp  08:24
> 3015814/lib/x86_64-linux-gnu/libgcc_s.so.1
> 7f4d3d659000-7f4d3d858000 ---p 00016000 08:24
> 3015814/lib/x86_64-linux-gnu/libgcc_s.so.1
> 7f4d3d858000-7f4d3d859000 r--p 00015000 08:24
> 3015814/lib/x86_64-linux-gnu/libgcc_s.so.1
> 7f4d3d859000-7f4d3d85a000 rw-p 00016000 08:24
> 3015814/lib/x86_64-linux-gnu/libgcc_s.so.1
> 7f4d3d873000-7f4d3d879000 r-xp  08:24 1187724
> /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-xpm.so
> 7f4d3d879000-7f4d3da78000 ---p 6000 08:24 1187724
> /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-xpm.so
> 7f4d3da78000-7f4d3da79000 r--p 5000 08:24 1187724
> /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-xpm.so
> 7f4d3da79000-7f4d3da7a000 rw-p 6000 08:24 1187724
> /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-xpm.so
> 7f4d3da7b000-7f4d3da83000 r-xp  08:24
> 1195014/usr/lib/fbpanel/libtaskbar.so
> 7f4d3da83000-7f4d3dc82000 ---p 8000 08:24
> 1195014/usr/lib/fbpanel/libtaskbar.so
> 7f4d3dc82000-7f4d3dc83000 r--p 7000 08:24
> 1195014/usr/lib/fbpanel/libtaskbar.so
> 7f4d3dc83000-7f4d3dc84000 rw-p 8000 08:24
> 1195014/usr/lib/fbpanel/libtaskbar.so
> 7f4d3dc8b000-7f4d3dc8d000 r-xp  08:24
> 1195019/usr/lib/fbpanel/libwincmd.so
> 7f4d3dc8d000-7f4d3de8c000 ---p 2000 08:24
> 1195019/usr/lib/fbpanel/libwincmd.so
> 7f4d3de8c000-7f4d3de8d000 r--p 1000 08:24
> 1195019/usr/lib/fbpanel/libwincmd.so
> 7f4d3de8d000-7f4d3de8e000 rw-p 2000 08:24
> 1195019/usr/lib/fbpanel/libwincmd.so
> 7f4d3de91000-7f4d3de92000 ---p  00:00 0
> 7f4d3de92000-7f4d3e692000 rw-p  00:00 0
> 7f4d3e692000-7f4d3e693000 ---p  00:00 0
> 7f4d3e693000-7f4d3ee93000 rw-p  00:00 0
> 7f4d3ee93000-7f4d3ee95000 r-xp  08:24
> 3020637/lib/x86_64-linux-gnu/libutil-2.24.so
> 7f4d3ee95000-7f4d3f094000 ---p 2000 08:24
> 3020637/lib/x86_64-linux-gnu/libutil-2.24.so
> 7f4d3f094000-7f4d3f095000 r--p 1000 08:24
> 3020637/lib/x86_64-linux-gnu/libutil-2.24.so
> 7f4d3f095000-7f4d3f096000 rw-p 2000 08:24
> 3020637/lib/x86_64-linux-gnu/libutil-2.24.so
> 7f4d3f0b3000-7f4d3f0e9000 r-xp  08:24 1317789
> /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so
> 7f4d3f0e9000-7f4d3f2e9000 ---p 00036000 08:24 1317789
> /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so
> 7f4d3f2e9000-7f4d3f2ef000 r--p 00036000 08:24 1317789
> /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so
> 7f4d3f2ef000-7f4d3f2f rw-p 0003c000 08:24 1317789
> /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so
> 

Bug#802658: libesmtp: Should support TLS 1.1+

[Sebastian Andrzej Siewior]

On 2017-08-07 21:00:05 [+0200], Salvatore Bonaccorso wrote:
> Hi Sebastian
Hi Salvatore,

> Thanks for review. The reason I did that is indeed, to have a patch
> which is most acceptable for upstream to include, independent on
> Debian, although upstream since I initially pinged never replied to my
> queries :-(. Thus as well the explicit version checking, since AFAIU
> the use of the SSLv23_client_method is deprecated in favour of
> TLS_client_method. 
…
> Did I missunderstood something here?
no, you are absolutely right. I just though SSLv23_client_method is
something that currently works for everybody and is the smallest change
given that old-stable Stretch won't be able to connect stable-Buster in
approx. two years (so it coul be a candidate for s-p-u).

However, yes, future proof, this is what the openssl project currently
suggests.

> Regards,
> Salvatore

Sebastian

Bug#871413: diffoscope: AssertionError with cups/2.2.4-3 in unstable/amd64

[Mattia Rizzolo]

Package: diffoscope
Version: 85
Severity: important

As seen in tests.reproducible-builds.org today:

Mon Aug  7 15:30:34 UTC 2017  I: diffoscope 85 will be used to compare the two 
builds:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/diffoscope/main.py", line 396, in main
sys.exit(run_diffoscope(parsed_args))
  File "/usr/lib/python3/dist-packages/diffoscope/main.py", line 376, in 
run_diffoscope
PresenterManager().output(difference, parsed_args, has_differences)
  File "/usr/lib/python3/dist-packages/diffoscope/presenters/formats.py", line 
106, in output
data['klass'].run(data, difference, parsed_args)
  File "/usr/lib/python3/dist-packages/diffoscope/presenters/html/html.py", 
line 713, in run
jquery_url=parsed_args.jquery_url,
  File "/usr/lib/python3/dist-packages/diffoscope/presenters/html/html.py", 
line 705, in output_html
self.output_difference(ctx, difference)
  File "/usr/lib/python3/dist-packages/diffoscope/presenters/html/html.py", 
line 615, in output_difference
assert node is difference
AssertionError


(I haven't tried to reproduce it nor anything)

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#750946: libhtml-html5-parser-perl: UTF-8 character breaks parse_file

[gregor herrmann]

On Mon, 07 Aug 2017 08:48:36 -0700, Gregory Williams wrote:

> On Aug 7, 2017, at 8:26 AM, gregor herrmann  wrote:
> > This looks indeed much better than my crude workarounds, thanks for
> > that!
> > Do you think you can take this up with upstream?
> Yes, I think Kjetil and I can work on getting this merged upstream.

Aweseome, thank you!


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Bug#869938: Raising severity to serious since g-s-d 3.24 has been uploaded to unstable

[Robert Luberda]

Jeremy Bicha pisze:
> Control: severity -1 serious
> 
> gnome-settings-daemon 3.24 has been uploaded to unstable. We intend to
> NMU your package today so that the transition is not delayed.

I have the package ready, I will upload it shortly.


Regards,
robert

Bug#867978: /usr/bin/qemu-system-x86_64: virtio-net with vhost is broken with legacy interrupts

[Stefan Fritsch]

Hi,

is it ok if I upload an NMU with the attached patch to 
stable-proposed-updates?

Cheers,
Stefan
diff -Nru qemu-2.8+dfsg/debian/changelog qemu-2.8+dfsg/debian/changelog
--- qemu-2.8+dfsg/debian/changelog  2017-08-02 15:57:34.0 +0200
+++ qemu-2.8+dfsg/debian/changelog  2017-08-07 18:03:51.0 +0200
@@ -1,3 +1,10 @@
+qemu (1:2.8+dfsg-6+deb9u3) stretch; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix virtio-net with vhost with legacy interrupts. Closes: #867978
+
+ -- Stefan Fritsch   Mon, 07 Aug 2017 18:03:51 +0200
+
 qemu (1:2.8+dfsg-6+deb9u2) stretch-security; urgency=high
 
   * actually apply the nbd server patches, not only include in debian/patches/
diff -Nru qemu-2.8+dfsg/debian/patches/fix-vhost-net-legacy-irq.patch 
qemu-2.8+dfsg/debian/patches/fix-vhost-net-legacy-irq.patch
--- qemu-2.8+dfsg/debian/patches/fix-vhost-net-legacy-irq.patch 1970-01-01 
01:00:00.0 +0100
+++ qemu-2.8+dfsg/debian/patches/fix-vhost-net-legacy-irq.patch 2017-08-07 
18:03:51.0 +0200
@@ -0,0 +1,50 @@
+From: Michael S. Tsirkin 
+Date: Fri, 17 Feb 2017 04:52:16 +0200
+X-Dgit-Generated: 1:2.8+dfsg-6+deb9u2.1 
6290f12ade202d40e5ed6535cd3c6a3049aa6888
+Subject: virtio: Fix no interrupt when not creating msi controller
+
+For ARM virt machine, if we use virt-2.7 which will not create ITS node,
+the virtio-net can not recieve interrupts so it can't get ip address
+through dhcp.
+This fixes commit 83d768b(virtio: set ISR on dataplane notifications).
+
+Signed-off-by: Shannon Zhao 
+Reviewed-by: Michael S. Tsirkin 
+Signed-off-by: Michael S. Tsirkin 
+
+---
+
+--- qemu-2.8+dfsg.orig/hw/virtio/virtio.c
 qemu-2.8+dfsg/hw/virtio/virtio.c
+@@ -1387,6 +1387,12 @@ void virtio_notify_irqfd(VirtIODevice *v
+ event_notifier_set(>guest_notifier);
+ }
+ 
++static void virtio_irq(VirtQueue *vq)
++{
++virtio_set_isr(vq->vdev, 0x1);
++virtio_notify_vector(vq->vdev, vq->vector);
++}
++
+ void virtio_notify(VirtIODevice *vdev, VirtQueue *vq)
+ {
+ if (!virtio_should_notify(vdev, vq)) {
+@@ -1394,8 +1400,7 @@ void virtio_notify(VirtIODevice *vdev, V
+ }
+ 
+ trace_virtio_notify(vdev, vq);
+-virtio_set_isr(vq->vdev, 0x1);
+-virtio_notify_vector(vdev, vq->vector);
++virtio_irq(vq);
+ }
+ 
+ void virtio_notify_config(VirtIODevice *vdev)
+@@ -2023,7 +2028,7 @@ static void virtio_queue_guest_notifier_
+ {
+ VirtQueue *vq = container_of(n, VirtQueue, guest_notifier);
+ if (event_notifier_test_and_clear(n)) {
+-virtio_notify_vector(vq->vdev, vq->vector);
++virtio_irq(vq);
+ }
+ }
+ 
diff -Nru qemu-2.8+dfsg/debian/patches/series 
qemu-2.8+dfsg/debian/patches/series
--- qemu-2.8+dfsg/debian/patches/series 2017-08-02 15:57:00.0 +0200
+++ qemu-2.8+dfsg/debian/patches/series 2017-08-07 18:03:51.0 +0200
@@ -42,3 +42,4 @@
 slirp-check-len-against-dhcp-options-array-end-CVE-2017-11434.patch
 exec-use-qemu_ram_ptr_length-to-access-guest-ram-CVE-2017-11334.patch
 usb-redir-fix-stack-overflow-in-usbredir_log_data-CVE-2017-10806.patch
+fix-vhost-net-legacy-irq.patch

Bug#802658: libesmtp: Should support TLS 1.1+

[Kurt Roeckx]

On Mon, Aug 07, 2017 at 09:00:05PM +0200, Salvatore Bonaccorso wrote:
> Hi Sebastian
> 
> On Mon, Aug 07, 2017 at 07:15:19PM +0200, Sebastian Andrzej Siewior wrote:
> > On 2017-08-07 14:26:07 [+0200], Salvatore Bonaccorso wrote:
> > > Control: severity important
> > 
> > as in SSL not working anymore in unstable for libesmtp.
> > 
> > > Hi Jeremy,
> > Hi Salvatore,
> > 
> > > Please find attached a (refreshed) patch which is still valid to add
> > > the proper support for TLSv1.1+
> > 
> > Description: Add TLSv1.1 and TLSv1.2 support
> > Origin: vendor
> > Bug-Debian: https://bugs.debian.org/802658
> > Author: Salvatore Bonaccorso 
> > Last-Update: 2015-11-07
> > 
> > --- a/smtp-tls.c
> > +++ b/smtp-tls.c
> > @@ -197,11 +197,24 @@ starttls_create_ctx (smtp_session_t sess
> >ckf_t status;
> >  
> >/* The decision not to support SSL v2 and v3 but instead to use only
> > - TLSv1 is deliberate.  This is in line with the intentions of RFC
> > + TLSv1.X is deliberate.  This is in line with the intentions of RFC
> >   3207.  Servers typically support SSL as well as TLS because some
> >   versions of Netscape do not support TLS.  I am assuming that all
> >   currently deployed servers correctly support TLS.  */
> > -  ctx = SSL_CTX_new (TLSv1_client_method ());
> > +#if (OPENSSL_VERSION_NUMBER >= 0x1010L) && \
> > +!defined(LIBRESSL_VERSION_NUMBER)  && !defined(OPENSSL_IS_BORINGSSL)
> > +ctx = SSL_CTX_new (TLS_client_method ());
> > +#else
> > +ctx = SSL_CTX_new (SSLv23_client_method ());
> > +#endif
> > +
> > +#ifdef OPENSSL_NO_SSL3
> > +SSL_CTX_set_options(ctx, SSL_OP_NO_SSLv3);
> > +#endif
> > +
> > +#ifdef OPENSSL_NO_SSL2
> > +SSL_CTX_set_options(ctx, SSL_OP_NO_SSLv2);
> > +#endif
> >  
> >/* Load our keys and certificates.  To avoid messing with configuration
> >   variables etc, use fixed paths for the certificate store.  These are
> > 
> > This looks good. I would however just replace TLSv1_client_method() with
> > SSLv23_client_method() (without the version check) and be done with it.
> > Setting the NO_SSLvX thingy is a nop in Debian but upstream might be
> > happy to see it.
> 
> Thanks for review. The reason I did that is indeed, to have a patch
> which is most acceptable for upstream to include, independent on
> Debian, although upstream since I initially pinged never replied to my
> queries :-(. Thus as well the explicit version checking, since AFAIU
> the use of the SSLv23_client_method is deprecated in favour of
> TLS_client_method. 
> 
> The POD for SSL_CTX_new states this explicitly:
> 
> SSLv23_method(), SSLv23_server_method() and SSLv23_client_method()
> were deprecated and the preferred TLS_method(), TLS_server_method()
> and TLS_client_method() functions were introduced in OpenSSL 1.1.0.
> 
> Did I missunderstood something here?

Even tought it's deprecated, it's unlikely we'll remove the
compatiblity define any time soon. So either way really works for
me.


Kurt

Bug#870813: wget: Please hash the hostname in ~/.wget-hsts files

[Noël Köthe]

Hello Chris,

Am Samstag, den 05.08.2017, 08:59 -0400 schrieb Chris Lamb:

> I can't help but think of ~/.ssh/known_hosts which moved to hashing
> the hostname for various security/privacy concerns. Shouldn't wget
> make the parallel change?

Upstream Tim answered but the answer didn't reach you. You can read it
here:

https://savannah.gnu.org/bugs/index.php?51666

or

https://bugs.debian.org/870813

Regards

Noel

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

Bug#871412: move libmpdclient.pc to a multiarch location

[Helmut Grohne]

Package: libmpdclient-dev
Version: 2.9-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:mpc src:ncmpc src:ncmpcpp

The packages listed under affects fail to cross build from source,
because they cannot find libmpdclient.pc. During cross compilation,
pkg-config does not search /usr/lib/pkgconfig. It only searches
/usr/share/pkgconfig and /usr/lib//pkgconfig. Thus
libmpdclient.pc should be moved to the latter directory. The attached
patch achieves just that. Please consider applying it.

Helmut
diff -u libmpdclient-2.9/debian/changelog libmpdclient-2.9/debian/changelog
--- libmpdclient-2.9/debian/changelog
+++ libmpdclient-2.9/debian/changelog
@@ -1,3 +1,10 @@
+libmpdclient (2.9-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Pass a multiarch --libdir to ./configure (Closes: #-1)
+
+ -- Helmut Grohne   Mon, 07 Aug 2017 20:58:06 +0200
+
 libmpdclient (2.9-1) UNRELEASED; urgency=low
 
   * New upstream release (Closes: #671094).
diff -u libmpdclient-2.9/debian/libmpdclient-dev.install 
libmpdclient-2.9/debian/libmpdclient-dev.install
--- libmpdclient-2.9/debian/libmpdclient-dev.install
+++ libmpdclient-2.9/debian/libmpdclient-dev.install
@@ -1,6 +1,6 @@
 usr/include/*
-usr/lib/lib*.a
-usr/lib/lib*.so
-usr/lib/pkgconfig/*
+usr/lib/*/lib*.a
+usr/lib/*/lib*.so
+usr/lib/*/pkgconfig/*
 usr/share/vala/vapi/libmpdclient.vapi
 
diff -u libmpdclient-2.9/debian/libmpdclient2.install 
libmpdclient-2.9/debian/libmpdclient2.install
--- libmpdclient-2.9/debian/libmpdclient2.install
+++ libmpdclient-2.9/debian/libmpdclient2.install
@@ -1,2 +1,2 @@
-usr/lib/lib*.so.*
+usr/lib/*/lib*.so.*
 
diff -u libmpdclient-2.9/debian/rules libmpdclient-2.9/debian/rules
--- libmpdclient-2.9/debian/rules
+++ libmpdclient-2.9/debian/rules
@@ -8,8 +8,7 @@
 
 # These are used for cross-compiling and for saving the configure script
 # from having to guess our platform (since we know it already)
-DEB_HOST_GNU_TYPE   ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
-DEB_BUILD_GNU_TYPE  ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
+include /usr/share/dpkg/architecture.mk
 
 CPPFLAGS = $(shell dpkg-buildflags --get CPPFLAGS)
 CFLAGS = $(shell dpkg-buildflags --get CFLAGS)
@@ -36,6 +35,7 @@
--build=$(DEB_BUILD_GNU_TYPE) \
--prefix=/usr \
--mandir=\$${prefix}/share/man \
+   --libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH) \
CPPFLAGS="$(CPPFLAGS)" CFLAGS="$(CFLAGS)"
 
 build: build-arch build-indep
@@ -70,7 +70,7 @@
$(MAKE) install DESTDIR=$(CURDIR)/debian/tmp

# we do not want .la files in Debian
-   rm -f debian/tmp/usr/lib/libmpdclient.la
+   rm -f debian/tmp/usr/lib/*/libmpdclient.la

# these files do not include any useful content
rm -f debian/tmp/usr/share/doc/libmpdclient/README

Bug#596513: [git-buildpackage/master] dch: support passing arbitrary dch command line options

[Iain Lane]

On Mon, Aug 07, 2017 at 08:42:56PM +0200, Guido Günther wrote:
> tag 596513 pending
> tag 682854 pending
> thanks

Amazing! I got this email and was like "what in the world is that
about?" - well, it's a bug from ~7 years ago being fixed. Nice :).

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]


signature.asc
Description: PGP signature

Bug#853513: libvigraimpex: ftbfs with GCC-7

[Daniel Stender]

On 07.08.2017 20:26, Matthias Klose wrote:
> Control: tags -1 + patch
> 
> patch at
> http://launchpadlibrarian.net/332312910/libvigraimpex_1.10.0+git20160211.167be93+dfsg-2build3_1.10.0+git20160211.167be93+dfsg-2ubuntu1.diff.gz

Great! I'll take care of it shortly.

DS

-- 
4096R/DF5182C8 (sten...@debian.org)
http://www.danielstender.com/

Bug#802658: libesmtp: Should support TLS 1.1+

[Salvatore Bonaccorso]

Hi Sebastian

On Mon, Aug 07, 2017 at 07:15:19PM +0200, Sebastian Andrzej Siewior wrote:
> On 2017-08-07 14:26:07 [+0200], Salvatore Bonaccorso wrote:
> > Control: severity important
> 
> as in SSL not working anymore in unstable for libesmtp.
> 
> > Hi Jeremy,
> Hi Salvatore,
> 
> > Please find attached a (refreshed) patch which is still valid to add
> > the proper support for TLSv1.1+
> 
> Description: Add TLSv1.1 and TLSv1.2 support
> Origin: vendor
> Bug-Debian: https://bugs.debian.org/802658
> Author: Salvatore Bonaccorso 
> Last-Update: 2015-11-07
> 
> --- a/smtp-tls.c
> +++ b/smtp-tls.c
> @@ -197,11 +197,24 @@ starttls_create_ctx (smtp_session_t sess
>ckf_t status;
>  
>/* The decision not to support SSL v2 and v3 but instead to use only
> - TLSv1 is deliberate.  This is in line with the intentions of RFC
> + TLSv1.X is deliberate.  This is in line with the intentions of RFC
>   3207.  Servers typically support SSL as well as TLS because some
>   versions of Netscape do not support TLS.  I am assuming that all
>   currently deployed servers correctly support TLS.  */
> -  ctx = SSL_CTX_new (TLSv1_client_method ());
> +#if (OPENSSL_VERSION_NUMBER >= 0x1010L) && \
> +!defined(LIBRESSL_VERSION_NUMBER)  && !defined(OPENSSL_IS_BORINGSSL)
> +ctx = SSL_CTX_new (TLS_client_method ());
> +#else
> +ctx = SSL_CTX_new (SSLv23_client_method ());
> +#endif
> +
> +#ifdef OPENSSL_NO_SSL3
> +SSL_CTX_set_options(ctx, SSL_OP_NO_SSLv3);
> +#endif
> +
> +#ifdef OPENSSL_NO_SSL2
> +SSL_CTX_set_options(ctx, SSL_OP_NO_SSLv2);
> +#endif
>  
>/* Load our keys and certificates.  To avoid messing with configuration
>   variables etc, use fixed paths for the certificate store.  These are
> 
> This looks good. I would however just replace TLSv1_client_method() with
> SSLv23_client_method() (without the version check) and be done with it.
> Setting the NO_SSLvX thingy is a nop in Debian but upstream might be
> happy to see it.

Thanks for review. The reason I did that is indeed, to have a patch
which is most acceptable for upstream to include, independent on
Debian, although upstream since I initially pinged never replied to my
queries :-(. Thus as well the explicit version checking, since AFAIU
the use of the SSLv23_client_method is deprecated in favour of
TLS_client_method. 

The POD for SSL_CTX_new states this explicitly:

SSLv23_method(), SSLv23_server_method() and SSLv23_client_method()
were deprecated and the preferred TLS_method(), TLS_server_method()
and TLS_client_method() functions were introduced in OpenSSL 1.1.0.

Did I missunderstood something here?

So ok I will again do some testing now that the new version is in
unstable.

Regards,
Salvatore

Bug#871411: mtink: [INTL:de] Initial German po4a translation

[Chris Leick]

Package: mtink
Version: 1.0.16-9\
Severity: wishlist
Tags: l10n patch



Hi,

please find attached the initial German po4a translation. I've marked 
some typos in the original file with »FIXME« in this translation.


Kind regards,
Chris


de.po.gz
Description: application/gzip

Bug#856139: [pkg-go] Bug#856139: Bug#856139: certspotter: long description advertises commercial service

[Vincent Bernat]

 ❦  7 août 2017 18:12 GMT, "Dr. Bas Wijnen"  :

>> We have all kind of software advertising non-free services. Search for
>> "Google" or "Amazon". The comparison is even unfair as the service
>> advertised here is available as free software (not the case for most
>> services from Amazon and Google we advertise).
>
> If other packages are worse, that means they should be fixed, not that this
> should be allowed.
>
>> Example: [s3cmd]
>
> How is this not in contrib?  This software is useless without the non-free
> service (which is also software, and it is not in main) from Amazon.  Policy
> even mentions as an example for things in contrib: wrapper packages or other
> sorts of free accessories for non-free programs.  That's exactly what
> this is.
>
> I didn't know that this was in main, and I expect most others to not know
> either.  But I don't think they should be.  I wouldn't expect this to be
> controversial, but it seems that it is, given that you suggest they obviously
> belong in main?
>
> To be clear: the sort of software (of this type) I expect in main is like
> mumble: it connects to a server, and you can connect to a commercially hosted
> server if you want to, but you can also run your own server, because it's free
> software.  If the mumble server would not be free, and the only way to use the
> client was to connect to a commercial server, mumble should not be in main.
>
> As I wrote, I expected there to be consensus on this.  Am I incorrect about
> that?

In this case, free S3 implementations exist (like Swift, available
in Debian). However, it is easy to find other packages interacting with
proprietary services without a free implementation. For example, any
package interacting with Google Cloud (golang-google-cloud package).
-- 
Your manuscript is both good and original, but the part that is good is not
original and the part that is original is not good.
-- Samuel Johnson


signature.asc
Description: PGP signature

Bug#845255: debian-policy: Include best practices for packaging database applications

[Paul Gevers]

Hi,

As promised, I send the converted dbapp-policy documentation to this
bug. Credits go to Osamu, any bug is mine.

Paul


http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd; [


]>



Best practices for packaging database applications




Sean Finney









This draft describes a set of guidelines and best practices to be implemented
by the maintainers of database application packages.  Pending a final draft,
desire, and acceptance by the developer community at large, this may serve as
the foundation for an official policy--or it may simply remain as it is.



2005sean finney 
sean...@debian.org


This document is licensed under the https://spdx.org/licenses/AFL-2.1.html;>Academic Free License, Version
2.1






Database Applications
Scope

In this document a "database application" is any program that relies on some
form of data storage outside the scope of the program's execution.  This is
primarily intended to encompass applications which rely on a relational
database server or their own persistent storage mechanism, though effectively
is a much larger set of applications.  In the future this scope may have to be
narrowed to avoid ambiguity and be more effective as a policy.



Terminology

For the purposes of this document, there are two types of databases:
persistent and cached.


Persistent databases contain data that can not be entirely
reconstituted in the case that the database is removed.  Also included are
databases that if removed would cause serious denial of service (making a
system unstable/unusable) or security concerns.  Applications using this
category of databases are the primary focus of this document.  Examples:




relational database servers providing storage to other applications.




web applications using a relational database




openldap's slapd databases




rrd files containing accumulated/historical data.




Cached databases are a specific group of databases which
upon their removal could be sufficiently regenerated, and could be removed
without causing serious denial of service or security concerns.  Examples
include:




debconf responses




locate database




caching nameserver data




apt's list of available packages





Placement of databases

Both persistent and cached databases fall under already defined guidelines in
the FHS; persistent data must be placed under
/var/lib/packagename, and cached data under
/var/cache/packagename, respectively  or
an equivalently compliant location  .  The remainder of this
document primarily addresses the former.



Installation related issues

The following descriptions are divided into different parts, based on the
action being performed.  For each process, the acceptable behavior of database
application packages is outlined.

Automatic Database 
Configuration/Prompting

It must always be assumed that the local admin knows more than any automated
system.  He/She must be given the ability to opt out of any "assistance" on the
part of the package maintainer.  Packages providing any such automated
assistance may do so by default if and only if the opt-out debconf prompt is
equal to or greater than priority high.  With this in mind, directions for
manually installing (and upgrading if relevant) the database must be included
in the documentation for the package.



Database Installation

For packages providing automated assistance, database
installation/configuration should be considered as part of the package
installation process.  A failure to install a database should be considered a
failure to install the package and should result in an error value returned by
the relevant maintainer script.  Packages may provide a "try again" option to
re-attempt configuration.  Any such "try again" features here or elsewhere
mentioned in this document must have a default negative response value,
otherwise infinite loops could occur for noninteractive installs.


To properly handle package reinstallation and reconfiguration, any automated
assistance must allow for a package to be reinstalled at the same version
without removing or overwriting existing application data.  Package
reconfiguration may do so.



Database Upgrading

Occasionally a new upstream version of an application will require
modifications to be made to the application's underlying database.  If an
automated system is to assist in such an upgrade, it should be considered as a
part of the package upgrade process; failure to upgrade the database should be
considered a failure to upgrade the package.  This is the only way to safely
guarantee the chance to reattempt the upgrade with respect to the underlying
database.


Furthermore, any automated system that makes modifications to a database during
upgrade must provide the ability to back-up the database before proceeding.
Packages may perform such backups automatically, or prompt the admin via
debconf.  Failure to back up the database should also be considered a failure
in the upgrade process of the whole package.  As in 

Bug#871410: cramfsswap FTCBFS: uses the build architecture compiler

[Helmut Grohne]

Source: cramfsswap
Version: 1.4.1-1.1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

cramfsswap fails to cross build from source, because its Makefile
hard codes the build architecture compiler gcc. After making it
substitutable and substituting it by dh_auto_build, cramfsswap cross
builds successfully. Please consider applying the attached patch.

Helmut
diff --minimal -Nru cramfsswap-1.4.1/Makefile cramfsswap-1.4.1/Makefile
--- cramfsswap-1.4.1/Makefile   2007-10-14 23:37:58.0 +0200
+++ cramfsswap-1.4.1/Makefile   2017-08-07 20:43:44.0 +0200
@@ -4,7 +4,7 @@
 debian: cramfsswap
 
 cramfsswap: cramfsswap.c
-   gcc -Wall -g -O -o cramfsswap -lz cramfsswap.c
+   $(CC) -Wall -g -O -o cramfsswap -lz cramfsswap.c
 
 strip:
strip cramfsswap
diff --minimal -Nru cramfsswap-1.4.1/debian/changelog 
cramfsswap-1.4.1/debian/changelog
--- cramfsswap-1.4.1/debian/changelog   2016-12-18 12:50:25.0 +0100
+++ cramfsswap-1.4.1/debian/changelog   2017-08-07 20:43:44.0 +0200
@@ -1,3 +1,12 @@
+cramfsswap (1.4.1-1.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ Let dh_auto_build pass cross compilers to make.
++ Make compiler substitutable in Makefile
+
+ -- Helmut Grohne   Mon, 07 Aug 2017 20:43:44 +0200
+
 cramfsswap (1.4.1-1.1) unstable; urgency=medium
 
   * Non-maintainer upload
diff --minimal -Nru cramfsswap-1.4.1/debian/rules cramfsswap-1.4.1/debian/rules
--- cramfsswap-1.4.1/debian/rules   2007-10-14 23:41:26.0 +0200
+++ cramfsswap-1.4.1/debian/rules   2017-08-07 20:32:34.0 +0200
@@ -11,7 +11,7 @@
 build: build-stamp
 build-stamp: 
dh_testdir
-   $(MAKE) debian
+   dh_auto_build -- debian
touch build-stamp
 
 clean:

Bug#871409: libio-socket-ssl-perl: FTBFS: t/protocol_version.t failure

[Niko Tyni]

Package: libio-socket-ssl-perl
Version: 2.049-1
Severity: serious
User: debian-p...@lists.debian.org
Usertags: autopkgtest

As noticed by ci.debian.net:

 https://ci.debian.net/packages/libi/libio-socket-ssl-perl/unstable/amd64/

this package fails to build on current sid/amd64. debci.log indicates
this is fallout from openssl disabling TLS 1.0 and 1.1 recently:

 -openssl 1.1.0f-3
 +openssl 1.1.0f-4

See https://lists.debian.org/debian-devel-announce/2017/08/msg4.html

>From the build log:


  # looks like OpenSSL was compiled without SSLv3 support
  
  #   Failed test 'accept TLSv1'
  #   at t/protocol_version.t line 125.
  
  #   Failed test 'accept SSLv23:!TLSv1_2:!TLSv1_1'
  #   at t/protocol_version.t line 125.
  
  #   Failed test 'accept TLSv1_1'
  #   at t/protocol_version.t line 125.
  
  #   Failed test 'accept SSLv23:!TLSv1_2'
  #   at t/protocol_version.t line 125.
  # Looks like you failed 4 tests of 7.
  t/protocol_version.t .. 
  ok 1 - accept SSLv23 with any, got TLSv1_2
  not ok 2 - accept TLSv1
  not ok 3 - accept SSLv23:!TLSv1_2:!TLSv1_1
  not ok 4 - accept TLSv1_1
  not ok 5 - accept SSLv23:!TLSv1_2
  ok 6 - accept TLSv1_2 with TLSv1_2
  ok 7 - accept SSLv23 with TLSv1_2
  1..7
  Dubious, test returned 4 (wstat 1024, 0x400)
  Failed 4/7 subtests 
  [...]
  Test Summary Report
  ---
  t/protocol_version.t(Wstat: 1024 Tests: 7 Failed: 4)
Failed tests:  2-5
Non-zero exit status: 4
  t/sessions.t(Wstat: 256 Tests: 11 Failed: 1)
Failed test:  10
Non-zero exit status: 1
Parse errors: Bad plan.  You planned 35 tests but ran 11.
  Files=36, Tests=747, 42 wallclock secs ( 0.27 usr  0.04 sys +  7.04 cusr  
0.73 csys =  8.08 CPU)
  Result: FAIL
 
-- 
Niko Tyni   nt...@debian.org

Bug#596513: [git-buildpackage/master] dch: support passing arbitrary dch command line options

[Guido Günther]

tag 596513 pending
tag 682854 pending
thanks

Date:   Mon Aug 7 15:26:21 2017 -0300
Author: Guido Günther 
Commit ID: 01a4a7fe91b8fb7193a1344409855c4f61e1f880
Commit URL: 
https://git.sigxcpu.org/cgit/git-buildpackage//commit/?id=01a4a7fe91b8fb7193a1344409855c4f61e1f880
Patch URL: 
https://git.sigxcpu.org/cgit/git-buildpackage//patch/?id=01a4a7fe91b8fb7193a1344409855c4f61e1f880

dch: support passing arbitrary dch command line options

Closes: #596513, #682854

  

Bug#869986: [Debian-ha-maintainers] Bug#869986: Bug#869986: pacemaker FTBFS: missing symbols

[Ferenc Wágner]

Valentin Vidic  writes:

> Right, the upstream is having problems with libqb, but maybe they don't
> see the problem with pacemaker libs if they are not checking the
> exported symbols.

There's no problem with the Pacemaker libs, the "missing" symbols are a
manifestation of the binutils incompatibility in the libqb headers.

> Do you know if these start/stop symbols were used anywhere or it would
> be safe to drop them from the pacemaker libs?

They are not used explicitly, but the bug report you found mentions
silent loss of log messages, let's not paper over that.
-- 
Feri

Bug#871371: singularity-container: FTBFS: help2man: can't get `--version' info from /tmp/tmp.YU5T8oOc4W/run-singularity

[Yaroslav Halchenko]

severity 871371 important
tags 871371 + unreproducible
thanks

Ran rebuild which succeeded just fine on up to date sid for both amd64
and i386 (binary only)

Would need to be able to reproduce to figure out WTF

On Mon, 07 Aug 2017, Lucas Nussbaum wrote:

> Source: singularity-container
> Version: 2.3.1-1
> Severity: serious
> Tags: buster sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20170807 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):
> > make[1]: Entering directory '/<>'
> > : # Very sloppy man pages for now
> > debian/generate_manpages debian/singularity-container
> > help2man: can't get `--version' info from 
> > /tmp/tmp.YU5T8oOc4W/run-singularity
> > Try `--no-discard-stderr' if option outputs to stderr
> > debian/rules:21: recipe for target 'override_dh_installman' failed
> > make[1]: *** [override_dh_installman] Error 1

> The full build log is available from:
>
> http://aws-logs.debian.net/2017/08/07/singularity-container_2.3.1-1_unstable.log

> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

> About the archive rebuild: The rebuild was done on EC2 VM instances from
> Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> failed build was retried once to eliminate random failures.


-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik

Bug#871279: libdolfin2016.2: requires rebuild against GCC 7 and symbols/shlibs bump

[Drew Parsons]

On Mon, 2017-08-07 at 17:44 +, Mattia Rizzolo wrote:
> 
> > dolfin 2017.1 is in the NEW queue, so that upgrade will handle this
> > bug.
> 
> Is the binary you uploaded built with gcc-7?  Otherwise that would
> not fix this bug.

It's been sitting in NEW for a month, so it would have been gcc-6 I
think.  But the upload is to experimental.  I figure we can ignore
anything in experimental, the symbols will get reset for the new ABI
when we drop it into unstable.

Drew

Bug#871408: lookup FTCBFS: uses the build architecture compiler

[Helmut Grohne]

Source: lookup
Version: 1.08b-11
Severity: normal
Tags: patch

lookup fails to cross build from source, because it uses the build
architecture compiler. dh_auto_build passes cross compilers to make, so
after switching to it, lookup cross builds successfully. Please consider
applying the attached patch.

Helmut
diff -u lookup-1.08b/debian/control lookup-1.08b/debian/control
--- lookup-1.08b/debian/control
+++ lookup-1.08b/debian/control
@@ -2,7 +2,7 @@
 Section: text
 Priority: optional
 Maintainer: Ludovic Drolez 
-Build-Depends: debhelper (>> 2.0.0), groff-base
+Build-Depends: debhelper (>= 7), groff-base
 Standards-Version: 3.8.3
 
 Package: lookup
diff -u lookup-1.08b/debian/rules lookup-1.08b/debian/rules
--- lookup-1.08b/debian/rules
+++ lookup-1.08b/debian/rules
@@ -22,7 +22,7 @@
dh_testdir
 
# Add here commands to compile the package.
-   $(MAKE) CFLAGS="$(CFLAGS)"
+   dh_auto_build CFLAGS="$(CFLAGS)"
(cd doc; soelim lookup.man) > lookup.man
 
touch build-stamp
diff -u lookup-1.08b/debian/changelog lookup-1.08b/debian/changelog
--- lookup-1.08b/debian/changelog
+++ lookup-1.08b/debian/changelog
@@ -1,3 +1,10 @@
+lookup (1.08b-11.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_build pass cross compilers to make. Closes: #-1
+
+ -- Helmut Grohne   Mon, 07 Aug 2017 19:57:12 +0200
+
 lookup (1.08b-11) unstable; urgency=low
 
   * renamed the getline() function to mygetline(). Closes: #552827

Bug#856139: certspotter: long description advertises commercial service

[Shengjing Zhu]

On Tue, Aug 8, 2017 at 2:12 AM, Dr. Bas Wijnen  wrote:
>> Example: [s3cmd]
>
> How is this not in contrib?  This software is useless without the non-free
> service (which is also software, and it is not in main) from Amazon.  Policy
> even mentions as an example for things in contrib: wrapper packages or other
> sorts of free accessories for non-free programs.  That's exactly what this is.

Maybe some off topic here.

The description of s3cmd is outdated. It's *not* useless without AWS.
It can be used with self-hosted S3 protocol compatible service, such
as Ceph RGW, minio[1]. Both are free softwares, and Ceph is in our
main archive.

[1] https://github.com/minio/minio


-- 
Best regards,
Shengjing Zhu

Bug#871406: doc-debian-fr: Update to DocBookXML or drop package

[Osamu Aoki]

Package: doc-debian-fr
Version: 3.1.3.2
Severity: important

Dear QA team,

debiandoc-sgml will be dropped after buster or buster+1.

I am going over packages which uses it.

Normally using debiandoc2dbk in debiandoc-sgml, you can update source to modern
format.  But as I see this package that is not the most important issue.  The
English uses wml to build page.  I don't know exactly now but normally
www.debian.org is translated via PO system.  Or bare wml if the translation was
done long time ago.  This package doesn't track web page contents.

So if you want doc-debian in French or in other language, use the more updated
content from web to build such (probably by fixing and extending doc-debian
itself.)  Then this french page is reliably updated.

This package has been around without fix to bug reported.

Anyway, dropping of debiandoc-sgml will make this package RC buggy.

Since this is not maintained, it's time to drop.

Please consider.

Osamu

Bug#853513: libvigraimpex: ftbfs with GCC-7

[Matthias Klose]

Control: tags -1 + patch

patch at
http://launchpadlibrarian.net/332312910/libvigraimpex_1.10.0+git20160211.167be93+dfsg-2build3_1.10.0+git20160211.167be93+dfsg-2ubuntu1.diff.gz

Bug#871052: Info received (mariadb: [INTL:pt] Updated Portuguese translation for debconf messages)

[Traduz - DebianPT]

Updated correct pt translation (package name and version metadata).

On 07-08-2017 18:24, Debian Bug Tracking System wrote:

Thank you for the additional information you have supplied regarding
this Bug report.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
  Debian MySQL Maintainers 

If you wish to submit further information on this problem, please
send it to 871...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.



--
Best regards,

"Traduz" - Portuguese Translation Team
http://www.DebianPT.org

# Portuguese translation for mysql-dfsg-5.1's debconf messages
# Copyright (C) 2006 Miguel Figueiredo 
# This file is distributed under the same license as the mariadb package.
# Miguel Figueiredo , 2014
# Rui Branco , 2017.
#
msgid ""
msgstr ""
"Project-Id-Version: mariadb-10.1 10.1.25-1\n"
"Report-Msgid-Bugs-To: mariadb-1...@packages.debian.org\n"
"POT-Creation-Date: 2016-04-30 22:44+0300\n"
"PO-Revision-Date: 2017-08-06 10:00+0100\n"
"Last-Translator: Rui Branco \n"
"Language-Team: Portuguese \n"
"Language: pt\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

#. Type: note
#. Description
#: ../mariadb-server-10.1.templates:2001
msgid "The old data directory will be saved at new location"
msgstr "O antigo directório de data será guardado num novo local"

#. Type: note
#. Description
#: ../mariadb-server-10.1.templates:2001
msgid ""
"A file named /var/lib/mysql/debian-*.flag exists on this system. The number "
"indicates a database binary format version that cannot automatically be "
"upgraded (or downgraded)."
msgstr ""
"Já existe um ficheiro /var/lib/mysql/debian-*.flag no sistema. O número "
"indica uma base de dados de formato binário que não pode ser actualizada "
"automaticamente (ou baixar de versão)."

#. Type: note
#. Description
#: ../mariadb-server-10.1.templates:2001
msgid ""
"Therefore the previous data directory will be renamed to /var/lib/mysql-* "
"and a new data directory will be initialized at /var/lib/mysql."
msgstr ""
"Assim o directório de dados anterior será renomeado para /var/lib/mysql-* e "
"um novo directório de dados será inicializado em /var/lib/mysql."

#. Type: note
#. Description
#: ../mariadb-server-10.1.templates:2001
msgid ""
"Please manually export/import your data (e.g. with mysqldump) if needed."
msgstr ""
"Por favor, se necessário, exporte/importe manualmente os seus dados (p.ex. com "
"mysqldump)."

#. Type: note
#. Description
#: ../mariadb-server-10.1.templates:3001
msgid "Important note for NIS/YP users"
msgstr "Nota importante para os utilizadores de NIS/YP"

#. Type: note
#. Description
#: ../mariadb-server-10.1.templates:3001
msgid ""
"Using MariaDB under NIS/YP requires a mysql user account to be added on the "
"local system with:"
msgstr ""
"Utilizar MariaDB com NIS/YP necessita de uma conta de utilizador de mysql "
"para ser acrescentada ao sistema local com:"

#. Type: note
#. Description
#: ../mariadb-server-10.1.templates:3001
msgid ""
"You should also check the permissions and ownership of the /var/lib/mysql "
"directory:"
msgstr ""
"Deve também verificar as permissões e o dono do directório /var/lib/mysql:"

#. Type: boolean
#. Description
#: ../mariadb-server-10.1.templates:4001
msgid "Remove all MariaDB databases?"
msgstr "Remover todas as bases de dados MariaDB?"

#. Type: boolean
#. Description
#: ../mariadb-server-10.1.templates:4001
msgid ""
"The /var/lib/mysql directory which contains the MariaDB databases is about "
"to be removed."
msgstr ""
"O directório /var/lib/mysql que contém as bases de dados MariaDB está "
"prestes a ser removido."

#. Type: boolean
#. Description
#: ../mariadb-server-10.1.templates:4001
msgid ""
"If you're removing the MariaDB package in order to later install a more "
"recent version or if a different mariadb-server package is already using it, "
"the data should be kept."
msgstr ""
"Se está a remover o pacote MariaDB de forma a posteriormente instalar uma "
"versão mais recente ou se um pacote mariadb-server já o está a utilizar, "
"então os dados devem ser mantidos."

Bug#856139: [pkg-go] Bug#856139: certspotter: long description advertises commercial service

[Dr. Bas Wijnen]

On Sun, Aug 06, 2017 at 02:15:17PM +0200, Vincent Bernat wrote:
>  ❦  4 août 2017 20:03 +0200, Jonas Smedegaard  :
> > No, at worst this is misuse of Debian ressources for commercial gain - 
> > i.e. using long description field for advertising a non-free service.
> 
> We have all kind of software advertising non-free services. Search for
> "Google" or "Amazon". The comparison is even unfair as the service
> advertised here is available as free software (not the case for most
> services from Amazon and Google we advertise).

If other packages are worse, that means they should be fixed, not that this
should be allowed.

> Example: [s3cmd]

How is this not in contrib?  This software is useless without the non-free
service (which is also software, and it is not in main) from Amazon.  Policy
even mentions as an example for things in contrib: wrapper packages or other
sorts of free accessories for non-free programs.  That's exactly what this is.

I didn't know that this was in main, and I expect most others to not know
either.  But I don't think they should be.  I wouldn't expect this to be
controversial, but it seems that it is, given that you suggest they obviously
belong in main?

To be clear: the sort of software (of this type) I expect in main is like
mumble: it connects to a server, and you can connect to a commercially hosted
server if you want to, but you can also run your own server, because it's free
software.  If the mumble server would not be free, and the only way to use the
client was to connect to a commercial server, mumble should not be in main.

As I wrote, I expected there to be consensus on this.  Am I incorrect about
that?

Thanks,
Bas


signature.asc
Description: PGP signature

Bug#823373: I have the same issue on a mac

[Ian Gallina]

OSX 10.12.6
Aegisub 3.2.2

The video volume is stuck, can't move it (and it shows as a locked button,
unlike the other two)

Bug#871405: gdm3: russian secondary languaje not displayed if not default

[PICCORO McKAY Lenz]

Package: gdm3
Severity: serious
Tags: l10n
Justification: causes serious data loss

gdm3 has a terribe bug: does not show russian languaje if are
secondary or as alternative

i installed debian 8 from scrach in spanish and then adde russian
languaje locale as second optionaly..

the iso used was DVD flavor with GDM3 as display manager..
NOTE: all the es_XX, ru_XX and en_XX locales where are generated
correctly i mans ALL including ucranian russian UTF8 and non UTF8
locales

then the screen of the GDM3 are showed, only englich and spanish are
availables..

restarted and again try to login and only spanish and russian are availables..

install the lightdm (due now debians only offerts NOTHING display
managers such GMD3 and LIGHTY)

then now russian are available in languaje choices only if lightdm are
set as default

but are not saved for specific users as defaul languje, so all users
if choose another languaje optionally to use, does not saved as user
default.. like DEbian squeeze does perfectly and debian lenny!


-- System Information:
Debian Release: 8.5
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-586
Locale: LANG=es_VE.UTF-8, LC_CTYPE=es_VE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)


Versions of packages gdm3 depends on:
ii  accountsservice0.6.37-3+b1
ii  adduser3.113+nmu3
ii  dconf-cli  0.22.0-1
ii  dconf-gsettings-backend0.22.0-1
ii  debconf [debconf-2.0]  1.5.56
ii  gir1.2-gdm33.14.1-6
ii  gnome-session [x-session-manager]  3.14.0-2
ii  gnome-session-bin  3.14.0-2
ii  gnome-settings-daemon  3.14.2-3
ii  gnome-shell3.14.2-3+b1
ii  gnome-terminal [x-terminal-emulator]   3.14.1-1
ii  gsettings-desktop-schemas  3.14.1-1
ii  kde-window-manager [x-window-manager]  4:4.11.13-2
ii  libaccountsservice00.6.37-3+b1
ii  libaudit1  1:2.4-1+b1
ii  libc6  2.19-17
ii  libcanberra-gtk3-0 0.30-2.1
ii  libcanberra0   0.30-2.1
ii  libgdk-pixbuf2.0-0 2.31.1-2+b1
ii  libgdm13.14.1-6
ii  libglib2.0-0   2.42.1-1
ii  libglib2.0-bin 2.42.1-1
ii  libgtk-3-0 3.14.5-1
ii  libpam-modules 1.1.8-3.1
ii  libpam-runtime 1.1.8-3.1
ii  libpam-systemd 215-14
ii  libpam0g   1.1.8-3.1
ii  librsvg2-common2.40.5-1
ii  libselinux12.3-2
ii  libsystemd0215-14
ii  libwrap0   7.6.q-25
ii  libx11-6   2:1.6.2-3
ii  libxau61:1.0.8-1
ii  libxdmcp6  1:1.1.1-1+b1
ii  libxrandr2 2:1.4.2-1+b1
ii  lsb-base   4.1+Debian13+nmu1
ii  metacity [x-window-manager]1:3.14.3-1
ii  mutter [x-window-manager]  3.14.2-1
ii  policykit-10.105-8
ii  ucf3.0030
ii  x11-common 1:7.7+7
ii  x11-xserver-utils  7.7+3+b1
ii  xterm [x-terminal-emulator]312-2

Versions of packages gdm3 recommends:
ii  at-spi2-core   2.14.0-1
ii  desktop-base   8.0.2
ii  gnome-icon-theme   3.12.0-1
ii  gnome-icon-theme-symbolic  3.12.0-1
ii  x11-xkb-utils  7.7+1
ii  xserver-xephyr 2:1.16.4-1
ii  xserver-xorg   1:7.7+7
ii  zenity 3.14.0-1

Versions of packages gdm3 suggests:
ii  gnome-orca3.14.0-4
ii  libpam-gnome-keyring  3.14.0-1+b1

-- Configuration Files:
/etc/gdm3/daemon.conf changed [not included]

-- debconf information:
  gdm3/daemon_name: /usr/sbin/gdm3
* shared/default-x-display-manager: kdm


Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com

Bug#732445: debian-policy should encourage verification of upstream cryptographic signaturse

[Holger Levsen]

On Mon, Aug 07, 2017 at 09:40:22AM -0700, Russ Allbery wrote:
> In an ideal world, we would have a documented set of metadata for finding
> upstream releases, of which uscan is just one implementation, and document
> that in Policy.  This patch doesn't attempt to do that; it tries to find a
> compromise between the current Policy language ("include a watch file for
> uscan") and specifying the location of the upstream signing keys, while
> deferring all of the details to the uscan documentation.
> 
> I decided to keep this all in the uscan section rather than adding a new
> section for the upstream signing key location, since right now this is all
> closely linked to uscan functionality (and to avoid renumbering sections
> or having a section weirdly separated from the uscan description).
> 
> How does this look to everyone?
 
looks good to me and the reasoning as well. happy to second if you think it's
ready.

thanks!


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#870874: support sound on ltsp clients with pulseaudio

[Holger Levsen]

On Mon, Aug 07, 2017 at 07:36:34PM +0200, Petter Reinholdtsen wrote:
> > Also: should we remove gtick now from education-music?
> If there is a better digital metronome available, I see no reason to
> cling to gtick.  I've been looking for one my self to use with my kids
> music education, so please let me know which program is better at this
> task.

right, it also makes sense to keep it even if it wouldnt work for LTSP thin 
clients but only for workstations.

(but you should maybe pick up its maintenance if you want to ensure it
stays in Debian, it's currently orphaned.)


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#870796: [Dev-luatex] [tex-live] segfault on build-testing luatex

[luigi scarso]

On Mon, Aug 7, 2017 at 4:17 PM, Norbert Preining  wrote:
>> Related to gcc-7.1?
>> http://tug.org/pipermail/tex-live/2017-June/040192.html
>
> Ahh, sounds reasonable .



OK I see it with gcc 7.1 and -O3 , but not with -O0

It happens when luatex exits and closes the state L;
the garbage collector calls the pending finalizers and luaffi fails.
I am working on the luaffi code,  it could be that will aply the patch.


(gdb) fr 1
#1  check_cdata (L=L@entry=0x30e8b90, idx=idx@entry=1,
ct=ct@entry=0x7fff8b5aed30) at
../../../source/texk/web2c/luatexdir/luaffi/ctype.c:266
266void* p = to_cdata(L, idx, ct);
(gdb) fr 2
#2  0x006845d5 in cdata_gc (L=0x30e8b90) at
../../../source/texk/web2c/luatexdir/luaffi/ffi.c:1429
1429check_cdata(L, 1, );
(gdb) fr 3
#3  0x006a9ea8 in luaD_precall (L=L@entry=0x30e8b90,
func=, nresults=0) at
../../../source/libs/lua52/lua52-src/src/ldo.c:319
319  n = (*f)(L);  /* do the actual call */
(gdb) fr 4
#4  0x006aa582 in luaD_call (L=0x30e8b90, func=, nResults=, allowyield=) at
../../../source/libs/lua52/lua52-src/src/ldo.c:401
401  if (!luaD_precall(L, func, nResults))  /* is a Lua function? */
(gdb) fr 5
#5  0x006a9599 in luaD_rawrunprotected (L=0x30e8b90,
f=0x6abc30 , ud=0x0) at
../../../source/libs/lua52/lua52-src/src/ldo.c:131
131  LUAI_TRY(L, ,
(gdb) fr 6
#6  0x006aa933 in luaD_pcall (L=L@entry=0x30e8b90,
func=func@entry=0x6abc30 , u=u@entry=0x0, old_top=896,
ef=ef@entry=0) at ../../../source/libs/lua52/lua52-src/src/ldo.c:603
603  status = luaD_rawrunprotected(L, func, u);
(gdb) fr 7
#7  0x006ad750 in GCTM (propagateerrors=0, L=0x30e8b90) at
../../../source/libs/lua52/lua52-src/src/lgc.c:824
824status = luaD_pcall(L, dothecall, NULL, savestack(L, L->top - 2), 0);
(gdb) fr 8
#8  callallpendingfinalizers (propagateerrors=,
L=) at
../../../source/libs/lua52/lua52-src/src/lgc.c:978
978GCTM(L, propagateerrors);
(gdb) fr 9
#9  luaC_freeallobjects (L=L@entry=0x30e8b90) at
../../../source/libs/lua52/lua52-src/src/lgc.c:988
988  callallpendingfinalizers(L, 0);
(gdb) fr 10
#10 0x006b7677 in close_state (L=0x30e8b90) at
../../../source/libs/lua52/lua52-src/src/lstate.c:226
226  luaC_freeallobjects(L);  /* collect all objects */
(gdb) fr 11
#11 lua_close (L=0x30e8b90) at
../../../source/libs/lua52/lua52-src/src/lstate.c:320
320  close_state(L);
(gdb) fr  12
#12 0x00476ff6 in do_final_end () at
../../../source/texk/web2c/luatexdir/tex/errors.w:223
223lua_close(Luas); /* new per 0.99 */
(gdb) fr 13
#13 0x00447abe in main (ac=, av=) at ../../../source/texk/web2c/luatexdir/luatex.c:582
582main_body();

-- 
luigi

Bug#870073: [Pkg-mozext-maintainers] Bug#870073: enigmail: Does not encrypt and gives alerts after upgrade to Thunderbird 52

[Paul van der Vlis]

Hello Daniel,

Op 07-08-17 om 18:57 schreef Daniel Kahn Gillmor:
> Control: retitle 870073 enigmail: [jessie only] enigmail needs access to a 
> running gpg-agent
> 
> On Sun 2017-08-06 16:16:18 +0200, Paul van der Vlis wrote:
>> Op 31-07-17 om 23:38 schreef Daniel Kahn Gillmor:
>>> I haven't seen this message at all.  are you certain that gpg-agent is
>>> running?
>>
>> I don't see it when I using "ps aux".
> 
> ok, this is an issue that is specific to debian jessie only.  on stretch
> and later, the gpg-agent has an autolaunch mechanism that avoids these
> problems entirely.

Aha.

>>> Do you ever see a dialog box that prompts you for your gpg
>>> password?
>>
>> When I first use Enigmail I am asked for a password. After that, I can
>> use Enigmail without any question about a password (I don't like this
>> behaviour. But I don't know how to turn it off).
> 
> It sounds like enigmail is auto-launching an agent during key
> generation, and using it for the rest of the session.  I'd imagine if
> you "killall gpg-agent" after key creation you will find that enigmail
> no longer works.

I have not created a keypair, I have an excisting keypair what I use.

> enigmail 1.9.8.1 expects gpg to use a gpg agent process.  It does not
> prompt the user for a passphrase during normal use.

Aha.

>>> Can you try adding "use-agent" to your ~/.gnupg/gpg.conf  and then
>>> logging out and logging back in again?
>>
>> Yes, the behaviour is still there when I use "use-agent" in
>> ~/.gnupg/gpg.conf and logout and login again.
>>
>> But then I see gpg-agent running with "ps aux".
> 
> this is strange.  what do the following commands show when you've logged
> in with "use-agent" running?
> 
> 
>  echo $GPG_AGENT_INFO

/run/user/1000/keyring/gpg:0:1

>  gpg-connect-agent 'getinfo socket_name' /bye

ERR 280 not implemented

>> The following tests are without "use-agent" in my gpg.conf.
> 
> you should put use-agent in gpg.conf if you want to use enigmail 

I've done that now, but it does not work OK.

> -- or
> you should upgrade to stretch where it is on by default. :)

I would like to find out this problem first.

>>> As a workaround, please also try closing thunderbird and then
>>> re-launching it with the following command:
>>>
>>> gpg-agent --daemon thunderbird
>>>
>>> Does that cause the error message to go away?
>>
>> Now, I get another dialog window asking me for the password. It has
>> "pinentry" in the title.
>> I don't get an error anymore while decrypting.
>> Encryption seems to be OK, and asks again for a password.
>>
>> So this looks-like OK, but different as normal.
> 
> this is a workaround for you not having "use-agent" in your gpg.conf.

I think it's also a workarround for the Gnome-keyring-hijaking...

>> Maybe this is interesting:
>> gpg: WARNING: The GNOME keyring manager hijacked the GnuPG agent.
>> gpg: WARNING: GnuPG will not work properly - please configure that tool
>> to not interfere with the GnuPG system!
>>
>> I am using Cinnamon as my desktop-environment, and GDM3 as display manager.
> 
> please see:
> 
>https://wiki.gnupg.org/GnomeKeyring

I did now as root:
dpkg-divert --local --rename --divert \
  /etc/xdg/autostart/gnome-keyring-gpg.desktop-disable \
  --add /etc/xdg/autostart/gnome-keyring-gpg.desktop

And I logged out and in again. Now I can use Enigmail, but it works not
really nice. Before I could turn-on encrypting and signing using the
menu. Now it says default "encrypt (auto)" and it's not clear if it's
encrypting or not. If I click on it, it says "encrypt" without "(auto)"
and then it works, but I cannot turn it off anymore using the menu. But
maybe this is new and normal.

> for information about gnome-keyring and gpg-agent.  modern versions of
> gnome-keyring and gpg-agent play nicer together.
> 
>> 2017-08-06 16:00:06.149 [DEBUG] enigmail.js: detectGpgAgent: 
>> GPG_AGENT_INFO='/run/user/1000/keyring/gpg:0:1'
> 
> This is very surprising to me, especially for gpg-agent 2.0.26.  I don't
> think that version of gpg-agent used /run/user -- i would expect it
> instead to use something like /tmp/gpg-1uGi7D/S.gpg-agent:679:1
> 
> where is this value coming from?  have you modified any config files, or
> tried to mix packages across versions of the distro?

No, my installation is "clean". I don't do strange things on this
production machine. But maybe I have copied my ~/.gnupg directory from
my old computer and are there now other defaults.

> I'm still not able to reproduce the specific behavior you describe,
> unfortunately.

Maybe this is interesting for you:
---
paul@laptopp:~$ echo $GPG_AGENT_INFO
/tmp/gpg-ti0k4C/S.gpg-agent:10207:1
paul@laptopp:~$
paul@laptopp:~$ gpg-connect-agent 'getinfo socket_name' /bye
D /tmp/gpg-ti0k4C/S.gpg-agent
OK
paul@laptopp:~$
--

This is after the "dpkg-divert" command.

So I think what other people with this probleme have to do is:
-
echo "use-agent" >> ~/.gnupg/gpg.conf

sudo dpkg-divert --local --rename --divert \
  

Bug#871404: openbox-menu FTCBFS: uses the build architecture pkg-config

[Helmut Grohne]

Source: openbox-menu
Version: 0.8.0-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

openbox-menu fails to cross build from source, because it fails finding
packages with the build architecture pkg-config. It also calls the build
architecture strip, which not only breaks cross compilation, but also
-dbgsym packages. After fixing both, openbox-menu cross builds a -dbgsym
package successfully.

Helmut
diff --minimal -Nru openbox-menu-0.8.0/debian/changelog 
openbox-menu-0.8.0/debian/changelog
--- openbox-menu-0.8.0/debian/changelog 2016-03-03 11:54:19.0 +0100
+++ openbox-menu-0.8.0/debian/changelog 2017-08-07 19:37:41.0 +0200
@@ -1,3 +1,12 @@
+openbox-menu (0.8.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ Make pkg-config substitutable.
++ Do not strip during install.
+
+ -- Helmut Grohne   Mon, 07 Aug 2017 19:37:41 +0200
+
 openbox-menu (0.8.0-1) unstable; urgency=medium
 
   * New upstream release. (Closes: #797016, #797022, #797241)
diff --minimal -Nru openbox-menu-0.8.0/debian/patches/debian_build.patch 
openbox-menu-0.8.0/debian/patches/debian_build.patch
--- openbox-menu-0.8.0/debian/patches/debian_build.patch2015-11-30 
18:05:21.0 +0100
+++ openbox-menu-0.8.0/debian/patches/debian_build.patch2017-08-07 
19:37:41.0 +0200
@@ -1,10 +1,19 @@
 Description: Make makefile compatible with Debian's standards.
 Author: Mateusz Łukasik 
-Last-Update: 2013-11-30
+Last-Update: 2017-08-07
 
 --- a/Makefile
 +++ b/Makefile
-@@ -7,7 +7,7 @@ CC=gcc
+@@ -1,5 +1,6 @@
+-LIBS= `pkg-config --libs glib-2.0 gtk+-2.0 libmenu-cache`
+-CFLAGS+= -g -Wall `pkg-config --cflags glib-2.0 gtk+-2.0 libmenu-cache`
++PKG_CONFIG ?= pkg-config
++LIBS= `$(PKG_CONFIG) --libs glib-2.0 gtk+-2.0 libmenu-cache`
++CFLAGS+= -g -Wall `$(PKG_CONFIG) --cflags glib-2.0 gtk+-2.0 libmenu-cache`
+ CC=gcc
+ #-DG_DISABLE_DEPRECATED
+ 
+@@ -7,7 +8,7 @@
  CFLAGS+=-DWITH_ICONS
  # Uncomment this line if Openbox can display SVG icons 
  # Check SVG support with '$ ldd /usr/bin/openbox | grep svg', librsvg must 
appear..
@@ -13,3 +24,11 @@
  
  prefix= /usr/local
  DESTDIR ?= $(prefix)
+@@ -31,7 +32,6 @@
+   @rm -rf doc
+ 
+ install:
+-  @strip -s openbox-menu
+   @install -Dm 755 openbox-menu $(BINDIR)/openbox-menu
+ 
+ doc:

Bug#871279: libdolfin2016.2: requires rebuild against GCC 7 and symbols/shlibs bump

[Mattia Rizzolo]

On Mon, 7 Aug 2017, 6:57 p.m. Drew Parsons,  wrote:

> > - If your package is about to be renamed due to an upstream SONAME
> bump,
> >   you do not need to add any special symbols handling.
> >
>
>
> dolfin 2017.1 is in the NEW queue, so that upgrade will handle this
> bug.
>

Is the binary you uploaded built with gcc-7?  Otherwise that would not fix
this bug.

Bug#871052: mariadb: [INTL:pt] Updated Portuguese translation for debconf messages

[Mattia Rizzolo]

Indeed, but in Debian the version separator between package name and
version is _ not - :)
Hence it should have been
Package: mariadb-10.1
Version: 10.1.25-1
;)

On Mon, 7 Aug 2017, 7:17 p.m. Traduz - DebianPT, 
wrote:

> Hi Mattia,
>
> Got file from
>
> https://i18n.debian.org/material/po/unstable/main/m/mariadb-10.1/debian/po/mariadb-10.1_10.1.25-1_pt.po.gz
> .
>
> It's the last version the site shows has outdated translation.
>
> On 06-08-2017 22:30, Mattia Rizzolo wrote:
> > Control: reassign -1 src:mariadb-10.1 10.1.25-1
> >
> > On Sun, Aug 06, 2017 at 10:06:44PM +0100, Traduz - DebianPT wrote:
> >> Package: mariadb
> >> Version: 10.1_10.1.25-1
> > please be more precise about the metadata… neither package name nor
> > version were right…
> >
> >> Updated Portuguese translation for mariadb's debconf messages.
> >> Feel free to use it.
> >>
> >> For translation updates please contact 'Last Translator' or the
> >> Portuguese Translation Team .
> Cheers,
> Rui Branco
>
> --
>
> "Traduz" - Portuguese Translation Team
> http://www.DebianPT.org
>
>

Bug#869705: debmirror: dists/wheezy-proposed-updates/Release fails gpg validation

[Martin Dorey]

tags 869705 fixed
stop

The last record I have of these errors was 2017-07-30.  The times on the 
Release and Release.gpg files at 
http://ftp.debian.org/debian/dists/wheezy-proposed-updates/ are now the same.  
Sorry for the noise.

Bug#870874: support sound on ltsp clients with pulseaudio

[Petter Reinholdtsen]

[Holger Levsen]
> Also: should we remove gtick now from education-music?

If there is a better digital metronome available, I see no reason to
cling to gtick.  I've been looking for one my self to use with my kids
music education, so please let me know which program is better at this
task.

-- 
Happy hacking
Petter Reinholdtsen

Bug#869745: enigmail: Enigmail stopped working after the update on Debian Jessie

[Daniel Bareiro]

El lunes 07 de agosto del 2017 a las 13:03:41 -0400,
Daniel Kahn Gillmor escribió:

> > Please mark as duplicate with #869774.
> >
> > This issue has already been solved in that other bug report.

> sorry to hear you had trouble.  hopefully the other report provided the
> information you needed.
> 
> Regards,

Hi, Daniel.

Yes. It did it! Thanks!


Kind regards,

-- 
Ing. Daniel Bareiro

Opción Libre - Soberanía tecnológica para su empresa
WWW: http://www.opcion-libre.com.ar
Tel: +54 11 5235-3090
Correo-e: conta...@opcion-libre.com.ar


signature.asc
Description: Digital signature

Bug#871402: ddclient: [INTL:pt] Updated Portuguese translation for debconf messages

[Traduz - DebianPT]

Package: ddclient
Version: 3.8.3-1.1
Tags: l10n, patch
Severity: wishlist

Updated Portuguese translation for ddclient's debconf messages.
Feel free to use it.

For translation updates please contact 'Last Translator' or the
Portuguese Translation Team .
--
Best regards,

"Traduz" - Portuguese Translation Team
http://www.DebianPT.org










# Portuguese translation of ddclient debconf messages.
# This file is distributed under the same license as the ddclient package.
# Ricardo Silva , 2006.
# Miguel Figueiredo , 2009, 2010.
# Rui Branco - DebianPT , 2017.
msgid ""
msgstr ""
"Project-Id-Version: ddclient 3.8.3-1.1\n"
"Report-Msgid-Bugs-To: ddcli...@packages.debian.org\n"
"POT-Creation-Date: 2014-01-16 00:49+0100\n"
"PO-Revision-Date: 2017-08-05 16:19+\n"
"Last-Translator: Rui Branco - DebianPT \n"
"Language-Team: Portuguese \n"
"Language: pt\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

#. Type: select
#. Choices
#: ../ddclient.templates:2001
msgid "other"
msgstr "outro"

#. Type: select
#. Description
#: ../ddclient.templates:2002
msgid "Dynamic DNS service provider:"
msgstr "Provedor do serviço de DNS dinâmico:"

#. Type: select
#. Description
#: ../ddclient.templates:2002
msgid ""
"Please select the dynamic DNS service you are using. If the service you use "
"is not listed, choose \"other\" and you will be asked for the protocol and "
"the server name."
msgstr ""
"Por favor escolha o serviço de DNS dinâmico que está a usar. Se o serviço "
"que utiliza não está listado, escolha \"outro\" e ser-lhe-á perguntado pelo "
"protocolo e pelo nome do servidor."

#. Type: string
#. Description
#: ../ddclient.templates:3001
msgid "Dynamic DNS server:"
msgstr "Servidor de DNS dinâmico:"

#. Type: string
#. Description
#: ../ddclient.templates:3001
msgid ""
"Please enter the name of the server which is providing you with dynamic DNS "
"service (example: members.dyndns.org)."
msgstr ""
"Por favor introduza o nome do servidor que lhe disponibiliza o serviço de "
"DNS dinâmico (exemplo: members.dyndns.org)."

#. Type: select
#. Description
#: ../ddclient.templates:4001
msgid "Dynamic DNS update protocol:"
msgstr "Protocolo de actualização do DNS dinâmico:"

#. Type: select
#. Description
#: ../ddclient.templates:4001
msgid ""
"Please select the dynamic DNS update protocol used by your dynamic DNS "
"service provider."
msgstr ""
"Por favor escolha o protocolo de actualização de DNS dinâmico usado pelo seu "
"provedor do serviço de DNS dinâmico."

#. Type: string
#. Description
#: ../ddclient.templates:5001
msgid "DynDNS fully qualified domain names:"
msgstr "Nomes de domínio qualificados DynDNS:"

#. Type: string
#. Description
#: ../ddclient.templates:5001
msgid ""
"Please enter the list of fully qualified domain names for the local host(s) "
"(for instance, \"myname.dyndns.org\" with only one host or \"myname1.dyndns."
"org,myname2.dyndns.org\" for two hosts)."
msgstr ""
"Por favor introduza a lista de domínios de nome qualificado para a(s) "
"máquina(s) (por exemplo \"meu_nome.dyndns.org\" se tiver apenas uma máquina "
"ou \"meu_nome1.dyndns.org,meu_nome2.dyndns.org\" para duas máquinas)."

#. Type: string
#. Description
#: ../ddclient.templates:6001
msgid "Username for dynamic DNS service:"
msgstr "Nome de utilizador para o serviço de DNS dinâmico:"

#. Type: string
#. Description
#: ../ddclient.templates:6001
msgid "Please enter the username to use with the dynamic DNS service."
msgstr ""
"Por favor introduza o nome de utilizador a utilizar com o serviço de DNS "
"dinâmico."

#. Type: password
#. Description
#: ../ddclient.templates:7001
msgid "Password for dynamic DNS service:"
msgstr "Palavra-passe para o serviço de DNS dinâmico:"

#. Type: password
#. Description
#: ../ddclient.templates:7001
msgid "Please enter the password to use with the dynamic DNS service."
msgstr ""
"Por favor introduza a palavra-passe que utiliza para se ligar ao serviço de "
"DNS dinâmico."

#. Type: password
#. Description
#: ../ddclient.templates:8001
msgid "Re-enter password to verify:"
msgstr "Reintroduza a palavra-chave para verificação:"

#. Type: password
#. Description
#: ../ddclient.templates:8001
msgid ""
"Please enter your dynamic DNS service password again to make sure you typed "
"it correctly."
msgstr ""
"Por favor introduza novamente a sua palavra-passe do serviço DNS dinâmico"
" para "
"verificar que a digitou correctamente."

#. Type: error
#. Description
#: ../ddclient.templates:9001
msgid "Passwords do not match"
msgstr "As palavras chaves não coincidem"

#. Type: error
#. Description
#: ../ddclient.templates:9001
msgid "The two passwords you entered were not the same. Please try again."
msgstr ""
"As duas palavras-passe que inseriu não são iguais. Por favor tente de 

Bug#871403: RM: clamav/experimental -- NVIU; lower version in unstable

[Sebastian Andrzej Siewior]

Package: ftp.debian.org
Severity: normal

The experimental suite for clamav has 0.99.3~snapshot20170704+dfsg-1 and
unstable 0.99.3~beta1+dfsg-1 and this makes the unstable version appear
to be lower than the version in experimental.
Therefore I am asking for its removal from experimental.

The difference (source code wise) isn't that big / relevant (between exp
and unstable). Which means if you are not comfortable with the removal,
we could just wait until the final 0.99.3 appears and the exp version
gets removed on its own by the auto-decrufter.

Sebastian

Bug#871401: debian-i18n: russian-spanish cant change in display manager

[PICCORO McKAY Lenz]

Package: debian-i18n
Severity: grave
Tags: l10n
Justification: causes non-serious data loss

Dear Maintainer,

Install debian in spanish and added optionally russian and english as
alternate languajes..
When try to access in GDM3 login screen, only Spanish and english are available
NOTE: all the es_XX, ru_XX and en_XX locales where are generated correctly

I Regenerate all the locales again, and remove the stupid gnome-puach dm
install the lightdm (due now debians only offerts nothing about
display managers)
then now russian are available in languaje choices
but are not saved for specific users as defaul languje
and if does not choose for fist time, next time are not set correctly

In resume:

1) the stupid GDM3 does not offer russian languaje option if spanish are default
2) lightdm offers russian laguaje option but are not saved for users
that choose it
3) if user forgot to use russian, when logout and choose it, no
russian are showed
4) if spanish are default or english, missing russian entries are in desktop
5) only gonmepuach desktop use complete russian translations, Xfce4
and LXDE does not .
6) russian translations appears only when are set by default, and then
spanish are missing


-- System Information:
Debian Release: 8.5
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-586
Locale: LANG=es_VE.UTF-8, LC_CTYPE=es_VE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)



Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com

Bug#871389: altree: FTBFS: build-dependency not installable: libmath-tamuanova-perl

[Niko Tyni]

On Mon, Aug 07, 2017 at 06:46:25PM +0200, Andreas Tille wrote:
 
> I wonder whether something might be wrong with the apt cache, since
> I can not find any sign that libmath-tamuanova-perl would be missing.

It's not missing but it's uninstallable in sid together with the other
build dependencies, specifically libgsl-dev.

  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  
  The following packages have unmet dependencies:
   libgsl-dev : Depends: libgsl23 (= 2.4+dfsg-4) but it is not going to be 
installed
Depends: libgslcblas0 (= 2.4+dfsg-4) but it is not going to be 
installed
  E: Unable to correct problems, you have held broken packages.
 
This is due to gsl breakage/uncoordinated transition, see #869778 .
-- 
Niko Tyni   nt...@debain.org

Bug#871400: courier: [INTL:pt] Updated Portuguese translation for debconf messages

[Traduz - DebianPT]

Package: courier
Version: 0.76.3-5
Tags: l10n, patch
Severity: wishlist

Updated Portuguese translation for courier's debconf messages.
Feel free to use it.

For translation updates please contact 'Last Translator' or the
Portuguese Translation Team .
--
Best regards,

"Traduz" - Portuguese Translation Team
http://www.DebianPT.org










# Portuguese translation of courier's debconf messages.
# 2005, Miguel Figueiredo 
# 30-10-2005 - Miguel Figueiredo  - initial translation
# Miguel Figueiredo , 2005-2008
# Rui Branco , 2017.
#
msgid ""
msgstr ""
"Project-Id-Version: courier 0.76.3-5\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2017-05-09 14:26+\n"
"PO-Revision-Date: 2017-08-05 15:55+0100\n"
"Last-Translator: Rui Branco \n"
"Language-Team: Portuguese \n"
"Language: pt\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
"X-Generator: Gtranslator 2.91.7\n"

#. Type: boolean
#. Description
#: ../courier-base.templates:2001
msgid "Create directories for web-based administration?"
msgstr "Criar os directórios para administração via web?"

#. Type: boolean
#. Description
#: ../courier-base.templates:2001
msgid ""
"Courier uses several configuration files in /etc/courier. Some of these "
"files can be replaced by a subdirectory whose contents are concatenated and "
"treated as a single, consolidated, configuration file."
msgstr ""
"O courier utiliza vários ficheiros de configuração que estão em /etc/"
"courier. Alguns desses ficheiros de configuração podem ser substituídos por "
"um subdirectório cujo conteúdo é concatenado e tratado como um único "
"ficheiro de configuração."

#. Type: boolean
#. Description
#: ../courier-base.templates:2001
msgid ""
"The web-based administration provided by the courier-webadmin package relies "
"on configuration directories instead of configuration files.  If you agree, "
"any directories needed for the web-based administration tool will be created "
"unless there is already a plain file in place."
msgstr ""
"A administração via web disponibilizada pelo pacote courier-webmin baseia-se "
"em directórios de configuração em vez de ficheiros de configuração.  Se "
"concordar, serão criados quaisquer directórios necessários para a ferramenta "
"de administração via web a menos que já exista no local um ficheiro simples."

#. Type: string
#. Description
#: ../courier-base.templates:3001
msgid "Path to Maildir directory:"
msgstr "Caminho para o directório Maildir:"

#. Type: string
#. Description
#: ../courier-base.templates:3001
msgid ""
"Please give the relative path name from each user's home directory to the "
"Maildir directory where the Courier servers store and access the user's "
"email. Please refer to the maildir.courier(5) manual page if you are "
"unfamiliar with the mail storage format used by Courier."
msgstr ""
"Por favor indique o caminho relativo a partir do directório 'home' de cada "
"utilizador para o directório Maildir onde os servidores Courier guardam e "
"acedem ao email do utilizador. Por favor veja a página maildir.courier(5) do "
"manual se não estiver familiarizado com o formato de armazenamento de mail "
"utilizado pelo Courier."

#. Type: note
#. Description
#: ../courier-base.templates:4001
msgid "Obsolete setting of MAILDIR"
msgstr "Definição obsoleta de MAILDIR"

#. Type: note
#. Description
#: ../courier-base.templates:4001
msgid ""
"The name of the Maildir directory is now recognized through the variable "
"MAILDIRPATH in Courier configuration files. The MAILDIR setting in /etc/"
"default/courier is therefore obsolete and will be not recognized."
msgstr ""
"O nome do directório Maildir é agora reconhecido através da variável "
"MAILDIRPATH nos ficheiros de configuração do Courier. Por isso a definição "
"MAILDIR em /etc/default/courier é por isso obsoleta e não será reconhecida."

#. Type: note
#. Description
#: ../courier-base.templates:5001
msgid "SSL certificate required"
msgstr "É necessário um certificado SSL"

#. Type: note
#. Description
#: ../courier-base.templates:5001
msgid ""
"POP and IMAP over SSL requires a valid, signed, X.509 certificate. During "
"the installation of courier-pop or courier-imap, a self-signed X.509 "
"certificate will be generated if necessary."
msgstr ""
"POP e IMAP sobre SSL necessitam de um certificado X.509 válido e assinado. "
"Durante a instalação de courier-pop ou do courier-imap, se necessário, irá "
"ser gerado um certificado X.509 auto-assinado."

#. Type: note
#. Description
#: ../courier-base.templates:5001
msgid ""
"For production use, the X.509 certificate must be signed by a recognized "
"certificate authority, in order for mail clients to accept the certificate. "
"The default location for this certificate is 

Bug#870874: support sound on ltsp clients with pulseaudio

[Holger Levsen]

On Sun, Aug 06, 2017 at 10:45:25PM +0200, Wolfgang Schweer wrote:
> I guess this bug has been filed after the removal of the dependency on
> pulseaudio-esound-compat.

yup
 
> IMO the remaining cleanup things still to do are:
> 
> (1) drop /usr/share/debian-edu-config/tools/debian-edu-ltsp-audiodivert 
> because gtick (metronome) is the only program listed but doesn't 
> need to be diverted as /dev/dsp isn't used anymore.
> 
> (2) remove the line containing ESPEAKER in 
> /etc/desktop-profiles/debian-edu-config.listing

thanks for this list, done in git now, please review. (Especially the part
about removing the diverts…)

Also: should we remove gtick now from education-music?


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#871257: kexi: new release

[Pino Toscano]

tag 871257 + pending
thanks

In data lunedì 7 agosto 2017 12:59:15 CEST, Christian Buhtz ha scritto:
> Package: kexi
> Version: 1:2.9.11+dfsg-4+b1
> Severity: normal
> 
> Dear Maintainer,
> 
> the current 2.9.11 version in sid is far away from being usable and it is
> outdated/old.

Outdated ok, but if it's buggy then please say which actual issues
there are (since they might affect stable, for example).

Anyway, it is already worked on (by me), see
https://ftp-master.debian.org/new/kexi_1:3.0.1.1-1.html
(sadly, Debian bureaucracy at its finest blocks it in the NEW queue...)

> Kernel: Linux 4.12.4-towo.1-siduction-amd64 (SMP w/4 CPU cores; PREEMPT)

Please note that bugs.debian.org tracks bug for Debian only, not for
derivatives.  In this specific case the version is old in Debian as
well, but otherwise it would invalidate the bug. FYI.

-- 
Pino Toscano

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

Bug#871052: mariadb: [INTL:pt] Updated Portuguese translation for debconf messages

[Traduz - DebianPT]

Package: mariadb
Version: 10.1_10.1.25-1
Tags: l10n, patch
Severity: wishlist


Updated Portuguese translation for mariadb's debconf messages.
Feel free to use it.

Minor corrections.
Got po-debconf from 
https://i18n.debian.org/material/po/unstable/main/m/mariadb-10.1/debian/po/mariadb-10.1_10.1.25-1_pt.po.gz 



For translation updates please contact 'Last Translator' or the
Portuguese Translation Team .
--
Best regards,

"Traduz" - Portuguese Translation Team
http://www.DebianPT.org












# Portuguese translation for mysql-dfsg-5.1's debconf messages
# Copyright (C) 2006 Miguel Figueiredo 
# This file is distributed under the same license as the mariadb package.
# Miguel Figueiredo , 2014
# Rui Branco , 2017.
#
msgid ""
msgstr ""
"Project-Id-Version: mariadb 10.1_10.1.25-1\n"
"Report-Msgid-Bugs-To: mariadb-1...@packages.debian.org\n"
"POT-Creation-Date: 2016-04-30 22:44+0300\n"
"PO-Revision-Date: 2017-08-06 10:00+0100\n"
"Last-Translator: Rui Branco \n"
"Language-Team: Portuguese \n"
"Language: pt\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

#. Type: note
#. Description
#: ../mariadb-server-10.1.templates:2001
msgid "The old data directory will be saved at new location"
msgstr "O antigo directório de data será guardado num novo local"

#. Type: note
#. Description
#: ../mariadb-server-10.1.templates:2001
msgid ""
"A file named /var/lib/mysql/debian-*.flag exists on this system. The number "
"indicates a database binary format version that cannot automatically be "
"upgraded (or downgraded)."
msgstr ""
"Já existe um ficheiro /var/lib/mysql/debian-*.flag no sistema. O número "
"indica uma base de dados de formato binário que não pode ser actualizada "
"automaticamente (ou baixar de versão)."

#. Type: note
#. Description
#: ../mariadb-server-10.1.templates:2001
msgid ""
"Therefore the previous data directory will be renamed to /var/lib/mysql-* "
"and a new data directory will be initialized at /var/lib/mysql."
msgstr ""
"Assim o directório de dados anterior será renomeado para /var/lib/mysql-* e "
"um novo directório de dados será inicializado em /var/lib/mysql."

#. Type: note
#. Description
#: ../mariadb-server-10.1.templates:2001
msgid ""
"Please manually export/import your data (e.g. with mysqldump) if needed."
msgstr ""
"Por favor, se necessário, exporte/importe manualmente os seus dados (p.ex. com "
"mysqldump)."

#. Type: note
#. Description
#: ../mariadb-server-10.1.templates:3001
msgid "Important note for NIS/YP users"
msgstr "Nota importante para os utilizadores de NIS/YP"

#. Type: note
#. Description
#: ../mariadb-server-10.1.templates:3001
msgid ""
"Using MariaDB under NIS/YP requires a mysql user account to be added on the "
"local system with:"
msgstr ""
"Utilizar MariaDB com NIS/YP necessita de uma conta de utilizador de mysql "
"para ser acrescentada ao sistema local com:"

#. Type: note
#. Description
#: ../mariadb-server-10.1.templates:3001
msgid ""
"You should also check the permissions and ownership of the /var/lib/mysql "
"directory:"
msgstr ""
"Deve também verificar as permissões e o dono do directório /var/lib/mysql:"

#. Type: boolean
#. Description
#: ../mariadb-server-10.1.templates:4001
msgid "Remove all MariaDB databases?"
msgstr "Remover todas as bases de dados MariaDB?"

#. Type: boolean
#. Description
#: ../mariadb-server-10.1.templates:4001
msgid ""
"The /var/lib/mysql directory which contains the MariaDB databases is about "
"to be removed."
msgstr ""
"O directório /var/lib/mysql que contém as bases de dados MariaDB está "
"prestes a ser removido."

#. Type: boolean
#. Description
#: ../mariadb-server-10.1.templates:4001
msgid ""
"If you're removing the MariaDB package in order to later install a more "
"recent version or if a different mariadb-server package is already using it, "
"the data should be kept."
msgstr ""
"Se está a remover o pacote MariaDB de forma a posteriormente instalar uma "
"versão mais recente ou se um pacote mariadb-server já o está a utilizar, "
"então os dados devem ser mantidos."

Bug#871052: mariadb: [INTL:pt] Updated Portuguese translation for debconf messages

[Traduz - DebianPT]

Hi Mattia,

Got file from 
https://i18n.debian.org/material/po/unstable/main/m/mariadb-10.1/debian/po/mariadb-10.1_10.1.25-1_pt.po.gz 
.


It's the last version the site shows has outdated translation.

On 06-08-2017 22:30, Mattia Rizzolo wrote:

Control: reassign -1 src:mariadb-10.1 10.1.25-1

On Sun, Aug 06, 2017 at 10:06:44PM +0100, Traduz - DebianPT wrote:

Package: mariadb
Version: 10.1_10.1.25-1

please be more precise about the metadata… neither package name nor
version were right…


Updated Portuguese translation for mariadb's debconf messages.
Feel free to use it.

For translation updates please contact 'Last Translator' or the
Portuguese Translation Team .

Cheers,
Rui Branco

--

"Traduz" - Portuguese Translation Team
http://www.DebianPT.org

Bug#870888: breaks awscli 1.11.121-1

[Daniele Tricoli]

Hello Jamie,

On Sunday, August 6, 2017 1:06:22 AM CEST Jamie Heilman wrote:
> Package: python3-requests
> Version: 2.18.1-1
> Severity: important
> 
> With this version installed (and python3-urllib3 1.21.1-1), aws cli
> just spits out:
> 
> 'AWSHTTPSConnection' object has no attribute 'ssl_context'
> 
> downgrading to 2.12.4-1 restores normal functionality.  I haven't
> looked to see if awscli is playing dirty pool and fiddling with things
> that were never part of a guaranteed API, if that's the case, reassign
> as necessary.

Thanks for the report. Can you share more details? I don't use AWS for 
personal projects and I forgot to test it at work.

Thanks,

-- 
 Daniele Tricoli 'eriol'
 https://mornie.org

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

Bug#870874: support sound on ltsp clients with pulseaudio

[Mike Gabriel]

On  So 06 Aug 2017 22:45:25 CEST, Wolfgang Schweer wrote:


On Sat, Aug 05, 2017 at 09:35:16PM +, Holger Levsen wrote:

package: debian-edu-config
version: 1.930
severity: wishlist

< pere> a quick look in debian-edu-config make me believe ESPEAKER  
is the secret word to

look for, and /usr/sbin/debian-edu-ltsp-audiodivert and
/etc/desktop-profiles/debian-edu-config.listing are the  
places to update.
PULSE_SERVER seem to be the equivalent pulseaudio  
environment variable, but a
~/.pulse_cookie file might be related too.  given that the  
latter is already
mentioned in /usr/sbin/debian-edu-ltsp-audiodivert, I would  
guess ltsp already

have pulseaudio support...


I guess this bug has been filed after the removal of the dependency on
pulseaudio-esound-compat.

LTSP supports pulseaudio since years (for both thin clients and diskless
workstations).

LTSP_ALSA_DEFAULT is set to 'pulse' and PULSE_SERVER
to something like 'tcp::'

It's rather about the compatibility of programs using esound or even
older ones using /dev/dsp (audio OSS).

IMO the remaining cleanup things still to do are:

(1) drop /usr/share/debian-edu-config/tools/debian-edu-ltsp-audiodivert
because gtick (metronome) is the only program listed but doesn't
need to be diverted as /dev/dsp isn't used anymore.

(2) remove the line containing ESPEAKER in
/etc/desktop-profiles/debian-edu-config.listing

Wolfgang


Thanks for feedback on this. I could hardly imagine that espeaker did  
still player a role in LTSP audio, so I offered help.


Glad to hear, that the clean-up seems to be a minor task.

Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpe63GaKhUqT.pgp
Description: Digitale PGP-Signatur

Bug#871311: Opensmtpd don't find my interface at boot

[Nicolas Repentin]

Hi

Good idea. Indeed there is no ip address yet when opensmtpd start... 

Any way to correct the systemd service to tell him to wait for an ip address ?

I know it's not an opensmtpd package but more a bug with the integration on 
debian and systemd, doesn't it ?


Le 7 août 2017 18:48:30 GMT+02:00, Ryan Kavanagh  a écrit :
>package opensmtpd
>tags 871311 + moreinfo
>thanks
>
>Hi Nicolas,
>
>On Mon, Aug 07, 2017 at 05:16:07PM +0200, Nicolas Repentin wrote:
>> Aug 07 17:07:00 debian opensmtpd[380]: invalid virtual ip or
>interface:
>> enp1s0
>> 
>> The interface really exists:
>
>Does enp1s0 have an associated inet4/inet6 address? I tried debugging
>here, and observed that I can start smtpd with it listening on an
>interface only if that interface has an address. Here's what happens
>when I assign my (unplugged ethernet) interface eno1 a bogus address
>and
>try to start smtpd, versus what happens when I try to start smtpd when
>eno1 doesn't have an address associated with it.
>
>rak@zeta:~$ grep eno1 /etc/smtpd.conf
>listen on eno1
>rak@zeta:~$ sudo ip address flush dev eno1
>rak@zeta:~$ ip addr show eno1
>2: eno1:  mtu 1500 qdisc pfifo_fast
>state DOWN group default qlen 1000
>link/ether 20:47:47:ae:78:79 brd ff:ff:ff:ff:ff:ff
>rak@zeta:~$ sudo smtpd -n
>invalid virtual ip or interface: eno1
>rak@zeta:~$ sudo ip addr add 123.123.123.123 dev eno1
>rak@zeta:~$ ip addr show eno1
>2: eno1:  mtu 1500 qdisc pfifo_fast
>state DOWN group default qlen 1000
>link/ether 20:47:47:ae:78:79 brd ff:ff:ff:ff:ff:ff
>inet 123.123.123.123/32 scope global eno1
>   valid_lft forever preferred_lft forever
>rak@zeta:~$ sudo smtpd -n
>configuration OK
>rak@zeta:~$ sudo ip address flush dev eno1
>rak@zeta:~$ sudo smtpd -n
>invalid virtual ip or interface: eno1
>
>Best wishes,
>Ryan
>
>-- 
>|_)|_/  Ryan Kavanagh  | GPG: 4E46 9519 ED67 7734 268F
>| \| \  https://ryanak.ca/ |  BD95 8F7B F8FC 4A11 C97A

-- 
Nicolas

Bug#802658: libesmtp: Should support TLS 1.1+

[Sebastian Andrzej Siewior]

On 2017-08-07 14:26:07 [+0200], Salvatore Bonaccorso wrote:
> Control: severity important

as in SSL not working anymore in unstable for libesmtp.

> Hi Jeremy,
Hi Salvatore,

> Please find attached a (refreshed) patch which is still valid to add
> the proper support for TLSv1.1+

Description: Add TLSv1.1 and TLSv1.2 support
Origin: vendor
Bug-Debian: https://bugs.debian.org/802658
Author: Salvatore Bonaccorso 
Last-Update: 2015-11-07

--- a/smtp-tls.c
+++ b/smtp-tls.c
@@ -197,11 +197,24 @@ starttls_create_ctx (smtp_session_t sess
   ckf_t status;
 
   /* The decision not to support SSL v2 and v3 but instead to use only
- TLSv1 is deliberate.  This is in line with the intentions of RFC
+ TLSv1.X is deliberate.  This is in line with the intentions of RFC
  3207.  Servers typically support SSL as well as TLS because some
  versions of Netscape do not support TLS.  I am assuming that all
  currently deployed servers correctly support TLS.  */
-  ctx = SSL_CTX_new (TLSv1_client_method ());
+#if (OPENSSL_VERSION_NUMBER >= 0x1010L) && \
+!defined(LIBRESSL_VERSION_NUMBER)  && !defined(OPENSSL_IS_BORINGSSL)
+ctx = SSL_CTX_new (TLS_client_method ());
+#else
+ctx = SSL_CTX_new (SSLv23_client_method ());
+#endif
+
+#ifdef OPENSSL_NO_SSL3
+SSL_CTX_set_options(ctx, SSL_OP_NO_SSLv3);
+#endif
+
+#ifdef OPENSSL_NO_SSL2
+SSL_CTX_set_options(ctx, SSL_OP_NO_SSLv2);
+#endif
 
   /* Load our keys and certificates.  To avoid messing with configuration
  variables etc, use fixed paths for the certificate store.  These are

This looks good. I would however just replace TLSv1_client_method() with
SSLv23_client_method() (without the version check) and be done with it.
Setting the NO_SSLvX thingy is a nop in Debian but upstream might be
happy to see it.

> Regards,
> Salvatore

Sebastian

Bug#870073: [Pkg-mozext-maintainers] Bug#870073: enigmail: Does not encrypt and gives alerts after upgrade to Thunderbird 52

[Daniel Kahn Gillmor]

Control: retitle 870073 enigmail: [jessie only] enigmail needs access to a 
running gpg-agent

On Sun 2017-08-06 16:16:18 +0200, Paul van der Vlis wrote:
> Op 31-07-17 om 23:38 schreef Daniel Kahn Gillmor:
>> I haven't seen this message at all.  are you certain that gpg-agent is
>> running?
>
> I don't see it when I using "ps aux".

ok, this is an issue that is specific to debian jessie only.  on stretch
and later, the gpg-agent has an autolaunch mechanism that avoids these
problems entirely.

>> Do you ever see a dialog box that prompts you for your gpg
>> password?
>
> When I first use Enigmail I am asked for a password. After that, I can
> use Enigmail without any question about a password (I don't like this
> behaviour. But I don't know how to turn it off).

It sounds like enigmail is auto-launching an agent during key
generation, and using it for the rest of the session.  I'd imagine if
you "killall gpg-agent" after key creation you will find that enigmail
no longer works.

enigmail 1.9.8.1 expects gpg to use a gpg agent process.  It does not
prompt the user for a passphrase during normal use.

>> Can you try adding "use-agent" to your ~/.gnupg/gpg.conf  and then
>> logging out and logging back in again?
>
> Yes, the behaviour is still there when I use "use-agent" in
> ~/.gnupg/gpg.conf and logout and login again.
>
> But then I see gpg-agent running with "ps aux".

this is strange.  what do the following commands show when you've logged
in with "use-agent" running?


 echo $GPG_AGENT_INFO
 gpg-connect-agent 'getinfo socket_name' /bye

> The following tests are without "use-agent" in my gpg.conf.

you should put use-agent in gpg.conf if you want to use enigmail -- or
you should upgrade to stretch where it is on by default. :)

>> As a workaround, please also try closing thunderbird and then
>> re-launching it with the following command:
>> 
>> gpg-agent --daemon thunderbird
>> 
>> Does that cause the error message to go away?
>
> Now, I get another dialog window asking me for the password. It has
> "pinentry" in the title.
> I don't get an error anymore while decrypting.
> Encryption seems to be OK, and asks again for a password.
>
> So this looks-like OK, but different as normal.

this is a workaround for you not having "use-agent" in your gpg.conf.

> Maybe this is interesting:
> gpg: WARNING: The GNOME keyring manager hijacked the GnuPG agent.
> gpg: WARNING: GnuPG will not work properly - please configure that tool
> to not interfere with the GnuPG system!
>
> I am using Cinnamon as my desktop-environment, and GDM3 as display manager.

please see:

   https://wiki.gnupg.org/GnomeKeyring

for information about gnome-keyring and gpg-agent.  modern versions of
gnome-keyring and gpg-agent play nicer together.

> 2017-08-06 16:00:06.149 [DEBUG] enigmail.js: detectGpgAgent: 
> GPG_AGENT_INFO='/run/user/1000/keyring/gpg:0:1'

This is very surprising to me, especially for gpg-agent 2.0.26.  I don't
think that version of gpg-agent used /run/user -- i would expect it
instead to use something like /tmp/gpg-1uGi7D/S.gpg-agent:679:1

where is this value coming from?  have you modified any config files, or
tried to mix packages across versions of the distro?

I'm still not able to reproduce the specific behavior you describe,
unfortunately.

Regards,

--dkg


signature.asc
Description: PGP signature

Bug#869745: enigmail: Enigmail stopped working after the update on Debian Jessie

[Daniel Kahn Gillmor]

Control: forcemerge 869745 869745

On Sat 2017-08-05 18:44:22 -0300, Daniel Bareiro wrote:
> Please mark as duplicate with #869774.
>
> This issue has already been solved in that other bug report.

sorry to hear you had trouble.  hopefully the other report provided the
information you needed.

Regards,

--dkg

Bug#871398: fontconfig: [INTL:pt] Updated Portuguese translation for debconf messages

[Traduz - DebianPT]

Package: fontconfig
Version: 2.12.3-0.2
Tags: l10n, patch
Severity: wishlist

Updated Portuguese translation for fontconfig's debconf messages.
Feel free to use it.

For translation updates please contact 'Last Translator' or the
Portuguese Translation Team .
--
Best regards,

"Traduz" - Portuguese Translation Team
http://www.DebianPT.org











# Portuguese translation of fontconfig
# 2004 Miguel Figueiredo 
# 2007 Eduardo Silva , 14 trad.
# 2012 Miguel Figueiredo 
# Rui Branco - DebianPT , 2017.
#
msgid ""
msgstr ""
"Project-Id-Version: fontconfig 2.12.3-0.2\n"
"Report-Msgid-Bugs-To: fontcon...@packages.debian.org\n"
"POT-Creation-Date: 2017-07-05 11:29+0200\n"
"PO-Revision-Date: 2017-08-06 10:06+0100\n"
"Last-Translator: Rui Branco - DebianPT \n"
"Language-Team: Portuguese \n"
"Language: pt\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

#. Type: select
#. Choices
#: ../fontconfig-config.templates:2001
msgid "Native"
msgstr "Nativo"

#. Type: select
#. Choices
#: ../fontconfig-config.templates:2001
msgid "Autohinter"
msgstr "Desenho automático (Autohinter)"

#. Type: select
#. Choices
#. Type: select
#. Choices
#: ../fontconfig-config.templates:2001 ../fontconfig-config.templates:3001
msgid "None"
msgstr "Nenhum"

#. Type: select
#. Description
#: ../fontconfig-config.templates:2002
msgid "Font tuning method for screen (system default):"
msgstr "Método de optimização de tipos de letra para ecrã (predefinido):"

#. Type: select
#. Description
#: ../fontconfig-config.templates:2002
msgid ""
"Please select the preferred method for tuning fonts for screen rendering."
msgstr ""
"Por favor seleccione o método preferido para optimizar os tipos de letra "
"para o seu desenho no ecrã."

#. Type: select
#. Description
#: ../fontconfig-config.templates:2002
msgid ""
"Select 'Native' if you mostly use DejaVu (the default in Debian) or any of "
"the Microsoft fonts. Select 'Autohinter' if you mostly use other TrueType "
"fonts. Select 'None' if you want blurry text."
msgstr ""
"Seleccione 'Nativo' se utiliza mais o tipo de letra DejaVu (utilizado por "
"omissão em Debian) ou quaisquer dos tipos de letra da Microsoft. Seleccione "
"'Desenho Automático' (Autohinter)' se utiliza maioritariamente outros tipos "
"de letra TrueType. Selecione 'Nenhum' se desejar ter texto desfocado."

#. Type: select
#. Choices
#: ../fontconfig-config.templates:3001
msgid "Slight"
msgstr "Ligeiro"

#. Type: select
#. Choices
#: ../fontconfig-config.templates:3001
msgid "Medium"
msgstr "Médio"

#. Type: select
#. Choices
#: ../fontconfig-config.templates:3001
msgid "Full"
msgstr "Total"

#. Type: select
#. Description
#: ../fontconfig-config.templates:3002
#| msgid "Font tuning method for screen (system default):"
msgid "Automatic font hinting style:"
msgstr "Estilo de desenho do tipo de letra automático:"

#. Type: select
#. Description
#: ../fontconfig-config.templates:3002
#| msgid ""
#| "Please select the preferred method for tuning fonts for screen rendering."
msgid ""
"Please select the preferred automatic font hinting style to be used as the "
"system default."
msgstr ""
"Por favor seleccione o estilo de desenho do tipo de letra automático a "
"ser usado como predefinição do sistema."

#. Type: select
#. Description
#: ../fontconfig-config.templates:3002
msgid ""
"The hinting style is the amount of font reshaping done to line up to the "
"grid. \"Slight\" will make the font more fuzzy to line up to the grid but "
"will be better in retaining font shape, while \"Full\" will be a crisp font "
"that aligns well to the pixel grid but will lose a greater amount of font "
"shape. \"Slight\" is the default setting."
msgstr ""
"O estilo de desenho do tipo de letra é a parte de redesenhamento efectuado "
"de modo a encaixar na grelha. \"Ligeiro\" tornará o tipo de letra mais"
" desfocado de modo a encaixar na grelha mas manterá mais fielmente o formato "
"do tipo de letra. O \"Total\" será um tipo de letra mais contundente que se "
"adapta melhor à grelha do pixel mas perderá uma grande parte do formato do "
"tipo de letra. \"Ligeiro\" é a configuração predefinida."

#. Type: select
#. Description
#: ../fontconfig-config.templates:3002
msgid "To revert to the pre-2.12 behavior, select \"Full\"."
msgstr "Para reverter para o comportamento pre-2.12, selecione \"Total\"."

#. Type: select
#. Choices
#: ../fontconfig-config.templates:4001
msgid "Automatic"
msgstr "Automático"

#. Type: select
#. Choices
#: ../fontconfig-config.templates:4001
msgid "Always"
msgstr "Sempre"

#. Type: select
#. Choices
#: ../fontconfig-config.templates:4001
msgid "Never"
msgstr "Nunca"

#. Type: select
#. Description
#: ../fontconfig-config.templates:4002
msgid "Enable subpixel rendering for screen:"
msgstr 

Bug#871399: libreoffice-impress: Textboxes content no longer read by screen reader

[Alex ARNAUD]

Package: libreoffice-impress
Version: 1:5.3.0~alpha1-1
Tags: a11y upstream
Owner: b...@hypra.fr
User: b...@hypra.fr
Usertags: hypra
Forwarded: https://bugs.documentfoundation.org/show_bug.cgi?id=102145

DESCRIPTION FROM UPSTREAM:

Steps:
1) Start screen reader
2) Open impress
3) Change to 'title, content'
4) Select content textbox and press F2
5) Enter 2 bullets and press Esc
6) Press tab twice to change focus to title textbox and back
7) press f2 to edit and then press arrow keys and nothing will be read by 
screen reader in this textbox or title textbox

Tested with Orca and NVDA.

Bug#858911: thunderbird: Apparmor prevents opening links from emails in firefox.

[intrigeri]

Control: reassign -1 apparmor
Control: retitle -1 ubuntu-browsers abstraction lacks support for non-ESR 
Firefox
Control: affects -1 + thunderbird

Hi!

intrigeri:
> I'll start playing with Flatpak to reproduce this.

After investigating this bug has nothing to do with Flatpak (this was
a good opportunity to try it out though! :) 

I can't reproduce this bug when Firefox ESR is configured as the
default browser. I can reproduce the bug when Firefox is.

The bug is in abstractions/ubuntu-browsers, and can be fixed this way:

--- a/apparmor.d/abstractions/ubuntu-browsers
+++ b/apparmor.d/abstractions/ubuntu-browsers
@@ -31,7 +31,7 @@
   # and abrowser)
   /usr/bin/firefox Cxr -> sanitized_helper,
   /usr/lib/firefox*/firefox*.sh Cx -> sanitized_helper,
-  /usr/lib/firefox-esr/firefox* Cx -> sanitized_helper,
+  /usr/lib/firefox*/firefox* Cx -> sanitized_helper,
 
   # Iceweasel
   /usr/bin/iceweasel Cxr -> sanitized_helper,


I'll fix this in src:apparmor later today and will submit a merge
request upstream about it.

Thanks!

Bug#871279: libdolfin2016.2: requires rebuild against GCC 7 and symbols/shlibs bump

[Drew Parsons]

On Mon, 07 Aug 2017 15:47:15 +0100 jcowg...@debian.org wrote:
> Package: libdolfin2016.2
> Version: 2016.2.0-5
> 
> It appears that your package provides an external symbol that is
> affected by the recent name mangling changes in GCC 7. See:
> https://gcc.gnu.org/gcc-7/porting_to.html#conversion-op-mangling
> 
...
> 
> - If your package is about to be renamed due to an upstream SONAME
bump,
>   you do not need to add any special symbols handling.
> 


dolfin 2017.1 is in the NEW queue, so that upgrade will handle this
bug.

Drew

Bug#871397: RM: doris -- ROM; RC buggy, dead upstream

[Bas Couwenberg]

Package: ftp.debian.org
Severity: normal

Please remove doris from the archive, it is RC buggy and dead upstream.

Kind Regards,

Bas

Bug#871311: Opensmtpd don't find my interface at boot

[Ryan Kavanagh]

package opensmtpd
tags 871311 + moreinfo
thanks

Hi Nicolas,

On Mon, Aug 07, 2017 at 05:16:07PM +0200, Nicolas Repentin wrote:
> Aug 07 17:07:00 debian opensmtpd[380]: invalid virtual ip or interface:
> enp1s0
> 
> The interface really exists:

Does enp1s0 have an associated inet4/inet6 address? I tried debugging
here, and observed that I can start smtpd with it listening on an
interface only if that interface has an address. Here's what happens
when I assign my (unplugged ethernet) interface eno1 a bogus address and
try to start smtpd, versus what happens when I try to start smtpd when
eno1 doesn't have an address associated with it.

rak@zeta:~$ grep eno1 /etc/smtpd.conf
listen on eno1
rak@zeta:~$ sudo ip address flush dev eno1
rak@zeta:~$ ip addr show eno1
2: eno1:  mtu 1500 qdisc pfifo_fast state 
DOWN group default qlen 1000
link/ether 20:47:47:ae:78:79 brd ff:ff:ff:ff:ff:ff
rak@zeta:~$ sudo smtpd -n
invalid virtual ip or interface: eno1
rak@zeta:~$ sudo ip addr add 123.123.123.123 dev eno1
rak@zeta:~$ ip addr show eno1
2: eno1:  mtu 1500 qdisc pfifo_fast state 
DOWN group default qlen 1000
link/ether 20:47:47:ae:78:79 brd ff:ff:ff:ff:ff:ff
inet 123.123.123.123/32 scope global eno1
   valid_lft forever preferred_lft forever
rak@zeta:~$ sudo smtpd -n
configuration OK
rak@zeta:~$ sudo ip address flush dev eno1
rak@zeta:~$ sudo smtpd -n
invalid virtual ip or interface: eno1

Best wishes,
Ryan

-- 
|_)|_/  Ryan Kavanagh  | GPG: 4E46 9519 ED67 7734 268F
| \| \  https://ryanak.ca/ |  BD95 8F7B F8FC 4A11 C97A


signature.asc
Description: PGP signature

Bug#871395: transition: qtbase-opensource-src

[Lisandro Damián Nicanor Pérez Meyer]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

Hi RT! Normal request for a Qt transition slot.

Dmitry took the time to check all reverse dependencies and created
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-qt-...@lists.debian.org;tag=qt5.9

>From all this ones all are fixed except one which has a patch available.

As somewhat "normal" with a Qt transition we have two "tracks":

title = "qtbase-opensource-src";
is_affected = .depends ~ "qtbase-abi-5-7-1" | .depends ~ "qtbase-abi-5-9-1";
is_good = .depends ~ "qtbase-abi-5-9-1";
is_bad = .depends ~ "qtbase-abi-5-7-1";

And:

title = "qtdeclarative-opensource-src";
is_affected = .depends ~ "qtdeclarative-abi-5-7-0" | .depends ~ 
"qtdeclarative-abi-5-9-1";
is_good = .depends ~ "qtdeclarative-abi-5-9-1";
is_bad = .depends ~ "qtdeclarative-abi-5-7-0";

Thanks in advance, Lisandro.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'buildd-unstable'), (500, 'testing'), (500, 'stable'), 
(500, 'oldstable'), (1, 'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.11.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_AR:es (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Bug#871389: altree: FTBFS: build-dependency not installable: libmath-tamuanova-perl

[Andreas Tille]

Hi Lucas,

I wonder whether something might be wrong with the apt cache, since
I can not find any sign that libmath-tamuanova-perl would be missing.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#871394: libreoffice-writer: A section in writer document is not visible to AT-SPI

[Alex ARNAUD]

Package: libreoffice-writer
Version: 1:3.3.0~beta2-1
Tags: a11y upstream
Owner: b...@hypra.fr
User: b...@hypra.fr
Usertags: hypra
Forwarded: https://bugs.documentfoundation.org/show_bug.cgi?id=35112

DESCRIPTION FROM UPSTREAM:> A section in writer document is not visible 
to AT-SPI. If a section is visible to AT-SPI and exposes ROLE_SECTION, 
assistive tools like a screen reader can use the information to improve 
accessibility of the document.


Steps to reproduce:
1. Start Libre Office writer. Create a new text document. Add a section. Add 
some text e.g. 'Content of section 1' into the section. Add another section. 
Add some text e.g. 'Content of section 2' into it. Save the document.

2. Start Accerciser accessibility explorer.

3. Go to the accessible tree view at top left. As shown in attached 
screen-shot, select the accessible object corresponding to the document just 
created. The tree shows only paragraphs under the document. There are no 
accessible container objects corresponding to the sections.

Bug#870035: Compile with '--disable-bundled-libtom' to use system libtomcrypt/libtommath (Was: Bug#870035: dropbear-bin: ftbfs on x32)

[Guilhem Moulin]

Hi,

Actually libtomcrypt 1.17 and libtommath 1.0 are both available in
Debian, so I'm tempted to add --disable-bundled-libtom to CFLAGS and
dynamically link against these libraries.  Not doing so is in fact a
violation of Debian policy §4.13:

“Some software packages include in their distribution convenience
copies of code from other software packages, generally so that users
compiling from source don't have to download multiple packages.
Debian packages should not make use of these convenience copies
unless the included package is explicitly intended to be used in
this way.”
— https://www.debian.org/doc/debian-policy/ch-source.html#s-embeddedfiles

However, as of 2017.75 dropbear's libtom bundle consists of libtomcrypt
1.16 and libtommath 0.40.  AFAICT dynamic linking against the latest
versions (1.17 + 1.0) works out of the box; Matt (X-Debbugs-Cc), are you
aware of any regressions when linking 2017.75 against the latest libtom?

Cheers,
-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#855118: Please fix in Stretch

[Bastian Blank]

Hi

Right now this package is unusable in Stretch. Please fix.

Bastian

-- 
The sooner our happiness together begins, the longer it will last.
-- Miramanee, "The Paradise Syndrome", stardate 4842.6

Bug#732445: debian-policy should encourage verification of upstream cryptographic signaturse

[Russ Allbery]

Control: tag -1 patch

Daniel Kahn Gillmor  writes:

> debian-policy should encourage verification of upstream cryptographic
> signatures.

> Since devscripts 2.13.3 (see #610712), uscan has supported the ability
> to automatically verify upstream's cryptographic signatures if the
> signing key and URL to the signature is well-known.
>  
> debian-policy should recommend that package maintainers regularly
> verify these signatures for new versions, and mention the files used.

Hi everyone,

Here's a proposed new patch for this.

In an ideal world, we would have a documented set of metadata for finding
upstream releases, of which uscan is just one implementation, and document
that in Policy.  This patch doesn't attempt to do that; it tries to find a
compromise between the current Policy language ("include a watch file for
uscan") and specifying the location of the upstream signing keys, while
deferring all of the details to the uscan documentation.

I decided to keep this all in the uscan section rather than adding a new
section for the upstream signing key location, since right now this is all
closely linked to uscan functionality (and to avoid renumbering sections
or having a section weirdly separated from the uscan description).

How does this look to everyone?

diff --git a/policy.xml b/policy.xml
index 6086901..c14d9b4 100644
--- a/policy.xml
+++ b/policy.xml
@@ -2556,11 +2556,28 @@ endif
 
   
 This is an optional, recommended configuration file for the
-uscan utility which defines how to
+uscan utility which defines how to
 automatically scan ftp or http sites for newly available updates
 of the package.  This is used Debian QA tools to help with quality
 control and maintenance of the distribution as a whole.
   
+  
+If the upstream maintainer of the software provides PGP signatures
+for new releases, including the information required for
+uscan to verify signatures for new upstream
+releases is also recommended.  To do this, use the
+pgpsigurlmangle option in
+debian/watch to specify the location of the
+upstream signature, and include the key or keys used to sign
+upstream releases in the Debian source package as
+debian/upstream/signing-key.asc.
+  
+  
+For more information about uscan and these
+options, including how to generate the file containing upstream
+signing keys, see
+
uscan1.
+  
 
 
 

-- 
Russ Allbery (r...@debian.org)   

Bug#871379: libpdl-stats-perl: FTBFS: build-dependency not installable: pdl (>= 1:2.016)

[Sebastiaan Couwenberg]

Hi Lucas,

Thanks for your rebuild work.

Having said that, I'm not happy with this bugreport. There is nothing we
can do about it without a massive amount of work.

The gsl maintain has once again not coordinated the transition, and
created a mess for its reverse dependencies in unstable.

To fix this issue we need to fix the conflicts in the updated gls
package, which also has a revision stuck in NEW, and coordinate the gls
transition with the Release Team. I'm not really willing to do that
again, I'm still upset that I had to get involved in the previous
uncoordinated gsl transition.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#871393: sxiv FTCBFS: uses the build architecture toolchain

[Helmut Grohne]

Source: sxiv
Version: 1.3.2-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

sxiv fails to cross build from source, because it uses the build
architecture toolchain. Just indirecting the make invocation through
dh_auto_build fixes the cross build, because debhelper knows how to pass
cross compilers to make. Please consider applying the attached patch.

Helmut
diff --minimal -Nru sxiv-1.3.2/debian/changelog sxiv-1.3.2/debian/changelog
--- sxiv-1.3.2/debian/changelog 2015-12-27 18:45:57.0 +0100
+++ sxiv-1.3.2/debian/changelog 2017-08-07 18:28:44.0 +0200
@@ -1,3 +1,10 @@
+sxiv (1.3.2-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_build pass cross compilers to make. (Closes: #-1)
+
+ -- Helmut Grohne   Mon, 07 Aug 2017 18:28:44 +0200
+
 sxiv (1.3.2-1) unstable; urgency=medium
 
   * New upstream release.
diff --minimal -Nru sxiv-1.3.2/debian/rules sxiv-1.3.2/debian/rules
--- sxiv-1.3.2/debian/rules 2015-12-27 16:54:47.0 +0100
+++ sxiv-1.3.2/debian/rules 2017-08-07 18:28:42.0 +0200
@@ -7,7 +7,7 @@
dh $@
 
 override_dh_auto_build:
-   CFLAGS="$(CFLAGS) $(shell getconf LFS_CFLAGS) $(CPPFLAGS)" 
LDFLAGS="$(LDFLAGS)" $(MAKE) PREFIX=/usr
+   CFLAGS="$(CFLAGS) $(shell getconf LFS_CFLAGS) $(CPPFLAGS)" 
LDFLAGS="$(LDFLAGS)" dh_auto_build -- PREFIX=/usr

 
 override_dh_auto_install:

Bug#864701: grub-common: grub-mkrescue does nothing, successfully

[Thomas Schmitt]

Hi,

Vladimir Serbinenko has just committed a fix:
  
http://git.savannah.gnu.org/cgit/grub.git/commit/?id=e66dc5d71ebfc9763420a76c274e6980d54641c3


Have a nice day :)

Thomas

Bug#871392: miaviewit: FTBFS: build-dependency not installable: libmia-2.4-dev (>= 2.4.4)

[Lucas Nussbaum]

Source: miaviewit
Version: 1.0.5-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9.0.0), autotools-dev, libmia-2.4-dev (>= 
> 2.4.4), libgle3-dev, libgtkglextmm-x11-1.2-dev, libboost-thread-dev, 
> libgtkmm-2.4-dev, libxml++2.6-dev, libvistaio-dev
> Filtered Build-Depends: debhelper (>= 9.0.0), autotools-dev, libmia-2.4-dev 
> (>= 2.4.4), libgle3-dev, libgtkglextmm-x11-1.2-dev, libboost-thread-dev, 
> libgtkmm-2.4-dev, libxml++2.6-dev, libvistaio-dev
> dpkg-deb: building package 'sbuild-build-depends-miaviewit-dummy' in 
> '/<>/resolver-WxzSAH/apt_archive/sbuild-build-depends-miaviewit-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-miaviewit-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-WxzSAH/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-WxzSAH/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-WxzSAH/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-WxzSAH/apt_archive ./ Sources [566 B]
> Get:5 copy:/<>/resolver-WxzSAH/apt_archive ./ Packages [648 B]
> Fetched 2177 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install miaviewit build dependencies (apt-based resolver)
> -
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-miaviewit-dummy : Depends: libmia-2.4-dev (>= 2.4.4) 
> but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/miaviewit_1.0.5-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#871389: altree: FTBFS: build-dependency not installable: libmath-tamuanova-perl

[Lucas Nussbaum]

Source: altree
Version: 1.3.1-4
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: bash-completion, debhelper (>= 9), latex-make, 
> ghostscript, texlive-lang-french, texlive-latex-extra, 
> texlive-latex-recommended, texlive-fonts-recommended, libmath-tamuanova-perl, 
> libgsl-dev, libatlas-base-dev, libtest-deep-perl
> Filtered Build-Depends: bash-completion, debhelper (>= 9), latex-make, 
> ghostscript, texlive-lang-french, texlive-latex-extra, 
> texlive-latex-recommended, texlive-fonts-recommended, libmath-tamuanova-perl, 
> libgsl-dev, libatlas-base-dev, libtest-deep-perl
> dpkg-deb: building package 'sbuild-build-depends-altree-dummy' in 
> '/<>/resolver-rsVmG6/apt_archive/sbuild-build-depends-altree-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-altree-dummy 
> sbuild-build-depends-core-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-rsVmG6/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-rsVmG6/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-rsVmG6/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-rsVmG6/apt_archive ./ Sources [591 B]
> Get:5 copy:/<>/resolver-rsVmG6/apt_archive ./ Packages [676 B]
> Fetched 2230 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install altree build dependencies (apt-based resolver)
> --
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-altree-dummy : Depends: libmath-tamuanova-perl but it 
> is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/altree_1.3.1-4_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#871391: pygpiv: FTBFS: build-dependency not installable: libgpiv3-dev

[Lucas Nussbaum]

Source: pygpiv
Version: 2.0.0-4.2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dpkg-dev (>= 1.16.1), python-all-dev 
> (>= 2.6.6-3~), swig, libglib2.0-dev, libfftw3-dev, libgsl0-dev, libhdf5-dev 
> (>= 1.8.8), libnetpbm10-dev, libpng-dev, libgpiv3-dev
> Filtered Build-Depends: debhelper (>= 9), dpkg-dev (>= 1.16.1), 
> python-all-dev (>= 2.6.6-3~), swig, libglib2.0-dev, libfftw3-dev, 
> libgsl0-dev, libhdf5-dev (>= 1.8.8), libnetpbm10-dev, libpng-dev, libgpiv3-dev
> dpkg-deb: building package 'sbuild-build-depends-pygpiv-dummy' in 
> '/<>/resolver-xp8Ktu/apt_archive/sbuild-build-depends-pygpiv-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-pygpiv-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-xp8Ktu/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-xp8Ktu/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-xp8Ktu/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-xp8Ktu/apt_archive ./ Sources [569 B]
> Get:5 copy:/<>/resolver-xp8Ktu/apt_archive ./ Packages [649 B]
> Fetched 2181 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install pygpiv build dependencies (apt-based resolver)
> --
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-pygpiv-dummy : Depends: libgpiv3-dev but it is not 
> going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/pygpiv_2.0.0-4.2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#871386: firefox: FTBFS: cc1: error: -Wformat-security ignored without -Wformat [-Werror=format-security]

[Lucas Nussbaum]

Source: firefox
Version: 54.0-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 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):
> /usr/bin/gcc -std=gnu99 -o nr_crypto.o -c 
> -I/<>/build-browser/dist/system_wrappers -include 
> /<>/config/gcc_hidden.h -DNDEBUG -DTRIMMED=1 
> -D_FILE_OFFSET_BITS=64 -DCHROMIUM_BUILD -DUSE_LIBJPEG_TURBO=1 -DUSE_NSS=1 
> -DENABLE_ONE_CLICK_SIGNIN -DGTK_DISABLE_SINGLE_INCLUDES=1 -D_ISOC99_SOURCE=1 
> -DENABLE_REMOTING=1 -DENABLE_WEBRTC=1 -DENABLE_CONFIGURATION_POLICY 
> -DENABLE_INPUT_SPEECH -DENABLE_NOTIFICATIONS -DENABLE_GPU=1 
> -DENABLE_EGLIMAGE=1 -DUSE_SKIA=1 -DENABLE_TASK_MANAGER=1 
> -DENABLE_WEB_INTENTS=1 -DENABLE_EXTENSIONS=1 -DENABLE_PLUGIN_INSTALLATION=1 
> -DENABLE_PROTECTOR_SERVICE=1 -DENABLE_SESSION_SERVICE=1 -DENABLE_THEMES=1 
> -DENABLE_BACKGROUND=1 -DENABLE_AUTOMATION=1 -DENABLE_PRINTING=1 
> -DENABLE_CAPTIVE_PORTAL_DETECTION=1 -DSANITY_CHECKS -DUSE_TURN -DUSE_ICE 
> -DUSE_RFC_3489_BACKWARDS_COMPATIBLE -DUSE_STUND_0_96 -DUSE_STUN_PEDANTIC 
> -DNR_SOCKET_IS_VOID_PTR -Drestrict= '-DR_PLATFORM_INT_TYPES=' 
> -DR_DEFINED_INT2=int16_t -DR_DEFINED_UINT2=uint16_t -DR_DEFINED_INT4=int32_t 
> -DR_DEFINED_UINT4=uint32_t -DR_DEFINED_INT8=int64_t 
> -DR_DEFINED_UINT8=uint64_t -DLINUX -DHAVE_LIBM=1 -DHAVE_STRDUP=1 
> -DHAVE_STRLCPY=1 -DHAVE_SYS_TIME_H=1 -DHAVE_VFPRINTF=1 
> -DNEW_STDIORETSIGTYPE=void -DTIME_WITH_SYS_TIME_H=1 
> '-D__UNUSED__=__attribute__((unused))' -DNVALGRIND 
> -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DSTATIC_EXPORTABLE_JS_API -DMOZ_HAS_MOZGLUE 
> -DMOZILLA_INTERNAL_API -DIMPL_LIBXUL 
> -I/<>/media/mtransport/third_party/nICEr 
> -I/<>/build-browser/media/mtransport/third_party/nICEr/nicer_nicer
>  -I/<>/media/mtransport/third_party/nrappkit/src/event 
> -I/<>/media/mtransport/third_party/nrappkit/src/log 
> -I/<>/media/mtransport/third_party/nrappkit/src/plugin 
> -I/<>/media/mtransport/third_party/nrappkit/src/registry 
> -I/<>/media/mtransport/third_party/nrappkit/src/share 
> -I/<>/media/mtransport/third_party/nrappkit/src/stats 
> -I/<>/media/mtransport/third_party/nrappkit/src/util 
> -I/<>/media/mtransport/third_party/nrappkit/src/util/libekr 
> -I/<>/media/mtransport/third_party/nrappkit/src/port/generic/include
>  -I/<>/media/mtransport/third_party/nICEr/src/crypto 
> -I/<>/media/mtransport/third_party/nICEr/src/ice 
> -I/<>/media/mtransport/third_party/nICEr/src/net 
> -I/<>/media/mtransport/third_party/nICEr/src/stun 
> -I/<>/media/mtransport/third_party/nICEr/src/util 
> -I/<>/media/mtransport/third_party/nrappkit/src/port/linux/include
>  -I/<>/build-browser/ipc/ipdl/_ipdlheaders 
> -I/<>/ipc/chromium/src -I/<>/ipc/glue 
> -I/<>/build-browser/dist/include-fPIC  -include 
> /<>/build-browser/mozilla-config.h -DMOZILLA_CLIENT -MD -MP -MF 
> .deps/nr_crypto.o.pp -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wempty-body 
> -Wignored-qualifiers -Wpointer-arith -Wsign-compare -Wtype-limits 
> -Wunreachable-code -Wno-error=maybe-uninitialized 
> -Wno-error=deprecated-declarations -Wno-error=array-bounds -Wformat 
> -fstack-protector-strong -Wformat -Werror=format-security 
> -fno-schedule-insns2 -fno-lifetime-dse -fno-delete-null-pointer-checks 
> -fno-strict-aliasing -ffunction-sections -fdata-sections -fno-math-errno 
> -pthread -pipe  -g -freorder-blocks -Os -fomit-frame-pointer -Wall 
> -Wno-parentheses -Wno-strict-prototypes -Wmissing-prototypes -Wno-format  
> /<>/media/mtransport/third_party/nICEr/src/crypto/nr_crypto.c
> cc1: error: -Wformat-security ignored without -Wformat 
> [-Werror=format-security]
> cc1: some warnings being treated as errors
> /<>/config/rules.mk:886: recipe for target 'nr_crypto.o' failed
> make[6]: *** [nr_crypto.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/firefox_54.0-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#871390: canu: FTBFS: merTrim/merTrim.C:1785:26: error: format not a string literal and no format arguments [-Werror=format-security]

[Lucas Nussbaum]

Source: canu
Version: 1.5+dfsg-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 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):
> g++ -o 
> /<>/canu-1.5+dfsg/Linux-amd64/obj/overlapInCore/overlapInCore/overlapInCore-Process_String_Overlaps.o
>  -c -MD -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -fdebug-prefix-map=/<>/canu-1.5+dfsg=. -fstack-protector-strong 
> -Wformat -Werror=format-security -D_GLIBCXX_PARALLEL -pthread -fopenmp -fPIC 
> -Wall -Wextra -Wno-write-strings -Wno-unused -Wno-char-subscripts 
> -Wno-sign-compare -Wformat -g3 -O4 -funroll-loops -fexpensive-optimizations 
> -finline-functions -fomit-frame-pointer -DLIBBACKTRACE 
> -I/<>/canu-1.5+dfsg/src -IAS_UTL -Istores 
> -IoverlapInCore/liboverlap 
> overlapInCore/overlapInCore-Process_String_Overlaps.C
> meryl/maskMers.C: In member function 'void 
> merMaskedSequence::loadMasking(uint32)':
> meryl/maskMers.C:159:8: warning: ignoring return value of 'size_t 
> fread(void*, size_t, size_t, FILE*)', declared with attribute 
> warn_unused_result [-Wunused-result]
>fread(&_numSeq,  sizeof(uint32), 1, maskMersFile);
>~^~~~
> meryl/maskMers.C:160:8: warning: ignoring return value of 'size_t 
> fread(void*, size_t, size_t, FILE*)', declared with attribute 
> warn_unused_result [-Wunused-result]
>fread(&_merSize, sizeof(uint32), 1, maskMersFile);
>~^~~~
> meryl/maskMers.C:168:8: warning: ignoring return value of 'size_t 
> fread(void*, size_t, size_t, FILE*)', declared with attribute 
> warn_unused_result [-Wunused-result]
>fread( _seqLen,   sizeof(uint32), _numSeq, maskMersFile);
>~^~~
> meryl/maskMers.C:183:12: warning: ignoring return value of 'size_t 
> fread(void*, size_t, size_t, FILE*)', declared with attribute 
> warn_unused_result [-Wunused-result]
>fread(_masking[i],  sizeof(char),   _seqLen[i], maskMersFile);
>~^~~~
> meryl/maskMers.C:184:12: warning: ignoring return value of 'size_t 
> fread(void*, size_t, size_t, FILE*)', declared with attribute 
> warn_unused_result [-Wunused-result]
>fread(_repeatID[i], sizeof(uint32), _seqLen[i], maskMersFile);
>~^~~~
> merTrim/merTrim.C: In member function 'bool 
> mertrimComputation::initializeFASTQ(mertrimGlobalData*)':
> merTrim/merTrim.C:557:37: warning: 'memset' used with constant zero length 
> parameter; this could be due to transposed parameters 
> [-Wmemset-transposed-args]
>memset(verifyName, 1024, 0);
>  ^
> merTrim/merTrim.C:558:37: warning: 'memset' used with constant zero length 
> parameter; this could be due to transposed parameters 
> [-Wmemset-transposed-args]
>memset(verifySeq,  allocLen, 0);  //  Needed, for verified reads 
> shorter than real reads
>  ^
> merTrim/merTrim.C: In member function 'void mertrimComputation::dump(char*)':
> merTrim/merTrim.C:1785:26: error: format not a string literal and no format 
> arguments [-Werror=format-security]
>fprintf(stderr, logLine);
>   ^
> merTrim/merTrim.C:1795:26: error: format not a string literal and no format 
> arguments [-Werror=format-security]
>fprintf(stderr, logLine);
>   ^
> merTrim/merTrim.C:1816:28: error: format not a string literal and no format 
> arguments [-Werror=format-security]
>  fprintf(stderr, logLine);
> ^
> merTrim/merTrim.C:1826:28: error: format not a string literal and no format 
> arguments [-Werror=format-security]
>  fprintf(stderr, logLine);
> ^
> merTrim/merTrim.C:1837:26: error: format not a string literal and no format 
> arguments [-Werror=format-security]
>fprintf(stderr, logLine);
>   ^
> merTrim/merTrim.C:1847:26: error: format not a string literal and no format 
> arguments [-Werror=format-security]
>fprintf(stderr, logLine);
>   ^
> merTrim/merTrim.C:1857:26: error: format not a string literal and no format 
> arguments [-Werror=format-security]
>fprintf(stderr, logLine);
>   ^
> merTrim/merTrim.C:1867:26: error: format not a string literal and no format 
> arguments [-Werror=format-security]
>fprintf(stderr, logLine);
>   ^
> merTrim/merTrim.C:1877:2

Bug#871388: gqrx-sdr: FTBFS: unsatisfiable build-dependency: libgsl0-dev (versioned dep on a virtual pkg?)

[Lucas Nussbaum]

Source: gqrx-sdr
Version: 2.6-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cmake (>= 2.8), debhelper (>= 9), gnuradio-dev (>> 
> 3.7.10), gr-osmosdr (>> 0.1.4-11), libasound2-dev, libboost-dev, 
> libboost-program-options-dev, libboost-system-dev, libfftw3-dev, libgsl0-dev, 
> liblog4cpp5-dev, libpulse-dev, libqt5svg5-dev, libsoapysdr-dev, libudev-dev, 
> pkg-config, qt5-qmake, qtbase5-dev, qtbase5-dev-tools, qtchooser
> Filtered Build-Depends: cmake (>= 2.8), debhelper (>= 9), gnuradio-dev (>> 
> 3.7.10), gr-osmosdr (>> 0.1.4-11), libasound2-dev, libboost-dev, 
> libboost-program-options-dev, libboost-system-dev, libfftw3-dev, libgsl0-dev, 
> liblog4cpp5-dev, libpulse-dev, libqt5svg5-dev, libsoapysdr-dev, libudev-dev, 
> pkg-config, qt5-qmake, qtbase5-dev, qtbase5-dev-tools, qtchooser
> dpkg-deb: building package 'sbuild-build-depends-gqrx-sdr-dummy' in 
> '/<>/resolver-BOjegu/apt_archive/sbuild-build-depends-gqrx-sdr-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-gqrx-sdr-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-BOjegu/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-BOjegu/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-BOjegu/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-BOjegu/apt_archive ./ Sources [653 B]
> Get:5 copy:/<>/resolver-BOjegu/apt_archive ./ Packages [722 B]
> Fetched 2338 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install gqrx-sdr build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-gqrx-sdr-dummy : Depends: libgsl0-dev
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/gqrx-sdr_2.6-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#871385: python-scrapy-djangoitem: FTBFS: build-dependency not installable: python3-scrapy

[Lucas Nussbaum]

Source: python-scrapy-djangoitem
Version: 1.1.1-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dh-python, python-all, python-django, 
> python-scrapy, python-setuptools, python-six, python3-all, python3-django, 
> python3-scrapy, python3-setuptools, python3-six
> Filtered Build-Depends: debhelper (>= 9), dh-python, python-all, 
> python-django, python-scrapy, python-setuptools, python-six, python3-all, 
> python3-django, python3-scrapy, python3-setuptools, python3-six
> dpkg-deb: building package 
> 'sbuild-build-depends-python-scrapy-djangoitem-dummy' in 
> '/<>/resolver-NzGLi2/apt_archive/sbuild-build-depends-python-scrapy-djangoitem-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-python-scrapy-djangoitem-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-NzGLi2/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-NzGLi2/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-NzGLi2/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-NzGLi2/apt_archive ./ Sources [548 B]
> Get:5 copy:/<>/resolver-NzGLi2/apt_archive ./ Packages [630 B]
> Fetched 2141 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install python-scrapy-djangoitem build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-python-scrapy-djangoitem-dummy : Depends: 
> python3-scrapy but it is not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/2017/08/07/python-scrapy-djangoitem_1.1.1-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#871387: qupzilla: FTBFS: build-dependency not installable: qtwebengine5-dev

[Lucas Nussbaum]

Source: qupzilla
Version: 2.1.2~dfsg1-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), qtbase5-dev, qtchooser, qt5-qmake, 
> libqt5webkit5-dev, qtwebengine5-dev, qttools5-dev-tools, libxcb-util0-dev, 
> qtbase5-private-dev, qtscript5-dev, libqt5x11extras5-dev, libx11-dev, 
> libssl1.0-dev, kdelibs5-dev, libgnome-keyring-dev, libjs-jquery, 
> libjs-jquery-ui
> Filtered Build-Depends: debhelper (>= 9), qtbase5-dev, qtchooser, qt5-qmake, 
> libqt5webkit5-dev, qtwebengine5-dev, qttools5-dev-tools, libxcb-util0-dev, 
> qtbase5-private-dev, qtscript5-dev, libqt5x11extras5-dev, libx11-dev, 
> libssl1.0-dev, kdelibs5-dev, libgnome-keyring-dev, libjs-jquery, 
> libjs-jquery-ui
> dpkg-deb: building package 'sbuild-build-depends-qupzilla-dummy' in 
> '/<>/resolver-dAb3BH/apt_archive/sbuild-build-depends-qupzilla-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-qupzilla-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-dAb3BH/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-dAb3BH/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-dAb3BH/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-dAb3BH/apt_archive ./ Sources [611 B]
> Get:5 copy:/<>/resolver-dAb3BH/apt_archive ./ Packages [692 B]
> Fetched 2266 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install qupzilla build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-qupzilla-dummy : Depends: qtwebengine5-dev but it is 
> not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/qupzilla_2.1.2~dfsg1-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#871379: libpdl-stats-perl: FTBFS: build-dependency not installable: pdl (>= 1:2.016)

[Lucas Nussbaum]

Source: libpdl-stats-perl
Version: 0.75-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9.20120312~), libgsl-dev, pdl (>= 
> 1:2.016), perl
> Filtered Build-Depends: debhelper (>= 9.20120312~), libgsl-dev, pdl (>= 
> 1:2.016), perl
> dpkg-deb: building package 'sbuild-build-depends-libpdl-stats-perl-dummy' in 
> '/<>/resolver-vUSNcr/apt_archive/sbuild-build-depends-libpdl-stats-perl-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-libpdl-stats-perl-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-vUSNcr/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-vUSNcr/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-vUSNcr/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-vUSNcr/apt_archive ./ Sources [524 B]
> Get:5 copy:/<>/resolver-vUSNcr/apt_archive ./ Packages [605 B]
> Fetched 2092 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install libpdl-stats-perl build dependencies (apt-based resolver)
> -
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-libpdl-stats-perl-dummy : Depends: pdl (>= 1:2.016) but 
> it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/libpdl-stats-perl_0.75-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#871384: redmine: FTBFS: build-dependency not installable: ruby-roadie-rails

[Lucas Nussbaum]

Source: redmine
Version: 3.3.1-4
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: dbconfig-common, debhelper (>= 9), ruby | 
> ruby-interpreter, ruby-actionpack-action-caching, ruby-actionpack-xml-parser, 
> ruby-bundler, ruby-coderay (>= 1.0.6), ruby-i18n (>= 0.6.9-1~), 
> ruby-jquery-rails (>= 4.0.5), ruby-mimemagic, ruby-mime-types (>= 1.25), 
> ruby-net-ldap (>= 0.3.1), ruby-openid, ruby-protected-attributes, ruby-rack 
> (>= 1.4.5~), ruby-rack-openid, ruby-rails (>= 2:4.2.5), ruby-rails-observers, 
> ruby-rbpdf, ruby-redcarpet, ruby-request-store, ruby-rmagick, 
> ruby-roadie-rails, po-debconf
> Filtered Build-Depends: dbconfig-common, debhelper (>= 9), ruby, 
> ruby-actionpack-action-caching, ruby-actionpack-xml-parser, ruby-bundler, 
> ruby-coderay (>= 1.0.6), ruby-i18n (>= 0.6.9-1~), ruby-jquery-rails (>= 
> 4.0.5), ruby-mimemagic, ruby-mime-types (>= 1.25), ruby-net-ldap (>= 0.3.1), 
> ruby-openid, ruby-protected-attributes, ruby-rack (>= 1.4.5~), 
> ruby-rack-openid, ruby-rails (>= 2:4.2.5), ruby-rails-observers, ruby-rbpdf, 
> ruby-redcarpet, ruby-request-store, ruby-rmagick, ruby-roadie-rails, 
> po-debconf
> dpkg-deb: building package 'sbuild-build-depends-redmine-dummy' in 
> '/<>/resolver-4VQuge/apt_archive/sbuild-build-depends-redmine-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-redmine-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-4VQuge/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-4VQuge/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-4VQuge/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-4VQuge/apt_archive ./ Sources [722 B]
> Get:5 copy:/<>/resolver-4VQuge/apt_archive ./ Packages [781 B]
> Fetched 2466 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install redmine build dependencies (apt-based resolver)
> ---
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-redmine-dummy : Depends: ruby-roadie-rails but it is 
> not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/redmine_3.3.1-4_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#871383: ruby-gsl: FTBFS: build-dependency not installable: libtamuanova-dev

[Lucas Nussbaum]

Source: ruby-gsl
Version: 2.1.0.1+dfsg1-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9~), gem2deb, libgsl-dev (>= 2.0), 
> libtamuanova-dev, plotutils, quilt, ruby-narray
> Filtered Build-Depends: debhelper (>= 9~), gem2deb, libgsl-dev (>= 2.0), 
> libtamuanova-dev, plotutils, quilt, ruby-narray
> dpkg-deb: building package 'sbuild-build-depends-ruby-gsl-dummy' in 
> '/<>/resolver-ueqn3b/apt_archive/sbuild-build-depends-ruby-gsl-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-ruby-gsl-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-ueqn3b/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-ueqn3b/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-ueqn3b/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-ueqn3b/apt_archive ./ Sources [540 B]
> Get:5 copy:/<>/resolver-ueqn3b/apt_archive ./ Packages [622 B]
> Fetched 2125 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install ruby-gsl build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-ruby-gsl-dummy : Depends: libtamuanova-dev but it is 
> not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/ruby-gsl_2.1.0.1+dfsg1-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#871380: algobox: FTBFS: build-dependency not installable: qtwebengine5-dev

[Lucas Nussbaum]

Source: algobox
Version: 1.0.1+dfsg-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), qtbase5-dev, qtwebengine5-dev
> Filtered Build-Depends: debhelper (>= 9), qtbase5-dev, qtwebengine5-dev
> dpkg-deb: building package 'sbuild-build-depends-algobox-dummy' in 
> '/<>/resolver-MDbFki/apt_archive/sbuild-build-depends-algobox-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-algobox-dummy 
> sbuild-build-depends-core-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-MDbFki/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-MDbFki/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-MDbFki/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-MDbFki/apt_archive ./ Sources [506 B]
> Get:5 copy:/<>/resolver-MDbFki/apt_archive ./ Packages [587 B]
> Fetched 2056 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install algobox build dependencies (apt-based resolver)
> ---
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-algobox-dummy : Depends: qtwebengine5-dev but it is not 
> going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/algobox_1.0.1+dfsg-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#871378: ruby-roadie-rails: FTBFS: build-dependency not installable: ruby-roadie (>= 3.1)

[Lucas Nussbaum]

Source: ruby-roadie-rails
Version: 1.1.0-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9~), gem2deb, rake, rails, ruby-railties 
> (<< 2:4.3), ruby-railties (>= 2:3.0), ruby-roadie (>= 3.1), ruby-rspec, 
> ruby-rspec-collection-matchers, ruby-sass-rails
> Filtered Build-Depends: debhelper (>= 9~), gem2deb, rake, rails, 
> ruby-railties (<< 2:4.3), ruby-railties (>= 2:3.0), ruby-roadie (>= 3.1), 
> ruby-rspec, ruby-rspec-collection-matchers, ruby-sass-rails
> dpkg-deb: building package 'sbuild-build-depends-ruby-roadie-rails-dummy' in 
> '/<>/resolver-MRv34j/apt_archive/sbuild-build-depends-ruby-roadie-rails-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-ruby-roadie-rails-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-MRv34j/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-MRv34j/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-MRv34j/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-MRv34j/apt_archive ./ Sources [569 B]
> Get:5 copy:/<>/resolver-MRv34j/apt_archive ./ Packages [652 B]
> Fetched 2184 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install ruby-roadie-rails build dependencies (apt-based resolver)
> -
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-ruby-roadie-rails-dummy : Depends: ruby-roadie (>= 3.1) 
> but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/ruby-roadie-rails_1.1.0-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#871382: 3depict: FTBFS: unsatisfiable build-dependencies: libgsl-dev, libmgl-dev (>= 2.0)

[Lucas Nussbaum]

Source: 3depict
Version: 0.0.19-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dh-autoreconf (>= 9), dpkg-dev (>= 
> 1.16.1~), libgl1-mesa-dev | libgl-dev, libpng-dev | libpng15-dev, 
> libqhull-dev, libwxgtk3.0-dev, libgsl-dev, libftgl-dev, libxml2-dev, 
> libmgl-dev (>= 2.0), libvigraimpex-dev, automake, autotools-dev, pkg-config
> Filtered Build-Depends: debhelper (>= 9), dh-autoreconf (>= 9), dpkg-dev (>= 
> 1.16.1~), libgl1-mesa-dev, libpng-dev, libqhull-dev, libwxgtk3.0-dev, 
> libgsl-dev, libftgl-dev, libxml2-dev, libmgl-dev (>= 2.0), libvigraimpex-dev, 
> automake, autotools-dev, pkg-config
> dpkg-deb: building package 'sbuild-build-depends-3depict-dummy' in 
> '/<>/resolver-YpzjUj/apt_archive/sbuild-build-depends-3depict-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-3depict-dummy 
> sbuild-build-depends-core-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-YpzjUj/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-YpzjUj/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-YpzjUj/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-YpzjUj/apt_archive ./ Sources [601 B]
> Get:5 copy:/<>/resolver-YpzjUj/apt_archive ./ Packages [666 B]
> Fetched 2230 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install 3depict build dependencies (apt-based resolver)
> ---
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-3depict-dummy : Depends: libgsl-dev but it is not going 
> to be installed
>   Depends: libmgl-dev (>= 2.0) but it is 
> not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/3depict_0.0.19-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#871381: gyoto: FTBFS: build-dependency not installable: liblorene-dev

[Lucas Nussbaum]

Source: gyoto
Version: 1.2.0-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9~), yorick-dev, yorick-yutils, 
> libxerces-c-dev, libcfitsio-dev, libudunits2-dev, automake, libboost-dev (>= 
> 1.53.1), libboost-mpi-dev, dh-autoreconf, mpi-default-dev, dh-python, 
> python-all-dev (>= 2.6.6-3~), python-setuptools, python3-all-dev, 
> python3-setuptools, swig3.0, python-numpy, python3-numpy, doxygen, dh-exec 
> (>= 0.3), pkg-config, liblorene-dev, lorene-codes-src, gfortran, 
> doxygen-latex, texlive-bibtex-extra, texlive-latex-base, texlive-lang-french, 
> tipa
> Filtered Build-Depends: debhelper (>= 9~), yorick-dev, yorick-yutils, 
> libxerces-c-dev, libcfitsio-dev, libudunits2-dev, automake, libboost-dev (>= 
> 1.53.1), libboost-mpi-dev, dh-autoreconf, mpi-default-dev, dh-python, 
> python-all-dev (>= 2.6.6-3~), python-setuptools, python3-all-dev, 
> python3-setuptools, swig3.0, python-numpy, python3-numpy, doxygen, dh-exec 
> (>= 0.3), pkg-config, liblorene-dev, lorene-codes-src, gfortran, 
> doxygen-latex, texlive-bibtex-extra, texlive-latex-base, texlive-lang-french, 
> tipa
> dpkg-deb: building package 'sbuild-build-depends-gyoto-dummy' in 
> '/<>/resolver-2D0FNP/apt_archive/sbuild-build-depends-gyoto-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-gyoto-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-2D0FNP/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-2D0FNP/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-2D0FNP/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-2D0FNP/apt_archive ./ Sources [717 B]
> Get:5 copy:/<>/resolver-2D0FNP/apt_archive ./ Packages [786 B]
> Fetched 2466 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install gyoto build dependencies (apt-based resolver)
> -
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-gyoto-dummy : Depends: liblorene-dev but it is not 
> going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/gyoto_1.2.0-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#870698: [Debian-science-sagemath] Possible fix for fplll/fpylll issue with default strategy path

[Ximin Luo]

Ximin Luo:
> Julien Puydt:
>> Hi,
>>
>> I just pushed to fplll's Debian git repository a tentative 5.1.0-3 which
>> would fix the recently reported issue with fpylll : I rewrote the patch
>> for the default strategies path changes.
>>
>> I'm a bit at loss on how to check if that really fixes anything : I
>> tried to build fpylll (success), but then trying to "import fpylll" in
>> python gave:
>> RuntimeError: You must get the file local/bin/sage-maxima.lisp
>>
>> so I can't really test seriously...
>>
> 
> I can reproduce this, it works if you uninstall sage (but of course we have 
> to fix it properly).
> 
> The underlying issue is caused by the fact that Sage sets things like 
> SAGE_LOCAL outside of python itself, so that one gets e.g.:
> 
> $ python -c 'from sage.env import DOT_SAGE, SAGE_SCRIPTS_DIR; 
> print(SAGE_SCRIPTS_DIR)'
> $SAGE_LOCAL/bin
> $ sage -c 'from sage.env import DOT_SAGE, SAGE_SCRIPTS_DIR; 
> print(SAGE_SCRIPTS_DIR)'
> /usr/share/sagemath/bin
> 
> I would guess that this also affects upstream Sage, but perhaps the issue is 
> hidden somehow (Debian uses a different "sage-env" shell script).
> 

So for example this works, with sage installed:

$ SAGE_LOCAL=/usr SAGE_SCRIPTS_DIR=/usr/share/sagemath/bin python -c "import 
fpylll"
# no errors, exit code 0

Now the question is, does Sage always expect that itself should be run via the 
"sage" program, with particular envvars set? 

If yes, then fpylll should run the "sage" version of itself after detecting the 
presence of these envvars - a simple "try: import sage; except ImportError" is 
not enough.

If no (i.e. "import sage" etc should work in a plain python program), then sage 
should put its own "sage-env" shell script logic, into the "sage.env" python 
module instead, so that it gets run properly when things like "from sage.env 
import *" are done by third-party libs/programs. (And we in Debian would patch 
this logic for Debian paths.)

In both cases, this should be documented somewhere upstream in the Sage source 
code / documentation.

François & Jeroen (and any other Sage devs here), what do you think? Shall I 
file an upstream trac ticket about this?

(In any case, I think the fplll/fpylll bug is fixed, and we can upload + close 
#870698).

X

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Bug#871377: pymia: FTBFS: build-dependency not installable: libmia-2.4-dev

[Lucas Nussbaum]

Source: pymia
Version: 0.1.9-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), pkg-config, python-all-dev, 
> python3-all-dev, python-numpy, python3-numpy, python-setuptools, 
> python3-setuptools, libmia-2.4-dev
> Filtered Build-Depends: debhelper (>= 9), pkg-config, python-all-dev, 
> python3-all-dev, python-numpy, python3-numpy, python-setuptools, 
> python3-setuptools, libmia-2.4-dev
> dpkg-deb: building package 'sbuild-build-depends-pymia-dummy' in 
> '/<>/resolver-mI6weo/apt_archive/sbuild-build-depends-pymia-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-pymia-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-mI6weo/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-mI6weo/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-mI6weo/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-mI6weo/apt_archive ./ Sources [536 B]
> Get:5 copy:/<>/resolver-mI6weo/apt_archive ./ Packages [620 B]
> Fetched 2119 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install pymia build dependencies (apt-based resolver)
> -
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-pymia-dummy : Depends: libmia-2.4-dev but it is not 
> going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/pymia_0.1.9-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#871376: qtiplot: FTBFS: build-dependency not installable: libtamuanova-dev (>= 0.2-4)

[Lucas Nussbaum]

Source: qtiplot
Version: 0.9.8.9-15
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dblatex, docbook-utils, doxygen, 
> libgsl-dev, zlib1g-dev, libpng-dev, libgl2ps-dev, libjs-jquery, 
> liborigin2-dev, libmuparser-dev, python-all-dev, python-qt4, python-qt4-dev, 
> python-sip-dev, libqt4-opengl-dev, libboost-thread-dev, libboost-system-dev, 
> libqtassistantclient-dev, libalglib-dev (>= 3.9.0), libtamuanova-dev (>= 
> 0.2-4), libqtexengine-dev, texlive-lang-european, texlive-lang-italian, 
> imagemagick
> Filtered Build-Depends: debhelper (>= 9), dblatex, docbook-utils, doxygen, 
> libgsl-dev, zlib1g-dev, libpng-dev, libgl2ps-dev, libjs-jquery, 
> liborigin2-dev, libmuparser-dev, python-all-dev, python-qt4, python-qt4-dev, 
> python-sip-dev, libqt4-opengl-dev, libboost-thread-dev, libboost-system-dev, 
> libqtassistantclient-dev, libalglib-dev (>= 3.9.0), libtamuanova-dev (>= 
> 0.2-4), libqtexengine-dev, texlive-lang-european, texlive-lang-italian, 
> imagemagick
> dpkg-deb: building package 'sbuild-build-depends-qtiplot-dummy' in 
> '/<>/resolver-Q9Zily/apt_archive/sbuild-build-depends-qtiplot-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-qtiplot-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-Q9Zily/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-Q9Zily/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-Q9Zily/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-Q9Zily/apt_archive ./ Sources [682 B]
> Get:5 copy:/<>/resolver-Q9Zily/apt_archive ./ Packages [761 B]
> Fetched 2406 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install qtiplot build dependencies (apt-based resolver)
> ---
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-qtiplot-dummy : Depends: libtamuanova-dev (>= 0.2-4) 
> but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/qtiplot_0.9.8.9-15_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#866696: src:python-pyeclib: FTBFS on mips64el due to test failures after rebuild with python3.6

[Ondrej Novy]

Hi,

I requested removal of mips64el [1]. This lib is not compatible with this
arch and it was built by mistake.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871054

-- 
Best regards
 Ondřej Nový

Email: n...@ondrej.org
PGP: 3D98 3C52 EB85 980C 46A5  6090 3573 1255 9D1E 064B

Bug#870698: [Debian-science-sagemath] Possible fix for fplll/fpylll issue with default strategy path

[Ximin Luo]

Julien Puydt:
> Hi,
> 
> I just pushed to fplll's Debian git repository a tentative 5.1.0-3 which
> would fix the recently reported issue with fpylll : I rewrote the patch
> for the default strategies path changes.
> 
> I'm a bit at loss on how to check if that really fixes anything : I
> tried to build fpylll (success), but then trying to "import fpylll" in
> python gave:
> RuntimeError: You must get the file local/bin/sage-maxima.lisp
> 
> so I can't really test seriously...
> 

I can reproduce this, it works if you uninstall sage (but of course we have to 
fix it properly).

The underlying issue is caused by the fact that Sage sets things like 
SAGE_LOCAL outside of python itself, so that one gets e.g.:

$ python -c 'from sage.env import DOT_SAGE, SAGE_SCRIPTS_DIR; 
print(SAGE_SCRIPTS_DIR)'
$SAGE_LOCAL/bin
$ sage -c 'from sage.env import DOT_SAGE, SAGE_SCRIPTS_DIR; 
print(SAGE_SCRIPTS_DIR)'
/usr/share/sagemath/bin

I would guess that this also affects upstream Sage, but perhaps the issue is 
hidden somehow (Debian uses a different "sage-env" shell script).

X

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git