Bug#841411: libkf5kface: FTBFS: error with opencv 3.1

[Maximiliano Curia]

¡Hola Nobuhiro!

El 2016-11-08 a las 12:38 +0900, Nobuhiro Iwamatsu escribió:
Thanks for your pointing. 
I worked about this on with-contrib branch, but I think this work too 
late about transiton. 
 https://anonscm.debian.org/cgit/debian-science/packages/opencv.git/log/?h=with-contrib


Thanks for adding the face module, I see that the contrib modules are 
being installed under an opencv2 directory, is that intentional?


About the timing for the transition, it shouldn't hurt to ask the release team 
about it. If all the issues raised by the opencv change have been 
addressed and you are willing to fix any ripples it might cause then it might 
be just a matter of waiting for the colliding transitions to settle.


Happy hacking,
--
"There are two ways of constructing a software design.  One way is to make it
so simple that there are obviously no deficiencies. And the other way is to
make it so complicated that there are no obvious deficiencies."
-- C.A.R. Hoare
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#843612: trash-cli: debian trash-cli segmentation faults

[Gijs Hillenius]

Package: trash-cli
Version: 0.12.9.14-2
Severity: important

Dear Maintainer,

In Debian Sid, trash-cli is resulting in segmentation faults (since eh,
like a week or so?).


for example:

trash-empty 7
Segmentation fault

trash-list
2016-11-01 12:09:36 /path/to/some/file
(long list)
2016-11-04 15:37:55 /path/to/some/file
Segmentation fault

I don't know how to debug this, I tried running

gdb run usr/bin/trash-empty

and several variations, but that is clearly not the right way to debug this. 

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

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 trash-cli depends on:
ii  python2.7.11-2
ii  python-pkg-resources  28.7.1-1

trash-cli recommends no packages.

trash-cli suggests no packages.

-- no debconf information

Bug#843611: Problem with your blog feed

[Daniel Pocock]

Package: drupal7
Version: 7.32-1+deb8u7
Severity: important
X-Debbugs-CC: hert...@debian.org


On 07/11/16 23:04, Raphael Hertzog wrote:
> Hi,
>
> looking at
> https://validator.w3.org/feed/check.cgi?url=http%3A%2F%2Fplanet.debian.org%2Frss20.xml
> it looks like your blog entries are creating troubles:
>
> This feed does not validate.
>
> line 13, column 63: Invalid character in a URI: 
> https://danielpocock.com/317 at https://danielpocock.com (2 occurrences) 
> [help]
>
>   https://danielpocock.com/317 at 
> https://danielpocock.com
>^
>
> Can you look into fixing this?

The blog is maintained using Drupal 7 packaged on Debian jessie.

I couldn't find that exact string in the feed.  I did find this:

317 at https://danielpocock.com

while looking at:
view-source:https://danielpocock.com/tags/debian/feed


but I found:

https://danielpocock.com/317 at https://danielpocock.com

in view-source:http://planet.debian.org/rss20.xml


I'm guessing it is a Drupal bug or configuration issue, as it appears to
be like this for all my blog posts.  Would any of the Drupal maintainers
be able to comment on this?  Has it been seen in other Drupal blogs?

Regards,

Daniel

Bug#843551: konsole: Starting konsole from menu or krunner does not work anymore

[Maximiliano Curia]

Control: forcemerge 841502 843551

This issue was already reported in 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841502

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

I'm merging the reports.

¡Hola M!

El 2016-11-07 a las 18:43 +0100, M G Berberich escribió:
Package: konsole 
Version: 4:16.08.2-1.1 
Severity: important


starting konsole from start-menu or krunner is totaly broken. 
Sometimes it starts a konsole with the last used profile instead of the default profile, mostly nothing happens at all. 
Starting a xterm and then starting konsole from xterm works.



There exists a fix from Martin T. H. Sandsmark:
https://quickgit.kde.org/?p=konsole.git=commit=4ec9b565800b9e9bdbf45dbb5983530fb95791e7


I was testing this fix, it seems to work.

Happy hacking,
--
"If I ask another professor what he teaches in the introductory programming
course, whether he answers proudly "Pascal" or diffidently "FORTRAN," I know
that he is teaching a grammar, a set of semantic rules, and some finished
algorithms, leaving the students to discover, on their own, some process of
design."
-- Robert W. Floyd
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#843506: libosinfo-1.0-0: Please bump libosinfo-l10n dependency to Depends or Recommends

[Guido Günther]

Hi Laurent,
On Mon, Nov 07, 2016 at 08:17:53AM +0100, Laurent Bigonville wrote:
> Package: libosinfo-1.0-0
> Version: 1.0.0-2
> Severity: normal
> 
> Hi,
> 
> Shouldn't the dependency against libosinfo-l10n be bumped to a Depends
> or at least a Recommends?
> 
> Suggested packages are not installed by default and I feel that
> translation might be important enough for some users

TBH I'm not sure. While icedove and firefox don't even suggest l10n
libreoffice recommends it.

Policy has not word about this so there doesn't seem to be common
practive.

There are lots of uses where l10n for libosinfo is not needed so I'm
inclined to leave it as is.
Cheers,
 -- Guido

Bug#645334: [Pkg-libvirt-maintainers] Bug#645334: support for manipulating the command line directly

[Guido Günther]

Hi,
On Mon, Nov 07, 2016 at 11:50:33AM +0100, Odd Martin Baanrud wrote:
> Hello,
> 
> > On 07 Nov 2016, at 08:22, Guido Günther  wrote:
> > 
> > Supporting brltty would be great but we must not add hacks for that. It
> > needs to be added as a device to libvirt and can then be exposed to
> > virt-manager/virtinst which can then auto add it if the host has brltty.
> 
> I understand.
> I thaught it needed to be done that way.
> Are you able to add it in the Debian package, or does it need to be 
> implemented upstream?
> If you could make a Debian fix, it would be nice to see it in Stretch, if 
> possible.

Since this needs new domain XML we should do this upstream to not create
a incompatible domain format. In case you want to help filing an
upstream bug would already help:

https://bugzilla.redhat.com/enter_bug.cgi?product=Virtualization 
Tools=libvirt

Cheers,
 -- Guido

Bug#838176: mcabber: please update the package to the latest release

[Anatoly A. Kazantsev]

Hello,

On Tue, 11 Oct 2016 19:51:16 +1300
"Anatoly A. Kazantsev"  wrote:

> On Sun, 9 Oct 2016 09:57:21 +0200
> Franziska Lichtblau  wrote:
> 
> > My view is that I'd like to move the git to alioth[1] and make it a
> > collab-maint project[2]. This makes it much easier to give people access to
> > the git repository and push their work there. So you'd need to go and
> > create a guest account and apply for access to the collab-maint project.
> 
> I've registered on alioth under anatoly-guest name. Please send a signed 
> email to n...@debian.org as stated on [1]

Just checked my account page on alioth and I haven't been assigned to
collab-maint project yet.

It seems we got stuck again :-)

-- 
Regards,
Anatoly

Bug#842555: QA upload

[gustavo panizzo (gfa)]

On Sun, Nov 06, 2016 at 07:58:14AM +0300, Dmitry Bogatov wrote:
> 
> [2016-11-03 09:37] "gustavo panizzo (gfa)" 
> >
> > I intend to do a QA upload for this package soon, if anybody wants to be
> > the real maintainer, ping me I can handover my improvements to you
> 
> Hello! I am interested in tsocks maintainership and your improvements.

Hello,

I'm sending my updates to my sponsor who will upload the package, after
that is yours to take it.

I'll defer to you decisions around some bugs I'd like to fix but I
think is better if a maintainer decides instead of a QA upload

# 616121
# 480119

cheers!


-- 
1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333

keybase: https://keybase.io/gfa

Bug#843610: xscreensaver should ship a systemd user .service instead of just documenting it in xscreensaver(1)

[Daniel Kahn Gillmor]

Package: xscreensaver
Version: 5.34-2
Severity: wishlist

xscreensaver(1) says:

--
USING SYSTEMD
   If  the  above  didn't do it, and your system has systemd(1), then give
   this a try:

   1: Create a service.
  Create the file ~/.config/systemd/user/xscreensaver.service contain‐
  ing:
  [Unit]
  Description=XScreenSaver
  [Service]
  ExecStart=xscreensaver
  [Install]
  WantedBy=default.target
  2. Enable it.
  systemctl --user enable xscreensaver
  Then restart X11.
--

It would be better to ship this file as
/usr/lib/systemd/user/xscreensaver.service, and just tell the user to:

   systemctl --user enable xscreensaver

rather than making them copy and paste.

Thanks for maintaining xscreensaver for debian!

Regards,

--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.7.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 xscreensaver depends on:
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-5
ii  libcairo21.14.6-1+b1
ii  libfontconfig1   2.11.0-6.7
ii  libfreetype6 2.6.3-3+b1
ii  libgdk-pixbuf2.0-0   2.36.0-1
ii  libglade2-0  1:2.6.4-2
ii  libglib2.0-0 2.50.1-1
ii  libgtk2.0-0  2.24.31-1
ii  libice6  2:1.0.9-1+b1
ii  libpam0g 1.1.8-3.3
ii  libpango-1.0-0   1.40.3-2
ii  libpangocairo-1.0-0  1.40.3-2
ii  libpangoft2-1.0-01.40.3-2
ii  libsm6   2:1.2.2-1+b1
ii  libx11-6 2:1.6.3-1
ii  libxext6 2:1.3.3-1
ii  libxi6   2:1.7.6-1
ii  libxinerama1 2:1.1.3-1+b1
ii  libxml2  2.9.4+dfsg1-2.1
ii  libxmu6  2:1.1.2-2
ii  libxpm4  1:3.5.11-1+b1
ii  libxrandr2   2:1.5.0-1
ii  libxrender1  1:0.9.9-2
ii  libxt6   1:1.1.5-1
ii  libxxf86vm1  1:1.1.4-1
ii  xscreensaver-data5.34-2

Versions of packages xscreensaver recommends:
ii  libgnomeui-0 2.24.5-3.1
ii  libjpeg-turbo-progs [libjpeg-progs]  1:1.5.1-2
pn  perl5
ii  wamerican [wordlist] 7.1-1
ii  witalian [wordlist]  1.7.6

Versions of packages xscreensaver suggests:
ii  chromium [www-browser]  53.0.2785.143-1
ii  elinks [www-browser]0.12~pre6-12
ii  epiphany-browser [www-browser]  3.22.1-2
ii  firefox [www-browser]   49.0-5
ii  firefox-esr [www-browser]   45.4.0esr-2
ii  fortune-mod [fortune]   1:1.99.1-7
pn  gdm3 | kdm-gdmcompat
ii  links [www-browser] 2.13-1
ii  lynx [www-browser]  2.8.9dev9-1
pn  qcam | streamer 
ii  w3m [www-browser]   0.5.3-32
pn  xdaliclock  
pn  xfishtank   
pn  xscreensaver-gl 

-- no debconf information

Bug#840575: [buildd-tools-devel] Bug#840575: sbuild bpo: uses non-available option gnupg --pinentry-mode

[Daniel Kahn Gillmor]

On Thu 2016-11-03 06:56:21 -0600, Luca Falavigna wrote:
> 2016-11-03 13:41 GMT+01:00 Thomas Goirand :
>> dkg, you had the intention to upload gnupg 2.1 to backports. Is there
>> anything that's holding it?
>>
>> Lucas, could you upload a version of sbuild to BPO without this hard
>> requirement, and maybe with the fix I suggested for the keygen thing?
>> While not the definitive solution, this would fix it in the mean time.
>
> If Daniel is willing to upload gnupg2, that would be cool! Otherwise
> I'll try to see which other alternatives we have.

I'd be happy to upload gnupg2 2.1.15-8 to backports, but it's currently
not migrating to testing, i think because of the current udeb freeze (we
have gpgv-udeb).  I'm adding kibi to the cc list here to see whether
that's something he's ok with unblocking.

   --dkg


signature.asc
Description: PGP signature

Bug#842015: Merging bugs about pinentry failing without GNOME-connected d-bus

[Daniel Kahn Gillmor]

On Sun 2016-11-06 04:25:27 -0500, Vincent Lefevre  wrote:
> On 2016-11-06 01:13:53 -0500, Daniel Kahn Gillmor wrote:
>> If you want a pinentry that only speaks curses (and never tries to
>> integrate with a gnome3 session), you should install pinentry-curses and
>> either remove pinentry-gnome3, or place "pinentry-program
>> /usr/bin/pinentry-curses" in your gpg-agent.conf.
>
> I expect that the fallback to curses be automatic.

It is indeed automatic -- it falls back when it is unable to communicate
with a gnome3 prompter, which happens via d-bus.

>> One additional exacerbating factor that you're seeing is probably due to
>> the fact that pinentry-gnome3 doesn't currently respect the default
>> timeout.
>
> No, this is not a timeout issue, as a window is opened on the
> X display, while it should never do that when DISPLAY is unset.

DISPLAY has nothing to do with how pinentry-gnome3 works.
pinentry-gnome3 does not communicate with any X11 session -- it
communicates with a d-bus session.

>> Can you explain what you'd rather happen here?
>
> I don't use GNOME at all, so this isn't this scenario. But the above
> would not be OK for GNOME & SSH users anyway. IMHO, what matters is
> whether DISPLAY is set or not, and its value when it is set.

It sounds like you are expecting the beahvior of pinentry-gtk-2 (which
does indeed talk directly to an X11 display), but using pinentry-gnome3
instead (which talks instead to a d-bus session).  We could make
pinentry-gnome3 test for the presence of DISPLAY, and fall back if it is
unset, but why would we do this, if pinentry-gnome3 doesn't even assume
X11?  If a user runs gnome3 in some non-x11 environment (wayland?  i
don't know specifically), should pinentry-gnome3 fall back to curses,
even when it can provide a graphical prompt?

Perhaps you mean to be using pinentry-gtk-2?

Still at a loss as to how to resolve this bug report satisfactorily,

--dkg



signature.asc
Description: PGP signature

Bug#839563: opendmarc-expires fails with "Use of uninitialized value in concatenation"

[Scott Kitterman]

On Sun, 02 Oct 2016 04:05:53 +0200 Stefan Tittel  
wrote:
> Package: opendmarc
> Version: 1.3.0+dfsg-1
> Severity: important
> Tags: upstream
> 
> Running /usr/sbin/opendmarc-expire on a fresh opendmarc installations fails 
as follows:
> 
> opendmarc-expire: started at Sun Oct  2 03:59:48 2016
> opendmarc-expire: connected to database
> opendmarc-expire: expiring messages older than 180 day(s)
> opendmarc-expire: no rows deleted
> Use of uninitialized value in concatenation (.) or string at 
/usr/sbin/opendmarc-expire line 291.
> opendmarc-expire: TRUNCATE failed:
> 
> The cause of this bug is a missing exclamation mark in /usr/sbin/opendmarc-
expire.
> 
> The problem has recently been fixed by upsteam (including a patch):
> https://sourceforge.net/p/opendmarc/tickets/143/

This is included in the 1.3.2 pre-release currently in Testing.

Scott K

Bug#843608: mini-buildd: reprepro not recognizing .buildinfo file, causing upload failure

[Boyuan Yang]

Source: mini-buildd
Severity: important
Tags: upstream

Upstream bug #843402.

Example logs here:

2016-11-08 13:29:16,100 mini_buildd.call (0114): WARNING : ?
reprepro.. (stderr): Unknown file type: 'd882b1dff57c2e8d722fa1e67599a410 9716
libs extra libqtshadowsocks_1.9.0-1.1_20161108T052651z-d882b1df.buildinfo',
assuming source format...
2016-11-08 13:29:16,100 mini_buildd.call (0114): WARNING : ?
reprepro.. (stderr): 'libqtshadowsocks_1.9.0-1.1_20161108T052651z-
d882b1df.buildinfo' looks like part of an source package, but no dsc file
listed in the .changes file!
2016-11-08 13:29:16,100 mini_buildd.call (0114): WARNING : ?
reprepro.. (stderr): There have been errors!



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

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

Bug#843607: certbot: Unknown lvalue 'RandomizedDelaySec' in section 'Timer'

[Kazuhiro NISHIYAMA]

Package: certbot
Version: 0.9.3-1~bpo8+1
Severity: normal

Dear Maintainer,

After upgrade to 0.9.3-1~bpo8+1,
systemd message in log:
systemd[1]: [/lib/systemd/system/certbot.timer:6] Unknown lvalue 
'RandomizedDelaySec' in section 'Timer'

And certbot.service runs without any random sleep.

I think 'RandomizedDelaySec' is not supported by jessie's systemd.

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

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

Versions of packages certbot depends on:
ii  dialog   1.2-20140911-1
ii  init-system-helpers  1.22
ii  python   2.7.9-1
ii  python-certbot   0.9.3-1~bpo8+1
pn  python:any   

certbot recommends no packages.

Versions of packages certbot suggests:
pn  python-certbot-apache  
pn  python-certbot-doc 

-- no debconf information

Bug#843606: reprepro FTCBFS: sbuild/apt fails to install pinentry-curses:$DEB_HOST_ARCH

[Helmut Grohne]

Source: reprepro
Version: 4.17.1-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

reprepro fails to cross build from source, because sbuild and/or apt
fail to install its pinentry-curses build dependency. I couldn't figure
out why that is the case and dose-builddebcheck claims that dependency
to be satisfiable. The error message from sbuild is:

| sbuild-build-depends-reprepro-dummy:armel : Depends: pinentry-curses:armel 
but it is not going to be installed

In any case, I looked at the reason for adding that dependency and it
was added for avoiding pinentry-gtk2. Nowadays, that problem has been
fixed, so dropping the pinentry-curses dependency looks sane to me. Even
better: No pinentry is installed at all. And the best part is: After
removing pinentry-curses, reprepro just cross builds.

Please consider applying the attached patch. Maybe you also want to
remove pinentry-curses from the runtime dependencies.

Helmut
diff --minimal -Nru reprepro-4.17.1/debian/changelog 
reprepro-4.17.1/debian/changelog
--- reprepro-4.17.1/debian/changelog2016-04-30 15:32:28.0 +0200
+++ reprepro-4.17.1/debian/changelog2016-11-08 06:08:01.0 +0100
@@ -1,3 +1,11 @@
+reprepro (4.17.1-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Drop pinentry-curses from Build-Depends as pinentry-gtk is no
+longer pulled and apt fails to satisfy this dependency (Closes: #-1)
+
+ -- Helmut Grohne   Tue, 08 Nov 2016 06:08:01 +0100
+
 reprepro (4.17.1-1) unstable; urgency=medium
 
   * new bugfix release
diff --minimal -Nru reprepro-4.17.1/debian/control 
reprepro-4.17.1/debian/control
--- reprepro-4.17.1/debian/control  2016-04-30 15:29:44.0 +0200
+++ reprepro-4.17.1/debian/control  2016-11-08 06:07:58.0 +0100
@@ -2,7 +2,7 @@
 Section: utils
 Priority: extra
 Maintainer: Bernhard R. Link 
-Build-Depends: debhelper (>= 7), pinentry-curses, libgpgme11-dev, libdb-dev, 
libz-dev, libbz2-dev, liblzma-dev, libarchive-dev
+Build-Depends: debhelper (>= 7), libgpgme11-dev, libdb-dev, libz-dev, 
libbz2-dev, liblzma-dev, libarchive-dev
 Standards-Version: 3.9.6
 Vcs-Browser: http://anonscm.debian.org/cgit/mirrorer/reprepro.git/log/?h=debian
 Vcs-Git: https://anonscm.debian.org/git/mirrorer/reprepro.git -b debian

Bug#841294: Overrule maintainer of "global" to package a new upstream version

[Ron]

On Mon, Nov 07, 2016 at 12:09:21PM -0800, Nikolaus Rath wrote:
> On Nov 07 2016, Ron  wrote:
> 
> > I've taken the time to repeat this all again now, because regardless
> > of how it got here, I actually have some faith in the new face of the
> > TC as a forum for building 'project wide' consensus around hard problems.
> > Having read all of that, Phil has now asked me to propose a concrete
> > alternative to what he suggested, which I did. And I think the important
> > difference is that we have the opportunity to build a consensus here
> > which includes a good proportion of impartial and non-partisan voices who
> > weighed up all the options like I've been doing.
> 
> It seems you're only interested in impartial and non-partisan voices
> when they happen to back your position. I am impartial and non-partisan,
> and formed my opinion by reading the bugs and your emails.

And "your opinion" still hasn't said even a single word to show that you
understand the technical problem here, or to offer any solution to it.
The problem which doesn't just magically go away regardless of who might
implement it.

And now you say that apparently you didn't even read the conversation that
you interjected into enough to notice that Phil and I were having a civil
discussion precisely on the _difference_ we saw in ways that this might be
'solved' ...

All you did was dismiss and (continue to) try to side track that.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841294#155
(for anyone who missed it before people tried to bury it piling on to
the man again)


> If you indeed welcome opinions from people like me, your statements
> above are a little odd.

I think you missed the bit about "comprehending the problem and building
consensus on solutions" - because if this is all you have to offer then
no, "opinions" from people "like you" are neither helpful nor welcome.
Even if they 100% agree with me.  They are just a toxic symptom of people
still ignoring the hard technical problem.


Which is very different from the suggestions of people, say, "like Phil",
where no matter how much we disagree at the outset, we can still focus
that on looking at the merits of ways to solve the problem as best we
can in the circumstances that we have.  And try to come to some sort of
best consensus on it.

When you understand that distinction, and have something we've all missed
to contribute, _then_ you'll be welcome, whoever you're disagreeing with.

If all you want to do is play "Trump school of debate", then please take
that somewhere else, and leave this thread to focus on the technical
details of _what_ we ought to do.  If we don't solve that, then who does
it is kind of irrelevant, there'll still be a Hard Problem that someone
won't be happy with.


  Ron

Bug#843215: fwupd: Please announce supported hardware using appstream

[Paul Wise]

On Mon, 2016-11-07 at 19:26 +, Mario Limonciello wrote:

> That's a chicken and egg problem unfortunately.  This type of information is
> dependent upon the machine that fwupd is running on and can't be determined
> at build time.

I was mainly talking about the devices that can be found in this file:

/lib/udev/rules.d/90-fwupd-devices.rules

Those are a static set of devices not determined at runtime.
I guess for those, prompting the user to install fwupd is a good idea.

> If fwupd can be included by default in Debian I think a better experience can
> be had though.

For proprietary platforms that seems like a reasonable idea but for
fairly open platforms like ARM/etc, I would much prefer all firmware to
be packaged for Debian and flashed using flash-kernel or similar.

> So for now I think it would be better for isenkram to do one of these:
> 1) Query fwupd for updatable objects if it's installed.

That sounds like a good idea, could you file a bug with the details?
I am not aware how that should work.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#842965: 4.08 regression: gaps between the xterms

[tony mancill]

Hello Harald,

Thank you for the bug report and the pointer.  I will get this
addressed with a new Debian upload soon.

Cheers,
tony

On Mon, Nov 7, 2016 at 12:00 AM, Harald Dunkel  wrote:
> PS: See the comments in
>
> https://github.com/duncs/clusterssh/pull/66
>
> It would be very nice if you could back out pull 66 for
> the Debian version.

Bug#843605: lives: remove Harry Rickards from uploaders

[Paul Wise]

Source: lives
Severity: wishlist
X-Debbugs-CC: m...@qa.debian.org, w...@debian.org

This person doesn't appear to be active on lives and the Debian wiki
got a bounce mail saying that the email address no longer exists.
Please remove them from the Uploaders field of this package.

Harry Rickards 

MIA team: they don't appear to maintain any other packages.

https://qa.debian.org/developer.php?login=Harry%20Rickards

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#843559: works

[Ivan Sergio Borgonovo]

Thanks for the upload, it works.

It seems you could close the bug

--
Ivan Sergio Borgonovo
http://www.webthatworks.it http://www.borgonovo.net

Bug#843493: bsdutils: /usr/bin/logger writes to systemd journal

[Charles]

Hello Andreas Henriksson

On 07/11/16 18:36, Andreas Henriksson wrote:

On Mon, Nov 07, 2016 at 04:16:16PM +0530, Charles wrote:



The logger man page says "logger - a shell command interface to the
syslog(3) system log module".  man 3 syslog says "syslog() generates a log
message, which will be distributed by syslogd(8).  There is no man
syslogd(8).  man 8 rsyslogd says see also rsyslog.conf(5).  man 5
rsyslog.conf lists /etc/rsyslog.conf as the default configuration file.

/etc/rsyslog.conf has nothing in it which I understand effects copying
messages to the systemd journal or to the "kernel log buffer" (a term which
I am not familiar with):


Yes, first the syslog(3) system call is something completely different
from a syslog daemon/server implementation! Maybe they are unfortunately
named too similarly but they've been named like this for decades and are
unlikely to be renamed. You'll just have to learn what they do.


man 3 syslog says "syslog() generates a log message, which will be 
distributed by syslogd(8)




Regards,
Andreas



What about the change of PID in the tag value provided to the logger 
call?  That question is regards these mail excerpts which show the tag 
value was set with PID 20892 and appeared in the systemd journal with 
PID 20893:


>> The situation was reproduced by running this script:
>> #!/bin/bash
>> echo $$
>> logger -t "task3092.sh[$$]" 'Test message'
>>
>> The outcome was reproduced by:
>> # ./task3092.sh
>> 20892
>> # tail -1 /var/log/syslog
>> Nov  7 08:35:36 sysmgt.iciti task3092.sh[20892]: Test message
>> # journalctl | grep task3092
>> Nov 07 08:35:36 sysmgt task3092.sh[20893]: Test message
>> Given that the messsage did appear in the systemd journal, the expected
>> outcome was:
>> 1. It had the specified tag, not one with an altered PID
>> 2. It had a systemd journal format preamble, not syslog format
>
> Not sure what you're saying here really, but if you want to alter
> which meta-data is fetched from the journal for each message
> just see the journalctl manpage for which options to use.

1. The logger's -t option value had the PID of the calling process as is 
conventional for syslog messages.  The syslog message showed it.  The 
journal message showed a different PID.

Bug#843565: ifupdown2: Unsupported keyword (wpa-ssid) (wpa-psk) after upgrade to 1.0~git20161101-1

[Roopa Prabhu]

It appears we have enabled a config that should have been off by default for 
debian ifupdown scripts.
Please set the attribute addon_syntax_check=0 in ifupdown2.conf to disable 
syntax checking.

/etc/network/ifupdown2/ifupdown2.conf
# enable addon module syntax check:
# Python addon modules register dictionary of supported attributes.
# The syntax checker in ifupdown2 uses this dictionary for syntax
# checks in the interfaces file. This works well, when only python modules
# are used. But when a mix of scripts and modules are used (which is the
# default case), you may get false warnings for attributes supported
# by scripts
addon_syntax_check=1

we will submit a fix to set it to 0 by default 'addon_syntax_check=0' so that 
it does not break
existing deployments or files.

Thanks for the report. And please let us know if you continue seeing problems 
with addon_syntax_check=0



On 11/7/16, 4:47 PM, Julien Fortin wrote:
> Hello Jacek,
>
> Thanks for reporting this issue, I will look into it this week and get back
> to you accordingly.
>
> Regards,
> Julien.
>
> On Mon, Nov 7, 2016 at 8:34 PM, Jacek Politowski  wrote:
>
>> Package: ifupdown2
>> Version: 1.0~git20161101-1
>> Severity: important
>>
>> Dear Maintainer,
>>
>> after recent upgrade (ifupdown2:amd64 1.0~git20160525-1 ->
>> 1.0~git20161101-1)
>> my WLAN network interface stopped working. Ifupdown gives error messages
>> about
>> unsupported keywords in 'interfaces' configuration file.
>>
>> My configuration was made according to this guide:
>> https://wiki.debian.org/WiFi/HowToUse#WPA-PSK_and_WPA2-PSK
>>
>>
>> $ sudo ifup wlxABCDEFGHI
>> error: /etc/network/interfaces.d/wlxABCDEFGHI: line3: iface wlxABCDEFGHI:
>> unsupported keyword (wpa-ssid)
>> error: /etc/network/interfaces.d/wlxABCDEFGHI: line4: iface wlxABCDEFGHI:
>> unsupported keyword (wpa-psk)
>>
>>
>> I can't see anything related in changelog.Debian or similar files in
>> /usr/share/doc/ifupdown2.
>>
>> However, downgrading to version 1.0~git20160525-1 (from Stretch) brings
>> everything back to order.
>> 'ifup' doesn't complain and my ath9k works as expected.
>>
>>
>> -- System Information:
>> Debian Release: stretch/sid
>>   APT prefers unstable
>>   APT policy: (500, 'unstable'), (1, 'experimental')
>> Architecture: amd64 (x86_64)
>> Foreign Architectures: i386
>>
>> Kernel: Linux 4.8.0-1-amd64 (SMP w/2 CPU cores)
>> Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
>> Shell: /bin/sh linked to /bin/dash
>> Init: systemd (via /run/systemd/system)
>>
>> Versions of packages ifupdown2 depends on:
>> ii  init-system-helpers  1.46
>> ii  python-argcomplete   1.4.1-0.1
>> ii  python-ipaddr2.1.11-2
>> pn  python:any   
>>
>> ifupdown2 recommends no packages.
>>
>> Versions of packages ifupdown2 suggests:
>> ii  python-gvgen  0.9-2
>> ii  python-mako   1.0.4+ds1-2
>>
>> -- no debconf information
>>

Bug#841248: opencfu: FTBFS: error with opencv 3.1

[Nobuhiro Iwamatsu]

Control: tags -1 patch

Hi,

I created a patch from upstream repository which revice this problem.
Could you check this patch?

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


opencfu.debdiff
Description: Binary data

Bug#843604: RFS: xerces-c/3.1.4+debian-1 [RC]

[Bill Blough]

Package: sponsorship-requests
Severity: important

Dear mentors,

  I am looking for a sponsor for my package "xerces-c"

 * Package name: xerces-c
   Version : 3.1.4+debian-1
   Upstream Author : Xerces-C developers 
 * URL : https://xerces.apache.org/xerces-c/
 * License : Apache 2.0
   Section : libs

  It builds those binary packages:

 libxerces-c-dev - validating XML parser library for C++ (development files)
 libxerces-c-doc - validating XML parser library for C++ (documentation)
 libxerces-c-samples - validating XML parser library for C++ (compiled samples)
 libxerces-c3.1 - validating XML parser library for C++

  To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/xerces-c


  Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/x/xerces-c/xerces-c_3.1.4+debian-1.dsc

  More information about hello can be obtained from 
https://xerces.apache.org/xerces-c/

  Changes since the last upload:

  * New upstream release
  * Removed patches that are no longer needed (applied upstream)
  * Compile with curl support to allow accessing https urls.  Closes: #821380
  * Added patch to fix some compiler warnings (forwarded upstream)

  In addition, I'm hopeful that the new upstream release will resolve the
  FTBFS issue on s390x (bug 833754), however I don't know that for sure.

  Regards,
   Bill Blough

Bug#841411: libkf5kface: FTBFS: error with opencv 3.1

[Nobuhiro Iwamatsu]

Hi!

2016-10-22 17:53 GMT+09:00 Maximiliano Curia :
> ¡Hola Nobuhiro!
>
> El 2016-10-22 a las 17:22 +0900, Nobuhiro Iwamatsu escribió:
>>
>> The contrib module does not provides by opencv 3.1, this module obsoleted.
>> We need to update CMakeLists.txt of libkf5kface and use
>> "-DENABLE_OPENCV3=ON" to flag for cmake.
>
>
> Ah, good point.
>
>> CMakeLists.txt :
>> 82 if(ENABLE_OPENCV3) 83 84 set(OPENCV_MIN_VERSION "3.0.0") 85
>> DETECT_OPENCV(${OPENCV_MIN_VERSION} core face highgui objdetect imgproc)
>
>
> This uses the opencv_face module, I guess this mudule used to be part of the
> contrib one.
>
> Anyway, the face module is not currently included in the opencv 3.1
> packages.
>
> Could you add it?

Thanks for your pointing.
I worked about this on with-contrib branch, but I think this work too
late about transiton.
  
https://anonscm.debian.org/cgit/debian-science/packages/opencv.git/log/?h=with-contrib

>
>> 87 if(${OpenCV_FOUND}) 88 if(${OpenCV_VERSION} VERSION_LESS
>> 3.0.0) 89 message(STATUS "ENABLE_OPENCV3 option is enabled and
>> OpenCV < 3.0.0 have been found. Disabled ENABLE_OPENCV3") 90
>> set(OpenCV_FOUND FALSE) 91 endif() 92 endif() 93 94 else()
>
>
> Happy hacking,
> --
> "If you optimize everything, you will always be unhappy."
> -- Donald Knuth
>
> Saludos /\/\ /\ >< `/

Best regards,
  Nobuhiro


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

Bug#841287: saga: FTBFS: error with opencv 3.1

[Nobuhiro Iwamatsu]

Hi,

I update patch for opencv transition.
If we apply this patch, we can migrate using binNMU smoothly.

Best regards,
  Nobuhiro

2016-10-20 6:05 GMT+09:00 Nobuhiro Iwamatsu :
> Hi!
>
> Thanks for your reply.
> 2016-10-20 3:30 GMT+09:00 Sebastiaan Couwenberg :
>> Hi Nobuhiro,
>>
>> Thanks for your work on OpenCV and reporting this issue.
>>
>> On 10/19/2016 01:21 PM, Nobuhiro Iwamatsu wrote:
>>> I am scheduled to transition of opencv, and this package is target to
>>> transition.
>>> So I tested build with opencv 3.1.As a result, this FTBFS with opencv 3.1.
>>> Because libcv-dev, ibopencv-contrib-dev and libopencv-legacy-dev has been
>>> removed from opencv 3.1 package.
>>>
>>> [...]
>>>
>>> I attached a patch that revice this problem.
>>> Could you check this patch and apply?
>>
>> The patch is incomplete as it removes libcv-dev from the build
>> dependencies, but doesn't add libopencv-dev to which opencv/cv.h has
>> been moved.
>
> Oh, sorry. I send other patch.
> As you say, we need to add libopencv-dev to B-D.
>
>>
>> Since we cannot adapt the saga package for 3.1 until the transition
>> starts, we'll need to apply the changes when the transition starts and
>> do a new upload.
>
> no problem.
>
>>
>> Have you considered transitional packages for the removed -dev packages
>> to not require changes to the opencv reverse dependencies and have
>> binNMUs suffice for the transition?
>>
>
> I am working about that.
> I finished the investigation of the packages that depend on opencv, I
> will make it
> easier to migrate, and bug reports to the package there is a problem.
>
>> Kind Regards,
>>
> Best regards,
>   Nobuhiro
>
> --
> Nobuhiro Iwamatsu
>iwamatsu at {nigauri.org / debian.org}
>GPG ID: 40AD1FA6



-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6
diff --git a/debian/control b/debian/control
index ba73127..da565a7 100644
--- a/debian/control
+++ b/debian/control
@@ -6,16 +6,16 @@ Section: science
 Priority: optional
 Build-Depends: debhelper (>= 9),
dh-autoreconf,
-   libcv-dev,
+   libopencv-dev | libcv-dev,
libdxflib-dev,
libexpat-dev,
libgdal-dev,
libhpdf-dev,
libogdi3.2-dev,
-   libopencv-contrib-dev,
+   libopencv-dev | libopencv-contrib-dev,
libopencv-core-dev,
libopencv-imgproc-dev,
-   libopencv-legacy-dev,
+   libopencv-dev | libopencv-legacy-dev,
libopencv-photo-dev,
libproj-dev,
libqhull-dev,
-- 
2.9.3

Bug#831236: klog: FTBFS: dh_install: missing files, aborting

[FanJun Kong]

Hi

fixed and upload package here:
https://mentors.debian.net/package/klog

Jaime, could you help me to review it?

Thanks very much

FanJun Kong
BH1SCW

Bug#843603: openssl fails on sid version to handshake with tls_1.2 to postfix echos ssl_errors

[supp...@opensource-systems.com]

Package: openssl
Version: 1.0.2j-1
Severity: important

Dear Maintainer,


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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?


 openssl of Sid fails handshake with postfix and echos ssl_error on mail.log, 
no mail
 can be send with TLS_1.2 on Port 465

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



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

Kernel: Linux 4.8.3-x86_64-linode76 (SMP w/1 CPU core)
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)

Versions of packages openssl depends on:
ii  libc62.24-5
ii  libssl1.0.2  1.0.2j-4

openssl recommends no packages.

Versions of packages openssl suggests:
ii  ca-certificates  20161102

-- no debconf information

Bug#843602: systemd service file ignores /etc/default/nfdump

[Alexander Zangerl]

Package: nfdump
Version: 1.6.15-3
Severity: normal

this version of the nfdump package includes a systemd service file
that completely ignores /etc/default/nfdump. it makes it impossible to
adjust the listener port, the database directory or any of the other common
options of the nfcapd.

most of those options are supported normally by the init script
for nfcapd/nfdump (which is also included). (not highly important but would be
nice to have: could you maybe add support for something like
-p $NETFLOW_PORT -t $DATA_ROTATE_INTERVAL ?)

please make the behaviour wrt. /etc/default/nfdump consistent across
all supported init systems.

regards
az

Bug#843601: phantomjs: Missing file for unlock-qt.patch in debian sources

[Juan Carlos Romero]

Package: phantomjs
Severity: normal

Dear Maintainer,

You have forgotten to include the file unlock-qt.patch, so the package
doesn't build.

Regards.

Bug#843565: ifupdown2: Unsupported keyword (wpa-ssid) (wpa-psk) after upgrade to 1.0~git20161101-1

[Julien Fortin]

Hello Jacek,

Thanks for reporting this issue, I will look into it this week and get back
to you accordingly.

Regards,
Julien.

On Mon, Nov 7, 2016 at 8:34 PM, Jacek Politowski  wrote:

> Package: ifupdown2
> Version: 1.0~git20161101-1
> Severity: important
>
> Dear Maintainer,
>
> after recent upgrade (ifupdown2:amd64 1.0~git20160525-1 ->
> 1.0~git20161101-1)
> my WLAN network interface stopped working. Ifupdown gives error messages
> about
> unsupported keywords in 'interfaces' configuration file.
>
> My configuration was made according to this guide:
> https://wiki.debian.org/WiFi/HowToUse#WPA-PSK_and_WPA2-PSK
>
>
> $ sudo ifup wlxABCDEFGHI
> error: /etc/network/interfaces.d/wlxABCDEFGHI: line3: iface wlxABCDEFGHI:
> unsupported keyword (wpa-ssid)
> error: /etc/network/interfaces.d/wlxABCDEFGHI: line4: iface wlxABCDEFGHI:
> unsupported keyword (wpa-psk)
>
>
> I can't see anything related in changelog.Debian or similar files in
> /usr/share/doc/ifupdown2.
>
> However, downgrading to version 1.0~git20160525-1 (from Stretch) brings
> everything back to order.
> 'ifup' doesn't complain and my ath9k works as expected.
>
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.8.0-1-amd64 (SMP w/2 CPU cores)
> Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages ifupdown2 depends on:
> ii  init-system-helpers  1.46
> ii  python-argcomplete   1.4.1-0.1
> ii  python-ipaddr2.1.11-2
> pn  python:any   
>
> ifupdown2 recommends no packages.
>
> Versions of packages ifupdown2 suggests:
> ii  python-gvgen  0.9-2
> ii  python-mako   1.0.4+ds1-2
>
> -- no debconf information
>

Bug#766461: gitg: upload 3.22 to unstable

[Michael Biebl]

On Fri, 14 Oct 2016 19:51:47 +0200 =?utf-8?b?SsOpcsOpbXkgTGFs?=
 wrote:
> Package: gitg
> Followup-For: Bug #766461
> 
> Hi Dmitry,
> 
> just a few words to say that i'm having an incredibly good
> user experience with gitg 3.22.
> It's fast, it's packed with wonderful features (uncomparably
> better than old 0.2.7 version) and upstream seems to be
> going in a very pragmatic direction.
> If you need any help maintaining libgit2-glib/gitg, please
> do not hesitate to ask.
> 

I can only second this. I find the new interface much more pleasant.

Dmitry, it would be great if you can upload this version to unstable.

What can we do to move this forward?
I don't think it makes sense to block new upstream releases forever
because of personal disagreements on what upstream is doing.
At some point, Dmitry, you have to fork gitg and maybe ship it as
gitg-legacy.

It would be a shame if we shipped stretch with a horribly outdated
version of gitg.

Michael

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



signature.asc
Description: OpenPGP digital signature

Bug#843597: More robust capability handling

[Sam Hartman]

> "Thomas" == Thomas Lange  writes:

> On Mon, 07 Nov 2016 17:36:41 -0500, Sam Hartman
>> Currently, the sample configuration namespace has a shell script
>> to restore the common capabilities found in base files; see
>> scripts/DEBIAN/20-capabilities.
Thomas> In this script, I'm doing the same things that are done in
Thomas> the postinst script of the package.

No, you're doing what the postinst script did on the day you wrote that
config script.
First, there's no guarantee that you'll notice when the packages in
question change.
Secondly, even if you do update the examples, each FAI user has to
update every one of their configuration spaces.
That tends to produce unexpected behavior over time.

Thomas> Also there was a bug in tar which added some xattr or
Thomas> capabilities even no were defined when creating the tar
Thomas> file. Have a look at #819978. IIRC this was one reason to no
Thomas> use xattrs with tar by default.  -- regards Thomas

That seems to be dealing with --acls not --xattrs
--xattrs-include=security.capability.

At least with the stretch tar, I do not get default ACLs when I use
--xattrs --xattrs-include=security.capability.

Bug#843600: checkbashishm should warn about trap with SIG-something names

[Carlos Alberto Lopez Perez]

Package: devscripts
Version: 2.16.8

Hi,

It seems that referring to the signals with a SIG prefix is not
something that has to be supported by the POSIX standard:


​http://pubs.opengroup.org/onlinepubs/95399/utilities/trap.html:

RATIONALE

Implementations may permit lowercase signal names as an extension.
Implementations may also accept the names with the SIG prefix; no known
historical shell does so. The trap and kill utilities in this volume of
IEEE Std 1003.1-2001 are now consistent in their omission of the SIG
prefix for signal names. Some kill implementations do not allow the
prefix, and kill -l lists the signals without prefixes.

Trapping SIGKILL or SIGSTOP is syntactically accepted by some
historical implementations, but it has no effect. Portable POSIX
applications cannot attempt to trap these signals.


And this is major problem, because our default /bin/sh (dash) fails to
run scripts using SIGSOMETHING.


Check this example:


$ cat test.sh
#/bin/sh
trap "echo hi from int" SIGINT
kill -INT $$

$ bash test.sh
hi from int

$ dash test.sh
trap: SIGINT: bad trap

$ sh test.sh
trap: SIGINT: bad trap

$ ./test.sh
trap: SIGINT: bad trap


To fix the script, SIGINT should be replaced with INT

So I think checkbashishm should warn always that it finds SIGSOMETHING
on a trap line.



signature.asc
Description: OpenPGP digital signature

Bug#843599: RFS: passwordsafe/1.00+dfsg-1

[Bill Blough]

Package: sponsorship-requests
Severity: normal [important for RC bugs, wishlist for new packages]

Dear mentors,

I am looking for a sponsor for my package "passwordsafe"

* Package name: passwordsafe
  Version : 1.00+dfsg-1
  Upstream Author : Rony Shapiro ]
* URL : https://pwsafe.org
* License : Artistic 2.0
  Section : utils

It builds those binary packages:

passwordsafe - Simple & Secure Password Management
passwordsafe-common - architecture independent files for Password Safe

To access further information about this package, please visit the following 
URL:

https://mentors.debian.net/package/passwordsafe


 Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/p/passwordsafe/passwordsafe_1.00+dfsg-1.dsc

More information about hello can be obtained from https://pwsafe.org.

Changes since the last upload:

* Change d/rules to eliminate depencdency on locales-all.  Thanks to
  Stephen Kitt for the bug report and patch.  Closes: 833533
* Fix watch file
* New upstream version
* Remove reproducibe-build.patch, which was applied upstream.


Regards,
Bill Blough

Bug#828252: qtcreator is marked for autoremoval from testing

[Christian Hofstaedtler]

Ondřej,

* Ondřej Surý  [161106 21:12]:
> In the end it was very easy (hopefully) - the OpenSSL module is optional
> and hopefully this won't break anything :). Ccing other botan1.10 users.
> 
> Please test with botan1.10 - 1.10.13-1 that just got uploaded to
> unstable.

Tested pdns 4.0.1-5 against the new botan1.10 1.10.13-1 and can
confirm that pdns still works (without rebuilding).

Thanks for taking care of this.

Cheers,
-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-

Bug#840540: dianara: Please update to v1.3.5 to allow switching qoauth to qt5

[Lisandro Damián Nicanor Pérez Meyer]

On martes, 8 de noviembre de 2016 00:05:06 ART Jan wrote:
[snip] 
> If it still crashes for you, could you run it with --debug and paste the
> last ~5 lines or so? =)

My plasma-integration package was out of date, now it work perfectly :)

-- 
Hi! I'm a .signature virus! Copy me into your ~/.signature, please!

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#843597: More robust capability handling

[Thomas Lange]

> On Mon, 07 Nov 2016 17:36:41 -0500, Sam Hartman  
> said:

> Currently, the sample configuration namespace has a shell script to
> restore the common capabilities found in base files; see
> scripts/DEBIAN/20-capabilities.
In this script, I'm doing the same things that are done in the
postinst script of the package.

Also there was a bug in tar which added some xattr or capabilities
even no were defined when creating the tar file. Have a look at
#819978. IIRC this was one reason to no use xattrs with tar by
default.
-- 
regards Thomas

Bug#843450: [pkg-lxc-devel] Bug#843450: Bug#843450: lxc: Corrupt /proc/self/cgroup / Failed to get list of controllers

[Francois Marier]

On 2016-11-07 at 13:00:31, Evgeni Golov wrote:
> Can you please try booting with
>  systemd.legacy_systemd_cgroup_controller
> and see if that fixes the issue for you for now?

It seems to work fine. Thanks for the pointer!

Should there be a versioned conflict on systemd or the kernel? Maybe a note
in NEWS.Debian?

Francois

-- 
https://fmarier.org/

Bug#840540: dianara: Please update to v1.3.5 to allow switching qoauth to qt5

[Lisandro Damián Nicanor Pérez Meyer]

Mónica: you should now be able to drop the patch.

-- 
Only Irish coffee provides in a single glass all four essential food groups
-- alcohol, caffeine, sugar, and fat.
  Alex Levine

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#840540: dianara: Please update to v1.3.5 to allow switching qoauth to qt5

[Jan]

On Mon, Nov 07, 2016 at 07:17:31PM -0300, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> > This is a simple diff of the changes I made to make it work:
> 
> Jan: next time please use diff -Nau, that's the most used format when dealing 
> with patches.
>  

Thanks for the hint! I wanted that kind of output, but I didn't find the
switch for it. I was even tempted to use a git repo to use git diff!

> > When starting up Dianara, I get an early crash, related to the systray
> > icon, both under Plasma and under LXQt, but I imagine it has to do with
> > the Qt5.7.1 transition. It works fine under a bare Openbox+Tint2
> > session.
> 
> Mmm, need to check in fluxbox then.

At the moment, it works fine for me under current Sid's Plasma. I
haven't checked, but I imagine it will still crash under LXQt.
Under Openbox there wasn't any problem at any time (i386 machines).

If it still crashes for you, could you run it with --debug and paste the
last ~5 lines or so? =)

Cheers!


-- 
Development blog: https://jancoding.wordpress.com

Bug#837485: [pkg-golang-devel] Bug#837485: Bug#837485: golang-1.6: FTBFS with bindnow and PIE enabled

[Niels Thykier]

Tianon Gravi:
> On 5 November 2016 at 09:00, Niels Thykier  wrote:
>> Cool! :)
>>
>> Should I file a bug against ftp.d.o, asking them to remove golang-1.6
>> from unstable? :)
> 
> If you're willing, that sounds great! (I always end up having to
> re-read the docs any time I use the BTS for more than simply replying,
> so I hadn't gotten around to doing so yet)
> 
> 
> ♥,
> - Tianon
>   4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4
> 

Ack - filed as #843598.

Thanks,
~Niels

Bug#843598: RM: golang-1.6 -- RoQA; Replaced by newer package; no rdeps left; FTBFS in sid

[Niels Thykier]

Package: ftp.debian.org
Severity: normal

Hi,

Per #837485, please remove golang-1.6 from unstable.  The last rdep
has been removed, the package FTBFS, the maintainers have replaced
it with a difference source package and agree to its removal.

Thanks,
~Niels

Bug#811960: pulseview NMU?

[Uwe Hermann]

Hi,

On Mon, Nov 07, 2016 at 04:25:14PM +, Jonathan McDowell wrote:
> Uwe, do you have any plans for this?

Yeah, might upload some new packages soonish, but long-term
I'd be happy to hand over the full sigrok suite of packages to another
interested + active developer, so I can focus more on upstream development.


Uwe.
-- 
http://hermann-uwe.de | http://randomprojects.org | http://sigrok.org

Bug#840540: dianara: Please update to v1.3.5 to allow switching qoauth to qt5

[gregor herrmann]

On Mon, 07 Nov 2016 19:18:46 -0300, Lisandro Damián Nicanor Pérez Meyer wrote:

> > > gregorr, looks like you need libqca-qt5-2-plugins, which contains the
> > > Qt5 version of the QCA openssl plugin.
> > I see, thank you.
> > But then there's a dependency problem somewhere ...
> I think that in libqoauth2, will be fixed in a few minutes.

Great, thank you Lisandro! 


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
   `-   


signature.asc
Description: Digital Signature

Bug#842574: transition: qtbase-opensource-src

[Emilio Pozuelo Monfort]

On 06/11/16 19:59, Dmitry Shachnev wrote:
> Hi Emilio,
> 
> On Sun, Nov 06, 2016 at 04:17:55PM +0100, Emilio Pozuelo Monfort wrote:
>>> Please also binNMU plasma-integration against the new qtbase.
>>>
>>> It links with the static library libQt5PlatformSupport.a, and should pick
>>> up the new version of it.
>>
>> Done. I wonder if this shouldn't have a stricter dependency though.
> 
> Do you mean that it should depend on qtbase-abi-5-x-y?
> 
> If yes, I would like this to be the case, but as it is a plugin which just
> implements the QPlatformTheme interface, and it does not use any Qt private
> symbols. And as there are no private symbols on it, it does not get such a
> dependency.
> 
> In this particular case, a new method was added to its (pure virtual) parent
> class (with the default implementation), and the rebuild makes sure that
> this method can be called.

I mean if changes in qtbase can break this package, then it probably needs a
stricter dependency than it currently has. But maybe it's qtbase's fault for
breaking the public ABI (if that is considered an ABI break. I'm not too
familiar with C++ ABI so I can't say). But I'll just leave this up to you.

Cheers,
Emilio

Bug#837485: [pkg-golang-devel] Bug#837485: Bug#837485: golang-1.6: FTBFS with bindnow and PIE enabled

[Tianon Gravi]

On 5 November 2016 at 09:00, Niels Thykier  wrote:
> Cool! :)
>
> Should I file a bug against ftp.d.o, asking them to remove golang-1.6
> from unstable? :)

If you're willing, that sounds great! (I always end up having to
re-read the docs any time I use the BTS for more than simply replying,
so I hadn't gotten around to doing so yet)


♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#843597: More robust capability handling

[Sam Hartman]

package: fai
version: 5.2

Currently, the sample configuration namespace has a shell script to
restore the common capabilities found in base files; see
scripts/DEBIAN/20-capabilities.

This approach is brittle because as new packages in the base system gain
capabilities, everyone's configuration space needs to be updated.

tar does support saving and restoring capabilities.
If base file tars are created using
tar --xattrs --xattrs-include=security.capability -cf blah blah

and restored with
tar -xf filename --xattrs --xattrs-include=security.capability

Then capabilities are directly preserved.

I understand that you may want to preserve the script in the
configuration space because you cannot guarantee how people create base
files.
However for restore of base files, please include the xattrs options.

Bug#828252: qtcreator is marked for autoremoval from testing

[Lisandro Damián Nicanor Pérez Meyer]

On domingo, 6 de noviembre de 2016 21:12:14 ART Ondřej Surý wrote:
> In the end it was very easy (hopefully) - the OpenSSL module is optional
> and hopefully this won't break anything :). Ccing other botan1.10 users.
> 
> Please test with botan1.10 - 1.10.13-1 that just got uploaded to
> unstable.

Hi Ondřej! Will check for sure!


-- 
Una sola bomba nuclear puede arruinar el resto de tu día.

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#843145: files with the same name installed in / and /usr

[Martin Pitt]

Control: tag -1 grave

Martin Pitt [2016-11-04 12:14 +0200]:
> Merged /usr is the default since debootstrap 1.0.85, so this is
> possibly even RC.

It is: Installing libjson-c-dev on a freshly bootstrapped sid chroot
causes a symlink loop:

# head /lib/x86_64-linux-gnu/libjson-c.so.3
head: cannot open '/lib/x86_64-linux-gnu/libjson-c.so.3' for reading: Too many 
levels of symbolic links

Thus bumping severity. I'm happy to do an NMU if you don't have time
(I'd also fix the broken Vcs-Browse: field while I'm at it).

Martin
-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

Bug#842264: Wrong OS version detected

[Трезвый Дворник]

Hi!
I am sorry for delay.

noroot@f555l:~$ apt-cache policy | grep release
 release a=now
 release
v=14.04,o=LP-PPA-keks9n-skypetab,a=trusty,n=trusty,l=SkypeTab,c=main,b=i386
 release
v=14.04,o=LP-PPA-keks9n-skypetab,a=trusty,n=trusty,l=SkypeTab,c=main,b=amd64
 release
v=15.04,o=LP-PPA-openshot.developers,a=vivid,n=vivid,l=OpenShot: Stable PPA
- Official Releases,c=main,b=i386
 release
v=15.04,o=LP-PPA-openshot.developers,a=vivid,n=vivid,l=OpenShot: Stable PPA
- Official Releases,c=main,b=amd64
 release v=15.10,o=LP-PPA-obsproject-obs-studio,a=wily,n=wily,l=OBS
Studio,c=main,b=i386
 release v=15.10,o=LP-PPA-obsproject-obs-studio,a=wily,n=wily,l=OBS
Studio,c=main,b=amd64
 release v=15.10,o=LP-PPA-noobslab-icons,a=wily,n=wily,l=Collection of
icons PPA,c=main,b=i386
 release v=15.10,o=LP-PPA-noobslab-icons,a=wily,n=wily,l=Collection of
icons PPA,c=main,b=amd64
 release v=15.10,o=LP-PPA-noobslab-themes,a=wily,n=wily,l=Themes
Collection by NoobsLab,c=main,b=i386
 release v=15.10,o=LP-PPA-noobslab-themes,a=wily,n=wily,l=Themes
Collection by NoobsLab,c=main,b=amd64
 release o=liquorix,a=unstable,n=sid,l=kernel,c=main,b=i386
 release o=liquorix,a=unstable,n=sid,l=kernel,c=main,b=amd64
 release
v=15.04,o=LP-PPA-alessandro-strada,a=vivid,n=vivid,l=google-drive-ocamlfuse,c=main,b=i386
 release
v=15.04,o=LP-PPA-alessandro-strada,a=vivid,n=vivid,l=google-drive-ocamlfuse,c=main,b=amd64
 release v=1.0,o=Google, Inc.,a=stable,n=stable,l=Google,c=main,b=amd64
 release
v=6.0.10,o=Debian,a=oldoldstable,n=squeeze,l=Debian,c=main,b=i386
 release
v=6.0.10,o=Debian,a=oldoldstable,n=squeeze,l=Debian,c=main,b=amd64
 release o=obs://
build.opensuse.org/home:Horst3180/Debian_8.0,n=Debian_8.0,l=home:Horst3180,c=
 release o=. trusty,n=trusty,l=. trusty,c=non-free,b=i386
 release o=. trusty,n=trusty,l=. trusty,c=non-free,b=amd64
 release
o=Debian,a=experimental,n=experimental,l=Debian,c=non-free,b=i386
 release
o=Debian,a=experimental,n=experimental,l=Debian,c=non-free,b=amd64
 release
o=Debian,a=experimental,n=experimental,l=Debian,c=contrib,b=i386
 release
o=Debian,a=experimental,n=experimental,l=Debian,c=contrib,b=amd64
 release o=Debian,a=experimental,n=experimental,l=Debian,c=main,b=i386
 release o=Debian,a=experimental,n=experimental,l=Debian,c=main,b=amd64
 release o=Debian,a=unstable,n=sid,l=Debian,c=non-free,b=i386
 release o=Debian,a=unstable,n=sid,l=Debian,c=non-free,b=amd64
 release o=Debian,a=unstable,n=sid,l=Debian,c=contrib,b=i386
 release o=Debian,a=unstable,n=sid,l=Debian,c=contrib,b=amd64
 release o=Debian,a=unstable,n=sid,l=Debian,c=main,b=i386
 release o=Debian,a=unstable,n=sid,l=Debian,c=main,b=amd64
 release o=Debian,a=testing,n=stretch,l=Debian,c=non-free,b=i386
 release o=Debian,a=testing,n=stretch,l=Debian,c=non-free,b=amd64
 release o=Debian,a=testing,n=stretch,l=Debian,c=contrib,b=i386
 release o=Debian,a=testing,n=stretch,l=Debian,c=contrib,b=amd64
 release o=Debian,a=testing,n=stretch,l=Debian,c=main,b=i386
 release o=Debian,a=testing,n=stretch,l=Debian,c=main,b=amd64

noroot@f555l:~$ lsb_release -sirc
Debian
6.0.10
squeeze

I added second section to my lonely preferences file

noroot@f555l:~$ cat /etc/apt/preferences.d/baobab
Package: baobab
Pin: version 2.*
Pin-Priority: 1001

Package: *
Pin: release o=Debian,n=squeeze
Pin-Priority: 1

And it works better now
noroot@f555l:~$ lsb_release -sirc
Debian
unstable
sid
noroot@f555l:~$ screenfetch -n
 noroot@f555l
 OS: Debian unstable sid
 Kernel: x86_64 Linux 4.8.0-5.2-liquorix-amd64

Can that string (optionally) be taken from hostnameclt(for systemd users)
or something like that to avoid wrong apt/preferences configuration?

Thank you!
Best regards,
Dmitri

2016-11-04 0:49 GMT+03:00 Hideki Yamane :

>  lsb-release package probably detects your system as squeeze due to
>  apt policy setting. Could you show me "apt-cache policy | grep release"?
>

Bug#840540: dianara: Please update to v1.3.5 to allow switching qoauth to qt5

[Lisandro Damián Nicanor Pérez Meyer]

On lunes, 7 de noviembre de 2016 22:55:30 ART gregor herrmann wrote:
> On Mon, 07 Nov 2016 20:41:01 +0100, Jan wrote:
> > On Mon, Nov 07, 2016 at 05:44:31PM +0100, gregor herrmann wrote:
> > > postInit();
> > > PumpController::getInitialData() step 0
> > > HMAC(SHA1) is not supported!
> > 
> > gregorr, looks like you need libqca-qt5-2-plugins, which contains the
> > Qt5 version of the QCA openssl plugin.
> 
> I see, thank you.
> But then there's a dependency problem somewhere ...

I think that in libqoauth2, will be fixed in a few minutes.

-- 
Never attribute to malice that which is adequately explained by stupidity.
  http://en.wikipedia.org/wiki/Hanlon's_razor

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#840540: dianara: Please update to v1.3.5 to allow switching qoauth to qt5

[Lisandro Damián Nicanor Pérez Meyer]

On domingo, 6 de noviembre de 2016 13:52:08 ART Jan wrote:
> On Sat, Oct 29, 2016 at 10:10:39AM -0300, Lisandro Damián Nicanor Pérez 
Meyer wrote:
> > Already in experimental! please ping me if you need help with Dianara.
> > 
> > I don't know if you have packaged Qt5 apps before (nor did check
> > actually). In case you didn't you might want to read
> > 
> >   http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
> > 
> > Cheers!
> 
> Hi!
> 
> I've tested this (on two i386 Sid machines) and have some feedback.
> 
> Dianara uses qmake as the buildsystem, so it relies on a oauth.prf spec
> file, which was missing in the Qt4 version of libqoauth-dev[1], but is
> present now.
> The problem is that this oauth.prf file needs some adapting.

ACK, this is true.

> This is a simple diff of the changes I made to make it work:

Jan: next time please use diff -Nau, that's the most used format when dealing 
with patches.
 
> 1c1
> < QOAUTH_INCDIR = $$[QT_INSTALL_HEADERS]
> ---
> 
> > QOAUTH_INCDIR = /usr/include  ### $$[QT_INSTALL_HEADERS]
> 
> 4,5c4,5
> < QOAUTH_INCDIR ~= s!/qt4*!!
> < QOAUTH_LIBDIR ~= s!/qt4*!!
> ---
> 
> > #QOAUTH_INCDIR ~= s!/qt4*!!
> > #QOAUTH_LIBDIR ~= s!/qt4*!!
> 
> Basically, make QOAUT_INCDIR point to /usr/include instead of using that
> variable, which points to /usr/lib/{$arch-triplet}/qt5.
> 
> Then the other two lines that would take care of removing "qt4" from the
> resulting variable, should be removed or commented out.
> 
> Or, as an alternative, libqoauth-dev should put its header files in that
> /usr/lib/{archtriplet}/qt5 path, whatever's best. I don't know how that
> would affect Choqok or other potential "users".

Headers should be installed there only if they differe from arch to arch. As 
Qt5 headers do, QT_INSTALL_HEADER follows that.

And yes, the Qt4 stuff should be removed.

I'll fix that.

> With this, Dianara builds perfectly with Qt 5. Package
> libqca-qt5-2-plugins should be a new dependency instead of
> libqca2-plugin-ossl, since apparently QCA plugins for the Qt5 version
> are all packed into that one.

Actualli libqoauth2 should depend on them, if I'm not mistaken it definitely 
needs them. I'll do this change now.
 
> When starting up Dianara, I get an early crash, related to the systray
> icon, both under Plasma and under LXQt, but I imagine it has to do with
> the Qt5.7.1 transition. It works fine under a bare Openbox+Tint2
> session.

Mmm, need to check in fluxbox then.

-- 
Geek Inside!

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#843596: RFS: node-jsonparse/1.2.0-1

[Bastien ROUCARIES]

Package: sponsorship-requests
Severity: normal [important for RC bugs, wishlist for new packages]
X-Debbugs-CC :prav...@debian.org
X-Debbugs-CC :locutusofb...@debian.org


  Dear mentors,

  I am looking for a sponsor for my package "node-jsonparse"

 * Package name: node-jsonparse
   Version : 1.2.0-1
   Upstream Author :  2015-2016 Tim Caswell 
 * License : expat
   Section : web

  It builds those binary packages:

node-jsonparse - Pure javascript JSON streaming parser for node.js

  To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/node-jsonparse


  Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/n/node-jsonparse/node-jsonparse_1.2.0-1.dsc


  Changes since the last upload:

   * New upstream version.
  * Bump policy version (no changes).
  * Use compat 10.
  * Upgrade VCS fields.

It is needed for browserify effort so try to upload correct version


  Regards,
   bastien roucaries

Bug#843334: transition: czmq

[Luca Boccassi]

On Sun, 2016-11-06 at 10:44 +, Luca Boccassi wrote:
> On Sun, 2016-11-06 at 11:01 +0100, Emilio Pozuelo Monfort wrote:
> > On 06/11/16 00:43, Luca Boccassi wrote:
> > > On Sat, 5 Nov 2016 22:43:46 + Luca Boccassi  
> > > wrote:
> > >> Package: release.debian.org
> > >> Severity: normal
> > >> User: release.debian@packages.debian.org
> > >> Usertags: transition
> > >>
> > >> Dear release team,
> > >>
> > >> czmq 4.0.0 was released yesterday, and it breaks ABI, which was bumped
> > >> from 3 to 4.
> > >>
> > >> https://packages.qa.debian.org/c/czmq.html
> > >>
> > >> Reverse dependencies source packages:
> > >>
> > >> rsyslog
> > >>
> > >> The reverse dependency rebuild cleanly without any patches. binNMU
> > >> rebuilds should be all that's needed.
> > >>
> > >> libczmq4 is in experimental and it has rebuilt most architectures,
> > >> with the mips and armv7 queued. I built locally in qemu and it was all
> > >> fine so I do not expect trouble.
> > >>
> > >> I know it's a bit late, but given it's a very simple case I hope it
> > >> can be authorized, to avoid having to maintain an old version for many
> > >> years! Upstream will not release bug fixes for 3.0.x anymore.
> > >>
> > >> Thank you!
> > >>
> > >> Kind regards,
> > >> Luca Boccassi
> > > 
> > > Transition tracker item has been autogenerated now, here's the link:
> > > 
> > > https://release.debian.org/transitions/html/auto-czmq.html
> > 
> > Go ahead.
> > 
> > Cheers,
> > Emilio
> 
> Thank you!
> 
> Will upload tonight as I'm travelling.
> 
> Kind regards,
> Luca Boccassi

Hi,

I have uploaded czmq 4.0.0-3 to unstable:

https://packages.qa.debian.org/c/czmq/news/20161107T214955Z.html

Will rsyslog be rebuilt automatically, or manually by the ftp/release
team?

Kind regards,
Luca Boccassi


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

Bug#843595: [lintian] Detect non free unicode code and embeded copy

[Bastien ROUCARIÈS]

Package: lintian
Version: 2.5.49
Severity: important

Detect code described here :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823100

I will do it in the few next day

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

Bug#843594: ilmbase: Proprietary licence in halfExport.h

[D Haley]

Source: ilmbase
Version: 2.2.0-11
Severity: normal

Dear Maintainer,

It appears that in the current ilmbase package there is a small 
file that contains code with a proprietary licence.

Specifically Half/halfExport.h contains the following:

//  Copyright (c) 2008 Lucasfilm Entertainment Company Ltd.
//  All rights reserved.   Used under authorization.
//  This material contains the confidential and proprietary
//  information of Lucasfilm Entertainment Company and
//  may not be copied in whole or in part without the express
//  written permission of Lucasfilm Entertainment Company.
//  This copyright notice does not imply publication.


Is it possible to replace this (tiny) file, or to confirm
that this is a non-issue?

Thanks!

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

Kernel: Linux 4.7.0-1-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: sysvinit (via /sbin/init)

Bug#840540: dianara: Please update to v1.3.5 to allow switching qoauth to qt5

[gregor herrmann]

On Mon, 07 Nov 2016 20:41:01 +0100, Jan wrote:

> On Mon, Nov 07, 2016 at 05:44:31PM +0100, gregor herrmann wrote:
> > postInit();
> > PumpController::getInitialData() step 0
> > HMAC(SHA1) is not supported!
> > 
> 
> gregorr, looks like you need libqca-qt5-2-plugins, which contains the
> Qt5 version of the QCA openssl plugin.

I see, thank you.
But then there's a dependency problem somewhere ...
 

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
   `-   


signature.asc
Description: Digital Signature

Bug#843589: opendnssec: Files required for update missing

[Simon Ruderich]

Hello again,

Just noticed another update issue. All the paths given in the
update README are not correct on Debian. I noticed at least
/var/opendnssec vs. /var/lib/opendnssec on Debian.

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


signature.asc
Description: PGP signature

Bug#833217: pycryptopp: Uses obsolete compressor for .deb data.tar member

[IOhannes m zmoelnig]

Package: src:pycryptopp
Followup-For: Bug #833217

Control: tags -1 pending
thanks

I've just uploaded an NMU with a fix (using gzip instead of bzip2) to DELAYED/5.

Please find the diff attached.

mfgards
IOhannes

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

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru pycryptopp-0.6.0.20120313/debian/changelog pycryptopp-0.6.0.20120313/debian/changelog
--- pycryptopp-0.6.0.20120313/debian/changelog	2013-08-22 23:07:55.0 +0200
+++ pycryptopp-0.6.0.20120313/debian/changelog	2016-11-07 22:43:57.0 +0100
@@ -1,3 +1,10 @@
+pycryptopp (0.6.0.20120313-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use gzip compression for package (Closes: #833217)
+
+ -- IOhannes m zmölnig (Debian/GNU)   Mon, 07 Nov 2016 22:43:57 +0100
+
 pycryptopp (0.6.0.20120313-1) unstable; urgency=low
 
   * Update debian/watch
diff -Nru pycryptopp-0.6.0.20120313/debian/rules pycryptopp-0.6.0.20120313/debian/rules
--- pycryptopp-0.6.0.20120313/debian/rules	2013-08-22 23:07:55.0 +0200
+++ pycryptopp-0.6.0.20120313/debian/rules	2016-11-07 22:43:57.0 +0100
@@ -69,7 +69,7 @@
 	dh_shlibdeps -a
 	dh_gencontrol -a
 	dh_md5sums -a
-	dh_builddeb -a -- -Z bzip2
+	dh_builddeb -a -- -Z gzip
 
 binary-indep:
 

Bug#837928: Bug#837925: usrmerge: fails to merge with molly-guard installed

[Jonas Smedegaard]

Quoting Francois Marier (2016-11-07 18:38:58)
> On 2016-11-02 at 03:02:29, Jonas Smedegaard wrote:
> > I am busy getting that system to production use (yes, stretch is not yet 
> > stable, but more stable than stable on the ARM device I use), but if you 
> > have suggestions for closer inspections that might help shed some light 
> > on this issue, please shoot - fast.
> 
> I reached out to Marco about this bug but have not heard back.
> 
> I don't know how dpkg-diverts are supposed to work in a usrmerge world and I
> can't see anything obviously wrong with the way it's done in molly-guard so
> I don't have any ideas on how to fix this.

I no longer believe this issue is tied to use with the usrmerge package: 
It happens also on freshly installed systems!

It seems that on a usrmerge+systemd system /bin/reboot is a symlink.

Perhaps molly-guard (in its use of dpkg-divert) wrongly assumes that if 
/bin/reboot already exists then it is _installed_ by a package rather 
than added in a package postinst script which seems to be the case with 
systemd (just guessing here, having looked closely at it).

 - Jonas

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

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

Bug#843592: RFS: node-punycode/2.0.1-1

[Bastien ROUCARIES]

Package: sponsorship-requests
Severity: normal
X-Debbugs-CC :prav...@debian.org
X-Debbugs-CC :locutusofb...@debian.org

Dear mentors,

  I am looking for a sponsor for my package "node-punycode"

 * Package name: node-punycode
   Version : 2.0.1-1
   Upstream Author : Mathias Bynens
 * URL : [fill in URL of upstreams web site]
 * License : expat
   Section : web

  It builds those binary packages:

node-punycode - Nodejs robust Punycode converter fully RFC compliant

  To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/node-punycode


  Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/n/node-punycode/node-punycode_2.0.1-1.dsc

  More information about hello can be obtained from https://mths.be/punycode


  Changes since the last upload:

  node-punycode (2.0.1-1) unstable; urgency=medium

  * New upstream release.
  * Bump standard version (no changes).
  * Use compat version 10.

 -- Bastien Roucariès   Mon, 07
Nov 2016 22:17:15 +0100

It is needed for browserify effort so try to upload correct version


  Regards,
   bastien roucaries

Bug#843593: Please add support for ESP partitions

[Sam Hartman]

package: fai
version: 5.2
tags: patch
severity: wishlist

It's impossible to use FAI to install for a platform/system that
requires UEFI because FAI does not currently support setting up a
extended system partition as required by the UEFI spec.
This patch adds code to do that.

I did not update the documentation in this patch, because I'm not that
familiar with all the documentation I'd need to touch.
An example disk_config might look something like:

#
#

disk_config disk1 disklabel:gpt bootable:1 esp:1 fstabkey:uuid align-at:1M

primary /boot/efi 300vfat  defaults
primary /  300-  ext4  rw,barrier=0,noatime,errors=remount-ro 
tuneopts="-c 0 -i 0"


>From 06a30575b8c473da89a031587debd8f6f350ba6b Mon Sep 17 00:00:00 2001
From: Sam Hartman 
Date: Mon, 7 Nov 2016 16:41:12 -0500
Subject: [PATCH] Add support for ESP partitions

UEFI requires a special vfat partition on which the boot loader and
potentially other UEFI information lives.  Parted represents this with
an esp flag.  Add support for this in setup-storage.
---
 lib/setup-storage/Commands.pm | 2 ++
 lib/setup-storage/Parser.pm   | 8 
 2 files changed, 10 insertions(+)

diff --git a/lib/setup-storage/Commands.pm b/lib/setup-storage/Commands.pm
index 31898ca..6190343 100755
--- a/lib/setup-storage/Commands.pm
+++ b/lib/setup-storage/Commands.pm
@@ -1344,6 +1344,8 @@ sub setup_partitions {
   if ($part->{size}->{preserve} || $part->{size}->{resize});
 # set the bootable flag, if requested at all
 $flags .= ",boot" if($FAI::configs{$config}{bootable} == $part_id);
+# set the ESP flag, if requested at all
+$flags .= ",esp" if($FAI::configs{$config}{esp} == $part_id);
 # set the bios_grub flag on BIOS compatible GPT tables
 $flags .= ",bios_grub" if($FAI::configs{$config}{disklabel} eq "gpt-bios"
   && $FAI::configs{$config}{gpt_bios_part} == $part_id);
diff --git a/lib/setup-storage/Parser.pm b/lib/setup-storage/Parser.pm
index 943eaa5..d58afe9 100755
--- a/lib/setup-storage/Parser.pm
+++ b/lib/setup-storage/Parser.pm
@@ -144,6 +144,7 @@ sub init_disk_config {
 virtual=> 0,
 disklabel  => "msdos",
 bootable   => -1,
+esp=> 0,
 fstabkey   => "device",
 preserveparts => 0,
 partitions => {},
@@ -690,6 +691,13 @@ $FAI::Parser = Parse::RecDescent->new(
   ($FAI::device =~ /^PHY_(.+)$/) or
 ::internal_error("unexpected device name");
 }
+| /^esp:(\d+)/
+{
+  # specify a partition that should get the ESP flag set
+  $FAI::configs{$FAI::device}{esp} = $1;
+  ($FAI::device =~ /^PHY_(.+)$/) or
+::internal_error("unexpected device name");
+}
 | 'virtual'
 {
   # this is a configuration for a virtual disk
-- 
2.9.3

Bug#840540: dianara: Please update to v1.3.5 to allow switching qoauth to qt5

[Lisandro Damián Nicanor Pérez Meyer]

On lunes, 7 de noviembre de 2016 20:41:01 ART Jan wrote:
> On Mon, Nov 07, 2016 at 05:44:31PM +0100, gregor herrmann wrote:
> > postInit();
> > PumpController::getInitialData() step 0
> > HMAC(SHA1) is not supported!
> 
> gregorr, looks like you need libqca-qt5-2-plugins, which contains the
> Qt5 version of the QCA openssl plugin.
> 
> https://packages.debian.org/sid/libqca-qt5-2-plugins

I have it installed and I'm getting a segfault :-(

-- 
Outside of a dog, a book is man's best friend.
Inside of a dog, it's too dark to read.
 -- Groucho Marx

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#842795: email-reminder: Fail to send email as release version cannot be detect

[Jack.R]

On Mon, 7 Nov 2016 08:57:58 -0800 Francois Marier 
wrote:
> On 2016-11-06 at 10:09:21, Jack.R wrote:
> > I start to suspect a right access as that part is executed as
> > email-reminder user.
> > 
> > So I try with a normal user by putting
> > my $distro = `/bin/su - alain -s /bin/sh -c "/usr/bin/lsb_release -s
> > -d"`;
> > I am prompt for the password and then it works.
> > It looks like email-reminder user has not sufficient rights to
> > run /usr/bin/lsb_release without error but currently I did not see
> > why.
> 
> What about this then?
> 
> my $distro = `/bin/su - email-reminder -s /bin/sh -c
> "/usr/bin/lsb_release -s -d"`;
> 
> Francois
> 

I am prompted for the password of email-reminder account and this
one is locked (! in second field of shadow file).

If I add a password to that account and unlock it, $distro is still
empty 

--> {} <--

instead of getting the version like when I use a normal user account:

--> {Debian GNU/Linux testing (stretch)
} <--

Code has been modified as follow for testing:
my $distro = `/bin/su - email-reminder -s /bin/sh -c "/usr/bin/lsb_release -s 
-d"`;
print "--> {$distro} <--";
chomp $distro;


-- 
Jack.R

Bug#843502: stopping with NMU

[Geert Stappers]

On Mon, Nov 07, 2016 at 06:43:16AM +0100, Geert Stappers wrote:
> In https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796341#10
> is being spoken about team maintenance. That bugreport is closed,
> This new BR is a public reminder of that task.

The next upload of radvd will have me as maintainer.

The idea is stopping with Non-Maintainer-Uploads.

Maintainer Uploads is the essential task of the pkg-radvd-team ...


Groeten
Geert Stappers
-- 
Leven en laten leven


signature.asc
Description: Digital signature

Bug#843591: O: ldap2dns -- LDAP based DNS management system

[Tobias Frost]

Package: wnpp
Severity: normal

The current maintainer of ldap2dns, Igor Stroh ,
has retired.  Therefore, I orphan this package now.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
https://www.debian.org/devel/wnpp/index.html#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: ldap2dns
Binary: ldap2dns
Version: 0.3.1-3.1
Maintainer: Igor Stroh 
Build-Depends: debhelper (>= 4.1.16), libldap2-dev (>= 2.1.22-1), links (>= 
0.98-3)
Architecture: any
Standards-Version: 3.6.1
Format: 1.0
Files:
 a4a070a9b1d2afec3e6c35a7136ab85f 1048 ldap2dns_0.3.1-3.1.dsc
 3f661468159633a8fdd843db2af97721 40760 ldap2dns_0.3.1.orig.tar.gz
 df438e6bacc0d032d113787f3649a147 6216 ldap2dns_0.3.1-3.1.diff.gz
Checksums-Sha1:
 eae51475330897f43b7b22e257302c78f7f15edd 1048 ldap2dns_0.3.1-3.1.dsc
 3fb4e126916fe3a2f80369ba94e58b5a9563990e 40760 ldap2dns_0.3.1.orig.tar.gz
 c105e3a50f8e82925f3856e9063555c7f087ee5e 6216 ldap2dns_0.3.1-3.1.diff.gz
Checksums-Sha256:
 74ff3d75cce0075b76ba4c03baeee14f00c5a9e74a7e914a1bc909202e121875 1048 
ldap2dns_0.3.1-3.1.dsc
 cf5595e9197209a3b9db63855113924ee9d574503e091ceac7c942ff83b69759 40760 
ldap2dns_0.3.1.orig.tar.gz
 c79ffa8f6bec4fd72b4b7f74ddc23de4c4546266dfdfdac6762037c2a1b9cbf1 6216 
ldap2dns_0.3.1-3.1.diff.gz
Package-List: 
 ldap2dns deb admin optional
Directory: pool/main/l/ldap2dns
Priority: source
Section: admin

Package: ldap2dns
Binary: ldap2dns
Version: 0.3.1-3.2
Maintainer: Igor Stroh 
Build-Depends: debhelper (>= 10), libldap2-dev (>= 2.1.22-1), links (>= 0.98-3)
Architecture: any
Standards-Version: 3.9.8
Format: 1.0
Files:
 a56282c18bee5a7870d26f82994e7fce 1654 ldap2dns_0.3.1-3.2.dsc
 3f661468159633a8fdd843db2af97721 40760 ldap2dns_0.3.1.orig.tar.gz
 d781a11fbe77a63fe1514cfbaee50635 6633 ldap2dns_0.3.1-3.2.diff.gz
Checksums-Sha256:
 bc924041909ccc19bb6f115d50dab1ea9e44036cf6595f12cef71b5d8ad2d6d7 1654 
ldap2dns_0.3.1-3.2.dsc
 cf5595e9197209a3b9db63855113924ee9d574503e091ceac7c942ff83b69759 40760 
ldap2dns_0.3.1.orig.tar.gz
 95e9b4fe707a5babd3a171d1ed1088b56332e2b3c557b414f77e5be6c36751ad 6633 
ldap2dns_0.3.1-3.2.diff.gz
Package-List: 
 ldap2dns deb admin optional arch=any
Directory: pool/main/l/ldap2dns
Priority: source
Section: admin

Package: ldap2dns
Binary: ldap2dns
Version: 0.3.1-3.2
Maintainer: Igor Stroh 
Build-Depends: debhelper (>= 10), libldap2-dev (>= 2.1.22-1), links (>= 0.98-3)
Architecture: any
Standards-Version: 3.9.8
Format: 1.0
Files:
 a56282c18bee5a7870d26f82994e7fce 1654 ldap2dns_0.3.1-3.2.dsc
 3f661468159633a8fdd843db2af97721 40760 ldap2dns_0.3.1.orig.tar.gz
 d781a11fbe77a63fe1514cfbaee50635 6633 ldap2dns_0.3.1-3.2.diff.gz
Checksums-Sha1:
 c1f54ccf258a58adad28faae412bb0c48e4269c7 1654 ldap2dns_0.3.1-3.2.dsc
 3fb4e126916fe3a2f80369ba94e58b5a9563990e 40760 ldap2dns_0.3.1.orig.tar.gz
 9a8f3d2f0b43aa38f6f4d96b8564bb66b931e1d8 6633 ldap2dns_0.3.1-3.2.diff.gz
Checksums-Sha256:
 bc924041909ccc19bb6f115d50dab1ea9e44036cf6595f12cef71b5d8ad2d6d7 1654 
ldap2dns_0.3.1-3.2.dsc
 cf5595e9197209a3b9db63855113924ee9d574503e091ceac7c942ff83b69759 40760 
ldap2dns_0.3.1.orig.tar.gz
 95e9b4fe707a5babd3a171d1ed1088b56332e2b3c557b414f77e5be6c36751ad 6633 
ldap2dns_0.3.1-3.2.diff.gz
Package-List: 
 ldap2dns deb admin optional arch=any
Directory: pool/main/l/ldap2dns
Priority: source
Section: admin

Package: ldap2dns
Version: 0.3.1-3.2
Installed-Size: 81
Maintainer: Igor Stroh 
Architecture: amd64
Depends: bind | bind9 | djbdns | djbdns-installer, libc6 (>= 2.7), 
libldap-2.4-2 (>= 2.4.7)
Recommends: ldap-utils (>= 2.1.22-1)
Description-en: LDAP based DNS management system
 ldap2dns is a program to create DNS (Domain Name Service) records directly
 from a LDAP directory. It can and should be used to replace the secondary
 name-server by a second primary one. ldap2dns reduces all kind of
 administration overhead: No more flat file editing, no more zone file
 editing. After having installed ldap2dns, the administrator only has to
 access the LDAP directory.
 .
 ldap2dns is designed to write ASCII data files used by tinydns from the
 djbdns package, but also may be used to write .db-files used by named as
 found in the BIND package.
Description-md5: e5935d11adb3f1cc6f5c44415284a117
Tag: interface::commandline, protocol::dns, protocol::ldap, role::program,
 scope::utility, works-with::db
Section: admin
Priority: optional
Filename: pool/main/l/ldap2dns/ldap2dns_0.3.1-3.2_amd64.deb
Size: 29606
MD5sum: 86c429be1103c2471c904e7f68dcd7b3
SHA256: cb4b4bad60d41b1668bbe4aade163c57803a44eae9a3ca4e033bae5bebf3f9e7

Package: ldap2dns
Version: 0.3.1-3.1
Installed-Size: 57
Maintainer: Igor Stroh 
Architecture: amd64
Depends: libc6 (>= 2.7), libldap-2.4-2 (>= 2.4.7), bind | bind9 | djbdns | 

Bug#843590: opendnssec: ods-migrate can't open libsqlite3.so

[Simon Ruderich]

Package: opendnssec
Version: 1:2.0.3-1
Severity: important

Hello,

I followed the update instructions for 2.0 and tried to run
ods-migrate, however it failed with the following error:

Failed to load sqlite3 library. dlerror(): libsqlite3.so: cannot open 
shared object file: No such file or directory

A temporary fix is easy (symlink libsqlite3.so.0 to
libsqlite3.so) but I think ods-migrate should be patched to link
against the correct version or at least try to dlopen the
versioned so-file.

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


signature.asc
Description: PGP signature

Bug#843589: opendnssec: Files required for update missing

[Simon Ruderich]

Package: opendnssec
Version: 1:2.0.3-1
Severity: important

Hello,

First a minor issue, the path to the README mentioned in the
update notification doesn't work, the directory
/usr/share/opendnssec/1.4-2.0_db_convert is empty.

But the bigger problem is that convert_sqlite doesn't work
because "../../src/db/schema.sqlite" is not present in the debian
package.

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


signature.asc
Description: PGP signature

Bug#799281: [Mailman-Developers] Let's try to package mailman3 in Debian!

[Pierre-Elliott Bécue]

Le lundi 07 novembre 2016 à 21:42:21+0100, Jan Luca Naumann a écrit :
> Dear Pierre-Elliott Bécue,
> 
> what is the current status of your packaging intend. Since I did not
> the WNPP-list very well I started another ITP (that I closed of course
> now) and maybe we can work together and/or I can take over some of the
> work.
> 
> Best regards,

Dear Jan,

I'd be happy to work with you.

Mostly, all parts of mailman are "pre-packaged" on my server. I met issues
with HyperKitty regarding dependencies, currently, these are not fully
solved, as the devs had to move from django-browserid (implementation of
persona protocol, by Mozilla) to another dependency offering implementation
of a still used protocol (Mozilla is dropping persona).

The second "issue" is mailman itself. It's using python3.4, but default
version of python3 in debian is 3.5 for something like 10 months. I'm
waiting mailman version 3.1, as Barry Warsaw told me it'd use python3.5.

If you wish I can give you the developper accesses on my github repositories
which contain the current packages, except hyperkitty (because of what I
mentioned before).

Cheers,

-- 
PEB


signature.asc
Description: PGP signature

Bug#842919: failed armhf build of xen 4.8.0~rc3-1 [and 1 more messages]

[Kurt Roeckx]

On Mon, Nov 07, 2016 at 08:54:49PM +, Ian Jackson wrote:
> Kurt Roeckx writes ("Re: failed armhf build of xen 4.8.0~rc3-1 [and 1 more 
> messages]"):
> > On Mon, Nov 07, 2016 at 08:05:22PM +, Ian Jackson wrote:
> > > Have I done something wrong ?  Do the buildd chroots need to be
> > > updated ?
> > 
> > The buildd chroots are automatically generated once a week. No
> > package that's installed in the chroot get upgraded without a
> > reason like a Depends requiring them.
> 
> Ah.  We were unlucky then that the broken bintuils ended up cached
> this way.
> 
> > I'll see about upgrading the chroots, I have no idea how to do
> > this myself.
> 
> Thanks.  I do think this should be done, then, as other packages are
> likely to be affected.
> 
> This probably applies to all the architectures, not just armhf and
> i386.  The xen package for sid escaped the bug on amd64 because I
> built it myself.

I just gave back xen and set an extra depends for the fixed
version.

The chroots get updated on sunday and wednesday. It seems to be
easier to just wait for wednesday and give back those few that are
affected. It looks like all buildds actually need the new chroot.


Kurt

Bug#837402: [htcondor-debian] Bug#837402: Fix for the Condor PIE FTBFS

[Tim Theisen]

Hello,

Thank you for this fix. We needed to add -fnoPIC because of the severe 
performance impact on the benchmarks. Adding the -fPIE as well has a 
minimal performance impact. I will apply this patch to our upstream sources.


...Tim

On 11/04/2016 06:14 AM, Adrian Bunk wrote:

Control: tags -1 patch

A fix for the Condor PIE FTBFS is attached.

cu
Adrian



___
htcondor-debian mailing list
htcondor-deb...@cs.wisc.edu
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-debian


--
Tim Theisen
Release Manager
HTCondor & Open Science Grid
Center for High Throughput Computing
Department of Computer Sciences
University of Wisconsin - Madison
4261 Computer Sciences and Statistics
1210 W Dayton St
Madison, WI 53706-1685
+1 608 265 5736

Bug#828287: dsniff: FTBFS with openssl 1.1.0

[Christoph Biedl]

Christoph Biedl wrote...

> The patch attached:

Now really attached.
diff --git a/ssh.c b/ssh.c
index bb73ff3..ee6cb58 100644
--- a/ssh.c
+++ b/ssh.c
@@ -234,6 +234,8 @@ SSH_accept(SSH *ssh)
 	u_char *p, cipher, cookie[8], msg[1024];
 	u_int32_t num;
 	int i;
+	const BIGNUM *servkey_e, *servkey_n;
+	const BIGNUM *hostkey_e, *hostkey_n;
 
 	/* Generate anti-spoofing cookie. */
 	RAND_bytes(cookie, sizeof(cookie));
@@ -243,11 +245,13 @@ SSH_accept(SSH *ssh)
 	*p++ = SSH_SMSG_PUBLIC_KEY;			/* type */
 	memcpy(p, cookie, 8); p += 8;			/* cookie */
 	num = 768; PUTLONG(num, p);			/* servkey bits */
-	put_bn(ssh->ctx->servkey->e, );		/* servkey exponent */
-	put_bn(ssh->ctx->servkey->n, );		/* servkey modulus */
+	RSA_get0_key(ssh->ctx->servkey, _n, _e, NULL);
+	put_bn(servkey_e, );		/* servkey exponent */
+	put_bn(servkey_n, );		/* servkey modulus */
 	num = 1024; PUTLONG(num, p);			/* hostkey bits */
-	put_bn(ssh->ctx->hostkey->e, );		/* hostkey exponent */
-	put_bn(ssh->ctx->hostkey->n, );		/* hostkey modulus */
+	RSA_get0_key(ssh->ctx->hostkey, _n, _e, NULL);
+	put_bn(hostkey_e, );		/* hostkey exponent */
+	put_bn(hostkey_n, );		/* hostkey modulus */
 	num = 0; PUTLONG(num, p);			/* protocol flags */
 	num = ssh->ctx->encmask; PUTLONG(num, p);	/* ciphers */
 	num = ssh->ctx->authmask; PUTLONG(num, p);	/* authmask */
@@ -298,7 +302,7 @@ SSH_accept(SSH *ssh)
 	SKIP(p, i, 4);
 
 	/* Decrypt session key. */
-	if (BN_cmp(ssh->ctx->servkey->n, ssh->ctx->hostkey->n) > 0) {
+	if (BN_cmp(servkey_n, hostkey_n) > 0) {
 		rsa_private_decrypt(enckey, enckey, ssh->ctx->servkey);
 		rsa_private_decrypt(enckey, enckey, ssh->ctx->hostkey);
 	}
@@ -318,8 +322,8 @@ SSH_accept(SSH *ssh)
 	BN_clear_free(enckey);
 
 	/* Derive real session key using session id. */
-	if ((p = ssh_session_id(cookie, ssh->ctx->hostkey->n,
-ssh->ctx->servkey->n)) == NULL) {
+	if ((p = ssh_session_id(cookie, hostkey_n,
+servkey_n)) == NULL) {
 		warn("ssh_session_id");
 		return (-1);
 	}
@@ -328,10 +332,8 @@ SSH_accept(SSH *ssh)
 	}
 	/* Set cipher. */
 	if (cipher == SSH_CIPHER_3DES) {
-		ssh->estate = des3_init(ssh->sesskey, sizeof(ssh->sesskey));
-		ssh->dstate = des3_init(ssh->sesskey, sizeof(ssh->sesskey));
-		ssh->encrypt = des3_encrypt;
-		ssh->decrypt = des3_decrypt;
+		warnx("cipher 3des no longer supported");
+		return (-1);
 	}
 	else if (cipher == SSH_CIPHER_BLOWFISH) {
 		ssh->estate = blowfish_init(ssh->sesskey,sizeof(ssh->sesskey));
@@ -357,6 +359,8 @@ SSH_connect(SSH *ssh)
 	u_char *p, cipher, cookie[8], msg[1024];
 	u_int32_t num;
 	int i;
+	BIGNUM *servkey_n, *servkey_e;
+	BIGNUM *hostkey_n, *hostkey_e;
 
 	/* Get public key. */
 	if ((i = SSH_recv(ssh, pkt, sizeof(pkt))) <= 0) {
@@ -379,21 +383,23 @@ SSH_connect(SSH *ssh)
 
 	/* Get servkey. */
 	ssh->ctx->servkey = RSA_new();
-	ssh->ctx->servkey->n = BN_new();
-	ssh->ctx->servkey->e = BN_new();
+	servkey_n = BN_new();
+	servkey_e = BN_new();
+	RSA_set0_key(ssh->ctx->servkey, servkey_n, servkey_e, NULL);
 
 	SKIP(p, i, 4);
-	get_bn(ssh->ctx->servkey->e, , );
-	get_bn(ssh->ctx->servkey->n, , );
+	get_bn(servkey_e, , );
+	get_bn(servkey_n, , );
 
 	/* Get hostkey. */
 	ssh->ctx->hostkey = RSA_new();
-	ssh->ctx->hostkey->n = BN_new();
-	ssh->ctx->hostkey->e = BN_new();
+	hostkey_n = BN_new();
+	hostkey_e = BN_new();
+	RSA_set0_key(ssh->ctx->hostkey, hostkey_n, hostkey_e, NULL);
 
 	SKIP(p, i, 4);
-	get_bn(ssh->ctx->hostkey->e, , );
-	get_bn(ssh->ctx->hostkey->n, , );
+	get_bn(hostkey_e, , );
+	get_bn(hostkey_n, , );
 
 	/* Get cipher, auth masks. */
 	SKIP(p, i, 4);
@@ -405,8 +411,8 @@ SSH_connect(SSH *ssh)
 	RAND_bytes(ssh->sesskey, sizeof(ssh->sesskey));
 
 	/* Obfuscate with session id. */
-	if ((p = ssh_session_id(cookie, ssh->ctx->hostkey->n,
-ssh->ctx->servkey->n)) == NULL) {
+	if ((p = ssh_session_id(cookie, hostkey_n,
+servkey_n)) == NULL) {
 		warn("ssh_session_id");
 		return (-1);
 	}
@@ -422,7 +428,7 @@ SSH_connect(SSH *ssh)
 		else BN_add_word(bn, ssh->sesskey[i]);
 	}
 	/* Encrypt session key. */
-	if (BN_cmp(ssh->ctx->servkey->n, ssh->ctx->hostkey->n) < 0) {
+	if (BN_cmp(servkey_n, hostkey_n) < 0) {
 		rsa_public_encrypt(bn, bn, ssh->ctx->servkey);
 		rsa_public_encrypt(bn, bn, ssh->ctx->hostkey);
 	}
@@ -470,10 +476,8 @@ SSH_connect(SSH *ssh)
 		ssh->decrypt = blowfish_decrypt;
 	}
 	else if (cipher == SSH_CIPHER_3DES) {
-		ssh->estate = des3_init(ssh->sesskey, sizeof(ssh->sesskey));
-		ssh->dstate = des3_init(ssh->sesskey, sizeof(ssh->sesskey));
-		ssh->encrypt = des3_encrypt;
-		ssh->decrypt = des3_decrypt;
+		warnx("cipher 3des no longer supported");
+		return (-1);
 	}
 	/* Get server response. */
 	if ((i = SSH_recv(ssh, pkt, sizeof(pkt))) <= 0) {
diff --git a/sshcrypto.c b/sshcrypto.c
index 09a04e7..f66202d 100644
--- a/sshcrypto.c
+++ b/sshcrypto.c
@@ -28,10 +28,12 @@ struct blowfish_state {
 	u_char			iv[8];
 };
 
+#if 0
 struct des3_state {
 	des_key_schedule	k1, k2, k3;
 	des_cblock		iv1, iv2, iv3;
 };
+#endif
 
 void
 

Bug#828287: dsniff: FTBFS with openssl 1.1.0

[Christoph Biedl]

Sandro Tosi wrote...

> Hello Dug,
> in Debian we started the transition to OpenSSL 1.1.0: do you have any
> plan to port dsniff to that version?

Since I have some interest in keeping dsniff in Debian, I spent some
time on that bug.

The patch attached:
- replaces the access to struct elements with getter usage.
- disables 3des as it's no longer supported by OpenSSL.

It's pretty much untested and could also take a review.

Christoph


signature.asc
Description: Digital signature

Bug#843588: mesa: FTBFS on hurd-i386 due to PATH_MAX

[Samuel Thibault]

Source: mesa
Version: 13.0.0-1
Severity: important
Tags: upstream patch
User: debian-h...@lists.debian.org
Usertags: hurd
Control: forwarded https://bugs.freedesktop.org/show_bug.cgi?id=98632

Hello,

Just for information and upstream tracking, probably to be turned into
cherry-pick request when fixed upstream.

Thanks,
Samuel

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

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

-- 
Samuel
 > Il [e2fsck] a bien démarré, mais il m'a rendu la main aussitot en me
 > disant "houlala, c'est pas beau à voir votre truc, je préfèrerai que
 > vous teniez vous même la tronçonneuse" (traduction libre)
 NC in Guide du linuxien pervers : "Bien configurer sa tronçonneuse."

Bug#843380: libgvc6 fail to install on stretch

[batta...@libero.it]

While checking for another bug, I found the cause of this also, libgd3 on my 
system was corrupted.After reinstalling it installation of libgvc6 has no 
problem.

Bug#843587: ITP: r-cran-randomfieldsutils -- utilities for the simulation and analysis of random fields

[Andreas Tille]

Package: wnpp
Severity: wishlist
Owner: Andreas Tille 

* Package name: r-cran-randomfieldsutils
  Version : 0.3.3.1
  Upstream Author : Martin Schlather, Reinhard Furrer, Martin Kroll
* URL : https://cran.r-project.org/package=RandomFieldsUtils
* License : GPL-3+
  Programming Lang: GNU-R
  Description : utilities for the simulation and analysis of random fields
 Various utilities are provided that might be used in spatial statistics
 and elsewhere. It delivers a method for solving linear equations that
 checks the sparsity of the matrix before any algorithm is used.
 Furthermore, it includes the Struve functions.

Remark: This package is needed to upgrade r-cran-randomfields to the latest
version.  It is maintained by the Debian Science team at
   
svn://anonscm.debian.org/debian-science/packages/R/r-cran-randomfieldsutils/trunk

Bug#843586: evolution - cited e-mails vanish from reply e-mail while editing

[Zoltan]

Package: evolution
Version: 3.22.1 (testing)


When replying to a chain of cited e-mails, after adding a couple of
empty lines with the button [Enter] in the reply e-mail, the older e-
mails simply vanish. Undo won't restore them in the composing window.
No common-sense / user-friendly way to avoid automatic deletion of
cited older e-mails. 
SERIOUS PROBLEM. Affects core usability of the package / software. 


Using 
Debian GNU/Linux 3.22.1  (stretch)
kernel: Linux 4.7.0-1-686-pae 

Bug#843585: GtkLinkButton has no property "Label" to edit

[Daniel Leidert]

Package: glade
Version: 3.20.0-2
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

When adding a GtkLinkButton there is no property "Label" available to change
the button label. Thus one has to edit the reasulting glade file to change the
label.

Regards, Daniel



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

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

Versions of packages glade depends on:
ii  libc6   2.24-5
ii  libcairo2   1.14.6-1.1
ii  libgdk-pixbuf2.0-0  2.36.0-1
ii  libgladeui-2-6  3.20.0-2
ii  libglib2.0-02.50.1-1
ii  libgtk-3-0  3.22.2-1
ii  libpango-1.0-0  1.40.3-3

Versions of packages glade recommends:
ii  devhelp   3.22.0-1
ii  libgtk-3-dev  3.22.2-1

glade suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJYIO2nAAoJEEvNBWfCltBdsjQQAK/arlQpuBbwxG5WwfQCmlFO
4eL5IS3lDwlVJu6RbwGNy2ra1z9jtgFAcKBxikYBghBr9ZeeCx6Ldthun+Z85OsT
vsRUxCVmCe1FNcCcsCvt8edL3N/lnz5vkhLTIsBHTrMTe/Eo4pxxpsJNbEzvTl2y
Kjr+/H9EFUCkvl46ecK8VNQI5xLYWgqT349VS8EET95sj5uFVNkLdRKE0ldEucAK
67cwLGWY6feKY1Ty1Bde0lCIgPdlaUBS04+CkmC1VPdb8W9WtA7dpZnyQoZuNAXN
dq7kdbrO7mNW6h6Gv5nBcivNXxaLHTRT74U9FBHk0Q2mYCDrH0O5+D98dQw9gG95
Y2i4UKFd6QEcEhQR1/sRTDJVSz7thOypw4lwDzQ6COUCFHx4wfLb4/BAwCdcwaXI
Z+XIz38sTquuAykR3/Wj/tBGHAIwoIkc9a7gXfCpnRdpUngTGIjpO6+h4UgY56a2
6KmbeV/B38xGPfhjO4nZkRFKHM+kFnzC5pEXW0VzDAPzXxtej47/KMI/VAwM12ly
Bh64DqML+5G48p73kXMOMC4t1dju3vxjnBdJrEIMIPdws7rf6QYJhWCHUaelCe+6
qm5Gt4RkeZ9PUYSv9Jxsbf94VKSYzT0FwgimT1zEVmWKao8+VxiQFvU3gXdBl6fi
dncR9ICnC6nTpNna8pbP
=OvnA
-END PGP SIGNATURE-

Bug#842721: jayway-jsonpath: FTBFS (Could not resolve all dependencies)

[Emmanuel Bourg]

Le 1/11/2016 à 07:58, 殷啟聰 a écrit :

> Here's the right link:
> 

I confirm the fix works. Do you know what triggered this error? Was this
caused by the recent changes to gradle-debian-helper?

Emmanuel Bourg

Bug#473383: /usr/bin/glade-3: Cannot create a two-pages notebook

[Daniel Leidert]

Package: glade
Followup-For: Bug #473383

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

This particular issue seems to have been fixed. In the right-mouse-click-dialog
you can choose to remove or add a page. Just click on any child of GtkNotebook.
Unfortunately after removing all pages, I did not yet figure out a way to add
one again :)

Regards, Daniel



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

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

Versions of packages glade depends on:
ii  libc6   2.24-5
ii  libcairo2   1.14.6-1.1
ii  libgdk-pixbuf2.0-0  2.36.0-1
ii  libgladeui-2-6  3.20.0-2
ii  libglib2.0-02.50.1-1
ii  libgtk-3-0  3.22.2-1
ii  libpango-1.0-0  1.40.3-3

Versions of packages glade recommends:
ii  devhelp   3.22.0-1
ii  libgtk-3-dev  3.22.2-1

glade suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJYIOv1AAoJEEvNBWfCltBdgg8QAMie5zS3IEfsxmLkIbKkWHBn
DTE5tuzpZ9/gUoO/vgJyhTg1l5DIIKv2JXYdYSwH5xAEUr/Ub/7zB9uJHZyLiTJd
pvQbJeyACzXAKfjjLIpQpVI++4OCr8KOK5KrrSthLM/+1agpX6d1bVs9xbANq1co
dvXWkJLJltlC61blz30Uymz2Wx6WJqUR3fY8eUBbB8/v5HkyD4dbx6ZenKvJUmj/
0yFaoiFDToJYvpMX9K/TBBDuvkrnCLjPJuWwr+rM/wRblEaywY6K5QiAZCLLJSOX
Ktkiprt1ITo9k5OUYp5SnKGQuXJoXAHfabpHBec0XcH4eV32kdGzpWSL5sj0uCSI
Fdf2FY/2xAYYLSbZQNsYec8M9y1TkeRdgCSb/3tfMsMcSBoZ7UPsFK4bb2hHXIzs
3b3fUEttGiIH+ohsEZycP2C/YhHTewEXtZ66vlYfwFpwZRFL2CvWQyI+tEN/qQ0Y
4ClqeYsWax8Bi3nvxPwjtQ+0lYZy0DmndrcSBPU3xUyRKqjRWvj4+7yYhawgn5ny
YZnOS6EmSJ3odz+Id7jt0yUgGpVF/BBgyFVTdiiJaSksy5EEpuYmX3gSfnbx7bm5
RbXy8fi6U7F0eppXC7xIaMUjS7IOivWbt3Gggg4i8hSu8NJfj6pl624871wBhqzp
MOBVIgQaUj7pJ2I3sHVS
=W6RA
-END PGP SIGNATURE-

Bug#843584: Crash trying to change a toolbar item to be a separator

[Daniel Leidert]

Package: glade
Version: 3.20.0-2
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

There is a reproducible crash.

- - open glade
- - add a GtkToolbar
- - go to "right click" > Edit
- - go to tab "Hierarchy"
- - add an item (push the "+" button")
- - now try to change this item from "button" to "separator"

The crash happens all the time. I can provide a backtrace if necessary. But
because it is reproducible, ...

Regards, Daniel



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

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

Versions of packages glade depends on:
ii  libc6   2.24-5
ii  libcairo2   1.14.6-1.1
ii  libgdk-pixbuf2.0-0  2.36.0-1
ii  libgladeui-2-6  3.20.0-2
ii  libglib2.0-02.50.1-1
ii  libgtk-3-0  3.22.2-1
ii  libpango-1.0-0  1.40.3-3

Versions of packages glade recommends:
ii  devhelp   3.22.0-1
ii  libgtk-3-dev  3.22.2-1

glade suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJYIO0RAAoJEEvNBWfCltBd3xMQAJjg2ARfy5AinzrxF31RtBJ1
zUHDCfQxN7hPkyKbPpGTVrMUIaqIrTOS9OB7USRJ2lrfSwJUke6ftrZkoPpNsYgb
x2ehFkjsdx+dgGQRQW9zf+TKAcwfP5A4DTSTTNvXOMPydqijKSIqeJayv4MAwLHb
u168YAv1VycAIpHYHrcEiGcQrBZAyj8F+D+YG6Q8Sr1dnR0KII0kW0Z9s8pFyP8U
MkJZEp3H5ZaCesqM5YeObgKvTcoRG1yb5+iFfo2RvGKEPY7pazL76piwwYbM7pGI
vB+AZvGLGgvlGpKavd6fX4RJvsBM47cifz9or4oEcVEDagq31WPISWZhjU++O/a7
YOB50yIE3hDUFUrxiuBgP+66cyc90WpBdQTX8pYzUN4rw1E84IyAi5ayiSKVC5w5
HaRvZs2/xKt31PdL5o4Wp/2jlvZo3x7uoMN0Abs3zoYXObhD95CimbjxNSTe0mr7
NHrFJry+b/YRPWUxbD8lofAJgAd4d0aY4D0zRFC2/rxuY05nHz5Bbcb7zBBrCf0B
4AzkIIoOO4noVdv682CHZI7rJj0Dcld5+29SOPhz2Z8tzjgPtwgVokE18sTMORs2
uF70OzEkLMbV7VoaZ3Kahxm3zxJ9m626/5zHTeXnfOVnpFZRwwK/79jpPkrs3KWJ
H84c188iU+dIwloECxpK
=fHkr
-END PGP SIGNATURE-

Bug#843532: dnssec-trigger: broken by OpenSSL 1.1.0

[Sebastian Andrzej Siewior]

control: tags -1 patch

On 2016-11-07 08:39:17 [-0500], Zack Weinberg wrote:
> Nov 07 08:34:17 moxana dnssec-triggerd[20281]: Nov 07 08:34:17 
> dnssec-triggerd[20281] error: could not set SSL_OP_NO_SSLv2 crypto 
> error:

could someone please check if the patch attached works? I am confident
but don't time todo it myself just now.

Sebastian
>From 05cd529e19d317b8bcc69f7d883873a27195b904 Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior 
Date: Mon, 7 Nov 2016 20:59:11 +
Subject: [PATCH] dnssec-trigger: openssl 1.1.0 fixup

- SSL_OP_NO_SSLv2 / SSLv2 has been removed from openssl 1.1.0 and as
  such it can't be tested (the way it is) if disabling it worked.

- SSL_CTX_load_verify_locations() return 1 un success and 0 on failure.
  The check for the result code is bogus and has nothing to do with the
  switch to openssl 1.1.0 itself

- ERR_remove_state() and friends are NOPs in current openssl 1.1.0 due
  the threading model. This operations are nops therefore and do nothing
  and can be removed in a later version.

Signed-off-by: Sebastian Andrzej Siewior 
---
 riggerd/cfg.c  | 2 ++
 riggerd/net_help.c | 4 +++-
 riggerd/riggerd.c  | 2 ++
 riggerd/svr.c  | 2 ++
 4 files changed, 9 insertions(+), 1 deletion(-)

diff --git a/riggerd/cfg.c b/riggerd/cfg.c
index 03f4f73..08b2028 100644
--- a/riggerd/cfg.c
+++ b/riggerd/cfg.c
@@ -540,9 +540,11 @@ cfg_setup_ctx_client(struct cfg* cfg, char* err, size_t errlen)
 	if(!ctx)
 		return ctx_err_ret(ctx, err, errlen,
 			"could not allocate SSL_CTX pointer");
+#if OPENSSL_VERSION_NUMBER < 0x1010
 	if(!(SSL_CTX_set_options(ctx, SSL_OP_NO_SSLv2) & SSL_OP_NO_SSLv2))
 		return ctx_err_ret(ctx, err, errlen, 
 			"could not set SSL_OP_NO_SSLv2");
+#endif
 	if(!SSL_CTX_use_certificate_file(ctx,c_cert,SSL_FILETYPE_PEM) ||
 		!SSL_CTX_use_PrivateKey_file(ctx,c_key,SSL_FILETYPE_PEM)
 		|| !SSL_CTX_check_private_key(ctx))
diff --git a/riggerd/net_help.c b/riggerd/net_help.c
index 21e79e7..b17486c 100644
--- a/riggerd/net_help.c
+++ b/riggerd/net_help.c
@@ -447,11 +447,13 @@ void* listen_sslctx_create(char* key, char* pem, char* verifypem)
 		return NULL;
 	}
 	/* no SSLv2 because has defects */
+#if OPENSSL_VERSION_NUMBER < 0x1010
 	if(!(SSL_CTX_set_options(ctx, SSL_OP_NO_SSLv2) & SSL_OP_NO_SSLv2)){
 		log_crypto_err("could not set SSL_OP_NO_SSLv2");
 		SSL_CTX_free(ctx);
 		return NULL;
 	}
+#endif
 	if(!SSL_CTX_use_certificate_file(ctx, pem, SSL_FILETYPE_PEM)) {
 		log_err("error for cert file: %s", pem);
 		log_crypto_err("error in SSL_CTX use_certificate_file");
@@ -517,7 +519,7 @@ void* connect_sslctx_create(char* key, char* pem, char* verifypem)
 		}
 	}
 	if(verifypem && verifypem[0]) {
-		if(!SSL_CTX_load_verify_locations(ctx, verifypem, NULL) != 1) {
+		if(SSL_CTX_load_verify_locations(ctx, verifypem, NULL) != 1) {
 			log_crypto_err("error in SSL_CTX verify");
 			SSL_CTX_free(ctx);
 			return NULL;
diff --git a/riggerd/riggerd.c b/riggerd/riggerd.c
index 9cb6023..2490a72 100644
--- a/riggerd/riggerd.c
+++ b/riggerd/riggerd.c
@@ -393,10 +393,12 @@ int main(int argc, char *argv[])
 #ifdef HAVE_OPENSSL_CONF_H
 	CONF_modules_free();
 #endif
+#if OPENSSL_VERSION_NUMBER < 0x1010
 	CRYPTO_cleanup_all_ex_data();
 	ERR_remove_state(0);
 	ERR_free_strings();
 	RAND_cleanup();
+#endif
 
 #ifdef USE_WINSOCK
 	if(WSACleanup() != 0) {
diff --git a/riggerd/svr.c b/riggerd/svr.c
index 0b46b1d..5f232f4 100644
--- a/riggerd/svr.c
+++ b/riggerd/svr.c
@@ -162,10 +162,12 @@ static int setup_ssl_ctx(struct svr* s)
 		return 0;
 	}
 	/* no SSLv2 because has defects */
+#if OPENSSL_VERSION_NUMBER < 0x1010
 	if(!(SSL_CTX_set_options(s->ctx, SSL_OP_NO_SSLv2) & SSL_OP_NO_SSLv2)){
 		log_crypto_err("could not set SSL_OP_NO_SSLv2");
 		return 0;
 	}
+#endif
 	s_cert = s->cfg->server_cert_file;
 	s_key = s->cfg->server_key_file;
 	verbose(VERB_ALGO, "setup SSL certificates");
-- 
2.10.2

Bug#818107: The future of DocOnce

[Francesco Poli]

On Mon, 7 Nov 2016 17:03:07 + Kristian Gregorius Hustad wrote:

> Version 1.0.0 is now listed at https://github.com/hplgit/doconce/releases 

That's awesome, thanks a lot!   :-)

Now I hope the Debian Python Applications Packaging Team will consider
packaging it...

-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpnKW5npr0Y6.pgp
Description: PGP signature

Bug#842796: libc recently more aggressive about pthread locks in stable ?

[Lucas Nussbaum]

Hi,

On 06/11/16 at 17:41 -0200, Henrique de Moraes Holschuh wrote:
> On Sun, 06 Nov 2016, Ben Hutchings wrote:
> > It's worth noting that TSX is broken in 'Haswell' processors and is
> > supposed to be disabled via a microcode update.  I don't know whether
> > glibc avoids using it on these processors if the microcode update is
> > not applied.  (Linux doesn't appear to hide the feature flags.)
> 
> It does avoid it.  For glibc libpthreads, Debian has blacklisted Intel
> TSX use [in libpthreads] on all of Haswell and much of Broadwell.
> 
> But anything else *will* attempt to use it, people query cpuid directly
> for these things.  You need a hypervisor that filters cpuid().

How can one know what glibc does on a given CPU? (preferably without
access to the hardware)

I could try to run an archive rebuild on hardware where glibc leverages
TSX to see what happens.

Lucas

Bug#842919: failed armhf build of xen 4.8.0~rc3-1 [and 1 more messages]

[Ian Jackson]

Kurt Roeckx writes ("Re: failed armhf build of xen 4.8.0~rc3-1 [and 1 more 
messages]"):
> On Mon, Nov 07, 2016 at 08:05:22PM +, Ian Jackson wrote:
> > Have I done something wrong ?  Do the buildd chroots need to be
> > updated ?
> 
> The buildd chroots are automatically generated once a week. No
> package that's installed in the chroot get upgraded without a
> reason like a Depends requiring them.

Ah.  We were unlucky then that the broken bintuils ended up cached
this way.

> I'll see about upgrading the chroots, I have no idea how to do
> this myself.

Thanks.  I do think this should be done, then, as other packages are
likely to be affected.

This probably applies to all the architectures, not just armhf and
i386.  The xen package for sid escaped the bug on amd64 because I
built it myself.

Thanks,
Ian.

Bug#843227: PTS, UDD: packages removed from testing still listed in testing

[Lucas Nussbaum]

On 05/11/16 at 11:31 +0200, Adrian Bunk wrote:
> Package: qa.debian.org
> Severity: normal
> 
> I came across an odd bug affecting both packages.qa.d.o and UDD:
> 
> https://packages.qa.debian.org/b/banshee.html
> [2016-09-01] banshee REMOVED from testing (Britney)
> testing 2.6.2-4
> 
> https://tracker.debian.org/pkg/banshee
> Correct information that the package is not in testing.
> 
> https://udd.debian.org/bugs/?release=sid_not_stretch=ign=ign=7=7=1=source=asc=html#results
> this is "bug is in unstable and not in testing, package is in testing"
> #805997 in src:banshee is listed here
> This is correct information from the BTS (bug is not in testing),
> but UDD thinks the package is still in testing.

Hi Adrian,

That's because the (source) package is still in testing, but only
because another package (in testing) was built using it:

udd=> select source,extra_source_only from sources where source='banshee' and 
release='stretch';
 source  | extra_source_only 
-+---
 banshee | t
(1 row)

For example:

Package: gnome-do-plugins
Version: 0.8.5-4
[...]
Built-Using: banshee (= 2.6.2-4)

It's not clear what to do in that case; I think that being on the safe side is
considering that the package is still in testing, because we would ship that
source. In some cases (e.g. undistributable source) it would make to go further
and really remove it completely from testing.

Lucas

Bug#843583: RFS: imagemagick/8:6.9.6.2+dfsg-3

[Bastien ROUCARIES]

Package: sponsorship-requests
Severity: normal [important for RC bugs, wishlist for new packages]

  Dear mentors,

  I am looking for a sponsor for my package "imagemagick"

 * Package name: imagemagick
   Version : 8:6.9.6.2+dfsg-3
 * License : imagemagick
   Section : graphics

  It builds those binary packages:

imagemagick - image manipulation programs -- binaries
 imagemagick-6-common - image manipulation programs -- infrastructure
 imagemagick-6-doc - document files of ImageMagick
 imagemagick-6.q16 - image manipulation programs -- quantum depth Q16
 imagemagick-6.q16hdri - image manipulation programs -- quantum depth Q16HDRI
 imagemagick-common - image manipulation programs -- infrastructure
dummy package
 imagemagick-doc - document files of ImageMagick -- dummy package
 libimage-magick-perl - Perl interface to the ImageMagick graphics routines
 libimage-magick-q16-perl - Perl interface to the ImageMagick graphics
routines -- Q16 versio
 libimage-magick-q16hdri-perl - Perl interface to the ImageMagick
graphics routines -- Q16HDRI ve
 libmagick++-6-headers - object-oriented C++ interface to ImageMagick
- header files
 libmagick++-6.q16-6v6 - C++ interface to ImageMagick -- quantum depth Q16
 libmagick++-6.q16-dev - C++ interface to ImageMagick - development files (Q16)
 libmagick++-6.q16hdri-6v6 - C++ interface to ImageMagick -- quantum
depth Q16HDRI
 libmagick++-6.q16hdri-dev - C++ interface to ImageMagick -
development files (Q16HDRI)
 libmagick++-dev - object-oriented C++ interface to ImageMagick -- dummy package
 libmagickcore-6-arch-config - low-level image manipulation library -
architecture header files
 libmagickcore-6-headers - low-level image manipulation library - header files
 libmagickcore-6.q16-2 - low-level image manipulation library --
quantum depth Q16
 libmagickcore-6.q16-2-extra - low-level image manipulation library -
extra codecs (Q16)
 libmagickcore-6.q16-dev - low-level image manipulation library -
development files (Q16)
 libmagickcore-6.q16hdri-2 - low-level image manipulation library --
quantum depth Q16HDRI
 libmagickcore-6.q16hdri-2-extra - low-level image manipulation
library - extra codecs (Q16HDRI)
 libmagickcore-6.q16hdri-dev - low-level image manipulation library -
development files (Q16HDRI
 libmagickcore-dev - low-level image manipulation library -- dummy package
 libmagickwand-6-headers - image manipulation library - headers files
 libmagickwand-6.q16-2 - image manipulation library -- quantum depth Q16
 libmagickwand-6.q16-dev - image manipulation library - development files (Q16)
 libmagickwand-6.q16hdri-2 - image manipulation library -- quantum depth Q16HDRI
 libmagickwand-6.q16hdri-dev - image manipulation library -
development files (Q16HDRI)
 libmagickwand-dev - image manipulation library -- dummy package
 perlmagick - Perl interface to ImageMagick -- dummy package

  To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/imagemagick


  Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/i/imagemagick/imagemagick_6.9.6.2+dfsg-3.dsc

  Changes since the last upload:
Mainly create package for high dynamic range. No upstream code change


  Regards,
   bastien roucaries

Bug#843386: [php-maint] Bug#843386: php7.0-gd: wrong libwebp dependency

[batta...@libero.it]

> Strange, it doesn't exhibit on my system:
> 
> ondrej@komorebi:~$ ldd /usr/lib/php/20151012/gd.so | grep webp
>   libwebp.so.6 => /usr/lib/x86_64-linux-gnu/libwebp.so.6
>   (0x7f7a085dd000)
> ondrej@komorebi:~$ sha256sum /usr/lib/php/20151012/gd.so
> 31a113c71efc66abe161f3034cf0c4a89aad3575d8df25c6c17b1186179b952d 
> /usr/lib/php/20151012/gd.so
> 
> Are you sure the modules comes from the package?
> apt-get install debsums
> debsums php7.0-gd
I did some checks, I found the dependecy to be indirect from libgd3.so.3,and 
the file was corrupted, reinstalling libgd3 solves the problem.

Bug#841853: inkscape: Mouse cursor is a white outline on PowerPC

[Mattia Rizzolo]

Control: tag -1 pending

On Mon, Nov 07, 2016 at 12:46:25PM -0500, Steven Gawroriski wrote:
> > I'll see about uploading an updated debian package with this too.
> 
> That would be cool.

Committed:
https://anonscm.debian.org/git/pkg-multimedia/inkscape.git/commit/?id=0be84125610e178c2e68fbc03f13ed88128a9d32


I'd like to also include anohter thing before uploading, but it'll come.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#799281: [Mailman-Developers] Let's try to package mailman3 in Debian!

[Jan Luca Naumann]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Pierre-Elliott Bécue,

what is the current status of your packaging intend. Since I did not
the WNPP-list very well I started another ITP (that I closed of course
now) and maybe we can work together and/or I can take over some of the
work.

Best regards,
Jan

On Fri, 19 Feb 2016 11:26:15 +0100 Pierre-Elliott
=?iso-8859-1?Q?B=E9cue?=  wrote:
> 
> Hello!
> 
> Before requesting for sponsorship, and packaging officially the
> other components of mailman3, I'd like some "testers" for the core
> package I built, in order to be sure that it works, and that I will
> not introduce some stupid caveats on the packaging of the other
> components.
> 
> .deb can be found here:
> http://peb.pimeys.fr/mailman/mailman3-core/ git repo can be found
> there: https://gitlab.pimeys.fr/PEB/mailman3-core and there:
> https://github.com/P-EB/mailman3-core
> 
> Any volunteer welcome! Please, I need your help, I cannot review my
> work alone! :)
> 
> -- PEB
> 
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJYIOctAAoJEH4R1/EZ+XG7QdEQAKvSTrZeexBJLZnHXddRxCW+
W5HUxJryZvQiu73cw5w/1ra008bjWZOHzCD+oj9WdbxrKE+QFf46Zl+gFEfQO2Qf
+nNHjZIxzwK5UFrw119lhxqTrALoaJs7FgoWxnA98v0wXQ9UdXcmve7HA4fVIAOS
uL5tvybnj+SLUpw7/VPEgl1SGdhOrcRQD5m/6notmR+2JgRfYCzvptoNxv4uDGD4
ZEV/t+BxJsMuv4mS9l+mZLN6FoOBaq+Wwd9w3/Vea9npxliIFRJ54Zp0nT+uhzjG
Uyhepw4/qgRAj1hBDx+UnKwn84qd1YsTJ9LzPqMJg48LBR58bt+y5d6hX8MFpfAW
NG2aunZlwj/i7/J1uvkYJTXA/1VLtBxaWHuR2jjAQVvFjnEPHBquNSIUqinl2hv/
d+xSCnx8OGDUG231uWYiQAZWhXUGy3eyEjJjpEiyKTQyhW0msgxow9IozdVpKURY
wBcykEpa815YDfzCtHOYtdGziTEHq6Z2mGEc1kbCd9q51b7fsSMeABr7pxqyDcyA
Y5csXo9PsrdSg10a5USn29kTZiiE3V7jiiK/q6HUpcochAn2ebyE1sDea2m8HDMc
FHEJ4wlWQwRqbJ/D2PwnoZUTXyA8oe8AJTqKKqAWHLhO2qWEm9WOIf1wZ8efiyzx
K32qAoT/7AAazKn8puGY
=2jY1
-END PGP SIGNATURE-

Bug#843328: O: dimbl - Distributed Memory Based Learner for Natural Language Processing

[Joost van Baal-Ilić]

Hi Bálint,

On Mon, Nov 07, 2016 at 08:45:07PM +0100, Bálint Réczey wrote:
> 2016-11-05 22:17 GMT+01:00 Joost van Baal-Ilić
> :
> >
> > I am no longer interested in maintaining dimbl.  Upstream (Maarten van 
> > Gompel)
> > feels shipping dimbl with Debian is of very limited use: people interested 
> > in
> > dimbl likely are better served always using the very latest version of it.
> >
> > I'll request for removal of dimbl from unstable and testing, soonish.
> 
> I suggest not requesting the removal. The package was practically
> unmaintained in Debian for years (last upload: 2013-09-17) while upstream
> is not exactly fast moving (last release was in January).
> Please delay the removal request by at least 6 months to let others step
> up as maintainers.
> 
> I may fix the RC bug with a new upstream during the freeze after all
> packages under my name are ready for Stretch.

Great, consider this package yours.

Thanks a lot, Bye,

Joost


> Joost wrote:
> > Unless someone else steps up RSN, that is.  Be aware there is 
> > serious/RC/FTBFS
> > Bug #833905 open (which is relatively easy to fix).)
> >
> > (From the description: The Dimbl Distributed Memory Based Learner is a 
> > wrapper
> > around the k-nearest neighbor classifier in TiMBL, offering parallel
> > classification on multi-CPU machines. Dimbl splits the original training 
> > set,
> > builds separate TiMBL classifiers per training subset, and merges their
> > nearest-neighbor sets per classified instance.  If you do scientific 
> > research
> > in Natural Language Processing using the Memory-Based Learning technique, 
> > Dimbl
> > will likely be of use to you.)


signature.asc
Description: Digital signature

Bug#842919: failed armhf build of xen 4.8.0~rc3-1 [and 1 more messages]

[Kurt Roeckx]

On Mon, Nov 07, 2016 at 08:05:22PM +, Ian Jackson wrote:
> Debian buildds writes ("failed armhf build of xen 4.8.0~rc3-1"):
> >  * Source package: xen
> >  * Version: 4.8.0~rc3-1
> >  * Architecture: armhf
> >  * State: failed
> >  * Suite: sid
> >  * Builder: hartmann.debian.org
> >  * Build log: 
> > https://buildd.debian.org/status/fetch.php?pkg=xen=armhf=4.8.0%7Erc3-1=1478544996=log
> 
> Debian buildds writes ("failed i386 build of xen 4.8.0~rc3-1"):
> >  * Source package: xen
> >  * Version: 4.8.0~rc3-1
> >  * Architecture: i386
> >  * State: failed
> >  * Suite: sid
> >  * Builder: x86-grnet-01.debian.org
> >  * Build log: 
> > https://buildd.debian.org/status/fetch.php?pkg=xen=i386=4.8.0%7Erc3-1=1478544915=log
> 
> These builds failed because they were done with binutils
> 2.27.51.20161105-1.  That version had a severe bug that causes ld to
> spin on the cpu (on amd64 and other architectures, apparently).
> 
> I uploaded xen 4.8.0~rc3-1 to sid after I observed that my amd64 sid
> chroot had obtained 2.27.51.20161105-2 which has the fix.  4.8.0~rc3-1
> has no code changes compared to 4.8.0~rc3-0exp2 which built on all
> applicable architectures in experimental.
> 
> I see from
>   https://buildd.debian.org/status/package.php?p=binutils=sid
> that the fixed version of binutils is showing as "Installed" for armhf
> and i386.
> 
> Have I done something wrong ?  Do the buildd chroots need to be
> updated ?

The buildd chroots are automatically generated once a week. No
package that's installed in the chroot get upgraded without a
reason like a Depends requiring them.

I'll see about upgrading the chroots, I have no idea how to do
this myself.


Kurt

Bug#843582: 0xffff: Zsh completion should be deployed to /usr/share/zsh/vendor-completions

[Frank Terbeck]

Package: 0x
Version: 0.6.1-3
Severity: normal

Dear Maintainer,

Debian's zsh package offers a dedicated directory for other packages to
put additional completion function files into. That directory is:

  /usr/share/zsh/vendor-completions

0x seems to use:

  /usr/share/zsh/functions/Completion/Unix/_0x

Please consider using the dedicated directory instead.

See the zsh package's README for details:

  https://anonscm.debian.org/cgit/collab-maint/zsh.git/tree/debian/README.Debian

Regards, Frank — on behalf of the pkg-zsh team.

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

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

Bug#843576: taskwarrior: Zsh completion should be deployed to /usr/share/zsh/vendor-completions

[Frank Terbeck]

Package: taskwarrior
Version: 2.5.1+dfsg-1
Severity: normal

Dear Maintainer,

Debian's zsh package offers a dedicated directory for other packages to
put additional completion function files into. That directory is:

  /usr/share/zsh/vendor-completions

taskwarrior seems to use:

  /usr/share/zsh/functions/Completion/Unix/_task

Please consider using the dedicated directory instead.

See the zsh package's README for details:

  https://anonscm.debian.org/cgit/collab-maint/zsh.git/tree/debian/README.Debian

Regards, Frank — on behalf of the pkg-zsh team.

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

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

Bug#843581: python3-doit: Zsh completion should be deployed to /usr/share/zsh/vendor-completions

[Frank Terbeck]

Package: python3-doit
Version: 0.28.0-1
Severity: normal

Dear Maintainer,

Debian's zsh package offers a dedicated directory for other packages to
put additional completion function files into. That directory is:

  /usr/share/zsh/vendor-completions

python3-doit seems to use:

  /usr/share/zsh/functions/Completion/Linux/_doit3

Please consider using the dedicated directory instead.

See the zsh package's README for details:

  https://anonscm.debian.org/cgit/collab-maint/zsh.git/tree/debian/README.Debian

Regards, Frank — on behalf of the pkg-zsh team.

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

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

Bug#843578: dochelp: Zsh completion should be deployed to /usr/share/zsh/vendor-completions

[Frank Terbeck]

Package: dochelp
Version: 0.1.3+b1
Severity: normal

Dear Maintainer,

Debian's zsh package offers a dedicated directory for other packages to
put additional completion function files into. That directory is:

  /usr/share/zsh/vendor-completions

dochelp seems to use:

  /usr/share/zsh/functions/Completion/Debian/_dochelp

Please consider using the dedicated directory instead.

See the zsh package's README for details:

  https://anonscm.debian.org/cgit/collab-maint/zsh.git/tree/debian/README.Debian

Regards, Frank — on behalf of the pkg-zsh team.

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

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

Bug#843573: herbstluftwm: Zsh completion should be deployed to /usr/share/zsh/vendor-completions

[Frank Terbeck]

Package: herbstluftwm
Version: 0.7.0-1
Severity: normal

Dear Maintainer,

Debian's zsh package offers a dedicated directory for other packages to
put additional completion function files into. That directory is:

  /usr/share/zsh/vendor-completions

herbstluftwm seems to use:

  /usr/share/zsh/functions/Completion/X/_herbstclient

Please consider using the dedicated directory instead.

See the zsh package's README for details:

  https://anonscm.debian.org/cgit/collab-maint/zsh.git/tree/debian/README.Debian

Regards, Frank — on behalf of the pkg-zsh team.

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

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

Bug#843580: autojump: Zsh completion should be deployed to /usr/share/zsh/vendor-completions

[Frank Terbeck]

Package: autojump
Version: 22.5.0-1
Severity: normal

Dear Maintainer,

Debian's zsh package offers a dedicated directory for other packages to
put additional completion function files into. That directory is:

  /usr/share/zsh/vendor-completions

autojump seems to use:

  /usr/share/zsh/functions/Completion/Unix/_j

Please consider using the dedicated directory instead.

See the zsh package's README for details:

  https://anonscm.debian.org/cgit/collab-maint/zsh.git/tree/debian/README.Debian

Regards, Frank — on behalf of the pkg-zsh team.

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

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

Bug#843575: ninja-build: Zsh completion should be deployed to /usr/share/zsh/vendor-completions

[Frank Terbeck]

Package: ninja-build
Version: 1.7.1-1
Severity: normal

Dear Maintainer,

Debian's zsh package offers a dedicated directory for other packages to
put additional completion function files into. That directory is:

  /usr/share/zsh/vendor-completions

ninja-build seems to use:

  /usr/share/zsh/functions/Completion/_ninja

Please consider using the dedicated directory instead.

See the zsh package's README for details:

  https://anonscm.debian.org/cgit/collab-maint/zsh.git/tree/debian/README.Debian

Regards, Frank — on behalf of the pkg-zsh team.

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

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