Bug#880846: libc-bin: libnss_compat is deprecated and nsswitch should stop using it on new installation

[Florian Weimer]

* Laurent Bigonville:

> According to the release note of 2.26, the nss_compat module is
> deprecated[0].

> [0]https://sourceware.org/ml/libc-announce/2017/msg1.html

I think we made changes so that it is no longer deprecated, by
removing the hard NIS dependency.  It shouldn't be used by default
nevertheless.

Bug#901435: [nore...@release.debian.org: [Pkg-electronics-devel] kicad 5.0.0~rc2+dfsg1-3 MIGRATED to testing]

[Geert Stappers]

For your information
and thanks

- Forwarded message from Debian testing watch  
-

Date: Wed, 20 Jun 2018 04:39:18 +
From: Debian testing watch 
To: ki...@packages.debian.org
Subject: [Pkg-electronics-devel] kicad 5.0.0~rc2+dfsg1-3 MIGRATED to testing

FYI: The status of the kicad source package
in Debian's testing distribution has changed.

  Previous version: (not in testing)
  Current version:  5.0.0~rc2+dfsg1-3

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

___
Pkg-electronics-devel mailing list
pkg-electronics-de...@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-electronics-devel

- End forwarded message -


Groeten
Geert Stappers
-- 
Leven en laten leven

Bug#900596: [chromium-browser] unicode non free license

[Emilio Pozuelo Monfort]

Control: found -1 62.0.3202.89-1

On Mon, 18 Jun 2018 19:24:48 +0200 Emilio Pozuelo Monfort  
wrote:
> On Fri, 01 Jun 2018 21:56:51 +0200 "Bastien =?ISO-8859-1?Q?ROUCARI=C8S?="
>  wrote:
> > Package: chromium-browser
> > Severity: serious
> > version: 67.0.3396.62-1 
> > 
> > The following file are non free:
> > third_party/breakpad/breakpad/src/common/convert_UTF.c

That's not present in testing, but it's free in unstable, so ignoring that.

> > third_party/swiftshader/third_party/llvm-subzero/lib/Support/
> > ConvertUTF.cpp

That's the one that looks non-free, but it's already that way in testing.

So marking this as found in the version in testing.

Emilio

Bug#901655: plasma-workspace: Keyboard input and clipboard freezes when virt-manager is used

[Maximiliano Curia]

¡Hola Phil!

El 2018-06-16 a las 06:02 -0400, Phil Wolf escribió:

Package: plasma-workspace
Version: 4:5.12.5-1
Severity: normal



after update to Buster I found that I cannot use virtualization (KVM/QEMU, 
virt-manager) on KDE Plasma 5.12
since clipboard is constantly freezing. I tested this behaviour both with 
Debian VM with Plasma and Windows VM.



To reproduce this issue simply install and upgrade host to Buster and run one 
or more VMs with
"spice-vdagent" that handles clipboard. Simply copy text (Ctrl+C/V) from host 
to host or from host to VM or
from VM to host or within. In random intervals paste fails and time to time 
keyboard input hangs so you
cannot even type.



The solution is to close virt-manager. Then everything is OK again and you can 
copy and paste.


As a workaround, you might want to disable the kde clipboard manager, you can 
disable it in the system tray settings (right click on top of the system tray 
applet), and deselect the clipboard checkbox.


As for the bug, this is an upstream bug, either in spice-vdagent or in klipper 
or in spice-vdagent, could you report the issue to klipper in bugs.kde.org? If 
you do this, please add a note in this bug with the link of the reported bug.


Happy hacking,
--
"It is practically impossible to teach good programming to students that have 
had a prior exposure to BASIC: as potential programmers they are mentally 
mutilated beyond hope of regeneration."

-- Edsger W. Dijkstra
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#901912: CVE-2018-11468 CVE-2018-11503 CVE-2018-11504 CVE-2018-12495

[Moritz Muehlenhoff]

Source: discount
Severity: grave
Tags: security

Hi,
please see
https://security-tracker.debian.org/tracker/CVE-2018-11468
https://security-tracker.debian.org/tracker/CVE-2018-11503
https://security-tracker.debian.org/tracker/CVE-2018-11504
https://security-tracker.debian.org/tracker/CVE-2018-12495

Cheers,
Moritz

Bug#901913: CVE-2018-3760

[Moritz Muehlenhoff]

Package: ruby-sprockets
Severity: grave
Tags: security

Hi,
please see http://www.openwall.com/lists/oss-security/2018/06/19/2

Cheers,
Moritz
 

Bug#901883: xwayland: Firefox causes Xwayland to freeze and eat 100% CPU

[tino . mettler+debbugs]

Hi,

I forgot to mention that the patches are already applied in xorg
upstream, according to this comment:

https://bugzilla.redhat.com/show_bug.cgi?id=1579067#c26

Regards,
Tino

Bug#885250: shared-mime-info: include filename and line in warning "Unknown media type in type 'all/all'"

[Julian Gilbey]

On Wed, Jun 20, 2018 at 08:25:22AM +0100, Julian Gilbey wrote:
> I think the culprit may be /usr/share/mime/packages/kde.xml, which
> contains both of these file types, along with the message:

The kde bug itself is long-since reported in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525599  There are
links at the end of it; https://bugs.kde.org/show_bug.cgi?id=303627
discusses the current "solution".

But that doesn't change the original comment that it would have been
nice to know the origin of the error message.

Best wishes,

   Julian

Bug#901914: ITP: vulkan-headers

[Timo Aaltonen]

Package: wnpp
Severity: wishlist

Package name: vulkan-headers
Version : 1.1.77
Upstream Author : The Khronos Group Inc
URL : https://github.com/KhronosGroup/Vulkan-Headers
License : Apache 2.0
Programming Lang: C
Description : Vulkan headers and API registry

upstream split the vulkan repository, this is the new headers repo

Bug#885250: shared-mime-info: include filename and line in warning "Unknown media type in type 'all/all'"

[Julian Gilbey]

On Tue, Dec 26, 2017 at 11:50:39AM +0800, Paul Wise wrote:
> Package: shared-mime-info
> Version: 1.9-2
> Severity: normal
> Usertags
> 
> During many different upgrades I get the warning below. I cannot easily
> file bug reports about these warnings because the warning does not
> mention which file is causing the warning.
> 
> Processing triggers for shared-mime-info (1.9-2) ...
> Unknown media type in type 'all/all'
> Unknown media type in type 'all/allfiles'

I think the culprit may be /usr/share/mime/packages/kde.xml, which
contains both of these file types, along with the message:



I hope this is useful; I'm also seeing this error message.  (It
doesn't detract from the sensible request to know the source of the
error in the error message, though.)

Best wishes,

   Julian

Bug#901901: Please create a backport for stable (stretch)

[Julian Andres Klode]

Control: severity -1 wishlist

On Tue, Jun 19, 2018 at 10:10:59PM -0400, Jerome Charaoui wrote:
> Package: keepassxc
> Version: 2.3.1+dfsg.1-1
> 
> Hello,
> 
> Please consider uploading a backport for this package.
> 
> I was able to successfully create such a backport without any
> modifications, as the build requirements seem to be satisfied using
> stretch and stretch-backports sources.

Three things need to happen first

(1) I need to figure out why it crashes most of the time when saving an
entry on my Ubuntu system
(2) Keyring needs to have my key back in, which should happen shortly
(3) Need to upgrade to 2.3.3

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en


signature.asc
Description: PGP signature

Bug#847190: The following feature isn't implemented by Apache FOP, yet: table-layout="auto" (on fo:table)

[Petter Reinholdtsen]

[Petter Reinholdtsen]
> I see from  https://docs.oracle.com/javase/tutorial/jaxp/properties/properties.html >
> these were new in JAXP 1.5, but fail to understand why they are not available 
> when
> building with javac in jdk 10. :(

I tried building in Debian Stable with JDK 8, and here it worked. :/

-- 
Happy hacking
Petter Reinholdtsen

Bug#901915: monero: Incomplete debian/copyright?

[Chris Lamb]

Source: monero
Version: 0.12.2.0~dfsg-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Jonas Smedegaard 

Hi,

I just ACCEPTed monero from NEW but noticed it was missing 
attribution in debian/copyright for at least the gtest code
copy and what (looks like at a quick glance) some imported
code under src/ringct/.

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


Regards,

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

Bug#901134: RFS: anbox-modules/0.0~git20180608-1 [ITP]

[Shengjing Zhu]

Hi Ben,

On Thu, Jun 14, 2018 at 10:46 AM Shengjing Zhu  wrote:
>
> On Thu, Jun 14, 2018 at 01:09:39AM +0100, Ben Hutchings wrote:
> > I agree, I don't think it makes much sense to build these OOT if they
> > can be built in-tree.
>
> Here goes the bug #901492 (linux: Please enable Android ashmem and binder 
> module)

Is there any update about this?
It's it acceptable to enable the in-tree version, as built-in module?
Or it would be better to continue this dkms package as they can't be
built as modules?

>
> > The in-tree version of ashmem *cannot* be built as a module, though,
> > which we would probably want to change.
>


-- 
Best regards,
Shengjing Zhu

Bug#881982: mirror submission for mirror.vpgrp.io

[NOC]

Hello,

Everything is OK now !

Thanks.

On 06/06/2018, 02:48, "Marco d'Itri"  wrote:

On Nov 17, Antoine MILLET  wrote:

Thank you for your contribution to the Debian Project.
Mirror submissions are being processed again, we apologize for the delay.

> Trace Url: http://mirror.vpgrp.io/debian/project/trace/mirror.vpgrp.io
I see that the mirror is not up to date: can you check how ftpsync is 
being run?

-- 
ciao,
Marco

Bug#901883: xwayland: Firefox causes Xwayland to freeze and eat 100% CPU

[Mike Hommey]

Package: xwayland
Version: 2:1.20.0-2
Followup-For: Bug #901883

Dear Maintainer,

I am able to reproduce this reliably with Firefox from experimental by
going to 
http://example.qt.io/qt-webassembly/widgets/richtext/textedit/textedit.html

Attaching gdb to Xwayland shows the same information as mentioned in
https://bugs.archlinux.org/task/58705#comment169691, that is, that
WriteToClient receives a negative count.

Mike


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

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

Versions of packages xwayland depends on:
ii  libaudit1   1:2.8.3-1
ii  libbsd0 0.9.1-1
ii  libc6   2.27-3
ii  libdrm2 2.4.92-1
ii  libegl1 1.0.0+git20180308-3
ii  libepoxy0   1.4.3-1
ii  libgbm1 18.1.2-1
ii  libgcrypt20 1.8.3-1
ii  libgl1  1.0.0+git20180308-3
ii  libpixman-1-0   0.34.0-2
ii  libselinux1 2.8-1
ii  libsystemd0 238-5
ii  libwayland-client0  1.15.0-2
ii  libxau6 1:1.0.8-1+b2
ii  libxdmcp6   1:1.1.2-3
ii  libxfont2   1:2.0.3-1
ii  libxshmfence1   1.3-1
ii  xserver-common  2:1.20.0-2

xwayland recommends no packages.

xwayland suggests no packages.

-- no debconf information

Bug#901916: chemical-structures: provide data-only package

[Andrius Merkys]

Source: chemical-structures
Severity: wishlist

Hello,

the package contains both static data (CML, MOL, SMI, etc) and Web stuff (HTML, 
CGI,
JS, CSS, PNG). It would be beneficial to be able to install the static data 
part only,
as Web stuff has "heavy" dependencies. A straightforward use case: package
'avogadro-data' bundles the static data part (~2 Mb) whereas it could simply 
depend
on static part of 'chemical-structures'.

I suggest putting all static structural data of this package into
'chemical-structures-data', leaving all the rest in 'chemical-structures', 
which would
then depend on the 'chemical-structures-data'. I could help with reorganizing 
the
package should this be deemed useful.

Best wishes,
Andrius 

-- 
Andrius Merkys
Vilnius University Institute of Biotechnology, Saulėtekio al. 7, room V325
LT-10257 Vilnius, Lithuania

Bug#901917: firmware-misc-nonfree: "Failed to load DMC firmware i915/skl_dmc_ver1_27.bin." Please consider including it

[Sergey Protserov]

Package: firmware-misc-nonfree
Version: 20170823-1
Severity: normal
Tags: upstream

Dear Maintainer,
I experience the following problem, as reported by dmesg:
[   12.820043] i915 :00:02.0: firmware: failed to load 
i915/skl_dmc_ver1_27.bin (-2)
[   12.820049] firmware_class: See https://wiki.debian.org/Firmware for 
information about missing firmware
[   12.820054] i915 :00:02.0: Direct firmware load for 
i915/skl_dmc_ver1_27.bin failed with error -2
[   12.820058] i915 :00:02.0: Failed to load DMC firmware 
i915/skl_dmc_ver1_27.bin. Disabling runtime power management.
[   12.820059] i915 :00:02.0: DMC firmware homepage: 
https://01.org/linuxgraphics/downloads/firmware
It seems like firmware-misc-nonfree currently includes only older versions of
skl_dmc. Could you please consider including ver1_27 in an updated package? 
Thanks in
advance.
Yours, Sergey.

-- 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.16.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE=ru 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

firmware-misc-nonfree depends on no packages.

firmware-misc-nonfree recommends no packages.

Versions of packages firmware-misc-nonfree suggests:
ii  initramfs-tools  0.130

-- no debconf information

Bug#901918: apt: Pinning in /etc/apt/preferences ignored

[Johannes Rohr]

Package: apt
Version: 1.6.1
Severity: important

I am trying to downgrade unstable to testing, yet my apt pinning is ignored.

According to /etc/apt/preferences (see below), testing should get 1001 and 
unstable 60, 

yet what I see is this:


xserver-xorg-core:
  Installiert:   2:1.20.0-2
  Installationskandidat: 2:1.20.0-2
  Versionstabelle:
 *** 2:1.20.0-2 500
500 http://deb.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status
 2:1.19.6-1 500
500 http://deb.debian.org/debian testing/main amd64 Packages

Therefore I don't get to downgrade.

-- Package-specific info:

-- apt-config dump --

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "1";
APT::Install-Suggests "0";
APT::Sandbox "";
APT::Sandbox::User "_apt";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^linux-image-4\.16\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-image-4\.16\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-headers-4\.16\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-headers-4\.16\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-4\.16\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-4\.16\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-modules-4\.16\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-modules-4\.16\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-modules-extra-4\.16\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-modules-extra-4\.16\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-4\.16\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-4\.16\.0-2-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-4\.16\.0-1-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-4\.16\.0-2-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-4\.16\.0-1-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-4\.16\.0-2-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-4\.16\.0-1-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-4\.16\.0-2-amd64$";
APT::NeverAutoRemove:: "^.*-modules-4\.16\.0-1-amd64$";
APT::NeverAutoRemove:: "^.*-modules-4\.16\.0-2-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-4\.16\.0-1-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-4\.16\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.16\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.16\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-modules-.*-4\.16\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-modules-.*-4\.16\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-tools-4\.16\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-tools-4\.16\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-cloud-tools-4\.16\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-cloud-tools-4\.16\.0-2-amd64$";
APT::VersionedKernelPackages "";
APT::VersionedKernelPackages:: "linux-image";
APT::VersionedKernelPackages:: "linux-headers";
APT::VersionedKernelPackages:: "linux-image-extra";
APT::VersionedKernelPackages:: "linux-modules";
APT::VersionedKernelPackages:: "linux-modules-extra";
APT::VersionedKernelPackages:: "linux-signed-image";
APT::VersionedKernelPackages:: "kfreebsd-image";
APT::VersionedKernelPackages:: "kfreebsd-headers";
APT::VersionedKernelPackages:: "gnumach-image";
APT::VersionedKernelPackages:: ".*-modules";
APT::VersionedKernelPackages:: ".*-kernel";
APT::VersionedKernelPackages:: "linux-backports-modules-.*";
APT::VersionedKernelPackages:: "linux-modules-.*";
APT::VersionedKernelPackages:: "linux-tools";
APT::VersionedKernelPackages:: "linux-cloud-tools";
APT::Never-MarkAuto-Sections "";
APT::Never-MarkAuto-Sections:: "metapackages";
APT::Never-MarkAuto-Sections:: "contrib/metapackages";
APT::Never-MarkAuto-Sections:: "non-free/metapackages";
APT::Never-MarkAuto-Sections:: "restricted/metapackages";
APT::Never-MarkAuto-Sections:: "universe/metapackages";
APT::Never-MarkAuto-Sections:: "multiverse/metapackages";
APT::Move-Autobit-Sections "";
APT::Move-Autobit-Sections:: "oldlibs";
APT::Move-Autobit-Sections:: "contrib/oldlibs";
APT::Move-Autobit-Sections:: "non-free/oldlibs";
APT::Move-Autobit-Sections:: "restricted/oldlibs";
APT::Move-Autobit-Sections:: "universe/oldlibs";
APT::Move-Autobit-Sections:: "multiverse/oldlibs";
APT::Periodic "";
APT::Periodic::Update-Package-Lists "1";
APT::Periodic::AutocleanInterval "0";
APT::Periodic::Download-Upgradeable-Packages "1";
APT::Periodic::Unattended-Upgrade "1";
APT::Update "";
APT::Update::Post-Invoke-Success "";
APT::Update::Post-Invoke-Success:: "test -x /usr/bin/apt-show-versions || exit 
0 ; apt-show-versions -i";
APT::Update::Post-Invoke-Success:: "/usr/bin/test -e 
/usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && 
/usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call 
--system --dest org.freedesktop.PackageKit --object-path 
/org/freedesktop/PackageKit --timeout 4 --method 
org.freedesktop.PackageK

Bug#899269: [Pkg-samba-maint] Bug#899269: changes to 4.8

[Mathieu Parent]

Le mar. 19 juin 2018 à 00:39, Chad William Seys
 a écrit :
[...]
> I've posted to the samba mailing list about this:
> https://lists.samba.org/archive/samba/2018-June/216447.html

Your problem looks different. Your idmap config is wrong.

Try somehting like this:

idmap config * : backend = tdb
idmap config * : range = 100-199

idmap config PHYSICS : backend  = ad
idmap config PHYSICS : range = 1000-99

Regards
-- 
Mathieu Parent

Bug#899269: [Pkg-samba-maint] Bug#899269: changes to 4.8

[Mathieu Parent]

Le mer. 20 juin 2018 à 11:46, Mathieu Parent  a écrit :
>
> Le mar. 19 juin 2018 à 00:39, Chad William Seys
>  a écrit :
> [...]
> > I've posted to the samba mailing list about this:
> > https://lists.samba.org/archive/samba/2018-June/216447.html
>
> Your problem looks different. Your idmap config is wrong.
>
> Try somehting like this:
>
> idmap config * : backend = tdb
> idmap config * : range = 100-199
>
> idmap config PHYSICS : backend  = ad
> idmap config PHYSICS : range = 1000-99

Remove the two above lines. See man smb.conf for details and man idmap_ad.

Regards
-- 
Mathieu

Bug#899238: RFP: ppx-tools-versioned -- Tools for authors of ppx rewriters

[Andy Li]

On Mon, May 21, 2018 at 7:50 PM, Mehdi Dogguy  wrote:
> Package: wnpp
> Severity: wishlist
>
> * Package name: ppx-tools-versioned
>   Version : 5.1
>   Upstream Author : Alain Frisch and al.
> * URL : https://github.com/ocaml-ppx/ppx_tools_versioned
> * License : MIT
>   Programming Lang: OCaml
>   Description : Tools for authors of ppx rewriters
>
> This library is a variant of ppx-tools where all tools are versioned.
> It is needed to build latest versions of tyxml.
>

Hi Mehdi,

I've created an initial version of the package in salsa:
https://salsa.debian.org/ocaml-team/ppx-tools-versioned
Tested building it with sbuild (and adt-run) for both amd64 and mips.
Would you review it?

Best regards,
Andy

Bug#901919: nvidia-driver: black screen with the latest Linux kernel

[Vincent Lefevre]

Package: nvidia-driver
Version: 390.48-3
Severity: grave
Justification: renders package unusable

After upgrade to the Linux kernel 4.16.16-1, I get a black screen.

-- Package-specific info:
uname -a:
Linux zira 4.16.0-2-amd64 #1 SMP Debian 4.16.16-1 (2018-06-19) x86_64 GNU/Linux

/proc/version:
Linux version 4.16.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 
7.3.0 (Debian 7.3.0-23)) #1 SMP Debian 4.16.16-1 (2018-06-19)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 PDT 
2018
GCC version:  gcc version 7.3.0 (Debian 7.3.0-23) 

lspci 'display controller [030?]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK208GLM [Quadro 
K610M] [10de:12b9] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company GK208GLM [Quadro K610M] [103c:2254]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia
Kernel modules: nvidia

dmesg:

Device node permissions:
crw-rw 1 root video 226,   0 2018-06-20 11:46:55 /dev/dri/card0
crw-rw 1 root video 226, 128 2018-06-20 11:46:55 /dev/dri/renderD128
crw-rw-rw- 1 root root  195, 254 2018-06-20 11:46:57 /dev/nvidia-modeset
crw-rw-rw- 1 root root  195,   0 2018-06-20 11:46:57 /dev/nvidia0
crw-rw-rw- 1 root root  195, 255 2018-06-20 11:46:56 /dev/nvidiactl

/dev/dri/by-path:
total 0
lrwxrwxrwx 1 root root  8 2018-06-20 11:46:55 pci-:01:00.0-card -> ../card0
lrwxrwxrwx 1 root root 13 2018-06-20 11:46:55 pci-:01:00.0-render -> 
../renderD128
video:x:44:vinc17

OpenGL and NVIDIA library files installed:
lrwxrwxrwx 1 root root   15 2018-01-07 20:11:56 /etc/alternatives/glx -> 
/usr/lib/nvidia
lrwxrwxrwx 1 root root   49 2016-04-11 21:40:32 
/etc/alternatives/glx--libEGL.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so
lrwxrwxrwx 1 root root   51 2018-01-07 20:11:56 
/etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so.1
lrwxrwxrwx 1 root root   48 2016-04-11 21:40:32 
/etc/alternatives/glx--libGL.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so
lrwxrwxrwx 1 root root   48 2016-04-11 21:40:32 
/etc/alternatives/glx--libGL.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so
lrwxrwxrwx 1 root root   50 2018-01-07 20:11:56 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   50 2018-01-07 20:11:56 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   52 2016-04-11 21:40:32 
/etc/alternatives/glx--libGLESv2.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so
lrwxrwxrwx 1 root root   52 2016-04-11 21:40:32 
/etc/alternatives/glx--libGLESv2.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so
lrwxrwxrwx 1 root root   54 2018-01-07 20:11:56 
/etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2
lrwxrwxrwx 1 root root   54 2018-01-07 20:11:56 
/etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2
lrwxrwxrwx 1 root root   51 2018-01-07 20:11:56 
/etc/alternatives/glx--libnvidia-cfg.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libnvidia-cfg.so.1
lrwxrwxrwx 1 root root   25 2018-01-07 20:11:56 
/etc/alternatives/glx--linux-libglx.so -> /usr/lib/nvidia/libglx.so
lrwxrwxrwx 1 root root   42 2018-01-07 20:11:56 
/etc/alternatives/glx--nvidia-blacklists-nouveau.conf -> 
/etc/nvidia/nvidia-blacklists-nouveau.conf
lrwxrwxrwx 1 root root   36 2018-01-07 20:11:56 
/etc/alternatives/glx--nvidia-bug-report.sh -> 
/usr/lib/nvidia/nvidia-bug-report.sh
lrwxrwxrwx 1 root root   39 2018-01-07 20:11:56 
/etc/alternatives/glx--nvidia-drm-outputclass.conf -> 
/etc/nvidia/nvidia-drm-outputclass.conf
lrwxrwxrwx 1 root root   28 2018-01-07 20:11:56 
/etc/alternatives/glx--nvidia-load.conf -> /etc/nvidia/nvidia-load.conf
lrwxrwxrwx 1 root root   32 2018-01-07 20:11:56 
/etc/alternatives/glx--nvidia-modprobe.conf -> /etc/nvidia/nvidia-modprobe.conf
lrwxrwxrwx 1 root root   29 2018-01-07 20:11:56 
/etc/alternatives/glx--nvidia_drv.so -> /usr/lib/nvidia/nvidia_drv.so
lrwxrwxrwx 1 root root   22 2016-04-11 21:40:32 
/etc/alternatives/libGL.so-master -> /usr/lib/mesa-diverted
lrwxrwxrwx 1 root root   23 2018-04-23 18:40:28 /etc/alternatives/nvidia -> 
/usr/lib/nvidia/current
lrwxrwxrwx 1 root root   59 2018-04-23 18:40:28 
/etc/alternatives/nvidia--libEGL_nvidia.so.0-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/current/libEGL_nvidia.so.0
lrwxrwxrwx 1 root root   62 2018-04-2

Bug#901920: plplot FTBFS on alpha: misdetects compiler as not supporting NaN

[Michael Cree]

Source: plplot
Version: 5.13.0+dfsg-7
Severity: important
Justification: fails to build from source (but built in past)
User: debian-al...@lists.debian.org
Usertags: ftbfs
Tags: patch

plplot FTBFS on Alpha [1] with missing libcsirocsa.so files at the
install stage.  One can trace this back to the cmake configure at
the start which misdetects the compiler as not supporting NaNs
(from the build log):

-- Check for NaN awareness in C compiler
-- Check for NaN awareness in C compiler - not found
-- WARNING: Setting PL_HAVE_QHULL and WITH_CSA to OFF.

In cmake/modules/csiro.cmake is:

  if(CMAKE_SYSTEM_PROCESSOR MATCHES "alpha.*")
if(CMAKE_C_COMPILER MATCHES "gcc")
  set(NAN_CFLAGS "${NAN_CFLAGS} -mieee")
else(CMAKE_C_COMPILER MATCHES "gcc")
  set(NAN_CFLAGS "${NAN_CFLAGS} -ieee")
endif(CMAKE_C_COMPILER MATCHES "gcc")

In the build CMAKE_C_COMPILER gets set to /usr/bin/cc which is gcc
on Debian Linux but does not match "gcc" in the test and thus the
test proceeds with the compiler option "-ieee" intended for the
Compaq C compiler, not for gcc.

A simple fix for Debian Linux would be to eliminate the test for
gcc (as the Compaq C Compiler for Alpha Linux has not been runnable
under Linux for quite a few years so there is no point in testing
for it) and just use the -mieee command line argument, i.e.,

  if(CMAKE_SYSTEM_PROCESSOR MATCHES "alpha.*")
 set(NAN_CFLAGS "${NAN_CFLAGS} -mieee")
  endif(CMAKE_SYSTEM_PROCESSOR MATCHES "alpha.*")

I suspect this fix might not be acceptable to upstream as it
potentially breaks the build on Tru64 Unix with the Compaq C
compiler.

Cheers,
Michael.

[1]
https://buildd.debian.org/status/fetch.php?pkg=plplot&arch=alpha&ver=5.13.0%2Bdfsg-7&stamp=1529330311&raw=0

Bug#901921: linux-image-4.16.0-2-amd64: kernel oops on shutdown

[Wil van Lierop]

Package: src:linux
Version: 4.16.16-1
Severity: important
Tags: d-i

Dear Maintainer,

   * What led up to the situation?
 Trying to shutdown system.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 Trying a gracefull shutdown of the system.
   * What was the outcome of this action?
 A kernel oops after the graphical system gracefully was shutdown.
   * What outcome did you expect instead?
 A gracefull shutdown.




-- Package-specific info:
** Version:
Linux version 4.16.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version
7.3.0 (Debian 7.3.0-21)) #1 SMP Debian 4.16.16-1 (2018-06-19)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.16.0-2-amd64
root=UUID=40246db7-8b97-4afd-b66b-cbef476b53c5 ro intel_iommu=on iommu=pt quiet

** Not tainted

** Kernel log:
[   12.223298] [drm]   HPD1
[   12.223300] [drm]   DDC: 0x486c 0x486c 0x486d 0x486d 0x486e 0x486e 0x486f
0x486f
[   12.223300] [drm]   Encoders:
[   12.223301] [drm] DFP3: INTERNAL_UNIPHY1
[   12.223302] [drm] Connector 3:
[   12.223302] [drm]   HDMI-A-2
[   12.223303] [drm]   HPD5
[   12.223305] [drm]   DDC: 0x4874 0x4874 0x4875 0x4875 0x4876 0x4876 0x4877
0x4877
[   12.223305] [drm]   Encoders:
[   12.223306] [drm] DFP4: INTERNAL_UNIPHY1
[   12.244220] iwlwifi :03:00.0 wlp3s0: renamed from wlan0
[   12.533557] amdgpu :01:00.0: firmware: direct-loading firmware
amdgpu/polaris10_pfp_2.bin
[   12.544116] usbcore: registered new interface driver btusb
[   12.558330] amdgpu :01:00.0: firmware: direct-loading firmware
amdgpu/polaris10_me_2.bin
[   12.559007] Bluetooth: hci0: read Intel version: 370810011003110e27
[   12.559007] Bluetooth: hci0: Intel device is already patched. patch num: 27
[   12.736300] amdgpu :01:00.0: firmware: direct-loading firmware
amdgpu/polaris10_ce_2.bin
[   12.736305] [drm] Chained IB support enabled!
[   12.781585] amdgpu :01:00.0: firmware: direct-loading firmware
amdgpu/polaris10_rlc.bin
[   12.909901] amdgpu :01:00.0: firmware: direct-loading firmware
amdgpu/polaris10_mec_2.bin
[   13.106237] amdgpu :01:00.0: firmware: direct-loading firmware
amdgpu/polaris10_mec2_2.bin
[   13.138446] usbcore: registered new interface driver snd-usb-audio
[   13.239996] amdgpu :01:00.0: firmware: direct-loading firmware
amdgpu/polaris10_sdma.bin
[   13.240561] amdgpu :01:00.0: firmware: direct-loading firmware
amdgpu/polaris10_sdma1.bin
[   13.353826] amdgpu :01:00.0: firmware: direct-loading firmware
amdgpu/polaris10_uvd.bin
[   13.353835] [drm] Found UVD firmware Version: 1.130 Family ID: 16
[   13.396440] amdgpu :01:00.0: firmware: direct-loading firmware
amdgpu/polaris10_vce.bin
[   13.396443] [drm] Found VCE firmware Version: 52.4 Binary ID: 3
[   13.435205] amdgpu :01:00.0: firmware: direct-loading firmware
amdgpu/polaris10_smc.bin
[   13.540962] [drm] UVD and UVD ENC initialized successfully.
[   13.634978] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
[   13.648026] snd_hda_intel :00:1f.3: bound :00:02.0 (ops
i915_audio_component_bind_ops [i915])
[   13.650907] [drm] VCE initialized successfully.
[   13.686989] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3861:
line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line
[   13.686991] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0
(0x0/0x0/0x0/0x0/0x0)
[   13.686993] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1
(0x1b/0x0/0x0/0x0/0x0)
[   13.686994] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[   13.686995] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
[   13.686996] snd_hda_codec_realtek hdaudioC0D0:inputs:
[   13.686998] snd_hda_codec_realtek hdaudioC0D0:  Front Mic=0x19
[   13.686999] snd_hda_codec_realtek hdaudioC0D0:  Rear Mic=0x18
[   13.687001] snd_hda_codec_realtek hdaudioC0D0:  Line=0x1a
[   13.932311] input: HDA Intel PCH Front Mic as
/devices/pci:00/:00:1f.3/sound/card0/input13
[   13.932376] input: HDA Intel PCH Rear Mic as
/devices/pci:00/:00:1f.3/sound/card0/input14
[   13.932432] input: HDA Intel PCH Line as
/devices/pci:00/:00:1f.3/sound/card0/input15
[   13.932485] input: HDA Intel PCH Line Out Front as
/devices/pci:00/:00:1f.3/sound/card0/input16
[   13.932544] input: HDA Intel PCH Line Out Surround as
/devices/pci:00/:00:1f.3/sound/card0/input17
[   13.932598] input: HDA Intel PCH Line Out CLFE as
/devices/pci:00/:00:1f.3/sound/card0/input18
[   13.932650] input: HDA Intel PCH Line Out Side as
/devices/pci:00/:00:1f.3/sound/card0/input19
[   13.932705] input: HDA Intel PCH Front Headphone as
/devices/pci:00/:00:1f.3/sound/card0/input20
[   13.932759] input: HDA Intel PCH HDMI/DP,pcm=3 as
/devices/pci:00/:00:1f.3/sound/card0/input21
[   13.932811] input: HDA Intel PCH HDMI/DP,pcm=7 as
/devices/pci:00/:00:1f.3/sound/card0/input22
[   13.932863] input: HDA Intel PCH HDMI/DP,pcm=8 as
/devices/pci:00/:00:1f.3/sound/card0

Bug#901922: python2.7: python-gdb extensions do not work

[Richard van der Hoff]

Package: python2.7
Version: 2.7.9-2+deb8u1
Severity: normal

Dear Maintainer,

It appears that the python-gdb extensions [1] do not work with the regular 
python package in Jessie.

For example:



# gdb --args /usr/bin/python test.py



^C
Program received signal SIGINT, Interrupt.
0x76fd2873 in __select_nocancel () at 
../sysdeps/unix/syscall-template.S:81
81  ../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) py-bt
Python Exception  <__main__.PyCodeObjectPtr 
object at 0x7faf9336fb90>: 
Error occurred in Python command: <__main__.PyCodeObjectPtr object at 
0x7faf9336fb90>



I suspect the problem is something to do with the way gcc arranges/optimises 
the stack frames; for example if I go to a 'PyEval_EvalFrameEx' frame and try 
to inspect the 'f' python frame object I do not get sensible results:

(gdb) frame 4
#4  PyEval_EvalFrameEx () at ../Python/ceval.c:2679
2679../Python/ceval.c: No such file or directory.
(gdb) p f->ob_refcnt
$5 = 140737352679576
(gdb) frame 7
#7  PyEval_EvalFrameEx () at ../Python/ceval.c:2679
2679in ../Python/ceval.c
(gdb) p f->ob_refcnt
$6 = 140737352693232


Other versions of python built from source give similar results. The 
unoptimised build in python2.7-dbg works fine, but has too much of a 
performance hit for me.

[1] https://wiki.python.org/moin/DebuggingWithGdb

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

Kernel: Linux 4.14.30-041430-generic (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages python2.7 depends on:
ii  libpython2.7-stdlib  2.7.9-2+deb8u1
ii  mime-support 3.58
ii  python2.7-minimal2.7.9-2+deb8u1

python2.7 recommends no packages.

Versions of packages python2.7 suggests:
ii  binutils   2.25-5+deb8u1
pn  python2.7-doc  

-- no debconf information

Bug#901924: gcr: Fingerprints in SHA256 for certificates

[Frederic MASSOT]

Package: gcr
Version: 3.28.0-1
Severity: wishlist

Dear Maintainer,

gcr-viewer displays MD5 and SHA1 fingerprints of certificates.

MD5 is depreciated and SHA256 is more and more used.

It would be interesting if gcr-viewer also displays SHA256 for fingerprints 
certificates.

On the site "https://www.ssllabs.com/ssltest/analyze.html"; certificate 
fingerprints are now provided in SHA256.


Regards.


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

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

Versions of packages gcr depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.12.8-2
ii  dbus-x11 [dbus-session-bus]   1.12.8-2
ii  dconf-gsettings-backend [gsettings-backend]   0.28.0-2
ii  libc6 2.27-3
ii  libgcr-base-3-1   3.28.0-1
ii  libgcr-ui-3-1 3.28.0-1
ii  libglib2.0-0  2.56.1-2
ii  libgtk-3-03.22.29-3

gcr recommends no packages.

gcr suggests no packages.

-- no debconf information

Bug#901923: buildd.debian.org: Wrong links to git repositories on front page

[Tollef Fog Heen]

Package: buildd.debian.org
Severity: normal

At the bottom of https://buildd.debian.org/, there are links marked with
gitweb that points to Alioth.  Those should be updated to where the
source actually lives.

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are

Bug#901897: git introduces new hazardous working-tree-encoding attribute

[Ian Jackson]

Hi.  Thanks for your prompt attention.  Again, sorry for my
contribution to an annoying situation.

Jonathan Nieder writes ("Re: git introduces new hazardous working-tree-encoding 
attribute"):
> Ian Jackson wrote:
> > Subject: git introduces new hazardous working-tree-encoding attribute
> 
> This title doesn't describe a bug.  On first reading, I thought you
> were saying that some working-tree-encoding related feature was
> behaving incorrectly, but it doesn't appear to be so.  (I was trying
> to understand so that I could forward this report upstream.)

Sorry about that.

> Happy to add a Breaks.  Do you know what version of dgit will have the
> fix?

5.1.  I suggest

   Breaks: dgit (<< 5.1~)

5.1 doesn't exist yet but fixing this issue is very high up on my
list.  Expect it in the next few days.  dgit 5.0 has not yet migrated
and was due to do so on about Sunday.  Because 5.0 has a lot of other
changes I don't want to bring that forward, but I will upload 5.1 with
a higher urgency, so that the migration date is not delayed either.


Much of the rest of what you write is perhaps more relevant to 851679
so I'll answer it there.

Thanks,
Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#901925: git-debrebase new-upstream leaves unhelpful reflog entries

[Ian Jackson]

Package: git-debrebase
Version: 5.0

git-debrebase new-upstream leaves an entry like this in the reflog,
before the rest of the output from git-rebase.

  c15f4d5391 HEAD@{33}: rebase: checkout 
c15f4d5391ff07a718431aca68a73e672fe8870e

Really, this ought to mention at least that this was due to
git-debrebase, and the version number.

But git-rebase doesn't provide a way to specify this.  We need the
move to the new anchor to be done with git-debrebase --onto, so that
a later git-rebase --abort undoes it.

Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#851679: Want way to disable all checkout-affecting gitattributes

[Ian Jackson]

(Replying in the bug as that seems more apposite:)

Firstly, I reread gitattributes(5) and there is a concept of a
`builtin macro'.  (Not sure if that was there when I filed #851679; I
do ask for a `git-defined macro attribute'.)

I think what I am asking for in this bug report is a builtin macro
attribute that disables all checkin/checkout attributes, including all
future ones.  (In the Subject of this report I wrote
"checkout-affecting", but of I mean checkin-affecting ones too.)

(I think it would also be nice to have a builtin macro attribute that
disables all import/export attributes too - but that is not strictly
necessary to avoid the kind of lossage we have right now with dgit and
the new git.)


Jonathan Nieder writes in #901897:
> [Ian Jackson]
> > So, on to the actual problem:
> >
> > Looking at the manpage for gitattributes(7) it mentions a new
> > attribute
> >working-tree-encoding
> > which affects the way files are checked in and out.
> >
> > dgit and similar workflows need to disable this attribute, because
> > they require that git trees and source packages correspond, which
> > cannot be achieved if working trees made from source packages are not
> > identical to git trees once committed.
> 
> I think you're saying that attributes like "text" are forbidden in
> dgit packages because dgit wants to compare the content of the working
> directory to the tracked content without using Git for that.  Am I
> understanding correctly?

Not quite.

Firstly it's not *packages* that are affected.  dgit needs to be able
to work with nonconsenting packages or git branches, including source
packages in the actual Debian archive which contain .gitattributes
files.  So the change needs to be made in particular *clones*.

dgit's design principle is that the git tree object is identical to
the result of dpkg-source -x (minus any .pc directory).  These git
branches are published.  Obviously they have to not depend on
gitattributes, what version of git is being used, the user's git
config, etc.

So such attributes must be disabled *when dgit operations are being
performed*, because dgit's own git operations might get wrong answers
otherwise.

But it also means that such attributes must be disabled *in the user's
tree* because otherwise they will cause terrific trouble.  The thing
the user gets from `git checkout' would not be the same as
dpkg-source -x and might not even be buildable.  Attempts to apply
patches might fail. etc.

dgit doesn't just compare things.  It imports and exports.  Much of
dgit is a sophisticated bidirectional translator between source
packages and git branches, and a converter between git branches of
various different forms and fixer-upper of anomalous states which can
occur with dpkg-source `3.0 (quilt)'.

> Strictly speaking, since users can configure filters that run
> arbitrary commands (see "filter" in gitattributes(5)), that's true,
> but the transformations are meant to produce a canonical "smudged"
> form in the worktree and a canonical "clean" form in the repository.

I don't think that is sufficiently robust.  And the functionality
implemented by checkin/checkout .gitattributes is not needed in the
context of dgit.  dpkg-source doesn't have that feature which means
that Debian source code doesn't need those features.

> Sorry I missed bug#851679 before.  We can discuss this more there.
> Perhaps some command like "git archive" would work better than "git
> checkout" for this use.

dgit does a lot more than `git checkout'.  `git add -Af .' and `git
am' and lots of other things.  dgit likes to work in git where it can
because git is better at many of these operations than copying files
etc.

Thanks for your attention.

Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#901926: git-debrebase should use git-deborig

[Sean Whitton]

Package: git-debrebase
Version: 5.0
Severity: minor

As discussed by private e-mail, git-debrebase should defer to
`git-deborig --just-print`'s determination of the tag corresponding to a
given upstream release, rather than reimplementing the algorithm.

In a message I proposed doing it like this:

  couldn't find any of the following tags: 2.1x, v2.1x, upstream/2.1x
  tell me a tag or branch head to make an orig.tar from: git deborig
  --version=2.1x --just-print COMMITTISH
  git-debrebase: failed command: git-deborig --version=2.1x --just-print
  git-debrebase: subprocess failed with error exit status 1
  git-debrebase: git-deborig was unable to find a
  unique committish corresponding to upstream version 2.1.  Supply a
  commitish as the second argument to new-upstream, e.g.:
   git debrebase new-upstream 2.1 v2.1 

-- 
Sean Whitton

Bug#901927: Add gitk tricks to documentation

[Sean Whitton]

Package: dgit,git-debrebase
Version: 5.0
Severity: wishlist

Ian discovered that the --date-order and --first-parent options are
useful for using gitk with git-debrebase branches.  We should document
that somewhere, because without either of those options using gitk with
git-debrebase branches it likely to be a frustrating experience.

-- 
Sean Whitton

Bug#899269: [Pkg-samba-maint] Bug#899269: Bug#899269: changes to 4.8

[L . P . H . van Belle]

No, dont try below. 

Thats wrong ( sorry Mathieu ) 

> idmap config * : backend = tdb
> idmap config * : range = 100-199
> 
> idmap config PHYSICS : backend  = ad
> idmap config PHYSICS : range = 1000-99
The first configured user in debian has uid???  Yes 1000. 
There for this example isnt correct. 

Better is. 
Your normal linux users start as of  : 1000 - . ? Unknown. 

The BUILIN range is added above the normal linux range. 
Something like this 
> idmap config * : backend = tdb
> idmap config * : range = 4000-

Samba AD started default with 1 
> idmap config PHYSICS : backend  = ad
> idmap config PHYSICS : range = 1-9
I really advice to start as of that point. 

You can change any range but dont overlap any.
I also suggest you to read : 
https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Domain_Member 

And cleanup you config. 
You config is not for a member server as it is now. 
I can ask Rowland on the list if he could advice you on some setttings. 
I for example dont use any "fruit" vfs things. 

ps, sometimes people are very buzy on the samba list and havent replied yet.. 


Best regards, 

Louis



> -Oorspronkelijk bericht-
> Van: Pkg-samba-maint 
> [mailto:pkg-samba-maint-bounces+belle=bazuin.nl@alioth-lists.d
ebian.net] Namens Mathieu Parent
> Verzonden: woensdag 20 juni 2018 11:47
> Aan: Chad William Seys; 899...@bugs.debian.org
> Onderwerp: [Pkg-samba-maint] Bug#899269: Bug#899269: changes to 4.8
> 
> Le mar. 19 juin 2018 à 00:39, Chad William Seys
>  a écrit :
> [...]
> > I've posted to the samba mailing list about this:
> > https://lists.samba.org/archive/samba/2018-June/216447.html
> 
> Your problem looks different. Your idmap config is wrong.
> 
> Try somehting like this:
> 
> idmap config * : backend = tdb
> idmap config * : range = 100-199
> 
> idmap config PHYSICS : backend  = ad
> idmap config PHYSICS : range = 1000-99
> 
> Regards
> -- 
> Mathieu Parent
> 
> ___
> Pkg-samba-maint mailing list
> pkg-samba-ma...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-s
amba-maint
> 

Bug#901915: monero: Incomplete debian/copyright?

[Jonas Smedegaard]

Quoting Chris Lamb (2018-06-20 10:07:57)
> I just ACCEPTed monero from NEW but noticed it was missing attribution 
> in debian/copyright for at least the gtest code copy and what (looks 
> like at a quick glance) some imported code under src/ringct/.

Thanks, for accepting but also for spotting these licensing issues!

gtest code copy I simply forgot to list: Wanted to strip it from source 
tarball but decided to postpone that cleanup till later, and forgot to 
then mention it in debian/changelog until then.  Done now in git.

I fail to locate any omission under src/ringct/.  If you mean the 
references to Sarang Noether then I believe that is mentioned only as 
author (not copyright holder), and besides seems seems part of copyright 
holder The Monero Project.  If you mean the references to Cryptonote 
developers then I believe that copyright holder is already properly 
included in initial Files section.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#886243: freerdp2-shadow-x11 on startuo

[Alberto Luaces Fernández]

> Can you guys try again with the latest freerdp2 version in Debian
> testing? I don't get this issue anymore.

Now it is not SIGSEVing for me anymore as well, but I cannot connect to the 
server, possibly an unrelated issue.

I never used this feature before, so I don't know if my setup is to blame.  I'd 
better wait for other users that have been using the server feature before to 
confirm if everything is back to normal.

Bug#901918: apt: Pinning in /etc/apt/preferences ignored

[Julian Andres Klode]

On Wed, Jun 20, 2018 at 11:41:47AM +0200, Johannes Rohr wrote:
> Package: apt
> Version: 1.6.1
> Severity: important
> 
> I am trying to downgrade unstable to testing, yet my apt pinning is ignored.
> 
[...]
> -- /etc/apt/preferences --
> 
> Package: *
> Pin: release n=buster
> Pin-Priority: 1001
> 
> Package: *
> Pin: release a=testing
> Pin-Priority: 1001
> 
> Package: *
> Pin: release a=unstable
> Pin-Priority: 60
> 
> Package: *
> Pin: release n=sid
> Pin-Priority: 60

Oh I see what's going on - there are spaces at the beginning of your line,
and apt ignores them all.


-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#901900: grep-excuses

[Ian Jackson]

Control: found -1 + 4.4

This problem was not introduced in dgit 5.0; dgit has not changed in
this respect since the gitattributes tests were added.  The regression
is triggered by a change in git, as discussed in #901900 and its
parent #901897.

Ian Jackson writes ("grep-excuses"):
> dgit (4.4 to 5.0)
> Migration status: BLOCKED: Rejected/introduces a regression
> Maintainer: Ian Jackson
> Too young, only 2 of 7 days old
> Updating dgit introduces new bugs: #901900
> Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dgit.html
> autopkgtest for dgit/5.0: amd64:  style="background:#87d96c">Pass
> Required age reduced by 3 days because of autopkgtest

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#901928: xwayland: Firefox causes Xwayland to freeze and eat 100% CPU

[Tino Mettler]

Package: xwayland
Version: 2:1.20.0-2
Severity: normal
Tags: patch

Dear Maintainer,

while trying to watch the German TV show "Die Sendung mit der Maus" from
https://www.wdrmaus.de/aktuelle-sendung/, my Gnome desktop freezes.  I can
SSH into the machine and see that Xwayland eats 100% CPU.  The freeze can be
reproduced, it happened every time I accessed the above URL in Firefox 60.

I found a similar issue in the Red Hat bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1579067

The issue mentions patches in
https://patchwork.freedesktop.org/series/43618/.  I applied them to the
xorg-server source, built and installed the package and the freeze does not
happen anymore.

The patches are also attached to this bugreport.

Regards,
Tino

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

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

Versions of packages xwayland depends on:
ii  libaudit1   1:2.8.3-1
ii  libbsd0 0.9.1-1
ii  libc6   2.27-3
ii  libdrm2 2.4.92-1
ii  libegl1 1.0.0+git20180308-3
ii  libepoxy0   1.4.3-1
ii  libgbm1 18.1.1-1
ii  libgcrypt20 1.8.3-1
ii  libgl1  1.0.0+git20180308-3
ii  libpixman-1-0   0.34.0-2
ii  libselinux1 2.8-1
ii  libsystemd0 238-5
ii  libwayland-client0  1.15.0-2
ii  libxau6 1:1.0.8-1+b2
ii  libxdmcp6   1:1.1.2-3
ii  libxfont2   1:2.0.3-1
ii  libxshmfence1   1.3-1
ii  xserver-common  2:1.20.0-2

xwayland recommends no packages.

xwayland suggests no packages.

-- debconf-show failed
diff --git a/glamor/glamor.c b/glamor/glamor.c
index d984d20f3..e2c74d17a 100644
--- a/glamor/glamor.c
+++ b/glamor/glamor.c
@@ -836,20 +836,20 @@ glamor_fds_from_pixmap(ScreenPtr screen, PixmapPtr 
pixmap, int *fds,
 glamor_get_screen_private(pixmap->drawable.pScreen);
 
 if (!glamor_priv->dri3_enabled)
-return -1;
+return 0;
 switch (pixmap_priv->type) {
 case GLAMOR_TEXTURE_DRM:
 case GLAMOR_TEXTURE_ONLY:
 if (!glamor_pixmap_ensure_fbo(pixmap, pixmap->drawable.depth == 30 ?
   GL_RGB10_A2 : GL_RGBA, 0))
-return -1;
+return 0;
 return glamor_egl_fds_from_pixmap(screen, pixmap, fds,
   strides, offsets,
   modifier);
 default:
 break;
 }
-return -1;
+return 0;
 }
 
 _X_EXPORT int
diff --git a/glamor/glamor.c b/glamor/glamor.c
index e2c74d17a..63f0947fa 100644
--- a/glamor/glamor.c
+++ b/glamor/glamor.c
@@ -865,17 +865,15 @@ glamor_fd_from_pixmap(ScreenPtr screen,
  &modifier);
 
 /* Pixmaps with multi-planes/modifier are not supported in this interface 
*/
-if (ret > 1) {
-while (ret > 0)
-close(fds[--ret]);
-return -1;
+if (ret == 1 && offsets[0] == 0) {
+*stride = strides[0];
+*size = pixmap->drawable.height * *stride;
+return fds[0];
 }
 
-ret = fds[0];
-*stride = strides[0];
-*size = pixmap->drawable.height * *stride;
-
-return ret;
+while (ret > 0)
+close(fds[--ret]);
+return -1;
 }
 
 _X_EXPORT int

Bug#901918: apt: Pinning in /etc/apt/preferences ignored

[Julian Andres Klode]

On Wed, Jun 20, 2018 at 11:41:47AM +0200, Johannes Rohr wrote:
> Package: apt
> Version: 1.6.1
> Severity: important
> 
> I am trying to downgrade unstable to testing, yet my apt pinning is ignored.
> 
> According to /etc/apt/preferences (see below), testing should get 1001 and 
> unstable 60, 
> 
> yet what I see is this:
> 
> 
> xserver-xorg-core:
>   Installiert:   2:1.20.0-2
>   Installationskandidat: 2:1.20.0-2
>   Versionstabelle:
>  *** 2:1.20.0-2 500
> 500 http://deb.debian.org/debian unstable/main amd64 Packages
> 100 /var/lib/dpkg/status
>  2:1.19.6-1 500
> 500 http://deb.debian.org/debian testing/main amd64 Packages
> 
> Therefore I don't get to downgrade.

What does apt-cache policy (without arguments) tell you?

> deb [arch=amd64] http://repo.yandex.ru/yandex-browser/deb beta main
> 
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
> 'testing-debug'), (500, 'unstable')

This policy says something different than your preferences file too

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#901929: transition: openbabel

[Andrius Merkys]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

Hello,

I would like to request a transition slot for openbabel (experimental -> 
unstable). Some of the r-depends
already build successfully (for example avogadro), nevertheless, a slot would 
help a lot to track the progress
of the transition.

Thanks,
Andrius

-- 
Andrius Merkys
Vilnius University Institute of Biotechnology, Saulėtekio al. 7, room V325
LT-10257 Vilnius, Lithuania

Bug#901930: crash upon trying to enter "Config"

[Toni Mueller]

Package: wicd-curses
Version: 1.7.4+tb2-6
Severity: important
Tags: upstream


Hi,

I am trying to run wicd-curses, but it crashes hard. I've culled the
control characters and the boilerplate ("About" etc.) from the
typescript:


root@nutshell:~# wicd-curses
... Not connected ...

Traceback (most recent call last):
  File "/usr/share/wicd/curses/wicd-curses.py", line 1149, in call_update_ui
self.update_ui(True)
  File "/usr/share/wicd/curses/wicd-curses.py", line 97, in wrapper
return func(*args, **kargs)
  File "/usr/share/wicd/curses/wicd-curses.py", line 1162, in update_ui
self.handle_keys(input_data)
  File "/usr/share/wicd/curses/wicd-curses.py", line 1040, in handle_keys
self.diag = WirelessSettingsDialog(pos, self.frame)
  File "/usr/share/wicd/curses/netentry_curses.py", line 503, in __init__
self.set_values()
  File "/usr/share/wicd/curses/netentry_curses.py", line 539, in set_values
self.bitrates.append('auto')
AttributeError: 'dbus.String' object has no attribute 'append'



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

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

Versions of packages wicd-curses depends on:
ii  python2.7.15-3
ii  python-urwid  2.0.1-2
ii  wicd-daemon   1.7.4+tb2-6

Versions of packages wicd-curses recommends:
ii  sudo  1.8.2301

wicd-curses suggests no packages.

Versions of packages wicd-daemon depends on:
ii  adduser  3.117
ii  dbus 1.12.8-2
ii  debconf  1.5.67
ii  iputils-ping 3:20161105-1
ii  isc-dhcp-client  4.3.5-4
ii  lsb-base 9.20170808
ii  psmisc   23.1-1+b1
ii  python   2.7.15-3
ii  python-dbus  1.2.8-2
ii  python-gobject-2 2.28.6-13+b1
ii  python-wicd  1.7.4+tb2-6
ii  wireless-tools   30~pre9-12+b1
ii  wpasupplicant2:2.6-16

Versions of packages wicd-daemon recommends:
ii  rfkill  0.5-1+b1

Versions of packages wicd-daemon suggests:
ii  pm-utils  1.4.1-17

Versions of packages python-wicd depends on:
ii  python  2.7.13-2

-- debconf information excluded

Bug#901931: timidity-daemon: upgrading to 2.14.0-3 breaks whole sound-system

[Klaumi Klingsporn]

Package: timidity-daemon
Version: 2.14.0-3
Severity: important

Dear Maintainer,

after the daily upgrade of my testing-system where also timidity and 
timidity-daemon were upgraded 
my whole sound-system was broken: pulseaudio didn't find the sound-card, 
jack-server wasn't 
able to start. The sound-device seemed to be blocked to these sound-servers, 
although some 
applications like audacious could access it and play sound.

Whatever happend (and believe me it took a while to figure out that timidity 
was the reason of 
all this mess!) - after killing the running timiditiy-process as root all 
sound-problems were gone 
and all was fine again. 

Hopefully you can fix the problem. Until then I'll have to purge the 
timidity-daemon package.

Thanks for maintaining the packages!

Klaumi


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

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

Versions of packages timidity-daemon depends on:
ii  adduser   3.117
ii  lsb-base  9.20170808
ii  timidity  2.14.0-3

timidity-daemon recommends no packages.

timidity-daemon suggests no packages.

-- no debconf information

Bug#901929: transition: openbabel

[Emilio Pozuelo Monfort]

On 20/06/18 13:07, Andrius Merkys wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Hello,
> 
> I would like to request a transition slot for openbabel (experimental -> 
> unstable). Some of the r-depends
> already build successfully (for example avogadro), nevertheless, a slot would 
> help a lot to track the progress
> of the transition.

Does that mean that some of the rdeps don't build against the new version? Can
you be more specific on the number, the possible solutions...?

Emilio

Bug#901918: apt: Pinning in /etc/apt/preferences ignored

[Johannes Rohr]

Am 20.06.2018 um 12:38 schrieb Julian Andres Klode:
>
> What does apt-cache policy (without arguments) tell you?

Here, and see that the list of pinned packages in the end is empty, even
though according to /etc/apt/preferences, all packages are pinned.

r@tommy:~$ LANG=C apt-cache policy
Package files:
 100 /var/lib/dpkg/status
 release a=now
 500 http://repo.yandex.ru/yandex-browser/deb beta/main amd64 Packages
 release v=all,o=Yandex Browser
Archive,n=beta,l=Ubuntu/Debian,c=main,b=amd64
 origin repo.yandex.ru
 500 https://dl.winehq.org/wine-builds/debian buster/main i386 Packages
 release
v=10.0,o=dl.winehq.org,a=testing,n=buster,l=winehq,c=main,b=i386
 origin dl.winehq.org
 500 https://dl.winehq.org/wine-builds/debian buster/main amd64 Packages
 release
v=10.0,o=dl.winehq.org,a=testing,n=buster,l=winehq,c=main,b=amd64
 origin dl.winehq.org
 500 http://download.virtualbox.org/virtualbox/debian stretch/contrib
i386 Packages
 release o=Oracle Corporation,n=stretch,l=Oracle
Corporation,c=contrib,b=i386
 origin download.virtualbox.org
 500 http://download.virtualbox.org/virtualbox/debian stretch/contrib
amd64 Packages
 release o=Oracle Corporation,n=stretch,l=Oracle
Corporation,c=contrib,b=amd64
 origin download.virtualbox.org
 500 http://linux.teamviewer.com/deb preview/main i386 Packages
 release o=TeamViewer GmbH,a=preview,l=TeamViewer,c=main,b=i386
 origin linux.teamviewer.com
 500 http://linux.teamviewer.com/deb preview/main amd64 Packages
 release o=TeamViewer GmbH,a=preview,l=TeamViewer,c=main,b=amd64
 origin linux.teamviewer.com
 500 http://linux.teamviewer.com/deb stable/main i386 Packages
 release o=TeamViewer GmbH,a=stable,l=TeamViewer,c=main,b=i386
 origin linux.teamviewer.com
 500 http://linux.teamviewer.com/deb stable/main amd64 Packages
 release o=TeamViewer GmbH,a=stable,l=TeamViewer,c=main,b=amd64
 origin linux.teamviewer.com
 500 https://repo.skype.com/deb stable/main amd64 Packages
 release o=. stable,a=stable,n=stable,l=. stable,c=main,b=amd64
 origin repo.skype.com
 500 http://deb.playonlinux.com wheezy/main i386 Packages
 release v=7.0,o=PlayOnLinux,a=wheezy,n=wheezy,l=PoL,c=main,b=i386
 origin deb.playonlinux.com
 500 http://deb.playonlinux.com wheezy/main amd64 Packages
 release v=7.0,o=PlayOnLinux,a=wheezy,n=wheezy,l=PoL,c=main,b=amd64
 origin deb.playonlinux.com
 500 http://ppa.launchpad.net/nextcloud-devs/client/ubuntu zesty/main
i386 Packages
 release
v=17.04,o=LP-PPA-nextcloud-devs-client,a=zesty,n=zesty,l=Desktop
client,c=main,b=i386
 origin ppa.launchpad.net
 500 http://ppa.launchpad.net/nextcloud-devs/client/ubuntu zesty/main
amd64 Packages
 release
v=17.04,o=LP-PPA-nextcloud-devs-client,a=zesty,n=zesty,l=Desktop
client,c=main,b=amd64
 origin ppa.launchpad.net
 500 file:/home/jr/src/debian unstable/ Packages
 release o=johannes,a=unstable,n=unstable,l=jr,c=
 500 http://apt.insynchq.com/debian buster/contrib i386 Packages
 release o=Insynchq, Inc.,n=buster,l=Insynchq, Inc.,c=contrib,b=i386
 origin apt.insynchq.com
 500 http://apt.insynchq.com/debian buster/contrib amd64 Packages
 release o=Insynchq, Inc.,n=buster,l=Insynchq, Inc.,c=contrib,b=amd64
 origin apt.insynchq.com
 500 http://apt.insynchq.com/debian buster/non-free i386 Packages
 release o=Insynchq, Inc.,n=buster,l=Insynchq, Inc.,c=non-free,b=i386
 origin apt.insynchq.com
 500 http://apt.insynchq.com/debian buster/non-free amd64 Packages
 release o=Insynchq, Inc.,n=buster,l=Insynchq, Inc.,c=non-free,b=amd64
 origin apt.insynchq.com
 500 http://dl.google.com/linux/chrome/deb stable/main amd64 Packages
 release v=1.0,o=Google, Inc.,a=stable,n=stable,l=Google,c=main,b=amd64
 origin dl.google.com
 500 http://www.deb-multimedia.org testing/non-free i386 Packages
 release v=0.0,o=Unofficial Multimedia
Packages,a=testing,n=buster,l=Unofficial Multimedia
Packages,c=non-free,b=i386
 origin www.deb-multimedia.org
 500 http://www.deb-multimedia.org testing/non-free amd64 Packages
 release v=0.0,o=Unofficial Multimedia
Packages,a=testing,n=buster,l=Unofficial Multimedia
Packages,c=non-free,b=amd64
 origin www.deb-multimedia.org
 500 http://www.deb-multimedia.org testing/main i386 Packages
 release v=0.0,o=Unofficial Multimedia
Packages,a=testing,n=buster,l=Unofficial Multimedia Packages,c=main,b=i386
 origin www.deb-multimedia.org
 500 http://www.deb-multimedia.org testing/main amd64 Packages
 release v=0.0,o=Unofficial Multimedia
Packages,a=testing,n=buster,l=Unofficial Multimedia Packages,c=main,b=amd64
 origin www.deb-multimedia.org
 500 http://www.deb-multimedia.org sid/non-free i386 Packages
 release v=0.0,o=Unofficial Multimedia
Packages,a=unstable,n=sid,l=Unofficial Multimedia Packages,c=non-free,b=i386
 origin www.deb-multimedia.org
 500 http://www.deb-multimedia.org sid/non-free amd64 Packages
 release v=0.0,o=Unofficial 

Bug#901880: transition: libantlr3c

[Emilio Pozuelo Monfort]

Control: tags -1 confirmed

On 19/06/18 21:07, Fabian Wolff wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Dear Release Team,
> 
> I would hereby like to request a transition slot for libantlr3c.
> 
> The current version of libantlr3c in experimental, 3.4+dfsg-1,
> includes a patch for the RC bug #900601 that changes the public API of
> the library. It also includes a new upstream version with a different
> SONAME. The package builds on all release architectures [0].
> 
> The reverse dependencies of libantlr3c (belle-sip, cvc4 and
> forked-daapd) can all be built with the libantlr3c version from
> experimental (build logs are available at [1]). Therefore, binNMUs for
> these packages should be sufficient.
> 
> The auto-generated tracker file at [2] looks good to me.

Go ahead then.

Emilio

Bug#901918: apt: Pinning in /etc/apt/preferences ignored

[Johannes Rohr]

> Oh I see what's going on - there are spaces at the beginning of your line,
> and apt ignores them all.

Oh, I see. Thanks! Removing the spaces helps. Bug or feature? If you
decide that this is a feature, feel free to close.

Thanks again for your help!!

>
>

Bug#901932: linux-image-4.16.0-2-amd64: Blank screen after update kernel 4.16.16

[jerome]

Package: src:linux
Version: 4.16.16-1
Severity: important

Dear Maintainer,

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

   * What led up to the situation?
Blank (black) screen after kernel image 4.16.16 update. 
At boot the system don't response after the kernel loading, i have to do hard 
reset from power button.
   * 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 ***


-- Package-specific info:
** Version:
Linux version 4.16.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 
7.3.0 (Debian 7.3.0-23)) #1 SMP Debian 4.16.16-1 (2018-06-19)

** Command line:
BOOT_IMAGE=/vmlinuz-4.16.0-2-amd64 root=/dev/nvme0n1p6 ro single

** Tainted: PO (4097)
 * Proprietary module has been loaded.
 * Out-of-tree module has been loaded.

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: System manufacturer
product_name: System Product Name
product_version: System Version
chassis_vendor: Default string
chassis_version: Default string
bios_vendor: American Megatrends Inc.
bios_version: 1301
board_vendor: ASUSTeK COMPUTER INC.
board_name: STRIX Z270F GAMING
board_version: Rev 1.xx

** Loaded modules:
snd_hda_codec_hdmi
nls_ascii
nls_cp437
vfat
fat
ext4
crc16
mbcache
jbd2
intel_rapl
x86_pkg_temp_thermal
intel_powerclamp
snd_hda_codec_realtek
coretemp
snd_hda_codec_generic
kvm
snd_hda_intel
irqbypass
snd_hda_codec
crct10dif_pclmul
snd_hda_core
ghash_clmulni_intel
efi_pstore
snd_hwdep
intel_cstate
eeepc_wmi
snd_pcm
snd_timer
asus_wmi
sparse_keymap
mei_me
intel_uncore
joydev
snd
intel_rapl_perf
rfkill
iTCO_wdt
wmi_bmof
efivars
pcspkr
soundcore
iTCO_vendor_support
sg
mei
shpchp
nvidia_drm(PO)
acpi_pad
evdev
drm_kms_helper
drm
nvidia_modeset(PO)
nvidia(PO)
ipmi_devintf
ipmi_msghandler
parport_pc
ppdev
lp
parport
efivarfs
ip_tables
x_tables
autofs4
hid_logitech_hidpp
libcrc32c
crc32_generic
f2fs
crc32c_generic
fscrypto
ecb
hid_logitech_dj
hid_generic
usbhid
hid
sd_mod
crc32_pclmul
crc32c_intel
ahci
libahci
mxm_wmi
aesni_intel
xhci_pci
aes_x86_64
nvme
crypto_simd
xhci_hcd
libata
cryptd
glue_helper
e1000e
i2c_i801
nvme_core
usbcore
scsi_mod
usb_common
wmi
video
button

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Intel Kaby Lake Host Bridge 
[8086:591f] (rev 05)
Subsystem: ASUSTeK Computer Inc. Intel Kaby Lake Host Bridge [1043:872f]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x16) 
[8086:1901] (rev 05) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:14.0 USB controller [0c03]: Intel Corporation 200 Series PCH USB 3.0 xHCI 
Controller [8086:a2af] (prog-if 30 [XHCI])
Subsystem: ASUSTeK Computer Inc. 200 Series PCH USB 3.0 xHCI Controller 
[1043:872f]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:16.0 Communication controller [0780]: Intel Corporation 200 Series PCH CSME 
HECI [8086:a2ba]
Subsystem: ASUSTeK Computer Inc. 200 Series PCH CSME HECI [1043:872f]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: mei_me
Kernel modules: mei_me

00:17.0 SATA controller [0106]: Intel Corporation 200 Series PCH SATA 
controller [AHCI mode] [8086:a282] (prog-if 01 [AHCI 1.0])
Subsystem: ASUSTeK Computer Inc. 200 Series PCH SATA controller [AHCI 
mode] [1043:872f]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: ahci
Kernel modules: ahci

00:1b.0 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI Express Root 
Port [8086:a2e7] (rev f0) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriD

Bug#901933: ITP: prometheus-bird-exporter -- Prometheus exporter for the BIRD routing daemon

[Daniel Swarbrick]

Package: wnpp
Severity: wishlist
Owner: Daniel Swarbrick 

* Package name: prometheus-bird-exporter
  Version : 1.2.1
  Upstream Author : Daniel Czerwonk 
* URL : https://github.com/czerwonk/bird_exporter
* License : MIT
  Programming Lang: Go
  Description : Prometheus exporter for the BIRD routing daemon

Prometheus exporter for the BIRD routing daemon, which collects metrics
via the BIRD Unix socket.

This exporter provides useful information for network administrators to
monitor the health of BGP / OSPF peering of the BIRD daemon. We are
currently testing it in a cloud hosting environment.

I think / hope I can maintain this more or less singlehandedly, however
it will be my first package contribution to Debian (do I need a
sponsor?), so any help will be gladly accepted.

Bug#886243: freerdp2-shadow-x11 on startuo

[Mike Gabriel]

Control: close -1
Control: fixed -1 2.0.0~git20180411.1.7a7b1802+dfsg1-1

Hi,

On  Mi 20 Jun 2018 12:30:13 CEST, Alberto Luaces Fernández wrote:


Can you guys try again with the latest freerdp2 version in Debian
testing? I don't get this issue anymore.


Now it is not SIGSEVing for me anymore as well, but I cannot connect  
to the server, possibly an unrelated issue.


I never used this feature before, so I don't know if my setup is to  
blame.  I'd better wait for other users that have been using the  
server feature before to confirm if everything is back to normal.


$ freerdp-shadow-cli -auth -sec-tls

was the command I used. And it worked fine. About other option  
combinations, I don't know much either, really.


However, I consider this info enough to close this bug. Feel free to  
reopen, if needed.


Mike
--

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

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



pgpLIMkY9na_O.pgp
Description: Digitale PGP-Signatur

Bug#899259: cups-daemon: with IdleExitTimeout 60, fails to exit after 60 s of inactivity

[Brian Potkin]

On Wed 20 Jun 2018 at 00:31:19 +0200, Francesco Poli wrote:

> On Tue, 19 Jun 2018 14:25:07 +0100 Brian Potkin wrote:
> 
> [...]
> >   A temporary workaround is to run:
> > 
> > cupsctl Browsing=No
> > 
> >   to restore the CUPS default setting.
> > 
> > How do you go on with that, Francesco?
> 
> I can try, but I already have:
> 
>   $ grep Browsing /etc/cups/cupsd.conf 
>   Browsing Off
> 
> Isn't that enough to disable browsing ?!?
> I have always thought it was...
> Has something changed recently?
> 
> Wait, I see that
> 
>   $ /usr/sbin/cupsctl
>   _debug_logging=0
>   _remote_admin=0
>   _remote_any=0
>   _share_printers=0
>   _user_cancel_any=0
>   BrowseLocalProtocols=dnssd
>   DefaultAuthType=Basic
>   IdleExitTimeout=60
>   JobPrivateAccess=default
>   JobPrivateValues=default
>   MaxLogSize=0
>   PageLogFormat=
>   SubscriptionPrivateAccess=default
>   SubscriptionPrivateValues=default
>   WebInterface=No
> 
> does not include any value for Browsing ...

My output is the same as this.
 
> Does this mean that "Off" is not a valid value for Browsing and that
> cupsd simply ignores invalid values?!? without complaining at all?!?

"Browsing Off", "Browsing No" and "Browsing 0" are all equivalent.
A value other than these (xxx, say) is interpreted as "Yes".

Cheers,

Brian.

Bug#901919: nvidia-driver: black screen with the latest Linux kernel

[Vincent Lefevre]

Control: retitle -1 nvidia-driver: black screen with the latest Linux kernel - 
general protection fault

The kernel log was not included. It ends with:

Jun 20 11:46:59 zira kernel: [   17.930908] usercopy: Kernel memory exposure 
attempt detected from SLUB object 'nvidia_stack_cache' (offset 11440, size 3)!
Jun 20 11:46:59 zira kernel: [   17.930915] [ cut here ]
Jun 20 11:46:59 zira kernel: [   17.930915] kernel BUG at 
/build/linux-s0lf2B/linux-4.16.16/mm/usercopy.c:100!
Jun 20 11:46:59 zira kernel: [   17.930919] invalid opcode:  [#1] SMP PTI
Jun 20 11:46:59 zira kernel: [   17.930920] Modules linked in: appletalk ax25 
ipx(C) p8023 p8022 psnap llc cmac bnep cpufreq_conservative cpufreq_userspace 
cpufreq_powersave snd_hda_codec_hdmi arc4 intel_rapl x86_pkg_temp_thermal 
intel_powerclamp binfmt_misc iTCO_wdt iTCO_vendor_support iwlmvm hp_wmi 
coretemp sparse_keymap wmi_bmof mxm_wmi mac80211 btusb btrtl btbcm btintel kvm 
bluetooth irqbypass iwlwifi intel_cstate joydev snd_hda_codec_realtek 
intel_uncore uvcvideo tpm_infineon intel_rapl_perf snd_hda_codec_generic pcspkr 
rtsx_pci_ms drbg serio_raw videobuf2_vmalloc memstick videobuf2_memops sg 
snd_hda_intel cfg80211 videobuf2_v4l2 ansi_cprng videobuf2_common snd_hda_codec 
evdev videodev snd_hda_core snd_hwdep media lpc_ich ecdh_generic snd_pcm 
snd_timer rfkill snd soundcore mei_me mei shpchp ie31200_edac battery tpm_tis 
hp_accel
Jun 20 11:46:59 zira kernel: [   17.930952]  tpm_tis_core lis3lv02d wmi 
input_polldev tpm video hp_wireless rng_core button ac nvidia_drm(PO) 
drm_kms_helper drm nvidia_modeset(PO) nvidia(PO) ipmi_devintf ipmi_msghandler 
parport_pc ppdev lp sunrpc parport ip_tables x_tables autofs4 ext4 crc16 
mbcache jbd2 crc32c_generic fscrypto ecb algif_skcipher af_alg dm_crypt dm_mod 
sr_mod cdrom sd_mod hid_apple hid_generic usbhid hid crct10dif_pclmul 
crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc rtsx_pci_sdmmc mmc_core ahci 
libahci aesni_intel ehci_pci aes_x86_64 xhci_pci ehci_hcd crypto_simd 
glue_helper libata cryptd xhci_hcd psmouse scsi_mod i2c_i801 rtsx_pci usbcore 
e1000e usb_common thermal
Jun 20 11:46:59 zira kernel: [   17.930981] CPU: 4 PID: 1098 Comm: Xorg 
Tainted: P C O 4.16.0-2-amd64 #1 Debian 4.16.16-1
Jun 20 11:46:59 zira kernel: [   17.930982] Hardware name: Hewlett-Packard HP 
ZBook 15 G2/2253, BIOS M70 Ver. 01.08 03/16/2015
Jun 20 11:46:59 zira kernel: [   17.930987] RIP: 0010:usercopy_abort+0x69/0x80
Jun 20 11:46:59 zira kernel: [   17.930988] RSP: 0018:baef028f3b50 EFLAGS: 
00010282
Jun 20 11:46:59 zira kernel: [   17.930989] RAX: 006f RBX: 
0003 RCX: 
Jun 20 11:46:59 zira kernel: [   17.930990] RDX:  RSI: 
9ededdd16738 RDI: 9ededdd16738
Jun 20 11:46:59 zira kernel: [   17.930991] RBP: 0003 R08: 
03a7 R09: 0004
Jun 20 11:46:59 zira kernel: [   17.930992] R10: 90077e48 R11: 
907a8dcd R12: 0001
Jun 20 11:46:59 zira kernel: [   17.930993] R13: 9edeae9e2cb3 R14: 
 R15: 9edeae9e2cf8
Jun 20 11:46:59 zira kernel: [   17.930994] FS:  7f85040566c0() 
GS:9ededdd0() knlGS:
Jun 20 11:46:59 zira kernel: [   17.930995] CS:  0010 DS:  ES:  CR0: 
80050033
Jun 20 11:46:59 zira kernel: [   17.930996] CR2: 7f84fc13d010 CR3: 
00046ffd0005 CR4: 001606e0
Jun 20 11:46:59 zira kernel: [   17.930997] Call Trace:
Jun 20 11:46:59 zira kernel: [   17.931003]  __check_heap_object+0xe7/0x120
Jun 20 11:46:59 zira kernel: [   17.931005]  __check_object_size+0x9c/0x1a0
Jun 20 11:46:59 zira kernel: [   17.931126]  os_memcpy_to_user+0x21/0x40 
[nvidia]
Jun 20 11:46:59 zira kernel: [   17.931246]  _nv009377rm+0xbf/0xe0 [nvidia]
Jun 20 11:46:59 zira kernel: [   17.931342]  ? _nv028067rm+0x79/0x90 [nvidia]
Jun 20 11:46:59 zira kernel: [   17.931435]  ? _nv028067rm+0x55/0x90 [nvidia]
Jun 20 11:46:59 zira kernel: [   17.931522]  ? _nv013694rm+0xee/0x100 [nvidia]
Jun 20 11:46:59 zira kernel: [   17.931609]  ? _nv015342rm+0x154/0x270 [nvidia]
Jun 20 11:46:59 zira kernel: [   17.931725]  ? _nv008310rm+0x134/0x1a0 [nvidia]
Jun 20 11:46:59 zira kernel: [   17.931840]  ? _nv008289rm+0x29c/0x2b0 [nvidia]
Jun 20 11:46:59 zira kernel: [   17.931955]  ? _nv001072rm+0xe/0x20 [nvidia]
Jun 20 11:46:59 zira kernel: [   17.932070]  ? _nv007316rm+0xd8/0x100 [nvidia]
Jun 20 11:46:59 zira kernel: [   17.932185]  ? _nv001171rm+0x627/0x830 [nvidia]
Jun 20 11:46:59 zira kernel: [   17.932300]  ? rm_ioctl+0x73/0x100 [nvidia]
Jun 20 11:46:59 zira kernel: [   17.932355]  ? nvidia_ioctl+0xb0/0x720 [nvidia]
Jun 20 11:46:59 zira kernel: [   17.932410]  ? nvidia_ioctl+0x573/0x720 [nvidia]
Jun 20 11:46:59 zira kernel: [   17.932412]  ? kmem_cache_free+0x19c/0x1d0
Jun 20 11:46:59 zira kernel: [   17.932466]  ? 
nvidia_frontend_unlocked_ioctl+0x3e/0x50 [nvidia]
Jun 20 11:46:59 zira kernel: [   17.932468]  ? do_vfs_

Bug#901934: searchmonkey: tries to use icons from wrong location (and fails)

[Dirk Griesbach]

Package: searchmonkey
Version: 0.8.3-1
Severity: normal
Tags: patch

Hi,

While this version of searchmonkey installs its various sized icons into the 
default location under /usr/share/icons/highcolor/, searchmonkey.desktop 
still points to a now non-existent searchmonkey-32x32.png icon in 
/usr/share/pixmaps/searchmonkey, similar to searchmonkey.png in /u/s/p/ being 
a dangling symlink pointing to searchmonkey/searchmonkey-48x48.png.

The attached patch fixes the .desktop file. No patch attached for the 
dangling symlink.

Regards,
Dirk

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

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

Versions of packages searchmonkey depends on:
ii  libatk1.0-0  2.28.1-1
ii  libc62.27-3
ii  libcairo21.15.10-3
ii  libfontconfig1   2.13.0-5
ii  libfreetype6 2.8.1-2
ii  libgdk-pixbuf2.0-0   2.36.11-2
ii  libglib2.0-0 2.56.1-2
ii  libgtk2.0-0  2.24.32-1
ii  libpango-1.0-0   1.42.1-1
ii  libpangocairo-1.0-0  1.42.1-1
ii  libpangoft2-1.0-01.42.1-1
ii  libpoppler-glib8 0.63.0-2
ii  libzip4  1.1.2-1.1+b1
ii  zlib1g   1:1.2.11.dfsg-1

searchmonkey recommends no packages.

searchmonkey suggests no packages.

-- no debconf information
diff -u a/searchmonkey.desktop b/searchmonkey.desktop
--- a/searchmonkey.desktop  2018-06-20 13:09:37.308476519 +0200
+++ b/searchmonkey.desktop  2018-06-20 13:11:33.405052211 +0200
@@ -2,7 +2,7 @@
 Name=Searchmonkey
 Comment=Regular expression power search utility
 Exec=searchmonkey
-Icon=/usr/share/pixmaps/searchmonkey/searchmonkey-32x32.png
+Icon=searchmonkey
 Type=Application
 StartupNotify=false
 Terminal=false

Bug#901930: [pkg-wicd-maint] Bug#901930: crash upon trying to enter "Config"

[Axel Beckert]

Control: tag -1 + moreinfo

Hi Toni,

thanks for bug report.

On a first glance it looks as if this issue only happens if a specific
flow path is taken in wicd-curses. It would be interesting to know
under which circumstances it exactly happens for you.

I assume it's reproducible for you.

Toni Mueller wrote:
> I am trying to run wicd-curses, but it crashes hard. I've culled the
> control characters and the boilerplate ("About" etc.) from the
> typescript:
> 
> 
> root@nutshell:~# wicd-curses
> ... Not connected ...
> 
> Traceback (most recent call last):
>   File "/usr/share/wicd/curses/wicd-curses.py", line 1149, in call_update_ui
> self.update_ui(True)
>   File "/usr/share/wicd/curses/wicd-curses.py", line 97, in wrapper
> return func(*args, **kargs)
>   File "/usr/share/wicd/curses/wicd-curses.py", line 1162, in update_ui
> self.handle_keys(input_data)
>   File "/usr/share/wicd/curses/wicd-curses.py", line 1040, in handle_keys
> self.diag = WirelessSettingsDialog(pos, self.frame)
>   File "/usr/share/wicd/curses/netentry_curses.py", line 503, in __init__
> self.set_values()
>   File "/usr/share/wicd/curses/netentry_curses.py", line 539, in set_values
> self.bitrates.append('auto')
> AttributeError: 'dbus.String' object has no attribute 'append'

Does this happen immediately or only when a known network which is set
to connect automatically is detected to be available, i.e. only after
a few seconds)?

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#860796: appears to be linked to the lack of a running "nautilus --gapplication-service"

[Marcel Lautenbach]

Interesting, I had the same experience today and can confirm that 
nautilus-desktop works if nautilus is started but does not without 
nautilus running, too.


What strikes me odd is the fact, that it only happens on my cloned 
systems. That is: I have an Intel NUC running just fine. I cloned the 
system to my older laptop and there I experienced this "phenomena". Then 
I cloned the NUC system on a virutal disk and ran VirtualBox. Same thing 
there. Without running only nautilus-desktop does not allow me to double 
click any folders on my desktop. Other icons like text files work just fine.



On Fri, 28 Apr 2017 09:15:34 +0100 Ben Green wrote:
> Hi,
>
> Some further observations. Here are two procedures on my system. I run
> these via the gnome-terminal:
>
>
> Procedure 1
> ===
> killall -SIGKILL nautilus
> killall -SIGKILL nautilus-desktop
> ps -ef | grep naut #confirm that no nautilus processes exist for the
> current session
> nautilus &
> nautilus-desktop &
>
>
>
> Procedure 2
> ===
> killall -SIGKILL nautilus
> killall -SIGKILL nautilus-desktop
> ps -ef | grep naut #confirm that no nautilus processes exist for the
> current session
> nautilus-desktop &
>
>
> The following results are produced consistently:
>
> Results of Procedure 1
> ==
> So with Procedure 1, I get a working desktop, with clickable folders
> opening out in new nautilus windows. I note also that the launching of
> nautilus-desktop is very fast, almost instant in most cases.
>
> Of course with this procedure I also get nautilus launched with an
> open home folder too due to having run nautilus. The desktops icons
> are fully clickable though. If I close all the nautilus windows, the
> clickability of desktop icons is lost.
>
>
> Results of Procedure 2
> ==
> With Procedure 2 I get a desktop, but the icons are not clickable at
> all, they will highlight but never open into nautilus folder displays.
> Even if I then run 'nautilus' icons are not clickable.
>
>
>
>
>
> Having had a look at this I can do:
>
> Procedure 3
> ===
> killall -SIGKILL nautilus
> killall -SIGKILL nautilus-desktop
> ps -ef | grep naut #confirm that no nautilus processes exist for the
> current session
> nautilus --gapplication-service &
> nautilus-desktop &

--
__
Marcel Lautenbach | Oppelner Str. 3 | 40880 Ratingen
Telefon: 02102 44 72 06 | Mobil:  0151 251 393 59
eMail: marcel@lautenbach.email



smime.p7s
Description: S/MIME Cryptographic Signature

Bug#901935: dgit and git-debrebase should honour GIT_REFLOG_ACTION

[Ian Jackson]

Package: dgit
Versioni 5.0
Usertags: ijack...@chiark.greenend.org.uk
Usertags: rsn

This will affect nearly every call to git-update-ref and perhaps some
calls to git-commit etc.

https://public-inbox.org/git/23338.12262.631847.860...@chiark.greenend.org.uk/T/#t

Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#901936: chromium: Please provide debug symbols

[Witold Baryluk]

Package: chromium
Version: 62.0.3202.89-1
Severity: normal


I do have chromium crashing every 5 minutes, even with single tab open,
even with ~/.cache and ~/.config cleared / removed or when using chromium
--temp-profile, so I am sure this is not related to particular website or
extension, or amount of tabs, or past usage.

It crashes (SIG SEGV) with a stack trace, but it only show main and
clone, and all other functions are just instruction pointers in hex.

I suspect this is related to my hardware, weak GPU in particular, but
hard to say (i.e. it just crashes for some reasons, even if all the page
is doing is pure JS benchmark with nothing on display). (Firefox is
working perfectly on the same pages with dozens of tabs).


So,

please provide package with debug symbols in a separate package, so the stack 
traces
are meaningful and to run it under gdb.

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

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

Versions of packages chromium depends on:
ii  chromium-common  62.0.3202.89-1
ii  libasound2   1.1.6-1
ii  libatk1.0-0  2.28.1-1
ii  libavcodec57 7:3.4.2-2+b2
ii  libavformat577:3.4.2-2+b2
ii  libavutil55  7:3.4.2-2+b2
ii  libc62.27-3
ii  libcairo21.15.10-3
ii  libcups2 2.2.8-3
ii  libdbus-1-3  1.12.8-3
ii  libevent-2.1-6   2.1.8-stable-4
ii  libexpat12.2.5-3
ii  libflac8 1.3.2-3
ii  libfontconfig1   2.13.0-5
ii  libfreetype6 2.8.1-2
ii  libgcc1  1:8.1.0-5
ii  libgdk-pixbuf2.0-0   2.36.11-2
ii  libglib2.0-0 2.56.1-2
ii  libgtk2.0-0  2.24.32-1
ii  libharfbuzz0b1.7.6-1+b1
ii  libicu57 57.1-9
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  liblcms2-2   2.9-2
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.19-3
ii  libnss3  2:3.37.1-1
ii  libopus0 1.3~beta+20180518-1
ii  libpango-1.0-0   1.42.0-1
ii  libpangocairo-1.0-0  1.42.0-1
ii  libpng16-16  1.6.34-1
ii  libpulse011.1-5
ii  libre2-3 20170101+dfsg-1
ii  libsnappy1v5 1.1.7-1
ii  libstdc++6   8.1.0-5
ii  libvpx4  1.6.1-3
ii  libwebp6 0.6.1-2
ii  libwebpdemux20.6.1-2
ii  libwebpmux3  0.6.1-2
ii  libx11-6 2:1.6.5-1
ii  libx11-xcb1  2:1.6.5-1
ii  libxcb1  1.13-1
ii  libxcomposite1   1:0.4.4-2
ii  libxcursor1  1:1.1.15-1
ii  libxdamage1  1:1.1.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  libxml2  2.9.4+dfsg1-7
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.32-2
ii  libxss1  1:1.2.2-1+b2
ii  libxtst6 2:1.2.3-1
ii  zlib1g   1:1.2.11.dfsg-1

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

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

-- no debconf information

Bug#901784: libmypaint-1.3-0: Can't install libmypaint-1.3-0

[José Couto]

Hi.

Thanks for your help and sorry for the delay in answering.

I found the problem while gathering info for you:

# apt-cache policy
Package files:
 100 /var/lib/dpkg/status
 release a=now
   1 http://deb.debian.org/debian experimental/main amd64 Packages
 release o=Debian,a=experimental,n=experimental,l=Debian,c=main,b=amd64
 origin deb.debian.org
 500 http://deb.debian.org/debian sid/contrib amd64 Packages
 release o=Debian,a=unstable,n=sid,l=Debian,c=contrib,b=amd64
 origin deb.debian.org
 500 http://deb.debian.org/debian sid/non-free amd64 Packages
 release o=Debian,a=unstable,n=sid,l=Debian,c=non-free,b=amd64
 origin deb.debian.org
 500 http://deb.debian.org/debian sid/main amd64 Packages
 release o=Debian,a=unstable,n=sid,l=Debian,c=main,b=amd64
 origin deb.debian.org
Pinned packages:
 libmypaint-common -> 1.3.0-2 with priority -3

This file was in /etc/apt/preferences.d/apt-listbugs:

Explanation: Pinned by apt-listbugs at 2018-05-03 08:43:14 +0200
Explanation:   #894757: libmypaint-common: file conflict with mypaint-data
Package: libmypaint-common
Pin: version *
Pin-Priority: -3

After removing the file, I could install gimp without issues.

Best regards!

On Mon, Jun 18, 2018 at 9:41 PM James Cowgill  wrote:

> Hi,
>
> Sorry I accidentally sent the last email by mistake before it was finished.
>
> On 18/06/18 14:35, José Couto wrote:
> > Sorry, I forgot to cc bugs.debian.org .
> >
> > Hi, James. Thank you for your help.
> [...]
> > I can't install libmypaint-common by hand either:
> >
> > ###
> > # apt-get -o Debug::pkgProblemResolver=yes install libmypaint-commo
> > n
> >
> > Reading package lists... Done
> > Building dependency tree
> > Reading state information... Done
> > Package libmypaint-common is not available, but is referred to by
> > another packag
> > e.
> > This may mean that the package is missing, has been obsoleted, or
> > is only available from another source
> >
> > E: Package 'libmypaint-common' has no installation candidate
> > ###
>
> As I said I don't know what's wrong here. That package should exist and
> does exist in the main package lists and on my machine.
>
> Maybe try running "apt update" again?
> What's in your /etc/apt/sources.list?
>
> James
>
>

Bug#901938: RFS: libgooglepinyin/0.1.2-4 [RC]

[Boyuan Yang]

Package: sponsorship-requests
Severity: important
X-Debbugs-CC: debian-input-met...@lists.debian.org sunwea...@debian.org 
a...@debian.org

Dear Mike, Aron, debian-input-method team members and mentors,

As a continuation of dealing with massive RC bugs caused by IME team maintainer
address migration, I have prepared a team upload for package "libgooglepinyin"
and I am looking for a sponsor to push it into unstable. Besides, I am looking
for a DD to help importing the packaging git repository onto Salsa from my
temporary repo and grant me (hosiet-guest) the Master role so that previous
packaging commits could be pushed and maintained there.

Transition is not needed since it is merely a rebuild. Its sole reverse
dependency, fcitx-googlepinyin, will be handled by me and uploaded very soon.

Package "libgooglepinyin" is indeed a dead project (hosted on Google Code w/o
migration efforts) but it does provides important features for East Asian users
and is worthwhile to be kept inside Debian in the foreseeable future.

* Package name : libgooglepinyin
   Version : 0.1.2-4
   Upstream Author : Weng Xuetian 
 * URL : https://code.google.com/archive/p/libgooglepinyin/
 * License : Apache-2.0
   Section : libs

  It builds those binary packages:

libgooglepinyin0 - Pinyin engine fork from Google Pinyin on Android
libgooglepinyin0-dev - Pinyin engine fork from Google Pinyin on Android - 
development files

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

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


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

dget -x 
https://mentors.debian.net/debian/pool/main/libg/libgooglepinyin/libgooglepinyin_0.1.2-4.dsc


  Git packaging repository: (temporary, will be removed after upload)

https://salsa.debian.org/hosiet-guest/libgooglepinyin.git

  Git packaging repository: (proposed, not exists yet)

https://salsa.debian.org/debian/libgooglepinyin.git

  Changes since the last upload:

libgooglepinyin (0.1.2-4) unstable; urgency=medium
 .
   * Team upload.
   * debian: Apply "wrap-and-sort -abst".
   * d/control: Set maintainer to debian-input-met...@lists.debian.org.
 Closes: #899574.
   * d/control: Set homepage to
 https://code.google.com/archive/p/libgooglepinyin/.
   * d/control: Point Vcs fields to Salsa platform.
   * d/control: Bump Standards-Version to 4.1.4.
   * debian: Drop old -dbg package in favour of automatic -dbgsym packages.
   * debian: Bump debhelper compat to v11.
   * d/rules:
 - Drop manual LDFLAGS manipulation in favour of DEB_LDFLAGS_MAINT_APPEND.
 - Use "dh_missing --fail-missing".
   * d/watch: Removed, there won't be any releases anymore.
   * d/copyright: Refresh format and information.
   * d/libgooglepinyin-dev.install: Explicitly install static library file.
   * d/libgooglepinyin0.symbols: Refresh symbols with build log.

--
Regards,
Boyuan Yang

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

Bug#901936: chromium: Please provide debug symbols

[Braiam Peguero]

Debugs symbols are already provided, just not in the mirrored repository.
Follow the instructions at
https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols

On Wed, Jun 20, 2018 at 8:36 AM, Witold Baryluk 
wrote:

> Package: chromium
> Version: 62.0.3202.89-1
> Severity: normal
>
>
> I do have chromium crashing every 5 minutes, even with single tab open,
> even with ~/.cache and ~/.config cleared / removed or when using chromium
> --temp-profile, so I am sure this is not related to particular website or
> extension, or amount of tabs, or past usage.
>
> It crashes (SIG SEGV) with a stack trace, but it only show main and
> clone, and all other functions are just instruction pointers in hex.
>
> I suspect this is related to my hardware, weak GPU in particular, but
> hard to say (i.e. it just crashes for some reasons, even if all the page
> is doing is pure JS benchmark with nothing on display). (Firefox is
> working perfectly on the same pages with dozens of tabs).
>
>
> So,
>
> please provide package with debug symbols in a separate package, so the
> stack traces
> are meaningful and to run it under gdb.
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.16.0-2-amd64 (SMP w/2 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_US:en (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages chromium depends on:
> ii  chromium-common  62.0.3202.89-1
> ii  libasound2   1.1.6-1
> ii  libatk1.0-0  2.28.1-1
> ii  libavcodec57 7:3.4.2-2+b2
> ii  libavformat577:3.4.2-2+b2
> ii  libavutil55  7:3.4.2-2+b2
> ii  libc62.27-3
> ii  libcairo21.15.10-3
> ii  libcups2 2.2.8-3
> ii  libdbus-1-3  1.12.8-3
> ii  libevent-2.1-6   2.1.8-stable-4
> ii  libexpat12.2.5-3
> ii  libflac8 1.3.2-3
> ii  libfontconfig1   2.13.0-5
> ii  libfreetype6 2.8.1-2
> ii  libgcc1  1:8.1.0-5
> ii  libgdk-pixbuf2.0-0   2.36.11-2
> ii  libglib2.0-0 2.56.1-2
> ii  libgtk2.0-0  2.24.32-1
> ii  libharfbuzz0b1.7.6-1+b1
> ii  libicu57 57.1-9
> ii  libjpeg62-turbo  1:1.5.2-2+b1
> ii  liblcms2-2   2.9-2
> ii  libminizip1  1.1-8+b1
> ii  libnspr4 2:4.19-3
> ii  libnss3  2:3.37.1-1
> ii  libopus0 1.3~beta+20180518-1
> ii  libpango-1.0-0   1.42.0-1
> ii  libpangocairo-1.0-0  1.42.0-1
> ii  libpng16-16  1.6.34-1
> ii  libpulse011.1-5
> ii  libre2-3 20170101+dfsg-1
> ii  libsnappy1v5 1.1.7-1
> ii  libstdc++6   8.1.0-5
> ii  libvpx4  1.6.1-3
> ii  libwebp6 0.6.1-2
> ii  libwebpdemux20.6.1-2
> ii  libwebpmux3  0.6.1-2
> ii  libx11-6 2:1.6.5-1
> ii  libx11-xcb1  2:1.6.5-1
> ii  libxcb1  1.13-1
> ii  libxcomposite1   1:0.4.4-2
> ii  libxcursor1  1:1.1.15-1
> ii  libxdamage1  1:1.1.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  libxml2  2.9.4+dfsg1-7
> ii  libxrandr2   2:1.5.1-1
> ii  libxrender1  1:0.9.10-1
> ii  libxslt1.1   1.1.32-2
> ii  libxss1  1:1.2.2-1+b2
> ii  libxtst6 2:1.2.3-1
> ii  zlib1g   1:1.2.11.dfsg-1
>
> Versions of packages chromium recommends:
> ii  fonts-liberation  1:1.07.4-7
>
> Versions of packages chromium suggests:
> pn  chromium-driver
> pn  chromium-l10n  
> pn  chromium-shell 
> ii  chromium-widevine  62.0.3202.89-1
>
> -- no debconf information
>
>


-- 
Braiam Peguero

Bug#901940: Please separate uncommon connection drivers

[Christian Ehrhardt]

Package: libvirt
Version: 4.3.0-1
Severity: normal

I'd suggest we do split the connectino backends as it was done for storage
drivers before:

https://salsa.debian.org/libvirt-team/libvirt/commit/ea0f70cfde9ad38b40df4db4b05582d498f2a8e0

https://salsa.debian.org/libvirt-team/libvirt/commit/a218a9c45ca2af824c20e2b7b369984f48202a8d

Reasoning: In 9/10 cases people drive KVM via libvirt, which is why I have
split it the way I'm suggesting.

I'd suggest to keep these for being "internal" libvirt functionality
/usr/lib/libvirt/connection-driver/libvirt_driver_interface.so
/usr/lib/libvirt/connection-driver/libvirt_driver_network.so
/usr/lib/libvirt/connection-driver/libvirt_driver_nodedev.so
/usr/lib/libvirt/connection-driver/libvirt_driver_nwfilter.so
/usr/lib/libvirt/connection-driver/libvirt_driver_secret.so
/usr/lib/libvirt/connection-driver/libvirt_driver_storage.so

And qemu/kvm for being the most commonly used virt backend
/usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so

I'd break the following out to extra packages, with the latter two groupesd
for xen
/usr/lib/libvirt/connection-driver/libvirt_driver_uml.so
/usr/lib/libvirt/connection-driver/libvirt_driver_lxc.so
/usr/lib/libvirt/connection-driver/libvirt_driver_vbox.so
/usr/lib/libvirt/connection-driver/libvirt_driver_libxl.so
/usr/lib/libvirt/connection-driver/libvirt_driver_xen.so

I was going back and forth on breaking out lxc or not.
I know that you (Guido) worked a bit with it. In case Debian wants to keep
lxc in the default set I'd ask you to accept my changes but make it a
recommends on Debian. From Ubuntu's POV libvirt-lxc is clearly inferior to
LXD in so many way that I'd want to keep it out of the default libvirt
connections.

Overall this allows to drop all xen related dependencies ones like
libxen-4.9 /libxenstore3.0.
Separating the others does not grant more dependencies to be dropped, but
it still is cleaner and more lightweight in general.

Since not all arches build all connection drivers anyway I used [1] to
derive which ones I need to list for vbox/xen as linux-any would leave
empty packages on e.g. s390x.

The aborts without those connection drivers installed are not ugly and
actually quite correct in its error message:
$ export LIBVIRT_DEFAULT_URI='lxc:///'
$ virsh list
error: failed to connect to the hypervisor
error: no connection driver available for lxc:///

After install and libvirtd service restart (just as with the storgae
drivers) it works fine:

# virsh list
 IdName   State

...

I have a patch ready to do all that which I'll submit in salsa as soon as I
got the bug number from this report (to make the changelog correctly refer
to the bug).

I already test-backported to the (currently shamefully out of date) Ubuntu
version and a test build is in [2] in case you want to look at buildlogs or
such.

[1]: https://buildd.debian.org/status/package.php?p=libvirt
[2]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3302

-- 
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd

Bug#901939: qgit: Please package new upstream version (v2.8) with updated project homepage

[Boyuan Yang]

Source: qgit
Version: 2.7-2
Severity: normal

Dear qgit maintainer,

According to http://libre.tibirna.org/ , qgit upstream has moved to GitHub and
released qgit 2.8.

New upstream homepage is https://github.com/tibirna/qgit .

Please consider packaging qgit 2.8 and update Homepage field in debian/control
file.

Thanks!

--
Regards,
Boyuan Yang



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

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

-- no debconf information

Bug#901941: IO performance hit on kernel 4.9

[Martin Molnar]

Package: linux-image-4.9.0-0.bpo.6-amd64
Version: 4.9.88-1+deb9u1~bpo8+1

We use debian as our system of choice for running our proprietary software. 
This application
is used to store large ammounts of data. Files can range from 1-30 megabytes in 
size and
on demand be served over network to other services. Data is stored on 81 disks
formated to XFS filesystem.
During peak hours the overall bandwidth used on one server can reach up to 
15Gbps.

We would like to upgrade our systems from jessie to stretch and we tried
to install new kernel 4.9 from jessie-backports repository. This resulted in
a huge performance drop for us.

At the time of the upgrade the overall bandwidth used was around 8Gbps,
15 min system load around 11, average cpu utilization at 60%, 27% in iowait,
22% in system. Response times of our application were below 90 miliseconds in 
90 percentile.

Being aware of Spectre, Meltdown i booted into kernel 4.9 with the option 
pti=off.

While the bandwidth stayed at around 8Gbps, system metrics got significantly 
worse.
System 15 min load stabilized around 20, but 1min system load was jumping 
between 20
and 30. Average cpu utilization has also increased, it was jumping between 60% 
and 70%,
seems that most of it was caused by system. Our response time metric changed
to 200 in 90 percentile.

Curiosly, disk read bytes increased by about 20%, but that might have been 
caused by clearing
of filesystem cache by the reboot.

Now some information about the hardware:
CPU: 2x AMD Opteron(tm) Processor 6128
RAM: 256GB

There are 81 data disks connected over 4 SCSI controllers:
LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon]
There is a JBOD system, with 45 disks and 36 are on the server itself,
the JBOD sysstem is connected by external SAS2 cables.

I am unable to find out the exact type of the controllers, but I might
be able to request it if required.

I tried to check cpufreq if there might be something throttling the system,
but it seemed that all cpus are set to performance governor and at max 
frequency.

The installed system is Debian Jessie 8.10 with libc6 2.19-18+deb8u10

Thank you for any help you can provide.

Bug#899269: [Pkg-samba-maint] Bug#899269: Bug#899269: changes to 4.8

[Mathieu Parent]

Le mer. 20 juin 2018 à 12:39, L.P.H. van Belle  a écrit :
>
> No, dont try below.
>
> Thats wrong ( sorry Mathieu )

Yes. This was copied from manpage, then (few minutes) later corrected.
(I removed the ad backend, because it requires SFU to be enabled and
other requirements.)

The idea Chad William Seys, is that specifying the idmap range is mandatory.


Regards

-- 
Mathieu Parent

Bug#901942: telegram-desktop doesn't show text box to others when a user creates a channel.

[shirish शिरीष]

Package: telegram-desktop
Version: 1.2.17-1
Severity: normal

Dear Maintainer,

I created a channel and it was reported that no text-box appeared. Now
I don't know whether it was because of the oldish version of
telegram-desktop at my end or something else. Attaching a screenshot
shared by the other person. They were on mobile which auto-updates.


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

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

Versions of packages telegram-desktop depends on:
ii  libavcodec57  7:3.4.2-2+b2
ii  libavformat57 7:3.4.2-2+b2
ii  libavutil55   7:3.4.2-2+b2
ii  libc6 2.27-3
ii  libgcc1   1:8.1.0-5
ii  libglib2.0-0  2.56.1-2
ii  libminizip1   1.1-8+b1
ii  libopenal11:1.18.2-3
ii  libqt5core5a [qtbase-abi-5-10-0]  5.10.1+dfsg-7
ii  libqt5dbus5   5.10.1+dfsg-7
ii  libqt5gui55.10.1+dfsg-7
ii  libqt5network55.10.1+dfsg-7
ii  libqt5widgets55.10.1+dfsg-7
ii  libssl1.1 1.1.0h-4
ii  libstdc++68.1.0-5
ii  libswresample27:3.4.2-2+b2
ii  libswscale4   7:3.4.2-2+b2
ii  libtgvoip1.0.31.0.3-3
ii  libx11-6  2:1.6.5-1
ii  qt5-image-formats-plugins 5.10.1-2
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages telegram-desktop recommends:
ii  fonts-open-sans 1.11-1
ii  libappindicator3-1  0.4.92-5

telegram-desktop suggests no packages.

-- no debconf information


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

Bug#901940: PR in Salsa

[Christian Ehrhardt]

FYI - submitted changes for review as
https://salsa.debian.org/libvirt-team/libvirt/merge_requests/2

Bug#901936: chromium: Please provide debug symbols

[Witold Baryluk]

Followup-For: Bug #901936


Ok, fair enough. That is actually smart to not mirror debug symbols by
default to all mirrors, and create debug package automatically out of
compiled binaries in standarized way.

However...

But before reporting I checked:

https://packages.debian.org/source/sid/chromium-browser
https://packages.debian.org/source/buster/chromium-browser
https://tracker.debian.org/pkg/chromium-browser

https://tracker.debian.org/news/964307/accepted-chromium-browser-670339679-2-source-into-unstable/

https://buildd.debian.org/status/logs.php?pkg=chromium-browser&arch=amd64

https://packages.qa.debian.org/c/chromium-browser.html

https://packages.debian.org/search?searchon=sourcenames&keywords=chromium-browser

and none of them show any mention of debug symbols or links to packages
for buster or unstable.

https://packages.debian.org/search?suite=buster&arch=amd64&searchon=names&keywords=chromium-dbgsym

is also empty. When looking at suite option, there are -backports, but no
-debug or anything like that.

Thechnically automatically crated debug symbol package are normal deb packages,
just in different repo.

Feel free to reassign to qa.debian.org , tracker.debian.org , or who ever is 
more relevant for
this problem.



Thank you!

Witold

Bug#899269: [Pkg-samba-maint] Bug#899269: Bug#899269: changes to 4.8

[L . P . H . van Belle]

Hai Mathieu, 

The user got also reply on the list now but Rowland ( from samba devs ) pointed 
a good thing out. 

Linux user nobody : uid 65534 
That wil conflic with the defaults used for the domain id ranges. 

Quote from Rowland:
So, what I recommend is, use '1000-2999' for local Unix users &
groups, '3000-7999' for the 'Well known SIDS' and anything outside the
Domain and start the main AD DOMAIN at '1' (which is, incidentally,
the number Microsoft chose).

This leads to lines such as these in smb.conf:

idmap config *:backend = tdb
idmap config *:range = 3000-7999
idmap config SAMDOM : backend = rid
idmap config SAMDOM : range = 1-99


Now, for Debian that would be
idmap config SAMDOM : range = 1-65533
But that is a small range or debian should advice 
idmap config SAMDOM : range = 10-99
Anything from/above 100.000 for samba AD. 

So imo, the debian setup the README.Debian should mention something about this. 


Best regards, 

Louis


> -Oorspronkelijk bericht-
> Van: Mathieu Parent [mailto:math.par...@gmail.com] 
> Verzonden: woensdag 20 juni 2018 15:08
> Aan: Louis; 899...@bugs.debian.org
> CC: Chad William Seys
> Onderwerp: Re: Bug#899269: [Pkg-samba-maint] Bug#899269: 
> Bug#899269: changes to 4.8
> 
> Le mer. 20 juin 2018 à 12:39, L.P.H. van Belle 
>  a écrit :
> >
> > No, dont try below.
> >
> > Thats wrong ( sorry Mathieu )
> 
> Yes. This was copied from manpage, then (few minutes) later corrected.
> (I removed the ad backend, because it requires SFU to be enabled and
> other requirements.)
> 
> The idea Chad William Seys, is that specifying the idmap 
> range is mandatory.
> 
> 
> Regards
> 
> -- 
> Mathieu Parent
> 
> 

Bug#901943: gfortran aborts with internal compiler error: segmentation fault

[fulvio ciriaco]

Package: gfortran
Version: 4:7.3.0-3
Severity: important
Tags: upstream

While compiling any of the recent versions of exciting: exciting-code.org
gfortran aborts. If I comment the portions of code implied in the error message,
it aborts at other points.
The first position where it aborts is at the piece of code:

fox_m_fsys_format.F90:1289:0:

 if (.not.checkFmt(fmt)) then

The package compiles perfectly with gfortran 6.3 from debian stable.

Best regards
Fulvio Ciriaco

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

Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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)
LSM: AppArmor: enabled

Versions of packages gfortran depends on:
ii  cpp 4:7.3.0-3
ii  gcc 4:7.3.0-3
ii  gfortran-7  7.3.0-21

gfortran recommends no packages.

Versions of packages gfortran suggests:
pn  gfortran-doc   
pn  gfortran-multilib  

-- no debconf information

Bug#901938: RFS: libgooglepinyin/0.1.2-4 [RC]

[Mike Gabriel]

Hi Buyon,

On  Mi 20 Jun 2018 14:51:00 CEST, Boyuan Yang wrote:


Package: sponsorship-requests
Severity: important
X-Debbugs-CC: debian-input-met...@lists.debian.org  
sunwea...@debian.org a...@debian.org


Dear Mike, Aron, debian-input-method team members and mentors,

As a continuation of dealing with massive RC bugs caused by IME team  
maintainer
address migration, I have prepared a team upload for package  
"libgooglepinyin"
and I am looking for a sponsor to push it into unstable. Besides, I  
am looking

for a DD to help importing the packaging git repository onto Salsa from my
temporary repo and grant me (hosiet-guest) the Master role so that previous
packaging commits could be pushed and maintained there.

Transition is not needed since it is merely a rebuild. Its sole reverse
dependency, fcitx-googlepinyin, will be handled by me and uploaded very soon.

Package "libgooglepinyin" is indeed a dead project (hosted on Google Code w/o
migration efforts) but it does provides important features for East  
Asian users

and is worthwhile to be kept inside Debian in the foreseeable future.

* Package name : libgooglepinyin
   Version : 0.1.2-4
   Upstream Author : Weng Xuetian 
 * URL : https://code.google.com/archive/p/libgooglepinyin/
 * License : Apache-2.0
   Section : libs

  It builds those binary packages:

libgooglepinyin0 - Pinyin engine fork from Google Pinyin on Android
libgooglepinyin0-dev - Pinyin engine fork from Google Pinyin on  
Android - development files


Put on my list for tomorrow.

Mike
--

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

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



pgprP0em1rMQU.pgp
Description: Digitale PGP-Signatur

Bug#901939: qgit: Please package new upstream version (v2.8) with updated project homepage

[Andrey Rahmatullin]

On Wed, Jun 20, 2018 at 08:59:01PM +0800, Boyuan Yang wrote:
> According to http://libre.tibirna.org/ , qgit upstream has moved to GitHub and
> released qgit 2.8.
> 
> New upstream homepage is https://github.com/tibirna/qgit .
> 
> Please consider packaging qgit 2.8 and update Homepage field in debian/control
> file.
Yeah, thank you, I've already done most of the work on this (should be on
salsa).

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#901852: claws-mail-spamassassin: Move message marked as Ham to INBOX

[Avinash Sonawane]

On Tue, 19 Jun 2018 16:44:28 +0200
Ricardo Mones  wrote:

> you can already make an action which marks the message as ham and
> moves it to the folder you want, see:
> https://www.claws-mail.org/manual/claws-mail-manual.html#ch_advanced

Action allows executing external command or filtering action but not
both.

By setting 'action' to external spamfilter command, one can merely
teach that spamfilter. Forget moving the message it doesn't even change
the status of that message to 'spam' in Claws UI.

Fortunately, SpamAssassin plugin does that! Trains the SA as well as
marks the message as 'spam' in UI. But sadly, doesn't move the message.

Even if one decides to not use the plugin (as the plugin doesn't move
the message marked as Ham to INBOX (or pre-configure folder)) and
decides to use the 'action' method, how does an external command
can be executed *and* a message can be moved using 'action'?

Regards,
Avinash Sonawane (rootKea)
PICT, Pune
https://rootkea.wordpress.com


pgpEu1A6n7zbv.pgp
Description: OpenPGP digital signature

Bug#899269: [Pkg-samba-maint] Bug#899269: Bug#899269: changes to 4.8

[Mathieu Parent]

Le mer. 20 juin 2018 à 15:19, L.P.H. van Belle  a écrit :
[...]
> So imo, the debian setup the README.Debian should mention something about 
> this.

Merge request appreciated. But it should probably go in the defult
smb.conf instead (which currently uses the obsolete "idmap uid/gid").

Regards

-- 
Mathieu Parent

Bug#901929: transition: openbabel

[Andrius Merkys]

Hi,

On 06/20/2018 02:13 PM, Emilio Pozuelo Monfort wrote:
> Does that mean that some of the rdeps don't build against the new version? Can
> you be more specific on the number, the possible solutions...?

sorry for not being specific enough. I have tested rebuilding of all the 
packages in [1] against the new version of libopenbabel. All seem to build 
successfully except mpqc3, which FTBFS on x86_64 unstable no matter which 
libopenbabel version I use.

Thanks,
Andrius

[1] https://release.debian.org/transitions/html/auto-openbabel.html

-- 
Andrius Merkys
Vilnius University Institute of Biotechnology, Saulėtekio al. 7, room V325
LT-10257 Vilnius, Lithuania

Bug#901932: linux-image-4.16.0-2-amd64: Blank screen after update kernel 4.16.16

[Michael Kümmling]

I have the same issue. It is a problem with the propriatary nvidia
kernel module.
Loading the module works, but starting desktop manager gives a blank screen.

I got the following messages (accessed via ssh):

Jun 20 15:21:08 metropol kernel: resource sanity check: requesting [mem
0x000c-0x000f], which spans more than PCI Bus :00 [mem
0x000c-0x000d window]
Jun 20 15:21:08 metropol kernel: caller _nv001169rm+0xe3/0x1d0 [nvidia]
mapping multiple BARs
Jun 20 15:21:08 metropol kernel: nvidia-modeset: Allocated GPU:0
(GPU-1dd5344e-b699-f58e-ad7d-67c8d97cf99e) @ PCI::01:00.0
Jun 20 15:21:09 metropol kernel: usercopy: Kernel memory exposure
attempt detected from SLUB object 'nvidia_stack_cache' (offset 11440,
size 3)!
Jun 20 15:21:09 metropol kernel: [ cut here ]
Jun 20 15:21:09 metropol kernel: kernel BUG at
/build/linux-s0lf2B/linux-4.16.16/mm/usercopy.c:100!
Jun 20 15:21:09 metropol kernel: invalid opcode:  [#1] SMP NOPTI
Jun 20 15:21:09 metropol kernel: Modules linked in: pci_stub vboxpci(O)
vboxnetadp(O) vboxnetflt(O) vboxdrv(O) binfmt_misc snd_hda_codec_hdmi
pktcdvd fuse tda18212 cxd2841er nls_ascii nls_cp437 edac_mce_amd kvm_amd
vfat ccp rng_core snd_hda_codec_realtek snd_hda_codec_generic kvm fat
irqbypass efi_pstore crct10dif_pclmul snd_hda_intel crc32_pclmul
snd_hda_codec snd_hda_core snd_hwdep evdev ddbridge snd_pcm snd_timer
ghash_clmulni_intel serio_raw pcspkr efivars snd fam15h_power dvb_core
soundcore k10temp sg sp5100_tco nvidia_drm(PO) shpchp button
acpi_cpufreq drm_kms_helper drm nvidia_modeset(PO) nvidia(PO)
ipmi_devintf ipmi_msghandler nct6775 hwmon_vid efivarfs ip_tables
x_tables autofs4 ext4 crc16 mbcache jbd2 fscrypto ecb btrfs
crc32c_generic xor zstd_decompress zstd_compress xxhash raid6_pq
hid_generic usbhid hid
Jun 20 15:21:09 metropol kernel:  sr_mod cdrom sd_mod uas usb_storage
ohci_pci crc32c_intel xhci_pci ahci aesni_intel libahci aes_x86_64
ohci_hcd crypto_simd ehci_pci xhci_hcd ehci_hcd cryptd r8169 glue_helper
libata nvme mii usbcore i2c_piix4 scsi_mod usb_common nvme_core
Jun 20 15:21:09 metropol kernel: CPU: 3 PID: 1698 Comm: Xorg Tainted: P
 O 4.16.0-2-amd64 #1 Debian 4.16.16-1
Jun 20 15:21:09 metropol kernel: Hardware name: To Be Filled By O.E.M.
To Be Filled By O.E.M./970 Pro3 R2.0, BIOS P2.80 05/31/2016
Jun 20 15:21:09 metropol kernel: RIP: 0010:usercopy_abort+0x69/0x80
Jun 20 15:21:09 metropol kernel: RSP: 0018:a9a0c415bb50 EFLAGS: 00010282
Jun 20 15:21:09 metropol kernel: RAX: 006f RBX:
0003 RCX: 
Jun 20 15:21:09 metropol kernel: RDX:  RSI:
9ccb7ecd6738 RDI: 9ccb7ecd6738
Jun 20 15:21:09 metropol kernel: RBP: 0003 R08:
03b4 R09: 0007
Jun 20 15:21:09 metropol kernel: R10: a0077e48 R11:
a07a8dcd R12: 0001
Jun 20 15:21:09 metropol kernel: R13: 9ccb3ceb2cb3 R14:
 R15: 9ccb3ceb2cf8
Jun 20 15:21:09 metropol kernel: FS:  7f3624fb76c0()
GS:9ccb7ecc() knlGS:
Jun 20 15:21:09 metropol kernel: CS:  0010 DS:  ES:  CR0:
80050033
Jun 20 15:21:09 metropol kernel: CR2: 7f361d050d40 CR3:
0003df228000 CR4: 000406e0
Jun 20 15:21:09 metropol kernel: Call Trace:
Jun 20 15:21:09 metropol kernel:  __check_heap_object+0xe7/0x120
Jun 20 15:21:09 metropol kernel:  __check_object_size+0x9c/0x1a0
Jun 20 15:21:09 metropol kernel:  os_memcpy_to_user+0x21/0x40 [nvidia]
Jun 20 15:21:09 metropol kernel:  _nv009383rm+0xbf/0xe0 [nvidia]
Jun 20 15:21:09 metropol kernel:  ? _nv028084rm+0x79/0x90 [nvidia]
Jun 20 15:21:09 metropol kernel:  ? _nv028084rm+0x55/0x90 [nvidia]
Jun 20 15:21:09 metropol kernel:  ? _nv013694rm+0xee/0x100 [nvidia]
Jun 20 15:21:09 metropol kernel:  ? _nv015342rm+0x154/0x270 [nvidia]
Jun 20 15:21:09 metropol kernel:  ? _nv008316rm+0x134/0x1a0 [nvidia]
Jun 20 15:21:09 metropol kernel:  ? _nv008295rm+0x29c/0x2b0 [nvidia]
Jun 20 15:21:09 metropol kernel:  ? _nv001072rm+0xe/0x20 [nvidia]
Jun 20 15:21:09 metropol kernel:  ? _nv007322rm+0xd8/0x100 [nvidia]
Jun 20 15:21:09 metropol kernel:  ? _nv001171rm+0x627/0x830 [nvidia]
Jun 20 15:21:09 metropol kernel:  ? rm_ioctl+0x73/0x100 [nvidia]
Jun 20 15:21:09 metropol kernel:  ? nvidia_ioctl+0xb0/0x720 [nvidia]
Jun 20 15:21:09 metropol kernel:  ? nvidia_ioctl+0x573/0x720 [nvidia]
Jun 20 15:21:09 metropol kernel:  ?
nvidia_frontend_unlocked_ioctl+0x3e/0x50 [nvidia]
Jun 20 15:21:09 metropol kernel:  ? do_vfs_ioctl+0xa4/0x630
Jun 20 15:21:09 metropol kernel:  ? handle_mm_fault+0xdc/0x210
Jun 20 15:21:09 metropol kernel:  ? SyS_ioctl+0x74/0x80
Jun 20 15:21:09 metropol kernel:  ? do_syscall_64+0x6c/0x130
Jun 20 15:21:09 metropol kernel:  ? entry_SYSCALL_64_after_hwframe+0x3d/0xa2
Jun 20 15:21:09 metropol kernel: Code: 0f 44 d0 53 48 c7 c0 41 de 03 a0
51 48 c7 c6 dd d3 02 a0 41 53 48 89 f9 48 0f 45 f0 4c 89 d2 48 c7 c7 28
df 03 a0 e8 f1 2e ea ff <0f> 0b 49 c7 c1 ac de 04 a0 4

Bug#901944: ITP: dupd -- A fast and efficient CLI file duplicate detection utility

[Daniel Sullivan]

Package: dupd
Severity: wishlist
Owner: 'Daniel Sullivan' 


*Package Name : dupd
 Version : 1.6
 Upstream Author : Jyri J. Virkki 
*URL : https://github.com/jvirkki/dupd
*License : GPL-3.0+
*Description : A fast and efficient CLI file duplicate detection utility

Bug#901930: [pkg-wicd-maint] Bug#901930: crash upon trying to enter "Config"

[Toni Mueller]

Hi Axel,

On Wed, Jun 20, 2018 at 02:06:41PM +0200, Axel Beckert wrote:
> On a first glance it looks as if this issue only happens if a specific
> flow path is taken in wicd-curses. It would be interesting to know
> under which circumstances it exactly happens for you.
> 
> I assume it's reproducible for you.

yes, it is: On a buster machine, installed yesterday and today, I can do
the following:

* as root, start wicd-curses.
* press the right arrow key
* crash!


Cheers,
Toni

Bug#901945: apt-cudf: apt install --solver mccs-cbc fails with "Please specifify the optimization criteria using --criteria-plain"

[Julian Andres Klode]

Package: apt-cudf
Version: 5.0.1-10
Severity: normal

It seems criteria-plain solvers are broken by default.

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

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

Versions of packages apt-cudf depends on:
ii  aspcud [cudf-solver]  1:1.9.4-1
ii  libbz2-1.01.0.6-8.1
ii  libc6 2.27-3ubuntu1
ii  mccs [cudf-solver]1:1.1-7
ii  packup [cudf-solver]  0.6-3
ii  perl  5.26.1-6
ii  zlib1g1:1.2.11.dfsg-0ubuntu2

apt-cudf recommends no packages.

apt-cudf suggests no packages.

-- debconf-show failed

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#901852: claws-mail-spamassassin: Move message marked as Ham to INBOX

[Avinash Sonawane]

We have 'Save spam in' in SpamAssasin plugin settings.
How about adding 'Save spam messages marked as ham in'?

Now it's completely up to user's discretion as to where to save
spam messages which are marked as Ham. This should help us answer
some of your questions!

Regards,
Avinash Sonawane (rootKea)
PICT, Pune
https://rootkea.wordpress.com


pgpnnhVQSz48V.pgp
Description: OpenPGP digital signature

Bug#901801: Bug#901794: ITP: check-pgactivity -- PostgreSQL plugin for Nagios

[Christoph Berg]

Re: Christophe Courtois 2018-06-18 
<152932664119.27238.10739173586687082058.report...@pegase.dalibo.net>
> This would be my first package. First tests are encouraging. I intend to
> maintain it (and others) as a part of my job. While the goal is the mainstream
> Debian, I suppose that I need a mentor from the PDGD team.

Re: Christophe Courtois 2018-06-18 
<152932929747.13026.10517626334155921077.report...@pegase.dalibo.net>
> This is ideal for my first package with compilation. My first tests are
> encouraging. I intend to maintain it as part of my current job. The upstream
> author is a colleague.
> 
> Maintenance would be in Debian PostgreSQL Maintainers.

Hi,

this is very interesting! please get in touch with me (e.g. on IRC,
I'm Myon) so we can properly set up the packages.

Thanks,
Christoph

Bug#901897: git introduces new hazardous working-tree-encoding attribute

[Paul Gevers]

On Tue, 19 Jun 2018 18:28:13 -0700 Jonathan Nieder 
wrote:
> By the way, is there a way to trigger these autopkgtests automatically
> with git from experimental as well?  That way, I'd get earlier notice
> about these issues.

Not yet. It's on my list to add experimental support in ci.d.n, but it
hasn't materialized yet.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#901946: nmu: dovecot-antispam_2.0+20171229-1

[Apollon Oikonomopoulos]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Dear Release Team,

Please schedule a binNMU for dovecot-antispam to be built against the 
current dovecot version.

Regards,
Apollon

nmu dovecot-antispam_2.0+20171229-1 . ANY . unstable . -m "Rebuild against 
dovecot 2.2.36"

Bug#899259: cups-daemon: with IdleExitTimeout 60, fails to exit after 60 s of inactivity

[Brian Potkin]

On Wed 20 Jun 2018 at 00:31:19 +0200, Francesco Poli wrote:

> On Tue, 19 Jun 2018 14:25:07 +0100 Brian Potkin wrote:
> 
> [...]
> >   A temporary workaround is to run:
> > 
> > cupsctl Browsing=No
> > 
> >   to restore the CUPS default setting.
> > 
> > How do you go on with that, Francesco?
> 
> I can try, but I already have:
> 
>   $ grep Browsing /etc/cups/cupsd.conf 
>   Browsing Off

I also tried with this but it didn't give me anything that I would
want to recommend. Indeed, socket deacativation took place at the
first printing attempt but thereafter the timeout behaviour was
inconsistent. However, IMO, the suggestion and the committed code
from upstream are the best we are going to get for now.

Looking at the debug2 error log lead me to putting

  PreserveJobHistory No

in cupsd.conf. This gives reliable and consistent socket activation
and timing out. How about for you?

Cheers,

Brian.

Bug#901915: monero: Incomplete debian/copyright?

[Chris Lamb]

Hi Jonas,

> gtest code copy I simply forgot to list

Thanks.

> I fail to locate any omission under src/ringct/.  If you mean the 
> references to Sarang Noether then I believe that is  […]

I'm afraid I can't recall exactly what it was but if there is any
ambiguity whatsoever please clarify this in debian/copyright.

After all, there was probably /some/ reason why I didn't immediately
understand what was going on and we should fix that in the packaging
(and not document it on bugs like this where it will get lost).

Thanks :)


Regards,

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

Bug#901867: [gnome] Now also happens in my laptop

[rastersoft]

Package: gnome
Version: 1:3.22+9

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

Today I updated my laptop (which I kept without updating for nearly a 
month to avoid bug 897975), and now the same is happening to it: when 
launching gnome shell with Wayland, and opening a firefox, loading some 
pages (now it is Facebook) completely hangs the computer.


My laptop is a Zenbook UX21E, with an i3-2367 processor and Intel HD 
Graphics 3000, while my other computer (the one in the first report) is 
an i5-4440 with a Radeon HD7750 graphics card.


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

Debian Release: buster/sid
500 unstable ftp.debian.org
500 stable packages.microsoft.com
500 stable dl.google.com

--- Package information. ---
Depends (Version) | Installed
-+-=
gnome-core (= 1:3.22+9) | 1:3.22+9
desktop-base | 9.0.7
network-manager-gnome (>= 1.4) | 1.8.12-2
libproxy1-plugin-networkmanager | 0.4.15-1
cheese (>= 3.22) | 3.28.0-1
evolution (>= 3.22) | 3.28.2-1
evolution-plugins (>= 3.22) | 3.28.2-1
file-roller (>= 3.22) | 3.28.0-2
gnome-calendar (>= 3.22) | 3.28.2-1
gnome-clocks (>= 3.22) | 3.28.0-1
gnome-color-manager (>= 3.22) | 3.28.0-1
gnome-documents (>= 3.22) | 3.28.0-1
gnome-getting-started-docs (>= 3.22) | 3.28.2-1
gnome-maps (>= 3.22) | 3.28.2-1
gnome-music (>= 3.22) | 3.28.2.1-1
gnome-todo (>= 3.22) | 3.28.1-1
shotwell | 0.26.4-1
OR gnome-photos (>= 3.22) |
gnome-screenshot (>= 3.22) | 3.26.0-3
gnome-sound-recorder | 3.28.1-1
gnome-tweaks (>= 3.22) | 3.28.1-1
gnome-weather (>= 3.20) | 3.26.0-4
nautilus-sendto (>= 3.8) | 3.8.6-2
orca (>= 3.22) | 3.28.1-1
rygel-playbin (>= 0.24) | 0.36.1-1
rygel-tracker (>= 0.24) | 0.36.1-1
seahorse (>= 3.20) | 3.20.0-5
simple-scan | 3.26.2-1
vinagre (>= 3.22) | 3.22.0-5
avahi-daemon | 0.7-4
gimp (>= 2.8) | 2.10.2-1
inkscape (>= 0.48) | 0.92.3-2
libreoffice-gnome | 1:6.0.5~rc1-2
libreoffice-writer | 1:6.0.5~rc1-2
libreoffice-calc | 1:6.0.5~rc1-2
libreoffice-impress | 1:6.0.5~rc1-2
libgsf-bin | 1.14.43-1
rhythmbox (>= 3.0) | 3.4.2-4
vino (>= 3.22) | 3.22.0-3
xdg-user-dirs-gtk | 0.10-2
cups-pk-helper (>= 0.2) | 0.2.6-1+b1
gedit-plugins (>= 3.22) | 3.28.1-1
gstreamer1.0-libav (>= 1.10) | 1.14.1-1
gstreamer1.0-plugins-ugly (>= 1.10) | 1.14.1-1+b1
rhythmbox-plugins | 3.4.2-4
rhythmbox-plugin-cdrecorder | 3.4.2-4
totem-plugins | 3.26.0-3+b1
libgtk2-perl (>= 1:1.130) | 2:1.24992-1+b1
gnome-core (= 1:3.22+9) | 1:3.22+9
desktop-base | 9.0.7
network-manager-gnome (>= 1.4) | 1.8.12-2
libproxy1-plugin-networkmanager | 0.4.15-1
cheese (>= 3.22) | 3.28.0-1
evolution (>= 3.22) | 3.28.2-1
evolution-plugins (>= 3.22) | 3.28.2-1
file-roller (>= 3.22) | 3.28.0-2
gnome-calendar (>= 3.22) | 3.28.2-1
gnome-clocks (>= 3.22) | 3.28.0-1
gnome-color-manager (>= 3.22) | 3.28.0-1
gnome-documents (>= 3.22) | 3.28.0-1
gnome-getting-started-docs (>= 3.22) | 3.28.2-1
gnome-maps (>= 3.22) | 3.28.2-1
gnome-music (>= 3.22) | 3.28.2.1-1
gnome-todo (>= 3.22) | 3.28.1-1
shotwell | 0.26.4-1
OR gnome-photos (>= 3.22) |
gnome-screenshot (>= 3.22) | 3.26.0-3
gnome-sound-recorder | 3.28.1-1
gnome-tweaks (>= 3.22) | 3.28.1-1
gnome-weather (>= 3.20) | 3.26.0-4
nautilus-sendto (>= 3.8) | 3.8.6-2
orca (>= 3.22) | 3.28.1-1
rygel-playbin (>= 0.24) | 0.36.1-1
rygel-tracker (>= 0.24) | 0.36.1-1
seahorse (>= 3.20) | 3.20.0-5
simple-scan | 3.26.2-1
vinagre (>= 3.22) | 3.22.0-5
avahi-daemon | 0.7-4
gimp (>= 2.8) | 2.10.2-1
inkscape (>= 0.48) | 0.92.3-2
libreoffice-gnome | 1:6.0.5~rc1-2
libreoffice-writer | 1:6.0.5~rc1-2
libreoffice-calc | 1:6.0.5~rc1-2
libreoffice-impress | 1:6.0.5~rc1-2
libgsf-bin | 1.14.43-1
rhythmbox (>= 3.0) | 3.4.2-4
vino (>= 3.22) | 3.22.0-3
xdg-user-dirs-gtk | 0.10-2
cups-pk-helper (>= 0.2) | 0.2.6-1+b1
gedit-plugins (>= 3.22) | 3.28.1-1
gstreamer1.0-libav (>= 1.10) | 1.14.1-1
gstreamer1.0-plugins-ugly (>= 1.10) | 1.14.1-1+b1
rhythmbox-plugins | 3.4.2-4
rhythmbox-plugin-cdrecorder | 3.4.2-4
totem-plugins | 3.26.0-3+b1
libgtk2-perl (>= 1:1.130) | 2:1.24992-1+b1
libatk-adaptor (>= 2.22) | 2.26.2-1
at-spi2-core (>= 2.22) | 2.28.0-3
adwaita-icon-theme | 3.28.0-1
baobab (>= 3.22) | 3.28.0-2
fonts-cantarell (>= 0.0.25) | 0.0.25-4
caribou (>= 0.4.21) | 0.4.21-5
dconf-cli (>= 0.26) | 0.28.0-2
dconf-gsettings-backend (>= 0.26) | 0.28.0-2
eog (>= 3.20) | 3.28.2-1
evince (>= 3.22) | 3.28.2-1
evolution-data-server (>= 3.22) | 3.28.2-1+b1
sound-theme-freedesktop | 0.8-2
gdm3 (>= 3.22) | 3.28.2-3
gedit (>= 3.22) | 3.28.1-1
glib-networking (>= 2.50) | 2.56.0-1
gnome-backgrounds (>= 3.22) | 3.28.0-1
gnome-bluetooth (>= 3.20) | 3.28.0-2
gnome-calculator (>= 3.22) | 3.28.1-1
gnome-characters (>= 3.22) | 3.28.2-1
gnome-contacts (>= 3.22) | 3.28.2-1
gnome-control-center (>= 1:3.22) | 1:3.28.1-1
gnome-disk-utility (>= 3.22) | 3.28.1-1
gnome-font-viewer (>= 3.22) | 3.28.0-1
gnome-keyring (>= 3.20) | 3.28.2-1
libpam-gnome-keyring (>= 3.20) | 3.28.2-1
gnome-logs (>= 3.22) | 3.28.2-1
gnome-menus (>= 3.13) | 3.13.3-11
gnome-online-ac

Bug#900851: [Pkg-deepin-devel] Bug#900851: Papirus icon theme in Stretch backports request

[Yangfl]

2018-06-19 21:36 GMT+08:00 Samuel Henrique :
>
> Thanks for the access, i can sponsor any backports uploads for sure, count
> with me if you need some help within the deepin team, although i won't have
> too much time to do ~actual~ work right now, i can do some backport uploads
> of other packages if needed.

If you (or your friends) are interested in deepin desktop environment,
you can do more backports jobs with dde applications, of course. Any
kind of help is highly welcomed.

>
> From what i've seen, you're a small team on Salsa and it looks like czchen
> is the only one with uploads permissions but he is also helping with
> Debconf. The work of packaging the Deepin tools is highly valuable by a lot
> of users i know, are you in need of people to sponsor uploads/review
> packages right now?
>

You can see the progress of packaging in
https://salsa.debian.org/pkg-deepin-team/progress-tracker/blob/master/depgraph/pkg-deepin-dep.svg
. Many dde applications have find their way into main repo, but our
work is basically paused regarding of the golang part below, because
many deps don't meet our (members') criteria. Other DDs are kindly
enough to sponsor us to do regular updating works, so we might not
need a dedicated hand for this in a short time. If we need to upload
new packages, we will send rfs for it as usual.

Thank for your help in papirus-icon-theme.

Bug#901788: i2pd: systemd service does not run

[sergey]

When I run it from terminal I get the same error. No systemd involved.

Command: strace /usr/sbin/i2pd --conf=/etc/i2pd/i2pd.conf 
--tunconf=/etc/i2pd/tunnels.conf --pidfile=/tmp/i2pd.pid 
--logfile=/tmp/i2pd.log 2> /tmp/strace_i2pd.log

Bug#901948: [libsignal-protocol-c] New version of library is available

[Boris Pek]

Source: libsignal-protocol-c
Version: 2.3.1+git20171007-3
Severity: wishlist


Hi,

Could you update this library to latest git tag [1]?
Small discussion about it may be found at [2].

[1] https://github.com/signalapp/libsignal-protocol-c/releases/tag/v2.3.2
[2] https://github.com/signalapp/libsignal-protocol-c/issues/107

Best regards,
Boris

Bug#901792: claws-mail-clamd-plugin: Save infected emails in respective spam folders

[Avinash Sonawane]

On Wed, 20 Jun 2018 16:50:33 +0200
Ricardo Mones  wrote:
 
> Not sure why do you mix infected mails with spam folders. Also don't
> see what this could be useful for or what are you trying to achieve.

As I have mentioned previously, I have 2 IMAP accounts. My use-case is
to keep the emails from both the accounts separate (may be because I
don't trust at least 1 of them?). Anyways, so I would like to store the
emails identified by Clam as "infected" on respective IMAP servers
separate from each other.

> Could you explain which benefit arises from spreading infected mails
> in several folders?

It's not about spreading infected mails in several folders but about
keeping mails separate in respective IMAP accounts.

Regards,
Avinash Sonawane (rootKea)
PICT, Pune
https://rootkea.wordpress.com


pgppAKofkDXzC.pgp
Description: OpenPGP digital signature

Bug#901932: linux-image-4.16.0-2-amd64: Blank screen after update kernel 4.16.16

[Ben Hutchings]

Control: reassign -1 src:nvidia-graphics-drivers

On Wed, 2018-06-20 at 13:19 +0200, jerome wrote:
> Package: src:linux
> Version: 4.16.16-1
> Severity: important
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where
> appropriate ***
> 
>* What led up to the situation?
> Blank (black) screen after kernel image 4.16.16 update. 
> At boot the system don't response after the kernel loading, i have to
> do hard reset from power button.
[...]
> nvidia_drm(PO)
[...]
> nvidia_modeset(PO)
> nvidia(PO)
[...]

You are using nvidia drivers which are not part of this package.

Ben.

-- 
Ben Hutchings
Horngren's Observation:
  Among economists, the real world is often a special case.



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

Bug#901792: claws-mail-clamd-plugin: Save infected emails in respective spam folders

[Ricardo Mones]

control: tags -1 moreinfo
control: severity -1 wishlist

On Mon, Jun 18, 2018 at 06:09:02PM +0530, Avinash Sonawane wrote:
> Package: claws-mail-clamd-plugin
> Version: 3.14.1-3+b1
> Severity: normal
> 
> Dear Maintainer,
> 
> I'm using Claws-mail 3.14.1 with Clam Antivirus plugin. I am managing
> 2 email accounts with separate INBOX, Trash, Spam folders.
> 
> There doesn't seem to be a way to configure Clam Antivirus plugin such
> that the infected emails get saved in respective Spam folders.

Not sure why do you mix infected mails with spam folders. Also don't see
what this could be useful for or what are you trying to achieve.

Could you explain which benefit arises from spreading infected mails in
several folders?

Anyway, this is clearly a feature request so tagging it accordingly.

regards,
-- 
  Ricardo Mones 
  ~
  15:14 <@mones> you're overconfident today :) 
  15:14 <@claws> i will be this way forever nowSeen on #claws



signature.asc
Description: PGP signature

Bug#901919: nvidia-driver: black screen with the latest Linux kernel - general protection fault

[Diederik de Haas]

Package: nvidia-driver
Version: 390.59-1
Followup-For: Bug #901919

Control tag -1 confirmed

I can confirm this issue which occured with 4.16.16-1, but not with 4.16.12-1

my relevant part of kern.log
Jun 13 16:32:53 bagend kernel: [6.992399] [ cut here 
]
Jun 13 16:32:53 bagend kernel: [6.992401] Bad or missing usercopy 
whitelist? Kernel memory exposure attempt detected from SLUB object 
'nvidia_stack_cache' (offset 11440, size 3)!
Jun 13 16:32:53 bagend kernel: [6.992409] WARNING: CPU: 5 PID: 1110 at 
/build/linux-43CEzF/linux-4.16.12/mm/usercopy.c:81 usercopy_warn+0x7e/0xa0
Jun 13 16:32:53 bagend kernel: [6.992409] Modules linked in: pci_stub 
vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) snd_hda_codec_hdmi 
cpufreq_powersave cpufreq_conservative cpufreq_userspace binfmt_misc 
edac_mce_amd snd_hda_codec_realtek kvm_amd pl2303 snd_hda_codec_generic 
usbserial kvm eeepc_wmi asus_wmi sparse_keymap irqbypass crct10dif_pclmul 
rfkill crc32_pclmul joydev video wmi_bmof mxm_wmi evdev snd_hda_intel 
ghash_clmulni_intel snd_hda_codec snd_hda_core snd_hwdep pcspkr ccp k10temp 
snd_pcm rng_core snd_timer sp5100_tco snd soundcore sg shpchp wmi button 
acpi_cpufreq nvidia_drm(PO) drm_kms_helper drm nvidia_modeset(PO) nvidia(PO) 
ipmi_devintf ipmi_msghandler loop parport_pc ppdev lp parport sunrpc ip_tables 
x_tables autofs4 ext4 crc16 mbcache jbd2 fscrypto btrfs zstd_decompress 
zstd_compress xxhash raid10 raid456
Jun 13 16:32:53 bagend kernel: [6.992437]  async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
md_mod sd_mod hid_logitech_hidpp hid_logitech_dj hid_microsoft hid_generic 
usbhid hid crc32c_intel aesni_intel ahci xhci_pci aes_x86_64 libahci 
crypto_simd xhci_hcd cryptd glue_helper libata i2c_piix4 igb e1000e nvme 
i2c_algo_bit usbcore dca scsi_mod usb_common nvme_core gpio_amdpt gpio_generic
Jun 13 16:32:53 bagend kernel: [6.992453] CPU: 5 PID: 1110 Comm: Xorg 
Tainted: P   O 4.16.0-2-amd64 #1 Debian 4.16.12-1
Jun 13 16:32:53 bagend kernel: [6.992454] Hardware name: System 
manufacturer System Product Name/CROSSHAIR VI HERO, BIOS 6101 04/19/2018
Jun 13 16:32:53 bagend kernel: [6.992455] RIP: 0010:usercopy_warn+0x7e/0xa0
Jun 13 16:32:53 bagend kernel: [6.992456] RSP: 0018:a95c47637b60 
EFLAGS: 00010282
Jun 13 16:32:53 bagend kernel: [6.992457] RAX:  RBX: 
959fc6e35cb0 RCX: 0006
Jun 13 16:32:53 bagend kernel: [6.992457] RDX: 0007 RSI: 
0096 RDI: 959fde756730
Jun 13 16:32:53 bagend kernel: [6.992458] RBP: 0003 R08: 
0404 R09: 0004
Jun 13 16:32:53 bagend kernel: [6.992458] R10: 8be77220 R11: 
0001 R12: 0001
Jun 13 16:32:53 bagend kernel: [6.992459] R13: 959fc6e35cb3 R14: 
 R15: 959fc6e35cf8
Jun 13 16:32:53 bagend kernel: [6.992460] FS:  7f2371b096c0() 
GS:959fde74() knlGS:
Jun 13 16:32:53 bagend kernel: [6.992460] CS:  0010 DS:  ES:  CR0: 
80050033
Jun 13 16:32:53 bagend kernel: [6.992461] CR2: 7f2369bed130 CR3: 
000fbfcf8000 CR4: 003406e0
Jun 13 16:32:53 bagend kernel: [6.992462] Call Trace:
Jun 13 16:32:53 bagend kernel: [6.992465]  __check_object_size+0x9c/0x1a0
Jun 13 16:32:53 bagend kernel: [6.992547]  os_memcpy_to_user+0x21/0x40 
[nvidia]
Jun 13 16:32:53 bagend kernel: [6.992658]  _nv009383rm+0xbf/0xe0 [nvidia]
Jun 13 16:32:53 bagend kernel: [6.992755]  ? _nv028084rm+0x79/0x90 [nvidia]
Jun 13 16:32:53 bagend kernel: [6.992850]  ? _nv028084rm+0x55/0x90 [nvidia]
Jun 13 16:32:53 bagend kernel: [6.992939]  ? _nv013694rm+0xee/0x100 [nvidia]
Jun 13 16:32:53 bagend kernel: [6.993027]  ? _nv015342rm+0x154/0x270 
[nvidia]
Jun 13 16:32:53 bagend kernel: [6.993134]  ? _nv008316rm+0x134/0x1a0 
[nvidia]
Jun 13 16:32:53 bagend kernel: [6.993240]  ? _nv008295rm+0x29c/0x2b0 
[nvidia]
Jun 13 16:32:53 bagend kernel: [6.993346]  ? _nv001072rm+0xe/0x20 [nvidia]
Jun 13 16:32:53 bagend kernel: [6.993453]  ? _nv007322rm+0xd8/0x100 [nvidia]
Jun 13 16:32:53 bagend kernel: [6.993566]  ? _nv001171rm+0x627/0x830 
[nvidia]
Jun 13 16:32:53 bagend kernel: [6.993681]  ? rm_ioctl+0x73/0x100 [nvidia]
Jun 13 16:32:53 bagend kernel: [6.993755]  ? nvidia_ioctl+0xf0/0x720 
[nvidia]
Jun 13 16:32:53 bagend kernel: [6.993828]  ? nvidia_ioctl+0x519/0x720 
[nvidia]
Jun 13 16:32:53 bagend kernel: [6.993830]  ? kmem_cache_free+0x19c/0x1d0
Jun 13 16:32:53 bagend kernel: [6.993903]  ? 
nvidia_frontend_unlocked_ioctl+0x3e/0x50 [nvidia]
Jun 13 16:32:53 bagend kernel: [6.993904]  ? do_vfs_ioctl+0xa4/0x630
Jun 13 16:32:53 bagend kernel: [6.993906]  ? __fput+0x164/0x1e0
Jun 13 16:32:53 bagend kernel: [6.993907]  ? SyS_ioctl+0x74/0x80
Jun 13 16:32:53 bagend kernel: [6.993909]  ? do_s

Bug#901884: [pkg-cryptsetup-devel] Bug#901884: (no subject)

[Guilhem Moulin]

On Wed, 20 Jun 2018 at 06:42:03 +, 901...@chiru.no wrote:
> This line:
> blockcipher="$(printf '%s' "$value" | cut -d':' -f1 | cut -d'-' -f1)"
> should be:
> blockcipher="$(printf '%s' "$value" | cut -d':' -f1 | cut -d'-' -f2)"

That's indeed the regression, causing modules required for the cipher
mode not to be included to the initrd, for instance with AES-XTS on CPUs
lacking the AES-NI instruction set.

But it's wasn't the only problem with that code.  Looking closer at the
specs [0], the mapping table format for crypt target prints the cipher
specifications in the following format

cipher[:keycount]-chainmode-ivmode[:ivopts]

or (since linux 4.12)

capi:cipher_api_spec-ivmode[:ivopts]

Determining the cipher/mode/IV to use in the first format when a
keycount is present, such as "aes:64-cbc-lmk", or in the second format,
such as "capi:xts(aes)-plain64", was already broken in <2:2.0.3-2.  The
former is now fixed, for the latter a warning is now displayed.

-- 
Guilhem.

[0] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/device-mapper/dm-crypt.txt


signature.asc
Description: PGP signature

Bug#901915: monero: Incomplete debian/copyright?

[Jonas Smedegaard]

Quoting Chris Lamb (2018-06-20 16:33:17)
>> I fail to locate any omission under src/ringct/.  If you mean the 
>> references to Sarang Noether then I believe that is […]
>
> I'm afraid I can't recall exactly what it was but if there is any 
> ambiguity whatsoever please clarify this in debian/copyright.
> 
> After all, there was probably /some/ reason why I didn't immediately 
> understand what was going on and we should fix that in the packaging 
> (and not document it on bugs like this where it will get lost).

I agree that any ambiguity should be reflected in debian/copyright.

I am unaware of any ambiguity now (after adding the gtest part), 
however, and consider this bugreport solved.

If you recall/rediscover more info, please do share it here.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#831699: release.debian.org: urgency is sticky across dists - low urgency on sid upload ignored

[Ian Jackson]

I have just read this bug report (which affects a situation I care
about) and I don't quite understand.

Adam writes:
> britney knows nothing about changelogs. The input is a strictly
> chronological (in terms of when dak accepted the package) list of
> source package name, version and urgency tuples for all uploads to
> the main archive.

What I don't understand is why it is not correct for britney to use
the urgency of the actual version it is considering migrating, rather
than some other version.

Or is that what it does ?  I get the impression from what was written
in this bug that it does something more complicated, but that may be a
misunderstanding.

(Sadly no-one copied the actual database information from the original
case into the bug log, so it is not now possible to make sense of what
is written early in the bug.)

I assume that the urgency information reported by dak to britney is
that from the .changes file.  Is that right ?

I experimented and dpkg-genchanges -vX provides a Changes file with
the maximum urgency of any of the included changelog stanzas.  So if
you say

   blah (2.0-3) unstable; urgency=low
   blah (2.0-2) experimental; urgency=high
   blah (2.0-1) experimental; urgency=medium
   blah (1.0-1) unstable; urgency=whatever

and you (correctly) do your upload of 2.0-3 to unstable with -v1.0-1,
the .changes file will say `high', even though from the pov of users
of unstable and testing, it ought to be `low'.

I think that the right fix for this bug is as follows:

 dpkg-genchanges should not consider as higher-urgency any changelog
 entries for "unrelated" suites in previous changelog entries that are
 being included, as a reason to bump the urgency for *this* .changes.
 (An "unrelated" suite is perhaps one whose ^\w+ is not the same as
 that of the final, target, suite.)

 Ie in the examle above, dpkg-genchanges -v1.0-1 should say
 Urgency: medium.

 dak should use the Urgency from the .changes file and report that in
 its /britney/urgencies output.  (It may already do this.)

 britney should use the urgency of the particular package, only.
 (It may already do this.)

 An in-archive copy should not be done to move a package into testing,
 since doing so does not afford anyone the opportunity to specify the
 proper urgency.  (I don't think we do this.)

What do others think ?

Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#901788: i2pd: systemd service does not run

[Yangfl]

2018-06-20 22:55 GMT+08:00 sergey :
> When I run it from terminal I get the same error. No systemd involved.
>
> Command: strace /usr/sbin/i2pd --conf=/etc/i2pd/i2pd.conf
> --tunconf=/etc/i2pd/tunnels.conf --pidfile=/tmp/i2pd.pid
> --logfile=/tmp/i2pd.log 2> /tmp/strace_i2pd.log

can't reproduce, neither sudo -u i2pd -g i2pd /usr/sbin/i2pd nor sudo
-u i2pd -g i2pd /usr/sbin/i2pd --conf=/etc/i2pd/i2pd.conf
--tunconf=/etc/i2pd/tunnels.conf --pidfile=/tmp/i2pd.pid
--logfile=/tmp/i2pd.log, but without systemd, since i'm using a clean
chroot.

Bug#831699: release.debian.org: urgency is sticky across dists - low urgency on sid upload ignored

[Adam D. Barratt]

On 2018-06-20 15:55, Ian Jackson wrote:

I have just read this bug report (which affects a situation I care
about) and I don't quite understand.

Adam writes:

britney knows nothing about changelogs. The input is a strictly
chronological (in terms of when dak accepted the package) list of
source package name, version and urgency tuples for all uploads to
the main archive.


What I don't understand is why it is not correct for britney to use
the urgency of the actual version it is considering migrating, rather
than some other version.


If you upload 1.0-2 containing an RC bug fix, so with "Urgency: high" 
and then, before 1.0-2 has migrated, upload 1.0-3 with default urgency, 
what should happen?


Currently the result is that the "high" from 1.0-2 is used, and 1.0-3 
(including the RC bug fix) migrates two days later. If only 1.0-3's 
urgency is considered, the package spends at least another five days in 
unstable before the RC fix reaches testing.


Regards,

Adam

Bug#901949: qemubuilder: No information on what KERNEL_IMAGE is about

[Bob Ham]

Package: qemubuilder
Version: 0.85
Severity: normal

Dear Maintainer,

   * What led up to the situation?

I was trying to use qemubuilder to build some armhf packages on amd64.

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

I ran qemubuilder and it told me:

E: No KERNEL_IMAGE defined in pbuilderrc
E: qemu exited unexpectedly: 256

Then I looked in the man page for information that would help me set
KERNEL_IMAGE to a useful value.


   * What was the outcome of this action?

I saw this:

   KERNEL_IMAGE=vmlinuz
  Linux kernel to use.

   * What outcome did you expect instead?

Some kind of information about what the "vmlinuz" value is meant to
refer to (is it a local file, name of a package, file in the target
file system, etc.), why I need to set this option and how the value
will be used.


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

Kernel: Linux 4.17.0-linux-latest-5 (SMP w/16 CPU cores; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages qemubuilder depends on:
ii  debootstrap 1.0.89
ii  libc6   2.26-6
ii  libncurses5 6.0+20161126-1+deb9u1
ii  libtinfo5   6.0+20161126-1+deb9u1
ii  pbuilder0.228.7
ii  qemu-kvm [kvm]  1:2.8+dfsg-6+deb9u4
ii  qemu-system 1:2.8+dfsg-6+deb9u4

qemubuilder recommends no packages.

qemubuilder suggests no packages.

-- no debconf information

Bug#901950: claws-mail-fancy-plugin: HTML email is not getting rendered properly

[Avinash Sonawane]

Package: claws-mail-fancy-plugin
Version: 3.14.1-3+b1
Severity: important

Dear Maintainer,

I'm using Claws Mail 3.14.1 with Fancy plugin.

I have from Fancy settings set 'Enable loading of remote control', 'Display
images', 'Execute javascript', 'Execute java applets', 'Render objects using
plugins' to on.

I have also set 'Automatically display attached images', 'Resize attached
images by default', 'Display images inline' from Preferences/Message View/Image
Viewer to on.

But still the HTML email is being displayed as plain text while I can see the
HTML links lying in the very same email using another mail client.



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

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

Versions of packages claws-mail-fancy-plugin depends on:
ii  claws-mail  3.14.1-3+b1
ii  libatk1.0-0 2.22.0-1
ii  libc6   2.24-11+deb9u3
ii  libcairo2   1.14.8-1
ii  libcurl3-gnutls 7.52.1-5+deb9u6
ii  libdb5.35.3.28-12+deb9u1
ii  libetpan17  1.6-3
ii  libfontconfig1  2.11.0-6.7+b1
ii  libfreetype62.6.3-3.2
ii  libgdk-pixbuf2.0-0  2.36.5-2+deb9u2
ii  libglib2.0-02.50.3-2
ii  libgnutls30 3.5.8-5+deb9u3
ii  libgtk2.0-0 2.24.31-2
ii  libjavascriptcoregtk-1.0-0  2.4.11-3
ii  liblockfile11.14-1+b1
ii  libpango-1.0-0  1.40.5-1
ii  libpangocairo-1.0-0 1.40.5-1
ii  libpangoft2-1.0-0   1.40.5-1
ii  libsasl2-2  2.1.27~101-g0780600+dfsg-3
ii  libsoup2.4-12.56.0-2+deb9u1
ii  libwebkitgtk-1.0-0  2.4.11-3
ii  zlib1g  1:1.2.8.dfsg-5

claws-mail-fancy-plugin recommends no packages.

Versions of packages claws-mail-fancy-plugin suggests:
pn  html2ps  

-- no debconf information

Bug#901915: monero: Incomplete debian/copyright?

[Chris Lamb]

Hi Jonas,

> I am unaware of any ambiguity now (after adding the gtest part), 
> however, and consider this bugreport solved.

Thanks. It /might/ have been that this had a different author ("Shen"
rings a bell) but if the Copyright is the same then I'm happy. :)


Regards,

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