Bug#911813: use ptrdiff_t as the type of size instead of int

[Mo Zhou]

Package: libdsfmt-dev
Version: 2.2.3+dfsg-3
Severity: important

https://salsa.debian.org/julia-team/julia/blob/master/deps/patches/dSFMT.c.patch
https://salsa.debian.org/julia-team/julia/blob/master/deps/patches/dSFMT.h.patch

This change is similar to changes about BLAS's 64-bit-index version.
However, I doubt whether there is only Julia using this package.
If so, it's much easier for us to directly bump API and ABI.


Reverse Build-depends in main:
--

julia

Found a total of 1 reverse build-depend(s) for libdsfmt-dev.

Reverse Build-depends in contrib:
--

No reverse build-depends found for libdsfmt-dev.

Reverse Build-depends in non-free:
--

No reverse build-depends found for libdsfmt-dev.

Reverse Build-depends in main:
--

julia

Found a total of 1 reverse build-depend(s) for libdsfmt-dev.

Reverse Build-depends in contrib:
--

No reverse build-depends found for libdsfmt-dev.

Reverse Build-depends in non-free:
--

No reverse build-depends found for libdsfmt-dev.

Bug#911812: RM: src:ruby-grpc -- ROM; obsolete, src:grpc now builds ruby-grpc

[Pirate Praveen]

Package: ftp.debian.org
Severity: normal

src:grpc now builds ruby-grpc and hence
src:ruby-grpc is no longer required.





signature.asc
Description: OpenPGP digital signature

Bug#911811: RM: src:ruby-google-protobuf -- ROM; obsolete, src:protobuf now builds ruby-google-protobuf

[Pirate Praveen]

Package: ftp.debian.org
Severity: normal

src:protobuf now builds ruby-google-protobuf and hence
src:ruby-google-protobuf is no longer required.



signature.asc
Description: OpenPGP digital signature

Bug#911810: debian-installer: cannot boot installed on EFI with single xfs root

[Yangfl]

Package: debian-installer
Severity: important

I found with the lastest weekly iso (found in
debian-cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-netinst.iso)
installing with xfs+uefi lead to a non-bootable system due to grub not
being able to find the xfs module, without any notice or warning
during setup. I've confirmed it on KVM+OVMF / Hyper-V gen 2.

Step to reproduce:

 1. setup VM with EFI enabled
 2. when partitioning, use xfs as root (/) fs, no /boot, and a EFI system
partition (if you omit EFI system partition, setup won't let you continue)
 3. finish installation, not bootable, only a plain GRUB prompt
 4. grub> insmod xfs
error: file '/boot/grub/x86_64-efi/xfs.mod' not found.
grub> set root=(hd0,`Tab`
Possible partitions are:

  Partition hd0,gpt1: Filesystem type fat, UUID x
  Partition hd0,gpt2: No known filesystem detected

It doesn't happen with a separate /boot partition (in ext4) present.

Bug#911809: ITP: r-cran-ini -- Read and Write '.ini' Files

[Dylan Aïssi]

Package: wnpp
Owner: Dylan Aïssi 
Severity: wishlist

* Package name: r-cran-ini
  Version : 0.3.1
  Upstream Author : David Valentim Dias
* URL : https://cran.r-project.org/package=ini
* License : GPL-3
  Programming Lang: GNU R
  Description : Read and Write '.ini' Files
 Parse simple '.ini' configuration files to an structured list. Users
 can manipulate this resulting list with lapply() functions. This same
 structured list can be used to write back to file after modifications.

Remark: This package is maintained by Debian R Packages Maintainers at
   https://salsa.debian.org/r-pkg-team/r-cran-ini

Bug#911808: /sbin/iptables: no such file or directory

[Jason Woofenden]

Package: docker.io
Version: 18.06.1+dfsg1-2
Severity: important

Dear Maintainer,

When I run docker with -p it fails with:

docker: Error response from daemon: driver failed programming external 
connectivity on endpoint :  (iptables failed: iptables --wait -t nat -A 
DOCKER -p tcp -d 0/0 --dport *** -j DNAT --to-destination ***:*** ! -i docker0: 
 (fork/exec /sbin/iptables: no such file or directory)).

There's currently no debian package shipping /sbin/iptables:

https://packages.debian.org/search?suite=sid=amd64=exactfilename=contents=%2Fsbin%2Fiptables

The iptables package has recent changes to its alternatives. Maybe
it removed /sbin/iptables accidentally, but even if that is the
case, docker.io should probably search PATH or use
/usr/sbin/iptables

There's a recent bug against iptables about ferm breaking with a
similar error message:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911777


Please let me know if this is not as easy to reproduce as I think.

-- 
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 docker.io depends on:
ii  adduser 3.118
ii  iptables1.8.1-1
ii  libc6   2.27-6
ii  libdevmapper1.02.1  2:1.02.145-4.1
ii  libltdl72.4.6-6
ii  libnspr42:4.20-1
ii  libnss3 2:3.39-1
ii  libseccomp2 2.3.3-3
ii  libsystemd0 239-10
ii  lsb-base9.20170808
ii  runc1.0.0~rc5+dfsg1-4
ii  tini0.18.0-1

Versions of packages docker.io recommends:
ii  ca-certificates  20180409
ii  cgroupfs-mount   1.4
ii  git  1:2.19.1-1
pn  needrestart  
ii  xz-utils 5.2.2-1.3

Versions of packages docker.io suggests:
ii  aufs-tools   1:4.9+20170918-2
pn  btrfs-progs  
pn  debootstrap  
pn  docker-doc   
ii  e2fsprogs1.44.4-2
pn  rinse
pn  xfsprogs 
pn  zfs-fuse | zfsutils  

-- no debconf information

Bug#911807: ITP: rover -- text-based light-weight frontend for update-alternatives

[Mo Zhou]

Package: wnpp
Severity: wishlist

* Package name: rover
  Version : 0.1
  Upstream Author : myself
* URL : https://salsa.debian.org/debian/rover
* License : GPL-3+
  Programming Lang: Python
  Description : text-based light-weight frontend for update-alternatives


Rover is a text-based light-weight frontend for update-alternatives, built on
top of termbox.  It was inspired by the ranger file browser. There are several
similar works that provides graphical frontend to update-alternatives:
galternatives and kalternatives. However, Rover still have some advantages
compared to these implementations:
.
1. User doesn't need to move hand off the keyboard.
2. Extremely light weight implementation with zero GUI overhead.
3. Support search by substring and Python regex.
4. Not bound to X service. Usable under tty.
5. Much easier to maintain as a native package due to short code.

Bug#911806: Please provide a way to opt out of AppArmor confinement when running tests

[Michael Biebl]

Source: debci
Severity: wishlist

Hi,

atm, debci runs on stable, i.e. AppArmor is not active by default.
Once buster is released, this is likely going to change.

autopktest with lxc as backend and AppArmor confinement enabled is
problematic atm, at least for certain packages.
E.g. if I try to run autopkgtest for systemd on sid in a AA-confined LXC
container, it explodes left and right, whereas it passes with
AA-confinement turned off.

It is my understanding, that Ubuntu itself turns off AA-confinement in
their LXC based CI or at least ship a AA policy which is much less
strict [1].

Looking ahead at the buster release, we either need to turn off AA
confinement in our Debian CI as well, ship a custom AA policy or provide
a way for individual packages to opt out of AA confinement. In the
latter case, this will probably need some changes to autopkgtest as
well.

Would welcome your input on this.

Regards,
Michael


[1] https://github.com/systemd/systemd/issues/10166#issuecomment-428523883

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

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

Bug#801727: pugixml: Please package pugixml variant with wchar enabled

[Bill Blough]

block 801727 by 911805
thanks

I looked at this a little back when we discussed it, but it looked like
it was going to take more time than I had right then, so I put it off.

I recently had time to dig into this properly, but have hit a snag.

After several hours of testing and tweaking, and reading cdbs files,
it appears that the multiple builds work under autotools, but not under
cmake.

I've opened  #911805 against cdbs requesting that this functionality be
added for cmake.  I think that rabbit hole is a little too deep for me
to go down myself right now.

Bug#910394: sqlcipher: Crashes on running any SQL Statement (with a key)

[Mark Eichin]

Freshly installed to test this:

i-meant-that$ dpkg --status sqlcipher|grep Version
Version: 3.2.0-2
i-meant-that$ sqlcipher mydata.db
SQLCipher version 3.8.6 2014-08-15 11:46:33
Enter ".help" for instructions
Enter SQL statements terminated with a ";"
sqlite> pragma key = 'passphrase';
sqlite> create table memos(text, priority INTEGER);
Segmentation fault

ie. one line from https://www.zetetic.net/sqlcipher/sqlcipher-api/ about
actually setting a key, plus the first line of the man page example.

(Bonus points for maybe adding any mention at all of "pragma key" to the man 
page :-)

i-meant-that$ gdb --quiet -ex run --args sqlcipher mydata.db
SQLCipher version 3.8.6 2014-08-15 11:46:33
sqlite> pragma key = 'passphrase';
sqlite> create table memos(text, priority INTEGER);

Program received signal SIGSEGV, Segmentation fault.
0x76fc195f in EVP_EncryptUpdate () from 
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1
(gdb) where
#0  0x76fc195f in EVP_EncryptUpdate () from 
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1
#1  0x77b22e3b in sqlcipher_openssl_cipher (ctx=0x5579c238, 
mode=, key=0x5579c258 
"\352U\243\236\375\266\026\037\242\247\370\232\215\323\063O\362-w\367\223c\242ɑ^W_]\254#)",
key_sz=, iv=0x55797f98 
"+\372\032\331\003O\271\246\201>\210\210\360\375W\034\253p\227\303\315\331Y\210@\252\233\\\212<\032y\177\334\330\030\231\213F\177.\365\032\222\360\063\361\067q",
in=0x5579d1b8 "\004", in_sz=960, out=0x55797bd8 "") at 
sqlite3.c:16517
#2  0x77b3347e in sqlcipher_page_cipher (ctx=ctx@entry=0x55797b38, 
for_ctx=, pgno=1, mode=1, page_sz=, 
in=0x5579d1b8 "\004", out=0x55797bd8 "") at sqlite3.c:15696
#3  0x77b45104 in sqlite3Codec (iCtx=0x55797b38, 
data=0x5579d1a8, pgno=1, mode=6) at sqlite3.c:14389
#4  0x77b53799 in pager_write_pagelist 
(pPager=pPager@entry=0x55785a78, pList=0x5579d5e0) at sqlite3.c:48086
#5  0x77b5b5fa in sqlite3PagerCommitPhaseOne (pPager=0x55785a78, 
zMaster=zMaster@entry=0x0, noSync=noSync@entry=0) at sqlite3.c:50033
#6  0x77b5b7cf in sqlite3PagerCommitPhaseOne (noSync=0, zMaster=0x0, 
pPager=) at sqlite3.c:49932
#7  sqlite3BtreeCommitPhaseOne (p=0x55785558, zMaster=zMaster@entry=0x0) at 
sqlite3.c:57764
#8  0x77b5f421 in sqlite3BtreeCommitPhaseOne (zMaster=0x0, p=) at sqlite3.c:89551
#9  vdbeCommit (p=0x5579cb48, db=0x5576ec58) at sqlite3.c:1586
#10 sqlite3VdbeHalt (p=p@entry=0x5579cb48) at sqlite3.c:1993
#11 0x77b8e926 in sqlite3VdbeExec (p=p@entry=0x5579cb48) at 
sqlite3.c:71867
#12 0x77b8f8cf in sqlite3Step (p=0x5579cb48) at sqlite3.c:69631
#13 sqlite3_step (pStmt=) at sqlite3.c:4161
#14 0xa9d3 in shell_exec (db=0x5576ec58, zSql=0x5576ebc0 
"create table memos(text, priority INTEGER);", pArg=0x7fffd2d0, 
pzErrMsg=0x7fffd138, xCallback=0x9a90 )
at ./src/shell.c:1360
#15 0xbbdf in process_input (p=0x7fffd2d0, in=0x0) at 
./src/shell.c:3613
#16 0x7406 in main (argc=, argv=) at 
./src/shell.c:4129

Bug#911733: libfiu: FTBFS on 32-bit architectures?

[Chris Lamb]

tags 911733 + pending patch
thanks

Hi Alberto,

I think this is what we need:

  
https://salsa.debian.org/lamby/pkg-libfiu/commit/f80fb7ab3a96fe206e8610fc1f01dd1b370f206e

  ...e-return-offset-size-for-64-bit-variants-to.patch | 20 
  debian/patches/series|  1 +
  2 files changed, 21 insertions(+)


Regards,

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

Bug#911805: Please support "multiple flavors" for cmake builds

[William Blough]

Package: cdbs
Version: 0.4.158
Severity: wishlist


Based on my research and testing, it appears that the "multiple flavors"
capability that cdbs provides for autotools-based builds does not work
for cmake-based builds.

Please consider adding this for cmake builds.

Thanks!


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

Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C), 
LANGUAGE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

cdbs depends on no packages.

Versions of packages cdbs recommends:
ii  autotools-dev  20180224.1

Versions of packages cdbs suggests:
pn  devscripts  

-- no debconf information

Bug#911804: wit: please make the build reproducible

[Chris Lamb]

Source: wit
Version: 3.01a-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], we noticed
that wit could not be built reproducibly.

This because the binaries and the load-titles.sh scripts (etc.)
embedded the build path.

Patch attached. It's a bit complicated due to some weirdness in
the upstream Makefile; hopefully should be documented enough.

  [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/rules  2018-10-24 20:59:49.437323011 -0400
--- b/debian/rules  2018-10-24 22:28:23.278956670 -0400
@@ -31,13 +31,18 @@
 override_dh_auto_test:
 
 override_dh_auto_build:
-   $(MAKE) INSTALL_PATH=$(CURDIR)/debian/wit/usr HAVE_ZLIB=1
-   $(MAKE) INSTALL_PATH=$(CURDIR)/debian/wit/usr doc
+   # Build targetting /usr...
+   $(MAKE) INSTALL_PATH=/usr HAVE_ZLIB=1
+   $(MAKE) INSTALL_PATH=/usr doc
 
 override_dh_auto_install:
+   # ... and then recreate install.sh with a new INSTALL_PATH
+   rm -f templates.sed
mkdir -p $(CURDIR)/debian/wit/usr/bin
mkdir -p $(CURDIR)/debian/wit/usr/share
-   $(MAKE) INSTALL_PATH=$(CURDIR)/debian/wit/usr install
+   $(MAKE) install.sh INSTALL_PATH=$(CURDIR)/debian/wit/usr
+   # Manually call ./install.sh to avoid rebuilding
+   ./install.sh --make
 
 override_dh_installchangelogs:
dh_installchangelogs doc/HISTORY.txt

Bug#911698: ITS: tbb

[Mo Zhou]

On Tue, Oct 23, 2018 at 08:42:31PM +0100, Steven Capper wrote:
> Hi Mo,
> I maintain the package and we had it hosted on Debian Science. I would
> like to keep maintaining the package, but I am happy to co-maintain
> the package with others.

Thank you for the quick reply. I'm happy to co-maintain this package
since it's one of the dependencies of src:intel-mkl. If the one
contacted me decided to contribute to this package, I'll help him/her
by sponsoring / team uploading.
 
> Out of interest, what would you like doing with the package? Would you
> like the version updating?

Yes, the package looks somewhat old.

Bug#911803: RFP: golang-gopkg-clog.v1-dev -- channel-based logging package for Go

[Jeff Cliff]

Package: wnpp
Severity: wishlist

* Package name: golang-gopkg-clog.v1-dev
  Version : 1.2
  Upstream Author : 无闻 
* URL : https://notabug.org/makenotabuggreatagain/clog
* License : Apache-2.0
  Programming Lang: go
  Description : channel-based logging package for Go

This package supports multiple logger adapters across different levels of 
logging.  It uses Go's native channel feature to provide goroutine-safe 
mechanism 
on large concurrency.

It is a vendored dependency of gogs ( #911419 )

Bug#586709: Think I found the problem

[Jesse Smith]

I believe I found the problem here, after much poking around. Turns out
the issue does not appear to be in the halt source code, but in the
/etc/init.d/halt file.

The /etc/init.d/halt file does some checking to see what the contents of
the /etc/default/halt file is (halt or poweroff). If it's the standard
"poweroff" then /etc/initd/halt behaves properly, setting the necessary
flags to kill the power.

However, when /etc/init.d/halt is set to "halt" then the
/etc/init.d/halt script does not handle this properly. Or, more
specifically, it looks like the script does not correctly figure out
whether the user has passed in any of our own special parameters.

This might be easier with some examples. When /etc/default/halt is set
to "halt" then here is how the /etc/init.d/halt script works:

1. Running plain "halt" results in "halt" being called and we get the
correct behaviour. The system stops, but does not power off.

2. Running "halt -p" results in "halt" being called as just "halt". The
user's special "-p" flag is not appended to the command. The halt
command stops the system, but does not power off.

I believe the solution here is to update /etc/init.d/halt and have it
call the "halt" command with any parameters the user specifies, appended
to the command line. Otherwise it only reads the default value and
ignores command line parameters.

I manually modified my copy of the script to put "-p" on the end of
"halt", regardless of the default, and it correctly shutdown the system
and powered off. So the issue here seems to be the script not passing
user parameters rather than an issue with the halt.c code.

Though I'm open to ways we can better manage parameters to make
writing/updating the halt init.d script easier.

- Jesse (upstream dev)

Bug#911802: ITP: kovri -- C++ I2P router

[Ben Hutchings]

On Wed, 2018-10-24 at 17:54 -0700, oneiric wrote:
[...]
> I plan to create a Kovri package for Debian. Building Kovri on Debian
> will involve statically building and linking against the most recent
> Boost and OpenSSL libraries.
[...]

You will need to have a very good reason to do this.  It is recommended
to use shared libraries in Debian packages where possible.

Ben.

-- 
Ben Hutchings
The obvious mathematical breakthrough [to break modern encryption]
would be development of an easy way to factor large prime numbers.
   - Bill Gates




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

Bug#911802: ITP: kovri -- C++ I2P router

[oneiric]

Package: wnpp
Severity: wishlist

Dear Maintainer,

Adding Kovri to the Debian ecosystem would provide users a lightweight
entry into the I2P network.

Kovri is a C++ implementation of an I2P router. I2P is an overlay
network, providing users with secure, private access to a number of
services.

I plan to create a Kovri package for Debian. Building Kovri on Debian
will involve statically building and linking against the most recent
Boost and OpenSSL libraries.

The package will be built from source against release tags.
Updates to the package will mirror project releases.

Kovri is licensed under the BSD-3 license.

Currently, Kovri is in alpha-release. 
Nightly release downloads will soon be available from the project's GitLab:
https://gitlab.com/kovri-project/kovri

Thank you for your time considering this package proposal.

- oneiric

Bug#586709: Can confirm this bug

[Jesse Smith]

I can confirm this bug exists in SysV init 2.91. Have not found the
cause yet. At first I thought it might be a matter of shutdown and halt
using different methods to cut power (ie maybe halt was trying to
poweroff but couldn't do to a compatibility problem). But I have
confirmed on my own machine that

1. halt's default behaviour is to poweroff (good)
2. switch halt's default to "halt" causes it to halt without powering
off (also good)
3. halt -p does not power off, it just halts (bad)

So I know halt _can_ poweroff the computer, it just is not for some
reason. I suspect there is something that is cancelling out the -p flag
late in the code, but haven't found it yet.

- Jesse (upstream dev)

Bug#783781: apt-show-versions: shows "foo:all not installed" for packages that transitioned from arch any to arch all

[Paul Wise]

On Wed, 2018-10-24 at 11:42 -0400, Antoine Beaupré wrote:

> But it's not clear to me what the proper solution is or what the purpose
> of this 'not installed' statement is... That code has been present
> basically forever (since the 2007, 0.10 original git import) without any
> clear explanation.

snapshot goes back to 0.03 and the code is slightly different there but
there is also a not installed statement.

https://snapshot.debian.org/package/apt-show-versions/

BTW Christoph, when this package moves to salsa it would be nice to
import those versions so people could use grafts to view the history.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#911777: iptables: iptables-persistent broken by changed path of iptables-restore

[Jon DeVree]

The iptables-persistent package was also broken by this change.

-- 
Jon
Doge Wrangler
X(7): A program for managing terminal windows. See also screen(1) and tmux(1).

Bug#827337: apt-show-versions: option to hide packages that are at the right version based on pinning upgradeable

[Paul Wise]

On Wed, 2018-10-24 at 12:05 -0400, Antoine Beaupré wrote:

> What *is* the proper way of figuring out what the default release is?
> Or should we have a --ignore flag that would ignore a certain suite?

APT developers: we could use your help on this bug report:

https://bugs.debian.org/827337

Using the APT Perl libraries, what is the right way to determine if the
currently installed version of a package matches the default release
and pinning setup configured by the system or if the installed version
was manually updated to a non-default release?

I guess this is pretty complicated, since different pinning value
ranges have different meanings and this should affect the results.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#911801: pacemaker: Cannot complete pcs cluster setup command, returns error HTTP401

[Duncan Hare]

Package: pacemaker
Version: 1.1.16-1
Severity: grave
Justification: causes non-serious data loss



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

Kernel: Linux 4.9.0-8-amd64 (SMP w/1 CPU core)
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 pacemaker depends on:
ii  corosync   2.4.2-3+deb9u1
ii  dbus   1.10.26-0+deb9u1
ii  init-system-helpers1.48
ii  libc6  2.24-11+deb9u3
ii  libcfg62.4.2-3+deb9u1
ii  libcib41.1.16-1
ii  libcmap4   2.4.2-3+deb9u1
ii  libcorosync-common42.4.2-3+deb9u1
ii  libcpg42.4.2-3+deb9u1
ii  libcrmcluster4 1.1.16-1
ii  libcrmcommon3  1.1.16-1
ii  libcrmservice3 1.1.16-1
ii  libglib2.0-0   2.50.3-2
ii  libgnutls303.5.8-5+deb9u3
ii  liblrmd1   1.1.16-1
ii  libpam0g   1.1.8-3.6
ii  libpe-rules2   1.1.16-1
ii  libpe-status10 1.1.16-1
ii  libpengine10   1.1.16-1
ii  libqb0 1.0.1-1
ii  libquorum5 2.4.2-3+deb9u1
ii  libstonithd2   1.1.16-1
ii  libtransitioner2   1.1.16-1
ii  lsb-base   9.20161125
ii  pacemaker-common   1.1.16-1
ii  pacemaker-resource-agents  1.1.16-1
ii  perl   5.24.1-3+deb9u4

Versions of packages pacemaker recommends:
ii  fence-agents 4.0.25-1
ii  pacemaker-cli-utils  1.1.16-1

Versions of packages pacemaker suggests:
ii  cluster-glue  1.0.12-5
ii  pcs   0.9.155+dfsg-2+deb9u1


Running: /usr/bin/ruby -I/usr/share/pcsd/ /usr/share/pcsd/pcsd-cli.rb auth
--Debug Input Start--
{"username": "hacluster", "local": false, "nodes": ["greene", "pinke"], 
"password": "Cl3nt4n@@", "force": true}
--Debug Input End--
Return Value: 0
--Debug Output Start--
{
  "status": "ok",
  "data": {
"auth_responses": {
  "pinke": {
"status": "ok",
"token": "c4dca519-18ab-4ca9-b218-af6e03b3731d"
  },
  "greene": {
"status": "ok",
"token": "d0ea589d-0a05-40d8-a366-82b40d557465"
  }
},
"sync_successful": true,
"sync_nodes_err": [

],
"sync_responses": {
}
  },
  "log": [
"I, [2018-10-24T17:03:01.093531 #7491]  INFO -- : PCSD Debugging enabled\n",
"D, [2018-10-24T17:03:01.093652 #7491] DEBUG -- : Did not detect RHEL 6\n",
"I, [2018-10-24T17:03:01.093733 #7491]  INFO -- : Running: 
/usr/sbin/corosync-cmapctl totem.cluster_name\n",
"I, [2018-10-24T17:03:01.093816 #7491]  INFO -- : CIB USER: hacluster, 
groups: \n",
"D, [2018-10-24T17:03:01.134130 #7491] DEBUG -- : [\"totem.cluster_name 
(str) = debian\\n\"]\n",
"D, [2018-10-24T17:03:01.134912 #7491] DEBUG -- : []\n",
"D, [2018-10-24T17:03:01.135169 #7491] DEBUG -- : Duration: 0.040189124s\n",
"I, [2018-10-24T17:03:01.135618 #7491]  INFO -- : Return Value: 0\n",
"I, [2018-10-24T17:03:01.430297 #7491]  INFO -- : Running: /usr/sbin/pcs 
status nodes corosync\n",
"I, [2018-10-24T17:03:01.430644 #7491]  INFO -- : CIB USER: hacluster, 
groups: \n",
"D, [2018-10-24T17:03:03.173921 #7491] DEBUG -- : [\"Corosync Nodes:\\n\", 
\" Online:\\n\", \" Offline:\\n\"]\n",
"D, [2018-10-24T17:03:03.174581 #7491] DEBUG -- : []\n",
"D, [2018-10-24T17:03:03.174852 #7491] DEBUG -- : Duration: 1.743259319s\n",
"I, [2018-10-24T17:03:03.175252 #7491]  INFO -- : Return Value: 0\n",
"I, [2018-10-24T17:03:03.184745 #7491]  INFO -- : Sending config 'tokens' 
version 1 baa843266738f0107221006d0e7dfd43ba74c73b to nodes: \n"
  ]
}
--Debug Output End--


Running: /usr/sbin/corosync -v

Finished running: /usr/sbin/corosync -v
Return value: 0
--Debug Stdout Start--
Corosync Cluster Engine, version '2.4.2'
Copyright (c) 2006-2009 Red Hat, Inc.

--Debug Stdout End--
--Debug Stderr Start--

--Debug Stderr End--

Destroying cluster on nodes: pinke, greene...
Running: /usr/bin/ruby -I/usr/share/pcsd/ /usr/share/pcsd/pcsd-cli.rb 
read_tokens
--Debug Input Start--
{}
--Debug Input End--
Running: /usr/bin/ruby -I/usr/share/pcsd/ /usr/share/pcsd/pcsd-cli.rb 
read_tokens
--Debug Input Start--
{}
--Debug Input End--
Return Value: 0
--Debug Output Start--
{
  "status": "ok",
  "data": {
  },
  "log": [
"I, [2018-10-24T17:03:36.610130 #7562]  INFO -- : PCSD Debugging enabled\n",
"D, [2018-10-24T17:03:36.610225 #7562] DEBUG -- : Did not detect RHEL 6\n",
"I, [2018-10-24T17:03:36.610297 #7562]  INFO -- : Running: 
/usr/sbin/corosync-cmapctl totem.cluster_name\n",
"I, [2018-10-24T17:03:36.610391 #7562]  INFO -- : CIB USER: hacluster, 
groups: \n",
"D, [2018-10-24T17:03:36.793991 #7562] DEBUG -- : 

Bug#749991: A tiresome subject for YEARS.

[Ben Hutchings]

On Wed, 2018-10-24 at 18:44 +0200, John Paul Adrian Glaubitz wrote:
> On 10/24/18 6:42 PM, Oliver Riesener wrote:
> > No unetbootin, it’s the stock  stretch netboot   installation.
> > initrd kernel from actual Debian9.5/…./amd64/netboot/netboot.tar.gz
> > didn’t find kernel modules anymore. The old one before too. 
> > It’s a point release problem. Older versions of modules (.udeb ?) seems
> > to be from debian repo. 
> Are you sure you used a matching kernel image and initrd? Both have to match
> their version otherwise it won't work.

But when you use netboot the udebs in the archive *also* have to match.
And they don't after a point release.

Ben.

> I'm creating debian-installer images myself on a regular basis and from my
> current knowledge and testing, it's very unlikely that there is a bug in
> the kernel and initrd matching.

-- 
Ben Hutchings
The obvious mathematical breakthrough [to break modern encryption]
would be development of an easy way to factor large prime numbers.
   - Bill Gates




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

Bug#911791: drupal7: DATE_RFC7231 already defined in PHP 7.0.19 and 7.1.5

[Bill Blough]

Will do.  Thanks.

Bug#911777: iptables: ferm broken by changed path of iptables-restore

[Cesare Leonardi]

Dear iptables maintainers, reading the initial bug report you can think 
I haven't read README.Debian before filing this bug, but I did. It's 
clear that now iptables is handled by update-alternatives, so that the 
user can choose between the new nftables compatible programs (the 
dafault) or the legacy programs. That's great!
And you have also documented the changed path of the binaries, from 
/sbin to /usr/sbin/.


The point is: existing packages, like ferm, that search for the previous 
full paths, are now broken. Since iptables-nft-save/iptables-nft-restore 
should be compatible with the legacy iptables-save/iptables-restore, why 
not render the old paths a symlink to /etc/alternatives/?

For example:
/sbin/iptables -> /etc/alternatives/iptables
/sbin/iptables-restore -> /etc/alternatives/iptables-restore
/sbin/iptables-save -> /etc/alternatives/iptables-save

In the ferm case, it suffice to create the following two symlinks, to 
make it start again:

ln -s /etc/alternatives/iptables-restore /sbin/iptables-restore
ln -s /etc/alternatives/ip6tables-restore /sbin/ip6tables-restore
With alternatives left with the current default:
/etc/alternatives/iptables-restore -> /usr/sbin/iptables-nft-restore
/etc/alternatives/ip6tables-restore -> /usr/sbin/ip6tables-nft-restore

Cesare.

Bug#911800: cabal-install: depend on or recommend curl/wget for HTTPS support?

[Colin Watson]

Package: cabal-install
Version: 2.0.0.1-1
Severity: wishlist

Since version 1.24.0.0, cabal-install can use curl or wget for HTTPS
support, if installed; but there's no indication of this in its package
relationships.

Would it be worth depending on or at least recommending curl | wget, to
clue users into the fact that cabal-install works better with them?  I
think at least Recommends for HTTPS support would be justified on the
modern internet.

Thanks,

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

Bug#911798: /usr/sbin/rsyslogd: Upgrade in 2018-06 caused rsyslogd to not log to auth.log and other files

[Michael Biebl]

Control: tags -1 moreinfo

Am 24.10.18 um 23:00 schrieb Jeffrey:
> We found a number of Debian 9 servers that stopped logging after OS updates 
> in 2018-06. If my memory serves me (and it probably doesn't), it would appear 
> that syslog was removed but rsyslog wasn't installed as a replacement. When 
> we installed rsyslog there was an error in the file
> /etc/rsyslogs/named.conf
> 
> I don't understand what the error is. We didn't create the file manually, it 
> was a part of a Debian package at some point.

Are you sure?
I don't find any package in the archive which ships that file
"apt-file search /etc/rsyslog.d/named.conf" doesn't give me any hits.

What I can say for sure is that this file was not shipped by the rsyslog
package, so there is nothing the rsyslog package can do about this issue.

Can you run
dpkg -S /etc/rsyslog.d/named.conf

If that turns up a debian package, we can re-assign the bug report.

Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#908847: llvm-toolchain-6.0: FTBFS on hurd-i386

[Samuel Thibault]

Hello,

There was an issue with paths returned by llvm-config, discussed
upstream on https://reviews.llvm.org/D53557 , I'd like to NMU the fix
commited upstream attached here, may I proceed?

Samuel
[hurd] Make getMainExecutable get the real binary path

On GNU/Hurd, llvm-config is returning bogus value, such as:

$ llvm-config-6.0 --includedir
/usr/include

while it should be:
$ llvm-config-6.0 --includedir
/usr/lib/llvm-6.0/include

This is because getMainExecutable does not get the actual installation
path. On GNU/Hurd, /proc/self/exe is indeed a symlink to the path that
was used to start the program, and not the eventual binary file. Llvm's
getMainExecutable thus needs to run realpath over it to get the actual
place where llvm was installed (/usr/lib/llvm-6.0/bin/llvm-config), and
not /usr/bin/llvm-config-6.0. This will not change the result on Linux,
where /proc/self/exe already points to the eventual file.

Patch by Samuel Thibault!

While making changes here, I reformatted this block a bit to reduce
indentation and match 2 space indent style.

Differential Revision: https://reviews.llvm.org/D53557

Index: llvm/trunk/lib/Support/Unix/Path.inc
===
--- llvm/trunk/lib/Support/Unix/Path.inc
+++ llvm/trunk/lib/Support/Unix/Path.inc
@@ -179,14 +179,34 @@
   char exe_path[MAXPATHLEN];
   StringRef aPath("/proc/self/exe");
   if (sys::fs::exists(aPath)) {
-  // /proc is not always mounted under Linux (chroot for example).
-  ssize_t len = readlink(aPath.str().c_str(), exe_path, sizeof(exe_path));
-  if (len >= 0)
-  return std::string(exe_path, len);
+// /proc is not always mounted under Linux (chroot for example).
+ssize_t len = readlink(aPath.str().c_str(), exe_path, sizeof(exe_path));
+if (len < 0)
+  return "";
+
+// Null terminate the string for realpath. readlink never null
+// terminates its output.
+len = std::min(len, long(sizeof(exe_path) - 1));
+exe_path[len] = '\0';
+
+// At least on GNU/Hurd, /proc/self/exe is a symlink to the path that
+// was used to start the program, and not the eventual binary file.
+// We thus needs to run realpath over it to get the actual place
+// where llvm was installed.
+#if _POSIX_VERSION >= 200112 || defined(__GLIBC__)
+char *real_path = realpath(exe_path, NULL);
+std::string ret = std::string(real_path);
+free(real_path);
+return ret;
+#else
+char real_path[MAXPATHLEN];
+realpath(exe_path, real_path);
+return std::string(real_path);
+#endif
   } else {
-  // Fall back to the classical detection.
-  if (getprogpath(exe_path, argv0))
-return exe_path;
+// Fall back to the classical detection.
+if (getprogpath(exe_path, argv0))
+  return exe_path;
   }
 #elif defined(HAVE_DLFCN_H) && defined(HAVE_DLADDR)
   // Use dladdr to get executable path if available.

Bug#911768: [pkg-gnupg-maint] Bug#911768: pinentry-gnome3 fails to open a window with 'No Gcr System Prompter available, falling back to curses'

[Daniel Kahn Gillmor]

Hi Tiziano--

On Wed 2018-10-24 17:24:33 +0200, Tiziano Zito wrote:
> pinentry-gnome3 (but also pinentry-gtk-2) does not open a window anymore to 
> ask for a passphrase. If run from terminal it shows:
>
> No Gcr System Prompter available, falling back to curses
> OK Pleased to meet you
>
> It was working fine since years. Of the packages pinentry-gnome3 depends on, 
> I have only upgraded recently libgpg-error0,  libncursesw6, libtinfo6.
> Even downgrading libgpg-error0 to 1.32-1 does not fix the issue.

hmm, looking at the installed packages:

> Versions of packages pinentry-gnome3 depends on:
> ii  gcr  3.28.0-1
> ii  libassuan0   2.5.1-2
> ii  libc62.27-6
> ii  libgcr-base-3-1  3.28.0-1
> ii  libglib2.0-0 2.58.1-2
> ii  libgpg-error01.32-3
> ii  libncursesw6 6.1+20181013-1
> ii  libsecret-1-00.18.6-3
> ii  libtinfo66.1+20181013-1
>
> Versions of packages pinentry-gnome3 recommends:
> pn  dbus-user-session  

can you try installing dbus-user-session, then log out and log back in
and let me know whether it works in that case?

Regards,

--dkg


signature.asc
Description: PGP signature

Bug#911785: dnssec-coverage complains about issues in the past

[Ondřej Surý]

Control: forwarded -1 https://gitlab.isc.org/isc-projects/bind9/issues/625

--
Ondřej Surý
ond...@sury.org



> On 24 Oct 2018, at 21:59, Peter Palfrader  wrote:
> 
> To reproduce:
> 
> 
> mkdir example.com
> cd example.com
> faketime -f '-1y'  /usr/sbin/dnssec-keygen -f KSK -K . -a RSASHA256 -3 -b 
> 2048 example.com
> 
> key=$(faketime -f '-1y'  /usr/sbin/dnssec-keygen -K . -a RSASHA256 -3 -b 1024 
> -I +120d -D +150d example.com)
> first=$key
> 
> lt=120
> for i in `seq 1 5`; do
>  lt=$((lt + 120))
>  key=$(faketime -f '-1y'  /usr/sbin/dnssec-keygen -K . -S "$key.key" -I 
> +${lt}d -D +$((lt+30))d example.com)
> done
> 
> /usr/sbin/dnssec-coverage -K . -l 200d -c /usr/sbin/named-compilezone 
> example.com
> rm $first.key $first.private
> /usr/sbin/dnssec-coverage -K . -l 200d -c /usr/sbin/named-compilezone 
> example.com
> 
> 
> 
> Cheers,
> -- 
>|  .''`.   ** Debian **
>  Peter Palfrader   | : :' :  The  universal
> https://www.palfrader.org/ | `. `'  Operating System
>|   `-https://www.debian.org/
> 

Bug#911799: python-libvirt: Fail to create or start virtual network interfaces after an upgrade

[Alex Volkov]

Package: python-libvirt
Version: 4.6.0-1
Severity: important

Dear Maintainer,

After a recent upgrade of libvirt packages I'm no longer able to virtual
networking for libvirt.

I've tried installing firewalld and dnsmasq to fix some of the errors
I've received when attemting to get virtual networking working again.

I have installed the following packages

ii  firewalld 0.6.3-1   
  all  dynamically managed firewall with support for network 
zones
ii  dnsmasq   2.79-1
  all  Small caching DNS proxy and DHCP/TFTP server
ii  dnsmasq-base  2.80-1
  amd64Small caching DNS proxy and DHCP/TFTP server

I also created symlink from /usr/sbin/iptables to /usr/sbin/ip4tables in
hopes to fix the problem.


I'm still getting this error when attempting to create or start a
network interface.

Error creating virtual network: COMMAND_FAILED: UNKNOWN_ERROR: 'ip4tables' 
backend does not exist

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper
callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/createnet.py", line 818, in 
_async_net_create
net.install()
  File "/usr/share/virt-manager/virtinst/network.py", line 275, in install
net.create()
  File "/usr/lib/python2.7/dist-packages/libvirt.py", line 2982, in create
if ret == -1: raise libvirtError ('virNetworkCreate() failed', net=self)
libvirtError: COMMAND_FAILED: UNKNOWN_ERROR: 'ip4tables' backend does not exist

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

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

Versions of packages python-libvirt depends on:
ii  libc6 2.27-6
ii  libvirt0  4.7.0-1+b1
ii  python2.7.15-3

Versions of packages python-libvirt recommends:
ii  libvirt-daemon  4.7.0-1+b1

python-libvirt suggests no packages.

-- no debconf information

Bug#911774: O: xview -- XView shared libraries

[Mattia Rizzolo]

On Wed, Oct 24, 2018 at 08:37:33PM +0200, Sven Joachim wrote:
> On 2018-10-24 18:17 +0200, Mattia Rizzolo wrote:
> 
> > Package: wnpp
> >
> > The current maintainer of xview, Blars Blarson ,
> > is apparently not active anymore.  Therefore, I orphan this package now.
> >
> > Maintaining a package requires time and skills. Please only adopt this
> > package if you will have enough time and attention to work on it.
> >
> > If you want to be the new maintainer, please see
> > https://www.debian.org/devel/wnpp/#howto-o for detailed
> > instructions how to adopt a package properly.
> 
> FWIW, this package should be removed rather than adopted.  It is ugly
> legacy code from the 1990's that apparently does not work at all on
> 64-bit architectures anymore.  Fortunately there do not seem to be any
> reverse dependencies.

Boyuan Yang opened the RM bug: #911787

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#911791: drupal7: DATE_RFC7231 already defined in PHP 7.0.19 and 7.1.5

[Gunnar Wolf]

William Blough dijo [Wed, Oct 24, 2018 at 03:56:56PM -0400]:
> In stable, drupal7 defines a constant (DATE_RFC7231) that conflicts with
> the same constant already defined by php7.  This happens intermittently
> depending on what code is being loaded/executed in php (the drupal
> constant is defined in bootstrap, so is always loaded).  This results in
> intermittent server errors (HTTP 500).
> 
> The upstream bug report and patch can be found at
> 
> https://www.drupal.org/project/drupal/issues/2877243
> 
> and has been applied by upstream in the 7.55 release.
> 
> It would be great if the patch for this issue could be applied in the
> next stable update.

Hi William,

Thanks for your report. Being brutally honest, I doubt I will have
time to do this - If you think you can backport the fix, I will check
and apply it. Send me a merge request in Salsa! :-]

Thanks,

Bug#911798: /usr/sbin/rsyslogd: Upgrade in 2018-06 caused rsyslogd to not log to auth.log and other files

[Jeffrey]

Package: rsyslog
Version: 8.24.0-1
Severity: important
File: /usr/sbin/rsyslogd

Hello there!

We found a number of Debian 9 servers that stopped logging after OS updates in 
2018-06. If my memory serves me (and it probably doesn't), it would appear that 
syslog was removed but rsyslog wasn't installed as a replacement. When we 
installed rsyslog there was an error in the file
/etc/rsyslogs/named.conf

I don't understand what the error is. We didn't create the file manually, it 
was a part of a Debian package at some point.

That error prevents rsyslogd from writing to auth.log and other important log 
files. There is no output to stout to say there was an issue starting or 
running.

Here's the error:
# service rsyslog status
● rsyslog.service - System Logging Service
   Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor preset: 
enabled)
   Active: active (running) since Wed 2018-10-24 15:56:51 CDT; 3s ago
 Docs: man:rsyslogd(8)
   http://www.rsyslog.com/doc/
 Main PID: 13874 (rsyslogd)
Tasks: 4 (limit: 4915)
   CGroup: /system.slice/rsyslog.service
   └─13874 /usr/sbin/rsyslogd -n

Oct 24 15:56:51 sochi systemd[1]: Starting System Logging Service...
Oct 24 15:56:51 sochi liblogging-stdlog[13874]:  [origin software="rsyslogd" 
swVersion="8.24.0" x-pid="13874" x-info="http://www.rsyslog.com;] start
Oct 24 15:56:51 sochi liblogging-stdlog[13874]: action 'logging' treated as 
':omusrmsg:logging' - please use ':omusrmsg:logging' syntax instead, 'logging' 
will not be supported in the future
Oct 24 15:56:51 sochi systemd[1]: Started System Logging Service.
Oct 24 15:56:51 sochi liblogging-stdlog[13874]: error during parsing file 
/etc/rsyslog.d/named.conf, on or before line 1: warnings occured in file 
'/etc/rsyslog.d/named.conf' around line 1 [
Oct 24 15:56:51 sochi liblogging-stdlog[13874]: error during parsing file 
/etc/rsyslog.d/named.conf, on or before line 1: syntax error on token '{' 
[v8.24.0 try http://www.rsyslog.com/e/2207
Oct 24 15:56:51 sochi liblogging-stdlog[13874]: CONFIG ERROR: could not 
interpret master config file '/etc/rsyslog.conf'. [v8.24.0 try 
http://www.rsyslog.com/e/2207 ]


Here is that named.conf file:
# cat /etc/rsyslog.d/named.conf
logging {
  channel bind_log {
file "/var/log/bind/bind.log" versions 3 size 5m;
severity info;
print-category yes;
print-severity yes;
print-time yes;
  };
  category default { bind_log; };
  category update { bind_log; };
  category update-security { bind_log; };
  category security { bind_log; };
  category queries { bind_log; };
  category lame-servers { null; };
};


By moving that file to an unexpected extension, we can restart rsyslogd and 
things are working again
mv /etc/rsyslog.d/named.conf /etc/rsyslog.d/named.conf.bak

Thanks Debian and everyone!


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

Kernel: Linux 4.9.0-7-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 rsyslog depends on:
ii  init-system-helpers  1.48
ii  libc62.24-11+deb9u3
ii  libestr0 0.1.10-2
ii  libfastjson4 0.99.4-1
ii  liblogging-stdlog0   1.0.5-2+b2
ii  liblognorm5  2.0.1-1.1+b1
ii  libsystemd0  232-25+deb9u4
ii  libuuid1 2.29.2-1+deb9u1
ii  lsb-base 9.20161125
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages rsyslog recommends:
ii  logrotate  3.11.0-0.1

Versions of packages rsyslog suggests:
pn  rsyslog-doc
pn  rsyslog-gnutls 
pn  rsyslog-gssapi 
pn  rsyslog-mongodb
pn  rsyslog-mysql | rsyslog-pgsql  
pn  rsyslog-relp   

-- no debconf information

Bug#911797: Multiple vulnerabilities

[Moritz Muehlenhoff]

Source: open-build-service
Severity: grave
Tags: security

Please verify whether these affect OBS as packaged in Debian:

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12477
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12478
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12479
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12467
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12466

Cheers,
Moritz

Bug#910397: Firefox 60.3.0esr, same problem

[Paul van der Vlis]

Firefox 60.3.0esr has the same problem. Tested with both Linkello and
meet.jit.si.

Bug#868895: xtensa toolchain(s)

[Helmut Grohne]

Hi Jonathan,

On Fri, Aug 03, 2018 at 04:46:16AM +0100, Jonathan McDowell wrote:
> I've been looking at generating binutils + gcc packages based on the
> binutils-source + gcc-7-source packages for the xtensa-lx106 target
> (ESP8266). I have something that seems to be working, and I'm
> considering uploading them, but I don't think it's possible to build a
> single toolchain that will target the ESP8266, ESP32 + ath9k Xtensa
> variants. The xtensa-lx106 binary packages are turning out at about 20M
> between them; is there enough use that it would be worth having all 3
> options present in Debian?

Let me argue that yes, that would be a good idea.

We have esptool in the archive. The esptool comes with a flasher_stub
(https://sources.debian.org/src/esptool/2.5.0+dfsg-1/flasher_stub/).
Presently it cannot be built, because the toolchain would be required
for doing so. It needs the xtensa-lx106-elf and xtensa-esp32-elf
toolchains.

The open-ath9k-htc-firmware package presently builds an xtensa toolchain
from gcc-7 sources during build
https://sources.debian.org/src/open-ath9k-htc-firmware/1.4.0-97-g75b3e59+dfsg-1/debian/cross-toolchain.mk/
using --target xtensa-elf. Having separate binary packages could
simplify the packaging of open-ath9k-htc-firmware.

Maybe the ath9k toolchain is less relevant as most users will be using
open-ath9k-htc-firmware or firmware-atheros. Those that need can quite
easily produce the toolchain from the open-ath9k-htc-firmware source
package. But given the rising popcon of esptool (~200 now), toolchains
for ESP8266 and ESP32 seem sensible to me.

Note that any practical use will also need esp-idf. In particular, the
flasher_stub from esptool needs esp-idf. Do you have any plans for
packaging esp-idf?

Also moving to gcc-8-source seems in order.

Helmut

Bug#911795: CVE-2018-17846 / CVE-2018-17847 / CVE-2018-17848

[Martín Ferrari]

On 24/10/18 22:17, Moritz Muehlenhoff wrote:
> Source: golang-golang-x-net-dev
> Severity: important
> Tags: security
> 
> Please see
> http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-17846
> http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-17847
> http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-17848
> 

Thanks for the heads up!

Sadly, it seems it has not yet been fixed upstream.

-- 
Martín Ferrari (Tincho)

Bug#911796: CVE-2018-14642

[Moritz Muehlenhoff]

Source: undertow
Severity: important
Tags: security

Limited details so far:
https://bugzilla.redhat.com/show_bug.cgi?id=1628702

Cheers,
Moritz

Bug#911795: CVE-2018-17846 / CVE-2018-17847 / CVE-2018-17848

[Moritz Muehlenhoff]

Source: golang-golang-x-net-dev
Severity: important
Tags: security

Please see
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-17846
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-17847
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-17848

Bug#911792: sdlgfx: autopkgtest regression: seems to run same test over and over again

[Manuel A. Fernandez Montecelo]

Hi,

Em qua, 24 de out de 2018 às 22:03, Paul Gevers  escreveu:
>
> Source: sdlgfx
> Version: 2.0.25-10
> X-Debbugs-CC: debian...@lists.debian.org
> User: debian...@lists.debian.org
> Usertags: regression
>
> Dear maintainers,
>
> With a recent upload of sdlgfx the autopkgtest of sdlgfx fails in
> testing when that autopkgtest is run with the binary packages of sdlgfx
> from unstable. It passes when run with only packages from testing. In
> tabular form:

Ah, indeed, thanks for the heads-up -- I'll look into it.


Cheers.
-- 
Manuel A. Fernandez Montecelo 

Bug#911794: bluetooth: Baseus B11: Poor audio quality HSP/HFP, terrible with a2dp sink

[Stelios Barberakis]

Package: bluetooth
Version: 5.50-1
Severity: important

Dear Maintainer,

** I am not sure if this is a bluetooth or pulseaudio issue :S **

New Baseus b11 device works seamlessly with my android 4.0 phone.
Also pairing with Dell Latitude e5550 (current debian installation) works fine.
However:
* Sound streaming with HSP/HFP sounds like a poor 1950 recording with audio
source away from microphone but you can still understand conversations or
lyrics in music
* Sound streaming with a2dp sink, is normal for ~5sec and then starts periodic
cycles (~2 seconds) of fast-forwarding (with noise) -> Stop -> Fast Forwarding,
etc. This is unusable.


$ rfkill list

0: dell-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
1: dell-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
4: phy1: Wireless LAN
Soft blocked: no
Hard blocked: no
7: hci0: Bluetooth
Soft blocked: no
Hard blocked: no


package versions missing from auto report:
* pulseaudio-module-bluetooth 12.2-2
* pulseaudio 12.2-2


$ lspci

02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
Subsystem: Intel Corporation Dual Band Wireless-AC 7265
Flags: bus master, fast devsel, latency 0, IRQ 49
Memory at f700 (64-bit, non-prefetchable) [size=8K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [40] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number 18-5e-0f-ff-ff-9f-2c-61
Capabilities: [14c] Latency Tolerance Reporting
Capabilities: [154] L1 PM Substates
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi


$ hciconfig -a

hci0:   Type: Primary  Bus: USB
BD Address: 18:5E:0F:9F:2C:65  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING
RX bytes:46259396 acl:441 sco:892779 events:97477 errors:0
TX bytes:105267095 acl:94171 sco:892691 commands:2626 errors:0
Features: 0xff 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF
Link mode: SLAVE ACCEPT
Class: 0x1c010c
Service Classes: Rendering, Capturing, Object Transfer
Device Class: Computer, Laptop
HCI Version: 4.2 (0x8)  Revision: 0x1000
LMP Version: 4.2 (0x8)  Subversion: 0x1000
Manufacturer: Intel Corp. (2)


$ bluetoothctl

[Baseus B11]# show
Controller 18:5E:0F:9F:2C:65 (public)
Class: 0x001c010c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: OBEX Object Push  (1105--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: IrMC Sync (1104--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Vendor specific   (5005--1000-8000-0002ee01)
UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
UUID: Message Access Server (1132--1000-8000-00805f9b34fb)
UUID: Headset   (1108--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0532
Discovering: no

[Baseus B11]# devices
Device 00:00:00:02:16:6A Baseus B11

[Baseus B11]# info 00:00:00:02:16:6A
Device 00:00:00:02:16:6A (public)
Name: Baseus B11
Alias: Baseus B11
Class: 0x00240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Headset   (1108--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Advanced Audio Distribu.. (110d--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)

Bug#909624: flightgear-phi: diff for NMU version 2018.1.1+dfsg1-1.1

[Adrian Bunk]

Control: tags 909624 + patch
Control: tags 909624 + pending

Dear maintainer,

I've prepared an NMU for flightgear-phi (versioned as 2018.1.1+dfsg1-1.1)
and uploaded it to DELAYED/14. Please feel free to tell me if I should 
cancel it.

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

diff -Nru flightgear-phi-2018.1.1+dfsg1/debian/changelog flightgear-phi-2018.1.1+dfsg1/debian/changelog
--- flightgear-phi-2018.1.1+dfsg1/debian/changelog	2018-05-14 21:39:03.0 +0300
+++ flightgear-phi-2018.1.1+dfsg1/debian/changelog	2018-10-24 23:31:32.0 +0300
@@ -1,3 +1,10 @@
+flightgear-phi (2018.1.1+dfsg1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix the sprintf.min.js symlink. (Closes: #909624)
+
+ -- Adrian Bunk   Wed, 24 Oct 2018 23:31:32 +0300
+
 flightgear-phi (2018.1.1+dfsg1-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru flightgear-phi-2018.1.1+dfsg1/debian/links flightgear-phi-2018.1.1+dfsg1/debian/links
--- flightgear-phi-2018.1.1+dfsg1/debian/links	2018-05-14 21:39:03.0 +0300
+++ flightgear-phi-2018.1.1+dfsg1/debian/links	2018-10-24 23:31:29.0 +0300
@@ -8,4 +8,4 @@
 usr/share/javascript/requirejs/text.jsusr/share/games/flightgear/Phi/3rdparty/require/text.js
 usr/share/javascript/bootstrap/css/bootstrap.min.css  usr/share/games/flightgear/Aircraft/c172p/WebPanel/bootstrap/bootstrap.min.css
 usr/share/javascript/bootstrap/js/bootstrap.min.jsusr/share/games/flightgear/Aircraft/c172p/WebPanel/bootstrap/bootstrap.min.js
-usr/lib/nodejs/sprintf-js/src/sprintf.min.js  usr/share/games/flightgear/Phi/3rdparty/sprintf/sprintf.min.js
+usr/share/javascript/sprintf-js/sprintf.min.jsusr/share/games/flightgear/Phi/3rdparty/sprintf/sprintf.min.js

Bug#911605: remove addresses of retired DDs from cdvendors@d.o alias

[Holger Wansing]

Hi,

Laura Arjona Reina  wrote:
> Hello all
> 
> Thanks Holger and Mattia for the report.
> 
> I have removed atte...@debian.org from the CDVENDORS entry in 
> www-master.debian.org
> I didn't find spaill...@debian.org there, but it was present in the WEBMASTER 
> entry, and since it's a retired address that won't work anymore, I have 
> removed 
> it from there.
> 
> FTR, these "aliases" are maintained in /srv/www.debian.org/mail/.mailfilter 
> in 
> www-master.debian.org machine.
> 
> Holger, if the issue is still not resolved please reopen this bug and I would 
> investigate further.

Let's see:
also sending this to cdvendors@d.o will show, if everything is fine now :-)

Thanks, Laura!


Holger


-- 
Holger Wansing 
PGP-Finterprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Bug#911780: psk31lx: version monotony violation: lenny had 2.1+2.2beta1-8

[Ervin Hegedüs]

Hi Andreas,

On Wed, Oct 24, 2018 at 07:17:21PM +0200, Andreas Beckmann wrote:
> Package: psk31lx
> Version: 2.1-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> lenny had the following binary package (from src:twpsk):

[...]
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911780
 
> According to
> http://snapshot.debian.org/binary/psk31lx/
> there is quite a mess of version numbers.
> 
> Bumping the source package version to 2.1+really2.1-1 with no further
> changes should fix this. This is preferred over adding an epoch.
> 
> $ dpkg --compare-versions 2.1+2.2beta1-8 lt 2.1+really2.1-1 && echo lt
> lt

thanks for the info, I've contacted with Ted, the maintainer of
psk31lx, is there any avaliable new relase - hope he will answer
as soon.



Anyway, I've checked the source package of psk31lx on stretch:

$ lsb_release -id
Distributor ID: Debian
Description:Debian GNU/Linux 9.4 (stretch)

$ apt-get source psk31lx
...

$ cat psk31lx-2.1/debian/changelog 
psk31lx (2.1-1) unstable; urgency=low

  * Initial release. (Closes: #772087)

 -- Milan Kupcevic   Sat, 07 Nov 2015 19:51:41 -0500

$ cat psk31lx-2.1/debian/control 
Source: psk31lx
Section: hamradio
Priority: optional
Maintainer: Debian Hamradio Maintainers 
Uploaders: Milan Kupcevic 
Build-Depends: debhelper (>= 9.0.0), libncurses5-dev, libpulse-dev
Standards-Version: 3.9.6
Homepage: http://wa0eir.bcts.info/psk31lx.html

Package: psk31lx
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: PSK31 terminal application with text-based user
interface
 psk31lx is a simple text-based terminal program with a built-in phase scope 
 and spectrum analyzer to aid in signal tuning. It uses a sound card to receive 
 and transmit PSK31 tone.


So looks like the avaliable source and binary packages are
differs (just fyi).

(And I din't find the source of the current stable package - the package site
is this:

https://packages.debian.org/stretch/psk31lx

the source points to here:
http://http.debian.net/debian/pool/main/p/psk31lx/psk31lx_2.1-1.debian.tar.xz

which is what I got through apt-get source, not the released
binary source (2.1-1+b1). This package contains an "empty"
changelog, there isn't any version history - how could I fix this
what you described?)


thanks, regards,


a.

Bug#910969: firmware-nonfree 20161130-4 flagged for acceptance

[Adam D Barratt]

Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian .

Thanks for your contribution!

Upload details
==

Package: firmware-nonfree
Version: 20161130-4

Explanation: fix security issues in Broadcom wifi firmware [CVE-2016-0801 
CVE-2017-0561 CVE-2017-9417 CVE-2017-13077 CVE-2017-13078 CVE-2017-13079 
CVE-2017-13080 CVE-2017-13081]; re-add transitional packages for 
firmware-{adiralink}

Bug#911281: disorderfs: can not update only mtime

[Chris Lamb]

tags 911281 + pending
thanks

Fixed in Git, pending upload:

  
https://salsa.debian.org/reproducible-builds/disorderfs/commit/e58c31a869a1b575a946b8977c6adf8aece5f1d7

  disorderfs.cpp |  6 ++
  tests/common   |  4 
  tests/touch| 12 
  3 files changed, 10 insertions(+), 12 deletions(-)


Regards,

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

Bug#911793: camitk: autopkgtest regression: Segmentation fault

[Paul Gevers]

Source: camitk
Version: 4.1.2-2
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With a recent upload of camitk the autopkgtest of camitk fails in
testing when that autopkgtest is run with the binary packages of camitk
from unstable. It passes when run with only packages from testing. In
tabular form:
   passfail
camitk from testing4.1.2-2
all others from testingfrom testing

I copied some of the output at the bottom of this report. As the
autopkgtest of the same version in unstable is passing, it may be caused
by a missing *versioned* (test) dependency.

Currently this regression is contributing to the delay of the migration
to testing [1]. Can you please investigate the situation and fix it? If
needed, please change the bug's severity.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=camitk

https://ci.debian.net/data/autopkgtest/testing/amd64/c/camitk/1201581/log.gz

autopkgtest [04:42:59]: test config-test.sh: [---
== checking camitk configuration ==
= Testing installed version =
= Temporary directory created /tmp/camitk-test-tmp.8KqRtk4hlS =
= Check OS =
= Uname is Linux = OS is Linux =
= Configuring xvfb =
PID of Xvfb: 7451
= Checking camitk-config =
[OK]
= Get CamiTK configuration =
/tmp/autopkgtest-lxc.73ftktc1/downtmp/build.Rkn/src/debian/tests/config-test.sh:
line 148:  7453 Segmentation fault  $camitkConfig --config 2>
/dev/null > ./config-output
unlink: No such file or directory
unlink /tmp/camitk-test-tmp.8KqRtk4hlS//Xvfb_screen0 failed, Invalid
argumentautopkgtest [04:43:00]: test config-test.sh:
---]



signature.asc
Description: OpenPGP digital signature

Bug#911785: dnssec-coverage complains about issues in the past

[Peter Palfrader]

To reproduce:


mkdir example.com
cd example.com
faketime -f '-1y'  /usr/sbin/dnssec-keygen -f KSK -K . -a RSASHA256 -3 -b 2048 
example.com

key=$(faketime -f '-1y'  /usr/sbin/dnssec-keygen -K . -a RSASHA256 -3 -b 1024 
-I +120d -D +150d example.com)
first=$key

lt=120
for i in `seq 1 5`; do
  lt=$((lt + 120))
  key=$(faketime -f '-1y'  /usr/sbin/dnssec-keygen -K . -S "$key.key" -I 
+${lt}d -D +$((lt+30))d example.com)
done

/usr/sbin/dnssec-coverage -K . -l 200d -c /usr/sbin/named-compilezone 
example.com
rm $first.key $first.private
/usr/sbin/dnssec-coverage -K . -l 200d -c /usr/sbin/named-compilezone 
example.com



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

Bug#911792: sdlgfx: autopkgtest regression: seems to run same test over and over again

[Paul Gevers]

Source: sdlgfx
Version: 2.0.25-10
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With a recent upload of sdlgfx the autopkgtest of sdlgfx fails in
testing when that autopkgtest is run with the binary packages of sdlgfx
from unstable. It passes when run with only packages from testing. In
tabular form:
   passfail
sdlgfx from testing2.0.25-10
all others from testingfrom testing

I copied the link to the log file below. It seems the same test is run
over and over again until the test finally times out.

Currently this regression is contributing to the delay of the migration
to testing [1]. Can you please investigate the situation and fix it?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul
PS: if this package migrates to testing like it is now, I'll add it to
the blacklist as this is wasting resources.

[1] https://qa.debian.org/excuses.php?package=sdlgfx

https://ci.debian.net/data/autopkgtest/testing/amd64/s/sdlgfx/1201557/log.gz




signature.asc
Description: OpenPGP digital signature

Bug#911791: drupal7: DATE_RFC7231 already defined in PHP 7.0.19 and 7.1.5

[William Blough]

Package: drupal7
Version: 7.52-2+deb9u4
Severity: important
Tags: upstream

In stable, drupal7 defines a constant (DATE_RFC7231) that conflicts with
the same constant already defined by php7.  This happens intermittently
depending on what code is being loaded/executed in php (the drupal
constant is defined in bootstrap, so is always loaded).  This results in
intermittent server errors (HTTP 500).

The upstream bug report and patch can be found at

https://www.drupal.org/project/drupal/issues/2877243

and has been applied by upstream in the 7.55 release.

It would be great if the patch for this issue could be applied in the
next stable update.

Thanks!

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

Kernel: Linux 4.9.0-6-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 drupal7 depends on:
ii  apache2 [httpd] 2.4.25-3+deb9u4
ii  curl7.52.1-5+deb9u6
ii  dbconfig-common 2.0.8
ii  debconf [debconf-2.0]   1.5.61
ii  default-mysql-client1.0.2
ii  exim4-daemon-light [mail-transport-agent]   4.89-2+deb9u3
ii  mariadb-client-10.1 [virtual-mysql-client]  10.1.26-0+deb9u1
ii  php 1:7.0+49
ii  php-gd  1:7.0+49
ii  php-mysql   1:7.0+49
ii  php-xml 1:7.0+49
ii  php7.0 [php]7.0.30-0+deb9u1
ii  php7.0-gd [php-gd]  7.0.30-0+deb9u1
ii  php7.0-xml [php-xml]7.0.30-0+deb9u1
ii  postgresql-client-9.4 [postgresql-client]   9.4.18-0+deb8u1
ii  postgresql-client-9.6 [postgresql-client]   9.6.7-0+deb9u1
ii  wwwconfig-common0.3.0

Versions of packages drupal7 recommends:
ii  default-mysql-server  1.0.2
ii  postgresql9.6+181+deb9u1
ii  sqlite3   3.16.2-5+deb9u1

drupal7 suggests no packages.

-- debconf information excluded

Bug#911760: lightdm-gtk-greeter segfault, lightdm restart too fast, can't login to desktop (Bug #911760)

[Bernhard Übelacker]

Hello Alex Andreotti,
just tried to reproduce this issue but did not happen inside my unstable amd64 
qemu VM.

Probably you can install an core dump collector like systemd-coredump?

Then you could see the stack where the crash happened by:
  coredumpctl gdb list
  coredumpctl gdb 

And even better would be if you could add the debug symbol repository
described in [1] and install e.g. lightdm-gtk-greeter-dbgsym plus
maybe more dbgsym packages for the shared objects shown in the stack.

Kind regards,
Bernhard

[1] https://wiki.debian.org/HowToGetABacktrace

Bug#911789: erlang-depends crashes on empty substvars file

[Michael Kuhn]

Package: erlang
Severity: normal
Tags: patch

Dear Maintainer,

erlang-depends crashes when the corresponding substvars file is empty.
This causes crashes on Ubuntu, where dpkg-shlibdeps sometimes creates
empty substvars files:

escript: exception error: no function clause matching string:substr([],1,-1) 
(string.erl, line 1774)
  in function  erl_eval:do_apply/6 (erl_eval.erl, line 670)
  in call from erl_eval:expr/5 (erl_eval.erl, line 438)
  in call from erl_eval:exprs/5 (erl_eval.erl, line 122)
  in call from erl_eval:local_func/6 (erl_eval.erl, line 557)
  in call from erl_eval:exprs/5 (erl_eval.erl, line 122)
  in call from lists:foreach/2 (lists.erl, line 1338)
dh_rebar: erlang-depends -perlang-p1-zlib returned exit code 127

See: 
https://launchpadlibrarian.net/379512161/buildlog_ubuntu-cosmic-amd64.erlang-p1-zlib_1.0.4-2_BUILDING.txt.gz

The attached patch fixes the problem.

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

Kernel: Linux 4.18.0-10-generic (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)
LSM: AppArmor: enabled

Versions of packages erlang depends on:
ii  erlang-asn1   1:20.3.8.5+dfsg-1build1
ii  erlang-base   1:20.3.8.5+dfsg-1build1
pn  erlang-common-test
pn  erlang-corba  
ii  erlang-crypto 1:20.3.8.5+dfsg-1build1
pn  erlang-debugger   
pn  erlang-dev
pn  erlang-dialyzer   
pn  erlang-diameter   
ii  erlang-edoc   1:20.3.8.5+dfsg-1build1
pn  erlang-eldap  
pn  erlang-erl-docgen 
pn  erlang-et 
pn  erlang-eunit  
pn  erlang-ic 
ii  erlang-inets  1:20.3.8.5+dfsg-1build1
pn  erlang-megaco 
ii  erlang-mnesia 1:20.3.8.5+dfsg-1build1
pn  erlang-observer   
ii  erlang-odbc   1:20.3.8.5+dfsg-1build1
ii  erlang-os-mon 1:20.3.8.5+dfsg-1build1
pn  erlang-parsetools 
ii  erlang-public-key 1:20.3.8.5+dfsg-1build1
pn  erlang-reltool
ii  erlang-runtime-tools  1:20.3.8.5+dfsg-1build1
ii  erlang-snmp   1:20.3.8.5+dfsg-1build1
pn  erlang-ssh
ii  erlang-ssl1:20.3.8.5+dfsg-1build1
ii  erlang-syntax-tools   1:20.3.8.5+dfsg-1build1
pn  erlang-tools  
pn  erlang-wx 
ii  erlang-xmerl  1:20.3.8.5+dfsg-1build1

Versions of packages erlang recommends:
pn  erlang-examples
pn  erlang-ic-java 
pn  erlang-jinterface  
pn  erlang-mode
pn  erlang-src 

Versions of packages erlang suggests:
pn  erlang-doc   
pn  erlang-manpages  
diff -Nru erlang-20.3.8.5+dfsg/debian/scripts/erlang-depends.in 
erlang-20.3.8.5+dfsg/debian/scripts/erlang-depends.in
--- erlang-20.3.8.5+dfsg/debian/scripts/erlang-depends.in   2018-08-13 
16:56:38.0 +0200
+++ erlang-20.3.8.5+dfsg/debian/scripts/erlang-depends.in   2018-10-24 
18:05:57.0 +0200
@@ -342,8 +342,10 @@
 
Len = string:len(StrData),
StrData2 = case Len - string:rstr(StrData, "\n") of
-   0 ->
+   0 when Len > 0 ->
string:left(StrData, Len - 1);
+   0 when Len == 0 ->
+   StrData;
_ ->
StrData
   end,
@@ -406,8 +408,10 @@
 
Len = string:len(StrData),
StrData2 = case Len - string:rstr(StrData, "\n") of
-   0 ->
+   0 when Len > 0 ->
string:left(StrData, Len - 1);
+   0 when Len == 0 ->
+   StrData;
_ ->
StrData
   end,

Bug#911790: update-chromium-homepage uses static config file

[Mike Gabriel]

Package: debian-edu-config
Severity: minor
Version: 2.10.41

Hi,

I looked at the update-firefox-homepage and update-chromium-homepage  
scripts today and realized that the update-chromium-homepage script  
statically creates this config file snippet:


```
{
  "HomepageLocation" : "https://www;,
  "HomepageIsNewTabPage" : false
}
```

Should this passage in the script be

```
{
  "HomepageLocation" : "$url",
  "HomepageIsNewTabPage" : false
}
```

???

Mike
--

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

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



pgpTBa4bRNNPY.pgp
Description: Digitale PGP-Signatur

Bug#909818: confirm downgrade of fontconfig solves the problem

[Francesco Potortì]

I can confirm that downgrading fontconfig and libfontcofig1 solves the
problem.  Unfortunately, the 2.13.0 version is no more available in the
archive, and previous versions are not compatible.  So I had to
recompile them myself.  Here are the packages I just installed on my
amd64 box:

 
 

You can download them, install them with

$ sudo dpkg -i libfontconfig1_2.13.0-5_amd64.deb fontconfig_2.13.0-5_amd64.deb

and prevent upgrading them with

$ sudo aptitude hold fontconfig libfontconfig1

until this bug is solved

-- 
Francesco Potortì (ricercatore)Voice:  +39.050.621.3058
ISTI - Area della ricerca CNR  Mobile: +39.348.8283.107
via G. Moruzzi 1, I-56124 Pisa Skype:  wnlabisti
(entrance 20, 1st floor, room C71) Web:http://fly.isti.cnr.it

Bug#911788: [game-data-packager] Fails to download wolf3d data from http://pkg-games.alioth.debian.org

[Juanjo Benages]

Package: game-data-packager
Version: 59
Severity: normal

--- Please enter the report below this line. ---
When trying to download the demo data gives the following error:

$ game-data-packager wolf3d
WARNING:game_data_packager.download:Failed to download 
"http://pkg-games.alioth.debian.org/game-data/1wolf14.zip": error [Errno -2] Name or service not known>
ERROR:game_data_packager.build:Failed to download necessary files for 
wolf3d-demo-data
ERROR:game_data_packager.build:Unable to complete any packages because 
downloads failed.


Downloading the file from the internet 1wolf14.zip and using this file 
works.


--- System information. ---
Architecture:
Kernel:   Linux 4.18.0-2-amd64

Debian Release: buster/sid
 500 testing deb.debian.org

--- Package information. ---
Depends(Version) | Installed
-+-==
dpkg(>= 1.19.0)  | 1.19.2
OR fakeroot | 1.23-1
python3-debian   | 0.1.33
python3-yaml | 3.12-1+b2
python3:any(>= 3.3.2-2~) |


Recommends  (Version) | Installed
=-+-===
game-data-packager-runtime(>= 59) | 59


Suggests(Version) | Installed
=-+-=
arj   |
binutils  | 2.31.1-7
cabextract| 1.6-1.1
cdparanoia|
dynamite (>= 0.1.1-2) | 0.1.1-2+b2
gcc   | 4:8.1.0-1
gdebi |
OR gdebi-kde |
gir1.2-gdkpixbuf-2.0  | 2.38.0+dfsg-6
innoextract   | 1.7-1
lgc-pg|
lgogdownloader|
lhasa |
OR jlha-utils|
OR lzh-archiver  |
make  | 4.2.1-1.2
p7zip-full| 16.02+dfsg-6
steam |
steamcmd  |
unace-nonfree |
unar  |
unrar |
unshield  |
unzip | 6.0-21
vorbis-tools  |
xdelta|
xdelta3   |

Bug#911787: RM: xview -- RoQA; Orphaned; RC-Buggy; Not compatible with 64-bit arch; Upstream dead for decades

[Boyuan Yang]

Package: ftp.debian.org
Severity: normal
X-Debbugs-CC: 911...@bugs.debian.org
User: ftp.debian@packages.debian.org
Usertags: remove

Dear FTP Masters,

As discussed in https://bugs.debian.org/911774 ,
please remove package xview from Debian archive. It is basically a
legacy left from
last century and it's a long overdue to get it removed.

Package xview has no reverse dependencies.

--
Regards,
Boyuan Yang

Bug#911786: libspring-java: CVE-2018-15756

[Salvatore Bonaccorso]

Source: libspring-java
Version: 4.3.19-1
Severity: important
Tags: security upstream

Hi,

The following vulnerability was published for libspring-java.

CVE-2018-15756[0]:
| Spring Framework, version 5.1, versions 5.0.x prior to 5.0.10,
| versions 4.3.x prior to 4.3.20, and older unsupported versions on the
| 4.2.x branch provide support for range requests when serving static
| resources through the ResourceHttpRequestHandler, or starting in 5.0
| when an annotated controller returns an
| org.springframework.core.io.Resource. A malicious user (or attacker)
| can add a range header with a high number of ranges, or with wide
| ranges that overlap, or both, for a denial of service attack. This
| vulnerability affects applications that depend on either spring-webmvc
| or spring-webflux. Such applications must also have a registration for
| serving static resources (e.g. JS, CSS, images, and others), or have
| an annotated controller that returns an
| org.springframework.core.io.Resource. Spring Boot applications that
| depend on spring-boot-starter-web or spring-boot-starter-webflux are
| ready to serve static resources out of the box and are therefore
| vulnerable.

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-15756
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-15756
[1] https://pivotal.io/security/cve-2018-15756

Please adjust the affected versions in the BTS as needed, but
basically as well already it is know older 4.2 versions (wich are
unsupported) are affected as well.

Regards,
Salvatore

Bug#907336: disable ghostscript

[Bastien ROUCARIES]

Le mer. 24 oct. 2018 à 20:39, Thorsten Alteholz  a
écrit :

> Hi,
>
> is there any plan to do the suggested disabling of ghostscript?
> I wonder whether this should be done as well in other releases when
> CVE-2018-18025 will be fixed.
>

If security team thinks it a good idéal why not. But we lost pdf
convention...

Maybe a debconf question ?

Bastien

>
>Thorsten
>
>

Bug#911750: Race condition in d-i leading to kernel from security.debian.org to be kept back

[Ben Hutchings]

On Wed, 2018-10-24 at 16:30 +0200, Raphaël Halimi wrote:
> Le 24/10/2018 à 14:15, Ben Hutchings a écrit :
> > > When the kernel metapackage (linux-image-) is initially installed,
> > > APT doesn't install recommended packages, and security.debian.org
> > > repository is not configured yet, so the installer naturally fetches the
> > > latest kernel from the core suite. After APT configuration, and other
> > > repositories and suites are available, debian-installer runs an upgrade;
> > > but if a newer version of linux-image- is found in one of those
> > > newly available repositories (security.debian.org in this case), it's
> > > not installed because APT refuses to install the recommended packages
> > > (firware-linux-free, irqbalance) to satisfy dependencies, so the kernel
> > > metapackage is kept back.
> > 
> > I'm fairly sure it's the ABI bump in the kernel that prevents
> > upgrading, not the recommended packages.  This is tracked as #908711.
> 
> You're right, it seems so obvious now.
> 
> Sorry for the duplicate, I did search the web for "bugs debian-installer
> kernel not upgraded during installation" but the title of this bug was
> too different, and I missed it.
> 
> Do you want me to close this one, or to merge it ?

I'll merge it.

Ben.

-- 
Ben Hutchings
Never put off till tomorrow what you can avoid all together.




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

Bug#911757: zsh-antigen: please make the build reproducible

[Chris Lamb]

Hi Daniel,

> Chris, are you sure that's right?  According to date(1), the --date
> option takes an argument, so that would seem to take "--utc" as the date
> to parse

Mea culpa.

I think what happened was that as it was a patch-to-a-patch I
either a) made the change I attached quasi-manually and I made a
mistake or b) I just screwed up and the error message itself made
the package reproducible.

As in:

  date: the argument ‘@1’ lacks a leading '+';

… is, of course, the same in all timezones. *grin*

Updated patch attached. Thanks for your careful review, extremely
appreciated.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- 
a/debian/patches/0001-Use-package-specific-revision-and-date-for-build.patch
2018-10-24 13:50:20.920473047 -0400
--- 
b/debian/patches/0001-Use-package-specific-revision-and-date-for-build.patch
2018-10-24 13:51:46.254632670 -0400
 @@ -91,8 +91,8 @@ build:
@echo "-antigen-env-setup" >> ${TARGET}
@echo "${VERSION}" > ${VERSION_FILE}
@@ -17,7 +15,7 @@
 -  @$(call ised,"s/{{ANTIGEN_REVISION}}/$$(git log -n1 --format=%h -- 
src)/",${TARGET})
 -  @$(call ised,"s/{{ANTIGEN_REVISION_DATE}}/$$(git log -n1 --format='%ai' 
-- src)/",${TARGET})
 +  @$(call ised,"s/{{ANTIGEN_REVISION}}/Debian/",${TARGET})
-+  @$(call ised,"s/{{ANTIGEN_REVISION_DATE}}/$$(date --date 
@$$(dpkg-parsechangelog -STimestamp) --rfc-3339=seconds)/",${TARGET})
++  @$(call ised,"s/{{ANTIGEN_REVISION_DATE}}/$$(date --utc --date 
@$$(dpkg-parsechangelog -STimestamp) --rfc-3339=seconds)/",${TARGET})
  ifeq (${WITH_DEBUG}, no)
@$(call isede,"s/ (WARN|LOG|ERR|TRACE) .*&//",${TARGET})
@$(call isede,"/ (WARN|LOG|ERR|TRACE) .*/d",${TARGET})

Bug#911774: O: xview -- XView shared libraries

[Sven Joachim]

On 2018-10-24 18:17 +0200, Mattia Rizzolo wrote:

> Package: wnpp
>
> The current maintainer of xview, Blars Blarson ,
> is apparently not active anymore.  Therefore, I orphan this package now.
>
> Maintaining a package requires time and skills. Please only adopt this
> package if you will have enough time and attention to work on it.
>
> If you want to be the new maintainer, please see
> https://www.debian.org/devel/wnpp/#howto-o for detailed
> instructions how to adopt a package properly.

FWIW, this package should be removed rather than adopted.  It is ugly
legacy code from the 1990's that apparently does not work at all on
64-bit architectures anymore.  Fortunately there do not seem to be any
reverse dependencies.

Cheers,
   Sven

Bug#907336: disable ghostscript

[Thorsten Alteholz]

Hi,

is there any plan to do the suggested disabling of ghostscript?
I wonder whether this should be done as well in other releases when 
CVE-2018-18025 will be fixed.


  Thorsten

Bug#911785: dnssec-coverage complains about issues in the past

[Peter Palfrader]

Package: bind9utils
Version: 1:9.10.3.dfsg.P4-12.3+deb9u4
Severity: normal
Tags: patch

We regularly rotate our ZSKs, and just recently we started removing old
.key files from our keydir.

The oldest remaining ZSK now has a published date in the past, and an
activation date also in the past but after the publish date.
  (Previously, the oldest ZSK was the *first* ZSK, and it had publish
   and activate at the same time.)

dnssec-coverage complains about this:

| Checking scheduled ZSK events for zone debian.nl, algorithm RSASHA256...
|   Wed Jul 11 12:07:03 UTC 2018:
| Publish: debian.nl/008/17304 (ZSK)
| ERROR: No ZSK's are active after this event

for
; This is a zone-signing key, keyid 17304, for debian.nl.
; Created: 20180211121307 (Sun Feb 11 12:13:07 2018)
; Publish: 20180711120703 (Wed Jul 11 12:07:03 2018)
; Activate: 20180810120703 (Fri Aug 10 12:07:03 2018)
; Inactive: 20181208120703 (Sat Dec  8 12:07:03 2018)
; Delete: 20190107120703 (Mon Jan  7 12:07:03 2019)
[..key..]

; This is a zone-signing key, keyid 29616, for debian.nl.
; Created: 20180612045523 (Tue Jun 12 04:55:23 2018)
; Publish: 20181108120703 (Thu Nov  8 12:07:03 2018)
; Activate: 20181208120703 (Sat Dec  8 12:07:03 2018)
; Inactive: 20190407120703 (Sun Apr  7 12:07:03 2019)
; Delete: 20190507120703 (Tue May  7 12:07:03 2019)
[..key..]

; This is a zone-signing key, keyid 37155, for debian.nl.
; Created: 20181009121102 (Tue Oct  9 12:11:02 2018)
; Publish: 20190308120703 (Fri Mar  8 12:07:03 2019)
; Activate: 20190407120703 (Sun Apr  7 12:07:03 2019)
; Inactive: 20190805120703 (Mon Aug  5 12:07:03 2019)
; Delete: 20190904120703 (Wed Sep  4 12:07:03 2019)
[..key..]

I propose dnssec-coverage ignore cases of no
active/publish/active that happened in the past.


--- /usr/sbin/dnssec-coverage   2018-01-15 21:40:17.0 +
+++ /srv/dns.debian.org/bin/dnssec-coverage 2018-10-24 18:24:01.216562896 
+
@@ -15,6 +15,10 @@
 # PERFORMANCE OF THIS SOFTWARE.
 
 
+# changes 2018-10-24, Peter Palfrader
+#  - ignore "errors" in the past (like no active keys)
+#as that can result from retiring old (and deleted) keyfiles
+
 import argparse
 import os
 import glob
@@ -23,6 +27,7 @@
 import time
 import calendar
 from collections import defaultdict
+from itertools import zip_longest
 import pprint
 
 prog='dnssec-coverage'
@@ -531,7 +536,7 @@
 if eventgroup:
 eventgroups.append(eventgroup)
 
-for eventgroup in eventgroups:
+for eventgroup, next_eventgroup in zip_longest(eventgroups, 
eventgroups[1:]):
 if (args.checklimit and
 calendar.timegm(eventgroup[0].when) > args.checklimit):
 print("Ignoring events after %s" %
@@ -545,18 +550,19 @@
 list_events(eventgroup)
 
 # and then check for inconsistencies:
+
+# but do not bail out on inconsistencies in the past that may be the 
result of keys that got retired
+bygones = next_eventgroup is not None and 
calendar.timegm(next_eventgroup[0].when) < time.time()
 if len(active) == 0:
-print ("ERROR: No %s's are active after this event" % keytype)
-return False
+print ("%s: No %s's are active after this event" %(['ERROR', 
'INFO'][bygones], keytype))
+if not bygones: return False
 elif len(published) == 0:
-sys.stdout.write("ERROR: ")
-print ("ERROR: No %s's are published after this event" % keytype)
-return False
+print ("%s: No %s's are published after this event" % (['ERROR', 
'INFO'][bygones], keytype))
+if not bygones: return False
 elif len(published.intersection(active)) == 0:
-sys.stdout.write("ERROR: ")
-print (("ERROR: No %s's are both active and published " +
-"after this event") % keytype)
-return False
+print (("%s: No %s's are both active and published " +
+"after this event") % (['ERROR', 'INFO'][bygones], 
keytype))
+if not bygones: return False
 
 if not eventsfound:
 print ("ERROR: No %s events found in '%s'" %

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

Bug#911784: grub: Couldn't find physical volume `(null)'. Some modules may be missing from core image..

[Thorsten Glaser]

Package: grub-pc
Version: 2.02~beta2-22+deb8u1
Severity: minor

Screenshot:

# dpkg-reconfigure -plow grub-pc
[… I’ll spare you debconf …]
Installing for i386-pc platform.
grub-install: warning: Couldn't find physical volume `(null)'. Some modules may 
be missing from core image..
grub-install: warning: Couldn't find physical volume `(null)'. Some modules may 
be missing from core image..
Installation finished. No error reported.
Installing for i386-pc platform.
grub-install: warning: Couldn't find physical volume `(null)'. Some modules may 
be missing from core image..
grub-install: warning: Couldn't find physical volume `(null)'. Some modules may 
be missing from core image..
Installation finished. No error reported.
Installing for i386-pc platform.
grub-install: warning: Couldn't find physical volume `(null)'. Some modules may 
be missing from core image..
grub-install: warning: Couldn't find physical volume `(null)'. Some modules may 
be missing from core image..
Installation finished. No error reported.
Installing for i386-pc platform.
grub-install: warning: Couldn't find physical volume `(null)'. Some modules may 
be missing from core image..
grub-install: warning: Couldn't find physical volume `(null)'. Some modules may 
be missing from core image..
Installation finished. No error reported.
Installing for i386-pc platform.
grub-install: warning: Couldn't find physical volume `(null)'. Some modules may 
be missing from core image..
grub-install: warning: Couldn't find physical volume `(null)'. Some modules may 
be missing from core image..
Installation finished. No error reported.
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-3.16.0-7-amd64
Found initrd image: /boot/initrd.img-3.16.0-7-amd64
/usr/sbin/grub-probe: warning: Couldn't find physical volume `(null)'. Some 
modules may be missing from core image..
/usr/sbin/grub-probe: warning: Couldn't find physical volume `(null)'. Some 
modules may be missing from core image..
/usr/sbin/grub-probe: warning: Couldn't find physical volume `(null)'. Some 
modules may be missing from core image..
Found linux image: /boot/vmlinuz-3.16.0-6-amd64
Found initrd image: /boot/initrd.img-3.16.0-6-amd64
/usr/sbin/grub-probe: warning: Couldn't find physical volume `(null)'. Some 
modules may be missing from core image..
/usr/sbin/grub-probe: warning: Couldn't find physical volume `(null)'. Some 
modules may be missing from core image..
/usr/sbin/grub-probe: warning: Couldn't find physical volume `(null)'. Some 
modules may be missing from core image..
Found memtest86+ image: /memtest86+.bin
Found memtest86+ multiboot image: /memtest86+_multiboot.bin
done


The MBR did install successfully on the new /dev/sde drive, though
I’m a bit wary to reboot now.


The information below is slightly redacted to remove customer names.

-- Package-specific info:

*** BEGIN /proc/mounts
/dev/dm-0 / ext4 rw,relatime,stripe=256,data=ordered 0 0
/dev/md0 /boot ext3 rw,noatime,data=ordered 0 0
/dev/mapper/vg--ldegen--wirt-someOSiso /var/lib/libvirt/someOSiso ext4 
rw,noatime,stripe=256,data=ordered 0 0
*** END /proc/mounts

*** BEGIN /boot/grub/device.map
(hd0)   /dev/disk/by-id/ata-SAMSUNG_HD502HJ_S20BJ9EB811390
(hd1)   /dev/disk/by-id/ata-SAMSUNG_HD502HJ_S20BJ9KB913500
(hd2)   /dev/disk/by-id/ata-SAMSUNG_HD502HJ_S20BJ9KB913499
(hd3)   /dev/disk/by-id/ata-SAMSUNG_HD502HJ_S20BJA0B806498
(hd4)   /dev/disk/by-id/ata-SAMSUNG_HD502HJ_S20BJ9KB913498
*** END /boot/grub/device.map

*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
  fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
insmod all_video
  else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
  fi
}

insmod part_msdos
insmod part_msdos
insmod part_msdos
insmod part_msdos
insmod diskfilter
insmod mdraid09
insmod lvm
insmod ext2
set 
root='lvmid/J88cU5-AHPt-dbjT-kJta-5Wa4-l1KP-XzQPG4/xBPd3p-bp65-XpBW-yWHy-9tvT-S7ah-fbetZj'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid 

Bug#882047: [pkg-apparmor] Bug#882047: Bug#882047: apparmor-utils: aa-complain thunderbird fails

[Christian Boltz]

Hello,

Am Sonntag, 21. Oktober 2018, 16:49:29 CEST schrieb Christian Boltz:
> As usual if I do some tests, I found more issues:
> - the attachment won't be checked if a profile has a name (so using a
>   variable currently doesn't matter ;-)
> - aa-complain first does a "which thunderbird" and then checks with
> the full path, so the profile name also won't match - "thunderbird"
> != "/usr/bin/thunderbird"
> - profile names with alternations (without attachment specification)
>   will also not match because aa.py get_profile_filename() doesn't use
> AARE

I worked on this in the last days, and as expected, it really resulted 
in "bigger changes". On the positive side, the new code now 
distinguishes between profile name and attachment (which avoids 
accidential matches and documents what each section of the code is 
using) and between active (/etc/apparmor.d/) and inactive/extra 
(/usr/share/share/apparmor/extra-profiles) profiles which fixes another 
sourse of problems. Oh, and the ProfileList class is covered by unit 
tests :-)

All changes survived my testing, but getting more testers always helps. 
If you want to test and/or review my changes, you can get them from
https://gitlab.com/apparmor/apparmor/merge_requests/249

Note that variables in the profile name still don't get expanded/
matched.

> Maybe (additionally) matching the aa-complain parameter against the
> profile name would be an easy option/workaround, but I'm undecided if
> this is a good idea because it could also cause false positives -
> opinions?
> 
> Or to ask the other way round - assuming you have
> profile foo /bin/bar { ... }
> should   aa-complain foo   find that profile?

For now, I decided not to support that, so aa-complain will continue to 
interpret all parameters as attachment.


Regards,

Christian Boltz
-- 
> Was muß man tun um auf NTFS schreiben zu können. In der fstab
> hab ich schon auf rw gesetzt. Was muß man noch tun?
1. Beten.
2. MS veranlassen, die Spezifikationen offenzulegen.
3. Weiterbeten.
[> Stefan und Bernd Obermayr in suse-linux]


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

Bug#909523: [pkg-apparmor] Bug#909523: cachefilesd broken by apparmor

[Anthony DeRobertis]

On Sun, Oct 21, 2018 at 10:24:46AM +0200, intrigeri wrote:
> 
> Can you please retry with AppArmor enabled, after commenting out the
> "secctx" directive in /etc/cachefilesd.conf? If this works, then my
> hypothesis will be confirmed and my recommendation will be:

Seems your hypothesis is correct.

I rebooted and removed apparmor=0 from the kernel command line, thus
re-enabling AppArmor. Cachefilesd failed again (as expected).

I then went ahead and edited cachefilesd.conf and commented out the
secctx line. After that, cachefilesd started successfully.

Bug#911782: python-cryptography FTBFS: openssl test fails

[Helmut Grohne]

Source: python-cryptography
Version: 2.3-1
Severity: serious
Tags: ftbfs

python-cryptography fails to build from source in unstable. The same
version builds fine in testing. This indicates that a dependency (e.g.
openssl) is the cause.

https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/python-cryptography_2.3-1.rbuild.log.gz

| === FAILURES 
===
|  TestOpenSSL.test_openssl_assert_error_on_stack 

| 
| self = 
| 
| def test_openssl_assert_error_on_stack(self):
| b = Binding()
| b.lib.ERR_put_error(
| b.lib.ERR_LIB_EVP,
| b.lib.EVP_F_EVP_ENCRYPTFINAL_EX,
| b.lib.EVP_R_DATA_NOT_MULTIPLE_OF_BLOCK_LENGTH,
| b"",
| -1
| )
| with pytest.raises(InternalError) as exc_info:
| _openssl_assert(b.lib, False)
| 
| error = exc_info.value.err_code[0]
| >   assert error.code == 101183626
| E   AssertionError: assert 337146240L == 101183626
| E+  where 337146240L = _OpenSSLErrorWithText(code=337146240L, lib=20, 
func=391, reason=384, reason_text='error:14187180:SSL 
routines:ssl_do_config:bad value').code
| 
| ../../../tests/hazmat/bindings/test_openssl.py:98: AssertionError
| === warnings summary 
===
...
| = 1 failed, 96853 passed, 4186 skipped, 25 warnings in 443.73 seconds 
==
| E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd 
/build/1st/python-cryptography-2.3/.pybuild/cpython2_2.7_cryptography/build; 
python2.7 -m pytest {dir}/tests/
| dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
| make: *** [debian/rules:17: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Helmut

Bug#905262: RFS: golang-github-tcnksm-go-gitconfig

[Alexandre Viau]

On 2018-10-24 1:23 p.m., Jongmin Kim wrote:
> Thank you for your upload!
> 
> I have one more request. Could you please review and upload?
> Pushed all to our team's repo:
> 
> https://salsa.debian.org/go-team/packages/golang-github-tcnksm-go-gitconfig

Uploaded!

Thank you for your contribution!

Cheers,

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#910764: openjfx: segmentation fault in GtkNativeMainLoopThread

[Markus Koschany]

I believe I have found a way to workaround this issue for the moment. If
I pass -Djdk.gtk.version=2 to PDFsam version 3.3.7 it no longer crashes.
However there is another issue with fontawesomefx, so there is still
some work to do. I think I will forward this issue to the OpenJFX
developers because it looks like a bug in the GTK3 related native libraries.



signature.asc
Description: OpenPGP digital signature

Bug#905262: RFS: golang-github-tcnksm-go-gitconfig

[Jongmin Kim]

Thank you for your upload!

I have one more request. Could you please review and upload?
Pushed all to our team's repo:

https://salsa.debian.org/go-team/packages/golang-github-tcnksm-go-gitconfig

As you know, we applied a patch in this package.

'go-gitconfig' did a test which is not fully isolated from testing
environment. It fails when it runs on git repo with its local config
including 'user.name' and/or 'user.email'.

The patch makes the test creating and using the temporary git repo
instead of using the real, both for global config (~/.gitconfig) and
local config (.git/config). Felix, who wrote the patch, also sent a PR
to the upstream repo [1] for fixing this problem. When it fixed, we will
remove the patch and update the package.

Thanks for your time!


-- 
Jongmin Kim

OpenPGP key located at
https://jmkim-pgp.github.io/keys/pubkey.D39D8D29BAF36DF8.Jongmin_Kim.asc
OpenPGP fingerprint: 012E 4A06 79E1 4EFC DAAE  9472 D39D 8D29 BAF3 6DF8


signature.asc
Description: PGP signature

Bug#911780: psk31lx: version monotony violation: lenny had 2.1+2.2beta1-8

[Andreas Beckmann]

Package: psk31lx
Version: 2.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

lenny had the following binary package (from src:twpsk):

Package: psk31lx
Priority: optional
Section: hamradio
Installed-Size: 148
Maintainer: Joop Stakenborg 
Architecture: i386
Source: twpsk
Version: 2.1+2.2beta1-8
Depends: libc6 (>= 2.7-1), libgcc1 (>= 1:4.2.1), libncurses5 (>= 
5.6+20071006-3), libstdc++6 (>= 4.2.1)
Filename: pool/main/t/twpsk/psk31lx_2.1+2.2beta1-8_i386.deb
Size: 33248
MD5sum: a47956cf6af3d155f797ffc8b4a644b1
SHA1: 3ce698aa6974a1b4b049a7944d1a474e4e3c7b0c
SHA256: 173e0a76cbf0afcbb83f1c0ad4368b816c5acbc8dc459ecccf81a308dd62c674
Description: Soundcard-based ncurses program for operating PSK31
 Psk31lx uses a soundcard to receive and transmit PSK31, an extremely
 narrow band HF-mode. PSK31 is a mode for keyboard QSO's.


while stretch has this one with a lower version number (from src:psk31lx):

Package: psk31lx
Source: psk31lx (2.1-1)
Version: 2.1-1+b1
Installed-Size: 91
Maintainer: Debian Hamradio Maintainers 
Architecture: i386
Depends: libc6 (>= 2.4), libgcc1 (>= 1:3.0), libncurses5 (>= 6), libpulse0 (>= 
0.99.1), libstdc++6 (>= 5), libtinfo5 (>= 6)
Description: PSK31 terminal application with text-based user interface
Homepage: http://wa0eir.bcts.info/psk31lx.html
Description-md5: 55820db20bf58c287b473c1e3b6c6ac7
Tag: hardware::hamradio, hardware::modem, implemented-in::c,
 interface::text-mode, role::program, scope::utility,
 uitoolkit::ncurses, use::chatting
Section: hamradio
Priority: optional
Filename: pool/main/p/psk31lx/psk31lx_2.1-1+b1_i386.deb
Size: 34248
MD5sum: 74882786eba9fdc15634323f36e617d1
SHA256: 8eeeaf4a951c62b424c16e8c76b97e873c2b2b92c8d7d00790c5b6f0cd7d472a


According to
http://snapshot.debian.org/binary/psk31lx/
there is quite a mess of version numbers.

Bumping the source package version to 2.1+really2.1-1 with no further
changes should fix this. This is preferred over adding an epoch.

$ dpkg --compare-versions 2.1+2.2beta1-8 lt 2.1+really2.1-1 && echo lt
lt


Andreas

Bug#911781: kmail and akoinadi not working correctly - deleted mails appear again

[Hans-J. Ullrich]

Package: kmail
Version: 4:18.08.1-1
Severity: important

Dear Maintainer,

sadlly the playing together between kamial and akonadi is going worse from 
version to version. 
At first, when you want to delete mails, the deletion was lasting a long time. 

Then soime versions later, mails in inbox folder could not be deleted when 
deleting them fast or if you wanted to delete several mails in one stap (mark 
all, then delete). Either kmail hanged in a loop or the delted mails appeared 
again, whgen you clicked anotherfolder, then clicking inbox again. Sometimes 
akonadi had to be complete restartetd , to get kmail initialised.

All these things I reported in the forums, but things did not imporove.

And today, there is this:

1. Move a bunsch of unread mails from inbox to trash in kamil.

2. Empty the trash.

3. Click on any other folkder i.e. inbox.

4. click now trash again.

5. Tadaaa! Most mails appear again!

Mails also appear after restart of kmail, restart akonadi or reboot. Even after 
some days they appear again!

I set this report to "important" because IMHO this is a security hole, too. 
Maybe I want to have important mnails deleted for security reasons or what ever 
- and then they are not gone? This is not good!

Please, if this is not a kmail problem, but an akonadi issue (what I can not 
verify), it would be nice, if you could inform those maintainers.

Thank you for reading and any help!


Best regards

Hans




  

-e System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

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

Versions of packages kmail depends on:
ii  akonadi-server   4:18.08.1-1+b1
ii  kdepim-runtime   4:18.08.1-1
ii  kio  5.49.0-1
ii  libc62.27-6
ii  libgcc1  1:8.2.0-8
ii  libgpgmepp6  1.12.0-4
ii  libkf5akonadiagentbase5  4:18.08.1-1+b1
ii  libkf5akonadicontact54:18.08.1-1
ii  libkf5akonadicore5abi2   4:18.08.1-1+b1
ii  libkf5akonadimime5   4:18.08.1-2
ii  libkf5akonadisearch-bin  4:18.08.1-1+b1
ii  libkf5akonadisearch-plugins  4:18.08.1-1+b1
ii  libkf5akonadisearchdebug54:18.08.1-1+b1
ii  libkf5akonadisearchpim5  4:18.08.1-1+b1
ii  libkf5akonadiwidgets5abi14:18.08.1-1+b1
pn  libkf5bookmarks5 
ii  libkf5calendarcore5abi2  4:18.08.1-1
ii  libkf5calendarutils5 4:18.08.1-1
pn  libkf5codecs5
pn  libkf5completion5
pn  libkf5configcore5
ii  libkf5configgui5 5.49.0-1
ii  libkf5configwidgets5 5.49.0-1
ii  libkf5contacts5  4:18.08.1-1
ii  libkf5coreaddons55.49.0-1
ii  libkf5crash5 5.49.0-1
ii  libkf5dbusaddons55.49.0-1
ii  libkf5followupreminder5  4:18.08.1-1
ii  libkf5grantleetheme-plugins  18.08.1-1
ii  libkf5gravatar5abi2  4:18.08.1-1
ii  libkf5guiaddons5 5.49.0-1
ii  libkf5i18n5  5.49.0-1
ii  libkf5iconthemes55.49.0-1
ii  libkf5identitymanagement518.08.1-1
ii  libkf5itemmodels55.49.0-1
ii  libkf5itemviews5 5.49.0-1
ii  libkf5jobwidgets55.49.0-1
ii  libkf5kcmutils5  5.49.0-1
ii  libkf5kiocore5   5.49.0-1
ii  libkf5kiofilewidgets55.49.0-1
ii  libkf5kiowidgets55.49.0-1
ii  libkf5kontactinterface5  18.08.1-1
ii  libkf5ksieveui5  4:18.08.1-1
ii  libkf5libkdepim-plugins  4:18.08.1-1
ii  libkf5libkdepim5 4:18.08.1-1
ii  libkf5libkdepimakonadi5  4:18.08.1-1
ii  libkf5libkleo5   4:18.08.1-1
ii  libkf5mailcommon5abi24:18.08.1-1
ii  libkf5mailtransport5 18.08.1-2
ii  libkf5mailtransportakonadi5  18.08.1-2
ii  libkf5messagecomposer5abi1   4:18.08.1-1
ii  libkf5messagecore5abi1   4:18.08.1-1
ii  libkf5messagelist5abi1   4:18.08.1-1
ii  libkf5messageviewer5abi1 4:18.08.1-1
ii  libkf5mime5abi1  18.08.1-1
ii  libkf5mimetreeparser5abi14:18.08.1-1
ii  libkf5notifications5 5.49.0-1
ii  libkf5notifyconfig5  5.49.0-1
ii  libkf5parts5 5.49.0-1
ii  libkf5pimcommon5abi2 4:18.08.1-1
ii  libkf5pimcommonakonadi5abi1  4:18.08.1-1
ii  libkf5pimtextedit5abi2   18.08.1-1
ii  libkf5sendlater5 4:18.08.1-1
ii  libkf5service-bin5.49.0-1
ii  libkf5service5   5.49.0-1
ii  libkf5sonnetui5  5.49.0-1
ii  libkf5templateparser54:18.08.1-1
ii  libkf5textwidgets5   5.49.0-1
ii  libkf5tnef5  4:18.08.1-1
ii  libkf5wallet-bin 5.49.0-1
ii  libkf5wallet55.49.0-1
ii  libkf5webengineviewer5abi1   

Bug#911779: RFS: multiblend/0.6.2-1 multi-level image blender for the seamless blending of panoramic

[Fernando Toledo]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

  I am looking for a sponsor for my package "multiblend"

 * Package name: multiblend
   Version : 0.6.2-1
   Upstream Author : David Horman 
 * URL : http://horman.net/multiblend/
 * License : GPL-2+
   Section : graphics

  It builds those binary packages:

multiblend - multi-level image blender for the seamless blending of
panoramic

  To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/multiblend


  Alternatively, one can download the package with dget using this command:

dget -x
https://mentors.debian.net/debian/pool/main/m/multiblend/multiblend_0.6.2-1.dsc

  More information about multiblend can be obtained from
http://horman.net/multiblend/


  Regards,
   Fernando Toledo
-- 
Fernando Toledo
Dock Sud BBS
http://bbs.docksud.com.ar
telnet://bbs.docksud.com.ar

Bug#911778: bash: I would like to be able to disable v which runs $EDITOR.

[Jim Lebeau]

Package: bash
Version: 4.4-5
Severity: wishlist

Dear Maintainer,
I use vi a great deal and so press escape a great deal. (often when I 
shouldn't)  If I plan to run vi again I then type v.  The results are not 
pleasing. I have been known to say bad words.
I never use the "edit-and-execute" feature, and would prefer that 
v ignore the escape, place a v where appropriate, and leave readline in 
input mode. If that is too much, if it would just leave readline in input mode 
would be bette than now.
I set EDITOR=false as a workaround, but that breaks reportbug among 
other things.

Thanks,

Jim

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

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

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


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

Kernel: Linux 4.9.0-6-amd64 (SMP w/1 CPU core)
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 bash depends on:
ii  base-files   9.9+deb9u5
ii  dash 0.5.8-2.4
ii  debianutils  4.8.1.1
ii  libc62.24-11+deb9u3
ii  libtinfo56.0+20161126-1+deb9u2

Versions of packages bash recommends:
ii  bash-completion  1:2.1-4.3

Versions of packages bash suggests:
pn  bash-doc  

-- Configuration Files:
/etc/bash.bashrc changed:
[ -z "$PS1" ] && return
shopt -s checkwinsize
if [ -z "${debian_chroot:-}" ] && [ -r /etc/debian_chroot ]; then
debian_chroot=$(cat /etc/debian_chroot)
fi
PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
if [ -x /usr/lib/command-not-found -o -x 
/usr/share/command-not-found/command-not-found ]; then
function command_not_found_handle {
# check because c-n-f could've been removed in the meantime
if [ -x /usr/lib/command-not-found ]; then
   /usr/lib/command-not-found -- "$1"
   return $?
elif [ -x /usr/share/command-not-found/command-not-found ]; then
   /usr/share/command-not-found/command-not-found -- "$1"
   return $?
else
   printf "%s: command not found\n" "$1" >&2
   return 127
fi
}
fi
export EDITOR=vi
alias l='ls -h -lA'


-- no debconf information

Bug#865086: xen-hypervisor-4.8-amd64: Default grub entry broken with locales (how to reproduce)

[Hans van Kranenburg]

Hi,

Can anyone explain me how I can reproduce this failure, and how exactly
I can verify the fix? From a QA POV I'd like to verify this before
applying. I don't have a lot of experience with gettext.

What I did to test is (buster dom0 with latest xen 4.11 from unstable):

-# dpkg-reconfigure locales
   -> also select nl_NL.UTF-8 UTF-8
   -> choose nl_NL.UTF-8 as default instead of en_US.UTF-8

-# apt-get update
[...]
10,9 kB opgehaald in 1s (7523 B/s)
Pakketlijsten worden ingelezen... Klaar

Ok, that looks dutch.

-# update-grub
Generating grub configuration file ...
[...]
done

-# grep Xen /boot/grub/grub.cfg |sed 's/ --class.*//;s/\$menuentry.*//'
   set default="Debian GNU/Linux, with Xen hypervisor"
menuentry 'Debian GNU/Linux, with Xen hypervisor'
echo'Loading Xen 4.11-amd64 ...'
submenu 'Advanced options for Debian GNU/Linux (with Xen hypervisor)'
submenu 'Xen hypervisor, version 4.11-amd64'
menuentry 'Debian GNU/Linux, with Xen 4.11-amd64 and Linux 
4.18.0-2-amd64'
echo'Loading Xen 4.11-amd64 ...'
menuentry 'Debian GNU/Linux, with Xen 4.11-amd64 and Linux 
4.18.0-1-amd64'
echo'Loading Xen 4.11-amd64 ...'
submenu 'Xen hypervisor, version 4.11-amd64.efi'
menuentry 'Debian GNU/Linux, with Xen 4.11-amd64.efi and Linux
4.18.0-2-amd64'
echo'Loading Xen 4.11-amd64.efi ...'
menuentry 'Debian GNU/Linux, with Xen 4.11-amd64.efi and Linux
4.18.0-1-amd64'
echo'Loading Xen 4.11-amd64.efi ...'
submenu 'Xen hypervisor, version 4.11-amd64.config'
menuentry 'Debian GNU/Linux, with Xen 4.11-amd64.config and 
Linux
4.18.0-2-amd64'
echo'Loading Xen 4.11-amd64.config ...'
menuentry 'Debian GNU/Linux, with Xen 4.11-amd64.config and 
Linux
4.18.0-1-amd64'
echo'Loading Xen 4.11-amd64.config ...'

So, as a result of applying this patch, I would like to see all of this
translated in Dutch.

At this point, the first thing I want to test is if I can see that the
gettext commands give me dutch output for things:

-# env |grep LANG
LANG=nl_NL.UTF-8

-# printf "$(gettext "%s, with Xen hypervisor")" "Debian GNU/Linux"
Debian GNU/Linux, with Xen hypervisor

-# dpkg -L grub-common |grep -i nl
/usr/share/locale/nl
/usr/share/locale/nl/LC_MESSAGES
/usr/share/locale/nl/LC_MESSAGES/grub.mo

-# strings /usr/share/locale/nl/LC_MESSAGES/grub.mo |grep Xen
%s, with Xen %s and Linux %s
%s, with Xen hypervisor
Advanced options for %s (with Xen hypervisor)
Check if FILE can be booted as i386 PAE Xen unprivileged guest kernel
Check if FILE can be booted as x86_64 Xen unprivileged guest kernel
Check if FILE can be used as Xen x86 privileged guest kernel
List Xen storage.
Loading Xen %s ...
Xen hypervisor, version %s
you need to load the Xen Hypervisor first
%s, met Xen %s en Linux %s
%s, met Xen-hypervisor
Geavanceerde opties voor %s (met Xen-hypervisor)
Controleren of BESTAND als ongeprivilegieerde i386-PAE-Xen-gast-kernel
gestart kan worden
Controleren of BESTAND als ongeprivilegieerde x86_64-Xen-gast-kernel
gestart kan worden
Controleren of BESTAND als geprivilegieerde x86-Xen-gast-kernel gebruikt
kan worden
Xen-opslag tonen.
Een Xen-hypervisor laden.
Een Xen-module laden.
Laden van Xen %s...
Xen-hypervisor, versie %s
u dient eerst de Xen-hypervisor te laden

Ok, so those are the translations that I can get...

What am I doing wrong, so that the first test already doesn't give me:
"Debian GNU/Linux, met Xen-hypervisor"

Thanks,
Hans

Bug#905090: wine-development: Causing SEGV when using Qt.

[Bernhard Übelacker]

Hello all,
to upstream git this patch [1] got just committed.

I repeated my tests from message #25 with
wine-development version 3.18  and found:

- Debian packages show still that exact crash.
- A local rebuilt package show that crash too.
- A local rebuilt package with just patch applied does not crash.

Therefore I assume this bug might be closed with
the next package version 3.19.

Kind regards,
Bernhard

[1] 
https://source.winehq.org/git/wine.git/commit/4e122bdaddf1a1c6d6211b5d7ce412b23a6efe57

Bug#749991: A tiresome subject for YEARS.

[John Paul Adrian Glaubitz]

On 10/24/18 6:42 PM, Oliver Riesener wrote:
> No unetbootin, it’s the stock  stretch netboot   installation.
> initrd kernel from actual Debian9.5/…./amd64/netboot/netboot.tar.gz
> didn’t find kernel modules anymore. The old one before too. 
> It’s a point release problem. Older versions of modules (.udeb ?) seems
> to be from debian repo. 
Are you sure you used a matching kernel image and initrd? Both have to match
their version otherwise it won't work.

I'm creating debian-installer images myself on a regular basis and from my
current knowledge and testing, it's very unlikely that there is a bug in
the kernel and initrd matching.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#911777: iptables: ferm broken by changed path of iptables-restore

[Cesare Leonardi]

Package: iptables
Version: 1.8.1-1
Severity: normal

After the upgrade from 1.6.2-1.1 to 1.8.1-1, ferm firewall cannot start
anymore, because it doesn't find /sbin/iptables-restore.
Now iptables programs are all under /usr/sbin (with the exception of
iptables-xml under /usr/bin), while in 1.6.2 many executables where
under /sbin.
Perhaps some compatibility symlinks should be placed there.

Cesare.

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

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

Versions of packages iptables depends on:
ii  libc62.27-6
ii  libip4tc01.8.1-1
ii  libip6tc01.8.1-1
ii  libiptc0 1.8.1-1
ii  libmnl0  1.0.4-2
ii  libnetfilter-conntrack3  1.0.7-1
ii  libnfnetlink01.0.1-3+b1
ii  libnftnl71.1.1-1
ii  libxtables12 1.8.1-1

iptables recommends no packages.

Versions of packages iptables suggests:
ii  kmod  25-1

-- no debconf information

Bug#749991: A tiresome subject for YEARS.

[Oliver Riesener]

No unetbootin, it’s the stock  stretch netboot   installation.
initrd kernel from actual Debian9.5/…./amd64/netboot/netboot.tar.gz
didn’t find kernel modules anymore. The old one before too. 
It’s a point release problem. Older versions of modules (.udeb ?) seems
to be from debian repo. 


> Am 24.10.2018 um 17:26 schrieb John Paul Adrian Glaubitz 
> :
> 
> On 10/24/18 5:15 PM, Oliver Riesener wrote:
>> Debian Stretch 9.5 (stable) kernel 3.16.0-4
>> * no packages matching kernel failed.
> 
> This error usually comes up with installation media created using
> unetbootin. Have you, by any chance, used unetbootin to create your
> installation medium?
> 
> Adrian
> 
> -- 
> .''`.  John Paul Adrian Glaubitz
> : :' :  Debian Developer - glaub...@debian.org
> `. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
>  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
> 

Bug#911773: RFS (team upload): golang-github-rivo-tview/0.0~git20181018.a7c1880-1 [ITP]

[Jongmin Kim]

Thanks, Alexandre!

On Wed, Oct 24, 2018 at 12:17:49PM -0400, Alexandre Viau wrote:
> Why would you set builder and cleaner in debian/gbp.conf?
>
> It has nothing to do with the layout of the repository. It should be up
> to whoever maintains the package to decide how he wants to build it.

Yes, it can be personalisable. I removed it.

Many thanks for your careful review.

-- 
Jongmin Kim

OpenPGP key located at
https://jmkim-pgp.github.io/keys/pubkey.D39D8D29BAF36DF8.Jongmin_Kim.asc
OpenPGP fingerprint: 012E 4A06 79E1 4EFC DAAE  9472 D39D 8D29 BAF3 6DF8


signature.asc
Description: PGP signature

Bug#839008: scribus no longer finds DejaVu fonts

[Mattia Rizzolo]

Control: reassign -1 libfreetype6 2.6.3-3.2
Control: fixed -1 2.7.1-0.1
Control: affects -1 scribus

On Fri, Nov 24, 2017 at 12:45:46AM +0100, Hartmut Buhrmester wrote:
> Apparently, this is caused by a bug in the FreeType library libfreetype6. An
> upstream bug report says:
> 
> > This is a bug caused by some FreeType versions which fail when loading
> > some glyphs outlines and make us consider some fonts as broken. At
> > least FreeType 2.6.0 to 2.6.3 are affected. FreeType 2.6.5 was
> > fixed. Unfortunately Debian 9 has FreeType 2.6.3. If you upgrade
> > FreeType to >= 2.6.5, you will have to clear scribus font cache.
> 
> - https://bugs.scribus.net/view.php?id=15042

As such, I'm reassign this bug report to freetype.

I don't know whether its maintainer have enough time to go through the
process to find the minimal fix and do a stable update though.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#911776: fontconfig: makes Firefox, Gimp, Inkscape occasionally freeze

[Francesco Potortì]

Package: fontconfig
Version: 2.13.0-5
Severity: grave

Details are reported in bug #909818

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

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

Versions of packages fontconfig depends on:
ii  fontconfig-config  2.13.1-1
ii  libc6  2.27-6
pn  libfontconfig1 
ii  libfreetype6   2.8.1-2

fontconfig recommends no packages.

fontconfig suggests no packages.

-- no debconf information

Bug#911775: Please package Elixir >= 1.6.6

[Thomas Goirand]

Source: elixir
Severity: normal

Dear Maintainer,

I'm packaging RabbitMQ-server, and the latest upstream release needs
Elixir 1.6.6 at least. It'd be nice if you could update the package.

Cheers,

Thomas Goirand (zigo)

Bug#911773: RFS (team upload): golang-github-rivo-tview/0.0~git20181018.a7c1880-1 [ITP]

[Alexandre Viau]

Forgot to CC debian-go.

On 2018-10-24 12:16 p.m., Alexandre Viau wrote:
> On 2018-10-24 11:55 a.m., Jongmin Kim wrote:
>> I am looking for a sponsor for my package "golang-github-rivo-tview".
> 
> Why would you set builder and cleaner in debian/gbp.conf?
> 
> It has nothing to do with the layout of the repository. It should be up
> to whoever maintains the package to decide how he wants to build it.
> 
> If you want to build all your packages with pbuilder, please set it in
> ~/.gbp.conf instead.
> 

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#911774: O: xview -- XView shared libraries

[Mattia Rizzolo]

Package: wnpp

The current maintainer of xview, Blars Blarson ,
is apparently not active anymore.  Therefore, I orphan this package now.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
https://www.debian.org/devel/wnpp/#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: xview
Binary: xviewg, xviewg-dev, xview-clients, xview-examples, olwm, olvwm
Version: 3.2p1.4-28.2
Maintainer: Blars Blarson 
Build-Depends: debhelper (>= 5), bison, libfl-dev, ed, libncurses5-dev | 
libncurses-dev, libx11-dev (>= 2:1.0.0), libxt-dev, libxext-dev, libxpm-dev, 
xutils-dev
Architecture: any
Standards-Version: 3.8.0.0
Format: 3.0 (quilt)
Files:
 4f1b6dd7eb789984019d14c35a99084f 2029 xview_3.2p1.4-28.2.dsc
 b9ff26d6ad378af320bac45154ceaeba 3227552 xview_3.2p1.4.orig.tar.gz
 965e46a364ab73fd0ccf52d604edd174 82124 xview_3.2p1.4-28.2.debian.tar.xz
Checksums-Sha256:
 1c904036e7afa1487ec8f90ebf078150076fe9d3621fb958250141a87dd88ec1 2029 
xview_3.2p1.4-28.2.dsc
 fcc88f884a6cb05789ed800edea24d9c4cf1f60cb7d61f3ce7f10de677ef9e8d 3227552 
xview_3.2p1.4.orig.tar.gz
 c84f18a588b848a95f2fed08c3d0514e96792408ebf8120e53e585efd3045f96 82124 
xview_3.2p1.4-28.2.debian.tar.xz
Package-List: 
 olvwm deb x11 optional arch=any
 olwm deb x11 optional arch=any
 xview-clients deb x11 optional arch=any
 xview-examples deb x11 optional arch=any
 xviewg deb x11 optional arch=any
 xviewg-dev deb devel optional arch=any
Directory: pool/main/x/xview
Priority: source
Section: x11

Package: xviewg
Source: xview
Version: 3.2p1.4-28.2
Installed-Size: 1995
Maintainer: Blars Blarson 
Architecture: amd64
Depends: libc6 (>= 2.14), libx11-6, libxext6, xbitmaps
Pre-Depends: x11-common (>= 1:7.0.0)
Suggests: indent
Conflicts: xview (<< 3.2p1.4-1)
Description: XView shared libraries
Description-md5: 0e5206021e9a2582a115e4c7894a9afc
Tag: devel::library, interface::graphical, interface::x11, role::program,
 scope::utility, use::viewing, works-with::image,
 works-with::image:raster, x11::application
Section: x11
Priority: optional
Filename: pool/main/x/xview/xviewg_3.2p1.4-28.2_amd64.deb
Size: 654124
MD5sum: bed6f0025244390c20492f8d36103358
SHA256: 5181e3369fd6f48d7886a3158c413c1422da946478009cce525c9f3c697aa104

Package: xviewg-dev
Source: xview
Version: 3.2p1.4-28.2
Installed-Size: 3916
Maintainer: Blars Blarson 
Architecture: amd64
Depends: xviewg (= 3.2p1.4-28.2), libc6 (>= 2.2.5), libx11-dev
Pre-Depends: x11-common (>= 1:7.0.0)
Conflicts: xview-dev (<< 3.2p1.4-1)
Description: XView development tools
Description-md5: da1e4e1ebe66398a922308862e377aaf
Tag: devel::library, interface::graphical, interface::x11, role::devel-lib,
 role::program, use::viewing, works-with::image,
 works-with::image:raster, x11::application
Section: devel
Priority: optional
Filename: pool/main/x/xview/xviewg-dev_3.2p1.4-28.2_amd64.deb
Size: 883622
MD5sum: 3bfcfb1fa95953d48b9a0d504593598a
SHA256: 6235308e3b9330f2a027e6e167fc6e4d4eae392e28e234e4e8481ba99825c304

Package: xview-clients
Source: xview
Version: 3.2p1.4-28.2
Installed-Size: 196
Maintainer: Blars Blarson 
Architecture: amd64
Depends: libc6 (>= 2.14), libx11-6, libxext6, xviewg (>= 3.2p1.4-6)
Description: XView client programs
Description-md5: 80414ece9f4573d68466143adb9353c9
Tag: interface::graphical, interface::x11, role::program, scope::utility,
 use::configuring, use::editing, use::timekeeping, works-with::text,
 x11::application, x11::terminal
Section: x11
Priority: optional
Filename: pool/main/x/xview/xview-clients_3.2p1.4-28.2_amd64.deb
Size: 67512
MD5sum: 0a3f9a2c5a22b84f3719c892e443b1f8
SHA256: 73a11ac5532cadfcd3630294d7d35858797aaede07250ddaee305df39fd547f7

Package: xview-examples
Source: xview
Version: 3.2p1.4-28.2
Installed-Size: 1473
Maintainer: Blars Blarson 
Architecture: amd64
Depends: libc6 (>= 2.14), libncurses5 (>= 6), libtinfo5 (>= 6), libx11-6, 
libxext6, xviewg (>= 3.2p1.4-6)
Recommends: xviewg-dev, xutils-dev
Description: XView contrib programs
Description-md5: 67cef80319a653e89c65b3940e9f63ca
Tag: devel::examples, interface::graphical, interface::x11, role::app-data,
 role::program, role::source, uitoolkit::ncurses, x11::application
Section: x11
Priority: optional
Filename: pool/main/x/xview/xview-examples_3.2p1.4-28.2_amd64.deb
Size: 178020
MD5sum: 474ba74f1560cd320453984788e95056
SHA256: bd4fd087d5e60f2c6c52aadc0d981520ed4e0f541b3c874bfe94baa5f976cb9c

Package: olwm
Source: xview
Version: 3.2p1.4-28.2
Installed-Size: 371
Maintainer: Blars Blarson 
Architecture: amd64
Provides: x-window-manager
Depends: libc6 (>= 2.14), libx11-6, libxext6, xviewg (>= 3.2p1.4-6)
Suggests: menu (>= 2.1.9), xview-clients
Conflicts: menu (<< 2.1.9), olvwm (<< 4.1.3.2p1.4-1), xview (<< 3.2p1.4-1)
Description: Open Look Window Manager
Description-md5: d0d4334f3b466b34d03687a9faea5982
Tag: interface::graphical, interface::x11, 

Bug#911773: RFS (team upload): golang-github-rivo-tview/0.0~git20181018.a7c1880-1 [ITP]

[Alexandre Viau]

On 2018-10-24 12:17 p.m., Alexandre Viau wrote:
> Forgot to CC debian-go.
> 
> On 2018-10-24 12:16 p.m., Alexandre Viau wrote:
>> On 2018-10-24 11:55 a.m., Jongmin Kim wrote:
>>> I am looking for a sponsor for my package "golang-github-rivo-tview".
>>
>> Why would you set builder and cleaner in debian/gbp.conf?
>>
>> It has nothing to do with the layout of the repository. It should be up
>> to whoever maintains the package to decide how he wants to build it.

And here I meant "whoever builds the package"

>> If you want to build all your packages with pbuilder, please set it in
>> ~/.gbp.conf instead.
>>
> 

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#911773: RFS (team upload): golang-github-rivo-tview/0.0~git20181018.a7c1880-1 [ITP]

[Alexandre Viau]

On 2018-10-24 11:55 a.m., Jongmin Kim wrote:
> I am looking for a sponsor for my package "golang-github-rivo-tview".

Why would you set builder and cleaner in debian/gbp.conf?

It has nothing to do with the layout of the repository. It should be up
to whoever maintains the package to decide how he wants to build it.

If you want to build all your packages with pbuilder, please set it in
~/.gbp.conf instead.

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#911773: RFS (team upload): golang-github-rivo-tview/0.0~git20181018.a7c1880-1 [ITP]

[Jongmin Kim]

Control: block 905240 by -1

-- 
Jongmin Kim

OpenPGP key located at
https://jmkim-pgp.github.io/keys/pubkey.D39D8D29BAF36DF8.Jongmin_Kim.asc
OpenPGP fingerprint: 012E 4A06 79E1 4EFC DAAE  9472 D39D 8D29 BAF3 6DF8


signature.asc
Description: PGP signature

Bug#908064: diaspora-installer: please update to 0.7.6.0

[Gianfranco Costamagna]

control: tags -1 patch pending
On Wed, 5 Sep 2018 20:25:05 +0200 Gianfranco Costamagna 
 wrote:
> Source: diaspora-installer
> Version: 0.7.4.0+nmu1
> Severity: important
> Tags: patch
> 
> This new release drops sigar, that is unmaintained and FTBFS with glibc
> 2.28
> 
> I might NMU later this month or next one, because this will become RC once 
> glibc 2.28 goes in unstable.
> 

in deferred/15
(I don't use the NMU syntax because I don't want to mess up the rules file 
parsing of the versioning)

G.
> Thanks for caring, I'm attaching a diff right now (note: I can't test on 
> pbuilder, so I presume
> the fix works by the fact that the testsuite is now completely green)
> 
> thanks
> 
> Gianfranco

Bug#827337: apt-show-versions: option to hide packages that are at the right version based on pinning upgradeable

[Antoine Beaupré]

On 2016-06-15 13:44:50, Paul Wise wrote:
> Package: apt-show-versions
> Version: 0.22.7
> Severity: wishlist
>
> I pin most packages to testing and then have progressively lower pin
> values for less desirable suites. I also pin some particular packages
> to other suites. I also pin security updates using the script in bug
> #725934 to the suite that they come from (mostly unstable). I would
> like to have an option to hide packages that are at the right version
> based on pinning. So for most packages, hide if they are the version in
> testing. For specific packages pinned to a different release, hide if
> they are the version from the pinned release. For security updates
> pinned to unstable release, hide if they are the version from unstable.

I have a similar requirement, at least I think it is. I'm running
testing and pin some packages to "unstable until it hits testing". For
example, I have this for Firefox right now:

Package: firefox-esr
Pin: release n=sid
Pin-Priority: 501

Package: firefox-esr
Pin: release n=buster
Pin: release v=60
Pin-Priority: 502

It gives me a quantum-enabled firefox in buster, from sid, but will
transition to the buster version when it makes it. I also manually
install some packages from sid that are missing from buster in the hope
they transition.

I use apt-show-versions to keep track of those transitions. This
requires me to add a filter to hide "uptodate" entries from
"buster". For example, here's the output I am looking at right now:

$ apt-show-versions  | grep -v '/buster [^ ]* uptodate'
firefox-esr:amd64/sid 60.3.0esr-1 uptodate
network-manager-iodine:amd64/sid 1.2.0-3 uptodate
network-manager-iodine-gnome:amd64/sid 1.2.0-3 uptodate
printer-driver-postscript-hp:amd64 not installed
python-hvac:amd64 0.6.4-1 installed: No available version in archive
wireguard:all/sid 0.0.20181018-1 uptodate
wireguard-dkms:all/sid 0.0.20181018-1 uptodate
wireguard-tools:amd64/sid 0.0.20181018-1 uptodate

The first three and last three are normal there: both firefox-esr,
wireguard, and nm-iodine have excuses for not migrating to testing. The
`not installed` bit doesn't belong there but that's #783781. The
python-hvac one is interesting: it's a package that is currently in WNPP
(#875603) that I've worked on. Hopefully it will get there as well.

So that's really nice, but I always forget that cute regex. I wished
there was a way to simply add an option to get that clean output. I
tried this patch:

diff --git i/apt-show-versions w/apt-show-versions
index 3df13c7..6266b10 100755
--- i/apt-show-versions
+++ w/apt-show-versions
@@ -79,6 +79,7 @@ unless (GetOptions (\%opts,
 'upgradeable|u',
 'brief|b',
 'nohold|nh',
+'nouptodate|nu',
 'initialize|i',
 'verbose|v',
'version|V',
@@ -143,6 +144,7 @@ Options:
  -a|--allversions   Print all available versions.
  -b|--brief Short output.
  -nh|--nohold   Don't treat holded packages.
+ -nu|--nouptodate   Don't display up to date packages.
  -i|--initializeInitialize or update package cache only (as root).
  -v|--verbose   Verbose messages.
  -V|--version  Prints apt-show-versions version
@@ -458,7 +460,9 @@ sub print_package_internal {
 ($found, @version_info) =
_version(($irelease ? $irelease : 
_rel_name($_->{$RELEASE})),
$pkgarch, $iversion, $version, $cand);
-push @print_info, @version_info if ($found);
+if ($found and ($found != 1 or !$opts{'nouptodate'})) {
+push @print_info, @version_info;
+}
 $aversion = $version;
 }
 $is_upgradeable = 1 if ($found == 2);

But that doesn't give the right output:

$ ./apt-show-versions --nouptodate
python-hvac:amd64 0.6.4-1 installed: No available version in archive

Obviously, it removes just all uptodate packages, regardless of
suite. There should be a way to figure out if the found release (the
$irelease thing above) is the default release, but unfortunately
apt-show-versions does not have a good notion of what that is. It only
relies on APT::Default-Release (#875603) and that's usually not defined.

What *is* the proper way of figuring out what the default release is? Or
should we have a --ignore flag that would ignore a certain suite?

So I'm not sure if there's a clean way of fixing this.

A.

-- 
No animal has more liberty than the cat; but it buries the mess it
makes. The cat is the best anarchist. Until they learn that from the cat
I cannot respect them.
- For whom the bell tolls, Ernest Hemingway

Bug#911617: nm.debian.org: AM's profile says "0 applicants processed"

[Mattia Rizzolo]

On Mon, Oct 22, 2018 at 12:34:06PM -0400, Alexandre Viau wrote:
> I have processed two applicants and their process status is now "Closed".
> 
> However, my AM profile still says "0 applicants processed".


In [1]: import backend.models as bmodels

In [2]: from django.db.models import Min, Max

In [3]: am = 
bmodels.AM.objects.get(person=bmodels.Person.objects.get(uid='aviau'))

In [4]: am
Out[4]: b'Alexandre Viau'  [uid:aviau, status:dd_u] a-- 
slots:1

In [5]: am.processed.annotate(started=Min("log__logdate"), 
ended=Max("log__logdate")).order_by('is_active', 'ended')
Out[5]: 

this is what the code does, and as you can see apparently it believes
you processed nobody there.

In [17]: import process.models as pmodels

In [18]: pmodels.Process.objects.filter(ams__am=am).distinct()
Out[18]:  to 
become dd_u>,  to 
become dd_u>,  to become 
dd_u>]>

here instead it finds the 3 applicants by you, which are properly listed
in the table in your profile.


tbh I can't really see where that "processed" property is coming from,
so I'm unable to follow it for now.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#804099: apt-xapian-index and Python 3

[Dino]

Hi,

I just realised that update-apt-xapian-index is not working if 
/usr/bin/python is pointing to a Python 3 interpreter. It gives the 
following error:


  File "/usr/sbin/update-apt-xapian-index", line 86
    except OSError, e:
  ^
SyntaxError: invalid syntax


Thus, I guess the changes mentioned above have not been incorporated 
into the code. (The links are not working anymore...)


What do you think about changing the shebang line to:
#!/usr/bin/python2
?

Best,
Dino

Bug#911773: RFS (team upload): golang-github-rivo-tview/0.0~git20181018.a7c1880-1 [ITP]

[Jongmin Kim]

Package: sponsorship-requests
Severity: wishlist
Control: -1 block 905240
X-Debbugs-CC: debian...@lists.debian.org, av...@debian.org

Dear mentors,

I am looking for a sponsor for my package "golang-github-rivo-tview".

This package is a prerequisite for upcoming package "git-lab" (#898246).

This package will be maintained as part of the Go Packaging Team going forward.

* Package name: golang-github-rivo-tview
  Version : 0.0~git20181018.a7c1880-1
  Upstream Author : Oliver Kuederle 
* URL : https://github.com/rivo/tview
* License : Expat
  Section : devel

It builds those binary packages:

  golang-github-rivo-tview-dev - Rich interactive widgets for terminal-based 
UIs in Go

If you have access to Salsa, please check out:

  https://salsa.debian.org/go-team/packages/golang-github-rivo-tview

Otherwise, please visit the following URL (You can also find the orig.tar.gz 
here):

  https://mentors.debian.net/package/golang-github-rivo-tview

Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/g/golang-github-rivo-tview/golang-github-rivo-tview_0.0~git20181018.a7c1880-1.dsc

Thanks for your time! Any review is appreciated.

Regards,
 Jongmin Kim

-- 
Jongmin Kim

OpenPGP key located at
https://jmkim-pgp.github.io/keys/pubkey.D39D8D29BAF36DF8.Jongmin_Kim.asc
OpenPGP fingerprint: 012E 4A06 79E1 4EFC DAAE  9472 D39D 8D29 BAF3 6DF8


signature.asc
Description: PGP signature

Bug#909926: No more segfaulting with 0.7.8-1

[Ritesh Raj Sarraf]

Hello Hans,

On Wed, 2018-10-24 at 17:42 +0200, Hans van Kranenburg wrote:
> Hi,
> 
> Just a success report from a user:
> 
> I've been seeing this in dmesg on buster previously, every time
> during boot:
> 
> [   37.091372] multipath[530]: segfault at 100 ip 7fdc202b6136 sp
> 7ffdf8d740d8 error 4 in libc-2.27.so[7fdc20241000+146000]
> 
> I found this bug report yesterday, and saw that you just uploaded
> 0.7.8-1.
> 
> So, today I installed it and the segfault doesn't show up any more.

THank you for your test report. Much appreciated.

Ritesh

-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System


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

Bug#826994: ZFS Missing init-scripts, Status? #826994

[Chris Dos]

Hello Aron,

I would just like to get a final statement from you regarding if this patch is
going to be applied or not?

If this sysvinit bug is going to forever remain a wishlist and never have the
patch applied, then say so and I'll make other arrangements and no longer
maintain the patch.

Chris

Bug#783781: apt-show-versions: shows "foo:all not installed" for packages that transitioned from arch any to arch all

[Antoine Beaupré]

On 2015-04-30 08:27:20, Paul Wise wrote:
> The packages apertium-en-es, proj-data and wml have transitioned from
> Architecture: any in unstable to Architecture: all in experimental. I
> have the unstable versions installed but not the experimental ones and
> apt-show-versions shows "foo:all not installed" for all of them. This is
> confusing since apt-show-versions is meant to only show installed stuff.
>
> apertium-en-es:all not installed
> apertium-en-es:amd64/testing 0.6.0-1.1+b2 uptodate
> proj-data:all not installed
> proj-data:amd64/testing 4.8.0-5 uptodate
> wml:all not installed
> wml:amd64/testing 2.0.12ds1-8 uptodate

It seems like this is deliberate in the code, yet it's totally unclear
to me why it's happening. The following patch, of course, fixes the
problem:

diff --git i/apt-show-versions w/apt-show-versions
index 3df13c7..ab1f91c 100755
--- i/apt-show-versions
+++ w/apt-show-versions
@@ -513,7 +513,7 @@ sub print_package_internal {
  "version in archive\n");
 }
 }
-} else {
+} elsif ($ipkg->{$VERS}) {
 push(@print_info, "$pkgarch not installed",
  ($mode == $MODE_SINGLE and not 
keys(%{$apackages->{$package}{$arch}}))
 ? " (even not available)\n" : "\n");

But it's not clear to me what the proper solution is or what the purpose
of this 'not installed' statement is... That code has been present
basically forever (since the 2007, 0.10 original git import) without any
clear explanation.

Another alternative would be to just remove that code completely, since
it's unclear what purpose it serves. This is basically what the above
does anyways.

Other opinions?

A.

-- 
Growth for the sake of growth is the ideology of the cancer cell.
- Edward Abbey

Bug#909926: No more segfaulting with 0.7.8-1

[Hans van Kranenburg]

Hi,

Just a success report from a user:

I've been seeing this in dmesg on buster previously, every time during boot:

[   37.091372] multipath[530]: segfault at 100 ip 7fdc202b6136 sp
7ffdf8d740d8 error 4 in libc-2.27.so[7fdc20241000+146000]

I found this bug report yesterday, and saw that you just uploaded 0.7.8-1.

So, today I installed it and the segfault doesn't show up any more.

Thanks!

Hans

Bug#894359: Now we have antlr 4.6 - any chance to get 4.7 soon (Was: beast-mcmc2: Cannot find symbol CharStreams.fromString(newick))

[Andrius Merkys]

On 10/24/18 1:40 PM, Emmanuel Bourg wrote:
> I've uploaded mojo-executor and string-template-maven-plugin, they are
> awaiting in the NEW queue for the FTP masters approval. Thanks a lot
> Andrius.

Many thanks for reviewing and uploading the packages!

Best,
Andrius