Bug#815461: ping

2017-02-15 Thread Dima Kogan

Uwe Hermann  writes:

> On Sat, Feb 11, 2017 at 05:34:37PM -0800, Dima Kogan wrote:
>> Hi. Do you need help? Any objections if this package moved to
>> pkg-electronics for team maintenance?
>
> I've officially RFA'd all sigrok-related packages recently and I'm looking
> for new maintainer(s) indeed.
>
> Details:
> https://lists.debian.org/debian-devel/2017/01/msg00675.html
>
> Please get in touch with the people I CC'd (who have also potentially
> shown interest in sigrok Debian package maintenance) and coordinate
> who wants / plans to adopt which package(s) and/or if and how
> group-maintenance via pkg-electronics or otherwise is possible.

Uwe: thanks for the upstream development and the package maintenance!

Rest of you: does anybody have any tangible progress to share? If not,
I'll get the new release out in a week or two. It's really too bad we
missed the stretch cutoff, but better late than never.

dima


signature.asc
Description: PGP signature


Bug#854436:

2017-02-15 Thread Arturo Borrero Gonzalez
While I still think that tcp_wrappers are something to left behind at
this point,
I agree that the issue is somewhere else and has nothing to do with slapd.

I found a way of overcoming this issue by tuning system resouce limits
for the slapd process.
Read more about this here:
http://ral-arturo.org/2017/02/14/about-process-limits.html

If the link is down and someone is looking for this in the future: use
prlimit(1) and read getrlimit(2).

sorry for the nose, best regards



Bug#855186: keepass2: ctrl+c ctrl+v doesn't work in openjdk8 apps

2017-02-15 Thread benoit barthelet
Package: keepass2
Version: 2.28+dfsg-1
Severity: important

Dear Maintainer,

Upgrading keepass2 to 2.35 leads to this issue, 2.28 doesnt have.
When I'm in pycharm for instance with keepass 2.35 opened, I cant ctrl+c
ctrl+v, nothing is pasted from clipboard. If I close pycharm the copy-paste
works fine.
I can only paste if I ctrl+c twice.

If I use keepass2 2.28 there's no issue.

It seems there is a conflict between mono and openjdk on clipboard handling, at
least it has been reported here
http://askubuntu.com/questions/873815/kubuntu-16-04-lts-and-phpstorm-2016-3-clipboard-issue-cannot-paste

So there might be a regression between 2.28 and 2.35


-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (990, 'testing'), (980, 'stable-updates'), (980, 'stable'), (90, 
'experimental'), (90, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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)

Versions of packages keepass2 depends on:
ii  libmono-corlib4.5-cil4.6.2.7+dfsg-1
ii  libmono-system-drawing4.0-cil4.6.2.7+dfsg-1
ii  libmono-system-security4.0-cil   4.6.2.7+dfsg-1
ii  libmono-system-windows-forms4.0-cil  4.6.2.7+dfsg-1
ii  libmono-system-xml4.0-cil4.6.2.7+dfsg-1
ii  libmono-system4.0-cil4.6.2.7+dfsg-1
ii  libx11-6 2:1.6.4-3
ii  mono-runtime 4.6.2.7+dfsg-1

Versions of packages keepass2 recommends:
ii  xsel  1.2.0-2

Versions of packages keepass2 suggests:
pn  keepass2-doc  
pn  mono-dmcs 
pn  xdotool   

-- no debconf information



Bug#855130: med-fichier: MED library is not compatible with HDF5 1.10

2017-02-15 Thread Gilles Filippini

Control: tags -1 + patch

On 2017-02-14 14:37, Gilles Filippini wrote:

Source: med-fichier
Version: 3.0.6-11
Severity: grave
Justification: renders package unusable

Hi,

From the Salome Platform support forum [1]:


Problems with Salome and Code Saturne in Debian
Posted by Elektrix at January 03. 2017

Hello all,

I'm trying to set up a CFD case with Salome, export the mesh in a MED 
file and then process it with Code Saturne. CS doesn't read the MED 
file and gives the error in the preprocessing stage:


_MEDdatasetRd.c [139] : Erreur à la lecture du dataset
_MEDdatasetRd.c [139] : COO
HDF5-DIAG: Error detected in HDF5 (1.10.0-patch1) thread 0:
  #000: ../../../src/H5Dio.c line 170 in H5Dread(): can't read data
major: Dataset
minor: Read failed
  #001: ../../../src/H5Dio.c line 418 in H5D__read(): unable to set up 
type info

major: Dataset
minor: Unable to initialize object
  #002: ../../../src/H5Dio.c line 953 in H5D__typeinfo_init(): not a 
datatype

major: Invalid arguments to routine
minor: Inappropriate type
_MEDdatasetRd.c [142] : _dataset = 2
_MEDdatasetRd.c [143] : _i = 0
_MEDdatasetRd.c [144] : (*filter).memspace[_i] = 2
_MEDdatasetRd.c [145] : (*filter).diskspace[_i] = 3
_MEDmeshAdvancedRd30.c [462] : Erreur à la lecture du dataset
_MEDmeshAdvancedRd30.c [462] :
_MEDmeshAdvancedRd30.c [463] : meshname = "Mesh_water"
_MEDmeshAdvancedRd30.c [463] : numit = -1
_MEDmeshAdvancedRd30.c [463] : numdt = -1
_MEDmeshAdvancedRd30.c [463] : _datagroupname2 = "NOE"
_MEDmeshAdvancedRd30.c [464] : _datagroupname3 = ""
_MEDmeshAdvancedRd30.c [464] : _profilename = 
"MED_NO_PROFILE_INTERNAL"


The problem can be because I installed Salome from the 
SALOME-7.6.0-DB07.tgz archive whilst Code Saturne is a Debian package 
and is installed via the Debian package system which is much easier 
than installing the original package. So the med and hdf5 libraries of 
CS come from the Debian repositories. I can't use newer versions of 
Salome (7.7.1 or 7.8.0) as they produce MED3.1 files but my CS reads 
only MED3.0 files.


The details of my machine:

Debian stretch (testing) on AMD64

Salome 7.6.0 from SALOME-7.6.0-DB07.tgz

Code Saturne 4.3 Debian package

libmed 3.0.6-10.1 Debian package

hdf5 1.10.0 Debian package

Not knowing if this problem comes from how I create the mesh I tried 
to run one of the test cases from the Code Saturne tutorials but ran 
into other problems.


If you need any other information pleas let me know. Any hint on how 
to go further is very welcome.


Best regards

Elektrix





Re: Problems with Salome and Code Saturne in Debian
Posted by Yvan Fournier at Monday 16:21

Hello,

I was contacted by the Debian maintainer relative to this, so it seems 
the bug was reported.


The root problem is that the MED library is not compatible with HDF5 
1.10 yet. So reverting to HDF5 1.8 as indicated is the solution for 
now, but the better solution would be for MED to handle compatibility 
with both HDF5 1.8 and HDF5 1.10 (or at least 1.10 for future 
versions).


Best regards,

Yvan


[1] http://www.salome-platform.org/forum/forum_9/122041955


Patch proposal attached.
Thanks,

_gdiff -Nru med-fichier-3.0.6/debian/changelog med-fichier-3.0.6/debian/changelog
--- med-fichier-3.0.6/debian/changelog	2016-10-30 18:06:27.0 +0100
+++ med-fichier-3.0.6/debian/changelog	2017-02-13 18:02:35.0 +0100
@@ -1,3 +1,11 @@
+med-fichier (3.0.6-10.2) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * New patch type_hdf_should_be_hid_t.patch fixing HDF5 1.10 support
+for the C API (closes: #855130)
+
+ -- Gilles Filippini   Mon, 13 Feb 2017 18:02:35 +0100
+
 med-fichier (3.0.6-10.1) unstable; urgency=medium
 
   * Non-maintainer upload
diff -Nru med-fichier-3.0.6/debian/patches/series med-fichier-3.0.6/debian/patches/series
--- med-fichier-3.0.6/debian/patches/series	2016-10-20 21:58:54.0 +0200
+++ med-fichier-3.0.6/debian/patches/series	2017-02-13 18:02:35.0 +0100
@@ -2,3 +2,4 @@
 hdf5_link.patch
 clang-ftbfs.diff
 fix-fid-type-in-medequivinfo.patch
+type_hdf_should_be_hid_t.patch
diff -Nru med-fichier-3.0.6/debian/patches/type_hdf_should_be_hid_t.patch med-fichier-3.0.6/debian/patches/type_hdf_should_be_hid_t.patch
--- med-fichier-3.0.6/debian/patches/type_hdf_should_be_hid_t.patch	1970-01-01 01:00:00.0 +0100
+++ med-fichier-3.0.6/debian/patches/type_hdf_should_be_hid_t.patch	2017-02-13 18:02:35.0 +0100
@@ -0,0 +1,152 @@
+Index: med-fichier-3.0.6/src/2.3.6/hdfi/MEDdatasetNumLire232.c
+===
+--- med-fichier-3.0.6.orig/src/2.3.6/hdfi/MEDdatasetNumLire232.c
 med-fichier-3.0.6/src/2.3.6/hdfi/MEDdatasetNumLire232.c
+@@ -71,8 +70,8 @@ void  _MEDdatasetNumLire232(int dummy,..
+   med_size   start_mem[1],start_data[1],*pflmem=0,*pfldsk=0;
+   med_size   stride[1],count[1],pcount[1],size[1],pflsize[1];
+   med_errret;
+-  inti,j,index,type_hdf;
+-  hid_t  data

Bug#855187: network-manager: Connection to WPA2 enterprise network (eduroam) is dysfunctional

2017-02-15 Thread Ralf Jung
Package: network-manager
Version: 1.6.0-1
Severity: normal

Dear Maintainer,

when I try to connect to the eduroam network of my institution, the resulting
connection does not actuall work.  NetworkManager considers the network to be
"connected" if I enter my credentials correctly (whereas it times out during
connection if I do not).  I even obtain an IPv4 address via DHCP.  However, the
resulting connection does not work: I cannot even ping my router ("Destination
Host Unreachable"), let alone anything on the internet.  I have two eduroam
logins, and this issues occurs with both of them.  At the same time, the network
works fine with my phone and for everyone else around me, so I am pretty sure
the network itself is not at fault here.  This started happening some time
during the last two or three weeks -- previously, the network worked fine.
Other WiFi networks (WPA2 Personal) work mostly fine (the driver is sometimes
making trouble and restarting the device during association, but then NM doesn't
even get to say that a connection was established, let alone obtain an IP via
DHCP).

Here's a log from connecting to eduroam:

Feb 15 09:49:37 r-schwarzschild NetworkManager[947]:   [1487148577.0743] 
device (wlp6s0): Activation: starting connection 'eduroam (MPI)' 
(54e9f63c-67f0-457a-84cb-99739079a842)
Feb 15 09:49:37 r-schwarzschild NetworkManager[947]:   [1487148577.0747] 
audit: op="connection-activate" uuid="54e9f63c-67f0-457a-84cb-99739079a842" 
name="eduroam (MPI)" pid=4988 uid=1000 result="success"
Feb 15 09:49:37 r-schwarzschild NetworkManager[947]:   [1487148577.0752] 
device (wlp6s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Feb 15 09:49:37 r-schwarzschild NetworkManager[947]:   [1487148577.0755] 
manager: NetworkManager state is now CONNECTING
Feb 15 09:49:37 r-schwarzschild NetworkManager[947]:   [1487148577.0792] 
device (wlp6s0): set-hw-addr: reset MAC address to 94:E9:79:7B:A3:43 (preserve)
Feb 15 09:49:37 r-schwarzschild kernel: IPv6: ADDRCONF(NETDEV_UP): wlp6s0: link 
is not ready
Feb 15 09:49:37 r-schwarzschild NetworkManager[947]:   [1487148577.1075] 
device (wlp6s0): supplicant interface state: disconnected -> disabled
Feb 15 09:49:37 r-schwarzschild NetworkManager[947]:   [1487148577.1080] 
device (wlp6s0): state change: prepare -> config (reason 'none') [40 50 0]
Feb 15 09:49:37 r-schwarzschild NetworkManager[947]:   [1487148577.1082] 
device (wlp6s0): Activation: (wifi) access point 'eduroam (MPI)' has security, 
but secrets are required.
Feb 15 09:49:37 r-schwarzschild NetworkManager[947]:   [1487148577.1082] 
device (wlp6s0): state change: config -> need-auth (reason 'none') [50 60 0]
Feb 15 09:49:37 r-schwarzschild NetworkManager[947]:   [1487148577.1222] 
device (wlp6s0): supplicant interface state: disabled -> disconnected
Feb 15 09:49:37 r-schwarzschild NetworkManager[947]:   [1487148577.1246] 
device (wlp6s0): state change: need-auth -> prepare (reason 'none') [60 40 0]
Feb 15 09:49:37 r-schwarzschild NetworkManager[947]:   [1487148577.1249] 
device (wlp6s0): state change: prepare -> config (reason 'none') [40 50 0]
Feb 15 09:49:37 r-schwarzschild NetworkManager[947]:   [1487148577.1250] 
device (wlp6s0): Activation: (wifi) connection 'eduroam (MPI)' has security, 
and secrets exist.  No new secrets needed.
Feb 15 09:49:37 r-schwarzschild NetworkManager[947]:   [1487148577.1251] 
Config: added 'ssid' value 'eduroam'
Feb 15 09:49:37 r-schwarzschild NetworkManager[947]:   [1487148577.1251] 
Config: added 'scan_ssid' value '1'
Feb 15 09:49:37 r-schwarzschild NetworkManager[947]:   [1487148577.1251] 
Config: added 'key_mgmt' value 'WPA-EAP'
Feb 15 09:49:37 r-schwarzschild NetworkManager[947]:   [1487148577.1251] 
Config: added 'password' value ''
Feb 15 09:49:37 r-schwarzschild NetworkManager[947]:   [1487148577.1251] 
Config: added 'eap' value 'TTLS'
Feb 15 09:49:37 r-schwarzschild NetworkManager[947]:   [1487148577.1251] 
Config: added 'fragment_size' value '1266'
Feb 15 09:49:37 r-schwarzschild NetworkManager[947]:   [1487148577.1251] 
Config: added 'phase2' value 'auth=PAP'
Feb 15 09:49:37 r-schwarzschild NetworkManager[947]:   [1487148577.1251] 
Config: added 'ca_cert' value '/home/r//MPI_eduroam_cert.crt'
Feb 15 09:49:37 r-schwarzschild NetworkManager[947]:   [1487148577.1252] 
Config: added 'identity' value ''
Feb 15 09:49:37 r-schwarzschild NetworkManager[947]:   [1487148577.1252] 
Config: added 'anonymous_identity' value 'anonym...@mpi-sws.org'
Feb 15 09:49:37 r-schwarzschild NetworkManager[947]:   [1487148577.1252] 
Config: added 'bgscan' value 'simple:30:-65:300'
Feb 15 09:49:37 r-schwarzschild NetworkManager[947]:   [1487148577.1252] 
Config: added 'proactive_key_caching' value '1'
Feb 15 09:49:37 r-schwarzschild NetworkManager[947]:   [1487148577.1258] 
sup-iface[0x55a89a403830,wlp6s0]: config: set interface ap_scan to 1
Feb 15 09:49:37 r-schwarzschild NetworkManager[947]:   [1487148577.1324] 
device (wlp6s0): supplicant interface state: disconnect

Bug#847069: mirror submission for debian.e4a.it

2017-02-15 Thread NOC
Fixed, bug on script for cron sync...

Sorry

> Il giorno 14 feb 2017, alle ore 12:50, Peter Palfrader  ha 
> scritto:
> 
> On Tue, 14 Feb 2017, NOC wrote:
> 
>> Hi,
>> we corrected the tracefiles for debian.e4a.it.
> 
> http://debian.e4a.it/debian/project/trace/debian.e4a.it looks to be
> empty.
> 
> You are using ftpsync to sync the mirror, correct?
> http://debian.e4a.it/debian/project/ftpsync/ftpsync-current.tar.gz
> 
> -- 
>|  .''`.   ** Debian **
>  Peter Palfrader   | : :' :  The  universal
> https://www.palfrader.org/ | `. `'  Operating System
>|   `-https://www.debian.org/



Bug#618606: git-daemon: Still happening, what to do ?

2017-02-15 Thread Xavier Bestel
Package: git-daemon-run
Version: 1:2.11.0-2
Followup-For: Bug #618606


Hi,

After an upgrade, git-daemon refuses to run with
fail: git-daemon: runsv not running
No amount of reinstalling or reconfiguring fixes this.

Cheers,
Xav


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

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

Versions of packages git-daemon-run depends on:
ii  adduser  3.115
ii  git  1:2.11.0-2
ii  runit2.1.2-9

git-daemon-run recommends no packages.

git-daemon-run suggests no packages.

-- no debconf information



Bug#854997: Some info on reproducing the case

2017-02-15 Thread Christian Ehrhardt
Hi,
I was just about to report to pkg-postgresql-pub...@lists.alioth.debian.org
when I found that Jeremy already opened a bug. I just started on this, but
still I wanted to share the bit I had.

I hit it while trying to prepare the recent postgres mircorelease for
Ubuntu.
At least the issue seems 100% reproducible with autopkgtests and locally as
well.

The error comes down to
pg_buildext installcheck
[...]
test tablespace   ... FAILED
[...]
ERROR:  could not create unique index "idx_badindex_n"
DETAIL:  Key (n)=(10) is duplicated.
STATEMENT:  CREATE UNIQUE INDEX CONCURRENTLY idx_badindex_n ON tbl_badindex
(n);

Jeremy already pointed out the issue is not specific to Ubuntu, Debian hits
the same in debci with the recent 9.6.2 update, see [1].

As mentioned before the case can be reproduced easily in any Debian/Ubuntu
environment with pg-repack, example:
# prep current debian system
 $ lxc launch  95fba011e3ad debiansid-postgres-fail-stableupdate
 $ lxc exec debiansid-postgres-fail-stableupdate bash
# get packages and source
 $ apt-get install postgresql-9.6-repack postgresql-server-dev-all dpkg-dev
 $ echo "deb-src http://httpredir.debian.org/debian sid main" >>
/etc/apt/sources.list
 $ apt-get update
 $ apt-get source pg-repack
# prep test env
 $ cd pg-repack-1.3.4/
 $ mkdir /tmp/pg-repack-tablespace
 $ chown postgres:postgres /tmp/pg-repack-tablespace
# these two commands you can iterate on when debugging
 $ service postgresql stop
 $ pg_buildext installcheck

On Ubuntu you'd need the ppa [2] I currently test on to trigger it - also
Yakkety is the only releases which has pr-repack atm.

[1]: https://ci.debian.net/packages/p/pg-repack/unstable/amd64/
[2]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2470


-- 
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd


Bug#855189: mirror listing update for mirrors.xservers.ro

2017-02-15 Thread Tehnic Department
Package: mirrors
Severity: minor
User: mirr...@packages.debian.org
Usertags: mirror-list

Submission-Type: update
Site: mirrors.xservers.ro
Type: leaf
Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x
Archive-http: /debian/
CDImage-http: /debian-cd/
Old-http: /debian/
Archive-upstream: ftp.ro.debian.org
CDImage-upstream: ftp.ro.debian.org
Updates: twice
Maintainer: Tehnic Department 
Country: RO Romania
Location: Bucharest
Sponsor: https://xservers.ro https://xservers.ro



Trace Url: http://mirrors.xservers.ro/debian/project/trace/ftp-master.debian.org
Trace Url: http://mirrors.xservers.ro/debian/project/trace/mirrors.xservers.ro
Trace Url: http://mirrors.xservers.ro/debian-cd/project/trace/cdimage.debian.org
Trace Url: 
http://mirrors.xservers.ro/debian-cd/project/trace/mirrors.xservers.ro
Trace Url: http://mirrors.xservers.ro/debian/project/trace/archive.debian.org
Trace Url: http://mirrors.xservers.ro/debian/project/trace/mirrors.xservers.ro



Bug#855188: mirror submission for mirrors.xservers.ro

2017-02-15 Thread Tehnic Department
Package: mirrors
Severity: wishlist
User: mirr...@packages.debian.org
Usertags: mirror-submission

Submission-Type: new
Site: mirrors.xservers.ro
Type: leaf
Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x
Archive-http: /debian/
CDImage-http: /debian-cd/
Old-http: /debian/
Archive-upstream: ftp.ro.debian.org
CDImage-upstream: ftp.ro.debian.org
Updates: twice
Maintainer: Tehnic Department 
Country: RO Romania
Location: Bucharest
Sponsor: https://xservers.ro https://xservers.ro



Trace Url: http://mirrors.xservers.ro/debian/project/trace/ftp-master.debian.org
Trace Url: http://mirrors.xservers.ro/debian/project/trace/mirrors.xservers.ro
Trace Url: http://mirrors.xservers.ro/debian-cd/project/trace/cdimage.debian.org
Trace Url: 
http://mirrors.xservers.ro/debian-cd/project/trace/mirrors.xservers.ro
Trace Url: http://mirrors.xservers.ro/debian/project/trace/archive.debian.org
Trace Url: http://mirrors.xservers.ro/debian/project/trace/mirrors.xservers.ro



Bug#850421: libsqlcipher0: qTox segfaults with distro provided libsqlcipher0

2017-02-15 Thread Hans-Christoph Steiner
sqlcipher 3.4.1 was just released, and it supports OpenSSL 1.1.  I think
the best approach here is to try to get 3.4.1 into stretch and remove
the hacky patches for OpenSSL 1.1 that we currently have.  I don't
currently have time to take that project on, but I'm happy to answer
questions for anyone who can.



Bug#855191: guile-2.0 FTCBFS for tilegx

2017-02-15 Thread Helmut Grohne
Source: guile-2.0
Tags: patch upstream
User: helm...@debian.org
Usertags: rebootstrap

guile-2.0 fails to cross build for tilegx, because its target.scm file
lacks the required definitions for tilegx. I am attaching a patch that
adds the relevant definitions and thus makes guile-2.0 cross build
successfully for tilegx. Please consider applying it.

I also ask Chris Metcalf (X-Debbugs-Cced, porter from Mellanox) to
review and forward the patch to guile upstream.

Helmut
--- a/module/system/base/target.scm
+++ b/module/system/base/target.scm
@@ -65,7 +65,7 @@
   (cond ((string-match "^i[0-9]86$" cpu)
  (endianness little))
 ((member cpu '("x86_64" "ia64"
-   "powerpcle" "powerpc64le" "mipsel" "mips64el" "nios2" "sh4" "alpha"))
+   "powerpcle" "powerpc64le" "mipsel" "mips64el" "nios2" "sh4" "alpha" "tilegx"))
  (endianness little))
 ((member cpu '("sparc" "sparc64" "powerpc" "powerpc64" "spu"
"mips" "mips64" "m68k" "s390x"))
@@ -105,7 +105,7 @@
   ((string-match "64$" cpu) 8)
   ((string-match "64_?[lbe][lbe]$" cpu) 8)
   ((member cpu '("sparc" "powerpc" "mips" "mipsel" "nios2" "m68k" "sh4")) 4)
-  ((member cpu '("s390x" "alpha")) 8)
+  ((member cpu '("s390x" "alpha" "tilegx")) 8)
   ((string-match "^arm.*" cpu) 4)
   (else (error "unknown CPU word size" cpu)
 


Bug#855188: mirror submission for mirrors.xservers.ro

2017-02-15 Thread Peter Palfrader
Control: tags -1 moreinfo

Hi!

Thanks for your (re-)submission.  I have one question, two issues, and
one suggestion:

On Wed, 15 Feb 2017, Tehnic Department wrote:

> Maintainer: Tehnic Department 
> Maintainer: Tehnic Department 

Question:

o We should use the noc@ address in our file?

> Archive-http: /debian/

Issues:

o The tracefile
  http://mirrors.xservers.ro/debian/project/trace/mirrors.xservers.ro
  suggests that the ftpsync version you are using is very old.  Please upgrade.
  http://mirrors.xservers.ro/debian/project/ftpsync/ftpsync-current.tar.gz

> Updates: twice

Please run the update 4 times a day (every 6 hours) to match the update
frequency of the archive.  Consult the upstream trace file on what a
good time offset might be:
  http://mirrors.xservers.ro/debian/project/trace/ftp.upcnet.ro

Suggestion:

> Archive-upstream: ftp.ro.debian.org
> CDImage-upstream: ftp.ro.debian.org

o we recommend mirrors not sync directly from service aliases such as
  ftp..debian.org (only http for /debian/ is guaranteed to be
  available at ftp..d.o sites).  Maybe change your config to sync
  from  (which is the same host)?

  Currently, ftp.ro.debian.org is an alias for ftp.upcnet.ro - maybe you
  want to mirror from that ftp.upcnet.ro.

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



Bug#855188: [tehnic #KBM-940-37601]: debian mirror mirrors.xservers.ro

2017-02-15 Thread Departamentul Tehnic xServers
Hello,

We use ftpsync, but because we have a option in config(--max-delete) the sync 
stop.
So, i eliminate that option and now the mirror update without error :-)
I use the link and added the mirror as a new, because message say that "I am 
removing this mirror".

Thanks for help and have a nice day.


-- 
Cristian Opriț
Departamentul Tehnic xServers

Tehnic: +40-755-038-875 teh...@xservers.ro
Comercial: +40-749-266-266 comerc...@xservers.ro
Fax: +40-212-120-844

Ticket History
===


Peter Palfrader (Client) Posted On: 14 Feb 2017 11:24

===
On Tue, 14 Feb 2017, Departamentul Tehnic xServers wrote:

>> Should you wish to restore the service and be included again in our list
>> of mirrors, please submit the mirror anew at
>> https://www.debian.org/mirror/submit

> The link https://www.debian.org/mirror/submit it give me error 500 when it 
> try to submit.
> Please verify in order to update the information for mirrors.xservers.ro.

My bad, sorry - my perl is too rusty it seems.  I think I have now fixed
the script, please try it again after addressing the issues mentioned
below.  If there are more problems, please do let me know!

Looking at your mirror manually, I noticed.

o You seem to not be using ftpsync.  At least
  http://mirrors.xservers.ro/debian/project/trace/ has no recent
  tracefile named "mirrors.xservers.ro".  It has a localhost one, but
  that is ancient.

  You can find ftpsync at
  http://mirrors.xservers.ro/debian/project/ftpsync/ftpsync-current.tar.gz

There might be more items, but without a tracefile it'll be more
difficult to check.  Looking forward to your submission.

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





Opriț Cristian (Staff) Posted On: 14 Feb 2017 11:06

===
Hello,

The link https://www.debian.org/mirror/submit it give me error 500 when it try 
to submit.
Please verify in order to update the information for mirrors.xservers.ro.

Thank you, 

-- 
Cristian Opriț
Departamentul Tehnic xServers

Tehnic: +40-755-038-875 teh...@xservers.ro
Comercial: +40-749-266-266 comerc...@xservers.ro
Fax: +40-212-120-844







Ticket Details
-
Ticket ID: KBM-940-37601
Department: Dept Tehnic
Type: Sesizare tehnica
Status: Closed
Priority: Normal

Support Center: https://client.xservers.ro/index.php?


Bug#854899: procps: /bin/ps needs /usr/lib/x86_64-linux-gnu/liblz4.so.1 so separate /usr fails

2017-02-15 Thread Craig Small
reassign 854899 libsystemd0
forcemerge 845480 854899
thankyou

Hi Paul,
This is a duplicate of #845480 which is against libsystemd0 and is
tagged wontfix. It's not a direct link but via libsystemd0.

 - Craig
-- 
Craig Small (@smallsees)  https://dropbear.xyz/ csmall at : enc.com.au
Debian GNU/Linux  https://www.debian.org/   csmall at : debian.org
GPG fingerprint:5D2F B320 B825 D939 04D2  0519 3938 F96B DF50 FEA5



Bug#855188: [tehnic #KBM-940-37601]: debian mirror mirrors.xservers.ro [tehnic #MMT-770-90243]

2017-02-15 Thread Peter Palfrader
On Wed, 15 Feb 2017, Departamentul Tehnic xServers wrote:

> We use ftpsync, but because we have a option in config(--max-delete) the sync 
> stop.
> So, i eliminate that option and now the mirror update without error :-)

That makes sense, your mirror was very out of date and a lot of files
have been removed (and replaced) since.

> I use the link and added the mirror as a new, because message say that "I am 
> removing this mirror".

Yup, tracking it already as Bug#855188 on https://bugs.debian.org/855188.

I pointed out a few remaining issue in my other mail.

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



Bug#840064: apticron: apt-get stops when an update for a held back package is found

2017-02-15 Thread Michael Lange
> If the use of "--allow-change-held-packages" seams dangerous to you (it
> might not as we also set "-s" in the command line, it should be safer to
> juste replace "-y" by "--trivial-only" which will answer yes for all non
> dangerous questions and no on the orthers.

Since -s is used it is not a matter of "safe" vs. "dangerous", nothing
will be actually installed anyway. Otoh, with --trivial-only an available
update that however requires "yes" being answered on a "dangerous"
question might get lost in the process.

> What about replacing the whole complicated line by something more simple
> based on apt like this:
> 
> apt list --upgradable 2>/dev/null | sed -ne 's#^\(.*\)/.*$#\1#p'

Sounds reasonable, however I believe there are two problems with this:

1. if the maintainers wish to keep apticron's behavior intact, it is not
possible this way, since NOTIFY_NEW="1" would no longer have any effect
(although most likely the majority of users could live with that).

2. more seriously: the following part from man apt

> The apt(8) commandline is designed as a end-user tool and it may change
> the output between versions. While it tries to not break backward
> compatibility there is no guarantee for it either. All features of apt
> (8) are available in apt-cache(8) and apt-get(8) via APT options.
> Please prefer using these commands in your scripts.  

does not sound like the apt command is the preferred tool for a script
like apticron. Maybe if apticron's developers contacted the apt
development team, they could reassure them that this part of the cli is
no subject for changes, though.



Bug#815461: ping

2017-02-15 Thread Jonathan McDowell
On Wed, Feb 15, 2017 at 12:23:37AM -0800, Dima Kogan wrote:
> Uwe: thanks for the upstream development and the package maintenance!
> 
> Rest of you: does anybody have any tangible progress to share? If not,
> I'll get the new release out in a week or two. It's really too bad we
> missed the stretch cutoff, but better late than never.

Aaron had made some progress (e.g. https://github.com/insom/libsigrok)
and was keen on being involved in the ongoing maintenance; it might be
good to enable him to do so as part of pkg-electronics?

J.

-- 
  Three can keep a secret, if two  |  .''`.  Debian GNU/Linux Developer
 are dead. | : :' :  Happy to accept PGP signed
   | `. `'   or encrypted mail - RSA
   |   `-key on the keyservers.


signature.asc
Description: Digital signature


Bug#853254: ftp.debian.org: please create stretch-backports suite

2017-02-15 Thread Ansgar Burchardt
Niels Thykier writes:
>> In preparation of the freeze, it would be nice if the stretch-backports
>> could be populated, with the same architectures as stretch.  If
>> possible, the new suite should not accept uploads until the actual
>> stretch release.
>
> Are there any news on this?  Currently, the DSA are waiting for this
> before starting their upgrade tests to stretch.

stretch-backports and jessie-backports-sloppy should appear on the
mirrors with the next dinstall run. (-sloppy at the same time as it is
the same work after all.)

They should reject uploads for now and the build queues on incoming.d.o
are not setup yet either.

Ansgar



Bug#854997: Just slight but acceptable changes in the expected output

2017-02-15 Thread Christian Ehrhardt
I beg a pardon if that all is trivial to you, I get to this part of
postgres for the first time.

The error around index creation matches the release note changes to index
creation.
But the source for this error that we see is actually an expected fail:

regress/sql/repack.sql:
-- This will fail. Silence the message as it's different across PG versions.
SET client_min_messages = fatal;
CREATE UNIQUE INDEX CONCURRENTLY idx_badindex_n ON tbl_badindex (n);
SET client_min_messages = warning;

When diving into the diff of result vs expected output I found some issues
on the path used for the tablespace.
I needed to add this in my repro iteration
 $ rm -rf /tmp/pg-repack-tablespace/*

The diff then comes down to:
- whitespace
- the explicit listing of TABLESPACE pg_default in some statements

The output of those two calls has changed:
  repack.repack_indexdef(indexrelid, 'testts1'::regclass, NULL, true)
If there is a value instead of NULL the output did not change.

This argument is defined as
* @param»··tablespace»·Namespace for the index. If NULL keep the original.

In the cases with a tablespace already defined as "foo" the expected output
already lists "TABLESPACE foo" that is why it is not changing.
The cases with NULL had nothing about it before but now get "TABLESPACE
pg_default" which exactly matches the defintion of the argument.

Upstream has several changes like [1] to add more accepted output versions.

I think that it might be ok to integrate a new
pg-repack-1.3.4/regress/expected/tablespace_2.out with the new content.
I'm gonna suggest upstream at pg_repack as well, but I'd be happy to hear
your expertise on it as well.

[1]:
https://github.com/reorg/pg_repack/commit/4002b4e18f030c8e265707e0174b184d325eeb1b

-- 
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd


Bug#855192: RM: raptor -- RoQA; superseded by raptor2

2017-02-15 Thread Simon McVittie
Package: ftp.debian.org
Severity: normal

raptor was superseded by raptor2 around 6 years ago, and the last two
accidental build-dependencies on it were recently removed. The maintainer
has not responded to a RC bug asking for it to be excluded from stretch.
I think we should remove it from unstable instead, so that we won't have
the same conversation again in 2 years.

For context: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850840

Regards,
S



Bug#855193: RFS: slt/0.0.git20140301-2.1 [RC][NMU] -- TLS reverse-proxy with SNI multiplexing (TLS virtual hosts)

2017-02-15 Thread Roger Shimizu
Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for my package "slt" as [RC][NMU].
I posted the patch to Bug#851876 for 4 days but no feedback.
And pkg maintainer is in LowThresholdNmu list.

 * Package name: slt
   Version : 0.0.git20140301-2.1
   Upstream Author : Alan Shreve 
 * URL : https://github.com/inconshreveable/slt
 * License : Apache-2.0
   Section : devel

It builds those binary packages:

  slt   - TLS reverse-proxy with SNI multiplexing (TLS virtual hosts)

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

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


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

  dget -x 
https://mentors.debian.net/debian/pool/main/s/slt/slt_0.0.git20140301-2.1.dsc

or you can use git-buildpackage to build:
  gbp clone --pristine-tar https://anonscm.debian.org/git/collab-maint/slt.git
  cd slt
  git checkout debian_nmu
  gbp buildpackage -uc -us --git-ignore-branch

I also made it available on debomatic (i386):
  
http://debomatic-i386.debian.net/distribution#unstable/slt/0.0.git20140301-2.1/buildlog

Changes since the last upload:

  slt (0.0.git20140301-2.1) unstable; urgency=medium

[ Roger Shimizu ]
* Non-maintainer upload.
* debian/rules:
  - Run dh_auto_test only if CPUs >= 2 (Closes: #851876).

I also enclosed the debdiff for NMU review.
Thank you!

Cheers,
--
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1
diff -Nru slt-0.0.git20140301/debian/changelog 
slt-0.0.git20140301/debian/changelog
--- slt-0.0.git20140301/debian/changelog2017-01-03 14:37:31.0 
+0900
+++ slt-0.0.git20140301/debian/changelog2017-02-15 07:52:32.0 
+0900
@@ -1,3 +1,12 @@
+slt (0.0.git20140301-2.1) unstable; urgency=medium
+
+  [ Roger Shimizu ]
+  * Non-maintainer upload.
+  * debian/rules:
+- Run dh_auto_test only if CPUs >= 2 (Closes: #851876).
+
+ -- Roger Shimizu   Wed, 15 Feb 2017 07:52:32 +0900
+
 slt (0.0.git20140301-2) unstable; urgency=medium
 
   * wrap-and-sort -ast
diff -Nru slt-0.0.git20140301/debian/rules slt-0.0.git20140301/debian/rules
--- slt-0.0.git20140301/debian/rules2017-01-03 14:36:32.0 +0900
+++ slt-0.0.git20140301/debian/rules2017-02-15 07:52:32.0 +0900
@@ -8,3 +8,11 @@
 override_dh_installman:
ronn < man/slt.8.ronn >debian/slt.8
dh_installman
+
+# Run test only if CPUs >= 2. See Bug#851876
+override_dh_auto_test:
+ifneq ($(shell nproc), 1)
+   dh_auto_test
+else
+   @echo dh_auto_test skipped on 1-Core CPU platform
+endif


Bug#854997: new tablespace for me looks like the attached file

2017-02-15 Thread Christian Ehrhardt
new tablespace for me looks like the attached file


-- 
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd


tablespace_2.out
Description: Binary data


Bug#568375: [pkg-gnupg-maint] Bug#568375: Bug#568375: gnupg-agent: does not work with `git tag -s`

2017-02-15 Thread Werner Koch
On Tue, 14 Feb 2017 00:55, d...@fifthhorseman.net said:

>  * gpg 1.4 expects to connect directly to the active smartcard.  2.1
>expects access to the smartcard to be mediated by the scdaemon
>process.  I don't know what happens if both of these systems try to
>access a single smartcard concurrently, but i imagine it's not

If gpg 1.4 can access the card via agent+scdaemon it uses these daemons
to access the card.  Thus many things should work.

If 1.4 can't do that it uses an old copy of the code used by scdaemon to
access the card.  That code is old and thus a lot of things won't work.

I can't suggest to use 1.4 with smardcards.


Salam-Shalom,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.


pgpCLzy6TNyOz.pgp
Description: PGP signature


Bug#855194: locales: locale en_US.ISO-8859-1 and en_US.iso88591 wrong with dpkg-reconfigure locales

2017-02-15 Thread Hermann Lauer
Package: locales
Version: 2.24-9
Severity: important
Tags: l10n

Dear Maintainer,

# dpkg-reconfigure locales
Generating locales (this might take a while)...
  de_DE.ISO-8859-1... done
  de_DE.UTF-8... done
  en_GB.UTF-8... done
  en_US.ISO-8859-1... done
  en_US.UTF-8... done
  en_US.iso88591...character map file `iso88591' not found: No such file or 
directory
 done
Generation complete.

This is on a stretch system, on a jessie system codeset is ISO-8859-1 in
"locale -a -v" output. Complete output on stretch is below.

Thanks,
  greetings
   Hermann

# locale -a -v
locale: de_DE   archive: /usr/lib/locale/locale-archive
---
title | German locale for Germany
   source | Free Software Foundation, Inc.
  address | http://www.gnu.org/software/libc/
email | bug-glibc-loca...@gnu.org
 language | German
territory | Germany
 revision | 1.0
 date | 2000-06-24
  codeset | ISO-8859-1

locale: de_DE.iso88591  archive: /usr/lib/locale/locale-archive
---
title | German locale for Germany
   source | Free Software Foundation, Inc.
  address | http://www.gnu.org/software/libc/
email | bug-glibc-loca...@gnu.org
 language | German
territory | Germany
 revision | 1.0
 date | 2000-06-24
  codeset | ISO-8859-1

locale: de_DE.utf8  archive: /usr/lib/locale/locale-archive
---
title | German locale for Germany
   source | Free Software Foundation, Inc.
  address | http://www.gnu.org/software/libc/
email | bug-glibc-loca...@gnu.org
 language | German
territory | Germany
 revision | 1.0
 date | 2000-06-24
  codeset | UTF-8

locale: deutsch archive: /usr/lib/locale/locale-archive
---
title | German locale for Germany
   source | Free Software Foundation, Inc.
  address | http://www.gnu.org/software/libc/
email | bug-glibc-loca...@gnu.org
 language | German
territory | Germany
 revision | 1.0
 date | 2000-06-24
  codeset | ISO-8859-1

locale: en_GB.utf8  archive: /usr/lib/locale/locale-archive
---
title | English locale for Britain
   source | RAP
  address | Sankt Jørgens Alle 8, DK-1615 København V, Danmark
  contact | Keld Simonsen
email | bug-glibc-loca...@gnu.org
 language | British English
territory | United Kingdom
 revision | 1.0
 date | 2000-06-28
  codeset | UTF-8

locale: en_US   archive: /usr/lib/locale/locale-archive
---
title | English locale for the USA
   source | Free Software Foundation, Inc.
  address | http://www.gnu.org/software/libc/
email | bug-glibc-loca...@gnu.org
 language | American English
territory | United States
 revision | 1.0
 date | 2000-06-24
  codeset | ANSI_X3.4-1968

locale: en_US.iso88591  archive: /usr/lib/locale/locale-archive
---
title | English locale for the USA
   source | Free Software Foundation, Inc.
  address | http://www.gnu.org/software/libc/
email | bug-glibc-loca...@gnu.org
 language | American English
territory | United States
 revision | 1.0
 date | 2000-06-24
  codeset | ANSI_X3.4-1968

locale: en_US.utf8  archive: /usr/lib/locale/locale-archive
---
title | English locale for the USA
   source | Free Software Foundation, Inc.
  address | http://www.gnu.org/software/libc/
email | bug-glibc-loca...@gnu.org
 language | American English
territory | United States
 revision | 1.0
 date | 2000-06-24
  codeset | UTF-8

locale: german  archive: /usr/lib/locale/locale-archive
---
title | German locale for Germany
   source | Free Software Foundation, Inc.
  address | http://www.gnu.org/software/libc/
email | bug-glibc-loca...@gnu.org
 language | German
territory | Germany
 revision | 1.0
 date | 2000-06-24
  codeset | ISO-8859-1

locale: C.UTF-8 directory: /usr/lib/locale/C.UTF-8
---
title | C locale
email | aure...@debian.org
 language | C
 revision | 1.6
 date | 2016-08-08
  codeset | UTF-8

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

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

Versions of packages locales depends on:
ii  debconf [debconf-2.0]  1.5.60
ii  libc-bin  

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

2017-02-15 Thread Peter Palfrader
Package: mirrors
User: mirr...@packages.debian.org
Usertags: mirror-problem

Tracking this in the BTS.

o Please use our ftpsync script to mirror Debian.

  Using ftpsync ensures updates are done in the correct order so apt
  clients don't get confused.  It also should produce correct trace
  files that contain more information that is useful for us.
  https://mirror.dataone.nl/debian/project/ftpsync/ftpsync-current.tar.gz

  [This script should also work for mirroring Ubuntu.]

o The mirror does not delete old files.

Cheers,

- Forwarded message from Peter Palfrader  -

From: Peter Palfrader 
Subject: Re: debian mirror mirror.dataone.nl: weird trace file
To: "[ mirror.dataone.nl ] - admin" 
Cc: Debian Mirror Team 
Reply-To: Debian Mirror Team 
Date: Sun, 12 Feb 2017 20:54:47 +
Message-ID: <20170212205447.gm11...@sarek.noreply.org>

On Sun, 12 Feb 2017, [ mirror.dataone.nl ] - admin wrote:

> We currently run the following each 6 hours:
> 
> /usr/bin/rsync -av rsync://ftp.nl.debian.org/debian/ /mirror/pub/debian/
> >> /mirror/log/debian/`date '+%Y_%m_%d_%H:%M'`_rsync.log
> /bin/date -u > /mirror/pub/debian/project/trace/mirror.dataone.nl
> 
> please let me know how we can sort / fix it. thanks!

Can we convince you to run our ftpsync script?  Yes, it's a complicated
beast, but multi-stage rsyncs are required to avoid (or minimize)
clients getting errors if they fetch metainformation (such as package
lists) while the mirror upgrades.

You can find a copy at http://mirror.dataone.nl/debian/project/ftpsync/
or if you prefer git
https://anonscm.debian.org/cgit/mirror/archvsync.git/ as the links to
clone from.

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


- End forwarded message -



Bug#855196: RM: fnordmetric -- ROM; Unmaintained; dead upstream; low popcon

2017-02-15 Thread Sebastien Delafond
Package: ftp.debian.org
Severity: normal

No point in leaving this in the archive.

Cheers,

--Seb



Bug#854997: [Pkg-postgresql-public] Bug#854997: new tablespace for me looks like the attached file

2017-02-15 Thread Christian Ehrhardt
FYI - Upstream PR https://github.com/reorg/pg_repack/pull/115


Bug#855193: RFS: slt/0.0.git20140301-2.1 [RC][NMU] -- TLS reverse-proxy with SNI multiplexing (TLS virtual hosts)

2017-02-15 Thread James Cowgill
Hi,

On 15/02/17 10:19, Roger Shimizu wrote:
> Package: sponsorship-requests
> Severity: important
> 
> Dear mentors,
> 
> I am looking for a sponsor for my package "slt" as [RC][NMU].
> I posted the patch to Bug#851876 for 4 days but no feedback.
> And pkg maintainer is in LowThresholdNmu list.
[...]
> Changes since the last upload:
> 
>   slt (0.0.git20140301-2.1) unstable; urgency=medium
> 
> [ Roger Shimizu ]
> * Non-maintainer upload.
> * debian/rules:
>   - Run dh_auto_test only if CPUs >= 2 (Closes: #851876).
> 
> I also enclosed the debdiff for NMU review.
> Thank you!

So do you know why the tests only pass when using 2 CPUs? That seems
pretty fishy to me. Maybe there is an underlying bug here?

Thanks,
James



signature.asc
Description: OpenPGP digital signature


Bug#855197: gcc-6: Please use --with-cpu on sparc without biarch

2017-02-15 Thread John Paul Adrian Glaubitz
Source: gcc-6
Version: 6.3.0-6
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

Hi!

The rebootstrap for sparc with nobiarch still fails [1].

This is because we're using --with-cpu-32=ultrasparc for all
sparc configurations although we have to use --with-cpu=ultrasparc
instead.

An alternative approach would be to apply the patch for PR libstdc++/64735
on sparc as well and use --with-cpu-32=ultrasparc on biarch configurations
as well. This means, we'd be defaulting to SPARCv7 on nobiarch confiurations
while UltraSPARC (SPARCv8+) would be use for biarch configurations. This
would allow the "sparc" port to be bootstrapped for old sun4m hardware.

However, after a quick discussion in #sparc, we have come to the conclusion
to pin sparc to UltraSPARC for now and create a new GNU triplet for SPARCv7
in the future.

The attached patch fixes the FTCBFS issue for sparc-nobiarch.

Thanks,
Adrian

> [1] 
> https://jenkins.debian.net/view/rebootstrap/job/rebootstrap_sparc_gcc6_nobiarch/

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
--- gcc-6-6.3.0/debian/rules2.old   2017-02-15 11:51:16.0 +0100
+++ gcc-6-6.3.0/debian/rules2   2017-02-15 11:53:56.619034818 +0100
@@ -544,9 +544,11 @@
 endif
 
 ifneq (,$(findstring sparc-linux,$(DEB_TARGET_GNU_TYPE)))
-  CONFARGS += --with-cpu-32=ultrasparc
   ifeq ($(biarch64),yes)
 CONFARGS += --enable-targets=all
+CONFARGS += --with-cpu-32=ultrasparc
+  else
+CONFARGS += --with-cpu=ultrasparc
   endif
 endif
 


Bug#855198: [obs-studio] Requested i386 architecture

2017-02-15 Thread Fenix

Package: obs-studio
Severity: wishlist

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


Dear maintainer:

Any chance to get this package officially into i386 architecture?



   Greetings and thanks.



--- System information. ---
Architecture: Kernel:   Linux 4.9.0-1-686-pae

Debian Release: 9.0
  500 testing ftp.de.debian.org
  50 testing www.deb-multimedia.org



Bug#855197: gcc-6: Please use --with-cpu on sparc without biarch

2017-02-15 Thread John Paul Adrian Glaubitz
On 02/15/2017 11:55 AM, John Paul Adrian Glaubitz wrote:
> This is because we're using --with-cpu-32=ultrasparc for all
> sparc configurations although we have to use --with-cpu=ultrasparc
> instead.

... when using nobiarch, I meant.

nobiarch = --with-cpu=ultrasparc
biarch = --with-cpu-32=ultrasparc

> However, after a quick discussion in #sparc, we have come to the conclusion
> to pin sparc to UltraSPARC for now and create a new GNU triplet for SPARCv7
> in the future.

I said "#sparc", I meant "#debian-bootstrap".

> The attached patch fixes the FTCBFS issue for sparc-nobiarch.

Actually verified:

biarch: https://people.debian.org/~glaubitz/bootstrap-sparc-biarch.log.gz
nobiarch: https://people.debian.org/~glaubitz/bootstrap-sparc-nobiarch.log.gz

I'm not fully awake yet. I need another coffee.

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



Bug#850149: shotwell: Freezes when trying to open an image in fullscreen mode

2017-02-15 Thread Alberto Garcia
On Tue, Feb 14, 2017 at 06:36:05PM +, Debian Bug Tracking System wrote:
>  shotwell (0.25.4+really0.24.5-0.1) unstable; urgency=medium
>  .
>* Revert to last stable release 0.24.5 (Closes: #850149).

Thanks for this! Shotwell is finally usable again.

However the original problem (as described in the first comment) is
still present, do you want me to file a separate bug for that, or what
do you prefer?

Regards,

Berto



Bug#817236: schroot: no access to pseudo-terminals in new chroots

2017-02-15 Thread Simon McVittie
On Sat, 26 Nov 2016 at 10:27:38 +, Ben Hutchings wrote:
> On Fri, 2016-11-25 at 18:54 +0100, Marco d'Itri wrote:
> > setup_devices_simple() could be easily modified to create /dev/ptmx with 
> > mknod instead of the current symlink.

That's presumably:

-   ln -s pts/ptmx $TARGET/dev/ptmx
+   mknod -m 666 $TARGET/dev/ptmx c 5 2

That matches what cdebootstrap does, for what it's worth. (Was
cdebootstrap meant to be used in d-i like cdebconf is, or is it just
a trap for the unwary?)

> > While this would solve this problem, it would also break again 
> > debootstrap in containers (which was discussed in different bugs), so 
> > I am not sure if it is a good idea.

Am I correct in thinking that the issue you're talking about here is that
the obvious solution (above) would break this scenario?

* Obtain a rootfs for a container somehow (debootstrap or otherwise)
* Launch a container with that rootfs, using some containerization
  technology (which one?) that applies the same device-cgroup policy that
  systemd's src/core/cgroup.c does:
  - may read and write null, zero, full, random, urandom, tty, ptmx
  - may mknod null, zero, full, random, urandom, tty but *not* ptmx
* Inside that container, run debootstrap
* Good result: debootstrap succeeds
* Bad result: debootstrap fails to mknod $TARGET/dev/ptmx

Or if it's something different, please could you describe it in similar
terms?

If debootstrap inside a container is meant to work, then this would seem
like a job for an autopkgtest. I'll try to write one if someone can tell me
which containerization technologies (systemd-nspawn? lxc? both? others?)
are the ones of interest here.

However, it seems to me that being able to create a chroot that can be
chrooted into with currently-critical bits of Debian infrastructure
(schroot, sbuild) *at all* is probably a higher priority for stretch
than being able to create a conditionally-usable chroot from inside a
container. (By "conditionally usable" I mean schroot/pbuilder can't use
the resulting chroot but maybe systemd-nspawn can.)

Regardless of whether people think sbuild+schroot is the best thing for
the future, it's how current Debian buildds work, and how the next Debian
stable's buildds will work unless sbuild changes extensively during the
freeze, so anything that prevents it from working is de facto release
critical for all releases <= buster.

> The temporary workaround with /dev/ptmx could be made optional.  It's
> not OK to break the previously working configurations.

If I'm understanding the situation correctly then the next best thing would
seem to be:

-   ln -s pts/ptmx $TARGET/dev/ptmx
+   # Inside a container, we might not be allowed to create /dev/ptmx.
+   # If not, do the next best thing (but see #817236).
+   mknod -m 666 $TARGET/dev/ptmx c 5 2 || ln -s pts/ptmx $TARGET/dev/ptmx

which would result in debootstrap inside a container continuing to create
a /dev that current schroot etc. cannot successfully use (but that's maybe
better than it failing completely?), whereas debootstrap outside a container
would create a /dev that works fine?

Is there a reason why mounting /dev/pts results in 000 permissions
on /dev/pts/ptmx? That seems odd. If it didn't, then what debootstrap
does would work.

I notice that systemd creates a symlink when making a new namespace, but
systemd also mounts /dev/pts with newinstance,ptmxmode=0666 when making a
new namespace, and existing tools like schroot and pbuilder presumably
don't do that. Should they? Or would that break the ability for an
interactive shell inside the chroot to have its stdin/stdout/stderr
point to the pty created by an xterm, screen or equivalent outside the
chroot?

Regards,
S



Bug#809405: systemd: Backport systemctl is-enabled support for SysV init scripts to Debian Jessie

2017-02-15 Thread Michael Biebl
Control: tags -1 + patch

Am 27.03.2016 um 22:57 schrieb Branko Majic:
> Sorry for the super-late reply on this one. I haven't dug into it any
> further at the moment. I'm afraid I might have wiped-out the patches I
> had in the meantime (it was still a very dirty hack), but will need to
> check it.

Attached is a patch for v215 which adds support for is-enabled for SysV
init scripts. It uses the same heuristics/logic as systemd-sysv-install.

Feedback welcome. I'd appreciate it if you could test the patch.

Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
From 74a55eee2e4fdc15d4b7857e2f2454dd00730fc0 Mon Sep 17 00:00:00 2001
From: Michael Biebl 
Date: Wed, 15 Feb 2017 10:03:37 +0100
Subject: [PATCH] Support is-enabled for SysV init scripts

As update-rc.d does not provide is-enabled, we implement it ourselves in
systemctl. It uses the same logic as in systemd-sysv-install, see
commit b5aa768d8108b294c1187a0728f5b13c033b3d47

Closes: #809405
---
 src/systemctl/systemctl.c | 38 --
 1 file changed, 24 insertions(+), 14 deletions(-)

diff --git a/src/systemctl/systemctl.c b/src/systemctl/systemctl.c
index c67b86d..efce97f 100644
--- a/src/systemctl/systemctl.c
+++ b/src/systemctl/systemctl.c
@@ -4998,9 +4998,8 @@ static int enable_sysv_units(const char *verb, char **args) {
 return 0;
 
 if (!streq(verb, "enable") &&
-!streq(verb, "disable"))
-// update-rc.d currently does not provide is-enabled
-//!streq(verb, "is-enabled"))
+!streq(verb, "disable") &&
+!streq(verb, "is-enabled"))
 return 0;
 
 /* Processes all SysV units, and reshuffles the array so that
@@ -5045,6 +5044,12 @@ static int enable_sysv_units(const char *verb, char **args) {
 break;
 }
 
+/* If we have both a native unit and a SysV script,
+ * enable/disable them both (below); for is-enabled,
+ * prefer the native unit */
+if (found_native && streq(verb, "is-enabled"))
+continue;
+
 if (!isempty(arg_root))
 asprintf(&p, "%s/" SYSTEM_SYSVINIT_PATH "/%s", arg_root, name);
 else
@@ -5065,6 +5070,21 @@ static int enable_sysv_units(const char *verb, char **args) {
 args[f] = (char*) "";
 }
 
+if (streq(verb, "is-enabled")) {
+_cleanup_free_ char *g = NULL;
+asprintf(&g, "%s%s", "/etc/rc[S5].d/S??", basename(p));
+if (glob_exists(g)) {
+if (!arg_quiet)
+puts("enabled");
+r = 1;
+continue;
+} else {
+if (!arg_quiet)
+puts("disabled");
+continue;
+}
+}
+
 log_info("Synchronizing state for %s with sysvinit using update-rc.d...", name);
 
 if (!isempty(arg_root) && !streq(arg_root, "/")) {
@@ -5149,17 +5169,7 @@ static int enable_sysv_units(const char *verb, char **args) {
 }
 
 if (status.si_code == CLD_EXITED) {
-if (streq(verb, "is-enabled")) {
-if (status.si_status == 0) {
-if (!arg_quiet)
-puts("enabled");
-r = 1;
-} else {
-if (!arg_quiet)
-puts("disabled");
-}
-
-} else if (status.si_status != 0) {
+if (status.si_status != 0) {
 r = -EINVAL;
 goto finish;
 }
-- 
2.11.0



signature.asc
Description: OpenPGP digital signature


Bug#854997: [Pkg-postgresql-public] Bug#854997: new tablespace for me looks like the attached file

2017-02-15 Thread Christian Ehrhardt
​Fix for Debian,
I don't know what you prefer and you very likely want to adapt it anyway to
match your upload plans.
But to be sure here as debdiff (attached) and git branch [1] from latest
debian git on pg-repack

[1]:
https://code.launchpad.net/~paelzer/ubuntu/+source/pg-repack/+git/pg-repack/+ref/fix-pg-feb-2017-microrelease


fix-854997-pg-repack-testcase.debdiff
Description: Binary data


Bug#855193: RFS: slt/0.0.git20140301-2.1 [RC][NMU] -- TLS reverse-proxy with SNI multiplexing (TLS virtual hosts)

2017-02-15 Thread Roger Shimizu
Dear James,

On Wed, Feb 15, 2017 at 7:51 PM, James Cowgill  wrote:
>
> So do you know why the tests only pass when using 2 CPUs? That seems
> pretty fishy to me. Maybe there is an underlying bug here?

I'm not sure the reason.
I was just trying to help on the FTBFS RC bug during BSP Tokyo.

What I know is this is not rare, like another one I fixed:
https://bugs.debian.org/854500

Could you kindly help to upload?
Buildd [0] shows it actually build fine for all ARCHs I should build,
so I don't what to trigger the autoremove ...
Thanks!

[0] https://buildd.debian.org/status/package.php?p=slt

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1



Bug#835104: schroot: please provide a systemd service file

2017-02-15 Thread Laurent Bigonville

tag 835104 + patch
thanks

On Mon, 22 Aug 2016 15:59:24 +0200 Aurelien Jarno  
wrote:

> Dear Maintainer,
>
> schroot provides an initscript which can take quite some time to
> execute, for example if configured to end up all active sessions. When
> running under systemd, it is often killed after the default 90 seconds
> timeout. This happens regularly on the Debian porterboxes where many
> users leave their chroot sessions opened.
>
> The solution is probably to provide a systemd service file running in
> oneshot mode, so that it defaults to no timeout.

I've attached here a patch to add a .service file, it calls the 
initscript, this is a quick solution but it should work.


I didn't add any dependency against LVM because the VG should already 
for all services that have DefaultDependencies=yes (the default) defined.


I also see that the LSB initscript has a dependency against the network, 
any idea why this is needed? Was this necessary to guarantee the network 
shares? Or was it for something else?


Maybe a RequiresMountsFor=/var/lib/schroot could also be added?

On my laptop, schroot is the last LSB initscript without equivalent that 
requires the $network facility, in some situation, this makes the boot 
stall for around 20s (as it waits for the network to come online). Could 
it still be an option to add that for stretch?


Regards,

Laurent Bigonville
diff -Nru schroot-1.7.2/debian/control schroot-1.7.2/debian/control
--- schroot-1.7.2/debian/control	2015-08-18 15:15:47.0 +0200
+++ schroot-1.7.2/debian/control	2017-02-15 11:56:24.0 +0100
@@ -5,6 +5,7 @@
 Uploaders: Raphaël Hertzog 
 Build-Depends:
  debhelper (>= 9),
+ dh-systemd,
  cmake (>= 2.8.12),
  pkg-config,
  libpam0g-dev,
diff -Nru schroot-1.7.2/debian/rules schroot-1.7.2/debian/rules
--- schroot-1.7.2/debian/rules	2015-08-18 15:15:47.0 +0200
+++ schroot-1.7.2/debian/rules	2017-02-15 11:56:15.0 +0100
@@ -23,7 +23,7 @@
 	CFLAGS += -O2
 endif
 
-DH_OPTIONS = --buildsystem=cmake --builddirectory=debian/build --parallel
+DH_OPTIONS = --with systemd --buildsystem=cmake --builddirectory=debian/build --parallel
 
 ifneq (,$(filter parallel=%,$(DEB_BUILD_OPTIONS)))
   NUMJOBS = $(patsubst parallel=%,%,$(filter parallel=%,$(DEB_BUILD_OPTIONS)))
diff -Nru schroot-1.7.2/debian/schroot.service schroot-1.7.2/debian/schroot.service
--- schroot-1.7.2/debian/schroot.service	1970-01-01 01:00:00.0 +0100
+++ schroot-1.7.2/debian/schroot.service	2017-02-15 11:56:24.0 +0100
@@ -0,0 +1,12 @@
+[Unit]
+Description=Recover schroot sessions
+Documentation=man:schroot(1)
+
+[Service]
+Type=oneshot
+ExecStart=/etc/init.d/schroot start
+ExecStop=/etc/init.d/schroot stop
+RemainAfterExit=yes
+
+[Install]
+WantedBy=multi-user.target


Bug#855199: sympa web interface broken with jquery v3

2017-02-15 Thread Ander Punnar
Package: sympa
Version: 6.2.16~dfsg-2
Severity: important

sympa upstream ships with jquery v1.11.1, but next stable stretch ships
v3.1.1-2, which breaks web interface (unable to use hover menus).

please add libjs-jquery-migrate-1 into dependencies and patch
head_javascript.tt2 until upstream migrates to newer jquery.

also, quick workaround:

# apt-get install javascript-common libjs-jquery-migrate-1
# service apache2 reload
# cd /etc/sympa/web_tt2
# cp /usr/share/sympa/default/web_tt2/head_javascript.tt2 .
# vim /usr/share/sympa/default/web_tt2/head_javascript.tt2
# diff -u /usr/share/sympa/default/web_tt2/head_javascript.tt2 
head_javascript.tt2
--- /usr/share/sympa/default/web_tt2/head_javascript.tt22016-11-25
12:41:16.0 +0200
+++ head_javascript.tt2 2017-02-15 13:24:15.114609026 +0200
@@ -54,6 +54,7 @@
 

  
  +

   



Bug#817236: schroot: no access to pseudo-terminals in new chroots

2017-02-15 Thread Ben Hutchings
On Wed, 2017-02-15 at 11:13 +, Simon McVittie wrote:
> On Sat, 26 Nov 2016 at 10:27:38 +, Ben Hutchings wrote:
[...]
> > The temporary workaround with /dev/ptmx could be made optional.  It's
> > not OK to break the previously working configurations.
> 
> If I'm understanding the situation correctly then the next best thing would
> seem to be:
> 
> -   ln -s pts/ptmx $TARGET/dev/ptmx
> +   # Inside a container, we might not be allowed to create /dev/ptmx.
> +   # If not, do the next best thing (but see #817236).
> +   mknod -m 666 $TARGET/dev/ptmx c 5 2 || ln -s pts/ptmx $TARGET/dev/ptmx
> 
> which would result in debootstrap inside a container continuing to create
> a /dev that current schroot etc. cannot successfully use (but that's maybe
> better than it failing completely?), whereas debootstrap outside a container
> would create a /dev that works fine?

That seems reasonable.

> Is there a reason why mounting /dev/pts results in 000 permissions
> on /dev/pts/ptmx? That seems odd. If it didn't, then what debootstrap
> does would work.

It *is* odd.  I think the assumption was that normally you carry on
using a simple device node at /dev/ptmx but you can opt-in to using
/dev/pts/ptmx through mount options.

> I notice that systemd creates a symlink when making a new namespace, but
> systemd also mounts /dev/pts with newinstance,ptmxmode=0666 when making a
> new namespace, and existing tools like schroot and pbuilder presumably
> don't do that. Should they?

Yes, I think so.  ('newinstance' is always enabled in recent kernel
versions, but must be enabled explicitly for older kernel versions.)

> Or would that break the ability for an
> interactive shell inside the chroot to have its stdin/stdout/stderr
> point to the pty created by an xterm, screen or equivalent outside the
> chroot?

I don't think so.  I don't see why that would happen.

Ben.

-- 
Ben Hutchings
Lowery's Law:
 If it jams, force it. If it breaks, it needed replacing
anyway.



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


Bug#853753: Acknowledgement (gitlab-shell: fails after update - git auth ?)

2017-02-15 Thread Xavier Bestel
Resolved with gitlab_8.13.11+dfsg-2 and gitlab-shell_3.6.6-3.
Please close.

Cheers,
Xav



Bug#618606: Info received (git-daemon: Still happening, what to do ?)

2017-02-15 Thread Xavier Bestel
Resolved by installing runit-systemd. This should somehow be a
dependency.

Cheers,
Xav



Bug#855035: debian-installer: https does not work with stretch rc2 installer

2017-02-15 Thread Philipp Kern
On 02/13/2017 04:45 PM, Steve McIntyre wrote:
> On Mon, Feb 13, 2017 at 04:03:42PM +0100, Cyril Brulebois wrote:
>> Hi Hilko,
>>
>> Strange, debootstrap already has this:
>> | case $MIRRORS in
>> | https://*)
>> | base="$base apt-transport-https ca-certificates"
>> | ;;
>> | esac
>>
>> Please share your installer's syslog?
>>
>> Anyway, putting debian-cd@ in copy since package lists might need an
>> update for those two packages, so that they have a high(er) chance of
>> being available on installation images.
> 
> Just added those to the "forcd1" package list so they'll always get
> pulled in for our media. Surprised that they're not already
> recommended/depended, to be honest!

Hrm, why "forcd1" specifically? I'm not sure what the netinst list is
but forcd1's header tells me it's specifically not for
netinst/businesscard. I fear we also need it there given the fix will be
in bootstrap-base. Does that mean that we actually need to propagate
dependencies there somehow?

Kind regards
Philipp Kern




signature.asc
Description: OpenPGP digital signature


Bug#855200: gnomint: segfault when exporting private keys

2017-02-15 Thread Karl E. Jorgensen
Package: gnomint
Version: 1.2.1-7
Severity: important

Dear Maintainer,

When exporting private keys from gnomint, the export appars to work
ok, but is immediately followed by a segfault.  This happens on both
version 1.2.1-7+b2 and version 1.2.1-7

This doesn't happen when exporting the public parts.

I managed to build gnomint 1.2.1-7 [1] from the debian source ("managed" -
it was easy) , which also produced the gnomint-dbgsym package which
allowed me to examine the resulting core dump. It gave me this backtrace:

Core was generated by `gnomint'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7fbe7c4bd445 in ?? () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
[Current thread is 1 (Thread 0x7fbe7ce73a80 (LWP 25490))]
(gdb) bt
#0  0x7fbe7c4bd445 in ?? () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#1  0x7fbe7c4b032c in gtk_tree_model_get_valist () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#2  0x7fbe7c4b0629 in gtk_tree_model_get () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#3  0x5589191c2a4b in __ca_export_private_pkcs8 (iter=0x5589, 
type=type@entry=0) at ca.c:950
#4  0x5589191c34ea in ca_on_extractprivatekey1_activate 
(menuitem=, user_data=) at ca.c:1192
#5  0x7fbe7be3df75 in g_closure_invoke () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#6  0x7fbe7be4ff82 in ?? () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#7  0x7fbe7be58bcc in g_signal_emit_valist () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#8  0x7fbe7be58faf in g_signal_emit () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#9  0x7fbe7c4ec62e in gtk_widget_activate () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#10 0x7fbe7c3e74dd in gtk_menu_shell_activate_item () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#11 0x7fbe7c3e7846 in ?? () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#12 0x7fbe7c3d57bc in ?? () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#13 0x7fbe7be3df75 in g_closure_invoke () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#14 0x7fbe7be5037d in ?? () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#15 0x7fbe7be5866f in g_signal_emit_valist () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16 0x7fbe7be58faf in g_signal_emit () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#17 0x7fbe7c4ed8ac in ?? () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#18 0x7fbe7c3d3f84 in gtk_propagate_event () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#19 0x7fbe7c3d433b in gtk_main_do_event () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#20 0x7fbe79f45cbc in ?? () from 
/usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
#21 0x7fbe7bb647f7 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7fbe7bb64a60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7fbe7bb64d82 in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x7fbe7c3d33b7 in gtk_main () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#25 0x5589191b828a in main (argc=, argv=) at 
main.c:201


[1] "apt-get source" was unwilling give the source for 1.2.1-7+b2 !?
It would only give me version 1.2.1-7. But the same problem
exists there too.


-- System Information:
Debian Release: 9.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (300, 
'unstable')
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)

Versions of packages gnomint depends on:
ii  gconf-service   3.2.6-4
ii  gconf2  3.2.6-4
ii  libc6   2.24-9
ii  libgconf-2-43.2.6-4
ii  libgcrypt20 1.7.6-1
ii  libgdk-pixbuf2.0-0  2.36.4-1
ii  libglib2.0-02.50.2-2
ii  libgnutls30 3.5.8-3
ii  libgtk2.0-0 2.24.31-2
ii  libreadline77.0-2
ii  libsqlite3-03.16.2-2

gnomint recommends no packages.

gnomint suggests no packages.

-- no debconf information



Bug#855199: sympa web interface broken with jquery v3

2017-02-15 Thread Emmanuel Bouthenot
Ander,

On Wed, Feb 15, 2017 at 01:49:18PM +0200, Ander Punnar wrote:
> Package: sympa
> Version: 6.2.16~dfsg-2
> Severity: important
> 
> sympa upstream ships with jquery v1.11.1, but next stable stretch ships
> v3.1.1-2, which breaks web interface (unable to use hover menus).
> 
> please add libjs-jquery-migrate-1 into dependencies and patch
> head_javascript.tt2 until upstream migrates to newer jquery.

This fix is already in the pipe for the next upload as I've already
stumble upon this bug.

Regards,

-- 
Emmanuel Bouthenot
  mail: kolter@{openics,debian}.orggpg: 4096R/0x929D42C3
  xmpp: kol...@im.openics.org  irc: kolter@{freenode,oftc}



Bug#855201: bad terminal size

2017-02-15 Thread Harald Dunkel
Package: clusterssh
Version: 4.08-2

~/.clusterssh/config says

terminal_size=80x24

but the xterm started by "cssh localhost" gives me

% tput cols
77
% tput lines
24

config file is attached. Window manager is fvwm2.


Regards
Harri
auto_close=0
auto_quit=yes
command=
comms=ssh
console_position=
debug=0
extra_cluster_file=
history_height=10
history_width=40
key_addhost=Control-Shift-plus
key_clientname=Alt-n
key_history=Alt-h
key_paste=Control-v
key_quit=
key_retilehosts=Alt-r
lang=en
max_addhost_menu_cluster_items=6
max_host_menu_items=30
menu_host_autotearoff=0
menu_send_autotearoff=0
mouse_paste=Button-2
rsh_args=
screen_reserve_bottom=60
screen_reserve_left=0
screen_reserve_right=0
screen_reserve_top=0
send_menu_xml_file=/home/hdunkel/.csshrc_send_menu
show_history=0
ssh=/usr/bin/ssh
ssh_args=-x -o ConnectTimeout=10
telnet_args=
terminal=/usr/bin/xterm
terminal_allow_send_events=-xrm '*.VT100.allowSendEvents:true'
terminal_args=
terminal_bg_style=dark
terminal_colorize=1
terminal_decoration_height=10
terminal_decoration_width=8
terminal_font=6x13
terminal_reserve_left=7
terminal_reserve_right=7
terminal_reserve_top=23
terminal_reserve_bottom=7
terminal_size=80x24
terminal_title_opt=-T
title=CSSH
unmap_on_redraw=no
use_all_a_records=0
use_hotkeys=yes
window_tiling=yes
window_tiling_direction=right


Bug#855202: RFS: binaryornot/0.4.0+dfsg-0.1 [RC][NMU] -- check if a file is binary or text

2017-02-15 Thread Roger Shimizu
Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for my package "binaryornot" as [RC][NMU].

 * Package name: binaryornot
   Version : 0.4.0+dfsg-0.1
   Upstream Author : Audrey Roy 
 * URL : https://github.com/audreyr/binaryornot
 * License : BSD-3-clause
   Section : python

It builds those binary packages:

  python-binaryornot - check if a file is binary or text (Python 2 module)
  python3-binaryornot - check if a file is binary or text (Python 3 module)

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

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


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

  dget -x 
https://mentors.debian.net/debian/pool/main/b/binaryornot/binaryornot_0.4.0+dfsg-0.1.dsc

or you can use git-buildpackage to build:
(since I don't have access to maintainer's Vcs, I pushed my changes to github)
  gbp clone --pristine-tar https://github.com/rogers0/binaryornot
  cd binaryornot
  gbp buildpackage -uc -us --pristine-tar

I also made it available on debomatic (i386):
  
http://debomatic-i386.debian.net/distribution#unstable/binaryornot/0.4.0+dfsg-0.1/buildlog

Changes since the last upload:

  binaryornot (0.4.0+dfsg-0.1) unstable; urgency=medium

* Non-maintainer upload.

[ Ondřej Nový ]
* Fixed VCS URL (https)

[ Roger Shimizu ]
* Remove non-free image files, and repack as +dfsg.
* Add patch to remove tests regarding to non-free image files.
  (Closes: #854851)

I also enclosed the debdiff for NMU review.
Thank you!

Cheers,
--
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1
diff -Nru binaryornot-0.4.0/debian/changelog 
binaryornot-0.4.0+dfsg/debian/changelog
--- binaryornot-0.4.0/debian/changelog  2015-11-16 07:05:20.0 +0900
+++ binaryornot-0.4.0+dfsg/debian/changelog 2017-02-15 21:07:15.0 
+0900
@@ -1,3 +1,17 @@
+binaryornot (0.4.0+dfsg-0.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Ondřej Nový ]
+  * Fixed VCS URL (https)
+
+  [ Roger Shimizu ]
+  * Remove non-free image files, and repack as +dfsg.
+  * Add patch to remove tests regarding to non-free image files.
+(Closes: #854851)
+
+ -- Roger Shimizu   Wed, 15 Feb 2017 21:07:15 +0900
+
 binaryornot (0.4.0-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru binaryornot-0.4.0/debian/control binaryornot-0.4.0+dfsg/debian/control
--- binaryornot-0.4.0/debian/control2015-11-16 07:05:20.0 +0900
+++ binaryornot-0.4.0+dfsg/debian/control   2017-02-15 21:01:09.0 
+0900
@@ -10,7 +10,7 @@
python-hypothesis, python3-hypothesis
 Standards-Version: 3.9.6
 Homepage: https://github.com/audreyr/binaryornot
-Vcs-Git: git://anonscm.debian.org/python-modules/packages/binaryornot.git
+Vcs-Git: https://anonscm.debian.org/git/python-modules/packages/binaryornot.git
 Vcs-Browser: 
https://anonscm.debian.org/cgit/python-modules/packages/binaryornot.git
 
 Package: python-binaryornot
diff -Nru 
binaryornot-0.4.0/debian/patches/0001-Remove-tests-regarding-to-non-free-image-lena.patch
 
binaryornot-0.4.0+dfsg/debian/patches/0001-Remove-tests-regarding-to-non-free-image-lena.patch
--- 
binaryornot-0.4.0/debian/patches/0001-Remove-tests-regarding-to-non-free-image-lena.patch
   1970-01-01 09:00:00.0 +0900
+++ 
binaryornot-0.4.0+dfsg/debian/patches/0001-Remove-tests-regarding-to-non-free-image-lena.patch
  2017-02-15 21:07:15.0 +0900
@@ -0,0 +1,26 @@
+From: Roger Shimizu 
+Date: Wed, 15 Feb 2017 21:14:30 +0900
+Subject: Remove tests regarding to non-free image lena
+
+See Bug #854851
+---
+ tests/test_check.py | 6 --
+ 1 file changed, 6 deletions(-)
+
+diff --git a/tests/test_check.py b/tests/test_check.py
+index 338119e..fbe32d1 100755
+--- a/tests/test_check.py
 b/tests/test_check.py
+@@ -49,12 +49,6 @@ class TestIsBinary(unittest.TestCase):
+ def test_png(self):
+ self.assertTrue(is_binary('tests/files/logo.png'))
+ 
+-def test_gif(self):
+-self.assertTrue(is_binary('tests/files/lena.gif'))
+-
+-def test_jpg(self):
+-self.assertTrue(is_binary('tests/files/lena.jpg'))
+-
+ def test_tiff(self):
+ self.assertTrue(is_binary('tests/files/palette-1c-8b.tiff'))
+ 
diff -Nru binaryornot-0.4.0/debian/patches/series 
binaryornot-0.4.0+dfsg/debian/patches/series
--- binaryornot-0.4.0/debian/patches/series 1970-01-01 09:00:00.0 
+0900
+++ binaryornot-0.4.0+dfsg/debian/patches/series2017-02-15 
21:07:15.0 +0900
@@ -0,0 +1 @@
+0001-Remove-tests-regarding-to-non-free-image-lena.patch
Binary files /tmp/carUuVTSnE/binaryornot-0.4.0/tests/files/lena.gif and 
/tmp/lVa9B18e3R/binaryornot-0.4.0+dfsg/tests/files/lena.gif differ
Binary files /tmp/carUuVTSnE/binaryornot-0.4.0/tests/files/lena.jpg and 
/tmp/lVa9B18e3R/binaryornot-0.4.0+dfsg/tests/files/lena.jpg differ


Bug#855035: debian-installer: https does not work with stretch rc2 installer

2017-02-15 Thread Steve McIntyre
On Wed, Feb 15, 2017 at 01:12:16PM +0100, Philipp Kern wrote:
>On 02/13/2017 04:45 PM, Steve McIntyre wrote:
>> On Mon, Feb 13, 2017 at 04:03:42PM +0100, Cyril Brulebois wrote:
>>> Hi Hilko,
>>>
>>> Strange, debootstrap already has this:
>>> | case $MIRRORS in
>>> | https://*)
>>> | base="$base apt-transport-https ca-certificates"
>>> | ;;
>>> | esac
>>>
>>> Please share your installer's syslog?
>>>
>>> Anyway, putting debian-cd@ in copy since package lists might need an
>>> update for those two packages, so that they have a high(er) chance of
>>> being available on installation images.
>> 
>> Just added those to the "forcd1" package list so they'll always get
>> pulled in for our media. Surprised that they're not already
>> recommended/depended, to be honest!
>
>Hrm, why "forcd1" specifically? I'm not sure what the netinst list is
>but forcd1's header tells me it's specifically not for
>netinst/businesscard. I fear we also need it there given the fix will be
>in bootstrap-base. Does that mean that we actually need to propagate
>dependencies there somehow?

Crap, thanks for catching that. It needs moving to the d-i+kernel
task, doing that now.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
< liw> everything I know about UK hotels I learned from "Fawlty Towers"



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

2017-02-15 Thread Andreas Tille
tags 854341 unreproducible
thanks

I can confirm that it now also builds for me again.  I'm tempted to
close this bug again which seems to have been a temporary issue of some
Build-Dependency.

Chris, what do you think?

Kind regards

 Andreas.

On Tue, Feb 14, 2017 at 08:47:32PM +0100, gregor herrmann wrote:
> On Tue, 14 Feb 2017 09:46:23 +, olivier sallou wrote:
> 
> > > I admit I have no idea how to fix this.  Help from people with
> > > Perl background would be really appreciated.
> > I just made a build attempt (1-31-3) with pbuilder, updated right before
> > build, based on latest svn source and it built fine
> > Onyl difference is make -j4 for you and make -j1 for me (automatic update
> > by debhelper?)
> 
> Builds for me as well (both from svn and from the archive, both with
> -j1 and -j4). cowbuilder sid amd64.
> 
> (BZW: svn seems to miss the tag for 1.31-3. Or my svn foo has
> deteriorated too much.)
>  
> Cheers,
> gregor



-- 
http://fam-tille.de



Bug#855203: hwclock-set: Synchronize from hwclock despite systemd presence

2017-02-15 Thread Lukas Wunner
Package: util-linux
Version: 2.19.1-5
Severity: important
Tags: patch

Back in 2011, hwclock-set was amended to bail out if systemd is present.
According to #629811 the rationale was that "systemd > 25 sets the
hwclock itself, based on the contents of /etc/adjtime, so
/lib/udev/hwclock-set should not do anything if running under systemd."

More accurately however, systemd only determines if the RTC runs at
UTC or local time, and warps the system clock accordingly.  It does
*not* set the system clock from the RTC:  An examination of the systemd
git repo shows that clock_get_hwclock() is only called from
src/timedate/timedated.c in the D-Bus methods SetLocalRTC and
RTCTimeUSec.  The latter, which reads the RTC, is only called from
src/timedate/timedatectl.c when the user invokes "timedatectl status":
https://github.com/systemd/systemd/blob/master/src/core/main.c#L1457
https://github.com/systemd/systemd/blob/master/src/basic/clock-util.c#L36
https://github.com/systemd/systemd/blob/master/src/timedate/timedated.c
https://github.com/systemd/systemd/blob/master/src/timedate/timedatectl.c

In most cases, the kernel itself initializes the system clock from the
RTC with the late_initcall rtc_hctosys():
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/rtc/hctosys.c

But this doesn't work if the driver for the RTC is compiled as a module
or if the kernel was compiled with CONFIG_RTC_HCTOSYS disabled.  One use
case where both of these prerequisites are not met is the Raspberry Pi:
Raspbian ships with a kernel which disables CONFIG_RTC_HCTOSYS and also
compiles all RTC drivers as a module.  This makes sense because the
Raspberry Pi does not possess an RTC.  Instead, people use add-on boards
with various types of clocks and it wouldn't be reasonable to link all
of their drivers into the kernel.

The Internet is full of recipes where /lib/udev/hwclock-set is edited to
remove the lines which cause it to bail out when detecting presence of
systemd, as otherwise the system clock is never initialized from the RTC.
But this approach has the disadvantage that the change will get
overwritten whenever the util-linux package is updated.  Examples:
https://learn.adafruit.com/adding-a-real-time-clock-to-raspberry-pi/set-rtc-time
https://afterthoughtsoftware.com/products/rasclock
http://spellfoundry.com/sleepy-pi/setting-up-the-real-time-clock-on-raspbian-jessie/

Constrain the check for systemd presence in hwclock-set to the
invocation of "hwclock --systz", and do set the system clock from the
RTC unless the kernel has already done that (in which case
/sys/class/rtc/rtc0/hctosys contains "1".)

This patch was developed for and tested successfully on a Revolution Pi
by Kunbus GmbH.

Cc: Mathias Duckeck 
Cc: Phil Elwell 
Signed-off-by: Lukas Wunner 
---
 debian/hwclock-set   | 18 +-
 debian/hwclock.rules |  2 +-
 2 files changed, 10 insertions(+), 10 deletions(-)
>From 48207793e5131b7fdb8ccd039a20d54db3ce9cc2 Mon Sep 17 00:00:00 2001
From: Lukas Wunner 
Date: Tue, 14 Feb 2017 13:51:38 +0100
Subject: [PATCH] hwclock-set: Synchronize from hwclock despite systemd
 presence

Back in 2011, hwclock-set was amended to bail out if systemd is present.
According to #629811 the rationale was that "systemd > 25 sets the
hwclock itself, based on the contents of /etc/adjtime, so
/lib/udev/hwclock-set should not do anything if running under systemd."

More accurately however, systemd only determines if the RTC runs at
UTC or local time, and warps the system clock accordingly.  It does
*not* set the system clock from the RTC:  An examination of the systemd
git repo shows that clock_get_hwclock() is only called from
src/timedate/timedated.c in the D-Bus methods SetLocalRTC and
RTCTimeUSec.  The latter, which reads the RTC, is only called from
src/timedate/timedatectl.c when the user invokes "timedatectl status":
https://github.com/systemd/systemd/blob/master/src/core/main.c#L1457
https://github.com/systemd/systemd/blob/master/src/basic/clock-util.c#L36
https://github.com/systemd/systemd/blob/master/src/timedate/timedated.c
https://github.com/systemd/systemd/blob/master/src/timedate/timedatectl.c

In most cases, the kernel itself initializes the system clock from the
RTC with the late_initcall rtc_hctosys():
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/rtc/hctosys.c

But this doesn't work if the driver for the RTC is compiled as a module
or if the kernel was compiled with CONFIG_RTC_HCTOSYS disabled.  One use
case where both of these prerequisites are not met is the Raspberry Pi:
Raspbian ships with a kernel which disables CONFIG_RTC_HCTOSYS and also
compiles all RTC drivers as a module.  This makes sense because the
Raspberry Pi does not possess an RTC.  Instead, people use add-on boards
with various types of clocks and it wouldn't be reasonable to link all
of their drivers into the kernel.

The Internet is full of recipes where /lib/udev/hwclock-set is edited to
remove the lin

Bug#849355: still occurs in fvwm 1:2.6.7-3

2017-02-15 Thread Vincent Lefevre
Control: reopen -1
Control: found -1 1:2.6.7-3

On 2017-01-20 03:05:12 +, Jaimos Skriletz wrote:
> Format: 1.8
> Date: Mon, 16 Jan 2017 10:52:00 -0700
> Source: fvwm
> Binary: fvwm
> Architecture: source amd64
> Version: 1:2.6.7-3
> Distribution: unstable
> Urgency: low
> Maintainer: Jaimos Skriletz 
> Changed-By: Jaimos Skriletz 
> Description:
>  fvwm   - F(?) Virtual Window Manager
> Closes: 849355 849422 849423
> Changes:
>  fvwm (1:2.6.7-3) unstable; urgency=low
>  .
>* Updates to default configuration.
>* Improved fvwm-menu-directory error handling when python-xdg or
>  a menu is not installed.
>* Fixed an issue with FvwmIconMan triggering window hit warnings.
>  (Closes: #849355)
>* Added patch to improve window hit warnings (related to above).

I still have these warnings:

[fvwm][GetWindowSizeHints]: <> The application window (id 0xc4)
  "FvwmIconMan" has broken size hints (inconsistent with current size).
fvwm is ignoring those hints.hint override = 0, flags = 371
  min_width = 94, min_height = 68, max_width = 94, max_height = 68
  width_inc = 1, height_inc = 1
  min_aspect = 0/0, max_aspect = 0/0
  base_width = 0, base_height = 0
  win_gravity = 1

If you are having a problem with the application, send a bug report
with this message included to the application owner.
There is no need to notify fvwm-work...@fvwm.org.
[fvwm][GetWindowSizeHints]: <> reason: 4: The hints have been ignored 
because the window's current size would have become invalid.  The new hints 
will become active when the window generates the next ConfigureRequest.

[fvwm][GetWindowSizeHints]: <> The application window (id 0xc4)
  "FvwmIconMan" has broken size hints (inconsistent with current size).
fvwm is ignoring those hints.hint override = 0, flags = 371
  min_width = 94, min_height = 51, max_width = 94, max_height = 51
  width_inc = 1, height_inc = 1
  min_aspect = 0/0, max_aspect = 0/0
  base_width = 0, base_height = 0
  win_gravity = 1

If you are having a problem with the application, send a bug report
with this message included to the application owner.
There is no need to notify fvwm-work...@fvwm.org.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#845155: Bug#851606: RFS: rmlint/2.4.6-1 [ITP]

2017-02-15 Thread Roger Shimizu
On Wed, Feb 15, 2017 at 10:27 AM, Axel Beckert  wrote:
>
> Thanks. The package got really nice. Seems to have been still quite
> some work on top of my work
>
> I've just uploaded your package and it should show up within the next
> few hours in the so called NEW queue for review by the FTP masters,
> i.e. at the end of https://ftp-master.debian.org/new.html
>
> Anyway, thanks for your contribution to Debian! (And thanks to Roger
> for his review, too!)

My pleasure.
Good to see the first package, that I get involved in review, is uploaded.

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1



Bug#855204: libpetsc3.7.5-dev: uninstallable - Depends: libopenmpi-dev (< 2.0.2~git.20161226)

2017-02-15 Thread James Cowgill
Package: libpetsc3.7.5-dev
Version: 3.7.5+dfsg1-3
Severity: serious
Tags: sid stretch

Hi,

libpetsc3.7.5-dev 3.7.5+dfsg1-3 and 3.7.5+dfsg1-4 cannot be installed
in unstable. This may or may not affect stretch depending on whether
openmpi migrates (I have conservatively tagged it for the moment).

$ sudo apt-get install libpetsc3.7.5-dev
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libpetsc3.7.5-dev : Depends: libopenmpi-dev (< 2.0.2~git.20161226) but 2.0.2-2 
is to be installed
 Recommends: tcsh but it is not going to be installed or
 csh but it is not going to be installed or
 c-shell
 Recommends: ksh but it is not going to be installed or
 mksh but it is not going to be installed or
 pdksh but it is not installable or
 zsh but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

Thanks,
James



signature.asc
Description: OpenPGP digital signature


Bug#855205: please package more recent version

2017-02-15 Thread Bas Zoetekouw
Package: python-xlib

Please package a more recent version.  Development has moved to Github
(https://github.com/python-xlib/python-xlib) and a much more recent
version (0.18 from november 2016) is available compared to the 0.14 from
2009 which is currently in the archive.

Gr,
Bas.



signature.asc
Description: OpenPGP digital signature


Bug#849823: xfdesktop4: can't click to select a folder with background images

2017-02-15 Thread Pascal Gervais
Hi

There is a patch (a git commit) available on Xfce Bugzilla:
https://bugzilla.xfce.org/show_bug.cgi?id=12832

-- 
Pascal  ><©>



Bug#792205: Fusioninventory in stretch ?

2017-02-15 Thread Adrien Grellier

Hi,

Do you think fusioninventory will made its way to stretch ?

The freeze is here, I see no package in testing, but only this bug is 
blocking. In my lab, we are using fusioninventory a lot on Debian, so I 
am very interesting to have it for the next stable version.


Kind regards,

Adrien

--

Adrien Grellier  (02 40 37 15 55)
Informaticien du LHEEA
CNRS – École Centrale de Nantes



Bug#855206: fvwm: When xterm quits, fvwm doesn't always remove its window immediately

2017-02-15 Thread Vincent Lefevre
Package: fvwm
Version: 1:2.6.7-3
Severity: minor

When xterm quits, fvwm doesn't always remove its window immediately;
it remains on screen for several seconds. During this time, when the
mouse pointer is over this xterm window, the pointer disappears.
That's why I think that this is a fvwm issue, since I do not obtain
this behavior with xterm (+ the screenshot issue below).

When this happens, this is always with a special script. This may mean
that the bug occurs only under some particular conditions. One of them
that might matter is that the window title changes just before xterm
quits (new title: TITLEDISABLED).

The xterm command is something like:

  /usr/bin/xterm -xrm "*printFileOnXError: 
/home/vlefevre/private/xterm-saved-1487164622-23460" +sb -sl 0 -n Mutt - 
cventin -T Mutt -e sh -c "smutt || { echo 'Press [Enter] to quit.'; read x; }"

where smutt is a script that runs GNU screen:

  screen -c /home/vlefevre/.screenrc-mutt -T screen-bce -dRR mutt -t mutt 
/home/vlefevre/bin/smutt --

and .screenrc-mutt contains in particular:

termcapinfo xterm*|rxvt*|mlterm|xfce4-terminal 
hs:ts=\E]2;:fs=^G:ds=\E]2;TITLEDISABLED^G

The new title "TITLEDISABLED" comes from that.

Note: I did a screenshot with CM-s[*], but this made the window
disappear and it didn't appear on the screenshot.

[*] I have in my fvwm config:

Key s   A   CM  Exec gnome-screenshot -w

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

Kernel: Linux 4.9.0-1-amd64 (SMP w/12 CPU cores)
Locale: LANG=POSIX, 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 fvwm depends on:
ii  libc6   2.24-9
ii  libcairo2   1.14.8-1
ii  libfontconfig1  2.11.0-6.7
ii  libfreetype62.6.3-3+b1
ii  libfribidi0 0.19.7-1
ii  libgdk-pixbuf2.0-0  2.36.4-1
ii  libglib2.0-02.50.2-2
ii  libice6 2:1.0.9-1+b1
ii  libperl4-corelibs-perl  0.003-2
ii  libpng16-16 1.6.28-1
ii  libreadline77.0-2
ii  librplay3   3.3.2-16+b1
ii  librsvg2-2  2.40.16-1
ii  libsm6  2:1.2.2-1+b1
ii  libstroke0  0.5.1-8
ii  libtinfo5   6.0+20161126-1
ii  libx11-62:1.6.4-3
ii  libxcursor1 1:1.1.14-1+b1
ii  libxext62:1.3.3-1
ii  libxft2 2.3.2-1
ii  libxinerama12:1.1.3-1+b1
ii  libxpm4 1:3.5.12-1
ii  libxrender1 1:0.9.10-1
ii  perl5.24.1-1

Versions of packages fvwm recommends:
ii  lxmenu-data  0.1.5-2
ii  python   2.7.13-2
ii  python-xdg   0.25-4

Versions of packages fvwm suggests:
ii  cpp   4:6.3.0-1
ii  libx11-protocol-perl  0.56-7
ii  m41.4.18-1
ii  perl-tk   1:804.033-1+b3
pn  stalonetray   

-- no debconf information



Bug#835104: schroot: please provide a systemd service file

2017-02-15 Thread Felipe Sateler
On Wed, Feb 15, 2017 at 8:28 AM, Laurent Bigonville  wrote:
> tag 835104 + patch
> thanks
>
> On Mon, 22 Aug 2016 15:59:24 +0200 Aurelien Jarno 
> wrote:
>> Dear Maintainer,
>>
>> schroot provides an initscript which can take quite some time to
>> execute, for example if configured to end up all active sessions. When
>> running under systemd, it is often killed after the default 90 seconds
>> timeout. This happens regularly on the Debian porterboxes where many
>> users leave their chroot sessions opened.
>>
>> The solution is probably to provide a systemd service file running in
>> oneshot mode, so that it defaults to no timeout.
>
> I've attached here a patch to add a .service file, it calls the initscript,
> this is a quick solution but it should work.

A better solution would be to move the program part out into a script
in /usr/lib, and have both the init script and service file call out
to that. This wat if the logic changes updates are consistently
delivered to users.

I agree though that this is a quick and good enough solution.

>
> I didn't add any dependency against LVM because the VG should already for
> all services that have DefaultDependencies=yes (the default) defined.
>
> I also see that the LSB initscript has a dependency against the network, any
> idea why this is needed? Was this necessary to guarantee the network shares?
> Or was it for something else?
>
> Maybe a RequiresMountsFor=/var/lib/schroot could also be added?

I think it should be added, yes. In practice, it should have little
effect though, otherwise schroot would have bugs filed about this.

>
> On my laptop, schroot is the last LSB initscript without equivalent that
> requires the $network facility, in some situation, this makes the boot stall
> for around 20s (as it waits for the network to come online). Could it still
> be an option to add that for stretch?
>

As an interested user, thanks for the patch!

-- 

Saludos,
Felipe Sateler



Bug#809669: unattended-upgrades: files got created under /var/ mountpoint

2017-02-15 Thread Louis Bouchard
Hello,

I may be wrong, but this clearly shows that the Unattended Upgrades Shutdown
unit starts once the target Network is being brought down :

> Feb 15 12:35:52 ZunattendedUpgrade systemd[1]: Stopped target Network is 
> Online.
> Feb 15 12:35:52 ZunattendedUpgrade systemd[1]: Stopped target Network.
> Feb 15 12:35:52 ZunattendedUpgrade systemd[1]: Started Unattended Upgrades 
> Shutdown.
> Feb 15 12:35:52 ZunattendedUpgrade systemd[1]: Stopping ifup for ens3...
> Feb 15 12:35:52 ZunattendedUpgrade systemd[1]: Stopping Raise network 
> interfaces...
> Feb 15 12:35:52 ZunattendedUpgrade systemd[1]: Reloading.
> Feb 15 12:35:52 ZunattendedUpgrade systemd[1]: Reloading.
> Feb 15 12:35:52 ZunattendedUpgrade dhclient[2799]: Killed old client process
> Feb 15 12:35:52 ZunattendedUpgrade ifdown[2765]: Killed old client process
> Feb 15 12:35:52 ZunattendedUpgrade systemd[1]: Reloading.
> Feb 15 12:35:52 ZunattendedUpgrade systemd[1]: Stopped Raise network 
> interfaces.
> Feb 15 12:35:53 ZunattendedUpgrade dhclient[2799]: Internet Systems 
> Consortium DHCP Client 4.3.3
> Feb 15 12:35:53 ZunattendedUpgrade ifdown[2765]: Internet Systems Consortium 
> DHCP Client 4.3.3
> Feb 15 12:35:53 ZunattendedUpgrade ifdown[2765]: Copyright 2004-2015 Internet 
> Systems Consortium.
> Feb 15 12:35:53 ZunattendedUpgrade ifdown[2765]: All rights reserved.
> Feb 15 12:35:53 ZunattendedUpgrade ifdown[2765]: For info, please visit 
> https://www.isc.org/software/dhcp/
> Feb 15 12:35:53 ZunattendedUpgrade dhclient[2799]: Copyright 2004-2015 
> Internet Systems Consortium.
> Feb 15 12:35:53 ZunattendedUpgrade dhclient[2799]: All rights reserved.
> Feb 15 12:35:53 ZunattendedUpgrade dhclient[2799]: For info, please visit 
> https://www.isc.org/software/dhcp/
> Feb 15 12:35:53 ZunattendedUpgrade dhclient[2799]: 
> Feb 15 12:35:53 ZunattendedUpgrade dhclient[2799]: Listening on 
> LPF/ens3/52:54:00:69:a4:c4
> Feb 15 12:35:53 ZunattendedUpgrade ifdown[2765]: Listening on 
> LPF/ens3/52:54:00:69:a4:c4
> Feb 15 12:35:53 ZunattendedUpgrade ifdown[2765]: Sending on   
> LPF/ens3/52:54:00:69:a4:c4
> Feb 15 12:35:53 ZunattendedUpgrade ifdown[2765]: Sending on   Socket/fallback
> Feb 15 12:35:53 ZunattendedUpgrade dhclient[2799]: Sending on   
> LPF/ens3/52:54:00:69:a4:c4
> Feb 15 12:35:53 ZunattendedUpgrade dhclient[2799]: Sending on   
> Socket/fallback
> Feb 15 12:35:53 ZunattendedUpgrade dhclient[2799]: DHCPRELEASE on ens3 to 
> 192.168.1.1 port 67 (xid=0x3e07e0e5)
> Feb 15 12:35:53 ZunattendedUpgrade ifdown[2765]: DHCPRELEASE on ens3 to 
> 192.168.1.1 port 67 (xid=0x3e07e0e5)
> Feb 15 12:35:53 ZunattendedUpgrade systemd[1]: Stopped ifup for ens3.

Pinging google for 4 seconds is not sufficient, the Unattended upgrade shutdown
can run for saveral minutes before completing.

HTH,

Kind regards,

...Louis


-- 
Louis Bouchard
Software engineer, Cloud & Sustaining eng.
Canonical Ltd
Ubuntu developer   Debian Maintainer
GPG : 429D 7A3B DD05 B6F8 AF63  B9C4 8B3D 867C 823E 7A61



Bug#855207: owncloud: ownCloud cannot be updated because of wrong dependency information, see ownCloud Issue 26999

2017-02-15 Thread ViaThinkSoft
Package: owncloud
Version: 8.1.9-12.1
Severity: grave
Justification: renders package unusable

See:
https://github.com/owncloud/core/issues/26999
and
https://central.owncloud.org/t/debian-package-conflict-how-to-update-owncloud/5753



-- 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/8 CPU cores)
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages owncloud depends on:
ii  owncloud-server  8.1.9-12.1

Versions of packages owncloud recommends:
ii  curl7.38.0-4+deb8u5
ii  mysql-server5.5.54-0+deb8u1
ii  owncloud-config-apache  8.1.9-12.1
ii  postfix [mail-transport-agent]  2.11.3-1

Versions of packages owncloud suggests:
ii  clamav  0.99.2+dfsg-0+deb8u2
ii  clamav-daemon   0.99.2+dfsg-0+deb8u2
pn  libreoffice-writer  
ii  smbclient   2:4.2.14+dfsg-0+deb8u2

-- no debconf information



Bug#855204: libpetsc3.7.5-dev: uninstallable - Depends: libopenmpi-dev (< 2.0.2~git.20161226)

2017-02-15 Thread Mattia Rizzolo
Control: reassign -1 release.debian.org
Control: forcemerge 854905 -1

On Wed, Feb 15, 2017 at 01:09:16PM +, James Cowgill wrote:
> Package: libpetsc3.7.5-dev
> Version: 3.7.5+dfsg1-3
> Severity: serious
> Tags: sid stretch

Please look for already reported bugs before reporting new ones (there
is an "affect" so it is in libpetsc3.7.5-dev bugs list).

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#855204: libpetsc3.7.5-dev: uninstallable - Depends: libopenmpi-dev (< 2.0.2~git.20161226)

2017-02-15 Thread James Cowgill
On 15/02/17 13:41, Mattia Rizzolo wrote:
> Control: reassign -1 release.debian.org
> Control: forcemerge 854905 -1
> 
> On Wed, Feb 15, 2017 at 01:09:16PM +, James Cowgill wrote:
>> Package: libpetsc3.7.5-dev
>> Version: 3.7.5+dfsg1-3
>> Severity: serious
>> Tags: sid stretch
> 
> Please look for already reported bugs before reporting new ones (there
> is an "affect" so it is in libpetsc3.7.5-dev bugs list).

Well I did check petsc (not release.debian.org), but affects on binary
packages don't actually show up on the main bugs page - #636689

James



signature.asc
Description: OpenPGP digital signature


Bug#855206: fvwm: When xterm quits, fvwm doesn't always remove its window immediately

2017-02-15 Thread Vincent Lefevre
On 2017-02-15 14:31:43 +0100, Vincent Lefevre wrote:
> When xterm quits, fvwm doesn't always remove its window immediately;
> it remains on screen for several seconds. During this time, when the
> mouse pointer is over this xterm window, the pointer disappears.
> That's why I think that this is a fvwm issue, since I do not obtain
> this behavior with xterm (+ the screenshot issue below).

I'd add that the screenshot issue is reproducible, and while the
window is still shown, the xterm process no longer appears in the
ps output.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#792205: Fusioninventory in stretch ?

2017-02-15 Thread Andreas Beckmann
On 2017-02-15 14:22, Adrien Grellier wrote:
> Do you think fusioninventory will made its way to stretch ?

I'm sorry, but it's too late for that (deadline was Jan 5th).

> The freeze is here, I see no package in testing, but only this bug is
> blocking. In my lab, we are using fusioninventory a lot on Debian, so I
> am very interesting to have it for the next stable version.

Looks like the package is not actively maintained (last upload of
version 2.3.16 in June 2015, current upstream is 2.3.18 from06/20/2016)


Andreas



Bug#855208: runc: 1.0 release candidate breaks docker 1.11 - oci runtime error: flag provided but not defined: -bundle

2017-02-15 Thread Felipe Sateler
Package: runc
Version: 1.0.0~rc2+git20161109.131.5137186-1
Severity: grave
Justification: renders docker unusable
Control: affects -1 docker.io

After upgrading to 1.0.0~rc2+git20161109.131.5137186-1 , docker
containers fail to start:

 Cannot start service web: rpc error: code = 2 desc = "oci runtime error: flag 
provided but not defined: -bundle"

I don't know what docker version allows usage of runc 1.0 rc.

I'm tagging the severity as grave since runc appears to be a component
of docker (there are no other rdeps), and docker fails to work with this
version.

Saludos

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

Kernel: Linux 4.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 /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages runc depends on:
ii  libapparmor1  2.11.0-2
ii  libc6 2.24-9
ii  libseccomp2   2.3.1-2.1

runc recommends no packages.

runc suggests no packages.

-- no debconf information



Bug#855035: debian-installer: https does not work with stretch rc2 installer

2017-02-15 Thread Cyril Brulebois
Cyril Brulebois  (2017-02-14):
> Philipp Kern  (2017-02-14):
> > Given that Steve added it to the CD's force list, what about adding the two
> > packages to $include in the https check that already exists in
> > bootstrap-base.postinst (to set the proxy correctly)? I don't see a good way
> > of adding the two packages after debootstrap ran but telling debootstrap to
> > pull them in upon initial installation, assuming the media has it, seems
> > feasible to me.
> 
> That's exactly the solution I came up with while thinking about it. Since
> you agree I suppose this makes it a reasonable solution, and I'll be
> implementing and checking that in a moment. Thanks for the quick feedback.

I should clarify a bit: we can't look at PROTOCOL at this point, since a
netinst with mirror/protocol=https is going to use local files on the
cdrom; if it was using https, debootstrap would do the job already
(except it would fail to load both packages right now since Steve only
added them to the images a few hours ago).

So I'm adding a mirror/protocol check instead, and I have to adjust
include/exclude handling accordingly.

KiBi.


signature.asc
Description: Digital signature


Bug#855035: debian-installer: https does not work with stretch rc2 installer

2017-02-15 Thread Cyril Brulebois
Cyril Brulebois  (2017-02-15):
> I should clarify a bit: we can't look at PROTOCOL at this point, since a
> netinst with mirror/protocol=https is going to use local files on the
> cdrom; if it was using https, debootstrap would do the job already
> (except it would fail to load both packages right now since Steve only
> added them to the images a few hours ago).

Eww, we have this code right now already:
|   # If we need SSL certificates, copy them in now.
|   if [ "$PROTOCOL" = "https" ] && [ -d /etc/ssl/certs ]; then
|   if find /etc/ssl/certs/ -name \*.crt | grep -q .; then
|   mkdir -p /target/usr/local/share/ca-certificates
|   cp -a /etc/ssl/certs/*.crt 
/target/usr/local/share/ca-certificates/
|   chroot /target update-ca-certificates || true
|   fi
|   fi

→ It's likely not getting run with netinst images…

I think I'll file this as another bug report for reference.


KiBi.


signature.asc
Description: Digital signature


Bug#855206: fvwm: When xterm quits, fvwm doesn't always remove its window immediately

2017-02-15 Thread Vincent Lefevre
On 2017-02-15 14:31:43 +0100, Vincent Lefevre wrote:
> When this happens, this is always with a special script. This may mean
> that the bug occurs only under some particular conditions. One of them
> that might matter is that the window title changes just before xterm
> quits (new title: TITLEDISABLED).

I've noticed another difference: contrary to the other xterm
processes, this one is no longer a descendent of the fvwm2
process. But the bug is reproducible even when I change my
script to make xterm a descendent of fvwm2 (the script normally
runs xterm in the background before quitting).

It seems that the window remains on screen until some particular
fvwm operation makes it disappear. In particular, I have:

Mouse 0 1   A   Windowops-or-Die

where Windowops-or-Die opens a menu. I was getting this menu
when I clicked on the title-bar button 1, but when I selected
"Module FvwmIdent", the window disappeared.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



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

2017-02-15 Thread Patrick Ohly
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.

> > 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?

> > 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.

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.

> Comes from a lot of facepalming. My car supports my phones contacts
> quite well. And all Mercedes cars I get to drive sometimes almost
> perfectly. But in the Linux land, well, when I apt-cache-search for
> "bluetooth contact" the only thing I find is syncevolution and sync-ui
> and it's apparently totally useless with modern phones.

Some people still use older feature phones with it. Others synchronize
against a CalDAV/CardDAV service.

Lack of local synchronization is basically a result of device
manufacturers no longer supporting it, and customers not caring enough
to complain. Not much that can be done about either of these.

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.



Bug#849065: janus depends on libsrtp-dev (>= 1.5)

2017-02-15 Thread Victor Seva
2017-02-05 15:53 GMT+01:00 Jonas Smedegaard :
> Quoting Victor Seva (2016-12-22 14:05:03)
>
> Concretely for Janus the better solution than waiting (in vein) for
> libsrtp 1.5 is to instead link with libsrtp2.
>
> I have a succesful build with a few upstrem-cherrypicked pathes to fix
> linking with libsrtp2.

Perfect

>> Let's try to work to get Janus packaged, no matter if it gets into
>> stretch or not
>
> Would you mind me applying those to the Debian git?
>
> And more generally, would you like me to add myself as co-maintainer and
> hack along without asking you each time?  Even release at will too?  Or
> what level of coordination would you prefer?

Sure, go ahead and hack, just ping me before release anything



Bug#855210: kernel BUG at /home/zumbi/linux-4.9.2/fs/ocfs2/dlm/dlmast.c:306!

2017-02-15 Thread Russell Mosemann
Package: src:linux
Version: 4.9.2-2~bpo8+1
Severity: important

Dear Maintainer,

   * What led up to the situation?
The server had unexpectedly rebooted. Upon reboot, several DRBD drives were 
resynching when the bug was exposed. The system was forced to reboot, again.

Feb 15 07:53:47 vhost172 kernel: block drbd1: helper command: /sbin/drbdadm 
after-resync-target minor-1 exit code 0 (0x0)
Feb 15 07:54:07 vhost172 kernel: 
(kworker/u24:3,221,11):dlm_proxy_ast_handler:306 ERROR: bug expression: 
!dlm_domain_fully_joined(dl
m)
Feb 15 07:54:07 vhost172 kernel: 
(kworker/u24:3,221,11):dlm_proxy_ast_handler:306 ERROR: Domain 
930824A27206493B9F8823F4B9D780E9 not
 fully joined!
Feb 15 07:54:07 vhost172 kernel: [ cut here ]
Feb 15 07:54:07 vhost172 kernel: kernel BUG at 
/home/zumbi/linux-4.9.2/fs/ocfs2/dlm/dlmast.c:306!
Feb 15 07:54:08 vhost172 kernel: invalid opcode:  [#1] SMP
Feb 15 07:54:08 vhost172 kernel: Modules linked in: ocfs2 quota_tree hmac veth 
iptable_filter ip_tables x_tables nfsd auth_rpcgss nfs_acl nfs lockd grace 
fscache sunrpc ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager 
ocfs2_stackglue configfs bridge stp llc bonding intel_rapl sb_edac edac_core 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm xhci_pci ast 
xhci_hcd irqbypass crct10dif_pclmul ttm crc32_pclmul ehci_pci 
ghash_clmulni_intel drm_kms_helper ehci_hcd iTCO_wdt iTCO_vendor_support 
intel_cstate mxm_wmi evdev igb drm e1000e mei_me intel_uncore dca usbcore 
lpc_ich pcspkr sg ptp mei i2c_algo_bit intel_rapl_perf mfd_core pps_core 
i2c_i801 usb_common shpchp i2c_smbus ipmi_si ipmi_msghandler wmi fjes tpm_tis 
tpm_tis_core tpm acpi_power_meter acpi_pad button fuse drbd lru_cache libcrc32c 
crc32c_generic
Feb 15 07:54:08 vhost172 kernel:  autofs4 ext4 crc16 jbd2 fscrypto mbcache 
dm_mod md_mod sd_mod crc32c_intel ahci libahci aesni_intel libata aes_x86_64 
glue_helper lrw gf128mul ablk_helper cryptd scsi_mod
Feb 15 07:54:08 vhost172 kernel: CPU: 11 PID: 221 Comm: kworker/u24:3 Not 
tainted 4.9.0-0.bpo.1-amd64 #1 Debian 4.9.2-2~bpo8+1
Feb 15 07:54:08 vhost172 kernel: Hardware name: To Be Filled By O.E.M. To Be 
Filled By O.E.M./EPC612D4I, BIOS P2.10 03/31/2016
Feb 15 07:54:08 vhost172 kernel: Workqueue: o2net o2net_rx_until_empty 
[ocfs2_nodemanager]
Feb 15 07:54:08 vhost172 kernel: task: 971bf59f8000 task.stack: 
a95886d6c000
Feb 15 07:54:08 vhost172 kernel: RIP: 0010:[]  
[] dlm_proxy_ast_handler+0x734/0x770 [ocfs2_dlm]
Feb 15 07:54:08 vhost172 kernel: RSP: 0018:a95886d6fcf8  EFLAGS: 00010246
Feb 15 07:54:08 vhost172 kernel: RAX:  RBX: 970ddfcc 
RCX: 
Feb 15 07:54:08 vhost172 kernel: RDX:  RSI: 971bff4ce008 
RDI: 971bff4ce008
Feb 15 07:54:08 vhost172 kernel: RBP: 970ded7a4c00 R08: 0478 
R09: 000a
Feb 15 07:54:08 vhost172 kernel: R10: a95886d6fc88 R11: 0478 
R12: 971bf5346200
Feb 15 07:54:08 vhost172 kernel: R13: eeef R14: f6664f90 
R15: 971bf4c55500
Feb 15 07:54:08 vhost172 kernel: FS:  () 
GS:971bff4c() knlGS:
Feb 15 07:54:08 vhost172 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
Feb 15 07:54:08 vhost172 kernel: CR2: 7f0b781c1162 CR3: 21007000 
CR4: 001406e0
Feb 15 07:54:08 vhost172 kernel: Stack:
Feb 15 07:54:08 vhost172 kernel:  3261 971bf5346200 
eeef 01f0
Feb 15 07:54:08 vhost172 kernel:  0246 8aae79cd 
971bf53462c0 c0a047c9
Feb 15 07:54:08 vhost172 kernel:  1040 ce37533f 
971bf5346218 970ddfcc
Feb 15 07:54:08 vhost172 kernel: Call Trace:
Feb 15 07:54:08 vhost172 kernel:  [] ? mod_timer+0x18d/0x300
Feb 15 07:54:08 vhost172 kernel:  [] ? 
o2net_handler_tree_lookup+0x49/0xd0 [ocfs2_nodemanager]
Feb 15 07:54:08 vhost172 kernel:  [] ? 
o2net_rx_until_empty+0x8b4/0xcd0 [ocfs2_nodemanager]
Feb 15 07:54:08 vhost172 kernel:  [] ? 
process_one_work+0x14b/0x410
Feb 15 07:54:08 vhost172 kernel:  [] ? 
worker_thread+0x65/0x4a0
Feb 15 07:54:08 vhost172 kernel:  [] ? 
rescuer_thread+0x340/0x340
Feb 15 07:54:08 vhost172 kernel:  [] ? do_group_exit+0x39/0xb0
Feb 15 07:54:08 vhost172 kernel:  [] ? kthread+0xe0/0x100
Feb 15 07:54:08 vhost172 kernel:  [] ? __switch_to+0x2bb/0x700
Feb 15 07:54:08 vhost172 kernel:  [] ? kthread_park+0x60/0x60
Feb 15 07:54:08 vhost172 kernel:  [] ? ret_from_fork+0x25/0x30
Feb 15 07:54:08 vhost172 kernel: Code: 00 00 00 00 00 00 10 48 8d 7c 24 40 48 
89 44 24 40 48 c7 c1 0a 20 bb c0 ba 32 01 00 00 48 c7 c6 30 89 ba c0 31 c0 e8 
9c 11 e6 ff <0f> 0b 4d 89 e9 48 b8 ff ff ff ff ff ff ff 00 48 c7 44 24 40 40
Feb 15 07:54:08 vhost172 kernel: RIP  [] 
dlm_proxy_ast_handler+0x734/0x770 [ocfs2_dlm]
Feb 15 07:54:08 vhost172 kernel:  RSP 
Feb 15 07:54:08 vhost172 kernel: ---[ end trace c2285c3c100bca16 ]---
Feb 15 07:54:08 vhost172 kernel: BUG: unable

Bug#855209: systemd ignores configuration for getty when switching and autostarting a new vt

2017-02-15 Thread Salvo Tomaselli
Package: systemd
Version: 232-18
Severity: normal

Dear Maintainer,
I want to have logs on tty6, rather than a login shell.

I created a file called /etc/systemd/system/getty@tty6.service

What happens is that if I press ctrl+alt+f6, I get a login shell.

However, if after that I give

# service getty@tty6 stop
# service getty@tty6 start

and then switch again to tty6 with ctrl+alt+f6, then I will see
the wanted tail of logs.

I tried with daemon-reload, but the issue remains present, when switching
to a vt that doesn't exist, systemd always uses the generic getty@.service
file, ignoring the instance specific configuration.

Attaching my .service file

Best

-- Package-specific info:

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

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

Versions of packages systemd depends on:
ii  adduser 3.115
ii  libacl1 2.2.52-3
ii  libapparmor12.11.0-2
ii  libaudit1   1:2.6.7-1
ii  libblkid1   2.29.1-1
ii  libc6   2.24-9
ii  libcap2 1:2.25-1
ii  libcryptsetup4  2:1.7.3-3
ii  libgcrypt20 1.7.6-1
ii  libgpg-error0   1.26-2
ii  libidn111.33-1
ii  libip4tc0   1.6.0+snapshot20161117-5
ii  libkmod223-2
ii  liblz4-10.0~r131-2
ii  liblzma55.2.2-1.2
ii  libmount1   2.29.1-1
ii  libpam0g1.1.8-3.5
ii  libseccomp2 2.3.1-2.1
ii  libselinux1 2.6-3
ii  libsystemd0 232-18
ii  mount   2.29.1-1
ii  util-linux  2.29.1-1

Versions of packages systemd recommends:
ii  dbus1.10.14-1
ii  libpam-systemd  232-18

Versions of packages systemd suggests:
ii  policykit-10.105-17
pn  systemd-container  
pn  systemd-ui 

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.127
ii  udev 232-18

-- no debconf information
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

[Unit]
Description=tty logger on %I
After=systemd-user-sessions.service plymouth-quit-wait.service
After=rc-local.service

# If additional gettys are spawned during boot then we should make
# sure that this is synchronized before getty.target, even though
# getty.target didn't actually pull it in.
Before=getty.target
IgnoreOnIsolate=yes

# IgnoreOnIsolate causes issues with sulogin, if someone isolates
# rescue.target or starts rescue.service from multi-user.target or
# graphical.target.
Conflicts=rescue.service
Before=rescue.service

# On systems without virtual consoles, don't start any getty. Note
# that serial gettys are covered by serial-getty@.service, not this
# unit.
ConditionPathExists=/dev/tty0

[Service]

Type=simple
ExecStart=/bin/journalctl -f
StandardOutput=tty
UtmpIdentifier=%I
TTYPath=/dev/%I
TTYReset=no
TTYVHangup=no
TTYVTDisallocate=no
KillMode=process
IgnoreSIGPIPE=no
SendSIGHUP=no

# Unset locale for the console getty since the console has problems
# displaying some internationalized messages.
Environment=LANG= LANGUAGE= LC_CTYPE= LC_NUMERIC= LC_TIME= LC_COLLATE= 
LC_MONETARY= LC_MESSAGES= LC_PAPER= LC_NAME= LC_ADDRESS= LC_TELEPHONE= 
LC_MEASUREMENT= LC_IDENTIFICATION=

[Install]
WantedBy=getty.target
DefaultInstance=tty6


Bug#855211: ITP: qcumber -- quality control of genomic sequences

2017-02-15 Thread Andreas Tille
Package: wnpp
Severity: wishlist
Owner: Andreas Tille 

* Package name: qcumber
  Version : 1.0.5
  Upstream Author : Vivi Lieu 
* URL : https://gitlab.com/RKIBioinformaticsPipelines/QCumber
* License : LGPL
  Programming Lang: Python
  Description : quality control of genomic sequences
 QCPipeline is a tool for quality control. The workflow is as follows:
 .
  1. Quality control with FastQC
  2. Trim Reads with Trimmomatic
  3. Quality control of trimmed reads with FastQC
  4. Map reads against reference using bowtie2
  5. Classify reads with Kraken



Bug#855114: unblock (pre-approval): nginx/1.10.3-1

2017-02-15 Thread Christos Trochalakis

On Tue, Feb 14, 2017 at 05:12:00PM +, Niels Thykier wrote:

Control: tags -1 confirmed

Christos Trochalakis:

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

*I have not yet uploaded to unstable*, and I am asking for pre-approval
to upload 1.10.3-1.

1.10.3-1 will only include the new upstream release (1.10.2 -> 1.10.3)
and no packaging changes.

Nginx 1.10.3 is a stable bugfix release that handles 8 bugfixes
including a segmentation fault.

Relevant bug report: https://bugs.debian.org/855113
Changelog: https://nginx.org/en/CHANGES-1.10
Diff:
https://github.com/nginx/nginx/compare/release-1.10.2...release-1.10.3

Thank you!



Ok, please go ahead and upload that to unstable (I assuming there are
not changes to the debian/ beyond on the d/changelog).

Thanks,
~Niels



Thanks, I have uploaded nginx-1.10.3-1 to unstable.

I took the liberty to also piggyback a change to our VCS location in d/control:

nginx-1.10.2/debian/control nginx-1.10.3/debian/control
--- nginx-1.10.2/debian/control 2017-01-22 12:19:30.0 +0200
+++ nginx-1.10.3/debian/control 2017-02-15 09:58:13.0 +0200
@@ -27,8 +27,8 @@
   zlib1g-dev
Standards-Version: 3.9.8.0
Homepage: http://nginx.net
-Vcs-Git: https://anonscm.debian.org/cgit/collab-maint/nginx.git
-Vcs-Browser: https://anonscm.debian.org/cgit/collab-maint/nginx.git
+Vcs-Git: https://anonscm.debian.org/cgit/pkg-nginx/nginx.git
+Vcs-Browser: https://anonscm.debian.org/cgit/pkg-nginx/nginx.git



Bug#855212: emacs25-common: nxml-mode regards XML as valid though it contains an invalid character

2017-02-15 Thread Vincent Lefevre
Package: emacs25-common
Version: 25.1+1-3
Severity: normal

Consider the file generated by:

  printf '\n\f\n'

i.e. a file that contains a ^L character.

nXML regards this file as valid XML, while the ^L character is invalid
in XML 1.0: https://www.w3.org/TR/2006/REC-xml-20060816/#charsets

As a comparison, xmllint complains:

file.xml:2: parser error : PCDATA invalid Char value 12

  
  ^

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

Kernel: Linux 4.9.0-1-amd64 (SMP w/12 CPU cores)
Locale: LANG=POSIX, 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 emacs25-common depends on:
ii  dpkg1.18.22
ii  emacsen-common  2.0.8
ii  install-info6.3.0.dfsg.1-1+b1

Versions of packages emacs25-common recommends:
ii  emacs25-el  25.1+1-3

Versions of packages emacs25-common suggests:
ii  emacs25-common-non-dfsg  25.1+1-1
ii  ncurses-term 6.0+20161126-1

-- no debconf information



Bug#854103: grub-pc: Wrong detection of the initramfs file of Arch Linux

2017-02-15 Thread Khurram Mahmood
Hi

I upgraded to stretch and the problem persists.

Thankyou.

*(Khurram Mahmood)*


On 4 February 2017 at 10:54, Khurram Mahmood  wrote:

> Package: grub-pc
> Version: 2.02~beta2-22+deb8u1
> Severity: important
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate
> ***
>
>* What led up to the situation?
>
> running update-grub I get in /boot/grub/grub.cfg:
> [code] initrd /boot/intel-ucode.img[/code]
>
> The rest output seems fine.
>
> The result is the unbootable system. Then I have to manually correct this.
> The interesting thing is that I have another arch installation, which is
> detected okay.
>
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>* What was the outcome of this action?
>* What outcome did you expect instead?
>
> *** End of the template - remove these template lines ***
>
>
> -- Package-specific info:
>
> *** BEGIN /proc/mounts
> /dev/sda5 / ext4 rw,relatime,errors=remount-ro,commit=600,data=ordered 0 0
> /dev/sda4 /media/hdd/sda4 ext4 rw,relatime,commit=600,data=ordered 0 0
> /dev/sda2 /media/hdd/sda2 ext4 rw,relatime,commit=600,data=ordered 0 0
> /dev/sda3 /media/hdd/sda3 ext4 rw,relatime,commit=600,data=ordered 0 0
> /dev/sda6 /media/hdd/sda6 ext4 rw,relatime,commit=600,data=ordered 0 0
> *** END /proc/mounts
>
> *** BEGIN /boot/grub/grub.cfg
> #
> # DO NOT EDIT THIS FILE
> #
> # It is automatically generated by grub-mkconfig using templates
> # from /etc/grub.d and settings from /etc/default/grub
> #
>
> ### BEGIN /etc/grub.d/00_header ###
> if [ -s $prefix/grubenv ]; then
>   set have_grubenv=true
>   load_env
> fi
> if [ "${next_entry}" ] ; then
>set default="${next_entry}"
>set next_entry=
>save_env next_entry
>set boot_once=true
> else
>set default="4"
> fi
>
> if [ x"${feature_menuentry_id}" = xy ]; then
>   menuentry_id_option="--id"
> else
>   menuentry_id_option=""
> fi
>
> export menuentry_id_option
>
> if [ "${prev_saved_entry}" ]; then
>   set saved_entry="${prev_saved_entry}"
>   save_env saved_entry
>   set prev_saved_entry=
>   save_env prev_saved_entry
>   set boot_once=true
> fi
>
> function savedefault {
>   if [ -z "${boot_once}" ]; then
> saved_entry="${chosen}"
> save_env saved_entry
>   fi
> }
> function load_video {
>   if [ x$feature_all_video_module = xy ]; then
> insmod all_video
>   else
> insmod efi_gop
> insmod efi_uga
> insmod ieee1275_fb
> insmod vbe
> insmod vga
> insmod video_bochs
> insmod video_cirrus
>   fi
> }
>
> if [ x$feature_default_font_path = xy ] ; then
>font=unicode
> else
> insmod part_gpt
> insmod ext2
> set root='hd0,gpt5'
> if [ x$feature_platform_search_hint = xy ]; then
>   search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt5
> --hint-efi=hd0,gpt5 --hint-baremetal=ahci0,gpt5  b635f48f-40fe-4a54-8fac-
> f5953137b67e
> else
>   search --no-floppy --fs-uuid --set=root b635f48f-40fe-4a54-8fac-
> f5953137b67e
> fi
> font="/usr/share/grub/unicode.pf2"
> fi
>
> if loadfont $font ; then
>   set gfxmode=auto
>   load_video
>   insmod gfxterm
>   set locale_dir=$prefix/locale
>   set lang=en_US
>   insmod gettext
> fi
> terminal_output gfxterm
> if [ "${recordfail}" = 1 ] ; then
>   set timeout=-1
> else
>   if [ x$feature_timeout_style = xy ] ; then
> set timeout_style=menu
> set timeout=3
>   # Fallback normal timeout code in case the timeout_style feature is
>   # unavailable.
>   else
> set timeout=3
>   fi
> fi
> ### END /etc/grub.d/00_header ###
>
> ### BEGIN /etc/grub.d/05_debian_theme ###
> insmod part_gpt
> insmod ext2
> set root='hd0,gpt5'
> if [ x$feature_platform_search_hint = xy ]; then
>   search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt5
> --hint-efi=hd0,gpt5 --hint-baremetal=ahci0,gpt5  b635f48f-40fe-4a54-8fac-
> f5953137b67e
> else
>   search --no-floppy --fs-uuid --set=root b635f48f-40fe-4a54-8fac-
> f5953137b67e
> fi
> insmod png
> if background_image /usr/share/images/desktop-base/lines-grub.png; then
>   set color_normal=white/black
>   set color_highlight=black/white
> else
>   set menu_color_normal=cyan/blue
>   set menu_color_highlight=white/blue
> fi
> ### END /etc/grub.d/05_debian_theme ###
>
> ### BEGIN /etc/grub.d/10_linux ###
> function gfxmode {
> set gfxpayload="${1}"
> }
> set linux_gfx_mode=
> export linux_gfx_mode
> menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu
> --class os $menuentry_id_option 
> 'gnulinux-simple-b635f48f-40fe-4a54-8fac-f5953137b67e'
> {
> load_video
> insmod gzio
> if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
> insmod part_gpt
> insmod ext2
> set root='hd0,gpt5'
> if [ x$feature_platform_search_hint = xy ]; then
>   search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt5
> --hint-efi=hd0,gpt5 --hint-baremetal=ahci0

Bug#855214: unblock: asterisk/1:13.14.0~dfsg-1 (pre-approval)

2017-02-15 Thread Bernhard Schmidt
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Hi,

I would like to request permission to update Asterisk in Stretch to a new
upstream release (13.13.2 to 13.14.0). This version has mostly bugfixes 
but only very minor new features.

Unfortunately a couple of bugs have surfaced that make Asterisk in Stretch
close to unusable in certain configurations. They are priority important right
now but are borderline RC for some system configurations

Bug#853792: Asterisk does not work at all on systems without IPv6. Only viable
workaround is to enable IPv6

Bug#855014: The chan_pjsip driver has a broken codec selection that leads
to asymetric codecs being negotiated with the endpoint, leading to
one-way audio. The only viable workaround is to limit codecs on the
phone to just one codec.

Both commits could be backported, but this would make it harder to support
during the lifetime of Stretch. Additionally there are a tons of other fixes
in this version that sound good-to-have in Stretch (memory leaks etc.). 

Additionally it would allow us to drop two patches that have been included
upstream and our OpenSSL 1.1.0 support would be much closer to upstream (we
cannot drop all patches because something is still missing, but all remaining
patches are already queued in upstreams CI for merging). 

There are no changes in packaging besides debian/patches.

The package is currently in experimental as asterisk/1:13.14.0~dfsg-1~exp1.
I'm asking for approval for upload to unstable. 

Bernhard



Bug#855215: libstatgrab error

2017-02-15 Thread Erik Thiele
Package: bwm-ng
Version: 0.6-3.1+b1

I am running amd64.
cat /etc/debian_version 
8.7
system is fully updated.

ii  libstatgrab9   0.90-1.2 amd64

start bwm-ng. it displays networking statistics. press the 'n'
key and it sais "libstatgrab error!" and terminates.

I got no clue how to debug.


cya
erik



Bug#855216: unblock: singularity-container/2.2-2

2017-02-15 Thread Yaroslav Halchenko
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package singularity-container

2.2 release contained a vulnerability described in detail upstream
https://github.com/singularityware/singularity/releases/tag/2.2.1 :
In versions of Singularity previous to 2.2.1, it was possible for a malicious 
user to create and manipulate specifically crafted raw devices within 
containers they own. Utilizing MS_NODEV as a container image mount option 
mitigates this potential vector of attack. As a result, this update should be 
implemented with high urgency. A big thanks to Mattias Wadenstein (@UMU in 
Sweden) for identifying and reporting this issue!

2.2-2 (debdiff attached) was prepared in collaboration with upstream to cover
that vulnerability and address few other possibly security related (snprintf)
and  functionality related issues.  security@d.o was provided with debdiff and
no negative opinions were expressed.

unblock singularity-container/2.2-2

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100, 
'unstable-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-1-amd64 (SMP w/4 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)
diff -Nru singularity-container-2.2/debian/changelog 
singularity-container-2.2/debian/changelog
--- singularity-container-2.2/debian/changelog  2016-11-30 12:33:01.0 
-0500
+++ singularity-container-2.2/debian/changelog  2017-02-09 16:27:55.0 
-0500
@@ -1,3 +1,24 @@
+singularity-container (2.2-2) unstable; urgency=high
+
+  * debian/patches - picks up from upcoming 2.2.1 release
+critical functionality and possibly security-related fixes
+- changeset_b859cd8b4b9293f2a8a893ef41c5d93a5318dd6c.diff
+  to support mounting ext4 formatted images read-only
+- changeset_f79e853d9ee8a15b1d16cdc7dfbe85eca50efc6d.diff
+  to utilize mount option MS_NODEV for images
+  (fixes potential security implications)
+- changeset_d835fa1d20efc4aaacca4be68431d193d6625bd8.diff
+  to fix bootstrapping ran as root (thus no MS_NODEV restriction
+  from above patch should be applied)
+- changeset_3a2b6537f0b1386336e29d7f763ae62374a7cb77.diff
+  exit with error if snprintf would have went out of bounds
+- changeset_acc02b921192e7e16afe1513d5338904f8e6f907.diff
+  changeset_0935d68145ce575444b7ced43417cc6fccffd670.diff
+  changeset_0d04edaeb5cb3607ab25588f4db177c0878adcc0.diff
+  Various obvious fixes (updated URLs, apt --force-yes)
+
+ -- Yaroslav Halchenko   Thu, 09 Feb 2017 16:27:55 -0500
+
 singularity-container (2.2-1) unstable; urgency=medium
 
   [ Mehdi Dogguy ]
diff -Nru 
singularity-container-2.2/debian/patches/changeset_0935d68145ce575444b7ced43417cc6fccffd670.diff
 
singularity-container-2.2/debian/patches/changeset_0935d68145ce575444b7ced43417cc6fccffd670.diff
--- 
singularity-container-2.2/debian/patches/changeset_0935d68145ce575444b7ced43417cc6fccffd670.diff
1969-12-31 19:00:00.0 -0500
+++ 
singularity-container-2.2/debian/patches/changeset_0935d68145ce575444b7ced43417cc6fccffd670.diff
2017-02-09 16:27:55.0 -0500
@@ -0,0 +1,21 @@
+From: Gregory M. Kurtzer 
+Subject: Use --force-yes
+
+--- a/examples/debian.def
 b/examples/debian.def
+@@ -16,5 +16,5 @@ MirrorURL: http://ftp.us.debian.org/debi
+ %post
+ echo "Hello from inside the container"
+ apt-get update
+-apt-get -y install vim
++apt-get -y --force-yes install vim
+ 
+--- a/examples/ubuntu.def
 b/examples/ubuntu.def
+@@ -16,5 +16,5 @@ MirrorURL: http://us.archive.ubuntu.com/
+ %post
+ echo "Hello from inside the container"
+ sed -i 's/$/ universe/' /etc/apt/sources.list
+-apt-get -y install vim
++apt-get -y --force-yes install vim
+ 
diff -Nru 
singularity-container-2.2/debian/patches/changeset_0d04edaeb5cb3607ab25588f4db177c0878adcc0.diff
 
singularity-container-2.2/debian/patches/changeset_0d04edaeb5cb3607ab25588f4db177c0878adcc0.diff
--- 
singularity-container-2.2/debian/patches/changeset_0d04edaeb5cb3607ab25588f4db177c0878adcc0.diff
1969-12-31 19:00:00.0 -0500
+++ 
singularity-container-2.2/debian/patches/changeset_0d04edaeb5cb3607ab25588f4db177c0878adcc0.diff
2017-02-09 16:27:55.0 -0500
@@ -0,0 +1,14 @@
+From: Nekel-Seyew 
+Subject: added an ERRNO==ENOENT clause
+
+--- a/src/lib/file/group/group.c
 b/src/lib/file/group/group.c
+@@ -139,7 +139,7 @@ int singularity_file_group(void) {
+ singularity_message(VERBOSE3, "Found supplementary group 
membership in: %d\n", gids[i]);
+ singularity_message(VERBOSE2, "Adding user's supplementary 
group ('%s') info to template group file\n", grent->gr_name);
+ fprintf(file_fp, "%s:x:%u:%s\n", gr->gr_name

Bug#855217: unblock: openmpi/2.0.2

2017-02-15 Thread Alastair McKinstry
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package openmpi to fix RC bug #848574

Openmpi 2.0.2 was released just as Stretch was being frozen. The package in 
testing,
2.0.2~git.20161225 was packaged to get relevant (2.0.2) changes into Stretch, 
but unfortuanatelt contained
a significant bug on mips64el release architecture that was not caught before 
transition.

debdiff too large to be useful.

unblock openmpi/2.0.2-2


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

Kernel: Linux 4.9.0-1-686-pae (SMP w/1 CPU core)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_IE.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)



Bug#568375: [pkg-gnupg-maint] Bug#568375: Bug#568375: gnupg-agent: does not work with `git tag -s`

2017-02-15 Thread Daniel Kahn Gillmor
On Wed 2017-02-15 05:24:34 -0500, Werner Koch wrote:
> On Tue, 14 Feb 2017 00:55, d...@fifthhorseman.net said:
>
>>  * gpg 1.4 expects to connect directly to the active smartcard.  2.1
>>expects access to the smartcard to be mediated by the scdaemon
>>process.  I don't know what happens if both of these systems try to
>>access a single smartcard concurrently, but i imagine it's not
>
> If gpg 1.4 can access the card via agent+scdaemon it uses these daemons
> to access the card.  Thus many things should work.
>
> If 1.4 can't do that it uses an old copy of the code used by scdaemon to
> access the card.  That code is old and thus a lot of things won't work.
>
> I can't suggest to use 1.4 with smardcards.

should we adjust the build of 1.4 in debian to patch out the direct
access of smartcards?  if we use --disable-card-support during
./configure will that disable use of the agent for smartcards as well,
or will it just remove the direct access?

   --dkg


signature.asc
Description: PGP signature


Bug#855141: Importing pdf fail with newer gscan2pdf

2017-02-15 Thread Jeffrey Ratcliffe
On 14 February 2017 at 16:56, Bastien ROUCARIES
 wrote:
> Recent version of gscan2pdf fail to correctly import NIST bulletin
>
> http://nvlpubs.nist.gov/nistpubs/bulletin/03/nbsbulletinv3n2p295_A2b.pdf

The PDF has, per page, three images and a hidden text layer.

gscan2pdf does not (yet) support the concept of background/foreground
images and thus each image is imported as a separate page. This is
also what the warning at the end of the process says.

This is a feature, not a bug, as the aim of gscan2pdf is not to
provide a fully-fledged PDF viewer.

Unless you are referring to some other part of import process, I am
tempted to tag this as wishlist.

I hope at some point in the future to add features splitting
foreground and background. At this point, gscan2pdf could be expect to
import PDFs like this better.



Bug#855218: kubernetes-master: Unable to install due to failing kubernetes-master.service

2017-02-15 Thread John Paul Adrian Glaubitz
Package: kubernetes-master
Version: 1.2.5+dfsg-1
Severity: serious
Justification: renders package unusable

Hi!

Trying to install the kubernetes-master package on Debian unstable fails with:

root@test-janluca2:~# apt install kubernetes-master
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  linux-image-4.3.0-1-amd64 linux-image-4.5.0-2-amd64 linux-image-4.6.0-1-amd64
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
  kubernetes-client
The following NEW packages will be installed:
  kubernetes-client kubernetes-master
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 31.2 MB of archives.
After this operation, 198 MB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://ftp.de.debian.org/debian experimental/main amd64 kubernetes-client 
amd64 1.2.5+dfsg-1 [4,647 kB]
Get:2 http://ftp.de.debian.org/debian experimental/main amd64 kubernetes-master 
amd64 1.2.5+dfsg-1 [26.6 MB]
Fetched 31.2 MB in 1s (30.3 MB/s)
Selecting previously unselected package kubernetes-client.
(Reading database ... 205878 files and directories currently installed.)
Preparing to unpack .../kubernetes-client_1.2.5+dfsg-1_amd64.deb ...
Unpacking kubernetes-client (1.2.5+dfsg-1) ...
Selecting previously unselected package kubernetes-master.
Preparing to unpack .../kubernetes-master_1.2.5+dfsg-1_amd64.deb ...
Unpacking kubernetes-master (1.2.5+dfsg-1) ...
Setting up kubernetes-master (1.2.5+dfsg-1) ...
Job for kube-apiserver.service failed because the control process exited with 
error code.
See "systemctl status kube-apiserver.service" and "journalctl -xe" for details.
invoke-rc.d: initscript kube-apiserver, action "start" failed.
● kube-apiserver.service - Kubernetes API Server
   Loaded: loaded (/lib/systemd/system/kube-apiserver.service; disabled; vendor 
preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Wed 2017-02-15 
16:26:38 CET; 9ms ago
 Docs: https://github.com/kubernetes/kubernetes
   man:kube-apiserver
  Process: 29675 ExecStart=/usr/bin/kube-apiserver $KUBE_LOGTOSTDERR 
$KUBE_LOG_LEVEL $KUBE_ALLOW_PRIV $KUBE_API_ADDRESS $KUBE_API_PORT $KUBELET_PORT 
$KUBE_ETCD_SERVERS $KUBE_SERVICE_ADDRESSES $KUBE_ADMISSION_CONTROL $DAEMON_ARGS 
(code=exited, status=255)
 Main PID: 29675 (code=exited, status=255)
  CPU: 174ms

Feb 15 16:26:38 test-janluca2 systemd[1]: kube-apiserver.service: Unit entered 
failed state.
Feb 15 16:26:38 test-janluca2 systemd[1]: kube-apiserver.service: Failed with 
result 'exit-code'.
dpkg: error processing package kubernetes-master (--configure):
 subprocess installed post-installation script returned error exit status 1
Setting up kubernetes-client (1.2.5+dfsg-1) ...
Processing triggers for systemd (232-15) ...
Processing triggers for man-db (2.7.6.1-2) ...
Errors were encountered while processing:
 kubernetes-master
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@test-janluca2:~#

Thanks,
Adrian

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


Bug#801247: [gpg-agent] Env variables not available in some unknown cases

2017-02-15 Thread aeris
Package: gpg-agent

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

Hi,

Seems not related to pinentry-gnome3 directly.
I use a custom pinentry python script (not using any gpg provided pinentry) to 
use kwallet, and I think I hit the same trouble.

Triggering pinentry invocation from shell (gpg) or desktop app (kmail), all is 
good. Triggering pinentry through gpg-agent ssh export, fails.

The difference in my case is env variable.

On the working case :
LANG LISTEN_FDNAMES MANAGERPID SHELL XDG_RUNTIME_DIR JOURNAL_STREAM 
LISTEN_FDS LISTEN_PID XAUTHORITY LOGNAME USER PATH XMODIFIERS HOME 
GTK_IM_MODULE _assuan_pipe_connect_pid DBUS_SESSION_BUS_ADDRESS INVOCATION_ID
On the not working case :
LANG LISTEN_FDNAMES MANAGERPID SHELL XDG_RUNTIME_DIR JOURNAL_STREAM 
LISTEN_FDS LISTEN_PID LOGNAME USER PATH HOME _assuan_pipe_connect_pid 
INVOCATION_ID

Missing between the two :
XAUTHORITY XMODIFIERS GTK_IM_MODULE DBUS_SESSION_BUS_ADDRESS

Seems all X session related env variable are not propagated.

Pinentry is from the same gpg-agent, I don’t kill it between invocation.
There is trouble whatever the first call you do (shell/desktop or ssh), shell/
desktop always work even on a agent started with ssh and ssh always fail even 
on a shell/desktop started agent.

In my case, forcing manually the DBUS_SESSION_BUS_ADDRESS on my script resolve 
the trouble but ugly workaround (need to edit the script for each new 
session…). Without this variable, KWallet.Wallet.OpenWallet fails, perhaps the 
same thing happens with gnome wallet.

So, it’s seems something on gpg-agent which filter env variable based on an 
unknown criteria, probably related to X session.

As far I as know, I don’t faced this trouble some weeks ago with same 
configuration, so perhaps a regression somewhere. It works on my setup on 
2016-12-29.
I try to downgrade to gnupg 2.1.16-3 (used until 2017-01-04), but no more 
luck. This fact lets me to thing it’s perhaps not at all related to gnupg.

The process which run gpg-agent is systemd in my case.
/lib/systemd/systemd --user
\_ /usr/bin/dirmngr --supervised
\_ /usr/bin/gpg-agent --supervised

--- System information. ---
Architecture: 
Kernel:   Linux 4.9.0-1-amd64

Debian Release: 9.0
  515 testing vwakviie2ienjx6t.onion 
  510 stable-updates  vwakviie2ienjx6t.onion 
  505 stable  vwakviie2ienjx6t.onion 
  505 stable  sgvtcaew4bxjd7ln.onion 
  500 unstablevwakviie2ienjx6t.onion 
  100 jessie-backports vwakviie2ienjx6t.onion 
1 experimentalvwakviie2ienjx6t.onion 

--- Package information. ---
ii  gnupg 2.1.16-3  
   
amd64GNU privacy guard - a free PGP replacement
ii  gnupg-agent   2.1.16-3  
   
amd64GNU privacy guard - cryptographic agent
ii  gnupg22.1.16-3  
   
all  GNU privacy guard - a free PGP replacement (dummy transitional 
package)

ii  gnupg 2.1.18-3  
   
amd64GNU privacy guard - a free PGP replacement
ii  gnupg-agent   2.1.18-3  
   
amd64GNU privacy guard - cryptographic agent
ii  gnupg22.1.18-3  
   
all  GNU privacy guard - a free PGP replacement (dummy transitional 
package)

-- 
Aeris
Individual crypto-terrorist group self-radicalized on the digital Internet
https://imirhil.fr/

Protect your privacy, encrypt your communications
GPG : EFB74277 ECE4E222
OTR : 5769616D 2D3DAC72
https://café-vie-privée.fr/

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


Bug#853751: unbound: FTBFS[!linux]: missing getentropy implementations

2017-02-15 Thread Steven Chamberlain
Control: tags -1 + patch

Hi again,

Attached is an updated patch, that I hope is more suitable for upstream.
It adds a configure option `--with-libbsd' allowing to use it if
desired (instead of using the overlay);  and it updates libunbound.pc if
necessary, to tell users of -lunbound to also use -lbsd.

Also attached is a patch for the unbound Debian packaging, which would
use that option on non-Linux architectures.  libunbound would then build
with portable implementations of getentropy, arc4random etc. from
libbsd, fixing the current FTBFS.  This shouldn't break any
reverse-depends because those already FTBFS on kfreebsd and hurd, and
those architectures are not in testing.

In future, if libbsd was enabled on linux architectures too, then there
perhaps should be a soname bump / transition where reverse-depends (e.g.
gnutls28) switch to using pkg-config, so that they themselves link with
-lbsd if necessary, and not simply -lunbound as most do currently.
Helmut Grohne suggested uploading to experimental in that case, and then
I could file patches for all the reverse-depends.

Thanks for considering,
Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


signature.asc
Description: Digital signature


Bug#855204: libpetsc3.7.5-dev: uninstallable - Depends: libopenmpi-dev (< 2.0.2~git.20161226)

2017-02-15 Thread Drew Parsons
On Wed, 15 Feb 2017 13:45:41 + James Cowgill 
wrote:
> > 
> > Please look for already reported bugs before reporting new ones
(there
> > is an "affect" so it is in libpetsc3.7.5-dev bugs list).
> 
> Well I did check petsc (not release.debian.org), but affects on
binary
> packages don't actually show up on the main bugs page - #636689
> 


James is right, the Affecting Bug shows up neither on the src:petsc
overview on bugs.debian.org, nor in reportbug (for libpetsc3.7.5-dev).

I'll file a bug (or 2 bugs).

Drew



Bug#855219: ghostscript: Please add gspcl

2017-02-15 Thread Patrik Schindler
Package: ghostscript
Version: 9.06~dfsg-2+deb8u4
Severity: wishlist

The GhostScript project also offers gspcl, which does the same with PCL-Data as
GhostScript does with PostScript. There's no package for Debian and
implementing this seems to be not so trivial, because gspcl generates the same
scripts as ghostscript itself (ps2pdf and the like).

Please add gspcl to Debian. :-) Thanks!

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

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

Versions of packages ghostscript depends on:
ii  debconf [debconf-2.0]  1.5.56
ii  gsfonts1:8.11+urwcyr1.0.7~pre44-4.2
ii  libc6  2.19-18+deb8u7
ii  libgs9 9.06~dfsg-2+deb8u4

ghostscript recommends no packages.

Versions of packages ghostscript suggests:
ii  ghostscript-x  9.06~dfsg-2+deb8u4

-- no debconf information



Bug#855204: libpetsc3.7.5-dev: uninstallable - Depends: libopenmpi-dev (< 2.0.2~git.20161226)

2017-02-15 Thread Drew Parsons
On Wed, 15 Feb 2017 23:40:57 +0800 Drew Parsons 
wrote:
> 
> the Affecting Bug shows up neither on the src:petsc
> overview on bugs.debian.org, nor in reportbug (for libpetsc3.7.5-
> dev).

> I'll file a bug (or 2 bugs).
> 


In fact already reported.

#544812 against reportbug
#636689 against bugs.debian.org



Bug#855209: systemd ignores configuration for getty when switching and autostarting a new vt

2017-02-15 Thread Felipe Sateler
On Wed, Feb 15, 2017 at 11:28 AM, Salvo Tomaselli  wrote:
> Package: systemd
> Version: 232-18
> Severity: normal
>
> Dear Maintainer,
> I want to have logs on tty6, rather than a login shell.
>
> I created a file called /etc/systemd/system/getty@tty6.service
>
> What happens is that if I press ctrl+alt+f6, I get a login shell.
>
> However, if after that I give
>
> # service getty@tty6 stop
> # service getty@tty6 start
>
> and then switch again to tty6 with ctrl+alt+f6, then I will see
> the wanted tail of logs.

I think the problem is that logind actually tries to start
autovt@tty6. Thus the chain is:

autovt@tty6
=> resolved as instance of autovt@
=> resolved as alias of getty@

The whole alias thing is very weird , as aliasing depends on load
orer. There is discussion upstream of better handling but not fixed
yet.

In the meantime, you should be able to fix the issue via `ln -s
getty@tty6.service /etc/systemd/system/autovt@tty6.service`

-- 

Saludos,
Felipe Sateler



Bug#853751: unbound: FTBFS[!linux]: missing getentropy implementations

2017-02-15 Thread Steven Chamberlain
Steven Chamberlain wrote:
> Attached is [...]

Oops.

-- 
Steven Chamberlain
ste...@pyro.eu.org
Date: Wed, 15 Feb 2017 12:44:13 +
From: Steven Chamberlain 
Subject: enable use of portable libbsd functions

Add a new configure option `--with-libbsd', which allows to use libbsd's
portable implementations of:
strlcpy strlcat arc4random arc4random_uniform reallocarray
instead of the embedded code copies in contrib/, which will be
difficult to maintain in the long term.

Also patch util/random.c so that, when building with libbsd and without
OpenSSL, arc4random can still be used as the PRNG.  Otherwise, building
with libnettle would need a kernel-specific getentropy implementation,
and libbsd does not export one.

diff --git a/configure.ac b/configure.ac
index d850539..9744388 100644
--- a/configure.ac
+++ b/configure.ac
@@ -707,6 +707,19 @@ AC_INCLUDES_DEFAULT
 fi
 AC_SUBST(SSLLIB)
 
+# libbsd
+AC_ARG_WITH([libbsd], AC_HELP_STRING([--with-libbsd=path], [Use portable libbsd functions]), [
+	AC_CHECK_HEADERS([bsd/string.h bsd/stdlib.h],,, [AC_INCLUDES_DEFAULT])
+	if test "x$ac_cv_header_bsd_string_h" = xyes -a "x$ac_cv_header_bsd_stdlib_h" = xyes; then
+		for func in strlcpy strlcat arc4random arc4random_uniform reallocarray; do
+			AC_SEARCH_LIBS([$func], [bsd], [
+AC_DEFINE(HAVE_LIBBSD, 1, [Use portable libbsd functions])
+PC_LIBBSD_DEPENDENCY=libbsd
+AC_SUBST(PC_LIBBSD_DEPENDENCY)
+			])
+		done
+	fi
+])
 
 AC_ARG_ENABLE(sha2, AC_HELP_STRING([--disable-sha2], [Disable SHA256 and SHA512 RRSIG support]))
 case "$enable_sha2" in
@@ -1469,6 +1482,11 @@ struct tm;
 char *strptime(const char *s, const char *format, struct tm *tm);
 #endif
 
+#ifdef HAVE_LIBBSD
+#include 
+#include 
+#endif
+
 #ifdef HAVE_LIBRESSL
 #  if !HAVE_DECL_STRLCPY
 size_t strlcpy(char *dst, const char *src, size_t siz);
diff --git a/contrib/libunbound.pc.in b/contrib/libunbound.pc.in
index 130bef5..b6aec29 100644
--- a/contrib/libunbound.pc.in
+++ b/contrib/libunbound.pc.in
@@ -7,7 +7,7 @@ Name: unbound
 Description: Library with validating, recursive, and caching DNS resolver
 URL: http://www.unbound.net
 Version: @PACKAGE_VERSION@
-Requires: libcrypto libssl @PC_LIBEVENT_DEPENDENCY@ @PC_PY_DEPENDENCY@
+Requires: libcrypto libssl @PC_LIBEVENT_DEPENDENCY@ @PC_PY_DEPENDENCY@ @PC_LIBBSD_DEPENDENCY@
 Libs: -L${libdir} -lunbound
 Libs.private: @SSLLIB@ @LIBS@
 Cflags: -I${includedir} 
diff --git a/util/random.c b/util/random.c
index 8332960..b86c548 100644
--- a/util/random.c
+++ b/util/random.c
@@ -78,7 +78,7 @@
  */
 #define MAX_VALUE 0x7fff
 
-#if defined(HAVE_SSL)
+#if defined(HAVE_SSL) || defined(HAVE_LIBBSD)
 void
 ub_systemseed(unsigned int ATTR_UNUSED(seed))
 {
@@ -208,10 +208,10 @@ long int ub_random(struct ub_randstate* s)
 	}
 	return x & MAX_VALUE;
 }
-#endif /* HAVE_SSL or HAVE_NSS or HAVE_NETTLE */
+#endif /* HAVE_SSL or HAVE_LIBBSD or HAVE_NSS or HAVE_NETTLE */
 
 
-#if defined(HAVE_NSS) || defined(HAVE_NETTLE)
+#if defined(HAVE_NSS) || defined(HAVE_NETTLE) && !defined(HAVE_LIBBSD)
 long int
 ub_random_max(struct ub_randstate* state, long int x)
 {
@@ -223,7 +223,7 @@ ub_random_max(struct ub_randstate* state, long int x)
 		v = ub_random(state);
 	return (v % x);
 }
-#endif /* HAVE_NSS or HAVE_NETTLE */
+#endif /* HAVE_NSS or HAVE_NETTLE and !HAVE_LIBBSD */
 
 void 
 ub_randfree(struct ub_randstate* s)
diff --git a/debian/control b/debian/control
index f27c922..001428c 100644
--- a/debian/control
+++ b/debian/control
@@ -15,6 +15,7 @@ Build-Depends:
  dh-systemd ,
  dpkg-dev (>= 1.16.1~),
  flex,
+ libbsd-dev (>= 0.8.1~) [!linux-any],
  libevent-dev,
  libexpat1-dev,
  libfstrm-dev ,
diff --git a/debian/rules b/debian/rules
index f978494..3e5c216 100755
--- a/debian/rules
+++ b/debian/rules
@@ -7,6 +7,10 @@ ifneq ($(DEB_HOST_ARCH), amd64)
 CONFIGURE_ARGS = --disable-flto
 endif
 
+ifneq ($(DEB_HOST_ARCH_OS), linux)
+CONFIGURE_ARGS = --with-libbsd
+endif
+
 LIBRARY = libunbound2
 DOPACKAGES = $(shell dh_listpackages)
 


signature.asc
Description: Digital signature


Bug#855220: [PATCH] a new cgi script

2017-02-15 Thread Mattia Rizzolo
Package: qa.debian.org
Severity: wishlist
User: qa.debian@packages.debian.org
Usertags: udd
Control: submitter -1 Erwan Prioul 
X-Debbugs-Cc: Erwan Prioul 


Re-submitting the request to the BTS, so it won't get lost until
somebody will came around at reading the proposed script and push it.
(also re-attached the attachment).  Original text follows:

On Wed, Feb 15, 2017 at 04:07:56PM +0100, Erwan Prioul wrote:
> I'd like to add a new cgi script into udd.
> The goal of this script is to display FTBFS packages on a given
> architecture.
> For every package, it gives the name of the package, its version, the
> time since the latest build and links to the bts, the tracker and the
> logs of the latest build. It also shows the related bugs (bug id +
> bug title) if any.
> 
> Let me know if I'm doing wrong.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#855220: [PATCH] a new cgi script

2017-02-15 Thread Mattia Rizzolo
On Wed, Feb 15, 2017 at 04:53:14PM +0100, Mattia Rizzolo wrote:
> (also re-attached the attachment).

... here.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
From 9cf994e38331f895fae15772225925e25d304391 Mon Sep 17 00:00:00 2001
From: Erwan Prioul 
Date: Wed, 15 Feb 2017 15:43:32 +0100
Subject: [PATCH] add first version of ftbfs.cgi

script that displays the FTBFS packages on a given architecture, with related bugs if any.
---
 web/cgi-bin/ftbfs.cgi | 247 ++
 1 file changed, 247 insertions(+)
 create mode 100755 web/cgi-bin/ftbfs.cgi

diff --git a/web/cgi-bin/ftbfs.cgi b/web/cgi-bin/ftbfs.cgi
new file mode 100755
index 000..b340e59
--- /dev/null
+++ b/web/cgi-bin/ftbfs.cgi
@@ -0,0 +1,247 @@
+#!/usr/bin/env python
+# Display FTBFS packages on given arch
+# Copyright (C) 2017, Erwan Prioul 
+#
+# This program is free software: you can redistribute it and/or modify it under
+# the terms of the GNU General Public License as published by the Free Software
+# Foundation, either version 3 of the License, or (at your option) any later
+# version.
+# This program is distributed in the hope that it will be useful, but WITHOUT
+# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
+# FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more
+# details.
+# You should have received a copy of the GNU General Public License along with
+# this program.  If not, see .
+
+import datetime
+import psycopg2
+import cgi
+import cgitb
+
+DATABASE = {
+'database': 'udd',
+'port': 5452,
+'host': 'localhost',
+'user': 'guest'
+}
+
+class AttrDict(dict):
+def __init__(self, **kwargs):
+for key, value in kwargs.iteritems():
+self[key] = value
+
+def __getattr__(self, name):
+try:
+return self[name]
+except KeyError, e:
+raise AttributeError(e)
+
+def query(query, cols, *parameters):
+try:
+conn = psycopg2.connect(**DATABASE)
+cursor = conn.cursor()
+cursor.execute(query, parameters)
+except:
+exit(1)
+for row in cursor.fetchall():
+yield AttrDict(**dict(zip(cols, row)))
+cursor.close()
+conn.close()
+
+def pretty_time_delta(when):
+seconds = (datetime.datetime.now() - when).total_seconds()
+days, seconds = divmod(seconds, 86400)
+hours, seconds = divmod(seconds, 3600)
+minutes, seconds = divmod(seconds, 60)
+if days > 0:
+return '%dd' % (days)
+elif hours > 0:
+return '%dh' % (hours)
+elif minutes > 0:
+return '%dm' % (minutes)
+else:
+return '%ds' % (seconds)
+
+def packageLine(packages, package, pending = False):
+u = package.replace('+', '%2B')
+bugs = " "
+what = 'nopatch'
+if pending:
+what = 'patch'
+if len(packages[package][what]) > 0:
+bugs = ''.join('http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=%d";>#%d - %s' % (x[0], x[0], x[1]) for x in sorted(packages[package][what]))
+return \
+'%s_%s' % (package, packages[package]['version']) + \
+'' + \
+'https://buildd.debian.org/status/package.php?p=%s&suite=sid"; title="Debian buildd status">%s ' % (u, pretty_time_delta(packages[package]['state_change'])) + \
+'[http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=%s"; title="Debian bugs in source package">B]' % (u) + \
+'[http://buildd.debian.org/status/logs.php?pkg=%s"; title="Debian build logs">L]' % (u) + \
+'[https://tracker.debian.org/pkg/%s"; title="Debian Package Tracker">T]' % (u) + \
+'%s' % bugs
+
+def generatePending(packages, nb, arch):
+return \
+'%d FTBFS packages on %s with a patch pending' % (nb, arch) + \
+''.join(packageLine(packages, x, True) for x in sorted(packages.keys()) if len(packages[x]['patch']) > 0) + \
+''
+
+def generateFailing(packages, failing, nb, arch):
+html = '%d FTBFS packages on %s without patch' % (nb, arch)
+for c in sorted(failing.keys()):
+if c > 2:
+	txt = "and %d other architectures" % (c - 1)
+elif c == 2:
+txt = "and 1 other architecture"
+else:
+txt = ""
+html += \
+'%d packages are failing on %s %s' % (len(failing[c]), arch, txt) + \
+''.join(packageLine(packages, x) for x in sorted(failing[c])) + \
+''
+return html
+
+def getPackages(arch):
+# Get all FTBFS packages on given architecture
+q = """
+select distinct source, version, state_change
+from wannabuild
+where architecture = '%s' and
+  distribution = 'sid' and
+  state in ('F

Bug#855221: pulseaudio: ThinkPad T420s docking station: no sound from external speakers

2017-02-15 Thread otas.pe
Package: pulseaudio
Version: 10.0-1
Severity: important
Tags: d-i

Hello

When I plug external speakers into the docking station Lenovo Mini Dock Series
3 type 4337 and Lenovo Thinkpad T420s is attached then there is no sound
although internal speakers shut down. No HW issue, it work under W10.

Thans

Otas



-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


-- 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=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pulseaudio depends on:
ii  adduser  3.115
ii  libasound2   1.1.3-4
ii  libasound2-plugins   1:1.1.1-dmo1
ii  libc62.24-9
ii  libcap2  1:2.25-1
ii  libdbus-1-3  1.10.14-1
ii  libgcc1  1:6.3.0-6
ii  libice6  2:1.0.9-1+b1
ii  libltdl7 2.4.6-2
ii  liborc-0.4-0 1:0.4.26-2
ii  libpulse010.0-1
ii  libsm6   2:1.2.2-1+b1
ii  libsndfile1  1.0.27-1
ii  libsoxr0 0.1.2-2
ii  libspeexdsp1 1.2~rc1.2-1
ii  libstdc++6   6.3.0-6
ii  libsystemd0  232-15
ii  libtdb1  1.3.11-2
ii  libudev1 232-15
ii  libwebrtc-audio-processing1  0.3-1
ii  libx11-6 2:1.6.4-3
ii  libx11-xcb1  2:1.6.4-3
ii  libxcb1  1.12-1
ii  libxtst6 2:1.2.3-1
ii  lsb-base 9.20161125
ii  pulseaudio-utils 10.0-1

Versions of packages pulseaudio recommends:
ii  rtkit  0.11-4

Versions of packages pulseaudio suggests:
pn  paman
pn  paprefs  
ii  pavucontrol  3.0-3+b2
pn  pavumeter
ii  udev 232-15

-- no debconf information
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; default-sink =
; default-source =
; default-server =
; default-dbus-server =

; autospawn = yes
; daemon-binary = /usr/bin/pulseaudio
; extra-arguments = --log-target=syslog

; cookie-file =

; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB

; auto-connect-localhost = no
; auto-connect-display = no
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; daemonize = no
; fail = yes
; allow-module-loading = yes
; allow-exit = yes
; use-pid-file = yes
; system-instance = no
; local-server-type = user
; enable-shm = yes
; enable-memfd = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB
; lock-memory = no
; cpu-limit = no

; high-priority = yes
; nice-level = -11

; realtime-scheduling = yes
; realtime-priority = 5

; exit-idle-time = 20
; scache-idle-time = 20

; dl-search-path = (depends on architecture)

; load-default-script-file = yes
; default-script-file = /etc/pulse/default.pa

; log-target = auto
; log-level = notice
; log-meta = no
; log-time = no
; log-backtrace = 0

; resample-method = speex-float-1
; enable-remixing = yes
; enable-lfe-remixing = no
; lfe-crossover-freq = 0

; flat-volumes = yes

; rlimit-fsize = -1
; rlimit-data = -1
; rlimit-stack = -1
; rlimit-c

Bug#851784: [Pkg-nginx-maintainers] Bug#851784: libnginx-mod-http-dav-ext: unknown directive "dav_ext_methods"

2017-02-15 Thread Ñãzãr
Hello Christos,

I've tried 1.10.2-4, in fact I've also tried the recent 1.10.3-1 both has
the same error:

nginx: [emerg] unknown directive "dav_ext_methods" in
> /etc/nginx/sites-enabled/default.conf:91
> nginx: configuration file /etc/nginx/nginx.conf test failed


Again if I recompile without the dav-ext dynamic module patch, it works.


Best Regards,
Ñážàŕ

On Tue, Feb 14, 2017 at 6:27 PM, Christos Trochalakis <
ctrochala...@debian.org> wrote:

> On Sat, Jan 21, 2017 at 09:16:07PM +0800, Ńăzăr wrote:
>
>> Hello Christos,
>>
>> Thanks for replying. I'm actually trying to install on a mixed
>> wheezy/jessie armhf system, a WDMyCloud NAS. Today I re-compiled both
>> 1.10.2-2 and 1.11.8-1~exp1 from the deb-src on my dev system but this time
>> I removed the "dav-ext dynamic module" patch:
>>
>> cd nginx_1.*/debian/;
>> rm -rf ./patches/modules/nginx-dav-ext-module/
>> ./libnginx-mod-http-dav-ext.
>> nginx;
>> cd .. && dpkg-buildpackage -b;
>>
>> Using these re-compiled nginx-full package with the "dav-ext dynamic
>> module" patch removed (both 1.10.2-2 and 1.11.8-1~exp1), I can use the
>> dav_ext_methods directive without errors.
>>
>> I'm wondering if you could help to point out what causes this "unknown
>> directive" issue on my system when the dav-ext is separated as a loaded
>> module (load_module modules/ngx_http_dav_ext_module.so;) because I have
>> all
>> the dependencies met.
>>
>> Thank you.
>>
>
> Could you please retry against 1.10.2-4? There are some changes there
> that might affect you.
>
>


Bug#855216: unblock: singularity-container/2.2-2

2017-02-15 Thread Sébastien Delafond
Dear Release Managers,

the Security Team has reviewed the diff related to this security
problem, and we support the unblock request.

Cheers,

--Seb



Bug#855188: [tehnic #MMT-770-90243]: Re: Bug#855188: mirror submission for mirrors.xservers.ro

2017-02-15 Thread Departamentul Tehnic xServers
Hello,

Yes, please use n...@xservers.ro because the email teh...@xservers.ro have a 
lot of traffic.
I change the mirror update at 4 times / day but most of the mirrors drop the 
connection when i try to update :(
The ftpsync have been updated at you suggestion.
Thanks for help and suggestions.

Have a nice day.


-- 
Cristian Opriț
Departamentul Tehnic xServers

Tehnic: +40-755-038-875 teh...@xservers.ro
Comercial: +40-749-266-266 comerc...@xservers.ro
Fax: +40-212-120-844

Ticket History
===


Peter Palfrader (Client) Posted On: 15 Feb 2017 11:31

===
Control: tags -1 moreinfo

Hi!

Thanks for your (re-)submission.  I have one question, two issues, and
one suggestion:

On Wed, 15 Feb 2017, Tehnic Department wrote:

> Maintainer: Tehnic Department 
> Maintainer: Tehnic Department 

Question:

o We should use the noc@ address in our file?

> Archive-http: /debian/

Issues:

o The tracefile
  http://mirrors.xservers.ro/debian/project/trace/mirrors.xservers.ro
  suggests that the ftpsync version you are using is very old.  Please upgrade.
  http://mirrors.xservers.ro/debian/project/ftpsync/ftpsync-current.tar.gz

> Updates: twice

Please run the update 4 times a day (every 6 hours) to match the update
frequency of the archive.  Consult the upstream trace file on what a
good time offset might be:
  http://mirrors.xservers.ro/debian/project/trace/ftp.upcnet.ro

Suggestion:

> Archive-upstream: ftp.ro.debian.org
> CDImage-upstream: ftp.ro.debian.org

o we recommend mirrors not sync directly from service aliases such as
  ftp..debian.org (only http for /debian/ is guaranteed to be
  available at ftp..d.o sites).  Maybe change your config to sync
  from  (which is the same host)?

  Currently, ftp.ro.debian.org is an alias for ftp.upcnet.ro - maybe you
  want to mirror from that ftp.upcnet.ro.

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








Ticket Details
-
Ticket ID: MMT-770-90243
Department: Dept Tehnic
Type: Sesizare tehnica
Status: Closed
Priority: Normal

Support Center: https://client.xservers.ro/index.php?


Bug#855193: RFS: slt/0.0.git20140301-2.1 [RC][NMU] -- TLS reverse-proxy with SNI multiplexing (TLS virtual hosts)

2017-02-15 Thread James Cowgill
retitle 851876 slt: FTBFS on uniprocessor systems - testsuite deadlocks
forwarded 851876 https://github.com/inconshreveable/slt/issues/5
thanks

Hi,

On 15/02/17 11:24, Roger Shimizu wrote:
> Dear James,
> 
> On Wed, Feb 15, 2017 at 7:51 PM, James Cowgill  wrote:
>>
>> So do you know why the tests only pass when using 2 CPUs? That seems
>> pretty fishy to me. Maybe there is an underlying bug here?
> 
> I'm not sure the reason.
> I was just trying to help on the FTBFS RC bug during BSP Tokyo.

I found the actual cause - there's a race condition in the testsuite
which will usually (100% in practice) cause it to deadlock on single
processor systems. You can look at the bug I filed upstream if you want.

> What I know is this is not rare, like another one I fixed:
> https://bugs.debian.org/854500

This is at best a big hack, since it almost certainly hides a real bug,
but I guess in this situation it does kind of work since the bug is in
the testsuite.

> Could you kindly help to upload?
> Buildd [0] shows it actually build fine for all ARCHs I should build,
> so I don't what to trigger the autoremove ...

James



signature.asc
Description: OpenPGP digital signature


Bug#853251: Confirmation that unstable package fix the problem

2017-02-15 Thread SWAELENS Jonathan
Hello,
I had the same problem on the last version of gitlab in Debian Stretch.
I download manually the deb of unstable and it solved my problem.

My actual gitlab version is 8.13.11+dfsg-2




signature.asc
Description: OpenPGP digital signature


Bug#855222: clang-4.0 has wrong C++ include search path order

2017-02-15 Thread Jason Rhinelander
Package: clang-4.0
Version: 1:4.0~+rc2-1
Severity: normal

Dear Maintainer,

clang-4.0 appears to have a search path order for includes that causes problems
with compilation with libc++ when trying to load stl headers; here's an example
that fails:

$ cat test.cpp
#include 
int main() { return 0; }
$ clang++-3.9 -stdlib=libc++ test.cpp
$ clang++-4.0 -stdlib=libc++ test.cpp
In file included from test.cpp:1:
In file included from /usr/include/c++/v1/limits:110:
In file included from /usr/include/c++/v1/type_traits:387:
/usr/include/c++/v1/cstddef:43:15: fatal error: 'stddef.h' file not found
#include_next 
  ^~
1 error generated.


The problem seems to be that, in clang-4.0, clang's include path is injected
before the standard library search path:

$ clang-4.0 -x c++ -stdlib=libc++ -v -E -
...
#include <...> search starts here:
 /usr/include/clang/4.0.0/include
 /usr/include/c++/v1
 /usr/local/include
 /usr/include/x86_64-linux-gnu
 /usr/include

This isn't specific to libc++: without the -stdlib=libc++ the second line is
replaced with three stdlibc++ include paths, but still show up after the clang
include path.  This doesn't seem to cause problems for stdlibc++, but still
seems incorrect.

In clang-3.9, clang's include path comes after the c++ library:

$ clang-3.9 -x c++ -stdlib=libc++ -v -E -
...
#include <...> search starts here:
 /usr/include/c++/v1
 /usr/local/include
 /usr/lib/llvm-3.9/bin/../lib/clang/3.9.1/include
 /usr/include/x86_64-linux-gnu
 /usr/include


This breaks libc++ under clang-4.0 because it uses `#include_next `
to get at the compiler's stddef.h, which won't work with the paths in the wrong
order.


Other things I tried:

- I built and installed upstream libc++ 4.0 instead of the debian-packaged
libc++ 3.9.1: same error (unsurprisingly).
- I tried the clang-4.0 snapshot from http://apt.llvm.org/, which exhibits
exactly the same behaviour.
- I built clang and libc++ from the upstream llvm 4.0 branch: it works fine.
The search path for this clang is:
 /usr/local/bin/../include/c++/v1
 /usr/local/include
 /usr/local/bin/../lib/clang/4.0.0/include
 /usr/include/x86_64-linux-gnu
 /usr/include

i.e. the clang include is after the C++ library, where it belongs.



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

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

Versions of packages clang-4.0 depends on:
ii  binutils 2.27.90.20170205-1
ii  libc62.24-9
ii  libc6-dev2.24-9
ii  libclang-common-4.0-dev  1:4.0~+rc2-1
ii  libclang1-4.01:4.0~+rc2-1
ii  libgcc-6-dev 6.3.0-6
ii  libgcc1  1:6.3.0-6
ii  libjsoncpp1  1.7.4-3
ii  libllvm4.0   1:4.0~+rc2-1
ii  libobjc-6-dev6.3.0-6
ii  libstdc++-6-dev  6.3.0-6
ii  libstdc++6   6.3.0-6

Versions of packages clang-4.0 recommends:
ii  llvm-4.0-dev  1:4.0~+rc2-1
ii  python2.7.13-2

Versions of packages clang-4.0 suggests:
pn  clang-4.0-doc  
pn  gnustep
pn  gnustep-devel  

-- no debconf information



Bug#853254: ftp.debian.org: please create stretch-backports suite

2017-02-15 Thread Niels Thykier
Ansgar Burchardt:
> Niels Thykier writes:
>>> In preparation of the freeze, it would be nice if the stretch-backports
>>> could be populated, with the same architectures as stretch.  If
>>> possible, the new suite should not accept uploads until the actual
>>> stretch release.
>>
>> Are there any news on this?  Currently, the DSA are waiting for this
>> before starting their upgrade tests to stretch.
> 
> stretch-backports and jessie-backports-sloppy should appear on the
> mirrors with the next dinstall run. (-sloppy at the same time as it is
> the same work after all.)
> 
> They should reject uploads for now and the build queues on incoming.d.o
> are not setup yet either.
> 
> Ansgar
> 

Thanks a lot for the fast update :)

~Niels



  1   2   3   >