Bug#855267: debian mirror mirrors.liquidweb.com - broken HTTP

[Peter Palfrader]

Ping.

On Thu, 16 Feb 2017, Peter Palfrader wrote:

> Hi,
> 
> I was checking some things in the Debian mirror universe and noticed
> that your mirror is not accessible using a variety of http clients,
> though it does work with firefox.
> 
> e.g.:
> | weasel@orinoco:~$ wget -O - 
> http://mirrors.liquidweb.com/debian/project/trace/
> | --2017-02-16 09:30:51--  http://mirrors.liquidweb.com/debian/project/trace/
> | Resolving mirrors.liquidweb.com (mirrors.liquidweb.com)... 
> 2607:fad0:3500:1::, 69.167.187.144
> | Connecting to mirrors.liquidweb.com 
> (mirrors.liquidweb.com)|2607:fad0:3500:1::|:80... connected.
> | HTTP request sent, awaiting response...  0 
> | 2017-02-16 09:30:51 ERROR 0: (no description).
> | 
> | e8:weasel@orinoco:~$ 
> 
> Please fix.

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

Bug#854941: sync-ui: fails to do anything

[Tino Mettler]

Hi,

the syncevo-dbus-server.service file was missing in the
syncevolution-dbus package. I have a fix ready and will start the
procedure to get it into Stretch in the next few days.

Patrick, are you aware of other changes/additions of this kind in the
1.5.2 release?

Regards,
Tino

Bug#855823: RFP: upspin -- global name space to name all your files

[Michael Stapelberg]

Package: wnpp
Severity: wishlist

* Package name: upspin
  Version : git-snapshot
  Upstream Author : The Upspin Authors
* URL : https://upspin.io/
* License : BSD
  Programming Lang: Go
  Description : global name space to name all your files

Upspin is an experimental project to build a framework for naming and
sharing files and other data securely, uniformly, and globally: a global
name system of sorts.
.
It is not a file system, but a set of protocols and reference
implementations that can be used to join things like file systems and
other storage services to the name space.
.
Performance is not a primary goal. Uniformity and security are.

This package will be maintained within the pkg-go team.

Bug#704303: violates Debian Policy 2.3 Copyright considerations

[Russ Allbery]

"Pirate Praveen"  writes:
> On Sun, 19 Feb 2017 12:43:30 +0530 Pirate Praveen  wrote:
>> On Sun, 1 Jan 2017 16:55:52 +0500 Andrey Rahmatullin  wrote:

>>> Note that since Policy 3.9.9 MPL should be in common-licenses.

>> Reassigning to firefox, which also has the same issue. When is Policy
>> 3.9.9 expected to be released, would it be before stretch release?

> since this will not be an issue after debian-policy 3.9.9 release, can
> this get a stretch-ignore tag?

I'm currently holding off on releasing debian-policy 3.9.9 until the
corresponding base-files change has been uploaded.

(It will probably actually be 3.10.0.)

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

Bug#855805: [libreoffice-common] Texts in Tooltips are not visible

[Rene Engelhard]

On Wed, Feb 22, 2017 at 12:48:38AM +0100, Thomas Florek wrote:
> That bug does not occur on another computer with identical software but
> other graphics hardware:
> VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2).
> Thus the bug might be related to the corresponding Intel graphics driver.

I don't believe tooltip or not is something which would have to do with the
graphics driver, but anyway:

In your initial post you write:

---
VGA compatible controller: Intel Corporation 4th Generation Core
Processor Family Integrated Graphics Controller (rev 06) (prog-if 00
[VGA controller]) 
---

% lspci | grep -i gra
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor 
Integrated Graphics Controller (rev 06)

same for me. And as said, it works here.

Regards,

Rene

Bug#855615: tachyon: not binNMU safe

[Jerome BENOIT]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear James, thanks for your report.
I am looking for reproducing the issue. So far, I cannot.
Where can we get the binMMUed source material ?
Cheers, Jerome

On 20/02/17 23:42, James Cowgill wrote:
> Source: tachyon
> Version: 0.99~b6+dsx-7
> Severity: serious
> 
> Hi,
> 
> tachyon was recently binNMUed on mips* as part of fixing the fallout of
> the binutils symbol table bug (#844227) but unfortunately it is now
> uninstallable on mips.
> 
> Multiple packages are affected, but for example the Depends line of
> libtachyon-mpich-0-dev contains this on mips which is obviously
> unsatisfiable:
> 
> Depends: libtachyon-dev-common (= 0.99~b6+dsx-7), libtachyon-mpich-0 (= 
> 0.99~b6+dsx-7+b1), libtachyon-dev-common (= 0.99~b6+dsx-7+b1)
> 
> This is likely caused by the use of dh_installdocs --link-doc (see
> #747141)
> 
> Thanks,
> James
> 
> 
> 

- -- 
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B
-BEGIN PGP SIGNATURE-

iQQcBAEBCgAGBQJYrTc9AAoJED+SGaZ/NsaL1+UgANMdjPsRAQLaI3aktjExBSxv
+w1xZ+BhxtB1MKCxwbI9Oikr6/BgB3j14mtFldyr9dHEMaHyNuqkRbYCKct7AwGf
l4JfW4AHJ/TZEkxIuWio23wt25DNywfjKrCXRstDfRvvXwH940YYOZR5dwDMHKJM
5ueSaRirSj1Dbrg26b6cAwZ1ZWcT4fgVn8v5xsYDAiKumjIXnvweqDq04PH9nWFs
rNGWbHrhPdV3JtUqrpezbbV1Tfi7e0W0ZPYfgbGY9IkQ32HuHcCL77DlFmyP4chW
O5OnxO3QpjZR/v0dF+NbzvhTBlGT/CBhj+O3t96fJIi11YLtRkd0vUKW1vfvI3Zg
z7Xk+KORk2l9UzEVZh7hsb64JxSis+wqG41T1L6yauY/bplvdQglvv/zgkeByAMl
gVdf9WTKkrnsEiPYKNDRIt5YaKBc8ENHm52ZXy/7c3SY2L2p2G1LdZa58UmzfCHy
xgjGw1qO9c26TKKjZCyBcn25/kEzThcPTDfomo7+l8AZUkn+/TE7din9xhqxqss8
H5TFDkzOdS8H8QG6JtryGy5t9gzv5uxZB8nrD6rJtdd/UfoNNQx2agu3F+1d00ot
nCkrV2JPQoBoXmDBVaIKffUyzqUYJoark9V3XuDPSleG/7YGZ/hH6n6jwohBruFz
JJ88L39GSArOss60661HOamXxIR1slEVSenn6+tfoj+VZ5k4A3gWsb+MVMgYVttu
+YwdH0UOfMhBKdj1ovMn75nOrcsMZGhXgri8tNjA+PODkV4bcGVryNfC9mAuiyzo
sjvz/SjL1WHUmD1YEWjMxvFqFJ8MCFO2+53nWMUZyUiR6Hm90xs7K78rbOC88uzJ
sPHb4zX9+EH0s9MxlQ+M4ahmunpIa07AaTbyphZHaVxRH8gTFiDbzZgNbgGw0UjG
J+Ahp1ZvO8iRVV3/5vKPVpFIKTxZmgIk4mgzbXmqSC3jqogFWrYL5NkxcxeVeNlp
P3m7wjlzk2PsVq4FIMSgVygPuFxz0IH5jQFJyVlU5V+7z4CK08jAbGeE5ipIXP5y
jZPBza+vV7MJV57L88jKjisUShCVkQZojchPs7MdXrI/K+8662Ju5HYwBcqbMRys
hRuqub7jjdZpHyIrqCXS1UTSdudp6uNnWs7T1Sy6IgFC6AZDMTiffOmZmkbp3NJ1
ryC5LJVQtB8laXriePVFsT4rNhOKue6ZiHrF4GdfaIIc8pyolH6kCy83w3tf9p5s
FIx52v6Ao84NTzDXViPxpx9y4XC+OEZHecvwGANB1yAtfKeGubJa+3E1/TJdVVNK
VKqSiaoekNZ5W5k9cJ/JAfLGhS6CNIGCUiRspOh70xF7gSfa9YaIhBh/y6th7wE=
=z8iO
-END PGP SIGNATURE-

Bug#626524: DefaultAddress not obeyed when SocketBindTight is off

[TJ Saunders]

I've tried to clarify the behavior; see:

  http://www.proftpd.org/docs/modules/mod_core.html#SocketBindTight

If you are have:

  SocketBindTight on

And proftpd receives a connection for which there is no 
configured, the client will receive this response

  500 Sorry, no server available to handle request on xxx.xxx.xxx.xxx.

EXCEPT if your proftpd.conf has "DefaultServer on" somewhere.  If
DefaultServer IS used, then that  (or "server config")
section bearing the "DefaultServer on" setting is used to handle that
connection -- that's what the DefaultServer directive is for.

Thus if your "SocketBindTight on" configuration is not causing clients
to receive the "no server available to handle request" when they try to
connect to an unconfigured IP address/port, then it says that your
proftpd.conf is using DefaultServer somewhere.

Cheers,
TJ

Bug#855822: ipmievd.service: exits with failure instead of success when no IPMI device exists

[Paul Wise]

Package: ipmitool
Version: 1.8.14-4
Severity: normal
User: debian-ad...@lists.debian.org
Usertags: needed-by-DSA-Team

On one of the Debian buildd machines, DSA have installed ipmitool for
managing another server over the network using the command-line
utilities. This led to our monitoring flagging the ipmievd service as
failed because the host ipmitool is installed on doesn't have any IPMI
devices of its own. In this situation, ipmievd.service should exit with success 
instead of failure. I've masked the service so this doesn't happen again on 
this host but it would be nice if the daemon would exit with success instead of 
failure when no IPMI devices are present.

pabs@host:~$ systemctl --failed
  UNITLOAD   ACTIVE SUBDESCRIPTION
● ipmievd.service loaded failed failed IPMI event daemon

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB= The low-level unit activation state, values depend on unit type.

1 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
pabs@host:~$ sudo systemctl restart ipmievd.service
Job for ipmievd.service failed. See 'systemctl status ipmievd.service' and 
'journalctl -xn' for details.
pabs@host:~$ sudo systemctl status ipmievd.service
● ipmievd.service - IPMI event daemon
   Loaded: loaded (/lib/systemd/system/ipmievd.service; disabled)
   Active: failed (Result: exit-code) since Wed 2017-02-22 06:12:16 UTC; 4s ago
  Process: 15359 ExecStart=/usr/sbin/ipmievd $IPMIEVD_OPTIONS (code=exited, 
status=1/FAILURE)

Feb 22 06:12:16 host ipmievd[15359]: Could not open device at /dev/ipmi0 or 
/dev/ipmi/0 or /dev/ipmidev/0: No such file or directory
Feb 22 06:12:16 host systemd[1]: ipmievd.service: control process exited, 
code=exited status=1
Feb 22 06:12:16 host systemd[1]: Failed to start IPMI event daemon.
Feb 22 06:12:16 host systemd[1]: Unit ipmievd.service entered failed state.
pabs@host:~$ sudo find /dev/ /sys/ | grep -i ipmi
pabs@host:~$ sudo dmesg | grep -i ipmi

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#855821: libhdcd: Short description of packages libhdcd1 and libhdcd-dev switched

[Beatrice Torracca]

Package: libhdcd
Severity: minor

Hi!

The short package description of packages libhdcd1 and libhdcd-dev
seem to be switched one with the other. In sid libhdcd1 package
description is

libhdcd1: «HDCD decoding and analysis library (development files)»,

while in testing libhdcd-dev description is

libhdcd-dev: «HDCD decoding and analysis library (shared library»

thanks,

beatrice

Bug#704303: violates Debian Policy 2.3 Copyright considerations

[Pirate Praveen]

On Sun, 19 Feb 2017 12:43:30 +0530 Pirate Praveen  wrote:
> On Sun, 1 Jan 2017 16:55:52 +0500 Andrey Rahmatullin 
> wrote:
> > Note that since Policy 3.9.9 MPL should be in common-licenses.
> 
> Reassigning to firefox, which also has the same issue. When is Policy
> 3.9.9 expected to be released, would it be before stretch release?
> 

since this will not be an issue after debian-policy 3.9.9 release, can this get 
a stretch-ignore tag?

Bug#855427: quicktun: Does not work

[James Cloos]

The upstream web site recommended using qt_private_key_file in
interfaces.

Your readme instead recommends qt_private_key.

Switching to qt_private_key helped.

But there is still the problem that only one tunnel can be used at a
time.

It would help were the readme to include mention that in order to run
multiple tunnels each has to specify a differnt port number for the
udp traffic.

I had to strace ifup(8) to notice that.

-JimC
-- 
James Cloos  OpenPGP: 0x997A9F17ED7DAEA6

Bug#855818: linux-image-4.8.0-2-amd64: segfault in intel 9815 drm kernel module

[Luke Kenneth Casson Leighton]

---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68


On Wed, Feb 22, 2017 at 2:38 AM, Ben Hutchings  wrote:
> Control: tag -1 - upstream
> Control: tag -1 moreinfo
>
> On Wed, 2017-02-22 at 01:45 +, lkcl wrote:
>> Package: src:linux
>> Version: 4.8.15-2
>> Severity: normal
>> Tags: upstream
>>
>> not sure what's going on, or why.  reporting as-is fyi.  can't upgrade
>> to 4.9 due to other issues (also reported)
>
> We don't support 4.8 any more; let us know when you're able to test on
> 4.9.

 i would if it was possible, but i can't, ben:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=88

 that's a severity "important".  total boot failure.  segfault running
/init from the initramfs, a DMAR ACPI error accessing the PCIe bus
0xf0:1f.0 which doesn't actually exist.

l.

Bug#855820: RM: azure-cli/0.1.0~b7-1

[Iain R. Learmonth]

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

Hi,

In the opinion of the maintainer (me), this is not fit for release. I intent to
support this in stretch via backports only.

Thanks,
Iain.

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

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

Bug#855819: Remmina : SSH white blanking square after connection establish, but no Cursor

[Jimmy Parr]

Package: remmina
Version: 1.1.2-4
Severity: important

Dear Maintainer,

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


   * What led up to the situation? real situation (every SSH 
connection, get to a square blanking white)

   * What exactly did you do (or not do) that was effective (or
 ineffective)? simple connection SSH that use to work on Jessie
   * What was the outcome of this action?
   * What outcome did you expect instead?

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


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

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

Versions of packages remmina depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.10.14-1
ii  dbus-x11 [dbus-session-bus]   1.10.14-1
ii  libavahi-client3  0.6.32-2
ii  libavahi-common3  0.6.32-2
ii  libavahi-ui-gtk3-00.6.32-2
ii  libc6 2.24-9
ii  libgcrypt20   1.7.6-1
ii  libgdk-pixbuf2.0-02.36.4-1
ii  libglib2.0-0  2.50.2-2
ii  libgtk-3-03.22.7-2
ii  libpango-1.0-01.40.3-3
ii  libssh-4  0.7.3-2
ii  libvte-2.91-0 0.46.1-1
ii  libx11-6  2:1.6.4-3
ii  remmina-common1.1.2-4

Versions of packages remmina recommends:
ii  remmina-plugin-rdp  1.1.2-4
ii  remmina-plugin-vnc  1.1.2-4

remmina suggests no packages.

-- no debconf information




--
Jimmy Parr
Technicien Senior
Conseiller Indépendant

Cellulaire : 418-573-6434


AVIS IMPORTANT : Cette transmission électronique est strictement
réservée à l'usage de la (des) personne(s) à qui elle est adressée
et contient des informations privilégiées et confidentielles. Toute
divulgation, distribution, copie, ou autre utilisation de cette
transmission par une autre personne est strictement prohibée. Si vous
avez reçu ce courriel par erreur, veuillez s'il vous plaît en aviser
immédiatement l'expéditeur par courriel et détruire tout exemplaire
ou copie de la transmission originale.

WARNING: This electronic transmission contains confidential information,
intended only for the person(s) named above, and is privileged. If you
are not the intended recipient, you are hereby notified that any
disclosure, copying, distribution, or any other use of this email is
strictly prohibited. If you have received this transmission by error,
please notify us immediately by return email and destroy the original
transmission immediately and all copies thereof.

Bug#855818: linux-image-4.8.0-2-amd64: segfault in intel 9815 drm kernel module

[Ben Hutchings]

Control: tag -1 - upstream
Control: tag -1 moreinfo

On Wed, 2017-02-22 at 01:45 +, lkcl wrote:
> Package: src:linux
> Version: 4.8.15-2
> Severity: normal
> Tags: upstream
> 
> not sure what's going on, or why.  reporting as-is fyi.  can't upgrade
> to 4.9 due to other issues (also reported)

We don't support 4.8 any more; let us know when you're able to test on
4.9.

[...]
> [ 3390.357523] [ cut here ]
> [ 3390.357596] WARNING: CPU: 1 PID: 6461 at 
> /build/linux-zDY19G/linux-4.8.15/drivers/gpu/drm/i915/intel_display.c:14329 
> skl_max_scale.part.120+0x69/0x70 [i915]
[...]

...is not a segfault.

Finally, you'll need to test without bbswitch and nvidia modules as
it's quite possible that these are part of the problem.

Ben.

-- 
Ben Hutchings
Man invented language to satisfy his deep need to complain. - Lily
Tomlin



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

Bug#855664: RFS: htp/1.19-3 -- nice HTML pre-processor [QA]

[Marcelo S Mota]

Em Tue, 21 Feb 2017 16:06:06 + (UTC)
Gianfranco Costamagna  escreveu:

Hello Gianfranco,

First of all thank you for the quick reply!

> control: owner -1 !
> control: tags -1 moreinfo
> 
> hello Marcelo,
> 
> >  I am looking for a sponsor for my package "htp"  
> 
> 
> sadly we are on freeze, I can sponsor on experimental with two little
> changes: added a newline before your signature on changelog file
> (line 23) changed unstable/experimental

Ok, done!


> I'm worried about the examples:
> debdiff htp_1.19-2_amd64.deb htp_1.19-3_amd64.deb
> 
> or:
> dpkg -c htp_1.19-2_amd64.deb |grep examples |wc -l
> 51
> 
> dpkg -c htp_1.19-3_amd64.deb |grep examples |wc -l
> 34
> 
> 
> seems that a lot of files disappeared from the example directory
> (e.g. examples/tests)
> 
> is this something intended or not? In case please document it in
> changelog file
> 
> G.

It was intended indeed because upstream's tests generate duplicated
files (all *.exp under tests/ exists for comparison against
respective runtime generated *.html along with licenses files and others).
It launches a bunch of lintians (including experimental ("X:") -
i was trying to avoid that (with DH_ALWAYS_EXCLUDE at debian/rules).

There is also a privacy-breach-generic that i tried to address with a patch.

I reverted all of that, fixed the changelog and uploaded it again to
mentors - it's my first work on Debian at all so i shall keep it simple,
don't i? ;-)


Regards,
   Marcelo S Mota

Bug#336001: proftpd: improving documentation

[TJ Saunders]

Done; see:

  http://www.proftpd.org/docs/modules/mod_core.html#MaxInstances

Cheers,
TJ

Bug#855818: linux-image-4.8.0-2-amd64: segfault in intel 9815 drm kernel module

[lkcl]

Package: src:linux
Version: 4.8.15-2
Severity: normal
Tags: upstream

not sure what's going on, or why.  reporting as-is fyi.  can't upgrade
to 4.9 due to other issues (also reported)



-- Package-specific info:
** Version:
Linux version 4.8.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 5.4.1 
20161202 (Debian 5.4.1-4) ) #1 SMP Debian 4.8.15-2 (2017-01-04)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.8.0-2-amd64 root=/dev/mapper/pc-root ro quiet 
rcutree.rcu_idle_gp_delay=1 iommu=debug apic_verbosity=debug loglvl=all

** Tainted: PWOE (12801)
 * Proprietary module has been loaded.
 * Taint on warning.
 * Out-of-tree module has been loaded.
 * Unsigned module has been loaded.

** Kernel log:
[  981.350904] Restarting tasks ... done.
[  981.435459] bbswitch: disabling discrete graphics
[  981.435476] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20160422/nsarguments-95)
[  981.633479] iwlwifi :04:00.0: L1 Enabled - LTR Enabled
[  981.634115] iwlwifi :04:00.0: L1 Enabled - LTR Enabled
[  981.761118] iwlwifi :04:00.0: L1 Enabled - LTR Enabled
[  981.761416] iwlwifi :04:00.0: L1 Enabled - LTR Enabled
[  981.846277] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  981.921709] [drm] RC6 on
[  982.193431] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[  992.953325] iwlwifi :04:00.0: L1 Enabled - LTR Enabled
[  992.953961] iwlwifi :04:00.0: L1 Enabled - LTR Enabled
[  993.081292] iwlwifi :04:00.0: L1 Enabled - LTR Enabled
[  993.081574] iwlwifi :04:00.0: L1 Enabled - LTR Enabled
[  993.167691] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1021.945790] iwlwifi :04:00.0: L1 Enabled - LTR Enabled
[ 1021.946445] iwlwifi :04:00.0: L1 Enabled - LTR Enabled
[ 1022.073780] iwlwifi :04:00.0: L1 Enabled - LTR Enabled
[ 1022.074060] iwlwifi :04:00.0: L1 Enabled - LTR Enabled
[ 1022.160881] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1022.366484] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1022.604447] iwlwifi :04:00.0: L1 Enabled - LTR Enabled
[ 1022.605120] iwlwifi :04:00.0: L1 Enabled - LTR Enabled
[ 1022.732223] iwlwifi :04:00.0: L1 Enabled - LTR Enabled
[ 1022.732527] iwlwifi :04:00.0: L1 Enabled - LTR Enabled
[ 1022.819186] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1025.132299] wlan0: authenticate with 78:44:76:ff:84:74
[ 1025.140532] wlan0: send auth to 78:44:76:ff:84:74 (try 1/3)
[ 1025.146497] wlan0: authenticated
[ 1025.146533] iwlwifi :04:00.0 wlan0: disabling HT/VHT due to WEP/TKIP use
[ 1025.148969] wlan0: associate with 78:44:76:ff:84:74 (try 1/3)
[ 1025.152953] wlan0: RX AssocResp from 78:44:76:ff:84:74 (capab=0xc11 status=0 
aid=1)
[ 1025.154978] wlan0: associated
[ 1025.155046] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 1025.754552] iwlwifi :04:00.0: No association and the time event is over 
already...
[ 1025.754587] wlan0: Connection to AP 78:44:76:ff:84:74 lost
[ 1032.725321] wlan0: authenticate with 78:44:76:ff:84:74
[ 1032.732659] wlan0: send auth to 78:44:76:ff:84:74 (try 1/3)
[ 1032.735833] wlan0: authenticated
[ 1032.735864] iwlwifi :04:00.0 wlan0: disabling HT/VHT due to WEP/TKIP use
[ 1032.737612] wlan0: associate with 78:44:76:ff:84:74 (try 1/3)
[ 1032.744154] wlan0: RX AssocResp from 78:44:76:ff:84:74 (capab=0xc11 status=0 
aid=1)
[ 1032.757907] wlan0: associated
[ 1041.794719] wlan0: authenticate with 78:44:76:ff:84:74
[ 1041.802188] wlan0: send auth to 78:44:76:ff:84:74 (try 1/3)
[ 1041.804804] wlan0: authenticated
[ 1041.804836] iwlwifi :04:00.0 wlan0: disabling HT/VHT due to WEP/TKIP use
[ 1041.806316] wlan0: associate with 78:44:76:ff:84:74 (try 1/3)
[ 1041.811573] wlan0: RX AssocResp from 78:44:76:ff:84:74 (capab=0xc11 status=0 
aid=1)
[ 1041.815475] wlan0: associated
[ 1131.573551] usb 1-2: new low-speed USB device number 5 using xhci_hcd
[ 1131.721114] usb 1-2: New USB device found, idVendor=0f62, idProduct=1001
[ 1131.721119] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1131.721122] usb 1-2: Product: USB & PS/2 Mouse
[ 1131.721124] usb 1-2: Manufacturer: Acrox
[ 1131.725862] input: Acrox USB & PS/2 Mouse as 
/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:0F62:1001.0004/input/input24
[ 1131.726482] hid-generic 0003:0F62:1001.0004: input,hidraw3: USB HID v1.10 
Mouse [Acrox USB & PS/2 Mouse] on usb-:00:14.0-2/input0
[ 1349.883538] usb usb3: root hub lost power or was reset
[ 1349.883541] usb usb4: root hub lost power or was reset
[ 3390.357523] [ cut here ]
[ 3390.357596] WARNING: CPU: 1 PID: 6461 at 
/build/linux-zDY19G/linux-4.8.15/drivers/gpu/drm/i915/intel_display.c:14329 
skl_max_scale.part.120+0x69/0x70 [i915]
[ 3390.357598] WARN_ON_ONCE(!crtc_clock || cdclk < crtc_clock)
[ 3390.357600] Modules linked in:
[ 3390.357602]  iwlmvm snd_hda_intel iwlwifi bbswitch(OE) rfcomm 
cpufreq_conservative cpufreq_userspace 

Bug#854821: Reverting 29be63fd restores the old behavior

[Nish Aravamudan]

On 14.02.2017 [20:30:52 +0100], Aurelien Jarno wrote:
> On 2017-02-10 11:50, Nish Aravamudan wrote:
> > Just ran a quick test using a PPA build of glibc with 29be63fd
> > ("debian/patches/localedata/locale-C.diff: switch back transliterations
> > to combining. Closes: #840199" [0] reverted and the test passes in a
> > 17.04 (Zesty) container again.
> 
> This change is intentional, and was done to revert an unintentional
> change (see #840199). Now the behaviour is consistent between jessie
> and stretch/sid.

I understand that, the above revert was mostly informational. Reading
the other bug, I see the reasoning behind not changing behavior. But it
seems like this also changes behavior, even if only within Unstable, and
needs some follow-up as phpmyadmin in Unstable will fail to rebuild
(verified just now in the chroot).

Given that this appears in an upstream test that is making an assumption
about \\TRANSLIT support from iconv (meaning that the behavior they are
testing for might be consistent across distributions), I'm not sure what
the best next step would be. Note that the phpmyadmin tests were only
relatively recently enabled at build-time, so that may be why this
wasn't noticed.

Any advice would be greatly appreciated!

Thanks,
Nish

-- 
Nishanth Aravamudan
Ubuntu Server
Canonical Ltd

Bug#855703: xen-create-image: doesn't create random MAC addresses

[Axel Beckert]

Hi Ian,

thanks for your comments.

Ian Jackson wrote:
> Pietro Staeheli writes ("Bug#855703: xen-create-image: doesn't create random 
> MAC addresses"):
> > xen-create-image derives its generated MAC addresses from the
> > hostname, IP address configuration and distribution of the domU to
> > be installed (see: sub generateMACAddress). This behavior leads to a
> > MAC address collisions when multiple domU's with the same
> > configuration and hostname are created on the same network on
> > different dom0's.
[…]
> I think what you are doing is a bit odd.  I would almost expect the
> two identically named VMs to be failover for each other or something.
> (If they share a hostname, do they share IPv6 and IPv4 addresses?)
> Anyway, I'll assume you have a good reason...

This was already discussed upstream on the mailing list at
http://xen-tools.org/pipermail/xen-tools-discuss/2017-February/thread.html
and I asked Pietro to file a proper bug report for it, but forgot to
mention that I meant an upstream bug report.

My plan is to make the default generated MAC address no more dependent
on the distribution (see
https://github.com/xen-tools/xen-tools/issues/33) but to also offer to
allow more control over how random the MAC address will be, i.e. allow
to set a different OUI (see
https://github.com/xen-tools/xen-tools/issues/34) as well as totally
random NIC part as requested by Pietro. (The latter won't become
default, though.)

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://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#855817: Please hide automatic debug packages from NEW overview pages

[James Clarke]

Package: ftp.debian.org
Severity: wishlist
Tags: patch
User: ftp.debian@packages.debian.org
Usertags: dak

Hi,
Currently, the NEW package overview pages include all the automatic
debug packages, which makes it very noisy. Please consider the attached
untested patch, which should (hopefully) hide these packages when they
are not considered NEW.

Regards,
James
>From db48e4d24d5a1793579e02d1964e5a5306bae946 Mon Sep 17 00:00:00 2001
From: James Clarke 
Date: Wed, 22 Feb 2017 00:57:53 +
Subject: [PATCH] Hide automatic debug packages from overview page

---
 dak/show_new.py  |  2 +-
 daklib/policy.py | 17 +
 2 files changed, 14 insertions(+), 5 deletions(-)

diff --git a/dak/show_new.py b/dak/show_new.py
index af1b8a648..f3dd6f8ef 100755
--- a/dak/show_new.py
+++ b/dak/show_new.py
@@ -175,7 +175,7 @@ def do_pkg(upload_id):
 with open(htmlfile, 'w') as outfile:
   with policy.UploadCopy(upload, group=group) as upload_copy:
 handler = policy.PolicyQueueUploadHandler(upload, session)
-missing = [ (o['type'], o['package']) for o in 
handler.missing_overrides() ]
+missing = [ (o['type'], o['package']) for o in 
handler.missing_overrides(hide_debug=True) ]
 distribution = changes.distribution
 
 print >>outfile, html_header(changes.source, missing)
diff --git a/daklib/policy.py b/daklib/policy.py
index aa5f12f0a..77dde2c52 100644
--- a/daklib/policy.py
+++ b/daklib/policy.py
@@ -222,13 +222,16 @@ class PolicyQueueUploadHandler(object):
 
 return None
 
-def missing_overrides(self, hints=None):
+def missing_overrides(self, hints=None, hide_debug=False):
 """get missing override entries for the upload
 
 @type  hints: list of dict
 @param hints: suggested hints for new overrides in the same format as
   the return value
 
+@type  hide_debug: bool
+@param hide_debug: don't include automatic debug packages
+
 @return: list of dicts with the following keys:
 
  - package: package name
@@ -244,15 +247,20 @@ class PolicyQueueUploadHandler(object):
 components = set()
 
 source = self.upload.source
+suite = self._overridesuite
 
 if hints is None:
 hints = []
 hints_map = dict([ ((o['type'], o['package']), o) for o in hints ])
 
-def check_override(name, type, priority, section, included):
+def check_override(name, type, priority, section, included, autobuilt):
 component = 'main'
 if section.find('/') != -1:
 component = section.split('/', 1)[0]
+if hide_debug:
+control = {'Section': section, 'Auto-Built-Package': autobuilt}
+if utils.is_in_debug_section(control) and suite.debug_suite is 
not None:
+return
 override = self._binary_override(name, type, component)
 if override is None and not any(o['package'] == name and o['type'] 
== type for o in missing):
 hint = hints_map.get((type, name))
@@ -274,7 +282,8 @@ class PolicyQueueUploadHandler(object):
 binary_proxy = binary.proxy
 priority = binary_proxy['Priority']
 section = binary_proxy['Section']
-check_override(binary.package, binary.binarytype, priority, 
section, included=True)
+autobuilt = binary_proxy['Auto-Built-Package']
+check_override(binary.package, binary.binarytype, priority, 
section, included=True, autobuilt=autobuilt)
 
 if source is not None:
 source_proxy = source.proxy
@@ -282,7 +291,7 @@ class PolicyQueueUploadHandler(object):
 if not package_list.fallback:
 packages = 
package_list.packages_for_suite(self.upload.target_suite)
 for p in packages:
-check_override(p.name, p.type, p.priority, p.section, 
included=False)
+check_override(p.name, p.type, p.priority, p.section, 
included=False, autobuilt=None)
 
 # see daklib.archive.source_component_from_package_list
 # which we cannot use here as we might not have a Package-List
-- 
2.11.1

Bug#807427: sane-utils: Can not provide access to hplip scanner over network

[Vladimir K]

Any news on this? localOnly check is still active in current testing.

Bug#825727: python-babel: FTBFS: assert 'GMT+00:00' == 'GMT-01:59'

[Santiago Vila]

On Mon, 12 Dec 2016, Chris Lamb wrote:

> Santiago Vila wrote:
> 
> > I guess this makes the bug not to be RC after all, not because
> > it simply "does not usually happen" in the official autobuilders
> 
> Not sure I agree with that logic, but that's a debate for elsewhere
> and another time. :)

Note: I do not agree with such logic either :-). That was really not
an endorsement of the (wrong) rule saying "if it does not happen on
buildd.debian.org, it's not RC".

Instead, it is just an acknowledgement of the fact that if we
build packages with TZ=Etc/UTC, as it happens in buildd.debian.org,
then the build failure will never happen.

In other words, I consider Etc/UTC to be part of the "standard to
build Debian packages".

> However, more important is the question is: Does the fact that
> python-babel FTBFS in such conditions imply that it is broken at
> runtime for our users running under such timezones?

Yes. That's a very good point indeed!

So: Only in case the test failure does not mean that the program will
not work properly for the users in such timezone, as explained by
Chris:

Does the proposed patch look good enough to be applied, so that we can
finally fix this bug?

Thanks.

Bug#855816: unblock: mypaint/1.2.0-4

[Andrew Chadwick]

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

Please unblock package mypaint.

MyPaint 1.2.0-4, currently in unstable for 17 days, contains a targetted fix
for bug 848356. This bug has been assigned a severity of important becuase it
largely makes MyPaint useless in fullscreen mode with the version of
libgtk-3-0 which is due to be relesed with stretch.

Fullscreen mode is a primary way of using this package, and fullscreen state
is remembered across restarts of the app.

Debian bug being targetted:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848356

This patch originates from upstream:
https://github.com/mypaint/mypaint/commit/c225d1132a7da956a35a32534e91a42d22cdb8e1

This bug is fixed in the latest upstream release (1.2.1),i which will not be
part of stretch, but I've backported and tested this fix for Stretch's 1.2.0.

Upstream bug reference:
https://github.com/mypaint/mypaint/issues/735

There are no unrelated changes in unstable, or included in this unblock.
Please cross-check it with the upstream patch to verify that it is the same
code. This is my first unblock request, so I hope I've mentioned the right
version in the subject and below.

Debdiff follows, as requested.

--8<
diff -Nru mypaint-1.2.0/debian/changelog mypaint-1.2.0/debian/changelog
--- mypaint-1.2.0/debian/changelog  2016-11-22 08:02:02.0 +
+++ mypaint-1.2.0/debian/changelog  2017-02-02 14:39:42.0 +
@@ -1,3 +1,10 @@
+mypaint (1.2.0-4) unstable; urgency=medium
+
+  * Add debian/patches/fix-gtk-3.22.4-canvas-disappearance.patch to fix
+fullscreen mode. (Closes: #848356)
+
+ -- Andrew Chadwick   Thu, 02 Feb 2017 14:39:42 +
+
 mypaint (1.2.0-3) unstable; urgency=medium
 
   * Update d/rules to use dh sequencer. Fixes arch-indep FTBFS.
diff -Nru 
mypaint-1.2.0/debian/patches/fix-gtk-3.22.4-canvas-disappearance.patch 
mypaint-1.2.0/debian/patches/fix-gtk-3.22.4-canvas-disappearance.patch
--- mypaint-1.2.0/debian/patches/fix-gtk-3.22.4-canvas-disappearance.patch  
1970-01-01 01:00:00.0 +0100
+++ mypaint-1.2.0/debian/patches/fix-gtk-3.22.4-canvas-disappearance.patch  
2017-02-02 13:06:12.0 +
@@ -0,0 +1,63 @@
+diff --git a/gui/workspace.py b/gui/workspace.py
+index 7f4f4abe..2af856a5 100644
+--- a/gui/workspace.py
 b/gui/workspace.py
+@@ -223,6 +223,7 @@ class Workspace (Gtk.VBox, Gtk.Buildable):
+ lpaned.pack1(lscrolls, resize=False, shrink=False)
+ lpaned.pack2(rpaned, resize=True, shrink=False)
+ rpaned.pack2(rscrolls, resize=False, shrink=False)
++rpaned.pack1(cscrolls, resize=True, shrink=False)
+ self.pack_start(lpaned, True, True, 0)
+ # Autohide
+ self._autohide_enabled = True
+@@ -397,43 +398,21 @@ class Workspace (Gtk.VBox, Gtk.Buildable):
+ def set_canvas(self, widget):
+ """Canvas widget (setter)"""
+ assert self.get_canvas() is None
+-self._rpaned.pack1(widget, resize=True, shrink=False)
+-self._update_canvas_scrolledwindow()
++widget = self._canvas_scrolls.add(widget)
+
+ def get_canvas(self):
+ """Canvas widget (getter)"""
+-widget = self._rpaned.get_child1()
+-if widget is self._canvas_scrolls:
+-widget = widget.get_child()
++widget = self._canvas_scrolls.get_child()
+ return widget
+
+ def _update_canvas_scrolledwindow(self):
+-"""Update whether the canvas has a surrounding ScrolledWindow
+-
+-In fullscreen mode, the ScrolledWindow is removed from the widget
+-hierarchy so that the canvas widget can occupy the full size of the
+-screen. In nonfullscreen mode, the scrollers provide a pretty frame.
+-"""
+-canvas = self.get_canvas()
+-parent = canvas.get_parent()
++"""Update the canvas ScrolledWindow's border."""
++parent = self._canvas_scrolls
+ if not self._is_fullscreen:
+-if parent is self._canvas_scrolls:
+-return
+-logger.debug("Adding GtkScrolledWindow around canvas")
+-assert parent is self._rpaned
+-self._rpaned.remove(canvas)
+-self._rpaned.pack1(self._canvas_scrolls, resize=True, 
shrink=False)
+-self._canvas_scrolls.add(canvas)
+-self._canvas_scrolls.show_all()
++parent.set_shadow_type(Gtk.ShadowType.NONE)
+ else:
+-if parent is self._rpaned:
+-return
+-logger.debug("Removing GtkScrolledWindow around canvas")
+-assert parent is self._canvas_scrolls
+-self._canvas_scrolls.remove(canvas)
+-self._rpaned.remove(self._canvas_scrolls)
+-self._rpaned.pack1(canvas, resize=True, shrink=False)
+-self._canvas_scrolls.hide()
++

Bug#855815: unblock: glabels/3.4.0-2

[Jakob Haufe]

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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please unblock package glabels

The new package builds correctly on all release architectures:
https://buildd.debian.org/status/package.php?p=glabels=unstable

This upload fixes a segmentation fault bug in the batch processing
component of glabels which rendered that part of the package unusable on
64 bit architectures.

The fix is cherry-picked from upstream and very simple.

debian bug numbers: #855604 (severity normal)

source debdiff:

diff -Nru glabels-3.4.0/debian/changelog glabels-3.4.0/debian/changelog
- --- glabels-3.4.0/debian/changelog2016-12-29 21:30:59.0 +0100
+++ glabels-3.4.0/debian/changelog  2017-02-20 23:52:38.0 +0100
@@ -1,3 +1,11 @@
+glabels (3.4.0-2) unstable; urgency=medium
+
+  * Cherry-pick from upstream:
+add-missing-prototype (Closes: #855604)
+Thanks to Keith Packard for reporting this
+
+ -- Jakob Haufe   Mon, 20 Feb 2017 23:52:38 +0100
+
 glabels (3.4.0-1) unstable; urgency=medium
 
   * New upstream version
diff -Nru glabels-3.4.0/debian/patches/add-missing-prototype 
glabels-3.4.0/debian/patches/add-missing-prototype
- --- glabels-3.4.0/debian/patches/add-missing-prototype1970-01-01 
01:00:00.0 +0100
+++ glabels-3.4.0/debian/patches/add-missing-prototype  2017-02-20 
23:01:56.0 +0100
@@ -0,0 +1,17 @@
+From: Jim Evins 
+Subject: Added missing function prototype to header.
+Origin: upstream, 
https://github.com/jimevins/glabels/commit/01c80fc941cf5c8bf0d2b64a6a58cc3b5138f932
+Bug-Debian: http://bugs.debian.org/855604
+
+diff --git a/src/prefs-model.h b/src/prefs-model.h
+index 72efa84..10316a1 100644
+--- a/src/prefs-model.h
 b/src/prefs-model.h
+@@ -59,6 +59,7 @@ GType  gl_prefs_model_get_type  
(void) G_GNUC_CONST;
+ 
+ glPrefsModel  *gl_prefs_model_new   (void);
+ 
++glPrefsModel  *gl_prefs_model_new_null  (void);
+ 
+ void   gl_prefs_model_set_units (glPrefsModel 
*this,
+  lglUnits 
 units);
diff -Nru glabels-3.4.0/debian/patches/series 
glabels-3.4.0/debian/patches/series
- --- glabels-3.4.0/debian/patches/series   2016-12-15 21:00:44.0 
+0100
+++ glabels-3.4.0/debian/patches/series 2017-02-20 22:48:47.0 +0100
@@ -1,3 +1,4 @@
 0002-manpage.patch
 0003-Ignore-license.page.patch
 gnome-common-cleanup
+add-missing-prototype
(include/attach the debdiff against the package in testing)


unblock glabels/3.4.0-2

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

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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEe/X2rDZDH11A3BN6TPKyGPVNrj0FAlis1yAACgkQTPKyGPVN
rj3VaBAAhKNOhnnSPZrP2+OMmUWtwwI/6/aEt+rxvhTK4K0ojkTjJDvtyU4O1EP+
KJxQg8UPUeJ0J8n4no5o8ZxeD9o2mQxmo8CgHXhv5vLBIu9ljIEqJ19VibdSlLe4
tt4c1WQJVZzZwHFKJ6+qY2JEwxBzzwS38v5yUAwcPfjUflRGbeeqb3N1UfjTZH6/
BRgfrb5w2aiwYu3P3RB23H9nZoahqJtOxcTOemieERrEbc2TCnbXdDv80aO+TaLU
DG5ZHO+N9jtAaqv2sbwrBZP7BqpDLbI+9hdKJ89JEoPw8BFrSQFpOx/wu5fMrwi7
ZN402Wlo2V/+jbGp+KQ8sz8Foa9Ic5zrX2WkLCNMf7evtHOZ//+zSBfjrKIwzc/T
5sZSDpY1Mao04KE22b58+M9trKK7DQbd9L1iRn1U8hqfjhAuV0lAdIVPfqCxGHXt
Xdzr9vwImb+7wYqQXvPhRfFGrJ8Fz0vg+FgYxztxXxg11PR7v1A1YhpAYXkxmBdi
Z1YKmKYUv3s/LpGsa+1SfhRHfRR1wqQnXgii7skv5PyQMkzRna4nNWCYhPSifB/C
JEIDdcscxp0yBtgS3F2tSzU4ISmnd3B7OirSHt59EKobgQovpDrPUuYR5gW0dCgL
A+2ehHIAf8w/arlM0tPWGFkPBsw+tIIhgLiwrSzIEqB0wOaxdCI=
=ufe6
-END PGP SIGNATURE-

Bug#849357:

[Santiago José López Borrazás]

On Mon, 20 Feb 2017 17:13:39 -0800 VDR User  wrote:
> Kernel 4.10 is the current stable kernel now and this still hasn't
> been fixed. Has there been any acknowledgement of the bug from the
> maintainer yet?

Egalite. The problem is ONLY on the lines affect on the file headers.mk.

Check of file /usr/share/kernel-package/ruleset/targets/headers.mk on (and
modified lines):

-   $(install_file) REPORTING-BUGS  $(DOCDIR)/
+   test ! -f REPORTING-BUGS|| \
+  $(install_file) REPORTING-BUGS$(DOCDIR)/

IN this moment is probe and COMPROBATION is correct.

Thank's.

-- 
Saludos de Santiago José López Borrazás.
Greetins of Santiago José López Borrazás.




signature.asc
Description: OpenPGP digital signature

Bug#855805: [libreoffice-common] Texts in Tooltips are not visible

[Thomas Florek]

That bug does not occur on another computer with identical software but
other graphics hardware:
VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2).
Thus the bug might be related to the corresponding Intel graphics driver.

Bug#827061: transition: openssl

[Emilio Pozuelo Monfort]

On 22/02/17 00:28, Sebastian Andrzej Siewior wrote:
> On 2017-01-28 19:37:09 [+0100], Julien Cristau wrote:
>> At this point, it seems clear to me that we're getting nowhere fast.
>> With the freeze looming in a few days, this is growing to be a very big
>> risk for the stretch release.
> 
> Where do we stand on the openssl transition from the perspective of
> people who think it is not done yet?
> 
> The transition tracker for 1.0 shows three packages red. They depend on
> "libssl-dev | libssl1.0-dev" and it builds against 1.1. Do want them to
> decide properly?

I think that's alright.

> The transition tracker for 1.1 shows 11 packages. Except for pyrit all
> are out of testing and have more than just one RC bug which is not
> relevant to the transition. And pyrit just didn't make it on i386.

Hopefully it gets fixed, but otherwise it's not a key package so it will
eventually get dropped from testing.

> There are 78 packages in the unkown state. The first few I looked could
> actually have their libssl-dev dependency dropped. khtml is the first
> one which looked wrong. I will open a bug about that later. I didn't get
> any further yet.

Thanks. Investigating the rest would be good. I guess most of those are just for
build-depends, but if there are any with bad depends (e.g. some -dev package
unnecessarily depending on libssl*-dev) it'd be good to fix that for stretch,
because of the conflicting libssl dev packages.

Sounds like things are under control now. The concern of -dev packages not being
co-installable is a valid one, but I guess we'll have to live with that.

Thanks,
Emilio

Bug#827061: transition: openssl

[Sebastian Andrzej Siewior]

On 2017-01-28 19:37:09 [+0100], Julien Cristau wrote:
> At this point, it seems clear to me that we're getting nowhere fast.
> With the freeze looming in a few days, this is growing to be a very big
> risk for the stretch release.

Where do we stand on the openssl transition from the perspective of
people who think it is not done yet?

The transition tracker for 1.0 shows three packages red. They depend on
"libssl-dev | libssl1.0-dev" and it builds against 1.1. Do want them to
decide properly?

The transition tracker for 1.1 shows 11 packages. Except for pyrit all
are out of testing and have more than just one RC bug which is not
relevant to the transition. And pyrit just didn't make it on i386.

There are 78 packages in the unkown state. The first few I looked could
actually have their libssl-dev dependency dropped. khtml is the first
one which looked wrong. I will open a bug about that later. I didn't get
any further yet.

> Cheers,
> Julien

Sebastian

Bug#850506: Unreproducible FTBFS of acorn

[Santiago Vila]

Hi.

I don't know anything about Javascript (sorry), but I'd like to suggest a
general way to deal with this, which is not language-specific:

Instead of trying to reproduce the bug yourself (by trying many times),
look at the build logs and look at the code, and try to guess how it
could happen:

Error: missing module import from src/bin/acorn.js for path: acorn
at Container.getModule
(/usr/lib/nodejs/es6-module-transpiler/lib/container.js:94:9)
at Module.getModule
(/usr/lib/nodejs/es6-module-transpiler/lib/module.js:189:25)
at ImportDeclaration.
(/usr/lib/nodejs/es6-module-transpiler/lib/module_binding_declaration.js:106:40)
at ImportDeclaration.Object.defineProperty.get
(/usr/lib/nodejs/es6-module-transpiler/lib/utils.js:15:31)
at CommonJSFormatter.importedReference
(/usr/lib/nodejs/es6-module-transpiler/lib/formatters/commonjs_formatter.js:319:46)
at Context.Rewriter.getExportReferenceForReference
(/usr/lib/nodejs/es6-module-transpiler/lib/rewriter.js:363:20)
at Context.Rewriter.visitIdentifier
(/usr/lib/nodejs/es6-module-transpiler/lib/rewriter.js:106:32)
at Context.invokeVisitorMethod
(/usr/lib/nodejs/ast-types/lib/path-visitor.js:344:49)
at Rewriter.PVp.visitWithoutReset
(/usr/lib/nodejs/ast-types/lib/path-visitor.js:196:32)
at visitChildren
(/usr/lib/nodejs/ast-types/lib/path-visitor.js:246:25)


For example: Is it true that the above functions call the other
functions in cascade and the first one (or the last one) tries to load
a module which is missing? How could that happen? That sort of thing.

If you can guess how it may happen by looking at the code and the
build log, you would not even need to reproduce it, but of course this
would be all Knuth style:

"Beware of bugs in the above code; I have only proved it correct, not tried it"

In this case, if you try to prove that the code is correct, you should
surely fail, because we get those build failures which seem to
indicate that it's not.

And if this does not help you in any way, well, I'm really sorry.
I would try to forward the bug upstream anyway. The bug seems real,
as it happens on completely different environments (my autobuilders,
using sbuild, and the ones from reproducible builds, using pbuilder).

Thanks.

Bug#794856: fixed in opencv 3.0.0+dfsg-1~exp1

[Nobuhiro Iwamatsu]

Hi!

Thanks for your work!
You do not need delayed upload. Please go ahead.

Best regards,
  Nobuhiro

2017-02-20 7:31 GMT+09:00 Jochen Sprickerhof :
> Hi Nobuhiro,
>
> I've pushed a new OpenCV version excluding the Lenna images to delayed/5
> and the vcs. Please tell me, if I should delay it further.
>
> I will take care of the unblock request once it's true, as well.
>
> Cheers Jochen



-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6

Bug#855812: borgbackup: missing fuse dependency

[Gianfranco Costamagna]

control: tags -1 patch pending

thanks, uploaded in experimental due to the freeze

G.





Il Martedì 21 Febbraio 2017 23:09, Magnus Nord  ha scritto:
Package: borgbackup
Version: 1.0.9-1~bpo8+1
Severity: minor

Dear Maintainer,

The "borg umount" command does not work, giving the error:
FileNotFoundError: [Errno 2] No such file or directory: 'fusermount'

Installing the fuse package fixes this, so one solution for this
is adding the fuse package as a dependency.


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

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

Versions of packages borgbackup depends on:
ii  libacl12.2.52-2
ii  libc6  2.19-18+deb8u7
ii  liblz4-1   0.0~r122-2
ii  libssl1.0.01.0.1t-1+deb8u6
ii  python33.4.2-2
ii  python3-llfuse 0.40-2+b2
ii  python3-msgpack0.4.6-1~bpo8+1
ii  python3-pkg-resources  5.5.1-1

borgbackup recommends no packages.

Versions of packages borgbackup suggests:
pn  borgbackup-doc  

-- no debconf information

Bug#760414: [ola] Source package includes non-source files without corresponding source

[Wouter Verhelst]

Hi Ben,

Sorry for the late reply; I've been fighting a viral infection for the past
week+

On Wed, Feb 15, 2017 at 12:21:53AM +1100, Ben Finney wrote:
> Control: reassign -1 src:ola
> Control: retitle -1 ola: Source package includes non-source files without 
> corresponding source
> 
> On 14-Feb-2017, Wouter Verhelst wrote:
> > If the FTP team explains to me why that is a DFSG violation, I'll
> > add the "missing" files. If they don't, things will remain as they
> > are (and if they don't but do change severities, I'll ask the TC to
> > rule).
> 
> This surprises me. Do you mean to imply that only the FTP Master team
> can bring reasoned argument to convince you?

At this point in the release, yes.

> That you would reject such reasons if they came from different people?

I would not reject them if they were well presented.

> I ask because I am confident you're amenable to rational discussion
> about bugs, regardless of who presents those reasons. I hope that's
> right.

That's certainly right.

-- 
< ron> I mean, the main *practical* problem with C++, is there's like a dozen
   people in the world who think they really understand all of its rules,
   and pretty much all of them are just lying to themselves too.
 -- #debian-devel, OFTC, 2016-02-12

Bug#855656: release-notes: update on mysql/mariadb for stretch

[Vincent McIntyre]

On Tue, Feb 21, 2017 at 09:56:44AM +0100, Baptiste Jammet wrote:
> Hello,
> 
> Le 21/02/2017 01:09, Vincent McIntyre a écrit :
> 
> >this is a start on the notes needed regarding mysql/mariadb.
> >[...]
> >Comments welcome.
> Thanks for the patch. Here are some comments:
> 
> >   
> > MySQLMySQL
> > 5.5
> >-5.6
> >+-
> Maybe we could remove the entire line instead.
> Or mark the second column with removed.
> 

Sure, removed seens fine to me.

> >+ Installing the metapackage XX will pull in YY
> s/will pull in/will install/ ?
> 
> >+The virtual-mysql-* packages
> >+will continue to exist.
> I don't find any package named like this. Could you explain, please ?

This was taken from an email thread of the mysql packagers and it
was not all that clear to me either. I found an explanation here
   https://wiki.debian.org/Teams/MySQL/virtual-mysql-server

Since this seems to be something that only matters to packagers
of mysql-related software, perhaps the sentence should be dropped?

> 
> >+See the http://wiki.debian.org/Teams/MySQL;>Debian MySQL
> >Team
> >+wiki page
> s/http/https/
> 
> >+software availble in Debian.
> typo : available
> 

Agree on these

-- 

Bug#855814: unblock: graphite2/1.3.9-4

[Rene Engelhard]

Hi,

On Tue, Feb 21, 2017 at 11:25:34PM +0100, Rene Engelhard wrote:
> diff -Nru graphite2-1.3.9/debian/libgraphite2-3-dbg.substvars 
> graphite2-1.3.9/debian/libgraphite2-3-dbg.substvars
> --- graphite2-1.3.9/debian/libgraphite2-3-dbg.substvars 2016-11-17 
> 13:54:13.0 +0100
> +++ graphite2-1.3.9/debian/libgraphite2-3-dbg.substvars 1970-01-01 
> 01:00:00.0 +0100
> @@ -1,2 +0,0 @@
> -misc:Depends=
> -misc:Pre-Depends=

Noticed I missed this in the mail and changelog. But this was apparently
a accidentially committed generated substvars file. And graphite2 is already
at the new -dbgsym world anyway.

Regards,

Rene

Bug#855814: unblock: graphite2/1.3.9-4

[Rene Engelhard]

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

Please unblock package graphite2

1.3.9-1 FTBFSed on *i386 with the tests failing[1]. Discussion with upstream at
that time resulted in disabling the tests (see the log in the patch file
removed below). That happened in 1.3.9-2.

Yesterday I got approached by upstream pointing me to 
https://github.com/silnrsi/graphite/commit/f7bbdd87d510d587c872e314d6458160c0069c65
(the first part) which was supposed to fix this.

It did.[2]

Your mileage may vary, but I think it's worthwile and better to have the tests
ran and do the necessary adaptions than keep them disabled. Though I of course
don't believe they'll break during stretchs cycle...

Debdiff:

diff -Nru graphite2-1.3.9/debian/changelog graphite2-1.3.9/debian/changelog
--- graphite2-1.3.9/debian/changelog2017-01-11 21:33:49.0 +0100
+++ graphite2-1.3.9/debian/changelog2017-02-21 12:02:23.0 +0100
@@ -1,3 +1,9 @@
+graphite2 (1.3.9-4) unstable; urgency=medium
+
+  * add -ffloat-store to COMPILE_FLAGS; enable awami tests again
+
+ -- Rene Engelhard   Tue, 21 Feb 2017 12:02:23 +0100
+
 graphite2 (1.3.9-3) unstable; urgency=medium
 
   * s/asciidoc, dblatex/asciidoc-dblatex/ in Build-Depends-Indep
diff -Nru graphite2-1.3.9/debian/libgraphite2-3-dbg.substvars 
graphite2-1.3.9/debian/libgraphite2-3-dbg.substvars
--- graphite2-1.3.9/debian/libgraphite2-3-dbg.substvars 2016-11-17 
13:54:13.0 +0100
+++ graphite2-1.3.9/debian/libgraphite2-3-dbg.substvars 1970-01-01 
01:00:00.0 +0100
@@ -1,2 +0,0 @@
-misc:Depends=
-misc:Pre-Depends=
diff -Nru graphite2-1.3.9/debian/patches/disable-awami-tests.diff 
graphite2-1.3.9/debian/patches/disable-awami-tests.diff
--- graphite2-1.3.9/debian/patches/disable-awami-tests.diff 2016-11-17 
13:54:13.0 +0100
+++ graphite2-1.3.9/debian/patches/disable-awami-tests.diff 1970-01-01 
01:00:00.0 +0100
@@ -1,36 +0,0 @@
-Description: Disable awami tests
- 12:06 < uniscript> @_rene_ I'm not surprised about that particular error, and 
I 
- would be tempted to say: ignore it. But we should make the package pass that 
tes
- t. Any chance you can get hold of the test result? build/tests/awamicmp1.json 
fr
- om that build?
- 12:07 -!- erAck [~e...@x4e3637b2.dyn.telefonica.de] has joined 
#libreoffice-dev
- 12:07 -!- mode/#libreoffice-dev [+o erAck] by ChanServ
- 12:07 < uniscript> grr. I must learn to drop @. sorry
- 12:07 < uniscript> _rene_
- 12:09 < _rene_> can try in a i386 chroot when back home, yes..
- 12:09 < uniscript> tia
- 12:10 < uniscript> basically there are rounding errors, I assume, and they 
can be ignored. It's a matter of quietly dropping the failing strings.
- 12:10 < _rene_> and well, ignoring would mean ignoring the testsuite results, 
so... (or just ignore those two tests...)
- 12:10 < uniscript> just ignore those two tests
-Author: Rene Engelhard 
-

-The information above should follow the Patch Tagging Guidelines, please
-checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
-are templates for supplementary fields that you might want to add:
-
-Origin: vendor
-Forwarded: not-needed
-Reviewed-By: Martin Hosken 
-Last-Update: 2016-11-17
-
 graphite2-1.3.9.orig/tests/CMakeLists.txt
-+++ graphite2-1.3.9/tests/CMakeLists.txt
-@@ -122,5 +122,5 @@ cmptest(chariscmp1 charis_r_gr.ttf udhr_
- cmptest(chariscmp2 charis_r_gr.ttf udhr_yor.txt)
- cmptest(annacmp1 Annapurnarc2.ttf udhr_nep.txt)
- cmptest(schercmp1 Scheherazadegr.ttf udhr_arb.txt -r)
--cmptest(awamicmp1 Awami_test.ttf awami_tests.txt -r -e 1)
--cmptest(awamicmp2 Awami_compressed_test.ttf awami_tests.txt -r -e 1)
-+#cmptest(awamicmp1 Awami_test.ttf awami_tests.txt -r -e 1)
-+#cmptest(awamicmp2 Awami_compressed_test.ttf awami_tests.txt -r -e 1)
diff -Nru graphite2-1.3.9/debian/patches/ffloat-store.diff 
graphite2-1.3.9/debian/patches/ffloat-store.diff
--- graphite2-1.3.9/debian/patches/ffloat-store.diff1970-01-01 
01:00:00.0 +0100
+++ graphite2-1.3.9/debian/patches/ffloat-store.diff2017-02-21 
12:02:23.0 +0100
@@ -0,0 +1,13 @@
+diff --git a/src/CMakeLists.txt b/src/CMakeLists.txt
+index 4f1e7e5..5b61b5c 100644
+--- a/src/CMakeLists.txt
 b/src/CMakeLists.txt
+@@ -108,7 +108,7 @@ set_target_properties(graphite2 PROPERTIES  PUBLIC_HEADER 
"${GRAPHITE_HEADERS}"
+ 
+ if  (${CMAKE_SYSTEM_NAME} STREQUAL "Linux")
+ set_target_properties(graphite2 PROPERTIES 
+-COMPILE_FLAGS   "-Wall -Wextra -Wno-unknown-pragmas -Wendif-labels 
-Wshadow -Wctor-dtor-privacy -Wnon-virtual-dtor -fno-rtti -fno-exceptions 
-fvisibility=hidden -fvisibility-inlines-hidden -fno-stack-protector"
++COMPILE_FLAGS   "-Wall -Wextra -Wno-unknown-pragmas -Wendif-labels 
-Wshadow -Wctor-dtor-privacy -Wnon-virtual-dtor -fno-rtti -fno-exceptions 
-fvisibility=hidden -fvisibility-inlines-hidden -fno-stack-protector 

Bug#855813: unblock: pound/2.7-1.3

[Sebastian Andrzej Siewior]

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

Please unblock package pound. It has been removed from testing due
openssl1.1. It has been fixed and user confirmed in #855458 that it is
working. Please find attach the debdiff against .2 which was in testing
earlier.

unblock pound/2.7-1.3

Sebastian
diff -Nru pound-2.7/debian/changelog pound-2.7/debian/changelog
--- pound-2.7/debian/changelog	2016-07-31 11:40:52.0 +0200
+++ pound-2.7/debian/changelog	2017-02-19 15:13:02.0 +0100
@@ -1,3 +1,10 @@
+pound (2.7-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build it with libssl1.0-dev for Jessie (Closes: #828511).
+
+ -- Sebastian Andrzej Siewior   Sun, 19 Feb 2017 15:13:02 +0100
+
 pound (2.7-1.2) unstable; urgency=medium
 
   * Include .orig.tar.gz in upload.
diff -Nru pound-2.7/debian/control pound-2.7/debian/control
--- pound-2.7/debian/control	2016-07-30 21:10:00.0 +0200
+++ pound-2.7/debian/control	2017-02-19 15:12:47.0 +0100
@@ -2,7 +2,7 @@
 Section: net
 Priority: extra
 Maintainer: Brett Parker 
-Build-Depends: debhelper (>= 9), libssl-dev (>= 1.0.2), autotools-dev, libpcre3-dev, openssl
+Build-Depends: debhelper (>= 9), libssl1.0-dev | libssl-dev (<< 1.1), autotools-dev, libpcre3-dev, openssl
 Standards-Version: 3.9.2
 Homepage: http://www.apsis.ch/pound/
 
diff -Nru pound-2.7/debian/patches/0002-add-support-openssl1.1-dhparam.patch pound-2.7/debian/patches/0002-add-support-openssl1.1-dhparam.patch
--- pound-2.7/debian/patches/0002-add-support-openssl1.1-dhparam.patch	1970-01-01 01:00:00.0 +0100
+++ pound-2.7/debian/patches/0002-add-support-openssl1.1-dhparam.patch	2017-02-19 15:10:59.0 +0100
@@ -0,0 +1,54 @@
+From: Sebastian Andrzej Siewior 
+Date: Sun, 19 Feb 2017 14:34:38 +0100
+Subject: [PATCH] pound: Add support for openssl 1.1
+
+This patch adds support for "openssl dhparam -C" created header files where
+openssl binary itself is 1.1 but the code using the file is linked against
+1.0.2.
+This will not let the pound as compile against openssl 1.1.
+
+Signed-off-by: Sebastian Andrzej Siewior 
+---
+ svc.c |   31 +++
+ 1 file changed, 31 insertions(+)
+
+--- a/svc.c
 b/svc.c
+@@ -1448,6 +1448,37 @@ do_RSAgen(void)
+ return;
+ }
+ 
++#if OPENSSL_VERSION_NUMBER < 0x1010
++static inline int DH_set0_pqg(DH *dh, BIGNUM *p, BIGNUM *q, BIGNUM *g)
++{
++	/* If the fields p and g in d are NULL, the corresponding input
++	 * parameters MUST be non-NULL.  q may remain NULL.
++	 */
++	if ((dh->p == NULL && p == NULL)
++	|| (dh->g == NULL && g == NULL))
++		return 0;
++
++	if (p != NULL) {
++		BN_free(dh->p);
++		dh->p = p;
++	}
++	if (q != NULL) {
++		BN_free(dh->q);
++		dh->q = q;
++	}
++	if (g != NULL) {
++		BN_free(dh->g);
++		dh->g = g;
++	}
++
++	if (q != NULL) {
++		dh->length = BN_num_bits(q);
++	}
++
++	return 1;
++}
++#endif
++
+ #include"dh512.h"
+ 
+ #if DH_LEN == 1024
diff -Nru pound-2.7/debian/patches/series pound-2.7/debian/patches/series
--- pound-2.7/debian/patches/series	2016-07-30 22:50:48.0 +0200
+++ pound-2.7/debian/patches/series	2017-02-19 15:11:19.0 +0100
@@ -1 +1,2 @@
 0001-Add-MKCALENDAR-to-xHTTP-2-and-above.patch
+0002-add-support-openssl1.1-dhparam.patch

Bug#855812: borgbackup: missing fuse dependency

[Magnus Nord]

Package: borgbackup
Version: 1.0.9-1~bpo8+1
Severity: minor

Dear Maintainer,

The "borg umount" command does not work, giving the error:
FileNotFoundError: [Errno 2] No such file or directory: 'fusermount'

Installing the fuse package fixes this, so one solution for this
is adding the fuse package as a dependency.


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

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

Versions of packages borgbackup depends on:
ii  libacl12.2.52-2
ii  libc6  2.19-18+deb8u7
ii  liblz4-1   0.0~r122-2
ii  libssl1.0.01.0.1t-1+deb8u6
ii  python33.4.2-2
ii  python3-llfuse 0.40-2+b2
ii  python3-msgpack0.4.6-1~bpo8+1
ii  python3-pkg-resources  5.5.1-1

borgbackup recommends no packages.

Versions of packages borgbackup suggests:
pn  borgbackup-doc  

-- no debconf information

Bug#855811: release.debian.org: release.d.o WWW should explicitly recommend against uploading to sid during the freeze

[Sean Whitton]

Package: release.debian.org
Severity: wishlist

Dear release team,

release.d.o WWW says

If you are unable to bring your fix through unstable, for example
because there are unrelated changes already uploaded there, the
release team can grant you permission to use the
testing-proposed-updates mechanism.

It is possible to infer from this that one should not upload anything to
unstable unless it is a targeted fix for a bug in testing.  However, one
might not make this inference before making an upload of, say, a new
upstream version.  DDs make this mistake from time-to-time.

In my own case, I was only aware of the release team's recommendation to
use experimental because I watched the release team's presentation at
debconf17.  So far as I can tell, this recommendation is not documented
anywhere, nor stated in any recent editions of "Bits from the Release
Team".

I'd like to suggest that this recommendation be stated explicitly on the
release team's website, to reduce the number of blocking uploads to
unstable made during the freeze.

Thanks!

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: amd64 (x86_64)

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

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#855810: libhdf5-openmpi-100 doesn't work on arm64

[Gilles Filippini]

Package: libhdf5-openmpi-100
Version: 1.10.0-patch1+docs-3
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

The attached simple testcase fails on arm64 with:
HDF5-DIAG: Error detected in HDF5 (1.10.0-patch1) MPI-process 0:
  #000: ../../../src/H5F.c line 491 in H5Fcreate(): unable to create file
major: File accessibilty
minor: Unable to open file
  #001: ../../../src/H5Fint.c line 1100 in H5F_open(): unable to open
file: time = Mon Feb 20 10:57:13 2017
, name = 'test.med', tent_flags = 13
major: File accessibilty
minor: Unable to open file
  #002: ../../../src/H5FD.c line 812 in H5FD_open(): open failed
major: Virtual File Layer
minor: Unable to initialize object
  #003: ../../../src/H5FDmpio.c line 997 in H5FD_mpio_open():
MPI_File_open failed
major: Internal error (too specific to document in detail)
minor: Some MPI function failed
  #004: ../../../src/H5FDmpio.c line 997 in H5FD_mpio_open():
MPI_ERR_OTHER: known error not in list
major: Internal error (too specific to document in detail)
minor: MPI Error String
HDF5-DIAG: Error detected in HDF5 (1.10.0-patch1) MPI-process 0:
  #000: ../../../src/H5F.c line 749 in H5Fclose(): not a file ID
major: Invalid arguments to routine
minor: Inappropriate type

To build it:
$ h5pcc.openmpi -o h5_mpitest h5_mpitest.c

To run it:
$ OMPI_MCA_orte_rsh_agent=/bin/false mpirun.openmpi -np 1 ./h5_mpitest

_g.

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEoJObzArDE05WtIyR7+hsbH/+z4MFAlisuGoACgkQ7+hsbH/+
z4OlwAf/UP1ZVWtfDEkSiGiGz8ieeQ2gzmogBnd64WPKdKupv3ApyXwh33Of00pw
KtRxN6cDqYIxKkd5dbwERHf2+pV82kWLJmnV6gDhi83FjEPm6cxNhaKUAcgnexZz
QlNHjfQKXoYj8NAm7rtOyJSKyEVfupGzJNgYWdUat9xEnh1blbRNGKeod8y67HVC
lM2CEw+jPNpuFlHSVuNP3eJj4rym+KybYF6dSlQRrDrv9zSs7XREyvfiJ6MaHpzZ
Fzq/xlTR0nfQ0xBvec6aTzuOqdkFsYhNJ1hH+p+9oNnrkv9czIogU8avYe5snde0
H2HMZn5P02JhvfB6wAZy4IfHt/SXNg==
=a4uN
-END PGP SIGNATURE-
#include 
#include 
#define FILE "test.med"

int main(int argc, char *argv[]) {

   hid_t   file_id;
   hid_t   fapl;
   int mpi_size, mpi_rank, ret=0;

   MPI_Init(, );
   MPI_Comm_size(MPI_COMM_WORLD, _size);
   MPI_Comm_rank(MPI_COMM_WORLD, _rank);

   /* Create a new file using default properties. */
   fapl = H5Pcreate (H5P_FILE_ACCESS);
   H5Pset_fapl_mpio(fapl, MPI_COMM_WORLD, MPI_INFO_NULL);
   file_id = H5Fcreate(FILE,H5F_ACC_TRUNC, H5P_DEFAULT,fapl);

   /* Close the file. */
   H5Fclose(file_id);
   H5Pclose(fapl);

   MPI_Finalize();
   return 0;
}

Bug#855809: [clamav-milter] LocalNet configuration via debconf fails for multiple networks or hosts

[Lars Kruse]

Package: clamav-milter
Version: 0.99.2+dfsg-0+deb8u2
Severity: minor

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

Dear Maintainer,

the helpful debconf-based configuration of clamav-milter contains the following
description for the "LocalNet" setting:

 Please specify, in CIDR notation (host(name)/mask), the hosts for which no
 scanning should be performed on incoming mail. Multiple entries should be
 separated by spaces.


After entering multiple networks in this field (e.g. "10.0.1.0/24 10.0.2.0/24")
the following line is written into the clamav-milter config file:

 LocalNet 10.0.1.0/24 10.0.2.0/24

clamav-milter refuses to work with this setting ("failed to resolve ...").


The proper configuration settings (according to the manpage) would be the
following:

 LocalNet 10.0.1.0/24
 LocalNet 10.0.2.0/24


Thank you for your time!
Cheers,
Lars

Bug#837067: Help requested: Packages which FTBFS randomly

[Emilio Pozuelo Monfort]

Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=779041

On 21/02/17 21:44, Emilio Pozuelo Monfort wrote:
> On 21/02/17 18:30, Santiago Vila wrote:
>> On Tue, Feb 21, 2017 at 11:21:30AM -0600, Jeff Epler wrote:
>>> On Tue, Feb 21, 2017 at 05:32:34PM +0100, Santiago Vila wrote:
 On Fri, 17 Feb 2017, Jeff Epler wrote:
> Using a fresh 1CPU / 1GB x86 system on digitalocean's NYC region, 
> upgraded to
> debian testing, I tried sbuilding libsecret.  So far, 2/2 builds failed.
>
> # grep ^FAIL libsecret_*.build
> libsecret_i386-2017-02-17T14:42:53Z.build:FAIL: test-collection 18 
> /collection/delete-sync
> libsecret_i386-2017-02-17T14:50:00Z.build:FAIL: test-collection 18 
> /collection/delete-sync

 Thanks a lot. Can you try a few more times?
>>>
>>> I ended up leaving that machine up for 12 builds total.  they all failed.  
>>> I've since recycled the instance.
>>
>> Ok, I think that's enough to prove that the reason for this is not a
>> misconfiguration in my machines.
>>
>> (I tried 434 times in total and it failed 434 times).
>>
>> Debian GNOME Maintainers: Do you plan to fix this for stretch?
> 
> Yes.

This now is https://bugzilla.gnome.org/show_bug.cgi?id=779041.

Emilio

Bug#855808: Pending fixes for bugs in the prometheus package

[pkg-go-maintainers]

tag 855808 + pending
thanks

Some bugs in the prometheus package are closed in revision
cb72f3807cabc7526052540055056dd1b5890979 in branch 'debian/sid' by
Martín Ferrari

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/prometheus.git/commit/?id=cb72f38

Commit message:

Add version to libjs-mustache dependency. Closes: #855808.

Bug#844762: [Pkg-kde-extras] Bug#844762: amarok crashes on startup with "Message recipient disconnected from message bus without replying"

[Florian Ernst]

tag 844762 - moreinfo
thanks

On Sat, Dec 03, 2016 at 12:19:07PM -0800, Phil Dibowitz wrote:
> Here you are:
> 
> Thread 1 "amarok" received signal SIGSEGV, Segmentation fault.
> 0x7fffcdd4ab67 in QMetaObject::className() const ()
>from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
> (gdb) thread apply all bt
> [...]

And for me it looks like this:

$ gdb --args amarok --nofork
GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from amarok...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/amarok --nofork
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
QDBusConnection: session D-Bus connection created before QCoreApplication. 
Application may misbehave.

Program received signal SIGSEGV, Segmentation fault.
0x7fffcdd4c4c7 in QMetaObject::className() const () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5   
  
(gdb) thread apply all bt   

   


   
Thread 1 (Thread 0x77ed4b80 (LWP 626)): 

   
#0  0x7fffcdd4c4c7 in QMetaObject::className() const () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5   
  
#1  0x7fffce68c2cf in ?? () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  
#2  0x7fffce625d17 in ?? () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  
#3  0x77de864a in ?? () from /lib64/ld-linux-x86-64.so.2

   
#4  0x77de875b in ?? () from /lib64/ld-linux-x86-64.so.2

   
#5  0x77deccd8 in ?? () from /lib64/ld-linux-x86-64.so.2

   
#6  0x77de84f4 in ?? () from /lib64/ld-linux-x86-64.so.2

   
#7  0x77dec489 in ?? () from /lib64/ld-linux-x86-64.so.2

   
#8  0x7fffeec9eee9 in ?? () from /lib/x86_64-linux-gnu/libdl.so.2   

   
#9  0x77de84f4 in ?? () from /lib64/ld-linux-x86-64.so.2

   
#10 0x7fffeec9f521 in ?? () from /lib/x86_64-linux-gnu/libdl.so.2   

   
#11 0x7fffeec9ef82 in dlopen () from /lib/x86_64-linux-gnu/libdl.so.2   

   
#12 0x7fffcf6e23a0 in ?? () from /usr/lib/x86_64-linux-gnu/libvlccore.so.8  

   
#13 0x7fffcf6c665b in ?? () from /usr/lib/x86_64-linux-gnu/libvlccore.so.8  
   

Bug#855808: [pkg-go] Bug#855808: prometheus: Graph page on web interface references nonexistent mustache.min.js

[Martín Ferrari]

Hi Drew,

On 21/02/17 18:09, Drew Bloechl wrote:

> The graph page on the Prometheus web interface references a
> mustache.min.js file that doesn't exist in my libjs-mustache package,
> which makes the page nonfunctional. I see the file list in the 2.3.0-2
> version of libjs-mustache does include this file, so I think the
> prometheus package needs to depend on libjs-mustache (>= 2.3.0).

Thanks for spotting this. It is definitely an omission on my part, but
libjs-mustache 2.3.0-2 has been in testing since December, so this can
only affect you if you have not updated that package...


-- 
Martín Ferrari (Tincho)

Bug#855617: [Popcon-developers] Bug#855617: popularity-contest: /etc/cron.daily/popularity-contest can't locate strict.pm

[Martin Dosch]

Hi Bill,


> what about
> ls -ld /usr/local/lib/x86_64-linux-gnu/
> ls -ld /usr/local/lib
> ls -ld /usr/local/

ls -ld /usr/local/lib/x86_64-linux-gnu/
ls: cannot access '/usr/local/lib/x86_64-linux-gnu/': No such file or
directory

ls -ld /usr/local/lib/
drwxr-s--- 5 root staff 4096 Feb 14 20:10 /usr/local/lib/

ls -ld /usr/local/
drwxrwsr-x 10 root staff 4096 Jul 24  2016 /usr/local/

I'm still irritated why popcon expects perl in /usr/local/ when the
debian stretch package perl-base is installing these files in
/usr/lib/x86_64-linux-gnu/perl-base

Best wishes,
Martin

Bug#764639: libgl1-nvidia-glx: failst to upgrade or install with KMS (nouveau) active

[Luca Boccassi]

On Mon, 2017-02-20 at 11:25 +, Luca Boccassi wrote:
> On Sun, 2017-02-19 at 21:09 +0100, Andreas Beckmann wrote:
> > Control: fixed -1 361.45.18-1
> > 
> > On 2017-02-11 00:06, Andreas Beckmann wrote:
> > > Problem is that the 340xx driver (didn't check 304xx) does not
> > > unregister the proc entries if it aborts loading (due to nouveau
> > > being
> > > loaded already).
> > 
> > The missing nv_unregister_procfs() call was added upstream in the
> > 361
> > series.
> > 
> > The same problem seems to exist in 304xx. I've ported my patch to
> > that
> > legacy series, too, but I have no way to test it properly.
> > 
> > Luca, perhaps you could try the following (even if you have no
> > 304xx
> > requiring hardware, as long as the test machine has a nvidia gpu):
> > * load nouveau module
> > * load 304xx module (should fail, since another module has already
> > grabbed the device)
> > 
> > I don't know if the relevant code path gets executed if no
> > supported
> > hardware is available ... if it is I would expect the 304xx module
> > (without patch) to leave a stale /proc/driver/nvidia (requires
> > reboot to
> > get rid of it again), while the patched version leaves /proc clean.
> > It's also possible that the problem is not (easily) reproducible on
> > 304xx, since the initialization of the procfs entries seems to come
> > much
> > later.
> 
> I can certainly give it a spin, in the next couple of days probably,
> will report back how it goes.
> 
> Kind regards,
> Luca Boccassi

It is surprisingly difficult to boot with only nouveau! Loads and loads
of things trying to load the nvidia module.

Anyway, I just tried with the latest 378 kernel module, and it still
leaves behind the /proc/driver/nvidia, if nouveau is loaded first.

Kind regards,
Luca Boccassi

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

Bug#854608: subuser: Bundles sphinx_rtd_theme, please use packaged version instead

[Stanislas Leduc]

Hi Aaron, 

i think change Build-Depends, but i set them for 0.6.0, but seem not for
0.6.1, i fix them and pushed new version, wait that sponsored 0.6.1-3 to
main repository. 

Sorry for this lack of vigilance. 

Best regards 

Le 2017-02-21 21:23, Aaron M. Ucko a écrit :

> Package: subuser
> Version: 0.6.1-2
> Followup-For: Bug #854608
> 
> Please don't forget to
> 
>> * Add python3-sphinx-rtd-theme to Build-Depends.
> 
> As it is, the automatic build failed:
> 
> https://buildd.debian.org/status/fetch.php?pkg=subuser=all=0.6.1-2=1487669248=0
> 
> Theme error:
> sphinx_rtd_theme is no longer a hard dependency since version 1.4.0. Please 
> install it manually.(pip install sphinx_rtd_theme)
> debian/rules:12: recipe for target 'override_dh_auto_build' failed
> 
> Thanks!

Bug#853010: FWD: Re: build depends, maintainer interest for package OpenOCD

[Geert Stappers]

The e-mail that I wrote yesterday went to the wrong bugreport.

This time it should go the intented bugreport.
And it has a better "From: " address


- Forwarded message from Geert Stappers -

Date: Mon, 20 Feb 2017 17:59:07 +0100
From: Geert Stappers
To: 853...@bugs.debian.org, lu...@debian.org, u...@debian.org
Subject: Re: build depends,  maintainer interest for package OpenOCD
User-Agent: Mutt/1.5.21 (2010-09-15)

On Sat, Jan 28, 2017 at 10:24:57PM +0100, Geert Stappers wrote:
> Package: openocd
> Tags: patch
> 
> --- a/debian/control
> +++ b/debian/control
  
> That removes 'autotools-dev', there is still 'autotools-dev, autoconf,'.
> And 'libftdi-dev' is now on separate line.
> 
> 
> Also is this bugreport to show my interrest in co-maintaining
> the Debian OpenOCD package.
> 

Yes, I still want to work on packaging openocd.

But how think the current maintainers about that?

That is why Uwe and Luca are also in the To: field.


Groeten
Geert Stappers
DD, Maintainer of package urjtag
-- 
Leven en laten leven



- End forwarded message -

Groeten
Geert Stappers
-- 
Leven en laten leven

Bug#837067: Help requested: Packages which FTBFS randomly

[Emilio Pozuelo Monfort]

On 21/02/17 18:30, Santiago Vila wrote:
> On Tue, Feb 21, 2017 at 11:21:30AM -0600, Jeff Epler wrote:
>> On Tue, Feb 21, 2017 at 05:32:34PM +0100, Santiago Vila wrote:
>>> On Fri, 17 Feb 2017, Jeff Epler wrote:
 Using a fresh 1CPU / 1GB x86 system on digitalocean's NYC region, upgraded 
 to
 debian testing, I tried sbuilding libsecret.  So far, 2/2 builds failed.

 # grep ^FAIL libsecret_*.build
 libsecret_i386-2017-02-17T14:42:53Z.build:FAIL: test-collection 18 
 /collection/delete-sync
 libsecret_i386-2017-02-17T14:50:00Z.build:FAIL: test-collection 18 
 /collection/delete-sync
>>>
>>> Thanks a lot. Can you try a few more times?
>>
>> I ended up leaving that machine up for 12 builds total.  they all failed.  
>> I've since recycled the instance.
> 
> Ok, I think that's enough to prove that the reason for this is not a
> misconfiguration in my machines.
> 
> (I tried 434 times in total and it failed 434 times).
> 
> Debian GNOME Maintainers: Do you plan to fix this for stretch?

Yes.

Cheers,
Emilio

Bug#855805: [libreoffice-common] Texts in Tooltips are not visible

[Rene Engelhard]

reassign 855805 libreoffice-kde
found 855805 1:5.3.0-1
tag 855805 + moreinfo
tag 855805 + unreproducible
thanks

Hi,

On Tue, Feb 21, 2017 at 10:02:32PM +0100, Thomas Florek wrote:
> > And which UI? gtk? gtk3? kde?
> 
> KDE Version 5.8.5
> KDE Frameworks 5.28.0
> Qt 5.7.1 (compiled against 5.7.1)
> 
> Tested against galaxy, breeze, sifr.

Ok, so it looks KDE-specific since it works in my gtk3-environment.

That said, even with installing libreoffice-kde and export 
OOO_FORCE_DESKTOP="kde4"
to force KDE UI I *do* get tooltips (just tried the toolbar buttons)...

Regards,

Rene

Bug#855617: [Popcon-developers] Bug#855617: popularity-contest: /etc/cron.daily/popularity-contest can't locate strict.pm

[Martin Dosch]

Hi Bill,

Am 21.02.2017 um 22:10 schrieb Bill Allombert:
> So what gives:
> 
> ls -ld /usr/local/lib/x86_64-linux-gnu/perl

ls: cannot access '/usr/local/lib/x86_64-linux-gnu/perl': No such file
or directory

> ls -ld /usr/local/lib/x86_64-linux-gnu/perl/5.24.1/

ls: cannot access '/usr/local/lib/x86_64-linux-gnu/perl/5.24.1/': No
such file or directory

> ls -l /usr/local/lib/x86_64-linux-gnu/perl/5.24.1/strict.pm

ls: cannot access
'/usr/local/lib/x86_64-linux-gnu/perl/5.24.1/strict.pm': No such file or
directory

Now according to the file location from
https://packages.debian.org/stretch/amd64/perl-base/filelist :

ls -ld /usr/lib/x86_64-linux-gnu/perl-base/
drwxr-xr-x 16 root root 4096 Jan 17 21:47
/usr/lib/x86_64-linux-gnu/perl-base/

ls -l /ls -l /usr/lib/x86_64-linux-gnu/perl-base/strict.pm
-rw-r--r-- 1 root root 1606 Jan 16 00:35
/usr/lib/x86_64-linux-gnu/perl-base/strict.pm

Best wishes,
Martin

Bug#855808: prometheus: Graph page on web interface references nonexistent mustache.min.js

[Drew Bloechl]

Package: prometheus
Version: 1.5.2+ds-2
Severity: important

The graph page on the Prometheus web interface references a
mustache.min.js file that doesn't exist in my libjs-mustache package,
which makes the page nonfunctional. I see the file list in the 2.3.0-2
version of libjs-mustache does include this file, so I think the
prometheus package needs to depend on libjs-mustache (>= 2.3.0).

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

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

Versions of packages prometheus depends on:
ii  daemon   0.6.4-1
ii  libc62.19-18+deb8u7
ii  libjs-bootstrap  3.2.0+dfsg-1
ii  libjs-eonasdan-bootstrap-datetimepicker  4.17.43-1
ii  libjs-jquery 3.1.1-2
ii  libjs-jquery-hotkeys 0~20130707+git2d51e3a9+dfsg-2
ii  libjs-moment 2.17.1+ds-1
ii  libjs-mustache   0.4.2-2
ii  libjs-rickshaw   1.5.0.dfsg-1

Versions of packages prometheus recommends:
ii  prometheus-node-exporter  0.13.0+ds-1

prometheus suggests no packages.

-- Configuration Files:
/etc/default/prometheus changed [not included]
/etc/prometheus/prometheus.yml changed [not included]

-- no debconf information

Bug#855689: jython.jar does not provide a Class-Path

[Gilles Filippini]

Hi Ole,

On Tue, 21 Feb 2017 09:54:48 +0100 Ole Streicher  wrote:
> Package: jython
> Version: 2.5.3-14
> Severity: serious
> 
> There is no classpath for the dependencies of jython.jar defined in its
> manifest:
> 
> $ unzip -p /usr/share/java/jython.jar META-INF/MANIFEST.MF | \
>   grep Class-Path
> $
> 
> This leads to the problem that dependent packages need to specify the
> classpath themself, which is difficult since it is not documented in
> /usr/share/docs/jython. Also, it requires tracking internal changes of
> jython, since some of the dependent jar names are version dependent;
> namely antlr3-runtime-3.2.jar, which makes it difficult to handle for
> the dependencies over long time (f.e. for backports).
> 
> Java policy requires to have the classpath documented. I would ask you
> to do this in the manifest (at least for the strong dependencies), since
> this makes the usage much easier.

Would the attached patch do the trick?

Thanks,

_g.
diff -Nru jython-2.5.3/debian/changelog jython-2.5.3/debian/changelog
--- jython-2.5.3/debian/changelog   2016-12-11 17:02:02.0 +0100
+++ jython-2.5.3/debian/changelog   2017-02-21 20:22:33.0 +0100
@@ -1,3 +1,9 @@
+jython (2.5.3-15) UNRELEASED; urgency=medium
+
+  * Set 'Class-Path' into jython.jar's manifest (closes: #855689)
+
+ -- Gilles Filippini   Tue, 21 Feb 2017 20:22:33 +0100
+
 jython (2.5.3-14) unstable; urgency=medium
 
   * debian/jython_perl: fix use of abs_path
diff -Nru jython-2.5.3/debian/patches/04-runtime-classpath.patch 
jython-2.5.3/debian/patches/04-runtime-classpath.patch
--- jython-2.5.3/debian/patches/04-runtime-classpath.patch  1970-01-01 
01:00:00.0 +0100
+++ jython-2.5.3/debian/patches/04-runtime-classpath.patch  2017-02-21 
20:22:33.0 +0100
@@ -0,0 +1,12 @@
+Index: jython/build.xml
+===
+--- jython.orig/build.xml
 jython/build.xml
+@@ -721,6 +721,7 @@ The readme text for the next release wil
+  
excludes="org/python/expose/generate/**,org/python/version.properties"/>   
+   
+   
++  
+   
+   
+   
diff -Nru jython-2.5.3/debian/patches/series jython-2.5.3/debian/patches/series
--- jython-2.5.3/debian/patches/series  2016-12-11 17:02:02.0 +0100
+++ jython-2.5.3/debian/patches/series  2017-02-21 20:22:33.0 +0100
@@ -1,3 +1,4 @@
 01-build.patch
 02-jnr_refactoring.patch
 03-default-cachedir.patch
+04-runtime-classpath.patch
diff -Nru jython-2.5.3/debian/rules jython-2.5.3/debian/rules
--- jython-2.5.3/debian/rules   2016-12-11 17:02:02.0 +0100
+++ jython-2.5.3/debian/rules   2017-02-21 20:22:33.0 +0100
@@ -1,5 +1,7 @@
 #!/usr/bin/make -f
 
+RTCLASSPATH := $(shell grep '^\s*appendJar' debian/jython_perl | sed 
"s/^.*('//;s/').*$$//" | tr '\n' ' ')
+
 %:
dh $@ --with python2 --with maven-repo-helper
 
@@ -31,7 +33,7 @@
 
 override_dh_auto_build:
# Build the class files.
-   ant -nouserlib developer-build jar javadoc
+   ant -nouserlib developer-build jar javadoc 
-DRuntimeClasspath="$(RTCLASSPATH)"
# -nouserlib is required to prevent conflicts with the ant jython plugin
 
# Generate OSGi metadata for jython.jar


signature.asc
Description: OpenPGP digital signature

Bug#855617: [Popcon-developers] Bug#855617: popularity-contest: /etc/cron.daily/popularity-contest can't locate strict.pm

[Bill Allombert]

On Tue, Feb 21, 2017 at 09:42:46PM +0100, Martin Dosch wrote:
> Hello Bill,
> 
> actually I haven't installed an alternative version of perl (at least
> I'm not aware of) and the path where the files are located fits the
> official debian package of perl base:
> https://packages.debian.org/stretch/amd64/perl-base/filelist
> If popcon expects a different perl package with files located somewhere
> else the dependencies should be fixed.

Hello Martin,

popcon expects the user 'nobody' to be allowed to use perl.
Otherwise you have to change the config file
/etc/cron.daily/popularity-contest
specifically the function run_popcon().

> >apt list -a perl-base
> >Listing... Done
> >perl-base/testing,unstable,now 5.24.1-1 amd64 [installed]
> 
> Obviously it's due to my UMASK of 077 cause this wouldn't allow
> nobody:nogroup to access it.
> But shouldn't debian packages installed via apt/dpkg manage the access
> rights regardless of UMASK?

So what gives:

ls -ld /usr/local/lib/x86_64-linux-gnu/perl
ls -ld /usr/local/lib/x86_64-linux-gnu/perl/5.24.1/
ls -l /usr/local/lib/x86_64-linux-gnu/perl/5.24.1/strict.pm

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 

Bug#855805: [libreoffice-common] Texts in Tooltips are not visible

[Thomas Florek]

> And which UI? gtk? gtk3? kde?

KDE Version 5.8.5
KDE Frameworks 5.28.0
Qt 5.7.1 (compiled against 5.7.1)

Tested against galaxy, breeze, sifr.

> Can you please stop filing non-Debian bugs in Debian. You use siduction,
> not Debian. (Yeah, I know it's a sid snapshot/based on sid. still.)

No offense, but siduction installs (almost) only packages from genuine
Debian repos and the kernel is in no way exotic ;)

Greetings,
Tom

Bug#846068: nitrogen: GUI fails to start due to GIO error

[Vladimir K]

https://github.com/l3ib/nitrogen/issues/93
The cause was an empty structure in /usr/local/share/icons/hicolor/ with 
supposedly broken cache.
This bug can be closed.

Bug#855617: [Popcon-developers] Bug#855617: popularity-contest: /etc/cron.daily/popularity-contest can't locate strict.pm

[Martin Dosch]

Hello Bill,

actually I haven't installed an alternative version of perl (at least
I'm not aware of) and the path where the files are located fits the
official debian package of perl base:
https://packages.debian.org/stretch/amd64/perl-base/filelist
If popcon expects a different perl package with files located somewhere
else the dependencies should be fixed.

> apt list -a perl-base
> Listing... Done
> perl-base/testing,unstable,now 5.24.1-1 amd64 [installed]

Obviously it's due to my UMASK of 077 cause this wouldn't allow
nobody:nogroup to access it.
But shouldn't debian packages installed via apt/dpkg manage the access
rights regardless of UMASK?

Best wishes,
Martin

Bug#853147: Please reopen Bug #853147 - Users still get misleading warning at first login when nautilus-admin is installed

[Mantas Baltix]

Please don't close this bugreport - current implementation is really bad
way on multi-user systems and no other nautilus extensions (except dead
6-years old nautilus-compare) uses this approach.
When I install nautilus-admin package on multi-user system (where reboots
are very rare), then *all users* gets this misleading warning *at first
login* after installation:
"The file manager must be restarted in order to start the Nautilus Admin
extension."
Users shouldn't see such dialog at login, because nautilus-admin extension
works fine right after login (there was no nautilus process for that user
at installation time), so, no need to restart nautilus!

Bruno Nova  wrote:
> dialog asking to restart the file manager is there to do that, so
> that average users are not confused when the extension doesn't
> work after being installed.

Average users doesn't have administration rights and doesn't have ability
to install deb packages :)
This dialog should be displayed *only for user, who install this package*,
not for every user in operating system.

User's should not be disturbed about installed nautilus extensions,
*this info is useful only for system administrator* - only for 1 user, who
installs this package, so, please use debconf in debian/postinst or put
this info in package's description or
/usr/share/doc/nautilus-admin/README.Debian

Prompting "every" user instead of system administrator violates Debian
policy, see
www.debian.org/doc/debian-policy/ch-binary.html#s-maintscriptprompt

Prompting must be done by *communicating through a program, such as
*debconf*, which conforms to the Debian Configuration Management
 Specification, version 2 or higher.

Thanks for maintaining such useful extension,
Mantas,
Prekyba kompiuteriais su Linux OS - http://tinklas.eu/prekyba
Naudokite laisvą Linux operacinę sistemą savo kompiuteryje -
http://baltix.akl.lt

On Mon, Feb 20, 2017 at 10:27 PM, Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the nautilus-admin package:
>
> #853147: Users get misleading warning at first login when nautilus-admin
> is installed
>
> It has been closed by Bruno Nova .
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Bruno Nova <
> brunomb.n...@gmail.com> by
> replying to this email.
>
> --
> 853147: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853147
>
> -- Forwarded message --
> From: Bruno Nova 
> To: 853147-d...@bugs.debian.org
> Cc:
> Date: Mon, 20 Feb 2017 20:22:54 +
> Subject:
> Since this doesn't appear to be a bug, and no one else has voiced
> their opinion, I'm closing this bug.
>
> -- Forwarded message --
> From: Mantas Baltix 
> To: Debian Bug Tracking System 
> Cc:
> Date: Mon, 30 Jan 2017 11:47:18 +0200
> Subject: Users get misleading warning at first login when nautilus-admin
> is installed
> Package: nautilus-admin
> Version: 0.2.4-1
>
> Dear Bruno,
>
> When I install nautilus-admin package on Ubuntu, then all users get
> misleading warning at first login after installation:
>
> "The file manager must be restarted in order to start the Nautilus
> Admin extension."
>
> This warning should be moved from nautilus-admin package
> debian/postinst script to package's description or
> /usr/share/doc/nautilus-admin/README.Debian, because of 2 reasons:
>
> 1. User's should not be disturbed about installed nautilus extensions,
> this info is useful only for system administrator, so, it belongs to
> package's description or /usr/share/doc/nautilus-admin/README.Debian
>
> 2. Prompting "every" user instead of system administrator violates
> Debian policy, see
> www.debian.org/doc/debian-policy/ch-binary.html#s-maintscriptprompt
>
> Prompting must be done by *communicating through a program, such as
> debconf*, which conforms to the Debian Configuration Management
> Specification, version 2 or higher.
>
> Thanks,
> Mantas
>

-- 
Prekyba kompiuteriais su Linux OS - http://tinklas.eu/prekyba
Naudokite laisvą Linux operacinę sistemą savo kompiuteryje -
http://baltix.akl.lt
Use Baltix GNU/Linux OS !

Bug#854608: subuser: Bundles sphinx_rtd_theme, please use packaged version instead

[Aaron M. Ucko]

Package: subuser
Version: 0.6.1-2
Followup-For: Bug #854608

Please don't forget to

> * Add python3-sphinx-rtd-theme to Build-Depends.

As it is, the automatic build failed:

https://buildd.debian.org/status/fetch.php?pkg=subuser=all=0.6.1-2=1487669248=0

  Theme error:
  sphinx_rtd_theme is no longer a hard dependency since version 1.4.0. Please 
install it manually.(pip install sphinx_rtd_theme)
  debian/rules:12: recipe for target 'override_dh_auto_build' failed

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#855807: unblock: fltk1.3/1.3.4-3

[Aaron M. Ucko]

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

Please unblock package fltk1.3.

It's been available for all architectures for just over a week without
incident (but can wait the full ten days if you prefer), and the only
difference between 1.3.4-2 (currently in testing) and 1.3.4-3 is a small
fix for Severity: important bug #855040:

https://anonscm.debian.org/cgit/users/ucko/fltk1.3.git/commit/?id=6f73807ca4ad2cefc969deb1020b88674f2fb2a6
(inlined below)

In short:

unblock fltk1.3/1.3.4-3

Thanks!

diff --git a/debian/changelog b/debian/changelog
index cc7571f..6e491ab 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+fltk1.3 (1.3.4-3) unstable; urgency=medium
+
+  * debian/fix-fltk-targets-noconfig: Append logic to refrain from
+enforcing the existence of fluid in FLTK_SKIP_FLUID mode, based
+on a suggestion from Gianfranco Costamagna .
+(Closes: #855040.)
+
+ -- Aaron M. Ucko   Mon, 13 Feb 2017 22:26:35 -0500
+
 fltk1.3 (1.3.4-2) unstable; urgency=medium
 
   * debian/fix-fltk-targets-noconfig: Update for current CMake output
diff --git a/debian/fix-fltk-targets-noconfig b/debian/fix-fltk-targets-noconfig
index e223940..8ef02d7 100755
--- a/debian/fix-fltk-targets-noconfig
+++ b/debian/fix-fltk-targets-noconfig
@@ -23,3 +23,12 @@ while (<>) {
 }
 print;
 }
+
+print <

Bug#855805: [libreoffice-common] Texts in Tooltips are not visible

[Rene Engelhard]

tag 855805 + moreinfo
thanks

Hi,

On Tue, Feb 21, 2017 at 09:26:33PM +0100, Thomas Florek wrote:
> Texts in Tooltips are not visible, Tooltips frames are empty.
> 
> VGA compatible controller: Intel Corporation 4th Generation Core
> Processor Family Integrated Graphics Controller (rev 06) (prog-if 00
> [VGA controller])
> 
> No matter, if xserver-xorg-video-intel is installed or not.
> No matter, which libreoffice-style.

And which UI? gtk? gtk3? kde?
(These days About also shows this.)

Given you use -breeze I _assume_ kde, but...

(KDE is the least tested thing. And it even is actually designed for
KDE4...)

> Kernel: Linux 4.10.0-towo.1-siduction-amd64

Can you please stop filing non-Debian bugs in Debian. You use siduction,
not Debian. (Yeah, I know it's a sid snapshot/based on sid. still.)

Regards,

Rene

Bug#855806: Translation for src:icedove packages

[Carsten Schoenert]

Package: src:icedove
Version: 1:45.7.1-1
Severity: normal

Hello Joe,

debian-devel is not the right place to request changes or talk about
very specific packaging details, so I dropped d-d and forward this
answer to the BTS.

Am 21.02.2017 um 21:23 schrieb Joe Dalton:
> Hi Carsten,
> I have a small request. When making the package descriptions (that is
> adding the phrase: This is a transitional package. It can be safely
> removed), it would be nice for us translators that a . is made
> between the text and the phrase. That phrase is already translated in
> most of the active languages. and adding it in a separate sections,
> means no work for us translators, as opposite to now there we have to
> run through x number of strings, copy the old text and adding This is
> a transitional package. It can be safely removed (translated) in all
> the sections, go through proofreading/control etc.
> 
> It's a small thing then making the package descriptions, but saves us
> a lot of work.

For sure we can do this and it's in all no problem. Will prepare
something for the next upload.

-- 
Regards
Carsten Schoenert

Bug#853783: ping

[Svante Signell]

On Tue, 2017-02-21 at 19:40 +, Brian Potkin wrote:
> On Thu 16 Feb 2017 at 22:38:59 +, Brian Potkin wrote:
> 
> YAP (Yet Another Ping :) )

Thanks for your reply. I'll do these test when I have physical access
to that printer/scanner in the end of this week.

Bug#855805: [libreoffice-common] Texts in Tooltips are not visible

[Thomas Florek]

Package: libreoffice-common
Version: 1:5.3.0-1
Severity: normal

--- Please enter the report below this line. ---
Texts in Tooltips are not visible, Tooltips frames are empty.

VGA compatible controller: Intel Corporation 4th Generation Core
Processor Family Integrated Graphics Controller (rev 06) (prog-if 00
[VGA controller])

No matter, if xserver-xorg-video-intel is installed or not.
No matter, which libreoffice-style.

--- System information. ---
Architecture:
Kernel: Linux 4.10.0-towo.1-siduction-amd64

Debian Release: 9.0
500 unstable ftp.spline.de
500 unstable deb.debian.org
500 testing deb.debian.org
500 buildd-unstable incoming.debian.org
1 experimental deb.debian.org

--- Package information. ---
Depends (Version) | Installed
==-+-=
libreoffice-style-default |
OR libreoffice-style |
ure | 5.3.0-1
libreoffice-core (= 1:5.3.0-1) | 1:5.3.0-1
python3:any (>= 3.3.2-2~) |
python3 (<< 3.6) | 3.5.3-1
python3 (>= 3.5~) | 3.5.3-1
python3.5 | 3.5.3-1
libc6 (>= 2.14) | 2.24-9
libgcc1 (>= 1:3.0) | 1:6.3.0-7
libpython3.5 (>= 3.5.0~b1) | 3.5.3-1
libstdc++6 (>= 5) | 6.3.0-7
uno-libs3 (>= 5.3.0~alpha) | 5.3.0-1
ure | 5.3.0-1


Recommends (Version) | Installed
==-+-=
fonts-liberation | 1:1.07.4-2
OR ttf-mscorefonts-installer |
python3-uno (>= 4.4.0~beta2) | 1:5.3.0-1
libexttextcat-data | 3.4.4-2


Suggests (Version) | Installed
===-+-===
libreoffice-style-breeze | 1:5.3.0-1
libreoffice-style-hicontrast |
libreoffice-style-oxygen |
libreoffice-style-sifr | 1:5.3.0-1
libreoffice-style-tango |

Bug#673515: do

[Geert Stappers]

Hi,

On 2017-02-23 I was impressed by seeing all those ITPs.  They say: do

Yes, doing gets things done.


Thanks for being an example.

Yes, this e-mail is intented as a compliment

Bug#855804: mirror listing update for ftp.ec-m.fr

[Geoffroy Desvernay]

Package: mirrors
Severity: minor
User: mirr...@packages.debian.org
Usertags: mirror-list

Submission-Type: update
Site: ftp.ec-m.fr
Type: leaf
Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x
Archive-ftp: /debian/
Archive-http: /debian/
Archive-rsync: debian/
Archive-upstream: ftp.de.debian.org
Updates: four
Maintainer: Geoffroy Desvernay 
Country: FR France
Sponsor: Ecole Centrale Marseille https://cri.centrale-marseille.fr/



Trace Url: http://ftp.ec-m.fr/debian/project/trace/ftp-master.debian.org
Trace Url: http://ftp.ec-m.fr/debian/project/trace/ftp.ec-m.fr

Bug#855430: examl: FTBFS on non-x86: unrecognized command line option ‘-msse3’

[Alexandros Stamatakis]

Dear Andreas,


I have packaged examl for Debian


Thank you :-)


and this is the first bug report the
package received.  As far as I'm reading the Makefile and docs the
-msse3 switch is effectively needed in the code.


Yes.


The only solution I
see to close this bug report is to not provide the binaries resulting
from those makefiles that are containing the -msse3 switch on those
architectures that do not know it.

Could you please confirm this suspicion?


Yes. The reason for this design is that the code is targeted at x86 
based cluster and supercomputing systems which are the most 
common/readily available, hence we do not support any other 
architectures for this code.



Kind regards and thanks for providing examl as free software


:-) Thanks for thr packaging.


   Andreas.

PS: If your lab provides other code you consider important for
bioinformatics please give me a hint to add it to the Debian
package pool as well.


Based on impact I would suggest packaging the following codes:

ExaBayes: https://github.com/aberer/exabayes
RogueNaRok: https://github.com/aberer/RogueNaRok
mPTP: https://github.com/Pas-Kapli/mptp

All the best,

Alexis

--
Prof. Dr. Alexandros (Alexis) Stamatakis

Phone:  +49-6221-533-240
Fax:+49-6221-533-298
E-Mail: alexandros.stamata...@h-its.org
WWW:www.h-its.org

HITS gGmbH
Schloss-Wolfsbrunnenweg 35
D-69118 Heidelberg
Amtsgericht Mannheim / HRB 337446
Managing Director: Dr. Gesa Schönberger
Scientific Director: Prof. Dr. Michael Strube

Bug#854941: sync-ui: fails to do anything

[Eduard Bloch]

Hallo,
* Patrick Ohly [Wed, Feb 15 2017, 03:07:46PM]:
> On Tue, 2017-02-14 at 22:47 +0100, Eduard Bloch wrote:
> > Hallo,
> > * Patrick Ohly [Sun, Feb 12 2017, 02:24:17PM]:
> > > On Sun, 2017-02-12 at 11:27 +0100, Eduard Bloch wrote:
> > > > Package: sync-ui
> > > > Version: 1.5.2-1
> > > > Severity: important
> > > > 
> > > > Dear Maintainer,
> > > > 
> > > >* What led up to the situation?
> > > > 
> > > > Attempted to download contacts from a phone (Android 6, Samsung A310F).
> > > 
> > > Can you check whether the phone really supports SyncML? See how to do
> > 
> > I thought SyncML was an emerging standard in the last decade and
> > in 2017 it's an obligatory feature.
> 
> The focus seems more on cloud synchronization these days.

Yeah, unfortunatelly.

> > > that with hcitool and sdptool under the "Troubleshooting" section from
> > > https://syncevolution.org/wiki/sync-your-phone-bluetooth
> > 
> > Checked that. Seems not to be supported.
> 
> Bummer. Do you know how car integration works? Does the car deal with
> the phone over Bluetooth (pairing and all), or did you install a special
> app?

No special app, the normal contact synchronization. The whole story
started because I wanted to find out why some contacts are not visible
to the car radio. Anyhow, I have a hunch on that story that I need to
track separately.

Tino mentioned PBAP, that might be it.

> > > A search shows that Samsung claims SyncML support for the phone, but it
> > > remains open whether that is SyncML over Bluetooth (a rare feature these
> > > days) or a SyncML client for a SyncML server (also a dying feature, but
> > > a bit more likely).
> > 
> > Well, ok, that might explain it. But could you please create a
> > messagebox saying "no supported SyncML or CalDAV device found" or
> > something like that rather than keeping the user look stupid?
> 
> There should have been something, so this bug may be valid.

I got an updated systemd config from the proposed package update and it
looks better now - i.e. there is a message that invites you to configure
syncronization instead of a plain grey screen.

There is just one cosmetic issue, the button looks misplaced. See here:
http://abload.de/image.php?img=6672cmssi.png

> However, there's no special "you seem to want to use this phone but it
> doesn't support SyncML" error handling, because the UI doesn't know
> which device you want to use. What it can do is find devices that have
> been paired and which advertise SyncML support. Your phone doesn't seem
> to do that, if you ran sdptool against it and did not find a SYNCML
> service.

Right, I gave up already. Sorry for bothering.

Regards,
Eduard.

Bug#756897: Specify ways to proof-read document post-save

[Jeffrey Ratcliffe]

On 20/02/17 00:56, martin f krafft wrote:
> also sprach Jeffrey Ratcliffe  [2017-02-19 00:26 
> +1300]:
>> I apologise for the previous poor tip. I've just tested exactly this,
>> i.e. a user-defined tool "run-mailcap %i" and it worked as expected.
> I can now confirm this:

Thanks.

> Indeed, and this is good enough I guess to replace the
> view-after-save feature, though there might be the situation where
> you're post-processing a PDF and then want to auto-view it, yet
> on-save hooks can't be chained… but I guess that's then the realm of
> shell scripts…
This occurred to me, too. I'll leave it in for a release or two, to let
any other bugs surface, but you are right, long-term, there is no need
for the view-after-save option any more.

In the mean time, I have fixed the bug where the post-save hooks in the
save window are not updated if it is opened before the Preferences
window. You'll see it in the next release.



signature.asc
Description: OpenPGP digital signature

Bug#855621: downgraded containerd

[Jamie McClelland]

I had the same problem.

It was triggered by upgrading containerd from 0.2.1~ds1-3 to
0.2.3~git20161117.78.03e5862~ds1-1.

There is an upstream ticket here:

https://github.com/docker/containerd/issues/299

I resolved it by downgrading containerd (I found an old copy here:
http://ftp.acc.umu.se/mirror/cdimage/snapshot/Debian/pool/main/c/containerd/).

It should be fixable by upgrading docker to 1.12 which will pass the
socket path in the right format expected by containerd.

jamie

Bug#855342: RFH: ntp

[Kurt Roeckx]

On Tue, Feb 21, 2017 at 02:10:09PM -0500, Peter Eisentraut wrote:
> On 2/19/17 07:01, Kurt Roeckx wrote:
> >>> I could really use some help with the ntp (network time protocol)
> >>> package. There have been various bugs filed, and I didn't have the
> >>> time to properly look at them and deal with them.
> >>>
> >>> It's currently team maintained, but I've been the only one doing
> >>> anything the past few years.
> >>
> >> I'm willing to help (both triaging bugs and updating the package).
> >>
> >> I would prefer the repository to be converted to git though, I'm much
> >> more experienced with git-buildpackage than the svn toolchain.
> > 
> > I wanted to give you access to the repository, but I see I'm only
> > a junior developer.
> > 
> > Peter,
> > 
> > Can you change the permissions on the alioth project?
> 
> done

I've given both Bernhard and Guus access to. If someone wants to
covert the repository to git, please feel free.


Kurt

Bug#853783: ping

[Brian Potkin]

On Thu 16 Feb 2017 at 22:38:59 +, Brian Potkin wrote:

> On Sat 11 Feb 2017 at 12:24:37 +0100, Didier 'OdyX' Raboud wrote:
> 
> Hello Svante and OdyX. Let's see if we can make some progress. Reports
> of this nature ('scanimage -L' working but scanning not taking place
> because of an I/O error) are not unknown. I've not seen anything which
> satisfactorily explains this behaviour, even on the sane-devel list.
>  
> > Le vendredi, 10 février 2017, 21.46:05 h CET Svante Signell a écrit :
> > > I view of the imminent release I'm upgrading the severity, since there has
> > > been no replies so far, really strange.
> > 
> > Please don't mix severities, release schedule and maintainer 
> > responsiveness, 
> > they have nothing to do with eachothers, at all. This bug is rightfully 
> > 'important', hereby downgrading. 
> 
> Agreed.
> 
> > > Do you not get reports about bugs via the bug tracker?
> > 
> > I do; it doesn't mean I have time to respond anything meaningful. Bug 
> > squasing 
> > can take some time, and hardware-related bugs are even harder: I don't have 
> > a 
> > scanner at home. It's only been _ten_ days too.
> 
> Scanning problems are not the easiest to debug, but a couple of aspects
> should be clarified. Firstly, there is no connection between the printing
> and scanning functions of a device. They are separate processes. One can
> work and the other not.
> 
> Secondly, the MFP M277DW does Bonjour broadcasting. All that is need to
> scan is sane-utils and libsane-hpaio (both without their recommended
> packages). Neither hplip nor avahi-daemon is required, It would be great
> if such an environment were set up to test the existence of the problem
> reported.
> 
> > > How come 3.16.7-1 works and not later versions?
> > 
> > I don't know, but here are the facts I could gather:
> > * there are no significant differences in the Debian packaging;
> > * the only relevant difference regarding hpaio is the addition of more 
> > models 
> > (but nothing related to your model) in scan/sane/hpaio.desc
> 
> Seeing log1 and log2 might provide a clue.
> 
>   SANE_DEBUG_DLL=128 scanimage -L 2>log1
>   SANE_DEBUG_DLL=128 scanimage > image.pnm 2>log2
> 
> My /etc/sane.d.dll.d/hplip has "hpaio". /etc/sane.d/dll.conf has only
> the line "net" (the other backends are not required). saned.conf is
> effectively empty.
> 
> > When you write that "3.16.7-1" works, is that the version of the Debian 
> > package? (I ask because that version is not an hplip Debian release).
> 
> Please clarify.
>  
> > Can you confirm using http://snapshot.debian.org/package/hplip/ until 
> > exactly 
> > which version it works, and from which version it fails?
> 
> Would be very useful.

YAP (Yet Another Ping :) )

--  
Brian.

Bug#855467: php7.0-snmp generates many warnings without snmp installed.

[Nishanth Aravamudan]

Package: php7.0
Followup-For: Bug #855467
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu zesty ubuntu-patch

Dear Maintainer,


I believe the following patch fixes snmp (and in theory any other
affected extensions, but there are none) to include its recommends.
Note, I think the resulting d/control file for most packages will have
an empty Recommends, but that seems ok and is dropped at build-time.

  * d/php-module.control.in: add Recommends to extension substitution.
Closes: #855467.


Thanks for considering the patch.

*** /tmp/tmpiZK86k/php7.0_7.0.16-3.debdiff
diff -Nru php7.0-7.0.16/debian/php-module.control.in 
php7.0-7.0.16/debian/php-module.control.in
--- php7.0-7.0.16/debian/php-module.control.in  2017-02-18 04:48:34.0 
-0800
+++ php7.0-7.0.16/debian/php-module.control.in  2017-02-21 11:20:55.0 
-0800
@@ -13,6 +13,7 @@
 Breaks: ${php-@ext@:Breaks}
 Conflicts: ${php-@ext@:Conflicts}
 Provides: ${php-@ext@:Provides}
+Recommends: ${php-@ext@:Recommends}
 Description: @description@ module for PHP
  This package provides the @description@ module(s) for PHP.
  .


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

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

-- 
Nishanth Aravamudan
Ubuntu Server
Canonical Ltd

Bug#855406: [thunderbird] commandline argument "-compose attachment" not recognized

[Carsten Schoenert]

Hello Jason,

On Tue, Feb 21, 2017 at 12:15:35PM -0600, Jason Crain wrote:
> Having this same problem with nautilus-sendto: https://bugs.debian.org/855449
> 
> nautilus-sendto calls icedove/thunderbird as "/usr/bin/icedove -compose
> attachment='file:///tmp/attachment'" when trying to email a file.  This
> no longer works with the new thunderbird.  However, after applying the
> patch in https://bugs.debian.org/855334, it will work if the command is
> changed to "/usr/bin/icedove -- -compose attachment='file:///tmp/attachment'".
> 
> Is this the recommended way to do it now?  Debian's icedove/thunderbird
> is going to now require "--" before any options?

yes, this assumption is correct.
But please don't use icedove in any helper script then.
/usr/bin/icedove comes from a transitional package that could be removed
every time by the user. It is of course working because /u/b/icedove is
symlinked to /u/b/thunderbird.

We need this '--' operator to seperate options for the wrapper from the
options for the thunderbird binary itself.

The patch from Daniel is applied to the current packaging work and will
be available with the next upload.

Regards
Carsten

Bug#837081: netbeans: Crashes due to assertion failure in GLib

[Markus Koschany]

On 21.02.2017 18:38, Jaime Torres wrote:
> commenting in /etc/java-8-openjdk/accessibility.properties the next line
> seems to work:
> 
> #assistive_technologies=org.GNOME.Accessibility.AtkWrapper
> 
> I figured it out cause I have a computer with netbeans working properly
> without any problem with that settings due to a time ago bug that
> preventing netbeans to start and another with a fresh debian
> installation, in the last one, netbeans closed sundenly when editing in
> php. Changing that in the new one seems to work and I have no unexpected
> close of netbeans.

Thank you for this valuable information. Eventually Netbeans also
crashed on my system when I worked on an HTML5 project and started to
use code completion. This happened three times now. I will try again
with assistive_technologies disabled.

Regards,

Markus




signature.asc
Description: OpenPGP digital signature

Bug#855655: Please provide documentation, manpage, --help

[martin f krafft]

also sprach Félix Sipma  [2017-02-22 05:18 +1300]:
> This part of the bug is fixed upstream, in 0.11.4. I've already
> prepared the package, I'll upload it as soon as stretch is out.

Thank you!

-- 
 .''`.   martin f. krafft  @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems


digital_signature_gpg.asc
Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Bug#855617: [Popcon-developers] Bug#855617: popularity-contest: /etc/cron.daily/popularity-contest can't locate strict.pm

[Bill Allombert]

On Mon, Feb 20, 2017 at 09:02:35PM +0100, Martin Dosch wrote:
> Package: popularity-contest
> Version: 1.64
> Severity: normal
> 
> Dear Maintainer,
> 
> the cronjob fails with following error:
> 
> "Can't locate strict.pm:   /usr/local/lib/x86_64-linux-
> gnu/perl/5.24.1/strict.pm: Permission denied at /usr/sbin/popularity-contest
> line 25.
> BEGIN failed--compilation aborted at /usr/sbin/popularity-contest line 25."

Hello Martin,

You have installed an alternative version of perl in /usr/local/

/usr/sbin/popularity-contest is run as the user 'nobody'.
If the user 'nobody' do not have permission to access it, then
/etc/cron.daily/popularity-contest fail.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 

Bug#855342: RFH: ntp

[Peter Eisentraut]

On 2/19/17 07:01, Kurt Roeckx wrote:
>>> I could really use some help with the ntp (network time protocol)
>>> package. There have been various bugs filed, and I didn't have the
>>> time to properly look at them and deal with them.
>>>
>>> It's currently team maintained, but I've been the only one doing
>>> anything the past few years.
>>
>> I'm willing to help (both triaging bugs and updating the package).
>>
>> I would prefer the repository to be converted to git though, I'm much
>> more experienced with git-buildpackage than the svn toolchain.
> 
> I wanted to give you access to the repository, but I see I'm only
> a junior developer.
> 
> Peter,
> 
> Can you change the permissions on the alioth project?

done

I'm sorry I haven't been of much use lately.  If I'm in the way of new
people taking over, let me know.

Bug#855799: install_packages: installing i386 packages on multiarch failed: unknown packages

[Thomas Lange]

I can confirm this bug. I also had this problem once, and I'm sure
it's in the new code. I'm pretty sure I can still fix this for the
stretch release.
-- 
regards Thomas

Bug#855585: multipath-tools 0.6.4-4 debdiff review

[Julien Cristau]

On Mon, Feb 20, 2017 at 20:20:34 +0530, Ritesh Raj Sarraf wrote:

> Dear Release Team,
> 
> Package: multipath-tools
> Version: 0.6.4-4
> Request: Pre-Approval
> 
> Please find attached a debdiff of 0.6.4-3 and 0.6.4-4.
> 
> These are minor changes, which should qualify for an upload exception. The new
> file additions are mostly autopkg tests related, which have no impact on the
> software. The other changes are good to have for Stretch.
> 
unblock requests (including pre-upload) go through the BTS against the
release.debian.org pseudo package.

Cheers,
Julien

Bug#855803: xserver-xorg-video-intel 2:2.99.917+git20161206-1 improve NEWS.Debian

[Marc MERLIN]

Package: xserver-xorg-video-intel
Version: 2:2.99.917+git20161206-1

This is a followup to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854934 
which because it's closed, my update seem to have gone nowwhere.

NEWS.Debian could definitely be improved. I did read it during upgrade
time, and what I read did not warn me that the new driver could just
stop being autodetected and not load at all as a result.

When read that message, it did not seem like it was the problem I was
having. Let me explain so that you can maybe improve the message?

1) I have been using modsetting for a long time (at least I
thought/think I was), so that part of the message did not seem
relevant to me.

2) you mention "triggers bugs" which read to me like "cause display problems"
not "The driver will fail to detect your hardware and not even load"
Note that average user will probably not even notice that the X server
fell back to vesa or framebuffer mode (I did however).
Could you add a blurb mentioning "this may cause the driver not to
detect your hardware and refuse to load, requiring the driver to be
manually loaded in xorg.conf" ?

3) you say "please file them against the xserver"
Can you add details on which package exactly?
xserver-xorg-core ?

Ultimately I'm still not super clear what's going on, the core server
talks to each driver to auto detect hardware and load the driver, or
not.
Is the bug in the core server where it somehow fails to load the intel
driver, or is the intel driver failing the initial autodetection,
requiring a force load to actually work?

As an extra suggestion, I know you said intel does not make releases of
the intel driver, which is a shame, but would you consider versioning
the driver on your side at least to reflect changes in abi
compatibility?
In this case, between 201602 and 201612, the driver changed abi version
and there was no way to apt-get install an older one. I had to manually 
fetch one from /var/cache/apt/archives/ on my system and be thankful
that I always keep old packages to revert in cases just like this one.
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems 
   what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901

Bug#855798: udev: MemoryDenyWriteExecute=yes should not be applied to udev plugins

[Mike Manning]

The problem binary is built using Go and is not part of the Debian distro.
We are in the process of assessing why the way Go has created this
executable and shared libs is infringing the W^X check during dynamic load.
I am not aware of any other type of binary causing the problem, and have
tested the plugin mechanism as working fine for test scripts and for
statically linked executables created by Go. The question is where
the boundary for security lies in terms of calling executables outside of
systemd and indeed the distro, vs the pain involved in distro-upgrade due
to the debuggability issues with this. Thanks, Mike

Bug#855798: udev: MemoryDenyWriteExecute=yes should not be applied to udev plugins

[Michael Biebl]

Am 21.02.2017 um 17:37 schrieb Marco d'Itri:
> On Feb 21, Mike Manning  wrote:
> 
>> Some executables outside of systemd are no longer run as plugins after 
>> an upgrade from Debian 8 to Debian 9 RC2, even though they should be 
> Do you have a list? I would like to better understand the impact of this 
> regression: we need to find the appropriate tradeoff between security 
> and compatibility.


ifmgrctl doesn't seem to be a binary/script shipped by Debian itself.

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



signature.asc
Description: OpenPGP digital signature

Bug#854341: libchado-perl: FTBFS: The following enviroment variables not detected: CHADO_DB_USERNAME

[Santiago Vila]

severity 854341 important
thanks

On Tue, Feb 21, 2017 at 06:25:05PM +0100, Andreas Tille wrote:

> I'm tempted to set the severity to this bug to normal/minor.  Could you
> please try again whether we can even close it?

I'm making this bug not RC in the meantime.

My current theory is that this is an artifact of the setup used by
Chris to build packages.

In my own setup, I use sbuild + eatmydata + overlayfs.

I can build most packages with such setup, but sometimes I get some
strange build failures which disappear when I stop using eatmydata or
overlayfs. An example:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842786

So I always have to disable those addons and try again after a build
failure to be sure that the build failure is real.

I believe that this build failure could be similar, because AFAIK
docker uses overlayfs internally.

But of course, I could be wrong.

Thanks.

Bug#855195: [mirror.dataone.nl] syncscript, does not remove old files file

[Peter Palfrader]

On Tue, 21 Feb 2017, [ mirror.dataone.nl ] - admin wrote:

> hey

Hola!

> we have changed to ftpsync now.
> 
> please confirm its working ok now please, thanks.

http://mirror.dataone.nl/debian/project/trace/mirror.dataone.nl only has
a date line.  Are you "manually" overwriting the trace file produced by
ftpsync?

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

Bug#733454: installation-reports: Install freezes after install selection from first menu

[Bryan Klumpp]

It looks like my issue is not the same as the one above.  Sorry, I thought
I was searching a list of stretch-only bugs and didn't notice the old date
on this one.  Also the vga=normal workaround does not work for me, so
probably not the same issue.  While I'm writing this though, I should note
that the Help screen did allow me to get to the boot prompt (seems like an
odd way to get to a boot prompt).  I tried boot: install vga=normal
fb=false hw-detect/startpcmcia=false bootkbd=es netcfg/disable_dhcp=true
desktop=kde but it still hangs immediately.  I also found
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838320, but in that case
the user seems to have gotten to the mirror selection screen so that
appears to be a different issue as well.  I guess I'll file a new bug
report.

Bug#851756: telegram-desktop/1.0.13-1

[Boyuan Yang]

When we are checking  a debian package, lintian is always the best friend.

Running lintian against telegram-desktop 1.0.12 gives the following 
information:

% lintian -E -I --pedantic ./*.dsc ./*.deb
P: telegram-desktop source: source-contains-autogenerated-visual-c++-file 
Telegram/Resources/winrc/Telegram.rc
P: telegram-desktop source: source-contains-autogenerated-visual-c++-file 
Telegram/Resources/winrc/Updater.rc
P: telegram-desktop source: source-contains-autogenerated-visual-c++-file 
Telegram/Resources/winrc/resource1.h
P: telegram-desktop source: debian-watch-may-check-gpg-signature
I: telegram-desktop: hardening-no-fortify-functions usr/bin/telegram-desktop
I: telegram-desktop: spelling-error-in-binary usr/bin/telegram-desktop catched 
caught
I: telegram-desktop: spelling-error-in-binary usr/bin/telegram-desktop ment 
meant
I: telegram-desktop: spelling-error-in-binary usr/bin/telegram-desktop Lenght 
Length
I: telegram-desktop: spelling-error-in-binary ... use --no-tag-display-limit 
to see all (or pipe to a file/program)
I: telegram-desktop: spelling-error-in-manpage usr/share/man/man1/telegram-
desktop.1.gz Allows to Allows one to
I: telegram-desktop: desktop-entry-contains-encoding-key usr/share/
applications/telegramdesktop.desktop:2 Encoding
I: telegram-desktop: desktop-entry-lacks-keywords-entry usr/share/
applications/telegramdesktop.desktop

This might be helpful when correcting spelling mistakes.

Another good tool is check-all-the-things [1], which is provided by Debian 
since Stretch. This tool checks enormous aspects and warns you in the output.

[1] https://tracker.debian.org/pkg/check-all-the-things

--
Sincerely,
Boyuan Yang

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

Bug#854706: RFS on hold

[Gianfranco Costamagna]

control: reopen -1
control: owner -1 !
control: tags -1 moreinfo


>I'd rather drop the upload of spyder-unittest/0.1.0-1 altogether and 
>submit spyder-unittest/0.1.1-1 (which I can prepare soon).


ack ok!

$ dcut ftp-master cancel -f spyder-unittest_0.1.0-1_amd64.changes
Uploading commands file to ftp.upload.debian.org (incoming: /pub/UploadQueue/)

You need a passphrase to unlock the secret key for
user: "Gianfranco Costamagna "
4096-bit RSA key, ID 4E9F5DD9, created 2014-09-14

Uploading locutus-1487701064.commands to ftp-master
ping again when ready then

Bug#855406: [thunderbird] commandline argument "-compose attachment" not recognized

[Jason Crain]

On Sun, Feb 19, 2017 at 12:24:51PM +0100, Carsten Schoenert wrote:
> without feedback it's obviously impossible to solve this report.
> I'll close the report then now. The command line option '-compose' is
> working so far with the fix from Daniel.

Having this same problem with nautilus-sendto: https://bugs.debian.org/855449

nautilus-sendto calls icedove/thunderbird as "/usr/bin/icedove -compose
attachment='file:///tmp/attachment'" when trying to email a file.  This
no longer works with the new thunderbird.  However, after applying the
patch in https://bugs.debian.org/855334, it will work if the command is
changed to "/usr/bin/icedove -- -compose attachment='file:///tmp/attachment'".

Is this the recommended way to do it now?  Debian's icedove/thunderbird
is going to now require "--" before any options?

Bug#855802: nvidia-kernel-dkms failed compile for stable kernel 4.10

[VDR User]

Package: nvidia-kernel-dkms
Version: 375.26-2

Driver fails to compile against current stable kernel 4.10:

In file included from
/var/lib/dkms/nvidia-current/375.26/build/common/inc/nv-linux.h:18:0,
 from
/var/lib/dkms/nvidia-current/375.26/build/nvidia/nv-frontend.c:13:
/var/lib/dkms/nvidia-current/375.26/build/common/inc/nv-mm.h: In
function ‘NV_GET_USER_PAGES_REMOTE’:
/var/lib/dkms/nvidia-current/375.26/build/common/inc/nv-mm.h:86:20:
error: too few arguments to function ‘get_user_pages_remote’
 return get_user_pages_remote(tsk, mm, start, nr_pages,
flags, pages, vmas);
^
In file included from
/var/lib/dkms/nvidia-current/375.26/build/common/inc/nv-pgprot.h:17:0,
 from
/var/lib/dkms/nvidia-current/375.26/build/common/inc/nv-linux.h:17,
 from
/var/lib/dkms/nvidia-current/375.26/build/nvidia/nv-frontend.c:13:
/usr/src/linux-4.10/include/linux/mm.h:1267:6: note: declared here
 long get_user_pages_remote(struct task_struct *tsk, struct mm_struct *mm,
  ^
/usr/src/linux-4.10/scripts/Makefile.build:294: recipe for target
'/var/lib/dkms/nvidia-current/375.26/build/nvidia/nv-frontend.o'
failed
make[3]: *** [/var/lib/dkms/nvidia-current/375.26/build/nvidia/nv-frontend.o]
Error 1
/usr/src/linux-4.10/Makefile:1490: recipe for target
'_module_/var/lib/dkms/nvidia-current/375.26/build' failed
make[2]: *** [_module_/var/lib/dkms/nvidia-current/375.26/build] Error 2
make[2]: Leaving directory '/usr/src/linux-4.10'
Makefile:150: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory '/usr/src/linux-4.10'
Makefile:81: recipe for target 'modules' failed
make: *** [modules] Error 2

This has been fixed in stable nvidia driver 378.13. Please update
nvidia-kernel-dkms to nvidia driver 378.13.

Thanks

Bug#848101: [Pkg-raspi-maintainers] Bug#848101: please add the package to armhf

[Michael Stapelberg]

On Tue, Feb 21, 2017 at 1:54 PM, gustavo panizzo  wrote:

> Hello
>
> Can you please publish this pkg in armhf? I have a bunch of RPI3 and RPI2
> deployed as small servers, running jessie/stretch, I don't think I'll ever
> upgrade them to arm64.
> The amount of RAM on the RPI3 does not justify to run arm64, I don't do
> math on them so I dont see the point of running a newer arch on them (all
> of them are remote, so reliability is important)
>

The key advantage for me is that the upstream Linux kernel can be used,
i.e. a kernel that is supported by Debian can be used. That alone justifies
using arm64 for me.


>
> I know Debian's kernel doesn't support RPI3 in armhf, but maybe it will at
> some point. And if Debian's kernel never


IIUC, this is unlikely because people aren’t actively working on
upstreaming the armhf patches.


> supports armhf on the RPI3 doesn't matter, I'll build the kernel but I
> won't have to build the firmware :)
>

The firmware isn’t built in Debian either: the Debian package uses the
pre-built files from https://github.com/raspberrypi/firmware and adds a
hook script to copy these files (plus the kernel image/dtbs/initrd and a
generated config) upon kernel/firmware changes.

The use-case you’re describing is something which I do not want to support.
The firmware (configuration at least) depends on the kernel build
configuration: obviously the CPU shouldn’t be put into arm64 mode when a
non-arm64 kernel is about to be booted, for example.

What you’re suggesting, hence, is to blow up the test/support matrix
significantly: in addition to being responsible for the kernel which is
included in Debian, we would also need to respond to potential problem
reports of users who use a kernel outside of Debian.

Such a change places an undue burden on the pkg-raspi team, which is
stretched very thin already.

All that said, as a practical workaround you can use dpkg
--add-architecture arm64 && apt update && apt install raspi3-firmware. Do
note that the package maintainers don’t endorse this and won’t support your
use-case.


>
>
> Regarding the config handling, I personally don't care. I want them to be
> pure Debian so I can manage them as my other servers.
>
>
> --
> 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333
>
> keybase: https://keybase.io/gfa
>
> ___
> Pkg-raspi-maintainers mailing list
> pkg-raspi-maintain...@lists.alioth.debian.org
> https://lists.alioth.debian.org/mailman/listinfo/pkg-raspi-maintainers
>



-- 
Best regards,
Michael

Bug#837081: netbeans: Crashes due to assertion failure in GLib

[Jaime Torres]

commenting in /etc/java-8-openjdk/accessibility.properties the next line seems 
to work:

#assistive_technologies=org.GNOME.Accessibility.AtkWrapper

I figured it out cause I have a computer with netbeans working properly without 
any problem with that settings due to a time ago bug that preventing netbeans 
to start and another with a fresh debian installation, in the last one, 
netbeans closed sundenly when editing in php. Changing that in the new one 
seems to work and I have no unexpected close of netbeans.

Bug#855554: unblock: debian-goodies/0.69

[Emilio Pozuelo Monfort]

On 20/02/17 02:58, Axel Beckert wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please unblock the just uploaded debian-goodies version 0.69. (Not yet
> accepted due to a just started dinstall run, but should be accepted
> within the next hour or so.)
> 
> It fixes a regression from the Python 3 conversion in 0.65. It only
> happens with a specific option, but causes a syntax error if that
> option is used, i.e. makes that option unusable.
> 
> Unfortunately I didn't notice the according bug report when preparing
> the last upload before the freeze and only a second bug report for the
> same issue made me aware of it.
> 
> Full debdiff:
> 
> diff -Nru debian-goodies-0.68/checkrestart debian-goodies-0.69/checkrestart
> --- debian-goodies-0.68/checkrestart  2017-01-21 16:27:32.0 +0100
> +++ debian-goodies-0.69/checkrestart  2017-02-20 02:28:58.0 +0100
> @@ -126,7 +126,8 @@
>  checkroot()
>  
>  for f in blacklistFiles:
> -for line in file(f, "r"):
> +blacklistFile = open(f, 'r')
> +for line in blacklistFile.readlines():
>  if line.startswith("#"):
>  continue
>  blacklist.append(re.compile(line.strip()))

BTW you don't seem to close those files ever. You may want to call f.close(), or
use the with statement.

Cheers,
Emilio

Bug#837067: Help requested: Packages which FTBFS randomly

[Santiago Vila]

On Tue, Feb 21, 2017 at 11:21:30AM -0600, Jeff Epler wrote:
> On Tue, Feb 21, 2017 at 05:32:34PM +0100, Santiago Vila wrote:
> > On Fri, 17 Feb 2017, Jeff Epler wrote:
> > > Using a fresh 1CPU / 1GB x86 system on digitalocean's NYC region, 
> > > upgraded to
> > > debian testing, I tried sbuilding libsecret.  So far, 2/2 builds failed.
> > > 
> > > # grep ^FAIL libsecret_*.build
> > > libsecret_i386-2017-02-17T14:42:53Z.build:FAIL: test-collection 18 
> > > /collection/delete-sync
> > > libsecret_i386-2017-02-17T14:50:00Z.build:FAIL: test-collection 18 
> > > /collection/delete-sync
> > 
> > Thanks a lot. Can you try a few more times?
> 
> I ended up leaving that machine up for 12 builds total.  they all failed.  
> I've since recycled the instance.

Ok, I think that's enough to prove that the reason for this is not a
misconfiguration in my machines.

(I tried 434 times in total and it failed 434 times).

Debian GNOME Maintainers: Do you plan to fix this for stretch?

Thanks.

Bug#748716: Bug#855475: libreswan: [INTL:nl] Dutch translation of debconf messages

[Daniel Kahn Gillmor]

On Tue 2017-02-21 10:47:25 -0500, Frans Spiesschaert wrote:
> You may try filing a bug report against the pseudo-package debian-i18n
> and/or sending an email to debian-i...@lists.debian.org.

Looks like the problem that caused #855475 is already reported as bugs
#748716, #750810, #751685, #761092, #766265, if i'm to believe their
title "l10n scripts should not look at upstream debian/ …"

 --dkg

Bug#855606: sqrt() regression on powerpc/jessie

[James Cloos]

It may be a bit more informative to add:

   printf("0X %A\n", r);

to that main() to see exactly what is different between the two.

The only ppc I have access to are those in the gcc farm and those (the
online ones anyway) only run fedora and aix, so I cannot test it
myself.

Except that everything else reports:

  0X 0X1.C48C6001F0ACP+3

-JimC
-- 
James Cloos  OpenPGP: 0x997A9F17ED7DAEA6

Bug#854341: libchado-perl: FTBFS: The following enviroment variables not detected: CHADO_DB_USERNAME

[Andreas Tille]

Hi Chris,s

I'm tempted to set the severity to this bug to normal/minor.  Could you
please try again whether we can even close it?

Kind regards

   Andreas.

On Thu, Feb 16, 2017 at 01:55:53AM +0100, Santiago Vila wrote:
> Hi.
> 
> It builds ok for me on eight different autobuilders,
> using sbuild on a sid chroot.
> 
> Chris, I would try with sbuild and without docker.
> 
> Thanks.
> 
> 

-- 
http://fam-tille.de

Bug#855801: zfs-mount.service / zfs.target should be WantedBy=local-fs.target, not multi-user.target

[Christopher Martin]

Package: zfsutils-linux
Version: 0.6.5.9-2

Currently, the zfs-mount.service is started through the zfs.target,
which is itself in turn WantedBy=multi-user.target. This happens after
local-fs.target is reached (which is when local file systems are
expected to be mounted). As a result, there is no guarantee that a
daemon or other service, many of which are also started through
multi-user.target, will be able to see ZFS mounts when they launch.
This can cause problems (e.g. a DLNA server that wants to serve files
stored on a ZFS array).

Instead, I would suggest that zfs-mount.service or the zfs.target
(whichever makes most sense) be WantedBy=local-fs.target, thereby
mounting ZFS along with all the other local filesystems. That way,
daemons etc. started later, through multi-user.target, will reliably
be able see the system's ZFS mounts when they launch.

Thanks,

Christopher Martin

Bug#837067: Help requested: Packages which FTBFS randomly

[Jeff Epler]

On Tue, Feb 21, 2017 at 05:32:34PM +0100, Santiago Vila wrote:
> On Fri, 17 Feb 2017, Jeff Epler wrote:
> > Using a fresh 1CPU / 1GB x86 system on digitalocean's NYC region, upgraded 
> > to
> > debian testing, I tried sbuilding libsecret.  So far, 2/2 builds failed.
> > 
> > # grep ^FAIL libsecret_*.build
> > libsecret_i386-2017-02-17T14:42:53Z.build:FAIL: test-collection 18 
> > /collection/delete-sync
> > libsecret_i386-2017-02-17T14:50:00Z.build:FAIL: test-collection 18 
> > /collection/delete-sync
> 
> Thanks a lot. Can you try a few more times?

I ended up leaving that machine up for 12 builds total.  they all failed.  I've 
since recycled the instance.

Jeff