Bug#816313: marked as done (dash: executes binary data as a shell script in case of ENOEXEC (Exec format error))

[Debian Bug Tracking System]

Your message dated Thu, 26 Jan 2017 07:18:55 +
with message-id 
and subject line Bug#816313: fixed in dash 0.5.8-2.4
has caused the Debian Bug report #816313,
regarding dash: executes binary data as a shell script in case of ENOEXEC (Exec 
format error)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
816313: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816313
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dash
Version: 0.5.8-2.1
Severity: grave
Justification: causes non-serious data loss

When executing a command that yields an "Exec format error", dash
tries to reexecute the command as a shell script. This gives completely
erratic behavior, with random files created, in particular breaking
Subversion. Data loss may be possible since random files are created.

For instance:

$ file tadd.exe
tadd.exe: PE32 executable (console) Intel 80386, for MS Windows
$ /bin/dash -c tadd.exe
./tadd.exe: 1: ./tadd.exe: MZ��¸@€º´: not found
./tadd.exe: 2: ./tadd.exe: : not found
./tadd.exe: 1: ./tadd.exe: @.bss €: not found
./tadd.exe: 1: ./tadd.exe: .textd*,: not found
./tadd.exe: 3: ./tadd.exe: JPL2@�.idata: not found
./tadd.exe: 3: ./tadd.exe: –u
 : not found
./tadd.exe: 4: ./tadd.exe: ~@0�.CRT4�ˆ@0�.tls: not found
./tadd.exe: 5: ./tadd.exe: @B/81P: not found
./tadd.exe: 13: ./tadd.exe: Syntax error: Missing '}'

and the following file has been created:

-rw-r--r-- 1  0 2016-02-29 20:06:23 \220\324V\366

A strace output shows:

16487 execve("./tadd.exe", ["tadd.exe"], [/* 109 vars */]) = -1 ENOEXEC (Exec 
format error)
16487 execve("/bin/sh", ["/bin/sh", "./tadd.exe"], [/* 109 vars */]) = 0

With bash, I just get:

$ bash -c ./tadd.exe
bash: ./tadd.exe: cannot execute binary file: Exec format error

With ksh93, I just get:

$ ksh93 -c ./tadd.exe
ksh93: ./tadd.exe: cannot execute [Exec format error]

With mksh, I just get:

$ mksh -c ./tadd.exe
mksh: ./tadd.exe: not executable: magic 4D5A

With zsh, I just get:

$ zsh -c ./tadd.exe
zsh:1: exec format error: ./tadd.exe

Only dash has some nasty behavior!

Note: I got this problem after cross-compiling for Windows and running
"make check" but forgetting to add "LOG_COMPILER=wine".

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

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

Versions of packages dash depends on:
ii  debianutils  4.7
ii  dpkg 1.18.4
ii  libc62.21-9

dash recommends no packages.

dash suggests no packages.

-- debconf information:
* dash/sh: true
--- End Message ---
--- Begin Message ---
Source: dash
Source-Version: 0.5.8-2.4

We believe that the bug you reported is fixed in the latest version of
dash, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 816...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adam Borowski  (supplier of updated dash package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 24 Jan 2017 06:16:56 +0100
Source: dash
Binary: dash ash
Architecture: source
Version: 0.5.8-2.4
Distribution: unstable
Urgency: medium
Maintainer: Gerrit Pape 
Changed-By: Adam Borowski 
Description:
 ash- compatibility package for dash
 dash   - POSIX-compliant shell
Closes: 816295 816313 832173
Changes:
 dash (0.5.8-2.4) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Don't execute binary files as scripts. (Closes: #816313)
   * printf '\e' (Closes: #816295)
   * Fix bad permissions on dash.md5sums (Closes: #832173)
Checksums-Sha1:
 b7056c03780023724d5b30fa8cf33ea5dce84c08 1461 dash_0.5.8-2.4.dsc
 d0301097b1302f8d6297812eec3c763ba170a40a 44058 dash_0.5.8-2.4.diff.gz
Checksums-Sha256:
 

Bug#851834: [Pkg-pascal-devel] Bug#851834: mricron FTBFS on armhf: parconvert.s:3121: Error: co-processor offset out of range

[Graham Inggs]

The patch below adds line number information to the generated parconvert.s:

--- a/dcm2nii/dcm2nii.lpi
+++ b/dcm2nii/dcm2nii.lpi
@@ -482,6 +482,7 @@
 
   
   
+  
 
   
   

Because of the additional lines, this changes the assembler messages to:

(9009) Assembling parconvert
parconvert.s: Assembler messages:
parconvert.s:3775: Error: co-processor offset out of range
parconvert.s:3783: Error: co-processor offset out of range
parconvert.s:3880: Error: co-processor offset out of range
parconvert.s:3886: Error: co-processor offset out of range
parconvert.s:3892: Error: co-processor offset out of range
parconvert.s:3895: Error: co-processor offset out of range
parconvert.s:3899: Error: co-processor offset out of range
parconvert.s:3903: Error: co-processor offset out of range
parconvert.s:3918: Error: co-processor offset out of range
parconvert.s:3924: Error: co-processor offset out of range
parconvert.s:3930: Error: co-processor offset out of range
parconvert.s:4813: Error: co-processor offset out of range
parconvert.s:4817: Error: co-processor offset out of range
parconvert.s:4821: Error: co-processor offset out of range
parconvert.s:4825: Error: co-processor offset out of range
parconvert.s:4895: Error: co-processor offset out of range
parconvert.s:4899: Error: co-processor offset out of range
parconvert.pas(1375) Error: (9007) Error while assembling exitcode 1
parconvert.pas(1375) Fatal: (10026) There were 2 errors compiling
module, stopping
Fatal: (1018) Compilation aborted

The first error corresponds to the vstr instruction on line 3775 below:

# [593] lScanResX :=  round(readParFloat);
movr0,r11
blxPARCONVERT$_$READ_PAR2NII$crcDDE5A164_$$_READPARFLOAT$$DOUBLE
blxfpc_round_real
blxfpc_int64_to_double
vmov.f64d1,d0
subr0,r11,#143360
vstrd1,[r0, #-2528]

Which in turn, corresponds to line 593 of parconvert.pas:

  if lUpCaseStr = 'SCANRESOLUTION(XY)' then begin
 lScanResX :=  round(readParFloat);
 lScanResY :=  round(readParFloat);

readParFloat is a nested function returning double, starting on line
461 of parconvert.pas:

function readParFloat:double;//nested
var lStr: string;
begin
  lStr := '';
  result := 1;
...

Bug#851834: [Pkg-pascal-devel] Bug#851834: mricron FTBFS on armhf: parconvert.s:3121: Error: co-processor offset out of range

[Graham Inggs]

I see the same failure with 0.20140804.1~dfsg.1-1.
According to reproducible builds [1], the last successful build on
armhf was on 2016-02-19.

Can we request removal of the armhf binary, so this can at least
migrate before the final freeze?
I have some ideas on how to debug this further.

[1] https://tests.reproducible-builds.org/debian/history/mricron.html

Processed: severity 757343

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 757343 normal
Bug #757343 [src:gamera] gamera: inappropriate use of general exceptions
Severity set to 'normal' from 'wishlist'
> severity 812852 important
Bug #812852 [src:libvigraimpex] libvigraimpex: fail of test_multiarray_chunked 
on ppc64el
Severity set to 'important' from 'normal'
> severity 760396 normal
Bug #760396 [src:pdf2djvu] pdf2djvu: Recent versions compress very badly
Severity set to 'normal' from 'wishlist'
> severity 846599 important
Bug #846599 [pydocstyle] pydocstyle: SyntaxError: (unicode error) 
'unicodeescape' codec can't decode bytes in position 2132-2133
Severity set to 'important' from 'normal'
> severity 834910 serious
Bug #834910 [src:lasagne] lasagne: two tests failing on Python 3.5
Severity set to 'serious' from 'normal'
> severity 844358 important
Bug #844358 [src:pytest-httpbin] pytest-httpbin: FTBFS 
(test_chunked_encoding[https] FAILED)
Severity set to 'important' from 'normal'
> severity 835647 wishlist
Bug #835647 [src:python-brainstorm] python-brainstorm: build path is captured
Severity set to 'wishlist' from 'normal'
> severity 802318 important
Bug #802318 [src:scoop] scoop: test break in reproducible builds CI (fail of 
tests_stopwatch.TestStopWatch)
Severity set to 'important' from 'normal'
> severity 835534 important
Bug #835534 [src:scoop] scoop: FTBFS (test errors: could not start server) on 
armhf in reproducible builds CI
Severity set to 'important' from 'normal'
> severity 835531 important
Bug #835531 [src:theano] theano: FTBFS on amd64 (fail of 
test_csr_correct_output_faster_than_scipy)
Severity set to 'important' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
757343: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757343
760396: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760396
802318: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802318
812852: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812852
834910: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834910
835531: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835531
835534: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835534
835647: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835647
844358: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844358
846599: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846599
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#777525: marked as done (rope: CVE-2014-3539)

[Debian Bug Tracking System]

Your message dated Thu, 26 Jan 2017 05:34:00 +
with message-id 
and subject line Bug#777525: fixed in rope 0.10.3-1
has caused the Debian Bug report #777525,
regarding rope: CVE-2014-3539
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
777525: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777525
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rope
Severity: important
Tags: security

Hi,
please see https://bugzilla.redhat.com/show_bug.cgi?id=1116485 for
details.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: rope
Source-Version: 0.10.3-1

We believe that the bug you reported is fixed in the latest version of
rope, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 777...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Arnaud Fontaine  (supplier of updated rope package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 26 Jan 2017 14:04:41 +0900
Source: rope
Binary: python-rope
Architecture: source all
Version: 0.10.3-1
Distribution: unstable
Urgency: high
Maintainer: Arnaud Fontaine 
Changed-By: Arnaud Fontaine 
Description:
 python-rope - Python refactoring library
Closes: 777525
Changes:
 rope (0.10.3-1) unstable; urgency=high
 .
   [ Arnaud Fontaine ]
   * New upstream release.
   * d/source/options: Ignore .egg-info directory.
   * d/patches/CVE-2014-3539.patch: Mitigations for this CVE. Closes: #777525.
   * d/control:
 + Bump Standards-Version to 3.9.8. No change needed.
 + Bump debhelper compat version to 10 as 7 is deprecated.
 + Add dh-python to Build-Depends (dh_python2 warning).
 .
   [ Ondřej Nový ]
   * d/control: Fixed VCS URL (https).
Checksums-Sha1:
 de592cdaa950c94b486060d51b838b1d37f4ffbd 1975 rope_0.10.3-1.dsc
 8c2e85336ef9c95127cabd05b39227094c6db19a 226123 rope_0.10.3.orig.tar.gz
 eb419b2fd044ad75dbd2ee789fcc041af20de6a9 5076 rope_0.10.3-1.debian.tar.xz
 f9b0cfd33096701337908be492023a8b0a40d8c3 129834 python-rope_0.10.3-1_all.deb
 e77dfa09807b740bde079ea23a8e88ec131873c9 5234 rope_0.10.3-1_amd64.buildinfo
Checksums-Sha256:
 5d19933596f01d207ea2893dd4e8721a5a090572aeb0399fe068903911c081b1 1975 
rope_0.10.3-1.dsc
 eb45bea0abcf31a1a12ff087b990060e64244b835582ebc7642e6f7ea1fd65a2 226123 
rope_0.10.3.orig.tar.gz
 d8afe7195c1a3ed10c8d4a00fd8ca195e52f70fa4e41e7984efd5dce672c8210 5076 
rope_0.10.3-1.debian.tar.xz
 ea2eb6c10fb62f92c5907d644be637afca47266e0dc238a899773bb8d64a192f 129834 
python-rope_0.10.3-1_all.deb
 97d79007c05fb54fce5447d007f7960246e167520a6f5f9e34e7fcf73517c196 5234 
rope_0.10.3-1_amd64.buildinfo
Files:
 ef8ff7a100153d514e83ce9f8c49c16f 1975 devel optional rope_0.10.3-1.dsc
 2fd498b64fe5390946167494eff13642 226123 devel optional rope_0.10.3.orig.tar.gz
 487f0f9f17d3f23dd043d6574632e7d3 5076 devel optional 
rope_0.10.3-1.debian.tar.xz
 aaec57e1cd4de586f1b2ddc1a3515384 129834 devel optional 
python-rope_0.10.3-1_all.deb
 2fdf1550c44b73bc8b603f73f0abc094 5234 devel optional 
rope_0.10.3-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE1xYaYy/QdfbkUZRKNnqrYv0A09kFAliJhOAACgkQNnqrYv0A
09kNSRAAlkSU2LyQM1DIuIrmzsRXJMPPCS23Ee0Q03FeoEYyfkBTQMNdL1mGzpzE
pL+hVBpVZGJ3sv8bJNYiN9SKK/ethnPb2MofuCv/sH5uz9WBW6+P6o68zXWRIuxk
eDbliajhVpOkWlOH67+Pk+bBzCWMPdmb09B9NW5iTDk+OYr8LtwjHnWzvZTDxYtD
+b+7AX4KWT2dwq4RRwPpLqp2TYnmTyv5OZ+WBPcK3hUshgvEYZKwsuD0teIvwwsd
h9eNmYHSJ/LUR+4sQnva2UBzijV9QAmqZjKqBIQ/oALYZfxHl7e8OBWUfWsR0PYU
dAzMTCQpq2kM07EpWKOISZ8ia0xK3H/MtJZINqjAxb1RBavqRrjXrRvgGU15Leyc
7trBLHc+/a89mV1+WVBDUVDJDch0o8tx/JSEXTf+cyQo5njGlrT/T1c3M8clMPpN
7rAg6WmE4oRR23bW2feY+mJvCkYBX2GEbE6Z11lTybvQNGAexBIxROhILGWR5qEG
DTRdwDMEVYdyljfyZ3NTwee1wk1oOovx0g7auskA0RBigyKI8nFoIYCECDP+E8Rq
OYNI1HZxVDzTIoKfH9vHkDb79n379Ps3D4dphjf/KBWmY+YBROSOgxvkW4EdL3wY
O9JVlEmM3nLgvoKQdQjbn3byPAAypaRwrbJKrm1N7R27oytSli4=
=ETQm
-END PGP SIGNATURE End Message ---

Processed: severity of 852654 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 852654 serious
Bug #852654 [src:pbcopper] src:pbcopper: no point to releasing it without 
`unanimity`
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
852654: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852654
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#850951: [pkg-go] Bug#850951: CVE-2016-9962

[Tianon Gravi]

On 11 January 2017 at 07:21, Moritz Muehlenhoff  wrote:
> Please see:
> https://bugzilla.suse.com/show_bug.cgi?id=1012568
> https://github.com/docker/docker/compare/v1.12.5...v1.12.6
> https://github.com/opencontainers/runc/commit/50a19c6ff828c58e5dab13830bd3dacde268afe5

I've been working on backporting this patch to 0.1.1, and I think the
CVE actually doesn't apply to 0.1.1 (the version currently in
sid/stretch).  The file descriptor being closed in this patch isn't
being opened at all in 0.1.1 ("stateDirFD" doesn't exist yet).

https://github.com/opencontainers/runc/pull/886 is the upstream PR
which introduced this file descriptor, and it was not included in a
release until 1.0.0-rc2.

As a consequence, I think this bug should be closed (and probably the
security tracker updated to reflect the fact that this CVE doesn't
apply to our older version of runc).


♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#852653: Grub install failed on encrypted LVM disk

[laalaa]

Dear Maintainer:

Problem solved.  Mark "BOOT" flag in the encrypted disk.  Then grub install 
completed successfully.

Suggest to verify BOOT flag has been marked to allow proceeding to next 
installation stage.

Regards,

Alan

Bug#852653: Grub install failed on encrypted LVM disk

[laalaa]

Package: installation-reports
Version: jessie rc1
Severity: critical
Justification: failed to install grub

Dear Maintainer,

   * What led up to the situation?
Failed installation of grub under KVM system with encrypted LVM disk.

   * What exactly did you do (or not do) that was effective (or ineffective)?
Source:
    netinst iso-cd weekly built on 2017-01-23, downloaded from debian 
website
System:
    Debian Jessie running qemu-kvm 1:2.1+dfsg-12+deb8u6
KVM hardware:
    1 x IDE CDROM (debian-testing netinst iso-cd)
    1 x 8GB virtio disk (vda)
1 x virtio network adapter
QXL display
Partition disks:
    Encrypte vda disk and setup with LVM:
    Encrypted volume (vda1_crypt) - 8.6GB
        #1  8.6GB    K    lvm
        LVM VG vg, LV lvhome - 4.1GB
            #1  4.1GB    K    ext4    /home
        LVM VG vg, LV lvroot - 4.1GB
            #1  4.1GB    K    ext4    /
        LVM VG vg, LV lvswap - 255.9MB
            #1  255.9MB  K    swap    swap
        Virtual disk 1 (vda) - 8.6GB Virtio Block Device
            #1  primary 8.6GB K crypto
GRUB installation:
    Install the GRUB boot loader to the master boot record --> Yes
    Device for boot loader installation: /dev/vda
    Force GRUB installation to the EFI removable media path? Yes

   * What was the outcome of this action?
Error message:
    Unable to install GRUB in /dev/vda
    Executing 'grub-install /dev/vda' failed.
    This is a fatal error.

   * What outcome did you expect instead?
Installation of grub completed.

-- System Information:
Debian Release: stretch/sid
Architecture: amd64

Bug#852631: marked as done (bzr-git: FTBFS: NotImplementedError:

[Debian Bug Tracking System]

Your message dated Thu, 26 Jan 2017 03:04:02 +
with message-id 
and subject line Bug#852631: fixed in bzr-git 0.6.13-2
has caused the Debian Bug report #852631,
regarding bzr-git: FTBFS: NotImplementedError: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852631
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bzr-git
Version: 0.6.13-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

bzr-git fails to build from source in unstable/amd64:

  […]

  if self._determine_file_mode():
File "/usr/lib/python2.7/dist-packages/dulwich/repo.py", line 189, in 
_determine_file_mode
  raise NotImplementedError(self._determine_file_mode)
  NotImplementedError: >>
  
  ==
  ERROR: 
bzrlib.plugins.git.tests.test_push.InterToGitRepositoryTests.test_instance
  --
  Traceback (most recent call last):
  testtools.testresult.real._StringException: Empty attachments:
log
  
  Traceback (most recent call last):
File "«BUILDDIR»/tests/test_push.py", line 45, in setUp
  format=format_registry.make_bzrdir("git"))
File "/usr/lib/python2.7/dist-packages/bzrlib/tests/__init__.py", line 
2756, in make_repository
  made_control = self.make_bzrdir(relpath, format=format)
File "/usr/lib/python2.7/dist-packages/bzrlib/tests/__init__.py", line 
2743, in make_bzrdir
  return format.initialize_on_transport(t)
File "«BUILDDIR»/dir.py", line 231, in initialize_on_transport
  repo = TransportRepo.init(transport, bare=self.bare)
File "«BUILDDIR»/transportgit.py", line 396, in init
  ret._init_files(bare)
File "/usr/lib/python2.7/dist-packages/dulwich/repo.py", line 198, in 
_init_files
  if self._determine_file_mode():
File "/usr/lib/python2.7/dist-packages/dulwich/repo.py", line 189, in 
_determine_file_mode
  raise NotImplementedError(self._determine_file_mode)
  NotImplementedError: >>
  
  ==
  ERROR: 
bzrlib.plugins.git.tests.test_git_remote_helper.OpenLocalDirTests.test_from_dir
  --
  Traceback (most recent call last):
  testtools.testresult.real._StringException: Empty attachments:
log
  
  Traceback (most recent call last):
File "«BUILDDIR»/tests/test_git_remote_helper.py", line 61, in test_from_dir
  self.make_branch_and_tree('.', format='git')
File "/usr/lib/python2.7/dist-packages/bzrlib/tests/__init__.py", line 
3021, in make_branch_and_tree
  b = self.make_branch(relpath, format=format)
File "/usr/lib/python2.7/dist-packages/bzrlib/tests/__init__.py", line 
2711, in make_branch
  repo = self.make_repository(relpath, format=format)
File "/usr/lib/python2.7/dist-packages/bzrlib/tests/__init__.py", line 
2756, in make_repository
  made_control = self.make_bzrdir(relpath, format=format)
File "/usr/lib/python2.7/dist-packages/bzrlib/tests/__init__.py", line 
2743, in make_bzrdir
  return format.initialize_on_transport(t)
File "«BUILDDIR»/dir.py", line 231, in initialize_on_transport
  repo = TransportRepo.init(transport, bare=self.bare)
File "«BUILDDIR»/transportgit.py", line 396, in init
  ret._init_files(bare)
File "/usr/lib/python2.7/dist-packages/dulwich/repo.py", line 198, in 
_init_files
  if self._determine_file_mode():
File "/usr/lib/python2.7/dist-packages/dulwich/repo.py", line 189, in 
_determine_file_mode
  raise NotImplementedError(self._determine_file_mode)
  NotImplementedError: >>
  
  ==
  ERROR: 
bzrlib.plugins.git.tests.test_push.InterToGitRepositoryTests.test_pointless_fetch_refs_old_mapping
  --
  Traceback (most recent call last):
  testtools.testresult.real._StringException: Empty attachments:
log
  
  Traceback (most recent call last):
File "«BUILDDIR»/tests/test_push.py", line 45, in setUp
  format=format_registry.make_bzrdir("git"))
File "/usr/lib/python2.7/dist-packages/bzrlib/tests/__init__.py", line 
2756, in make_repository
  made_control = self.make_bzrdir(relpath, format=format)
File "/usr/lib/python2.7/dist-packages/bzrlib/tests/__init__.py", line 
2743, in make_bzrdir
  return format.initialize_on_transport(t)
File "«BUILDDIR»/dir.py", line 231, in initialize_on_transport
  repo = TransportRepo.init(transport, bare=self.bare)
File "«BUILDDIR»/transportgit.py", line 396, in init
  ret._init_files(bare)
File "/usr/lib/python2.7/dist-packages/dulwich/repo.py", line 198, in 

Bug#852250: [lua-socket] luasocket was not compiled with UNIX sockets support

[Courtney Bane]

On Wed, Jan 25, 2017 at 10:48:43PM +0100, Mathieu Parent wrote:
> Will look at a fix inside lua-socket (preserving both
> compatibilities), but please relax your rules to help find a fix for
> all cases.

I just opened a pull request[1] with upstream that adds backwards
compatibility wrappers. It should be simple to adapt it to the version
currently in Debian.

[1] https://github.com/diegonehab/luasocket/pull/207

Bug#852625: marked as done (unrar-free is useless and should be removed)

[Debian Bug Tracking System]

Your message dated Thu, 26 Jan 2017 01:53:23 +0200
with message-id <20170125235323.odiyuegn5tizdsjx@localhost>
and subject line Re: Bug#852625: unrar-free is useless and should be removed
has caused the Debian Bug report #852625,
regarding unrar-free is useless and should be removed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
852625: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852625
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: unrar-free
Version: 1:0.0.1+cvs20140707-1
Severity: serious
Tags: stretch sid

unrar-free itself supports only ancient versions of the RAR format,
and for any archives created with WinRAR during the past 15 years
all it does is to call unar.
--- End Message ---
--- Begin Message ---
On Thu, Jan 26, 2017 at 04:34:44AM +0800, PaulLiu wrote:
> Exactly,
> 
> But the problem is how many other programs depends on unrar's command line.
> unar doesn't support unrar and that means other programs has to re-program.
> 
> Take an example, Package "unp" doesn't call unar but call unrar.

Good point, I'm closing this bug.

> Yours,
> Paul

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--- End Message ---

Bug#852543: marked as done (Apache doesn't start anymore with sysvinit)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2017 23:49:41 +
with message-id 
and subject line Bug#852543: fixed in apache2 2.4.25-3
has caused the Debian Bug report #852543,
regarding Apache doesn't start anymore with sysvinit
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
852543: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852543
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: apache2
Version: 2.4.25-2
Severity: important

Dear Maintainer,

I’m using sysvinit as my init system.

Since the update to version 2.4.25-2 apache isn’t starting anymore 
because apache2ctl tries to invoke systemctl which will fail of course.


It seems that the fix for 839227 creates this problem.

If I comment the systemd checks in apache2ctl I can start my apache 
again.


Many greetings,

Stephan

-- Package-specific info:

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

Kernel: Linux 4.9.5 (SMP w/8 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: sysvinit (via /sbin/init)

Versions of packages apache2 depends on:
ii  apache2-bin  2.4.25-2
ii  apache2-data 2.4.25-2
ii  apache2-utils2.4.25-2
ii  dpkg 1.18.18
ii  init-system-helpers  1.46
ii  lsb-base 9.20161125
ii  mime-support 3.60
ii  perl 5.24.1~rc4-1
ii  procps   2:3.3.12-3

Versions of packages apache2 recommends:
ii  ssl-cert  1.0.38

Versions of packages apache2 suggests:
ii  elinks [www-browser] 0.12~pre6-12
ii  epiphany-browser [www-browser]   3.22.4-1
ii  firefox-esr [www-browser]45.6.0esr-1
ii  konqueror [www-browser]  4:16.08.3-1
ii  links [www-browser]  2.14-2
ii  lynx [www-browser]   2.8.9dev11-1
ii  opera-stable [www-browser]   42.0.2393.351
ii  w3m [www-browser]0.5.3-34

Versions of packages apache2-bin depends on:
ii  libapr1  1.5.2-5
ii  libaprutil1  1.5.4-3
ii  libaprutil1-dbd-mysql1.5.4-3
ii  libaprutil1-dbd-pgsql1.5.4-3
ii  libaprutil1-dbd-sqlite3  1.5.4-3
ii  libaprutil1-ldap 1.5.4-3
ii  libc62.24-8
ii  libldap-2.4-22.4.44+dfsg-3
ii  liblua5.2-0  5.2.4-1.1+b1
ii  libnghttp2-141.17.0-1
ii  libpcre3 2:8.39-2
ii  libssl1.0.2  1.0.2j-5
ii  libxml2  2.9.4+dfsg1-2.1
ii  zlib1g   1:1.2.8.dfsg-4

Versions of packages apache2-bin suggests:
ii  elinks [www-browser] 0.12~pre6-12
ii  epiphany-browser [www-browser]   3.22.4-1
ii  firefox-esr [www-browser]45.6.0esr-1
ii  konqueror [www-browser]  4:16.08.3-1
ii  links [www-browser]  2.14-2
ii  lynx [www-browser]   2.8.9dev11-1
ii  opera-stable [www-browser]   42.0.2393.351
ii  w3m [www-browser]0.5.3-34

Versions of packages apache2 is related to:
ii  apache2  2.4.25-2
ii  apache2-bin  2.4.25-2

-- Configuration Files:
/etc/apache2/mods-available/ssl.conf changed [not included]
/etc/apache2/sites-available/000-default.conf changed [not included]
/etc/apache2/sites-available/default-ssl.conf changed [not included]

-- no debconf information

--
| Public Keys: http://fsing.rootsland.net/~stse/keys.html |


smime.p7s
Description: S/MIME cryptographic signature
--- End Message ---
--- Begin Message ---
Source: apache2
Source-Version: 2.4.25-3

We believe that the bug you reported is fixed in the latest version of
apache2, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 852...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stefan Fritsch  (supplier of updated apache2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive

Bug#794466: VIrtualBox future in Debian

[Jeremy Bicha]

Sorry for the long post, but it does give a walkthrough of how this is
working now in Stretch…


I installed Debian Stretch today using the January 23 weekly
netinstall image. I installed to a VirtualBox guest (the host is
Ubuntu 17.04 Alpha). The install went well except for two issues.

1. I chose to install the GNOME desktop. tasksel had some kind of
error near the end of downloading packages. Maybe some transient
network error. When I re-ran the task, it suggested I install some
virtualbox-ose-something package. The install completed successfully.

2. When I rebooted after install, gdm did not start and my console was
flickering really bad. Along with the console flickering, I could not
reliably enter my password since keypresses were getting dropped. I
tried booting into recovery mode but since I did not set a root
password (I prefer to use sudo), Debian gave me an error about the
root account being locked and after I pressed Enter as prompted, it
continued a normal boot. After about 5 minutes, the flickering
stopped. I guess this is systemd eagerly retrying a failed service
until it reaches its timeout.

journalctl -xb revealed that gdm ""could not find drm kms device". I
couldn't find anything useful by searching for that message on Google.
I then checked to see whether the VirtualBox guest utils were
installed. They weren't. So I had to enable unstable in my apt
sources, then
sudo apt -t unstable install virtualbox-guest-utils virtualbox-guest-x11
sudo reboot

gdm works great now.

Suggestions
=
3. Something needs to be done about whatever in the installer suggests
installing the virtualbox-ose package. Since I clicked OK, I thought
it *did* install something useful for VirtualBox but I don't think it
did.

4. I have not had the #2 problem with other distros. Ubuntu includes
some minimal VirtualBox-compatible driver as part of its default
kernel. Could Debian do the same so that Debian will actually run on
VirtualBox?

5. As far as the drivers go, if they aren't in a Debian release, then
once someone actually gets Debian running, I guess they'll either just
keep whatever drivers they installed the first time. Or maybe they'll
use VirtualBox's guest additions iso to install the drivers. Neither
way offers automatic update of drivers. I feel this situation is worse
from a security perspective than having a Debian package that is at
least updated on major new Debian releases.

Why can't the Security Team treat VirtualBox like how it's been
treating WebKit1? Still have it in the archives but with a prominent
notice that Debian does not provide security updates.

6. Assuming that VirtualBox won't be in the next stable Debian
release, I guess we need a page like mozilla.debian.net for it?

Thanks,
Jeremy Bicha

Bug#852645: dafny: FTBFS

[Santiago Vila]

Package: src:dafny
Version: 1.9.7-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with cli
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
cp -a /usr/lib/boogie/* Binaries
mkdir -p Source/Dafny/bin/Checked
cp -a /usr/lib/boogie/* Source/Dafny/bin/Checked
xbuild Source/Dafny.sln
XBuild Engine Version 14.0
Mono, Version 4.6.2.0
Copyright (C) 2005-2013 Various Mono authors

[... snipped ...]

Resolver.cs(2197,57): error CS0246: The type or namespace name `IToken' 
could not be found. Are you missing an assembly reference?
Resolver.cs(2871,44): error CS0246: The type or namespace name `IToken' 
could not be found. Are you missing an assembly reference?
Resolver.cs(3394,41): error CS0246: The type or namespace name `IToken' 
could not be found. Are you missing an assembly reference?
Resolver.cs(4399,82): error CS0246: The type or namespace name `IToken' 
could not be found. Are you missing an assembly reference?
Resolver.cs(4932,29): error CS0246: The type or namespace name `IToken' 
could not be found. Are you missing an assembly reference?
Resolver.cs(4940,29): error CS0246: The type or namespace name `IToken' 
could not be found. Are you missing an assembly reference?
Resolver.cs(4968,49): error CS0246: The type or namespace name `IToken' 
could not be found. Are you missing an assembly reference?
Resolver.cs(5114,37): error CS0246: The type or namespace name `IToken' 
could not be found. Are you missing an assembly reference?
Resolver.cs(5598,28): error CS0246: The type or namespace name `IToken' 
could not be found. Are you missing an assembly reference?
Resolver.cs(6255,45): error CS0246: The type or namespace name `Boogie' 
could not be found. Are you missing an assembly reference?
Resolver.cs(7070,38): error CS0246: The type or namespace name `IToken' 
could not be found. Are you missing an assembly reference?
Resolver.cs(7197,23): error CS0246: The type or namespace name `IToken' 
could not be found. Are you missing an assembly reference?
Resolver.cs(7300,30): error CS0246: The type or namespace name `IToken' 
could not be found. Are you missing an assembly reference?
Resolver.cs(7394,56): error CS0246: The type or namespace name `IToken' 
could not be found. Are you missing an assembly reference?
Resolver.cs(7525,47): error CS0246: The type or namespace name `IToken' 
could not be found. Are you missing an assembly reference?
Resolver.cs(7536,51): error CS0246: The type or namespace name `IToken' 
could not be found. Are you missing an assembly reference?
Resolver.cs(8316,38): error CS0246: The type or namespace name `IToken' 
could not be found. Are you missing an assembly reference?
Resolver.cs(8316,95): error CS0246: The type or namespace name `IToken' 
could not be found. Are you missing an assembly reference?
Resolver.cs(8552,40): error CS0246: The type or namespace name `Boogie' 
could not be found. Are you missing an assembly reference?
Resolver.cs(9085,59): error CS0246: The type or namespace name `IToken' 
could not be found. Are you missing an assembly reference?
Resolver.cs(9379,35): error CS0246: The type or namespace name `IToken' 
could not be found. Are you missing an assembly reference?
Resolver.cs(845,29): error CS0246: The type or namespace name `IToken' 
could not be found. Are you missing an assembly reference?
Resolver.cs(853,35): error CS0246: The type or namespace name `IToken' 
could not be found. Are you missing an assembly reference?
Resolver.cs(2250,16): error CS0246: The type or namespace name `IToken' 
could not be found. Are you missing an assembly reference?
Resolver.cs(2253,53): error CS0246: The type or namespace name `IToken' 
could not be found. Are you missing an assembly reference?
Resolver.cs(2543,34): error CS0246: The type or namespace name `IToken' 
could not be found. Are you missing an assembly reference?
Resolver.cs(3311,43): error CS0246: The type or namespace name `IToken' 
could not be found. Are you missing an assembly reference?
Resolver.cs(3435,28): error CS0246: The type or namespace name `IToken' 
could not be found. Are you missing an assembly reference?
Resolver.cs(9448,23): error CS0246: The type or namespace name `IToken' 
could not be found. Are you missing an assembly reference?
Resolver.cs(9460,36): error CS0246: The type or namespace name `IToken' 
could not be found. Are you missing an assembly reference?
Rewriter.cs(34,31): error CS0246: The type or namespace name `Boogie' 
could not be found. Are 

Bug#852643: libbfio FTBFS on armel/armhf/mips*: bfio_test_handle.c:803 result (1) != -1

[Adrian Bunk]

Source: libbfio
Version: 20170123-1
Severity: serious

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

...
make  check-TESTS
make[3]: Entering directory '/«PKGBUILDDIR»/tests'
make[4]: Entering directory '/«PKGBUILDDIR»/tests'
FAIL: test_library.sh
PASS: test_write_functions.sh

   libbfio 20170123: tests/test-suite.log


# TOTAL: 2
# PASS:  1
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: test_library.sh
=

Testing: error  (PASS)
Testing: support  (PASS)
bfio_test_handle.c:803 result (1) != -1
Unable to run test: libbfio_handle_initialize
Testing: handle with input: input/raw/test.raw (FAIL)
FAIL test_library.sh (exit status: 1)


Testsuite summary for libbfio 20170123

# TOTAL: 2
# PASS:  1
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See tests/test-suite.log
Please report to joachim.m...@gmail.com

Makefile:1014: recipe for target 'test-suite.log' failed
make[4]: *** [test-suite.log] Error 1

Bug#850983: marked as done (gvpe: FTBFS: configure: error: OpenSSL depends on libz.)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2017 22:49:05 +
with message-id 
and subject line Bug#850983: fixed in gvpe 2.25-3.1
has caused the Debian Bug report #850983,
regarding gvpe: FTBFS: configure: error: OpenSSL depends on libz.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
850983: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850983
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gvpe
Version: 2.25-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> checking for SSLeay_add_all_algorithms... no
> checking for dlopen... no
> checking for dlopen in -ldl... yes
> checking for inflate... no
> checking for inflate in -lz... no
> configure: error: OpenSSL depends on libz.
>   "tail -v -n +0 config.log"

The full build log is available from:
   http://aws-logs.debian.net/2017/01/11/gvpe_2.25-3_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: gvpe
Source-Version: 2.25-3.1

We believe that the bug you reported is fixed in the latest version of
gvpe, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 850...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated gvpe package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 26 Jan 2017 00:18:25 +0200
Source: gvpe
Binary: gvpe
Architecture: source
Version: 2.25-3.1
Distribution: unstable
Urgency: medium
Maintainer: TANIGUCHI Takaki 
Changed-By: Adrian Bunk 
Description:
 gvpe   - creates a virtual ethernet between multiple endpoints
Closes: 850983
Changes:
 gvpe (2.25-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build-depend on zlib1g-dev. (Closes: #850983)
Checksums-Sha1:
 92ff5b7ea6d94be7e4761df62dedc990df630c17 1889 gvpe_2.25-3.1.dsc
 2cf1504a8c2cdd94b0cdfd6086a21a5bfc0a938d 16612 gvpe_2.25-3.1.debian.tar.xz
Checksums-Sha256:
 00c49473e194984d0fcf3c8e96ba6c7970bcc034f8b3c53245deaff63a1cced4 1889 
gvpe_2.25-3.1.dsc
 684d935ed747d6ad087a40bf5e377c728759d7f3d71e0d774d09938ce7a0aea8 16612 
gvpe_2.25-3.1.debian.tar.xz
Files:
 3d5f8beb09749d0240bbc888138a6fbc 1889 net extra gvpe_2.25-3.1.dsc
 a1915641522a9a138bb1bc5fcacf1539 16612 net extra gvpe_2.25-3.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAliJJbUACgkQiNJCh6LY
mLHnxxAAsTRYDunVxFjoTGf6xdb42q7nhGB6d76BCVX2XpNKPZFTVfrw/IUdsf21
M6EpLP7OFIMtyt9kDjVbXeekiCVFEOAf6jT57+/l6Qo4tR+cLF3L1daGssCSuPKf
4CaO7tzw+GqwVLimtOz/8bJ2nKn8kZWNq6FHZO0URe+U37pkwVFs6niZAeJ62E9z
pn+/IWQwIUgwX8TXsa4AmhyIyZMByJcGYmoj2UFyhmh9niwteociXYHF0ZDm28yM
luOHBcGFW5b+XJ4dcoJ7US7j7ddJSMCcePZyz3XnO/SBCvz3dWp1VyFnxO2muNju
Kiz9gH/CDt8v9yijK+9vvclsWo1hoBETfOVv07QNKG98OpPv4VNwTILKU6Wvkl0L
DVaRX30ZNd6+sCUowqsh0CnT+kxfuei3wr5Qrj1AUh+EQyik5K1TLsLCwhTWVhjq
H8cbN7++7taRzDix1Dth+blNIC71IZok1Qq1YZosmBOET6wCOpIB9UBpdpjjY5EK
fmrzMahvAOrC+UtDnl+erKH81JYe/MBYE8LPskAidmPSUxDqoo0WMjqfzJ38hNU7
v+eYRaQrXxPS8ov2JtAxufwkY26REzG81pOyziN0Rl2dqf12/N3VxZd0V2hrxsMS
xK4AMOsNj/I7ObB/Sdf0dLm55pos5gfCiAoH8NnQ7C+Us8SIFpA=
=KUAr
-END PGP SIGNATURE End Message ---

Bug#839300: marked as done (gnustep-make: FTBFS: dh_install: missing files, aborting)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2017 22:40:02 +
with message-id 
and subject line Bug#838278: fixed in gnustep-make 2.6.8-2.1
has caused the Debian Bug report #838278,
regarding gnustep-make: FTBFS: dh_install: missing files, aborting
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
838278: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838278
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnustep-make
Version: 2.6.8-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160930 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>/build-gnustep-make'
> Creating system tools directory: /<>/debian/tmp/usr/bin
> Creating makefile directories in: 
> /<>/debian/tmp/usr/share/GNUstep/Makefiles
> Installing GNUstep configuration file in 
> /<>/debian/tmp/etc/GNUstep/GNUstep.conf
> Installing gnustep-make support software
> Installing makefiles
> Installing Test Framework scripts
> Installing Test Framework support files
> Installing (and compressing) manpages
> make[1]: Leaving directory '/<>/build-gnustep-make'
>dh_install -O--builddirectory=build-gnustep-make
> dh_install: Cannot find (any matches for) "Documentation/gnustep-make.pdf" 
> (tried in "." and "debian/tmp")
> dh_install: gnustep-make-doc missing files: Documentation/gnustep-make.pdf
> dh_install: missing files, aborting
> debian/rules:24: recipe for target 'binary' failed
> make: *** [binary] Error 255

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

The full build log is available from:
   http://aws-logs.debian.net/2016/09/30/gnustep-make_2.6.8-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: gnustep-make
Source-Version: 2.6.8-2.1

We believe that the bug you reported is fixed in the latest version of
gnustep-make, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 838...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated gnustep-make package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 25 Jan 2017 23:53:44 +0200
Source: gnustep-make
Binary: gnustep-common gnustep-make gnustep-make-doc
Architecture: source
Version: 2.6.8-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNUstep maintainers 

Changed-By: Adrian Bunk 
Description:
 gnustep-common - Common files for the core GNUstep environment
 gnustep-make - GNUstep build system
 gnustep-make-doc - Documentation for GNUstep Make
Closes: 838278
Changes:
 gnustep-make (2.6.8-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Replace @setcontentsaftertitlepage with @contents.
 (Closes: #838278)
Checksums-Sha1:
 21286ee0104aab27d5e21a4eadad4c9a69f15eb1 2284 gnustep-make_2.6.8-2.1.dsc
 65b7ca7c4ae55355b1c29286ad6954c2902d56ca 107180 
gnustep-make_2.6.8-2.1.debian.tar.xz
Checksums-Sha256:
 57ab37e42e5e1adb89f9e6380e6ccaba27cdfd71761be388871f31a933983a8f 2284 
gnustep-make_2.6.8-2.1.dsc
 9d7d82c8843049963f88fe86550b71683fd0f10bcf0fb2bc28f2f8627374e409 107180 
gnustep-make_2.6.8-2.1.debian.tar.xz
Files:
 3c9d8838106bb8a62161ba3cf75c8747 2284 gnustep optional 
gnustep-make_2.6.8-2.1.dsc
 3f95fb1ba571485dea71dacfa4c81016 

Bug#838278: marked as done (gnustep-make: FTBFS in testing (@setcontentsaftertitlepage no longer works))

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2017 22:40:02 +
with message-id 
and subject line Bug#838278: fixed in gnustep-make 2.6.8-2.1
has caused the Debian Bug report #838278,
regarding gnustep-make: FTBFS in testing (@setcontentsaftertitlepage no longer 
works)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
838278: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838278
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gnustep-make
Version: 2.6.8-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:


[...]
./gnustep-howto.texi:8: @setcontentsaftertitlepage has been removed as a Texinf
o command; move your @contents command if you want the contents after the title
 page..
@setcontentsaftertitlepage ...ter the title page.}
  
l.8 @setcontentsaftertitlepage
  
? 
./gnustep-howto.texi:8: Emergency stop.
@setcontentsaftertitlepage ...ter the title page.}
  
l.8 @setcontentsaftertitlepage
  
./gnustep-howto.texi:8:  ==> Fatal error occurred, no output PDF file produced!
Transcript written on gnustep-howto.log.


The relevant part of the build is included.

In addition to this, the build continues after this TeX failure, and
the target which fails is really binary-indep. That should not really
happen. If the build fails, it's the build-indep target the one that
should fail.

Thanks.
--- End Message ---
--- Begin Message ---
Source: gnustep-make
Source-Version: 2.6.8-2.1

We believe that the bug you reported is fixed in the latest version of
gnustep-make, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 838...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated gnustep-make package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 25 Jan 2017 23:53:44 +0200
Source: gnustep-make
Binary: gnustep-common gnustep-make gnustep-make-doc
Architecture: source
Version: 2.6.8-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNUstep maintainers 

Changed-By: Adrian Bunk 
Description:
 gnustep-common - Common files for the core GNUstep environment
 gnustep-make - GNUstep build system
 gnustep-make-doc - Documentation for GNUstep Make
Closes: 838278
Changes:
 gnustep-make (2.6.8-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Replace @setcontentsaftertitlepage with @contents.
 (Closes: #838278)
Checksums-Sha1:
 21286ee0104aab27d5e21a4eadad4c9a69f15eb1 2284 gnustep-make_2.6.8-2.1.dsc
 65b7ca7c4ae55355b1c29286ad6954c2902d56ca 107180 
gnustep-make_2.6.8-2.1.debian.tar.xz
Checksums-Sha256:
 57ab37e42e5e1adb89f9e6380e6ccaba27cdfd71761be388871f31a933983a8f 2284 
gnustep-make_2.6.8-2.1.dsc
 9d7d82c8843049963f88fe86550b71683fd0f10bcf0fb2bc28f2f8627374e409 107180 
gnustep-make_2.6.8-2.1.debian.tar.xz
Files:
 3c9d8838106bb8a62161ba3cf75c8747 2284 gnustep optional 
gnustep-make_2.6.8-2.1.dsc
 3f95fb1ba571485dea71dacfa4c81016 107180 gnustep optional 
gnustep-make_2.6.8-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAliJIfkACgkQiNJCh6LY
mLF04xAAt2RlsUVMVqRCoqNynzD6nQuh2qIVenKR7P+yF23jVcJ45Qa05gLjxTWB
598PTriXt//048s6BexSiXg903ic9Zg+VGaWHFKz7XQ0MnBfXnDK7OG+XyrUIhDh
DpURB616lrWA1meSEoeu4lsF/tcRGrJIf9q8HcVcf/c9UvWGyR9cP7PgDX97oDC0
iotYLvk+fvi9kMmiftj+mNvlm5/oH8RznQgV59Mr4Fu8lBMAAHRDk3/35hrQYwm3
DneoEtRSfkFukYUntu4SIi/gcj3suVJ/z7fM+eSMWo5EvamA0WpYa38x1WtuwzeK
jQ2xZzPUKK3THdkjzFAw+T86zBmsxvbvK3aaoZcyOs6QhZmU0yQOVI11tu2Zh08y
8FjRP2gVyu8DyJhaMYrB+Ch6r+ei/zOzE9+pB8Sh6LY4HppxEjLtIff5L9YIpzgk
t9vKSPwIHjexoDGZKMo/7C7TwWeBaNMLcdegrrpsuOP/HLDMhB6JQQfnkbxjaCYK

Bug#834063: marked as done (gosa: GOsa setup complains about missing php mysql module even if php-mysql is installed)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2017 21:49:03 +
with message-id 
and subject line Bug#834063: fixed in gosa 2.7.4+reloaded2-13
has caused the Debian Bug report #834063,
regarding gosa: GOsa setup complains about missing php mysql module even if 
php-mysql is installed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
834063: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834063
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gosa
Version: 2.7.4+reloaded2-12
Severity: grave
Justification: renders package unusable

Hi,

I tried to update the GOsa configuration in Debian-LAN and started the web 
interface 
without '/etc/gosa.conf' in place.  The installation check complains about 
missing 
mysql support and recommends to install and activate the MySQL PHP module.
However, after installing all suspicious packages, for example php-mysql, the 
issue 
remains and the setup process can't be continued and finished.

So for users that doo not have a useable configuration available, GOsa seems to 
be 
useless.  (Therefore severity grave, feel free to adjust).  With the Debian-EDU 
configuration in place, things seem to work fine. 

Best regards,

Andi  
  


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

Kernel: Linux 4.6.0-1-amd64 (SMP w/1 CPU core)
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 gosa depends on:
ii  apache2 [httpd]2.4.23-2
ii  exim4  4.87-3
ii  exim4-daemon-heavy [mail-transport-agent]  4.87-3
ii  fonts-liberation   1.07.4-1
ii  gettext0.19.8.1-1
ii  imagemagick8:6.8.9.9-7.2
ii  libcrypt-smbhash-perl  0.12-4
ii  libjs-scriptaculous1.9.0-2
ii  php1:7.0+42
ii  php-curl   1:7.0+42
ii  php-gd 1:7.0+42
ii  php-imap   1:7.0+42
ii  php-ldap   1:7.0+42
ii  php-mbstring   1:7.0+42
ii  php-mcrypt 1:7.0+42
ii  php-mysql  1:7.0+42
ii  php-recode 1:7.0+42
ii  php-xml1:7.0+42
ii  php7.0 [php]   7.0.9-1
ii  php7.0-cli [php-cli]   7.0.9-1
ii  php7.0-curl [php-curl] 7.0.9-1
ii  php7.0-gd [php-gd] 7.0.9-1
ii  php7.0-imap [php-imap] 7.0.9-1
ii  php7.0-ldap [php-ldap] 7.0.9-1
ii  php7.0-mbstring [php-mbstring] 7.0.9-1
ii  php7.0-mcrypt [php-mcrypt] 7.0.9-1
ii  php7.0-mysql [php-mysqlnd] 7.0.9-1
ii  php7.0-recode [php-recode] 7.0.9-1
ii  php7.0-xml [php-xml]   7.0.9-1
ii  smarty-gettext 1.3.0-1
ii  smarty33.1.21-1.1

gosa recommends no packages.

Versions of packages gosa suggests:
pn  cyrus21-imapd   
ii  gosa-schema 2.7.4+reloaded2-12
pn  gosa-si-server  
pn  php-apc 
pn  php-fpdf
pn  php-suhosin 
pn  postfix-ldap
ii  slapd   2.4.42+dfsg-2+b2

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gosa
Source-Version: 2.7.4+reloaded2-13

We believe that the bug you reported is fixed in the latest version of
gosa, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 834...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated gosa package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 25 Jan 2017 22:11:04 +0100
Source: gosa
Binary: gosa gosa-dev gosa-desktop 

Bug#852250: [lua-socket] luasocket was not compiled with UNIX sockets support

[Mathieu Parent]

2017-01-25 22:15 GMT+01:00 Michael Meskes :
> Control: reassign -1 lua-socket
>
> I don't think this is the way to go. There is no grave bug in prosody-modules,
> it's lua-socket that changed its API during freeze. The way I understand our
> freeze policy this is a no-go, but feel free to check with the release team.

The way you want will make prosody-modules break when someone start to
use lua-socket from stretch-backports.

The unix socket API is not stable nor documented yet [1], being tied
to an API that we know will change on buster is not very solid either.

As for the freeze definition, the updated lua-socket was uploaded
during soft freeze. I agree that this could be seen as a "transition"
as the API was changed.

Will look at a fix inside lua-socket (preserving both
compatibilities), but please relax your rules to help find a fix for
all cases.

[1]: https://github.com/diegonehab/luasocket/pull/199#issuecomment-275220892

Regards
-- 
Mathieu

Bug#796609: fcoe-utils: Has init script in runlevel S but no matching service file

[Jacob Luna Lundberg]

Hi Felipe,

On Wed, Jan 25, 2017 at 03:00:29PM -0300, Felipe Sateler wrote:
> > It is plenty usable, just not if you are using systemd.  Yes, I am aware
> > policy at this point requires systemd support.
> 
> OK, sorry. The impression I had from your earlier message is that it
> didn't work[1].

Ahh, I see.  No, the package provides the utilities necessary to mount 
FCoE volumes, it just does not work when you try to mount them 
automatically at boot time.  I would be curious how systemd accomplishes 
the necessary ordering if that is working with the systemd units.  If 
so, when I have some time I will have to try and understand what systemd 
is doing.

As far as I can tell this problem is not well solved, at least in 
sysvinit.  NFS has a special arrangement.  FCoE and iSCSI can't work as 
far as I can tell because the network must come up in order to discover 
volumes, but aside from NFS, volumes are mounted before the network is 
brought up.  If Debian has a provision to mark f.e. an ext4 volume as a 
network volume in /etc/fstab, I do not know about it.  Additionally, in 
sysvinit the network is stopped before unmounting volumes, so when the 
system attempts to unmount the FCoE volumes, the network is already down 
and the system waits forever for the volumes to unmount.  Both of these 
problems can be worked around with kludgy init hacks that are not really 
a high enough quality to ship in Debian.  Resolving these problems the 
right way is what I was referring to when I said the init scripts need 
work.

> 0030-fcoe.service-Add-foreground-to-prevent-fcoemon-to-be.patch
> 
> => Seems to me it is better to change the unit to Type=forking
> instead? This way, systemd would know when the monitor is ready.

Given the description of Type=forking that does sound sensible.

> debian/rules:
> 
> => it seems weird to me that the socket is not started by default.

Maybe something to do with the hack-y version of dealing with forking?

Thanks,
-Jacob

Processed: Bug#834063 marked as pending

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 834063 pending
Bug #834063 [gosa] gosa: GOsa setup complains about missing php mysql module 
even if php-mysql is installed
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
834063: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834063
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#834063: marked as pending

[Mike Gabriel]

tag 834063 pending
thanks

Hello,

Bug #834063 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://git.debian.org/?p=debian-edu/pkg-team/gosa.git;a=commitdiff;h=8a46523

---
commit 8a465232d4fe30669b12734ae8697c1a1adf150f
Author: Mike Gabriel 
Date:   Wed Jan 25 22:31:57 2017 +0100

upload to unstable (debian/2.7.4+reloaded2-13)

diff --git a/debian/changelog b/debian/changelog
index 139693d..5289491 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,9 +1,25 @@
-gosa (2.7.4+reloaded2-13) UNRELEASED; urgency=medium
+gosa (2.7.4+reloaded2-13) unstable; urgency=medium
 
+  [ Dominik George ]
   * Allow IPv4 addresses and FQDNs as sudoHost. (Closes: #834065).
   * Added myself to Uploaders.
 
- -- Dominik George   Sun, 27 Nov 2016 18:25:03 +0100
+  [ Mike Gabriel ]
+  * debian/control:
++ Update D (gosa, gosa-dev): php-cli -> php7.0-cli.
++ Update PHP MySQL(i) dependency. GOsa with PHP 7 now depends on 
php-mysqli.
+  * debian/patches:
+ + Add 1028_use-mysqli-instead-of-mysql.patch. Migrate from PHP MySQL
+   extension to MySQLi extension. (Closes: #834063).
+ + Fix another man page type via 1004_fix-typos-in-man-pages.patch.
+  * lintian:
++ Update source.lintian-overrides.
++ Add php-script-but-no-phpX-cli-dep override for two files.
+  * debian/README.Debian: Fix spelling issue.
+  * debian/gosa-plugin-opsi.lintian-overrides:
++ Drop. No required any more.
+
+ -- Mike Gabriel   Wed, 25 Jan 2017 22:11:04 +0100
 
 gosa (2.7.4+reloaded2-12) unstable; urgency=medium
 

Bug#852250: [lua-socket] luasocket was not compiled with UNIX sockets support

[Michael Meskes]

Control: reassign -1 lua-socket

I don't think this is the way to go. There is no grave bug in prosody-modules,
it's lua-socket that changed its API during freeze. The way I understand our
freeze policy this is a no-go, but feel free to check with the release team.

Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL

Processed: Re: Bug#852250: [lua-socket] luasocket was not compiled with UNIX sockets support

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 lua-socket
Bug #852250 [prosody-modules] [lua-socket] luasocket was not compiled with UNIX 
sockets support
Bug reassigned from package 'prosody-modules' to 'lua-socket'.
Ignoring request to alter found versions of bug #852250 to the same values 
previously set
Ignoring request to alter fixed versions of bug #852250 to the same values 
previously set

-- 
852250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#852261: profanity FTBFS on armel/armhf/mips/mipsel: prof_whole_occurrences_tests failed

[Jack Henschel]

I created an upstream bug report at:
https://github.com/boothj5/profanity/issues/901

Greetings,
Jack



signature.asc
Description: OpenPGP digital signature

Bug#852625: unrar-free is useless and should be removed

[Ying-Chun Liu (PaulLiu)]

Let me say more clear. unrar-free currently isn't useless. Many GUI programs 
are still calling /usr/bin/unrar

And unrar-free converts those calls to unar. Unless all the programs in main 
callls unar or unar provides a compatible /usr/bin/unrar, unrar-free are still 
useful.

Please correct me or I'll lower the severity of the bug.

Thanks a lot,
Paul

Bug#852530: marked as done (terminix: Terminix fails to start)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2017 21:00:24 +
with message-id 
and subject line Bug#852530: fixed in terminix 1.4.2-3
has caused the Debian Bug report #852530,
regarding terminix: Terminix fails to start
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
852530: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852530
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: terminix
Version: 1.4.2-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Since the update to version 1.4.2, terminix fails to start with the
following message :

terminix: symbol lookup error: terminix: undefined symbol:
_D7gobject7ObjectG7ObjectG11addOnNotifyMFDFC7gobject9ParamSpec9ParamSpecC7gobject7ObjectG7ObjectGZvAyaE4gtkc12gobjecttypes13GConnectFlagsZv

Thanks


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

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

Versions of packages terminix depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2
ii  libc62.24-9
ii  libgtkd-3-0  3.5.1-1
ii  libphobos2-ldc71 1:1.1.0+b6-2
ii  libvted-3-0  3.5.1-1
ii  libx11-6 2:1.6.4-2
ii  terminix-common  1.4.2-2

terminix recommends no packages.

terminix suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: terminix
Source-Version: 1.4.2-3

We believe that the bug you reported is fixed in the latest version of
terminix, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 852...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klumpp  (supplier of updated terminix package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 25 Jan 2017 20:52:14 +0100
Source: terminix
Binary: terminix terminix-common
Architecture: source all amd64
Version: 1.4.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Matthias Klumpp 
Description:
 terminix   - Tiling terminal emulator for GNOME
 terminix-common - Tiling terminal emulator - data files
Closes: 852530
Changes:
 terminix (1.4.2-3) unstable; urgency=medium
 .
   * Tighten dependency on GtkD (Closes: #852530)
   * Update homepage
   * new-gtkdevents.patch: Build with GtkD 3.5
   * fix-32bit.patch: Fix FTBFS on 32bit architectures
Checksums-Sha1:
 2cac68d1bbc5b96ea41bb8631e3c953d8494a2d9 2127 terminix_1.4.2-3.dsc
 4b06cb0e136167814edd6359d99aca45eff320bc 16704 terminix_1.4.2-3.debian.tar.xz
 1c2eaf50e5233eec25b778fc611b3671600c265e 168522 terminix-common_1.4.2-3_all.deb
 739940993a491b1c7579264957c55af0f5626af2 955358 
terminix-dbgsym_1.4.2-3_amd64.deb
 538f6f2ca82769a48829a9668bbb55cec8a05f4a 12375 terminix_1.4.2-3_amd64.buildinfo
 afc3228d048293bf48e7206f304660b5a523c83b 408022 terminix_1.4.2-3_amd64.deb
Checksums-Sha256:
 92675053af4704b864ea98534f975f6af4339ef0fd08ef91ba9668b5c44c337f 2127 
terminix_1.4.2-3.dsc
 8779344523883f86bb9d47126bfc96cdb8087285c7651addbbc5f3d567c699fd 16704 
terminix_1.4.2-3.debian.tar.xz
 b902df5cbef8803a7ed4fb3627e349645a1ffd3e350fe790bb3058ab9e205d29 168522 
terminix-common_1.4.2-3_all.deb
 046d769717ac5b6c8a6276e55f647342e08df78154f79866a0e1d7f9bd81bdd8 955358 
terminix-dbgsym_1.4.2-3_amd64.deb
 828e7143e9da7c740b9533cdc3d698a10ca5924257b22fda57ec2a30fbff2b92 12375 
terminix_1.4.2-3_amd64.buildinfo
 585c77ac9740cf701964719695f5048422037187004fb0cc651999752889770d 408022 
terminix_1.4.2-3_amd64.deb
Files:
 6166982636df4b62feb979cff05161f8 2127 gnome optional terminix_1.4.2-3.dsc
 7889a3afee6f370409fc96bc86c998c1 16704 gnome optional 

Bug#852216: marked as done (kodi FTBFS with libcec 4)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2017 20:56:45 +
with message-id 
and subject line Bug#852216: fixed in kodi 2:17.0~rc3+dfsg1-2
has caused the Debian Bug report #852216,
regarding kodi FTBFS with libcec 4
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
852216: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852216
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kodi
Version: 2:17.0~rc3+dfsg1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

kodi FTBFS on the mips64el buildd:

> PeripheralCecAdapter.cpp: In member function 'virtual void 
> PERIPHERALS::CPeripheralCecAdapter::Announce(ANNOUNCEMENT::AnnouncementFlag, 
> const char*, const char*, const CVariant&)':
> PeripheralCecAdapter.cpp:169:25: error: 'CEC::libcec_configuration {aka 
> struct CEC::libcec_configuration}' has no member named 'bPowerOnScreensaver'
>  if (m_configuration.bPowerOnScreensaver == 1 && !bIgnoreDeactivate &&
>  ^~~

Full log at
https://buildd.debian.org/status/fetch.php?pkg=kodi=mips64el=2%3A17.0~rc3%2Bdfsg1-1=1484804663=0

Cheers,
Julien
--- End Message ---
--- Begin Message ---
Source: kodi
Source-Version: 2:17.0~rc3+dfsg1-2

We believe that the bug you reported is fixed in the latest version of
kodi, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 852...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Balint Reczey  (supplier of updated kodi package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 25 Jan 2017 21:23:22 +0100
Source: kodi
Binary: kodi kodi-data kodi-bin kodi-eventclients-common kodi-eventclients-dev 
kodi-eventclients-wiiremote kodi-eventclients-ps3 kodi-eventclients-kodi-send 
kodi-addons-dev xbmc xbmc-bin xbmc-eventclients-common xbmc-eventclients-dev 
xbmc-eventclients-wiiremote xbmc-eventclients-ps3 xbmc-eventclients-xbmc-send 
xbmc-addons-dev
Architecture: source
Version: 2:17.0~rc3+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Balint Reczey 
Description:
 kodi   - Open Source Home Theatre (executable binaries)
 kodi-addons-dev - Open Source Home Theatre (Addons Dev package)
 kodi-bin   - Open Source Home Theatre (architecture-dependent files)
 kodi-data  - Open Source Home Theatre (arch-independent data package)
 kodi-eventclients-common - Open Source Home Theatre (Event Client Common 
package)
 kodi-eventclients-dev - Open Source Home Theatre (Event Client Dev package)
 kodi-eventclients-kodi-send - Open Source Home Theatre (Event Client Kodi-SEND 
package)
 kodi-eventclients-ps3 - Open Source Home Theatre (Event Client PS3 package)
 kodi-eventclients-wiiremote - Open Source Home Theatre (Event Client WII 
Remote support package
 xbmc   - transitional dummy package
 xbmc-addons-dev - transitional dummy package
 xbmc-bin   - transitional dummy package
 xbmc-eventclients-common - transitional dummy package
 xbmc-eventclients-dev - transitional dummy package
 xbmc-eventclients-ps3 - transitional dummy package
 xbmc-eventclients-wiiremote - transitional dummy package
 xbmc-eventclients-xbmc-send - transitional dummy package
Closes: 784578 852216
Changes:
 kodi (2:17.0~rc3+dfsg1-2) unstable; urgency=medium
 .
   * Bump debhelper compat level to 10.
 Remove --parallel and --with autoreconf since those are now defaults
   * Build-depend on libcec-dev >= 4~ (Closes: #852216)
   * Fix make clean in debian/rules
   * Use real dlopen() for opening libdvdcss (Closes: #784578)
Checksums-Sha1:
 86f1632c5cfdc5584fcd41948a6895f09f41073a 5712 kodi_17.0~rc3+dfsg1-2.dsc
 48d7602e57265c77389c4017264df072823a396f 37808 
kodi_17.0~rc3+dfsg1-2.debian.tar.xz
Checksums-Sha256:
 2758ef07242b674338c6a5ba31c0e3ba0acbda5e84291a1b14f52b5a2aab04e6 5712 
kodi_17.0~rc3+dfsg1-2.dsc
 e679bb1261e2320cd8bd5e23b331a3223fd80ed45cf688a8a58ded315e0fdff7 37808 
kodi_17.0~rc3+dfsg1-2.debian.tar.xz
Files:
 

Bug#852625: unrar-free is useless and should be removed

[PaulLiu]

Exactly,

But the problem is how many other programs depends on unrar's command line.
unar doesn't support unrar and that means other programs has to re-program.

Take an example, Package "unp" doesn't call unar but call unrar.

Yours,
Paul


On Thu, Jan 26, 2017 at 2:00 AM, Adrian Bunk  wrote:

> Package: unrar-free
> Version: 1:0.0.1+cvs20140707-1
> Severity: serious
> Tags: stretch sid
>
> unrar-free itself supports only ancient versions of the RAR format,
> and for any archives created with WinRAR during the past 15 years
> all it does is to call unar.
>

Bug#852216: marked as pending

[Balint Reczey]

tag 852216 pending
thanks

Hello,

Bug #852216 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://git.debian.org/?p=pkg-multimedia/kodi.git;a=commitdiff;h=b1c2bed

---
commit b1c2bed8fb7de8f08ea97a5b9de6e6af0b7dd56b
Author: Balint Reczey 
Date:   Wed Jan 25 21:23:59 2017 +0100

Update changelog

diff --git a/debian/changelog b/debian/changelog
index 4fb41c3..5d937d1 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,12 @@
-kodi (2:17.0~rc3+dfsg1-2) UNRELEASED; urgency=medium
+kodi (2:17.0~rc3+dfsg1-2) unstable; urgency=medium
 
-  *
+  * Bump debhelper compat level to 10.
+Remove --parallel and --with autoreconf since those are now defaults
+  * Build-depend on libcec-dev >= 4~ (Closes: #852216)
+  * Fix make clean in debian/rules
+  * Use real dlopen() for opening libdvdcss (Closes: #784578)
 
- -- Balint Reczey   Wed, 18 Jan 2017 16:04:41 +0100
+ -- Balint Reczey   Wed, 25 Jan 2017 21:23:22 +0100
 
 kodi (2:17.0~rc3+dfsg1-1) unstable; urgency=medium
 

Processed: Bug#852216 marked as pending

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 852216 pending
Bug #852216 [src:kodi] kodi FTBFS with libcec 4
Ignoring request to alter tags of bug #852216 to the same tags previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
852216: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852216
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#852608: closing 852608

[Daniel Kahn Gillmor]

close 852608 2.1.18-2
thanks

Processed: closing 852608

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 852608 2.1.18-2
Bug #852608 [gnupg-agent] gnupg-agent: double-free in gpg-agent during heavily 
concurrent use
Marked as fixed in versions gnupg2/2.1.18-2; no longer marked as fixed in 
versions 2.1.18-2.
Bug #852608 [gnupg-agent] gnupg-agent: double-free in gpg-agent during heavily 
concurrent use
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
852608: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Bug#852530 marked as pending

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 852530 pending
Bug #852530 [terminix] terminix: Terminix fails to start
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
852530: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852530
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#852530: marked as pending

[Matthias Klumpp]

tag 852530 pending
thanks

Hello,

Bug #852530 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://git.debian.org/?p=pkg-gnome/terminix.git;a=commitdiff;h=f799eaf

---
commit f799eaf556bcaa13ace5345e769b1c8a111cd744
Author: Matthias Klumpp 
Date:   Wed Jan 25 21:00:58 2017 +0100

Finalize changelog for 1.4.2-3

diff --git a/debian/changelog b/debian/changelog
index b72edc1..97699da 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+terminix (1.4.2-3) unstable; urgency=medium
+
+  * Tighten dependency on GtkD (Closes: #852530)
+  * Update homepage
+  * new-gtkdevents.patch: Build with GtkD 3.5
+  * fix-32bit.patch: Fix FTBFS on 32bit architectures
+
+ -- Matthias Klumpp   Wed, 25 Jan 2017 20:52:14 +0100
+
 terminix (1.4.2-2) unstable; urgency=medium
 
   * Make archive contents reflect Git contents

Bug#852631: bzr-git: FTBFS: NotImplementedError:

[Chris Lamb]

Source: bzr-git
Version: 0.6.13-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

bzr-git fails to build from source in unstable/amd64:

  […]

  if self._determine_file_mode():
File "/usr/lib/python2.7/dist-packages/dulwich/repo.py", line 189, in 
_determine_file_mode
  raise NotImplementedError(self._determine_file_mode)
  NotImplementedError: >>
  
  ==
  ERROR: 
bzrlib.plugins.git.tests.test_push.InterToGitRepositoryTests.test_instance
  --
  Traceback (most recent call last):
  testtools.testresult.real._StringException: Empty attachments:
log
  
  Traceback (most recent call last):
File "«BUILDDIR»/tests/test_push.py", line 45, in setUp
  format=format_registry.make_bzrdir("git"))
File "/usr/lib/python2.7/dist-packages/bzrlib/tests/__init__.py", line 
2756, in make_repository
  made_control = self.make_bzrdir(relpath, format=format)
File "/usr/lib/python2.7/dist-packages/bzrlib/tests/__init__.py", line 
2743, in make_bzrdir
  return format.initialize_on_transport(t)
File "«BUILDDIR»/dir.py", line 231, in initialize_on_transport
  repo = TransportRepo.init(transport, bare=self.bare)
File "«BUILDDIR»/transportgit.py", line 396, in init
  ret._init_files(bare)
File "/usr/lib/python2.7/dist-packages/dulwich/repo.py", line 198, in 
_init_files
  if self._determine_file_mode():
File "/usr/lib/python2.7/dist-packages/dulwich/repo.py", line 189, in 
_determine_file_mode
  raise NotImplementedError(self._determine_file_mode)
  NotImplementedError: >>
  
  ==
  ERROR: 
bzrlib.plugins.git.tests.test_git_remote_helper.OpenLocalDirTests.test_from_dir
  --
  Traceback (most recent call last):
  testtools.testresult.real._StringException: Empty attachments:
log
  
  Traceback (most recent call last):
File "«BUILDDIR»/tests/test_git_remote_helper.py", line 61, in test_from_dir
  self.make_branch_and_tree('.', format='git')
File "/usr/lib/python2.7/dist-packages/bzrlib/tests/__init__.py", line 
3021, in make_branch_and_tree
  b = self.make_branch(relpath, format=format)
File "/usr/lib/python2.7/dist-packages/bzrlib/tests/__init__.py", line 
2711, in make_branch
  repo = self.make_repository(relpath, format=format)
File "/usr/lib/python2.7/dist-packages/bzrlib/tests/__init__.py", line 
2756, in make_repository
  made_control = self.make_bzrdir(relpath, format=format)
File "/usr/lib/python2.7/dist-packages/bzrlib/tests/__init__.py", line 
2743, in make_bzrdir
  return format.initialize_on_transport(t)
File "«BUILDDIR»/dir.py", line 231, in initialize_on_transport
  repo = TransportRepo.init(transport, bare=self.bare)
File "«BUILDDIR»/transportgit.py", line 396, in init
  ret._init_files(bare)
File "/usr/lib/python2.7/dist-packages/dulwich/repo.py", line 198, in 
_init_files
  if self._determine_file_mode():
File "/usr/lib/python2.7/dist-packages/dulwich/repo.py", line 189, in 
_determine_file_mode
  raise NotImplementedError(self._determine_file_mode)
  NotImplementedError: >>
  
  ==
  ERROR: 
bzrlib.plugins.git.tests.test_push.InterToGitRepositoryTests.test_pointless_fetch_refs_old_mapping
  --
  Traceback (most recent call last):
  testtools.testresult.real._StringException: Empty attachments:
log
  
  Traceback (most recent call last):
File "«BUILDDIR»/tests/test_push.py", line 45, in setUp
  format=format_registry.make_bzrdir("git"))
File "/usr/lib/python2.7/dist-packages/bzrlib/tests/__init__.py", line 
2756, in make_repository
  made_control = self.make_bzrdir(relpath, format=format)
File "/usr/lib/python2.7/dist-packages/bzrlib/tests/__init__.py", line 
2743, in make_bzrdir
  return format.initialize_on_transport(t)
File "«BUILDDIR»/dir.py", line 231, in initialize_on_transport
  repo = TransportRepo.init(transport, bare=self.bare)
File "«BUILDDIR»/transportgit.py", line 396, in init
  ret._init_files(bare)
File "/usr/lib/python2.7/dist-packages/dulwich/repo.py", line 198, in 
_init_files
  if self._determine_file_mode():
File "/usr/lib/python2.7/dist-packages/dulwich/repo.py", line 189, in 
_determine_file_mode
  raise NotImplementedError(self._determine_file_mode)
  NotImplementedError: >>
  
  ==
  ERROR: 

Bug#852543: apache and sysvinit

[Tom H]

apache2ctl should check for "/run/systemd/system" not for "/run/systemd"

Processed: severity of 852543 is grave

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 852543 grave
Bug #852543 [apache2] Apache doesn't start anymore with sysvinit
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
852543: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852543
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#833327: marked as done (xmldiff: maintainer address bounces)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2017 19:51:30 +
with message-id 
and subject line Bug#833327: fixed in xmldiff 0.6.10-3
has caused the Debian Bug report #833327,
regarding xmldiff: maintainer address bounces
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
833327: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xmldiff
Version: 0.6.10-2
Severity: serious

[ Uploaders X-Debbugs-Cc'ed ]

The maintainer address for xmldiff bounces, see below.

Ansgar

Mail Delivery System  writes:
> This message was created automatically by mail delivery software.
>
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es) failed:
>
>   afayo...@debian.org
> Unrouteable address
>
> -- This is a copy of the message, including all the headers. --
>
[...]
> To: Alexandre Fayolle , John Paul Adrian Glaubitz 
> 
> X-DAK: dak process-upload
> X-Debian: DAK
> X-Debian-Package: xmldiff
> Precedence: bulk
> Auto-Submitted: auto-generated
> MIME-Version: 1.0
> Content-Type: text/plain; charset="utf-8"
> Content-Transfer-Encoding: 8bit
> Subject: xmldiff_0.6.10-2.2_amd64.changes ACCEPTED into unstable
> Message-Id: [...]
> Date: Wed, 03 Aug 2016 04:34:49 +
>
> Mapping sid to unstable.
>
> Accepted:
>
> Format: 1.8
> Date: Wed, 03 Aug 2016 05:59:29 +0200
> Source: xmldiff
> Binary: xmldiff xmldiff-xmlrev
> Architecture: source amd64 all
> Version: 0.6.10-2.2
> Distribution: sid
> Urgency: medium
> Maintainer: Alexandre Fayolle 
> Changed-By: John Paul Adrian Glaubitz 
> Description:
>  xmldiff- tree to tree correction between xml documents
>  xmldiff-xmlrev - xmldiff output formatter
> Closes: 822039
> Changes:
>  xmldiff (0.6.10-2.2) unstable; urgency=medium
>  .
>* Non-maintainer upload.
>* Add build-arch and build-indep targets to debian/rules to fix
>  FTBFS with newer versions of dpkg (Closes: #822039)
> Checksums-Sha1:
>  2f0f87aa9d1ad8190ea6073dc564e5ec718242b7 1981 xmldiff_0.6.10-2.2.dsc
>  c939c67aa97b2fd1d087308e6183674ac5fb5071 4404 xmldiff_0.6.10-2.2.diff.gz
>  562b85a2a148ea226f1a0b99a425cf76f274c8e1 11038 
> xmldiff-dbgsym_0.6.10-2.2_amd64.deb
>  d069ddb7d738dd9c14e14b882eb7b52ab2787b95 8646 
> xmldiff-xmlrev_0.6.10-2.2_all.deb
>  39246abfce47bec773312a488692ea6ce0e96968 43726 xmldiff_0.6.10-2.2_amd64.deb
> Checksums-Sha256:
>  04f1dba94436a7cd282acca063e697680d2c103633fea4f348183e2a481409dd 1981 
> xmldiff_0.6.10-2.2.dsc
>  5e404657e73eae4e67cfcfff23433a4d73f77034cf4c1461e0276e3193ab4b1f 4404 
> xmldiff_0.6.10-2.2.diff.gz
>  4675477b1a512f31e84880534c384bb5a794d7a0a10323d4b775d0b28bb351cf 11038 
> xmldiff-dbgsym_0.6.10-2.2_amd64.deb
>  6302573638935240ed56a8bf6d398331cfa57529a014432fa116d31ec4a00fe5 8646 
> xmldiff-xmlrev_0.6.10-2.2_all.deb
>  1e27b93b3ce05763dbe8e48eb3181436031d15cc22dab739164688d8a9b0a876 43726 
> xmldiff_0.6.10-2.2_amd64.deb
> Files:
>  5b2d7bb27c8910d25fafa327e9bbd9e2 1981 misc optional xmldiff_0.6.10-2.2.dsc
>  5356d53d2116dc3b7341c08510787368 4404 misc optional 
> xmldiff_0.6.10-2.2.diff.gz
>  6394766b9020e8039387fd8c3d140d2a 11038 debug extra 
> xmldiff-dbgsym_0.6.10-2.2_amd64.deb
>  851e76ecc29b2e570f3609b0de9e1234 8646 misc optional 
> xmldiff-xmlrev_0.6.10-2.2_all.deb
>  1b74a41206b3165d40cfab6df1b79a4d 43726 misc optional 
> xmldiff_0.6.10-2.2_amd64.deb
>
>
>
> Thank you for your contribution to Debian.
--- End Message ---
--- Begin Message ---
Source: xmldiff
Source-Version: 0.6.10-3

We believe that the bug you reported is fixed in the latest version of
xmldiff, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 833...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated xmldiff package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 25 Jan 2017 21:25:02 +0200
Source: xmldiff
Binary: xmldiff 

Bug#833331: marked as done (Updating the xmldiff Uploaders list)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2017 19:51:30 +
with message-id 
and subject line Bug#833327: fixed in xmldiff 0.6.10-3
has caused the Debian Bug report #833327,
regarding Updating the xmldiff Uploaders list
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
833327: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xmldiff
Version: 0.6.10-2.1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Alexandre Fayolle  has retired, so can't work on
the xmldiff package anymore (at least with this address).

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: xmldiff
Source-Version: 0.6.10-3

We believe that the bug you reported is fixed in the latest version of
xmldiff, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 833...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated xmldiff package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 25 Jan 2017 21:25:02 +0200
Source: xmldiff
Binary: xmldiff xmldiff-xmlrev
Architecture: source
Version: 0.6.10-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Description:
 xmldiff- tree to tree correction between xml documents
 xmldiff-xmlrev - xmldiff output formatter
Closes: 833327
Changes:
 xmldiff (0.6.10-3) unstable; urgency=medium
 .
   * QA upload.
   * Set maintainer to Debian QA Group. (see #852629) (Closes: #833327)
Checksums-Sha1:
 b9b43ed7f1dd983da2f3d788bec152f264e5f829 1811 xmldiff_0.6.10-3.dsc
 77d8c2cadce4576c79b366d0979ab8274072647f 4643 xmldiff_0.6.10-3.diff.gz
Checksums-Sha256:
 f3e4e2f8c93f092b78e724c56becc1e1190ebd3a00773ea373ecadef53ab4854 1811 
xmldiff_0.6.10-3.dsc
 2c7d6b85d548ce454672339631884f931c80fda7bb9e02b0499b8e593ece2028 4643 
xmldiff_0.6.10-3.diff.gz
Files:
 ea7fc33d7f38f6998de92bf266f93e9a 1811 misc optional xmldiff_0.6.10-3.dsc
 4c7ea052a248594da2c7aa5d5cfcd9d5 4643 misc optional xmldiff_0.6.10-3.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAliI/csACgkQiNJCh6LY
mLEDHg/6A2L/MYTQvtaavcN0G7hBcXUcBh376gMW3KMs7a2NnavHvAZ0Hjy24g2b
irUe1lGYpYp/JxjKdUx6U+xmW6G+/4ZbOXwIwjEfRhq7YSwARE+YLbZhzaixrmdK
q4rt+PP5P/B66f/Rw+YxsyNSMvovbdtYxDZarAA0hEHHaO/vFQafg+EAhTn2V4Ru
PH31KgO5a84/nIWEkFkqB5ULTOJ4Dml1N7WWjBWY6+VRpRmTMDT4E66cEhKPRLKZ
Vc53JOUZpEaZtzIQ4We46JyYqsKStqNDmq25M/YG2AXlvm9UqfELXKpmedASou1P
n0NTYFX5aR2+6xsqqTAPpzIyLatfPF2krbZ2MNhUcBAy1XDYj5q6PTx+JAtZrGe1
WtySEu7Bh55SK/RWLhRNt+eiA8gdaFZ1hwr0OrnTu5CaKBiILBwFu3bIWlw2iI5X
l9okNy3mj3QbNw4yRRWats+UxF2IPSnWFs+RkLCEVprlsNI6n2uwmvqD3wy51/mk
01IbUehhTOJWHnnR60jPPi7VLaUUwxXLK9zl9p6VrF51d/xnR+onbpsimO/x3xxt
m1VgKUzXb8+B4lLy8lyc9dmtvrHwQNUgqtREUptnEYUAaLttoeYlQtlDLd8TfZyZ
1cn1slE8ULfmTgH2q25S9hKUlsVIm8E3261jDLaaTQ9ey/+7hrw=
=UltL
-END PGP SIGNATURE End Message ---

Bug#848748: marked as done (blockdiag: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2017 19:48:36 +
with message-id 
and subject line Bug#848748: fixed in blockdiag 1.5.3+dfsg-1.1
has caused the Debian Bug report #848748,
regarding blockdiag: FTBFS: E: Build killed with signal TERM after 150 minutes 
of inactivity
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
848748: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848748
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: blockdiag
Version: 1.5.3+dfsg-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161219 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>   File "/usr/lib/python3/dist-packages/wand/image.py", line 2767, in destroy
> for i in range(0, len(self.sequence)):
> TypeError: object of type 'NoneType' has no len()
> 
> 
> - >> end captured stdout << --
> 
> Ran 710 tests in 2.617s
> 
> FAILED (SKIP=351, failures=2)
> E: pybuild pybuild:276: test: plugin distutils failed with: exit code=1: cd 
> /<>/blockdiag-1.5.3+dfsg/.pybuild/pythonX.Y_3.5/build; python3.5 -m 
> nose 
> dh_auto_test: pybuild --test --test-nose -i python{version} -p 3.5 returned 
> exit code 13
> debian/rules:13: recipe for target 'build' failed
> make: *** [build] Error 25
> dpkg-buildpackage: error: debian/rules build gave error exit status 2
> E: Build killed with signal TERM after 150 minutes of inactivity

The full build log is available from:
   http://aws-logs.debian.net/2016/12/19/blockdiag_1.5.3+dfsg-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: blockdiag
Source-Version: 1.5.3+dfsg-1.1

We believe that the bug you reported is fixed in the latest version of
blockdiag, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 848...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Rebecca N. Palmer  (supplier of updated blockdiag 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 22 Jan 2017 22:13:59 +
Source: blockdiag
Binary: python-blockdiag python3-blockdiag
Architecture: source
Version: 1.5.3+dfsg-1.1
Distribution: unstable
Urgency: medium
Maintainer: Kouhei Maeda 
Changed-By: Rebecca N. Palmer 
Description:
 python-blockdiag - generate block-diagram image file from spec-text file
 python3-blockdiag - generate block-diagram image file from spec-text file for 
Python
Closes: 848748
Changes:
 blockdiag (1.5.3+dfsg-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Don't fail tests on a harmless wand warning. Closes: #848748
Checksums-Sha1:
 11789938ba37d0cfcbd675dd1bb59cd35bc2f77e 2326 blockdiag_1.5.3+dfsg-1.1.dsc
 f351bda0f542079560657eaac4d1fa6d8215158b 152803 
blockdiag_1.5.3+dfsg.orig.tar.gz
 bfe5bce0f9f69db4aad46790afba3e05c5fec5c2 9176 
blockdiag_1.5.3+dfsg-1.1.debian.tar.xz
Checksums-Sha256:
 15f9d600cb43b06116fe53702488cbf7b275a0d87955037f57e5fcb64c06cc6d 2326 
blockdiag_1.5.3+dfsg-1.1.dsc
 83fd0896986d003ed51f7d17a5af642a2a46ecd0e1503a5c48bdb9953869c8ea 152803 
blockdiag_1.5.3+dfsg.orig.tar.gz
 28bdd1f1c564e47abe74555997dad1967f435bceafa9c56cb0cc652002fb89ca 9176 
blockdiag_1.5.3+dfsg-1.1.debian.tar.xz
Files:
 fbaecf987561585c1bcf27057215f762 2326 python optional 
blockdiag_1.5.3+dfsg-1.1.dsc
 4f961e8d3c145975d2cbca78aee3a124 152803 python optional 
blockdiag_1.5.3+dfsg.orig.tar.gz
 66804509ef7dd17693cfe77c2670b964 9176 python optional 
blockdiag_1.5.3+dfsg-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAliI/NoACgkQ0+Fzg8+n

Processed: Re: Bug#852250: [lua-socket] luasocket was not compiled with UNIX sockets support

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 prosody-modules
Bug #852250 [lua-socket] [lua-socket] luasocket was not compiled with UNIX 
sockets support
Bug reassigned from package 'lua-socket' to 'prosody-modules'.
No longer marked as found in versions luasocket/3.0~rc1+git+ac3201d-2.
Ignoring request to alter fixed versions of bug #852250 to the same values 
previously set
> tag -1 + patch upstream confirmed
Bug #852250 [prosody-modules] [lua-socket] luasocket was not compiled with UNIX 
sockets support
Added tag(s) confirmed, patch, and upstream.

-- 
852250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#852250: [lua-socket] luasocket was not compiled with UNIX sockets support

[Mathieu Parent]

Control: reassign -1 prosody-modules
Control: tag -1 + patch upstream confirmed


On Wed, 25 Jan 2017 13:04:02 +0100 Enrico Tassi
 wrote:
> On Wed, Jan 25, 2017 at 10:24:25AM +0100, Michael Meskes wrote:
> > > Hopefully somebody is prepared to fix all rdepends.
> >
> > Or better reverts the API change.
>
> The bug is definitely important.
>
> Mathieu can you take care of it?

Can you test the attached patch on prosody-modules? It's future-proof
and inspired by Courtney's patch on ekeyd.

Regards.

Mathieu Parent
From 6e1199cd1b19361a03bbd2d2243246bd1f75921b Mon Sep 17 00:00:00 2001
From: Mathieu Parent 
Date: Wed, 25 Jan 2017 20:42:56 +0100
Subject: [PATCH] Fix compatibility problems with Unix domain sockets in newer
 versions of luasocket

Inspired by a similar patch on ekeyd by Courtney Bane.
---
 mod_auth_dovecot/auth_dovecot/sasl_dovecot.lib.lua | 10 +++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/mod_auth_dovecot/auth_dovecot/sasl_dovecot.lib.lua b/mod_auth_dovecot/auth_dovecot/sasl_dovecot.lib.lua
index a6f1958..8e2f1cf 100644
--- a/mod_auth_dovecot/auth_dovecot/sasl_dovecot.lib.lua
+++ b/mod_auth_dovecot/auth_dovecot/sasl_dovecot.lib.lua
@@ -26,7 +26,11 @@ local m_random = math.random;
 local tostring, tonumber = tostring, tonumber;
 
 local socket = require "socket"
-pcall(require, "socket.unix");
+function tryload_unix()
+   socket.unix = require "socket.unix"
+end
+pcall(tryload_unix);
+local sock = socket.unix.stream or socket.unix.tcp or socket.unix
 local base64 = require "util.encodings".base64;
 local b64, unb64 = base64.encode, base64.decode;
 local jid_escape = require "util.jid".escape;
@@ -54,9 +58,9 @@ local function connect(socket_info)
 		conn = socket.tcp();
 		ok, err = conn:connect(socket_host, socket_port);
 		socket_path = ("%s:%d"):format(socket_host, socket_port);
-	elseif socket.unix then
+	elseif sock then
 		socket_path = socket_info;
-		conn = socket.unix();
+		conn = sock();
 		ok, err = conn:connect(socket_path);
 	else
 		err = "luasocket was not compiled with UNIX sockets support";
-- 
2.11.0

Bug#844886: libalog is waiting for binutils testing migration

[Adrian Bunk]

libalog is waiting for gcc-6 testing migration,
which itself depends on binutils testing migration.

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#852250: [lua-socket] luasocket was not compiled with UNIX sockets support

[Mathieu Parent]

On Wed, 25 Jan 2017 13:37:41 +0100 Enrico Tassi
 wrote:
> On Wed, Jan 25, 2017 at 10:24:25AM +0100, Michael Meskes wrote:
> > > Hopefully somebody is prepared to fix all rdepends.
> >
> > Or better reverts the API change.
>
> I gave a quick look at the problem.
>
> I don't know why Mathieu packaged a new upstream snapshot exactly,
> I hope it is not for the new unix.tcp/udp feature.  If so, reverting the
> API change is as simple as reverting
>
>   aa1b8cc9bc35e56de15eeb153c899e4c51de82a8
>
> There is just a trivial conflict on the makefile.
>
> Mathieu, does luasandbox need the new unix sockets?

Yes. I need both TCP and UDP socket.

Regards.

Mathieu Parent

Processed: Re: Bug#852627: lcms2: CVE-2016-10165: heap OOB read parsing crafted ICC profile

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #852627 [src:lcms2] lcms2: CVE-2016-10165: heap OOB read parsing crafted 
ICC profile
Severity set to 'grave' from 'important'

-- 
852627: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852627
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#844918: libncursesada is waiting for binutils testing migration

[Adrian Bunk]

libncursesada is waiting for gcc-6 testing migration,
which itself depends on binutils testing migration.

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#851162: marked as done (FTBFS: issues with longdouble precision on ppc)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2017 18:18:45 +
with message-id 
and subject line Bug#851162: fixed in h5py 2.7.0~rc3-1
has caused the Debian Bug report #851162,
regarding FTBFS: issues with longdouble precision on ppc
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
851162: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851162
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:h5py
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Usertags: ppc64el

Dear Maintainer,

The recent release of h5py FTBFS on powerpc-based architectures due to
test failures regarding long-double precision.

Upstream has been notified but fails to find where the origin of the
issue is. Some help from ppc experts would be appreciated. The latest
build log is available here [1].

[1] 
https://buildd.debian.org/status/fetch.php?pkg=h5py=ppc64el=2.7.0~rc2-1=1483739258

Regards,
Ghis


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

Kernel: Linux 4.8.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: h5py
Source-Version: 2.7.0~rc3-1

We believe that the bug you reported is fixed in the latest version of
h5py, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 851...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ghislain Antony Vaillant  (supplier of updated h5py package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 25 Jan 2017 14:13:35 +
Source: h5py
Binary: python-h5py python-h5py-dbg python3-h5py python3-h5py-dbg 
python-h5py-doc
Architecture: source
Version: 2.7.0~rc3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Ghislain Antony Vaillant 
Description:
 python-h5py - general-purpose Python interface to hdf5 (Python 2)
 python-h5py-dbg - debug extension for h5py (Python 2)
 python-h5py-doc - h5py documentation
 python3-h5py - general-purpose Python interface to hdf5 (Python 3)
 python3-h5py-dbg - debug extension for h5py (Python 3)
Closes: 851162
Changes:
 h5py (2.7.0~rc3-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #851162)
   * Rebase patch queue
 - Drop 0002-Explicity-specify-endianess-of-expected-output-type.patch,
 applied upstream
   * Cherry pick upstream fix for builds on ppc64el
 - New patch 0002-Fix-arch-name-for-ppc64le.patch
   * Cherry-pick proposed fix for version numbers
 - New patch 0003-Fix-version_tuple-to-make-it-PEP440-compliant.patch
Checksums-Sha1:
 9ae426992cedb3d97dc205e4022de21e0bf4c340 2639 h5py_2.7.0~rc3-1.dsc
 9098edc50d89b086999c3e7a984a91266aa6a5ee 265017 h5py_2.7.0~rc3.orig.tar.gz
 7032fb6cac78872d8d48c049b6dceb6592efe13f 7876 h5py_2.7.0~rc3-1.debian.tar.xz
Checksums-Sha256:
 b780ffd947a85d1a1dfc09b3ac8809bd5d68152ed059e77c059e63deaf6292fb 2639 
h5py_2.7.0~rc3-1.dsc
 af509d1e817ef2788560149bb0ee0eda4c6e83a790e38a1d194ef8f874268cb4 265017 
h5py_2.7.0~rc3.orig.tar.gz
 7f280d1f953baa315509330f1c169be408b214d5e93180f3425093ac75e33990 7876 
h5py_2.7.0~rc3-1.debian.tar.xz
Files:
 6e34f82fd92a6d8485ec89515e3fd806 2639 python optional h5py_2.7.0~rc3-1.dsc
 b932f250d77c370a573795e6cacad075 265017 python optional 
h5py_2.7.0~rc3.orig.tar.gz
 56b0ddcd503c37a2ab1b1a239db7ec4e 7876 python optional 
h5py_2.7.0~rc3-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJYiOofAAoJEPNPCXROn13ZZsEP/0WuS2+5wDzzKNuMmGL1gm0R
4q5AIEC4h1h4ng76hVi4wvv/fq9IwI/jC8gQJdU2WVCsvzl+XJbpJeu1soGcsm/y
w9x1epVrhcSMxCedI7nVGMRYhf8nNCUUVf99Inw3O13aWKJHuBejg9/e1lU/ROQA
xg3qGh4Jj7Oonsvgc3m+Hq9quKNYJ9Pq769T4YXSGYxeW0HJqIOxivE/PBSIOhZi
WAez9vep8xjYOi5H98RuyfEWN8h88aHZl25pVyx6BXbaHeHYT+fKjqXjGEa7hW1V
NpLGtwNu9b95CaidhrO9McQekcVElQKO2bQ9mIKxXBSqaWWxv8SK9ywZkf9z4QXK

Processed: (no subject)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 848742 + jessie
Bug #848742 {Done: Mike Gabriel } [src:libmateweather] 
libmateweather: FTBFS: configure: error: Can't find zoneinfo directory. Use 
--with-zoneinfo-dir
Added tag(s) jessie.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
848742: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848742
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Works for me and no feedback from the submitter

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 802954 important
Bug #802954 [gnu-smalltalk-el] gnu-smalltalk-el: Prevents upgrade of emacs24
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
802954: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802954
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#852622: marked as done (xcffib FTBFS in stretch)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2017 20:01:45 +0200
with message-id <20170125180145.7mxiaz4443tokhyc@localhost>
and subject line This is already fixed in unstable
has caused the Debian Bug report #852622,
regarding xcffib FTBFS in stretch
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
852622: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852622
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xcffib
Version: 0.3.6-1
Severity: serious

...
Building xcffib-0.3.6...
Preprocessing library xcffib-0.3.6...
[1 of 2] Compiling Data.XCB.Python.PyHelpers ( 
generator/Data/XCB/Python/PyHelpers.hs, dist/build/Data/XCB/Python/PyHelpers.o )

generator/Data/XCB/Python/PyHelpers.hs:90:25: error:
* Couldn't match expected type `Op ()'
  with actual type `Ident annot0 -> annot0 -> Expr annot0'
* Probable cause: `Dot' is applied to too few arguments
  In the first argument of `BinaryOp', namely `(Dot ())'
  In the expression: BinaryOp (Dot ()) (getExpr e1) (getExpr e2) ()
  In an equation for `mkDot':
  mkDot e1 e2 = BinaryOp (Dot ()) (getExpr e1) (getExpr e2) ()

generator/Data/XCB/Python/PyHelpers.hs:90:29: error:
* Couldn't match expected type `Expr annot0' with actual type `()'
* In the first argument of `Dot', namely `()'
  In the first argument of `BinaryOp', namely `(Dot ())'
  In the expression: BinaryOp (Dot ()) (getExpr e1) (getExpr e2) ()
cabal: unable to decommit memory: Invalid argument
cabal: unable to decommit memory: Invalid argument
Makefile:30: recipe for target 'dist/build/xcffibgen/xcffibgen' failed
make[2]: *** [dist/build/xcffibgen/xcffibgen] Error 1



This works in 0.4.2-2 in unstable, but 0.4.2-2 FTBFS later (see #839314).
--- End Message ---
--- Begin Message ---
Version: 0.4.2-2

As explained in the bug report, this is already fixed in unstable.

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--- End Message ---

Bug#796609: fcoe-utils: Has init script in runlevel S but no matching service file

[Felipe Sateler]

On 25 January 2017 at 14:36, Jacob Luna Lundberg  wrote:
>
> Hi Felipe,
>
> On Wed, Jan 25, 2017 at 11:50:33AM -0300, Felipe Sateler wrote:
>> Apparently, fcow-utils as currently packaged is not usable in
>> debian.
>
> It is plenty usable, just not if you are using systemd.  Yes, I am aware
> policy at this point requires systemd support.

OK, sorry. The impression I had from your earlier message is that it
didn't work[1].

>> Jacob Luna Lundberg, Liang Guo, could you please review and upload
>> this patch?
>
> I can't review the systemd components.  I do not use systemd and I am
> unfamiliar with its configuration.  Also, I am not a DD, so although I
> could upload the patch to the repository, I can't upload a package.

I can sponsor your upload, but as I have never used fcoe, I do not
want to upload such a large NMU without maintainer input.

> There are (as mentioned) a few bugs in the current package, so if there
> has been an upstream release, we should really incorporate that as well.
> Some of the patches merged into this jumbo patch also sound like a good
> idea for inclusion into Debian.  I can (will) look into all of the
> non-systemd parts in a month or so when my schedule settles a bit.  I
> would be inclined to just accept the systemd parts as submitted given
> they seem to have seen some testing already.

Seems like a good plan. I can provide input on the systemd-specific parts:

0030-fcoe.service-Add-foreground-to-prevent-fcoemon-to-be.patch

=> Seems to me it is better to change the unit to Type=forking
instead? This way, systemd would know when the monitor is ready.

0038-Makes-fcoe.service-starting-before-network.patch

=> this appears to have a slight malformation (a / is missing in the
header, this it edits etc/systemdfcoe.service)

debian/rules:

=> it seems weird to me that the socket is not started by default.
=> I would process the socket before the daemon, so that the daemon
cannot be started by the socket when removing the package.


If you have any questions, I'm always available to help.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796609#22

-- 

Saludos,
Felipe Sateler

Bug#852625: unrar-free is useless and should be removed

[Adrian Bunk]

Package: unrar-free
Version: 1:0.0.1+cvs20140707-1
Severity: serious
Tags: stretch sid

unrar-free itself supports only ancient versions of the RAR format,
and for any archives created with WinRAR during the past 15 years
all it does is to call unar.

Bug#852622: xcffib FTBFS in stretch

[Adrian Bunk]

Source: xcffib
Version: 0.3.6-1
Severity: serious

...
Building xcffib-0.3.6...
Preprocessing library xcffib-0.3.6...
[1 of 2] Compiling Data.XCB.Python.PyHelpers ( 
generator/Data/XCB/Python/PyHelpers.hs, dist/build/Data/XCB/Python/PyHelpers.o )

generator/Data/XCB/Python/PyHelpers.hs:90:25: error:
* Couldn't match expected type `Op ()'
  with actual type `Ident annot0 -> annot0 -> Expr annot0'
* Probable cause: `Dot' is applied to too few arguments
  In the first argument of `BinaryOp', namely `(Dot ())'
  In the expression: BinaryOp (Dot ()) (getExpr e1) (getExpr e2) ()
  In an equation for `mkDot':
  mkDot e1 e2 = BinaryOp (Dot ()) (getExpr e1) (getExpr e2) ()

generator/Data/XCB/Python/PyHelpers.hs:90:29: error:
* Couldn't match expected type `Expr annot0' with actual type `()'
* In the first argument of `Dot', namely `()'
  In the first argument of `BinaryOp', namely `(Dot ())'
  In the expression: BinaryOp (Dot ()) (getExpr e1) (getExpr e2) ()
cabal: unable to decommit memory: Invalid argument
cabal: unable to decommit memory: Invalid argument
Makefile:30: recipe for target 'dist/build/xcffibgen/xcffibgen' failed
make[2]: *** [dist/build/xcffibgen/xcffibgen] Error 1



This works in 0.4.2-2 in unstable, but 0.4.2-2 FTBFS later (see #839314).

Bug#852452: marked as done (obmenu: Uninstallable due to dependency on "2.7" (should be "python2.7"))

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2017 17:49:48 +
with message-id 
and subject line Bug#852452: fixed in obmenu 1.0-4
has caused the Debian Bug report #852452,
regarding obmenu: Uninstallable due to dependency on "2.7" (should be 
"python2.7")
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
852452: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852452
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: obmenu
Version: 1.0-3
Severity: serious

Hi,

obmenu 1.0-3 is uninstallable since it has a dependency on the
non-existing package "2.7" (which probably should be "python2.7"
instead).

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

We believe that the bug you reported is fixed in the latest version of
obmenu, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 852...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Diego Sarzi  (supplier of updated obmenu package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 25 Jan 2017 13:55:34 -0200
Source: obmenu
Binary: obmenu
Architecture: source
Version: 1.0-4
Distribution: unstable
Urgency: medium
Maintainer: Diego Sarzi 
Changed-By: Diego Sarzi 
Description:
 obmenu - Graphical menu editor for openbox
Closes: 852452
Changes:
 obmenu (1.0-4) unstable; urgency=medium
 .
   * debian/control:
   - Removed "${python:Versions}" to avoid the package can't
 be uninstallable. (Closes: #852452)
   * debian/copyright:
   - Updated the copyright years.
Checksums-Sha1:
 4ab69d6468e125df768595103e3f180137a4d7b1 1692 obmenu_1.0-4.dsc
 2b7c7ec7fe178279c9caffef62db37589d76efad 6380 obmenu_1.0-4.debian.tar.xz
Checksums-Sha256:
 3952f488509fd8376b8b64f4994407bd9026cde561cac7fc8a1add01f56dd740 1692 
obmenu_1.0-4.dsc
 e03a5d2608168fac303f6832193047b9842056b57f276b9b4911738ce0ce822e 6380 
obmenu_1.0-4.debian.tar.xz
Files:
 3867d5ade4cc874c1eb554e5aa9c9ec2 1692 x11 extra obmenu_1.0-4.dsc
 4e6195055f0a02ea3f49db91fac0a2a2 6380 x11 extra obmenu_1.0-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEs/UaJxJhnD7NdLjheElO9yN1pmwFAliI4YMACgkQeElO9yN1
pmwWcg/+NAsuzlV8eSb04HUPGahXhl/wxckzGz9UMNDcQP13mI8hCyllmJ5rHdvZ
D7hiEXAivMXX+6TW4brz8Gvc3WjaM+YZWHECwtB11ns3Nb1kAk71EAJKXVUOJklh
dYvxfUNMageUIadbPN9qbVqL8mh/Q+Cddvu72A4sgc9SKfLp8lvhLoyapYba2AWw
0X30HJA+hYjn0Hy/hygCRCHoFXlOSmTJKcIqqoZ89Ids6/hPHWPieMS9dbOd/UhH
MBL3B22sFXaHlAQlmjNYbd/I5QAwy3nHRK5I1ylSDXv9NaFhEE/GjX4jI6bzzHg/
ab63X7bzxH3cz6zQuvpXbYz8WA13uHsEzH9GBITRISFiRFD+/53DQ1PN9sIstzai
8NGnEZ9+6uZl6/YNXpqI6c/s4DK8y7HhwurR0yB9h5uCsdjoWiaqsCwptFHXQSFe
S9iJ8bp9N2UCVJARRcTqodBqzRJ2Q1IdOTqjYzyQ3zyS7F9pwR5+JNZ4vQ9cTAYG
ONMoiwlUvo5jeN4rgKAGHeUQvXPYMtXNxn2+ctr/KhO5h48UV7TQz6Bo/kuIqlfw
KE+ZYAdhJ+qJGlvpuSlkF0wUlCcyQ7WKA5AN3wcSLaqd2jVEet01/OJ7Z0T/Voa5
KzIQrFjl1yL17lvTi4yj09bI4RDSo+8vf+1uU9St8jtjoSrYuBM=
=kiDa
-END PGP SIGNATURE End Message ---

Bug#796609: fcoe-utils: Has init script in runlevel S but no matching service file

[Jacob Luna Lundberg]

Hi Felipe,

On Wed, Jan 25, 2017 at 11:50:33AM -0300, Felipe Sateler wrote:
> Apparently, fcow-utils as currently packaged is not usable in
> debian.

It is plenty usable, just not if you are using systemd.  Yes, I am aware 
policy at this point requires systemd support.

> Jacob Luna Lundberg, Liang Guo, could you please review and upload
> this patch?

I can't review the systemd components.  I do not use systemd and I am 
unfamiliar with its configuration.  Also, I am not a DD, so although I 
could upload the patch to the repository, I can't upload a package.

There are (as mentioned) a few bugs in the current package, so if there 
has been an upstream release, we should really incorporate that as well.  
Some of the patches merged into this jumbo patch also sound like a good 
idea for inclusion into Debian.  I can (will) look into all of the 
non-systemd parts in a month or so when my schedule settles a bit.  I 
would be inclined to just accept the systemd parts as submitted given 
they seem to have seen some testing already.

Thanks,
-Jacob

Bug#852597: marked as done (iio-sensor-proxy: process keeps running after package purge)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2017 17:04:41 +
with message-id 
and subject line Bug#852597: fixed in iio-sensor-proxy 2.0-3
has caused the Debian Bug report #852597,
regarding iio-sensor-proxy: process keeps running after package purge
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
852597: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852597
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: iio-sensor-proxy
Severity: serious
Version: 2.0-1

I just purged iio-sensor-proxy, but:

$ ps 574
  PID TTY  STAT   TIME COMMAND
  574 ?Ssl4:10 /usr/sbin/iio-sensor-proxy

The process should stop running on removing the package.

Cheers,
Julien
--- End Message ---
--- Begin Message ---
Source: iio-sensor-proxy
Source-Version: 2.0-3

We believe that the bug you reported is fixed in the latest version of
iio-sensor-proxy, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 852...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ritesh Raj Sarraf  (supplier of updated iio-sensor-proxy 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 25 Jan 2017 22:09:12 +0530
Source: iio-sensor-proxy
Binary: iio-sensor-proxy
Architecture: source amd64
Version: 2.0-3
Distribution: unstable
Urgency: medium
Maintainer: Ritesh Raj Sarraf 
Changed-By: Ritesh Raj Sarraf 
Description:
 iio-sensor-proxy - IIO sensors to D-Bus proxy
Closes: 852597
Changes:
 iio-sensor-proxy (2.0-3) unstable; urgency=medium
 .
   * [827854b] Enable integration with systemd.
 Thanks to Julien Cristau (Closes: #852597)
Checksums-Sha1:
 f9e9d71a21887e7e3f8750eaf95f32719264f0c2 2036 iio-sensor-proxy_2.0-3.dsc
 172d063e1413292383e6cc06ff4c102f48e42ea3 4060 
iio-sensor-proxy_2.0-3.debian.tar.xz
 c48c50023664de68fe07d2c1cf528633389ebe74 75168 
iio-sensor-proxy-dbgsym_2.0-3_amd64.deb
 49549c6d91ee3a579abb884663c212036706fd94 12582 
iio-sensor-proxy_2.0-3_amd64.buildinfo
 5ec917e91b42647335f858186592a636a8ca948c 25306 iio-sensor-proxy_2.0-3_amd64.deb
Checksums-Sha256:
 9b64b476c439ac514ba0a3edfc71f71c3eac0817b07ca33969a9fcaa54b8287b 2036 
iio-sensor-proxy_2.0-3.dsc
 8f0e114a0191f09b217836c207efaa257c367b6ca430b2a59d9b4c285c4b911a 4060 
iio-sensor-proxy_2.0-3.debian.tar.xz
 9372f91b8f58d574905a3bf9e61eb7b36a7feaabb9cecd215facc1a36e0bf6aa 75168 
iio-sensor-proxy-dbgsym_2.0-3_amd64.deb
 4ca071fd8b45b5f2fa8c754a81b2dc68849358f14dd264fbd9d5b3dac0c5f59a 12582 
iio-sensor-proxy_2.0-3_amd64.buildinfo
 63e7fd1c21a8e190f0995f4015e63ebaa8f3a1c7e615dfcb7808d69035947ef0 25306 
iio-sensor-proxy_2.0-3_amd64.deb
Files:
 05dd68d6aab40e814c0f5acdbdc323b4 2036 utils optional iio-sensor-proxy_2.0-3.dsc
 8945f8deea5608c79b8800be7bdd1c7d 4060 utils optional 
iio-sensor-proxy_2.0-3.debian.tar.xz
 57512f00b96b658e5aac66b4b68f44f3 75168 debug extra 
iio-sensor-proxy-dbgsym_2.0-3_amd64.deb
 8909c92f2780f1aa075da4d207e41a80 12582 utils optional 
iio-sensor-proxy_2.0-3_amd64.buildinfo
 b4a345a005f10d2cd413c01750cebba7 25306 utils optional 
iio-sensor-proxy_2.0-3_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEQCVDstmIVAB/Yn02pjpYo/LhdWkFAliI1ogACgkQpjpYo/Lh
dWlaCQ//WMKdpplFGeAKQKdrSpH+g4xOK9ekVvlcYObJAZyVjDXEEWXA48kw6tFT
rBo5Uva+0b+aTJGGex/tW3v6tPnScbW+Kh73nO07IwTEmi7vn5kJ2NsOa12mrRwq
fMLtNr5KsTKo5Z9zZLdHXqEUNLnAezfyejenlq4qEjXlyzG4Y/Ex+I8EsQjLccJX
S9bn/vizwAE7tdIu0GyoZQphEWP+ubZ4/ILJxdS3tZkPtTce1jFVpIng//mlPdwk
k3Llp+Xs8o4QDCcxl8dYOGQNScGUAX3kSqRLvpSM7YjphClUfu2jHP8TcwZxHkjs
XimkQNpuET38YjlprlQUBP1tFuYHpb8IpHG9g0hC1npgoD1oBkV4Gpdi1UkeXbzw
G2eP3kZaUUyi1T+1H1LhOnWZ+Gw0BudoLfHLTFnfkXgNDh6ovpCgeQmyTIM6WOwu
QEMXrRTUOdRtXRb+yQt02f2C3dd2P1+dKUEtYSbUE+4lqAz0/G7AD5H4rx4dzwGS
tU5qFm2cQNwz1hImHpHwq8Iggb3t3EYUDkJY7gODVwW9gczpz5N6LCrQFIZ/gSBh
mqT2eu9PSamYT3H7pPEdRaLBQWXP0Tatqj1g8Hv0loYjWL3fQk8/0IpSTbIT/IMI
A7MkufNK9CorB1m4X2zLgsZeQlXFkkXCvOVVXDllIFbWDNt7lVA=
=UZxP
-END PGP SIGNATURE End Message ---

Bug#852597: iio-sensor-proxy: process keeps running after package purge

[Ritesh Raj Sarraf]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On Wed, 2017-01-25 at 16:41 +0100, Michael Biebl wrote:
> > Dear Debian Systemd Team,
> > 
> > For a static service, upon package de-install, how do we ensure the service
> is
> > killed. Should this be done manually and individually in a package's prerm
> > script ?
> 
> Have a look at dh_systemd_start

Hello Michael,

Thank you very much for the quick reply, and the documentation done on the wiki.
With it, I seem to have been able to get a fix.

https://wiki.debian.org/Teams/pkg-systemd/Packaging?action=show=systemd%2FPackaging#Using_debhelper_with_dh_systemd


- -- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEQCVDstmIVAB/Yn02pjpYo/LhdWkFAliI2UoACgkQpjpYo/Lh
dWnfGQ//Zbjrxxw642aqafkXk2EpviVH/4sLTD1osh97nGyLn3OnulFvXdTjqrpz
f9RjmuxgIJzylW3Irkd7zrmHrN86KW7g5GZ91yFA1/4xtQvVjaGk2nW1LSDU4Ijt
oTdZrz2D5pYI6UGZrN7BwW6YUd4+zYzPqJ4B6T1zT8z5vqXXQgvKmLNZ6UEdgzkO
8PlZbFvQEum43Y4U9B3VCZnDpWmLb6aqb1P2o9i/IOE6fT43cWusioOeYfbyxnZj
fzZke7xnIRzkD4yk8jpVHC1MrfAoOwxIoVIkz7oTMbvVEYp+El686x0pUPlXoIYa
p0Aio+7PRhod3Anfn0mbjLLpYJkeSvsuwVgTHzaVNNA2OXCtdrvBdYn4m1b2pyaI
mBqoCPeXchlaMJTolQJxaKEy4x6WO0RnnsJCPc2I5j5kdHPzQNUHHMJziMIxJfVq
teaUlyj8CIkaSiP6J4O1pmpEFtDT80zlrUNcghlwT27Xd+8wZDWxRaZVphaplD9e
T2neSrIn/y7YuZmoADl1v4H0dE8Vc+Coj8nHJ0wfkJ67lCE9P3TUTYwCfGotQzTJ
ZxfNBE4tjeYGqH0IoUu4gO8gbJH+FAOgen3Q2RzNfsr2saVvD4fJB2qiX2u1szgn
5iGtSnCr8UdX8sWY8XquURwzy+Som20vMY/q/BjhMF0dKismGDA=
=UCQx
-END PGP SIGNATURE-

Bug#852597: iio-sensor-proxy: process keeps running after package purge

[Ritesh Raj Sarraf]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello Laurent,

On Wed, 2017-01-25 at 17:00 +0100, Laurent Bigonville wrote:
> Package: iio-sensor-proxy
> Followup-For: Bug #852597
> 
> Hi,
> 
> The patch attached here seems to do the job.

Thank you for the quick patch you provided. Appreciate you help. But it reached
me after I did the upload. :-)

There's a nice wiki howto for developers integrating systemd into their
packages.

https://wiki.debian.org/Teams/pkg-systemd/Packaging?action=show=systemd%2FPackaging#Using_debhelper_with_dh_systemd

That link was comprehensive enough. Thanks to the Debian Systemd team.


I was able to fix the bug just with the following changes, with dh-systemd. It
takes care of populating the installation scripts by itself.


diff --git a/debian/control b/debian/control
index a3e4ed2..6abdb98 100644
- --- a/debian/control
+++ b/debian/control
@@ -2,7 +2,7 @@ Source: iio-sensor-proxy
 Section: utils
 Priority: optional
 Maintainer: Ritesh Raj Sarraf 
- -Build-Depends: debhelper (>= 9.20120312), libgudev-1.0-dev, udev, systemd, 
gtk-
doc-tools (>= 1.0), libgtk-3-dev
+Build-Depends: debhelper (>= 9.20120312), libgudev-1.0-dev, udev, systemd, gtk-
doc-tools (>= 1.0), libgtk-3-dev, dh-systemd (>= 1.5)
 Standards-Version: 3.9.8
 Homepage: https://github.com/hadess/iio-sensor-proxy
 Vcs-Git: https://anonscm.debian.org/git/collab-maint/iio-sensor-proxy
diff --git a/debian/rules b/debian/rules
index 2086e2f..8ebdc52 100755
- --- a/debian/rules
+++ b/debian/rules
@@ -8,7 +8,7 @@ export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 export DH_OPTIONS
 
 %:
- -   dh $@ 
+   dh $@ --with systemd
 


- -- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEQCVDstmIVAB/Yn02pjpYo/LhdWkFAliI2OIACgkQpjpYo/Lh
dWkbkg/8DBIOIODw7cBZB0B7qT2+kD7moHDlrK1UHYueNFl2zzGwt1mO+01G17i1
5RFzSykrd40X5DmpYJNNzcxOAWeHso2Mkmdk83NDLF4N5ka3eDcFm4eQsyey63mN
N3BFfp4zb+nQRvnqCP4NaGZvvtUGIQCOqNSThs2IikjOSVWtb4MhjJVm49e4r/0X
6XQ/mrWvBJyOCIqJ5q6g7CKQvzgU8MWQ8eQZsqpzyQmCPvt/hEqUWBXIBPpKPF1H
OYExubOnafU29Nnln4BpctUBTaHWejyUzpYSeUI60rOyLwgyhd9k1nIwo5lt7oUE
U9FVE/1NPAL1ICY8le9OgUb6gVn9hMur/T0I/8AYQd+rviHyRd12pLbndhojx5tY
I0+luumNur63r6w4BRRbrx/8VbaSLTNhiDGTMX+bGwMyGSDYZRI20yBV5CZkhrKo
l91j/opwvWWaINCGnlwvDgTUembKYUQIdasJECKw/SzwHgZSQoSXQYeaFWpTYpVC
/REaZ33hSEnas/lAAVhAgiBsWzYGkxQkKUW2SC7d+A2G6lEA2bc/vUr6XIujFNcd
Z0coqkesDPDMLFbZNwnHrFbKYCYdQwracJ7HE4cSfRkC9Dx8LUlF8RF4323TZpEH
7oEELYjhGjM2ydwamHhKD71xRZF5u1vhkVk/q4RLFKl69MK4sLY=
=FpdQ
-END PGP SIGNATURE-

Bug#852516: marked as done (request-tracker4: prompting due to modified conffiles which were not modified by the user: /etc/request-tracker4/RT_SiteConfig.pm)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2017 16:09:27 +
with message-id 
and subject line Bug#852516: fixed in request-tracker4 4.4.1-3
has caused the Debian Bug report #852516,
regarding request-tracker4: prompting due to modified conffiles which were not 
modified by the user: /etc/request-tracker4/RT_SiteConfig.pm
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
852516: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: request-tracker4
Version: 4.4.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed the piuparts
upgrade test because dpkg detected a conffile as being modified and then
prompted the user for an action. As there is no user input, this fails.
But this is not the real problem, the real problem is that this prompt
shows up in the first place, as there was nobody modifying this conffile
at all, the package has just been installed and upgraded...

This is a violation of policy 10.7.3, see
https://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3,
which says "[These scripts handling conffiles] must not ask unnecessary
questions (particularly during upgrades), and must otherwise be good
citizens."

https://wiki.debian.org/DpkgConffileHandling should help with figuring
out how to do this properly.

In https://lists.debian.org/debian-devel/2009/08/msg00675.html and
followups it has been agreed that these bugs are to be filed with
severity serious.

This was observed during an upgrade from stretch to sid.

>From the attached log (scroll to the bottom...):

  Setting up request-tracker4 (4.4.1-2) ...
  
  Configuration file '/etc/request-tracker4/RT_SiteConfig.pm'
   ==> File on system created by you or by a script.
   ==> File also in package provided by package maintainer.
 What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
   The default action is to keep your current version.
  *** RT_SiteConfig.pm (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing 
package request-tracker4 (--configure):
   end of file on stdin at conffile prompt
  Processing triggers for libc-bin (2.24-9) ...
  Errors were encountered while processing:
   request-tracker4


cheers,

Andreas


request-tracker4_4.4.1-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: request-tracker4
Source-Version: 4.4.1-3

We believe that the bug you reported is fixed in the latest version of
request-tracker4, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 852...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dominic Hargreaves  (supplier of updated request-tracker4 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 25 Jan 2017 15:22:46 +
Source: request-tracker4
Binary: request-tracker4 rt4-clients rt4-standalone rt4-fcgi rt4-apache2 
rt4-db-postgresql rt4-db-mysql rt4-db-sqlite rt4-doc-html
Architecture: source
Version: 4.4.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Request Tracker Group 

Changed-By: Dominic Hargreaves 
Description:
 request-tracker4 - extensible trouble-ticket tracking system
 rt4-apache2 - Apache 2 specific files for request-tracker4
 rt4-clients - mail gateway and command-line interface to request-tracker4
 rt4-db-mysql - MySQL database backend for request-tracker4
 rt4-db-postgresql - PostgreSQL database backend for request-tracker4
 rt4-db-sqlite - SQLite database backend for request-tracker4
 rt4-doc-html - HTML documentation for request-tracker4
 rt4-fcgi   - External FastCGI support for request-tracker4
 rt4-standalone - Standalone web server support for request-tracker4
Closes: 852516 852522
Changes:
 request-tracker4 (4.4.1-3) unstable; 

Bug#852546: marked as done (bowtie2 build-depends on non-free libmath-random-perl)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2017 16:03:51 +
with message-id 
and subject line Bug#852546: fixed in bowtie2 2.3.0-2
has caused the Debian Bug report #852546,
regarding bowtie2 build-depends on non-free libmath-random-perl
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
852546: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852546
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bowtie2
Version: 2.3.0-1
Severity: serious


bowtie2 (2.3.0-1) unstable; urgency=medium
...
  [ Andreas Tille ]
...
  * Remove code from test suite that is requiring non-free package
libmath-random-perl
...
  [ Sascha Steinbiss ]
  * Even more new Build-Depends: libmath-random-perl, libtest-deep-perl
...
 -- Sascha Steinbiss   Sat, 14 Jan 2017 07:50:51 +
--- End Message ---
--- Begin Message ---
Source: bowtie2
Source-Version: 2.3.0-2

We believe that the bug you reported is fixed in the latest version of
bowtie2, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 852...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sascha Steinbiss  (supplier of updated bowtie2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 25 Jan 2017 16:27:13 +0100
Source: bowtie2
Binary: bowtie2 bowtie2-examples
Architecture: source
Version: 2.3.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Sascha Steinbiss 
Description:
 bowtie2- ultrafast memory-efficient short read aligner
 bowtie2-examples - Examples for bowtie2
Closes: 852546
Changes:
 bowtie2 (2.3.0-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Sascha Steinbiss ]
   * Skip tests involving simulated reads to avoid use of non-free build-dep
 libmath-random-perl again.
 Closes: #852546
   * Add libclone-perl build dependency.
 .
   [ Alexandre Mestiashvili ]
   * Add patch suppressing -Wmisleading-indentation warnings.
 .
   [ Steffen Moeller ]
   * Adjust EDAM annotations.
Checksums-Sha1:
 1f40af2a7852b8038e818b2886cba220e1ac93c9 2190 bowtie2_2.3.0-2.dsc
 840049ba9e3323dfded459f07b448b604c7e8f1f 12068 bowtie2_2.3.0-2.debian.tar.xz
Checksums-Sha256:
 3b54a946733d39ee23e7dcc8de651f334fde9307d9f2851b06ddc44f9323a5f0 2190 
bowtie2_2.3.0-2.dsc
 e83693ae4b6c3051e005be6569335aacae57d07b435b065af51aa0ab053acf99 12068 
bowtie2_2.3.0-2.debian.tar.xz
Files:
 0e41bdd3450221813702bb13e1225730 2190 science optional bowtie2_2.3.0-2.dsc
 ad6886dda649b64c40dcd8ccf6193b64 12068 science optional 
bowtie2_2.3.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEWzS6WqtVB+kDQm6F6NN64vCfSHIFAliIykUACgkQ6NN64vCf
SHKLRw//eFE/uQDN+vZm3LIeeYNk9Q8+dSGjg+5YbuYf54YXPjbRhGIn0Kvgz9E4
Tbk5oAVSIbvX9H8115XH1tr469n8iT4fDO7eJDe+fVEsHkNY/bcEZmKIYikIGAEd
5rP0fJWsqVgyAGfyERo77IVMIPiP/+owXMTQmkHB8buAy5ejpli+LEQdZGBN63R1
pJjaJvNzl2/MX8jytJEA8mfp4igz5fJN92+TwNpsiVj5OIxGAuBbVst/XjWYJTb8
gk78iIj6Ot9GBU2FDON1I5irhHqA4RPNMwr+I6EA46f0ROD09sUt2TEd8A61uVJW
q/9HvW3Shx1nB2byipLvUtXSKUWi14BTUhkQb+js6RTUumeroB0/SNj0QcyqAUOv
d/0NOgctSUG6XDG3rVWQbrMpjdKsf5ncax7QZtzXwOPUnVLtU74cKn4tDCFeMc4T
HuTS7yRRa7VVE578YF+EinzG1Il3qtq7k2rgWXydhjxdB/svWNMd5vRaYsyvBOyj
lBW/nEVqf9i0x0gdDkp8zYx6UO7u3w92KDWrQsJrEIlKnd7ayJLjRlFqk4dlx9Rq
AskP6M+0Jrft0swq3z2Bm5KwFEBg4PL57fFUn95GpQ0Mwyg4f8qw2PRj02irmbbd
PNp8euIIfioxdmzWHsOQW9BS8cYa2zK5rucpKwkIxsUN22IZBEk=
=KB7A
-END PGP SIGNATURE End Message ---

Processed: tagging 852597

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 852597 + patch
Bug #852597 [iio-sensor-proxy] iio-sensor-proxy: process keeps running after 
package purge
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
852597: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852597
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#852597: iio-sensor-proxy: process keeps running after package purge

[Laurent Bigonville]

Package: iio-sensor-proxy
Followup-For: Bug #852597

The patch...

-- System Information:
Debian Release: 9.0
  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.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages iio-sensor-proxy depends on:
ii  libc6   2.24-9
ii  libglib2.0-02.50.2-2
ii  libgudev-1.0-0  230-3
ii  systemd 232-14

iio-sensor-proxy recommends no packages.

iio-sensor-proxy suggests no packages.

-- no debconf information
diff -Nru iio-sensor-proxy-2.0/debian/changelog 
iio-sensor-proxy-2.0/debian/changelog
--- iio-sensor-proxy-2.0/debian/changelog   2016-12-21 18:02:51.0 
+0100
+++ iio-sensor-proxy-2.0/debian/changelog   2017-01-25 16:48:47.0 
+0100
@@ -1,3 +1,12 @@
+iio-sensor-proxy (2.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Mask and unmask iio-sensor-proxy service during upgrade to avoid dbus
+restarting the daemon at the wrong time, copied from ModemManager (Closes:
+#852597)
+
+ -- Laurent Bigonville   Wed, 25 Jan 2017 16:48:47 +0100
+
 iio-sensor-proxy (2.0-1) unstable; urgency=medium
 
   * [e44c466] New upstream version 2.0
diff -Nru iio-sensor-proxy-2.0/debian/control 
iio-sensor-proxy-2.0/debian/control
--- iio-sensor-proxy-2.0/debian/control 2016-12-20 19:23:53.0 +0100
+++ iio-sensor-proxy-2.0/debian/control 2017-01-25 16:11:00.0 +0100
@@ -2,7 +2,7 @@
 Section: utils
 Priority: optional
 Maintainer: Ritesh Raj Sarraf 
-Build-Depends: debhelper (>= 9.20120312), libgudev-1.0-dev, udev, systemd, 
gtk-doc-tools (>= 1.0), libgtk-3-dev
+Build-Depends: debhelper (>= 9.20160709), libgudev-1.0-dev, udev, systemd, 
gtk-doc-tools (>= 1.0), libgtk-3-dev
 Standards-Version: 3.9.8
 Homepage: https://github.com/hadess/iio-sensor-proxy
 Vcs-Git: https://anonscm.debian.org/git/collab-maint/iio-sensor-proxy
diff -Nru iio-sensor-proxy-2.0/debian/postrm iio-sensor-proxy-2.0/debian/postrm
--- iio-sensor-proxy-2.0/debian/postrm  1970-01-01 01:00:00.0 +0100
+++ iio-sensor-proxy-2.0/debian/postrm  2017-01-25 16:43:46.0 +0100
@@ -0,0 +1,9 @@
+#!/bin/sh
+set -e
+
+# drop the temporary mask from prerm
+if [ -d /run/systemd/system ] && [ "$1" = remove ]; then
+systemctl unmask --runtime iio-sensor-proxy.service
+fi
+
+#DEBHELPER#
diff -Nru iio-sensor-proxy-2.0/debian/prerm iio-sensor-proxy-2.0/debian/prerm
--- iio-sensor-proxy-2.0/debian/prerm   1970-01-01 01:00:00.0 +0100
+++ iio-sensor-proxy-2.0/debian/prerm   2017-01-25 16:44:40.0 +0100
@@ -0,0 +1,9 @@
+#!/bin/sh
+set -e
+
+# avoid cancelling of "stop" when D-BUS reactivates iio-sensor-proxy
+if [ -d /run/systemd/system ] && [ "$1" = remove ]; then
+systemctl mask --runtime iio-sensor-proxy.service
+fi
+
+#DEBHELPER#
diff -Nru iio-sensor-proxy-2.0/debian/rules iio-sensor-proxy-2.0/debian/rules
--- iio-sensor-proxy-2.0/debian/rules   2016-12-20 19:23:53.0 +0100
+++ iio-sensor-proxy-2.0/debian/rules   2017-01-25 16:48:07.0 +0100
@@ -8,7 +8,10 @@
 export DH_OPTIONS
 
 %:
-   dh $@ 
+   dh $@  --with systemd
+
+override_dh_systemd_start:
+   dh_systemd_start --no-start --no-restart-on-upgrade
 
 #override_dh_auto_configure:
 #  ./autogen.sh --prefix=/ --exec-prefix=/usr

Bug#852597: iio-sensor-proxy: process keeps running after package purge

[Laurent Bigonville]

Package: iio-sensor-proxy
Followup-For: Bug #852597

Hi,

The patch attached here seems to do the job.

Cheers,

Laurent Bigonville

-- System Information:
Debian Release: 9.0
  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.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages iio-sensor-proxy depends on:
ii  libc6   2.24-9
ii  libglib2.0-02.50.2-2
ii  libgudev-1.0-0  230-3
ii  systemd 232-14

iio-sensor-proxy recommends no packages.

iio-sensor-proxy suggests no packages.

-- no debconf information

Processed: limit source to request-tracker4, tagging 852522, tagging 852516

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> limit source request-tracker4
Limiting to bugs with field 'source' containing at least one of 
'request-tracker4'
Limit currently set to 'source':'request-tracker4'

> tags 852522 + pending
Bug #852522 [request-tracker4] request-tracker4: contains conflicts/replaces 
with wrong package name rt4-authen-externalauth
Added tag(s) pending.
> tags 852516 + pending
Bug #852516 [request-tracker4] request-tracker4: prompting due to modified 
conffiles which were not modified by the user: 
/etc/request-tracker4/RT_SiteConfig.pm
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
852516: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852516
852522: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852522
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#852597: iio-sensor-proxy: process keeps running after package purge

[Michael Biebl]

Am 25.01.2017 um 16:27 schrieb Ritesh Raj Sarraf:

> So a "static" service is:
> 
> The state will usually be "enabled", "disabled", "static", or "masked". In 
> this
> context, static means that the unit file does not contain an "install" 
> section,
> which is used to enable a unit. As such, these units cannot be enabled. 
> Usually,
> this means that the unit performs a one-off action or is used only as a
> dependency of another unit and should not be run by itself.

That's about enabling a service, i.e. dh_systemd_enable

> 
> Dear Debian Systemd Team,
> 
> For a static service, upon package de-install, how do we ensure the service is
> killed. Should this be done manually and individually in a package's prerm
> script ?

Have a look at dh_systemd_start


-- 
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#852374: marked as done (sagemath FTBFS on i386: recipe for target 'had-few-failures' failed)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2017 15:37:44 +
with message-id 
and subject line Bug#852374: fixed in sagemath 7.4-8
has caused the Debian Bug report #852374,
regarding sagemath FTBFS on i386: recipe for target 'had-few-failures' failed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
852374: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852374
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sagemath
Version: 7.4-7
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=sagemath=i386=7.4-7=1485112049=0

...
--
sage -t --long 
src/sage/schemes/hyperelliptic_curves/hyperelliptic_finite_field.py  # 1 
doctest failed
sage -t --long src/sage/plot/plot.py  # 1 doctest failed
sage -t --long src/sage/tests/cmdline.py  # 4 doctests failed
sage -t --long src/sage/coding/linear_code.py  # 3 doctests failed
sage -t --long src/sage/plot/arrow.py  # 1 doctest failed
sage -t --long src/sage/misc/cython.py  # 2 doctests failed
sage -t --long src/sage/rings/integer.pyx  # 1 doctest failed
sage -t --long src/sage/interfaces/maxima.py  # 1 doctest failed
sage -t --long src/sage/tests/french_book/recequadiff.py  # 2 doctests failed
sage -t --long src/sage/misc/randstate.pyx  # 13 doctests failed
sage -t --long src/sage/interfaces/r.py  # 2 doctests failed
sage -t --long src/sage/gsl/probability_distribution.pyx  # 1 doctest failed
sage -t --long src/sage/coding/codecan/autgroup_can_label.pyx  # 1 doctest 
failed
sage -t --long src/sage/algebras/group_algebra.py  # 2 doctests failed
sage -t --long src/sage/libs/libecm.pyx  # 1 doctest failed
sage -t --long src/sage/numerical/optimize.py  # 1 doctest failed
sage -t --long src/sage/libs/singular/function.pyx  # 2 doctests failed
sage -t --long src/sage/groups/matrix_gps/matrix_group.py  # 1 doctest failed
sage -t --long src/sage/geometry/polyhedron/backend_cdd.py  # 1 doctest failed
sage -t --long src/sage/rings/number_field/number_field_element.pyx  # 1 
doctest failed
sage -t --long src/sage/functions/wigner.py  # Timed out (and interrupt failed)
--
Total time for all tests: 7560.0 seconds
cpu time: 2648.0 seconds
cumulative wall time: 2811.0 seconds
make[2]: Entering directory '/«PKGBUILDDIR»'
debian/rules:130: recipe for target 'had-few-failures' failed
make[2]: *** [had-few-failures] Error 1
--- End Message ---
--- Begin Message ---
Source: sagemath
Source-Version: 7.4-8

We believe that the bug you reported is fixed in the latest version of
sagemath, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 852...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ximin Luo  (supplier of updated sagemath package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 25 Jan 2017 16:08:28 +0100
Source: sagemath
Binary: sagemath sagemath-common sagemath-jupyter sagemath-doc-hu 
sagemath-doc-it sagemath-doc-fr sagemath-doc-ca sagemath-doc-en sagemath-doc-tr 
sagemath-doc-pt sagemath-doc-es sagemath-doc-de sagemath-doc-ja sagemath-doc-ru
Architecture: source
Version: 7.4-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Ximin Luo 
Description:
 sagemath   - Open Source Mathematical Software
 sagemath-common - Open Source Mathematical Software - architecture-independent 
file
 sagemath-doc-ca - Open Source Mathematical Software - documentation (Catalan; 
Valen
 sagemath-doc-de - Open Source Mathematical Software - documentation (German)
 sagemath-doc-en - Open Source Mathematical Software - documentation (English)
 sagemath-doc-es - Open Source Mathematical Software - documentation (Spanish; 
Casti
 sagemath-doc-fr - Open Source Mathematical Software - documentation (French)
 sagemath-doc-hu - Open Source Mathematical Software - documentation (Hungarian)
 sagemath-doc-it - Open Source Mathematical Software - documentation (Italian)
 sagemath-doc-ja - Open 

Bug#734385: marked as done (cardstories: Package installation fails if /etc/apache2/conf.d does not exist)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2017 15:29:41 +
with message-id 
and subject line Bug#852541: Removed package(s) from unstable
has caused the Debian Bug report #734385,
regarding cardstories: Package installation fails if /etc/apache2/conf.d does 
not exist
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
734385: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734385
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cardstories
Version: 1.0.6-1.3
Severity: grave
Justification: renders package unusable

I installed the game.

Package configuration asked me which http server to use, and I selected apache.

Installation failed with message:

Configuring cardstories (1.0.6-1.3) ...
ln: failed to create symbolic link «/etc/apache2/conf.d/cardstories.conf»: No
such file or directory
dpkg: error processing package cardstories (--configure):

The package could be installed by manually create the directory
/etc/apache2/conf.d , but I think that directory should not exist.



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

Kernel: Linux 3.11-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages cardstories depends on:
ii  adduser3.113+nmu3
ii  apache2-bin [httpd]2.4.6-3
ii  debconf [debconf-2.0]  1.5.52
ii  python 2.7.5-5
ii  python-lxml3.2.0-1+b1
ii  python-openssl 0.13-2.1
ii  python-twisted-conch   1:13.1.0-1
ii  python-twisted-mail13.1.0-1
ii  python-twisted-web 13.1.0-1

cardstories recommends no packages.

cardstories suggests no packages.

-- debconf information:
* cardstories/reconfigure-webserver: apache2
--- End Message ---
--- Begin Message ---
Version: 1.0.6-2+rm

Dear submitter,

as the package cardstories has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/852541

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#753195: marked as done (cardstories: FTBFS: make[3]: virtualenv: Command not found)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2017 15:29:41 +
with message-id 
and subject line Bug#852541: Removed package(s) from unstable
has caused the Debian Bug report #753195,
regarding cardstories: FTBFS: make[3]: virtualenv: Command not found
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
753195: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753195
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cardstories
Version: 1.0.6-1.3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140628 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[3]: Entering directory '/«PKGBUILDDIR»'
> virtualenv spritemapper
> make[3]: virtualenv: Command not found
> maintain.mk:25: recipe for target 'spritemapper/bin/spritemapper' failed
> make[3]: *** [spritemapper/bin/spritemapper] Error 127

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/06/28/cardstories_1.0.6-1.3_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Version: 1.0.6-2+rm

Dear submitter,

as the package cardstories has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/852541

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#735761: marked as done (cardstories: FTBFS: Tries to write outside build dir)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2017 15:29:41 +
with message-id 
and subject line Bug#852541: Removed package(s) from unstable
has caused the Debian Bug report #735761,
regarding cardstories: FTBFS: Tries to write outside build dir
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
735761: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735761
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cardstories
Version: 1.0.6-1.3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140114 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[3]: Entering directory `/«PKGBUILDDIR»'
> virtualenv spritemapper
> New python executable in spritemapper/bin/python
> Installing setuptools, pip...
>   Complete output from command /build/cardstories-g...itemapper/bin/python -c 
> "import sys, pip; pip...ll\"] + sys.argv[1:])" setuptools pip:
>   Traceback (most recent call last):
>   File "", line 1, in 
>   File 
> "/usr/share/python-virtualenv/pip-1.5-py2.py3-none-any.whl/pip/__init__.py", 
> line 11, in 
>   File 
> "/usr/share/python-virtualenv/pip-1.5-py2.py3-none-any.whl/pip/vcs/subversion.py",
>  line 4, in 
>   File 
> "/usr/share/python-virtualenv/pip-1.5-py2.py3-none-any.whl/pip/index.py", 
> line 16, in 
>   File 
> "/usr/share/python-virtualenv/pip-1.5-py2.py3-none-any.whl/pip/wheel.py", 
> line 23, in 
>   File 
> "/usr/share/python-virtualenv/pip-1.5-py2.py3-none-any.whl/pip/_vendor/distlib/scripts.py",
>  line 15, in 
>   File 
> "/usr/share/python-virtualenv/pip-1.5-py2.py3-none-any.whl/pip/_vendor/distlib/resources.py",
>  line 105, in 
>   File 
> "/usr/share/python-virtualenv/pip-1.5-py2.py3-none-any.whl/pip/_vendor/distlib/resources.py",
>  line 40, in __init__
>   File 
> "/usr/share/python-virtualenv/pip-1.5-py2.py3-none-any.whl/pip/_vendor/distlib/util.py",
>  line 602, in get_cache_base
>   File "/«PKGBUILDDIR»/spritemapper/lib/python2.7/os.py", line 150, in 
> makedirs
> makedirs(head, mode)
>   File "/«PKGBUILDDIR»/spritemapper/lib/python2.7/os.py", line 157, in 
> makedirs
> mkdir(name, mode)
> OSError: [Errno 13] Permission denied: '/sbuild-nonexistent'
> 
> ...Installing setuptools, pip...done.
> Traceback (most recent call last):
>   File "/usr/bin/virtualenv", line 3, in 
> virtualenv.main()
>   File "/usr/lib/python2.7/dist-packages/virtualenv.py", line 821, in main
> symlink=options.symlink)
>   File "/usr/lib/python2.7/dist-packages/virtualenv.py", line 989, in 
> create_environment
> install_wheel(to_install, py_executable, search_dirs)
>   File "/usr/lib/python2.7/dist-packages/virtualenv.py", line 957, in 
> install_wheel
> 'PIP_NO_INDEX': '1'
>   File "/usr/lib/python2.7/dist-packages/virtualenv.py", line 899, in 
> call_subprocess
> % (cmd_desc, proc.returncode))
> OSError: Command /build/cardstories-g...itemapper/bin/python -c "import sys, 
> pip; pip...ll\"] + sys.argv[1:])" setuptools pip failed with error code 1
> make[3]: *** [spritemapper/bin/spritemapper] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/01/14/cardstories_1.0.6-1.3_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Version: 1.0.6-2+rm

Dear submitter,

as the package cardstories has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/852541

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#852597: iio-sensor-proxy: process keeps running after package purge

[Ritesh Raj Sarraf]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On Wed, 2017-01-25 at 20:05 +0530, Ritesh Raj Sarraf wrote:
> > I just purged iio-sensor-proxy, but:
> > 
> > $ ps 574
> >   PID TTY  STAT   TIME COMMAND
> >   574 ?    Ssl    4:10 /usr/sbin/iio-sensor-proxy
> > 
> > The process should stop running on removing the package.
> 
> Hmmm. The service is marked static and only operated through systemd.
> Let me check what the expectations are with a static service, and how systemd
> deals with service start/stop during package install/removal.
> 
> I've marked this report "help" because I'm not fully versed with the other
> supporting tools. If you can provide any help, that'll be nice.

So a "static" service is:

The state will usually be "enabled", "disabled", "static", or "masked". In this
context, static means that the unit file does not contain an "install" section,
which is used to enable a unit. As such, these units cannot be enabled. Usually,
this means that the unit performs a one-off action or is used only as a
dependency of another unit and should not be run by itself.


Dear Debian Systemd Team,

For a static service, upon package de-install, how do we ensure the service is
killed. Should this be done manually and individually in a package's prerm
script ?


- -- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEQCVDstmIVAB/Yn02pjpYo/LhdWkFAliIw84ACgkQpjpYo/Lh
dWlLwhAAtikvOsCUPtwrZxd/F6+tyRCJE+R4s4uZ1S8KLLFKtCRYmm008BJidvGO
Td9IqgmVYnuQkIPaN70V9R0tC+fBNad4u8pWL2QjWqwrHvJbSliqrpImqlIQqZQM
y5GoUzXj+lx9xa6Yv/7/XdXB7TK1+ms5JUaTJJH+xkXX2AMmCGwbX+mFt1s1676Z
z3/nQbS4Me6Q94vn64AeEWWTKwtyx+SN+Gg7Zyr8GNMIcoGuhVeP0y9Qei9DcH6P
ynof5uI87ZXi6Qui5Bn7p2GsXhuvsO1I3wDw6IR2pVzwUX8LP3clhygUFbIceHKp
Bezx0QhvcSB/P5tUdDhKNUkkaBqm9Ix6BO4lmWACOtckitRVxKERQaPs18P56XOH
EIxswi+3BDN8alSXMdPrZbffEPbPAzcAAoKxWw6YMExYr7J+gw0PgcTOildcOzJS
b/dH1Af5uEKS9UEpkcjR0MizNX4HZ0pnx+E8YEtDrl98TmEbwNqvCXQQZStleJPG
DTgr02raku+onbAaPb5ylLoa6cnjomxfcaCYh4gPktXAxSaAh2CF502j1GLSHIXc
mkqKKKi9BRcG6+XEM2mvjHSGIJlpJqBrvEZ13TZ16TlSPZySOPY9dtT058SJQL/i
2yEa0oaHpHldKs+xnMP5AoMcUuy1M2ShY1CxBChDRkEj015GOUw=
=hBvS
-END PGP SIGNATURE-

Processed: Set astroplan bug forwarded

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 851437 https://github.com/astropy/astroplan/issues/282
Bug #851437 [src:astroplan] astroplan: FTBFS (requires Internet to build)
Set Bug forwarded-to-address to 
'https://github.com/astropy/astroplan/issues/282'.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
851437: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851437
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#794316: several bug reports involving inability to unlock desktop

[Simon McVittie]

This bug report seems to be mixing up several distinct situations that
all have the common symptom "I can't unlock the screen shield".
That makes it much less likely that any of them will get solved, so I'm
trying to disentangle them.

When reporting bugs against a commonly-used component, please try to
make the subject line as specific as possible (for instance mentioning a
distinctive log message) - otherwise we get followups from users who see
vaguely similar symptoms for different reasons, and it all gets horribly
mixed up.

On Sat, 01 Aug 2015 at 11:01:31 +0200, Daniel Pocock wrote:
> My laptop screen had been locked for a while.  I typed the password and
> nothing happened.  After a few seconds, the screen went blank again.
> 
> Looking at journalctl I observed:
> 
> gdm-session-worker[23803]: <5>AccountsService: Failed to monitor logind
> session changes: Too many open files

I'm taking this to be the canonical description of #794316.
If this is your bug, please send any follow-up messages to
794...@bugs.debian.org only.

All the reports of this bug seem to be for Debian 8 'jessie' (gdm 3.14).
Has anyone seen *this specific bug* (not just similar symptoms)
with a later version? It might well have been fixed upstream in the 2
years of development since that version was released.

On Fri, 05 Feb 2016 at 11:56:36 +0200, Timo Juhani Lindfors wrote:
> I see this today too (gdm3 3.14.1-7 on amd64 Debian 8). strace shows
> 
> 3654  <... inotify_init1 resumed> ) = -1 EMFILE (Too many open files)

I think you have been seeing #794316, same as Daniel. See above.

On Sat, 09 Apr 2016 at 10:25:50 +, Ignacio G. Dupont wrote:
> I have noticed that gdm-session-worker instances occurs only on unsuccessful
> login attempts.
> 
> Once the fs.inotify.max_user_instances limit is reached /var/log/messages 
> shows
> error logs like:
> 
> Apr  7 10:05:25 jessie gdm-session-worker[3789]: <5>AccountsService: Failed to
> monitor logind session changes: Too many open files

I think you have been seeing #794316, same as Daniel. See above.

On Sun, 24 Apr 2016 at 10:50:28 -0700, Ray Dillinger wrote:
> I had an issue where login didn't work.
...
> Anyway, when I fixed the .profile error and rebooted, the problem with
> gdm refusing to start was gone.

You are seeing a separate issue: a syntax error in ~/.profile is treated
the same as a login session that instantly ends (because that's effectively
what it is). Please send any further messages on this subject to
852...@bugs.debian.org only.

On Tue, 21 Jun 2016 at 18:16:50 +0200, Quentin BUISSON-DEBON wrote:
> Same issue here but without the blank screen --> Just a freeze of gdm3 with 
> the
> login screen.

I think this is a third, different bug, which we are very unlikely to be
able to do anything about without more information (for example syslog
or Journal messages around the time of the freeze).
Please send any further messages regarding this one to
852...@bugs.debian.org only.

Both the reports of this bug seem to be for Debian 8 'jessie' (gdm 3.14).
Has anyone seen *this specific bug* (not just similar symptoms)
with a later version?

On Sat, 24 Sep 2016 at 14:55:08 +0200, Anonymous wrote:
> Similar/same problem here, with Jessie 8.6 / Gnome 3-3.14.1-7; the lock screen
> was unresponsive after the desktop was locked for some time.

I'm going to say this is the same bug as Quentin's, although "the lock
screen becomes unresponsive" isn't really much to go on.
Please send any further messages regarding this one to
852...@bugs.debian.org only.

Regards,
S

Processed: severity of 852603 is grave, severity of 852604 is grave

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 852603 grave
Bug #852603 [src:virglrenderer] virglrenderer: CVE-2016-10163
Severity set to 'grave' from 'important'
> severity 852604 grave
Bug #852604 [src:virglrenderer] virglrenderer: CVE-2017-5580
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
852603: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852603
852604: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852604
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: cloning 794316 ..., severity of -2 is normal, retitle -3 to lock screen becomes unresponsive ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> clone 794316 -2 -3
Bug #794316 [gdm3] can't unlock desktop
Bug 794316 cloned as bugs 852606-852607
> retitle 794316 can't unlock desktop: Too many open files (inotify fds leaked 
> on unsuccessful login)
Bug #794316 [gdm3] can't unlock desktop
Changed Bug title to 'can't unlock desktop: Too many open files (inotify fds 
leaked on unsuccessful login)' from 'can't unlock desktop'.
> retitle -2 syntax error in ~/.profile indistinguishable from other forms of 
> login failure
Bug #852606 [gdm3] can't unlock desktop
Changed Bug title to 'syntax error in ~/.profile indistinguishable from other 
forms of login failure' from 'can't unlock desktop'.
> severity -2 normal
Bug #852606 [gdm3] syntax error in ~/.profile indistinguishable from other 
forms of login failure
Severity set to 'normal' from 'serious'
> retitle -3 lock screen becomes unresponsive
Bug #852607 [gdm3] can't unlock desktop
Changed Bug title to 'lock screen becomes unresponsive' from 'can't unlock 
desktop'.
> severity -3 important
Bug #852607 [gdm3] lock screen becomes unresponsive
Severity set to 'important' from 'serious'
> tags -3 + moreinfo
Bug #852607 [gdm3] lock screen becomes unresponsive
Added tag(s) moreinfo.
> notfound 794316 3.18.0-2
Bug #794316 [gdm3] can't unlock desktop: Too many open files (inotify fds 
leaked on unsuccessful login)
No longer marked as found in versions gdm3/3.18.0-2.
> notfound -2 3.14.1-7
Bug #852606 [gdm3] syntax error in ~/.profile indistinguishable from other 
forms of login failure
No longer marked as found in versions gdm3/3.14.1-7.
> notfound -3 3.18.0-2
Bug #852607 [gdm3] lock screen becomes unresponsive
No longer marked as found in versions gdm3/3.18.0-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
794316: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794316
852606: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852606
852607: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852607
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: gnupg-agent: double-free in gpg-agent during heavily concurrent use

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 2.1.18-2
Bug #852608 [gnupg-agent] gnupg-agent: double-free in gpg-agent during heavily 
concurrent use
There is no source info for the package 'gnupg-agent' at version '2.1.18-2' 
with architecture ''
Unable to make a source version for version '2.1.18-2'
Marked as fixed in versions 2.1.18-2.

-- 
852608: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#852608: gnupg-agent: double-free in gpg-agent during heavily concurrent use

[Daniel Kahn Gillmor]

Package: gnupg-agent
Version: 2.1.17-2
Severity: grave
Justification: renders package unusable
Control: fixed -1 2.1.18-2

There is a crash in gpg-agent under heavily concurrent use.

See:

https://lists.gnupg.org/pipermail/gnupg-devel/2017-January/032499.html

This is reproducible on debian with:

export GNUPGHOME=$(mktemp -d)
gpg --passphrase abc123 --quick-gen-key t...@example.org
gpgconf --kill gpg-agent
gpg -d < test.asc ## give the agent the passphrase
gpg-connect-agent 'getinfo pid' /bye
for i in $(seq 1 20); do
   gpg2 -d < test.asc &
done
wait
gpg-connect-agent 'getinfo pid' /bye

It's fixed with the upload of 2.1.18-2.

 --dkg

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

Kernel: Linux 4.8.0-2-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 gnupg-agent depends on:
ii  libassuan0  2.4.3-2
ii  libc6   2.24-8
ii  libgcrypt20 1.7.5-2
ii  libgpg-error0   1.26-2
ii  libnpth01.3-1
ii  libreadline77.0-1
ii  pinentry-curses [pinentry]  1.0.0-1
ii  pinentry-gnome3 [pinentry]  1.0.0-1
ii  pinentry-gtk2 [pinentry]1.0.0-1
ii  pinentry-qt [pinentry]  1.0.0-1
ii  pinentry-tty [pinentry] 1.0.0-1

Versions of packages gnupg-agent recommends:
ii  gnupg  2.1.17-2
ii  gpgsm  2.1.17-2

Versions of packages gnupg-agent suggests:
ii  scdaemon  2.1.17-2

-- no debconf information

Bug#796609: fcoe-utils: Has init script in runlevel S but no matching service file

[Felipe Sateler]

Hello Sylvain Costard,

On 20 January 2017 at 09:10, Sylvain Costard
 wrote:
>
> Hello,
>
> Here is in attachment the latest patch we made for 
> fcoe-utils-1.0.29+git20140505 version for Debian.
>
> All is working and ifdown/ifup is no longer necessary to see hosts in 
> /sys/class/fc_host/

Thanks for your patch. This is a far larger patch than I'm comfortable
uploading as non-maintainer.  Jacob Luna Lundberg, Liang Guo, could
you please review and upload this patch? Apparently, fcow-utils as
currently packaged is not usable in debian. Sylvain Costard, Yann
Richard, maybe you are interested in helping maintain this package?


-- 

Saludos,
Felipe Sateler

Processed: Re: Bug#852557: Acknowledgement (bucklespring: FTBFS on non-linux architectures)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #852557 [src:bucklespring] bucklespring: FTBFS on non-linux architectures
Severity set to 'normal' from 'serious'

-- 
852557: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852557
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#852557: Acknowledgement (bucklespring: FTBFS on non-linux architectures)

[Dominik George]

Control: severity -1 normal

Not RC because no supported architectures.

-- 
PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17  FD26 B79A 3C16 A0C4 F296

Dominik George · Hundeshagenstr. 26 · 53225 Bonn
Mobile: +49-1520-1981389 · https://www.dominik-george.de/

Teckids e.V. · FrOSCon e.V.
Fellowship of the FSFE · Piratenpartei Deutschland
Opencaching Deutschland e.V. · Debian Maintainer

LPIC-3 Linux Enterprise Professional (Security)


signature.asc
Description: PGP signature

Processed: Re: Bug#852597: iio-sensor-proxy: process keeps running after package purge

[Debian Bug Tracking System]

Processing control commands:

> tag -1 help
Bug #852597 [iio-sensor-proxy] iio-sensor-proxy: process keeps running after 
package purge
Added tag(s) help.

-- 
852597: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852597
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#852597: iio-sensor-proxy: process keeps running after package purge

[Ritesh Raj Sarraf]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Control: tag -1 help

Hello

On Wed, 2017-01-25 at 14:59 +0100, Julien Cristau wrote:
> Package: iio-sensor-proxy
> Severity: serious
> Version: 2.0-1
> 

Is this severity justified ?


> I just purged iio-sensor-proxy, but:
> 
> $ ps 574
>   PID TTY  STAT   TIME COMMAND
>   574 ?    Ssl    4:10 /usr/sbin/iio-sensor-proxy
> 
> The process should stop running on removing the package.

Hmmm. The service is marked static and only operated through systemd.
Let me check what the expectations are with a static service, and how systemd
deals with service start/stop during package install/removal.

I've marked this report "help" because I'm not fully versed with the other
supporting tools. If you can provide any help, that'll be nice.

- -- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEQCVDstmIVAB/Yn02pjpYo/LhdWkFAliIt8gACgkQpjpYo/Lh
dWmKmg//cVb3zSKXG0Ep0CmkCJM8G3e1b6O8950npiSG2XiutIrZ2s9/0FnWuiRz
/dGEqLYSVz6zzXQ39HsiuAPaUyjAeH+8Z+31vwcnhHEdj3xGjS/uYi6RrXVr3Fvw
em5qHqC084fqKNkMZiUWSnb6j8kgWygtL32AZTGxtN9XyuIgL7+kfEWndGOAvbGS
QiKYAdtRFutuU+JPY5kR3fwT6Xuyclkjr8E9ee9lhtpp6+1ZnhBEXH9bW8HLg6Rf
cqqccMWxuCCmwYXe6f1Zs5QUHFOZvpIzGaFsaFCHCZNaLj2EQbQ7DtljlYNuIemT
ZMF7Dj9vvSo9Y7B5S2kuoT7oiwTU3gKSaEQbQQofW9NqTFU5ElpKI2q49Sl11BKZ
xqdA6Jp8zdF9A6gCKZ3TUP+Z+X3a7q/yUCyc4KXZ40/HIc4HsyNyb5YeXl2d4vIk
Bbi6I8KH7X/j2EWXdIDi5gSBJeF/XEzJiG7tPHcBTq5VMYvFoOSNQELFuPh1hR0y
or+xwOFbUVI9YJRDp01rM72gh5ttKCq2hOvBnbouowM9VDUScmb9YyTJ/zGXrSTw
6GHiIYtREgfVp3WfrN/emtRGrfHhbaN0dEg9bEEAjYw/6UBj1iT8SeP9CE5Bl8Zu
R1wMaTVC1FCAzx60CEvsH1wKhg6OiQf3tfniQymKL6+B8G4w7Go=
=xGCX
-END PGP SIGNATURE-

Bug#789118: Cannot unlock screen after upgrading GNOME if locked before upgrade

[Simon McVittie]

On Wed, 25 Jan 2017 at 12:52:13 +, Simon McVittie wrote:
> With that incompatibility out of the way, there's another one:
> 
> Jan 25 12:28:31 host gdm-session-worker.really[11355]: 
> pam_unix(gdm-password:auth): conversation failed
> Jan 25 12:28:31 host gdm-session-worker.really[11355]: 
> pam_unix(gdm-password:auth): auth could not identify password for [user]

I think this might be caused by gnome-shell raising an exception when
it fails to load an animation, with the traceback below, and the PAM
conversation not proceeding because gnome-shell is no longer talking
to the gdm-session-worker as a result of that exception.

> Jan 25 12:28:14 host gnome-session[5143]: (gnome-shell:5342): Gjs-WARNING 
> **: JS
>  ERROR: Exception in callback for signal: next: Error: can't convert 
> this._frame
>  to an integer
> Jan 25 12:28:14 host gnome-session[5143]: 
> Animation<._showFrame@resource:///org/
> gnome/shell/ui/animation.js:59
> Jan 25 12:28:14 host gnome-session[5143]: 
> wrapper@resource:///org/gnome/gjs/modules/lang.js:169
> Jan 25 12:28:14 host gnome-session[5143]: 
> Animation<.play@resource:///org/gnome/shell/ui/animation.js:34
> Jan 25 12:28:14 host gnome-session[5143]: 
> wrapper@resource:///org/gnome/gjs/modules/lang.js:169
> Jan 25 12:28:14 host gnome-session[5143]: 
> AuthPrompt<.setActorInDefaultButtonWell@resource:///org/gnome/shell/gdm/authPrompt.js:313
> Jan 25 12:28:14 host gnome-session[5143]: 
> wrapper@resource:///org/gnome/gjs/modules/lang.js:169
> Jan 25 12:28:14 host gnome-session[5143]: 
> AuthPrompt<.startSpinning@resource:///org/gnome/shell/gdm/authPrompt.js:329
> Jan 25 12:28:14 host gnome-session[5143]: 
> wrapper@resource:///org/gnome/gjs/modules/lang.js:169
> Jan 25 12:28:14 host gnome-session[5143]: 
> AuthPrompt<._init/<@resource:///org/gnome/shell/gdm/authPrompt.js:67
> Jan 25 12:28:14 host gnome-session[5143]: 
> _emit@resource:///org/gnome/gjs/modules/signals.js:124
> Jan 25 12:28:14 host gnome-session[5143]: 
> AuthPrompt<._initButtons/<@resource:///org/gnome/shell/gdm/authPrompt.js:191

That looks like https://bugzilla.redhat.com/show_bug.cgi?id=1350303
which is some sort of install-order issue, or possibly the existing
gnome-shell trying to use the old pixbuf loader cache that has been
invalidated in the meantime by upgrading.

There is a workaround for that bug in stretch's gnome-shell, added
by ;
but of course during a live upgrade we're still dealing with jessie's
gnome-shell, not stretch's, so we can't fix bugs.

S

Bug#852597: iio-sensor-proxy: process keeps running after package purge

[Julien Cristau]

Package: iio-sensor-proxy
Severity: serious
Version: 2.0-1

I just purged iio-sensor-proxy, but:

$ ps 574
  PID TTY  STAT   TIME COMMAND
  574 ?Ssl4:10 /usr/sbin/iio-sensor-proxy

The process should stop running on removing the package.

Cheers,
Julien

Bug#848287: marked as done (python-testing.mysqld: (build-)depends on mysql-{client,server})

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2017 13:51:18 +
with message-id 
and subject line Bug#848287: fixed in python-testing.mysqld 1.4.0-2
has caused the Debian Bug report #848287,
regarding python-testing.mysqld: (build-)depends on mysql-{client,server}
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
848287: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848287
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-testing.mysqld
Version: 1.4.0-1
Severity: serious

Your package (build-)depends on mysql-server/client. Since we're
transitioning to mariadb as the default mysql provider, you should
switch your build dependencies and dependencies to something like:

default-mysql-server | virtual-mysql-server, default-mysql-client | 
virtual-mysql-client

I have seen in your override that you have forwarded this upstream.
I am filing this anyway to keep track of this along with the rest of the
packages.

Cheers,
Emilio

Cheers,
Emilio

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

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: python-testing.mysqld
Source-Version: 1.4.0-2

We believe that the bug you reported is fixed in the latest version of
python-testing.mysqld, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 848...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dominik George  (supplier of updated python-testing.mysqld 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 25 Jan 2017 14:11:07 +0100
Source: python-testing.mysqld
Binary: python-testing.mysqld python3-testing.mysqld
Architecture: source
Version: 1.4.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Dominik George 
Description:
 python-testing.mysqld - Python testing.* framework - MySQLd helpers (Python 2)
 python3-testing.mysqld - Python testing.* framework - MySQL helpers (Python 3)
Closes: 848287
Changes:
 python-testing.mysqld (1.4.0-2) unstable; urgency=medium
 .
   * Build-Depend / Depend on default-mysql-server. (Closes: #848287)
 + Now works with MariaDB.
 + Does not depend on mysql-client anymore.
Checksums-Sha1:
 975fd3146bb848b457ee9ce0ee76089cc9708487 2646 python-testing.mysqld_1.4.0-2.dsc
 5a0dc61054ea0886c2b3dbdd0fa5a29ccb43afcb 4516 
python-testing.mysqld_1.4.0-2.debian.tar.xz
Checksums-Sha256:
 9263dff5785939f449d90f5b0b633d828c139ef9c87fcf318a0fff16680c71e1 2646 
python-testing.mysqld_1.4.0-2.dsc
 9abeaf7f8225ff6bfe0ff21ca35dba8aef72d2ae9004b2240768ed9d8e7b839c 4516 
python-testing.mysqld_1.4.0-2.debian.tar.xz
Files:
 3cabf457c47efdb637de725cf417bb44 2646 python optional 
python-testing.mysqld_1.4.0-2.dsc
 638eed6434f84227cde48d4b1ff29f07 4516 python optional 
python-testing.mysqld_1.4.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJlBAEBCABPFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAliIqLsxGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYwAKCRC3mjwW
oMTyljnTD/9rdvhTN84DBj2nObmSeIbRRAiaf60w5CoSIScs3faSYam5m5uV2KSM
wOObjJr7TMZbFoAYr7VGlJ7G99HaQY0swSfcpHOifQnxt7OziUhLMvhh4TfxaunF
s/Ad0M+CkwozB4nPwRF1VN+q7QP622J9ukb2Wtf4NNhxjY4oy1Hdjn6F5gHqrEbq
5czFcDfXTv5vspPJiWKwkqGwb0lbrKYoKCZqnj4w7As440PHyHPp+YK+SD0BiJTW
B+QtrZAojlb/i13DCVWX6FQd84rw/6eUzne0pxKolkC9SrsMdbWC3j9qjCtLB2q7
RKEc3fxvVAZiSDtE9eNxZ1pcXQXrzgvQ22DrTz/35AIZFez37W5wcXV9chfik/0m
G/F9jM8S0sHOde3SrCix5Z5yc4Fpjg3yqgV9he2fN0qiX3YMN7LHilmPcdA9G2Va
ituAMmQ5yCSNFTsUzfubKLOwqveGTQ6h94WUikdJhInT7dv15uXBgogfE2pxkPCG
lRwQlUINzPwMUWZM1p1iwHNCuRfWlvm/OWxT6YRtIh4YBKBK/qtPtW8x/1hS0b8d
TFwANPjc2cYKmLP/e5kvq9zO/15zRwcCOfTT4c5xuHmHdDDJ+MB29kMjVK5PIoDf

Bug#852557: bucklespring: FTBFS on non-linux architectures

[Dominik George]

Source: bucklespring
Version: 1.4.0-1
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
Control: forwarded -1 https://github.com/zevv/bucklespring/issues/44

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

bucklespring only implements the scan() function for Windows, macOS and
Linux, which means the package cannot build on non-linux architectures
in Debian:

gcc -o buckle  main.o scan-linux.o scan-windows.o scan-mac.o  -fPIE -pie 
-Wl,-z,relro -Wl,-z,now -g -lalure -lopenal -lXtst -lX11 
main.o: In function 
ain':
./main.c:143: undefined reference to can'
./main.c:109: undefined reference to en_console'
collect2: error: ld returned 1 exit status

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

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

-BEGIN PGP SIGNATURE-

iQJ4BAEBCABiFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAliIqxsxGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYxIcbmlrQG5h
dHVyYWxuZXQuZGUACgkQt5o8FqDE8pbgJQ/+O/PjLJByqdSR9BW30a31EXP6y8io
I/pslikalBgjxdq/+WwaJiQzOI+sr38tMxHqC02YyxK2MuKBVieIIgUc5sEu71Z2
rKIL2pKPXdKsHkqE4IUASCOlrKK4Y14lHe3WvA7RDuk1HTWKcbRyGoCjqoflZVaq
LlXk1WVdAIPkWSM4fR9O1NieQWcniu0F1iwtYd6W9tZIkhJnlG0+XYHLlpq+kUwN
6M+KSbwbG3b+UKdaq2wH+aCe3FINK4Ueu28iwdkgmK3C4laF9WWYZ09nDZ24yWUD
XLOIcoAuqqWsCftJQGAEY+cCNF3y9EjI8kFdcqEWV0pKRCoeECmteBQuPevRtWWK
IPeMp4UkF/pCTYiSD2lydfARk0c01IHSaOyfgZXuP1Y0uSK5PTEfqsjJWGDEKoPd
oKo20bn/wCgp9y9AlyPvDn5P6xMdt3+AORQ+TiTkMH1lOEfsKe0+83YujMpepB/M
cRJDKVH0CvtQ/ZbSW4l/F2ZfVuG8zPv3S8FhTvSPjzIAqZ5OUJYu6xzXckURR9m2
EKx7BH+lqsd0VJ5R8tWLQi+YJorcyexrfLYHehEtG4Vb5kFVn1ZvSvTrKpySMbdb
8oNNZFPg1QLeN6m2V7EEKf2bF0nqEncBfRakTSDcTaVuvanW7ETOiaZ7tJ8DdjZS
uDVgNqwsZhGoW9I=
=awqR
-END PGP SIGNATURE-

Processed: bucklespring: FTBFS on non-linux architectures

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/zevv/bucklespring/issues/44
Bug #852557 [src:bucklespring] bucklespring: FTBFS on non-linux architectures
Set Bug forwarded-to-address to 
'https://github.com/zevv/bucklespring/issues/44'.

-- 
852557: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852557
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Bug#848287 marked as pending

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 848287 pending
Bug #848287 [src:python-testing.mysqld] python-testing.mysqld: (build-)depends 
on mysql-{client,server}
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
848287: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848287
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#848287: marked as pending

[Dominik George]

tag 848287 pending
thanks

Hello,

Bug #848287 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


http://git.debian.org/?p=python-modules/packages/python-testing.mysqld.git;a=commitdiff;h=027f21f

---
commit 027f21f157c3af9601fd743430d151b5a2372001
Author: Dominik George 
Date:   Wed Jan 25 14:12:34 2017 +0100

dch -i.

diff --git a/debian/changelog b/debian/changelog
index b5247fb..fe1935f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+python-testing.mysqld (1.4.0-2) unstable; urgency=medium
+
+  * Build-Depend / Depend on default-mysql-server. (Closes: #848287)
++ Now works with MariaDB.
++ Does not depend on mysql-client anymore.
+
+ -- Dominik George   Wed, 25 Jan 2017 14:11:07 +0100
+
 python-testing.mysqld (1.4.0-1) unstable; urgency=low
 
   * Initial release. (Closes: #838581)

Bug#851437: astroplan: FTBFS (requires Internet to build)

[Ole Streicher]

There are quite a couple of problems, some of which are due to bugs in
astropy (namely #852550), and others already solved upstream:

https://github.com/astropy/astroplan/pull/273
https://github.com/astropy/astroplan/pull/274
https://github.com/astropy/astroplan/pull/281
https://github.com/astropy/astroplan/files/726302/diff.txt

The remaining problems are in test_transitioner,
test_priority_scheduler, test_sequential_scheduler:

__ test_transitioner ___
self = 
instance = <[ValueError("attribute obstime should be scalar or have shape (2, 
1), but is has shape (2,) and could not be broadcast.") raised in repr()] AltAz 
object at 0x7f8032fb2470>
frame_cls = 

def __get__(self, instance, frame_cls=None):
[...]
if instance is not None:
instance_shape = getattr(instance, 'shape', None)
if instance_shape is not None and (getattr(out, 'size', 1) > 1 and
   out.shape != instance_shape):
# If the shapes do not match, try broadcasting.
try:
if isinstance(out, ShapedLikeNDArray):
out = out._apply(np_broadcast_to, shape=instance_shape,
>subok=True)


[...]
/usr/lib/python3/dist-packages/numpy/lib/stride_tricks.py:174: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

array = array([ 2457424.5,  2457424.5]), shape = (2, 1), subok = True
readonly = True

def _broadcast_to(array, shape, subok, readonly):
[...]
broadcast = np.nditer(
(array,), flags=['multi_index', 'refs_ok', 'zerosize_ok'] + extras,
>   op_flags=[op_flag], itershape=shape, order='C').itviews[0]
E   ValueError: operands could not be broadcast together with remapped 
shapes [original->remapped]: (2,) and requested shape (2,1)

/usr/lib/python3/dist-packages/numpy/lib/stride_tricks.py:129: ValueError


It is unclear (to me) whether this is a problem in astroplan or in astropy.

Processed: Fixed in openmpi, so close the bug properly

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> notfound 842881 mpich/3.2-7
Bug #842881 {Done: Alastair McKinstry } [src:mpich] 
libmpich12: extraneous - and possibly wrong - symbolic link: 
/usr/lib/libmpich.so.12 -> libmpi.so
No longer marked as found in versions mpich/3.2-7.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
842881: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842881
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#852356: marked as done (ck builds with -sse2 on i386)

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2017 13:18:52 +
with message-id 
and subject line Bug#852356: fixed in ck 0.5.2-2.1
has caused the Debian Bug report #852356,
regarding ck builds with -sse2 on i386
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
852356: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852356
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ck
Version: 0.5.2-2
Severity: serious

https://sources.debian.net/src/ck/0.5.2-2/build/ck.build.x86/

On i386 software in Debian must run on machines that have
no SSE (and not even MMX).

Removing the "-msse -msse2" builds for me.
--- End Message ---
--- Begin Message ---
Source: ck
Source-Version: 0.5.2-2.1

We believe that the bug you reported is fixed in the latest version of
ck, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 852...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated ck package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 25 Jan 2017 11:49:02 +0200
Source: ck
Binary: libck0 libck-dev
Architecture: source
Version: 0.5.2-2.1
Distribution: unstable
Urgency: medium
Maintainer: Robert Edmonds 
Changed-By: Adrian Bunk 
Description:
 libck-dev  - Concurrency Kit - development files
 libck0 - Concurrency Kit - shared libraries
Closes: 852344 852356
Changes:
 ck (0.5.2-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Don't use SSE on i386. (Closes: #852356)
   * Configure with --platform to avoid bogus upstream guessing.
 (Closes: #852344)
Checksums-Sha1:
 59f0cf9617507e7042283a34213f00ab2b2542e3 1922 ck_0.5.2-2.1.dsc
 d3e44831ea9b6820a6e6fffe5144d430007365a2 3885 ck_0.5.2-2.1.debian.tar.gz
Checksums-Sha256:
 0d7a3d5dadedc5139cb7842782535ae25bf1387ebd7b4f8024d8900b5c909cd2 1922 
ck_0.5.2-2.1.dsc
 c1f1c6d2a1f94b7eb8cd1b28ac8045285fa87f72cfd8b33d0ad23046b2831077 3885 
ck_0.5.2-2.1.debian.tar.gz
Files:
 2ffd069bfc0a47531dd76ef4f5bc1d80 1922 libs optional ck_0.5.2-2.1.dsc
 7832422013df2160f6068c939c3895bf 3885 libs optional ck_0.5.2-2.1.debian.tar.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAliIoikACgkQiNJCh6LY
mLF/BQ/8DvIzLs9Mh5VvWMPik0dzFUIudKWeaOweKnI4UJULGFpaqU01PZfLWY1S
M4exh8fWKxcdztG4QmDlX828wmWAlSL9VNbaaLIewuqGCx5JOR+L8BNNgoObHxer
n4zZmUmbwRqjItUsHupLN5LahTYpewR+/LH2lhIzJbzhYEoe1HYSE2TeCUOf3Li1
ZPTKj7rOyUEvN/OPbveygae08S/MXS8wDKwzayT72TFaf9/SGL7bQZfS46q3/Xhx
xGnjqCszA2/kT+8dXVibNdgQqWdT69jBDsMkITKiJbeoM+9FUt/QpfqUC+HnsbJ+
M3SNUabIkcMPhjnT9bzm87zP9kVLNXniPn6z7I4cuCYguSxkIPLvyeMQBMzGYyca
boIQ4bVIzoJr9q/D7foGiEmEKo5RCh6zYDe6PPwxoBFA5j+uWl5yubekk64cfkDQ
h0M2WcjVO5mhiarqr4iVKA7vO3GC6cWHn9Gm3u1NQAi0W8d+NGYns/cvhCFMQi06
s8836MClSBRqLJvb0tYSuhNgg7pfncjBNW4/CXsahoJ1UR7Azm1pNmNlRMusisJu
SJUtj6m768fS2AsiSSWoXDYrf6ND6pRwd1NeBgg+jHLq6GOerway6PNoqd1sSzC4
QhlrWqhbVPYJTbRxpcDcnLLE3fAaYC4hRwFg9+Xg3G4TW6wvj8A=
=BhHi
-END PGP SIGNATURE End Message ---

Bug#852344: marked as done (ck: FTBFS on i386 (fatal error: sys/cdefs.h: No such file or directory))

[Debian Bug Tracking System]

Your message dated Wed, 25 Jan 2017 13:18:52 +
with message-id 
and subject line Bug#852344: fixed in ck 0.5.2-2.1
has caused the Debian Bug report #852344,
regarding ck: FTBFS on i386 (fatal error: sys/cdefs.h: No such file or 
directory)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
852344: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852344
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ck
Version: 0.5.2-2
Severity: serious
Justification: ftbfs
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs

Dear Maintainer,

ck fails to build from source in unstable and testing on i386:


In file included from /usr/include/limits.h:25:0,
 from /usr/lib/gcc/i686-linux-gnu/6/include-fixed/limits.h:168,
 from /usr/lib/gcc/i686-linux-gnu/6/include-fixed/syslimits.h:7,
 from /usr/lib/gcc/i686-linux-gnu/6/include-fixed/limits.h:34,
 from /build/1st/ck-0.5.2/include/ck_limits.h:47,
 from /build/1st/ck-0.5.2/include/spinlock/anderson.h:31,
 from /build/1st/ck-0.5.2/include/ck_spinlock.h:30,
 from /build/1st/ck-0.5.2/include/ck_barrier.h:31,
 from /build/1st/ck-0.5.2/src/ck_barrier_combining.c:28:
/usr/include/features.h:364:25: fatal error: sys/cdefs.h: No such file or 
directory
 #  include 
 ^
compilation terminated.

The full build log is attached.

(we could build it fine on amd64, armhf and arm64, as can be seen
on https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/ck.html )
)


-- 
cheers,
Holger
Mon Jan 23 13:22:41 UTC 2017  I: starting to build ck/unstable/i386 on 
jenkins.debian.net on '2017-01-23 13:22'
Mon Jan 23 13:22:41 UTC 2017  I: The jenkins build log is/was available at 
https://jenkins.debian.net/job/reproducible_builder_i386_24/7810/console
Mon Jan 23 13:22:42 UTC 2017  I: Downloading source for unstable/ck
--2017-01-23 13:22:50--  
http://ftp.de.debian.org/debian/pool/main/c/ck/ck_0.5.2-2.dsc
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:3128... connected.
Proxy request sent, awaiting response... 200 OK
Length: 1914 (1.9K)
Saving to: ‘ck_0.5.2-2.dsc’

 0K . 100%  160M=0s

2017-01-23 13:22:50 (160 MB/s) - ‘ck_0.5.2-2.dsc’ saved [1914/1914]

Mon Jan 23 13:22:50 UTC 2017  I: ck_0.5.2-2.dsc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 3.0 (quilt)
Source: ck
Binary: libck0, libck-dev
Architecture: amd64 arm64 armhf i386 ppc64el
Version: 0.5.2-2
Maintainer: Robert Edmonds 
Homepage: http://concurrencykit.org/
Standards-Version: 3.9.8
Vcs-Browser: https://anonscm.debian.org/cgit/collab-maint/ck.git
Vcs-Git: https://anonscm.debian.org/git/collab-maint/ck.git
Build-Depends: debhelper (>= 10)
Package-List:
 libck-dev deb libdevel optional arch=amd64,arm64,armhf,i386,ppc64el
 libck0 deb libs optional arch=amd64,arm64,armhf,i386,ppc64el
Checksums-Sha1:
 37772895660d29beab00bc81b3c4082eff7fa12f 209257 ck_0.5.2.orig.tar.gz
 548fc6c2dd83eee14936568c2eb5af6cbf49fb61 3371 ck_0.5.2-2.debian.tar.gz
Checksums-Sha256:
 7958c40d873a0846c22b5f718c598aa0a4a8da44edf76a5c6f5251aa19f5c681 209257 
ck_0.5.2.orig.tar.gz
 7281610e696e8e291c1c752a8ff0fa78b1882350767e6501d80ca25643e269a6 3371 
ck_0.5.2-2.debian.tar.gz
Files:
 637d0ff4f709ff579def8ded0141d07c 209257 ck_0.5.2.orig.tar.gz
 f30cb9d27878d310040b66515b9874e0 3371 ck_0.5.2-2.debian.tar.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE3z2W7rOCeCDzAmZcAYF6sKr2za4FAlhliRwACgkQAYF6sKr2
za7HXA/6A0yi4oS+JpbA4MWryYX0AjGJT9/VMz8+OVjWrhHHAVU+8eUKTioptsAY
auyBSBOwhMwgTRXxYst92mQW5kauws5bhis+C7zHkYw3ul5emrZ0NgOjjYylkZa2
pJDPRWyqbUE5+vOfGmIJKfyzZ31TbRsvpb4q6CjYed+J+HskmepnfnESXTnofC39
Vr9MEgCuRf2WYZi+edOh+Hs64lEYxW2UFFlWsj0p8LphuXhkqYGSqnelyUXpIll6
4/Jlk9kaxccbkzFPFgFqIYSlblGQoiC5k+nnhpK9/pi3k1rKJpgTW5lSJKbWVpZp
jw5xu3U/Trc9eDEWWIkzvH2q2IsHK5ZGU232imkcUXGrj6epuOk9jGWfA6ZWrjCu
Iv1qYRXVjoh3UHlu7heA5dga202OIJycAPwUcoUeuoWKxVwtG/iwld+w3QuiDsM+
HcEAjvEaeFJ0Xxayg60y0MhDWZZS8RR2qQAM3vGEpvqL1ymuXKRPPBZXJALQ9mpw
mPcbDZxtn2OXbREzfrYVyNNzTrwBu8q1cz/T93fi/6GmOhapFhIkl5jYEEVcSMgH
c3rrEdHwvJGDbh0daEeXR1COAqMs+doHM2ngfGrIUE4CSo/fN8rNuC7uKyDSx0xs
g5S2YrPv6L+i66wDzCwdbIx7E3r3KFMOpxUAsMhw3pJj8NOZYcU=
=aYJa
-END PGP SIGNATURE-
Mon Jan 23 13:22:50 UTC 2017  I: Checking whether the package is not for us
Mon Jan 23 13:22:50 UTC 2017  I: Starting 1st build on remote node 

Bug#840789: #840789: ruby-gettext: FTBFS: Error: test_relative ... undefined method `stub

[Santiago Vila]

reopen 840789
thanks

On Mon, 23 Jan 2017, Christian Hofstaedtler wrote:

> Hi Chris,
> 
> I've just tried to repro this in unstable today, but haven't been
> successful. I imagine a dependency change has fixed this. If you're
> still seeing this FTBFS, please reopen.

This is still happening, both here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-gettext.html

and also in my own autobuilders, so I'm reopening.

Thanks.

Processed: Re: #840789: ruby-gettext: FTBFS: Error: test_relative ... undefined method `stub

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reopen 840789
Bug #840789 {Done: Christian Hofstaedtler } [src:ruby-gettext] 
ruby-gettext: FTBFS: Error: test_relative(TestToolsXGetText::TestReference): 
NoMethodError: undefined method `stub' for 
#
Bug reopened
Ignoring request to alter fixed versions of bug #840789 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
840789: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840789
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#852552: ocserv: Build fail on arm patch inc

[Phillip Camp]

Package: ocserv
Version: 0.11.6-1~bpo8+1
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

build is failing for arm have tested this patch on armhf, on backported
package results in installable package, fails on other arms from
autobuild logs this may fix them aswell.

Keep up the hard work would be grateful if you could fix up the
backports etc.

Thanks

Phill.


--- ocserv-0.11.6.orig/debian/rules 2017-01-02 16:18:52.0 +
+++ ocserv-0.11.6/debian/rules  2017-01-25 12:31:01.117711166 +
@@ -14,6 +14,11 @@
OTHER_CONF_OPTS = --enable-systemd --enable-linux-namespaces
 #endif
 
+DEB_BUILD_ARCH_CPU = $(dpkg-architecture -qDEB_BUILD_ARCH_CPU)
+#ifeq ($(DEB_BUILD_ARCH_CPU),arm)
+   OTHER_CONF_OPTS = --enable-systemd --enable-linux-namespaces 
--disable-seccomp
+#endif
+
 %:
dh $@ --with systemd
 

-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux 8.0 (jessie)
Release:8.0
Codename:   jessie
Architecture: armv7l

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

Versions of packages ocserv depends on:
ii  dbus 1.8.22-0+deb8u1
ii  init-system-helpers  1.22
ii  libc62.19-18+deb8u7
ii  libev4   1:4.15-3
ii  libgnutls-deb0-283.3.8-6+deb8u4
ii  libgssapi-krb5-2 1.12.1+dfsg-19+deb8u2
ii  libhttp-parser2.12.1-2
ii  liblz4-1 0.0~r122-2
ii  libnettle4   2.7.1-5+deb8u2
ii  libnl-3-200  3.2.24-2
ii  libnl-route-3-2003.2.24-2
ii  liboath0 2.4.1-1
ii  libopts251:5.18.4-3
ii  libpam0g 1.1.8-3.1+deb8u2
ii  libpcl1  1.6-1
ii  libprotobuf-c1   1.0.2-1+b1
ii  libradcli4   1.2.6-3~bpo8+1
ii  libreadline6 6.3-8
ii  libsystemd0  215-17+deb8u6
ii  libtalloc2   2.1.2-0+deb8u1
ii  libtasn1-6   4.2-3+deb8u2
ii  libwrap0 7.6.q-25
ii  lsb-base 4.1+Debian13+rpi1+nmu1
ii  ssl-cert 1.0.35

Versions of packages ocserv recommends:
ii  ca-certificates  20141019+deb8u2

ocserv suggests no packages.

-- no debconf information

Bug#789118: Cannot unlock screen after upgrading GNOME if locked before upgrade

[Simon McVittie]

On Sun, 11 Oct 2015 at 15:48:10 -0700, Josh Triplett wrote:
> I just encountered this problem again, and in addition to the repeated
> authentication failure messages, I also saw a message on the lock screen
> matching this one I later found in logs:
> 
> gnome-session[551]: (gnome-shell:956): Gjs-WARNING **: JS ERROR: Failed to 
> start verification for user: Gio.DBusError: 
> GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: 
> GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Type of message, 
> '(sssb)', does not match expected type '(sssbb)'

This is really a gdm3 issue, which is why I've reassigned it there.
gnome-shell uses libgdm to communicate with a process called
gdm-session-worker, so that the actual authentication (PAM) can happen in
a privileged process. Unfortunately, the old gnome-shell will be using
jessie's libgdm, which expects a D-Bus API from jessie; and the
gdm-session-worker is started on-demand, so you got one that is using
stretch's libgdm, which expects a D-Bus API from stretch (with an extra
parameter).

It's possible to hack around this in stretch's gdm (patch attached),
but the best workaround I can see is still horrible, and so far I
haven't actually got unlocking to work again. With that
incompatibility out of the way, there's another one:

Jan 25 12:28:31 host gdm-session-worker.really[11355]: 
pam_unix(gdm-password:auth): conversation failed
Jan 25 12:28:31 host gdm-session-worker.really[11355]: 
pam_unix(gdm-password:auth): auth could not identify password for [user]

(gdm-session-worker.really is the real gdm-session-worker - I've used
dpkg-divert to inject more logging on my test system).

Possibly related, or perhaps just a side-effect of failing authentication:

Jan 25 12:28:14 host gnome-session[5143]: (gnome-shell:5342): Gjs-WARNING 
**: JS
 ERROR: Exception in callback for signal: next: Error: can't convert 
this._frame
 to an integer
Jan 25 12:28:14 host gnome-session[5143]: 
Animation<._showFrame@resource:///org/
gnome/shell/ui/animation.js:59
Jan 25 12:28:14 host gnome-session[5143]: 
wrapper@resource:///org/gnome/gjs/modules/lang.js:169
Jan 25 12:28:14 host gnome-session[5143]: 
Animation<.play@resource:///org/gnome/shell/ui/animation.js:34
Jan 25 12:28:14 host gnome-session[5143]: 
wrapper@resource:///org/gnome/gjs/modules/lang.js:169
Jan 25 12:28:14 host gnome-session[5143]: 
AuthPrompt<.setActorInDefaultButtonWell@resource:///org/gnome/shell/gdm/authPrompt.js:313
Jan 25 12:28:14 host gnome-session[5143]: 
wrapper@resource:///org/gnome/gjs/modules/lang.js:169
Jan 25 12:28:14 host gnome-session[5143]: 
AuthPrompt<.startSpinning@resource:///org/gnome/shell/gdm/authPrompt.js:329
Jan 25 12:28:14 host gnome-session[5143]: 
wrapper@resource:///org/gnome/gjs/modules/lang.js:169
Jan 25 12:28:14 host gnome-session[5143]: 
AuthPrompt<._init/<@resource:///org/gnome/shell/gdm/authPrompt.js:67
Jan 25 12:28:14 host gnome-session[5143]: 
_emit@resource:///org/gnome/gjs/modules/signals.js:124
Jan 25 12:28:14 host gnome-session[5143]: 
AuthPrompt<._initButtons/<@resource:///org/gnome/shell/gdm/authPrompt.js:191

I broadly agree with upstream on this issue: the more distribution
development I do, the less faith I have in our ability to support
in-place major upgrades, which change relatively fundamental things while
the OS is still fully active. We already don't actually restart gdm,
because that would terminate all user X/Wayland sessions, or dbus, because
that would terminate all D-Bus connections.

We can get away with in-place upgrades for stable updates, because they
already don't change very much, but for stable -> next-stable or for
testing/unstable, it's very easy to create a situation that can't work.

unattended-upgrades has an InstallOnShutdown mode, which is what SteamOS
uses (with some patches that I wrote a couple of years ago to improve it,
). systemd has systemd.offline-updates(7),
which PackageKit and GNOME Software can use.

S
Index: debian/changelog
===
--- debian/changelog	(revision 51941)
+++ debian/changelog	(working copy)
@@ -1,7 +1,16 @@
 gdm3 (3.22.1-2) UNRELEASED; urgency=medium
 
+  [ Michael Biebl ]
   * Stop setting authdir, has beend dropped upstream in favour of xauthdir.
 
+  [ Simon McVittie ]
+  * Add a non-upstreamable patch to edit D-Bus messages from libgdm
+to the session worker and adapt them from the pre-3.16 interface
+to the post-3.16 interface. Only do this if a flag file in /run
+has been created, so that this workaround will only be active
+until the next reboot.
+  * gdm3.preinst: Create that flag file on upgrades. (Closes: #789118)
+
  -- Michael Biebl   Mon, 17 Oct 2016 01:07:52 +0200
 
 gdm3 (3.22.1-1) unstable; urgency=medium
Index: debian/gdm3.preinst

Bug#852250: [lua-socket] luasocket was not compiled with UNIX sockets support

[Enrico Tassi]

On Wed, Jan 25, 2017 at 10:24:25AM +0100, Michael Meskes wrote:
> > Hopefully somebody is prepared to fix all rdepends.
> 
> Or better reverts the API change.

I gave a quick look at the problem.

I don't know why Mathieu packaged a new upstream snapshot exactly,
I hope it is not for the new unix.tcp/udp feature.  If so, reverting the
API change is as simple as reverting

  aa1b8cc9bc35e56de15eeb153c899e4c51de82a8

There is just a trivial conflict on the makefile.

Mathieu, does luasandbox need the new unix sockets?

Best,
-- 
Enrico Tassi