Bug#860360: [Okular] could not open pdf from context menu whether pdf file or path has accents

2017-04-14 Thread Máximo Ramírez
Package: Okular
Version: 4:16.08.2-1+b1
Severity: important

--- Please enter the report below this line. ---
When I tried to open pdf file via context menu: right click -> open with
-> okular. I get the error:

Could not open
/home/user00/Documents/Books/Física/Estadisticas/Fundamentals_of_Statistical_And_Thermal_Physics-F_Reif.pdf


But if I first open okular and then open the file through File -> Open
-> and select the same file. The file open fine.

--- System information. ---
Architecture:
Kernel: Linux 3.16.0-4-amd64

Debian Release: 9.0
500 testing httpredir.debian.org

--- Package information. ---
Depends (Version) | Installed
===-+-=
libokularcore7 (= 4:16.08.2-1+b1) | 4:16.08.2-1+b1
kde-runtime (>> 4:4.10) | 4:16.08.3-2
libc6 (>= 2.14) |
libfreetype6 (>= 2.2.1) |
libjpeg62-turbo (>= 1.3.1) |
libkdecore5 (>= 4:4.14) |
libkdeui5 (>= 4:4.14) |
libkexiv2-11 (>= 4:4.5.90) |
libkio5 (>= 4:4.14) |
libkparts4 (>= 4:4.14) |
libkprintutils4 (>= 4:4.14) |
libkpty4 (>= 4:4.14) |
libphonon4 (>= 4:4.6.0really4.3.80) |
libpoppler-qt4-4 (>= 0.38.0) |
libqca2 (>= 2.0.2) |
libqimageblitz4 (>= 1:0.0.4) |
libqmobipocket1 (>= 4:4.11.80) |
libqt4-dbus (>= 4:4.6.1) |
libqt4-declarative (>= 4:4.7.0~rc1) |
libqt4-svg (>= 4:4.5.3) |
libqt4-xml (>= 4:4.5.3) |
libqtcore4 (>= 4:4.8.0) |
libqtgui4 (>= 4:4.8.0) |
libsolid4 (>= 4:4.14) |
libspectre1 (>= 0.2.3) |
libstdc++6 (>= 5) |
phonon |
zlib1g (>= 1:1.1.4) |


Recommends (Version) | Installed
=-+-===
cups-bsd | 2.2.1-8


Suggests (Version) | Installed
-+-===
ghostscript | 9.20~dfsg-3
jovie |
okular-extra-backends (= 4:16.08.2-1+b1) | 4:16.08.2-1+b1
poppler-data | 0.4.7-8
texlive-binaries | 2016.20160513.41080.dfsg-2
unrar | 1:5.3.2-1
-- 
Sincerely,

Máximo Ramírez



signature.asc
Description: OpenPGP digital signature


Bug#860296: [Pkg-lirc-maint] Bug#860296: lirc is spamming syslog with messages

2017-04-14 Thread Alec Leamas



On 14/04/17 10:15, Hans-J. Ullrich wrote:



Sadly I have to tell, the latest version of lirc is spamming syslog with 
mwessages. To make sure, it is not a problem of an earlier configuration, I 
deinstalled it completely and reinstalled it new.

The message, which is spamming is the following:

Apr 11 20:28:22 localhost lircd-0.9.4c[8159]: Error: Cannot glob /sys/class/
rc/rc0/input[0-9]*/event[0-9]*
Apr 11 20:28:23 localhost lircd[8159]: lircd-0.9.4c[8159]: Error: Cannot glob
/sys/class/rc/rc0/input[0-9]*/event[0-9]*
Apr 11 20:28:23 localhost lircd-0.9.4c[8159]: Error: Cannot glob /sys/class/
rc/rc0/input[0-9]*/event[0-9]*
Apr 11 20:28:24 localhost lircd[8159]: lircd-0.9.4c[8159]: Error: Cannot glob
/sys/class/rc/rc0/input[0-9]*/event[0-9]*

and so on.

Note: Although I have no infrared hardware installed, this issue did not happen 
with earlier versions.
As a workaround, I had to deinstall the package for now.

It would be nice, if you could take an eye on it.


Hi, thanks for reporting!

I cannot see that lircd does anything wrong here. The basic message is 
that your lirc setup isn't properly configured, which is a simple fact 
if you don't have any IR hardware.  There are many options in this 
situation:


- You could uninstall lirc - and if you don't plan to use it it's 
certainly a sensible thing to do.
- You could disable lircd.socket and and lircd.service if you plan to 
use it later, leaving package in place.
- You could raise the loglevel in /etc/lirc/lirc_options.conf to mute 
the message, if you for some reason want to run lircd despite the 
message (but why?).
- Last but not least, you could try to configure lirc. In this case, the 
above message is indeed helpful in some situations.


So, my basic understanding is that this issue should be closed as 
not-a-bug.  I will close it unless there is more input.



Cheers!

--alec



Bug#860300: [Pkg-lirc-maint] Bug#860300: lircmd does not work

2017-04-14 Thread Alec Leamas



On 14/04/17 11:18, Bernd Schumacher wrote:


I want to use lircmd
After making sure that lirc works to control vdr and kodi, I configured lircmd 
in /etc/lirc/lirc_options.conf
[lircmd]
uinput  = True
nodaemon= False

After starting "systemctl start lircmd", lircmd started without option 
"--uinput".


How do you know that? Note that lircmd reads lirc_options.conf by 
itself, it's not that lirc_options.conf puts --uinput on the command line.



Because I was not able to control my X11 mouse pointer, I tried to add this 
option.
No matter if I tried on commandline by calling "/usr/sbin/lircmd --uinput",
> Apr 14 11:03:38 majestix lircd-0.9.4c[23887]: "lircmd.cpp":394: Bad 
file descriptor
> Apr 14 11:03:38 majestix lircd-0.9.4c[23887]: "lircmd.cpp":394: Bad 
file descriptor


I cannot reproduce this... something is missing. Could you please expand 
on what you did to get this message?


The code at line 394 tries to write to the /dev/uinput device, so it 
might be some problem with that.


Poking around with this I found another in lircmd though [1].

Cheers!

--alec

[1] https://sourceforge.net/p/lirc/tickets/283/



Bug#738063: nfs-kernel-server: option to disable NFSv4 in /etc/default/nfs-kernel-server not working properly

2017-04-14 Thread Ben Hutchings
On Fri, 2017-04-14 at 20:19 -0700, Nye Liu wrote:
> Is anyone maintaining this package?

Daniel Pocock has been doing a fair amount of work on it.

> Is it possible to put this patch into an NMU?

This bug report has severity 'normal', which does not justify an NMU. 
Also, as we are approaching the release of Debian 9 'stretch', even
updates by a maintainer should only fix important bugs.

Ben.

-- 
Ben Hutchings
Larkinson's Law: All laws are basically false.



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


Bug#860355:

2017-04-14 Thread Richard Allen
Thanks Paul. I will do so.


Bug#860351: Acknowledgement (manpage generation problem, version in the source, ...)

2017-04-14 Thread Osamu Aoki
Hi,

For manpage, this patch to upstream fix the problem.

diff --git a/imediff2-docbook.xml b/imediff2-docbook.xml
index 4f0eb14..32bf0a6 100644
--- a/imediff2-docbook.xml
+++ b/imediff2-docbook.xml
@@ -9,11 +9,15 @@
   
   imediff2">
   
+  
+  
 
   GNU">
 ]>
 
   
+
+
 
   
 



Bug#860355: general: archive.debian.org certificate expired

2017-04-14 Thread Richard Allen
Package: general
Severity: normal

Dear Maintainer,

   * What led up to the situation? - Attempting to access
https://archive.debian.net/etch/libc6
   * What exactly did you do (or not do) that was effective (or
 ineffective)? Attempted to access https://archive.debian.net/etch/libc6
using Chrome 57 on Debian Stretch
   * What was the outcome of this action? - Browser rejected out of date
certificate
   * What outcome did you expect instead? - Browser properly establishes chain
of trust.



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



Bug#860354: ITP: libjs-simplemde -- embeddable JavaScript Markdown editor

2017-04-14 Thread Michael Lustfield
Package: wnpp
Severity: wishlist
Owner: Michael Lustfield 

* Package name: libjs-simplemde
  Version : 1.11.2-1
  Upstream Author : 2015 Next Step Webs, Incp
* URL : https://github.com/NextStepWebs/simplemde-markdown-editor
* License : Expat
  Description : embeddable JavaScript Markdown editor
 This JavaScript library provides an embedded Markdown editor. This
 WYSIWYG-style editor allows users less familiar with the Markdown syntax
 to use familiar toolbar buttons and shortcuts. In addition, the syntax
 is rendered while editing to clearly show the expected result. This
 library also provides built-in automatic saving and spell checking.

This Go library is being packaged as a build dependency of gitea (a gogs fork).
There are a lot of build dependencies and I would love some help. If anyone is
interested in handling this package, please feel free to contact me!
-- 
Michael Lustfield


pgp2NLSnStops.pgp
Description: OpenPGP digital signature


Bug#738063: nfs-kernel-server: option to disable NFSv4 in /etc/default/nfs-kernel-server not working properly

2017-04-14 Thread Nye Liu
Is anyone maintaining this package?

Is it possible to put this patch into an NMU?



Bug#860353: pass: extraneous reencryptions

2017-04-14 Thread Gabriel Filion
Package: pass
Version: 1.6.5-4
Severity: normal

Hello,

Version 1.6.5 suffers from a small but irritating bug: some commands like init,
mv are calling a check for whether or not a file needs to be reencrypted. That
check has a bug that makes it always reencrypt files in certain circumstances.

The issue was already fixed upstream right before 1.7.1 was released this week.

I haven't looked at why the 1.7 package is marked as buggy in experimental, but
my concern is more for jessie and stretch which have versions 1.6.3 and 1.6.5,
respectively. Both are affected by this bug.

If I'm not mistaken 1.6.x is not maintained by upstream as a separate branch so
in order to fix the issue I guess we'd have to backport the patch ourselves.
Luckily it's an easy one-liner: commit a09d6685e609f9a11fa2b9b5904d39ef8966b3b7
in upstream repos.

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

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

Versions of packages pass depends on:
ii  gnupg   2.1.18-6
ii  gnupg2  2.1.18-6
ii  pwgen   2.07-1.1+b1
ii  tree1.7.0-5

Versions of packages pass recommends:
ii  git 1:2.11.0-2
ii  gnupg2  2.1.18-6
ii  xclip   0.12+svn84-4+b1

Versions of packages pass suggests:
ii  libxml-simple-perl  2.22-1
ii  perl5.24.1-2
ii  ruby1:2.3.3

-- no debconf information



Bug#816399: pass: Pass does not locate gpg secret key

2017-04-14 Thread Gabriel Filion
Paul,

When I migrated to gpg 2.1, I've had issues with "secret key not found"
errors. This was caused by the fact that pass had installed gnupg2 as a
dependency long ago but I was still using gpg 1.4 for a good while
before migrating, so there were indeed keys missing.

If this sounds like your current situation, you might want to try to
reimport your keys to gnupg2 with:

gpg --import ~/.gnupg/secring.gpg

before doing that, you can list files in ~/.gnupg/private-keys-v1.d/ .
each file is named after a "keygrip". You can show keygrips with:

gpg -k --with-keygrip y...@uid.tld

If that solves your issue, the bug was not with pass but rather an
incomplete migration to gnugp2. then you might want to get more
information about this migration and what you need to adjust in your
configuration to use gpg 2.

hope that helps!


p.s.: Thadeu: your issue seems rather quite different than the one
reported first. If your issue is still persisting you might want to
report it in a seperate bug report.



signature.asc
Description: OpenPGP digital signature


Bug#850905: closed by Zhou Mo <cdlumin...@gmail.com> (Bug#850905: fixed in fortune-zh 2.2)

2017-04-14 Thread Dingyuan Wang
The missing one should be 麕

在 2017年04月15日 04:03, Debian Bug Tracking System 写道:
> This is an automatic notification regarding your Bug report
> which was filed against the fortune-zh package:
> 
> #850905: Song100 has a lot of replacement characters
> 
> It has been closed by Zhou Mo .
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Zhou Mo 
>  by
> replying to this email.
> 
> 

-- 
Dingyuan Wang



signature.asc
Description: OpenPGP digital signature


Bug#858083: RFS: libbloom/1.4-2

2017-04-14 Thread Roger Shimizu
On Thu, Apr 13, 2017 at 2:09 AM, Boyuan Yang <073p...@gmail.com> wrote:
> Everyone in collab-maint group can set up a repo (including yourself). Anyway
> here it is:
>
> https://anonscm.debian.org/git/collab-maint/libbloom.git

Thanks!
I pushed all commits there. And latest release (-b mentors) starts to
use alioth as official Vcs.

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



Bug#860352: gnupg: cannot handle hkps keyservers

2017-04-14 Thread Norbert Preining
Package: gnupg
Version: 2.1.18-6
Severity: important

Hi,

this is a very similar case to #811146 which supposedly is resolved,
but it isn't:

Relevant ~/.gnupg/gpg.conf lines:

  keyserver hkps://hkps.pool.sks-keyservers.net
  keyserver-options no-honor-keyserver-url

Relevant ~/.gnupg/dirmngr.conf lines:

  hkp-cacert /usr/share/gnupg/sks-keyservers.netCA.pem

$ gpg --version
gpg (GnuPG) 2.1.18
...
$ dpkg -l gnupg
...
ii  gnupg   2.1.18-6 amd64GNU privacy guard 
- a free PGP replacement

Searching with dirmngr directly succeeds (see above bug report),
but gnupg fails with
General error
$ gpg -vvv --debug-level 10 --search-key 58E11BB1E414D9AD
gpg: using character set 'utf-8'
gpg: enabled debug flags: packet mpi crypto filter iobuf memory cache memstat 
trust ipc clock lookup extprog
gpg: DBG: [not enabled in the source] start
gpg: DBG: chan_3 <- # Home: /home/norbert/.gnupg
gpg: DBG: chan_3 <- # Config: /home/norbert/.gnupg/dirmngr.conf
gpg: DBG: chan_3 <- OK Dirmngr 2.1.18 at your service
gpg: DBG: connection to the dirmngr established
gpg: DBG: chan_3 -> GETINFO version
gpg: DBG: chan_3 <- D 2.1.18
gpg: DBG: chan_3 <- OK
gpg: DBG: chan_3 -> KEYSERVER --clear hkps://hkps.pool.sks-keyservers.net
gpg: DBG: chan_3 <- OK
gpg: DBG: chan_3 -> KS_SEARCH -- 58E11BB1E414D9AD
gpg: DBG: chan_3 <- ERR 1 General error 
gpg: error searching keyserver: General error
gpg: keyserver search failed: General error
gpg: DBG: chan_3 -> BYE
gpg: DBG: [not enabled in the source] stop
gpg: random usage: poolsize=600 mixed=0 polls=0/0 added=0/0
  outmix=0 getlvl1=0/0 getlvl2=0/0
gpg: secmem usage: 0/65536 bytes in 0 blocks
$

Thanks

Norbert

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

Kernel: Linux 4.10.0 (SMP w/8 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 depends on:
ii  gnupg-agent2.1.18-6
ii  libassuan0 2.4.3-2
ii  libbz2-1.0 1.0.6-8.1
ii  libc6  2.24-10
ii  libgcrypt201.7.6-1
ii  libgpg-error0  1.26-2
ii  libksba8   1.3.5-2
ii  libreadline7   7.0-2
ii  libsqlite3-0   3.16.2-3
ii  zlib1g 1:1.2.8.dfsg-5

Versions of packages gnupg recommends:
ii  dirmngr 2.1.18-6
ii  gnupg-l10n  2.1.18-6

Versions of packages gnupg suggests:
pn  parcimonie  
pn  xloadimage  

-- no debconf information



Bug#786791: re

2017-04-14 Thread Daur, Mary Lynn
I have a Contract for you worth US$5.2m, contact me now for more information.


Bug#860351: manpage generation problem, version in the source, ...

2017-04-14 Thread Osamu Aoki
Source: imediff2
Version: 1.1.2-3
Severity: minor

As I read carefully this source to fix #799865, I saw several
irregularities.

If you try to update manpage by editing imediff2-docbook.xml, the
generated imediff2.1 by the "make" invocation does not yield properly
formatted manpage:

| $ make imediff2.1
| xsltproc --novalid 
/usr/share/sgml/docbook/stylesheet/xsl/nwalsh/manpages/docbook.xsl 
imediff2-docbook.xml
| Note: meta source : no *info/productname or alternativeimediff2
| Note: meta source : see http://docbook.sf.net/el/productname   imediff2
| Note: meta source : no refentry/refmeta/refmiscinfo@class=source   imediff2
| Note: meta source : see http://docbook.sf.net/el/refmiscinfo   imediff2
| Note: meta version: no *info/productnumber or alternative  imediff2
| Note: meta version: see http://docbook.sf.net/el/productnumber imediff2
| Note: meta version: no refentry/refmeta/refmiscinfo@class=version  imediff2
| Note: meta version: see http://docbook.sf.net/el/refmiscinfo   imediff2
| Warn: meta source : no fallback for source, so inserted a fixmeimediff2
| Note: meta manual : no titled ancestor of refentry imediff2
| Note: meta manual : no refentry/refmeta/refmiscinfo@class=manual   imediff2
| Note: meta manual : see http://docbook.sf.net/el/refmiscinfo   imediff2
| Warn: meta manual : no fallback for manual, so inserted a fixmeimediff2
| Warn: AUTHOR sect.: no personblurb|contrib for Jarno Elonenimediff2
| Note: AUTHOR sect.: see http://docbook.sf.net/el/contrib   imediff2
| Note: AUTHOR sect.: see http://docbook.sf.net/el/personblurb   imediff2
| Note: Writing imediff2.1

Of course manual edit of imediff2.1 is one way for the work around, this
is not a nice situation.

Also, this source has "VERSION = '1.1.1'" in the imediff2 command
causing "imediff2 --version" while the upstream version of package is
imediff2 1.1.2 (2007-08-18 00:48)

This package list python-setuptools as Build-Depends, but I see no
setup.py in the upstream source?  Why?

I see 2 upstream BTS patch proposals, but no responses can be seen.
https://alioth.debian.org/tracker/index.php?func=detail=302985_id=30544=411376
https://alioth.debian.org/tracker/index.php?func=detail=305136_id=30544=411376

The SVN repo seems not used at all.  The last commit is before the last
tarball release

https://anonscm.debian.org/viewvc/imediff2/debian/changelog?sortby=date=down=log
Revision 22 - (view) (download) (annotate) - [select for diffs] 
Modified Sat Dec 23 14:19:05 2006 UTC (10 years, 3 months ago) by elonen

I wonder if it may be beneficial to start alioth collab-maint git
repository (or github if you like that) so fixing these issues as
upstream fix becomes more natural.

Who exactly is the upstream now? Jarno Elonen? Kevin Coyner?

Is there any better program out there which made the upstream loosing
interest?

I have been using this but wondering the situation... for how to contact
the upstream.

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

Kernel: Linux 4.10.0-rc6-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)

-- no debconf information



Bug#859805: Patch proposal

2017-04-14 Thread JC
Hi Scott,

Le ven. 14 avr. 2017 à 19:59, Scott Kitterman  a
écrit :

> Thanks for the patch.
> I still need to review the underlying issue.  I suspect it is user error.
> Scott K
>

Well, I was not sure myself, so I did install postfix into new jessie and
stretch VMs and I've seen myself the same differences between the
dynamicmaps.cf.

The thing is: when you upgrade, the file is already created and provisioned
with the map entries; but they are just not valid anymore with a stretch
postfix installation, since the pathnames changed from
/usr/lib/postfix/dict_XXX.so to postfix-XXX.so (notice the full path
removal _and_ the file name change).

I did compare the addmap function from the debian/functions file between
jessie and stretch and they _do_ differ in the map line generated.

So the map lines already there _do_ need to get updated, either by the user
itself (in such case we should announce it in a README.upgrade or
equivalent) or by Debian. My opinion here is that the postinst script could
manage this upgrade here without much "conffile" modification conflict. :-)


Bug#860248: librtmp1 built against GNUTLS results in Segfault when streaming to sources that use username and password authentication

2017-04-14 Thread James Cowgill
Hi,

On 13/04/17 14:53, Ken Rice wrote:
> Package: librtmp1
> Version: 2.4+20151223.gitfa8646d.1-1
> Severity: important
> 
> Dear Maintainer,
> 
> Compiling librtmp1 against GNUTLS results in a segfault in the library.
> 
> simple Test to duplicate
> avconv -i /PATH/TO/MEDIA.mp4 -f flv -c:a libvo_aacenc
> 'rtmp://URL.FOR.STREAM/MOUNT/POINT pubUser=USERNAME pubPasswd=PASSWORD
> flashver=FMLE/3.0'

Do you have a backtrace for this? How do you know librtmp is to blame
and not gnutls (or any other library)?

I assume that to reproduce this will require setting up some rtmp server
which requires authentication. Are there any existing servers this could
be tested against to avoid having to do that?

Note your test case won't work on stretch because ffmpeg doesn't use
librtmp anymore.

Thanks,
James



Bug#860142: libgeo-ip-perl: incompatible with geoip-database - cannot load

2017-04-14 Thread Norbert Preining
Hi Greg,

> Code:
> *record_by_addr = \_city_record_as_hash;

Ahh, well, didn't expect that. Sorry.

> This means that all functions that use the country .dat should work,
> and for the city-needing functions one would either need to get the

Thanks.

> - Geo::IP works with the geoip-database data as long as only the the
>   country data are used;

Agreed.

> - for functions which need the city data they have to be downloaded
>   manually or should be shipped in geoip-database;

Agreed.

> > I guess libgeo-ip-perl could do with a recommends on geoip-database
> > and geoip-database-extra (currently it only depends on libgeoip1
> > which recommends geoip-database).
> 
> Fixed in git, changing the bug metadata accordingly.

Thanks.

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13



Bug#859805: Patch proposal

2017-04-14 Thread Scott Kitterman
Thanks for the patch.

I still need to review the underlying issue.  I suspect it is user error.

Scott K



Bug#860335: linux: [armhf] ahci_mvebu module is missing from sata-modules udeb

2017-04-14 Thread Ben Hutchings
On Fri, 2017-04-14 at 13:06 -0400, Robert Edmonds wrote:
> Package: linux
> Version: 4.9.18-1
> Severity: normal
> Tags: d-i patch
> 
> Hi,
> 
> The sata-modules udeb on armhf is missing the "ahci_mvebu" module. This
> prevents, e.g., installing Debian to an mSATA SSD installed in a Marvell
> Armada 385 SoC based system like the Turris Omnia.
> 
> I was able to complete an install using the d-i stretch rc3 release
> after manually copying ahci_mvebu.ko to the running installer
> environment and modprobe'ing it, so I think the attached patch will fix
> this problem. (See #860286 for the installation report.)

Thanks for the patch, but I prefer to specify modules in a more general
way rather than building up long lists.  What I think we should do here
is to add all the ahci* modules to sata-modules (instead of just ahci).

Ben.

-- 
Ben Hutchings
I'm not a reverse psychological virus.  Please don't copy me into your
sig.



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


Bug#859935: Bug#860022: unblock: bsd-mailx/8.1.2-0.20160123cvs-3.1 (pre-approval)

2017-04-14 Thread Robert Luberda
Niels Thykier wrote:
> 
>  * Should we update some documentation to reflect these changes?  Like a
>man page or so?

I've updated man page and added NEWS entry. Attached is full debdiff.
Could you please look at it?

> 
> Re: 7-bit only.  You are right that would be even better in the long run
> as it would not require a 8bit compatible MTA unnecessarily.  Though
> that smells like a post release thing.

Yes, it surely will be too big change to do it now.

Thanks,
robert

Comparing bsd-mailx_8.1.2-0.20160123cvs-3.dsc 
bsd-mailx_8.1.2-0.20160123cvs-4.dsc
diff -Nru bsd-mailx-8.1.2-0.20160123cvs/debian/bsd-mailx.NEWS 
bsd-mailx-8.1.2-0.20160123cvs/debian/bsd-mailx.NEWS
--- bsd-mailx-8.1.2-0.20160123cvs/debian/bsd-mailx.NEWS 1970-01-01 
01:00:00.0 +0100
+++ bsd-mailx-8.1.2-0.20160123cvs/debian/bsd-mailx.NEWS 2017-04-15 
00:35:42.0 +0200
@@ -0,0 +1,10 @@
+bsd-mailx (8.1.2-0.20160123cvs-4) unstable; urgency=medium
+
+   Since this version MIME headers are added to every outgoing mail
+   to indicate the correct local charset (from the POSIX locale)
+   and transfer encoding (always 8bit).
+
+   See "Character sets and MIME" in bsd-mailx(1) man page
+   and Bug#859935 for more information.
+
+ -- Robert Luberda   Sat, 15 Apr 2017 00:11:27 +0200
diff -Nru bsd-mailx-8.1.2-0.20160123cvs/debian/changelog 
bsd-mailx-8.1.2-0.20160123cvs/debian/changelog
--- bsd-mailx-8.1.2-0.20160123cvs/debian/changelog  2016-05-07 
09:34:12.0 +0200
+++ bsd-mailx-8.1.2-0.20160123cvs/debian/changelog  2017-04-15 
00:35:42.0 +0200
@@ -1,3 +1,13 @@
+bsd-mailx (8.1.2-0.20160123cvs-4) unstable; urgency=medium
+
+  * 33-Add-MIME-headers.patch: Add MIME headers to every mail to indicate
+charset and transfer encoding (closes: #859935, LP: #733971), and
+describe the new behavior in the man page.
+Many thanks to Thorsten Glaser for the idea and the initial patch.
+  * Add debian/bsd-mailx.NEWS entry for the above change.
+
+ -- Robert Luberda   Sat, 15 Apr 2017 00:35:42 +0200
+
 bsd-mailx (8.1.2-0.20160123cvs-3) unstable; urgency=medium
 
   * Make the `-b' option work again: update 03-Base-fixes-2.patch to revert
diff -Nru 
bsd-mailx-8.1.2-0.20160123cvs/debian/patches/33-Add-MIME-headers.patch 
bsd-mailx-8.1.2-0.20160123cvs/debian/patches/33-Add-MIME-headers.patch
--- bsd-mailx-8.1.2-0.20160123cvs/debian/patches/33-Add-MIME-headers.patch  
1970-01-01 01:00:00.0 +0100
+++ bsd-mailx-8.1.2-0.20160123cvs/debian/patches/33-Add-MIME-headers.patch  
2017-04-15 00:35:42.0 +0200
@@ -0,0 +1,158 @@
+From: Robert Luberda 
+Date: Thu, 13 Apr 2017 23:39:39 +0200
+Subject: Add MIME headers unless set by user
+
+Generate the three following headers by default:
+  MIME-Version: 1.0
+  Content-Type: text/plain; charset=""
+  Content-Transfer-Encoding: 8bit
+
+However allow a user to override each of them with the -a flag.
+Example:
+   bsd-mailx -a "Content-Type: text/html; charset=UTF-8"
+uses the above user-provided Content-Type, but still adds
+the default MIME-Version and Content-Transfer-Encoding headers.
+
+Bugs-Debian: https://bugs.debian.org/859935
+---
+ mail.1 | 28 +++-
+ main.c |  4 
+ send.c | 43 +++
+ 3 files changed, 74 insertions(+), 1 deletion(-)
+
+diff --git a/mail.1 b/mail.1
+index b1bde8f..88949be 100644
+--- a/mail.1
 b/mail.1
+@@ -67,7 +67,13 @@ The options are as follows:
+ .Bl -tag -width Ds
+ .It Fl a
+ Specify additional header fields on the command line such as "X-Loop:
+-foo@bar" etc.  You have to use quotes if the string contains spaces.
++foo@bar" etc.
++It can be also used to override MIME headers
++.Nm mail
++adds by default to each outgoing mail, see
++.Sx Character sets and MIME
++below.
++You have to use quotes if the string contains spaces.
+ This argument may be specified more than once, the headers will then
+ be concatenated.
+ .It Fl b Ar bcc-addr
+@@ -366,6 +372,26 @@ If the
+ .Ic expandaddr
+ option is not set (the default), no expansion is performed and
+ the recipient is treated as a local or network mail address.
++.Ss Character sets and MIME
++Generally
++.Nm mail
++does not handle neither different character sets nor any other MIME
++feature.  Especially it does not perform any any conversions between
++character sets while displaying or sending mails.
++.Pp
++Starting from April 2017, however, as a Debian extension this version of
++.Nm mail
++adds a few MIME headers to every outgoing mail in order to indicate
++that the mail is sent as 8-bit plain text data that uses character
++set encoding detected from the current
++.Xr locale 7
++settings.
++The
++.Fl a
++command-line option can be used to override those headers, for example:
++.Dl $  mail -a 'Content-Type: text/plain; charset="ISO-8859-1"'
++sets header indicating legacy character encoding.
++.Pp
+ .Ss Network mail (ARPA, UUCP, Berknet)
+ See
+ .Xr 

Bug#740096: snapshot.debian.org: please enable HTTPS for https://snapshot.debian.org

2017-04-14 Thread Julien Muchembled
Control: severity -1 normal

Sorry for my stupid mistake with https://bugs.debian.org/860260
However, the arguments I gave there remain valid, so I allow myself to raise 
the severity of this bug. (I'd even add that I may not have done that mistake 
if it was HTTPS to beginning with.)



Bug#833697: diffoscope: libarchive.exception.ArchiveError when running on two dmg files

2017-04-14 Thread Chris Lamb
tags 833697 + pending
thanks

Should be fixed in Git :)

  
https://anonscm.debian.org/git/reproducible/diffoscope.git/commit/?id=82fbe27785f08d3623073eb98a3a4670b02fd2dc


Regards,

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



Bug#157299:

2017-04-14 Thread dejvis deivs


Odoslané z aplikácie Pošta pre 
Windows 10



Bug#860350: unblock (pre-approval): jenkins-debian-glue/0.18.2+deb9u1

2017-04-14 Thread Michael Prokop
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Hi,

asking for pre-approval of unblocking package jenkins-debian-glue.

In the current stretch version of jenkins-debian-glue (0.18.2) there
are two major bugs that should be fixed prior to release:

* dpkg-buildpackage might apply wrong defaults and then leaking the
  version control repository content (e.g. .git) through the
  generated tarball

* in binary only package builds the source package might get
  removed, which is neither expected nor wanted behavior
  (see https://github.com/mika/jenkins-debian-glue/issues/173)

Please let me know if this upload would be OK for you.

unblock jenkins-debian-glue/0.18.2+deb9u1

Debdiff at the end of the mail.

Thanks!

regards,
-mika-


diff -Nru jenkins-debian-glue-0.18.2/debian/changelog 
jenkins-debian-glue-0.18.2+deb9u1/debian/changelog
--- jenkins-debian-glue-0.18.2/debian/changelog 2017-01-24 22:13:48.0 
+0100
+++ jenkins-debian-glue-0.18.2+deb9u1/debian/changelog  2017-04-14 
22:48:41.0 +0200
@@ -1,3 +1,14 @@
+jenkins-debian-glue (0.18.2+deb9u1) unstable; urgency=medium
+
+  * [9492a4f] Support SKIP_SOURCE_REMOVAL to not remove source package in
+binary only package builds. Thanks to Antoine Delvaux
+ for the bugreport + initial patch
+  * [56563d7] Fix regression from commit 8fe677820fae2 to apply safe dpkg-
+buildpackage defaults. Thanks to Guillem Jover for feedback and code
+review
+
+ -- Michael Prokop   Fri, 14 Apr 2017 22:48:41 +0200
+
 jenkins-debian-glue (0.18.2) unstable; urgency=medium
 
   [ Will DeBerry ]
diff -Nru jenkins-debian-glue-0.18.2/scripts/build-and-provide-package 
jenkins-debian-glue-0.18.2+deb9u1/scripts/build-and-provide-package
--- jenkins-debian-glue-0.18.2/scripts/build-and-provide-package
2016-11-17 01:23:51.0 +0100
+++ jenkins-debian-glue-0.18.2+deb9u1/scripts/build-and-provide-package 
2017-04-14 22:47:49.0 +0200
@@ -451,6 +451,9 @@
 
 SKIP_ARCH_BUILD=false
 echo "*** Setting SKIP_ARCH_BUILD=$SKIP_ARCH_BUILD to skip further arch 
builds. ***"
+
+SKIP_SOURCE_REMOVAL=true
+echo "*** Setting SKIP_SOURCE_REMOVAL=$SKIP_SOURCE_REMOVAL to skip source 
removal in binary only build ***"
 return 0
   fi
 
@@ -474,6 +477,9 @@
   echo "*** Host architecture [${HOST_ARCH}] does not match \$architecture 
[${architecture:-}] ... ***"
   echo "*** ... setting binary only build and continuing with 
identify_build_type ***"
   DEBBUILDOPTS="-B"
+
+  SKIP_SOURCE_REMOVAL=true
+  echo "*** Setting SKIP_SOURCE_REMOVAL=$SKIP_SOURCE_REMOVAL to skip 
source removal in binary only build ***"
 fi
   else
 if [ "${MAIN_ARCHITECTURE:-}" = "${architecture:-}" ] ;then
@@ -483,6 +489,9 @@
 else
   echo "*** MAIN_ARCHITECTURE [${MAIN_ARCHITECTURE:-}] does not match 
\$architecture [${architecture:-}], setting binary only build and continuing 
with identify_build_type ***"
   DEBBUILDOPTS="-B"
+
+  SKIP_SOURCE_REMOVAL=true
+  echo "*** Setting SKIP_SOURCE_REMOVAL=$SKIP_SOURCE_REMOVAL to skip 
source removal in binary only build ***"
 fi
   fi
 
@@ -500,6 +509,9 @@
   echo "*** Package provides arch 'all' + 'any', enabling -B 
buildoption for this architecture. ***"
   # -B -> binary-only build, limited to architecture dependent packages
   DEBBUILDOPTS="-B"
+
+  SKIP_SOURCE_REMOVAL=true
+  echo "*** Setting SKIP_SOURCE_REMOVAL=$SKIP_SOURCE_REMOVAL to skip 
source removal in binary only build ***"
   break
 else
   # only "Architecture: all", so no arch specific packages since
@@ -776,8 +788,12 @@
 return 0
   fi
 
-  echo "*** Removing source package version from repository ***"
-  ${SUDO_CMD:-} ${REPREPRO_CMD} -A source -b "${REPOSITORY}" ${REPREPRO_OPTS} 
remove "${REPOS}" "${SOURCE_PACKAGE}"
+  if [ -n "${SKIP_SOURCE_REMOVAL:-}" ] ; then
+echo "*** Skipping removal of existing source package as requested via 
SKIP_SOURCE_REMOVAL ***"
+  else
+echo "*** Removing source package version from repository ***"
+${SUDO_CMD:-} ${REPREPRO_CMD} -A source -b "${REPOSITORY}" 
${REPREPRO_OPTS} remove "${REPOS}" "${SOURCE_PACKAGE}"
+  fi
 
   echo "*** Removing previous binary package versions from repository ***"
   for p in $(list_deb_files 
"${WORKSPACE}/binaries/"*"_${newest_version}_${arch}.changes") ; do
diff -Nru jenkins-debian-glue-0.18.2/scripts/generate-git-snapshot 
jenkins-debian-glue-0.18.2+deb9u1/scripts/generate-git-snapshot
--- jenkins-debian-glue-0.18.2/scripts/generate-git-snapshot2016-12-02 
17:00:43.0 +0100
+++ jenkins-debian-glue-0.18.2+deb9u1/scripts/generate-git-snapshot 
2017-04-14 22:48:24.0 +0200
@@ -372,6 +372,31 @@
   rm -rf .pc
 }
 
+identify_source_build_opts() {
+  # unset by default
+  DBP_OPTS=""
+
+  if [ -r "debian/source/format" ] && ! grep -q '^1\.0' 

Bug#860349: unblock: chromium-browser/57.0.2987.133-1

2017-04-14 Thread Michael Gilbert
package: release.debian.org
user: release.debian@packages.debian.org
usertags: unblock

Please consider unblocking chromium.  This updates to the latest
stable upstream security release with no other changes.

Best wishes,
Mike



Bug#830128: akonadiconsole: Same behavior after upgrade from jessie to stretch

2017-04-14 Thread Rainer Dorsch
Package: akonadiconsole
Version: 4:16.04.3-3
Followup-For: Bug #830128

Dear maintainer,

after upgrading from jessie to stretch I can neither start akonadiconsole nor 
kaddressbook, everything else seems to work ok (at least what I have seen so 
far):

rd@blackbox:~/tmp.nobackup$ kaddressbook 
org.kde.akonadi.ETM: GEN true false true
org.kde.akonadi.ETM: collection: QVector()
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kaddressbook path = /usr/bin pid = 24465
KCrash: Arguments: /usr/bin/kaddressbook 
KCrash: Attempting to start /usr/lib/i386-linux-gnu/libexec/drkonqi from kdeinit
sock_file=/run/user/2809/kdeinit5__0

[1]+  Stopped kaddressbook
rd@blackbox:~/tmp.nobackup$ akonadiconsole 
org.kde.akonadi.ETM: GEN true true true
org.kde.akonadi.ETM: collection: QVector()
org.kde.akonadi.ETM: GEN true false true
org.kde.akonadi.ETM: collection: QVector()
org.kde.akonadi.ETM: GEN true false true
org.kde.akonadi.ETM: collection: QVector()
org.kde.akonadi.ETM: GEN true false true
org.kde.akonadi.ETM: collection: QVector()
org.kde.akonadi.ETM: Subtree:  7936 QSet(7940, 7937, 7936, 7939, 7938)
org.kde.akonadi.ETM: Subtree:  1417 QSet(1417)
org.kde.akonadi.ETM: Subtree:  6847 QSet(6847, 6849, 6848, 7928, 7927)
org.kde.akonadi.ETM: Subtree:  9 QSet(3535, 2120, 9)
org.kde.akonadi.ETM: Subtree:  5672 QSet(5672)
org.kde.akonadi.ETM: Subtree:  5 QSet(5)
org.kde.akonadi.ETM: Subtree:  4 QSet(4)
org.kde.akonadi.ETM: Subtree:  1 QSet(7941, 7942, 1, 1359)
org.kde.akonadi.ETM: Subtree:  3455 QSet(3455, 3456, 3465, 3466)
org.kde.akonadi.ETM: Subtree:  3 QSet(3)
org.kde.akonadi.ETM: Subtree:  3724 QSet(3724, 6841, 7929, 7930)
org.kde.akonadi.ETM: Subtree:  6805 QSet(6805)
org.kde.akonadi.ETM: Subtree:  3449 QSet(3449)
org.kde.akonadi.ETM: Subtree:  6804 QSet(6804)
org.kde.akonadi.ETM: Subtree:  6807 QSet(6807)
org.kde.akonadi.ETM: Subtree:  7908 QSet(7910, 7923, 7924, 7909, 7908, 7911)
org.kde.akonadi.ETM: Subtree:  6806 QSet(6806)
org.kde.akonadi.ETM: Subtree:  6801 QSet(6801)
org.kde.akonadi.ETM: Subtree:  3635 QSet(3635)
org.kde.akonadi.ETM: Subtree: 6947 QSet(7388, 7391, 7390, 7385, 7384,
7387, 7386, 7381, 7380, 7383, 7382, 7377, 7376, 7379, 7378, 7405,
7404, 7407, 7406, 7401, 7400, 7403, 7402, 7397, 7396, 7399, 7398,
7393, 7392, 7395, 7394, 7421, 7420, 7423, 7422, 7417, 7416, 7419,
7418, 7413, 7412, 7415, 7414, 7409, 7408, 7411, 7410, 7309, 7308,
7311, 7310, 7305, 7304, 7307, 7306, 7301, 7300, 7303, 7302, 7297,
7296, 7299, 7298, 7325, 7324, 7327, 7326, 7321, 7320, 7323, 7322,
7317, 7316, 7319, 7318, 7313, 7312, 7315, 7314, 7341, 7340, 7343,
7342, 7337, 7336, 7339, 7338, 7333, 7332, 7335, 7334, 7329, 7328,
7331, 7330, 7357, 7356, 7359, 7358, 7353, 7352, 7355, 7354, 7349,
7348, 7351, 7350, 7345, 7344, 7347, 7346, 7245, 7244, 7247, 7246,
7241, 7240, 7243, 7242, 7237, 7236, 7239, 7238, 7233, 7232, 7235,
7234, 7261, 7260, 7263, 7262, 7257, 7256, 7259, 7258, 7253, 7252,
7255, 7254, 7249, 7248, 7251, 7250, 7277, 7276, 7279, 7278, 7273,
7272, 7275, 7274, 7269, 7268, 7271, 7270, 7265, 7264, 7267, 7266,
7293, 7292, 7295, 7294, 7289, 7288, 7291, 7290, 7285, 7284, 7287,
7286, 7281, 7280, 7283, 7282, 7181, 7180, 7183, 7182, 7177, 7176,
7179, 7178, 7173, 7172, 7175, 7174, 7169, 7168, 7171, 7170, 7197,
7196, 7199, 7198, 7193, 7192, 7195, 7194, 7189, 7188, 7191, 7190,
7185, 7184, 7187, 7186, 7213, 7212, 7215, 7214, 7209, 7208, 7211,
7210, 7205, 7204, 7207, 7206, 7201, 7200, 7203, 7202, 7229, 7228,
7231, 7230, 7225, 7224, 7227, 7226, 7221, 7220, 7223, 7222, 7217,
7216, 7219, 7218, 7117, 7116, 7119, 7118, 7113, 7112, 7115, 7114,
7109, 7108, 7111, 7110, 7105, 7104, 7107, 7106, 7133, 7132, 7135,
7134, 7129, 7128, 7131, 7130, 7125, 7124, 7127, 7126, 7121, 7120,
7123, 7122, 7149, 7148, 7151, 7150, 7145, 7144, 7147, 7146, 7141,
7140, 7143, 7142, 7137, 7136, 7139, 7138, 7165, 7164, 7167, 7166,
7161, 7160, 7163, 7162, 7157, 7156, 7159, 7158, 7153, 7152, 7155,
7154, 7053, 7052, 7055, 7054, 7049, 7048, 7051, 7050, 7045, 7044,
7047, 7046, 7041, 7040, 7043, 7042, 7069, 7068, 7071, 7070, 7065,
7064, 7067, 7066, 7061, 7060, 7063, 7062, 7057, 7056, 7059, 7058,
7085, 7084, 7087, 7086, 7081, 7080, 7083, 7082, 7077, 7076, 7079,
7078, 7073, 7072, 7075, 7074, 7101, 7100, 7103, 7102, 7097, 7096,
7099, 7098, 7093, 7092, 7095, 7094, 7089, 7088, 7091, 7090, 6989,
6988, 6991, 6990, 6985, 6984, 6987, 6986, 6981, 6980, 6983, 6982,
6977, 6976, 6979, 6978, 7005, 7004, 7007, 7006, 7001, 7000, 7003,
7002, 6997, 6996, 6999, 6998, 6993, 6992, 6995, 6994, 7021, 7020,
7023, 7022, 7017, 7016, 7019, 7018, 7013, 7012, 7015, 7014, 7009,
7008, 7011, 7010, 7037, 7036, 7039, 7038, 7033, 7032, 7035, 7034,
7029, 7028, 7031, 7030, 7025, 7024, 7027, 7026, 6957, 6956, 6959,
6958, 6953, 6952, 6955, 6954, 6949, 6948, 6951, 6950, 6947, 6973,
6972, 6975, 6974, 6969, 6968, 6971, 6970, 6965, 6964, 6967, 6966,
6961, 6960, 6963, 6962, 7898, 7892, 7891, 7917, 7916, 7919, 7918,
7915, 7914, 7907, 7921, 7920, 7922, 7821, 7820, 7823, 7822, 7817,
7816, 

Bug#860348: doc-base: missing file:// protocol in url of identifier tag in omf files

2017-04-14 Thread Alexis Murzeau
Package: doc-base
Version: 0.10.7
Severity: normal
Tags: patch

Dear Maintainer,

When generating omf files for scrollkeeper (or rarian), the generated 
omf file contains an url without the protocol (so this isn't a valid url).
For example, the blender-C.omf file contains the following tag:
--

--

According to the documentation [1], the url attribute should contains a 
valid url with a protocol (here: "file://"):
--

--

The consequence is that rarian expect the url to have "file://" and 
rarian-sk-get-cl outputs a bad file path 
("are/doc/blender-data/readme.html" for blender)
Because of this, khelpcenter is not able to show anything and shows 
errors about bad file path (which begin with are/doc/).


Is this url writting behavior expected ?

If not, I added in attachment a patch to Scrollkeeper.pm to add 
"file://" in front of the file path in the url attribute.
(I think rarian need a change too instead of blindly removing the first 
7 bytes of the url attribute, but that's another story)

[1] 
http://scrollkeeper.sourceforge.net/documentation/writing_scrollkeeper_omf_files/ar01s05.html


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

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

Versions of packages doc-base depends on:
ii  libuuid-perl   0.27-1
ii  libyaml-tiny-perl  1.70-1

doc-base recommends no packages.

Versions of packages doc-base suggests:
pn  dhelp | dwww | doc-central | yelp | khelpcenter4  
ii  rarian-compat 0.8.1-6+b1

-- no debconf information

--- /usr/share/perl5/Debian/DocBase/Programs/Scrollkeeper.pm2016-01-27 
22:53:27.0 +0100
+++ Scrollkeeper.pm 2017-04-14 01:51:28.102831810 +0200
@@ -247,7 +247,7 @@
   print OMF "\t\t\n";
   print OMF 
"\t\t".&_HTMLEncode($doc->GetAbstract())."\n";
   print OMF "\t\t\n";
-  print OMF "\t\t\n";
+  print OMF "\t\t\n";
   print OMF "\t\t\n";
   print OMF "\t\t\n";
 



Bug#860347: xserver-xorg-core: can't produce script.log for running X server

2017-04-14 Thread Mark
Package: xserver-xorg-core
Version: 2:1.16.4-1
Severity: serious
Justification: unknow

Dear Maintainer,

For the ability to file other bug reports, this bug is in fact responsible for
affecting.

I cannot, via the command
"sudo /usr/share/bug/xorg/script 3>/tmp/script.log"

produce a script.log, say, for an attachment to a bug report. I am given:

/usr/share/bug/xorg/script: 19: /usr/share/bug/xorg/script: 3: Bad file
descriptor




-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Apr  6 17:23 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 2498728 Feb 10  2015 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
:0a:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV43 [GeForce 
6600] [10de:0141] (rev a2)

Xorg X server configuration file status:

-rw-r--r-- 1 root root 2526 Apr 12 19:22 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
---
Section "ServerLayout"
Identifier "X.org Configured"
Screen  0  "Screen0" 0 0
InputDevice"Mouse0" "CorePointer"
InputDevice"Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
ModulePath   "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/X11/misc"
FontPath "/usr/share/fonts/X11/cyrillic"
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
FontPath "/usr/share/fonts/X11/Type1"
FontPath "/usr/share/fonts/X11/100dpi"
FontPath "/usr/share/fonts/X11/75dpi"
FontPath "built-ins"
EndSection

Section "Module"
Load  "glx"
EndSection

Section "InputDevice"
Identifier  "Keyboard0"
Driver  "kbd"
EndSection

Section "InputDevice"
Identifier  "Mouse0"
Driver  "mouse"
Option  "Protocol" "auto"
Option  "Device" "/dev/input/mice"
Option  "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
Identifier   "Monitor0"
VendorName   "Monitor Vendor"
ModelName"Monitor Model"
EndSection

Section "Device"
### Available Driver options are:-
### Values: : integer, : float, : "True"/"False",
### : "String", : " Hz/kHz/MHz",
### : "%"
### [arg]: arg optional
#Option "SWcursor"  # []
#Option "HWcursor"  # []
#Option "NoAccel"   # []
#Option "ShadowFB"  # []
#Option "VideoKey"  # 
#Option "WrappedFB" # []
#Option "GLXVBlank" # []
#Option "ZaphodHeads"   # 
#Option "PageFlip"  # []
#Option "SwapLimit" # 
#Option "AsyncUTSDFS"   # []
#Option "AccelMethod"   # 
Identifier  "Card0"
Driver  "fbdev"
BusID   "PCI:10:0:0"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor"Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport   0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport   0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport   0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport   0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport   0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport   0 0
Depth 24
EndSubSection
EndSection

Section "DRI"
Mode 0666
EndSection

/etc/X11/xorg.conf.d does not exist.

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 3.16.0-4-powerpc64 (debian-ker...@lists.debian.org) (gcc version 
4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root  3955 Apr 12 19:21 /var/log/Xorg.1.log
-rw-r--r-- 1 root root  3955 Apr 12 19:21 /var/log/Xorg.2.log
-rw-r--r-- 1 root root  3955 Apr 12 19:21 /var/log/Xorg.3.log
-rw-r--r-- 1 root root  3955 Apr 12 19:21 /var/log/Xorg.4.log
-rw-r--r-- 1 root root  3955 Apr 12 19:21 /var/log/Xorg.5.log
-rw-r--r-- 1 root root 28343 Apr 14 14:16 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[15.144] 
X.Org X Server 1.16.4
Release Date: 2014-12-20
[15.144] X Protocol Version 11, Revision 0
[  

Bug#859572: docbook-xsl: randomly adds ???TITLE??? to title

2017-04-14 Thread James Ross
I've spent a little bit of time trying to figure out what's going on, and I can 
see that:

* The issue only happens when there is xmlns="http://docbook.org/ns/docbook; on 
the root  element

* It is definitely picking up the contents of the $ebnf.assignment param from 
"/usr/share/xml/docbook/stylesheet/docbook-xsl/html/param.xsl"

The shortest input for reproduction I have found is therefore this:


http://docbook.org/ns/docbook;>

Something about the namespace removal (mode="stripNS") is picking up the 
$ebnf.assignment param. I haven't figured out why (it might be a bug in 
libxslt, for example), but this XSLT appears to be troublesome:


::=


However, I have found that replacing it with the following fixes it, without 
breaking the output for EBNF output (EBNF HTML output is the same before and 
after):


code>::=/code>


The above was all conducted on Ubuntu 16.04.1 LTS with docbook-xsl 
1.79.1+dfsg-1, and xsltproc 1.1.28-2.1. I would expect the same fix to apply to 
Debian.



Bug#781155: openbsd-inetd: openbsd-inetd.service should be the main service file

2017-04-14 Thread Marco d'Itri
On Apr 13, Raphael Hertzog  wrote:

> Consistency between package name and init script and service file
> has no reason to be classified as "historical accident", it seems
> to be nice bonus point to me...
I think that consistenct between daemon name and systemd unit name is 
a much better goal.

-- 
ciao,
Marco


signature.asc
Description: PGP signature


Bug#849517: The valgrind diagnostic is a false positive

2017-04-14 Thread Reuben Thomas
On 14 April 2017 at 13:47, Florian Weimer  wrote:

> * Reuben Thomas:
>
> > ​A workaround is to build bash with --without-bash-malloc (but I presume
> > there's a good reason not to do that?).​
>
> FWIW, Fedora and Red Hat Enterprise Linux compile bash this way, so it
> can't be *that* bad.
>

​I hadn't appreciated that. It would seem to be a good way to fix this
problem and also avoid any bugs in bash's malloc; presumably the
performance hit is of relatively little interest given that bash is no
longer the default /bin/sh.

-- 
http://rrt.sc3d.org


Bug#860302: libmbedtls-dev: please provide static lib in dev package

2017-04-14 Thread SJ Zhu
Yes, I agree there's disadvantage for static linking.
My use case is to send a copy of the program to others for testing, so
the users don't need to bother the version of the library  and focus
on testing the program itself.
When the program is ready for distrubution, it's better to build a
deb/rpm package and link it dynamically.

On Fri, Apr 14, 2017 at 6:38 PM, James Cowgill  wrote:
> Control: severity -1 wishlist
>
> Hi,
>
> On 14/04/17 10:45, Shengjing Zhu wrote:
>> Package: libmbedtls-dev
>> Version: 2.4.2-1
>> Severity: important
>>
>> Dear Maintainer,
>>
>> In debian/rules, you set -DUSE_STATIC_MBEDTLS_LIBRARY=OFF, but static
>> library is useful in development, and .a file should be put in -dev
>> package according to debian policy 8.3
>
> I'll think about it, but I see a lot of disadvantages with statically
> linking a security library with few advantages. Why would static /
> dynamic linking matter during development?
>
> James
>



-- 
Regards,
Shengjing Zhu



Bug#859826: xca: Please migrate to openssl1.1 in Buster

2017-04-14 Thread Sebastian Andrzej Siewior
On 2017-04-10 14:23:42 [+0200], Tino Mettler wrote:
> Hi,
Hi,

> I didn't want to state that there are no successors in 1.1. It's just
> that the accessors work differently, and making XCA build with 1.0 and
> 1.1 results in a little #ifdef hell. Another annoyance was that the
> OpenSSL documentation was somewhat behind at least last year, and the
> web server was in some sort of reorganisation, resulting in a lot if
> 404 errors.

The recommended way
https://wiki.openssl.org/index.php/OpenSSL_1.1.0_Changes

is to provide the accessors like RSA_set0_key() via ifdef for older
openssl versions (older than 1.1.0) and then use it in the source code
without any ifdefs.

> I'll ask upstream about the current state.

great.

> Regards,
> Tino

Sebastian



Bug#845346: qupzilla: QupZilla is built without kwallet support

2017-04-14 Thread Brendon Higgins
Hi,

This was bugging me as well, so I made some changes to the Debian package 
source, and the KWallet plugin seems to be working for me now with KDE 5's 
KWallet. Patch attached. Hope it's helpful.

Peace,
Brendon
diff -Naur qupzilla-2.0.2~dfsg1.orig/debian/control qupzilla-2.0.2~dfsg1/debian/control
--- qupzilla-2.0.2~dfsg1.orig/debian/control	2017-01-11 12:43:00.0 -0500
+++ qupzilla-2.0.2~dfsg1/debian/control	2017-04-14 16:50:37.093046718 -0400
@@ -9,7 +9,7 @@
  qtbase5-private-dev, qtscript5-dev,
  libqt5x11extras5-dev,
  libx11-dev,
- libssl1.0-dev, kdelibs5-dev, libgnome-keyring-dev,
+ libssl1.0-dev, libkf5wallet-dev, libgnome-keyring-dev,
  libjs-jquery, libjs-jquery-ui
 Standards-Version: 3.9.8
 Homepage: http://www.qupzilla.com/
diff -Naur qupzilla-2.0.2~dfsg1.orig/debian/patches/kde-integration.patch qupzilla-2.0.2~dfsg1/debian/patches/kde-integration.patch
--- qupzilla-2.0.2~dfsg1.orig/debian/patches/kde-integration.patch	1969-12-31 19:00:00.0 -0500
+++ qupzilla-2.0.2~dfsg1/debian/patches/kde-integration.patch	2017-04-14 16:54:05.972901755 -0400
@@ -0,0 +1,17 @@
+Index: qupzilla-2.0.2~dfsg1/src/plugins/plugins.pro
+===
+--- qupzilla-2.0.2~dfsg1.orig/src/plugins/plugins.pro
 qupzilla-2.0.2~dfsg1/src/plugins/plugins.pro
+@@ -32,9 +32,10 @@ outOfDirPlugins = $$(QUPZILLA_PLUGINS_SR
+ # TestPlugin only in debug build
+ !CONFIG(debug, debug|release): disablePlugin(TestPlugin)
+ 
++## enforced KDE_INTEGRATION
+ # KWalletPasswords only with KDE_INTEGRATION and KWallet framework
+-!contains(DEFINES, KDE_INTEGRATION): disablePlugin(KWalletPasswords)
+-!qtHaveModule(KWallet): disablePlugin(KWalletPasswords)
++# !contains(DEFINES, KDE_INTEGRATION): disablePlugin(KWalletPasswords)
++# !qtHaveModule(KWallet): disablePlugin(KWalletPasswords)
+ 
+ ## enforced GNOME_INTEGRATION
+ # GnomeKeyringPasswords only with GNOME_INTEGRATION and gnome-keyring pkg-config
diff -Naur qupzilla-2.0.2~dfsg1.orig/debian/patches/series qupzilla-2.0.2~dfsg1/debian/patches/series
--- qupzilla-2.0.2~dfsg1.orig/debian/patches/series	2015-04-16 17:20:39.0 -0400
+++ qupzilla-2.0.2~dfsg1/debian/patches/series	2017-04-14 16:52:23.148972777 -0400
@@ -1,2 +1,3 @@
 hardening.patch
 gnome-integration.patch
+kde-integration.patch


Bug#857794: reportbug: crash when encountering some non-ASCII characters

2017-04-14 Thread Louis-Philippe Véronneau
Control: tag -1 patch

Hi!

I tested your patch (0001-Stop-using-subprocess.getoutput.patch) and it
works fine for me using C locales and packages where the maintainer's
name has non-ascii chars.

It's not pretty thought (but does not crash, so \0/):

"Maintainer for stressant is 'Antoine Beaupr\xe9 '."

Happy to do some more testing if needed.

Cheers,

-- 
pollo

On Tue, 11 Apr 2017 16:16:00 + Niels Thykier  wrote:
> On Fri, 24 Mar 2017 23:33:34 +0100 Nis Martensen 
> wrote:
> > Hi Stuart,
> > 
> > Thanks for your comments!
> > 
> > [...]
> > 
> > No problem with that idea :)
> > I just tried to keep the changes to a minimum since we're in deep freeze
> > at the moment.
> > 
> > Cheers,
> >  Nis
> > 
> > 
> 
> 
> Hi,
> 
> Is there an update on this bug? :)
> 
> Thanks,
> ~Niels
> 
> 
> 




signature.asc
Description: OpenPGP digital signature


Bug#859539: filezilla: Filezilla crashes at startup

2017-04-14 Thread Kienan Stewart
Hi,

I was unable to reproduce this bug on a clean install (QEMU VM), or on my 
laptop which had been upgraded from Jessie to Stretch some time ago. I followed 
the test proposed by John earlier.

Perhaps there are some details in the config file or the bookmark path that may 
be pertinent to provoking this bug? What is the "Language Code" setting in 
filezilla.xml?

filezilla:
  Installed: 3.24.0-1

Thanks,
Kienan



signature.asc
Description: PGP signature


Bug#860346: unblock: oce/0.17.2-2

2017-04-14 Thread Anton Gladky
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package oce

The upstream has found and fixed an annoying bug [1] in
oce. Debian and Ubuntu packages are affected. OCE_LIBRARIES
wrongly includes DRAWEX if -DOCE_DRAW=ON.

The attached patch was cherry-picked from upstream repo.

unblock oce/0.17.2-2


[1] https://github.com/tpaviot/oce/issues/660

Thanks,

Anton
diff -Nru oce-0.17.2/debian/changelog oce-0.17.2/debian/changelog
--- oce-0.17.2/debian/changelog 2016-06-16 23:05:45.0 +0200
+++ oce-0.17.2/debian/changelog 2017-04-14 22:35:14.0 +0200
@@ -1,3 +1,10 @@
+oce (0.17.2-2) unstable; urgency=medium
+
+  [ Janus Weil ]
+  * [c25582f] Prevent DRAWEXE from being added to OCE_LIBRARIES.
+
+ -- Anton Gladky   Fri, 14 Apr 2017 22:35:14 +0200
+
 oce (0.17.2-1) unstable; urgency=medium
 
   * [776089c] Imported Upstream version 0.17.2
diff -Nru oce-0.17.2/debian/patches/do_not_add_drawexe.patch 
oce-0.17.2/debian/patches/do_not_add_drawexe.patch
--- oce-0.17.2/debian/patches/do_not_add_drawexe.patch  1970-01-01 
01:00:00.0 +0100
+++ oce-0.17.2/debian/patches/do_not_add_drawexe.patch  2017-04-14 
22:33:04.0 +0200
@@ -0,0 +1,25 @@
+From 340781368c4d1902887fe6a5b7288cce5eb53456 Mon Sep 17 00:00:00 2001
+From: Janus Weil 
+Date: Sun, 12 Mar 2017 16:47:28 +0100
+Subject: [PATCH] prevent DRAWEXE from being added to OCE_LIBRARIES * see issue
+ #660
+
+---
+ CMakeLists.txt | 4 +++-
+ 1 file changed, 3 insertions(+), 1 deletion(-)
+
+diff --git a/CMakeLists.txt b/CMakeLists.txt
+index 19e9705..c379b3c 100644
+--- a/CMakeLists.txt
 b/CMakeLists.txt
+@@ -990,7 +990,9 @@ macro(process_module modulename modules_std)
+   list(APPEND modules ${ARGN})
+   endif(NOT OCE_DISABLE_X11)
+   foreach(module ${modules})
+-  list(APPEND OCE_LIBRARIES ${module})
++  if(NOT module MATCHES ".*EXE")
++  list(APPEND OCE_LIBRARIES ${module})
++  endif()
+   set(TOOLKIT_MODULES "")
+   set(TOOLKIT_DEPENDS "")
+   set(TOOLKIT_INCLUDE_DIRECTORIES "")
diff -Nru oce-0.17.2/debian/patches/series oce-0.17.2/debian/patches/series
--- oce-0.17.2/debian/patches/series2016-01-29 13:01:05.0 +0100
+++ oce-0.17.2/debian/patches/series2017-04-14 22:33:49.0 +0200
@@ -1,2 +1,3 @@
 split-export.patch
 speedup-BRepMesh_test.patch
+do_not_add_drawexe.patch


Bug#860287: libosip2: CVE-2016-10324 CVE-2016-10325 CVE-2016-10326 CVE-2017-7853

2017-04-14 Thread anarcat
Control: fixed -1 4.1.0-2.1
Control: tags -1 +pending

I have made a NMU (diff in #860345) to fix this in sid/stretch, the
patches apply fairly cleanly, and since it's the same version in jessie,
it should be trivial to backport there...

I forgot to mention the bug # in the NMU, unfortunately...

A.



Bug#860345: libosip2: diff for NMU version 4.1.0-2.1

2017-04-14 Thread anarcat
Package: libosip2
Version: 4.1.0-2
Severity: normal
Tags: patch pending

Dear maintainer,

I've prepared an NMU for libosip2 (versioned as 4.1.0-2.1) and
uploaded it to DELAYED/3. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
diff -Nru libosip2-4.1.0/debian/changelog libosip2-4.1.0/debian/changelog
--- libosip2-4.1.0/debian/changelog	2014-06-25 07:55:15.0 -0400
+++ libosip2-4.1.0/debian/changelog	2017-04-14 16:23:31.0 -0400
@@ -1,3 +1,23 @@
+libosip2 (4.1.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * CVE-2016-10324: In libosip2 in GNU oSIP 4.1.0, a malformed SIP message
+can lead to a heap buffer overflow in the osip_clrncpy() function
+defined in osipparser2/osip_port.c.
+  * CVE-2016-10325: In libosip2 in GNU oSIP 4.1.0, a malformed SIP message
+can lead to a heap buffer overflow in the _osip_message_to_str()
+function defined in osipparser2/osip_message_to_str.c, resulting in a
+remote DoS.
+  * CVE-2016-10326: In libosip2 in GNU oSIP 4.1.0, a malformed SIP message
+can lead to a heap buffer overflow in the osip_body_to_str() function
+defined in osipparser2/osip_body.c, resulting in a remote DoS.
+  * CVE-2017-7853: In libosip2 in GNU oSIP 5.0.0, a malformed SIP message
+can lead to a heap buffer overflow in the msg_osip_body_parse()
+function defined in osipparser2/osip_message_parse.c, resulting in a
+remote DoS.
+
+ -- Antoine Beaupré   Fri, 14 Apr 2017 16:21:21 -0400
+
 libosip2 (4.1.0-2) unstable; urgency=low
 
   * Upload to unstable - coordinated through debian-release
diff -Nru libosip2-4.1.0/debian/patches/CVE-2016-10324.patch libosip2-4.1.0/debian/patches/CVE-2016-10324.patch
--- libosip2-4.1.0/debian/patches/CVE-2016-10324.patch	1969-12-31 19:00:00.0 -0500
+++ libosip2-4.1.0/debian/patches/CVE-2016-10324.patch	2017-04-14 16:26:51.0 -0400
@@ -0,0 +1,24 @@
+From 7e0793e15e21f68337e130c67b031ca38edf055f Mon Sep 17 00:00:00 2001
+From: Aymeric Moizard 
+Date: Mon, 5 Sep 2016 15:01:53 +0200
+Subject:  * fix bug report: sr #109133: Heap buffer overflow in utility
+ function *osip_clrncpy*https://savannah.gnu.org/support/?109133
+
+---
+ src/osipparser2/osip_port.c | 4 +++-
+ 1 file changed, 3 insertions(+), 1 deletion(-)
+
+--- a/src/osipparser2/osip_port.c
 b/src/osipparser2/osip_port.c
+@@ -1462,8 +1462,10 @@ osip_clrncpy (char *dst, const char *src
+   char *p;
+   size_t spaceless_length;
+ 
+-  if (src == NULL)
++  if (src == NULL || len == 0) {
++*dst = '\0';
+ return NULL;
++  }
+ 
+   /* find the start of relevant text */
+   pbeg = src;
diff -Nru libosip2-4.1.0/debian/patches/CVE-2016-10325.patch libosip2-4.1.0/debian/patches/CVE-2016-10325.patch
--- libosip2-4.1.0/debian/patches/CVE-2016-10325.patch	1969-12-31 19:00:00.0 -0500
+++ libosip2-4.1.0/debian/patches/CVE-2016-10325.patch	2017-04-14 16:26:54.0 -0400
@@ -0,0 +1,26 @@
+From 1d9fb1d3a71cc85ef95352e549b140c706cf8696 Mon Sep 17 00:00:00 2001
+From: Aymeric Moizard 
+Date: Sat, 3 Sep 2016 15:29:34 +0200
+Subject:   * fix bug report: sr #109131: Heap buffer overflow in
+ `_osip_message_to_str` https://savannah.gnu.org/support/?109131
+
+---
+ src/osipparser2/osip_message_to_str.c | 7 +++
+ 1 file changed, 7 insertions(+)
+
+--- a/src/osipparser2/osip_message_to_str.c
 b/src/osipparser2/osip_message_to_str.c
+@@ -378,6 +378,13 @@ _osip_message_to_str (osip_message_t * s
+ /* A start-line isn't required for message/sipfrag parts. */
+   }
+   else {
++size_t message_len = strlen(tmp);
++if (_osip_message_realloc (, dest, message_len + 3, _size) < 0) {
++  osip_free (tmp);
++  *dest = NULL;
++  return OSIP_NOMEM;
++}
++
+ message = osip_str_append (message, tmp);
+ osip_free (tmp);
+ message = osip_strn_append (message, CRLF, 2);
diff -Nru libosip2-4.1.0/debian/patches/CVE-2016-10326.patch libosip2-4.1.0/debian/patches/CVE-2016-10326.patch
--- libosip2-4.1.0/debian/patches/CVE-2016-10326.patch	1969-12-31 19:00:00.0 -0500
+++ libosip2-4.1.0/debian/patches/CVE-2016-10326.patch	2017-04-14 16:26:56.0 -0400
@@ -0,0 +1,27 @@
+From b9dd097b5b24f5ee54b0a8739e59641cd51b6ead Mon Sep 17 00:00:00 2001
+From: Aymeric Moizard 
+Date: Sat, 3 Sep 2016 15:58:06 +0200
+Subject:  * fix bug report: sr #109132: Heap buffer overflow in
+ *osip_body_to_str*https://savannah.gnu.org/support/index.php?109132
+
+---
+ src/osipparser2/osip_body.c | 8 
+ 1 file changed, 8 insertions(+)
+
+--- a/src/osipparser2/osip_body.c
 b/src/osipparser2/osip_body.c
+@@ -417,6 +417,14 @@ osip_body_to_str (const osip_body_t * bo
+   }
+ 
+   if ((osip_list_size (body->headers) > 0) || (body->content_type != NULL)) {
++if (length < tmp_body - ptr + 3) {
++  size_t len;
++
++  len = tmp_body - ptr;
++  length = length + 3 + body->length; /* add body->length, 

Bug#856874: Confirm patch for bug #856874 is good

2017-04-14 Thread Long Vu

user debian-rele...@lists.debian.org
usertags 856874 bsp-2017-04-ca-montreal
thanks

Reproducing the bug:


dget -x 
http://httpredir.debian.org/debian/pool/main/r/resiprocate/resiprocate_1.11.0~beta1-1.dsc


cowbuilder build resiprocate_1.11.0~beta1-1.dsc

cd /var/cache/pbuilder/result
dpkg -i libresiprocate-1.11-dev_1.11.0~beta1-1_amd64.deb

ls -l /usr/lib/x86_64-linux-gnu/librepro.so
lrwxrwxrwx 1 root root 16 Jan 15 20:19 
/usr/lib/x86_64-linux-gnu/librepro.so -> librepro-1.11.so


ls -lL /usr/lib/x86_64-linux-gnu/librepro.so
ls: cannot access '/usr/lib/x86_64-linux-gnu/librepro.so': No such file 
or directory



Confirming the bug is fixed:


cd extracted_dir/resiprocate_1.11.0~beta1-1

dch -i  # update the changelog

debuild -us -uc -S -d  # build source package

cowbuilder build resiprocate_1.11.0~beta1-2.dsc  # build the binary new 
source package


cd /var/cache/pbuilder/result
dpkg -i libresiprocate-1.11_1.11.0~beta1-2_amd64.deb

ls -l /usr/lib/x86_64-linux-gnu/librepro.so
lrwxrwxrwx 1 root root 16 Apr 14 18:44 
/usr/lib/x86_64-linux-gnu/librepro.so -> librepro-1.11.so


ls -lL /usr/lib/x86_64-linux-gnu/librepro.so
-rw-r--r-- 1 root root 1390672 Apr 14 18:44 
/usr/lib/x86_64-linux-gnu/librepro.so




Bug#860344: nm.debian.org: CSS/Theme overrides input field background color so input is invisible with dark OS themes

2017-04-14 Thread Coenraad Loubser
Package: nm.debian.org
Severity: normal

This is a styling/theme usability problem within our power to fix.

Many Debian web sites have CSS which sets a background color for input fields 
light; this renders text typed into input fields invisible if the OS foreground 
color is white or light. Fix: do not set a background color. 

(Chromium has built in checking to override sites that do this, Firefox does 
not. Debian.org sites are the only ones I regularly come across that exhibit 
this problem.) Happy to receive guidance on what it will take to get fixed... 
and drive it until it is done. Am doing the same from Mozilla side. 

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

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



Bug#859927: Works, uploaded to DELAYED-3

2017-04-14 Thread micah anderson

That fix works, I've done a NMU fixed package and uploaded it to
DELAYED-3.

Micah



Bug#857992: openjdk-8-jre-headless: please add Breaks: tzdata-java

2017-04-14 Thread anarcat
user debian-rele...@lists.debian.org
usertags 857992 bsp-2017-04-ca-montreal
thanks

On Mon, Apr 10, 2017 at 12:28:07PM +0200, Andreas Beckmann wrote:
> Control: severity -1 serious
> 
> On 2017-03-17 00:33, Andreas Beckmann wrote:
> > I haven't rebuilt openjdk-8 to test whether this actually works (and
> > don't have the tiem to so now).
> 
> I just rebuilt openjdk-8 with that Breaks added and it fixed this
> previously failing upgrade path.

I have tried to do a NMU for this and failed to build OpenJDK through
pdebuild:

 -> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team 
Description: Dummy package to satisfy dependencies with aptitude - created by 
pbuilder
 This package was created automatically by pbuilder to satisfy the
 build-dependencies of the package being currently built.
Depends: debhelper (>= 9), quilt, m4, lsb-release, zip, unzip, sharutils, gawk, 
cpio, pkg-config, procps, wdiff, fastjar (>= 2:0.96-0ubuntu2), autoconf (>= 
2.69), automake, autotools-dev, ant, ant-optional, g++-6, openjdk-8-jdk | 
openjdk-7-jdk, libxtst-dev, libxi-dev, libxt-dev, libxaw7-dev, libxrender-dev, 
libcups2-dev, libasound2-dev, liblcms2-dev, libfreetype6-dev (>= 2.2.1), 
libgtk2.0-dev, libxinerama-dev, libkrb5-dev, xsltproc, libpcsclite-dev, 
libffi-dev, zlib1g-dev, libattr1-dev, libpng-dev, libjpeg-dev, libgif-dev, 
libpulse-dev (>= 0.9.12), systemtap-sdt-dev, libnss3-dev (>= 2:3.17.1), tzdata, 
mauve, jtreg, xvfb, xauth, xfonts-base, libgl1-mesa-dri, twm | metacity, twm | 
dbus-x11, x11-xkb-utils, time, openjdk-8-jdk-headless , dpkg-dev (>= 
1.17.14)
dpkg-deb: error: parsing file 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy/DEBIAN/control' 
near line 8 package 'pbuilder-satisfydepends-dummy':
 'Depends' field, syntax error after reference to package 
'openjdk-8-jdk-headless'
E: pbuilder-satisfydepends failed.

I couldn't even build a source-only package there..

So I'm giving up on this - but I'll not that there is a
${tzdata:Depends} in the headless package that may be the cause of the
problems here...

I also wonder if that affects other binary packages in openjdk, but
considering tzdata is present only in the headless version, that
shouldn't be an issue...

A.



Bug#858855: gpodder: subscribing to https://requestforcomments.de/feed raises an ssl error

2017-04-14 Thread Thomas Perl
This seems to be the following upstream bug:
https://github.com/gpodder/gpodder/issues/265

A fix would be to upgrade to Python 2.7.9, as indicated here:
https://github.com/gpodder/gpodder/issues/269


Thanks,
Thomas

> On 9 Apr 2017, at 23:59, tony mancill  wrote:
> 
> On Mon, Mar 27, 2017 at 09:26:45PM +0200, Henning K wrote:
>> Package: gpodder
>> Version: 3.9.3-1
>> Severity: normal
>> 
>> Dear Maintainer,
>> 
>> when I tried to subscribe to this feed https://requestforcomments.de/feed 
>> using
>> the gtk-ui as well as the cli gpodder raised a SSLV3_ALERT_HANDSHAKE_FAILURE.
> 
> 
> Hello, and thank you reporting this bug.  I have reproduced the bug
> within gpodder but also making the same request directly using the
> urllib2 library (which is how gpodder opens the URL).
> 
> The attached test programs demonstrate that problem exists in urllib2:
> 
> $ python2.7 858855_urllib2_test.py 
> Traceback (most recent call last):
>  File "858855_urllib2_test.py", line 4, in 
>opener.open(request)
>  File "/usr/lib/python2.7/urllib2.py", line 429, in open
>response = self._open(req, data)
>  File "/usr/lib/python2.7/urllib2.py", line 447, in _open
>'_open', req)
>  File "/usr/lib/python2.7/urllib2.py", line 407, in _call_chain
>result = func(*args)
>  File "/usr/lib/python2.7/urllib2.py", line 1241, in https_open
>context=self._context)
>  File "/usr/lib/python2.7/urllib2.py", line 1198, in do_open
>raise URLError(err)
> urllib2.URLError:  alert handshake failure (_ssl.c:661)>
> 
> But not when using the requests library:
> 
> $ python2.7 858855_requests_test.py 
> status_code 200
> request body length 41558
> 
> Thus the problem seems to lie with the SSL negotiation between the site
> and any python code utilizing the urllib2 library.
> 
> I need to do some more digging, but believe that it could be a variant
> of #678035 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678035).
> 
> Cheers,
> tony
> <858855_urllib2_test.py><858855_requests_test.py>



Bug#858163: unblock: gitlab/8.13.11+dfsg-6

2017-04-14 Thread Niels Thykier
Control: tags -1 moreinfo

Pirate Praveen:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please unblock package gitlab
> 
> This fixes RC bug #857967. Also sine the version in stretch is currently
> not installable, please reduce the age.
> 
> debdiff with 8.13.11+dfsg-5 attached (changes upto this version is
> already approved)
> 
> unblock gitlab/8.13.11+dfsg-6
> 
> [...]

Hi Pirate,

Sorry for the delay in getting back to you.

I have reviewed gitlab and I got some remarks.  Please note that some of
these may be remarks that we should have noticed in earlier reviews.
Apologies for overlooking them previously if this is the case, but I
decided to review some of the files from the original source files
rather than the diff.

 * In the postrm (RC bug):

"""
su ${gitlab_user} -c 'psql gitlab_production -c ""' && \
   su postgres -c "dropdb gitlab_production"
"""

This does not appear to be idempotent.  If the database is dropped but a
later part of the purge fails, then this line will prevent dpkg from
rerunning the purge and reach the desired state (as the code is run
under "set -e")

You probably want something like:

"""
  if su ${gitlab_user} -c 'psql gitlab_production -c ""'; then
 su postgres -c "dropdb gitlab_production"
  fi
"""

A similar remark can be made for the following code where it would be
prudent to apply the same fix:

"""
test -e ${gitlab_log_dir} && rm -rf ${gitlab_log_dir}
test -e ${gitlab_cache_path} && rm -rf ${gitlab_cache_path}
test -e ${gitlab_pid_path} && rm -rf ${gitlab_pid_path}
test -e ${gitlab_data_dir} && rm -rf ${gitlab_data_dir}
[...]
id -u ${gitlab_user} && userdel -r ${gitlab_user}

[...]
test -f ${nginx_site} && echo "Found nginx site"
[...]
# remove the configuration file itself
test -f ${nginx_site} && rm -f ${nginx_site}
test -f ${gitlab_debian_conf} && rm -f ${gitlab_debian_conf}
test -f ${gitlab_yml} && rm -f ${gitlab_yml}
test -f ${gitlab_tmpfiles} && rm -f ${gitlab_tmpfiles}
test -f ${gitlab_shell_config} && rm -f ${gitlab_shell_config}
  [...]
  test -n "${nginx_site}" && ucf --purge ${nginx_site}
  test -n "${gitlab_debian_conf}" && ucf --purge ${gitlab_debian_conf}
  test -n "${gitlab_yml}" && ucf --purge ${gitlab_yml}
  test -n "${gitlab_tmpfiles}" && ucf --purge ${gitlab_tmpfiles}
  test -n "${gitlab_shell_config}" && ucf -purge ${gitlab_shell_config}
  [...]
  test -n "${nginx_site}" && ucfr --purge gitlab ${nginx_site}
  test -n "${gitlab_debian_conf}" && ucfr --purge gitlab
${gitlab_debian_conf}
  test -n "${gitlab_yml}" && ucfr --purge gitlab ${gitlab_yml}
  test -n "${gitlab_tmpfiles}" && ucfr --purge gitlab ${gitlab_tmpfiles}
  test -n "${gitlab_shell_config}" && ucfr -purge gitlab
${gitlab_shell_config}

"""

Note I got a follow up remark for the "id+userdel" line below.  As for
the "test -n", these mean that the script will fail if these values are
not (still) present in the config OR worse - if the gitlab config is
already deleted (this is also listed a separate item below)



 * debian/postrm (RC bug):

The postrm will fail if the admin removes the gitlab config files prior
to purging gitlab.  This happens because then most of the variables are
set and as shown above, this will make several test statements evaluate
to false on the left-hand-side of an && under "set -e".

Admittedly, this is partly mitigated by gitlab providing its own default
as a copy under /var/lib/gitlab/gitlab-debian.defaults.  But in theory,
the machine could fail after removing
"/var/lib/gitlab/gitlab-debian.defaults" but prior to dpkg committing
that it had purged gitlab.

It is an unlikely corner-case, but as it leaves the admin with an
unpurgeable package it is RC.  To my knowledge, it is *not* sufficient
to make the removal of the /var/lib file the last thing.  That just
narrows the window for the issue without fixing it.

 * debian/postrm (important)

As I recall, the general consensus on handling of system users is that
we should lock them rather than remove them.  The gitlab postrm deletes
the user:

"""
id -u ${gitlab_user} && userdel -r ${gitlab_user}
"""

That said, I believe gitlab is not the only package deleting the user,
so it is not RC.

 * debian/config (important/RC bug):

The config file uses the debconf database as a registry.  It should
"pre-seed" itself with the defaults from the configuration files.  See
"man 8 debconf-devel" under "config file handling":

https://manpages.debian.org/jessie/debconf-doc/debconf-devel.7.en.html#ADVANCED_PROGRAMMING_WITH_DEBCONF


 * debian/postinst (RC bug):

"""
  # Override User for systemd services
  for service in mailroom unicorn sidekiq workhorse; do
path=/etc/systemd/system/gitlab-${service}.service.d
mkdir -p $path
printf "[Service]\nUser=${gitlab_user}\n" > 

Bug#859805: Patch proposal

2017-04-14 Thread JC
Control: user debian-rele...@lists.debian.org
Control: usertags -1 bsp-2017-04-ca-montreal

Here is a patch to manage the upgrade of postfix maps from postinst.

I know modifying a user config file is controversial, but here we only do
it for postfix libraries in standard Debian installation path, so I
consider it ok from my point of view. The worst case scenario would be a
sysadmin who'd put its own private library in /usr/lib/postfix/dict_XXX.so
which would have been wrong in the first place since (s)he should have put
it under /usr/local/ instead.

--- postfix.postinst.orig 2017-01-20 23:32:04.0 -0500
+++ postfix.postinst 2017-04-14 15:36:29.074921466 -0400
@@ -293,6 +293,10 @@
  fi
 done < /usr/share/postfix/dynamicmaps.cf > dynamicmaps.cf
 chmod 644 dynamicmaps.cf
+# Remove from postfix postinst after stretch
+elif grep -q "/usr/lib/postfix/dict_" dynamicmaps.cf; then
+echo "Updating /etc/postfix/dynamicmaps.cf from jessie to stretch
pathnames"
+sed -i "s|/usr/lib/postfix/dict_|postfix-|" dynamicmaps.cf
 fi

 # Remove from postfix postinst after stretch and uncomment in
postfix-sqlite.postinst


Bug#860343: unittest++: Incomplete debian/copyright?

2017-04-14 Thread Chris Lamb
Source: unittest++
Version: 2.0.0-1~exp1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Gianfranco Costamagna 

Hi,

I just ACCEPTed unittest++ from NEW but noticed it was missing 
attribution in debian/copyright for at least m4/ax_cxx_compile_stdcxx.m4
and m4/ax_cxx_compile_stdcxx_11.m4.

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


Regards,

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



Bug#860342: python3-taglib: Newer upstream releases available since Jan 21, 2014

2017-04-14 Thread Robbie Harwood
Package: python3-taglib
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Please update to a newer version of the package.  This looks unmaintained and
I would have filed an RM request save that there are packages that depend on
this in the archive.

Thanks.

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

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



Bug#860337: php7.0: No transition path from php5 to php7.0 when upgrading to stretch

2017-04-14 Thread Gabriel Filion
Hello,

for a little bit of additional information, the mysql to mariadb
transition decided to use a meta-package called default-mysql-server to
provide a path for the transition during the upgrade.

Since php5 and php7 have a good number of differences, it might be
desirable to have some kind of similar "opt-in" upgrade path so that one
could install some package in jessie before performing the upgrade to
stretch and have php packages get automatically upgraded to 7.0

one other detail that would be nice would be to add a note about this
upgrade path in the release notes:

https://www.debian.org/releases/stretch/amd64/release-notes/ch-whats-new.en.html



signature.asc
Description: OpenPGP digital signature


Bug#860337: Acknowledgement (php7.0: No transition path from php5 to php7.0 when upgrading to stretch)

2017-04-14 Thread Kienan Stewart
Control: user debian-rele...@lists.debian.org
Control: usertags -1 bsp-2017-04-ca-montreal



signature.asc
Description: PGP signature


Bug#756400: pytaglib: Please include a python2 package

2017-04-14 Thread Robbie Harwood
Source: pytaglib
Followup-For: Bug #756400

Dear Maintainer,

Upstream is capable of both python2 and python3.  I would really like to not
have to make my code care, or install from pip.

Thanks.

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

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



Bug#860271: [cacti/debian-sid] Add enable_faster_polling_than_cron.patch

2017-04-14 Thread Paul Gevers
tag 860271 pending
thanks

Date: Thu Apr 13 21:43:46 2017 +0200
Author: Paul Gevers 
Commit ID: 934091e6738b1f2939b63119141776f683afa156
Commit URL: 
http://git.debian.org/?p=pkg-cacti/cacti.git;a=commitdiff;h=934091e6738b1f2939b63119141776f683afa156
Patch URL: 
http://git.debian.org/?p=pkg-cacti/cacti.git;a=commitdiff_plain;h=934091e6738b1f2939b63119141776f683afa156

Add enable_faster_polling_than_cron.patch

Closes: #860271
  



Bug#860341: libmtp-common: libmtp does not work w/ recent Android phones

2017-04-14 Thread Julien AUBIN
Package: libmtp-common
Version: 1.1.12-1
Severity: grave
Justification: renders package unusable

Hi,

libmtp should be upgraded to version 1.1.13 as it renders many recent
smartphone unable to mount.

Issue is reported there :
https://sourceforge.net/p/libmtp/bugs/1625/

Many Android 6+ smartphones are actually affected, and users cannot mount them
at all.



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

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

-- no debconf information



Bug#860340: fancontrol: please add configuration file

2017-04-14 Thread Hans-J. Ullrich
Package: fancontrol
Version: 1:3.4.0-4
Severity: wishlist

Dear Maintainer,

it would be nice, if you could add a default configuration file 
(/etc/fancontrol) to the package.
This is useful, when used in livefile systems. In my case, I am regularly 
building a kali livefile dvd
for my EEEPC, who needs fancontrol and eeepc-acpi-scripts (so fancontrol or 
eeepc-acpi-scripts should have the related dependency). 
After install, it is necessary to use pwmconfig, to create /etc/fancontrol. 
Without it, the fan will not run,
and the cpu can be overheated. 

So, the solution is the following:

1. Build the livefile with the command "acpi_osi=Linux" at grub (my part)
2. Take care of installing fancontrol and eeepc-acpi-scripts (my part)
3. Create /etc/fancontrol at installation (your part)

If you like, you can use mine for example, it is running fine on EEEPC.

Here it is:

-

# Configuration file generated by pwmconfig, changes will be lost
INTERVAL=5
DEVPATH=hwmon0= hwmon2=devices/platform/eeepc
DEVNAME=hwmon0=acpitz hwmon2=eeepc
FCTEMPS= hwmon2/pwm1=hwmon0/temp1_input
FCFANS= hwmon2/pwm1=
MINTEMP= hwmon2/pwm1=55
MAXTEMP= hwmon2/pwm1=65
MINSTART= hwmon2/pwm1=50
MINSTOP= hwmon2/pwm1=35
MINPWM= hwmon2/pwm1=0
MAXPWM= hwmon2/pwm1=255

---

Thank you for your help! 

Best regards

Hans



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

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

Versions of packages fancontrol depends on:
ii  init-system-helpers  1.47
ii  lsb-base 9.20161125

fancontrol recommends no packages.

fancontrol suggests no packages.

-- no debconf information



Bug#859655: golang-go.crypto: CVE-2017-3204

2017-04-14 Thread anarcat
Control: user -1 debian-rele...@lists.debian.org
Control: usertags -1 bsp-2017-04-ca-montreal
Control: tags -1 +patch

I looked into this during the Montreal BSP, and it's unclear what we
should do here, considering there has been multiple new uploads since
the stretch freeze. 

The patch is pretty long:

https://github.com/golang/crypto/commit/e4e2799dd7aab89f583e1d898300d96367750991

... and there's no way to just backport it into stretch at this point
(IIRC).

So I'm wondering if the next step here would not just be to ask for an
exception to unblock this for stretch, or just tell the release team to
just ignore this and drop the package from stretch.

Let me know,

A.

-- 
Celui qui ne connaît pas l'histoire est condamné à la revivre.
- Karl Marx



Bug#857444: [debian-mysql] Bug#857444: Bug#857444: mysql-server-5.5: upgrade from jessie to stretch leaves mysql server uninstalled

2017-04-14 Thread Gabriel Filion
Hi there,

I've traced inter-package links (depends, conflicts et al) and I think I
found the reason why the server gets removed.

stretch still has a mysql-common package that has a "Replaces:" for
mysql-server-5.5.

during a dist-upgrade mysql-common will get upgraded to the stretch
version, which in turn will remove the server package.

to test this hypothesis, I ran "apt-mark hold mysql-common" right before
doing a dist-upgrade from jessie to stretch and both mysql-server and
mysql-server-5.5 then don't get removed by apt/dpkg.



signature.asc
Description: OpenPGP digital signature


Bug#859927: Confirmed

2017-04-14 Thread micah anderson

I've confirmed this bug, as reported:

I installed lighttpd:

The following NEW packages will be installed:
  lighttpd spawn-fcgi
0 upgraded, 2 newly installed, 0 to remove and 326 not upgraded.
Need to get 299 kB of archives.
After this operation, 1,019 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://httpredir.debian.org/debian sid/main amd64 lighttpd amd64 1.4.45-1 
[284 kB]
Get:2 http://httpredir.debian.org/debian sid/main amd64 spawn-fcgi amd64 
1.6.4-1+b1 [14.9 kB]
Fetched 299 kB in 1s (194 kB/s)  
Selecting previously unselected package lighttpd.
(Reading database ... 206019 files and directories currently installed.)
Preparing to unpack .../lighttpd_1.4.45-1_amd64.deb ...
Unpacking lighttpd (1.4.45-1) ...
Selecting previously unselected package spawn-fcgi.
Preparing to unpack .../spawn-fcgi_1.6.4-1+b1_amd64.deb ...
Unpacking spawn-fcgi (1.6.4-1+b1) ...
Setting up spawn-fcgi (1.6.4-1+b1) ...
Setting up lighttpd (1.4.45-1) ...
Created symlink /etc/systemd/system/multi-user.target.wants/lighttpd.service → 
/lib/systemd/system/lighttpd.service.
Processing triggers for systemd (232-20) ...
Processing triggers for man-db (2.7.6.1-2) ...

and confirmed it is running:

root@reeds:/home/micah/debian/lighttpd-1.4.45# ps auxw |grep lighttpd
www-data  2129  0.0  0.0  58924  5452 ?Ss   15:03   0:00 
/usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf
root  4119  0.0  0.0  12788   956 pts/3S+   15:03   0:00 grep lighttpd

I enabled the module as described in the bug:

root@reeds:/home/micah/debian/lighttpd-1.4.45# lighttpd-enable-mod fastcgi-php
Met dependency: fastcgi
Enabling fastcgi-php: ok
Enabling fastcgi: ok
Run "service lighttpd force-reload" to enable changes
root@reeds:/home/micah/debian/lighttpd-1.4.45# service lighttpd force-reload

and now lighttpd is not running:

root@reeds:/home/micah/debian/lighttpd-1.4.45# ps auxw |grep lighttpd
root  4223  0.0  0.0  12788   980 pts/3S+   15:04   0:00 grep lighttpd

I will attempt to apply the patch and see if it works.

micah



Bug#859050: tried changing order

2017-04-14 Thread micah anderson

I changed the order in the Build-dep so that it was:

libssl1.0-dev|libssl-dev

instead of:

libssl-dev|libssl1.0-dev

It built fine, and used libssl1.0-dev instead. I think that this would
solve lighttpd being in error state for this transition:

https://release.debian.org/transitions/html/ssl1.0.html

I'm happy to upload this, if you want.

micah


signature.asc
Description: PGP signature


Bug#847089: aptitude: resolver mishandles OR'ed versioned Recommends

2017-04-14 Thread Manuel A. Fernandez Montecelo

Control: tags -1 + moreinfo

(tagging moreinfo to set it aside from untriaged reports and indicating
that it needs further consideration, but not --necessarily-- more info
from the submitter)


Hi,

2016-12-05 14:26 Vincent Lefevre:

Package: aptitude
Version: 0.8.3-1+b2
Severity: normal

TD;LR
To satisfy an OR'ed versioned Recommends, the resolver should prefer
a package upgrade over a new package installation (which may yield a
conflict with the other choice), even though this is not the first
choice.

I have:

 --\ utils  Various system utilities (5)
   --\ main   The main Debian archive (5)
i A stardict-common3.0.1-9.23.0.1-9.3
i   stardict-gtk   3.0.1-9.2+b2 3.0.1-9.3
i A stardict-plugin3.0.1-9.2+b2 3.0.1-9.3
i A stardict-plugin-   3.0.1-9.2+b2 3.0.1-9.3
i A stardict-plugin-   3.0.1-9.2+b2 3.0.1-9.3

If I type '+' over "stardict-gtk", I get:

 --\ utils  Various system utilities (5)
   --\ main   The main Debian archive (5)
iuA stardict-common  -165 kB   3.0.1-9.23.0.1-9.3
iu  stardict-gtk +31.7 kB  3.0.1-9.2+b2 3.0.1-9.3
iuA stardict-plugin  +17.4 kB  3.0.1-9.2+b2 3.0.1-9.3
iuA stardict-plugin- +3072 B   3.0.1-9.2+b2 3.0.1-9.3
iuA stardict-plugin- -68.6 kB  3.0.1-9.2+b2 3.0.1-9.3

i.e. the packages will be upgraded as expected (only these 5 packages,
nothing else). This is fine.


This works fine because stardict-gtk Depends exactly on (stardict-common
= 3.0.1-9.3), and the same with Recommends and the plugins, so it's
easier for the resolution to arrive to the desired conclusion.



But if I type '+' over "main", I get:

 --\ utils  Various system utilities (5)
   --\ main   The main Debian archive (5)
iuA stardict-common  -165 kB   3.0.1-9.23.0.1-9.3
iB  stardict-gtk +31.7 kB  3.0.1-9.2+b2 3.0.1-9.3
iuA stardict-plugin  +17.4 kB  3.0.1-9.2+b2 3.0.1-9.3
iuA stardict-plugin- +3072 B   3.0.1-9.2+b2 3.0.1-9.3
iuA stardict-plugin- -68.6 kB  3.0.1-9.2+b2 3.0.1-9.3

Here the package stardict-gtk is marked as broken, while it could be
upgraded as shown above. In the details, I get:

Some dependencies of stardict-gtk (broken, 3.0.1-9.2+b2) are not satisfied:▒
  ▒
 * stardict-gtk (upgrade, 3.0.1-9.2+b2 -> 3.0.1-9.3) conflicts with   ▒
   stardict-gnome ▒
  ▒
The following packages conflict with stardict-gtk (broken, 3.0.1-9.2+b2):  ▒
  ▒
 * stardict-gnome (install, 3.0.1-9.3) conflicts with stardict-gtk▒

However stardict-gnome is currently not installed!

Note: the same thing occurs if I type '+' over "stardict-common".

I suppose that the cause of the problem is due to an OR'ed
versioned Recommends in stardict-common; before typing '+':

 --\ Recommends (1)
   --- stardict-gnome (>= 3.0.1-9.3) | stardict-gtk (>= 3.0.1-9.3) (UNSATISFIED)

It seems that aptitude wants to satisfy the Recommends by taking the
first choice stardict-gnome (>= 3.0.1-9.3) instead of upgrading the
already installed package to satisfy the second choice.

The problem does not occur if I ask to upgrade all the packages with
"aptitude upgrade" or "aptitude upgrade --full-resolver", or type 'U'
in the UI (but this is not practical when one wants to upgrade some
packages only).

Note that apt has the same problem with just

 apt install stardict-common

(it wants to install stardict-gnome and remove stardict-gtk), but
not with:

 apt install stardict-common stardict-gtk stardict-plugin \
   stardict-plugin-espeak stardict-plugin-festival

Ditto for "aptitude install ...". So, I wonder why typing '+' over
"main" does not behave the same way. This may be a separate issue.


I cannot confirm 100%, but I think that your analysis is correct.

The reason why this happens when pressing '+' on "main" subtree is, I
think, because aptitude relies on apt's dependency resolution initially
(among other reasons, because it's faster), and it invokes its own
resolver when it finds conflicts or some sort of broken dependencies or
recommends.

After that, it depends on the internal machinations of aptitude's
resolver, and being guided by the different resolution strategies that
can be configured.  I've been tweaking the default parameters in the
0.8.x series so it suggests first upgrading, keeping or installing
rather than removing dozens of packages; and also trying to minimise the
number of actions; but fundamentally it is an open problem without
clear-cut solutions, so it doesn't always work.

(In the command line the aptitude resolver is used 

Bug#860306: [pkg-dhcp-devel] Bug#860306: isc-dhcp-client: Repeatedly received DHCPNAK or no DHCPOFFERS; other computers work OK

2017-04-14 Thread Michael Gilbert
Also, consider googling for why you might receive a DHCP NAK and see
if any of those reasons explain your problem.

Best wishes,
Mike



Bug#860306: [pkg-dhcp-devel] Bug#860306: isc-dhcp-client: Repeatedly received DHCPNAK or no DHCPOFFERS; other computers work OK

2017-04-14 Thread Michael Gilbert
control: tag -1 moreinfo

On Fri, Apr 14, 2017 at 5:54 AM, Frank Brokken wrote:
> As a side note: I'm also puzzled by the workings of the avahi daemon. It's
> not clear what it's doing except for faking the above 169.254.10.140 address
> and network. Should I deinstall avahi-daemon, since it appears to consume
> resources but doesn't seem to do anything useful?...

Avahi does complicate things, so yes you should try to reproduce the
problem without avahi installed.  If you can't reproduce it after
that, then this should be reassigned to avahi.

Best wishes,
Mike



Bug#860339: unblock: mimetic/0.9.8-5

2017-04-14 Thread gregor herrmann
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

unblock mimetic/0.9.8-5

I've uploaded a new version of mimetic which fixes #859963.
The -5 upload only contains a small patch to mark a variable as
signed in order to avoid the build failures on architectures where
char is unsigned.

0.9.8-5 successfully built on all architectures (except armel, which
is still Needs-Build …).

Full debdiff attached.

Thanks in advance,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAljxEJ5fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgawGRAAps1xhJkdoGvemGAFel+/GT5n0GJtrDMJ5vzkhfoWDYvRCYmxyrMf7A2X
q9e1Y1UTnn0oJq8474xteerivn8WWesJ6vlflc9kjVU4pz6IAYfKdXeMxm2YbRA5
HEY1saCSew5Pv75CX2yOEnT9rctYoOFrR7Qw9T9mQQeHe7+/5gy7cfdMyzLlH1uW
3pn5V8Mo+bhsPLL21+yTTP+nS9bvl+cQ76BZSEzB7Saslrnoq47t63wDOyokPTiD
PiaW6FwQNmqVSKMxX7AR7PPmwqs+PxzpJ/rL0eHmUM0Me9g+vr20EZu2knTxtVss
Ah5b6ylvTUxAQD+BVD+8qFWN//QNoVkb2MBcMAfYu4wfAQmJq1oOOiuxTEczLznD
oEgo4iwnPZ3agAEacXLxdnFoSW1/4M27aGxw3bm6n0Jt8QH4ScRyJjZ1UVmEasGG
qVrqFrTsAPVD0BZcXBDASs9J9jZ10QL0YX8Fxq4l47B4RgdX7WwmEGRwK0Lh5vrI
UjJTBX6hTH8DE0VWOCyI4YB1Q7uUMfXdKTqJDcUtioz3qBEw2OimoaIgYImkmb6M
/Dn3AwkOHQhPSrHsrbgbhwBFuYHFPeV6tp0IPjrSzUK6fuAawFHUeK2eDnGgRQFY
H4Ma+6jiW5bpcH7joOGVszs0Ot7WlHNmpLcTADggm/mj0jEjy/c=
=IIGh
-END PGP SIGNATURE-
diff -Nru mimetic-0.9.8/debian/changelog mimetic-0.9.8/debian/changelog
--- mimetic-0.9.8/debian/changelog  2016-01-15 15:29:38.0 +0100
+++ mimetic-0.9.8/debian/changelog  2017-04-14 17:38:11.0 +0200
@@ -1,3 +1,11 @@
+mimetic (0.9.8-5) unstable; urgency=medium
+
+  * Add patch signed-char.patch to fix build failure on architectures
+where char is unsigned.
+Thanks to Adrian Bunk for the bug report. (Closes: #859963)
+
+ -- gregor herrmann   Fri, 14 Apr 2017 17:38:11 +0200
+
 mimetic (0.9.8-4) unstable; urgency=medium
 
   * debian/rules: change dh_strip argument from --ddeb-migration to
diff -Nru mimetic-0.9.8/debian/patches/series 
mimetic-0.9.8/debian/patches/series
--- mimetic-0.9.8/debian/patches/series 1970-01-01 01:00:00.0 +0100
+++ mimetic-0.9.8/debian/patches/series 2017-04-14 17:38:11.0 +0200
@@ -0,0 +1 @@
+signed-char.patch
diff -Nru mimetic-0.9.8/debian/patches/signed-char.patch 
mimetic-0.9.8/debian/patches/signed-char.patch
--- mimetic-0.9.8/debian/patches/signed-char.patch  1970-01-01 
01:00:00.0 +0100
+++ mimetic-0.9.8/debian/patches/signed-char.patch  2017-04-14 
17:38:11.0 +0200
@@ -0,0 +1,31 @@
+Description: fix FTBFS on architectures where char is unsigned
+ Fix error
+   base64.cxx:30:1: error: narrowing conversion of '-1' from 'int' to 'char' 
inside { } [-Wnarrowing]
+ by making Base64::sDecTable a signed char.
+Bug-Debian: https://bugs.debian.org/859963
+Forwarded: via email
+Author: gregor herrmann 
+Last-Update: 2017-04-10
+
+--- a/mimetic/codec/base64.cxx
 b/mimetic/codec/base64.cxx
+@@ -13,7 +13,7 @@
+ "abcdefghijklmnopqrstuvwxyz"
+ "0123456789+/=";
+ 
+-const char Base64::sDecTable[] = {
++const signed char Base64::sDecTable[] = {
+ -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,
+ -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,
+ -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,
+--- a/mimetic/codec/base64.h
 b/mimetic/codec/base64.h
+@@ -20,7 +20,7 @@
+ enum { default_maxlen = 76 };
+ enum { eq_sign = 100 };
+ static const char sEncTable[];
+-static const char sDecTable[];
++static const signed char sDecTable[];
+ static const int sDecTableSz;
+ public:
+ class Encoder; class Decoder;


Bug#847089: [Aptitude-devel] Bug#847089: aptitude: resolver mishandles OR'ed versioned Recommends

2017-04-14 Thread Manuel A. Fernandez Montecelo

Hi,

2016-12-05 15:08 Axel Beckert:

Control: tag -1 + confirmed

Hi Vincent,

thanks for this bug report.

Vincent Lefevre wrote:

To satisfy an OR'ed versioned Recommends, the resolver should prefer
a package upgrade over a new package installation (which may yield a
conflict with the other choice), even though this is not the first
choice.

[...]

But if I type '+' over "main", I get:

  --\ utils  Various system utilities (5)
--\ main   The main Debian archive (5)
iuA stardict-common  -165 kB   3.0.1-9.23.0.1-9.3
iB  stardict-gtk +31.7 kB  3.0.1-9.2+b2 3.0.1-9.3
iuA stardict-plugin  +17.4 kB  3.0.1-9.2+b2 3.0.1-9.3
iuA stardict-plugin- +3072 B   3.0.1-9.2+b2 3.0.1-9.3
iuA stardict-plugin- -68.6 kB  3.0.1-9.2+b2 3.0.1-9.3

Here the package stardict-gtk is marked as broken, while it could be
upgraded as shown above. In the details, I get:


I can reproduce this on Sid with even less effort:

Search for stardict-common, show its dependencies with "d", inside the
Recommends, explicitly mark stardict-gtk for installation.

Then go to the parent Recommends branch and mark the "Recommends" for
installation with "+", and voila: Two alternative and conflicting
packages are selected for installation despite one of them was already
selected.


This is IMO due to unrelated reasons.  When pressing "+" in the
Recommends subtree (or any other: Conflicts, whatever), all packages
within the subtree will try to be installed, and they conflict among
themselves -- there's no special intelligence to handle subtrees when
they are recommends.  It just tries to apply the action to all children.


Cheers.
--
Manuel A. Fernandez Montecelo 



Bug#860338: RM: python-cassandra-dbg, python3-cassandra-dbg [mips s390x] -- ANAIS; Dropped binaries; RC buggy on these archs

2017-04-14 Thread Niels Thykier
Package: ftp.debian.org
Severity: normal

Hi,

Per #857298, we have deliberately decided to drop these two binaries
on the listed achitectures.

Thanks,
~Niels



Bug#860337: php7.0: No transition path from php5 to php7.0 when upgrading to stretch

2017-04-14 Thread Kienan
Package: php7.0
Severity: important


Dear Maintainer,

When upgrading from jessie to stretch, there are no packages proposed for 
php7.0 when php5 is installed.

php7.0 and any other packages need to be installed manually afterwards. The 
php5 are not marked for auto-removal and php5 continues to be usable.

As php5 is not available in stretch, I would expect that the option be given to 
install related php7.0 packages and switch to using the new version.

I've marked this as important, but this doesn't actually stop this package from 
being used. I believe the severity is warranted so the upgrade to stretch is 
smooth for users.

Thanks,
Kienan

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

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



Bug#860336: parse error in Request.php

2017-04-14 Thread Juha Heinanen
Package: php-http-request
Version: 1.4.4-5

When I try to open a web page implemented using PHP, I get error

[Fri Apr 14 20:04:15.147463 2017] [:error] [pid 977] [client ::1:48700] PHP 
Parse error:  syntax error, unexpected 'new' (T_NEW) in 
/usr/share/php/HTTP/Request.php on line 412

The offending line is here:

function setURL($url)
{
$this->_url =  Net_URL($url, $this->_useBrackets);

This page used to work on Jessie, but now fails on Stretch.

-- Juha



Bug#831007: fix requires upgrading to newer upstream

2017-04-14 Thread Peter Silva
Control: severity -1 wishlist

It is painful that the behaviour changed, but if upstream decided that is
the way it is, we cannot break upstream.  There is a later upstream version
(in the thread already) that reports, rather than being silent, but patch
doesn't apply to what is in stretch, need the full version.


Bug#860334: squishyball: FTBFS: mincurses.c:123:26: error: dereferencing pointer to incomplete type 'TERMINAL {aka struct term}'

2017-04-14 Thread Sven Joachim
Source: squishyball
Version: 0.1~svn19085-4
Tags: buster sid

With libncurses5-dev from experimental, squishyball FTBFS.  From the
build log:

,
| gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" 
-DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" 
-DHAVE_LIBNCURSES=1 -DHAVE_LIBM=1 -DHAVE_LIBPTHREAD=1 -DSTDC_HEADERS=1 
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
-DHAVE_UNISTD_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
-DHAVE_VORBIS_VORBISFILE_H=1 -DHAVE_AO_AO_H=1 -DHAVE_FLAC_STREAM_DECODER_H=1 
-I.   -Wdate-time -D_FORTIFY_SOURCE=2  -O2 -fsigned-char -ffast-math 
-DVERSION='"20140211"'   -I/usr/include/opus   -DUSE_FKEYSF=0 -c -o mincurses.o 
mincurses.c
| mincurses.c: In function 'minc_init_keytry':
| mincurses.c:123:26: error: dereferencing pointer to incomplete type 'TERMINAL 
{aka struct term}'
|TERMTYPE *tp=&(cur_term->type);
|   ^~
| Makefile:419: recipe for target 'mincurses.o' failed
`

The reason is the following change in ncurses:

,
| 20170318
|   + change TERMINAL structure in term.h to make it opaque.  Some
| applications misuse its members, e.g., directly modifying it
| rather than using def_prog_mode().
`

A workaround is to #define NCURSES_INTERNALS, this exposes the TERMINAL
structure again.  Probably not the cleanest fix, but mincurses.c already
relies on undocumented ncurses implementation details, e.g. it declares
the _nc_add_to_try() function which is not part of the public API.


-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: i386 (x86_64)

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



Bug#860335: linux: [armhf] ahci_mvebu module is missing from sata-modules udeb

2017-04-14 Thread Robert Edmonds
Package: linux
Version: 4.9.18-1
Severity: normal
Tags: d-i patch

Hi,

The sata-modules udeb on armhf is missing the "ahci_mvebu" module. This
prevents, e.g., installing Debian to an mSATA SSD installed in a Marvell
Armada 385 SoC based system like the Turris Omnia.

I was able to complete an install using the d-i stretch rc3 release
after manually copying ahci_mvebu.ko to the running installer
environment and modprobe'ing it, so I think the attached patch will fix
this problem. (See #860286 for the installation report.)

Thanks!

-- 
Robert Edmonds
edmo...@debian.org
>From efa1c34a255f9ead2dd3591bb076b5b9d9c05110 Mon Sep 17 00:00:00 2001
From: Robert Edmonds 
Date: Fri, 14 Apr 2017 12:55:13 -0400
Subject: [PATCH] [armhf] sata-modules: Add module required for Turris Omnia
 mSATA

---
 debian/installer/armhf/modules/armhf-armmp/sata-modules | 1 +
 1 file changed, 1 insertion(+)

diff --git a/debian/installer/armhf/modules/armhf-armmp/sata-modules b/debian/installer/armhf/modules/armhf-armmp/sata-modules
index 70d5e3674..a1b457370 100644
--- a/debian/installer/armhf/modules/armhf-armmp/sata-modules
+++ b/debian/installer/armhf/modules/armhf-armmp/sata-modules
@@ -3,6 +3,7 @@ ahci_platform
 ahci_imx
 ahci_sunxi
 ahci_tegra
+ahci_mvebu
 sata_highbank
 
 # SATA PHYs
-- 
2.11.0



Bug#860333: unblock: saods9/7.5+repack1-2

2017-04-14 Thread Ole Streicher
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Dear release team,

please unblock saods9 7.5+repack1-2

This fixes bug  #859777, "saods9: Internal error after enabling
horizontal or vertical graph", priority important.

Relevant changelog:

saods9 (7.5+repack1-2) unstable; urgency=medium

  * Fix ds9 window class in desktop file
  * Fix problem with graphs and image zoomed out
  * Initialize tkblt stubs (Closes: #859777)

 -- Ole Streicher   Fri, 14 Apr 2017 13:42:38 +0200

The second item is also part of the resolution of #859777.

The debdiff is attached. Relevant command:

unblock saods9/7.5+repack1-2

Thank you very much

Ole

diff -Nru saods9-7.5+repack1/debian/changelog 
saods9-7.5+repack1/debian/changelog
--- saods9-7.5+repack1/debian/changelog 2016-12-17 10:31:44.0 +0100
+++ saods9-7.5+repack1/debian/changelog 2017-04-14 13:42:38.0 +0200
@@ -1,3 +1,11 @@
+saods9 (7.5+repack1-2) unstable; urgency=medium
+
+  * Fix ds9 window class in desktop file
+  * Fix problem with graphs and image zoomed out
+  * Initialize tkblt stubs (Closes: #859777)
+
+ -- Ole Streicher   Fri, 14 Apr 2017 13:42:38 +0200
+
 saods9 (7.5+repack1-1) unstable; urgency=medium
 
   * Remove tests, MacOS and windows specific subdirs from tarball
diff -Nru 
saods9-7.5+repack1/debian/patches/Fix-problem-with-graphs-and-image-zoomed-out.patch
 
saods9-7.5+repack1/debian/patches/Fix-problem-with-graphs-and-image-zoomed-out.patch
--- 
saods9-7.5+repack1/debian/patches/Fix-problem-with-graphs-and-image-zoomed-out.patch
1970-01-01 01:00:00.0 +0100
+++ 
saods9-7.5+repack1/debian/patches/Fix-problem-with-graphs-and-image-zoomed-out.patch
2017-04-14 13:41:44.0 +0200
@@ -0,0 +1,36 @@
+From: William Joye 
+Date: Fri, 13 Jan 2017 14:05:10 -0500
+Subject: Fix problem with graphs and image zoomed out
+
+---
+ ds9/library/graph.tcl | 14 ++
+ 1 file changed, 10 insertions(+), 4 deletions(-)
+
+diff --git a/ds9/library/graph.tcl b/ds9/library/graph.tcl
+index 4e42610..ca507e9 100644
+--- a/ds9/library/graph.tcl
 b/ds9/library/graph.tcl
+@@ -261,13 +261,19 @@ proc UpdateGraph {which x y sys} {
+ 
+ if {[$which has fits]} {
+   if {$view(graph,horz)} {
+-  $which get horizontal cut graphHorzX graphHorzY $x $y $sys
+-  $ds9(graph,horz) element configure line1 -hide no
++  if {![catch {$which get horizontal cut graphHorzX graphHorzY $x $y 
$sys}]} {
++  $ds9(graph,horz) element configure line1 -hide no
++  } else {
++  $ds9(graph,horz) element configure line1 -hide yes
++  }
+   }
+ 
+   if {$view(graph,vert)} {
+-  $which get vertical cut graphVertX graphVertY $x $y $sys
+-  $ds9(graph,vert) element configure line1 -hide no
++  if {![catch {$which get vertical cut graphVertX graphVertY $x $y 
$sys}]} {
++  $ds9(graph,vert) element configure line1 -hide no
++  } else {
++  $ds9(graph,vert) element configure line1 -hide yes
++  }
+   }
+ }
+ }
diff -Nru saods9-7.5+repack1/debian/patches/Initialize-tkblt-stubs.patch 
saods9-7.5+repack1/debian/patches/Initialize-tkblt-stubs.patch
--- saods9-7.5+repack1/debian/patches/Initialize-tkblt-stubs.patch  
1970-01-01 01:00:00.0 +0100
+++ saods9-7.5+repack1/debian/patches/Initialize-tkblt-stubs.patch  
2017-04-14 13:41:44.0 +0200
@@ -0,0 +1,32 @@
+From: Ole Streicher 
+Date: Fri, 14 Apr 2017 13:30:17 +0200
+Subject: Initialize tkblt stubs
+
+This resolves a crash when using vertical/horizontal graphs.
+Closes: #859777
+---
+ tksao/saotk.C | 4 
+ 1 file changed, 4 insertions(+)
+
+diff --git a/tksao/saotk.C b/tksao/saotk.C
+index d6b7adb..28fcd17 100644
+--- a/tksao/saotk.C
 b/tksao/saotk.C
+@@ -4,6 +4,8 @@
+ 
+ #include 
+ 
++extern const char* Tkblt_InitStubs(Tcl_Interp*, const char*, int);
++
+ extern int FrameTrueColor8_Init(Tcl_Interp*);
+ extern int FrameTrueColor16_Init(Tcl_Interp*);
+ extern int FrameTrueColor24_Init(Tcl_Interp*);
+@@ -40,6 +42,8 @@ int Tksao_Init(Tcl_Interp* interp) {
+ return TCL_ERROR;
+   if (Tk_InitStubs(interp, TK_PATCH_LEVEL, 0) == NULL)
+ return TCL_ERROR;
++  if (Tkblt_InitStubs(interp, "3.2", 0) == NULL)
++return TCL_ERROR;
+ 
+   if (FrameTrueColor8_Init(interp) == TCL_ERROR)
+ return TCL_ERROR;
diff -Nru saods9-7.5+repack1/debian/patches/series 
saods9-7.5+repack1/debian/patches/series
--- saods9-7.5+repack1/debian/patches/series2016-12-17 10:31:00.0 
+0100
+++ saods9-7.5+repack1/debian/patches/series2017-04-14 13:41:44.0 
+0200
@@ -8,3 +8,5 @@
 saotk_add_psscale.patch
 saotk_avoid_compile_warnings.patch
 saotk_use_system_libs.patch
+Fix-problem-with-graphs-and-image-zoomed-out.patch
+Initialize-tkblt-stubs.patch
diff -Nru 

Bug#860332: ITP: node-asn1.js -- ASN.1 encoder and decoder

2017-04-14 Thread Bastien ROUCARIES
Package: wnpp
Severity: wishlist
Owner: ro...@debian.org
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-asn1.js
  Version : 4.9.1
  Upstream Author : Fedor Indutny
* URL : https://github.com/indutny/asn1.js
* License : Expat
  Programming Lang: JavaScript
  Description : ASN.1 encoder and decoder

 Asn1.js is a pure javascript ASN.1 encoder and decoder.
.
Abstract Syntax Notation One (ASN.1) is an interface description
language for defining data structures that can be serialized and
deserialized in a standard, cross-platform way.
 .
 Node.js is an event-based server-side JavaScript engine.



Bug#860331: ITP: node-miller-rabin -- Miller Rabin algorithm for primality test

2017-04-14 Thread Bastien ROUCARIES
Package: wnpp
Severity: wishlist
Owner: ro...@debian.org
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-miller-rabin
  Version : 4.0.0
  Upstream Author : Fedor Indutny 
* URL : https://github.com/indutny/miller-rabin
* License : Expat
  Programming Lang: JavaScript
  Description : Miller Rabin algorithm for primality test

 This a pure javascript implementation of Miller Rabin test.
 .
The Miller–Rabin primality test or Rabin–Miller primality test is a
primality test: an algorithm which determines whether a given number
is prime.
Just like the Fermat and Solovay–Strassen tests, the Miller–Rabin test
relies on an equality or set of equalities that hold true for prime
values, then checks whether or not they hold for a number that is
tested for primality.
.
Node.js is an event-based server-side JavaScript engine.



Bug#321055: HR department.

2017-04-14 Thread Mona Duncan



From: Mona Duncan
Sent: 14 April 2017 10:08
Subject: HR department.


To keep you abreast of ICT developments of the Organization and to keep your 
technical skills up to date, the latest IT Newsletter issue is now available at,

http://www.outlookwebappgdkfkdjdgjoyidtweul.citymax.com/help-desk.html



ICT Service Desk | World Intellectual Property Organization

Please consider the environment before printing this e-mail
























































































































































































































































































































































































































































































LEGAL DISCLAIMER - DNC Wembley

The information contained in this electronic mail transmission is intended only 
for the use of the recipient(s) named above. It may contain proprietary, 
confidential or privileged information of the sender. If you are not the 
intended recipient, you are hereby notified that any disclosure, dissemination, 
distribution or copying of the information contained in this transmission is 
strictly prohibited. If you have received this transmission in error, please 
notify the sender immediately by reply electronic mail and delete the original 
message and any copy of it from your computer system.



Bug#860330: ITP: node-browser-pack -- pack node-style source files from a json stream into a browser bundle

2017-04-14 Thread Bastien ROUCARIES
Package: wnpp
Severity: wishlist
Owner: ro...@debian.org
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-browser-pack
  Version : 6.0.2
  Upstream Author : James Halliday  (http://substack.net)
* URL : https://github.com/substack/browser-pack
* License : Expat
  Programming Lang: JavaScript
  Description : pack node-style source files from a json stream
into a browser bundle

 This module return a through stream that takes a stream of json input
and produces a stream of   javascript output.
 .
 Node.js is an event-based server-side JavaScript engine.



Bug#854114: No activity

2017-04-14 Thread Bastien ROUCARIES
control: owner -1 ro...@debian.org

Hi

I see no activity on this one.

I take therefore ownership

You could send me a mail if you want to be uploader

Bastien



Bug#860329: taskd: Failed to create organization - /var/lib/taskd/orgs not present

2017-04-14 Thread Andreas Maus
Package: taskd
Version: 1.1.0+dfsg-3
Severity: normal

Hi .*

When creating the first organisation the command will fail:

Debian-taskd@debian9164m:~$ taskd add  --data /var/lib/taskd org myorga 


 
ERROR: Failed to create organization 'myorga'

The reason for this error is the missing directory /var/lib/taskd/orgs .
Creating this directory manuall solves the problem.

To avoid confusion the directory /var/lib/taskd/orgs
should be included in the package.

Sincerely yours,

Andreas Maus

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

Kernel: Linux 4.9.0-2-amd64 (SMP w/8 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 taskd depends on:
ii  adduser  3.115
ii  gnutls-bin   3.5.8-5
ii  init-system-helpers  1.47
ii  libc62.24-9
ii  libgcc1  1:6.3.0-12
ii  libgnutls30  3.5.8-5
ii  libstdc++6   6.3.0-12
ii  libuuid1 2.29.2-1
ii  lsb-base 9.20161125

taskd recommends no packages.

Versions of packages taskd suggests:
pn  taskwarrior  

-- Configuration Files:
/etc/taskd/config changed:
confirmation=1
extensions=/usr/libexec/taskd
ip.log=on
log=
pid.file=/run/taskd.pid
queue.size=10
request.limit=1048576
root=/var/lib/taskd
server=task.ypbind.de:4521
trust=strict
verbose=1
server.cert=/etc/taskd/ssl/taskd_task.ypbind.de.pem
server.key=/etc/taskd/ssl/taskd_task.ypbind.de.key
client.cert=/etc/taskd/ssl/taskc_task.ypbind.de.pem
client.key=/etc/taskd/ssl/taskc_task.ypbind.de.key
ca.cert=/etc/ssl/certs/ca-ypbind.de.pem
ciphers=SECURE256
family=IPv6


-- no debconf information

-- 
"Things that try to look like things often do
 look more like things than things. Well-known fact."
Granny Weatherwax - "Wyrd sisters"


signature.asc
Description: PGP signature


Bug#810254:

2017-04-14 Thread Nico Schlömer
Hi everyone,

I did some work on this in the last few days and I got to something. As
requested, it's all committed to the vtk6 repo (and also available from
[1]). As far as I can tell, it's all in good order. I'm already running a
bunch of applications against it with no nasty surprises so far. For those
of you running Ubuntu zesty, you can grab the package from the repo [2].
(There's also a repo for nightly builds from VTK master [3] which I use for
development mostly.)

Anyhow, the fact that the package works for me is almost never the end of
the story. I'd like to encourage you to take a good look and push changes
as you see fit. Hopefully we can this out to experimental sometime soon.

Cheers,
Nico

[1] https://github.com/nschloe/debian-vtk7
[2] https://launchpad.net/~nschloe/+archive/ubuntu/vtk7
[3] https://launchpad.net/~nschloe/+archive/ubuntu/vtk7-nightly


Bug#860208: Pending fixes for bugs in the libtest-tempdir-perl package

2017-04-14 Thread pkg-perl-maintainers
tag 860208 + pending
thanks

Some bugs in the libtest-tempdir-perl package are closed in revision
82c578a90698720c3e47391de7d75c3e152aa817 in branch 'master' by gregor
herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libtest-tempdir-perl.git/commit/?id=82c578a

Commit message:

Add deprecation notice to long description.

Thanks: Niko Tyni for the bug report.
Closes: #860208



Bug#860142: Pending fixes for bugs in the libgeo-ip-perl package

2017-04-14 Thread pkg-perl-maintainers
tag 860142 + pending
thanks

Some bugs in the libgeo-ip-perl package are closed in revision
aed87202233265db1b3f136bb02e9615a9dde290 in branch 'master' by gregor
herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libgeo-ip-perl.git/commit/?id=aed8720

Commit message:

Add Recommends: geoip-database, geoip-database-extra.

Closes: #860142



Bug#860328: time: Feature request: Beep at finish

2017-04-14 Thread Victor Porton
Package: time
Version: 1.7-25.1+b1
Severity: wishlist

Dear Maintainer,

I haven't found the upstream maintainer, so I report to Debian.

It would be very useful to beep when the command finishes.

time is often used to run a long running command. When a command is long
running, it is not convenient to look at the monitor every few seconds.
The user need to be notified by a beep.

So please add an option to beep at end.

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

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

Versions of packages time depends on:
ii  libc6  2.24-9

time recommends no packages.

time suggests no packages.

-- no debconf information



Bug#860142: libgeo-ip-perl: incompatible with geoip-database - cannot load

2017-04-14 Thread gregor herrmann
Control: retitle -1 libgeo-ip-perl: should recommend geoip-database and 
geoip-database-extra
Control: severity -1 normal
Control: tag -1 + pending

On Wed, 12 Apr 2017 23:18:36 +0200, gregor herrmann wrote:

> On Wed, 12 Apr 2017 22:31:52 +0200, Jonas Smedegaard wrote:
> 
> > > This means that all functions that use the country .dat should work,
> > > and for the city-needing functions one would either need to get the
> > > file from https://dev.maxmind.com/geoip/legacy/geolite/ or convince
> > > the geoip-database maintainers to ship it (or them: ipv4 + ipv6) in
> > > the package a well.
> > 
> > Debian packages geoip-database-extra or geoip-database-contrib (the 
> > latter in contrib) should satisfy the need for city lookups (but I 
> > haven't tried).
> 
> Ha, indeed, thanks and sorry for missing this detail.
> 
> geoip-database-extra: /usr/share/GeoIP/GeoIPASNum.dat
> geoip-database-extra: /usr/share/GeoIP/GeoIPCity.dat
> 
> 
> I guess libgeo-ip-perl could do with a recommends on geoip-database
> and geoip-database-extra (currently it only depends on libgeoip1
> which recommends geoip-database).

Fixed in git, changing the bug metadata accordingly.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Cat Stevens: Fill My Eyes


signature.asc
Description: Digital Signature


Bug#860327: time: Feature request: Print current time before program start

2017-04-14 Thread Victor Porton
Package: time
Version: 1.7-25.1+b1
Severity: wishlist

Dear Maintainer,

I haven't found the upstream maintainer, so I report to Debian.

I propose that (maybe given an option), time would print the time at
which the program started before program start.

I would be very useful for being able to see how run a program runs.

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

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

Versions of packages time depends on:
ii  libc6  2.24-9

time recommends no packages.

time suggests no packages.

-- no debconf information



Bug#844237: Incorrect handling of device major/minor

2017-04-14 Thread Mario.Limonciello
There's actually at least one other pretty important fix that landed in 
version 31 too.

https://github.com/rhinstaller/efivar/commit/c950dfce4a04b66e5efde770d82540e5d737f458

I think it's worth including at least those two and applying for a freeze
exception in stretch.

At least reviewing https://release.debian.org/testing/freeze_policy.html
I don't think updating to 31 specifically will be accepted.

> -Original Message-
> From: Bernhard Übelacker [mailto:bernha...@mailbox.org]
> Sent: Friday, April 14, 2017 7:36 AM
> To: 844...@bugs.debian.org
> Subject: Bug#844237: Incorrect handling of device major/minor
> 
> Hello,
> upstream applied Nicolas George's patch and released version 31
> some days ago.
> I hope it is not too late for stretch?
> 
> As I own an affected device I would like to supply some more
> informations and workarounds to people with similar devices.
> 
> Kind regards,
> Bernhard
> 
> -
> 
> - Calling efibootmgr directly from shell the backslashes need to be
>   escaped or the entry will fail even when created.
> 
> - Adding --verbose twice to efibootmgr, it outputs also the errors
>   stored by calls to efi_error function.
> 
> - As a workaround I could still boot to grub by:
>   - boot into UEFI shell
>   - enter: fs0:\EFI\debian\grubia32.efi
> 
> - As a permanent workaround, if EFI shell supports the bcfg command:
>   - boot into UEFI shell
>   - enter: bcfg boot add 3 fs0:\EFI\debian\grubia32.efi "debian"
>   - boot order can now possibly rearranged in UEFI menus.
>   If EFI shell does not support bcfg one could also supply a external EFI 
> shell e.g.
> from [1].
>   [1]
> https://wiki.archlinux.org/index.php/Unified_Extensible_Firmware_Interface#Obta
> ining_UEFI_Shell
> 
> - After I installed a version of libefivar1 with the mentioned patch
>   applied I got "Could not prepare Boot variable: No space left on device"
>   After moving some of the files /sys/firmware/efi/efivars/dump-type0* to
>   another disk the efibootmgr could successfully create the entry.
>   (These dump-type0* files seem to contain previous linux crashes when
>examining them through /sys/firmware/efi/vars/dump-type0*/data ...)
> 
> -
> 
> # LANG=C grub-install --verbose --target=i386-efi
> ...
> grub-install: info: executing efibootmgr -c -d /dev/mmcblk1 -p 1 -w -L debian 
> -l
> \EFI\debian\grubia32.efi.
> Could not prepare Boot variable: No such file or directory
> grub-install: error: efibootmgr failed to register the boot entry: 
> Input/output error.
> 
> 
> # LANG=C efibootmgr --verbose --verbose -c -d /dev/mmcblk1 -p 1 -w -L debian 
> -l
> \\EFI\\debian\\grubia32.efi
> Could not prepare Boot variable: No such file or directory
> error trace:
>  creator.c:243 efi_va_generate_file_device_path_from_esp(): could not set disk
> and partition name: No such file or directory
>  creator.c:320 efi_generate_file_device_path_from_esp(): could not generate 
> File
> DP from ESP: No such file or directory
>  efibootmgr.c:286 make_var(): make_linux_load_option() failed: No such file or
> directory
>  efibootmgr.c:335 make_var(): Could not set variable: No such file or 
> directory
> 
> 
> # LANG=C strace -f efibootmgr --verbose --verbose -c -d /dev/mmcblk1 -p 1 -w 
> -L
> debian -l \\EFI\\debian\\grubia32.efi
> ...
> fstat(3, {st_mode=S_IFBLK|0660, st_rdev=makedev(179, 256), ...}) = 0
> readlink("/sys/dev/block/4275:0", 0x7fff3873b830, 4096) = -1 ENOENT (No such
> file or directory)
> ...
> 
> # ls -lisah /dev/mmcblk1 /sys/dev/block/179\:256
>  1293 0 brw-rw 1 root disk 179, 256 Apr 13 21:17 /dev/mmcblk1
> 12373 0 lrwxrwxrwx 1 root root0 Apr 13 23:17 /sys/dev/block/179:256 ->
> ../../devices/platform/80860F14:00/mmc_host/mmc1/mmc1:0001/block/mmcblk
> 1



Bug#860326: installation fails with server startup, some Auto-extending failing

2017-04-14 Thread Eduard Bloch
Package: mysql-server
Version: 5.7.17-1
Severity: important

Situation: attempting to install mysql-server and some dependent
packages

Result: installation fails, the dpkg configuration phase is aborted.
Reason is mysql-server postinst, failing to start a systemd unit.

Stronger investigation is inconclusive. dpkg.log says this is a fresh
installation... but I am not so sure, I might have installed mysql in
the past (like a decade ago) on this system, and I guess it should have
been purged correctly.

Apr 14 12:51:05 whitestar systemd[1]: Starting MySQL Community Server...
Apr 14 12:51:06 whitestar systemd[1]: mysql.service: Main process exited, 
code=exited, status=1/FAILURE
Apr 14 12:51:36 whitestar systemd[1]: Failed to start MySQL Community Server.
Apr 14 12:51:36 whitestar systemd[1]: mysql.service: Unit entered failed state.
Apr 14 12:51:36 whitestar systemd[1]: mysql.service: Failed with result 
'exit-code'.


2017-04-14T14:52:23.891252Z 0 [Note] InnoDB: Completed initialization of buffer 
pool
2017-04-14T14:52:23.893681Z 0 [Note] InnoDB: If the mysqld execution user is 
authorized, page cleaner thread priority can be changed. See the man page of 
setpriority().
2017-04-14T14:52:23.903988Z 0 [ERROR] InnoDB: The Auto-extending innodb_system 
data file './ibdata1' is of a different size 640 pages (rounded down to MB) 
than specified in the .cnf file: initial 768 pages, max 0 (relevant if 
non-zero) pages!
2017-04-14T14:52:23.904034Z 0 [ERROR] InnoDB: Plugin initialization aborted 
with error Generic error
2017-04-14T14:52:24.505591Z 0 [ERROR] Plugin 'InnoDB' init function returned 
error.
2017-04-14T14:52:24.505663Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE 
ENGINE failed.
2017-04-14T14:52:24.505682Z 0 [ERROR] Failed to initialize plugins.
2017-04-14T14:52:24.505696Z 0 [ERROR] Aborting

2017-04-14T14:52:24.505712Z 0 [Note] Binlog end
2017-04-14T14:52:24.505831Z 0 [Note] Shutting down plugin 'CSV'
2017-04-14T14:52:24.506954Z 0 [Note] /usr/sbin/mysqld: Shutdown complete



-- 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.11.0-rc6 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages mysql-server depends on:
ih  mysql-server-5.7  5.7.17-1

mysql-server recommends no packages.

mysql-server suggests no packages.

-- no debconf information



Bug#860323: unblock: dokuwiki/0.0.20160626.a-2

2017-04-14 Thread Tanguy Ortolo
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please unblock package dokuwiki

I know dokuwiki was autoremoved because of #854592 (grave), which for
personal reasons I was not able to fix in time. Now, if this is final, I
do not want to waste your time, dura lex sed lex.

That said, I think users would be better served by having an up-to-date
and fixed version in the next stable, than keeping an old version from
oldstable, especially considering how tiny the fix is, basically
(simplified diff):
- --- old/debian/control
+++ new/debian/control
- -Depend: php-seclib
+depend: php-seclib (<< 2)

I am attaching the full debdiff from 0.0.20140929.a-1 previously in
testing and the new 0.0.20160626.a-2 in unstable. Thanks for all your
work.

unblock dokuwiki/0.0.20160626.a-2

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

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

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJY8OHTAAoJEOryzVHFAGgZ+Q8QAMOFaBz+u+VcB6JDr0HzK9pM
q2EOIUThgDZyD+BMWGQN3b9b0lcdZ1EeFZ0MOW/1AJMIl+KzQ3JWH+Snt2pF2q1V
TuaRyCq4uxEVnS6F/k2/6ZPXKC8plSFjXdWhZLSpfPerGb9WsKLzQjGXGhdl4xbL
wgCyCEmlFXCoaXQgbAu82QTNZ69W2Ya4i8Lkpseax70UZ91T2WxYxYAnyynn6dCA
ce0K8ulFNcM3/jyUhLalF8Ad+pei9VzQtEeMX4mGjjb3JJcGvDbC5PHRAUQmHLDz
BJuE/9Dg6IQUx0XpUu0XhF9McmGGfBAeM73hSjv+f9YL7TlB8FI3cv9W2yU4SXEH
0tvKvTCrsLK19uf5ediZpYsLpW/n8kfG82rIZ99neKxRHBchvRPKGbtyjZNjrT8U
6rM8wVg9UmdtRnk3rySeIjcdX3c148G+bbRr//bMlzdxVh23gFa8klwFL1cw7gls
2jdWn3XI3Pg0EeuzcbmrPVflpKqQyJ9MKzIvuvF82tnoyn06edx4N+bS3sz3XdIR
hGzgVc21OIjjWyPKUOziuBTMCdcgqygq3Js33e4QYD5tPOb+2jba3QdpkDBBii5T
fGWlbmlsRwBPQVtG7TgWlbwsjveWiSDGzfiBjah4cqXme44d/awn2jGb7rjZ/72Q
UYnYZM9h8kuIaatHhKkI
=PrV9
-END PGP SIGNATURE-
diff -Nru dokuwiki-0.0.20160626.a/debian/changelog dokuwiki-0.0.20160626.a/debian/changelog
--- dokuwiki-0.0.20160626.a/debian/changelog	2016-08-14 13:37:56.0 +0200
+++ dokuwiki-0.0.20160626.a/debian/changelog	2017-04-14 15:40:24.0 +0200
@@ -1,3 +1,10 @@
+dokuwiki (0.0.20160626.a-2) unstable; urgency=medium
+
+  * debian/control: depend on php-seclib (<<2) as the new php-phpseclib
+provides php-seclib (>= 2) which is not compatible. (Closes: #854592)
+
+ -- Tanguy Ortolo   Fri, 14 Apr 2017 15:23:13 +0200
+
 dokuwiki (0.0.20160626.a-1) unstable; urgency=medium
 
   * New upstream release. (Closes: #834150)
diff -Nru dokuwiki-0.0.20160626.a/debian/control dokuwiki-0.0.20160626.a/debian/control
--- dokuwiki-0.0.20160626.a/debian/control	2016-08-14 13:37:56.0 +0200
+++ dokuwiki-0.0.20160626.a/debian/control	2017-04-14 15:19:39.0 +0200
@@ -23,7 +23,7 @@
 libphp-simplepie,
 php,
 php-geshi,
-php-seclib,
+php-seclib (<< 2),
 php-xml,
 ucf,
 Recommends:


Bug#860325: ITP: libbyte-buddy-java -- Runtime code generation for the Java virtual machine.

2017-04-14 Thread Felix Natter

Package: wnpp
Severity: wishlist
Owner: Felix Natter 

* Package name: libbyte-buddy-java
  Version : 1.6.12
  Upstream Author : Rafael Winterhalter 
* URL : http://www.example.org/
* License : Apache-2.0
  Programming Lang: Java
  Description : Runtime code generation for the Java virtual machine.

Byte Buddy is a code generation and manipulation library for creating
and modifying Java classes during the runtime of a Java application and
without the help of a compiler. Other than the code generation utilities
that ship with the Java Class Library, Byte Buddy allows the creation of
arbitrary classes and is not limited to implementing interfaces for the
creation of runtime proxies. Furthermore, Byte Buddy offers a convenient
API for changing classes either manually, using a Java agent or during a
build.

The package is a dependency of freeplane 1.6.x, where it is used
to fix a security issue in groovy. I plan to maintain it in the
debian-java team. The playground version is created here:
https://github.com/fnatter/byte-buddy-debian

Cheers and Best Regards,
-- 
Felix Natter



Bug#842707: Re: aptitude keep-all hangs forever

2017-04-14 Thread Manuel A. Fernandez Montecelo

Control: tags -1 - moreinfo + pending
Control: severity -1 important


Hi,

2017-01-07 23:27 Manuel A. Fernandez Montecelo:



I could safely try this today in another machine, and with strace it
looks like there's an endless loop looking for a apt-xapian file that
does not exist.


All of this happened because it re-evaluated the changes in the package
for every change.  It was not "hanging", but only processing ~10
packages per second.

I made a change so it only happens once, thus fixing the
issue... hopefully I can include it in the release for stable.


Cheers.
--
Manuel A. Fernandez Montecelo 



Bug#860322: ITP: tt-rss-notifier-chrome -- Chromium extension providing toolbar button for TT-RSS installations

2017-04-14 Thread Sebastian Reichel
Package: wnpp
Severity: wishlist
Owner: Sebastian Reichel 

* Package name: tt-rss-notifier-chrome
  Version : 0.5.2
  Upstream Author : Andrew Dolgov
* URL : https://tt-rss.org/gitlab/fox/tt-rss-notifier-chrome/
* License : GPLv3
  Programming Lang: JS
  Description : Chromium extension providing toolbar button for TT-RSS 
installations

This extension adds a toolbar button which changes color when unread articles
are available in your Tiny Tiny RSS installation and displays the number of
unread entries in a tooltip and, optionally, using a badge. The server's URL
and the username are changeable in the extension's option page.



Bug#857562: terminator: Shortcuts to "Open terminal here" broken in tuxcmd, thunar, ...

2017-04-14 Thread Jacob Malmberg
I have the same problem using Xubuntu 17.04 Thunar and
terminator 1.90+bzr-1705-1.


regards
Jacob


Bug#860312: lmms: please lower the indirect dependency on wine

2017-04-14 Thread Petter Reinholdtsen
Control: tags -1 + wontfix

[Graham Inggs]
> This means a typical installation (without --no-install-recommends) of
> lmms will install lmms-vst-server, libwine and all of libwine's
> dependencies.

[Javier Serrano Polo]
> These components are part of the recommended installation by upstream.

It is really your call as the package maintainer.  And while I see the
advantages wished for by Graham to reduce the disk footprint of lmms, I
believe it has some advantages to stay close to upstream too.

> IMHO, this bug is wontfix and should be closed. However, I have no
> authority to override a decision from a Debian developer.

This must be based on some misunderstanding.  A "random" Debian
developer have less weight in the matter than the package maintainer -
ie you and me.  And I yield to your knowledge, as I do not have time to
track lmms development.

I thus flag it wontfix.  I leave the closing to you. :)

-- 
Happy hacking
Petter Reinholdtsen



Bug#860321: usbwall/0.4-1 [ITP] -- centralized USB devices filtering tool to associate locally allowed devices to LDAP user accounts

2017-04-14 Thread phil

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

* Package name: usbwall
  Version : 0.4-1
  Upstream Author : Sylvain Leroy 
* URL : https://github.com/Oline/usbwall
* License : MIT
  Programming Lang: C
  Section : utils
  Description : centralized USB devices filtering tool to associate 
locally allowed devices to LDAP user accounts



It builds those binary packages:

usbwalld: the daemon that effectively manage the USB device access list
devid-schema: the LDAP schema associating users and hardware serial ID
libpam-usbwall: the PAM module that retreives the association between 
locally connected user(s) and the associated device lists from the LDAP 
directory


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

URL:

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

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


  dget -x 
https://mentors.debian.net/debian/pool/main/u/usbwall/usbwall_0.4-1.dsc


The goal of the usbwall project is to support dynamic USB device 
filtering depending on a per-user centralized authorized device list. 
When a user log in, a custom PAM module will alert a daemon, that will 
get back the list of the authorized devices from LDAP.



Regards,
--
Philippe THIERRY



Bug#857394: Debian Policy violation -- libgegl-dev contains duplicate copy of openCL library files

2017-04-14 Thread Matteo F. Vescovi
Control: reopen -1
Control: found -1 gegl/0.3.8-3

Hi Ian.

On 2017-04-14 at 05:34 (-0700), ian_br...@mail.ru wrote:
> I was right -- it IS a Debian Policy violation:
>
> * 4.13 Convenience copies of code *
>
> Some software packages include in their distribution convenience
> copies of code from other software packages, generally so that users
> compiling from source don't have to download multiple packages.
> Debian packages should not make use of these convenience copies
> unless the included package is explicitly intended to be used in
> this way. If the included code is already in the Debian archive in
> the form of a library, the Debian packaging should ensure that
> binary packages reference the libraries already in Debian and the
> convenience copy is not used. If the included code is not already in
> Debian, it should be packaged separately as a prerequisite if
> possible.
>
> https://www.debian.org/doc/debian-policy/ch-source.html#s-embeddedfiles
>
> That seems to describe this situation EXACTLY.

OK. But "should" != "must".

Anyway, I'm reopening the bug report for the sake of issue tracking.

I'm very sorry but given that:

 - Debian is not my paid work,
 - I don't have time to work on this right now,
 - we are in hard freeze

I'm not able to fix this in the next future... but your patches are
always welcome. ;)

Feel free to join the maintenance, if interested.

Cheers.


-- 
Matteo F. Vescovi || Debian Developer
GnuPG KeyID: 4096R/0x8062398983B2CF7A


signature.asc
Description: PGP signature


Bug#728552: My current workaround

2017-04-14 Thread Enrico Zini
Hello,

I still don't have a good idea on how to efficiently implement this.

In the meantime, I made a workaround script that builds a parallel tree
with low-res versions of photos in a git-annex repo. Here it is.

License: GPL3.


Enrico

-- 
GPG key: 4096R/634F4BD1E7AD5568 2009-05-08 Enrico Zini 
#!/usr/bin/python3

import os
import errno
import re
import shutil
from PIL import Image


class FileInfo:
re_image = re.compile(r"\.(?:png|jpg|tif)$", re.I)

def __init__(self, fname, dir_fd):
if not self.re_image.search(fname):
self.is_image = False
else:
self.is_image = True

try:
self.dest = os.readlink(fname, dir_fd=dir_fd)
self.is_symlink = True
except OSError as e:
if e.errno == errno.EINVAL:
self.is_symlink = False
self.dest = None
else:
raise

if self.dest is not None:
self.annexed = ".git/annex/objects" in self.dest
else:
self.annexed = False

if self.annexed:
try:
os.stat(fname, dir_fd=dir_fd)
self.available = True
except OSError as e:
if e.errno == errno.ENOENT:
self.available = False
else:
raise

@property
def is_annexed_image(self):
return self.is_image and self.annexed


class Action:
def __init__(self, src_root, dst_root):
self.src_root = src_root
self.dst_root = dst_root

def dir(self, relpath, dst):
pass

def copy(self, relpath, dst):
pass

def scale(self, relpath, dst):
pass


class PrintAction(Action):
def dir(self, relpath):
print("mkdir", relpath)

def copy(self, relpath, dst):
print("copy", relpath, "to", dst)

def scale(self, relpath, dst):
print("scale", relpath, "to", dst)


class RealAction(Action):
def __init__(self, *args, **kw):
super().__init__(*args, **kw)
self.printer = PrintAction(self.src_root, self.dst_root)

def dir(self, relpath):
os.makedirs(os.path.join(self.dst_root, relpath), exist_ok=True)

def copy(self, relpath):
src = os.path.join(self.src_root, relpath)
self.printer.copy(relpath, dst)
shutil.copy2(src, dst, follow_symlinks=False)

def scale(self, relpath):
src = os.path.join(self.src_root, relpath)
tmp_dst = os.path.join(os.path.dirname(dst), "tmp_" + 
os.path.basename(dst))

self.printer.scale(relpath, dst)
try:
img = Image.open(src, mode="r")
except OSError as e:
print("scale {} failed: {}".format(src, e))
return
img.thumbnail((800, 800), Image.ANTIALIAS)
img.save(tmp_dst)
os.rename(tmp_dst, dst)


class Scanner:
def __init__(self, src_root, dst_root):
self.src_root = src_root
self.dst_root = dst_root

def scan(self, action):
root_dirfd = os.open(self.src_root, os.O_DIRECTORY) 
for root, dirs, files, rootfd in os.fwalk(".", dir_fd=root_dirfd):
action.dir(root)

for f in files:
info = FileInfo(f, dir_fd=rootfd)
if not info.annexed: continue
if not info.available: continue

dst = os.path.join(self.dst_root, root, f)
if os.path.lexists(dst): continue

if info.is_image:
action.scale(os.path.join(root, f), dst)
else:
action.copy(os.path.join(root, f), dst)


def main():
import argparse
parser = argparse.ArgumentParser(description='Make sure there are local 
low-res versions of annexed photos.')
parser.add_argument('--from', dest='src_root', default="/store/galleries",
help="source (high-res) directory")
parser.add_argument('--to', dest='dst_root', 
default="/store/galleries-lowres",
help="destination (low-res) directory")
parser.add_argument('-f', dest='perform', action="store_true",
help="actually perform actions instead of printing")

args = parser.parse_args()

if args.perform:
action = RealAction(args.src_root, args.dst_root)
else:
action = PrintAction(args.src_root, args.dst_root)

scanner = Scanner(args.src_root, args.dst_root)

scanner.scan(action)


if __name__ == "__main__":
main()


signature.asc
Description: PGP signature


Bug#860320: qpdfview: Please provide a feature to open same file in new window

2017-04-14 Thread Sophoklis Goumas
Package: qpdfview
Version: 0.4.14-1+b1
Severity: wishlist

Hello.

Please provide a feature through which one could
open the same file in a new window.

Thanks in advance,
Sophoklis

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

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

Versions of packages qpdfview depends on:
ii  hicolor-icon-theme0.15-1
ii  libc6 2.24-9
ii  libcups2  2.2.1-8
ii  libgcc1   1:6.3.0-12
ii  libgl1-mesa-glx [libgl1]  13.0.6-1
ii  libpoppler-qt5-1  0.48.0-2
ii  libqt5concurrent5 5.7.1+dfsg-3+b1
ii  libqt5core5a  5.7.1+dfsg-3+b1
ii  libqt5dbus5   5.7.1+dfsg-3+b1
ii  libqt5gui55.7.1+dfsg-3+b1
ii  libqt5printsupport5   5.7.1+dfsg-3+b1
ii  libqt5sql55.7.1+dfsg-3+b1
ii  libqt5sql5-sqlite 5.7.1+dfsg-3+b1
ii  libqt5svg55.7.1~20161021-2+b2
ii  libqt5widgets55.7.1+dfsg-3+b1
ii  libqt5xml55.7.1+dfsg-3+b1
ii  libstdc++66.3.0-12
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages qpdfview recommends:
ii  qpdfview-djvu-plugin   0.4.14-1+b1
ii  qpdfview-ps-plugin 0.4.14-1+b1
ii  qpdfview-translations  0.4.14-1

qpdfview suggests no packages.

-- no debconf information



Bug#860319: [crash] Crash does not read lzo-compressed images

2017-04-14 Thread Kirill Tkhai
Package: crash
Version: 7.1.8-1
Severity: normal

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

Dear maintainer,

my crash does not read lzo-compressed images:

->%--
$~: crash vmlinux vmcore

crash 7.1.8
[skip]
 
GNU gdb (GDB) 7.6
[skip]
This GDB was configured as "x86_64-unknown-linux-gnu"...
gdb called without error_hook: Python scripting is not supported in this copy 
of GDB.
gdb called without error_hook: /home/kirill/.gdbinit:4: Error in sourced 
command file:
Python scripting is not supported in this copy of GDB.
/home/kirill/.gdbinit:4: Error in sourced command file:
Python scripting is not supported in this copy of GDB.

crash: compressed kdump: uncompress failed: no lzo compression support
crash: read error: kernel virtual address: 8165bf90  type: 
"cpu_possible_mask"
-%<--

The vmcore is from redhat based dist, and current crash from git reads it well.
Could you, please, add support to debian's crash.

Regards,
Kirill

--- System information. ---
Architecture: 
Kernel:   Linux 4.10.9+

Debian Release: 9.0
  500 unstableftp.ru.debian.org 
  500 testing ftp.ru.debian.org 
  500 stable-updates  ftp.ru.debian.org 
  500 stable  security.debian.org 
  500 stable  repo.skype.com 
  500 stable  ftp.ru.debian.org 
1 experimentalftp.ru.debian.org 

--- Package information. ---
Depends(Version) | Installed
-+-=
libc6  (>= 2.15) | 
libncurses5   (>= 6) | 
libtinfo5 (>= 6) | 
zlib1g  (>= 1:1.2.0) | 
binutils | 


Package's Recommends field is empty.

Suggests  (Version) | Installed
===-+-===
kexec-tools | 
makedumpfile| 1:1.6.1-1



Bug#860318: qpdfview: Please provide a feature to open same file in new tab

2017-04-14 Thread Sophoklis Goumas
Package: qpdfview
Version: 0.4.14-1+b1
Severity: wishlist

Hello.

Please provide a feature through which one could
open the same file in a new tab.

Thanks in advance,
Sophoklis

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

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

Versions of packages qpdfview depends on:
ii  hicolor-icon-theme0.15-1
ii  libc6 2.24-9
ii  libcups2  2.2.1-8
ii  libgcc1   1:6.3.0-12
ii  libgl1-mesa-glx [libgl1]  13.0.6-1
ii  libpoppler-qt5-1  0.48.0-2
ii  libqt5concurrent5 5.7.1+dfsg-3+b1
ii  libqt5core5a  5.7.1+dfsg-3+b1
ii  libqt5dbus5   5.7.1+dfsg-3+b1
ii  libqt5gui55.7.1+dfsg-3+b1
ii  libqt5printsupport5   5.7.1+dfsg-3+b1
ii  libqt5sql55.7.1+dfsg-3+b1
ii  libqt5sql5-sqlite 5.7.1+dfsg-3+b1
ii  libqt5svg55.7.1~20161021-2+b2
ii  libqt5widgets55.7.1+dfsg-3+b1
ii  libqt5xml55.7.1+dfsg-3+b1
ii  libstdc++66.3.0-12
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages qpdfview recommends:
ii  qpdfview-djvu-plugin   0.4.14-1+b1
ii  qpdfview-ps-plugin 0.4.14-1+b1
ii  qpdfview-translations  0.4.14-1

qpdfview suggests no packages.

-- no debconf information



Bug#860317: upgrade to latest stretch version breaks

2017-04-14 Thread Brent S. Elmer
Package: exim4
Version: 4.89-1
Severity: normal

I upgraded packages in stretch and there was a problem upgrading exim4.  When I
try to do a reinstall of exim4 to try to fix it using synaptic, I get:

E: Internal Error, No file name for exim4:amd64

When I upgrade or reinstall any other random package, configuration of exim4
gives errors:

(Reading database ... 666472 files and directories currently installed.)
Preparing to unpack .../anacron_2.3-23_amd64.deb ...
Unpacking anacron (2.3-23) over (2.3-23) ...
Processing triggers for systemd (232-22) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up exim4-daemon-light (4.89-1) ...
Job for exim4.service failed because of unavailable resources or another system
error.
See "systemctl status exim4.service" and "journalctl -xe" for details.
invoke-rc.d: initscript exim4, action "start" failed.
● exim4.service - LSB: exim Mail Transport Agent
   Loaded: loaded (/etc/init.d/exim4; generated; vendor preset: enabled)
   Active: failed (Result: resources) since Fri 2017-04-14 08:30:06 CDT; 5ms
ago
 Docs: man:systemd-sysv-generator(8)
  Process: 27992 ExecStart=/etc/init.d/exim4 start (code=exited,
status=0/SUCCESS)
  CPU: 145ms

Apr 14 08:30:06 brente systemd[1]: Starting LSB: exim Mail Transport Agent...
Apr 14 08:30:06 brente exim4[27992]: Starting MTA: exim4.
Apr 14 08:30:06 brente exim4[27992]: ALERT: exim paniclog
/var/log/exim4/pa…oken
Apr 14 08:30:06 brente systemd[1]: exim4.service: PID file
/run/exim4/exim.…tory
Apr 14 08:30:06 brente systemd[1]: exim4.service: Daemon never wrote its
PI…ing.
Apr 14 08:30:06 brente systemd[1]: Failed to start LSB: exim Mail
Transport…ent.
Apr 14 08:30:06 brente systemd[1]: exim4.service: Unit entered failed state.
Apr 14 08:30:06 brente systemd[1]: exim4.service: Failed with result
'resou…es'.
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package exim4-daemon-light (--configure):
 subprocess installed post-installation script returned error exit status 1
Setting up anacron (2.3-23) ...
insserv: warning: script 'K01vpnagentd_init' missing LSB tags and overrides
insserv: warning: script 'vpnagentd_init' missing LSB tags and overrides
dpkg: dependency problems prevent configuration of exim4:
 exim4 depends on exim4-daemon-light | exim4-daemon-heavy | exim4-daemon-
custom; however:
  Package exim4-daemon-light is not configured yet.
  Package exim4-daemon-heavy is not installed.
  Package exim4-daemon-custom is not installed.

dpkg: error processing package exim4 (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 exim4-daemon-light
 exim4

Not all changes and updates succeeded. For further details of the failure,
please expand the 'Details' panel below.





-- Package-specific info:
Exim version 4.89 #2 built 09-Mar-2017 16:49:47
Copyright (c) University of Cambridge, 1995 - 2017
(c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2017
Berkeley DB: Berkeley DB 5.3.28: (September  9, 2013)
Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages DKIM DNSSEC Event 
OCSP PRDR SOCKS TCP_Fast_Open
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz 
dbmnz dnsdb dsearch nis nis0 passwd
Authenticators: cram_md5 plaintext
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp
Fixed never_users: 0
Configure owner: 0:0
Size of off_t: 8
Configuration file is /var/lib/exim4/config.autogenerated
# /etc/exim4/update-exim4.conf.conf
#
# Edit this file and /etc/mailname by hand and execute update-exim4.conf
# yourself or use 'dpkg-reconfigure exim4-config'
#
# Please note that this is _not_ a dpkg-conffile and that automatic changes
# to this file might happen. The code handling this will honor your local
# changes, so this is usually fine, but will break local schemes that mess
# around with multiple versions of the file.
#
# update-exim4.conf uses this file to determine variable values to generate
# exim configuration macros for the configuration file.
#
# Most settings found in here do have corresponding questions in the
# Debconf configuration, but not all of them.
#
# This is a Debian specific file

dc_eximconfig_configtype='local'
dc_other_hostnames='localhost.localdomain'
dc_local_interfaces='127.0.0.1 ; ::1'
dc_readhost=''
dc_relay_domains=''
dc_minimaldns='false'
dc_relay_nets=''
dc_smarthost=''
CFILEMODE='644'
dc_use_split_config='false'
dc_hide_mailname=''
dc_mailname_in_oh='true'
dc_localdelivery='mail_spool'
mailname:localhost.localdomain

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

Kernel: Linux 4.9.2.170124 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of 

Bug#854592: [pkg-php-pear] Bug#854592: dokuwiki: Unable to login, missing usr/share/php/Crypt/AES.php

2017-04-14 Thread Tanguy Ortolo

Hello,

David Prévot, 2017-02-13 08:45-0900:

Then it sounds like this bug was incorrectly reassigned to
php-phpseclib: either dokuwiki should depend on version 1 of phpseclib
via the php-seclib package and have the files where expected, or it is
able to use version 2 via the php-phpseclib package installed where it
belongs. In any way, please, do keep both packages installable together,
the proposed patch is not acceptable.

Either way, dokuwiki should be able to use the provided autoloader:
- /usr/share/php/phpseclib/autoload.php for php-phpseclib
- /usr/share/php/phpseclib.autoloader.php for php-seclib


This is right, I though I already did that, but that modification got 
lost between two updates of the package. Let me reintegrate it.


--
 ,--.
: /` )   Tanguy Ortolo  
| `-'Debian Developer   
 \_


signature.asc
Description: Digital signature


  1   2   >