Bug#862068: 9wm: inactive window border color

[Ricardo Fabian Peliquero]

Package: 9wm
Version: 1.3.9-1
Severity: normal

Dear Maintainer,

Setting inactive window border color to black falls back to default (white). 
Other colors, however, do work as expected.

Kindest regards,

Ricardo

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

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

Versions of packages 9wm depends on:
ii  libc6 2.24-10
ii  libx11-6  2:1.6.4-3
ii  libxext6  2:1.3.3-1+b2

9wm recommends no packages.

Versions of packages 9wm suggests:
ii  9menu  1.9-1+b1

-- no debconf information

Bug#861792: ITP: lr -- list files, recursively

[Alexander Wirt]

On Sun, 07 May 2017, Nicolas Braud-Santoni wrote:

> On Thu, May 04, 2017 at 08:53:27AM +0200, Alexander Wirt wrote:
> > On Thu, 04 May 2017, Nicolas Braud-Santoni wrote:
> > > 
> > > * Package name: lr
> > >   Version : 0.4
> >
> > Please don't (and this counts for your xr ITP too) add new two-letter 
> > binaries. 
> > This will just get everyone into trouble. 
> 
> What would be the rationale for this?
There are not enough two letter names for everyone. Therefore it is preferred
not to polute that namespace. 

Alex

Bug#861198: Shutting down public FTP services

[Vagrant Cascadian]

On 2017-04-28, Vagrant Cascadian  wrote:
> On 2017-04-28, Vagrant Cascadian wrote:
>> On 2017-04-28, Vagrant Cascadian wrote:
>>> On 2017-04-28, Enrico Zini wrote:
 Would you like me to try and provide a version which uses urlretrieve?
>>>
>>> All these ideas sound good to me, so please take a shot at it!
>>
>> Actually, being able to verify the checksums instead of relying on
>> timestamps got me excited enough to try this myself...
>
> And pushed to git, review appreciated.

Any chance you could review the urllib implementation that is in git
soonish? :)

In particular:

1faddb9cfe4992c36bca7e502f5190e96de74f77 Explicitly set http_proxy in the 
environment.
b164d54b912a8d702576c191a821ec2f374642cf Only re-download files if known 
checksums do not match.
6717a008549cd792a4c08d7c21d09cbd8b82a67a Switch to urllib.

I suspect my exception handling is a bit over-broad and there are better
ways to handle it, at the very least.


Thanks for all your help on this!


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#861631: libinput10: Imposible to increase TrackPoint speed

[Charles Plessy]

Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=100965

Le Wed, May 03, 2017 at 11:00:36AM +0200, Julien Cristau a écrit :
> 
> please file this upstream at
> https://bugs.freedesktop.org/enter_bug.cgi?component=Input%2Flibinput=xorg
> including your full X log and details about the hardware.  Let us know
> the bug number for tracking.

Hi Julien,

submitted, thank you.

-- 
Charles

Bug#856487: libsbc1: compiling with gcc > 4.9 causes stack corruption

[Nobuhiro Iwamatsu]

Hi, all.

Thanks for your comments.

>On Mon, Apr 17, 2017 at 05:02:32PM +0100, Paul Brook wrote:
>> Package: libsbc1
>> Version: 1.3-1+b2
>> Followup-For: Bug #856487
>>
>> Not a stack corruption.
>>
>> This is miscompilation of sbc_analyze_4b_8s_armv6.  gcc appears to look
>> into the asm function and decides that it does not clobber r3 (which the
>> normal ARM ABI says is call clobbered).  The last out += out_stride ends
>> up incrementing the pointer by an arbitrary amount.
>>
>> The attached patch works around the bug.
>
>Unfortunately this is not correct since extended asm is not allowed in
>naked functions.
>
>Short-term I'd suggest to use the attached patch, that disables the
>ARMv6 asm implementation and uses the C implementation instead.
>
>> I'm not entirely sure whether this is a gcc bug or not, but at best it's
>> surprising behavior from gcc.  I've attached a reduced testcase for the 
>> toolchain
>> folks to argue over (compile with gcc -O2, tested with gcc 6.3.0-2 from
>> sid).
>
>This is either a bug in gcc or insufficient documentation in gcc.
>

I see.
I will fix using --enable-high-precision of configure option.

>Could you (or did you already) submit that to the gcc bugzilla?

OK, I will report this to GCC.
>
>> Paul
>>...
>
>Thanks
>Adrian


Best regards,
  Nobuhiro

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6

Bug#854475: postfix: systemd needs postfix@.service to have "After=network.target"

[Scott Kitterman]

On Sunday, May 07, 2017 10:55:58 PM Bernhard Schmidt wrote:
> On Sat, Apr 15, 2017 at 11:42:37PM +0200, Marcus Jodorf wrote:
> 
> Hi,
> 
> is there anything I can do to get this fixed for Stretch? I can
> pretty reliably reproduce this issue with all my upgraded Stretch
> systems, neither of them can send mails after a reboot until Postfix is
> getting restarted
> 
> An After=network.target should be pretty low-risk even this late in the
> release cycle and should fix this issue.
> 
> Best Regards,
> Bernhard

postfix.service has After=network.target.  Why isn't that enough (I have not 
had a lot of time to investigate this, but I have not given on up getting a 
fix into stretch)?

Scott K

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

Bug#862066: cyrus-common: cyrmaster does not start

[MIZUHARA Bun]

Package: cyrus-common
Version: 2.4.17+nocaldav-0+deb8u2
Severity: normal

Dear Maintainer,

I have upgraded my servers from Debian 7.11 to 8.8, involving replacement of
cyrus-2.2 with cyrus-2.4.
After rebooting, all servers failed to start cyrmaster daemon.

On one server, cyrmaster could be started successfully with this command:

# /etc/init.d/cyrus-imapd start

And this command seems to be effective in starting cyrmaster on reboot:

# systemctl enable cyrus-imapd.service

But on the other server, '/etc/init.d/cyrus-imapd start' did not work.
In /var/log/daemon.log, I found this line:

cyrus[1383]: /usr/lib/cyrus/bin/init-helper: You are missing a 
dpkg-statoverride on /var/run/cyrus.  Add it.

Therefore I performed the following command, referring to the output from
'dpkg-statoverride --list' executed on the other server:

# dpkg-statoverride --add cyrus mail 755 /var/run/cyrus

Then tried to start cyrmaster again, and got this message in daemon.log:

cyrus[1760]: /usr/lib/cyrus/bin/init-helper: You are missing a 
dpkg-statoverride on /var/run/cyrus/socket.  Add it.

Again I performed the command:

# dpkg-statoverride --add cyrus lmtp 750 /var/run/cyrus/socket

Finally, I was able to start cyrmaster.

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

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

Versions of packages cyrus-common depends on:
ii  adduser 3.113+nmu3
ii  db-upgrade-util 5.3.0
ii  db-util 5.3.0
ii  debconf [debconf-2.0]   1.5.56
ii  dpkg1.17.27
ii  gawk1:4.1.1+dfsg-1
ii  libc6   2.19-18+deb8u9
ii  libcomerr2  1.42.12-2+b1
ii  libdb5.35.3.28-9
ii  libkrb5-3   1.12.1+dfsg-19+deb8u2
ii  libldap-2.4-2   2.4.40+dfsg-1+deb8u2
ii  libsasl2-2  2.1.26.dfsg1-13+deb8u1
ii  libsasl2-modules2.1.26.dfsg1-13+deb8u1
ii  libsnmp30   5.7.2.1+dfsg-1
ii  libssl1.0.0 1.0.1t-1+deb8u6
ii  libwrap07.6.q-25
ii  libzephyr4  3.1.2-1
ii  netbase 5.3
ii  perl5.20.2-3+deb8u6
ii  postfix [mail-transport-agent]  2.11.3-1+deb8u2
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages cyrus-common recommends:
ii  cyrus-admin  2.4.17+nocaldav-0+deb8u2
ii  cyrus-imapd  2.4.17+nocaldav-0+deb8u2

Versions of packages cyrus-common suggests:
ii  apt-listchanges2.85.13+nmu1
ii  cyrus-admin2.4.17+nocaldav-0+deb8u2
pn  cyrus-clients  
ii  cyrus-doc  2.4.17+nocaldav-0+deb8u2
ii  cyrus-imapd2.4.17+nocaldav-0+deb8u2
pn  cyrus-murder   
pn  cyrus-nntpd
pn  cyrus-pop3d
pn  cyrus-replication  
ii  sasl2-bin  2.1.26.dfsg1-13+deb8u1

-- Configuration Files:
/etc/cyrus.conf changed:
START {
# do not delete this entry!
recover cmd="/usr/sbin/cyrus ctl_cyrusdb -r"
  
# this is only necessary if idlemethod is set to "idled" in imapd.conf
#idled  cmd="idled"
# this is useful on backend nodes of a Murder cluster
# it causes the backend to syncronize its mailbox list with
# the mupdate master upon startup
#mupdatepush   cmd="/usr/sbin/cyrus ctl_mboxlist -m"
# this is recommended if using duplicate delivery suppression
delprunecmd="/usr/sbin/cyrus expire -E 3"
# this is recommended if caching TLS sessions
tlsprunecmd="/usr/sbin/cyrus tls_prune"
}
SERVICES {
# --- Normal cyrus spool, or Murder backends ---
# add or remove based on preferences
imapcmd="imapd -U 30" listen="imap" prefork=0 maxchild=100
#imaps  cmd="imapd -s -U 30" listen="imaps" prefork=0 
maxchild=100
pop3cmd="pop3d -U 30" listen="pop3" prefork=0 maxchild=50
#pop3s  cmd="pop3d -s -U 30" listen="pop3s" prefork=0 
maxchild=50
nntpcmd="nntpd -U 30" listen="nntp" prefork=0 maxchild=100
#nntps  cmd="nntpd -s -U 30" listen="nntps" prefork=0 
maxchild=100
httpcmd="httpd -U 30" listen="8008" prefork=0 maxchild=100
#https  cmd="httpd -s -U 30" listen="8443" prefork=0 
maxchild=100
# At least one form of LMTP is required for delivery
# (you must keep the Unix socket name in sync with imap.conf)
#lmtp   cmd="lmtpd" listen="localhost:lmtp" prefork=0 
maxchild=20
lmtpunixcmd="lmtpd" listen="/var/run/cyrus/socket/lmtp" 
prefork=0 maxchild=20
# 

Bug#862065: starplot: does not start due to invalid pointer error

[Fred Barclay]

Package: starplot
Version: 0.95.5-8.2
Severity: important

Dear Maintainer,

Starplot doesn't start and returns `*** Error in `starplot': free(): invalid
pointer: 0x55f5759e60d0 ***` when started from terminal.

However, `valgrind starplot` allows starplot to run normally.

This is a completely fresh installation of starplot on a computer that's never
had starplot installed before (so no leftover data in ${HOME}).



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

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

Versions of packages starplot depends on:
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-10
ii  libcairo21.14.8-1
ii  libfontconfig1   2.11.0-6.7+b1
ii  libfreetype6 2.6.3-3.2
ii  libgcc1  1:6.3.0-16
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.50.3-2
ii  libgtk2.0-0  2.24.31-2
ii  libpango-1.0-0   1.40.5-1
ii  libpangocairo-1.0-0  1.40.5-1
ii  libpangoft2-1.0-01.40.5-1
ii  libstdc++6   6.3.0-16

Versions of packages starplot recommends:
ii  stardata-common  0.8+b1

Versions of packages starplot suggests:
pn  gliese  
pn  yale

-- no debconf information

Bug#862063: more detail on results from edited file

[Matt Beary]

As a clarification - editing the file allowed it to be loaded into
transmission successfully.  The download could not continue and logged the
bug below.  If I'm reading the standard correctly, the no-longer-matching
hash of the info dictionary caused this.

MiniMetro-gamma19a-linux.tar.gz Tracker error: "unregistered torrent"
(torrent.c:581)

Bug#862056: screen-message: please invert the default colours

[Joachim Breitner]

Dear Chris,

Am Sonntag, den 07.05.2017, 22:47 +0100 schrieb Chris Lamb:
> Please invert the default colours for screen-message; a large white
> background is not very "hacker friendly" and almost physically
> painful to experience very late into the early hours…


the choice of default colors is obvious a contestable one, and there is
no single right answer. I prefer it this way (I mostly use sm during
talks, where the background tends to be bright). I think I’ll play the
“I wrote this, so I make the call” and also the “Changing a default
will upset a few people” card and not apply the patch.

I recommend you to use the bash alias feature to make sm behave the way
you prefer – just like people have been configuring their unix tools
for decades.

Greetings,
Joachim

-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

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

Bug#862064: unblock: haskell-glut/2.7.0.10-4

[Joachim Breitner]

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

Please unblock package haskell-glut, to fix a rc problem with raincat:


diff -Nru haskell-glut-2.7.0.10/debian/changelog 
haskell-glut-2.7.0.10/debian/changelog
--- haskell-glut-2.7.0.10/debian/changelog  2016-10-27 18:33:52.0 
-0400
+++ haskell-glut-2.7.0.10/debian/changelog  2017-05-06 16:56:46.0 
-0400
@@ -1,3 +1,10 @@
+haskell-glut (2.7.0.10-4) unstable; urgency=medium
+
+  * Use extra-libraries: GLUT so that this properly links against libglut
+(Closes: 861976)
+
+ -- Joachim Breitner   Sat, 06 May 2017 16:56:46 -0400
+
 haskell-glut (2.7.0.10-3) unstable; urgency=medium
 
   * Upload to unstable as part of GHC 8 transition.
diff -Nru haskell-glut-2.7.0.10/debian/patches/series 
haskell-glut-2.7.0.10/debian/patches/series
--- haskell-glut-2.7.0.10/debian/patches/series 1969-12-31 19:00:00.0 
-0500
+++ haskell-glut-2.7.0.10/debian/patches/series 2017-05-06 16:54:24.0 
-0400
@@ -0,0 +1 @@
+use-extra-libraries
diff -Nru haskell-glut-2.7.0.10/debian/patches/use-extra-libraries 
haskell-glut-2.7.0.10/debian/patches/use-extra-libraries
--- haskell-glut-2.7.0.10/debian/patches/use-extra-libraries1969-12-31 
19:00:00.0 -0500
+++ haskell-glut-2.7.0.10/debian/patches/use-extra-libraries2017-05-06 
16:56:44.0 -0400
@@ -0,0 +1,25 @@
+Index: haskell-glut/GLUT.cabal
+===
+--- haskell-glut.orig/GLUT.cabal   2016-05-12 12:47:38.0 -0400
 haskell-glut/GLUT.cabal2017-05-06 16:55:16.164611101 -0400
+@@ -103,6 +103,7 @@
+   else
+ cpp-options: "-DCALLCONV=ccall"
+ cc-options: "-DUSE_DLSYM"
++extra-libraries: glut
+ 
+ executable BOGLGP01-OnYourOwn1
+   if !flag(BuildExamples)
+Index: haskell-glut/cbits/HsGLUT.c
+===
+--- haskell-glut.orig/cbits/HsGLUT.c   2016-05-12 12:47:38.0 -0400
 haskell-glut/cbits/HsGLUT.c2017-05-06 16:56:30.898637798 -0400
+@@ -66,7 +66,7 @@
+   handle = dlopen("/System/Library/Frameworks/GLUT.framework/GLUT", 
RTLD_LAZY | RTLD_GLOBAL);
+ }
+ #else
+-handle = dlopen("libglut.so", RTLD_LAZY | RTLD_GLOBAL);
++handle = dlopen(NULL, RTLD_LAZY | RTLD_GLOBAL);
+ #endif
+   }
+ 

unblock haskell-glut/2.7.0.10-4

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

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

Bug#861707: unblock: mysql-connector-java/5.1.42-1

[Emmanuel Bourg]

Control: tags -1 - moreinfo

Le 7/05/2017 à 19:02, Niels Thykier a écrit :

> Ack, please go ahead and remove the moreinfo tag once the upload has
> been accepted.

Thank you, uploaded.

Bug#819657: Additional information about our submission

[兰州大学开源社区 LZUOSS]

Hi,

> Is there a reason why you use gmail.com instead of a proper e-mail
> address of your organization?

Our mailbox with lzu.edu.cn suffix is not so stable. There are usually about
several hours' delay while receiving an email(some mails might even be dropped).
So considering that we need to contact with others instantly and
stably, we choose to
use Gmail as our main email address. If you are wondering if we are actually the
controller of mirror.lzu.edu.cn ,  I guess you may send us with a PGP signed or
encrypted message, then we can put it on our server so you can verify it.

> Please ping as again after you did this change.  We are reluctant to add
> mirrors without, as most are not able to get the mirror process right.

We have tested the ftpsync in a recent sync process. It seems works
fine. You can verify it
with our trace file:
http://mirror.lzu.edu.cn/debian/project/trace/mirror.lzu.edu.cn

Anyway, thanks for your help. We are grateful to what you made to
Debian community.

Best regards,
Mirror Maintenance Team@LZUOSS

2017-05-07 23:45 GMT+08:00 Bastian Blank :
> Hi
>
> On Sun, May 07, 2017 at 05:37:31PM +0800, 兰州大学开源社区 LZUOSS wrote:
>> We are so sorry about not catching the latest response made by you. We
>> really didn't receive any mail about the response. For this we must express
>> our sincere apologies.
>
> Is there a reason why you use gmail.com instead of a proper e-mail
> address of your organization?
>
>> As you mentioned, we are now still using our own sync script to finish the
>> mirror sync, but we will turn to the official provided ftpsync soon(in less
>> than one month).
>
> Please ping as again after you did this change.  We are reluctant to add
> mirrors without, as most are not able to get the mirror process right.
>
> Regards,
> Bastian
>
> --
> Dammit Jim, I'm an actor, not a doctor.



-- 
兰州大学开源社区
Lanzhou University Open Source Society
https://oss.lzu.edu.cn

Bug#862063: transmission: info/name entry with forward-slash fails to parse - Invalid metadata entry "path"

[Matt Beary]

Package: transmission-daemon
Version: 2.92-2
Severity: normal
File: transmission

Dear Maintainer,

While attempting to download a purchase from Humble Bundle, which provides 
.torrent download options, I stumbled across an issue triggered by the torrent 
file for MiniMetro.  transmission-daemon's directory watch feature failed to 
load the file with a metadata error.  Attempting to use transmission-show 
resulted in the same error:

[2017-05-07 19:40:24.417] dinosaurpoloclub/MiniMetro-gamma19a-linux.tar.gz: 
Invalid metadata entry "path"
Error parsing .torrent file "MiniMetro-gamma19a-linux.tar.gz.torrent"

I was able to open the file using the Python library "bencode", and saw that 
there was no "path" metadata entry, and that the torrent was for a single file 
with the info/name entry "dinosaurpoloclub/MiniMetro-gamma19a-linux.tar.gz".

Removing "dinosaurpoloclub/" from that entry was enough to allow the torrent to 
work.  I did a bit of searching, and it looks like having a full path in the 
info/name entry is valid (although I've never seen it before, bep 3 doesn't 
seem to prohibit it)

It may also be worth noting that the "dinosaurpoloclub" folder did not exist on 
my computer


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

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

Versions of packages transmission-daemon depends on:
ii  adduser  3.115
ii  init-system-helpers  1.48
ii  libc62.24-10
ii  libcurl3-gnutls  7.52.1-5
ii  libevent-2.0-5   2.0.21-stable-3
ii  libminiupnpc10   1.9.20140610-2.1
ii  libnatpmp1   20110808-4+b1
ii  libssl1.11.1.0e-1
ii  libsystemd0  232-22
ii  lsb-base 9.20161125
ii  transmission-common  2.92-2
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages transmission-daemon recommends:
ii  transmission-cli  2.92-2

transmission-daemon suggests no packages.

-- Configuration Files:
/etc/transmission-daemon/settings.json [Errno 13] Permission denied: 
'/etc/transmission-daemon/settings.json'

-- no debconf information

Bug#862062: FTBFS on sparc64 due to SIGBUS in test suite

[James Clarke]

Source: systemd
Version: 233-6
Tags: upstream patch
Forwarded: https://github.com/systemd/systemd/pull/5622
User: debian-sp...@lists.debian.org
Usertags: sparc64
X-Debbugs-Cc: debian-sp...@lists.debian.org

Hi,
Currently systemd FTBFS in experimental on sparc64 due to
journal-importer performing an unaligned access when running the test
suite. If you upload another version between now and 234, could you
please include the patch accepted upstream?

Regards,
James

Bug#712612: gcr: diff for NMU version 3.20.0-5.1

[Michael Biebl]

Am 06.05.2017 um 10:43 schrieb Christoph Biedl:
> Michael Biebl wrote...
> 
>> Am 06.05.2017 um 00:00 schrieb Christoph Biedl:
> 
>>> I've prepared an NMU for gcr (versioned as 3.20.0-5.1), upload to
>>> DELAYED/5 will follow in a few hours. Please feel free to tell me if I
>>> should delay it longer.
>>>
>>
>> Seems to be missing doc/
> 
> That's not obvious for me.

Well, Ansgar mentioned this:

> there are two files under a BSD license in build/valgrind/*. In
addition the
> documentation has its own license in docs/reference/COPYING.

He was referring to that file afaics:
https://git.gnome.org/browse/gcr/tree/docs/reference/COPYING



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



signature.asc
Description: OpenPGP digital signature

Bug#858250: Bug#861953: unblock: runc/0.1.1+dfsg1-3

[Roger Shimizu]

[ CC: original Bug #858250 ]

On Sun, 07 May 2017 21:02:00 +
Niels Thykier  wrote:

> Roger Shimizu:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: unblock
> > 
> > Please unblock package runc
> > 
> > Since there's already a newer package in unstable, I guess it's
> > necessary to use "testing-proposed-updates"
> > 
> > Here I'm fixing #858250, which is FTBFS RC issue.
> 
> 
> Hi Roger,
> 
> Thanks for working on fixing #858250 for stretch. :)
> 
> Before there is an upload to testing-proposed-updates, the original bug
> should be resolved in unstable first.  That means that #858250 should be
> closed in unstable first.
> 
> On a related note, the Debian Bug Tracker can determine which suites are
> affected by looking at found + fixed versions, so there is no need to
> have two bugs for this (which is why I have merged #861966 back into
> #858250).

#858250 is not easy to fix for unstable, since there's already newer version
runc/1.0.0~rc2+git20161109.131.5137186-2, with newer version of Build-Depends
golang-github-opencontainers-specs/1.0.0~rc2+git20160926.38.1c7c27d-1.

As stated by #858250, runc is FTBFS with
golang-github-opencontainers-specs/1.0.0~rc2+git20160926.38.1c7c27d-1.
So my original plan was just patch d/control to limit the version of
Build-Depends.

Since you say it should fix unstable first, then stretch or t-p-u,
now I think we may just leave runc/0.1.1+dfsg1-2 (current in stretch)
as it is in stretch. Because it builds OK (without FTBFS) for stretch.
The #858250 FTBFS only occurs on unstable.

What's your opinion?

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


pgpzNEbGNWjfS.pgp
Description: PGP signature

Bug#861957: closed by Joachim Breitner <nome...@debian.org> (Re: Bug#861976: libghc-glut-dev: attempts to load libglut.so instead of libglut.so.3)

[James Cowgill]

Hi,

On 07/05/17 19:38, Adrian Bunk wrote:
> Control: reassign -1 libghc-glut-dev 2.7.0.10-3
> Control: fixed -1 2.7.0.10-4
> Control: affects -1 src:raincat
> 
> On Sun, May 07, 2017 at 01:51:04PM +, Debian Bug Tracking System wrote:
>> ...
>> With haskell-glut 2.7.0.10-4 this should be fixed in unstable.
> 
> I am reassigning it so that version tracking covers this.
> 
> I'd guess raincat might additionally need a binNMU?

It does - filed as #862061.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#862061: nmu: raincat_1.1.1.2-3

[James Cowgill]

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

Hi,

raincat needs binNMUing against haskell-glut 2.7.0.10-4 to fix the RC
bug #861957. This should pick up the fixes to haskell-glut in #861976
so raincat can start again. It needs binNMUing to pick up the changes
because these are both haskell packages (so it's statically linked).

Thanks,
James

nmu raincat_1.1.1.2-3 . ANY . unstable . -m "rebuild against haskell-glut 
2.7.0.10-4 to fix #861957"

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

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



signature.asc
Description: OpenPGP digital signature

Bug#861792: ITP: lr -- list files, recursively

[Nicolas Braud-Santoni]

On Thu, May 04, 2017 at 08:53:27AM +0200, Alexander Wirt wrote:
> On Thu, 04 May 2017, Nicolas Braud-Santoni wrote:
> > 
> > * Package name: lr
> >   Version : 0.4
>
> Please don't (and this counts for your xr ITP too) add new two-letter 
> binaries. 
> This will just get everyone into trouble. 

What would be the rationale for this?

Changing the executable name from upstream's would be even more confusing, IME.


Best,

  nicoo

Bug#862042: xterm: if the faceName resource is defined, the -fn (-font) option is ignored

[Thomas Dickey]

- Original Message -
| From: "Vincent Lefevre" 
| To: "Thomas Dickey" 
| Cc: 862...@bugs.debian.org
| Sent: Sunday, May 7, 2017 6:10:47 PM
| Subject: Bug#862042: xterm: if the faceName resource is defined, the -fn 
(-font) option is ignored
| 
| On 2017-05-07 17:24:43 -0400, Thomas Dickey wrote:
| > Perhaps you'll see it here:
| > 
| > 
http://invisible-island.net/xterm/manpage/xterm.html#VT100-Widget-Resources:renderFont
| > 
| > Most of xterm's options work by setting resource values (there are
| > a
| > handful of special cases such as "-help", "-version" which do not).
| > I can clarify the manual, but there's no reason to change the
| > program logic (in this bug, anyway).
| 
| The behavior is not what is described in this section. I would agree
| if renderFont were "true". But the manual says:
| 
|   The default is "default".
| 
| (and I haven't changed it). For "default":
| 
| startup using the normal (bitmap) font, but enable the
| ^^
| "TrueType Fonts" menu entry to allow runtime switching
| to/from TrueType fonts.
| 
| If there is no faceName resource set, then runtime
| switching to TrueType fonts is disabled.  Xterm has a
| separate  compiled-in value for faceName for the special
| case where renderFont is "default".  That is normally
| "mono".
| 
| So, according to the manual, I should get the bitmap font.

I'll take a closer look, to see where the disagreement lies.

| Moreover, the text for "-fn font" is not sufficient.
| 
| This option specifies the font to be used for displaying normal
| text.  The corresponding resource name is font.  The resource
| value default is fixed.
| 
| First, it is not mentioned that the font must be a bitmap font (?).
| For instance, it does not work with "Monospace". It should also be
| clarified when the -fn option is ignored.

"-fn" is (as noted in the manual page), an "X Toolkit Option", which is
documented in the X manual page, where it expects an XLFD.

https://www.x.org/archive//X11R6.8.2/doc/X.7.html

-- 
Thomas E. Dickey 
http://invisible-island.net
ftp://invisible-island.net

Bug#826008: xserver-xorg-input-multitouch -- new version available

[Nobuhiro Iwamatsu]

Hi,

2017-05-03 7:11 GMT+09:00 Nicholas D Steeves :
> Control: retitle -1 xserver-xorg-input-multitouch -- new version available
>

Current installed vetsion is 1.0~rc2+git20110312-2, not 1.0~rc2.
This version includes following commit:

> git log --pretty=oneline v1.0-rc2..v1.0-rc3
> 55ab6c4ecb43e6f2ec34b36533ef308d00a709e4 xf86-input-multitouch v1.0-rc3
> 4d87c041f6a232aa30528d70d4b9946d1824b4ed Four finger swipes in multitouch
> afbbc4b9470869933223e3970c7a63f1c52c1d69 Makefile: make LIBDIR configurable
> 161026ce49526593d0ebfd96a7c087e3e1b0f9f5 Add missing thumb reset at state 
> extraction
> 1db2e14bed379bbf1c5f3140a903437b146c5cce Fix event flood in tap handling
> a12ed738095819beab0b42c6c8a1566c063bb79e Support XINPUT 12
>
> Are these features available using another driver?  Given how I've
> seen Macbook powerusers use their touchpads, four finger swipes are
> fairly important.  Also, what is the severity of missing XINPUT 12
> support?
>

We can use xserver-xorg-input-mtrack instead of xserver-xorg-input-multitouch.
Could you use xserver-xorg-input-mtrack?

> Cheers,
> Nicholas
>
> P.S. Please CC Bug #826008 and me

Best regards,
  Nobuhiro

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6

Bug#862060: eyeD3: no option to move v2 tag to end of file

[Thorsten Glaser]

Package: eyed3
Version: 0.7.10-1
Severity: normal

To make MP3 files with ID3 tags compatible with e.g. mpg123,
the ID3 tags have to be at the end of the file, not at the
beginning.

When converting v2.3 tags to v2.4 with eyeD3, they still are
at the beginning of the files afterwards, and I can’t figure
out from the manpage how to move them to the end.

(The manpage could use rework anyway, e.g. it does not document
that calling without *any* non-argument options displays _some_
(not all?) of the tag data.)

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

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

Versions of packages eyed3 depends on:
ii  python-eyed3  0.7.10-1

eyed3 recommends no packages.

eyed3 suggests no packages.

-- no debconf information

Bug#862057: udev: If more than one NIC the system is booting longer

[Michael Biebl]

Control: tags -1 moreinfo

Am 08.05.2017 um 01:45 schrieb m.alfa...@gmail.com:
> Package: udev
> Version: 232-22
> Severity: important
> 
> Hi.
> 
> When using more than one NIC the system boot is longer than usual. In dmesg
> i have fond a message telling me that it took too long to do it.

Do what exactly? Can you provide specific error messages please

 This appears
> on NICs after the first. The first NIC does not have trouble detecting it.
> After that it ends up with following names renameX. X means a number.
> This happens even if disabled Predictable Network Names.

Please share more information about your network configuration.
Please also provide a journal log from the boot.



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



signature.asc
Description: OpenPGP digital signature

Bug#849784: lomoco: udev support broken, missing file /lib/udev/udev.lomoco

[Gunnar Hjalmarsson]

This issue was reported in Ubuntu as well via 
, and I proposed a fix there (please 
find the debdiff attached to this message).


--
Gunnar Hjalmarsson
https://launchpad.net/~gunnarhj

diff -Nru lomoco-1.0.orig/debian/changelog lomoco-1.0/debian/changelog
--- lomoco-1.0.orig/debian/changelog2016-12-18 12:48:37.0 +0100
+++ lomoco-1.0/debian/changelog 2017-05-07 23:12:07.018931544 +0200
@@ -1,3 +1,10 @@
+lomoco (1.0.0-2ubuntu1) artful; urgency=low
+
+  * 'Merge' the two install files in /debian so /lib/udev/udev.lomoco
+gets installed (LP: #1685660).
+
+ -- Gunnar Hjalmarsson   Sun, 07 May 2017 23:12:00 +0200
+
 lomoco (1.0.0-2) unstable; urgency=low
 
   * QA upload.
diff -Nru lomoco-1.0.orig/debian/install lomoco-1.0/debian/install
--- lomoco-1.0.orig/debian/install  2016-12-18 12:34:45.0 +0100
+++ lomoco-1.0/debian/install   1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-udev/udev.lomoco /lib/udev
diff -Nru lomoco-1.0.orig/debian/lomoco.install lomoco-1.0/debian/lomoco.install
--- lomoco-1.0.orig/debian/lomoco.install   2016-12-18 12:48:18.0 
+0100
+++ lomoco-1.0/debian/lomoco.install2017-05-07 22:58:12.828457018 +0200
@@ -1 +1,2 @@
+udev/udev.lomoco /lib/udev
 debian/lomoco.metainfo.xml /usr/share/metainfo

Bug#862059: sbuild: please sign buildinfo files

[Steven Chamberlain]

Package: sbuild
Version: 0.73.0-4
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: infrastructure

Hello,

dpkg-buildpackage typically generates a .changes and .buildinfo file,
and signs both (since at least dpkg 1.18.19).

But when using sbuild, dpkg-buildpackage inside of the build chroot does
not do the signing, but rather sbuild signs the .changes file afterward.

Please could that code be updated to also sign the .buildinfo (if one
was created).

I have not tested the attached patch (yet?) but it explains the issue at
least.  Here is typical output where only the .changes file gets signed:

> 
> Finished at 20170314-2338
> Build needed 00:00:43, 5660k disc space
> Signature with key 'F2F4A5FC' requested:
>  signfile /home/buildd/build/hello_2.10-1+b1_amd64.changes F2F4A5FC
> 
> Successfully signed changes file

The relevance/importance of this is that official Debian package builds
produce .buildinfo files now, and dak archives them, but they are not
being signed yet.

Thanks!

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

Kernel: kFreeBSD 10.1-0-amd64
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
diff --git a/lib/Sbuild/Build.pm b/lib/Sbuild/Build.pm
index 9a767a2..b196812 100644
--- a/lib/Sbuild/Build.pm
+++ b/lib/Sbuild/Build.pm
@@ -2668,6 +2668,21 @@ sub get_changes {
 return $changes;
 }
 
+sub get_buildinfo {
+my $self=shift;
+my $buildinfo;
+
+if ($self->get_conf('BUILD_ARCH_ANY')) {
+	$buildinfo = $self->get('Package_SVersion') . '_' . $self->get('Host Arch') . '.buildinfo';
+} elsif ($self->get_conf('BUILD_ARCH_ALL')) {
+	$buildinfo = $self->get('Package_SVersion') . "_all.buildinfo";
+} elsif ($self->get_conf('BUILD_SOURCE')) {
+	$buildinfo = $self->get('Package_SVersion') . "_source.buildinfo";
+}
+
+return $buildinfo;
+}
+
 sub check_space {
 my $self = shift;
 my @files = @_;
@@ -3169,6 +3184,7 @@ sub close_build_log {
 	my $key_id = $self->get_conf('KEY_ID');
 	my $build_dir = $self->get_conf('BUILD_DIR');
 	my $changes;
+	my $buildinfo;
 	$self->log(sprintf("Signature with key '%s' requested:\n", $key_id));
 	$changes = $self->get_changes();
 	if (!defined($changes)) {
@@ -3176,6 +3192,10 @@ sub close_build_log {
 	} else {
 		system('debsign', '--re-sign', "-k$key_id", '--', "$build_dir/$changes");
 	}
+	$buildinfo = $self->get_buildinfo();
+	if (defined($buildinfo) && stat($buildinfo)) {
+		system('debsign', '--re-sign', "-k$key_id", '--', "$build_dir/$buildinfo");
+	}
 	if ($self->get_conf('SOURCE_ONLY_CHANGES')) {
 		my $so_changes = $build_dir . '/' . $self->get('Package_SVersion') . "_source.changes";
 		if (-r $so_changes) {

Bug#862042: xterm: if the faceName resource is defined, the -fn (-font) option is ignored

[Vincent Lefevre]

On 2017-05-07 17:24:43 -0400, Thomas Dickey wrote:
> Perhaps you'll see it here:
> 
> http://invisible-island.net/xterm/manpage/xterm.html#VT100-Widget-Resources:renderFont
> 
> Most of xterm's options work by setting resource values (there are a
> handful of special cases such as "-help", "-version" which do not).
> I can clarify the manual, but there's no reason to change the
> program logic (in this bug, anyway).

The behavior is not what is described in this section. I would agree
if renderFont were "true". But the manual says:

  The default is "default".

(and I haven't changed it). For "default":

startup using the normal (bitmap) font, but enable the
^^
"TrueType Fonts" menu entry to allow runtime switching
to/from TrueType fonts.

If there is no faceName resource set, then runtime
switching to TrueType fonts is disabled.  Xterm has a
separate  compiled-in value for faceName for the special
case where renderFont is "default".  That is normally
"mono".

So, according to the manual, I should get the bitmap font.

Moreover, the text for "-fn font" is not sufficient.

This option specifies the font to be used for displaying normal
text.  The corresponding resource name is font.  The resource
value default is fixed.

First, it is not mentioned that the font must be a bitmap font (?).
For instance, it does not work with "Monospace". It should also be
clarified when the -fn option is ignored.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#860947: [Pkg-openldap-devel] Bug#860947: Bug#860947: slapd: Slapd fails to stop sometimes

[Ryan Tandy]

I have committed a fix upstream for the SASL concurrency issue I found.

http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=patch;h=431c4af526b18abb4a18c2c4c8655690b753cbe5

Since I still don't know for sure whether it's the same problem you were 
having, it would still be great if you could try to test it at some 
point. Otherwise I may just close this bug when the fix reaches Debian, 
and let you reopen if it happens again.

Bug#862058: python-debian: required dependency on python-apt

[Matthieu Caneill]

Package: python-debian
Version: 0.1.28
Severity: normal

Dear Maintainer,

python-debian has a Recommends: dependency on python-apt, and a
mechanism to import alternatives when it is not present.

However, when using Sources.iter_paragraphs(f), with f being a file
object of a compressed file (e.g. Sources.gz), python-debian will
decompress the file when python-apt is present, and try to read the
compressed file when it is not (and fail with an expected
UnicodeDecode error).

This affects all current versions.

Cheers,
--
Matthieu

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

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

Versions of packages python-debian depends on:
ii  python-chardet  2.3.0-2
ii  python-six  1.10.0-3
pn  python:any  

Versions of packages python-debian recommends:
ii  python-apt  1.1.0~beta4

Versions of packages python-debian suggests:
ii  gpgv  1.4.20-6

-- no debconf information


signature.asc
Description: PGP signature

Bug#862053: wordpress: CVE-2017-8295

[Craig Small]

Hi Markus,
  Thankyou for the bug report. I was aware of this bug but haven't seen
anything from the WordPress upstream yet. I'll give them a few days to see
if they bring out an official patch or not.

This only seems to work for IP based virtual hosts. If your wordpress
server uses named virtual hosts, then it doesn't work unless it is the
default because the host header is used to work out what virtual server to
use.

 - Craig

>
> --
Craig Small (@smallsees)   http://dropbear.xyz/ csmall at : enc.com.au
Debian GNU/Linux   http://www.debian.org/   csmall at : debian.org
GPG fingerprint:5D2F B320 B825 D939 04D2  0519 3938 F96B DF50 FEA5

Bug#847479: xterm: display issue with double-width character like ? on the last column via ncurses

[Vincent Lefevre]

On 2017-05-07 16:30:24 -0400, Thomas Dickey wrote:
> a typescript (from "script") helps.

After trying again. the problem seems to occur only when one resizes
the terminal window. So, a typescript doesn't help. It seems to be a
problem similar to what I had already reported under other conditions:

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

The problem disappears if the xterm window is redrawn, e.g. via the
RefreshWindow fvwm command:

  RefreshWindow
Causes the chosen window to redraw itself.  All pending updates
of the window's style and look are applied immediately.  E.g. if
Style or TitleStyle commands were issued inside a fvwm function.

To reproduce the bug, use xterm with the 7x13 font.

Consider the following mbox file:

--
>From a@b.invalid Thu Dec  8 16:50:47 2016
Subject: =?utf-8?Q?character_like_?= =?utf-8?B?8J+NuA==?= on

--

Open it with:

  mutt -F /dev/null -R -f test.mbox

Then reduce the xterm window width so that the second column of the
double-width character is removed (but not the first column).

For instance, you should get initially:

q:Quit  d:Del  u:Undel  s:Save  m:Mail  r:Reply  g:Group  ?:Help  
   1 N   Dec 08 a@b.invalid (  0K) character like XY on   

where "XY" is the double-width character (here it appears as a
wide question mark in a circle since the character isn't probably
in the font). So, reduce the xterm window width so that the first
line is:

q:Quit  d:Del  u:Undel  s:Save  m:Mail  r:Reply  g:Grou

Here, the second line is:

   1 N   Dec 08 a@b.invalid (  0K) character like

but some pixels on the right of the last column are visible
(a bit like in bug 738794 mentioned above).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#861681: unblock: tomcat8/8.5.14-1

[Emmanuel Bourg]

Le 7/05/2017 à 19:49, Niels Thykier a écrit :

> ASSUMING that nothing in Debian stretch relies on the servlet4 preview
> parts, then ack, please go ahead.  Please remove the moreinfo tag once
> the upload has been processed.

Thank you Niels. I confirm that the Servlet 4 preview isn't used in
Debian yet.

Emmanuel Bourg

Bug#862057: udev: If more than one NIC the system is booting longer

[m . alfaeko]

Package: udev
Version: 232-22
Severity: important

Hi.

When using more than one NIC the system boot is longer than usual. In dmesg
i have fond a message telling me that it took too long to do it. This appears
on NICs after the first. The first NIC does not have trouble detecting it.
After that it ends up with following names renameX. X means a number.
This happens even if disabled Predictable Network Names.

Thank You

-- Package-specific info:

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

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

Versions of packages udev depends on:
ii  adduser  3.115
ii  dpkg 1.18.23
ii  libacl1  2.2.52-3+b1
ii  libblkid12.29.2-1
ii  libc62.24-10
ii  libkmod2 23-2
ii  libselinux1  2.6-3+b1
ii  libudev1 232-22
ii  lsb-base 9.20161125
ii  procps   2:3.3.12-3
ii  util-linux   2.29.2-1

udev recommends no packages.

udev suggests no packages.

Versions of packages udev is related to:
ii  systemd  232-22

-- Configuration Files:
/etc/udev/udev.conf changed [not included]

-- no debconf information
P: /devices/LNXSYSTM:00
E: DEVPATH=/devices/LNXSYSTM:00
E: ID_VENDOR_FROM_DATABASE=The Linux Foundation
E: MODALIAS=acpi:LNXSYSTM:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=1004322
E: net.ifnames=0

P: /devices/LNXSYSTM:00/LNXCPU:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:00
E: ID_VENDOR_FROM_DATABASE=The Linux Foundation
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=1007855
E: net.ifnames=0

P: /devices/LNXSYSTM:00/LNXPWRBN:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00
E: DRIVER=button
E: ID_VENDOR_FROM_DATABASE=The Linux Foundation
E: MODALIAS=acpi:LNXPWRBN:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=1058269
E: net.ifnames=0

P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
E: EV=3
E: ID_FOR_SEAT=input-acpi-LNXPWRBN_00
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=acpi-LNXPWRBN:00
E: ID_PATH_TAG=acpi-LNXPWRBN_00
E: KEY=10 0
E: MODALIAS=input:b0019vp0001e-e0,1,k74,ramlsfw
E: NAME="Power Button"
E: PHYS="LNXPWRBN/button/input0"
E: PRODUCT=19/0/1/0
E: PROP=0
E: SUBSYSTEM=input
E: TAGS=:seat:
E: USEC_INITIALIZED=96187328
E: net.ifnames=0

P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event3
N: input/event3
E: DEVNAME=/dev/input/event3
E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event3
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=acpi-LNXPWRBN:00
E: ID_PATH_TAG=acpi-LNXPWRBN_00
E: MAJOR=13
E: MINOR=67
E: SUBSYSTEM=input
E: TAGS=:power-switch:
E: USEC_INITIALIZED=96280782
E: net.ifnames=0

P: /devices/LNXSYSTM:00/LNXSLPBN:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSLPBN:00
E: DRIVER=button
E: ID_VENDOR_FROM_DATABASE=The Linux Foundation
E: MODALIAS=acpi:LNXSLPBN:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=1056610
E: net.ifnames=0

P: /devices/LNXSYSTM:00/LNXSLPBN:00/input/input5
E: DEVPATH=/devices/LNXSYSTM:00/LNXSLPBN:00/input/input5
E: EV=3
E: ID_FOR_SEAT=input-acpi-LNXSLPBN_00
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=acpi-LNXSLPBN:00
E: ID_PATH_TAG=acpi-LNXSLPBN_00
E: KEY=4000 0 0
E: MODALIAS=input:b0019vp0003e-e0,1,k8E,ramlsfw
E: NAME="Sleep Button"
E: PHYS="LNXSLPBN/button/input0"
E: PRODUCT=19/0/3/0
E: PROP=0
E: SUBSYSTEM=input
E: TAGS=:seat:
E: USEC_INITIALIZED=96187843
E: net.ifnames=0

P: /devices/LNXSYSTM:00/LNXSLPBN:00/input/input5/event4
N: input/event4
E: DEVNAME=/dev/input/event4
E: DEVPATH=/devices/LNXSYSTM:00/LNXSLPBN:00/input/input5/event4
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=acpi-LNXSLPBN:00
E: ID_PATH_TAG=acpi-LNXSLPBN_00
E: MAJOR=13
E: MINOR=68
E: SUBSYSTEM=input
E: TAGS=:power-switch:
E: USEC_INITIALIZED=96281618
E: net.ifnames=0

P: /devices/LNXSYSTM:00/LNXSYBUS:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00
E: ID_VENDOR_FROM_DATABASE=The Linux Foundation
E: MODALIAS=acpi:LNXSYBUS:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=1055309
E: net.ifnames=0

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00
E: ID_VENDOR_FROM_DATABASE=The Linux Foundation
E: MODALIAS=acpi:PNP0A03:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=1152793
E: net.ifnames=0

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/ACPI0003:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/ACPI0003:00
E: DRIVER=ac
E: ID_VENDOR_FROM_DATABASE=The Linux Foundation
E: MODALIAS=acpi:ACPI0003:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=1160886
E: net.ifnames=0

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/ACPI0003:00/power_supply/AC
E: 
DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/ACPI0003:00/power_supply/AC
E: POWER_SUPPLY_NAME=AC
E: POWER_SUPPLY_ONLINE=1
E: SUBSYSTEM=power_supply
E: USEC_INITIALIZED=96190343
E: net.ifnames=0

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/LNXVIDEO:00
E: 

Bug#862056: screen-message: please invert the default colours

[Chris Lamb]

Source: screen-message
Version: 0.24-1
Severity: wishlist
Tags: patch

Hi,

Please invert the default colours for screen-message; a large white
background is not very "hacker friendly" and almost physically painful
to experience very late into the early hours…

Patch attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/sm.6 b/sm.6
index 6a344b1..92140dd 100644
--- a/sm.6
+++ b/sm.6
@@ -28,7 +28,7 @@ sm \- Displays a short text fullscreen
 .SH DESCRIPTION
 .BR Screen\ Message 
 will display a given multi-line message as large as
-possible, fullscreen and black on white. You can specify the text either
+possible, fullscreen and white on black. You can specify the text either
 when launching sm, or edit it while the program is running.
 .PP
 After a short timeout, the text entry and the quit button will disappear, 
leaving
@@ -48,13 +48,13 @@ it will read the text to display from the standard input, 
see \fBREMOTE CONTROLL
 .TP
 .BI \-f,\ \-\-foreground= colordesc
 Define a different color to use for the foreground of the text to
-display than black. The text string can be in any of the forms accepted
+display than white. The text string can be in any of the forms accepted
 by XParseColor; these include name for a color from rgb.txt, such as
 DarkSlateGray, or a hex specification such as #3050b2 or #35b.
 .TP
 .BI \-b,\ \-\-background= colordesc
 Define a different color to use for the background of the text to
-display than white. For possible values, see above.
+display than black. For possible values, see above.
 .TP
 .BI \-n,\ \-\-font= fontspec
 Define a different font to use than the default sans-serif font of your
diff --git a/sm.c b/sm.c
index 0adc28f..0471720 100644
--- a/sm.c
+++ b/sm.c
@@ -97,7 +97,7 @@ static char *get_text() {
 static void redraw(GtkWidget *draw, cairo_t *cr, gpointer data) {
int q;
 
-   gdk_cairo_set_source_rgba(cr, );
+   gdk_cairo_set_source_rgba(cr, );
cairo_paint(cr);
 
const char *text = get_text();
@@ -333,14 +333,14 @@ int main(int argc, char **argv) {
g_signal_connect(window, "destroy", G_CALLBACK(gtk_main_quit), NULL);
 
if (foreground != NULL) {
-   my_gdk_rgba_parse(, foreground);
+   my_gdk_rgba_parse(, foreground);
} else {
-   my_gdk_rgba_parse(, "black");
+   my_gdk_rgba_parse(, "white");
}
if (background != NULL) {
-   my_gdk_rgba_parse(, background);
+   my_gdk_rgba_parse(, background);
} else {
-   my_gdk_rgba_parse(, "white");
+   my_gdk_rgba_parse(, "black");
}
 
draw = gtk_drawing_area_new();
diff --git a/webapp.html b/webapp.html
index 27a6b8c..f4fa968 100644
--- a/webapp.html
+++ b/webapp.html
@@ -31,6 +31,8 @@
border:0px;
text-align:center;
overflow:hidden;
+   background-color:black;
+   color:white;
 }
 
 #test {

Bug#861985: unblock: variety/0.6.3-5 (pre-upload approval)

[Gianfranco Costamagna]

control: tags -1 -moreinfo
> Ack, please go ahead and remove the moreinfo tag once the upload is in
> unstable and have built on all relevant release architectures.
> 
it should be ok now

thanks!

G.




signature.asc
Description: OpenPGP digital signature

Bug#862042: xterm: if the faceName resource is defined, the -fn (-font) option is ignored

[Thomas Dickey]

- Original Message -
| From: "Vincent Lefevre" 
| To: "Thomas Dickey" 
| Cc: 862...@bugs.debian.org
| Sent: Sunday, May 7, 2017 5:13:32 PM
| Subject: Bug#862042: xterm: if the faceName resource is defined, the -fn 
(-font) option is ignored
| 
| On 2017-05-07 16:29:35 -0400, Thomas Dickey wrote:
| > - Original Message -
| > | From: "Vincent Lefevre" 
| > | To: "Debian Bug Tracking System" 
| > | Sent: Sunday, May 7, 2017 1:23:00 PM
| > | Subject: Bug#862042: xterm: if the faceName resource is defined,
| > | the -fn (-font) option is ignored
| > | 
| > | Package: xterm
| > | Version: 327-2
| > | Severity: minor
| > | 
| > | If I define the faceName resource, e.g. with
| > | 
| > | XTerm*faceName: Monospace
| > | 
| > | in the .Xresources file (read by xrdb), then the -fn (-font)
| > | option
| > | is ignored. For instance,
| > | 
| > |   xterm -fn 7x13
| > | 
| > | has no effect. Options normally override the default resources,
| > | but
| > | this is not the case here. And the observed behavior is not
| > | documented.
| > 
| > last paragraph in this section:
| > 
| > 
http://invisible-island.net/xterm/manpage/xterm.html#VT100-Widget-Resources:faceSize
| > 
| > (it's been there quite a while, and won't be changed)
| 
| Sorry, but I don't understand. In particular, this does not
| explain the behavior when none of faceSize resources are set.

Perhaps you'll see it here:

http://invisible-island.net/xterm/manpage/xterm.html#VT100-Widget-Resources:renderFont

Most of xterm's options work by setting resource values (there are a handful
of special cases such as "-help", "-version" which do not).  I can clarify the
manual, but there's no reason to change the program logic (in this bug, 
anyway). 

-- 
Thomas E. Dickey 
http://invisible-island.net
ftp://invisible-island.net

Bug#862022: [Qa-jenkins-dev] Bug#862022: reproducible-builds.org: build log sent uncompressed

[Mattia Rizzolo]

On Sun, May 07, 2017 at 02:46:15PM +, Daniel Shahaf wrote:
> Ivo De Decker wrote on Sun, May 07, 2017 at 16:24:14 +0200:
> > there is a link with the build log which is listed as '7 MB', which is in 
> > fact
> > 240 MB. It seems the site lists the compressed size, but sends the
> > uncompressed log file.
> 
> Further information:
> 
> % wget 
> https://tests.reproducible-builds.org/debian/logs/unstable/amd64/cross-toolchain-base-ports_10.build2.log.gz
> ⋮
> HTTP/1.1 200 OK
> Content-Type: text/plain; charset=utf-8
> % file - < cross-toolchain-base-ports_10.build2.log.gz
> /dev/stdin: ASCII text, with CRLF line terminators
> %
> 
> So, the gunzipping is not browser-side but jenkins-side.

This is only partially right: the uncrompression is done server
(jenkins) side only if the client doesn't acknowledge it is able to
receive gzip data:

mattia@warren /tmp % curl -H "Accept-Encoding: gzip" -o foo -D - 
https://tests.reproducible-builds.org/debian/logs/unstable/amd64/cross-toolchain-base-ports_10.build2.log.gz
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0HTTP/1.1 200 OK
Date: Sun, 07 May 2017 21:13:55 GMT
Server: Apache/2.4.10
Strict-Transport-Security: max-age=15552000
Last-Modified: Sun, 30 Apr 2017 01:09:55 GMT
ETag: "bd545-54e57f6ee2800"
Accept-Ranges: bytes
Content-Length: 775493
Vary: Accept-Encoding
Content-Type: text/plain; charset=utf-8
Content-Encoding: gzip

100  757k  100  757k0 0   395k  0  0:00:01  0:00:01 --:--:--  395k
mattia@warren /tmp % file foo
foo: gzip compressed data, max compression, from Unix
mattia@warren /tmp % lh foo
-rw-r--r-- 1 mattia mattia 758K May  7 23:13 foo
mattia@warren /tmp % 


This is done becuase of apache also happily mapping foo.txt files to a
file that it is actually foo.txt.gz, and also for browser not understing
gzip.

That said, I agree it's a buggy behaviour when the user really requested
a file named .gz, and it should really send the gzip-compressed file.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#862042: xterm: if the faceName resource is defined, the -fn (-font) option is ignored

[Vincent Lefevre]

On 2017-05-07 16:29:35 -0400, Thomas Dickey wrote:
> - Original Message -
> | From: "Vincent Lefevre" 
> | To: "Debian Bug Tracking System" 
> | Sent: Sunday, May 7, 2017 1:23:00 PM
> | Subject: Bug#862042: xterm: if the faceName resource is defined, the -fn 
> (-font) option is ignored
> | 
> | Package: xterm
> | Version: 327-2
> | Severity: minor
> | 
> | If I define the faceName resource, e.g. with
> | 
> | XTerm*faceName: Monospace
> | 
> | in the .Xresources file (read by xrdb), then the -fn (-font) option
> | is ignored. For instance,
> | 
> |   xterm -fn 7x13
> | 
> | has no effect. Options normally override the default resources, but
> | this is not the case here. And the observed behavior is not
> | documented.
> 
> last paragraph in this section:
> 
> http://invisible-island.net/xterm/manpage/xterm.html#VT100-Widget-Resources:faceSize
> 
> (it's been there quite a while, and won't be changed)

Sorry, but I don't understand. In particular, this does not
explain the behavior when none of faceSize resources are set.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#861484: [Pkg-julia-devel] Bug#861484: Bug#861484: Bug#861484: Bug#861484: julia: FTBFS on arm64

[Graham Inggs]

Julia builds successfully on a Raspberry Pi 3 running an image
prepared by xylnao, dated 2016-04-14 [1] with kernel 4.5.0.
It fails in the same way as on arm-arm-04 and arm-conova-01 on a
Raspberry Pi 3 running an image prepared by Michael Stapelberg, dated
2017-03-22 [2] with kernel 4.9.18-1.
Both images were upgraded to current Stretch and 1GB was allocated for
a swapfile.

The build failures occur after the Julia executable has been built,
when it is run for the first time in order to compile coreimg.jl.

Instead of building the package, the segfault should be reproducible
by installing julia from the archive and then running 'julia' from a
terminal.

You should get output similar to:

ginggs@rpi3:~$ uname -a
Linux rpi3 4.5.0+ #1 SMP PREEMPT Tue Apr 12 22:51:39 PDT 2016 aarch64 GNU/Linux
ginggs@rpi3:~$ julia
   _
   _   _ _(_)_ |  A fresh approach to technical computing
  (_) | (_) (_)|  Documentation: http://docs.julialang.org
   _ _   _| |_  __ _   |  Type "?help" for help.
  | | | | | | |/ _` |  |
  | | |_| | | | (_| |  |  Version 0.4.7 (2016-09-18 16:17 UTC)
 _/ |\__'_|_|_|\__'_|  |  Debian version 0.4.7-6+b2
|__/   |  aarch64-linux-gnu

julia> versioninfo()
Julia Version 0.4.7
Commit ae26b25 (2016-09-18 16:17 UTC)
Platform Info:
  System: Linux (aarch64-linux-gnu)
  CPU: unknown
  WORD_SIZE: 64
  BLAS: libopenblas (NO_LAPACKE NO_AFFINITY ARMV8)
  LAPACK: libopenblas
  LIBM: libopenlibm
  LLVM: libLLVM-3.8

...but this is bad:

ginggs@rpi3:~$ uname -a
Linux rpi3 4.9.0-2-arm64 #1 SMP Debian 4.9.18-1 (2017-03-30) aarch64 GNU/Linux
ginggs@rpi3:~$ julia

signal (11): Segmentation fault
isfile at ./stat.jl:107
Segmentation fault


[1] https://www.raspberrypi.org/forums/viewtopic.php?f=72=137963=141
[2] https://people.debian.org/~stapelberg//2017/03/22/raspberry-pi-3.html

Bug#861953: unblock: runc/0.1.1+dfsg1-3

[Niels Thykier]

Control: tags -1 moreinfo
Control: forcemerge 858250 861966

Roger Shimizu:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please unblock package runc
> 
> Since there's already a newer package in unstable, I guess it's
> necessary to use "testing-proposed-updates"
> 
> Here I'm fixing #858250, which is FTBFS RC issue.


Hi Roger,

Thanks for working on fixing #858250 for stretch. :)

Before there is an upload to testing-proposed-updates, the original bug
should be resolved in unstable first.  That means that #858250 should be
closed in unstable first.

On a related note, the Debian Bug Tracker can determine which suites are
affected by looking at found + fixed versions, so there is no need to
have two bugs for this (which is why I have merged #861966 back into
#858250).


> [...]
> 
> Please help to:
>   - confirm it's OK to target "testing-proposed-updates"

Once #858250 is fixed in unstable, then please go ahead.

>   - help to sponsor the upload from mentors (if not, I'll file a RFS to
>   mentors list)
> 

Please file an RFS bug for this upload once #858250 is resolved in unstable.

> Enclosed is the debdiff against the package in testing.
> 
> unblock runc/0.1.1+dfsg1-3
> 
> Cheers,
> --
> Roger Shimizu, GMT +9 Tokyo
> PGP/GPG: 4096R/6C6ACD6417B3ACB1
> 

Thanks,
~Niels

Bug#847440: pending

[Bernhard Schmidt]

On Thu, Dec 15, 2016 at 11:18:47AM +, Thomas Hood wrote:

Hi Thomas,

> package resolvconf
> tags 847440 pending
> stop

You set this to Pending almost five months ago, do you still plan to
apply this for Stretch?

Bernhard


signature.asc
Description: Digital signature

Bug#847479: xterm: display issue with double-width character like ? on the last column via ncurses

[Thomas Dickey]

- Original Message -
| From: "Vincent Lefevre" 
| To: dic...@his.com, 847...@bugs.debian.org
| Sent: Sunday, May 7, 2017 12:56:32 PM
| Subject: Bug#847479: xterm: display issue with double-width character like ? 
on the last column via ncurses
| 
| On 2017-05-07 10:53:24 -0400, Thomas Dickey wrote:
| > Attaching a script, for discussion.  I don't see the problem, but
| > noticed
| > that the character is "new", and for instance if you were running
| > xterm
| > remotely so that the wcwidth wasn't known then you could get odd
| > results.
| 
| I can't reproduce the problem with your script. But it is
| reproducible
| with Mutt. Maybe a problem that occurs only when margins are used.
| I don't know what ncurses does exactly...
| 
| Everything is local on the machine.


a typescript (from "script") helps.

-- 
Thomas E. Dickey 
http://invisible-island.net
ftp://invisible-island.net

Bug#844431: Packages should be reproducible

[Daniel Shahaf]

Chris Lamb wrote on Thu, Nov 17, 2016 at 12:30:44 +0100:
> +++ b/policy.sgml
> @@ -2503,6 +2503,20 @@ endif
> +  

Note that the id should be changed before applying, since there already
is a sect with this id value.

Bug#854475: postfix: systemd needs postfix@.service to have "After=network.target"

[Bernhard Schmidt]

On Sat, Apr 15, 2017 at 11:42:37PM +0200, Marcus Jodorf wrote:

Hi,

is there anything I can do to get this fixed for Stretch? I can
pretty reliably reproduce this issue with all my upgraded Stretch
systems, neither of them can send mails after a reboot until Postfix is
getting restarted

An After=network.target should be pretty low-risk even this late in the
release cycle and should fix this issue.

Best Regards,
Bernhard


signature.asc
Description: Digital signature

Bug#841243: mate-desktop: Please change icon location for mate-color-select

[Vlad Orlov]

Hi,

This utility should not affect desktop colors. You can copy color code from it
to use in some other application, that's all.

Bug#862042: xterm: if the faceName resource is defined, the -fn (-font) option is ignored

[Thomas Dickey]

- Original Message -
| From: "Vincent Lefevre" 
| To: "Debian Bug Tracking System" 
| Sent: Sunday, May 7, 2017 1:23:00 PM
| Subject: Bug#862042: xterm: if the faceName resource is defined, the -fn 
(-font) option is ignored
| 
| Package: xterm
| Version: 327-2
| Severity: minor
| 
| If I define the faceName resource, e.g. with
| 
| XTerm*faceName: Monospace
| 
| in the .Xresources file (read by xrdb), then the -fn (-font) option
| is ignored. For instance,
| 
|   xterm -fn 7x13
| 
| has no effect. Options normally override the default resources, but
| this is not the case here. And the observed behavior is not
| documented.

last paragraph in this section:

http://invisible-island.net/xterm/manpage/xterm.html#VT100-Widget-Resources:faceSize

(it's been there quite a while, and won't be changed)

-- 
Thomas E. Dickey 
http://invisible-island.net
ftp://invisible-island.net

Bug#861715: unblock: php-horde-crypt/2.7.5-2

[Niels Thykier]

Control: tags -1 moreinfo

Mathieu Parent:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please unblock package php-horde-crypt
> 
> This fixes a security issue:
> 
>   * Escape user provided recipients and charset data. Fixes CVE-2017-7413 and
> CVE-2017-7414 (Closes: #859635)
> 
> (debdiff attached)
> 
> Note that the package doesn't work correctly in stretch, because it is not
> compatible with gpg v2 (#849151 and #854819). I plan to fix this later, but
> maybe in a point-release. Today, I want to prevent IMP (php-horde-imp) from
> being removed from testing.
> 
> unblock php-horde-crypt/2.7.5-2
> 
> Thanks!
> 
> [...]

Sorry, but I think I am missing context here.  How functional is
php-horde-crypt in stretch right now?  If lack of gpg v2 support causes
a major loss of functionality then #849151 and #854819 should be RC and
handled accordingly.

Thanks,
~Niels

Bug#862055: apt: Rework daily timers for buster, drop internal timestamps

[Julian Andres Klode]

Package: apt
Severity: normal
Control: tag -1 confirmed

APT's daily cron job and systemd timers currently keep internal
timestamps. systemd keeps its own internal timestamp, leading
to two timestamps: When the systemd timestamp is old enough,
the apt timestamp might not be causing confusion because the
service started and did nothing.

We currently have 6 timestamps:

* update
* download upgradable
* unattended-upgrade
* backup archive/
* autoclean
* clean

I propose to refactor this into three groups:

* download (update, download-upgradable, download u-u upgrades)
* upgrade (run unattended-upgrade)
* maintenance (backup/autoclean/clean)

And the existing options for intervals become booleans for systemd
users, where the intervals are configured by overriding the systemd
timer units apt-daily-download, apt-daily-upgrade, apt-daily-maintenance
instead.

This means systemd systems will have 3 timers with 3 time stamps,
clearly defined behavior when starting the service (always performing
the action), and things will just work in a reasonable way.

This will also allow us to implement retrying on failure efficiently
and generally have a better working solution than now.

-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev
  |  Ubuntu Core Developer |
When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to ('inline').  Thank you.

Bug#861442: unblock: (pre-approval) courier/0.76.3-5

[Niels Thykier]

Control: tags -1 confirmed moreinfo

Markus Wanner:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Dear Release Team,
> 
> only after the freeze, I realized that courier-mta is unmaintained and
> got orphaned a couple moons ago. As I still use and like that MTA, but
> it broke after an upgrade to stretch, I opted to adopt courier and
> continue maintenance (#823807).
> 
> I realize it's pretty late in the process, but I'd appreciate keeping
> courier in stretch. In any case, I plan to continue maintaining the
> package for later releases.
> 
> [...]
> 
> Kind Regards
> 
> Markus Wanner
> 

Ack, please go ahead and remove the moreinfo tag once the upload has
been processed and built on all relevant release architectures.

Should any of these changes turn out to cause issues, please be ready to
revert them.

Thanks,
~Niels

Bug#839575: Tinyca is incompatible with openssl 1.1 and some 1.0.2 versions

[Thomas Viehweger]

Edit:
The working openssl-version 1.02g-2 was not from jessie-backports.
It was from an older stretch version.

Now I tried the current version 1.0.2k-1~bpo8+1 from jessie-backports:
Tinyca hangs with this version, too - when creating a CA.

openssl version 1.0.1t-1+deb8u6 works as expected...

Bug#830671: klavaro: Does not start when locale is FI_fi

[Felipe Castro]

Hi, this is a very tiny bug, and it was difficult to find it! The problem
is the default keyboard indicated for Finnish, it is defined as
"querty_se", but it should be "qwerty_se" (to see the difference, pay
attention to the u ==> w mispelling).

Hope to be fixed from version 3.03, ok?

Felipe Castro



2016-07-10 6:08 GMT-03:00 Tapio Lehtonen :

> Package: klavaro
> Version: 3.01-1
> Severity: normal
> Tags: l10n
>
> Subject: klavaro: Does not start when locale is FI_fi
> Package: klavaro
> Version: 3.01-1
> Severity: normal
> Tags: l10n
>
> Trying to start Klavaro from GUI menu fails. Starting from terminal
> window shows error message:
>
> taleman@yosemitesam:~$ klavaro
>
> ** (klavaro:2915): ERROR **: couldn't open the default keyboard layout:
> [querty_se]
> Jäljitys/katkaisupisteansa
> taleman@yosemitesam:~$ LANG=C klavaro
> ** Message: Empty accuracy log: /home/taleman/.local/share/
> klavaro/accuracy.log_qwerty_us
> ** Message: Empty proficiency log: /home/taleman/.local/share/
> klavaro/proficiency.log_qwerty_us
> ** Message: Empty accuracy log: /home/taleman/.local/share/
> klavaro/accuracy.log_qwerty_se
> ** Message: Empty proficiency log: /home/taleman/.local/share/
> klavaro/proficiency.log_qwerty_se
>
> Adiaux!
> taleman@yosemitesam:~$
>
> This can be fixed with starting klavaro prepending LANG=C to the
> command line. Then change keyboad layout to Swedish and language to
> Finnish. After this Klavaro starts OK from GUI menu and from command line.
>
> By the way, klavaro does not show Finnish keyboard layout in the
> menu. Finnish and Swedish keyboard layouts are exactly the same, so
> copying and renaming would fix this issue.
>
> I suspect this is caused by locale setting, and Klavaro would work OK with
> some other locale.
>
> taleman@yosemitesam:~$ locale
> LANG=fi_FI.UTF-8
> LANGUAGE=
> LC_CTYPE="fi_FI.UTF-8"
> LC_NUMERIC="fi_FI.UTF-8"
> LC_TIME="fi_FI.UTF-8"
> LC_COLLATE="fi_FI.UTF-8"
> LC_MONETARY="fi_FI.UTF-8"
> LC_MESSAGES="fi_FI.UTF-8"
> LC_PAPER="fi_FI.UTF-8"
> LC_NAME="fi_FI.UTF-8"
> LC_ADDRESS="fi_FI.UTF-8"
> LC_TELEPHONE="fi_FI.UTF-8"
> LC_MEASUREMENT="fi_FI.UTF-8"
> LC_IDENTIFICATION="fi_FI.UTF-8"
> LC_ALL=
> taleman@yosemitesam:~$
>
>
> -- System Information:
> Debian Release: 8.5
>   APT prefers stable
>   APT policy: (500, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
> Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages klavaro depends on:
> ii  libatk1.0-0  2.14.0-1
> ii  libc62.19-18+deb8u4
> ii  libcairo-gobject21.14.0-2.1+deb8u1
> ii  libcairo21.14.0-2.1+deb8u1
> ii  libcurl3-gnutls  7.38.0-4+deb8u3
> ii  libgdk-pixbuf2.0-0   2.31.1-2+deb8u5
> ii  libglib2.0-0 2.42.1-1+b1
> ii  libgtk-3-0   3.14.5-1+deb8u1
> ii  libpango-1.0-0   1.36.8-3
> ii  libpangocairo-1.0-0  1.36.8-3
>
> klavaro recommends no packages.
>
> klavaro suggests no packages.
>
> -- no debconf information
>
> -- System Information:
> Debian Release: 8.5
>   APT prefers stable
>   APT policy: (500, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
> Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages klavaro depends on:
> ii  libatk1.0-0  2.14.0-1
> ii  libc62.19-18+deb8u4
> ii  libcairo-gobject21.14.0-2.1+deb8u1
> ii  libcairo21.14.0-2.1+deb8u1
> ii  libcurl3-gnutls  7.38.0-4+deb8u3
> ii  libgdk-pixbuf2.0-0   2.31.1-2+deb8u5
> ii  libglib2.0-0 2.42.1-1+b1
> ii  libgtk-3-0   3.14.5-1+deb8u1
> ii  libpango-1.0-0   1.36.8-3
> ii  libpangocairo-1.0-0  1.36.8-3
>
> klavaro recommends no packages.
>
> klavaro suggests no packages.
>
> -- no debconf information
>
>

Bug#862054: python3-igraph: error when plotting graph inline in jupyter notebook

[Jorge Moraleda]

Package: python3-igraph
Version: 0.7.1.post6-3
Severity: normal

Dear Maintainer,

Attempting to plot within jupyter notebook yields the error:
AttributeError: 'bytes' object has no attribute 'encode'

This code reproduces this bug when typed inside a jupyter notebook:
import igraph
G = igraph.Graph.Erdos_Renyi(100, 0.1);
igraph.plot(G)

This bug agains the python igraph package is discussed in greater detail at 
https://github.com/igraph/python-igraph/issues/88 and was fixed in the 0.7 
release branch of python-igraph that debian includes on August 5, 2016 
(https://github.com/igraph/python-igraph/commit/8864b46849b031a3013764d03e167222963c0f5d)

We should repackage the debian package python3-igraph with a later version 
python igraph that incorporates this fix as plotting is an important component 
of the igraph library. Thank you.

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

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

Versions of packages python3-igraph depends on:
ii  libc6 2.24-10
ii  libigraph0v5  0.7.1-2.1+b2
ii  python3   3.5.3-1
pn  python3:any   

python3-igraph recommends no packages.

python3-igraph suggests no packages.

-- no debconf information

Bug#861112: xsane: always crashes on start

[Aaro Koskinen]

Hi,

On Fri, May 05, 2017 at 08:04:26PM +0200, John Paul Adrian Glaubitz wrote:
> On 05/05/2017 07:16 PM, Aaro Koskinen wrote:
> > I think Jörg Frings-Fürst has analyzed and fixed this bug already - he
> > provided me test packages (libsane_1.0.25-4~test1_amd64.deb etc.) offline
> > for testing and they seemed to fix the issue.
> 
> No, he didn't "fix" the issue. He completely removed a feature from 
> sane-backends
> and called it a fix, assuming that no one in Debian or Ubuntu or any of the 
> derived
> distributions wants to use Avahi with SANE.

Okay...

> > I'm currently away from my machines, but next week I'll recheck the
> > situation again with up-to-date Debian testing, If the problem is still
> > present I will provide the full backtrace etc.
> 
> Yes, please. I am not going to accept such a rather big cut in functionality
> without proper testing and error analysis first.

I found something when enabling debug outputs:

$ SANE_DEBUG_NET=3 scanimage -L
[sanei_debug] Setting debug level of net to 3.
[net] sane_init: authorize != null, version_code != null
[net] net_avahi_init: could not create Avahi client: Daemon not running
[net] net_avahi_init: Avahi init failed, support disabled
[net] sane_init: SANE net backend version 1.0.14 (AF-indep+IPv6) from 
sane-backends 1.0.25
[net] sane_init: Client has little endian byte order
[net] sane_init: searching for config file
scanimage: thread-watch.c:171: avahi_threaded_poll_lock: Assertion `p' failed.
Aborted

It's disabling Avahi support (I don't have such daemon) but still later
calling avahi_threaded_poll_lock() with NULL avahi_thread.

Here's the backtrace:

$ gdb scanimage
GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from scanimage...Reading symbols from 
/usr/lib/debug/.build-id/2a/f2218a71fe370679d900eca9ab1b1e4f575859.debug...done.
done.
(gdb) run -L
Starting program: /usr/bin/scanimage -L
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x76420700 (LWP 6782)]
scanimage: thread-watch.c:171: avahi_threaded_poll_lock: Assertion `p' failed.

Thread 1 "scanimage" received signal SIGABRT, Aborted.
x773c7fcf in raise () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0  0x773c7fcf in raise () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x773c93fa in abort () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x773c0e37 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#3  0x773c0ee2 in __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6
#4  0x70ce9404 in avahi_threaded_poll_lock ()
   from /usr/lib/x86_64-linux-gnu/libavahi-common.so.3
#5  0x7fffeadcac7c in sane_net_init (version_code=, 
authorize=) at net.c:1048
#6  0x77bd4dd0 in init (be=be@entry=0x55762290) at dll.c:614
#7  0x77bd5681 in sane_dll_get_devices (device_list=0x7fffbc18, 
local_only=0) at dll.c:1055
#8  0x62ab in main (argc=2, argv=0x7fffe068)
at scanimage.c:2038

A.

Bug#861736:

[PICCA Frederic-Emmanuel]

activating the NXError reporting we got

filenamenxs.h5 5 
ERROR: cannot open file: filenamenxs.h5
0


and looking for this errormessage,

we found it in the napi5.c file



NXstatus  NX5open(CONSTCHAR *filename, NXaccess am, 
 NXhandle* pHandle)
  {
  hid_t attr1,aid1, aid2, iVID;
  pNexusFile5 pNew = NULL;
  char pBuffer[512];
  char *time_buffer = NULL;
  char version_nr[10];
  unsigned int vers_major, vers_minor, vers_release, am1 ;
  hid_t fapl = -1; 
  int mdc_nelmts;
  size_t rdcc_nelmts;
  size_t rdcc_nbytes;
  double rdcc_w0;
  unsigned hdf5_majnum, hdf5_minnum, hdf5_relnum;

  *pHandle = NULL;

  if (H5get_libversion(_majnum, _minnum, _relnum) < 0)
  {
  NXReportError("ERROR: cannot determine HDF5 library version");
  return NX_ERROR;
  }
  if (hdf5_majnum == 1 && hdf5_minnum < 8)
  {
  NXReportError("ERROR: HDF5 library 1.8.0 or higher required");
  return NX_ERROR;
  }

  /* mask of any options for now */
  am = (NXaccess)(am & NXACCMASK_REMOVEFLAGS);

  /* turn off the automatic HDF error handling */  
  H5Eset_auto(H5E_DEFAULT, NULL, NULL);  
#ifdef USE_FTIME
struct timeb timeb_struct;
#endif 


pNew = (pNexusFile5) malloc (sizeof (NexusFile5));
if (!pNew) {
  NXReportError("ERROR: not enough memory to create file structure");
  return NX_ERROR;
}
memset (pNew, 0, sizeof (NexusFile5));


/* start HDF5 interface */
if (am == NXACC_CREATE5) {  
   fapl = H5Pcreate(H5P_FILE_ACCESS);
   H5Pget_cache(fapl,_nelmts,_nelmts,_nbytes,_w0);
   rdcc_nbytes=(size_t)nx_cacheSize;
   H5Pset_cache(fapl,mdc_nelmts,rdcc_nelmts,rdcc_nbytes,rdcc_w0);
   H5Pset_fclose_degree(fapl,H5F_CLOSE_STRONG);
   am1 = H5F_ACC_TRUNC;
   pNew->iFID = H5Fcreate (filename, am1, H5P_DEFAULT, fapl);
} else {
   if (am == NXACC_READ) {
  am1 = H5F_ACC_RDONLY;
} else {
  am1 = H5F_ACC_RDWR;
}
fapl = H5Pcreate(H5P_FILE_ACCESS);
H5Pset_fclose_degree(fapl,H5F_CLOSE_STRONG);
pNew->iFID = H5Fopen (filename, am1, fapl);
}  
if(fapl != -1) {
  H5Pclose(fapl);
}
if (pNew->iFID <= 0) {
  sprintf (pBuffer, "ERROR: cannot open file: %s", filename);
  NXReportError( pBuffer);
  free (pNew);
  return NX_ERROR;
}

Bug#862052: Latest slim upgrade caused involuntary crashes/logouts...

[Sebastian Rasmussen]

Of course, no problem, but it will have to wait a day or so. I didn't
notice that there was a new version in /unstable or /experimental when I
checked the other day so it is likely fairly recent.

/Sebastian

Bug#862052: Latest slim upgrade caused involuntary crashes/logouts...

[Niels Thykier]

On Mon, 8 May 2017 03:51:45 +0800 Sebastian Rasmussen 
wrote:
> Package: slim
> Version: 1.3.6-5
> Severity: serious
> 
> When upgrading from 1.3.6-4+b2 to 1.3.6-5 of slim I noticed that my
> window manager appeared to suddenly "crash" and logged me out. However
> I had
> not changed anything related to that but I had recently upgraded slim so I
> investigated it a bit.
> 
> I compiled 1.3.6-5 without the fix for 860465 as mentioned in the -5 debian
> patch (but keeping all other additions from -4+b2 to -5 the same). Without
> this "fix" my desktop no longer had problems. Could this be because
> I don't have plymouth installed (whatever that is)? I'm happy to do further
> testing if you can provide something for me to test. Besides this minor
> mishap I'm actually a happy slim user, thanks for putting in the effort. :)
> 
>  / Sebastian
> 
> 

Hi Sebastian,

Sorry to hear you ran into issues with the update.

Could you please try to upgrade to slim/1.3.6-5.1 to see if that fixes
your issue?  It is intended to fix some regressions in the -5 upload.

Thanks,
~Niels

Bug#862053: wordpress: CVE-2017-8295

[Markus Koschany]

Package: wordpress
X-Debbugs-CC: t...@security.debian.org 
secure-testing-t...@lists.alioth.debian.org
Severity: important
Tags: security

Hi,

the following vulnerability was published for wordpress.

CVE-2017-8295[0]:
| WordPress through 4.7.4 relies on the Host HTTP header for a
| password-reset e-mail message, which makes it easier for remote
| attackers to reset arbitrary passwords by making a crafted
| wp-login.php?action=lostpassword request and then arranging for this
| message to bounce or be resent, leading to transmission of the reset
| key to a mailbox on an attacker-controlled SMTP server. This is
| related to problematic use of the SERVER_NAME variable in
| wp-includes/pluggable.php in conjunction with the PHP mail function.
| Exploitation is not achievable in all cases because it requires at
| least one of the following: (1) the attacker can prevent the victim
| from receiving any e-mail messages for an extended period of time
| (such as 5 days), (2) the victim's e-mail system sends an autoresponse
| containing the original message, or (3) the victim manually composes a
| reply containing the original message.

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

No official patch has been published yet but there is an interesting assessment
at 
http://blog.dewhurstsecurity.com/2017/05/04/exploitbox-wordpress-security-advisories.html

I think it makes sense to wait for an official Wordpress response but we could 
also
try to avoid the SERVER_NAME variable in this case.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-8295
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8295

Please adjust the affected versions in the BTS as needed.



signature.asc
Description: OpenPGP digital signature

Bug#862052: Latest slim upgrade caused involuntary crashes/logouts...

[Sebastian Rasmussen]

Package: slim
Version: 1.3.6-5
Severity: serious

When upgrading from 1.3.6-4+b2 to 1.3.6-5 of slim I noticed that my
window manager appeared to suddenly "crash" and logged me out. However
I had
not changed anything related to that but I had recently upgraded slim so I
investigated it a bit.

I compiled 1.3.6-5 without the fix for 860465 as mentioned in the -5 debian
patch (but keeping all other additions from -4+b2 to -5 the same). Without
this "fix" my desktop no longer had problems. Could this be because
I don't have plymouth installed (whatever that is)? I'm happy to do further
testing if you can provide something for me to test. Besides this minor
mishap I'm actually a happy slim user, thanks for putting in the effort. :)

 / Sebastian

Bug#861207: unblock: iso-codes/3.75-1

[Niels Thykier]

Control: tags -1 confirmed moreinfo

On Tue, 25 Apr 2017 22:51:22 +0200 "Dr. Tobias Quathamer"
 wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please unblock package iso-codes
> 
> The package contains updates for some ISO data and quite a few 
> translation updates.
> 
> However, it does not contain any RC bug fixes, so it might not be 
> appropriate for an unblock. It is therefore not yet uploaded to 
> unstable, I'm waiting for your approval.
> 
> unblock iso-codes/3.75-1
> 
> Regards,
> Tobias

Ack, please go ahead and remove the moreinfo tag once the upload is in
unstable and has been built on all relevant release architectures.

Thanks,
~Niels

Bug#861736:

[PICCA Frederic-Emmanuel]

Herethe code ofthismethod

/**/
static NXstatus   NXinternalopen(CONSTCHAR *userfilename, NXaccess am, 
   pFileStack fileStack);
/*--*/
NXstatus   NXopen(CONSTCHAR *userfilename, NXaccess am, NXhandle *gHandle){
  int status;
  pFileStack fileStack = NULL;

  *gHandle = NULL;
  fileStack = makeFileStack();
  if(fileStack == NULL){
NXReportError("ERROR: no memory to create filestack");
  return NX_ERROR;
  }
  status = NXinternalopen(userfilename,am,fileStack);
  if(status == NX_OK){
*gHandle = fileStack;
  }

  return status;


so lets's see the internalopen


static NXstatus   NXinternalopen(CONSTCHAR *userfilename, NXaccess am, 
pFileStack fileStack)
{
return LOCKED_CALL(NXinternalopenImpl(userfilename, am, fileStack));
}



/*---*/
static NXstatus   NXinternalopenImpl(CONSTCHAR *userfilename, NXaccess am, 
pFileStack fileStack)
  {
int hdf_type=0;
int iRet=0;
NXhandle hdf5_handle = NULL;
pNexusFunction fHandle = NULL;
NXstatus retstat = NX_ERROR;
char error[1024];
char *filename = NULL;
int my_am = (am & NXACCMASK_REMOVEFLAGS);

/* configure fortify 
iFortifyScope = Fortify_EnterScope();
Fortify_CheckAllMemory();
*/

/*
  allocate data
*/
fHandle = (pNexusFunction)malloc(sizeof(NexusFunction));
if (fHandle == NULL) {
  NXReportError("ERROR: no memory to create Function structure");
  return NX_ERROR;
}
memset(fHandle, 0, sizeof(NexusFunction)); /* so any functions we miss are 
NULL */
   
/*
  test the strip flag. Elimnate it for the rest of the tests to work
*/
fHandle->stripFlag = 1;
if(am & NXACC_NOSTRIP){
  fHandle->stripFlag = 0;
  am = (NXaccess)(am & ~NXACC_NOSTRIP);
}
fHandle->checkNameSyntax = 0;
if (am & NXACC_CHECKNAMESYNTAX) {
fHandle->checkNameSyntax = 1;
am = (NXaccess)(am & ~NXACC_CHECKNAMESYNTAX);
}


if (my_am==NXACC_CREATE) {
  /* HDF4 will be used ! */
  hdf_type=1;
  filename = strdup(userfilename);
} else if (my_am==NXACC_CREATE4) {
  /* HDF4 will be used ! */
  hdf_type=1;   
  filename = strdup(userfilename);
} else if (my_am==NXACC_CREATE5) {
  /* HDF5 will be used ! */
  hdf_type=2;   
  filename = strdup(userfilename);
} else if (my_am==NXACC_CREATEXML) {
  /* XML will be used ! */
  hdf_type=3;   
  filename = strdup(userfilename);
} else {
  filename = locateNexusFileInPath((char *)userfilename);
  if(filename == NULL){
NXReportError("Out of memory in NeXus-API");
free(fHandle);
return NX_ERROR;
  }
  /* check file type hdf4/hdf5/XML for reading */
  iRet = determineFileType(filename);
  if(iRet < 0) {
snprintf(error,1023,"failed to open %s for reading",
 filename);
NXReportError(error);
free(filename);
return NX_ERROR;
  }
  if(iRet == 0){
snprintf(error,1023,"failed to determine filetype for %s ",
 filename);
NXReportError(error);
free(filename);
free(fHandle);
return NX_ERROR;
  }
  hdf_type = iRet;
}
if(filename == NULL){
NXReportError("Out of memory in NeXus-API");
return NX_ERROR;
}

if (hdf_type==1) {
  /* HDF4 type */
#ifdef HDF4
NXhandle hdf4_handle = NULL;
  retstat = NX4open((const char *)filename,am,_handle);
  if(retstat != NX_OK){
free(fHandle);
free(filename);
return retstat;
  }
  fHandle->pNexusData=hdf4_handle;
  NX4assignFunctions(fHandle);
  pushFileStack(fileStack,fHandle,filename);
#else
  NXReportError(
 "ERROR: Attempt to create HDF4 file when not linked with HDF4");
  retstat = NX_ERROR;
#endif /* HDF4 */
  free(filename);
  return retstat; 
} else if (hdf_type==2) {
  /* HDF5 type */
#ifdef HDF5
  retstat = NX5open(filename,am,_handle);
  if(retstat != NX_OK){
free(fHandle);
free(filename);
return retstat;
  }
  fHandle->pNexusData=hdf5_handle;
  NX5assignFunctions(fHandle);
  pushFileStack(fileStack,fHandle, filename);
#else
  NXReportError(
 "ERROR: Attempt to create HDF5 file when not linked with HDF5");
  retstat = NX_ERROR;
#endif /* HDF5 */
  free(filename);
  return retstat;
} else if(hdf_type == 3){
  /*
XML type
  */
#ifdef NXXML
NXhandle xmlHandle = NULL;
  retstat = NXXopen(filename,am,);
  if(retstat != NX_OK){
free(fHandle);
free(filename);
return retstat;
  }
  fHandle->pNexusData=xmlHandle;
  NXXassignFunctions(fHandle);
  pushFileStack(fileStack,fHandle, 

Bug#833476: mate-screensaver: Screensaver gets tiled under xmonad

[Vlad Orlov]

Hi,

Bug #826636 is now fixed by mate-screensaver 1.16.1-1.
Do you still get this issue with that version?

Bug#861580: (pre-approval) unblock: mysql-connector-python/2.1.6

[Niels Thykier]

Control: tags -1 confirmed moreinfo

Sandro Tosi:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Hello,
> BTS 861511 was reported yesterday against mysql-connector-python stating the 
> new
> upstream version (2.1.6) fixes CVE-2017-3590.
> 
> The upstream versions diff (attached) is quite important, so i would 
> understand
> if you decide not to accept a potential upload of this new version aiming for 
> an
> unblock to strech, but i would still like you to have a look and decide on it.
> 
> Thanks,
> Sandro
> 
> [...]

Ack, please go ahead and remove the moreinfo tag once the upload has
been processed and has been built on all relevant release architectures.

NOTE: the test suite contains certificates that expire in 2018.  If that
causes test failures, then that is an RC bug (as it would mean we would
be unable to compile mysql-connector-python in stretch before its EOL).
AFAICT, said problem would also exists in the current version (except
the expiry reads 2017 instead).
  Please consider replacing the certificates with once that can survive
stretch + stretch-lts's life-time.

Thanks,
~Niels

Bug#861736:

[PICCA Frederic-Emmanuel]

in the napi.h files we saw this.

define CONCAT(__a,__b) __a##__b/* token concatenation */

#ifdef __VMS
#define MANGLE(__arg)   __arg
#else
#define MANGLE(__arg)   CONCAT(__arg,_)
#endif

#define NXopen  MANGLE(nxiopen)

 /**
   * Open a NeXus file.
   * NXopen honours full path file names. But it also searches
   * for files in all the paths given in the NX_LOAD_PATH environment variable.
   * NX_LOAD_PATH is supposed to hold a list of path string separated by the 
platform
   * specific path separator. For unix this is the : , for DOS the ; . Please 
note
   * that crashing on an open NeXus file will result in corrupted data. Only 
after a NXclose
   * or a NXflush will the data file be valid.
   * \param filename The name of the file to open
   * \param access_method The file access method. This can be:
   * \li NXACC__READ read access
   * \li NXACC_RDWR read write access
   * \li NXACC_CREATE, NXACC_CREATE4 create a new HDF-4 NeXus file
   * \li NXACC_CREATE5 create a new HDF-5 NeXus file
   * \li NXACC_CREATEXML create an XML NeXus file.
   * see #NXaccess_mode
   * Support for HDF-4 is deprecated.
   * \param pHandle A file handle which will be initialized upon successfull 
completeion of NXopen.
   * \return NX_OK on success, NX_ERROR in the case of an error.
   * \ingroup c_init
   */
extern  NXstatus  NXopen(CONSTCHAR * filename, NXaccess access_method, 
NXhandle* pHandle);


so we need to check in this method what is going on.

Bug#856690: Wrong Galician translation

[txgvnn]

Dear Santiago Garcia Mantinan

I am sorry for late reply,

The patch has applied to the source repo.
Hope the package will release soon

Thank you for your patch,

Regards,
-- 
Giap Tran 
0xB8E9A6F112C2D7B7

Bug#861889: apt: apt.systemd.daily runs before network comes up

[Julian Andres Klode]

Control: forwarded -1 https://github.com/systemd/systemd/issues/5909

On Sun, May 07, 2017 at 09:14:49PM +0200, Julian Andres Klode wrote:
> Control: reassign -1 systemd
> Control: retitle -1 systemd: network-online.target remains active after resume
> Control: affects -1 apt
> 
> On Sun, May 07, 2017 at 09:09:23PM +0200, Hendrik Tews wrote:
> > 
> > > Note that this only applies on boot. Resume does not work.
> > 
> > What do you mean with "Resume does not work"? I usually wake up
> > my laptop from suspend or hibernate in the morning, then
> > apt.systemd.daily runs before the network comes up. Now and then
> > I reboot the system later, but then the time stamps prevent
> > apt.system.daily from doing anything.
> 
> Once the network has been activated at boot, it is considered
> active for the rest of the uptime, so services won't wait for
> it when resuming the machine.
> 
> If the time stamps prevent apt from doing anything, then
> apt ran successfully and all is well.
> 
> All in all, there's nothing to be done here on the APT
> side, that's a bug (design decision?) in systemd.

Forwarded to systemd upstream.
-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev
  |  Ubuntu Core Developer |
When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to ('inline').  Thank you.

Bug#857573: systemd: Raise network interfaces fails to stop cleanly on shutdown/reboot

[Mike Edwards]

On Fri, May 05, 2017 at 08:31:07AM +0200, Christoph Biedl babbled thus:
> The issues here are pretty similar so I guess it's the same thing: Up to
> and including jessie(sic!), networking wasn't brought down if there is
> something mounted using AoE.

This issue was definitely present in jessie - I discovered it while
building a test machine with jessie and AoE, and it's the reason that I
held off on upgrading my fileserver from wheezy for so long.

I believe the issue was introduced with the changeover to systemd,
which is why I initially opened the bug against systemd, not ifupdown.

In any case, the fix of adding 'no-auto-down' for any interfaces that
serve AoE appears to work well for me.  It's a slight annoyance, but it
means no more hangs on shutdown.

-- 
  
Mike Edwards|   If this email address disappears,   
Unsolicited advertisments to|   assume it was spammed to death.  To
this address are not welcome.   |   reach me in that case, s/-.*@/@/

"Our progress as a nation can be no swifter than our progress in education.
The human mind is our fundamental resource."
  -- John F. Kennedy

Bug#861889: apt: apt.systemd.daily runs before network comes up

[Julian Andres Klode]

Control: reassign -1 systemd
Control: retitle -1 systemd: network-online.target remains active after resume
Control: affects -1 apt

On Sun, May 07, 2017 at 09:09:23PM +0200, Hendrik Tews wrote:
> 
> > Note that this only applies on boot. Resume does not work.
> 
> What do you mean with "Resume does not work"? I usually wake up
> my laptop from suspend or hibernate in the morning, then
> apt.systemd.daily runs before the network comes up. Now and then
> I reboot the system later, but then the time stamps prevent
> apt.system.daily from doing anything.

Once the network has been activated at boot, it is considered
active for the rest of the uptime, so services won't wait for
it when resuming the machine.

If the time stamps prevent apt from doing anything, then
apt ran successfully and all is well.

All in all, there's nothing to be done here on the APT
side, that's a bug (design decision?) in systemd.

> 
> > You could look at 
> >
> >  /var/lib/systemd/deb-systemd-helper-enabled/network-online.target.wants/
> >  /{usr/,}lib/systemd/system/network-online.target.wants/ 
> >  /etc/systemd/system/network-online.target.wants
> 
> I have the first and the last and they both contain files
> networking.service and NetworkManager-wait-online.service and I
> use NetworkManager.

Great, then everything works fine.
-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev
  |  Ubuntu Core Developer |
When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to ('inline').  Thank you.

Bug#861761: unblock: (pre-approval) offlineimap/7.0.14+dfsg1-2

[Niels Thykier]

Control: tags -1 confirmed moreinfo

Ilias Tsitsimpis:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Dear Release Team,
> 
> One of the UIs for OfflineIMAP, namely Blinkenlights, is broken in the
> current version of OfflineIMAP. More specifically, the output of
> Blinkenlights becomes "garbled" and eventually results in a crash of the
> Python process. For more information, see the upstream bug report:
> 
> https://github.com/OfflineIMAP/offlineimap/issues/160
> 
> This has been broken for more than a year, but only recently fixed.
> Since the patch is fairly small, and users have already complained about
> this in the past[1], I would like to update OfflineIMAP to fix this bug.
> What do you think?
> 
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809676#31
> 
> unblock offlineimap/7.0.14+dfsg1-2
> 
> Kind Regards,
> 

Ack, please go ahead and remove the moreinfo tag once the upload has
been ACCEPT'ed + built on all relevant release architectures.

Thanks,
~Niels

Bug#862051: nodejs-legacy: possibly drop this package, now that ax25-node has been removed?

[James Lu]

Package: nodejs-legacy
Version: 4.8.2~dfsg-1
Severity: wishlist

Hi maintainers,

Back in 2015, ax25-node (and the "node" package following) were removed citing
lack of activity:
https://packages.qa.debian.org/n/node/news/20150915T000109Z.html

Would it be possible to drop nodejs-legacy in the next Debian release and
rename nodejs back to node? IMO doing so would make working with JS programs
outside of Debian a lot easier.

Best,
James



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

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

Versions of packages nodejs-legacy depends on:
ii  nodejs  4.8.2~dfsg-1

nodejs-legacy recommends no packages.

nodejs-legacy suggests no packages.

-- no debconf information

Bug#861889: apt: apt.systemd.daily runs before network comes up

[Hendrik Tews]

> Note that this only applies on boot. Resume does not work.

What do you mean with "Resume does not work"? I usually wake up
my laptop from suspend or hibernate in the morning, then
apt.systemd.daily runs before the network comes up. Now and then
I reboot the system later, but then the time stamps prevent
apt.system.daily from doing anything.

> You could look at 
>
>  /var/lib/systemd/deb-systemd-helper-enabled/network-online.target.wants/
>  /{usr/,}lib/systemd/system/network-online.target.wants/ 
>  /etc/systemd/system/network-online.target.wants

I have the first and the last and they both contain files
networking.service and NetworkManager-wait-online.service and I
use NetworkManager.

Thanks,

Hendrik

Bug#824607: Bug #824607: pam: diff for NMU version 1.1.8-3.3

[Steve Langasek]

Control: reopen 824607

On Sun, May 07, 2017 at 02:04:12PM -0400, Nicolas Braud-Santoni wrote:
> Hi,

> This NMU landed in sid on 2016-06-02, I think we can close the bug  ;)

The purpose of having bugs for the NMU diff is so that they are readily
findable until the maintainer acks them...

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#862050: New upstream bugfix release 25.2 available

[Rob Browning]

Dato Simó  writes:

> It would be nice to have it available on unstable.

I haven't finished packaging it yet, but when I do, it'll probably need
to go into experimental until stretch is released.

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Bug#861957: closed by Joachim Breitner <nome...@debian.org> (Re: Bug#861976: libghc-glut-dev: attempts to load libglut.so instead of libglut.so.3)

[Adrian Bunk]

Control: reassign -1 libghc-glut-dev 2.7.0.10-3
Control: fixed -1 2.7.0.10-4
Control: affects -1 src:raincat

On Sun, May 07, 2017 at 01:51:04PM +, Debian Bug Tracking System wrote:
>...
> With haskell-glut 2.7.0.10-4 this should be fixed in unstable.

I am reassigning it so that version tracking covers this.

I'd guess raincat might additionally need a binNMU?

> https://packages.qa.debian.org/h/haskell-glut.html
> does not tell me yet whether it will migrate to testing automatically
> or not.

Due to the freeze, there is no automatic testing migration since 
February 5th.

Please file an unblock request.

> Greetings,
> Joachim

cu
Adrian

-- 

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

Bug#861263: debian-installer: zfs support

[Steve McIntyre]

On Sun, May 07, 2017 at 06:44:11PM +0100, Sam Kuper wrote:
>On 05/05/2017, Sam Kuper  wrote:
>> Bill McGrath's request matches my suggestion above[3],
>> and Neil McGovern's reply suggests it is already on Debian's roadmap.
>> Why, then, is this bug (Bug#861263) marked as wontfix?
>>
>> [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861263#17
>
>In the light of this, and of the paths forward described above, please
>can I reiterate my earlier request for the "wontfix" label to be
>removed? Even if it takes years for ZFS support to be added to the
>Debian Installer, it would be worthwhile.
>
>Failing that, it would be good to have an explanation of why ZFS will
>*never* be supported in the Debian Installer.

While there might be a way to do this work technically, it's probably
fair to say that none of the existing maintainers have any plans to
work on it. It would need massive effort, and there's no sign of those
maintainers showing any interest in doing it. That sounds like a
reasonable description of "wontfix" to me.

If somebody was actually working on patches, that might change the
situation.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Is there anybody out there?

Bug#862050: New upstream bugfix release 25.2 available

[Dato Simó]

Source: emacs25
Version: 25.1+1-4

Emacs 25.2 was released on April 22nd:

[https://lists.gnu.org/archive/html/info-gnu/2017-04/msg9.html]

It would be nice to have it available on unstable.

-d

Bug#861681: unblock: tomcat8/8.5.14-1

[Niels Thykier]

Control: tags -1 confirmed moreinfo

Emmanuel Bourg:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Hi,
> 
> This is a pre-upload request to update tomcat8 to the version 8.5.14-1
> in stretch. This version is mostly a bug fix release, it also integrates
> the fixes for 3 vulnerabilities (CVE-2017-5647, CVE-2017-5650,
> CVE-2017-5651).
> 
> The full changelog is available here:
> 
> http://tomcat.apache.org/tomcat-8.5-doc/changelog.html#Tomcat_8.5.14_(markt)
> 
> Backporting security fixes to the stable version of Tomcat has proven
> to be a bit tedious in the past, so it would be appreciable to have
> a version as fresh as possible in stretch to ease the maintenance work
> on the long term.
> 
> Thank you,
> 
> Emmanuel Bourg
> 

ASSUMING that nothing in Debian stretch relies on the servlet4 preview
parts, then ack, please go ahead.  Please remove the moreinfo tag once
the upload has been processed.

Thanks,
~Niels

Bug#861707: unblock: mysql-connector-java/5.1.42-1

[Niels Thykier]

Control: tags -1 confirmed moreinfo

Emmanuel Bourg:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Hi,
> 
> This is a pre-upload request to update the mysql-connector-java package
> to the version 5.1.42-1 in stretch. This update is required to fix two
> vulnerabilities (CVE-2017-3586 and CVE-2017-3589). Upstream hasn't
> provided enough information to patch only the vulnerabilities, but the
> branch 5.1.x is in maintenance mode, well tested and stable.
> 
> The detailed changelog is available here:
> 
> https://dev.mysql.com/doc/relnotes/connector-j/5.1/en/news-5-1-42.html
> 
> Thank you,
> 
> Emmanuel Bourg
> 
> unblock mysql-connector-java/5.1.42-1
> 

Ack, please go ahead and remove the moreinfo tag once the upload has
been accepted.

Thanks,
~Niels

Bug#862048: lesspipe: Submission: Support for .whl and .egg files

[John T. Wodder II]

Package: less
Version: 481-2.1ubuntu0.1
Severity: wishlist

Dear Maintainer,

Enclosed below are recipes from my ~/.lessfilter for viewing .whl and .egg
files in less(1) which I hope will be of general use and worthy of inclusion in
lesspipe.

The wheel (.whl) format and its predecessor the egg (.egg) are the official
built-package formats for the Python programming language.  Both formats are
implemented as zipfiles containing a directory of metadata alongside the actual
Python files.  My recipes (in imitation of lesspipe's .deb recipe) display the
primary metadata file, a blank line, and the list of files in the zipfile.  The
primary metadata includes the package's entire README, which is frequently very
long, and so I have inserted sed(1) commands to remove this field.

If you need egg and/or wheel files to test against, I would direct you to
possibly the most popular Python project that still provides both:


*.egg)
if [ -x "`which unzip`" ]; then
unzip -p "$1" EGG-INFO/PKG-INFO | \
sed '/^Description:/,/^\S/{/^Description:/d; /^\S/b; d}'
echo
unzip -v "$1"
else
echo "No unzip available"
fi
;;

*.whl)
if [ -x "`which unzip`" ]; then
unzip -p "$1" '*.dist-info/METADATA' | sed '/^$/q'
unzip -v "$1"
else
echo "No unzip available"
fi
;;

-- John Wodder


-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages less depends on:
ii  debianutils  4.7
ii  libc62.23-0ubuntu7
ii  libtinfo56.0+20160213-1ubuntu1

less recommends no packages.

less suggests no packages.

-- no debconf information

Bug#862046: xwindows crashes on startup of some programs.

[Kenneth Howlett]

Package: xserver-xorg-video-nouveau
Version: 1:1.0.13-3

Dear Maintainer,

I am running stretch in multiuser mode, starting xwindows with startx.  I am
using xfce.  Simple programs and programs using minimal graphics seem to run
ok.  For some programs, xwindows crashes when the program starts.

run glxgears
glxgears window appears, remains black. computer no longer responds to 
keyboard or mouse.

Reboot. Check /var/log/kern.log, /var/log/messages, /var/log/syslog.
kern.log says: May  6 14:43:09 hpx2 kernel: [  233.822647] nouveau 
:00:0d.0: bus: MMIO write of 02670001 FAULT at 00b010
mesages says: May  6 14:44:30 hpx2 liblogging-stdlog:  [origin 
software="rsyslogd" swVersion="8.24.0" x-pid="507" 
x-info="http://www.rsyslog.com;] rsyslogd was HUPed


run synaptic
No window opens. Xwindows responds normally to mouse movements. Xwindows 
does not respond to mouse clicks. Change virtual terminals works.

From different virtual terminal, do killall Xorg.
Computer no longer responds to keyboard or mouse.
Reboot. Nothing in /var/log/kern.log, /var/log/messages, /var/log/syslog.

run firefox
display looks weird. computer no longer responds to keyboard or mouse.
Reboot. Check /var/log/kern.log, /var/log/messages, /var/log/syslog. 
Only related message is:
May  7 08:27:28 hpx2 org.a11y.atspi.Registry[1259]: XIO:  fatal IO error 
11 (Resource temporarily unavailable) on X server ":0"
May  7 08:27:28 hpx2 org.a11y.atspi.Registry[1259]:   after 1863 
requests (1863 known processed) with 0 events remaining.


I tried glxgears a second time, and it crashed the same as before. I tried
synaptic a second time, and it crashed like before, except this time
multiuser mode worked normally after doing killall Xorg.  I tried firefox a
second time, and firefox ran normally.

I tried switching to icewm and tried glxgears a third time, and it crashed
the same as before.

Glxgears, synaptic, and firefox work if I use the nvidia-legacy-304xx driver
instead of the nouveau driver.


-- Package-specific info:
/etc/X11/X does not exist.
/etc/X11/X is not a symlink.
/etc/X11/X is not executable.

VGA-compatible devices on PCI bus:
--
00:0d.0 VGA compatible controller [0300]: NVIDIA Corporation C61 
[GeForce 6150SE nForce 430] [10de:03d0] (rev a2)


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

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

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

Kernel version (/proc/version):
---
Linux version 4.9.0-2-amd64 (debian-ker...@lists.debian.org) (gcc 
version 6.3.0 20170321 (Debian 6.3.0-11) ) #1 SMP Debian 4.9.18-1 
(2017-03-30)


Xorg X server log files on system:
--
-rw-r--r-- 1 k k 25421 May  7 11:18 /home/k/.local/share/xorg/Xorg.0.log

Contents of most recent Xorg X server log file 
(/home/k/.local/share/xorg/Xorg.0.log):

--
[27.859]
X.Org X Server 1.19.2
Release Date: 2017-03-02
[27.859] X Protocol Version 11, Revision 0
[27.859] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[27.859] Current Operating System: Linux hpx2 4.9.0-2-amd64 #1 SMP 
Debian 4.9.18-1 (2017-03-30) x86_64
[27.859] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-2-amd64 
root=UUID=83b04634-5534-4c3f-9a8e-d38d43b453d8 ro quiet 
systemd.unit=multi-user.target 
drm_kms_helper.edid_firmware=edid/1680x1050.bin

[27.860] Build Date: 03 March 2017  03:14:41PM
[27.860] xorg-server 2:1.19.2-1 (https://www.debian.org/support)
[27.860] Current version of pixman: 0.34.0
[27.860] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[27.860] Markers: (--) probed, (**) from config file, (==) default 
setting,

(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[27.860] (==) Log file: "/home/k/.local/share/xorg/Xorg.0.log", 
Time: Sun May  7 11:15:14 2017

[27.876] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[27.894] (==) No Layout section.  Using the first Screen section.
[27.894] (==) No screen section available. Using defaults.
[27.894] (**) |-->Screen "Default Screen Section" (0)
[27.895] (**) |   |-->Monitor ""
[27.896] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[27.896] (==) Automatically adding devices
[27.896] (==) Automatically enabling devices
[27.896] (==) Automatically adding GPU devices
[27.896] (==) Max clients allowed: 256, resource mask: 0x1f
[27.925] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not 
exist.

[27.925] Entry deleted from font path.
[28.008] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,

Bug#862045: xwindows runs slow and crashes frequently

[Kenneth Howlett]

Package: gnome-session
Version: 3.22.3-1

Dear Maintainer,

I boot into multiuser mode. I start xwindows with startx.  Xwindows starts
ok, and I can start a program.  Simple programs start ok; complex programs
are still starting up several minutes later.  Once a program starts,
xwindows becomes barely responsive.  The cursor on the screen moves as I
move the mouse, but it takes a long time to respond to mouse clicks.  After
the first few mouse clicks, it seems to stop responding to mouse clicks, or
maybe it takes longer than I was willing to wait for.

Xwindows crashes frequently, especially when I change virtual terminals.
When xwindows crashes, xwindows exits to the terminal where I ran startx.
Multiuser mode works normally.  I can run startx again, with the same
result.

Xwindows works ok if I use update-alternatives to change x-session-manager
from gnome-session to startxfce4.

I am using the nvidia-legacy-304xx driver.  Gnome-session works ok if I use
the nouveau driver instead.

display controller (from lspci):
00:0d.0 VGA compatible controller [0300]: nVidia Corporation C61 
[GeForce 6150SE nForce 430] [10de:03d0] (rev a2)

Subsystem: Hewlett-Packard Company Device [103c:2a58]

Here are some logs from startx to crash:

/var/log/kern.log:
May  4 16:56:06 hpx2 gnome-keyring-d[3615]: couldn't access control 
socket: /run/user/1000/keyring/control: No such file or directory
May  4 16:56:06 hpx2 gnome-keyring-d[3616]: couldn't access control 
socket: /run/user/1000/keyring/control: No such file or directory
May  4 16:56:06 hpx2 gnome-keyring-d[3617]: couldn't access control 
socket: /run/user/1000/keyring/control: No such file or directory
May  4 16:56:09 hpx2 gnome-shell[3625]: JS LOG: Failed to launch 
ibus-daemon: Failed to execute child process "ibus-daemon" (No such file 
or directory)
May  4 16:56:13 hpx2 gnome-settings-[3653]: g_task_return_error: 
assertion 'error != NULL' failed

May  4 16:56:13 hpx2 gnome-session-binary[3555]: Entering running state
May  4 16:56:14 hpx2 kernel: [30824.936903] NVRM: Xid (PCI::00:0d): 
1, Channel 0002 Method 0060 Data beef0233
May  4 16:56:15 hpx2 gnome-shell[3625]: GNOME Shell started at Thu May 
04 2017 16:56:10 GMT-0400 (EDT)
May  4 16:57:03 hpx2 kernel: [30873.451302] NVRM: Xid (PCI::00:0d): 
1, Channel 0002 Method 0060 Data beef0233
May  4 16:57:03 hpx2 kernel: [30873.503328] NVRM: Xid (PCI::00:0d): 
1, Channel 0002 Method 0060 Data beef0233
May  4 16:57:05 hpx2 kernel: [30875.479536] NVRM: Xid (PCI::00:0d): 
1, Channel 0002 Method 0060 Data beef0233
May  4 16:57:08 hpx2 kernel: [30878.445029] NVRM: Xid (PCI::00:0d): 
1, Channel 0002 Method 0060 Data beef0233
May  4 16:57:17 hpx2 kernel: [30887.838224] NVRM: Xid (PCI::00:0d): 
1, Channel 0002 Method 0060 Data beef0233
May  4 16:57:17 hpx2 kernel: [30887.870815] traps: gnome-shell[3625] 
trap int3 ip:7fbc5db9a261 sp:7ffeaf26a170 error:0
May  4 16:57:17 hpx2 kernel: [30887.870829]  in 
libglib-2.0.so.0.5000.3[7fbc5db4a000+112000]
May  4 16:57:19 hpx2 gnome-shell[3855]: JS LOG: Failed to launch 
ibus-daemon: Failed to execute child process "ibus-daemon" (No such file 
or directory)
May  4 16:57:33 hpx2 kernel: [30903.680408] NVRM: Xid (PCI::00:0d): 
13, 001e 3141590c 0019 0104 9e09 0002
May  4 16:57:33 hpx2 kernel: [30903.684836] NVRM: Xid (PCI::00:0d): 
9, Channel 0020 Instance  Intr 0010
May  4 16:57:33 hpx2 kernel: [30903.688140] NVRM: Xid (PCI::00:0d): 
9, Channel 0020 Instance  Intr 0010
May  4 16:57:37 hpx2 gnome-shell[3855]: 
clutter_input_device_get_device_id: assertion 'CLUTTER_IS_INPUT_DEVICE 
(device)' failed
May  4 16:57:37 hpx2 gnome-shell[3855]: 
clutter_input_device_get_device_id: assertion 'CLUTTER_IS_INPUT_DEVICE 
(device)' failed
May  4 16:57:37 hpx2 gnome-shell[3855]: 
clutter_input_device_get_device_id: assertion 'CLUTTER_IS_INPUT_DEVICE 
(device)' failed
May  4 16:57:37 hpx2 gnome-shell[3855]: 
clutter_input_device_get_device_id: assertion 'CLUTTER_IS_INPUT_DEVICE 
(device)' failed
May  4 16:57:37 hpx2 gnome-shell[3855]: 
clutter_input_device_get_device_id: assertion 'CLUTTER_IS_INPUT_DEVICE 
(device)' failed
May  4 16:57:37 hpx2 gnome-shell[3855]: 
clutter_input_device_get_device_id: assertion 'CLUTTER_IS_INPUT_DEVICE 
(device)' failed
May  4 16:57:37 hpx2 gnome-shell[3855]: 
clutter_input_device_get_device_id: assertion 'CLUTTER_IS_INPUT_DEVICE 
(device)' failed
May  4 16:57:37 hpx2 gnome-shell[3855]: 
clutter_input_device_get_device_id: assertion 'CLUTTER_IS_INPUT_DEVICE 
(device)' failed
May  4 16:57:37 hpx2 gnome-shell[3855]: 
clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE 
(device)' failed
May  4 16:57:38 hpx2 gnome-shell[3855]: GNOME Shell started at Thu May 
04 2017 16:57:19 GMT-0400 (EDT)
May  4 16:57:39 hpx2 kernel: [30909.532837] traps: gnome-shell[3855] 
trap int3 ip:7fdea7401261 sp:7ffc47d18680 error:0
May  4 

Bug#861263: debian-installer: zfs support

[Sam Kuper]

On 05/05/2017, Sam Kuper  wrote:
> Bill McGrath's request matches my suggestion above[3],
> and Neil McGovern's reply suggests it is already on Debian's roadmap.
> Why, then, is this bug (Bug#861263) marked as wontfix?
>
> [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861263#17

In the light of this, and of the paths forward described above, please
can I reiterate my earlier request for the "wontfix" label to be
removed? Even if it takes years for ZFS support to be added to the
Debian Installer, it would be worthwhile.

Failing that, it would be good to have an explanation of why ZFS will
*never* be supported in the Debian Installer.

Thanks :)

Bug#660298: Debian Reference --- adding pdf support apparently now possible?

[Holger Wansing]

Hi,

Osamu Aoki  wrote:
> Above mentioned problem of installation-guide way can be fixed by moving
> out following from  
> 
> \setmainfont{FreeSerif}
> \setsansfont{FreeSans}
> \setmonofont{FreeMono}

Your concept in the xetex_param.xsl looks weird to me, to be honest:



if lang=zh: 

if lang=ja: 

otherwise: 


Why having nothing in otherwise???



> So installation-guide seems better choice as baseline.  My concern is
> that GNU Free fonts is not as easy to distinguish O and 0.  I will try
> both to check how they come out.
> 
> Also, I remember CJ people like SanSerif for their main text of the CJK
> character.
> 
> As for pt, I think I need to do divide and find to the offending string
> in PT PO file.  If I reset PT into no PO string, it creates proper PDF.
> This needs a bit more work.
> 
> Other problem is "-mark.  It used to look ``...'' but now ''...''.

I have already looked into the pt problem today.
It looks like a dblatex bug to me:
if there is a \" at the end of a string, and the string is from type
, it fails to build. The quotation mark is not correctly escaped
apparently.

Attached you will find a patch against the pt.po file, which makes the pt
language build PDF variant correctly. My way was, to change " quotation marks
into ' ones. 
(My main point for preparing this patch was to find out what's going wrong.
It's probably not the solution, to apply the patch and that's it. The 
portuguese translator may change such quotation marks later, and then it
breaks again.)

BTW: I wonder why this is only a problem with portuguese, it's no problem in
german for example...



Regards
Holger


-- 
Holger Wansing 
PGP-Finterprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076
--- pt.po	2017-05-07 07:35:08.684359583 +0200
+++ pt_workingcopy.po	2017-05-07 09:12:37.678325954 +0200
@@ -4079,7 +4079,7 @@
 
 #. type: Content of: 
 msgid "List of the first character of \"ls -l\" output"
-msgstr "Lista do primeiro caractere da saída de \"ls -l\""
+msgstr "Lista do primeiro caractere da saída de 'ls -l'"
 
 #. type: Content of: 
 msgid "character"
@@ -6439,7 +6439,7 @@
 
 #. type: Content of: 
 msgid "The \"$LANG\" variable"
-msgstr "A variável \"$LANG\""
+msgstr "A variável '$LANG'"
 
 #. type: Content of: 
 msgid "The full locale value given to \"$LANG\" variable consists of 3 parts: \"xx_YY.\"."
@@ -6696,7 +6696,7 @@
 
 #. type: Content of: 
 msgid "The \"$PATH\" variable"
-msgstr "A variável \"$PATH\""
+msgstr "A variável '$PATH'"
 
 #. type: Content of: 
 msgid "When you type a command into the shell, the shell searches the command in the list of directories contained in the \"$PATH\" environment variable.  The value of the \"$PATH\" environment variable is also called the shell's search path."
@@ -6712,7 +6712,7 @@
 
 #. type: Content of: 
 msgid "The \"$HOME\" variable"
-msgstr "A variável \"$HOME\""
+msgstr "A variável '$HOME'"
 
 #. type: Content of: 
 msgid "Many commands stores user specific configuration in the home directory and changes their behavior by their contents.  The home directory is identified by the environment variable \"$HOME\"."
@@ -6720,7 +6720,7 @@
 
 #. type: Content of: 
 msgid "List of \"$HOME\" values"
-msgstr "Lista de valores \"$HOME\""
+msgstr "Lista de valores '$HOME'"
 
 #. type: Content of: 
 msgid "value of \"$HOME\""
@@ -11962,7 +11962,7 @@
 
 #. type: Content of: 
 msgid "Blocking packages installed by \"Recommends\""
-msgstr "Bloquear pacotes instalados por \"Recomendados\""
+msgstr "Bloquear pacotes instalados por 'Recomendados'"
 
 #. type: Content of: 
 msgid "If you wish not to pull in particular packages automatically by \"Recommends\", you must create the \"/etc/apt/preferences\" file and explicitly list all those packages at the top of it as the following."
@@ -13887,7 +13887,7 @@
 
 #. type: Content of: 
 msgid "The second entry content of \"/etc/passwd\""
-msgstr "A segunda entrada no conteúdo de \"/etc/passwd\""
+msgstr "A segunda entrada no conteúdo de '/etc/passwd'"
 
 #. type: Content of: 
 msgid "(empty)"
@@ -14401,7 +14401,7 @@
 
 #. type: Content of: 
 msgid "\"Why GNU su does not support the wheel group\""
-msgstr "\"Porque o su do GNU não suporta o grupo wheel\""
+msgstr "'Porque o su do GNU não suporta o grupo wheel'"
 
 #. type: Content of: 
 msgid "This is the famous phrase at the bottom of the old \"info su\" page by Richard M. Stallman.  Not to worry: the current su command in Debian uses PAM, so that one can restrict the ability to use su to the root group by enabling the line with \"pam_wheel.so\" in \"/etc/pam.d/su\"."
@@ -16017,7 +16017,7 @@
 
 #. type: Content of: 
 msgid "The basic syntax of \"/etc/network/interfaces\""
-msgstr "A sintaxe básica de \"/etc/network/interfaces\""
+msgstr "A sintaxe básica de '/etc/network/interfaces'"
 
 #. type: Content of: 
 msgid "The key syntax of \"/etc/network/interfaces\" as explained in interfaces5 can be 

Bug#862044: unblock: strip-nondeterminism/0.033-1

[Chris Lamb]

Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Release Team,

Please consider unblocking strip-nondetermism 0.033-1. This is mostly
to:

 a) Enable logging so we can start to remove this ugly hack by looking
at build logs. (#862031)

 b) Update the package description so that people do not start relying on
the tool for similar reasons. (#862029)


The relevant changelog entry is:

strip-nondeterminism (0.033-1) unstable; urgency=medium

  [ Chris Lamb ]
  * Move from verbose_print to nonquiet_print so we print when normalising a
file. This is so we can start to target the removal of
strip-nondeterminism itself. (Closes: #862031)
  * Update package long descriptions to clarify that this tool is a temporary
workaround. (Closes: #862029)
  * Include the filename when testing failure fixtures.

  [ Bernhard M. Wiedemann ]
  * Only call get_normalizer_by_name once
  * Make get_normalizer_by_name O(1)

 -- Chris Lamb   Sun, 07 May 2017 19:32:19 +0200

The full debdiff is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diffstat for strip-nondeterminism-0.032 strip-nondeterminism-0.033

 bin/dh_strip_nondeterminism |2 -
 bin/strip-nondeterminism|   13 +
 debian/changelog|   16 +++
 debian/control  |   55 +++-
 lib/File/StripNondeterminism.pm |   32 +--
 t/failures.t|2 -
 6 files changed, 70 insertions(+), 50 deletions(-)

diff -Nru strip-nondeterminism-0.032/bin/dh_strip_nondeterminism 
strip-nondeterminism-0.033/bin/dh_strip_nondeterminism
--- strip-nondeterminism-0.032/bin/dh_strip_nondeterminism  2017-03-17 
09:25:00.0 +0100
+++ strip-nondeterminism-0.033/bin/dh_strip_nondeterminism  2017-05-07 
19:31:07.0 +0200
@@ -83,7 +83,7 @@
 
foreach (@nondeterministic_files) {
my ($path, $normalize) = @$_;
-   verbose_print("Normalizing $path");
+   nonquiet_print("Normalizing $path");
eval { $normalize->($path); 1 }
  or error("$path: $@");
}
diff -Nru strip-nondeterminism-0.032/bin/strip-nondeterminism 
strip-nondeterminism-0.033/bin/strip-nondeterminism
--- strip-nondeterminism-0.032/bin/strip-nondeterminism 2017-03-17 
09:25:00.0 +0100
+++ strip-nondeterminism-0.033/bin/strip-nondeterminism 2017-05-07 
19:31:07.0 +0200
@@ -60,15 +60,16 @@
 
 die $usage if @ARGV == 0;
 
+my $normalizer;
+if (defined $filetype) {
+   $normalizer
+ = File::StripNondeterminism::get_normalizer_by_name($filetype);
+   die "$filetype: Unknown file type\n" unless $normalizer;
+}
 for my $filename (@ARGV) {
die "$filename: Does not exist\n" unless -e $filename;
 
-   my $normalizer;
-   if (defined $filetype) {
-   $normalizer
- = 
File::StripNondeterminism::get_normalizer_by_name($filetype);
-   die "$filetype: Unknown file type\n" unless $normalizer;
-   } else {
+   if (!defined $filetype) {
$normalizer
  = 
File::StripNondeterminism::get_normalizer_for_file($filename);
next unless $normalizer;
diff -Nru strip-nondeterminism-0.032/debian/changelog 
strip-nondeterminism-0.033/debian/changelog
--- strip-nondeterminism-0.032/debian/changelog 2017-03-17 09:25:53.0 
+0100
+++ strip-nondeterminism-0.033/debian/changelog 2017-05-07 19:32:19.0 
+0200
@@ -1,3 +1,19 @@
+strip-nondeterminism (0.033-1) unstable; urgency=medium
+
+  [ Chris Lamb ]
+  * Move from verbose_print to nonquiet_print so we print when normalising a
+file. This is so we can start to target the removal of
+strip-nondeterminism itself. (Closes: #862031)
+  * Update package long descriptions to clarify that this tool is a temporary
+workaround. (Closes: #862029)
+  * Include the filename when testing failure fixtures.
+
+  [ Bernhard M. Wiedemann ]
+  * Only call get_normalizer_by_name once
+  * Make get_normalizer_by_name O(1)
+
+ -- Chris Lamb   Sun, 07 May 2017 19:32:19 +0200
+
 strip-nondeterminism (0.032-1) unstable; urgency=medium
 
   * Add support for testing files we should reject.
diff -Nru strip-nondeterminism-0.032/debian/control 
strip-nondeterminism-0.033/debian/control
--- strip-nondeterminism-0.032/debian/control   2017-03-17 09:25:53.0 
+0100
+++ strip-nondeterminism-0.033/debian/control   2017-05-07 19:32:19.0 
+0200
@@ -26,13 +26,16 @@
  ${misc:Depends},
  ${perl:Depends},
 Description: file non-deterministic information stripper — Perl module
- StripNondeterminism is a library for stripping non-deterministic
- information, such as timestamps and file system order, from files. It
- 

Bug#861889: apt: apt.systemd.daily runs before network comes up

[Julian Andres Klode]

On Sun, May 07, 2017 at 11:28:31AM +0200, Hendrik Tews wrote:
> Julian,
> 
> thanks a lot for you quick answer.
> 
> > Check that your network-online target actually ensures that the
> > network is up. (the service might want to depend on that as
> 
> I have no idea how to check this. Could you point me to a
> relevant HowTo?

You could look at 

 /var/lib/systemd/deb-systemd-helper-enabled/network-online.target.wants/
 /{usr/,}lib/systemd/system/network-online.target.wants/ 
 /etc/systemd/system/network-online.target.wants

to see if it contains your network managing wait service unit. You
should find one of these there:

NetworkManager-wait-online.service   for NetworkManager
systemd-networkd-wait-online.service for systemd-resolved
networking.service   for ifupdown

If not, you might have to enable the service with systemctl
enable. If you use other tools to manage your network figure
out yourself if they are part of network-online.target

Note that this only applies on boot. Resume does not work.

-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev
  |  Ubuntu Core Developer |
When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to ('inline').  Thank you.

Bug#862043: unblock: fwsnort/1.6.5-3

[Axel Beckert]

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

Please unblock package fwsnort 1.6.5-3.

It fixes two bug reports (1 RC, 1 important) and fixes the DEP-5
debian/copyright syntax (lintian warning
dep5-copyright-license-name-not-unique).

My patch for the RC bug already has been accepted upstream and
triggered a new upstream release (1.6.7).

Additionally it contains the following changes:

* Adding a debian/gbp.conf to declare the non-standard git branch
  being used. This should be a no-op for building the package from
  source, but fixes building the package from git.

* Updating Vcs-Git to declare the non-standard branch, too.

* Update the Maintainer field as the package has been orphaned due to
  Franck Joncourt's retirement.

diff -Nru fwsnort-1.6.5/debian/changelog fwsnort-1.6.5/debian/changelog
--- fwsnort-1.6.5/debian/changelog  2014-08-30 19:11:55.0 +0200
+++ fwsnort-1.6.5/debian/changelog  2017-05-07 11:47:15.0 +0200
@@ -1,3 +1,23 @@
+fwsnort (1.6.5-3) unstable; urgency=medium
+
+  * QA upload.
+  * Remove all fwsnort generated firewall rules upon purge.
+(Closes: #861999)
+  * Fix debian/copyright syntax by using a separate License stanza.
+
+ -- Axel Beckert   Sun, 07 May 2017 11:47:15 +0200
+
+fwsnort (1.6.5-2) unstable; urgency=medium
+
+  * Orphan the package. (See #831274.)
++ Set Maintainer to Debian QA Group.
+  * Add a debian/gbp.conf and "-b debian" to Vcs-Git to reflect the git
+repository layout.
+  * Add patch to also remove square brackets from single port definitions.
+(Closes: #860164)
+
+ -- Axel Beckert   Sat, 06 May 2017 16:17:38 +0200
+
 fwsnort (1.6.5-1) unstable; urgency=low
 
   * Imported Upstream version 1.6.5
diff -Nru fwsnort-1.6.5/debian/control fwsnort-1.6.5/debian/control
--- fwsnort-1.6.5/debian/control2014-08-30 19:11:55.0 +0200
+++ fwsnort-1.6.5/debian/control2017-05-07 11:12:59.0 +0200
@@ -3,9 +3,9 @@
 Priority: optional
 Build-Depends: debhelper (>= 8)
 Build-Depends-Indep: po-debconf
-Maintainer: Franck Joncourt 
+Maintainer: Debian QA Group 
 Standards-Version: 3.9.5
-Vcs-git: git://anonscm.debian.org/collab-maint/fwsnort.git
+Vcs-Git: git://anonscm.debian.org/collab-maint/fwsnort.git -b debian
 Vcs-Browser: 
https://anonscm.debian.org/gitweb/?p=collab-maint/fwsnort.git;a=summary
 Homepage: http://www.cipherdyne.org/fwsnort/
 
diff -Nru fwsnort-1.6.5/debian/copyright fwsnort-1.6.5/debian/copyright
--- fwsnort-1.6.5/debian/copyright  2014-08-30 19:11:55.0 +0200
+++ fwsnort-1.6.5/debian/copyright  2017-05-07 11:43:40.0 +0200
@@ -6,14 +6,17 @@
 Files: *
 Copyright: Copyright 2003-2012 by Michael B. Rash 
 License: GPL-2+
- This program is free software; you can redistribute it and/or modify
- it under the terms of the GNU General Public License as published by
- the Free Software Foundation; either version 2 of the License, or
- (at your option) any later version. You can find a copy of it in your
- Debian system under /usr/share/common-licenses/
 
 Files: debian/*
 Copyright: Copyright 2008-2012 by Franck Joncourt 
 License: GPL-2+
+Comment:
  Debian packaging is licensed under the same terms as the software itself 
  (see above).
+
+License: GPL-2+
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 2 of the License, or
+ (at your option) any later version. You can find a copy of it in your
+ Debian system under /usr/share/common-licenses/
diff -Nru fwsnort-1.6.5/debian/fwsnort.postrm 
fwsnort-1.6.5/debian/fwsnort.postrm
--- fwsnort-1.6.5/debian/fwsnort.postrm 2014-08-30 19:11:55.0 +0200
+++ fwsnort-1.6.5/debian/fwsnort.postrm 2017-05-07 11:43:40.0 +0200
@@ -5,6 +5,11 @@
 # In case the user wants to purge the fwsnort package, we must manually remove
 # some files.
 if [ "$1"  = "purge" ]; then
+   # Remove all fwsnort generated firewall rules
+   if [ -f  /var/lib/fwsnort/fwsnort.save ]; then
+   echo "[+] Reverting to original iptables policy..."
+   grep -Fv FWSNORT /var/lib/fwsnort/fwsnort.save | iptables-restore
+   fi
 
# Remove old log files (default directory)
if [ -d /var/log/fwsnort ]; then
diff -Nru fwsnort-1.6.5/debian/gbp.conf fwsnort-1.6.5/debian/gbp.conf
--- fwsnort-1.6.5/debian/gbp.conf   1970-01-01 01:00:00.0 +0100
+++ fwsnort-1.6.5/debian/gbp.conf   2017-05-06 12:18:38.0 +0200
@@ -0,0 +1,4 @@
+# Configuration file for git-buildpackage and friends
+
+[DEFAULT]
+debian-branch = debian
diff -Nru fwsnort-1.6.5/debian/patches/fix-dport-bracket-usage.patch 
fwsnort-1.6.5/debian/patches/fix-dport-bracket-usage.patch
--- 

Bug#861979: ufoai: crashes with signal 11 at mission start

[Markus Koschany]

Control: severity -1 serious
Control: tags -1 pending

Upstream provided a fix for the crash. I think we should fix this in
Stretch too.




signature.asc
Description: OpenPGP digital signature

Bug#862040: (no subject)

[Pierre Rudloff]

This fixed the issue:
echo PURGE | debconf-communicate steam:i386

But I still consider this a bug. It should not have been stuck like this.

Bug#258096: D

[Alak, Tamara Mae]

Can we discuss

Bug#862031: strip-nondeterminism: output a warning when underministic data is removed

[Chris Lamb]

tags 862031 + pending
thanks

Fixed in Git:

  
https://anonscm.debian.org/git/reproducible/strip-nondeterminism.git/commit/?id=b763e31a17ada00f36da0354776708a566454f30


Regards,

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

Bug#861911: closed by Andreas Tille <ti...@debian.org> (Bug#861911: fixed in e-mem 0.0+20160706-2)

[Adrian Bunk]

Control: reopen -1 thanks

On Fri, May 05, 2017 at 06:39:06PM +, Debian Bug Tracking System wrote:
>...
>  e-mem (0.0+20160706-2) unstable; urgency=medium
>  .
>* Restrict architectures to any-amd64 any-i386 any-x32
>  Closes: #861911

This is neither required nor the correct fix.

>...
>   g++: error: unrecognized command line option '-mpopcnt'
>...

Software in Debian is supposed to run on the baseline of the 
architecture, and not unconditionally require more recent CPUs.

The package builds just fine for me after removing the -mpopcnt from the 
Makefile, and this is the correct fix.

Fun fact:
Disassembling the binary in unstable reveals that gcc did not emit
any popcnt instructions on amd64.

cu
Adrian

-- 

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

Bug#862042: xterm: if the faceName resource is defined, the -fn (-font) option is ignored

[Vincent Lefevre]

Package: xterm
Version: 327-2
Severity: minor

If I define the faceName resource, e.g. with

XTerm*faceName: Monospace

in the .Xresources file (read by xrdb), then the -fn (-font) option
is ignored. For instance,

  xterm -fn 7x13

has no effect. Options normally override the default resources, but
this is not the case here. And the observed behavior is not documented.

As a workaround, one can do:

  xterm -fa '' -fn 7x13

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

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

Versions of packages xterm depends on:
ii  libc6   2.24-10
ii  libfontconfig1  2.11.0-6.7+b1
ii  libice6 2:1.0.9-2
ii  libtinfo5   6.0+20161126-1
ii  libutempter01.1.6-3
ii  libx11-62:1.6.4-3
ii  libxaw7 2:1.0.13-1+b2
ii  libxft2 2.3.2-1+b2
ii  libxinerama12:1.1.3-1+b3
ii  libxmu6 2:1.1.2-2
ii  libxpm4 1:3.5.12-1
ii  libxt6  1:1.1.5-1
ii  xbitmaps1.1.1-2

Versions of packages xterm recommends:
ii  x11-utils  7.7+3+b1

Versions of packages xterm suggests:
pn  xfonts-cyrillic  

-- no debconf information

Bug#862004: mwc: Fails to fetch some sites

[Manolo Díaz]

El domingo, 7 de mayo de 2017 a las 18:57
Jörg Frings-Fürst escribió:

> tags 862004 + moreinfo
> thanks
> 
> 
> Hello Manolo,
> 
> thank you for spending your time helping to make Debian better with
> this bug report.
> 
> I have checked your issue and have a quick fix for it.
> 
> Please can you test it?
> 
> Therefore you must change your setup (add the lines Accept and
> UserAgent):
> 
> {'shortname': 'WMO Library',
>    'type': 'html',
>    'uri': 
> 'https://library.wmo.int/opac/index.php?lvl=infopages=en_UK=1',
>    'Accept': 
> 'text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8',
>    'User-Agent': 'Mozilla/5.0 (X11; Linux x86_64; rv:45.0) 
> Gecko/20100101 Firefox/45.0',
>    'contentxpath': '//*[@id="overview"]/tbody/tr[1]/td[1]'
>    }
> 
> 
> backup the original cp /usr/share/mwc/mwc.py /usr/share/mwc/mwc.py.org ,
> 
> copy the attached mwc.py to /usr/share/mwc
> 
> and test it.
> 
> Many thanks!
> 
> CU
> Jörg
> 

Hello Jörg,

It does work. It now works with all my site list:

[WMO] Recently released Driving Innovation Together: The World Weather 
Research Programme WMO-No.1191, 2017 English Guidelines on Satellite Skills and 
Knowl [..]

Thank you very much for your prompt response and fix.

Best regards,
-- 
Manolo Díaz

Bug#862040: steam:i386: Installation terminated: Steam License Agreement was DECLINED.

[Pierre Rudloff]

Package: steam
Version: 1.0.0.49-1
Severity: important

Hello,

I purge the steam package to try to fix an issue and now I can't install it
back.
It fails everytime with this error:
Note: selecting "steam:i386" instead of the
  virtual package "steam"
The following NEW packages will be installed:
  steam:i386
0 packages upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B/835 kB of archives. After unpacking 2689 kB will be used.
Preconfiguring packages ...
(Reading database ... 309500 files and directories currently installed.)
Preparing to unpack .../steam_1.0.0.49-1_i386.deb ...
dpkg: error processing archive
/var/cache/apt/archives/steam_1.0.0.49-1_i386.deb (--unpack):
 subprocess new pre-installation script returned error exit status 30
Installation terminated: Steam License Agreement was DECLINED.
Errors were encountered while processing:
 /var/cache/apt/archives/steam_1.0.0.49-1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Failed to perform requested operation on package.  Trying to recover:

And of course it does not ask me to accept or decline the license agreement.

Regards,



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

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

Bug#862008: crashes, segmentation fault

[Mika Hanhijärvi]

Ok, thanks for the info :-)


_ Mika




On 05/07/2017 05:49 PM, Joanmarie Diggs wrote:

I am looking at the line of code which caused the crash and it is the
same line of code as in the bug I reported. So you might have been doing
something different, but it appears to be the same bug which needs to be
fixed in AT-SPI2.

--joanie

On 05/07/2017 09:14 AM, Mika Hanhijärvi wrote:


If it is the same bug then I have to say I did not close any application
when Orca crashed. I also did not do anythything particularly fast. I am
not 100% sure what I Was doing but If I remember correctly I just
switched between virtual Gnome desktops which did have some application
windows open.




On 05/07/2017 03:45 PM, Joanmarie Diggs wrote:

That is this AT-SPI2 bug:
https://bugzilla.gnome.org/show_bug.cgi?id=767074

--joanie

On 05/07/2017 08:00 AM, Mika Hanhijärvi wrote:

Package: gnome-orca
Version: 3.22.2-3
Severity: grave

Orca seems to sometime crash suddenly without any warning. This is
not good
because blind users like me have to rely on screen reader working
reliably.
This, or similar, problem also existed before the latest update to
Orca in
Debian Stretch, so I do not know if this has anything to do with the
latest
Orca update.

There are these lines in the /var/log/syslog

May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Fatal
Python error:
Segmentation fault
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Stack
(most recent
call first):
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/pyatspi/Accessibility.py", line 184
in 
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/event_manager.py", line 256 in
_queuePrintln
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/event_manager.py", line 329 in
_dequeue
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/pyatspi/registry.py", line 155 in start
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/orca.py", line 561 in start
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/lib/python3/dist-packages/orca/orca.py", line 712 in main
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/bin/orca", line 269 in main
May  7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]:   File
"/usr/bin/orca", line 272 in 




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

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

Versions of packages gnome-orca depends on:
ii  gir1.2-glib-2.01.50.0-1+b1
ii  gir1.2-gtk-3.0 3.22.11-1
ii  gir1.2-pango-1.0   1.40.5-1
ii  gir1.2-wnck-3.03.20.1-3
ii  gsettings-desktop-schemas  3.22.0-1
ii  python3-brlapi 5.4-7
ii  python3-cairo  1.10.0+dfsg-5+b1
ii  python3-gi 3.22.0-2
ii  python3-louis  3.0.0-3
ii  python3-pyatspi2.20.3+dfsg-1
ii  python3-speechd0.8.6-4
pn  python3:any
ii  speech-dispatcher  0.8.6-4

Versions of packages gnome-orca recommends:
ii  libgail-common  2.24.31-2
ii  xbrlapi 5.4-7

gnome-orca suggests no packages.

-- no debconf information

Bug#862029: strip-nondeterminism: clarify package description this is just a workaround which should go away

[Chris Lamb]

tags 862029 + pending
thanks

Fixed in Git:

  
https://anonscm.debian.org/git/reproducible/strip-nondeterminism.git/commit/?id=4ae1b6dc4357a9ca42db38b8f309dfc9150dca11


Regards,

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

Bug#862041: lsb-release: Version number typo in README.Debian

[Ronnie P. Thomas]

Package: lsb-release
Version: 4.1+Debian13+nmu1
Severity: minor

Dear Maintainer,

The README.Debian for lsb-release, shows the version for Jessie as 7.0, instead
of 8.0, in the example provided near the end. Please consider changing either 
the version number or the code name of the release to the proper value.


-- Package-specific info:
lsb_release output
-*- -*- -*- -*- -*-
Distributor ID: Debian
Description:Debian GNU/Linux 8.7 (jessie)
Release:8.7
Codename:   jessie
-*- -*- -*- -*- -*-
Apt policy
-*- -*- -*- -*- -*-
Package files:
 100 /var/lib/dpkg/status
 release a=now
 500 http://repos.sonar.digitalocean.com/apt/ main/main i386 Packages
 release o=. main,a=main,n=main,l=. main,c=main
 origin repos.sonar.digitalocean.com
 100 http://mirrors.digitalocean.com/debian/ jessie-backports/main i386 Packages
 release o=Debian Backports,a=jessie-backports,n=jessie-backports,l=Debian 
Backports,c=main
 origin mirrors.digitalocean.com
 500 http://mirrors.digitalocean.com/debian/ jessie-updates/main i386 Packages
 release o=Debian,a=stable-updates,n=jessie-updates,l=Debian,c=main
 origin mirrors.digitalocean.com
 500 http://security.debian.org/ jessie/updates/main i386 Packages
 release v=8,o=Debian,a=stable,n=jessie,l=Debian-Security,c=main
 origin security.debian.org
 500 http://mirrors.digitalocean.com/debian/ jessie/main i386 Packages
 release v=8.8,o=Debian,a=stable,n=jessie,l=Debian,c=main
 origin mirrors.digitalocean.com
Pinned packages:
-*- -*- -*- -*- -*-
   sources.list
-*- -*- -*- -*- -*-
deb http://mirrors.digitalocean.com/debian jessie main
deb http://security.debian.org/ jessie/updates main
deb http://mirrors.digitalocean.com/debian jessie-updates main
-*- -*- -*- -*- -*-
 /etc/lsb_release
-*- -*- -*- -*- -*-
- none

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

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

Versions of packages lsb-release depends on:
ii  python  2.7.9-1

Versions of packages lsb-release recommends:
ii  apt  1.0.9.8.4

Versions of packages lsb-release suggests:
pn  lsb  

-- no debconf information

Bug#844431: policy: packages should be reproducible

[Chris Lamb]

Hi Holger,

> unsurprisingly I'm also in favor of making this policy change, now.

Actually, yes, why were we waiting for stretch to be released? :)

> Last and least for now: the wording of
> https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=844431;filename=debian-policy.diff.txt;msg=17
> IMO is almost good as it is, though I'll try to amend it to include the
> definition of reproducible builds from reproducible-builds.org. 

That seems the next concrete step.


Regards,

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

Bug#862039: r-bioc-gviz: accesses the internet during build

[Chris Lamb]

Source: r-bioc-gviz
Version: 1.18.1-1
Severity: important
Justification: Policy 4.9
User: la...@debian.org
Usertags: network-access

Dear Maintainer,

Whilst r-bioc-gviz builds successfully on unstable/amd64, according to
Debian Policy 4.9 packages may not attempt network access during
a build.

   00:00:00.00 IP 5f02d4499efa.36140 > dns.z9.domain: 4778+ A? 
bioconductor.org. (34)
   00:00:00.51 IP 5f02d4499efa.36140 > dns.z9.domain: 45901+ ? 
bioconductor.org. (34)
   00:00:01.725656 IP dns.z9.domain > 5f02d4499efa.36140: 45901 0/1/0 (121)
   00:00:03.219280 IP dns.z9.domain > 5f02d4499efa.36140: 4778 8/4/0 A 
52.222.253.6, A 52.222.253.158, A 52.222.253.218, A 52.222.253.224, A 
52.222.253.45, A 52.222.253.252, A 52.222.253.94, A 52.222.253.219 (298)
   00:00:03.306580 IP 5f02d4499efa.8 > 52.222.253.6.https: Flags [S], seq 
4243355363, win 29200, options [mss 1460,sackOK,TS val 493652159 ecr 
0,nop,wscale 7], length 0
   00:00:03.347988 IP 52.222.253.6.https > 5f02d4499efa.8: Flags [S.], seq 
1407308632, ack 4243355364, win 28960, options [mss 1412,sackOK,TS val 
1448496045 ecr 493652159,nop,wscale 8], length 0
   00:00:03.348046 IP 5f02d4499efa.8 > 52.222.253.6.https: Flags [.], ack 
1, win 229, options [nop,nop,TS val 493652169 ecr 1448496045], length 0
   00:00:03.450001 IP 5f02d4499efa.8 > 52.222.253.6.https: Flags [P.], seq 
1:518, ack 1, win 229, options [nop,nop,TS val 493652195 ecr 1448496045], 
length 517
   00:00:03.491891 IP 52.222.253.6.https > 5f02d4499efa.8: Flags [.], ack 
518, win 118, options [nop,nop,TS val 1448496060 ecr 493652195], length 0
   00:00:03.495857 IP 52.222.253.6.https > 5f02d4499efa.8: Flags [.], seq 
1:1401, ack 518, win 118, options [nop,nop,TS val 1448496060 ecr 493652195], 
length 1400

  [..]

The full build log (including tcpdump output) is attached.


Regards,

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


r-bioc-gviz.1.18.1-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#862038: pass-extension-tail: Cannot install pass-extension-tail in sid

[Gavin Lai]

Package: pass-extension-tail
Version: 1.1.0-1
Severity: normal

Dear Maintainer,

   * What led up to the situation?
 APT source.list does not include experimental distribution.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 Add experimental distribution to apt source.list.
   * What was the outcome of this action?
 I can install pass-extension-tail successfully.
   * What outcome did you expect instead?
 I should install pass-extension-tail successfully, even I don't add any
 source.list.
   * Reason
 pass-extension-tail depends on pass package which needs to be at
 least 1.7.0. However, pass 1.7.0 is still in experimental
 distribution. This issue can be solved after pass 1.7.0 moves to
 sid.

Bug#862037: xfce4-systemload-plugin: frequent core files from systemload plugin

[Mike Kupfer]

Package: xfce4-systemload-plugin
Version: 1.1.2-1+b1
Severity: normal

Dear Maintainer,

I frequently notice a core file in $HOME.  The timestamps on the core
files suggest that they are generated when I log out.

$ file core
core: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style, from 
'/usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-1.0 
/usr/lib/x86_64-linux-gnu/xfc', real uid: 1000, effective uid: 1000, real gid: 
1000, effective gid: 1000, execfn: 
'/usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-1.0', platform: 'x86_64'

Suspecting this might be from the System Load Monitor plugin, I
right-clicked on it and removed it, which yielded another core.

Re-adding the plugin to the panel and immediately removing it (i.e.,
without changing its configuration) produced yet another core file.

I've seen core files when I use this plugin on Oracle Linux 7, so I
suspect--but am not certain--that this is an upstream bug.

Here's a stack trace from gdb.

$ gdb /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-1.0 core.bugreport
GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-1.0...(no 
debugging symbols found)...done.

warning: core file may not match specified executable file.
[New LWP 2159]
[New LWP 2160]
[New LWP 2161]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-1.0 
/usr/lib/x86_64-linux-gnu/xfc'.
Program terminated with signal SIGABRT, Aborted.
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
[Current thread is 1 (Thread 0x7fb597310a80 (LWP 2159))]
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x7fb5950133fa in __GI_abort () at abort.c:89
#2  0x7fb59504fbd0 in __libc_message (do_abort=do_abort@entry=2, 
fmt=fmt@entry=0x7fb595144bd0 "*** Error in `%s': %s: 0x%s ***\n")
at ../sysdeps/posix/libc_fatal.c:175
#3  0x7fb595055f96 in malloc_printerr (action=3, 
str=0x7fb59514176d "free(): invalid pointer", ptr=, 
ar_ptr=) at malloc.c:5046
#4  0x7fb59505678e in _int_free (av=0x7fb595377b00 , 
p=0x55c345ae39c0, have_lock=0) at malloc.c:3902
#5  0x7fb58e43abee in ?? ()
   from /usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libsystemload.so
#6  0x7fb595cdef75 in g_closure_invoke (closure=0x55c345af53b0, 
return_value=return_value@entry=0x0, n_param_values=1, 
param_values=param_values@entry=0x7ffd3e241630, 
invocation_hint=invocation_hint@entry=0x7ffd3e2415b0)
at ././gobject/gclosure.c:804
#7  0x7fb595cf0f82 in signal_emit_unlocked_R (
node=node@entry=0x55c345aa8650, detail=detail@entry=0, 
instance=instance@entry=0x55c345a9f0c0, 
emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7ffd3e241630)
at ././gobject/gsignal.c:3635
---Type  to continue, or q  to quit---
#8  0x7fb595cf9bdc in g_signal_emit_valist (instance=, 
signal_id=, detail=, 
var_args=var_args@entry=0x7ffd3e2417e0) at ././gobject/gsignal.c:3391
#9  0x7fb595cf9fbf in g_signal_emit (instance=, 
signal_id=, detail=)
at ././gobject/gsignal.c:3447
#10 0x7fb596f9fe87 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libxfce4panel-1.0.so.4
#11 0x7fb595ce5648 in g_object_run_dispose (object=0x55c345a9f0c0)
at ././gobject/gobject.c:1084
#12 0x7fb5969fefdf in gtk_container_destroy (object=0x55c345ac7090)
at ./gtk/gtkcontainer.c:1073
#13 0x7fb595cdef75 in g_closure_invoke (
closure=closure@entry=0x55c345a81400, return_value=return_value@entry=0x0, 
n_param_values=1, param_values=param_values@entry=0x7ffd3e241ab0, 
invocation_hint=invocation_hint@entry=0x7ffd3e241a30)
at ././gobject/gclosure.c:804
#14 0x7fb595cf1296 in signal_emit_unlocked_R (
node=node@entry=0x55c345a81450, detail=detail@entry=0, 
instance=instance@entry=0x55c345ac7090, 
emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7ffd3e241ab0)
at ././gobject/gsignal.c:3751
---Type  to continue, or q  to quit---
#15 0x7fb595cf9bdc in