Processed: Re: Bug#858736: xul-ext-gcontactsync: Depends on icedove or iceape but not thunderbird

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #858736 [xul-ext-gcontactsync] xul-ext-gcontactsync: Depends on icedove or 
iceape but not thunderbird
Severity set to 'serious' from 'normal'

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

Processed: Re: Bug#857792: icedove-bidiui needs to become thunderbird-bidiui

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #857792 [icedove-bidiui] icedove-bidiui needs to become thunderbird-bidiui
Severity set to 'serious' from 'normal'

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

Bug#880207: marked as done (e2fsprogs-l10n: copyright file missing)

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2018 06:19:03 +
with message-id 
and subject line Bug#880207: fixed in e2fsprogs 1.43.8-1
has caused the Debian Bug report #880207,
regarding e2fsprogs-l10n: copyright file missing
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
880207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880207
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: e2fsprogs-l10n
Version: 1.43.7-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package misses the copyright
file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

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

0m21.7s ERROR: WARN: Inadequate results from running adequate!
  e2fsprogs-l10n: missing-copyright-file /usr/share/doc/e2fsprogs-l10n/copyright

  MISSING COPYRIGHT FILE: /usr/share/doc/e2fsprogs-l10n/copyright
  # ls -lad /usr/share/doc/e2fsprogs-l10n
  drwxr-xr-x 2 root root 60 Oct 18 05:39 /usr/share/doc/e2fsprogs-l10n
  # ls -la /usr/share/doc/e2fsprogs-l10n/
  total 60
  drwxr-xr-x  2 root root60 Oct 18 05:39 .
  drwxr-xr-x 84 root root  1780 Oct 18 05:39 ..
  -rw-r--r--  1 root root 57976 Oct 16 05:20 changelog.Debian.gz


cheers,

Andreas


e2fsprogs-l10n_1.43.7-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: e2fsprogs
Source-Version: 1.43.8-1

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

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

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

Debian distribution maintenance software
pp.
Theodore Y. Ts'o  (supplier of updated e2fsprogs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 01 Jan 2018 19:44:41 -0500
Source: e2fsprogs
Binary: fuse2fs e2fsck-static e2fsprogs-l10n libcomerr2 comerr-dev libss2 
ss-dev e2fsprogs-udeb e2fslibs e2fslibs-dev e2fsprogs
Architecture: source
Version: 1.43.8-1
Distribution: unstable
Urgency: medium
Maintainer: Theodore Y. Ts'o 
Changed-By: Theodore Y. Ts'o 
Description:
 comerr-dev - common error description library - headers and static libraries
 e2fsck-static - statically-linked version of the ext2/ext3/ext4 filesystem 
checke
 e2fslibs   - ext2/ext3/ext4 file system libraries
 e2fslibs-dev - ext2/ext3/ext4 file system libraries - headers and static 
librari
 e2fsprogs  - ext2/ext3/ext4 file system utilities
 e2fsprogs-l10n - ext2/ext3/ext4 file system utilities - translations
 e2fsprogs-udeb - stripped-down versions of e2fsprogs, for debian-installer 
(udeb)
 fuse2fs- ext2 / ext3 / ext4 file system driver for FUSE
 libcomerr2 - common error description library
 libss2 - command-line interface parsing library
 ss-dev - command-line interface parsing library - headers and static libra
Closes: 879220 880207 880483 881408 881590 881591 883869
Changes:
 e2fsprogs (1.43.8-1) unstable; urgency=medium
 .
   * New upstream version
   * Fix a bug where updated bitmap checks might not be written to disk.
 (Closes: #883869)
   * Add missing byte swaps for newly added fields in the superbloc
   * Fix a potential use after free bug in e2fsck when fixing a corrupted
 root node in directory hash tree.
   * Fix a bug in e2fsck where a badly/maliciously corrupted superblock
 (which is not fixed due to the -n option, for example) can cause a
 floating point exception when printing the summary statistics.
 (Closes: #879220)
   * Fix debugfs's ncheck command so that it correctly prints the inode
 number when printing an error message.
   * Fix a bug in e2freefrag where it could print an incorrect free blocks
 count on a file system with the 64-bit block number feature.
   * Update the German, Serbian, Spanish, and Ukrainian translations.
   * Fix a bug where resize2fs's free blocks sanity check could fail with a
 false positive and refuse to check a file system with the 64-bit block
 number feature.
   * Fix and clarify various man pages and documentations.  Also fixed up
 some random usage texts that were incorrect.  

Bug#886093: Patch for #886093

[Joseph Nuthalapati]

Dear maintainer,

Please find the attached patch for the bug.

Submitted the same patch to the upstream.
Added appropriate headers to the patch for tracking the upstream bug.

-- 
Regards
Joseph Nuthalapati

From bdc803e185e1a7bb14892405a2c0c840ba6e0fe1 Mon Sep 17 00:00:00 2001
From: Joseph Nuthalapati 
Date: Tue, 19 Dec 2017 13:04:18 +0530
Bug-debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886093
Forwarded: https://github.com/asciimoo/searx/pull/1124
Reviewed-by: Sunil Mohan Adapa 
Subject: [PATCH] Make Python 3 able to read settings files with Unicode
 characters

SearX currently doesn't start up when run with Python 3 as it tries to parse the
settings.yml file with ASCII codecs.
There are similar problems with engines_languages.json and currencies.json
Python 3 requires that files with Unicode characters be read with a 'b' flag.
This also works with Python 2 and hence can be integrated into the main source
code.

Tested with the latest Python 3.6.4rc1 on Debian unstable.

Signed-off-by: Joseph Nuthalapati 
---
 searx/__init__.py | 2 +-
 searx/engines/__init__.py | 2 +-
 searx/engines/currency_convert.py | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/searx/__init__.py b/searx/__init__.py
index a57588c..84a377d 100644
--- a/searx/__init__.py
+++ b/searx/__init__.py
@@ -50,7 +50,7 @@ if not settings_path:
 raise Exception('settings.yml not found')
 
 # load settings
-with open(settings_path) as settings_yaml:
+with open(settings_path, 'rb') as settings_yaml:
 settings = load(settings_yaml)
 
 '''
diff --git a/searx/engines/__init__.py b/searx/engines/__init__.py
index 7a9cc56..bec8de3 100644
--- a/searx/engines/__init__.py
+++ b/searx/engines/__init__.py
@@ -36,7 +36,7 @@ engines = {}
 
 categories = {'general': []}
 
-languages = loads(open(engine_dir + '/../data/engines_languages.json').read())
+languages = loads(open(engine_dir + '/../data/engines_languages.json', 'rb').read())
 
 engine_shortcuts = {}
 engine_default_args = {'paging': False,
diff --git a/searx/engines/currency_convert.py b/searx/engines/currency_convert.py
index 1bb4e60..34a9af6 100644
--- a/searx/engines/currency_convert.py
+++ b/searx/engines/currency_convert.py
@@ -94,7 +94,7 @@ def load():
 global db
 
 current_dir = os.path.dirname(os.path.realpath(__file__))
-json_data = open(current_dir + "/../data/currencies.json").read()
+json_data = open(current_dir + "/../data/currencies.json", 'rb').read()
 
 db = json.loads(json_data)
 
-- 
2.15.1



signature.asc
Description: OpenPGP digital signature

Bug#886093: searx: Fails to start when using Python 3

[Joseph Nuthalapati]

Package: searx
Version: 0.13.1+dfsg1-3
Severity: grave


SearX currently doesn't start up when run with Python 3 as it tries to parse 
the settings.yml file with ASCII codecs. The file has a list of languages which 
are in Unicode characters.





signature.asc
Description: OpenPGP digital signature

Bug#866632: bibledit-gtk: depends on libwebkitgtk-1.0-0 which is deprecated

[Matthew A. Postiff]

  
  
Hi Jeremy, Roberto, Teus,

Thank you for your help. I have taken over the development on
  this project, though I will admit I'm not much of a developer :-)
  Thus what I say below may seem very unlearned. Any guidance you
  can provide will be received gratefully on my part.
I have managed to fix the configure.ac like so:
PKG_CHECK_MODULES(WEBKIT, webkit2gtk-4.0 >= 2.18.3,,...)
However, in the WEBKIT_LIBS in the Makefile, configure now
  includes -lgtk-3 -lgdk-3. Right now our package is running on
  gtk2, and I didn't anticipate upgrading both webkit and gtk at the
  same time. I was hoping to do webkit first, and then sometime
  later the gtk. Is that approach possible, or should I just bite
  the bullet now and upgrade both dependencies?
Thanks,

Matt

  

Bug#886075: gnome-mastermind: Depends on gconf

[Jeremy Bicha]

Source: gnome-mastermind
Version: 0.3.1-2
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs gconf
Tags: sid buster

Your package depends or build-depends on gconf, but gconf will be
removed from Debian soon.

gconf's last release was about 5 years ago. It has been replaced by
gsettings (provided in Debian by source glib2.0 )

References
--
https://developer.gnome.org/gio/stable/ch34.html
https://developer.gnome.org/gio/stable/GSettings.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#886065: gyrus: Depends on gconf

[Jeremy Bicha]

Source: gyrus
Version: 0.3.10-3
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs gconf
Tags: sid buster

Your package depends or build-depends on gconf, but gconf will be
removed from Debian soon.

gconf's last release was about 5 years ago. It has been replaced by
gsettings (provided in Debian by source glib2.0 )

References
--
https://developer.gnome.org/gio/stable/ch34.html
https://developer.gnome.org/gio/stable/GSettings.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885556: udeb uninstallability trend: worse (+20/-0)

[Don Armstrong]

On Mon, 01 Jan 2018, Don Armstrong wrote:
> On Mon, 01 Jan 2018, Cyril Brulebois wrote:
> > udeb uninstallability watcher  (2018-01-01):
> > > Newly-broken packages in testing
> > >   multipath-udeb   amd64 arm64 armel armhf i386 
> > > mips mips64el mipsel ppc64el s390x
> > >   partman-multipathamd64 arm64 armel armhf i386 
> > > mips mips64el mipsel ppc64el s390x
> > 
> > I'm wondering how this is possible with an RC bug filed against the
> > multipath-udeb udeb (#885556). For some reason, it's listed as found in
> > multipath-tools/0.7.4-2 on the BTS side, without a version graph; and
> > it isn't listed by tracker or by the old PTS. I'm suspecting there's
> > something fishy on the BTS side so britney didn't notice the RC bug
> > and let it migrate?
> 
> Yeah, this definitely looks like a BTS mistake. It seems to know that
> the right versions are in unstable, but they're not showing up on the
> graph.

OK. Found the issue. Apparently, packages in the */debian-installer
components were being skipped when the BTS was figuring out what was in
which distribution. I've fixed that now, and the versions database is
being updated with that information.

The underlying issue should show up as fixed once the version graph for
this bug looks sane. [Probably in another 10-20 minutes.]


-- 
Don Armstrong  https://www.donarmstrong.com

Every gun that is made, every warship launched, every rocket fired
signifies [...] a theft from those who hunger and are not fed, those
who are cold and are not clothed. This world in arms is not spending
money alone. It is spending the sweat of its laborers, the genius of
its scientists, the hopes of its children. [...] This is not a way of
life at all in any true sense. Under the cloud of threatening war, it
is humanity hanging from a cross of iron. [...] [I]s there no other
way the world may live?
 -- President Dwight D. Eisenhower, April 16, 1953

Processed: reassign 886049 to src:linux, severity of 886049 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 886049 src:linux 4.14.7-1
Bug #886049 [linux-image-4.14.0-2-amd64] [linux-image-4.14.0-2-amd64] Function 
g_file_copy() from libglib2.0-0 hangs when copying small files from CIFS-Share. 
This is relevant for Thunar filemanager.
Bug reassigned from package 'linux-image-4.14.0-2-amd64' to 'src:linux'.
No longer marked as found in versions 4.14.0-2-amd64.
Ignoring request to alter fixed versions of bug #886049 to the same values 
previously set
Bug #886049 [src:linux] [linux-image-4.14.0-2-amd64] Function g_file_copy() 
from libglib2.0-0 hangs when copying small files from CIFS-Share. This is 
relevant for Thunar filemanager.
Marked as found in versions linux/4.14.7-1.
> severity 886049 important
Bug #886049 [src:linux] [linux-image-4.14.0-2-amd64] Function g_file_copy() 
from libglib2.0-0 hangs when copying small files from CIFS-Share. This is 
relevant for Thunar filemanager.
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Processed: tagging 882066

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 882066 + fixed-upstream
Bug #882066 [ansible-lint] ansible-lint fails with ansible 2.4
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Processed: limit source to ktikz, tagging 874996, tagging 883501

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> limit source ktikz
Limiting to bugs with field 'source' containing at least one of 'ktikz'
Limit currently set to 'source':'ktikz'

> tags 874996 + pending
Bug #874996 [src:ktikz] [ktikz] Future Qt4 removal from Buster
Added tag(s) pending.
> tags 883501 + pending
Bug #883501 [src:ktikz] ktikz: depends on libpoppler-qt4 which is about to be 
removed
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#886063: libgnomecanvas: Don't release with Buster

[Jeremy Bicha]

Source: libgnomecanvas
Version: 2.30.3-3
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnomecanvas
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries.

libgnomecanvas is one of these unmaintained libraries.

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Processed: Re: Bug#883341: slic3r: Missing dependencies: wx-common, libopengl-perl, libwx-glcanvas-perl

[Debian Bug Tracking System]

Processing control commands:

> found -1 1.2.9+dfsg-6.1
Bug #883341 [slic3r] slic3r: Missing dependencies: wx-common, libopengl-perl, 
libwx-glcanvas-perl
Marked as found in versions slic3r/1.2.9+dfsg-6.1.
> severity -1 wishlist
Bug #883341 [slic3r] slic3r: Missing dependencies: wx-common, libopengl-perl, 
libwx-glcanvas-perl
Severity set to 'wishlist' from 'grave'

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

Bug#883341: slic3r: Missing dependencies: wx-common, libopengl-perl, libwx-glcanvas-perl

[Adrian Bunk]

Control: found -1 1.2.9+dfsg-6.1
Control: severity -1 wishlist

On Sat, Dec 02, 2017 at 05:00:26PM +0100, Antonio Trueba Gayol wrote:
> Package: slic3r
> Version: 1.2.9+dfsg-8
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> After installation, slic3r gui fails to start due to missing dependencies.
> Installing the following packages solves the problem:
> 
> - wx-common
> - libopengl-perl
> - libwx-glcanvas-perl
>...
> Versions of packages slic3r recommends:
> pn  libclass-xsaccessor-perl  
> pn  libio-all-perl
> ii  libopengl-perl0.7000+dfsg-1
> pn  libpdf-api2-perl  
> pn  libsvg-perl   
> ii  libwx-glcanvas-perl   0.09-3+b5
> ii  libwx-perl1:0.9932-2
> pn  libxml-sax-expatxs-perl   
>...

Thanks for your report.

The missing packages are recommended.

They are only recommended since the non-GUI functionality of the package 
does work without these packages.

Whether these should be recommends or dependencies is a valid question, 
and as far as I can see both choices would be reasonable maintainer[1] 
choices in this case.

cu
Adrian

[1] I am not the maintainer of slic3r

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Processed: Re: ooo-thumbnailer: No thumbnail generated in Gnome 3 Nautilus

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 659321 serious
Bug #659321 [ooo-thumbnailer] ooo-thumbnailer: No thumbnail generated in Gnome 
3 Nautilus
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.

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

Bug#886049: [linux-image-4.14.0-2-amd64] Function g_file_copy() from libglib2.0-0 hangs when copying small files from CIFS-Share. This is relevant for Thunar filemanager.

[reiny]

Package: linux-image-4.14.0-2-amd64
Version: 4.14.0-2-amd64
Severity: critical

--- Please enter the report below this line. ---

The function g_file_copy() from libglib2.0-0 hangs when copying a small
file from a mounted CIFS-Share. Since the thunar filemanager is using
this function to copy files, the whole copy process hangs and the
progress bar does not close again. I built a debug version of thunar
and found with gdb that the function g_file_copy() uses the systemcall
splice(). There seems to bee the problem. When Thunar hangs the
debugger gives the following output:

[debug]> thread 4
[debug][Switching to thread 4 (Thread 0x7fffe7fff700 (LWP 8037))]
[debug]#0  0x74a2f2a3 in splice () at 
../sysdeps/unix/syscall-template.S:84
[debug]84   in ../sysdeps/unix/syscall-template.S
[debug]>>cb_gdb:
[debug]> bt 30
[debug]#0  0x74a2f2a3 in splice () at 
../sysdeps/unix/syscall-template.S:84
[debug]#1  0x754b3cae in  () at 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
[debug]#2  0x754ba44c in g_file_copy () at 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
[debug]#3  0x55613619 in ttj_copy_file (job=0x55980370, 
source_file=0x55c99440, target_file=0x55cd9ae0, 
copy_flags=G_FILE_COPY_NOFOLLOW_SYMLINKS, merge_directories=1, 
error=0x7fffe7ffe8e0) at thunar-transfer-job.c:396
[debug]#4  0x55613a28 in thunar_transfer_job_copy_file 
(job=0x55980370, source_file=0x55c99440, target_file=0x55cd9ae0, 
error=0x7fffe7ffe980) at thunar-transfer-job.c:518
[debug]#5  0x55613f4e in thunar_transfer_job_copy_node 
(job=0x55980370, node=0x559ddce0, target_file=0x55cd9ae0, 
target_parent_file=0x559c3680, target_file_list_return=0x0, 
error=0x7fffe7ffea30) at thunar-transfer-job.c:655
[debug]#6  0x55613fc4 in thunar_transfer_job_copy_node 
(job=0x55980370, node=0x559c3a80, target_file=0x559c3680, 
target_parent_file=0x0, target_file_list_return=0x7fffe7ffeac8, 
error=0x7fffe7ffeac0) at thunar-transfer-job.c:671
[debug]#7  0x55614d62 in thunar_transfer_job_execute 
(job=0x55980370, error=0x7fffe7ffeb60) at thunar-transfer-job.c:1062
[debug]#8  0x779ae08d in exo_job_scheduler_job_func 
(scheduler_job=0x55c02080, cancellable=, 
user_data=) at exo-job.c:317
[debug]#9  0x754cfc96 in  () at 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
[debug]#10 0x754f6cf6 in  () at 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
[debug]#11 0x74f76000 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
[debug]#12 0x74f75635 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
[debug]#13 0x74cec519 in start_thread (arg=0x7fffe7fff700) at 
pthread_create.c:456
[debug]#14 0x74a2ea4f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:97
[debug]>>cb_gdb:
[debug]> if 1
disassemble $pc,$pc+50
info frame
end
[debug] > > >Dump of assembler code from 0x74a2f2a3 to 0x74a2f2d5:
[debug]=> 0x74a2f2a3 :   movrdi,QWORD PTR [rsp]
[debug]   0x74a2f2a7 :   movrdx,rax
[debug]   0x74a2f2aa :   call   0x74a3b690 
<__libc_disable_asynccancel>
[debug]   0x74a2f2af :   movrax,rdx
[debug]   0x74a2f2b2 :   addrsp,0x8
[debug]   0x74a2f2b6 :   cmprax,0xf001
[debug]   0x74a2f2bc :   jae0x74a2f2bf 

[debug]   0x74a2f2be :   ret
[debug]   0x74a2f2bf :   movrcx,QWORD PTR 
[rip+0x2afbb2]# 0x74cdee78
[debug]   0x74a2f2c6 :   negeax
[debug]   0x74a2f2c8 :   movDWORD PTR fs:[rcx],eax
[debug]   0x74a2f2cb :   or rax,0x
[debug]   0x74a2f2cf :   ret
[debug]   0x74a2f2d0 :   moveax,0x63
[debug]End of assembler dump.
[debug]Stack level 0, frame at 0x7fffe7ffe610:
[debug] rip = 0x74a2f2a3 in splice (../sysdeps/unix/syscall-template.S:84); 
saved rip = 0x754b3cae
[debug] called by frame at 0x7fffe7ffe660
[debug] source language asm.
[debug] Arglist at 0x7fffe7ffe5f8, args: 
[debug] Locals at 0x7fffe7ffe5f8, Previous frame's sp is 0x7fffe7ffe610
[debug] Saved registers:
[debug]  rip at 0x7fffe7ffe608
[debug]>>cb_gdb:
[debug]> disassemble /m 0x74a2f2a3
[debug]Dump of assembler code for function splice:
[debug]84   in ../sysdeps/unix/syscall-template.S
[debug]   0x74a2f270 <+0>:  cmpDWORD PTR [rip+0x2b5489],0x0 
   # 0x74ce4700 <__libc_multiple_threads>
[debug]   0x74a2f277 <+7>:  jne0x74a2f28c 
[debug]   0x74a2f279 <+0>:  movr10,rcx
[debug]   0x74a2f27c <+3>:  moveax,0x113
[debug]   0x74a2f281 <+8>:  syscall 
[debug]   0x74a2f283 <+10>: cmprax,0xf001
[debug]   0x74a2f289 <+16>: jae0x74a2f2bf 
[debug]   0x74a2f28b <+18>: ret
[debug]   0x74a2f28c <+28>: subrs

Bug#886050: openbox-gnome-session: Depends on gconf

[Jeremy Bicha]

Package: openbox-gnome-session
Version: 3.6.1-5
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs gconf
Tags: sid buster patch

openbox-gnome-session has an apparently unnecessary dependency on
gconf2. gconf will be removed from Debian soon. (No actual patch
attached because this seems trivial to fix.)

gconf's last release was about 5 years ago. It has been replaced by
gsettings (provided in Debian by source glib2.0 ) It shouldn't be
necessary for openbox to directly depend on that either unless it's
specifically working with gsettings.

On behalf of the Debian GNOME team,
Jeremy Bicha

Processed: Re: amide: Please drop the (build-)dependency against gnome-vfs

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 868383 885045
Bug #868383 [src:amide] amide: Please drop the (build-)dependency against 
gnome-vfs
Bug #885045 [src:amide] amide: Depends on old GNOME libraries
Severity set to 'important' from 'serious'
Marked as found in versions amide/1.0.5-7.
Bug #868383 [src:amide] amide: Please drop the (build-)dependency against 
gnome-vfs
Marked as found in versions amide/1.0.5-8.
Added tag(s) help.
Merged 868383 885045

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

Processed: Re: Bug#874949: These bugs are now blocking removal of qtwebkit from testing

[Debian Bug Tracking System]

Processing control commands:

> severity -1 wishlist
Bug #874949 [src:kdiff3] [kdiff3] Future Qt4 removal from Buster
Severity set to 'wishlist' from 'serious'

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

Processed: Re: Bug#874949: These bugs are now blocking removal of qtwebkit from testing

[Debian Bug Tracking System]

Processing control commands:

> severity -1 wishlist
Bug #874983 [src:konsole4] [konsole4] Future Qt4 removal from Buster
Severity set to 'wishlist' from 'serious'

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

Processed: Re: Bug#874949: These bugs are now blocking removal of qtwebkit from testing

[Debian Bug Tracking System]

Processing control commands:

> severity -1 wishlist
Bug #874966 {Done: Pino Toscano } [src:kile] [kile] Future Qt4 
removal from Buster
Severity set to 'wishlist' from 'serious'

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

Processed: Re: Bug#874949: These bugs are now blocking removal of qtwebkit from testing

[Debian Bug Tracking System]

Processing control commands:

> severity -1 wishlist
Bug #874981 [src:komparator] [komparator] Future Qt4 removal from Buster
Severity set to 'wishlist' from 'serious'

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

Bug#874949: These bugs are now blocking removal of qtwebkit from testing

[Adrian Bunk]

Control: severity -1 wishlist

On Mon, Jan 01, 2018 at 11:38:41PM +0200, Adrian Bunk wrote:
> Control: severity -1 serious
> 
> With kde-baseapps 4:16.08.3-2 these bugs became blockers for the
> qtwebkit removal, which will be removed from buster earlier than
> the rest of Qt4.

I was actually wrong on that, I missed that src:kde-baseapps still
builds libkonq5abi1/libkonq5-dev.

Sorry for the noise
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Processed: These bugs are now blocking removal of qtwebkit from testing

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #874949 [src:kdiff3] [kdiff3] Future Qt4 removal from Buster
Severity set to 'serious' from 'wishlist'

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

Processed: These bugs are now blocking removal of qtwebkit from testing

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #874983 [src:konsole4] [konsole4] Future Qt4 removal from Buster
Severity set to 'serious' from 'wishlist'

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

Processed: These bugs are now blocking removal of qtwebkit from testing

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #874981 [src:komparator] [komparator] Future Qt4 removal from Buster
Severity set to 'serious' from 'wishlist'

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

Processed: These bugs are now blocking removal of qtwebkit from testing

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #874966 {Done: Pino Toscano } [src:kile] [kile] Future Qt4 
removal from Buster
Severity set to 'serious' from 'wishlist'

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

Bug#885556: udeb uninstallability trend: worse (+20/-0)

[Don Armstrong]

On Mon, 01 Jan 2018, Cyril Brulebois wrote:
> udeb uninstallability watcher  (2018-01-01):
> > Newly-broken packages in testing
> >   multipath-udeb   amd64 arm64 armel armhf i386 
> > mips mips64el mipsel ppc64el s390x
> >   partman-multipathamd64 arm64 armel armhf i386 
> > mips mips64el mipsel ppc64el s390x
> 
> I'm wondering how this is possible with an RC bug filed against the
> multipath-udeb udeb (#885556). For some reason, it's listed as found in
> multipath-tools/0.7.4-2 on the BTS side, without a version graph; and
> it isn't listed by tracker or by the old PTS. I'm suspecting there's
> something fishy on the BTS side so britney didn't notice the RC bug
> and let it migrate?

Yeah, this definitely looks like a BTS mistake. It seems to know that
the right versions are in unstable, but they're not showing up on the
graph.

I'll try to track this down today and see what is going on there.


-- 
Don Armstrong  https://www.donarmstrong.com

The terrorist's job is to terrorize the people, to interfere with
freedom in such a way that disrupts ordinary life and commerce. With
due respect, it is clear that the above referenced governmental
agencies are aiding the terrorists' objective.
 -- Gary Fielder in Gary Fielder vs Janet Napolitano et al.

Bug#886035: cherrytree: Don't depend on python-appindicator

[Jeremy Bicha]

Index: debian/changelog
===
diff --git a/packages/cherrytree/trunk/debian/changelog b/packages/cherrytree/trunk/debian/changelog
--- a/packages/cherrytree/trunk/debian/changelog	(revision 14528)
+++ b/packages/cherrytree/trunk/debian/changelog	(working copy)
@@ -1,3 +1,10 @@
+cherrytree (0.37.6-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop depends on python-appindicator (Closes: #886035)
+
+ -- Jeremy Bicha   Mon, 01 Jan 2018 15:50:46 -0500
+
 cherrytree (0.37.6-1) unstable; urgency=medium
 
   * New upstream release.
Index: debian/control
===
diff --git a/packages/cherrytree/trunk/debian/control b/packages/cherrytree/trunk/debian/control
--- a/packages/cherrytree/trunk/debian/control	(revision 14528)
+++ b/packages/cherrytree/trunk/debian/control	(working copy)
@@ -19,7 +19,6 @@
 Architecture: all
 Depends:
  p7zip-full,
- python-appindicator,
  python-dbus,
  python-enchant,
  python-chardet,

Bug#886035: cherrytree: Don't depend on python-appindicator

[Jeremy Bicha]

Package: cherrytree
Version: 0.37.6-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs
Tags: patch pending sid buster
X-Debbugs-CC: vch...@debian.org


As part of a large ongoing effort to reduce the number of packages
depending on deprecated and unmaintained GNOME2 era stuff, I'd like to
remove the python-appindicator binary package.

cherrytree is the only package in Debian depending on
python-appindicator. Therefore, I'm filing this bug as serious. (One
python-appindicator reverse-depends and one reverse-recommends is
proposed for removal from Debian. The other reverse-recommends,
gpodder, will be fixed when the next version of gpodder is packaged in
Debian since gpodder has switched to gtk3).

cherrytree runs fine without python-appindicator. If it were
installed, it allows the app to be minimized to the appindicator area
instead of quit when the app is closed. (That option can be enabled in
Edit > Preferences > Miscellaneous > Enable System Tray Docking and >
Use Appindicator for Docking.)

cherrytree will eventually be ported to gtk3 and will then be able to
use the gtk3 appindicator support. See the upstream bug attached to
https://bugs.debian.org/822586 .

I am uploading a NMU to fix this issue to DELAYED/10. Please let me
know if I should upload sooner or slower than that. I will attach the
minimal debdiff in my follow-up email.

Thanks,
Jeremy Bicha

Bug#855494: Suggested removal of mgltools from Debian (Was: SVN to Git migration status)

[Andreas Tille]

Hi again - again,

On Fri, Dec 08, 2017 at 10:46:05AM +0100, Andreas Tille wrote:
> Hi again,
> 
> On Fri, Dec 01, 2017 at 02:24:18PM +0100, Andreas Tille wrote:
> > > >* RC-buggy (#855494 :-()
> > > This should have been addressed with that one upload of mine that 
> > > apparently
> > > had been lost before when the bug was addressed by upstream about two 
> > > years
> > > ago.
> > 
> > But the program does not yet start. :-(
> 
> Since a mgltools part now received a bug report (#883845) which I feel
> responsible to some extend since I once cared for the removal of the
> non-free image,

I fixed this bug in mgltools-vision and when doing so I realisied that
it is not my fault that the image popped up in the source tarball again.
Its just the non-default way to create the upstream source (and thus my
point that its a bad idea how this source is obtained is proven by
another issue).

> I hereby want to request a clear commitment of the
> persons mentioned in the Uploaders field whether bug #855494 will be
> fixed **soon** (= until 24.12.) to know whether it is worth spending
> some effort into it,

I'm a bit sad that my expectation that there was no commitment shown for
the issue which keeps my motivation high to ask for removal of the
package.

In any case I took over the migration from SVN to Git since I now
migrated *all* packaging stuff in SVN (also prospective packages) and so
even may be removal candidates packaging might serve some purpose in
case somebody will take over later again.

When doing the migration I realised that there was packaging code for


mgltools-cmolkit (1.5.7-1) UNRELEASED; urgency=medium

  * New upstream version (Closes: #767144,#783547,
  lp:#821299,lp:1386091,lp:#1386163,lp:#1492762)

 -- Steffen Moeller   Fri, 08 Jul 2016 17:54:14 +0200


in SVN and all other mgltools-* packages are featuring upstream version
1.5.7 but cmolkit is remaining at 1.5.7~rc1+cvs.20140424 which is most
probably unwanted.  If the get-orig-source method would not have failed
I would have injected the upgraded source but it did not worked :-(((

> or whether it is better to ask for removal since
> we have no manpower to solve RC bugs.

I'll wait with the request for removal until after our sprint. 

One more word to the "ftpmasters don't like a tarball of tarballs" [1]
workaround:  There should be other ways to deal with this "don't like"
than putting 20 times multiple work than necessary to switch to new
versions.  It took me an additional day in the SVN to Git migration.
Thus I removed myself from Uploaders which means I'll now consequently
leave the additional work to the remaining Uploaders who seem to prefer
this kind of workflow.

Kind regards

  Andreas.

[1] https://lists.debian.org/debian-med/2017/12/msg00010.html

-- 
http://fam-tille.de

Bug#822595: Raising severity to serious for packages depending on gksu

[shirish शिरीष]

at bottom :-

On 31/12/2017, Jeremy Bicha  wrote:
> Control: severity -1 serious
>
> On Wed, Aug 23, 2017 at 1:41 PM, Mike Gabriel
>  wrote:
>> I will drop severity temporarily for this bug, because we need
>> caja-extensions 1.18 in testing (rather than some older 1.16 version).
>>
>> Once caja-admin has landed in unstable, I will upload caja-extensions
>> without caja-gksu being built to address this bug.
>>
>> Hope dropping severity for now is ok. I fully get the need of caja-gksu
>> removal and by bringing caja-admin to Debian, we have worked on that.
>
> caja-admin has been in Testing for a while and caja-gksu is now
> blocking the removal of gksu from Testing. (Two packages were fixed in
> unstable today, and the third, gdebi, has an NMU in the DELAYED
> queues.) So it's time to bump the severity of this bug.
>
> Thanks,
> Jeremy Bicha
>
> --
> To unsubscribe, send mail to 822595-unsubscr...@bugs.debian.org.
>

just a small query - is gdebi supposed to be a drop-in replacement

I have used $ gksudo $GUI-editor $someconfigurationfile and it has
worked fine so far.

Look forward to know.

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#886018: fastd: FTBFS with libsodium-dev >= 1.0.15

[Colin Watson]

Package: fastd
Version: 18-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

fastd fails to build against libsodium 1.0.15 and newer.  For example:

  
https://buildd.debian.org/status/fetch.php?pkg=fastd&arch=amd64&ver=18-2%2Bb2&stamp=1514369136&raw=0

  cd /<>/obj-x86_64-linux-gnu/src/crypto/cipher/aes128_ctr/nacl && 
/u
  
/<>/src/crypto/cipher/aes128_ctr/nacl/cipher_aes128_ctr_nacl.c:36:1
   #include 
^~~
  compilation terminated.

https://projects.universe-factory.net/issues/251 suggests you're
probably aware of this; but could the workaround there perhaps be
implemented in the Debian package to unblock the libsodium transition in
advance of a new upstream release?

Thanks,

-- 
Colin Watson   [cjwat...@debian.org]

Bug#885875: seelablet: Depends on python-appindicator

[Georges Khaznadar]

Dear Jeremy,

thank you for this bug report.

I contacted Seelablet's author: he will not maintain this package in a
foreseeable future. On reason is that the hardware addressed by the
package seelablet is discontinued, and that he developped an new
hardware, known as expeyes17, with similar features, and which already
has received a noticeable success.

As expeyes17 is supported by the debian package eyes17, which I
maintain, I think that the bes solution would be to ask for the removal
of seelablet from debian/sid and debian/buster.

As there are less than a hundred users of Seelablet box in the world,
its author says me that he can support these users with a custom
package, while a package in debian/stretch would be less useful. So this
package may be removed from debian/stretch too.

I filed a RM bug report.

Best regards,   Georges.

Jeremy Bicha a écrit :
> Source: seelablet
> Version: 1.0.6-2
> Severity: serious
> User: pkg-gnome-maintain...@lists.alioth.debian.org
> Usertags: oldlibs
> Tags: sid buster
> 
> python-seelablet depends on python-appindicator but python3-seelablet
> depends on gir1.2-appindicator3-0.1
> 
> The gir dependency is wrong since as far as I can tell seelablet
> doesn't use GObject Introspection at all. I *think* the python-
> appindicator dependency is wrong too because I thought python-
> appindicator required gtk and this doesn't use gtk at all.
> 
> (I can't actually tell if it works because I can't get the app to run.
> Filing a separate bug for that.)
> 
> I'm filing this bug as Serious since this is the last package keeping
> python-appindicator from being removable in Testing.
> 
> On behalf of the Debian GNOME team,
> Jeremy Bicha

-- 
Georges KHAZNADAR et Jocelyne FOURNIER
22 rue des mouettes, 59240 Dunkerque France.
Téléphone +33 (0)3 28 29 17 70



signature.asc
Description: PGP signature

Processed: [bts-link] source package imagemagick

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package imagemagick
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #814836 (http://bugs.debian.org/814836)
> # Bug title: imagemagick: Font Metrics faulty textWidth | Integer overflow
> #  * https://github.com/ImageMagick/ImageMagick/issues/334
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 814836 + fixed-upstream
Bug #814836 [imagemagick] imagemagick: Font Metrics faulty textWidth | Integer 
overflow
Added tag(s) fixed-upstream.
> usertags 814836 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 814836 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> # remote status report for #885340 (http://bugs.debian.org/885340)
> # Bug title: CVE-2017-17504
> #  * https://github.com/ImageMagick/ImageMagick/issues/872
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 885340 + fixed-upstream
Bug #885340 [imagemagick] CVE-2017-17504
Added tag(s) fixed-upstream.
> usertags 885340 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#750732: libanyevent-perl: Intermittent build failures on various architectures

[Niko Tyni]

On Wed, Sep 13, 2017 at 04:45:39PM +0200, gregor herrmann wrote:
> On Sun, 17 Aug 2014 00:10:04 -0700, gregor herrmann wrote:
> > On Fri, 06 Jun 2014 12:42:08 +0200, gregor herrmann wrote:
> > 
> > > libanyevent-perl sometimes has test failures in different tests on
> > > different  architectures.
> > > I also had one locally (on amd64) once which went away in later
> > > rebuilds ...
> > > 
> > > Looks quite random :/

> On Ubuntu, the build failed everywhere:
> https://launchpad.net/ubuntu/+source/libanyevent-perl/7.140-1
> 
> On Debian only on armel (and hurd):
> https://buildd.debian.org/status/logs.php?pkg=libanyevent-perl&ver=7.140-1
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libanyevent-perl.html
> (amd64 only so far) and https://ci.debian.net/packages/liba/libanyevent-perl/
> (amd64 only so far) look good.
> 
> This looks all quite random. CPAN RT and cpantesters also don't show
> anything obvious …

The failing tests are conditional on the PERL_ANYEVENT_LOOP_TESTS
environmental variable, so it's no wonder cpantesters doesn't
help.

The issue seems mostly specific to armel and hurd, although
tests.reproducible-builds.org does have some failures on i386 (but no
logs so those could be just testbed glitches or transient sid issues.)
I don't know what happened in Ubuntu but it clearly built later.

Currently we have a build failure on armel that's blocking testing
migration of this package. Given the number of reverse dependencies,
I suppose we need to solve this one way or other.

Disregarding hurd-i386, the problematic test seems to be
t/66_ioasync_03_signals.t, which is using AnyEvent::Impl::IOAsync
which uses IO::Async. I see the AnyEvent::Impl::IOAsync docs have some
reservations about IO::Async, this in particular:

When you develop your program on FreeBSD and run it on GNU/Linux, you
might have unpleasant surprises, as IO::Async::Loop will by default
use IO::Async::Loop::Epoll, which is incompatible with "fork", so your
network server will run into spurious and very hard to debug problems
under heavy load, as IO::Async forks a lot of processes, e.g. for DNS
resolution. It would be better if IO::Async would only load "safe"
backends by default (or fix the epoll backend to work in the presence
of fork, which admittedly is hard - EV does it for you, and also does
not use unsafe backends by default).

I'm not sure what to make of this. Maybe disarm this particular test somehow
for now and see how it fares otherwise?
-- 
Niko Tyni   nt...@debian.org

Bug#785562: Status update

[gregor herrmann]

On Sat, 16 Dec 2017 23:41:05 +0100, Dr. Tobias Quathamer wrote:

> Am 15.12.2017 um 16:51 schrieb Emilio Pozuelo Monfort:
> > On 15/12/17 15:23, gregor herrmann wrote:
> >> On Tue, 31 Oct 2017 11:52:19 +0100, Dr. Tobias Quathamer wrote:
> >> Are there any plans to help users with the transition from openshot
> >> to openshot-qt, like the former depending on the latter before its
> >> removal or a transitional dummy package or something?
> >> Currently users will detect openshot-qt just by chance ...
> > Why was this renamed to openshot-qt? Upstream is still called 'openshot', 
> > so I'm
> > not sure it makes sense to embed the toolkit in the package name...
> my plan was to convert openshot into an empty transitional package which
> depends on openshot-qt.

That's an option.
 
> The renaming has been done by the previous maintainer, who already did
> much work but then orphaned the packaging. I have to admit that I did
> not think too much about the new package name and I'm not sticking to
> it. However, it made sense to me, because the new program is a complete
> rewrite of the old codebase, so starting the Debian package from scratch
> seemed sensible.

I see your point but from a user's point of view this is probably not
so relevant.
 
> Do you think that it might be better to reuse the "old" package openshot
> instead? Most (if not all) of the currently open bugs against openshot
> would no longer apply and could be closed, but that's of course manageable.
> I'm open for suggestions ... :-)

I think resuing the openshot package name would indeed be the easiest
/ least confusing way forward.


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 VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Davy Graham: Bulgarian Dance


signature.asc
Description: Digital Signature

Processed: owner 885295

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> owner 885295 tmanc...@debian.org
Bug #885295 [src:gpodder] gpodder: Depends on unmaintained pygtk
Owner recorded as tmanc...@debian.org.
> thanks
Stopping processing here.

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

Bug#885556: udeb uninstallability trend: worse (+20/-0)

[Cyril Brulebois]

Hello folks,

(Best wishes, yada yada)

udeb uninstallability watcher  (2018-01-01):
> Newly-broken packages in testing
>   multipath-udeb   amd64 arm64 armel armhf i386 mips 
> mips64el mipsel ppc64el s390x
>   partman-multipathamd64 arm64 armel armhf i386 mips 
> mips64el mipsel ppc64el s390x

I'm wondering how this is possible with an RC bug filed against the
multipath-udeb udeb (#885556). For some reason, it's listed as found in
multipath-tools/0.7.4-2 on the BTS side, without a version graph; and
it isn't listed by tracker or by the old PTS. I'm suspecting there's
something fishy on the BTS side so britney didn't notice the RC bug
and let it migrate?


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Processed: tagging 831835

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 831835 - jessie stretch
Bug #831835 [iceweasel] iceweasel: Padlock icon indicates a secure SSL 
connection established w  MitM-ed
Removed tag(s) stretch and jessie.
> thanks
Stopping processing here.

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

Bug#870738: marked as done (gtk2-engines-xfce: Fix FTBFS with glib 2.53.4)

[Debian Bug Tracking System]

Your message dated Mon, 01 Jan 2018 13:49:13 +
with message-id 
and subject line Bug#870738: fixed in gtk2-engines-xfce 3.2.0-3
has caused the Debian Bug report #870738,
regarding gtk2-engines-xfce: Fix FTBFS with glib 2.53.4
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
870738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870738
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gtk2-engines-xfce
Version: 3.2.0-2
Severity: serious
Tags: patch buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gtk2-engines-xfce.html

...
Making all in gtk-3.0
make[3]: Entering directory '/build/1st/gtk2-engines-xfce-3.2.0/gtk-3.0'
Traceback (most recent call last):
  File "/usr/bin/glib-mkenums", line 675, in 
process_file(fname)
  File "/usr/bin/glib-mkenums", line 407, in process_file
line = curfile.readline()
  File "/usr/lib/python3.5/codecs.py", line 321, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xd6 in position 980: 
invalid continuation byte
Makefile:743: recipe for target 'xfce_typebuiltin.c' failed
make[3]: *** [xfce_typebuiltin.c] Error 1
make[3]: *** Waiting for unfinished jobs
Traceback (most recent call last):
  File "/usr/bin/glib-mkenums", line 675, in 
process_file(fname)
  File "/usr/bin/glib-mkenums", line 407, in process_file
line = curfile.readline()
  File "/usr/lib/python3.5/codecs.py", line 321, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xd6 in position 980: 
invalid continuation byte
Makefile:737: recipe for target 'xfce_typebuiltin.h' failed
make[3]: *** [xfce_typebuiltin.h] Error 1


The fix is attached.
Description: Fix FTBFS with glib 2.54
 glib-mkenums now expects input files to be UTF-8,
 fix the encoding of libgnomeui/gnome-scores.h
Author: Adrian Bunk 

--- gtk2-engines-xfce-3.2.0.orig/gtk-3.0/xfce_style_types.h
+++ gtk2-engines-xfce-3.2.0/gtk-3.0/xfce_style_types.h
@@ -19,7 +19,7 @@
  *
  *  Portions based Thinice port by 
  *   Tim Gerla ,
- *   Tomas Ögren ,
  *   Richard Hult 
  *  Portions based on Smooth theme by
  *   Andrew Johnson 
--- End Message ---
--- Begin Message ---
Source: gtk2-engines-xfce
Source-Version: 3.2.0-3

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

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

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

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated gtk2-engines-xfce 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 01 Jan 2018 14:26:24 +0100
Source: gtk2-engines-xfce
Binary: gtk2-engines-xfce gtk3-engines-xfce
Architecture: source
Version: 3.2.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Description:
 gtk2-engines-xfce - GTK+-2.0 theme engine for Xfce
 gtk3-engines-xfce - GTK+-3.0 theme engine for Xfce
Closes: 870738
Changes:
 gtk2-engines-xfce (3.2.0-3) unstable; urgency=medium
 .
   * debian/patches:
 - 01_convert-source-utf8 added, convert source file to UTF-8 to fix FTBFS
 with glib 2.54. closes: #870738
   * Run wrap-and-sort.
   * debian/control:
 - update standards version to 4.1.3.
Checksums-Sha1:
 8f4689f49c9f834086b52b2a1fac4d5e014fc061 1907 gtk2-engines-xfce_3.2.0-3.dsc
 ff704f336acc4748ac7a8e89ca7bd44b37184a9b 5348 
gtk2-engines-xfce_3.2.0-3.debian.tar.xz
 05b8c3d225758e15a3c6047be14100a6ee2d6801 13962 
gtk2-engines-xfce_3.2.0-3_amd64.buildinfo
Checksums-Sha256:
 19e4209ef1b987cc90214cef878803d919dd5f5abda1f7a3443e3d1cb3587d80 1907 
gtk2-engines-xfce_3.2.0-3.dsc
 ffe3de67a04ad4c3836093f5a1e9344bab9e48f4b581a77a9bcc784686386623 5348 
gtk2-engines-xfce_3.2.0-3.debian.tar.xz
 0a8f1aae7f8a2f4ccf4e5a2b20d7945d1ccd866f90542ed627499c13462d3bcf 13962 
gtk2-engines-xfce_3.2.0-3_amd64.buildinfo
Files:
 f8296bf772b2d476d

Bug#885682: marked as done (to the initial the system remains before leaving the login screen with a panic kernel)

[Debian Bug Tracking System]

Your message dated Mon, 01 Jan 2018 14:45:42 +0100
with message-id <1514814342.2434.4.ca...@debian.org>
and subject line Re: [Pkg-xfce-devel] Bug#885682: to the initial the system 
remains before leaving the login screen with a panic kernel
has caused the Debian Bug report #885682,
regarding to the initial the system remains before leaving the login screen 
with a panic kernel
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
885682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885682
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xfce4
Version: 4.12.3
Severity: critical
Tags: upstream

o the initial the system remains before leaving the login screen with a panic
kernel



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

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

Versions of packages xfce4 depends on:
ii  gtk2-engines-xfce3.2.0-2
ii  libxfce4ui-utils 4.12.1-2
ii  orage4.12.1-3
ii  thunar   1.6.12-1
ii  xfce4-appfinder  4.12.0-2
ii  xfce4-panel  4.12.1-2
ii  xfce4-pulseaudio-plugin  0.2.5-1
ii  xfce4-session4.12.1-5
ii  xfce4-settings   4.12.1-1
ii  xfconf   4.12.1-1
ii  xfdesktop4   4.12.3-4
ii  xfwm44.12.4-1

Versions of packages xfce4 recommends:
ii  desktop-base  9.0.5
ii  tango-icon-theme  0.8.90-7
ii  thunar-volman 0.8.1-2
ii  xfce4-notifyd 0.3.6-1
ii  xorg  1:7.7+19

Versions of packages xfce4 suggests:
pn  gtk3-engines-xfce
ii  xfce4-goodies4.12.3
ii  xfce4-power-manager  1.4.4-4

-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, 2017-12-29 at 04:34 +0100, carlosnewmusic wrote:
> Package: xfce4
> Version: 4.12.3
> Severity: critical
> Tags: upstream
> 
> o the initial the system remains before leaving the login screen with a
> panic
> kernel

Hi,

this bug report is not really helpful for us, but in any case a kernel panic
is unlikely to be in the xfce4 package and the severity is completely
unrealistic.

I'm closing this bug, please report a new one against the linux kernel and
provide all the logs leading to the kernel panic.

Regards,
-- 
Yves-Alexis

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

Processed: limit source to sasview, tagging 885889

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> limit source sasview
Limiting to bugs with field 'source' containing at least one of 'sasview'
Limit currently set to 'source':'sasview'

> tags 885889 + pending
Bug #885889 [src:sasview] sasview: FTBFS: debian/sasview might not exist
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#879043: dahdi-linux No longer compiled with m-a as of 4.13: unknown field ‘dev_attrs’

[Tzafrir Cohen]

On Sat, Dec 30, 2017 at 11:47:21PM +0100, Bernhard Schmidt wrote:
> On Wed, Oct 18, 2017 at 08:19:26PM +0300, Tzafrir Cohen wrote:
> 
> Hi Tzafrir,
> 
> > Version: 1:2.11.1.0.20170917~dfsg-1
> > Flags: patch upstream
> > Forwarded: https://issues.asterisk.org/jira/browse/DAHLIN-356
> > Severity: grave
> > 
> > As of kernel 4.13, build fails with the following error:
> 
> Any update on this? The JIRA ticket seems to have a proposed patch
> attached, but it's not merged yet.

I pushed the fix to Upstream git. I don't think there's any upcoming
version. So it looks like a new git snapshot will do (also for better
hardware support).

And then I noticed that it fails to build with 4.15. Can be fixed, but
will require some more testing. I think I'll try to get this through
before 4.15 gets into Unstable:

https://issues.asterisk.org/jira/browse/DAHLIN-359

-- 
   Tzafrir Cohen
+972-50-7952406   mailto:tzafrir.co...@xorcom.com
http://www.xorcom.com

Processed: Re: gnome-shell-extension-show-ip: not compatible with gnome-shell 3.26: TypeError: calling a builtin typed array constructor without new is forbidden

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 gnome-shell-extension-show-ip: load fails: TypeError: calling a 
> builtin typed array constructor without new is forbidden
Bug #885996 [gnome-shell-extension-show-ip] gnome-shell-extension-show-ip: not 
compatible with gnome-shell 3.26
Changed Bug title to 'gnome-shell-extension-show-ip: load fails: TypeError: 
calling a builtin typed array constructor without new is forbidden' from 
'gnome-shell-extension-show-ip: not compatible with gnome-shell 3.26'.
> tags -1 + fixed-upstream upstream
Bug #885996 [gnome-shell-extension-show-ip] gnome-shell-extension-show-ip: load 
fails: TypeError: calling a builtin typed array constructor without new is 
forbidden
Added tag(s) upstream and fixed-upstream.
> forwarded -1 https://github.com/sgaraud/gnome-extension-show-ip/issues/22
Bug #885996 [gnome-shell-extension-show-ip] gnome-shell-extension-show-ip: load 
fails: TypeError: calling a builtin typed array constructor without new is 
forbidden
Set Bug forwarded-to-address to 
'https://github.com/sgaraud/gnome-extension-show-ip/issues/22'.

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

Bug#885996: gnome-shell-extension-show-ip: not compatible with gnome-shell 3.26: TypeError: calling a builtin typed array constructor without new is forbidden

[Paul Wise]

Control: retitle -1 gnome-shell-extension-show-ip: load fails: TypeError: 
calling a builtin typed array constructor without new is forbidden
Control: tags -1 + fixed-upstream upstream
Control: forwarded -1 
https://github.com/sgaraud/gnome-extension-show-ip/issues/22

On Mon, 2018-01-01 at 19:36 +0800, Paul Wise wrote:

> this extension is still not being loaded by gnome-shell 3.26

Looks like this is an issue with the code and mozjs:

GNOME Shell-Message: Extension "show...@kyle.aims.ac.za" had error: TypeError: 
calling a builtin typed array constructor without new is forbidden

It has been fixed upstream in version 8:

https://github.com/sgaraud/gnome-extension-show-ip/releases/tag/v8
https://github.com/sgaraud/gnome-extension-show-ip/issues/22
https://github.com/sgaraud/gnome-extension-show-ip/commit/123daa4e51594a191a24d58f7f2ea96ce93b67b8

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#885989: chromium: MitM-ed TLS sites are being recognized as secure even though they are not

[TemTem]

When I said "Because to implement an anti-DDoS service, you have to use 
CAPTCHAs.", I meant when you implement an anti-DDoS service like Cloudflare's, 
not the traditional DDos mitigation services.

Bug#885996: gnome-shell-extension-show-ip: not compatible with gnome-shell 3.26

[Paul Wise]

On Mon, 01 Jan 2018 19:27:47 +0800 Paul Wise wrote:

> This extension is not compatible with gnome-shell 3.26 and
> this prevents it from being loaded on Debian buster/sid:

Actually, it looks like the incorrect metadata issue is irrelevant to
the loading of gnome-shell extensions, but this extension is still not
being loaded by gnome-shell 3.26 on Debian buster/sid.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#885996: gnome-shell-extension-show-ip: not compatible with gnome-shell 3.26

[Paul Wise]

Package: gnome-shell-extension-show-ip
Version: 4.0.1-1
Severity: serious
Tags: buster sid

This extension is not compatible with gnome-shell 3.26 and
this prevents it from being loaded on Debian buster/sid:

$ grep -A2 shell-version 
/usr/share/gnome-shell/extensions/show...@kyle.aims.ac.za/metadata.json
  "shell-version": [
"3.22"
  ],
$ apt policy gnome-shell
gnome-shell:
  Installed: 3.26.2-2
  Candidate: 3.26.2-2
  Version table:
 *** 3.26.2-2 900
900 https://deb.debian.org/debian testing/main amd64 Packages
800 https://deb.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages gnome-shell-extension-show-ip depends on:
ii  gnome-shell  3.26.2-2

gnome-shell-extension-show-ip recommends no packages.

gnome-shell-extension-show-ip suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Processed: Re: Bug#873006: libgtk3-webkit2-perl: autopkgtest failures

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 libgtk3-webkit2-perl: missing dependency on gir1.2-webkit2-4.0
Bug #873006 [libgtk3-webkit2-perl] libgtk3-webkit2-perl: autopkgtest failures
Changed Bug title to 'libgtk3-webkit2-perl: missing dependency on 
gir1.2-webkit2-4.0' from 'libgtk3-webkit2-perl: autopkgtest failures'.
> severity -1 serious
Bug #873006 [libgtk3-webkit2-perl] libgtk3-webkit2-perl: missing dependency on 
gir1.2-webkit2-4.0
Severity set to 'serious' from 'important'

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

Bug#885989: chromium: MitM-ed TLS sites are being recognized as secure even though they are not

[TemTem]

Package: chromium
Version: 63.0.3239.84-1~deb9u1
Severity: grave
Tags: upstream security
Justification: user security hole

Inspired by bug 831835 (iceweasel: Padlock icon indicates a secure SSL 
connection established w MitM-ed).

Dear Maintainer,

A large portion of websites are being (willingly) attacked by 
man-in-the-middles (MitM) such as Cloudflare. Chromium aims to provide a SAFER 
web browsing experience, but it fails to do that by not preventing users from 
being attacked by a MitM. TLS is designed to protect against MitM attacks by 
providing an end-to-end encrypted connection between the client and the server. 
Cloudflare and other similar services undermines TLS by decrypting the 
connection, which is a very grave security and privacy concern, especially for 
Tor users. If passwords are entered in a such service pwned site, whether you 
are using TLS or not, the password (and any other sensitive data) would be 
known by an unintended third-party.

An example of a MitM-ed (and TLS encrypted) site is bitcoin.de. (Don't visit it 
if you don't want to be pwned).

The chromium package (and hopefully the upstream version) must be patched 
against this attacks ASAP.

So how will this be fixed? Display a "Your connection is not private/secure" 
warning when visiting a MitM-ed site like the above example.

How can Chromium know that the user is visiting a MitM-ed site? Let's look at 
Cloudflare. Cloudflare uses a "cf-ray:" HTTP header. Similar services probably 
has a similar kind to the "cf-ray:" header too. Use those headers and whatever 
kind which will identify that the site is pwned.

Why this is not reported upstream? Because to implement an anti-DDoS service, 
you have to use CAPTCHAs. Cloudflare uses Google's reCAPTCHA, and most of the 
MitM-ed sites are attacked because of Cloudflare. Furthermore, Cloudflare is 
backed by Google. It is almost impossible Google will be okay to mark such 
sites as insecure.

I am expecting a affirmative pong to this.

-- System Information:
Debian Release: 9.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages chromium depends on:
ii  libasound2   1.1.3-5
ii  libatk1.0-0  2.22.0-1
ii  libavcodec57 7:3.2.9-1~deb9u1
ii  libavformat577:3.2.9-1~deb9u1
ii  libavutil55  7:3.2.9-1~deb9u1
ii  libc62.24-11+deb9u1
ii  libcairo21.14.8-1
ii  libcups2 2.2.1-8
ii  libdbus-1-3  1.10.24-0+deb9u1
ii  libevent-2.0-5   2.0.21-stable-3
ii  libexpat12.2.0-2+deb9u1
ii  libflac8 1.3.2-1
ii  libfontconfig1   2.11.0-6.7+b1
ii  libfreetype6 2.6.3-3.2
ii  libgcc1  1:6.3.0-18
ii  libgdk-pixbuf2.0-0   2.36.5-2+deb9u1
ii  libglib2.0-0 2.50.3-2
ii  libgtk2.0-0  2.24.31-2
ii  libicu57 57.1-6+deb9u1
ii  libjpeg62-turbo  1:1.5.1-2
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.12-6
ii  libnss3  2:3.26.2-1.1+deb9u1
ii  libopus0 1.2~alpha2-1
ii  libpango-1.0-0   1.40.5-1
ii  libpangocairo-1.0-0  1.40.5-1
ii  libpng16-16  1.6.28-1
ii  libpulse010.0-1+deb9u1
ii  libre2-3 20170101+dfsg-1
ii  libsnappy1v5 1.1.3-3
ii  libstdc++6   6.3.0-18
ii  libvpx4  1.6.1-3
ii  libwebp6 0.5.2-1
ii  libwebpdemux20.5.2-1
ii  libwebpmux2  0.5.2-1
ii  libx11-6 2:1.6.4-3
ii  libx11-xcb1  2:1.6.4-3
ii  libxcb1  1.12-1
ii  libxcomposite1   1:0.4.4-2
ii  libxcursor1  1:1.1.14-1+deb9u1
ii  libxdamage1  1:1.1.4-2+b3
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.9-1
ii  libxml2  2.9.4+dfsg1-2.2+deb9u1
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.29-2.1
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.3-1
ii  x11-utils7.7+3+b1
ii  xdg-utils1.1.1-1
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages chromium recommends:
ii  fonts-liberation  1:1.07.4-2

Versions of packages chromium suggests:
pn  chromium-driver
pn  chromium-l10n  
pn  chromium-shell 
pn  chromium-widevine  

-- no debconf information