date:20150103

Control: tags -1 - moreinfo
Control: reassign -1 mplayer2 2.0-728-g2c378c7-4

On 2014-07-26 13:55:40, Reinhard Tartler wrote:
 Control: tag -1 upstream moreinfo
 
 Hi Sthu,
 
 I'm reviewing old bugs in the debian bug tracking system. Can you
 please take a few minutes to revisit
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647479? Is this
 still an issue? Does it reproduce with avplay or avprobe? Please
 provide an example file that exhibits this problem.
 
 Thanks and sorry for taking so long to get back to you.

I was able to reproduce the issue:

$ mplayer 01.\ False\ Awakening\ Suite.flac
MPlayer2 2.0-728-g2c378c7-4+b1 (C) 2000-2012 MPlayer Team
Cannot open file '/home/sebastian/.mplayer/input.conf': No such file or 
directory
Failed to open /home/sebastian/.mplayer/input.conf.
Cannot open file '/etc/mplayer/input.conf': No such file or directory
Failed to open /etc/mplayer/input.conf.

Playing 01. False Awakening Suite.flac.
Detected file format: raw FLAC (libavformat)
[flac @ 0x7f02ab49cb40]max_analyze_duration 500 reached
[lavf] stream 0: audio (flac), -aid 0
Clip info:
 ALBUM: Dream Theater
 ARTIST: Dream Theater
 DATE: 2013
 TITLE: False Awakening Suite
 TRACKTOTAL: 9
 track: 1
 REPLAYGAIN_ALBUM_GAIN: -10.90 dB
 REPLAYGAIN_ALBUM_PEAK: 1.00
 REPLAYGAIN_TRACK_GAIN: -9.23 dB
 REPLAYGAIN_TRACK_PEAK: 1.00
Selected audio codec: FLAC (Free Lossless Audio Codec) [libavcodec]
AUDIO: 44100 Hz, 2 ch, s16le, 0.0 kbit/0.00% (ratio: 0-176400)
AO: [pulse] 44100Hz 2ch s16le (2 bytes per sample)
Video: no video
Starting playback...
A:   4.3 (04.2) of 162.1 (02:42.1)  0.3% 


MPlayer interrupted by signal 2 in module: unknown

Exiting... (Quit)

$ avprobe 01.\ False\ Awakening\ Suite.flac
avprobe version 11.1-6:11.1-1, Copyright (c) 2007-2014 the Libav developers
  built on Dec 30 2014 17:31:25 with gcc 4.9.2 (Debian 4.9.2-9)
[flac @ 0xf6c760] max_analyze_duration 500 reached
Input #0, flac, from '01. False Awakening Suite.flac':
  Metadata:
ALBUM   : Dream Theater
ARTIST  : Dream Theater
DATE: 2013
TITLE   : False Awakening Suite
TRACKTOTAL  : 9
track   : 1
REPLAYGAIN_ALBUM_GAIN: -10.90 dB
REPLAYGAIN_ALBUM_PEAK: 1.00
REPLAYGAIN_TRACK_GAIN: -9.23 dB
REPLAYGAIN_TRACK_PEAK: 1.00
  Duration: 00:02:42.10, bitrate: 970 kb/s
Stream #0.0: Audio: flac, 44100 Hz, stereo, s16
Side data:
  replaygain: track gain - -9.23, track peak - 0.23, album gain - 
-10.90, album peak - 0.23, 
# avprobe output

This looks like a bug in mplayer2 too me.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature

Bug#694616: libav-tools: avprobe does not support -show_frames option from ffprobe

Control: tags -1 moreinfo upstream

On 2012-11-28 12:02:28, David Banks wrote:
 Package: libav-tools
 Version: 6:0.8.4-1
 Severity: wishlist
 File: /usr/bin/avprobe
 
 Hey,
 
 The 'ffprobe' tool from ffmpeg supports the option -show_frames, which 
 produces
 output like the following:
 
   [FRAME]
   media_type=video
   key_frame=1
   pkt_pts=N/A
   pkt_pts_time=N/A
   pkt_dts=1
   pkt_dts_time=0.04
   pkt_duration=1
   pkt_duration_time=0.04
   pkt_pos=17724
   width=608
   height=336
   pix_fmt=yuv420p
   sample_aspect_ratio=1:1
   pict_type=I
   coded_picture_number=0
   display_picture_number=0
   interlaced_frame=0
   top_field_first=0
   repeat_pict=0
   reference=3
   [/FRAME]
   ...
 
 It prints detailed per-frame information.  It differs from the output of
 -show_packets, which avprobe does support, by showing more detailed 
 information
 about the video encoding.  This example output is from the 'ffprobe' in the
 upstream git repository of ffmpeg.  The 'ffprobe' that was in squeeze also
 supports the -show_frames option, so in some ways this is a feature regression
 with the libav transition.  However, the output from the ffprobe in squeeze is
 considerably less detailed, and didn't work for some files that I tested on; 
 so
 merging the code from ffmpeg would be preferable.

Sorry for the long delay in getting back to you. This needs to be
implemented upstream. Could you take this upstream by filing a bug
report following https://libav.org/bugreports.html?

Please let us know the bug number so we can track the issue.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature

Bug#769576: linux: Btrfs goes forced readonly when qgroup already exists

2015-01-03 Thread Joseph Salisbury


On 12/23/2014 09:34 AM, Sebastiaan L. Zoutendijk wrote:

Dear Ubuntu Kernel Team,

I would like to request an upstream patch [1] to be applied to the 3.16
kernel.  This patch prevents Btrfs filesystems from going readonly when
a subvolume ID is reused but the corresponding qgroup wasn't destroyed
when the original subvolume was deleted.  This patch has been applied by
upstream to 3.17 [2], but not to 3.16 before it went EOL.  For more
details on the bug, please have a look at the Debian bug log [3].  That
log also contains instructions to reproduce the bug, dmesg output, and
my tests of the patch on various kernel versions.

  [1] https://patchwork.kernel.org/patch/4739211/
  [2] 
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=fe9133f10ca56e54c5f5075a802bc08e61ad8456
  [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769576

[Please keep 769576-forwar...@bugs.debian.org in the CC, this will log
your reply in the Debian bug tracker.  If you also want your reply to be
sent on to the Debian Kernel Team, please keep 769...@bugs.debian.org in
the CC.]

Would it be possible for you to also open a bug in Launchpad for this?  
It can be done by running the following from a terminal:


ubuntu-bug linux

Thanks,

Joe


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

Bug#774518: libupnp6-doc: fails reproducible-build because Doxygen inserts the build timestamp

2015-01-03 Thread Nick Leverton

Package: libupnp6-doc
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps

Doxygen includes timestamps in the generated HTML output.  This results
in libupnp6-doc builds not being binary reproducible.  Needs the new
HTML_TIMESTAMP=No option setting in Doxyfile.

https://wiki.debian.org/ReproducibleBuilds

https://reproducible.debian.net/userContent/rb-pkg/libupnp.html
Description: Do not write timestamps in documentation generated by Doxygen
 In order to make the build reproducible, we configure Doxygen to skip
 writing timestamps in the HTML documentation it generates.
Author: Jérémy Bobbio lu...@debian.org
Last-Update: 2014-09-24

Index: libupnp-1.6.19+git20141001.dev/Doxyfile
===
--- libupnp-1.6.19+git20141001.dev.orig/Doxyfile	2015-01-03 18:54:36.0 +
+++ libupnp-1.6.19+git20141001.dev/Doxyfile	2015-01-03 20:47:46.0 +
@@ -675,6 +675,14 @@
 
 HTML_FOOTER= 
 
+# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
+# page will contain the date and time when the page was generated. Setting this
+# to NO can help when comparing the output of multiple runs.
+# The default value is: YES.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+HTML_TIMESTAMP = NO
+
 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading 
 # style sheet that is used by each HTML page. It can be used to 
 # fine-tune the look of the HTML output. If the tag is left blank doxygen

Bug#774517: grub-pc: README material to help in troubleshooting password setting

2015-01-03 Thread Yann Dirson

Package: grub-pc
Version: 2.02~beta2-19
Severity: wishlist
Tags: patch

When setting up grub to password-protect commandline edition (see
configuration hints in my comment to #545163), it can take some effort
in case of error to determine whether the password is wrong, or
whether it is wrongly entered because of the keyboard layout.

What I wanted to do is to check that the password I expected was the
one in the password_pbkdf2 statement, which required a bit of work,
since grub-mkpasswd-pbkdf2 generates a new salt on each run.

The attached python script generates the hashed password from the
password and the salt.  Comparison is lefta as an exercise through
visual inspection :)
#!/usr/bin/python

from Crypto.Hash import SHA512
import pbkdf2
import sys

# default grub-mkpasswd-pbkdf2 settings
ITERATIONS = 1
LENGTH = 64

def unpack(s):
if s:
   return chr(int(s[:2], base=16)) + unpack(s[2:])
return ''

_, passwd, salt = sys.argv

print pbkdf2.PBKDF2(passwd, unpack(salt),
iterations=ITERATIONS,
digestmodule=SHA512).hexread(LENGTH).upper()

Bug#774361: how to play?

2015-01-03 Thread Markus Koschany

On 03.01.2015 21:20, Tomas Pospisek wrote:
[...]
 Please do mention the README.lgeneral.gz file as that has a
 description of the controls. 

I did:

Please also read README.lgeneral for further instructions
on how to play the game.

[...]
 I think the man page is fine because lgeneral really is only the engine.
 
 Again, as a user, I very like might not know that. I install the
 package, then type lgeneral on the command line. The game starts. And
 now what? So I either search for a README or I type man lgeneral. And
 that should give me the info that's necessary. According to Unix
 tradition all necessary should be contained in the man page.

I don't think it is helpful if we repeat the same information over and
over again. The man page should contain precise information about the
engine's commands and it is not a replacement for other documentation.
There are two README files under /usr/share/doc/lgeneral and after
reading them everyone should now be able to play the game.





signature.asc
Description: OpenPGP digital signature

Bug#757298: Please add fallback boot entry for sysvinit when systemd is the active init

2015-01-03 Thread Michael Biebl

Am 03.01.2015 um 13:28 schrieb Colin Watson:
 To be honest, I would be inclined to just omit the triggering entirely.
 update-grub is already called in plenty of situations and we probably
 don't need the complexity at this point; I certainly don't want to try
 to insert dpkg triggers at this stage.

You're probably right.

 I've combined your patch with that from Didier in #773173 (though
 without the extra configuration variables in the latter) and pushed a
 gestalt version to git.  I should manage to upload this today.

Great, thanks a lot!

Happy new year,
Michael

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



signature.asc
Description: OpenPGP digital signature

Bug#514464: ping?

2015-01-03 Thread Lukasz Stelmach

Helo,

Any news? Debian 7.7 is still affected.

This is all weird. 

CtrlL_Lock doesn't turn on the led but works fine for all Polish
diacritics.

Caps_Lock turns on led on the led but only Ó is correctly
capitalised.

-- 
Było mi bardzo miło.   Twoje oczy lubią mnie
Łukasz i to mnie zgubi  (c)SNL



signature.asc
Description: OpenPGP digital signature

Bug#764162: Regression with kernel 3.16.7-ckt2-1

2015-01-03 Thread Rogério Brito

Dear Ian,

First of all, thank you very much for the reply. I wasn't able to reply
earlier due to end of year activities, but now I will try to be as speedy as
feasible.

On Dec 31 2014, Ian Campbell wrote:
 On Wed, 2014-12-31 at 06:08 -0200, Rogério Brito wrote:
  I have a Kurobox Pro that I use as a NAS and I was affected by the network
  corruption when the TSO was enabled in versions 3.16 before the version with
  the workaround on the mv643xx_eth (not having seen the code, from a user's
  perspective, this workaround was more like a fix than a dirty hack).
 
 The workaround was just turning off the feature.

Exactly. This is what I did with ethtool.

 Please can you clarify which of these kernels did/didn't work (or for
 which you have no data):
   * 3.16.7-1 (has the bug)

I had the bug with this and I even put the last 3.14 that I had available
here on hold and, I was running all the time

,
| flash-kernel --force 3.14-2-orion5x
`

To prevent problems in the case of a power outage here and my wife booting
the NAS, as there are some educative programs that my little son watches
every day.

I even thought that the days of that device were counted, given that some
newer userspace is likely to require newer kernel versions and that this
device's live would be cut short (before I knew what the problem was---I was
only seeing the symptoms).

I did not report the problem because I thought that I would have little
success in explaining the problem (and doing git bisects on this thing would
be seriously would take so many weeks).  I was so happy that I wasn't the
only person seeing corruption with the 3.16.7-1 kernel!

   * 3.16.7-2 (with the hack/workaround of disabling TSO by default)

With this, I had *no* problems and I was relieved that things went back to
work just fine, without data corruption. (I also use this NAS as a way to
backup some of my data---if there is silent data corruption, then I would be
in trouble).

   * 3.16.7-ckt2-1 (with the supposed proper fix, 2c2a9cb from
 upstream, backported via the -ckt tree)

This brought me back the problematic situation of the 3.16.7-1. To avoid
forcing flash-kernel with the command above, I tried to turn TSO off and I
see no signs of corruption.

 FWIW I am running 3.16.7-ckt2-1 on my kirkwood based ts-419 right now
 and it seems fine. It's possible that your system has a separate issue
 or is somehow more susceptible to the original (Which IIRC was cache
 based, so could affect different platforms differently).

I have not read the code of the commit nor the context of fix,
unfortunately.

 Please can you also confirm that flash-kernel has been run and is
 picking up the correct kernel image, i.e. it hasn't installed an old
 kernel for you or something like that. uname -v includes the actual
 running version.

Sure. Here you go:

,[ uname -a ]
| Linux lattes 3.16.0-4-orion5x #1 Debian 3.16.7-ckt2-1 (2014-12-08) armv5tel 
GNU/Linux
`

  Can we get a fix for this in time for jessie?
 
 If one can be found of course we will try and apply it.

Thank you very much for being open to this possibility.

 Since I can't reproduce it would be useful if you could take this issue
 to the upstream developers who were involved in the original bug report
 and work with them directly to find a cure.

I may try, but I am not confident that I will have any success. :(

 If we can't find one then I suppose we will fall back to just disabling
 TSO by default on these systems.

Yes. In absence of further data, between data corruption an a performance
hit, the choice is quite easy.


Thanks,

-- 
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://cynic.cc/blog/ : github.com/rbrito : profiles.google.com/rbrito
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br


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

Bug#774492: [vim] c{motion} temporary cancels 'linebreak' option for current line

2015-01-03 Thread Dmitry Alexandrov


Package: vim
Version: 2:7.4.488-3
Severity: normal

When the 'linebreak' option (visually break long lines at spaces only 
rather than at a middle of a word) is set c{motion} command (but not 
d or x or i) cause current real line to be re-flowed like as the 
'linebreak' is not set.


This affects both GVim and terminal Vim with the minimal configuration 
('number' for the sake of demonstration):


  $ vim -u NONE -U NONE -N '+set linebreak' '+set number'

Suppose a buffer is 70-character-wide and looks like:

  1 “Free software” means software that respects users' freedom and
community. Roughly, it means that the users have the freedom to
run, copy, distribute, study, change and improve the software.
Thus, “free software” is a matter of liberty, not price. To
understand the concept, you should think of “free” as in “free
speech,” not as in “free beer”.

Now if I press c and some motion in any cursor position (for example, 
cl in 1,1) buffer would look like:


  1 Free software” means software that respects users' freedom and commu
nity. Roughly, it means that the users have the freedom to run, copy
, distribute, study, change and improve the software. Thus, “free so
ftware” is a matter of liberty, not price. To understand the concept
, you should think of “free” as in “free speech,” not as in “free be
er”.

When I leave the insert mode and continue edition, as the buffer is 
redrawn, it returns to the proper look until the next c{motion}.


I’ve tested other Vim versions available at snapshots.debian.org [0]: 
the first problematic is 7.4.481-1, so the last unaffected is 7.4.430-1.


[0]: http://snapshot.debian.org/binary/vim/

--- System information. ---
Architecture: amd64
Kernel:   Linux 3.2.0-4-amd64

Debian Release: 8.0
  500 trusty  ppa.launchpad.net
  500 testing www.deb-multimedia.org
  500 testing security.debian.org
  500 stable  deb.i2p2.no
  500 oneiric ppa.launchpad.net
 1995 oneiric ppa.launchpad.net
   10 unstablesnapshot.debian.org

--- Package information. ---
Depends   (Version) | Installed
===-+-
vim-common  (= 2:7.4.430-1) | 2:7.4.488-3
vim-runtime (= 2:7.4.430-1) | 2:7.4.488-3
libacl1   (= 2.2.51-8) | 2.2.52-2
libc6 (= 2.15) |
libgpm2 (= 1.20.4) |
libselinux1   (= 1.32) |
libtinfo5   |


Package's Recommends field is empty.

Suggests (Version) | Installed
==-+-===
ctags  |
vim-doc| 2:7.4.488-3
vim-scripts| 20130814



--- Output from package bug script ---

--- real paths of main Vim binaries ---
/usr/bin/vi is /usr/bin/vim.gtk
/usr/bin/vim is /usr/bin/vim.gtk
/usr/bin/gvim is /usr/bin/vim.gtk


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

Bug#774491: clang-3.5: No symlink like bug #737471

2015-01-03 Thread Aldo

Package: clang-3.5
Version: 1:3.5-9
Severity: important
Tags: newcomer

Dear Maintainer,

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


   Must have symlink and option for alternatives.
   
   Codeblock do not detect compiler because clang symlinks are not ok.
   
   it is the same with 3.4 etc...

   so:
   and create symlink in debian install package
   add and offer to use alternatives for this compiler.
   
   
*** End of the template - remove these template lines ***


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

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

Versions of packages clang-3.5 depends on:
ii  binutils 2.24.90.20141023-1
ii  libc62.19-13
ii  libc6-dev2.19-13
ii  libclang-common-3.5-dev  1:3.5-9
ii  libclang1-3.51:3.5-9
ii  libedit2 3.1-20140620-2
ii  libffi6  3.1-2+b2
ii  libgcc-4.9-dev   4.9.1-19
ii  libgcc1  1:4.9.1-19
ii  libllvm3.5   1:3.5-9
ii  libobjc-4.9-dev  4.9.1-19
ii  libstdc++-4.9-dev4.9.1-19
ii  libstdc++6   4.9.1-19
ii  libtinfo55.9+20140913-1+b1
ii  zlib1g   1:1.2.8.dfsg-2+b1

Versions of packages clang-3.5 recommends:
ii  llvm-3.5-dev  1:3.5-9
ii  python2.7.8-2

Versions of packages clang-3.5 suggests:
pn  clang-3.5-doc  none
pn  gnustepnone
pn  gnustep-devel  none

-- 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#754071: [Python-apps-team] Bug#754071: python-pelican : please include docuemnts or make python-pelican-doc package.

2015-01-03 Thread Vincent Cheng

Control: tag -1 + patch

On Fri, Jan 2, 2015 at 8:16 AM, Federico Ceratto
federico.cera...@gmail.com wrote:
 Package: python-pelican
 Version: 3.5.0-1
 Followup-For: Bug #754071

 Hello Vincent and thank you for maintaining the package. Attached is a patch 
 to
 build the -doc package. I had to switch debian/watch to use the tarball from
 GitHub as the PyPI version has no documentation in it.
 Also I switched to dh_python to simplify the build, I hope you don't mind.

Thanks for the patch! I skimmed through it and it looks good to me,
except that you're missing a build-dep on dh-python (since you're now
using dh_python/pybuild).

I'll hold off on uploading this for now, since Debian is in freeze and
the upload requires that I use a different orig tarball (which won't
work with the same upstream version unless I mangle the version,
urgh). But I'll include this in my next pelican upload. :)

Regards,
Vincent


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

Bug#774490: tar: Please generate -dbg package for tar

2015-01-03 Thread Vincent Stehl?

Package: tar
Version: 1.27.1-2+b1
Severity: wishlist

Dear Maintainer,

Would you please consider generating a `-dbg' package for tar, with debug 
symbols?

This is useful for example when using `perf top' on a system where top is in
the first consumers. This should help also for capturing backtraces in case of
crash, or for debugging.

Thank you for Debian tar!

V.

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages tar depends on:
ii  libacl1  2.2.52-2
ii  libc62.19-13
ii  libselinux1  2.3-2

tar recommends no packages.

Versions of packages tar suggests:
ii  bzip21.0.6-7+b2
pn  ncompressnone
pn  tar-scripts  none
ii  xz-utils 5.1.1alpha+20120614-2+b3


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

Bug#312265: IT Notification!

2015-01-03 Thread Hassan BILAAL



This is your IT Service Desk sending you this email for your account UPDATE, we 
are conducting an upgrade in all email account for the new year, all users are 
to verify his/her account for upgrade, CLICK HERE: http://tinyurl.com/ogf268v 
fill out the upgrade form and click FINISH.

We apologize for any inconvenience and do appreciate your understanding.

Yours,
IT-Helpdesk Service.


The information contained in this electronic message and any attachments is 
intended for specific individuals or entities, and may be confidential, 
proprietary or privileged. If you are not the intended recipient, please notify 
the sender immediately, delete this message and do not disclose, distribute or 
copy it to any third party or otherwise use this message. The content of this 
message does not necessarily reflect the official position of the World Food 
Programme. Electronic messages are not secure or error free and may contain 
viruses or may be delayed, and the sender is not liable for any of these 
occurrences. The sender reserves the right to monitor, record and retain 
electronic messages.

Bug#644912: works for getaddrinfo but not if AF_INET6 specified

2015-01-03 Thread chrysn

hello,

i've tested the patch on 0.10-6, it applies with small offsets, and
things work as described in the patch mail.

with explicitly specified AF instead of looking through the list to
find the v6 addresses, however, the interface index is zero as before
the patch:

$ python -c 'import socket; print socket.getaddrinfo(hephaistos.local, None)'
[(10, 1, 6, '', ('fe80::800:27ff:fe00:0%vboxnet0', 0, 0, 8)),
(10, 2, 17, '', ('fe80::800:27ff:fe00:0%vboxnet0', 0, 0, 8)),
(10, 3, 0, '', ('fe80::800:27ff:fe00:0%vboxnet0', 0, 0, 8)),
(2, 1, 6, '', ('10.13.13.131', 0)),
(2, 2, 17, '', ('10.13.13.131', 0)),
(2, 3, 0, '', ('10.13.13.131', 0))]
$ python -c 'import socket; print socket.getaddrinfo(hephaistos.local, None, 
socket.AF_INET6)'
[(10, 1, 6, '', ('fe80::800:27ff:fe00:0', 0, 0, 0)),
(10, 2, 17, '', ('fe80::800:27ff:fe00:0', 0, 0, 0)),
(10, 3, 0, '', ('fe80::800:27ff:fe00:0', 0, 0, 0))]

my testing may be faulty due to any stale caches -- i've installed the
patched version using dpkg and restarted avahi-daemon, anything else i
should have flushed?

best regards
chrysn

-- 
Ceterum censeo https://bugs.debian.org/466014 esse resolvendum.


signature.asc
Description: Digital signature

Bug#774364: release.debian.org: wheezy-pu: package debian-archive-keyring/2014.3~deb7u1

2015-01-03 Thread Jonathan Wiltshire

On Fri, Jan 02, 2015 at 06:25:24PM +, Adam D. Barratt wrote:
 Control: tag -1 + pending
 
 On Thu, 2015-01-01 at 23:21 +, Adam D. Barratt wrote:
  On Thu, 2015-01-01 at 22:51 +, Jonathan Wiltshire wrote:
   Control: tag -1 confirmed
   
   On Thu, Jan 01, 2015 at 02:56:41PM +, Adam D. Barratt wrote:
I'd like to backport the recently uploaded debian-archive-keyring
package to wheezy, to introduce the new archive signing keys for Jessie.

A debdiff since the package currently in wheezy is attached.
   
   Please go ahead.
  
  Thanks; uploaded.
 
 Apparently someone accepted it. Thanks. :-)

Indeed, but then realised I couldn't reply to the bug right there and then.

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51



signature.asc
Description: Digital signature

Bug#774457: unblock: gcompris/14.12-1

2015-01-03 Thread Jonathan Wiltshire

Control: tag -1 confirmed moreinfo

On Sat, Jan 03, 2015 at 12:15:27AM +0100, Yann Dirson wrote:
 This is a followup to #774136 to get pre-approval for gcompris 14.12-1
 (new upstream release with mostly translation updates and addition of
 a new language).

It's rather larger than I was hoping for, but with appropriate filtering
it's just about acceptable. You'll have to clear NEW; please go ahead and
ask ftp-masters to process it as soon as possible, and then ping this bug.

Thanks,

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51



signature.asc
Description: Digital signature

Bug#774504: debianutils: please make the build reproducible

Source: debianutils
Version: 4.4
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps fileordering

Hi!

While working on the “reproducible builds” effort [1], we have noticed
that debianutils could not be built reproducibly.

The attached patches make several small changes to debian/rules. Once
applied, debianutils can be built reproducibly on our current
experimental framework.

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

-- 
Lunar.''`. 
lu...@debian.org: :Ⓐ  :  # apt-get install anarchism
`. `'` 
  `-   
From deb21fda25109c104b81cc0536061bb14f426395 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=A9r=C3=A9my=20Bobbio?= lu...@debian.org
Date: Sat, 3 Jan 2015 16:16:35 +0100
Subject: [PATCH 1/3] Stop recording current time when using gzip

To enable debianutils to build reproducibly, we stop recording
the current time when using gzip.
---
 debian/rules | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/rules b/debian/rules
index 3f8c874..85b0a2a 100755
--- a/debian/rules
+++ b/debian/rules
@@ -93,7 +93,7 @@ endif
 	 debian/tmp/usr/share/man/ja/man[18] \
 	 debian/tmp/usr/share/man/pl/man[18] \
 	 debian/tmp/usr/share/man/sl/man[18] \
- debian/tmp/usr/share/doc/$(package) -type f | xargs gzip -9
+ debian/tmp/usr/share/doc/$(package) -type f | xargs gzip -9n
 	$(INSTALL_FILE) debian/copyright debian/tmp/usr/share/doc/$(package)
 	$(INSTALL_SCRIPT) debian/postinst debian/tmp/DEBIAN/
 	$(INSTALL_SCRIPT) debian/postrm debian/tmp/DEBIAN/
-- 
2.1.3

From 8a9a36d7b2a0c481a5b3c08305d192ac26933fc8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=A9r=C3=A9my=20Bobbio?= lu...@debian.org
Date: Sat, 3 Jan 2015 16:16:47 +0100
Subject: [PATCH 2/3] Sort file list when generating md5sums

In order to make debianutils builds reproducible, the list in md5sums must be
in a stable order. Sorting is the easiest way to achieve this.
---
 debian/rules | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/rules b/debian/rules
index 85b0a2a..b09c52c 100755
--- a/debian/rules
+++ b/debian/rules
@@ -98,7 +98,7 @@ endif
 	$(INSTALL_SCRIPT) debian/postinst debian/tmp/DEBIAN/
 	$(INSTALL_SCRIPT) debian/postrm debian/tmp/DEBIAN/
 
-	cd debian/tmp  find * -type f ! -regex '^DEBIAN/.*' -print0 | xargs -r0 md5sum  DEBIAN/md5sums
+	cd debian/tmp  find * -type f ! -regex '^DEBIAN/.*' -print0 | LC_ALL=C sort -z | xargs -r0 md5sum  DEBIAN/md5sums
 
 	dpkg-shlibdeps debian/tmp/bin/run-parts \
 			debian/tmp/bin/tempfile \
-- 
2.1.3

From b0ece24738e8ffcbc5c18fecd680704d031695a3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=A9r=C3=A9my=20Bobbio?= lu...@debian.org
Date: Sat, 3 Jan 2015 16:18:11 +0100
Subject: [PATCH 3/3] Fix mtimes before building binary packages

To enable debianutil to build reproducibly, mtimes of any files
created after the date of the latest debian/changelog entry
will be changed to that date.
---
 debian/rules | 4 
 1 file changed, 4 insertions(+)

diff --git a/debian/rules b/debian/rules
index b09c52c..45992d3 100755
--- a/debian/rules
+++ b/debian/rules
@@ -24,6 +24,8 @@ CFLAGS := $(shell dpkg-buildflags --get CFLAGS)
 CPPFLAGS := $(shell dpkg-buildflags --get CPPFLAGS)
 LDFLAGS := $(shell dpkg-buildflags --get LDFLAGS)
 
+BUILD_DATE := $(shell dpkg-parsechangelog | sed -n -e 's/^Date: //p')
+
 build: build-indep build-arch
 build-indep:
 
@@ -104,6 +106,8 @@ endif
 			debian/tmp/bin/tempfile \
 			debian/tmp/usr/bin/ischroot
 	dpkg-gencontrol -isp
+	find debian/tmp -depth -newermt '$(BUILD_DATE)' -print0 | \
+		xargs -0r touch --no-dereference --date='$(BUILD_DATE)'
 	dpkg --build debian/tmp ..
 
 define checkdir
-- 
2.1.3



signature.asc
Description: Digital signature

Bug#774036: Re: Bug#774036: linux-image-3.16.0-4-amd64: Untainted Kernel shows similar issue

2015-01-03 Thread Rainer Dorsch

Hi Emil,

I have only remote access to the system for the next few weeks and I feel 
somewhat uncomfortable to experiment with my self-compiled kernels on the 
system or changing networking configurations.

So please apologize that I may need 3-4 weeks to test that.

I assume you suggest to follow

http://kernel-handbook.alioth.debian.org/ch-common-tasks.html

to enable PM_TRACE_RTC and rebuild the kernel, correct?

Kind regards,
Rainer

On Tuesday 30 December 2014 12:40:53 Emil Goode wrote:
 Hello Rainer,
 
 On Tue, Dec 30, 2014 at 12:15:31AM +0100, Rainer Dorsch wrote:
  Hi Emil,
  
  Am Montag 29 Dezember 2014, 14:02:55 schrieb Emil Goode:
   Hello Rainer,
   
   The below procedure would give more information:
   
   Add the following line to the top of the file
   /usr/lib/pm-utils/pm-functions.
   
   export PM_DEBUG=true
   
   Then suspend with:
   
   echo 1  /sys/power/pm_trace
   echo mem  /sys/power/state
  
  HmmI do not have a pm_trace
 
 Ok, that is because PM_TRACE_RTC needs to be enabled in the kernel config.
 
 Please be aware that when using pm_trace it will mess with your machine's
 real-time clock.
 
  There is a similar bug report already for an older kernel, but that seems
  to be fixed (?)
  
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638264
 
 The iwlagn module is for intel wireless and I believe you are using
 broadcom.
   Post dmesg and the contents of /var/log/pm-suspend.log.
   
   Have you tried disabling the mac80211 module?
  
  Can you tell how I unload a module for suspend or if
  
  http://superuser.com/questions/620201/how-to-force-ubuntu-debian-mint-to-u
  nload-modules-at-suspend-to-disk also applies to systemd?
 
 I think you can temporarily blacklist modules as described here:
 
 https://wiki.debian.org/KernelModuleBlacklisting
 
 I would also try the latest upstream kernel, this might have been fixed.
 
 Best regards,
 
 Emil Goode

-- 
Rainer Dorsch
http://bokomoko.de/


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

Bug#418519: Reason for having raw disk as physical volume

2015-01-03 Thread Lennart Sorensen

On Sat, Jan 03, 2015 at 09:48:14AM +0200, Vincas Dargis wrote:
 With HW Raid, it's exactly what we intended to do: create very small
 volume (for Linux point of view it's just /dev/sda) to be as boot
 disk, containing only boot loader (and maybe /boot), which should
 not be ever resized or snapshoted or whatever, no need for LVM.
 
 Second volume (/dev/sdb) would be raw PV containing / and other
 LVM volumes. But I can't implement it simply by using partman.

I would think that having a partition on sda flagged bootable might
be necesary at least on systems.  Many systems over the years have had
BIOS/firmware issues that insisted things had to look a certain way to
be bootable even if that wasn't officially a requirement.  After all
that's how microsoft OSs were always installed, so making assumptions
was often considered valid since it always worked when tested.

So certainly not required, but might be safer.

Also there has to be somewhere to install the bootloader, and blockmapping
into the filesystem is a very bad idea, so having some space set aside
for the boot loader is a good idea (which often ends up being the unused
space of the disk before the 1st partition when doing 1MB alignment of
partition starts).  With EFI you simply have a dedicated mandetory
partition to store the boot loader, but of course then you must also
have another partition for /boot in that case, since /boot has to be a
unix style filesystem, and the EFI boot partition has to be FAT (as far
as I know).

-- 
Len Sorensen


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

Bug#774502: mtpaint: lack of MIME-type informations in mtpaint.desktop

2015-01-03 Thread Mito

Package: mtpaint
Version: 3.40-1ubuntu1
Severity: normal

Dear Maintainer,

After installing mtPaint on my Xubuntu 14.04 system there was no 'quick'
way to open an image with mtPaint for example in the 'open with' menu.
I asked in the ubuntu-forums for help and they told me to add a line
in '/usr/share/applications/mtpaint.desktop' for MIME-type informations,
but I don't know what the program is able to open and/or where to look for it.
So I didn't solve the problem yet.

thanks for the program, anyway.

mito


-- System Information:
Debian Release: jessie/sid
  APT prefers trusty-updates
  APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 
'trusty'), (100, 'trusty-backports')
Architecture: i386 (i686)

Kernel: Linux 3.13.0-43-generic (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages mtpaint depends on:
ii  libc6   2.19-0ubuntu6.4
ii  libfreetype62.5.2-1ubuntu2.2
ii  libgdk-pixbuf2.0-0  2.30.7-0ubuntu1
ii  libgif4 4.1.6-11
ii  libglib2.0-02.40.2-0ubuntu1
ii  libgtk2.0-0 2.24.23-0ubuntu1.1
ii  libjpeg88c-2ubuntu8
ii  libpango1.0-0   1.36.3-1ubuntu1.1
ii  libpng12-0  1.2.50-1ubuntu2
ii  libtiff54.0.3-7ubuntu0.1
ii  libx11-62:1.6.2-1ubuntu2
ii  zlib1g  1:1.2.8.dfsg-1ubuntu1

mtpaint recommends no packages.

mtpaint 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#774412: Re: Bug#774412: systemd unable to boot with fixed mount points

2015-01-03 Thread Michael Biebl

Am 03.01.2015 um 15:59 schrieb Andrei POPESCU:
 Control: severity -1 minor
 Control: retitle -1 systemd-fsck tries to check unavailable filesystems even 
 if 0 in fstab passno field
 
 On Sb, 03 ian 15, 13:42:34, HJ wrote:
 Does systemd still try to fsck the non-available filesystem?

 no ;)
 
 Ok, since systemd is failing the boot by design if a filesystem not 
 marked 'nofail' or 'noauto' is missing I'll re-purpose this bug to be 
 about the additional delay due to systemd-fsck trying to check a 
 filesystem which is not available, despite it being marked to not be 
 checked in fstab.
 
 However, since fsck will be skipped in the normal case I'll downgrade to 
 'minor'.

Are you sure, that systemd does actually run fsck for the device?

Looking back at HJs first message, he mentioned:

 at first fsck trieds to check this drive even if it does not exist and is
 disabled, this already takes ~1:30 minutes and I'm unable to stop it(A start
 job is running...)

We would need the full log message here, but to me, that rather looks
like systemd waits for the /dev/sdc1 device to appear and enters rescue
mode after the (internal) 90s timeout.

HJ, if you boot again with the faulty fstab, which drops you into the
emergency shell, can you check if you have active
systemd@device-name.service unit for /dev/sdc1 (it's most likely named
systemd@dev-sdc1.service).






-- 
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#774466: delete cdn.debian.net from mirrors list

2015-01-03 Thread Miguel Figueiredo


diff --git a/Mirrors.masterlist b/Mirrors.masterlist
index bd8718a..92bd6e4 100644
--- a/Mirrors.masterlist
+++ b/Mirrors.masterlist
@@ -54,17 +54,6 @@ Comment: HTTP redirector that uses the geo and 
network location of the

  few other things. Details: http://http.debian.net
 Sponsor: http://http.debian.net/

-Site: cdn.debian.net
-Type: GeoDNS
-Archive-architecture: amd64 arm64 armel armhf hurd-i386 i386 ia64 
kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc ppc64el s390 s390x sparc

-Archive-http: /debian/
-Archive-upstream: ftp-master.debian.org
-IPv6: no
-Maintainer: Yasuhiro Araki a...@debian.org, Kenshi Muto km...@debian.org
-Comment: Automatically selects geographically close, load balanced mirror
- from a pool of mirrors that are tested frequently to ensure they are
- healthy. Details: https://wiki.debian.org/DebianGeoMirror
-
 Site: ftp.us.debian.org
 Alias: http.us.debian.org
 Includes: mirrors.kernel.org debian.osuosl.org debian.csail.mit.edu 
mirror.mycre.ws debian.gtisc.gatech.edu



--
Melhores cumprimentos/Best regards,

Miguel Figueiredo


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

Bug#774503: RFS: mgrs/0.0~20131209-80d5465-1~exp1 [ITP]

2015-01-03 Thread Bas Couwenberg

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package mgrs

 Package name: mgrs
 Version : 0.0~20131209-80d5465-1~exp1
 Upstream Author : MetaCRS Developers meta...@lists.osgeo.org
 URL : https://github.com/proj4js/mgrs
 License : Expat
 Section : science

It builds those binary packages:

 libjs-mgrs - Javascript for converting between WGS84 lat/lng and MGRS 
coordinates
 node-mgrs  - Utility for converting between WGS84 lat/lng and MGRS coordinates

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

http://mentors.debian.net/package/mgrs


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

  dget -x 
http://mentors.debian.net/debian/pool/main/m/mgrs/mgrs_0.0~20131209-80d5465-1~exp1.dsc

More information about mgrs can be obtained from 
https://github.com/proj4js/mgrs.

Changes since the last upload:

  * Initial release (Closes: #774458)


Regards,
 Bas Couwenberg


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

Bug#773253: jenkins: please add script to detect dpkg trigger cycles

2015-01-03 Thread Holger Levsen

Hi josch,

On Donnerstag, 1. Januar 2015, Johannes Schauer wrote:
 that would be great, because then I could test everything locally and only
 submit you one commit that makes everything work instead of going back and
 forth :)

the schroot setup is defined in dpkg.yaml... it should be better explained in 
README one day...
 
 Which is the part where the jessie chroot is created? Casually looking
 through files in job-cfg which use chroot-run.sh I cannot see where to add
 additional packages to the chroot.

from dpkg.yaml:

   my_shell: '/srv/jenkins/bin/schroot-create.sh dpkg-jessie jessie 
python apt-file dose-extra'

- create a schroot called jenkins-dpkg-jessie, base it on jessie and install 
the additional packages python, apt-file and dose-extra.
 

So now https://jenkins.debian.net/view/d-
i_misc/job/dpkg_sid_find_trigger_cycles/19/console has this issue:

curl: (5) Could not resolve proxy: $http_proxy

I'll look into this now...


cheers,
Holger


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

Bug#774505: bouncy: Window is 4:3 on 16:9 display and not fullscreen or windowed

2015-01-03 Thread gaffa

Package: bouncy
Version: 0.6.20071104-4
Severity: normal

When I start bouncy it is displayed as a fullscreen 4:3 view at the right side
of my 16:9 screen.

I edited game.py:16 from:
screen = pygame.display.set_mode(viewport, OPENGL | DOUBLEBUF) # | FULLSCREEN
to
screen = pygame.display.set_mode(viewport, OPENGL | DOUBLEBUF | FULLSCREEN)

That gave me a normal fullscreen view. I don't know why the FULLSCREEN option
was disabled. It doesn't seem to be a decorated window controlled by the
window manager, before the change.


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

Bug#773085: Regression in escaped url handling with patch applied for #773085

2015-01-03 Thread Vincent Bernat

 ❦  3 janvier 2015 17:31 +0100, Salvatore Bonaccorso car...@debian.org :

 Steps for reproducing the issue:

 $ xdg-mime default chromium.desktop x-scheme-handler/http
 $ xdg-mime query default x-scheme-handler/http
 chromium.desktop
 $ DE='generic' XDG_CURRENT_DESKTOP= xdg-open 
 'http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=xdg-utilsrepeatmerged=no'

 Without the patch applied, the page correctly is opened. If doing so
 the same with the applied patch chromium get passed as argument
 '$sed_escaped_url', and xdg-open executes /usr/bin/chromium
 '$sed_escaped_url'.

I don't understand how the proposed patch would work. $arg_one (or
$sed_escaped_url) is singly quoted and therefore cannot be
expanded.

If I modify the first chunk of the patch, it works as expected:

arguments_exec=$(echo $arguments | sed -e 
's*%[fFuU]*'$sed_escaped_url'*g')

(this is not like the initial chunk, I don't quote the argument.

xdg-open 'http://www.example.com/$(xterm)' works as expected.

However, the whole stuff is quite fragile. I can't say for sure if
spaces would do something good or bad, but a star would not work. Here
is an improved version which is easier to understand.

#+begin_src sh
file=/usr/share/applications/chromium.desktop

# Safe quoting. We just enclose into single quotes the given argument
# and escape single quotes.
quote() {
printf %s\\n $1 | sed s/'/'''/g;1s/^/'/;\$s/\$/'/
}

arg=$1
set -- $(sed -n 's/^Exec\(\[[^]]*\]\)\{0,1\}=//p' $file)
cmd=$(which $1 2 /dev/null)
[ -n $cmd ] || exit 2
shift
args=
while [ $# -gt 0 ]; do
case $1 in
%[fFuU])
args=$args $(quote $arg)
;;
*)
args=$args $(quote $1)
;;
esac
shift
done
$cmd $args
#+end_src

The set is just here to let the shell do the quoting. If no
replacement was needed, we could just $cmd $@ after the first shift
and be done. Unfortunately, with just a POSIX shell, the replacement of
the positional argument is difficult. Instead, we build the list of args
by quoting correctly each of them. Then, it can be executed.

Using bash would be more straightforward since we could stack our
arguments into an array and modify this array to substitute %U and the
like.
-- 
The surest protection against temptation is cowardice.
-- Mark Twain


signature.asc
Description: PGP signature

Bug#769862: libav: target option broken - leads to wrong output files

Control: forwarded -1 https://bugzilla.libav.org/show_bug.cgi?id=468

On 2015-01-03 19:40:46, Sebastian Ramacher wrote:
 Control: found -1 6:11-1
 Control: notfound -1 11
 Control: tags -1 moreinfo
 
 On 2014-11-17 08:19:02, Vincent Pinon wrote:
  Source: libav
  Version: 11
  Severity: normal
  Tags: upstream
  
  This bug was reported upstream by someone else 1.5 year back,
  with note on how to simply fix it, but the problem persists.
 
 Do you have a link to the issue reported upstream?

I suspect this is https://bugzilla.libav.org/show_bug.cgi?id=468.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature

Bug#738760: libav: Add proper raspberry pi CPU detection

2015-01-03 Thread peter green


Sebastian Ramacher wrote:

there was a request to change the handling of the Raspberry Pi in the
libav package. Could you please explain the changes applied to the
Raspbian version? 
In raspbian we have a checker that runs after all our autobuilds (and I 
manually run a similar check when I do manual builds) that looks for 
files tagged as armv7 (note: it seems using neon compiler options causes 
files to be tagged as armv7 even if the CPU options aren't changed) and 
prevents the autobuilder from uploading them.


In general i've been adopting the principle that having armv7 code in 
raspbian is at best a pointless waste of space (if the code in question 
is correctly guarded behind runtime CPU detection) and at worst a 
serious problem (if it isn't). Therefore I have been responding to cases 
like this by simply disabling the armv7/neon code. The raspbian libav 
package got this treatment.


It's possible that I dodn't selct the best combination of flags, I'm no 
libav expert.


I have not tested whether an unodified debian libav package built in a 
raspbian chroot actually works on the Pi or not.



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

Bug#762492: libav-tools: Audio/video encoding produces an audio encoding error with openshot/kdenlive

Control: reassign -1 mlt 0.9.2-2
Control: forcemerge 761593 -1

On 2014-09-22 13:47:00, Charles Laws wrote:
 Package: libav-tools
 Version: 6:11-1
 Severity: important
 
 Dear Maintainer,
 
 My last video project was about 7 weeks ago. Sometime between then and now, I 
 lost the ability to export audio. I have tried a handful of different 
 encoding combinations with 
 both openshot and kdenlive. Running openshot --debug and doing an export 
 gives me this:
 
 [libx264 @ 0x7fac29e0] [Eval @ 0x7fac39ffa500] Undefined constant or
 missing '(' in 'dct8x8'
 [libx264 @ 0x7fac29e0] Unable to parse option value dct8x8
 [aac @ 0x7fac002caec0] [Eval @ 0x7fac39ffa4b0] Undefined constant or
 missing '(' in 'dct8x8'
 [aac @ 0x7fac002caec0] Unable to parse option value dct8x8
 [mp4 @ 0x7fac24a0] Using AVStream.codec.time_base as a timebase hint 
 to the muxer is deprecated. Set AVStream.time_base instead.
 on_frmExportVideo_destroy
 [consumer avformat] error writing flushed audio frame
 
 This bug is also #761518 for Openshot, listed here: 
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761518

This is #761593 in libmlt6. Reassigning in merging.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature

Bug#774521: sbuild-createchroot(8): default suffix is -sbuild, not, -chroot

2015-01-03 Thread Christian Kastner

Source: sbuild
Version: 0.65.0-1
Severity: minor
Tags: patch

Hi,

The man page says that the default for --chroot-suffix is -chroot,
however, it's -sbuild.

Patch against git master attached.

Regards,
Christian
From f251a823f42ca43191cfa7a0c70ee8123e893b13 Mon Sep 17 00:00:00 2001
From: Christian Kastner deb...@kvr.at
Date: Sat, 3 Jan 2015 23:18:09 +0100
Subject: [PATCH] sbuild-createchroot(8): default suffix is -sbuild, not
 -chroot

---
 man/sbuild-createchroot.8.in | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/man/sbuild-createchroot.8.in b/man/sbuild-createchroot.8.in
index e04628f..321a2da 100644
--- a/man/sbuild-createchroot.8.in
+++ b/man/sbuild-createchroot.8.in
@@ -91,7 +91,7 @@ Set the target architecture.  This may be used if dpkg is not already
 installed.  See also \fI\-\-foreign\fP, below.
 .TP
 .BR \-\-chroot-suffix=\fIsuffix\fP
-Add a custom suffix to the chroot name. Defaults to '\-schroot'.
+Add a custom suffix to the chroot name. Defaults to '\-sbuild'.
 .TP
 .BR \-\-foreign
 Only perform the initial unpack phase of bootstrapping.  This is required if
-- 
2.1.4

Bug#771037: [vlc] intermittent green overlay on video with audio muting when playing youtube videos

2015-01-03 Thread Rémi Denis-Courmont

tags 771037 + moreinfo
thanks

Le mardi 25 novembre 2014, 23:57:41 Andrew Kane a écrit :
 When invoking vlc via terminal with command line:
 vlc - https://www.youtube.com/watch?v=6hvcjxI3Wa4
 
 ...the phenomenon does not occur. Maybe the problem is with one or
 more of the options which apparently are specified when the program is
 started from the launcher or menu, but I don't know how to determine
 which.

hexdump -C /proc/$PID/cmdline

 Any guidance will be appreciated :^)

I would rather suspect a bug in your VDPAU driver than in VLC's command 
line...

-- 
Rémi


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

Bug#774519: Changelog entries for netscript-2.4 6 5.4.7 and 5.4.8

2015-01-03 Thread Matt Grant

Hi!

Forgot to copy these in:

netscript-2.4 (5.4.8) unstable; urgency=medium

  * Remove sysvint/inserv support for package. (Closes: #771871)
Revert totally removing ifupdown emulation/Provides as this breaks
too
many things.  This just removes the dependency loop in /etc/init.d
files 
which is unfixable.

 -- Matthew Grant m...@mattgrant.net.nz  Tue, 23 Dec 2014 17:50:04
+1300

netscript-2.4 (5.4.7) unstable; urgency=medium

  * Convert '-' in interface names to '_' (Closes: #773772)

 -- Matthew Grant m...@mattgrant.net.nz  Mon, 22 Dec 2014 21:10:30
+1300


Regards,

-- 
Matt Grant,  Debian and Linux Systems Administration and Consulting
Mobile: 021 0267 0578
Email: m...@mattgrant.net.nz


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

Bug#774453: zoo: directory traversal

2015-01-03 Thread Jakub Wilk


* Jakub Wilk jw...@debian.org, 2015-01-02, 23:16:
Either the fix for CVE-2005-2349 (bug #309594) wasn't complete, or it 
bit-rotted, because Zoo is still susceptible to directory traversal:


To clarify, #309594 discussed only relative path traversal (via .. 
sequences), but AFAICS the patch[0] tries to address also absolute path 
traversal.


And, despite the patch, Zoo is currently susceptible to relative 
directory traversal, too:


$ zoo x traversal-relative.zoo 
Zoo:  ../moo -- skipped


$ ls -l ../moo 
-rw-r--r-- 1 jwilk users 4 Jan  5  2015 ../moo



[0] 
https://sources.debian.net/src/zoo/2.10-27/debian/patches/02-traversal-directory.patch/

--
Jakub Wilk


traversal-relative.zoo
Description: Binary data

Bug#514464: ping? [Was: caps lock led does not show up]

2015-01-03 Thread Samuel Thibault

Hello,

Lukasz Stelmach, le Sat 03 Jan 2015 22:34:43 +0100, a écrit :
 Any news? Debian 7.7 is still affected.

Yes, I know.  This is still being discussed upstream on linux-kernel,
see the INPUT: Route keyboard LEDs through the generic LEDs layer
thread.

(and please keep the subject of the bug report in replies, I don't know
anybody who knows bug # by heart :))

Samuel


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

Bug#765969: (no subject)

2015-01-03 Thread Rémi Denis-Courmont

tags 765969 + fixed-upstream
found 765969 2.2.0~rc2-1
thanks

VLC 2.2.0-rc2-89-gfebaed2 works around this bug.


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

Bug#774489: xombrero: file:/// URL in favorites and history are not clickable

2015-01-03 Thread Pierre-Etienne Meunier

Package: xombrero
Version: 2:1.6.3-1
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?

Browse to a local page, for instance file:///usr/share/doc/mpd/user-manual.html.
Then add the page to the favorites with :favadd

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

(explained above)

   * What was the outcome of this action?

The page is listed in the favorites, as opened with command :favorites, but 
clicking on it does not open it. Clicking on other favorites works well, though.

   * What outcome did you expect instead?

I was expecting to be able to open it directly by clicking on it from the 
favorites pages, as I can do for other links, for instance http:// ones.


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

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

Versions of packages xombrero depends on:
ii  libbsd0 0.7.0-2
ii  libc6   2.19-13
ii  libgdk-pixbuf2.0-0  2.31.1-2+b1
ii  libglib2.0-02.42.1-1
ii  libgnutls-deb0-28   3.3.8-5
ii  libgtk-3-0  3.14.5-1
ii  libjavascriptcoregtk-3.0-0  2.4.7-3
ii  libpango-1.0-0  1.36.8-3
ii  libsoup2.4-12.48.0-1
ii  libwebkitgtk-3.0-0  2.4.7-3

xombrero recommends no packages.

xombrero 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#744932: debhelper: document compat level at which debug packages use build-id debug symbols

Control: tags -1 moreinfo

On Wed, 16 Apr 2014 09:34:44 -0300 Felipe Sateler fsate...@debian.org
wrote:
 Package: debhelper
 Version: 9.20140228
 Severity: normal
 
 dh_strip on compat levels 7 and below stores debug information on
 /usr/lib/debug/$fullpath, but on compat levels 8 and above it stores
 them on /usr/lib/debug/.build-id/${build-id}.
 
 This is not documented neither in debhelper(7) nor in dh_strip(1). I
 think it should be documented in both.
 
 Saludos
 
 [...]

Hi,

This is already documented in man 7 debhelper:



   v9  This is the recommended mode of operation.

   Changes from v8 are:
[...]

   -  dh_strip puts separated debug symbols in a location based
  on their build-id.


Though, I am a bit surprised to hear that you believe it happens at
compat 8 already.  Codewise and documentation wise, it seems to start at
compat 9.

~Niels


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

Bug#774412: Re: Bug#774412: systemd unable to boot with fixed mount points

2015-01-03 Thread Andrei POPESCU

On Vi, 02 ian 15, 18:58:45, HJ wrote:
 If you add 'nofail' to fstab does systemd still try to fsck the drive?
 
 thx a lot this works,

I assume this to mean that your system boots. Does systemd still try to 
fsck the non-available filesystem?

 but somebody should update the fstab manual in that
 case

fstab(5) has:

nofail do not report errors for this device if it does not exist.

It doesn't however say anything about (and probably shouldn't) how a 
given subsystem should treat such errors.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Bug#774443: unblock: reportbug/6.6.2

2015-01-03 Thread Ivo De Decker

Control: tags -1 moreinfo

Hi,

On Fri, Jan 02, 2015 at 08:59:16PM +, Sandro Tosi wrote:
 Please unblock package reportbug

 -if online:
 -if tag == 'wheezy-pu':
 -version = checkversions.get_versions_available(package, 
 timeout, 'wheezy').values()[0]
 -elif tag == 'squeeze-pu':
 -version = checkversions.get_versions_available(package, 
 timeout, 'squeeze').values()[0]
 +if online and tag.endswith('-pu'):
 +version = checkversions.get_versions_available(package, timeout, 
 tag[:-3]).values()[0]

This doesn't actually seem to be correct. The url that gets checked is this
one:

http://qa.debian.org/madison.php?package=reportbugtext=ons=j,e,s,s,i,ea=source,all,amd64

This return all versions, and a random one is picked.

It seems to work like this:

version = checkversions.get_versions_available(package, timeout, 
(tag[:-3],)).values()[0]

This isn't actually a regression (it doesn't work in the current version), but
it might be nice to fix it.

Cheers,

Ivo


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

Bug#739971: dh_link: support .links being executable

Control: tags -1 moreinfo

On Mon, 24 Feb 2014 14:30:52 +0100 Daniel Baumann
daniel.baum...@progress-technologies.net wrote:
 Package: debhelper
 Severity: list
 
 in newer debhelper versions, install files when marked executable, are
 processed in the way that their ouput constitutes the content of a
 traditional debhelper install file.
 
 please also support doing the same for links files, so that links can be
 created conditionally to match the install files.
 
 [...]

Hi,

AFAICT, this has already been implemented from the beginning of
executable debhelper files.  Can you provide an example of where it does
not work under compat 9 with an executable debian/(PACKAGE.)links file?

~Niels


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

Bug#737388: debhelper: update dh_installemacsen postinst etc. scripts to newest emacs policy

On Sun, 2 Feb 2014 11:17:52 + Julian Gilbey j...@debian.org wrote:
 Package: debhelper
 Version: 9.20131227
 
 The emacs policy has recently changed; the 2.0.7 version of
 emacsen-common has a slightly different set of snippets to place in
 the maintainer scripts (section 5 of the policy).
 
 Please could you update debhelper to reflect this change?
 
 Thanks!
 
Julian
 
 

Hi Julian,

Perhaps I could convince you to provide a patch for dh_installemacs and
the related files in autoscripts?  Namely, I am not entirely sure what
you want to have changed.

~Niels


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

Bug#774477: [Vmdebootstrap-devel] Bug#774477: vmdebootstrap: references cdn.debian.net, which is deprecated

2015-01-03 Thread Neil Williams

severity 774477 wishlist
retitle 774477 update manpage to current mirror default
found 774477 0.5-1
tag 774477 pending
thanks

On Sat, 03 Jan 2015 12:59:14 +0800
Paul Wise p...@debian.org wrote:

 Source: vmdebootstrap
 Severity: important
 
 cdn.debian.net is in the process of being deprecated, orphaned and
 transitioned to http.debian.net, please remove it from vmdebootstrap.

Already done in code:

http://sources.debian.net/src/vmdebootstrap/0.5-1/vmdebootstrap/#L63

The manpage lists it but that is a wishlist bug. The --help output of
vmdebootstrap already references http.

  --mirror=URL  use MIRROR as package source
(http://http.debian.net/debian/)


-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



pgpkuxKK6QfYU.pgp
Description: OpenPGP digital signature

Bug#774476: multistrap: references cdn.debian.net, which is deprecated

2015-01-03 Thread Neil Williams

severity 774476 minor
retitle 774476 switch example mirror in usage information
found 774476 2.2.0
tag 774476 + pending
thanks

On Sat, 03 Jan 2015 12:58:39 +0800
Paul Wise p...@debian.org wrote:

 Source: multistrap
 Severity: important
 
 cdn.debian.net is in the process of being deprecated, orphaned and
 transitioned to http.debian.net, please remove it from multistrap.

It's only mentioned in the example mirror of the usage information,
multistrap has no default mirror. Lowering severity.

-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



pgpsqzxjoKnvI.pgp
Description: OpenPGP digital signature

Bug#771857: caff: Please support GnuPG 2.1

2015-01-03 Thread Guilhem Moulin

Following http://lists.gnupg.org/pipermail/gnupg-devel/2015-January/029301.html
caff's $CONFIG{'secret-keyring'} has been deprecated, and the symlinks
are automatically created when the secret keyrings are not present.

-- 
Guilhem.


signature.asc
Description: Digital signature

Bug#774361: how to play?

2015-01-03 Thread Tomas Pospisek


tags 774361 - moreinfo + patch
severity 774361 wishlist

thanks

Hello in the new year Markus,

I've should have also read the accompanying README.lgeneral.gz, then I 
would have known. However I suggest to make it easier to users to just 
play. Imagine the following situation:


It's christmas holidays and I'm bored. I fire up aptitude and install some 
games at random. Then I start them from the Applications menu.


Once the game is started I think the user will intuitively start clicking 
around, not least around the menu. But unless he first selects a scenario 
*and then also a campaign*, he will not be able to play.


I think ideally the game should give the users a hint what to do next.

So upon loading the scenario, the text that is displayed should tell the 
user and now select a campaign from the menu.


But all of this is material for upstream.

What the Debian package could do is to make it easier for the Debian user. 
I think an advanced user will at least have a look at the README.Debian, 
and that's where you could give him/her the necessary hint. The same hint 
should also go into the manpage IMHO...


So here's my proposed patch for Debian.README (the same should go into 
'man lgeneral').


===
--- README.Debian.orig  2015-01-03 14:04:00.515754439 +0100
+++ README.Debian   2015-01-03 14:06:36.755751024 +0100
@@ -7,6 +7,10 @@
 the fun may vary. Playtesting, feedback and suggestions for improvements are
 most welcome.

+To start a game, you need to go to the menu and first select a scenario and 
then
+a campaign. Have a look at the provided README.lgeneral.gz, chapter 5. 
Interface
+for instructions on how to play the game.
+
 You can gather more information about LGeneral for Debian at
 http://wiki.debian.org/Games/LGeneral.
===

Thanks,
*t

On Thu, 1 Jan 2015, Markus Koschany wrote:


Control: tags -1 moreinfo

Hi and happy new year,

On Thu, 01. Jan 15:13 Tomas Pospisek tpo_...@sourcepole.ch wrote:

Package: lgeneral
Version: 1.2.3+dfsg-3
Severity: normal

How can I actually play the game?

1. I start lgeneral
2. I click C for campain, and select PG
3. a text explains what the aim is I click on that and
   the text disappears
4. I'm back to the map
5. what's the next step?
   - clicking anywhere doesn't seem to have any effect
   - right-click brings up the menu
   - any key-press on my keyboard doesn't seem to have
 any effect either
   - README.Debian does mention any controls, however it
 point to the LGeneral Debian Wiki
   - in the Debian Wiki there's no mention of controls
 either however it points to the LGeneral Web Page at SF
   - on the LGeneral Web Page there's no mentions of
 controls either

6. now what?


That sounds more like a support request and not like a bug report.

In short: You are supposed to click on S and start the scenarios except
you own a copy of the original Panzer General game yourself. In the
latter case you could then use game-data-packager to create a Debian package 
for the original
campaign. I have explained this in README.Debian. The campaign is
non-distributable for Debian despite the fact that the community claims
Panzer General was abandonware and there is even a commercial game
which reverse-engineered the PG engine but still I am not aware of a
free license that would allow it.

Let's start with the campaign (C) and the scenarios (S). If you install
lgeneral, you can only play the free scenarios provided by the
lgeneral-data package. You have to click on (S) and choose one of the
WWI scenarios from the kukgen directory. You can always bring up the
menu by right-clicking. After you have selected a scenario, the game
will start with the selected map. The rest is moving your units around
and attack other units. Pretty standard turn-based strategy.

I wonder how I am supposed to fix this bug. More information are
appreciated.

Regards,

Markus






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

Bug#774496: ncurses: please make ncurses build reproducibly

Source: ncurses
Version: 5.9+20140913-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps

Hi!

While working on the “reproducible builds” effort [1], we have noticed
that ncurses could not be built reproducibly.

The attached patch will add calls to strip-nondeterminism on static
libraries. Once applied, the package can be built reproducibly with our
current experimental framework.

I've initially tried to run `ar` in deterministic mode by passing
ARFLAGS=Dcrv. Unfortunately, `ranlib` is called after `ar` and there
doesn't seem to be a way to pass the `-D` flag to it, and so it will
write a timestamp in the newly created index.

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

-- 
Lunar.''`. 
lu...@debian.org: :Ⓐ  :  # apt-get install anarchism
`. `'` 
  `-   
From 914efd4f2ca07ada794bc70e6ecc8eb39725303c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=A9r=C3=A9my=20Bobbio?= lu...@debian.org
Date: Sat, 3 Jan 2015 13:54:20 +0100
Subject: [PATCH] Call strip-nondeterminism on static libraries

Static libraries will unfortunately contain timestamps, preventing the
package to be built reproducibly. strip-nondeterminism will take care
of normalizing the libraries.

Passing 'Dcvr' as ARFLAGS to configure is unfortunately not enough.
The build process also calls ranlib, and there doesn't seem to be
a way to give it the '-D' flag.
---
 debian/control | 1 +
 debian/rules   | 5 +
 2 files changed, 6 insertions(+)

diff --git a/debian/control b/debian/control
index 5c32f76..2cbbd67 100644
--- a/debian/control
+++ b/debian/control
@@ -9,6 +9,7 @@ Build-Depends: debhelper (= 8.1.3),
libgpm-dev [linux-any],
pkg-config,
autotools-dev,
+   strip-nondeterminism,
 Standards-Version: 3.9.5
 Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/ncurses.git
 Vcs-Git: git://anonscm.debian.org/collab-maint/ncurses.git
diff --git a/debian/rules b/debian/rules
index 1c0bc1a..924e7dd 100755
--- a/debian/rules
+++ b/debian/rules
@@ -344,6 +344,11 @@ install: build
 	dh_testroot
 	dh_prep
 
+	find $(objdir) $(objdir-static) $(objdir-32) $(objdir-64) \
+		$(wobjdir) $(wobjdir-static) $(wobjdir-32) \
+		$(objdir-debug) $(wobjdir-debug) -type f -name '*.a' -print0 | \
+		xargs -0r strip-nondeterminism --type ar
+
 	# Static debug libraries need _g suffix to avoid file clashes
 	set -e; \
 	for lib in $(objdir-debug)/lib/*.a; do \
-- 
2.1.4



signature.asc
Description: Digital signature

Bug#723931: src:libdist-zilla-plugin-requiresexternal-perl: FTBFS when verbose tests are enabled: Tests out of sequence.

2015-01-03 Thread Damyan Ivanov

-=| Damyan Ivanov, 03.01.2015 13:25:00 + |=-
 I tried to reproduce this today, and all tests passed. I've run 
 t/test.t (which was failing in 2013) a hundred times and it passed 
 100%.
 
 My guess is that the problem were in some of the build-dependencies, 
 and is now fixed there.
 
 Here's a list of build-dependencies and their versions back in 
 September 2013 and today, as reported by t/000-report-versions.t:
 
 Dependency  Failing Passing
 21 Sep 2013 03 Jan 2015
 === === ===
 Perl5.0180015.020001
 Carp1.291.3301
 Config  5.0180015.020001
 Dist::Zilla::File::InMemory 4.3000375.020
 Dist::Zilla::Role::FileGatherer 4.3000375.020
 Dist::Zilla::Role::MetaProvider 4.3000375.020
 Dist::Zilla::Role::Plugin   4.3000375.020
 Dist::Zilla::Role::TextTemplate 4.3000375.020
 English 1.061.09
 Env::Path   0.190.19
 ExtUtils::MakeMaker 6.666.98
 File::Find  1.231.27
 File::Temp  0.230.2304
 List::MoreUtils 0.330.33
 Modern::Perl1.20121103  1.20140107
 Moose   2.1005  2.1213
 MooseX::Has::Sugar  0.05070420  1.04
 MooseX::Types::Moose0.350.45
 Path::Class 0.320.35
 Scalar::Util1.271.38
 Test::DZil  4.3000375.020
 Test::More  0.981.001002
 Test::Most  0.310.34
 namespace::autoclean0.130.20
 strict  1.071.08
 utf81.101.13_01
 warnings1.181.23
 
 I haven't tried to downgrade some of the dependencies, seems like 
 too much work for little gain :)

Perhaps this is related to the similar #723930 in libdist-zilla-perl, 
which is fixed in version 5.20-1. Not sure if adding version to the 
build-dependency is worth it. The only use of that that I can imagine 
is backporting, but debhelper in wheezy/jessie will not have verbose 
testing enabled, so there should be no problem.


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

Bug#774204: please switch from cdn.debian.net to http.debian.net

2015-01-03 Thread Tomas Pospisek


Control: tags -1 + help

On Thu, 1 Jan 2015, Niels Thykier wrote:


On Tue, 30 Dec 2014 09:28:59 +0100 Tomas Pospisek
tpo_...@sourcepole.ch wrote:

Package: lxc
Version: 1:1.0.6-5
Severity: minor

Hello Daniel,

since http://cdn.debian.net will be discontinued [1] and upstream has
also switched to http://http.debian.net [2] I think it's better to
switch in Debian's lxc to the new URL now instead of running the risk of
shipping a broken lxc-create with jessie.

Thanks for maintaining lxc!
*t

[1] https://lists.debian.org/debian-devel/2014/12/msg00181.html
[2] https://github.com/lxc/lxc/blob/master/templates/lxc-debian.in#L36

[...]


This sounds like a reasonable thing to change for Jessie - especially if
the default lxc setup is broken with it.  In this case, please upgrade
it to an RC bug (e.g. grave).  That said...

@Thomas, I am a bit surprised to hear that cdn.d.n stopped working
entirely?  As I understand the discontinuation mail, it should simply
become a DNS alias for http.debian.net, so I would expect it to just
work(tm).   Could you have hit a broken / out-of-sync mirror?  Do the
problem persist even now when using cdn.debian.net?


What you are speculating could quite possibly be true, however it is 
for me currently quite hard to verify, due to my ISP (sunrise24) enforcing 
traffic caps, which reduce my connection to a unworkable trickle after a 
few lxc-creates. I might be able to test your hypothesis from work in 
a few days.


I've added the help tag to this bug report, so if anybody can have a 
look into this before me, then please do so.


Thanks
*t


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

Bug#714546: #723930: libdist-zilla-perl: FTBFS with verbose tests

2015-01-03 Thread Damyan Ivanov

Version: 5.020-1

-=| gregor herrmann, 16.02.2014 16:28:18 +0100 |=-
 # when run from d/rules with TEST_VERBOSE=1 not when run individually and 
 manually with prove
 found 723930 5.013-1

-=| Damyan Ivanov, 21.09.2013 14:22:58 +0300 |=-
 Package: src:libdist-zilla-perl
 Version: 4.300037-1
 Severity: important
 User: debian-p...@lists.debian.org
 Usertags: dh-verbose-perl-tests
 
 bdist-zilla-perl fails to build when tests are run with TEST_VERBOSE=1, e.g. 
 when -v is given to prove or verbose perl module testing patch from  #714546 
 is 
 applied to debhelper:
 
 Test Summary Report
 ---
 t/plugins/testrelease.t (Wstat: 0 Tests: 5 Failed: 3)
   Failed tests:  2-3, 3
   Parse errors: Tests out of sequence.  Found (1) but expected (2)
 Plan (1..1) must be at the beginning or end of the TAP output
 Tests out of sequence.  Found (2) but expected (4)
 Tests out of sequence.  Found (3) but expected (5)
 More than one plan found in TAP output
 Displayed the first 5 of 6 TAP syntax errors.
 Re-run prove with the -p option to see them all.
 t/tester.t  (Wstat: 0 Tests: 6 Failed: 2)
   Failed tests:  4-5
   Parse errors: Tests out of sequence.  Found (1) but expected (4)
 Plan (1..1) must be at the beginning or end of the TAP output
 Tests out of sequence.  Found (4) but expected (6)
 More than one plan found in TAP output
 Bad plan.  You planned 1 tests but ran 6.
 Files=41, Tests=565, 68 wallclock secs ( 0.15 usr  0.05 sys + 64.05 cusr  
 3.68 csys = 67.93 CPU)
 Result: FAIL
 Failed 2/41 test programs. 5/565 subtests failed.

-=| gregor herrmann, 21.09.2013 19:52:33 +0200 |=-
 Control: tag -1 + confirmed upstream
 Control: found -1 4.300039-1
 
 Same here, and still the same with 4.300039-1.
  
 Cheers,
 gregor, who wished that dpt forward-bug would support github ...

It does now :))

I tested this today with version 5.020-1 and all tests passed. Closing 
the bug, which is the last blocker for verbose perl module testing in 
debhelper (#714546) \o/


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

Bug#774497: no sound on macmini G4 on wheezy

2015-01-03 Thread Mathieu Malaterre

Package: debian-installer
Severity: important

[I am not familiar with how d-i works, so I reported the bug to d-i
package directly, feel free to re-assign if needed]

This is an attempt to fix an old bug with d-i on Mac Mini G4.
debian-installer should not blacklist snd_aoa, since it prevent user
from having sound working.

[...]
$ cat /etc/modprobe.d/blacklist.local.conf
# Local module settings
# Created by the Debian installer

blacklist snd-aoa-codec-tas
blacklist snd-aoa-fabric-layout
blacklist snd-aoa-i2sbus
blacklist snd-aoa-soundbus
blacklist snd-aoa
[...]

Ref:
https://lists.debian.org/debian-powerpc/2012/09/msg1.html


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

Bug#774498: base-files: please make the build reproducible

Source: base-files
Version: 8
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps

Hi!

While working on the “reproducible builds” effort [1], we have noticed
that base-files could not be built reproducibly.

The attached patch will stop recording the current time in gzip headers,
and adjust the files mtimes before building the binary package. With
these changes, base-files can be built reproducibly with our current
experimental framework.

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

-- 
Lunar.''`. 
lu...@debian.org: :Ⓐ  :  # apt-get install anarchism
`. `'` 
  `-   


signature.asc
Description: Digital signature

Bug#774493: wheezy-jessie: trigger loop gconf2 - initramfs-tools

Control: tags -1 confirmed

On Sat, 03 Jan 2015 14:11:05 +0100 Stefano Zacchiroli z...@debian.org
wrote:
 Package: upgrade-reports
 Severity: serious
 
 Heya, I've just upgraded a family laptop from wheezy to jessie. The general
 experience has been very good and quick, with no noticeable breakages. The 
 only
 problem is that the first apt-get dist-upgrade (after an apt-get upgrade,
 as recommended by the release notes) failed due to a trigger loop. Here are 
 the
 details (messages translated to English by hand, as the upgraded laptop had an
 Italian locale) :
 
   configuring libdevmapper1.02.1:amd64 (2:1.02.90-2)
   trigger loop detected
 potentially responsible packages:
   gconf2 - initramfs-tools
 awaiting triggers that might be non resolvable
   libc-bin: ldconfig
   initramfs-tools: update-initramfs
   gconf2: /usr/share/gconf/schemas
   dpkg: error while processing libc-bin (--configure):
 trigger loop, giving up
 
 (If needed, I have a picture of the tty console on my phone, which I can
 provide.)
 
 After a few dpkg --configure --pending / apt-get -f install the problem
 went away and I managed to succesfully complete apt-get dist-upgrade.
 
 Cheers.
 
 [...]

Seems to be #771730, so it should disappear once the new dpkg migrates.
 Would be possible for you to re-try the upgrade where you upgrade into
the dpkg from sid instead of the Jessie version?

~Niels


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

Bug#774493: wheezy-jessie: trigger loop gconf2 - initramfs-tools

2015-01-03 Thread Stefano Zacchiroli

On Sat, Jan 03, 2015 at 02:24:43PM +0100, Niels Thykier wrote:
 Seems to be #771730, so it should disappear once the new dpkg migrates.

Thanks. I've looked into the bug reports of the mentioned packages for
duplicates, but didn't look into dpkg itself.

  Would be possible for you to re-try the upgrade where you upgrade into
 the dpkg from sid instead of the Jessie version?

Unfortunately not :-/, as the laptop has been upgraded now, and I don't
have handy another laptop with a similar/identical configuration.

Cheers.
-- 
Stefano Zacchiroli  . . . . . . .  z...@upsilon.cc . . . . o . . . o . o
Maître de conférences . . . . . http://upsilon.cc/zack . . . o . . . o o
Former Debian Project Leader  . . @zack on identi.ca . . o o o . . . o .
« the first rule of tautology club is the first rule of tautology club »


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

Bug#774047: [Pkg-nagios-devel] Bug#774047: pnp4nagios FTBFS on arm64, outdated config.sub/guess

2015-01-03 Thread Markus Frosch

Control: -1 tags + pending

On So, 2014-12-28 at 00:11 +, peter green wrote:
 Your package FTBFS on arm64 due to outdated config.sub/guess. This is a 
 regression and arm64 is now a release architecture hence the serious 
 severity.
 
 Version 0.6.19-1 was the last to build successfully on arm64,  Versions 
 0.6.24+dfsg1-3 was the first to fail on arm64, the intervening versions 
 were not built on arm64 due to bug 769696.

Thanks for noticing.

Patch pending in GIT, will do some work on the package this week, then
upload.

-- 
Markus Frosch
lazyfro...@debian.org / mar...@lazyfrosch.de
http://www.lazyfrosch.de


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

Bug#771496: dpkg-cross follow-up

2015-01-03 Thread Neil Williams

summary 771496 If anything you are doing would fail after the removal of 
dpkg-cross,
you're doing it wrong. It's going away, whether you want it to or not.
thanks

Just a follow-up on dpkg-cross, for the benefit of anyone reviewing
the list of RC bugs.

 You are missing an important aspect here: dpkg-cross is currently the
 only way to build a cross compiler from src:gcc-4.9.

Sorry, I did not miss that aspect: your statement is incorrect.

Clean pbuilder sid chroot:

# dpkg --add-architecture armhf
# apt-get -qq update
# apt-get build-dep cross-gcc-4.9-armhf
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following NEW packages will be installed:
  autoconf autoconf2.64 autogen autotools-dev
binutils-arm-linux-gnueabihf bison bsdmainutils chrpath cross-gcc-dev
debhelper diffstat expect file flex gawk gcc-4.9-base:armhf
gcc-4.9-source gdb gettext gettext-base groff-base guile-2.0-libs
intltool-debian libasprintf0c2 libbison-dev libc6:armhf libc6-dev:armhf
libcloog-isl-dev libcroco3 libexpat1 libffi6 libfl-dev libgc1c2
libgcc1:armhf libglib2.0-0 libgmp-dev libisl-dev libltdl7 libmagic1
libmpc-dev libmpfr-dev libopts25 libopts25-dev libpipeline1
libpython-stdlib libpython2.7 libpython2.7-minimal libpython2.7-stdlib
libsigsegv2 libssl1.0.0 libtcl8.6 libtool libunistring0 libxml2
linux-libc-dev:armhf m4 man-db mime-support netbase patchutils
po-debconf python python-minimal python2.7 python2.7-minimal quilt
realpath sharutils systemtap-sdt-dev tcl-expect zip zlib1g-dev

dpkg-cross is not mentioned in that list. Not only is it not the only
way to build a cross compiler from src:gcc-4.9, it is not even the
default way to build a cross-compiler from src:gcc-4.9. Nothing about
building a cross-compiler or using a cross-compiler on Debian unstable
has to have anything at all to do with dpkg-cross - except that
some packages need data from those config files. Even that can be
patched in locally if someone has need. Such steps are a lot less work
than has been required to get packages to cross-build previously.

It is a shame that cross-gcc-4.9-armhf couldn't get into Jessie but
then, ever since the Wheezy release, cross-building in Jessie has been
a case of downgrading to Wheezy (or Squeeze) or upgrading to unstable
(or experimental) anyway. In many ways, it is only fitting that
dpkg-cross gets removed from Jessie as it makes it clear about the
status of cross-building in Jessie - absent.

  You may want to (re)discuss this with the
  gcc maintainer: He does not seem to be aware of this deprecation and
  declares dpkg-cross supported.

Matthias is aware of my personal feelings towards dpkg-cross and the
horrors that it spawned (apt-cross and xapt) - I've spoken to him at
length, face-to-face, a couple of times. He knows that I have been
trying to kill dpkg-cross for at least two release cycles already. If
it had been possible, I would have removed dpkg-cross when apt-cross
had to be removed - instead I needed to write xapt, a program I
bitterly regret needing to create.

Yes, there is no formal deprecation notice in the dpkg-cross manpage
but that is due to the following reasons:

0: lack of support  maintenance is one reason for deprecating it - no
upload for 8 months.
1: the replacement toolchains never made it into Jessie, so there was
no time to upload dpkg-cross with such changes and get those changes
into Jessie once the replacements were shown to be working. There is no
way that a deprecation notice in dpkg-cross would meet the Freeze
Policy.
2: the problems of cross-building on jessie have been well known since
the wheezy release and all the work went into trying to get the correct
methods working.

My personal feeling is that dpkg-cross never deserved to be in the main
archive - it should have stayed in the Emdebian toolchain repositories
- but I was not involved in dpkg-cross at that time, I had to work with
it where was. As I've already said, it was never possible for
dpkg-cross to be Policy compliant. It is designed to break Policy. The
irony is that it will finally be removed from testing for doing
explicitly what it was designed to do. That is fine by me, I wanted it
gone a long time ago.

-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



pgpZMZVADntiS.pgp
Description: OpenPGP digital signature

Bug#774509: python-qt4: remove timestamps in generated files to enable reproducible building

2015-01-03 Thread Reiner Herrmann

Source: python-qt4
Version: 4.11.2+dfsg-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps toolchain

Hi,

the uic python module and the pyrcc tool are currently embedding
timestamps into the comments of generated files.
This results in packages that can't be built reproducibly, because
the timestamp will be a different one on each build (see [1]).

The attached patch removes the timestamp writing in those tools,
as this is no useful information anyway.

Regards,
 Reiner

[1]: 
https://reproducible.debian.net/userContent/issues/timestamps_in_source_generated_by_pyqt4_ui_issue.html
diff --git a/debian/changelog b/debian/changelog
index 2df5e40..43e2fde 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+python-qt4 (4.11.2+dfsg-1.0~reproducible1) UNRELEASED; urgency=low
+
+  * Added patch which removes embedding of timestamps in generated
+files, to enable reproducible builds in packages build-depending
+on python-qt4.
+
+ -- Reiner Herrmann rei...@reiner-h.de  Sat, 03 Jan 2015 16:57:18 +0100
+
 python-qt4 (4.11.2+dfsg-1) unstable; urgency=medium
 
   * New upstream bugfix release.
diff --git a/debian/patches/remove_timestamps.diff b/debian/patches/remove_timestamps.diff
new file mode 100644
index 000..c60a51d
--- /dev/null
+++ b/debian/patches/remove_timestamps.diff
@@ -0,0 +1,59 @@
+Description: prevent embedding of timestamps in files generated by rcc and uic
+ Timestamps in generated files will make packages using those tools no longer
+ build reproducibly, because the files will differ in each build.
+ As those timestamps are no useful information, they can be left out.
+Author: Reiner Herrmann rei...@reiner-h.de
+
+Index: python-qt4-4.11.2+dfsg/pyrcc/rcc.cpp
+===
+--- python-qt4-4.11.2+dfsg.orig/pyrcc/rcc.cpp
 python-qt4-4.11.2+dfsg/pyrcc/rcc.cpp
+@@ -24,7 +24,6 @@
+ #include qfile.h
+ #include qfileinfo.h
+ #include qlocale.h
+-#include qdatetime.h
+ #include qtextstream.h
+ #include qbytearray.h
+ #include qhash.h
+@@ -407,8 +406,7 @@ RCCResourceLibrary::writeHeader(FILE *ou
+ fprintf(out, # -*- coding: utf-8 -*-\n\n);
+ fprintf(out, # Resource object code\n);
+ fprintf(out, #\n);
+-fprintf(out, # Created: %s\n, QDateTime::currentDateTime().toString().toUtf8().constData());
+-fprintf(out, #  by: The Resource Compiler for PyQt (Qt v%s)\n, QT_VERSION_STR);
++fprintf(out, # Created by: The Resource Compiler for PyQt (Qt v%s)\n, QT_VERSION_STR);
+ fprintf(out, #\n);
+ fprintf(out, # WARNING! All changes made in this file will be lost!\n);
+ fprintf(out, \n);
+Index: python-qt4-4.11.2+dfsg/pyuic/uic/__init__.py
+===
+--- python-qt4-4.11.2+dfsg.orig/pyuic/uic/__init__.py
 python-qt4-4.11.2+dfsg/pyuic/uic/__init__.py
+@@ -47,8 +47,7 @@ _header = # -*- coding: utf-8 -*-
+ 
+ # Form implementation generated from reading ui file '%s'
+ #
+-# Created: %s
+-#  by: PyQt4 UI code generator %s
++# Created by: PyQt4 UI code generator %s
+ #
+ # WARNING! All changes made in this file will be lost!
+ 
+@@ -160,7 +159,6 @@ def compileUi(uifile, pyfile, execute=Fa
+ module is foo_rc.
+ 
+ 
+-from time import ctime
+ from PyQt4.QtCore import PYQT_VERSION_STR
+ 
+ try:
+@@ -170,7 +168,7 @@ def compileUi(uifile, pyfile, execute=Fa
+ 
+ indenter.indentwidth = indent
+ 
+-pyfile.write(_header % (uifname, ctime(), PYQT_VERSION_STR))
++pyfile.write(_header % (uifname, PYQT_VERSION_STR))
+ 
+ winfo = compiler.UICompiler().compileUi(uifile, pyfile, from_imports, resource_suffix)
+ 
diff --git a/debian/patches/series b/debian/patches/series
index 30a5420..a89a1d2 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,3 +1,4 @@
 debian_configure_changes.diff
 qreal_float_support.diff
 config_flags.diff
+remove_timestamps.diff


signature.asc
Description: OpenPGP digital signature

Bug#774510: pyqt5: remove timestamps in generated files to enable reproducible building

2015-01-03 Thread Reiner Herrmann

Source: pyqt5
Version: 5.3.2+dfsg-3
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps toolchain

Hi,

the uic python module and the pyrcc tool are currently embedding
timestamps into the comments of generated files.
This results in packages that can't be built reproducibly, because
the timestamp will be a different one on each build (see Qt4 exmaple in [1]).

The attached patch removes the timestamp writing in those tools,
as this is no useful information anyway.

Regards,
 Reiner

[1]: 
https://reproducible.debian.net/userContent/issues/timestamps_in_source_generated_by_pyqt4_ui_issue.html

diff --git a/debian/changelog b/debian/changelog
index 4a86a73..f541d79 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+pyqt5 (5.3.2+dfsg-3.0~reproducible1) UNRELEASED; urgency=low
+
+  * Added patch which removes embedding of timestamps in generated
+files, to enable reproducible builds in packages build-depending
+on pyqt5.
+
+ -- Reiner Herrmann rei...@reiner-h.de  Sat, 03 Jan 2015 17:54:54 +0100
+
 pyqt5 (5.3.2+dfsg-3) unstable; urgency=medium
 
   * Fix a typo in debian/tests/control.
diff --git a/debian/patches/remove_timestamps.diff b/debian/patches/remove_timestamps.diff
new file mode 100644
index 000..41f6234
--- /dev/null
+++ b/debian/patches/remove_timestamps.diff
@@ -0,0 +1,59 @@
+Description: prevent embedding of timestamps in files generated by rcc and uic
+ Timestamps in generated files will make packages using those tools no longer
+ build reproducibly, because the files will differ in each build.
+ As those timestamps are no useful information, they can be left out.
+Author: Reiner Herrmann rei...@reiner-h.de
+
+Index: pyqt5-5.3.2+dfsg/pyrcc/rcc.cpp
+===
+--- pyqt5-5.3.2+dfsg.orig/pyrcc/rcc.cpp
 pyqt5-5.3.2+dfsg/pyrcc/rcc.cpp
+@@ -45,7 +45,6 @@
+ #include qfile.h
+ #include qfileinfo.h
+ #include qlocale.h
+-#include qdatetime.h
+ #include qtextstream.h
+ #include qbytearray.h
+ #include qhash.h
+@@ -421,8 +420,7 @@ RCCResourceLibrary::writeHeader(FILE *ou
+ fprintf(out, # -*- coding: utf-8 -*-\n\n);
+ fprintf(out, # Resource object code\n);
+ fprintf(out, #\n);
+-fprintf(out, # Created: %s\n, QDateTime::currentDateTime().toString().toUtf8().constData());
+-fprintf(out, #  by: The Resource Compiler for PyQt (Qt v%s)\n, QT_VERSION_STR);
++fprintf(out, # Created by: The Resource Compiler for PyQt (Qt v%s)\n, QT_VERSION_STR);
+ fprintf(out, #\n);
+ fprintf(out, # WARNING! All changes made in this file will be lost!\n);
+ fprintf(out, \n);
+Index: pyqt5-5.3.2+dfsg/pyuic/uic/__init__.py
+===
+--- pyqt5-5.3.2+dfsg.orig/pyuic/uic/__init__.py
 pyqt5-5.3.2+dfsg/pyuic/uic/__init__.py
+@@ -47,8 +47,7 @@ _header = # -*- coding: utf-8 -*-
+ 
+ # Form implementation generated from reading ui file '%s'
+ #
+-# Created: %s
+-#  by: PyQt5 UI code generator %s
++# Created by: PyQt5 UI code generator %s
+ #
+ # WARNING! All changes made in this file will be lost!
+ 
+@@ -149,7 +148,6 @@ def compileUi(uifile, pyfile, execute=Fa
+ module is foo_rc.
+ 
+ 
+-from time import ctime
+ from PyQt5.QtCore import PYQT_VERSION_STR
+ 
+ try:
+@@ -159,7 +157,7 @@ def compileUi(uifile, pyfile, execute=Fa
+ 
+ indenter.indentwidth = indent
+ 
+-pyfile.write(_header % (uifname, ctime(), PYQT_VERSION_STR))
++pyfile.write(_header % (uifname, PYQT_VERSION_STR))
+ 
+ winfo = compiler.UICompiler().compileUi(uifile, pyfile, from_imports, resource_suffix)
+ 
diff --git a/debian/patches/series b/debian/patches/series
index 422cb22..7ca589c 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1 +1,2 @@
+remove_timestamps.diff
 add_dependency.diff


signature.asc
Description: OpenPGP digital signature

Bug#774511: www.debian.org: fix architecture list for people.d.o scripts

2015-01-03 Thread Adam D. Barratt

Package: www.debian.org
Tags: patch

Hi,

people_scripts/update.packages+sources contains a hard-coded
architecture list, which is outdated. This causes the call from
lessoften to fail with:

2015-01-03 15:22:29
URL:http://ftp.ca.debian.org/debian/dists/unstable/non-free/binary-i386/Packages.gz
 [102395/102395] - Packages.gz [1]
http://ftp.ca.debian.org/debian/dists/unstable/main/binary-ia64/Packages.gz:
2015-01-03 15:22:29 ERROR 404: Not Found.

After the error, no further architectures are updated.

The attached patch brings the architecture list back in to sync with
unstable, removing ia64 and s390 and adding arm64 and ppc64el.

Regards,

Adam
commit c8940d8f1986df80d4ebf076ca3496275b313e44
Author: Adam D. Barratt a...@adam-barratt.org.uk
Date:   Sat Jan 3 18:15:56 2015 +

Sync the architecture list with the current reality in unstable

Signed-off-by: Adam D. Barratt a...@adam-barratt.org.uk

diff --git a/people_scripts/update.packages+sources b/people_scripts/update.packages+sources
index bf8e746..95173a3 100755
--- a/people_scripts/update.packages+sources
+++ b/people_scripts/update.packages+sources
@@ -5,7 +5,7 @@ base_dir=$crondir/people_scripts
 mirror=ftp.ca.debian.org
 # -nv is kinda fucked, see bug #141323
 verbose=-nv
-arches=amd64 armel armhf hurd-i386 i386 ia64 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc s390 s390x sparc
+arches=amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc ppc64el s390x sparc
 
 test -d $base_dir/data || mkdir $base_dir/data
 cd $base_dir/data

Bug#774512: RFS: python-osmapi/0.5.0-1~exp1 [ITP]

2015-01-03 Thread Bas Couwenberg

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package python-osmapi

 Package name: python-osmapi
 Version : 0.5.0-1~exp1
 Upstream Author : Stefan Oderbolz oderb...@gmail.com
 URL : http://wiki.openstreetmap.org/wiki/Osmapi
 License : GPL-3+
 Section : python

It builds those binary packages:

 python-osmapi  - Python wrapper for the OSM API
 python3-osmapi - Python 3 wrapper for the OSM API

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

http://mentors.debian.net/package/python-osmapi


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

  dget -x 
http://mentors.debian.net/debian/pool/main/p/python-osmapi/python-osmapi_0.5.0-1~exp1.dsc

More information about OsmApi can be obtained from 
http://wiki.openstreetmap.org/wiki/Osmapi.

Changes since the last upload:

  * Initial upload (closes: #774508)


Regards,
 Bas Couwenberg


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

Bug#774507: python-pbkdf2: dead link to standard

2015-01-03 Thread Yann Dirson

Package: python-pbkdf2
Version: 1.3+20110613.git2a0fb15~ds0-3
Severity: normal

README.txt points to http://www.rsa.com/rsalabs/node.asp?id=2127 which
according to archive.org went to 302 between June and August 2013.



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

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

Versions of packages python-pbkdf2 depends on:
ii  python  2.7.8-2

python-pbkdf2 recommends no packages.

python-pbkdf2 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#545163: How to add a password to grub-pc

2015-01-03 Thread Yann Dirson

Nowadays, /etc/grub.d/40_custom provides a nice place for the set
superusers and password* commands

But that's not sufficient, as it requires the allowed boot entries to
be marked --unrestricted, which no script appears to support yet.

I am adding myself --unrestricted to the CLASS definition in
/etc/grub.d/10_linux, but that's clearly a hack, as shown by the
system being turned unbootable each time I forget that *I* was the one
adding that option and let the package overwrite this script with the
new version.

With today's infrastructure, it would not be too hard to let the admin
add such a flag from /etc/default/grub, maybe with an ADDFLAGS
variable that would be usable by more than the 10_linux script (think
Hurd/*BSD/memtest*/whatever).

Or do I miss something ?


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

Bug#774506: unblock: r-bioc-altcdfenvs/2.26.0-2

2015-01-03 Thread Ivo De Decker

Control: tags -1 moreinfo

Hi Andreas,

On Sat, Jan 03, 2015 at 06:41:05PM +0100, Andreas Tille wrote:
 Please unblock package r-bioc-altcdfenvs
 
 Due to an accidental upload to unstable instead of experimental version
 2.28.0-1 of r-bioc-altcdfenvs ended up in unstable / testing.  It does
 not fit to all other r-bioc-* packages in testing.  At the time of the
 upload the transitions were not allowed any more and thus went to
 experimental.  The upload introduces an epoch (1:) to revert the version
 upgrade which should have never ended up in testing.

The version of r-bioc-altcdfenvs currently in testing is 2.26.0-1. The 2.28
upload in unstable never migrated to testing. I guess the version currently in
testing is ok? Or am I missing something?

Cheers,

Ivo


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

Bug#737895: Twinkle depends on QT3, put back in qt3 package to get back UI - and setup

2015-01-03 Thread Ronald Duncan


Arch have managed to maintain a qt3 package ??

https://aur.archlinux.org/packages/qt3/ 
https://aur.archlinux.org/packages/qt3/


Just created an arch VM and twinkle works fine on arch using the qt3 
package. ( You have to build the qt3 package and twinkle ) but this is 
straightforward. Just have a few cups of coffee whilst qt3 goes through 
all the compiler warnings.


The arch build files just work for both qt3 and twinkle with out any 
modification/patching.


It should be straight forward to resurrect the qt3 package that Twinkle 
depends upon, since this is still working in the older distributions and 
runs fine on a modern kernel and set of dependencies under arch.


It also works for those who have installed the older package under 
Ubuntu though that results in a configuration mess having multiple 
versions on the same machine.


Regards
Ronald

Bug#774508: ITP: python-osmapi -- Python wrapper for the OSM API

2015-01-03 Thread Bas Couwenberg

Package: wnpp
Severity: wishlist
Owner: Bas Couwenberg sebas...@xs4all.nl

Package: wnpp
Owner: Bas Couwenberg sebas...@xs4all.nl
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: python-osmapi
  Version : 0.5.0
  Upstream Author : Stefan Oderbolz oderb...@gmail.com
* URL : http://wiki.openstreetmap.org/wiki/Osmapi
* License : GPL-3+
  Programming Lang: Python
  Description : Python wrapper for the OSM API

The OsmApi module is a wrapper for the OpenStreetMap API.
As such it provides an easy access to the functionality of the API.

The package will be maintained within the Debian GIS team.


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

Bug#774526: linux-image-3.2.0-4-amd64: system crash with sudden reboot when hotplugging a CPU - suspend functionality broken

2015-01-03 Thread Julius

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

Dear Maintainer,

please note that not all information that are automatically included
here represent the state of the system at the observation of the bug.
Details at the end of my explanation. I am sorry for that.

   * What led up to the situation?
==

Via the proposed updates I upgraded the package
linux-image-3.2.0-4-amd64 and headers to 3.2.65-1. After that, my
system did not wake up from suspend as usual. Instead, it booted as
if it had crashed (short filesystem check and raid resync).

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
==

After experiencing the broken suspend functionality multiple times,
here is what I tried to investigate the problem.

I did some hibernation tests using /sys/power/pm_test as described in
https://www.kernel.org/doc/Documentation/power/basic-pm-debugging.txt
and found that the processor test (enabling/disabling cores) is the
first that is failing, i.e., leading to a sudden reboot. To confirm
the CPU issue I manually tested that individually:

# cat /proc/cpuinfo | grep processor
processor   : 0
processor   : 1
# echo 0  /sys/devices/system/cpu/cpu1/online
# cat /proc/cpuinfo | grep processor
processor   : 0
# echo 1  /sys/devices/system/cpu/cpu1/online

   * What was the outcome of this action?
==

What happens then is a boot from BIOS as if I switched-on the
computer after sudden shutdown.

   * What outcome did you expect instead?
==

I expect that the last echo re-enables the CPU so that it is listed
in /proc/cpuinfo again. I confirmed that this is the behavior when
using the version 3.2.63-2+deb7u2 that also succeeds to resume after
suspending.

Something else that I tried
==

Adding maxcpus=1 as boot argument made the system boot with only one
processor in /proc/cpuinfo. With this, I made the observation that
the pm tests for hibernation work. However, resuming after a real
suspend again leads to a reboot. Hence I removed this boot argument
again.

What else I (unfortunately) did after experiencing the bug
==

I downgraded my kernel to the previous version I found by apt-cache.

# aptitude install linux-image-3.2.0-4-amd64=3.2.63-2+deb7u2 \
linux-headers-3.2.0-4-amd64=3.2.63-2+deb7u2 \
linux-headers-3.2.0-4-common=3.2.63-2+deb7u2
# update-grub
# reboot

After reboot, everything worked as expected. I thus removed the
proposed updates from /etc/apt/sources.list.

Note again that due to these changes, some of the automatically
generated information here are wrong. Now I am back to version 
3.2.63-2+deb7u2 which works. The version that fails for me is
3.2.65-1. The version part in the pseudo header of this message has
been modified by me. All other information represent the current
(working) configuration of my system. It should still be helpful
because the hardware is the same.

Finally some proof (?) that I had another version once. After typing

$ zless /var/log/apt/history.log.1.gz

there is one paragraph (besides many others) which reads

Start-Date: 2014-12-31  11:37:04
Commandline: apt-get upgrade
Upgrade: wireless-regdb:amd64 (2014.06.13-1~deb7u1, 2014.10.07-1~deb7u1), 
linux-image-3.2.0-4-amd64:amd64 (3.2.63-2+deb7u2, 3.2.65-1), 
linux-headers-3.2.0-4-amd64:amd64 (3.2.63-2+deb7u2, 3.2.65-1), 
linux-headers-3.2.0-4-common:amd64 (3.2.63-2+deb7u2, 3.2.65-1), 
linux-libc-dev:amd64 (3.2.63-2+deb7u2, 3.2.65-1)
End-Date: 2014-12-31  11:38:00

I hope that helps. Anyway thanks for all your dedication!

-- Package-specific info:
** Version:
Linux version 3.2.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.6.3 
(Debian 4.6.3-14) ) #1 SMP Debian 3.2.63-2+deb7u2

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 
root=UUID=fd570e99-d11c-4a60-b919-4f8ad6beb1bd ro quiet

** Tainted: O (4096)
 * Out-of-tree module has been loaded.

** Kernel log:
[  735.674096] Calibrating delay loop (skipped) already calibrated this CPU
[  750.627738] NMI watchdog enabled, takes one hw-pmu counter.
[  750.628318] coretemp coretemp.0: Using relative temperature scale!
[ 3778.728164] CPU 1 is now offline
[ 3778.728170] SMP alternatives: switching to UP code
[ 3791.810370] SMP alternatives: switching to SMP code
[ 3791.819085] Booting Node 0 Processor 1 APIC 0x1
[ 3791.819089] smpboot cpu 1: start_ip = 9a000
[ 3778.729199] Calibrating delay loop (skipped) already calibrated this CPU
[ 3791.867545] NMI watchdog enabled, takes one hw-pmu counter.
[ 3791.868752] coretemp coretemp.0: Using relative temperature scale!
[ 3874.716032] CPU 1 is now offline
[ 3874.716038] SMP alternatives: switching to UP code
[ 3879.894306] SMP alternatives: switching to SMP code
[ 3879.897941] Booting Node 0 Processor 1 APIC 0x1
[ 3879.897943] smpboot cpu 1: start_ip = 9a000
[ 3874.616699] Calibrating delay loop (skipped)

Bug#773378: RFS: ledgersmb/1.3.46-1

2015-01-03 Thread Vincent Cheng

Hi Robert,

On Sat, Jan 3, 2015 at 8:26 AM, Robert J. Clay rjc...@gmail.com wrote:
 Hi Vincent!

 On Fri, Jan 2, 2015 at 6:18 AM, Vincent Cheng vch...@debian.org wrote:
 Control: tag -1 moreinfo

 Hi Robert,

 On Wed, Dec 17, 2014 at 8:54 AM, Robert James Clay j...@rocasa.us wrote:
 Package: sponsorship-requests
 Severity: normal

 Dear mentors,

   I am looking for a sponsor for my package ledgersmb

 * Package name: ledgersmb
   Version : 1.3.46-1
   Upstream Author :  Chris Travers ch...@metatrontech.com
 * URL : http://www.ledgersmb.org
 * License : GPL-2+
   Section : web

 It builds those binary packages:

 ledgersmb  - financial accounting and ERP program


 Just a few small questions/comments from skimming through the debdiff:

 - You added a small dpkg-maintscript-helper snippet to
 debian/ledgersmb.postrm, specifically checking if dpkg is new enough
 to support mv_conffile before using it; what happens if dpkg isn't
 sufficiently new enough to support that / is that something that
 should just fail?
 You can simply add a Pre-Depends:
 ${misc:Pre-Depends} (which will add a pre-dependency on the
 appropriate version of dpkg)

   That would do that simply because that form of it (mv_conffile) is
 used in the mantainer scripts?

Yes.

 if you want to use
 dpkg-maintscript-helper and not have to worry about whether dpkg is
 new enough (and avoid that if dpkg-maintscript-helper supports
 mv_conffile logic).

  That version doesn't quite go back far enough for where I may want to
 support the package.  Although it's getting less likely to be an issue
 over time.  I'll admit I haven't needed to help with support on
 squeeze or lucid recently;   are you thinking that I'm worrying too
 much about a situation that isn't very likely and that would need to
 be supported differently in any case? (For instance, a separate
 backport for it, if necessary.)

I suggest one of three different options (preferably options 2 or 3,
whichever is most appropriate):

1) check if dpkg-maintscript-helper supports mv_conffile and then use
that, otherwise fallback to handwritten logic to rename the conffile
(see [1], or look at how dpkg-maintscript-helper itself is
implemented)
2) pre-depend on a sufficiently recent version of dpkg such that
mv_conffile is always known to be supported
3) don't rename the conffile at all (if it's not necessary)

My concern is that what you're currently doing seems to be a mix of
options 1 and 3, which is possibly worse than any of them, since the
outcome of running your maintainer scripts will differ depending on
what version of dpkg the user already has installed. You either always
want the conffile to be renamed, or you never want the conffile
renamed; I can't think of a valid scenario where you want to rename a
conffile if and only if dpkg supports renaming that conffile.

 - Why bump the version number in debian/NEWS when there isn't a new
 entry, and nothing else in the file has changed aside from the
 timestamp? That seems likely to just annoy apt-listchanges users.

To ensure that it is taken as being current and will be seen again
 as necessary.  (I've corresponded  with people who didn't look at it
 until I pointed it out that the info was there.)

That seems like something that should go in a readme file, or a
low-priority debconf notice at most. debian/NEWS is essentially meant
to be a more visible user changelog that's used to notify the user of
significant changes [2], not a recurring, identical message that is
displayed every time the user updates this package. That being said,
there's nothing in Policy that prevents maintainers from (ab)using
debian/NEWS for different purposes, so I guess ultimately it's up to
you as maintainer.

Also, AFAIK apt-listchanges isn't installed by default on Debian, so
users aren't guaranteed to see your NEWS entry anyways.

 Also, note that since Debian is in freeze right now, if you wish to
 target unstable, any (RC) bugfix uploads that you wish to get into
 jessie would then have to go through testing-proposed-updates (which
 the release team apparently really doesn't like). Are you sure you're
 ok with that?

 None of the three bugs I'm seeking to close with this upload are RC,
 so I had not anticipated being able to update the package in jessie in
 any case.   (The new package upgrade I'm working on now involves an
 upgrade from v1.3.x to v1.4.x;  this upgrade for 1.3.46 is currently
 the last in the 1.3.46 series.)

Ok, sounds fine to me then (please address the
maintscript/conffile-renaming issue though).

Regards,
Vincent

[1] https://wiki.debian.org/DpkgConffileHandling
[2] 
https://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html#bpp-news-debian


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

Bug#774522: wheezy-pu: clamav/0.98.5+dfsg-0+deb7u2

2015-01-03 Thread Sebastian Andrzej Siewior

Package: release.debian.org
Severity: normal
Tags: wheezy
User: release.debian@packages.debian.org
Usertags: pu

Dear release team:

I'd like to update the clamav package in Wheezy with the following change:
|* Add libmspack-qtmd-fix-frame_end-overflow to avoid endless-loop on
| special crafted quantum compressed cab files. Patch suggested by Andreas
| Cadhalpus (Closes: #773318).

There was the same change to libmspack in #773041. We have the same
libmspack in clamav since 0.98.5~rc1+dfsg-1 which is now in s-p-u/
w-updates. We wanted to use the same library in stable and sid/jessie so
now we need to update the libmspack copy since it is not in Wheezy.

Attaching debdiff with git-dpm changes.

Sebastian
diff -Nru clamav-0.98.5+dfsg/debian/.git-dpm clamav-0.98.5+dfsg/debian/.git-dpm
--- clamav-0.98.5+dfsg/debian/.git-dpm  2014-11-21 14:22:13.0 +0100
+++ clamav-0.98.5+dfsg/debian/.git-dpm  2015-01-03 22:44:52.0 +0100
@@ -1,6 +1,6 @@
 # see git-dpm(1) from git-dpm package
-e084728afa6d6b031edd8ebe6bcb5f2dfc3a91dc
-e084728afa6d6b031edd8ebe6bcb5f2dfc3a91dc
+a0449d2079c4ba5822e6567ad7094c10108f16cd
+a0449d2079c4ba5822e6567ad7094c10108f16cd
 14c3d5ca803fd6baa5ab413e87ca6d6bb2e26a3d
 14c3d5ca803fd6baa5ab413e87ca6d6bb2e26a3d
 clamav_0.98.5+dfsg.orig.tar.xz
diff -Nru clamav-0.98.5+dfsg/debian/changelog 
clamav-0.98.5+dfsg/debian/changelog
--- clamav-0.98.5+dfsg/debian/changelog 2014-11-21 15:05:24.0 +0100
+++ clamav-0.98.5+dfsg/debian/changelog 2015-01-03 22:44:52.0 +0100
@@ -1,3 +1,12 @@
+clamav (0.98.5+dfsg-0+deb7u2) stable; urgency=medium
+
+  [ Sebastian Andrzej Siewior ]
+  * Add libmspack-qtmd-fix-frame_end-overflow to avoid endless-loop on
+special crafted quantum compressed cab files. Patch suggested by Andreas
+Cadhalpus (Closes: #773318).
+
+ -- Salvatore Bonaccorso car...@debian.org  Sat, 03 Jan 2015 22:43:46 +0100
+
 clamav (0.98.5+dfsg-0+deb7u1) stable; urgency=medium
 
   [ Sebastian Andrzej Siewior ]
diff -Nru 
clamav-0.98.5+dfsg/debian/patches/0018-libmspack-qtmd-fix-frame_end-overflow.patch
 
clamav-0.98.5+dfsg/debian/patches/0018-libmspack-qtmd-fix-frame_end-overflow.patch
--- 
clamav-0.98.5+dfsg/debian/patches/0018-libmspack-qtmd-fix-frame_end-overflow.patch
  1970-01-01 01:00:00.0 +0100
+++ 
clamav-0.98.5+dfsg/debian/patches/0018-libmspack-qtmd-fix-frame_end-overflow.patch
  2015-01-03 22:44:52.0 +0100
@@ -0,0 +1,62 @@
+From a0449d2079c4ba5822e6567ad7094c10108f16cd Mon Sep 17 00:00:00 2001
+From: Sebastian Andrzej Siewior sebast...@breakpoint.cc
+Date: Tue, 23 Dec 2014 21:20:43 +0100
+Subject: libmspack: qtmd: fix frame_end overflow
+
+Debian bts #773041, #772891 contains a report of a .cab file which
+causes an endless loop.
+Eric Sharkey diagnosed the problem as frame_end is 32bit and overflows
+and the result the loop makes no progress.
+The problem seems that after the overflow, window_posn is larger than
+frame_end and therefore we never enter the loop to make progress. But we
+still have out_bytes 0 so we don't leave the outer loop either.
+
+Andreas Cadhalpun suggested to instead makeing frame_end 64bit, we could
+avoid the overflow by reordering the code the following way:
+
+original, with just out_bytes (without (qtm-o_end - qtm-o_ptr))
+| frame_end = window_posn + out_bytes;
+| if ((window_posn + frame_todo)  frame_end) {
+| frame_end = window_posn + frame_todo;
+| }
+
+replace frame_end in if with its content (and move the first frame_end
+into the else path)
+| if ((window_posn + frame_todo)  (window_posn + out_bytes))
+| frame_end = window_posn + frame_todo;
+| else
+| frame_end = window_posn + out_bytes;
+
+remove window_posn from if since it is the same both times.
+| if (frame_todo   out_bytes)
+| frame_end = window_posn + frame_todo;
+| else
+| frame_end = window_posn + out_bytes;
+
+Andreas added:
+|This works, because frame_todo is at most QTM_FRAME_SIZE = 32768.
+
+Suggested-as-patch: Andreas Cadhalpun andreas.cadhal...@googlemail.com
+[sebastian@breakpoint: added patch description]
+Signed-off-by: Sebastian Andrzej Siewior sebast...@breakpoint.cc
+---
+ libclamav/libmspack-0.4alpha/mspack/qtmd.c | 5 +++--
+ 1 file changed, 3 insertions(+), 2 deletions(-)
+
+diff --git a/libclamav/libmspack-0.4alpha/mspack/qtmd.c 
b/libclamav/libmspack-0.4alpha/mspack/qtmd.c
+index 12b27f5608c4..e584aef8e576 100644
+--- a/libclamav/libmspack-0.4alpha/mspack/qtmd.c
 b/libclamav/libmspack-0.4alpha/mspack/qtmd.c
+@@ -296,9 +296,10 @@ int qtmd_decompress(struct qtmd_stream *qtm, off_t 
out_bytes) {
+ 
+ /* decode more, up to the number of bytes needed, the frame boundary,
+  * or the window boundary, whichever comes first */
+-frame_end = window_posn + (out_bytes - (qtm-o_end - qtm-o_ptr));
+-if ((window_posn + frame_todo)  frame_end) {
++if (frame_todo  (out_bytes - (qtm-o_end - qtm-o_ptr))) {
+   frame_end = window_posn + frame_todo;
++} else {
++

Bug#772008: CVE request: mpfr: buffer overflow in mpfr_strtofr

2015-01-03 Thread cve-assign



On Tue, 30 Dec 2014, Moritz Muehlenhoff wrote:


On Mon, Dec 08, 2014 at 01:45:12PM +0100, Vasyl Kaigorodov wrote:

Hello,

A buffer overflow was reported [1] in mpfr.
This is due to incorrect GMP documentation for mpn_set_str about the
size of a buffer (discussion is at [1]; first fix in the GMP
documentation is at [2]). This bug is present in the MPFR versions
from 2.1.0 (adding mpfr_strtofr) to this one, and can be detected by
running make check in a 32-bit ABI under GNU/Linux with alloca
disabled (this is currently possible by using the --with-gmp-build
configure option where alloca has been disabled in the GMP build). It
is fixed by the strtofr patch [3].
Corresponding changeset in the 3.1 branch: 9110 [4].

[1]: https://gmplib.org/list-archives/gmp-bugs/2013-December/003267.html
[2]: https://gmplib.org/repo/gmp-5.1/raw-rev/d19172622a74
[3]: http://www.mpfr.org/mpfr-3.1.2/patch11
[4]: https://gforge.inria.fr/scm/viewvc.php?view=revroot=mpfrrevision=9110

References:
- https://bugzilla.redhat.com/show_bug.cgi?id=1171701
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772008

Can a CVE be assigned to this please?


Use CVE-2014-9474.

---

CVE assignment team, MITRE CVE Numbering Authority M/S M300
202 Burlington Road, Bedford, MA 01730 USA
[ PGP key available through http://cve.mitre.org/cve/request_id.html ]


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

Bug#774524: squeezelite: Dies frequently with SIGSEGV

2015-01-03 Thread John Goerzen

Package: squeezelite
Version: 1.6.4-1+b1
Severity: important

I've had squeezelite die on me several times with SIGSEGV.  I do have a
core file, although gdb bt doesn't seem to show much of use with it.
Let me know how I can help you debug this.


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

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

Versions of packages squeezelite depends on:
ii  libasound2  1.0.28-1
ii  libavcodec566:11-2
ii  libavformat56   6:11-2
ii  libavutil54 6:11-2
ii  libc6   2.19-13
ii  libfaad22.7-8
ii  libflac81.3.0-3
ii  libmad0 0.15.1b-8
ii  libmpg123-0 1.20.1-2
ii  libsoxr00.1.1-1
ii  libvorbisfile3  1.3.4-2

squeezelite recommends no packages.

squeezelite 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#774523: Mirror/dist cache sub-directories

2015-01-03 Thread jnqnfe

Package: live-build
Version: 5.0~a1-1
Severity: wishlist

A possible improvement for the future, submitting now ahead of time.
(Can be ignored for the time being).

Taking a que from the current installer_debian-installer cache, which
uses URLs (with forward slashes replaced with underscores) in the
filenames, to separate out files from different locations, such as daily
builds of installer image files from normal, my new almost complete bug
#718225 solution caches files in a similar way, using the URL to build
sub directories that closely mirror the URL path.

There are advantages to this, making the cache more suitable for
building images of different distributions, and when building for a
derivative distribution, it ensures that files from parent and
derivative mirrors are separated. Also, should a user mix up the parent
and derivative config parameters, and then correct them without flushing
the cache, there's no problem, the correct files are retrieved from the
cache.

I actually don't particularly like the base of the URL being used in
this way because although it works, it looks really messy. Furthermore,
simply switching from say one debian mirror to another means perfectly
good cached files are ignored, which isn't desirable. So I'm considering
alternatives for how this could be improved in the future (LB v5.x).

One would be simply sub-directories of 'parent' and 'derivative' or
'parent{-|.}mirror' and 'derivative{-|.}mirror'. This obviously breaks
the latter advantage of the user specifying the URLs the wrong way
around and fixing without a cache flush though (not a big deal, but good
to allow if possible). It also requires ensuring that 'parent'
attributes are used throughout the code when not doing a derivative
build, if this is not the case already, but such consistency is
desirable anyhow.

An alternative could be to have a simple label to go alongside each of
parent and derivative mirrors, i.e. 'debian', 'ubuntu',
'progress-linux', etc., which can be used for sub-directory names (e.g.
cache/packages.bootstrap/debian).

How such labels are supplied is a tricky question however. It would be
over the top I think for new config params to be added. Hard coding a
grep against the url to determine which of progress-linux/ubuntu/debian
might work, but further works against opening up use of LB on more
derivative distributions (something I personally am supportive of
improving, I don't know about maintainer).

The best approach might be to completely revise the config format in the
planned switch to python in v5.x+. Instead of taking the user's config
as a set of parameters, read them from a file (as is done with the full
config files in config/ after processing auto/config and other params).
This would provide a more simple opportunity for the user to supply
labels. Furthermore, much more of the 'mode' customisations could
possibly be captured in such a config file, making the code neater,
simpler, and more open to other debian derivatives.


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

Bug#774525: installation-reports: Problem formating entire disk to ext4.

2015-01-03 Thread Marek Zelem

Package: installation-reports
Severity: important

When attempting to format entire disk (LOOP partition type) to ext4 format
process hangs at 30% or so.
I figured out that it runs mkfs.ext4 /dev/sda which prompts whether I realy
want to format entire disk.

Solution to this problem is to add option -F to mkfs.
I did it by modifying file /lib/partman/commit.d/50format_ext3 line starting
with mkfs.$filesystem $device ... to mkfs.$filesystem -F $device ...
My fix worked.


-- Package-specific info:

Boot method: CD
Image version: 
http://cdimage.debian.org/debian-cd/7.7.0/amd64/iso-cd/debian-7.7.0-amd64-netinst.iso
Date: Date and time of the install

Machine: QEMU virtual machine
Partitions: df -Tl will do; the raw partition table is preferred


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [ ]
Detect network card:[ ]
Configure network:  [ ]
Detect CD:  [ ]
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:

Description of the install, in prose, and any thoughts, comments
  and ideas you had during the initial install.


-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.


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

Bug#774466: choose-mirror: references cdn.debian.net, which is deprecated

2015-01-03 Thread Cyril Brulebois

Control: tag -1 moreinfo
Control: severity -1 normal

Paul Wise p...@debian.org (2015-01-03):
 Source: choose-mirror
 Severity: important
 
 cdn.debian.net is in the process of being deprecated, orphaned and
 transitioned to http.debian.net, please remove it from the mirrors list.
 This should be fixed in both wheezy and jessie d-i.
 
 https://lists.debian.org/cag2rkxmdbll-vsfw6deu4p0nwt7qqor3pxvqdu-mwrm1j-6...@mail.gmail.com

Please get the upstream file fixed?

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#760763: fixed in libav 6:11~beta1-3

Control: tags -1 + pending

On 2014-12-31 13:15:32, Jakub Wilk wrote:
 * Sebastian Ramacher sramac...@debian.org, 2014-12-31, 11:46:
 So I've tried some upgrades yesterday and was able to reproduce it. The
 version given in libav-tools.maintscript is too low, since 6:10.2-1 still
 contains /etc/avserver.conf. It was removed from the binary package in
 6:11~alpha1-1.
 
 This should do the trick:
 
 diff --git a/debian/libav-tools.maintscript b/debian/libav-tools.maintscript
 index fd11a31..c19977d 100644
 --- a/debian/libav-tools.maintscript
 +++ b/debian/libav-tools.maintscript
 @@ -1 +1 @@
 -rm_conffile /etc/avserver.conf 6:10.2-1~
 +rm_conffile /etc/avserver.conf 6:11~alpha1-1~
 
 dpkg-maintscript-helper(1) manpage says: “If the conffile has not been
 shipped for several versions, and you are now modifying the maintainer
 scripts to clean up the obsolete file, prior-version should be based on
 the version of the package that you are now preparing, not the first version
 of the package that lacked the conffile.
 
 So, assuming the *.maintscript file will be fixed in 6:11.1-2, it should
 read:
 
 rm_conffile /etc/avserver.conf 6:11.1-2~

Thanks, I forgot about that. This is now fixed in the experimental
branch.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature

Bug#774134: pre-approval: unblock: wader/0.5.12-1.1

2015-01-03 Thread Graham Inggs

Attached is an updated debdiff which includes upstream's fix for
#768756 and change of maintainer and uploaders fields.
It also includes some minor packaging changes which were committed to
wader's vcs [1], but not yet released (see #662823).

I haven't pushed any changes to wader's vcs as I am waiting for
approval to join the Python Applications Packaging Team.


[1] http://anonscm.debian.org/viewvc/python-apps/packages/wader/


wader-new-maintainer.debdiff
Description: Binary data

Bug#774466: delete cdn.debian.net from mirrors list

2015-01-03 Thread Christian PERRIER

Quoting Miguel Figueiredo (el...@debianpt.org):
 diff --git a/Mirrors.masterlist b/Mirrors.masterlist


Isn't Mirrors.masterlist generated at build time? So this bug would
indeed be useless, assuming that we rebuild choose-mirror and the
official mirror list is updated to drop cdn.debian.net

Or am I missing something?




signature.asc
Description: Digital signature

Bug#747069: New upstream release and maintainer

2015-01-03 Thread Jackson Doak

Upstream has now released version 1.0. Has there been any progress on this?
https://github.com/SpamExperts/pyzor/releases

Bug#758389:

2015-01-03 Thread Jackson Doak

This should be fixed in the upstream git. Could someone please check that
everything is working? https://github.com/dialelo/turses

Bug#774501: base: Distorted single channel audio output

2015-01-03 Thread Alexander Veit

Package: base
Severity: important

Dear Maintainer,

After installing Debian Jessie (with XFCE desktop) audio output is only
hearable on the left channel and sounds metallic.  Any attempts to fix
the problem failed.  Tests with Windows 7 on the same machine showed
good sound quality, so hardware defects can be ruled out.


System: Dell Precision 7810 Workstation

XFCE Audio Mixer shows HDAIntel PCH (Alsa mixer)

~ # cat /proc/asound/cards
 0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0xfbf3 irq 70
 1 [Generic]: HDA-Intel - HD-Audio Generic
  HD-Audio Generic at 0xfbe6 irq 72

~ # lsmod | grep -i snd
snd_hda_codec_hdmi 45118  1
snd_hda_codec_realtek63031  1
snd_hda_codec_generic63107  1 snd_hda_codec_realtek
snd_hda_intel  26327  10
snd_hda_controller 26727  1 snd_hda_intel
snd_hda_codec 104463  5
snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel,snd_hda_controller
snd_hwdep  13148  1 snd_hda_codec
snd_pcm88662  5
snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_controller
snd_timer  26614  1 snd_pcm
snd65244  27
snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
soundcore  13026  2 snd,snd_hda_codec

~ # lspci -v

00:1b.0 Audio device: Intel Corporation Wellsburg HD Audio Controller
(rev 05)
Subsystem: Dell Device 0618
Flags: bus master, fast devsel, latency 0, IRQ 70
Memory at fbf3 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Kernel driver in use: snd_hda_intel

02:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device aac0
Subsystem: Dell Device aac0
Physical Slot: 2
Flags: bus master, fast devsel, latency 0, IRQ 72
Memory at fbe6 (64-bit, non-prefetchable) [size=16K]
Capabilities: [48] Vendor Specific Information: Len=08 ?
Capabilities: [50] Power Management version 3
Capabilities: [58] Express Legacy Endpoint, MSI 00
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1
Len=010 ?
Capabilities: [150] Advanced Error Reporting
Kernel driver in use: snd_hda_intel





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

Kernel: Linux 3.16.0-4-amd64 (SMP w/16 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)


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

Bug#774499: RFP: wmm -- The World Magnetic Model

2015-01-03 Thread Erich Schulman (KT4VOL/KTN4CA)

Package: wnpp
Severity: wishlist

Package name : wmm
Version : 2014
Upstream Author : geomag.mod...@noaa.gov
URL : http://www.ngdc.noaa.gov/geomag/WMM/DoDWMM.shtml
http://www.ngdc.noaa.gov/geomag/WMM/soft.shtml
License : Public domain (attribution to US government may be required)
http://www.ngdc.noaa.gov/geomag/WMM/license.shtml
Description :

The World Magnetic Model is a joint product of the United States’ National
Geospatial-Intelligence Agency (NGA) and the United Kingdom’s Defence
Geographic Centre (DGC). The WMM was developed jointly by the National
Geophysical Data Center (NGDC, Boulder CO, USA) and the British Geological
Survey (BGS, Edinburgh, Scotland).

The World Magnetic Model is the standard model used by the U.S. Department
of Defense, the U.K. Ministry of Defence, the North Atlantic Treaty
Organization (NATO) and the International Hydrographic Organization (IHO),
for navigation, attitude and heading referencing systems using the
geomagnetic field. It is also used widely in civilian navigation and
heading systems. The model, associated software, and documentation are
distributed by NGDC on behalf of NGA. The model is produced at 5-year
intervals, with the current model expiring on December 31, 2019.
The software computes the main components of the geomagnetic field and
their annual changes. The programs are designed to be used in demand mode.
The software is available as both C and Fortran source code. The model
file, WMM.COF, is expected to reside in the same directory as the software.
Note: The altitude is referenced to the World Geodetic System 1984 (WGS 84)
ellipsoid. The WMM software library provides functions to convert height
above mean sea level (AMSL) to height above WGS 84. This option is enabled
by default.

Bug#774496: ncurses: please make ncurses build reproducibly

Sven Joachim:
I am not strictly opposed to your patch, but I think the problem should
be tackled elsewhere, so that fewer packages need to be modified.

In our experimental toolchain, packages built using `dh` will
automatically call `dh_strip_nondeterminism`. Packages using `dh` are
the 60% plateau you can see on:
https://jenkins.debian.net/userContent/stats_pkg_state.png

Since a few days, we are getting more packages considered reproducible
as we moved generation of the .buildinfo files to dpkg-buildpackage
instead of doing it as a dh stop.

Have you considered filing a wishlist bug against binutils to build with
--enable-deterministic-archives, so that ar and ranlib operate in
deterministic mode by default?

Yes. This is how we did the experiment in January last year:
https://wiki.debian.org/ReproducibleBuilds/Rebuild20140126

During discussions at DebConf14, it was acknowledged that having
`--enable-deterministic-archives` could break some build systems in
subtle ways and that it would be better to do without. Unfortunately,
I have never been able to get Matthias Klose's opinion on the matter.

Also, what's the current state of #759895?

The original patch became part of strip-nondeterminism. I guess it
should be updated to ask the inclusion of the following patch:
https://anonscm.debian.org/cgit/reproducible/debhelper.git/commit/?h=pu/reproducible_buildsid=7fbd7ba

--
Lunar.''`.
lu...@debian.org: :Ⓐ : # apt-get install anarchism
`. `'`
`-

signature.asc
Description: Digital signature

Bug#774498: base-files: please make the build reproducible

 Tags: patch

Here it is.

-- 
Lunar.''`. 
lu...@debian.org: :Ⓐ  :  # apt-get install anarchism
`. `'` 
  `-   
diff -Nru base-files-8/debian/changelog base-files-8.0~reproducible1/debian/changelog
--- base-files-8/debian/changelog	2014-11-30 13:36:23.0 +0100
+++ base-files-8.0~reproducible1/debian/changelog	2015-01-03 14:36:15.0 +0100
@@ -1,3 +1,11 @@
+base-files (8.0~reproducible1) UNRELEASED; urgency=low
+
+  * Make package build reproducibly:
+  - Stop recording current time in gzip headers.
+  - Fix mtimes before building the binary package.
+
+ -- Jérémy Bobbio lu...@debian.org  Sat, 03 Jan 2015 13:35:32 +
+
 base-files (8) unstable; urgency=low
 
   * Release for jessie as stable:
diff -Nru base-files-8/debian/rules base-files-8.0~reproducible1/debian/rules
--- base-files-8/debian/rules	2014-07-20 12:11:12.0 +0200
+++ base-files-8.0~reproducible1/debian/rules	2015-01-03 14:35:30.0 +0100
@@ -11,6 +11,8 @@
   OSNAME=GNU/Hurd
 endif
 
+BUILD_DATE := $(shell dpkg-parsechangelog | sed -n -e 's/^Date: //p')
+
 VENDORFILE = debian
 
 VERSION = $(shell cat etc/debian_version)
@@ -64,7 +66,7 @@
 		 debian/tmp/etc/os-release
 	mv debian/tmp/etc/os-release debian/tmp/usr/lib
 	ln -s ../usr/lib/os-release debian/tmp/etc/os-release
-	gzip -9 $(docdir)/changelog
+	gzip -9n $(docdir)/changelog
 	cd debian/tmp  \
 		md5sum `find usr -type f`  DEBIAN/md5sums
 	chown -R root:root debian/tmp
@@ -74,6 +76,8 @@
 	cd debian/tmp  chmod 2775 `cat ../2775-dirs`
 	cd debian/tmp  chmod 700 root
 	dpkg-gencontrol -pbase-files
+	find debian/tmp -depth -newermt '$(BUILD_DATE)' -print0 | \
+		xargs -0r touch --no-dereference --date='$(BUILD_DATE)'
 	dpkg-deb --build -Zgzip debian/tmp ..
 
 binary-indep: build


signature.asc
Description: Digital signature

Bug#774496: ncurses: please make ncurses build reproducibly

2015-01-03 Thread Sven Joachim

On 2015-01-03 14:19 +0100, Jérémy Bobbio wrote:

 While working on the “reproducible builds” effort [1], we have noticed
 that ncurses could not be built reproducibly.

 The attached patch will add calls to strip-nondeterminism on static
 libraries. Once applied, the package can be built reproducibly with our
 current experimental framework.

 I've initially tried to run `ar` in deterministic mode by passing
 ARFLAGS=Dcrv. Unfortunately, `ranlib` is called after `ar` and there
 doesn't seem to be a way to pass the `-D` flag to it, and so it will
 write a timestamp in the newly created index.

I am not strictly opposed to your patch, but I think the problem should
be tackled elsewhere, so that fewer packages need to be modified.

Have you considered filing a wishlist bug against binutils to build with
--enable-deterministic-archives, so that ar and ranlib operate in
deterministic mode by default?  Also, what's the current state of
#759895?

Cheers,
   Sven


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

Bug#774412: Re: Bug#774412: systemd unable to boot with fixed mount points

2015-01-03 Thread Andrei POPESCU

Control: severity -1 minor
Control: retitle -1 systemd-fsck tries to check unavailable filesystems even if 
0 in fstab passno field

On Sb, 03 ian 15, 13:42:34, HJ wrote:
 Does systemd still try to fsck the non-available filesystem?
 
 no ;)

Ok, since systemd is failing the boot by design if a filesystem not 
marked 'nofail' or 'noauto' is missing I'll re-purpose this bug to be 
about the additional delay due to systemd-fsck trying to check a 
filesystem which is not available, despite it being marked to not be 
checked in fstab.

However, since fsck will be skipped in the normal case I'll downgrade to 
'minor'.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Bug#759824: Fwd: [pyfltk:bugs] #24 FTBFS: ./python/fltk_wrap.cpp:5241:35: error: format not a string literal and no format arguments [-Werror=format-security]

2015-01-03 Thread Jean-Michel Nirgal Vourgère

Control: tags -1 fixed-upstream

 Forwarded Message 
Subject: [pyfltk:bugs] #24 FTBFS: ./python/fltk_wrap.cpp:5241:35: error:
format not a string literal and no format arguments
[-Werror=format-security]
Date: Sat, 03 Jan 2015 10:37:08 +
From: Andreas Held andreash...@users.sf.net
Reply-To: [pyfltk:bugs]  2...@bugs.pyfltk.p.re.sf.net
To: [pyfltk:bugs]  2...@bugs.pyfltk.p.re.sf.net

- **status**: pending -- open-fixed
- **Comment**:

Fixed in release V1.3.3



signature.asc
Description: OpenPGP digital signature

Bug#759895: [Reproducible-builds] Bug#774496: ncurses: please make ncurses build reproducibly

2015-01-03 Thread Holger Levsen

On Samstag, 3. Januar 2015, Jérémy Bobbio wrote:
 Sven Joachim:
  Also, what's the current state of #759895?
 
 The original patch became part of strip-nondeterminism. I guess it
 should be updated to ask the inclusion of the following patch:
 https://anonscm.debian.org/cgit/reproducible/debhelper.git/commit/?h=pu/rep
 roducible_buildsid=7fbd7ba





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

Bug#774500: please notify maintainers when their packages are orphaned by other people

2015-01-03 Thread Holger Levsen

package: bugs.debian.org

Hi,

when someone else orphans a package, the maintainers of that package are not 
automatically notified, as the bug is assigned to the wnpp pseudo-package. 
Thus maintainers might not learn about this (it's shown in the PTS, so it's  
not hidden), but there is no active notification which I consider a bug. (And 
not just a wishlist missing feature ;)


cheers,
Holger


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

Bug#768314: [pkg-cryptsetup-devel] Bug#768314: cryptsetup: Passphrase prompt rolls by without stopping (fwd)

2015-01-03 Thread Tomas Pospisek


Hello systemd maintainers  Laurent,

bug #768314 [0] has been reassigned to the release-notes. It's 
about a user not being able to enter his cryptsetup 
password. A solution seems to be to install plymouth.


It seems, that's a known problem, as noted in your titanpad [1]. However I 
could not find a respective issue in the BTS entries for systemd [2] - is 
there one that tracks this problem?


Do you have any idea how this problem should be resolved for jessie?

The original owner of the bug report suggests raising plymouth to a 
Recommends dependency.


I suggested that systemd could recognize that there are mounted crypted 
partitions and suggest to the user to install plymouth at postinst time.


Another workaround would be to just document the problem in the release 
notes and hope users won't run into it.


Do you see or prefer any other approach?

Second question: in the titanpad entry you write The plan with plymouth 
0.9.0-9 is to not require any modification to the kernel cmdline and 
enable the I/O multiplexing functionality by default when the pkg is 
installed.


As far as I can see from the plymouth changelog [3] no solution was 
implemented for this problem [4] in 0.9.0-9 and there hasn't been any 
activity in that bug report since Nov 14th. What's the current goal/aim 
wrt that bug?


Thanks,
*t

[0] https://bugs.debian.org/768314
[1] https://debian.titanpad.com/23?
[2] http://bugs.debian.org/systemd
[3] 
http://metadata.ftp-master.debian.org/changelogs//main/p/plymouth/plymouth_0.9.0-9_changelog
[4] https://bugs.debian.org/768329

@bugs.debian.org -- Forwarded message --
Date: Tue, 30 Dec 2014 23:11:58 +0100
From: Jonas Meurer jo...@freesources.org
To: Tomas Pospisek t...@sourcepole.ch, 768...@bugs.debian.org
Cc: Kjetil Kjernsmo kje...@kjernsmo.net
Subject: Re: [pkg-cryptsetup-devel] Bug#768314: cryptsetup: Passphrase prompt
rolls by without stopping

Hi Tomas,

thanks for taking care of the bugreport.

Am 30.12.2014 um 19:27 schrieb Tomas Pospisek:

Hello Jonas  Kjetil,

(context: I'm reading through release-notes bug reports).

I'm not sure I understand what you are expecting as a result by
cloning/reassigning this to the release notes -

Let me try to understand the problem:

* if there's an encrypted partition, then systemd, who aparently would be
  responsible to do so will not prompt for the password, if plymouth is
  not installed.

Is my understanding of the problem correct?


Yes. Actually, it is even more complicated, but your understanding is
correct:

Systemd includes its own dm-crypt/cryptsetup device unlocking functions.
With systemd as init system, it processes all dm-crypt encrypted devices
that shall be unlocked during the boot process and *after* initramfs.
I don't know systemd, but from the bugreports I learned that it
apparently doesn't implement a proper mechanism to prompt for user input
itself. Instead it relies on plymouth doing that task. As a result,
systemd without plymouth doesn't wait for user input at unlocking
dm-crypt devices but instead continues to print boot logging output to
the console.


So I think the right thing to do would be, that during the upgrade the
systemd postinstallation should check whether there are some mounted
partitions that are crypted and then recommend to install plymouth. Do
you concur?


I would even go futher and say that systemd should recommend plymouth in
any case. Still, if it's only recommended and not a hard dependency, the
discovered behaviour should be documented in the release notes in my eyes.


Otherwise, should the release-notes recommend to install plymouth to the
user if s/he has crypted partitions that should get mounted during boot?


Yes, that's what needs to be done at least.


Ideally IMHO the release notes should also explain the problem in
sufficient technical detail to allow the user to take his own steps to
further understand the problem and to choose an alternative solution if
he deems so.

Optimally you could suggest a wording?


Unfortunately I've not enough knowledge about systemd to propose a
wording. But feel free to use anything I wrote in the bugreport for a draft.

Cheers,
 jonas


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

Bug#738760: libav: Add proper raspberry pi CPU detection

Control: tags -1 moreinfo

On 2014-09-26 13:12:42, Janne Grunau wrote:
 On 2014-09-05 00:17:15 +0200, Florian Will wrote:
  Hi,
  
  Please note that I'm not the bug submitter.
  
   Can you provide a patch, please?
  
  As of now, I can't. :/ I don't have the hardware to reproduce this or to
  verify the correctness of a patch.
  
  So I can only give a few hints about the background of this bug report.
  Anyone not planning to come up with a patch can probably skip it. :-)
  
   I don't know much about raspbian, and don't understand what you
   actually want to be changed here.
  
  I've used raspbian some time ago. The issue with some packages is that
  they enable ARM NEON instructions (and other illegal instructions?)
  during compilation, either generally for the armhf architecture, or
  based on what the build machine supports. The Raspberry Pi is armhf, but
  does not support NEON. Raspbian buildds *do* probably support NEON though.
  
  The Raspbian toolchain is configured to disable NEON. However, libav
  apparently still ends up with NEON instructions in the binary.
 
 That is not a problem. If NEON is disabled in the toolchain there will 
 be still NEON specific asm included which will be only used if a CPU 
 with NEON is detected at runtime. I'm quite certain that this works as 
 intended.
 
  Surprisingly, NEON is supposed to get enabled for libav only if the
  debian/confflag script detects that the toolchain supports NEON.
  
  Still, for the libav package in Raspbian, this line was changed:
  #RPI -- don't build neon flavour
  #FLAVORS += neon
 
 That's now how I read the debian/confflags in 
 http://security.debian.org/debian-security/pool/updates/main/liba/libav/libav_0.8.16-1.debian.tar.gz
 
 It checks if the toolchain supports NEON and other things by default. If 
 it does *not* support NEON, the debian package will build a additional 
 NEON flavor of the package. Building that flavor is quite pointless if a 
 single CPU without NEON is targeted. So disabling that in raspbian makes 
 sense.
 
 Building a NEON flavor makes sense for general distribution like Debian 
 that will run on different CPUs with different supported instruction set 
 extensions.
 
 That is the only relevant change I see in debian/ for the libav src 
 package.
 
 So unless the original patch reported specifies what he wants exactly 
 I'd say everything is fine and working as expected.
 
 The only minor issue is that if the toolchain uses NEON by default and 
 one uses '-mfpu=' to disable it, the check will be wrong. I don;t think 
 any of the debian toolchains are configured this way though.

Hi Peter,

there was a request to change the handling of the Raspberry Pi in the
libav package. Could you please explain the changes applied to the
Raspbian version? To me it looks like there's nothing wrong with the
package, but that you have applied some flags to optimize for the
Raspberry Pi? Is my understanding of the situation correct?

For the record, this is the current diff:

diff -Nru libav-11/debian/changelog libav-11/debian/changelog
--- libav-11/debian/changelog   2014-10-19 22:20:25.0 +0200
+++ libav-11/debian/changelog   2014-11-26 23:05:30.0 +0100
@@ -1,3 +1,11 @@
+libav (6:11-2+rpi1) jessie-staging; urgency=low
+
+  * Disable build of neon flavour
+  * Disable armv6t2 and neon for regular flavours
+  * Disable runtime cpu detection
+
+ -- Peter Michael Green plugw...@raspbian.org  Wed, 26 Nov 2014 22:05:05 
+
+
 libav (6:11-2) unstable; urgency=medium
 
   * add patches post v11 release, all of which will be included in the 
diff -Nru libav-11/debian/confflags libav-11/debian/confflags
--- libav-11/debian/confflags   2014-10-19 22:18:26.0 +0200
+++ libav-11/debian/confflags   2014-11-26 23:05:30.0 +0100
@@ -47,7 +47,8 @@
 endif
 # only build a NEON flavour if the toolchain doesn't enable NEON by default
 ifneq ($(has_neon),1)
-FLAVORS += neon
+#RPI -- don't build neon flavour
+#FLAVORS += neon
 endif
 # calling-conventions for VFP and NEON flavours: if the toolchain uses
 # -mfloat-abi=soft, we want to use softfp, otherwise we want to use the
@@ -97,12 +98,13 @@
 # Common configuration flags
 confflags += --arch='$(DEB_HOST_ARCH_CPU)'
 confflags += --enable-pthreads
-confflags += --enable-runtime-cpudetect
+#confflags += --enable-runtime-cpudetect
 confflags += --extra-version='$(DEB_VERSION)'
 confflags += --libdir=/usr/lib/$(DEB_HOST_MULTIARCH)
 confflags += --prefix=/usr
 confflags += $(shell test -x /usr/bin/yasm || echo --disable-yasm )
 confflags += --disable-avserver
+confflags += --disable-armv6t2 --disable-neon
 
 ifeq  ($(DEB_HOST_ARCH),armel)
 # this is required on Ubuntu lucid as it defaults to thumb2 and Libav has

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature

Bug#774361: how to play?

2015-01-03 Thread Markus Koschany

Hi Tomas,

On 03.01.2015 14:22, Tomas Pospisek wrote:
 tags 774361 - moreinfo + patch
 severity 774361 wishlist
 
 thanks
 
 Hello in the new year Markus,
 
 I've should have also read the accompanying README.lgeneral.gz, then I
 would have known. However I suggest to make it easier to users to just
 play. 

I have just improved README.Debian. You can find the new version at

http://anonscm.debian.org/cgit/pkg-games/lgeneral.git/tree/debian/README.Debian

I hope this new version incorporates your suggestions and makes it now
generally intelligible how to start and play a game.


 Imagine the following situation:
 
 It's christmas holidays and I'm bored. I fire up aptitude and install
 some games at random. Then I start them from the Applications menu.
 
 Once the game is started I think the user will intuitively start
 clicking around, not least around the menu. But unless he first selects
 a scenario *and then also a campaign*, he will not be able to play.

This is not correct. You can play the game by selecting a single
scenario. A campaign is merely a sequence of scenarios accompanied by a
short briefing screen. A campaign is not mandatory to play the game.

 I think ideally the game should give the users a hint what to do next.
 
 So upon loading the scenario, the text that is displayed should tell the
 user and now select a campaign from the menu.
 
 But all of this is material for upstream.

I agree that the game could be a lot more user friendly. However one
must understand what LGeneral always was, a game engine without free
data. I believe this is already well explained in README.lgeneral but I
did emphasize this in README.Debian too. For playing the original,
non-free, Panzer General campaign, the user has to take additional steps.

 What the Debian package could do is to make it easier for the Debian
 user. I think an advanced user will at least have a look at the
 README.Debian, and that's where you could give him/her the necessary
 hint. The same hint should also go into the manpage IMHO...

The Debian package already goes far beyond what upstream provides. You
can install lgeneral and you will also get additional free WWI scenarios
+ a very convenient way to install the original PG campaign by using
game-data-packager.

game-data-packager lgeneral -w

I think the man page is fine because lgeneral really is only the engine.
I think a pop-up warning would be nice, if you click on the PG campaign
but didn't install the data prior to that. This is something for
upstream and I gladly forward patches to him.

If there are no further objections, I will fix this issue with the next
scheduled upload of LGeneral.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#774514: winbind crashes when a user with an expired password logs in

2015-01-03 Thread Jason Gunthorpe

Package: winbind
Version: 2:4.1.13+dfsg-2
Severity: important

Pretty simple, if the password has expired in AD then at login a
winbind process begins looping with 100% CPU and all of winbind
becomes unusable, which basically crashes the OS since nss hangs.

Further, 'systemctl restart winbindd' doesn't actually kill the
looping winbind (!?! I thought systemd gurenteed that?) a kill -9 is
needed to recover from this.

gdb says the backtrace is:

#0  0x7f7b059013cf in krb5_get_init_creds_password () from 
/usr/lib/x86_64-linux-gnu/libkrb5.so.26
#1  0x7f7b0797f969 in kerberos_kinit_password_ext () from 
/usr/lib/x86_64-linux-gnu/samba/libgse.so.0
#2  0x7f7b0b995959 in kerberos_return_pac ()
#3  0x7f7b0b9bb530 in winbindd_dual_pam_auth ()
#4  0x7f7b0b9cfcec in ?? ()
#5  0x7f7b04e402cb in ?? () from /usr/lib/x86_64-linux-gnu/libtevent.so.0
#6  0x7f7b04e3e797 in ?? () from /usr/lib/x86_64-linux-gnu/libtevent.so.0
#7  0x7f7b04e3af9d in _tevent_loop_once () from 
/usr/lib/x86_64-linux-gnu/libtevent.so.0
#8  0x7f7b0b9d2068 in ?? ()
#9  0x7f7b0b9d2765 in ?? ()
#10 0x7f7b04e3b7c4 in tevent_common_loop_immediate () from 
/usr/lib/x86_64-linux-gnu/libtevent.so.0
#11 0x7f7b04e4008e in ?? () from /usr/lib/x86_64-linux-gnu/libtevent.so.0
#12 0x7f7b04e3e797 in ?? () from /usr/lib/x86_64-linux-gnu/libtevent.so.0
#13 0x7f7b04e3af9d in _tevent_loop_once () from 
/usr/lib/x86_64-linux-gnu/libtevent.so.0
#14 0x7f7b0b994fac in main ()

The internet has a few notes about something that sounds very similar:

https://bugzilla.samba.org/show_bug.cgi?id=8747

  The prompter only returns the password once, so the Kerberos library
  sees that the entered passwords don't match. MIT Kerberos only tries
  again three times, but Heimdal loops forever (in init_creds_pw.c).

The above is a backport from Samba 4 - and the Samba 4 fix is included
in Debian's version:

http://anonscm.debian.org/cgit/pkg-samba/samba.git/commit/?id=10989431e533bd60de242dbd78c4b62c4ace7812

However, for some reason, Samba 4 has two copies of that function, one
in source4/auth/kerberos/kerberos.c (addressed by above) and one
here:

http://anonscm.debian.org/cgit/pkg-samba/samba.git/tree/source3/libads/kerberos.c

Looking at the backtrace we can see winbind calls
kerberos_kinit_password_ext, which is only present in
source3/libads/kerberos.c which seems to strongly suggest it is this bug.

At the very least it doesn't make alot of sense to apply 10989431 to only
one of the two locations in the source tree.

Jason


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

Bug#774513: /sbin/fsck.fat: problem with strange formated fat disk

2015-01-03 Thread treaki

Package: dosfstools
Version: 3.0.26-4
Severity: normal
File: /sbin/fsck.fat

Dear Maintainer,


   * What led up to the situation?
 ive checked the sd card of my mp3 player using fsck
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
$ sudo fsck -p /dev/sdb1
fsck from util-linux 2.25.2
fsck.fat 3.0.26 (2014-03-07)
/
  Bad short file name ().
  Auto-renaming it.
  Renamed to 
/dev/sdb1: 6097 files, 450807/485936 clusters
$ sudo fsck /dev/sdb1
fsck from util-linux 2.25.2
fsck.fat 3.0.26 (2014-03-07)
/
  Bad short file name ().
1) Drop file
2) Rename file
3) Auto-rename
4) Keep it
? 2
Cannot rename FAT32 root dir
/
  Bad short file name ().
1) Drop file
2) Rename file
3) Auto-rename
4) Keep it
? 2
Cannot rename FAT32 root dir
/
  Bad short file name ().
1) Drop file
2) Rename file
3) Auto-rename
4) Keep it
? 3
  Renamed to 
/dev/sdb1: 6097 files, 450807/485936 clusters
$ sudo fsck /dev/sdb1
fsck from util-linux 2.25.2
fsck.fat 3.0.26 (2014-03-07)
/dev/sdb1: 6097 files, 450807/485936 clusters
$ 


   * What was the outcome of this action?
automatic recovery wasnt successfully
   * What outcome did you expect instead?
manual recovery was strange but worked after all



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

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

Versions of packages dosfstools depends on:
ii  libc6  2.19-13

dosfstools recommends no packages.

dosfstools 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#769862: libav: target option broken - leads to wrong output files

Control: found -1 6:11-1
Control: notfound -1 11
Control: tags -1 moreinfo

On 2014-11-17 08:19:02, Vincent Pinon wrote:
 Source: libav
 Version: 11
 Severity: normal
 Tags: upstream
 
 This bug was reported upstream by someone else 1.5 year back,
 with note on how to simply fix it, but the problem persists.

Do you have a link to the issue reported upstream?

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature

Bug#739768: Confirm

2015-01-03 Thread Jason Gunthorpe

I am seeing this bug too, and I can confirm it is fixed in Ubuntu's
version. They have been shipping with this fix in trusty which works
in my environment. The latest patch from the upstream bug might be
better, but I haven't tried it.

For whatever reason upstream remains typically silent on the bug
report and proposed patch..

Here is the fix ubuntu is shipping:

--- samba-4.1.6+dfsg.orig/source3/librpc/crypto/gse_krb5.c  2014-04-29 
16:05:42.045043324 -0500
+++ samba-4.1.6+dfsg/source3/librpc/crypto/gse_krb5.c   2014-04-29 
16:05:42.041043324 -0500
@@ -414,6 +414,10 @@ static krb5_error_code fill_mem_keytab_f
if (ret) {
DEBUG(1, (__location__ : krb5_kt_start_seq_get failed (%s)\n,
  error_message(ret)));
+   if (keytab) {
+   krb5_kt_close(krbctx, keytab);
+   keytab = NULL;
+   }
goto out;
}


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

Bug#762362: flashplugin-nonfree: support request - wget failed to download a file

2015-01-03 Thread Marcel Dischinger

Package: flashplugin-nonfree
Version: 1:3.6.1
Followup-For: Bug #762362

I was able to reproduce this with a recent Knoppix Live CD. Problem is that the
SSL certificate of people.debian.org is not trusted (running wget to the URL
shows just this error). Disabling the certificate-check in the update script 
fixed
this problem (e.g., adding --no-check-certificate to line 165 of 
/usr/sbin/update-flashplugin-nonfree).
Of course this is not a solution to this problem. Not sure why the certificate
is not trusted, works fine on a Wheezy install here.

BTW, ticket #773141 is most likely a duplicate of this ticket.

Cheers,
Marcel


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

Bug#774265: fdroidserver: Unrecognised build flag at antcommands=mod-release against current fdroiddata

2015-01-03 Thread Chris

Hi,

this should be fixed with the fdroidserver version 0.3.0:

https://gitlab.com/fdroid/fdroidserver/tree/0.3.0

As a workaround the problematic .txt files can be deleted from the
/metadata folder of fdroiddata.


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

Bug#774090: emacs24: a left-click in Emacs sometimes modifies the PRIMARY selection

2015-01-03 Thread Alex Goebel

Seems to work ok with emacs24-nox. Perhaps using that would be a 
temporary workaround?



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

Bug#774484: tar: please stop recording current time when generating tar.1