Bug#848782: statsmodels: FTBFS: TypeError: 'float' object cannot be interpreted as an index

[Andreas Tille]

Hi Ole,

> the attached patch fixes the FTBFS. What is the schedule to fix the
> other problems with statsimage -- especially pandas?

I learned that NeuroDebian is happy about team uploads / NMUs - so
I think its fine if you upload your patch.

Kind regards

Andreas.

PS: If you are not convinced and there is no response from Yaroslav or
Michael in the next 24 hours - well, people are occupied by real life
these days, yust tell me and I'd upload.

-- 
http://fam-tille.de

Bug#849309: nmu: bino_1.6.5-1

[Daniel Schaal]

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

Hello,

on amd64 bino wasn't built in a clean environment causing it to depend on 
unavailable libraries,
so please rebuild it for this architecture.

Thanks

nmu bino_1.6.5-1 . amd64 . unstable . -m "Rebuild against libass and ffmpeg 
from unstable"

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

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

Bug#849308: wireguard: Wireguard should not transition to stable yet

[Daniel Kahn Gillmor]

Source: wireguard
Version: 0.0.20161223-1
Severity: grave
Tags: upstream
Justification: renders package unusable

Wireguard appears to be stable and reliable enough to distribute in
debian unstable, to get more widespread testing than would arise from
distribution in experimental alone.

However, the on-wire format might still change, leading to potential
interop issues, and upstream isn't yet willing to maintain a stable
branch in the face of security issues (which is understandable given
the age of the project.

So this bug report is a placeholder to keep it from migration.  Feel
free to comment here!

   --dkg

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

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

Bug#844034: Any intend to fix this soon

[Andreas Tille]

Hi Afif,

On Sat, Dec 24, 2016 at 09:47:56PM -0800, Afif Elghraoui wrote:
> > Its no real problem.  I think it will not happen to frequently since the
> > situation to save package for upcoming releases is only every second
> > year - perhaps posting the fact you are working in a separate branch
> > would help in such cases.
> 
> Fair enough. I thought it might have been sufficient to post updates to
> the upstream tracker since the bug was marked as forwarded.

I admit I'm not happy about the BTS feature which moves "Forwarded bugs
-- Serious" below "Outstanding bugs -- Wishlist items".  I would prefer
if these would stay on top of the bugs page.  Since I forget this all
the time I was stumbling about this quite late in our bug squashing
effort.  So I most probably over reacted yesterday a bit without diving
more into the details of the issue.
 
> >  Feel free to replace everything I did by your
> > probably more advanced changes since you know the internals way better.
> > I also do not consider my time terribly wasted since I now have some
> > insight into these packages.
> 
> Thanks.

I should explicitly say "also cme formating changes". ;-)
 
> As a quick update (also posted to the upstream tracker), some changes in
> blasr 5's handling of SAM/BAM files is causing the main problems now.
> Fixing it in pbhoney would require some more intrusive changes, which I
> could probably handle, but I don't think it would be a good idea to
> proceed without upstream's cooperation on this. It's possible that
> pbsuite will not be released with Stretch because of this.

That's OK.  We will manage to get several new packages into Stretch and
others are just missing.  Backports will help users until Stretch+1. :-)
 
Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#849307: New upstream version available

[Alexander Gerasiov]

Package: postsrsd
Severity: wishlist

Upstream version 1.4 is available for a year. Please consider packaging
it.

-- System Information:
Debian Release: 7.11
  APT prefers oldstable-updates
  APT policy: (640, 'oldstable-updates'), (640, 'oldstable-proposed-updates'), 
(640, 'oldstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-45-pve (SMP w/4 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Bug#849294: python-apt: aptsources.sourceslist ignores sources.list.d/*.sources files

[Paul Gevers]

Hi Julian

I am then asking for advice.

On 12/25/16 01:00, Julian Andres Klode wrote:
> If you want to use the aptsources module or a software based on it,
> I can only advise you not to use the deb822 format.

I am currently working on autopkgtest in scope of support for gating
autopkgtests for unstable to testing migration¹. One of the steps that
is needed (and currently supported for Ubuntu's pockets (without deb822
support)) is a way to generate a new sources file for an additional
release based on the *first* currently configured release. What I need
is to be able to reasonably reliably determine it, hence rely on
integrated tools from apt. What tools do you propose I use (autopkgtest
is written in python, hence I was looking at python-apt). I hope you
will not recommend to not support deb822 in general.

> Given the complexity of the issue at hand and no chance for a solution in
> the foreseeable future, I'm downgrading this to wishlist, according to its
> description: "[for any feature request, and also] for any bugs that are very
> difficult to fix due to major design considerations."

Fine with me.

Paul

¹ https://wiki.debian.org/debci/britneyIntegration



signature.asc
Description: OpenPGP digital signature

Bug#849306: libpam-mount: typo prevents extra hardening flags from being enabled

[Jeremy Bicha]

Package: libpam-mount
Version: 2.16-1

See the Ubuntu patch:

https://launchpadlibrarian.net/287089358/libpam-mount_2.14-2_2.14-2ubuntu1.diff.gz

--- libpam-mount-2.14/debian/rules 2016-09-27 09:40:33.0 +
+++ libpam-mount-2.14/debian/rules 2016-09-28 14:34:08.0 +
@@ -1,6 +1,6 @@
 #!/usr/bin/make -f

-export DEB_BUILD_OPTIONS = hardening=+all
+export DEB_BUILD_MAINT_OPTIONS = hardening=+all

 %:
  dh $@



Thanks,
Jeremy Bicha

Bug#849305: ITP: python-shutilwhich -- A backport of Python3's shutil.which module

[Ramakrishnan Muthukrishnan]

On Thu, Dec 22, 2016, at 07:29 AM, Ramakrishnan Muthukrishnan wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Ramakrishnan Muthukrishnan 
> 
> * Package name: python-shutilwhich
>   Version : 1.1.0
>   Upstream Author : Marc Brinkmann 
> * URL : https://github.com/mbr/shutilshich

Hmm.. Typo. The upstream url should be read as

Bug#849305: ITP: python-shutilwhich -- A backport of Python3's shutil.which module

[Ramakrishnan Muthukrishnan]

Package: wnpp
Severity: wishlist
Owner: Ramakrishnan Muthukrishnan 

* Package name: python-shutilwhich
  Version : 1.1.0
  Upstream Author : Marc Brinkmann 
* URL : https://github.com/mbr/shutilshich
* License : Python-3
  Programming Lang: Python
  Description : A backport of Python3's shutil.which module

This is a port of Python 3's shutil.which module mostly copied and pasted
from Python 3 source.
.
This package contains the Python 2 module.

Bug#801619: postsrsd: [INTL:ru] Russian debconf templates translation

[Yuri Kozlov]

Hello.

Any progress?

-- 
Best Regards,
Yuri Kozlov

Bug#849304: actiona: Actiona fails to start

[Will]

Package: actiona
Version: 3.9.2-1
Severity: important

Dear Maintainer,

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

 * What led up to the situation?
   - Nothing. It didn't work after installing.

 * What exactly did you do (or not do) that was effective (or
   ineffective)?
   - I started this program in a terminal emulator and it just stalls.

 * What was the outcome of this action?
   - The program stalls at "Creating action dialog Pixel color..."

Here's what is shown when I start actiona in the terminal emulator:

`
(actiona:924): GLib-GObject-WARNING **: cannot register existing type 
'GtkWidget'

(actiona:924): GLib-GObject-WARNING **: cannot add class private field to 
invalid type ''

(actiona:924): GLib-GObject-WARNING **: cannot add private field to invalid 
(non-instantiatable) type ''

(actiona:924): GLib-GObject-CRITICAL **: g_type_add_interface_static: assertion 
'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed

(actiona:924): GLib-GObject-WARNING **: cannot register existing type 
'GtkBuildable'

(actiona:924): GLib-GObject-CRITICAL **: g_type_interface_add_prerequisite: 
assertion 'G_TYPE_IS_INTERFACE (interface_type)' failed

(actiona:924): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' 
failed

(actiona:924): GLib-GObject-CRITICAL **: g_type_add_interface_static: assertion 
'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed

(actiona:924): GLib-GObject-CRITICAL **: g_type_register_static: assertion 
'parent_type > 0' failed

(actiona:924): GLib-GObject-WARNING **: cannot add private field to invalid 
(non-instantiatable) type ''
Killed
`

   * What outcome did you expect instead?

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


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

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

Versions of packages actiona depends on:
ii  libc6  2.24-7
ii  libgcc11:6.2.1-5
ii  libgdk-pixbuf2.0-0 2.36.0-1
ii  libgl1-mesa-glx [libgl1]   13.0.2-1
ii  libglib2.0-0   2.50.2-2
ii  libnotify4 0.7.7-1
ii  libopencv-calib3d2.4v5 2.4.9.1+dfsg-2.1
ii  libopencv-contrib2.4v5 2.4.9.1+dfsg-2.1
ii  libopencv-core2.4v52.4.9.1+dfsg-2.1
ii  libopencv-features2d2.4v5  2.4.9.1+dfsg-2.1
ii  libopencv-flann2.4v5   2.4.9.1+dfsg-2.1
ii  libopencv-gpu2.4v5 2.4.9.1+dfsg-2.1
ii  libopencv-highgui2.4-deb0  2.4.9.1+dfsg-2.1
ii  libopencv-imgproc2.4v5 2.4.9.1+dfsg-2.1
ii  libopencv-legacy2.4v5  2.4.9.1+dfsg-2.1
ii  libopencv-ml2.4v5  2.4.9.1+dfsg-2.1
ii  libopencv-objdetect2.4v5   2.4.9.1+dfsg-2.1
ii  libopencv-ocl2.4v5 2.4.9.1+dfsg-2.1
ii  libopencv-photo2.4v5   2.4.9.1+dfsg-2.1
ii  libopencv-stitching2.4v5   2.4.9.1+dfsg-2.1
ii  libopencv-superres2.4v52.4.9.1+dfsg-2.1
ii  libopencv-ts2.4v5  2.4.9.1+dfsg-2.1
ii  libopencv-video2.4v5   2.4.9.1+dfsg-2.1
ii  libopencv-videostab2.4v5   2.4.9.1+dfsg-2.1
ii  libqt5core5a   5.7.1~20161021+dfsg-6
ii  libqt5dbus55.7.1~20161021+dfsg-6
ii  libqt5gui5 5.7.1~20161021+dfsg-6
ii  libqt5multimedia5  5.7.1~20161021-2
ii  libqt5multimediawidgets5   5.7.1~20161021-2
ii  libqt5network5 5.7.1~20161021+dfsg-6
ii  libqt5script5  5.7.1~20161021+dfsg-2
ii  libqt5scripttools5 5.7.1~20161021+dfsg-2
ii  libqt5sql5 5.7.1~20161021+dfsg-6
ii  libqt5widgets5 5.7.1~20161021+dfsg-6
ii  libqt5x11extras5   5.7.1~20161021-2
ii  libqt5xml5 5.7.1~20161021+dfsg-6
ii  libqt5xmlpatterns5 5.7.1~20161021-3
ii  libstdc++6 6.2.1-5
ii  libx11-6   2:1.6.3-1
ii  libxtst6   2:1.2.2-1+b1

Versions of packages actiona recommends:
ii  libqt5sql5-sqlite  5.7.1~20161021+dfsg-6

actiona suggests no packages.

-- no debconf information

Bug#849266: [Pkg-lirc-maint] Bug#849266: lirc: does not work with update 0.9.4c-4 to 0.9.4c-5

[Alec Leamas]

Hi Tomas!


On 24/12/16 16:40, Thomas Renard wrote:




What version where you updating from?



it was 0.9.4c-4 and yes, I needed to change my configs with upgrading to
0.9.4xxx some weeks ago.


OK, that should rule out a lot of things...

> etc/lirc/lircd.conf.dist [Errno 2] Datei oder Verzeichnis nicht 
gefunden: u'/etc/lirc/lircd.conf.dist'


This is just weird. This file is part of the lirc package:

$ dpkg -c lirc_0.9.4c-6_amd64.deb | grep lircd.conf.dist
-rw-r--r-- root/root  [...]  ./etc/lirc/lircd.conf.dist

Have you any idea why this file is missing by you? The same goes for the 
 missing devinput.lircd.conf:


$ dpkg -c lirc_0.9.4c-6_amd64.deb | grep devinput.lircd.conf
-rw-r--r-- root/root  [...] ./etc/lirc/lircd.conf.d/devinput.lircd.conf



- Configuration Files:



/etc/lirc/lirc_options.conf changed:


This shouldn't change on an update from -4. Yes, indeed, it's missing
is conffiles. Will fix, but it looks you have updated this so it's OK 
(?) This is probably not the cause of your problem as long as the 
/dev/input/myremote device exists and works OK.



/etc/lirc/lircd.conf changed:
include "lircd.conf.d/*.conf"


This looks bad. lirc is not supposed to touch an existing lircd.conf on 
an update, just to create it if it does not exist. Did you have a 
/etc/lirc/lircd.conf before upgrading to -5?



/etc/lirc/lircd.conf.d/devinput.lircd.conf [Errno 2] Datei oder Verzeichnis 
nicht gefunden: u'/etc/lirc/lircd.conf.d/devinput.lircd.conf'


This might be the culprit.  Since you are using the devinput driver it 
needs the devinput.lircd.conf.


If you have a /etc/lirc/lircd.conf.d/devinput.lircd.conf.dist you could 
just copy it to /etc/lirc/lircd.conf.d/devinput.lircd. Otherwise, the 
lirc-make-devinput script can create a new and possibly better file 
using something like


  # lirc-make-devinput > /etc/lirc/lircd.conf.d/devinput.lircd.conf

However, the core issue is why it's not there, see above.



Cheers!

--alec

Bug#844034: Any intend to fix this soon

[Afif Elghraoui]

Hi, Andreas,

على السبت 24 كانون الأول 2016 ‫11:34، كتب Andreas Tille:
> On Sat, Dec 24, 2016 at 07:24:22AM -0800, Afif Elghraoui wrote:
>> I'm really sad to see the duplication of effort when I was so
>> particular to make sure my work was pushed :(. Is there a way we can
>> avoid this in the future?
> 
> Its no real problem.  I think it will not happen to frequently since the
> situation to save package for upcoming releases is only every second
> year - perhaps posting the fact you are working in a separate branch
> would help in such cases.

Fair enough. I thought it might have been sufficient to post updates to
the upstream tracker since the bug was marked as forwarded.

>  Feel free to replace everything I did by your
> probably more advanced changes since you know the internals way better.
> I also do not consider my time terribly wasted since I now have some
> insight into these packages.
> 

Thanks.

As a quick update (also posted to the upstream tracker), some changes in
blasr 5's handling of SAM/BAM files is causing the main problems now.
Fixing it in pbhoney would require some more intrusive changes, which I
could probably handle, but I don't think it would be a good idea to
proceed without upstream's cooperation on this. It's possible that
pbsuite will not be released with Stretch because of this.

Thanks and regards
Afif

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

Bug#817602: olpc-xo1: Removal of debhelper compat 4

[Andres Salomon]

On December 24, 2016 7:24:00 PM PST, Paul Wise  wrote:
>On Sun, Dec 25, 2016 at 10:38 AM, Andres Salomon wrote:
>
>> Thanks for the patch.  Given that OLPC isn't really alive any more,
>> I'm thinking the OLPC packages should probably just be removed from
>the
>> archive for Stretch.  Popcon shows exactly 1 installation of this
>> package.. https://qa.debian.org/popcon.php?package=olpc-xo1
>
>I think you will find that OLPC is still active and recently made a
>release:
>
>http://lists.laptop.org/pipermail/devel/2016-December/thread.html
>
>They also have a Debian derivative:
>
>https://wiki.debian.org/Derivatives/Census/OLPC
>
>I've asked James to respond to your mail.
>


I meant OLPC the hardware organization. I'm glad to see James is still 
producing Fedora-based images for legacy hardware.  I'm pretty sure they 
haven't produced XO-1s in close to a decade, and that us what my packages are 
for.  XO-1.5 and XO-4 were never supported without additional hacks.

That said, I can orphan the packages; I just don't see much point with such old 
hardware and the lack of package users.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#849303: rear: FTBFS: asciidoc: Command not found

[Aaron M. Ucko]

Source: rear
Version: 1.19+dfsg-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Builds of rear in minimal environments geared for building only the
architecture-dependent rear binary package (as on the autobuilders)
have been failing:

  asciidoc -b docbook -d manpage rear.8.adoc
  make[3]: asciidoc: Command not found
  Makefile:34: recipe for target 'rear.8.xml' failed
  make[3]: *** [rear.8.xml] Error 127
  make[3]: Leaving directory '/«BUILDDIR»/rear-1.19+dfsg/doc'
  Makefile:90: recipe for target 'man' failed
  make[2]: *** [man] Error 2
  make[2]: Leaving directory '/«BUILDDIR»/rear-1.19+dfsg'
  debian/rules:13: recipe for target 'override_dh_auto_build-arch' failed
  make[1]: *** [override_dh_auto_build-arch] Error 2
  make[1]: Leaving directory '/«BUILDDIR»/rear-1.19+dfsg'
  debian/rules:5: recipe for target 'build-arch' failed
  make: *** [build-arch] Error 2

Please move asciidoc from Build-Depends-Indep to Build-Depends, since
the man page (correctly) goes in the main rear package.

Thanks!

FTR, I'm reporting this bug as a regression because it would affect binNMUs.

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

Bug#849302: battery-graph: off-by-one error in date label

[gregor herrmann]

Package: battery-stats
Version: 0.5.6-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

When I run battery-graph, I get a nice plot which ends in 04:30 26 Dec
which is one day in the future compared to my usual datetime sources.

battery-log ends with 1482637148, i.e. "Sun Dec 25 04:39:08 CET 2016",
which matches my experiences.


Cheers,
gregor

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

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

Versions of packages battery-stats depends on:
ii  gzip   1.6-5
ii  logrotate  3.8.7-2

Versions of packages battery-stats recommends:
pn  gnuplot
pn  libtext-csv-perl   
ii  python 2.7.13-1
ii  python-matplotlib  2.0.0~rc2-1

battery-stats suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlhfP9RfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgb/Mw//TP5/C5IS5KxMHvNZHMypxvFmiELmbZeISv6Gc/d40OZtayWeG9LHQybo
6FmlJRYDQ9uWj06SW4y6azTwnUt6rJrxhR8VdpnMmxTzA4qABvcfZ4qqnGkZ9DQM
SudrsGAEzkcj1q1qimWCBJps4/h2rrwynhC0tCXW099iksHYooa+rQqknK33M7Df
qC1Le4uCiNvigyZn11XUrPyswipPgh/0jD7fta6EGpbrAhsKN3x1qCJHwBQsEN2I
QFg+mF92uRU3j8t1SNe9793zTf+jS56Wu3dApvjX/IsNmdi942aKRfiwgTpuvDjl
GqL5p6w4KHF2Q3uPwT0GBDWYdx37eikecSstDfEj7mJUjGbcX1nSLYG2fSmXHn6B
62AXdrO/EVjlJFQZSvRjZpAKcKA4YrpWknwJUZ30Yu3V7p+7c1pvwI2djxJPPEmt
hws3XJpWvISFocKkKTH704DOglHyD3uqxEaSWWcYn6mmng6y/Kx7dppqBpnDBUEG
acCBGN2AoQJ2KpsFZFEMGAMrCEJaSu+eepWT4o6jhfsAtVM9ymp5IjlJZX4L+Jql
XxNRkoIkQkoK+VB0IyWB2mzeRj720SpjCrR9+e1yaPIU6S0rXTLz0+oZ9JfgY2Yr
zXyk/Lfzlho8tHrF3FOQeb3rCorzecFEpVDnabNin4xukOHpXA4=
=O9RZ
-END PGP SIGNATURE-

Bug#832941: RFS: 4pane (debian: to exclusive)

[Paul Wise]

On Sun, Dec 25, 2016 at 3:53 AM, David Hart wrote:

> However will it be accepted into debian? The project is moribund: apart from a
> single commit 3 years ago, it's been unmaintained for 6 years. That was
> supposed to give time for a rewrite which hasn't happened.

I might be a good idea for 4pane upstream to switch to a long-term
maintained build system like autotools/cmake or something new-fangled
like bazel.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#817602: olpc-xo1: Removal of debhelper compat 4

[Paul Wise]

On Sun, Dec 25, 2016 at 10:38 AM, Andres Salomon wrote:

> Thanks for the patch.  Given that OLPC isn't really alive any more,
> I'm thinking the OLPC packages should probably just be removed from the
> archive for Stretch.  Popcon shows exactly 1 installation of this
> package.. https://qa.debian.org/popcon.php?package=olpc-xo1

I think you will find that OLPC is still active and recently made a release:

http://lists.laptop.org/pipermail/devel/2016-December/thread.html

They also have a Debian derivative:

https://wiki.debian.org/Derivatives/Census/OLPC

I've asked James to respond to your mail.

I expect most OLPC XO1 devices exist in offline mode and couldn't
submit to popcon even if they were configured to.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#849301: qtwebengine-opensource-src: bad VCS links in debian/control

[Boyuan Yang]

Source: qtwebengine-opensource-src
Severity: wishlist
Version: 5.7.1+dfsg-1

Hi,

The VCS link is broken.

Currently: https://anonscm.debian.org/cgit/pkg-kde/qt/qt5webengine.git
Correct one: https://anonscm.debian.org/git/pkg-kde/qt/qtwebengine.git

(Perhaps we should rename cgit -> git in case Debian move away from cgit in 
the future.)

P.S. Making another upload may make the package miss the deadline 2016-01-05, 
so maybe we should either update it after the package enter testing, or ask 
the release team for an immediate testing transition? I'm not quite sure about 
it, but this problem should be put into consideration.

--
Sincerely,
Boyuan Yang

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

Bug#817602: olpc-xo1: Removal of debhelper compat 4

[Andres Salomon]

On Sat, 24 Dec 2016 20:26:06 -0500
Logan Rosen  wrote:

> Control: tags -1 patch
> 
> Dear Maintainer,
> 
> In Ubuntu, the attached patch was applied to achieve the following:
> 
>   * debian/compat: Bump to 10.
>   * debian/control:
> - Build-depend on debhelper (>= 10).
> - Depend on ${misc:Depends}.
> 
> Thanks for considering the patch.
> 
> Logan Rosen


Thanks for the patch.  Given that OLPC isn't really alive any more,
I'm thinking the OLPC packages should probably just be removed from the
archive for Stretch.  Popcon shows exactly 1 installation of this
package.. https://qa.debian.org/popcon.php?package=olpc-xo1

Bug#817639: python-tcpwrap: Removal of debhelper compat 4

[Logan Rosen]

Control: tags -1 patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * debian/compat: Bump to 10.
  * debian/control: Build-depend on debhelper (>= 10) and dh-python.
  * debian/rules: Use dh_prep instead of dh_clean -k.

Thanks for considering the patch.

Logan Rosen
diff -u python-tcpwrap-0.2/debian/compat python-tcpwrap-0.2/debian/compat
--- python-tcpwrap-0.2/debian/compat
+++ python-tcpwrap-0.2/debian/compat
@@ -1 +1 @@
-4
+10
diff -u python-tcpwrap-0.2/debian/rules python-tcpwrap-0.2/debian/rules
--- python-tcpwrap-0.2/debian/rules
+++ python-tcpwrap-0.2/debian/rules
@@ -27,13 +27,13 @@
 install-indep:
 	dh_testdir
 	dh_testroot
-	dh_clean -k -i
+	dh_prep
 	dh_installdirs -i
 
 install-arch: build-arch
 	dh_testdir
 	dh_testroot
-	dh_clean -k -s
+	dh_prep
 	dh_installdirs -s
 	set -e; \
 	for v in $(PYVERS); do \
diff -u python-tcpwrap-0.2/debian/control python-tcpwrap-0.2/debian/control
--- python-tcpwrap-0.2/debian/control
+++ python-tcpwrap-0.2/debian/control
@@ -2,7 +2,7 @@
 Section: python
 Priority: optional
 Maintainer: Brian Sutherland 
-Build-Depends: debhelper (>= 5.0.37.2), python-all-dev (>= 2.6.6-3~), libwrap0-dev
+Build-Depends: debhelper (>= 10), python-all-dev (>= 2.6.6-3~), libwrap0-dev, dh-python
 Standards-Version: 3.6.1
 
 Package: python-tcpwrap

Bug#848076: openconnect 7.07 fails to connect to latest Pulse / Juniper VPN

[Hillel Lubman]

On Sat, 24 Dec 2016 11:11:58 -0800 Mike Miller wrote:
> Can you please test with 7.08-1 which will be available in the archive
> soon? Does 7.08-1 fix the problem you were having with 7.07-1?

I just tested it with 7.08-1 from unstable, and it fixes the problem.

Thanks!
Hillel.

Bug#849300: usbguard-applet-qt: applet icon doesn't show up in cinnamon

[Christoph Anton Mitterer]

Package: usbguard-applet-qt
Version: 0.6.2+ds1-1
Severity: normal


Hi.

With the new autostart .desktop file, the usbguard applet still
doesn't show up in cinnamon's systray - it is however running
and the dialogs when a USB device are inserted show up.

This may very well be a bug in cinnamon itself (which seems to have
quite some issues with regards to systray icons).
Even if, it's unlikely that this is going to be fixed anytime soon...

A workaround for me seemed to be setting a delay in the startup,
which works with e.g.:
X-GNOME-Autostart-Delay=5
(for 5 secs delay)

Since the actual usbguard daemon is still running, this wouldn't have
anysecurity implications.


Cheers,
Chris.

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

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

Versions of packages usbguard-applet-qt depends on:
ii  libc6   2.24-8
ii  libgcc1 1:6.2.1-7
ii  libqt5core5a5.7.1+dfsg-1
ii  libqt5gui5  5.7.1+dfsg-1
ii  libqt5svg5  5.7.1~20161021-2
ii  libqt5widgets5  5.7.1+dfsg-1
ii  libstdc++6  6.2.1-7
ii  libusbguard00.6.2+ds1-1
ii  usbguard0.6.2+ds1-1

usbguard-applet-qt recommends no packages.

usbguard-applet-qt suggests no packages.

-- no debconf information

Bug#817619: piwi: Removal of debhelper compat 4

[Logan Rosen]

Package: piwi
Version: 0.8+20041206-3
Followup-For: Bug #817619
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu zesty ubuntu-patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * debian/compat: Bump to 10.
  * debian/control:
- Build-depend on debhelper (>= 10).
- Depend on ${misc:Depends}.
  * debian/rules:
- Use dh_prep instead of dh_clean -k.
- Add recommended build-arch and build-indep targets.

Thanks for considering the patch.

Logan Rosen
diff -u piwi-0.8+20041206/debian/compat piwi-0.8+20041206/debian/compat
--- piwi-0.8+20041206/debian/compat
+++ piwi-0.8+20041206/debian/compat
@@ -1 +1 @@
-4
+10
diff -u piwi-0.8+20041206/debian/rules piwi-0.8+20041206/debian/rules
--- piwi-0.8+20041206/debian/rules
+++ piwi-0.8+20041206/debian/rules
@@ -28,7 +28,9 @@
 	touch configure-stamp
 
 
-build: build-stamp
+build: build-arch build-indep
+build-arch: build-stamp
+build-indep: build-stamp
 
 build-stamp: configure-stamp 
 	dh_testdir
@@ -52,7 +54,7 @@
 install: build
 	dh_testdir
 	dh_testroot
-	dh_clean -k 
+	dh_prep
 	dh_installdirs
 	dh_install 
 
diff -u piwi-0.8+20041206/debian/control piwi-0.8+20041206/debian/control
--- piwi-0.8+20041206/debian/control
+++ piwi-0.8+20041206/debian/control
@@ -2,12 +2,12 @@
 Section: admin
 Priority: optional
 Maintainer: Mickael Profeta 
-Build-Depends-Indep: debhelper (>= 4.0.0)
+Build-Depends: debhelper (>= 10)
 Standards-Version: 3.6.1.0
 
 Package: piwi
 Architecture: all
-Depends: ${perl:Depends}, apache | apache-ssl | apache-perl | httpd, mysql-client | postgresql-client, libapache-dbi-perl, libdbd-mysql-perl| libdbd-pg-perl, libdate-calc-perl
+Depends: ${misc:Depends}, ${perl:Depends}, apache | apache-ssl | apache-perl | httpd, mysql-client | postgresql-client, libapache-dbi-perl, libdbd-mysql-perl| libdbd-pg-perl, libdate-calc-perl
 Suggests:  libgd-gd2-perl, geoip-bin
 Description: P(erl|relude) IDS Web Interface - A frontend to your Prelude database
  Providing a complete web front-end for the Prelude-Intrusion Detection System

Bug#817602: olpc-xo1: Removal of debhelper compat 4

[Logan Rosen]

Control: tags -1 patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * debian/compat: Bump to 10.
  * debian/control:
- Build-depend on debhelper (>= 10).
- Depend on ${misc:Depends}.

Thanks for considering the patch.

Logan Rosen
diff -Nru olpc-xo1-0.3/debian/compat olpc-xo1-0.3ubuntu1/debian/compat
--- olpc-xo1-0.3/debian/compat	2009-02-15 16:37:40.0 -0500
+++ olpc-xo1-0.3ubuntu1/debian/compat	2016-12-24 20:18:25.0 -0500
@@ -1 +1 @@
-4
+10
diff -Nru olpc-xo1-0.3/debian/control olpc-xo1-0.3ubuntu1/debian/control
--- olpc-xo1-0.3/debian/control	2009-02-15 16:43:07.0 -0500
+++ olpc-xo1-0.3ubuntu1/debian/control	2016-12-24 20:18:47.0 -0500
@@ -2,11 +2,12 @@
 Section: admin
 Priority: extra
 Maintainer: Andres Salomon 
-Build-Depends: debhelper (>= 4.1.0), cdbs
+Build-Depends: debhelper (>= 10), cdbs
 Standards-Version: 3.8.0
 
 Package: olpc-xo1-hw
 Architecture: all
+Depends: ${misc:Depends}
 Description: Support for OLPC XO-1 hardware
  This package contains necessary scripts and other things to support OLPC's
  XO-1 hardware.  This hardware is a mix between a laptop and an embedded

Bug#830424: eficas: FTBFS: dh_listpackages: Compatibility levels before 5 are no longer supported (level 1 requested)

[Logan Rosen]

Control: tags -1 patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * debian/compat: Indicate compatibility level of 10.
  * debian/control: Build-depend on debhelper (>= 10) and dh-python.
  * debian/eficas.install: Remove executable bit.

Thanks for considering the patch.

Logan Rosen
diff -Nru eficas-6.4.0-1/debian/compat eficas-6.4.0-1/debian/compat
--- eficas-6.4.0-1/debian/compat	1969-12-31 19:00:00.0 -0500
+++ eficas-6.4.0-1/debian/compat	2016-12-24 20:08:55.0 -0500
@@ -0,0 +1 @@
+10
diff -Nru eficas-6.4.0-1/debian/control eficas-6.4.0-1/debian/control
--- eficas-6.4.0-1/debian/control	2012-04-29 04:40:03.0 -0400
+++ eficas-6.4.0-1/debian/control	2016-12-24 20:09:08.0 -0500
@@ -3,9 +3,9 @@
 Priority: optional
 Maintainer: Debian Science Team 
 Uploaders: Christophe Trophime 
-Build-Depends: debhelper (>= 5.0.38), cdbs (>= 0.4.90~), 
+Build-Depends: debhelper (>= 10), cdbs (>= 0.4.90~), 
  python-all (>= 2.6.6-3~), python-qt4-dev, quilt,
- python-openturns
+ python-openturns, dh-python
 Standards-Version: 3.9.3
 X-Python-Version: all
 Homepage: http://www.code-aster.org/

Bug#848761: ovito: FTBFS: Test failures, now fixed upstream

[Ghislain Vaillant]

On Fri, 23 Dec 2016 19:28:09 + Ghislain Vaillant  wrote:
> I have forwarded the issue upstream with a build log on the latest
> upstream version done on debomatic.

Alright, upstream claims the issue is fixed on `master`. I intend to
cherry-pick the fix onto 2.8.1, unless upstream decides to release a
new version as suggested.

Ghis

Bug#844055: Doesn't support conversion of images with dimensions of 256x256 or greater.

[Paul Wise]

FYI, I've uploaded your openjpeg2 branch as an NMU.

After the holiday season I will look into properly sorting the rest out.

Some comments:

The GCC warning fix silences GCC but doesn't fix the portability issues
with the code that it changes, since there can be platforms with floats
that are not 32-bit IEEE float format.

The separate copyright file were on purpose since the different binary
packages have different licenses, it would be better to update them.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#849299: Maybe only print Time has been changed log message once

[積丹尼 Dan Jacobson]

Package: systemd
Version: 232-7
Severity: wishlist

Maybe only print Time has been changed log message once
12月 25 08:24:48 jidanni3 ntpd[2504]: Soliciting pool server 
2001:b030:131b:ff00::1
12月 25 08:23:52 jidanni3 systemd[1146]: Time has been changed
12月 25 08:23:52 jidanni3 systemd[1]: Time has been changed

Bug#849284: insserv: fopen(/etc/insserv.conf): No such file or directory

[積丹尼 Dan Jacobson]

First I installed a fresh Debian testing system from a USB stick.
The stick was only 300 MB big and only needed to go online to get the
current time to set the clock.
Then I installed aptitude.
Then I installed the rest of the packages by
# aptitude install package1 package2 ... package777
My point is there are many different orders one could install packages,
all legal, and it would be good to do some checks in order not to
have the administrator see these warnings.

Bug#849294: python-apt: aptsources.sourceslist ignores sources.list.d/*.sources files

[Julian Andres Klode]

Control: severity -1 wishlist

On Sat, Dec 24, 2016 at 08:21:58PM +0100, Paul Gevers wrote:
> Package: python-apt
> Version: 1.1.0~beta5
> Severity: important
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> I noticed that aptsources.sourceslist doesn't take the content of 
> souces.list.d
> sources files into account.

That's true. aptsources does not support the deb822 file format and there
are no plans to add that for the foreseeable future. Details:

(1) In fact, there is no way to add support for the format. The format is too
expressive to be able to be express the data in the current API, requiring
an API break.

=> Adding support for it means breaking existing applications even more
then they are now. (or well, we'd have to introduce an aptsources2 module
or a function to switch to a new API, but that is all fairly awkward).

(2) The code is unmaintained. In fact, most of it was not written by anyone
on the APT team but by Michiel Sikkes and Sebastian Heinlein both of which
are not involved anymore.

The whole parsing needs to be moved up a level into apt-pkg really, and then
we could have code in there.

If you want to use the aptsources module or a software based on it,
I can only advise you not to use the deb822 format.

Given the complexity of the issue at hand and no chance for a solution in
the foreseeable future, I'm downgrading this to wishlist, according to its
description: "[for any feature request, and also] for any bugs that are very
difficult to fix due to major design considerations."

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

Bug#808915: util-linux: dmesg fails with dmesg: read kernel buffer failed: Operation not permitted

[shirish शिरीष]

Hi all,

I got this when trying to run dmesg for info. on a bug -

/home/shirish 16-12-25 4:26:20 $ dmesg > dmesg.txt
dmesg: read kernel buffer failed: Operation not permitted

Then I did -

$ cat /proc/sys/kernel/unprivileged_userns_clone
0

which confirmed that unprivileed people cannot use this.

Then I used the option shared -

$ sudo su -c 'echo 1> /proc/sys/kernel/unprivileged_userns_clone'
[sudo] password for shirish:
bash: line 0: echo: write error: Invalid argument

Should I make a new bug ?

-- 
  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#849298: libconfig-inifiles-perl: Infinite loop when "each" is used

[Johannes Schauer]

Package: libconfig-inifiles-perl
Version: 2.94-1
Severity: normal

Hi,

suppose the following code which seems normal for processing the module
as a tied hash:

use Config::IniFiles;
tie (my %ini, 'Config::IniFiles', -file=>"test.ini");
foreach my $s (keys %ini) {
while (my ($k,$v) = each %{$ini{$s}}) {
print("$s $k $v\n");
}
}

Try it on the following trivial config file:

[foo]
bar=baz

The result will be an infinite loop printing "foo bar baz".

This is especially frustrating, because the docs list explicitly that a
statement like the following should work:

while (($k, $v) = each %{$ini{$section}}) {...}

Thanks!

cheers, josch

Bug#848826: More info. on vainfo

[shirish शिरीष]

in-line  :-

On 24/12/2016, Sebastian Ramacher  wrote:
> Hi

Hi,

> On 2016-12-23 15:43:10, shirish शिरीष wrote:



>> (+) Video --vid=1 (*) (h264)
>>  (+) Audio --aid=1 --alang=und (*) (aac)
>> [vo/opengl] GLX not found.
>> [vo/opengl] GLX not found.
>
> I suppose your issues start here already. Please provide a X.org log and
> dmesg.
>
> Cheers

Warning - Longish mail (a bit)

Have provided Xorg.0.log from /var/log/X.org.0.log

While I'm able to figure out and troubleshoot some parts and able to
play the videos without the warnings. What had happened was -

a. For some reason nvidia-* packages had occupied center-stage along
with Intel. It took me sometime to realize that maybe because some
laptops which are available today are 'hybrid' laptops which have both
intel and nvidia graphics hence nvidia which usually had a
breaks/replaces against intel was not there.

How it came to be, I'm clueless still.

b. I removed all instances of any nvidia package except for
nvidia-installer-cleanup which depends on glx-diversions.

c. Then rebooted the system and found it was flashing the monitor.

d. Then rebooted into single user mode, found out mesa-vdpau-drivers
was not installed, As I was in single-user-mode/recovery-mode had to
take a usb disk, download mesa-vdpau-drivers, copied it to this
machine and installed it via dpkg.

e. Rebooted again and this time got the login page, saw couple of
videos, the complain was no longer in the videos.

So while on Xorg.0.log shouldn't have anything untoward now -

I did see something Very strange on the dmesg front

/home/shirish $ dmesg
dmesg: read kernel buffer failed: Operation not permitted

I was forced to become root and then was able to share dmesg.txt

> --
> Sebastian Ramacher
>

-- 
  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
[0.00] 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)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.8.0-2-amd64 
root=UUID=aaafd0a1-62db-4216-80be-cf0dc016ac7c ro initrd=/install/initrd.gz 
ipv6.disable=1 init=/lib/systemd/systemd
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, 
using 'standard' format.
[0.00] x86/fpu: Using 'eager' FPU context switches.
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009cfff] usable
[0.00] BIOS-e820: [mem 0x0009d000-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000e-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0xae21dfff] usable
[0.00] BIOS-e820: [mem 0xae21e000-0xbcd3efff] reserved
[0.00] BIOS-e820: [mem 0xbcd3f000-0xbce7efff] ACPI NVS
[0.00] BIOS-e820: [mem 0xbce7f000-0xbcefefff] ACPI data
[0.00] BIOS-e820: [mem 0xbceff000-0xbf9f] reserved
[0.00] BIOS-e820: [mem 0xf800-0xfbff] reserved
[0.00] BIOS-e820: [mem 0xfe101000-0xfe112fff] reserved
[0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved
[0.00] BIOS-e820: [mem 0xfed08000-0xfed08fff] reserved
[0.00] BIOS-e820: [mem 0xfed1-0xfed19fff] reserved
[0.00] BIOS-e820: [mem 0xfed1c000-0xfed1] reserved
[0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved
[0.00] BIOS-e820: [mem 0xffc0-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x00023e5f] usable
[0.00] NX (Execute Disable) protection: active
[0.00] SMBIOS 2.7 present.
[0.00] DMI: LENOVO 20B7A1SD00/20B7A1SD00, BIOS GJET79WW (2.29 ) 
09/03/2014
[0.00] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.00] e820: remove [mem 0x000a-0x000f] usable
[0.00] e820: last_pfn = 0x23e600 max_arch_pfn = 0x4
[0.00] MTRR default type: write-back
[0.00] MTRR fixed ranges enabled:
[0.00]   0-9 write-back
[0.00]   A-B uncachable
[0.00]   C-F write-protect
[0.00] MTRR variable ranges enabled:
[0.00]   0 base 00C000 mask 7FC000 uncachable
[0.00]   1 base 00BE00 mask 7FFE00 uncachable
[

Bug#849297: /usr/lib/x86_64-linux-gnu/libSDL2-2.0.so: broken symbolic link

[Ben Longbons]

Package: libsdl2-dev
Version: 2.0.5+dfsg1-1
Severity: normal
File: /usr/lib/x86_64-linux-gnu/libSDL2-2.0.so

Dear Maintainer,

I'm not sure who (if anyone) wants -lSDL2-2.0 rather than -lSDL2 (which is
what pkg-config and sdl2-config give), but the link is broken for them.

libSDL2-2.0.so -> libSDL2-2.0.so.0.4.0
libSDL2.so -> libSDL2-2.0.so.0.4.1

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

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

Versions of packages libsdl2-dev depends on:
ii  libasound2-dev 1.1.2-1
ii  libdbus-1-dev  1.10.14-1
ii  libegl1-mesa-dev   13.0.2-3
ii  libgl1-mesa-dev13.0.2-3
ii  libgles2-mesa-dev  13.0.2-3
ii  libglu1-mesa-dev   9.0.0-2.1
ii  libibus-1.0-dev1.5.14-2
ii  libpulse-dev   9.0-5
ii  libsdl2-2.0-0  2.0.5+dfsg1-1
ii  libsndio-dev   1.1.0-3
ii  libudev-dev232-8
ii  libwayland-dev 1.12.0-1
ii  libx11-dev 2:1.6.4-2
ii  libxcursor-dev 1:1.1.14-1+b1
ii  libxext-dev2:1.3.3-1
ii  libxi-dev  2:1.7.8-1
ii  libxinerama-dev2:1.1.3-1+b1
ii  libxkbcommon-dev   0.7.0-1
ii  libxrandr-dev  2:1.5.1-1
ii  libxss-dev 1:1.2.2-1
ii  libxt-dev  1:1.1.5-1
ii  libxv-dev  2:1.0.11-1
ii  libxxf86vm-dev 1:1.1.4-1

libsdl2-dev recommends no packages.

libsdl2-dev suggests no packages.

-- no debconf information

Bug#848551: f2fs-tools: please make an udeb

[Adam Borowski]

On Sat, Dec 24, 2016 at 04:17:52AM -0800, Vincent Cheng wrote:
> On Sun, Dec 18, 2016 at 3:05 AM, Adam Borowski  wrote:
> > Adding d-i support, besides adding a menu item that's simple for a
> > single-device filesystem, requires having an udeb with at least mkfs, other
> > tools also being nice to have in case the user needs to troubleshoot during
> > the installation.
> >
> > Thus, would you care creating such an udeb?  Apologies for waking up that
> > late, it'd need to pass NEW no later than Xmas.
> 
> I have no time to work on this before the NEW freeze, but feel free to
> NMU to have src:f2fs-tools build a udeb package, and whatever else is
> required for d-i support.

Here's my first stab.

The list of included files, and generated dependencies look right, but the
udeb is _not_ yet tested inside d-i.  I'm uploading now to have a chance of
passing NEW.

I'll then prepare proper patches for d-i -- if it turns out there's
something that needs fixing in f2fs-tools, it'll be obviously my
responsibility.

Debdiff attached.


Meow!
-- 
Autotools hint: to do a zx-spectrum build on a pdp11 host, type:
  ./configure --host=zx-spectrum --build=pdp11
diff -Nru f2fs-tools-1.7.0/debian/changelog f2fs-tools-1.7.0/debian/changelog
--- f2fs-tools-1.7.0/debian/changelog   2016-09-02 08:47:51.0 +0200
+++ f2fs-tools-1.7.0/debian/changelog   2016-12-24 22:54:41.0 +0100
@@ -1,3 +1,10 @@
+f2fs-tools (1.7.0-1.1) unstable; urgency=medium
+
+  * NMU with permission.
+  * Make an udeb. (Closes: #848551)
+
+ -- Adam Borowski   Sat, 24 Dec 2016 22:54:41 +0100
+
 f2fs-tools (1.7.0-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru f2fs-tools-1.7.0/debian/control f2fs-tools-1.7.0/debian/control
--- f2fs-tools-1.7.0/debian/control 2016-09-02 08:47:51.0 +0200
+++ f2fs-tools-1.7.0/debian/control 2016-12-24 22:54:37.0 +0100
@@ -62,3 +62,10 @@
  System (LFS).
  .
  This package contains the development files.
+
+Package: f2fs-tools-udeb
+Package-Type: udeb
+Section: debian-installer
+Architecture: linux-any
+Depends: ${misc:Depends}, ${shlibs:Depends}
+Description: Tools for Flash-Friendly File System (udeb)
diff -Nru f2fs-tools-1.7.0/debian/f2fs-tools-udeb.install 
f2fs-tools-1.7.0/debian/f2fs-tools-udeb.install
--- f2fs-tools-1.7.0/debian/f2fs-tools-udeb.install 1970-01-01 
01:00:00.0 +0100
+++ f2fs-tools-1.7.0/debian/f2fs-tools-udeb.install 2016-12-24 
22:54:41.0 +0100
@@ -0,0 +1,2 @@
+/sbin
+/lib/*/libf2fs.so*
diff -Nru f2fs-tools-1.7.0/debian/rules f2fs-tools-1.7.0/debian/rules
--- f2fs-tools-1.7.0/debian/rules   2015-12-22 10:04:01.0 +0100
+++ f2fs-tools-1.7.0/debian/rules   2016-12-24 22:54:41.0 +0100
@@ -20,3 +20,7 @@
 get-orig-source:
wget 
http://git.kernel.org/cgit/linux/kernel/git/jaegeuk/f2fs-tools.git/snapshot/f2fs-tools-$(DEB_UPSTREAM_VERSION).tar.xz
mv f2fs-tools-$(DEB_UPSTREAM_VERSION).tar.xz 
f2fs-tools_$(DEB_UPSTREAM_VERSION).orig.tar.xz
+
+override_dh_shlibdeps:
+   dh_shlibdeps -a -p f2fs-tools-udeb -- -xlibf2fs0
+   dh_shlibdeps -a -N f2fs-tools-udeb

Bug#817461: freepwing: Removal of debhelper compat 4

[Logan Rosen]

Control: tags -1 patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * debian/compat: Bump to 10.
  * debian/control: Build-depend on debhelper (>= 10).

Thanks for considering the patch.

Logan Rosen
diff -u freepwing-1.5/debian/compat freepwing-1.5/debian/compat
--- freepwing-1.5/debian/compat
+++ freepwing-1.5/debian/compat
@@ -1 +1 @@
-4
+10
diff -u freepwing-1.5/debian/control freepwing-1.5/debian/control
--- freepwing-1.5/debian/control
+++ freepwing-1.5/debian/control
@@ -2,7 +2,7 @@
 Section: utils
 Priority: optional
 Maintainer: Masayuki Hatta (mhatta) 
-Build-Depends: debhelper (>= 4.0.0), perl
+Build-Depends: debhelper (>= 10), perl
 Standards-Version: 3.8.0
 
 Package: freepwing

Bug#825487: [Piuparts-devel] Bug#825487: Bug#825487: Patch

[Sean Whitton]

control: tag -1 +patch

Hello Holger, Andreas,

New patch attached.

I'm not totally sure about the version number comparison code, because
LooseVersion doesn't understand things like "~beta2".  However, it gives
the right answer for the versions of apt in all current Debian suites.

-- 
Sean Whitton
From 2e4bf077af395829898a34bde9aa4eb967d6cc28 Mon Sep 17 00:00:00 2001
From: Sean Whitton 
Date: Sat, 24 Dec 2016 21:51:56 +
Subject: [PATCH] use apt-get install /tmp/foo.deb

---
 debian/changelog |  8 
 piuparts.py  | 55 +++
 2 files changed, 51 insertions(+), 12 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 9cb1565..6534322 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+piuparts (0.74) UNRELEASED; urgency=medium
+
+  * piuparts.py: use `apt-get install ./foo.deb` instead of `dpkg -i
+./foo.deb && apt-get install -yf` for more reliable dependency
+resolution (Closes: #825487).
+
+ -- Sean Whitton   Sat, 24 Dec 2016 21:50:21 +
+
 piuparts (0.73) unstable; urgency=medium
 
   * Add new option, --hard-link, and do *not* use it by default.
diff --git a/piuparts.py b/piuparts.py
index dbf2b18..06d7901 100644
--- a/piuparts.py
+++ b/piuparts.py
@@ -52,6 +52,7 @@ import subprocess
 import urllib
 import uuid
 from collections import namedtuple
+from distutils.version import LooseVersion
 from signal import alarm, signal, SIGALRM, SIGTERM, SIGKILL
 
 try:
@@ -1162,14 +1163,39 @@ class Chroot:
 self.install_packages_by_name(packages, with_scripts=with_scripts)
 return
 if package_files:
+# We need an absolute path here so that apt-get can
+# distinguish our deb from a request to install a package
+# from a suite called 'tmp'
 self.copy_files(package_files, "tmp")
 tmp_files = [os.path.basename(a) for a in package_files]
-tmp_files = [os.path.join("tmp", name) for name in tmp_files]
+tmp_files = [os.path.join("/tmp", name) for name in tmp_files]
+
+# Check whether apt can install debs
+#
+# If it can, this is preferable to the traditional `dpkg
+# -i foo.deb && apt-get install -yf` approach:
+#
+# - the traditional approach can 'resolve' the dependency
+#   by removing the package we are trying to install
+#
+# - the new approach successfully handles simultaneously
+#   installing a new binary package and its transitional
+#   dummy package
+(status, output) = run(["dpkg-query", "-f", "${Version}\n", "-W", "apt"], ignore_errors=True)
+apt_can_install_debs = LooseVersion(output.strip()) >= LooseVersion("1.1")
 
 if with_scripts:
 self.run_scripts("pre_install")
 
-apt_get_install = ["apt-get", "-yf"]
+if apt_can_install_debs:
+# --allow-downgrades is required in order to permit
+# installing a deb with the same version as that
+# already installed, which we need to do at various
+# points in piuparts testing
+apt_get_install = ["apt-get", "-y", "--allow-downgrades"]
+else:
+apt_get_install = ["apt-get", "-yf"]
+
 apt_get_install.extend(settings.distro_config.get_target_flags(
 os.environ["PIUPARTS_DISTRIBUTION"]))
 apt_get_install.append("install")
@@ -1177,18 +1203,23 @@ class Chroot:
 if settings.list_installed_files:
 pre_info = self.save_meta_data()
 
-(ret, out) = self.run(["dpkg", "-i"] + tmp_files, ignore_errors=True)
-if ret != 0:
-if "dependency problems - leaving unconfigured" in out:
-pass
-else:
-logging.error("Installation failed")
-panic()
+if apt_can_install_debs:
+self.run(apt_get_install + tmp_files)
+else:
+logging.info("apt too old; falling back to dpkg -i && apt-get install -yf")
 
-if settings.list_installed_files:
-self.list_installed_files(pre_info, self.save_meta_data())
+(ret, out) = self.run(["dpkg", "-i"] + tmp_files, ignore_errors=True)
+if ret != 0:
+if "dependency problems - leaving unconfigured" in out:
+pass
+else:
+logging.error("Installation failed")
+panic()
+
+if settings.list_installed_files:
+self.list_installed_files(pre_info, self.save_meta_data())
 
-self.run(apt_get_install)
+self.run(apt_get_install)
 

Bug#849142: [PATCH] Update dex_expected_diffs and test requirement to ensure test compatibility with enjarify >= 1.0.3. (Closes: #849142)

[Chris Lamb]

Daniel Shahaf wrote:

> > +if subprocess.call(
> > +('python3', '-c', 'import enjarify.typeinference'),
> 
> Use sys.executable instead of hardcoding 'python3', to handle the case
> that there's more than one python3 binary on the system?

I deliberately used python3 to match the behaviour of what the
/usr/bin/enjarify script does.

Besides, sys.executable could be the virtualenv's python which we don't
want to call :)


Regards,

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

Bug#811887: duma: FTBFS with GCC 6: declaration of ... has a different exception specifier

[Logan Rosen]

Control: tags -1 patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * dumapp.{cpp,h}: Apply patch from Buildroot (thanks, Yann E. MORIN!) to fix
FTBFS with C++14.

Thanks for considering the patch. It was found here:
https://github.com/maximeh/buildroot/blob/master/package/duma/0003-fix-C%2B%2B14.patch

Logan Rosen
--- duma-2.5.15.orig/dumapp.cpp
+++ duma-2.5.15/dumapp.cpp
@@ -190,7 +190,9 @@
  * (11) = (a) ; ASW
  */
 void * DUMA_CDECL operator new( DUMA_SIZE_T size )
+#ifdef DUMA_EXCEPTION_SPECS
 throw(std::bad_alloc)
+#endif
 {
   return duma_new_operator(size, EFA_NEW_ELEM, true  DUMA_PARAMS_UK);
 }
@@ -254,7 +256,9 @@
  * (21) = (a) ; AAW
  */
 void * DUMA_CDECL operator new[]( DUMA_SIZE_T size )
+#ifdef DUMA_EXCEPTION_SPECS
 throw(std::bad_alloc)
+#endif
 {
   return duma_new_operator(size, EFA_NEW_ARRAY, true  DUMA_PARAMS_UK);
 }
--- duma-2.5.15.orig/dumapp.h
+++ duma-2.5.15/dumapp.h
@@ -35,6 +35,10 @@
 
 #include "duma.h"
 
+#if __cplusplus < 201103L
+  #define DUMA_EXCEPTION_SPECS 1
+#endif
+
 /* remove previous macro definitions */
 #include "noduma.h"
 

Bug#848403: diffoscope: FTBFS randomly (Fatal Python error: deallocating None)

[Ximin Luo]

Chris Lamb:
> Ximin Luo wrote:
> 
>> I still haven't managed to reproduce this myself but I'll just note
>> for the record we have seen this on jenkins before
> 
> My guess is that one of the third-party Python extension modules that
> we import does not correctly reference count Py_None. Someone did a
> good writeup here:
> 
>   http://stackoverflow.com/a/15288194
> 
> Now, we just need to narrow down which one… and then fix it.  >.>
> 

For all you people that already have single-CPU KVM VMs set up, can you please 
try to reduce your test cases that still reproduce the bug?

For example, can you still reproduce it with `debian/rules clean build`? What 
about `python3 -m pytest`? Then, does it reproduce when you start manually 
disabling various tests? What about when running only 1 test case?

X

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Bug#488386: please provide an udeb for laptop-detect

[Philipp Kern]

On 24.12.2016 16:24, Petter Reinholdtsen wrote:
> [Christoph Biedl]
>> Um, Jan 5th (i.e. upload by tomorrow-ish) is about uploads that are
>> NEW or about re-entry. Neither applies for laptop-detect, so deadline
>> is *Feb* 5th minus ten days for migration. Or I misread the message
>> horribly.
> Adding the udeb back to laptop-detect will require NEW processing.

As the referenced mail mentions, this is generally about source
packages. Not speaking for -boot here, but in general terms. Britney
will continue to propagate new binary packages when migrating new
versions to testing. The release team has historically asked for some
updates not to be released from NEW, but that was mostly to avoid
uncoordinated transitions.

Kind regards
Philipp Kern

Bug#849296: libsmbclient-dev: Incorrect version (0.2.1 instead of 4.2.14) in pkgconfig/smbclient.pc

[Konstantin Gribov]

Package: libsmbclient-dev
Version: 2:4.2.14+dfsg-0+deb8u2
Severity: important

Hello, Debian maintainers.

-- Steps to reproduce:
$ apt-get install -y libsmbclient-dev pkg-config
$ pkg-config --cflags --libs 'smbclient >= 4.0'
Requested 'smbclient >= 4.0' but version of smbclient is 0.2.1
You may find new versions of smbclient at http://www.samba.org/
$ pkg-config --modversion smbclient
0.2.1

-- Expected output:
$ pkg-config --cflags --libs 'smbclient >= 4.0'
-I/usr/include/samba-4.0 -lsmbclient
$ pkg-config --modversion smbclient
4.2.14

-- Patch:
--- /usr/lib/x86_64-linux-gnu/pkgconfig/smbclient.pc2016-12-17
20:07:34.0 +
+++ smbclient.pc2016-12-24 22:26:04.517089847 +
@@ -5,7 +5,7 @@

Name: smbclient
Description: A SMB library interface
-Version: 0.2.1
+Version: 4.2.14
Libs:  -L${libdir} -lsmbclient
Cflags: -I${includedir}
URL: http://www.samba.org/

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

Kernel: Linux 4.8.13-1-ARCH (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages libsmbclient-dev depends on:
ii  dpkg  1.17.27
ii  libsmbclient  2:4.2.14+dfsg-0+deb8u2

libsmbclient-dev recommends no packages.

libsmbclient-dev suggests no packages.

-- no debconf information

Additional notes:
- Debian is running in Docker container but it doesn't change anything for
this bug.

-- 

Best regards,
Konstantin Gribov

Bug#846002: blends-tasks must not be priority:important (was Re: Bug#846002: Lowering severity)

[Cyril Brulebois]

Philip Hands  (2016-12-24):
> OK, this is tiresome -- you're complaining about question marks when I
> was still exploring the options and looking for feedback -- I could
> instead have been definite about an earlier option, but that would
> have deprived you of choices, and would not have resulted in a patch
> as good as it is now.
> 
> Please don't punish me for being open about my feelings on the various
> commits because if you do that you'll reap the whirlwind when people
> start lying to you to get past your superficial metrics.

My initial comments weren't about those. But they indeed add up with
what I mentioned earlier, and this tends to confirm that december,
with a freeze already started, is just not the right time to start
exploring options.

Sorry, but my mind is made up here: it's just too late (1) to change
tasksel entirely, (2) to require translation updates we're already not
getting in time, be it for screens, and for the installation guide.

I'll stop repeating myself here, and start enjoying festivities.


KiBi.


signature.asc
Description: Digital signature

Bug#849295: denyhosts with iptables enabled fails to remove entries from iptables

[Rich]

Package: denyhosts
Version: 2.10-2
Severity: normal

Dear Maintainer,

If you have IPTABLES support enabled in denyhosts, then it will happily add
hosts to the iptables DROP rules, but it does not remove those entries when
it garbage collects old blocks from hosts.deny (and friends), leaving them
infinitely accruing.

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

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

Versions of packages denyhosts depends on:
ii  init-system-helpers  1.22
ii  lsb-base 4.1+Debian13+nmu1
ii  python   2.7.9-1
pn  python:any   

denyhosts recommends no packages.

denyhosts suggests no packages.

-- Configuration Files:
/etc/denyhosts.conf [Errno 13] Permission denied: u'/etc/denyhosts.conf'

-- no debconf information

Bug#811655: Patch for Debian bug #811655

[Petter Reinholdtsen]

[Andrea Claudi]
> This simple patch fix the build issue with gcc-6.
> Please, let me know if it needs improvements.

Thank you for the patch.  I just NMUed the package to fix this RC bug
using this patch.

Once the package upload is registered and this bug is closed, the bug
should be reopened and renamed to a NMU patch bug with severity wishlist.

-- 
Happy hacking
Petter Reinholdtsen

Bug#744517: starplot: run dh-autoreconf to update config.{sub,guess} and {libtool,aclocal}.m4

[Petter Reinholdtsen]

[Matthias Klose 2014-04-13]
>   - For other rules files, call dh_autoreconf before calling
> configure (in the build or configure target), and call
> dh_autoreconf_clean before dh_clean in the clean target.

As far as I can see, the d/rules file already uses dh_autoreconf and
dh_autoreconf_clean.  Is this issue already solved?

-- 
Happy hacking
Petter Reinholdtsen

Bug#846002: blends-tasks must not be priority:important (was Re: Bug#846002: Lowering severity)

[Philip Hands]

Cyril Brulebois  writes:

> Raphael Hertzog  (2016-12-24):
>> I would suggest to commit this to git, do a call for translators to
>> update this new translation and then judge on the result to see if you
>> have enough translations to release it for stretch.
>> 
>> I know it's late in the release cycle, but we're not yet in deep
>> freeze and the release team has always accomodated far more invasive
>> changes to debian-installer in the past.
>
> I've already explained why this wasn't a reasonable approach in earlier
> mails over the past few days. I'm fine with asking the release team to
> accomodate for changes which are needed, but those don't qualify. Heck,
> we had obvious syntax issues in bash scripts in earlier commits, plenty
> of question marks

OK, this is tiresome -- you're complaining about question marks when I
was still exploring the options and looking for feedback -- I could
instead have been definite about an earlier option, but that would have
deprived you of choices, and would not have resulted in a patch as good
as it is now.

Please don't punish me for being open about my feelings on the various
commits because if you do that you'll reap the whirlwind when people
start lying to you to get past your superficial metrics.

Cheers, Phil.
-- 
|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
|-|  http://www.hands.com/http://ftp.uk.debian.org/
|(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,GERMANY


signature.asc
Description: PGP signature

Bug#849242: More info

[Nekki Nekki]

Please, check   https://youtu.be/r5VT0kp9JZw for get a better idea
about the bug.
Note that the problem, if autohide is enabled for Tint2, only exists under
Openbox and it only affects Virtualbox.
Cheers,
Nekki

Bug#849228: Correction - more info

[Nekki Nekki]

Please, check   https://youtu.be/r5VT0kp9JZw for get a better idea
about the bug.
As I said the problem, if autohide in enabled for Tint2, only exists under
Openbox and it only affects Virtualbox,
Cheers,
Nekki

2016-12-23 20:53 GMT-05:00 Nekki Nekki :

> Hi!
> I wanted to precise: sorry, the issue isn't present in all DE's/WM's.
> After further investigation,
> I found that the issue I described in bug #844165 is ONLY reproducible
> under OPENBOX window manager.
> I just reported a "basic" bug report about Openbox. Please check bug
> #849242.
> Cheers,
> Nekki
>

Bug#846002: blends-tasks must not be priority:important (was Re: Bug#846002: Lowering severity)

[Cyril Brulebois]

Raphael Hertzog  (2016-12-24):
> I would suggest to commit this to git, do a call for translators to
> update this new translation and then judge on the result to see if you
> have enough translations to release it for stretch.
> 
> I know it's late in the release cycle, but we're not yet in deep
> freeze and the release team has always accomodated far more invasive
> changes to debian-installer in the past.

I've already explained why this wasn't a reasonable approach in earlier
mails over the past few days. I'm fine with asking the release team to
accomodate for changes which are needed, but those don't qualify. Heck,
we had obvious syntax issues in bash scripts in earlier commits, plenty
of question marks, and even Steve didn't understand the resulting code
when trying to get me to rethink my decision a few hours ago.

> But a plain reject at this point with the associated refusal for the
> blends to appear in the list is going to make everybody upset which is
> a pity since we have a rather good compromise here.

The real pity here is that nobody addressed my early comments when there
was plenty of time. Like early this year, plenty of months ago.

See you next release cycle. The earlier, the better.


KiBi.


signature.asc
Description: Digital signature

Bug#829046: pagure dependencies (JavaScript libraries) packaged

[Sergio Durigan Junior]

On Saturday, December 24 2016, Pirate Praveen wrote:

> On ഞായര്‍ 25 ഡിസംബര്‍ 2016 12:01 രാവിലെ, Sergio Durigan Junior wrote:
>> Yep, I did it before building pagure.
>
> It is failing here on sbuild as well.

OK, managed to reproduce it here.

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


signature.asc
Description: PGP signature

Bug#849252: Please ship pkg-config file in libopts25-dev, not autogen

[Josh Triplett]

On Sat, Dec 24, 2016 at 04:31:58PM +0100, Andreas Metzler wrote:
> On 2016-12-24 Josh Triplett  wrote:
> > Package: autogen
> > Version: 1:5.18.12-3
> > Severity: normal
> 
> > While working on a way to automatically detect pkg-config dependencies,
> > I noticed that autogen ships the pkg-config file autoopts.pc (for
> > instance, /usr/lib/x86_64-linux-gnu/pkgconfig/autoopts.pc), which
> > corresponds to the library in libopts25-dev.  Please ship this
> > pkg-config file in the libopts25-dev package, instead.
> [...]
> 
> Hello,
> 
> parts of the source code of binaries linking against libopts is usually
> generated from template files by invoking autogen. Therefore source
> packages usually b-d and require on autogen (not only libots25-dev) and
> ./configure searches for autogen. autogen (the binary package) in turn
> depends on libopts25-dev.
> 
> So imho shipping autoopts.pc in autogen is the right thing to do.

I understand that packages may need both.  However, the pkg-config file
doesn't identify autogen; it identifies the libopts library, and
provides the details needed to link against libopts.  Having the
pkg-config file in autogen diverges from every other library package
that ships pkg-config files.

It might also make sense to have a pkg-config file for autogen itself,
which would live in the autogen package.

Bug#847581: jabref: doesn't always exit and throws exception upon exit

[gregor herrmann]

On Sat, 24 Dec 2016 08:44:48 -0800, tony mancill wrote:

> On Fri, 9 Dec 2016 08:17:17 -0800 tony mancill  wrote:
> > Package: jabref
> > Version: 3.6+ds-1
> > Severity: normal
> 
> I am unable to reproduce this with 3.8+ds-2.

I guess we can close the bug? 


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Lee Ann Rimes: Please Remember


signature.asc
Description: Digital Signature

Bug#711842: jabref: Jabref won't start

[gregor herrmann]

On Sat, 24 Dec 2016 08:53:29 -0800, tony mancill wrote:

> Do we feel that this bug can be closed?  Perhaps after the release of stretch?

Yes, I guess we can close it with 3.6+ds-1 which reworked the runtime
dependencies, so the original problem with the various java packages
shouldn't occur anymore.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Simon And Garfunkel: Sound Of Silence


signature.asc
Description: Digital Signature

Bug#849204: jupyter-nbextension-jupyter-js-widgets: fails to configure

[Ximin Luo]

Control: reassign -1 jupyter-notebook 4.2.3-2
Control: severity -1 normal
Control: close -1 4.2.3-3
Control: merge -1 847917

Hi Norbert, this is due to a bug in jupyter-notebook 4.2.3-2. You can fix it 
locally by removing any empty files matching /etc/jupyter/nbconfig/*.json, then 
reinstalling/reconfiguring ipywidgets.

Because 4.2.3-2 was only in unstable for about 3 days, I didn't think it was 
worth the effort trying to add logic to handle this case specifically. For more 
details see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847917

Please reopen/reassign the bug if my diagnosis was incorrect, and the error is 
caused by some other reason.

X

On Fri, 23 Dec 2016 22:02:28 +0900 Norbert Preining  wrote:
> Package: jupyter-nbextension-jupyter-js-widgets
> Version: 5.2.2-2
> Severity: grave
> Justification: renders package unusable
> 
> Hi all,
> 
> thanks for taking up the incredible complex job of packaging sagemath,
> that is very much appreciated.
> 
> Unforunately, the above package does not configure:
> Unpacking sagemath-jupyter (7.4-3) ...
> Setting up jupyter-nbextension-jupyter-js-widgets (5.2.2-2) ...
> /usr/lib/python3.5/runpy.py:125: RuntimeWarning: 'notebook.nbextensions' 
> found in sys.modules after import of package 'notebook', but prior to 
> execution of 'notebook.nbextensions'; this may result in unpredictable 
> behaviour
>   warn(RuntimeWarning(msg))
> Enabling notebook extension jupyter-js-widgets/extension...
> Traceback (most recent call last):
>   File "/usr/lib/python3.5/runpy.py", line 193, in _run_module_as_main
> "__main__", mod_spec)
>   File "/usr/lib/python3.5/runpy.py", line 85, in _run_code
> exec(code, run_globals)
>   File "/usr/lib/python3/dist-packages/notebook/nbextensions.py", line 1176, 
> in 
> main()
>   File "/usr/lib/python3/dist-packages/jupyter_core/application.py", line 
> 267, in launch_instance
> return super(JupyterApp, cls).launch_instance(argv=argv, **kwargs)
>   File "/usr/lib/python3/dist-packages/traitlets/config/application.py", line 
> 658, in launch_instance
> app.start()
>   File "/usr/lib/python3/dist-packages/notebook/nbextensions.py", line 961, 
> in start
> super(NBExtensionApp, self).start()
>   File "/usr/lib/python3/dist-packages/jupyter_core/application.py", line 
> 256, in start
> self.subapp.start()
>   File "/usr/lib/python3/dist-packages/notebook/nbextensions.py", line 871, 
> in start
> self.toggle_nbextension(self.extra_args[0])
>   File "/usr/lib/python3/dist-packages/notebook/nbextensions.py", line 861, 
> in toggle_nbextension
> logger=self.log)
>   File "/usr/lib/python3/dist-packages/notebook/nbextensions.py", line 407, 
> in enable_nbextension
> logger=logger)
>   File "/usr/lib/python3/dist-packages/notebook/nbextensions.py", line 345, 
> in _set_nbextension_state
> cm.update(section, {"load_extensions": {require: state}})
>   File "/usr/lib/python3/dist-packages/traitlets/config/manager.py", line 85, 
> in update
> data = self.get(section_name)
>   File "/usr/lib/python3/dist-packages/traitlets/config/manager.py", line 63, 
> in get
> return json.load(f)
>   File "/usr/lib/python3.5/json/__init__.py", line 268, in load
> parse_constant=parse_constant, object_pairs_hook=object_pairs_hook, **kw)
>   File "/usr/lib/python3.5/json/__init__.py", line 319, in loads
> return _default_decoder.decode(s)
>   File "/usr/lib/python3.5/json/decoder.py", line 339, in decode
> obj, end = self.raw_decode(s, idx=_w(s, 0).end())
>   File "/usr/lib/python3.5/json/decoder.py", line 357, in raw_decode
> raise JSONDecodeError("Expecting value", s, err.value) from None
> json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
> dpkg: error processing package jupyter-nbextension-jupyter-js-widgets 
> (--configure):
>  subprocess installed post-installation script returned error exit status 1
> dpkg: dependency problems prevent configuration of sagemath-jupyter:
>  sagemath-jupyter depends on jupyter-nbextension-jupyter-js-widgets; however:
>   Package jupyter-nbextension-jupyter-js-widgets is not configured yet.
> 
> Thanks
> 

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Bug#849142: [PATCH] Update dex_expected_diffs and test requirement to ensure test compatibility with enjarify >= 1.0.3. (Closes: #849142)

[Daniel Shahaf]

Chris Lamb wrote on Sat, Dec 24, 2016 at 18:57:38 +:
> @@ -30,6 +31,17 @@ from test_java import javap_version
> +def enjarify_version():
> +# Module enjarify.typeinference appeared in enjarify 1.0.3.  We use a 
> call
> +# directly to the python3 binary over importing with this module to 
> escape
> +# virtualenvs, etc.
> +if subprocess.call(
> +('python3', '-c', 'import enjarify.typeinference'),

Use sys.executable instead of hardcoding 'python3', to handle the case
that there's more than one python3 binary on the system?

(This would be correct for straight python3; is it also correct with
virtualenvs at play?)

Cheers,

Daniel

> +stderr=subprocess.PIPE,
> +) == 0:
> +return '1.0.3'
> +return '1.0.2'

Bug#848942: jessie-pu: package most/5.0.0a-2.3

[Adam D. Barratt]

Control: tags -1 + confirmed

On Tue, 2016-12-20 at 17:52 -0800, Benjamin Mako Hill wrote:
> There was a recent non-critical CVE issued for most:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848132
> https://security-tracker.debian.org/tracker/CVE-2016-1253
> 
> The fix (a debdiff is attached) is this on-liner that changes single quotes to
> double quotes.

Please go ahead.

Regards,

Adam

Bug#824169: ~ Re: Bug#824169: ftp.debian.org: src:chocolate-doom/2.2.1-3 is in both main and contrib

[Jonathan Dowland]

> On 24 Dec 2016, at 11:48, Fabian Greffrath  wrote:
> 
> Merged and uploaded, thanks!

Thank you, Merry Christmas!

Bug#848049: diffoscope: Add detection of order-only differences in plain text formats

[Daniel Shahaf]

Маша Глухова wrote on Sat, Dec 24, 2016 at 18:14:16 +:
> +def order_only_difference(unified_diff):
> +diff_lines = unified_diff.splitlines()
> +added_lines = [line[1:] for line in diff_lines if line.startswith('+')]
> +removed_lines = [line[1:] for line in diff_lines if line.startswith('-')]
> +# Faster check: does number of lines match?
> +if len(added_lines) != len(removed_lines):
> +return False
> +# Counter stores line and number of its occurrences.
> +return sorted(added_lines) == sorted(removed_lines)

What happens if one of the files has a trailing newline and one does
not?  Strictly speaking, that's not an "ordering only difference", but
this function doesn't seem to handle this case.

Example:

% diff -u <(echo foo) <(printf foo) 
--- /proc/self/fd/112016-12-24 20:24:22.064115616 +
+++ /proc/self/fd/122016-12-24 20:24:22.064115616 +
@@ -1 +1 @@
-foo
+foo
\ No newline at end of file

Cheers,

Daniel

Bug#849175: jessie-pu: package ganeti-instance-debootstrap/0.14-2

[Adam D. Barratt]

Control: tags -1 + confirmed

On Fri, 2016-12-23 at 11:00 +0200, Apollon Oikonomopoulos wrote:
> I would like to update ganeti-instance-debootstrap in Jessie to fix 
> #834404. In particular, the proposed update includes an upstream commit 
> that replaces all instances of `losetup -s' with `losetup --show', as 
> the former is no longer supported since util-linux 2.21.

Please go ahead.

Regards,

Adam

Bug#845263: jessie-pu: package w3m/0.5.3-19+deb8u1

[Adam D. Barratt]

Control: tags -1 + pending

On Mon, 2016-12-19 at 01:01 +0900, Tatsuya Kinoshita wrote:
> On December 17, 2016 at 12:30PM +0100, jcristau (at debian.org) wrote:
> >> w3m (0.5.3-19+deb8u1) jessie; urgency=medium
> > Please go ahead.
> 
> Uploaded.

Flagged for acceptance.

Regards,

Adam

Bug#849004: jessie-pu: package evolution-data-server/3.12.9~git20141128.5242b0-2+deb8u2

[Adam D. Barratt]

Control: tags -1 + pending

On Thu, 2016-12-22 at 09:41 +0100, Wouter Verhelst wrote:
> On Wed, Dec 21, 2016 at 07:37:50PM +, Adam D. Barratt wrote:
> > Control: tags -1 + confirmed
> > 
> > On Wed, 2016-12-21 at 18:45 +0100, Wouter Verhelst wrote:
> > > I'd like to see an update for #787398 in jessie, as a customer of mine has
> > > hit this bug, and it's a particularly nasty one. 
> > > 
> > > proposed debdiff:
> > > 
> > > diff -Nru 
> > > evolution-data-server-3.12.9~git20141128.5242b0/debian/changelog 
> > > evolution-data-server-3.12.9~git20141128.5242b0/debian/changelog
> > > --- evolution-data-server-3.12.9~git20141128.5242b0/debian/changelog  
> > > 2015-03-25 12:16:25.0 +0100
> > > +++ evolution-data-server-3.12.9~git20141128.5242b0/debian/changelog  
> > > 2016-12-21 18:31:01.0 +0100
> > > @@ -1,3 +1,13 @@
> > > +evolution-data-server (3.12.9~git20141128.5242b0-2+deb8u2.1) jessie; 
> > > urgency=medium
> > 
> > 3.12.9~git20141128.5242b0-2+deb8u3, please. The part after the "u" is a
> > strictly increasing integer indicating the number of uploads to the
> > relevant Debian release.
> 
> Oops, sorry. dch automatically did that because "NMU".
> 
> > [...]
> > >* d/p/05_imapx-Shared-folders-removed-folder-list-refresh.patch: Fix 
> > > shared
> > > diff -Nru 
> > > evolution-data-server-3.12.9~git20141128.5242b0/debian/patches/06_787398_bae0c64_fix_connection_drop.patch
> > >  
> > > evolution-data-server-3.12.9~git20141128.5242b0/debian/patches/06_787398_bae0c64_fix_connection_drop.patch
> > > --- 
> > > evolution-data-server-3.12.9~git20141128.5242b0/debian/patches/06_787398_bae0c64_fix_connection_drop.patch
> > > 1970-01-01 01:00:00.0 +0100
> > > +++ 
> > > evolution-data-server-3.12.9~git20141128.5242b0/debian/patches/06_787398_bae0c64_fix_connection_drop.patch
> > > 2016-12-21 18:31:01.0 +0100
> > > @@ -0,0 +1,58 @@
> > > +Description: Make camel_stream_write() try to write all bytes at once
> > > + The default implementation of CamelStream::write() used
> > [...]
> > > + evolution-data-server (3.12.9~git20141128.5242b0-2+deb8u2) unstable; 
> > > urgency=medium
> > > + .
> > > +   * d/p/05_imapx-Shared-folders-removed-folder-list-refresh.patch: Fix 
> > > shared
> > > + IMAP folders disappearing in some situations.
> > 
> > I'm assuming those latter few lines aren't meant to be in the patch
> > header?
> 
> Indeed not, those were from the template. I did remove some lines, but left
> some others in.
> 
> > With the above notes in mind, please go ahead.
> 
> Issues you pointed out fixed, rebuilt, uploaded. Thanks!

Flagged for acceptance into p-u; thanks.

Regards,

Adam

Bug#848926: jessie-pu: package libclamunrar/0.99-0+deb8u2

[Adam D. Barratt]

Control: tags -1 + pending

On Wed, 2016-12-21 at 13:42 +0100, Sebastian Andrzej Siewior wrote:
> On 2016-12-20 21:56:22 [+], Adam D. Barratt wrote:
> > Please go ahead.
> 
> done, thx.

Flagged for acceptance.

Regards,

Adam

Bug#849216: Packages which FTBFS with AssertionError about len(context)

[Niko Tyni]

On Fri, Dec 23, 2016 at 06:41:20PM +0100, Santiago Vila wrote:
> Package: checkbox-ng,dhcpcanon,ipywidgets,nbsphinx,pylibmc
> Severity: serious
 
> The following packages currently FTBFS in testing:
> 
> checkbox-ng
> dhcpcanon
> ipywidgets
> nbsphinx
> pylibmc
> 
> with an AssertionError like this:

>   File "/usr/lib/python2.7/dist-packages/docutils/writers/_html_base.py", 
> line 671, in depart_document
> assert not self.context, 'len(context) = %s' % len(self.context)
> AssertionError: len(context) = 1

Seems to be https://github.com/sphinx-doc/sphinx/issues/3212
which should be fixed in sphinx_1.4.9-2, migrated to testing today or so.
-- 
Niko Tyni   nt...@debian.org

Bug#832941: RFS: 4pane (debian: to exclusive)

[Sean Whitton]

Hello David,

On Sat, Dec 24, 2016 at 07:53:09PM +, David Hart wrote:
> Many thanks for the offer. I don't mind packaging Bakefile, and it shouldn't 
> be
> difficult to do.
> 
> However will it be accepted into debian? The project is moribund: apart from a
> single commit 3 years ago, it's been unmaintained for 6 years. That was
> supposed to give time for a rewrite which hasn't happened.
> 
> On the other hand it works as well as ever and is still easily available
> (http://bakefile.org/).
> 
> Do you feel this alters the situation?

If it hasn't bitrotted after 3 years, and you're willing to fix
non-wishlist bugs that get reported to the Debian bug tracker, it would
be fine to upload Bakefile.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#832941: RFS: 4pane (debian: to exclusive)

[David Hart]

Dear Sean,

>Thank you for revising your work in light of my review.  We're too late
>to get 4Pane into stretch, so there's no longer any time pressure on
>this review process.

I know. It missed the jessie freeze too ;)

>So I'd like to reply regarding only the Bakefile
>issue, since that's the biggest blocker to uploading this.

Good; I've found more issues in d/copyright that need sorting out first.

>(Also, by the time the ftp-masters are accepting NEW packages again, I
>will be a DD, so I can actually do the upload for you.)
//snip
>I suspect that those other packages are buggy, then.  I note that the
>ftp-masters have stated that their review process does not operate on
>precedent: the presence of any given package in the archive does not
>itself constitute a reason for accepting another.

I see.

>Why not just go ahead and package Bakefile?  It might be useful to
>someone else.  You don't have to invoke it during the 4Pane build; it
>just needs to be possible for someone else to get everything they need
>to do so from the Debian mirrors.
>
>I will review and sponsor your packaging of Bakefile.

Many thanks for the offer. I don't mind packaging Bakefile, and it shouldn't be
difficult to do.

However will it be accepted into debian? The project is moribund: apart from a
single commit 3 years ago, it's been unmaintained for 6 years. That was
supposed to give time for a rewrite which hasn't happened.

On the other hand it works as well as ever and is still easily available
(http://bakefile.org/).

Do you feel this alters the situation?

Regards,

David Hart

Bug#848403: diffoscope: FTBFS randomly (Fatal Python error: deallocating None)

[Chris Lamb]

Ximin Luo wrote:

> I still haven't managed to reproduce this myself but I'll just note
> for the record we have seen this on jenkins before

My guess is that one of the third-party Python extension modules that
we import does not correctly reference count Py_None. Someone did a
good writeup here:

  http://stackoverflow.com/a/15288194

Now, we just need to narrow down which one… and then fix it.  >.>


Regards,

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

Bug#848403: diffoscope: FTBFS randomly (Fatal Python error: deallocating None)

[Ximin Luo]

I still haven't managed to reproduce this myself but I'll just note for the 
record we have seen this on jenkins before:

https://jenkins.debian.net/job/reproducible_diffoscope_from_git_master/63/console

Santiago Vila:
> Package: src:diffoscope
> Version: 63
> Severity: serious
> 
> Hello folks.
> 
> I tried to build this package in stretch with "dpkg-buildpackage -A"
> (which is what the "Arch: all" autobuilder would do to build it)
> but it failed:
> 
> 
> [...]
>  debian/rules build-indep
> dh build-indep --with python3 --with bash-completion --buildsystem=pybuild
>dh_testdir -i -O--buildsystem=pybuild
>dh_update_autotools_config -i -O--buildsystem=pybuild
>dh_autoreconf -i -O--buildsystem=pybuild
>dh_auto_configure -i -O--buildsystem=pybuild
> I: pybuild base:184: python3.5 setup.py config 
> running config
>debian/rules override_dh_auto_build
> make[1]: Entering directory '/<>'
> register-python-argcomplete diffoscope > debian/diffoscope.bash-completion
> rst2man debian/trydiffoscope.1.rst debian/trydiffoscope.1
> rst2man debian/diffoscope.1.rst debian/diffoscope.1
> 
> [... snipped ...]
> 
> diffoscope/comparators/squashfs.py144 1987%   75, 91, 
> 105, 111, 114, 126, 134, 154, 159-160, 163-164, 167-168, 181, 210-213, 227
> diffoscope/comparators/symlink.py  28  196%   35
> diffoscope/comparators/tar.py  13  0   100%
> diffoscope/comparators/text.py 25  292%   52-54
> diffoscope/comparators/utils.py   224 2390%   67, 
> 132-135, 182-183, 188-191, 195, 199, 300, 304, 308, 312, 320, 323, 326, 335, 
> 345, 348, 353
> diffoscope/comparators/xz.py   27  0   100%
> diffoscope/comparators/zip.py  90  397%   64, 70, 73
> diffoscope/config.py   24  292%   49, 57
> diffoscope/difference.py  327 2393%   75, 108, 
> 163, 305, 311, 321-325, 335, 353, 411, 426-428, 446-450, 456-461
> diffoscope/exc.py  15  847%   23-24, 
> 210-217
> diffoscope/main.py170 3281%   44-45, 160, 
> 162, 164-165, 189, 198-203, 209, 224, 229, 240, 253, 258, 264-267, 273, 279, 
> 284, 295, 297-301, 306
> diffoscope/presenters/__init__.py   0  0   100%
> diffoscope/presenters/html.py 42411373%   253, 282, 
> 367, 372, 374-376, 406, 409, 411, 437, 451, 456, 493-497, 506-509, 513-519, 
> 536-560, 576-577, 580-581, 593-594, 597-601, 609-612, 622-625, 640, 653-656, 
> 666-667, 672-673, 681-683, 713-715, 722, 739, 744-746, 752-753, 766-798
> diffoscope/presenters/icon.py   1  0   100%
> diffoscope/presenters/text.py  36  489%   34, 61-63
> diffoscope/progress.py 68 2169%   39-44, 47, 
> 52, 57, 61, 66, 70, 95-104, 107-109, 112, 116, 119, 122
> -
> TOTAL379359984%
> Coverage HTML written to dir htmlcov
> 
> === short test summary info 
> 
> SKIP [1] .pybuild/pythonX.Y_3.5/build/tests/comparators/test_cbfs.py:80: 
> requires cbfstool
> SKIP [1] .pybuild/pythonX.Y_3.5/build/tests/comparators/test_fsimage.py:79: 
> guestfs not working on the system
> SKIP [1] .pybuild/pythonX.Y_3.5/build/tests/comparators/test_fsimage.py:61: 
> guestfs not working on the system
> SKIP [1] .pybuild/pythonX.Y_3.5/build/tests/comparators/test_cbfs.py:87: 
> requires cbfstool
> SKIP [1] .pybuild/pythonX.Y_3.5/build/tests/comparators/test_utils.py:49: 
> requires /missing
> SKIP [1] .pybuild/pythonX.Y_3.5/build/tests/comparators/test_utils.py:45: 
> requires
> SKIP [1] .pybuild/pythonX.Y_3.5/build/tests/comparators/test_cbfs.py:75: 
> requires cbfstool
> SKIP [1] .pybuild/pythonX.Y_3.5/build/tests/comparators/test_cbfs.py:64: 
> requires cbfstool
> SKIP [1] .pybuild/pythonX.Y_3.5/build/tests/comparators/test_cbfs.py:60: 
> requires cbfstool
> SKIP [1] .pybuild/pythonX.Y_3.5/build/tests/comparators/test_cbfs.py:56: 
> requires cbfstool
> SKIP [1] 
> /<>/.pybuild/pythonX.Y_3.5/build/tests/comparators/test_haskell.py:33:
>  mismatch between system ghc and fixture
> SKIP [1] .pybuild/pythonX.Y_3.5/build/tests/comparators/test_macho.py:50: 
> requires otool and lipo
> SKIP [1] 
> /<>/.pybuild/pythonX.Y_3.5/build/tests/comparators/test_haskell.py:47:
>  mismatch between system ghc and fixture
> SKIP [1] .pybuild/pythonX.Y_3.5/build/tests/comparators/test_fsimage.py:50: 
> guestfs not working on the system
> SKIP [1] .pybuild/pythonX.Y_3.5/build/tests/comparators/test_macho.py:43: 
> requires otool and lipo
> 
> === 233 passed, 15 skipped in 237.38 seconds 
> ===
> Fatal Python error: 

Bug#820111: document how to use per-user systemd --user services

[Patrick Schleizer]

Michael Biebl:
> Can you attache the full output of
> systemctl status --user mytest
> 
> and the completer mytest.service unit.

You looking into this is appreciated!

cat /etc/systemd/user/mytest.service
[Unit]
Description=mytest

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/bin/true

[Install]
WantedBy=multi-user.target

systemctl status --user mytest
● mytest.service - mytest
   Loaded: loaded (/etc/systemd/user/mytest.service; enabled)
   Active: inactive (dead)

Best regards,
Patrick

Bug#844034: Any intend to fix this soon

[Andreas Tille]

Hi Afif,

On Sat, Dec 24, 2016 at 07:24:22AM -0800, Afif Elghraoui wrote:
> 
> I have actually been working on this over the past few days. I keep
> works-in-progress out of the master branch, so my work is in the branch
> topic/blasr-5 [1] and I've been posting updates to the upstream bug
> tracker to avoid duplication of efforts between here and upstream. I
> hoped anyone taking a look here would first check the upstream bug
> tracker. I'm really sad to see the duplication of effort when I was so
> particular to make sure my work was pushed :(. Is there a way we can
> avoid this in the future?

Its no real problem.  I think it will not happen to frequently since the
situation to save package for upcoming releases is only every second
year - perhaps posting the fact you are working in a separate branch
would help in such cases.  Feel free to replace everything I did by your
probably more advanced changes since you know the internals way better.
I also do not consider my time terribly wasted since I know have some
insight into these packages.

> The reason I made a blasr upload yesterday was because I was advised
> that it might fix a problem that was affecting pbhoney (after correcting
> the command-line flags). I was going to continue testing today, now that
> the upload has been installed in the archive, and report back to the
> blasr upstream.

That's fine. 

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#849216: Packages which FTBFS with AssertionError about len(context)

[Chris Lamb]

Hi Santiago,

> Packages which FTBFS with AssertionError about len(context)

Haven't tested this but python-docutils 0.13.1+dfsg-1 migrated to
testing just a few days ago so that seems the most likely culprit:

  https://tracker.debian.org/news/826060


Regards,

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

Bug#846002: blends-tasks must not be priority:important (was Re: Bug#846002: Lowering severity)

[Raphael Hertzog]

On Sat, 24 Dec 2016, Cyril Brulebois wrote:
> So I've just looked at the proposed changes, and adding a prompt at this
> point is not an option: we're changing logic during the freeze, and
> adding translatable material (not the kind of hidden stuff that might
> happen with obscure preseeding values, but something that is going to
> hit all users) is not a good thing either.

I would suggest to commit this to git, do a call for translators to update
this new translation and then judge on the result to see if you have enough
translations to release it for stretch.

I know it's late in the release cycle, but we're not yet in deep freeze
and the release team has always accomodated far more invasive changes to
debian-installer in the past.

But a plain reject at this point with the associated refusal for the blends to
appear in the list is going to make everybody upset which is a pity since
we have a rather good compromise here.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/

Bug#849284: insserv: fopen(/etc/insserv.conf): No such file or directory

[Petter Reinholdtsen]

[積丹尼 Dan Jacobson]
> # grep -B 2 insserv.conf /var/log/apt/term.log
> Selecting previously unselected package ppp.
> Preparing to unpack .../1065-ppp_2.4.7-1+4_amd64.deb ...
> insserv: fopen(/etc/insserv.conf): No such file or directory

What is your point?  The file is part of the inssserv package, and if
you remove the file insserv no longer work.  The conclusion to draw from
that is simply: do not remove /etc/insserv.conf.  Do you know how it
disappeared?

There are many ways to break insserv.  Those who do get to keep all the
pieces. :)

--
Happy hacking
Petter Reinholdtsen

Bug#849293: [Pkg-libvirt-maintainers] Bug#849293: virt-manager is uninstallable: virtinst binary package went missing

[Guido Günther]

Hi Simon,
On Sat, Dec 24, 2016 at 06:25:26PM +, Simon McVittie wrote:
> Package: virt-manager
> Version: 1:1.4.0-4
> Severity: grave
> Justification: renders package unusable
> 
> virt-manager Depends on virtinst. Both are produced by src:virt-manager
> and are Architecture: all, but the 1:1.4.0-4 upload somehow includes
> virt-manager_*_all.deb but not virtinst_*_all.deb.
>  says:
> 
> > Files: 
> >  120ff4558a7c16d7ce34e819c4443658 2167 admin optional 
> > virt-manager_1.4.0-4.dsc
> >  6845af224bda02baf0224d337d019f18 15208 admin optional 
> > virt-manager_1.4.0-4.debian.tar.xz
> >  245d8408f4a1242ab2d26b8fed725467 913498 admin optional 
> > virt-manager_1.4.0-4_all.deb
> 
> I don't know how this happened, but when I rebuilt it in a clean sid chroot
> with sbuild, I correctly got both binary packages produced.

mergechanges -i virt-manager_1.4.0-4_amd64.changes 
virt-manager_1.4.0-4_amd64.changes > virt-manager_1.4.0-4_source+all.changes

is buggy in 2.16.10 and reliably drops virtinstall - if the cowbuilder
build would have missed the package already the autopkgtests would have
failed. devscripts  2.16.13 looks fixed.

> I would suggest making source-only uploads so that the Architecture: all
> buildd will do the build in a predictable environment (this worked in my
> sbuild when I tried it, so hopefully it will work equally well on buildds).

Not uploading binary packages was the whole point of the above (althogh
did not yet switch to -S instead of -i for unstable which I've done
now).

Cheers and sorry for the inconvenience,
 -- Guido

> 
> Regards,
> S
> 
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), 
> (500, 'stable'), (1, 'experimental-debug'), (1, 'experimental')
> 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)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> -- no debconf information
> 
> ___
> Pkg-libvirt-maintainers mailing list
> pkg-libvirt-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-libvirt-maintainers
> 

Bug#849294: python-apt: aptsources.sourceslist ignores sources.list.d/*.sources files

[Paul Gevers]

Package: python-apt
Version: 1.1.0~beta5
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

I noticed that aptsources.sourceslist doesn't take the content of souces.list.d
sources files into account.

paul@testavoira /etc/apt $ ls -al sources.list
ls: cannot access 'sources.list': No such file or directory
paul@testavoira /etc/apt $ ls -al sources.list.d
total 12
drwxr-xr-x 2 root root 4096 dec 24 20:15 .
drwxr-xr-x 6 root root 4096 dec 24 20:15 ..
- -rw-r--r-- 1 root root  313 dec 24 10:50 default.sources
paul@testavoira /etc/apt $ cat sources.list.d/default.sources 
Types: deb deb-src
URIs: https://deb.debian.org/debian
Suites: stretch
Components: main contrib non-free

Types: deb
URIs: https://deb.debian.org/debian-security
Suites: stretch/updates
Components: main contrib non-free

Types: deb
URIs: https://deb.debian.org/debian-debug
Suites: stretch-debug
Components: main

>>> from aptsources import sourceslist
>>> sl = sourceslist.SourcesList()
WARNING:root:could not open file '/etc/apt/sources.list'

>>> len(sl.list)
0


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

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

Versions of packages python-apt depends on:
ii  dirmngr2.1.16-3
ii  gnupg  2.1.16-3
ii  libapt-inst2.0 1.4~beta2
ii  libapt-pkg5.0  1.4~beta2
ii  libc6  2.24-8
ii  libgcc11:6.2.1-5
ii  libstdc++6 6.2.1-5
ii  python 2.7.11-2
ii  python-apt-common  1.1.0~beta5
pn  python:any 

Versions of packages python-apt recommends:
ii  iso-codes3.72-1
ii  lsb-release  9.20161125
ii  xz-utils 5.2.2-1.2

Versions of packages python-apt suggests:
ii  apt 1.4~beta2
pn  python-apt-dbg  
pn  python-apt-doc  

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAlheytYACgkQnFyZ6wW9
dQodCgf/aGwEQTj4ZX1kpDsAFVsY5IW2QC3+4eqUgZyuCE233HIzElZlgQ9cHGZk
oaLzx54Pwlhs37DHoD6glrzehn2nLUR3KHVZD1ULU3WpBrd2TiZNCU0ltUkRt78u
3Qra7nQmmqpDCqTHWXF3PsZrFsz1v2K8HP73Lc+kuVgj+iqewbz51kdbEhGFsJ0S
itSA8RhHmOsfS3MLAtdjDYggFDK38EBqcWYIktZGQIA9c5hiZqH8FoPoYzwO2JJ7
FDFrDCK4/6VY3mcISxD/NG0qN60BPKdNpLTFQSdXBF0Sm7ZA/kkN4GYKHBy5Qc7G
xTye42WdcJfWaxfXQB7r9mUnQXwFZQ==
=6hIb
-END PGP SIGNATURE-

Bug#848076: openconnect 7.07 fails to connect to latest Pulse / Juniper VPN

[Mike Miller]

Control: tags -1 - pending + moreinfo 

On Tue, Dec 13, 2016 at 15:23:41 -0500, Hillel Lubman wrote:
> Package: openconnect
> Version: 7.07-1
> Severity: important
> 
> openconnect 7.07 stopped working with latest release of Pulse/Juniper VPN.
> See http://lists.infradead.org/pipermail/openconnect-
> devel/2016-November/004052.html
> 
> This is fixed in 7.08 which was released recently. Please update it in Debian
> to the latest release to fix this bug.

I can't tell by inspection whether 7.08 fixes the problem you are
experiencing or not. The mailing list thread you point to seems
unrelated (user had self-compiled OpenConnect using OpenSSL).

Can you please test with 7.08-1 which will be available in the archive
soon? Does 7.08-1 fix the problem you were having with 7.07-1?

Thanks,

-- 
mike


signature.asc
Description: PGP signature

Bug#849277: A typo, "flavor", which evaluates to nothing, prevents bbdb3 from loading

[Barak A. Pearlmutter]

Thanks for the report.
Just pushed a fix.
(This issue was not upstream, just in the debian packaging goo.)

Bug#817638: pyode: diff for NMU version 1.2.0-4+cvs20090320.2

[Christoph Biedl]

Christoph Biedl wrote...

> Find below the debdiff for a NMU I've prepared for pyode (versioned as
> 1.2.0-4+cvs20090320.2)

Upon review I realized the correct version number for an NMU should have
been 1.2.0-4+cvs20090320.1.1 instead. Indulge me.

Christoph



signature.asc
Description: Digital signature

Bug#815085: mailutils: Fix implicit pointer conversion on 64bit targets

[Jeremy Bicha]

mailutils, as synced with Debian, built successfully on all Ubuntu
arches so I believe this has been fixed. I didn't see any "implicit
conversion" warnings in the 64-bit build logs either.

https://launchpad.net/ubuntu/+source/mailutils/1:3.0-1

Thanks,
Jeremy Bicha

Bug#829046: pagure dependencies (JavaScript libraries) packaged

[Pirate Praveen]

On ഞായര്‍ 25 ഡിസംബര്‍ 2016 12:01 രാവിലെ, Sergio Durigan Junior wrote:
> Yep, I did it before building pagure.

It is failing here on sbuild as well.

aviau, can you try to build it?





signature.asc
Description: OpenPGP digital signature

Bug#849063: src:haskell-mode: maintainer address bounces

[Barak A. Pearlmutter]

> Barak, can you do the necessary upload? You seem to be most involved
> with the package these days, so feel free to "promote" yourself to
> maintainer.

Will do.

> http://pkg-emacsen.alioth.debian.org/

https://.  And even better: I'll do that!

Two other minor matters.

(a) For this or any of my other packages, please feel free to just
push a change to collab-maint git or whatever, or even to do an NMU,
for stuff like this. I really don't mind!

(b) Um, Ansgar, the "Severity: Important" for an issue like this seems
overly strident to me. I'd classify this as "minor" or at worst
"normal", since it has zero actual effect on the package's
functionality to users.

Bug#839582: USB-Keyboard don't work with latest daily build

[Bernhard]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello

I tested the daily build again.
Problem still exists.

Best regards
Bernhard
-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEE7jPG5HJ+kWHn/cxg003JKjHIodAFAlhev+QTHGJld29lcm4x
QGdtYWlsLmNvbQAKCRDTTckqMcih0MEtEACLDAQDEuPGO4n0bAUBw5paJ5P8HXrK
/fjqoBG3KvA3Muf8txGkqK0/wOCJDCzCmvM0t+JRp8GB56gtZbc/I5WwOQGSafvX
RV2AIR3kRmaIss3oPsmlrPlOLuRZWlKmJmWq88ufEsJf8chrVY98adUYMSF1vy5q
YL2eOvkNjfF3wuRwWufYF4TzVwBK75Mo3SA6vDhqsmpdNXV6EhNcsX+1p8I1rvRY
9z4OYYwOxNjzfCu+XrIgZiT0iRMwxEaWXo6Vr4yrfw8ChhiTs0frktiz4IpYEhHt
cDqDg6tPIX+gHcJci619MYBzeqTyMQZRTV8kwdRIjcQCWOxHH7ylG7qsIWw+QBUU
z+sCSqlTpp9gUAHlMfUHcSMqr9FqqdwWLY8aalNWrV7pedaMs9EUj9nh9AhJLcjk
oU/JgOdiLNo6H2q5uMlEgxYiencCEbzn+84Y7/8BlCorGgspjSIsniYNs42kf9QS
v/iUcU4zZmopvMeSjrvv17iyGzN5s/9uSr+1TOqBIUs+PqX+nO/4UKA9cnK7RTmx
10ICyoV1e85MNena+hRHgP2H8wav2XymTus29ZlPZt2jsxt2wDdaWA14MsxTazhU
pxfvaE1AwRMfswTGNK1ucWeFqrnFX74EJ9MEJDZe31CwSHN0eyx2X3HvCgWno4hs
W99hsogSCmEUXQ==
=uXOz
-END PGP SIGNATURE-

Bug#829046: pagure dependencies (JavaScript libraries) packaged

[Sergio Durigan Junior]

On Saturday, December 24 2016, Pirate Praveen wrote:

> On ശനി 24 ഡിസംബര്‍ 2016 11:58 വൈകു, Sergio Durigan Junior wrote:
>> Hm, strange.  I'm using pbuilder/cowdancer to build the package, so it
>> should catch this.  I'll look into it.
>
> Did you update pbuilder recently? You have to run 'pbuilder update' often.

Yep, I did it before building pagure.

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


signature.asc
Description: PGP signature

Bug#829046: pagure dependencies (JavaScript libraries) packaged

[Pirate Praveen]

On ശനി 24 ഡിസംബര്‍ 2016 11:58 വൈകു, Sergio Durigan Junior wrote:
> Hm, strange.  I'm using pbuilder/cowdancer to build the package, so it
> should catch this.  I'll look into it.

Did you update pbuilder recently? You have to run 'pbuilder update' often.




signature.asc
Description: OpenPGP digital signature

Bug#829046: pagure dependencies (JavaScript libraries) packaged

[Sergio Durigan Junior]

On Saturday, December 24 2016, Pirate Praveen wrote:

> On ശനി 24 ഡിസംബര്‍ 2016 07:26 വൈകു, Sergio Durigan Junior wrote:
>> Yep, I forgot :-/.  Anyway, pushed now.  Sorry about that.
>
> I'm still getting the same error,
>
> from html5lib.sanitizer import HTMLSanitizer
> ImportError: No module named sanitizer
>
> I don't see either python-bleach or python-html5lib is updated.
>
> This bug is still open
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844943 May be you have
> an older version of python-html5lib in your system. We have to fix this
> bug to proceed further.

Hm, strange.  I'm using pbuilder/cowdancer to build the package, so it
should catch this.  I'll look into it.

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


signature.asc
Description: PGP signature

Bug#818230: aircrack-ng: please make the build reproducible

[Samuel Henrique]

Control: tags 818230 - patch

Hi Reiner,

Thanks a lot for the work, but aircrack has made considerable amount of
changes on its build system since 1.2-0~beta3-4, i understand that rc4
still doesn't builds reproducibly.

Could you please update the patch to rc4? I would be infinitely grateful :)

Also, i believe you can also send this upstream, but if you don't, i can do
that for you.

Samuel Henrique 

Bug#845623: Pending fixes for bugs in the golang-github-aelsabbahy-gonetstat package

[pkg-go-maintainers]

tag 845623 + pending
thanks

Some bugs in the golang-github-aelsabbahy-gonetstat package are
closed in revision ff4abffd16a1fd4f1dfa08af0157468d0e7758d7 in branch
'master' by Andrew Starr-Bochicchio

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-aelsabbahy-gonetstat.git/commit/?id=ff4abff

Commit message:

Rebuild to remove errant depends on golang-github-drael-gonetstat-dev 
(Closes: #845623).

Bug#848063: fixed in ri-li 2.0.1+ds-4

[Santiago Vila]

I have now built the package 99 more times and this has been the result:

Tried 100 times. Failed 97 times.
Approximate failure rate: 97%.

I've put the 100 build logs here for you to see:

https://people.debian.org/~sanvila/ri-li/

The builds were made on different autobuilders.

The Release Managers are considering a threshold for FTBFS
which happen randomly. Where would you put the threshold
in your opinion? Do we need a failure rate of 98% to be RC,
so that this package is still under the threshold?

IMO, any such threshold over 10% would be too high.

Thanks.

Bug#849293: virt-manager is uninstallable: virtinst binary package went missing

[Simon McVittie]

Package: virt-manager
Version: 1:1.4.0-4
Severity: grave
Justification: renders package unusable

virt-manager Depends on virtinst. Both are produced by src:virt-manager
and are Architecture: all, but the 1:1.4.0-4 upload somehow includes
virt-manager_*_all.deb but not virtinst_*_all.deb.
 says:

> Files: 
>  120ff4558a7c16d7ce34e819c4443658 2167 admin optional virt-manager_1.4.0-4.dsc
>  6845af224bda02baf0224d337d019f18 15208 admin optional 
> virt-manager_1.4.0-4.debian.tar.xz
>  245d8408f4a1242ab2d26b8fed725467 913498 admin optional 
> virt-manager_1.4.0-4_all.deb

I don't know how this happened, but when I rebuilt it in a clean sid chroot
with sbuild, I correctly got both binary packages produced.

I would suggest making source-only uploads so that the Architecture: all
buildd will do the build in a predictable environment (this worked in my
sbuild when I tried it, so hopefully it will work equally well on buildds).

Regards,
S

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), 
(500, 'stable'), (1, 'experimental-debug'), (1, 'experimental')
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)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information

Bug#849292: ITP: node-rollup -- Next-generation ES6 module bundler

[Pirate Praveen]

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

* Package name: node-rollup
  Version : 0.38.0
  Upstream Author : Rich Harris
* URL : https://github.com/rollup/rollup
* License : Expat
  Programming Lang: JavaScript
  Description : Next-generation ES6 module bundler



signature.asc
Description: OpenPGP digital signature

Bug#711716: openssh-server: generated config file differs from reality

[Colin Watson]

Source: openssh
Source-Version: 1:6.4p1-2

On Sun, Jun 09, 2013 at 12:12:08AM +0200, Toni Mueller wrote:
> I found that the sshd_config file generated from postinst says that
> the server key size should be 768 bits. Fortunately, the rest of
> the postinst doesn't care and proceeds to generate an RSA key with
> 2048 bits (the recommended size). I suggest that the generated config
> file also states that the key size be 2048 bits instead of 768.

I updated this somewhat in 1:6.4p1-2 (to 1024), and it's now moot since
protocol 1 support has been disabled (in 7.0p1) and removed (in 7.4p1)
from the server.

Thanks,

-- 
Colin Watson   [cjwat...@debian.org]

Bug#848049: diffoscope: Add detection of order-only differences in plain text formats

[Маша Глухова]

I believe the attached patch would provide the requested functionality.
From 0ae6d16037cc4912e5a165ee050e31e99402c912 Mon Sep 17 00:00:00 2001
From: Maria Glukhova 
Date: Sat, 24 Dec 2016 12:29:57 +0200
Subject: [PATCH] Add detection of order-only difference in plain text format.

Detect if the text files' contents differ only in line ordering, and give an appropriate comment.

Closes: #848049
---
 diffoscope/comparators/text.py  | 14 ++
 tests/comparators/test_text.py  |  8 
 tests/data/text_order1  |  7 +++
 tests/data/text_order2  |  7 +++
 tests/data/text_order_expected_diff | 11 +++
 5 files changed, 47 insertions(+)
 create mode 100644 tests/data/text_order1
 create mode 100644 tests/data/text_order2
 create mode 100644 tests/data/text_order_expected_diff

diff --git a/diffoscope/comparators/text.py b/diffoscope/comparators/text.py
index 909ff98..f7f423f 100644
--- a/diffoscope/comparators/text.py
+++ b/diffoscope/comparators/text.py
@@ -24,6 +24,17 @@ from diffoscope.difference import Difference
 from diffoscope.comparators.binary import File
 
 
+def order_only_difference(unified_diff):
+diff_lines = unified_diff.splitlines()
+added_lines = [line[1:] for line in diff_lines if line.startswith('+')]
+removed_lines = [line[1:] for line in diff_lines if line.startswith('-')]
+# Faster check: does number of lines match?
+if len(added_lines) != len(removed_lines):
+return False
+# Counter stores line and number of its occurrences.
+return sorted(added_lines) == sorted(removed_lines)
+
+
 class TextFile(File):
 RE_FILE_TYPE = re.compile(r'\btext\b')
 
@@ -44,6 +55,9 @@ class TextFile(File):
 with codecs.open(self.path, 'r', encoding=my_encoding) as my_content, \
  codecs.open(other.path, 'r', encoding=other_encoding) as other_content:
 difference = Difference.from_text_readers(my_content, other_content, self.name, other.name, source)
+# Check if difference is only in line order.
+if difference and order_only_difference(difference.unified_diff):
+difference.add_comment("ordering differences only")
 if my_encoding != other_encoding:
 if difference is None:
 difference = Difference(None, self.path, other.path, source)
diff --git a/tests/comparators/test_text.py b/tests/comparators/test_text.py
index 9892826..afa0716 100644
--- a/tests/comparators/test_text.py
+++ b/tests/comparators/test_text.py
@@ -65,3 +65,11 @@ def test_difference_between_iso88591_and_unicode_only(iso8859, tmpdir):
 
 def test_compare_non_existing(monkeypatch, ascii1):
 assert_non_existing(monkeypatch, ascii1, has_null_source=False, has_details=False)
+
+text_order1 = load_fixture(data('text_order1'))
+text_order2 = load_fixture(data('text_order2'))
+
+def test_ordering_differences(text_order1, text_order2):
+difference = text_order1.compare(text_order2)
+assert difference.comments == ['ordering differences only']
+assert difference.unified_diff == open(data('text_order_expected_diff')).read()
diff --git a/tests/data/text_order1 b/tests/data/text_order1
new file mode 100644
index 000..9f85b81
--- /dev/null
+++ b/tests/data/text_order1
@@ -0,0 +1,7 @@
+These
+lines
+follow
+in
+some
+order
+.
diff --git a/tests/data/text_order2 b/tests/data/text_order2
new file mode 100644
index 000..7890b50
--- /dev/null
+++ b/tests/data/text_order2
@@ -0,0 +1,7 @@
+These
+some
+order
+follow
+in
+lines
+.
diff --git a/tests/data/text_order_expected_diff b/tests/data/text_order_expected_diff
new file mode 100644
index 000..2d8b915
--- /dev/null
+++ b/tests/data/text_order_expected_diff
@@ -0,0 +1,11 @@
+@@ -1,7 +1,7 @@
+ These
+-lines
+-follow
+-in
+ some
+ order
++follow
++in
++lines
+ .
-- 
2.11.0

Bug#847819: [performous] update the ffmpeg and continue the issue

[ftoledo]

hi Andreas. I test in a new machine (no external repos and differnte hardware) 
and have same issue.
The graphics freeze and the sound continue. 

i wait if another people can reproducte it.

Bug#849291: ITP: node-babel -- Babel is a JavaScript compiler to use next generation JavaScript, today

[Pirate Praveen]

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

* Package name: node-babel
  Version : 6.21.1
  Upstream Author : Sebastian McKenzie 
* URL : https://babeljs.io/
* License : Expat
  Programming Lang: JavaScript
  Description :  Babel is a JavaScript compiler to use next
generation JavaScript, today



signature.asc
Description: OpenPGP digital signature

Bug#839783: marked as done (Please package Emacs 25.1)

[Rob Browning]

Eugen Dedu  writes:

> Would it be possible to make it the version by default?  Currently, it 
> is version 24.

Definitely, though we're not quite there yet.  We've had to deal with
some stability issues, and now we're looking at the state of various
add-on packages, but we'd like to make the change soon.

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

Bug#849290: dovecot-core: incorrect information in /etc/dovecot/README

[Rolf Leggewie]

Package: dovecot-core
Severity: minor

Dear Maintainer,

I would say that the file /etc/dovecot/README is pretty unnecessary.
I run the version from Jessie and there is nothing particularly
interesting in that file and the referenced directory does not even
exist.  Time to drop the file?

Regards

Rolf

Bug#849288: zsh-dev: installing config.h breaks reproducibility (followup to #776964)

[Daniel Shahaf]

Package: zsh-dev
Version: 5.3.1-1

Since #776964, the package installs /usr/include/zsh/config.h for
plugins' benefit.  Since upstream's 'make install' does not install
config.h, plugins developed on Debian will fail to compile on other
systems.

The set of header files installed by the package and by upstream should
be brought back in sync.

Bug#849289: git-annex: [RFE] youtube-dl support

[Rolf Leggewie]

Package: git-annex
Severity: wishlist
Tags: upstream

Dear Maintainer,

it would be nice if git-annex supported the youtube-dl package as an
alternative to quvi, especially considering that quvi is currently in
RFA status (bug #831732).

Regards

Rolf

Bug#849142: test regression in test_dex.test_differences with enjarify >= 1.0.3

[Mattia Rizzolo]

Control: severity -1 serious
Control: found -1 65

On Thu, Dec 22, 2016 at 11:53:04PM +0100, Levente Polyak wrote:
> current version: git HEAD 8dde15f9200094882c26a1cf422556c43ec5d5dc
> 
> The test_differences test case fails in the test_dex module when using
> enjarify 1.0.3. A downgrade of enjarify to 1.0.2 makes the test pass
> again. As enjarify 1.0.3 itself seems to do what its supposed to do, i
> think the test diff/output is just too strictly tied to the 1.0.2 output.

And this now came into unstable too, and we're seeing that error in
buildds and in ci.d.n.

> If the guess above is actually the case, a possible workaround may be to
> expect enjarify to be 1.0.2 and skip the test otherwise.
> However we start ending up with too many tests strictly tight to a very
> specific toolset version, making a more general approach for multiple
> sets more and more important.

ISTR you mentioning a patch for that making the test compatible with
both versions, care to share? :)

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature