Bug#831335: jessie-pu: package publicsuffix/20160703-1

[Adam D. Barratt]

On Mon, 2016-08-08 at 18:51 -0400, Daniel Kahn Gillmor wrote:
> On Sat 2016-08-06 17:15:25 -0400, Adam D. Barratt wrote:
> > Thanks; please feel free to upload that, with a small tweak:
> >
> > +publicsuffix (20160703-0+deb8u1) stable; urgency=medium
> > +
> > +  * prepare for stable-proposed-updates.
> >
> > "jessie" is generally preferred as the changelog distribution and maybe
> > "Upload to stable" or something similar?
[...]
> > Every couple of months is when we aim (not always successfully) to do a
> > stable point release, so that hopefully works out well all around.
> 
> I've never maintained this class of package before.  do i just do
> regular uploads to "jessie" as new versions of the package become
> available, or do i need to do a jessie-pu bug report for each one?

The latter, please.

Regards,

Adam

Bug#833823: CVE-2016-6515: CPU consumption via auth_password

[Guido Günther]

Source: openssh
Severity: important
Version: 1:7.3p1-1

Hi,
Openssh is affected by this issue:

 https://security-tracker.debian.org/tracker/CVE-2016-6515

Cheers,
 -- Guido


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

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

Bug#831113: [/master] New upstream release (Closes: #831113).

[Andrew Starr-Bochicchio]

tag 831113 pending
thanks

Date: Mon Aug 8 22:40:07 2016 -0400
Author: Andrew Starr-Bochicchio 
Commit ID: a67a429d29aa060b41f9f4faf8be28b105f6b5ad
Commit URL: 
http://anonscm.debian.org/gitweb/?p=collab-maint/qbittorrent.git;a=commitdiff;h=a67a429d29aa060b41f9f4faf8be28b105f6b5ad
Patch URL: 
http://anonscm.debian.org/gitweb/?p=collab-maint/qbittorrent.git;a=commitdiff_plain;h=a67a429d29aa060b41f9f4faf8be28b105f6b5ad

New upstream release (Closes: #831113).

  

Bug#827245: missing backend for pool type 11 (zfs)

[Guido Günther]

On Tue, Aug 09, 2016 at 06:50:20AM +0200, Guido Günther wrote:
> On Mon, Aug 08, 2016 at 09:28:12PM +, Tyler Fenby wrote:
> > I can confirm that the ZFS backend works as expected on Debian after
> > recompiling libvirt with only a couple lines added to debian/rules to
> > enable the configure flag.
> 
> Care enough to send a patch that does the right selection of
> architectures and adds the build-deps to debian/control?

Nevermind. I think I figured it out. It's zfs-utils-linux on linux not
zfs-utils.
 -- Guido

Bug#833486: (no subject)

[Josue Ortega]

Version: 2.4.103-3

I am closing this bug since I'll be the new
maintainer. 

---
Josue Ortega
«Happy Hacking»
http://josueortega.org

signature.asc
Description: PGP signature

Bug#833745: [Pkg-libvirt-maintainers] Bug#833745: libvirt-daemon-system: Please use SIGUSR1 to restart virtlockd and virtlogd on upgrade

[Guido Günther]

On Tue, Aug 09, 2016 at 12:44:41AM +0200, Laurent Bigonville wrote:
> Le 08/08/16 à 18:59, Guido Günther a écrit :
> > We should be doing this for virtlockd already since ages, we have:
> > 
> >dh_systemd_start -p libvirt-daemon-system --no-restart-on-upgrade 
> > libvirt-guests.service virtlockd.socket virtlockd.service
> > 
> > so this should work. virtlogd is indeed missing. Do you have a log of
> > the virtlockd restart?
> Looking at /var/lib/dpkg/info/libvirt-daemon-system.postinst, virtlockd is
> not restarted or reloaded at all, only started the first time:
> 
> # End automatically added section
> # Automatically added by dh_systemd_start
> if [ -d /run/systemd/system ]; then
> systemctl --system daemon-reload >/dev/null || true
> if [ -n "$2" ]; then
> _dh_action=try-restart
> else
> _dh_action=start
> fi
> deb-systemd-invoke $_dh_action virtlockd.socket >/dev/null || true
> fi
> # End automatically added section
> # Automatically added by dh_systemd_start
> if [ -d /run/systemd/system ]; then
> systemctl --system daemon-reload >/dev/null || true
> deb-systemd-invoke start virtlockd.service virtlockd.socket 
> >/dev/null || true
> fi

I'm not talking about the automatically added stuff. I mean

$ git show debian/sid:debian/libvirt-daemon-system.postinst | grep -C2 reload
# Force virtlockd to reexec if enabled
if [ -d /run/systemd/system ] && systemctl is-active -q 
virtlockd.service; then
   systemctl reload virtlockd.service
fi

Cheers,
 -- Guido

Bug#827245: missing backend for pool type 11 (zfs)

[Guido Günther]

On Mon, Aug 08, 2016 at 09:28:12PM +, Tyler Fenby wrote:
> I can confirm that the ZFS backend works as expected on Debian after
> recompiling libvirt with only a couple lines added to debian/rules to
> enable the configure flag.

Care enough to send a patch that does the right selection of
architectures and adds the build-deps to debian/control?
 -- Guido

> 
> Regards,
> 
> Tyler Fenby

Bug#833798: krb5: FTBFS with -O3: uninitialized variables

[Benjamin Kaduk]

I guess I can take responsibility for telling upstream about it, since no
one seems to have done so yet :-/

-Ben

Bug#803456: Digikam 5.0.0 uploaded

[Steve M. Robbins]

On Wednesday, August 3, 2016 10:59:30 PM CDT you wrote:
> Hi,
> 
> First a big thanks at Steve for packaging digikam!
> I proposed an information on the welcome page about the configuration
> transition. I hope this is included before 5.1.0:
> https://bugs.kde.org/show_bug.cgi?id=364258#c18

Thank you for that!  I see it was merged by Gilles.

> I will keep you posted. I would really like to see digikam5 in
> non-experimental debian repo soon!
> 
> On a side note: Is bug triaging on this package welcomed?

Yes, please!  And thank you!

-Steve


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

Bug#833771: nspr FTCBFS: does not honour DEB_BUILD_OPTIONS=nocheck

[Helmut Grohne]

Hi Mike,

On Tue, Aug 09, 2016 at 06:38:09AM +0900, Mike Hommey wrote:
> I'd argue dh should not be calling override_dh_auto_test in the first
> place...

Incidentally, I am fixing precisely this bug in a lot of packages, and
had the same idea. So even before filing this bug, I went to Niels and
discussed exactly that idea.

The gist of that discussion was that the suggested behaviour would add
inconsistency to debhelpers interface and could break packages. While
the common case is to actually run tests in the override target, they
can be used for anything. In keeping with our suggestion, maybe
override_dh_strip should be skipped for DEB_BUILD_OPTIONS=nostrip? It's
not too hard to find actual packages broken by that move.

So our conclusion at that time (and maybe Niels had more and better
arguments) was that debhelper should not do that. Still, maybe some part
of its documentation could have a faq entry as it keeps popping up?

Even though I would have liked not having to send this patch to many
different packages, it looks like it's not gonna happen.

Helmut

Bug#833709: Please add the MIT/Expat license to common-licenses

[Josh Triplett]

On Mon, Aug 08, 2016 at 06:37:41PM -0700, Russ Allbery wrote:
> Josh Triplett  writes:
> > On Mon, Aug 08, 2016 at 11:53:37AM -0700, Russ Allbery wrote:
> 
> >> I don't think this is a good idea.  This license is extremely short,
> >> and it has a ton of minor variations, so we'll get a lot of people
> >> using it even though the exactly licensing terms of their package don't
> >> match the canonical copy.
> 
> >> For example, it's very common to see "THE AUTHORS" replaced with a
> >> specific list of people or organizations in the license, which is a
> >> very small change that's easy for someone to miss when they know that
> >> the terms are just the Expat terms.
> 
> > In the various packages I looked at, I haven't seen any such variation
> > of the MIT/Expat license.  I've seen many variations of the MIT/X11
> > license, but not of Expat.
> 
> I just checked my (tiny) corpus and you're right, I haven't seen
> variations in the stuff I've analyzed in the Expat wording variation.  I
> was thinking of the MIT wording variation.

Thanks for confirming.

> > For many of the packages I'd hoped to use it for, the sum total of the
> > license information in the upstream source consists of the following
> > line in the package metadata:
> 
> > license = "MIT"
> 
> > No copyright notices, no license file, just a simple statement of the
> > license name using canonical SPDX license identifiers.
> 
> > For such packages, referencing a canonical copy of the license seems
> > preferable.
> 
> It really doesn't to me.  Copying the text that identifier refers to in
> whatever metadata scheme you're looking at seems much better to me, since
> you know for certain what text this is supposed to reference.  (There are
> a ton of licenses named "MIT", and I think far more people don't use SPDX
> than actually use it.)
> 
> I could see the argument if we were fully adopting SPDX and checking that
> these things mean something consistent, but I think we should do that in a
> broader way than just adding more licenses to common-licenses if we do
> that.

In the specific case of the MIT/Expat license, it's one of the most
popular FOSS licenses, and thousands of packages in Debian use it.  It's
certainly used by far more packages than other licenses already included
in common-licenses.  I realize it's a short license, but I find it quite
helpful to see references to common-licenses in debian/copyright files,
not least of which because I can assume they match the canonical
license.

- Josh Triplett

Bug#833706: Additional instance

[Carl Fink]

Another report: same error and same behavior on a Lenovo Yoga 11S. Using 
the 64-bit netinst image. Going to try the more complete media image now.


--

Carl Fink
c...@finknetwork.com

Bug#816779: Remmina doesn't always honor scale ratio lock

[Dark Penguin]

This is one of two bugs with Remmina that really annoy me; after a 
while, I've gathered more data and now I think have the simplest way to 
reproduce the problem. Also, this time all the machines are running 
Debian Jessie with MATE.


- I connect over VNC to one machine with a 1024x768 screen. A small 
window appears in the center of my FullHD screen. (This is a good 
starting point to see all kinds of scaling problems that I have.)


- Then I connect to another machine with a FullHD screen. The window is 
still the same size, but now a FullHD screen is cramped into it (without 
honoring my "Maintain scale ratio" option, of course.)


Now if I resize the window by dragging its border, or click "Maintain 
scale ratio" twice to disable it and enable it back, then it resizes the 
image properly; but whatever else I do, the scale ration is not honored.


What I've tried:

- Being not happy, I try to "Maximize" the window. The image is now 
stretched in a thin horizontal line with black borders above and below - 
neither honoring the scale ratio, nor even scaling to fit all the screen.


- If I click "Resize the windows to fit in remote resolution", the same 
happens.


- If I click "Toggle fullscreen mode", the same happens.

- After any of those, if I toggle the "Scaling mode" off and back on, 
then it scales to cover all the window, but still does not honor the 
"Maintain scale ratio".



I've also tried this with RDP - connecting to Windows machines. The 
results are the same.


And finally, only in the case when the remote screen is SMALLER than the 
window, turning "Scaled mode" off and on helps resize the window 
properly. When the remote screen is LARGER than the window, it does not 
honor the aspect ratio.



--
darkpenguin

Bug#816097: Possible point of interest, sbuild does not exhibit this bug

[Chris Lea]

There doesn't seem to be much if any activity around this bug for pbuilder
/ cowbuilder. I did want to let folks know that sbuild does not have the
same issues with the armhf emulation. Meaning I've successfully built armhf
binaries for Sid and Xenial on a Xenial host machine using sbuild.

It took an hour or two to get used to the sbuild tools, but they aren't
really any trickier to get working than pbuilder was. This article from the
Ubuntu wiki was quite helpful:

https://wiki.ubuntu.com/SimpleSbuild

so if anybody is stuck here, I'd advise checking sbuild out.

-- 
__
https://chrislea.com
http://about.me/chrislea
310-709-4021

Bug#833709: Please add the MIT/Expat license to common-licenses

[Russ Allbery]

Simon McVittie  writes:

> It would be great if Policy described what the ftp-masters actually
> require and why, so that maintainers could provide everything that Debian
> needs to avoid legal trouble but no more. At the moment, Policy is rather
> more vague than the actual requirements to get software into Debian; there
> seems to be some (unwritten?) policy based on ftp-master consensus.

The prerequisite for this would be for ftp-master to publish what they
require and why.  There have been a lot of past discussions about that.
My understanding is that this document does not presently exist except
insofar as the REJECT FAQ could be said to be that document.

-- 
Russ Allbery (r...@debian.org)   

Bug#833709: Please add the MIT/Expat license to common-licenses

[Russ Allbery]

Josh Triplett  writes:
> On Mon, Aug 08, 2016 at 11:53:37AM -0700, Russ Allbery wrote:

>> I don't think this is a good idea.  This license is extremely short,
>> and it has a ton of minor variations, so we'll get a lot of people
>> using it even though the exactly licensing terms of their package don't
>> match the canonical copy.

>> For example, it's very common to see "THE AUTHORS" replaced with a
>> specific list of people or organizations in the license, which is a
>> very small change that's easy for someone to miss when they know that
>> the terms are just the Expat terms.

> In the various packages I looked at, I haven't seen any such variation
> of the MIT/Expat license.  I've seen many variations of the MIT/X11
> license, but not of Expat.

I just checked my (tiny) corpus and you're right, I haven't seen
variations in the stuff I've analyzed in the Expat wording variation.  I
was thinking of the MIT wording variation.

> For many of the packages I'd hoped to use it for, the sum total of the
> license information in the upstream source consists of the following
> line in the package metadata:

> license = "MIT"

> No copyright notices, no license file, just a simple statement of the
> license name using canonical SPDX license identifiers.

> For such packages, referencing a canonical copy of the license seems
> preferable.

It really doesn't to me.  Copying the text that identifier refers to in
whatever metadata scheme you're looking at seems much better to me, since
you know for certain what text this is supposed to reference.  (There are
a ton of licenses named "MIT", and I think far more people don't use SPDX
than actually use it.)

I could see the argument if we were fully adopting SPDX and checking that
these things mean something consistent, but I think we should do that in a
broader way than just adding more licenses to common-licenses if we do
that.

-- 
Russ Allbery (r...@debian.org)   

Bug#833709: Please add the MIT/Expat license to common-licenses

[Josh Triplett]

On Mon, Aug 08, 2016 at 05:10:52PM +0100, Simon McVittie wrote:
> On Sun, 07 Aug 2016 at 21:00:12 -1000, Josh Triplett wrote:
> > Numerous packages use the MIT/Expat license, and currently all of those
> > packages need to include it in their copyright files.
> 
> Although Policy does not say so, the ftp-masters require the license
> grant to be quoted in the copyright file, even for common-licenses. [1][2]

Can't quote something that doesn't exist in the upstream source.

> For the Expat license and other simple licenses, the license grant *is*
> the license, so putting it in common-licenses would make no difference
> to the length or complexity of copyright files unless the ftp-masters
> were willing to change their policy to accept something like
> 
> Files: foo
> Copyright: © 2000 Mickey Mouse
> License: Expat
> 
> (or its non-machine-readable equivalent) without any further text.

I wouldn't suggest making it quite *that* concise, because that leaves
out a human-readable cross-reference.  I'd suggest an explicit
reference, like this:

Debian systems provide the MIT license in /usr/share/common-licenses/MIT

> However, for the specific case of the Expat license, if I'm reading the
> license correctly you are required to include the license grant with the
> (binary form of the) software. For compiled code, the copyright file is
> likely the most convenient way to achieve that.

If the upstream source just says:

license = "MIT"

then that should suffice.

> It would be great if Policy described what the ftp-masters actually
> require and why, so that maintainers could provide everything that Debian
> needs to avoid legal trouble but no more. At the moment, Policy is rather
> more vague than the actual requirements to get software into Debian; there
> seems to be some (unwritten?) policy based on ftp-master consensus.

Agreed.  I'd prefer a written policy, and preferably one that doesn't
introduce any unnecessary boilerplate.

- Josh Triplett

Bug#809611: d-i fails to boot on HP mv2120

[Martin Michlmayr]

Please add the following to the release-notes on armel in the upgrade
section:

HP mv2120

The default u-boot settings from HP no longer work with Debian 9.
Before you can upgrade to Debian 9, you have to change some settings
in the u-boot configuration.  The required changes are documented on
the [Debian on HP
mv2120](http://www.cyrius.com/debian/orion/hp/mv2120/uboot-config/)
page.

or if you don't want to link to an external page:

HP mv2120

The default u-boot settings from HP no longer work with Debian 9.
Before you can upgrade to Debian 9, you have to change some settings
in the u-boot configuration.

If you have serial console access to the mv2120, you can run some
commands in u-boot. Simply interrupt the boot process by pressing a
key and type the following:

setenv loadAddr 0x060
setenv bootcmd 'bootext2 0,1:1,2 0x060 /boot/uImage /dev/sda /dev/sdb'
saveenv

If you don't have a serial console, you can make the changes from
within Debian. Run the following commands:

   cat >/etc/fw_env.config 

Bug#833709: Please add the MIT/Expat license to common-licenses

[Josh Triplett]

On Mon, Aug 08, 2016 at 11:53:37AM -0700, Russ Allbery wrote:
> Josh Triplett  writes:
> 
> > Numerous packages use the MIT/Expat license, and currently all of those
> > packages need to include it in their copyright files.  I'd love to see
> > this license added to /usr/share/common-licenses/ ; this would require a
> > Policy change to section 12.5 to allow.
> 
> I don't think this is a good idea.  This license is extremely short, and
> it has a ton of minor variations, so we'll get a lot of people using it
> even though the exactly licensing terms of their package don't match the
> canonical copy.
> 
> For example, it's very common to see "THE AUTHORS" replaced with a
> specific list of people or organizations in the license, which is a very
> small change that's easy for someone to miss when they know that the terms
> are just the Expat terms.

In the various packages I looked at, I haven't seen any such variation
of the MIT/Expat license.  I've seen many variations of the MIT/X11
license, but not of Expat.

> I think the common-license infrastructure is designed for licenses that
> are small novels, like the GPL.  For something that's just three
> paragraphs, putting it directly in the copyright file has a simplicity and
> robustness that I think outweighs any minor one-time inconvenience during
> packaging or a bit of additional disk space usage.

For many of the packages I'd hoped to use it for, the sum total of the
license information in the upstream source consists of the following
line in the package metadata:

license = "MIT"

No copyright notices, no license file, just a simple statement of the
license name using canonical SPDX license identifiers.

For such packages, referencing a canonical copy of the license seems
preferable.

- Josh Triplett

Bug#809611: d-i fails to boot on HP mv2120

[Martin Michlmayr]

retitle 809611 armel: HP mv2120 requires change in u-boot setting
reassign 809611 release-notes
thanks

I documented the new settings here:
http://www.cyrius.com/debian/orion/hp/mv2120/uboot-config/

I emailed the hackingthemediavault and debian-arm mailing lists.

Since we cannot fix this in Debian, I'll reassign this bug to
release-notes where we should add a link to the configuration change.

-- 
Martin Michlmayr
http://www.cyrius.com/

Bug#816123: bug#22833: Bug#816123: guile-2.0-libs: guile-procedures.txt is actually port-dependent

[Rob Browning]

Rob Browning  writes:

> Andy Wingo  writes:
>
>> Confirmed.  I guess we could put this in libdir somehow.  I wonder if we
>> shouldn't take advantage of the opportunity to do something more
>> sensible and extensible... the easy thing to do would be to just keep
>> doing the same thing though.
>
> I suppose for Debian's guile-2.0, if it's not to complicated, I should
> see if I can move it to libdir.  Otherwise as described, /usr/share is
> isn't.

Perhaps I could move it to the %guile-build-info libdir, i.e. here
/usr/lib/x86_64-linux-gnu/guile/2.0/guile-procedures.txt and make sure
documentation-files includes that in its search list.

-- 
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#816123: bug#22833: Bug#816123: guile-2.0-libs: guile-procedures.txt is actually port-dependent

[Rob Browning]

Andy Wingo  writes:

> Confirmed.  I guess we could put this in libdir somehow.  I wonder if we
> shouldn't take advantage of the opportunity to do something more
> sensible and extensible... the easy thing to do would be to just keep
> doing the same thing though.

I suppose for Debian's guile-2.0, if it's not to complicated, I should
see if I can move it to libdir.  Otherwise as described, /usr/share is
isn't.

-- 
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#833599: debian-installer: choose-mirror segfaults

[Witold Baryluk]

Package: debian-installer
Followup-For: Bug #833599

Few more details.

I bissected the problem to start showing up in image

https://d-i.debian.org/daily-images/amd64/20160731-00:14/netboot/mini.iso


but not showing in


Comparing

https://d-i.debian.org/daily-images/amd64/20160731-00:14/build_netboot.log

and

https://d-i.debian.org/daily-images/amd64/20160801-00:15/build_netboot.log

with lines Unpacking I see this diff only:

$ grep Unpacking build_netboot.log  > /tmp/a1
$ grep Unpacking build_netboot.log.1  > /tmp/a2
$ diff /tmp/a1  /tmp/a2 
12,13c12,13
< Unpacking choose-mirror-bin (2.70) ...
< Unpacking choose-mirror (2.70) ...
---
> Unpacking choose-mirror-bin (2.69) ...
> Unpacking choose-mirror (2.69) ...
92c92
< Unpacking wpasupplicant-udeb (2.5-1) ...
---
> Unpacking wpasupplicant-udeb (2.3-2.4) ...


Which is strange. As the 2.70 only contains translation fixes.

But it is possible that the compiler used or libc used was different than
previously, which somehow manifests here.

Bug#831335: jessie-pu: package publicsuffix/20160703-1

[Daniel Kahn Gillmor]

On Mon 2016-08-08 18:51:32 -0400, Daniel Kahn Gillmor wrote:
> On Sat 2016-08-06 17:15:25 -0400, Adam D. Barratt wrote:
>> Thanks; please feel free to upload that, with a small tweak:
>>
>> +publicsuffix (20160703-0+deb8u1) stable; urgency=medium
>> +
>> +  * prepare for stable-proposed-updates.
>>
>> "jessie" is generally preferred as the changelog distribution and maybe
>> "Upload to stable" or something similar?
>
> changed and uploaded (as a source-only upload; please let me know if
> that causes trouble; i always prefer to do source-only uploads where the
> build infrastructure supports it)

hm, it looks like jessie can't handle source-only uploads that generate
arch-indep packages, according to the rejection notice i just got.

That's a shame.  I guess i'll try again and include the arch-indep
binary in my upload.  Is there any chance that the jessie builders can
learn to handle such a thing or is that just for unstable?

--dkg


signature.asc
Description: PGP signature

Bug#831335: jessie-pu: package publicsuffix/20160703-1

[Daniel Kahn Gillmor]

On Sat 2016-08-06 17:15:25 -0400, Adam D. Barratt wrote:
> Thanks; please feel free to upload that, with a small tweak:
>
> +publicsuffix (20160703-0+deb8u1) stable; urgency=medium
> +
> +  * prepare for stable-proposed-updates.
>
> "jessie" is generally preferred as the changelog distribution and maybe
> "Upload to stable" or something similar?

changed and uploaded (as a source-only upload; please let me know if
that causes trouble; i always prefer to do source-only uploads where the
build infrastructure supports it)

>> The git tree's jessie branch which i'm proposing is at commit ID
>> 6520ee81d3e2d73192e67685652ef6bccdb2e637, fwiw, so you don't have to
>> worry about it changing.
>
> Thanks for that, but we'd still prefer p-u bug reports to be
> free-standing.

no problem, just providing multiple ways to access the data.

> Every couple of months is when we aim (not always successfully) to do a
> stable point release, so that hopefully works out well all around.

I've never maintained this class of package before.  do i just do
regular uploads to "jessie" as new versions of the package become
available, or do i need to do a jessie-pu bug report for each one?

   --dkg


signature.asc
Description: PGP signature

Bug#831228: flashplugin-nonfree: Signature status

[Elliott Mitchell]

Sorry to be the bearer of bad news, but:

$ wget 
https://people.debian.org/~bartm/flashplugin-nonfree/D5C0FC14/fp.22.0.0.209.sha512.amd64.pgp.asc
--2016-08-08 16:48:41--  
https://people.debian.org/~bartm/flashplugin-nonfree/D5C0FC14/fp.22.0.0.209.sha512.amd64.pgp.asc
Resolving people.debian.org (people.debian.org)... 5.153.231.30, 
2001:41c8:1000:21::21:30
Connecting to people.debian.org (people.debian.org)|5.153.231.30|:443... 
connected.
HTTP request sent, awaiting response... 404 Not Found
2016-08-08 16:48:41 ERROR 404: Not Found.

$ 

While alas the signature at 
http://people.debian.org/~bartm/flashplugin-nonfree/D5C0FC14/fp10.sha512.amd64.pgp.asc
is still the one for 11.2.202.632.  Seems the webserver or 
isn't working quite the way you expected.


-- 
(\___(\___(\__  --=> 8-) EHM <=--  __/)___/)___/)
 \BS (| ehem+sig...@m5p.com  PGP 87145445 |)   /
  \_CS\   |  _  -O #include  O-   _  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445

Bug#815319: Fix for upgrade process

[Lucas Castro]

I got the same issue,
I've been analyzing the init script and noticed that
nothing will be executed if no interfaces network is set to INTERFACES
variables
in /etc/default/isc-dhcp-server.

I've created to variables in /etc/default/isc-dhcp-server, DHCPDv4 and
DHCPDv6
and checked for true|false and then call the related command for each
variable if its enabled.

I don't think a good idea relies on setting the network interfaces for
INTERFACES variables,
because the service don't do that, it just run on the subnet that found
in config file,
if the user decided to do that he can, but it's not essential.
--- isc-dhcp-server	2016-08-08 19:11:30.639671000 -0300
+++ /etc/init.d/isc-dhcp-server	2016-08-08 19:48:57.047671000 -0300
@@ -95,7 +95,7 @@
 	DESC="$5"
 
 	shift 5
-	INTERFACES="$*"
+	#INTERFACES="$*"
 
 	test_config "$VERSION" "$CONF"
 	log_daemon_msg "Starting $DESC" "$NAME"
@@ -146,10 +146,16 @@
 		if test -n "$INTERFACESv4"; then
 			start_daemon "-4" "$DHCPDv4_CONF" "$NAME4" \
 "$DHCPDv4_PID" "$DESC4" "$INTERFACESv4"
+		else
+			start_daemon "-4" "$DHCPDv4_CONF" "$NAME4" \
+"$DHCPDv4_PID" "$DESC4" "$INTERFACESv4"
 		fi
 		if test -n "$INTERFACESv6"; then
 			start_daemon "-6" "$DHCPDv6_CONF" "$NAME6" \
 "$DHCPDv6_PID" "$DESC6" "$INTERFACESv6"
+		else
+			start_daemon "-6" "$DHCPDv6_CONF" "$NAME6" \
+"$DHCPDv6_PID" "$DESC6" "$INTERFACESv6"
 		fi
 		;;
 	stop)
@@ -170,6 +176,9 @@
 		if test -n "$INTERFACESv4"; then
 			echo -n "Status of $DESC4: "
 			check_status -v $DHCPDv4_PID $NAME4 || exit $?
+		else
+			echo -n "Status of $DESC4: "
+			check_status -v $DHCPDv4_PID $NAME4 || exit $?
 		fi
 		if test -n "$INTERFACESv6"; then
 			echo -n "Status of $DESC6: "
--- isc-dhcp-server	2016-08-08 19:11:30.639671000 -0300
+++ /etc/init.d/isc-dhcp-server	2016-08-08 20:22:18.879671000 -0300
@@ -95,7 +95,7 @@
 	DESC="$5"
 
 	shift 5
-	INTERFACES="$*"
+	#INTERFACES="$*"
 
 	test_config "$VERSION" "$CONF"
 	log_daemon_msg "Starting $DESC" "$NAME"
@@ -137,17 +137,12 @@
 
 case "$1" in
 	start)
-		if test -n "$INTERFACES" -a -z "$INTERFACESv4"; then
-echo "DHCPv4 interfaces are no longer set by the INTERFACES variable in" >&2
-echo "/etc/default/isc-dhcp-server.  Please use INTERFACESv4 instead." >&2
-echo "Migrating automatically for now, but this will go away in the future." >&2
-INTERFACESv4="$INTERFACES"
-		fi
-		if test -n "$INTERFACESv4"; then
+		if [ $DHCPD_ENABLED = true ]; then
 			start_daemon "-4" "$DHCPDv4_CONF" "$NAME4" \
 "$DHCPDv4_PID" "$DESC4" "$INTERFACESv4"
 		fi
-		if test -n "$INTERFACESv6"; then
+		if [ $DHCPDv6_ENABLED = true ]; then
+			log_progress_msg "dhcpd" "dhcpdv6 is enabled";
 			start_daemon "-6" "$DHCPDv6_CONF" "$NAME6" \
 "$DHCPDv6_PID" "$DESC6" "$INTERFACESv6"
 		fi
@@ -164,14 +159,11 @@
 		fi
 		;;
 	status)
-		if test -n "$INTERFACES" -a -z "$INTERFACESv4"; then
-INTERFACESv4="$INTERFACES"
-		fi
-		if test -n "$INTERFACESv4"; then
+		if [ $DHCPDv4_ENABLED = true ]; then 
 			echo -n "Status of $DESC4: "
 			check_status -v $DHCPDv4_PID $NAME4 || exit $?
 		fi
-		if test -n "$INTERFACESv6"; then
+		if [ $DHCPDv6_ENABLED = true ]; then
 			echo -n "Status of $DESC6: "
 			check_status -v $DHCPDv6_PID $NAME6 || exit $?
 		fi


signature.asc
Description: OpenPGP digital signature

Bug#833423: [Aptitude-devel] Bug#833423: aptitude says packages are broken just because we didn't upgrade to our target (experimental)?

[Axel Beckert]

Hi Dan,

積丹尼 Dan Jacobson wrote:
> AB> If so, please save that state with aptitude-create-state-bundle,
> AB> upload the file (around 100 MB) somewhere and post the link here.
> 
> Even though it turns out to be only 37MB,

Depends on the amount of entries in /etc/apt/sources.list

> but its contents are overkill for the problem at hand.

Depends. If you want us to reproduce the issue, that tar ball contains
all of your environment to start aptitude with the very same
environment. That's the only purpose of aptitude-create-state-bundle,
but sending less doesn't allow us to start aptitude in exactly the
same environment.

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

Bug#829046: Status of pagure

[Sergio Durigan Junior]

On Sunday, August 07 2016, Ben Finney wrote:

> On 29-Jul-2016, Sergio Durigan Junior wrote:
>
>> Thanks for the help! I'll send you an e-mail as soon as I set up a
>> repository.
>
> I would also like to be able to contribute to maintenance of Pagure in
> Debian.
>
> Can you post an update to this bug report for how volunteers can help:
> repository (at Alioth?), discussion mailing list, etc.

OK, so here's a more detailed update.

I've advanced quite a bit in the packaging, but there are still some
things to do.

I'm using a temporary repository to push what I've done so far; it's
good because I can overwrite history if needed.  The URL is:

  

Eventually I'll move everything to collab-maint/pagure, which should be
the official repository anyway.

All the Python dependencies have finally been packaged, which is good
because I can fully build the package now.  However, there are still
some JavaScript libraries that are (a) not being shipped on Debian, and
(b) bundled in their minified version inside pagure.  This is bad, so my
next task is to package those libraries for Debian.  You can take a look
at them by going to the pagure/static directory on the source tree.

I decided to follow what Fedora does and split the package into several
subpackages.  The first one, pagure, should contain the core
functionality and work out-of-the-box.  Then, the user will also have
the possibility to install:

 - pagure-milters, which takes care of allowing users to comment on
   tickets/pull-requests by e-mail (instead of going to the web
   interface).  This package in specific also has a "problem": it
   depends on postfix to work properly, which is not good because Debian
   ships exim4 as the default MTA.  I've also been investigating how to
   use milters with exim4, and I *may* have a solution.

 - pagure-ev-server, which allows live refreshing of a page when someone
   is viewing it.

 - pagure-webhook-server, which sends notifications to third-party
   services (like fedmsg) using POST http reqs.

There's also the pagure-doc package.

I ran the full testsuite and found a few errors on Debian.  I'm in
constant communication with upstream, so they are aware and I should
send some patches in the next days.

I still have this TODO list:

 - Package missing JS libraries

 - Send patch upstream to use python-bcrypt instead of py-bcrypt to hash
   passwords

 - Take care of d/copyright

 - Correctly fill d/pagure-doc.doc-base

 - Review the *.init scripts and make sure they work

 - Review the *.postinst scripts and make sure they work

 - Write *.postrm scripts

 - Decide whether to run pagure-milters as user/group postfix.  Maybe
   decide that based on what the user is using as MTA, and change it
   accordingly on pagure-milters.postinst.  Same applies for
   pagure-milters.tmpfile.

 - Maybe include more systemd security features on *.service files.

 - Fix some lintian warnings/errors that I've seen

Well, that's it.  I think I should be able to finish everything by the
end of the week, and then move to the sponsorship phase :-).

Cheers,

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


signature.asc
Description: PGP signature

Bug#833423: [Aptitude-devel] Bug#833423: aptitude says packages are broken just because we didn't upgrade to our target (experimental)?

[積丹尼 Dan Jacobson]

AB> If so, please save that state with aptitude-create-state-bundle,
AB> upload the file (around 100 MB) somewhere and post the link here.

Even though it turns out to be only 37MB, but its contents are overkill
for the problem at hand.

Bug#833423: [Aptitude-devel] Bug#833423: aptitude says packages are broken just because we didn't upgrade to our target (experimental)?

[積丹尼 Dan Jacobson]

> "AB" == Axel Beckert  writes:

AB> If so, please save that state with aptitude-create-state-bundle,
AB> upload the file (around 100 MB) somewhere and post the link here.

That would take long on my 2MB/64K connection.

Have this script instead



f.gz
Description: application/gzip

Bug#833423: aptitude says packages are broken just because we didn't upgrade to our target (experimental)?

[積丹尼 Dan Jacobson]

> "MAFM" == Manuel A Fernandez Montecelo  
> writes:

MAFM> Do you still have the system in that state?  What does "why" say for
MAFM> those packages?

# aptitude why perl-doc |wc
   8963   39931  531886


w.gz
Description: application/gzip

Bug#833654: gold in binutils-2.27 fails to build on mips* targets

[Aurelien Jarno]

control: tag -1 + patch
control: tag -1 + upstream

On 2016-08-07 16:31, Matthias Klose wrote:
> Package: src:binutils
> Version: 2.27-1
> Severity: important
> Tags: sid stretch
> 
> gold fails to link, see at least
> https://buildd.debian.org/status/fetch.php?pkg=binutils=all=2.27-1=1470579877


I have sent a patch on the upstream mailing list:
https://sourceware.org/ml/binutils/2016-08/msg00048.html

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#833822: ITP: sagetex -- LaTeX package for Sage

[Jerome Benoit]

Package: wnpp
Severity: wishlist
Owner: Jerome Benoit 

* Package name: sagetex
  Version : 3.0
  Upstream Author : Dan Drake 
* URL : https://github.com/dandrake/sagetex
* License : GPL-2+, CC-BY-SA-3.0
  Programming Lang: TeX, Python
  Description : LaTeX package for Sage


The SageTex LaTeX package allows you to embed code, results of computations,
and plots from Sage[Math] into LaTeX documents; Sage[Math] is a Computer
Algebra System (CAS) .

Bug#833821: ticket filed

[meejah]

Yes, Petter is absolutely correct that the code is wrong. I have filed a
ticket in txtorcon, see https://github.com/meejah/txtorcon/issues/179

Thanks!

-- 
meejah

Bug#743662: wmweather has no option to turn off metric

[Joey Morris]

I like the patch adding an imperial option, and it's unclear why it hasn't been
merged. Alternatively, because the metric option cannot be overridden, it could
be removed from the system-wide wmweather.conf. Users who wish to see metric
units would then add the option to their personal config file.

Bug#833821: txtorcon: Should age() use an old new timestamp?

[Petter Reinholdtsen]

Package: txtorcon
Version: 0.15.0-1
Tags: patch

I noticed this issue because the package fail to build reproducably, and
sphinx generate documentation where the now statement below is replaced
with a concrete timestamp.  See  for the details about this.

But while looking at the code, it occured to me that it probably is not
working as the author intended.  If I remember correctly (based on a
blog post from Chris Lamb[1]), the default function arguments in Python
are evaluated when the code is parsed (ie when the 'import' statements
are evaluated).  The effect of this is that the age() function is not
give a fresh new timestamp generated at call time, but the timestamp
generated when the file was imported.

 [1] https://chris-lamb.co.uk/posts/python-quirk-signatures-are-evaluated-import-time
 >

I suspect the author wanted fresh timestamp, and suggest to rewrite the
age() function like this to make sure age() without any now value
specified actually uses a fresh timestamp:

diff --git a/txtorcon/circuit.py b/txtorcon/circuit.py
index 5166fc1..cd9a3cf 100644
--- a/txtorcon/circuit.py
+++ b/txtorcon/circuit.py
@@ -157,7 +157,7 @@ class Circuit(object):
 d.addCallback(close_command_is_queued)
 return self._closing_deferred
 
-def age(self, now=datetime.datetime.utcnow()):
+def age(self, now=None):
 """
 Returns an integer which is the difference in seconds from
 'now' to when this circuit was created.
@@ -166,6 +166,8 @@ class Circuit(object):
 """
 if not self.time_created:
 return None
+if now == None:
+now = datetime.datetime.utcnow()
 return (now - self.time_created).seconds
 
 def _create_flags(self, kw):

-- 
Happy hacking
Petter Reinholdtsen

Bug#833820: sphinx: Avoid evaulating default function arguments when including them in the documentation

[Petter Reinholdtsen]

Source: sphinx
Version: 1.3.6-2
Severity: wishlist
User: reproducible-bui...@lists.alioth.debian.org
Usertags: toolchain
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi.  The documentation generated by sphinx expands default python
arguments instead of reproducing the values listed in the source.  This
is related to the reproducability issues reported in
https://bugs.debian.org/795976 > and
https://bugs.debian.org/822197 >, but seem to be a different issue
from those solved there.

I discovered this from
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/txtorcon.html
 >
which report this difference in the generated documentation
(txtorcon-state.txt):

@@ -385,15 +385,15 @@
   Returns:
  Deferred which callbacks with this Circuit instance
 
   ONLY after Tor has confirmed it is gone (not simply that the
   CLOSECIRCUIT command has been queued). This could be a while if
   you included IfUnused.
 
-   age(now=datetime.datetime(2016, 8, 5, 7, 33, 8, 845335))
+   age(now=datetime.datetime(2017, 9, 7, 13, 58, 10, 541674))
 
   Returns an integer which is the difference in seconds from 'now'
   to when this circuit was created.
 
   Returns None if there is no created-time.
 
update(args)

This documentation is generated from this function definition in
txtorcon/circuit.py in the source:

def age(self, now=datetime.datetime.utcnow()):
"""
Returns an integer which is the difference in seconds from
'now' to when this circuit was created.

Returns None if there is no created-time.
"""

Notice how the now argument is supposed to be a dynamic function call to
datetime.datetime.utcnow(), and not a fixed timestamp as the
documentation could lead you to believe.

Please change sphinx to correctly report the arguments used by this age
function.  It would have the side effect of making the txtorcon build
reproducable.

-- 
Happy hacking
Petter Reinholdtsen

Bug#831469: brp-pacu has a new version

[Jaromír Mikeš]

Hi,

This new version only fixing build on Mac 64bit ... no other changes in code.
There is no need to update :(

best regards

mira

Bug#833679: BitPaddedInt import error

[mike winsor]

compatid3 mutagen.id3 ImportError: cannot import name BitPaddedInt

puddletag and  picard same error , Quod Libet and Ex Falso both load, run OK


puddletag
Traceback (most recent call last):
  File "/usr/bin/puddletag", line 328, in 
migrate_settings()
  File "/usr/bin/puddletag", line 86, in migrate_settings
_migrate_action_shortcuts()
  File "/usr/bin/puddletag", line 92, in _migrate_action_shortcuts
from puddlestuff.puddleobjects import PuddleConfig
  File "/usr/lib/python2.7/dist-packages/puddlestuff/puddleobjects.py",
line 17, in 
import audioinfo
  File
"/usr/lib/python2.7/dist-packages/puddlestuff/audioinfo/__init__.py", line
104, in 
import id3, vorbis, apev2, mp4
  File "/usr/lib/python2.7/dist-packages/puddlestuff/audioinfo/id3.py",
line 19, in 
from _compatid3 import CompatID3
  File
"/usr/lib/python2.7/dist-packages/puddlestuff/audioinfo/_compatid3.py",
line 25, in 
from mutagen.id3 import ID3, Frame, Frames, Frames_2_2, TextFrame,
TORY, \
ImportError: cannot import name BitPaddedInt

 picard
Traceback (most recent call last):
  File "/usr/bin/picard", line 2, in 
from picard.tagger import main; main('/usr/share/locale', True)
  File "/usr/lib/picard/picard/tagger.py", line 65, in 
from picard.formats import open as open_file
  File "/usr/lib/picard/picard/formats/__init__.py", line 157, in 
from picard.formats.id3 import (
  File "/usr/lib/picard/picard/formats/id3.py", line 30, in 
from picard.formats.mutagenext import compatid3
  File "/usr/lib/picard/picard/formats/mutagenext/compatid3.py", line 25,
in 
from mutagen.id3 import ID3, Frames, Frames_2_2, TextFrame, TORY, \
ImportError: cannot import name BitPaddedInt

Warning i am not a programmer, but i would like to help, if your requests
for me are easy to copy into my Terminal.

Bug#811576: patch

[Mike Gerow]

Added header to patch refrencing the trousers mailing list posting.

-- 
Mike Gerow
ge...@google.com
diff -Nru tpm-tools-1.3.8/debian/changelog tpm-tools-1.3.8/debian/changelog
--- tpm-tools-1.3.8/debian/changelog	2015-06-28 03:15:23.0 -0700
+++ tpm-tools-1.3.8/debian/changelog	2016-07-04 07:49:41.0 -0700
@@ -1,3 +1,11 @@
+tpm-tools (1.3.8-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix confusing indentation in tpm_present.c that fails build with GCC 6
+(Closes: #811576).
+
+ -- Mike Gerow   Mon, 04 Jul 2016 16:49:41 +0200
+
 tpm-tools (1.3.8-2) unstable; urgency=medium
 
   * Add patch 03 to fix FTBFS with gcc-5 (Closes: #778147)
diff -Nru tpm-tools-1.3.8/debian/patches/05-fix-FTBFS-gcc-6.patch tpm-tools-1.3.8/debian/patches/05-fix-FTBFS-gcc-6.patch
--- tpm-tools-1.3.8/debian/patches/05-fix-FTBFS-gcc-6.patch	1969-12-31 16:00:00.0 -0800
+++ tpm-tools-1.3.8/debian/patches/05-fix-FTBFS-gcc-6.patch	2016-07-04 07:49:41.0 -0700
@@ -0,0 +1,24 @@
+Description: Fix FTBFS with GCC 6 due to confusing indentation
+Author: Mike Gerow 
+Bug: https://sourceforge.net/p/trousers/mailman/message/35261553/
+--- a/src/tpm_mgmt/tpm_present.c
 b/src/tpm_mgmt/tpm_present.c
+@@ -349,13 +349,13 @@
+ 		}
+ 	} while (flags[++i].name);
+ 
+-  out_success:
++out_success:
+ 	logSuccess(argv[0]);
+ 	iRc = 0;
+-  out_close:
++out_close:
+ 	contextClose(hContext);
+-  out:
+-if (szTpmPasswd && !isWellKnown)
+-	shredPasswd( szTpmPasswd );
++out:
++	if (szTpmPasswd && !isWellKnown)
++		shredPasswd( szTpmPasswd );
+ 	return iRc;
+ }
diff -Nru tpm-tools-1.3.8/debian/patches/series tpm-tools-1.3.8/debian/patches/series
--- tpm-tools-1.3.8/debian/patches/series	2015-06-28 03:11:26.0 -0700
+++ tpm-tools-1.3.8/debian/patches/series	2016-07-04 07:49:41.0 -0700
@@ -2,3 +2,4 @@
 02-cflags-errors-unused.patch
 03-fix-bool-error-parseStringWithValues.patch
 04-fix-FTBFS-clang.patch
+05-fix-FTBFS-gcc-6.patch


signature.asc
Description: Digital signature

Bug#833745: [Pkg-libvirt-maintainers] Bug#833745: libvirt-daemon-system: Please use SIGUSR1 to restart virtlockd and virtlogd on upgrade

[Laurent Bigonville]

Le 08/08/16 à 18:59, Guido Günther a écrit :

We should be doing this for virtlockd already since ages, we have:

   dh_systemd_start -p libvirt-daemon-system --no-restart-on-upgrade 
libvirt-guests.service virtlockd.socket virtlockd.service

so this should work. virtlogd is indeed missing. Do you have a log of
the virtlockd restart?
Looking at /var/lib/dpkg/info/libvirt-daemon-system.postinst, virtlockd 
is not restarted or reloaded at all, only started the first time:


# End automatically added section
# Automatically added by dh_systemd_start
if [ -d /run/systemd/system ]; then
systemctl --system daemon-reload >/dev/null || true
if [ -n "$2" ]; then
_dh_action=try-restart
else
_dh_action=start
fi
deb-systemd-invoke $_dh_action virtlockd.socket >/dev/null || true
fi
# End automatically added section
# Automatically added by dh_systemd_start
if [ -d /run/systemd/system ]; then
systemctl --system daemon-reload >/dev/null || true
deb-systemd-invoke start virtlockd.service virtlockd.socket >/dev/null 
|| true
fi

Bug#833819: n2n: please make the build reproducible

[Chris Lamb]

Source: n2n
Version: 1.3.1~svn3789-5
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

Whilst working on the "reproducible builds" effort [0], we noticed
that n2n could not be built reproducibly.

Patch attached.

 [0] https://wiki.debian.org/ReproducibleBuilds


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/patches/02-reproducible-build.diff 1970-01-01 01:00:00.0 
+0100
--- b/debian/patches/02-reproducible-build.diff 2016-08-08 23:39:02.090124318 
+0100
@@ -0,0 +1,18 @@
+Description: Make the build reproducible
+Author: Chris Lamb 
+Last-Update: 2016-08-08
+
+--- n2n-1.3.1~svn3789.orig/Makefile
 n2n-1.3.1~svn3789/Makefile
+@@ -57,7 +57,11 @@ $(N2N_LIB): $(N2N_OBJS)
+ version.c:
+   @echo $(N2N_VERSION) | sed -e 's/.*/const char * version   = "&";/' > 
version.c
+   @uname -p | sed -e 's/.*/const char * osName= "&";/' >> version.c
++ifdef SOURCE_DATE_EPOCH
++  @LC_ALL=C date --utc --date="@$(SOURCE_DATE_EPOCH)" +"%D %r" | sed -e 
's/.*/const char * buildDate = "&";/' >> version.c
++else
+   @date +"%D %r" | sed -e 's/.*/const char * buildDate = "&";/' >> 
version.c
++endif
+ 
+ clean:
+   rm -rf $(N2N_OBJS) $(N2N_LIB) $(APPS) $(DOCS) *.dSYM *~ version.c
--- a/debian/patches/series 2016-08-08 23:36:03.288651222 +0100
--- b/debian/patches/series 2016-08-08 23:40:33.494871046 +0100
@@ -1,3 +1,4 @@
 01-edge.8.diff
 upstream-svn4235.patch
 makefile.patch
+02-reproducible-build.diff

Bug#833818: dnssec-trigger: please make the build reproducible

[Chris Lamb]

Source: dnssec-trigger
Version: 0.13~svn685-5
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

Whilst working on the "reproducible builds" effort [0], we noticed
that dnssec-trigger could not be built reproducibly.

Patch attached.

 [0] https://wiki.debian.org/ReproducibleBuilds


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/patches/reproducible-build.patch   1970-01-01 01:00:00.0 
+0100
--- b/debian/patches/reproducible-build.patch   2016-08-08 23:33:50.479553264 
+0100
@@ -0,0 +1,23 @@
+Description: Make the build reproducible
+Author: Chris Lamb 
+Last-Update: 2016-08-08
+
+--- dnssec-trigger-0.13~svn685.orig/Makefile.in
 dnssec-trigger-0.13~svn685/Makefile.in
+@@ -54,7 +54,7 @@ pidfile=@pidfile@
+ login_command=@login_command@
+ login_location=@login_location@
+ unbound_control_path=@unbound_control_path@
+-DATE=$(shell date +%F -r $(srcdir)/Changelog)
++DATE=$(shell date -u +%F -r $(srcdir)/Changelog)
+ 
+ do_subst = sed -e 's,[@]SHELL[@],$(SHELL),g' \
+  -e 's,[@]PACKAGE[@],$(PACKAGE),g' \
+@@ -96,7 +96,6 @@ LIBOBJS=@LIBOBJS@
+ RUNTIME_PATH=@RUNTIME_PATH@
+ DEPFLAG=@DEPFLAG@
+ EXPORT_DYNAMIC=@EXPORT_DYNAMIC@
+-DATE=$(shell date +%Y%m%d)
+ BUILD=build/
+ 
+ WINDRES=@WINDRES@
--- a/debian/patches/series 2016-08-08 23:09:05.211264776 +0100
--- b/debian/patches/series 2016-08-08 23:22:49.654088164 +0100
@@ -4,3 +4,4 @@
 strip-version-number-from-config.patch
 fix-desktop-file-dirs.patch
 dnssec-trigger-nm-1.1.90.patch
+reproducible-build.patch
--- a/debian/rules  2016-08-08 23:09:05.211264776 +0100
--- b/debian/rules  2016-08-08 23:34:02.875655750 +0100
@@ -9,6 +9,8 @@
 export DEB_CFLAGS_MAINT_APPEND  = -Wall -pedantic -g -pipe $(if $(findstring 
noopt,$(DEB_BUILD_OPTIONS)),-O0,-O2)
 export DEB_LDFLAGS_MAINT_APPEND = -Wl,-z,defs -Wl,--as-needed
 
+export SHELL = /bin/sh
+
 %:
dh $@ --with autoreconf,systemd,python2
 

Bug#729924: Default to Python3 builds, add Python2 variants

[James McCoy]

On Sun, Apr 24, 2016 at 12:19:01AM -0400, James McCoy wrote:
> On Wed, Apr 06, 2016 at 12:21:33PM +0200, Matthias Klose wrote:
> > please find attached a debdiff which builds with Python3 as the default, and
> > adds Python2 variants as extra packages.
> 
> I understand the desire to have Python3 support, but I'm not keen on
> creating separate Python2 and Python3 packages.
> 
> From an initial look, it seems like the only packaged addons that
> require Python support both 2 & 3.  Maybe it's time to just switch to
> Python3.

If there are no objections, I'm going to make this change in the next
upload.

> I guess the sooner that happens before the release, the more
> chance there is for people to complain about broken stuff.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#833536: pkg-haskell-tools: dht should allow uploading by FTP

[Sean Whitton]

On Fri, Aug 05, 2016 at 07:19:47PM -0400, Joachim Breitner wrote:
> With "someone" I meant me, not you: "dht upload" should just call dput,
> and I should be able to tell dput to use ssh-upload by default.

Oh, I see.

I'm inclined to agree with Sven that dht should default to SSH because
DDs often use it to make huge numbers of uploads, and it would be a pain
to sort it out if some of them failed.

I think I'm the only active DM on DHT so I'll put this bug on my todo list!

-- 
Sean Whitton

Bug#833779: devscripts: [uscan] please strip whitespace in href when matching URLs

[James McCoy]

On Mon, Aug 08, 2016 at 11:40:39AM -0400, Daniel Kahn Gillmor wrote:
> the HTML there is decidedly weird, with extra whitespace in the href:
> 
> -
>  sks-1.1.6.tgz
> 
> -
> 
> So uscan isn't able to find it.
> 
> I reported the issue to bitbucket:
> 
> https://bitbucket.org/site/master/issues/13130/downloads-page-has-spurious-whitespace
> 
> and got this response on IRC (#bitbucket on freenode):
> 
> 11:29 <+dwfreed> dkg: browsers ignore the whitespace
> 11:30 <+dwfreed> URLs can't have spaces in them anyway, which is what the 
> field is
> 11:30 <+dwfreed> it must be encoded, either as + or %20
> 11:30 <+dwfreed> so teach the tracker to adhere to the spec

Referencing the HTML spec[0], the value of the href attribute is a
"valid URL potentially surrounded by spaces", so uscan does indeed need
to be fixed.

[0]: https://www.w3.org/TR/html5/links.html#links-created-by-a-and-area-elements

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#833817: kido: FTBFS on non-x86 architectures due to hard-wired compiler flags

[John Paul Adrian Glaubitz]

Source: kido
Version: 0.1.0+dfsg-1
Severity: important

Hello!

Your package fails to build from source on all non-x86 architectures because the
build system hard-wires the compiler flags to use x86-specific flags like 
"-msse2":

[  0%] Building CXX object kido/CMakeFiles/kido.dir/common/Console.cpp.o
cd /<>/kido-0.1.0+dfsg/build/kido && /usr/bin/c++   
-DBOOST_TEST_DYN_LINK -DHAVE_BULLET_COLLISION -Dkido_EXPORTS 
-I/<>/kido-0.1.0+dfsg -isystem /usr/include/eigen3 -isystem 
/usr/include/bullet -I/<>/kido-0.1.0+dfsg/build  -Wall -msse2 -fPIC 
-std=c++11 -g -O2 -fdebug-prefix-map=/<>/kido-0.1.0+dfsg=. -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC   -I/usr/include/bullet -o 
CMakeFiles/kido.dir/common/Console.cpp.o -c 
/<>/kido-0.1.0+dfsg/kido/common/Console.cpp
c++: error: unrecognized command line option '-msse2'
kido/CMakeFiles/kido.dir/build.make:65: recipe for target 
'kido/CMakeFiles/kido.dir/common/Console.cpp.o' failed
make[4]: *** [kido/CMakeFiles/kido.dir/common/Console.cpp.o] Error 1

Please modify the CFLAGS used to make your package build on all architectures!

Full build log available in [1].

Thanks!
Adrian

> [1] 
> https://buildd.debian.org/status/fetch.php?pkg=kido=sparc64=0.1.0%2Bdfsg-1=1470693049

--
 .''`.  John Paul Adrian Glaubitz
 : :' :  Debian Developer - glaub...@debian.org
 `. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
   `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#833785: apt: please add configuration option to never allow installation of unauthenticated packages

[Chris Lamb]

Hi,

> I've heard this is a blocker for wider Debian adoption by some > 
> people/projects/organisations.

I would be very interested to know more.

Have they considered simply patching apt? The patch (attached) is
somewhat trivial.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/apt-private/private-download.cc b/apt-private/private-download.cc
index 4ffe78b..b1ad307 100644
--- a/apt-private/private-download.cc
+++ b/apt-private/private-download.cc
@@ -41,42 +41,7 @@ bool CheckAuth(pkgAcquire& Fetcher, bool const PromptUser)
   if (!(*I)->IsTrusted())
 UntrustedList.push_back((*I)->ShortDesc());
 
-   if (UntrustedList.empty())
-  return true;
-
-   return AuthPrompt(UntrustedList, PromptUser);
-}
-   /*}}}*/
-bool AuthPrompt(std::vector const , bool const 
PromptUser)/*{{{*/
-{
-   ShowList(c2out,_("WARNING: The following packages cannot be 
authenticated!"), UntrustedList,
-[](std::string const&) { return true; },
-[](std::string const) { return str; },
-[](std::string const&) { return ""; });
-
-   if (_config->FindB("APT::Get::AllowUnauthenticated",false) == true)
-   {
-  c2out << _("Authentication warning overridden.\n");
-  return true;
-   }
-
-   if (PromptUser == false)
-  return _error->Error(_("Some packages could not be authenticated"));
-
-   if (_config->FindI("quiet",0) < 2
-   && _config->FindB("APT::Get::Assume-Yes",false) == false)
-   {
-  if (!YnPrompt(_("Install these packages without verification?"), false))
- return _error->Error(_("Some packages could not be authenticated"));
-
-  return true;
-   }
-   else if (_config->FindB("APT::Get::Force-Yes",false) == true) {
-  _error->Warning(_("--force-yes is deprecated, use one of the options 
starting with --allow instead."));
-  return true;
-   }
-
-   return _error->Error(_("There were unauthenticated packages and -y was used 
without --allow-unauthenticated"));
+   return UntrustedList.empty();
 }
/*}}}*/
 bool AcquireRun(pkgAcquire , int const PulseInterval, bool * const 
Failure, bool * const TransientNetworkFailure)/*{{{*/
diff --git a/apt-private/private-download.h b/apt-private/private-download.h
index d829e8b..4358af8 100644
--- a/apt-private/private-download.h
+++ b/apt-private/private-download.h
@@ -12,10 +12,6 @@
 // Check if all files in the fetcher are authenticated
 bool CheckAuth(pkgAcquire& Fetcher, bool const PromptUser);
 
-// show a authentication warning prompt and return true if the system
-// should continue
-bool AuthPrompt(std::vector const , bool const 
PromptUser);
-
 APT_PUBLIC bool AcquireRun(pkgAcquire , int const PulseInterval, bool 
* const Failure, bool * const TransientNetworkFailure);
 
 bool CheckFreeSpaceBeforeDownload(std::string const , unsigned long long 
FetchBytes);
diff --git a/apt-private/private-source.cc b/apt-private/private-source.cc
index fab1b45..47ece7f 100644
--- a/apt-private/private-source.cc
+++ b/apt-private/private-source.cc
@@ -485,7 +485,7 @@ bool DoSource(CommandLine )
}
 
// check authentication status of the source as well
-   if (UntrustedList.empty() == false && AuthPrompt(UntrustedList, false) == 
false)
+   if (UntrustedList.empty() == false)
   return false;
 
// Run it

Bug#833815: qmhandle: FTBFS when built with dpkg-buildpackage -A (binary build with no binary artifacts)

[Santiago Vila]

tags 833815 + patch
thanks

Hi.

In addition to this failure, targets build-arch and build-indep are
now mandatory. The attached patch should fix both this bug and the missing
build-* targets.

Thanks.--- a/debian/rules
+++ b/debian/rules
@@ -7,6 +7,8 @@
 
 # This is the debhelper compatability version to use.
 
+build-arch: build
+build-indep: build
 build: build-stamp
 build-stamp:
dh_testdir
@@ -33,12 +35,12 @@ install: build
install -m755 qmHandle debian/qmhandle/usr/bin/
mv debian/qmhandle/usr/bin/qmHandle debian/qmhandle/usr/bin/qmhandle
 
-# Build architecture-independent files here.
-binary-indep: build install
-# We have nothing to do by default.
-
 # Build architecture-dependent files here.
 binary-arch: build install
+# We have nothing to do by default.
+
+# Build architecture-independent files here.
+binary-indep: build install
dh_testdir
dh_testroot
dh_installdocs 
@@ -58,4 +60,4 @@ binary-arch: build install
dh_builddeb
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary 
install

Bug#833816: icc-profiles: FTBFS when built with dpkg-buildpackage -A (dh_testroot: You must run this as root)

[Santiago Vila]

Package: src:icc-profiles
Version: 2.0.1-1
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh_testdir
touch build-stamp
dh_testdir -i
dh_testroot -i
dh_testroot: You must run this as root (or use fakeroot).
debian/rules:25: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 255
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Hint: In debian/rules, build-indep depends on binary-indep.
That may simply not be right, as dpkg-buildpackage -A first invokes
build-indep as a normal user and binary-indep is supposed to be run as root.

Note: I'm reporting this as "serious" after getting the ok from the release
managers. See Bug #830997 for details.

Once that "dpkg-buildpackage -A" work properly, the package would be
suitable to be uploaded in source-only form if you wish.

Thanks.

Bug#833156: [Pkg-openssl-devel] Bug#833156: Bug#833156: openssl: Please enable s390x asm optimisations

[Sebastian Andrzej Siewior]

On 2016-08-01 21:38:07 [+0200], Kurt Roeckx wrote:
> I'm just wondering if we should do this for:
> - Stable (Does 1.0.1 also have the assembler?)
yes, commited

> - Backports
commited.

> Kurt

Sebastian

Bug#833815: qmhandle: FTBFS when built with dpkg-buildpackage -A (binary build with no binary artifacts)

[Santiago Vila]

Package: src:qmhandle
Version: 1.3.2-1
User: sanv...@debian.org
Usertags: arch-all-swapped-binary-targets
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 fakeroot debian/rules binary-indep
dh_testdir
dh_testroot
dh_clean -k
dh_clean: dh_clean -k is deprecated; use dh_prep instead
dh_installdirs
# Add here commands to install the package into debian/qmhandle.
install -m755 qmHandle debian/qmhandle/usr/bin/
mv debian/qmhandle/usr/bin/qmHandle debian/qmhandle/usr/bin/qmhandle
 dpkg-genchanges --build=all >../qmhandle_1.3.2-1_all.changes
dpkg-genchanges: error: binary build with no binary artifacts found; cannot 
distribute
dpkg-buildpackage: error: dpkg-genchanges gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is usually a sign that the binary-arch and binary-indep targets of
debian/rules are just swapped.

Note: I'm reporting this as "serious" after getting the ok from the release
managers. See Bug #830997 for details.

Once that "dpkg-buildpackage -A" work properly, the package would be
suitable to be uploaded in source-only form if you wish.

Thanks.

Bug#833771: nspr FTCBFS: does not honour DEB_BUILD_OPTIONS=nocheck

[Mike Hommey]

On Mon, Aug 08, 2016 at 05:15:15PM +0200, Helmut Grohne wrote:
> Source: nspr
> Version: 2:4.12-3
> Severity: important
> Justification: fails to cross build but built before
> Tags: patch
> User: helm...@debian.org
> Usertags: rebootstrap
> 
> Hi Mike,
> 
> Thank you for enabling the test suite and thus improving the quality of
> nspr. Unfortunately, it is also being run during cross builds that set
> DEB_BUILD_OPTIONS=nocheck. Thus cross builds fail. Please add support
> for DEB_BUILD_OPTIONS=nocheck. I am proposing the attached patch to
> implement it.

I'd argue dh should not be calling override_dh_auto_test in the first
place...

Mike

Bug#833328: openssl does not start on x86_64: version `OPENSSL_1.0.1s' not found

[Sebastian Andrzej Siewior]

control: tags -1 pending

On 2016-08-06 15:19:16 [+0200], Kurt Roeckx wrote:
> Right, now we do.  We didn't at that time.

okay. commited, built:
| openssl version
| OpenSSL 1.0.1t  3 May 2016 (Library: OpenSSL 1.0.2h  3 May 2016)

so it seems to work.

> Kurt

Sebastian

Bug#827245: missing backend for pool type 11 (zfs)

[Tyler Fenby]

I can confirm that the ZFS backend works as expected on Debian after
recompiling libvirt with only a couple lines added to debian/rules to
enable the configure flag.

Regards,

Tyler Fenby

Bug#833805: picon-domains: FTBFS when built with dpkg-buildpackage -A (binary build with no binary artifacts)

[Santiago Vila]

Hi.

While we are at it: You might want to modernize debian/rules a little
bit. In particular, targets build-arch and build-indep are now
mandatory too (so it's likely that just swapping binary-arch and
binary-indep might not be enough).

But debhelper (or dh) takes care of this if you let it to care.

For example, after creating debian/compat with "9" as the contents,
the attached debian/rules would possibly work for picon-domains, and I
guess that maybe for all the other packages as well without changing a
single line.

Thanks.#!/usr/bin/make -f
%:
dh $@

override_dh_auto_build:

override_dh_auto_install:
$(MAKE) install DESTDIR=`pwd`/debian/tmp

override_dh_install:
dh_install usr

Bug#833090: ITP: magic-wormhole -- Securely and simply transfer data between computers

[Jameson Graef Rollins]

On Mon, Aug 08 2016, Antoine Beaupré  wrote:
>> I think the argument against that was that it requires a hard-coded
>> third-party server as a middleman, and it's explicitly stated that it'll
>> disappear if load increases.
>
> It is not hardcoded: you can change the central host and relay with a
> simple commandline option.

The default server is definitely hardcoded, and it is hosted by the
author who has explicitly absolved himself of any responsibility to
maintain it in the long run.  But yes it is also possible to specify
relay and transfer servers manually from the command line (which of
course reduces a lot of the "magic").

I would say that the current dependence on a shared central server is
the one achilles heel of magic-wormhole.  The author is actively working
on ways to reduce that dependence, though (e.g. MDNS).

jamie.


signature.asc
Description: PGP signature

Bug#814628: radiotray run failure

[Elías Alejandro]

Hello Jane,
I'm not sure, but are your talking about Ubuntu 16.04.1 and Unity?
I guess Ubuntu developers apply a patch to radiotray to run properly
under Unity.

Best Regards.

Elías Alejandro



On Sun, Aug 7, 2016 at 5:33 PM, Jane  wrote:
> my attempt to start produces
> david@davidAsusP50Pro:~$ radiotray
> /usr/lib/python2.7/dist-packages/radiotray/XmlDataProvider.py:23:
> PyGIWarning: Gtk was imported without specifying a version first. Use
> gi.require_version('Gtk', '3.0') before import to ensure that the right
> version gets loaded.
>   from gi.repository import Gtk
> /usr/lib/python2.7/dist-packages/radiotray/AudioPlayerGStreamer.py:64:
> FutureWarning: The behavior of this method will change in future versions.
> Use specific 'len(elem)' or 'elem is not None' test instead.
>   if(cfg_provider._settingExists("buffer_size")):
> /usr/lib/python2.7/dist-packages/radiotray/SysTray.py:100: PyGIWarning:
> AppIndicator3 was imported without specifying a version first. Use
> gi.require_version('AppIndicator3', '0.1') before import to ensure that the
> right version gets loaded.
>   from gi.repository import AppIndicator3
> Sleep Timer, Stops playing after a predefined time, SleepTimerPlugin.py,
> Carlos Ribeiro
> StationSwitcher, Allows cycling through stations, StationSwitcherPlugin.py,
> Mark F
> HelloWorld, This is a test plugin, HelloWorld.py, Carlos Ribeiro
> started
> Notifications, Shows message notifications on the desktop,
> NotificationPlugin.py, Carlos Ribeiro
> /usr/share/radiotray/plugins/NotificationPlugin.py:25: PyGIWarning: Notify
> was imported without specifying a version first. Use
> gi.require_version('Notify', '0.7') before import to ensure that the right
> version gets loaded.
>   from gi.repository import Notify
> Mate Media Keys, Controls Radio Tray through keyboard multimedia keys,
> MateMediaKeysPlugin.py, Ken
> Gnome Media Keys, Controls Radio Tray through keyboard multimedia keys,
> GnomeMediaKeysPlugin.py, Carlos Ribeiro
> History, Shows song history, HistoryPlugin.py, Carlos Ribeiro
>
> I've tried a number of different things install dh-python python-central dtc
> This to a fresh install of ubuntu 16.04.1
> It did work well for a while years ago but failed on an upgrade attempt
>  Now attempt to run produces radio tray icon in Unity taskbar for a few
> seconds
>
> ALERT!!!
> Just realized that a greyed out radio tray icon appeared in the top task
> bar.
>  And when I tried it runs!!
> I'm almost afraid to stop it now.
> If you ask I can report the output of  a terminal start again.
>  Also on further inspection what appeared to be a Ubuntu program "SPLAT"
> icon was in fact the radiotray icon.
> "Radiotray" It's worth the trouble!
> Apologies for taking up your time
> Hope it starts again next time
> doxl...@shaw.ca

Bug#833814: libreoffice-voikko: missing dependency on python3-uno

[Rene Engelhard]

Package: libreoffice-voikko
Version: 5.0-2
Severity: serious

Hi,

I noticed that libreoffice-voikko switched to python some time ago, but then
unfortunately dropped the ball.

I noticed the following right now, though:

(sid)rene@frodo ..ice/share/extensions/voikko/pythonpath % grep import * | grep 
uno
GrammarChecker.py:import unohelper
HyphenatedWord.py:import unohelper
Hyphenator.py:import unohelper
PossibleHyphens.py:import unohelper
PropertyManager.py:import unohelper
PropertyManager.py:import uno
SettingsEventHandler.py:import unohelper
SettingsEventHandler.py:import uno
SpellAlternatives.py:import unohelper
SpellChecker.py:import unohelper

But there's no dependency on python3-uno, which provides those. libreoffice-core
itself does NOT depend on it, and libreoffice-common merely just recommends it
for it's wizards...

So you need to depend on it yourself.

Regards,

Rene

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

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

Versions of packages libreoffice-voikko depends on:
ii  libreoffice-core   1:5.2.0-1
ii  python3-libvoikko  4.0.2-2
ii  voikko-fi  2.0-3

Versions of packages libreoffice-voikko recommends:
ii  libreoffice  1:5.2.0-1
ii  libreoffice-calc 1:5.2.0-1
ii  libreoffice-draw 1:5.2.0-1
ii  libreoffice-impress  1:5.2.0-1
ii  libreoffice-writer   1:5.2.0-1

libreoffice-voikko suggests no packages.

-- debconf-show failed

Bug#833628: Please package latest upstream version based on liblognorm

[Michael Biebl]

Hi

Am 08.08.2016 um 22:04 schrieb Pierre Chifflier:
> On 08/07/2016 11:07 AM, Michael Biebl wrote:
> Hi Michael,
> 
> I'm working on the packaging of version 2.0.1, it should be ready soon.
> I had a look at your repository, it seems you only bumped dependencies,

No, I did not only bump the dependencies.
https://anonscm.debian.org/cgit/users/biebl/liblognorm.git/log/
has quite a few more changes

> but I got new errors with gcc 6:
> 
> samp.c: In function ‘ln_sampChkRunawayRule’:
> samp.c:937:4: error: ignoring return value of ‘fread’, declared with
> attribute warn_unused_result [-Werror=unused-result]
> (void)fread(buf, sizeof(char), 1, repo); /* skip '\n' */
> ^~~
> 
> [...]
> 
> While it will be easy to fix, I'm surprised you did not had the same.

You've enabled Werror. Probably because you've built directly inside the
git directory. In this case, --enable-compile-warnings= defaults to
error. I use git buildpackage, which uses a git export in a separate
build directory, so I don't run into this problem.

You can explicitly set --enable-compile-warnings=yes in debian/rules to
avoid that. (Or disable compiler warnings completely via
--enable-compile-warnings=no, but I wouldn't recommend that)

> I also had to drop 01-fix-pkgconfig.patch, conflicting, and I think not
> necessary now.

Yeah, this was fixed upstream
https://github.com/rsyslog/liblognorm/pull/215

> The new binary package is a good idea, I will indeed merge it.
> 
> When the upload is ready, I will push my repository on alioth to ease
> collaborative work.

This would be great.

> Thanks for your patches.

Regards,
Michael


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



signature.asc
Description: OpenPGP digital signature

Bug#776283: sat-xmpp-wix: assertion fails when not configuring in the right order

[Dominik George]

Hi,

>I'm guessing once the package will have migrated to testing that
>situation 
>will be met.

yep.

I just didn't realise there actually is an updated source package; I took your 
explanation about wix for all of salutatoi and thought it wouldn't be updated.

With the new package in sid, you are of course right.

-nik
-- 
PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296

Dominik George · Mobil: +49-1520-1981389

Teckids e.V. · FrOSCon e.V. · OpenRheinRuhr e.V.
Fellowship of the FSFE · Piratenpartei Deutschland
Opencaching Deutschland e.V. · Debian Contributor

LPIC-3 Linux Enterprise Professional (Security)

Bug#833787: aptitude: please add configuration option to never allow installation of unauthenticated packages

[Manuel A. Fernandez Montecelo]

Control: tags -1 + moreinfo


Hi Holger,

2016-08-08 17:06 Holger Levsen:

Package: aptitude
Version: 0.8.2-1
Severity: wishlist

Hi,

thanks for maintaing aptitude!

There is a trivial attack on aptitude: press "y" on the "do you really want to
install  those unauthenticated packages?" question and there is no way to
prevent people from doing so (by means of configuration), like a strict mode.

Please implement something along these lines, I've heard this is a
blocker for wider Debian adoption by some people/projects/organisations.

I've filed the same bug against apt, it's #833785: "apt: please add 
configuration
option to never allow installation of unauthenticated packages", maybe
apt and aptitude could share that configuration bit too?


As per the reply to apt's counterpart, #833785, this will probably fix
itself by the next release.

Leaving open for a while in the case that it needs some review or if we
can do something extra about this.

(But apt is more popular and a prerequisite of the system, so perhaps
the possible extra strictness of aptitude wouldn't actually be of any
help).


Cheers.
--
Manuel A. Fernandez Montecelo 

Bug#776283: sat-xmpp-wix: assertion fails when not configuring in the right order

[Thomas Preud'homme]

On lundi 8 août 2016 10:27:55 BST Dominik George wrote:
> Hi,
> 
> > First of all, my apologize for this extreme delay. Haven't been very
> > present in Debian for a while. The experience you describe rings a bell,
> > I think I went through it myself and I've probably reported it to
> > upstream in private. Sadly there is no point raising a ticket now because
> > Wix has been discontinued.
> 
> In that case, please file a RoM to remove salutatoi-0.5.1 from testing.

It's been a long time I haven't done it but I was under the impression that 
this was done automatically. Devref seems to agree with me:

"Furthermore, if a package has been removed from unstable, and no package in 
testing depends on it any more, then it will automatically be removed."

I'm guessing once the package will have migrated to testing that situation 
will be met. If I remember well I was even frowned upon once because I 
requested a RoM when this was not necessary and I think it was a situation 
similar to that one.

Best regards,

Thomas

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

Bug#833813: libreoffice-voikko: please provide libreoffice-grammarcheck-fi

[Rene Engelhard]

Package: libreoffice-voikko
Version: 5.0-2
Severity: wishlist

libreoffice-l10n-fi has the following since long:

% apt-cache show libreoffice-l10n-fi
Package: libreoffice-l10n-fi
Source: libreoffice
Version: 1:5.2.0-1
Installed-Size: 2247
Maintainer: Debian LibreOffice Maintainers 
Architecture: all
Provides: libreoffice-l10n-5.2
Depends: libreoffice-common (= 1:5.2.0-1), locales | locales-all
Pre-Depends: dpkg (>= 1.17.13)
Recommends: libreoffice-core (>> 1:5.2.0) | language-support-translations-fi
Suggests: hunspell-dictionary-fi | myspell-dictionary-fi | 
libreoffice-spellcheck-fi, hyphen-fi, libreoffice-grammarcheck-fi, 
libreoffice-help-fi, mythes-fi
 ^^^
Description-en: office productivity suite -- Finnish language package
[...]

So far this is only provided by libreoffice-lightproof-* (en, -ru-ru, hu-hu
und pt-br (NEW)).
I think libreoffice-voikko should provide it too if it does grammar checking.

Regards,

Rene

Bug#833812: Prevent possible stack overflow

[Bastien ROUCARIES]

Package: src:imagemagick
Version: 8:6.7.7.10-5
Severity: grave
Tags: patch security
X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org




Prevent possible stack overflow

Prevent stack overflow by checking if string is null

(cherry picked from commit 6ea4d4e9eeac1e287bdbfda84f67fb1e50242fb5)

origin: upstream,
https://github.com/ImageMagick/ImageMagick/commit/6ea4d4e9eeac1e287bdbfda84f67fb1e50242fb5

Bug#833811: picon-weather: FTBFS when built with dpkg-buildpackage -A (binary build with no binary artifacts)

[Santiago Vila]

Package: src:picon-weather
Version: 2016.01.02-1
User: sanv...@debian.org
Usertags: arch-all-swapped-binary-targets
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 fakeroot debian/rules binary-indep
echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
test -f debian/rules
test root = "`whoami`"
echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
test -f debian/rules
 dpkg-genchanges --build=all >../picon-weather_2016.01.02-1_all.changes
dpkg-genchanges: error: binary build with no binary artifacts found; cannot 
distribute
dpkg-buildpackage: error: dpkg-genchanges gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is usually a sign that the binary-arch and binary-indep targets of
debian/rules are just swapped.

Note: I'm reporting this as "serious" after getting the ok from the release
managers. See Bug #830997 for details.

Once that "dpkg-buildpackage -A" work properly, the package would be
suitable to be uploaded in source-only form if you wish.

[ Note: You will receive seven bugs like this one today. Sorry!
  On the other hand, they are all trivial to fix ].

Thanks.

Bug#833809: picon-usenix: FTBFS when built with dpkg-buildpackage -A (binary build with no binary artifacts)

[Santiago Vila]

Package: src:picon-usenix
Version: 1995.04.13-8
User: sanv...@debian.org
Usertags: arch-all-swapped-binary-targets
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 fakeroot debian/rules binary-indep
echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
test -f debian/rules
test root = "`whoami`"
echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
test -f debian/rules
 dpkg-genchanges --build=all >../picon-usenix_1995.04.13-8_all.changes
dpkg-genchanges: error: binary build with no binary artifacts found; cannot 
distribute
dpkg-buildpackage: error: dpkg-genchanges gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is usually a sign that the binary-arch and binary-indep targets of
debian/rules are just swapped.

Note: I'm reporting this as "serious" after getting the ok from the release
managers. See Bug #830997 for details.

Once that "dpkg-buildpackage -A" work properly, the package would be
suitable to be uploaded in source-only form if you wish.

[ Note: You will receive seven bugs like this one today. Sorry!
  On the other hand, they are all trivial to fix ].

Thanks.

Bug#833810: picon-users: FTBFS when built with dpkg-buildpackage -A (binary build with no binary artifacts)

[Santiago Vila]

Package: src:picon-users
Version: 2016.01.02-1
User: sanv...@debian.org
Usertags: arch-all-swapped-binary-targets
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 fakeroot debian/rules binary-indep
echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
test -f debian/rules
test root = "`whoami`"
echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
test -f debian/rules
 dpkg-genchanges --build=all >../picon-users_2016.01.02-1_all.changes
dpkg-genchanges: error: binary build with no binary artifacts found; cannot 
distribute
dpkg-buildpackage: error: dpkg-genchanges gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is usually a sign that the binary-arch and binary-indep targets of
debian/rules are just swapped.

Note: I'm reporting this as "serious" after getting the ok from the release
managers. See Bug #830997 for details.

Once that "dpkg-buildpackage -A" work properly, the package would be
suitable to be uploaded in source-only form if you wish.

[ Note: You will receive seven bugs like this one today. Sorry!
  On the other hand, they are all trivial to fix ].

Thanks.

Bug#833808: picon-unknown: FTBFS when built with dpkg-buildpackage -A (binary build with no binary artifacts)

[Santiago Vila]

Package: src:picon-unknown
Version: 2016.01.02-1
User: sanv...@debian.org
Usertags: arch-all-swapped-binary-targets
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 fakeroot debian/rules binary-indep
echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
test -f debian/rules
test root = "`whoami`"
echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
test -f debian/rules
 dpkg-genchanges --build=all >../picon-unknown_2016.01.02-1_all.changes
dpkg-genchanges: error: binary build with no binary artifacts found; cannot 
distribute
dpkg-buildpackage: error: dpkg-genchanges gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is usually a sign that the binary-arch and binary-indep targets of
debian/rules are just swapped.

Note: I'm reporting this as "serious" after getting the ok from the release
managers. See Bug #830997 for details.

Once that "dpkg-buildpackage -A" work properly, the package would be
suitable to be uploaded in source-only form if you wish.

[ Note: You will receive seven bugs like this one today. Sorry!
  On the other hand, they are all trivial to fix ].

Thanks.

Bug#833807: picon-news: FTBFS when built with dpkg-buildpackage -A (binary build with no binary artifacts)

[Santiago Vila]

Package: src:picon-news
Version: 2016.01.02-1
User: sanv...@debian.org
Usertags: arch-all-swapped-binary-targets
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 fakeroot debian/rules binary-indep
echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
test -f debian/rules
test root = "`whoami`"
echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
test -f debian/rules
 dpkg-genchanges --build=all >../picon-news_2016.01.02-1_all.changes
dpkg-genchanges: error: binary build with no binary artifacts found; cannot 
distribute
dpkg-buildpackage: error: dpkg-genchanges gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is usually a sign that the binary-arch and binary-indep targets of
debian/rules are just swapped.

Note: I'm reporting this as "serious" after getting the ok from the release
managers. See Bug #830997 for details.

Once that "dpkg-buildpackage -A" work properly, the package would be
suitable to be uploaded in source-only form if you wish.

[ Note: You will receive seven bugs like this one today. Sorry!
  On the other hand, they are all trivial to fix ].

Thanks.

Bug#833805: picon-domains: FTBFS when built with dpkg-buildpackage -A (binary build with no binary artifacts)

[Santiago Vila]

Package: src:picon-domains
Version: 2016.06.27-1
User: sanv...@debian.org
Usertags: arch-all-swapped-binary-targets
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 fakeroot debian/rules binary-indep
echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
test -f debian/rules
test root = "`whoami`"
echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
test -f debian/rules
 dpkg-genchanges --build=all >../picon-domains_2016.06.27-1_all.changes
dpkg-genchanges: error: binary build with no binary artifacts found; cannot 
distribute
dpkg-buildpackage: error: dpkg-genchanges gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is usually a sign that the binary-arch and binary-indep targets of
debian/rules are just swapped.

Note: I'm reporting this as "serious" after getting the ok from the release
managers. See Bug #830997 for details.

Once that "dpkg-buildpackage -A" work properly, the package would be
suitable to be uploaded in source-only form if you wish.

[ Note: You will receive seven bugs like this one today. Sorry!
  On the other hand, they are all trivial to fix ].

Thanks.

Bug#833806: picon-misc: FTBFS when built with dpkg-buildpackage -A (binary build with no binary artifacts)

[Santiago Vila]

Package: src:picon-misc
Version: 2016.06.10-1
User: sanv...@debian.org
Usertags: arch-all-swapped-binary-targets
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 fakeroot debian/rules binary-indep
echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
test -f debian/rules
test root = "`whoami`"
echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
test -f debian/rules
 dpkg-genchanges --build=all >../picon-misc_2016.06.10-1_all.changes
dpkg-genchanges: error: binary build with no binary artifacts found; cannot 
distribute
dpkg-buildpackage: error: dpkg-genchanges gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is usually a sign that the binary-arch and binary-indep targets of
debian/rules are just swapped.

Note: I'm reporting this as "serious" after getting the ok from the release
managers. See Bug #830997 for details.

Once that "dpkg-buildpackage -A" work properly, the package would be
suitable to be uploaded in source-only form if you wish.

[ Note: You will receive seven bugs like this one today. Sorry!
  On the other hand, they are all trivial to fix ].

Thanks.

Bug#833485: CVE-2016-6520: imagemagick: buffer overflow

[Bastien ROUCARIES]

control: fixed -1 8:6.8.9.9-7.2

according to 
http://www.imagemagick.org/discourse-server/viewtopic.php?f=3=30259=136359#p136359
it is not for us

This is a ImageMagick 7 specific patch. We allocate the buffers based
on the number of image pixel channels, however, the method was not
returning the correct number of channels, 3 (RGB) instead of 4 (RGBA).
Calling SyncImagePixelCache() forces an update to the pixel cache
morphology and then GetImageChannels() correctly returns 4 channels. A
better fix, which we subsequently added, was to ensure that each
image, as it is returned by a coder, is synced such that
GetImageChannels() always returns the correct value. For this
particular case, we set the image trait to alpha but we did not
evaluate the image to update the change in the pixel cache morphology
from 3 to 4.

On Fri, Aug 5, 2016 at 4:19 AM, Henri Salo  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Package: imagemagick
> Version: 8:6.8.9.9-7.2
> Severity: important
> Tags: security, upstream, fixed-upstream
>
> A buffer overflow vulnerability has been fixed by following commit:
>
> https://github.com/ImageMagick/ImageMagick/commit/76401e172ea3a55182be2b8e2aca4d07270f6da6
>
> Related CVE request: http://www.openwall.com/lists/oss-security/2016/08/02/6
>
> - --
> Henri Salo
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1
>
> iQIcBAEBAgAGBQJXo/eaAAoJECet96ROqnV0u9QQANLAzG9TZtzzJ5PLCtr4ZeGZ
> 4HgWCG/QyZ050w3ytvmffRprsZIW05WrsAq9bOHqWE5pZEC9jBWNWs4bIlQtnD5n
> mw7onqbNQLVX/MToBFvCKz9/Ng9YjSvseRG9dAsNgZGSghg/OL6MF53fu14V4lOv
> J2zMGy7fLsgwSBQKNjpQAqKAfigZq+XSYFQ9UtV+kuiNk7Wjh+vJXn4GO/T1v5EM
> LhLdoZCb9ebmtvkfqlEFAESbCe1QTGeT09gRjbJ43aynAIz+gvt/mM4JUfiBpiDx
> ///+P056oOLTAPNmCSMcapdX2A5DedOJDh8e6zrurJmbAEnbvIUGvcPKmdFS34au
> y9w4RF2NGNFJNf9zJ/vNLbsbjsXQQEE6qZ8bBxdZ9u9lNwbaI6lLtriOOLdlWfX+
> a5Swe9Yt+sw0hY9TTmGxpyEfpXnzvggOWOs/4879g/+LjWc5waJlU+sSygi+JYHF
> srtK3U8gLr9jlG7nGa6zMG7euRmuc+ipoYcyjYEb89TOrBQq4U6MqhCpQutVsDq4
> 78KY9UEHfF8MSNWiWJUgKcQws2tGKFmJz3WhRqE4D6TXajKD0IfaFQ4oJwuhA9ty
> G8HuMT38mtIBjpVSv+jYT312XfZ0bWRmzuKWIGiTxl1tygTdV5OgPkkJWL0K+4dA
> f/jwBBIC7FnUx3vQ20S9
> =VOoc
> -END PGP SIGNATURE-
>

Bug#833181: libreoffice-draw: I/O general error when saving leads to defunct

[Rene Engelhard]

tag 833181 + unreproducible
thanks

Hi,

On Mon, Aug 08, 2016 at 10:17:15AM -0300, Ricardo Fabian Peliquero wrote:
> It happens every time I try to save an odg document.

Mmh.

>After I/O error, I can still create a new other-than-draw document (e.g. odt, 
>ods) and save it. But the lodraw window will still be there and won't be able 
>to close it when back to it.

I still can't reproduce it. New document, a few shapes. I even inserted
a picture.
 
> I have never used backtrace nor strace, but here it is the output of just 
> 'strace -o lodraw.strace lodraw', Ctrl-g (that is 'save' for 'guardar' on my 
> Spanish localized suite), I/O error dialog pops up, go back to terminal and 
> Ctrl-c. I hope it helps!!!

Not really, AFAICS it misses the interesting part. I think you missed
-f or -ff to strace to follow the childs. Right now you just strace'd
sdraw which is a shell script running the "real" binary..

Regards,
 
Rene

Bug#833804: ITP: mkosi -- create legacy-free OS images

[Felipe Sateler]

Package: wnpp
Severity: wishlist
Owner: Felipe Sateler 

* Package name: mkosi
  Version : 1
  Upstream Author : Lennart Poettering
* URL : https://github.com/systemd/mkosi
* License : LGPL-2.1
  Programming Lang: Python3
  Description : create legacy-free OS images

 A fancy wrapper around "dnf --installroot", "debootstrap" and
 "pacstrap", that may generate disk images with a number of
 bells and whistles.

 Generated images are "legacy-free". This means only GPT disk
 labels (and no MBR disk labels) are supported, and only
 systemd based images may be generated. Moreover, for bootable
 images only EFI systems are supported (not plain MBR/BIOS).

I plan to maintain this within the pkg-systemd umbrella

Bug#741628: Same issue between a fresh Debian unstable and an Ubuntu Server 14.04 LTS

[Benoît Sibaud]

Hi, next step,

According to https://rsync.samba.org/FAQ.html#13
"inflate (token) returned -5
This error means that rsync failed to handle an expected error from the 
compression code for a file that happened to be transferred with a block size 
of 32816 bytes. You can avoid this issue for the affected file by transferring 
it with a manually-set block size (e.g. --block-size=33000), or by upgrading 
the receiving side to rsync 3.0.7. "

Looks like rsync 3.0.7+ is not enough (currently using 3.1.1).

New test with the backup of the day:

Default blocksize 32816, read 7,657,969 bytes, failed inflate returned -3 (0 
bytes)
With --block-size=33000, read 7,690,797 bytes, failed inflate returned -3 (0 
bytes)
With --block-size=36000, read 8,018,923 bytes, failed inflate returned -3 (20 
bytes)
With --block-size=65536, success.

So now we have an other workaround at least (instead of removing -z).

I also have logs from rsync-debug on both sides (mentioned in 
https://rsync.samba.org/issues.html ), but it's huge (400 MB and 236 MB) and 
I'm not sure it's still useful with the two workarounds.

-- 
Benoît Sibaud

Bug#830626: suggested patch adds suite::mysql

[Dieter Adriaenssens]

Control: tags -1 patch

Dear maintainer,

Please find a patch in attachment that adds suite::mysql

Kind regards,
Dieter Adriaenssens
>From f08112549963bca5dfffdfbe32924143612a59f8 Mon Sep 17 00:00:00 2001
From: Dieter Adriaenssens 
Date: Mon, 8 Aug 2016 21:59:35 +0200
Subject: [PATCH] add suite::mysql (closes #830626)

---
 debian-packages | 4 
 1 file changed, 4 insertions(+)

diff --git a/debian-packages b/debian-packages
index d2cec47..600911e 100644
--- a/debian-packages
+++ b/debian-packages
@@ -1721,6 +1721,10 @@ Tag: suite::mozilla
 Description: Mozilla
  Mozilla Browser and extensions
 
+Tag: suite::mysql
+Description: MySQL
+ MySQL and variants like MariaDB and Percona
+
 Tag: suite::netscape
 Description: Netscape Navigator
  The pre-6.0 versions of netscape browser
-- 
2.5.0

Bug#833628: Please package latest upstream version based on libfastjson

[Pierre Chifflier]

On 08/07/2016 11:07 AM, Michael Biebl wrote:
> Source: liblognorm
> Version: 1.1.2-1.1
> Severity: important
> Tags: patch
> 
> Hi Pierre!
> 
> The latest rsyslog version in Debian is quite outdated. The reason is,
> that newer versions require libfastjson instead of json-c.
> 
> I've already packages libfastjson, and it is available in unstable and
> testing [1].
> Before I can switch rsyslog over to use libfastjson, I need a newer
> version of liblognorm as well, which as been compiled against
> libfastjson. I've been working with rsyslog/liblognorm upstream and the
> latest versio 2.0.1 should be ok.
> Please consider packaging that version. To test newer rsyslog versions,
> I've already updated liblognorm locally and pushed my work to [2]. Feel
> free to base your update on that.
> Since the library had a soname bump which means going through the NEW
> queue, I decided to introduce a new binary package for the lognormalizer
> tool to fix #753510.
> The git log should be self-explanatory. If you have any questions,
> please don't hesitate to ask.
> 
> As the package didn't have a public (Git) repository, I've created a
> private on based on the last NMU using git-buildpackage [2].
> 

Hi Michael,

I'm working on the packaging of version 2.0.1, it should be ready soon.
I had a look at your repository, it seems you only bumped dependencies,
but I got new errors with gcc 6:

samp.c: In function ‘ln_sampChkRunawayRule’:
samp.c:937:4: error: ignoring return value of ‘fread’, declared with
attribute warn_unused_result [-Werror=unused-result]
(void)fread(buf, sizeof(char), 1, repo); /* skip '\n' */
^~~

[...]

While it will be easy to fix, I'm surprised you did not had the same.
I also had to drop 01-fix-pkgconfig.patch, conflicting, and I think not
necessary now.

The new binary package is a good idea, I will indeed merge it.

When the upload is ready, I will push my repository on alioth to ease
collaborative work.
Thanks for your patches.

Regards,
Pierre

Bug#829063: reopen Bug#829063: graphicsmagick: regression convert: Non-conforming drawing primitive definition (push)

[Bob Friesenhahn]

On Mon, 8 Aug 2016, Paul Gevers wrote:


Hi Bob,

On 07-08-16 15:47, Bob Friesenhahn wrote:

The code in GraphicsMagick Mercurial is working with this file.


I don't know what Mercurial is, but I assume it is an upstream version.
For me, I have 1.3.24-2 and/or 1.3.24-2+b1 installed for the
graphicsmagick related packages (graphicsmagick, libgraphicsmagick and
graphicsmagick-imagemagick-compat)


Yes, it represents unreleased upstream code that the patches possibly 
used to create the new 1.3.24-2 version might have been based on.


Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,http://www.GraphicsMagick.org/

Bug#833603: [Reproducible-builds] Bug#833603: src:strip-nondeterminism: Please provide a process to remove unused handlers over time

[Holger Levsen]

On Sun, Aug 07, 2016 at 12:06:14AM +0200, Chris Lamb wrote:
> Whilst I really like hacking on strip-nondeterminsm I feel it might
> hold back the Reproducible Builds effort in general by hiding the full
> impact of issues.

I don't think so, as I see it, Debian is one of the very few (the only?)
project not normalizing large parts of the environment, so we often
see+fix more reproducibile issues than projects will hit.

(eg locale, timezone, username, shell, etc are normalized in most other
distros and in the bsd world.)

(and surely that doesnt invalid three things: a.) that strip-nondetermism
hides/fixes problems and b.) that other projects should use it c.) that
we should try to fix everything on the core and thus make strip-nondetermism
obsolete and until then, it should explain what it has hidden.)

> Its certainly not a Debian-specific tool per se but I feel like it could
> be fairly labelled as such in an informal context ("Debian run this tool",
> etc.) which isn't excellent marketing for widespread adoption.

we just haven't figured how to run it elsewhere, but this is certainly
my goal. (and has been.)

> It also mean that any distribution that (for whatever reason) cannot use
> it will be exposed to a whole bunch of issues that we are not working on
> because they are "fixed" by strip-nondeterminism.

at least coreboot manages quite well without it ;-)


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#819333: [llvm-3.8-dev] LLVMgold.so is missing, so "clang -flto" is unusable

[Lorenz Hübschle-Schneider]

Awesome - thank you very much! I must confess that I'm not very
proficient in Debian packaging and the package build process. I'll have
to change that some day ;)

Best,
Lorenz

On Mon, 8 Aug 2016, at 18:40, Sylvestre Ledru wrote:
> I think I found the fix. So, don't bother :)
> 
> Le 08/08/2016 à 17:10, Sylvestre Ledru a écrit :
> > I will have a look but don't hesitate to provide a patch to make
> > things moving faster
> >
> > Le 08/08/2016 à 16:41, Lorenz Hübschle-Schneider a écrit :
> >> Dear maintainer,
> >>
> >> this issue is still present in version 1:3.8.1-8. According to
> >> http://llvm.org/docs/GoldPlugin.html the fix should be quite simple. I'd
> >> really appreciate it if you could bring back LLVMgold.so in 3.8.
> >>
> >> Best,
> >> Lorenz
> >>
> >> On Sat, 26 Mar 2016 23:10:18 +0100 Steffen Weinhart
> >>  wrote:
> >>> Package: llvm-3.8-dev
> >>> Version: 1:3.8-2
> >>> Severity: important
> >>>
> >>> In versions prior to 3.8 (final), there was LLVMgold.so, which was used
> >>> e.g. when clang was invoked with "-flto". When using clang-3.8 with
> >>> "-flto" now, the linker cannot find the library and aborts. Why has it
> >>> been removed? Or at least what package should I install then? "apt-file
> >>> search LLVMgold.so" only finds entries in older llvm-3.*-dev packages.
> >>>
> >>> --- System information. ---
> >>> Architecture: amd64
> >>> Kernel: Linux 4.4.6
> >>>
> >>> Debian Release: stretch/sid
> >>> 900 testing security.debian.org
> >>> 900 testing ftp.deb-multimedia.org
> >>> 900 testing ftp.de.debian.org
> >>> 500 testing-updates ftp.de.debian.org
> >>> 500 testing-proposed-updates ftp.de.debian.org
> >>> 500 stable-updates ftp.de.debian.org
> >>> 500 stable security.debian.org
> >>> 500 stable ftp.de.debian.org
> >>> 500 proposed-updates ftp.de.debian.org
> >>> 50 unstable ftp.deb-multimedia.org
> >>> 50 unstable ftp.de.debian.org
> >>> 100 jessie-backports ftp.de.debian.org
> >>> 1 experimental ftp.de.debian.org
> >>>
> >>> --- Package information. ---
> >>> Package's Depends field is empty.
> >>>
> >>> Package's Recommends field is empty.
> >>>
> >>> Package's Suggests field is empty.
> >>>
> >>>
> >>
> >> ___
> >> Pkg-llvm-team mailing list
> >> pkg-llvm-t...@lists.alioth.debian.org
> >> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-llvm-team
> >>
> >
> > ___
> > Pkg-llvm-team mailing list
> > pkg-llvm-t...@lists.alioth.debian.org
> > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-llvm-team
> 
> 

Bug#833803: oxygen-icon-theme: Gtk-WARNING **: Theme directory base/ of theme default.kde4 has no size field

[Fernando Santagata]

Package: oxygen-icon-theme
Version: 5:5.24.0-1
Severity: normal
Tags: patch

Dear Maintainer,
I'm running Debian sid. After one update/dist-upgrade cycle I found out that
starting gvim from the terminal output this message:

(gvim:14295): Gtk-WARNING **: Theme directory base/ of theme default.kde4 has
no size field

The directory of the theme default.kde4 is a link to the oxygen theme
directory.

On my system "dpkg -S /usr/share/icons/oxygen" outputs this:

dragonplayer, korganizer, oxygen-icon-theme, kdepim-runtime, konq-plugins,
kopete, kdepimlibs-data: /usr/share/icons/oxygen

so one of those packages wrote something incorrect in the index.theme file.
When I delved into that file I found out that in the "Directories="
configuration parameter, among the other directories listed, there was a
"base/", which does not have a corresponding section.

The patch to avoid the error message is just to find the string "base/," in the
list of directories and delete it.



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

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

Versions of packages oxygen-icon-theme depends on:
ii  hicolor-icon-theme  0.15-1

oxygen-icon-theme recommends no packages.

oxygen-icon-theme suggests no packages.

-- no debconf information

Bug#830940: mirrors: more files should be excluded in stage1 sync

[SJ Zhu]

> Please provide a proper error messages.  by-hash should provide proper
> ordering of updates
>

After investigating this problem again, I find all components of debian have
enabled by-hash, for example Contents*.gz files. Then there will be no problem
in this situation.

When I reported this bug, apt-file has upgraded to 3.0 in debian testing, which
downloads Contents*.gz files during apt update. But debian testing has no
by-hash dir for Contents*.gz.

Debian jessie has no by-hash dir but apt-file in jessie will not be
upgraded to 3.0.
So I think the problem is gone in debian.
However not sure for other distributions which also use apt-file and ftpsync.

Thanks,
Shengjing Zhu

Bug#833392: hilive: FTBFS: assumes uint64_t is unsigned long

[Andreas Tille]

Hi Martin,

On Mon, Aug 08, 2016 at 09:04:56AM -0700, Martin Lindner wrote:
> 
> Sorry for the late reply. This is a case of: It's not a bug, a feature. 
> HiLive makes heavy use of 64bit data structures, so I would expect that it 
> doesn't compile on 32bit architectures.

Don't you think that's a bit simple explanation.  Using different
declarations for variables is not really the proper means to prevent
building on 32 bit archs, isn't it.

Kind regards

Andreas.

-- 
http://fam-tille.de

Bug#829063: reopen Bug#829063: graphicsmagick: regression convert: Non-conforming drawing primitive definition (push)

[Paul Gevers]

Hi Bob,

On 07-08-16 15:47, Bob Friesenhahn wrote:
> The code in GraphicsMagick Mercurial is working with this file.

I don't know what Mercurial is, but I assume it is an upstream version.
For me, I have 1.3.24-2 and/or 1.3.24-2+b1 installed for the
graphicsmagick related packages (graphicsmagick, libgraphicsmagick and
graphicsmagick-imagemagick-compat)

Paul



signature.asc
Description: OpenPGP digital signature

Bug#833802: clang-tidy-3.9: readability-identifier-naming segfaults

[paul cannon]

Package: clang-tidy-3.9
Version: 1:3.9~svn274438-1
Severity: normal
Tags: upstream, fixed-in-experimental, fixed-upstream

Running clang-tidy-3.9 with the "readability-identifier-naming" check
enabled fails with a segmentation fault at the slightest provocation:

paul@turing:~$ cat breaks-clang-tidy.cpp 
#include 

int main()
{
return 0;
}
paul@turing:~$ clang-tidy-3.9 breaks-clang-tidy.cpp 
-checks='-*,readability-identifier-naming'
Error while trying to load a compilation database:
Could not auto-detect compilation database for file "breaks-clang-tidy.cpp"
No compilation database found in /home/paul or any parent directory
json-compilation-database: Error while opening JSON database: No such file 
or directory
Running without flags.
Segmentation fault
paul@turing:~$

This matches the behavior complained of in the upstream bug at
https://llvm.org/bugs/show_bug.cgi?id=28481 , and the patch attached to
that bug does indeed fix the problem.

The problem is also fixed in version 1:3.9~svn275918-1~exp1 (in
experimental).

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

Kernel: Linux 4.4.0-28-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages clang-tidy-3.9 depends on:
ii  libc6   2.23-4
ii  libgcc1 1:6.1.1-11
ii  libllvm3.9  1:3.9~svn274438-1
ii  libstdc++6  6.1.1-11
ii  python  2.7.11-2

clang-tidy-3.9 recommends no packages.

clang-tidy-3.9 suggests no packages.

-- no debconf information

Bug#833709: Please add the MIT/Expat license to common-licenses

[Russ Allbery]

Josh Triplett  writes:

> Numerous packages use the MIT/Expat license, and currently all of those
> packages need to include it in their copyright files.  I'd love to see
> this license added to /usr/share/common-licenses/ ; this would require a
> Policy change to section 12.5 to allow.

I don't think this is a good idea.  This license is extremely short, and
it has a ton of minor variations, so we'll get a lot of people using it
even though the exactly licensing terms of their package don't match the
canonical copy.

For example, it's very common to see "THE AUTHORS" replaced with a
specific list of people or organizations in the license, which is a very
small change that's easy for someone to miss when they know that the terms
are just the Expat terms.

I think the common-license infrastructure is designed for licenses that
are small novels, like the GPL.  For something that's just three
paragraphs, putting it directly in the copyright file has a simplicity and
robustness that I think outweighs any minor one-time inconvenience during
packaging or a bit of additional disk space usage.

(And if I could go back in time, I'd pull the BSD license from
common-licenses on the same grounds.)

-- 
Russ Allbery (r...@debian.org)   

Bug#832983: nettle: CVE-2016-6489

[Salvatore Bonaccorso]

Hi,

On Sat, Jul 30, 2016 at 04:34:12PM +0200, Salvatore Bonaccorso wrote:
> Furthermore there seem to be possible problems with the approach.
> Hanno Boeck mentions on
> http://www.openwall.com/lists/oss-security/2016/07/30/2 that the patch
> has some unintended side effects. Cf.
> https://lists.lysator.liu.se/pipermail/nettle-bugs/2016/003104.html

According to https://bugzilla.redhat.com/show_bug.cgi?id=1362016#c6 ,
there is
https://git.lysator.liu.se/nettle/nettle/commit/52b9223126b3f997c00d399166c006ae28669068
additionally needed to add some snaity checks at the functions using
mpz_powm_sec()

Regards,
Salvatore

Bug#833801: thunar: intensive scrollig with mouse wheel ejects me to the login screen

[Marian]

Package: thunar
Version: 1.6.3-2
Severity: important

I have a shortcut on panel #2 to launch Thunar. I use it to open my music
folder. When I start to scroll down the list with the mouse whell after
(usually) 3 movements I am sudenly presented with the login screen to enter my
login name and password. This behavior is 100% reproducible on my laptop - each
time I try it I get it.



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

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

Versions of packages thunar depends on:
ii  desktop-file-utils  0.22-1
ii  exo-utils   0.10.2-4
ii  libatk1.0-0 2.14.0-1
ii  libc6   2.19-18+deb8u4
ii  libcairo2   1.14.0-2.1+deb8u1
ii  libdbus-1-3 1.8.20-0+deb8u1
ii  libdbus-glib-1-20.102-1
ii  libexo-1-0  0.10.2-4
ii  libgdk-pixbuf2.0-0  2.31.1-2+deb8u5
ii  libglib2.0-02.42.1-1+b1
ii  libgtk2.0-0 2.24.25-3+deb8u1
ii  libgudev-1.0-0  215-17+deb8u4
ii  libice6 2:1.0.9-1+b1
ii  libnotify4  0.7.6-2
ii  libpango-1.0-0  1.36.8-3
ii  libsm6  2:1.2.2-1+b1
ii  libthunarx-2-0  1.6.3-2
ii  libxfce4ui-1-0  4.10.0-6
ii  libxfce4util6   4.10.1-2
ii  libxfconf-0-2   4.10.0-3
ii  shared-mime-info1.3-1
ii  thunar-data 1.6.3-2

Versions of packages thunar recommends:
ii  dbus-x11 1.8.20-0+deb8u1
ii  gvfs 1.22.2-1
ii  libfontconfig1   2.11.0-6.3+deb8u1
ii  libfreetype6 2.5.2-3+deb8u1
ii  libpangocairo-1.0-0  1.36.8-3
ii  libpangoft2-1.0-01.36.8-3
ii  thunar-volman0.8.0-4
ii  tumbler  0.1.30-1+b1
ii  xdg-user-dirs0.15-2
ii  xfce4-panel  4.10.1-1

Versions of packages thunar suggests:
ii  thunar-archive-plugin 0.3.1-3
ii  thunar-media-tags-plugin  0.2.1-1

-- no debconf information

Bug#790339: [wine-development] Last two upgrades: Kindle No Longer Working

[Jens Reyer]

control: tags -1 + moreinfo


On 28.06.2015 10:21, David Baron wrote:
> Some downloaded books simply highlight but do not go to reader.
> Others crash out. Backtrace attacher

>From https://bugs.winehq.org/show_bug.cgi?id=38383:

Did you install the required MS core fonts?


There were some changes in our fonts packages, please make sure that you
have at least fonts-wine 1.8.2-1 installed and check again.

If it still fails you might try ttf-mscorefonts-installer (from the
contrib section).

Please report back.


> --- Package information. ---
> Package's Depends field is empty.

This seems very wrong. Either your Wine installation is broken, or
something went wrong while you reported the bug.


Greets
jre

Bug#830777: fixed with package keyutils

[Andreas B. Mundt]

Hi,

I can confirm that installing keyutils fixes the issue, as reported by
Stig Inge Lea Bjørnsen in Message #10.  See also [1].

Perhaps keyutils shouel be added as a dependency?

Regards,

Andi


[1] http://www.spinics.net/lists/linux-nfs/msg49996.html

Bug#833791: dh_sphinxdoc: Misleading error message “Sphinx documentation not found at […]”

[Ben Finney]

Control: clone 833791 -1
Control: retitle -1 dh_sphinxdoc: Misleading error message “Sphinx 
documentation not found at […]”

On 08-Aug-2016, Dmitry Shachnev wrote:
> Hi Ben,
> 
> On Tue, Aug 09, 2016 at 03:15:49AM +1000, Ben Finney wrote:
> > Its error message even reports the very directory where it looked,
> > and claims it can't find documentation that evidently exists
> > there.
> 
> I agree the error message is a bit misleading, but this is not what
> you have been complaining about.

Thanks, I am now creating a new bug report for that.

The error message should always say the correct directory name that
was actually inspected.

If the directory does not exist, that should also be a separate error
message.

-- 
 \ “If you don't want your beliefs to be ridiculed, don't have |
  `\such ridiculous beliefs.” —Greta Christina, 2011-10-22 |
_o__)  |
Ben Finney 


signature.asc
Description: PGP signature

Bug#833798: krb5: FTBFS with -O3: uninitialized variables

[Sam Hartman]

Yeah, thanks for reminding me of this.
I had intended to apply it from the launchpad bug but just forgot.

Bug#833798: krb5: FTBFS with -O3: uninitialized variables

[Steve Langasek]

Package: krb5
Version: 1.14.3+dfsg-1
Severity: minor
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkety ubuntu-patch

Hi Sam,

As you saw in https://bugs.launchpad.net/bugs/1592841, krb5 was failing to
build in Ubuntu on ppc64el because we build that architecture with -O3
optimization, which detected some additional uninitialized variables at
compile time compared to the Debian toolchain.

The attached patch was uploaded to fix the build failure in Ubuntu, but does
not appear to have been included in either Debian or upstream.  Could you
consider applying it in Debian, so that the krb5 package can be in sync
again?

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru krb5-1.14.3+dfsg/debian/patches/0011-sendto_kdc-uninitialized-variable.patch krb5-1.14.3+dfsg/debian/patches/0011-sendto_kdc-uninitialized-variable.patch
--- krb5-1.14.3+dfsg/debian/patches/0011-sendto_kdc-uninitialized-variable.patch	1969-12-31 16:00:00.0 -0800
+++ krb5-1.14.3+dfsg/debian/patches/0011-sendto_kdc-uninitialized-variable.patch	2016-06-15 22:57:49.0 -0700
@@ -0,0 +1,45 @@
+From 0696cc5a5dfb59f15dc0212d58aa509066212b65 Mon Sep 17 00:00:00 2001
+From: Steve Langasek 
+Date: Thu, 16 Jun 2016 08:57:00 +0300
+Subject: sendto_kdc uninitialized variable
+
+---
+ src/lib/krb5/os/sendto_kdc.c | 5 +++--
+ 1 file changed, 3 insertions(+), 2 deletions(-)
+
+Index: krb5-1.14.2+dfsg/src/lib/krb5/os/sendto_kdc.c
+===
+--- krb5-1.14.2+dfsg.orig/src/lib/krb5/os/sendto_kdc.c
 krb5-1.14.2+dfsg/src/lib/krb5/os/sendto_kdc.c
+@@ -339,7 +339,8 @@ cm_select_or_poll(const struct select_st
+ struct timeval tv;
+ #endif
+ krb5_error_code retval;
+-time_ms curtime, interval;
++time_ms curtime = 0;
++time_ms interval;
+ 
+ retval = get_curtime_ms();
+ if (retval != 0)
+@@ -1315,7 +1316,7 @@ service_fds(krb5_context context, struct
+ void *msg_handler_data, struct conn_state **winner_out)
+ {
+ int e, selret = 0;
+-time_ms endtime;
++time_ms endtime = 0;
+ struct conn_state *state;
+ 
+ *winner_out = NULL;
+Index: krb5-1.14.2+dfsg/src/tests/asn.1/trval.c
+===
+--- krb5-1.14.2+dfsg.orig/src/tests/asn.1/trval.c
 krb5-1.14.2+dfsg/src/tests/asn.1/trval.c
+@@ -404,7 +404,7 @@ int do_cons(fp, enc, len, lev, rlen)
+ {
+ int n;
+ int r = 0;
+-int rlen2;
++int rlen2 = 0;
+ int rlent;
+ int save_appl;
+ 
diff -Nru krb5-1.14.3+dfsg/debian/patches/series krb5-1.14.3+dfsg/debian/patches/series
--- krb5-1.14.3+dfsg/debian/patches/series	2016-07-30 18:56:43.0 -0700
+++ krb5-1.14.3+dfsg/debian/patches/series	2016-07-31 16:01:55.0 -0700
@@ -8,3 +8,4 @@
 debian-local/0008-Use-isystem-for-include-paths.patch
 debian-local/0009-Fix-krb5-config-paths.patch
 0010-Initial-German-translations.patch
+0011-sendto_kdc-uninitialized-variable.patch

Bug#816020: /usr/bin/wineserver disables persistence delay

[Jens Reyer]

control: severity -1 wishlist

On 18.06.2016 00:44, Jens Reyer wrote:
> On 26.02.2016 19:08, Jakub Wilk wrote:
>> /usr/bin/wineserver passes -p0 to wineserver32. This seems to be an
>> undocumented deviation from upstream behavior. The manpage says: "the
>> default value is 3 seconds".
> 
> I'll patch the manpage.

Done in wine 1.8.3-3.

Downgrading the severity to wishlist for the request to revert to the
upstream behavior.

Bug#819255: wine-binfmt: doesn't register the binfmt on install/remove

[Jens Reyer]

control: severity -1 wishlist

On 28.07.2016 17:08, Jens Reyer wrote:
> This is documented in the README.debian, which also gives an explanation
> why this doesn't happen automatically (I just added the last paragraph
> with removal instructions in git master):

Released in wine 1.8.3-3.

Downgrading the severity to wishlist.

Bug#760787: Please try these

[anarcat]

On Sun, Apr 24, 2016 at 09:13:09PM +0200, Richard Hartmann wrote:
> Hi,
> 
> feel free to use
> dediserver.eu/misc/git-annex_6.20160418-1~bpo8+1_amd64.deb until its
> "real" package migrated into testing.

The package did migrate to testing now, can the backport be updated?

Thanks!

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


signature.asc
Description: Digital signature

Bug#833797: cegui-mk2: FTBFS with Boost 1.61

[Graham Inggs]

Source: cegui-mk2
Version: 0.8.7-1.1
Severity: serious


Hi Maintainer

Your package build-depends on Boost 1.58 libraries.
The default Boost version is now 1.61.
This causes your package to FTBFS BD-Uninstallable as it attempts to
install development libraries from Boost 1.58 and 1.61 together.

Please build-depend on the unversioned Boost libraries,
e.g. libboost-signals-dev instead of libboost-signals1.58-dev, etc.

Please also consider using wrap-and-sort from the devscripts package
to nicely sort and split your build-depends in debian/control into
multiple lines.

Regards
Graham

Bug#723474: lilv link with -L/usr/lib

[Jaromír Mikeš]

Hi YunQiang Su,

is this bug still actual? Or this bug can be closed now?
I have several instances of this bug in packages I am maintain.
What about the others?

best regards

mira