date:20171021

Bug#779305: Package is NEW

2017-10-21 Thread Pirate Praveen

On Sun, 15 Oct 2017 17:19:48 +0200 Ross Gammon  wrote:
> Hi,
> 
> I have uploaded the package, and it is waiting in the NEW queue:
> https://ftp-master.debian.org/new.html

I'm trying to use node-bluebird in node-copy-webpack-plugin[1], but
getting this error when running tests.

[1]
https://anonscm.debian.org/cgit/pkg-javascript/node-copy-webpack-plugin.git

 1) apply function with glob in from can use a glob to move multiple
files to a non-root directory with name, hash and ext:

  AssertionError: expected { Object
(nested///binextension-d41d8c.bin,
nested/directory/directoryfile-22af64.txt, ...) } to have keys
'nested/binextension-d41d8c.bin', 'nested/file-22af64.txt',
'nested/directory/directoryfile-22af64.txt',
'nested/directory/nested/nestedfile-d41d8c.txt', and
'nested/noextension-d41d8c'
  + expected - actual

   [
  -  "nested///binextension-d41d8c.bin",
  -  "nested///file-22af64.txt",
  -  "nested///noextension-d41d8c",
  +  "nested/binextension-d41d8c.bin",
 "nested/directory/directoryfile-22af64.txt",
  -  "nested/directory/nested/nestedfile-d41d8c.txt"
  +  "nested/directory/nested/nestedfile-d41d8c.txt",
  +  "nested/file-22af64.txt",
  +  "nested/noextension-d41d8c"
   ]

  at /tmp/autopkgtest.k3ipWx/tree/compiled_tests/index.js:117:67
  at tryCatcher (/usr/lib/nodejs/bluebird/js/release/util.js:16:23)
  at Promise._settlePromiseFromHandler
(/usr/lib/nodejs/bluebird/js/release/promise.js:512:31)
  at Promise._settlePromise
(/usr/lib/nodejs/bluebird/js/release/promise.js:569:18)
  at Promise._settlePromise0
(/usr/lib/nodejs/bluebird/js/release/promise.js:614:10)
  at Promise._settlePromises
(/usr/lib/nodejs/bluebird/js/release/promise.js:693:18)
  at Async._drainQueue
(/usr/lib/nodejs/bluebird/js/release/async.js:133:16)
  at Async._drainQueues
(/usr/lib/nodejs/bluebird/js/release/async.js:143:10)
  at Immediate.Async.drainQueues
(/usr/lib/nodejs/bluebird/js/release/async.js:17:14)
  at runCallback (timers.js:672:20)
  at tryOnImmediate (timers.js:645:5)
  at processImmediate [as _immediateCallback] (timers.js:617:5)


  2) apply function with directory in from can move multiple files to a
non-root directory with name, hash and ext:

  AssertionError: expected { Object (nested///.dottedfile-79d39f,
nested/nested/nestedfile-d41d8c.txt, ...) } to have keys
'nested/.dottedfile-79d39f', 'nested/directoryfile-22af64.txt', and
'nested/nested/nestedfile-d41d8c.txt'
  + expected - actual

   [
  -  "nested///.dottedfile-79d39f",
  -  "nested///directoryfile-22af64.txt",
  +  "nested/.dottedfile-79d39f",
  +  "nested/directoryfile-22af64.txt",
 "nested/nested/nestedfile-d41d8c.txt"
   ]

  at /tmp/autopkgtest.k3ipWx/tree/compiled_tests/index.js:117:67
  at tryCatcher (/usr/lib/nodejs/bluebird/js/release/util.js:16:23)
  at Promise._settlePromiseFromHandler
(/usr/lib/nodejs/bluebird/js/release/promise.js:512:31)
  at Promise._settlePromise
(/usr/lib/nodejs/bluebird/js/release/promise.js:569:18)
  at Promise._settlePromise0
(/usr/lib/nodejs/bluebird/js/release/promise.js:614:10)
  at Promise._settlePromises
(/usr/lib/nodejs/bluebird/js/release/promise.js:693:18)
  at Async._drainQueue
(/usr/lib/nodejs/bluebird/js/release/async.js:133:16)
  at Async._drainQueues
(/usr/lib/nodejs/bluebird/js/release/async.js:143:10)
  at Immediate.Async.drainQueues
(/usr/lib/nodejs/bluebird/js/release/async.js:17:14)
  at runCallback (timers.js:672:20)
  at tryOnImmediate (timers.js:645:5)
  at processImmediate [as _immediateCallback] (timers.js:617:5)






signature.asc
Description: OpenPGP digital signature

Bug#879483: golang-github-ugorji-go-codec FTBFS: rm: cannot remove '/<>/debian//*/usr/share/gocode/src/github.com/ugorji/go/codec/prebuild.sh': No such file or directory

2017-10-21 Thread Adrian Bunk

Source: golang-github-ugorji-go-codec
Version: 0.0~git20171019.0.bdcc60b-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=golang-github-ugorji-go-codec=all=0.0~git20171019.0.bdcc60b-1=1508610038=0

...
dh_auto_install
cd obj-x86_64-linux-gnu && mkdir -p 
/<>/golang-github-ugorji-go-codec-0.0\~git20171019.0.bdcc60b/debian/golang-github-ugorji-go-codec-dev/usr
cd obj-x86_64-linux-gnu && cp -r bin 
/<>/golang-github-ugorji-go-codec-0.0\~git20171019.0.bdcc60b/debian/golang-github-ugorji-go-codec-dev/usr
cd obj-x86_64-linux-gnu && mkdir -p 
/<>/golang-github-ugorji-go-codec-0.0\~git20171019.0.bdcc60b/debian/golang-github-ugorji-go-codec-dev/usr/share/gocode/src/github.com/ugorji/go
cd obj-x86_64-linux-gnu && cp -r -T src/github.com/ugorji/go 
/<>/golang-github-ugorji-go-codec-0.0\~git20171019.0.bdcc60b/debian/golang-github-ugorji-go-codec-dev/usr/share/gocode/src/github.com/ugorji/go
rm -rf --verbose /<>/debian//*/usr/bin
removed 
'/<>/debian//golang-github-ugorji-go-codec-dev/usr/bin/codecgen'
removed directory 
'/<>/debian//golang-github-ugorji-go-codec-dev/usr/bin'
rm /<>/debian//*/usr/share/gocode/src/github.com/ugorji/go/LICENSE
rm 
/<>/debian//*/usr/share/gocode/src/github.com/ugorji/go/codec/prebuild.sh
rm: cannot remove 
'/<>/debian//*/usr/share/gocode/src/github.com/ugorji/go/codec/prebuild.sh':
 No such file or directory
debian/rules:13: recipe for target 'override_dh_auto_install' failed
make[1]: *** [override_dh_auto_install] Error 1

Bug#879482: yt FTBFS on 32bit: test failures

2017-10-21 Thread Adrian Bunk

Source: yt
Version: 3.4.0-2
Severity: serious

https://buildd.debian.org/status/package.php?p=yt

...
==
ERROR: yt.utilities.lib.tests.test_alt_ray_tracers.test_cylindrical_ray_trace
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File "/<>/yt/utilities/lib/tests/test_alt_ray_tracers.py", line 
65, in test_cylindrical_ray_trace
t, s, rztheta, inds = cylindrical_ray_trace(p1, p2, left_grid, right_grid)
  File "yt/utilities/lib/alt_ray_tracers.pyx", line 204, in 
yt.utilities.lib.alt_ray_tracers.cylindrical_ray_trace
tsect, tinds = ret[0], ret[1].astype('int64')
ValueError: Item size of buffer (8 bytes) does not match size of 'int_t' (4 
bytes)

==
ERROR: test_points_vr 
(yt.visualization.volume_rendering.tests.test_points.PointsVRTest)
--
Traceback (most recent call last):
  File 
"/<>/yt/visualization/volume_rendering/tests/test_points.py", line 
75, in test_points_vr
im = sc.render()
  File "/<>/yt/visualization/volume_rendering/scene.py", line 229, 
in render
bmp = self.composite(camera=camera)
  File "/<>/yt/visualization/volume_rendering/scene.py", line 529, 
in composite
source.render(camera, zbuffer=opaque)
  File "/<>/yt/visualization/volume_rendering/render_source.py", 
line 893, in render
zpoints(empty, z, px, py, dz, self.colors, self.radii, self.color_stride)
  File "yt/utilities/lib/misc_utilities.pyx", line 440, in 
yt.utilities.lib.misc_utilities.zpoints
idx = np.argsort(zs)
ValueError: Buffer dtype mismatch, expected 'int64_t' but got 'int'

--
Ran 1161 tests in 1361.004s

FAILED (errors=2)
debian/rules:37: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#879481: ITP: node-copy-webpack-plugin -- Copy files and directories in webpack

2017-10-21 Thread Pirate Praveen

Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-copy-webpack-plugin
  Version : 4.2.0
  Upstream Author : Len Boyette
* URL : https://github.com/webpack-contrib/copy-webpack-plugin
* License : Expat
  Programming Lang: JavaScript
  Description : Copy files and directories in webpack

 This webpack plugin copies individual files or entire directories to
the build
 directory.
 .
 Webpack takes code targeted at node.js and makes it run in the browser.
 Node.js comes with API of its own that is not available in the browsers.
 Webpack exposes this code to programs that are unaware they are running
in a
 browser.
 .
 Node.js is an event-based server-side JavaScript engine.

Dependency of gitlab 9.5



signature.asc
Description: OpenPGP digital signature

Bug#879177: Remmina: Not connecting to Windows 7 using RDP connection

2017-10-21 Thread Ali Sayed


Hi Matteo -

Thanks for responding.

i) I installed the "sid" package on "stretch" only to demonstrate that 
the latest Remmina actually works on the Stable release.  It can't 
really be that bad and I can always remove it without any serious issues.


ii) All that other "mess" is actually needed by "Vinagre" the other RDP 
connection client that actually works and allows me to get work done, 
since I really have to connect to Windows systems all day long, as much 
as I dis-like them ;)



iii) And lastly, now that I have reported this issue, I would really 
hope that the package maintainer would do some trouble shooting and 
provide a fix, I am really not qualified to debug this issue.  I really 
would like to get back to using Remmina, and was happy to see it back in 
"testing" except that its not quite working for me.



thanks

-ali




On 10/21/2017 06:26 AM, Matteo F. Vescovi wrote:


Hi!

Il 21/ott/2017 04:51, "Ali Sayed" > ha scritto:

>
> Hi There -
>
>
> Here is some additional details, as you had requested.
>
>
> On Debian Stretch, I installed Remmina from the "sid" repo : apt-get 
-t sid install remmina, and it runs fine:

>
> uname -a
> Linux teal 4.9.0-4-amd64 #1 SMP Debian 4.9.51-1 (2017-09-28) x86_64 
GNU/Linux

>
> ii  remmina 1.2.0-rcgit.21-1
> ii  remmina-common 1.2.0-rcgit.21-1
> ii  remmina-plugin-rdp:amd64 1.2.0-rcgit.21-1
> ii  remmina-plugin-vnc:amd64 1.2.0-rcgit.21-1
> ii  libfreerdp-client2-2:amd64 2.0.0~git20170725.1.1648deb+dfsg1-4
> ii  libfreerdp2-2:amd64 2.0.0~git20170725.1.1648deb+dfsg1-4

But you shouldn't. Remmina is on its way to enter stretch-backports.
Please avoid using unstable/sid packages in a stretch installation.
Any bug opened ona similar environment will be closed immediately.

> On Debian Buster, I installed Remmina from the "buster" repo, and 
its NOT CONNECTING !

>
> uname -a
> Linux blue 4.13.0-1-amd64 #1 SMP Debian 4.13.4-2 (2017-10-15) x86_64 
GNU/Linux

>
> ii  remmina 1.2.0-rcgit.21-1
> ii  remmina-common 1.2.0-rcgit.21-1
> ii  remmina-plugin-rdp:amd64 1.2.0-rcgit.21-1
> ii  remmina-plugin-vnc:amd64 1.2.0-rcgit.21-1
> ii  remmina-plugin-xdmcp:amd64 1.2.0-rcgit.21-1
> ii  libfreerdp-cache1.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-15
> ii  libfreerdp-client1.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-15
> ii  libfreerdp-client2-2:amd64 2.0.0~git20170725.1.1648deb+dfsg1-4
> ii  libfreerdp-codec1.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-15
> ii  libfreerdp-common1.1.0:amd64 1.1.0~git20140921.1.440916e+dfsg1-15
> ii  libfreerdp-core1.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-15
> ii  libfreerdp-crypto1.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-15
> ii  libfreerdp-gdi1.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-15
> ii  libfreerdp-locale1.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-15
> ii  libfreerdp-plugins-standard:amd64 
1.1.0~git20140921.1.440916e+dfsg1-15

> ii  libfreerdp-primitives1.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-15
> ii  libfreerdp-utils1.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-15
> ii  libfreerdp2-2:amd64 2.0.0~git20170725.1.1648deb+dfsg1-4

Why on earth do you have all that mess installed?
Could you please uninstall all the old freerdp1 packages, uninstall 
remmina and its dependencies and reinstall remmina again without 
mixing suites?

Thanks.

Cheers.

mfv

Bug#879480: ITP: node-mississippi -- collection of useful streams

2017-10-21 Thread Pirate Praveen

Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-mississippi
  Version : 1.3.0
  Upstream Author : max ogden
* URL : https://github.com/maxogden/mississippi#readme
* License : BSD-2-Clause
  Programming Lang: JavaScript
  Description : collection of useful streams

 This modules is a collection of useful stream utility modules. Learn
how the
 modules work using this and then pick the ones you want and use them
 individually.
 .
 The goal of the modules included in mississippi is to make working with
 streams easy without sacrificing speed, error handling or composability.
 .
 Node.js is an event-based server-side JavaScript engine.

Dependency of npm 5.x



signature.asc
Description: OpenPGP digital signature

Bug#879479: indexed-gzip: FTBFS on hurd-i386: self.base.flush not implemented

2017-10-21 Thread Aaron M. Ucko

Source: indexed-gzip
Version: 0.6.1-1
Severity: important
Tags: upstream
Justification: fails to build from source
User: debian-h...@lists.debian.org

Builds of indexed-gzip continue to fail on hurd-i386 (admittedly not a
release architecture) even with #861463 fixed.

https://buildd.debian.org/status/fetch.php?pkg=indexed-gzip=hurd-i386=0.6.1-1=1508582420=0

reports the overall statistics

  >  3 failed, 6 passed, 23 error in 35.05 seconds 
=

where the errors typically (always?) boil down to

  if self.base is not None and hasattr(self.base, 'flush'):
  >   self.base.flush()
  E   error: [Errno 1073741902] Function not implemented
  
  /usr/lib/python2.7/dist-packages/numpy/core/memmap.py:317: error

Could you please take a look?  FTR, 1073741902 is 0x404e, whose
low bits amount to 78 decimal.

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#879259: python-lupa FTBFS on ppc64el: test_coroutine_sets_callback_debug_hook_nowrap (lupa.tests.test.TestLuaCoroutinesWithDebugHooks) ... Segmentation fault

2017-10-21 Thread Aaron M. Ucko

Source: python-lupa
Followup-For: Bug #879259
User: debian-powe...@lists.debian.org

FTR, this same error also occurs on the big-endian non-release variant ppc64.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#879478: debhelper: dh_testroot regression: relies on debian/control

2017-10-21 Thread Cyril Brulebois

Package: debhelper
Version: 10.10
Severity: serious
Tags: d-i
Justification: triggers FTBFS

[ Please keep both debian-boot@ and myself in the loop, thanks. ]

Hi,

debian-installer uses compat 7, a build/ directory, and its daily-build
script is started from this directory. Makefiles use dh_testroot from
that directory, and starting with 10.10, the build is broken because of:
| dh_testroot: "debian/control" not found. Are you sure you are in the correct 
directory?

The changes were obvious since 10.9.2 (known good), but I've confirmed
anyway (through bisection) that it's caused by:
| commit 087be1a300581b989aa38227693a8a6f112408f9 (refs/bisect/bad)
| Author: Niels Thykier 
| Date:   Sat Sep 16 14:51:53 2017 +
| 
| Add minimal R³ support for debhelper
| 
| Signed-off-by: Niels Thykier 

It seems to me that's due to the getpackages call addition, but I don't
think it's reasonable for debhelper to break compat 7 this way. Also,
even if one might object d-i is abusing dh_testroot (or using it
incorrectly), its documented purpose is:
| dh_testroot simply checks to see if you are root. If not, it exits
| with an error. Debian packages must be built as root, though you can
| use fakeroot(1)


KiBi.

Bug#879475: php-igbinary: Please recompile to support php7.1

2017-10-21 Thread anomie

Package: php-igbinary
Version: 2.0.1-1

The package does not contain the shared library compiled for php 7.1,
only for php 7.0. Simply recompiling it locally with dpkg-buildpackage
produces a package that contains the necessary shared library and other
infrastructure, and seems to function correctly.

Bug#879477: php-redis: Please recompile to support php7.1

2017-10-21 Thread anomie

Package: php-redis
Version: 3.1.2-1

The package does not contain the shared library compiled for php 7.1,
only for php 7.0. Simply recompiling it locally with dpkg-buildpackage
produces a package that contains the necessary shared library and other
infrastructure, and seems to function correctly.

Bug#879476: php-msgpack: Please recompile to support php7.1

2017-10-21 Thread anomie

Package: php-msgpack
Version: 2.0.2+0.5.7-1

The package does not contain the shared library compiled for php 7.1,
only for php 7.0. Simply recompiling it locally with dpkg-buildpackage
produces a package that contains the necessary shared library and other
infrastructure, and seems to function correctly.

Bug#878491: Pending fixes for bugs in the fonts-hosny-amiri package

2017-10-21 Thread pkg-fonts-devel

tag 878491 + pending
thanks

Some bugs in the fonts-hosny-amiri package are closed in revision
c3a090fe345f807b87750622bd81e2956935e668 in branch 'master' by
أحمد المحمودي (Ahmed El-Mahmoudy)

The full diff can be seen at
http://anonscm.debian.org/gitweb/?p=pkg-fonts/fonts-hosny-amiri.git;a=commitdiff;h=c3a090f

Commit message:

Remove transitional package

Closes: #878491

Bug#879268: btrbk: Failed to parse subvolume list

2017-10-21 Thread Nicholas D Steeves

Control: tags -1 upstream fixed-upstream

On Sat, Oct 21, 2017 at 03:47:32PM +0530, Ritesh Raj Sarraf wrote:
> 
> rrs@priyasi:~$ sudo btrbk list snapshots
> ERROR: Failed to parse subvolume list (unsupported btrfs-progs) for: 
> /media/BTRFS
> WARNING: Skipping volume "/media/BTRFS": Failed to fetch subvolume detail
> source_host  source_subvol  snapshot_subvol  status  target_host  
> target_subvol
[...]
> I noticed this today. My guess is that it may have been triggered
> because I recently switched back to my custom kernels. Is it really that
> tightly dependent on the Debian kernels ?
> Or maybe it is just another bug ?

Btrbk bug, not a kernel bug:
https://github.com/digint/btrbk/issues/192

Btrfs-progs 4.13.2->4.13.3 is a patch-level bump, so the fix in
btrbk-0.26.0 (not packaged yet) should work.

Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#879466: Debian mirror debian.uchicago.edu: fails to finish update run

2017-10-21 Thread Brent Busby

Peter Palfrader  writes:

> We should get proper syncing back soon, and ideally also fix ftpsync
> such that it just works for everyone, including you.  I don't think
> downgrading is necessart just yet.
>
>> Here is my most recent ftpsync log:
>> Oct 21 16:17:14 punk ftpsync[52281]: Latest recorded rsync transfer
>> speed: 867 KB/s
>
> After that, it tries to write the tracefile and this seems failed.
>
> It seems it failed while writing the new tracefile.  It ends with
> writing some log line from cleanup() into the trace file [1].
>
> It wrote Trigger:, but never wrote any Architectures: or related
> information, suggesting it fell over in that part of the code:
>
> |   if [[ ${INFO_TRIGGER:-} ]]; then
> |   echo "Trigger: ${INFO_TRIGGER}"
> |   fi
> |
> |   if [[ -d ${TO}/dists ]]; then
> |   ARCH=$(find ${TO}/dists \( -name 'Packages.*' -o -name 
> 'Sources.*' \) -printf '%h\n' 2>/dev/null |
> |   sed -Ene 's#.*/binary-([^/]+)$#\1#p; s#.*/(source)$#\1#p' | 
> sort -u | tr '\n' ' ')
> |   if [[ $ARCH ]]; then
> |   echo "Architectures: ${ARCH}"
> |   fi
> |   fi
> |   if [[ ${ARCH_INCLUDE} ]]; then
> |   echo "Architectures-Configuration: INCLUDE $(tr ' ' '\n' <<< 
> ${ARCH_INCLUDE} | sort -u | tr '\n' ' ')"
> |   elif [[ ${ARCH_EXCLUDE} ]]; then
> |   echo "Architectures-Configuration: EXCLUDE $(tr ' ' '\n' <<< 
> ${ARCH_EXCLUDE} | sort -u | tr '\n' ' ')"
> |   else
> |   echo "Architectures-Configuration: ALL"
> |   fi
> |   echo "Upstream-mirror: ${RSYNC_HOST}"
> |   echo "Rsync-Transport: ${RSYNC_TRANSPORT}"
>
> ...
>
> Can you tell us more about your environment?  Do you have find/sed
> variants we did not test with?

We're running in a FreeBSD jail.  The GNU versions of both the findutils
and sed are available as installable FreeBSD packages, but to keep them
out of the way of the base system counterparts, they get installed as
gfind and gsed.  I have these packages installed now, but it won't use
them unless the binaries are called by those names.

On our site, running 'uname' with no options returns "FreeBSD".  That
will allow for a testable condition in the script if you want to have
ftpsync check for that.

I haven't experimented with it, but I'm almost certain it's BSD sed
that's breaking it.  The only difference between the two finds that ever
affects my daily usage is that GNU find seems to just default to your
current directory if you don't specify path(s) to search in, and in BSD
find, at least one path is required to run.  It doesn't look like the
code above would break any of that, since I don't see find being invoked
with no path anywhere here.

BSD sed on the other hand has all kinds of uniqueness going on.  It's
very likely the problem could be fixed by calling gsed on FreeBSD sites,
and requiring that FreeBSD sites must have gsed.

-- 
+ Brent A. Busby +  "Controlling a laser
+ UNIX Systems Admin +   with Linux is crazy..."
+ University of Chicago  +
+ Physical Sciences Div. +  -- Linus Torvalds,
+ James Franck Institute + creator of Linux

Bug#865975: docker.io breaks (bridged) network for VMs

2017-10-21 Thread Alban Browaeys

Package: docker.io
Followup-For: Bug #865975


The FORWARD chain policy is set to DROP by docker since 1.13.

The verbose (-V) iptables output (which gives interfaces and packet counters) 
is:
# iptables -L -v -n
Chain INPUT (policy ACCEPT 281 packets, 14176 bytes)
 pkts bytes target prot opt in out source   destination

Chain FORWARD (policy DROP 0 packets, 0 bytes)
 pkts bytes target prot opt in out source   destination
0 0 DOCKER-ISOLATION  all  --  *  *   0.0.0.0/0
0.0.0.0/0
0 0 DOCKER all  --  *  docker0  0.0.0.0/00.0.0.0/0
0 0 ACCEPT all  --  *  docker0  0.0.0.0/00.0.0.0/0  
  ctstate RELATED,ESTABLISHED
0 0 ACCEPT all  --  docker0 !docker0  0.0.0.0/00.0.0.0/0
0 0 ACCEPT all  --  docker0 docker0  0.0.0.0/00.0.0.0/0

Chain OUTPUT (policy ACCEPT 225 packets, 27980 bytes)
 pkts bytes target prot opt in out source   destination

Chain DOCKER (1 references)
 pkts bytes target prot opt in out source   destination

Chain DOCKER-ISOLATION (1 references)
 pkts bytes target prot opt in out source   destination
0 0 RETURN all  --  *  *   0.0.0.0/00.0.0.0/0


I reproduced the network setup but not the KVM one.I cannot confirm
that forwarding is broken.

Upstream provides:

- a command line switch to docker daemon "--iptables=false"
or a config item in /etc/docker/daemon.json:
{
  "iptables": false
}

- upstream also tell to revert the FORWARD policy to ACCEPT byhand ...
but I tested and it stay so on docker restart (even stop and start).
If the box is rebooted the change is lost
as confirmed by 
https://docs.docker.com/engine/userguide/networking/default_network/container-communication/
"The iptables settings are lost when the system reboots. If you want the change 
to be permanent,
refer to your Linux distribution’s documentation."
Mind we cannot apply it from /etc/rc.local or anything boot related as it has 
to be applied
after docker is started ... 
with socket activation we activate docker daemon long after boot.



references:

- 
https://docs.docker.com/engine/userguide/networking/default_network/container-communication/
Container communication between hosts
For security reasons, Docker configures the iptables rules to prevent 
containers from forwarding traffic
from outside the host machine, on Linux hosts. Docker sets the default policy 
of the FORWARD chain to DROP.
(...)
Note: In Docker 1.12 and earlier, the default FORWARD chain policy was ACCEPT. 
When you upgrade
to Docker 1.13 or higher, this default is automatically changed for you.



- Also from 
https://docs.docker.com/engine/userguide/networking/default_network/container-communication/
Communication between containers
(...)
Docker will never make changes to your system iptables rules if you set 
--iptables=false when the daemon starts.
Otherwise the Docker server will add a default rule to the FORWARD chain with a 
blanket ACCEPT policy
if you retain the default --icc=true, or else will set the policy to DROP if 
--icc=false.



Best regards
Alban

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

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

Versions of packages docker.io depends on:
ii  adduser 3.116
ii  docker-containerd   0.2.3+git+docker1.13.1~ds1-1
ii  docker-runc 1.0.0~rc2+git+docker1.13.1~ds1-2
ii  golang-libnetwork   0.8.0-dev.2+git20170202.599.45b4086-3
ii  iptables1.6.1-2+b1
ii  libapparmor12.11.0-11
ii  libc6   2.24-17
ii  libdevmapper1.02.1  2:1.02.142-1
ii  libsqlite3-03.20.1-2
ii  libsystemd0 235-2
ii  lsb-base9.20170808

Versions of packages docker.io recommends:
ii  ca-certificates  20170717
ii  cgroupfs-mount   1.4
ii  git  1:2.15.0~rc1-1
ii  xz-utils 5.2.2-1.3

Versions of packages docker.io suggests:
ii  aufs-tools   1:4.1+20161219-1
ii  btrfs-progs  4.13.3-1
ii  debootstrap  1.0.91
pn  docker-doc   
ii  rinse3.2
pn  zfs-fuse | zfsutils  

-- no debconf information

Bug#876364: dovecot-sieve: Just discovered imap_sieve/sieve_imapsieve is not set up to work with virtual mailboxes.

2017-10-21 Thread Thurgood Angelou

Hey.

So I just tested this with a blank (0KB) sieve script. Apparently the
plugin crashes whenever it executes the BEFORE/AFTER function and when it
checks to see if the uid's are still the same.

Copying without the plugin (tested with telnet) works but copying with the
plugin causes the plugin to crash due to the BEFORE/AFTER function being
broken for virtual folders.

Just want to know what's the ETA for a fix if at possible. I don't know how
the thing works so I'm wondering if it's at all possible to fix this simple
thing...

On Thu, Sep 21, 2017 at 5:13 PM, Thurgood Angelou  wrote:

> Hi... The output of my doveconf -n is as folllows.
>
> # 2.2.32 (dfbe293d4): /etc/dovecot/dovecot.conf
> # Pigeonhole version 0.4.20 (7cd71ba)
> doveconf: Warning: /etc/dovecot/dovecot.conf line 105: Global setting
> mail_plugins won't change the setting inside an earlier filter at
> /etc/dovecot/conf.d/15-lda.conf line 47 (if this is intentional, avoid
> this warning by moving the global setting before
> /etc/dovecot/conf.d/15-lda.conf line 47)
> doveconf: Warning: /etc/dovecot/dovecot.conf line 105: Global setting
> mail_plugins won't change the setting inside an earlier filter at
> /etc/dovecot/conf.d/15-lda.conf line 47 (if this is intentional, avoid
> this warning by moving the global setting before
> /etc/dovecot/conf.d/15-lda.conf line 47)
> # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.2 ext4
> auth_default_realm = othersider92.com
> auth_mechanisms = plain login
> first_valid_uid = 100
> log_path = /var/log/dovecot.log
> mail_location = maildir:/var/mail/%d/%n
> mail_plugins = " virtual"
> managesieve_notify_capability = mailto
> managesieve_sieve_capability = fileinto reject envelope encoded-character
> vacation subaddress comparator-i;ascii-numeric relational regex imap4flags
> copy include variables body enotify environment mailbox date index ihave
> duplicate mime foreverypart extracttext imapsieve vnd.dovecot.imapsieve
> namespace inbox {
>   inbox = yes
>   location =
>   mailbox Drafts {
> auto = create
> special_use = \Drafts
>   }
>   mailbox Junk {
> auto = create
> autoexpunge = 1 weeks
> special_use = \Junk
>   }
>   mailbox Promotions {
> auto = subscribe
>   }
>   mailbox Sent {
> auto = create
> special_use = \Sent
>   }
>   mailbox Trash {
> auto = create
> autoexpunge = 30 days
> special_use = \Trash
>   }
>   prefix =
>   separator = /
>   type = private
> }
> namespace virtual {
>   disabled = yes
>   hidden = yes
>   list = no
>   location = virtual:/var/mail/virtual
>   prefix = virtual/
>   separator = /
>   type = private
> }
> passdb {
>   args = /etc/dovecot/dovecot-sql.conf.ext
>   driver = sql
> }
> plugin {
>   imapsieve_mailbox1_before = file:/etc/sieve/report-spam.sieve
>   imapsieve_mailbox1_causes = COPY
>   imapsieve_mailbox1_name = Junk
>   imapsieve_mailbox2_before = file:/etc/sieve/report-ham.sieve
>   imapsieve_mailbox2_causes = COPY
>   imapsieve_mailbox2_from = Junk
>   imapsieve_mailbox2_name = *
>   imapsieve_mailbox3_before = file:/etc/sieve/report-spam-promo.sieve
>   imapsieve_mailbox3_causes = COPY
>   imapsieve_mailbox3_name = Promotions
>   imapsieve_mailbox4_before = file:/etc/sieve/report-ham-promo.sieve
>   imapsieve_mailbox4_causes = COPY
>   imapsieve_mailbox4_from = Promotions
>   imapsieve_mailbox4_name = *
>   sieve = file:~/sieve;active=~/.dovecot.sieve
>   sieve_after = /etc/sieve/conf.d/after
>   sieve_before = /etc/sieve/conf.d/before
>   sieve_global_extensions = +editheader +vnd.dovecot.pipe
>   sieve_pipe_bin_dir = /usr/local/bin
>   sieve_plugins = sieve_extprograms sieve_imapsieve
> }
> protocols = imap lmtp
> service auth-worker {
>   user = vmail
> }
> service auth {
>   unix_listener /var/spool/postfix/private/auth {
> group = postfix
> mode = 0666
> user = postfix
>   }
>   unix_listener auth-userdb {
> mode = 0600
> user = vmail
>   }
>   user = dovecot
> }
> service imap-login {
>   inet_listener imap {
> port = 0
>   }
>   inet_listener imaps {
> port = 993
> ssl = yes
>   }
> }
> service lmtp {
>   unix_listener /var/spool/postfix/private/dovecot-lmtp {
> group = postfix
> mode = 0600
> user = postfix
>   }
> }
> ssl = required
> ssl_cert =  ssl_client_ca_dir = /etc/ssl/certs
> ssl_key =  # hidden, use -P to show it
> userdb {
>   args = uid=vmail gid=vmail home=/var/mail/%d/%n
>   driver = static
> }
> protocol lmtp {
>   info_log_path = /var/log/dovecot-lmtp.log
>   mail_plugins = " virtual"
> }
> protocol lda {
>   mail_plugins = " sieve virtual"
> }
> protocol imap {
>   mail_plugins = " virtual imap_sieve"
> }
>
> I hope this helps.
>
> On Thu, Sep 21, 2017 at 4:47 AM, Apollon Oikonomopoulos <
> apoi...@debian.org> wrote:
>
>> Control: tags -1 + moreinfo upstream
>>
>> [Forwarding this to the Dovecot mailing list, just in case someone can
>> help]
>>
>> Hi,
>>
>> Thanks for the report! See my comments inline.
>>
>> On 11:56

Bug#879474: quagga-bgpd: BGP session termination due to rather long AS paths in update messages

2017-10-21 Thread Christoph Biedl

Package: quagga-bgpd
Version: 1.1.1-3
Severity: important
Tags: security upstream

Dear Maintainer,

there is a longstanding bug in quagga where certain BGP update messages
cause a quagga bgpd to drop a session, possibly resulting in loss of
network connectivity.

Details:

Long paths in update messages are segmented in BGP, and the bug is in
the recalculation of the framing information if there are more than two
segments. The resulting data is invalid but will will be used for
redistribution. At least if the receiver is another quagga bgpd, that
message is rejected, eventually resulting in a BGP session termination.

The receiver's log (if written) contains an error message like
| BGP: 172.23.97.181: BGP type 2 length 3074 is too large, attribute total
length is 2069. attr_endp is 0x562feb368121. endp is 0x562feb367d2c
then.

So if a site's BGP peers all run quagga, that site will lose network
connectivity due to frequent session termination. Additionally, the
repeated initial full table transfer will result in a significantly
bigger network load, I've seen around 1 MByte/sec/link, compared to
usually less than one 1 kbyte/sec/link.

Such extremely long AS paths have occured in the global BGP table at
least four times since June. Last time started on Oct 13th around 20:43
UTC and lasted until the following week.

All versions of quagga in Debian are affected.

How to fix:

Kudos to Andreas Jaggi who identified the bug and provided a fix[1].
After some hours of work I was able to reproduce the issue and can
confirm this patch resolves the issues for all versions of quagga in
Debian (wheezy, jessie, stretch = buster = sid). Details about the
setup available upon request, it's just some stuff to write down.

In my opinion this is serious enough to justify a security upload. If
stable security disagrees, please fix this in the next stable point
release.

Regards,
Christoph

[1] https://lists.quagga.net/pipermail/quagga-dev/2017-September/033284.html

http://git.savannah.gnu.org/cgit/quagga.git/commit/?id=7a42b78be9a4108d98833069a88e6fddb9285008

signature.asc
Description: Digital signature

Bug#848193: Want "dgit clone RUNNING" or some such

2017-10-21 Thread Sean Whitton

Hello,

On Sat, Oct 21 2017, Michael Stapelberg wrote:

> Shameless plug: I just released pk4, see
> https://people.debian.org/~stapelberg//2017/10/21/pk4.html, which
> covers a large fraction of the described use-case, IIUC.

Cool!

> Possibly pk4’s -resolve_only option is of interest, with which we
> could re-use the pk4 resolving logic but then run dgit instead.

Yes.  We'd probably want dgit to do the unpack and git init, so it can
pass the right options to dpkg-source.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#879466: Debian mirror debian.uchicago.edu: fails to finish update run

2017-10-21 Thread Peter Palfrader

On Sat, 21 Oct 2017, Brent Busby wrote:

> Peter Palfrader  writes:
> 
> > It seems your mirror fails to finish its update run,
> > failing while building the new tracefile.
> >
> > Status: 
> > https://mirror-master.debian.org/status/mirror-info/debian.uchicago.edu.html
> >
> > Please investigate and if it's an ftpsync issue please let us know.
> 

> Our most recent ftpsync log, from about an hour ago, seems to complete
> successfully on both stages, and ends with returncode zero both times,
> despite the tracefile showing that it hasn't worked since the upgrade.
> 
> Is there some log I can increase the verbosity of that will give more
> information?  If it's imperative that we get syncing fixed immediately,
> I am sure reverting to 20120521 would do that since we've had to do it
> before, but I'd like to not do that because of the security issues that
> were recently announced.

We should get proper syncing back soon, and ideally also fix ftpsync
such that it just works for everyone, including you.  I don't think
downgrading is necessart just yet.

> Here is my most recent ftpsync log:
> Oct 21 16:17:14 punk ftpsync[52281]: Latest recorded rsync transfer speed: 
> 867 KB/s

After that, it tries to write the tracefile and this seems failed.

It seems it failed while writing the new tracefile.  It ends with
writing some log line from cleanup() into the trace file [1].

It wrote Trigger:, but never wrote any Architectures: or related
information, suggesting it fell over in that part of the code:

|   if [[ ${INFO_TRIGGER:-} ]]; then
|   echo "Trigger: ${INFO_TRIGGER}"
|   fi
|
|   if [[ -d ${TO}/dists ]]; then
|   ARCH=$(find ${TO}/dists \( -name 'Packages.*' -o -name 'Sources.*' 
\) -printf '%h\n' 2>/dev/null |
|   sed -Ene 's#.*/binary-([^/]+)$#\1#p; s#.*/(source)$#\1#p' | 
sort -u | tr '\n' ' ')
|   if [[ $ARCH ]]; then
|   echo "Architectures: ${ARCH}"
|   fi
|   fi
|   if [[ ${ARCH_INCLUDE} ]]; then
|   echo "Architectures-Configuration: INCLUDE $(tr ' ' '\n' <<< 
${ARCH_INCLUDE} | sort -u | tr '\n' ' ')"
|   elif [[ ${ARCH_EXCLUDE} ]]; then
|   echo "Architectures-Configuration: EXCLUDE $(tr ' ' '\n' <<< 
${ARCH_EXCLUDE} | sort -u | tr '\n' ' ')"
|   else
|   echo "Architectures-Configuration: ALL"
|   fi
|   echo "Upstream-mirror: ${RSYNC_HOST}"
|   echo "Rsync-Transport: ${RSYNC_TRANSPORT}"

...

Can you tell us more about your environment?  Do you have find/sed variants we 
did not test with?

Peter

1. The last line of
  http://debian.uchicago.edu/debian/project/trace/debian.uchicago.edu.new 
  currently is
  | Oct 21 16:17:14 punk ftpsync[52281]: Mirrorsync done

-- 
|  .''`.   ** Debian **
  Peter Palfrader   | : :' :  The  universal
 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/

Bug#879472: ITP: libqtdbustest -- Library for testing DBus interactions using Qt

2017-10-21 Thread Mike Gabriel

Package: wnpp
Severity: wishlist
Owner: Mike Gabriel 

* Package name: libqtdbustest
  Version : 0.2+bzr42
  Upstream Author : Pete Woods 
* URL : https://code.launchpad.net/libqtdbustest
* License : LGPL-3
  Programming Lang: C++
  Description : Library for testing DBus interactions using Qt

 Simple library for testing Qt based DBus services and clients.
 .
 The library also comes with a simple executable for running test
 scripts under a private DBus environment.
 .
 This package will be maintained under the umbrella of the Ayatana
 Packagers Team.

Bug#879251: Pending fixes for bugs in the apache-log4j1.2 package

2017-10-21 Thread pkg-java-maintainers

tag 879251 + pending
thanks

Some bugs in the apache-log4j1.2 package are closed in revision
6d062cdeaff21171a573eb0527f50d73db448d9a in branch 'master' by
Emmanuel Bourg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/apache-log4j1.2.git/commit/?id=6d062cd

Commit message:

No longer attempt to install the javadoc jar (Closes: #879251)

Bug#879471: src:varnish: 5.2 needs a SONAME version bump

2017-10-21 Thread Sebastian Harl

Package: src:varnish
Version: 5.2.0-1
Severity: serious
Justification: Policy 8.6.2

Hi,

version 5.2 of Varnish introduces a bunch of backward incompatible API
and ABI changes which require a SONAME version bump.

For example, types like VSC_point in /usr/include/varnish/vapi/vsc.h
have changed in incompatible ways (e.g. the 'section' field of the
struct has been removed). This is an incompatible API change causing
other packages to FTBFS (e.g. collectd). Anyway, that's up to those
other packages to fix in new versions.

More importantly, though, the ABI of the library has changed as well.
For example, the VSM_N_Arg symbol has been removed. This causes existing
programs / libraries linked against libvarnishapi1 to fail at runtime
when trying to load the library.

Cheers,
Sebastian

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

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



signature.asc
Description: Digital signature

1 2 3 4 >

1 - 100 of 332 matches

Mail list logo