Bug#855877: [Python-modules-team] Bug#855877: python3-django-celery: management commands broken with Django 1.10

[Brian May]

Antonio Terceiro  writes:

> Package: python3-django-celery
> Version: 3.1.17-3.1
> Severity: grave
> Forwarded: https://github.com/celery/django-celery/pull/458
> Justification: renders package unusable

Unblock request sent #855899
-- 
Brian May 

Bug#816063: emacs24: TLS certificate validation is silently broken

[Trent W. Buck]

Antoine Beaupre wrote:
> tags -1 -unreproducible
>
> I can reproduce issues with certification verification in Emacs 24.5+1-8
> in Debian Stretch. As documented here:
>
> [...]
>
> I am not sure what changed between Emacs 24 and 25, but it seems to me
> Emacs 24 should absolutely be fixed before Stretch is released, or just
> be removed from stretch.

Stretch currently has both emacs24 and emacs25,
so is there any major downside to removing emacs24 from Stretch?

Bug#816063: emacs24: TLS certificate validation is silently broken

[Rob Browning]

"Trent W. Buck"  writes:

> Stretch currently has both emacs24 and emacs25,
> so is there any major downside to removing emacs24 from Stretch?

I think it would be fairly straightforward, though it might still
require a bit of work to fix the few reverse deps that dak didn't catch,
but Sean and I are now quite familiar with that process -- unless of
course the reverse deps just aren't compatible with 25.

FWIW, I'd probably be able to make/spend a good bit of time on this over
the next few weeks if it's actually still a possibility.  I'm fairly
certain that would be more effort now in exchange for *much* less effort
over the next year or two for any number of people.

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

Bug#816063: emacs24: TLS certificate validation is silently broken

[Antoine Beaupré]

On 2017-02-23 12:41:05, Trent W. Buck wrote:
> Antoine Beaupre wrote:
>> tags -1 -unreproducible
>>
>> I can reproduce issues with certification verification in Emacs 24.5+1-8
>> in Debian Stretch. As documented here:
>>
>> [...]
>>
>> I am not sure what changed between Emacs 24 and 25, but it seems to me
>> Emacs 24 should absolutely be fixed before Stretch is released, or just
>> be removed from stretch.
>
> Stretch currently has both emacs24 and emacs25,
> so is there any major downside to removing emacs24 from Stretch?

Not from my perspective. I've been happily running emacs 25 since i
upgraded, without any significant issue.

I'm using Notmuch, Auctex, Markdown, Go modes and all sorts of other
random shit. It just works.

A.

-- 
Les plus beaux chants sont les chants de revendications
Le vers doit faire l'amour dans la tête des populations.
À l'école de la poésie, on n'apprend pas: on se bat!
- Léo Ferré, "Préface"

Processed: Merge duplicates

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 854692 serious
Bug #854692 {Done: Matthias Klose } [gcc-6] pybind11: FTBFS 
due to an internal compiler error
Severity set to 'serious' from 'important'
> forcemerge 854692 855883
Bug #854692 {Done: Matthias Klose } [gcc-6] pybind11: FTBFS 
due to an internal compiler error
Bug #855883 [gcc-6] pybind11: FTBFS in stretch
Marked Bug as done
Removed indication that 855883 affects pybind11
Marked as fixed in versions gcc-6/6.3.0-7.
Marked as found in versions gcc-6/6.3.0-6.
Added tag(s) fixed-upstream.
Merged 854692 855883
> affects 854692 src:pybind11
Bug #854692 {Done: Matthias Klose } [gcc-6] pybind11: FTBFS 
due to an internal compiler error
Bug #855883 {Done: Matthias Klose } [gcc-6] pybind11: FTBFS in 
stretch
Added indication that 854692 affects src:pybind11
Added indication that 855883 affects src:pybind11
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
854692: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854692
855883: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855883
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#816063: emacs24: TLS certificate validation is silently broken

[Rob Browning]

[Summary: say the word and I (and Sean, I strongly suspect) will
 immediately resume the (possibly minimal) work that remains before we
 can remove emacs24 from stretch.]

Antoine Beaupre  writes:

> I am not sure what changed between Emacs 24 and 25, but it seems to me
> Emacs 24 should absolutely be fixed before Stretch is released, or just
> be removed from stretch.

Well, of course broadly speaking, I'm still very much in favor of
removing emacs24 from stretch.

Sean and I put in a good bit of time toward that end before the most
recent freeze deadline, and thought we were going to make it:

  https://wiki.debian.org/Emacs25InStretch

but we were surprised at the "last minute" by some packages that "dak
-Rn emacs24" didn't report.  Likely my fault for (I assume)
misunderstanding dak's behavior.  I suspect that fixing the remaining
packages wouldn't be too hard, but we stopped worrying about it because
those uploads wouldn't have made the deadline.

In any case, if there's still any chance we can remove emacs24, I think
we'd all (users and contributors) be better off without having to carry
emacs24 through stretch.  (I think users would also be better off
without emacs and emacs-nox metapackages that point to 24, even if
emacs24 were still in stretch.)

And while I'm certainly willing to put in time to try to fix the current
issue for emacs24.  If it's non-trivial, I imagine that time would be
better spent finishing the removal.

However, I also understand that Emacs 25 may have been released too
close to the freeze (given the stability issues that we had to track
down) for that to be feasible.

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

Bug#855895: lvm2: lvchange while raid1 conversion active causes instant and serious loss of whole device

[Marc Lehmann]

Package: lvm2
Version: 2.02.168(2) (2016-11-30)
Severity: critical
Justification: causes serious data loss

Dear Maintainer,

I just lost the root filesystem on one of my boxes within a few seconds by
converting an existing LV to raid1 type and then trying to set writemostly
behaviour on the origin disk. The fs is now completey corrupted and I have
very limited logs, but I will try to splice together what happened in the
hope of this being useful to replicate and fix the issue.

I might also note that I didn't lose the actual data, as I have a complete
backup, so I got away with having some hours of extra work and a reboot
(which unfortunately involves a lot of manual steps...), but I think this
is very unexpected behaviour and can result in very serious data loss.

Basically, the following sequence of commands trashed the fs.

First convert an existing linear lv on sda to raid1. The only allocatable
space was on sdb:

   # lvconvert --type raid1 --mirrors 1 vg_fuji/root

All ok till here, and then about 40 seconds later I entered this, which
apparently triggered the destruction:

   # lvchange --writemostly /dev/sda2 vg_fuji/root
   Logical volume vg_fuji/root changed.

I skimmed the manpage and tried again (this probably didn't make it worse):

   # lvchange --writemostly /dev/sda2 vg_fuji/root
   Logical volume vg_fuji/root changed.

And then a few seconds later, btrfs complained about corruption in the
kernel log, and...

   # df -h /
   -bash: /bin/df: Input/output error

I had dstat running concurrently (see "appendix"), so I have a good idea
of what happened. Immediately after the lvconvert, I had lots of read I/O
from the existing lv on sda2, and the same amount of write activity on
sdb2, which is the only device where the mirror could be created. When
I issued the lvchange command, the I/O direction suddenly changed - it
started reading from the new device, writing back to the old device.

The time between commands was long enough to copy about 1.2GB at 30MB/s,
and since the root device is 15GB large, it's absolutely impossible that
the whole device was mirrored fully before lvm/md started "syncing" back.

The kernel log gives some more insights. It starts when I issued the
lvconvert, as I did dmesg -c before:

   [ 7027.947881] async_tx: api initialized (async)
   [ 7027.969794] md: raid6 personality registered for level 6
   [ 7027.969801] md: raid5 personality registered for level 5
   [ 7027.969803] md: raid4 personality registered for level 4
   [ 7027.973665] device-mapper: raid: Loading target version 1.7.0
   [ 7028.269268] device-mapper: raid: Superblocks created for new array
   [ 7028.277085] md: raid1 personality registered for level 1
   [ 7028.279282] md/raid1:mdX: not clean -- starting background reconstruction
   [ 7028.279287] md/raid1:mdX: active with 2 out of 2 mirrors
   [ 7028.279293] Choosing daemon_sleep default (5 sec)
   [ 7028.279298] created bitmap (15 pages) for device mdX
   [ 7028.335126] mdX: bitmap file is out of date, doing full recovery
   [ 7028.342576] mdX: bitmap initialized from disk: read 1 pages, set 30720 of 
30720 bits
   [ 7028.354762] md: resync of RAID array mdX
   [ 7028.354771] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
   [ 7028.354775] md: using maximum available idle IO bandwidth (but not more 
than 20 KB/sec) for resync.
   [ 7028.354791] md: using 128k window, over a total of 15728640k.

Very likely, at this point I issued the lvchange:

   [ 7067.066129] md/raid1:mdX: not clean -- starting background reconstruction
   [ 7067.066136] md/raid1:mdX: active with 2 out of 2 mirrors
   [ 7067.066303] created bitmap (15 pages) for device mdX
   [ 7067.117388] md: mdX: resync interrupted.
   [ 7067.182336] md: checkpointing resync of mdX.
   [ 7067.238944] mdX: bitmap initialized from disk: read 1 pages, set 28390 of 
30720 bits
   [ 7067.253829] md: resync of RAID array mdX
   [ 7067.253841] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
   [ 7067.253843] md: using maximum available idle IO bandwidth (but not more 
than 20 KB/sec) for resync.
   [ 7067.253848] md: using 128k window, over a total of 15728640k.

The above seems to have been the point where data copy changed
direction. What follows is likely the result of my second lvchange
command:

   [ 7086.544989] md/raid1:mdX: not clean -- starting background reconstruction
   [ 7086.545000] md/raid1:mdX: active with 2 out of 2 mirrors
   [ 7086.545177] created bitmap (15 pages) for device mdX
   [ 7086.944772] md: mdX: resync interrupted.
   [ 7086.946987] md: checkpointing resync of mdX.
   [ 7101.047749] mdX: bitmap initialized from disk: read 1 pages, set 27932 of 
30720 bits
   [ 7101.780179] md: resync of RAID array mdX
   [ 7101.780186] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
   [ 7101.780188] md: using maximum available idle IO bandwidth (but not more 
than 20 KB/sec) for resync.
   [ 7101.780191] md: using 128k window, over a total of 15728640k.

And this 

Bug#855541: purple-matrix: Not ready for release yet

[Kurt Roeckx]

On Wed, Feb 22, 2017 at 11:21:57PM +0100, Alberto Garcia wrote:
> On Wed, Feb 22, 2017 at 10:59:08PM +0100, Kurt Roeckx wrote:
> 
> > > I don't know, I think I would understand you better if I had a
> > > list of specific problems that make this software unsuitable for
> > > release.
> > 
> > I currently have a connection to my homeserver on 2 devices, and
> > pidgin isn't receive any messages, but riot is. I have this problem
> > every few days. And like I said, it's not clear where the problem
> > is. It looks I can actually send things when in that state, and
> > other people receive it, I just don't receive anything back.  And
> > people generally blame purple-matrix for that if I tell I'm using
> > that.
> 
> Ok, interesting.
> 
> > > > Like I said, if you think that you can support this version for
> > > > the next 3 years, I have no problem with it. But I wouldn't add
> > > > it to a stable release yet in it's current state.
> > > 
> > > I plan to keep using this plugin for the foreseeable time.
> > 
> > But do you think you'll still use this version, or will you upgrade
> > the version you're running when there is a new upstream version?
> 
> Well, I'll upgrade it of course, and if there's any critical fix I'll
> try to backport it.
> 
> > > Maybe I'm missing something, what is the scenario that you are
> > > worried about?
> > 
> > So some of my worries:
> > - It crashes for me a few times a week.
> > - There seem to be various issues that don't make it behave
> >   properly.
> > - Maybe next year some of those issues have been fixed in
> >   purple-matrix, it's recommended to use it for the desktop,
> >   but then people install the version from Debian stable and
> >   get a crappy version.
> 
> But how is that scenario better if there's no version at all in Debian
> stable?

That they try to find it in a different place, like backports.

An other thing I'm concerned about is that I don't see any
activity upstream.


Kurt

Bug#855407: docker.io: Dependency missmatch (docker.io 1.11.2~ds1-6 vs. containerd 0.2.3~git20161117.78.03e5862~ds1-1)

[Sebastian Wyngaard]

Package: docker.io
Version: 1.11.2~ds1-6
Followup-For: Bug #855407

Thanks for the workaround! I can start containers again.



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

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

Versions of packages docker.io depends on:
ii  adduser  3.115
ii  containerd   0.2.1~ds1-3
ii  init-system-helpers  1.47
ii  iptables 1.6.0+snapshot20161117-5
ii  libapparmor1 2.11.0-2
ii  libc62.24-9
ii  libdevmapper1.02.1   2:1.02.137-1
ii  libsqlite3-0 3.16.2-2
ii  libsystemd0  232-15
ii  runc 0.1.1+dfsg1-2

Versions of packages docker.io recommends:
ii  ca-certificates  20161130
ii  cgroupfs-mount   1.3
ii  git  1:2.11.0-2
ii  xz-utils 5.2.2-1.2

Versions of packages docker.io suggests:
pn  aufs-tools   
pn  btrfs-progs  
ii  debootstrap  1.0.88
pn  docker-doc   
pn  rinse
pn  zfs-fuse | zfsutils  

-- no debconf information

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 855883 gcc-6
Bug #855883 [src:pybind11] pybind11: FTBFS in stretch
Bug reassigned from package 'src:pybind11' to 'gcc-6'.
No longer marked as found in versions pybind11/2.0.1-1.
Ignoring request to alter fixed versions of bug #855883 to the same values 
previously set
> affects 855883 pybind11
Bug #855883 [gcc-6] pybind11: FTBFS in stretch
Added indication that 855883 affects pybind11
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
855883: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855883
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#855883: (no subject)

[Adrian Heine]

Control: reassign -1 gcc-6
Control: affects -1 pybind11

See #854692 [1].

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



signature.asc
Description: OpenPGP digital signature

Bug#855846: [Android-tools-devel] Bug#855846: repo: requires software outside of the distribution to function

[Jonas Smedegaard]

Quoting Hans-Christoph Steiner (2017-02-22 16:49:03)
> Its more vague than that.  repo clones a git repo for each source repo 
> that it manages, so it becomes something like the stuff in the .git/ 
> subdir for git repos.  That functionality comes entirely from what's 
> packaged in Debian.

If you say that the code packaged for Debian does _not_ download code, 
then I guess this bug can be transformed into a minor bug about long 
description being wrong (it should reflect the _package_ not upstream, 
if those differ).


 - Jonas

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

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


signature.asc
Description: signature

Bug#855541: purple-matrix: Not ready for release yet

[Alberto Garcia]

On Wed, Feb 22, 2017 at 10:59:08PM +0100, Kurt Roeckx wrote:

> > I don't know, I think I would understand you better if I had a
> > list of specific problems that make this software unsuitable for
> > release.
> 
> I currently have a connection to my homeserver on 2 devices, and
> pidgin isn't receive any messages, but riot is. I have this problem
> every few days. And like I said, it's not clear where the problem
> is. It looks I can actually send things when in that state, and
> other people receive it, I just don't receive anything back.  And
> people generally blame purple-matrix for that if I tell I'm using
> that.

Ok, interesting.

> > > Like I said, if you think that you can support this version for
> > > the next 3 years, I have no problem with it. But I wouldn't add
> > > it to a stable release yet in it's current state.
> > 
> > I plan to keep using this plugin for the foreseeable time.
> 
> But do you think you'll still use this version, or will you upgrade
> the version you're running when there is a new upstream version?

Well, I'll upgrade it of course, and if there's any critical fix I'll
try to backport it.

> > Maybe I'm missing something, what is the scenario that you are
> > worried about?
> 
> So some of my worries:
> - It crashes for me a few times a week.
> - There seem to be various issues that don't make it behave
>   properly.
> - Maybe next year some of those issues have been fixed in
>   purple-matrix, it's recommended to use it for the desktop,
>   but then people install the version from Debian stable and
>   get a crappy version.

But how is that scenario better if there's no version at all in Debian
stable?

> - I don't know if it's still going to be compatible next year.

As far as I'm aware the client-server protocol is stable, well
documented and doesn't just break from one version to the next.

https://matrix.org/docs/spec/

Berto

Bug#855830: marked as done (pytest-qt: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Wed, 22 Feb 2017 22:03:49 +
with message-id 
and subject line Bug#855830: fixed in pytest-qt 2.1.0-2
has caused the Debian Bug report #855830,
regarding pytest-qt: Incomplete debian/copyright?
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
855830: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855830
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pytest-qt
Version: 2.1.0-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Ghislain Antony Vaillant 

Hi,

I just ACCEPTed pytest-qt from NEW but noticed it was missing 
attribution in debian/copyright for at least scripts/link_pyqt.py.

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


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: pytest-qt
Source-Version: 2.1.0-2

We believe that the bug you reported is fixed in the latest version of
pytest-qt, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 855...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ghislain Antony Vaillant  (supplier of updated pytest-qt 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 22 Feb 2017 14:48:29 +
Source: pytest-qt
Binary: python3-pytestqt python-pytestqt-doc
Architecture: source
Version: 2.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Ghislain Antony Vaillant 
Description:
 python-pytestqt-doc - documentation for pytest-qt
 python3-pytestqt - pytest plugin for Qt application testing (Python 3)
Closes: 855830
Changes:
 pytest-qt (2.1.0-2) unstable; urgency=medium
 .
   * Add missing copyright information.
 Thanks to Chris Lamb for reporting (Closes: #855830)
   * Run autopkgtests for all supported Python versions
Checksums-Sha1:
 d31f98032aa544b598cd4e47a905b7483f3d53b3 2278 pytest-qt_2.1.0-2.dsc
 fd7bcd26b29339fa054ab9040e731888fe44aeec 3636 pytest-qt_2.1.0-2.debian.tar.xz
Checksums-Sha256:
 7c7b2f75a5868e816c0094e2413220c97e134f31f7a6c5de749bfaad639525f1 2278 
pytest-qt_2.1.0-2.dsc
 d8585f25063bee71f5fde5b69b4e75b59e064e8e0c7d913e8fcc2f8782e10406 3636 
pytest-qt_2.1.0-2.debian.tar.xz
Files:
 c158c935f955683e9578965830254942 2278 python optional pytest-qt_2.1.0-2.dsc
 0a10fa4fc895319ef2b98879a984f9b0 3636 python optional 
pytest-qt_2.1.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJYrgnZAAoJEPNPCXROn13Zi5sP/1esVvOH1dLSkrdwrAreqgtV
v7AbpRx1WzOqkFWso1p6ghEMDmnFlSzmcVqIjmM4oH6o8FHgn4tj83+EXekl1BMN
S38yIsV1hwm12Tx7EIdFoneHBNL/nvIN9kwPN0fbcknM480KJD1+/JzbsViAFbGO
XHhziTf/iugTwuNvx+iVQtDi6d/3plr8DwuztP+JSqc+Zdk60HtHj1bhkSokMa3a
eSylKsOVFYZefmJFXJVDy0JopT/OsIEsgXf/3dJXX50kdn26UulyF9aVCPT+2e6X
MjoJmCQORIdHeAFce3fDl+UPCs/m6gVGDKd6qsoHeEqX0e5IdymlfzNB4S38a0X/
yxZfu5sfR9cmJnBRjwPV7q5wBkyptTRcWErXt1pVSlwwXNr/OwCPQKrdGs47oAiK
N4KUoh/MwtEVhXiTHSrzgH/+ilyyiD7lY3njiFi/XFzH4s2BeqpAuoCbyDi0jAL/
z5Z6C3nmSTzK8XSYutXWrJmEVsb6aQf/aWX2uZEYVxyCK20meG2ttYrOYEDBf06y
lvwkSRO7+D8iaMRLCVHIFWj+G6O3thJpCajk3YvC6Fgtt+LS2T8cdx9DHW0vHgK4
VraBf/gYCo1yS+6b1/bVTMt0amYxYl2khH0/gvc+s2dy1l1wvYmjvuXGncCqEKjl
z0G1iu00xIWqsVMPx5dr
=hcrG
-END PGP SIGNATURE End Message ---

Bug#855541: purple-matrix: Not ready for release yet

[Kurt Roeckx]

On Wed, Feb 22, 2017 at 01:56:31PM +0100, Alberto Garcia wrote:
> On Mon, Feb 20, 2017 at 06:52:58PM +0100, Kurt Roeckx wrote:
> 
> > It's just that each time I mention I'm using this, people tell me
> > taht it's experimental, and probably a bug in purple-matrix. But
> > it's at least not always clear to me where the bugs are, and there
> > seem to be various problems with the homeserver (synapse) too.
> 
> I don't know, I think I would understand you better if I had a list of
> specific problems that make this software unsuitable for release.
> 
> I've been using it daily for months as my primary Matrix client on
> my desktop computer, and the only issues I found are occasional
> disconnects (and I'm not even sure that it's not a server problem).

I currently have a connection to my homeserver on 2 devices, and
pidgin isn't receive any messages, but riot is. I have this
problem every few days. And like I said, it's not clear where the
problem is. It looks I can actually send things when in that state,
and other people receive it, I just don't receive anything back.
And people generally blame purple-matrix for that if I tell I'm
using that.

Sometimes the connection really breaks, and then it reconnects and
works (or crashes).

> > Like I said, if you think that you can support this version for the
> > next 3 years, I have no problem with it. But I wouldn't add it to a
> > stable release yet in it's current state.
> 
> I plan to keep using this plugin for the foreseeable time.

But do you think you'll still use this version, or will you
upgrade the version you're running when there is a new upstream
version?

> If this goes to stretch then it will be a simple Matrix client with
> few dependencies and limited functionality, but otherwise stable
> enough for everyday use.
> 
> Maybe I'm missing something, what is the scenario that you are worried
> about?

So some of my worries:
- It crashes for me a few times a week.
- There seem to be various issues that don't make it behave
  properly.
- Maybe next year some of those issues have been fixed in
  purple-matrix, it's recommended to use it for the desktop,
  but then people install the version from Debian stable and
  get a crappy version.
- I don't know if it's still going to be compatible next year.


Kurt

Bug#855888: gnutls.pc requires libidn2.pc which does not exist

[Michael Biebl]

Package: libgnutls28-dev
Version: 3.5.9-1
Severity: serious

gnutls.pc from experimental contains
Requires.private: nettle, hogweed, libtasn1, libidn2, p11-kit-1, zlib

The package depends on libidn11-dev which ships libidn.pc though.

libidn2.pc is not available in the archive afaics.
I suppose you want libidn2-0-dev, but that package doesn't ship a libidn2.pc
(maybe a bug in that package).

As a result, building against libgnutls28-dev results in a FTBFS, like e.g. in
https://buildd.debian.org/status/fetch.php?pkg=rsyslog=ppc64=8.25.0-1=1487703642=0

Regards,
Michael


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

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

Versions of packages libgnutls28-dev depends on:
ii  libc6-dev [libc-dev]  2.24-9
ii  libgnutls-dane0   3.5.8-3
ii  libgnutls-openssl27   3.5.8-3
ii  libgnutls30   3.5.8-3
ii  libgnutlsxx28 3.5.8-3
ii  libidn11-dev  1.33-1
ii  libp11-kit-dev0.23.3-5
ii  libtasn1-6-dev4.10-1
ii  nettle-dev3.3-1
ii  zlib1g-dev1:1.2.8.dfsg-5

libgnutls28-dev recommends no packages.

Versions of packages libgnutls28-dev suggests:
pn  gnutls-bin  
pn  gnutls-doc  

-- no debconf information

Bug#855877: marked as done (python3-django-celery: management commands broken with Django 1.10)

[Debian Bug Tracking System]

Your message dated Wed, 22 Feb 2017 21:33:39 +
with message-id 
and subject line Bug#855877: fixed in django-celery 3.1.17-4
has caused the Debian Bug report #855877,
regarding python3-django-celery: management commands broken with Django 1.10
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
855877: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855877
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-django-celery
Version: 3.1.17-3.1
Severity: grave
Forwarded: https://github.com/celery/django-celery/pull/458
Justification: renders package unusable

$ ./manage.py celery worker
Traceback (most recent call last):
  File "./manage.py", line 22, in 
execute_from_command_line(sys.argv)
  File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
line 367, in execute_from_command_line
utility.execute()
  File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
line 359, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
line 208, in fetch_command
klass = load_command_class(app_name, subcommand)
  File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
line 40, in load_command_class
module = import_module('%s.management.commands.%s' % (app_name, name))
  File "/usr/lib/python3.5/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
  File "", line 986, in _gcd_import
  File "", line 969, in _find_and_load
  File "", line 958, in _find_and_load_unlocked
  File "", line 673, in _load_unlocked
  File "", line 673, in exec_module
  File "", line 222, in _call_with_frames_removed
  File "/usr/lib/python3/dist-packages/djcelery/management/commands/celery.py", 
line 6, in 
from djcelery.management.base import CeleryCommand
  File "/usr/lib/python3/dist-packages/djcelery/management/base.py", line 59, 
in 
class CeleryCommand(BaseCommand):
  File "/usr/lib/python3/dist-packages/djcelery/management/base.py", line 60, 
in CeleryCommand
options = BaseCommand.option_list
AttributeError: type object 'BaseCommand' has no attribute 'option_list'

Fix:
https://github.com/celery/django-celery/pull/458
https://patch-diff.githubusercontent.com/raw/celery/django-celery/pull/458.patch

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

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

Versions of packages python3-django-celery depends on:
ii  python3-anyjson0.3.3-1
ii  python3-celery 3.1.23-5
ii  python3-django 1:1.10.5-1
ii  python3-pkg-resources  33.1.1-1
ii  python3-tz 2016.7-0.2
pn  python3:any

python3-django-celery recommends no packages.

python3-django-celery suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: django-celery
Source-Version: 3.1.17-4

We believe that the bug you reported is fixed in the latest version of
django-celery, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 855...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Brian May  (supplier of updated django-celery package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 23 Feb 2017 08:10:49 +1100
Source: django-celery
Binary: python-django-celery python3-django-celery python-django-celery-doc
Architecture: source all
Version: 3.1.17-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Brian May 
Description:
 python-django-celery - Celery integration for Django
 

Bug#855881: freecontact: FTBFS in stretch (devlibs error)

[Niels Thykier]

On Wed, 22 Feb 2017 21:05:23 + Santiago Vila  wrote:
> Package: src:freecontact
> Version: 1.0.21-4
> Severity: serious
> 
> Dear maintainer:
> 
> I tried to build this package in stretch with "dpkg-buildpackage -A"
> but it failed:
> 
> 
> [...]

Seems related to the gcc-5 removal which only happened in testing so far.

Thanks,
~Niels

Bug#855883: pybind11: FTBFS in stretch

[Santiago Vila]

Package: src:pybind11
Version: 2.0.1-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3,sphinxdoc --buildsystem=cmake
   dh_testdir -i -O--buildsystem=cmake
   dh_update_autotools_config -i -O--buildsystem=cmake
   dh_autoreconf -i -O--buildsystem=cmake
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- -DPYBIND11_TEST=ON
cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DPYBIND11_TEST=ON
-- The C compiler identification is GNU 6.3.0
-- The CXX compiler identification is GNU 6.3.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info

[... snipped ...]

9637: .def(py::init<>())
9637: .def("f", ::f);
9637: 
9637: m.def("call_f", call_f);
9637: 
9637: 
9637: 
9637: struct A2 {
9637: virtual ~A2() {}
9637: virtual void f() { py::print("A2.f()"); }
9637: };
9637: 
9637: struct PyA2 : A2 {
9637: PyA2() { py::print("PyA2.PyA2()"); }
9637: ~PyA2() { py::print("PyA2.~PyA2()"); }
9637: void f() override {
9637: py::print("PyA2.f()");
9637: { pybind11::gil_scoped_acquire gil; pybind11::function 
overload = pybind11::get_overload(static_cast(this), "f"); if 
(overload) { auto o = overload(); if 
(pybind11::detail::cast_is_temporary_value_reference::value) { static 
pybind11::detail::overload_caster_t caster; return 
pybind11::detail::cast_ref(std::move(o), caster); } else return 
pybind11::detail::cast_safe(std::move(o)); } } return A2::f();
9637: }
9637: };
9637: 
9637: py::class_(m, "A2")
9637: .def(py::init_alias<>())
9637: .def("f", ::f);
9637: 
9637: m.def("call_f", [](A2 *a2) { a2->f(); });
9637: 
9637: });
=== END GCC DUMP ===
tests/CMakeFiles/pybind11_tests.dir/build.make:89: recipe for target 
'tests/CMakeFiles/pybind11_tests.dir/test_alias_initialization.cpp.o' failed
make[4]: *** 
[tests/CMakeFiles/pybind11_tests.dir/test_alias_initialization.cpp.o] Error 1
make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
CMakeFiles/Makefile2:160: recipe for target 
'tests/CMakeFiles/pybind11_tests.dir/all' failed
make[3]: *** [tests/CMakeFiles/pybind11_tests.dir/all] Error 2
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
Makefile:130: recipe for target 'all' failed
make[2]: *** [all] Error 2
make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
dh_auto_build: make -j1 returned exit code 2
debian/rules:27: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
debian/rules:15: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


This is just how the build ends, not necessarily the relevant part.

I've put several build logs here:

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

The bug should be reproducible with sbuild on a single CPU virtual machine.
I only tried twice and it failed twice, but it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pybind11.html

so hope this may be reproduced easily.

Thanks.

Bug#855881: freecontact: FTBFS in stretch (devlibs error)

[Santiago Vila]

Package: src:freecontact
Version: 1.0.21-4
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --parallel --with bash-completion --with autoreconf
   dh_testdir -i -O--parallel
   dh_update_autotools_config -i -O--parallel
   dh_autoreconf -i -O--parallel
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:29: installing './compile'

[... snipped ...]

  /bin/bash ../libtool   --mode=install /usr/bin/install -c freecontact 
'/<>/debian/tmp/usr/bin'
libtool: warning: '../lib/libfreecontact.la' has not been installed in 
'/usr/lib/x86_64-linux-gnu'
libtool: install: /usr/bin/install -c .libs/freecontact 
/<>/debian/tmp/usr/bin/freecontact
 /bin/mkdir -p '/<>/debian/tmp/usr/share/doc/freecontact/examples'
 /usr/bin/install -c -m 644 demo_1000.aln demo_1000.psicov.50 
PF00071_v25_999.fa PF00071_v25_999.xml PF00071_v25_999.evfold.50 
PF00071_v25_999.evfold.50.xml 
'/<>/debian/tmp/usr/share/doc/freecontact/examples'
 /bin/mkdir -p '/<>/debian/tmp/usr/share/freecontact'
 /usr/bin/install -c -m 644 BioXSD-1.1.xsd freecontact_input.xsd 
freecontact_output.xsd '/<>/debian/tmp/usr/share/freecontact'
 /bin/mkdir -p '/<>/debian/tmp/usr/share/freecontact'
 /usr/bin/install -c a2m2aln '/<>/debian/tmp/usr/share/freecontact'
 /bin/mkdir -p '/<>/debian/tmp/usr/share/man/man1'
 /usr/bin/install -c -m 644 freecontact.1 
'/<>/debian/tmp/usr/share/man/man1'
make[3]: Leaving directory '/<>/src'
make[2]: Leaving directory '/<>/src'
make[2]: Entering directory '/<>'
make[3]: Entering directory '/<>'
make[3]: Nothing to be done for 'install-exec-am'.
make[3]: Nothing to be done for 'install-data-am'.
make[3]: Leaving directory '/<>'
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
dh_install
d-shlibmove --commit \
--multiarch \
--exclude-la \
--devunversioned \
--override s/libblas3-dev/libblas-dev/ \
--v5 \
--override s/libgfortran3-dev/libgfortran-5-dev/ \
--override s/libquadmath0-dev/libgcc-5-dev/ \
--override s/liblapack3-dev/liblapack-dev/ \
--movedev debian/tmp/usr/include/* usr/include \
debian/tmp/usr/lib/*/*.so
Library package automatic movement utility
 --> libblas-dev package exists.
devlibs error: There is no package matching [libgcc-5-dev] and noone provides 
it, please report bug to d-shlibs maintainer
devlibs error: There is no package matching [libgfortran-5-dev] and noone 
provides it, please report bug to d-shlibs maintainer
 --> liblapack-dev package exists.
debian/rules:29: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 1
make[1]: Leaving directory '/<>'
debian/rules:11: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


This may or may not be a bug in d-shlibs, but I'm not sure, so I'm
reporting this initially against freecontact, the failing package,
and I'm including Jonas in X-Debbugs-Cc.

The failure also happens here in testing at least:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/freecontact.html

so I assume it should be easy to reproduce on current stretch.

If this is really a bug in one of the build-depends (for example,
d-shlibs), please use reassign and then "affects src:freecontact",
so that this is still visible in the page for this package.

Thanks.

Processed: tagging 816063

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 816063 - unreproducible
Bug #816063 [emacs24] emacs24: TLS certificate validation is silently broken
Removed tag(s) unreproducible.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
816063: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816063
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#851841: xonsh: jobs and backgrounding broken

[Gordon Ball]

As noted above, the bug severity was upgraded too late to stop 0.5.2
migrating.

There have been a series of releases since, and while this bug was
mostly fixed in 0.5.3 it appears there were still some edge cases.

The code is still fairly fast moving, and in the end I don't think it's
a good candidate for a stable release at this time; I'll aim to provide
a version in stretch-backports in due course.

Bug#766397: Bug#766395: emacs/gnus: Uses s_client to for SSL.

[Antoine Beaupre]

On Sun, Feb 21, 2016 at 01:47:45PM +1100, Lars Ingebrigtsen wrote:
> Kurt Roeckx  writes:
> 
> > From what I understand, it is (or was) possible to configure
> > things in such a way that it uses s_client to set up SSL, even
> > when it's configured to use gnutls.  You should never use s_client
> > for that.  s_client is a debug tool.  It does create an SSL
> > connection for you, but in an insecure way.
> 
> Emacs has built-in TLS support these days, so s_client is only used if
> the user (for some weird reason or other) has built or installed a
> version of Emacs without TLS support.
> 
> I think that should probably be removed, because it's less secure than
> users would expect.

This is now a release-blocking bug, but hasn't seen any activity in the
last year or so. It would be good to see this finally fixed!

Obviously, one should never use openssl s_client for stuff like this...
I should also note that even though Emacs 24 supports TLS natively now,
its handling of X509 certificate is really problematic, as documented in
#816063. I would hardly consider it complete.

Emacs 25 doesn't suffer from those issues, but may still allow
s_client...

A.

-- 
Il est sage de nous réconcilier avec notre adolescence ; haїr, mépriser,
nier ou simplement oublier l’adolescent que nous fûmes est en soi une
attitude adolescente.
- Daniel Pennac, Comme un roman


signature.asc
Description: PGP signature

Processed: Re: Bug#855455: revelation: ImportError: No module named randpool (python-crypto)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #855455 [revelation] revelation: ImportError: No module named randpool 
(python-crypto)
Severity set to 'important' from 'grave'

-- 
855455: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855455
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#816063: emacs24: TLS certificate validation is silently broken

[Antoine Beaupre]

tags -1 -unreproducible

I can reproduce issues with certification verification in Emacs 24.5+1-8
in Debian Stretch. As documented here:

https://glyph.twistedmatrix.com/2015/11/editor-malware.html

The following script will yield an error:

(let ((bad-hosts
   (cl-loop for bad
 in `("https://wrong.host.badssl.com/;
  "https://self-signed.badssl.com/;)
 if (condition-case e
(url-retrieve
 bad (lambda (retrieved) t))
  (error nil))
 collect bad)))
  (if bad-hosts
  (error (format "tls misconfigured; retrieved %s ok"
 bad-hosts))
(url-retrieve "https://badssl.com;
  (lambda (retrieved) t

The error is:

Debugger entered--Lisp error: (error "tls misconfigured; retrieved 
(https://wrong.host.badssl.com/ https://self-signed.badssl.com/) ok")
  signal(error ("tls misconfigured; retrieved (https://wrong.host.badssl.com/ 
https://self-signed.badssl.com/) ok"))
  error("tls misconfigured; retrieved (https://wrong.host.badssl.com/ 
https://self-signed.badssl.com/) ok")
  (if bad-hosts (error (format "tls misconfigured; retrieved %s ok" bad-hosts)) 
(url-retrieve "https://badssl.com; (function (lambda (retrieved) t
  (let ((bad-hosts (let* ((--cl-var-- (quote ("https://wrong.host.badssl.com/; 
"https://self-signed.badssl.com/;))) (bad nil) (--cl-var-- nil)) (while (consp 
--cl-var--) (setq bad (car --cl-var--)) (if (condition-case e (url-retrieve bad 
...) (error nil)) (progn (setq --cl-var-- ...))) (setq --cl-var-- (cdr 
--cl-var--))) (nreverse --cl-var-- (if bad-hosts (error (format "tls 
misconfigured; retrieved %s ok" bad-hosts)) (url-retrieve "https://badssl.com; 
(function (lambda (retrieved) t)
  eval-region(192 615 t #[257 "\300\242b\210\301\207" [(615) (let ((bad-hosts 
(let* ((--cl-var-- ...) (bad nil) (--cl-var-- nil)) (while (consp --cl-var--) 
(setq bad ...) (if ... ...) (setq --cl-var-- ...)) (nreverse --cl-var-- (if 
bad-hosts (error (format "tls misconfigured; retrieved %s ok" bad-hosts)) 
(url-retrieve "https://badssl.com; (function (lambda (retrieved) t)] 2 
"\n\n(fn IGNORE)"])  ; Reading at buffer position 615
  eval-defun-2()
  eval-defun(nil)
  call-interactively(eval-defun nil nil)
  command-execute(eval-defun)

In other words, by default, with Emacs 24.5 in Debian stretch right now,
visiting self-signed or hijacked certificates will yield no warning at
all.

Therefore, I currently have the following snippet in my .emacs to fix
X509 certification validation:

;; make sure we check against trusted X509 roots
;; requires python-certifi
;; see https://glyph.twistedmatrix.com/2015/11/editor-malware.html
(when (< emacs-major-version 25)
  (let ((trustfile
 (replace-regexp-in-string
  "" "/"
  (replace-regexp-in-string
   "\n" ""
   (shell-command-to-string "python -m certifi")
(setq tls-program
  (list
   (format "gnutls-cli%s --x509cafile %s -p %%p %%h"
   (if (eq window-system 'w32) ".exe" "") trustfile)))
(setq gnutls-verify-error t)
(setq gnutls-trustfiles (list trustfile))
(setq gnutls-log-level 2)
(setq tls-checktrust t)
;; disable builtin gnutls support completely, as it fails on checks:
;; http://emacs.stackexchange.com/a/18610
(defun user/disable-gnutls (f  args) nil)
(advice-add 'gnutls-available-p :around #'user/disable-gnutls)))

Emacs 25 doesn't have this problem: certificate validation works fine
there. Or, to be more accurate, it yields a warning like this:

Certificate information
Issued by:  *.badssl.com
Issued to:  BadSSL 
Hostname:   *.badssl.com
Public key: RSA, signature: RSA-SHA256
Protocol:   TLS1.2, key: ECDHE-RSA, cipher: AES-128-GCM, mac: AEAD
Security level: Medium
Valid:  From 2016-08-08 to 2018-08-08
   

The TLS connection to self-signed.badssl.com:443 is insecure for the
following reasons:
 
certificate signer was not found (self-signed)
the certificate was signed by an unknown and therefore untrusted authority
certificate could not be verified
 
Continue connecting? (No, Session-only, Always)
  
I am not sure what changed between Emacs 24 and 25, but it seems to me
Emacs 24 should absolutely be fixed before Stretch is released, or just
be removed from stretch.

A.


signature.asc
Description: PGP signature

Bug#855455: revelation: ImportError: No module named randpool (python-crypto)

[GCS]

Control: severity -1 important

Hi Mathieu,

On Sat, Feb 18, 2017 at 3:46 PM, Mathieu Basille
 wrote:
> Package: revelation
> Version: 0.4.14-3
> Severity: grave
> Justification: renders package unusable
[...]
> Using Debian Stretch (testing), I am now unable to run revelation. There must 
> have been an update in the meanwhile, since I used to be able to use it just 
> a few days ago.
 As unreproducible and asked for more information, but none given yet,
I lower the severity.
Please give me at least pointers how may I reproduce this issue.

Thanks,
Laszlo/GCS

Processed: reassign 850229 to src:dune-common, severity of 850229 is minor, tagging 850229

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 850229 src:dune-common
Bug #850229 [dune-grid] openmpi-bin: default for oversubscription changed
Bug #850559 [dune-grid] openmpi-bin: default for oversubscription changed
Bug reassigned from package 'dune-grid' to 'src:dune-common'.
Bug reassigned from package 'dune-grid' to 'src:dune-common'.
Ignoring request to alter found versions of bug #850229 to the same values 
previously set
Ignoring request to alter found versions of bug #850559 to the same values 
previously set
Ignoring request to alter fixed versions of bug #850229 to the same values 
previously set
Ignoring request to alter fixed versions of bug #850559 to the same values 
previously set
> severity 850229 minor
Bug #850229 [src:dune-common] openmpi-bin: default for oversubscription changed
Bug #850559 [src:dune-common] openmpi-bin: default for oversubscription changed
Severity set to 'minor' from 'serious'
Severity set to 'minor' from 'serious'
> tags 850229 + pending
Bug #850229 [src:dune-common] openmpi-bin: default for oversubscription changed
Bug #850559 [src:dune-common] openmpi-bin: default for oversubscription changed
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
850229: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850229
850559: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850559
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 850229 dune-grid

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 850229 dune-grid
Bug #850229 [openmpi-bin] openmpi-bin: default for oversubscription changed
Bug #850559 [openmpi-bin] openmpi-bin: default for oversubscription changed
Bug reassigned from package 'openmpi-bin' to 'dune-grid'.
Bug reassigned from package 'openmpi-bin' to 'dune-grid'.
No longer marked as found in versions openmpi/2.0.2~git.20161225-8.
No longer marked as found in versions openmpi/2.0.2~git.20161225-8.
Ignoring request to alter fixed versions of bug #850229 to the same values 
previously set
Ignoring request to alter fixed versions of bug #850559 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
850229: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850229
850559: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850559
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#851841: xonsh: jobs and backgrounding broken

[Alexander Sosedkin]

On Thu, 19 Jan 2017 22:14:25 +0100 Gordon Ball 
wrote:
> I have upgraded the bug to severity:serious to prevent migration, so
> stretch will get 0.4.7

It looks like stretch currently lacks xonsh at all, be it 0.4.7,
broken 0.5.2 or recent 0.5.6. Will any xonsh get into stretch?

Processed: tagging 704303

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 704303 + stretch-ignore
Bug #704303 [firefox,firefox-esr] iceweasel: MPL license text is missing
Added tag(s) stretch-ignore.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
704303: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704303
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#855877: python3-django-celery: management commands broken with Django 1.10

[Antonio Terceiro]

Package: python3-django-celery
Version: 3.1.17-3.1
Severity: grave
Forwarded: https://github.com/celery/django-celery/pull/458
Justification: renders package unusable

$ ./manage.py celery worker
Traceback (most recent call last):
  File "./manage.py", line 22, in 
execute_from_command_line(sys.argv)
  File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
line 367, in execute_from_command_line
utility.execute()
  File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
line 359, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
line 208, in fetch_command
klass = load_command_class(app_name, subcommand)
  File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
line 40, in load_command_class
module = import_module('%s.management.commands.%s' % (app_name, name))
  File "/usr/lib/python3.5/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
  File "", line 986, in _gcd_import
  File "", line 969, in _find_and_load
  File "", line 958, in _find_and_load_unlocked
  File "", line 673, in _load_unlocked
  File "", line 673, in exec_module
  File "", line 222, in _call_with_frames_removed
  File "/usr/lib/python3/dist-packages/djcelery/management/commands/celery.py", 
line 6, in 
from djcelery.management.base import CeleryCommand
  File "/usr/lib/python3/dist-packages/djcelery/management/base.py", line 59, 
in 
class CeleryCommand(BaseCommand):
  File "/usr/lib/python3/dist-packages/djcelery/management/base.py", line 60, 
in CeleryCommand
options = BaseCommand.option_list
AttributeError: type object 'BaseCommand' has no attribute 'option_list'

Fix:
https://github.com/celery/django-celery/pull/458
https://patch-diff.githubusercontent.com/raw/celery/django-celery/pull/458.patch

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

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

Versions of packages python3-django-celery depends on:
ii  python3-anyjson0.3.3-1
ii  python3-celery 3.1.23-5
ii  python3-django 1:1.10.5-1
ii  python3-pkg-resources  33.1.1-1
ii  python3-tz 2016.7-0.2
pn  python3:any

python3-django-celery recommends no packages.

python3-django-celery suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Bug#855876: golang-etcd-server-dev: ships md5sums but no files: /usr/share/gocode/src/github.com/coreos/etcd/integration/*

[Andreas Beckmann]

Package: golang-etcd-server-dev
Version: 3.1.1+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed debsums reports some missing
files in your package.
Looks like these are present in the md5sums file, but not in the
package itself.

>From the attached log (scroll to the bottom...):

2m18.1s ERROR: FAIL: debsums reports modifications inside the chroot:
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2100901396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2101001396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2101101396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2101201396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2101301396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2101401396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2102901396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2103001396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2103101396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2103201396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2103301396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2103401396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2105101396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2105201396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2105301396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2105401396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2105501396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2105601396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2142501396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2142601396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2142701396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2142801396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2142901396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2143001396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2143701396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2143801396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2143901396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2144001396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2144101396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/127.0.0.1:2144201396 
(from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/localhost:1482183007541472900
 (from golang-etcd-server-dev package)
  debsums: missing file 
/usr/share/gocode/src/github.com/coreos/etcd/integration/localhost:14821830075414729000
 (from golang-etcd-server-dev package)
  debsums: 

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 850984 1:45.7.1-1
Bug #850984 {Done: Carsten Schoenert } [src:icedove] 
icedove: FTBFS: configure: error: cannot determine icu version number from 
uvernum.h header file
Marked as fixed in versions icedove/1:45.7.1-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
850984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850984
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 855344 icedove/1:45.6.0-2
Bug #855344 [thunderbird] thunderbird: retains mails from removed IMAP accounts
Marked as found in versions icedove/1:45.6.0-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
855344: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855344
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: retitle 855705 to munin: CVE-2017-6188: munin-cgi-graph local file write vulnerability

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 855705 munin: CVE-2017-6188: munin-cgi-graph local file write 
> vulnerability
Bug #855705 [munin] munin-cgi-graph local file write vulnerability
Changed Bug title to 'munin: CVE-2017-6188: munin-cgi-graph local file write 
vulnerability' from 'munin-cgi-graph local file write vulnerability'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
855705: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855705
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: block 855859 with 855872

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 855859 with 855872
Bug #855859 [xdg-utils] xdg-utils: xdg-email doesn't work with Debian's 
Thunderbird wrapper script
855859 was blocked by: 855334
855859 was not blocking any bugs.
Added blocking bug(s) of 855859: 855872
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
855859: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855859
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: block 855449 with 855872

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 855449 with 855872
Bug #855449 [nautilus-sendto] nautilus-sendto: Thunderbird debranding breaks 
the program
855449 was blocked by: 855334
855449 was not blocking any bugs.
Added blocking bug(s) of 855449: 855872
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
855449: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855449
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#855872: command line arguments are not properly handled (breaking existing applications)

[Michael Biebl]

Package: thunderbird
Version: 1:45.7.1-1
Severity: serious

Hi,

the new thunderbird wrapper script breaks the command line parsing
E.g. "thunderbird --ProfileManager" no longer works, instead you get an
error:

$ thunderbird --ProfileManager
Illegal option --

Usage: thunderbird [-h|-vg|-- @args]
The options have to be used in the correct order!
...

This is related to #855334, but I don't think, existing tools should be
updated to use "--", instead the wrapper script needs to be fixed to be
backwards compatible.

Marking this as RC, as it breaks existing applications and scripts.

Regards,
Michael

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

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

Versions of packages thunderbird depends on:
ii  debianutils   4.8.1
ii  fontconfig2.11.0-6.7
ii  libasound21.1.3-5
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-9
ii  libcairo2 1.14.8-1
ii  libdbus-1-3   1.10.16-1
ii  libdbus-glib-1-2  0.108-2
ii  libevent-2.0-52.0.21-stable-3
ii  libffi6   3.2.1-6
ii  libfontconfig12.11.0-6.7
ii  libfreetype6  2.6.3-3+b1
ii  libgcc1   1:6.3.0-8
ii  libgdk-pixbuf2.0-02.36.5-2
ii  libglib2.0-0  2.50.3-1
ii  libgtk2.0-0   2.24.31-2
ii  libhunspell-1.4-0 1.4.1-2+b1
ii  libicu57  57.1-5
ii  libnspr4  2:4.12-6
ii  libnss3   2:3.26.2-1
ii  libpango-1.0-01.40.3-3
ii  libpangocairo-1.0-0   1.40.3-3
ii  libpangoft2-1.0-0 1.40.3-3
ii  libpixman-1-0 0.34.0-1
ii  libsqlite3-0  3.16.2-2
ii  libstartup-notification0  0.12-4
ii  libstdc++66.3.0-8
ii  libvpx4   1.6.1-2
ii  libx11-6  2:1.6.4-3
ii  libxcomposite11:0.4.4-2
ii  libxdamage1   1:1.1.4-2+b1
ii  libxext6  2:1.3.3-1
ii  libxfixes31:5.0.3-1
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1
ii  psmisc22.21-2.1+b1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages thunderbird recommends:
ii  hunspell-de-de [hunspell-dictionary]  20161207-1
ii  hunspell-en-us [hunspell-dictionary]  20070829-7
ii  lightning 1:45.7.1-1

Versions of packages thunderbird suggests:
pn  apparmor  
ii  fonts-lyx 2.2.2-1
ii  libgssapi-krb5-2  1.15-1

-- no debconf information

Bug#855588: Acknowledgement (memory leak could lead to Denial Of Service)

[Antoine Beaupré]

Control: block -1 with 855595

I have filed an unblock request in #855595 to make sure an eventual
update to sid would be accepted by the release managers.

A.
-- 
Le pouvoir n'est pas à conquérir, il est à détruire
- Jean-François Brient, de la servitude moderne

Processed: Re: Bug#855588: Acknowledgement (memory leak could lead to Denial Of Service)

[Debian Bug Tracking System]

Processing control commands:

> block -1 with 855595
Bug #855588 [atheme-services] memory leak could lead to Denial Of Service
855588 was not blocked by any bugs.
855588 was not blocking any bugs.
Added blocking bug(s) of 855588: 855595

-- 
855588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855588
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#854985: marked as done (kodi.service spamming the logs due to xinit being missing)

[Debian Bug Tracking System]

Your message dated Wed, 22 Feb 2017 16:49:31 +
with message-id 
and subject line Bug#854985: fixed in kodi 2:17.0+dfsg1-3
has caused the Debian Bug report #854985,
regarding kodi.service spamming the logs due to xinit being missing
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
854985: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854985
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kodi
Version: 2:17.0+dfsg1-2
Severity: normal

Dear Maintainer,

Since the latest round of updates, kodi.service spams syslog with:

Feb 12 22:14:35 zephyr systemd[1]: kodi.service: Service hold-off time over, 
scheduling restart.
Feb 12 22:14:35 zephyr systemd[1]: Stopped Kodi Open Source Home Theatre.
Feb 12 22:14:35 zephyr systemd[1]: Started Kodi Open Source Home Theatre.
Feb 12 22:14:35 zephyr systemd[17588]: kodi.service: Failed at step USER 
spawning /usr/bin/xinit: No such process
Feb 12 22:14:35 zephyr systemd[1]: kodi.service: Main process exited, 
code=exited, status=217/USER
Feb 12 22:14:35 zephyr systemd[1]: kodi.service: Unit entered failed state.
Feb 12 22:14:35 zephyr systemd[1]: kodi.service: Failed with result 'exit-code'.

If Kodi really needs xinit, then the package should depend on it. xinit
is rather old-fashioned, and is no longer generally useful if one runs
one of the "big" desktop environments, so nothing should assume it just
exists.

Actually, I don't think this service should be automatically enabled at
all. I do not want to run kodi in stand-alone mode.

Gabor

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

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

Versions of packages kodi depends on:
ii  init-system-helpers  1.47
ii  kodi-bin 2:17.0+dfsg1-2
ii  kodi-data2:17.0+dfsg1-2

Versions of packages kodi recommends:
ii  kodi-visualization-spectrum  1.1.1-1

kodi suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: kodi
Source-Version: 2:17.0+dfsg1-3

We believe that the bug you reported is fixed in the latest version of
kodi, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 854...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Balint Reczey  (supplier of updated kodi package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 22 Feb 2017 01:28:43 +0100
Source: kodi
Binary: kodi kodi-data kodi-bin kodi-eventclients-common kodi-eventclients-dev 
kodi-eventclients-wiiremote kodi-eventclients-ps3 kodi-eventclients-kodi-send 
kodi-addons-dev xbmc xbmc-bin xbmc-eventclients-common xbmc-eventclients-dev 
xbmc-eventclients-wiiremote xbmc-eventclients-ps3 xbmc-eventclients-xbmc-send 
xbmc-addons-dev
Architecture: source
Version: 2:17.0+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Balint Reczey 
Description:
 kodi   - Open Source Home Theatre (executable binaries)
 kodi-addons-dev - Open Source Home Theatre (Addons Dev package)
 kodi-bin   - Open Source Home Theatre (architecture-dependent files)
 kodi-data  - Open Source Home Theatre (arch-independent data package)
 kodi-eventclients-common - Open Source Home Theatre (Event Client Common 
package)
 kodi-eventclients-dev - Open Source Home Theatre (Event Client Dev package)
 kodi-eventclients-kodi-send - Open Source Home Theatre (Event Client Kodi-SEND 
package)
 kodi-eventclients-ps3 - Open Source Home Theatre (Event Client PS3 package)
 kodi-eventclients-wiiremote - Open Source Home Theatre (Event Client WII 
Remote support package
 xbmc   - transitional dummy package
 xbmc-addons-dev - transitional dummy package
 xbmc-bin   - transitional dummy package
 

Bug#854288: apt-dpkg-ref FTBFS: build dependency clisp is not in stretch

[Balint Reczey]

Hi,

On Sun, 05 Feb 2017 21:01:29 +0200 Adrian Bunk  wrote:
> Source: apt-dpkg-ref
> Version: 5.3.1+nmu1
> Severity: serious
> Tags: stretch sid
> 
> apt-dpkg-ref build-depends on clisp which is not in stretch.
> 
> (I also wonder whether we really need an own package
>  for a 3 page document.)

I have uploaded an NMU to DELAYED/2 with the  attached patch.

Cheers,
Balint
diff -Nru apt-dpkg-ref-5.3.1+nmu1/debian/changelog apt-dpkg-ref-5.3.1+nmu2/debian/changelog
--- apt-dpkg-ref-5.3.1+nmu1/debian/changelog	2015-06-13 15:03:28.0 +0200
+++ apt-dpkg-ref-5.3.1+nmu2/debian/changelog	2017-02-22 17:24:34.0 +0100
@@ -1,3 +1,10 @@
+apt-dpkg-ref (5.3.1+nmu2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build-depend on and use sbcl instead of clisp (Closes: #854288)
+
+ -- Balint Reczey   Wed, 22 Feb 2017 17:23:38 +0100
+
 apt-dpkg-ref (5.3.1+nmu1) unstable; urgency=low
 
   [ Andreas Moog ]
diff -Nru apt-dpkg-ref-5.3.1+nmu1/debian/control apt-dpkg-ref-5.3.1+nmu2/debian/control
--- apt-dpkg-ref-5.3.1+nmu1/debian/control	2015-06-13 15:00:32.0 +0200
+++ apt-dpkg-ref-5.3.1+nmu2/debian/control	2017-02-22 17:22:11.0 +0100
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Vanessa Gutiérrez 
 Build-Depends: debhelper (>= 7.0)
-Build-Depends-Indep: clisp | cmucl, texlive-base, texlive-latex-base, 
+Build-Depends-Indep: sbcl, texlive-base, texlive-latex-base, 
  texlive-latex-recommended, texlive-fonts-recommended
 Standards-Version: 3.9.2.0
 
diff -Nru apt-dpkg-ref-5.3.1+nmu1/make-docs apt-dpkg-ref-5.3.1+nmu2/make-docs
--- apt-dpkg-ref-5.3.1+nmu1/make-docs	2011-04-13 04:11:20.0 +0200
+++ apt-dpkg-ref-5.3.1+nmu2/make-docs	2017-02-22 17:21:33.0 +0100
@@ -1,10 +1,10 @@
 #!/bin/sh
 
-CLISP_BIN=$(which clisp)
+CLISP_BIN=$(which sbcl)
 LISP_BIN=$(which cmucl)
 
 if [ -n "$CLISP_BIN" ]; then
-	$CLISP_BIN apt-dpkg-ref.lisp
+	$CLISP_BIN < apt-dpkg-ref.lisp
 elif [ -n "$LISP_BIN" ]; then
 	$LISP_BIN -load apt-dpkg-ref.lisp
 else

Bug#855846: [Android-tools-devel] Bug#855846: repo: requires software outside of the distribution to function

[Hans-Christoph Steiner]

Its more vague than that.  repo clones a git repo for each source repo
that it manages, so it becomes something like the stuff in the .git/
subdir for git repos.  That functionality comes entirely from what's
packaged in Debian.

Bug#852645: dafny: FTBFS

[Benjamin Barenblat]

Thanks for looking into this.  You’re right – it looks like Dafny’s
having some trouble linking against Boogie.  The Dafny build process
statically links Boogie into Dafny; that’s why

cp -a /usr/lib/boogie/* Binaries
mkdir -p Source/Dafny/bin/Checked
cp -a /usr/lib/boogie/* Source/Dafny/bin/Checked

appears before the `xbuild` command.  However, Boogie builds fine and
is listed as a `Build-Depends-Indep` of Dafny, so I’m not entirely
sure what’s going on.

If you’d like to experiment with this, you can grab the relevant source from

https://benjamin.barenblat.name/git/debian-boogie.git
https://benjamin.barenblat.name/git/debian-dafny.git

Otherwise, I’ll try to have a look this weekend.

Bug#848729: It is grave

[Ondřej Surý]

Hi Nis,

indeed, the attached patch fixes sending unblock emails (where there's
at least always my name in the debdiffs and changelogs).

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

On Tue, Feb 14, 2017, at 22:26, Nis Martensen wrote:
> Hi Ondřej,
> 
> Ondřej Surý wrote:
> > As this bug is preventing me from filling any bugs at all and it fails
> > only after I press "Y", so the content of the lengthy unblock bug is
> > gone...  and this puts my laptop in danger of my rage :).
> > 
> > Traceback (most recent call last):
> >   File "/usr/bin/reportbug", line 2234, in 
> > main()
> >   File "/usr/bin/reportbug", line 1107, in main
> > return iface.user_interface()
> >   File "/usr/bin/reportbug", line 2225, in user_interface
> > self.options.envelopefrom)
> >   File "/usr/lib/python3/dist-packages/reportbug/submit.py", line 209,
> >   in send_report
> > (message, failed) = mime_attach(body, attachments, charset,
> > body_charset)
> >   File "/usr/lib/python3/dist-packages/reportbug/submit.py", line 157,
> >   in mime_attach
> > part = MIMEText(fp.read())
> >   File "/usr/lib/python3.5/codecs.py", line 321, in decode
> > (result, consumed) = self._buffer_decode(data, self.errors, final)
> > UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe5 in position
> > 296505: invalid continuation byte
> > 
> > and my locale is:
> > 
> > $ locale
> > LANG=en_DK.UTF-8
> 
> Your Traceback is different from the others. This bug is not fixed yet.
> 
> Did you try to attach a text(plain/html/etc) file in a different
> encoding than UTF-8? As a workaround, you could gzip that file.
> 
> Attached a patch that should fix the problem.
> Email had 1 attachment:
> + 0001-Handle-text-attachments-in-different-encodings.patch
>   1k (text/x-patch)

Bug#855602: libnids: undefined reference to `before' after being rebuilt / on mips64el

[James Cowgill]

Control: tags -1 - patch

Hi,

It seems that there are some other cases where the pre-GCC 5 behavior
of inline is assumed in libnids and therefore the patch I originally
posted it not enough to fix this.

For example, dsniff failed to build on Ubuntu (where this previous
patch is already applied) with:
> /usr/lib/libnids.so: undefined reference to `ip_compute_csum'
> /usr/lib/libnids.so: undefined reference to `my_tcp_check'
> /usr/lib/libnids.so: undefined reference to `my_udp_check'
> /usr/lib/libnids.so: undefined reference to `ip_fast_csum'

I found this patch from fedora which may be able to fix these, but I
have not tested it:

http://pkgs.fedoraproject.org/cgit/rpms/libnids.git/commit/?id=ecafb692f20e0acad555f66c3cc1646997a82dae

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#855602: libnids: undefined reference to `before' after being rebuilt / on mips64el

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - patch
Bug #855602 [src:libnids] libnids: undefined reference to `before' after being 
rebuilt / on mips64el
Removed tag(s) patch.

-- 
855602: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855602
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#855851: gcc-3.3: still in stretch

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 855851 wishlist
Bug #855851 [src:gcc-3.3] gcc-3.3: still in stretch
Severity set to 'wishlist' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
855851: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855851
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#855851: gcc-3.3: still in stretch

[Philipp Kern]

severity 855851 wishlist
thanks

On 2017-02-22 14:01, Santiago Vila wrote:

Dear maintainer:

Would be possible to get rid of gcc-3.3 in stretch?

We don't have gcc-5 anymore in stretch, so it would be really strange
that we still need gcc-3.3 (even if it's only the source) which is a
lot older.

If we really need gcc-3.3 in stretch, please downgrade and document
the reason here, so that it serves as documentation.

Thanks.


Why would I need to justify package presence in a serious RC bug? Wat?

It only builds libstdc++5. It's not even a full compiler. That's for 
compatibility with old binaries.


Kind regards
Philipp Kern

Bug#855843: marked as done (gtranscribe: fails to load audio file)

[Debian Bug Tracking System]

Your message dated Wed, 22 Feb 2017 14:49:12 +
with message-id 
and subject line Bug#855843: fixed in gtranscribe 0.7.1-2
has caused the Debian Bug report #855843,
regarding gtranscribe: fails to load audio file
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
855843: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855843
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gtranscribe
Version: 0.7.1-1
Severity: grave
Tags: upstream
Justification: renders package unusable

Hi,

trying to load an audio file (from console or gui) throws an error and the file
is not loaded. This makes gTranscribe rather useless:

philip@debian:~/gTranscribe$ gtranscribe ./WS321063.ogg
Traceback (most recent call last):
  File "/usr/bin/gtranscribe", line 210, in on_file_ready
logger.debug('received signal "ready"')
NameError: name 'logger' is not defined

A workaround is to enable debug logging.


Best,
Philip



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

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

Versions of packages gtranscribe depends on:
ii  gir1.2-glib-2.0  1.50.0-1
ii  gir1.2-gspell-1  1.2.2-1
ii  gir1.2-gst-plugins-base-1.0  1.10.3-1
ii  gir1.2-gstreamer-1.0 1.10.3-1
ii  gir1.2-gtk-3.0   3.22.7-2
ii  python3-dbus 1.2.4-1
ii  python3-gi   3.22.0-2
pn  python3:any  

Versions of packages gtranscribe recommends:
ii  gstreamer1.0-plugins-bad  1.10.3-1

gtranscribe suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gtranscribe
Source-Version: 0.7.1-2

We believe that the bug you reported is fixed in the latest version of
gtranscribe, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 855...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Philip Rinn  (supplier of updated gtranscribe package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 22 Feb 2017 12:59:44 +0100
Source: gtranscribe
Binary: gtranscribe
Architecture: source
Version: 0.7.1-2
Distribution: unstable
Urgency: medium
Maintainer: Philip Rinn 
Changed-By: Philip Rinn 
Description:
 gtranscribe - simple GTK+ tool focussed on easy transcription of spoken words
Closes: 855843
Changes:
 gtranscribe (0.7.1-2) unstable; urgency=medium
 .
   * Fix loading of audio files (closes: #855843).
Checksums-Sha1:
 08a61207f5048fc331a5abc5fb4b938c86d4fb5f 2208 gtranscribe_0.7.1-2.dsc
 7e1f3a139ba4fe257d020b799310667997c32594 4828 gtranscribe_0.7.1-2.debian.tar.xz
Checksums-Sha256:
 fec8f49f4c99f49d0db74f756fbf19b0e8f9d0a317f4eaec4dab667268c23004 2208 
gtranscribe_0.7.1-2.dsc
 aba0834b23f96aa3ea1ab8a462565beaada63956ce20170711060d95b8e1ea96 4828 
gtranscribe_0.7.1-2.debian.tar.xz
Files:
 876fd2370cb63bd815312623aaa963b8 2208 sound optional gtranscribe_0.7.1-2.dsc
 02e5deb1fda97c9b926ebf0b3be47fa6 4828 sound optional 
gtranscribe_0.7.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEYQsotVz8/kXqG1Y7MRa6Xp/6aaMFAlitlj8ACgkQMRa6Xp/6
aaPaTQ/9Gl8xihYgeVizYy0hgB+bC0fIIH5SS3lfQZLpEsPameJovEdzInZhOoLu
UpQ5R5d845jo0hfbQJhUJq5EZAascxFoQNsf8UJrHY+jQ/hU60fUAjX3VlUrAjY+
wrBnAd4m6FvqNmgvOcso+Ac66DBvd8S2az8DHzR7RxfBeWtCrWn4Z9pze5k4Bqel
mvVoOF1ZWhWwQSrwHVA4QHgZ14FJjz3V4CewiPVLTLFyMnKNs+iq5rEi+5tp6p6r
jt77k8fPPG7e1BH0NMilKn5EueXGQ5ZcyIgc3oYgSW0qBDgUWdtY2LL3HSAqTlCj
D7ynhe0/JqoV2MS0Gf47klYgfT2fBKwyRPnadM5WzNQGiSK2MrytNc/951BnzscS
QUJhXzyKfalK5kEdYvn+8LMOgPTsOcfUE4lmJNrYoYJ2RigvNw29FsgLKpUpAl3/
8MToJwAczzavtyFEGM8XuSczKxoDjq9ac07/L5CHOP3CXFDoncHz/qmiVxCgPIpo
OAgyjWQtAS/w6nJxU9rEQYnvwSW1bk6+3UnLWeqckh4rk7kA9A2DZgcuZEZo/kAi
PWfV7e6a5Q8iLL9eoFmu9xw7Xhu4KFKl35PnQhhLU4OiYrra2zSrHFOfyrT06bKs
qBHQYVm2gVJxJMlO5lYIxHIoxof1kkccT6a3SH+mkgjFc7A2D8M=
=KXSz
-END PGP 

Bug#855830: marked as pending

[Ghislain Antony Vaillant]

tag 855830 pending
thanks

Hello,

Bug #855830 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


http://git.debian.org/?p=python-modules/packages/pytest-qt.git;a=commitdiff;h=64acc56

---
commit 64acc56cca67110660e766527f43c60bff6d53c8
Author: Ghislain Antony Vaillant 
Date:   Wed Feb 22 14:24:39 2017 +

Release to unstable

diff --git a/debian/changelog b/debian/changelog
index ea1391d..c0d942d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+pytest-qt (2.1.0-2) unstable; urgency=medium
+
+  * Add missing copyright information.
+Thanks to Chris Lamb for reporting (Closes: #855830)
+  * Run autopkgtests for all supported Python versions
+
+ -- Ghislain Antony Vaillant   Wed, 22 Feb 2017 14:48:29 
+
+
 pytest-qt (2.1.0-1) unstable; urgency=low
 
   * Initial release. (Closes: #854365)

Bug#854991: marked as done (dnssec-triggerd: wrong path to dnssec-trigger-script (/usr/libexec vs /usr/lib))

[Debian Bug Tracking System]

Your message dated Wed, 22 Feb 2017 14:48:52 +
with message-id 
and subject line Bug#854991: fixed in dnssec-trigger 0.13-6
has caused the Debian Bug report #854991,
regarding dnssec-triggerd: wrong path to dnssec-trigger-script (/usr/libexec vs 
/usr/lib)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
854991: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854991
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dnssec-trigger
Version: 0.13-5
Severity: serious
File: /usr/sbin/dnssec-triggerd

I recently noticed this error in the systemd journal for dnssec-triggerd:

Feb 13 07:55:24 chianamo dnssec-triggerd[23003]: sh: 1: 
/usr/libexec/dnssec-trigger-script: not found
Feb 13 07:55:24 chianamo dnssec-triggerd[23003]: ok

Looks like the libexecdir was attempted to be set correctly but wasn't:

pabs@chianamo ~ $ dpkg -L dnssec-trigger  | xargs zgrep libexec
/usr/sbin/dnssec-triggerd:Binary file (standard input) matches
/usr/share/doc/dnssec-trigger/changelog.Debian.gz:  * Correctly set libexecdir 
to /usr/lib/dnssec-trigger to avoid patching
pabs@chianamo ~ $ strings /usr/sbin/dnssec-triggerd | grep libexec
/usr/libexec/dnssec-trigger-script --setup
/usr/libexec/dnssec-trigger-script --restore

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

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

Versions of packages dnssec-trigger depends on:
ii  gir1.2-networkmanager-1.0  1.6.0-1
ii  init-system-helpers1.47
ii  libc6  2.24-9
ii  libgdk-pixbuf2.0-0 2.36.4-1
ii  libglib2.0-0   2.50.2-2
ii  libgtk2.0-02.24.31-2
ii  libldns2   1.7.0-1
ii  libssl1.1  1.1.0d-2
ii  python 2.7.13-2
ii  python-gi  3.22.0-2
ii  python-lockfile1:0.12.2-2
ii  unbound1.6.0-2

dnssec-trigger recommends no packages.

dnssec-trigger suggests no packages.

-- debconf-show failed

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: dnssec-trigger
Source-Version: 0.13-6

We believe that the bug you reported is fixed in the latest version of
dnssec-trigger, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 854...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated dnssec-trigger package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 22 Feb 2017 15:11:05 +0100
Source: dnssec-trigger
Binary: dnssec-trigger
Architecture: source
Version: 0.13-6
Distribution: unstable
Urgency: medium
Maintainer: Debian DNS Packaging 
Changed-By: Ondřej Surý 
Description:
 dnssec-trigger - reconfiguration tool to make DNSSEC work
Closes: 854991
Changes:
 dnssec-trigger (0.13-6) unstable; urgency=medium
 .
   * Unhardcode libexec dir in riggerd/reshook.c (Closes: #854991)
Checksums-Sha1:
 5dbac0ad3642fd9e1824bf02c9dc30c0e7ce3d9e 2254 dnssec-trigger_0.13-6.dsc
 8e6b0649aa0c9dded4dd939b232b026102f87ee4 11960 
dnssec-trigger_0.13-6.debian.tar.xz
 07919ae5d7e7250f83b163243d15845a126e1f98 9684 
dnssec-trigger_0.13-6_amd64.buildinfo
Checksums-Sha256:
 e1e03ae1037bf4e6cfbd3dd10db4ac8742771827452ad75424be9d7e0be61f24 2254 
dnssec-trigger_0.13-6.dsc
 6f7cd800bc7431dcc114de4fc962f52b0c39397fc6988e0d14e4f4848448c942 11960 
dnssec-trigger_0.13-6.debian.tar.xz
 25ce9219541f98c710a5e98fd2cfb80f4f7bce8da45889230ad08c401653c9a9 9684 
dnssec-trigger_0.13-6_amd64.buildinfo
Files:
 f12b4757e28604c2fb59b5f8ab5babbb 2254 net optional dnssec-trigger_0.13-6.dsc
 

Processed: Bug#855830 marked as pending

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 855830 pending
Bug #855830 [src:pytest-qt] pytest-qt: Incomplete debian/copyright?
Warning: Unknown package 'src:pytest-qt'
Added tag(s) pending.
Warning: Unknown package 'src:pytest-qt'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
855830: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855830
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#855851: gcc-3.3: still in stretch

[Santiago Vila]

Package: src:gcc-3.3
Version: 1:3.3.6ds1-28
Severity: serious

Dear maintainer:

Would be possible to get rid of gcc-3.3 in stretch?

We don't have gcc-5 anymore in stretch, so it would be really strange
that we still need gcc-3.3 (even if it's only the source) which is a
lot older.

If we really need gcc-3.3 in stretch, please downgrade and document
the reason here, so that it serves as documentation.

Thanks.

Bug#855541: purple-matrix: Not ready for release yet

[Alberto Garcia]

On Mon, Feb 20, 2017 at 06:52:58PM +0100, Kurt Roeckx wrote:

> It's just that each time I mention I'm using this, people tell me
> taht it's experimental, and probably a bug in purple-matrix. But
> it's at least not always clear to me where the bugs are, and there
> seem to be various problems with the homeserver (synapse) too.

I don't know, I think I would understand you better if I had a list of
specific problems that make this software unsuitable for release.

I've been using it daily for months as my primary Matrix client on
my desktop computer, and the only issues I found are occasional
disconnects (and I'm not even sure that it's not a server problem).

> There are more problems with purple-matrix then that. For instance
> from the description of the package itself:
>  The following are not yet supported:
>   * Creating new rooms (and one-to-one chats)
>   * Joining existing rooms by alias instead of room_id

Those are clear missing features, and yes, you need a different client
to join a room. For some people that's probably an essential feature,
that's why it's clearly indicated in the package description.

In my case I only follow a limited number of rooms, I don't need to
join or create new ones, so this keeps me from having yet another chat
client open all the time.

> Like I said, if you think that you can support this version for the
> next 3 years, I have no problem with it. But I wouldn't add it to a
> stable release yet in it's current state.

I plan to keep using this plugin for the foreseeable time.

If this goes to stretch then it will be a simple Matrix client with
few dependencies and limited functionality, but otherwise stable
enough for everyday use.

Maybe I'm missing something, what is the scenario that you are worried
about?

Berto

Bug#855689: marked as done (jython.jar does not provide a Class-Path)

[Debian Bug Tracking System]

Your message dated Wed, 22 Feb 2017 12:33:46 +
with message-id 
and subject line Bug#855689: fixed in jython 2.5.3-15
has caused the Debian Bug report #855689,
regarding jython.jar does not provide a Class-Path
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
855689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855689
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jython
Version: 2.5.3-14
Severity: serious

There is no classpath for the dependencies of jython.jar defined in its
manifest:

$ unzip -p /usr/share/java/jython.jar META-INF/MANIFEST.MF | \
  grep Class-Path
$

This leads to the problem that dependent packages need to specify the
classpath themself, which is difficult since it is not documented in
/usr/share/docs/jython. Also, it requires tracking internal changes of
jython, since some of the dependent jar names are version dependent;
namely antlr3-runtime-3.2.jar, which makes it difficult to handle for
the dependencies over long time (f.e. for backports).

Java policy requires to have the classpath documented. I would ask you
to do this in the manifest (at least for the strong dependencies), since
this makes the usage much easier.

Thank you very much

Best regards

Ole
--- End Message ---
--- Begin Message ---
Source: jython
Source-Version: 2.5.3-15

We believe that the bug you reported is fixed in the latest version of
jython, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 855...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gilles Filippini  (supplier of updated jython package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 22 Feb 2017 11:52:18 +0100
Source: jython
Binary: jython jython-doc
Architecture: source
Version: 2.5.3-15
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Gilles Filippini 
Description:
 jython - Python seamlessly integrated with Java
 jython-doc - Jython documentation including API docs
Closes: 855689
Changes:
 jython (2.5.3-15) unstable; urgency=medium
 .
   * Set 'Class-Path' into jython.jar's manifest (closes: #855689)
Checksums-Sha1:
 20ca204aee0f648adf5902feec62accdeba44aff 2057 jython_2.5.3-15.dsc
 f9f79746cfc1202e5b1e98780550489c524e6e5e 19780 jython_2.5.3-15.debian.tar.xz
 87a9cd4b1a5b30cbec7ee93ce70950b33dd6ac55 6044 jython_2.5.3-15_source.buildinfo
Checksums-Sha256:
 bff4175d91ebdb6bfa37b475d1cabd0cab75844328c37d783153652c94b4e11b 2057 
jython_2.5.3-15.dsc
 f328ca40f3c5d67b3539e02f97280ef5be3828ceb28f38780ff830871d552b27 19780 
jython_2.5.3-15.debian.tar.xz
 cf35e2bcf2ef2cd4464ed2398c9159253de034a46f5549125e36854f990b7f02 6044 
jython_2.5.3-15_source.buildinfo
Files:
 84486a1c296f0611bf8a420b5e513767 2057 python optional jython_2.5.3-15.dsc
 58be3815076a63d186d8d9ec0c53ce4d 19780 python optional 
jython_2.5.3-15.debian.tar.xz
 0ff9227fce17b84ef566fe4a475f13b4 6044 python optional 
jython_2.5.3-15_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFEBAEBCAAuFiEEoJObzArDE05WtIyR7+hsbH/+z4MFAlitf1sQHHBpbmlAZGVi
aWFuLm9yZwAKCRDv6Gxsf/7Pg253B/9B7lUqro4Rx6ArdkMbWoBnffgSTGo4P3cQ
kQajlnegk7LkLCRuh8i+S5aWwGrfcA1zDobokwsGE0a5XEl482RLRSjU2zQ13RJT
dANB4gh6wiTkrJxziV2TEGFSOZDEYcpj38Ag+P8PGPjN5KXqsL37HuRDI/7T0K51
E9LpfJ0fqt6OoZ2JIna97r21Ktk0c6uSIbD612C1nMR1/P9/v1zNhQyPrzlcsVEw
C6tW0FxBT51T5JM/qS2B4G6szQDKD8WI31AY0M5EJIkO9noau2CzdLqabioDG6dE
GW0XF5KlR6U4tfL+BUIsgDzP9Q0Ri7QUYPpwMNE4PuNeRlaTaRed
=C2iI
-END PGP SIGNATURE End Message ---

Bug#855843: gtranscribe: fails to load audio file

[Philip Rinn]

Fixed version uploaded to mentors:

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

Waiting for my sponsor to upload.

Best,
Philip



signature.asc
Description: OpenPGP digital signature

Bug#855846: repo: requires software outside of the distribution to function

[Jonas Smedegaard]

Package: repo
Version: 1.12.37-1
Severity: serious
Justification: Policy 2.2

From the package description:

> repo is an unusual tool because it downloads all of its own Python
> modules using GPG-signed git tags, and stores those files as part of
> the project that it is working with.  So this package just provides
> the wrapper script, which provides the GPG signing keys for verifying
> that the correct Python code was downloaded.

Debian Policy § 2.2.1 says:

> [...] must not require or recommend a package outside of _main_ for
> compilation or execution

Debian Policy § 2.2.2 says:

> The _contrib_ archive area contains supplemental packages intended to
> work with the Debian distribution, but which require software outside
> of the distribution to either build or function.


I can only read this as repo (in its current form) belongs in contrib,
not main.

 - Jonas

Bug#855843: Patch

[Adrian Heine]

tags -1 + upstream patch

See https://github.com/innir/gtranscribe/commit/8c1da0f705
for a fix.



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#855843: gtranscribe: fails to load audio file

[Debian Bug Tracking System]

Processing control commands:

> tags -1 fixed-upstream pending
Bug #855843 [gtranscribe] gtranscribe: fails to load audio file
Added tag(s) pending and fixed-upstream.

-- 
855843: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855843
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#855843: gtranscribe: fails to load audio file

[Philip Rinn]

Control: tags -1 fixed-upstream pending

Hi,

here is the trivial patch:

https://github.com/innir/gtranscribe/commit/8c1da0f705edd1915aced4fa2359b76ca662a3ae.patch

I'll upload a fixed version soon and ask for an unblock.

Best,
Philip



signature.asc
Description: OpenPGP digital signature

Bug#855843: gtranscribe: fails to load audio file

[Philip Rinn]

Package: gtranscribe
Version: 0.7.1-1
Severity: grave
Tags: upstream
Justification: renders package unusable

Hi,

trying to load an audio file (from console or gui) throws an error and the file
is not loaded. This makes gTranscribe rather useless:

philip@debian:~/gTranscribe$ gtranscribe ./WS321063.ogg
Traceback (most recent call last):
  File "/usr/bin/gtranscribe", line 210, in on_file_ready
logger.debug('received signal "ready"')
NameError: name 'logger' is not defined

A workaround is to enable debug logging.


Best,
Philip



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

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

Versions of packages gtranscribe depends on:
ii  gir1.2-glib-2.0  1.50.0-1
ii  gir1.2-gspell-1  1.2.2-1
ii  gir1.2-gst-plugins-base-1.0  1.10.3-1
ii  gir1.2-gstreamer-1.0 1.10.3-1
ii  gir1.2-gtk-3.0   3.22.7-2
ii  python3-dbus 1.2.4-1
ii  python3-gi   3.22.0-2
pn  python3:any  

Versions of packages gtranscribe recommends:
ii  gstreamer1.0-plugins-bad  1.10.3-1

gtranscribe suggests no packages.

-- no debconf information

Bug#855615: tachyon: not binNMU safe

[Jerome BENOIT]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Thanks, now I can reproduce the issue. Jerome

On 22/02/17 14:08, James Cowgill wrote:
> Hi,
> 
> On 22/02/17 07:01, Jerome BENOIT wrote:
>> Dear James, thanks for your report.
>> I am looking for reproducing the issue. So far, I cannot.
>> Where can we get the binMMUed source material ?
>> Cheers, Jerome
> 
> Starting from tachyon 0.99~b6+dsx-7:
> $ dch --bin-nmu test
> $ dpkg-buildpackage -B -us -uc
> 
> Or alternatively using sbuild:
> $ sbuild -m'test ' --make-binNMU=test --binNMU=1 
> tachyon_0.99~b6+dsx-7
> 
> Thanks,
> James
> 
> 
> 

- -- 
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B
-BEGIN PGP SIGNATURE-

iQQcBAEBCgAGBQJYrXq1AAoJED+SGaZ/NsaLytwf/1/+s2kWcTI+D0lKksSEItqR
LvE68gKFPsSP82uWf6tXzbhSoDWXrQqBOX0pxbSVukyUogdczw1ZAxttFrN3ZRJI
N5v+0UZTyhrbIem0BgxZeOWAZhhsWZQoddF10AFVLq04EIsNc687kdQqqFzAKM6M
DglNeAv4HRBCXqcgNPZqeMEoOz385khL9gMCE4gKsuEXRQZNUKuCSxTVH5wdpOZY
OcfiXowQeZkXAtszBqjNf0kVHHwTUJLEuTRg+0B3nkG0DGRtd9di72wTpiRlb6oY
8NztEKV0H0Kmx+a4oBHDk5LwiGvzZ1mlMxFIjVVGrKegFoHlRmiGarMoG77Fy0Jo
uzcbJHq1OtUsz4vMi/jU0FDNoj9vVREuyG//CvNisZ8GAhqMbgMyLPn2qOB4smtb
xwoyktLWXfPhaxghBBg8nvrpwxoztvSSjUOBQ+cQq0sOCtbyn5Iuv56865XZmdq9
kkrEb/LmrtP3rRVi7gAqAMUUDUg1253t/Hg8n3vcSMVQqd1MDGkZzbYWodnanFEM
BrJKymf8HaNqRgxX2wPfmnYj9SRIu0+suTctY1OlWTrmoTX3vyxKJaXGeO0Ns9Tu
SEhrIMIP9lF4ILGKTlXsGF4MziakSvlY9SzVh00853igEU/Dpwz9mbZDOPXPe6NB
VdcK/nuyCnk9YO6eYBOFECdBV5vTSLNwmcWGH21lkl87gzaj2QiOPWGR4EElKv51
DKVfj7G2V+gdQE3ItQeCOjce21Ux9bY2Mf50bZgIeQ7jEGh2Qdy0v9UT6nAjtW3g
fXDh1plYrUu2bt8CH004W2syyPSnuSZgotUTRSAfWQg3pW2uiUPNX8giZ+ly2FsW
JXef7zSBmzh6d/UN4cWSLMizSS7XGZ/KOw6lI2Vv6mTC6pO/jXZgR5TcF1gKbiug
1eyEWG5Hvrzdp5zUVqfD5o9fyuzyrs9IwltgJbFz6KXW99MpgZ7b4TFlt/AO+YA6
GOOAh5RYqBQOVjZNlLlya36IEKcuia2MmEqEde6+pIE/XXbyX4wyB8qaxyoo+gji
9au6HKFV++TfRnkDjzsiE0y0GyPjsnzSA2YGzewXbgeGIOQ6k+nL5GlErJcSzZsc
ijol+dISUZa9Kb2FgHhX0bParAcMfrU5JTG3yEBJ8HKuyaofGbmfLBvZuH4IOfn0
2m0okf/0ncLDrc1iLwPZbl2cpuFpiOLXaQje00a2LXvgJ3rTJq8+WyoPZKpqPyjx
e3iWgDbB2LUKHL6mDP5eNzZV4vDdP2fOy+U/6q5Wfse2ZVu7fcQsJE4g3A5+q/7X
W+YpP3wD44w2kqnE6SweS4zoUg84+R884Y42zgCeZUz2r71F0wMTyNJ1/onMrZw=
=oo5G
-END PGP SIGNATURE-

Bug#855480: marked as done (examl: FTBFS with bash as /bin/sh)

[Debian Bug Tracking System]

Your message dated Wed, 22 Feb 2017 11:33:50 +
with message-id 
and subject line Bug#855480: fixed in examl 3.0.18-2
has caused the Debian Bug report #855480,
regarding examl: FTBFS with bash as /bin/sh
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
855480: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855480
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: examl
Version: 3.0.18-1
Severity: serious
Tags: patch
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

examl fails to build from source in unstable/amd64 when 
/bin/sh is set to bash:

  […]

  dh_auto_clean
  for mfile in Makefile.AVX.gcc Makefile.OMP.AVX.gcc Makefile.OMP.SSE3.gcc 
Makefile.SSE3.gcc; do /usr/bin/make --directory=examl -f ${mfile} clean ; done
  make[2]: Entering directory '«BUILDDIR»/examl'
  rm -f *.o examl-AVX
  make[2]: Leaving directory '«BUILDDIR»/examl'
  make[2]: Entering directory '«BUILDDIR»/examl'
  rm -f *.o examl-OMP-AVX
  make[2]: Leaving directory '«BUILDDIR»/examl'
  make[2]: Entering directory '«BUILDDIR»/examl'
  rm -f *.o examl-OMP
  make[2]: Leaving directory '«BUILDDIR»/examl'
  make[2]: Entering directory '«BUILDDIR»/examl'
  rm -f *.o examl
  make[2]: Leaving directory '«BUILDDIR»/examl'
  /usr/bin/make --directory=parser -f Makefile.SSE3.gcc clean ; done
  /bin/sh: -c: line 0: syntax error near unexpected token `done'
  /bin/sh: -c: line 0: `/usr/bin/make --directory=parser -f Makefile.SSE3.gcc 
clean ; done'
  debian/rules:15: recipe for target 'override_dh_auto_clean' failed
  make[1]: *** [override_dh_auto_clean] Error 1
  make[1]: Leaving directory '«BUILDDIR»'
  debian/rules:12: recipe for target 'clean' failed
  make: *** [clean] Error 2
  dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2

  […]

Patch attached.


Regards,

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


examl.3.0.18-1.unstable.amd64.log.txt.gz
Description: Binary data
diff --git a/debian/rules b/debian/rules
index 84fa450..ad28a42 100755
--- a/debian/rules
+++ b/debian/rules
@@ -14,9 +14,9 @@ SRCDIR:=examl
 override_dh_auto_clean:
dh_auto_clean
for mfile in $(MFILES); do $(MAKE) --directory=$(SRCDIR) -f $${mfile} 
clean ; done
-   $(MAKE) --directory=parser -f Makefile.SSE3.gcc clean ; done
+   $(MAKE) --directory=parser -f Makefile.SSE3.gcc clean
 
 override_dh_auto_build:
dh_auto_build
for mfile in $(MFILES); do $(MAKE) --directory=$(SRCDIR) -f $${mfile} ; 
done
-   $(MAKE) --directory=parser -f Makefile.SSE3.gcc ; done
+   $(MAKE) --directory=parser -f Makefile.SSE3.gcc
--- End Message ---
--- Begin Message ---
Source: examl
Source-Version: 3.0.18-2

We believe that the bug you reported is fixed in the latest version of
examl, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 855...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated examl package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 22 Feb 2017 12:06:12 +0100
Source: examl
Binary: examl
Architecture: source amd64
Version: 3.0.18-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 examl  - Exascale Maximum Likelihood (ExaML) code for phylogenetic inferen
Closes: 855430 855480
Changes:
 examl (3.0.18-2) unstable; urgency=medium
 .
   * Fix cut-n-pasto in d/rules (thanks for the patch to Chris Lamb
 )
 Closes: #855480
   * Restrict build to intel architectures
 Closes: #855430
Checksums-Sha1:
 c01a5e5b0890bc876ad43358e4353e22bdc82ef6 2052 examl_3.0.18-2.dsc
 59e14491a6233c7e96a6594a9d70c31e96905e64 7588 examl_3.0.18-2.debian.tar.xz
 4c6c7e3c04d3e4824ad806c8d085abc77bcb0d65 1311064 
examl-dbgsym_3.0.18-2_amd64.deb
 

Bug#852960: rt-app FTBFS on mips64el/ppc64el: error: conflicting types for 'timespec_to_nsec'

[Gianfranco Costamagna]

Hi,
On Tue, 7 Feb 2017 14:23:33 + Radovan Birdic  
wrote:
> Hi,
> 
> Build for mips64 and powerpc64 fails because __SANE_USERSPACE_TYPES__ is not 
> defined.
> Without this flag in "asm/types.h" file always will be included "int-l64.h" 
> which means that __u64 always will be defined as unsigned long.
> 
> I have created and attached a patch witch defines __SANE_USERSPACE_TYPES__ 
> flag for mips64 and powerpc64.
> With this patch package builds successfully on mips, mipsel and  mips64el.
> 
> Another way to solve the problem could be adding -D__SANE_USERSPACE_TYPES__ 
> to CFLAGS.
> 

Another way might even be to patch the .h and .c to use the same prototype, in 
the same way as before

diff -Nru rt-app-0.3/debian/changelog rt-app-0.3/debian/changelog
--- rt-app-0.3/debian/changelog 2017-01-26 05:23:22.0 +
+++ rt-app-0.3/debian/changelog 2017-02-22 10:28:22.0 +
@@ -1,3 +1,9 @@
+rt-app (0.3-1ubuntu1) zesty; urgency=medium
+
+  * Fix build on ppc64el
+
+ -- Gianfranco Costamagna   Wed, 22 Feb 2017 
11:28:13 +0100
+
 rt-app (0.3-1) unstable; urgency=medium
 
   * New upstream release, merging ARM and Linaro variants
diff -Nru rt-app-0.3/debian/patches/longlong-u64.diff 
rt-app-0.3/debian/patches/longlong-u64.diff
--- rt-app-0.3/debian/patches/longlong-u64.diff 1970-01-01 00:00:00.0 
+
+++ rt-app-0.3/debian/patches/longlong-u64.diff 2017-02-22 10:28:09.0 
+
@@ -0,0 +1,11 @@
+--- rt-app-0.3.orig/src/rt-app_utils.h
 rt-app-0.3/src/rt-app_utils.h
+@@ -123,7 +123,7 @@ log_timing(FILE *handler, timing_point_t
+ pid_t
+ gettid(void);
+ 
+-unsigned long long
++__u64
+ timespec_to_nsec(struct timespec *ts);
+ #endif
+ 
diff -Nru rt-app-0.3/debian/patches/series rt-app-0.3/debian/patches/series
--- rt-app-0.3/debian/patches/series1970-01-01 00:00:00.0 +
+++ rt-app-0.3/debian/patches/series2017-02-22 10:28:09.0 +
@@ -0,0 +1 @@
+longlong-u64.diff


(this was already there in the previous release, I reintroduced it in Ubuntu)

G.



signature.asc
Description: OpenPGP digital signature

Processed: Fwd: Re: jython.jar does not provide a Class-Path

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 855689 + patch
Bug #855689 [jython] jython.jar does not provide a Class-Path
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
855689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855689
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#855837: golang-petname: Do not include in stretch at request of maintainer

[Jonathan Dowland]

Package: golang-petname
Severity: serious

I uploaded this as a dependency of LXD which unfortunately we did not finish
packaging in time for the Stretch freeze. As such, unless someone else is
prepared to help support it, and/or users of this package come out of the
woodwork, I do not think we should include this library in Stretch.

-- 
Jonathan Dowland


signature.asc
Description: Digital signature

Bug#855689: jython.jar does not provide a Class-Path

[Ole Streicher]

Hi Gilles,

Am 21.02.2017 um 22:09 schrieb Gilles Filippini:
> Would the attached patch do the trick?

yes, I can confirm that this works well for me. Thank you for the quick fix.

Best regards

Ole

Bug#855615: tachyon: not binNMU safe

[James Cowgill]

Hi,

On 22/02/17 07:01, Jerome BENOIT wrote:
> Dear James, thanks for your report.
> I am looking for reproducing the issue. So far, I cannot.
> Where can we get the binMMUed source material ?
> Cheers, Jerome

Starting from tachyon 0.99~b6+dsx-7:
$ dch --bin-nmu test
$ dpkg-buildpackage -B -us -uc

Or alternatively using sbuild:
$ sbuild -m'test ' --make-binNMU=test --binNMU=1 
tachyon_0.99~b6+dsx-7

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Processed: tagging 852380

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # compatibility with a stretch library, does not affect jessie
> tags 852380 + stretch sid
Bug #852380 {Done: Simon McVittie } [ekeyd] ekeyd: Does not 
start after luasocket upgrade
Added tag(s) sid and stretch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
852380: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852380
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#855830: pytest-qt: Incomplete debian/copyright?

[Chris Lamb]

Source: pytest-qt
Version: 2.1.0-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Ghislain Antony Vaillant 

Hi,

I just ACCEPTed pytest-qt from NEW but noticed it was missing 
attribution in debian/copyright for at least scripts/link_pyqt.py.

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


Regards,

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

Bug#794856: marked as done (opencv: non DFSG file in the source package)

[Debian Bug Tracking System]

Your message dated Wed, 22 Feb 2017 08:50:22 +
with message-id 
and subject line Bug#794856: fixed in opencv 2.4.9.1+dfsg1-1
has caused the Debian Bug report #794856,
regarding opencv: non DFSG file in the source package
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
794856: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794856
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: opencv
Version: 2.4.9.1+dfsg-1.1
Severity: Serious
Justification: non DFSG file in the source package
User: locutusofb...@debian.org
Usertags: license-problem-non-free-img-lenna

Hi opencv Maintainer(s),
your package has been found to contain a copy of a non DFSG
file, that makes your package non DFSG.

This image (called lenna.jpg, or lena.jpg with some variants)
is an image of Lena Söderberg, photographed by Dwight Hooker,
cropped from the centerfold of the November 1972 issue of Playboy magazine.

This file is to be considered distributable but non free
(at the end of this bug report you will find a link to the lintian tag,
with a more complete description of the issue and references)

Below a list of the affected files:
- samples/c/lena.jpg
- samples/cpp/lena.jpg
- samples/cpp/tutorial_code/images/lena.png
- doc/tutorials/introduction/clojure_dev_intro/images/lena.png
- doc/tutorials/introduction/desktop_java/images/lena.png
- modules/java/android_test/res/drawable/lena.jpg
- samples/winrt/OcvImageProcessing/OcvImageProcessing/Assets/Lena.png
- samples/java/clojure/simple-sample/resources/images/lena.png

note, I did stop checking for the all files as soon as I found one
good match, so they might be not all bad references, please update
this bug if not correct.

More information about this issue can be found on the
license-problem-non-free-img-lenna lintian tag [1] and Debian bug [2]

[1] https://lintian.debian.org/tags/license-problem-non-free-img-lenna.html
[2] https://bugs.debian.org/771191

thanks,

Gianfranco
--- End Message ---
--- Begin Message ---
Source: opencv
Source-Version: 2.4.9.1+dfsg1-1

We believe that the bug you reported is fixed in the latest version of
opencv, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 794...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated opencv package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 19 Feb 2017 17:15:16 +0100
Source: opencv
Binary: opencv-doc libcv-dev libcv2.4 libhighgui-dev libhighgui2.4 libcvaux-dev 
libcvaux2.4 libopencv-dev opencv-data libopencv-core-dev libopencv-core2.4v5 
libopencv-ml-dev libopencv-ml2.4v5 libopencv-imgproc-dev libopencv-imgproc2.4v5 
libopencv-video-dev libopencv-video2.4v5 libopencv-objdetect-dev 
libopencv-objdetect2.4v5 libopencv-highgui-dev libopencv-highgui2.4-deb0 
libopencv-calib3d-dev libopencv-calib3d2.4v5 libopencv-flann-dev 
libopencv-flann2.4v5 libopencv-features2d-dev libopencv-features2d2.4v5 
libopencv-legacy-dev libopencv-legacy2.4v5 libopencv-contrib-dev 
libopencv-contrib2.4v5 libopencv-ts-dev libopencv-ts2.4v5 libopencv-photo-dev 
libopencv-photo2.4v5 libopencv-videostab-dev libopencv-videostab2.4v5 
libopencv-stitching-dev libopencv-stitching2.4v5 libopencv-gpu-dev 
libopencv-gpu2.4v5 libopencv-superres-dev libopencv-superres2.4v5 
libopencv-ocl-dev libopencv-ocl2.4v5 libopencv2.4-java libopencv2.4-jni 
python-opencv
Architecture: source
Version: 2.4.9.1+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Jochen Sprickerhof 
Description:
 libcv-dev  - Translation package for libcv-dev
 libcv2.4   - computer vision library - libcv* translation package
 libcvaux-dev - Translation package for libcvaux-dev
 libcvaux2.4 - computer vision library - libcvaux translation package
 libhighgui-dev - Translation package for libhighgui-dev
 libhighgui2.4 - computer vision library - libhighgui translation package
 libopencv-calib3d-dev - development files for libopencv-calib3d
 libopencv-calib3d2.4v5 - 

Bug#849504: Data corruption with copy-on-write and multiple threads

[Wouter Verhelst]

On Tue, Feb 14, 2017 at 04:41:00PM +, Niels Thykier wrote:
> Wouter Verhelst:
> > Hi Niels,
> > 
> > On Sun, Feb 12, 2017 at 08:52:00AM +, Niels Thykier wrote:
> >> Any news on this bug?
> > 
> > I'm going to release (upstream) nbd 3.15.2 later this week (probably on
> > thursday), which contains the fix:
> > 
> > https://github.com/NetworkBlockDevice/nbd/compare/nbd-3.15.1...master
> > 
> > This patch series includes:
> > 
> > - The fix for this bug, commit a43a2d8;
> > - Several minor documentation fixes (e.g., fixed the sorting of a listing 
> > in a
> >   man page);
> > - A better fix for the issue of nbd-client-udeb being compiled against 
> > GnuTLS
> >   that does not break the build on kFreeBSD etc;
> > - The ability to change the GnuTLS priority string, to follow TLS best
> >   practices and allow people to lock down the TLS configuration
> > 
> > I would like to update nbd to that version; but if the release team
> > prefers, I can cherry-pick a43a2d8 onto 3.15.1 and upload that instead.
> > 
> 
> Thanks for getting back to me on this.
> 
> On the note of the actual changes, could you please provide a (source)
> debdiff, so I know what we are looking at?

Attached.

Unfortunately, there's a bit of churn because I forgot to rename
nbd-3.15.1.tar.gz to nbd_3.15.1.orig.tar.gz, thereby causing it to be
uploaded as a native package, with a bit of stuff that shouldn't have
been in there. At least it didn't contain random junk like in the past,
but a .gitignore, some autotools metadata files, as well as a few files
that are meant to be shipped as symlinks rather than copies of files
from elsewhere in the tree (e.g., tests/run/buffer.c) do show up in the
debdiff.

If you ignore those, what remains is the changelog entry plus the
changes that I pointed to earlier.

Thanks for looking at this,

-- 
< ron> I mean, the main *practical* problem with C++, is there's like a dozen
   people in the world who think they really understand all of its rules,
   and pretty much all of them are just lying to themselves too.
 -- #debian-devel, OFTC, 2016-02-12
diff -Nru nbd-3.15.1/debian/changelog nbd-3.15.2/debian/changelog
--- nbd-3.15.1/debian/changelog 2016-12-20 20:36:11.0 +0100
+++ nbd-3.15.2/debian/changelog 2017-02-22 09:10:22.0 +0100
@@ -1,3 +1,12 @@
+nbd (1:3.15.2-1) unstable; urgency=medium
+
+  * New upstream release
+- Fixes data corruption with multiple threads and copyonwrite enabled;
+  Closes: #852288, #849504. Why did I create multiple bugs for this?
+  Ah well, no matter.
+
+ -- Wouter Verhelst   Wed, 22 Feb 2017 00:09:31 +0100
+
 nbd (1:3.15.1-2) unstable; urgency=medium
 
   * Build nbd-client a second time with GnuTLS disabled, and install
diff -Nru nbd-3.15.1/.deps/libcliserv_la-cliserv.Plo 
nbd-3.15.2/.deps/libcliserv_la-cliserv.Plo
--- nbd-3.15.1/.deps/libcliserv_la-cliserv.Plo  2016-12-20 20:36:11.0 
+0100
+++ nbd-3.15.2/.deps/libcliserv_la-cliserv.Plo  1970-01-01 01:00:00.0 
+0100
@@ -1 +0,0 @@
-# dummy
diff -Nru nbd-3.15.1/.deps/libnbdsrv_la-nbdsrv.Plo 
nbd-3.15.2/.deps/libnbdsrv_la-nbdsrv.Plo
--- nbd-3.15.1/.deps/libnbdsrv_la-nbdsrv.Plo2016-12-20 20:36:11.0 
+0100
+++ nbd-3.15.2/.deps/libnbdsrv_la-nbdsrv.Plo1970-01-01 01:00:00.0 
+0100
@@ -1 +0,0 @@
-# dummy
diff -Nru nbd-3.15.1/.deps/libnbdsrv_la-treefiles.Plo 
nbd-3.15.2/.deps/libnbdsrv_la-treefiles.Plo
--- nbd-3.15.1/.deps/libnbdsrv_la-treefiles.Plo 2016-12-20 20:36:11.0 
+0100
+++ nbd-3.15.2/.deps/libnbdsrv_la-treefiles.Plo 1970-01-01 01:00:00.0 
+0100
@@ -1 +0,0 @@
-# dummy
diff -Nru nbd-3.15.1/.deps/make-integrityhuge.Po 
nbd-3.15.2/.deps/make-integrityhuge.Po
--- nbd-3.15.1/.deps/make-integrityhuge.Po  2016-12-20 20:36:11.0 
+0100
+++ nbd-3.15.2/.deps/make-integrityhuge.Po  1970-01-01 01:00:00.0 
+0100
@@ -1 +0,0 @@
-# dummy
diff -Nru nbd-3.15.1/.deps/nbd_client-buffer.Po 
nbd-3.15.2/.deps/nbd_client-buffer.Po
--- nbd-3.15.1/.deps/nbd_client-buffer.Po   2016-12-20 20:36:11.0 
+0100
+++ nbd-3.15.2/.deps/nbd_client-buffer.Po   1970-01-01 01:00:00.0 
+0100
@@ -1 +0,0 @@
-# dummy
diff -Nru nbd-3.15.1/.deps/nbd_client-crypto-gnutls.Po 
nbd-3.15.2/.deps/nbd_client-crypto-gnutls.Po
--- nbd-3.15.1/.deps/nbd_client-crypto-gnutls.Po2016-12-20 
20:36:11.0 +0100
+++ nbd-3.15.2/.deps/nbd_client-crypto-gnutls.Po1970-01-01 
01:00:00.0 +0100
@@ -1 +0,0 @@
-# dummy
diff -Nru nbd-3.15.1/.deps/nbd_client-nbd-client.Po 
nbd-3.15.2/.deps/nbd_client-nbd-client.Po
--- nbd-3.15.1/.deps/nbd_client-nbd-client.Po   2016-12-20 20:36:11.0 
+0100
+++ nbd-3.15.2/.deps/nbd_client-nbd-client.Po   1970-01-01 01:00:00.0 
+0100
@@ -1 +0,0 @@
-# dummy
diff -Nru nbd-3.15.1/.deps/nbd_server-nbd-server.Po 
nbd-3.15.2/.deps/nbd_server-nbd-server.Po
--- nbd-3.15.1/.deps/nbd_server-nbd-server.Po   2016-12-20 20:36:11.0 
+0100
+++