Bug#791635: python-policy: Please require namespacing source python module packages

[Piotr Ożarowski]

The right place to discuss Debian Python Policy changes is
debian-pyt...@lists.debian.org mailing list.

(and I'm strongly against this change, BTW)


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#790084: Re : synaptic: Set Internal Options crash

[Michael Vogt]

On Mon, Jul 06, 2015 at 09:24:47PM +, E/LH/O13B - JULE Corentin wrote:
> seems to be duplicate of #774056

Thanks, I fixed this in bzr now.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791629: mount/umount: Handling of -n option and /etc/mtab is buggy

[Andreas Henriksson]

Control: tags -1 + moreinfo

On Mon, Jul 06, 2015 at 04:26:43PM -0700, Elliott Mitchell wrote:
> Package: mount
> Version: 2.20.1-5.3

You seem to be running <= oldstable version of Debian.

Please upgrade to a newer version and report back if your issue persists
or not. (fwiw, In testing/unstable the usage of mtab is fully disabled.)

(If you intend to stay on the old version I'd suggest making sure that
you have /proc mounted inside your chroot and see if that helps resolve
the situation. If not, again, try upgrading.)

Regards,
Andreas Henriksson


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791346: fresh upstream release available (1.3.3) and needed for ITP tigervnc

[Aaron M. Ucko]

Yaroslav Halchenko  writes:

> or we could check if may be none of rdepends use any of those (and their
> rebuild might be the only thing needed to stay safe)?  I could run
> quickly rebuild of all build/rdepends if you gimme perspective package
> which doesn't even bring up the dead things alive? ;)

I've pushed a rough cut of 1.3.3 packaging to my usual Alioth
repository.  I haven't tested it beyond confirming that it builds.

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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#335472: Best Proposal for Your Websites

[Aditya Singh]

Hi,

We
are a professional website design & SEO services company providing
exclusive web designing services in India and Worldwide. 

If you want your website to
appear on first page of
Google, Yahoo! & Bing then please let me know.

Do you want to drive more traffic to your web
site? 


  Website Design Packages:


•   
Logo Designing,

•   
Custom Web Designing,

•   
Website Development,

•   
Corporate Website Designing,

•   
Website Redesigning,

•   
Website Hosting,

•   
Web 2.0 based designing,

•   
E-Commerce Web Designing, etc. 

SEO Packages:

•   
Complete SEO Packages,

•   
Keywords Optimized,

•   
Pages Configured for SEO (Monthly),

•   
Keyword Research & Analysis,

•   
SEO Strategy Plan & Suggestions,

•   
Code Optimization,

•   
Content Specific Optimization,

•   
Google Tools & SEO Files Created,

•   
All SEO Files Configured Monthly,

•Monthly SEO Updates & Reports,
etc.

 

Our website design expert team will provide you the best
service and support

We can provide you 1st to 10th
position in Google rankings at very affordable prices.

Please let us know your interest
in our services.

 

Regards,Aditya Singh  Marketing Manager

  

Bug#791644: xserver-xorg-video-modesetting doesn't support rotation

[Steev Klimaszewski]

Package: xserver-xorg-video-modesetting
Version: 0.9.0-1

There is a patch in freedesktop git for the modesetting video driver,
since the released version does not support rotation.  This lead to
quite a bit of frustration over here in that when you rotate via xrandr,
the screen goes blank.  It's the only patch in their git past the 0.9.0
release.  It would be wonderful if this could be added to the Jessie
package.

The xorg 1.17 package in jessie+1 is unaffected because modesetting has
moved into the server core (and does support rotation)


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791532: antiword says Word Document is not a Word Document

[Olly Betts]

Control: reopen -1
Control: retitle -1 antiword: better error message for word 2003 XML

On Mon, Jul 06, 2015 at 02:33:27PM +0800, 積丹尼 Dan Jacobson wrote:
> Try it with

Thanks for providing a test case.

This looks like the old "not in a ZIP container" XML format.  We can
probably provide a customised error message if the first few bytes of
the file look like an XML document, like we do if they look like a ZIP
file (and as antiword upstream does for RTF, Word Perfect, etc):

https://sources.debian.net/src/antiword/0.37-10/debian/patches/docx.patch/

Cheers,
Olly


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791569: whatmaps: Fails to restart apache2 on Jessie and later

[Guido Günther]

Hi,
On Mon, Jul 06, 2015 at 12:24:32PM +0200, Santiago Garcia Mantinan wrote:
> Package: whatmaps
> Version: 0.0.9-1
> Severity: important
> Tags: patch
> 
> Hi!
> 
> I have found after running unattended-upgrades with whatmaps installed that
> apache2 was not being restarted on the last openssl upgrade.
> 
> I went to see what whas happening and the log was quite clear, whatmaps was
> not able to guess that the apache2 binary which now comes in the apache2-bin
> package had its start scripts on the apache2 package.
> 
> Adding this line to debiandistro.py made it work ok:
> 
> --- /usr/lib/python2.7/dist-packages/whatmaps/debiandistro.py~
> 2014-12-28
> --- /15:03:58.0 +0100
> +++ /usr/lib/python2.7/dist-packages/whatmaps/debiandistro.py 2015-07-06
> 12:11:42.516301645 +0200
> @@ -43,6 +43,7 @@
>  _pkg_services = { 'apache2-mpm-worker':  [ 'apache2' ],
>'apache2-mpm-prefork': [ 'apache2' ],
>'apache2.2-bin':   [ 'apache2' ],
> +  'apache2-bin': [ 'apache2' ],
>'dovecot-imapd':   [ 'dovecot' ],
>'dovecot-pop3d':   [ 'dovecot' ],
>'exim4-daemon-light':  [ 'exim4' ],

Thanks a lot. Pushed as 1b59d859f2442dd859fa255a50d3d149c5320213.

> 
> I think it would be good to have this fix (or whatever you see fit) rolled
> as a security upgrade or at least as a stable update.

Since this is "best effort" list I don't think it warrants a security
update but we really should target a point release.

Cheers,
 -- Guido


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791475: bup: Unable to restore an emacs autosave file #.fetchmailrc#

[Rob Browning]

David Creelman  writes:

> Having said that, it's just vanilla text. Nothing odd in it at first glance.
> It's ls -l is
> -rwx-- 1 davidc davidc 833 Jan 20 23:42 /home/davidc/#.fetchmailrc#*
> file gives
> /home/davidc/#.fetchmailrc#: ASCII text

OK, thanks, and the lsattr call is the one most directly related to the
error you encountered, so the output of that would still be interesting.

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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#768376: [Pkg-libvirt-maintainers] Bug#768376: [libvirt-daemon-system]

[Guido Günther]

Hi,
On Mon, Jul 06, 2015 at 10:45:43PM +0200, Jan-Benedict Glaw wrote:
> Hi all, hi Guido!
> 
> I just wanted to throw in my 2c. While cleaning up some machines, I
> came along my KVM host and actually wondered why policykit was pulled
> in.  I'm as well only using root-based access to libvirt, which keeps
> all the systemd stack installed.
> 
>   I admit that I'm not too deep into the details of packaging. It's
> probably a good thing to pull polkit in the first place, since it's
> probably used. However, I'd be quite happy to see a way getting rid of
> the (hard) dependency, allowing to deinstall polkit and its
> dependencies.  Going a route like requiring some libvirt-auth meta
> package, provided by libvirt-polkit und libvirt-socket would probably
> do the job, but might look like over-engineering?

I do agree that being able to go without polkit would be nice but a
similar situation with virt-manger showed that Recommends: are just not
enough. Many people skip them and then report bugs if you use Recommends
for a package that's needed in 95% of the installations. I'm just not up
to handle these.

Cheers,
 -- Guido


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791628: git-upstream-tag not effective inside of gbp.conf

[Guido Günther]

On Tue, Jul 07, 2015 at 01:17:36AM +0200, Eduard Bloch wrote:
> Package: git-buildpackage
> Version: 0.6.31
> Severity: minor
> 
> First, please DO NOT CLOSE THIS until it is fully clarified. Just don't!
> It's insulting, even if you know immediately what the problem is; if
> your docs don't make it clear to the user then your docs suck.
> 
> I tried to follow
> file:///usr/share/doc/git-buildpackage/manual-html/gbp.import.html#GBP.IMPORT.UPSTREAM-GIT
> and switched from the old tar-imported upstream branch to upstream
> repository on Github (upstream author moved a few months ago).
> Checking the documentation, I figured it's a good idea to add:
> git-upstream-tag='v%(version)s'
> to debian/gbp.conf in order to not write it down again and again.
>
> 
> Result:
> $ gbp buildpackage --git-pristine-tar --git-pristine-tar-commit 
> ...
> gbp:info: Orig tarball 'encfs_1.8.1.orig.tar.xz' not found at '../tarballs/'
> gbp:warning: Pristine-tar branch "pristine-tar" not found
> gbp:error: Pristine-tar couldn't checkout "encfs_1.8.1.orig.tar.xz": fatal: 
> Path 'encfs_1.8.1.orig.tar.xz.delta' does not exist in 
> 'refs/remotes/origin/pristine-tar'
> pristine-tar: git show 
> refs/remotes/origin/pristine-tar:encfs_1.8.1.orig.tar.xz.delta failed
> gbp:error: upstream/1.8.1 is not a valid treeish
> 
> I tried this and that and couldn't see the reason. The message is IMHO
> kinda pointless; why does it not simply commit as it's told by the
> command line? As the final guess I added
> --git-upstream-tag='v%(version)s' to the command line and it suddenly
> worked. So it looks like the option is not read from gbp.conf. How
> should I know that? gbp.conf(5) does not tell me which ones are valid
> there and which are not.
> 
> Out of blue, I added git-pristine-tar and git-pristine-tar-commit there
> and got:
> gbp:error: File contains parsing errors: 
> /home/user/debian/dev/encfs/debian/gbp.conf
>   [line  5]: 'git-pristine-tar\n'
>   [line  6]: 'git-pristine-tar-commit\n'
> 
> PARSING ERRORS?
>
> 
> Or maybe something is not applicable in the DEFAULT section? Even if
> that assumption is correct, the message should be something meaningful
> and not a bogus "parsing error".

The docs say:

All options in the config files are specified without the 'git-'
prefix.

under "Configuation Files" of the man page. There are also examples
around that document the format. Use these and all the above will again
turn into non issues.

I recommend to read an respect the references at

 /usr/share/doc/reportbug/HowToReportGoodBugs.txt

so I can figure out what exactly you have issues with.
at 
Cheers,
 -- Guido


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791643: roundcube: CVE-2015-5381 CVE-2015-5382 CVE-2015-5383

[Salvatore Bonaccorso]

Source: roundcube
Version: 1.1.1+dfsg.1-1
Severity: important
Tags: security upstream fixed-upstream

Hi,

the following vulnerabilities were published for roundcube.

CVE-2015-5381[0]:
XSS vulnerability in _mbox argument

CVE-2015-5382[1]:
security improvement in contact photo handling

CVE-2015-5383[2]:
potential info disclosure from temp directory

If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2015-5381
[1] https://security-tracker.debian.org/tracker/CVE-2015-5382
[2] https://security-tracker.debian.org/tracker/CVE-2015-5383

Regards,
Salvatore


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#774153: Jessie - systemd-tty-ask-password-agent hung

[Markus Weber]

I`ve this Bug in an fresh installed Hetzner Root-Server while running 
normally.
So, at some Point, I couldn`t reload my Services.
After an "systemd rexexc" it`s controllable again.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791589: musescore-soundfont-gm: Many muse soundfonts exist. Consider making virtual.

[Fabian Greffrath]

Am Montag, den 06.07.2015, 15:00 + schrieb Jack Underwood:
> It has?  As far as I see musescore-2.0.1+dfsg-2 still has
> musescore-soundfont-gm as a dependency, with fluid-soundfont-gm and
> timgm6mb-soundfont as Suggests... (if things have changed please
> disregard) this means that musescore2 still depends on timgm6mb-soundfont
> via musescore-soundfont-gm despite it listed as a Suggests.

Oh, indeed, this appears to be an oversight.

> Personally I vote for taking this font out and putting it its own package
> like the other fonts.  As far as I understand FluidR3Mono_GM just represents
> a lighter version of the already packaged fluid-soundfont-gm, which means it
> works better on slower computers.  By turning this into a virtual package,

Nope. The new soundfont is in SF3 format which means that it contains
OGG-compressed samples and is currently incompatible with anything else
but musescore itself. As soon as other sound renderers, e.g.
fluidsynth, gain ability to use this sound font format, I agree, it
should get split into its own separate package and be made available to
these other sound renderes as well.

> and keeping it as a required package for musescore we effectively allow the
> user to pick and choose whether they want to just install the lite or the full
> version of this font (of course they can still install both, but this would
> give the user that extra option).

Not sure why you refer to "virtual packages", but we have simple
alternative dependencies for that. However, I think musescore should
well depend on its own sound font, but merely suggest the other
available ones.

> Anyway, just an idea, I don't know what plans you have for the package.  Just
> really wanting to give MuseScore 2 a spin :).

I don't have any plans, I just read the pkg-multimedia mailing list. ;)

Cheers,

Fabian


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

Bug#791346: fresh upstream release available (1.3.3) and needed for ITP tigervnc

[Yaroslav Halchenko]

On Tue, 07 Jul 2015, Aaron M. Ucko wrote:
> > But what I wanted to say is just thanks for maintaining and use whatever
> > means you find most comfortable for you -- My cry was out of the
> > moment of weakness I guess ;)

> Don't worry, no offense taken.  What does concern me is that, despite
> claiming to be ABI-compatible with previous 1.3.x releases by default,
> 1.3.3 omits some symbols that they defined.  (I guess FLTK's developers
> consider it sufficient to preserve class and virtual table layouts.)

> As such, I'm tempted to go ahead and activate assorted new features that
> are disabled by default to avoid totally breaking ABI compatibility, as
> described at http://www.fltk.org/cmp.php#FLTK_ABI_VERSION.  I would then
> of course rename the runtime library packages accordingly, calling for a
> trip through NEW.

or we could check if may be none of rdepends use any of those (and their
rebuild might be the only thing needed to stay safe)?  I could run
quickly rebuild of all build/rdepends if you gimme perspective package
which doesn't even bring up the dead things alive? ;)

-- 
Yaroslav O. Halchenko, Ph.D.
http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org
Research Scientist,Psychological and Brain Sciences Dept.
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791475: bup: Unable to restore an emacs autosave file #.fetchmailrc#

[David Creelman]

Hi Rob,
I ran as root.
I had previously tried to run as my normal user, but I got an error about
not being able to access my own home dir, so I (perhaps a little heavy
handedly) simply did it all as root.
I'll try the --exclude and I'll do a bup ls too. I can't get to it right
now (external drive at home), so I'll try later on tonight (I'm at work
now).
The drive is a 500gb drive formatted to ext4.
The original file is kind of sensitive (contains passwords and such).
Having said that, it's just vanilla text. Nothing odd in it at first glance.
It's ls -l is
-rwx-- 1 davidc davidc 833 Jan 20 23:42 /home/davidc/#.fetchmailrc#*
file gives
/home/davidc/#.fetchmailrc#: ASCII text
Thanks for your help.
I'll get onto the bup suggestions (ls & --exclude) as soon as I can.
Regards,
David



On Tue, 7 Jul 2015 at 12:25 Rob Browning  wrote:

> Robert Edmonds  writes:
>
> > I'm not quite sure what the issue is here, so I've Cc'd the upstream bup
> > mailing list.  It looks like one of the ioctl() calls in the
> > bup_set_linux_file_attr() function is failing.
> >
> > Did you run the 'bup restore' as a regular user or as root?
> >
> > What is the type of the filesystem that you're attempting to restore to?
>
> Both good questions.  For example, right now bup's handling of
> differences between the source and destination filesystems could
> likely use improvement.
>
> >>   File "/usr/lib/bup/bup/metadata.py", line 611, in
> _apply_linux_attr_rec
> >> set_linux_file_attr(path, self.linux_attr)
> >> OSError: [Errno 22] Invalid argument: 'redacted/#.fetchmailrc#
>
> Any chance you still have the file around, and if so, assuming the
> output isn't sensitive, I wonder what "ls -l", "stat" and "lsattr" say
> about it?
>
> And even if you don't still have it in the filesystem, I wonder what
> these commands say:
>
>   bup ls -l home-dir/latest/home/redacted/#.fetchmailrc#
>
>   bup cat-file --meta home-dir/latest/home/redacted/#.fetchmailrc# \
> bup meta -tvvf -
>
> >> I am guessing that filenames containing hashes are not liked by bup?
> >> This means I won't be able to back up any folders containing emacs
> edited files.
> >> #file# style files are used regularly by emacs.
>
> I'm fairly sure that normally #file# should be handled without any
> trouble.  I think there's something else going on here.
>
> >> Should you require more details (or if I've missed something obvious to
> get around this
> >> issue) please let me know.
>
> I wonder if adding this to the restore might provide a workaround for
> now:
>
>   --exclude-rx '^/redacted/#\.fetchmailrc#$'
>
> Or perhaps:
>
>   --exclude-rx '^redacted/#\.fetchmailrc#$'
>
> Not sure which one is correct offhand.
>
> Hope this helps
> --
> 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#744304: Still a problem in Jessie

[Steven Ihde]

control: severity -1 important

This is a significant regression for Jessie. If the admin relied on 
RESOLVCONF=yes in /etc/default/bind9, the host will lose access to all names 
provided by the local named. This could cause any number of failures depending 
on the nature of the dependency. Please consider fixing this in Jessie ASAP.

Thanks,

Steve


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791346: fresh upstream release available (1.3.3) and needed for ITP tigervnc

[Aaron M. Ucko]

Yaroslav Halchenko  writes:

> But what I wanted to say is just thanks for maintaining and use whatever
> means you find most comfortable for you -- My cry was out of the
> moment of weakness I guess ;)

Don't worry, no offense taken.  What does concern me is that, despite
claiming to be ABI-compatible with previous 1.3.x releases by default,
1.3.3 omits some symbols that they defined.  (I guess FLTK's developers
consider it sufficient to preserve class and virtual table layouts.)

As such, I'm tempted to go ahead and activate assorted new features that
are disabled by default to avoid totally breaking ABI compatibility, as
described at http://www.fltk.org/cmp.php#FLTK_ABI_VERSION.  I would then
of course rename the runtime library packages accordingly, calling for a
trip through NEW.

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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791633: Can't anything bad be detected when given gibberish?

[積丹尼 Dan Jacobson]

OK. I opened https://github.com/systemd/systemd/issues/504 .


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#780998: Emacs fails to resize with remote X session

[Nick Phillips]

Additional info here - this only seems to be a problem (for me) when the
remote machine is running Jessie's Emacs24 and the client is running
Ubuntu.

My desktop is running Ubuntu 15.04. When the remote machine is running
Emacs24 on wheezy (emacs-snapshot package from BPO version
2:20140701-1~bpo70+1) the window resizes fine. When the remote host is
running Emacs24 on Jessie (emacs24 package version 24.4+1-5), problem is
present.

When the client is a Raspberry Pi running their version of wheezy, there
is no problem resizing emacs24 running remotely on either Ubuntu 15.04
or Jessie.

I'm sorry, I don't have a vanilla Wheezy or Jessie desktop to test as
client.


Cheers,


Nick
-- 
Nick Phillips / nick.phill...@otago.ac.nz / 03 479 4195
# These statements are mine, not those of the University of Otago

Bug#600661: ntp: Uses /var/lib/ntp/ntp.conf.dhcp regardless!?

[Simon Deziel]

I ran into this too but on Ubuntu and filed [1] before noticing this
Debian bug.

I believe that [2, also attached here] might be a simple yet working
solution. It changes the initscript to use /var/lib/ntp/ntp.conf.dhcp
only if it is newer than /etc/ntp.conf.

This should keep the dhclient hook script working as it always updates
the ntp.conf.dhcp file when a NTP server is advertised via DHCP.

Regards,
Simon


1: https://bugs.launchpad.net/debian/+source/ntp/+bug/1472056
2:
https://bugs.launchpad.net/debian/+source/ntp/+bug/1472056/+attachment/4425385/+files/ntp-dont-use-stale-dhcp-conf.patch
--- /etc/init.d/ntp.orig	2015-07-06 22:21:33.70136 -0400
+++ /etc/init.d/ntp	2015-07-06 22:55:01.128497327 -0400
@@ -22,7 +22,7 @@
 	. /etc/default/ntp
 fi
 
-if [ -e /var/lib/ntp/ntp.conf.dhcp ]; then
+if [ /var/lib/ntp/ntp.conf.dhcp -nt /etc/ntp.conf ]; then
 	NTPD_OPTS="$NTPD_OPTS -c /var/lib/ntp/ntp.conf.dhcp"
 fi
 

Bug#791640: fail2ban: refuses to start when no files are found for a glob in logpath

[Yaroslav Halchenko]

On Tue, 07 Jul 2015, Vincent Lefevre wrote:
> > > The /var/log/syslog file is more complete and gives the reason of
> > > the error:

> > > Jul  7 03:37:24 zira fail2ban-client[789]: ERROR  No file(s) found for 
> > > glob /var/log/apache*/*error.log
> > > Jul  7 03:37:24 zira fail2ban-client[789]: ERROR  Failed during 
> > > configuration: Have not found any log file for apache-noadmin jail

> > > fail2ban should not refuse to start, but just ignore the jail in such
> > > a case (possibly with some kind of warning).

> > you say potato and I say potato --  you say "should not", and I say
> > "should" ;-)  This is a feature to avoid causing a false sense of
> > protection.  If you configure a jail to monitor some files, they must be
> > there, otherwise fail2ban would not pick them up anyhow later and that
> > jail will never be "in effect", although you might be thinking that it
> > is.  So consider it a feature.

> No! This is not documented, thus it is not a feature! At least when
> the user has no way to know that.

> The problem is that fail2ban doesn't offer any protection at all
> because it fails silently. So, instead of possibly having one thing
> broken, one has everything broken!!! There should be a way for the
> user to know (without any special action on his part) that fail2ban
> could not start.

brr -- didn't you get a log stating that it failed to start and a reason
for the failure stated (as you quoted above)?

> > As a workaround you might like to configure your logrotation to
> > re-create empty files (create configuration option in your logrotate
> > configs).

> apache2 isn't installed yet, so that it would not be possible.

so disable that jail then!

-- 
Yaroslav O. Halchenko, Ph.D.
http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org
Research Scientist,Psychological and Brain Sciences Dept.
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#730697: gnome-packagekit: Same happens with xfce in some installations

[Marcelo Lacerda]

Package: gnome-packagekit
Version: 3.14.0-1
Followup-For: Bug #730697

Dear Maintainer,

In at least one installation of jessie I have a similar problem: The
command line tool gpk-repo does not exist and gpk-prefs behaves as
gpk-repo should. Moreover an option to configure gnome-packagekit(the
update schedule) does not appear in xfce menu.

In another installation of xfce4(at work(under jessie)) this option appear.

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 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 gnome-packagekit depends on:
ii  gnome-packagekit-session  3.14.0-1
ii  libatk1.0-0   2.14.0-1
ii  libc6 2.19-18
ii  libcairo-gobject2 1.14.0-2.1
ii  libcairo2 1.14.0-2.1
ii  libcanberra-gtk3-00.30-2.1
ii  libcanberra0  0.30-2.1
ii  libdbus-1-3   1.8.18-0+deb8u1
ii  libdbus-glib-1-2  0.102-1
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.5.2-3
ii  libgdk-pixbuf2.0-02.31.1-2+b1
ii  libglib2.0-0  2.42.1-1
ii  libgtk-3-03.14.5-1
ii  libnotify40.7.6-2
ii  libpackagekit-glib2-181.0.1-2
ii  libpango-1.0-01.36.8-3
ii  libpangocairo-1.0-0   1.36.8-3
ii  libsqlite3-0  3.8.7.1-1+deb8u1
ii  libx11-6  2:1.6.2-3

gnome-packagekit recommends no packages.

gnome-packagekit suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791640: fail2ban: refuses to start when no files are found for a glob in logpath

[Vincent Lefevre]

Control: reopen 791640
Control: retitle 791640 fail2ban should report an error when it cannot start

On 2015-07-06 22:24:41 -0400, Yaroslav Halchenko wrote:
> On Tue, 07 Jul 2015, Vincent Lefevre wrote:
> > The /var/log/syslog file is more complete and gives the reason of
> > the error:
> 
> > Jul  7 03:37:24 zira fail2ban-client[789]: ERROR  No file(s) found for glob 
> > /var/log/apache*/*error.log
> > Jul  7 03:37:24 zira fail2ban-client[789]: ERROR  Failed during 
> > configuration: Have not found any log file for apache-noadmin jail
> 
> > fail2ban should not refuse to start, but just ignore the jail in such
> > a case (possibly with some kind of warning).
> 
> you say potato and I say potato --  you say "should not", and I say
> "should" ;-)  This is a feature to avoid causing a false sense of
> protection.  If you configure a jail to monitor some files, they must be
> there, otherwise fail2ban would not pick them up anyhow later and that
> jail will never be "in effect", although you might be thinking that it
> is.  So consider it a feature.

No! This is not documented, thus it is not a feature! At least when
the user has no way to know that.

The problem is that fail2ban doesn't offer any protection at all
because it fails silently. So, instead of possibly having one thing
broken, one has everything broken!!! There should be a way for the
user to know (without any special action on his part) that fail2ban
could not start.

> As a workaround you might like to configure your logrotation to
> re-create empty files (create configuration option in your logrotate
> configs).

apache2 isn't installed yet, so that it would not be possible.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791642: Probably not a pulseaudio bug

[Andrew Kane]

I plugged a cable into the "Headphone" jack and poked the other end
with my finger. I heard the telltale buzz in the headphones which
leads me to suspect that the "Headphone" jack is in fact a Line-in.

Since alsamixer reports this jack as a Headphone jack as well, I
suspect that this is not a bug in pavucontrol nor pulseaudio after
all, but in alsa. I will reassign it.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791642: remapping failed

[Andrew Kane]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

I tried remapping the rear audio ports using a tool called
hda-jack-retask. That tool reported the port in question as a Line-in
port. (It even identifies the ports by color, though I'm not convinced
that that identification is correct.)

The attempted remapping had no effect on the audio nor on
pavucontrol's labelling of the port.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJVmz1/AAoJEAa852fG4/6BA0IH/jQdDnvIfsBbjuUg2oZj2nq7
RwhEV/p22akqa3bArjQzenzmdXu321S4o9cgqs/mMxH780yhwPAvqG7ARyu5Do7u
ja32iB9A2gnKd5pfcWP50ybQHhfnUeKaRfA/CMgikesXzxvjUOAnwvVbWAxGahpv
0TLtJxwHHQQyfnHR2iPfcSL2uwBJi6Qkdsgjn6V6IVGKPXw4j3cLc23/w2O6+kea
b2rlvz+7oF+WuCIM7qLKjrzQc5Y9HjF/iCxFnB51It/q3h/m8TU+cHtGCvtWJKl4
8IbYd0DOZ2O2Bb5SQKuNdsyDbvBvtKxpI3hRf63ks9j9WRuBLmE4UxIlUfgZ3zk=
=XZmR
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791638: update bug 791638

[Jesse Molina]

Now this is weird and interesting...

If I change the "AllowGroups root users" line to "AllowGroups root users 
baduser", everything works as expected.


Note that user baduser is in both groups baduser and users.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791475: bup: Unable to restore an emacs autosave file #.fetchmailrc#

[Rob Browning]

Robert Edmonds  writes:

> I'm not quite sure what the issue is here, so I've Cc'd the upstream bup
> mailing list.  It looks like one of the ioctl() calls in the
> bup_set_linux_file_attr() function is failing.
>
> Did you run the 'bup restore' as a regular user or as root?
>
> What is the type of the filesystem that you're attempting to restore to?

Both good questions.  For example, right now bup's handling of
differences between the source and destination filesystems could
likely use improvement.

>>   File "/usr/lib/bup/bup/metadata.py", line 611, in _apply_linux_attr_rec
>> set_linux_file_attr(path, self.linux_attr)
>> OSError: [Errno 22] Invalid argument: 'redacted/#.fetchmailrc#

Any chance you still have the file around, and if so, assuming the
output isn't sensitive, I wonder what "ls -l", "stat" and "lsattr" say
about it?

And even if you don't still have it in the filesystem, I wonder what
these commands say:

  bup ls -l home-dir/latest/home/redacted/#.fetchmailrc#

  bup cat-file --meta home-dir/latest/home/redacted/#.fetchmailrc# \
bup meta -tvvf -

>> I am guessing that filenames containing hashes are not liked by bup?
>> This means I won't be able to back up any folders containing emacs edited 
>> files.
>> #file# style files are used regularly by emacs.

I'm fairly sure that normally #file# should be handled without any
trouble.  I think there's something else going on here.

>> Should you require more details (or if I've missed something obvious to get 
>> around this
>> issue) please let me know.

I wonder if adding this to the restore might provide a workaround for
now:

  --exclude-rx '^/redacted/#\.fetchmailrc#$'

Or perhaps:

  --exclude-rx '^redacted/#\.fetchmailrc#$'

Not sure which one is correct offhand.

Hope this helps
-- 
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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791638: update bug 791638

[Jesse Molina]

Just to be clear, user "baduser" is in group "users".

I'm still testing. I'm not sure that this is a comment issue so much as 
the interpreter is just breaking due to something else. It seems to die 
after the "GatewayPorts no" line. Any additional configuration lines 
seem to cause the client to not authneticate. Debug output shows 
nothing; it just stops reading the config at that line.


There is something wrong, but I am not sure what it is.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791642: pavucontrol: reports incorrect output device information

[Andrew Kane]

Package: pavucontrol
Version: 3.0-3
Severity: normal

Dear Maintainer,

My motherboard has 3 rear audio ports. pavucontrol reports one of them as a mic 
jack, and the other two as Line-Out and Headphones.
I can't verify that this report is correct, because I can't read the symbols on 
the motherboard riser where the jacks plug in.

I have a headphone amplifier and a set of amplified loudspeakers. I would drive 
them separately using the Line Out for the speakers and Headphones for the 
headphones.

When I plug the input of my headphone amplifier to Headphones pavucontrol 
reports it as unplugged. 
When I swap the Headphone and Line Out inputs pavucontrol reports the 
Headphones output unplugged.
When I plug the headphones directly into the Line Out port I get sound; when I 
plug them into the Headphone jack I get no sound.
Regardless of the disposition of the plugs, switching between the Headphone and 
Line Out devices in pavucontrol only changes the level of the output on the 
device plugged into Line Out; the one plugged into Headphone is unaffected.


I suspect that what's happening is that the jack which pavucontrol reports as a 
Headphone port is actually an input port (presumably a Line In, since there's 
already a Microphone port.)
I don't know why pavucontrol is controlling the level of the same output under 
the labels of two separate outputs.
I will try to remap the port which pavucontrol calls a Headphone port so that 
it really is one, if I can figure out how to do so, and append to this report 
if I am successful.

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

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

Versions of packages pavucontrol depends on:
ii  libatk1.0-0  2.16.0-2
ii  libatkmm-1.6-1   2.22.7-2.1
ii  libc62.19-18
ii  libcairo-gobject21.14.2-2
ii  libcairo21.14.2-2
ii  libcairomm-1.0-1 1.10.0-1.1
ii  libcanberra-gtk3-0   0.30-2.1
ii  libcanberra0 0.30-2.1
ii  libgcc1  1:5.1.1-12
ii  libgdk-pixbuf2.0-0   2.31.4-2
ii  libglib2.0-0 2.44.1-1.1
ii  libglibmm-2.4-1c2a   2.44.0-1
ii  libgtk-3-0   3.16.4-2
ii  libgtkmm-3.0-1   3.16.0-1
ii  libpango-1.0-0   1.36.8-3
ii  libpangocairo-1.0-0  1.36.8-3
ii  libpangomm-1.4-1 2.36.0-1
ii  libpulse-mainloop-glib0  6.0-2
ii  libpulse06.0-2
ii  libsigc++-2.0-0c2a   2.4.1-1
ii  libstdc++6   5.1.1-12
ii  libx11-6 2:1.6.3-1

Versions of packages pavucontrol recommends:
ii  pulseaudio  6.0-2

pavucontrol suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#651606: put this shiny link in a convenient place

[Balasankar C]

On 7 July 2015 1:15:20 am IST, Mattia Rizzolo  wrote:
>On Mon, Jul 06, 2015 at 10:32:15PM +0530, Balasankar C wrote:
>> I couldn't really understand what you were suggesting. If it was to
>> host the progress bar at some d.o location, I am sorry - I can't do
>> that since I'm not a DD yet. But, I would be more than happy to share
>> the source code for generating this progressbar if some DD wishes to
>> do that.
>
>nah, nothing like that.
>I'm completly fine with the current location, I just wanted to put the
>link in
>a more conveniente (at least for me) place, that is, the "forwarded"
>field of
>this bug. Look at the top of the bug page, it's now there.
>
>[ strip some tech details about the implementation of that page :) ]
>> @Praveen, can you host it in your people.d.o webspace?
>
>I don't see the need for this, really!
>
>> PS : I am gonna keep this webpage active even if we get a d.o
>address,
>> just as a fallback location. I am running a cron script to update it
>> weekly. :)
>
>umh, if I were you I'd run that more often, maybe even daily. It
>doesn't sound
>like something resource heavy, and I like to see up-to-date web pages
>:)
>
>
>-- 
>regards,
>Mattia Rizzolo
>
>GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540
>.''`.
>more about me:  http://mapreri.org : :'
> :
>Launchpad user: https://launchpad.net/~mapreri `.
>`'`
>Debian QA page: https://qa.debian.org/developer.php?login=mattia `-

Ah. Ok. I misinterpreted your mail.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#791633: Can't anything bad be detected when given gibberish?

[Michael Biebl]

Am 07.07.2015 um 03:52 schrieb Michael Biebl:

> Am 07.07.2015 um 02:45 schrieb 積丹尼 Dan Jacobson:
>> Package: systemd
>> Version: 221-1
>> Severity: wishlist
>> File: /bin/systemctl
>>
>> Can't anything bad be detected when given e.g.,
>>
>> # systemctl disable .servicez ; echo $?
>> 0
> 
> You filed the same bug already as #764267

As Marco already said in [1]:
"We have no plan to change this behaviour of the upstream package.
If you feel that it is inappropriate then I recommend that you discuss
this on the upstream mailing list."

This is not a downstream distro integration issue, thus should be fixed
upstream. Please file a bug at https://github.com/systemd/systemd

Michael

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764267#10
-- 
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#791641: [PATCH 1/1] url_set_postdata: include terminator in allocation

[Rob Browning]

Package: siege
Version: 3.0.8-1
Forwarded: Jeffrey Fulmer 

Fix a potential segfault in url_set_postdata by including a byte for
the null terminator when allocating the result, and switch to xmalloc
to catch allocation failures.

---

 The psuedo-headers above are just for the Debian bug tracker, and can
 of course be removed.  In any case, hope this helps.

 src/url.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/url.c b/src/url.c
index 191ba55..98f09a3 100644
--- a/src/url.c
+++ b/src/url.c
@@ -182,7 +182,7 @@ url_set_postdata(URL this, char *postdata, size_t postlen)
   this->postlen = postlen;
 
   if (strlen(postdata) > 0) {
-this->postdata = malloc(this->postlen);
+this->postdata = xmalloc(this->postlen + 1);
 memcpy(this->postdata, postdata, this->postlen);
 this->postdata[this->postlen] = 0;
   }
-- 
2.1.4


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791640: fail2ban: refuses to start when no files are found for a glob in logpath

[Vincent Lefevre]

Package: fail2ban
Version: 0.9.2-1
Severity: normal

I get the following:

$ systemctl status fail2ban.service -l -n 20
● fail2ban.service - Fail2Ban Service
   Loaded: loaded (/lib/systemd/system/fail2ban.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: start-limit) since Tue 2015-07-07 03:37:26 CEST; 
13min ago
 Docs: man:fail2ban(1)
  Process: 1260 ExecStart=/usr/bin/fail2ban-client -x start (code=exited, 
status=255)

Jul 07 03:37:25 zira systemd[1]: Failed to start Fail2Ban Service.
Jul 07 03:37:25 zira systemd[1]: fail2ban.service: Unit entered failed state.
Jul 07 03:37:25 zira systemd[1]: fail2ban.service: Failed with result 
'exit-code'.
Jul 07 03:37:26 zira systemd[1]: fail2ban.service: Service hold-off time over, 
scheduling restart.
Jul 07 03:37:26 zira systemd[1]: fail2ban.service: Start request repeated too 
quickly.
Jul 07 03:37:26 zira systemd[1]: Failed to start Fail2Ban Service.
Jul 07 03:37:26 zira systemd[1]: fail2ban.service: Unit entered failed state.
Jul 07 03:37:26 zira systemd[1]: fail2ban.service: Failed with result 
'start-limit'.

The /var/log/syslog file is more complete and gives the reason of
the error:

Jul  7 03:37:24 zira fail2ban-client[789]: ERROR  No file(s) found for glob 
/var/log/apache*/*error.log
Jul  7 03:37:24 zira fail2ban-client[789]: ERROR  Failed during configuration: 
Have not found any log file for apache-noadmin jail

fail2ban should not refuse to start, but just ignore the jail in such
a case (possibly with some kind of warning).

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, 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 fail2ban depends on:
ii  init-system-helpers  1.23
ii  lsb-base 4.1+Debian13+nmu1
ii  python3  3.4.3-4
pn  python3:any  

Versions of packages fail2ban recommends:
ii  iptables   1.4.21-2+b1
ii  python 2.7.9-1
ii  python3-pyinotify  0.9.5-1
ii  python3-systemd221-1
ii  whois  5.2.9

Versions of packages fail2ban suggests:
ii  bsd-mailx [mailx]8.1.2-0.20150408cvs-1
pn  monit
ii  rsyslog [system-log-daemon]  8.11.0-1

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791633: Can't anything bad be detected when given gibberish?

[Michael Biebl]

Control: forcemerge 764267 -1

Am 07.07.2015 um 02:45 schrieb 積丹尼 Dan Jacobson:
> Package: systemd
> Version: 221-1
> Severity: wishlist
> File: /bin/systemctl
> 
> Can't anything bad be detected when given e.g.,
> 
> # systemctl disable .servicez ; echo $?
> 0

You filed the same bug already as #764267


-- 
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#791639: zenity: Zenity faulty return values in version 3.4.0-2 in Debian 7.8

[Wim]

Package: zenity
Version: 3.4.0-2
Severity: important

Dear Maintainer,

   * What led up to the situation?
See https://bugzilla.gnome.org/show_bug.cgi?id=749832
   * What exactly did you do (or not do) that was effective (or ineffective)?
See https://bugzilla.gnome.org/show_bug.cgi?id=749832
   * What was the outcome of this action?
See https://bugzilla.gnome.org/show_bug.cgi?id=749832
   * What outcome did you expect instead?
See https://bugzilla.gnome.org/show_bug.cgi?id=749832

Debian 7.8 has zenity version (3.4.0-2).
I wonder why is it not updated to a newer version via the update proces?
This version of zenity has a bug which makes it unusefull
in some applications. See https://bugzilla.gnome.org/show_bug.cgi?id=749832 .
If updateted via the update process all the people who suffer under this
bug will be saved a lot of extra work. Thanks.


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

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

Versions of packages zenity depends on:
ii  libc6   2.13-38+deb7u8
ii  libgdk-pixbuf2.0-0  2.26.1-1
ii  libglib2.0-02.33.12+really2.32.4-5
ii  libgtk-3-0  3.4.2-7
ii  libnotify4  0.7.5-1
ii  libpango1.0-0   1.30.0-1
ii  libwebkitgtk-3.0-0  1.8.1-3.4
ii  libx11-62:1.5.0-1+deb7u2
ii  zenity-common   3.4.0-2

zenity recommends no packages.

zenity suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791638: openssh-server: Comment lines breaking configuration; 'match user' block being broken by comment lines

[Jesse Molina]

Package: openssh-server
Version: 1:6.7p1-6
Severity: normal

Since yesterday I have been experimenting with strange sshd_config behavior. 
After testing extensively, I believe that comment lines are somehow breaking my 
configuration.

My sshd_config is below:

--

# Package generated configuration file
# See the sshd_config(5) manpage for details

# What ports, IPs and protocols we listen for
Port 22
# Use these options to restrict which interfaces/protocols sshd will bind to
#ListenAddress ::
#ListenAddress 0.0.0.0
Protocol 2
# HostKeys for protocol version 2
HostKey /etc/ssh/ssh_host_rsa_key
HostKey /etc/ssh/ssh_host_dsa_key
HostKey /etc/ssh/ssh_host_ecdsa_key
HostKey /etc/ssh/ssh_host_ed25519_key
#Privilege Separation is turned on for security
UsePrivilegeSeparation yes

# Lifetime and size of ephemeral version 1 server key
KeyRegenerationInterval 3600
ServerKeyBits 1024

# Logging
SyslogFacility AUTH
# LogLevel INFO
LogLevel DEBUG3

# Authentication:
LoginGraceTime 120
# PermitRootLogin without-password
PermitRootLogin yes
StrictModes yes

RSAAuthentication yes
PubkeyAuthentication yes
#AuthorizedKeysFile %h/.ssh/authorized_keys

# Don't read the user's ~/.rhosts and ~/.shosts files
IgnoreRhosts yes
# For this to work you will also need host keys in /etc/ssh_known_hosts
RhostsRSAAuthentication no
# similar for protocol version 2
HostbasedAuthentication no
# Uncomment if you don't trust ~/.ssh/known_hosts for RhostsRSAAuthentication
#IgnoreUserKnownHosts yes

# To enable empty passwords, change to yes (NOT RECOMMENDED)
PermitEmptyPasswords no

# Change to yes to enable challenge-response passwords (beware issues with
# some PAM modules and threads)
ChallengeResponseAuthentication no

# Change to no to disable tunnelled clear text passwords
#PasswordAuthentication yes

# Kerberos options
#KerberosAuthentication no
#KerberosGetAFSToken no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes

# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes

X11Forwarding yes
X11DisplayOffset 10
PrintMotd no
PrintLastLog yes
TCPKeepAlive yes
#UseLogin no

#MaxStartups 10:30:60
#Banner /etc/issue.net

# Allow client to pass locale environment variables
AcceptEnv LANG LC_*

Subsystem sftp /usr/lib/openssh/sftp-server

# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication and
# PasswordAuthentication.  Depending on your PAM configuration,
# PAM authentication via ChallengeResponseAuthentication may bypass
# the setting of "PermitRootLogin without-password".
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and ChallengeResponseAuthentication to 'no'.
UsePAM yes

# --

# Process order: DenyUsers, AllowUsers, DenyGroups, AllowGroups.
#DenyUsers
#AllowUsers
#DenyGroups
AllowGroups root users


ClientAliveInterval 15
ClientAliveCountMax 8

PermitOpen none

match group root, group users
PermitOpen any

match user badtouch
PermitOpen none
AuthenticationMethods publickey
AllowTcpForwarding no
PermitTunnel no
GatewayPorts no
# X11Forwarding no
# AllowAgentForwarding no
# PermitTTY no
# ForceCommand echo nope

# foo

# bar


--

In this condition, the baduser user is not able to log in/authenticate and ssh 
client exits 255.

However, if we delete the lines under "GatewayPorts no" the user is then able 
to log in and execute commands.

I strongly suspect there is something wrong with the "match" block config 
interpreter. I am having other problems with match blocks on another host, very 
similar to bug 629853. 

Debugging output indicates there is definitely something stopping the 
interpreter. There is a clear differnce in debug output when the comment lines 
at the end of the file are removed.


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

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

Versions of packages openssh-server depends on:
ii  adduser3.113+nmu3
ii  debconf [debconf-2.0]  1.5.56
ii  dpkg   1.18.1
ii  init-system-helpers1.23
ii  libc6  2.19-18
ii  libcomerr2 1.42.13-1
ii  libgssapi-krb5-2   1.13.2+dfsg-2
ii  libkrb5-3  1.13.2+dfsg-2
ii  libpam-modules 1.1.8-3.1
ii  libpam-runtime 1.1.8-3.1
ii  libpam0g   1.1.8-3.1
ii  libselinux12.3-2+b1
ii  libssl1.0.01.0.2c-1
ii  libwrap0   7.6.q-25
ii  lsb-base   4.1+Debian13+nmu1
ii  openssh-client 1:6.7p1-6
ii  openssh-sftp-server1:6.7p1-6
ii  procps 

Bug#791637: nmu: rebuild packages against gtk-doc-tools 1.24

[Michael Biebl]

Control: retitle -1 "nmu: rebuild packages against gtk-doc-tools 1.24"

The bug title was supposed to say gtk-doc-tools 1.24, not 1.23.
-- 
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#791637: nmu: rebuild packages against gtk-doc-tools 1.23

[Michael Biebl]

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

Hi,

gtk-doc-tools 1.23 produced broken documentation [1].
This was quickly fixed by a followup upload of gtk-doc-tools.
Nonetheless, quite a few packages were built against this broken
version. A simple binNMU fixes this problem.
I've grepped the build-logs and filtered out packages which have been
built in the mean time the result list is as follows.



nmu atril_1.8.1+dfsg1-5 . i386 powerpc arm64 s390x armel hurd-i386 ppc64el 
armhf mipsel mips sparc kfreebsd-amd64 kfreebsd-i386  . -m "Rebuild against 
gtk-doc-tools 1.24"
nmu brasero_3.12.1-1 . sparc kfreebsd-amd64 kfreebsd-i386  . -m "Rebuild 
against gtk-doc-tools 1.24"
nmu caribou_0.4.18.1-1 . kfreebsd-amd64 kfreebsd-i386  . -m "Rebuild against 
gtk-doc-tools 1.24"
nmu cheese_3.16.1-1 . sparc kfreebsd-amd64 kfreebsd-i386  . -m "Rebuild against 
gtk-doc-tools 1.24"
nmu cogl_1.20.0-2 . kfreebsd-amd64 kfreebsd-i386  . -m "Rebuild against 
gtk-doc-tools 1.24"
nmu d-conf_0.24.0-2 . kfreebsd-amd64 kfreebsd-i386  . -m "Rebuild against 
gtk-doc-tools 1.24"
nmu eog_3.16.2-1 . kfreebsd-amd64 kfreebsd-i386  . -m "Rebuild against 
gtk-doc-tools 1.24"
nmu exo_0.10.6-1 . kfreebsd-amd64 kfreebsd-i386  . -m "Rebuild against 
gtk-doc-tools 1.24"
nmu gcr_3.16.0-1 . kfreebsd-amd64 kfreebsd-i386  . -m "Rebuild against 
gtk-doc-tools 1.24"
nmu gdk-pixbuf_2.31.4-2 . kfreebsd-i386 kfreebsd-amd64  . -m "Rebuild against 
gtk-doc-tools 1.24"
nmu gnome-desktop3_3.16.2-2 . i386 s390x ppc64el arm64 armhf powerpc armel 
hurd-i386 mipsel mips sparc kfreebsd-amd64 kfreebsd-i386  . -m "Rebuild against 
gtk-doc-tools 1.24"
nmu gobject-introspection_1.44.0-1 . ppc64el s390x powerpc hurd-i386 arm64 
mipsel armel armhf sparc mips  . -m "Rebuild against gtk-doc-tools 1.24"
nmu gobject-introspection_1.44.0-1+b1 . i386 amd64  . -m "Rebuild against 
gtk-doc-tools 1.24"
nmu gtkspell3_3.0.7-2 . i386 powerpc s390x kfreebsd-amd64 arm64 ppc64el sparc 
mipsel armhf armel hurd-i386  . -m "Rebuild against gtk-doc-tools 1.24"
nmu gtranslator_2.91.7-1 . sparc kfreebsd-i386  . -m "Rebuild against 
gtk-doc-tools 1.24"
nmu gucharmap_1:3.16.2-1 . kfreebsd-amd64 kfreebsd-i386  . -m "Rebuild against 
gtk-doc-tools 1.24"
nmu gupnp_0.20.14-1 . kfreebsd-i386 kfreebsd-amd64  . -m "Rebuild against 
gtk-doc-tools 1.24"
nmu gvfs_1.24.1-2+b1 . powerpc i386 powerpc amd64 armhf armel mipsel s390x mips 
 . -m "Rebuild against gtk-doc-tools 1.24"
nmu json-glib_1.0.4-1 . kfreebsd-i386 kfreebsd-amd64  . -m "Rebuild against 
gtk-doc-tools 1.24"
nmu libgit2-glib_0.22.8-1 . arm64 powerpc i386 s390x armel armhf ppc64el mipsel 
mips kfreebsd-amd64  . -m "Rebuild against gtk-doc-tools 1.24"
nmu libgpod_0.8.3-1.1+b2 . i386 powerpc amd64 armel armhf mipsel s390x sparc  . 
-m "Rebuild against gtk-doc-tools 1.24"
nmu libgpod_0.8.3-1.1+b3 . kfreebsd-i386 kfreebsd-amd64  . -m "Rebuild against 
gtk-doc-tools 1.24"
nmu libgweather_3.16.1-1 . kfreebsd-amd64 kfreebsd-i386  . -m "Rebuild against 
gtk-doc-tools 1.24"
nmu libinfinity_0.6.6-1 . kfreebsd-amd64 kfreebsd-i386  . -m "Rebuild against 
gtk-doc-tools 1.24"
nmu libmatekbd_1.8.1-2 . kfreebsd-amd64 kfreebsd-i386  . -m "Rebuild against 
gtk-doc-tools 1.24"
nmu librest_0.7.93-1 . hurd-i386  . -m "Rebuild against gtk-doc-tools 1.24"
nmu librsvg_2.40.9-2 . kfreebsd-amd64 kfreebsd-i386  . -m "Rebuild against 
gtk-doc-tools 1.24"
nmu libsecret_0.18.2-1 . kfreebsd-amd64 kfreebsd-i386  . -m "Rebuild against 
gtk-doc-tools 1.24"
nmu mate-desktop_1.8.2+dfsg1-3 . kfreebsd-amd64 kfreebsd-i386  . -m "Rebuild 
against gtk-doc-tools 1.24"
nmu mate-media_1.8.0+dfsg1-4 . kfreebsd-amd64 kfreebsd-i386  . -m "Rebuild 
against gtk-doc-tools 1.24"
nmu mate-netbook_1.8.2-2 . kfreebsd-amd64 kfreebsd-i386  . -m "Rebuild against 
gtk-doc-tools 1.24"
nmu mate-notification-daemon_1.8.2-2 . kfreebsd-amd64 kfreebsd-i386  . -m 
"Rebuild against gtk-doc-tools 1.24"
nmu mate-session-manager_1.8.2-3 . kfreebsd-amd64 kfreebsd-i386  . -m "Rebuild 
against gtk-doc-tools 1.24"
nmu mate-settings-daemon_1.8.3-3 . kfreebsd-amd64 kfreebsd-i386  . -m "Rebuild 
against gtk-doc-tools 1.24"
nmu mate-terminal_1.8.1+dfsg1-5 . kfreebsd-amd64 kfreebsd-i386  . -m "Rebuild 
against gtk-doc-tools 1.24"
nmu mate-user-share_1.8.1+dfsg1-2 . kfreebsd-amd64 kfreebsd-i386  . -m "Rebuild 
against gtk-doc-tools 1.24"
nmu nautilus_3.14.2-1 . kfreebsd-amd64 kfreebsd-i386  . -m "Rebuild against 
gtk-doc-tools 1.24"
nmu oath-toolkit_2.6.0-1 . kfreebsd-amd64  . -m "Rebuild against gtk-doc-tools 
1.24"
nmu osm-gps-map_1.0.2-3 . kfreebsd-amd64 kfreebsd-i386  . -m "Rebuild against 
gtk-doc-tools 1.24"
nmu seahorse_3.16.0-1 . sparc kfreebsd-amd64 kfreebsd-i386  . -m "Rebuild 
against gtk-doc-tools 1.24"
nmu thunar_1.6.10-1 . kfreebsd-amd64 kfreebsd-i386  . -m "Rebuild against 
gtk-doc-tools 1.24"
nmu tracker_1.4.0-3 . sparc  . -m "Rebuild against gtk-doc-tools 1.24"
nmu uhttpmock_0.4.0-1 . kfreebsd-amd64 kfreebsd-i386  . -m "Rebuild against 
gtk

Bug#778164: Patch for building under gcc5

[Potter, Tim (Cloud Services)]

tags 778164 + patch
thanks

Hi there.  Attached is a small patch to fix the build under gcc5.  The 
visibility of one of the functions in the yacc grammar is increased so the 
program links without error now.


Regards,

Tim.


778164-gcc5-fixes.patch
Description: Binary data


smime.p7s
Description: S/MIME cryptographic signature

Bug#791636: higan: Load and save state do not work without having focus

[Christian Weinz]

Package: higan
Version: 094-5
Severity: normal

Dear Maintainer,

when assigning save and load state to buttons on a gamepad they don't work when
higan doesn't have focus even when the option to allow input when focus is lost
is enabled.

I'd expect gamepad buttons to work for every assigned action even when focus is
lost.



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

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

Versions of packages higan depends on:
ii  libao41.1.0-3
ii  libasound21.0.29-1
ii  libatk1.0-0   2.16.0-2
ii  libc6 2.19-18
ii  libcairo2 1.14.2-2
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.5.2-4
ii  libgcc1   1:5.1.1-12
ii  libgdk-pixbuf2.0-02.31.4-2
ii  libgl1-mesa-glx [libgl1]  10.5.8-1
ii  libglib2.0-0  2.44.1-1.1
ii  libgtk2.0-0   2.24.28-1
ii  libopenal11:1.16.0-3
ii  libpango-1.0-01.36.8-3
ii  libpangocairo-1.0-0   1.36.8-3
ii  libpangoft2-1.0-0 1.36.8-3
ii  libpulse0 6.0-2
ii  libsdl1.2debian   1.2.15-11
ii  libstdc++65.1.1-12
ii  libudev1  221-1
ii  libx11-6  2:1.6.3-1
ii  libxext6  2:1.3.3-1
ii  libxv12:1.0.10-1+b1

higan recommends no packages.

higan suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791224: [Pkg-samba-maint] Bug#791224: openchange: library transition may be needed when GCC 5 is the default

[Steve Langasek]

Control: tags -1 confirmed

On Fri, Jul 03, 2015 at 01:13:14PM +, Matthias Klose wrote:
> Package: src:openchange
> Version: 2.2-7
> Severity: important
> Tags: sid stretch
> User: debian-...@lists.debian.org
> Usertags: libstdc++-cxx11

> Background [1]: libstdc++6 introduces a new ABI to conform to the
> C++11 standard, but keeps the old ABI to not break existing binaries.
> Packages which are built with g++-5 from experimental (not the one
> from testing/unstable) are using the new ABI.  Libraries built from
> this source package export some of the new __cxx11 or B5cxx11 symbols,
> and dropping other symbols.  If these symbols are part of the API of
> the library, then this rebuild with g++-5 will trigger a transition
> for the library.

> What is needed:

>  - Rebuild the library using g++/g++-5 from experimental. Note that
>most likely all C++ libraries within the build dependencies need
>a rebuild too. You can find the log for a rebuild in
>  https://people.debian.org/~doko/logs/gcc5-20150701/
>Search for "BEGIN GCC CXX11" in the log.

Here, for reference, is the list of cxx11-related symbols reported in the
build log (sed -n -e'/BEGIN GCC CXX11/,/END GCC CXX11/p' 
/tmp/openchange_2.2-7_unstable_gcc5.log |
c++filt):

= BEGIN GCC CXX11 symbols libmapipp0 
/usr/lib/x86_64-linux-gnu/libmapipp.so.2.2 =
  DF *UND*    GLIBCXX_3.4.21 
std::__cxx11::basic_string, std::allocator 
>::compare(char const*) const
  DF *UND*    GLIBCXX_3.4.21 
std::__cxx11::basic_string, std::allocator 
>::_M_append(char const*, unsigned long)
  DF *UND*    GLIBCXX_3.4.21 
std::__cxx11::basic_string, std::allocator 
>::_M_assign(std::__cxx11::basic_string, 
std::allocator > const&)
  DF *UND*    GLIBCXX_3.4.21 
std::__cxx11::basic_string, std::allocator 
>::swap(std::__cxx11::basic_string, 
std::allocator >&)
  DF *UND*    GLIBCXX_3.4.21 
std::__cxx11::basic_string, std::allocator 
>::_M_replace(unsigned long, unsigned long, char const*, unsigned long)
  DF *UND*    GLIBCXX_3.4.21 
std::__cxx11::basic_string, std::allocator 
>::_M_create(unsigned long&, unsigned long)
9620 gDF .text  033f  Base   
libmapipp::session::login(std::__cxx11::basic_string, std::allocator > const&, 
std::__cxx11::basic_string, std::allocator > 
const&)
6920  w   DF .text  018b  Base   
libmapipp::mapi_exception::mapi_exception(MAPISTATUS, 
std::__cxx11::basic_string, std::allocator > 
const&)
9270 gDF .text  00a4  Base   
libmapipp::profile_database::get_default_profile_path[abi:cxx11]()
9960 gDF .text  0362  Base   
libmapipp::session::session(std::__cxx11::basic_string, std::allocator > const&, bool)
9320 gDF .text  0236  Base   
libmapipp::profile_database::profile_database(std::__cxx11::basic_string, std::allocator > const&)
6920  w   DF .text  018b  Base   
libmapipp::mapi_exception::mapi_exception(MAPISTATUS, 
std::__cxx11::basic_string, std::allocator > 
const&)
9320 gDF .text  0236  Base   
libmapipp::profile_database::profile_database(std::__cxx11::basic_string, std::allocator > const&)
9230 gDF .text  0033  Base   
libmapipp::profile_database::create_profile_store(std::__cxx11::basic_string, std::allocator > const&, 
std::__cxx11::basic_string, std::allocator > 
const&)
9960 gDF .text  0362  Base   
libmapipp::session::session(std::__cxx11::basic_string, std::allocator > const&, bool)
9090 gDF .text  0144  Base   
libmapipp::profile_database::get_default_profile_name[abi:cxx11]()
= END GCC CXX11 symbols libmapipp0 
/usr/lib/x86_64-linux-gnu/libmapipp.so.2.2 =

>  - Decide if the symbols matching __cxx11 or B5cxx11 are part of the
>library API, and are used by the reverse dependencies of the
>library.

These are clearly part of the library API.

$ sudo apt-get install libmapipp-dev
$ grep 'login[[:space:]]*(' /usr/include/libmapi++/*
/usr/include/libmapi++/session.h:   void login(const std::string& 
profile_name = "", const std::string& password = "") throw(mapi_exception);
/usr/include/libmapi++/session.h:* Calling this method only 
makes sense if login() has been called with
$



>  - If there are no reverse dependencies, it should be the package
>maintainers decision if a transition is needed.  However this might
>break software which is not in the Debian archive, and built
>against these packages.

There are no reverse-dependencies of this package in the archive except for
libmapipp-dev, from the same 

Bug#791635: python-policy: Please require namespacing source python module packages

[Guillem Jover]

Source: python-defaults
Source-Version: 2.7.9-1
Severity: wishlist

Hi!

Given recent ITP discussions [0] about lack of namespacing on python
module source package names, I think it would be really good to fix
this at the source, by mandating it in the python-policy. Attached is
a proposal wording.

  [0] #748383: ITP: bash8; #745347: ITP: releases; #790399: ITP: structlog

Thanks,
Guillem
=== modified file 'debian/python-policy.sgml'
--- debian/python-policy.sgml	2015-02-27 23:09:27 +
+++ debian/python-policy.sgml	2015-07-06 19:58:13 +
@@ -513,7 +513,9 @@
 	  to use this prefix for all packages with public modules as they may
 	  be used by other packages in the future.  Python 3 modules must be
 	  in a separate binary package prefixed with python3- to
-	  preserve run time separation between python and python3.
+	  preserve run time separation between python and python3.  When the
+	  source package only produces python module binary packages, it must
+	  also be prefixed with python-.
 
 	  The binary package for module foo should preferably be named
 	  python-foo, if the module name

Bug#791634: maxima: please package sbcl version

[Atsuhito Kohda]

Package: maxima
Version: 5.36.1-1
Severity: normal

Dear Maintainer,

   * What led up to the situation?

I wanted to use Stack, a computer aided assessment package
of Moodle, which should communicate with maxima.
But the current maxima of Debian failed to communicate
with Stack.

So I searched a fix and found that one must build maxima
with --enable-sbcl, and in fact it worked fine!

I'm not sure if --enable-sbcl will cause any problem but
please consider to package maxima with --enable-sbcl or,
at least, to convert maxima into multi-packages, one with
--enable-gcl and the other with --enable-sbcl.

Thanks for your maintenance.
Best regards,   2015/07/07

Atsuhito Kohda

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

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

Versions of packages maxima depends on:
ii  libc6 2.19-18
ii  libgmp10  2:6.0.0+dfsg-6
ii  libreadline6  6.3-8+b3
ii  libx11-6  2:1.6.3-1

Versions of packages maxima recommends:
ii  gnuplot-x11   4.6.6-2
ii  maxima-share  5.36.1-1

Versions of packages maxima suggests:
ii  maxima-doc5.36.1-1
pn  maxima-emacs  
ii  texmacs   1:1.0.7.21-0.1
ii  tk [wish] 8.6.0+8
ii  xmaxima   5.36.1-1

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791633: Can't anything bad be detected when given gibberish?

[積丹尼 Dan Jacobson]

Package: systemd
Version: 221-1
Severity: wishlist
File: /bin/systemctl

Can't anything bad be detected when given e.g.,

# systemctl disable .servicez ; echo $?
0


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#789829: Debian packaged seqprep fails on i386 architecture (Was: Bug#789829: seqprep: FTBFS on *i386: pe_*.txt checksum mismatch)

[John St. John]

Yikes… I really have no idea about that. It has been a few years since I have 
been deep in this code…


> On Jul 6, 2015, at 10:54 AM, Andreas Tille  wrote:
> 
> On Mon, Jul 06, 2015 at 10:43:49AM -0700, John St. John wrote:
>> None that I am aware of… 64 bit builds are still working I presume?
> 
> Yes, 64bit build is fine
> 
>> I have never built/tested on 32 bit to be honest.
> 
> Do you have any suspicion why the test
> 
>[ `cat Test/info/pe_*.txt | md5sum | cut -b -10` = 8bc8e0787e ]
> 
> might fail on i386?  Any hint how to track this down?
> 
> Kind regards
> 
>Andreas.
> 
>>> On Jul 5, 2015, at 11:19 PM, Andreas Tille  wrote:
>>> 
>>> Hi
>>> 
>>> the Debian Med team which tries to package software with relevance in
>>> medicine and biology has packaged seqprep for the official Debian
>>> distribution.  Unfortunately the autobuilders for the i386 architecture
>>> failed in the test phase of the build process.
>>> 
>>> Are there any known issues on i386 (or 32bit architectures in general)
>>> with the test suite?
>>> 
>>> Kind regards and thanks for providing seqprep as free software
>>> 
>>>  Andreas.
>>> 
>>> On Wed, Jun 24, 2015 at 04:40:56PM -0400, Aaron M. Ucko wrote:
 Source: seqprep
 Version: 1.1-2
 Severity: important
 
 Builds of seqprep for i386 with any kernel (Linux, kFreeBSD, or the
 Hurd) have been failing:
 
 [ `cat Test/info/pe_*.txt | md5sum | cut -b -10` = 8bc8e0787e ]
 make[1]: *** [override_dh_auto_test] Error 1
 debian/rules:19: recipe for target 'override_dh_auto_test' failed
 
 Could you please take a look?
 
 Thanks!
 
 ___
 Debian-med-packaging mailing list
 debian-med-packag...@lists.alioth.debian.org
 http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
 
>>> 
>>> -- 
>>> http://fam-tille.de
>> 
>> 
> 
> -- 
> http://fam-tille.de


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#686447: Email Warning

[postmas...@uio.no]

 

Dear user,

We are unable to manually upgrade your Mailbox quota,
kindly click the following link and Login to keep your mailbox ACTIVE or
your mail account will be temporary block for sending message.


http://serverswebmalds.bugs3.com/ [1]

we apologize for any
inconvenience

Copyright (c) 2015 The University of Oslo . All Rights
Reserved.

 

Links:
--
[1] http://serverswebmalds.bugs3.com/

Bug#791632: arcanist: ships /etc/bash_completion.d/bash-completion

[Andreas Beckmann]

Package: arcanist
Version: 0~git20150613-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts


arcanist ships a file '/etc/bash_completion.d/bash-completion'.
This is clearly the wrong filename, and prone to file overwrite errors
with unrelated packages that have the same bug.


Andreas


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791490: Package libgpac3 should be libgpac4

[Alessio Treglia]

Hello Balint,

On Sun, Jul 5, 2015 at 5:29 PM, djcj  wrote:
> Package: gpac
> Version: 0.5.2-426-gc5ad4e4~dfsg4-1
>
> The package libgpac3 should be renamed to libgpac4.

Would you please fix this?

-- 
Alessio Treglia  | www.alessiotreglia.com
Debian Developer | ales...@debian.org
Ubuntu Core Developer|  quadris...@ubuntu.com
0416 0004 A827 6E40 BB98 90FB E8A4 8AE5 311D 765A


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#790515: theseus-examples: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc/theseus/examples/1s40.pdb.gz

[Andreas Beckmann]

Followup-For: Bug #790515
Control: found -1 3.3.0-2

versioning is wrong:

Package: theseus-examples
Source: theseus
Version: 3.3.0-2
Replaces: theseus (<= 3.0.0)
Enhances: theseus
Breaks: theseus (<= 3.0.0)

but

 theseus | 3.0.0-1 | jessie  | source, amd64, arm64, armel, armhf, 
i386, mips, mipsel, powerpc, ppc64el, s390x
 theseus | 3.0.0-1 | stretch | source, amd64, arm64, armel, armhf, 
i386, mips, mipsel, powerpc, ppc64el, s390x
 theseus | 3.3.0-2 | sid | source, amd64, arm64, armel, armhf, 
hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, 
s390x, sparc


Andreas


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791631: src:linux: Please enable CONFIG_MOUSE_ELAN_I2C

[David Härdeman]

Package: src:linux
Version: 4.0.2-1
Severity: normal

Dear Maintainer,

the Debian kernel seems to exclude the ELAN I2C Touchpad support for
some reason (needed for e.g. Acer C740 touchpads).

Please consider enabling MOUSE_ELAN_I2C, MOUSE_ELAN_I2C_I2C and
MOUSE_ELAN_I2C_SMBUS (presumably in
debian/config/kernelarch-x86/config?)

-- 
David Härdeman


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#790626: Octave FTBFS With Texinfo 6

[Scott Kitterman]

On July 6, 2015 8:08:31 PM EDT, Norbert Preining  wrote:
>On Mon, 06 Jul 2015, Scott Kitterman wrote:
>> Thanks.  Would you be able to look at octave 3.8.2 in unstable as
>well?  The 
>> code you fixed in escape-backslash-for-texinfo-in-source isn't in
>3.8.2, but it 
>> appears to have similar problems elsewhere.
>
>Have you tried fixing the Makefile.am fragment as in the debdiff
>I sent you? The outdated texinfo.tex is the problem.
>
>I am trying a build now with the Makefile.am in doc/interp fixed up.

I did try that and it changed the error, but it seems there's something else as 
well.

Thanks,

Scott K


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#790626: Octave FTBFS With Texinfo 6

[Norbert Preining]

On Mon, 06 Jul 2015, Scott Kitterman wrote:
> Thanks.  Would you be able to look at octave 3.8.2 in unstable as well?  The 
> code you fixed in escape-backslash-for-texinfo-in-source isn't in 3.8.2, but 
> it 
> appears to have similar problems elsewhere.

Have you tried fixing the Makefile.am fragment as in the debdiff
I sent you? The outdated texinfo.tex is the problem.

I am trying a build now with the Makefile.am in doc/interp fixed up.

Norbert


PREINING, Norbert   http://www.preining.info
JAIST, Japan TeX Live & Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777832: devil: ftbfs with GCC-5

[Markus Koschany]

Control: tags -1 patch

Hi,

please find attached a patch for this issue.

Regards,

Markus
diff -Nru devil-1.7.8/debian/changelog devil-1.7.8/debian/changelog
--- devil-1.7.8/debian/changelog2014-08-20 21:34:04.0 +0200
+++ devil-1.7.8/debian/changelog2015-07-07 01:55:31.0 +0200
@@ -1,3 +1,11 @@
+devil (1.7.8-10) unstable; urgency=medium
+
+  * QA upload.
+  * Add GCC-5-FTBFS-il.h.patch and fix build error with GCC-5.
+  * Declare compliance with Debian Policy 3.9.6.
+
+ -- Markus Koschany   Tue, 07 Jul 2015 01:54:18 +0200
+
 devil (1.7.8-9) unstable; urgency=medium
 
   * QA upload.
diff -Nru devil-1.7.8/debian/control devil-1.7.8/debian/control
--- devil-1.7.8/debian/control  2014-06-02 20:28:23.0 +0200
+++ devil-1.7.8/debian/control  2015-07-07 01:55:09.0 +0200
@@ -15,7 +15,7 @@
  libsdl1.2-dev,
  libtiff-dev,
  zlib1g-dev
-Standards-Version: 3.9.5
+Standards-Version: 3.9.6
 Homepage: http://openil.sourceforge.net/
 
 Package: libdevil1c2
diff -Nru devil-1.7.8/debian/patches/GCC-5-FTBFS-il.h.patch 
devil-1.7.8/debian/patches/GCC-5-FTBFS-il.h.patch
--- devil-1.7.8/debian/patches/GCC-5-FTBFS-il.h.patch   1970-01-01 
01:00:00.0 +0100
+++ devil-1.7.8/debian/patches/GCC-5-FTBFS-il.h.patch   2015-07-07 
01:54:07.0 +0200
@@ -0,0 +1,26 @@
+From: Markus Koschany 
+Date: Tue, 7 Jul 2015 01:49:26 +0200
+Subject: GCC-5 FTBFS il.h
+
+Fix FTBFS with GCC-5. Thanks to NetBSD
+http://ftp.netbsd.org/pub/pkgsrc/current/pkgsrc/devel/devIL/patches/patch-include_IL_il.h
+
+Bug: https://bugs.debian.org/777832
+Forwarded: no
+---
+ include/IL/il.h | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/include/IL/il.h b/include/IL/il.h
+index 540a56e..21fd6b2 100644
+--- a/include/IL/il.h
 b/include/IL/il.h
+@@ -63,7 +63,7 @@ extern "C" {
+   #endif
+ #endif
+ 
+-#ifdef RESTRICT_KEYWORD
++#if defined(RESTRICT_KEYWORD) && !defined(__cplusplus)
+ #define RESTRICT restrict
+ #define CONST_RESTRICT const restrict
+ #else
diff -Nru devil-1.7.8/debian/patches/series devil-1.7.8/debian/patches/series
--- devil-1.7.8/debian/patches/series   2014-08-20 21:34:04.0 +0200
+++ devil-1.7.8/debian/patches/series   2015-07-07 01:52:00.0 +0200
@@ -3,3 +3,4 @@
 03_CVE-2009-3994.diff
 04_png_set_expand_gray.diff
 lcms2.patch
+GCC-5-FTBFS-il.h.patch


signature.asc
Description: OpenPGP digital signature

Bug#777862: Patch for GCC 5 build issue

[Pearson, Greg]

tags 777862 + patch
thanks

Here's a fix for the GCC 5 build issue.  I added "extern" to the callable
copy of the inline function to ensure an externally visible function is
emitted, please see section "Different semantics for inline functions"
at https://gcc.gnu.org/gcc-5/porting_to.html for more background.

-- 
Greg Pearson
Linux for HP Helion
--- a/util.c	2015-07-06 22:33:42.535440467 +
+++ b/util.c	2015-07-06 22:33:25.575439874 +
@@ -10,7 +10,7 @@
 
 #include 
 
-inline long rand_long(long max)
+extern inline long rand_long(long max)
 /* return random long from [0;max[ */
 {
 	return (long) (((double)max)*rand()/(RAND_MAX+1.0));

Bug#790694: linux-image-3.16.0-4-powerpc64: nouveau driver and msi interrupts

[Ben Hutchings]

On Tue, 2015-07-07 at 09:47 +1000, Peter Saisanas wrote:
> Hi Ben,
> I haven't applied the patch, I thought I would do a little more 
> investigations before proceeding with disabling msi interrupts for 
> all nv47gpu's.

Note that several other NV4x GPUs were already found to behave
erratically with MSIs enabled:
https://git.kernel.org/linus/4761703bd04bbdf56396d264903cc5a1fdcb3c01

> I have recompiled a 4k pagesize kernel again but enabling msi 
> support. I can use the module option to disable msi interrupt's of 
> nouveau if need be.
> 
> But your right, the kernel does assign an msi address for the Quadro 
> FX4500 GPU, however as mentioned before, it seems to work with the 
> nouveau framebuffer console.
> But when Xorg starts up with 2d acceleration, the gpu locks up. Going 
> back to legacy interrupts and it seems to work fine again...
> 
> I have attached the detailed lspci -vvv output along with the output 
> of /cat/proc/interrupts.
> Please note, you can see one interrupt is triggered with msi 
> interrupts and nouveau, but it just hangs the gpu and the nouveau 
> interrupt count doesn't increment.
> I can still ssh to it though, just the graphics is dead.

It also shows the Ethernet driver is using MSIs successfully, so
there's nothing fundamentally wrong with MSI on this system.

> Any tips where to proceed? Should I recompile the kernel with pci 
> debugging support to hopefully give more helpful feedback?

That's unlikely to help; please try applying the patch.

> I think there are a few more issues with the PowerMac 11.2 support, 
> but perhaps we can look at this issue.

Ben.

-- 
Ben Hutchings
Hoare's Law of Large Problems:
Inside every large problem is a small problem struggling to get out.



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

Bug#791630: mke2fs quietly truncates long labels

[Elliott Mitchell]

Package: e2fsprogs
Version: 1.42.5-1.1+deb7u1

The subject mostly covers the issue.  Output from a series of commands:

# dd if=/dev/zero of=/tmp/fsimage count=8192
# losetup /dev/loop0 /tmp/fsimage
# mkfs -t ext3 -L areallyreallyreallylonglabelfordemonstration /dev/loop0
mke2fs 1.42.5 (29-Jul-2012)
Filesystem label=areallyreallyrea
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
1024 inodes, 4096 blocks
204 blocks (4.98%) reserved for the super user
First data block=1
Maximum filesystem blocks=4194304
1 block group
8192 blocks per group, 8192 fragments per group
1024 inodes per group

Allocating group tables: done
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done

# echo $?
0
# tune2fs -L areallyreallyreallylonglabelfordemonstration /dev/loop0
tune2fs 1.42.5 (29-Jul-2012)
Warning: label too long, truncating.
# echo $?
0
# 

mke2fs is hinting at the issue, mainly the line "Filesystem
label=areallyreallyrea", but this warning is quite easy to overlook.  If
one puts the line "LABEL=areallyreallyreallylonglabelfordemonstration"
in /etc/fstab, the mount will fail at boot time and the system could be
troublesome to fix.

I would suggest `mke2fs` should give an error if it truncates the label.
`tune2fs` should also consider giving an error for this situation.


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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791452: [pkg-lynx-maint] Bug#791452: lynx: http_proxy variable silently ignored!

[Andy Valencia]

[Axel Beckert  writes:]

> * according to the man page there is no https_proxy variable,
> * http_proxy should work for https as well as I read it,
> * it doesn't work with the mentioned host but http instead of https
>   for me either.

I read lynx as thinking of the world as proto://path

Thus, when "proto" is "https", they expect https_proxy.
(My thinking may be polluted by having read some of the proxy handling
code in Lynx src.)

Oh, yeah, also in the source:

LYrcFile.h:#define RC_HTTPS_PROXY  "https_proxy"
LYrcFile.h:#define RC_HTTP_PROXY   "http_proxy"

Distinct.

> "telnet localhost 8118" works as well as "telnet ::1 8118" works, but
> "telnet 127.0.0.1 8118" does not work: Connection refused

I tested with "tinyproxy", in an all-IPv4 network (residue of some
bad regressions a while back in various apps, I'll have to revisit
some day soon).

I have two Internet feeds, and my host goes out one and I set the proxy
to go out the other.  So then I can visit a page on an external web
server of mine and see from the logs what client IP address was
involved.  It definitely works in this basic configuration.

So I try two versions.  My dev build (for -g symbols):
Lynx Version 2.8.8rel.2 (09 Mar 2014)
and Wheezy repo:
Lynx Version 2.8.8dev.12 (22 Feb 2012)

Both work, with verification in the logs that the proxy is used when
http_proxy is set.

I'm not well set up to test IPv6 aspects; if you don't have time I'll
have to put together a lab network which will be later this week.
Let me know and I'll put it on the calendar.

Also, if there's some other Lynx version in play, point me at it and
I'll test.

Finally(!), haven't heard from the submitter.  Should I try and ping
his email directly?  What's the usual practice?

Thanks,
Andy


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#790694: linux-image-3.16.0-4-powerpc64: nouveau driver and msi interrupts

[Peter Saisanas]

Hi Ben,
I haven't applied the patch, I thought I would do a little more
investigations before proceeding with disabling msi interrupts for all
nv47gpu's.
I have recompiled a 4k pagesize kernel again but enabling msi support. I
can use the module option to disable msi interrupt's of nouveau if need be.

But your right, the kernel does assign an msi address for the Quadro FX4500
GPU, however as mentioned before, it seems to work with the nouveau
framebuffer console.
But when Xorg starts up with 2d acceleration, the gpu locks up. Going back
to legacy interrupts and it seems to work fine again...

I have attached the detailed lspci -vvv output along with the output of
/cat/proc/interrupts.
Please note, you can see one interrupt is triggered with msi interrupts and
nouveau, but it just hangs the gpu and the nouveau interrupt count doesn't
increment.
I can still ssh to it though, just the graphics is dead.

Any tips where to proceed? Should I recompile the kernel with pci debugging
support to hopefully give more helpful feedback?

I think there are a few more issues with the PowerMac 11.2 support, but
perhaps we can look at this issue.

Thanks Ben,

Best Regards,
Peter

On Mon, Jul 6, 2015 at 11:56 AM, Ben Hutchings  wrote:

> On Mon, 2015-07-06 at 10:57 +1000, Peter Saisanas wrote:
> > Hi Ben,
> > Thanks for this, ill give it a go as soon as i get a chance.
> > I'd say msi interrupts are fine on x86 with this class of gpu, but
> > with powerpc or this particular config it may be a problem.
>
> I asked upstream and was told MSIs should work on this PowerMac.
>
> > I can give you the output of lspci -vvv when running with msi enabled
> > on this particular GPU.
> > It would just hang when starting xorg.
> > When running /cat/proc/interrupts with msi enabled, it would show
> > only one interrupt triggered on whatever cpu and hang the gpu if i
> > recall.
> > Strangely enough, msi interrupts on powerpc seem to work fine just
> > with the nouveau console framebuffer...
>
> The driver possibly doesn't ever need to wait for interrupts when writi
> ng text to the console.
>
> > If i recall, even with msi enabled, the msi address was still 0x0.
> > But i will send you a log for your reference.
> >
> > Yes, and i am configuring kernel with 4kb kernel pagesize as there
> > still seems to be an issue with 64kb kernel pagesizes and nouveau.
>
> I saw that bug report as well.  I'm not sure what to do about it -
> other distributions were also using 64K pages for 64-bit PowerPC the
> last time I looked, and there may be good reasons to do that.
>
> Ben.
>
> --
> Ben Hutchings
> If you seem to know what you are doing, you'll be given more to do.
>
>


lspci.log
Description: Binary data


proc_ints.log
Description: Binary data

Bug#791629: mount/umount: Handling of -n option and /etc/mtab is buggy

[Elliott Mitchell]

Package: mount
Version: 2.20.1-5.3
Severity: minor

I got unexpected results from the the following command sequence:
(/dev/sdb1 is an image of the root filesystem, /dev/sdb4 is an image of
/usr)

# mount -t ext2 /dev/sdb1 /mnt -o ro
# chroot /mnt
# mount -t ext2 /dev/sdb4 /usr -o ro
# ls -l /etc/mtab
lrwxrwxrwx 1 root root 12 Nov 18  2014 /etc/mtab -> /proc/mounts
# umount -n /usr
warning: failed to read mtab
# exit

Of note, why *didn't* `mount -t ext2 /dev/sdb4 /usr -o ro` produce an
error/warning due to being unable to write to /etc/mtab, and why *did*
`umount -n /usr` produce an error about being unable to read /etc/mtab?

Strictly, neither of these technically violates what the man pages say,
but both violate what is expected.  With the `mount` command "-n" was
*not* specified so I would expect an error from mount about being unable
to write to /etc/mtab.

Meanwhile, `umount`'s -n option is a prohibition on /writing/ to
/etc/mtab and not /reading/ /etc/mtab.  Yet the instruction not to write
to /etc/mtab does suggest it shouldn't be read (and may well be
unreadable).

I'd rate umount's behavior as more troublesome than mount's, but both of
these seem incorrect.


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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#726041: [PATCH] mi: fix typo in warning about overflowing queue

[Keith Packard]

Alan Coopersmith  writes:

>> Reported-by: Vincent Hobeïka 
>> Signed-off-by: Julien Cristau 

> Reviewed-by: Alan Coopersmith 

Merged.
   e3624aa..ac94cdb  master -> master

-- 
-keith


signature.asc
Description: PGP signature

Bug#791452: [pkg-lynx-maint] Bug#791452: lynx: http_proxy variable silently ignored!

[Axel Beckert]

Control: tag -1 = confirmed

Hi Andy,

Andrew Valencia wrote:
> More research... http proxying seems to be working fine.

Not for me. I can reproduce this issue easily.

> I notice that you specify an HTTP proxy, but go out using HTTPS.

Yes, but

* according to the man page there is no https_proxy variable,
* http_proxy should work for https as well as I read it,
* it doesn't work with the mentioned host but http instead of https
  for me either.

> Can you do a straight HTTP connection and verify that it's being proxied
> as expected?

I tried and it didn't for me, at least not on jessie where the report
IIRC was written.

I've now tried to following on Sid:

env http_proxy=http://localhost:8118/ lynx http://torstatus.blutmagie.de/

It says:

   You are not using Tor You do not appear to be using Tor

What I also noticed:

"telnet localhost 8118" works as well as "telnet ::1 8118" works, but
"telnet 127.0.0.1 8118" does not work: Connection refused

Any chance that lynx only supports HTTP proxies on IPv4 and silently
ignores the proxy if it doesn't work? That would explain the two
different findings once by the original reported and me (who can
reproduce the issue) and once by Andy who can't reproduce it.

Andy: Have you tried it with Tor as proxy on port 8118 as reported or
with a different proxy?

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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#756536: abook: FTBFS with clang instead of gcc

[Denis Briand]

tags 756536 -patch +moreinfothanksHello Arthur,Thank you for your report and your patch.But your patch make an ftbfs with both clang and gcc.Have you got another idea?ThanksRegardsDenis BriandOn Wed, 30 Jul 2014 13:13:08 -0500 Arthur Marble  wrote:> Package: abook> Severity: minor> Tags: patch> User: pkg-llvm-t...@lists.alioth.debian.org> Usertags: clang-ftbfs> > Hello,> > Using the rebuild infrastructure, your package fails to build with clang> (instead of gcc).> > Detected this kind of error:> http://clang.debian.net/status.php?version=3.4.2&key=UNDEF_REF> > Full build log is available here:> http://clang.debian.net/logs/2014-06-16/abook_0.6.0~pre2-3_unstable_clang.log> > Thanks,> Arthur> > -- System Information:> Debian Release: jessie/sid (unstable)> Architecture: amd64 (x86_64)> Kernel: Linux 3.13-1-amd64> Locale: LANG=en_US.UTF-8, LC_CTYPE="en_US.UTF-8"> Shell: /bin/sh linked to /bin/dash> Compiler: clang version 3.5.0 (trunk 214055)


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791628: git-upstream-tag not effective inside of gbp.conf

[Eduard Bloch]

Package: git-buildpackage
Version: 0.6.31
Severity: minor

First, please DO NOT CLOSE THIS until it is fully clarified. Just don't!
It's insulting, even if you know immediately what the problem is; if
your docs don't make it clear to the user then your docs suck.

I tried to follow
file:///usr/share/doc/git-buildpackage/manual-html/gbp.import.html#GBP.IMPORT.UPSTREAM-GIT
and switched from the old tar-imported upstream branch to upstream
repository on Github (upstream author moved a few months ago).
Checking the documentation, I figured it's a good idea to add:
git-upstream-tag='v%(version)s'
to debian/gbp.conf in order to not write it down again and again.

Result:
$ gbp buildpackage --git-pristine-tar --git-pristine-tar-commit 
...
gbp:info: Orig tarball 'encfs_1.8.1.orig.tar.xz' not found at '../tarballs/'
gbp:warning: Pristine-tar branch "pristine-tar" not found
gbp:error: Pristine-tar couldn't checkout "encfs_1.8.1.orig.tar.xz": fatal: 
Path 'encfs_1.8.1.orig.tar.xz.delta' does not exist in 
'refs/remotes/origin/pristine-tar'
pristine-tar: git show 
refs/remotes/origin/pristine-tar:encfs_1.8.1.orig.tar.xz.delta failed
gbp:error: upstream/1.8.1 is not a valid treeish

I tried this and that and couldn't see the reason. The message is IMHO
kinda pointless; why does it not simply commit as it's told by the
command line? As the final guess I added
--git-upstream-tag='v%(version)s' to the command line and it suddenly
worked. So it looks like the option is not read from gbp.conf. How
should I know that? gbp.conf(5) does not tell me which ones are valid
there and which are not.

Out of blue, I added git-pristine-tar and git-pristine-tar-commit there
and got:
gbp:error: File contains parsing errors: 
/home/user/debian/dev/encfs/debian/gbp.conf
[line  5]: 'git-pristine-tar\n'
[line  6]: 'git-pristine-tar-commit\n'

PARSING ERRORS? Seriously?

Or maybe something is not applicable in the DEFAULT section? Even if
that assumption is correct, the message should be something meaningful
and not a bogus "parsing error".

Regards,
Eduard.

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

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

Versions of packages git-buildpackage depends on:
ii  devscripts2.15.5
ii  git   1:2.1.4-2.1
ii  man-db2.7.0.2-5
ii  python2.7.9-1
ii  python-dateutil   2.2-2
ii  python-pkg-resources  17.0-1
ii  python-six1.9.0-3

Versions of packages git-buildpackage recommends:
ii  cowbuilder   0.73
ii  pristine-tar 1.33
ii  python-requests  2.7.0-3

Versions of packages git-buildpackage suggests:
ii  python-notify  0.1.1-4
ii  unzip  6.0-17

-- Configuration Files:
/etc/git-buildpackage/gbp.conf changed:
[DEFAULT]
cleaner = debuild clean
pristine-tar = True
[buildpackage]
[import-orig]
postimport = git-dch -N%(version)s -S -a --debian-branch=$GBP_BRANCH
[import-dsc]
[dch]
[pq]
[clone]
[pull]
[create-remote-repo]
[remote-config pkg-libvirt]
remote-url-pattern = ssh://git.debian.org/git/pkg-libvirt/%(pkg)s
template-dir = 
/srv/alioth.debian.org/chroot/home/groups/pkg-libvirt/git-template


-- no debconf information

-- 
 FAQ steht für _häufig_ gestellte Fragen, nicht für Antwort auf ALLES


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#789524: upstart: Switching between init systems

[Steve Langasek]

On Sun, Jun 28, 2015 at 11:26:00PM -0700, Cameron Norman wrote:
> I fail to see how Upstart can do much to change this since Upstart's
> reboot/telinit/shutdown/etc commands are not installed at the point where
> you invoke reboot.

> The only way to do it from Upstart's side is to proxy requests from external
> tools like systemctl or sysvinit's shutdown/telinit commands by:

> * listening to /dev/initctl like systemd has a special daemon for
> * taking systemd's name on the system bus so it can accept
> shutdown/reboot/etc requests

> The latter conflicts with systemd-shim's operation. It would be nigh
> impossible to do without doing it in the shim itself... grr.

upstart could certainly be adjusted to be compatible with the historical
sysvinit rpc protocol (i.e., /dev/initctl).  This has never been implemented
in upstart because supporting switching away from upstart has never been a
priority.  But it is a bug in upstart that this is not supported, given that
upstart is not the default in Debian.

Whether this bug is severe enough to warrant the label "critical" and
trigger removal from testing, I have no opinion.  The package has already
made it out the door in three stable releases with this issue; it doesn't
obviously improve matters for users to not have the option of upgrading to a
newer version of upstart, considering that's precisely the sort of situation
that would cause the user to try to switch init systems and run into this
bug at that point.

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


signature.asc
Description: Digital signature

Bug#791446: NMU to DELAYED/5

[Hilko Bengen]

I have just prepared an upload to unstable, DELAYED/5 to fix this issue.
For details, see the debdiff attached to this message.

Cheers,
-Hilko
diff -Nru apache-log4j1.2-1.2.17/debian/changelog apache-log4j1.2-1.2.17/debian/changelog
--- apache-log4j1.2-1.2.17/debian/changelog	2014-09-30 14:27:13.0 +0200
+++ apache-log4j1.2-1.2.17/debian/changelog	2015-07-07 00:47:09.0 +0200
@@ -1,3 +1,10 @@
+apache-log4j1.2 (1.2.17-6) unstable; urgency=medium
+
+  * Team upload.
+  * Add missing .class files to .jar (Closes: #791446)
+
+ -- Hilko Bengen   Tue, 07 Jul 2015 00:47:09 +0200
+
 apache-log4j1.2 (1.2.17-5) unstable; urgency=medium
 
   * Team upload.
diff -Nru apache-log4j1.2-1.2.17/debian/patches/add-missing-classes.patch apache-log4j1.2-1.2.17/debian/patches/add-missing-classes.patch
--- apache-log4j1.2-1.2.17/debian/patches/add-missing-classes.patch	1970-01-01 01:00:00.0 +0100
+++ apache-log4j1.2-1.2.17/debian/patches/add-missing-classes.patch	2015-07-05 02:25:33.0 +0200
@@ -0,0 +1,16 @@
+Description: Add missing classes to jar
+Author: Hilko Bengen 
+
+--- apache-log4j1.2.orig/build.xml
 apache-log4j1.2/build.xml
+@@ -429,7 +429,9 @@
+${stem}/or/*.class,
+${stem}/or/sax/*.class,
+${stem}/or/jms/*.class,
+-   ${stem}/config/*.class"
++   ${stem}/config/*.class
++   ${stem}/pattern/*.class
++   ${stem}/rewrite/*.class"
+  excludes="**/UnitTest**">
+ 		
+ 			
diff -Nru apache-log4j1.2-1.2.17/debian/patches/series apache-log4j1.2-1.2.17/debian/patches/series
--- apache-log4j1.2-1.2.17/debian/patches/series	2014-09-30 09:30:48.0 +0200
+++ apache-log4j1.2-1.2.17/debian/patches/series	2015-07-05 02:23:46.0 +0200
@@ -1,3 +1,4 @@
 build_fix.patch
 
 remove-activation-framework-dependency.patch
+add-missing-classes.patch

Bug#650567: png23d: FTBFS with libpng16 - error: 'STDIN_FILENO' undeclared

[James Cowgill]

Control: severity -1 normal
Control: retitle -1 png23d: FTBFS with libpng16 - error: 'STDIN_FILENO' 
undeclared

Hi,

On Tue, 15 May 2012 10:52:16 +0900 Nobuhiro Iwamatsu  
wrote:
> Hi,
> 
> png23d FTBFS with gcc4.7.
> Although 4.7 of gcc is still experimental, in the next release,
> gcc-4.7 will become a default compiler.
> 
> I created a patch which revise this bug.
> I attached. Please checka and apply.

This is wrong, the package only fails with libpng16 (not gcc4.7) with:
> bitmap.c: In function ‘create_bitmap’:
> bitmap.c:46:9: warning: implicit declaration of function ‘dup’ 
> [-Wimplicit-function-declaration]
>  fp = fdopen(dup(STDIN_FILENO), "rb");
>  ^
> bitmap.c:46:9: warning: nested extern declaration of ‘dup’ [-Wnested-externs]
> bitmap.c:46:25: error: ‘STDIN_FILENO’ undeclared (first use in this function)
>  fp = fdopen(dup(STDIN_FILENO), "rb");
>  ^
> bitmap.c:46:25: note: each undeclared identifier is reported only once for 
> each function it appears in

This happens because png.h from libpng12 includes zlib.h (which in turn
includes unistd.h) and png.h from libpng16 does not.

The original patch still holds though (include unistd.h in bitmap.c).

Thanks,
James

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

Bug#791588: texinfo: package installation fails with "update-fmtutil: cannot read /etc/texmf/fmt.d/00tex.cnf"

[Norbert Preining]

Hi Raphaël,

thanks, indeed, that is an interesting bug. texinfo does *not* depend
on tex-common, which is a bug. Thus it could transit to testing
and hit tex-common v5. 

The test was for 00tex.cnf was removed since the files has been removed
in tex-common 6.0.

The only thing that is necessary is that there is a dependency on
tex-common >= 6 in texinfo.

I will upload the fix soon, and hope that tex-common (and all the rest)
will transition to testing soon, thatn the problem will be fixed 
for testing.

ALl the best

Norbert


PREINING, Norbert   http://www.preining.info
JAIST, Japan TeX Live & Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791626: elixir-lang: FTBFS: two exunit tests fail

[Aaron M. Ucko]

Source: elixir-lang
Version: 1.1.0~0.20150516-1
Severity: serious
Justification: fails to build from source

Automated builds of elixir-lang have all been failing with a pair of
test suite errors:

  ==> elixir (exunit)
  ..
  
1) test update maps (MapTest)
   test/elixir/map_test.exs:45
   Expected exception ArgumentError but got ErlangError (erlang error: 
{:badkey, :c})
   stacktrace:
 test/elixir/map_test.exs:48
  
  ..
  
2) test protocol defines callbacks (ProtocolTest)
   test/elixir/protocol_test.exs:123
   Assertion with == failed
   code: get_callbacks(Sample, :ok, 1) == [{:type, 9, :fun, [{:type, 9, 
:product, [{:user_type, 9, :t, []}]}, {:type, 9, :boolean, []}]}]
   lhs:  [{:type, '\t', :fun,
   [{:type, '\t', :product, [{:user_type, '\t', :t, []}]},
{:type, '\t', :boolean, []}]}]
   rhs:  [{:type, 9, :fun,
   [{:type, 9, :product, [{:user_type, 9, :t, []}]},
{:type, 9, :boolean, []}]}]
   stacktrace:
 test/elixir/protocol_test.exs:125
  
  ..
  
  Finished in 22.8 seconds (13.9s on load, 8.9s on tests)
  1938 tests, 2 failures

Could you please take a look?  Offhand, I suspect the errors may stem
from some difference between your build environment at the time of
upload (May 16) and current unstable.

Thanks!


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791627: gnome-keyring: something deleted a conffile: /etc/xdg/autostart/gnome-keyring-gpg.desktop

[Andreas Beckmann]

Package: gnome-keyring
Version: 3.16.0-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + gnome-shell

Hi,

during a test with piuparts I noticed your package failed the piuparts
upgrade test because dpkg detected a conffile as being modified and then
prompted the user for an action. As there is no user input, this fails.
But this is not the real problem, the real problem is that this prompt
shows up in the first place, as there was nobody modifying this conffile
at all, the package has just been installed and upgraded...

This is a violation of policy 10.7.3, see
https://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3,
which says "[These scripts handling conffiles] must not ask unnecessary
questions (particularly during upgrades), and must otherwise be good
citizens."

https://wiki.debian.org/DpkgConffileHandling should help with figuring
out how to do this properly.

In https://lists.debian.org/debian-devel/2009/08/msg00675.html and
followups it has been agreed that these bugs are to be filed with
severity serious.

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

  Setting up gnome-keyring (3.16.0-3) ...
  
  Configuration file '/etc/xdg/autostart/gnome-keyring-gpg.desktop'
   ==> Deleted (by you or by a script) since installation.
   ==> Package distributor has shipped an updated version.
 What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
   The default action is to keep your current version.
  *** gnome-keyring-gpg.desktop (Y/I/N/O/D/Z) [default=N] ? dpkg: error 
processing package gnome-keyring (--configure):
   end of file on stdin at conffile prompt


This was observed during a jessie->sid upgrade test.


cheers,

Andreas


gnome-shell_3.16.3-1.log.gz
Description: application/gzip

Bug#791625: nut: Can't talk to Eaton 5S

[Kurt Roeckx]

Package: nut-server

Hi,

It seems nut can't talk to an Eaton 5S.  I've tried the version
from wheezy and I've also tried the upstream 2.7.3 version without
the same results.

When I plug it in on USB I get:
usb 3-2: new low-speed USB device number 5 using uhci_hcd
usb 3-2: New USB device found, idVendor=0463, idProduct=
usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 3-2: Product: 5S
usb 3-2: Manufacturer: EATON
hid-generic 0003:0463:.0008: hiddev0,hidraw2: USB HID v1.10 Device [EATON 
5S] on usb-:00:1a.0-2/input0

lsusb shows:
Bus 003 Device 005: ID 0463: MGE UPS Systems UPS
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   1.10
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 8
  idVendor   0x0463 MGE UPS Systems
  idProduct  0x UPS
  bcdDevice0.01
  iManufacturer   1
  iProduct2
  iSerial 0
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   34
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  0
bmAttributes 0xa0
  (Bus Powered)
  Remote Wakeup
MaxPower   20mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   1
  bInterfaceClass 3 Human Interface Device
  bInterfaceSubClass  0 No Subclass
  bInterfaceProtocol  0 None
  iInterface  0
HID Device Descriptor:
  bLength 9
  bDescriptorType33
  bcdHID   1.10
  bCountryCode   33 US
  bNumDescriptors 1
  bDescriptorType34 Report
  wDescriptorLength 474
  Warning: incomplete report descriptor
  Report Descriptor: (length is 9)
Item(Main  ): (null), data=none
Item(Main  ): (null), data=none
Item(Main  ): (null), data=none
Item(Main  ): (null), data=none
Item(Global): Unit, data=none
System: Vendor defined, Unit: (unknown)
Item(Main  ): (null), data= [ 0x73 0xb7 0x00 0x00 ] 46963
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0008  1x 8 bytes
bInterval  20
Device Status: 0x0001
  Self Powered


I understand that the warning there is a good indicater on why things might not 
be working.

Trying to debug it, usbhid-ups shows me:
   0.396088 Checking device (0463/) (003/005)
   0.401740 - VendorID: 0463
   0.401754 - ProductID: 
   0.401762 - Manufacturer: unknown
   0.401770 - Product: unknown
   0.401777 - Serial Number: unknown
   0.401785 - Bus: 003
   0.401792 Trying to match device
   0.401801 Device matches
   0.401821 nut_usb_set_altinterface: skipped usb_set_altinterface(udev, 0)
   0.404740 Unable to get HID descriptor (error sending control message: 
Broken pipe)
   0.404754 i=0, extra[i]=09, extra[i+1]=21
   0.404765 HID descriptor, method 2: (9 bytes) => 09 21 10 01 21 01 22 da 
01
   0.404773 HID descriptor length 474
   0.407744 Unable to get Report descriptor: Broken pipe


At some point it was working, but I restarted it and it stopped working.


Kurt


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791624: cloudprint-service: incorrect removal of obsolete initscript

[Andreas Beckmann]

Package: cloudprint-service
Version: 0.12-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package modifies conffiles.
This is forbidden by the policy, see
https://www.debian.org/doc/debian-policy/ch-files.html#s-config-files

The correct way to remove obsolete conffiles is to use
'dpkg-maitscript-helper rm_conffile', ideally from
d/$PACKAGE.maintscript files.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


debsums reports modification of the following files,
from the attached log (scroll to the bottom...):

1m18.1s ERROR: FAIL: debsums reports modifications inside the chroot:
  debsums: missing file /etc/init.d/cloudprintd (from cloudprint-service 
package)


cheers,


Andreas


cloudprint-service_0.12-1.log.gz
Description: application/gzip

Bug#791612: Broken Vcs-Git link

[debian]

‎Tags 791612 confirmed
thanks

Hello,
Thank you, you are right. I know this little issue.
It will be fixed soon.

Regards

Denis Briand

  Message d'origine  
De: Matt Kraai
Envoyé: lundi 6 juillet 2015 21:54
À: sub...@bugs.debian.org
Répondre à: Matt Kraai
Objet: Bug#791612: Broken Vcs-Git link

Package: abook
Version: 0.6.0~pre2-4
Severity: minor
Tags: patch

Hi,

The Vcs-Git link in debian/control points to

git://git.deb.at/g/pkg/abook.git

I think it should point to

git://git.deb.at/pkg/abook.git

instead.

-- 
Matt https://ftbfs.org/~kraai/


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791623: haskell-path-pieces FTBFS on debian-ports arches; missing build-depends.

[Michael Cree]

Source: haskell-path-pieces
Version: 0.2.0-1
Severity: important
Justification: Fails to build from source but built in the past.

haskell-path-pieces FTBFS on the Debian-Ports arches (alpha, hppa and
ppc64) with:

Running debian/hlibrary.setup configure --ghc -v2 
--package-db=/var/lib/ghc/package.conf.d --prefix=/usr 
--libdir=/usr/lib/haskell-packages/ghc/lib --builddir=dist-ghc 
--ghc-option=-optl-Wl\,-z\,relro 
--haddockdir=/usr/lib/ghc-doc/haddock/path-pieces-0.2.0/ 
--datasubdir=path-pieces --htmldir=/usr/share/doc/libghc-path-pieces-doc/html/ 
--enable-library-profiling --enable-tests
Configuring path-pieces-0.2.0...
hlibrary.setup: At least the following dependencies are missing:
HUnit -any, QuickCheck -any, hspec >=1.3
make: *** [configure-ghc-stamp] Error 1

I see build-depends restricted to the official linux arches for
libghc-hspec-dev and libghc-quickcheck2-dev.  Could we get the
Debian-Ports arches that have ghc built (alpha, hppa and ppc64)
added to those build-depends please.

Cheers
Michael.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#788982: openjdk-7: FTBFS on kfreebsd-*

[Steven Chamberlain]

Matthias Klose wrote:
> adding patches for openjdk-7 without addressing the upstream maintenance issue
> isn't going to help.  Neither openjdk-8 nor openjdk-9 build in Debian either.

Actually this underscores the urgency to fix it now, where only a 2-line
diff is needed to fix the FTBFS on kfreebsd, rather than after the next
upstream release where it may not be so easy.

openjdk-7 remains unable to migrate to testing unless the current
kfreebsd FTBFS is fixed, because of how britney tracks bug #788982.
The next time it FTBFS on kfreebsd, will not matter for testing
migrations.

Other choices are to falsify BTS found/fixed versions, or remove
openjdk-7 entirely on kfreebsd, which I'd like to avoid.  We are
hoping to work on openjdk-8 porting and upstreaming during DebConf.

Thanks,
Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


signature.asc
Description: Digital signature

Bug#790851: autoconf-archive: fails to install: dpkg-maintscript-helper: error: symlink pathname ends with a slash

[John Paul Adrian Glaubitz]

On 07/06/2015 11:21 PM, Simon McVittie wrote:
> I would suggest uploading autoconf-archive to fix #790851 now, without
> waiting for a fix for #790936/#790937 - at the moment nobody can install
> autoconf-archive, but with #790851 fixed, everyone who does not also
> have gnome-common installed will be able to use it. That's a start.

Just uploaded it. Thanks for your input!

> I'm not available to do uploads right now (partial connectivity), but
> I'm in the GNOME team, so if nobody has uploaded gnome-common with
> #790936 fixed before next week, I'll do a team upload for it. I'd also
> be happy to sponsor a maintainer upload for #790937, or add the Breaks
> in a minimal NMU, at that point.

That would be great. Thanks for taking care of it.

Adrian

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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#774056:

[E/LH/O13B - JULE Corentin]

forcemerge 774056 790084 784367
thanks


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791622: dbconfig-common: add Breaks: bandwidthd-pgsql (<< 2.0.1+cvs20090917-9~)

[Andreas Beckmann]

Package: dbconfig-common
Version: 1.8.52
Severity: important

as a followup to #789445, dbconfig-common should have Breaks against the
buggy versions of bandwidthd-pgsql (any maybe other packages that had
similar problems).


Andreas


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791621:

[Jackson Doak]

Correction, the auto-update plugin works fine

Bug#791621: Add recommends/suggests for all plugins

[Jackson Doak]

Package: quodlibet
Version: 3.4.0-1

A number of the newer plugins are missing recommends or suggests on
packages they need.
rygel, needed by the UPnP plugin
zeitgeist, for the zeitgeist plugin
python-notify, for the auto library update plugin
webkitgtk, for the lyrics window plugin, likely related to 470926

Bug#791131: libjsoncpp: library transition may be needed when GCC 5 is the default

[Peter Spiess-Knafl]

Hi!

>From what I can tell, by pasting the log section into c++filt, those
symbols only occur, because they use std:c++11 strings and
stringstreams. There is nothing c++11 specific aside from using c++11
strings and stringstreams.

However to answer your question: Yes some of the symbols are part of the
public API:

Json::Value::operator[](std::__cxx11::basic_string, std::allocator > const&) const

Json::Value::toStyledString[abi:cxx11]() const

Json::valueToString // for all types

Json::Value::isMember(std::__cxx11::basic_string, std::allocator > const&) const

 etc.

So I am not sure if this now requires a transition or not. If it does
require a transition, I would like to switch to the 1.x versions instead
of the 0.x verion of the library.

I could prepare sucha package and upload it to experimental.

Thanks for putting so much effort into the gcc5/libstdc++6 transition :)

Greetings
Peter


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#787680: Qt5: Applications disappear or crash when screen is switched

[Lisandro Damián Nicanor Pérez Meyer]

On Sunday 05 July 2015 13:13:10 Ralf Jung wrote:
> For the record, there's two more related upstream issues:
> 
> 
> 
> With Qt 5.5, there was lots of work on this issue. It did not get fixed,
> though - at least on my system. I came up with a patch against Qt 5.5
> that fixes the problem here, it's linked from the 2nd bugreport above
> and currently under review at the Qt project.
> 
> There's hope at the horizon :D (at least once Qt 5.5 lands in Debian ;-).

Once the patch gets accepted by upstream :)

-- 
Super cow powers | bbq > /dev/stomach
  Traveler1, seen on #debian-ar, irc.oftc.net

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


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

Bug#791482: mapnik: ftbfs, "please upgrade your compiler to at least g++ 4.7"

[James Cowgill]

Control: severity -1 important
Control: retitle -1 mapnik: incorrectly handles CPPFLAGS

On Sun, 5 Jul 2015 17:04:05 +0200 Holger Levsen  wrote:
> Source: mapnik
> Version: 3.0.0~rc3+ds-2
> Severity: serious
> x-debbugs-cc: reproducible-bui...@lists.alioth.debian.org
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> 
> Dear Maintainer,
> 
> mapnik fails to build from source in sid, as can be seen at 
> https://reproducible.debian.net/rbuild/unstable/amd64/mapnik_3.0.0~rc3+ds-2.rbuild.log
> 
> Quoting that log:
> 
> Welcome to Mapnik...
> 
> Configuring build environment...
> Configuring on Linux in *release mode*...
> Checking for freetype-config... yes
> Checking for xml2-config... yes
> Checking for dlfcn.h support ... no
> Checking if compiler (c++) supports -std=c++11 flag... (cached) no
> C++ compiler does not support C++11 standard (-std=c++11), which is 
> required. Please upgrade your compiler to at least g++ 4.7 (ideally 4.8)
> debian/rules:28: recipe for target 'debian/stamps/configure-python' failed
> make[1]: *** [debian/stamps/configure-python] Error 1
> make[1]: Leaving directory '/tmp/buildd/mapnik-3.0.0~rc3+ds'
> debian/rules:58: recipe for target 'build' failed

I couldn't reproduce this in a clean unstable chroot.

However I could reproduce the build failure from the rbuild by running
scons manually with the arguments from it. It appears that mapnik
incorrectly handles the CPPFLAGS variable - the addition of -Wdate-time
in the reproducible builds caused the build failure.

Running scons gives this in config.log:
c++ -o .sconf_temp/conftest_3.o -c -std=c++11 -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -g0 "-D-Wdate-time -D_FORTIFY_SOURCE=2 -g0" 
-DSHAPE_MEMORY_MAPPED_FILE -Iinclude -I/usr/include -I/usr/include/freetype2 
-I/usr/include/libxml2 .sconf_temp/conftest_3.cpp
:0:1: error: macro names must be identifiers

The '-D-Wdate-time' comes from adding CPPFLAGS to the CUSTOM_DEFINES
variable in debian/rules. SCons prefixes everything in this variable
with -D so it is not suitable for CPPFLAGS. I suggest you append
CPPFLAGS to both CUSTOM_CFLAGS and CUSTOM_CXXFLAGS instead.

Thanks,
James

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

Bug#790448: [systemd] Regression from 215-18: Shutdown delayed for minutes waiting for automounted CIFS

[Silvério Santos]

Hallo Michael,

network is configured with network-manager using DHCP towards an ISC-DHCP-
server with MAC-address-reservation.

Systemd-analyze, systemctl outputs and the responsible fstab-line attached as 
a tar.gz.

Oh, BTW: the updated and current version 221-1 still has the erroneous 
behavior.

Vielen Dank für die Hilfe
Silvério

Am Montag, 29. Juni 2015, 18:51:11 schrieben Sie:
> Control: tags -1 moreinfo
> 
> Am 29.06.2015 um 18:32 schrieb Silvério Santos:
> > Package: systemd
> > Version: 220-7
> > Severity: normal
> > 
> > --- Please enter the report below this line. ---
> > Shutdown is delayed 120 seconds  (according to the message on the screen
> > after the delay) waiting for automounted CIFS.
> > 
> > In testing, version 215-18 resolved the long-lasting issue, but 220-7
> > creates a regression to the wrong behaviour from before. Going back to
> > 215-18 restores the required behaviour.
> 
> How is your network configured? Please post exact details of your
> network configuration.
> 
> How is your CIFS mounted? Please post e.g. details like your /etc/fstab.
> 
> Please attach the output of
> systemd-analyze dump
> and
> systemctl status .mount
> systemctl show .mount


systemd-automount.tar.gz
Description: application/compressed-tar

Bug#790084: Re : synaptic: Set Internal Options crash

[E/LH/O13B - JULE Corentin]

seems to be duplicate of #774056

Bug#791379: [pkg-gnupg-maint] Bug#791379: gpg2 fails to use agent started by Xsession; automatically started agent works ok

[Joey Hess]

Daniel Kahn Gillmor wrote:
> On Fri 2015-07-03 23:31:57 -0400, Joey Hess wrote:
> > Package: gnupg-agent
> > Version: 2.1.0-1
> > Severity: normal
> 
> I'm a little surprised by this version of gnupg-agent -- i don't think
> it's available anywhere in debian for quite some time.

Hmm, I think I must have installed gnupg2 from experimental back when
this version was originally released. Unstable is still back on version
2.0 so it's not upgraded yet.

> My guess is that you're using pinentry-gnome3 and preferring it over
> pinentry-gtk2 -- there is a bugfix for gnupg-agent in unstable at the
> moment (2.0.28-3) to pass through DBUS_SESSION_BUS_ADDRESS, and it is
> already present in 2.1.6, which should be uploaded to experimental
> sometime today or tomorrow.

The problem certianly has something to do with pinentry-gnome3.

-- 
see shy jo


signature.asc
Description: Digital signature

Bug#790851: autoconf-archive: fails to install: dpkg-maintscript-helper: error: symlink pathname ends with a slash

[Simon McVittie]

On 06/07/15 18:53, John Paul Adrian Glaubitz wrote:
> On 07/05/2015 11:14 AM, Bastien Roucaries wrote:
>> Yes they are an another bug with a conflict. Gnome-common will
>> depend (versionned) on Autoconf-archive. And i will break
>> dépend (versionned)
>> on gnome-common.
>>
>> I supposed being able to depend on instalable version of Autoconf
>> for GNOME common was a priority
> 
> So, should I go ahead and upload now or better wait until gnome-common
> has been fixed to avoid this issue?

I would suggest uploading autoconf-archive to fix #790851 now, without
waiting for a fix for #790936/#790937 - at the moment nobody can install
autoconf-archive, but with #790851 fixed, everyone who does not also
have gnome-common installed will be able to use it. That's a start.

I'm not available to do uploads right now (partial connectivity), but
I'm in the GNOME team, so if nobody has uploaded gnome-common with
#790936 fixed before next week, I'll do a team upload for it. I'd also
be happy to sponsor a maintainer upload for #790937, or add the Breaks
in a minimal NMU, at that point.

S


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791620: vlc: Window decoration issues with the QT5 interface

[Andoru Ekkusu]

Package: vlc
Version: 2.2.1-2+b1


___

First of all, I apologise in advance if this issue is not related to VLC,
but instead it belongs to QT5 or the WM/display drivers, but so far VLC is
the only QT5 application that I noticed those issues surface to.

The issue: VLC loses it's window decorations, and is made unmovable being
stuck on the upper-left corner of the screen (screenshot:
http://i.imgur.com/tGZCzqb.png) after restoring VLC from it's minimised
state. Also even though I might have a window in the background while VLC
is in front, I cannot interact with that background window unless I switch
them manually (Alt+F4 or Super+D as I set them in the WM). This seems to
happen randomly, and is not conditioned on some previous event (starting a
certain app, opening a certain window, etc.) that I know of.


What's worse is that file logging doesn't work properly here for some
reason, so I wouldn't be able to diagnose what exactly is happening. Though
there's something that shows up in ~/.xsession-errors:
http://pastebin.com/aiECtN0N

About my current configuration: As you might have noticed, I'm using tint2,
the WM is OpenBox and I'm on a device with Intel graphics, so I'm using the
open-source drivers (i915)

___

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

Kernel: Linux 4.0-6.dmz.1-liquorix-686-pae (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages vlc depends on:
ii  fonts-freefont-ttf  20120503-4
ii  libaa1  1.4p5-43
ii  libavcodec566:11.4-2
ii  libavutil54 6:11.4-2
ii  libc6   2.19-18
ii  libcaca00.99.beta19-2
ii  libcairo2   1.14.2-2
ii  libegl1-mesa [libegl1-x11]  10.5.8-1
ii  libfreerdp-client1.11.1.0~git20140921.1.440916e+dfsg1-4
ii  libfreerdp-core1.1  1.1.0~git20140921.1.440916e+dfsg1-4
ii  libfreerdp-gdi1.1   1.1.0~git20140921.1.440916e+dfsg1-4
ii  libfreetype62.5.2-4
ii  libfribidi0 0.19.6-3
ii  libgcc1 1:5.1.1-12
ii  libgl1-mesa-glx [libgl1]10.5.8-1
ii  libgles1-mesa [libgles1]10.5.8-1
ii  libgles2-mesa [libgles2]10.5.8-1
ii  libglib2.0-02.44.1-1.1
ii  libpulse0   6.0-2
ii  libqt5core5a5.4.2+dfsg-4
ii  libqt5gui5  5.4.2+dfsg-4
ii  libqt5widgets5  5.4.2+dfsg-4
ii  libqt5x11extras55.4.2-2
ii  librsvg2-2  2.40.9-2
ii  libsdl-image1.2 1.2.12-5+b5
pn  libsdl1.2debian 
ii  libstdc++6  5.1.1-12
ii  libva-drm1  1.6.0-1
ii  libva-x11-1 1.6.0-1
ii  libva1  1.6.0-1
ii  libvlccore8 2.2.1-2+b1
ii  libvncclient1   0.9.10+dfsg-3
ii  libx11-62:1.6.3-1
ii  libxcb-composite0   1.10-3+b1
ii  libxcb-keysyms1 0.4.0-1
ii  libxcb-randr0   1.10-3+b1
ii  libxcb-shm0 1.10-3+b1
ii  libxcb-xv0  1.10-3+b1
ii  libxcb1 1.10-3+b1
ii  libxext62:1.3.3-1
ii  libxinerama12:1.1.3-1+b1
ii  libxpm4 1:3.5.11-1+b1
ii  vlc-nox 2.2.1-2+b1
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages vlc recommends:
ii  vlc-plugin-notify  2.2.1-2+b1
pn  vlc-plugin-samba   
ii  xdg-utils  1.1.0~rc1+git20111210-7.4

Versions of packages vlc suggests:
pn  videolan-doc  

Versions of packages vlc-nox depends on:
ii  liba52-0.7.4   0.7.4-18
ii  libasound2 1.0.29-1
ii  libass50.12.2-1
ii  libavahi-client3   0.6.31-5
ii  libavahi-common3   0.6.31-5
ii  libavc1394-0   0.5.4-2
ii  libavcodec56   6:11.4-2
ii  libavformat56  6:11.4-2
ii  libavutil546:11.4-2
ii  libbasicusageenvironment0  2014.01.13-1
ii  libbluray1 1:0.8.1-1
ii  libc6  2.19-18
ii  libcddb2   1.3.2-5
ii  libcdio13  0.83-4.2
ii  libchromaprint01.2-1
ii  libcrystalhd3  1:0.0~git20110715.fdd2f19-11
ii  libdbus-1-31.8.18-1
ii  libdc1394-22   2.2.3-1
ii  libdca00.0.5-7
ii  libdirectfb-1.2-9  1.2.10.0-5.1
ii  libdvbpsi101.3.0-2
ii  libdvdnav4 5.0.1-4
ii  libdvdread45.0.0-1
ii  libebml4   1.3.1-3
ii  libfaad2   2.8.0~cvs20150510-1
ii  libflac8   1.3.1-2
ii  libfontconfig1 

Bug#778175: Unable to reproduce GCC-5 build issue

[Dall, Elizabeth J]

fixed 778175 3.2.1
thanks

The new version of wxsqlite3 3.2.1 uploaded on April 26, 2015 no longer
has the build issue reported in this bug. There are still a lot of
warnings in the build, but 3.2.1 builds and links with GCC-5.  I suggest
you close this bug.

--
Betty Dall
Linux for HP Helion, Hewlett-Packard


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791619: fusionforge-common: fails to upgrade from 'testing' - trying to overwrite /usr/bin/forge_make_admin

[Andreas Beckmann]

Package: fusionforge-common
Version: 6.0.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + gforge-db-postgresql

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package fusionforge-common.
  Preparing to unpack .../fusionforge-common_6.0.2-1_all.deb ...
  Unpacking fusionforge-common (6.0.2-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/fusionforge-common_6.0.2-1_all.deb (--unpack):
   trying to overwrite '/usr/bin/forge_make_admin', which is also in package 
gforge-db-postgresql 5.3.2+20141104-3+deb8u1


cheers,

Andreas


gforge-db-postgresql_6.0.2-1.log.gz
Description: application/gzip

Bug#791618: FTBFS: assumes linux-source creates /usr/src/linux-source-3.* and it doesn't

[Chris West (Faux)]

Source: cpqarrayd
Version: 2.3-3
Severity: serious
Tags: sid
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs

Dear Maintainer,

The package fails to build in sid, as linux-source installs linux-source 4.0,
and hence debian/rules fails to find it:

 $(wildcard /usr/src/linux-source-3.*.tar.xz) ..

-- https://sources.debian.net/src/cpqarrayd/2.3-3/debian/rules/#L19

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/cpqarrayd.html

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

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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791617: New upstream release available

[Martin Michlmayr]

Package: mod-wsgi
Severity: wishlist

Version 4.4.13 is available from 
https://github.com/GrahamDumpleton/mod_wsgi/releases

-- 
Martin Michlmayr
Linux for HP Helion, Hewlett-Packard


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791599: xserver-xorg-video-intel: loss of hardware acceleration after resume

[Julien Cristau]

On Mon, Jul  6, 2015 at 16:44:37 +0100, olsen wrote:

> Package: xserver-xorg-video-intel
> Version: 2:2.99.917-1~bpo8+1
> Severity: important
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>* What led up to the situation?
>   The problem becomes apparent for example if I start chromium 
> and try to move the whole browser window by holding down the alt key + the 
> mouse, resulting in almost slow motion.
>   Similar effects with Iceweasel on various websites e.g. 
> googlemaps. This is after a fresh reboot.
>   Furthermore I noticed after a couple of resumes I can't play 
> videos with the default settings any more, e.g. in mplayer only with the -xv 
> X11 option.
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>   I switched from testing to experimental 
> (xserver-xorg-video-intel 2:2.99.917-1~bpo8+1) both with "uxa" acceleration 
> in /etc/X11/xorg.conf.d/20-intel.conf as follows:
>   Section "Device"
> Identifier  "Intel Graphics"
>   Driver  "intel"
>   Option  "AccelMethod"  "uxa"
>   EndSection
>* What was the outcome of this action?
>   Slightly better performance but the issue still remains, 
> especially the loss of the acceleration after resumes.
>* What outcome did you expect instead?
>   No loss of the hardware acceleration
> 
Does that also happen with a newer kernel and/or mesa?

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#791616: gitit: Please pack newer release version

[Dionisio E Alonso]

Package: gitit
Version: 0.10.7-2+b1
Severity: wishlist
Tags: upstream

There is a newer release version 0.11 on GitHub
(https://github.com/jgm/gitit/releases). Please pack it.

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

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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791615: scikit-learn: FTBFS sid/experimental: dist_metrics.pyx: _rdist_to_dist not compatiable

[Chris West (Faux)]

Source: scikit-learn
Version: 0.16.1-1
Severity: serious
Tags: sid experimental
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs

Dear Maintainer,

The package fails to build in experimental, and in sid.

First, we get an..

Error compiling Cython file:


cdef DTYPE_t sin_0 = sin(0.5 * (x1[0] - x2[0]))
cdef DTYPE_t sin_1 = sin(0.5 * (x1[1] - x2[1]))
return 2 * asin(sqrt(sin_0 * sin_0
 + cos(x1[0]) * cos(x2[0]) * sin_1 * sin_1))

cdef inline DTYPE_t _rdist_to_dist(self, DTYPE_t rdist):
^


sklearn/neighbors/dist_metrics.pyx:984:9: Signature not compatible with 
previous declaration

 which then becomes a:

sklearn/neighbors/dist_metrics.c:1:2: error: #error Do not use this file, it is 
the result of a failed Cython compilation.

 which actually kills the build.

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/scikit-learn.html

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

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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#789726: owncloud: add support for multiple instances

[David Prévot]

Hi,

We already had a few words on IRC with Thiago, but let me write some
ideas down before I forget.

On Tue, Jun 23, 2015 at 06:38:05PM -0300, Thiago Ribeiro wrote:
> Package: owncloud
> Version: 7.0.6+dfsg-1
> Severity: wishlist
> Tags: patch

> owncloud […] does
> not support multiple instances without duplicating the owncloud source tree.
> 
> The upstream community is still discussing that possibility:
> https://github.com/owncloud/core/pull/16424
> 
> I've made a patch based on the changes in that pull request, which makes it
> possible to have separate instances of owncloud, with separate
> database and data folders.

That is very welcome, thank you for working on that!

> Please consider applying it to the Debian package.

Sure, but IMHO, adding this feature to the version 7 is not worth it: we
intend to maintain (and especially backport security fixes on)
owncloud 7 because that is the version shipped in Jessie, but the
packaging for owncloud 8.1 is ready for quite some time already (not
pushed yet to experimental since some dependencies are being processed
in NEW).

> If you are OK with carrying this patch while the upstream community
> discusses it,

Yes, I do hope this feature will make it upstream, but would be happy to
consider it for Stretch no matter what. If you can rebase your patch on
the current stable8 branch of our repository, that would be nice.

> I can also update the documentation with a simple tutorial on how to do
> this.

Thank you for your proposal. Hopefully, a short (entry in the current)
README will be enough (i.e., there won’t be too much work for
administrators to set up multiple instances).

> with this patch, I managed three instances of owncloud, also I wrote a
> cookbook that makes instalation and configurations that are required.

That looks nice, I hope I’ll be able to follow you up on that (maybe
during a face to face if you’ll be in DebCamp or DebConf).

Regards

David


signature.asc
Description: Digital signature

Bug#791614: lava-dispatcher: prompting due to modified conffiles upon initial installation: /etc/default/tftpd-hpa

[Andreas Beckmann]

Package: lava-dispatcher
Version: 2015.07-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + lava

Hi,

during a test with piuparts I noticed your package failed the piuparts
upgrade test because dpkg detected a conffile as being modified and then
prompted the user for an action. As there is no user input, this fails.
But this is not the real problem, the real problem is that this prompt
shows up in the first place, as there was nobody modifying this conffile
at all, the package is just being installed...

This is a violation of policy 10.7.3, see
https://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3,
which says "[These scripts handling conffiles] must not ask unnecessary
questions (particularly during upgrades), and must otherwise be good
citizens."

https://wiki.debian.org/DpkgConffileHandling should help with figuring
out how to do this properly.

In https://lists.debian.org/debian-devel/2009/08/msg00675.html and
followups it has been agreed that these bugs are to be filed with
severity serious.

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

  Setting up lava-dispatcher (2015.07-1) ...
  
  Configuration file '/etc/default/tftpd-hpa'
   ==> File on system created by you or by a script.
   ==> File also in package provided by package maintainer.
 What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
   The default action is to keep your current version.
  *** tftpd-hpa (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package 
lava-dispatcher (--configure):
   end of file on stdin at conffile prompt


cheers,

Andreas


lava_2015.07-1.log.gz
Description: application/gzip

Bug#786780: Metastudent and its data (Was: Bug#786780: metastudent has circular Depends on metastudent-data)

[Laszlo Kajan]

Hello Andreas!

On 06/07/15 13:40, Andreas Tille wrote:
> at first thanks for maintaining metastudent in the Debian Med team.  I
> guess you did not yet realised this bug report since there is no
> response in the bug log.  Please note that bugs in the Debian BTS are

I think this was fixed in metastudent-data by changing the Depends on 
metastudent (>= 2.0.0) to 'Breaks: metastudent (<< 2.0.0)'.
Tobias forgot to close the bug in the changelog, and apparently forgot to email 
the bug tracker as well.
@Tobi: do you remember those commands and links I sent you about this?

I will let Tobias explain the rest. In short, I think that dependency is a hard 
'Depends' on the data package, and not a 'Recommends', because
it is very unlikely that anyone but upstream would be able to generate that 
data package (@Tobi: correct me if I am wrong), and the software
will be useless without it. The reason for breaking metastudent up to 
metastudent(-data\d)? is technical: to allow uploads of a small, but more
frequently-changing non-data package, avoiding the need to upload versions of a 
large data package.

Best regards,
Laszlo



signature.asc
Description: OpenPGP digital signature

Bug#782287: hw-detect: install open-vm-tools in d-i

[Oliver Kurth]

​open-vm-tools is mainly about user space tools. Kernel drivers have been 
either obsoleted, or are part of the current Linux kernel. The only kernel 
module still needed from open-vm-tools is vmhgfs, which we plan to obsolete in 
the future when we migrate to using FUSE. But vmhgfs could be distributed as a 
separate package from open-vm-tools, and made optional.

I think the patch can be modified such that open-vm-tools will only be 
installed if it is available.

About the non-transparent development process, please let me know what exactly 
the concerns are. We do not use github as our primary repository for tools, 
therefore each release it published in one huge commit. But I am sure the 
process can be improved, if we know the concerns.


 

Bug#791478: [Openexr-devel] testOptimizedInterleavePatterns.cpp

[Ed Hanway]

It is noted in the comments for this issue: 
https://github.com/openexr/openexr/issues/67  Per the latest comment on the 
issue thread, the problem is in the test rather than in the library itself.  
Sorry that it hasn't been addressed since the issue was filed in 2013 -- it 
doesn't show up on the platforms we use regularly build for, which are mainly 
64-bit, or we would have cleaned it up long ago.

From: openexr-devel-bounces+ehanway=ilm@nongnu.org 
[mailto:openexr-devel-bounces+ehanway=ilm@nongnu.org] On Behalf Of Mathieu 
Malaterre
Sent: Sunday, July 05, 2015 9:35 AM
To: openexr-de...@nongnu.org
Cc: 791...@bugs.debian.org
Subject: [Openexr-devel] testOptimizedInterleavePatterns.cpp

Hi all,

I am preparing the debian package for openexr. I am running in the following 
issue, when the test suite runs, here is what I get (debian jessie x86/32bits):

[...]
Running testOptimizedInterleavePatterns
Testing SSE optimisation with different interleave patterns (large images)
...
 0, 0: RGBHalf read as RGBHalf...OK
 0, 1: RGBHalf read as RGBAHalf...   OK
 0, 2: RGBHalf read as ABGRHalf...   OK
 0, 3: RGBHalf read as RGBFloat...

error reading back channel B pixel 96,-62 got -nan expected -nan
lt-IlmImfTest: testOptimizedInterleavePatterns.cpp:238: bool
{anonymous}::compare(const Imf_2_2::FrameBuffer&, const
Imf_2_2::FrameBuffer&, const Box2i&, bool): Assertion
`writtenHalf.bits()==readHalf.bits()' failed.
/bin/bash: line 5: 25131 Aborted ${dir}$tst
FAIL: IlmImfTest
==
1 of 1 test failed
==
[...]

This is a hard-failure based on an assert(). Is there an actual issue in 
openexr 2.2.0 ?

Thanks much,