Bug#847931: joe: Segmentation fault

[Vitez Gabor]

Package: joe
Version: 4.3-1
Followup-For: Bug #847931

Dear Maintainer,

A quick followup: the " characters at the start and end of the one-liner 
are needed to produce the segfault. The unmodified original that segfaults joe 
is this:

script -c "tar  --one-file-system -cf - /boot |tee \"$OUT\" |md5sum 
>\"$OUT.md5\";sync" $OUT.out



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

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

Versions of packages joe depends on:
ii  libc62.24-8
ii  libncurses5  6.0+20161126-1
ii  libtinfo56.0+20161126-1

joe recommends no packages.

joe suggests no packages.

-- no debconf information

Bug#849787: probably best to just ignore this for Stretch

[Russell Coker]

priority 849787 wishlist
thanks

I've made selinux policy packages conflict with mcstrans so this shouldn't be 
a problem any more.

-- 
My Main Blog http://etbe.coker.com.au/
My Documents Bloghttp://doc.coker.com.au/

Bug#847931: joe: Segmentation fault

[Vitez Gabor]

Package: joe
Version: 4.3-1
Followup-For: Bug #847931

Dear Maintainer,


Editing a one-liner shell script makes joe segfault. This is the "script":
"tar  --one-file-system -cf - /boot | tee \"$OUT\" |md5sum  >\"$OUT.md5\";sync"


Joe only segfaults if the file name ends with .sh, or a #!/bin/sh or 
#!/bin/bash line is 
prepended, so the issue could be with the shell syntax highlighting.

dmesg shows these after two tries:
[ 2673.397432] joe[11870]: segfault at 42 ip 5618a13515c5 sp 
7fff2964e170 error 4 in joe[5618a12fc000+8a000]
[ 2692.855386] joe[12221]: segfault at 42 ip 55ea88cdb5c5 sp 
7ffe954188b0 error 4 in joe[55ea88c86000+8a000]




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

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

Versions of packages joe depends on:
ii  libc62.24-8
ii  libncurses5  6.0+20161126-1
ii  libtinfo56.0+20161126-1

joe recommends no packages.

joe suggests no packages.

-- no debconf information

Bug#849845: [pkg-gnupg-maint] Bug#849845: Bug#849845: dirmngr: Can't resolve keyserver hostname anymore

[intrigeri]

shirish शिरीष:
> in-line :-

> On 07/01/2017, Daniel Kahn Gillmor  wrote:
>> Have you restarted dirmngr since the upgrade?

> how do I restart it ?

systemctl --user restart dirmngr.socket 

:)

Bug#850586: leafnode: watchfile needs update

[Andreas Metzler]

Package: leafnode
Version: 1.11.10-3
Severity: normal
Tags: patch

Hello,

the watchfile points to an outdated URL. Find attached a new version,
which will promptly find leafnode 1.11.11.

cu Andreas

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

opts=uversionmangle=s/-/~/,pgpsigurlmangle=s/$/.asc/  \
http://krusty.dt.e-technik.tu-dortmund.de/~ma/leafnode/leafnode-@ANY_VERSION@@ARCHIVE_EXT@

Bug#850221: Errata

[solitone]

> Trying the following command from ssh has no effect--it doesn't change the 
> value in bl_power and the screen doesn't turn on:
> $ xset -display :0 dpms force off

Sorry, I meant:
$ xset -display :0 dpms force on

Bug#850256: RFS:node-pkg-conf -- Get namespaced config from the closest package.json

[akshay kemekar]

i have done node-pkg-conf it's lintian and clean. i had done sbuild also.
the link is:https://github.com/akshaykemekar/pkg-conf

please review and sponsor.
thank you.

Bug#850585: ITP: node-progress-stream -- Read the progress of a stream

[Yashashree Kolhe]

Package: wnpp
Severity: wishlist
Owner: Yashashree Kolhe 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-progress-stream
  Version : 1.2.0
  Upstream Author : freeall 
* URL : https://github.com/freeall/progress-stream#readme
* License : BSD-2-Clause
  Programming Lang: JavaScript
  Description : Read the progress of a stream
  Gets the lengths of the stream automatically if you're using the
request or httpmodule. You can also pass the length on initiation.
Progress-stream will also check to see if the stream already have a
length property.

  It is a dependency of nugget which is needed to be packaged for riot.

Bug#850221: brightness, actual_brightness, bl_power

[solitone]

I've checked with ssh that, after resume, I have the following values in 
backlight files brightness, actual_brightness, and bl_power:

$ cat /sys/class/backlight/intel_backlight/brightness 
1388
$ cat /sys/class/backlight/intel_backlight/actual_brightness 
0
$ cat /sys/class/backlight/intel_backlight/bl_power 
4

Trying the following command from ssh has no effect--it doesn't change the 
value in bl_power, and the screen doesn't turn on:

$ xset -display :0 dpms force off

I get the issue everytime I hibernate with bl_power set to 4 (screen off).

Bug#850584: qemu: Please provide qemu without GTK for headless machines

[Peter Colberg]

Package: qemu
Version: 1:2.8+dfsg-1
Severity: wishlist

Dear Maintainer,

The upgrade to the above version pulls in a large number of new packages:

# apt upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  libcaca0 libsdl1.2debian
Use 'apt autoremove' to remove them.
The following NEW packages will be installed:
  adwaita-icon-theme dconf-gsettings-backend dconf-service fontconfig 
fontconfig-config fonts-dejavu-core
  glib-networking glib-networking-common glib-networking-services 
gsettings-desktop-schemas gtk-update-icon-cache
  hicolor-icon-theme libatk-bridge2.0-0 libatk1.0-0 libatk1.0-data 
libatspi2.0-0 libavahi-client3
  libavahi-common-data libavahi-common3 libcairo-gobject2 libcairo2 libcolord2 
libcroco3 libcups2 libdatrie1
  libdconf1 libdrm2 libegl1-mesa libepoxy0 libfontconfig1 libgbm1 
libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common
  libgraphite2-3 libgtk-3-0 libgtk-3-common libharfbuzz0b libjbig0 
libjson-glib-1.0-0 libjson-glib-1.0-common
  liblcms2-2 libnuma1 libpango-1.0-0 libpangocairo-1.0-0 libpangoft2-1.0-0 
libpcre2-8-0 libproxy1v5 librest-0.7-0
  librsvg2-2 librsvg2-common libsoup-gnome2.4-1 libsoup2.4-1 libthai-data 
libthai0 libtiff5 libvirglrenderer0
  libvte-2.91-0 libvte-2.91-common libwayland-client0 libwayland-cursor0 
libwayland-egl1-mesa libwayland-server0
  libxcb-dri2-0 libxcb-dri3-0 libxcb-present0 libxcb-render0 libxcb-shm0 
libxcb-sync1 libxcb-xfixes0 libxcomposite1
  libxcursor1 libxdamage1 libxfixes3 libxinerama1 libxkbcommon0 libxrandr2 
libxrender1 libxshmfence1 shared-mime-info
  xkb-data
The following packages will be upgraded:
  qemu-system-common qemu-system-x86
2 upgraded, 80 newly installed, 0 to remove and 0 not upgraded.
Need to get 36.0 MB of archives.
After this operation, 108 MB of additional disk space will be used.
Do you want to continue? [Y/n] ^C


On a headless machine, all of the above libraries will be effectively
unused, and the number of potential security updates that necessitate
a restart of qemu instances is increased significantly.

Could you provide package variants for headless servers without GTK?
This probably comes (too) late for the stretch release cycle; it’s a
bit unfortunate that the switch to GTK (#839695) was made only now.

Regards,
Peter

Bug#850583: csvkit is missing documentation

[Craig Sanders]

Package: python3-csvkit
Version: 0.9.1-3

NOTE: this applies to python-csvkit as well as python3-csvkit

The upstream github repository for csvkit includes documentation for the
included command-line tools as well as tutorials and examples of how to
use csvkit.

None of this is present in the debian packages python-csvkit or
python3-csvkit.

the csvkit tools don't even have '-h' or '--help' options, making
documentation even more important.


The documentation on github is in ReStructured Text (.rst) format.  This
is easily converted with tools like pandoc or python-docutils into man
pages, html pages, pdf, epub, and several other formats.

This conversion should be done during the package build, in the
debian/rules makefile, with the output placed in the correct location.
This would require a build-depends on the tool used (pandoc, docutils,
etc).

craig

--
craig sanders 

Bug#824252: -t and -d don't work as expected

[Craig Sanders]

On Sat, Jan 07, 2017 at 10:28:14PM -0500, Sandro Tosi wrote:
> upstream at https://github.com/wireservice/csvkit/issues/666 closed
> the issue with
> 
> ```
> Not a bug. You must pipe the output of a command into csvformat to
> change the output format.
> ```
> 
> hence i'm closing this report as well. If you still think something
> needs fixing, i suggest to continue discussing that upstream on the
> mentioned github issue

The upstream response misses the point (and the problem) entirely.

Here's the real issue, quoted from my original bug report.

 > Using tr or similar to work around this is unreliable - there may be
 > actual commas in any of the tab-separated fields.

(i made a mistake there. i meant to say "any of the comma-separated
fields", not "tab-separated").

if there are commas inside the fields, in the actual data, it is
**impossible** for any other program that post-processes csvkit's
output to distinguish between a comma within a field from a comma that
separates a field.  That includes csvformat as well as tr, awk, sed, or
any other tool.

THAT is why being able to specify the output field separator is
essential - so you can choose a delimiter that ISN'T in the data.

if csvkit can't do that, then it's not fit for purpose.

This sort of data vs delimiter problem is very common. If you can choose
the delimiter, then it's a trivial problem to solve, easily scripted.
If you can't choose, then the **only** way to be certain that your
output isn't going to be garbled by an extra comma or tab is to visually
inspect it and edit it by hand - it is a task that requires human-level
intelligence and great patience and attention to detail (or at least AI
parsing of the data)



I'll leave it up to you to decide whether it's worth re-opening this
bugupstream seems either indifferent or hostile to fixing it.

I will open another bug report, though. Looking at the github repo, it
seems that documentation for csvkit does exist.  I thought there wasn't
any, but there is, in .rst format - it's just missing from the debian
packages. rst files can easily be converted to manpages, html, epub,
pdf, and other formats with, e.g., pandoc or python-docutils.

craig

--
craig sanders 

Bug#850582: RM: src:sphinxcontrib-phpdomain -- ROM; Useless in Debian

[Scott Kitterman]

Package: ftp.debian.org
Severity: normal

See #818673.

Bug#850580: ITP: node-home-path -- Cross-platform home directory retriever

[Nupur Malpani]

Package: wnpp
Severity: wishlist
Owner: Nupur Malpani 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-home-path
  Version : 1.0.3
  Upstream Author : Lloyd Brookes <75po...@gmail.com>
* URL : https://github.com/75lb/home-path#readme
* License : Expat
  Programming Lang: JavaScript
  Description : Cross-platform home directory retriever

Bug#850113: vim-youcompleteme: 'KeyError's on every key press flooding vim

[Vitry David Gilbert]

Bonjour,
For me patch from
https://github.com/Valloric/YouCompleteMe/commit/85d58448732b46359db3e38b862ba935d7c3bb02

seems to work

Thank


signature.asc
Description: OpenPGP digital signature

Bug#649860: closing RFP: wwwoffle -- World Wide Web OFFline Explorer

[Axel Beckert]

Control: reopen -1

Hi Bart,

Bart Martens schrieb am Fri, Jan 06, 2017 at 04:20:17PM +:
> RFP 649860 has no visible progress for a long time, so closing.

That doesn't mean that there's no more interest in getting wwwoffle
back into Debian. It's an RFP and not an ITP after all.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#832937: RFP: python3-pypeg2 -- a PEG Parser-Interpreter in Python

[Axel Beckert]

Control: retitle -1 ITP: python3-pypeg2 -- a PEG Parser-Interpreter in Python
Control: owner -1 Fritz Reichwald 

Hi Bart,

once again: please stop modifying WNPP bugs without having really read them!

Bart Martens wrote:
> I guess you meant to express that you want this software added in Debian by
> someone else than yourself

Why did you guess so? Fritz explicitly wrote:

| I packaged this because qutebrowser
| https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832159 needs it.
| Files can be found in my github:
| https://github.com/V155/python-pypeg2/tree/debian-2.15.2

I think that very obvious that he intents to package it and this was
_not_ meant to be an RFP

Thanks!

Regards, Axel (about to sponsor the initial upload of pypeg2)
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#790235: [Python-modules-team] Bug#790235: basemap: [PATCH] please make the build reproducible

[Sandro Tosi]

On Mon, Aug 15, 2016 at 11:13 PM, Juan Picca  wrote:
> The patch is no longer valid.
> Also, basemap 1.0.7+dfsg-3 currently is not reproducible.
> I hope that in the coming weeks i will have the time to make the build
> reproducible.

gentle ping

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#850579: process `snmpd' is using deprecated sysctl (syscall) net.ipv6.neigh.lo.retrans_time - use net.ipv6.neigh.lo.retrans_time_ms instead

[Vladislav Artemyev]

package: snmpd
version: 5.7.2.1+dfsg-1

it's probably related to an archived #428824 
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=428824) which mention 
it could have been fixed in 5.7.2~dfsg-1~0.1, yet it's still there. not 
sure about conditions when it happens:


kern.log:Jan  6 09:09:03 bar kernel: [15065.486444] ICMPv6: process 
`snmpd' is using deprecated sysctl (syscall) 
net.ipv6.neigh.lo.retrans_time - use net.ipv6.neigh.lo.retrans_time_ms 
instead
messages:Jan  6 09:09:03 bar kernel: [15065.486444] ICMPv6: process 
`snmpd' is using deprecated sysctl (syscall) 
net.ipv6.neigh.lo.retrans_time - use net.ipv6.neigh.lo.retrans_time_ms 
instead
syslog.1:Jan  6 09:09:03 bar kernel: [15065.486444] ICMPv6: process 
`snmpd' is using deprecated sysctl (syscall) 
net.ipv6.neigh.lo.retrans_time - use net.ipv6.neigh.lo.retrans_time_ms 
instead



--
Vladislav Artemyev

Bug#849663: Pending fixes for bugs in the golang-github-boltdb-bolt package

[pkg-go-maintainers]

tag 849663 + pending
thanks

Some bugs in the golang-github-boltdb-bolt package are closed in
revision 8e938b6075967aa48d768f854731edb1636d019b in branch 'master'
by Martín Ferrari

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-boltdb-bolt.git/commit/?id=8e938b6

Commit message:

Patch a test that fails on 32-bit architectures due to the usage of a 
constnat that is too big to fit in an int. Closes: #849663

Bug#848999: pinentry-gtk2: Fails to work, appears as gpg-agent not working

[Roland Hieber]

Package: pinentry-gtk2
Version: 1.0.0-1
Followup-For: Bug #848999

I can confirm that behaviour, the pinentry-gtk2 window only flashes up shortly
and then closes, but pinenetry-ncurses and -gnome3 work fine. The last time it
worked for me was on Jan 1st 2017 with Enigmail. It also doesn't work for me
after a reboot, and I haven't changed anything related to my setup since then
(if you want to see, have a look at https://github.com/rohieb/dotfiles/tree/r2d2
;-))

Here's a session transcript:

$ sudo login
r2d2 login: rohieb
Password: 

$ echo $GPG_TTY
/dev/pts/7
$ tty
/dev/pts/7
$ gpgconf --kill gpg-agent
$ ps -Af|grep gpg-agent
rohieb   23122 21990  0 02:43 pts/700:00:00 grep --color=auto 
gpg-agent
$ echo foobar | gpg --sign

(at this point, pinentry-ncurses window pops up normally, but choosing "Cancel")

gpg: using "DD2C3FEA" as default secret key for signing
gpg: signing failed: Operation cancelled
£ÀËÌÀŸÉÑ&í®ý+ÆӼI

3Óòó¸gpg: signing failed: Operation cancelled
$ 
$ export DISPLAY=:0 XAUTHORITY=~/.Xauthority
$ echo foobar | gpg --sign

(pinentry-gtk2 window flashes up, closes directly)

gpg: using "DD2C3FEA" as default secret key for signing
gpg: signing failed: Operation cancelled
£ÀËÌÀŸÉÑ&í®ý+ÆӼI

3¥åç'%qgpg: signing failed: Operation cancelled
$ 

But maybe this is of interest, also with short window flashing as before:

$ echo GETPIN | pinentry-gtk-2
OK Pleased to meet you

** (pinentry-gtk-2:30108): CRITICAL **: could not grab keyboard: not 
viewable (3)

** (pinentry-gtk-2:30108): WARNING **: it took 4097 tries to grab the 
keyboard

** (pinentry-gtk-2:30108): WARNING **: it took 1795 tries to grab the 
pointer
ERR 83886179 Operation cancelled 
$

However, my usual workaround for those keyboard grabbing errors (changing to a
tty, then changing back to X) did not solve that issue. Neither did export
GTK_IM_MODULE="", or killing ibus-daemon, to maybe work around ibus issues.

 - Roland

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

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

Versions of packages pinentry-gtk2 depends on:
ii  libassuan0 2.4.3-2
ii  libc6  2.24-8
ii  libglib2.0-0   2.50.2-2
ii  libgpg-error0  1.25-2
ii  libgtk2.0-02.24.31-1
ii  libncursesw5   6.0+20161126-1
ii  libsecret-1-0  0.18.5-2
ii  libtinfo5  6.0+20161126-1

pinentry-gtk2 recommends no packages.

Versions of packages pinentry-gtk2 suggests:
ii  pinentry-doc  1.0.0-1

-- no debconf information

Bug#850578: selinux-basics: wrong label on /dev/pts/ptmx

[Russell Coker]

Package: selinux-basics
Version: 0.5.6
Severity: normal

selinux-basics should run restorecon on /dev/pts/ptmx and/or have a systemd
tmpfiles configuration entry for it to give it the correct context on boot.

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

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

Versions of packages selinux-basics depends on:
ii  checkpolicy  2.6-2
pn  perl:any 
ii  policycoreutils  2.6-2
pn  python3:any  
ii  selinux-utils2.6-3

Versions of packages selinux-basics recommends:
ii  policycoreutils-python-utils  2.6-2
ii  selinux-policy-default2:2.20161023.1-6
ii  setools   4.0.1-4

Versions of packages selinux-basics suggests:
pn  logcheck
pn  syslog-summary  

-- no debconf information

Bug#850560: Want `dgit nmudiff`

[Sean Whitton]

On Sun, Jan 08, 2017 at 01:12:20AM +, Ian Jackson wrote:
> Generating the nmudiff with debdiff is rather silly IMO.  It can be
> generated by git more easily.  I have a half-finished branch which
> does this.
> 
> The idea is that dgit push would do it for you.  I guess a separate
> command to send it would be fine, too.

Fair enough.  What's most convenient about nmudiff is that it drops you
into your MUA with an e-mail ready to go, including the appropriate
control: lines.  It would be best if dgit didn't need to reimplement
this.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#849619: python-networkx: agressive use of Recommends

[Afif Elghraoui]

On السبت  7 كانون الثاني 2017 15:17, Sandro Tosi wrote:

On Sat, Jan 7, 2017 at 5:34 PM, Afif Elghraoui  wrote:

I hope what I've said now convinces you



sadly you didnt



What is it that doesn't make sense to you? Is it that you don't agree 
that the current situation violates policy or that you just don't want 
to change it?


The specific case in which I discovered this problem is that installing 
pbhoney gets all of networkx's unnecessary recommends. If you do 
no-install-recommends to avoid the unnecessary recommends, you don't get 
pbhoney's legitimate recommends of pbdagcon and unnecessarily use the 
inferior built-in fallback implementation.


If I made pbdagcon a hard dependency, then you would not be able to 
install pbhoney in a situation where pbdagcon isn't available without 
making a dummy package using equivs.


What functionality of *networkx* is affected when its recommends are not 
installed? If the answer is nothing, which it seems to be, then they 
definitely don't belong in recommends.


regards
Afif

--
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name

Bug#850575: diaspora: cannot install because broken maintscript line in preinst and missing gem files

[Julian Gilbey]

On Sun, Jan 08, 2017 at 07:03:30AM +0530, Pirate Praveen wrote:
> Control: severity -1 important

> I don't think the dir_to_symlink bug warrants grave severity.

Oh, now I've got this, when trying to remove diaspora:

Performing actions...
dpkg: error processing package diaspora (--remove):
 package is in a very bad inconsistent state; you should
 reinstall it before attempting a removal
Errors were encountered while processing:
 diaspora

:-(

   Julian

Bug#850575: diaspora: cannot install because broken maintscript line in preinst and missing gem files

[Julian Gilbey]

Hi Pirate,

Thanks for the quick response!

On Sun, Jan 08, 2017 at 07:03:30AM +0530, Pirate Praveen wrote:
> Control: severity -1 important
> 
> On ഞായര്‍ 08 ജനുവരി 2017 06:49 രാവിലെ, Julian Gilbey wrote:
> > This is not the correct syntax for the dir_to_symlink command: it
> > should be
> > dir_to_symlink pathname new-target [prior-version [package]]
> > 
> > So I guess this line should read:
> > dir_to_symlink /usr/share/diaspora/config /etc/diaspora 0.5.9.1+debian3 
> > diaspora-common
> > 
> > With this change, then diaspora installs more successfully.  (Well,
> > successfully, except that it couldn't find the gem mysql2 (I've gone
> > for the mysql option.):
> 
> I don't think the dir_to_symlink bug warrants grave severity.

I made it grave, because package simply will not install: the preinst
failed; and as far as I can tell, that counts as a grave bug:

Preparing to unpack .../137-diaspora_0.6.0.0+debian-7_all.deb ...
psql: FATAL:  role "diaspora" does not exist
dpkg-maintscript-helper: error: dpkg: warning: version 'diaspora-common' has 
bad syntax: version number does not start with digit
dpkg: error processing archive 
/tmp/apt-dpkg-install-SWG1Sz/137-diaspora_0.6.0.0+debian-7_all.deb (--unpack):
 subprocess new pre-installation script returned error exit status 1
dpkg-maintscript-helper: error: dpkg: warning: version 'diaspora-common' has 
bad syntax: version number does not start with digit
dpkg: error while cleaning up:
 subprocess new post-removal script returned error exit status 1

(and I don't know why the postrm failed too).

> > Could not find gem 'mysql2 (~> 0.4.4)' in any of the gem sources listed in 
> > your
> > Gemfile or available on this machine.
> 
> Because the diaspora package currently only supports postgresql. I have
> added mysql support to diaspora-installer via diaspora-installer-mysql
> but did not get time to create diaspora-mysql.

Ah, OK thanks.  I've purged it and will start again - it will probably
be more successful this time!

Ah, no, it gave up on diaspora-common, because it's trying to connect
with debian-sys-maint to port 3306, which is not where postgresql is
connected.  And I can't find an obvious way to change it.

:-(

   Julian

Bug#850577: grub-choose-default does not starts due to python error

[alvaro]

Package: grub-choose-default
Version: 0.2-6
Severity: important

Dear Maintainer,

grub-choose-default does not starts
errors:

root@sinamaica:~# grub-choose-default
Using /boot/grub/menu.lst and /boot/grub/default
Getting entries
Getting default
Creating window, might take a second
No protocol specified
No protocol specified
Traceback (most recent call last):
  File "/usr/sbin/grub-choose-default", line 325, in 
tk_root = Tk()
  File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 1813, in __init__
self.tk = _tkinter.create(screenName, baseName, className, interactive,
wantobjects, useTk, sync, use)
_tkinter.TclError: couldn't connect to display ":0"
root@sinamaica:~#



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

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

Versions of packages grub-choose-default depends on:
ii  grub-legacy [grub]  0.97-70
ii  menu2.1.47
ii  python  2.7.9-1
ii  python-tk   2.7.8-2+b1

grub-choose-default recommends no packages.

grub-choose-default suggests no packages.

-- no debconf information

Bug#536401: meaningless errors in syslog: error caught in getattr

[Joe Pfeiffer]

Package: encfs
Version: 1.9.1-3
Followup-For: Bug #536401

The issue appears to be that encfs is logging errors when getattr is
called on a nonexistent file, instead of simply returning an error
code.  My /var/log/syslog is littered with messages of the form

Jan  7 18:26:08 snowball encfs: 2017-01-07 18:26:08,462 DEBUG [default] 
[user@unknown-host] [int encfs::withFileNode(const char*, const char*, 
fuse_file_info*, std::function)] 
[/build/encfs-VGUC5_/encfs-1.9.1/encfs/encfs.cpp:145] op: getattr error: No 
such file or directory

Reverting to 1.7.4-5 (the most recent version in my package cache,
other than the current version) makes it go away.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (700, 'testing'), (650, 'stable'), (600, 'unstable'), (550, 
'experimental'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages encfs depends on:
ii  debconf [debconf-2.0]  1.5.59
ii  fuse   2.9.7-1
ii  libc6  2.24-8
ii  libfuse2   2.9.7-1
ii  libgcc11:6.2.1-5
ii  libssl1.1  1.1.0c-2
ii  libstdc++6 6.2.1-5
ii  libtinyxml2-4  4.0.1-1
ii  mount  2.29-1

encfs recommends no packages.

encfs suggests no packages.

-- debconf-show failed

Bug#850575: diaspora: cannot install because broken maintscript line in preinst and missing gem files

[Pirate Praveen]

On ഞായര്‍ 08 ജനുവരി 2017 07:22 രാവിലെ, Julian Gilbey wrote:
> On Sun, Jan 08, 2017 at 07:03:30AM +0530, Pirate Praveen wrote:
>> Control: severity -1 important
> 
>> I don't think the dir_to_symlink bug warrants grave severity.
> 
> Oh, now I've got this, when trying to remove diaspora:
> 
> Performing actions...
> dpkg: error processing package diaspora (--remove):
>  package is in a very bad inconsistent state; you should
>  reinstall it before attempting a removal
> Errors were encountered while processing:
>  diaspora

Try reinstalling with postgres if that is an option for you. If not, we
have to first add mysql support.



signature.asc
Description: OpenPGP digital signature

Bug#850576: gdb: print mismatching build-id(s) on "warning: core file may not match specified executable file."

[Paul Wise]

Package: gdb
Version: 7.12-4
Severity: normal

When I've upgraded a library or a binary and then subsequently try to
create a backtrace from a core file created before the upgrade, I get a
warning about a mismatch between the core file and the executable but
the warning is completely annoyingly non-actionable because it doesn't
include any information about build-ids so I can't lookup the old ones
on build-id.debian.net and download the binary packages from the
snapshot.debian.org service. The warnings about libraries should also be 
printing out mismatched build-ids.

warning: core file may not match specified executable file.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages gdb depends on:
ii  libbabeltrace-ctf1  1.5.0-1
ii  libbabeltrace1  1.5.0-1
ii  libc6   2.24-8
ii  libexpat1   2.2.0-2
ii  liblzma55.2.2-1.2
ii  libncurses5 6.0+20161126-1
ii  libpython3.53.5.2-9
ii  libreadline77.0-1
ii  libtinfo5   6.0+20161126-1
ii  zlib1g  1:1.2.8.dfsg-4

Versions of packages gdb recommends:
ii  libc6-dbg [libc-dbg]  2.24-8

Versions of packages gdb suggests:
ii  gdb-doc7.12-2
ii  gdbserver  7.12-4

-- debconf-show failed

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#748936: apt doesnt understand architecture wildcards

[James Clarke]

On Mon, Feb 01, 2016 at 12:05:18AM +0100, David Kalnischkies wrote:
> On Wed, Jan 20, 2016 at 01:39:45PM +, Colin Watson wrote:
> > On Wed, Jan 20, 2016 at 12:31:52PM +0100, Balint Reczey wrote:
> > > On 06/04/2014 03:41 AM, Guillem Jover wrote:
> > > >  * Other programs could “easily” use dpkg-architecture to check for
> > > >identity or a match. (This poses problems for programs that do not
> > >
> > > I think making apt call dpkg-architecture for matching would be a good
> > > way of ensuring consistency with dpkg. Caching the results in a hash
> > > table would make matching even faster than it is currently.
> >
> > dpkg-architecture is in dpkg-dev, so not reliably usable at run-time.
>
> Also, apt is trying to remain largely independent of the low-level
> package manager, so bluntly depending on it wouldn't be good, but …
>
> … apt could survive this (for now) as these architecture specifications
> can at the moment only be encountered in
> a) build-dependencies of source packages
>(effecting via python-apt also presumably stuff like dak)
> b) the commandline like 'apt install libfoo:linux-* foo:linux-any'
>(and aptitude uses it, too, for this)
>
> So, we could do that without too much pain, while keeping a fallback
> around for cases in which we don't have dpkg-architecture around for
> whatever reason as it doesn't effect apts primary operation (but might
> effect the primary operation of other tools which would need to be
> tested first).
>
>
> I wonder through if we aren't creating the debian version of a tar bomb
> (xkcd#1168) and to illustrate that a little quiz:
>
> dpkg-architecture -ai386 -ii386 true
> dpkg-architecture -ai386 -ilinux-i386   true
> dpkg-architecture -ai386 -iany-i386 true
> dpkg-architecture -aarmhf -iarmhf   true
> dpkg-architecture -aarmhf -ilinux-armhf true
> dpkg-architecture -aarmhf -iany-armhf   false
> dpkg-architecture -aarmhf -iarm false
> dpkg-architecture -aarmhf -ilinux-arm   false
> dpkg-architecture -aarmhf -iany-arm true
>
> Now, given we want to go to -- lets see:
> dpkg-architecture -aarmhf -iany-linux-arm   true
> dpkg-architecture -aarmhf -iany-any-arm true
> dpkg-architecture -aarmhf -ignu-any-arm false
> dpkg-architecture -aarmhf -ignueabihf-any-arm   true
>
> And to cool off, think about what matches any-arm, linux-any, and if
> gnu-any is even supported and if what that matches…
>
>
> Truth be told, I would have died on 'any-armhf' already even through
> that is "obvious" as 'linux-armhf' is interpreted as a literal
> architecture, while 'any-armhf' is a pattern (just that neither dpkg nor
> the policy highlight that such a difference exists explicitly).
>
> Anyway, I somehow doubt it will be a good idea to trouble mere mortals
> with the difference between gnu and gnueabihf for matching proposes, so
> I wonder why we have to trouble them with the difference of armhf and
> arm depending on if that specification is a literal architecture or an
> architecture pattern – especially if the two are different only for some
> architectures… I would personally be more happy with any-armhf working
> (and a special case letting arm match all of the arms).
>
>
> So, I actually like how apt behaves currently as it just makes more
> sense in my head to expand armhf to gnu-linux-armhf and match it against
> gnu-any-armhf instead of gnueabihf-linux-arm and and gnueabihf-any-arm,
> but so be it – it tends to be more important to have a consistent answer
> in Debian than to keep me sane… (yeah, I know, that triplet makes
> perfect sense if you know history, Debian and arm – I just don't).
>
>
> I am therefore going to happily accept any patch flying my way
> implementing architecture wildcards differently if need be, but I am not
> going to do it myself mainly because I expect that to have fallout – not
> in apt, but in things using apt – and I don't have the energy (or the
> rights) to deal with such things efficiently.

Hi David,
I actually ran into this bug in the real world: elfutils has a
Build-Depends: gcc-multilib [any-amd64], which includes x32
(x32-gnu-linux-amd64), but apt build-dep didn't install it, so
dpkg-checkbuilddeps errored out when building. I agree some of this
seems crazy, but it's even more crazy to have apt and dpkg disagree IMO.

I have attached an initial proof-of-concept[0] patch for apt to embed the
list of architecture tuples at build-time. It's not especially pretty,
but it passes the now-modified test suite run during the build
(integration tests not yet run), which includes testing x32 and arm
behave like they do in dpkg. I also haven't actually tested that
"apt build-dep elfutils" on x32 installs 

Bug#850575: diaspora: cannot install because broken maintscript line in preinst and missing gem files

[Pirate Praveen]

Control: severity -1 important

On ഞായര്‍ 08 ജനുവരി 2017 06:49 രാവിലെ, Julian Gilbey wrote:
> Package: diaspora
> Version: 0.6.0.0+debian-7
> Severity: grave
> 
> In the debian/maintscript file, you have:
> dir_to_symlink /usr/share/diaspora/config 0.5.9.1+debian3 diaspora-common
> 
> This is not the correct syntax for the dir_to_symlink command: it
> should be
> dir_to_symlink pathname new-target [prior-version [package]]
> 
> So I guess this line should read:
> dir_to_symlink /usr/share/diaspora/config /etc/diaspora 0.5.9.1+debian3 
> diaspora-common
> 
> With this change, then diaspora installs more successfully.  (Well,
> successfully, except that it couldn't find the gem mysql2 (I've gone
> for the mysql option.):
> 

I don't think the dir_to_symlink bug warrants grave severity.

> Could not find gem 'mysql2 (~> 0.4.4)' in any of the gem sources listed in 
> your
> Gemfile or available on this machine.

Because the diaspora package currently only supports postgresql. I have
added mysql support to diaspora-installer via diaspora-installer-mysql
but did not get time to create diaspora-mysql.

> Installing ruby-mysql2 then gave the error:
> 
> export DB_NAME=diaspora_production
> RAILS_ENV=production DB=mysql ENVIRONMENT_URL=https://diaspora.d-and-j.net
> Verifying we have all required libraries...
> Resolving dependencies...
> Bundler could not find compatible versions for gem "jquery-ui-rails":
>   In Gemfile:
> jquery-ui-rails (~> 6.0)
> 
> rails_admin (~> 0.8.1) was resolved to 0.8.1, which depends on
>   jquery-ui-rails (~> 5.0)
> 
> Oh dear :-(
> 
> Any suggestions?

This is fixed in ruby-rails-admin, so just update it. If you are
interested you can try creating diaspora-mysql in the same way I did
diaspora-installer-mysql.

1. Make postgres optional dependency for diaspora (change postgresql ->
postgresql | virtual-mysql-server and dbconfig-postgres ->
dbconfig-postgres | dbconfig-mysql and ruby-pg | ruby-mysql2)
2. Create new binary package diaspora-mysql whcih depends on
dbconfig-mysql, default-mysql-server | virtual-mysql-server, ruby-mysql2
and diaspora.




signature.asc
Description: OpenPGP digital signature

Bug#850089: #850089 ITP: flask-restplus - upstream version considerations

[Carl Suster]

This is wanted for flexget, which currently pins its dependency on 
flask-restplus==0.8.6. I have opened an upstream issue to ask that this be 
updated to the newest flask-restplus version 0.9.2:


  https://github.com/Flexget/Flexget/issues/1615

This will require some changes to flexget as it was patching some internal 
methods of flask-restplus which have changed.


If upstream does not want to change the dependency soon, then I will initially 
package flask-restplus at the older version 0.8.6 until I can work out how to 
help make the change with upstream.

Bug#850505: fortune-zh: please make the build reproducible

[lumin]

Hi Boyuan,

Thank you for concerning this package. I've noticed the CI
failure several weeks ago.

According to the failure logs e.g.
https://tests.reproducible-builds.org/debian/rb-pkg/testing/i386/fortune-zh.html
the problem is caused by the difference in traversal order of findutil.

Remind that there is such a line in the Makefile:
```
 18 find chinese.d -type f -name '*.dat' -exec cat '{}' \; >> chinese
```
The resulting fortune cookie file `chinese` differs as long as the
traversal order of findutil changes.

So there is nothing harm to this package since fortune
picks data randomly from its cookie files. To fix the
reproducibility I think I should find a way to fix
the traversal order. I plan to fix this in the Stretch+1
cycle.

Bug#850575: diaspora: cannot install because broken maintscript line in preinst and missing gem files

[Julian Gilbey]

Package: diaspora
Version: 0.6.0.0+debian-7
Severity: grave

In the debian/maintscript file, you have:
dir_to_symlink /usr/share/diaspora/config 0.5.9.1+debian3 diaspora-common

This is not the correct syntax for the dir_to_symlink command: it
should be
dir_to_symlink pathname new-target [prior-version [package]]

So I guess this line should read:
dir_to_symlink /usr/share/diaspora/config /etc/diaspora 0.5.9.1+debian3 
diaspora-common

With this change, then diaspora installs more successfully.  (Well,
successfully, except that it couldn't find the gem mysql2 (I've gone
for the mysql option.):

Could not find gem 'mysql2 (~> 0.4.4)' in any of the gem sources listed in your
Gemfile or available on this machine.

Installing ruby-mysql2 then gave the error:

export DB_NAME=diaspora_production
RAILS_ENV=production DB=mysql ENVIRONMENT_URL=https://diaspora.d-and-j.net
Verifying we have all required libraries...
Resolving dependencies...
Bundler could not find compatible versions for gem "jquery-ui-rails":
  In Gemfile:
jquery-ui-rails (~> 6.0)

rails_admin (~> 0.8.1) was resolved to 0.8.1, which depends on
  jquery-ui-rails (~> 5.0)

Oh dear :-(

Any suggestions?

   Julian

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

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

-- no debconf information

Bug#850560: Want `dgit nmudiff`

[Ian Jackson]

Sean Whitton writes ("Bug#850560: Want `dgit nmudiff`"):
> Package: dgit
> Version: 2.16.2
> Severity: wishlist
> 
> You can't just invoke the excellent nmudiff tool when following the
> steps in dgit-nmu-simple(7): nmudiff requires the old source package to
> be present in the parent directory.
...
> It would be good to have a simple wrapper `dgit nmudiff` that either
> (i) downloads the .dsc from the archive and then runs nmudiff, or
> (ii) rewinds the dgit/sid branch and builds the .dsc, and then runs
> nmudiff.

Generating the nmudiff with debdiff is rather silly IMO.  It can be
generated by git more easily.  I have a half-finished branch which
does this.

The idea is that dgit push would do it for you.  I guess a separate
command to send it would be fine, too.

I have heard allegations that for `3.0 (quilt)' debdiff produces diffs
of patches-unapplied trees, in which case I need to produce that for
the nmudiff, I guess.  *sigh*

Ian.

-- 
Ian Jackson    These opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#850427: Suggestions

[Simon Howard]

One (entirely valid) criticism is that not even an error message popup
appears. It should be the case that a GUI error message is displayed if
Zenity is installed. So a simple thing to do would be to add Zenity as a
Suggests: line for the package.

If you instead go with the .desktop approach, please bear in mind that it's
not just /usr/share/games/doom you should check - there's also
/usr/local/... and ~/.local/share/games/doom.

-- 
Simon Howard
https://soulsphere.org/

Bug#534687: libssl0.9.8: lh_retrieve modifies global data, bug in valgrind or OpenSSL?

[Russell Coker]

On Saturday, 7 January 2017 10:23:56 PM AEDT Sebastian Andrzej Siewior wrote:
> I am tempted to close this. Can you still reproduce this with current
> openssl & valgrind? RSA_new_method() is no longer using the class thingy
> / lhash so your old testcase won't do. And then 1.1.0c is using
> pthread's locking functions so valgrind should know by now when a lock
> is held.

Yes close these ancient bugs.

Running valgrind from a clean slate is no more difficult than trying to 
reproduce ancient bugs.

-- 
My Main Blog http://etbe.coker.com.au/
My Documents Bloghttp://doc.coker.com.au/

Bug#848496: RFS: libopenshot/0.1.2+ds1-1 [ITP][experimental]

[Andreas Henriksson]

Hello Ghislain Vaillant,

On Sat, Dec 17, 2016 at 04:22:03PM +, Ghislain Vaillant wrote:
> Package: sponsorship-requests
> Severity: wishlist
> 
> Dear mentors,
> 
> I am looking for a sponsor for my package "libopenshot"
[...]

I looked at your package and it looks fine to me, but given you're
putting it under team maintenance (which is great!) shouldn't someone
from the team sponsor you?
They will likely also be able to review the package better then me.

A personal recommendation would be to put the so version (9) in the
filename pattern of your debian/lib*9.install file so that whenever the
soname gets bumped you'll instantly notice it while building. Ofcourse
lintian will also complain about soname not matching package name, but
that's less subtle and you can't really have too many safeguards in
place to catch potential mistakes in package ABI handling.

Would also be interesting to know what your interest in packaging this
library is. Do you have or intend to package something using this
library?

Regards,
Andreas Henriksson

Bug#849521: RFS: rutorrent/3.7-1 [ITP] -- A front-end for the rTorrent torrent client

[Andreas Henriksson]

Hello Taylor Kline,

On Tue, Dec 27, 2016 at 11:26:30PM -0500, Taylor Kline wrote:
> Package: sponsorship-requests
> Severity: wishlist
> 
> Hello fine mentors,
> 
> I am looking for a sponsor for "rutorrent"
> 
> Package name: rutorrent
> Version : 3.7-1
[...]
> 
>   /etc/ruTorrent  - server files
> 
>   /usr/share/ruTorrent  - user-set configuration files chmod'd to a+rwX
[...]

Thanks for being upfront with this, appreciated.

I've looked over your package which I think mostly looks good.

I'm not overly joyed by seeing the symlink farm in /etc pointing
to /usr/share though. This is simply wrong as the files are
not configuration files (which is why they don't live in
/etc to begin with). Whatever needs these files should IMHO
be fixed up to look for the in the correct location (so
you can drop the symlinks).

Making /usr/share/ruTorrent world-writable is the main issue though.
This will never end well. You need to think about security and
how you manage permissions somehow. This is in my opinion a
blocker for uploading your package.

Please also consider upstreaming your manpages.

Not sure but if nginx has '*-available' '*-enabled' configuration
pattern but I think it does and then maybe there's a way to
provide a snippet for '*-available' that a user can in normal
cases just enable. This should simplify for the user over having
to read up and manually configure nginx.

Regards,
Andreas Henriksson

Bug#850232: installation-guide: FTBFS randomly (ERROR: xref linking to appendix-gpl has no generated link text.)

[Samuel Thibault]

Samuel Thibault, on Sun 08 Jan 2017 01:20:06 +0100, wrote:
> > Was debian/rules and the various Makefiles following Policy 4.6 before
> > the fix you applied? (i.e. errors must be trapped so that the build stops)
> 
> ? The error is trapped, yes.  As I said po2xml just doesn't print any
> useful error message.

Ah, sorry, no, it seems the error is not trapped indeed, I don't
immediately see at which level exactly.

Samuel

Bug#850574: mesa: cursor flickers when using software cursor

[Christian Weinz]

Source: mesa
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear Maintainer,

I enabled software cursor to workaround the issue of the unaffected
cursor when using redshift. For details see [0]

When I move the cursor in the gnome session near the top panel the
cursor start flickering. When moving the cursor away the flickering
stops.

[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791758


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

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

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEELoVpkSZn7eKnq6ocybioqkLpKa4FAlhxhsoTHGNocmlzdGlh
bkBtYWRlei5kZQAKCRDJuKiqQukprs3/EACDoLhc9lQdwUnCW35YXu94vU3sxoD5
ArkrRdMb6vrKUi17oJM32K5abWlC2b0uGXxclVeLlwgvncyoqPZq4rFd3tR/MYMH
h26qdJukTvKDL91DBdcCs8MCeXqAe6MHcc+88ISbBTY/DKDXuzzp0hn7242GIZSK
9fd5uvHbaMIyD8Oyf6bY5p8dEECfMCxRwOuUoJfQWORhwN6itU0ZchtO0SBtKwiW
4dR84wbUrQhsuvwadPlIQ6UqtWyvOaDmQP/BigZB1kcz2h/lt/1MM3dw9n1/aJWR
gQNvyHpbqI0LVTWFJpRpbez+2WGe8KU23UXfpR+OblQH+0lrplbK6LoyJR44cPf6
zjdW8hinPIwUUKKSBPjRqcv/MbibwjoWwvh13xzUchv+tAj4GMQLc1RxwB7H3vyt
XoLNhV2arPUmPGW0HA9b9i7cQAMSjJ1yo8nY6Ga1NaM94P+2Vyyuq5kyBbeuga4G
bPkqczj3Gwl4napQQNBocKu2X1lUVHgTWSeMZ2j9gOVEdlxL2AgTZ++921cOdzTL
Jw0f4c2E/8iiMp5X0gnNQiQZExqvMJgpT9AS33aCboyH936veJkXcfe61lhHUle7
NcGdZSTS1mKiu2fdgNbPPbhodI70ApT6qPZ3LlZRG0ykgcnLJEeDgCPWqSPWWFUd
sN04rTBRPiXpUg==
=IN/P
-END PGP SIGNATURE-

Bug#850232: installation-guide: FTBFS randomly (ERROR: xref linking to appendix-gpl has no generated link text.)

[Samuel Thibault]

Samuel Thibault, on Sun 08 Jan 2017 01:23:53 +0100, wrote:
> Samuel Thibault, on Sun 08 Jan 2017 01:20:06 +0100, wrote:
> > > Was debian/rules and the various Makefiles following Policy 4.6 before
> > > the fix you applied? (i.e. errors must be trapped so that the build stops)
> > 
> > ? The error is trapped, yes.  As I said po2xml just doesn't print any
> > useful error message.
> 
> Ah, sorry, no, it seems the error is not trapped indeed, I don't
> immediately see at which level exactly.

Ok, seen where, an extra grep command which gets in the way, should be
fixed too now.

Samuel

Bug#850232: installation-guide: FTBFS randomly (ERROR: xref linking to appendix-gpl has no generated link text.)

[Samuel Thibault]

Santiago Vila, on Sun 08 Jan 2017 01:11:41 +0100, wrote:
> On Sun, Jan 08, 2017 at 12:55:38AM +0100, Samuel Thibault wrote:
> > Santiago Vila, on Sat 07 Jan 2017 23:37:03 +0100, wrote:
> > > On Sat, Jan 07, 2017 at 11:20:35PM +0100, Samuel Thibault wrote:
> > > 
> > > > Could you also post build logs which are successful?
> > > 
> > > Ok, all the build logs I have, same place as before:
> > > 
> > > https://people.debian.org/~sanvila/build-logs/installation-guide/
> > 
> > Ok, thanks!
> > 
> > What was in common in failed builds was that it started creating xml
> > files from gpl.xml (depending in which order the filesystem laid
> > files).  I could then reproduce the issue easily by starting with it.
> > What happens is that for 'da' there is no translation, and in that
> > case msgattrib does *not* create the file, and thus po2xml just fails
> > without an explicit error message.  I fixed it by passing --force-po to
> > msgattrib to always create a file, even if without any translation.
> 
> Reminds me of this bug:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841096#47
> 
> Was debian/rules and the various Makefiles following Policy 4.6 before
> the fix you applied? (i.e. errors must be trapped so that the build stops)

? The error is trapped, yes.  As I said po2xml just doesn't print any
useful error message.

Samuel

Bug#749031: transmission-gtk: Tray icon in mate-panel and gnome-shell has excessive spacing

[Sandro Tosi]

On Fri, Apr 3, 2015 at 1:05 PM, Eric Pruitt  wrote:
> I don't use Sid, and I'm not particularly interested in mixing stable
> and unstable packages just to test this. I intend to update to Jessie
> when it's released later this month, and I will see if the problem is
> still reproducible at that time.

any update on this?

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#808564: RFP: searx -- privacy-respecting, hackable metasearch engine

[W. Martin Borgert]

On 2017-01-08 00:48, Johannes Schauer wrote:
> I'm not in a rush to get the package into unstable.
>
> If you want to invest the time to port my packaging to the python2 0.10 
> release
> then feel free to do so and upload to NEW. :)

I'll think about it! Maybe when stretch is in deep freeze :~)

Bug#850232: installation-guide: FTBFS randomly (ERROR: xref linking to appendix-gpl has no generated link text.)

[Santiago Vila]

On Sun, Jan 08, 2017 at 12:55:38AM +0100, Samuel Thibault wrote:
> Control: tags -1 + pending
> 
> Hello,
> 
> Santiago Vila, on Sat 07 Jan 2017 23:37:03 +0100, wrote:
> > On Sat, Jan 07, 2017 at 11:20:35PM +0100, Samuel Thibault wrote:
> > 
> > > Could you also post build logs which are successful?
> > 
> > Ok, all the build logs I have, same place as before:
> > 
> > https://people.debian.org/~sanvila/build-logs/installation-guide/
> 
> Ok, thanks!
> 
> What was in common in failed builds was that it started creating xml
> files from gpl.xml (depending in which order the filesystem laid
> files).  I could then reproduce the issue easily by starting with it.
> What happens is that for 'da' there is no translation, and in that
> case msgattrib does *not* create the file, and thus po2xml just fails
> without an explicit error message.  I fixed it by passing --force-po to
> msgattrib to always create a file, even if without any translation.

Reminds me of this bug:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841096#47

Was debian/rules and the various Makefiles following Policy 4.6 before
the fix you applied? (i.e. errors must be trapped so that the build stops)

Thanks.

Bug#850232: installation-guide: FTBFS randomly (ERROR: xref linking to appendix-gpl has no generated link text.)

[Samuel Thibault]

Control: tags -1 + pending

Hello,

Santiago Vila, on Sat 07 Jan 2017 23:37:03 +0100, wrote:
> On Sat, Jan 07, 2017 at 11:20:35PM +0100, Samuel Thibault wrote:
> 
> > Could you also post build logs which are successful?
> 
> Ok, all the build logs I have, same place as before:
> 
> https://people.debian.org/~sanvila/build-logs/installation-guide/

Ok, thanks!

What was in common in failed builds was that it started creating xml
files from gpl.xml (depending in which order the filesystem laid
files).  I could then reproduce the issue easily by starting with it.
What happens is that for 'da' there is no translation, and in that
case msgattrib does *not* create the file, and thus po2xml just fails
without an explicit error message.  I fixed it by passing --force-po to
msgattrib to always create a file, even if without any translation.

> As usual, if you find a fix please consider uploading in source-only
> form (dpkg-buildpackage -S), so that we always have official build
> logs here:
> 
> https://buildd.debian.org/status/package.php?p=installation-guide

Well, we usually upload installation-guide when we need it for a d-i
release, so I'm not sure we can really wait for a buildd with unknown
processing power and busyness to build it.

Samuel

Bug#846661: Processed: light-locker: screen remains black after unlock

[Michael Biebl]

Am 08.01.2017 um 00:47 schrieb Gedalya:
> On 01/07/2017 06:43 PM, Michael Biebl wrote:
>>> As stated in the last few messages in this bug report, the problem appears 
>>> exclusively when not using systemd as init.
>>> At Yves-Alexis's request I confirmed the symptoms do not occur when booting 
>>> with systemd as init.
>>>
>>> This is the n'th recurrence of, basically, the same problem, just the added 
>>> issue with light-locker is new.
>>> In previous times as well, things did work when using systemd as init.
>> Since the reassign message did not include this information, this was
>> not clear.
>>
>> Thanks for confirming this works with systemd as PID 1.
>> So this seems to be a problem in the SysV - systemd shim layer, i.e.
>> systemd-shim.
>> Reassigning accordingly.
>>
>> Word of warning: systemd-shim is orphaned and currently has no
>> maintainer. So my recommendation would be to stick with systemd-sysv.
>>
> 
> On the other hand, this did work well in all versions of systemd prior to 
> 232-1, confirmed specifically with 231-10.
> Would there be a way, and particularly due to systemd-shim being orphaned, to 
> identify the problem and possibly fix it with systemd?

You are asking the wrong audience here, you should ask people using
sysvinit as PID 1.


-- 
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#849957: llmnrd: tidy up and improve init script

[Andreas Henriksson]

On Sat, Jan 07, 2017 at 09:16:58PM +0100, Pali Rohár wrote:
> That sounds strange as calling init script is standard way how to start 
> or stop some service in Linux and Unix world for a very long time...

No, calling init scripts directly brings only pain given that you'll
leak your environment into the daemon.

Consider an admin loggin in on a server using his personal account
where he has for example the locale set up to his preferred
language eg. greek, he then continues to su to gain root, then
he invokes /etc/init.d/foo restart.
This results in system logs being filled up with greek messages
which the other admins while investigating the system logs
can't read/understand.

To make an attempt at preventing atleast some of the environment
leakage the 'service' command was born a decade or two ago.
This is the proper interface for a local sysadmin to use
to manage services.

(Also, people want to *always* use 'su - foo' rather than just 'su foo'
to get a new environment for the new user, rather than inheriting the
previous environment.)

On the debian side we have Debian Policy 9.3.3 explicitly forbidding
directly invoking init scripts. That's what the abstraction layer
invoke-rc.d is for (which is basically the service command extended
with policy-rc.d support).

No packages in debian directly invokes init scripts. Users have
had a decade or two to learn about the service command (which
in turn runs systemctl on a systemd based system). Given we've
already given decades as a grace period for users to catch up,
it'll soon be time to turn up the heat on getting users to
do it right

Under systemd, you really want to use systemctl (which service does
under the hood) to manage services. Anything started directly
and forks processes will leave those processes outside the
correct cgroup and then systemd can't track and kill them properly.
Having systemd start things via systemctl will also guarantee
that the services are started under a clean environment that
is the same every time. No environment leakage or variable
preconditions.


> 
> Anyway, I uploaded new llmnrd version 0.2.1-2 to mentors which should 
> address this bug: https://mentors.debian.net/package/llmnrd
> 
> I added also "try-restart" action, I believe logic is correct.

Looks good, uploaded.

Regards,
Andreas Henriksson

Bug#808564: RFP: searx -- privacy-respecting, hackable metasearch engine

[Johannes Schauer]

Hi,

Quoting W. Martin Borgert (2017-01-08 00:42:22)
> On 2017-01-07 18:53, Johannes Schauer wrote:
> > To not introduce yet another python2-only package into Debian I packaged 
> > their
> > Python3 branch. I only intend to upload the package once upstream makes a
> > release that has this branch merged.
> I suggest, to upload searx 0.10 with Python 2 to unstable and just follow
> upstream when they move to Python 3. Having searx early in the release cycle
> will help getting a well-tested package for buster. This involves only a
> short delay in NEW for the new binary package, when the change is done.

I'm not in a rush to get the package into unstable.

If you want to invest the time to port my packaging to the python2 0.10 release
then feel free to do so and upload to NEW. :)

> > As the blocking bugs indicate, some packages are missing to run the unit
> > tests of the source package. Because the packages are still missing, I
> > disabled the unit tests for now.
> 
> I started with some of the stuff (robotframework, robotsuite),
> but got stuck over some JS library issues. At some point, I
> will resume packaging this.
> 
> Btw. I get some (non-fatal) exceptions:
> jinja2.exceptions.UndefinedError: 'str object' has no attribute 'decode'
> 
> But this might be because I run searx on stable with only the
> absolutely necessary packages from testing (babel stuff). Not a
> supported configuration, of course :~)

It might also be because the Python3 conversion isn't completed yet. There are
still some remaining issues which is why the py3 branch isn't merged into
master yet.

Thanks!

cheers, josch


signature.asc
Description: signature

Bug#846661: Processed: light-locker: screen remains black after unlock

[Gedalya]

On 01/07/2017 06:47 PM, Gedalya wrote:
> On the other hand, this did work well in all versions of systemd prior to 
> 232-1
Misspoke: it came and went several times.

Bug#846661: Processed: light-locker: screen remains black after unlock

[Gedalya]

On 01/07/2017 06:43 PM, Michael Biebl wrote:
>> As stated in the last few messages in this bug report, the problem appears 
>> exclusively when not using systemd as init.
>> At Yves-Alexis's request I confirmed the symptoms do not occur when booting 
>> with systemd as init.
>>
>> This is the n'th recurrence of, basically, the same problem, just the added 
>> issue with light-locker is new.
>> In previous times as well, things did work when using systemd as init.
> Since the reassign message did not include this information, this was
> not clear.
>
> Thanks for confirming this works with systemd as PID 1.
> So this seems to be a problem in the SysV - systemd shim layer, i.e.
> systemd-shim.
> Reassigning accordingly.
>
> Word of warning: systemd-shim is orphaned and currently has no
> maintainer. So my recommendation would be to stick with systemd-sysv.
>

On the other hand, this did work well in all versions of systemd prior to 
232-1, confirmed specifically with 231-10.
Would there be a way, and particularly due to systemd-shim being orphaned, to 
identify the problem and possibly fix it with systemd?
It should go without saying that people who are avoiding systemd (well, trying 
hard to avoid it, but not being allowed to), are more than aware of systemd's 
existence, and are consciously choosing to avoid it.

Bug#823695: transmission: gui wrongly positioned buttons xfce

[Sandro Tosi]

control: tags -1 +moreinfo

On Sat, May 7, 2016 at 3:19 PM, Karagkiaouris Diamantis
 wrote:
> When i open transmission there are no frames in buttons in menu and on 
> navigation menu. Also when i click on the place that a checkbox is supposed 
> to be (what i remember from previous versions), the option vanishes. It is 
> reproducable anytime.

is this still happening with 2.92?

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#808564: RFP: searx -- privacy-respecting, hackable metasearch engine

[W. Martin Borgert]

Many thanks, this is wonderful! It took me only some minutes
with your package and the README.Debian to get searx running.

On 2017-01-07 18:53, Johannes Schauer wrote:
> To not introduce yet another python2-only package into Debian I packaged their
> Python3 branch. I only intend to upload the package once upstream makes a
> release that has this branch merged.

I suggest, to upload searx 0.10 with Python 2 to unstable and
just follow upstream when they move to Python 3. Having searx
early in the release cycle will help getting a well-tested
package for buster. This involves only a short delay in NEW
for the new binary package, when the change is done.

> As the blocking bugs indicate, some packages are missing to run the unit tests
> of the source package. Because the packages are still missing, I disabled the
> unit tests for now.

I started with some of the stuff (robotframework, robotsuite),
but got stuck over some JS library issues. At some point, I
will resume packaging this.

Btw. I get some (non-fatal) exceptions:
jinja2.exceptions.UndefinedError: 'str object' has no attribute 'decode'

But this might be because I run searx on stable with only the
absolutely necessary packages from testing (babel stuff). Not a
supported configuration, of course :~)

Bug#846661: Processed: light-locker: screen remains black after unlock

[Michael Biebl]

Control: reassign -1 systemd-shim

Am 08.01.2017 um 00:22 schrieb Gedalya:
> On 01/07/2017 06:18 PM, Michael Biebl wrote:
>> Control: tags -1  + moreinfo
>>
>> Can you reproduce the reproduce the problem with systemd as PID 1?
>>
>> loginctl unlock-session works fine here (using systemd-sysv).
>>
>> Michael
> 
> As stated in the last few messages in this bug report, the problem appears 
> exclusively when not using systemd as init.
> At Yves-Alexis's request I confirmed the symptoms do not occur when booting 
> with systemd as init.
> 
> This is the n'th recurrence of, basically, the same problem, just the added 
> issue with light-locker is new.
> In previous times as well, things did work when using systemd as init.

Since the reassign message did not include this information, this was
not clear.

Thanks for confirming this works with systemd as PID 1.
So this seems to be a problem in the SysV - systemd shim layer, i.e.
systemd-shim.
Reassigning accordingly.

Word of warning: systemd-shim is orphaned and currently has no
maintainer. So my recommendation would be to stick with systemd-sysv.

Regards,
Michael

-- 
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#794957: transmission: Upgrading transmission made it the default program for bittorrent files

[Sandro Tosi]

control: tags -1 +moreinfo

On Sat, Aug 8, 2015 at 1:28 PM, Anders Andersson  wrote:
> Since there has been no changes to the package 'deluge' or to the
> meta-package 'gnome' (which depends on transmission) for a long time, my guess
> is that the simple act of upgrading the package transmission caused it to
> override whatever was the previous default application.

Both deluge-gtk and transmission-gtk install a MIME type file for
application/x-bittorrent:

https://anonscm.debian.org/cgit/collab-maint/deluge.git/tree/debian/deluge-gtk.mime
https://anonscm.debian.org/cgit/collab-maint/transmission.git/tree/debian/transmission-gtk.mime

i think that's a  correct behavior for both of them, but if the last
installed takes all, the problem is probably bigger than transmission
and it is in how we handle mime types maybe

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#846335: cross-toolchain-base: FTBFS in testing (2 out of 2 hunks FAILED)

[Santiago Vila]

On Sat, 7 Jan 2017, Johannes Schauer wrote:

> The Built-Using field is for binary packages to indicate that they incorporate
> code from other source packages than the source package that the build from.

I see that's the case indeed, but in an indirect way.

The package cross-toolchain-base-ports, for example, has this in Build-Depends:

  binutils-source (>= 2.27.51.20161101-1~),
  glibc-source (>= 2.24-5~),
  gcc-6-source (>= 6.2.0-11~),
  linux-source (>= 4.8),

So they incorporate code from other source packages, but only as far
as they are distribured in "foo-source"-like packages. This is to be
able to build-depend on them.

So, the normal build-depends mechanism is used to decide which version
need to be installed for the build.

> If the package really fails to build from source because you are not 
> installing
> the right package versions or not the right packages, then these are missing
> from the Build-Depends-* fields.

That's basically what I thought.

Matthias, I have built these two packages in stretch again.

Now they build ok so I did a diff between old (failed) and new
build logs and found this:


-if dpkg --compare-versions 6.2.0-13 le 6.2.1-4; then \
+if dpkg --compare-versions 6.2.1-5 le 6.2.1-4; then \
   cd gcc; \
   patch -p1 < ../debian/patches/gcc/gcc-stage1.diff; \
 fi
-patching file debian/rules.patch
-Hunk #1 FAILED at 151.
-Hunk #2 FAILED at 187.
-2 out of 2 hunks FAILED -- saving rejects to file debian/rules.patch.rej
-debian/rules:213: recipe for target 'stamp-dir/init-gcc' failed
-make: *** [stamp-dir/init-gcc] Error 1
-dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


> The Built-Using header is for binary packages to assure copyright compliance 
> in
> the archive. They are not indicators of the binary packages required to build 
> a
> source package.

Again as I thought: Neither I or sbuild is supposed to look at the
Built-Using field in the binary packages when trying to rebuild
packages for testing purposes.

Instead, I suggest Matthias that he just updates the (already versioned)
build-depends on the *-source packages in the control file.

Then we could avoid filddling with conditional patching in
debian/rules, which we all see that it's prone to error.

If you are worried of this package propagating to testing before its
build-dependencies, I consider that to be a bug in britney and do not
usually report it as a bug in the package itself.

An error of type "build-dependencies not met" (i.e. "wait-dep" in
wannabuild speak) is always better than a tried-then-failed build.


Thanks a lot.

Bug#849845: [pkg-gnupg-maint] Bug#849845: Bug#849845: dirmngr: Can't resolve keyserver hostname anymore

[shirish शिरीष]

in-line :-

On 07/01/2017, Daniel Kahn Gillmor  wrote:
> On Fri 2017-01-06 17:49:04 -0500, shirish शिरीष wrote:
>> But issue is still continuing -
>>
>> ─[$] gpg --keyserver pgp.mit.edu --recv-keys DAD95197
>>
>> [4:22:18]
>> gpg: keyserver receive failed: No keyserver available
>>
>> I tried multiple times with various other keys but didn't succeed.
>
> Have you restarted dirmngr since the upgrade?

how do I restart it ?

dirmngr.service isn't even found :(

─[$] dpkg -L dirmngr | grep dirmngr.service
/usr/lib/systemd/user/dirmngr.service

─[$] ll -h /usr/lib/systemd/user/dirmngr.service

-rw-r--r-- 1 root root 250 2016-11-18 19:53
/usr/lib/systemd/user/dirmngr.service

and trying to see if it works got me nothing :(


[$] sudo systemctl status dirmngr.service

[sudo] password for shirish:
Unit dirmngr.service could not be found.


I did do a cat and saw this -

─[$] cat /usr/lib/systemd/user/dirmngr.service

[4:57:44]
[Unit]
Description=GnuPG network certificate management daemon
Documentation=man:dirmngr(8)
Requires=dirmngr.socket
After=dirmngr.socket
## This is a socket-activated service:
RefuseManualStart=true

[Service]
ExecStart=/usr/bin/dirmngr --supervised

Can you help ?


>are you using tor?  if
> you're using tor, have you removed all the ipv6 entries ?

I actually have this in grub for few years now

─[$] cat /etc/default/grub | grep ipv6

GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1"

Maybe this goves a clue, dunno

> what does:
>
>gpg-connect-agent --dirmngr 'keyserver --hosttable' /bye
>
> show you?
>
>  --dkg
>
└─[$] gpg-connect-agent --dirmngr 'keyserver --hosttable' /bye

gpg-connect-agent: no running Dirmngr - starting '/usr/bin/dirmngr'
gpg-connect-agent: waiting for the dirmngr to come up ... (5s)
gpg-connect-agent: connection to the dirmngr established
S # hosttable (idx, ipv6, ipv4, dead, name, time):


Look forward to guidance.
-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#794519: localhost:9091 inaccessable after a reboot

[Sandro Tosi]

control: tags -1 +moreinfo

On Mon, Aug 3, 2015 at 9:16 PM, James Dietrich  wrote:
> After rebooting my machine, I can see that systemd is starting
> transmission-daemon:
...
> However, the web interface is not set up, and so any attempt to visit
> localhost:9091 in my web browser fails.

is this still happening with 2.92?

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#846661: Processed: light-locker: screen remains black after unlock

[Gedalya]

On 01/07/2017 06:18 PM, Michael Biebl wrote:
> Control: tags -1  + moreinfo
>
> Can you reproduce the reproduce the problem with systemd as PID 1?
>
> loginctl unlock-session works fine here (using systemd-sysv).
>
> Michael

As stated in the last few messages in this bug report, the problem appears 
exclusively when not using systemd as init.
At Yves-Alexis's request I confirmed the symptoms do not occur when booting 
with systemd as init.

This is the n'th recurrence of, basically, the same problem, just the added 
issue with light-locker is new.
In previous times as well, things did work when using systemd as init.

Thanks,

Gedalya

Bug#850573: postfix: [INTL:fr] French debconf translation

[jean-pierre giraud]

Package: postfix
Severity: wishlist
Tags: patch l10n

Hi!

Please find attached the french translation, proofread
by the debian-l10n-french mailing list contributors.

This file should be put as debian/po/fr.po in your package build tree.

Kind Regards

jipege


fr.po.gz
Description: application/gzip

Bug#848016: brltty-espeak: very monotonous speech and noticable delays in speech output

[Samuel Thibault]

Hello,

Eric Scheibler, on Mon 02 Jan 2017 22:16:36 +0100, wrote:
> Samuel Thibault  schrieb am 02.01.2017, 20:56 +0100:
> >Can you please test with the latest version libespeak-ng, 1.49.0+dfsg-3?
> 
> Same problem.

Could you try the latest version, 1.49.0+dfsg-4?

Thanks
Samuel

Bug#849619: python-networkx: agressive use of Recommends

[Sandro Tosi]

On Sat, Jan 7, 2017 at 5:34 PM, Afif Elghraoui  wrote:
> I hope what I've said now convinces you


sadly you didnt

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#846661: Processed: light-locker: screen remains black after unlock

[Michael Biebl]

Control: tags -1  + moreinfo

Can you reproduce the reproduce the problem with systemd as PID 1?

loginctl unlock-session works fine here (using systemd-sysv).

Michael


-- 
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#850572: linux-image-4.8.0-2-amd64: Performance regression in 4.8

[Ross Vandegrift]

Package: src:linux
Version: 4.8.11-1
Severity: normal
Tags: upstream

Hello,

I recently upgraded to linux-image-4.8.0-2-amd64 and hit a performance
regression in some steam games.  On 4.7.0-1 the RimWorld title screen
renders at 60fps.  On 4.8.0-2, it renders at 30fps with noticable input
latency.  So far I haven't found a microbenchmark that demostrates the
issue.

The problem appears in 4.8.0-rc1 and is still present in 4.10-rc2.  I
tried to bisect v4.7.8..v4.8.0-rc1, but after a few iterations the
kernels lock hard very quickly after bootup.

The only clue I have: my laptop has Intel and nvidia GPUs.  The problem
affects both.  The above tests were performed on Intel.

Let me know if I can provide any additional info,
Ross

-- Package-specific info:
** Version:
Linux version 4.8.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 5.4.1 
20161019 (Debian 5.4.1-3) ) #1 SMP Debian 4.8.11-1 (2016-12-02)

** Command line:
BOOT_IMAGE=/vmlinuz-4.8.0-2-amd64 root=/dev/mapper/vg0-root ro quiet splash

** Tainted: OE (12288)
 * Out-of-tree module has been loaded.
 * Unsigned module has been loaded.

** Kernel log:
[9.696762] proc_thermal :00:04.0: enabling device ( -> 0002)
[9.696764] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[9.699958] mei_me :00:16.0: enabling device ( -> 0002)
[9.704705] sd 1:0:0:0: Attached scsi generic sg0 type 0
[9.707696] iTCO_vendor_support: vendor-support=0
[9.708592] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[9.708704] iTCO_wdt: Found a Intel PCH TCO device (Version=4, 
TCOBASE=0x0400)
[9.708806] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[9.713612] EFI Variables Facility v0.08 2004-May-17
[9.716602] input: PC Speaker as /devices/platform/pcspkr/input/input9
[9.724713] usbcore: registered new interface driver brcmfmac
[9.724761] brcmfmac :02:00.0: enabling device ( -> 0002)
[9.728491] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
[9.728651] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[9.745245] pstore: using zlib compression
[9.756181] pstore: Registered efi as persistent store backend
[9.759166] intel_rapl: Found RAPL domain package
[9.759168] intel_rapl: Found RAPL domain core
[9.759169] intel_rapl: Found RAPL domain uncore
[9.759171] intel_rapl: Found RAPL domain dram
[9.765329] media: Linux media interface: v0.10
[9.765766] dcdbas dcdbas: Dell Systems Management Base Driver (version 
5.6.0-3.2)
[9.768053] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3266: 
line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
[9.768055] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[9.768056] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
[9.768057] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[9.768058] snd_hda_codec_realtek hdaudioC0D0:inputs:
[9.768059] snd_hda_codec_realtek hdaudioC0D0:  Headset Mic=0x18
[9.768060] snd_hda_codec_realtek hdaudioC0D0:  Headphone Mic=0x1a
[9.768061] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12
[9.770572] Linux video capture interface: v2.00
[9.820095] input: HDA Intel PCH Headphone Mic as 
/devices/pci:00/:00:1f.3/sound/card0/input10
[9.820134] input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1f.3/sound/card0/input11
[9.820167] input: HDA Intel PCH HDMI/DP,pcm=7 as 
/devices/pci:00/:00:1f.3/sound/card0/input12
[9.820202] input: HDA Intel PCH HDMI/DP,pcm=8 as 
/devices/pci:00/:00:1f.3/sound/card0/input13
[9.831114] Adding 7811068k swap on /dev/mapper/vg0-swap.  Priority:-1 
extents:1 across:7811068k SSFS
[9.837381] brcmfmac :02:00.0: firmware: direct-loading firmware 
brcm/brcmfmac43602-pcie.bin
[9.837392] brcmfmac :02:00.0: firmware: failed to load 
brcm/brcmfmac43602-pcie.txt (-2)
[9.837395] brcmfmac :02:00.0: Direct firmware load for 
brcm/brcmfmac43602-pcie.txt failed with error -2
[9.842562] usbcore: registered new interface driver btusb
[9.852375] Bluetooth: hci0: BCM: chip id 102
[9.868231] Bluetooth: hci0: BCM20703A1
[9.869234] Bluetooth: hci0: BCM (001.001.005) build 
[9.869721] bluetooth hci0: firmware: direct-loading firmware 
brcm/BCM-0a5c-6410.hcd
[9.934230] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD (1bcf:28be)
[9.941813] uvcvideo 1-12:1.0: Entity type for entity Extension 4 was not 
initialized!
[9.941815] uvcvideo 1-12:1.0: Entity type for entity Extension 3 was not 
initialized!
[9.941816] uvcvideo 1-12:1.0: Entity type for entity Processing 2 was not 
initialized!
[9.941817] uvcvideo 1-12:1.0: Entity type for entity Camera 1 was not 
initialized!
[9.941976] input: Integrated_Webcam_HD as 
/devices/pci:00/:00:14.0/usb1/1-12/1-12:1.0/input/input14
[9.942044] 

Bug#846661: light-locker: screen remains black after unlock

[Gedalya]

reassign 846661 systemd 232-1
thanks

Bug#850562: passwordsafe: Package 1.00 in jessie-backports

[Bill Blough]

Hi Sergei,
`
Since you were nice enough to backport the version of passwordsafe
that's currently in jessie-backports, I figured I would reach out to you
directly before trying alternative methods.

On Sat, Jan 07, 2017 at 11:30:31AM -0800, Bill Wohler wrote:
> Package: passwordsafe
> Version: 0.98.1+dfsg-3~bpo8+1
> Severity: normal
> 
> I see version 1.00+dfsg-1 has been packaged on stretch. Would it be
> possible to package this in jessie-backports as well?

Would you also be willing to backport the version that's in stretch in
order to satisfy the above user request?  Or if you'd prefer, I can
prepare the backport package if you would be willing to sponsor/upload it.

My DM applicaiton is still pending approval, but in the future I hope to be
able to handle these requests myself.

Best regards,
Bill

Bug#850433: fixing nonexistant version

[Chris Knadle]

notfound 850433 1.2.18
found 850433 1.2.17
stop

In case you're not aware: new packages cannot be uploaded to Stable,
i.e. Jessie.  Stable essentially gets release-critical bugfixes only to
the packged version that's in the release.

A mumble_1.2.17-1~bpo8+1 backport for Jessie is in the "backports-NEW"
queue which was uploaded on Jan 2nd:

   https://ftp-master.debian.org/backports-new.html

Mumble upstream 1.2.18 has been available for 3 weeks.  Bugs for
backports should be reported to the backports mailing list @
debian-backpo...@lists.debian.org.

   https://lists.debian.org/debian-backports/

The mumble backport includes a Bugs: header to point bug reports to the
backports mailing list when using the 'reportbug' program, which is the
recommended way to file bug reports for Debian.

Despite this bug being opened for a backport, I think I'll leave it open
for the version in unstable and close it when 1.2.18-1 is uploaded to
Unstable.

   -- Chris

Chris Knadle
chris.kna...@coredump.us

Bug#849761: aptitude: new russian translation

[Manuel A. Fernandez Montecelo]

2017-01-03 21:45 Lev Lamberov:

Hi Manuel,

31.12.2016 22:16, Manuel A. Fernandez Montecelo пишет:

2016-12-31 17:43 GMT+01:00 Lev Lamberov :

Manuel, I'll proofread the translation next week or something and will
send it through the bug report.


I commited it already (thanks again, Ulyanich), since at first glance
it was adding new strings and fixing format for things that changed...
but I'll gladly accept revised versions... and there shouldn't be many
changes before the freeze/release, so now it's a good time for this.


Please, find the patch attached. I've proofread all the translation
(including what was not changed by Michael) and updated it.


Thanks, update applied.

--
Manuel A. Fernandez Montecelo 

Bug#850232: installation-guide: FTBFS randomly (ERROR: xref linking to appendix-gpl has no generated link text.)

[Santiago Vila]

On Sat, Jan 07, 2017 at 11:20:35PM +0100, Samuel Thibault wrote:

> Could you also post build logs which are successful?

Ok, all the build logs I have, same place as before:

https://people.debian.org/~sanvila/build-logs/installation-guide/

As usual, if you find a fix please consider uploading in source-only
form (dpkg-buildpackage -S), so that we always have official build
logs here:

https://buildd.debian.org/status/package.php?p=installation-guide

Thanks.

Bug#849619: python-networkx: agressive use of Recommends

[Afif Elghraoui]

On الجمعـة  6 كانون الثاني 2017 12:34, Sandro Tosi wrote:

On Wed, Dec 28, 2016 at 10:28 PM, Afif Elghraoui  wrote:

There are many valid use cases of networkx on headless systems or where
visualization is done by other, separate programs, possibly written in
different languages where these currently recommended packages are not needed.


i consider the ability to generate graphical visualization of a graph
an important feature (not a core one), that's why those packages (all
required for visualization) are in Recommends.  If you dont like them,
you can apt remove them or dont install recommends at all,but you are
not providing strong indication we should change this behavior


I think it's enough to reiterate the policy for Recommends, especially 
the part that says "This declares a strong, but not absolute, 
*dependency*", which is the reason why apt installs them by default. The 
things you have in Recommends now are not any kind of dependency at all. 
People who like to always get useful extras can install suggests.


To give an example of an appropriate Recommends situation, I have a 
package, pbhoney that uses pbdagcon, but has a fallback implementation 
in case pbdagcon is not available. I therefore put pbdagcon as a 
Recommends. pbhoney's fallback implementation should only be used if 
pbdagcon isn't available, like on some architectures. If people have to 
keep disabling Recommends to avoid installing things that should be 
Suggests, they will have a somewhat crippled installation here.



(which
has been there since ~10 years).



I don't think this makes it more correct. The misuse of Recommends has 
been discussed before. See 
https://lists.debian.org/debian-devel/2016/04/msg00159.html and the rest 
of the thread.


I hope what I've said now convinces you. Thanks for working on these 
packages in any case.


regards
Afif

--
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name

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

[Manuel A. Fernandez Montecelo]

2017-01-01 15:12 GMT+01:00 Andreas Neudecker :
> Hi Manuel,
>
> I did not find this setting
>
>> Do you have GzipIndexes indexes enabled in apt/aptitude config?
>
> anywhere. root's ~/.aptitude/config is:
>
> 8<
> aptitude "";
> aptitude::Keep-Unused-Pattern "";
> aptitude::Delete-Unused-Pattern "";
> aptitude::Delete-Unused "false";
> aptitude::Auto-Upgrade "true";
> aptitude::UI "";
> aptitude::UI::Pause-After-Download "OnlyIfError";
> aptitude::UI::InfoAreaTabs "false";
> 8<
>
> I also checked in /etc/apt/apt.conf.d/* and a grep on GzipIndexes yielded 
> nothing.
>
> Where else should I look?

What you cited is everywhere where you can look, I think.  I think
that "apt-config dump -c /root/.aptitude/config" would also achieve
the same results, but basically you looked into the right places.

I was asking because several reports related with "freezes" when
changing the states of the packages were due to the gzipped indices.




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

[pid 28407] stat("/var/lib/apt-xapian-index/index", 0x7ffc41affc40) =
-1 ENOENT (No such file or directory)
[pid 28407] stat("/var/lib/apt-xapian-index/index", 0x7ffc41b00330) =
-1 ENOENT (No such file or directory)
[pid 28407] stat("/var/lib/apt-xapian-index/index", 0x7ffc41affc40) =
-1 ENOENT (No such file or directory)
[pid 28407] stat("/var/lib/apt-xapian-index/index", 0x7ffc41b00330) =
-1 ENOENT (No such file or directory)
[pid 28407] stat("/var/lib/apt-xapian-index/index", 0x7ffc41affc40) =
-1 ENOENT (No such file or directory)


When installing "apt-xapian-index" and then running
"update-apt-xapian-index" the strace changes but it also seems to get
caught in another kind of endless loop.


Cheers.
-- 
Manuel A. Fernandez Montecelo 

Bug#850570: python-scapy: inet traceroute method world_trace() import wrong module

[Petter Reinholdtsen]

Package: python-scapy
Version: 2.2.0-1

The execution fail when trying to call TracerouteResult.world_trace() on
a traceroute result.  Here is how to reproduce the problem:

% cat x.py 
from scapy.all import *
host = "8.8.8.8"
res,unans = traceroute(host, dport=[80,443], maxttl=30, retry=-2)
res.world_trace()
% sudo python x.py 
WARNING: No route found for IPv6 destination :: (no default route?)
Begin emission:
.*Finished to send 60 packets.
***...Begin emission:
Finished to send 24 packets.
..Begin emission:
Finished to send 24 packets.
..
Received 44 packets, got 36 answers, remaining 24 packets
   8.8.8.8:tcp443 8.8.8.8:tcp80  
1  192.168.1.1 11 192.168.1.1 11 
2  10.231.128.111 10.231.128.111 
3  84.208.41.5011 84.208.41.5011 
4  80.232.88.4511 80.232.88.4511 
5  80.232.88.4411 80.232.88.4411 
6  62.95.54.12211 62.95.54.12211 
7  88.131.152.10   11 -  
8  209.85.142.85   11 -  
9  74.125.37.129   11 -  
10 8.8.8.8 SA -  
11 8.8.8.8 SA -  
12 8.8.8.8 SA -  
13 8.8.8.8 SA -  
14 8.8.8.8 SA -  
15 8.8.8.8 SA -  
16 8.8.8.8 SA -  
17 8.8.8.8 SA -  
18 8.8.8.8 SA -  
19 8.8.8.8 SA -  
20 8.8.8.8 SA -  
21 8.8.8.8 SA -  
22 8.8.8.8 SA -  
23 8.8.8.8 SA -  
24 8.8.8.8 SA -  
25 8.8.8.8 SA -  
26 8.8.8.8 SA -  
27 8.8.8.8 SA -  
28 8.8.8.8 SA -  
29 8.8.8.8 SA -  
30 8.8.8.8 SA -  
Traceback (most recent call last):
  File "x.py", line 4, in 
res.world_trace()
  File "/usr/lib/python2.7/dist-packages/scapy/layers/inet.py", line 1072, in 
world_trace
from modules.geo import locate_ip
ImportError: No module named modules.geo
%

The code look like this:

def world_trace(self):
from modules.geo import locate_ip

I suspect 'modules.geo' should read 'modules.geoip', as the geoip.py
file have a locate_ip() method.

Note, the locate_ip() method do not seem to work either.  Using it fail
like this:

% cat y.py 
from scapy.all import *
from scapy.modules.geoip import locate_ip
host = "8.8.8.8"
print locate_ip(host)
% python y.py 
WARNING: No route found for IPv6 destination :: (no default route?)
Traceback (most recent call last):
  File "y.py", line 4, in 
print locate_ip(host)
  File "/usr/lib/python2.7/dist-packages/scapy/modules/geoip.py", line 59, in 
locate_ip
cloc = country_loc_kdb.get_base()
NameError: global name 'country_loc_kdb' is not defined
%

-- 
Happy hacking
Petter Reinholdtsen

Bug#850571: mention there were some warnings removed from the example

[積丹尼 Dan Jacobson]

Package: netcat-openbsd
Version: 1.130-1
Severity: wishlist
File: /usr/share/man/man1/nc_openbsd.1.gz

On the man page:

   $ nc -zv host.example.com 20-30
   Connection to host.example.com 22 port [tcp/ssh] succeeded!
   Connection to host.example.com 25 port [tcp/smtp] succeeded!

[In reality there are many Connection refused messages not shown above,
but shown below. Therefore the above paragraph should make a note of it.]

   $ nc -zv host.example.com 80 20 22
   nc: connect to host.example.com 80 (tcp) failed: Connection refused
   nc: connect to host.example.com 20 (tcp) failed: Connection refused
   Connection to host.example.com port [tcp/ssh] succeeded!

Bug#677673: another one: Accepted ncc 2.8-2.1 (source amd64) into UNRELEASED… ;)

[Holger Levsen]

another candidate for autorects… (UNRELEASED)

- Forwarded message from John Paul Adrian Glaubitz 
 -

Date: Sat, 07 Jan 2017 21:33:44 +
From: John Paul Adrian Glaubitz 
To: debian-devel-chan...@lists.debian.org
Subject: Accepted ncc 2.8-2.1 (source amd64) into unstable
Reply-To: debian-de...@lists.debian.org
List-Id: 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 07 Jan 2017 22:10:15 +0100
Source: ncc
Binary: ncc
Architecture: source amd64
Version: 2.8-2.1
Distribution: sid
Urgency: medium
Maintainer: Anuradha Weeraman (anu) 
Changed-By: John Paul Adrian Glaubitz 
Description:
 ncc- C source code analyzer
Closes: 811745
Changes:
 ncc (2.8-2.1) UNRELEASED; urgency=medium
 .
   * Non-maintainer upload.
   * Fixed type for file_chunk::start,end from unsigned int to int
 to fix narrowing conversion issues with gcc-6 (Closes: #811745)
Checksums-Sha1:
 [trimmed]

-BEGIN PGP SIGNATURE-
 [trimmed]
-END PGP SIGNATURE-


- End forwarded message -

-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#850232: installation-guide: FTBFS randomly (ERROR: xref linking to appendix-gpl has no generated link text.)

[Samuel Thibault]

Hello,

Santiago Vila, on Thu 05 Jan 2017 10:05:24 +, wrote:
> This is just how the build ends, not necessarily the relevant part.
> 
> I've put several build logs here:
> 
> https://people.debian.org/~sanvila/build-logs/installation-guide/

Could you also post build logs which are successful?

Samuel

Bug#850569: jstest-gtk: Crash for missing data files

[James Cowgill]

Control: forcemerge 850022 -1

Hi,

On 07/01/17 21:43, Lluís Vilanova wrote:
> Package: jstest-gtk
> Version: 0.1.1~git20160825-1
> Severity: important
> 
> Starting jstest-gtk with a PS3 controller connected crashes the application 
> with
> the following message:
> 
>   Error: Failed to open file '/usr/bin/data/PS3.png': No such file or 
> directory

Duplicate of #850022 (different symptoms but caused by the same bug).

> If I start the app with a disconnected controller, an unhandled exception 
> error
> is shown after connecting the controller and clicking refresh.

Just to clarify, is this the same message as above (ie not a separate bug)?

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#850430: fixed in postfix 3.1.4-2

[Wolfgang Walter]

On Fri, 06 Jan 2017 16:49:17 + LaMont Jones  wrote:
> Source: postfix
> Source-Version: 3.1.4-2
> 
> We believe that the bug you reported is fixed in the latest version of
> postfix, which is due to be installed in the Debian FTP archive.

This does not fix the problem here. What fixes the problem is making a symlink 
to smtp called lmtp and changing master.cf to call lmtp instead of smtp.

I don't think you can call smtp as smtp if you want it to act in lmtp mode. 
Here code from smtp.c:
(from https://git.launchpad.net/postfix/tree/src/smtp/smtp.c?h=stable/v3.1)


/*
 * XXX At this point, var_procname etc. are not initialized.
 * 
 * The process name, "smtp" or "lmtp", determines the protocol, the DSN
 * server reply type, SASL service information lookup, and more. Prepare
 * for the possibility there may be another personality.
 */
sane_procname = sane_basename((VSTRING *) 0, argv[0]);
if (strcmp(sane_procname, "smtp") == 0)
smtp_mode = 1;
else if (strcmp(sane_procname, "lmtp") == 0)
smtp_mode = 0;


So I think there must be a link lmtp => smtp and in master.cf it sould be

lmtp  unix  -   -   -   -   -   lmtp

Regards,
-- 
Wolfgang Walter
Studentenwerk München
Anstalt des öffentlichen Rechts

Bug#850037: r-cran-rsqlite: Row value IN queries give syntax errors.

[Kirill Müller]

On 07.01.2017 22:02, Andreas Tille wrote:

Hi,

On Sat, Jan 07, 2017 at 07:56:24PM +0100, Kirill Müller wrote:

After upgrading the embedded SQLite sources to 3.16.2, the query now works.
Please install the branch that contains the upgrade with

#install.packages("remotes")
remotes::install_github("rstats-db/RSQLite@f-upgrade")

(not recommended for production!)

Hmmm, this does not really help.  We want to release rsqlite with the
next Debian stable release so this is definitely for production.  The
version that was used once this bug report was created was 3.15.2 but
we expect to release with sqlite version 3.16.2.

Do you think you can release some stable version ready for production
soon?
Thanks. The only issue I see is that RSQLite (that comes in 
r-cran-rsqlite) is bundled with a version of the SQLite library that is 
older than the one of the command line. Users who want to use RSQLite 
with a more recent version of the SQLite library will be able to do so 
by installing the development version of RSQLite from source. This is 
currently in a branch, therefore not recommended for production, but 
will be soon merged to master -- I'm afraid this is as stable as I can 
make it in the nearest future.


We decided to bundle the SQLite library (and not to use the system 
version) to simplify installation on other platforms and to simplify 
troubleshooting.



-Kirill


Kind regards

Andreas.

Bug#850569: jstest-gtk: Crash for missing data files

[Lluís Vilanova]

Package: jstest-gtk
Version: 0.1.1~git20160825-1
Severity: important

Starting jstest-gtk with a PS3 controller connected crashes the application with
the following message:

  Error: Failed to open file '/usr/bin/data/PS3.png': No such file or directory

If I start the app with a disconnected controller, an unhandled exception error
is shown after connecting the controller and clicking refresh.

It seems like the program is calculating the data path from its main program's
basename. This is useful for running from the build directory, but does not
follow the installation structure (the missing file is installed at
/usr/share/jstest-gtk/data/PS3.png).


Thanks,
  Lluis


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

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

Versions of packages jstest-gtk depends on:
ii  libatkmm-1.6-1v52.24.2-2
ii  libc6   2.24-8
ii  libcairomm-1.0-1v5  1.12.0-1+b1
ii  libgcc1 1:6.2.1-5
ii  libglibmm-2.4-1v5   2.50.0-1
ii  libgtkmm-2.4-1v51:2.24.5-1
ii  libsigc++-2.0-0v5   2.10.0-1
ii  libstdc++6  6.2.1-5
ii  libx11-62:1.6.4-2

Versions of packages jstest-gtk recommends:
ii  joystick  1:1.6.0-1

jstest-gtk suggests no packages.

-- no debconf information

Bug#846988: gnuplot: diff for NMU version 5.0.5+dfsg1-4.1

[Rob Browning]

Control: tags 846988 + patch
Control: tags 846988 + pending

Dear maintainer,

I've prepared an NMU for gnuplot (versioned as 5.0.5+dfsg1-4.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.
diff -Nru gnuplot-5.0.5+dfsg1/debian/changelog 
gnuplot-5.0.5+dfsg1/debian/changelog
--- gnuplot-5.0.5+dfsg1/debian/changelog2016-11-13 12:41:25.0 
-0600
+++ gnuplot-5.0.5+dfsg1/debian/changelog2017-01-07 15:23:15.0 
-0600
@@ -1,3 +1,11 @@
+gnuplot (5.0.5+dfsg1-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Change build dependency to "emacs25-nox | emacs25 | emacs24" to
+support and prefer emacs25. (Closes: #846988)
+
+ -- Rob Browning   Sat, 07 Jan 2017 15:23:15 -0600
+
 gnuplot (5.0.5+dfsg1-4) unstable; urgency=medium
 
   * [3ff368e] Move info-file into gnuplot-doc. (Closes: #843987)
diff -Nru gnuplot-5.0.5+dfsg1/debian/control gnuplot-5.0.5+dfsg1/debian/control
--- gnuplot-5.0.5+dfsg1/debian/control  2016-11-13 12:41:25.0 -0600
+++ gnuplot-5.0.5+dfsg1/debian/control  2017-01-07 15:23:15.0 -0600
@@ -33,7 +33,7 @@
texlive-latex-recommended,
libwxgtk3.0-dev,
zlib1g-dev,
-   emacs24
+   emacs25-nox | emacs25 | emacs24
 Standards-Version: 3.9.8
 Vcs-Browser: 
https://anonscm.debian.org/cgit/debian-science/packages/gnuplot.git
 Vcs-Git: https://anonscm.debian.org/git/debian-science/packages/gnuplot.git

Bug#850539: stable-pu: irssi

[Adam D. Barratt]

Control: tags -1 + pending

On Sat, 2017-01-07 at 16:36 +0100, Rhonda D'Vine wrote:
> Package: release.debian.org
> Severity: high

That's not a thing. :-) In any case, p-u bugs are "normal".

>  irssi got some security related updates, and I prepared an update.  I'm
> sending the debdiff for it, should be pretty straight forward, it's
> mostly the upstream commit fixing the security issues in a patch file,
> and I'm going to upload it now so it makes it in time for the point
> release.  If anything more is needed please let me know and I can try to
> fix that ASAP.

Flagged for acceptance.

Regards,

Adam

Bug#850320: mock: CVE-2016-6299: privilige escalation via mock-scm

[Tzafrir Cohen]

On Fri, Jan 06, 2017 at 01:37:58PM +, Holger Levsen wrote:
> Hi Tzafrir,
> 
> On Fri, Jan 06, 2017 at 12:25:07AM +0100, Tzafrir Cohen wrote:
> > The version in Jessie-backports seems to be the only one affected by it.
> 
> will you upload a fixed version to jessie-bpo or should I? (I'd be happy
> if you did, but I was the person introducing mock to bpo, so I'd take
> responsibility and fix, if needed.)

I prepared a version in the branch jessie-backports in git[1].

It seems to work OK here. I don't hae my key in the backports keyring,
so I prefer that you upload it.


-- 
Tzafrir Cohen | tzaf...@jabber.org | VIM is
http://tzafrir.org.il || a Mutt's
tzaf...@cohens.org.il ||  best
tzaf...@debian.org|| friend

Bug#534699: libssl0.9.8: likely race condition in int_new_ex_data()

[Sebastian Andrzej Siewior]

On 2009-06-26 23:26:34 [+1000], Russell Coker wrote:
> ==28314== Possible data race during read of size 8 at 0x6535338 by thread #3
> ==28314==at 0x52D183B: int_new_ex_data (ex_data.c:410)
> ==28314==by 0x5318BD7: RSA_new_method (rsa_lib.c:185)
> ==28314==by 0x531B76C: rsa_cb (rsa_asn1.c:80)
> ==28314==by 0x534CB42: asn1_item_ex_combine_new (tasn_new.c:177)
> ==28314==by 0x53501E4: ASN1_item_ex_d2i (tasn_dec.c:399)
> ==28314==by 0x53502B3: ASN1_item_d2i (tasn_dec.c:134)
> ==28314==by 0x534863C: d2i_PublicKey (d2i_pu.c:96)
> ==28314==by 0x534624F: X509_PUBKEY_get (x_pubkey.c:364)
> ==28314==by 0x5346C07: d2i_PUBKEY (x_pubkey.c:390)
> ==28314==by 0x40D480: SelectorInfo::Parse(char*) (dkimverify.cpp:1312)
> ==28314==by 0x40E0A4: CDKIMVerify::GetSelector(std::string const&, 
> std::string const&) (dkimverify.cpp:1369)
> 
> I get the above from helgrind on my AMD64 system.
> 
> EX_CLASS_ITEM *item = def_get_class(class_index);
> if(!item)
> /* error is already set */
> return 0;
> ad->sk = NULL;
> CRYPTO_r_lock(CRYPTO_LOCK_EX_DATA);
> mx = sk_CRYPTO_EX_DATA_FUNCS_num(item->meth); // line 410
> 
> Above is the relevant section of int_new_ex_data().
> 
> The def_get_class() function calls CRYPTO_w_lock(CRYPTO_LOCK_EX_DATA); before
> returning a pointer to a member of the hash table.  Now it seems possible for
> the item to be deleted from the hash table after def_get_class() is called but
> before CRYPTO_r_lock(CRYPTO_LOCK_EX_DATA) is called.

Does this still apply to 1.1.0c? The way the code looks now nothing
should vanish out of the sudden.

Sebastian

Bug#534687: libssl0.9.8: lh_retrieve modifies global data, bug in valgrind or OpenSSL?

[Sebastian Andrzej Siewior]

On 2009-06-26 21:09:13 [+1000], Russell Coker wrote:
> ==27681== Possible data race during write of size 4 at 0x652e2f0 by thread #5
> ==27681==at 0x5330C84: lh_retrieve (lhash.c:254)
> ==27681==by 0x52D12E1: def_get_class (ex_data.c:301)
> ==27681==by 0x52D180A: int_new_ex_data (ex_data.c:404)
> ==27681==by 0x5318BD7: RSA_new_method (rsa_lib.c:185)
> ==27681==by 0x531B76C: rsa_cb (rsa_asn1.c:80)
> ==27681==by 0x534CB42: asn1_item_ex_combine_new (tasn_new.c:177)
> ==27681==by 0x53501E4: ASN1_item_ex_d2i (tasn_dec.c:399)
> ==27681==by 0x53502B3: ASN1_item_d2i (tasn_dec.c:134)
> ==27681==by 0x534863C: d2i_PublicKey (d2i_pu.c:96)
> ==27681==by 0x534624F: X509_PUBKEY_get (x_pubkey.c:364)
> ==27681==by 0x5346C07: d2i_PUBKEY (x_pubkey.c:390)
> ==27681==by 0x40D480: SelectorInfo::Parse(char*) (dkimverify.cpp:1312)
> 
> The above is from a helgrind run on my AMD64 system.
> 
> void *lh_retrieve(LHASH *lh, const void *data)
> {
> lh->error=0;
> 
> The relevant code from lhash.c is above, it writes to data in the LHASH
> structure pointed to by the first parameter.
> 
> static EX_CLASS_ITEM *def_get_class(int class_index)
> {
> CRYPTO_w_lock(CRYPTO_LOCK_EX_DATA);
> p = lh_retrieve(ex_data, );
> 
> The relevant code from ex_data.c is above.  It seems that the lock
> CRYPTO_LOCK_EX_DATA will protect the data, so maybe valgrind is getting this
> wrong.  Valgrind 3.3.1 seemed to miss the CRYPTO_w_lock() type calls, but
> I'm using 3.4.1.  Maybe this is a bug in valgrind?  If you think so then feel
> free to reassign it.

I am tempted to close this. Can you still reproduce this with current
openssl & valgrind? RSA_new_method() is no longer using the class thingy
/ lhash so your old testcase won't do. And then 1.1.0c is using
pthread's locking functions so valgrind should know by now when a lock
is held.

Sebastian

Bug#850568: popularity-contest: popcon-largest-unused tries to read encrypted log

[Celelibi]

Package: popularity-contest
Version: 1.64
Severity: normal

Dear maintainer,

I'm not sure when this happened, but it looks like the statistics
gathered by popularity-contest are not encrypted before sending them
online.

However, the tool popcon-largest-unused (provided by this package) try
to read this file as if it were not encrypted.

I may suggest that popcon-largest-unused reads from
/var/log/popularity-contest.new, which is the unencrypted last file.

Best regards,
Celelibi

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

Kernel: Linux 3.10.11 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages popularity-contest depends on:
ii  debconf [debconf-2.0]  1.5.59
ii  dpkg   1.18.18

Versions of packages popularity-contest recommends:
ii  cron [cron-daemon] 3.0pl1-128
ii  exim4  4.88-2
ii  exim4-daemon-light [mail-transport-agent]  4.88-2
ii  gnupg  2.1.17-2

Versions of packages popularity-contest suggests:
pn  anacron  

-- debconf information:
  popularity-contest/submiturls:
* popularity-contest/participate: true

Bug#850567: jessie-pu: package qtbase-opensource-src/5.3.2+dfsg-4+deb8u2

[Adam D. Barratt]

Control: tags -1 + confirmed

On Sun, 2017-01-08 at 00:12 +0300, Dmitry Shachnev wrote:
> I want to request a stable update for qtbase-opensource-src to fix two bugs:
> 
> * #805265 (Sporadic segfault on exit in QNetworkConfigurationManagerPrivate::
>   pollEngines()) — backport of a one-line fix from Qt 5.5.
> 
> * #775398 / #847665 (QSystemTrayIcon not working on XFCE and MATE) —
>   backport of a six-lines fix from Qt 5.4.2.

Please go ahead.

Regards,

Adam

Bug#846991: vm: diff for NMU version 8.2.0b-2.1

[Rob Browning]

Control: tags 846991 + patch
Control: tags 846991 + pending

Hi Manoj,

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

Regards.
diff -u vm-8.2.0b/debian/changelog vm-8.2.0b/debian/changelog
--- vm-8.2.0b/debian/changelog
+++ vm-8.2.0b/debian/changelog
@@ -1,3 +1,12 @@
+vm (8.2.0b-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Support emacs25.  Change build dependency from emacs24 to "emacs25-nox
+| emacs25 | emacs24", and allow emacs25 as a flavor in the postinst
+and postrm (Closes: #846991).
+
+ -- Rob Browning   Sat, 07 Jan 2017 14:38:24 -0600
+
 vm (8.2.0b-2) unstable; urgency=low
 
   * Updated to standards version 3.9.6, no changes needed
diff -u vm-8.2.0b/debian/control vm-8.2.0b/debian/control
--- vm-8.2.0b/debian/control
+++ vm-8.2.0b/debian/control
@@ -6,7 +6,8 @@
 Priority: optional
 Maintainer: Manoj Srivastava 
 Standards-Version: 3.9.6
-Build-Depends-Indep: debhelper (>= 9.0.0), autotools-dev, emacs24,
+Build-Depends-Indep: debhelper (>= 9.0.0), autotools-dev,
+ emacs25-nox | emacs25 | emacs24,
  texinfo, texlive-latex-base, texlive-fonts-recommended
 
 Package: vm
diff -u vm-8.2.0b/debian/vm.postinst vm-8.2.0b/debian/vm.postinst
--- vm-8.2.0b/debian/vm.postinst
+++ vm-8.2.0b/debian/vm.postinst
@@ -186,7 +186,7 @@
 fi
 
 if which ucfr >/dev/null; then
-for flavour in emacs24 emacs22 emacs23 emacs-snapshot xemacs21; do
+for flavour in emacs25 emacs24 emacs22 emacs23 emacs-snapshot 
xemacs21; do
STARTDIR=/etc/$flavour/site-start.d;
STARTFILE="${package_name}-init.el";
 if [ -e "$STARTDIR/50$STARTFILE" ]; then
diff -u vm-8.2.0b/debian/vm.postrm vm-8.2.0b/debian/vm.postrm
--- vm-8.2.0b/debian/vm.postrm
+++ vm-8.2.0b/debian/vm.postrm
@@ -117,7 +117,7 @@
 rm -f -f $ELDIR/vm.elc
 fi
 
-for flavour in emacs24 emacs22 emacs23 emacs-snapshot xemacs21; do
+for flavour in emacs25 emacs24 emacs22 emacs23 emacs-snapshot xemacs21; do
 ELCDIR=/usr/share/$flavour/site-lisp/$package_name/
 if [ -f /etc/$flavour/site-start.d/50vm-init.el ]; then
 rm -f /etc/$flavour/site-start.d/50vm-init.el
@@ -136,7 +136,7 @@
 
 # This package has previously been removed and is now having
 # its configuration purged from the system.
-for flavour in emacs24 emacs22 emacs23 emacs-snapshot xemacs21; do
+for flavour in emacs25 emacs24 emacs22 emacs23 emacs-snapshot xemacs21; do
STARTDIR=/etc/$flavour/site-start.d;
STARTFILE="${package_name}-init.el";
 if which ucf >/dev/null; then

Bug#850567: jessie-pu: package qtbase-opensource-src/5.3.2+dfsg-4+deb8u2

[Dmitry Shachnev]

Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu

Dear Release team,

I want to request a stable update for qtbase-opensource-src to fix two bugs:

* #805265 (Sporadic segfault on exit in QNetworkConfigurationManagerPrivate::
  pollEngines()) — backport of a one-line fix from Qt 5.5.

* #775398 / #847665 (QSystemTrayIcon not working on XFCE and MATE) —
  backport of a six-lines fix from Qt 5.4.2.

The debdiff is attached.

--
Dmitry Shachnev
diff -Nru qtbase-opensource-src-5.3.2+dfsg/debian/changelog 
qtbase-opensource-src-5.3.2+dfsg/debian/changelog
--- qtbase-opensource-src-5.3.2+dfsg/debian/changelog   2015-05-19 
19:56:43.0 +0300
+++ qtbase-opensource-src-5.3.2+dfsg/debian/changelog   2017-01-07 
22:23:58.0 +0300
@@ -1,3 +1,15 @@
+qtbase-opensource-src (5.3.2+dfsg-4+deb8u2) jessie; urgency=medium
+
+  [ Dmitry Shachnev ]
+  * Backport upstream change (networkconfig_prevent_bad_deref.patch) to
+prevent bad-ptrs deref in QNetworkConfigurationManagerPrivate.
+Closes: #805265.
+  * Backport upstream change to fix X11 tray icons on some desktops
+(xcb_delay_showing_tray_icon_window_until_it_is_embedded.patch).
+Closes: #775398, #847665.
+
+ -- Dmitry Shachnev   Sat, 07 Jan 2017 22:09:33 +0300
+
 qtbase-opensource-src (5.3.2+dfsg-4+deb8u1) stable-proposed-updates; 
urgency=medium
 
   [ Dmitry Shachnev ]
diff -Nru 
qtbase-opensource-src-5.3.2+dfsg/debian/patches/networkconfig_prevent_bad_deref.patch
 
qtbase-opensource-src-5.3.2+dfsg/debian/patches/networkconfig_prevent_bad_deref.patch
--- 
qtbase-opensource-src-5.3.2+dfsg/debian/patches/networkconfig_prevent_bad_deref.patch
   1970-01-01 03:00:00.0 +0300
+++ 
qtbase-opensource-src-5.3.2+dfsg/debian/patches/networkconfig_prevent_bad_deref.patch
   2017-01-07 21:27:12.0 +0300
@@ -0,0 +1,15 @@
+Description: prevent bad-ptrs deref in QNetworkConfigurationManagerPrivate
+Origin: upstream, 
http://code.qt.io/cgit/qt/qtbase.git/commit/?id=3f0f707d4b898a96
+Bug: https://bugs.debian.org/805265
+Last-Update: 2015-11-16
+
+--- a/src/network/bearer/qnetworkconfigmanager_p.cpp
 b/src/network/bearer/qnetworkconfigmanager_p.cpp
+@@ -83,6 +83,7 @@
+ QMutexLocker locker();
+ 
+ qDeleteAll(sessionEngines);
++sessionEngines.clear();
+ if (bearerThread)
+ bearerThread->quit();
+ }
diff -Nru qtbase-opensource-src-5.3.2+dfsg/debian/patches/series 
qtbase-opensource-src-5.3.2+dfsg/debian/patches/series
--- qtbase-opensource-src-5.3.2+dfsg/debian/patches/series  2015-05-19 
19:54:43.0 +0300
+++ qtbase-opensource-src-5.3.2+dfsg/debian/patches/series  2017-01-07 
21:27:12.0 +0300
@@ -4,6 +4,8 @@
 gnukfreebsd.diff
 fix_bug_in_internal_comparison_operator.patch
 fix_imagehandlers_cves.diff
+networkconfig_prevent_bad_deref.patch
+xcb_delay_showing_tray_icon_window_until_it_is_embedded.patch
 
 # Patches that need to be upstreamed
 fix_sparc_atomics.patch
diff -Nru 
qtbase-opensource-src-5.3.2+dfsg/debian/patches/xcb_delay_showing_tray_icon_window_until_it_is_embedded.patch
 
qtbase-opensource-src-5.3.2+dfsg/debian/patches/xcb_delay_showing_tray_icon_window_until_it_is_embedded.patch
--- 
qtbase-opensource-src-5.3.2+dfsg/debian/patches/xcb_delay_showing_tray_icon_window_until_it_is_embedded.patch
   1970-01-01 03:00:00.0 +0300
+++ 
qtbase-opensource-src-5.3.2+dfsg/debian/patches/xcb_delay_showing_tray_icon_window_until_it_is_embedded.patch
   2017-01-07 21:27:12.0 +0300
@@ -0,0 +1,37 @@
+Description: xcb: delay showing tray icon window until it is embedded
+ Otherwise there is a race condition: when the tray implementation
+ gets around to embedding the window, if it was already shown,
+ it will be unmapped, embedded, and then remapped. Some tray
+ implementations will resize the tray icon to 1 pixel wide in
+ that case. We also never want to show a window that was intended
+ for the tray in any other location, so it's better that it remain
+ invisible until we are sure it is embedded.
+Origin: upstream, 
https://code.qt.io/cgit/qt/qtbase.git/commit/?id=612953a626ec21b8
+Bug: https://bugs.debian.org/775398
+Bug: https://bugs.debian.org/847665
+Last-Update: 2016-12-26
+
+--- a/src/plugins/platforms/xcb/qxcbwindow.cpp
 b/src/plugins/platforms/xcb/qxcbwindow.cpp
+@@ -701,6 +701,9 @@
+ if (connection()->time() != XCB_TIME_CURRENT_TIME)
+ updateNetWmUserTime(connection()->time());
+ 
++if (window()->objectName() == QLatin1String("QSystemTrayIconSysWindow"))
++return; // defer showing until XEMBED_EMBEDDED_NOTIFY
++
+ Q_XCB_CALL(xcb_map_window(xcb_connection(), m_window));
+ 
+ if (QGuiApplication::modalWindow() == window())
+@@ -2130,7 +2133,10 @@
+ switch (event->data.data32[1]) {
+ case XEMBED_WINDOW_ACTIVATE:
+ case XEMBED_WINDOW_DEACTIVATE:
++break;
+ case XEMBED_EMBEDDED_NOTIFY:
++

Bug#534534: libssl0.9.8: valgrind/helgrind reports Possible data race during write

[Sebastian Andrzej Siewior]

On 2009-06-25 15:59:32 [+1000], Russell Coker wrote:
> ==32465== Possible data race during write of size 4 at 0x55D7CE8
> ==32465==at 0x52CD88D: CRYPTO_malloc (mem.c:298)
> ==32465==by 0x534AC75: asn1_item_ex_combine_new (tasn_new.c:191)
> ==32465==by 0x534E184: ASN1_item_ex_d2i (tasn_dec.c:399)
> ==32465==by 0x534E253: ASN1_item_d2i (tasn_dec.c:134)
> ==32465==by 0x5344B7E: d2i_PUBKEY (x_pubkey.c:388)
> ==32465==by 0x40D580: SelectorInfo::Parse(char*) (dkimverify.cpp:1312)
> 
> Above is a helgrind error I get on my AMD64 system.

Is valgrind still complaining here?

> Below is a patch I wrote which appears to solve this problem.  According to
> the comments on my above blog post it seems possible that this patch will also
> slightly improve performance on SMP systems when under heavy load.
> 
> --- ../t/openssl-0.9.8g/crypto/mem.c  2003-12-01 23:06:15.0 +1100
> +++ crypto/mem.c  2009-06-25 10:42:03.0 +1000
> @@ -254,10 +254,12 @@
>  
>   if (num <= 0) return NULL;
>  
> - allow_customize = 0;
> + if(allow_customize)
> + allow_customize = 0;
>   if (malloc_debug_func != NULL)
>   {
> - allow_customize_debug = 0;
> + if(allow_customize_debug)
> + allow_customize_debug = 0;
>   malloc_debug_func(NULL, num, file, line, 0);
>   }
>   ret = malloc_locked_ex_func(num,file,line);

The code is mostly the same in 1.1.0c. The variable is always to 0 so
there is no problem if two threads do it at the same time.
I see no reason not to close this report. There might be room for
improvement to safe a few cycles and not alays set allow_customize to
zero.

Sebastian

Bug#849848: blhc: Architecture independent packages shouldn't log compiler commands

[Simon Ruderich]

On Sun, Jan 01, 2017 at 12:06:39PM +0100, Ferenc Wágner wrote:
> Dear Maintainer,
>
> https://qa.debian.org/bls/bytag/I-no-compiler-commands.html says:
>
>   Possible issues this might hint at:
>   * A package being Architecture: all, though it only contains architecture
> independent data.
>
> which I don't get.  The very point of Architecture: all packages is that they
> contain architecture independent data (or code) only.  So why is this flagged
> as a possible issue?

You're right, that doesn't sound correct. Maybe it's a typo and
should say "any" instead of "all".

However this is not a bug in blhc itself, but in bls and the
website. Please report it to the QA mailing list
debian...@lists.debian.org as mentioned on the website.

Regards
Simon
-- 
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9


signature.asc
Description: PGP signature

Bug#805265: Raising severity of bugs

[Dmitry Shachnev]

severity 805265 important
severity 847665 important

In my opinion these two bugs deserve important severity, and I am including
them in my stable upload.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#850037: r-cran-rsqlite: Row value IN queries give syntax errors.

[Andreas Tille]

Hi,

On Sat, Jan 07, 2017 at 07:56:24PM +0100, Kirill Müller wrote:
> After upgrading the embedded SQLite sources to 3.16.2, the query now works.
> Please install the branch that contains the upgrade with
> 
> #install.packages("remotes")
> remotes::install_github("rstats-db/RSQLite@f-upgrade")
> 
> (not recommended for production!)

Hmmm, this does not really help.  We want to release rsqlite with the
next Debian stable release so this is definitely for production.  The
version that was used once this bug report was created was 3.15.2 but
we expect to release with sqlite version 3.16.2.

Do you think you can release some stable version ready for production
soon?

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#849676: autopkgtest fails it's own testcases since dpkg 1.18.15

[Paul Gevers]

Hi Martin,

On 30-12-16 15:24, Paul Gevers wrote:
> On 30-12-16 15:12, Martin Pitt wrote:
>> This is worth uploading, but I figure I'll wait a bit more for your
>> --apt-series changes to land too?

I have an RC bug in one of my packages and will need to attend to that
first. It will probably take me more than a week for my --apt-release
changes to finalize. (I think I'll go back non python3-apt processing).

Paul



signature.asc
Description: OpenPGP digital signature

Bug#849959: Removed package(s) from unstable

[Adam D. Barratt]

On Sat, 2017-01-07 at 21:22 +0100, Tomasz Buchert wrote:
> On 07/01/17 16:49, Debian FTP Masters wrote:
> > We believe that the bug you reported is now fixed; the following
> > package(s) have been removed from unstable:
> > 
> > python-guess-language |0.5.2-3 | all
> > 
> > --- Reason ---
> > NBS; depending on broken python-3to2
> > --
> 
> Will python3-guess-language migrate to stretch? I'm a bit worried
> seeing this message.

You mean python-guess-language, given that's what the source package is
named.

That's not up to the FTP team, so I'm not sure why you're asking them.
In any case, as looking at the excuses for the package will show, it
certainly _wouldn't_ have migrated without the outdated builds for the
Python 2 package being removed.

Regards,

Adam

Bug#849382: [apt] Every package on the system gets silently upgraded to backports. The result is severe system breakage, malfunctioning and data loss.

[Sven Hartge]

On 07.01.2017 21:24, Julian Andres Klode wrote:
> On Sat, Jan 07, 2017 at 09:15:15PM +0100, Sven Hartge wrote:
>> On Mon, 26 Dec 2016 14:40:05 +0100 (CET) <34tg...@tutanota.com> wrote:
>>
>>> I use Debian 8 64bit with GNOME installed with standard install
>>> procedure from netinstall and using tasksel. This occured to me the
>>> second time. First time was a year ago, I reinstalled Debian then and
>>> a year after this happens again. Both occurences were on Debian 8,
>>> stable at the time.
>>
>> I have seen this as well and know under which circumstances this happens:
>>
>> a) backports repository is enabled in source.list (obviously)
>> b) "apt update" is run and all normal repositories fail to download or
>> are invalid
>>
>> When this happens, apt will happily upgrade all packages where a
>> backported version exists to that version.
> 
> This should not happen. The old repository state should be used, and thus
> the pinning should not change. 

That's what I thought as well.

> That said, maybe that only works right in 1.1 and newer, I don't
> really know.

I have definitely seen this in Jessie, maybe even Wheezy (memory a bit
fuzzy in that regard).

I run apticron on all our servers (~250) and it happened about once a
month that one (a different one every time) of the server prompted to
upgrade all packages to their backports-version.

But after switching from httpredir.debian.org to deb.debian.org this
problem did not occur again, so far at least.

But there is absolutely something problematic with the version in Jessie
where it is possible to trigger the behavior from this bug report.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature

Bug#849959: Removed package(s) from unstable

[Tomasz Buchert]

On 07/01/17 16:49, Debian FTP Masters wrote:
> We believe that the bug you reported is now fixed; the following
> package(s) have been removed from unstable:
> 
> python-guess-language |0.5.2-3 | all
> 
> --- Reason ---
> NBS; depending on broken python-3to2
> --

Will python3-guess-language migrate to stretch? I'm a bit worried
seeing this message.

Tomasz


signature.asc
Description: PGP signature

Bug#850563: jessie-pu: package debian-edu-install/1.821+deb8u2

[Holger Levsen]

Hi,

as this was such a trivial change, I forgot that d-e-install also
produces udebs and as such you probably want an KiBi ack, thus cc:ing
him and debian-boot for feedback+acking. Thanks!

On Sat, Jan 07, 2017 at 09:15:56PM +0100, Holger Levsen wrote:
> Package: release.debian.org
> Severity: normal
> Tags: jessie
> User: release.debian@packages.debian.org
> Usertags: pu
> 
> Hi,
> 
> we would like to update debian-edu-install with a single change:
> 
> * Update version number to 8+edu1 in preparation of our second Debian Edu
>   release based on Debian Jessie.
> 
> which is needed to build new installation images for jessie (which
> should have a different version…)
> 
> The full debdiff is:
> 
> $ debdiff debian-edu-install_1.821+deb8u1.dsc 
> debian-edu-install_1.821+deb8u2.dsc
> diff -Nru debian-edu-install-1.821+deb8u1/debian/changelog 
> debian-edu-install-1.821+deb8u2/debian/changelog
> --- debian-edu-install-1.821+deb8u1/debian/changelog  2016-05-24 
> 16:23:18.0 +0200
> +++ debian-edu-install-1.821+deb8u2/debian/changelog  2017-01-07 
> 14:29:22.0 +0100
> @@ -1,3 +1,10 @@
> +debian-edu-install (1.821+deb8u2) jessie; urgency=medium
> +
> +  * Update version number to 8+edu1 in preparation of our second Debian Edu
> +release based on Debian Jessie.
> +
> + -- Holger Levsen   Sat, 07 Jan 2017 14:28:45 +0100
> +
>  debian-edu-install (1.821+deb8u1) jessie; urgency=medium
>  
>* Update version number to 8+edu0 in preparation of our first Jessie 
> release.
> diff -Nru debian-edu-install-1.821+deb8u1/debian/debian-edu-install.postinst 
> debian-edu-install-1.821+deb8u2/debian/debian-edu-install.postinst
> --- debian-edu-install-1.821+deb8u1/debian/debian-edu-install.postinst
> 2016-05-23 00:17:14.0 +0200
> +++ debian-edu-install-1.821+deb8u2/debian/debian-edu-install.postinst
> 2017-01-07 13:36:55.0 +0100
> @@ -155,7 +155,7 @@
>'7.1+edu0~a3' '7.1+edu0~b0' '7.1+edu0~b1' '7.1+edu0~b2' \
>'7.1+edu0' '8.0.0+edu+alpha0' '8.0+edu+alpha0' \
>'8.0+edu0~alpha0' '8.0+edu0~alpha1' '8.0+edu0~alpha2' \
> -  '8.0+edu0~beta1'
> +  '8.0+edu0~beta1' '8+edu0'
>   do
>   if [ "$VERSION" = "$i" ] ; then
>   sed -i $debian_edu_config -e \
> diff -Nru debian-edu-install-1.821+deb8u1/version 
> debian-edu-install-1.821+deb8u2/version
> --- debian-edu-install-1.821+deb8u1/version   2016-05-23 00:17:14.0 
> +0200
> +++ debian-edu-install-1.821+deb8u2/version   2017-01-07 13:36:55.0 
> +0100
> @@ -1 +1 @@
> -8+edu0
> +8+edu1
> 
> 
> 
> (The change in postinst is for recording previous versions.)
> 
> As the change is trivial and hopefully uncontroversial (and as we have done so
> during wheezy too), I'll go ahead and upload this straight away.
> 
> 
> Thanks for all your work on 8.7!
> 
> btw, is the subject correct? reportbug asked me for the current version
> number, which was …+deb8u1 and which I then manully corrected in the subject…
> 
> -- 
> cheers,
>   Holger



-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#850566: jessie-pu: package debian-edu-doc/1.6~20161129+deb8u3

[Holger Levsen]

Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu

Hi,

we would like to update debian-edu-doc in jessie to bring documentation
and translation updates of the jessie manual (and updated wheezy bokmal 
translation) to our users:

 debian-edu-doc (1.6~20161129+deb8u3) jessie; urgency=medium
 .
   * Update Debian Edu Jessie manual from the wiki.
 .
   [ Wolfgang Schweer ]
   * Fix (da|nl) Jessie manual PO files to get the PDF manuals built.
 .
   [ Jessie Manual translation updates ]
   * German: Wolfgang Schweer.
   * Norwegian Bokmål: Ingrid Yrvin, Ole-Erik Yrvin and Petter Reinholdtsen.
   * Dutch: Frans Spiesschaert.
   * Italian: Claudio Carboncini.
 .
   [ Wheezy Manual translation updates ]
   * Norwegian Bokmål: Petter Reinholdtsen, Ingrid Yrvin.


$ debdiff debian-edu-doc_1.6~20160910+deb8u2.dsc  
debian-edu-doc_1.6~20161129+deb8u3.dsc|diffstat
 
/tmp/Tmm0Q5UfOS/debian-edu-doc-1.6~20161129+deb8u3/documentation/debian-edu-jessie/images/de/worldmap.png
 |binary
 
/tmp/Tmm0Q5UfOS/debian-edu-doc-1.6~20161129+deb8u3/documentation/debian-edu-jessie/images/es/worldmap.png
 |binary
 
/tmp/Tmm0Q5UfOS/debian-edu-doc-1.6~20161129+deb8u3/documentation/debian-edu-jessie/images/fr/worldmap.png
 |binary
 
/tmp/Tmm0Q5UfOS/debian-edu-doc-1.6~20161129+deb8u3/documentation/debian-edu-jessie/images/worldmap.png
|binary
 debian-edu-doc-1.6~20161129+deb8u3/debian/changelog
   |   18 
 
debian-edu-doc-1.6~20161129+deb8u3/documentation/debian-edu-jessie/debian-edu-jessie-manual.da.po
 |  149 ++--
 
debian-edu-doc-1.6~20161129+deb8u3/documentation/debian-edu-jessie/debian-edu-jessie-manual.de.po
 |  163 ++--
 
debian-edu-doc-1.6~20161129+deb8u3/documentation/debian-edu-jessie/debian-edu-jessie-manual.es.po
 |   91 +-
 
debian-edu-doc-1.6~20161129+deb8u3/documentation/debian-edu-jessie/debian-edu-jessie-manual.fr.po
 |  157 ++--
 
debian-edu-doc-1.6~20161129+deb8u3/documentation/debian-edu-jessie/debian-edu-jessie-manual.it.po
 |  292 +++
 
debian-edu-doc-1.6~20161129+deb8u3/documentation/debian-edu-jessie/debian-edu-jessie-manual.nb.po
 |  372 +-
 
debian-edu-doc-1.6~20161129+deb8u3/documentation/debian-edu-jessie/debian-edu-jessie-manual.nl.po
 |  176 +++-
 
debian-edu-doc-1.6~20161129+deb8u3/documentation/debian-edu-jessie/debian-edu-jessie-manual.pot
   |   89 +-
 
debian-edu-doc-1.6~20161129+deb8u3/documentation/debian-edu-jessie/debian-edu-jessie-manual.xml
   |   44 -
 debian-edu-doc-1.6~20161129+deb8u3/documentation/debian-edu-jessie/version 
   |2 
 
debian-edu-doc-1.6~20161129+deb8u3/documentation/debian-edu-wheezy/debian-edu-wheezy-manual.nb.po
 |  188 ++---

$ debdiff debian-edu-doc_1.6~20160910+deb8u2_amd64.changes 
debian-edu-doc_1.6~20161129+deb8u3_amd64.changes
showed identical files inside all the debs (and reasonable, aka minimal
file size changes).

The diff is attached compressed. I've also uploaded the package as this seems
to be an easy accept to me ;)


Thanks for all your work on 8.7!

-- 
cheers,
Holger


debian-edu-doc_1.6~20161129+deb8u3.diff.xz
Description: application/xz


signature.asc
Description: Digital signature