Processed: Bug#880528 marked as pending

[Debian Bug Tracking System]

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

> tag 880528 pending
Bug #880528 {Done: Craig Small } [src:wordpress] wordpress: 
CVE-2017-16510: Unsafe queries with wpdb->prepare
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#880528: marked as pending

[Craig Small]

tag 880528 pending
thanks

Hello,

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


https://anonscm.debian.org/cgit/collab-maint/wordpress.git/commit/?id=88c9ef8

---
commit 88c9ef8afe03dafa9499cf1065d35a0106fe8d71
Author: Craig Small 
Date:   Thu Jan 4 18:26:37 2018 +1100

Restore numbered placeholders

Apply changeset 42058 to restored nuymbered placeholders in
wpdb::prepare()

Fixes CVE-2017-16510

diff --git a/debian/changelog b/debian/changelog
index b18edcf..aec750c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -16,8 +16,10 @@ wordpress (4.7.5+dfsg-2+deb9u2) stretch-security; 
urgency=high
   Ensure the attributes of enclosures are correctly escaped in
   RSS and Atom feeds
   Changeset 42274
+  * Also backport patch for $wpdb->prepare CVE-2017-16510
+Closes: 880528
 
- -- Craig Small   Sat, 09 Dec 2017 18:13:16 +1100
+ -- Craig Small   Thu, 04 Jan 2018 18:19:44 +1100
 
 wordpress (4.7.5+dfsg-2+deb9u1) stretch-security; urgency=medium
 

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

[Clint Adams]

On Sun, Oct 22, 2017 at 02:00:58AM +0200, Alban Browaeys wrote:
> or a config item in /etc/docker/daemon.json:
> {
>   "iptables": false
> }

Seems like the docker.io package should ship this as a conffile then.

Bug#885631: marked as done (src:juffed: Will FTBFS with new qscintilla2)

[Debian Bug Tracking System]

Your message dated Thu, 04 Jan 2018 02:52:39 +
with message-id 
and subject line Bug#885631: fixed in juffed 0.10-85-g5ba17f9-17
has caused the Debian Bug report #885631,
regarding src:juffed: Will FTBFS with new qscintilla2
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.)


-- 
885631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885631
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:juffed
Version: 0.10-85-g5ba17f9-16
Severity: wishlist
Tags: patch

Dear Maintainer,

The qscintilla2 package in experimental contains a number of changes in
library naming to match upstream's changes.  As a result, juffed will FTBFS
with this version due to a link failure.  I've attached a patch for an
eventual NMU (when the transition starts).  If you would prefer to handle the
upload yourself, please let me know.

Scott K
diff -Nru juffed-0.10-85-g5ba17f9/debian/changelog juffed-0.10-85-g5ba17f9/debian/changelog
--- juffed-0.10-85-g5ba17f9/debian/changelog	2017-09-30 20:33:30.0 -0400
+++ juffed-0.10-85-g5ba17f9/debian/changelog	2017-12-27 15:27:51.0 -0500
@@ -1,3 +1,12 @@
+juffed (0.10-85-g5ba17f9-16.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update for new qscintilla2 library names
+- Update build-depends
+- Add debian/patches/new-qsci-name.patch
+
+ -- Scott Kitterman   Wed, 27 Dec 2017 15:27:17 -0500
+
 juffed (0.10-85-g5ba17f9-16) unstable; urgency=medium
 
   * Fixed typo Arch -> arch 
diff -Nru juffed-0.10-85-g5ba17f9/debian/control juffed-0.10-85-g5ba17f9/debian/control
--- juffed-0.10-85-g5ba17f9/debian/control	2017-09-30 19:39:18.0 -0400
+++ juffed-0.10-85-g5ba17f9/debian/control	2017-12-27 15:28:15.0 -0500
@@ -7,7 +7,7 @@
 Build-Depends: debhelper (>= 10),
cmake (>= 3.0.2),
libenca-dev,
-   libqt5scintilla2-dev,
+   libqscintilla2-qt5-dev,
pkg-config,
qttools5-dev,
qttools5-dev-tools
diff -Nru juffed-0.10-85-g5ba17f9/debian/patches/new-qsci-name.patch juffed-0.10-85-g5ba17f9/debian/patches/new-qsci-name.patch
--- juffed-0.10-85-g5ba17f9/debian/patches/new-qsci-name.patch	1969-12-31 19:00:00.0 -0500
+++ juffed-0.10-85-g5ba17f9/debian/patches/new-qsci-name.patch	2017-12-27 15:26:50.0 -0500
@@ -0,0 +1,22 @@
+Index: juffed-0.10-85-g5ba17f9/cmake/FindQScintilla2.cmake
+===
+--- juffed-0.10-85-g5ba17f9.orig/cmake/FindQScintilla2.cmake	2016-03-05 18:14:01.0 -0500
 juffed-0.10-85-g5ba17f9/cmake/FindQScintilla2.cmake	2017-12-27 15:26:47.261545094 -0500
+@@ -38,7 +38,7 @@
+ ${FRAMEWORK_INCLUDE_DIR}/Qsci
+ )
+ 
+-SET(QSCINTILLA_NAMES ${QSCINTILLA_NAMES} qscintilla2 libqscintilla2)
++SET(QSCINTILLA_NAMES ${QSCINTILLA_NAMES} qscintilla2 libqscintilla2 qscintilla2_qt4)
+ FIND_LIBRARY(QSCINTILLA_LIBRARY
+ NAMES ${QSCINTILLA_NAMES}
+ PATHS ${QT_LIBRARY_DIR}
+@@ -52,7 +52,7 @@
+ ENDIF()
+ ENDFOREACH()
+ 
+-SET(QSCINTILLA_NAMES ${QSCINTILLA_NAMES} qt5scintilla2 libqt5scintilla2 libqscintilla2-qt5 qscintilla2-qt5)
++SET(QSCINTILLA_NAMES ${QSCINTILLA_NAMES} qt5scintilla2 libqt5scintilla2 libqscintilla2-qt5 qscintilla2-qt5 qscintilla2_qt5)
+ GET_TARGET_PROPERTY(QT5_WIDGETSLIBRARY Qt5::Widgets LOCATION)
+ GET_FILENAME_COMPONENT(QT5_WIDGETSLIBRARYPATH ${QT5_WIDGETSLIBRARY} PATH)
+ 
diff -Nru juffed-0.10-85-g5ba17f9/debian/patches/series juffed-0.10-85-g5ba17f9/debian/patches/series
--- juffed-0.10-85-g5ba17f9/debian/patches/series	2017-06-29 17:14:33.0 -0400
+++ juffed-0.10-85-g5ba17f9/debian/patches/series	2017-12-27 15:24:57.0 -0500
@@ -1,3 +1,4 @@
 PluginPage.patch
 fix-fm-start-crash.patch
 fix-symbolbrowser-remaining.patch 
+new-qsci-name.patch
--- End Message ---
--- Begin Message ---
Source: juffed
Source-Version: 0.10-85-g5ba17f9-17

We believe that the bug you reported is fixed in the latest version of
juffed, 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 885...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alf Gaida  (supplier of updated juffed package)

(This message was generated 

Bug#886119: marked as done (e2fsprogs: FTBFS on big-endian architectures)

[Debian Bug Tracking System]

Your message dated Thu, 04 Jan 2018 01:04:02 +
with message-id 
and subject line Bug#886119: fixed in e2fsprogs 1.43.8-2
has caused the Debian Bug report #886119,
regarding e2fsprogs: FTBFS on big-endian architectures
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.)


-- 
886119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886119
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: e2fsprogs
Version: 1.43.8-1
Severity: serious
Tags: upstream patch

Hi,
The latest upload of e2fsprogs FTBFS on all big-endian architectures due
to two problems in swapfs.c:

> ../../../../lib/ext2fs/swapfs.c: In function 'ext2fs_swap_super':
> ../../../../lib/ext2fs/swapfs.c:132:2: warning: implicit declaration of 
> function 'EXT2FS_BUILD_BUG_ON'; did you mean 'EXT2FS_NUM_B2C'? 
> [-Wimplicit-function-declaration]
>   EXT2FS_BUILD_BUG_ON(sizeof(sb->s_reserved) != 98 * sizeof(__le32));
>   ^~~
>   EXT2FS_NUM_B2C
> ../../../../lib/ext2fs/swapfs.c: In function 'ext2fs_swap_inode_full':
> ../../../../lib/ext2fs/swapfs.c:361:29: error: 'ext2_inode_large' undeclared 
> (first use in this function)
>   EXT2FS_BUILD_BUG_ON(sizeof(ext2_inode_large) != 160);
>  ^~~~
> ../../../../lib/ext2fs/swapfs.c:361:29: note: each undeclared identifier is 
> reported only once for each function it appears in
> Makefile:657: recipe for target 'swapfs.o' failed

Please apply the attached patch to include ext2fsP.h (for
EXT2FS_BUILD_BUG_ON) and add the missing "struct" keyword before
ext2_inode_large, which has been tested on sparc64.

Regards,
James
--- a/lib/ext2fs/swapfs.c
+++ b/lib/ext2fs/swapfs.c
@@ -19,6 +19,7 @@
 
 #include "ext2_fs.h"
 #include "ext2fs.h"
+#include "ext2fsP.h"
 #include 
 
 #ifdef WORDS_BIGENDIAN
@@ -358,7 +359,7 @@ void ext2fs_swap_inode_full(ext2_filsys
if (inode_includes(inode_size, i_projid))
 t->i_projid = ext2fs_swab16(f->i_projid);
/* catch new static fields added after i_projid */
-   EXT2FS_BUILD_BUG_ON(sizeof(ext2_inode_large) != 160);
+   EXT2FS_BUILD_BUG_ON(sizeof(struct ext2_inode_large) != 160);
 
i = sizeof(struct ext2_inode) + extra_isize + sizeof(__u32);
if (bufsize < (int) i)
--- End Message ---
--- Begin Message ---
Source: e2fsprogs
Source-Version: 1.43.8-2

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 886...@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: Wed, 03 Jan 2018 16:18:40 -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-2
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: 886119
Changes:
 e2fsprogs (1.43.8-2) unstable; urgency=medium
 .
   * Update debian policy version to 4.1.3
   * Mark library packages as priority: optional
   * Simplify the debian/rules file and don't build e2fsprogs-l10n
 unnecessarily
   * Fix FTBFS on big-endian systems (Closes: #886119)
   * Add 

Processed: Not a problem in stretch

[Debian Bug Tracking System]

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

> tags 885961 buster sid
Bug #885961 [src:util-vserver] FTBFS: __kernel_rwf_t in 4.14 kernel headers
Added tag(s) sid and buster.
> tags 885955 buster sid
Bug #885955 [src:jcc] FTBFS: /usr/bin/ld: cannot find -ljvm
Added tag(s) sid and buster.
> tags 867939 buster sid
Bug #867939 [src:smbnetfs] smbnetfs: Build-Depends on deprecated 
libgnome-keyring-dev
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Bug#883526: marked as done (geeqie build does not trap errors from make)

[Debian Bug Tracking System]

Your message dated Wed, 03 Jan 2018 23:20:03 +
with message-id 
and subject line Bug#883526: fixed in geeqie 1:1.4-1
has caused the Debian Bug report #883526,
regarding geeqie build does not trap errors from make
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.)


-- 
883526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: geeqie
Version: 1:1.3-1
Severity: serious
Justification: policy 4.6
User: helm...@debian.org
Usertags: rebootstrap

The upstream build system of geeqie does not trap all errors from
programs executed by make. In src/Makefile.am in the ui_icons.h target,
$(GDK_PIXBUF_CSOURCE) is chained with a semicolon. Thus a potential
failure is suppressed and a misbuild can result. This is why such
behaviour is prohibited by the Debian policy section 4.6. Indeed, cross
builds do exhibit exactly that behaviour. Inserting a "set -e;" into the
subshell is an easy fix.

Helmut
--- End Message ---
--- Begin Message ---
Source: geeqie
Source-Version: 1:1.4-1

We believe that the bug you reported is fixed in the latest version of
geeqie, 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 883...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Rönnquist  (supplier of updated geeqie 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: Wed, 03 Jan 2018 23:33:34 +0100
Source: geeqie
Binary: geeqie geeqie-common
Architecture: source all amd64
Version: 1:1.4-1
Distribution: unstable
Urgency: medium
Maintainer: Michal Čihař 
Changed-By: Andreas Rönnquist 
Description:
 geeqie - image viewer using GTK+
 geeqie-common - data files for Geeqie
Closes: 883526
Changes:
 geeqie (1:1.4-1) unstable; urgency=medium
 .
   * New upstream version 1.4
 - Really fixes the problems with trapping errors (Closes: 883526)
   * Remove patch trap_errors_from_make.patch - Fix applied upstream
   * Remove patch geeqie-bug-800350-libstc++-copy-on-write-string -
 fix applied upstream
   * Don't build changelog, required files missing in upstream tar
   * Add myself to uploaders
   * Update to debhelper compat 11
   * Distribute README.md as documentation
   * Add README.md and AUTHORS to removed files
   * Don't remove README before distributing
   * README is removed, remove also from docs
   * Remove trailing whitespace
   * Remove duplicated build-depend on gnome-doc-utils
   * Remove builddepends on autotools-dev
   * Use secure VCS fields
   * Update Standards-Version to 4.1.3 (No changes required)
Checksums-Sha1:
 d9ae1c42e33a2fb2b545ec8335a2e11ff95ef9d0 2153 geeqie_1.4-1.dsc
 49f0b38953cbd864625b11a3847f97c141c4dc25 37333850 geeqie_1.4.orig.tar.gz
 10dbf309a507f98dd217105139cdb82f8c0695ba 66204 geeqie_1.4-1.debian.tar.xz
 acfeb38dea030bbaf6b195497976b3e4a052a520 429580 geeqie-common_1.4-1_all.deb
 5f9e679a7e1a2af12d562428fccdba563daae7cf 2181800 geeqie-dbgsym_1.4-1_amd64.deb
 7fb6333cd2e666bfbd0884af611ab51955702c64 13041 geeqie_1.4-1_amd64.buildinfo
 6ba9c160c1633629985a4732b675eb9e52c3d0e3 532516 geeqie_1.4-1_amd64.deb
Checksums-Sha256:
 9b81e90f8577fe252a96ef35004fc8a36b4366e4ea52061797a214af66693432 2153 
geeqie_1.4-1.dsc
 ab9f674d6714be63f5f87ba7d6f2ffcb400ece6779f8ce5ff14b44cfc1c5bf1c 37333850 
geeqie_1.4.orig.tar.gz
 e1fc5c4dddffcdd64352511c9e56ace18c1be24f5064064c379c57186874c229 66204 
geeqie_1.4-1.debian.tar.xz
 6d7f134f925d28cf713c472860a01de9fabd86ad135a943125a0d0e2e79a34a3 429580 
geeqie-common_1.4-1_all.deb
 9bac155ca3b0fee3d187141c3e05bd90b44de6f0cfdf94be0773c4ad79275307 2181800 
geeqie-dbgsym_1.4-1_amd64.deb
 cbb3c91ed7771f5d6953fa1c9666d79bd4f8455cdecca666907782ae1ba40dd8 13041 
geeqie_1.4-1_amd64.buildinfo
 1d0ef5127fc6083396a11d2695631d0693222ca72731b64422f7ed05e8b30e32 532516 
geeqie_1.4-1_amd64.deb
Files:
 904544d08eaff1b7674aa400f50a5e2b 2153 graphics optional geeqie_1.4-1.dsc
 c31d329d1cc616d6698925124c678818 37333850 graphics optional 
geeqie_1.4.orig.tar.gz
 f5ed516bac78d4eafe1f03089c5213c7 66204 graphics optional 

Processed: Not a problem in stretch

[Debian Bug Tracking System]

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

> tags 867950 buster sid
Bug #867950 [mailnag] mailnag: Uses deprecated gir1.2-gnomekeyring-1.0
Added tag(s) sid and buster.
> tags 867946 buster sid
Bug #867946 [src:libsocialweb] libsocialweb: Build-Depends on deprecated 
libgnome-keyring-dev
Added tag(s) buster and sid.
> tags 867933 buster sid
Bug #867933 [src:mail-notification] mail-notification: Build-Depends on 
deprecated libgnome-keyring-dev
Added tag(s) sid and buster.
> tags 867937 buster sid
Bug #867937 [src:mate-power-manager] mate-power-manager: Build-Depends on 
deprecated libgnome-keyring-dev
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#886290: node-timed-out: FTBFS: Assumes

[Chris Lamb]

Source: node-timed-out
Version: 4.0.1-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

node-timed-out fails to build from source in unstable/amd64. Not sure
why it fails to timeout when accessing http://192.0.2.1 but this seems
to be a broken way of testing anyway...

  […]
  
1) should emit ETIMEDOUT when connection timeout expires
when connection is established
  ✓ should emit ESOCKETTIMEDOUT (no data) (221ms)
  ✓ should emit ESOCKETTIMEDOUT (only first chunk of body) (313ms)
  ✓ should be able to only apply connect timeout
  ✓ should be able to only apply socket timeout (55ms)
  ✓ should not add event handlers twice for the same socket
  ✓ should set socket timeout if socket is already connected (211ms)
  ✓ should clear socket timeout for keep-alive sockets
  
  
7 passing (3s)
1 failing
  
1) should emit ETIMEDOUT when connection timeout expires:
   Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure 
"done()" is called; if returning a Promise, ensure it resolves.
at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19)
  
  
  
  debian/rules:13: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 1

  […]

The full build log is attached or can be viewed here:


https://tests.reproducible-builds.org/debian/logs/unstable/amd64/node-timed-out_4.0.1-1.build1.log.gz


Regards,

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


node-timed-out.4.0.1-1.unstable.amd64.log.txt.gz
Description: Binary data

Processed: Not an RC issue for stretch

[Debian Bug Tracking System]

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

> tags 867561 buster sid
Bug #867561 {Done: Didier Raboud } [hplip-gui] hplip-gui: 
Depending on gksu is not good
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Bug#787527: Google

[Jonnie Brown]

What is going on

Bug#886288: node-macaddress: FTBFS: Assumes build environment has network interfaces

[Chris Lamb]

Source: node-macaddress
Version: 0.2.8-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

node-macaddress fails to build from source in amd64/unstable if there
are no network interfaces:

  dh_auto_test
  node test.js
  
  /build/1st/node-macaddress-0.2.8/test.js:5
  throw err || mac;
  ^
  no interfaces found
  debian/rules:13: recipe for target 'override_dh_auto_test' failed


Regards,

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

Bug#886287: node-coveralls: FTBFS: makes assumptions about build path

[Chris Lamb]

Source: node-coveralls
Version: 3.0.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

node-coveralls fails to build from source in amd64/unstable if you
rename the build directory. I see you patch the upstream function
but the whole thing is too brittle IMHO.

eg.

  $ cd $(mktemp -d)
  $ apt-get source node-coveralls
  $ mv node-coveralls*/ renamed
  $ cd renamed
  $ dpkg-buildpackage -uc -us

  […]

2) detectLocalGit
 "after all" hook:
   Error: Tried to clean a temp git directory that did not match path: 
node-coveralls/test
at _deleteFolderRecursive (test/detectLocalGit.js:61:11)
at _cleanTempGitDir (test/detectLocalGit.js:55:5)
at Context. (test/detectLocalGit.js:19:9)
at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21)
at Hook.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
at next (/usr/lib/nodejs/mocha/lib/runner.js:304:10)
at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:334:5)
  
  
  
  debian/rules:30: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 1
  make[1]: Leaving directory '/build/node-coveralls-3.0.0/2nd'
  debian/rules:10: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
  I: copying local configuration
  E: Failed autobuilding of package

  […]


Regards,

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


node-coveralls.3.0.0-1.logs.unstable.log.txt.gz
Description: Binary data

Bug#878588: marked as done (sysbench must pass --without-gcc-arch to configure)

[Debian Bug Tracking System]

Your message dated Wed, 03 Jan 2018 22:35:10 +
with message-id 
and subject line Bug#878588: fixed in sysbench 1.0.11+ds-1
has caused the Debian Bug report #878588,
regarding sysbench must pass --without-gcc-arch to configure
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.)


-- 
878588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878588
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sysbench
Version: 1.0.7+ds-1
Severity: serious

sysbench uses AX_GCC_ARCHFLAG for autodetecting and optimizing
for the processor of the build machine (this is basically a manual
way of doing -march=native).

This must not be used in Debian since it makes the package
only work on cpus that are compatible with the cpu of
whatever buildd was used to build the package this time.

Passing --without-gcc-arch to configure fixes this bug.
--- End Message ---
--- Begin Message ---
Source: sysbench
Source-Version: 1.0.11+ds-1

We believe that the bug you reported is fixed in the latest version of
sysbench, 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 878...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
JCF Ploemen (jcfp)  (supplier of updated sysbench 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: Wed, 03 Jan 2018 14:06:21 +
Source: sysbench
Binary: sysbench
Architecture: source
Version: 1.0.11+ds-1
Distribution: unstable
Urgency: medium
Maintainer: JCF Ploemen (jcfp) 
Changed-By: JCF Ploemen (jcfp) 
Description:
 sysbench   - multi-threaded benchmark tool for database systems
Closes: 878588
Changes:
 sysbench (1.0.11+ds-1) unstable; urgency=medium
 .
   * New upstream release:
 + fixes build failure on kfreebsd.
   * Bump Standards-Version to 4.1.3 (from 4.0.0).
   * Control:
 + change priority to optional, extra is deprecated by policy.
 + remove build-depend on dh-autoreconf, redundant with compat 10.
   * Rules: add --without-gcc-arch to dh_auto_configure in an attempt to
 make the build reproducible and avoid instructions too specific to
 the cpu of the buildd (Closes: #878588).
Checksums-Sha1:
 b7ef5a223bff05fa18eff9e7d5a91adcbf7b6d1b 2019 sysbench_1.0.11+ds-1.dsc
 aed358fe15768a7cf6d274725a581cc2b3a68fe7 224337 sysbench_1.0.11+ds.orig.tar.gz
 d8966c98b21350956dbe284a84b7a70937c9cc59 9584 
sysbench_1.0.11+ds-1.debian.tar.xz
 5c18c3fd840228df1c43c9d5ccf6c64b1b7e9a56 5337 
sysbench_1.0.11+ds-1_source.buildinfo
Checksums-Sha256:
 cc9389631c24b84601fda83e921074509ab755654e332bf5c820be51c63731c2 2019 
sysbench_1.0.11+ds-1.dsc
 0f838f628c41e29a5b777c9c35e4c895bf3852a6e8fdad53e5e74aebb8c27211 224337 
sysbench_1.0.11+ds.orig.tar.gz
 11fce0ce8cfcc9eb1f4aa0dc694df42bcb1f3b208b238a885aed4152f21d182f 9584 
sysbench_1.0.11+ds-1.debian.tar.xz
 222bfa488da763687e9ec37448d8b28477d65e9a99b57567bf0ab0501000ecdb 5337 
sysbench_1.0.11+ds-1_source.buildinfo
Files:
 2e439957b0092edba02cd170f7522100 2019 misc optional sysbench_1.0.11+ds-1.dsc
 e87f95faf9692d9623cbea573402303b 224337 misc optional 
sysbench_1.0.11+ds.orig.tar.gz
 e592795217c554da662bb7caacbcdd25 9584 misc optional 
sysbench_1.0.11+ds-1.debian.tar.xz
 f9934c47d5f6770a6a456ebf94d4d97b 5337 misc optional 
sysbench_1.0.11+ds-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAlpNVLgACgkQweDZLphv
fH5XRw/8CCVGF5fSy+8nWFj1+BldNKDU5SqfPYr0qZP5q4V6174DLTzqcocFi4cU
lxRJswpJf8Gvi1EEJHHjhSZhsKbyMjgLfO4OJj5dk1Yemf2nQGFHiVkX0gp7UhzM
RveXsJ6sUfeIlivb0DImJaVFjZUQkoPWoA7hAuA7Oz+a+BQnPbT+WR/l7FzOKBxW
vblSE2jmOD5C6O5vgVR6SiBq8FB22NNi0joUMJv5/V82TgvuNrO1lvlm93zzjRTa
CEeHiZXMTMllZJQ38jUB87EtqPtAILOk0amXlc06tMc+mP7+5hJQY08Diw5rc2kH
8gPuz/cpl0faQ1DVB7EHbgkEWHHy67oBcUYVeNb84ImdF3Zgay06mJXQZJIU6SwD
IAWx8oYUedeTCec4Z1JlE7Wvif3imjqx0FGkkTcGzcYDJ225dZdovFc/3JRE/5gI
GQ70mFb3Nywx8Yk/qSp7nVIS0JknmEZthKLzS76O5He432FLyvuK34SrUi1hl+fU
BjtCfyHm36O7KDQequrz6CwkC7juwVUSvT1IvuX2hJ2a8UwiqRv0EUfnQhuM6KMe
AbLYF0Ufa5vEpcg8Vrejf7QQWXsgMU5gRRjT+Qmp+j9lSEP4DVkFiCpXCotRk161
sNW92MsTaUimNN3PCbtPqlz+80Mq3ZgyA51/Imy9JKnj/5d01TU=
=d0Nf
-END PGP 

Bug#878429: marked as done (octave-ltfat: FTBFS on mips(el): tests time out)

[Debian Bug Tracking System]

Your message dated Wed, 3 Jan 2018 23:26:55 +0100
with message-id <20180103222655.gd3...@laboissiere.net>
and subject line Re: [Pkg-octave-devel] Bug#878429: octave-ltfat: FTBFS on 
mips(el): tests time out
has caused the Debian Bug report #878429,
regarding octave-ltfat: FTBFS on mips(el): tests time out
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.)


-- 
878429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878429
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: octave-ltfat
Version: 2.2.0+dfsg-4
Severity: serious

Your package failed to build on mips and mipsel:

PASSES 7 out of 7 tests
Checking CC files ...
[running test_all_ltfat]
 ===  TEST_DGT 
 ===  TEST_DWILT 
 ===  TEST_WMDCT 
 ===  TEST_DGT_FB 
 ===  TEST_MULTIWIN 
 ===  TEST_GABFIRTIGHT 
 ===  TEST_PUREFREQ 
 ===  TEST_ZAK 
 ===  TEST_GABMULAPPR =
 ===  TEST_DGT2 
 ===  TEST_DWILT2 
 ===  TEST_WMDCT2 
 ===  TEST_FIRWIN 
 ===  TEST_SPREAD 
 ===  TEST_DSFT ==
 ===  TEST_THRESH 
 ===  TEST_PCONV ==
 ===  TEST_LCONV ==
 ===  TEST_INVOLUTE ===
 ===  TEST_SIGNALS ===
 ===  TEST_REALOUT 
 ===  TEST_WINDRIVERS 
 ===  TEST_NSDGT 
 ===  TEST_FILTERBANK 
 ===  TEST_PGAUSS 
 ===  TEST_PFILT ==
 ===  TEST_RANGECOMPRESS 
 ===  TEST_GABMULEIGS 
 ===  TEST_PHASELOCK 
= TEST FWT 
-TEST_BLOCKFWT--
= TEST UFWT 
= TEST WFBT 
= TEST UWPFBT 
= TEST WPFBT 
= TEST UWPFBT 
= TEST FWT2 
 ===  TEST_WFBT2FILTERBANK ===
TEST_FREQORDER--
 ===  TEST_GGA 
 ===  TEST_CHIRPZT 
 ===  TEST_FRAMES 
E: Build killed with signal TERM after 360 minutes of inactivity

Full logs at https://buildd.debian.org/status/package.php?p=octave-ltfat

Emilio

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 
'unstable-debug'), (500, 'testing-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Version: 2.2.0+dfsg-5

Version 2.2.0+dfsg-5 of octave-ltfat, uploaded recently to unstable, 
built fine on mips [1] and mipsel [2].  I am hereby closing this bug 
report.


Rafael

[1] 
https://buildd.debian.org/status/fetch.php?pkg=octave-ltfat=mips=2.2.0%2Bdfsg-5=1514690824=0
[2] 
https://buildd.debian.org/status/fetch.php?pkg=octave-ltfat=mipsel=2.2.0%2Bdfsg-5=1514761186=0

* Emilio Pozuelo Monfort  [2017-10-13 19:01]:


Source: octave-ltfat
Version: 2.2.0+dfsg-4
Severity: serious

Your package failed to build on mips and mipsel:

PASSES 7 out of 7 tests 
Checking CC files ... 
[running test_all_ltfat] 
===  TEST_DGT  
===  TEST_DWILT  
===  TEST_WMDCT  
===  TEST_DGT_FB  
===  TEST_MULTIWIN  
===  TEST_GABFIRTIGHT  
===  TEST_PUREFREQ  
===  TEST_ZAK  
===  TEST_GABMULAPPR = 
===  TEST_DGT2  
===  TEST_DWILT2  
===  TEST_WMDCT2  
===  TEST_FIRWIN  
===  TEST_SPREAD  
===  TEST_DSFT == 
===  TEST_THRESH  

Bug#886133: ndpi: FTBFS on mips, s390x, powerpc, and ppc64: tests time out

[Ludovico Cavedon]

Thank you for looking into this.

On Tue, Jan 2, 2018 at 12:15 PM Aaron M. Ucko  wrote:

> > It so happens that I was having a brief look already :)
>
> Great, thanks!
>
> > The hang occurs inside the above while loop. Notice that the value
> > loaded into "label" inside the loop never changes and this is the only
> > variable the loop condition depends on. Therefore, if the initial loop
> > condition is true, the program will loop forever.
>
> So I see.  Perhaps the intent was to update mpls after bumping ip_offset.
>

Yes, there is clearly something missing.
Probably
mpls = (struct ndpi_mpls_header *) [ip_offset];
is missing from inside the loop.

I will check on this before the end of the week, follow up with upstream,
and patch.

Thanks,
Ludovico

Bug#886133: ndpi: FTBFS on mips, s390x, powerpc, and ppc64: tests time out

[Aurelien Jarno]

On 2018-01-02 10:57, Aaron M. Ucko wrote:
> Source: ndpi
> Version: 2.2-1
> Severity: serious
> Tags: upstream
> Justification: fails to build from source (but built successfully in the past)
> User: debian-m...@lists.debian.org
> Usertags: mips
> 
> Builds of ndpi for mips, s390x, and the non-release architectures
> powerpc and ppc64 all failed because running the test suite hit the
> autobuilders' inactivity timeouts.  These timeouts are generous enough
> (600 minutes on ppc64, 150 minutes on the other three architectures)
> that hitting them generally indicates that something managed to hang
> or spin indefinitely.  However, I see that the hppa build ran for a
> long time before terminating on its own (albeit with test suite
> errors), so you may simply need to add progress indicators for the
> sake of slow architectures.  (These are inactivity timeouts, so any
> output to stdout or stderr resets them.)

s390x and ppc64 are definitely not slow architectures. The common
between all these architectures is that there are big endian.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#884236: marked as done (fis-gtm FTBFS with linux-libc-dev 4.14.2-1)

[Debian Bug Tracking System]

Your message dated Wed, 03 Jan 2018 21:34:46 +
with message-id 
and subject line Bug#884236: fixed in fis-gtm 6.3-002-4
has caused the Debian Bug report #884236,
regarding fis-gtm FTBFS with linux-libc-dev 4.14.2-1
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.)


-- 
884236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884236
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fis-gtm
Version: 6.3-002-3
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/fis-gtm.html

...
/usr/bin/cc -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -D_LARGEFILE64_SOURCE 
-D_XOPEN_SOURCE=600 -I/build/1st/fis-gtm-6.3-002/obj-x86_64-linux-gnu/gen 
-I/build/1st/fis-gtm-6.3-002/sr_linux -I/build/1st/fis-gtm-6.3-002/sr_x86_64 
-I/build/1st/fis-gtm-6.3-002/sr_x86_regs 
-I/build/1st/fis-gtm-6.3-002/sr_unix_gnp 
-I/build/1st/fis-gtm-6.3-002/sr_unix_cm -I/build/1st/fis-gtm-6.3-002/sr_unix 
-I/build/1st/fis-gtm-6.3-002/sr_port_cm -I/build/1st/fis-gtm-6.3-002/sr_port 
-I/build/1st/fis-gtm-6.3-002/obj-x86_64-linux-gnu -I/usr/local/include 
-I/usr/local/ssl/include  -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -ansi -fPIC  
-fsigned-char -Wmissing-prototypes -Wreturn-type -Wpointer-sign 
-fno-omit-frame-pointer -O2 -DNDEBUG   -o 
CMakeFiles/gtm_threadgbl_deftypes.dir/sr_port/gtm_threadgbl_deftypes.c.o   -c 
/build/1st/fis-gtm-6.3-002/sr_port/gtm_threadgbl_deftypes.c
In file included from /build/1st/fis-gtm-6.3-002/sr_port/gdsfhead.h:29:0,
 from 
/build/1st/fis-gtm-6.3-002/sr_port/gtm_threadgbl_deftypes.c:43:
/build/1st/fis-gtm-6.3-002/sr_port/gtm_libaio.h:72:2: warning: parameter names 
(without types) in function declaration
  __u32 PADDED(aio_key, aio_reserved1);
  ^
/build/1st/fis-gtm-6.3-002/sr_port/gtm_libaio.h:72:8: error: field 'PADDED' 
declared as a function
  __u32 PADDED(aio_key, aio_reserved1);
^~
CMakeFiles/gtm_threadgbl_deftypes.dir/build.make:65: recipe for target 
'CMakeFiles/gtm_threadgbl_deftypes.dir/sr_port/gtm_threadgbl_deftypes.c.o' 
failed
make[3]: *** 
[CMakeFiles/gtm_threadgbl_deftypes.dir/sr_port/gtm_threadgbl_deftypes.c.o] 
Error 1


The PADDED define was removed from /usr/include/linux/aio_abi.h
--- End Message ---
--- Begin Message ---
Source: fis-gtm
Source-Version: 6.3-002-4

We believe that the bug you reported is fixed in the latest version of
fis-gtm, 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 884...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated fis-gtm 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: Wed, 03 Jan 2018 21:52:11 +0100
Source: fis-gtm
Binary: fis-gtm fis-gtm-6.3-002
Architecture: source
Version: 6.3-002-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 fis-gtm- metapackage for the latest version of FIS-GT.M database
 fis-gtm-6.3-002 - package for FIS-GT.M database
Closes: 881368 884236
Changes:
 fis-gtm (6.3-002-4) unstable; urgency=medium
 .
   [ Andreas Tille ]
   * Switch Build-Depends from libconfig8-dev to libconfig-dev
 Closes: #881368
   * Standards-Version: 4.1.3
   * do not parse d/changelog
 .
   [ Amul Shah ]
   * Address fis-gtm FTBFS with linux-libc-dev 4.14.2-1
 Closes: #884236
Checksums-Sha1:
 bf2321de823258254b10c6f96ed7aec285e4a28f 2409 fis-gtm_6.3-002-4.dsc
 ff53bb1523a7366155a76d13be8afeb6c29cb8d9 25648 fis-gtm_6.3-002-4.debian.tar.xz
 888ce17bd6ad5bae27bf1b93c63182f4ed212628 14410 
fis-gtm_6.3-002-4_source.buildinfo
Checksums-Sha256:
 819067ce03dd869d69251963f2be5d86c7f93a4ce78eaef7a78aab0539af255a 2409 
fis-gtm_6.3-002-4.dsc
 85129638fba67a32d73f7c97c957952f2a68ff647c4ff9729a665f19ef31362a 25648 
fis-gtm_6.3-002-4.debian.tar.xz
 cf4ed459cec15d9aa104035fceb56936d293a9c3499d7dd9b385fb9800e8c410 14410 
fis-gtm_6.3-002-4_source.buildinfo
Files:
 be2a58a3ce8e2656335ae40d1e5a06ea 2409 database optional 

Bug#884200: marked as done (libsynthesis FTBFS with libical3)

[Debian Bug Tracking System]

Your message dated Wed, 03 Jan 2018 21:12:01 +
with message-id 
and subject line Bug#884200: fixed in libsynthesis 
3.4.0.47.5+syncevolution-1.5.2-3
has caused the Debian Bug report #884200,
regarding libsynthesis FTBFS with libical3
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.)


-- 
884200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884200
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libsynthesis
Version: 3.4.0.47.5+syncevolution-1.5.2-1
Severity: serious
Tags: buster sid

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

...
platform_adapters/linux/platform_timezones.cpp: In function 'void 
sysync::finalizeSystemZoneDefinitions(sysync::GZones*)':
platform_adapters/linux/platform_timezones.cpp:209:3: error: 
'icaltzutil_set_exact_vtimezones_support' was not declared in this scope
   icaltzutil_set_exact_vtimezones_support(0);
   ^~~
platform_adapters/linux/platform_timezones.cpp:209:3: note: suggested 
alternative: 'icaltzutil_fetch_timezone'
   icaltzutil_set_exact_vtimezones_support(0);
   ^~~
   icaltzutil_fetch_timezone
Makefile:1884: recipe for target 
'platform_adapters/linux/libsynthesis_la-platform_timezones.lo' failed
make[3]: *** [platform_adapters/linux/libsynthesis_la-platform_timezones.lo] 
Error 1
--- End Message ---
--- Begin Message ---
Source: libsynthesis
Source-Version: 3.4.0.47.5+syncevolution-1.5.2-3

We believe that the bug you reported is fixed in the latest version of
libsynthesis, 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 884...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Tino Mettler  (supplier of updated libsynthesis package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 30 Dec 2017 22:28:52 +0100
Source: libsynthesis
Binary: libsynthesis-dev libsynthesis0v5 libsmltk0
Architecture: source amd64
Version: 3.4.0.47.5+syncevolution-1.5.2-3
Distribution: unstable
Urgency: medium
Maintainer: Tino Mettler 
Changed-By: Tino Mettler 
Description:
 libsmltk0  - library for SyncML-DS (SyncML Data Sync) clients (shared librarie
 libsynthesis-dev - library for SyncML-DS (SyncML Data Sync) clients 
(development fil
 libsynthesis0v5 - library for SyncML-DS (SyncML Data Sync) clients (shared 
librarie
Closes: 884200
Changes:
 libsynthesis (3.4.0.47.5+syncevolution-1.5.2-3) unstable; urgency=medium
 .
   [ Patrick Ohly ]
   * libical: support libical v3 (Closes: #884200)
Checksums-Sha1:
 6bc2e42b1105d167532e0ea277fba338097153bf 2349 
libsynthesis_3.4.0.47.5+syncevolution-1.5.2-3.dsc
 36ec5c277293656104e897e9ef29ae90b5020112 6225215 
libsynthesis_3.4.0.47.5+syncevolution-1.5.2.orig.tar.gz
 cef9ae4341073403b67cea8840160d28ad8b5cfe 12284 
libsynthesis_3.4.0.47.5+syncevolution-1.5.2-3.debian.tar.xz
 061e767233ada3dd45e6c5d788a564765535b2a1 103832 
libsmltk0-dbgsym_3.4.0.47.5+syncevolution-1.5.2-3_amd64.deb
 929a379a0ee35fc54e73388a8b908fd5f2401bfe 45564 
libsmltk0_3.4.0.47.5+syncevolution-1.5.2-3_amd64.deb
 38ac8aa6cc393b165bdb9c93f660fbdef4506eb3 903320 
libsynthesis-dev_3.4.0.47.5+syncevolution-1.5.2-3_amd64.deb
 eed008d326915a39446f82126a80b9f8e6949269 4375672 
libsynthesis0v5-dbgsym_3.4.0.47.5+syncevolution-1.5.2-3_amd64.deb
 857bf71e529343661c90ad2cefc5c8b563527f96 60 
libsynthesis0v5_3.4.0.47.5+syncevolution-1.5.2-3_amd64.deb
 22edaca7f1056e9316d22f1fd6eb3b758dc8f7e1 8632 
libsynthesis_3.4.0.47.5+syncevolution-1.5.2-3_amd64.buildinfo
Checksums-Sha256:
 17a425fd5651a4d825ece8713e0ff69c3152da3bb1baf1e6de2598dbc9d758ff 2349 
libsynthesis_3.4.0.47.5+syncevolution-1.5.2-3.dsc
 cbdba591dcd10ee29a0af4163c09f5f4548cc3fd9a50f0c372f8eeabbdda5970 6225215 
libsynthesis_3.4.0.47.5+syncevolution-1.5.2.orig.tar.gz
 493d93882bb3ad7875c44021bc854a489f654bd2d58edee6207d25c2364778a3 12284 
libsynthesis_3.4.0.47.5+syncevolution-1.5.2-3.debian.tar.xz
 af02a967f5b80a1dc913d1d9f20e866a9b371b280fcda92414f88a6caf7e773c 103832 
libsmltk0-dbgsym_3.4.0.47.5+syncevolution-1.5.2-3_amd64.deb
 

Processed: Not a problem in stretch

[Debian Bug Tracking System]

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

> tags 885252 buster sid
Bug #885252 [src:yahtzeesharp] yahtzeesharp: Build-Depends on libart2.0-cil-dev
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Processed: Not a problem in stretch

[Debian Bug Tracking System]

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

> tags 867929 buster sid
Bug #867929 [src:bisho] bisho: Build-Depends on deprecated libgnome-keyring-dev
Added tag(s) sid and buster.
> tags 674107 buster sid
Bug #674107 [mx] mx: Consider dropping libcluttergesture-dev build-depends
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Processed: Not a problem in stretch

[Debian Bug Tracking System]

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

> tags 885134 buster sid
Bug #885134 {Done: Debian FTP Masters } 
[src:gnome-icon-theme-extras] gnome-icon-theme-extras: Don't include in Debian
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#883100: Bug#886245: RM: ksudoku [armel armhf] -- ROM; does not support Desktop OpenGL

[Pino Toscano]

On mercoledì 3 gennaio 2018 20:48:25 CET Adrian Bunk wrote:
> On Wed, Jan 03, 2018 at 07:32:46PM +0100, Pino Toscano wrote:
> > On mercoledì 3 gennaio 2018 20:26:53 CET Adrian Bunk wrote:
> > > On Wed, Jan 03, 2018 at 07:14:58PM +0100, Pino Toscano wrote:
> > > > On mercoledì 3 gennaio 2018 20:12:05 CET Adrian Bunk wrote:
> > > >...
> > > > > Regarding ksudoku, is there any reason why you didn't apply
> > > > > either my patch from #883100 or the similar change from Ubuntu?
> > > > > Either one would fix the build on armel and armhf.
> > > > 
> > > > It is a bad hack, and I do not want to carry and support it.
> > > 
> > > Ubuntu backported the upstream fix.
> > 
> > Ah I see, a different hack than yours [1],
> >...
> > [1] that btw will not work, since even if you skip the
> > find_package(OpenGL) call, then set_package_properties(OpenGL ...) sets
> > TYPE REQUIRED, and thus make cmake error out (see feature_summary)
> > because a required dependency was not found
> 
> Why are you implying that I did not test that my patch fixed the FTBFS
> before submitting it?
> 
> When you are claiming that it "will not work", all I can say is
> that it did work for me in an armel build on November 29th 2017.

I stand corrected: your patch "builds" (although IMHO it should not).

Still, both yours and "upstream" patches are hacks, and no, I am *not*
going to support them.  If you could stop pushing for them, it would
be less time I am wasting on this.

Thanks,
-- 
Pino Toscano

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

Processed: Not a problem in stretch

[Debian Bug Tracking System]

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

> tags 885133 buster sid
Bug #885133 {Done: Debian FTP Masters } 
[src:gnome-search-tool] gnome-search-tool: Don't include in Buster
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Bug#883100: Bug#886245: RM: ksudoku [armel armhf] -- ROM; does not support Desktop OpenGL

[Adrian Bunk]

On Wed, Jan 03, 2018 at 07:32:46PM +0100, Pino Toscano wrote:
> On mercoledì 3 gennaio 2018 20:26:53 CET Adrian Bunk wrote:
> > On Wed, Jan 03, 2018 at 07:14:58PM +0100, Pino Toscano wrote:
> > > On mercoledì 3 gennaio 2018 20:12:05 CET Adrian Bunk wrote:
> > >...
> > > > Regarding ksudoku, is there any reason why you didn't apply
> > > > either my patch from #883100 or the similar change from Ubuntu?
> > > > Either one would fix the build on armel and armhf.
> > > 
> > > It is a bad hack, and I do not want to carry and support it.
> > 
> > Ubuntu backported the upstream fix.
> 
> Ah I see, a different hack than yours [1],
>...
> [1] that btw will not work, since even if you skip the
> find_package(OpenGL) call, then set_package_properties(OpenGL ...) sets
> TYPE REQUIRED, and thus make cmake error out (see feature_summary)
> because a required dependency was not found

Why are you implying that I did not test that my patch fixed the FTBFS
before submitting it?

When you are claiming that it "will not work", all I can say is
that it did work for me in an armel build on November 29th 2017.

> Pino Toscano

cu
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: Not a problem in stretch

[Debian Bug Tracking System]

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

> tags 879034 buster sid
Bug #879034 [pdfshuffler] pdfshuffler: port to gir1.2-poppler-0.18
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Processed: lower severity of pygtkspellcheck to match zim's pygtk bug

[Debian Bug Tracking System]

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

> severity 885375 important
Bug #885375 [src:pygtkspellcheck] pygtkspellcheck: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'
>
End of message, stopping processing here.

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

Bug#886275: gourmet: Don't depend on python-poppler

[Jeremy Bicha]

From 1cf2c5fbd5520fdf16c2d9aab401329fc00ba930 Mon Sep 17 00:00:00 2001
From: Jeremy Bicha 
Date: Wed, 3 Jan 2018 12:49:20 -0500
Subject: [PATCH] Don't depend on python-poppler

since it's being removed from Debian and
don't install the printing plugin. Thanks Steve Langasek.

Closes: #886275
---
 debian/changelog | 8 
 debian/control   | 2 +-
 debian/rules | 2 ++
 3 files changed, 11 insertions(+), 1 deletion(-)

diff --git a/debian/changelog b/debian/changelog
index f0ca49c..a84b7b4 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+gourmet (0.17.4-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Don't depend on python-poppler (since it's being removed from Debian) and
+don't install the printing plugin. Thanks Steve Langasek. (Closes: #886275)
+
+ -- Jeremy Bicha   Wed, 03 Jan 2018 12:48:28 -0500
+
 gourmet (0.17.4-4) unstable; urgency=medium
 
   * Remove python-imaging dependency (Closes: #866427)
diff --git a/debian/control b/debian/control
index 1c84c57..d2d7ff2 100644
--- a/debian/control
+++ b/debian/control
@@ -10,7 +10,7 @@ Build-Depends-Indep: intltool, python-distutils-extra
 
 Package: gourmet
 Architecture: all
-Depends: ${misc:Depends}, ${python:Depends}, python-gtk2 (>= 2.22.0), python-reportlab, python-sqlalchemy, python-poppler, python-elib.intl, python-pil (>= 3.0.0~)
+Depends: ${misc:Depends}, ${python:Depends}, python-gtk2 (>= 2.22.0), python-reportlab, python-sqlalchemy, python-elib.intl, python-pil (>= 3.0.0~)
 Recommends: python-gst-1.0, python-gtkspell, python-beautifulsoup, python-lxml
 Description: Recipe organizer and shopping list generator
  Gourmet Recipe Manager is a gtk-based application to store, organize and
diff --git a/debian/rules b/debian/rules
index 0bc7a15..b6c05bf 100755
--- a/debian/rules
+++ b/debian/rules
@@ -10,6 +10,8 @@ override_dh_install:
 	dh_install --fail-missing
 
 	rm debian/gourmet/usr/share/doc/gourmet/LICENSE
+	# python-poppler has been removed from Debian
+	rm debian/gourmet/usr/lib/python2.*/dist-packages/gourmet/plugins/import_export/pdf_plugin/print_plugin.py
 
 override_dh_clean:
 	dh_clean po/gourmet.pot
-- 
2.14.1

Bug#886275: gourmet: Don't depend on python-poppler

[Jeremy Bicha]

Source: gourmet
Version: 0.17.4-4
Severity: serious
Tags: patch pending
X-Debbugs-CC: steve.langa...@ubuntu.com

I am uploading an NMU to the DELAYED/10 queue to drop the
python-poppler dependency and not install gourmet's printing plugin
since that seems more reasonable than dropping gourmet completely at
this point. (This was originally done by Steve Langasek in Ubuntu.)
Please let me know if I should speed up or slow down the upload.

Once the upload is accepted into Debian, we can lower the severity of
https://bugs.debian.org/879035 to important.

Note that the Debian GNOME would like to remove pygtk from Debian
soon, but I'll file a separate bug for that.

I'm attaching the debdiff in my follow-up email here.

Thanks,
Jeremy Bicha

Bug#885829: marked as done (lios: Lios crashing on start)

[Debian Bug Tracking System]

Your message dated Wed, 03 Jan 2018 17:49:58 +
with message-id 
and subject line Bug#885829: fixed in lios 2.7-1
has caused the Debian Bug report #885829,
regarding lios: Lios crashing on start
to be marked as done.

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

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


-- 
885829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885829
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lios
Version: 2.6-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Lios package is crashing on start, giving following error message :

lios
/usr/lib/python3/dist-packages/lios/ui/gtk/text_view.py:21: PyGIWarning: Gtk 
was imported without specifying a version first. Use gi.require_version('Gtk', 
'3.0') before import to ensure that the right version gets loaded.
  from gi.repository import Gtk
/usr/lib/python3/dist-packages/lios/ui/gtk/print_dialog.py:23: PyGIWarning: 
PangoCairo was imported without specifying a version first. Use 
gi.require_version('PangoCairo', '1.0') before import to ensure that the right 
version gets loaded.
  from gi.repository import PangoCairo
/usr/lib/python3/dist-packages/lios/cam.py:19: PyGIWarning: GstVideo was 
imported without specifying a version first. Use gi.require_version('GstVideo', 
'1.0') before import to ensure that the right version gets loaded.
  from gi.repository import GdkX11, GstVideo
/usr/lib/python3/dist-packages/lios/ui/gtk/terminal.py:21: PyGIWarning: Vte was 
imported without specifying a version first. Use gi.require_version('Vte', 
'2.91') before import to ensure that the right version gets loaded.
  from gi.repository import Gtk, GObject, Vte

(lios:21533): Gtk-WARNING **: Cannot connect attribute 'text' for cell renderer 
class 'lios+ui+gtk+tree_view+CellRendererToggle' since attribute does not exist
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/lios/main.py", line 1297, in 
make_preferences_effective
self.dict = 
dictionary.Dict(dictionary.dictionary_language_dict[languages[self.preferences.language]])
IndexError: list index out of range

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/lios", line 8, in 
linux_intelligent_ocr_solution()
  File "/usr/lib/python3/dist-packages/lios/main.py", line 331, in __init__
self.make_preferences_effective()
  File "/usr/lib/python3/dist-packages/lios/main.py", line 1318, in 
make_preferences_effective
pacman -S aspell-fr""").format(languages[self.preferences.language]))
IndexError: list index out of range
zsh: exit 1 lios


 Regards




*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: buster/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0 (SMP w/8 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 lios depends on:
ii  aspell-en2017.08.24-0-0.1
ii  espeak   1.48.04+dfsg-5+b1
ii  gir1.2-gst-plugins-base-1.0  1.12.4-1
ii  gir1.2-gtk-3.0   3.22.26-2
ii  gir1.2-vte-2.91  0.50.2-3
ii  imagemagick  8:6.9.7.4+dfsg-16
ii  imagemagick-6.q16 [imagemagick]  8:6.9.7.4+dfsg-16
ii  poppler-utils0.61.1-2
ii  python3  3.6.4-1
ii  python3-enchant  2.0.0-1
ii  python3-gi   3.26.1-2
ii  python3-sane 2.8.3-1+b1
ii  python3-speechd  0.8.8-1
ii  tesseract-ocr4.00~git2188-cdc35338-2

lios recommends no packages.

Versions of packages lios suggests:
ii  cuneiform  1.1.0+dfsg-6

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lios
Source-Version: 2.7-1

We believe that the bug you reported is fixed in the latest version of
lios, 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 

Bug#873370: marked as done (kmenuedit: All versions in repositories are extremely out of date.)

[Debian Bug Tracking System]

Your message dated Wed, 3 Jan 2018 14:32:33 -0300
with message-id <20180103173229.ojun3lyvtj7bp...@neoptolemo.gnuservers.com.ar>
and subject line Re: Bug#873370: kmenuedit: All versions in repositories are 
extremely out of date.
has caused the Debian Bug report #873370,
regarding kmenuedit: All versions in repositories are extremely out of date.
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.)


-- 
873370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873370
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kmenuedit
Version: 4:5.8.4-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The out of date kmenuedit saves configuration files in the wrong directories, 
causing most menu edits to be lost.
The newest version in repositories is 4.8.5. The newest version available from 
upstream is 5.10.5. The version of kmenuedit
in the repositories does not work with the version of plasma that is available 
in the repositories.

The recommended solution is to package a more up-to-date version for Debian and 
submit it. 

-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages kmenuedit depends on:
ii  kio 5.28.0-2
ii  libc6   2.24-11+deb9u1
ii  libkf5completion5   5.28.0-1
ii  libkf5configcore5   5.28.0-2
ii  libkf5configgui55.28.0-2
ii  libkf5configwidgets55.28.0-2
ii  libkf5coreaddons5   5.28.0-2
ii  libkf5dbusaddons5   5.28.0-1
ii  libkf5i18n5 5.28.0-2
ii  libkf5iconthemes5   5.28.0-2
ii  libkf5kdelibs4support5  5.28.0-1
ii  libkf5kiowidgets5   5.28.0-2
ii  libkf5service-bin   5.28.0-1
ii  libkf5service5  5.28.0-1
ii  libkf5sonnetcore5   5.28.0-2
ii  libkf5sonnetui5 5.28.0-2
ii  libkf5widgetsaddons55.28.0-3
ii  libkf5xmlgui5   5.28.0-1
ii  libqt5core5a5.7.1+dfsg-3+b1
ii  libqt5dbus5 5.7.1+dfsg-3+b1
ii  libqt5gui5  5.7.1+dfsg-3+b1
ii  libqt5widgets5  5.7.1+dfsg-3+b1
ii  libqt5xml5  5.7.1+dfsg-3+b1
ii  libstdc++6  6.3.0-18

Versions of packages kmenuedit recommends:
ii  khotkeys  4:5.8.6-1

kmenuedit suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---

¡Hola Brice!

El 2017-08-26 a las 21:51 -0600, Brice Hunt escribió:
Package: kmenuedit 
Version: 4:5.8.4-1 
Severity: grave 


Don't abuse the bug severities.


Justification: renders package unusable


The out of date kmenuedit saves configuration files in the wrong directories, causing most menu edits to be lost. 
The newest version in repositories is 4.8.5. The newest version available from upstream is 5.10.5. The version of kmenuedit 
in the repositories does not work with the version of plasma that is available in the repositories.



The recommended solution is to package a more up-to-date version for Debian and 
submit it.


Closing the issue as, it's not really an issue for 4:5.8.4-1 (when using with 
plasma 5.8) nor a current issue with plasma 5.10.


Happy hacking,
--
"By definition, when you are investigating the unknown, you do not know what
you will find"
-- The Ultimate Principle
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature
--- End Message ---

Bug#873370: kmenuedit: All versions in repositories are extremely out of date.

[Maximiliano Curia]

¡Hola Brice!

El 2017-08-26 a las 21:51 -0600, Brice Hunt escribió:
Package: kmenuedit 
Version: 4:5.8.4-1 
Severity: grave 


Don't abuse the bug severities.


Justification: renders package unusable


The out of date kmenuedit saves configuration files in the wrong directories, causing most menu edits to be lost. 
The newest version in repositories is 4.8.5. The newest version available from upstream is 5.10.5. The version of kmenuedit 
in the repositories does not work with the version of plasma that is available in the repositories.



The recommended solution is to package a more up-to-date version for Debian and 
submit it.


Closing the issue as, it's not really an issue for 4:5.8.4-1 (when using with 
plasma 5.8) nor a current issue with plasma 5.10.


Happy hacking,
--
"By definition, when you are investigating the unknown, you do not know what
you will find"
-- The Ultimate Principle
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Processed: tagging 885829

[Debian Bug Tracking System]

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

> tags 885829 + pending
Bug #885829 [lios] lios: Lios crashing on start
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#869484: marked as done (haskell-stack: << build dependencies on packages with a more recent version)

[Debian Bug Tracking System]

Your message dated Wed, 03 Jan 2018 17:04:39 +
with message-id 
and subject line Bug#869484: fixed in haskell-stack 1.5.1-1
has caused the Debian Bug report #869484,
regarding haskell-stack: << build dependencies on packages with a more recent 
version
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.)


-- 
869484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869484
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-stack
Version: 1.1.2-8
Severity: serious

The following packages have unmet dependencies:
 builddeps:haskell-stack : Depends: libghc-hpack-dev (< 0.15) but 0.17.1-1 is 
to be installed
   Depends: libghc-hspec-dev (< 2.3) but 2.4.3-2 is to 
be installed
   Depends: libghc-http-client-dev (< 0.5) but 
0.5.7.0-1+b3 is to be installed
   Depends: libghc-http-client-tls-dev (< 0.3) but 
0.3.5.1-1+b3 is to be installed
   Depends: libghc-http-conduit-dev (< 2.2) but 
2.2.3.2-1 is to be installed
   Depends: libghc-optparse-applicative-dev (< 0.13) 
but 0.13.2.0-1+b1 is to be installed
--- End Message ---
--- Begin Message ---
Source: haskell-stack
Source-Version: 1.5.1-1

We believe that the bug you reported is fixed in the latest version of
haskell-stack, 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 869...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated 
haskell-stack 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: Tue, 12 Dec 2017 18:01:42 +0100
Source: haskell-stack
Binary: haskell-stack
Architecture: source
Version: 1.5.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Gianfranco Costamagna 
Description:
 haskell-stack - ${haskell:ShortDescription}${haskell:ShortBlurb}
Closes: 869484
Changes:
 haskell-stack (1.5.1-1) unstable; urgency=medium
 .
   * New upstream release, drop patches
 (Closes: #869484)
   * Patch to avoid mintty dependency (thanks Clint for the hint)
   * Update copyright file
   * Update control file dependencies
Checksums-Sha1:
 6bcd3fa9d16503e66991092e7ba6f840e5d4a371 10876 haskell-stack_1.5.1-1.dsc
 a30cc7f41b7851d41b69f782f7d07773f64d67a3 539383 haskell-stack_1.5.1.orig.tar.gz
 b96cf7a7186782fcccd7b648791a7ee2f0bae975 5236 
haskell-stack_1.5.1-1.debian.tar.xz
 dad2e9135c28d055fca688863ea42e773a1582df 9224 
haskell-stack_1.5.1-1_source.buildinfo
Checksums-Sha256:
 85027e8e8bacf48bfad794fe8e1b6f7d2980c39ae861b3fbb83bab64c37745ec 10876 
haskell-stack_1.5.1-1.dsc
 dd38cb8407f2ab46e99d88b1c29b3ad75ea6dff9e211438fe0dff54626a788c3 539383 
haskell-stack_1.5.1.orig.tar.gz
 74da6c50e752c375cdaea747ba4238d1e684ebfb55ab0494596a5a76248b752e 5236 
haskell-stack_1.5.1-1.debian.tar.xz
 fce2d14b0111769a9e010a9cafe7f25b1437631e79284835b0b38e02d8166d71 9224 
haskell-stack_1.5.1-1_source.buildinfo
Files:
 ce135b48631d3791e3aaa41a650137fb 10876 haskell optional 
haskell-stack_1.5.1-1.dsc
 b325c27f55cb064086fe3b51eb74a60e 539383 haskell optional 
haskell-stack_1.5.1.orig.tar.gz
 9f559f0f951769faf4a29bb01cea4f06 5236 haskell optional 
haskell-stack_1.5.1-1.debian.tar.xz
 65df26fbd05e22af61f456967da6afec 9224 haskell optional 
haskell-stack_1.5.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJaTQr3AAoJEPNPCXROn13ZywsP/RHHGBa8nKZ5rltN6PHQNd1F
n9YV7GNh7ttCJ7e9tlefFOaB/79zc2OLw4hrU3gLhUoIfziZBttZyYzrOsv7fwt1
f2gquXLQMGkLJdDWrMUq+dYoSeOCfstkvcn0u7GCeCgTORz0zgZM3dffl8cPJ7AW
unx1wRBxKOZc2sBP4daUCtxDkIm8M480IW2V23Gz9YSgQvgpsN3n1z2NNgCwSxYW
oiJCFncbee0xTZAkTSHUjb8XweyLQ4mtp3zpZWnjcnQQgHhaeKNmpy5XQnfZLtzo
15uN3sT8Og2wke99WfgpsU8eOvuIITKJIOTW7hxeaSX+5Umg8wKLuUWvbMs1TP8g
VHVTDTJ6gcY4AH3Ds0STS6qeQCCI8OFuB88Mip8Y/fa2UiX0LObBrbKQKa4F5WPo
AmIvGOPZQpupUoecvWlpb25VrcsWg357M+XCGRyZhDXEtIUkGptK9xGa9HoAUFB1
5BTEPZ3kgcvaoLhJoC/DjBJD670GG8S3PZ4MwCbxVM5I9x0a+F1MGA4LP4xw30LB

Bug#878009: marked as done (easytag fails to add tags to .ogg files)

[Debian Bug Tracking System]

Your message dated Wed, 03 Jan 2018 17:04:24 +
with message-id 
and subject line Bug#855251: fixed in easytag 2.4.3-2
has caused the Debian Bug report #855251,
regarding easytag fails to add tags to .ogg files
to be marked as done.

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

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


-- 
855251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855251
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: easytag
Severity: important
Tags: upstream

Dear Maintainer,

  Easytag is not adding audio tags to .ogg files. Upon trying to modify tags of
an already tagged .ogg file, it DELETES all tags, leaving everything blank.

What works? .mp3 files are edited successfully. I can see the Nautilus window
flashing (updating contents) as soon as I press the "save changes" icon in
Easytag. But when the file is .ogg, the Nautilus screen where the file is
remains unchanged, probably a sign that the component that deals with vorbis
files is not acting/working.

I tried newer packages from Fedora Workstation 26 and Arch Linux before filing
this bug report, and the result is the same in all of them. Therefore I'm
assuming it concerns upstream developers.




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

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



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

Kernel: Linux 4.9.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), 
LANGUAGE=pt_BR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: easytag
Source-Version: 2.4.3-2

We believe that the bug you reported is fixed in the latest version of
easytag, 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 855...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
James Cowgill  (supplier of updated easytag 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: Wed, 03 Jan 2018 16:39:00 +
Source: easytag
Binary: easytag easytag-nautilus
Architecture: source
Version: 2.4.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: James Cowgill 
Description:
 easytag- GTK+ editor for audio file tags
 easytag-nautilus - Nautilus extension for easytag
Closes: 855251 886137
Changes:
 easytag (2.4.3-2) unstable; urgency=medium
 .
   * debian/control:
 - Use debhelper compat 11.
 - Bump standards version.
   * debian/patches:
 - Add patch to remove use of gdk-pixbuf-pixdata.
   Thanks to Helmut Grohne. (Closes: #886137)
   * debian/rules:
 - Remove --disable-silent-rules which is used by default.
 - Disable OGG, OPUS and Speex. (Closes: #855251)
Checksums-Sha1:
 1b9a48d0710a9f0a14d3c38b992bac12b6383de3 2469 easytag_2.4.3-2.dsc
 bded95565a3200e3509c83f58b8af34392898489 12108 easytag_2.4.3-2.debian.tar.xz
 76a1af0f839ddc3d6a2ce79dff2c095e44f5f9a5 6908 easytag_2.4.3-2_source.buildinfo
Checksums-Sha256:
 08fdbf8987cb56f9ca21c2f59abee0a65ce1601397e62dd07d73a0be361f71eb 2469 
easytag_2.4.3-2.dsc
 715c59286dc74063e98e004078056810310898cf1d8aa1f31ed19094c8aa78dd 12108 
easytag_2.4.3-2.debian.tar.xz
 fb2bf976b4cc0e9e0b32f7849d4d0f8a5cd589741c69905c77a2e1210c10afc7 6908 
easytag_2.4.3-2_source.buildinfo
Files:
 41ebdb90d0aa88f3809a7ce8ac6f7a73 2469 sound optional easytag_2.4.3-2.dsc
 36af3d112648ef0b1b63a3d379bd66fa 12108 sound optional 
easytag_2.4.3-2.debian.tar.xz
 05664711f89e277d3506b609b5d7c2c3 6908 sound optional 
easytag_2.4.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#855251: marked as done (easytag corrupt ogg files)

[Debian Bug Tracking System]

Your message dated Wed, 03 Jan 2018 17:04:24 +
with message-id 
and subject line Bug#855251: fixed in easytag 2.4.3-2
has caused the Debian Bug report #855251,
regarding easytag corrupt ogg files
to be marked as done.

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

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


-- 
855251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855251
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: easytag
Version: 2.4.3-1
Severity: normal

Dear Maintainer,
I have a ogg file encoded from a live cd, I split it to single tracks with 
oggsplt and then tag the tracks with easytag.
When I play the files I hear a click at file change.
The click is not present in files before the tagging and if I tag with kid3.

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (900, 'testing'), (500, 'stable-updates'), (500, 'unstable'), 
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages easytag depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2
ii  libc62.24-9
ii  libflac8 1.3.2-1
ii  libgcc1  1:6.3.0-6
ii  libgdk-pixbuf2.0-0   2.36.4-1
ii  libglib2.0-0 2.50.2-2
ii  libgtk-3-0   3.22.7-2
ii  libid3-3.8.3v5   3.8.3-16.2
ii  libid3tag0   0.15.1b-12
ii  libogg0  1.3.2-1
ii  libopus0 1.2~alpha2-1
ii  libopusfile0 0.8-1+b1
ii  libspeex11.2~rc1.2-1
ii  libstdc++6   6.3.0-6
ii  libtag1v51.11.1+dfsg.1-0.1
ii  libvorbis0a  1.3.5-4
ii  libvorbisfile3   1.3.5-4
ii  libwavpack1  5.0.0-2

Versions of packages easytag recommends:
pn  gnome-icon-theme  
pn  gvfs  
pn  yelp  

Versions of packages easytag suggests:
pn  easytag-nautilus  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: easytag
Source-Version: 2.4.3-2

We believe that the bug you reported is fixed in the latest version of
easytag, 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 855...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
James Cowgill  (supplier of updated easytag 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: Wed, 03 Jan 2018 16:39:00 +
Source: easytag
Binary: easytag easytag-nautilus
Architecture: source
Version: 2.4.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: James Cowgill 
Description:
 easytag- GTK+ editor for audio file tags
 easytag-nautilus - Nautilus extension for easytag
Closes: 855251 886137
Changes:
 easytag (2.4.3-2) unstable; urgency=medium
 .
   * debian/control:
 - Use debhelper compat 11.
 - Bump standards version.
   * debian/patches:
 - Add patch to remove use of gdk-pixbuf-pixdata.
   Thanks to Helmut Grohne. (Closes: #886137)
   * debian/rules:
 - Remove --disable-silent-rules which is used by default.
 - Disable OGG, OPUS and Speex. (Closes: #855251)
Checksums-Sha1:
 1b9a48d0710a9f0a14d3c38b992bac12b6383de3 2469 easytag_2.4.3-2.dsc
 bded95565a3200e3509c83f58b8af34392898489 12108 easytag_2.4.3-2.debian.tar.xz
 76a1af0f839ddc3d6a2ce79dff2c095e44f5f9a5 6908 easytag_2.4.3-2_source.buildinfo
Checksums-Sha256:
 08fdbf8987cb56f9ca21c2f59abee0a65ce1601397e62dd07d73a0be361f71eb 2469 
easytag_2.4.3-2.dsc
 715c59286dc74063e98e004078056810310898cf1d8aa1f31ed19094c8aa78dd 12108 

Bug#871091: marked as done (khotkeys: FTBFS: make[4]: *** No rule to make target 'app/org.kde.khotkeys.xml', needed by 'kcm_hotkeys/khotkeys_interface.cpp'. Stop.)

[Debian Bug Tracking System]

Your message dated Wed, 3 Jan 2018 13:56:48 -0300
with message-id <20180103165645.n3vqxmgw2pyzx...@neoptolemo.gnuservers.com.ar>
and subject line Re: Bug#871091: khotkeys: FTBFS: make[4]: *** No rule to make 
target 'app/org.kde.khotkeys.xml', needed by 
'kcm_hotkeys/khotkeys_interface.cpp'. Stop.
has caused the Debian Bug report #871091,
regarding khotkeys: FTBFS: make[4]: *** No rule to make target 
'app/org.kde.khotkeys.xml', needed by 'kcm_hotkeys/khotkeys_interface.cpp'. 
Stop.
to be marked as done.

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

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


-- 
871091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871091
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: khotkeys
Version: 4:5.8.6-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
> make[4]: *** No rule to make target 'app/org.kde.khotkeys.xml', needed by 
> 'kcm_hotkeys/khotkeys_interface.cpp'.  Stop.
> make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> CMakeFiles/Makefile2:3712: recipe for target 
> 'kcm_hotkeys/CMakeFiles/kcm_hotkeys_autogen.dir/all' failed
> make[3]: *** [kcm_hotkeys/CMakeFiles/kcm_hotkeys_autogen.dir/all] Error 2

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/khotkeys_5.8.6-1_unstable.log

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

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

Version: 4:5.10.5-2

¡Hola Lucas!

I'm closing this report with the version currently in sid, as the buildd 
clearly build this package fine.


Happy hacking,
--
"If a thing is done wrong often enough, it becomes right" -- Leahy's Law
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature
--- End Message ---

Bug#855251: easytag corrupt ogg files

[James Cowgill]

Control: clone -1 -2
Control: notfound -2 2.4.3-1
Control: found -2 2.4.3-2
Control: severity -2 normal
Control: tags -2 - pending
Control: retitle -2 easytag: re-enable ogg after corruption bug is fixed

Hi,

On 16/02/17 01:02, Samuele Battarra wrote:
> Package: easytag
> Version: 2.4.3-1
> Severity: normal
> 
> Dear Maintainer,
> I have a ogg file encoded from a live cd, I split it to single tracks with 
> oggsplt and then tag the tracks with easytag.
> When I play the files I hear a click at file change.
> The click is not present in files before the tagging and if I tag with kid3.

As you might have noticed, I have decided that the best way to fix this
is to disable support for OGG and related media types in easytag for the
time being. Solving this bug is apparently quite complex and while the
upstream bug has been open for over a year, there has not been much
progress on it. I think it is better to have some version in buster
(which does not mangle your media files) than nothing at all.

I have cloned this bug to remind me to re-enable ogg support once the
corruption bug is fixed.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Processed (with 6 errors): Re: Bug#855251: easytag corrupt ogg files

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #855251 [easytag] easytag corrupt ogg files
Bug #878009 [easytag] easytag fails to add tags to .ogg files
Failed to clone 855251: Bug is marked as being merged with others. Use an 
existing clone.

> notfound -2 2.4.3-1
Failed to remove found on -2: The 'bug' parameter ("-2") to 
Debbugs::Control::set_found did not pass regex check
.

> found -2 2.4.3-2
Failed to add found on -2: The 'bug' parameter ("-2") to 
Debbugs::Control::set_found did not pass regex check
.

> severity -2 normal
Failed to set severity of Bug -2 to normal: The 'bug' parameter ("-2") to 
Debbugs::Control::set_severity did not pass regex check
.

> tags -2 - pending
Failed to alter tags of Bug -2: The 'bug' parameter ("-2") to 
Debbugs::Control::set_tag did not pass regex check
.

> retitle -2 easytag: re-enable ogg after corruption bug is fixed
Failed to set the title of -2: The 'bug' parameter ("-2") to 
Debbugs::Control::set_title did not pass regex check
.


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

Processed: Bug#855251 marked as pending

[Debian Bug Tracking System]

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

> tag 855251 pending
Bug #855251 [easytag] easytag corrupt ogg files
Bug #878009 [easytag] easytag fails to add tags to .ogg files
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#855251: marked as pending

[James Cowgill]

tag 855251 pending
thanks

Hello,

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

http://anonscm.debian.org/git/pkg-multimedia/easytag.git/commit/?id=82a46fb

---
commit 82a46fbc12f28e5979c000c2bb457d252fec16ae
Author: James Cowgill 
Date:   Wed Jan 3 16:41:00 2018 +

Upload to unstable

diff --git a/debian/changelog b/debian/changelog
index 2469f62..a8df5e1 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,16 @@
-easytag (2.4.3-2) UNRELEASED; urgency=medium
+easytag (2.4.3-2) unstable; urgency=medium
 
-  *
+  * debian/control:
+- Use debhelper compat 11.
+- Bump standards version.
+  * debian/patches:
+- Add patch to remove use of gdk-pixbuf-pixdata.
+  Thanks to Helmut Grohne. (Closes: #886137)
+  * debian/rules:
+- Remove --disable-silent-rules which is used by default.
+- Disable OGG, OPUS and Speex. (Closes: #855251)
 
- -- James Cowgill   Tue, 02 Jan 2018 22:48:37 +
+ -- James Cowgill   Wed, 03 Jan 2018 16:39:00 +
 
 easytag (2.4.3-1) unstable; urgency=medium
 

Bug#886224: printer-driver-cups-pdf: Virtual pdf printer error: no output and config problem

[Rudolf Polzer]

You are right - the cups pdf printer is now working.

I changed the pdf output directory a long time ago before using
Apparmor, but now Apparmor needs to allow rw access to this directory.

So I updated /etc/apparmor.d/usr.sbin.cupsd
and the pdf printing works.

The config problem remains unsolved.

Rudolf Polzer

Bug#884196: marked as done (debtags FTBFS with pyflakes 1.6.0-1)

[Debian Bug Tracking System]

Your message dated Wed, 03 Jan 2018 16:19:15 +
with message-id 
and subject line Bug#884196: fixed in debtags 2.1.5
has caused the Debian Bug report #884196,
regarding debtags FTBFS with pyflakes 1.6.0-1
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.)


-- 
884196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884196
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debtags
Version: 2.1.4
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/debtags.html

...
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:184: python3.6 setup.py test 
running test
running egg_info
creating debtags.egg-info
writing debtags.egg-info/PKG-INFO
writing dependency_links to debtags.egg-info/dependency_links.txt
writing top-level names to debtags.egg-info/top_level.txt
writing manifest file 'debtags.egg-info/SOURCES.txt'
reading manifest file 'debtags.egg-info/SOURCES.txt'
writing manifest file 'debtags.egg-info/SOURCES.txt'
running build_ext
test_pyflakes_clean (test.test_pyflakes.TestPyflakesClean) ... 
/build/1st/debtags-2.1.4/debtags:634:74: invalid syntax
print("{}: {}".format(pkg, ", ".join(sorted(tags))), file=out)
 ^
/build/1st/debtags-2.1.4/build/scripts-3.6/debtags:634:74: invalid syntax
print("{}: {}".format(pkg, ", ".join(sorted(tags))), file=out)
 ^
FAIL

==
FAIL: test_pyflakes_clean (test.test_pyflakes.TestPyflakesClean)
--
Traceback (most recent call last):
  File "/build/1st/debtags-2.1.4/test/test_pyflakes.py", line 15, in 
test_pyflakes_clean
self.assertEqual(subprocess.call(["pyflakes", basedir]), 0)
AssertionError: 1 != 0

--
Ran 1 test in 0.306s

FAILED (failures=1)
Test failed: 
error: Test failed: 
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: 
python3.6 setup.py test 
dh_auto_test: pybuild --test -i python{version} -p 3.6 returned exit code 13
debian/rules:8: recipe for target 'build' failed
make: *** [build] Error 25
--- End Message ---
--- Begin Message ---
Source: debtags
Source-Version: 2.1.5

We believe that the bug you reported is fixed in the latest version of
debtags, 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 884...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Enrico Rossi  (supplier of updated debtags 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: Wed, 03 Jan 2018 16:30:46 +0100
Source: debtags
Binary: debtags
Architecture: source
Version: 2.1.5
Distribution: unstable
Urgency: low
Maintainer: Enrico Rossi 
Changed-By: Enrico Rossi 
Description:
 debtags- Debian Package Tags support tools
Closes: 884196
Changes:
 debtags (2.1.5) unstable; urgency=low
 .
   * Fix FTBFS with pyflakes 1.6.0-1. (Closes: #884196)
   * std-version to 4.1.3 checked and applied.
Checksums-Sha1:
 4d3759cea2c851587a4ba885771395a2003216b8 1384 debtags_2.1.5.dsc
 8c7423eac4b2ee111421c160d05dfa97097dbab3 581612 debtags_2.1.5.tar.xz
 3d2a8766bc46bdd8c0fd55d185177dc4d9c82fb6 5546 debtags_2.1.5_source.buildinfo
Checksums-Sha256:
 94c4d5810f18eb5a32af0ae13b4c62277d4922b6e4bc2254e57618c81fd9d2d9 1384 
debtags_2.1.5.dsc
 60f6960e3458577f16fa3946e2c0564f870316ec9eeddfdbac5e8ec57ce9e296 581612 
debtags_2.1.5.tar.xz
 5fee1a79f52aa78829fab16bb363a349005d5e51710486721438f0aa6e431a2d 5546 
debtags_2.1.5_source.buildinfo
Files:
 c33ff278807b871284b5378d143b8a40 1384 admin optional debtags_2.1.5.dsc
 31a578745b15e86dc31198cfec871ded 581612 admin optional debtags_2.1.5.tar.xz
 7faf7142b0a38e55b13df37a623bccf7 5546 admin optional 
debtags_2.1.5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEb47PIpL0wGGtjB3rx8F83ljNAVQFAlpM/T8ACgkQx8F83ljN

Bug#885793: #885793: tldr-py,tldr: File collision when installing together: /usr/bin/tldr (and maybe further files)

[Clint Adams]

On Wed, Jan 03, 2018 at 04:48:12PM +0100, Ondrej Novy wrote:
> I prefer to use update-alternatives.
> 
> What do you think Clint?

I haven't looked at the different implementations but
alternatives sounds like the right answer to me.

Bug#790176: guake gtk3

[Daniel Echeverry]

Hi

The upstream are working hard to port  guake to gtk3, I hope upload
the new version soon.

Regards!

-- 
Daniel Echeverry
http://wiki.debian.org/DanielEcheverry
http://rinconinformatico.net
Linux user: #477840
Debian user

Bug#885793: #885793: tldr-py,tldr: File collision when installing together: /usr/bin/tldr (and maybe further files)

[Ondrej Novy]

Hi,

I prefer to use update-alternatives.

What do you think Clint?

-- 
Best regards
 Ondřej Nový

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

Bug#878216: Info received (Regression in linux in jessie-proposed-updates)

[vincent.ta...@amen.fr]

Hi again,

As problem is too in Vanilla flavour, must we open a ticket directly at 
kernel.org ? (Or should we wait some answer here first ?)


Best regards
Vince

Bug#886117: FTBFS: most of testsuite

[Adam Borowski]

On Wed, Jan 03, 2018 at 06:29:06PM +1000, Alexander Zangerl wrote:
> On Tue, 02 Jan 2018 14:40:33 +0100, Adam Borowski writes:
> >I'm afraid that your package fails to build on current unstable, failing the
> >vast majority of tests:
> 
> looks like every one of the failed tests fails for the same reason,
> (which to me indicates rather a failure of the test suite
> than a failure of duplicity itself):
> 
>   File "/<>/testing/__init__.py", line 88, in unpack_testfiles
> assert not os.system("tar xzf testfiles.tar.gz > /dev/null 2>&1")
> AssertionError
> 
> i'll go dig deeper when i find the time, but i've got no clue how
> why that could be a platform-specific failure.

It's not: I tried on armhf (many times) and amd64 (once).

But, trying more:

machine   archresult

armhf armhf   ✗

arm64 arm64   ✗
arm64 armhf   ✗

amd64 amd64   ✗
amd64 i386✗
amd64 x32 ✗
amd64 armhf (qemu-user)   ✗
amd64 arm64 (qemu-user)   ✗
amd64 mips  (qemu-user)   ✗

i386  i386✓

The machine that succeeded differs by:
* (slightly) kernel: 4.15-rc3 vs 4.15-rc6 on the rest
* decade of manufacture (a dingy pre-NX Pentium4)
* host release: stretch vs unstable on the rest
* sbuild backend: dir vs btrfs on the rest
* underlying filesystem: ext4...

Working hypothesis so far is that the testsuite fails on btrfs; I won't be
able to confirm until the evening.


Meow!
-- 
// If you believe in so-called "intellectual property", please immediately
// cease using counterfeit alphabets.  Instead, contact the nearest temple
// of Amon, whose priests will provide you with scribal services for all
// your writing needs, for Reasonable And Non-Discriminatory prices.

Processed: severity of 885111 is important

[Debian Bug Tracking System]

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

> severity 885111 important
Bug #885111 [kdepim-runtime] kdepim-runtime: kdepim-runtime depends on 
libkolab-dev
Bug #886107 [kdepim-runtime] kdepim: depends on a lot of developer packages
Severity set to 'important' from 'serious'
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#885111: Note that this bug prevents to install libssl-dev and force libssl1.0-dev => severity should be raised

[Pino Toscano]

Dear user,

On mercoledì 3 gennaio 2018 14:54:08 CET Eric Valette wrote:
> severity 885111 serious

Please do not bump the severity of bugs with random criterias.

Thanks,
-- 
Pino Toscano

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

Bug#884466: mesa: firefox, thunderbird, chromium don't start with mesa 17.3.0-1

[Michal Suchanek]

Package: libglx-mesa0
Followup-For: Bug #884466

This works for me with [AMD/ATI] Baffin [Radeon RX 460] (rev cf)

I can open chromium and firefox just fine.

-- System Information:
Debian Release: 9.3
  APT prefers stable
  APT policy: (900, 'stable'), (505, 'oldstable'), (500, 'oldoldstable'), (500, 
'testing'), (171, 'unstable'), (151, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages libglx-mesa0:amd64 depends on:
ii  libc62.24-11+deb9u1
ii  libdrm2  2.4.89-1
ii  libexpat12.2.0-2+deb9u1
ii  libgl1-mesa-dri  17.3.1-1
ii  libglapi-mesa17.3.1-1
ii  libx11-6 2:1.6.4-3
ii  libx11-xcb1  2:1.6.4-3
ii  libxcb-dri2-01.12-1
ii  libxcb-dri3-01.12-1
ii  libxcb-glx0  1.12-1
ii  libxcb-present0  1.12-1
ii  libxcb-sync1 1.12-1
ii  libxcb-xfixes0   1.12-1
ii  libxcb1  1.12-1
ii  libxdamage1  1:1.1.4-2+b3
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxshmfence11.2-1+b2
ii  libxxf86vm1  1:1.1.4-1+b2
ii  zlib1g   1:1.2.8.dfsg-5

libglx-mesa0:amd64 recommends no packages.

libglx-mesa0:amd64 suggests no packages.

-- no debconf information

Bug#886224: printer-driver-cups-pdf: Virtual pdf printer error: no output and config problem

[Martin-Éric Racine]

2018-01-03 11:51 GMT+02:00 Rudolf Polzer :
> Package: printer-driver-cups-pdf
> Version: 3.0.1-4
> Severity: grave
> Justification: renders package unusable
>
>
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.14.0-2-amd64 (SMP w/4 CPU cores)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= 
> (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages printer-driver-cups-pdf depends on:
> ii  cups2.2.6-4
> ii  cups-client 2.2.6-4
> ii  ghostscript 9.22~dfsg-1
> ii  libc6   2.25-6
> ii  libcups22.2.6-4
> ii  libpaper-utils  1.1.24+nmu5
>
> printer-driver-cups-pdf recommends no packages.
>
> Versions of packages printer-driver-cups-pdf suggests:
> pn  system-config-printer  
>
> -- no debconf information
>
>
> Bug description:
>
> The cups pdf printer produces no pdf output file.
>
> After deleting the pdf printer, the add printer function does not work as 
> expected:
> After selecting "Generic" as printer make, no pdf printer model is selectable.
> I instead selected one of the existing ppd files in /usr/share/ppd/cups-pdf
> but this did not make the pdf printer work.
>
> The bug started by my recent update from cups-pdf, where pdf printing did 
> work,
> to printer-driver-cups-pdf.

I notice that you're using AppArmor.  Please check what the README
says about this.

Martin-Éric

Processed (with 1 error): Rize severity correctly

[Debian Bug Tracking System]

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

> severity 885111 serious
Bug #885111 [kdepim-runtime] kdepim-runtime: kdepim-runtime depends on 
libkolab-dev
Bug #886107 [kdepim-runtime] kdepim: depends on a lot of developer packages
Severity set to 'serious' from 'wishlist'
Severity set to 'serious' from 'wishlist'
> --eric
Unknown command or malformed arguments to command.
>
End of message, stopping processing here.

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

Processed: retitle 886024 to dh-elpa: make maintainer scripts more robust, severity of 886024 is important

[Debian Bug Tracking System]

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

> retitle 886024 dh-elpa: make maintainer scripts more robust
Bug #886024 [dh-elpa] dh-elpa: make maintainer scripts more robust, severity it 
importnat
Changed Bug title to 'dh-elpa: make maintainer scripts more robust' from 
'dh-elpa: make maintainer scripts more robust, severity it importnat'.
> severity 886024 important
Bug #886024 [dh-elpa] dh-elpa: make maintainer scripts more robust
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Processed: reassign 886024 to dh-elpa ...

[Debian Bug Tracking System]

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

> reassign 886024 dh-elpa
Bug #886024 [emacsen-common, markdown-mode] emacsen-addon package installation 
may never comes to an end
Bug reassigned from package 'emacsen-common, markdown-mode' to 'dh-elpa'.
Ignoring request to alter found versions of bug #886024 to the same values 
previously set
Ignoring request to alter fixed versions of bug #886024 to the same values 
previously set
> retitle 886024 dh-elpa: make maintainer scripts more robust, severity it 
> importnat
Bug #886024 [dh-elpa] emacsen-addon package installation may never comes to an 
end
Changed Bug title to 'dh-elpa: make maintainer scripts more robust, severity it 
importnat' from 'emacsen-addon package installation may never comes to an end'.
> thanks
Stopping processing here.

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

Bug#785562: Status update

[Dr. Tobias Quathamer]

Am 01.01.2018 um 17:55 schrieb 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:
[...]
>>> 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.

Hi again,

thanks for your input. I've looked again at the package, and upstream
did rename most relevant parts to "openshot-qt".

The program itself (in /usr/bin) is called "openshot-qt", the manpages
are, the MIME type is, and so on.

Therefore, I think the best option would be to upload the empty
transitional package "openshot".

If I reuse the package name, the package would be called openshot, but
the executable would be openshot-qt. So the upgrade from stretch would
work, but the "openshot" executable would be gone.

This is a bit confusing, IMHO.

So if nobody objects or has a better idea, I'll upload the transitional
package in the next couple of days.

Regards,
Tobias



signature.asc
Description: OpenPGP digital signature

Bug#886024: split off anything-el related part

[era eriksson]

On Wed, Jan 3, 2018, at 03:45, H.-Dirk Schmitt wrote:
> On Mi, 2018-01-03 at 02:06 +0200, era eriksson wrote:
> > Code outline for an emacs batch wrapper
>
> I do not insist on bash – you are free to fix it in any programming
> language ;-)

A fair amont of work has gone into making the core system work without
Bash. If you want this proposal to succeed, it woud seem important to
demonstrate a good understanding of the surrounding system and the needs
of our users.
I'll be happy to try to convert this script into POSIX sh or at least
Dash-compatible code if the maintainers agree that this is a good way
forward, but so far, my impression is that they are unconvinced, or
perhaps just waiting to see if this evolves into a serious proposal.
The compilation bug you originally reported does not seem to affect
other users, and at least I am still wondering if there is a way to
trigger it which is likely to happen again.
However, I think it would be useful to improve package compilation,
with an eye towards making bug reporting easier and eventually
somewhat more scriptable, perhaps with some way for Ubuntu's Apport
system and eventually even some Debian-native replacement to hook in
and fetch logs etc.
I'm just thinking out loud here; sorry if this comes across as a rant.

/* era */

--
If this were a real .signature, it would suck less.  Well, maybe not.

Bug#858736: marked as done (xul-ext-gcontactsync: Depends on icedove or iceape but not thunderbird)

[Debian Bug Tracking System]

Your message dated Wed, 03 Jan 2018 11:04:43 +
with message-id 
and subject line Bug#858736: fixed in gcontactsync 2.0.13-1
has caused the Debian Bug report #858736,
regarding xul-ext-gcontactsync: Depends on icedove or iceape but not thunderbird
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.)


-- 
858736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858736
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xul-ext-gcontactsync
Version: 2.0.5-1
Severity: normal

Dear Maintainer,

icedove is now a transitional package for thunderbird. xul-ext-gcontactsync
works with thunderbird without issue; however the dependency information does
not list thunderbird, so the icedove transitional package must be installed in
order to use xul-ext-gcontactsync with thunderbird.

Provides: gcontactsync, iceape-gcontactsync, icedove-gcontactsync
Depends: icedove (>= 17.0) | iceape (>= 2.14)
Breaks: iceape (>> 2.35+), iceape (<< 2.14), icedove (<< 17.0)
Enhances: iceape, icedove

Also, many of the files for this package are installed under
'/usr/lib/icedove/extensions'.

-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages xul-ext-gcontactsync depends on:
ii  icedove1:45.8.0-2
ii  thunderbird [icedove]  1:45.8.0-2

xul-ext-gcontactsync recommends no packages.

xul-ext-gcontactsync suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gcontactsync
Source-Version: 2.0.13-1

We believe that the bug you reported is fixed in the latest version of
gcontactsync, 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 858...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Meskes  (supplier of updated gcontactsync 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: Wed, 03 Jan 2018 11:40:19 +0100
Source: gcontactsync
Binary: xul-ext-gcontactsync
Architecture: source all
Version: 2.0.13-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Mozilla Extension Maintainers 

Changed-By: Michael Meskes 
Description:
 xul-ext-gcontactsync - synchronize contacts from Gmail into Thunderbird
Closes: 814669 858736
Changes:
 gcontactsync (2.0.13-1) unstable; urgency=medium
 .
   * Updated watch file.
   * New upstream version 2.0.13 (Closes: #814669)
   * Make package work with Thunderbird instead of Icedove. (Closes: #858736)
   * Bumped Standards-Version to 4.1.3, no changes needed.
   * Switched to debhelper 11.
Checksums-Sha1:
 6d066c4bdfb09cff6b78b50d77f3477de751d7be 2066 gcontactsync_2.0.13-1.dsc
 8b8d08e5e63a01a549e21db4b9f493d822577f51 177000 gcontactsync_2.0.13.orig.tar.xz
 4e2ee84f583dc422a12b3a201817eca2b2dde037 15084 
gcontactsync_2.0.13-1.debian.tar.xz
 5ff3aa5ba78cc1221c616773583b4610e9c279b7 6770 
gcontactsync_2.0.13-1_amd64.buildinfo
 4243cea25efad54b265788b29eac5aa17bc57990 195692 
xul-ext-gcontactsync_2.0.13-1_all.deb
Checksums-Sha256:
 75c04bd356fcbd333f35eb7b9fe9ae0dac523f5b3724d107937ba753bea76508 2066 
gcontactsync_2.0.13-1.dsc
 cc4df119da63e3b2d6dfb5fccaafc3889ae6abf97b849dca44b7908fd8a2f015 177000 
gcontactsync_2.0.13.orig.tar.xz
 0400cf8f82f6817ae350b472517b3ed8454bfee81fbb1ea62bf364ad5167ef6a 15084 
gcontactsync_2.0.13-1.debian.tar.xz
 85b101db388d2ff205af8befd08f812d938463d36ab77897488cb136c2cd8a3d 6770 
gcontactsync_2.0.13-1_amd64.buildinfo
 9d54dd9c5d93a05ada0287f81b1f062992b9da632d57e2c2b2cc625d0c5421e0 195692 
xul-ext-gcontactsync_2.0.13-1_all.deb
Files:
 24b0f0c581fac117b16f561193da5892 2066 mail optional gcontactsync_2.0.13-1.dsc
 d3aac2a6c7ea554ebdba0a665b089391 177000 mail optional 
gcontactsync_2.0.13.orig.tar.xz
 

Bug#885603: gajim in stretch-backports depends on python3-nbxmpp, which is not in stretch-backports

[Patrik Marschalik]

Thank you so much!

Patrik

On Sun, Dec 31, 2017 at 12:44:54AM +0100, W. Martin Borgert wrote:
> Dear Patrik,
> 
> python-nbxmpp (which includes python3-nbxmpp) is now in backports.
> Gajim should be installablen now!
> 
> Have fun!


signature.asc
Description: PGP signature

Bug#884204: marked as done (webcit FTBFS with libical3)

[Debian Bug Tracking System]

Your message dated Wed, 03 Jan 2018 10:21:04 +
with message-id 
and subject line Bug#884204: fixed in webcit 916-dfsg-1
has caused the Debian Bug report #884204,
regarding webcit FTBFS with libical3
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.)


-- 
884204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884204
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: webcit
Version: 904-dfsg-1
Severity: serious

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

...
CC ical_dezonify.c
ical_dezonify.c: In function 'ical_dezonify_backend':
ical_dezonify.c:119:14: error: 'struct icaltimetype' has no member named 
'is_utc'; did you mean 'is_date'?
  if (TheTime.is_utc) {
  ^~
  is_date
ical_dezonify.c:129:11: error: 'struct icaltimetype' has no member named 
'is_utc'; did you mean 'is_date'?
   TheTime.is_utc = 1;
   ^~
   is_date
ical_dezonify.c:149:11: error: 'struct icaltimetype' has no member named 
'is_utc'; did you mean 'is_date'?
   TheTime.is_utc = 1;
   ^~
   is_date
Makefile:91: recipe for target 'ical_dezonify.o' failed
make[1]: *** [ical_dezonify.o] Error 1
--- End Message ---
--- Begin Message ---
Source: webcit
Source-Version: 916-dfsg-1

We believe that the bug you reported is fixed in the latest version of
webcit, 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 884...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Meskes  (supplier of updated webcit 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: Tue, 02 Jan 2018 10:54:47 +0100
Source: webcit
Binary: citadel-webcit citadel-suite
Architecture: source all amd64
Version: 916-dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Citadel Team 
Changed-By: Michael Meskes 
Description:
 citadel-suite - complete and feature-rich groupware server; metapackage for 
full
 citadel-webcit - web-based frontend to Citadel groupware server
Closes: 859789 884204
Changes:
 webcit (916-dfsg-1) unstable; urgency=medium
 .
   * New upstream version 916-dfsg (Closes: #859789)
   * Build depend on libical2-dev for now. (Closes: #884204)
   * Bumped Standards-Version to 4.1.3, no changes needed.
   * Bumped debhelper compat level to 11.
   * Changed priority to optional.
   * Remove obsolete -dbg package
Checksums-Sha1:
 da7db7b4a0d828a4bdf499fa316186b26fc8bf18 2224 webcit_916-dfsg-1.dsc
 2f11fa3d506b0a461048e5a6afcf3c6f36dccad2 1678556 webcit_916-dfsg.orig.tar.gz
 9c52a3a3b2fc65d0acc55280ada7fbfd1b0c4045 25079 webcit_916-dfsg-1.diff.gz
 a72e68c69a6d0284be264728c3d3bb7c51ebec34 8388 citadel-suite_916-dfsg-1_all.deb
 7b312a095596232cbc9940d3df8b73b0abe72daf 721708 
citadel-webcit-dbgsym_916-dfsg-1_amd64.deb
 e8f237637a8c8985443503f6cfe33723c2cfbf3e 753624 
citadel-webcit_916-dfsg-1_amd64.deb
 fa3192005aef87ba53c13865de0f61a32af5c6f0 6595 webcit_916-dfsg-1_amd64.buildinfo
Checksums-Sha256:
 b3ce49abf62e9fb6e3b44a47b54392e1393a2d24fcbb83b57d6329bd5f1be727 2224 
webcit_916-dfsg-1.dsc
 16a09bb9f6e1c931921b51b1a1dc97478682b8efe1f2661c4295ef434905ede7 1678556 
webcit_916-dfsg.orig.tar.gz
 ede82d2c6a7c1a61bc35034fc6e8d61972150f978db4e3db2d6159c352a99beb 25079 
webcit_916-dfsg-1.diff.gz
 7e609b3041d4c360488dead4acb9fed0de9f00cdb89485c09c6d652613ffed59 8388 
citadel-suite_916-dfsg-1_all.deb
 7bc78327173e34f3110dd1b7ca53e05b0f0d00b4e44d0c34eb907e1a7c871751 721708 
citadel-webcit-dbgsym_916-dfsg-1_amd64.deb
 9882bf68b5c5f4619ce89ee513ebfccfe10bf4569408bf7599c44918f0f66a3b 753624 
citadel-webcit_916-dfsg-1_amd64.deb
 366632fe2a27b99e5ae92b33e41dfe43df8acbbd186e6e8c7c46abc830a74266 6595 
webcit_916-dfsg-1_amd64.buildinfo
Files:
 9c137b1c7bfcae2cf61bbbf4365a7e1a 2224 web optional webcit_916-dfsg-1.dsc
 a1387f12421bfa1c7cdb0a4f34993b6c 1678556 web optional 
webcit_916-dfsg.orig.tar.gz
 4f9a2969c41c2117631805c0f7651492 25079 web optional webcit_916-dfsg-1.diff.gz
 c6f9210c384975f7011f99ae97d27dd0 8388 mail optional 
citadel-suite_916-dfsg-1_all.deb
 

Bug#859789: marked as done (webcit: Please migrate to openssl1.1 in Buster)

[Debian Bug Tracking System]

Your message dated Wed, 03 Jan 2018 10:21:04 +
with message-id 
and subject line Bug#859789: fixed in webcit 916-dfsg-1
has caused the Debian Bug report #859789,
regarding webcit: Please migrate to openssl1.1 in Buster
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.)


-- 
859789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859789
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: webcit
Version: 902-dfsg-1
Severity: important
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1-trans

Please migrate to libssl-dev in the Buster cycle. The bug report about
the FTBFS is #828598. The log of the FTBFS can be found at

https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/webcit_902-dfsg-1_amd64-20160529-1551

Sebastian
--- End Message ---
--- Begin Message ---
Source: webcit
Source-Version: 916-dfsg-1

We believe that the bug you reported is fixed in the latest version of
webcit, 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 859...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Meskes  (supplier of updated webcit 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: Tue, 02 Jan 2018 10:54:47 +0100
Source: webcit
Binary: citadel-webcit citadel-suite
Architecture: source all amd64
Version: 916-dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Citadel Team 
Changed-By: Michael Meskes 
Description:
 citadel-suite - complete and feature-rich groupware server; metapackage for 
full
 citadel-webcit - web-based frontend to Citadel groupware server
Closes: 859789 884204
Changes:
 webcit (916-dfsg-1) unstable; urgency=medium
 .
   * New upstream version 916-dfsg (Closes: #859789)
   * Build depend on libical2-dev for now. (Closes: #884204)
   * Bumped Standards-Version to 4.1.3, no changes needed.
   * Bumped debhelper compat level to 11.
   * Changed priority to optional.
   * Remove obsolete -dbg package
Checksums-Sha1:
 da7db7b4a0d828a4bdf499fa316186b26fc8bf18 2224 webcit_916-dfsg-1.dsc
 2f11fa3d506b0a461048e5a6afcf3c6f36dccad2 1678556 webcit_916-dfsg.orig.tar.gz
 9c52a3a3b2fc65d0acc55280ada7fbfd1b0c4045 25079 webcit_916-dfsg-1.diff.gz
 a72e68c69a6d0284be264728c3d3bb7c51ebec34 8388 citadel-suite_916-dfsg-1_all.deb
 7b312a095596232cbc9940d3df8b73b0abe72daf 721708 
citadel-webcit-dbgsym_916-dfsg-1_amd64.deb
 e8f237637a8c8985443503f6cfe33723c2cfbf3e 753624 
citadel-webcit_916-dfsg-1_amd64.deb
 fa3192005aef87ba53c13865de0f61a32af5c6f0 6595 webcit_916-dfsg-1_amd64.buildinfo
Checksums-Sha256:
 b3ce49abf62e9fb6e3b44a47b54392e1393a2d24fcbb83b57d6329bd5f1be727 2224 
webcit_916-dfsg-1.dsc
 16a09bb9f6e1c931921b51b1a1dc97478682b8efe1f2661c4295ef434905ede7 1678556 
webcit_916-dfsg.orig.tar.gz
 ede82d2c6a7c1a61bc35034fc6e8d61972150f978db4e3db2d6159c352a99beb 25079 
webcit_916-dfsg-1.diff.gz
 7e609b3041d4c360488dead4acb9fed0de9f00cdb89485c09c6d652613ffed59 8388 
citadel-suite_916-dfsg-1_all.deb
 7bc78327173e34f3110dd1b7ca53e05b0f0d00b4e44d0c34eb907e1a7c871751 721708 
citadel-webcit-dbgsym_916-dfsg-1_amd64.deb
 9882bf68b5c5f4619ce89ee513ebfccfe10bf4569408bf7599c44918f0f66a3b 753624 
citadel-webcit_916-dfsg-1_amd64.deb
 366632fe2a27b99e5ae92b33e41dfe43df8acbbd186e6e8c7c46abc830a74266 6595 
webcit_916-dfsg-1_amd64.buildinfo
Files:
 9c137b1c7bfcae2cf61bbbf4365a7e1a 2224 web optional webcit_916-dfsg-1.dsc
 a1387f12421bfa1c7cdb0a4f34993b6c 1678556 web optional 
webcit_916-dfsg.orig.tar.gz
 4f9a2969c41c2117631805c0f7651492 25079 web optional webcit_916-dfsg-1.diff.gz
 c6f9210c384975f7011f99ae97d27dd0 8388 mail optional 
citadel-suite_916-dfsg-1_all.deb
 54af842dd1c940c55a925a4a3fd22855 721708 debug optional 
citadel-webcit-dbgsym_916-dfsg-1_amd64.deb
 c26cb962c157856a6b20fb109396a19a 753624 web optional 
citadel-webcit_916-dfsg-1_amd64.deb
 1505fd6b8f1b15a30b486a0df9960e2c 6595 web optional 
webcit_916-dfsg-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJKBAEBCAA0FiEEZ/2RWVGI6sRsEOjtNdhXwLvLOyUFAlpMqucWHG1lc2tlc0Bw

Bug#884203: marked as done (citadel FTBFS with libical3)

[Debian Bug Tracking System]

Your message dated Wed, 03 Jan 2018 10:19:25 +
with message-id 
and subject line Bug#884203: fixed in citadel 916-1
has caused the Debian Bug report #884203,
regarding citadel FTBFS with libical3
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.)


-- 
884203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884203
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: citadel
Version: 911-1
Severity: serious

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

...
CC ical_dezonify.c
ical_dezonify.c: In function 'ical_dezonify_backend':
ical_dezonify.c:138:14: error: 'struct icaltimetype' has no member named 
'is_utc'; did you mean 'is_date'?
  if (TheTime.is_utc) {
  ^~
  is_date
ical_dezonify.c:144:11: error: 'struct icaltimetype' has no member named 
'is_utc'; did you mean 'is_date'?
   TheTime.is_utc = 1;
   ^~
   is_date
ical_dezonify.c:164:11: error: 'struct icaltimetype' has no member named 
'is_utc'; did you mean 'is_date'?
   TheTime.is_utc = 1;
   ^~
   is_date
Makefile:145: recipe for target 'ical_dezonify.o' failed
make[1]: *** [ical_dezonify.o] Error 1
--- End Message ---
--- Begin Message ---
Source: citadel
Source-Version: 916-1

We believe that the bug you reported is fixed in the latest version of
citadel, 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 884...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Meskes  (supplier of updated citadel 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: Wed, 03 Jan 2018 11:02:02 +0100
Source: citadel
Binary: citadel-server citadel-doc
Architecture: source all amd64
Version: 916-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Citadel Team 
Changed-By: Michael Meskes 
Description:
 citadel-doc - complete and feature-rich groupware server (documentation)
 citadel-server - complete and feature-rich groupware server
Closes: 851086 884203
Changes:
 citadel (916-1) unstable; urgency=medium
 .
   * Build depend on libical2-dev for now. (Closes: #884203)
   * New upstream version 916 (Closes: #851086)
   * Bumped Standards-Version to 4.1.3, no changes needed.
   * Changed priority to optional.
   * Switched to debhelper 11.
   * Set all hardening options.
   * Removed -dbg package.
Checksums-Sha1:
 afeb629b17c9f49af45556719ab8dae9e06c344d 2311 citadel_916-1.dsc
 35c3129c616b2fcaee3ef6e6ac3314bc7fd83c55 727058 citadel_916.orig.tar.gz
 9886609e98b3720ec80c5a837e03b8dcb69baa3c 50086 citadel_916-1.diff.gz
 cf746d749888baf8d4e492654057fb55045e5e39 43944 citadel-doc_916-1_all.deb
 3d51154e9db708613d2cc42a69c590f996dff166 2129564 
citadel-server-dbgsym_916-1_amd64.deb
 8189ee72a8d384f17b3589e16d18adc8c31d1c89 332424 citadel-server_916-1_amd64.deb
 1c97b8329a9a975346303bdf095d36b1454ca33f 7517 citadel_916-1_amd64.buildinfo
Checksums-Sha256:
 de3cd47d98b6ae99f0ddcac1734b7aa90bdf5894fa4f5a0a0fbe7badfc86dc3b 2311 
citadel_916-1.dsc
 e2f19631da8d9e1f0f191a2cc261a717fea4091766ca6d734cbfbe46833314fd 727058 
citadel_916.orig.tar.gz
 0abb869f41ae87d23ee775ae405ec5b68e815a9a2cb36712a136169b9f5a11f7 50086 
citadel_916-1.diff.gz
 89b80101b477ebbbe5f847a452529ead2ee3971d8bf4005108ce6a631c8159f1 43944 
citadel-doc_916-1_all.deb
 1c12fabcc4ae75ca1781b19ef224bad02b574f4a0ce67d484f7ca3ed75c77934 2129564 
citadel-server-dbgsym_916-1_amd64.deb
 90e33e3b7a806ed905a8283123bb62bb3fff5c19a36589670a6d65f4c9112827 332424 
citadel-server_916-1_amd64.deb
 3c036fe232d655a675a8eb974f247f53f4fc4199f6b0c97776b4c777fa4f6671 7517 
citadel_916-1_amd64.buildinfo
Files:
 613e3ae8136ade5e4488ddb7ecad9756 2311 mail optional citadel_916-1.dsc
 9c1ab8be62fa4986511adbd072486258 727058 mail optional citadel_916.orig.tar.gz
 ede67d3da726c9f872d5ff8cccd98b0c 50086 mail optional citadel_916-1.diff.gz
 3f167bd12c34f5a5363a4f1743841106 43944 doc optional citadel-doc_916-1_all.deb
 54caf20c5c92ed9a64d4391e0e922850 2129564 debug optional 
citadel-server-dbgsym_916-1_amd64.deb
 

Bug#851086: marked as done (citadel: Please migrate to openssl1.1 in buster)

[Debian Bug Tracking System]

Your message dated Wed, 03 Jan 2018 10:19:25 +
with message-id 
and subject line Bug#851086: fixed in citadel 916-1
has caused the Debian Bug report #851086,
regarding citadel: Please migrate to openssl1.1 in buster
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.)


-- 
851086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851086
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: citadel
Version: 902-1
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/citadel_902-1_amd64-20160529-1410

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: citadel
Source-Version: 916-1

We believe that the bug you reported is fixed in the latest version of
citadel, 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 851...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Meskes  (supplier of updated citadel 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: Wed, 03 Jan 2018 11:02:02 +0100
Source: citadel
Binary: citadel-server citadel-doc
Architecture: source all amd64
Version: 916-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Citadel Team 
Changed-By: Michael Meskes 
Description:
 citadel-doc - complete and feature-rich groupware server (documentation)
 citadel-server - complete and feature-rich groupware server
Closes: 851086 884203
Changes:
 citadel (916-1) unstable; urgency=medium
 .
   * Build depend on libical2-dev for now. (Closes: #884203)
   * New upstream version 916 (Closes: #851086)
   * Bumped Standards-Version to 4.1.3, no changes needed.
   * Changed priority to optional.
   * Switched to debhelper 11.
   * Set all hardening options.
   * Removed -dbg package.
Checksums-Sha1:
 afeb629b17c9f49af45556719ab8dae9e06c344d 2311 citadel_916-1.dsc
 35c3129c616b2fcaee3ef6e6ac3314bc7fd83c55 727058 citadel_916.orig.tar.gz
 9886609e98b3720ec80c5a837e03b8dcb69baa3c 50086 citadel_916-1.diff.gz
 cf746d749888baf8d4e492654057fb55045e5e39 43944 citadel-doc_916-1_all.deb
 3d51154e9db708613d2cc42a69c590f996dff166 2129564 
citadel-server-dbgsym_916-1_amd64.deb
 8189ee72a8d384f17b3589e16d18adc8c31d1c89 332424 citadel-server_916-1_amd64.deb
 1c97b8329a9a975346303bdf095d36b1454ca33f 7517 citadel_916-1_amd64.buildinfo
Checksums-Sha256:
 de3cd47d98b6ae99f0ddcac1734b7aa90bdf5894fa4f5a0a0fbe7badfc86dc3b 2311 
citadel_916-1.dsc
 e2f19631da8d9e1f0f191a2cc261a717fea4091766ca6d734cbfbe46833314fd 727058 
citadel_916.orig.tar.gz
 0abb869f41ae87d23ee775ae405ec5b68e815a9a2cb36712a136169b9f5a11f7 50086 
citadel_916-1.diff.gz
 89b80101b477ebbbe5f847a452529ead2ee3971d8bf4005108ce6a631c8159f1 43944 
citadel-doc_916-1_all.deb
 1c12fabcc4ae75ca1781b19ef224bad02b574f4a0ce67d484f7ca3ed75c77934 2129564 
citadel-server-dbgsym_916-1_amd64.deb
 90e33e3b7a806ed905a8283123bb62bb3fff5c19a36589670a6d65f4c9112827 332424 
citadel-server_916-1_amd64.deb
 3c036fe232d655a675a8eb974f247f53f4fc4199f6b0c97776b4c777fa4f6671 7517 
citadel_916-1_amd64.buildinfo
Files:
 613e3ae8136ade5e4488ddb7ecad9756 2311 mail optional citadel_916-1.dsc
 9c1ab8be62fa4986511adbd072486258 727058 mail optional citadel_916.orig.tar.gz
 ede67d3da726c9f872d5ff8cccd98b0c 50086 mail optional citadel_916-1.diff.gz
 3f167bd12c34f5a5363a4f1743841106 43944 doc optional citadel-doc_916-1_all.deb
 54caf20c5c92ed9a64d4391e0e922850 2129564 debug optional 
citadel-server-dbgsym_916-1_amd64.deb
 

Bug#886224: printer-driver-cups-pdf: Virtual pdf printer error: no output and config problem

[Rudolf Polzer]

Package: printer-driver-cups-pdf
Version: 3.0.1-4
Severity: grave
Justification: renders package unusable



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

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

Versions of packages printer-driver-cups-pdf depends on:
ii  cups2.2.6-4
ii  cups-client 2.2.6-4
ii  ghostscript 9.22~dfsg-1
ii  libc6   2.25-6
ii  libcups22.2.6-4
ii  libpaper-utils  1.1.24+nmu5

printer-driver-cups-pdf recommends no packages.

Versions of packages printer-driver-cups-pdf suggests:
pn  system-config-printer  

-- no debconf information


Bug description:

The cups pdf printer produces no pdf output file.

After deleting the pdf printer, the add printer function does not work as 
expected:
After selecting "Generic" as printer make, no pdf printer model is selectable.
I instead selected one of the existing ppd files in /usr/share/ppd/cups-pdf
but this did not make the pdf printer work.

The bug started by my recent update from cups-pdf, where pdf printing did work,
to printer-driver-cups-pdf.

Bug#886200: FTBFS: XPA$ERROR: invalid host name specified: $host:$port.

[Ole Streicher]

Control: tag -1 moreinfo

Hi Adam,

I couldn't reproduce this on amd64; my test build runs fine (see
attached log).

Did you change anything in the setup of the machine between the
successfull and the failing build? Specifically in the networking? Since
xpa is a network protocol, it needs at least a working "localhost".

Cheers

Ole
dpkg-checkbuilddeps: error: Unmet build dependencies: tcl-dev
W: Unmet build-dependency in source
dpkg-source: info: applying Fix-the-paths-for-a-chroot-build-and-for-FHS.patch
dpkg-source: info: applying 
Fix-manpages-section-name-and-spellfixes-so-that-lintian-.patch
dpkg-source: info: applying Add-a-description-to-AC_DEFINEs.patch
dpkg-source: info: applying 
Install-the-tcl-interface-to-usr-lib-tcltk-xpa-according-.patch
dpkg-source: info: applying Add-hardening-flags.patch
dpkg-source: info: applying Sort-.o-files.patch
dpkg-source: info: applying Recognise-the-exit-status-of-mklibs.patch
dpkg-source: info: applying make-mklib-work-with-cross-compilation.patch
dh clean --with autoreconf
   dh_clean
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building xpa using existing ./xpa_2.1.18.orig.tar.gz
dpkg-source: info: building xpa in xpa_2.1.18-3.debian.tar.xz
dpkg-source: info: building xpa in xpa_2.1.18-3.dsc
I: Generating source changes file for original dsc
dpkg-genchanges: info: not including original source code in upload
dpkg-source: info: unapplying make-mklib-work-with-cross-compilation.patch
dpkg-source: info: unapplying Recognise-the-exit-status-of-mklibs.patch
dpkg-source: info: unapplying Sort-.o-files.patch
dpkg-source: info: unapplying Add-hardening-flags.patch
dpkg-source: info: unapplying 
Install-the-tcl-interface-to-usr-lib-tcltk-xpa-according-.patch
dpkg-source: info: unapplying Add-a-description-to-AC_DEFINEs.patch
dpkg-source: info: unapplying 
Fix-manpages-section-name-and-spellfixes-so-that-lintian-.patch
dpkg-source: info: unapplying Fix-the-paths-for-a-chroot-build-and-for-FHS.patch
I: Copying COW directory
I: forking: rm -rf /var/cache/pbuilder/build/cow.26943
I: forking: cp -al /var/cache/pbuilder/base.cow 
/var/cache/pbuilder/build/cow.26943
I: removed stale ilistfile /var/cache/pbuilder/build/cow.26943/.ilist
I: forking: chroot /var/cache/pbuilder/build/cow.26943 
cowdancer-ilistcreate /.ilist 'find . -xdev -path ./home -prune -o \( \( -type 
l -o -type f \) -a -links +1 -print0 \) | xargs -0 stat --format '%d %i ''
I: Invoking pbuilder
I: forking: pbuilder build --debbuildopts  --debbuildopts  --buildplace 
/var/cache/pbuilder/build/cow.26943 --buildresult /var/cache/pbuilder/result 
--extrapackages 'eatmydata ccache' --no-targz --internal-chrootexec 'chroot 
/var/cache/pbuilder/build/cow.26943 cow-shell' 
/home/ole/Projects/2011/debian/ds9/xpa_2.1.18-3.dsc
I: Running in no-targz mode
I: pbuilder: network access will be disabled during build
I: Current time: Wed Jan  3 09:28:17 CET 2018
I: pbuilder-time-stamp: 1514968097
I: copying local configuration
W: hookdir /etc/pbuilder/hooks does not exist, skipping
I: mounting /proc filesystem
I: mounting /sys filesystem
I: creating /{dev,run}/shm
I: mounting /dev/pts filesystem
I: redirecting /dev/ptmx to /dev/pts/ptmx
I: Mounting /var/cache/pbuilder/ccache
I: Mounting /var/cache/pbuilder/result
I: policy-rc.d already exists
I: Obtaining the cached apt archive contents
I: Copying source file
I: copying [/home/ole/Projects/2011/debian/ds9/xpa_2.1.18-3.dsc]
I: copying [/home/ole/Projects/2011/debian/ds9/xpa_2.1.18.orig.tar.gz]
I: copying 
[/home/ole/Projects/2011/debian/ds9/xpa_2.1.18-3.debian.tar.xz]
I: Extracting source
dpkg-source: warning: extracting unsigned source package (xpa_2.1.18-3.dsc)
dpkg-source: info: extracting xpa in xpa-2.1.18
dpkg-source: info: unpacking xpa_2.1.18.orig.tar.gz
dpkg-source: info: unpacking xpa_2.1.18-3.debian.tar.xz
dpkg-source: info: applying Fix-the-paths-for-a-chroot-build-and-for-FHS.patch
dpkg-source: info: applying 
Fix-manpages-section-name-and-spellfixes-so-that-lintian-.patch
dpkg-source: info: applying Add-a-description-to-AC_DEFINEs.patch
dpkg-source: info: applying 
Install-the-tcl-interface-to-usr-lib-tcltk-xpa-according-.patch
dpkg-source: info: applying Add-hardening-flags.patch
dpkg-source: info: applying Sort-.o-files.patch
dpkg-source: info: applying Recognise-the-exit-status-of-mklibs.patch
dpkg-source: info: applying make-mklib-work-with-cross-compilation.patch
I: using fakeroot in build.
I: Installing the build-deps
Reading package lists...
Building dependency tree...
Reading state information...
Suggested packages:
  autoconf-archive gnu-standards autoconf-doc wamerican | wordlist whois
  vacation dh-make dwz gettext-doc libasprintf-dev libgettextpo-dev groff
  libice-doc 

Processed: FTBFS: XPA$ERROR: invalid host name specified: $host:$port.

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #886200 [src:xpa] FTBFS: XPA$ERROR: invalid host name specified: 
$host:$port.
Added tag(s) moreinfo.

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

Bug#886218: ostree: FTBFS on big-endian CPUs: test failure in tests/test-basic-user-only.sh

[Simon McVittie]

Source: ostree
Version: 2017.15-1
Severity: serious
Tags: patch pending upstream
Justification: fails to build from source (but built successfully in the past)
Forwarded: https://github.com/ostreedev/ostree/issues/1392

ostree fails to build from source on mips, s390x, hppa, powerpc, ppc64
and sparc64. I believe those are exactly the architectures that are
big-endian and do not disable build-time tests.

(powerpcspe and m68k are also BE, but they don't run build-time tests,
which IMO is a bad idea; those ports ship an ostree package but don't
check whether it works.)

Patch at https://github.com/ostreedev/ostree/pull/1393.

smcv

Bug#886117: FTBFS: most of testsuite

[Alexander Zangerl]

On Tue, 02 Jan 2018 14:40:33 +0100, Adam Borowski writes:
>I'm afraid that your package fails to build on current unstable, failing the
>vast majority of tests:

looks like every one of the failed tests fails for the same reason,
(which to me indicates rather a failure of the test suite
than a failure of duplicity itself):

  File "/<>/testing/__init__.py", line 88, in unpack_testfiles
assert not os.system("tar xzf testfiles.tar.gz > /dev/null 2>&1")
AssertionError

i'll go dig deeper when i find the time, but i've got no clue how
why that could be a platform-specific failure.

regards
az



-- 
Alexander Zangerl + GPG Key 2FCCF66BB963BD5F + http://snafu.priv.at/
"Unterschätze nie die Macht dummer Leute, die einer Meinung sind."
 -- Kurt Tucholsky
% 
Which is worse: Ignorance or apathy? I don't know and I don't care.


signature.asc
Description: Digital Signature