Bug#916508: netplan: Should not be included in buster

[Petter Reinholdtsen]

Package: netplan
Severity: critical
Version: 1.10.1-5

I plan to orphan this package and do not want to take responsibility for
the network security support of netplan for the next stable release.
Because of this, I register a RC bug on the package to ensure it stay
out of buster until someone take over the package.

-- 
Happy hacking
Petter Reinholdtsen

Bug#916121: marked as done (array-info FTBFS with glibc 2.28)

[Debian Bug Tracking System]

Your message dated Sat, 15 Dec 2018 07:49:22 +
with message-id 
and subject line Bug#916121: fixed in array-info 0.16-4
has caused the Debian Bug report #916121,
regarding array-info FTBFS with glibc 2.28
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.)


-- 
916121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916121
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: array-info
Version: 0.16-3
Severity: serious
Tags: ftbfs

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

...
array_utils.c: In function 'open_ctrl':
array_utils.c:63:35: warning: implicit declaration of function 'major' 
[-Wimplicit-function-declaration]
  array_data->device_major.major = major(stat_buf.st_rdev);
   ^
array_utils.c:64:35: warning: implicit declaration of function 'minor'; did you 
mean 'mknod'? [-Wimplicit-function-declaration]
  array_data->device_major.minor = minor(stat_buf.st_rdev);
   ^
...
/usr/bin/ld: array_utils.o: in function `open_ctrl':
/build/1st/array-info-0.16/array_utils.c:63: undefined reference to `major'
/usr/bin/ld: /build/1st/array-info-0.16/array_utils.c:64: undefined reference 
to `minor'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:41: array-info] Error 1
--- End Message ---
--- Begin Message ---
Source: array-info
Source-Version: 0.16-4

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

Debian distribution maintenance software
pp.
Petter Reinholdtsen  (supplier of updated array-info 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: Sat, 15 Dec 2018 08:34:33 +0100
Source: array-info
Binary: array-info
Architecture: source
Version: 0.16-4
Distribution: unstable
Urgency: medium
Maintainer: Petter Reinholdtsen 
Changed-By: Petter Reinholdtsen 
Description:
 array-info - command line tool reporting RAID status for several RAID types
Closes: 900893 916121
Changes:
 array-info (0.16-4) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/changelog: Remove trailing whitespaces
   * d/control: Remove trailing whitespaces
   * d/control: Set Vcs-* to salsa.debian.org
 .
   [ Petter Reinholdtsen ]
   * Added 1000-major-minor-macros.patch to fix build problem with recent
 glibc (Closes: #916121).
   * Adjusted packaging to move AppStream metadata from
 /usr/share/appdata to /usr/share/metainfo.
   * Changed Standards-Version from 3.9.8 to 4.2.1.
   * Fixed FTCBFS: Let dh_auto_build pass cross tools to make
 (Closes: #900893).  Patch from Helmut Grohne.
   * Added d/gbp.conf to enforce the use of pristine-tar.
Checksums-Sha1:
 5399c59e78feb9e2a2b77811fc48290358dcfa28 1873 array-info_0.16-4.dsc
 7127b8b7d16bd6af703c6453fcc835707a5f4037 3312 array-info_0.16-4.debian.tar.xz
 ac02da4811c6e6c86a43ed4017c4fafe3c847993 7805 
array-info_0.16-4_source.buildinfo
Checksums-Sha256:
 d612a712cb661bab74c2403319aacda66be706b8c076ec503937127ecf352b8a 1873 
array-info_0.16-4.dsc
 b31d88f78dd1c5ee64b7186e6aae98df98bcb1e0d219ef28bd3ce8728269b8ef 3312 
array-info_0.16-4.debian.tar.xz
 ab269508c5f5b90ba8143b71a219b5da33a7e4389071ce67203790da8e576884 7805 
array-info_0.16-4_source.buildinfo
Files:
 438343858f10359f4812d24499bff668 1873 admin optional array-info_0.16-4.dsc
 c44e8904c33c64ca4d473add4f191dba 3312 admin optional 
array-info_0.16-4.debian.tar.xz
 389776824acfc164f3d3ec20dd6d01e4 7805 admin optional 
array-info_0.16-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAlwUrrQACgkQgSgKoIe6
+w65Aw//W15ryY5W7AVMJ6pFnj/gwvgKeDPqXC4v/amiwtVRBD/YJ67D7IRH+4Rj
3bZjwdCWgMF4ZaeGPURL5435X5M9L293ac1HR1y1dW2xnQTyuOXsVYKWAWOwpFAO
RUbBHOBfB6pePD6oDzld9OutrYnK9jM7h1idufKkeiNY0oSRURQVLn/3f8mTP9/n
FkGRDS4bipyLpGqfgZRWn8pGi3llc/V/oblbSdKNNe8+3uKKGVgi5FTNKaDd6n/U
c/jjiWyZP9xKjfjXlKKKSC2J9aLpMQRzG0Vse7mmgZ9uiUKWKgqExPP/jbhRL3c8
Owfa4/cHAjT1FWpBPRbBx8a0hW6o4xngn5JxTapkX0ZZp+3ESPch57jyaBC73qNn
tMwYt0sxScSAeG6YmO3W06CsoipxD1ww9m3nqXCdxDHUDJBTrDdAiZ0bYCFpzaU/

Bug#916121: array-info FTBFS with glibc 2.28

[Petter Reinholdtsen]

Control: tags -1 + patch

Thank you for the heads up.  I had a look at the code, and this patch
get the code building.

diff --git a/include/array_info.h b/include/array_info.h
index 70d6458..2566ee7 100644
--- a/include/array_info.h
+++ b/include/array_info.h
@@ -44,6 +44,7 @@
 #define _ARRAY_INFO_H_
 
 #include 
+#include 
 #include 
 #include 
 #include 

I currently lack the hardware required to verify the new code work, but
am quite sure I found the correct header to include.

-- 
Happy hacking
Petter Reinholdtsen

Processed: Re: array-info FTBFS with glibc 2.28

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #916121 [src:array-info] array-info FTBFS with glibc 2.28
Added tag(s) patch.

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

Bug#915759: gitaly: depends on gitlab-common which is in contrib

[Pirate Praveen]

On Thu, 06 Dec 2018 17:17:46 +0100 Andreas Beckmann  wrote:
> 
> during a test with piuparts I noticed your package failed to install.
> gitaly is in main, but depends on gitlab-common which is in contrib.
> One of the two packages needs to move ...

gitlab-common is moved to main in 11.5.3+dfsg-1 (its in NEW)



signature.asc
Description: OpenPGP digital signature

Bug#912823: marked as done (/usr/bin/byobu: 250: exec: tmux: not found)

[Debian Bug Tracking System]

Your message dated Sat, 15 Dec 2018 04:49:22 +
with message-id 
and subject line Bug#912823: fixed in hollywood 1.14-1.1
has caused the Debian Bug report #912823,
regarding /usr/bin/byobu: 250: exec: tmux: not found
to be marked as done.

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

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


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

Dear Maintainer,

Thanks for a fun one :)

But...

> hollywood
/usr/bin/byobu: 250: exec: tmux: not found
/usr/bin/byobu: 250: exec: tmux: not found
/usr/bin/byobu: 250: exec: tmux: not found
/usr/bin/byobu: 250: exec: tmux: not found
zsh: exit 127   hollywood


tmux is recommended by byobu, but it seems, is a must-have for
hollywood (and wallstreet).

-- 
Jason


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

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

Versions of packages hollywood depends on:
ii  byobu  5.112-1.1

Versions of packages hollywood recommends:
pn  apg 
pn  bmon
ii  bsdmainutils11.1.2+b1
pn  ccze
pn  cmatrix 
pn  htop
pn  jp2a
pn  mlocate 
pn  moreutils   
ii  openssh-client  1:7.9p1-1
pn  speedometer 
ii  tree1.7.0-5

Versions of packages hollywood suggests:
pn  mplayer  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: hollywood
Source-Version: 1.14-1.1

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated hollywood 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: Fri, 07 Dec 2018 23:02:30 -0500
Source: hollywood
Binary: hollywood wallstreet
Architecture: source
Version: 1.14-1.1
Distribution: unstable
Urgency: medium
Maintainer: Yangfl 
Changed-By: Boyuan Yang 
Description:
 hollywood  - fill your console with Hollywood melodrama technobabble
 wallstreet - fill your console with Wall Street-like news and stats
Closes: 912823
Changes:
 hollywood (1.14-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/control: Add missing package dependency tmux.
 (Closes: #912823)
Checksums-Sha1:
 3f838a1f879fd4053f373509e13cf82a8232ceea 2014 hollywood_1.14-1.1.dsc
 8916a7ca564b350228898214ec0c617c724f673d 13116 hollywood_1.14-1.1.debian.tar.xz
 1c26ed58603ba2f592a57ccd1641f4081d104658 5506 
hollywood_1.14-1.1_amd64.buildinfo
Checksums-Sha256:
 808dec1ecb209c0fd02047456c2dee52126f182966578a244d8dbdcc602b7069 2014 
hollywood_1.14-1.1.dsc
 f8f9df152669f553c4293e786d91c62236b5b42f7af212d728cda5faabbee321 13116 
hollywood_1.14-1.1.debian.tar.xz
 0625cd9facff329da06da7d6559da0ae218bb392cb6768515cafca0dd03e6b74 5506 
hollywood_1.14-1.1_amd64.buildinfo
Files:
 1ca46b54b539f5243c7d7a2519a6322b 2014 games optional hollywood_1.14-1.1.dsc
 1d0c8c966db7bb5c26a84d5a12a92a25 13116 games optional 
hollywood_1.14-1.1.debian.tar.xz
 c59c64e5140b148be1cf1e38397c0906 5506 games optional 
hollywood_1.14-1.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAlwLQxIACgkQwpPntGGC
Ws7RlRAAmwW+po5Qj3rT761uwPtqBCAuIY8TG8QrQcDJrnYaZsUqBXzYl+clTInH
uxEvmMyFIijM4zMqjB2z+xzxJAbR6wdGrnw/V8pAH7N8WlSoepbwKUkcydWCDiwm
UNmftSjgIBtg5cNWlGcHI1XiWyqwrJrlonHOFLAQmlZGo91KOHvs6f8GRiHGpVNM
w41Fk4w4zlbadh27SPWfv75oAOHD/gmiQ1gypdtt8PMtfbPH0bw3GfS1Y3MKpQLQ
LSbl4QPmJOh6cJsoWWsmMD0EQxX1RC+unKCQOvZTirPpcKY25r0+IjL7MYTS/UgQ
xccEKiOGrr/ZIJslCfKcPUy4Vg451/Mrgd5KNocIrdyV7+w0q5jt/kdbrKzlBdhq
wXlk8mfkG8x1XTnUuImG94FhEk2JL3TReoBWs68gkzVPKQV8uJKo14pAJ5QGj/oY
BGZgBdb386lYvNDun9jdf2XCtTvhY+WjgsjfmIKoNhmLmOP+FQiReJHvXB0Dvr2M

Bug#899869: marked as done (xfce4-linelight-plugin: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sat, 15 Dec 2018 04:45:33 +
with message-id 
and subject line Bug#916473: Removed package(s) from unstable
has caused the Debian Bug report #899869,
regarding xfce4-linelight-plugin: Invalid maintainer address 
pkg-xfce-de...@lists.alioth.debian.org
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.)


-- 
899869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899869
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xfce4-linelight-plugin
Version: 0.1.7-4
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of xfce4-linelight-plugin,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package xfce4-linelight-plugin since the list address
pkg-xfce-de...@lists.alioth.debian.org used in the Maintainer: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-xfce-de...@lists.alioth.debian.org is 55.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 0.1.7-4+rm

Dear submitter,

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

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

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

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

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

Bug#896168: marked as done (openacs depends on the removed aolserver4-xotcl)

[Debian Bug Tracking System]

Your message dated Sat, 15 Dec 2018 04:45:59 +
with message-id 
and subject line Bug#916241: Removed package(s) from unstable
has caused the Debian Bug report #896168,
regarding openacs depends on the removed aolserver4-xotcl
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.)


-- 
896168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896168
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openacs
Version: 5.9.0+dfsg-1
Severity: serious
Tags: buster sid

openacs depends on the removed aolserver4-xotcl.

Note that the other aolserver4 packages are
also scheduled for removal (#891633).
--- End Message ---
--- Begin Message ---
Version: 5.9.0+dfsg-1+rm

Dear submitter,

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

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

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

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

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

Bug#903577: marked as done (lua-torch-cutorch: FTBFS: does not find Torch)

[Debian Bug Tracking System]

Your message dated Sat, 15 Dec 2018 04:40:29 +
with message-id 
and subject line Bug#916281: Removed package(s) from unstable
has caused the Debian Bug report #903577,
regarding lua-torch-cutorch: FTBFS: does not find Torch
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.)


-- 
903577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903577
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lua-torch-cutorch
Version: 0~20170911-g5e9d86c-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

lua-torch-cutorch recently started to FTBFS in an up-to-date sid
environment.

dh_auto_configure --buildsystem=cmake --builddirectory=THC.build -- \
../lib/THC -DLUA=/usr/bin/lua5.1 -DLUA_INCDIR=/usr/include/lua5.1 
-DLUA_LIBDIR=/usr/lib -DLUA_BINDIR=/usr/bin -DLIBDIR=/usr/lib -DLUALIB=lua5.1 
-DTorch_INSTALL_BIN_SUBDIR=bin/ -DTorch_INSTALL_LIB_SUBDIR=li
b/x86_64-linux-gnu/ -DTorch_INSTALL_INCLUDE_SUBDIR=include/ 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=Release 
-DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_C_FLAGS="-I/usr/include/TH -g" 
-DCMAKE_CXX_FLAGS="-I/usr/inclu
de/TH -g" -DTorch_FOUND=ON \
-DTorch_INSTALL_CMAKE_SUBDIR=/usr/share/libtorch-thc-dev/
cd THC.build && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=O
N -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_C_COMPILER=gcc-6 -DCMAKE_CXX_COMPILER=g\+\+-6 
../lib/THC -DLUA=/usr/bin/lua5.1 -DLUA_INCDIR=/usr/include/lu
a5.1 -DLUA_LIBDIR=/usr/lib -DLUA_BINDIR=/usr/bin -DLIBDIR=/usr/lib 
-DLUALIB=lua5.1 -DTorch_INSTALL_BIN_SUBDIR=bin/ 
-DTorch_INSTALL_LIB_SUBDIR=lib/x86_64-linux-gnu/ 
-DTorch_INSTALL_INCLUDE_SUBDIR=include/ -DCMAKE_V
ERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/usr 
"-DCMAKE_C_FLAGS=-I/usr/include/TH -g" "-DCMAKE_CXX_FLAGS=-I/usr/include/TH -g" 
-DTorch_FOUND=ON -DTorch_INSTALL_CMAKE_SUBDIR=/usr/share/libtorch-thc-dev/ ..
-- The C compiler identification is GNU 6.4.0
-- The CXX compiler identification is GNU 6.4.0
-- Check for working C compiler: /usr/bin/gcc-6
-- Check for working C compiler: /usr/bin/gcc-6 -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/g++-6
-- Check for working CXX compiler: /usr/bin/g++-6 -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Error at CMakeLists.txt:6 (FIND_PACKAGE):
  By not providing "FindTorch.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "Torch", but
  CMake did not find one.

  Could not find a package configuration file provided by "Torch" with any of
  the following names:

TorchConfig.cmake
torch-config.cmake

  Add the installation prefix of "Torch" to CMAKE_PREFIX_PATH or set
  "Torch_DIR" to a directory containing one of the above files.  If "Torch"
  provides a separate development package or SDK, be sure it has been
  installed.


-- Configuring incomplete, errors occurred!


Andreas


lua-torch-cutorch_0~20170911-g5e9d86c-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 0~20170911-g5e9d86c-2+rm

Dear submitter,

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

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

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

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

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

Bug#899832: marked as done (xfswitch-plugin: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sat, 15 Dec 2018 04:41:42 +
with message-id 
and subject line Bug#916395: Removed package(s) from unstable
has caused the Debian Bug report #899832,
regarding xfswitch-plugin: Invalid maintainer address 
pkg-xfce-de...@lists.alioth.debian.org
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.)


-- 
899832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899832
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xfswitch-plugin
Version: 0.0.1-5
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of xfswitch-plugin,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package xfswitch-plugin since the list address
pkg-xfce-de...@lists.alioth.debian.org used in the Maintainer: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-xfce-de...@lists.alioth.debian.org is 55.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 0.0.1-5+rm

Dear submitter,

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

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

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

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

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

Bug#900773: marked as done (lua-torch-cutorch: build-depends on GCC 6)

[Debian Bug Tracking System]

Your message dated Sat, 15 Dec 2018 04:40:29 +
with message-id 
and subject line Bug#916281: Removed package(s) from unstable
has caused the Debian Bug report #900773,
regarding lua-torch-cutorch: build-depends on GCC 6
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.)


-- 
900773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900773
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lua-torch-cutorch
Version: 0~20170911-g5e9d86c-2
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcc-6-rm

Hi,

lua-torch-cutorch build-depends on GCC 6. We now have GCC 7 (default)
and GCC 8 in the archive, so please make your package build with a newer
compiler (preferably the default one) again, since we'd like to
remove GCC 6 from testing before the buster release.

Cheers,
Emilio
--- End Message ---
--- Begin Message ---
Version: 0~20170911-g5e9d86c-2+rm

Dear submitter,

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

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

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

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

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

Bug#899876: marked as done (xfwm4-themes: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sat, 15 Dec 2018 04:41:16 +
with message-id 
and subject line Bug#916394: Removed package(s) from unstable
has caused the Debian Bug report #899876,
regarding xfwm4-themes: Invalid maintainer address 
pkg-xfce-de...@lists.alioth.debian.org
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.)


-- 
899876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899876
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xfwm4-themes
Version: 4.10.0-2
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of xfwm4-themes,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package xfwm4-themes since the list address
pkg-xfce-de...@lists.alioth.debian.org used in the Maintainer: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-xfce-de...@lists.alioth.debian.org is 55.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 4.10.0-2+rm

Dear submitter,

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

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

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

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

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

Bug#896167: marked as done (dotlrn depends on the removed aolserver4-xotcl)

[Debian Bug Tracking System]

Your message dated Sat, 15 Dec 2018 04:39:07 +
with message-id 
and subject line Bug#916242: Removed package(s) from unstable
has caused the Debian Bug report #896167,
regarding dotlrn depends on the removed aolserver4-xotcl
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.)


-- 
896167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dotlrn
Version: 2.5.0+dfsg2-1
Severity: serious
Tags: buster sid

dotlrn depends on the removed aolserver4-xotcl.

Note that the other aolserver4 packages are
also scheduled for removal (#891633).
--- End Message ---
--- Begin Message ---
Version: 2.5.0+dfsg2-1+rm

Dear submitter,

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

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

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

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

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

Bug#876827: marked as done (fuji FTBFS with golang-github-eclipse-paho.mqtt.golang-dev 1.1.0-1)

[Debian Bug Tracking System]

Your message dated Sat, 15 Dec 2018 04:38:32 +
with message-id 
and subject line Bug#915059: Removed package(s) from unstable
has caused the Debian Bug report #876827,
regarding fuji FTBFS with golang-github-eclipse-paho.mqtt.golang-dev 1.1.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.)


-- 
876827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876827
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fuji
Version: 1.0.2-1
Severity: serious
Tags: buster sid

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

...
   dh_auto_build -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/build/1st/fuji-1.0.2/obj-x86_64-linux-gnu/src\" 
-asmflags=\"-trimpath=/build/1st/fuji-1.0.2/obj-x86_64-linux-gnu/src\" -v -p 1 
github.com/shiguredo/fuji github.com/shiguredo/fuji/broker 
github.com/shiguredo/fuji/cmd/fuji github.com/shiguredo/fuji/config 
github.com/shiguredo/fuji/device github.com/shiguredo/fuji/gateway 
github.com/shiguredo/fuji/message github.com/shiguredo/fuji/utils
src/github.com/shiguredo/fuji/broker/broker.go:28:2: cannot find package 
"git.eclipse.org/gitroot/paho/org.eclipse.paho.mqtt.golang.git" in any of:

/usr/lib/go-1.9/src/git.eclipse.org/gitroot/paho/org.eclipse.paho.mqtt.golang.git
 (from $GOROOT)

/build/1st/fuji-1.0.2/obj-x86_64-linux-gnu/src/git.eclipse.org/gitroot/paho/org.eclipse.paho.mqtt.golang.git
 (from $GOPATH)
dh_auto_build: cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/build/1st/fuji-1.0.2/obj-x86_64-linux-gnu/src\" 
-asmflags=\"-trimpath=/build/1st/fuji-1.0.2/obj-x86_64-linux-gnu/src\" -v -p 1 
github.com/shiguredo/fuji github.com/shiguredo/fuji/broker 
github.com/shiguredo/fuji/cmd/fuji github.com/shiguredo/fuji/config 
github.com/shiguredo/fuji/device github.com/shiguredo/fuji/gateway 
github.com/shiguredo/fuji/message github.com/shiguredo/fuji/utils returned exit 
code 1
debian/rules:7: recipe for target 'build' failed
make: *** [build] Error 1
--- End Message ---
--- Begin Message ---
Version: 1.0.2-1+rm

Dear submitter,

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

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

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

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

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

Processed: user debian...@lists.debian.org, affects 915580, usertagging 916279

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> affects 915580 + ucto
Bug #915580 [uctodata] uctodata: missing Breaks+Replaces: libucto2 (<< 0.9.6-2)
Added indication that 915580 affects ucto
> usertags 916279 piuparts
There were no usertags set.
Usertags are now: piuparts.
> thanks
Stopping processing here.

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

Bug#914297: apache2: getrandom call blocks on first startup, systemd kills with timeout

[Alexander E. Patrakov]

Stefan Fritsch :
> The rng should be initialized after the seed is loaded from disk.

This is false according to systemd developers. Its state is changed,
but it is still not initialized, because they think that the seed
might come from a gold master image.

-- 
Alexander E. Patrakov

Bug#915886: Additional Debug Data

[Ben McCann]

I'm also hitting this bug so I've collected the data requested by Rich:

b@mx17:~$ dpkg -l | egrep '^ii  perl-'
ii  perl-base 5.24.1-3+deb9u5
 amd64minimal Perl system
ii  perl-modules-5.24 5.24.1-3+deb9u5
 all  Core Perl modules
ii  perl-openssl-defaults:amd64   3
 amd64version compatibility baseline for Perl OpenSSL packages
b@mx17:~$ ls -l /usr/share/perl/5.24*/Getopt/Std.pm
-rw-r--r-- 1 root root 8790 Nov 29 06:11
/usr/share/perl/5.24.1/Getopt/Std.pm
-rw-r--r-- 1 root root 8790 Nov 29 06:11 /usr/share/perl/5.24/Getopt/Std.pm

As you can see, my box has GetOpt and yet it has the same dkms error:

checking global_page_state enums are sane... no
NR_FILE_PAGES in either node_stat_item or zone_stat_item: NOT FOUND
configure needs updating, see: config/kernel-global_page_state.m4
configure: error: in `/var/lib/dkms/zfs/0.7.12/build':
configure: error: SHUT 'ER DOWN CLANCY, SHE'S PUMPIN' MUD!
See `config.log' for more details

-Ben McCann

Bug#885677: liblablgtksourceview2-ocaml: Depends on unmaintained gtksourceview2

[Jeremy Bicha]

Control: reopen -1

You can't drop liblablgtksourceview2-ocaml-dev as long as stuff still
depends and build-depends on it.

coq
lablgtk-extra
laby
marionnet

gtksourceview2 will be included in Debian 10 "Buster" but we will try
to remove it early in the Bullseye series. [1]

Therefore, I suggest bringing that package back, then you can lower
the severity of this bug to Important. We'll have to figure something
out for Bullseye.

[1] https://lists.debian.org/debian-devel/2018/11/msg00570.html

Thanks,
Jeremy Bicha

Processed: Re: liblablgtksourceview2-ocaml: Depends on unmaintained gtksourceview2

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #885677 {Done: Stéphane Glondu } [src:lablgtk2] 
liblablgtksourceview2-ocaml: Depends on unmaintained gtksourceview2
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions lablgtk2/2.18.5+dfsg-2.

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

Bug#916236: golang-golang-x-net-dev: FTBFS on s390x - rawconn.go undefined: getsockopt

[Dr. Tobias Quathamer]

Am 14.12.2018 um 14:28 schrieb Martín Ferrari:
> Tobias: I see you did the latest upload, but you did not follow the git
> workflow I had started, and instead of following git commits, you merged
> a snapshot.. I will need to rewrite git history now :(

Hi Martín,

I'm really sorry that I messed up your workflow and caused you extra
work. That was certainly not my intention.

Regards,
Tobias



signature.asc
Description: OpenPGP digital signature

Bug#916459: marked as done (macchanger fails to work on backported kernel of Debian 9.6)

[Debian Bug Tracking System]

Your message dated Fri, 14 Dec 2018 22:25:41 +0200
with message-id <20181214202541.GA28617@localhost>
and subject line Re: Bug#916459: macchanger fails to work on backported kernel 
of Debian 9.6
has caused the Debian Bug report #916459,
regarding macchanger fails to work on backported kernel of Debian 9.6
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.)


-- 
916459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: macchanger
Version: 1.7.0-5.3+b1
Severity: grave
Tags: upstream
Justification: renders package unusable

Hi

As the subject line says, running

sudo macchanger eth0

does not result in a different MAC address



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

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

Versions of packages macchanger depends on:
ii  debconf [debconf-2.0]  1.5.61
ii  dpkg   1.18.25
ii  libc6  2.24-11+deb9u3

macchanger recommends no packages.

macchanger suggests no packages.

-- debconf-show failed
--- End Message ---
--- Begin Message ---
On Fri, Dec 14, 2018 at 05:32:21PM +, Alan Reding wrote:
> Package: macchanger
> Version: 1.7.0-5.3+b1
> Severity: grave
> Tags: upstream
> Justification: renders package unusable
> 
> Hi
> 
> As the subject line says, running
> 
> sudo macchanger eth0
> 
> does not result in a different MAC address

and is not expected to.

>From the manpage:

   -s, --show
  Prints the current MAC. This is the default action when no other 
option is specified.


You were looking for something like
  sudo macchanger -A eth0


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--- End Message ---

Processed: tagging 916463

[Debian Bug Tracking System]

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

> tags 916463 + buster sid
Bug #916463 [src:human-icon-theme] human-icon-theme: FTBFS (No rule to make 
target '/usr/share/gnome-pkg-tools/1/rules/ubuntu-get-source.mk')
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Processed: retitle 916469 to libfixbuf-{dev,doc}: missing Breaks+Replaces: libfixbuf3-{dev,doc} (<< 2)

[Debian Bug Tracking System]

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

> retitle 916469 libfixbuf-{dev,doc}: missing Breaks+Replaces: 
> libfixbuf3-{dev,doc} (<< 2)
Bug #916469 [libfixbuf-dev,libfixbuf-doc] libfixbuf-{dev,doc}: missing 
Breaks+Replaces: libfixbuf3-dev (<< 2)
Changed Bug title to 'libfixbuf-{dev,doc}: missing Breaks+Replaces: 
libfixbuf3-{dev,doc} (<< 2)' from 'libfixbuf-{dev,doc}: missing 
Breaks+Replaces: libfixbuf3-dev (<< 2)'.
> thanks
Stopping processing here.

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

Processed: severity of 893016 is normal

[Debian Bug Tracking System]

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

> # #916471: RM: oclgrind [mips s390x] -- ROM; FTBFS on big-endian architectures
> severity 893016 normal
Bug #893016 [src:oclgrind] oclgrind FTBFS on big endian: test failures
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#916469: libfixbuf-{dev,doc}: missing Breaks+Replaces: libfixbuf3-dev (<< 2)

[Andreas Beckmann]

Package: libfixbuf-dev,libfixbuf-doc
Version: 2.2.0+ds-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../libfixbuf-dev_2.2.0+ds-1_amd64.deb ...
  Unpacking libfixbuf-dev:amd64 (2.2.0+ds-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libfixbuf-dev_2.2.0+ds-1_amd64.deb (--unpack):
   trying to overwrite '/usr/include/fixbuf/autoinc.h', which is also in 
package libfixbuf3-dev:amd64 1.7.1+ds-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libfixbuf-dev_2.2.0+ds-1_amd64.deb

  Preparing to unpack .../libfixbuf-doc_2.2.0+ds-1_all.deb ...
  Unpacking libfixbuf-doc (2.2.0+ds-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libfixbuf-doc_2.2.0+ds-1_all.deb (--unpack):
   trying to overwrite '/usr/share/doc-base/libfixbuf', which is also in 
package libfixbuf3-doc 1.7.1+ds-1
  Errors were encountered while processing:
   /var/cache/apt/archives/libfixbuf-doc_2.2.0+ds-1_all.deb


cheers,

Andreas

PS: you should set the Maintainer to the QA group when doing another upload
if you still intend to orphan the package


libfixbuf3-dev=1.7.1+ds-1_libfixbuf-dev=2.2.0+ds-1.log.gz
Description: application/gzip

Bug#914297: apache2: getrandom call blocks on first startup, systemd kills with timeout

[Stefan Fritsch]

On Friday, 14 December 2018 12:43:29 CET Adrian Bunk wrote:
> On Sun, Nov 25, 2018 at 11:35:37PM +0100, Stefan Fritsch wrote:
> >...
> >
> > I don't see why it should take so
> > long for the random number generator to initialize.
> >
> >...
> 
> On embedded systems without hwrng "10 minutes" or "2 hours" are
> real-life observations for the time it takes.
> 
> Note that this became more problematic due to the CVE-2018-1108[1]
> fix (reverted in stretch, but in buster/unstable).

Is systemd-random-seed.service broken there? The rng should be initialized 
after the seed is loaded from disk. Adrian, please send the output of

journalctl -b UNIT=apache2.service + UNIT=systemd-random-seed.service + 
_TRANSPORT=kernel|grep -i -e apache -e random

if apache2 fails to start.

Bug#916468: dune: /usr/bin/dune is already provided by the whitedune package

[Andreas Beckmann]

Package: dune
Version: 1.6.2-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package dune.
  Preparing to unpack .../dune_1.6.2-1_amd64.deb ...
  Unpacking dune (1.6.2-1) ...
  dpkg: error processing archive /var/cache/apt/archives/dune_1.6.2-1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/bin/dune', which is also in package whitedune 
0.30.10-2.1+b2
  Errors were encountered while processing:
   /var/cache/apt/archives/dune_1.6.2-1_amd64.deb


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  usr/bin/dune
  usr/share/man/man1/dune.1.gz


Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


whitedune=0.30.10-2.1+b2_dune=1.6.2-1.log.gz
Description: application/gzip

Bug#916014: marked as done (squashfs-tools FTBFS with glibc 2.28)

[Debian Bug Tracking System]

Your message dated Fri, 14 Dec 2018 19:21:11 +
with message-id 
and subject line Bug#916014: fixed in squashfs-tools 1:4.3-7
has caused the Debian Bug report #916014,
regarding squashfs-tools FTBFS with glibc 2.28
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.)


-- 
916014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916014
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: squashfs-tools
Version: 1:4.3-6
Severity: serious
Tags: ftbfs

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

...
mksquashfs.c: In function 'create_inode':
mksquashfs.c:989:24: error: called object 'major' is not a function or function 
pointer
   unsigned int major = major(buf->st_rdev);
^
mksquashfs.c:989:16: note: declared here
   unsigned int major = major(buf->st_rdev);
^
mksquashfs.c:990:24: error: called object 'minor' is not a function or function 
pointer
   unsigned int minor = minor(buf->st_rdev);
^
mksquashfs.c:990:16: note: declared here
   unsigned int minor = minor(buf->st_rdev);
^
mksquashfs.c:1013:24: error: called object 'major' is not a function or 
function pointer
   unsigned int major = major(buf->st_rdev);
^
mksquashfs.c:1013:16: note: declared here
   unsigned int major = major(buf->st_rdev);
^
mksquashfs.c:1014:24: error: called object 'minor' is not a function or 
function pointer
   unsigned int minor = minor(buf->st_rdev);
^
--- End Message ---
--- Begin Message ---
Source: squashfs-tools
Source-Version: 1:4.3-7

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated squashfs-tools 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 14 Dec 2018 18:01:49 +
Source: squashfs-tools
Binary: squashfs-tools
Architecture: source
Version: 1:4.3-7
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 squashfs-tools - Tool to create and append to squashfs filesystems
Closes: 916014
Changes:
 squashfs-tools (1:4.3-7) unstable; urgency=medium
 .
   * Fix FTBFS with glibc 2.28 (closes: #916014).
   * Don't use custom compression settings for packaging.
   * Update Standards-Version to 4.2.1 .
Checksums-Sha1:
 fc1211b477ddea43a85e3bf4cdbd20c3e8512273 1935 squashfs-tools_4.3-7.dsc
 c9f50c92d3d5efe5bea5d131f7226ec93062 19612 
squashfs-tools_4.3-7.debian.tar.xz
 33986a823dd03b3cd3cfe25efbc23b7d086220b1 6845 
squashfs-tools_4.3-7_amd64.buildinfo
Checksums-Sha256:
 e900c3e8f60c6ab2b57b55da99d191f9913ca4bcea76dd8f8f1352ba119d9db4 1935 
squashfs-tools_4.3-7.dsc
 8b4ea3bd26d6483304f3f40b7cfff51e20d8a3666517a952da7edc57726cd06b 19612 
squashfs-tools_4.3-7.debian.tar.xz
 49fbc676c9410cb3840c064937229874eaa1b3e24f262beb1c71dd4bae951a92 6845 
squashfs-tools_4.3-7_amd64.buildinfo
Files:
 915423af091e26355a38ae2b6d84adb8 1935 kernel optional squashfs-tools_4.3-7.dsc
 698fd20587fa8fa9f019e5ca967568d0 19612 kernel optional 
squashfs-tools_4.3-7.debian.tar.xz
 73f721f9a5228dd746c6d1ca281d3c36 6845 kernel optional 
squashfs-tools_4.3-7_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAlwT/kwACgkQ3OMQ54ZM
yL/haw//cpVxpd1TQsHskyn7j/DnRqzuhV12TiX0Fz2iHYkVlux0BJaIAGugxmNp
wETQsOYIZMuw3Ln02KKYrwr76doNlAatBEfhKVB/xSj5b8+Bji8xShlfS3NIzejn
vtzmbOiXYEKThtXDlsarbGw/ET4DHOg1D0ox/qRSg8jCo03yfR/gMDk5lG1/RkXW
yOmuj6+j5WDoMj3jC17/JMBk+c/YSdepQKraiw8uHBy0UfZrooUZOPYHRS8+XHap
EeCzQV+1LiQEFkG/aQO2dbWTar8DWqW0fRX5yxIjIUuVTB5PJaZ5XkKncRR+NWin
12BABsJi4tU7S4ElATM9Fid+6/YwmFqX4y9VEaldDam/AuLZQy8YaldpjpUridI4
8Kw6VLo17bwO27u/5BJGQS4jwKUEssf73EvONXsbYb4SdE0zwJ4cyh3QjrYmXVwE
jGQO09unSZ3DS7oJv12obUBMF3l6/CuH7vNaL+eVDDLgEKfXd7kf4yex+yYqUvx1
UGSXDcZuVQc1pqsqCFkxi9s3sgJEWUIeYr9xvcpFEG4VtEuqwYnW0ksmiZkla5Uj

Bug#916308: marked as done (haproxy: CVE-2018-20102)

[Debian Bug Tracking System]

Your message dated Fri, 14 Dec 2018 19:04:51 +
with message-id 
and subject line Bug#916308: fixed in haproxy 1.8.15-1
has caused the Debian Bug report #916308,
regarding haproxy: CVE-2018-20102
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.)


-- 
916308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916308
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haproxy
Version: 1.8.14-1
Severity: grave
Tags: patch security upstream

Hi,

The following vulnerability was published for haproxy, the RC severity
might be not correct, but trying to be on safe side here.

CVE-2018-20102[0]:
| An out-of-bounds read in dns_validate_dns_response in dns.c was
| discovered in HAProxy through 1.8.14. Due to a missing check when
| validating DNS responses, remote attackers might be able read the 16
| bytes corresponding to an  record from the non-initialized part of
| the buffer, possibly accessing anything that was left on the stack, or
| even past the end of the 8193-byte buffer, depending on the value of
| accepted_payload_size.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-20102
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20102
[1] 
http://git.haproxy.org/?p=haproxy.git;a=commit;h=efbbdf72992cd20458259962346044cafd9331c0

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: haproxy
Source-Version: 1.8.15-1

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

Debian distribution maintenance software
pp.
Apollon Oikonomopoulos  (supplier of updated haproxy 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 14 Dec 2018 15:31:04 +0200
Source: haproxy
Binary: haproxy haproxy-doc vim-haproxy
Architecture: source amd64 all
Version: 1.8.15-1
Distribution: unstable
Urgency: high
Maintainer: Debian HAProxy Maintainers 
Changed-By: Apollon Oikonomopoulos 
Description:
 haproxy- fast and reliable load balancing reverse proxy
 haproxy-doc - fast and reliable load balancing reverse proxy (HTML documentatio
 vim-haproxy - syntax highlighting for HAProxy configuration files
Closes: 911933 916307 916308
Changes:
 haproxy (1.8.15-1) unstable; urgency=high
 .
   [ Vincent Bernat ]
   * d/rules: switch to pcre2. Closes: #911933.
 .
   [ Apollon Oikonomopoulos ]
   * New upstream version 1.8.15
 - BUG: dns: Fix off-by-one write in dns_validate_dns_response() (
 - BUG: dns: Fix out-of-bounds read via signedness error in
   dns_validate_dns_response()
 - BUG: dns: Prevent out-of-bounds read in dns_read_name()
 - BUG: dns: Prevent out-of-bounds read in dns_validate_dns_response()
   (CVE-2018-20102, closes: #916308)
 - BUG: dns: Prevent stack-exhaustion via recursion loop in dns_read_name
   (CVE-2018-20103, closes: #916307)
 - BUG/MAJOR: http: http_txn_get_path() may deference an inexisting buffer
Checksums-Sha1:
 11a5246474beb0bd706e1362be293efc296bb4ac 2262 haproxy_1.8.15-1.dsc
 ed7dfe5c7fc39fbb3b54e981eb709fd8bcd87042 2076583 haproxy_1.8.15.orig.tar.gz
 561cec2ca251abc0678db6679a1ac0a994119db5 66452 haproxy_1.8.15-1.debian.tar.xz
 bd085c38e96f8f46d832a9f1db217a7c04ec42e1 3319156 
haproxy-dbgsym_1.8.15-1_amd64.deb
 7f175c3e3951745d4ea7721823d6fc4adcd53f93 525524 haproxy-doc_1.8.15-1_all.deb
 d82628752d5b6f853c6c7648aa7e1ac659c9497a 8099 haproxy_1.8.15-1_amd64.buildinfo
 d3172b1fa1d3b37a5813c0186b33cd7c12d5f989 1298300 haproxy_1.8.15-1_amd64.deb
 221dd1427b613a62917c8408a919e49e13780c65 175928 vim-haproxy_1.8.15-1_all.deb
Checksums-Sha256:
 265a0790d1083b7c8bc4c182f8b370837234837dff047d4177bd7fb98ade9072 2262 
haproxy_1.8.15-1.dsc
 7113862f1146d7de8b8e64f45826ab3533c7f7f7b7767e24c08f7c762202a032 2076583 
haproxy_1.8.15.orig.tar.gz
 f48a7c574b3f32bf804f900ba232f43aa6017525f4375c78ad56ac1834286d1e 66452 

Bug#916463: human-icon-theme: FTBFS (No rule to make target '/usr/share/gnome-pkg-tools/1/rules/ubuntu-get-source.mk')

[Santiago Vila]

Package: src:human-icon-theme
Version: 0.28.debian-5
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]

dpkg-buildpackage
-

dpkg-buildpackage: info: source package human-icon-theme
dpkg-buildpackage: info: source version 0.28.debian-5
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Michael Biebl 
 dpkg-source --before-build .
 fakeroot debian/rules clean
debian/rules:6: /usr/share/gnome-pkg-tools/1/rules/ubuntu-get-source.mk: No 
such file or directory
make: *** No rule to make target 
'/usr/share/gnome-pkg-tools/1/rules/ubuntu-get-source.mk'.  Stop.
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit 
status 2


This used to build ok in the past, so apparently some of the
build-depends changed behaviour recently. In case it helps,
this is part of my build history for buster:

Status: successful human-icon-theme_0.28.debian-5_amd64-20181011T022111Z
Status: successful human-icon-theme_0.28.debian-5_amd64-20181022T020029Z
Status: failed human-icon-theme_0.28.debian-5_amd64-20181206T092923.282Z
Status: failed human-icon-theme_0.28.debian-5_amd64-20181208T113657.747Z

Thanks.

Bug#914051: Discussion on python-freecontact FTBFS

[Alex Mestiashvili]

>In the end we decided to not add additional compatibility links.
>However, the change on your side should be really small: just remove
>"-py" from "boost_python-py" in the setup.py file[1].
>
> [1] https://sources.debian.org/src/python-freecontact/1.1-3/setup.py/#L34
>
>Please let me know if there are problems.
>
>Giovanni.

Thanks for the hint. It was very helpful. I've uploaded the fixed
version of python-freecontact. However it might take some time as the
source package introduces new python3 package and it might stuck in the
new queue.

Regards,
Alex

Processed: tags 914051 + fixed pending

[Debian Bug Tracking System]

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

> tags 914051 + fixed pending
Bug #914051 [src:python-freecontact] python-freecontact FTBFS with boost 1.67
Added tag(s) fixed and pending.
>
End of message, stopping processing here.

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

Bug#916347: epiphany-browser: Don't include in Buster

[Simon McVittie]

On Fri, 14 Dec 2018 at 10:17:18 -0600, mcatanz...@gnome.org wrote:
> On Fri, Dec 14, 2018 at 10:02 AM, Alberto Garcia  wrote:
> > Notice however that the latest stable release of WebKitGTK+ is always
> > available in stable-backports at the same time as in testing, so it
> > is indeed possible to run Epiphany from Debian stable with the most
> > up-to-date WebKitGTK+.
> 
> Perhaps the epiphany package could be made available only in backports?

This only works as long as the epiphany package is in testing, because the
backports team are unwilling to have packages that are in backports but
not in testing (they enforce this so that there is an upgrade path from
Debian 9 with backports to Debian 10, and from Debian 10 with backports
to Debian 11, and so on).

However, if it isn't going to be in the next stable Debian release, then
it needs to be kicked out of testing at some point, because testing *is*
(a candidate for) the next stable Debian release. After that point,
there cannot be any more backports to the previous stable release,
because there is nothing in testing to backport from.

Some possible routes out of this hole:

* Exclude epiphany from testing sometime around freeze time, at which
  point its backports (if any) are EOL. Get it back into testing after
  buster is released.

* Persuade the release team that updating through the next 2+ years of
  new (stable) WebkitGTK+ versions is something they can include in stable
  updates with confidence, and that it is not going to break existing
  software in stable that uses them (including Evolution, Devhelp,
  Balsa, Anjuta, etc. as well as browsers) or grow new dependencies on
  lower levels of the stack like GTK+. The larger and more intrusive the
  changes are (particularly if other packages need changes to keep up),
  the more reluctant they will be.

  (A prerequisite for this is that someone needs to have enough time and
  expertise available to prepare the stable-updates.)

* Persuade the backports team to make an exception for certain packages
  that aren't in testing but only in unstable, and in particular Epiphany.

* Have a third-party apt repository with semi-official backports onto
  Debian stable, similar to mozilla.debian.net.

  (A prerequisite for this is that someone needs to have enough time and
  expertise available to operate it.)

* Make it possible to compile two parallel-installable copies of
  WebkitGTK+: a slow-moving copy that is used by random non-Web,
  non-security-sensitive apps like devhelp, and a fast-moving copy that
  is used by Epiphany (and anything else that renders untrusted HTML and
  can tolerate the possibility of regressions). Keep the slow-moving
  copy mostly static, fixing serious bugs with reviewable patches but
  not swapping between branches, analogous to what we do with
  WebkitGTK+ now (and also analogous to what we do with e.g. glibc, GTK+
  and dbus). Keep the fast-moving copy (and Epiphany) up to date,
  analogous to what happens with Firefox and Chromium.

  For example the slow-moving copy might be in the default linker path
  (/usr/lib/MULTIARCH) and the fast-moving copy might be elsewhere and
  used via -rpath, or they might both be in the default linker path but
  have different SONAMEs.

  (A prerequisite for this is that someone needs to have enough time and
  expertise available to prepare the stable-update for the fast-moving
  copy.)

None of those seem ideal but perhaps they give someone an idea?

smcv

Bug#916347: (no subject)

[Alberto Garcia]

On Fri, Dec 14, 2018 at 09:54:01AM -0600, mcatanz...@gnome.org wrote:

> But equally problematic is the Debian security team's lack of
> interest in allowing updates to the security-critical WebKitGTK+
> package, which is currently vulnerable to issues since WSA-2018-0003
> [1]

Notice however that the latest stable release of WebKitGTK+ is always
available in stable-backports at the same time as in testing, so it
is indeed possible to run Epiphany from Debian stable with the most
up-to-date WebKitGTK+.

Berto

Bug#916077: marked as done (virtualbox-dkms: module FTBFS for 4.18.0-3-686, 4.18.0-3-686-pae)

[Debian Bug Tracking System]

Your message dated Fri, 14 Dec 2018 17:36:49 +0100
with message-id <98d13a39-fc31-5151-15ba-066bd48a4...@debian.org>
and subject line Re: virtualbox-dkms: module FTBFS for 4.18.0-3-686, 
4.18.0-3-686-pae
has caused the Debian Bug report #916077,
regarding virtualbox-dkms: module FTBFS for 4.18.0-3-686, 4.18.0-3-686-pae
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.)


-- 
916077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: virtualbox-dkms
Version: 5.2.22-dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + virtualbox-guest-additions-iso

Hi,

virtualbox-dkms fails to build a module for 4.18.0-3-686,
4.18.0-3-686-pae (in an i386 chroot on an amd64 host, in case
it matters). There are no problems bulding for 4.18.0-3-amd64.
The (attached) make.log starts with:


DKMS make.log for virtualbox-5.2.22 for kernel 4.18.0-3-686 (i686)
Sun Dec  9 20:00:18 UTC 2018
make: Entering directory '/usr/src/linux-headers-4.18.0-3-686'
make[4]: dpkg-architecture: Command not found
  CC [M]  /var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/linux/SUPDrv-linux.o
  CC [M]  /var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/SUPDrv.o
  CC [M]  /var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/SUPDrvGip.o
  CC [M]  /var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/SUPDrvSem.o
In file included from 
/var/lib/dkms/virtualbox/5.2.22/build/include/VBox/types.h:30:0,
 from 
/var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/linux/../SUPDrvInternal.h:35,
 from 
/var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/linux/SUPDrv-linux.c:32:
/var/lib/dkms/virtualbox/5.2.22/build/include/iprt/types.h:280:9: error: 
unknown type name '__uint128_t'
 typedef __uint128_t uint128_t;
 ^~~
/var/lib/dkms/virtualbox/5.2.22/build/include/iprt/types.h:299:9: error: 
unknown type name '__int128_t'
 typedef __int128_t int128_t;
 ^~


Andreas


make.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Hello,
On Sun, 09 Dec 2018 21:09:25 +0100 Andreas Beckmann  wrote:
> Package: virtualbox-dkms
> Version: 5.2.22-dfsg-2
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> Control: affects -1 + virtualbox-guest-additions-iso
> 
> Hi,
> 
> virtualbox-dkms fails to build a module for 4.18.0-3-686,
> 4.18.0-3-686-pae (in an i386 chroot on an amd64 host, in case
> it matters). There are no problems bulding for 4.18.0-3-amd64.
> The (attached) make.log starts with:
> 

I think you can't build kernel modules in this way... nobody reported 
regressions so far, please
try with an i386 kernel space too :)

G.

> 
> DKMS make.log for virtualbox-5.2.22 for kernel 4.18.0-3-686 (i686)
> Sun Dec  9 20:00:18 UTC 2018
> make: Entering directory '/usr/src/linux-headers-4.18.0-3-686'
> make[4]: dpkg-architecture: Command not found
>   CC [M]  /var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/linux/SUPDrv-linux.o
>   CC [M]  /var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/SUPDrv.o
>   CC [M]  /var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/SUPDrvGip.o
>   CC [M]  /var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/SUPDrvSem.o
> In file included from 
> /var/lib/dkms/virtualbox/5.2.22/build/include/VBox/types.h:30:0,
>  from 
> /var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/linux/../SUPDrvInternal.h:35,
>  from 
> /var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/linux/SUPDrv-linux.c:32:
> /var/lib/dkms/virtualbox/5.2.22/build/include/iprt/types.h:280:9: error: 
> unknown type name '__uint128_t'
>  typedef __uint128_t uint128_t;
>  ^~~
> /var/lib/dkms/virtualbox/5.2.22/build/include/iprt/types.h:299:9: error: 
> unknown type name '__int128_t'
>  typedef __int128_t int128_t;
>  ^~
> 
> 
> Andreas--- End Message ---

Bug#916347: (no subject)

[mcatanzaro]

On Fri, Dec 14, 2018 at 10:26 AM, Alberto Garcia  
wrote:

WebKitGTK+ has a policy of being conservative with the build
dependencies so we can rely on it being buildable for Debian stable. I
don't know if that's the case with Epiphany, and if someone has the
time to take care of the backport.


Sorry, I don't actually care very much whether the Epiphany package 
itself is updated in backports or not, because I doubt many people use 
backports. I just don't want people using Epiphany with the WebKitGTK+ 
package in stable, and expecting that it will be safe and 
representative of a well-packaged version of Epiphany.


Michael

Bug#916347: (no subject)

[Alberto Garcia]

On Fri, Dec 14, 2018 at 10:17:18AM -0600, mcatanz...@gnome.org wrote:
> On Fri, Dec 14, 2018 at 10:02 AM, Alberto Garcia  wrote:
> >Notice however that the latest stable release of WebKitGTK+ is always
> >available in stable-backports at the same time as in testing, so it
> >is indeed possible to run Epiphany from Debian stable with the most
> >up-to-date WebKitGTK+.
> 
> Perhaps the epiphany package could be made available only in backports?

WebKitGTK+ has a policy of being conservative with the build
dependencies so we can rely on it being buildable for Debian stable. I
don't know if that's the case with Epiphany, and if someone has the
time to take care of the backport.

Berto

Bug#916347: (no subject)

[mcatanzaro]

On Fri, Dec 14, 2018 at 10:02 AM, Alberto Garcia  
wrote:

Notice however that the latest stable release of WebKitGTK+ is always
available in stable-backports at the same time as in testing, so it
is indeed possible to run Epiphany from Debian stable with the most
up-to-date WebKitGTK+.


Perhaps the epiphany package could be made available only in backports?

Bug#916347: (no subject)

[mcatanzaro]

Thanks Jeremy!

The GStreamer issue is unfortunate indeed, although it comes to mind 
that it is not as important for Debian, since gstreamer-libav is 
available in Debian and YouTube still provides non-MSE H.264 video. So 
low-quality video will still be available, which is a lot better than 
no video. This was not the best example for me to have used yesterday.


But equally problematic is the Debian security team's lack of interest 
in allowing updates to the security-critical WebKitGTK+ package, which 
is currently vulnerable to issues since WSA-2018-0003 [1]. I've been 
complaining about this for about three years now, and it's clear that 
the situation is irreconcilable with Debian's package stability 
policies. Although *very happy* with Debian's packaging in testing and 
unstable, the stable package is old, insufficient for the modern web, 
unsafe to use for its intended purpose, and really only serves to harm 
users' impression of Epiphany. Web browsers are special, and Debian's 
conservative packaging rules simply do not work here. So long as Debian 
maintains its position of not updating WebKitGTK+ in stable, it is 
harmful for it to remain in the stable distro.


Michael

[1] https://webkitgtk.org/security.html

Processed: found 906074 in 4.6.0-1 ...

[Debian Bug Tracking System]

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

> found 906074 4.6.0-1
Bug #906074 [src:libvirt] libvirt: Error connecting to graphical console
Marked as found in versions libvirt/4.6.0-1.
> forwarded 906074 https://bugzilla.redhat.com/show_bug.cgi?id=1614569
Bug #906074 [src:libvirt] libvirt: Error connecting to graphical console
Set Bug forwarded-to-address to 
'https://bugzilla.redhat.com/show_bug.cgi?id=1614569'.
> thanks
Stopping processing here.

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

Processed: fixed 850915 in ghc/8.4.3-4

[Debian Bug Tracking System]

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

> fixed 850915 ghc/8.4.3-4
Bug #850915 [src:ghc] ghc: Please switch to llvm 6.0
Marked as fixed in versions ghc/8.4.3-4.
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> severity 916349 important
Bug #916349 [xterm] xterm: X error (BadLength) when trying to display some 
glyphs
Severity set to 'important' from 'grave'
>
End of message, stopping processing here.

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

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 914565 libcap-ng0
Bug #914565 [libcap-ng] php7.3-intl: Segfaults after apache2 graceful restart
Bug reassigned from package 'libcap-ng' to 'libcap-ng0'.
No longer marked as found in versions 0.7.9-1.
Ignoring request to alter fixed versions of bug #914565 to the same values 
previously set
> forcemerge 904808 914565
Bug #904808 [libcap-ng0] libcap-ng0: libcap-ng's use of pthread_atfork causes 
segfaults
Bug #914565 [libcap-ng0] php7.3-intl: Segfaults after apache2 graceful restart
Set Bug forwarded-to-address to 
'https://github.com/stevegrubb/libcap-ng/issues/5'.
Severity set to 'grave' from 'serious'
902657 was blocked by: 904808
902657 was not blocking any bugs.
Added blocking bug(s) of 902657: 914565
902658 was blocked by: 904808
902658 was not blocking any bugs.
Added blocking bug(s) of 902658: 914565
902658 was blocked by: 904808 914565
902658 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #902658 to the same blocks 
previously set
902657 was blocked by: 904808 914565
902657 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #902657 to the same blocks 
previously set
Marked as found in versions libcap-ng/0.7.9-1.
Merged 904808 914565
> affects 904808 php7.3-intl
Bug #904808 [libcap-ng0] libcap-ng0: libcap-ng's use of pthread_atfork causes 
segfaults
Bug #914565 [libcap-ng0] php7.3-intl: Segfaults after apache2 graceful restart
Added indication that 904808 affects php7.3-intl
Added indication that 914565 affects php7.3-intl
> thanks
Stopping processing here.

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

Processed: Bug #916236 in golang-go.net marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #916236 [golang-golang-x-net-dev] golang-golang-x-net-dev: FTBFS on s390x - 
rawconn.go undefined: getsockopt
Added tag(s) pending.

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

Bug#916236: Bug #916236 in golang-go.net marked as pending

[Martín Ferrari]

Control: tag -1 pending

Hello,

Bug #916236 in golang-go.net reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/go-team/packages/golang-go.net/commit/7130cabebd53c0a171f53dd0c3591a63fa4d2f89


Remove obsolete patch for s390. Closes: #916236.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/916236

Processed (with 3 errors): Merge duplicates

[Debian Bug Tracking System]

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

> reassign 914565
Unknown command or malformed arguments to command.
> forcemerge 904808 914565
Bug #904808 [libcap-ng0] libcap-ng0: libcap-ng's use of pthread_atfork causes 
segfaults
Unable to merge bugs because:
package of #914565 is 'libcap-ng' not 'libcap-ng0'
Failed to forcibly merge 904808: Did not alter merged bugs.

> affects 904808 php7.3-intl
Failed to mark 904808 as affecting package(s): failed to get lock on 
/org/bugs.debian.org/spool/lock/904808 -- Unable to lock 
/org/bugs.debian.org/spool/lock/904808 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/904808 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/904808 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/904808 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/904808 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/904808 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/904808 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/904808 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/904808 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/904808 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 650.

> thanks
Stopping processing here.

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

Bug#916236: golang-golang-x-net-dev: FTBFS on s390x - rawconn.go undefined: getsockopt

[Martín Ferrari]

On 11/12/2018 19:11, Alexandre Viau wrote:
> Package: golang-golang-x-net-dev
> Version: 1:0.0+git20181201.351d144+dfsg-1
> 
> It looks like the golang-golang-x-net-dev build is broken on s390x.


I am also getting similar errors in prometheus-node-exporter. I will
take a look, but it seems this patch is not needed any more.

Tobias: I see you did the latest upload, but you did not follow the git
workflow I had started, and instead of following git commits, you merged
a snapshot.. I will need to rewrite git history now :(

-- 
Martín Ferrari (Tincho)

Processed: 850915 notfound 902999 in 0.3.10-1, reassign 871297 to src:openms ...

[Debian Bug Tracking System]

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

> notfound 850915 8.4.3-4
Bug #850915 [src:ghc] ghc: Please switch to llvm 6.0
No longer marked as found in versions ghc/8.4.3-4.
> thanks
Stopping processing here.

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

Bug#916375: question about your solution

[cyrille]

Hi,

If you suspect perl 'security update, you might want to try reverting to 
the previous version:


apt-get install libperl5.24=5.24.1-3+deb9u4

Br,

Cyrille

Bug#916430: wifite FTBFS: FAIL: testHandshakeAircrack (test_Handshake.TestHandshake)

[Adrian Bunk]

Source: wifite
Version: 2.2.5-1
Severity: serious
Tags: ftbfs

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

...
==
FAIL: testHandshakeAircrack (test_Handshake.TestHandshake)
--
Traceback (most recent call last):
  File "/build/1st/wifite-2.2.5/tests/test_Handshake.py", line 55, in 
testHandshakeAircrack
assert(len(hs.aircrack_handshakes()) > 0)
AssertionError

--
Ran 9 tests in 2.142s

FAILED (failures=1, skipped=2)
make[1]: *** [debian/rules:9: override_dh_auto_test] Error 1

Bug#913380: marked as done (tarantool FTBFS with curl 7.62.0)

[Debian Bug Tracking System]

Your message dated Fri, 14 Dec 2018 11:51:15 +
with message-id 
and subject line Bug#913380: fixed in tarantool 1.9.1.26.g63eb81e3c-1.1
has caused the Debian Bug report #913380,
regarding tarantool FTBFS with curl 7.62.0
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.)


-- 
913380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913380
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tarantool
Version: 1.9.1.26.g63eb81e3c-1
Severity: serious
Tags: ftbfs

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

...
cd /build/1st/tarantool-1.9.1.26.g63eb81e3c/obj-x86_64-linux-gnu/src && 
/usr/bin/cc -DCORO_ASM -DLUAJIT_SMART_STRINGS=1 -DNDEBUG -DNVALGRIND 
-DNVALGRIND=1 -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS=1 
-D__STDC_FORMAT_MACROS=1 -D__STDC_LIMIT_MACROS=1 
-I/build/1st/tarantool-1.9.1.26.g63eb81e3c/src 
-I/build/1st/tarantool-1.9.1.26.g63eb81e3c/obj-x86_64-linux-gnu/src 
-I/build/1st/tarantool-1.9.1.26.g63eb81e3c/src/lib 
-I/build/1st/tarantool-1.9.1.26.g63eb81e3c/src/lib/small 
-I/build/1st/tarantool-1.9.1.26.g63eb81e3c/src/lib/small/third_party 
-I/build/1st/tarantool-1.9.1.26.g63eb81e3c 
-I/build/1st/tarantool-1.9.1.26.g63eb81e3c/third_party/zstd/lib 
-I/build/1st/tarantool-1.9.1.26.g63eb81e3c/third_party/zstd/lib/common 
-I/build/1st/tarantool-1.9.1.26.g63eb81e3c/obj-x86_64-linux-gnu/third_party 
-I/build/1st/tarantool-1.9.1.26.g63eb81e3c/third_party 
-I/build/1st/tarantool-1.9.1.26.g63eb81e3c/third_party/coro 
-I/build/1st/tarantool-1.9.1.26.g63eb81e3c/third_party/luajit/src 
-I/build/1st/tarantool-1.9.1.26.g63eb81e3c/src/lib/msgpuck 
-I/usr/include/x86_64-linux-gnu 
-I/build/1st/tarantool-1.9.1.26.g63eb81e3c/third_party/libutil_freebsd  -g -O2 
-ffile-prefix-map=/build/1st/tarantool-1.9.1.26.g63eb81e3c=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -Wformat -Werror=format-security 
-Wdate-time -D_FORTIFY_SOURCE=2 -fexceptions -funwind-tables 
-fno-omit-frame-pointer -fno-stack-protector -fno-common -fopenmp -msse2 
-std=c11 -Wall -Wextra -Wno-strict-aliasing -Wno-char-subscripts 
-Wno-format-truncation -fno-gnu89-inline -O2 -g -DNDEBUG -ggdb -O2   -o 
CMakeFiles/server.dir/httpc.c.o   -c 
/build/1st/tarantool-1.9.1.26.g63eb81e3c/src/httpc.c
/build/1st/tarantool-1.9.1.26.g63eb81e3c/src/httpc.c: In function 
'httpc_execute':
/build/1st/tarantool-1.9.1.26.g63eb81e3c/src/httpc.c:336:2: error: duplicate 
case value
  case CURLE_PEER_FAILED_VERIFICATION:
  ^~~~
/build/1st/tarantool-1.9.1.26.g63eb81e3c/src/httpc.c:335:2: note: previously 
used here
  case CURLE_SSL_CACERT:
  ^~~~
make[3]: *** [src/CMakeFiles/server.dir/build.make:425: 
src/CMakeFiles/server.dir/httpc.c.o] Error 1


For background see
https://github.com/curl/curl/commit/3f3b26d6feb0667714902e836af608094235fca2
--- End Message ---
--- Begin Message ---
Source: tarantool
Source-Version: 1.9.1.26.g63eb81e3c-1.1

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated tarantool 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: Fri, 30 Nov 2018 12:45:36 +0200
Source: tarantool
Binary: tarantool-common tarantool tarantool-dev
Architecture: source
Version: 1.9.1.26.g63eb81e3c-1.1
Distribution: unstable
Urgency: medium
Maintainer: Roman Tsisyk 
Changed-By: Adrian Bunk 
Description:
 tarantool  - In-memory database with a Lua application server
 tarantool-common - Tarantool in-memory database - common files
 tarantool-dev - Tarantool in-memory database - development headers
Closes: 913380
Changes:
 tarantool (1.9.1.26.g63eb81e3c-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add upstream fix for FTBFS with curl >= 7.62. (Closes: #913380)
Checksums-Sha1:
 c19e605f359d058ecfda7312a6c9b9c2335f88e7 2460 
tarantool_1.9.1.26.g63eb81e3c-1.1.dsc
 a5a3fa297a40e17b3dcd5e4b4178620028d31c57 15208 
tarantool_1.9.1.26.g63eb81e3c-1.1.debian.tar.xz
Checksums-Sha256:
 

Bug#905254: libphp-phpmailer: Please update to version 6.x

[Craig Small]

Regarding wordpress and libphp-phpmailer. 5.0.1 will no longer depend on
libphp-phpmailer but use the one shipped with WordPress.

Except, its about as old :/
WordPress upstream are aware of it [1], we'll see what they do next.

 - Craig


1: https://core.trac.wordpress.org/ticket/40472#comment:25

On Sat, 8 Dec 2018 at 11:28, Craig Small  wrote:

> WordPress probably uses its own version which, I assume, they will
> maintain afterwards.
>
> I'll see if I can find more about what they're doing with it for the
> longer term.
>
> The easiest way for me is to just drop the depends.
>
>  - Craig
>
>
> On Sat, 8 Dec. 2018, 02:06 Salvatore Bonaccorso 
>> Control: severity -1 serious
>>
>> As mentioned in
>> https://github.com/PHPMailer/PHPMailer/releases/tag/v5.2.27 the 5.2
>> branch is deprecated and will not recieve security updates anymore
>> after 31st December 2018.
>>
>> This is not an issue per se, as we usually need to backport fixes to
>> older versions in general for bugfixes but in particular for
>> security-fixes; but starting buster with a know deprecated and not
>> supported version given upstream actively develops on the 6.x branch
>> looks somehow problematic for the buster release cycle.
>>
>> For this concern, I'm raising the severity to RC.
>>
>> there are a couple of packages with Depends or Build-Depends on
>> libphp-phpmailer, and I'm X-Debbugs-CC'ing those here.
>>
>> # Broken Depends:
>> cacti: cacti
>> tt-rss: tt-rss
>> wordpress: wordpress
>>
>> # Broken Build-Depends:
>> wordpress: libphp-phpmailer (>= 5.2.14)
>>
>> Regards,
>> Salvatore
>>
>

Bug#914297: apache2: getrandom call blocks on first startup, systemd kills with timeout

[Adrian Bunk]

On Sun, Nov 25, 2018 at 11:35:37PM +0100, Stefan Fritsch wrote:
>...
> I don't see why it should take so 
> long for the random number generator to initialize.
>...

On embedded systems without hwrng "10 minutes" or "2 hours" are 
real-life observations for the time it takes.

Note that this became more problematic due to the CVE-2018-1108[1]
fix (reverted in stretch, but in buster/unstable).

cu
Adrian

[1] https://security-tracker.debian.org/tracker/CVE-2018-1108

-- 

   "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

Bug#916377: marked as done (cups-browsed: segfault during upgrade and at system shutdown)

[Debian Bug Tracking System]

Your message dated Fri, 14 Dec 2018 11:19:24 +
with message-id 
and subject line Bug#916149: fixed in cups-filters 1.21.5-2
has caused the Debian Bug report #916149,
regarding cups-browsed: segfault during upgrade and at system shutdown
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.)


-- 
916149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916149
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cups-browsed
Version: 1.21.5-1
Severity: serious
Justification: segfaults

Setting up cups-browsed (1.21.5-1) ...
Installing new version of config file /etc/cups/cups-browsed.conf ...
Restarting CUPS Bonjour daemon: cups-browsed.
[ 1143.414255] cups-browsed[8312]: segfault at b8 ip 55dfd9fce560 sp 
7fffa05d5b20 error 4 in cups-browsed[55dfd9fc1000+17000]
[ 1143.420137] Code: 98 41 8b 8c 24 b4 00 00 00 85 c9 0f 84 7f ff ff ff 4c 89 
e7 e8 b1 fa ff ff 83 3d aa 90 01 00 01 0f 84 ec fe ff ff 0f 1f 40 00 <41> 8b 94 
24 b8 00 00 00 85 d2 0f 84 67 ff ff ff 49 8b 34 24 48 8d 


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

Kernel: Linux 4.18.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages cups-browsed depends on:
ii  cups-daemon   2.2.10-1
ii  libavahi-client3  0.7-4+b1
ii  libavahi-common3  0.7-4+b1
ii  libavahi-glib10.7-4+b1
ii  libc6 2.28-2
ii  libcups2  2.2.10-1
ii  libcupsfilters1   1.21.5-1
ii  libglib2.0-0  2.58.1-2
ii  libldap-2.4-2 2.4.46+dfsg-5+b1
ii  lsb-base  10.2018112800

Versions of packages cups-browsed recommends:
ii  avahi-daemon  0.7-4+b1

cups-browsed suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: cups-filters
Source-Version: 1.21.5-2

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

Debian distribution maintenance software
pp.
Didier Raboud  (supplier of updated cups-filters 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: Fri, 14 Dec 2018 11:54:44 +0100
Source: cups-filters
Binary: libcupsfilters1 libfontembed1 cups-filters cups-filters-core-drivers 
libcupsfilters-dev libfontembed-dev cups-browsed
Architecture: source
Version: 1.21.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Printing Team 
Changed-By: Didier Raboud 
Description:
 cups-browsed - OpenPrinting CUPS Filters - cups-browsed
 cups-filters - OpenPrinting CUPS Filters - Main Package
 cups-filters-core-drivers - OpenPrinting CUPS Filters - Driverless printing
 libcupsfilters-dev - OpenPrinting CUPS Filters - Development files for the 
library
 libcupsfilters1 - OpenPrinting CUPS Filters - Shared library
 libfontembed-dev - OpenPrinting CUPS Filters - Development files for font 
embed libr
 libfontembed1 - OpenPrinting CUPS Filters - Font Embed Shared library
Closes: 916149
Changes:
 cups-filters (1.21.5-2) unstable; urgency=medium
 .
   * Backport upstream patch:
 - cups-browsed: Fixed crashes caused by checking HTTP timeouts
   (Closes: #916149)
   * Cleanup d/control thanks to `cme`
   * Add gitlab-ci.yml from Salsa CI Team
Checksums-Sha1:
 e986037d2ec5e4cc9a9f3fdf9d72d46fa4a0fadf 2775 cups-filters_1.21.5-2.dsc
 9c15560b869bb8425031db0e3256bd3d97e27fb6 74896 
cups-filters_1.21.5-2.debian.tar.xz
Checksums-Sha256:
 dea6a5e0401637644d1fa61eed0b71ae921769cbb57014335934b837dd402ae9 2775 
cups-filters_1.21.5-2.dsc
 6ccb49d2906758b29bf3a348e9cdc62d8ce60f5bc6845d392dcb6425f28acf11 74896 
cups-filters_1.21.5-2.debian.tar.xz
Files:
 2fd4cb20a87d8a4ae5858d94b4612827 2775 net optional cups-filters_1.21.5-2.dsc
 8e8e44772f8cf734b22edd9126f35358 74896 net optional 
cups-filters_1.21.5-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEe+WPIRpjNw1/GSB7i8+nHsoWNFUFAlwTjgEACgkQi8+nHsoW

Bug#916149: marked as done (Segfault on systemctl stop or systemctl restart)

[Debian Bug Tracking System]

Your message dated Fri, 14 Dec 2018 11:19:24 +
with message-id 
and subject line Bug#916149: fixed in cups-filters 1.21.5-2
has caused the Debian Bug report #916149,
regarding Segfault on systemctl stop or systemctl restart
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.)


-- 
916149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916149
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cups-browsed
Version: 1.21.4-1
Severity: important

(Note: I'm currently running 1.21.5-1, but have set the version above
because I believe this started with 1.21.4-1. I apologize for not
reporting it earlier — I hadn't noticed it...)

Every time cups-browsed is stopped (or restarted), it segfaults. Since
its restarted every night, I checked the journal to see when this
behavior started (note the logs go back to September — so it started on
December 4). There are a bunch more on the 5th, from restarting it many
times about the now-fixed job-loss bug.

Dec 04 00:00:04 Zia systemd[1]: cups-browsed.service: Main process exited, 
code=killed, status=11/SEGV
Dec 05 00:00:08 Zia systemd[1]: cups-browsed.service: Main process exited, 
code=killed, status=11/SEGV
Dec 05 11:28:13 Zia systemd[1]: cups-browsed.service: Main process exited, 
code=killed, status=11/SEGV
Dec 05 11:28:42 Zia systemd[1]: cups-browsed.service: Main process exited, 
code=killed, status=11/SEGV
Dec 05 11:29:03 Zia systemd[1]: cups-browsed.service: Main process exited, 
code=killed, status=11/SEGV

The logs continue like that through present, including a few test stops
I just did to be sure.

I looked at the dpkg log and found:

2018-12-03 16:04:59 upgrade cups-browsed:amd64 1.21.3-3 1.21.4-1
2018-12-03 16:04:59 status half-configured cups-browsed:amd64 1.21.3-3
2018-12-03 16:04:59 status unpacked cups-browsed:amd64 1.21.3-3
2018-12-03 16:04:59 status half-installed cups-browsed:amd64 1.21.3-3
2018-12-03 16:05:00 status unpacked cups-browsed:amd64 1.21.4-1
⋮
2018-12-03 16:15:11 configure cups-browsed:amd64 1.21.4-1 
2018-12-03 16:15:11 status unpacked cups-browsed:amd64 1.21.4-1
2018-12-03 16:15:26 conffile /etc/cups/cups-browsed.conf keep
2018-12-03 16:15:26 status half-configured cups-browsed:amd64 1.21.4-1
2018-12-03 16:15:28 status installed cups-browsed:amd64 1.21.4-1

So I think that 1.21.4-1 introduced this.

I installed systemd-coredump to get a core dump and thus back trace (via
gdb), which I have attached.


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

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

Versions of packages cups-browsed depends on:
ii  cups-daemon   2.2.9-2
ii  libavahi-client3  0.7-4+b1
ii  libavahi-common3  0.7-4+b1
ii  libavahi-glib10.7-4+b1
ii  libc6 2.27-8
ii  libcups2  2.2.9-2
ii  libcupsfilters1   1.21.4-1
ii  libglib2.0-0  2.58.1-2
ii  libldap-2.4-2 2.4.46+dfsg-5+b1
ii  lsb-base  9.20170808

Versions of packages cups-browsed recommends:
ii  avahi-daemon  0.7-4+b1

cups-browsed suggests no packages.

-- Configuration Files:
/etc/cups/cups-browsed.conf changed:
BrowseRemoteProtocols none
BrowseLocalProtocols none
BrowsePoll watt.home
NewIPPPrinterQueuesShared No
AutoClustering No


-- no debconf information


cups-browsed-backtrace.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: cups-filters
Source-Version: 1.21.5-2

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

Debian distribution maintenance software
pp.
Didier Raboud  (supplier of updated cups-filters 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

Bug#914764: marked as done (biometric-driver-community-multidevice: modifies conffiles (policy 10.7.3): /etc/biometric-auth/biometric-drivers.conf)

[Debian Bug Tracking System]

Your message dated Fri, 14 Dec 2018 11:04:36 +
with message-id 
and subject line Bug#914764: fixed in biometric-authentication 0.9.61-2
has caused the Debian Bug report #914764,
regarding biometric-driver-community-multidevice: modifies conffiles (policy 
10.7.3): /etc/biometric-auth/biometric-drivers.conf
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.)


-- 
914764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914764
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: biometric-driver-community-multidevice
Version: 0.9.56-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package modifies conffiles.
This is forbidden by the policy, see
https://www.debian.org/doc/debian-policy/ch-files.html#configuration-files

10.7.3: "[...] The easy way to achieve this behavior is to make the
configuration file a conffile. [...] This implies that the default
version will be part of the package distribution, and must not be
modified by the maintainer scripts during installation (or at any
other time)."

Note that once a package ships a modified version of that conffile,
dpkg will prompt the user for an action how to handle the upgrade of
this modified conffile (that was not modified by the user).

Further in 10.7.3: "[...] must not ask unnecessary questions
(particularly during upgrades) [...]"

If a configuration file is customized by a maintainer script after
having asked some debconf questions, it may not be marked as a
conffile. Instead a template could be installed in /usr/share and used
by the postinst script to fill in the custom values and create (or
update) the configuration file (preserving any user modifications!).
This file must be removed during postrm purge.
ucf(1) may help with these tasks.
See also https://wiki.debian.org/DpkgConffileHandling

In https://lists.debian.org/debian-devel/2012/09/msg00412.html and
followups it has been agreed that these bugs are to be filed with
severity serious.

debsums reports modification of the following files,
from the attached log (scroll to the bottom...):

  /etc/biometric-auth/biometric-drivers.conf


cheers,

Andreas


biometric-driver-community-multidevice_0.9.56-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: biometric-authentication
Source-Version: 0.9.61-2

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

Debian distribution maintenance software
pp.
handsome_feng  (supplier of updated 
biometric-authentication package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 10 Dec 2018 10:58:34 +0800
Source: biometric-authentication
Binary: biometric-auth libbiometric0 libbiometric-dev biometric-utils 
biometric-driver-community-multidevice
Architecture: source amd64
Version: 0.9.61-2
Distribution: unstable
Urgency: medium
Maintainer: Kylin Team 
Changed-By: handsome_feng 
Description:
 biometric-auth - Biometric Authentication Service
 biometric-driver-community-multidevice - Biometric Authentication Driver 
(community multidevice)
 biometric-utils - Biometric authentication utils
 libbiometric-dev - Biometric Identification DRIVER API - development files
 libbiometric0 - Biometric Identification library
Closes: 914764
Changes:
 biometric-authentication (0.9.61-2) unstable; urgency=medium
 .
   * Change the configuration file to the configuration template file
 - Rename biometric-drivers.conf to biometric-drivers.conf.template
 - The default configuration template file is installed to
   /usr/share/biometric-auth/
   (Closes: #914764)
Checksums-Sha1:
 7d7115e54d976f519fb8a64832a42efdc656409f 2217 
biometric-authentication_0.9.61-2.dsc
 30ca24afc97bf00cbe667a20bf3a51edef1cf968 134356 
biometric-authentication_0.9.61.orig.tar.gz
 9a47c17b05813388b81b09c7f930696ef22e1a8b 5412 
biometric-authentication_0.9.61-2.debian.tar.xz
 6e09d22bcbd3ffa85842ad7c64e26c7b981da497 77196 
biometric-auth-dbgsym_0.9.61-2_amd64.deb
 

Bug#916375: question about your solution

[Hans-Georg Thien]

Hi,

we have already tried that too. But (to my surprise) no change regarding 
the SEGV problem.


- Hans

cyri...@bollu.be wrote:

Hi,

If you suspect perl 'security update, you might want to try reverting 
to the previous version:


apt-get install libperl5.24=5.24.1-3+deb9u4

Br,

Cyrille



--
Hans-Georg Thien | Software Engineer
callas software GmbH | Schoenhauser Allee 6/7 | 10119 Berlin | Germany
Tel +49.30.4439031-0 | Fax +49.30.4416402 | www.callassoftware.com
Amtsgericht Charlottenburg, HRB 59615
Geschäftsführung: Olaf Drümmer, Ulrich Frotscher, Dietrich von Seggern

Bug#915050: Keep out of testing

[Pirate Praveen]

On Thu, 29 Nov 2018 20:59:59 +0100 Moritz Muehlenhoff 
wrote:
> Source: gitlab
> Severity: serious
> 
> Gitlab is too fast-moving with weekly releases and backporting security fixes 
> has already
> failed us for stretch, keep it out of testing.

Just a clarification, major release happens every month, and security
updates are provided for last 3 major releases (so upto 3 months).

> To meaningfully support it for use on stable, this would require some of the
> infrastructure/policy changes discussed in the "What can Debian do to provide
> complex applications to its users" thread from earlier the year on 
> debian-devel.

Would it be okay to close this bug after buster release? That would make
it possible to provide newer versions via buster-backports. For
buster+1, we can remove it from testing again, close to freeze.



signature.asc
Description: OpenPGP digital signature

Bug#897877: marked as done (trinityrnaseq: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Fri, 14 Dec 2018 09:36:14 +
with message-id 
and subject line Bug#897877: fixed in trinityrnaseq 2.6.6+dfsg-1
has caused the Debian Bug report #897877,
regarding trinityrnaseq: ftbfs with GCC-8
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.)


-- 
897877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897877
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:trinityrnaseq
Version: 2.5.1+dfsg-2
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-8

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-8/g++-8, but succeeds to build with gcc-7/g++-7. The
severity of this report will be raised before the buster release.

The full build log can be found at:
http://aws-logs.debian.net/2018/05/01/gcc8/trinityrnaseq_2.5.1+dfsg-2_unstable_gcc8.log.gz
The last lines of the build log are at the end of this report.

To build with GCC 8, either set CC=gcc-8 CXX=g++-8 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-8/porting_to.html

[...]
mv slclust ../bin/
make[3]: Leaving directory 
'/<>/trinityrnaseq-2.5.1+dfsg/trinity-plugins/slclust/src'
make[1]: Leaving directory '/<>/trinityrnaseq-2.5.1+dfsg'
   debian/rules override_dh_install-arch
make[1]: Entering directory '/<>/trinityrnaseq-2.5.1+dfsg'
dh_install -a
dh_install: Cannot find (any matches for) "Chrysalis/TranscriptomeFromVaryK" 
(tried in ., debian/tmp)

dh_install: trinityrnaseq missing files: Chrysalis/TranscriptomeFromVaryK
dh_install: Cannot find (any matches for) "Chrysalis/RunButterfly" (tried in ., 
debian/tmp)

dh_install: trinityrnaseq missing files: Chrysalis/RunButterfly
dh_install: Cannot find (any matches for) 
"Chrysalis/ReadsToTranscripts_MPI_chang" (tried in ., debian/tmp)

dh_install: trinityrnaseq missing files: Chrysalis/ReadsToTranscripts_MPI_chang
dh_install: Cannot find (any matches for) "Chrysalis/ReadsToTranscripts_MPI" 
(tried in ., debian/tmp)

dh_install: trinityrnaseq missing files: Chrysalis/ReadsToTranscripts_MPI
dh_install: Cannot find (any matches for) "Chrysalis/ReadsToTranscripts" (tried 
in ., debian/tmp)

dh_install: trinityrnaseq missing files: Chrysalis/ReadsToTranscripts
dh_install: Cannot find (any matches for) "Chrysalis/QuantifyGraph" (tried in 
., debian/tmp)

dh_install: trinityrnaseq missing files: Chrysalis/QuantifyGraph
dh_install: Cannot find (any matches for) "Chrysalis/JoinTransByPairs" (tried 
in ., debian/tmp)

dh_install: trinityrnaseq missing files: Chrysalis/JoinTransByPairs
dh_install: Cannot find (any matches for) "Chrysalis/IsoformAugment" (tried in 
., debian/tmp)

dh_install: trinityrnaseq missing files: Chrysalis/IsoformAugment
dh_install: Cannot find (any matches for) "Chrysalis/GraphFromFasta_MPI" (tried 
in ., debian/tmp)

dh_install: trinityrnaseq missing files: Chrysalis/GraphFromFasta_MPI
dh_install: Cannot find (any matches for) "Chrysalis/GraphFromFasta" (tried in 
., debian/tmp)

dh_install: trinityrnaseq missing files: Chrysalis/GraphFromFasta
dh_install: Cannot find (any matches for) "Chrysalis/CreateIwormFastaBundle" 
(tried in ., debian/tmp)

dh_install: trinityrnaseq missing files: Chrysalis/CreateIwormFastaBundle
dh_install: Cannot find (any matches for) "Chrysalis/Chrysalis" (tried in ., 
debian/tmp)

dh_install: trinityrnaseq missing files: Chrysalis/Chrysalis
dh_install: Cannot find (any matches for) "Chrysalis/BreakTransByPairs" (tried 
in ., debian/tmp)

dh_install: trinityrnaseq missing files: Chrysalis/BreakTransByPairs
dh_install: missing files, aborting
make[1]: *** [debian/rules:46: override_dh_install-arch] Error 25
make[1]: Leaving directory '/<>/trinityrnaseq-2.5.1+dfsg'
make: *** [debian/rules:19: binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned 
exit status 2
--- End Message ---
--- Begin Message ---
Source: trinityrnaseq
Source-Version: 2.6.6+dfsg-1

We believe that the bug you reported is fixed in the latest version of

Bug#891434: grub-efi: System fails to boot after "No space left on device" on EFI variable storage

[Ralf Jung]

Hi,

> Fixing this does seem like it would be a good idea for general
> robustness against dodgy firmware (this is not the first iteration of
> problems along these lines).  It would take some development work, but
> hopefully not too much.
> 
> Things that GRUB can't do, as far as I can tell:
> 
>  * I don't think there's a way for GRUB to check whether it will be
>possible to recreate a boot entry later; as I understand it, that
>depends on various low-level details, including firmware-specific
>quirks.
>
>  * Even detecting that nothing changed would require cooperation from
>efibootmgr, since the encoding of the EFI variable is an
>implementation detail there (so we can't just read it out and
>compare), and efibootmgr doesn't expose a way for GRUB to say "set
>this configuration, but only if it's different from what's already
>there".
> 
> However, I think GRUB can at least manage to delete all but one entry
> from the same distributor rather than all of them, and if it finds one
> remaining entry then it can modify that rather than writing a brand new
> variable.  As I understand it, that would probably be enough to fix this
> bug?

Assuming that modification works even when the variable storage is (close to)
full, then yes, that would at least keep the device bootable which would be a
big improvement.

Kind regards,
Ralf

Processed: bug 915765 is forwarded to https://github.com/dnephin/PyStaticConfiguration/issues/104

[Debian Bug Tracking System]

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

> forwarded 915765 https://github.com/dnephin/PyStaticConfiguration/issues/104
Bug #915765 [src:pystaticconfiguration] pystaticconfiguration FTBFS: test error
Set Bug forwarded-to-address to 
'https://github.com/dnephin/PyStaticConfiguration/issues/104'.
> thanks
Stopping processing here.

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

Processed (with 1 error): FTBFS with pytest 3.10

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1
Unknown command or malformed arguments to command.

> tag -1 + upstream
Bug #915765 [src:pystaticconfiguration] pystaticconfiguration FTBFS: test error
Added tag(s) upstream.

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

Bug#915765: FTBFS with pytest 3.10

[Sébastien Delafond]

Control: forwarded -1 
Control: tag -1 + upstream

Let's wait a bit for upstream's take on this issue, that was triggered
when pytest 3.10 entered unstable last month. If need be, we could
disable TestConfigurationWatcher::* when building the python2 package.

Cheers,

-- 
Seb

Bug#911180: marked as done (freeradius: freeradius refuses to start - missing libs)

[Debian Bug Tracking System]

Your message dated Fri, 14 Dec 2018 09:04:16 +
with message-id 
and subject line Bug#911180: fixed in freeradius 3.0.16+dfsg-5
has caused the Debian Bug report #911180,
regarding freeradius: freeradius refuses to start - missing libs
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.)


-- 
911180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911180
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: freeradius
Version: 3.0.16+dfsg-4.1+b1
Severity: grave
Justification: renders package unusable

After upgrade, freeradius refuses to start.
In its log we can see:

Tue Oct 16 21:59:52 2018 : Error: /etc/freeradius/3.0/mods-enabled/dhcp[18]: 
Failed to link to module 'rlm_dhcp': libfreeradius-dhcp.so: cannot open shared 
object file: No such file or directory 

bug is mysterious because:
[from /etc/freeradius/3.0/radiusd.conf]
libdir = /usr/lib/freeradius/

#ls -la /usr/lib/freeradius/rlm_dhcp* 
-rw-r--r-- 1 root root 14344 Oct 13 06:49 /usr/lib/freeradius/rlm_dhcp.so


moreover (I do not know if it is important)
#ldd /usr/lib/freeradius/rlm_dhcp.so
linux-vdso.so.1 (0x7fff15dcc000)
libfreeradius-dhcp.so => not found
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f4c96b7a000)
/lib64/ld-linux-x86-64.so.2 (0x7f4c96d78000)


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

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

Versions of packages freeradius depends on:
ii  freeradius-common  3.0.16+dfsg-4.1
ii  freeradius-config  3.0.16+dfsg-4.1+b1
ii  libc6  2.27-6
ii  libcap21:2.25-1.2
ii  libct4 1.00.82-2+b1
ii  libfreeradius3 3.0.16+dfsg-4.1+b1
ii  libgdbm6   1.18-2
ii  libpam0g   1.1.8-3.8
ii  libpcre3   2:8.39-11
ii  libperl5.265.26.2-7+b1
ii  libreadline7   7.0-5
ii  libsqlite3-0   3.25.2-1
ii  libssl1.1  1.1.1-1
ii  libtalloc2 2.1.14-1
ii  libwbclient0   2:4.8.5+dfsg-1
ii  lsb-base   9.20170808

Versions of packages freeradius recommends:
ii  freeradius-utils  3.0.16+dfsg-4.1+b1

Versions of packages freeradius suggests:
pn  freeradius-krb5
ih  freeradius-ldap3.0.16+dfsg-4.1+b1
pn  freeradius-mysql   
ih  freeradius-postgresql  3.0.16+dfsg-4.1+b1
pn  freeradius-python2 
ii  snmp   5.7.3+dfsg-3

-- Configuration Files:
/etc/default/freeradius changed:
FREERADIUS_OPTIONS="-xxx -l /var/log/freeradius/radius.log"

/etc/logrotate.d/freeradius changed:
/var/log/freeradius/*.log {
weekly
compress
delaycompress
notifempty
missingok
postrotate
/etc/init.d/freeradius reload > /dev/null
endscript
}


-- no debconf information
--- End Message ---
--- Begin Message ---
Source: freeradius
Source-Version: 3.0.16+dfsg-5

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

Debian distribution maintenance software
pp.
Michael Stapelberg  (supplier of updated freeradius 
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: Fri, 14 Dec 2018 09:33:40 +0100
Source: freeradius
Binary: freeradius freeradius-common freeradius-config freeradius-utils 
libfreeradius3 libfreeradius-dev freeradius-dhcp freeradius-krb5 
freeradius-ldap freeradius-rest freeradius-postgresql freeradius-mysql 
freeradius-iodbc freeradius-redis freeradius-memcached freeradius-yubikey 
freeradius-python2
Architecture: source
Version: 3.0.16+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian FreeRADIUS Packaging Team 

Changed-By: Michael Stapelberg 
Description:
 freeradius - high-performance and highly configurable RADIUS server
 freeradius-common - FreeRADIUS 

Bug#911909: marked as done (freeradius: Failed to link to module 'rlm_dhcp': libfreeradius-dhcp.so: cannot open shared object file: No such file or directory)

[Debian Bug Tracking System]

Your message dated Fri, 14 Dec 2018 09:04:16 +
with message-id 
and subject line Bug#911180: fixed in freeradius 3.0.16+dfsg-5
has caused the Debian Bug report #911180,
regarding freeradius: Failed to link to module 'rlm_dhcp': 
libfreeradius-dhcp.so: cannot open shared object file: No such file or directory
to be marked as done.

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

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


-- 
911180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911180
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: freeradius
Version: 3.0.16+dfsg-4.1+b1
Severity: grave
Justification: renders package unusable

After the latest update the freeradius dhcp-module is broken - this
shows as it is unable to link rlm_dhcp.

The error message I get is:
/etc/freeradius/3.0/mods-enabled/dhcp[18]: Failed to link to module 'rlm_dhcp': 
libfreeradius-dhcp.so: cannot open shared object file: No such file or directory

The file exists though:
$ find /usr | grep "libfreeradius-dhcp.so"
/usr/lib/freeradius/libfreeradius-dhcp.so

State of freeradius-dhcp
C   freeradius-dhcp3.0.16+dfsg-4.1+b1  
I tried to reinstall the package which caused it to be marked as broken
since the reconfigure failed.

When stracing the freeradius process you can see it trying to find the
library in various places but never in /usr/lib/freeradius. I've
attached that part from strace below.


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages freeradius depends on:
ii  freeradius-common  3.0.16+dfsg-4.1
ii  freeradius-config  3.0.16+dfsg-4.1+b1
ii  libc6  2.27-6
ii  libcap21:2.25-1.2
ii  libct4 1.00.104-1
ii  libfreeradius3 3.0.16+dfsg-4.1+b1
ii  libgdbm6   1.18-2
ii  libpam0g   1.1.8-3.8
ii  libpcre3   2:8.39-11
ii  libperl5.265.26.2-7+b1
ii  libreadline7   7.0-5
ii  libsqlite3-0   3.25.2-1
ii  libssl1.1  1.1.0h-4
ii  libtalloc2 2.1.14-1
ii  libwbclient0   2:4.8.5+dfsg-1
ii  lsb-base   9.20170808

Versions of packages freeradius recommends:
ii  freeradius-utils  3.0.16+dfsg-4.1+b1

Versions of packages freeradius suggests:
pn  freeradius-krb5
pn  freeradius-ldap
pn  freeradius-mysql   
ih  freeradius-postgresql  3.0.16+dfsg-4.1+b1
ih  freeradius-python2 3.0.16+dfsg-4.1+b1
pn  snmp   

-- no debconf information


$ strace freeradius -X
...
openat(AT_FDCWD, "/usr/lib/freeradius/rlm_dhcp.so", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\340\21\0\0\0\0\0\0"..., 
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=14344, ...}) = 0
mmap(NULL, 16568, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f0fa9a27000
mmap(0x7f0fa9a28000, 4096, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1000) = 0x7f0fa9a28000
mmap(0x7f0fa9a29000, 4096, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x2000) = 0x7f0fa9a29000
mmap(0x7f0fa9a2a000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x2000) = 0x7f0fa9a2a000
close(3)= 0
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=32946, ...}) = 0
mmap(NULL, 32946, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f0fa9a1e000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, 
"/lib/x86_64-linux-gnu/tls/x86_64/x86_64/libfreeradius-dhcp.so", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/lib/x86_64-linux-gnu/tls/x86_64/x86_64", 0x7ffc7f541670) = -1 ENOENT (No 
such file or directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/tls/x86_64/libfreeradius-dhcp.so", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/lib/x86_64-linux-gnu/tls/x86_64", 0x7ffc7f541670) = -1 ENOENT (No such 
file or directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/tls/x86_64/libfreeradius-dhcp.so", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/lib/x86_64-linux-gnu/tls/x86_64", 0x7ffc7f541670) = -1 ENOENT (No such 
file or directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/tls/libfreeradius-dhcp.so", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/lib/x86_64-linux-gnu/tls", 0x7ffc7f541670) = 

Processed: bug 916415 is forwarded to https://github.com/Feh/nocache/issues/34

[Debian Bug Tracking System]

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

> forwarded 916415 https://github.com/Feh/nocache/issues/34
Bug #916415 [libc6,nocache] nocache broken with glibc 2.28: several programs 
just hang in call to futex(..., FUTEX_WAIT_PRIVATE, 2, NULL)
Ignoring request to change the forwarded-to-address of bug#916415 to the same 
value
> thanks
Stopping processing here.

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

Processed: tagging 915765

[Debian Bug Tracking System]

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

> tags 915765 + confirmed pending
Bug #915765 [src:pystaticconfiguration] pystaticconfiguration FTBFS: test error
Added tag(s) confirmed and pending.
> thanks
Stopping processing here.

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

Bug#916424: rust-crossbeam-channel: Incomplete debian/copyright?

[Chris Lamb]

Source: rust-crossbeam-channel
Version: 0.3.2-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Sylvestre Ledru , 
ftpmas...@debian.org

Hi,

I just ACCEPTed rust-crossbeam-channel from NEW but noticed it was 
missing attribution in debian/copyright for at least Dmitry Vyukov.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.


Regards,

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

Processed: retitle 916375 apache2: Segmentation fault when mod_perl.so is enabled

[Debian Bug Tracking System]

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

> retitle 916375 apache2: Segmentation fault when mod_perl.so is enabled
Bug #916375 [apache2] apache2: Segmentation fault when mod_perl.so is loaded
Changed Bug title to 'apache2: Segmentation fault when mod_perl.so is enabled' 
from 'apache2: Segmentation fault when mod_perl.so is loaded'.
>
End of message, stopping processing here.

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

Bug#905254: Status of libphp-phpmailer

[Chris Lamb]

Chris Lamb wrote:

> Vincent Danjean wrote:
> 
> >   However, the git does not seem to have been moved to salsa.
> 
> I fixed a number of CVEs recently and I would love to push my changes
> to suitable branches. Can the PEAR maintainers please migrate this
> repo ASAP?

Any update on getting this into Git...?


Regards,

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