date:20161111

On Thu, Oct 20, 2016 at 07:13:38PM +0900, Nobuhiro Iwamatsu wrote:
> Source: digikam
> Version: 5.2.0-1
> Severity: important
> Justification: fails to build from source
> 
> Dear Maintainer,
> 
> I am scheduled to transition of opencv.
>https://release.debian.org/transitions/html/auto-opencv.html
> This package is target to transition. I tested build with opencv 3.1.
> As a result, FTBFS with opencv 3.1.

Digikam has configuration option ENABLE_OPENCV3, set OFF by default.
Should be a simple matter of flipping it ON.

-Steve


signature.asc
Description: PGP signature

Bug#844055: Doesn't support conversion of images with dimensions of 256x256 or greater.

2016-11-11 Thread Paul Wise

On Sat, 2016-11-12 at 14:53 +1100, Carlos Maddela wrote:

> I will make my changes available at ... on the openjpeg2 branch for
> your perusal.

Looks like you forgot to push the branch. Also, please clone from the
upstream git repo instead of importing the Debian tarballs into git.

https://sourceforge.net/p/icns/code/ci/master/tree/

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

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

Bug#844056: Missing brcmfmac43362-sdio.txt stops wireless working

2016-11-11 Thread Wookey

Package: firmware-brcm80211
Version: 20160824-1
Severity: normal

The firmware file brcm/brcmfmac43362-sdio.bin is available in the
package, but the driver brcmfmac (at least on cubietruck and maybe
always) does not work unless the file brcmfmac43362-sdio.txt is also
supplied.

See the thread here for details: 
https://groups.google.com/forum/#!topic/linux-sunxi/NngIhT-ELVc

That says that for the sdio version of this device the rom/nvram is
normally not fitted so the OS has to provide the config, from this
text file. 

It also suggests that the best thing to do is put it in the firmware
package, next to the corresponding firmware.

There may well be more that one variant of this for different boards,
but this one covers several, probably everything using the ap6210.

The file is available from
http://dl.cubieboard.org/public/Cubieboard/benn/firmware/ap6210/nvram_ap6210.txt

and looks like this.
#AP6210_NVRAM_V1.2_03192013
manfid=0x2d0
prodid=0x492
vendid=0x14e4
devid=0x4343
boardtype=0x0598

# Board Revision is P307, same nvram file can be used for P304, P305, P306 and P
307 as the tssi pa params used are same
#Please force the automatic RX PER data to the respective board directory if not
 using P307 board, for e.g. for P305 boards force the data into the following di
rectory /projects/BCM43362/a1_labdata/boardtests/results/sdg_rev0305
boardrev=0x1307
boardnum=777
xtalfreq=26000
boardflags=0x80201
boardflags2=0x80
sromrev=3
wl0id=0x431b
macaddr=00:90:4c:07:71:12
aa2g=1
ag0=2
maxp2ga0=74
cck2gpo=0x
ofdm2gpo=0x
mcs2gpo0=0x
mcs2gpo1=0x
pa0maxpwr=56

#P207 PA params
#pa0b0=5447
#pa0b1=-658
#pa0b2=-175

#Same PA params for P304,P305, P306, P307

pa0b0=5447
pa0b1=-607
pa0b2=-160
pa0itssit=62
pa1itssit=62


cckPwrOffset=5
ccode=0
rssismf2g=0xa
rssismc2g=0x3
rssisav2g=0x7
triso2g=0
noise_cal_enable_2g=0
noise_cal_po_2g=0
swctrlmap_2g=0x04040404,0x02020202,0x02020202,0x010101,0x1ff
temp_add=29767
temp_mult=425

btc_flags=0x6
btc_params0=5000
btc_params1=1000
btc_params6=63


-- System Information:
Debian Release: 8.6
  APT prefers stable
  APT policy: (990, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64, armhf

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

Bug#844055: Doesn't support conversion of images with dimensions of 256x256 or greater.

2016-11-11 Thread Carlos Maddela

Package: icnsutils
Version: 0.8.1-3
Severity: normal
Tags: patch

Dear Maintainer,

Support for images with larger dimensions was available when the package
used to link with jasper, and presumably openjpeg1 as well. However, this
feature hasn't been available ever since the package has been mistakenly
trying to compile with openjpeg2.

As it is now, the code doesn't support openjpeg2 and the package may as
well not list openjpeg2 as a build dependency.

I have had a go at getting the code to work with openjpeg2 and
it seems to do the trick. I will make my changes available at
https://github.com/e7appew/libicns.git on the openjpeg2 branch for your
perusal.

Best regards,

Carlos

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

Kernel: Linux 4.7.0-1-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/dash
Init: systemd (via /run/systemd/system)

Versions of packages icnsutils depends on:
ii  libc62.24-5
ii  libicns1 0.8.1-3
ii  libpng16-16  1.6.26-1

icnsutils recommends no packages.

icnsutils suggests no packages.

-- no debconf information

Bug#832704: RFS: nixnote2/2.0~beta10+dfsg-1 [ITP] -- Open Source Evernote client

2016-11-11 Thread Boyuan Yang

retitle 832704 RFS: nixnote2/2.0~beta10+dfsg-1 [ITP] -- Open Source
Evernote client
thanks

Hi Sean,

Since the dependency qevercloud has entered unstable, it is perfectly
fine to move towards nixnote2. I have prepared the 2.0~beta10 version
of nixnote2 package, which should address previous problems.

Detailed changes since 2.0~beta9+dfsg:

* Legacy code about old OpenOffice.org was further explained in README.source.
* Move packaging Git repository to collab-maint, now I have write
permission there. The old GitHub repository still exists and in an
up-to-date state.
* Some minor modification to package description in debian/control.
* Switched back to build with Qt4. This is not ideal but will help
squashing bugs raised when using Qt5. I will switch back to build
against Qt5 once upstream declared that the Qt5 version is in mature
state.
* Copyright information update for beta10 version.

Package on debian-mentors:

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

Packaging repository can be found at

https://anonscm.debian.org/git/collab-maint/nixnote2.git

Deb-o-matic-amd64 build status:


http://debomatic-amd64.debian.net/debomatic/unstable/pool/nixnote2_2.0~beta10+dfsg-1/nixnote2_2.0~beta10+dfsg-1.dsc

Blhc on debomatic reported some missing CXXFLAGS (-fPIE). However
since new gcc has already set -fPIE by default since 6.2.0-7, this
should be harmless.

Looking forward to further review.


Sincerely,
Boyuan Yang

Bug#774053: bug digikam

On Wed, Jul 06, 2016 at 08:38:14PM +0200, Luc Castermans wrote:
> I observe similar behaviour, also with CPU remaining at 100%. Below I used
> strace().   You can see
> I needed to kill the process to get rid of it.

Was this with Digikam version 4.4.0, as the original poster?

-Steve


signature.asc
Description: PGP signature

Bug#844054: nginx-full: ngx_http_sub_module not working

2016-11-11 Thread TC Meggs

Package: nginx-full
Version: 1.6.2-5+deb8u4
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?

   I attempted to use the sub_filter directive in a location block.

   proxy_pass http://127.0.0.1:3500/;
   proxy_set_header Accept-Encoding '';

   sub_filter 'abc' 'xyz';
   sub_filter_once off;
   sub_filter_types *;

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

   I attempted to make a request to the nginx server for the location block in 
question.

   * What was the outcome of this action?

   The response from the server was not substituted as expected. 

   * What outcome did you expect instead?

   I expected that the server would substitute the string.
   
I copied an identical configuration block to an Ubuntu server and it worked 
without issue, Ubuntu 16.04.1 LTS (Xenial Xerus) running nginx-full 
1.10.0-0ubuntu0.16.04.4.

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

Kernel: Linux 3.16.0-4-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)

Versions of packages nginx-full depends on:
ii  libc6 2.19-18+deb8u6
ii  libexpat1 2.1.0-6+deb8u3
ii  libgd32.1.0-5+deb8u7
ii  libgeoip1 1.6.2-4
ii  libpam0g  1.1.8-3.1+deb8u1+b1
ii  libpcre3  2:8.35-3.3+deb8u4
ii  libssl1.0.0   1.0.1t-1+deb8u5
ii  libxml2   2.9.1+dfsg1-5+deb8u3
ii  libxslt1.11.1.28-2+deb8u2
ii  nginx-common  1.6.2-5+deb8u4
ii  zlib1g1:1.2.8.dfsg-2+b1

nginx-full recommends no packages.

Versions of packages nginx-full suggests:
pn  nginx-doc  

-- no debconf information

Bug#843996: grub wallpaper, wrong aspect ratio (as default)

2016-11-11 Thread Paul Wise

On Sat, Nov 12, 2016 at 12:35 AM, Michael Biebl wrote:

> detect the aspect ratio in postinst and set it accordingly.

It seems to me that runtime is the right time to detect aspect ratio.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#838152: kipi-plugins: Missing dependencies on KDE packages

On Sat, Sep 17, 2016 at 09:50:12PM +0200, Eike von Seggern wrote:

> after installing digikam with kipi-plugins on a non-KDE system, I cannot
> export files via 'Export->Export to remote storage'. On stderr, I get
> messages similar to:
>   "klauncher not running"
>   "no service file for klauncher"
>   "kinit not found in $PATH"
> 
> (I can try to reproduce the exact messages if necessary).
> 
> The problem looks similar to 801308 and
> http://askubuntu.com/questions/617955/problem-with-kde-programs-after-upgrading-to-15-04
> . Following the recommendations in the latter, I've installed
>  * kinit
>  * kio
>  * kio-extras
>  * kded5

So I tried to reproduce this issue with 5.2.0-3, but failed.  One difference 
from the
initial report is that installing digikam+kipi-plugins forced the install of 
kio.  I
did not have the other three you listed installed.  But in any case, the export 
worked.

Can you possibly try removing the four above and see if the problem recurs?

Thanks,
-Steve

signature.asc
Description: PGP signature

Bug#843940: [Pkg-libvirt-maintainers] Bug#843940: libvirt-daemon: "Permission denied" errors in VMM/virt-manager when dynamic_ownership=0

2016-11-11 Thread J Mo




On 11/11/2016 10:48 AM, Guido Günther wrote:

As far as I understand your report you're disabling the feature you
want: having libvirt fixup permissions. If you disable it you have (or
virt-manager) to do that.

There might be a bug in virt-manager where it should take more care of
adjusting permissions but it's hard to figure that out from your
report. You don't give virt-manager-versions, file permissions, etc or
what you did to get it to work.


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

This behavior is so vile that it's been the cause of CVEs, just as 
people predicted it would be (see the Ubuntu bug report in my previous 
response).


This still looks like a security issue to me. I can easily change the 
permission of any root:root owned file to libvirt-qemu:libvirt-qemu on 
the filesystem, as previously documented here:


https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701649#43

Once I can do that, I can write/wipe the file, as I just did to one of 
my older kernels under /boot:


[/boot]
shara@panic-->ls /boot/vmlinuz-4.*
-rw-r--r-- 1 libvirt-qemu libvirt-qemu5 Nov 11 18:21 
/boot/vmlinuz-4.4.0-1-amd64
-rw-r--r-- 1 root root 3.7M Apr 14  2016 
/boot/vmlinuz-4.5.0-1-amd64
-rw-r--r-- 1 root root 3.7M Jul 18 12:57 
/boot/vmlinuz-4.6.0-1-amd64




In practicality, this probably isn't very serious but damn if it 
ain't stupid.

Bug#833212: libevent: Uses obsolete compressor for .deb data.tar member

2016-11-11 Thread Guillem Jover

Control: reopen -1
Control: tag -1 - unreproducible
Control: notfound -1 2.0.21-stable-2
Control: found -1 2.1.4~alpha-0.1

Hi!

On Fri, 2016-11-11 at 15:41:48 +, Jonathan Wiltshire wrote:
> Control: tag -1 unreproducible
> 
> On Tue, Aug 02, 2016 at 04:04:41AM +0200, Guillem Jover wrote:
> > This source package builds one or more binary packages using the
> > deprecated compressor bzip2. The default has been xz for a while now
> > which should usually compress better than bzip2. If instead you'd like
> > speed then switch to use gzip.
> 
> This one appears to be a false positive:

Nope, just a mixed up version number. The affected packages are in
experimental! Sorry for the confusion.

Thanks,
Guillem

Bug#843940: [Pkg-libvirt-maintainers] Bug#843940: libvirt-daemon: "Permission denied" errors in VMM/virt-manager when dynamic_ownership=0

2016-11-11 Thread J Mo

On 11/11/2016 10:48 AM, Guido Günther wrote:

As far as I understand your report you're disabling the feature you
want: having libvirt fixup permissions. If you disable it you have (or
virt-manager) to do that.

There might be a bug in virt-manager where it should take more care of
adjusting permissions but it's hard to figure that out from your
report. You don't give virt-manager-versions, file permissions, etc or
what you did to get it to work.

The feature of libvirt to dynamically take ownership of files is
confounding, bizarre, and obviously poorly thought out. I'm not alone in
this opinion. A huge number of bugs and complaints have been filed about
this issue, yet it remains:

https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/691590
https://www.redhat.com/archives/libvir-list/2011-September/msg00458.html

https://www.redhat.com/archives/libvirt-users/2010-January/msg00010.html
https://www.redhat.com/archives/libvirt-users/2010-January/msg00023.html

https://unix.stackexchange.com/questions/110357/prevent-libvirtd-from-modifying-file-attributes

All of these complaints were the reason the "dynamic_ownership"
configuration option was apparently created in the first place.

The real source of our problems here is that libvirt changes the
ownership of files outside of it's own directories, even when it doesn't
need to do so. Libvirt has no justification to take user:group ownership
of .iso files when it already has read access to them.

The workaround for this is to set dynamic_ownership=0. Unfortunately,
that seems to be breaking the creation of new VMs, as my bug documents.

Just to be clear, my lack of information regarding details was an
indication that defaults are being used: I have made no
permission/ownership changes to anything in libvirt/qemu/et-cetera. I
have made no configuration changes other than setting
dynamic_ownership=0. This is a very new and default libvirt/virt-manager
setup.

Reproducing this issue is as easy as my original report documents: Set
dynamic_ownership=0 and create a new VM with a disk image.

When I have dynamic_ownership=0, and I create a new VM with libvirt and
instruct it to create a new .qcow2 disk, it creates a new file in
/var/lib/libvirt/images/

Unfortunately, the file remains owned by root:root, and libvirt fails to
chown it:

[/var/lib/libvirt]
user@hostname-->sudo ls -alh --color images/
total 74G
drwx--x--x 2 root root 4.0K Nov 11 17:18 .
drwxr-xr-x 6 root root 4.0K Sep 23 19:10 ..
-rw--- 1 libvirt-qemu libvirt-qemu 41G Nov 10 18:03
Debian_unstable.qcow2

-rw--- 1 root root 21G Nov 11 17:18 generic.qcow2
-rw--- 1 libvirt-qemu libvirt-qemu 21G Nov 11 17:17 linuxmint-18.qcow2
-rw--- 1 libvirt-qemu libvirt-qemu 21G Oct 7 20:18 openSUSE.qcow2
-rw--- 1 libvirt-qemu libvirt-qemu 101G Oct 7 20:18 ubuntu14.04.qcow2

If I manually fix the ownership of the file, the VM then can start and
works properly:

[/var/lib/libvirt]
user@hostname-->sudo chown libvirt-qemu:libvirt-qemu images/generic.qcow2

Thus, I'm put in the position where I either have to manually fix the
ownership of all the .iso images that libvirt wrongly and unjustifiably
takes ownership of, or I have to manually fix the ownership of the
.qcow2 files. One way or the other, something is broken.

Bug#833055: [pkg-uWSGI-devel] Bug#833055: Packaging of mongoclient replacement library: mongocxx

2016-11-11 Thread Jonas Smedegaard

Quoting Apollon Oikonomopoulos (2016-11-12 02:13:28)
> On 12:25 Wed 09 Nov , Apollon Oikonomopoulos wrote:
>>> Ok. Apollon, do you want to take up on this offer to handle the move 
>>> to unstable?
>> 
>> I guess I could do it together with the rest of the MongoDB-related 
>> work in a couple of days.
>> 
>
> The package is now in unstable and should (hopefully) work for you.  
> While mongodb-dev is still there, please B-D directly on 
> libmongoclient-dev as I don't plan to keep mongodb-dev around after 
> Stretch.

Thanks a log - to everyone helping out with this bugreport!

I am now working on patching uwsgi to work with the new library, and 
will indeed be build-depending on directly on libmongoclient-dev.

 - Jonas

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

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

Bug#844053: postgresql-common: pg_upgradecluster fails with NOT VALID constraints

2016-11-11 Thread Liam K Morland

Package: postgresql-common
Version: 177
Severity: important

Dear Maintainer,

I attempted to use pg_upgradecluster to update 9.5 to 9.6. One of my 
database tables contains this Check constraint:

"role_id_not_null" CHECK (role_id IS NOT NULL) NOT VALID

(A NOT VALID constraint is one is will be enforced for INSERT and 
UPDATE, but existing data may not meet the constraint.)

During the upgrade, I got this error message:

pg_restore: [archiver (db)] COPY failed for table "scout_registration": ERROR:  
new row for relation "scout_registration" violates check constraint 
"role_id_not_null"

After the upgrade, the table in question was empty. The error message 
was in the middle of the output. A novice user might not notice it and 
lose data because it is not obvious that the upgrade failed.

I suppose that the problem is that pg_restore enforces the constraint. 
To make NOT VALID constraints work, there needs to be an import method 
that does not enforce the constraint.

The command and its output:

$ sudo pg_upgradecluster 9.5 main
Stopping old cluster...
Notice: extra pg_ctl/postgres options given, bypassing systemctl for stop 
operation
Disabling connections to the old cluster during upgrade...
Restarting old cluster with restricted connections...
Redirecting start request to systemctl
Creating new cluster 9.6/main ...
  config /etc/postgresql/9.6/main
  data   /var/lib/postgresql/9.6/main
  locale en_CA.UTF-8
  socket /var/run/postgresql
  port   5433
Disabling connections to the new cluster during upgrade...
Redirecting start request to systemctl
Roles, databases, schemas, ACLs...
Fixing hardcoded library paths for stored procedures...
Upgrading database postgres...
Analyzing database postgres...
Fixing hardcoded library paths for stored procedures...
Upgrading database drupal8...
Analyzing database drupal8...
Fixing hardcoded library paths for stored procedures...
Upgrading database template1...
Analyzing database template1...
Fixing hardcoded library paths for stored procedures...
Upgrading database lkmorlan...
pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error from TOC entry 2288; 0 17795 TABLE DATA 
scout_registration lkmorlan
pg_restore: [archiver (db)] COPY failed for table "scout_registration": ERROR:  
new row for relation "scout_registration" violates check constraint 
"role_id_not_null"
DETAIL:  Failing row contains (94, 2004, null, 21W-T).
CONTEXT:  COPY scout_registration, line 16: "94 2004\N  21W-T"
WARNING: errors ignored on restore: 1
Analyzing database lkmorlan...
Re-enabling connections to the old cluster...
Re-enabling connections to the new cluster...
Copying old configuration files...
Copying old start.conf...
Copying old pg_ctl.conf...
Stopping target cluster...
Redirecting stop request to systemctl
Stopping old cluster...
Redirecting stop request to systemctl
Disabling automatic startup of old cluster...
Configuring old cluster to use a different port (5433)...
Starting target cluster on the original port...
Redirecting start request to systemctl
Success. Please check that the upgraded cluster works. If it does,
you can remove the old cluster with

  pg_dropcluster 9.5 main


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

Kernel: Linux 4.7.0-1-686-pae (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 /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages postgresql-common depends on:
ii  adduser   3.115
ii  debconf [debconf-2.0] 1.5.59
ii  init-system-helpers   1.45
ii  lsb-base  9.20161101
ii  postgresql-client-common  177
ii  procps2:3.3.12-2
ii  ssl-cert  1.0.38
ii  ucf   3.0036

Versions of packages postgresql-common recommends:
ii  logrotate  3.8.7-2

postgresql-common suggests no packages.

-- Configuration Files:
/etc/postgresql-common/createcluster.conf changed:
ssl = on
cluster_name = '%v/%c'
stats_temp_directory = '/var/run/postgresql/%v-%c.pg_stat_tmp'
log_line_prefix = '%%t [%%p-%%l] %%q%%u@%%d '


-- debconf information:
* postgresql-common/ssl: true
* postgresql-common/obsolete-major:
  postgresql-common/catversion-bump:

Bug#844052: glib2.0: FTBFS on !linux due to libmount

Source: glib2.0
Version: 2.50.2-1
Severity: important
Tags: patch
User: debian-h...@lists.debian.org
Usertags: hurd

Hello,

glib2.0 currently FTBFS on !linux because debian/rules inconditionally
enables the use of libmount, available on Linux only.  The attached
patch fixes this.

Samuel

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

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

-- 
Samuel
mdiym42: note to self
mdiym42: make sure your cat is not sleeping in the bass drum before you start 
playing them
--- debian/rules.original   2016-11-12 00:27:33.0 +
+++ debian/rules2016-11-12 00:28:18.0 +
@@ -104,8 +104,12 @@
--enable-static \
--enable-installed-tests \
--enable-always-build-tests \
-   --enable-debug=minimum \
+   --enable-debug=minimum
+
+ifeq ($(DEB_HOST_ARCH_OS), linux)
+DEB_CONFIGURE_FLAGS_deb += \
--enable-libmount
+endif
 
 DEB_CONFIGURE_FLAGS_udeb := \
--disable-selinux \

Bug#844051: unattended-upgrades: Recommends non-existent package need-restart, should be needrestart ?

2016-11-11 Thread Felipe Sateler

Package: unattended-upgrades
Version: 0.93
Severity: normal

As subject says.

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

Kernel: Linux 4.8.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 unattended-upgrades depends on:
ii  apt1.3.1
ii  apt-utils  1.3.1
ii  debconf [debconf-2.0]  1.5.59
ii  init-system-helpers1.46
ii  lsb-base   9.20161101
ii  lsb-release9.20161101
ii  python33.5.1-4
ii  python3-apt1.1.0~beta5
ii  ucf3.0036
ii  xz-utils   5.2.2-1.2

Versions of packages unattended-upgrades recommends:
ii  anacron 2.3-23
ii  cron [cron-daemon]  3.0pl1-128

Versions of packages unattended-upgrades suggests:
ii  bsd-mailx  8.1.2-0.20160123cvs-3
ii  nullmailer [mail-transport-agent]  1:1.13-1.2

-- debconf information:
  unattended-upgrades/origins_pattern: 
"origin=Debian,codename=${distro_codename},label=Debian-Security";
  unattended-upgrades/enable_auto_updates: true

Bug#833055: Packaging of mongoclient replacement library: mongocxx

2016-11-11 Thread Apollon Oikonomopoulos

Hi,

On 12:25 Wed 09 Nov , Apollon Oikonomopoulos wrote:
> > Ok. Apollon, do you want to take up on this offer to handle the move 
> > to
> > unstable?
> 
> I guess I could do it together with the rest of the MongoDB-related work 
> in a couple of days.
> 

The package is now in unstable and should (hopefully) work for you.  
While mongodb-dev is still there, please B-D directly on 
libmongoclient-dev as I don't plan to keep mongodb-dev around after 
Stretch.

Regards,
Apollon

Bug#844050: cryptsetup: /lib/cryptsetup/scripts/decrypt_ssl throws away the key it has just decrypted

2016-11-11 Thread g1

Package: cryptsetup
Version: 2:1.6.6-5
Severity: normal

In /lib/cryptsetup/scripts/decrypt_ssl the relevant decryption command,
/usr/bin/openssl enc -aes-256-cbc -d -salt -in $1 >/dev/null 2>&1
redirects output from openssl enc -d to /dev/null, rendering the script
useless except for checking the key can actually be decrypted.  I'm not sure
that was the intent.

Best regards,
g.

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

Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages cryptsetup depends on:
ii  cryptsetup-bin 2:1.6.6-5
ii  debconf [debconf-2.0]  1.5.56
ii  dmsetup2:1.02.90-2.2+deb8u1
ii  libc6  2.19-18+deb8u6

Versions of packages cryptsetup recommends:
pn  busybox | busybox-static
pn  console-setup   
ii  initramfs-tools [linux-initramfs-tool]  0.120+deb8u2
ii  kbd 1.15.5-2

Versions of packages cryptsetup suggests:
ii  dosfstools  3.0.27-1
pn  keyutils
ii  liblocale-gettext-perl  1.05-8+b1

-- debconf information excluded

Bug#844049: graphicsmagick-imagemagick-compat: graphicsmagic-imagemagick-compat wants to deinstall cups an bluetooth-packages on install

2016-11-11 Thread Jakobus Schürz

Package: graphicsmagick-imagemagick-compat
Version: 1.3.25-5
Severity: important

Dear Maintainer,

When i try to install this package, apt shows me the following:

LANG=C apt-get install graphicsmagick-imagemagick-compat 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer
required:
bc cups-browsed cups-core-drivers cups-daemon
cups-filters-core-drivers cups-ppdc cups-server-common dc
foomatic-db-compressed-ppds foomatic-db-engine foomatic-filters
hplip-data libcupscgi1 libcupsmime1
libcupsppdc1 libfontembed1 libgutenprint2 libhpmud0 libpaps0
libqpdf17 libsane-hpaio mscompress openprinting-ppds paps
printer-driver-all printer-driver-brlaser printer-driver-c2050
printer-driver-c2esp
printer-driver-cjet printer-driver-dymo printer-driver-escpr
printer-driver-foo2zjs printer-driver-foo2zjs-common
printer-driver-hpijs printer-driver-m2300w printer-driver-min12xxw
printer-driver-pnm2ppa
printer-driver-ptouch printer-driver-pxljr
printer-driver-sag-gdi python3-dbus.mainloop.pyqt5
python3-pexpect python3-ptyprocess python3-pyqt5 qpdf
system-config-printer
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
foomatic-filters libpaps0 paps
The following packages will be REMOVED:
bluez-cups cups cups-filters cups-pdf hpijs-ppds hplip
hplip-gui imagemagick imagemagick-6.q16
printer-driver-cups-pdf printer-driver-gutenprint
printer-driver-hpcups printer-driver-postscript-hp
printer-driver-splix task-print-server
The following NEW packages will be installed:
foomatic-filters graphicsmagick-imagemagick-compat
libpaps0 paps
0 upgraded, 4 newly installed, 15 to remove and 0 not
upgraded.
Need to get 208 kB of archives.
After this operation, 23.4 MB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.

So i didn't install this package.

Is this correct?

Regards

Jakob


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

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

Bug#844048: mysql-common: Fails to install when conffile /etc/mysql/my.cnf.fallback is removed

2016-11-11 Thread Felipe Sateler

Package: mysql-common
Version: 5.8+1.0.1
Severity: normal

As subject says. Error is:

update-alternatives: error: alternative path /etc/mysql/my.cnf.fallback doesn't 
exist


Perhaps preinst should recreate it before running update-alternatives?
If not desired, maybe it can suggest how to fix the issue (dpkg
--force-confask)

Saludos

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

Kernel: Linux 4.8.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)

-- no debconf information

Bug#843944: tracker.debian.org: please add “changes” anchor in news entries

2016-11-11 Thread Paul Wise

On Fri, 2016-11-11 at 14:33 +0100, Cyril Brulebois wrote:

> Is the code really deployed? 

Yes.

> I suspected maybe only new news pages would have this change (others
> might have been generated/cached already) but that doesn't seem to be
> the case, e.g.:
>   https://tracker.debian.org/news/814326

If you look in _process_package_event, you will see that it stores HTML
in the database! So your change would only affect new events indeed.
It looks like what you patched is only used for the plain text news
renderer but not for the email news renderer however.

> Or maybe I didn't patch the right code path?

That looks like the case indeed. These appears to be the right ones:

distro_tracker/core/templates/core/news-email.html: email-news-body
distro_tracker/core/models.py: EmailNewsRenderer

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

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

Bug#801084:

2016-11-11 Thread Azamat Hackimov

Hello.

You can use https://github.com/winterheart/broadcom-bt-firmware as base for
packaging.

Bug#844040: python-bashate is lagging 4 versions and more than 2 years, please package an up-to-date version

2016-11-11 Thread Víctor Cuadrado Juan

reopen 844040
thanks

I'm reopening this bug instead of refiling it again, since it was reassigned
seconds before it was closed, and this way seems cleaner.


-- 
Víctor Cuadrado Juan   m...@viccuad.me

PGP key ID: 4096R: 0xA2591E231E251F36
Key fingerprint: E3C5 114C 0C5B 4C49 BA03  0991 A259 1E23 1E25 1F36
My signed E-Mails are trustworthy.



signature.asc
Description: OpenPGP digital signature

Bug#844047: c-blosc: FTBFS on !linux

Source: c-blosc
Version: 1.11.1+ds1-2.2
Severity: important
Tags: upstream patch
User: debian-h...@lists.debian.org
Usertags: hurd

Hello,

c-blosc currently FTBFS on !linux because it confuses Mach with Darwin,
and it doesn't know that all glibc-enabled systems have CLOCK_MONOTONIC
in . The attached patch fixes that.

Samuel

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

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

-- 
Samuel
 RR> Ce que je cherche à démontrer, c'est qu'il est injuste de faire
 RR> l'amalgame entre du bulk mail et du courrier non-solicité très ciblé
 un suppositoire non reclamé, meme tres bien ciblé, reste un suppositoire.
 -+-OS in : Guide du Neuneu d'Usenet - Plein le cul de la pub à neuneu -+-
--- bench/bench.c.original  2016-11-12 00:04:38.0 +
+++ bench/bench.c   2016-11-12 00:06:59.0 +
@@ -31,14 +31,14 @@
 #if defined(_WIN32)
   /* For QueryPerformanceCounter(), etc. */
   #include 
-#elif defined(__MACH__)
+#elif defined(__MACH__) && defined(__APPLE__)
   #include 
   #include 
   #include 
   #include 
 #elif defined(__unix__)
   #include 
-  #if defined(__linux__)
+  #if defined(__GLIBC__)
 #include 
   #else
 #include 
@@ -89,7 +89,7 @@
 
 /* Set a timestamp value to the current time. */
 void blosc_set_timestamp(blosc_timestamp_t* timestamp) {
-#ifdef __MACH__ // OS X does not have clock_gettime, use clock_get_time
+#if defined(__MACH__) && defined(__APPLE__) // OS X does not have 
clock_gettime, use clock_get_time
   clock_serv_t cclock;
   mach_timespec_t mts;
   host_get_clock_service(mach_host_self(), CALENDAR_CLOCK, );

Bug#844046: RFP: python-weasyprint -- converts HTML/CSS documents to PDF

2016-11-11 Thread W. Martin Borgert

Package: wnpp
Severity: wishlist

* Package name: python-weasyprint
  Version : v0.31
  Upstream Author : Simon Sapin 
* URL : http://weasyprint.org/
* License : BSD
  Programming Lang: Python
  Description : converts HTML/CSS documents to PDF

WeasyPrint is a visual rendering engine for HTML and CSS that
can export to PDF. It aims to support web standards for
printing.

It is based on various libraries but not on a full rendering
engine like WebKit or Gecko. The CSS layout engine is written in
Python, designed for pagination, and meant to be easy to hack
on.

Note: The package needs pyphen (pure Python hyphenation) and
tinycss(2?) (Python CSS parser), which are not yet in Debian.

Bug#844045: gr-radar: FTBFS (linking error)

Package: src:gr-radar
Version: 0.0.0.20160615-3
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- -DLIB_SUFFIX=/x86_64-linux-gnu 
-DCMAKE_BUILD_TYPE="RelWithDebInfo"
cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DLIB_SUFFIX=/x86_64-linux-gnu 
-DCMAKE_BUILD_TYPE=RelWithDebInfo
-- The CXX compiler identification is GNU 6.2.0
-- The C compiler identification is GNU 6.2.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info

[... snipped ...]

[ 58%] Building CXX object 
lib/CMakeFiles/gnuradio-radar.dir/os_cfar_2d_vc_impl.cc.o
cd /<>/obj-x86_64-linux-gnu/lib && /usr/bin/c++   -DQT_CORE_LIB 
-DQT_GUI_LIB -DQT_NO_DEBUG -Dgnuradio_radar_EXPORTS -I/<>/lib 
-I/<>/include -I/<>/obj-x86_64-linux-gnu/lib 
-I/<>/obj-x86_64-linux-gnu/include -I/usr/include/qwt 
-I/usr/include/qt4 -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtCore  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -O2 -g -DNDEBUG -fPIC  
 -std=gnu++98 -o CMakeFiles/gnuradio-radar.dir/os_cfar_2d_vc_impl.cc.o -c 
/<>/lib/os_cfar_2d_vc_impl.cc
[ 59%] Building CXX object 
lib/CMakeFiles/gnuradio-radar.dir/estimator_ofdm_impl.cc.o
cd /<>/obj-x86_64-linux-gnu/lib && /usr/bin/c++   -DQT_CORE_LIB 
-DQT_GUI_LIB -DQT_NO_DEBUG -Dgnuradio_radar_EXPORTS -I/<>/lib 
-I/<>/include -I/<>/obj-x86_64-linux-gnu/lib 
-I/<>/obj-x86_64-linux-gnu/include -I/usr/include/qwt 
-I/usr/include/qt4 -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtCore  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -O2 -g -DNDEBUG -fPIC  
 -std=gnu++98 -o CMakeFiles/gnuradio-radar.dir/estimator_ofdm_impl.cc.o -c 
/<>/lib/estimator_ofdm_impl.cc
[ 61%] Building CXX object 
lib/CMakeFiles/gnuradio-radar.dir/estimator_rcs_impl.cc.o
cd /<>/obj-x86_64-linux-gnu/lib && /usr/bin/c++   -DQT_CORE_LIB 
-DQT_GUI_LIB -DQT_NO_DEBUG -Dgnuradio_radar_EXPORTS -I/<>/lib 
-I/<>/include -I/<>/obj-x86_64-linux-gnu/lib 
-I/<>/obj-x86_64-linux-gnu/include -I/usr/include/qwt 
-I/usr/include/qt4 -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtCore  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -O2 -g -DNDEBUG -fPIC  
 -std=gnu++98 -o CMakeFiles/gnuradio-radar.dir/estimator_rcs_impl.cc.o -c 
/<>/lib/estimator_rcs_impl.cc
[ 62%] Building CXX object 
lib/CMakeFiles/gnuradio-radar.dir/trigger_command_impl.cc.o
cd /<>/obj-x86_64-linux-gnu/lib && /usr/bin/c++   -DQT_CORE_LIB 
-DQT_GUI_LIB -DQT_NO_DEBUG -Dgnuradio_radar_EXPORTS -I/<>/lib 
-I/<>/include -I/<>/obj-x86_64-linux-gnu/lib 
-I/<>/obj-x86_64-linux-gnu/include -I/usr/include/qwt 
-I/usr/include/qt4 -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtCore  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -O2 -g -DNDEBUG -fPIC  
 -std=gnu++98 -o CMakeFiles/gnuradio-radar.dir/trigger_command_impl.cc.o -c 
/<>/lib/trigger_command_impl.cc
[ 64%] Linking CXX shared library libgnuradio-radar.so
cd /<>/obj-x86_64-linux-gnu/lib && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/gnuradio-radar.dir/link.txt --verbose=1
/usr/bin/c++  -fPIC -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -O2 -g -DNDEBUG  -Wl,-z,relro -shared 
-Wl,-soname,libgnuradio-radar.so.3.7.10 -o libgnuradio-radar.so.3.7.10 
CMakeFiles/gnuradio-radar.dir/moc_scatter_plot.cxx.o 
CMakeFiles/gnuradio-radar.dir/moc_time_plot.cxx.o 
CMakeFiles/gnuradio-radar.dir/moc_spectrogram_plot.cxx.o 
CMakeFiles/gnuradio-radar.dir/scatter_plot.cc.o 
CMakeFiles/gnuradio-radar.dir/time_plot.cc.o 
CMakeFiles/gnuradio-radar.dir/spectrogram_plot.cc.o 
CMakeFiles/gnuradio-radar.dir/signal_generator_cw_c_impl.cc.o 
CMakeFiles/gnuradio-radar.dir/signal_generator_fmcw_c_impl.cc.o 
CMakeFiles/gnuradio-radar.dir/split_cc_impl.cc.o 
CMakeFiles/gnuradio-radar.dir/os_cfar_c_impl.cc.o 
CMakeFiles/gnuradio-radar.dir/ts_fft_cc_impl.cc.o 
CMakeFiles/gnuradio-radar.dir/estimator_cw_impl.cc.o 
CMakeFiles/gnuradio-radar.dir/print_results_impl.cc.o 
CMakeFiles/gnuradio-radar.dir/static_target_si
 mulator_cc_impl.cc.o 
CMakeFiles/gnuradio-radar.dir/signal_generator_fsk_c_impl.cc.o 
CMakeFiles/gnuradio-radar.dir/split_fsk_cc_impl.cc.o

Bug#844044: gstreamer1.0: FTBFS on hurd-i386

Source: gstreamer1.0
Version: 1.10.0-2
Severity: important
Tags: upstream patch
User: debian-h...@lists.debian.org
Usertags: hurd

Hello,

gstreamer1.0 currently FTBFS on hurd-i386 because it erroneously
compiles clock_gettime.c on all archs because of a missing
AM_CONDITIONAL. It works on Linux only by luck, because __MACH__ is not
defined there, but it is on the Hurd since it uses a Mach kernel. But
gstreamer happens to confuse __MACH__ with "building on MacOS", and
starts using MacOS-specific mach calls, which don't exist on GNU Mach...

The attached patch fixes the build of clock_gettime.c by making
it properly detect Darwin, and it fixes not actually building
clock_gettime.c when clock_gettime is actually available, since it can
only bring issues, and it's probably only by luck if it never has on
Linux yet.

Samuel

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

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

-- 
Samuel
 je sens venir la fonte 14 pour le rapport
 -+- #ens-mim -+-
--- ./libs/gst/check/libcheck/clock_gettime.c.original  2016-11-11 
23:41:33.0 +
+++ ./libs/gst/check/libcheck/clock_gettime.c   2016-11-11 23:43:09.0 
+
@@ -1,6 +1,6 @@
 #include "libcompat.h"
 
-#ifdef __MACH__
+#if defined(__MACH__) && defined(__APPLE__)
 #include 
 #include 
 #include 
@@ -15,7 +15,7 @@
 clock_gettime (clockid_t clk_id CK_ATTRIBUTE_UNUSED, struct timespec *ts)
 {
 
-#ifdef __MACH__
+#if defined(__MACH__) && defined(__APPLE__)
   /* OS X does not have clock_gettime, use mach_absolute_time */
 
   static mach_timebase_info_data_t sTimebaseInfo;
--- ./m4/check-checks.m4.original   2016-11-11 23:52:21.0 +
+++ ./m4/check-checks.m42016-11-11 23:52:30.0 +
@@ -95,7 +95,7 @@
 AM_CONDITIONAL(HAVE_TIMER_CREATE_SETTIME_DELETE, test 
"x$ac_cv_lib_rt_timer_create__timer_settime__timer_delete" = "xyes")
 
 dnl Allow for checking HAVE_CLOCK_GETTIME in automake files
-AM_CONDITIONAL(HAVE_CLOCK_GETTIME, test "x$HAVE_CLOCK_GETTIME" = "xyes")
+AM_CONDITIONAL(HAVE_CLOCK_GETTIME, test "x$CLOCK_GETTIME_FOUND" = "xyes")
 
 dnl Create _stdint.h in the top-level directory
 AX_CREATE_STDINT_H

Bug#792859: Xession not executable

2016-11-11 Thread Neil Schemenauer

I ran into this bug today.  It took me nearly an hour to find out
the problem.  I never installed a copy of Xsession or removed the
executable bit on it.  Something in Debian created the situation.

Could we have a post-inst script that ensures the file is
executable?  I'm quite sure the average user it not going to solve
this if they run into it.  At minimum, something should write a
warning to the lightdm log file.

Bug#844043: git: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

Package: src:git
Version: 1:2.10.2-2
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with apache2
   dh_testdir -i
   dh_update_autotools_config -i
   debian/rules override_dh_auto_build-indep
make[1]: Entering directory '/<>'
gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/6/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 6.2.0-10' 
--with-bugurl=file:///usr/share/doc/gcc-6/README.Bugs 
--enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr 
--program-suffix=-6 --program-prefix=x86_64-linux-gnu- --enable-shared 
--enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext 
--enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ 
--enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie 
--with-system-zlib --disable-browser-plugin --enable-java-awt=gtk 
--enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-6-amd64/jre 
--enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-6-amd64 
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-6-amd64 
--with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar 
--enable-objc-g
 c --enable-multiarch --with-arch-32=i686 --with-abi=m64 
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic 
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu 
--target=x86_64-linux-gnu
Thread model: posix

[... snipped ...]

make[2]: Leaving directory '/<>/contrib/subtree'
make[2]: Entering directory '/<>/contrib/subtree'
xmlto -m ../../Documentation/manpage-normal.xsl man git-subtree.xml
make[2]: Leaving directory '/<>/contrib/subtree'
make[2]: Entering directory '/<>/contrib/subtree'
install -d -m 755 /<>/debian/tmp/usr/share/man/man1
install -m 644 git-subtree.1 /<>/debian/tmp/usr/share/man/man1
make[2]: Leaving directory '/<>/contrib/subtree'
make[2]: Entering directory '/<>/contrib/subtree'
asciidoc -b xhtml11 -d manpage -f ../../Documentation/asciidoc.conf \
-agit_version=2.10.2 git-subtree.txt
make[2]: Leaving directory '/<>/contrib/subtree'
make[2]: Entering directory '/<>/contrib/subtree'
install -d -m 755 /<>/debian/tmp/usr/share/doc/git/html
install -m 644 git-subtree.html 
/<>/debian/tmp/usr/share/doc/git/html
make[2]: Leaving directory '/<>/contrib/subtree'
make[1]: Entering directory '/<>'
install -m 0644 contrib/subtree/git-subtree.txt 
'/<>/debian/tmp'/html
# RelNotes are shipped in git
rm -rf '/<>/debian/tmp'/html/RelNotes
# don't include git-p4 man page
rm -f '/<>/debian/tmp'/html/git-p4.*
make[1]: Leaving directory '/<>'
   debian/rules override_dh_install-indep
make[1]: Entering directory '/<>'
dh_install --indep
for i in git-archimport git-cvs git-p4 git-svn git-send-email gitk \
 git-gui git-citool; do \
  rm -f '/<>/debian/git'-man/usr/share/man/man1/$i*; \
done
rm -f '/<>/debian/git'-man/usr/share/man/man3/Git::SVN*.3pm
make[1]: Leaving directory '/<>'
   dh_apache2 -i
   debian/rules override_dh_installdocs
make[1]: Entering directory '/<>'
install -d -m0755 '/<>/debian/git'-core/usr/share/doc
ln -s git '/<>/debian/git'-core/usr/share/doc/git-core
dh_installdocs -X.gitignore
# These licenses are replaced with symlinks in git.links.
diff -q 
'/<>/debian/git'/usr/share/doc/git/contrib/persistent-https/LICENSE
 /usr/share/common-licenses/Apache-2.0
diff: 
/<>/debian/git/usr/share/doc/git/contrib/persistent-https/LICENSE: 
No such file or directory
debian/rules:126: recipe for target 'override_dh_installdocs' failed
make[1]: *** [override_dh_installdocs] Error 2
make[1]: Leaving directory '/<>'
debian/rules:41: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


The relevant part of the build log is included above.

This happens because debian/git/[...] does not exist, as we are creating
arch-independent packages only.

I would try splitting override_dh_installdocs into
override_dh_installdocs-arch and override_dh_installdocs-indep.

Thanks.

Bug#842112: digikam: Export menu does not open - workaround

On Thursday, November 10, 2016 8:20:12 PM CST you wrote:
> I had the same issue on my setup.
> Installing kipi-plugins package solved the problem for me.
> Shouldn't kipi-plugins be in dependencies of digikam package?

Thank you!   I un-installed kipi-plugins and now I can reproduce the problem.  

I agree that digikam should have a dependency; at least the Recommends level 
-- which is what "showfoto" has -- if not a full Depends.

-Steve


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

Bug#843989: Please merge "fstab-generator: add x-systemd.mount-timeout" in v232

2016-11-11 Thread Michael Biebl

Control: tags -1 + pending

Am 11.11.2016 um 16:09 schrieb Alexander Kurtz:
> Package: src:systemd
> Version: 232-3
> Severity: wishlist
> 
> Hi!
> 
> Upstream just merged a patch fixing issue #4055 [0]; it would be really
> nice if you could merge this in v232, since the next systemd version is
> probably still some months away and this significantly simplifies
> mounting large btrfs file systems! 

Seems ok with me.

Cherry-picked as 20c006d


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



signature.asc
Description: OpenPGP digital signature

Bug#844042: node-cross-spawn-async: FTBFS (Cannot find module 'lru-cache')

Package: src:node-cross-spawn-async
Version: 2.1.9-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   dh_auto_build -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
nodejs test/prepare && mocha -C -R spec test/test
Copied "prepare_()%!^&;, .sh" to "()%!^&;, "
module.js:327
throw err;
^

Error: Cannot find module 'lru-cache'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/<>/lib/parse.js:2:22)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/<>/index.js:2:14)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/<>/test/util/buffered.js:3:13)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/<>/test/test.js:9:16)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at /usr/lib/nodejs/mocha/lib/mocha.js:172:27
at Array.forEach (native)
at Mocha.loadFiles (/usr/lib/nodejs/mocha/lib/mocha.js:169:14)
at Mocha.run (/usr/lib/nodejs/mocha/lib/mocha.js:356:31)
at Object. (/usr/lib/nodejs/mocha/bin/_mocha:366:16)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Function.Module.runMain (module.js:441:10)
at startup (node.js:139:18)
at node.js:974:3
debian/rules:11: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Looks like a missing build-depends.

Even if this is Arch:all, please consider uploading in source-only form,
so that these kind of bugs do not propagate to testing.

Thanks.

Bug#842906: lua-sec 0.6 is not compatible with lua 5.1

2016-11-11 Thread Elia Argentieri

> > lua-sec 0.6 is not compatible with lua 5.1
> 
> Are you sure about that? The rockspec says:
>
> dependencies = {
>"lua >= 5.1", "luasocket"
> }

I am, rockspec might be wrong. See https://github.com/brunoos/luasec,
it says "Lua 5.2 and 5.3 compatibility", but no lua 5.1 is mentioned.

Bug#843953: multipath-tools: LVM on internal disks + multipath-toosl = no multipaths

2016-11-11 Thread Vincent McIntyre

On Fri, Nov 11, 2016 at 04:06:44PM +0530, Ritesh Raj Sarraf wrote:
> > Related notes:
> > 
> >    On some reboots the system log shows multipath timing out. Below is 
> > 'sdd'.
> >    The timeout occurs 33 seconds after the disk was attached.
> >    I was unable to determine the cause of this or reproduce consistently.
> > 
> >    Nov 11 11:11:53  kernel: sd 1:0:0:4: [sdd] 25769805824 512-byte logical
> > blocks: (13.1 TB/12.0 TiB)
> >    Nov 11 11:11:53  kernel: sd 1:0:0:4: [sdd] Write Protect is off
> >    Nov 11 11:11:53  kernel: sd 1:0:0:4: [sdd] Mode Sense: 97 00 10 08
> >    Nov 11 11:11:53  kernel: sd 1:0:0:4: [sdd] Write cache: enabled, read
> > cache: enabled, supports DPO and FUA
> >    Nov 11 11:11:53  kernel:  sdd: sdd1
> >    Nov 11 11:11:53  kernel: sd 1:0:0:4: [sdd] Attached SCSI disk
> >    ...
> >    Nov 11 11:12:25  systemd-udevd[346]: timeout '/sbin/multipath -v0 
> > /dev/sdd'
> >    Nov 11 11:12:26  systemd-udevd[346]: timeout: killing '/sbin/multipath 
> > -v0
> > /dev/sdd' [459]
> >    Nov 11 11:12:26  systemd-udevd[346]: '/sbin/multipath -v0 /dev/sdd' [459]
> > terminated by signal 9 (Killed)
> > 
> 
> This is mostly the locking issue which you mentioned in the other bug.

This still occurs, but the system is able to recover from it.
I'll send you the log out of band.

> > Requests:
> > 
> > Can we please have sg3-utils v1.42 added to a stable point release?
> > Also multipath-tools needs to depend on sg3-utils-udev.
> > 
> 
> So as I understand, for now, you've already picked the fixed
> versions from testing for your setup.
 
Yes, that's the best way to summarise it.

> For this issue, multipath-tools doesn't really have any code
> change. The change is required in sg3-utils. For the stable
> release, I'm not sure what to do. 
> 
> 1. New releases are not allowed in stable
> 2. Backports could cover this case, but I really can't commit
>right now, on when I can get this done.
 
I understand. Probably backports, since it is hard to know what could
happen on systems that work already without the package.

> > It seems a shame to not include the shared lock patch as it avoids
> > a known deadlock and the system still works fine with it included.
> > 
> 
> Indeed. But, as I mentioned in other bug report, it was submitted
> upstream very recently only. And unless something is committed
> upstream, I don't pick it as a fix for Debian Stable.

Oh. I thought the link I gave was to the upstream repository...hm.
That's the repo Christoph's page links to.
I can see the commit in the master branch, what am I missing?

> I'd suggest, you pick the contents of sg3-utils-udev, for now.
> There's nothing other than the udev rules, in that package.
 
I've pretty much done that. I'll stick with the newer sg3-utils too.

> PS: You may also want to make plans for Stretch now. There are
> many more changes in multipath in the Stretch version. Having
> a test setup and reporting bugs in the development phase helps
> much more.

I am planning on this. I had some 'adventures' with 0.6.3 and the
4.7 backport kernel before trying the path I've described.

You may as well close this bug as wontfix, the workaround is just
install sg3-utils-udev.

Vince

Bug#844041: nvidia-cuda-toolkit: FTBFS (cannot create /dev/tty)

Package: src:nvidia-cuda-toolkit
Version: 8.0.44-2
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
perl -p \
-e 's{#VERSION_TOOLKIT#}{8.0.44}g;' \
-e 's{#SOVERSION#}{8.0}g;' \
-e 's{#CUDA_DOWNLOAD_URL#}{https://developer.nvidia.com/cuda-downloads}g;' \
-e 's{#LIBDIR#}{usr/lib/x86_64-linux-gnu}g;' \
-e 's{#MAN_DATE#}{8 Sep 2016}g;' \
< debian/libcudartSOVER.install.in > debian/libcudartSOVER.install

[... snipped ...]

cp debian/libnppicomSOVER.lintian-overrides 
debian/libnppicom8.0.lintian-overrides
cp debian/libnppicomSOVER.symbols debian/libnppicom8.0.symbols
cp debian/libnppideiSOVER.install debian/libnppidei8.0.install
cp debian/libnppideiSOVER.lintian-overrides 
debian/libnppidei8.0.lintian-overrides
cp debian/libnppideiSOVER.symbols debian/libnppidei8.0.symbols
cp debian/libnppifSOVER.install debian/libnppif8.0.install
cp debian/libnppifSOVER.lintian-overrides debian/libnppif8.0.lintian-overrides
cp debian/libnppifSOVER.symbols debian/libnppif8.0.symbols
cp debian/libnppigSOVER.install debian/libnppig8.0.install
cp debian/libnppigSOVER.lintian-overrides debian/libnppig8.0.lintian-overrides
cp debian/libnppigSOVER.symbols debian/libnppig8.0.symbols
cp debian/libnppimSOVER.install debian/libnppim8.0.install
cp debian/libnppimSOVER.lintian-overrides debian/libnppim8.0.lintian-overrides
cp debian/libnppimSOVER.symbols debian/libnppim8.0.symbols
cp debian/libnppistSOVER.install debian/libnppist8.0.install
cp debian/libnppistSOVER.lintian-overrides debian/libnppist8.0.lintian-overrides
cp debian/libnppistSOVER.symbols debian/libnppist8.0.symbols
cp debian/libnppisuSOVER.install debian/libnppisu8.0.install
cp debian/libnppisuSOVER.lintian-overrides debian/libnppisu8.0.lintian-overrides
cp debian/libnppisuSOVER.symbols debian/libnppisu8.0.symbols
cp debian/libnppitcSOVER.install debian/libnppitc8.0.install
cp debian/libnppitcSOVER.lintian-overrides debian/libnppitc8.0.lintian-overrides
cp debian/libnppitcSOVER.symbols debian/libnppitc8.0.symbols
cp debian/libnppsSOVER.install debian/libnpps8.0.install
cp debian/libnppsSOVER.lintian-overrides debian/libnpps8.0.lintian-overrides
cp debian/libnppsSOVER.symbols debian/libnpps8.0.symbols
cp debian/libnvblasSOVER.install debian/libnvblas8.0.install
cp debian/libnvblasSOVER.lintian-overrides debian/libnvblas8.0.lintian-overrides
cp debian/libnvblasSOVER.symbols debian/libnvblas8.0.symbols
cp debian/libnvgraphSOVER.install debian/libnvgraph8.0.install
cp debian/libnvgraphSOVER.lintian-overrides 
debian/libnvgraph8.0.lintian-overrides
cp debian/libnvgraphSOVER.symbols debian/libnvgraph8.0.symbols
cp debian/libnvrtcSOVER.install debian/libnvrtc8.0.install
cp debian/libnvrtcSOVER.lintian-overrides debian/libnvrtc8.0.lintian-overrides
cp debian/libnvrtcSOVER.symbols debian/libnvrtc8.0.symbols
dh_testdir
rm -f -r nvidia-cuda-amd64 nvidia-cuda-amd64.tmp
sh cuda-linux64-rel-8.0.44-21122537.run --noexec --keep --target 
nvidia-cuda-amd64.tmp
Creating directory nvidia-cuda-amd64.tmp
Verifying archive integrity... All good.
Uncompressing NVIDIA 
CUDA.

Bug#844040: Package: src:python-bashate: python-bashate is lagging 4 versions and more than 2 years, please package an up-to-date version

2016-11-11 Thread Víctor Cuadrado Juan

Package: Package
Severity: important
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

python-bashate is lagging 4 versions and 2 years plus a month,
please package an up-to-date version.

I'm tagging this as important since I can't use the current packaged
version on emacs with flycheck. I suppose that is not the only
broken interaction with this package that exists because of old
upstream version.



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

Kernel: Linux 4.7.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)

-BEGIN PGP SIGNATURE-

iQEcBAEBCgAGBQJYJldcAAoJECI/Fcparw54E/EIAMCkWLCXYX1WFqtSNfuDjKrv
szKWEtXQsds+d3wX11HkJS24i8bw5w0+2jShQtojj9hrcnG7ozuslphqbZE/DGWF
PowjglN53n6KffJHb0Dmt1ZOBPef25nojdMScOz8Z0+PBP1EJfFEWxsXi/AlKkk4
gbi+UqSEH68K8yMqHlJHETkz69Evy9ZGJuUk8ytChpU01iQPTjlB+ywb0Oz4QoUI
MYXE6jDVsbUfQ2bSKj6UbXY3va5RQ67PkYwptDWmyBN8jWe7DOq7DgpMWtYszYDt
WKaA5Wj9bPb15cDvn6aeqGtW2r+9YcFIjBYFxd5NOF5AQTSs0jW+Irlgx8Y+ZWE=
=hT/b
-END PGP SIGNATURE-

Bug#439121: Add a .pc file for libapt-pkt

2016-11-11 Thread David Kalnischkies

Hi,

On Sat, Oct 29, 2016 at 04:34:24PM +0200, Corentin Noël wrote:
> Here is a patch adding the pkg-config files for the apt-pkg and apt-inst
> packages.

Thanks!

Unfortunately, I am not experienced with pkg-config stuff, so ideally
I will leave that up for someone else to handle, but a few superficial
comments none the less:

> +Name: @PACKAGE@

"Name: apt" feels strange. Especially if we ship two with the same name…
I think I would expect (lib)apt-pkg or (lib)apt-inst here. Not sure.

> +Description: Read deb packages informations
> +Description: Manage deb packages

That is… very generic to a point that it is nearly wrong.  Maybe:
query and extract information from deb packages &
query and manage packages and the metadata about them

(which is roughly what the Description fields in debian/control say)

The URL could be our tracker page [0], it is the closest we have to
a Homepage and contains all the usual pointers like Git, News, Bugs, …

[0] https://tracker.debian.org/pkg/apt

> +install(FILES ${CMAKE_CURRENT_BINARY_DIR}/apt-pkg.pc DESTINATION 
> ${CMAKE_INSTALL_LIBDIR}/pkgconfig)

That doesn't seem to be enough to install the files. At least I don't
see them shipped in libapt-pkg-dev with this alone. You will likely need
to adapt debian/libapt-pkg-dev.install.

Slightly related: It seems relatively conventional that library packages
have an autopkgtest compiling the equivalent of a hello world program
against them. Adding such a test shouldn't be hard (at least I hope so)
& could provide some confidence that the pkg-config files actually work
(and will continue to work in the future) – and that the libraries
aren't completely broken either of course. :)

Best regards

David Kalnischkies

signature.asc
Description: PGP signature

Bug#844039: ctrl-alt-del.target symlink is shipped twice in /etc and /lib

2016-11-11 Thread Michael Biebl

Package: systemd
Version: 232-3
Severity: normal

For some reason, since v232, we ship two ctrl-alt-del.target, both
pointing at /lib/systemd/system/reboot.target

# ls -al /lib/systemd/system/ctrl-alt-del.target 
/etc/systemd/system/ctrl-alt-del.target
lrwxrwxrwx 1 root root 33 Nov  9 08:34 /etc/systemd/system/ctrl-alt-del.target 
-> /lib/systemd/system/reboot.target
lrwxrwxrwx 1 root root 13 Nov  9 08:34 /lib/systemd/system/ctrl-alt-del.target 
-> reboot.target

Both symlinks are created by the upstream build system, so we should
maybe fix it there as well:

GENERAL_ALIASES += \
   $(systemunitdir)/reboot.target 
$(pkgsysconfdir)/system/ctrl-alt-del.target \

and

SYSTEM_UNIT_ALIASES += \
   graphical.target default.target \
   reboot.target ctrl-alt-del.target \


-- Package-specific info:

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

Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=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.10.95-6
ii  libaudit1   1:2.6.7-1
ii  libblkid1   2.29-1
ii  libc6   2.24-5
ii  libcap2 1:2.25-1
ii  libcryptsetup4  2:1.7.3-2
ii  libgcrypt20 1.7.3-2
ii  libgpg-error0   1.24-2
ii  libidn111.33-1
ii  libip4tc0   1.6.0-4
ii  libkmod223-1
ii  liblz4-10.0~r131-2
ii  liblzma55.2.2-1.2
ii  libmount1   2.29-1
ii  libpam0g1.1.8-3.3
ii  libseccomp2 2.3.1-2
ii  libselinux1 2.6-3
ii  libsystemd0 232-3
ii  mount   2.29-1
ii  util-linux  2.29-1

Versions of packages systemd recommends:
ii  dbus1.10.12-1
ii  libpam-systemd  232-3

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

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

-- no debconf information

Bug#844038: ocamlnet: FTBFS on hurd-i386: PATH_MAX

Source: ocamlnet
Version: 4.1.2-1
Severity: important
Tags: upstream patch
User: debian-h...@lists.debian.org
Usertags: hurd

Hello,

ocamlnet currently FTBFS on hurd-i386 due to an inconditional usage of
PATH_MAX, which is not defined there since there is no such arbitrary
limit. The attached patch avoids using by by just reading the symlink
length, and adjusting the size in case the symlink length increased in
between through really bad concurrency luck.

I'm afraid I couldn't easily find the upstream URL for posting such
report, both the sourceforge tracker and the ocamlnet3 tracker seemed
outdated, and there is no link to a ocamlnet4 tracker.

Samuel

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

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

-- 
Samuel
  bien sûr que ça convient mieux à tout le monde
  enfin, dans la mesure où tout le monde c'est comme moi
 -+- le consensus, c'est facile -+-
--- ./src/netsys/netsys_c.c.original2016-11-11 23:14:29.0 +
+++ ./src/netsys/netsys_c.c 2016-11-11 23:25:42.0 +
@@ -607,12 +607,32 @@
 CAMLprim value netsys_readlinkat(value dirfd, value path)
 {
 #ifdef HAVE_AT
-  char buffer[PATH_MAX];
-  int len;
-  len = readlinkat(Int_val(dirfd), String_val(path), buffer, sizeof(buffer)-1);
-  if (len == -1) uerror("readlinkat", path);
+  char *buffer;
+  int buflen, len;
+  struct stat sb;
+  value ret;
+  if (lstat(String_val(path), ) == -1) {
+buflen = sb.st_size + 1;
+  }
+  else {
+buflen = 64;
+  }
+  while (1) {
+buffer = malloc(buflen);
+len = readlinkat(Int_val(dirfd), String_val(path), buffer, buflen-1);
+if (len == -1) {
+  free(buffer);
+  uerror("readlinkat", path);
+}
+if (len < buflen-1)
+  break;
+free(buffer);
+buflen *= 2;
+  }
   buffer[len] = '\0';
-  return copy_string(buffer);
+  ret = copy_string(buffer);
+  free(buffer);
+  return ret;
 #else
 invalid_argument("Netsys_posix.readlinkat not available");
 #endif

Bug#821974: comgt: Build arch:all+arch:any but is missing build-{arch,indep} targets

2016-11-11 Thread Christoph Biedl

Andreas "Jimmy" Gredler wrote...

> Thank you for the patch. I will review the package to see if I can
> change it to dh-* in time or if it would be better to upload it with the
> patch only.

Any progress on this? comgt has fallen out of testing in the meantime,
I was glad if it could return in due course.

Christoph


signature.asc
Description: Digital signature

Bug#844014: node-js-yaml

2016-11-11 20:48 GMT+01:00 Ross Gammon :

> Package: node-js-yaml
> Version: 3.6.1+dfsg-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> Node-js-yaml is currently uninstallable in unstable due to a tight
> dependency
> on node-esprima (< 3.0.0), when the current version of node-esprima in
> unstable
> is 3.1.0.
>
> The upstream testsuite passes fine with v3.1.0 of node-esprima, so it
> should be
> fine to just drop the (<3.0.0) dependency.
>
> Regards,
>
> Ross
>
>
You're the node-js-yaml maintainer - do you need help ?

Jérémy

Bug#793355: lmod: diff for NMU version 6.6-0.1

2016-11-11 Thread Ana Guerrero Lopez

Control: tags 793355 + patch
Control: tags 793355 + pending

Dear maintainer,

I've prepared an NMU for lmod (versioned as 6.6-0.1) and uploaded it
to DELAYED/10. This means in 10 days my package will be automatically
uploaded to the archive unless you upload a package yourself or
ask me to remove the package from the delayed queue.

I'm doing the NMU because it would be a pity to release Stretch with an
old version of lmod. Since you're maintaining the package in github,
I forked your repository and you can see easily my changes at:
https://github.com/ana/lmod-deb

Please, take a look, some of my changes are quite intrusive since I
made some changes to have lmod behaving like environment-modules:
- MODULEPATH can be set in a file /etc/lmod/modulespath
- added /etc/profile.d/lmod.sh so /usr/share/lmod/lmod/init/$SHELL
is automatically run.

Best regards,
Ana
diff -Nru lmod-5.8/debian/changelog lmod-6.6/debian/changelog
--- lmod-5.8/debian/changelog	2014-11-04 23:46:05.0 +0100
+++ lmod-6.6/debian/changelog	2016-11-11 23:37:24.0 +0100
@@ -1,3 +1,21 @@
+lmod (6.6-0.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * New upstream release. (Closes: #793355)
+  * Refresh patch change_paths
+  * Update debhelper compatibility 9.
+  * Install README.md, it has been renamed from README.
+  * Add build-depends on procps.
+  * Add build-depends and depends on tcl.
+  * Update Standars-Version to 3.9.8, no changes required.
+  * Update lintian overrides.
+  * Make lmod to behave like environment-modules:
+- Allow to configure the list of modules path at /etc/lmod/modulespath
+- Install /etc/profile.d/lmod.sh and read MODULESPATH from
+  /etc/lmod/modulespath
+
+ -- Ana Beatriz Guerrero Lopez   Fri, 11 Nov 2016 23:37:24 +0100
+
 lmod (5.8-1) unstable; urgency=medium
 
   * Imported Upstream version 5.8 (Closes: #764722)
diff -Nru lmod-5.8/debian/compat lmod-6.6/debian/compat
--- lmod-5.8/debian/compat	2014-05-21 00:44:01.0 +0200
+++ lmod-6.6/debian/compat	2016-11-11 16:56:05.0 +0100
@@ -1 +1 @@
-8
+9
diff -Nru lmod-5.8/debian/control lmod-6.6/debian/control
--- lmod-5.8/debian/control	2014-11-04 23:46:05.0 +0100
+++ lmod-6.6/debian/control	2016-11-11 16:56:06.0 +0100
@@ -2,15 +2,15 @@
 Section: devel
 Priority: optional
 Maintainer: Aaron Zauner 
-Build-Depends: debhelper (>= 8.0.0), autotools-dev, lua5.2, lua-filesystem, lua-posix, lua-term, lua-json
-Standards-Version: 3.9.6
+Build-Depends: debhelper (>= 9), autotools-dev, lua5.2, lua-filesystem, lua-posix, lua-term, lua-json, procps, tcl
+Standards-Version: 3.9.8
 Homepage: https://www.tacc.utexas.edu/tacc-projects/lmod
 Vcs-Git: git://github.com/azet/lmod-deb.git
 Vcs-Browser: https://github.com/azet/lmod-deb
 
 Package: lmod
 Architecture: all
-Depends: ${misc:Depends}, lua5.2, lua-filesystem, lua-posix, lua-term, lua-json
+Depends: ${misc:Depends}, lua5.2, lua-filesystem, lua-posix, lua-term, lua-json, tcl
 Description: Lua based environment modules
  Lmod is a Lua based module system that easily handles the MODULEPATH
  Hierarchical problem. Environment Modules provide a convenient way to
diff -Nru lmod-5.8/debian/dirs lmod-6.6/debian/dirs
--- lmod-5.8/debian/dirs	1970-01-01 01:00:00.0 +0100
+++ lmod-6.6/debian/dirs	2016-11-11 23:27:58.0 +0100
@@ -0,0 +1,3 @@
+etc/profile.d
+etc/lmod
+etc/lmod/modules
diff -Nru lmod-5.8/debian/docs lmod-6.6/debian/docs
--- lmod-5.8/debian/docs	2014-05-21 01:07:05.0 +0200
+++ lmod-6.6/debian/docs	2016-11-11 16:56:05.0 +0100
@@ -1,2 +1,2 @@
-README
+README.md
 README_lua_modulefiles.txt
diff -Nru lmod-5.8/debian/lmod.lintian-overrides lmod-6.6/debian/lmod.lintian-overrides
--- lmod-5.8/debian/lmod.lintian-overrides	2014-06-07 17:52:14.0 +0200
+++ lmod-6.6/debian/lmod.lintian-overrides	2016-11-11 16:57:52.0 +0100
@@ -5,7 +5,6 @@
 lmod: missing-dep-for-interpreter csh => tcsh | csh | c-shell (usr/share/lmod/*/init/cshrc)
 lmod: csh-considered-harmful usr/share/lmod/*/init/tcsh
 lmod: missing-dep-for-interpreter csh => tcsh | csh | c-shell (usr/share/lmod/*/init/tcsh)
-lmod: tclsh-script-but-no-tclsh-dep usr/share/lmod/*/libexec/ModulesVersion.tcl
-lmod: tclsh-script-but-no-tclsh-dep usr/share/lmod/*/libexec/RC2lua.tcl
-lmod: tclsh-script-but-no-tclsh-dep usr/share/lmod/*/libexec/tcl2lua.tcl
 lmod: executable-not-elf-or-script usr/share/lmod/*/init/perl
+lmod: script-not-executable usr/share/lmod/6.6/libexec/ignore_dirs_converter
+lmod: executable-not-elf-or-script usr/share/lmod/6.6/init/r
diff -Nru lmod-5.8/debian/modulespath lmod-6.6/debian/modulespath
--- lmod-5.8/debian/modulespath	1970-01-01 01:00:00.0 +0100
+++ lmod-6.6/debian/modulespath	2016-11-11 23:26:31.0 +0100
@@ -0,0 +1,8 @@
+#
+#  This file defines the initial setup for the module files search path.
+#  Comments must begin with # and continue until the end of the line.
+#  Each line containing a single

Bug#844036: gfortran-6: spits out false warning about COMPLEX(4) to REAL(4) conversion when using a complex parameter

2016-11-11 Thread Francesco Poli (wintermute)

Package: gfortran-6
Version: 6.2.0-10
Severity: normal

Hello,
I think I found a bug in gfortran.

Please consider the following simple program:

  $ cat cpxparam.f 
program main
  
complex iu
parameter (iu=(0,1))
  
complex val1,val2
  
write (*,*) 'iu = ',iu
  
val1 = (+2.0,+3.0)
val2 = (+4.0,-1.0)
  
  c the following should write (2 + j3)/(j*(4 - j) = (14 - j*5)/17
  c that is to say about  (0.8235294 , -0.2941176)
write (*,*) val1/(iu*val2)
  
end

If I try to compile this with the following command line:

  $ gfortran -pedantic -Wall -fimplicit-none -o cpxparam cpxparam.f
  cpxparam.f:4:20:
  
 parameter (iu=(0,1))
  1
  Warning: Non-zero imaginary part discarded in conversion from ‘COMPLEX(4)’ to 
‘REAL(4)’ at (1) [-Wconversion]

I get the above-quoted scary warning about an unintended conversion of
iu to real type!!!
But this conversion seems to never take place (luckily):

  $ ./cpxparam
   iu =  (  0.,  1.)
   ( 0.823529422,-0.294117659)

As you can see, the output is the expected one.

At first I thought a recent gfortran could maybe have some issues
in dealing with the old Fortran77-style syntax.
So, let's try with some more modern style:

  $ cat cpxparam_modern.f 
program main
  
complex,parameter :: iu=(0,1)
  
complex :: val1,val2
  
write (*,*) 'iu = ',iu
  
val1 = (+2.0,+3.0)
val2 = (+4.0,-1.0)
  
  c the following should write (2 + j3)/(j*(4 - j) = (14 - j*5)/17
  c that is to say about  (0.8235294 , -0.2941176)
write (*,*) val1/(iu*val2)
  
end

Same story:

  $ gfortran -pedantic -Wall -fimplicit-none -o cpxparam_modern 
cpxparam_modern.f 
  cpxparam_modern.f:3:30:
  
 complex,parameter :: iu=(0,1)
1
  Warning: Non-zero imaginary part discarded in conversion from ‘COMPLEX(4)’ to 
‘REAL(4)’ at (1) [-Wconversion]
  $ ./cpxparam_modern 
   iu =  (  0.,  1.)
   ( 0.823529422,-0.294117659)

The scary warning is still produced and the executable output is still
correct, despite the compile-time warning.


Curiously, changing the last expression to be evaluated into a
different, but mathematically equivalent one makes the warning go
away:

  $ cat cpxparam2.f 
program main
  
complex iu
parameter (iu=(0,1))
  
complex val1,val2
  
write (*,*) 'iu = ',iu
  
val1 = (+2.0,+3.0)
val2 = (+4.0,-1.0)
  
  c the following should write (2 + j3)/(j*(4 - j) = (14 - j*5)/17
  c that is to say about  (0.8235294 , -0.2941176)
write (*,*) -iu*val1/val2
  
end
  $ gfortran -pedantic -Wall -fimplicit-none -o cpxparam2 cpxparam2.f
  $ ./cpxparam2 
   iu =  (  0.,  1.)
   ( 0.823529422,-0.294117659)

No warning and correct output from the compiled program.


Please investigate this bug and/or forward my bug report upstream,
as appropriate.

Thanks for your time!
Bye.


P.S.: the above-quoted simple programs are probably trivial enough to
not be copyrighted; in case this turns out to be false, I hereby
release them under the terms of the Expat license



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

Kernel: Linux 4.7.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)

Versions of packages gfortran-6 depends on:
ii  gcc-6  6.2.0-10
ii  gcc-6-base 6.2.0-10
ii  libc6  2.24-5
ii  libc6-dev  2.24-5
ii  libgfortran-6-dev  6.2.0-10
ii  libgmp10   2:6.1.1+dfsg-1
ii  libisl15   0.17.1-1
ii  libmpc31.0.3-1
ii  libmpfr4   3.1.5-1
ii  zlib1g 1:1.2.8.dfsg-2+b3

gfortran-6 recommends no packages.

Versions of packages gfortran-6 suggests:
pn  gfortran-6-doc   
pn  gfortran-6-multilib  
pn  libcoarrays-dev  
pn  libgfortran3-dbg 

-- no debconf information

Bug#844037: src:python-django: New upstream release available

2016-11-11 Thread Scott Kitterman

Package: src:python-django
Version: 1.10.1
Severity: wishlist

Django 1.10.3 is out and it would be nice to see it in Debian.

Thanks,

Scott K

Bug#844035: RFS: hylafax/3:6.0.6-7 [RC] -- Flexible client/server fax software

2016-11-11 Thread Joachim Wiedorn

Package: sponsorship-requests
Severity: important

Dear mentors,

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

 * Package name: hylafax
   Version : 3:6.0.6-7
   Upstream Author : Sam Leffler and Silicon Graphics Inc.
 * URL : http://www.hylafax.org
 * License : MIT / HylaFAX variant
   Section : comm

It builds those binary packages:

 hylafax-server - Flexible client/server fax software - server daemons
 hylafax-server-dbg - Debug symbols for the hylafax server
 hylafax-client - Flexible client/server fax software - client utilities
 hylafax-client-dbg - Flexible client/server fax software - client utilities

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

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


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

  dget -x
  https://mentors.debian.net/debian/pool/main/h/hylafax/hylafax_6.0.6-7.dsc

More information about my hylafax package can be found here:

  https://www.joonet.de/sources/hylafax/debian/


Changes since the last upload:

  * debian/control:
- Use newer version of substvar: ${binary:Version}. Closes: #833207
- Add misc depends to debug packages.
- Set section of debug packages to 'debug'.
- Bump to Standards Version 3.9.8 (no changes).
- Set dependency to debhelper version 9.
- Remove Vcs entries (they were no Debian Vcs).
- Update my own email address.
  * Add some upstream patches:
- 821: Check faxanswer "how" parameter length.
- 822: Last line of configuration file may not be terminated by '\n'.
- 823: Set fax status on glare errors.
- 824: serverconfig fixup: JobRetryOther + JobRequeueOther.
- 825: Fix memory corruption when using libtiff v4.0 or newer.
  * Add some more patches:
- 826: Do not send pnmtops dpi value as float value. Closes: #727608
- 827: Make Debian build reproducible. Closes: #790355
  * Remove obsolete debian/NEWS file.


  Regards,
   Joachim Wiedorn



pgpFg5_dNBoWA.pgp
Description: Digitale Signatur von OpenPGP

Bug#844034: pbhoney: incompatible with blasr 5.x

2016-11-11 Thread Afif Elghraoui

Package: pbhoney
Version: 15.8.24+dfsg-1
Severity: serious
Control: forwarded -1 https://sourceforge.net/p/pb-jelly/tickets/5/

As blasr has been updated to 5.x in Unstable/Testing, pbhoney no longer works
due to the interface change there. blasr options in 5.x have been changed from
single dashes to double dashes.

pbhoney test log [1]:
~~~
2016-11-11 21:16:47,957 [INFO] Running /usr/bin/Honey pie 
filtered_subreads.fastq lambda_modified.fasta -o mappingFinal.sam
2016-11-11 21:16:47,957 [INFO] Running Blasr
2016-11-11 21:16:47,965 [ERROR] blasr mapping failed!
2016-11-11 21:16:47,965 [ERROR] RETCODE 1
2016-11-11 21:16:47,965 [ERROR] STDOUTOptions for blasr 
   Basic usage: 'blasr reads.{bam|fasta|bax.h5|fofn} genome.fasta [-options] 
 option Description (default_value).
~~~

1.https://ci.debian.net/data/packages/unstable/amd64/p/pbsuite/2016_211518.autopkgtest.log.gz

Bug#844033: ppp: FTBFS: in6.h:49:8: error: redefinition of 'struct sockaddr_in6'

2016-11-11 Thread Chris Lamb

Source: ppp
Version: 2.4.7-1+3
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

ppp fails to build from source in unstable/amd64:

  […]

  /usr/include/linux/in.h:34:3: error: redeclaration of enumerator 
'IPPROTO_IPIP'
 IPPROTO_IPIP = 4,  /* IPIP tunnels (older KA9Q tunnels use 94) */
 ^
  /usr/include/netinet/in.h:48:5: note: previous definition of 'IPPROTO_IPIP' 
was here
   IPPROTO_IPIP = 4,/* IPIP tunnels (older KA9Q tunnels use 94).  */
   ^~~~
  /usr/include/linux/in.h:36:3: error: redeclaration of enumerator 'IPPROTO_TCP'
 IPPROTO_TCP = 6,  /* Transmission Control Protocol */
 ^
  /usr/include/netinet/in.h:50:5: note: previous definition of 'IPPROTO_TCP' 
was here
   IPPROTO_TCP = 6,/* Transmission Control Protocol.  */
   ^~~
  /usr/include/linux/in.h:38:3: error: redeclaration of enumerator 'IPPROTO_EGP'
 IPPROTO_EGP = 8,  /* Exterior Gateway Protocol  */
 ^
  /usr/include/netinet/in.h:52:5: note: previous definition of 'IPPROTO_EGP' 
was here
   IPPROTO_EGP = 8,/* Exterior Gateway Protocol.  */
   ^~~
  /usr/include/linux/in.h:40:3: error: redeclaration of enumerator 'IPPROTO_PUP'
 IPPROTO_PUP = 12,  /* PUP protocol*/
 ^
  /usr/include/netinet/in.h:54:5: note: previous definition of 'IPPROTO_PUP' 
was here
   IPPROTO_PUP = 12,/* PUP protocol.  */
   ^~~
  /usr/include/linux/in.h:42:3: error: redeclaration of enumerator 'IPPROTO_UDP'
 IPPROTO_UDP = 17,  /* User Datagram Protocol  */
 ^
  /usr/include/netinet/in.h:56:5: note: previous definition of 'IPPROTO_UDP' 
was here
   IPPROTO_UDP = 17,/* User Datagram Protocol.  */
   ^~~
  /usr/include/linux/in.h:44:3: error: redeclaration of enumerator 'IPPROTO_IDP'
 IPPROTO_IDP = 22,  /* XNS IDP protocol   */
 ^
  /usr/include/netinet/in.h:58:5: note: previous definition of 'IPPROTO_IDP' 
was here
   IPPROTO_IDP = 22,/* XNS IDP protocol.  */
   ^~~
  /usr/include/linux/in.h:46:3: error: redeclaration of enumerator 'IPPROTO_TP'
 IPPROTO_TP = 29,  /* SO Transport Protocol Class 4 */
 ^
  /usr/include/netinet/in.h:60:5: note: previous definition of 'IPPROTO_TP' was 
here
   IPPROTO_TP = 29,/* SO Transport Protocol Class 4.  */
   ^~
  /usr/include/linux/in.h:48:3: error: redeclaration of enumerator 
'IPPROTO_DCCP'
 IPPROTO_DCCP = 33,  /* Datagram Congestion Control Protocol */
 ^
  /usr/include/netinet/in.h:62:5: note: previous definition of 'IPPROTO_DCCP' 
was here
   IPPROTO_DCCP = 33,/* Datagram Congestion Control Protocol.  */
   ^~~~
  /usr/include/linux/in.h:50:3: error: redeclaration of enumerator 
'IPPROTO_IPV6'
 IPPROTO_IPV6 = 41,  /* IPv6-in-IPv4 tunnelling  */
 ^
  /usr/include/netinet/in.h:64:5: note: previous definition of 'IPPROTO_IPV6' 
was here
   IPPROTO_IPV6 = 41, /* IPv6 header.  */
   ^~~~
  /usr/include/linux/in.h:52:3: error: redeclaration of enumerator 
'IPPROTO_RSVP'
 IPPROTO_RSVP = 46,  /* RSVP Protocol   */
 ^
  /usr/include/netinet/in.h:66:5: note: previous definition of 'IPPROTO_RSVP' 
was here
   IPPROTO_RSVP = 46,/* Reservation Protocol.  */
   ^~~~
  /usr/include/linux/in.h:54:3: error: redeclaration of enumerator 'IPPROTO_GRE'
 IPPROTO_GRE = 47,  /* Cisco GRE tunnels (rfc 1701,1702) */
 ^
  /usr/include/netinet/in.h:68:5: note: previous definition of 'IPPROTO_GRE' 
was here
   IPPROTO_GRE = 47,/* General Routing Encapsulation.  */
   ^~~
  /usr/include/linux/in.h:56:3: error: redeclaration of enumerator 'IPPROTO_ESP'
 IPPROTO_ESP = 50,  /* Encapsulation Security Payload protocol */
 ^
  /usr/include/netinet/in.h:70:5: note: previous definition of 'IPPROTO_ESP' 
was here
   IPPROTO_ESP = 50,  /* encapsulating security payload.  */
   ^~~
  /usr/include/linux/in.h:58:3: error: redeclaration of enumerator 'IPPROTO_AH'
 IPPROTO_AH = 51,  /* Authentication Header protocol */
 ^
  /usr/include/netinet/in.h:72:5: note: previous definition of 'IPPROTO_AH' was 
here
   IPPROTO_AH = 51,   /* authentication header.  */
   ^~
  /usr/include/linux/in.h:60:3: error: redeclaration of enumerator 'IPPROTO_MTP'
 IPPROTO_MTP = 92,  /* Multicast Transport Protocol  */
 ^
  /usr/include/netinet/in.h:74:5: note: previous definition of 'IPPROTO_MTP' 
was here
   IPPROTO_MTP = 92,/* Multicast Transport Protocol.  */
   ^~~
  /usr/include/linux/in.h:62:3: error: redeclaration of enumerator 
'IPPROTO_BEETPH'
 IPPROTO_BEETPH = 94,  /* IP option pseudo header for BEET */
 ^
  /usr/include/netinet/in.h:76:5: note: previous definition of 'IPPROTO_BEETPH' 
was here
   IPPROTO_BEETPH = 94,   /* IP option

Bug#843965: php-pecl-http: FTBFS: conftest.c:32:27: fatal error: unicode/uidna.h: No such file or directory

2016-11-11 Thread Chris Lamb

Adrian Bunk wrote:

> Some checks in configure are always expected to fail, the most important 
> part of the log is the last configure output before the cat of config.log 
> starts:

Indeed, sorry I selected the wrong bit for the title. :)


Regards,

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

Bug#842642: clang-3.9: memory sanitizer segfaults immediately

2016-11-11 Thread Sylvestre Ledru

I already uploaded 3.8 and 3.9 with the change. Could you report a new bug
for this? Merci

Le 11 nov. 2016 11:14 PM, "Norbert Lange"  a écrit :

> Hello,
>
> seems like the "efficiency sanitizer" needs a patch aswell. Luckily this
> is only for 3.9 as 3.8 doesnt even have this sanitizer.
> Building now, I don`t expect any problems.
>

Bug#844032: Annual ping for Andriy Grytsenko

2016-11-11 Thread Andriy Grytsenko

Package: debian-maintainers
Severity: normal

Annual ping it is.

Thanks!


signature.asc
Description: Digital signature

Bug#844031: [monitoring-plugins] Openssl 1.1 support missing

2016-11-11 Thread Jan Wagner

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Source: monitoring-plugins
Severity: normal

Since OpenSSL 1.1 was announced[1] to be default in unstable,
monitoring-plugins builds against libssl1-1-dev.

Indeed this fails:

[...]
checking openssl/ssl.h usability... yes
checking openssl/ssl.h presence... yes
checking for openssl/ssl.h... yes
checking openssl/x509.h usability... yes
checking openssl/x509.h presence... yes
checking for openssl/x509.h... yes
checking openssl/rsa.h usability... yes
checking openssl/rsa.h presence... yes
checking for openssl/rsa.h... yes
checking openssl/pem.h usability... yes
checking openssl/pem.h presence... yes
checking for openssl/pem.h... yes
checking openssl/crypto.h usability... yes
checking openssl/crypto.h presence... yes
checking for openssl/crypto.h... yes
checking openssl/err.h usability... yes
checking openssl/err.h presence... yes
checking for openssl/err.h... yes
checking for CRYPTO_lock in -lcrypto... no
configure: WARNING: OpenSSL or GnuTLS libs could not be found or were
disabled
[...]
configure: WARNING: unrecognized options: --with-proc-loadavg
--with-apt-get-command: /usr/bin/apt-get
  --with-ping6-command: /bin/ping6 -n -U -w %d -c %d %s
   --with-ping-command: /bin/ping -n -U -w %d -c %d %s
   --with-ipv6: yes
  --with-mysql: /usr/bin/mysql_config
--with-openssl: no
 --with-gnutls: no
   --enable-extra-opts: yes
   --with-perl: /usr/bin/perl
 --enable-perl-modules: no
 --with-cgiurl: /nagios/cgi-bin
   --with-trusted-path:
/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
   --enable-libtap: no
[...]

Same issue has nagios-plugins on Fedora 26[2]. So nothing to grab from
there.

Building against libssl1.0-dev, which was suggested in the
announcement of the openssl switch, results (actual) into:

[...]
checking for PQsetdbLogin in -lpq... no
configure: WARNING: Skipping PostgreSQL plugin (check_pgsql)
configure: WARNING: LIBS="-lcrypt " CPPFLAGS="-Wdate-time
- -D_FORTIFY_SOURCE=2 -I/usr/include"
configure: WARNING: install PostgreSQL libs to compile this plugin
(see REQUIREMENTS).
[...]

This is due postgresql-9.6 beeing linked against libssl1-1-dev and
libpg5 beeing remove when installing libssl1.0-dev. So check_psql can
not be build anymore.
As monitoring-plugins is linked against a couple of libs for it's
plugins, I expect the same for more plugins when their libs are build
against openssl 1.1.

With kind regards, Jan.

[1] https://lists.debian.org/debian-devel-announce/2016/11/msg1.html
[2] https://github.com/nagios-plugins/nagios-plugins/issues/190
- -- 
Never write mail to , you have been warned!
- -BEGIN GEEK CODE BLOCK-
Version: 3.12
GIT d-- s+: a C+++ UL P+ L+++ E--- W+++ N+++ o++ K++ w--- O M+ V-
PS PE Y++
PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h r+++ y
- --END GEEK CODE BLOCK--
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYJkVSAAoJEAxwVXtaBlE+/qsQAKfvDHLzWNs5Dom5P0XTQDip
UKYDfqA4csPr6E/xFIRhrCVTVKg2Ziv7QxW2+/npe8kAN/HqmJho1yHRI1PepVuY
308YPV5dkdfpkGUHuq6Wp0G8MGp0blks7jJuWpyFUEFNaM0+7fVg54zJDzxlfy6x
KwUbQfv0lvw/uhPcBAVVRidrTJW7SkBEDkPBG+RkALUOvKWha7/tamm4ymVTzAeo
8ioQzWW90ANtL5lXOI+YF8UWzeqg7zWA1TDb9W+sHnUa3xJ7IMj363zFTzVQrJ6t
B+nYPQRnOmd+RFKrBtxyOQPe26+v5xbvLDUXCxBlUJN2reQk4CvDUvbNWgGU77Ym
51kJ6DFPUeHFxNpigzSjClV0aKGW5HV55lgwuP0BUM3l0AY/7zqsnYDF316cnxBP
1HbYOEs7/Z6bfaFVyohzcJxhz8dxCV6G2fHeH3DSP+SXzUAHn6vhXzU4LZh78tXM
bWTJn12RCzjcmMBhkTOqgnBnFj5bKu7x2QYjyl3rPhZg7+4LgUU4Hvw9y9+zftX5
qpy8zrjXdtyPCYR7hOE+uxIAnDaabkmX9r5eCm3zP0yYbntIt5wSb9Ig0LbBPrzH
zDKI/tnuMXX1RxnlucXzjwrUvA2M4ULFynwkqtuSl5eDRQVWz5NFX833fbAPaIu5
P9cZRxajMArbXxcpB8Yo
=y2Wo
-END PGP SIGNATURE-

Bug#832391: consensuscore2: Any news?

2016-11-11 Thread Afif Elghraoui

Hi, Andreas,

على الأربعاء  9 تشرين الثاني 2016 ‫03:11، كتب Andreas Tille:
> 
> do you have any news with this issue?
> 

I should have posted an update. Upstream has moved consensuscore2 into a
new source package, unanimity [1]. The packaging issues I was having are
due to building the mixed-language code base. I have not found a good
solution for this with debhelper, and the upstream build system was also
very unconventional in order to handle it (which did not help
debhelper's latching onto it). I think what needs to be done is to just
package unanimity and have consensuscore2 be one of its binary packages.
I'll have to see whether this problem will come up again after that.

regards
Afif

1. https://github.com/PacificBiosciences/unanimity

-- 
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name

Bug#844030: ITP: node-tap-parser -- Test anything protocol stream parser - Node.js module

Package: wnpp
Severity: wishlist
Owner: "Jérémy Lal" 


* Package name: node-tap-parser
  Version : 3.0.3
  Upstream Author : James Halliday  (http://substack.net)
* URL : https://github.com/substack/tap-parser
* License : Expat
  Programming Lang: JavaScript
  Description : Test anything protocol stream parser - Node.js module


This module parses tap-formatted input as a stream of JavaScript
objects.
It is mainly used to extend tap reporters in various test setups.
.
Node.js is an event-based server-side JavaScript engine.

This module is a dependency of latest node-tap / node-tap-mocha-reporter.
It is also a dependency of many other softwares using tap, is well maintained
and popular.

Bug#828247: updated xobj patch

2016-11-11 Thread Alexander Couzens



-- 
Alexander Couzens

mail: lyn...@fe80.eu
jabber: lyn...@fe80.eu
mobile: +4915123277221
gpg: 390D CF78 8BF9 AA50 4F8F  F1E2 C29E 9DA6 A0DF 8604
Index: bip-0.8.9/src/connection.c
===
--- bip-0.8.9.orig/src/connection.c
+++ bip-0.8.9/src/connection.c
@@ -1322,9 +1322,14 @@ static int bip_ssl_verify_callback(int p
 			 err == X509_V_ERR_CERT_HAS_EXPIRED ||
 			 err == X509_V_ERR_SELF_SIGNED_CERT_IN_CHAIN)) {
 
+xobj = X509_OBJECT_new();
+if (!xobj) {
+return 0; /* fail the verification */
+}
+
 		if (X509_STORE_get_by_subject(ctx, X509_LU_X509,
-X509_get_subject_name(err_cert), ) > 0 &&
-!X509_cmp(xobj.data.x509, err_cert)) {
+X509_get_subject_name(err_cert), xobj) > 0 &&
+!X509_cmp(X509_OBJECT_get0_X509(xobj), err_cert)) {
 
 			if (err == X509_V_ERR_CERT_HAS_EXPIRED)
 mylog(LOG_INFO, "Basic mode; Accepting "
@@ -1345,6 +1350,8 @@ static int bip_ssl_verify_callback(int p
 
 			link_add_untrusted(c->user_data, X509_dup(err_cert));
 		}
+
+X509_OBJECT_free(xobj);
 	}
 
 	if (!result) {


pgpDvEn6JlZNg.pgp
Description: OpenPGP digital signature

Bug#842642: clang-3.9: memory sanitizer segfaults immediately

2016-11-11 Thread Norbert Lange

Hello,

seems like the "efficiency sanitizer" needs a patch aswell. Luckily this is
only for 3.9 as 3.8 doesnt even have this sanitizer.
Building now, I don`t expect any problems.


esan-patch_3.9.tar.gz
Description: GNU Zip compressed data

Bug#844029: munipack: B-D on retired libcfitsio3-dev

2016-11-11 Thread Aaron M. Ucko

Source: munipack
Version: 0.5.7-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

munipack declares a build dependency on libcfitsio3-dev, which has
been retired in favor of libcfitsio-dev.  Please update its
Build-Depends field accordingly.

Thanks!

FTR, I'm reporting this bug as a regression because it would affect
any binNMUs.

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

Bug#844028: jsusfx: FTBFS (32-bit): tries to use bad 32-bit x86 assembly

2016-11-11 Thread Aaron M. Ucko

Source: jsusfx
Version: 0.3.1-1
Severity: important
Justification: fails to build from source

Builds of jsusfx for 32-bit architectures have been failing due to the
attempted use of WDL/eel2/glue_x86.h, which turns out not to work even
on *i386 or x32.  64-bit builds all nominally succeed, but those for
non-amd64 processors almost certainly yield broken executables, since
they all (regardless of actual processor type) use glue_x86_64.h,
which uses raw machine code throughout.

I would recommend
* Using glue_x86_64.h only on actual x86_64
* Fixing glue_x86.h and using it only on *i386 and possibly x32.
* Using glue_ppc.h on powerpc, as presumably intended.  Its usage is
  conditional on __ppc__, but at least on Linux, the relevant
  predefined macro would be __powerpc__.  You might need to exclude
  __powerpc64__ and/or _LITTLE_ENDIAN for correct results.
* Actually using the fallback glue_port.h elsewhere.

Could you please take a look?

Thanks!

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

Bug#843881: request uid and gid allocation for libvirt-qemu

2016-11-11 Thread Colin Watson

On Thu, Nov 10, 2016 at 10:10:34AM -0200, Mauricio Faria de Oliveira wrote:
> I'd like to request an uid and gid for the libvirt-qemu user/group.

I have allocated uid/gid 64055 to libvirt-qemu, as per this commit:

  
https://anonscm.debian.org/cgit/users/cjwatson/base-passwd.git/commit/?id=4571f3e3a0a5539633734e474b03fdfdd8b99448

You can go ahead and make use of this immediately in Debian/Ubuntu.

Regards,

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

Bug#844021: libnative-platform-java 0.11-4 is not compatible with programs built with 0.10*

Le 11/11/2016 à 22:38, Emmanuel Bourg a écrit :
> Thank you for the report Vincent. libnative-platform-java/0.11 should
> probably declare that it breaks gradle (<< 3.1~).

The rebuild of gradle 2.13 breaks during tests:
[...]
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':test'.
[...]

Is there an easy way to (temporary) disable tests in gradle build?

I would like to try:
- first: rebuild gradle 2.13
  * without tests
  * with libnative-platform-java/0.11 installed
  * using the gradle version in sid
- then: rebuild gradle 2.13
  * with tests
  * with libnative-platform-java/0.11 installed
  * using the previous gradle build

but I do not know how/what to desactivate the (currently failing)
tests in the first build.

  Regards,
Vincent

> Emmanuel Bourg
> 


-- 
Vincent Danjean   GPG key ID 0xD17897FA vdanj...@debian.org
GPG key fingerprint: 621E 3509 654D D77C 43F5  CA4A F6AE F2AF D178 97FA
Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html
APT repo:  deb http://people.debian.org/~vdanjean/debian unstable main

Bug#839567: rake does not work with jruby

2016-11-11 Thread Christian Hofstaedtler

* Miguel Landaeta  [16 22:46]:
> Resuming the discussion about this bug, I believe the best solution we
> can come up right now is to drop the Provides for ruby-interpreter in
> jruby, given how late we are on the release cycle already.
> 
> However, I'd like to revisit this issue during "buster" development
> cycle.

Sure. I'd suggest coming to the next ruby sprint, whenever that will
be. Discussing the correct dependencies is a lot easier with a
whiteboard.

Cheers,
-- 
christian hofstaedtler

Bug#844027: libroot-io-dev: Missing TXMLEngine.h header file from /usr/include/root/

2016-11-11 Thread Fran Glais

Package: libroot-io-dev
Version: 5.34.19+dfsg-1.2
Severity: important

Dear Maintainer,

While trying to do some development with the ROOT framework, an error kept
telling me that the header file "TXMLEngine.h" was missing from
"/usr/inlude/root/".

I actually managed to overcome this by manually adding this file to the relevant
location, simply copying it from the source. Everything seems to be working.

>From the source package, the relevant file is here:
root-system-5.34.19+dfsg/io/xml/inc/TXMLEngine.h

Regards,
Fran

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

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

Versions of packages libroot-io-dev depends on:
ii  libroot-core-dev  5.34.19+dfsg-1.2
ii  libroot-io5.345.34.19+dfsg-1.2

libroot-io-dev recommends no packages.

libroot-io-dev suggests no packages.

-- no debconf information

Bug#844025: sslscan: static build

2016-11-11 Thread Stefan Pietsch

Package: sslscan
Version: 1.11.5-rbsec-1
Severity: normal


sslscan in Debian unstable does not support SSLv2 and v3.

$ sslscan --version
1.11.5
OpenSSL 1.0.2j  26 Sep 2016
OpenSSL version does not support SSLv2
SSLv2 ciphers will not be detected
OpenSSL version does not support SSLv3
SSLv3 ciphers will not be detected


Build sslscan statically to support legacy protocols for testing.

Bug#844026: Please handle malformed changelogs with more specific exceptions

2016-11-11 Thread Joe Bisch

Package: python-debian
Version: 0.1.29

I am getting a generic IndexError when I try to parse the attached
changelog using the attached reproducer script. I would expect a more
specific exception from python-debian. Dpkg-parsechangelog is able to
identify that the trailer line is badly formatted. (The issue is that
there is only a single space between the email address and the
timestamp).

Using the attached changelog with dpkg-parsechangelog, I get the following
results:

$ dpkg-parsechangelog
dpkg-parsechangelog: warning: debian/changelog(l5): badly formatted trailer 
line
LINE:  -- John Smith  Tue, 27 Sep 2016 14:08:04 -0600
Source: package
Version: 1.0-1
Distribution: codename
Urgency: medium
Maintainer: John Smith 
Timestamp: 1475006884
Date: Tue, 27 Sep 2016 14:08:04 -0600
Changes:
 package (1.0-1) codename; urgency=medium
  .
 * minimal example reproducer

whereas the script I have attached gives:

$ python3 reproducer.py
Traceback (most recent call last):
  File "reproducer.py", line 5, in 
version = debian.changelog.Changelog(file=contents).get_version()
  File "/usr/lib/python3.5/site-packages/debian/changelog.py", line 465, in 
get_version
return self._blocks[0].version
IndexError: list index out of range

-- 
Joe Bisch
HPE Linux, Hewlett Packard Enterprise
package (1.0-1) codename; urgency=medium

  * minimal example reproducer

 -- John Smith  Tue, 27 Sep 2016 14:08:04 -0600
import debian.changelog

with open('changelog') as f:
contents = f.read()
version = debian.changelog.Changelog(file=contents).get_version()

Bug#839567: rake does not work with jruby

2016-11-11 Thread Miguel Landaeta

Hi,

Resuming the discussion about this bug, I believe the best solution we
can come up right now is to drop the Provides for ruby-interpreter in
jruby, given how late we are on the release cycle already.

However, I'd like to revisit this issue during "buster" development
cycle.

jruby provides high compatibility with MRI, so users should be able
to use rake and/or another standard ruby tools with jruby if they want.
We should have in place a simple way to switch interpreters.

I'd like to have jruby 9k packaged for "buster", so this package can
be more relevant and more useful for real world users, so it's likely
this need will surface again in the future.

I plan to upload the most recent upstream release for jruby 1.7.x this
weekend and fix all remaining RC bugs, unless there is an objection or
some unexpected blocker.

Cheers,

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


signature.asc
Description: Digital signature

Bug#843965: php-pecl-http: FTBFS: conftest.c:32:27: fatal error: unicode/uidna.h: No such file or directory

2016-11-11 Thread Adrian Bunk

Control: retitle -1 php-pecl-http must build-depend on zlib1g-dev

On Fri, Nov 11, 2016 at 09:46:01AM +, Chris Lamb wrote:
>...
> php-pecl-http fails to build from source in unstable/amd64:
>...
>   configure:5784: checking for zlib.h
>   configure:5794: result: not found
>   configure:5796: error: could not find zlib.h
>...

This is the actual problem.

Some checks in configure are always expected to fail, the most important 
part of the log is the last configure output before the cat of config.log 
starts:

...
checking unicode/uidna.h usability... no
checking unicode/uidna.h presence... no
checking for unicode/uidna.h... no
checking for icu-config... no
checking for uidna_IDNToASCII... checking for zlib.h... not found
configure: error: could not find zlib.h
"tail -v -n +0 config.log"
==> config.log <==
...

This is likely fallout from the change that libssl-dev no longer 
depending on zlib1g-dev. exposing missing (build)dependencies on
zlib1g-dev elsewhere.

> Regards,

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#844021: libnative-platform-java 0.11-4 is not compatible with programs built with 0.10*

2016-11-11 Thread Emmanuel Bourg

Thank you for the report Vincent. libnative-platform-java/0.11 should
probably declare that it breaks gradle (<< 3.1~).

Emmanuel Bourg

Bug#766316: subdownloader: Fails to download substitles when having an accent in the path "é"

2016-11-11 Thread Emilien Klein

Yes, please do.
(FYI I'm no longer a user of that software)

Le ven. 11 nov. 2016 à 21:55, Sylvestre Ledru  a
écrit :

> If you are OK, can I just upload it now? Thanks
>
> Le 11 nov. 2016 21:32, "Emilien Klein"  a écrit :
>
> Ok, thanks.
>
> Le ven. 11 nov. 2016 20:52, Sylvestre Ledru  a
> écrit :
>
> Hello
>
> Because I am still facing this issue and this is causing this tool to be
> useless, I uploaded as NMU with a 7 days delay.
>
> Sylvestre
> Le 25/07/2016 à 14:14, Sylvestre Ledru a écrit :
> > The attached patch fixed it.
> >
> > https://bugs.launchpad.net/subdownloader/+bug/1289949 provided a partial
> > fix. I fixed the last issue in main.py
> >
> > My test didn't show other regressions but don't hesitate to double check
> > (you should ;)
> >
> > Sylvestre
> >
> >
>
>

Bug#844023: ITP: node-marked-man -- Markdown to man page conversion - Node.js

Package: wnpp
Severity: wishlist
Owner: "Jérémy Lal" 

* Package name: node-marked-man
  Version : 0.1.6
  Upstream Author : Jérémy Lal 
* URL : https://github.com/kapouer/marked-man
* License : Expat
  Programming Lang: JavaScript
  Description : Markdown to man page conversion - Node.js

This module adds groff output support to node-marked.
It provides an easy way to maintain man pages in a markdown
format (with gfm flavor by default).
.
Node.js is an event-based server-side JavaScript engine

Bug#844022: ITP: node-marked-man -- Markdown to man page conversion - Node.js

Package: wnpp
Severity: wishlist
Owner: "Jérémy Lal" 

* Package name: node-marked-man
  Version : 0.1.5
  Upstream Author : Jérémy Lal 
* URL : https://github.com/kapouer/marked-man
* License : Expat
  Programming Lang: JavaScript
  Description : Markdown to man page conversion - Node.js

 This module adds groff output support to node-marked.
 It provides an easy way to maintain man pages in a markdown
 format (with gfm flavor by default).
 .
 Node.js is an event-based server-side JavaScript engine

Bug#844024: coz-profiler: FTBFS on non-Linux

2016-11-11 Thread Aaron M. Ucko

Source: coz-profiler
Version: 0.0.git.20161011T1320-1
Severity: important
Justification: fails to build from source

coz-profiler is specifically geared for Linux, so attempts to build it
for other operating systems (kFreeBSD so far) have been failing badly.
Please set its architecture to linux-any so that non-Linux autobuilders
won't bother trying to cover it.  (If and when it gains support for
other kernels, you're of course welcome to reflect that change.)

Thanks!

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

Bug#843686: htsjdk: FTBFS: java.lang.NoSuchMethodError: net.rubygrapefruit.platform.PosixFiles.stat(Ljava/io/File; )Lnet/rubygrapefruit/platform/PosixFile

Package: src:htsjdk
Followup-For: Bug #843686

  Hi,

  This bug is in fact a bug in the gradle package. I just reported
it in #844020, there is nothing to be done in htsjdk.
  I do not close this bug for now, but I downgraded its severity
to normal and mark it blocked by #844020.

  Regards,
   Vincent


-- System Information:
Debian Release: stretch/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), 
(200, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armel, mipsel

Kernel: Linux 4.8.0-1-amd64 (SMP w/8 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)

Bug#844020: gradle 2.13 in unstable do not work with libnative-platform-java 0.11

Package: gradle
Version: 2.13-4
Severity: serious
Justification: Generate FTBFS in other packages (and in gradle itself)

  Hi,

I'm not an expert of java/gradle but I package several java programs (mainly
within the debian-med team).

I'm working on #843686. It took me time to understand that
net.rubygrapefruit.platform.PosixFiles.stat comes from the
libnative-platform-java package that is pulled by gradle itself.

I suspected that gradle was built with libnative-platform-java 0.10 and
does not work with libnative-platform-java 0.11.

So, I tried to do a local rebuild of gradle itself, so that it "links"
correctly with the new libnative-platform-java version.

=> it fails. So, currently, gradle FTBFS (as htsjdk), and for the same
reason (see the gradle build log in my up-to-date sid chroot at the
end of this report)

On my system, I downgraded libnative-platform-java to 0.10 (thanks to
snapshots.debian.org). With this, htsjdk can be built.


  So, I think that, with the current (2.13-4) gradle version:
- currently gradle FTBFS
- some gradle features do not work (I do not know gradle enought to
  be able to say which ones exactly) 
  that leads to FTBFS of different packages (at least htsjdk #843686
  and gradle itself)
- gradle should have been more strict wrt to libnative-platform-java
  dependency. I.e, instead of
  Depends: libnative-platform-java (>= 0.10)
  it should have had
  Depends: libnative-platform-java (>= 0.10), libnative-platform-java (<< 0.11)
  (or libnative-platform-java should have done a library transition rename
  as the new version is not compatible with the previous one
  => I will also open a bug for libnative-platform-java )


  I saw in the git that you are working to package the 3.1 version
of gradle. However, as this bug has annoying side effects, it would
be great if you can try to upload a new version of gradle compiled
with libnative-platform-java 0.11.
  The difficulty will be that you will need that, as gradle use itself
to compile, you will need libnative-platform-java 0.10 installed
in your environment... :-( I do not know enought of gradle and
libnative-platform-java to know how to workaround this.

  Of course, if gradle 3.1 is to be uploaded very soon, you can
ignore this bug.

  Regards,
Vincent


Part of gradle 2.13-4 build log in current unstable:

[...]
gradle assemble startScripts javadocAll groovydocAll dslHtml samplesDocs -x 
:docs:releaseNotes -x :distributions:assemble --project-prop finalRelease=true 
--offline --stacktrace --gradle-user-home debian/.gradlehome --parallel 
--max-workers=1
Parallel execution is an incubating feature.
:buildSrc:clean UP-TO-DATE
:buildSrc:compileJava UP-TO-DATE
:buildSrc:compileGroovySLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in 
[jar:file:/usr/share/java/gradle-core.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in 
[jar:file:/usr/share/gradle/lib/gradle-core-2.13.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type 
[org.gradle.logging.internal.slf4j.OutputEventListenerBackedLoggerContext]
warning: Implicitly compiled files were not subject to annotation processing.
  Use -proc:none to disable annotation processing or -implicit to specify a 
policy for implicit compilation.
1 warning

:buildSrc:processResources
:buildSrc:classes
:buildSrc:jar
:buildSrc:assemble
:buildSrc:compileTestJava UP-TO-DATE
:buildSrc:compileTestGroovy
:buildSrc:processTestResources
:buildSrc:testClasses
:buildSrc:test FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':test'.
> net.rubygrapefruit.platform.PosixFiles.stat(Ljava/io/File;)Lnet/rubygrapefruit/platform/PosixFile;

* Try:
Run with --info or --debug option to get more log output.

* Exception is:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':test'.
at 
org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:69)
at 
org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:46)
at 
org.gradle.api.internal.tasks.execution.PostExecutionAnalysisTaskExecuter.execute(PostExecutionAnalysisTaskExecuter.java:35)
at 
org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:68)
at 
org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:58)
at 
org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:52)
at 
org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:52)
at 
org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:53)
at

Bug#844019: RM: quake -- ROM; binary packages taken over by src:game-data-packager

2016-11-11 Thread Simon McVittie

Package: ftp.debian.org
Severity: normal

game-data-packager in unstable and testing has taken over the binary
packages that previously came from src:quake; as a result, src:quake has
been removed from testing. Please remove src:quake from unstable.

Thanks,
S

Bug#844021: libnative-platform-java 0.11-4 is not compatible with programs built with 0.10*