Bug#858967: initramfs-tools: Superfluous LVM errors before passphrase prompt after LUKS+LVM install

[Nathan Dorfman]

On Wed, Mar 29, 2017 at 03:07:31PM +0100, Ben Hutchings wrote:
> If you want a pretty boot process, install plymouth.  But I agree that
> it's undesirable to have error messages in a successful boot process.

Plymouth is ok, but for the prettiest boot, it must be clean,
error-free text :)

> However, this is not the fault of initramfs-tools - LVM, LUKS and
> software RAID are set up by scripts provided by other packages.

Sorry about that. I think the next question is still for you, though.
If not, sorry about that, too:

To fix this, would it be appropriate to use something like
lvm= in the options column of /etc/crypttab?

Then, the initramfs scripts (whichever package they come from) could
know that the volume group depends on the crypttab entry, and only try
to bring the former up after the latter.

This might not be relevant, but Ubuntu's installer does in fact add
exactly that option to crypttab. If it has any effect, though, I can't
tell what it is -- they exhibit the same behavior at boot. Maybe it's
something that used to work in the past?

-nd.

Bug#858920: neurodebian-desktop: Trigger cycle via interest(-await) on /usr/share/icons/gnome while depending (in)directly on gnome-icon-theme - please use interest-noawait

[Niels Thykier]

Yaroslav Halchenko:
> 
> [...]
> 
> so, smth like
> 
> diff --git a/debian/changelog b/debian/changelog
> index 6ecf20f..1952eca 100644
> --- a/debian/changelog
> +++ b/debian/changelog
> @@ -1,3 +1,10 @@
> +neurodebian (0.37.6) unstable; urgency=medium
> +
> +  * Switch to use interest-noawait for neurodebian-desktop.trigger
> +to avoid a circular deadlock (Closes: #858920)
> +
> + -- Yaroslav Halchenko   Tue, 28 Mar 2017 13:53:19 
> -0400
> +
>  neurodebian (0.37.5) unstable; urgency=medium
>  
>* debian/control
> diff --git a/debian/neurodebian-desktop.triggers 
> b/debian/neurodebian-desktop.triggers
> index 44fdcbd..2adc7ee 100644
> --- a/debian/neurodebian-desktop.triggers
> +++ b/debian/neurodebian-desktop.triggers
> @@ -1 +1 @@
> -interest /usr/share/icons/gnome
> +interest-noawait /usr/share/icons/gnome
> 
> should resolve this issue, correct? ;)
> 

Basically, yes.

Thanks,
~Niels

Bug#859070: /bin/zsh: status of resumed background jobs incorrectly listed as 'unknown signal (core dumped)'

[Nathan Dorfman]

Package: zsh
Version: 5.3.1-3+b1
Severity: normal
File: /bin/zsh

Dear Maintainer,

After a stopped pipeline job is resumed via the 'bg' builtin command,
the status of every command in the pipeline except the first is
incorrectly displayed. For example:

stretch% sleep 10 | sleep 15 | sleep 20
^Z
zsh: suspended  sleep 10 | sleep 15 | sleep 20
stretch% bg
[1]  + continued  sleep 10 | sleep 15 | sleep 20
stretch% jobs -l
[1]  + 1556 runningsleep 10 | 
   1557 unknown signal (core dumped) sleep 15 | 
   1558 unknown signal (core dumped) sleep 20
stretch%

The same thing happens regardless of what the commands are, as long as
there are at least two commands with a pipe petween them. Despite the
status, the jobs are definitely running:

stretch% cp /dev/null /tmp/emptyfile && tail -F /tmp/emptyfile | sed
's/foo/quux/'
^Z
zsh: suspended  tail -F /tmp/emptyfile | sed 's/foo/quux/'
stretch% bg
[1]  - continued  tail -F /tmp/emptyfile | sed 's/foo/quux/'
stretch% jobs -l
[1]  + 1583 runningtail -F /tmp/emptyfile | 
   1584 unknown signal (core dumped) sed
's/foo/quux/'
stretch% echo foobar > /tmp/emptyfile
stretch% quuxbar

After the job completes, the status is correctly displayed as 'done':

stretch% kill 1583
stretch% 
[1]  + terminated  tail -F /tmp/emptyfile | 
   donesed 's/foo/quux/'

While sending SIGCONT to the processes directly usually has the same
effect, by sending the signals individually in a certain order it's
actually possible to coax the correct behavior out:

stretch% sleep 120 | cat | cat
^Z
zsh: suspended  sleep 120 | cat | cat
stretch% jobs -l
[1]  + 1613 suspended  sleep 120 | 
   1614 suspended  cat | 
   1615 suspended  cat
stretch% kill -CONT 1615 ; jobs -l
[1]  + 1613 suspended  sleep 120 | 
   1614 suspended  cat | 
   1615 runningcat
stretch% kill -CONT 1614 ; jobs -l
[1]  + 1613 suspended  sleep 120 | 
   1614 runningcat | 
   1615 runningcat
stretch% kill -CONT 1613 ; jobs -l
[1]  + 1613 runningsleep 120 | 
   1614 runningcat | 
   1615 runningcat
stretch% 

Trying a different order seems to suggest that it happens to the
reader of a pipe if it wakes up (receives SIGCONT) after the writer,
but not if the writer is still suspended:

stretch% jobs -l
[1]  + 1653 suspended  sleep 120 | 
   1654 suspended  cat | 
   1655 suspended  cat
stretch% kill -CONT 1654; jobs -l
[1]  + 1653 suspended  sleep 120 | 
   1654 runningcat | 
   1655 suspended  cat
stretch% kill -CONT 1655; jobs -l
[1]  + 1653 suspended  sleep 120 | 
   1654 runningcat | 
   1655 unknown signal (core dumped) cat

-- Package-specific info:
Packages which provide code meant to be sourced in .zshrc:

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion  Architecture Description
+++-===---
un  grml-debootstra   (no description available)

Packages which provide vendor completions:

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion  Architecture Description
+++-===---
ii  pulseaudio  10.0-1   amd64PulseAudio sound server
ii  systemd 232-20~test0 amd64system and service manager
ii  udev232-20~test0 amd64/dev/ and hotplug management 
daemon
ii  vlc-bin 2.2.4-14 amd64binaries from VLC

dpkg-query: no path found matching pattern /usr/share/zsh/vendor-functions/


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

Kernel: Linux 4.9.0-2-amd64 (SMP w/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 zsh depends on:
ii  dpkg1.18.23
ii  libc6   2.24-9
ii  libcap2 1:2.25-1
ii  libtinfo5   6.0+20161126-1
ii  zsh-common  5.3.1-3

Versions of packages zsh recommends:
ii  libc6 2.24-9
ii  libncursesw5  6.0+20161126-1
ii  libpcre3  2:8.39-2.1

Versions of packages zsh suggests:
pn  zsh-doc  

-- no debconf information

Bug#750405: psmisc: FTBFS on hurd-i386

[Svante Signell]

found 750405 2.21-2.1
tags 750405 -pending -upstream
thanks

Hello,

Attached is an updated patch for the PATH_MAX issue in psmisc. It uses the fact
that calling snprintf() with *str=NULL and size=0 returns the number of bytes
needed for the string according to POSIX.1-2001 and later (which is supported by
all glibc versions since 2.1, see snprintf(3)).

Thanks!Index: psmisc-22.21/src/pstree.c
===
--- psmisc-22.21.orig/src/pstree.c
+++ psmisc-22.21/src/pstree.c
@@ -797,14 +797,24 @@ static char* get_threadname(const pid_t
 {
 FILE *file;
 char *thread_comm, *endcomm, *threadname;
-char path[PATH_MAX + 1];
+char *path = NULL;
+size_t len = 0;
+int nbytes;
 char readbuf[BUFSIZ + 1]; 
 
 if (! (threadname = malloc(COMM_LEN + 2 + 1))) {
 	exit(2);
 }
-if (snprintf(path, PATH_MAX, "%s/%d/task/%d/stat", PROC_BASE, pid, tid) < 0)
-	perror("get_threadname: asprintf");
+len = snprintf(NULL, 0, "%s/%d/task/%d/stat", PROC_BASE, pid, tid);
+if (len < 0)
+	exit(2);
+len++;
+path = malloc(len);
+if (path == NULL)
+	exit(2);
+nbytes = snprintf(path, len, "%s/%d/task/%d/stat", PROC_BASE, pid, tid);
+if (nbytes < 0 || nbytes >= len)
+	perror("get_threadname: snprintf");
 if ( (file = fopen(path, "r")) != NULL) {
 	if (fread(readbuf, 1, BUFSIZ, file) > 0) {
 	if ((thread_comm = strchr(readbuf, '('))
@@ -813,12 +823,14 @@ static char* get_threadname(const pid_t
 		*endcomm = '\0';
 		sprintf(threadname, "{%.*s}", COMM_LEN, thread_comm);
 		(void) fclose(file);
+		free(path);
 		return threadname;
 	}
 	}
 }
 /* Fall back to old method */
 sprintf(threadname, "{%.*s}", COMM_LEN, comm);
+free(path);
 fclose(file);
 return threadname;
 }

Bug#837893: systemd: Logging from gnome session is passed on to all syslog facilities

[Michael Biebl]

Control: tags -1 + patch

On Thu, 15 Sep 2016 11:15:29 +0200 Matijs van Zuijlen
 wrote:
> Package: systemd
> Version: 231-6
> Severity: normal
> 
> Since recently, log messages from programs running under the gnome
> session have started appearing in all logs in /var/logs, including
> /var/logs/kern.log, even though my rsyslog configuration has not
> changed, and correctly only routes kern.* there.
> 
> This is very annoying since it fills the logs with messages that don't
> belong there, and makes running logcheck tedious.
> 
> It seems this is a recent regression, since before I was able to route
> these messages to a low-priority log using the following rsyslog
> configuration:
> 
>   user.=info;user.=notice;\
>   user.=warn  -/var/log/user-low.log
> 
> If I look at the messages directly with journalctl -o verbose, it seems
> they do not set the syslog facility, which should make them end up with
> user facility, but doesn't.
> 

Patch posted upstream at
https://github.com/systemd/systemd/pull/5667


-- 
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#854372: Info received (kwin-x11: kwin starts flickering the screen contents)

[Julien Aubin]

Hi Maximiliano,

Got the 5.8.6 package. As of now no instability - will check over time to
confirm the result.

The only small issue appears when you switch to and from VT - the display
appears corrupt for a small time but then everything is back fine.

2017-03-26 9:46 GMT+02:00 Julien Aubin :

> Sorry cannot test Kwin 5.8.6 as of now since it would break many
> dependencies on my system (it has quite many 5.8.6 dependencies and KDE
> 5.8.6 is coming to testing as of now). Anyway I'll test it for sure once it
> lands into testing.
>
> Rgds
>
> 2017-03-25 9:12 GMT+01:00 Julien Aubin :
>
>> Hi,
>>
>> Yes it might. kwin 5.8.2 + breeze 5.8.4 produce the issue as well, while
>> kwin 5.8.4 + breeze 5.8.4 do not seem to cause the issue.
>>
>> 2017-03-25 8:47 GMT+01:00 Maximiliano Curia :
>>
>>> ¡Hola Julien!
>>>
>>> El 2017-03-24 a las 19:45 +0100, Julien Aubin escribió:
>>>
 Actually the issue has greatly reduced w/ kwin 5.8.4 from what it was
 in 5.8.2.

>>>
>>> Now if you disable the experimental "allow apps to disable compositing"
 feature, and set the "keep window thumbnails" to always in the compositor
 settings then the issue disappears. I think it should be the default.

>>>
>>> Then I guess that the breeze integration is makes a difference for this
>>> issue.
>>>
>>> This is mostly context for me: 5.8.4 and 5.8.6 are compiled with the
>>> breeze integration, 5.8.5 not, because kwin was looking for breeze 5.8.5
>>> and we were providing 5.8.4, for 5.8.6 Martin Gräßlin dropped the minor
>>> from the dependency.
>>>
>>> Can you test if 5.8.6 (currently in sid) has the same behaviour of 5.8.4
>>> for you?
>>>
>>> Happy hacking,
>>> --
>>> : You are in a dark room with a compiler, emacs, an internet connection,
>>> : and a thermos of coffee.
>>> : Your move ?
>>>
>>> Saludos /\/\ /\ >< `/
>>>
>>
>>
>

Bug#858084: closed by Ben Hutchings <b...@decadent.org.uk> (Re: Bug#858084: linux-image-amd64 - kernel option enable request)

[Narayanan R S]

Hello,

AFAIK, there's no (performance or size) penalty in enabling it and it
provides some very convenient stats directly via sysfs. As a user of the
stats, it is very convenient just to have them ready and usable without
having to jump through hoops to access them.

I don't understand the reason for not enabling them. Is there any reason
*NOT* to enable it?

Thanks.

Regards,

Narayanan.

On Thu, Mar 30, 2017 at 4:45 AM, Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the linux-image-amd64 package:
>
> #858084: linux-image-amd64 - kernel option enable request
>
> It has been closed by Ben Hutchings .
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Ben Hutchings <
> b...@decadent.org.uk> by
> replying to this email.
>
>
> --
> 858084: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858084
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
> -- Forwarded message --
> From: Ben Hutchings 
> To: 858084-d...@bugs.debian.org
> Cc:
> Bcc:
> Date: Thu, 30 Mar 2017 00:13:03 +0100
> Subject: Re: Bug#858084: linux-image-amd64 - kernel option enable request
> On Sat, 2017-03-18 at 10:16 +0530, Narayanan R S wrote:
> > Package: linux-image-amd64
> > Version: 4.9+79~bpo8+1
> >
> > Can you please enable the CONFIG_CPU_FREQ_STAT_DETAILS option for the
> > kernels.
>
> No, this is not really needed.  You can use the power:cpu_frequency
> tracepoint to see all transitions and then work out the statistics in a
> user-space program (or use bpfcc to do it in-kernel).
>
> Ben.
>
> --
> Ben Hutchings
> Everything should be made as simple as possible, but not simpler.
>- Albert
> Einstein
>
>
> -- Forwarded message --
> From: Narayanan R S 
> To: sub...@bugs.debian.org
> Cc:
> Bcc:
> Date: Sat, 18 Mar 2017 10:16:20 +0530
> Subject: linux-image-amd64 - kernel option enable request
> Package: linux-image-amd64
> Version: 4.9+79~bpo8+1
>
> Can you please enable the CONFIG_CPU_FREQ_STAT_DETAILS option for the
> kernels.
>
> Thanks in advance.
>
> Regards,
>
> Narayanan.
>
>

Bug#855922: [pkg-go] Bug#855922: containerd: 0.2.3 ds1-1 breaks docker 1.11 - unable to start containerd

[Potter, Tim]

On 30 Mar 2017, at 3:54 AM, Michael Stapelberg  wrote:
> 
> Hi Tim,
> 
> "Potter, Tim"  writes:
>> Hi Ricardo.  Thanks for the bug report.  I messed up by uploading some of 
>> the Docker 1.13
>> dependencies to unstable instead of experimental - my apologies.
>> 
>> I've done a new upload with a Breaks line to avoid this bug occurring until 
>> I finish testing
>> 1.13 and uploading to unstable.
> 
> I’m still running into this issue (or a very similar one?) with:
> 
> docker.io 1.13.0~ds1-2
> runc 0.1.1+dfsg1-2+b1
> containerd 0.2.3~git20161117.78.03e5862~ds1-2
> golang-libnetwork 0.8.0~dev.2+git20161130.568.fd27f22-4
> 
> I installed these packages from Debian unstable, but AFAICT, no newer
> version is available in experimental.
> 
> The symptom is:
> $ docker run -t -i debian:sid /bin/bash
> docker: Error response from daemon: containerd: container not started.
> 
> In the journal, I can’t see any errors from containerd itself.
> 
> Should docker be working in Debian at the moment? If not, is there a
> workaround?

Hi Michael.  I did an upload yesterday to unstable and things should be working 
again.
Sorry about the mess in experimental vs unstable.  I was trying to keep both 
the old
and new version working but failed miserably.

Please let me know if you find any more brokenness.


Tim.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#754785: ITP: fonts-open-sans -- sans serif typeface

[陳昌倬]

On Wed, Mar 29, 2017 at 08:37:31AM +0200, Gregor Riepl wrote:
> Hello again,
> 
> my packaging repository is here:
> https://github.com/onitake/fonts-open-sans
> 
> I uploaded the package to Debian mentors as well:
> https://mentors.debian.net/package/fonts-open-sans
> 
> Could a Debian maintainer take a look and sponsor my package?

Hi,

Thanks for contributing to Debian. The following is my suggestion for
your package.


- Since this package is maintain by Debian Fonts Task Force, you can
  change your Vcs-* to https://anonscm.debian.org/git/pkg-fonts so that
  other members can help to maintain the git repo.

- Not sure if necessary, but I always include the following text for
  Apache-2 license in debian/copyright.
 

License:   Apache-2.0
 Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 .
 http://www.apache.org/licenses/LICENSE-2.0
 .
 Unless required by applicable law or agreed to in writing, software
 distributed under the License is distributed on an "AS IS" BASIS,
 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 See the License for the specific language governing permissions and
 limitations under the License.
 .
 Bits here from Apache Kudu (incubating), ASL 2.0
 .
 On Debian systems, the complete text of the Apache License Version 2.0
  can be found in `/usr/share/common-licenses/Apache-2.0'.

-- 
ChangZhuo Chen (陳昌倬) czchen@{czchen,debian}.org
http://czchen.info/
Key fingerprint = BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature

Bug#852398: same here

[my]

Dear Devs,

This is not really helpful at all,  as whatever the intention was,  the
easy solution was to install google-chrome,  which is hardly a solution
at all.

Whether we like it or not,  many things we need are neither free nor
open source,  and this compilation means one must either use google-
chrome,  a truly commercial mess,  change the environmental variable, 
or give up synchronisation of chrome across all devices.   Since the
lattermost is important,  and each browser does something different, 
we can actually use sites in Firefox that run java,  for instance,  all
browsers must be equally functional whether on a debian Mate box, cell
phone or table.  

It is 2017.  and everyone does not expect synchro across devices,  but
requires it to work in the real world.

Best,
M

Bug#859067: opendkim: reason="key not found in DNS" is not an adequate explanation

[Russell Coker]

Package: opendkim
Version: 2.11.0~alpha-9
Severity: normal

Authentication-Results: smtp.sws.net.au;
dkim=fail reason="key not found in DNS" (0-bit key; unprotected) 
header.d=etbe.example.com header.i=@etbe.example.com header.b="VHEGE743";
dkim-atps=neutral

Above is a header error I received from sending a test email with the
domain etbe.example.com.  The command opendkim-testmsg on the same system
regards the email as ok and tcpdump showed the DNS lookup succeeding.

I think that there needs to be more information on how the key was not found
so I can track this sort of problem down.

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

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

Versions of packages opendkim depends on:
ii  adduser  3.115
ii  dns-root-data2015052300+h+1
ii  init-system-helpers  1.47
ii  libbsd0  0.8.3-1
ii  libc62.24-9
ii  libdb5.3 5.3.28-12+b1
ii  libldap-2.4-22.4.44+dfsg-3
ii  liblua5.1-0  5.1.5-8.1+b2
ii  libmemcached11   1.0.18-4.1
ii  libmemcachedutil21.0.18-4.1
ii  libmilter1.0.1   8.15.2-8
ii  libopendbx1  1.4.6-11
ii  libopendkim112.11.0~alpha-9
ii  librbl1  2.11.0~alpha-9
ii  libssl1.11.1.0e-1
ii  libunbound2  1.6.0-3
ii  libvbr2  2.11.0~alpha-9
ii  lsb-base 9.20161125

opendkim recommends no packages.

Versions of packages opendkim suggests:
ii  opendkim-tools  2.11.0~alpha-9
pn  unbound 

-- Configuration Files:
/etc/default/opendkim [Errno 2] No such file or directory: 
'/etc/default/opendkim'
/etc/opendkim.conf changed [not included]

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/lib/tmpfiles.d/opendkim.conf (from opendkim package)

Bug#859068: avahi-daemon race condition with ifupdown networking

[Matt Zagrabelny]

Package: avahi-daemon
Version: 0.6.32-2
Severity: normal

Greetings,

It appears that avahi-daemon is configuring eth0 before ifupdown can:

# journalctl -b | egrep 'ifup|avahi.*eth0'
Mar 29 20:20:52 achilles avahi-daemon[690]: Joining mDNS multicast group on 
interface eth0.IPv4 with address 131.212.60.13.
Mar 29 20:20:52 achilles avahi-daemon[690]: New relevant interface eth0.IPv4 
for mDNS.
Mar 29 20:20:52 achilles avahi-daemon[690]: Registering new address record for 
131.212.60.13 on eth0.IPv4.
Mar 29 20:20:52 achilles avahi-daemon[690]: Registering new address record for 
131.212.60.15 on eth0.IPv4.
Mar 29 20:20:57 achilles avahi-daemon[690]: Joining mDNS multicast group on 
interface eth0.IPv6 with address fe80::210:18ff:fe5c:c3ad.
Mar 29 20:20:57 achilles avahi-daemon[690]: New relevant interface eth0.IPv6 
for mDNS.
Mar 29 20:20:57 achilles avahi-daemon[690]: Registering new address record for 
fe80::210:18ff:fe5c:c3ad on eth0.*.
Mar 29 20:21:05 achilles ifup[717]: RTNETLINK answers: File exists
Mar 29 20:21:05 achilles ifup[717]: ifup: failed to bring up eth0
Mar 29 20:21:06 achilles avahi-daemon[690]: Leaving mDNS multicast group on 
interface eth0.IPv6 with address fe80::210:18ff:fe5c:c3ad.
Mar 29 20:21:06 achilles avahi-daemon[690]: Joining mDNS multicast group on 
interface eth0.IPv6 with address 2607:ea00:200:60::13.
Mar 29 20:21:06 achilles avahi-daemon[690]: Registering new address record for 
2607:ea00:200:60::13 on eth0.*.
Mar 29 20:21:06 achilles avahi-daemon[690]: Withdrawing address record for 
fe80::210:18ff:fe5c:c3ad on eth0.

ifup is failing with the "RTNETLINK answers: File exists" error.

This system is running sid, but was initially installed years ago, so there
may be some vestigial issues that are confounding things.

Let me know what you think.

Thanks!

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

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

Versions of packages avahi-daemon depends on:
ii  adduser  3.115
ii  bind9-host [host]1:9.10.3.dfsg.P4-12.1
ii  dbus 1.10.16-1
ii  init-system-helpers  1.47
ii  libavahi-common3 0.6.32-2
ii  libavahi-core7   0.6.32-2
ii  libc62.24-9
ii  libcap2  1:2.25-1
ii  libdaemon0   0.14-6
ii  libdbus-1-3  1.10.16-1
ii  libexpat12.2.0-2
ii  lsb-base 9.20161125

Versions of packages avahi-daemon recommends:
pn  libnss-mdns  

Versions of packages avahi-daemon suggests:
pn  avahi-autoipd  

-- Configuration Files:
/etc/network/if-up.d/avahi-daemon [Errno 2] No such file or directory: 
'/etc/network/if-up.d/avahi-daemon'

-- no debconf information

Bug#852398: STILL PRESENT on Version 57.0.2987.98 built on Debian 9.0, running on Debian 9.0 (64-bit)

[Michael Wilson]

This is getting beyond an absolute joke. It has been over a month
since the community has spoken of this issue and the maintainer has
said almost nothing. This is clearly just a terrible decision made by
the maintainer. It is a major usability issue. How are we to expect
new users to join Debian when stuff like this is hiding underneath?

Please can you address the STILL PRESENT ISSUE!

Version 57.0.2987.98 built on Debian 9.0, running on Debian 9.0 (64-bit)

Bug#859021: dd: document that bs overrides ibs and obs

[Pádraig Brady]

On 29/03/17 09:04, Chris Davies wrote:
> Package: coreutils
> Version: 8.25-2+b1
> Severity: minor
> 
> Dear Maintainer,
> 
> The man page for dd does not define an interaction between bs and its more
> specific ibs and obs options. POSIX does mandate that bs, if specified,
> shall override ibs and obs. Empirically I have determined that coreutils
> dd implements POSIX behaviour, so I should like to suggest the man page
> is updated to state that bs overrides ibs and/or obs.
> 
> 
> POSIX man page at http://www.unix.com/man-page/posix/1posix/dd/ defines
> the three options bs, ibs, and obs as follows:
> 
> ibs=expr
>   Specify the input block size, in bytes, by expr (default is 512).
> 
> obs=expr
>   Specify the output block size, in bytes, by expr (default is 512).
> 
> bs=expr
>   Set  both input and output block sizes to expr bytes, superseding
>   ibs= and obs=. If no conversion other than sync, noerror, and
>   notrunc is specified, each input  block shall be copied to the
>   output as a single block without aggregating short blocks.
> 
> 
> Extracts from the current coreutils man page read as follows:
> 
> bs=BYTES
>   read and write up to BYTES bytes at a time
> 
> ibs=BYTES
>   read up to BYTES bytes at a time (default: 512)
> 
> obs=BYTES
>   write BYTES bytes at a time (default: 512)
> 
> 
> I would like to suggest that the explanation is amended as follows:
> 
> bs=BYTES
>   read and write up to BYTES bytes at a time (default:
>   512); overrides ibs and obs

Done in your name upstream at:
http://git.sv.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=v8.27-15-gc1c558e

Bug#859066: linux-image-*: recommend firmware-ath9k-htc

[Paul Wise]

Source: linux
Version: 4.10~rc6-1~exp1
Severity: wishlist
X-Debbugs-CC: open-ath9k-htc-firmw...@packages.debian.org

Now that open-ath9k-htc-firmware has been accepted into Debian
unstable, please add "Recommends: firmware-ath9k-htc" to the
metadata for the linux-image-* packages in Debian experimental.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#847099:

[Patrick Beeson]

0.5.2-4 fix in Ubuntu Zesty works great!  Thanks.

At the very least now I can installed the two .deb files in 16.04.  Any
chance this could get pushed upstream to Xenial?

Bug#858525: marked as pending

[Reinhard Tartler]

On 03/29/2017 06:20 AM, Andreas Beckmann wrote:
> On 2017-03-29 03:09, Reinhard Tartler wrote:
>> tag 858525 pending
>> thanks
>>
>> Hello,
>>
>> Bug #858525 reported by you has been fixed in the Git repository. You can
>> see the changelog below, and you can check the diff of the fix at:
>>
>> 
>> http://anonscm.debian.org/git/pkg-multimedia/jackd2.git/commit/?id=cbbda8d
> 
> That misses Breaks+Replaces for the moved library.

Thanks for the review.

The Conflicts is already in place, but the Replaces was indeed missing.
I'll add the Replaces, and avoid exposing libjackserver.so as public
library.

Best,
Reinhard

Bug#859065: unblock: goiardi/0.11.2-2

[Jordi Mallach]

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

Please unblock package goiardi

It includes a backported fix for a server crash when handling objects with
duplicate array items. It also removes the logs on purge, a change that
should have been uploaded before the freeze but apparently didn't happen.

unblock goiardi/0.11.2-2

The debdiff is as follows:

+goiardi (0.11.2-2) unstable; urgency=medium
+
+  * Remove /var/log/goiardi on purge as well (really closes: #847354).
+  * Add databag_duplicate_field_crash.patch: cherrypick a fix for a server
+crash when handling objects with duplicate items in an array.
+
+ -- Jordi Mallach   Thu, 30 Mar 2017 02:51:02 +0200
+
 goiardi (0.11.2-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru goiardi-0.11.2/debian/patches/databag_duplicate_field_crash.patch 
goiardi-0.11.2/debian/patches/databag_duplicate_field_crash.patch
--- goiardi-0.11.2/debian/patches/databag_duplicate_field_crash.patch   
1970-01-01 01:00:00.0 +0100
+++ goiardi-0.11.2/debian/patches/databag_duplicate_field_crash.patch   
2017-03-30 02:50:08.0 +0200
@@ -0,0 +1,173 @@
+Index: goiardi/CHANGELOG
+===
+--- goiardi.orig/CHANGELOG
 goiardi/CHANGELOG
+@@ -4,6 +4,8 @@
+   Does require rebuilding the search index.
+ * Allow using 'novault' as a build tag to avoid having to have the vault api
+   present when building goiardi. Not relevant to most people.
++* Backport fix for duplicate items in arrays in indexed objects crashing the
++  server when saving.
+ 
+ 
+ 0.11.1
+Index: goiardi/circle.yml
+===
+--- goiardi.orig/circle.yml
 goiardi/circle.yml
+@@ -1,6 +1,6 @@
+ machine:
+   environment:
+-GODIST: "go1.7.3.linux-amd64.tar.gz"
++GODIST: "go1.7.4.linux-amd64.tar.gz"
+ dependencies:
+   pre:
+ - mkdir -p download
+Index: goiardi/indexer/postgres_indexer.go
+===
+--- goiardi.orig/indexer/postgres_indexer.go
 goiardi/indexer/postgres_indexer.go
+@@ -21,6 +21,7 @@ import (
+   "github.com/ctdk/goiardi/datastore"
+   "github.com/ctdk/goiardi/util"
+   "github.com/lib/pq"
++  "sort"
+   "strings"
+ )
+ 
+@@ -146,6 +147,11 @@ func (p *PostgresIndex) SaveItem(obj Ind
+   return err
+   }
+   case []string:
++  // remove dupes from slices of strings like we're doing
++  // now with the trie index, both to reduce ambiguity and
++  // to maybe make the indexes just a little bit smaller
++  sort.Strings(v)
++  v = util.RemoveDupStrings(v)
+   for _, w := range v {
+   w = util.IndexEscapeStr(w)
+   w = strings.Replace(w, "\n", "\\n", -1)
+Index: goiardi/search/search_test.go
+===
+--- goiardi.orig/search/search_test.go
 goiardi/search/search_test.go
+@@ -258,6 +258,14 @@ func TestSearchBasicQueryEscaped(t *test
+   }
+ }
+ 
++func TestIndexDupes(t *testing.T) {
++  r, _ := role.New("idx_role")
++  r.Default["foo"] = "bar"
++  r.Default["notdupe"] = []string{"I", "am", "good"}
++  r.Default["dupes"] = []string{"I", "", "will", "", "cause", "problems", 
"I", ""}
++  r.Save()
++}
++
+ // Probably don't want this as an always test, but it's handy to have 
available.
+ /*
+ func TestEmbiggenSearch(t *testing.T) {
+Index: goiardi/util/string_test.go
+===
+--- /dev/null
 goiardi/util/string_test.go
+@@ -0,0 +1,37 @@
++/*
++ * Copyright (c) 2013-2016, Jeremy Bingham ()
++ *
++ * Licensed under the Apache License, Version 2.0 (the "License");
++ * you may not use this file except in compliance with the License.
++ * You may obtain a copy of the License at
++ *
++ * http://www.apache.org/licenses/LICENSE-2.0
++ *
++ * Unless required by applicable law or agreed to in writing, software
++ * distributed under the License is distributed on an "AS IS" BASIS,
++ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
++ * See the License for the specific language governing permissions and
++ * limitations under the License.
++ */
++
++package util
++
++import (
++  "sort"
++  "testing"
++)
++
++func TestDupRemoval(t *testing.T) {
++  strs := []string{"This", "", "has", "", "some", "", "some", "dupes"}
++  sort.Strings(strs)
++  strs = RemoveDupStrings(strs)
++  chkmap := make(map[string]uint8)
++  for _, v := range strs {
++  chkmap[v]++
++  }
++  for k, v := range chkmap {
++  if v > 1 {
++  

Bug#850219: Should be solved in newer kernel

[Ben Hutchings]

Control: tag -1 moreinfo

On Tue, 2017-02-21 at 07:04 +0100, Ulrich Möhrke wrote:
> Bug 850219 should be solved with kernel 4.10-rc7.
> See https://bugs.freedesktop.org/show_bug.cgi?id=98405

If I read correctly, the fix is this:
https://git.kernel.org/linus/7dfee6827780d4228148263545af936d0cae8930

Could you test whether this works as a patch to 4.9?  I've attached the
patch and you can build a new package by following the instructions at:
https://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official

Ben.

-- 
Ben Hutchings
In a hierarchy, every employee tends to rise to his level of
incompetence.
From: Ben Skeggs 
Date: Mon, 9 Jan 2017 10:22:15 +1000
Subject: drm/nouveau/disp/mcp7x: disable dptmds workaround
Origin: https://git.kernel.org/linus/7dfee6827780d4228148263545af936d0cae8930
Bug-Debian: https://bugs.debian.org/850219

The workaround appears to cause regressions on these boards, and from
inspection of RM traces, NVIDIA don't appear to do it on them either.

Signed-off-by: Ben Skeggs 
Tested-by: Roy Spliet 
---
 drivers/gpu/drm/nouveau/nvkm/engine/disp/nv50.c | 2 --
 1 file changed, 2 deletions(-)

diff --git a/drivers/gpu/drm/nouveau/nvkm/engine/disp/nv50.c b/drivers/gpu/drm/nouveau/nvkm/engine/disp/nv50.c
index 567466f93cd5..0db8efbf1c2e 100644
--- a/drivers/gpu/drm/nouveau/nvkm/engine/disp/nv50.c
+++ b/drivers/gpu/drm/nouveau/nvkm/engine/disp/nv50.c
@@ -433,8 +433,6 @@ nv50_disp_dptmds_war(struct nvkm_device *device)
 	case 0x94:
 	case 0x96:
 	case 0x98:
-	case 0xaa:
-	case 0xac:
 		return true;
 	default:
 		break;


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

Bug#794680: Fix in stable

[Ben Hutchings]

On Tue, 2017-02-28 at 10:58 +0100, Michael Witrant wrote:
> Hello,
> 
> > fixed 794680 4.1.3-1
> 
> Is this fix available on stable?
> 
> I'm using stable and having the same problem.

No, we have no idea what fixed it.

Ben.

-- 
Ben Hutchings
In a hierarchy, every employee tends to rise to his level of
incompetence.



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

Bug#856505: No sound in Raspberry Pi 2, missing module?

[Ben Hutchings]

Control: retitle -1 No driver for BCM2835 audio output
Control: reassign -1 src:linux 4.9.10-1
Control: severity -1 important
Control: tag -1 upstream

On Wed, 2017-03-01 at 18:53 +, eHenry Berg wrote:
[...]
> I think the sound does not work for me because the module snd-bcm2835
> does not exist.
> Can you configure kernel version 4.10 to include snd-bcm2835 as a
> module, when it comes to sid.

This driver has still not been added upstream, so we cannot enable it
yet.

Ben.

-- 
Ben Hutchings
In a hierarchy, every employee tends to rise to his level of
incompetence.


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

Bug#852698: linux-image-4.9.0-1-amd64: nouveau seems to hang programs like lspci and Xorg

[Ben Hutchings]

Control: tag -1 moreinfo

On Thu, 26 Jan 2017 15:29:44 +0100 Hermann Lauer 
 wrote:
> Package: src:linux
> Version: 4.9.2-2
> Severity: important
> 
> Dear Maintainer,
> 
> the new testing 4.9.0 linux-image hangs on a machine with Optimus Technology
> related to the nouveau kernel module - even an "lspci" hangs the process hard.
> A controlled shutdown via systemd hangs also indefinitely.
> Kernel log is appended.
> 
> Tried vanilla 4.9.6 with similar results. The older 4.8 package from testing
> runs fine
[...]

This has been reported by another user as fixed in 4.9.10-1.  Can you
confirm whether this still occurs on your machine?

Ben.

-- 
Ben Hutchings
In a hierarchy, every employee tends to rise to his level of
incompetence.



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

Bug#859064: mypaint: It does not start on Wayland (fixed upstream)

[Claudio Sacerdoti Coen]

Package: mypaint
Version: 1.2.0-4
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

Starting mypaint on Wayland:
claudio@zenone:/tmp/libmypaint$ mypaint
INFO: mypaint: Installation layout: conventional POSIX-like structure
with prefix u'/usr'
INFO: lib.i18n: POSIX: LANG='en_US.UTF-8'
INFO: lib.i18n: POSIX: LANGUAGE='en_US:en'
Gdk-Message: Unable to load bogosity from the cursor theme
Traceback (most recent call last):
  File "/usr/bin/mypaint", line 462, in 
main.main(datapath, iconspath, old_confpath, version=version)
  File "/usr/share/mypaint/gui/main.py", line 95, in main
from gui import application
  File "/usr/share/mypaint/gui/application.py", line 53, in 
import gui.device
  File "/usr/share/mypaint/gui/device.py", line 25, in 
import gui.mode
  File "/usr/share/mypaint/gui/mode.py", line 809, in 
class SingleClickMode (InteractionMode):
  File "/usr/share/mypaint/gui/mode.py", line 813, in SingleClickMode
cursor = gdk.Cursor(gdk.BOGOSITY)
  File "/usr/lib/python2.7/dist-packages/gi/overrides/Gdk.py", line 329,
in __new__
return cls.new(*args, **kwds)
TypeError: constructor returned NULL

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Just launch it

   * What was the outcome of this action?

It does not start (see backtrace above)

   * What outcome did you expect instead?

It should start.

Note: the bug was reported and fixed upstream some time ago.
I tried compiling mypaint 1.3.0-alpha (from upstream git repository) and
it works perfectly.

*** End of the template - remove these template lines ***


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

Kernel: Linux 4.9.0-2-amd64 (SMP w/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 mypaint depends on:
ii  gir1.2-gtk-3.0   3.22.9-4
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-9
ii  libcairo-gobject21.14.8-1
ii  libcairo21.14.8-1
ii  libgcc1  1:6.3.0-10
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.50.3-1
ii  libgomp1 6.3.0-10
ii  libgtk-3-0   3.22.9-4
ii  libjson-c3   0.12.1-1.1
ii  liblcms2-2   2.8-4
ii  libpango-1.0-0   1.40.4-1
ii  libpangocairo-1.0-0  1.40.4-1
ii  libpng16-16  1.6.28-1
ii  libpython2.7 2.7.13-2
ii  libstdc++6   6.3.0-10
ii  mypaint-data 1.2.0-4
ii  python-gi-cairo  3.22.0-2
ii  python-numpy 1:1.12.0-2
pn  python2.7:any
pn  python:any   

Versions of packages mypaint recommends:
ii  shared-mime-info  1.8-1

Versions of packages mypaint suggests:
ii  mypaint-data-extras  1.2.0-4

-- no debconf information

Bug#834218: Bug also in 4.7

[Ben Hutchings]

Control: tag -1 moreinfo

On Fri, 2017-03-10 at 09:13 +0100, Christoph Schwerdtfeger wrote:
> Hi there,
> 
> this case can be closed. Looks like something in 4.5 changed (it was
> reproducible in 4.8, 4.9 and 4.10-trunk) and the modules are not
> getting loaded automatically anymore.
> After adding the modules to /etc/modules everything works fine on my end.
> 
> Everything works again on my end!

Whichever module you actually need *should* still get loaded
automatically.  The change between 4.4 and 4.5 was this:

commit acc1c3c688ed8cc862ddc007eab0dcef839f4ec8
Author: Heiner Kallweit 
Date:   Mon Nov 16 17:52:26 2015 -0200

[media] media: rc: load decoder modules on-demand

Remove code for unconditional decoder module loading (except lirc).

This removed code that was loading *all* decoder modules.  But the code
to load specific decoder modules is still there.

Could you try this:

1. Create /etc/modprobe.d/rc-core-debug.conf containing the line:
   options rc-core debug=1
2. Reboot
3. Look for more messages from the RC core in the kernel log

Ben.

-- 
Ben Hutchings
In a hierarchy, every employee tends to rise to his level of
incompetence.



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

Bug#858956: firefox-esr: Geolocation seems to be broken

[Alejandro Carrazzoni]

Package: firefox-esr
Version: 52.0.1esr-1
Followup-For: Bug #858956

Geolocation works fine with upstream Firefox.



-- Package-specific info:

-- Extensions information
Name: Application Update Service Helper
Location: ${PROFILE_EXTENSIONS}/aushel...@mozilla.org.xpi
Status: enabled

Name: Cookies Manager+
Location: ${PROFILE_EXTENSIONS}/{bb6bc1bb-f824-4702-90cd-35e2fb24f25d}
Status: enabled

Name: Default theme
Location: 
/usr/lib/firefox-esr/browser/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}.xpi
Package: firefox-esr
Status: user-disabled

Name: Diccionario Español Argentina dictionary
Location: ${PROFILE_EXTENSIONS}/es...@dictionaries.addons.mozilla.org
Status: enabled

Name: DOM Inspector
Location: ${PROFILE_EXTENSIONS}/inspec...@mozilla.org
Status: enabled

Name: Emoji Cheatsheet for GitHub, Basecamp etc.
Location: ${PROFILE_EXTENSIONS}/jid1-xo5sua6qc1d...@jetpack.xpi
Status: enabled

Name: Español (AR) Language Pack locale
Location: 
/usr/lib/firefox-esr/browser/extensions/langpack-es...@firefox-esr.mozilla.org.xpi
Package: firefox-esr-l10n-es-ar
Status: enabled

Name: Grayfox theme
Status: enabled

Name: KeeFox
Location: ${PROFILE_EXTENSIONS}/keefox@chris.tomlinson
Status: enabled

Name: MEGA
Location: ${PROFILE_EXTENSIONS}/fire...@mega.co.nz.xpi
Status: enabled

Name: Multi-process staged rollout
Location: ${PROFILE_EXTENSIONS}/e10sroll...@mozilla.org.xpi
Status: enabled

Name: Personas Plus
Location: ${PROFILE_EXTENSIONS}/perso...@christopher.beard.xpi
Status: enabled

Name: Pocket
Location: ${PROFILE_EXTENSIONS}/fire...@getpocket.com.xpi
Status: enabled

Name: Roomy Bookmarks Toolbar
Location: ${PROFILE_EXTENSIONS}/alone-l...@ya.ru.xpi
Status: enabled

Name: Search by Image for Google
Location: ${PROFILE_EXTENSIONS}/{ab4b5718-3998-4a2c-91ae-18a7c2db513e}.xpi
Status: enabled

Name: Speed Dial
Location: ${PROFILE_EXTENSIONS}/{64161300-e22b-11db-8314-0800200c9a66}.xpi
Status: enabled

Name: Tab Mix Plus
Location: ${PROFILE_EXTENSIONS}/{dc572301-7619-498c-a57d-39143191b318}.xpi
Status: enabled

Name: uBlock Origin
Location: ${PROFILE_EXTENSIONS}/ublo...@raymondhill.net.xpi
Status: enabled

Name: User Agent Switcher
Location: ${PROFILE_EXTENSIONS}/{e968fc70-8f95-4ab9-9e79-304de2a71ee1}.xpi
Status: enabled

Name: Video DownloadHelper
Location: ${PROFILE_EXTENSIONS}/{b9db16a4-6edc-47ec-a1f4-b86292ed211d}.xpi
Status: user-disabled

Name: Web Compat
Location: ${PROFILE_EXTENSIONS}/webcom...@mozilla.org.xpi
Status: enabled

Name: YesScript
Location: ${PROFILE_EXTENSIONS}/yesscr...@userstyles.org.xpi
Status: enabled

-- Plugins information
Name: Google Talk Plugin
Location: /opt/google/talkplugin/libnpgoogletalk.so
Package: google-talkplugin
Status: enabled

Name: Google Talk Plugin Video Renderer
Location: /opt/google/talkplugin/libnpo1d.so
Package: google-talkplugin
Status: enabled

Name: Shockwave Flash (24.0.0.194)
Location: 
/usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so
Package: browser-plugin-freshplayer-pepperflash
Status: enabled


-- Addons package information
ii  browser-plugin 0.3.5-1+b1   amd64PPAPI-host NPAPI-plugin adapter f
ii  firefox-esr52.0.1esr-1  amd64Mozilla Firefox web browser - Ext
ii  firefox-esr-l1 52.0.1esr-1  all  Spanish (Argentina) language pack
ii  google-talkplu 5.41.3.0-1   amd64Google Talk Plugin

-- 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-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_AR.utf8, LC_CTYPE=es_AR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages firefox-esr depends on:
ii  debianutils   4.8.1
ii  fontconfig2.11.0-6.7+b1
ii  libasound21.1.3-5
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-9
ii  libcairo-gobject2 1.14.8-1
ii  libcairo2 1.14.8-1
ii  libdbus-1-3   1.10.16-1
ii  libdbus-glib-1-2  0.108-2
ii  libevent-2.0-52.0.21-stable-3
ii  libffi6   3.2.1-6
ii  libfontconfig12.11.0-6.7+b1
ii  libfreetype6  2.6.3-3+b2
ii  libgcc1   1:6.3.0-8
ii  libgdk-pixbuf2.0-02.36.5-2
ii  libglib2.0-0  2.50.3-1
ii  libgtk-3-03.22.9-3
ii  libgtk2.0-0   2.24.31-2
ii  libhunspell-1.4-0 1.4.1-2+b2
ii  libjsoncpp1   1.7.4-3
ii  libpango-1.0-01.40.4-1
ii  libsqlite3-0  3.16.2-3
ii  libstartup-notification0  0.12-4
ii  libstdc++66.3.0-8
ii  libvpx4   1.6.1-2
ii  libx11-6  2:1.6.4-3
ii  libx11-xcb1   2:1.6.4-3
ii  libxcb-shm0   1.12-1
ii  libxcb1   1.12-1
ii  libxcomposite11:0.4.4-2
ii  libxdamage1   1:1.1.4-2+b1
ii  

Bug#859063: weston: running 'weston --fullscreen' inside of weston causes bad RAM access

[mviereck]

Package: weston
Version: 1.12.0-3
Severity: normal

Dear Maintainer,

Steps to reproduce:
Start weston from console:
  weston
Inside of weston, open terminal and run
  weston --fullscreen

The nested weston crashes with bad RAM access.


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

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

Versions of packages weston depends on:
ii  adduser 3.115
ii  libc6   2.24-9
ii  libcairo2   1.14.8-1
ii  libcolord2  1.3.3-2
ii  libdrm2 2.4.74-1
ii  libegl1-mesa [libegl1-x11]  13.0.5-1
ii  libgles2-mesa [libgles2]13.0.5-1
ii  libglib2.0-02.50.3-1
ii  libinput10  1.6.3-1
ii  libjpeg62-turbo 1:1.5.1-2
ii  liblcms2-2  2.8-4
ii  libpam0g1.1.8-3.5
ii  libpango-1.0-0  1.40.4-1
ii  libpangocairo-1.0-0 1.40.4-1
ii  libpixman-1-0   0.34.0-1
ii  libpng16-16 1.6.28-1
ii  libsystemd0 232-19
ii  libwayland-client0  1.12.0-1
ii  libwayland-cursor0  1.12.0-1
ii  libwayland-egl1-mesa [libwayland-egl1]  13.0.5-1
ii  libwayland-server0  1.12.0-1
ii  libweston-1-0   1.12.0-3
ii  libxkbcommon0   0.7.1-1

Versions of packages weston recommends:
ii  libgl1-mesa-dri  13.0.5-1

weston suggests no packages.

-- no debconf information

Bug#845382: BUG: soft lockup when radeon modesetting

[Dominik George]

I can confirm this issue.

I found a workaround by setting radeon.hard_reset=1, which resets the PCI bus 
after loading the firmware. Both Audio and KMS work with this option set.

Bug#858405: Stable update request: kernel changes to fix PIE with large stack

[Ben Hutchings]

On Thu, 2017-03-23 at 21:27 +, Ben Hutchings wrote:
> On Thu, 2017-03-23 at 17:06 +, James Cowgill wrote:
[...]
> > I believe any of the following will fix this (but have not all been tested):
> > - Reduce the stack usage in xsltproc (the upstream bug)
> > - Upgrade the relevant buildds to Linux >= 4.1
> > - Apply d1fd836dcf00 to jessie's kernel
> 
> That's part of a series of 10 commits covering multiple architectures. 
> I already picked one of them as a dependency for fixing CVE-2016-3672,
> which leaves 9 to do.  I think it is worth doing this in stable to
> support chroots and partial upgrades, but I would like to hear the
> release team ack/nak this in principle before I start preparing the
> change for Debian stable.
> 
> Kees Cook quotes the list of commits here:
> http://lists.openwall.net/linux-kernel/2015/07/27/964
> (I can't find the original message).
[...]

The kernel bug report for this is #797530.

Ben.

-- 
Ben Hutchings
Everything should be made as simple as possible, but not simpler.
   - Albert
Einstein


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

Bug#848368: llvm-toolchain-3.9: Please add ELF symbols versions to the libraries

[Rebecca N. Palmer]

The patches in SVN have a bug: 4.0 is using LLVM_3.9 for libllvm 
(simple_version_script.map), though the correct LLVM_4.0 elsewhere 
(AddLLVM.cmake).


The override_dh_makeshlibs/1:x symbols minimum version are needed in all 
versions, not just 3.8.



Also, #857623 (the OpenCL bug) also affects 3.8 and 4.0; the same fix
should work.

This has not yet been done.

Bug#858783: Synaptics Touchpad of Thinkpad X230 not working correctly with Kernel 4.9

[Ben Hutchings]

Control: tag -1 moreinfo

On Sun, 2017-03-26 at 21:00 +0200, Florian Roth wrote:
> Package: linux-image-4.9.0-2-amd64
> Version: 4.9.13-1
> 
> The synaptics touchpad of my X230 thinkpad stopped working as expected
> after upgrading to kernel 4.9.
> All the "touchpad features" are lost and it operates in generic
> pointing device mode. (no tap, no two finger scrolling, no two finger
> tap right click)
> 
> I compared the output of /var/log/Xorg.0.log in both versions:
[...]

We need the kernel log for a kernel bug report.  This should find the
relevant messages:

sudo zgrep -Ei  'kernel:.*(input|mouse|synaptics)' /var/log/messages*

Ben.

-- 
Ben Hutchings
Everything should be made as simple as possible, but not simpler.
   - Albert
Einstein


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

Bug#832128: freespace2: Bad symlinks /usr/games/fs2_open{,_DEBUG}

[Simon McVittie]

On Wed, 29 Mar 2017 at 21:27:26 +1100, Dmitry Smirnov wrote:
> On Wednesday, 29 March 2017 8:42:38 AM AEDT Simon McVittie wrote:
> > Please ask the release team to remove it if that's the case.
> 
> It is already scheduled for removal because of this bug's severity...

If you don't want it in stable, waiting for autoremoval leaves the bug
on the lists seen by people doing bug squashing (like me in this case),
whereas asking for it to be removed would take it off those lists sooner.

> > I've cancelled my delayed NMU.
> 
> OK. So you've decided not to save the package for stable? Fair enough.

You said "I'd rather drop it from Stretch" which I thought meant you
specifically didn't want it to be saved, so I went along with what I
thought was your request as maintainer. Was that a misinterpretation?

I can NMU or not NMU, whichever you prefer; please let me know. You're also
welcome to apply the patch that I attached a couple of messages ago if you
want to do a MU.

I'm not going to upload a new upstream version or other larger changes,
because I don't think the release team are likely to accept an upload not
based on 3.7.2+repack during the freeze.

S

Bug#859062: Apache2 segfaults when using ProxySet in a ProxyMatch block

[Alain Knaff]

Package: apache2
Version: 2.4.10-10+deb8u8

Hi,

The following config causes a segmentation fault:


  ProxySet connectiontimeout=86400 timeout=86400
  ...



==>
# systemctl status apache2.service -l
...
Mar 29 07:35:02 mysite systemd[1]: Reloaded LSB: Apache2 web server.
Mar 29 23:47:46 mysite systemd[1]: Reloading LSB: Apache2 web server.
Mar 29 23:47:46 mysite apache2[6157]: Reloading web server: apache2 failed!
Mar 29 23:47:46 mysite apache2[6157]: The apache2 configtest failed. Not doing 
anything. ... (warning).
Mar 29 23:47:46 mysite apache2[6157]: Output of config test was:
Mar 29 23:47:46 mysite apache2[6157]: Segmentation fault
Mar 29 23:47:46 mysite apache2[6157]: Action 'configtest' failed.
Mar 29 23:47:46 mysite apache2[6157]: The Apache error log may have more 
information.
Mar 29 23:47:46 mysite systemd[1]: apache2.service: control process exited, 
code=exited status=1

Thanks,

Alain

Bug#859061: gr-rds: GRC RDS Panel will not build in scripts w/ QT_GUI mode selected

[Christopher]

Package: gr-rds
Version: 3.7.0.2.a542331-1+b2
Severity: important
Tags: newcomer

Dear Maintainer,

RDS Panel block does not support QT panel?  I built a simple FM RDS decoder w/ 
RDS Panel block and WX_GUI selected, decodes as expected.  Setting options to 
QT_GUI and incorporating 'RDS Panel' block fails compile and throws trace.  
Changing GUI back to WX returns functionality, will compile & exec w/o issue. 


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

Kernel: Linux 4.9.0redux (SMP w/2 CPU cores; PREEMPT)
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 gr-rds depends on:
ii  gnuradio-dev   3.7.10.1-2+b3
ii  libboost-system1.62.0  1.62.0+dfsg-4
ii  libc6  2.24-8
ii  libgcc11:6.2.1-5
ii  libgnuradio-pmt3.7.10  3.7.10.1-2+b1
ii  libgnuradio-rds3.7.10  3.7.0.2.a542331-1+b2
ii  libgnuradio-runtime3.7.10  3.7.10.1-2+b1
ii  libpython2.7   2.7.13~rc1-1
ii  libstdc++6 6.2.1-5

gr-rds recommends no packages.

gr-rds suggests no packages.

-- no debconf information

Bug#810988: po4a: Always fuzzies one string, even if translation is correct (German goobox man page)

[Martin Quinson]

Hello,

I did not fix it yet, but I fixed the warning (Redundant argument in
sprintf) and improved the error message. Now it reads:

$ LC_ALL=C po4a -v -f debian/po4a.cfg 
Updating debian/manpage//goobox.pot:
po4a::sgml: msgid skipped to help translators (contains only tags)
po4a::sgml: msgid skipped to help translators (contains only an entity)
po4a::sgml: msgid skipped to help translators (contains only an entity)
po4a::sgml: msgid skipped to help translators (contains only tags)
po4a::sgml: Warning: onsgmls produced some errors.  This is usually
caused by po4a, which modifies the input and restores it
afterwards, causing the input of onsgmls to be 
invalid.  This is usually safe, but you may wish to verify
the generated document with onsgmls -wno-valid.
po4a::sgml: To see the error message, rerun po4a with this additional argument:
   -o debug=onsgmls
(108 entries)
Updating debian/manpage//de.po: 
 done.
debian/manpage//de.po: 107 translated messages, 1 fuzzy translation.
po4a::sgml: msgid skipped to help translators (contains only tags)
po4a::sgml: msgid skipped to help translators (contains only an entity)
po4a::sgml: msgid skipped to help translators (contains only an entity)
po4a::sgml: msgid skipped to help translators (contains only tags)
po4a::sgml: Warning: onsgmls produced some errors.  This is usually
caused by po4a, which modifies the input and restores it
afterwards, causing the input of onsgmls to be 
invalid.  This is usually safe, but you may wish to verify
the generated document with onsgmls -wno-valid.
po4a::sgml: To see the error message, rerun po4a with this additional argument:
   -o debug=onsgmls
debian/manpage/goobox.de.sgml is 99.08% translated (108 of 109 strings).


Adding -o debug=onsgmls as advised, this extra information appears:
$ LC_ALL=C po4a -v -f debian/po4a.cfg -o debug=onsgmls
Updating debian/manpage//goobox.pot:
read(debian/manpage/goobox.en.sgml)...done.
parse...CMD=onsgmls -l -E 0 -wno-valid < /tmp/po4a-7B4E.sgml |
onsgmls:0:41:1:E: start tag for "REFENTRYTITLE" omitted, but its 
declaration does not permit this
po4a::sgml: msgid skipped to help translators (contains only tags)
[...]

Does it help you to fix the issue, maybe? Or does it seem unrelated?
I think I never used nsgml myself...


Thanks for your help, 
Mt.

-- 
Les esprits sont comme les parachutes, ils ne fonctionnent que
lorsqu'ils sont ouverts. --- Pierre Desproges


signature.asc
Description: PGP signature

Bug#856984: fis-gtm: please enable openssl support

[Shah, Amul]

If I understood your question correctly, you are asking for the fis-gtm package 
to either enable openssl OR drop the libssl-dev requirement.

We dropped the openssl using encryption plugin libraries from the distributed 
package because of the "openssl advertising clause". To work around the 
advertising clause, we distribute our encryption plugin libraries as source, 
letting the end users that desire encryption support compile it for themselves. 
So we can't enable openssl.

The fis-gtm package builds the encryption plugin sources as a compatibility 
test build. That compatibility test build alerted us to the upcoming changes in 
openssl 1.1. So we won't drop the libssl-dev requirement.

If the above makes sense, I would like to close this bug. If you have some 
other option, let me know.

Thanks,
Amul

The information contained in this message is proprietary and/or confidential. 
If you are not the intended recipient, please: (i) delete the message and all 
copies; (ii) do not disclose, distribute or use the message in any manner; and 
(iii) notify the sender immediately. In addition, please be aware that any 
message addressed to our domain is subject to archiving and review by persons 
other than the intended recipient. Thank you.

Bug#859060: ITP: python-flask-socketio -- Socket.IO integration for Flask applications

[Paulo Henrique de Lima Santana (phls)]

Package: wnpp
Severity: wishlist
Owner: "Paulo Henrique de Lima Santana (phls)" 

* Package name: flask-socketio
  Version : 2.8.6
  Upstream Author : Miguel Grinberg 
* URL : https://github.com/miguelgrinberg/Flask-SocketIO
* License : MIT
  Programming Lang: Python
  Description : Socket.IO integration for Flask applications
 Flask-SocketIO gives Flask applications access to low latency bi-directional
 communications between the clients and the server. The client-side
 application can use any of the SocketIO official clients libraries in
 Javascript, C++, Java and Swift, or any compatible client to establish a
 permanent connection to the server.

Bug#858742: libvirt: [INTL:pt] Updated Portuguese translation for debconf messages

[TRADUZ - DebianPT]

Several minor corrections to the PT translation sent.

Regards,
Rui Branco

--
Best regards,

"Traduz" - Portuguese Translation Team
http://www.DebianPT.org

# Portuguese translation for libvirt(debconf)
# This file is distributed under the same license as the libvirt package.
# Rui Branco , 2017.
#
msgid ""
msgstr ""
"Project-Id-Version: libvirt 3.0.0-3\n"
"Report-Msgid-Bugs-To: libv...@packages.debian.org\n"
"POT-Creation-Date: 2016-12-22 14:20+0100\n"
"PO-Revision-Date: 2017-03-14 19:44+\n"
"Last-Translator: Rui Branco \n"
"Language-Team: Portuguese \n"
"Language: pt\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
"X-Generator: Gtranslator 2.91.7\n"

#. Type: boolean
#. Description
#: ../libvirt-daemon-system.templates:1001
msgid "Continue with incorrect libvirt-qemu user/group ID(s)?"
msgstr "Continuar com o ID(s) de libvirt-qemu user/group incorrecto(s)?"

#. Type: boolean
#. Description
#: ../libvirt-daemon-system.templates:1001
msgid ""
" The user/group ID (uid/gid) allocated for libvirt-qemu (64055)\n"
" seems to be taken by another user/group, thus it is not possible\n"
" to create the user/group with this numeric ID."
msgstr ""
" O ID (uid/gid) do utilizador/grupo alocado para libvirt-qemu \n"
" (64055)  parece ter sido tomado por outro utilizador/grupo, \n"
" tornando impossível criar o utilizador/grupo com este ID \n"
" numérico."

#. Type: boolean
#. Description
#: ../libvirt-daemon-system.templates:1001
msgid ""
" The migration of guests with disk image files shared over NFS\n"
" requires a static libvirt-qemu user and group ID (uid and gid)\n"
" between the source and destination host systems."
msgstr ""
" A migração de convidados com ficheiros de imagem de disco partilhados\n"
" por NFS requer um ID estático de utilizador e de grupo (uid e gid) do \n"
" libvirt-qemu entre a fonte e o destino dos sistemas anfitriões."

#. Type: boolean
#. Description
#: ../libvirt-daemon-system.templates:1001
msgid ""
" If guest migration over NFS is not required, you can continue\n"
" the installation."
msgstr ""
" Se não for necessária a migração de convidado sobre NFS, pode\n"
" continuar a instalação."

#. Type: boolean
#. Description
#: ../libvirt-daemon-system.templates:1001
msgid ""
" In order to resolve this problem, do not continue the installation,\n"
" release the 64055 uid/gid (which might involve permission changes),\n"
" then install this package again."
msgstr ""
" De modo a resolver este problema, não continue a instalação, liberte o\n"
" uid/gid 64055 (pode envolver alterações nas permissões) e volte\n"
" então a instalar este pacote novamente."

Bug#858653: dokuwiki: [INTL:pt] Updated Portuguese translation for debconf messages

[TRADUZ - DebianPT]

Minor correction on PT translation sent.

--
Best regards,

"Traduz" - Portuguese Translation Team
http://www.DebianPT.org

# Portuguese translation of dokuwiki debconf messages.
# This file is distributed under the same license as the dokuwiki package. 
# Rui Branco , 2006, 2010,2011,2017, 2017.
#
msgid ""
msgstr ""
"Project-Id-Version: dokuwiki 0.0.20160626.a-1\n"
"Report-Msgid-Bugs-To: dokuw...@packages.debian.org\n"
"POT-Creation-Date: 2013-10-27 19:00+0100\n"
"PO-Revision-Date: 2017-03-14 13:27+\n"
"Last-Translator: Rui Branco \n"
"Language-Team: Portuguese \n"
"Language: Portuguese\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

#. Type: multiselect
#. Choices
#: ../templates:1001
msgid "apache2"
msgstr "apache2"

#. Type: multiselect
#. Choices
#: ../templates:1001
msgid "lighttpd"
msgstr "lighttpd"

#. Type: multiselect
#. Description
#: ../templates:1002
msgid "Web server(s) to configure automatically:"
msgstr "Servidor(es) web a configurar automaticamente:"

#. Type: multiselect
#. Description
#: ../templates:1002
msgid ""
"DokuWiki runs on any web server supporting PHP, but only listed web servers "
"can be configured automatically."
msgstr ""
"O DokuWiki corre em qualquer servidor web que suporte PHP, mas apenas "
"servidores web existentes na lista podem ser automaticamente configurados."

#. Type: multiselect
#. Description
#: ../templates:1002
msgid ""
"Please select the web server(s) that should be configured automatically for "
"DokuWiki."
msgstr ""
"Por favor seleccione o(s) servidor(es) web que deverá ser configurado "
"automaticamente para o DokuWiki."

#. Type: boolean
#. Description
#: ../templates:2001
msgid "Should the web server(s) be restarted now?"
msgstr "Deve o(s) servidor(es) web ser reiniciado agora?"

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"In order to activate the new configuration, the reconfigured web server(s) "
"have to be restarted."
msgstr ""
"Para activar a nova configuração, o(s) servidor(s) web reconfigurado deve "
"ser reiniciado."

#. Type: string
#. Description
#: ../templates:3001
msgid "Wiki location:"
msgstr "Local do Wiki:"

#. Type: string
#. Description
#: ../templates:3001
msgid ""
"Specify the directory below the server's document root from which DokuWiki "
"should be accessible."
msgstr ""
"Especifique o directório abaixo da raiz de documentos do servidor a partir "
"do qual o DokuWiki deve ser acessível."

#. Type: select
#. Description
#: ../templates:4001
msgid "Authorized network:"
msgstr "Rede autorizada:"

#. Type: select
#. Description
#: ../templates:4001
msgid ""
"Wikis normally provide open access to their content, allowing anyone to "
"modify it. Alternatively, access can be restricted by IP address."
msgstr ""
"Os wikis normalmente fornecem acesso aberto ao seu conteúdo, permitindo que "
"qualquer pessoa o possa modificar. Alternativamente, o acesso pode ser "
"restrito ao endereço IP."

#. Type: select
#. Description
#: ../templates:4001
msgid ""
"If you select \"localhost only\", only people on the local host (the machine "
"the wiki is running on) will be able to connect. \"local network\" will "
"allow people on machines in a local network (which you will need to specify) "
"to talk to the wiki. \"global\" will allow anyone, anywhere, to connect to "
"the wiki."
msgstr ""
"Se seleccionar 'apenas máquina local', apenas pessoas a trabalhar na máquina "
"local (a máquina em que o Wiki está a correr) se poderão ligar.  A opção "
"'rede local ' permitirá pessoas em máquinas da rede local (que terá de "
"especificar) comunicar com o Wiki.  A opção 'global' permitirá a qualquer "
"pessoa em qualquer local, ligar-se ao Wiki."

#. Type: select
#. Description
#: ../templates:4001
msgid ""
"The default is for site security, but more permissive settings should be "
"safe unless you have a particular need for privacy."
msgstr ""
"A predefinição consiste na segurança do site, no entanto definições mais "
"permissivas deverão ser seguras a não ser que necessite de um nível particular "
"de segurança."

#. Type: select
#. Choices
#: ../templates:4002
msgid "localhost only"
msgstr "apenas localhost"

#. Type: select
#. Choices
#: ../templates:4002
msgid "local network"
msgstr "rede local"

#. Type: select
#. Choices
#: ../templates:4002
msgid "global"
msgstr "global"

#. Type: string
#. Description
#: ../templates:5001
msgid "Local network:"
msgstr "Rede local:"

#. Type: string
#. Description
#: ../templates:5001
msgid ""
"The specification of your local network should either be an IP network in "
"CIDR format (x.x.x.x/y) or a domain specification (like .example.com)."
msgstr ""
"A especificação da sua rede local deverá ser, ou uma rede de IP no formato "
"CIDR (x.x.x.x/y), ou uma especificação de domínio (tal como 

Bug#859029: Acknowledgement (po4a: [INTL:de] updated German man page translation)

[Martin Quinson]

package po4a
tag 859029 fixed-upstream
thanks

Hello,

On Wed, Mar 29, 2017 at 07:44:51PM +0200, Helge Kreutzmann wrote:
> 
> Hello,
> btw. is the SVN repository still the main one?

actually, no. I'm using a git nowadays. Or even better: 2 of them.
https://alioth.debian.org/projects/po4a/
https://github.com/mquinson/po4a

Thank you for your translation. I integrated it, but things moved
already: 1470 translated messages, 14 fuzzy translations, 4
untranslated messages. Here is the current version:

https://alioth.debian.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=po4a/po4a.git;a=blob_plain;f=po/pod/de.po;hb=HEAD

Bye, Mt.

-- 
How could I agree to use this computational contribution when I can do 
the same by hand in less time?-- Bastard Reviewer From Hell


signature.asc
Description: PGP signature

Bug#760072: gitso crashes with assertion failure on client side

[Florian Schlichting]

Hi Tim,

> connecting to a supporter leads to a crash with assertion failure, leaving the
> supportee without the possibility to cleanly terminate the session. Please 
> have
> a look at the attached console log.

I never experienced such a problem, do you have an idea about the
circumstances it occurs in, like a second person/process trying to
connect to the supporter?

> guyintrouble@hiscomputer:~$ gitso
> 31/08/2014 15:22:52 x11vnc version: 0.9.13 lastmod: 2011-08-10  pid: 6086
...
> [xcb] Unknown sequence number while processing queue
> [xcb] Most likely this is a multi-threaded client and XInitThreads has not 
> been called
> [xcb] Aborting, sorry about that.
> python: ../../src/xcb_io.c:274: poll_for_event: Zusicherung 
> »!xcb_xlib_threads_sequence_lost« nicht erfüllt.

this doesn't come from gitso itself, but one of its dependencies -
we could try asking the x11vnc maintainer about this...

Florian

Bug#859059: keyboard-configuration: many mac keymap in keyboard-configuration are faulty

[raphael]

Package: keyboard-configuration
Version: 1.160
Severity: important

Hi,

I have a macbook pro with us keymap, I tried different layouts available in 
keyboard-configuration to get accents, but ended with
Can not find "mac" in "macintosh_vndr/us". or Can not find "altgr-intl" in 
"macintosh_vndr/us".
and No Symbols named "altgr-intl" in the include file "macintosh_vndr/us" or No 
Symbols named "mac" in the include file "macintosh_vndr/us"

I ended up copying the altgr part of the pc keyboard (found in 
/usr/share/X11/xkb/symbols) to the macintosh one.
I already had the same kind of problem with mac french azerty keyboard.
I think either the /usr/share/X11/xkb/symbols/macintosh_vndr files should be 
corrected or choices in the keyboard-configuration setup reduced to what's 
really available (it took me quite a long time to understand why I couldn't get 
the accents though everything looked fine).

Thanks

Raphael

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (650, 'testing'), (300, 'unstable'), (100, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages keyboard-configuration depends on:
ii  debconf 1.5.60
ii  liblocale-gettext-perl  1.07-3+b1

keyboard-configuration recommends no packages.

keyboard-configuration suggests no packages.

Versions of packages console-setup depends on:
ii  console-setup-linux  1.160
ii  debconf  1.5.60
ii  xkb-data 2.19-1

Versions of packages console-setup suggests:
ii  locales   2.24-9
ii  lsb-base  9.20161125

Versions of packages console-setup-linux depends on:
ii  init-system-helpers  1.47
ii  initscripts  2.88dsf-59.9
ii  kbd  2.0.3-2+b1

Versions of packages console-setup-linux suggests:
ii  console-setup  1.160

Versions of packages keyboard-configuration is related to:
pn  console-common
pn  console-data  
pn  console-tools 
pn  gnome-control-center  
ii  kbd   2.0.3-2+b1
ii  systemd   232-19

-- debconf information:
* keyboard-configuration/ctrl_alt_bksp: true
* keyboard-configuration/store_defaults_in_debconf_db: true
  console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic 
languages
  console-setup/store_defaults_in_debconf_db: true
* keyboard-configuration/other:
  keyboard-configuration/unsupported_options: true
  console-setup/codesetcode: Lat15
* keyboard-configuration/switch: No temporary switch
* keyboard-configuration/altgr: The default for the keyboard layout
* console-setup/fontface47: Terminus
  keyboard-configuration/unsupported_config_options: true
  console-setup/guess_font:
* console-setup/fontsize-fb47: 8x16
  console-setup/framebuffer_only:
  console-setup/fontsize: 8x16
  debian-installer/console-setup-udeb/title:
* keyboard-configuration/layoutcode: us
* keyboard-configuration/layout:
  keyboard-configuration/unsupported_config_layout: true
* keyboard-configuration/xkb-keymap: us(altgr-intl)
  console-setup/charmap47: UTF-8
  keyboard-configuration/unsupported_layout: true
* keyboard-configuration/toggle: No toggling
  console-setup/fontsize-text47: 8x16
* keyboard-configuration/variantcode: altgr-intl
  console-setup/use_system_font:
* keyboard-configuration/modelcode: macbook79
* keyboard-configuration/optionscode: terminate:ctrl_alt_bksp
* keyboard-configuration/compose: No compose key
* keyboard-configuration/model: MacBook/MacBook Pro (Intl)
* keyboard-configuration/variant: Anglais (US) - Anglais (touches mortes 
internationales via AltGr)

Bug#859058: telegram-desktop: FTBFS in i386

[Mattia Rizzolo]

Source: telegram-desktop
Version: 1.0.14-1
Severity: important

telegram-desktop FTBFS on i386:

   dh_install -a -O--sourcedirectory=out/Release
Failed to copy 'obj-i386-linux-gnu/Telegram': No such file or directory at 
/usr/share/dh-exec/dh-exec-install-rename line 51, <> line 1.
dh_install: debian/install (executable config) returned exit code 127
debian/rules:30: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 127
dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit 
status 2

https://buildd.debian.org/status/fetch.php?pkg=telegram-desktop=i386=1.0.14-1=1490812364=0

-- 
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#859057: telegram-desktop: FTBFS everywhere but x86

[Mattia Rizzolo]

Source: telegram-desktop
Version 1.0.14-1
Severity: important
Tags: upstream
Forwarded: https://github.com/telegramdesktop/tdesktop/issues/3167

Telegram FTBFS everywhere but amd64 and i386 and x32

https://buildd.debian.org/status/package.php?p=telegram-desktop

I find it incredible, and as such complained to upstream, but it's so
absurd to me that I'm making noise here in the Debian bug tracker too.

-- 
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#760071: gitso: Gui obstructs buttons

[Florian Schlichting]

Hi Tim, Andreas and carlchen,

> Using Xfce the buttons in the gitso gui gets obstructed. Please see attached
> screen shot.

I'm sorry I haven't had an answer for you in several years, the reason
is not that you're doing anything wrong but rather that I don't have a
clue what's going wrong or how to reproduce your issue.

- Have you tried resizing the window you get (point the mouse at that
  1px wide lower/right border and drag it outwards)

- Could you have a look at the code (ConnectionWindows.py looks relevant)
  and play around with the width and height values, to find what would
  be right for you? Do you have a high-DPI display, or use larger fonts
  or something that would cause a fixed-width (in pixel) window to be
  too small?
  (to do that, you can just 'apt-get source gitso' and from the
  resulting directory run 'python Gitso.py' ignoring the error about
  icon.ico)

Florian

Bug#842246: Bug#795253: [debhelper-devel] Bug#795253: Bug#795253: Add support for Meson build system

[Niels Thykier]

Mattia Rizzolo:
> [ dropping #795253 (about adding meson) from the recipients ]
> 
> On Wed, Mar 29, 2017 at 06:14:00AM +, Niels Thykier wrote:
>> FYI: The primary thing keeping me back from merging dh-autoreconf fully
>> is the optional patching to "libtool".  If we can have that merged into
>> libtool itself, I am happy to completely integrate dh-autoreconf.
> 
> Is there a bug for this somewhere?
> From what I can see libtool bugs are screaming to be triaged, and I
> can't find anything useful there just by skimming the subjects.
> 

It is #347650. Allegedly, upstream is rather positive about it provided
someone cleaned it up and finished it, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=347650#65

Unfortunately, that never happened in the past 10-11 years.

Thanks,
~Niels

Bug#859027: telegram-desktop: Incomplete debian/copyright?

[Mattia Rizzolo]

On Wed, Mar 29, 2017 at 06:18:35PM +0100, Chris Lamb wrote:
> I just ACCEPTed telegram-desktop from NEW but noticed it was missing 
> attribution in debian/copyright for at least:
> 
>   Telegram/Patches/qtbase_5_6_2.diff
>   debian/patches/Avoid-depending-on-static-libraries.patch

About this last one, this remark is about the change of copyright that
is done in the patch.  Please add a comment in d/copyright about it.

Actually, Nicholas, what's the state of your endeavour to improve the
upstream situation, and reduce the patching done on the Debian site?

-- 
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#834686: ruby-httpclient: diff for NMU version 2.7.1-1.1

[Paul Gevers]

Control: tags 834686 + patch

Dear maintainer,

I've prepared an NMU for ruby-httpclient (versioned as 2.7.1-1.1). The
diff is below (sorry for in-line, nmudiff failed to work properly for me).

Due to the nature of the bug and the current freeze, I'll upload after
sending this e-mail.

Regards.
diff -Nru ruby-httpclient-2.7.1/debian/changelog
ruby-httpclient-2.7.1/debian/changelog
--- ruby-httpclient-2.7.1/debian/changelog  2016-02-29
21:18:36.0 +0100
+++ ruby-httpclient-2.7.1/debian/changelog  2017-03-29
20:38:15.0 +0200
@@ -1,3 +1,12 @@
+ruby-httpclient (2.7.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Update 0001-Fix-port-allocation-in-tests.patch and
+0003-Try-to-wait-until-socket-is-free.patch to include missing
+instances of port 0 added in upstream 2.6.0.1-1~exp1 (Closes: #834686)
+
+ -- Paul Gevers   Wed, 29 Mar 2017 20:38:15 +0200
+
 ruby-httpclient (2.7.1-1) unstable; urgency=medium

   * New upstream release
diff -Nru
ruby-httpclient-2.7.1/debian/patches/0001-Fix-port-allocation-in-tests.patch
ruby-httpclient-2.7.1/debian/patches/0001-Fix-port-allocation-in-tests.patch
---
ruby-httpclient-2.7.1/debian/patches/0001-Fix-port-allocation-in-tests.patch
   2016-02-29 21:18:36.0 +0100
+++
ruby-httpclient-2.7.1/debian/patches/0001-Fix-port-allocation-in-tests.patch
   2017-03-29 20:38:15.0 +0200
@@ -83,3 +83,23 @@
:AccessLog => [],
:DocumentRoot => DIR,
:SSLEnable => true,
+@@ -293,7 +293,7 @@ private
+ @server = WEBrick::HTTPServer.new(
+   :BindAddress => "localhost",
+   :Logger => logger,
+-  :Port => 0,
++  :Port => 50001,
+   :AccessLog => [],
+   :DocumentRoot => DIR,
+   :SSLEnable => true,
+--- a/test/test_jsonclient.rb
 b/test/test_jsonclient.rb
+@@ -69,7 +69,7 @@ class TestJSONClient < Test::Unit::TestC
+ @server = WEBrick::HTTPServer.new(
+   :BindAddress => "localhost",
+   :Logger => @logger,
+-  :Port => 0,
++  :Port => 5,
+   :AccessLog => [],
+   :DocumentRoot => File.dirname(File.expand_path(__FILE__))
+ )
diff -Nru
ruby-httpclient-2.7.1/debian/patches/0003-Try-to-wait-until-socket-is-free.patch
ruby-httpclient-2.7.1/debian/patches/0003-Try-to-wait-until-socket-is-free.patch
---
ruby-httpclient-2.7.1/debian/patches/0003-Try-to-wait-until-socket-is-free.patch
   2016-02-29 21:18:36.0 +0100
+++
ruby-httpclient-2.7.1/debian/patches/0003-Try-to-wait-until-socket-is-free.patch
   2017-03-29 20:38:15.0 +0200
@@ -112,3 +112,24 @@
end

def setup_server_with_ssl_version(ssl_version)
+@@ -310,6 +313,9 @@ private
+   )
+ end
+ @server_thread = start_server_thread(@server)
++  rescue Errno::EADDRINUSE
++sleep 1
++retry
+   end
+
+   def do_hello(req, res)
+--- a/test/test_jsonclient.rb
 b/test/test_jsonclient.rb
+@@ -76,5 +76,8 @@ class TestJSONClient < Test::Unit::TestC
+ @serverport = @server.config[:Port]
+ @server.mount('/json', JSONServlet.new(@server))
+ @server_thread = start_server_thread(@server)
++  rescue Errno::EADDRINUSE
++sleep 1
++retry
+   end
+ end



signature.asc
Description: OpenPGP digital signature

Bug#858800: RFS: xtrs/4.9d-1 [ITA]

[Sean Whitton]

Hello Branden,

On Tue, Mar 28, 2017 at 08:29:38PM -0400, G. Branden Robinson wrote:
> > On Tue, Mar 28, 2017 at 05:28:25PM -0400, G. Branden Robinson wrote:
> > > So my goals were, in this order:
> > > 1) Get the package suitable for unstable (which it wasn't); then
> > > 2) Get the package suitable for testing.
>
> It'll be suitable for testing for Buster, that's for sure.  My bad luck
> to return during a release freeze.

Right.  But your wording ("then") suggested that (2) could be done
exclusively of (1).

> I'm interested in the least-effort solution (for other people) that
> doesn't involve shipping a badly broken package in Stretch.

Well, letting it drop out of testing is technically the least-effort
solution.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#859056: diffoscope: Please add support for .docx and .odt files

[Chris Lamb]

tags 859056 + pending
thanks

Fixed in Git:

  
https://anonscm.debian.org/git/reproducible/diffoscope.git/commit/?id=5d96a92c783ddc595e840784b6630e654dc60c09


Regards,

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

Bug#857041: jessie-pu: package vim/2:7.4.488-7+deb8u3

[Adam D. Barratt]

Control: tags -1 + pending

On Thu, 2017-03-09 at 19:19 +, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Tue, 2017-03-07 at 08:02 -0500, James McCoy wrote:
> > This upload would fix two no-dsa CVEs (CVE-2017-6349, CVE-2017-6350) for
> > Vim.  Debdiff attached.
> 
> Please go ahead.

Uploaded and flagged for acceptance.

Regards,

Adam

Bug#761945: fixing links for DLAs in the security tracker

[Antoine Beaupré]

On 2017-03-29 17:02:44, Salvatore Bonaccorso wrote:
> Hi Antoine,

Hi!

> If you want to look at this part: There is a ./parse-dla.pl script in
> the webwml CVS, which is used to import the DLAs (this is an
> analogeous script to parse-advisory.pl which is used to import the
> DSAs).

I see... The scripts are in /english/security for anyone looking. And if
people are (like me) thinking "... wat.. CVS?" then yes, we are still
using this:

https://www.debian.org/devel/website/using_cvs

My cvs commandline finger memory is *definitely* still there though, so
that works for me. :)

> The "manual" steps one would perform are roughly:
>
> ./parse-dla.pl $message
> cvs add $year/dla-$nr.{wml,data}
> cvs commit -m '[DLA $nr] $source security update'

Is this something the security team performs as part of the DSA release
process? Or is this something the debian-www people do? I guess you need
write access to the repository and I see that *you* do, but is this
expected from everyone working on releasing public advisories, the same
way we need access to the security tracker?

And to import older entries, we'll need the original templates, which we
deliberately did *not* commit anywhere, so they are basically available
only as mailing list archives, and thus hard to find automatically.

I foresee difficulties in importing the missing data...

Here's the bits that are missing:

 * the last DLA on the website is DLA-445-2, which is basically the last
   DLA before squeeze support ended and wheezy was handed over

 * among those 445 DLAs, there are actually 31 missing:

   webwml$ cd english/security/; find -name 'dla-*.wml' | wc -l
   424

 * even worse, it seems there are at least 20 advisories missing from
   the website because regression uploads hide advisories, because our
   naming convention differs from DSA ("DLA-XXX-N", where XXX is the
   original advisory and N are regression updates)

   $ grep DLA- data/DLA/list | sed 's/.* DLA-//;s/ .*//' | sort -n | sed 
'/445-2/,$d' | wc -l
   465

 * the canonical list has 928 advisories:

   secure-testing$ grep DLA- data/DLA/list | wc -l 
   928

So, lots of work there.

> The background work leading to that was done by Frank Lichtenheld in
> #762255.

Great to see that! It does seem problematic to import regression updates
however.

> having something on the debian- side which does this
> automatically, once a DSA or DLA arrives would help surely the
> debian-www team who then "only" have to do the translations and fix
> obvious mistakes. OTOH keep in mind: When the debian- team imports
> a DSA or DLA they may need to do some adjustments so, I'm not sure if
> it's liked to have the automatism, since sometimes before cvs commit
> some changes need to be done on the .wml file. 

It looks like this is something that should be discussed with the www
people... Maybe a bug against www.debian.org?

This begs the question, however - wouldn't it be simpler to import those
advisories in the security tracker directly?

At least, we should figure out why the imports have ceased after
wheezy-LTS started...

> Writing the above a bit in a hurry let me know if unclear what I
> meant.

Thanks for the response!

A.

-- 
What this country needs is more unemployed politicians.
- Angela Davis

Bug#858028: jessie-pu: package libvirt/1.2.9-9+deb8u4

[Adam D. Barratt]

Control: tags -1 + pending

On Sun, 2017-03-19 at 19:05 +0100, Guido Günther wrote:
> On Sun, Mar 19, 2017 at 05:05:13PM +, Adam D. Barratt wrote:
> > Control: tags -1 + confirmed
> > 
> > On Fri, 2017-03-17 at 15:10 +0100, Guido Günther wrote:
> > > I'd like to update libvirt in jessie since the current one doesn't work
> > > with recent QEMU 2.6 (as the one in backports). It needs a single patch
> > > to to not generate QEMU invocationst that aren't understood by newer
> > > QEMU.
> > 
> > Please go ahead.
> 
> Uploaded. Thanks a lot!

Flagged for acceptance, thanks.

Regards,

Adam

Bug#858130: jessie-pu: package wget/1.16-1+deb8u2

[Adam D. Barratt]

Control: tags -1 + pending

On Sun, 2017-03-19 at 16:45 +, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Sat, 2017-03-18 at 18:44 +0100, Noël Köthe wrote:
> > wget 1.16-1+deb8u2 fixes CVE-2017-6508 (no-dsa) with the upstream patch.
> > https://security-tracker.debian.org/tracker/CVE-2017-6508
> 
> Please go ahead.

Uploaded and flagged for acceptance.

Regards,

Adam

Bug#856832: jessie-pu: package webissues-server/0.8.5-3+deb8u1

[Adam D. Barratt]

Control: tags -1 + pending

On Thu, 2017-03-09 at 20:06 +, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Sun, 2017-03-05 at 11:10 +0100, Andreas Beckmann wrote:
> > I'd like to update webissues-server in jessie to fix its unconditional
> > usage of ucf during postrm purge. This is the last package triggering
> > this bug after piuparts (upgrade) tests. Like ndoutils, the package
> > has been removed from unstable, therefore it can be fixed in stable
> > only.
> 
> Please go ahead.

Uploaded and flagged for acceptance.

Regards,

Adam

Bug#859056: diffoscope: Please add support for .docx and .odt files

[Chris Lamb]

Package: diffoscope
Version: 81
Severity: wishlist

Hi,

Please add support for .docx and .odt files via docx2txt and odt2txt
respectfully.


Regards,

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

Bug#857920: jessie-pu: package irqbalance/1.0.6-3+deb8u1

[Adam D. Barratt]

Control: tags -1 + pending

On Sun, 2017-03-19 at 20:27 +0100, Salvatore Bonaccorso wrote:
> Hi Adam,
> 
> On Sun, Mar 19, 2017 at 05:09:20PM +, Adam D. Barratt wrote:
> > Control: tags -1 + confirmed
> > 
> > On Thu, 2017-03-16 at 12:17 +0100, Salvatore Bonaccorso wrote:
> > > irqbalance on jessie ist still affected by #784391, causing irqbalance
> > > to spam logs under certain conditions where affinity_hint subset is
> > > empty.
> > 
> > Please go ahead.
> 
> Thanks a lot, uploaded.

Flagged for acceptance, thanks.

Regards,

Adam

Bug#856665: jessie-pu: package commons-daemon/1.0.15-6

[Adam D. Barratt]

Control: tags -1 + pending

On Thu, 2017-03-09 at 19:58 +, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Fri, 2017-03-03 at 17:07 -0300, Breno Leitao wrote:
> > Hi Adam,
> > 
> > On Fri, Mar 03, 2017 at 05:41:51PM +, Adam D. Barratt wrote:
> > > On 2017-03-03 17:29, Breno Leitao wrote:
> > > >Package jsvc (commons-daemon) contains a patch enabling ppc64el on
> > > >version 1.0.15-6 (currently on Jessie), but it does not work. A new
> > > >patch required to add functional support for commons-daemon on ppc64el.
> > > >
> > > >This patch is already commited on upstream as in Stretch.
> > > >
> > > >You can find more information about this bug at #856560.
> > > >
> > > >Let me know if I can update a fixed package in stable.
> > > 
> > > We'd need to see a source debdiff for the proposed (and tested) package
> > > first, please.
> > 
> > Sure. This is the debdiff I have. I tested it and it solves the problem
> > on ppc64el, and it does not seem cause any regression on amd64.
> 
> +  * This package is broken on Jessie, showing "Cannot find any VM in Java
> +Home". Fixing it. (Closes: #856560)
> 
> That sounds a little overly verbose, personally - it's reasonably
> obvious that the package is broken in some way and you're fixing it,
> otherwise the update wouldn't exist in the first place.
> 
> In any case, please update the changelog to mention the fact that the
> fix is specifically related to ppc64el, and feel free to upload.

Uploaded and flagged for acceptance.

Regards,

Adam

Bug#859051: pixfrogger: Pixfrogger is not installable on amd64 system

[Andrej Mernik]

Package: pixfrogger
Version: 1.0-4
Severity: important

Dear Maintainer,

it appears that the pixfrogger package is not installable on Stretch amd64,
because its depends are not installable.

I am aware that the package itself might be architecture independent, but it
should not be. The current state creates confusion for the end user, making
Debian amd64 and its derivatives look broken, which also contributes to the
overall public perception of GNU/Linux as unsuited for daily use.

The package should be marked as "i386 only" as soon as possible.

Best Regards,
Andrej Mernik



-- 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=sl_SI.UTF-8, LC_CTYPE=sl_SI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#859050: lighttpd: Please migrate to openssl1.1 in Buster

[Sebastian Andrzej Siewior]

Package: lighttpd
Version: 1.4.44-1
Severity: important
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1-trans

Please migrate to libssl-dev in the Buster cycle. I have no idea why
"libssl-dev|libssl1.0-dev" is currently used.

Sebastian

Bug#859048: Attachment check hook prevents IMP smartmobile view to send message with 'attachment' word when there's no attachment

[Leonardo Bruno]

Package: php-horde-imp
Version: 6.2.2-3
Severity: important

Scenario: Compose a message using the IMP smartmobile view in a Horde setup
with the 'attach_body_check' enabled.

Symptoms: When using the IMP smartmobile view, it will not be possible to
send a message without attachments if in the message body text there is any
of the keywords defined in the 'attach_body_check' IMP hook function.

The first attempt to send will show a warning message informing that no
attachments are indeed present, as it is expected. However, the following
attempts present the same behavior: a message warns about the absence of
attachments and the message is not sent. It will only be sent if: 1) you
remove the keyword(s) from the message, or 2) add some attachment, or 3)
disable the hook.

Remarks:
1. Only the smartmobile view is affected.
2. The tests where performed with the default Horde and IMP prefs. The only
hooke enabled is 'attach_body_check'.
3. This issue affects the upcoming php-horde-imp stable package (version
6.2.17-1) in Debian stretch.
4. I chose to mark this report as 'important' as the smartmobile view
actually is a must-have feature, and there is no way to deactivate the
'attach_body_check' only for this view.

Regards,
Leonardo Bruno

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

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

Versions of packages php-horde-imp depends on:
ii  php-horde  5.2.1+debian0-2+deb8u3
ii  php-horde-auth 2.1.5-5
ii  php-horde-browser  2.0.7-2
ii  php-horde-cache2.5.0-2
ii  php-horde-compress 2.0.8-5
ii  php-horde-core 2.15.0+debian0-1+deb8u1
ii  php-horde-crypt2.5.0-5
ii  php-horde-css-parser   1.0.4-5
ii  php-horde-date 2.0.12-5
ii  php-horde-editor   2.0.4+debian0-3
ii  php-horde-exception2.0.4-4
ii  php-horde-icalendar2.0.9-4
ii  php-horde-image2.1.0-4
ii  php-horde-imap-client  2.25.2-1
ii  php-horde-itip 2.0.6-4
ii  php-horde-listheaders  1.1.5-4
ii  php-horde-logintasks   2.0.3-4
ii  php-horde-mail 2.4.0-4
ii  php-horde-mail-autoconfig  1.0.1-3
ii  php-horde-mime 2.4.5-3
ii  php-horde-mime-viewer  2.0.7-2
ii  php-horde-nls  2.0.4-2
ii  php-horde-notification 2.0.1-6
ii  php-horde-pack 1.0.4-2
ii  php-horde-perms2.1.2-4
ii  php-horde-spellchecker 2.1.1-4
ii  php-horde-stream   1.6.1-4
ii  php-horde-stream-filter2.0.2-4
ii  php-horde-stream-wrapper   2.1.0-4
ii  php-horde-support  2.1.1-4
ii  php-horde-text-filter  2.2.1-5
ii  php-horde-text-flowed  2.0.1-6
ii  php-horde-tree 2.0.2-3
ii  php-horde-url  2.2.3-4
ii  php-horde-util 2.5.1-5
ii  php-horde-vfs  2.2.0-4
ii  php-horde-view 2.0.4-4
ii  php5-cli   5.6.30+dfsg-0+deb8u1
ii  php5-common5.6.30+dfsg-0+deb8u1
ii  php5-json  1.3.6-1

Versions of packages php-horde-imp recommends:
ii  php-horde-history   2.3.1-4
ii  php-horde-http  2.1.1-4
ii  php-horde-service-gravatar  1.0.0-4

php-horde-imp suggests no packages.

-- no debconf information

Bug#859049: pixbros: Pixbros is not installable on amd64 system

[Andrej Mernik]

Package: pixbros
Version: 0.6.3-2
Severity: important

Dear Maintainer,

it appears that the pixbros package is not installable on Stretch amd64,
because its depends are not installable.

I am aware that the package itself might be architecture independent, but it
should not be. The current state creates confusion for the end user, making
Debian amd64 and its derivatives look broken, which also contributes to the
overall public perception of GNU/Linux as unsuited for daily use.

The package should be marked as "i386 only" as soon as possible.

Best Regards,
Andrej Mernik



-- 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=sl_SI.UTF-8, LC_CTYPE=sl_SI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#858851: debarchiver: [INTL:de] updated German man page translation

[Ola Lundqvist]

Hi Helge

Apparently...
Uploading to ftp-master (via ftp to ftp.upload.debian.org):
  Uploading debarchiver_0.11.1.dsc: done.
  Uploading debarchiver_0.11.1.tar.gz: done.
  Uploading debarchiver_0.11.1_all.deb: done.
  Uploading debarchiver_0.11.1_amd64.changes: done.
Successfully uploaded packages.

So it was uploaded. The question is why it has not been accepted.

I do not follow debian-devel, maybe it is a scheduled stop.

You can find the source code here:
https://svn.inguza.org/fsp/trunk/debarchiver/
Do a svn checkout from there.

Or here (web interface):
http://svn.inguza.org/fsp/trunk/debarchiver/

Cheers

// Ola

On 29 March 2017 at 18:59, Helge Kreutzmann  wrote:

> Hello Ola,
> On Tue, Mar 28, 2017 at 09:17:22PM +0200, Ola Lundqvist wrote:
> > It should be in unstable/sid in an hour or so.
>
> 1.11.1  has not yet appeared in Unstable. Has there been a problem
> while uploading?
>
> Greetings
>
>   Helge
> --
>   Dr. Helge Kreutzmann deb...@helgefjell.de
>Dipl.-Phys.   http://www.helgefjell.de/
> debian.php
> 64bit GNU powered gpg signed mail preferred
>Help keep free software "libre": http://www.ffii.de/
>



-- 
 --- Inguza Technology AB --- MSc in Information Technology 
/  o...@inguza.comFolkebogatan 26\
|  o...@debian.org   654 68 KARLSTAD|
|  http://inguza.com/Mobile: +46 (0)70-332 1551 |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9  /
 ---

Bug#600882: ping?

[Martín Ferrari]

The reporter's email is bouncing, so i am closing this bug.

On 29/03/17 19:56, Martín Ferrari wrote:
> Hi, resending in case you did not see the last update to this bug:
> 
> "
> 
> This looks like it could be the same problem as #422118
> (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=422118), but I can't
> verify as there is no sample file to reproduce the issue. Please,
> provide one so I can do something about this bug.
> 
> "
> 
> 


-- 
Martín Ferrari (Tincho)

Bug#859033: pg_dump: creates dumps that cannot be restored

[Thorsten Glaser]

Dixi quod…

> ‣‣‣ What have I expected?
> 
> That pg_dump recognises the dependency (there i̲s̲ a FOREIGN KEY reference
> in there) and reorders the tables dumped.

I’d actually be happy if there were a way to restore those dumps,
for example by temporarily disabling constraint checks during the
restore. This MUST NOT cost consistence though — constraint checks
would, in this restore mode, need to be re-enabled AND all data
checked against them BEFORE the --single-transaction surrounding
all this finishes, and abort it if any data fails the constraints.

Well, actually even happier as it would allow me to restore such
dumps created by those buggy pg_dump versions, which are abundant.

Thanks in advance,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

Bug#810883: catdoc: Invalid memory access and segfaulting

[Martín Ferrari]

On 15/01/16 07:10, Steve Kemp wrote:

>   Great.  I have about twenty more files that crash the version of
>  catdoc available to sid.  I will wait to see your fix, and once posted
>  I'll test the current samples against them, I expect that some of them are
>  non-unique.

The new upstream version seems to fix this:

$ catdoc xx.doc
Broken OLE file. Try using -b switch

$ catdoc -b xx.doc | head
Company Logo Here   Your Company Name Here

INVOICE

Your Street Address Here

Invoice Number:

Your City/State/Zip Here



So I will close this bug on upload, as neither samples make it segfault
any more. Please, open more bugs if your other test files make it segfault.


-- 
Martín Ferrari (Tincho)

Bug#600882: ping?

[Martín Ferrari]

Hi, resending in case you did not see the last update to this bug:

"

This looks like it could be the same problem as #422118
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=422118), but I can't
verify as there is no sample file to reproduce the issue. Please,
provide one so I can do something about this bug.

"


-- 
Martín Ferrari (Tincho)

Bug#859047: pysolfc: Any stack of Hanafuda cards is always movable

[Frédéric Brière]

Package: pysolfc
Version: 2.0-4
Severity: normal
Tags: patch

Any stack of Hanafuda cards is always deemed movable, even if it is out
of sequence.  The effect can easily be seen a game such as Firecracker,
where:

 - Any stack can be dragged as a whole (but not released)
 - "Highlight piles" will highlight everything
 - Asking for a hint will ignore most valid moves

This is due to Hanafuda_SequenceStack lacking a canMoveCards() method.


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

Kernel: Linux 4.9.0-2-amd64 (SMP w/3 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: sysvinit (via /sbin/init)
>From 51d19eb99dc138549a0cb3b32c1e8983fe43d26a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Fr=C3=A9d=C3=A9ric=20Bri=C3=A8re?= 
Date: Wed, 29 Mar 2017 13:02:38 -0400
Subject: [PATCH] Define canMoveCards() for Hanafuda sequence stacks

---
 pysollib/games/ultra/hanafuda_common.py | 6 ++
 1 file changed, 6 insertions(+)

diff --git a/pysollib/games/ultra/hanafuda_common.py 
b/pysollib/games/ultra/hanafuda_common.py
index b4b9541..27d28b6 100644
--- a/pysollib/games/ultra/hanafuda_common.py
+++ b/pysollib/games/ultra/hanafuda_common.py
@@ -310,6 +310,9 @@ class Hanafuda_SequenceStack(Flower_OpenStack):
 return cards[0].rank == 0 or self.cap.base_rank == ANY_RANK
 return self.isHanafudaSequence([stackcards[-1], cards[0]])
 
+def canMoveCards(self, cards):
+return self.basicCanMoveCards(cards) and self.isHanafudaSequence(cards)
+
 
 class Oonsoo_SequenceStack(Flower_OpenStack):
 
@@ -322,6 +325,9 @@ class Oonsoo_SequenceStack(Flower_OpenStack):
 return cards[0].rank == 0 or self.cap.base_rank == ANY_RANK
 return self.isHanafudaSequence([stackcards[-1], cards[0]], 0)
 
+def canMoveCards(self, cards):
+return self.basicCanMoveCards(cards) and 
self.isHanafudaSequence(cards, 0)
+
 
 class FlowerClock_RowStack(Flower_OpenStack):
 
-- 
2.11.0

Bug#859008: dvb-tools: dvbv5-scan segfaults with DVB-T2 HD service that just started in Germany

[Gregor Jasny]

Hello Mauro & list,

could you please have a look at the dvbv5-scan crash report below?
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859008

Is there anything else you need to debug this?

Thanks,
Gregor

On 3/29/17 4:42 PM, Tino Mettler wrote:
> 
> $ gdb --args ./utils/dvb/dvbv5-scan ~/tmp/dvb-t2/init2 
> 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 ./utils/dvb/dvbv5-scan...done.
> (gdb) run
> Starting program: /home/scorpion/build/9643/v4l-utils/utils/dvb/dvbv5-scan 
> /home/scorpion/tmp/dvb-t2/init2
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> Scanning frequency #1 55400
> Lock   (0x1f) C/N= 23.75dB
> Service Das Erste HD, provider BR: reserved
> Service arte HD, provider BR: reserved
> Service PHOENIX HD, provider BR: reserved
> Service tagesschau24 HD, provider BR: reserved
> Service ONE HD, provider BR: reserved
> New transponder/channel found: #11: -1776415946
> New transponder/channel found: #12: 504706590
> New transponder/channel found: #13: 523640360
> New transponder/channel found: #14: 907948854
> New transponder/channel found: #15: -397832490
> New transponder/channel found: #16: 0
> New transponder/channel found: #17: 0
> New transponder/channel found: #18: 0
> New transponder/channel found: #19: 0
> New transponder/channel found: #20: 0
> New transponder/channel found: #21: 0
> New transponder/channel found: #22: 0
> New transponder/channel found: #23: 0
> New transponder/channel found: #24: 0
> New transponder/channel found: #25: 0
> New transponder/channel found: #26: 0
> New transponder/channel found: #27: 0
> New transponder/channel found: #28: 0
> New transponder/channel found: #29: 0
> New transponder/channel found: #30: 0
> New transponder/channel found: #31: 0
> New transponder/channel found: #32: 0
> New transponder/channel found: #33: 0
> New transponder/channel found: #34: 0
> New transponder/channel found: #35: 0
> New transponder/channel found: #36: 0
> New transponder/channel found: #37: 0
> New transponder/channel found: #38: 0
> New transponder/channel found: #39: 0
> New transponder/channel found: #40: 0
> New transponder/channel found: #41: 0
> New transponder/channel found: #42: 0
> New transponder/channel found: #43: 0
> New transponder/channel found: #44: 0
> New transponder/channel found: #45: 0
> New transponder/channel found: #46: 0
> New transponder/channel found: #47: 0
> New transponder/channel found: #48: 0
> New transponder/channel found: #49: 0
> New transponder/channel found: #50: 0
> New transponder/channel found: #51: 0
> New transponder/channel found: #52: 0
> New transponder/channel found: #53: 0
> New transponder/channel found: #54: 0
> New transponder/channel found: #55: 0
> New transponder/channel found: #56: 0
> New transponder/channel found: #57: 0
> New transponder/channel found: #58: 0
> New transponder/channel found: #59: 0
> New transponder/channel found: #60: 0
> New transponder/channel found: #61: 0
> New transponder/channel found: #62: 0
> New transponder/channel found: #63: 0
> New transponder/channel found: #64: 0
> New transponder/channel found: #65: 0
> New transponder/channel found: #66: 0
> New transponder/channel found: #67: 0
> New transponder/channel found: #68: 0
> New transponder/channel found: #69: 0
> New transponder/channel found: #70: 0
> New transponder/channel found: #71: 0
> New transponder/channel found: #72: 0
> New transponder/channel found: #73: 0
> New transponder/channel found: #74: 0
> New transponder/channel found: #75: 0
> Scanning frequency #2 65000
>(0x00) Signal= -69.00dBm
> Scanning frequency #3 73800
>(0x00) Signal= -76.00dBm
> Scanning frequency #4 57800
> Lock   (0x1f) Signal= -76.00dBm C/N= 27.25dB
> *** Error in `/home/scorpion/build/9643/v4l-utils/utils/dvb/dvbv5-scan': 
> malloc(): memory corruption: 0x557a6b70 ***
> === Backtrace: =
> /lib/x86_64-linux-gnu/libc.so.6(+0x70bcb)[0x7759fbcb]
> /lib/x86_64-linux-gnu/libc.so.6(+0x76f96)[0x775a5f96]
> /lib/x86_64-linux-gnu/libc.so.6(+0x78f69)[0x775a7f69]
> /lib/x86_64-linux-gnu/libc.so.6(__libc_calloc+0x27b)[0x775aa99b]
> 

Bug#823807: ITA: courier

[Ondřej Surý]

Hi Markus,

I got the email fixed. It was just the first relay rejecting emails.

Feel free and go ahead. I would be most happy if somebody take over and
I have already orphaned the package.

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver
Vše pro chleba (https://vseprochleba.cz) – Mouky ze mlýna a potřeby pro
pečení chleba všeho druhu

On Thu, Mar 23, 2017, at 22:48, Markus Wanner wrote:
> Hi,
> 
> as a happy long-time [0] user of courier-mta on Debian [0], I'd like to
> try my best to make that fine MTA stay in Debian. I'm offering to adopt
> courier, courier-authlib and courier-unicode.
> 
> I'd welcome all the help I can get and would love to team up with
> others, as my spare time is pretty limited. Therefore this call to other
> fellow courier users: please speak up!
> 
> Kind Regards
> 
> Markus Wanner
> 
> 
> [0]: Just checked my archive: Jun 2003 is the first mail I received with
> Courier. Must have been on Debian woody.
> 
> Email had 1 attachment:
> + signature.asc
>   2k (application/pgp-signature)

Bug#859046: bitlbee-facebook: Please, update to new upstream release, as the plugin is currently not working

[Martín Ferrari]

Source: bitlbee-facebook
Version: 1.0.0+git20170223.3e8dd70-1
Severity: important

(Important severity as the package is currently unusable)

Since yesterday, the plugin has become unusable due to a change in the Facebook
API. Today, the upstream author has released a new version including the fix.
I have built the package locally and works correctly.


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

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

Bug#772489: Start of apt-cacher-ng

[Georg Gast]

I could start apt-cacher-ng as i deleted /var/log/apt-cacher-ng and
recreated it. Set user and group to apt-cacher-ng

-- 
pgp key: 0x702C5BFC
Fingerprint: 267F DC06 7F96 3375 969A  9EE6 8E37 7CF4 702C 5BFC

Bug#859032: hfst-ospell: Incomplete debian/copyright?

[Tino Didriksen]

On 29 March 2017 at 19:43, Chris Lamb  wrote:

> I just ACCEPTed hfst-ospell from NEW but noticed it was missing
> attribution in debian/copyright for at least:
>
>   office.cc:4:  Copyright 2015 Tino Didriksen 
>
> (This is not exhaustive so please check over the entire package
> carefully and address these on your next upload.)



As the author of both office.cc and debian/*, I'd say it's fine.

I mostly put myself in office.cc so people would know who to direct bug
reports to, but the file is copyright-assigned to the HFST project, as the
first line says.

I did however miss attribution for a file in m4/ - will fix for next time.

-- Tino Didriksen

Bug#859034: diffoscope: Please add support for PGP files via pgpdump.

[Chris Lamb]

tags 859034 + pending
thanks

Fixed in Git:

  
https://anonscm.debian.org/git/reproducible/diffoscope.git/commit/?id=05b3d02fd7874a2e1e4c7ba38fa6de899dc79ee6


Regards,

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

Bug#859034: diffoscope: Please add support for PGP files via pgpdump.

[Chris Lamb]

Package: diffoscope
Version: 81
Severity: wishlist

Hi,

Please add support for PGP files via pgpdump.


Regards,

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

Bug#859033: pg_dump: creates dumps that cannot be restored

[Thorsten Glaser]

Package: postgresql-client-common
Version: 179
Severity: normal

I’ve created a testcase (MWE) here.


Step 1: initialise a new database user and DB, for the test:

user$ sudo su - postgres
postgres$ createuser -D -P -R -S testuser
postgres$ createdb -E UTF-8 -O testuser -T template0 -l de_DE.UTF-8 testdb
^D


Step 2: import the attached SQL, note the last two statements
will fail but the others will succeed:

psql -U testuser -h 127.0.0.1 -f testcase.sql testdb


Step 3: create a database dump, removing a few lines that are
known to always produce errors on restoring:

pg_dump -c -Fp --no-owner --if-exists -U testuser -h 127.0.0.1 testdb | sed \
-e '/^DROP EXTENSION IF EXISTS plpgsql/d' \
-e '/^DROP SCHEMA IF EXISTS public/d' \
-e '/^CREATE SCHEMA public/d' \
-e '/^COMMENT ON SCHEMA public/d' \
-e '/^COMMENT ON EXTENSION plpgsql/d' \
>dump.sql


Step 4: try to restore it, watch it explode:

$ psql -U testuser -h 127.0.0.1 -f dump.sql --single-transaction 
--set=ON_ERROR_STOP=1 testdb
Password for user testuser:
SET
SET
SET
SET
SET
SET
SET
SET
SET
ALTER TABLE
ALTER TABLE
ALTER TABLE
ALTER TABLE
ALTER TABLE
DROP SEQUENCE
DROP TABLE
DROP TABLE
DROP FUNCTION
DROP FUNCTION
CREATE EXTENSION
SET
CREATE FUNCTION
CREATE FUNCTION
SET
SET
CREATE TABLE
CREATE TABLE
CREATE SEQUENCE
ALTER SEQUENCE
ALTER TABLE
psql:dump.sql:146: ERROR:  new row for relation "derived_things" violates check 
constraint "derived_things_check_child"
DETAIL:  Failing row contains (3, 1, foobar on foo).
CONTEXT:  COPY derived_things, line 1: "3   1   foobar on foo"


‣‣‣ What happened?

The database dump contains the tables derived_things and things in
this order (ASCIIbetically), however, the table derived_things depends
on the table things.

‣‣‣ What have I expected?

That pg_dump recognises the dependency (there i̲s̲ a FOREIGN KEY reference
in there) and reorders the tables dumped.

‣‣‣ How can I prove this works?

$ ed dump.sql
/^COPY derived_things/ka
/^\\\./kb
/^COPY things/  
/^\\\./+1kc
'a,'bm'c
wq

This reorders the dump to look as follows:


[…]
-- Data for Name: things; Type: TABLE DATA; Schema: public; Owner: -
--

COPY things (pk, some_data, standalone) FROM stdin;
1   foo t
2   bar t
3   foobar  f
4   foofoobar   f
5   baz t
\.

COPY derived_things (parent, child, arbitrary_data) FROM stdin;
3   1   foobar on foo
3   2   foobar on bar
4   1   foofoobar on foo
\.

--
-- Name: things_pk_seq; Type: SEQUENCE SET; Schema: public; Owner: -
[…]


Restoring this works just fine:

$ psql -U testuser -h 127.0.0.1 -f dump.sql --single-transaction 
--set=ON_ERROR_STOP=1 testdb
Password for user testuser:
SET
SET
SET
SET
SET
SET
SET
SET
SET
ALTER TABLE
ALTER TABLE
ALTER TABLE
ALTER TABLE
ALTER TABLE
DROP SEQUENCE
DROP TABLE
DROP TABLE
DROP FUNCTION
DROP FUNCTION
CREATE EXTENSION
SET
CREATE FUNCTION
CREATE FUNCTION
SET
SET
CREATE TABLE
CREATE TABLE
CREATE SEQUENCE
ALTER SEQUENCE
ALTER TABLE
COPY 5
COPY 3
 setval

  1
(1 row)

ALTER TABLE
ALTER TABLE
ALTER TABLE
ALTER TABLE


-- 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 postgresql-client-common depends on:
ii  netbase  5.4

Versions of packages postgresql-client-common recommends:
ii  libreadline7  7.0-2
ii  lsb-release   9.20161125

postgresql-client-common suggests no packages.

-- no debconf information
CREATE TABLE things (
pk BIGSERIAL PRIMARY KEY,
some_data TEXT NOT NULL,
standalone BOOLEAN NOT NULL
);

CREATE FUNCTION check_derived_is_child(BIGINT) RETURNS BOOLEAN AS $$
SELECT EXISTS (
SELECT 1 FROM things
WHERE pk=$1 AND standalone=TRUE
);
$$ LANGUAGE sql;

CREATE FUNCTION check_derived_is_parent(BIGINT) RETURNS BOOLEAN AS $$
SELECT EXISTS (
SELECT 1 FROM things
WHERE pk=$1 AND standalone=FALSE
);
$$ LANGUAGE sql;

CREATE TABLE derived_things (
parent BIGINT NOT NULL REFERENCES things(pk),
child BIGINT NOT NULL REFERENCES things(pk),
arbitrary_data TEXT NOT NULL,
CONSTRAINT derived_things_check_child CHECK 
(check_derived_is_child(child)),
CONSTRAINT derived_things_check_parent CHECK 
(check_derived_is_parent(parent)),
PRIMARY KEY (parent, child)
);

-- these will succeed
INSERT INTO things VALUES (1, 'foo', TRUE);
INSERT INTO things VALUES (2, 'bar', TRUE);
INSERT INTO things VALUES (3, 'foobar', FALSE);
INSERT INTO things VALUES (4, 'foofoobar', FALSE);
INSERT INTO things VALUES (5, 'baz', TRUE);
INSERT INTO derived_things VALUES (3, 1, 'foobar 

Bug#859029: Acknowledgement (po4a: [INTL:de] updated German man page translation)

[Helge Kreutzmann]

Hello,
btw. is the SVN repository still the main one?

Greetings

  Helge
-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: Digital signature

Bug#857302: reprepro: Please run test suite on package build time

[Benjamin Drung]

Hi,

On Thu, 09 Mar 2017 19:56:47 +0100 Benjamin Drung 
 wrote:
> While developing the patch for #570623, I added shunit2-based tests.
> shunit2 is available as Debian package and can be easily integrated
> in the package build. Patches for some smoke tests are attached (in
> case you consider using shunit2).

attached the current version of the basic shunit2 tests.

-- 
Benjamin Drung
System Developer
Debian & Ubuntu Developer

ProfitBricks GmbH
Greifswalder Str. 207
D - 10405 Berlin

Email: benjamin.dr...@profitbricks.com
URL:  http://www.profitbricks.com

Sitz der Gesellschaft: Berlin.
Registergericht: Amtsgericht Charlottenburg, HRB 125506B.
Geschäftsführer: Andreas Gauger, Achim Weiss.From 6123d145779b461865e5ef9b470ee3e8080c1c05 Mon Sep 17 00:00:00 2001
From: Benjamin Drung 
Date: Mon, 6 Feb 2017 17:47:38 +0100
Subject: [PATCH 01/58] [testsuite] Use dpkg-source format 1.0

To silence dpkg-source, use source format 1.0
---
 tests/genpackage.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/genpackage.sh b/tests/genpackage.sh
index ac8ffec..ee21890 100755
--- a/tests/genpackage.sh
+++ b/tests/genpackage.sh
@@ -39,7 +39,7 @@ $PACKAGE ($EPOCH$VERSION$REVISION) $DISTRI; urgency=critical
  -- me   Mon, 01 Jan 1980 01:02:02 +
 END
 
-dpkg-source -b "$DIR"
+dpkg-source --format=1.0 -b "$DIR"
 mkdir -p "$DIR"/debian/tmp/DEBIAN
 touch "$DIR"/debian/tmp/x
 mkdir "$DIR"/debian/tmp/a
-- 
2.9.3

From aa30c40b40a1c05d87c6802f2d3c7055d2e2f4f6 Mon Sep 17 00:00:00 2001
From: Benjamin Drung 
Date: Mon, 6 Feb 2017 17:49:07 +0100
Subject: [PATCH 02/58] [testsuite] Use the host architecture by default

To be able to build packages for the tests, use the host architecture
(to avoid requiring a cross-compiler).
---
 tests/genpackage.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/genpackage.sh b/tests/genpackage.sh
index ee21890..ff18103 100755
--- a/tests/genpackage.sh
+++ b/tests/genpackage.sh
@@ -19,7 +19,7 @@ Maintainer: me 
 Standards-Version: 0.0
 
 Package: $PACKAGE
-Architecture: abacus
+Architecture: ${ARCH:-$(dpkg-architecture -qDEB_HOST_ARCH)}
 Description: bla
  blub
 
-- 
2.9.3

From b7c896010057f3107e947efcf038c8caa98fdb9b Mon Sep 17 00:00:00 2001
From: Benjamin Drung 
Date: Tue, 28 Mar 2017 15:10:10 +0200
Subject: [PATCH 03/58] [testsuite] Use existing priority

Using the non-existing priority 'superfluous' causes warning messages.
---
 tests/genpackage.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/genpackage.sh b/tests/genpackage.sh
index ff18103..b237e86 100755
--- a/tests/genpackage.sh
+++ b/tests/genpackage.sh
@@ -14,7 +14,7 @@ mkdir "$DIR"/debian
 cat >"$DIR"/debian/control <
 Standards-Version: 0.0
 
-- 
2.9.3

From fa0ecef0449c80489b86454e2d9a304ba9e76789 Mon Sep 17 00:00:00 2001
From: Benjamin Drung 
Date: Tue, 28 Mar 2017 15:15:22 +0200
Subject: [PATCH 04/58] [testsuite] genpackage.sh: Silence output

---
 tests/genpackage.sh | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/tests/genpackage.sh b/tests/genpackage.sh
index b237e86..df294f4 100755
--- a/tests/genpackage.sh
+++ b/tests/genpackage.sh
@@ -39,7 +39,7 @@ $PACKAGE ($EPOCH$VERSION$REVISION) $DISTRI; urgency=critical
  -- me   Mon, 01 Jan 1980 01:02:02 +
 END
 
-dpkg-source --format=1.0 -b "$DIR"
+dpkg-source --format=1.0 -b "$DIR" > /dev/null
 mkdir -p "$DIR"/debian/tmp/DEBIAN
 touch "$DIR"/debian/tmp/x
 mkdir "$DIR"/debian/tmp/a
@@ -56,9 +56,9 @@ for pkg in `grep '^Package: ' debian/control | sed -e 's/^Package: //'` ; do
 	else
 		dpkg-gencontrol -p$pkg
 	fi
-	dpkg --build debian/tmp ..
+	dpkg --build debian/tmp .. > /dev/null
 done
-dpkg-genchanges "$@" > "$OUTPUT".pre
+dpkg-genchanges -q "$@" > "$OUTPUT".pre
 # simulate dpkg-genchanges behaviour currently in sid so the testsuite runs for backports, too
 awk 'BEGIN{inheader=0} /^Files:/ || (inheader && /^ /)  {inheader = 1; next} {inheader = 0 ; print}' "$OUTPUT".pre | sed -e 's/ \+$//' >../"$OUTPUT"
 echo "Files:" >> ../"$OUTPUT"
-- 
2.9.3

From b63bdbb47941aa3da97c8c6c3d29ecba31cd79c1 Mon Sep 17 00:00:00 2001
From: Benjamin Drung 
Date: Mon, 6 Feb 2017 17:44:16 +0100
Subject: [PATCH 05/58] [testsuite] Add basic shunit2 based tests

Closes: #857302
Signed-off-by: Benjamin Drung 
---
 tests/Makefile.am | 10 -
 tests/basic.sh| 78 +++
 tests/shunit2-helper-functions.sh | 61 ++
 3 files changed, 148 insertions(+), 1 deletion(-)
 create mode 100755 tests/basic.sh
 create mode 100644 tests/shunit2-helper-functions.sh

diff --git a/tests/Makefile.am b/tests/Makefile.am
index 901b302..78cb38a 100644
--- 

Bug#822861: Unable to reproduce your killall bug

[Jörg Ludwig]

Hi Craig,

thank you for your efforts!

I added some debug code to killall.c and found out, that process_age_sec 
is either 0.00 or 0.01. If process_age_sec happens to be 
0.00, the process gets killed although it is younger than 1h. The 
locale and architecture seem to affect the timing, but do not cause the 
problem itself.


The following patch fixes the problem:

--- killall.c.orig  2017-03-29 19:21:01.693936749 +0200
+++ killall.c   2017-03-29 19:29:14.185785335 +0200
@@ -464,7 +464,7 @@

 	  if ( younger_than && process_age_sec && (process_age_sec > 
younger_than ) )

 continue;
-	  if ( older_than   && process_age_sec && (process_age_sec < 
older_than ) )

+ if ( older_than   && (process_age_sec < older_than ) )
 continue;

  if (!sts[j].st_dev)

I think the check of process_age_sec should be removed in both cases, as 
killall skips the current pid, if it fails to read the progress age anyway.


--
Mit freundlichen Grüßen,

Jörg Ludwig

IServ GmbH
Bültenweg 73
38106 Braunschweig

Telefon: 0531-2243666-0
Fax: 0531-2243666-9
Mobil:   0179-9101055
E-Mail:  joerg.lud...@iserv.eu
Internet:www.iserv.eu
USt.-IdNr.:  DE265149425

Am 25.03.2017 um 08:38 schrieb Craig Small:

tags 822861 unreproducible
thankyou

Hi Jörg,
  I am unable to make this problem occur. To me I'm not even sure how
the locale could cause this problem.

I tried on a debian i386 chroot and it worked fine, see below.
No Processes found, I believe its telling me.

(sid_i386-dchroot)csmall@barriere:~$ sleep 5 & LC_ALL=de_DE.UTF-8
killall --older-than 1h sleep
[1] 11121
sleep: Kein Prozess gefunden
(sid_i386-dchroot)csmall@barriere:~$ dpkg -l psmisc
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  psmisc 22.21-2.1+b2 i386 utilities that use the proc
file

Bug#859032: hfst-ospell: Incomplete debian/copyright?

[Chris Lamb]

Source: hfst-ospell
Version: 0.4.3~r338-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Kartik Mistry 

Hi,

I just ACCEPTed hfst-ospell from NEW but noticed it was missing 
attribution in debian/copyright for at least:

  office.cc:4:  Copyright 2015 Tino Didriksen 

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


Regards,

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

Bug#859031: glibmm2.4: Lack of dbg package

[Tony Houghton]

Source: glibmm2.4
Version: 2.50.0-1
Severity: important

There is no libglibmm-2.4-dbg package corresponding to this version.
This makes it much harder to debug applications using glibmm.

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

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

Bug#859030: RFP: rtags -- A c/c++ client/server indexer for c/c++/objc[++] with integration for Emacs based on clang

[Guido Günther]

Package: wnpp
Severity: wishlist

* Package name: rtags
  Version : 2.9
* URL : https://github.com/Andersbakken/rtags/
* License : GPLv3
  Programming Lang: C++, EmacsLisp
  Description : A c/c++ client/server indexer for c/c++/objc[++] with 
integration for Emacs based on clang


RTags is a client/server application that indexes C/C++ code and keeps a
persistent file-based database of references, declarations, definitions,
symbolnames etc. There’s also limited support for ObjC/ObjC++. It allows
you to find symbols by name (including nested class and namespace
scope). Most importantly we give you proper follow-symbol and
find-references support. We also have neat little things like
rename-symbol, integration with clang’s “fixits”
(http://clang.llvm.org/diagnostics.html). We also integrate with flymake
using clang’s vastly superior errors and warnings. Since RTags
constantly will reindex “dirty” files you get live updates of compiler
errors and warnings. Since we already know how to compile your sources
we have a way to quickly bring up the preprocessed output of the current
source file in a buffer.

Bug#831467: This "fix" is totally bogus and should be reverted ASAP

[Yuriy M. Kaminskiy]

As noted in (forwarded) github issue, this "fix" is totally bogus and 
(likely) breaks things.


ExecStop command is expected to kill daemon (in a friendly way), while 
(default handler for) kill(SIGSTOP) pauses/freezes/suspends process 
execution (and transmission-daemon does not override default SIGSTOP 
handler).


If ExecStop is not specified, systemd sends SIGTERM (which is handled by 
transmission-daemon, and should do right thing), and then (if process is 
still alive) SIGKILL.


If ExecStop is specified, but does not actually finish process (and kill 
-STOP does NOT finish transmission-daemon process), systemd waits for 
TimeoutStopSec, then sends SIGTERM (but as kill -STOP just suspended 
process, it will NOT be handled by transmission-daemon), and then (as 
process is still alive) sends SIGKILL.


So, as a result of this patch, transmission-daemon is killed in VERY 
unfriendly way (and very *slowly* - after waiting for 2*TimeoutStopSec).


As pointed in github issue, original poster log indicates that 
transmission-daemon dies by SIGSEGV, which is NOT signal that was 
(possibly) sent by systemd. That is, it is some transmission-daemon bug 
that was just triggered during "clean" process termination, and NOT 
systemd interaction issue.
Obviously, when daemon is hard-killed, this SIGSEGV is not (immediately) 
triggered, but it does not really fix issue, only hides it.


P.S. from first look at sources, transmission-daemon handles termination 
signals synchronously, so this is (probably) not 
async-signal-unsafe-function-in-signal-handler kind of bug.

Bug#858806: gbp-buildpackage: reset all time-stamps to last changelog entry

[Guido Günther]

Hi Dominique,
On Wed, Mar 29, 2017 at 04:27:40PM +0200, Dominique Dumont wrote:
> On Monday, 27 March 2017 19:07:06 CEST Guido Günther wrote:
> > So either the builder
> > is messing things up here or something else (package import or copy to a
> > temporary build place) is messing things up in the source resulting in
> > bad timestamps in the binary package.
> 
> Yes. You're right, Turns out that pristine-tar is setting the timestamp of 
> all 
> files [1] when creating a tarball.
> 
> The code that tweak timestamp has been present since 2007. I'm beginning to 
> wonder if that's should be considered as a bug or a feature.
> 
> I'll check with Perl6 upstream what can be done to avoid relying on timestamp 
> to trigger module rebuild.
> 
> I'll close this bug.

Thank you for investigating. What about reassigning to pristine-tar? I
wonder why it doesn' try to preserve timestamps.
Cheers,
 -- Guido

> 
> Thanks the the help
> 
> All the best
> 
> [1] see all calls to utime around there:
>  
> https://anonscm.debian.org/git/collab-maint/pristine-tar.git/tree/pristine-tar#n368
> 
> -- 
>  https://github.com/dod38fr/   -o- http://search.cpan.org/~ddumont/
> http://ddumont.wordpress.com/  -o-   irc: dod at irc.debian.org
> 

Bug#859027: telegram-desktop: Incomplete debian/copyright?

[Chris Lamb]

Source: telegram-desktop
Version: 1.0.14-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Nicholas Guriev 

Hi,

I just ACCEPTed telegram-desktop from NEW but noticed it was missing 
attribution in debian/copyright for at least:

  Telegram/Patches/qtbase_5_6_2.diff
  debian/patches/Avoid-depending-on-static-libraries.patch

etc.

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


Regards,

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

Bug#859028: emacs24: Will you consider dropping gconf support ?

[Itaï BEN YAACOV]

Package: emacs24
Version: 24.5+1-8.1
Severity: wishlist

Dear Maintainer,

The gconf library is deprecated, and on my system, only pulled in by emacs24.
Looking for various resources on its usefulness, I only found a reference in
the GNU Emacs Manual to gconf being needed for using the system font.  This
seems outdated, gsettings should suffice.  I recompiled without gconf
support, and emacs follows changes to the system monospace font just fine.

What are the reasons for keeping support for this deprecated library in
emacs24 (and emacs25) ?  Can it be removed ?

Cheers,
Itaï.


-- System Information:
Debian Release: 9.0
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages emacs24 depends on:
ii  emacs24-bin-common 24.5+1-8.1
ii  libacl12.2.52-3+b1
ii  libasound2 1.1.3-5
ii  libatk1.0-02.22.0-1
ii  libc6  2.24-9
ii  libcairo-gobject2  1.14.8-1
ii  libcairo2  1.14.8-1
ii  libdbus-1-31.10.16-1
ii  libfontconfig1 2.11.0-6.7+b1
ii  libfreetype6   2.6.3-3+b2
ii  libgdk-pixbuf2.0-0 2.36.5-2
ii  libgif75.1.4-0.4
ii  libglib2.0-0   2.50.3-2
ii  libgnutls303.5.8-5
ii  libgomp1   6.3.0-11
ii  libgpm21.20.4-6.2+b1
ii  libgtk-3-0 3.22.11-1
ii  libice62:1.0.9-2
ii  libjpeg62-turbo1:1.5.1-2
ii  libm17n-0  1.7.0-3+b1
ii  libmagickcore-6.q16-3  8:6.9.7.4+dfsg-2
ii  libmagickwand-6.q16-3  8:6.9.7.4+dfsg-2
ii  libotf00.9.13-3+b1
ii  libpango-1.0-0 1.40.4-1
ii  libpangocairo-1.0-01.40.4-1
ii  libpng16-161.6.28-1
ii  librsvg2-2 2.40.16-1+b1
ii  libselinux12.6-3+b1
ii  libsm6 2:1.2.2-1+b3
ii  libtiff5   4.0.7-5
ii  libtinfo5  6.0+20161126-1
ii  libx11-6   2:1.6.4-3
ii  libxft22.3.2-1+b2
ii  libxinerama1   2:1.1.3-1+b3
ii  libxml22.9.4+dfsg1-2.2
ii  libxpm41:3.5.12-1
ii  libxrandr2 2:1.5.1-1
ii  libxrender11:0.9.10-1
ii  zlib1g 1:1.2.8.dfsg-5

emacs24 recommends no packages.

Versions of packages emacs24 suggests:
pn  emacs24-common-non-dfsg  

-- no debconf information

Bug#810988: po4a: Always fuzzies one string, even if translation is correct (German goobox man page)

[Helge Kreutzmann]

Hello Martin,
On Tue, Mar 28, 2017 at 09:22:39PM +0200, Martin Quinson wrote:
> I am sorry to see that it took me over a year to properly investigate
> the issue. And now that I do, I cannot reproduce it. You forgot to
> attach the original sgml file in your initial report, and the bug
> seems to be gone in the current version of your package.

No problem for the delay, and yes, the bug is still present. 

> It seems to me that you had that bug with goobox v3.4.1, that you
> uploaded a few days after reporting this bug, but I cannot find it on
> the servers, and I fail to find a git repo of your repository.
> 
> Is there any chance that you still manage to reproduce that bug, maybe?

# In Testing/Unstable
apt-get source goobox
cd goobox-3.4.2/
cd debian/manpage/
# de.po is completely translated as expected
debuild
# de.po now has one fuzzy string

In the build log I see
po4a -v -f debian/po4a.cfg
debian/manpage//goobox.pot wird aktualisiert:
Redundant argument in sprintf at /usr/share/perl5/Locale/Po4a/Common.pm line 
147,  line 72.
po4a::sgml: msgid wurde übersprungen, um den Übersetzern zu helfen (enthält nur 
Tags)
Redundant argument in sprintf at /usr/share/perl5/Locale/Po4a/Common.pm line 
147,  line 134.
po4a::sgml: msgid wurde übersprungen, um den Übersetzern zu helfen (enthält nur 
eine Entity)
Redundant argument in sprintf at /usr/share/perl5/Locale/Po4a/Common.pm line 
147,  line 203.
po4a::sgml: msgid wurde übersprungen, um den Übersetzern zu helfen (enthält nur 
eine Entity)
Redundant argument in sprintf at /usr/share/perl5/Locale/Po4a/Common.pm line 
147,  line 336.
po4a::sgml: msgid wurde übersprungen, um den Übersetzern zu helfen (enthält nur 
Tags)
po4a::sgml: Warning: onsgmls produced some errors.  This is usually caused by 
po4a, which modifies the input and restores it afterwards, causing the input of 
onsgmls to be invalid.  This is usually safe, but you may wish to verify the 
generated document with onsgmls -wno-valid.  Continuing...
 (108 Einträge)
debian/manpage//de.po wird aktualisiert:
... fertig.
debian/manpage//de.po: 107 übersetzte Meldungen, 1 ungenaue Übersetzung.
Redundant argument in sprintf at /usr/share/perl5/Locale/Po4a/Common.pm line 
147,  line 72.
po4a::sgml: msgid wurde übersprungen, um den Übersetzern zu helfen (enthält nur 
Tags)
Redundant argument in sprintf at /usr/share/perl5/Locale/Po4a/Common.pm line 
147,  line 134.
po4a::sgml: msgid wurde übersprungen, um den Übersetzern zu helfen (enthält nur 
eine Entity)
Redundant argument in sprintf at /usr/share/perl5/Locale/Po4a/Common.pm line 
147,  line 203.
po4a::sgml: msgid wurde übersprungen, um den Übersetzern zu helfen (enthält nur 
eine Entity)
Redundant argument in sprintf at /usr/share/perl5/Locale/Po4a/Common.pm line 
147,  line 336.
po4a::sgml: msgid wurde übersprungen, um den Übersetzern zu helfen (enthält nur 
Tags)
po4a::sgml: Warning: onsgmls produced some errors.  This is usually caused by 
po4a, which modifies the input and restores it afterwards, causing the input of 
onsgmls to be invalid.  This is usually safe, but you may wish to verify the 
generated document with onsgmls -wno-valid.  Continuing...
debian/manpage/goobox.de.sgml ist zu 99.08% übersetzt (108 von 109 
Zeichenketten).

> Thanks for your patience, Mt.

Thanks for taking care!

> > po4a::sgml: Warning: onsgmls produced some errors.  This is usually caused 
> > by po4a, which modifies the input and restores it afterwards, causing the 
> > input of onsgmls to be invalid.  This is usually safe, but you may wish to 
> > verify the generated document with onsgmls -wno-valid.  Continuing...

Still present, see above.

If you need further files/information please do not hesitate to contact me.

Greetings

Helge
-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: Digital signature

Bug#858195: compass-bootstrap-sass-plugin: Wrong install path, and code not registered with Compass

[Jonas Smedegaard]

Quoting Antonio Terceiro (2017-03-29 17:42:33)
> Control: severity -1 important
> 
> On Wed, Mar 29, 2017 at 03:51:50PM +0200, Jonas Smedegaard wrote:
> > Quoting Antonio Terceiro (2017-03-28 20:01:37)
> > > Control: severity -1 wishlist
> > [...]
> > > While I agree with you that it _could_ work transparently, there 
> > > is nothing broken in the package. And I don't think this is 
> > > something we should be doing different from upstream.
> > 
> > Do you still believe there was nothing broken in the package?
> 
> No. Actually, it was _you_ who said that the original invocation as 
> documented by upstream worked with the version in testing:
> 
> $ compass create --using bootstrap-sass --require bootstrap-sass
> 
> I tested that again, and it turns out it doesn't.

I do not recognize having said that.  It helps if you quote the exact 
text you are referring to.


>> Please consider acknowledging that the former path was buggy, so that 
>> there is a chance of getting a fix included with Stretch.
> 
> Sure. I was going to request an unblock either way.

Thanks.


 - Jonas

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

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


signature.asc
Description: signature

Bug#858961: Dictionary includes apparent non-word "mys"

[Don Armstrong]

On Tue, 28 Mar 2017, Josh Triplett wrote:
> The scowl english wordlist includes "mys" at level 35.  However, no
> dictionary I can find actually lists that as a word.  A couple list it
> as a prefix or suffix, but not as a word in itself.

Yeah, not sure why that is included. Will patch it in Debian and raise
it upstream.


-- 
Don Armstrong  https://www.donarmstrong.com

Leukocyte... I am your father.
 -- R. Stevens http://www.dieselsweeties.com/archive.php?s=1546

Bug#858851: debarchiver: [INTL:de] updated German man page translation

[Helge Kreutzmann]

Hello Ola,
On Tue, Mar 28, 2017 at 09:17:22PM +0200, Ola Lundqvist wrote:
> It should be in unstable/sid in an hour or so.

1.11.1  has not yet appeared in Unstable. Has there been a problem
while uploading?

Greetings

  Helge
-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: Digital signature

Bug#858533: rtslib-fb-targetctl: doesn't work with sysvinit due to missing configfs mount

[Christian Seiler]

On 03/29/2017 03:31 PM, Harald Dunkel wrote:
> I agree about mounting configfs in the init script, but please
> note that /sys/kernel/config *is* mounted early at boot time.
> Its just not available yet.

No, it isn't mounted early at boot time, at least not from
sysvinit, due to a bug (see below).

> Maybe the LSB header is bad, or the timeout in rtslib-fb-targetctl
> has to be increased.

So apparently something else mounts configfs in your case that
is run in parallel to LIO. But the LSB headers of targetctl
clearly indicate that it's a standard service that's run _way_
later than early-boot services, even after $remote_fs - so
/etc/init.d/mountkernfs.sh will definitely have been run already
at that point.

The problem with mountkernfs.sh in sysvinit is that it will only
mount configfs if /sys/kernel/config exists, which will only
exist if the configfs module is loaded, which will only happen
after mountkernfs.sh is started on sysvinit. (systemd in contrast
loads modules before mounting things such as configfs nowadays;
it also got that wrong in the past though.) This bug in sysvinit
(or more accurately the initscripts package) is the bug I
referenced:

https://bugs.debian.org/840356

If in your case after boot configfs is mounted anyway, there's
another service that does that for you. Could you grep for
configfs in /etc/init.d? You'll probably fine something other
than targetctl or mountkernfs.sh that will mount it at a later
point in boot - but that's definitely not something I'd rely
on.

The proper way to fix this is to fix the initscripts package to
load modules before mounting configfs. Since targetctl is not
an early-boot service, ordering will automatically be correct
then and your use case will work.

However, that's something you'll have to take up with the
sysvinit/initscripts maintainers, because it clearly is a bug
in those packages.

(Actually, this is the first time I've looked at the targetctl
init script, and the loop in there waiting for configfs to be
mounted really should NOT be there, that is just plain wrong.
configfs availability should be done via ordering, not waiting
in the packground for stuff to start - because that really is
non-deterministic. And the ordering is actually correct
already; the other package that mounts configfs in the init
script is buggy in my eyes because it does something it should
not, as well as sysvinit for not properly mounting configfs in
the first place.)

The only "workaround" would be to mount configfs ourselves in
the targetctl init script, but to me this really not
advisable, because if something else is already mounting
configfs in the background, then the mount command could be
issued twice - which shouldn't happen, and can cause some
unexpected issues (appearing in /proc/mounts or
/proc/self/mountinfo twice for the same mount point could break
some scripts that don't expect that, for example. And since
the mount command being issued twice depends on a race
condition, this would be non-deterministic and very difficult
to debug).

Regards,
Christian

Bug#859017: pulseaudio: switch-on-port-available picks unavailable device port

[Felipe Sateler]

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

On Wed, Mar 29, 2017 at 1:51 PM, Vivek Das Mohapatra
 wrote:
> On Wed, 29 Mar 2017, Felipe Sateler wrote:
>
>> Could you forward this issue upstream to
>> pulseaudio-disc...@lists.freedesktop.org ? This looks like
>> something that should be fixed upstream.
>
>
> I've already filed https://bugs.freedesktop.org/show_bug.cgi?id=100451
>
> Is that good enough or should I also ping the list?

That's good enough, thanks! I somehow missed that you had filed this.

I'll wait for that discussion to settle before applying the patch
though. It appears the patched code was correct after all.

-- 

Saludos,
Felipe Sateler

Bug#855922: [pkg-go] Bug#855922: containerd: 0.2.3 ds1-1 breaks docker 1.11 - unable to start containerd

[Michael Stapelberg]

Hi Tim,

"Potter, Tim"  writes:
> Hi Ricardo.  Thanks for the bug report.  I messed up by uploading some of the 
> Docker 1.13
> dependencies to unstable instead of experimental - my apologies.
>
> I've done a new upload with a Breaks line to avoid this bug occurring until I 
> finish testing
> 1.13 and uploading to unstable.

I’m still running into this issue (or a very similar one?) with:

docker.io 1.13.0~ds1-2
runc 0.1.1+dfsg1-2+b1
containerd 0.2.3~git20161117.78.03e5862~ds1-2
golang-libnetwork 0.8.0~dev.2+git20161130.568.fd27f22-4

I installed these packages from Debian unstable, but AFAICT, no newer
version is available in experimental.

The symptom is:
$ docker run -t -i debian:sid /bin/bash
docker: Error response from daemon: containerd: container not started.

In the journal, I can’t see any errors from containerd itself.

Should docker be working in Debian at the moment? If not, is there a
workaround?

Thanks!

-- 
Best regards,
Michael

Bug#859017: pulseaudio: switch-on-port-available picks unavailable device port

[Vivek Das Mohapatra]

On Wed, 29 Mar 2017, Felipe Sateler wrote:


Could you forward this issue upstream to
pulseaudio-disc...@lists.freedesktop.org ? This looks like
something that should be fixed upstream.


I've already filed https://bugs.freedesktop.org/show_bug.cgi?id=100451

Is that good enough or should I also ping the list?

Bug#858849: installation-reports: Successful Jessie installation with backported kernel 4.9.16-1+reiser4.0.1 on i915 system AMD64

[Steve McIntyre]

Hi,

On Wed, Mar 29, 2017 at 09:27:42AM -0700, Jose R R wrote:
>On Wed, Mar 29, 2017 at 8:48 AM, Cyril Brulebois  wrote:
>> Jose R R  (2017-03-29):
>>
>>> "We also encourage installation reports to be sent even if the
>>> installation is successful, so that we can get as much information as
>>> possible on the largest number of hardware configurations." <
>>> https://www.debian.org/releases/stable/amd64/ch05s04.html.en#submit-bug
>>> >
>>
>> Sure, with official images.
>>
>>> If you are still 'bothered' with my sporadic submissions, I encourage
>>> you to modify the documentation to specifically exclude the glaring
>>> omission.
>>
>> I could be adding a specific “we don't need reiser4-specific reports”
>
>Please do add that phrase; thus removing any ambiguities and cover the
>glaring omission in the Debian documentation.

It's hardly a "glaring omission" that we don't list *explicitly*:

 * we don't want reiser4-specific reports
 * we don't want Ubuntu installation reports
 * we don't want installation reports about other modified images

You're reading the "Installation Guide for Debian", not the
"Installation Guide for every unofficial user-modified version of
Debian". The docs are meant to describe how to install Debian using
Debian's installer - is that not obvious?

>That clarification will prevent other individuals -- who have
>downloaded the netboot installer from SourceForge -- from potentially
>reporting via the debian mechanism -- once the installation completes.
>
>Additionally, appending “we don't need reiser4-specific reports” will
>be a welcome *explicit* change in policy from other FOSS projects,
>like GNU Parted, where the unspoken censorship on reiser4 bites anyone
>who submits patches in support of the
>'Batman Machine': Reiser4
>< https://metztli.it/readOnlyEphemeral/Batman_Machine-Reiser4.pdf >

I understand that you're working on reiser4 stuff and you'd like to
publicise it - that's cool and I hope it's working well for you! But
spamming us here is *not* helping. OK?

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"When C++ is your hammer, everything looks like a thumb." -- Steven M. Haflich

Bug#859025: imagemagick: CVE-2017-7275

[Salvatore Bonaccorso]

Source: imagemagick
Severity: minor
Tags: security upstream

Hi,

the following vulnerability was published for imagemagick.

CVE-2017-7275[0]:
| The ReadPCXImage function in coders/pcx.c in ImageMagick 7.0.4.9 allows
| remote attackers to cause a denial of service (attempted large memory
| allocation and application crash) via a crafted file. NOTE: this
| vulnerability exists because of an incomplete fix for CVE-2016-8862 and
| CVE-2016-8866.

NOTE: I'm opening still a bug for this, since it is unclear if that's
really a problem. Upstream is not able to reproduce the issue, and it
might be an issue on the reporter side.

For now the issue is marked as 'non-issue' in the security-tracker,
but in case more details and reproducibility is given of the issue,
and patch of upstream available, we might go forward and reevaluate
this.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-7275
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7275
[1] https://github.com/ImageMagick/ImageMagick/issues/271

Regards,
Salvatore

Bug#859026: Uses uscan in the clean target and passes its output to rm

[Andrey Rahmatullin]

Package: src:sugar-physics-activity
Version: 7+dfsg-1.3
Severity: critical

UPSTREAM_VERSION ?=$(shell uscan --dehs | sed -n 's/.*\(.*\)<\/upstream-version>.*/\1/p')
[...]
clean::
[...]
rm -rf Physics-${UPSTREAM_VERSION}

So, it uses network (the build without network doesn't fail though), it
downloads an unnecessary file, it looks for a latest version instead of the
package version and it puts untrusted network input right into an rm command.



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

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

Bug#859017: pulseaudio: switch-on-port-available picks unavailable device port

[Felipe Sateler]

Hi,

On Wed, Mar 29, 2017 at 12:14 PM, Vivek Das Mohapatra
 wrote:
> Package: pulseaudio
> Version: 5.0-13
> Severity: normal
>
> Dear Maintainer,
>
>* What led up to the situation?
>
>  Volume/Mute state was not restored on a laptop on reboot:
>  The speaker was always muted.
>
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>
>  Set the volume (in either gdm or gnome), rebooted (either from
>  within the gnome session or after logging out).
>
>* What was the outcome of this action?
>
>  Sound (speaker) was always muted on reboot.
>
>* What outcome did you expect instead?
>
>  Volume should have been restored to the value recorded
>  in the pulseaudio .tdb files.
>
> Eventually tracked this down to the wrong device port being selected by
> module-switch-on-port-available - the helper function new_sink_source
> iterates over the device ports and picks the one with the highest priority
> but then, just before returning, does this:
>
> if (p->available != PA_AVAILABLE_NO)
> return NULL;
>
> ie the selected port is returned _only_ if it is NOT available.
>
> This logic error appears to be in pulseaudio 10.x (the stretch version)
> also.
>
> This is used by (for example):
>
>   static pa_hook_result_t sink_new_hook_callback(pa_core *c,
> pa_sink_new_data *new_data, void *u) {
>
>   pa_device_port *p = new_sink_source(new_data->ports,
> new_data->active_port);
>
>   if (p) {
>   pa_log_debug("Switching initial port for sink '%s' to '%s'",
> new_data->name, p->name);
>   pa_sink_new_data_set_port(new_data, p->name);
>   }
>   return PA_HOOK_OK;
>   }
>
> So this module will never choose an available port.
>
> The p->available != PA_AVAILABLE_NO pattern appears all over the place in
> this module but I _think_ this is the only place where it's used the
> wrong way round.
>
> The following fixed the symptom here (and the pa - log indicated that
> a more sensible set of choices was being made with it applied):
>
> --- a/src/modules/module-switch-on-port-available.c
> +++ b/src/modules/module-switch-on-port-available.c
> @@ -256,7 +256,7 @@
>  p = i;
>  if (!p)
>  return NULL;
> -if (p->available != PA_AVAILABLE_NO)
> +if (p->available == PA_AVAILABLE_NO)
>  return NULL;
>
>  pa_assert_se(p = find_best_port(ports));
>

Your analysis looks correct to me. Could you forward this issue
upstream to pulseaudio-disc...@lists.freedesktop.org ? This looks like
something that should be fixed upstream.


-- 

Saludos,
Felipe Sateler

Bug#859024: unblock: libjs-jquery-selectize.js/0.12.3+dfsg-1.1

[Andrey Rahmatullin]

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

Please unblock package libjs-jquery-selectize.js

It fixes RC #857988

diff -Nru libjs-jquery-selectize.js-0.12.3+dfsg/debian/changelog libjs-jquery-
selectize.js-0.12.3+dfsg/debian/changelog
--- libjs-jquery-selectize.js-0.12.3+dfsg/debian/changelog  2016-08-31
22:22:43.0 +0500
+++ libjs-jquery-selectize.js-0.12.3+dfsg/debian/changelog  2017-03-29
20:50:45.0 +0500
@@ -1,3 +1,10 @@
+libjs-jquery-selectize.js (0.12.3+dfsg-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop unused B-D: npm (Closes: #857988).
+
+ -- Andrey Rahmatullin   Wed, 29 Mar 2017 20:50:45 +0500
+
 libjs-jquery-selectize.js (0.12.3+dfsg-1) unstable; urgency=medium

   * Update d/copyright to exclude jquery.min.js, in preparation for new
release.
diff -Nru libjs-jquery-selectize.js-0.12.3+dfsg/debian/control libjs-jquery-
selectize.js-0.12.3+dfsg/debian/control
--- libjs-jquery-selectize.js-0.12.3+dfsg/debian/control2016-08-20
12:00:41.0 +0500
+++ libjs-jquery-selectize.js-0.12.3+dfsg/debian/control2017-03-29
20:50:45.0 +0500
@@ -8,7 +8,6 @@
  libjs-jquery,
  libjs-sifter.js,
  libjs-microplugin.js,
- npm,
 Standards-Version: 3.9.8
 Homepage: https://github.com/selectize/selectize.js
 Vcs-Git: https://anonscm.debian.org/git/pkg-javascript/libjs-jquery-
selectize.js.git


unblock libjs-jquery-selectize.js/0.12.3+dfsg-1.1

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

Kernel: Linux 4.10.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)

Bug#859023: unblock: karchive/5.28.0-2

[Maximiliano Curia]

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

Dear release team,

Checking some of the KDE frameworks bugs and upstream fixes I stumbled upon a 
couple of changes in karchive that I think that it would be good to include 
for stretch. The changes consist on 3 new upstream patches to fix 2 problems:
  + Fix the seek implementation in KCompressionDevice (the only user that I've
found is libkdeedu's libkeduvocdocument4).
Patches: Fix-KCompressionDevice-to-work-with-Qt-5.7.patch
 Fix-my-fix-for-KCompressionDevice-seek.patch
  + A minor leak fix
Patch: Fix-Potential-leak-of-memory-pointed-to-by-limitedDev.patch

I'm attaching the debdiff between the 5.28.0-1 and 5.28.0-2 versions.

This patches are included in the 5.28.0-2 version currently in unstable and it 
has already built in all the release archs.

Please unblock package karchive

Happy hacking,

unblock karchive/5.28.0-2

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

Kernel: Linux 4.9.0-1-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/bash
Init: systemd (via /run/systemd/system)
diff -Nru karchive-5.28.0/debian/changelog karchive-5.28.0/debian/changelog
--- karchive-5.28.0/debian/changelog2016-11-18 16:00:41.0 +0100
+++ karchive-5.28.0/debian/changelog2017-03-29 15:09:44.0 +0200
@@ -1,3 +1,13 @@
+karchive (5.28.0-2) unstable; urgency=medium
+
+  * Add upstream patches for KCompressionDevice::seek:
++ Fix-KCompressionDevice-to-work-with-Qt-5.7.patch
++ Fix-my-fix-for-KCompressionDevice-seek.patch
+  * Backport upstream patch:
++ Fix-Potential-leak-of-memory-pointed-to-by-limitedDev.patch
+
+ -- Maximiliano Curia   Wed, 29 Mar 2017 15:09:44 +0200
+
 karchive (5.28.0-1) unstable; urgency=medium
 
   [ Automatic packaging ]
diff -Nru 
karchive-5.28.0/debian/patches/Fix-KCompressionDevice-to-work-with-Qt-5.7.patch 
karchive-5.28.0/debian/patches/Fix-KCompressionDevice-to-work-with-Qt-5.7.patch
--- 
karchive-5.28.0/debian/patches/Fix-KCompressionDevice-to-work-with-Qt-5.7.patch 
1970-01-01 01:00:00.0 +0100
+++ 
karchive-5.28.0/debian/patches/Fix-KCompressionDevice-to-work-with-Qt-5.7.patch 
2017-03-29 15:09:44.0 +0200
@@ -0,0 +1,78 @@
+From: Albert Astals Cid 
+Date: Sat, 4 Feb 2017 17:02:34 +0100
+Subject: Fix KCompressionDevice to work with Qt >= 5.7
+
+Don't use QIODevice:pos to track our pos, doesn't do what we want it to do.
+Call QIODevice::seek at the beginning as documentation says has to be done.
+
+Differential Revision: 4422
+---
+ src/kcompressiondevice.cpp | 16 ++--
+ 1 file changed, 10 insertions(+), 6 deletions(-)
+
+diff --git a/src/kcompressiondevice.cpp b/src/kcompressiondevice.cpp
+index de22bf8..04466a6 100644
+--- a/src/kcompressiondevice.cpp
 b/src/kcompressiondevice.cpp
+@@ -48,6 +48,7 @@ public:
+ , bOpenedUnderlyingDevice(false)
+ , bIgnoreData(false)
+ , type(KCompressionDevice::None)
++, deviceReadPos(0)
+ {
+ }
+ bool bNeedHeader;
+@@ -59,6 +60,7 @@ public:
+ KFilterBase::Result result;
+ KFilterBase *filter;
+ KCompressionDevice::CompressionType type;
++qint64 deviceReadPos;
+ };
+ 
+ KFilterBase 
*KCompressionDevice::filterForCompressionType(KCompressionDevice::CompressionType
 type)
+@@ -174,8 +176,10 @@ void KCompressionDevice::close()
+ 
+ bool KCompressionDevice::seek(qint64 pos)
+ {
+-qint64 ioIndex = this->pos(); // current position
+-if (ioIndex == pos) {
++if (!QIODevice::seek(pos))
++return false;
++
++if (d->deviceReadPos == pos) {
+ return true;
+ }
+ 
+@@ -189,13 +193,13 @@ bool KCompressionDevice::seek(qint64 pos)
+ d->result = KFilterBase::Ok;
+ d->filter->setInBuffer(0L, 0);
+ d->filter->reset();
+-QIODevice::seek(pos);
++d->deviceReadPos = 0;
+ return d->filter->device()->reset();
+ }
+ 
+ qint64 bytesToRead;
+-if (ioIndex < pos) { // we can start from here
+-bytesToRead = pos - ioIndex;
++if (d->deviceReadPos < pos) { // we can start from here
++bytesToRead = pos - d->deviceReadPos;
+ } else {
+ // we have to start from 0 ! Ugly and slow, but better than the 
previous
+ // solution (KTarGz was allocating everything into memory)
+@@ -210,7 +214,6 @@ bool KCompressionDevice::seek(qint64 pos)
+ d->bIgnoreData = true;
+ const bool result = (read(dummy.data(), bytesToRead) == bytesToRead);
+ d->bIgnoreData = false;
+-QIODevice::seek(pos);
+ return result;
+ }
+ 
+@@ -303,6 +306,7 @@ qint64 

Bug#858849: installation-reports: Successful Jessie installation with backported kernel 4.9.16-1+reiser4.0.1 on i915 system AMD64

[Jose R R]

Niltze,

On Wed, Mar 29, 2017 at 8:48 AM, Cyril Brulebois  wrote:
> Hi,
>
> Jose R R  (2017-03-29):
>> With all due respect, 99% of the build code for the debian-installer
>> is yours. As well as the build pulls 99% UDEBs from official debian
>> repositories.
>
> That doesn't mean that everything built on top of it has to be reported
> on Debian mailing lists and bug tracker. See derivative distributions,
> they have their own issue tracker, and only forward specific issues.
>
>> i.e., this is a Debian issue, not mine -- as I did not even touch that
>> code and/or modules -- which 1 month ago actually did work smooth:
>>
>> Netboot debian-installer was unable to load firmware from second USB
>> for wifi connection; accordingly, in another virtual screen, I mounted
>> the 2nd USB and manually copied the firmware directory onto the
>> installer environment /lib. d-i then detected the wifi signal, etc.
>>
>>
>> Second, report on this unofficial jessie-backports kernel
>> 4.9.16-1+reiser4.0.1 sheds light on the fact I experienced *no issue*
>> with module i915, as had been reported by (maintainer?): <
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858078 > thus, in a
>> collateral manner, I am contributing to official debian development.
>
> If you want to reply to submitters/maintainers, reply to specific bug
> reports/threads, instead of sending lengthy mails to other people?
>
>> Finally, I am not requesting *any* support. I am simply reporting that
>> your d-i pulling official UDEBs actually have been successful, with
>> minor modifications and a few extra UDEBs of mine, in my installation
>> experience, following Debian documentation guidelines:
>
> I haven't put words in your mouth and suggested you were requesting some
> support. I'm just not convinced such reports are useful. If you
> encounter specific issues, report specific bug reports against the
> relevant component.
>
> debian-boot@ isn't and shouldn't be the destination of each and every
> thing connected to, or merely using, Debian Installer.
>
>> "We also encourage installation reports to be sent even if the
>> installation is successful, so that we can get as much information as
>> possible on the largest number of hardware configurations." <
>> https://www.debian.org/releases/stable/amd64/ch05s04.html.en#submit-bug
>> >
>
> Sure, with official images.
>
>> If you are still 'bothered' with my sporadic submissions, I encourage
>> you to modify the documentation to specifically exclude the glaring
>> omission.
>
> I could be adding a specific “we don't need reiser4-specific reports”

Please do add that phrase; thus removing any ambiguities and cover the
glaring omission in the Debian documentation.

That clarification will prevent other individuals -- who have
downloaded the netboot installer from SourceForge -- from potentially
reporting via the debian mechanism -- once the installation completes.

Additionally, appending “we don't need reiser4-specific reports” will
be a welcome *explicit* change in policy from other FOSS projects,
like GNU Parted, where the unspoken censorship on reiser4 bites anyone
who submits patches in support of the
'Batman Machine': Reiser4
< https://metztli.it/readOnlyEphemeral/Batman_Machine-Reiser4.pdf >


Again, thank you.


Best Professional Regards.

-- 
Jose R R
http://metztli.it
-
Download Debian-Reiser4 for AMD64 https://sf.net/projects/debian-reiser4/
-
Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
-
from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!