Bug#809423: marked as done (klibc: FTBFS on i386: Multiple definition of `socket')

[Debian Bug Tracking System]

Your message dated Sun, 31 Dec 2017 08:14:36 +0100
with message-id <87lghj4bdv@turtle.gmx.de>
and subject line Re: Bug#809423: klibc: FTBFS on i386: Multiple definition of 
`socket'
has caused the Debian Bug report #809423,
regarding klibc: FTBFS on i386: Multiple definition of `socket'
to be marked as done.

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

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


-- 
809423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809423
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: klibc
Version: 2.0.4-4
Severity: serious

>From my pbuilder build log:

...
  ld -m elf_i386 -Ttext 0x06000200 -o usr/klibc/libc.so --start-group 
usr/klibc/arch/i386/crt0.o usr/klibc/__shared_init.o usr/klibc/vsnprintf.o 
usr/klibc/snprintf.o usr/klibc/vsprintf.o usr/klibc/sprintf.o 
usr/klibc/asprintf.o usr/klibc/vasprintf.o usr/klibc/vsscanf.o 
usr/klibc/sscanf.o usr/klibc/ctypes.o usr/klibc/strntoumax.o 
usr/klibc/strntoimax.o usr/klibc/atoi.o usr/klibc/atol.o usr/klibc/atoll.o 
usr/klibc/strtol.o usr/klibc/strtoll.o usr/klibc/strtoul.o usr/klibc/strtoull.o 
usr/klibc/strtoimax.o usr/klibc/strtoumax.o usr/klibc/globals.o 
usr/klibc/exit.o usr/klibc/atexit.o usr/klibc/onexit.o usr/klibc/execl.o 
usr/klibc/execle.o usr/klibc/execv.o usr/klibc/execvpe.o usr/klibc/execvp.o 
usr/klibc/execlp.o usr/klibc/execlpe.o usr/klibc/fork.o usr/klibc/vfork.o 
usr/klibc/wait.o usr/klibc/wait3.o usr/klibc/waitpid.o usr/klibc/system.o 
usr/klibc/setpgrp.o usr/klibc/getpgrp.o usr/klibc/daemon.o usr/klibc/printf.o 
usr/klibc/vprintf.o usr/klibc/fprintf.o usr/klibc/vfprintf.o usr/klibc/perror.o 
usr/klibc/statfs.o usr/klibc/fstatfs.o usr/klibc/umount.o usr/klibc/creat.o 
usr/klibc/open.o usr/klibc/openat.o usr/klibc/open_cloexec.o usr/klibc/fread2.o 
usr/klibc/fwrite2.o usr/klibc/fgets.o usr/klibc/fputc.o usr/klibc/fputs.o 
usr/klibc/puts.o usr/klibc/putchar.o usr/klibc/sleep.o usr/klibc/usleep.o 
usr/klibc/strtotimespec.o usr/klibc/strtotimeval.o usr/klibc/raise.o 
usr/klibc/abort.o usr/klibc/assert.o usr/klibc/alarm.o usr/klibc/pause.o 
usr/klibc/__signal.o usr/klibc/sysv_signal.o usr/klibc/bsd_signal.o 
usr/klibc/siglist.o usr/klibc/sigabbrev.o usr/klibc/siglongjmp.o 
usr/klibc/sigaction.o usr/klibc/sigpending.o usr/klibc/sigprocmask.o 
usr/klibc/sigsuspend.o usr/klibc/pselect.o usr/klibc/ppoll.o usr/klibc/pread.o 
usr/klibc/pwrite.o usr/klibc/brk.o usr/klibc/sbrk.o usr/klibc/malloc.o 
usr/klibc/realloc.o usr/klibc/zalloc.o usr/klibc/calloc.o usr/klibc/mmap.o 
usr/klibc/shm_open.o usr/klibc/shm_unlink.o usr/klibc/memcpy.o 
usr/klibc/memcmp.o usr/klibc/memset.o usr/klibc/memccpy.o usr/klibc/memmem.o 
usr/klibc/memswap.o usr/klibc/memmove.o usr/klibc/memchr.o usr/klibc/memrchr.o 
usr/klibc/bzero.o usr/klibc/strcasecmp.o usr/klibc/strncasecmp.o 
usr/klibc/strndup.o usr/klibc/strerror.o usr/klibc/strsignal.o 
usr/klibc/strcat.o usr/klibc/strchr.o usr/klibc/strcmp.o usr/klibc/strcpy.o 
usr/klibc/strdup.o usr/klibc/strlen.o usr/klibc/strnlen.o usr/klibc/strncat.o 
usr/klibc/strlcpy.o usr/klibc/strlcat.o usr/klibc/strstr.o usr/klibc/strncmp.o 
usr/klibc/strncpy.o usr/klibc/strrchr.o usr/klibc/strxspn.o usr/klibc/strspn.o 
usr/klibc/strcspn.o usr/klibc/strpbrk.o usr/klibc/strsep.o usr/klibc/strtok.o 
usr/klibc/strtok_r.o usr/klibc/fnmatch.o usr/klibc/gethostname.o 
usr/klibc/getdomainname.o usr/klibc/getcwd.o usr/klibc/seteuid.o 
usr/klibc/setegid.o usr/klibc/getenv.o usr/klibc/setenv.o usr/klibc/putenv.o 
usr/klibc/__put_env.o usr/klibc/unsetenv.o usr/klibc/clearenv.o 
usr/klibc/nullenv.o usr/klibc/getopt.o usr/klibc/getopt_long.o 
usr/klibc/readdir.o usr/klibc/scandir.o usr/klibc/alphasort.o 
usr/klibc/remove.o usr/klibc/syslog.o usr/klibc/closelog.o usr/klibc/pty.o 
usr/klibc/getpt.o usr/klibc/posix_openpt.o usr/klibc/isatty.o 
usr/klibc/reboot.o usr/klibc/time.o usr/klibc/utime.o usr/klibc/lseek.o 
usr/klibc/nice.o usr/klibc/getpriority.o usr/klibc/qsort.o usr/klibc/bsearch.o 
usr/klibc/lrand48.o usr/klibc/jrand48.o usr/klibc/mrand48.o usr/klibc/nrand48.o 
usr/klibc/srand48.o usr/klibc/seed48.o usr/klibc/inet/inet_ntoa.o 
usr/klibc/inet/inet_aton.o usr/klibc/inet/inet_addr.o 
usr/klibc/inet/inet_ntop.o usr/klibc/inet/inet_pton.o 
usr/klibc/inet/bindresvport.o usr/klibc/send.o usr/klibc/recv.o 
usr/klibc/access.o usr/klibc/chmod.o usr/klibc/chown.o usr/klibc/dup2.o 
usr/klibc/mknod.o usr/klibc/poll.o usr/klibc/rename.o usr/klibc/stat.o 
usr/klibc/lchown.o usr/klibc/link.o usr/klibc/rmdir.o usr/klibc/unlink.o 
usr/klibc/utimes.o usr/klibc/lstat.o usr/klibc/mkdir.o usr/klibc/readlink.o 
usr/klibc/realpath.o usr/klibc/select.o usr/klibc/symlink.o 

Bug#877661: marked as done (runc: Block migration to testing until docker.io moves to docker-runc)

[Debian Bug Tracking System]

Your message dated Sun, 31 Dec 2017 00:51:20 -0500
with message-id <665dde06-c59e-3869-0823-a1fa01193...@debian.org>
and subject line 877329 is fixed
has caused the Debian Bug report #877661,
regarding runc: Block migration to testing until docker.io moves to docker-runc
to be marked as done.

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

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


-- 
877661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877661
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: runc
Version: 1.0.0~rc4+dfsg1-1
Severity: critical
Control: block -1 by 877329


Hi,

Runc 1.0.0~rc4 breaks current docker.io (#877146) until docker.io
moves to docker-runc (#877329),
hence letting runc 1.0.0~rc4 to migrate to testing would be a bad idea.

After fixing #877329 this bug can be closed.

Cheers,
Balint
--- End Message ---
--- Begin Message ---
877329 is fixed

Cheers,

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#885053: Asked for removal

[Tiago Bortoletto Vaz]

Thanks for reporting, asked for removal:

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

Bests,

-- 
tiago

Bug#884807: getmail: does not ship /usr/bin/getmail

[Osamu Aoki]

Hi,

On Wed, Dec 20, 2017 at 11:23:54AM -0500, Daniel Kahn Gillmor wrote:
> On Thu 2017-12-21 00:48:44 +0900, Osamu Aoki wrote:
> >
> >   # Always use debian/getmail as destination (not debian/tmp)
> >   # even when dummy getmail4 package exists
> >   override_dh_auto_install:
> >   dh_auto_install --destdir debian/getmail
> 
> ok, it looks like i tend to prefer the more declarative style, and you
> prefer the imperative style.  You're the maintainer, so your decision
> goes :)

Just for the record, let me clarify my position.  I thought about this
concern.

> Just so you know why i prefer the declarative style, though:

I also prefer the declarative style for *splitting* generated files into
*multiple* binary packages from the debian/tmp directory.  But that is
for *splitting* into binary packages ;-)

> i think with your imperative changes to the debian/rules makefile, a new
> upstreamversion that injects something funky into the filesystem will
> just have it happen (possibly without the maintainer noticing).

I see your point.  You are considering *.install as a one level of
security check.  Then you should raise concern to the current
dh_auto_install behavior (maybe since debhelper compat>=4) which doesn't
use the debian/tmp directory as the DESTDIR.  All
"single_binary_package"-type packages use the debian/
directory as the DESTDIR and ship all generated files without filtering.

I remember this DESTDIR choice was flip-flopped before debhelper compat
4.  But the current choice of DESTDIR is quite stable since then. 

> With the declarative approach i'd outlined (that is, listing everything
> explicitly in debian/getmail.{docs,install,manpages}, and including
> dh_missing --fail-missing), the packager has to actively acknowledge
> changes to the installed filesystem, which i like as a double-check
> during packaging itself.

Please note there were imperative changes to the debian/rules even in
your proposed version which got carried over from my previous script.  I
mean "rm -rf debian/.../usr/share/doc/getmail-*".  I thought installing
documentation from upstream installed ones in DESTDIR are better than
copying from the source tree.  That was the reason why I changed from
"rm -rf" to "mv".

> > So when we drop getmail4 transition package, migration needs only
> > dropping it in the debian/control field.
> 
> I think that would happen either way :)

Once we drop getmail4 in buster+1, we will be back to the
"single_binary_package"-type package unless we change dh_auto_install to
override its default by setting --destdir=debian/tmp.
I thought that is a bit overkill.  Instead, I set
--destdir=debian/getmail since this is practically a single binary
package except for generating a dummy package.  Then with "mv" already
applied, I just don't need to have *.install.  That is what happened.

> anyway, just thought i'd explain my reasoning.  I'm happy to follow your
> lead on the package.

No problem.  Since I noticed your rationale, I just wanted to explain my
rationale ;-)

Osamu

Bug#876608: [Pkg-sass-devel] Bug#876608: Bug#876608: ruby-compass (build) depends on ruby-sass (< 3.5), but 3.5.1-2 is in unstable

[Jonas Smedegaard]

Quoting Daniele Scasciafratte (2017-12-30 18:32:56)
> Any updates for this ticket?

No.

 - Jonas

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

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


signature.asc
Description: signature

Processed: Re: ansible-lint fails with ansible 2.4

[Debian Bug Tracking System]

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

> severity 882066 grave
Bug #882066 [ansible-lint] ansible-lint fails with ansible 2.4
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#885570: Duplicate of 884061 ?

[Adrien Plan]

Hi,

I got the same issue on my i915 notebook (Dell E7450) and I had to boot 
on previous kernel (linux-image-4.9.0-3-amd64)


This bug report seems the same and suggest a tested revert on commit 
7de694782cbe7840f2c0de6f1e70f41fc1b8b6e8 :


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

Thanks,

Adrien

Processed: bug 884849 is forwarded to https://gitlab.gnome.org/GNOME/librsvg/issues/178

[Debian Bug Tracking System]

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

> forwarded 884849 https://gitlab.gnome.org/GNOME/librsvg/issues/178
Bug #884849 [src:librsvg] librsvg: FTBFS on any-i386: masking-path-04-b.svg: 
213 pixels differ (with maximum difference of 19) from reference image
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/librsvg/issues/178'.
> thanks
Stopping processing here.

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

Bug#885603: gajim in stretch-backports depends on python3-nbxmpp, which is not in stretch-backports

[W. Martin Borgert]

Dear Patrik,

python-nbxmpp (which includes python3-nbxmpp) is now in backports.
Gajim should be installablen now!

Have fun!

Bug#885603: marked as done (gajim in stretch-backports depends on python3-nbxmpp, which is not in stretch-backports)

[Debian Bug Tracking System]

Your message dated Sun, 31 Dec 2017 00:44:54 +0100
with message-id <20171230234454.GA11906@fama>
and subject line Re: Bug#885603: gajim in stretch-backports depends on 
python3-nbxmpp, which is not in stretch-backports
has caused the Debian Bug report #885603,
regarding gajim in stretch-backports depends on python3-nbxmpp, which is not in 
stretch-backports
to be marked as done.

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

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


-- 
885603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885603
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gajim
Version: 0.16.8-3~bpo9+1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

when trying to upgrade gajim from stretch-backports I get the following:

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

The following packages have unmet dependencies:
 gajim : Depends: python3-nbxmpp (>= 0.6.0) but 0.5.4-1 is to be installed
 Recommends: fonts-noto-color-emoji but it is not going to be installed
 Recommends: gajim-omemo (>= 2.5.1) but it is not going to be installed
 Recommends: gajim-pgp but it is not going to be installed
 Recommends: gir1.2-farstream-0.2 but it is not going to be installed
 Recommends: gir1.2-gspell-1 but it is not going to be installed
 Recommends: gir1.2-gupnpigd-1.0 but it is not going to be installed
 Recommends: gstreamer0.10-plugins-ugly but it is not installable
 Recommends: python3-gnupg (>= 0.4.1) but it is not going to be 
installed
 Recommends: python3-precis-i18n but it is not installable
E: Broken packages

I guess the problem is a missing python3-nbxmpp (>= 0.6.0) package in 
stretch-backports.

Thanks for your help.

Patrik


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

Kernel: Linux 4.9.0-4-amd64 (SMP w/2 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)

Versions of packages gajim depends on:
ii  dnsutils1:9.10.3.dfsg.P4-12.3+deb9u3
ii  python  2.7.13-2
ii  python-gtk2 2.24.0-5.1
ii  python-nbxmpp   0.5.4-1
ii  python-openssl  16.2.0-1
ii  python-pyasn1   0.1.9-2

Versions of packages gajim recommends:
ii  alsa-utils 1.1.3-1
ii  ca-certificates20161130+nmu1
ii  dbus   1.10.24-0+deb9u1
ii  gnome-shell [notification-daemon]  3.22.3-3
ii  notification-daemon3.20.0-1+b1
ii  pulseaudio-utils   10.0-1+deb9u1
ii  python-crypto  2.6.1-7
ii  python-dbus1.2.4-1+b1
ii  python-gnupg   0.3.9-1

Versions of packages gajim suggests:
ii  aspell-en [aspell-dictionary]  2016.11.20-0-0.1
ii  avahi-daemon   0.6.32-2
ii  dvipng 1.14-2+b3
ii  gnome-keyring  3.20.0-3
pn  gstreamer0.10-plugins-ugly 
ii  kwalletcli 3.00-1+b1
ii  libgtkspell0   2.0.16-1.1
ii  libxss11:1.2.2-1
ii  nautilus-sendto3.8.4-2+b1
ii  network-manager1.6.2-3
ii  python-avahi   0.6.32-2
ii  python-gconf   2.28.1+dfsg-1.2
ii  python-gnome2  2.28.1+dfsg-1.2
ii  python-gnomekeyring2.32.0+dfsg-3
ii  python-gupnp-igd   0.2.4-1+b2
ii  python-kerberos1.1.5-2+b2
ii  python-pycurl  7.43.0-2
ii  texlive-latex-base 2016.20170123-5

-- no debconf information
--- End Message ---
--- Begin Message ---
Dear Patrik,

python-nbxmpp (which includes python3-nbxmpp) is now in backports.
Gajim should be installablen now!

Have fun!--- End Message ---

Bug#883413: linux-image-4.14.0-1-amd64: WARN_ON_ONCE in page_counter_cancel() in mm/page_counter.c

[Chris Boot]

On 25/12/17 23:09, Ben Hutchings wrote:
> On Sat, 2017-12-23 at 12:42 +, Chris Boot wrote:
>> Severity: serious
>> Justification: kernel panic
>>
>> I experimented a little and disabled cgroupv2 on that server. Because I 
>> had some issues during boot I attempted to enable 
>> NetworkManager-wait-online.service using systemd, but that instantly 
>> resulted in the following kernel panic:
> [...]
>> I don't know that this is the same bug at all, but I'm keeping it on
>> this report for now as it seems at least related somehow.
> 
> The log messages don't look even slightly related, so please move this 
> to a separate bug report.

I'm still not so certain - both sets of stack dumps fall somewhere
within cgroup space, and disabling systemd's cgroup accounting (not
enabled by default) avoids these conditions.

I like to run this system with the following all enabled in
/etc/systemd/system.conf:

DefaultCPUAccounting=yes
DefaultIOAccounting=yes
DefaultBlockIOAccounting=yes
DefaultMemoryAccounting=yes

These are useful for tools like systemd-cgtop for example.

With cgroupv2, I can avoid the error by disabling
DefaultMemoryAccounting. I was running for nearly 48 hours with this
configuration before rebooting to try without cgroupv2.

Without cgroupv2, it's DefaultCPUAccounting I need to disable to avoid
the panics when I run 'systemd daemon-reload'. I have yet to run into
the warning or OOM killer with memory accounting enabled but I'll let
you know if it happens.

What makes me suspicious that these are related is that neither happens
with a 4.13 kernel, but I get both of these cgroup-related problems with
4.14.

I wouldn't mind trying to bisect this, but I haven't done that for many
years. Is there a nice way to do this with the Debian packaging or am I
better off seeing if I can reproduce with vanilla upstream kernels and
bisecting that? Or shall I give 4.15~rc5 from experimental a whirl instead?

Thanks,
Chris

-- 
Chris Boot
bo...@debian.org

Bug#885889: sasview: FTBFS: debian/sasview might not exist

[Aaron M. Ucko]

Source: sasview
Version: 4.2.0~git20171031-2
Severity: serious
Justification: fails to build from source

Builds of sasview covering only its architecture-dependent
python-sasview binary package (as on the autobuilders, or with
dpkg-buildpackage -B) have been failing:

  dh_install
  mv debian/python-sasview/usr/bin/sasview debian/sasview/usr/bin/sasview
  mv: cannot move 'debian/python-sasview/usr/bin/sasview' to 
'debian/sasview/usr/bin/sasview': No such file or directory
  debian/rules:27: recipe for target 'override_dh_install' failed
  make[1]: *** [override_dh_install] Error 1
  make[1]: Leaving directory '/<>'
  debian/rules:16: recipe for target 'binary-arch' failed
  make: *** [binary-arch] Error 2

Could you please take a look?  You may wish to consider splitting
override_dh_install into -arch and -indep targets.

Bonus points for additionally accounting for builds that cover only
the architecture-independent packages, as with dpkg-buildpackage -A
(allowing for source-only uploads). ;-)

Thanks!

FTR, I'm classifying this bug as a regression because it would affect
any needed binary-only rebuilds for amd64.

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

Bug#882026: marked as done (qtiplot FTBFS: fatal error: sipAPIqti.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Sat, 30 Dec 2017 23:07:59 +
with message-id 
and subject line Bug#882026: fixed in qtiplot 0.9.8.9-17
has caused the Debian Bug report #882026,
regarding qtiplot FTBFS: fatal error: sipAPIqti.h: No such file or directory
to be marked as done.

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

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


-- 
882026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882026
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qtiplot
Version: 0.9.8.9-16
Severity: serious

Some recent change in unstable makes qtiplot FTBFS:

https://tests.reproducible-builds.org/debian/history/qtiplot.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/qtiplot.html

...
src/scripting/PythonScripting.cpp:61:10: fatal error: sipAPIqti.h: No such file 
or directory
 #include "sipAPIqti.h"
  ^
--- End Message ---
--- Begin Message ---
Source: qtiplot
Source-Version: 0.9.8.9-17

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

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

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated qtiplot package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 30 Dec 2017 23:51:01 +0100
Source: qtiplot
Binary: qtiplot qtiplot-doc
Architecture: source
Version: 0.9.8.9-17
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Anton Gladky 
Description:
 qtiplot- data analysis and scientific plotting
 qtiplot-doc - data analysis and scientific plotting (documentation)
Closes: 882026
Changes:
 qtiplot (0.9.8.9-17) unstable; urgency=medium
 .
   * Team upload.
   * [aec7671] Remove myself from uploaders
   * [1843f27] First try to fix #882026
   * [ca9c06d] Fix compilation against sip_4.19. (Closes: #882026)
   * [ca50cee] Add dh-python into build-depends
   * [fbe2d82] Remove obsolete menu-file
Checksums-Sha1:
 c53bab4edb31490c7489c0b8e1184eeb30116419 2527 qtiplot_0.9.8.9-17.dsc
 5b05414371e82ad3da10f4a93a366ae23baebebf 22648 qtiplot_0.9.8.9-17.debian.tar.xz
 078336bcffa11460034db87d13a6045e1d66cba6 18242 
qtiplot_0.9.8.9-17_source.buildinfo
Checksums-Sha256:
 c26717ad49d545afae12689664a6ad27c455903c4511d09e64afcd3c7a6c10b0 2527 
qtiplot_0.9.8.9-17.dsc
 b3cbf779c02eaa622bf16771f20ba51ce740975191ce6ee01b8ecf51d84d19a1 22648 
qtiplot_0.9.8.9-17.debian.tar.xz
 a2e8bd5a14235f29984e9998447d5fad197318685085b803d5e72c0e0da9c800 18242 
qtiplot_0.9.8.9-17_source.buildinfo
Files:
 a5b4765eb725df6b5569cf436e7126f1 2527 math optional qtiplot_0.9.8.9-17.dsc
 2eca5ea0de7bf9ffdce60468aa9ee432 22648 math optional 
qtiplot_0.9.8.9-17.debian.tar.xz
 d59e2207076e4bb1a6de7621930cd31e 18242 math optional 
qtiplot_0.9.8.9-17_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAlpIGHMACgkQ0+Fzg8+n
/waHgBAAluSlV5YF02GqUZGdEyQF42qiZ/Ihuql7cQCVg5i3L3NUEbJV7Swuzz6A
7376sf+kzAnq6YiYFleqUS2yHs+lMsecbzbJ6YOHBCWi3IwYKPdJlacZVIS/BNHs
5qGEvozO2WGNdA5nMisV9jf25vJcqPTVM3lgPB5OQ/1qp8/fmObPEMe33T+8KpMS
OX0tbewVVUKsO5UptnqPi+1hmtxEg+6r0umMT9ZrSt8V+jPmDfVHXonXFyn+Hfrj
Y66fJGOXJsUTE1+kz+1ja8hZZK/nLc8EIhG03wlEAOHeOigVNtT770I1EybvsBRr
ZweSQrQDnm2ZZU7uEOdgXAbm73AMxzR036N+/8JTXuXPLcvfeYBHK0sHxbvkPk7k
qJPnC73K2SLHMPjgtJBA13yBcQPA3KtBV5rQONNJcx/lL8strxzOB6sbsnbabXY3
+Q5Hv06DhTQkBEahsuO/P00Q4W4mpT0DrTmobo49DI34eHQWCjwjwb7P2yWpEZDb
MI+3usA/sfFfIo7OG+PYltHMnckGGZ6wKMcVKfqQ/gmYRg4EBqsKCNKxsgQAEpRF
8iQjxlWT4QBw2yO5mfbHTV79aZXVJfc3Hpn91dAGmI6TejSa5TsDQWPt7R8jq/08
VIQ4mXCU3kQdIGnvzMgYH1zYWhStGBMCtVJpOm38MUYvCZbcMlI=
=5TRF
-END PGP SIGNATURE End Message ---

Bug#885888: lordsawar: Don't Build-Depend on libglademm2.4-dev

[Jeremy Bicha]

Source: lordsawar
Version: 0.3.1-3
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs glademm
Tags: sid buster patch

lordsawar has an apparently unnecessary Build-Depends on libglademm2.4-
dev. libglade is for gtk2 but lordsawar uses gtk3. Please drop this
Build-Depends since libglademm2.4 will be removed from Debian soon.

(No patch attached because this is a trivial fix.)

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#879043: dahdi-linux No longer compiled with m-a as of 4.13: unknown field ‘dev_attrs’

[Bernhard Schmidt]

On Wed, Oct 18, 2017 at 08:19:26PM +0300, Tzafrir Cohen wrote:

Hi Tzafrir,

> Version: 1:2.11.1.0.20170917~dfsg-1
> Flags: patch upstream
> Forwarded: https://issues.asterisk.org/jira/browse/DAHLIN-356
> Severity: grave
> 
> As of kernel 4.13, build fails with the following error:

Any update on this? The JIRA ticket seems to have a proposed patch
attached, but it's not merged yet.

Bernhard

Bug#882026: qtiplot FTBFS: fatal error: sipAPIqti.h: No such file or directory

[Anton Gladky]

Hi Dmitry!

Thanks a lot for the quick help! The patch really solves the rest
of the problems with new sip. I am preparing a new upload of qcustomplot.

Best regards

Anton


2017-12-30 22:51 GMT+01:00 Dmitry Shachnev :
> Hi Anton!
>
> On Sat, Dec 30, 2017 at 05:50:57PM +0100, Anton Gladky wrote:
>> It looks like sip4_4.19 broke the qtiplot (upload without rebuild of all
>> reverse dependencies?).
>
> sip 4.19 broke qtiplot, but I reported that and it was fixed. See #872636.
>
> Looks like this time some minor release of sip broke it (probably 4.19.4).
> It was a minor release and it was not announced that it can break something,
> so I did not test the reverse dependencies that time.
>
>> Anyway, I have tried to fix this particular part of compilation
>> process [1]. But it still fails to compile due to major changes in sip.
>> Help is welcome.
>
> Please try this patch: https://bugs.gentoo.org/641514#c2
>
> --
> Dmitry Shachnev

Bug#883759: marked as done (kashmir: Includes "gui/ios/Model/UUIDModel.h" listed in Files-Excluded header)

[Debian Bug Tracking System]

Your message dated Sat, 30 Dec 2017 22:39:13 +
with message-id 
and subject line Bug#883759: fixed in kashmir 0.0~git20150805.0.2f3913f+dfsg3-1
has caused the Debian Bug report #883759,
regarding kashmir: Includes "gui/ios/Model/UUIDModel.h" listed in 
Files-Excluded header
to be marked as done.

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

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


-- 
883759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883759
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kashmir
Version: 0.0~git20150805.0.2f3913f+dfsg1-3
Severity: serious
User: la...@debian.org
Usertags: files-excluded

Dear Maintainer,

kashmir lists "gui/*" in the Files-Excluded field in debian/copyright
but the source tree contains gui/ios/Model/UUIDModel.h.

This is probably a DFSG violation, or at the upstream tarball was not
repacked as intended. Alternatively, the field is simply out of date.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: kashmir
Source-Version: 0.0~git20150805.0.2f3913f+dfsg3-1

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

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

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

Debian distribution maintenance software
pp.
Alexandre Viau  (supplier of updated kashmir package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 30 Dec 2017 17:17:25 -0500
Source: kashmir
Binary: libkashmir-dev
Architecture: source
Version: 0.0~git20150805.0.2f3913f+dfsg3-1
Distribution: unstable
Urgency: medium
Maintainer: Alexandre Viau 
Changed-By: Alexandre Viau 
Description:
 libkashmir-dev - general purpose library to complement stdlib
Closes: 883759
Changes:
 kashmir (0.0~git20150805.0.2f3913f+dfsg3-1) unstable; urgency=medium
 .
   * Move to salsa.debian.org.
   * Priority extra -> optional.
   * Exclude gui/* (Closes: #883759).
Checksums-Sha1:
 4089f25003e93962a9a112579ce251e85334822e 2035 
kashmir_0.0~git20150805.0.2f3913f+dfsg3-1.dsc
 a93c902a758f3026f159bcdd96b99619f0842849 9816 
kashmir_0.0~git20150805.0.2f3913f+dfsg3.orig.tar.gz
 8bcd58bb09523852016bb128f8920997fe739d07 2048 
kashmir_0.0~git20150805.0.2f3913f+dfsg3-1.debian.tar.xz
 b1ddf6d1e7475ed38457ffd90096fc3e5bdfd3fe 5446 
kashmir_0.0~git20150805.0.2f3913f+dfsg3-1_source.buildinfo
Checksums-Sha256:
 99a6af674d9e002d9ea0f9461211fd741d5e22eb6828be3318fe1862bc96a4c6 2035 
kashmir_0.0~git20150805.0.2f3913f+dfsg3-1.dsc
 af579854e90a2138d4fbfe668a7079a781670b970ace9b75dd55065b7f948800 9816 
kashmir_0.0~git20150805.0.2f3913f+dfsg3.orig.tar.gz
 aa5a88fbb69aff97daa2e5a47e7e4f15a754bcfcc5b47b7e0f8a75bfaa7e88a0 2048 
kashmir_0.0~git20150805.0.2f3913f+dfsg3-1.debian.tar.xz
 22a793a24d5d374dacc389e1e40e9e2dccc0d7f8ccf527fdf801312d40dea01c 5446 
kashmir_0.0~git20150805.0.2f3913f+dfsg3-1_source.buildinfo
Files:
 2184ac45293888eaec7810d26175396c 2035 libs optional 
kashmir_0.0~git20150805.0.2f3913f+dfsg3-1.dsc
 0eb9d4b5f539c2d613a1b5cc6a49bfc0 9816 libs optional 
kashmir_0.0~git20150805.0.2f3913f+dfsg3.orig.tar.gz
 987fa8c6fc6d43df36466cb29e131b8c 2048 libs optional 
kashmir_0.0~git20150805.0.2f3913f+dfsg3-1.debian.tar.xz
 85d306a488a6c44bba323d1902c6ac5d 5446 libs optional 
kashmir_0.0~git20150805.0.2f3913f+dfsg3-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEB0B3ii38SjnAyLyMjysRPGU1xacFAlpIEUYRHGF2aWF1QGRl
Ymlhbi5vcmcACgkQjysRPGU1xaf11A/7Bkx1QW0WusOrLB+l9PtaV26JsTEl+vn0
ZpI5Tu9C67sLj3tMRMgIEUjM+4pzzbpAExPIlUpAe3hNaaNRKbEDzQMnCstjoEm6
6UXowb+6bvnj4SuJzHJxbvynr11DdkRUlgK+/p6gTHjYwLveRmCp//Ig+7p7qTv8
BhCaMKO3tniC1MDwPxwKwtYqHg+IdVynNjrNeoccEcNzvEAvQYzcF+tG0zaPqGes
dCfjd4P/ZSbQUzwwgJnYmaRzR9gz29WNGgJCv9PkuMcR53/ivHapyu7BLMY5lWiJ
N5VQSJLd7To9zoudToVkndedRXHWARC3+hZlgYUxzJM62dbFg/t1Z+wZNuEqOWEF
4GYLm/ELwnAuDhyCrg9O/NXV2wty6XMzHOPCC+/Qft+QKksZbzcoQ3BLBWrurMsN
s45P46FzmJ42fSEfWAj7E/xfyeYgVOxeTyChRBCo3eXQAcSp42VFg2eLGJOFBdIB
d29/DXwrNndCFJh9ZaJ8WML85+rL1NUNh11Vc0qmmCdIwsLgKK3KPxovgdDRLL4c

Bug#885885: FTBTS with linux 4.15, severe warnings with linux 4.14

[Gerardo Esteban Malazdrewicz]

Source: broadcom-sta
Version: 6.30.223.271-7
Severity: serious
Tags: patch
Justification: fails to build from source

linux 4.14 changed the kernel_read function prototype.
linux 4.15 deprecated the init_timer function.

Both functions are used by this package.

I am currectly using linux 4.15-rc5 with the attached patches applied
(my NIC is a Broadcom BCM4352).

Not sure the patches are correct, though.

Best regards,
Gerardo Malazdrewicz

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

Kernel: Linux 4.15.0-rc5-amd64 (SMP w/8 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/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- a/amd64/src/shared/linux_osl.c  2017-12-29 22:59:17.0 -0400
+++ b/amd64/src/shared/linux_osl.c  2017-12-29 23:44:24.786247269 -0400
@@ -1076,11 +1076,21 @@
 {
struct file *fp = (struct file *)image;
int rdlen;
+   loff_t pos;
 
if (!image)
return 0;
 
-   rdlen = kernel_read(fp, fp->f_pos, buf, len);
+   pos = fp->f_pos;
+   rdlen = kernel_read(fp, 
+#if LINUX_VERSION_CODE < KERNEL_VERSION(4, 14, 0)
+   pos, 
+#endif
+   buf, len
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 14, 0)
+   , 
+#endif
+   );
if (rdlen > 0)
fp->f_pos += rdlen;
 
--- a/amd64/src/wl/sys/wl_linux.c   2017-12-29 23:57:29.0 -0400
+++ b/amd64/src/wl/sys/wl_linux.c   2017-12-30 12:32:29.518324068 -0400
@@ -93,7 +93,13 @@
 
 #include 
 
-static void wl_timer(ulong data);
+static void wl_timer(
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 15, 0)
+   struct timer_list *tl
+#else
+   ulong data
+#endif
+   );
 static void _wl_timer(wl_timer_t *t);
 static struct net_device *wl_alloc_linux_if(wl_if_t *wlif);
 
@@ -2295,9 +2301,19 @@
 }
 
 static void
-wl_timer(ulong data)
-{
-   wl_timer_t *t = (wl_timer_t *)data;
+wl_timer(
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 15, 0)
+   struct timer_list *tl
+#else
+   ulong data
+#endif
+) {
+   wl_timer_t *t =
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 15, 0)
+   from_timer(t, tl, timer);
+#else
+   (wl_timer_t *)data;
+#endif
 
if (!WL_ALL_PASSIVE_ENAB(t->wl))
_wl_timer(t);
@@ -2349,9 +2365,13 @@
 
bzero(t, sizeof(wl_timer_t));
 
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 15, 0)
+   timer_setup(>timer, wl_timer, 0);
+#else
init_timer(>timer);
t->timer.data = (ulong) t;
t->timer.function = wl_timer;
+#endif
t->wl = wl;
t->fn = fn;
t->arg = arg;

Bug#882026: qtiplot FTBFS: fatal error: sipAPIqti.h: No such file or directory

[Dmitry Shachnev]

Hi Anton!

On Sat, Dec 30, 2017 at 05:50:57PM +0100, Anton Gladky wrote:
> It looks like sip4_4.19 broke the qtiplot (upload without rebuild of all
> reverse dependencies?).

sip 4.19 broke qtiplot, but I reported that and it was fixed. See #872636.

Looks like this time some minor release of sip broke it (probably 4.19.4).
It was a minor release and it was not announced that it can break something,
so I did not test the reverse dependencies that time.

> Anyway, I have tried to fix this particular part of compilation
> process [1]. But it still fails to compile due to major changes in sip.
> Help is welcome.

Please try this patch: https://bugs.gentoo.org/641514#c2

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Processed: tagging 884158

[Debian Bug Tracking System]

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

> tags 884158 + pending
Bug #884158 [src:syncevolution] FTBFS with libical 3.0
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 884158

[Debian Bug Tracking System]

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

> tags 884158 + fixed-upstream
Bug #884158 [src:syncevolution] FTBFS with libical 3.0
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#885102: marked as done (fpc: upgrading from 3.0.4+dfsg-2 to 3.0.4+dfsg-9 fails on /usr/bin/grab_vcsa-3.0.4)

[Debian Bug Tracking System]

Your message dated Sat, 30 Dec 2017 21:36:37 +
with message-id 
and subject line Bug#885102: fixed in fpc 3.0.4+dfsg-11
has caused the Debian Bug report #885102,
regarding fpc: upgrading from 3.0.4+dfsg-2 to 3.0.4+dfsg-9 fails on 
/usr/bin/grab_vcsa-3.0.4
to be marked as done.

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

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


-- 
885102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885102
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fpc
Version: 3.0.4+dfsg-9
Severity: serious
Justification: Fails to upgrade cleanly

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Piuparts¹ found that one can't upgrade from 3.0.4+dfsg-2 to 3.0.4+dfsg-9.

  dpkg: error processing archive 
/tmp/apt-dpkg-install-4InTKV/02-fp-utils-3.0.4_3.0.4+dfsg-9_amd64.deb 
(--unpack):
   trying to overwrite '/usr/bin/grab_vcsa-3.0.4', which is also in package 
fp-compiler-3.0.4:amd64 3.0.4+dfsg-2

Paul
¹ https://piuparts.debian.org/testing2sid/fail/fpc_3.0.4+dfsg-9.log

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

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

Versions of packages fpc depends on:
ii  fp-docs-3.0.4   3.0.4+dfsg-2
ii  fp-utils-3.0.4  3.0.4+dfsg-2
ii  fpc-3.0.4   3.0.4+dfsg-2

fpc recommends no packages.

fpc suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAlo+tjAACgkQnFyZ6wW9
dQpiUgf/RdGS+MW+9F80t/9oY++FGzYzmkzEfyohYcjL4YIzr7sEqSZEuLajnBpe
wVCISlA5rRF4z8ESqMP/vpBR1hIoJTBTERAqCqdEjJrPEVOAEF5f5ZH0YwySoEf7
inHn5Z85TdBFFfOYGYVHZeK7sROwJ8U3YGuoWWzUxPAp1C5KrAcQVwwhEYln/jps
XHy7Gfoy5OeMt2urqfswjOjjRHS/7TNqUiQoTgxdfA6xyTn+i6akV5qZUPPlVV4v
Hw5nc3DpfzK/10mhvamoM+IZ1HnLzaof1xrdvDgOjGYZbLTTMxEN3McvcWaGVSpC
lXnx9xizuV/CeYvfk9GksWZajZ3XpA==
=0up5
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: fpc
Source-Version: 3.0.4+dfsg-11

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

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

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

Debian distribution maintenance software
pp.
Abou Al Montacir  (supplier of updated fpc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 30 Dec 2017 21:14:32 +0100
Source: fpc
Binary: fpc-3.0.4 fpc-source-3.0.4 fp-compiler-3.0.4 fp-ide-3.0.4 
fp-utils-3.0.4 fp-docs-3.0.4 fp-units-rtl-3.0.4 fp-units-base-3.0.4 
fp-units-fcl-3.0.4 fp-units-fv-3.0.4 fp-units-gtk2-3.0.4 fp-units-db-3.0.4 
fp-units-gfx-3.0.4 fp-units-net-3.0.4 fp-units-math-3.0.4 fp-units-misc-3.0.4 
fp-units-multimedia-3.0.4 fp-units-i386-3.0.4 fpc fpc-source fp-compiler fp-ide 
fp-utils fp-docs fp-units-rtl fp-units-base fp-units-fcl fp-units-fv 
fp-units-gtk2 fp-units-db fp-units-gfx fp-units-net fp-units-math fp-units-misc 
fp-units-multimedia fp-units-i386
Architecture: source
Version: 3.0.4+dfsg-11
Distribution: unstable
Urgency: medium
Maintainer: Pascal Packaging Team 
Changed-By: Abou Al Montacir 
Description:
 fp-compiler - Free Pascal - compiler dependency package
 fp-compiler-3.0.4 - Free Pascal - compiler
 fp-docs- Free Pascal - documentation dependency package
 fp-docs-3.0.4 - Free Pascal - documentation
 fp-ide - Free Pascal - IDE dependency package
 fp-ide-3.0.4 - Free Pascal - IDE
 fp-units-base - Free Pascal - base units dependency package
 fp-units-base-3.0.4 - Free Pascal - base units
 fp-units-db - Free Pascal - database-library units dependency package
 fp-units-db-3.0.4 - Free Pascal - database-library units
 fp-units-fcl - Free Pascal - Free Component Library dependency package
 fp-units-fcl-3.0.4 - Free Pascal - Free Component Library
 fp-units-fv - Free Pascal - Free Vision units dependency package
 

Bug#885884: bashburn: does not work: it passes incorrect options to wodim, so no CD can ever be burnt

[Stephen McGregor]

Package: bashburn
Version: 3.0.1-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Correctly makes *.WAV files, but then incorrectly constructs the wodim
command line, so can not work




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

Kernel: Linux 4.13.0-rc5-686-pae (SMP w/1 CPU core)
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: sysvinit (via /sbin/init)

Versions of packages bashburn depends on:
ii  bash 4.4-5
ii  cdparanoia   3.10.2+debian-11.1
ii  cdrdao   1:1.2.3-3
ii  dvd+rw-tools 7.1-11.1
ii  eject2.1.5+deb1+cvs20081104-13.2
ii  flac 1.3.2-1
ii  genisoimage  9:1.1.11-3+b2
ii  mpg123   1.25.8-1
ii  normalize-audio  0.7.7-14+b1
ii  sudo 1.8.21p2-3
ii  vorbis-tools 1.4.0-10.1
ii  wodim9:1.1.11-3+b2

bashburn recommends no packages.

bashburn suggests no packages.

-- no debconf information

Processed: tagging 885283

[Debian Bug Tracking System]

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

> tags 885283 + confirmed upstream
Bug #885283 [src:ganyremote] ganyremote: Depends on unmaintained pygtk
Added tag(s) upstream and confirmed.
> thanks
Stopping processing here.

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

Processed: tagging 885273

[Debian Bug Tracking System]

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

> tags 885273 + confirmed upstream
Bug #885273 [src:diffuse] diffuse: Depends on unmaintained pygtk
Added tag(s) upstream and confirmed.
> thanks
Stopping processing here.

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

Bug#885881: mp3burn: does not work at all, produces blank CD ROMs

[Stephen McGregor]

Package: mp3burn
Version: 0.4.2-2.2
Severity: grave
Justification: renders package unusable

Dear Maintainer,


Ran 

 mp3burn --check ATIP -o "dev=/dev/sr0 speed=10 "  -M lame  *mp3 

in  a directory of mp3 files.

A CD of blank tracks was produced. 

Also, 

- the defaults are insane: can convert anything to a music CD, as long as
the files are in a nutty configuration

- last updated in 2002, 15-16 years ago. 



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

Kernel: Linux 4.13.0-rc5-686-pae (SMP w/1 CPU core)
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: sysvinit (via /sbin/init)

Versions of packages mp3burn depends on:
ii  file1:5.32-1
ii  libmp3-info-perl1.24-1.2
ii  libogg-vorbis-header-pureperl-perl  1.0-4
ii  libstring-shellquote-perl   1.04-1
ii  mpg123  1.25.8-1
ii  perl5.26.1-3
ii  vorbis-tools1.4.0-10.1
ii  wodim   9:1.1.11-3+b2

mp3burn recommends no packages.

Versions of packages mp3burn suggests:
ii  flac1.3.2-1
pn  libaudio-flac-perl  

-- no debconf information

Bug#885880: deluge: Depends on unmaintained pygtk

[Jeremy Bicha]

Package: deluge-gtk
Version: 1.3.15-2
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

deluge-gtk depends on python-glade2 which depends on python-gtk2. Both
come from the pygtk source. pygtk is unmaintained upstream. It has not
had a release since GNOME 3 was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings (and gtk3).

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885876: seelablet: wrong dependencies, app won't run

[Jeremy Bicha]

Source: seelablet
Version: 1.0.6-2
Severity: serious
Tags: sid buster

seelablet depends on python-seelablet (and not python3-seelablet)
although /usr/bin/Experiments has a python3 shebang.

When I tried to run /usr/bin/Experiments in a default Ubuntu 17.10
install (so using GNOME), I got

  $ Experiments 
  Traceback (most recent call last):
File "/usr/bin/Experiments", line 17, in 
  import sip
  ModuleNotFoundError: No module named 'sip'

Ok, so python3-seelablet needs to depend on python3-sip. After
installing that, I got

  $ Experiments 
  Traceback (most recent call last):
File "/usr/bin/Experiments", line 21, in 
  from PyQt4 import QtWebKit
  ImportError: cannot import name 'QtWebKit'

And that's where I stopped because it doesn't look like that's
available in Debian.

Thanks,
Jeremy Bicha

Bug#885875: seelablet: Depends on python-appindicator

[Jeremy Bicha]

Source: seelablet
Version: 1.0.6-2
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs
Tags: sid buster

python-seelablet depends on python-appindicator but python3-seelablet
depends on gir1.2-appindicator3-0.1

The gir dependency is wrong since as far as I can tell seelablet
doesn't use GObject Introspection at all. I *think* the python-
appindicator dependency is wrong too because I thought python-
appindicator required gtk and this doesn't use gtk at all.

(I can't actually tell if it works because I can't get the app to run.
Filing a separate bug for that.)

I'm filing this bug as Serious since this is the last package keeping
python-appindicator from being removable in Testing.

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#874176: git HEAD works for me

[Philipp Marek]

Using git HEAD gives me a working binary, so I suspect some interaction 
with changed liblua versions.


(4.0.1 doesn't work for me any more, but it did in the past.)


Please provide a package with from the current sources, thank you!

Bug#876608: [Pkg-sass-devel] Bug#876608: ruby-compass (build) depends on ruby-sass (< 3.5), but 3.5.1-2 is in unstable

[Daniele Scasciafratte]

Any updates for this ticket?

Bug#885071: marked as done (libelf-dev: pkg-config --exists/--cflags libelf fail without zlib1g-dev)

[Debian Bug Tracking System]

Your message dated Sat, 30 Dec 2017 17:34:49 +
with message-id 
and subject line Bug#885071: fixed in elfutils 0.170-0.2
has caused the Debian Bug report #885071,
regarding libelf-dev: pkg-config --exists/--cflags libelf fail without 
zlib1g-dev
to be marked as done.

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

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


-- 
885071: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885071
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libelf-dev
Version: 0.170-0.1
Severity: normal

Dear Maintainer,

Due to the use of "Requires.private: zlib" in the libelf.pc pkg-config
file, the following fails:

$ pkg-config --exists libelf; echo $?
1

$ pkg-config --cflags libelf
Package zlib was not found in the pkg-config search path.
Perhaps you should add the directory containing `zlib.pc'
to the PKG_CONFIG_PATH environment variable
Package 'zlib', required by 'libelf', not found


That is because pkg-config's Requires.private is parsed even when --
static is not used when calling pkg-config, even though it's only
needed when building a static library.

Please consider either adding a dependency to zlib1g-dev in libelf-dev
so that the required zlib pkg-config file is always available or to
change from "Requires.private: zlib" to "Libs.private: -lz" as a
workaround (yes it only applies to Requires, not to Libs - that's a
decision by the upstream developers of pkg-config).

Found while rebuilding iproute2 in a minimal chroot.

Thanks!

-- 
Kind regards,
Luca Boccassi

signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: elfutils
Source-Version: 0.170-0.2

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

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

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

Debian distribution maintenance software
pp.
Andreas Henriksson  (supplier of updated elfutils package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 30 Dec 2017 18:14:17 +0100
Source: elfutils
Binary: elfutils libelf1 libelf-dev libdw-dev libdw1 libasm1 libasm-dev
Architecture: source
Version: 0.170-0.2
Distribution: unstable
Urgency: medium
Maintainer: Kurt Roeckx 
Changed-By: Andreas Henriksson 
Description:
 elfutils   - collection of utilities to handle ELF objects
 libasm-dev - libasm development libraries and header files
 libasm1- library with a programmable assembler interface
 libdw-dev  - libdw1 development libraries and header files
 libdw1 - library that provides access to the DWARF debug information
 libelf-dev - libelf1 development libraries and header files
 libelf1- library to read and write ELF files
Closes: 885071
Changes:
 elfutils (0.170-0.2) unstable; urgency=medium
 .
   * Non-maintainer upload, acked by maintainer.
   * libelf-dev,libdw-dev: Add missing dependencies for packages that
 our pkg-config files requires (zlib1g-dev, liblzma-dev).
 (Closes: #885071)
Checksums-Sha1:
 ff5fa69cea052aa797ea801870c6c50b8ce7179a 2332 elfutils_0.170-0.2.dsc
 3c703277f084fcf57477c24ff91fe6034466a62a 37624 elfutils_0.170-0.2.debian.tar.xz
 d7522b3f5790550ded54d08d6ae1d1d6fb780874 9067 
elfutils_0.170-0.2_amd64.buildinfo
Checksums-Sha256:
 f743714766279f7057c1dab7f9d1e01489e28dfef183f8e967e53e128618a2f8 2332 
elfutils_0.170-0.2.dsc
 ac606bf158ca966392963996f3ccd299ed3af13421ca61c044150688d758ffd2 37624 
elfutils_0.170-0.2.debian.tar.xz
 547fa288d3ce5100ef57d679d2b04f65155b5f76fdad5e9723a98735e0566e7b 9067 
elfutils_0.170-0.2_amd64.buildinfo
Files:
 08dccddcecd6768e75ecebbe3a1faab7 2332 libs optional elfutils_0.170-0.2.dsc
 d72f3d4671b3a358b02e818e842c5642 37624 libs optional 
elfutils_0.170-0.2.debian.tar.xz
 777bba8de508ba47cd7a12f98ca22bb6 9067 libs optional 
elfutils_0.170-0.2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE+uHltkZSvnmOJ4zCC8R9xk0TUwYFAlpHyugRHGFuZHJlYXNA
ZmF0YWwuc2UACgkQC8R9xk0TUwZxew/+KSBHCkO+tLkAMpjUc+FJqPMDC+BCOKuJ
0p94/dpoO1Hb46Z5NhXtTxCmZ3xIIBgHfuVd2jtu/O9ZjSyLAAmc3zZZWN6APJUj

Bug#885071: missing dependency -> serious

[Andreas Henriksson]

Hi Kurt,

On Fri, Dec 29, 2017 at 06:35:00PM +0100, Kurt Roeckx wrote:
> Feel free to upload this. I can upload it for you if needed.

Thanks for the quick feedback. I've just uploaded it to unstable now.

Regards,
Andreas Henriksson

Bug#882026: qtiplot FTBFS: fatal error: sipAPIqti.h: No such file or directory

[Anton Gladky]

It looks like sip4_4.19 broke the qtiplot (upload without rebuild of all reverse
dependencies?).

Anyway, I have tried to fix this particular part of compilation
process [1]. But it still fails to compile due to major changes in sip.
Help is welcome.

[1] 
https://anonscm.debian.org/cgit/debian-science/packages/qtiplot.git/commit/?id=1843f2737a0293739c637dc8a526b315d786346d

Regards

Anton


2017-11-17 19:16 GMT+01:00 Adrian Bunk :
> Source: qtiplot
> Version: 0.9.8.9-16
> Severity: serious
>
> Some recent change in unstable makes qtiplot FTBFS:
>
> https://tests.reproducible-builds.org/debian/history/qtiplot.html
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/qtiplot.html
>
> ...
> src/scripting/PythonScripting.cpp:61:10: fatal error: sipAPIqti.h: No such 
> file or directory
>  #include "sipAPIqti.h"
>   ^
>
> --
> debian-science-maintainers mailing list
> debian-science-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#885628: marked as done (grcm: Please drop Build-Depends on scrollkeeper)

[Debian Bug Tracking System]

Your message dated Sat, 30 Dec 2017 16:28:43 +
with message-id 
and subject line Bug#885755: Removed package(s) from unstable
has caused the Debian Bug report #885628,
regarding grcm: Please drop Build-Depends on scrollkeeper
to be marked as done.

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

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


-- 
885628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885628
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: grcm
Version: 0.1.6-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs rarian
Tags: sid buster

scrollkeeper has been deprecated and unmaintained for years. Its
replacement, rarian has been deprecated for years too. More
importantly, it doesn't seem to be needed at all. yelp can easily
display Docbook help files without any .omf files.

We do not intend to ship rarian in Debian 10 "Buster". Therefore,
please drop rarian-compat from buzztrax's Build-Depends.

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 0.1.6-1+rm

Dear submitter,

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

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

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

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

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

Bug#883562: marked as done (ejabberd suddenly take all cpu)

[Debian Bug Tracking System]

Your message dated Sat, 30 Dec 2017 16:19:02 +
with message-id 
and subject line Bug#883562: fixed in ejabberd 17.11-1
has caused the Debian Bug report #883562,
regarding ejabberd suddenly take all cpu
to be marked as done.

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

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


-- 
883562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883562
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ejabberd
Version: 17.08-3

Hello,

with a sudden change ejabberd takes all cpu time on all core,
leading to very high system loads.

I am not aware of any specific change except erlang_p1* file
entered testing recently.

I do not see an apparant reason, and find nothing in the ejabberd
log.

How can I debug this any furhter?

TIA,

Joerg


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ejabberd
Source-Version: 17.11-1

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

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

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

Debian distribution maintenance software
pp.
Philipp Huebner  (supplier of updated ejabberd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 30 Dec 2017 17:01:53 +0100
Source: ejabberd
Binary: ejabberd
Architecture: source amd64
Version: 17.11-1
Distribution: unstable
Urgency: medium
Maintainer: Ejabberd Packaging Team 
Changed-By: Philipp Huebner 
Description:
 ejabberd   - distributed, fault-tolerant Jabber/XMPP server
Closes: 772031 878034 883024 883143 883416 883546 883562 883930 884531 885132
Changes:
 ejabberd (17.11-1) unstable; urgency=medium
 .
   [ Neil Castelino ]
   * Fix issue where debian/config did not work well with apt
   * Include erlang options in debconf query during configuration
 (Closes: #878034)
 .
   [ Philipp Huebner ]
   * New upstream version 17.11 (Closes: #772031, #883562, #885132)
   * Refreshed patches for 17.11
   * Increased (Build-)Depends for 17.11
   * Switched debian/watch to https
   * Enabled new graphics feature in debian/rules
   * Set apparmor profile to complain (Closes: #883143)
   * Improved default ejabberd.yml
   * Updated de.po
   * Updated pt.po (Closes: #883024)
   * Updated ru.po (Closes: #883416)
   * Updated pt_BR.po (Closes: #883546)
   * Updated es.po
   * Updated nl.po
   * Updated fr.po (Closes: #884531)
   * Improved AppArmor profile for usrmerge (Closes: #883930)
 Thanks Vincas Dargis for reporting and patching!
Checksums-Sha1:
 6f03288c74bbffeeb01f9cbc7e5f387c2550e1a3 2795 ejabberd_17.11-1.dsc
 91216df8899b4751e7616b351834e7742353d35d 1727050 ejabberd_17.11.orig.tar.gz
 48834cafd356724abb4aa127ca665732adb3849f 64352 ejabberd_17.11-1.debian.tar.xz
 d4e1ba971c16c1933f755b28e4e3a15e4624201f 10175 ejabberd_17.11-1_amd64.buildinfo
 13ef2d25524c589c5f56c89d206e504b1f1ba65f 5549476 ejabberd_17.11-1_amd64.deb
Checksums-Sha256:
 a7e8fc6be168c276196e501dce08255c484d9d25b667eb7747de633b0cb0ad77 2795 
ejabberd_17.11-1.dsc
 f1c204d1ad6cb32cb53c6168bdb569120057db4bd5120f01ed2c131982538fd5 1727050 
ejabberd_17.11.orig.tar.gz
 9e475cfdd201bed53294e2b0e5bb5d011413c33196b637adf27acf0c83f3d941 64352 
ejabberd_17.11-1.debian.tar.xz
 14115f3a3849c12f918aad6682cb2ec305b20b7cc238652bc54eb1cae2a46fff 10175 
ejabberd_17.11-1_amd64.buildinfo
 3ca2109d55a2c30dd1f1a2d07b0c5a2165d0e7e2cc627894e4d560c7603b4230 5549476 
ejabberd_17.11-1_amd64.deb
Files:
 c5bf2c65e551c4e533cf4bc81df7ab24 2795 net optional ejabberd_17.11-1.dsc
 1ce0d7333a34b1d19c62948b5951a163 1727050 net optional 
ejabberd_17.11.orig.tar.gz
 1be8ff1261305b24a3967c571a513b5c 64352 net optional 
ejabberd_17.11-1.debian.tar.xz
 6364f9cfce71911a1b0590d8212c5113 10175 net optional 
ejabberd_17.11-1_amd64.buildinfo
 54b69e3d78b58170a09e914427c78682 5549476 net optional 
ejabberd_17.11-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEECEGLvkRyDy26xQXsunokltrkDRwFAlpHuUwVHGRlYmFsYW5j
ZUBkZWJpYW4ub3JnAAoJELp6JJba5A0cKM0P/3kMJrwTqZs9faaS4NJi1jTKmoGh
UauYuUxteI2dP7BoMxVrDaLI94vK04KmXJ1gRLC2p7BuMhyKtU5SuNxnO5aUyZSH

Bug#885132: marked as done (ejabberd 17.08 is incompatible with erlang-p1-xmpp 1.16)

[Debian Bug Tracking System]

Your message dated Sat, 30 Dec 2017 16:19:02 +
with message-id 
and subject line Bug#885132: fixed in ejabberd 17.11-1
has caused the Debian Bug report #885132,
regarding ejabberd 17.08 is incompatible with erlang-p1-xmpp 1.16
to be marked as done.

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

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


-- 
885132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885132
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ejabberd
Version: 17.08-3
Severity: important

Since the last upgrade in Buster my ejabberd server has problems
with s2s outgoing connections. See the bugreport I posted upgream:
"Hook s2s_out_closed crashed"
https://github.com/processone/ejabberd/issues/2185

Downgrading erlang-p1-xmpp to 1.14 solves the problem as
suggested by the upstream developer.


-- System Information:
Debian Release: 9.3
  APT prefers stable
  APT policy: (800, 'stable'), (200, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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)

Versions of packages ejabberd depends on:
ii  adduser3.115
ii  debconf [debconf-2.0]  1.5.61
ii  erlang-asn11:20.2.1+dfsg-1
ii  erlang-base [erlang-abi-17.0]  1:20.2.1+dfsg-1
ii  erlang-crypto  1:20.2.1+dfsg-1
ii  erlang-inets   1:20.2.1+dfsg-1
ii  erlang-jiffy   0.14.8+dfsg-1
ii  erlang-lager   3.5.2-1
ii  erlang-mnesia  1:20.2.1+dfsg-1
ii  erlang-odbc1:20.2.1+dfsg-1
ii  erlang-p1-cache-tab1.0.12-1
ii  erlang-p1-iconv1.0.6-1
ii  erlang-p1-stringprep   1.0.10-1
ii  erlang-p1-tls  1.0.17-1
ii  erlang-p1-utils1.0.10-1
ii  erlang-p1-xml  1.1.25-1
ii  erlang-p1-xmpp 1.1.14-1
ii  erlang-p1-yaml 1.0.12-1
ii  erlang-p1-zlib 1.0.3-1
ii  erlang-public-key  1:20.2.1+dfsg-1
ii  erlang-ssl 1:20.2.1+dfsg-1
ii  erlang-syntax-tools1:20.2.1+dfsg-1
ii  erlang-xmerl   1:20.2.1+dfsg-1
ii  init-system-helpers1.48
ii  lsb-base   9.20161125
ii  openssl1.1.0f-3+deb9u1
ii  ucf3.0036

ejabberd recommends no packages.

Versions of packages ejabberd suggests:
pn  apparmor 
pn  apparmor-utils   
pn  ejabberd-contrib 
pn  erlang-luerl 
pn  erlang-p1-mysql  
pn  erlang-p1-oauth2 
pn  erlang-p1-pam
pn  erlang-p1-pgsql  
pn  erlang-p1-sip
pn  erlang-p1-sqlite3
pn  erlang-p1-stun   
pn  erlang-redis-client  
pn  imagemagick  
pn  libunix-syslog-perl  
pn  yamllint 

-- Configuration Files:
/etc/default/ejabberd changed [not included]
/etc/logrotate.d/ejabberd changed [not included]

-- debconf information excluded
--- End Message ---
--- Begin Message ---
Source: ejabberd
Source-Version: 17.11-1

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

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

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

Debian distribution maintenance software
pp.
Philipp Huebner  (supplier of updated ejabberd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 30 Dec 2017 17:01:53 +0100
Source: ejabberd
Binary: ejabberd
Architecture: source amd64
Version: 17.11-1
Distribution: unstable
Urgency: medium
Maintainer: Ejabberd Packaging Team 
Changed-By: Philipp Huebner 
Description:
 ejabberd   - distributed, fault-tolerant Jabber/XMPP server
Closes: 772031 878034 883024 883143 883416 883546 883562 883930 884531 885132
Changes:
 ejabberd (17.11-1) unstable; urgency=medium
 .
   [ Neil Castelino ]
   * Fix issue where debian/config did not work well with apt
   * Include erlang options in debconf query during 

Bug#885401: openmw uninstallable

[Markus Koschany]

Hi,

I suggest to continue the conversation in private. You can contact me
for future uploads directly. Should I be unresponsive, please ask for
sponsorship on the debian-games mailing list and someone will hopefully
help you. Have you considered to become a Debian maintainer?

Am 28.12.2017 um 19:30 schrieb bret curtis:
> Hello Markus, that would be awfully friendly of you. :)
> 
> Order of operations:
> 1) MyGUI needs to be bumped:
> https://qa.debian.org/cgi-bin/vcswatch?package=mygui  I've cleaned up
> the package a bit in the process to handle GCC7, debug symbols and
> other bits.

Uploaded. Thank you. Packaging could be slightly improved, e.g. compat
level 11 is now recommended but so far so good.

> 2) OpenAL-Soft https://qa.debian.org/cgi-bin/vcswatch?package=openal-soft
> needs love as well, but this isn't required for OpenMW release.

Great. I'll review that next year. ;)

> 3) OpenMW, once the libraries above are available we can upload/build
> OpenMW packages: https://qa.debian.org/cgi-bin/vcswatch?package=openmw

OpenMW fails to build for me. I've pushed some small changes to Git.
Could you take a look please?

> 
> bonus points:
> 4) WildMIDI should be updated as well:
> https://qa.debian.org/cgi-bin/vcswatch?package=wildmidi  <-- this has
> nothing to with OpenMW but is a new upstream release that I maintain.
> :)

Sure. I suggest to update the same things here: compat level,
Standard-Version, etc. I guess I can review that in a few days as well.

Cheers,

Markus



signature.asc
Description: OpenPGP digital signature

Processed: Severity #885825 isn't serious

[Debian Bug Tracking System]

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

> severity 885825 normal
Bug #885825 [miniupnpd] miniupnpd: listen needs to be set to an interface, not 
an ip addres
Severity set to 'normal' from 'serious'
>
End of message, stopping processing here.

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

Processed: tagging 885132

[Debian Bug Tracking System]

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

> tags 885132 + pending
Bug #885132 [ejabberd] ejabberd 17.08 is incompatible with erlang-p1-xmpp 1.16
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#876600: marked as done (hex-a-hop FTBFS: msgfmt: found 1 fatal error)

[Debian Bug Tracking System]

Your message dated Sat, 30 Dec 2017 16:00:11 +
with message-id 
and subject line Bug#876600: fixed in hex-a-hop 1.1.0+git20140926-1
has caused the Debian Bug report #876600,
regarding hex-a-hop FTBFS: msgfmt: found 1 fatal error
to be marked as done.

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

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


-- 
876600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876600
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hex-a-hop
Version: 0.0.20070315-8
Severity: serious
Tags: buster sid

Some recent change in unstable makes hex-a-hop FTBFS:

https://tests.reproducible-builds.org/debian/history/hex-a-hop.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/hex-a-hop.html

...
make[1]: Entering directory '/build/1st/hex-a-hop-0.0.20070315/debian/i18n'
cd ../..; g++ -Wall -W -g -DUSE_GETTEXT -O2 -E hex_puzzzle.cpp -o 
debian/i18n/hex_puzzzle_preprocessed.cpp
Creating Template "hex-a-hop.pot"
cd ../..; xgettext --add-comments="TRANSLATORS:" -k_ -o 
"debian/i18n/hex-a-hop.pot.templ" \
  gfx.cpp hex_puzzzle.cpp menus.h level_list.h 
debian/i18n/hex_puzzzle_preprocessed.cpp \
--msgid-bugs-address=hex-a-...@packages.debian.org \
--copyright-holder="Tom Beaumont"
cd ../..; po4a-updatepo -f man -m debian/hex-a-hop.6 -p 
debian/i18n/hex-a-hop.6.pot
sed 's/charset=CHARSET/charset=ascii/' hex-a-hop.pot.templ > 
hex-a-hop.pot.templ.po
sed 's/charset=CHARSET/charset=ascii/' hex-a-hop.6.pot > hex-a-hop.6.pot.po
sed -n '1,/^$/ p' hex-a-hop.pot.templ | sed "/^#$/ r hex-a-hop.pot.comments" > 
hex-a-hop.pot
msgcat --width=79 hex-a-hop.pot.templ.po hex-a-hop.6.pot.po | sed -n '1,/^$/ 
!p' >> hex-a-hop.pot
rm -f hex-a-hop.pot.templ hex-a-hop.6.pot hex-a-hop.pot.templ.po 
hex-a-hop.6.pot.po
Updating "bg" translation
.. done.
Updating "de" translation
.. done.
Updating "es" translation
.. done.
Updating "ja" translation
 done.
Updating "nl" translation
.. done.
Updating "pl" translation
 done.
Updating "ru" translation
.. done.
Updating "ta" translation
.. done.
Updating "vi" translation
 done.
Building "bg" translation
Your input po file plural_forms_stripped.po seems outdated (The amount of 
entries differ between files: 212 is not 18
). Please consider running po4a-updatepo to refresh it.
Building "de" translation
Your input po file plural_forms_stripped.po seems outdated (The amount of 
entries differ between files: 212 is not 18
). Please consider running po4a-updatepo to refresh it.
Building "es" translation
Your input po file plural_forms_stripped.po seems outdated (The amount of 
entries differ between files: 212 is not 18
). Please consider running po4a-updatepo to refresh it.
Building "ja" translation
Invalid po file plural_forms_stripped.po:
plural_forms_stripped.po:54: number of format specifications in 'msgid' and 
'msgstr' does not match
msgfmt: found 1 fatal error

Makefile:49: recipe for target 'build-stamp' failed
make[1]: *** [build-stamp] Error 1
--- End Message ---
--- Begin Message ---
Source: hex-a-hop
Source-Version: 1.1.0+git20140926-1

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

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

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated hex-a-hop package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 25 Dec 2017 15:24:56 +0100
Source: hex-a-hop
Binary: hex-a-hop hex-a-hop-data
Architecture: source all amd64
Version: 1.1.0+git20140926-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Description:
 hex-a-hop  - puzzle game based on hexagonal tiles
 hex-a-hop-data - graphics, audio, levels and translations for Hex-a-hop
Closes: 550583 550585 563187 567911 718656 724862 876600
Changes:
 hex-a-hop 

Bug#878937: marked as done (visp: port baseline violation on i386+amd64 (also causes FTBFS on amd64))

[Debian Bug Tracking System]

Your message dated Sat, 30 Dec 2017 16:00:22 +
with message-id 
and subject line Bug#878937: fixed in visp 3.1.0-1
has caused the Debian Bug report #878937,
regarding visp: port baseline violation on i386+amd64 (also causes FTBFS on 
amd64)
to be marked as done.

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

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


-- 
878937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878937
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: visp
Version: 3.0.1-2
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=visp=i386=3.0.1-2=1487064152=0

...
-- Performing Test HAVE_CXX_MSSE2
-- Performing Test HAVE_CXX_MSSE2 - Success
-- Performing Test HAVE_C_MSSE2
-- Performing Test HAVE_C_MSSE2 - Success
-- Performing Test HAVE_CXX_MSSE3
-- Performing Test HAVE_CXX_MSSE3 - Success
-- Performing Test HAVE_C_MSSE3
-- Performing Test HAVE_C_MSSE3 - Success
-- Performing Test HAVE_CXX_MSSSE3
-- Performing Test HAVE_CXX_MSSSE3 - Success
-- Performing Test HAVE_C_MSSSE3
-- Performing Test HAVE_C_MSSSE3 - Success
...
-- C++ flags (Release): -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -Wall -Wextra -fopenmp 
-fvisibility=hidden -msse2 -msse3 -mssse3 -fPIC -g -O2 
-fdebug-prefix-map=/«PKGBUILDDIR»=. -specs=/usr/share/dpkg/no-pie-compile.specs 
-fstack-protector-strong -Wformat -Werror=format-security
-- C++ flags (Debug):   -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -Wall -Wextra -fopenmp 
-fvisibility=hidden -msse2 -msse3 -mssse3 -fPIC -g
-- C Compiler:  /usr/bin/cc
-- C flags (Release):   -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -Wall -Wextra -fopenmp 
-fvisibility=hidden -msse2 -msse3 -mssse3 -fPIC -g -O2 
-fdebug-prefix-map=/«PKGBUILDDIR»=. -specs=/usr/share/dpkg/no-pie-compile.specs 
-fstack-protector-strong -Wformat -Werror=format-security
-- C flags (Debug): -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -Wall -Wextra -fopenmp 
-fvisibility=hidden -msse2 -msse3 -mssse3 -fPIC -g
...
The following tests FAILED:
  2 - testConversion (ILLEGAL)
  4 - testCropAdvanced (ILLEGAL)
 14 - testIoPPM (ILLEGAL)
 16 - testReadImage (ILLEGAL)
 37 - testHistogram (ILLEGAL)
 71 - testKeyPoint-5 (ILLEGAL)
 72 - testKeyPoint-6 (ILLEGAL)
 73 - testKeyPoint-7 (ILLEGAL)
100 - imageDiskRW (ILLEGAL)
Errors while running CTest
Makefile:107: recipe for target 'test' failed
make[2]: *** [test] Error 8


The baseline of the amd64 port includes nothing higher than SSE2.

The baseline of the i386 port includes no SSE (not even MMX).
--- End Message ---
--- Begin Message ---
Source: visp
Source-Version: 3.1.0-1

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

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

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

Debian distribution maintenance software
pp.
Fabien Spindler  (supplier of updated visp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 28 Dec 2017 10:31:31 +0100
Source: visp
Binary: libvisp-dev libvisp-core-dev libvisp-core3.1 libvisp-core3.1-dbg 
libvisp-gui-dev libvisp-gui3.1 libvisp-gui3.1-dbg libvisp-imgproc-dev 
libvisp-imgproc3.1 libvisp-imgproc3.1-dbg libvisp-io-dev libvisp-io3.1 
libvisp-io3.1-dbg libvisp-detection-dev libvisp-detection3.1 
libvisp-detection3.1-dbg libvisp-ar-dev libvisp-ar3.1 libvisp-ar3.1-dbg 
libvisp-blob-dev libvisp-blob3.1 libvisp-blob3.1-dbg libvisp-me-dev 
libvisp-me3.1 libvisp-me3.1-dbg libvisp-klt-dev libvisp-klt3.1 

Bug#856703: marked as done (visp: License violation)

[Debian Bug Tracking System]

Your message dated Sat, 30 Dec 2017 16:00:22 +
with message-id 
and subject line Bug#856703: fixed in visp 3.1.0-1
has caused the Debian Bug report #856703,
regarding visp: License violation
to be marked as done.

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

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


-- 
856703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856703
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: visp
Severity: serious
Hi. visp is using some numerical routines from numerical recipes. These
are NOT free software and may not be used in a free software project.

For Debian, you can elide these sources. It would also be great if you
talked to upstream so that they stop violating copyrights also.

Look at vpMatrix::svdNr() in

  modules/core/src/math/matrix/vpMatrix_svd.cpp

A later version of the book chapter this function came from lives here:

  http://numerical.recipes/webnotes/nr3web2.pdf

You can see many similarities. If you look at the older version of the
book, you will see 100% similarities.

The copyright statement is here:

  http://numerical.recipes/public-domain.html


I haven't done a thorough search, and the SVD implementation isn't the
only violation here. For instance I also see

  vpMatrix::LUBksb() and vpMatrix::LUDcmp()

but it would be great if you looked more thoroughly.

Thanks
--- End Message ---
--- Begin Message ---
Source: visp
Source-Version: 3.1.0-1

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

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

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

Debian distribution maintenance software
pp.
Fabien Spindler  (supplier of updated visp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 28 Dec 2017 10:31:31 +0100
Source: visp
Binary: libvisp-dev libvisp-core-dev libvisp-core3.1 libvisp-core3.1-dbg 
libvisp-gui-dev libvisp-gui3.1 libvisp-gui3.1-dbg libvisp-imgproc-dev 
libvisp-imgproc3.1 libvisp-imgproc3.1-dbg libvisp-io-dev libvisp-io3.1 
libvisp-io3.1-dbg libvisp-detection-dev libvisp-detection3.1 
libvisp-detection3.1-dbg libvisp-ar-dev libvisp-ar3.1 libvisp-ar3.1-dbg 
libvisp-blob-dev libvisp-blob3.1 libvisp-blob3.1-dbg libvisp-me-dev 
libvisp-me3.1 libvisp-me3.1-dbg libvisp-klt-dev libvisp-klt3.1 
libvisp-klt3.1-dbg libvisp-sensor-dev libvisp-sensor3.1 libvisp-sensor3.1-dbg 
libvisp-robot-dev libvisp-robot3.1 libvisp-robot3.1-dbg 
libvisp-visual-features-dev libvisp-visual-features3.1 
libvisp-visual-features3.1-dbg libvisp-vision-dev libvisp-vision3.1 
libvisp-vision3.1-dbg libvisp-vs-dev libvisp-vs3.1 libvisp-vs3.1-dbg 
libvisp-mbt-dev libvisp-mbt3.1 libvisp-mbt3.1-dbg libvisp-tt-dev libvisp-tt3.1 
libvisp-tt3.1-dbg libvisp-tt-mi-dev libvisp-tt-mi3.1 libvisp-tt-mi3.1-dbg 
libvisp-doc
Architecture: source amd64 all
Version: 3.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Fabien Spindler 
Description:
 libvisp-ar-dev - development files for libvisp-ar
 libvisp-ar3.1 - visual servoing platform ar library
 libvisp-ar3.1-dbg - Debugging symbol for libvisp-ar3.1
 libvisp-blob-dev - development files for libvisp-blob
 libvisp-blob3.1 - visual servoing platform blob tracking library
 libvisp-blob3.1-dbg - Debugging symbol for libvisp-blob3.1
 libvisp-core-dev - development files for libvisp-core
 libvisp-core3.1 - visual servoing platform core library
 libvisp-core3.1-dbg - Debugging symbol for libvisp-core3.1
 libvisp-detection-dev - development files for libvisp-detection
 libvisp-detection3.1 - visual servoing platform detection library
 libvisp-detection3.1-dbg - Debugging symbol for libvisp-detection3.1
 libvisp-dev - development files for ViSP
 libvisp-doc - visual servoing library - documentation
 libvisp-gui-dev - development files for libvisp-gui
 libvisp-gui3.1 - visual servoing platform gui library
 libvisp-gui3.1-dbg - Debugging symbol for libvisp-gui3.1
 libvisp-imgproc-dev - development files for libvisp-imgproc
 libvisp-imgproc3.1 - visual servoing platform imgproc 

Processed: tagging 883562

[Debian Bug Tracking System]

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

> tags 883562 + pending
Bug #883562 [ejabberd] ejabberd suddenly take all cpu
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: unblock 885132 with 883017

[Debian Bug Tracking System]

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

> unblock 885132 with 883017
Bug #885132 [ejabberd] ejabberd 17.08 is incompatible with erlang-p1-xmpp 1.16
885132 was blocked by: 883017
885132 was not blocking any bugs.
Removed blocking bug(s) of 885132: 883017
> thanks
Stopping processing here.

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

Bug#856087: marked as done (moon-buggy: Please drop the (build-)dependency against esound)

[Debian Bug Tracking System]

Your message dated Sat, 30 Dec 2017 15:49:24 +
with message-id 
and subject line Bug#856087: fixed in moon-buggy 1:1.0.51-1
has caused the Debian Bug report #856087,
regarding moon-buggy: Please drop the (build-)dependency against esound
to be marked as done.

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

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


-- 
856087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856087
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: moon-buggy
Version: 1.0.51-11
Severity: wishlist
Tags: sid buster
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: esd-removal

Dear maintainer,

Your package is {build-}depending against esound which is deprecated
for quite some times now.

We are planning to remove esound for Buster if possible.

Could you please verify that this dependency is mandatory and if it's
not the case, could you please remove it?

Don't hesitate to contact me if you have any questions.

Kind regards,

Laurent Bigonville 
--- End Message ---
--- Begin Message ---
Source: moon-buggy
Source-Version: 1:1.0.51-1

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

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

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

Debian distribution maintenance software
pp.
Christian T. Steigies  (supplier of updated moon-buggy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 30 Dec 2017 16:27:58 +0100
Source: moon-buggy
Binary: moon-buggy
Architecture: source amd64
Version: 1:1.0.51-1
Distribution: unstable
Urgency: medium
Maintainer: Christian T. Steigies 
Changed-By: Christian T. Steigies 
Description:
 moon-buggy - Drive a car across the moon
Closes: 856087 860439
Changes:
 moon-buggy (1:1.0.51-1) unstable; urgency=medium
 .
   * repackage from scratch using an epoch and dh 9
   * patch Makefile.in to not execute moon-buggy during install-data
   * patch Makefile.in to avoid shipping /usr/share/info/dir.gz
   * drop build-dependency against esound (closes: #856087)
   * remove sound patches
   * drop esd and pause packages from d/control
   * remove esd from POFILES.in
   * update watch file (closes: #860439)
   * do not build-depend on build-essential dpkg-dev
   * updated Standards-Version to 4.1.3 (no changes)
   * remove obsolete d/NEWS
   * provide machine readable copyright file
Checksums-Sha1:
 1e75a1edc4aeea359ba79c86c46ee1867799ab7b 2007 moon-buggy_1.0.51-1.dsc
 7f1c5df99944acfe98eeb5f8d5ab6f28ef61ee7e 263572 moon-buggy_1.0.51.orig.tar.gz
 77d4121680efe5afc99d8a918655b17af3117316 18248 
moon-buggy_1.0.51-1.debian.tar.xz
 5abb2aa81d7db146a8929ed7691f15f2b4cffeda 69148 
moon-buggy-dbgsym_1.0.51-1_amd64.deb
 b1db580c1fff1b194c5e3f1ef9ceb5d807a86332 9165 
moon-buggy_1.0.51-1_amd64.buildinfo
 9a2915cfe8c332869dfb090f056903ec18dec93c 217492 moon-buggy_1.0.51-1_amd64.deb
Checksums-Sha256:
 9a7e72bb3a535458a73fc70884e0b6b8e70e70d34dbe0100bb5391a5c123ac72 2007 
moon-buggy_1.0.51-1.dsc
 352dc16ccae4c66f1e87ab071e6a4ebeb94ff4e4f744ce1b12a769d02fe5d23f 263572 
moon-buggy_1.0.51.orig.tar.gz
 ca2dd590499d0308d5bc69857039215f365cd9480ac8cbf3cc3ca6cc9dc2bf03 18248 
moon-buggy_1.0.51-1.debian.tar.xz
 06d5a51d576ea1122ecaab9ea37cf426f006fe994dafb7e0ad75fe6c685a584e 69148 
moon-buggy-dbgsym_1.0.51-1_amd64.deb
 9d7c5ab0da63a462adcace751601d9654ee70db4c2ebd7a45ad011edc5d72e89 9165 
moon-buggy_1.0.51-1_amd64.buildinfo
 020d5568009d428a8d7d2aefc5dafa458098e8776324a19dc0830480e640ec31 217492 
moon-buggy_1.0.51-1_amd64.deb
Files:
 9b8cab02f14652b49587954718a73ce0 2007 games optional moon-buggy_1.0.51-1.dsc
 bfe23ef5cfa838ac261eee34ea5322f3 263572 games optional 
moon-buggy_1.0.51.orig.tar.gz
 80dcfcad7fd987cd3562eaadacb337b4 18248 games optional 
moon-buggy_1.0.51-1.debian.tar.xz
 16987527e13235b8f088df7af61c69ee 69148 debug optional 
moon-buggy-dbgsym_1.0.51-1_amd64.deb
 a2aa0c5b3a8782fc6f431e70264558fb 9165 games optional 
moon-buggy_1.0.51-1_amd64.buildinfo
 462fc4e9eb1a5b76741c3571a80ef475 217492 games optional 
moon-buggy_1.0.51-1_amd64.deb

-BEGIN PGP SIGNATURE-

Bug#885797: [Pkg-matrix-maintainers] Bug#885797: revolt: please build-depend on libglib2.0-dev-bin

[Boris Pek]

Hi,

>> I don't think we have any
>> uploads for Revolt planned in the near future, so we can just let the
>> NMU go through.
>
> Thanks, I've rescheduled it to 0-day so this bug can go away sooner.
>
> The collab-maint repository declared in the source package doesn't seem
> to exist, so I haven't pushed my changes. Please apply the change to
> whatever VCS you use for the next upload.

Imported using `gbp import-dscs`:
https://salsa.debian.org/matrix-team/revolt/commits/master

Thanks.

-- 
Boris

Bug#874699: marked as done (node-evp-bytestokey: Please migrate to openssl1.1 in Buster)

[Debian Bug Tracking System]

Your message dated Sat, 30 Dec 2017 15:34:50 +
with message-id 
and subject line Bug#874699: fixed in node-evp-bytestokey 1.0.3-2
has caused the Debian Bug report #874699,
regarding node-evp-bytestokey: Please migrate to openssl1.1 in Buster
to be marked as done.

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

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


-- 
874699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874699
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-evp-bytestokey
Version: 1.0.3-1
Severity: important
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1-trans
Control: block 871056 by -1

Please migrate to libssl-dev in the Buster cycle.

Sebastian
--- End Message ---
--- Begin Message ---
Source: node-evp-bytestokey
Source-Version: 1.0.3-2

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

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

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

Debian distribution maintenance software
pp.
Jérémy Lal  (supplier of updated node-evp-bytestokey package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 30 Dec 2017 14:47:59 +0100
Source: node-evp-bytestokey
Binary: node-evp-bytestokey
Architecture: source
Version: 1.0.3-2
Distribution: experimental
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jérémy Lal 
Description:
 node-evp-bytestokey - secure key derivation algorithm in pure javascript
Closes: 874699
Changes:
 node-evp-bytestokey (1.0.3-2) experimental; urgency=medium
 .
   * Team upload
   * Build-Depends nodejs-dev >= 8, Closes: #874699
   * Build-Depends node-gyp
   * Section: javascript
Checksums-Sha1:
 f799bfdf3a141c19024e66edcbbcec42de7950e5 2476 node-evp-bytestokey_1.0.3-2.dsc
 d7140997ed8312118995cf6b856387edd775d0b0 3148 
node-evp-bytestokey_1.0.3-2.debian.tar.xz
 052177ba1a2d55f836879fc84afce8f01d1ffd54 8048 
node-evp-bytestokey_1.0.3-2_source.buildinfo
Checksums-Sha256:
 30f23e957b70a13a905d1a5da99fbca76746fd19c3727a48d71beee6823637f0 2476 
node-evp-bytestokey_1.0.3-2.dsc
 f66dab7f0a8baab78a2d9c2568f5cb2e0d795ef8a17b91ad13cbdd68b276d6d5 3148 
node-evp-bytestokey_1.0.3-2.debian.tar.xz
 03f2166c3ef527ad814c912a27a95e10ec4cf3dab3b623dd64fd331684b3a9b9 8048 
node-evp-bytestokey_1.0.3-2_source.buildinfo
Files:
 4f821a7bb9cbcd3192aa835d3f045bd4 2476 javascript optional 
node-evp-bytestokey_1.0.3-2.dsc
 712ea780cea4c48a88b071e2fae59cef 3148 javascript optional 
node-evp-bytestokey_1.0.3-2.debian.tar.xz
 415b8bdfda8b3c43ee0ec58e746cfd66 8048 javascript optional 
node-evp-bytestokey_1.0.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAlpHrbgSHGthcG91ZXJA
bWVsaXgub3JnAAoJEGYRwF7dOfN0ZMcQALMR6tJ0m+qvUj+e70sy+lFbY9DR3S10
oWFddkbCIKHsjAW4bjXgb0Y1I7KP1tJX3xb2gzS4U9rcthxO2uwPq574i/kpeVTX
BwK6AQcuTobo/JFR23RnYNGjS2uqGZdttg+Mus4DB38AvXApXifuAaPtPENivRix
ohXCLBZfvztEKBhexOxuDRvNcOK8+nyI6fH61ueH/ykzgcsPFnOOyTgWKE2Mi1E0
IxHUqPo2Umq5ZNyZT7IjyP9zMGwmWkcGZD6JXE8QpQ6Afugm4AV7IndET/1j2Pn0
plYGbZS9fP6GQ535oUt7tecqLuRakXC0QX3UeexIgG//R1/4KOsQPHyMCzm9txas
AG7rAXbXISphnij4rI9hsVXm9nn7eyxTJvT4GIvBDV925xO7CHMdVONSsFSvMVE/
TXbdwMdzNt+0RFuyTiDZMY0S0ZxVCNhrK9H5hAoZk2A1hpPyynl7/H7rRdAcKg1Q
pJ6C3laHRdG9zzLLmg/Zhm2iLLK8KWVuJpsEgm3+H8H9+tN21oOnOAUEICea/FyR
mDRU9K9SEbAt7+XcuvwYmsAaGNJg7e7u9/aRdXDIxlxRdjj/RecQuCRcu0IW2GgY
VKZJCA/xSxI548BzwOW7jqeFBonhwqzzrbAg4ol0k7LVDWRBdbdZxOkU40Pp4pV0
XX/av8FWJElP
=6b/U
-END PGP SIGNATURE End Message ---

Processed: severity of 885132 is serious

[Debian Bug Tracking System]

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

> severity 885132 serious
Bug #885132 [ejabberd] ejabberd 17.08 is incompatible with erlang-p1-xmpp 1.16
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: block 885132 with 883017

[Debian Bug Tracking System]

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

> block 885132 with 883017
Bug #885132 [ejabberd] ejabberd 17.08 is incompatible with erlang-p1-xmpp 1.16
885132 was not blocked by any bugs.
885132 was not blocking any bugs.
Added blocking bug(s) of 885132: 883017
> thanks
Stopping processing here.

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

Bug#809423: klibc: FTBFS on i386: Multiple definition of `socket'

[Sven Joachim]

On 2015-12-30 09:48 -0500, Daniel Schepler wrote:

> Source: klibc
> Version: 2.0.4-4
> Severity: serious
>
> From my pbuilder build log:
>
> ...
> usr/klibc/socketcalls/socket.o: In function `socket':
> /build/klibc-2.0.4/usr/klibc/socketcalls/socket.S:8: multiple definition of 
> `socket'

After the removal of
syscalls-override-detection-of-direct-socket-syscalls-on-i386-m68k-s390.patch
in commit 9d23e3d69 ("Drop patches no longer required after stretch
release") this happens again in 2.0.4-10. :-(

Cheers,
   Sven

Processed: reopening 809423

[Debian Bug Tracking System]

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

> unarchive 809423
Bug #809423 {Done: Ben Hutchings } [src:klibc] klibc: 
FTBFS on i386: Multiple definition of `socket'
Unarchived Bug 809423
> found 809423 2.0.4-10
Bug #809423 {Done: Ben Hutchings } [src:klibc] klibc: 
FTBFS on i386: Multiple definition of `socket'
Marked as found in versions klibc/2.0.4-10 and reopened.
> thanks
Stopping processing here.

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

Processed: found 884345 in 1:13.14.1~dfsg-2, fixed 884345 in 1:13.14.1~dfsg-2+deb9u3 ...

[Debian Bug Tracking System]

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

> found 884345 1:13.14.1~dfsg-2
Bug #884345 [src:asterisk] asterisk: CVE-2017-17664: Remote Crash Vulnerability 
in RTCP Stack
Ignoring request to alter found versions of bug #884345 to the same values 
previously set
> fixed 884345 1:13.14.1~dfsg-2+deb9u3
Bug #884345 [src:asterisk] asterisk: CVE-2017-17664: Remote Crash Vulnerability 
in RTCP Stack
Ignoring request to alter fixed versions of bug #884345 to the same values 
previously set
> found 881256 1:13.14.1~dfsg-2
Bug #881256 {Done: Bernhard Schmidt } [src:asterisk] 
asterisk: CVE-2017-16672: AST-2017-011: Memory/File Descriptor/RTP leak in 
pjsip session resource
Marked as found in versions asterisk/1:13.14.1~dfsg-2.
> fixed 881256 1:13.14.1~dfsg-2+deb9u3
Bug #881256 {Done: Bernhard Schmidt } [src:asterisk] 
asterisk: CVE-2017-16672: AST-2017-011: Memory/File Descriptor/RTP leak in 
pjsip session resource
Marked as fixed in versions asterisk/1:13.14.1~dfsg-2+deb9u3.
> found 881257 1:13.14.1~dfsg-2
Bug #881257 {Done: Bernhard Schmidt } [src:asterisk] 
asterisk: CVE-2017-16671: AST-2017-010: Buffer overflow in CDR's set user
Marked as found in versions asterisk/1:13.14.1~dfsg-2.
> fixed 881257 1:13.14.1~dfsg-2+deb9u3
Bug #881257 {Done: Bernhard Schmidt } [src:asterisk] 
asterisk: CVE-2017-16671: AST-2017-010: Buffer overflow in CDR's set user
Marked as fixed in versions asterisk/1:13.14.1~dfsg-2+deb9u3.
> thanks
Stopping processing here.

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

Processed (with 4 errors): found 884345 in 1:13.14.1~dfsg-2, fixed 884345 in 1:13.14.1~dfsg-2+deb9u3 ...

[Debian Bug Tracking System]

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

> found 884345 1:13.14.1~dfsg-2
Bug #884345 [src:asterisk] asterisk: CVE-2017-17664: Remote Crash Vulnerability 
in RTCP Stack
Marked as found in versions asterisk/1:13.14.1~dfsg-2.
> fixed 884345 1:13.14.1~dfsg-2+deb9u3
Bug #884345 [src:asterisk] asterisk: CVE-2017-17664: Remote Crash Vulnerability 
in RTCP Stack
Marked as fixed in versions asterisk/1:13.14.1~dfsg-2+deb9u3.
> found 881256 1:13.14.1~dfsg-2
Failed to add found on 881256: Not altering archived bugs; see unarchive.

> fixed 881256 1:13.14.1~dfsg-2+deb9u3
Failed to add fixed on 881256: Not altering archived bugs; see unarchive.

> found 881257 1:13.14.1~dfsg-2
Failed to add found on 881257: Not altering archived bugs; see unarchive.

> fixed 881257 1:13.14.1~dfsg-2+deb9u3
Failed to add fixed on 881257: Not altering archived bugs; see unarchive.

> thanks
Stopping processing here.

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

Processed: Re: geeqie build does not trap errors from make

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending fixed-upstream
Bug #883526 [src:geeqie] geeqie build does not trap errors from make
Added tag(s) fixed-upstream and pending.

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

Bug#883526: geeqie build does not trap errors from make

[Andreas Ronnquist]

Control: tags -1 + pending fixed-upstream

This has been fixed upstream:

https://github.com/BestImageViewer/geeqie/commit/fa8f4638ee9f443cbe4a048f93b585e7fd995f57

I know there's a new upstream version in the works, I'll upload that,
or a new patched version of 1.3 if the new upstream version isn't
released before the Debian removal.

-- Andreas Rönnquist
gus...@debian.org

Bug#838499: wsjt unusable du to numpy

[Yvan Brodier]

Hi ! 

Same bug here. 

yvan@madiran:~$ wsjt
Traceback (most recent call last):
File "/usr/share/wsjt/wsjt.py", line 17, in 
from Numeric import zeros
ImportError: No module named Numeric 

yvan@madiran:~$ strace wsjt
execve("/usr/bin/wsjt", ["wsjt"], 0x7ffed9407480 /* 52 vars */) = 0
brk(NULL) = 0x55a381df5000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=262916, ...}) = 0
mmap(NULL, 262916, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7ffbbe1af000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3,
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\200\6\2\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1705896, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0x7ffbbe1ad000
mmap(NULL, 3811680, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
0) = 0x7ffbbdc2b000
mprotect(0x7ffbbddc4000, 2097152, PROT_NONE) = 0
mmap(0x7ffbbdfc4000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x199000) = 0x7ffbbdfc4000
mmap(0x7ffbbdfca000, 14688, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7ffbbdfca000
close(3) = 0
arch_prctl(ARCH_SET_FS, 0x7ffbbe1ae4c0) = 0
mprotect(0x7ffbbdfc4000, 16384, PROT_READ) = 0
mprotect(0x55a381377000, 8192, PROT_READ) = 0
mprotect(0x7ffbbe1f, 4096, PROT_READ) = 0
munmap(0x7ffbbe1af000, 262916) = 0
getpid() = 2715
rt_sigaction(SIGCHLD, {sa_handler=0x55a38116def0, sa_mask=~[RTMIN RT_1],
sa_flags=SA_RESTORER, sa_restorer=0x7ffbbdc5eaf0}, NULL, 8) = 0
geteuid() = 1000
brk(NULL) = 0x55a381df5000
brk(0x55a381e16000) = 0x55a381e16000
getppid() = 2713
stat("/home/yvan", {st_mode=S_IFDIR|0755, st_size=24576, ...}) = 0
stat(".", {st_mode=S_IFDIR|0755, st_size=24576, ...}) = 0
open("/usr/bin/wsjt", O_RDONLY) = 3
fcntl(3, F_DUPFD, 10) = 10
close(3) = 0
fcntl(10, F_SETFD, FD_CLOEXEC) = 0
rt_sigaction(SIGINT, NULL, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0},
8) = 0
rt_sigaction(SIGINT, {sa_handler=0x55a38116def0, sa_mask=~[RTMIN RT_1],
sa_flags=SA_RESTORER, sa_restorer=0x7ffbbdc5eaf0}, NULL, 8) = 0
rt_sigaction(SIGQUIT, NULL, {sa_handler=SIG_DFL, sa_mask=[],
sa_flags=0}, 8) = 0
rt_sigaction(SIGQUIT, {sa_handler=SIG_DFL, sa_mask=~[RTMIN RT_1],
sa_flags=SA_RESTORER, sa_restorer=0x7ffbbdc5eaf0}, NULL, 8) = 0
rt_sigaction(SIGTERM, NULL, {sa_handler=SIG_DFL, sa_mask=[],
sa_flags=0}, 8) = 0
rt_sigaction(SIGTERM, {sa_handler=SIG_DFL, sa_mask=~[RTMIN RT_1],
sa_flags=SA_RESTORER, sa_restorer=0x7ffbbdc5eaf0}, NULL, 8) = 0
read(10, "#!/bin/sh\nset -e\n\n# WSJT expects"..., 8192) = 890
stat("/home/yvan/.wsjt", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
stat("/home/yvan/.wsjt/CALL3.TXT", {st_mode=S_IFREG|0644,
st_size=227273, ...}) = 0
stat("/home/yvan/.wsjt/TSKY.DAT", {st_mode=S_IFREG|0644, st_size=129600,
...}) = 0
stat("/home/yvan/.wsjt/wsjtrc", {st_mode=S_IFREG|0644, st_size=236,
...}) = 0
stat("/home/yvan/.wsjt/RxWav", {st_mode=S_IFDIR|0755, st_size=4096,
...}) = 0
stat("/home/yvan/.wsjt/wsjt.xbm", {st_mode=S_IFREG|0644, st_size=3276,
...}) = 0
chdir("/home/yvan/.wsjt") = 0
stat("/usr/local/bin/env", 0x7c006da0) = -1 ENOENT (No such file or
directory)
stat("/usr/bin/env", {st_mode=S_IFREG|0755, st_size=31424, ...}) = 0
clone(child_stack=NULL,
flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
child_tidptr=0x7ffbbe1ae790) = 2716
wait4(-1, Traceback (most recent call last):
File "/usr/share/wsjt/wsjt.py", line 17, in  
from Numeric import zeros 
ImportError: No module named Numeric 
[{WIFEXITED(s) && WEXITSTATUS(s) == 1}], 0, NULL) = 2716 
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=2716,
si_uid=1000, si_status=1, si_utime=9, si_stime=1} --- 
rt_sigreturn({mask=[]}) = 2716 
exit_group(1) = ? 
+++ exited with 1 +++ 

73 and HNY ! 

F1RAD

Bug#885797: marked as done (revolt: please build-depend on libglib2.0-dev-bin)

[Debian Bug Tracking System]

Your message dated Sat, 30 Dec 2017 11:49:53 +
with message-id 
and subject line Bug#885797: fixed in revolt 0.0+git20170627.3f5112b-2.1
has caused the Debian Bug report #885797,
regarding revolt: please build-depend on libglib2.0-dev-bin
to be marked as done.

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

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


-- 
885797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885797
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: revolt
Version: 0.0+git20170627.3f5112b-2
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)

In bug #885019, the GNOME maintainers were asked to move the
glib-compile-resources tool to a more appropriate package to fix
cross-compiling. glib-compile-resources is a development tool and is not
needed by typical non-developer users, so moving it to libglib2.0-dev-bin
seemed most appropriate.

For the majority of packages that use glib-compile-resources, this had no
practical effect, because libglib2.0-dev depends on both. However,
revolt is unusual in that it uses glib-compile-resources without
depending on libglib2.0-dev (because it isn't native code). Depending
on libglib2.0-bin was previously enough to get glib-compile-resources,
but now isn't enough, making revolt FTBFS.

This is easily fixed by changing the Build-Depends to pull in either
libglib2.0-dev-bin, or libglib2.0-dev. I'll do a delayed NMU with the
obvious change when I get a bug number; or if a maintainer would prefer
to take care of this, a suitable patch is attached.

Thanks,
smcv
>From 3e10087807b360cc3d6d2ae208f92c3b9f28e9e6 Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Fri, 29 Dec 2017 23:32:27 +
Subject: [PATCH] Build-depend on libglib2.0-dev-bin as well as libglib2.0-bin

glib-compile-resources moved from -bin to -dev-bin in version
2.54.2-5 to fix #885019 (Closes: #nn)
---
 debian/changelog | 9 +
 debian/control   | 2 +-
 2 files changed, 10 insertions(+), 1 deletion(-)

diff --git a/debian/changelog b/debian/changelog
index c277bb9..5673bc0 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+revolt (0.0+git20170627.3f5112b-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Build-depend on libglib2.0-dev-bin as well as libglib2.0-bin.
+glib-compile-resources moved from -bin to -dev-bin in version
+2.54.2-5 to fix #885019 (Closes: #nn)
+
+ -- Simon McVittie   Fri, 29 Dec 2017 23:30:30 +
+
 revolt (0.0+git20170627.3f5112b-2) unstable; urgency=medium
 
   * Depend on gir1.2-webkit2-4.0 instead of directly on libwebkit2gtk-4.0.
diff --git a/debian/control b/debian/control
index 9834670..8c5b0c8 100644
--- a/debian/control
+++ b/debian/control
@@ -3,7 +3,7 @@ Section: net
 Priority: optional
 Maintainer: Matrix Packaging Team 
 Uploaders: Hubert Chathi 
-Build-Depends: debhelper (>=9), libglib2.0-bin, python3:any | python3-all:any | python3-dev:any | python3-all-dev:any, python3-gi
+Build-Depends: debhelper (>=9), libglib2.0-bin, libglib2.0-dev-bin, python3:any | python3-all:any | python3-dev:any | python3-all-dev:any, python3-gi
 Standards-Version: 3.9.8
 Homepage: https://github.com/aperezdc/revolt
 Vcs-Git: git://anonscm.debian.org/collab-maint/revolt.git
-- 
2.15.1

--- End Message ---
--- Begin Message ---
Source: revolt
Source-Version: 0.0+git20170627.3f5112b-2.1

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

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

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated revolt package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 30 Dec 2017 00:49:08 +
Source: revolt
Binary: revolt
Architecture: source
Version: 0.0+git20170627.3f5112b-2.1
Distribution: unstable
Urgency: medium
Maintainer: Matrix Packaging Team 

Changed-By: Simon McVittie 
Description:
 

Bug#885797: revolt: please build-depend on libglib2.0-dev-bin

[Simon McVittie]

On Fri, 29 Dec 2017 at 21:31:51 -0500, Hubert Chathi wrote:
> I don't think we have any
> uploads for Revolt planned in the near future, so we can just let the
> NMU go through.

Thanks, I've rescheduled it to 0-day so this bug can go away sooner.

The collab-maint repository declared in the source package doesn't seem
to exist, so I haven't pushed my changes. Please apply the change to
whatever VCS you use for the next upload.

smcv

Processed: gksu, kdesu, etc dependencies not really needed

[Debian Bug Tracking System]

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

> tag 867561 + patch
Bug #867561 [hplip-gui] hplip-gui: Depending on gksu is not good
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#867561: gksu, kdesu, etc dependencies not really needed

[Pino Toscano]

tag 867561 + patch
thanks

Hi,

according to:
- base/password.py, __get_password_utils_ui
- installer/core_install.py, check_passwd_util
all the bits that use kdesu, kdesudo, gnomesu, and gksu are commented,
so the dependencies can be removed altogether.  Even because, looking
at them we have:
- gksu: deprecated, broken, #867236
- kdebase-bin & kdebase-runtime: transitional since Wheezy
  (oldoldstable)
- kde-runtime: it does not contain the "kdesu" binary in $PATH anymore
- kdesudo: deprecated, dropped, #875107
- ktsuss: dropped more than 6 years ago, #622270

Patch attached for this.

Thanks.
-- 
Pino Toscano--- a/debian/control
+++ b/debian/control
@@ -122,7 +122,6 @@ Description: HP Printers PostScript Desc
 Package: hplip-gui
 Architecture: all
 Depends: default-dbus-session-bus | dbus-session-bus,
- gksu | kdebase-bin (<< 4:4.4.0-1) | kde-runtime | kdebase-runtime | kdesudo | ktsuss,
  hplip (>= ${source:Version}),
  python3-dbus.mainloop.pyqt5,
  python3-pyqt5,


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

Bug#877161: marked as done (astroml FTBFS and Debci failure: IndexError: boolean index did not match indexed array along dimension 0; dimension is 2048 but corresponding boolean dimension is 2047)

[Debian Bug Tracking System]

Your message dated Sat, 30 Dec 2017 12:14:54 +0100
with message-id 
and subject line Closing fixed bug
has caused the Debian Bug report #877161,
regarding astroml FTBFS and Debci failure: IndexError: boolean index did not 
match indexed array along dimension 0; dimension is 2048 but corresponding 
boolean dimension is 2047
to be marked as done.

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

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


-- 
877161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877161
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: astroml
Version: 0.3-6
Severity: serious
Tags: buster sid

Some recent change in unstable makes astroml FTBFS and Debci failure:

https://ci.debian.net/packages/a/astroml/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/astroml.html

...
==
ERROR: astroML.tests.test_filters.test_wiener_filter_simple
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 
"/build/1st/astroml-0.3/.pybuild/pythonX.Y_2.7/build/astroML/tests/test_filters.py",
 line 27, in test_wiener_filter_simple
s = wiener_filter(t, h)
  File 
"/build/1st/astroml-0.3/.pybuild/pythonX.Y_2.7/build/astroML/filters.py", line 
186, in wiener_filter
width_guess = np.min(np.abs(f[PSD[1:] < np.mean(PSD[1:])]))
IndexError: boolean index did not match indexed array along dimension 0; 
dimension is 256 but corresponding boolean dimension is 255

==
ERROR: astroML.tests.test_filters.test_wienter_filter_spike
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 
"/build/1st/astroml-0.3/.pybuild/pythonX.Y_2.7/build/astroML/tests/test_filters.py",
 line 39, in test_wienter_filter_spike
h_smooth = wiener_filter(t, hN)
  File 
"/build/1st/astroml-0.3/.pybuild/pythonX.Y_2.7/build/astroML/filters.py", line 
186, in wiener_filter
width_guess = np.min(np.abs(f[PSD[1:] < np.mean(PSD[1:])]))
IndexError: boolean index did not match indexed array along dimension 0; 
dimension is 2048 but corresponding boolean dimension is 2047

--
Ran 214 tests in 5.467s

FAILED (errors=2)
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd 
/build/1st/astroml-0.3/.pybuild/pythonX.Y_2.7/build; python2.7 -m nose 
dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned 
exit code 13
debian/rules:9: recipe for target 'build' failed
make: *** [build] Error 25
--- End Message ---
--- Begin Message ---
Source: astroml
Source-Version: 0.3-7
Control: forwarded -1 https://github.com/astroML/astroML/issues/101

This is (probably) fixed in 0.3-7. However, I am not sure that the fix
is really correct, so I give the upstream URL as reference.

Cheers

Ole--- End Message ---

Bug#790184: marked as done (lxterminal: depends on vte which is deprecated)

[Debian Bug Tracking System]

Your message dated Sat, 30 Dec 2017 10:34:32 +
with message-id 
and subject line Bug#790184: fixed in lxterminal 0.3.1-2
has caused the Debian Bug report #790184,
regarding lxterminal: depends on vte which is deprecated
to be marked as done.

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

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


-- 
790184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790184
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lxterminal
Severity: important
Tags: sid stretch
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs vte

Hi,

lxterminal depends on python-vte / libvte9, which are deprecated in
favor of gir1.2-vte-2.91 / libvte-2.91-0. Thus we want to remove
src:vte from the archive. lxterminal should switch to the new vte
version.

Please try to do this before the Stretch release as we're going to
try to remove src:vte this cycle.

We'll bump this to serious when the list of rdeps is small and we're
getting ready to removing vte completely.

If you have any question don't hesitate to ask.

Emilio 
--- End Message ---
--- Begin Message ---
Source: lxterminal
Source-Version: 0.3.1-2

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

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

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

Debian distribution maintenance software
pp.
Yao Wei (魏銘廷)  (supplier of updated lxterminal package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 30 Dec 2017 10:21:49 +0100
Source: lxterminal
Binary: lxterminal
Architecture: source
Version: 0.3.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian LXDE Maintainers 

Changed-By: Yao Wei (魏銘廷) 
Description:
 lxterminal - LXDE terminal emulator
Closes: 790184 878301
Changes:
 lxterminal (0.3.1-2) unstable; urgency=medium
 .
   * Use libvte-2.91 of GTK+ 3.0. (Closes: #790184)
   * Fix login shell with -e in some cases. (Closes: #878301)
   * Bump Standards-Version to 4.1.3
Checksums-Sha1:
 78614f77e34ba4fdba9bf730e16eb13eba6b453f 2078 lxterminal_0.3.1-2.dsc
 a0582d43bcb2ae0d8cd35738e0d62e01cd1e3d1c 7260 lxterminal_0.3.1-2.debian.tar.xz
 922385526b6b86308cdfaa900768a1cb2582cb27 14723 
lxterminal_0.3.1-2_source.buildinfo
Checksums-Sha256:
 89e4fbc110869ab95285880345a0c0d2dc1cf107f36b2c72af445b651c05dc76 2078 
lxterminal_0.3.1-2.dsc
 a49fbfb76d25e77f78333add6549f57b2d0b93fc047661f033382d6e2b4bfa04 7260 
lxterminal_0.3.1-2.debian.tar.xz
 a40e1fd295a79bce7878ae18b98b25ab185aafd00977a7d603c9626e734e9286 14723 
lxterminal_0.3.1-2_source.buildinfo
Files:
 b4b8e853ad46dedd14d28d3809c0018d 2078 x11 optional lxterminal_0.3.1-2.dsc
 07f2528b2a72ed5e5713fc20b862c902 7260 x11 optional 
lxterminal_0.3.1-2.debian.tar.xz
 ea9c0b6d0fa4a3430fa1c2e20ce59449 14723 x11 optional 
lxterminal_0.3.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCAAsFiEE/tVDSEUoffJikxSJz7v84LdPGxQFAlpHZW8OHG13ZWlAbHhk
ZS5vcmcACgkQz7v84LdPGxTKuA/8D/y3Jtr5JMzzlvIicLu8ebiZFcTuwiJmw0mJ
8/zNMgsEEYNyOqZVA3r4Wp/sYetv7tDl5HZAY0A4S/3IXcVAIFfrjI1eVIabtINI
icFqpzsFLp/axKADKEsLshO5HwUNzgC7l6dBXaVpxXGgl5bZnkz+SRyiOotbjaEw
iMZj3fJU62wapb07hacZcuU7qmiydyLCE0+54Z0NjK13jIRekJLBo3T7/a3jwdOm
N4ejBRD0l3desZR93RQ7m1aZZepKlAqHlbJ6tMCH7QsPp97aZgqwULeTQPJfVMia
hA0+jSug3C4sWTYdC+hmlgew97pm1WPkknbMkPfQOba9AuJWNIh0RKO37f8EMm0v
A5dYKXdUR35s9Ksq6bGOQ79MM2qeBJRUetAsSC2BqSoYeDjH/ZN/3BuXr0w50vBg
FZRtuc2opiyaUfM0gypJPOlZYfF7xeXPvm8rAQsG1w/XB8VC/3brRJDjEbb1grXP
87O6cDi/3duUbs9Lzr7QRCq6U81tcq0JkQ73IqAF9L6zKafZXu/a4ZMIxbIXePln
9UbPhm4Ufbn1NVcPwDzgT36ClJk1inkTUThMxT4i0MQjTZ1Aer1WskE72/3Nm9N8
fUDohfO6kkbhFhe/wLl8cFnnOSv1NeOSIWzIpnn50RqL8pzNPQXn6ItRZPwPssGG
ADMxo0c=
=6KbS
-END PGP SIGNATURE End Message ---

Bug#790184: marked as done (lxterminal: depends on vte which is deprecated)

[Debian Bug Tracking System]

Your message dated Sat, 30 Dec 2017 10:34:26 +
with message-id 
and subject line Bug#790184: fixed in lxterminal 0.3.1-1
has caused the Debian Bug report #790184,
regarding lxterminal: depends on vte which is deprecated
to be marked as done.

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

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


-- 
790184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790184
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lxterminal
Severity: important
Tags: sid stretch
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs vte

Hi,

lxterminal depends on python-vte / libvte9, which are deprecated in
favor of gir1.2-vte-2.91 / libvte-2.91-0. Thus we want to remove
src:vte from the archive. lxterminal should switch to the new vte
version.

Please try to do this before the Stretch release as we're going to
try to remove src:vte this cycle.

We'll bump this to serious when the list of rdeps is small and we're
getting ready to removing vte completely.

If you have any question don't hesitate to ask.

Emilio 
--- End Message ---
--- Begin Message ---
Source: lxterminal
Source-Version: 0.3.1-1

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

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

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

Debian distribution maintenance software
pp.
Yao Wei (魏銘廷)  (supplier of updated lxterminal package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 30 Dec 2017 11:15:41 +0100
Source: lxterminal
Binary: lxterminal
Architecture: source
Version: 0.3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian LXDE Maintainers 

Changed-By: Yao Wei (魏銘廷) 
Description:
 lxterminal - LXDE terminal emulator
Closes: 790184 878301
Changes:
 lxterminal (0.3.1-1) unstable; urgency=medium
 .
   * Merge upstream version to 0.3.1:
 - Changing keyboard shortcuts can be achieved by inputting key chords,
   rather than manual input.
   * Bump Standards-Version to 4.1.3:
 - Registration as an /usr/bin/x-terminal-emulator alternative now has
   priority of 20 instead of 40, as stated in Debian Policy §11.8.3.
   * Use debhelper 10.
   * Remove patches included in new upstream release.
   * Bump debian/watch version to 4.
   * Clean up debian/rules to use debhelper defaults.
   * Remove unused build dependency autotools-dev.
   * Remove debian/source/lintian-overrides as the supressed warning does not
 exist.
   * Use libvte-2.91 of GTK+ 3.0. (Closes: #790184)
   * Fix login shell with -e in some cases. (Closes: #878301)
Checksums-Sha1:
 db0a653a5bc09e80f8b658e8b0fd5d829961a4a3 2078 lxterminal_0.3.1-1.dsc
 51554be19cbe4ebbc8e3710935fa54c31338fabf 197628 lxterminal_0.3.1.orig.tar.xz
 af2cb7c6ede35e9445fcddaa6201f38a534f0767 7252 lxterminal_0.3.1-1.debian.tar.xz
 135c7003fe93d9a404ff97ffe6439950ceb3d01e 14723 
lxterminal_0.3.1-1_source.buildinfo
Checksums-Sha256:
 98adec331d5af1cc9cddbc92c5f024affe16223c473168ff8ab5ef7d6db15166 2078 
lxterminal_0.3.1-1.dsc
 cd8df387c2dd40e03b48caacf700820f9421b421954a0ed56395f505411d2c4b 197628 
lxterminal_0.3.1.orig.tar.xz
 042453e490a3e1866b6d39c4793904864d1ff0f48d45df6a19530e9b08329ca7 7252 
lxterminal_0.3.1-1.debian.tar.xz
 708318db8b8977b356b230efa5db640a2600cac097747daf7961d86a033fa65e 14723 
lxterminal_0.3.1-1_source.buildinfo
Files:
 6cb235a222bc988c9c3f175f7e92c923 2078 x11 optional lxterminal_0.3.1-1.dsc
 91febe1ec15297844333cb70f237b4b7 197628 x11 optional 
lxterminal_0.3.1.orig.tar.xz
 baec443cba18fba304d8983750cb 7252 x11 optional 
lxterminal_0.3.1-1.debian.tar.xz
 bc9ddcf27be7cb73cbbc5908cb17e4b0 14723 x11 optional 
lxterminal_0.3.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCAAsFiEE/tVDSEUoffJikxSJz7v84LdPGxQFAlpHZ88OHG13ZWlAbHhk
ZS5vcmcACgkQz7v84LdPGxTNwQ/+PU8rtWghCXyOFwLdRNcUwfjj1oNfcg6TkbyF
SRaRRWteIbQxPfZ16lZ4Gi7QX40LBloJGbSDKmNcz4N17vAfZETrk9FKCJUOFf4y
lYcQN4HuPqwbX0ugrpNV1oozBrx9HIKZkZQYgAm106RKO2PnJBfGLy5cs+OCcGVA
ThrwthDYHQ3QB+qnswqNtfm8E7mzC5FfEILGJsy9Rpx1sZlOZy+kBL66PGniOwqa

Processed: tagging 876242

[Debian Bug Tracking System]

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

> tags 876242 + fixed-upstream
Bug #876242 [src:exiv2] exiv2: CVE-2017-12957
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Processed (with 1 error): your mail

[Debian Bug Tracking System]

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

> forwarded 876242 https://github.com/Exiv2/exiv2/issues/60
Bug #876242 [src:exiv2] exiv2: CVE-2017-12957
Ignoring request to change the forwarded-to-address of bug#876242 to the same 
value
> tags fixed-upstream
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.

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

Processed: tagging 859789

[Debian Bug Tracking System]

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

> tags 859789 + pending
Bug #859789 [webcit] webcit: Please migrate to openssl1.1 in Buster
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 884204

[Debian Bug Tracking System]

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

> tags 884204 + pending
Bug #884204 [src:webcit] webcit FTBFS with libical3
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#876242: exiv2: CVE-2017-12957

[Simon Frei]

This has been fixed and and also backported to 0.26 upstream:
https://github.com/Exiv2/exiv2/issues/60

forwarded 876242 https://github.com/Exiv2/exiv2/issues/60
tags fixed-upstream
thanks

Processed (with 3 errors): Re: exiv2: CVE-2017-12957

[Debian Bug Tracking System]

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

> This has been fixed and and also backported to 0.26 upstream:
Unknown command or malformed arguments to command.
> https://github.com/Exiv2/exiv2/issues/60
Unknown command or malformed arguments to command.
> forwarded 876242 https://github.com/Exiv2/exiv2/issues/60
Bug #876242 [src:exiv2] exiv2: CVE-2017-12957
Set Bug forwarded-to-address to 'https://github.com/Exiv2/exiv2/issues/60'.
> tags fixed-upstream
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.

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

Bug#885835: awstats: CVE-2017-1000501: path traversals in config and migrate parameter

[Salvatore Bonaccorso]

Source: awstats
Version: 7.6+dfsg-1
Severity: grave
Tags: patch security upstream

Hi,

the following vulnerability was published for awstats.

CVE-2017-1000501[0]:
Path traversal flaws

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-2017-1000501
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000501
[1] http://www.openwall.com/lists/oss-security/2017/12/29/1
[2] 
https://github.com/eldy/awstats/commit/cf219843a74c951bf5986f3a7fffa3dcf99c3899
[3] 
https://github.com/eldy/awstats/commit/06c0ab29c1e5059d9e0279c6b64d573d619e1651

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#885459: telegram-desktop: FTCBFS on all architectures

[Коля Гурьев]

Hello,

27.12.2017 15:16, Boyuan Yang пишет:
> Package telegram-desktop FTCBFS on all architecture according to buildd
> logs[1].
> 
> There are all kinds of reasons about build failures across different
> architectures, including cc1plus internal compiler error, timeout, vmem
> exhaustion, etc.
> 
> Please investigate into this issue. I'm not sure what we can do, perhaps
> the best plan is to force non-parallel compilation (instead of make -j4
> or whatsoever on buildds).

I already found a fix[1] for memory exhaustion by GCC. If we look at a
file where the RPL_CONSUMER_TYPE_ERASED_ALWAYS macro is used[2], we
discover that the replacement of the auto keyword with more specific
type solves the problem.

But unfortunately there is another issue with linking on all
architectures except for amd64 and i386. Once a solution is found, I'll
prepare a new version of the package.

That's example of the error:

obj.target/liblinux_glibc_wraps.a(linux_glibc_wraps_64.o): In
function `__wrap_clock_gettime':

./obj-powerpc64le-linux-gnu/./Telegram/SourceFiles/platform/linux/linux_glibc_wraps_64.c:27:
undefined reference to `clock_gettime@GLIBC_2.2.5'
/usr/bin/ld: Telegram: No symbol version section for versioned
symbol `clock_gettime@GLIBC_2.2.5'
/usr/bin/ld: final link failed: Nonrepresentable section on output
collect2: error: ld returned 1 exit status

I don't think that non-parallel build let us avoid the errors.

 [1]:
https://anonscm.debian.org/git/collab-maint/telegram-desktop.git/commit/?id=4dc4aadc8497a996f91d75fa7d8b64884cf8b54c
 [2]:
https://anonscm.debian.org/git/collab-maint/telegram-desktop.git/tree/Telegram/SourceFiles/rpl/consumer.h?id=4dc4aadc8497a996f91d75fa7d8b64884cf8b54c#n629