Bug#873120: 389-ds-base: FTBFS on various architectures: test_plugin_pwdstorage_pbkdf2_rounds fails

[James Cowgill]

Source: 389-ds-base
Version: 1.3.6.7-2
Severity: serious
Tags: sid buster

Hi,

389-ds-base FTBFS on various architectures (including armel, i386 and
mips) with this error:
> [==] Running 3 test(s).
> [ RUN  ] test_plugin_hello
> [   OK ] test_plugin_hello
> [ RUN  ] test_plugin_pwdstorage_pbkdf2_auth
> [   OK ] test_plugin_pwdstorage_pbkdf2_auth
> [ RUN  ] test_plugin_pwdstorage_pbkdf2_rounds
> [  ERROR   ] --- pbkdf2_sha256_calculate_iterations(1) == 2
> [   LINE   ] --- ../test/plugins/pwdstorage/pbkdf2.c:70: error: Failure!
> [  FAILED  ] test_plugin_pwdstorage_pbkdf2_rounds
> [==] 3 test(s) run.
> [  PASSED  ] 2 test(s).
> [  FAILED  ] 1 test(s), listed below:
> [  FAILED  ] test_plugin_pwdstorage_pbkdf2_rounds

This happens because the prototype of the
pbkdf2_sha256_calculate_iterations function:
> ldap/servers/plugins/pwdstorage/pwdstorage.h
> 95:PRUint32 pbkdf2_sha256_calculate_iterations();

does not match the type of the definition:
> ldap/servers/plugins/pwdstorage/pbkdf2_pwd.c
> 261:pbkdf2_sha256_calculate_iterations(uint64_t time_nsec)

When the test calls this function with an integer argument, the "default
integer promotions" will apply promoting it to an int. Therefore on
every architecture where int != uint64_t (pretty much everything), this
function call will invoke undefined behavior by having the wrong
argument types.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#869667: stretch-pu: package xkeyboard-config/2.19-1

[Pirate Praveen]

On വ്യാഴം 24 ആഗസ്റ്റ് 2017 09:46 വൈകു, Cyril Brulebois wrote:
> Great thing that point releases usually happen once every 3 months, right?
> 
> Anyway: right now, D-I Buster Alpha 1 has the priority; point release
> material can definitely wait.

But it is blocking everyone, as it can't go into updates without your
ack. Packages in stretch/updates are available immediately to users once
it enters the archive.



signature.asc
Description: OpenPGP digital signature

Bug#682347: mark 'editor' virtual package name as obsolete

[Christoph Berg]

Re: To Russ Allbery 2017-08-24 <20170824171653.r24gyar5mikyj...@msg.df7cb.de>
> $ grep-dctrl -F Provides editor -nsPackage 
> /var/lib/apt/lists/deb_debian_dists_sid_main_binary-amd64_Packages | xargs
> deutex edbrowse emacs25 emacs25-lucid emacs25-nox fte-console
> fte-terminal fte-xwindow jed xjed jove jupp le ledit levee lpe mg
> xul-ext-password-editor nano nano-tiny ne pluma rlfe rlwrap scite
> vigor vile xvile vim vim-athena vim-gtk vim-gtk3 vim-nox vim-tiny vis
> xul-ext-exteditor

There are some false positives in that list (deutex, ledit, pluma,
rlwrap, xul-ext-exteditor; "Provides: readline-editor" and similar),
but the list is still pretty long, I'd conclude.

Christoph

Bug#682347: mark 'editor' virtual package name as obsolete

[Christoph Berg]

Re: Russ Allbery 2017-08-24 <87efs1lyc7@hope.eyrie.org>
> Oh, thank you!  For some reason, apt-cache rdepends didn't show any of
> those packages.  All of them except dnsvi are Suggests, which basically
> doesn't accomplish anything.
> 
> Copying myon on this message as maintainer of dnsvi, which has a
> dependency on "vim | editor".  Christoph, we're proposing finally removing
> the editor virtual package completely, with the patch included here:

Thanks for the notice. I'm quite surprised that my dnsvi seems to be
the only package in Debian that requires a text editor. Given that our
base doesn't really include one, and getting dependencies Just Right
is among the things that Debian is really good at, dropping the
existing "editor" virtual package seems Just Wrong to me.

Even if "editor" was de-officialized in 1996, it is very much used
today. Bill's original list from 2015 was incomplete (it is much
longer now, but given that even emacs was missing, I'd think the grep
command used back then was wrong):

$ grep-dctrl -F Provides editor -nsPackage 
/var/lib/apt/lists/deb_debian_dists_sid_main_binary-amd64_Packages | xargs
deutex edbrowse emacs25 emacs25-lucid emacs25-nox fte-console
fte-terminal fte-xwindow jed xjed jove jupp le ledit levee lpe mg
xul-ext-password-editor nano nano-tiny ne pluma rlfe rlwrap scite
vigor vile xvile vim vim-athena vim-gtk vim-gtk3 vim-nox vim-tiny vis
xul-ext-exteditor

Wouldn't it much better (cleaner, more correct, more userfriendly) to
promote "editor" to official status instead?

Christoph

Bug#872402: golang-golang-x-tools-dev: Does not work on mips*

[Shengjing Zhu]

Control: severity -1 normal

On Thu, Aug 24, 2017 at 10:37 PM, Martín Ferrari  wrote:
> Yes, sorry, I was confused with x/tools, which has disabled tests. This
> one does not get built in other arches, so the relevant tests are not
> executed.. Maybe we should make it arch:any...?
>

I think the CI like ci.d.n should run on more archs instead...

> Prometheus and friends were failing. I understood now what you are doing
> here (it took me a while), and by passing tags I managed to get them
> building again, but that's not a reasonable solution.. The packages
> should build out of the box. Can't you add the correct build
> restrictions for gccgo so we don't need the tags?

ok, so I read the issue on https://github.com/golang/go/issues/18031

I don't have mips env to verify comments by foka. But what foka said
in that issue is,
gccgo reports mipsel and mips both as `mipso32`. So we need pass
another `-tags` to distinguish the two archs.
Unless gccgo has corrent build tip, we can only manually add `-tags
mips` or `-tags mipsel`.

BTW, let me down grade this bug's severity first since I think we have
workaround for that :)

-- 
Best regards,
Shengjing Zhu

Bug#873119: graphicsmagick: CVE-2017-13065: null pointer dereference_in_SVGStartElement

[Salvatore Bonaccorso]

Source: graphicsmagick
Version: 1.3.26-5
Severity: important
Tags: security upstream patch
Forwarded: https://sourceforge.net/p/graphicsmagick/bugs/435/

Hi,

the following vulnerability was published for graphicsmagick.

CVE-2017-13065[0]:
| GraphicsMagick 1.3.26 has a NULL pointer dereference vulnerability in
| the function SVGStartElement in coders/svg.c.

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-2017-13065
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-13065
[1] https://sourceforge.net/p/graphicsmagick/bugs/435/

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#868773: khal FTBFS: AssertionError: assert not OSError(6, 'No such device or address')

[Guido Günther]

Hi,
On Tue, Jul 18, 2017 at 03:41:33PM +0300, Adrian Bunk wrote:
> Source: khal
> Version: 1:0.9.6-1
> Severity: serious
> 
> https://buildd.debian.org/status/fetch.php?pkg=khal=all=1:0.9.6-1=1500381224=0
> 
> ...
> === FAILURES 
> ===
>  test_import_from_stdin 
> 
> 
> runner = 
> 
> def test_import_from_stdin(runner):
> ics_data = 'This is some really fake icalendar data'
> 
> with mock.patch('khal.controllers.import_ics') as mocked_import:
> runner = runner()
> result = runner.invoke(main_khal, ['import'], input=ics_data)
> 
> >   assert not result.exception
> E   AssertionError: assert not OSError(6, 'No such device or address')
> E+  where OSError(6, 'No such device or address') =  OSError(6, 'No such device or address')>.exception
> 
> tests/cli_test.py:505: AssertionError
>  test_printics_read_from_stdin 
> _
> 
> runner = 
> 
> def test_printics_read_from_stdin(runner):
> runner = runner(command='printics')
> result = runner.invoke(main_khal, ['printics'], 
> input=_get_text('cal_d'))
> >   assert not result.exception
> E   AssertionError: assert not OSError(6, 'No such device or address')
> E+  where OSError(6, 'No such device or address') =  OSError(6, 'No such device or address')>.exception
> 
> tests/cli_test.py:683: AssertionError
> == 2 failed, 261 passed, 7 skipped, 3 xfailed in 9.52 seconds 
> ==
> E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd 
> /<>/.pybuild/pythonX.Y_3.6/build; python3.6 -m pytest tests
> dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.6 3.5 
> returned exit code 13
> debian/rules:26: recipe for target 'override_dh_auto_test' failed
> make[1]: *** [override_dh_auto_test] Error 25

Any chance this gets fixed? It would be great to have a recent khal in
unstable/testing.
 -- Guido

Bug#873118: commons-io: FTBFS: Several failed unit tests

[Miguel Landaeta]

Package: src:commons-io
Version: 2.5-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

[...]

Results :

Tests in error: 
  FileUtilsTestCase.testCopyDirectoryToDirectory_NonExistingDest:1323 ?? IO 
Unab...
  FileUtilsTestCase.testCopyDirectoryToExistingDest:1409 ?? IO Unable to delete 
...
  FileUtilsTestCase.testCopyDirectoryToNonExistingDest:1367 ?? IO Unable to 
dele...

Tests run: 1157, Failures: 0, Errors: 3, Skipped: 4

[INFO] 

[INFO] BUILD FAILURE
[INFO] 

[INFO] Total time: 02:01 min
[INFO] Finished at: 2017-08-24T09:16:19Z
[INFO] Final Memory: 14M/276M
[INFO] 

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test 
(default-test) on project commons-io: There are test 
failures.
[ERROR] 
[ERROR] Please refer to 
/<>/target/surefire-reports for the individual test results.
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with 
the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug 
logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, 
please read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
dh_auto_test: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo test returned exit code 1
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2


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

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

-- 
Miguel Landaeta, nomadium at debian.org
secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key.
"Faith means not wanting to know what is true." -- Nietzsche


commons-io_2.5-1_amd64-2017-08-24T09:13:55Z.build.gz
Description: application/gzip


signature.asc
Description: Digital signature

Bug#872867: is ISO-3166 really the optimal list for our users?

[Daniel Pocock]

On 24/08/17 18:02, Wouter Verhelst wrote:

> Case in point: why would Kosovo *need* to be on the d-i list of
> countries? Is there a difference between Kosovo and Serbia[1] or other
> countries in the former Yugoslavia that d-i would need to be aware of
> (such as locale settings, keyboard layout, time zone, or preferred
> mirror), or is this bug in fact just the result of people with a
> background of Kosovan nationalist ideology complaining about it to
> you[2]? So far I've only seen you argue that "Kosovo needs to be on the


Another consideration is the uncertainty:  for many ordinary users (not
necessarily people with strong political opinions) it is simply not
clear what the technical consequences will be if they select RS or AL
from the list.  Simply abolishing the list and asking people to manually
select a timezone may be one way to eliminate this uncertainty.

About 50% of the population is under 30[1] - many of them presumably
have no memory of being a Serbian or Yugoslavian, they have simply been
brought up as Kosovans.  This is also the age group where people are
likely to try free software.  I haven't observed any Kosovan taking up
arms when they see the country list, rather, it is more sadness,
disappointment and frustration.

Regards,

Daniel


1. http://www.indexmundi.com/kosovo/age_structure.html

Bug#648292: gnome-control-center: Sticky keys do not work.

[Filip Wardziński]

Dear Maintainer,

I've found out that my problem is related to running Gnome Shell trough
Wayland by default after upgrade. When GNOME on X.org is selected in GDM
during login Sticky Keys work as expected. Still I have no idea how to make
them work on Wayland.

Kind regards
Filip

Bug#873097: glibc: FTBFS on *all* architectures except m68k, powerpcspe, sh4

[Adrian Bunk]

On Thu, Aug 24, 2017 at 04:48:55PM +0200, Thorsten Glaser wrote:
> Source: glibc
> Version: 2.24-16
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
> 
> cf. https://buildd.debian.org/status/package.php?p=glibc
> 
> For over three days now, src:glibc is FTBFS’ing virtually everywhere:
> 
> amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el,
> s390x, alpha, hppa, hurd-i386, kfreebsd-amd64, kfreebsd-i386, powerpc,
> ppc64, sparc64, x32 — the list is so long it doesn’t fit into the
> bugreport’s Subject.

That's due to the #872846 change.

> ... which is probably why the
> three slow architectures have been spared.

These are buildds that are building with nocheck.

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

Bug#870199: lintian: file-contains-fixme-placeholder is "Certainty: certain" but has false positives

[Chris Lamb]

tags 870199 + pending
thanks

Fixed in Git:

  
https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=cbd623115c66e77a65cb022b5c46e78736761721


Regards,

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

Bug#873117: error: alternative path /usr/lib/jvm/java-9-openjdk-amd64/bin/rmid doesn't exist

[Dmitri]

Package: openjdk-9-jre-headless
Version: 9~b181-3
Severity: normal

Dear Maintainer,

Hi! Can not upgrade the package

Errors were encountered while processing:
 openjdk-9-jre-headless:amd64
 openjdk-9-jdk-headless:amd64
 openjdk-9-jdk:amd64
 openjdk-9-jre:amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up openjdk-9-jre-headless:amd64 (9~b181-3) ...
update-alternatives: error: alternative path /usr/lib/jvm/java-9-openjdk-
amd64/bin/rmid doesn't exist
dpkg: error processing package openjdk-9-jre-headless:amd64 (--configure):
 subprocess installed post-installation script returned error exit status 2
dpkg: dependency problems prevent configuration of openjdk-9-jdk-
headless:amd64:
 openjdk-9-jdk-headless:amd64 depends on openjdk-9-jre-headless (= 9~b181-3);
however:
  Package openjdk-9-jre-headless:amd64 is not configured yet.

dpkg: error processing package openjdk-9-jdk-headless:amd64 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of openjdk-9-jdk:amd64:
 openjdk-9-jdk:amd64 depends on openjdk-9-jdk-headless (= 9~b181-3); however:
  Package openjdk-9-jdk-headless:amd64 is not configured yet.

dpkg: error processing package openjdk-9-jdk:amd64 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of openjdk-9-jre:amd64:
 openjdk-9-jre:amd64 depends on openjdk-9-jre-headless (= 9~b181-3); however:
  Package openjdk-9-jre-headless:amd64 is not configured yet.

dpkg: error processing package openjdk-9-jre:amd64 (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 openjdk-9-jre-headless:amd64
 openjdk-9-jdk-headless:amd64
 openjdk-9-jdk:amd64
 openjdk-9-jre:amd64


   * What led up to the situation?
aptitude upgrade



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

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

Versions of packages openjdk-9-jre-headless depends on:
ii  ca-certificates-java  20170531+nmu1
ii  java-common   0.59
ii  libcups2  2.2.4-3
ii  libjpeg62-turbo   1:1.5.1-2
ii  liblcms2-22.8-4
ii  libnss3   2:3.32-1
ii  util-linux2.29.2-4

openjdk-9-jre-headless recommends no packages.

Versions of packages openjdk-9-jre-headless suggests:
ii  fonts-dejavu-extra 2.37-1
pn  fonts-indic
pn  fonts-ipafont-gothic   
pn  fonts-ipafont-mincho   
ii  libnss-mdns0.10-8
pn  ttf-wqy-microhei | ttf-wqy-zenhei  

-- no debconf information

Bug#682347: mark 'editor' virtual package name as obsolete

[Russ Allbery]

Dropping Artem, whose email address no longer works.

Brendan O'Dea  writes:
> On Wed, Aug 23, 2017 at 11:03:23PM -0700, Russ Allbery wrote:

>> In previous discussions, no one seemed to feel that it was helpful as a
>> virtual package.  Virtual packages are only useful for another package
>> to depend on (or recommend or suggest), or for someone to manually use
>> as in "apt-get install editor", neither of which seem like useful
>> actions here.  (Or to conflict with, but that's obviously wrong here.)
>> No packages currently declare any type of dependency on editor.

> Note that there *are* a handful packages which still depend/recommend/suggest
> editor and will need bugs raised along with those for the editors providing
> it.

>   $ apt-cache showpkg editor
>   Package: editor
>   Versions:

>   Reverse Depends:
> dnsvi,editor
> xpaint,editor
> udo-doc-en,editor
> udo-doc-de,editor
> libproc-invokeeditor-perl,editor
>   [...]

Oh, thank you!  For some reason, apt-cache rdepends didn't show any of
those packages.  All of them except dnsvi are Suggests, which basically
doesn't accomplish anything.

Copying myon on this message as maintainer of dnsvi, which has a
dependency on "vim | editor".  Christoph, we're proposing finally removing
the editor virtual package completely, with the patch included here:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682347#20

-- 
Russ Allbery (r...@debian.org)   

Bug#873116: mdadm: If no arrays are specified in mdadm.conf then initrd starts all arrays

[John Hughes]

Package: mdadm
Version: 3.4-4+b1
Severity: normal

Dear Maintainer,

   * What led up to the situation?

upgraded from jessie to stretch

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

We want to manually start our arrays, rather than having them started on
boot or udev detection, so we specify:

AUTO -all

with no ARRAYs in mdadm.conf

   * What was the outcome of this action?

On boot all arrays were started.

   * What outcome did you expect instead?

No arrays automatically started

What happens is that the script /usr/share/initramfs-tools/hooks/mdadm notices
that there are no ARRAYs defined in mdadm.conf it uses the script
/usr/share/mdadm/mkconf to make a configuration including all arrays attached
to the system.

As a workaround we have added a dummy array:

ARRAY name=unused

to our configuration and now no arrays get started on boot (which is what
we want).

The messages about currently running arrays that are not in the config
are annoying, but we can ignore them.


-- Package-specific info:
--- mdadm.conf
DEVICE partitions
CREATE owner=root group=disk mode=0660 auto=yes
HOMEHOST 
MAILADDR sta...@olympic.calvaedi.com
AUTO -all
ARRAY name=unused

--- /etc/default/mdadm
AUTOCHECK=true
START_DAEMON=true
DAEMON_OPTIONS="--syslog"
VERBOSE=false

--- /proc/mdstat:
Personalities : [raid1] [raid10] [linear] [multipath] [raid0] [raid6] [raid5] 
[raid4] 
md125 : active raid1 sdb[2] sdd[3]
  3906887360 blocks super 1.2 [2/2] [UU]
  bitmap: 0/30 pages [0KB], 65536KB chunk

md126 : active raid1 sdc[2] sde[3]
  1953511869 blocks super 1.1 [2/2] [UU]
  bitmap: 0/466 pages [0KB], 2048KB chunk

md127 : active raid10 sdz[0] sdi[11] sdq[12] sdj[9] sdt[8] sdk[7] sdu[6] sdl[5] 
sdw[4] sdm[3] sdx[2] sdn[1]
  429729792 blocks super 1.2 512K chunks 2 near-copies [12/12] 
[]
  bitmap: 1/4 pages [4KB], 65536KB chunk

unused devices: 

--- /proc/partitions:
major minor  #blocks  name

   80   71041024 sda
   81 498688 sda1
   82  1 sda2
   85   70539264 sda5
  1101048575 sr0
   8   16 3907018584 sdb
   8   32 1953514584 sdc
   8   48 3907018584 sdd
   8   64 1953514584 sde
   8   80  976762584 sdf
   8   96  143374740 sdg
   8  112   71687325 sdh
   8  128   71687325 sdi
   8  144   71687325 sdj
   8  160   71687325 sdk
   8  176   71687325 sdl
   8  192   71687325 sdm
   8  208   71687325 sdn
   8  224  143374740 sdo
   8  240   62522712 sdp
  650   71687325 sdq
  65   16  976762584 sdr
  65   32  143374740 sds
  65   48   71687325 sdt
  65   64   71687325 sdu
  65   80   62522712 sdv
  65   96   71687325 sdw
  65  112   71687325 sdx
  65  128  143374740 sdy
  65  144   71687325 sdz
 25307811072 dm-0
 2531   23437312 dm-1
 2532   15622144 dm-2
 25337811072 dm-3
   9  127  429729792 md127
 2590 258016 md127p1
 2591  429471504 md127p2
   9  126 1953511869 md126
   9  125 3906887360 md125

--- LVM physical volumes:
  PV VGFmt  Attr PSize  PFree 
  /dev/sda5  arabic-vg lvm2 a--  67.27g 15.12g
--- mount output
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs 
(rw,nosuid,relatime,size=12328556k,nr_inodes=3082139,mode=755)
devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=2468104k,mode=755)
/dev/mapper/arabic--vg-root on / type ext4 
(rw,relatime,errors=remount-ro,data=ordered)
securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/cpuset type cgroup 

Bug#872880: libemf: FTBFS: #error Unknown CPU architecture!

[Steve Langasek]

Control: affects -1 pstoedit
Control: severity -1 serious

pstoedit now build-depends on libemf on all architectures, so the fact that
libemf is not buildable on some release architectures is a release-critical
regression in architecture support which will block pstoedit from migrating
to testing.

This may be resolved either by making libemf buildable on all architectures,
or by making pstoedit's build-dependency arch-conditional.  In the latter
case this bug would still apply but would no longer be serious.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#873114: Acknowledgement (d-i: failure to install grub2 on USB drive)

[Heinrich Schuchardt]

Find screenshots of the problem appended

Bug#872867: is ISO-3166 really the optimal list for our users?

[Daniel Pocock]

On 24/08/17 18:02, Wouter Verhelst wrote:

> Case in point: why would Kosovo *need* to be on the d-i list of
> countries? Is there a difference between Kosovo and Serbia[1] or other
> countries in the former Yugoslavia that d-i would need to be aware of
> (such as locale settings, keyboard layout, time zone, or preferred
> mirror), or is this bug in fact just the result of people with a

90% of citizens in Kosovo are ethnic Albanian[1] and would probably
prefer the installer to help them select the Albanian language (coming
soon thanks to a translation sprint at FOSSCamp.cc) and mirrors in
Kosovo.  These are probably the two main differences from RS.  Kosovo
has EUR as currency, RS does not.

The locale chooser and the country list for mirrors could potentially
work in different ways too, e.g. maybe subdivisions could be introduced
for the mirror list.

It doesn't impact time zone

I don't have hard data about the keyboard layouts users prefer in the
region, but I've seen US style keyboards there.

Regards,

Daniel



1. https://en.wikipedia.org/wiki/Kosovo_Albanians

Bug#869667: stretch-pu: package xkeyboard-config/2.19-1

[Cyril Brulebois]

Pirate Praveen  (2017-08-24):
> On Sun, 30 Jul 2017 23:10:45 +0100 "Adam D. Barratt"
>  wrote:> As the package produces a udeb, this
> will need an ack from the d-i RM as
> > well; CCing appropriately.
> 
> Its already 3 weeks without a response. I tried pinging them on irc as well.

Great thing that point releases usually happen once every 3 months, right?

Anyway: right now, D-I Buster Alpha 1 has the priority; point release
material can definitely wait.


KiBi.


signature.asc
Description: Digital signature

Bug#873115: concurrent apache2 -k graceful hang

[Joey Hess]

Package: apache2
Version: 2.4.25-3+deb
Severity: normal

I woke up to a server with hundreds of apach2e -k graceful processes running.
This prevented any cgis from running since it was nearly out of process slots.

 2142 ?SNs0:01 /usr/sbin/apache2 -k graceful
 6007 ?SN 0:00  \_ /usr/sbin/apache2 -k graceful
 4680 ?SNl0:00  \_ /usr/sbin/apache2 -k graceful
 2217 ?SNs0:01 /usr/sbin/apache2 -k graceful
 7127 ?SN 0:00  \_ /usr/sbin/apache2 -k graceful
 2542 ?SNl0:00  \_ /usr/sbin/apache2 -k graceful
 2177 ?SNs0:01 /usr/sbin/apache2 -k graceful
 6748 ?SN 0:00  \_ /usr/sbin/apache2 -k graceful
 4189 ?SNl0:00  \_ /usr/sbin/apache2 -k graceful
 2214 ?SNs0:01 /usr/sbin/apache2 -k graceful
 6738 ?SN 0:00  \_ /usr/sbin/apache2 -k graceful
 3023 ?SNl0:00  \_ /usr/sbin/apache2 -k graceful

This was just after an upgrade from oldstable the day before.

I'm at this point not quite sure what reloaded apache multiple times,
but it was probably a cron job reloading it once per vhost or something
like that.

Running a single apache2ctl graceful did not result in any such stuck
processes. I was able to reproduce the basic problem thus:

apache2ctl graceful & apache2ctl graceful & apache2ctl graceful

With 3 running concurrently, they get in each other's way.

Output to the console looked like this:

pell:/# apache2ctl graceful & apache2ctl graceful  & apache2ctl graceful
[1] 15772
[2] 15773
httpd not running, trying to start
httpd not running, trying to start
httpd not running, trying to start
[1]-  Doneapache2ctl graceful
pell:/# 
[2]+  Doneapache2ctl graceful
pell:/# 
pell:/# ps -fax |grep graceful
16120 pts/0S+ 0:00   \_ grep graceful
15788 ?Ss 0:00 /usr/sbin/apache2 -k graceful
15790 ?S  0:00  \_ /usr/sbin/apache2 -k graceful
15795 ?Sl 0:00  \_ /usr/sbin/apache2 -k graceful
15796 ?Sl 0:00  \_ /usr/sbin/apache2 -k graceful
15789 ?Ss 0:00 /usr/sbin/apache2 -k graceful
15901 ?S  0:00  \_ /usr/sbin/apache2 -k graceful
15903 ?Sl 0:00  \_ /usr/sbin/apache2 -k graceful
15904 ?Sl 0:00  \_ /usr/sbin/apache2 -k graceful
15794 ?Ss 0:00 /usr/sbin/apache2 -k graceful
15902 ?S  0:00  \_ /usr/sbin/apache2 -k graceful
16010 ?Sl 0:00  \_ /usr/sbin/apache2 -k graceful

What are the stuck processes doing? Waiting on something..

pell:/# strace -p 15794
strace: Process 15794 attached
_newselect(0, NULL, NULL, NULL, {tv_sec=0, tv_usec=762363}) = 0 (Timeout)
waitpid(-1, 0xbfce1210, WNOHANG|WSTOPPED) = 0
_newselect(0, NULL, NULL, NULL, {tv_sec=1, tv_usec=0}) = 0 (Timeout)
waitpid(-1, 0xbfce1210, WNOHANG|WSTOPPED) = 0
pell:/# strace -p 15902
strace: Process 15902 attached
accept(4,  ^C
pell:/# ls -l /proc/15902/fd/4
lrwx-- 1 root root 64 Aug 24 16:18 /proc/15902/fd/4 -> socket:[2396130]
pell:/# strace -p 16010
strace: Process 16010 attached
read(7,^C
pell:/# ls -l /proc/16010/fd/7
lr-x-- 1 root root 64 Aug 24 16:18 /proc/16010/fd/7 -> pipe:[2401595]

-- 
see shy jo


signature.asc
Description: PGP signature

Bug#873096: Now nodejs provides node

[Chris Lamb]

tags 873096 + pending
thanks

Fixed in Git:

  
https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=7d0c0732e792cf0a0cadeb583c9878463813e24a


Regards,

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

Bug#873113: RFS: xssproxy/1.0.0-1 [ITP]

[tim]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

* Package name: xssproxy
  Version : 1.0.0-1
  Upstream Author : Tim Schumacher 
* URL : https://github.com/timakro/xssproxy
* License : GPL-3+
  Section : x11

It builds those binary packages:

xssproxy   - Forward freedesktop.org Idle Inhibition Service calls to Xss

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


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


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

dget -x  
https://mentors.debian.net/debian/pool/main/x/xssproxy/xssproxy_1.0.0-1.dsc



Regards,
 Tim Schumacher


binYV7cfZuEx7.bin
Description: PGP Public Key


pgp_Jsdy7nFrH.pgp
Description: PGP Digital Signature

Bug#873112: dehydrated-hook-ddns-tsig: please support placing challenge in different hostname than _acme-challenge.domain.ext

[Markus Treinen]

Package: dehydrated-hook-ddns-tsig
Version: 0.1.1-1
Severity: wishlist

Hello,

some people use static zone files in most of their zones and dynamic dns only 
in one or a few other zones.
To use dns-01 challenge, the zone has to be dynamic, which is often not 
possible in this constellation.
The solution is setting a CNAME from _acme-challenge.domain.ext to i.e. 
domain.ext.dynamiczone.otherdomain.ext. This lets ACME check the challenge in a 
static zone while allowing dehydrated to update the dynamic entry.

Would it be possible to include an option to transform the original location of 
the challenge to the other location in the dynamic zone? Perhaps by using a 
regular expression substitution rule:
  s/^_acme-challenge\.(.+)$/$1.dynamiczone.otherdomain.ext/

Cheers,
Markus

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

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

Versions of packages dehydrated-hook-ddns-tsig depends on:
ii  dehydrated0.4.0-2
ii  python2.7.13-2
ii  python-dnspython  1.15.0-1

dehydrated-hook-ddns-tsig recommends no packages.

dehydrated-hook-ddns-tsig suggests no packages.

-- no debconf information

Bug#873111: pqiv does not include .desktop file

[Jay Kamat]

Package: pqiv
Version: 2.6-1+b1
Severity: normal

Dear Maintainer,

pqiv has had a pqiv.desktop file since 
https://github.com/phillipberndt/pqiv/issues/73 was implemented.

However, the pqiv on debian stable does not include said pqiv.desktop in
/usr/share/applications. This means that it is impossible to open images
in pqiv via xdg-open.

Expected results: apt install pqiv places a pqiv.desktop file in
/usr/share/applications

Actual results: no pqiv.desktop file is placed in
/usr/share/applications

I don't know enough about debian packaging, if I did, I would have
submitted a patch myself to fix this.

if you run a 'make install' of pqiv, it places a pqiv.desktop file in
the correct location.

Thanks for all the work you do on debian!

-Jay

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

Kernel: Linux 4.9.0-3-amd64 (SMP w/8 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 pqiv depends on:
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-11+deb9u1
ii  libcairo-gobject21.14.8-1
ii  libcairo21.14.8-1
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.50.3-2
ii  libgtk-3-0   3.22.11-1
ii  libpango-1.0-0   1.40.5-1
ii  libpangocairo-1.0-0  1.40.5-1
ii  libx11-6 2:1.6.4-3

pqiv recommends no packages.

pqiv suggests no packages.

-- no debconf information

Bug#873096: Now nodejs provides node

[Mattia Rizzolo]

On Thu, Aug 24, 2017 at 08:52:27AM -0700, Chris Lamb wrote:
> Alas not, this is a separate bug/check as specifically requested in:
> 
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872699#10
> 
> To clarify, #873096 is to silence the incorrect warning about "node"
> being completely unrecognised whilst #873096 is about explicitly pointing
> out that nodejs is depecrated and you should move to node

Ah, sorry, thanks for explaining it.  I didn't undestand it from the
original message.

-- 
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#873108: xscreensaver does not trap errors from intltool-update

[Helmut Grohne]

Source: xscreensaver
Version: 5.36-1
Severity: serious
Justification: policy 4.6
User: helm...@debian.org
Usertags: rebootstrap

The debian policy section 4.6 requires that when build commands fail,
the build should abort. In case xscreensaver's intltool-update aborts,
the error is ignored and the build attempts to continue potentially
resulting in a broken package. Adding "set -e; " (as suggested by the
policy) or chaining the commands with "&&" fixes this issue.

Helmut

Bug#872867: is ISO-3166 really the optimal list for our users?

[Wouter Verhelst]

On Thu, Aug 24, 2017 at 09:05:22AM +0200, Daniel Pocock wrote:
> 
> 
> On 24/08/17 08:51, Wouter Verhelst wrote:
> 
> > In the case of XYZ, "use a different distribution" isn't going to
> > silence such people. Instead, they'll just yell harder. "Debian's making
> > a political statement about XYZ, and it's wrong, and I told them that
> > it's wrong, and they're ignoring me!"
> >
> 
> Including and excluding are different things
> 
> Including extra "countries" may cause offense to people with certain
> political sensitivities, but doesn't cause any technical problem for
> people in other countries.

That may be true, but even so, those sensitivities are a hornet's nest
that we really don't want to be involved in.

> So if Debian has a policy that we favour inclusion over exclusion and
> that any country can be listed if at least one DD visits there and
> confirms it exists, is that political or would that be a policy that can
> be defended?

All disputed territories *exist*, and there will almost always be a
government that de facto rules the territory, that's not the point.
Whether a region is a country, however, is not something that Debian
Developers are expected to be able to ascertain.

I don't think that's a policy that can be defended.

> I wonder how long it would be before somebody proposed California or
> Scotland?  If they entered the list at the same time as Kosovo (and Hutt
> River) then it becomes a lot less political and the focus is not on a
> single region.

You're making the mistake of assuming that people who get upset over a
list of countries will check the whole list rather than just the bit
they care about...

Case in point: why would Kosovo *need* to be on the d-i list of
countries? Is there a difference between Kosovo and Serbia[1] or other
countries in the former Yugoslavia that d-i would need to be aware of
(such as locale settings, keyboard layout, time zone, or preferred
mirror), or is this bug in fact just the result of people with a
background of Kosovan nationalist ideology complaining about it to
you[2]? So far I've only seen you argue that "Kosovo needs to be on the
list that d-i presents," but I have not seen any technical arguments for
which that would in fact be necessary.

Put otherwise, is this request in fact a request about technical
matters, or is it instead a request about a political matter?

[1] In case that wasn't clear: Serbia is the country that Kosovo
declared independence from in 2008.
[2] For clarity, I'm not saying they're right, and I'm not saying
they're wrong. I'm not opposed to including Kosovo, even if it is
technically not necessary, provided that it can be done in a
politically neutral way.

> > Whatever solution you[1] come up with should avoid that.
> > 
> > [1] I'm assuming you're planning on submitting a patch, since you
> > suggested this change in the first place...
> > 
> 
> I would not want to waste time coding something before we have some
> consensus about what the community is comfortable with.

Sure, fair enough.

-- 
Could you people please use IRC like normal people?!?

  -- Amaya Rodrigo Sastre, trying to quiet down the buzz in the DebConf 2008
 Hacklab

Bug#873110: Race condition in /lib/udev/ifupdown-hotplug causes interfaces to stay unconfigured

[Florian Zumbiehl]

Package: ifupdown
Version: 0.8.19

This code in /lib/udev/ifupdown-hotplug just fails when there is is another
ifup running at the same time:

|local out=$(ps -C ifup ho args)
|if [ "${out%$INTERFACE*}" != "$out" ]; then
|mesg "Already ifup-ing interface $INTERFACE"
|exit 0
|fi

When tracing the execution of that, this is the result:

| + local out=ifup --allow=hotplug veth-foo
| /lib/udev/ifupdown-hotplug: 70: local: veth-foo: bad variable name

The result is, obviously, that the interface simply stays unconfigured.

Commenting out that block seems to "solve" the problem.

Bug#873107: by not running it prevents changing screen resolution, breaks the font scaling, keyboard hotkeys and center touchpad tap

[Arnaldo Pirrone]

Package: cinnamon-settings-daemon
Version: 3.4.2-1
Severity: important
Tags: patch

Dear maintainer,

It has been 2 weeks this way,
I've upgraded it to experimental version, please push it into the main sid
repo!



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

Kernel: Linux 4.12.0-8.3-liquorix-amd64 (SMP w/4 CPU cores; PREEMPT)
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 cinnamon-settings-daemon depends on:
ii  cinnamon-desktop-data3.2.4-4
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2+b1
ii  gir1.2-cvc-1.0   3.2.4-4
ii  libc62.24-14
ii  libcairo21.14.10-1
ii  libcanberra-gtk3-0   0.30-3
ii  libcanberra0 0.30-3
ii  libcinnamon-desktop4 3.2.4-4
ii  libcolord2   1.3.3-2
ii  libcups2 2.2.4-3
ii  libcvc0  3.2.4-4
ii  libdbus-glib-1-2 0.108-2
ii  libfontconfig1   2.12.3-0.2
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.53.6-1
ii  libgnomekbd8 3.22.0.1-1+b1
ii  libgtk-3-0   3.22.18-1
ii  libgudev-1.0-0   230-3
ii  liblcms2-2   2.8-4
ii  libnotify4   0.7.7-2
ii  libnspr4 2:4.16-1
ii  libnss3  2:3.32-1
ii  libpolkit-gobject-1-00.105-18
ii  libpulse010.0-2
ii  libsystemd0  234-2.3
ii  libupower-glib3  0.99.5-3
ii  libx11-6 2:1.6.4-3
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.9-1
ii  libxklavier165.4-2

Versions of packages cinnamon-settings-daemon recommends:
ii  pulseaudio  10.0-2

Versions of packages cinnamon-settings-daemon suggests:
ii  cinnamon [x-window-manager]  3.4.4-1
ii  cinnamon-screensaver 3.2.13-4
ii  marco [x-window-manager] 1.18.1-2
ii  muffin [x-window-manager]3.2.1-2
ii  x11-xserver-utils7.7+7+b1

-- no debconf information

Bug#873096: Now nodejs provides node

[Chris Lamb]

unmerge 873096
thanks

Mattia,

> > It would be nice if lintian were warning about nodejs uses in script
> > (and in particular in debian/tests/).
>
> You already reported it 4 days ago :)

Alas not, this is a separate bug/check as specifically requested in:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872699#10

To clarify, #873096 is to silence the incorrect warning about "node"
being completely unrecognised whilst #873096 is about explicitly pointing
out that nodejs is depecrated and you should move to node


Best wishes,

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

Bug#873052: gcl FTBFS on arm64: Unrecoverable error: Segmentation violation..

[Adrian Bunk]

Control: severity -1 serious

On Thu, Aug 24, 2017 at 11:34:05AM -0400, Camm Maguire wrote:
> tags 873052 unreproducible
> severity 873052 important
> thanks
> 
> Greetings, and thanks for your report!  Built stock gcl sources on up to
> date sid chroot on asachi without issue.  Uploaded binary.  I assume
> this is some transient issue on some buildd machines, but if you can
> tell me how to reproduce will investigate further.

This happened twice in a row, with two months between,
and on different buildds, so this is not a transient issue:
  https://buildd.debian.org/status/logs.php?pkg=gcl=arm64

Please ask an arm64 porter for support if needed.

> Take care,

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

Bug#873109: ITP: ruby-peek -- Take a peek into your Rails application

[Pirate Praveen]

Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 

from rubygems.org/gems/peek
dependency of gitlab 9.5







signature.asc
Description: OpenPGP digital signature

Bug#873106: xscreensaver FTCBFS: fails to detect a working c compiler

[Helmut Grohne]

Source: xscreensaver
Version: 5.36-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

xscreensaver fails to cross build from source, because it insists on
using AC_TRY_RUN to verify that the compiler works. That's generally a
bad idea and can simply be discarded. It also uses the build
architecture pkg-config. After fixing both, it cross builds
successfully. Please consider applying the attached patch.

Helmut
diff -u xscreensaver-5.36/debian/changelog xscreensaver-5.36/debian/changelog
--- xscreensaver-5.36/debian/changelog
+++ xscreensaver-5.36/debian/changelog
@@ -1,3 +1,12 @@
+xscreensaver (5.36-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ Add 91_cross.patch.
++ autoreconf.
+
+ -- Helmut Grohne   Thu, 24 Aug 2017 16:59:05 +0200
+
 xscreensaver (5.36-1) unstable; urgency=medium
 
   * New upstream release 5.36, changes since 5.34:
diff -u xscreensaver-5.36/debian/control xscreensaver-5.36/debian/control
--- xscreensaver-5.36/debian/control
+++ xscreensaver-5.36/debian/control
@@ -2,7 +2,7 @@
 Section: x11
 Priority: optional
 Maintainer: Tormod Volden 
-Build-Depends: bc, debhelper (>= 9.0), fortune-mod, libgtk2.0-dev, 
libpam0g-dev, libgl1-mesa-dev | libgl-dev, libglu1-mesa-dev | xlibmesa-glu-dev 
| libglu-dev, xutils-dev, libxml2-dev, libglade2-dev, libjpeg-dev, libgle-dev, 
intltool, autotools-dev, libx11-dev, libxext-dev, libxinerama-dev, libxmu-dev, 
libxpm-dev, libxrandr-dev, libxss-dev, libxt-dev, libxtst-dev, libxxf86vm-dev, 
x11proto-core-dev, xbitmaps, quilt, dpkg-dev (>= 1.16.1)
+Build-Depends: bc, debhelper (>= 9.0), dh-autoreconf, fortune-mod, 
libgtk2.0-dev, libpam0g-dev, libgl1-mesa-dev | libgl-dev, libglu1-mesa-dev | 
xlibmesa-glu-dev | libglu-dev, pkg-config, xutils-dev, libxml2-dev, 
libglade2-dev, libjpeg-dev, libgle-dev, intltool, autotools-dev, libx11-dev, 
libxext-dev, libxinerama-dev, libxmu-dev, libxpm-dev, libxrandr-dev, 
libxss-dev, libxt-dev, libxtst-dev, libxxf86vm-dev, x11proto-core-dev, 
xbitmaps, quilt, dpkg-dev (>= 1.16.1)
 Standards-Version: 3.9.8
 Homepage: http://www.jwz.org/xscreensaver/
 Vcs-Git: https://anonscm.debian.org/git/collab-maint/xscreensaver.git
diff -u xscreensaver-5.36/debian/patches/series 
xscreensaver-5.36/debian/patches/series
--- xscreensaver-5.36/debian/patches/series
+++ xscreensaver-5.36/debian/patches/series
@@ -26,0 +27 @@
+91_cross.patch
diff -u xscreensaver-5.36/debian/rules xscreensaver-5.36/debian/rules
--- xscreensaver-5.36/debian/rules
+++ xscreensaver-5.36/debian/rules
@@ -45,6 +45,8 @@
  mv config.guess config.guess.upstream && \
cp /usr/share/misc/config.guess config.guess
 
+   dh_autoreconf
+
# Configure for xscreensaver
./configure --build $(DEB_BUILD_GNU_TYPE) --host $(DEB_HOST_GNU_TYPE) \
--prefix=/usr \
@@ -83,6 +85,7 @@
  mv driver/XScreenSaver_ad.h.upstream driver/XScreenSaver_ad.h
[ ! -f driver/XScreenSaver_Xm_ad.h.upstream ] || \
  mv driver/XScreenSaver_Xm_ad.h.upstream driver/XScreenSaver_Xm_ad.h
+   dh_autoreconf_clean
dh_clean
 
 binary-indep:  build
--- xscreensaver-5.36.orig/debian/patches/91_cross.patch
+++ xscreensaver-5.36/debian/patches/91_cross.patch
@@ -0,0 +1,42 @@
+From: Helmut Grohne 
+Subject: fix cross compilation
+
+AC_TRY_RUN fails during cross compilation. We can expect any compiler to just
+work, so discard the test.
+
+Consider $ac_tool_prefix for pkg-config by using PKG_PROG_PKG_CONFIG.
+
+Index: xscreensaver-5.36/configure.in
+===
+--- xscreensaver-5.36.orig/configure.in
 xscreensaver-5.36/configure.in
+@@ -421,13 +421,6 @@
+ 
+   OBJCC="$CC"
+ 
+-  AC_MSG_CHECKING([whether the compiler works on ANSI C])
+-  AC_TRY_RUN([ main(int ac, char **av) { return 0; } ],
+- AC_MSG_RESULT(yes),
+- AC_MSG_RESULT(no)
+- AC_MSG_ERROR(Couldn't build even a trivial ANSI C program: check CC.),
+- AC_MSG_ERROR(Couldn't build even a trivial ANSI C program: check CC.))
+-
+   if test -n "$GCC"; then
+ AC_MSG_RESULT(Turning on gcc compiler warnings.)
+ CC="$CC -pedantic -Wall -Wstrict-prototypes -Wnested-externs 
-Wmissing-prototypes"
+@@ -2626,11 +2619,13 @@
+   gtk_path="$foo:$gtk_path"
+ fi
+ 
+-AC_PATH_PROGS(pkg_config, pkg-config,, $gtk_path)
++PKG_PROG_PKG_CONFIG
+ 
+-if test -z "$pkg_config" ; then
++if test -z "$PKG_CONFIG" ; then
+   AC_MSG_WARN([pkg-config not found!])
+   pkg_config="false"
++else
++  pkg_config=$PKG_CONFIG
+ fi
+ 
+ 

Bug#873105: RFS: find-file-in-project/5.4.1-1 [ITP]

[Nicholas D Steeves]

Package: sponsorship-requests
Severity: wishlist

I am looking for a sponsor for my package "find-file-in-project"

* Package name: find-file-in-project
  Version : 5.4.1-1
  Upstream Author : Will Farrington et al, Chen Bin is the current maintainer
* URL : https://github.com/technomancy/find-file-in-project
* License : GPL-3+
  Section : lisp

It builds those binary packages:

  elpa-find-file-in-project - Quick access to project files in Emacs

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

  https://mentors.debian.net/package/find-file-in-project


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

  dget -x 
https://mentors.debian.net/debian/pool/main/f/find-file-in-project/find-file-in-project_5.4.1-1.dsc

One can also clone it from this remote:
  git clone 
https://anonscm.debian.org/cgit/pkg-emacsen/pkg/find-file-in-project.git

More information about ffip can be obtained from 
https://github.com/technomancy/find-file-in-project

Regards,
Nicholas

Bug#873104: openjdk-9: update-alternatives error + fail in updating

[Nelson A. de Oliveira]

Source: openjdk-9
Version: 9~b181-3
Severity: serious

Hi!

Today while upgrading openjdk-9* packages from 9~b181-2 to 9~b181-3:

=
Setting up openjdk-9-jre-headless:amd64 (9~b181-3) ...
update-alternatives: error: alternative path 
/usr/lib/jvm/java-9-openjdk-amd64/bin/rmid doesn't exist
dpkg: error processing package openjdk-9-jre-headless:amd64 (--configure):
 subprocess installed post-installation script returned error exit status 2
dpkg: dependency problems prevent configuration of openjdk-9-jdk-headless:amd64:
 openjdk-9-jdk-headless:amd64 depends on openjdk-9-jre-headless (= 9~b181-3); 
however:
  Package openjdk-9-jre-headless:amd64 is not configured yet.

dpkg: error processing package openjdk-9-jdk-headless:amd64 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of openjdk-9-jdk:amd64:
 openjdk-9-jdk:amd64 depends on openjdk-9-jdk-headless (= 9~b181-3); however:
  Package openjdk-9-jdk-headless:amd64 is not configured yet.

dpkg: error processing package openjdk-9-jdk:amd64 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of openjdk-9-jre:amd64:
 openjdk-9-jre:amd64 depends on openjdk-9-jre-headless (= 9~b181-3); however:
  Package openjdk-9-jre-headless:amd64 is not configured yet.

dpkg: error processing package openjdk-9-jre:amd64 (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 openjdk-9-jre-headless:amd64
 openjdk-9-jdk-headless:amd64
 openjdk-9-jdk:amd64
 openjdk-9-jre:amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
=

Before the update it was possible to see that a lot of disk space was
going to be freed (so probably something is missing on the new
packages?)

=
# LC_ALL=C apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  binutils-common binutils-x86-64-linux-gnu libbinutils
The following packages have been kept back:
  libc-dev-bin libc6 libc6-dev nodejs nodejs-dev
The following packages will be upgraded:
  binutils libdbusmenu-glib4 libdbusmenu-gtk3-4 libdbusmenu-gtk4 
libmariadbclient18 libnghttp2-14 libpam-systemd librtlsdr-dev librtlsdr0 
libsystemd0 libsystemd0:i386 libudev-dev libudev1 libudev1:i386 libxcursor1 
mariadb-common openjdk-9-jdk openjdk-9-jdk-headless openjdk-9-jre 
openjdk-9-jre-headless rtl-sdr
  systemd systemd-sysv udev
24 upgraded, 3 newly installed, 0 to remove and 5 not upgraded.
Need to get 10.2 MB/10.8 MB of archives.
After this operation, 274 MB disk space will be freed.
Do you want to continue? [Y/n]
=

And some warnings when trying to upgrade, saying that it was not
possible to remove some directories (since they were not empty; messages
are in Portuguese)

=
A descompactar openjdk-9-jre-headless:amd64 (9~b181-3) sobre (9~b181-2) ...
dpkg: aviso: não foi possível apagar o directório antigo 
'/usr/lib/jvm/java-9-openjdk-amd64/lib/server': Diretório não vazio
dpkg: aviso: não foi possível apagar o directório antigo 
'/etc/java-9-openjdk/security/policy/unlimited': Diretório não vazio
dpkg: aviso: não foi possível apagar o directório antigo 
'/etc/java-9-openjdk/security/policy/limited': Diretório não vazio
dpkg: aviso: não foi possível apagar o directório antigo 
'/etc/java-9-openjdk/security/policy': Diretório não vazio
dpkg: aviso: não foi possível apagar o directório antigo 
'/etc/java-9-openjdk/security': Diretório não vazio
dpkg: aviso: não foi possível apagar o directório antigo 
'/etc/java-9-openjdk/management': Diretório não vazio
dpkg: aviso: não foi possível apagar o directório antigo '/etc/java-9-openjdk': 
Diretório não vazi
=

Thank you!

Best regards,
Nelson

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

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

Bug#873052: gcl FTBFS on arm64: Unrecoverable error: Segmentation violation..

[Camm Maguire]

tags 873052 unreproducible
severity 873052 important
thanks

Greetings, and thanks for your report!  Built stock gcl sources on up to
date sid chroot on asachi without issue.  Uploaded binary.  I assume
this is some transient issue on some buildd machines, but if you can
tell me how to reproduce will investigate further.

Take care,
-- 
Camm Maguirec...@maguirefamily.org
==
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah

Bug#868990: lazarus: FTBFS: Architecture mips(el) is not available for elf format

[Peter Green]

Paul Gevers and I took at look at this while at Debconf.

Fixing the resource conversionturned out to be pretty easy. Unfortunately after 
doing so the lazarus package still failed to build. There seems to be a linker 
issue with freepascal and qt on mips.

So we decided to disable qt lazarus and only enable gtk lazarus. Unfortunately 
it seems paul forgot to disable the lcl-qt packages so it currently fails to 
build in the packaging step. Hopefully this should get fixed soon.

Bug#873103: [release.debian.org] Plan for imagemagick7 landing before next stable

[Bastien ROUCARIÈS]

Package: release.debian.org
Severity: wishlist

Hi,

I plan to release imagemagick 7 before next stable version. And I want to 
coexist imagemagick6 and imagemagick7.

Moreover I wish to allow smooth upgrade between the two

So I open a bug in order to allow discussion with release team.

Main problem is perl library. I do not know how to deal with it, I could use 
update alternative to select between 6 and 7 or I could package only the 7 
one...

Bastien

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

Bug#873102: [release.debian.org] transition: imagemagick

[Bastien ROUCARIÈS]

Package: release.debian.org
Severity: important

Hi,

I have just landed an imagemagick version in experimental, that break the ABI. 
Previous ABI used double_t that is not ABI stable...

Could we get a transition of libmagickcore, libmagickwand and libmagick++

I have rebuilded reverse deps a few week ago (waiting for ftpmaster) and it 
was fine.

I will fix ASAP the problems.

I have set the severity to important because I will prefer to get quickly a 
newer imagemagick version due to the number of security bug to backport

Thanks for your work

Bastien


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

Bug#869667: stretch-pu: package xkeyboard-config/2.19-1

[Pirate Praveen]

On Sun, 30 Jul 2017 23:10:45 +0100 "Adam D. Barratt"
 wrote:> As the package produces a udeb, this
will need an ack from the d-i RM as
> well; CCing appropriately.

Its already 3 weeks without a response. I tried pinging them on irc as well.



signature.asc
Description: OpenPGP digital signature

Bug#873101: virtualbox: stretch-backports of virtualbox

[Lucas Nussbaum]

Package: virtualbox
Version: 5.1.22-dfsg-1
Severity: wishlist

Hi,

While I understand the reasoning behind not shipping virtualbox in
stretch, I wonder if you have considered shipping it in
stretch-backports?

Thanks

Lucas


-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (990, 'stable'), (400, 'testing'), (300, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-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 virtualbox depends on:
ii  adduser   3.115
ii  init-system-helpers   1.48
ii  libc6 2.24-11+deb9u1
ii  libcurl3-gnutls   7.52.1-5
ii  libdevmapper1.02.12:1.02.137-2
ii  libgcc1   1:6.3.0-18
ii  libgsoap102.8.35-4
ii  libpng16-16   1.6.28-1
ii  libpython3.5  3.5.3-1
ii  libsdl1.2debian   1.2.15+dfsg1-4
ii  libssl1.1 1.1.0f-3
ii  libstdc++66.3.0-18
ii  libvncserver1 0.9.11+dfsg-1
ii  libvpx4   1.6.1-3
ii  libx11-6  2:1.6.4-3
ii  libxcursor1   1:1.1.14-1+b4
ii  libxext6  2:1.3.3-1+b2
ii  libxml2   2.9.4+dfsg1-2.2
ii  libxmu6   2:1.1.2-2
ii  libxt61:1.1.5-1
ii  procps2:3.3.12-3
ii  python3   3.5.3-1
ii  python3.5 3.5.3-1
ii  virtualbox-dkms [virtualbox-modules]  5.1.22-dfsg-1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages virtualbox recommends:
ii  libgl1-mesa-glx [libgl1]  13.0.6-1+b2
ii  libqt5core5a  5.7.1+dfsg-3+b1
ii  libqt5opengl5 5.7.1+dfsg-3+b1
ii  libqt5widgets55.7.1+dfsg-3+b1
ii  virtualbox-qt 5.1.22-dfsg-1

Versions of packages virtualbox suggests:
ii  vde22.3.2+r586-2.1
pn  virtualbox-guest-additions-iso  

-- no debconf information

Bug#873098: [Pkg-javascript-devel] Bug#873098: Use node instead of nodejs

[Bastien ROUCARIES]

It need in this cas a depend on nodejs (>= 6)

On Thu, Aug 24, 2017 at 4:50 PM, Julien Puydt  wrote:
> Package: npm2deb
> Version: 0.2.7-2
> Severity: wishlist
>
> Now nodejs provides /usr/bin/node -- so the tests (like the require one)
> should use node and not nodejs.
>
> Snark on #debian-js
>
> --
> Pkg-javascript-devel mailing list
> pkg-javascript-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

Bug#873096: Now nodejs provides node

[Mattia Rizzolo]

Control: forcemerge 872699 -1

On Thu, Aug 24, 2017 at 04:37:35PM +0200, Julien Puydt wrote:
> since a recent decision of the technical comity, the nodejs package
> provides /usr/bin/node, in addition to /usr/bin/nodejs for backward
> compatibility.
> 
> It would be nice if lintian were warning about nodejs uses in script
> (and in particular in debian/tests/).

You already reported it 4 days ago :)

-- 
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#873100: imagemagick: CVE-2017-13133

[Salvatore Bonaccorso]

Source: imagemagick
Version: 8:6.9.7.4+dfsg-11
Severity: important
Tags: security upstream patch
Forwarded: https://github.com/ImageMagick/ImageMagick/issues/679

Hi,

the following vulnerability was published for imagemagick.

CVE-2017-13133[0]:
| In ImageMagick 7.0.6-8, the load_level function in coders/xcf.c lacks
| offset validation, which allows attackers to cause a denial of service
| (load_tile memory exhaustion) via a crafted file.

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-2017-13133
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-13133
[1] https://github.com/ImageMagick/ImageMagick/issues/679

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#861101: Can't enter disk encryption password

[Laurent Bigonville]

tag 861101 + moreinfo
thanks

On Mon, 24 Apr 2017 18:49:07 +0200 Sven Bartscher 
 wrote:


Hello Sven,

>
> I have a system with an encrypted root partition.
> When I try to boot it with splash enabled, I get prompted for the
> password in graphical mode. When I try to enter the password, it isn't
> entered into the password entry. Instead it is written to the upper
> left corner of the screen. Pressing enter just moves outputs a newline
> instead of accepting the input.
>

Are you still able to reproduce this?

Are you using closed source drivers for your graphic card?

Regards,

Laurent Bigonville

Bug#873099: imagemagick: CVE-2017-13134

[Salvatore Bonaccorso]

Source: imagemagick
Version: 8:6.9.7.4+dfsg-11
Severity: important
Tags: security patch upstream
Forwarded: https://github.com/ImageMagick/ImageMagick/issues/670

Hi,

the following vulnerability was published for imagemagick.

CVE-2017-13134[0]:
| In ImageMagick 7.0.6-6, a heap-based buffer over-read was found in the
| function SFWScan in coders/sfw.c, which allows attackers to cause a
| denial of service via a crafted file.

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-2017-13134
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-13134

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#873098: Use node instead of nodejs

[Julien Puydt]

Package: npm2deb
Version: 0.2.7-2
Severity: wishlist

Now nodejs provides /usr/bin/node -- so the tests (like the require one)
should use node and not nodejs.

Snark on #debian-js

Bug#873097: glibc: FTBFS on *all* architectures except m68k, powerpcspe, sh4

[Thorsten Glaser]

Source: glibc
Version: 2.24-16
Severity: serious
Justification: fails to build from source (but built successfully in the past)

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

For over three days now, src:glibc is FTBFS’ing virtually everywhere:

amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el,
s390x, alpha, hppa, hurd-i386, kfreebsd-amd64, kfreebsd-i386, powerpc,
ppc64, sparc64, x32 — the list is so long it doesn’t fit into the
bugreport’s Subject.

Causa seems to be something about the expected testsuite failures
having been adjusted in the last upload, which is probably why the
three slow architectures have been spared.

Bug#871373: kmymoney: FTBFS: CMakeFiles/Makefile2:4181: recipe for target 'kmymoney/dialogs/settings/CMakeFiles/settings_autogen.dir/all' failed

[Dmitry Shachnev]

Control: tags -1 +fixed-upstream

On Mon, Aug 07, 2017 at 11:55:30AM -0400, Lucas Nussbaum wrote:
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
>
> [...]

These two patches from upstream seem to fix the build for me:

1) https://cgit.kde.org/kmymoney.git/commit/?id=b0a68ca075928aa2 — fixes
   “No rule to make target '//kmymoneysettings.h', needed by
   'kmymoney/dialogs/settings/CMakeFiles/settings_autogen'”

2) https://cgit.kde.org/kmymoney.git/commit/?id=6d235f2cd835d5d3 — fixes
   “multiple definition of `sepaStoragePlugin::qt_static_metacall(QObject*,
   QMetaObject::Call, int, void**)'”

--
Dmitry Shachnev

Bug#873096: Now nodejs provides node

[Julien Puydt]

Package: lintian
Version: 2.5.52
Severity: wishlist

Hi,

since a recent decision of the technical comity, the nodejs package
provides /usr/bin/node, in addition to /usr/bin/nodejs for backward
compatibility.

It would be nice if lintian were warning about nodejs uses in script
(and in particular in debian/tests/).

Thanks,

Snark on #debian-js

Bug#872402: golang-golang-x-tools-dev: Does not work on mips*

[Martín Ferrari]

On 24/08/17 16:31, Shengjing Zhu wrote:

> Hi Martín,
> So what's the prolem of this x/sys? I didn't see this package has
> disabled tests.

Yes, sorry, I was confused with x/tools, which has disabled tests. This
one does not get built in other arches, so the relevant tests are not
executed.. Maybe we should make it arch:any...?

> Which package ftbfs because of x/sys?

Prometheus and friends were failing. I understood now what you are doing
here (it took me a while), and by passing tags I managed to get them
building again, but that's not a reasonable solution.. The packages
should build out of the box. Can't you add the correct build
restrictions for gccgo so we don't need the tags?

-- 
Martín Ferrari (Tincho)

Bug#873057: [pkg-ntp-maintainers] Bug#873057: ntp: ntpd not started at boot

[Bernhard Schmidt]

On 24.08.2017 10:31, Bernhard Schmidt wrote:

>> I have an installation of Debian testing with ntp installed on it. With
>> ntp version 1:4.2.8p10+dfsg-3 and earlier, ntpd was started during boot,
>> but with 1:4.2.8p10+dfsg-4 and -5, ntpd isn't started (which BTW is far
>> from obvious; I became aware of the issue only after I noticed that the
>> machine's clock had drifted about a minute from the correct time). If I
>> copy /lib/systemd/system/ntp.service to /etc/systemd/system/ntp.service
>> and comment out the line "Conflicts=systemd-timesyncd.service" then ntpd
>> is started again, so I suggest that you remove that line. It shouldn't
>> be necessary for ntp to conflict with timesyncd anyway, because the file
>> /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
>> checks if /usr/sbin/ntpd exists, and doesn't start timesyncd if it does.
> 
> Thanks for your report. I have tested this on a new Buster installation.
> Indeed systemd-timesyncd is running by default (which I think was not
> the case with Stretch). 

Has been the case with Stretch already, but ntp did not ship a systemd unit.

Still it works for me, so please provide the requested data.

Bernhard

Bug#872402: golang-golang-x-tools-dev: Does not work on mips*

[Shengjing Zhu]

Control: retitle -1 golang-golang-x-sys-dev: Does not work on mips*

Hi Martín,
So what's the prolem of this x/sys? I didn't see this package has
disabled tests.
Which package ftbfs because of x/sys?

On Thu, Aug 17, 2017 at 10:08 PM, Martín Ferrari  wrote:
> reassign 872402 golang-golang-x-sys
> thanks
>
>> Since 0.0~git20170629.0.1b3bb8de-1 a patch has made the source files shipped
>> fail to build in mips* architectures. It does not FTBFS just because tests 
>> have
>> been disabled in a previous version, but it is making other packages FTBFS.
>>
>
> I am being stupid and mixing x/tools with x/sys. Sorry about the noise.
>
> --
> Martín Ferrari (Tincho)
>
> ___
> Pkg-go-maintainers mailing list
> pkg-go-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers



-- 
Best regards,
Shengjing Zhu

Bug#872943: libpam-heimdal: Cannot configure credential cache file

[Matthew Gabeler-Lee]

On Wed, 23 Aug 2017, Russ Allbery wrote:


You'd also mentioned that you had read the man page about this, so I think
there's a bug here in the man page and how it discusses options that I'd
love to try to fix.  It looks like the way to do this wasn't obvious
enough.  The key bit, though, is here: [snip]


Aah, now I see.  Indeed I was a bit hasty when scanning the manpage for 
the thing I wanted to change (I think I just searched for "krb5cc_" 
since that's what I wanted to change).



This *should* work; please let me know if it doesn't.


Gave it a whirl, it works ... after I sort out my typos ;)


And let me know if
there's a way that I can make this information easier to find in the man
page.


A possible wording for the individual options that might help point 
folks back at the krb5.conf explanation without being too wordy (since 
it gets repeated a lot):


"This option can be set in the [appdefaults]/pam section or krb5.conf, 
..."



I should probably also call out that the PAM module doesn't use the
library default ccache location.  (I should also remember why I did that;
I know I had a specific reason, but I don't remember what it was.)


Agreed -- looking through the man page more carefully, I notice there is 
some discussion about a similar issue relating to how realms are 
handled, it would make sense to add a note about not using the normal 
defaults to this parameter too.


Thinking it through, I have a hunch why using the default "just specific 
to the UID" cache might be a bad idea if you don't have a daemon like 
winbindd to help manage sessionss:


If you log in once, and then a second time, and then log out one of 
those two sessions, that would empty/destroy the cache, leaving the 
other session with no ticket(s).  I just tested that, and indeed it is 
the case.


(pam)_winbind(d) doesn't have this problem, I think because it uses the 
daemon to be aware of the multiple sessions, so it can advise them if 
they are the "last" one and thus whether the cache should be destroyed 
or not when each sesssion exits.


But without that kind of support, it's a good reason to have pam_krb5 
default to a per-session ticket cache.  It complicates upcalls and 
anything else that wants to leverage a session's ticket cache from 
outside the session, but I'm not sure there's any easy way around that.



For my edification, can you explain why /usr/share/pam-configs/krb5
can't be made a conffile?


Files in /usr are not permitted to be configuration files.

Now, the other question is why these files aren't in /etc somewhere, which
would allow them to be conffiles and configuration files.  That's a good
question -- I don't really know off the top of my head why it was defined
that way.  I'm pretty sure it was discussed in the original PAM
configuration proposal for pam-auth-update.  The intent was that this
system should only be used if you want a fully-default PAM configuration
given the modules you have installed, but I'm not sure why that was the
intent.


Thanks for explaining.  I can run with that and see what I can find, and 
maybe propose a change to the PAM maintainer(s).


--
-Matt
"Reality is that which, when you stop believing in it, doesn't go away".
-- Philip K. Dick
GPG fingerprint: 0061 15DF D282 D4A9 57CE  77C5 16AF 1460 4A3C C4E9

Bug#873095: ITP: revolt -- better desktop integration for Riot.im

[Hubert Chathi]

Package: wnpp
Owner: Hubert Chathi 
Severity: wishlist

* Package name: revolt
  Version : 0.0+git20170627.3f5112b
  Upstream Author : Adrian Perez 
* URL or Web page : https://github.com/aperezdc/revolt
* License : GPL-3
  Description : better desktop integration for Riot.im

Revolt is a small application which wraps the Riot.im webapp to provide better
integration with desktop environments in general, and GNOME in particular:

   * Having Riot as a “standalone” application with its own window, launcher,
 icon, etc. instead of it living in a browser tab.
   * Persistent notifications (for desktop environments supporting them, i.e.
 GNOME). Notifications are automatically prevented when the Revolt window
 is focused.
   * Status icon for desktop environment which have a tray bar applet (XFCE,
 Budgie, likely many others).

Riot.im is a chat client for Matrix, an open, federated communications
protocol.

Bug#873094: RFS: granite/0.4.1-1 [ITP]

[yang]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

* Package name: granite
  Version : 0.4.1-1
 Upstream Author : elementary OS
* URL : https://launchpad.net/granite
* License : LGPLv3+
  Section : libs

It builds those binary packages:

gir1.2-granite-1.0 - extension of GTK+ libraries (introspection files)
granite-demo - extension of GTK+ libraries (demo binary)
libgranite-common - extension of GTK+ libraries (common files)
libgranite-dev - extension of GTK+ libraries (development files)
libgranite3 - extension of GTK+ libraries
libgranite3-dbg - extension of GTK+ libraries (debugging symbols)

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

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


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

  dget -x 
https://mentors.debian.net/debian/pool/main/g/granite/granite_0.4.1-1.dsc

More information about hello can be obtained from
https://github.com/elementary/granite .

Changes since the last upload:

 granite (0.4.1-1) unstable; urgency=medium

   * Initial release (Closes: #872919)


Regards,
 Yangfl

Bug#726731: #726731: dump: Huge RAM usage on restore

[Alexander Zangerl]

On Mon, 17 Jul 2017 20:55:04 -0700, Elliott Mitchell writes:
>I should mention a reasonable alternative method.

i'm not sure i'd want to go to a dir tree for this; if
one just wants to handle level 0 backups then my understanding
is that the restoresymtable could be skipped completely.

there's no code for such a skip at this time, but i suspect that
that would be a cheap remedy - at least for full backups.

>I /think/ it should be reasonable to replace restoresymtable with a
>small directory tree.

right now i don't see why the symtable cannot be dumped incrementally
instead of being held in memory. 

regards
az


-- 
Alexander Zangerl + GPG Key 2FCCF66BB963BD5F + http://snafu.priv.at/
"It's a pity that punched card equipment is now almost all gone. There's
nothing better for grabbing a tie and breaking the wearer's neck."  
 -- Mike Andrews 


signature.asc
Description: Digital Signature

Bug#873093: ITP: django-test-without-migrations -- Disable migrations when running your tests

[Herbert Parentes Fortes Neto]

Package: wnpp
Severity: wishlist
Owner: Herbert Parentes Fortes Neto 

* Package name: django-test-without-migrations
  Version : 0.6
  Upstream Author : Henrique Bastos 
* URL : https://pypi.python.org/pypi/django-test-without-migrations
* License : MIT
  Programming Lang: Python
  Description : Disable migrations when running your tests

Test Without Migrations is a manage.py test command extension.

The Django 1.7 and 1.8 migration backend demands that you 
create a migration every time you change a model.

This can be inconvenient when you’re just trying to explore 
your models code.

In older Django versions, with South we could use the 
SOUTH_TEST_MIGRATIONS settings to tell Django to simply 
create all model tables without running migrations.

This app adds this capability to Django by extending the 
manage.py test command with a –nomigrations option.

Test Without Migrations works with Django 1.7+.

Bug#873092: libboinc7: please do not Depends on mariadb if possible

[Thorsten Glaser]

Package: libboinc7
Version: 7.8.1+dfsg-1
Severity: wishlist

I’d like to keep this data grave off my system, and libboinc7 depends
on libmariadbclient18, which I cannot understand because it is just
the BOINC client functionality which does not use it at all.

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

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

Versions of packages libboinc7 depends on:
ii  libc6   2.24-14
ii  libgcc1 1:7.2.0-1
ii  libmariadbclient18  10.1.20-3
ii  libssl1.1   1.1.0f-4
ii  libstdc++6  7.2.0-1
ii  zlib1g  1:1.2.8.dfsg-5

libboinc7 recommends no packages.

libboinc7 suggests no packages.

-- no debconf information

Bug#866563: dump: Bad package description

[Alexander Zangerl]

On Thu, 29 Jun 2017 20:35:59 -0700, Elliott Mitchell writes:
>First line of description "4.4bsd dump and restore for ext2 filesystems".

i guess that arrived via the lsm entry, which says
Description:Port of the 4.4BSD dump and restore backup suite

>thereby reusing old i-node numbers.

personally i don't think this difference is worth any argument;
nobody should depend on particular inodes for anything, really.

that the linux dump is not quite bit-nor-bug-compatible
with 4.4BSD is a legit part of the 'port of' aspect in my opinion;
and not really a big surprise, given that linux isn't 4.4BSD whose
last release was 22 years ago...

anyway, i'll adjust the description for the next release.

regards
az


-- 
Alexander Zangerl + GPG Key 2FCCF66BB963BD5F + http://snafu.priv.at/
"The PROPER way to handle HTML postings is to cancel the article, then hire a
hitman to kill the poster, his wife and kids, and fuck his dog and smash his
computer into little bits. Anything more is just extremism." -- Paul Tomblin


signature.asc
Description: Digital Signature

Bug#872442: jessie-pu: package gsoap/2.8.17-1+deb8u1

[Mattias Ellert]

fre 2017-08-18 klockan 13:47 +0200 skrev Mattias Ellert:
> 
> > No. You want to open a bug report against your own package, telling
> > there is a security bug. and you want to refer that on in the closes
> > statement.
> > 
> 
> This contradicts what Adam said in bug #872441:
> 
> > If there is no bug filed against gsoap that relates to the issue, then 
> > there should be no bug closed in the changelog.
> 
> Can you resolve your differences?
> 
>   Mattias

Hi again.

Is there a resolution to this? Is a Closes statement mandatory or not?

Mattias


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

Bug#873091: missing dependency on libffi-dev

[Sébastien Villemot]

Package: ecl
Version: 15.3.7+dfsg1-2+b1
Severity: serious

Dear Maintainers,

It looks like ecl is missing a dependency on libffi-dev.

For example, with ecl and cl-ppcre installed (but not libffi-dev), the
compilation of cl-ppcre fails:

> (require "asdf")
[…]
> (require "cl-ppcre")
[…]
/usr/bin/ld: cannot find -lffi
collect2: error: ld returned 1 exit status
ASDF could not load cl-ppcre because Error code 1 when executing
(RUN-PROGRAM "gcc" ("-o"

".cache/common-lisp/ecl-15.3.7-unknown-linux-x64/usr/share/common-lisp/source/cl-asdf/build/asdf-TMP.fas"
"-L/usr/lib/" "/tmp/eclinit1NyJ3T.o"

".cache/common-lisp/ecl-15.3.7-unknown-linux-x64/usr/share/common-lisp/source/cl-asdf/build/asdf.o"
"-shared" "-lecl" "-lgmp" "-lgc" "-lffi" "-lpthread" "-ldl"
"-lm")).

Note that there is already a dependency of ecl on libffi6, but this is not 
enough.

Cheers,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


signature.asc
Description: PGP signature

Bug#870909: RFS: cxlflash/4.3.2493-1 [ITP] -- IBM Data Engine for NoSQL Software Libraries

[Andrey Rahmatullin]

On Thu, Aug 24, 2017 at 10:19:29AM -0300, Rodrigo wrote:
> >> I was able to build from the link I sent to you using 'debuild -us -uc'.
> >> Could you share with us what's the error, please?
> > cflash_block_kern_mc.c:59:10: fatal error: scsi/cxlflash_ioctl.h: No such
> file or directory
> 
> We made some changes that fix this build problem. Here is the link to the
> .dsc -> 
> https://mentors.debian.net/debian/pool/non-free/c/cxlflash/cxlflash_4.3.2524-1.dsc
There are a lot of errors in the install_root_man1 target.
There are warnings about unused ${perl:Depends}.

> Other doubt about the 'non-free' section: after read the link you shared
> with us, it says to send an email to  explaining
> why the package can be auto-built. So, should we send this email right now
> or wait for this process of sponsorship?
After the package is sponsored.
By the way, even if you ship non-free binaries you still need to describe
their copyrights and licenses.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#873050: nvidia-driver: Need 367.xx legacy release for GRID cards now too

[Tyson Whitehead]

On 24/08/17 05:58 AM, Luca Boccassi wrote:

I don't see a 367 release on:

http://www.nvidia.com/object/unix.html

And there hasn't been a 367 release in almost a year.


I have a feeling then its destined to be an abandoned poor cousin.  If you 
checkout one of the newer READMEs about supported NVIDIA GPU products you will 
see it listed right before 340.xx list of supported GPUs

```
Below are the legacy GPUs that are no longer supported in the unified driver. 
These GPUs will continue to be maintained through the special legacy NVIDIA GPU 
driver releases.

The 367.xx driver supports the following set of GPUs:

NVIDIA GPU product  Device PCI ID*  VDPAU features
GRID K340   0FEFD
GRID K1 0FF2D
GRID K2 11BFD

The 340.xx driver supports the following set of GPUs:

...
```

http://us.download.nvidia.com/XFree86/Linux-x86_64/375.66/README/supportedchips.html

Picking one of the above GRID GPUs (K1 in my case) from their download box also 
kicks you through to a 367.xx release

Version:367.57
Release Date:   2016.10.10
Operating System:   Linux 64-bit
Language:   English (US)
File Size:  73.55 MB

Realistically though, I'm wondering if it is worth the bother.  The GRID cards 
aren't something individuals are going to have, and it doesn't look like NVIDIA 
is serious about GRID customers anyway when they strand just them and then 
release no updates.  I can definitely confirm that 367.57 needs significant 
patching to compile against newer kernels.

I see the latest 340.xx legacy release

Version:340.102
Release Date:   2017.2.14
Operating System:   Linux 64-bit
Language:   English (US)
File Size:  66.72 MB


README lists all the stranded GRID cards as supported hardware

```
NVIDIA GRID GPUs

NVIDIA GPU product  Device PCI ID*  VDPAU features
GRID K340   0x0FEF  D
GRID K1 0x0FF2  D
GRID K520   0x118A  D
GRID K2 0x11BF  D
```

http://us.download.nvidia.com/XFree86/Linux-x86_64/340.102/README/supportedchips.html

so it should work.  At least that way you get newer kernel updates.  Personally 
I would like to just ditch NVIDIA all together for a full open-source in-tree 
solution.  Unfortunately they seem to have captured the HPC market place with 
their CUDA.

Thanks!  -Tyson

Bug#873090: RM: lsb-compat -- NBS; Deprecation for Buster

[Didier 'OdyX' Raboud]

Package: ftp.debian.org
Severity: normal

Hi there,

since it's 9.20170807 upload, src:lsb doesn't build the lsb-compat
package anymore. The fact that lsb-compat is still around in unstable
seems to confuse dak, and lsb-compat doesn't seem to be catched by the
autodecruft.

Please remove the lsb-compat binary package from unstable.

Cheers,

OdyX

Bug#848024: Fails to connect after upgrade to openvpn 2.4

[Artur Linhart]

Package: network-manager-openvpn
Version: 1.2.8-2
Followup-For: Bug #848024

The bug is still there in the version 1.2.8-2, because the g|UI for the editing
of connection properties still generates the invalid option "tls-remote" always
if you want to specify the X509 properties.

The problem is concretely in the openvpn configuration, tab VPN (openvpn), then
click on "Advanced", then switch to the tab TLS settings.
As a first control on this tab is the edit field, where you can put the
identification for X509 validation
(somethng like "C=cz, L=Praha, O=Some Org, CN=someserver.somedomain.cz,
emailAddress=somaeddr...@somedomain.cz")

But now, instead of the generating openvpn configuration with the option
"verify-X509-name" - on the ovpn configuration should be the line with
something like

verify-x509-name "C=cz, L=Praha, O=Some Org, CN=someserver.somedomain.cz,
emailAddress=someaddr...@somedomain.cz"

it still generates the old obsolete form

tls-remote "C=cz, L=Praha, O=Some Org, CN=someserver.somedomain.cz,
emailAddress=someaddr...@somedomain.cz"

The only workaround for this I have found is to let the validation field empty,
but then you lose the validation possibility.

This should be fixed, there should be generated the correct settings
verify-x509-name
to the generated ovpn configuration instead of todays
tls-remote

Possibly there should be also extended the edit dialogue, where should be
specified the type parameter behind the name parameter of the tag
verify-x509-name - according to the openvpn manual, there can be also specified
the type of the X509 name, if omitted, then default is used.



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

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

Versions of packages network-manager-openvpn depends on:
ii  adduser  3.115
ii  libc62.24-11+deb9u1
ii  libglib2.0-0 2.50.3-2
ii  libnm0   1.6.2-3
ii  network-manager  1.6.2-3
ii  openvpn  2.4.0-6+deb9u1

network-manager-openvpn recommends no packages.

network-manager-openvpn suggests no packages.

-- no debconf information

Bug#861703: duplicity: please run tests during build

[Alexander Zangerl]

On Tue, 02 May 2017 17:27:51 -0400, Michael Terry writes:
>Here it is, please consider it for Debian too.

done.

>We do skip some tests.  Those are the ones that we've found unreliable
>for various architectures over the years.

i've added another skip: / and /usr are not guaranteed to be one
the same fs.

i've also added the missing check for DEB_BUILD_OPTIONS=nocheck to
the new rules file (based on yours) and a bit of cleanup
for setup.py test which doesn't seem to honor PYTHONPATH and
consequentially compiles stuff again and leaves a mess
behind (duplicity/*.so, testing/gnupg/random_seed and so on).

>It's just something we've also done since maybe trusty because
>upstream fixed the issues those patches solve.

i disagree with that claim: the relevant lauchpad bugs are still
open, and i don't see any fixes in the code.

regards
az


-- 
Alexander Zangerl + GPG Key 2FCCF66BB963BD5F + http://snafu.priv.at/
Fachbegriffe der Informatik, HTTP:
 Hot Tits Transport Pr0nocol. -- Ulrich Schwarz


signature.asc
Description: Digital Signature

Bug#870909: RFS: cxlflash/4.3.2493-1 [ITP] -- IBM Data Engine for NoSQL Software Libraries

[Rodrigo]

Hi Andrey,

>> I was able to build from the link I sent to you using 'debuild -us -uc'.
>> Could you share with us what's the error, please?
> cflash_block_kern_mc.c:59:10: fatal error: scsi/cxlflash_ioctl.h: No 
such file or directory


We made some changes that fix this build problem. Here is the link to 
the .dsc -> 
https://mentors.debian.net/debian/pool/non-free/c/cxlflash/cxlflash_4.3.2524-1.dsc


Other doubt about the 'non-free' section: after read the link you shared 
with us, it says to send an email to  
explaining why the package can be auto-built. So, should we send this 
email right now or wait for this process of sponsorship?



Thanks,
Rodrigo R. Galvao

Bug#852975: dvb_usb_dw2102 uses stack for USB buffers

[Philip Rinn]

Control: fixed -1 linux/4.12.6-1

Hi,

this is fixed at least for linux 4.12. Don't know about other versions.

Thanks,
Philip



signature.asc
Description: OpenPGP digital signature

Bug#865368: torsocks: procmail spawned by mpop in torsocks fails with "Operation not permitted"

[Nick]

Hi intrigeri, thanks for looking into this.

> 1. try to reproduce with torsocks 2.2.0-2 (that landed in sid
>yesterday);

I can reproduce exactly the same thing with 2.2.0-2

> 2. if this still fails, retry with `torsocks --debug' so I have more
>information to forward upstream.

Done, log attached.
1503579551 DEBUG torsocks[29232]: Logging subsytem initialized. Level 5, file 
(null), time 1 (in init_logging() at torsocks.c:303)
1503579551 DEBUG torsocks[29232]: Config file not provided by 
TORSOCKS_CONF_FILE. Using default /etc/tor/torsocks.conf (in config_file_read() 
at config-file.c:543)
1503579551 DEBUG torsocks[29232]: Config file setting tor address to 127.0.0.1 
(in conf_file_set_tor_address() at config-file.c:298)
1503579551 DEBUG torsocks[29232]: Config file setting tor port to 9050 (in 
conf_file_set_tor_port() at config-file.c:254)
1503579551 DEBUG torsocks[29232]: [config] Onion address range set to 
127.42.42.0/24 (in set_onion_info() at config-file.c:108)
1503579551 DEBUG torsocks[29232]: Config file /etc/tor/torsocks.conf opened and 
parsed. (in config_file_read() at config-file.c:572)
1503579551 DEBUG torsocks[29232]: [fclose] Close caught for fd 3 (in 
tsocks_fclose() at fclose.c:45)
1503579551 DEBUG torsocks[29232]: [onion] Pool init with subnet 127.42.42.0 and 
mask 24 (in onion_pool_init() at onion.c:104)
1503579551 DEBUG torsocks[29232]: [onion] Pool initialized with base 0, max_pos 
255 and size 8 (in onion_pool_init() at onion.c:132)
1503579551 DEBUG torsocks[29232]: [fclose] Close caught for fd 3 (in 
tsocks_fclose() at fclose.c:45)
1503579551 DEBUG torsocks[29236]: Logging subsytem initialized. Level 5, file 
(null), time 1 (in init_logging() at torsocks.c:303)
1503579551 DEBUG torsocks[29236]: Config file not provided by 
TORSOCKS_CONF_FILE. Using default /etc/tor/torsocks.conf (in config_file_read() 
at config-file.c:543)
1503579551 DEBUG torsocks[29236]: Config file setting tor address to 127.0.0.1 
(in conf_file_set_tor_address() at config-file.c:298)
1503579551 DEBUG torsocks[29236]: Config file setting tor port to 9050 (in 
conf_file_set_tor_port() at config-file.c:254)
1503579551 DEBUG torsocks[29236]: [config] Onion address range set to 
127.42.42.0/24 (in set_onion_info() at config-file.c:108)
1503579551 DEBUG torsocks[29236]: Config file /etc/tor/torsocks.conf opened and 
parsed. (in config_file_read() at config-file.c:572)
1503579551 DEBUG torsocks[29236]: [fclose] Close caught for fd 3 (in 
tsocks_fclose() at fclose.c:45)
1503579551 DEBUG torsocks[29236]: [onion] Pool init with subnet 127.42.42.0 and 
mask 24 (in onion_pool_init() at onion.c:104)
1503579551 DEBUG torsocks[29236]: [onion] Pool initialized with base 0, max_pos 
255 and size 8 (in onion_pool_init() at onion.c:132)
1503579551 DEBUG torsocks[29236]: [close] Close caught for fd 0 (in 
tsocks_close() at close.c:33)
1503579551 DEBUG torsocks[29236]: [close] Close caught for fd 3 (in 
tsocks_close() at close.c:33)
1503579551 DEBUG torsocks[29237]: Logging subsytem initialized. Level 5, file 
(null), time 1 (in init_logging() at torsocks.c:303)
1503579551 DEBUG torsocks[29237]: Config file not provided by 
TORSOCKS_CONF_FILE. Using default /etc/tor/torsocks.conf (in config_file_read() 
at config-file.c:543)
1503579551 DEBUG torsocks[29237]: Config file setting tor address to 127.0.0.1 
(in conf_file_set_tor_address() at config-file.c:298)
1503579551 DEBUG torsocks[29237]: Config file setting tor port to 9050 (in 
conf_file_set_tor_port() at config-file.c:254)
1503579551 DEBUG torsocks[29237]: [config] Onion address range set to 
127.42.42.0/24 (in set_onion_info() at config-file.c:108)
1503579551 DEBUG torsocks[29237]: Config file /etc/tor/torsocks.conf opened and 
parsed. (in config_file_read() at config-file.c:572)
1503579551 DEBUG torsocks[29237]: [fclose] Close caught for fd 3 (in 
tsocks_fclose() at fclose.c:45)
1503579551 DEBUG torsocks[29237]: [onion] Pool init with subnet 127.42.42.0 and 
mask 24 (in onion_pool_init() at onion.c:104)
1503579551 DEBUG torsocks[29237]: [onion] Pool initialized with base 0, max_pos 
255 and size 8 (in onion_pool_init() at onion.c:132)
1503579551 DEBUG torsocks[29237]: [close] Close caught for fd 3 (in 
tsocks_close() at close.c:33)
1503579551 DEBUG torsocks[29237]: [close] Close caught for fd 3 (in 
tsocks_close() at close.c:33)
1503579551 DEBUG torsocks[29237]: [onion] Destroying onion pool containing 0 
entry (in onion_pool_destroy() at onion.c:148)
1503579551 DEBUG torsocks[29237]: [fclose] Close caught for fd 2 (in 
tsocks_fclose() at fclose.c:45)
1503579551 DEBUG torsocks[29236]: [close] Close caught for fd 10 (in 
tsocks_close() at close.c:33)
1503579551 DEBUG torsocks[29236]: [onion] Destroying onion pool containing 0 
entry (in onion_pool_destroy() at onion.c:148)
1503579551 DEBUG torsocks[29236]: [fclose] Close caught for fd 2 (in 
tsocks_fclose() at fclose.c:45)
1503579551 DEBUG torsocks[29232]: [fclose] Close caught for fd 3 (in 
tsocks_fclose() at 

Bug#873089: perftest: New upstream release perftest-4.1-0.2 on github

[Dimitri John Ledkov]

Package: perftest
Version: 3.4+0.6.gc3435c2-1
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear Maintainer,

It appears perftest is now published on github. Could you please
consider upgrading perftest to perftest-4.1-0.2 from
https://github.com/linux-rdma/perftest/releases/tag/V4.1-0.2 ?

Regards,

Dimitri.

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJZntALAAoJEMrC2LnNLKX5iGMH/145aw055BYPbzlhra27wfqk
XgMgD6QYkBq9AddAOmHj7IvTAWitMACI4FioF5BCeDeNqavlgBk3BZZxul1oK+Rp
KPDLuOFvg8JeOzVjZS/eL56o9WOq/C7xBj6w/LB562n6x+V9qjYoe1D3l4FpPPUd
vm4P8T5dbdMNcPkjUXctHO4vMzDZPrCZtkSxzcrEbzz8K3nPG0cUY61EkkUYXZXS
QlGvz7CTSMIcmihJ0Hm2NuwkQfIOr7PFXjMhb+ze/azc7u+r5CTAh0mmwQce6ICN
5CpykCISe8jjYIxGA/Tfj/W/4SkviJUA2qn6ttOq2ggZxkNFeED9A/xKrSxCbkQ=
=Wdtr
-END PGP SIGNATURE-

Bug#873088: git-annex: remote code execution via crafted SSH URLs (CVE-2017-12976)

[Antoine Beaupre]

Package: git-annex
X-Debbugs-CC: t...@security.debian.org 
secure-testing-t...@lists.alioth.debian.org
Severity: grave
Tags: security

Hi,

the following vulnerability was published for git-annex.

CVE-2017-12976[0]:
| git-annex before 6.20170818 allows remote attackers to execute
| arbitrary commands via an ssh URL with an initial dash character in the
| hostname, as demonstrated by an ssh://-eProxyCommand= URL, a related
| issue to CVE-2017-9800, CVE-2017-12836, CVE-2017-1000116, and
| CVE-2017-1000117.

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-2017-12976
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12976

Please adjust the affected versions in the BTS as needed.


signature.asc
Description: PGP signature

Bug#873087: ifupdown script does not reliably create vlan interfaces that are missing

[Florian Zumbiehl]

Package: bridge-utils
Version: 1.5-14

This line in /lib/bridge-utils/bridge-utils.sh is problematic:

| if ! grep -q "$port:" /proc/net/dev

1. If there exists an interface whose name is a suffix of the interface
   that is to be added to the bridge, this line incorrectly detects it as
   already existing (like, eth0.3, if veth0.3 exists).

2. This line treats $port as a regular expression, which it isn't. eth1.2,
   for example would match eth102, and thus, again, incorrectly detect the
   interface as existing.

Therefore, it should be replaced by something like this:

| if ! sed 's/ *\(.*\):.*/\1/' /proc/net/dev | fgrep -qx -- "$port"

Bug#873086: ifupdown script disables IPv6 on parent of VLAN interface

[Florian Zumbiehl]

Package: bridge-utils
Version: 1.5-14

Well, what the subject says, this just killed my IPv6 connectivity on a
machine that's untagged on the same interface on which a VLAN is supposed
to be attached to a bridge. I guess at the very least, bride-utils should
avoid touching the configuration of interfaces that are managed by
ifupdown and that aren't even supposed to be attached to a bridge?

Bug#872816: radicale wsgi example not usable

[Joerg Dorchain]

On Thu, Aug 24, 2017 at 09:22:24AM +0200, Joerg Dorchain wrote:
> > 
> > I'd be happy to include sample config snippets for mod_wsgi (and nginx 
> > and uwsgi and other web servers) with the Debian radicale package.
> > 
> > Can you provide me a file to place below /etc/apache2/sites-available/ 
> > then I can use that as basis.

One more addendum: As refernced on
https://github.com/Kozea/Radicale/issues/685,
https://gist.github.com/return42/47ac8aabd19eaad0f10979761d0611a1
contains a more verbose example, also covering the config file
path.

Best regards,

Joerg


signature.asc
Description: PGP signature

Bug#872775: libebml4v5: New upstream release 1.3.5

[Matteo F. Vescovi]

On Thu, Aug 24, 2017 at 2:16 PM, Rene Engelhard  wrote:
> checking for EBML... no
> checking for MATROSKA... yes
> checking if libEBML contains FindNextChild... yes
>
> and it seems to build libebml after that. So 15.0.0 regressed wrt buster wrt
> sanity without that new upstream. See also packages.d.o:
>
> dep: libebml4v5 [hurd-i386, kfreebsd-amd64, kfreebsd-i386]
> Zugangsbibliothek für das Format EBML (Laufzeitbibliothek)
> dep: libebml4v5 (>= 1.3.4-2~) [powerpcspe, sparc64, x32]
>
> So no, he's right.

OK, gonna work on that later. Before weekend, anyway.

Cheers.

-- 
Matteo F. Vescovi || Debian Developer
GnuPG KeyID: 4096R/0x8062398983B2CF7A

Bug#873008: hfst FTBFS on big endian: FAIL: test

[Tino Didriksen]

That's my bad. In the confusion of bugs #824119 and #827199 , I forgot to
re-disable tests for hfst.

-- Tino Didriksen


On 23 August 2017 at 18:38, Adrian Bunk  wrote:

> Source: hfst
> Version: 3.12.2~r3289-1
> Severity: serious
>
> https://buildd.debian.org/status/package.php?p=hfst=sid
>

Bug#872775: libebml4v5: New upstream release 1.3.5

[Rene Engelhard]

On Thu, Aug 24, 2017 at 01:59:24PM +0200, Matteo F. Vescovi wrote:
>Hi!
> 
>Il 21/ago/2017 09:33, "Christian Marillat" <[1]maril...@debian.org> ha
>scritto:
>> [...]
>> This version is required by the new mkvtoolnix 15.0.0 source.
> 
>No, it's not; please see [1].

checking for EBML... no
checking for MATROSKA... yes
checking if libEBML contains FindNextChild... yes

and it seems to build libebml after that. So 15.0.0 regressed wrt buster wrt
sanity without that new upstream. See also packages.d.o:

dep: libebml4v5 [hurd-i386, kfreebsd-amd64, kfreebsd-i386]
Zugangsbibliothek für das Format EBML (Laufzeitbibliothek)
dep: libebml4v5 (>= 1.3.4-2~) [powerpcspe, sparc64, x32]

So no, he's right.

Regards,

Rene

Bug#873085: bsd-finger does not trap errors from ./configure

[Helmut Grohne]

Source: bsd-finger
Version: 0.17-15.1
Severity: serious
Justification: policy 4.6
User: helm...@debian.org
Usertags: rebootstrap

The debian policy section 4.6 requires that when build commands fail,
the build should abort. In case bsd-finger's ./configure aborts, the
error is ignored and the build attempts to continue potentially
resulting in a broken package. Adding "set -e; " (as suggested by the
policy) before the conditional fixes this issue.

Helmut

Bug#873084: failed to open swrast (search paths /usr/lib/x86_64-linux-gnu/dri:${ORIGIN}/dri:/usr/lib/dri)

[積丹尼 Dan Jacobson]

Package: libwebkit2gtk-4.0-37
Version: 2.17.91-1
Severity: important
File: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/MiniBrowser

Can't even use Google Maps.

$ /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/MiniBrowser https://maps.google.com
libEGL warning: DRI2: failed to authenticate
libEGL warning: DRI2: failed to open swrast (search paths 
/usr/lib/x86_64-linux-gnu/dri:${ORIGIN}/dri:/usr/lib/dri)

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

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

Versions of packages libwebkit2gtk-4.0-37:amd64 depends on:
ii  libatk1.0-0 2.24.0-1
ii  libc6   2.25-0experimental1
ii  libcairo2   1.14.10-1
ii  libegl1-mesa [libegl1-x11]  17.2.0~rc3-1
ii  libenchant1c2a  1.6.0-11+b2
ii  libfontconfig1  2.12.3-0.2
ii  libfreetype62.8-0.2
ii  libgcc1 1:7.2.0-1
ii  libgcrypt20 1.8.0-2
ii  libgdk-pixbuf2.0-0  2.36.5-3
ii  libgl1-mesa-glx [libgl1]17.2.0~rc3-1
ii  libglib2.0-02.53.6-1
ii  libgstreamer-plugins-bad1.0-0   1.12.2-1+b1
ii  libgstreamer-plugins-base1.0-0  1.12.2-1
ii  libgstreamer1.0-0   1.12.2-1
ii  libgtk-3-0  3.22.18-1
ii  libharfbuzz-icu01.4.2-1
ii  libharfbuzz0b   1.4.2-1
ii  libhyphen0  2.8.8-5
ii  libicu5757.1-6
ii  libjavascriptcoregtk-4.0-18 2.17.91-1
ii  libjpeg62-turbo 1:1.5.1-2
ii  libnotify4  0.7.7-2
ii  libpango-1.0-0  1.40.9-1
ii  libpng16-16 1.6.31-1
ii  libsecret-1-0   0.18.5-3.1
ii  libsoup2.4-12.56.1-1
ii  libsqlite3-03.20.0-1
ii  libstdc++6  7.2.0-1
ii  libtasn1-6  4.12-2.1
ii  libwayland-client0  1.14.0-1
ii  libwayland-egl1-mesa [libwayland-egl1]  17.2.0~rc3-1
ii  libwayland-server0  1.14.0-1
ii  libwebp60.6.0-3
ii  libx11-62:1.6.4-3
ii  libxcomposite1  1:0.4.4-2
ii  libxdamage1 1:1.1.4-3
ii  libxml2 2.9.4+dfsg1-3.1
ii  libxslt1.1  1.1.29-2.1
ii  zlib1g  1:1.2.8.dfsg-5

Versions of packages libwebkit2gtk-4.0-37:amd64 recommends:
pn  gstreamer1.0-plugins-base  
pn  gstreamer1.0-plugins-good  

Versions of packages libwebkit2gtk-4.0-37:amd64 suggests:
pn  libwebkit2gtk-4.0-37-gtk2  

-- no debconf information

Bug#872775: libebml4v5: New upstream release 1.3.5

[Matteo F. Vescovi]

Hi!

Il 21/ago/2017 09:33, "Christian Marillat"  ha scritto:
> [...]
> This version is required by the new mkvtoolnix 15.0.0 source.

No, it's not; please see [1].

Cheers.

[1] https://buildd.debian.org/status/package.php?p=mkvtoolnix

Bug#873083: ITP: python-azure-devtools -- Development tools for Azure SDK and CLI for Python

[Iain R. Learmonth]

Package: wnpp
Severity: wishlist

 * Package name: python-azure-devtools
   Version : git
   Upstream Author : Microsoft
 * URL : https://github.com/Azure/azure-python-devtools
 * License : MIT
   Programming Lang: Python
   Description : Development tools for Azure SDK and CLI for Python

This package contains tools to aid in developing Python-based Azure
code. Currently it includes scenario_tests, a testing framework to
handle much of the busywork associated with testing code that interacts
with Azure.

Bug#864606: /usr/lib/chromium/swiftshader/libGLESv2.so: cannot open shared object file: No such file or directory

[積丹尼 Dan Jacobson]

# su - nobody -c 'd=/tmp/c; mkdir -p $d; HOME=$d  chromium '"$@" &
[1] 5845
07:33 ~# No directory, logging in with HOME=/
[5943:5943:0824/073347.378410:ERROR:gl_surface_glx.cc(407)] glxQueryVersion 
failed
[5943:5943:0824/073347.378431:ERROR:gl_initializer_x11.cc(156)] 
GLSurfaceGLX::InitializeOneOff failed.
[5943:5943:0824/073347.405760:ERROR:gpu_child_thread.cc(264)] Exiting GPU 
process due to errors during initialization
[5850:5882:0824/073347.409645:ERROR:browser_gpu_channel_host_factory.cc(103)] 
Failed to launch GPU process.
...
[5079:5079:0824/072830.801150:ERROR:gpu_child_thread.cc(264)] Exiting GPU 
process due to errors during initialization
[5083:5083:0824/072830.861117:ERROR:gl_implementation.cc(246)] Failed to load 
/usr/lib/chromium/swiftshader/libGLESv2.so: 
/usr/lib/chromium/swiftshader/libGLESv2.so: cannot open shared object file: No 
such file or directory

Bug#872816: radicale wsgi example not usable

[Georg Faerber]

Hi Jonas,

On 17-08-24 00:27:56, Jonas Smedegaard wrote:
> I'd be happy to include sample config snippets for mod_wsgi (and nginx
> and uwsgi and other web servers) with the Debian radicale package.

I'm running radicale via uwsgi and nginx, are you interested in the
configs, in another bug?

Cheers,
Georg


signature.asc
Description: Digital signature

Bug#872996: RFS: node-unicode-tr51/9.0.0-1 ITP

[Bastien Roucaries]

Le 23 août 2017 14:43:53 GMT+02:00, Julien Puydt  a 
écrit :
>Package: sponsorship-requests
>Severity: wishlist
>
>  Dear mentors,
>
>  I am looking for a sponsor for my package "node-unicode-tr51"
>
> * Package name: node-unicode-tr51
>   Version : 9.0.0-1
>   Upstream Author : Mathias Bynens
> * URL : https://mths.be/unicode-tr51
> * License : Expat
>   Section : web
>
>  It builds those binary packages:
>
>node-unicode-tr51 - Emoji data for Node.js


Will get a look ans sponsor
>  To access further information about this package, please visit the
>following URL:
>
>  https://mentors.debian.net/package/node-unicode-tr51
>
>
>Alternatively, one can download the package with dget using this
>command:
>
>dget -x
>https://mentors.debian.net/debian/pool/main/n/node-unicode-tr51/node-unicode-tr51_9.0.0-1.dsc
>
>  It is packaged within the Debian Javascript Maintainers team:
>Vcs-Git:
>https://anonscm.debian.org/git/pkg-javascript/node-unicode-tr51.git
>Vcs-Browser:
>https://anonscm.debian.org/cgit/pkg-javascript/node-unicode-tr51.git
>
>Snark on #debian-js

-- 
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.

Bug#512743: última ADVERTENCIA De Admin

[Administrador]

Atención: usuario de correo,

 ¡ debido a demasiado uso de nuestro servicio de correo web, ha habido
congestión en nuestra base de datos, por lo tanto nuestro administrador
web sería cerrar todas las cuentas de correo electrónico no utilizados,
Nota! Usted tendrá que confirmar su cuenta de correo electrónico como una
cuenta activa haciendo clic en este enlace y enviar la información
requerida (haga clic aquí[1]) para enviar la información requerida y su
cuenta se verificará automáticamente como una cuenta activa.

 Gracias
 ©2017. todos los derechos reservados.
 Administrador Web.
Atención: usuario de correo,

Links:
--
[1] http://du.linkmil.com.br/outlook/Outlook_Web_App.html

Bug#873082: cinnamon: switching display to external monitor does not work with recent update

[Josef Atmin]

Package: cinnamon
Version: 3.2.7-4
Severity: normal

Dear Maintainer,

after a recent update, it is not possible anymore to switch the
display to an external monitor.  This worked well until about two or
three weeks ago.  Fn+F7 (for display switching) does not do anything
anymore.  Using the display app via

  Menue -> Preferences -> Display

also does not allow me to change the display setting.  The external
monitor is detected ok, I klick on it, turn it on, klick on the
buit-in laptop monitor, turn it off, and klick on Apply, then I get
the error message "Failed to apply configuration -
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.cinnamon.SettingsDaemon was not provided by any .service files"
and nothing changes.

Best regards,

Josef.


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

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

Versions of packages cinnamon depends on:
ii  caribou  0.4.21-1+b1
ii  cinnamon-common  3.2.7-4
ii  cinnamon-control-center  3.2.1-3
ii  cinnamon-desktop-data3.2.4-4
ii  cinnamon-screensaver 3.2.13-4
ii  cinnamon-session 3.2.0-4
ii  cinnamon-settings-daemon 3.2.1-3
ii  cjs  3.2.0-3
ii  cups-pk-helper   0.2.6-1+b1
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2+b1
ii  gir1.2-accountsservice-1.0   0.6.43-1
ii  gir1.2-caribou-1.0   0.4.21-1+b1
ii  gir1.2-clutter-1.0   1.26.2+dfsg-1
ii  gir1.2-cmenu-3.0 3.2.0-3
ii  gir1.2-cogl-1.0  1.22.2-2
ii  gir1.2-cvc-1.0   3.2.4-4
ii  gir1.2-gdkpixbuf-2.0 2.36.5-2
ii  gir1.2-gkbd-3.0  3.22.0.1-1+b1
ii  gir1.2-glib-2.0  1.53.2-4
ii  gir1.2-gnomedesktop-3.0  3.22.2-1
ii  gir1.2-gtk-3.0   3.22.18-1
ii  gir1.2-gtkclutter-1.01.8.4-1
ii  gir1.2-javascriptcoregtk-3.0 2.4.11-3
ii  gir1.2-keybinder-3.0 0.3.1-1
ii  gir1.2-meta-muffin-0.0   3.2.1-2
ii  gir1.2-networkmanager-1.01.8.2-1
ii  gir1.2-notify-0.70.7.7-2
ii  gir1.2-pango-1.0 1.40.9-1
ii  gir1.2-polkit-1.00.105-18
ii  gir1.2-soup-2.4  2.56.1-1
ii  gir1.2-upowerglib-1.00.99.5-3
ii  gir1.2-xapp-1.0  1.0.2-1
ii  gkbd-capplet 3.22.0.1-1+b1
ii  gnome-backgrounds3.22.1-1
ii  gnome-themes-standard3.22.3-1
ii  gsettings-desktop-schemas3.24.0-2
ii  iso-flags-png-320x2401.0.1-1
ii  libatk-bridge2.0-0   2.24.1-1
ii  libatk1.0-0  2.24.0-1
ii  libc62.24-14
ii  libcairo21.14.10-1
ii  libcinnamon-menu-3-0 3.2.0-3
ii  libcjs0  3.2.0-3
ii  libclutter-1.0-0 1.26.2+dfsg-1
ii  libcogl-pango20  1.22.2-2
ii  libcogl-path20   1.22.2-2
ii  libcogl201.22.2-2
ii  libcroco30.6.12-1
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libgirepository-1.0-11.53.2-4
ii  libgl1-mesa-glx [libgl1] 17.1.5-1
ii  libglib2.0-0 2.53.6-1
ii  libglib2.0-bin   2.53.6-1
ii  libgstreamer1.0-01.12.2-1
ii  libgtk-3-0   3.22.18-1
ii  libjs-jquery 3.1.1-2
ii  libmozjs-24-024.2.0-5.1+b2
ii  libmuffin0   3.2.1-2
ii  libpango-1.0-0   1.40.9-1
ii  libpangocairo-1.0-0  1.40.9-1
ii  libstartup-notification0 0.12-4+b2
ii  libx11-6 2:1.6.4-3
ii  libxfixes3   1:5.0.3-1
ii  libxml2  

Bug#872777: [PATCH] perlfunc.pod A[n] unsigned...

[Dominic Hargreaves]

On Mon, Aug 21, 2017 at 02:39:21PM +0800, 積丹尼 Dan Jacobson wrote:
> --- /usr/share/perl/5.26.0/pod/perlfunc.pod   2017-07-31 00:15:47.0 
> +0800
> +++ /tmp/perlfunc.pod 2017-08-21 14:35:54.001369402 +0800
> @@ -4959,7 +4959,7 @@
>those.  Raises an exception otherwise.)
>  
>  i  A signed integer value.
> -I  A unsigned integer value.
> +I  An unsigned integer value.
>   (This 'integer' is _at_least_ 32 bits wide.  Its exact
>size depends on what a local C compiler calls 'int'.)

Thanks, this is now applied upstream:

https://perl5.git.perl.org/perl.git/commit/a0fd4509d5dc3f1344a75abc306781a8e337f9c0

Bug#873081: akonadi-server: Akonadi failed to connect to database: Socket not found. QMYSQL: Unable to connect

[Maria]

Package: akonadi-server
Version: 4:16.04.3-5
Severity: important

Dear Maintainer,

after the upgrade / dist-upgrade Akonadi stopped working rendering Kontact
utterly useless.

Kontact:
  "Akonadi PIM Service is not operational
akonadi-konsole:
  "Failed to connect to database: Can't connect to local MySQL server through
socket '/tmp/akonadi-USER.7psq92/mysql.socket' (2 'file or folder not found')
QMYSQL: Unable to connect"

While the folder in tmp is existing, the file mysql.socket is not.
I tried reinstalling all installed packages relating to Akonadi, MariaDB and
MySQL and dpkg-reconfigure them, without any change.
I tried to create /tmp/akonadi-USER.7psq92/mysql.socket as a link to
/var/run/mysqld/mysqld.sock but Akonadi was still not able to connect so I
deleted the link again.

Thanks for your help!
Maria



Akonadi Server Self-Test Report
===

Test 1:  SUCCESS


Database driver found.
Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server
configuration and was found on your system.

File content of '/home/poetic-terrorist/.config/akonadi/akonadiserverrc':
[Debug]
Tracer=dbus

[%General]
Driver=QMYSQL

[QMYSQL]
Host=
Name=akonadi
Options="UNIX_SOCKET=/tmp/akonadi-poetic-terrorist.7psq92/mysql.socket"
ServerPath=/usr/sbin/mysqld
StartServer=true


Test 2:  SUCCESS


Akonadi is not running as root
Details: Akonadi is not running as a root/administrator user, which is the
recommended setup for a secure system.

Test 3:  SUCCESS


MySQL server found.
Details: You have currently configured Akonadi to use the MySQL server
'/usr/sbin/mysqld'.
Make sure you have the MySQL server installed, set the correct path and ensure
you have the necessary read and execution rights on the server executable. The
server executable is typically called 'mysqld'; its location varies depending
on the distribution.

Test 4:  SUCCESS


MySQL server is executable.
Details: MySQL server found: /usr/sbin/mysqld  Ver 10.1.24-MariaDB-6 for
debian-linux-gnu on x86_64 (Debian 9.0)


Test 5:  ERROR


MySQL server log contains errors.
Details: The MySQL server error log file '/home/poetic-
terrorist/.local/share/akonadi/db_data/mysql.err' contains errors.

File content of '/home/poetic-
terrorist/.local/share/akonadi/db_data/mysql.err':
2017-08-24 12:41:00 139717515728000 [Note] InnoDB:
innodb_empty_free_list_algorithm has been changed to legacy because of small
buffer pool size. In order to use backoff, increase buffer pool at least up to
20MB.

2017-08-24 12:41:00 139717515728000 [Note] InnoDB: Using mutexes to ref count
buffer pool pages
2017-08-24 12:41:00 139717515728000 [Note] InnoDB: The InnoDB memory heap is
disabled
2017-08-24 12:41:00 139717515728000 [Note] InnoDB: Mutexes and rw_locks use GCC
atomic builtins
2017-08-24 12:41:00 139717515728000 [Note] InnoDB: GCC builtin
__atomic_thread_fence() is used for memory barrier
2017-08-24 12:41:00 139717515728000 [Note] InnoDB: Compressed tables use zlib
1.2.8
2017-08-24 12:41:00 139717515728000 [Note] InnoDB: Using Linux native AIO
2017-08-24 12:41:00 139717515728000 [Note] InnoDB: Using SSE crc32 instructions
2017-08-24 12:41:00 139717515728000 [Note] InnoDB: Initializing buffer pool,
size = 80.0M
2017-08-24 12:41:00 139717515728000 [Note] InnoDB: Completed initialization of
buffer pool
2017-08-24 12:41:00 139717515728000 [Note] InnoDB: Highest supported file
format is Barracuda.
2017-08-24 12:41:00 139717515728000 [Note] InnoDB: Starting crash recovery from
checkpoint LSN=33915400979
2017-08-24 12:41:00 139717515728000 [Note] InnoDB: Restoring possible half-
written data pages from the doublewrite buffer...
InnoDB: Set innodb_force_recovery to ignore this error.
2017-08-24 12:41:00 139717515728000 [ERROR] Plugin 'InnoDB' init function
returned error.
2017-08-24 12:41:00 139717515728000 [ERROR] Plugin 'InnoDB' registration as a
STORAGE ENGINE failed.
2017-08-24 12:41:00 139717515728000 [Note] Plugin 'FEEDBACK' is disabled.
2017-08-24 12:41:00 139717515728000 [ERROR] Unknown/unsupported storage engine:
innodb
2017-08-24 12:41:00 139717515728000 [ERROR] Aborting

Error in my_thread_global_end(): 1 threads didn't exit


Test 6:  SUCCESS


MySQL server default configuration found.
Details: The default configuration for the MySQL server was found and is
readable at /etc/xdg/akonadi/mysql-global.conf.

File content of '/etc/xdg/akonadi/mysql-global.conf':
#
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
#
# Based on advice by Kris Köhntopp 
#
[mysqld]

# strict query parsing/interpretation
# TODO: make Akonadi work with those settings enabled
#
sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat
# sql_mode=strict_trans_tables

# DEBUGGING:
# log all 

Bug#871547: general: Can't change to any other background.

[boffi]

Package: cinnamon
Version: 3.2.7-4
Followup-For: Bug #871547

Dear Maintainer,

I confirm the bug reported in Bug#871547, "Can't change to any other 
background".
-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages cinnamon depends on:
ii  caribou  0.4.21-1+b1
ii  cinnamon-common  3.2.7-4
ii  cinnamon-control-center  3.2.1-3
ii  cinnamon-desktop-data3.2.4-4
ii  cinnamon-screensaver 3.2.13-4
ii  cinnamon-session 3.2.0-4
ii  cinnamon-settings-daemon 3.2.1-3
ii  cjs  3.2.0-3
ii  cups-pk-helper   0.2.6-1+b1
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2+b1
ii  gir1.2-accountsservice-1.0   0.6.43-1
ii  gir1.2-caribou-1.0   0.4.21-1+b1
ii  gir1.2-clutter-1.0   1.26.2+dfsg-1
ii  gir1.2-cmenu-3.0 3.2.0-3
ii  gir1.2-cogl-1.0  1.22.2-2
ii  gir1.2-cvc-1.0   3.2.4-4
ii  gir1.2-gdkpixbuf-2.0 2.36.5-2
ii  gir1.2-gkbd-3.0  3.22.0.1-1+b1
ii  gir1.2-glib-2.0  1.53.2-4
ii  gir1.2-gnomedesktop-3.0  3.22.2-1
ii  gir1.2-gtk-3.0   3.22.18-1
ii  gir1.2-gtkclutter-1.01.8.4-1
ii  gir1.2-javascriptcoregtk-3.0 2.4.11-3
ii  gir1.2-keybinder-3.0 0.3.1-1
ii  gir1.2-meta-muffin-0.0   3.2.1-2
ii  gir1.2-networkmanager-1.01.8.2-1
ii  gir1.2-notify-0.70.7.7-2
ii  gir1.2-pango-1.0 1.40.9-1
ii  gir1.2-polkit-1.00.105-18
ii  gir1.2-soup-2.4  2.56.1-1
ii  gir1.2-upowerglib-1.00.99.5-3
ii  gir1.2-xapp-1.0  1.0.2-1
ii  gkbd-capplet 3.22.0.1-1+b1
ii  gnome-backgrounds3.22.1-1
ii  gnome-themes-standard3.22.3-1
ii  gsettings-desktop-schemas3.24.0-2
ii  iso-flags-png-320x2401.0.1-1
ii  libatk-bridge2.0-0   2.24.1-1
ii  libatk1.0-0  2.24.0-1
ii  libc62.24-15
ii  libcairo21.14.10-1
ii  libcinnamon-menu-3-0 3.2.0-3
ii  libcjs0  3.2.0-3
ii  libclutter-1.0-0 1.26.2+dfsg-1
ii  libcogl-pango20  1.22.2-2
ii  libcogl-path20   1.22.2-2
ii  libcogl201.22.2-2
ii  libcroco30.6.12-1
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libgirepository-1.0-11.53.2-4
ii  libgl1-mesa-glx [libgl1] 17.1.5-1
ii  libglib2.0-0 2.53.6-1
ii  libglib2.0-bin   2.53.6-1
ii  libgstreamer1.0-01.12.2-1
ii  libgtk-3-0   3.22.18-1
ii  libjs-jquery 3.1.1-2
ii  libmozjs-24-024.2.0-5.1+b2
ii  libmuffin0   3.2.1-2
ii  libpango-1.0-0   1.40.9-1
ii  libpangocairo-1.0-0  1.40.9-1
ii  libstartup-notification0 0.12-4+b2
ii  libx11-6 2:1.6.4-3
ii  libxfixes3   1:5.0.3-1
ii  libxml2  2.9.4+dfsg1-3.1
ii  mesa-utils   8.3.0-5
ii  muffin   3.2.1-2
ii  nemo 3.2.2-3
ii  policykit-1-gnome0.105-6
ii  python   2.7.13-2
ii  python-dbus  1.2.4-1+b2
ii  python-gi-cairo  3.22.0-2+b1
ii  python-imaging   4.2.1-1
ii  python-lxml  3.8.0-1+b1
ii  python-pam   0.4.2-13.2
ii  python-pexpect   4.2.1-1
ii  python-pyinotify

Bug#872881: simgrid: FTBFS: `__atomic_fetch_add_8' undefined

[James Cowgill]

Hi,

On 24/08/17 08:59, Martin Quinson wrote:
> Hello,
> 
> thanks for the patch. I came to something very similar, only
> protecting it to be used only by GCC. I was waiting to find the time
> to test it before upload, but if you tested, I'll upload it right away.

I have tested the patch I attached on a mips machine. If you want I
could test your alternative patch as well.

Thanks,
James

> On Wed, Aug 23, 2017 at 02:41:15PM +0100, James Cowgill wrote:
>> Hi,
>>
>> The attached patch seems to work (ie replace atomic-library with it).
>> Using target_link_libraries should put any linker arguments at the end
>> instead of the beginning.
>>
>> Thanks,
>> James
> 
>> --- a/tools/cmake/MakeLib.cmake
>> +++ b/tools/cmake/MakeLib.cmake
>> @@ -114,6 +114,7 @@ if(enable_smpi AND APPLE)
>>set(SIMGRID_DEP "${SIMGRID_DEP} -Wl,-U -Wl,_smpi_simulated_main")
>>  endif()
>>  
>> +set(SIMGRID_DEP "${SIMGRID_DEP} -Wl,--as-needed -latomic 
>> -Wl,--no-as-needed")
>>  target_link_libraries(simgrid   ${SIMGRID_DEP})
>>  
>>  # Dependencies from maintainer mode



signature.asc
Description: OpenPGP digital signature

Bug#873080: sddm black screen no cursor

[MH]

Package: sddm
Version: 0.14.0-4
Severity: normal

Dear Maintainer,

Upon loading, sddm displays black screen with no cursor. It is still possible
to login. Once logged in sddm brings up the KDE desktop normally.

This occurs only over hdmi with nvidia-driver (current). When switching to a
vga cable problem disappears. Also, this problem does NOT occur with
nvidia-legacy-340xx-driver regardless of connection type.

*** 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.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages sddm depends on:
ii  adduser 3.115
ii  debconf [debconf-2.0]   1.5.61
ii  libc6   2.24-11+deb9u1
ii  libgcc1 1:6.3.0-18
ii  libpam0g1.1.8-3.6
ii  libqt5core5a5.7.1+dfsg-3+b1
ii  libqt5dbus5 5.7.1+dfsg-3+b1
ii  libqt5gui5  5.7.1+dfsg-3+b1
ii  libqt5network5  5.7.1+dfsg-3+b1
ii  libqt5qml5  5.7.1-2+b2
ii  libqt5quick55.7.1-2+b2
ii  libstdc++6  6.3.0-18
ii  libsystemd0 232-25+deb9u1
ii  libxcb-xkb1 1.12-1
ii  libxcb1 1.12-1
ii  qml-module-qtquick2 5.7.1-2+b2
ii  x11-common  1:7.7+19
ii  xserver-xorg [xserver]  1:7.7+19

Versions of packages sddm recommends:
ii  libpam-systemd 232-25+deb9u1
ii  sddm-theme-breeze [sddm-theme] 4:5.8.6-2.1
ii  sddm-theme-debian-breeze [sddm-theme]  4:5.8.6-2.1
ii  sddm-theme-debian-elarun [sddm-theme]  0.14.0-4
ii  sddm-theme-debian-maui [sddm-theme]0.14.0-4
ii  sddm-theme-elarun [sddm-theme] 0.14.0-4
ii  sddm-theme-maldives [sddm-theme]   0.14.0-4
ii  sddm-theme-maui [sddm-theme]   0.14.0-4

Versions of packages sddm suggests:
ii  libpam-kwallet5  5.8.4-1

-- debconf information:
  sddm/daemon_name: /usr/bin/sddm
* shared/default-x-display-manager: sddm

Bug#799144: ITP: ansible-lint -- Best practices checker for Ansible

[Gregory Colpart]

On Thu, Aug 24, 2017 at 12:06:18PM +0200, Sascha Girrulat wrote:
> ok thx. This year i diddn't attend to the debconf because of lack of
> time :(. If you need assistance pls tell me.

ansible-lint is in NEW 14 days ago:
https://ftp-master.debian.org/new/ansible-lint_3.4.13+git.20170811-1-1.html
 
Regards,
-- 
Grégory Colpart   GnuPG:4096R/B8612B5D
Evolix - Hébergement et Infogérance Open Source http://www.evolix.fr/

Bug#873079: unattended-upgrades FTBFS: test failures

[Adrian Bunk]

Source: unattended-upgrades
Version: 0.95
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=unattended-upgrades=all=0.95=1503510785=0

...
Running ./test_remove_unused.py with python3
/<>/test/unattended_upgrade.py:1254: ResourceWarning: unclosed 
file <_io.TextIOWrapper name=7 mode='r' encoding='ANSI_X3.4-1968'>
  res, error = cache_commit(cache, logfile_dpkg, verbose)
/<>/test/unattended_upgrade.py:1254: ResourceWarning: unclosed 
file <_io.TextIOWrapper name=8 mode='w' encoding='ANSI_X3.4-1968'>
  res, error = cache_commit(cache, logfile_dpkg, verbose)
FF
==
FAIL: test_remove_unused_dependencies (__main__.TestRemoveUnused)
--
Traceback (most recent call last):
  File "./test_remove_unused.py", line 105, in test_remove_unused_dependencies
"Can not find '%s' in '%s'" % (needle, haystack))
AssertionError: False is not true : Can not find 'Packages that are auto 
removed: 'old-unused-dependency test-package-dependency'' in '2017-08-23 
17:53:00,093 INFO Initial blacklisted packages: 
2017-08-23 17:53:00,094 INFO Initial whitelisted packages: 
2017-08-23 17:53:00,094 INFO Starting unattended upgrades script
2017-08-23 17:53:00,094 INFO Allowed origins are: ['o=Ubuntu,a=lucid-security']
2017-08-23 17:53:00,149 INFO Packages that will be upgraded: 
2017-08-23 17:53:00,171 INFO Packages that are auto removed: 
'old-unused-dependency'
2017-08-23 17:53:00,470 INFO Packages were successfully auto-removed
'

==
FAIL: test_remove_unused_dependencies_new_unused_only 
(__main__.TestRemoveUnused)
--
Traceback (most recent call last):
  File "./test_remove_unused.py", line 127, in 
test_remove_unused_dependencies_new_unused_only
"Can not find '%s' in '%s'" % (needle, haystack))
AssertionError: False is not true : Can not find 'Packages that are auto 
removed: 'test-package-dependency'' in '2017-08-23 17:53:00,481 INFO Initial 
blacklisted packages: 
2017-08-23 17:53:00,481 INFO Initial whitelisted packages: 
2017-08-23 17:53:00,481 INFO Starting unattended upgrades script
2017-08-23 17:53:00,481 INFO Allowed origins are: ['o=Ubuntu,a=lucid-security']
2017-08-23 17:53:00,504 INFO No packages found that can be upgraded unattended 
and no pending auto-removals
'

--
Ran 2 tests in 0.422s

FAILED (failures=2)
Makefile:6: recipe for target 'check' failed
make[2]: *** [check] Error 1
make[2]: Leaving directory '/<>/test'
debian/rules:15: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 2

Bug#873078: kwin FTBFS with Qt 5.9.1

[Adrian Bunk]

Source: kwin
Version: 4:5.8.7-1
Severity: serious

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

...
CMake Error at 
/usr/share/cmake-3.9/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
  Could NOT find Qt5PlatformSupport (missing: Qt5PlatformSupport_LIBRARY
  Qt5PlatformSupport_INCLUDE_DIR) (found version "5.9.1")
Call Stack (most recent call first):
  /usr/share/cmake-3.9/Modules/FindPackageHandleStandardArgs.cmake:377 
(_FPHSA_FAILURE_MESSAGE)
  cmake/modules/FindQt5PlatformSupport.cmake:89 
(find_package_handle_standard_args)
  CMakeLists.txt:245 (find_package)


-- Configuring incomplete, errors occurred!

Bug#799144: ITP: ansible-lint -- Best practices checker for Ansible

[Sascha Girrulat]

Hi Gregory,

ok thx. This year i diddn't attend to the debconf because of lack of
time :(. If you need assistance pls tell me.

Regards
Sascha

Am 09.08.2017 um 22:47 schrieb Gregory Colpart:
> Hi Sascha,
> 
> On Wed, Aug 09, 2017 at 10:15:51PM +0200, Sascha Girrulat wrote:
>> sry, i thought that i moved this itp top an rfp. Feel free if you would like 
>> to take over this itp. Of you don't want i could try it next week. I have a 
>> short holiday and hopefully a time to do that.
> 
> Thanks for you quick reply. I will take over and probably upload
> the package in NEW before the end of DebConf17 :)
> 
> Regards,
> 



signature.asc
Description: OpenPGP digital signature

Bug#873077: gparted reporting wrong disk size

[Daniel]

Package: gparted
Version: 0.25.0-1+b1
Severity: normal

Dear Maintainer,

   * What led up to the situation?
Have put a hybrid iso image (debian stretch installer) onto usb
flashdrive with dd. Then, started gparted and selected the flashdrive.

Warning message: The driver descriptor says the physical block size
is 2048 bytes, but Linux says it is 512 bytes.

Disk block size reported by hdparm is 512 bytes physical / 512 logical.

Wrong disk size calculated by gparted. lsblk reports correct disk size
of ~4gb, gparted reports ~16gb.

   * What outcome did you expect instead?

gparted reports the same disk size as lsblk.


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

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

Versions of packages gparted depends on:
ii  libatkmm-1.6-1v5  2.24.2-2
ii  libc6 2.24-11+deb9u1
ii  libgcc1   1:6.3.0-18
ii  libglib2.0-0  2.50.3-2
ii  libglibmm-2.4-1v5 2.50.0-1
ii  libgtk2.0-0   2.24.31-2
ii  libgtkmm-2.4-1v5  1:2.24.5-1
ii  libpangomm-1.4-1v52.40.1-3
ii  libparted-fs-resize0  3.2-17
ii  libparted23.2-17
ii  libsigc++-2.0-0v5 2.10.0-1
ii  libstdc++66.3.0-18
ii  libuuid1  2.29.2-1

gparted recommends no packages.

Versions of packages gparted suggests:
pn  dmraid 
ii  dmsetup2:1.02.137-2
ii  dosfstools 4.1-1
pn  gpart  
pn  jfsutils   
pn  kpartx 
pn  mtools 
ii  ntfs-3g1:2016.2.22AR.1+dfsg-1
pn  reiser4progs   
pn  reiserfsprogs  
pn  xfsprogs   
pn  yelp   

-- no debconf information

Bug#873075: backuppc: Please package 4.xx version (now 4.1.3)

[Peter Gervai]

Package: backuppc
Version: 3.3.1-4
Severity: wishlist

If possible please try to package the 4.xx version, it fixes numerous bugs 
including
ipv6 handling.

Thanks.

Bug#873076: silversearcher-ag: Crashes when reading a truncated file

[Sam Hocevar]

Package: silversearcher-ag
Version: 2.0.0-1
Severity: important
Tags: security upstream

Dear Maintainer,

here is an example of ag crashing when reading a file:

  # dd of=zob count=0 seek=16G; (sleep 0.1; truncate -s1 zob)&; ag -a lol zob
  [2]26016 bus error (core dumped)  ag -a lol zob

This is because ag uses mmap() to read files, which can cause a SIGBUS
when the file is truncated. This is problematic because another user can
cause the process to crash. There is a scenario where a local user can
hide information from root. Maybe it is worth documenting that fact, or
not making --mmap the default.

   A related discussion happened here on the ripgrep GitHub tracker:

  https://github.com/BurntSushi/ripgrep/issues/581

Regards,
-- 
Sam.

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

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

Versions of packages silversearcher-ag depends on:
ii  libc6 2.24-12
ii  liblzma5  5.2.2-1.3
ii  libpcre3  2:8.39-3
ii  zlib1g1:1.2.8.dfsg-5

silversearcher-ag recommends no packages.

silversearcher-ag suggests no packages.

-- no debconf information

Bug#873050: nvidia-driver: Need 367.xx legacy release for GRID cards now too

[Luca Boccassi]

On Wed, 2017-08-23 at 22:40 -0400, Tyson Whitehead wrote:
> Package: nvidia-driver
> Severity: important
> 
> Dear Maintainer,
> 
> As documented in the 375.xx README, NVIDIA has now created a 367.xx
> line of legacy drivers due to deprecating various GRID cards.
> 
> http://us.download.nvidia.com/XFree86/Linux-x86_64/375.66/README/supp
> ortedchips.html
> 
> Without packaging for the 367.xx legacy line, GRID users will find
> themselves having to downgrade to the legacy 340 line upon upgrading.
> 
> Thanks!  -Tyson

Hi,

I don't see a 367 release on:

http://www.nvidia.com/object/unix.html

And there hasn't been a 367 release in almost a year.

But if it did indeed get forked, then we will add a nvidia-legacy-367xx 
package series.

-- 
Kind regards,
Luca Boccassi

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