date:20150331

Am 01.04.2015 um 00:20 schrieb Christoph Egger:
> Hi!
> 
> Michael Biebl  writes:
>> Am 31.03.2015 um 19:07 schrieb Michael Biebl:
>>> Am 31.03.2015 um 17:45 schrieb Christoph Egger:
>>>
>>> That looks odd: While the fsck is running, a reboot was scheduled.
>>> Did you hit CTRL+ALT+DEL?
>>>
>>
>> Or is this caused by
>>
>> Job local-fs.target/sta[   12.366051] Copyright (C) 2004 MontaVista
>> Software - IPMI Powerdown via sys_reboot.
> 
> I just let it do it's thing waiting. And I had this behaviour bevore
> installing ipmi-foo

Could you blacklist the ipmi_si driver, just to be sure?

That aside, I wonder if it's related to the use of f2fs for /

[   12.306905] systemd-fsck[171]: Executing: /lib/systemd/systemd-fsck
[   12.332491] systemd-fsck[171]: Info: Fix the reported corruption.

systemd-fsck[171]: Error: Not available on mounted device!

That somehow looks suspicious.

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#779377: RFS: classified-ads/0.03-1 / ITP

2015-03-31 Thread Tobias Frost

Control: owner -1 !
Control: tags -1 pending
# (above means: I will sponsor you)

Am Samstag, den 28.03.2015, 23:34 +0200 schrieb Antti Järvinen:
> Tobias Frost writes:
>  > Am Donnerstag, den 26.03.2015, 01:19 +0200 schrieb Antti Järvinen:
>  > >   E: classified-ads source: 
> depends-on-build-essential-package-without-using-version dpkg-dev
>  > >   so the version numbers remain. 
>  > 
>  > You probably do not need the dpkg-dev dependency at all, do you?
> 
> I was under impression that dpkg-shlibdeps comes from
> dpkg-dev. pbuilder seems to happily build without and lintian is not
> complaining -> away it goes..

dpkg-dev pulled in by build-essential and therefore you do not need to
exclitly state it, except if you have a version constraint. (need a
minimum version of dpkg-dev; (read the description on the above quoted
lintian error; this also points you to Policy §4.2)

>  > You need to add -b debian then to VCS-Git (Refer to Policy 5.6.26)
> 
> Yes.
> 
>  > Well, you should not copy the license *text* into d/copyright, but you
>  > still need to put the license *grant* into it. 
>  > 
>  > The license grant is the header of your source files. So, you'd write
>  > 
>  > License: LGPL-2.1+
>  >  Classified Ads is free software; you can redistribute it and/or
> ...
> 
> Ok, I'll try restructuring. Software aside, this seems like
> complexiest thing ever..

No doubt, Copyright is complex; and this also very usual that sponsorees
don't get it right the few first times :)
But looking at the repository it looks fine now. (Though I will do a
final copyright check just before uploading -- because this topic is
complex and it is easy to overlook something.)

> 
>  > 
>  > > general:
>  > > - Huge high-resolution bitmaps removed from source
>  > 
>  > Not checked in the code, but this raises a flag: In Debian you need to
>  > have the source in the preferred form for modifications and for images
>  > this is the _best_ resolution.
>  > (And as said earlier, you need to compute the lower resolution at build
>  > time)   
> 
> Bitmaps are not modified at build-time, only wrapped into qt-format
> resource file. The binary .deb contains actually exactly same bits
> in bitmaps that are in orig.tar.gz. I was thinking about keeping the
> high-resolution gimp files in upstream repo anyway but not in source
> package as there is no transform done..

No, you've got me wrong... 
In Debian we build *everything* from source.
Spoken in source code analogy: Your high resolution file is the source
(like a cpp file) code, the bitmap is the object code: As like you need
to compile your cpp file, you must regenerate the bitmap during the
build from the highres image. 
Debian sees the (high-res image) as part of the source code, the
preferred form of the source actually. So you should include it into
your tarball and create the actual bitmaps at build-time.

>  > Did not check the code, but you also ensure that the RAM is not swapped
>  > out?
> 
> Yes and no. For actual key handling the task is outsourced to OpenSSL
> and I hope it is doing the Right Thing (starting from 1.0.1g it
> actually might, seems..). For content no, it is all over
> the place and goes through qt code also so I think easiest would be to
> flag the whole process out of swap if possible. After the heartbleed
> episode I marked a future development task of moving all
> key-handling into separate process, away from process where networking
> happens. ..the paranoid operators will have no swap or encrypted swap. 
> ..but I've tried to keep things simple also for end-users. Here you
> get automatic content signing+encryption always whenever possible. 
> Still I wouldn't like to start adding a manpage section about setting 
> up encrypted swap. 

Fine with me, just wanted to know if you put some thoughts into this
aspect.

> 
>  > Regarding my question regarding your plans for involvement into Debian
>  > -- Do you want to share your thoughts about this?
> 
> I've been trying to get involved into group things, as I was thinking
> this is kind of soft-landing into debian process. I've been in
> discussion with openssl team but then received no definite "yes/no"
> answer from them, nor any concrete work items to start working
> with. In the meantime I've been trying to do reviews on tickets that
> no-one has yet checked. 

Yes I saw it; thank you a lot.


> I noticed you had been marketing qemuctl in
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780270 so if I say that
> I know qt and qemu in advance (I do) and after half-hour study about
> understand the qemuctl behaviour, you think I could ITA this package?

Sure, just follow the ITa procedure. (I will also sponsor you on this)

> .. the part that I'm worried about is the mechanics of actual
> releasing (done in collab-maint?) so that I won't wreck the whole
> distro.. 

Its just a git repository ;-) No big risk to ruin everything.
You could also move the repository somewhere else, if you don't like
col

Bug#781639: apticron: email contains "E: There are problems" error when some packages put on hold

2015-03-31 Thread Vincas Dargis

Package: apticron
Version: 1.1.55
Severity: normal

Dear Maintainer,

After putting some postgresql packages (from pgdg repository) on hold to delay 
upgrade,
I've started receiving apticron emails with this error message:
"E: There are problems and -y was used without --force-yes"

Please take a look at "before" and "after" email content attached, one before 
performing 
apt-mark hold and one after.

I do no see any real problems while performing actual updates or upgrades, but 
apticron 
is upset about something.

Thanks.



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

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

Versions of packages apticron depends on:
ii  apt 0.9.7.9+deb7u7
ii  bsd-mailx [mailx]   8.1.2-0.2006cvs-1+deb7u1
ii  bzip2   1.0.6-4
ii  cron3.0pl1-124
ii  debconf [debconf-2.0]   1.5.49
ii  dpkg1.16.15
ii  heirloom-mailx [mailx]  12.5-2+deb7u1
ii  ucf 3.0025+nmu3

Versions of packages apticron recommends:
ii  apt-listchanges  2.85.11
ii  iproute  20120521-3+b3

apticron suggests no packages.

-- debconf information:
  apticron/notification: root


apticron report [Mon, 30 Mar 2015 23:59:07 +0300]


apticron has detected that some packages need upgrading on:

eterna 
[ 192.168.1.25 ]

The following packages are currently pending an upgrade:

liblwgeom-2.1.6 2.1.6+dfsg-1~exp1.pgdg70+1
postgresql-9.4-postgis-2.1 2.1.6+dfsg-1~exp1.pgdg70+1
postgresql-9.4-postgis-scripts 2.1.6+dfsg-1~exp1.pgdg70+1
E: There are problems and -y was used without --force-yes



Package Details:

Reading changelogs...
--- Changes for postgis (postgresql-9.4-postgis-2.1 
postgresql-9.4-postgis-scripts) ---
postgis (2.1.6+dfsg-1~exp1.pgdg70+1) wheezy-pgdg; urgency=low

  * Rebuild for wheezy-pgdg (jenkins-postgis-source-distribution=wheezy-
91, git revision bf135e6df0dd0573448a37994191ff1f3a7d699f)

 -- apt.postgresql.org autobuilder   Sun, 22 Mar 2015 20:55:09 
+0100

postgis (2.1.6+dfsg-1~exp1) experimental; urgency=medium

  * New upstream release.
  * Skip tests on mipsel too, due to persistent buildd issues.
  * Use uscan repacking to exclude CITE tests from upstream source.
  * Update patches for new upstream release.
  * Generate pom.xml before running maven.
  * Update symbols for liblwgeom-2.1.6.

 -- Bas Couwenberg   Sat, 21 Mar 2015 15:49:02 +0100

postgis (2.1.5+dfsg-1~exp2) experimental; urgency=medium

  * Update symbols for liblwgeom-2.1.5.
  * Update Homepage URL from postgis.refractions.net to postgis.net.
  * Update my email to use @debian.org address.
  * Add build dependency on openjdk-7-jdk | java7-sdk required to build
libpostgis-java. OpenJDK 7 is not yet available on GNU/Hurd.
  * GNU/Hurd doesn't implement semaphores; skip regress tests on hurd-*.

 -- Bas Couwenberg   Sun, 08 Feb 2015 21:41:31 +0100



You can perform the upgrade by issuing the command:

apt-get dist-upgrade

as root on eterna



INFO: the following packages are on hold, then will not be upgraded even if
they have been present in the upgrading candidates list:

 postgresql-9.4-postgis-2.1 postgresql-9.4-postgis-scripts

--
apticron




apticron report [Sun, 29 Mar 2015 23:59:10 +0300]


apticron has detected that some packages need upgrading on:

eterna 
[ 192.168.1.25 ]

The following packages are currently pending an upgrade:

libapache2-mod-php5 5.4.39-0+deb7u2
libfreexl1 1.0.0b-1+deb7u1
liblwgeom-2.1.6 2.1.6+dfsg-1~exp1.pgdg70+1
php5-common 5.4.39-0+deb7u2
postgresql-9.4-postgis-2.1 2.1.6+dfsg-1~exp1.pgdg70+1
postgresql-9.4-postgis-scripts 2.1.6+dfsg-1~exp1.pgdg70+1



Package Details:

Reading changelogs...
--- Changes for freexl (libfreexl1) ---
freexl (1.0.0b-1+deb7u1) wheezy-security; urgency=high

  * Add myself to Uploaders.
  * Update Vcs-* URLs for move to pkg-grass & wheezy branch for Vcs-Git. 
  * Add patch to fix vulnerabilities identified by American Fuzzy Lop.
(closes: #781228) 

 -- Bas Couwenberg   Thu, 26 Mar 2015 11:46:40 +0100

--- Changes for php5 (libapache2-mod-php5 php5-common) ---
php5 (5.4.39-0+deb7u2) wheezy-security; urgency=medium

  * Fix segfault when using SoapClient::__setSoapHeader (Closes: #781125)

 -- Ondřej Sur

Bug#618426: transmission: Stops torrents which have no tracker

2015-03-31 Thread Tony Houghton


On 31/03/15 22:36, Sandro Tosi wrote:

Hello,
I suspect this has been fixed a long ago, can you confim?


Sorry, I've been using rtorrent instead for the last few years.


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

Bug#781274: unblock: owncloud/7.0.4+dfsg-3

2015-03-31 Thread David Prévot

Control: retitle -1 unblock: owncloud/7.0.4+dfsg-3

Hi,

On Thu, Mar 26, 2015 at 03:26:37PM -0400, David Prévot wrote:

> Please pre-approve an unblock for the owncloud package

Let’s make it an approval request instead: I felt uneasy letting a
package with known security issues (and fixes) in unstable, so I went
ahead with the upload. It should save us a hop if you agree with the
request, and I’ll make sure to prepare a -4 version in a timely manner
if you disagree with any of the proposed changes.

unblock owncloud/7.0.4+dfsg-3

Thanks in advance.

Regards

P.-S.: Original request (without debdiff)

> It cherry-picks three security fixes from the recently released 7.0.5
> version (already in experimental):
> 
> owncloud (7.0.4+dfsg-3) unstable; urgency=medium
> 
>   * Add gbp config file to follow the jessie branch
>   * Backport security fixes from 7.0.5:
> - Multiple stored XSS in "contacts" application [OC-SA-2015-001]
> - Multiple stored XSS in "documents" application [OC-SA-2015-002]
> - Bypass of file blacklist [OC-SA-2015-004]
>   * Run upgrade script with sudo as www-data user
>   * Depend on php5-cli (it is actually used in postinst)
> 
>  -- David Prévot   Wed, 25 Mar 2015 16:20:32 -0400
> 
> I’d also like to shim in two other small changes:
> - the upgrade script should be run as the same user as the installed
>   data, i.e., www-data by default, instead of root: this recommendation
>   has recently been enforced upstream since the upgrade process may
>   touch data files on top of the potential database changes;
> - since the php CLI is called during postinst, php5-cli should be a
>   dependency instead of a recommendation (the README.Debian change just
>   drops the now useless explanation why php5-cli was recommended).
> 
> The attached debdiff stripes away the webodf.js changes from the
> cherry-picked commit from upstream: this minified JavaScript files is
> anyway regenerated at build time and is thus not the file included in
> the actual binary package.


signature.asc
Description: Digital signature

Bug#767040: Superblock time check causes problems for fsck in initramfs

2015-03-31 Thread Janis Hamme

On Tue, 31 Mar 2015 03:14:53 +0100 Ben Hutchings 
wrote:
> By the way, Lennart Poettering told me that other distributions have
> done that, though I haven't checked whether it is done with a
> configuration file or a patch to the code.
>
> > it wouldn't be better to just skip the fsck of / (and /usr, if
separate).
> > For that, initramfs-tools could create a flag file for / and /usr in
> > /run and we'd update systemd-fsck-root.service and systemd-fsck@.service
> > and add a Condition= which checks for that flag file.
> > (suggestion, let's call them /run/fsck/root and /run/fsck/usr)
> >
> >
> > The sysv init scripts could do something similar (therefore CCed).
>
> Not easily - they currently rely on the fsck binary to iterate over all
> filesystems, and don't have any logic to do so themselves. (That's why
> initramfs-tools still doesn't mount /usr if it's going to hand over to
> sysvinit.)

Actually it's not so difficult, as long as the following condition
holds: filesystems that are mounted before handing over to the init
system have been checked before. Since initramfs-tools are now
responsible for checking partitions that are mounted prior to init,
duplicate fsck's from sysvinit and systemd should be consequently avoided.

Root partition checking could be disabled in /etc/init.d/checkroot.sh
and systemd-fsck-root.service should be masked.
For all other partitions the fsck tool has the option "-M" to ignore
mounted file systems. It could be applied to /etc/init.d/checkfs.sh and
systemd-fsck internally.

Janis

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

Bug#753442: debootstrap: host's /run/shm gets unmounted after debootstrap run

2015-03-31 Thread Daniel Reichelt

Hi,

Commit a1d5ddea5b fixed this.


http://anonscm.debian.org/cgit/d-i/debootstrap.git/commit/?id=a1d5ddea5b7db00548173cee8236aaad61cf5961


cu
Daniel


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

Bug#780259: perl: please make the output of Pod::Man reproducible

2015-03-31 Thread Russ Allbery

Niko Tyni  writes:

> A downside of this is that POD_MAN_DATE will affect all the manual pages
> generated by Pod::Man and remove the potentially useful indications of
> their recency. I can't really see how to avoid that, but possibly we
> should set POD_MAN_DATE to something that isn't really a timestamp at
> all, so as not to mislead readers. Given the check for a true value in
> devise_date(), an empty string isn't an option, but a space or 'N/A'
> come to mind.

Oh, ugh, I'm sorry.  Both of the relevant truth checks should just be
defined(); that's a bug.  It's entirely valid to want to omit that heading
entirely, and --date '' or POD_MAN_DATE='' should do the right thing.  (As
should --date 0, for that matter.)  I'll fix that in the next upstream
release.

-- 
Russ Allbery (r...@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#780259: perl: please make the output of Pod::Man reproducible

2015-03-31 Thread Russ Allbery

Axel Beckert  writes:
> Chris Lamb wrote:

>> While working on the "reproducible builds" effort [1], we have noticed
>> that Pod::Man generates output that varies depending on the current
>> timezone.

> While I appreciate the reproducible builds effort a lot, I don't think
> hardcoding UTC instead of the local timezone is suitable for general
> use.

> The patch is fine for building packages in Debian -- but I think,
> users using Debian's Pod::Man for their own projects will partially be
> confused by UTC times, especially those users not living in Europe or
> Africa, i.e. close to the GMT timezone.

Sorry, I was going to respond to this and didn't get to it.

As upstream maintainer of Pod::Man, I'm inclined to take this patch.  Some
of this is because I don't think there's a clearly right answer, and I
have a personal preference for using UTC for things like this.  Living on
the west coast of the US myself, my own blog posts (which use UTC) are
frequently dated in the "future" by local time, and I don't think it's
that big of a deal.

I do understand the concern over user confusion, but I also think it's
very valuable for pod2man to produce consistent output when given the same
input file, as a general principle of software design, regardless of local
variations like time zone settings.  For better or worse, the only
generally-agreed-upon reproducible date strategy is to use UTC.

It's trivial for people to override this behavior with the --date option
to pod2man or similar settings to the Pod::Man constructor if they don't
like the default, and I'll clearly document this in the package
documentation.  Since this is used only to generate a date, not a
timestamp, I think the maximum "error" is for the date to be off by about
14 hours, which, given how this software is used, is rarely going to be
significant.

-- 
Russ Allbery (r...@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#781638: openscad: Openscad places build time into compiled output

2015-03-31 Thread David Eccles (gringer)

Package: openscad
Version: 2014.03+dfsg-1
Severity: minor

Dear Maintainer,

OpenSCAD fails reproducibility testing due to using the build date in the
compiled output:

https://reproducible.debian.net/rb-pkg/unstable/amd64/openscad.html

A patch to remove use of the offending '__DATE__' macro is attached.



-- Package-specific info:
Output of /usr/share/bug/openscad:
$ glxinfo |grep 'OpenGL .* string:'
OpenGL vendor string: nouveau
OpenGL renderer string: Gallium 0.4 on NVA8
OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.4.2
OpenGL core profile shading language version string: 3.30
OpenGL version string: 3.0 Mesa 10.4.2
OpenGL shading language version string: 1.30
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 10.4.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.0

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

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

Versions of packages openscad depends on:
ii  libboost-filesystem1.55.0   1.55.0+dfsg-3
ii  libboost-program-options1.55.0  1.55.0+dfsg-3
ii  libboost-regex1.55.01.55.0+dfsg-3
ii  libboost-system1.55.0   1.55.0+dfsg-3
ii  libboost-thread1.55.0   1.55.0+dfsg-3
ii  libc6   2.19-15
ii  libcgal10   4.5-2
ii  libgcc1 1:4.9.2-10
ii  libgl1-mesa-glx [libgl1]10.4.2-2
ii  libglew1.10 1.10.0-3
ii  libglib2.0-02.42.1-1
ii  libglu1-mesa [libglu1]  9.0.0-2
ii  libgmp102:6.0.0+dfsg-6
ii  libmpfr43.1.2-3
ii  libopencsg1 1.3.2-2+b1
ii  libqt4-opengl   4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqtcore4  4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqtgui4   4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libstdc++6  4.9.2-10
ii  libx11-62:1.6.2-3

Versions of packages openscad recommends:
pn  openscad-mcad  

Versions of packages openscad suggests:
pn  geomview  
ii  librecad  2.0.4-1
pn  meshlab   
pn  openscad-testing  

-- no debconf information
diff -u5 -r openscad-2014.03+dfsg/src/PlatformUtils.cc openscad-2014.03+notimestamp/src/PlatformUtils.cc
--- openscad-2014.03+dfsg/src/PlatformUtils.cc	2014-03-11 08:01:31.0 +1300
+++ openscad-2014.03+notimestamp/src/PlatformUtils.cc	2015-04-01 16:15:45.641731816 +1300
@@ -145,11 +145,11 @@
 #endif // ENABLE_CGAL
 
 	const char *env_path = getenv("OPENSCADPATH");
 	
 	s << "OpenSCAD Version: " << TOSTRING(OPENSCAD_VERSION)
-  << "\nCompiler, build date: " << compiler_info << ", " << __DATE__
+  << "\nCompiler: " << compiler_info
 	  << "\nBoost version: " << BOOST_LIB_VERSION
 	  << "\nEigen version: " << EIGEN_WORLD_VERSION << "." << EIGEN_MAJOR_VERSION << "." << EIGEN_MINOR_VERSION
 	  << "\nCGAL version, kernels: " << TOSTRING(CGAL_VERSION) << ", " << cgal_3d_kernel << ", " << cgal_2d_kernel << ", " << cgal_2d_kernelEx
 	  << "\nOpenCSG version: " << OPENCSG_VERSION_STRING
 	  << "\nQt version: " << qtVersion

Bug#774744: ITP: obs -- Open Broadcast Software

2015-03-31 Thread Jason Pleau

Hi

On Wed, 07 Jan 2015 02:57:45 +0100 =?utf-8?q?Carl_F=C3=BCrstenberg?=
 wrote:
> Package: wnpp
> Severity: wishlist
> Owner: "Carl FÃ¼rstenberg" 
> 
> * Package name: obs
>   Version : 0.7.2
>   Upstream Author : Hugh Bailey 
> * URL : https://obsproject.com/
> * License : GPL
>   Programming Lang: C, C++
>   Description : Open Broadcast Software
> 
> a rewrite of what was formerly known as "Open Broadcaster Software", 
> software originally designed for recording and streaming live
> video content, efficiently. 
> 
> 

Just wondering if you had started working on the packaging for
obs-studio ? The Linux version is now officially out ! :)

I am currently using OBS to stream to twitch using the source package
available at upstream's PPA:
https://launchpad.net/~obsproject/+archive/ubuntu/obs-studio. I rebuilt
the package myself though ;)

But I would prefer using the future official Debian package for this! I
think libobs would need its own package for example, the ubuntu ppa
packs everything into a single big binary package.

Hopefully we can get obs-studio in Debian in a near future !

Cheers

-- 
Jason Pleau

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

Bug#778016: mstflint: ftbfs with GCC-5

2015-03-31 Thread Steve Langasek

Package: mstflint
Version: 3.7.0+1.18.gcdb9f80-3
Followup-For: Bug #778016
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu vivid ubuntu-patch

Hi Ana,

In addition to failing to build under gcc 5, mstflint also fails to build
under gcc 4.9 with -O3 optimization.  As a result this package was failing
to build in Ubuntu on ppc64el (despite having had a patch included to
support ppc64el builds), where -O3 is used by default, and so I've prepared
the attached patch to fix the build.

This patch has been submitted upstream to Mohammed Sawalha
.

Hope that helps,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru mstflint-3.7.0+1.18.gcdb9f80/debian/changelog mstflint-3.7.0+1.18.gcdb9f80/debian/changelog
diff -Nru mstflint-3.7.0+1.18.gcdb9f80/debian/patches/series mstflint-3.7.0+1.18.gcdb9f80/debian/patches/series
--- mstflint-3.7.0+1.18.gcdb9f80/debian/patches/series	1969-12-31 16:00:00.0 -0800
+++ mstflint-3.7.0+1.18.gcdb9f80/debian/patches/series	2015-03-31 19:19:20.0 -0700
@@ -0,0 +1 @@
+uninitialized-variables-O3.patch
diff -Nru mstflint-3.7.0+1.18.gcdb9f80/debian/patches/uninitialized-variables-O3.patch mstflint-3.7.0+1.18.gcdb9f80/debian/patches/uninitialized-variables-O3.patch
--- mstflint-3.7.0+1.18.gcdb9f80/debian/patches/uninitialized-variables-O3.patch	1969-12-31 16:00:00.0 -0800
+++ mstflint-3.7.0+1.18.gcdb9f80/debian/patches/uninitialized-variables-O3.patch	2015-03-31 19:19:20.0 -0700
@@ -0,0 +1,82 @@
+Description: Fix uninitialized variables when building with -O3
+ When optimizing with -O3, gcc detects possible use-before-initialization
+ bugs in mlxfwops/lib/.  These are false positives but defy
+ compiler analysis, and it's better to be safe anyway so initialize the
+ variables explicitly.
+Author: Steve Langasek 
+Bug-Ubuntu: https://launchpad.net/bugs/1367842
+
+Index: mstflint-3.7.0+1.18.gcdb9f80/mlxfwops/lib/fw_ops.cpp
+===
+--- mstflint-3.7.0+1.18.gcdb9f80.orig/mlxfwops/lib/fw_ops.cpp
 mstflint-3.7.0+1.18.gcdb9f80/mlxfwops/lib/fw_ops.cpp
+@@ -623,8 +623,8 @@ bool FwOperations::writeImage(ProgressCa
+ 
+ bool FwOperations::ModifyImageFile(const char *fimage, u_int32_t addr, void *data, int cnt)
+ {
+-int file_size;
+-u_int8_t * file_data;
++int file_size = 0;
++u_int8_t * file_data = NULL;
+ 
+ if (!ReadImageFile(fimage, file_data, file_size, addr + cnt)) {
+ return false;
+Index: mstflint-3.7.0+1.18.gcdb9f80/mlxfwops/lib/fs2_ops.cpp
+===
+--- mstflint-3.7.0+1.18.gcdb9f80.orig/mlxfwops/lib/fs2_ops.cpp
 mstflint-3.7.0+1.18.gcdb9f80/mlxfwops/lib/fs2_ops.cpp
+@@ -452,8 +452,8 @@ bool Fs2Operations::Fs2Verify(VerifyCall
+ 
+  // Verify the images:
+  for (u_int32_t i = 0; i < cntx_image_num; i++) {
+- bool  fs_en;
+- u_int32_t log2chunk_size;
++ bool  fs_en = false;
++ u_int32_t log2chunk_size = 0;
+  u_int32_t buff[FS2_BOOT_START / 4];
+ 
+  _ioAccess->get_image_crc().clear();
+Index: mstflint-3.7.0+1.18.gcdb9f80/mlxfwops/lib/fs3_ops.cpp
+===
+--- mstflint-3.7.0+1.18.gcdb9f80.orig/mlxfwops/lib/fs3_ops.cpp
 mstflint-3.7.0+1.18.gcdb9f80/mlxfwops/lib/fs3_ops.cpp
+@@ -975,7 +975,7 @@ bool Fs3Operations::FwSetVPD(char* vpdFi
+ bool Fs3Operations::GetModifiedSectionInfo(fs3_section_t sectionType, fs3_section_t nextSectionType, u_int32_t &newSectAddr,
+ fs3_section_t &SectToPut, u_int32_t &oldSectSize)
+ {
+-struct toc_info *curr_itoc;
++struct toc_info *curr_itoc = NULL;
+ if (Fs3GetItocInfo(_fs3ImgInfo.tocArr, _fs3ImgInfo.numOfItocs, sectionType, curr_itoc) ||
+ Fs3GetItocInfo(_fs3ImgInfo.tocArr, _fs3ImgInfo.numOfItocs, nextSectionType, curr_itoc)) {
+ newSectAddr = curr_itoc->toc_entry.flash_addr << 2;
+@@ -1024,9 +1024,10 @@ bool Fs3Operations::UpdateItocAfterInser
+ 
+ if (toAdd) {
+ if (isReplacement) {
+-struct toc_info *curr_itoc;
++struct toc_info *curr_itoc = NULL;
+ u_int32_t sectSize;
+-Fs3GetItocInfo(_fs3ImgInfo.tocArr, _fs3ImgInfo.numOfItocs, sectionType, curr_itoc);
++if (!Fs3GetItocInfo(_fs3ImgInfo.tocArr, _fs3ImgInfo.numOfItocs, sectionType, curr_itoc))
++return false;
+ sectSize = curr_itoc->toc_entry.size * 4;
+ shiftSize = (removedOrNewSectSize > sectSize) ? removedOrNewSectSize - sectSize : 0;
+ } else {
+@@ -1404,7 +1405,7 @@ bool Fs3Operations::Fs3ReburnItocSection
+ //add callback if we want info during section update
+ bool  Fs3Oper

Bug#781637: unblock: apt-build/0.12.45

2015-03-31 Thread Axel Beckert

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

Dear Release Team,

I just did a QA upload of apt-build/0.12.45.

The upload fixes https://bugs.debian.org/659015 which recently has
been bumped to RC severity.

>From the changelog entry:

 * Use per-repo "deb [trusted=yes] ..." instead of global "-o
   Apt::Get::AllowUnauthenticated=true". (Closes: #659015)

This required multiple changes:

   + Bump versioned apt dependency to 0.8.16~exp3 for trusted=yes

the option trusted=yes in sources.list files has been introduced with
this apt version, hence apt-build won't work with earlier versions
anymore.

   + Automatically add [trusted=yes] to existing generated file
 /etc/apt/sources.list.d/apt-build.list in postinst.

First tests showed that the obvious way to fix it only fixes it for
new installations of apt-build, but with an upgrade, -o
Apt::Get::AllowUnauthenticated=true is no more used, but [trusted=yes]
has not been added. So an additional sed call was needed in postinst.

   + Use "grep -F" instead of "grep" to search for the whole "deb" line
 in postinst to avoid the brackets around trusted=yes being parsed as
 character class.

Previous postinst used plain grep to check for existing apt-build
sources.list entries. But since the new sources.list entry contains
square brackets, "grep -F" instead of "grep" is required.

 * Update Vcs-* URLs to current canonical forms and use collab-maint
   repository instead of the apt-build project one's while being under QA
   maintenance to allow write access to all DDs.

I left the original Vcs-* headers in there as comments, but since
neither me nor most QA uploads doing DDs have write-permissions to the
apt-build project's Git repository and I didn't want to stop using a
Vcs, I created a copy of the original repo under collab-maint and let
the Vcs-* headers point there -- with the current canonical forms.

Full source debdiff:

diff -Nru apt-build-0.12.44/apt-build apt-build-0.12.45/apt-build
--- apt-build-0.12.44/apt-build 2012-04-11 23:11:12.0 +0200
+++ apt-build-0.12.45/apt-build 2015-04-01 00:28:20.0 +0200
@@ -582,8 +582,7 @@
 if(@pkgs && !($conf->build_only))
 {
update() if $conf->update;
-   system($conf->apt_get . " -t apt-build @apt_args \\
--o Apt::Get::AllowUnauthenticated=true install @pkglist");
+   system($conf->apt_get . " -t apt-build @apt_args install @pkglist");
wait;
 }
 return 1;
diff -Nru apt-build-0.12.44/debian/changelog apt-build-0.12.45/debian/changelog
--- apt-build-0.12.44/debian/changelog  2012-11-27 18:43:26.0 +0100
+++ apt-build-0.12.45/debian/changelog  2015-04-01 02:56:35.0 +0200
@@ -1,3 +1,20 @@
+apt-build (0.12.45) unstable; urgency=medium
+
+  * QA upload
+  * Use per-repo "deb [trusted=yes] ..." instead of global "-o
+Apt::Get::AllowUnauthenticated=true". (Closes: #659015)
++ Bump versioned apt dependency to 0.8.16~exp3 for trusted=yes
++ Automatically add [trusted=yes] to existing generated file
+  /etc/apt/sources.list.d/apt-build.list in postinst.
++ Use "grep -F" instead of "grep" to search for the whole "deb" line
+  in postinst to avoid the brackets around trusted=yes being parsed as
+  character class.
+  * Update Vcs-* URLs to current canonical forms and use collab-maint
+repository instead of the apt-build project one's while being under QA
+maintenance to allow write access to all DDs.
+
+ -- Axel Beckert   Wed, 01 Apr 2015 02:42:19 +0200
+
 apt-build (0.12.44) unstable; urgency=low
 
   * QA upload.
diff -Nru apt-build-0.12.44/debian/config apt-build-0.12.45/debian/config
--- apt-build-0.12.44/debian/config 2012-10-15 23:46:03.0 +0200
+++ apt-build-0.12.45/debian/config 2015-04-01 00:28:20.0 +0200
@@ -88,7 +88,7 @@
   # run loop to prevent errors if some sources does not exist
   for source in "$sourceslist" "$sourcesparts"*.list ; do
 if [ -e "$source" ] ; then
-  if grep -Eq "^[[:space:]]*deb file:$repository_dir apt-build main" 
"$source" ; then
+  if grep -Eq "^[[:space:]]*deb \[trusted=yes\] file:$repository_dir 
apt-build main" "$source" ; then
 db_set apt-build/add_to_sourceslist "true"
 break
   fi
diff -Nru apt-build-0.12.44/debian/control apt-build-0.12.45/debian/control
--- apt-build-0.12.44/debian/control2012-04-11 23:11:12.0 +0200
+++ apt-build-0.12.45/debian/control2015-04-01 01:12:04.0 +0200
@@ -4,12 +4,14 @@
 Maintainer: Debian QA Group 
 Build-Depends: debhelper (>= 9), po4a, po-debconf
 Standards-Version: 3.9.3
-Vcs-Git: git://git.debian.org/git/apt-build/apt-build.git
-Vcs-Browser: http://git.debian.org/?p=apt-build/apt-build.git
+#Vcs-Git: git://anonscm.debian.org/apt-build/apt-build.git
+#Vcs-Browser: https://anonscm.debian.org/cgit/apt-build/apt-build.git
+Vcs-Git: git://anonscm.debian.org/collab-maint/apt-build.git
+Vcs-Browser: https:

Bug#781636: [doxygen] SVG function caller graph incorrectly includes a $ character instead of relative path in xlink::href

2015-03-31 Thread LeJacq, Jean Pierre

Package: doxygen
Version: 1.8.8-5
Severity: normal

--- Please enter the report below this line. ---

Generated function caller graphs in SVG have an invalid xlink:href. It starts 
the href with a '$' character instead of the relative path.

An example is:



This should be:



--- System information. ---
Architecture: amd64
Kernel:   Linux 3.18.0-trunk-amd64

Debian Release: 8.0
  800 unstableftp.us.debian.org 
  500 testing ftp.us.debian.org 
  500 stable  dl.google.com 
  100 experimentalftp.us.debian.org 

--- Package information. ---
Depends   (Version) | Installed
===-+-=
libc6 (>= 2.14) | 
libgcc1(>= 1:4.1.1) | 
libstdc++6   (>= 4.1.1) | 


Package's Recommends field is empty.

Suggests   (Version) | Installed
-+-===
doxygen-latex| 
doxygen-doc  | 1.8.8-5
doxygen-gui  | 1.8.8-5
graphviz | 2.38.0-7

-- 
JP


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

Bug#781635: yum-utils: Should recommend python-lzma

2015-03-31 Thread Clint Byrum

Package: yum-utils
Version: 1.1.31-2
Severity: normal

Dear Maintainer,

Hi! While using yumdownloader to try and build Fedora chroots, it became
clear that I was missing a library. Fedora 21 and presumably others use
xz compression from python-lzma. But this library is not suggested or
recommended in yumdownloader. I'd suggest that it should be a
"recommends" since the program allows for it to not be present.

Thanks!


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

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

Versions of packages yum-utils depends on:
ii  python 2.7.5-5ubuntu3
ii  python-iniparse0.4-2.1build1
ii  python-libxml2 2.9.1+dfsg1-3ubuntu4.4
ii  python-rpm 4.11.1-3ubuntu0.1
ii  python-urlgrabber  3.9.1-4ubuntu3.14.04.1
pn  python:any 
ii  yum3.4.3-2ubuntu1

yum-utils recommends no packages.

yum-utils 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#781562: [preapproval] unblock: vim/2:7.4.488-7

2015-03-31 Thread James McCoy

Control: tags -1 - moreinfo
Control: retitle -1 unblock: vim/2:7.4.488-7

On Tue, Mar 31, 2015 at 07:39:03AM +0100, Adam D. Barratt wrote:
> On 2015-03-31 2:39, James McCoy wrote:
> >Please unblock package vim
> >
> >The 'linebreak' patch in this upload addresses a very distracting bug
> >where the visual formatting of blocks of text changes every time the
> >user starts insert mode using Vim's c command.
> >
> >The NetRW patch fixes an error that will make any callers of the
> >function fail.
> 
> Please go ahead, and remove the "moreinfo" tag once the package is in
> unstable.

Uploaded.  Thanks.

-- 
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy 


signature.asc
Description: Digital signature

Bug#659015: apt-build disables apt's signature verification

2015-03-31 Thread Axel Beckert

Control: tag -1 + pending

Hi,

Ansgar Burchardt wrote:
> Axel Beckert  writes:
> > I've though observed two possibly minor issues with it:
> >
> > * An existing /etc/apt/sources.list.d/apt-build.list is not updated to
> >   add "[trusted=yes]".
> 
> Could probably be added in postinst (apt-build.list is not a conffile),
> e.g. something like
> 
>   sed -i 's/^deb file:/deb [trusted=yes] file:/'
> 
> or something more strict to make sure it doesn't touch other
> repositories.

Thanks for that idea and note about not being a conffile.

> > * Upon purge and (re)installation, I had the "deb" line twice in
> >   /etc/apt/sources.list.d/apt-build.list and it's not clear to me why.
> 
> The filename is generated differently in postinst and postrm:

That wasn't the issue, but using grep without -F to search for the
whole line -- which now contains brackets and they have special
meanings in grep basic regular expressions. So adding -F to the
according grep call fixes that.

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


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

Bug#781634: upower: Power incorrectly reported as 0% after hibernate (leads to re-hibernate if on battery power)

2015-03-31 Thread Neil Pilgrim

Package: upower
Version: 0.99.1-3.1
Severity: important

Dear Maintainer,

Using cinnamon desktop, I can hibernate and resume from hibernation with no
trouble if plugged-in. It does not need to remain plugged-in between, I
believe, it just needs to be plugged-in when rebooted to resume.

If the computer is unplugged when resuming from hibernation, then it claims
that the battery is completely discharged (0%) including showing a popup (both
probably being cinnamon-specific, but presumably from upower infrastructure)
and proceeds to automatically hibernate. I do not believe this is a hardware
issue since I have tested this from a near-full-charged state and it reports
uniquely 0%, and works fine if plugged in when resuming, as above.

I have experimented with 'upower -m', and this causes the unplugged resume-
from-hibernate to not automatically re-hibernate, but the battery does indicate
as being at 0%. Upon inserting the power, the number jumps to the 'real'
number, eg. 98%.

I am happy to run more tests; please let me know if I can help any further.

This quite limits the portability of my laptop, as I am tethered to a socket if
I want to be able to resume from hibernation - and need to 'look ahead' as I'm
not currently aware of how to avoid resuming instead of rebooting, and
obviously unsaved work may be 'locked away' in the repeatedly re-hibernating
machine.

--
Neil



-- 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_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages upower depends on:
ii  dbus   1.8.16-1
ii  libc6  2.19-15
ii  libdbus-1-31.8.16-1
ii  libdbus-glib-1-2   0.102-1
ii  libglib2.0-0   2.42.1-1
ii  libgudev-1.0-0 215-12
ii  libimobiledevice4  1.1.6+dfsg-3.1
ii  libplist2  1.11-3
ii  libupower-glib30.99.1-3.1
ii  libusb-1.0-0   2:1.0.19-1
ii  udev   215-12

Versions of packages upower recommends:
ii  policykit-1  0.105-8

upower 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#781622: RFS: opentyrian/2.1.20130907-1 [ITP]

2015-03-31 Thread Dmitry Smirnov

On Tue, 31 Mar 2015 19:35:12 Etienne Millon wrote:
> I am looking for a sponsor for my package "opentyrian"

That is very nice. I was looking forward to see opentyrian in Debian for a 
while. Thanks for packaging.

> I'm happy to hear your remarks about this package.

First thing to improve is to add more DEP-3 [1] headers to patches.
Specifically the following (missing) headers would be useful:

Forwarded
Last-Update
Origin
Applied-Upstream

Working with upstream is important part of package maintenance.
From looking at patch headers I need to see whether it was Forwarded,
when Last-Update happened, where patch was taken from (Origin, if it was 
borrowed from upstream or from another distro) and sometimes Applied-Upstream 
status.

If you did not forward patches yet I'd recommend to wait no further and 
document progress as described.

Also there are some remarks about packaging:

  * There should be versioned Depends on "game-data-packager" which actually 
support "tyrian-data" (i.e. "tyrian-data | game-data-packager (>= 40)").

  * Package should install icon (there are some in "linux/icons). Icon is 
referenced from installed .desktop file.

  * Repository do not match package uploaded to Mentors. There are differences 
in "control" (Standards-Version) and in README.Debian.

  * Why not enable full hardening?
(e.g. "export DEB_BUILD_MAINT_OPTIONS = hardening=+all")

  * Re-distribution of pre-built binary "macosx/tyrian.icns" in source archive 
may be a bit of concern.

  * There is a comma "," which is not present in the original copyright 
statement after copyright year in 

Files: ./src/video_scale_hqNx.c
Copyright: 2003, MaxSt ( ma...@hiend3d.com )

IMHO it should be just "2003", not "2003,".
Other than this "debian/copyright" looks good.

> Also, please note
> that I'm a Debian Maintainer, so once this clears NEW I'm interested
> in uploading the next revisions myself. Thanks!

Great attitude. :)

[1]: http://dep.debian.net/deps/dep3/

-- 
Cheers,
 Dmitry Smirnov
 GPG key : 4096R/53968D1B

---

The truth is incontrovertible, malice may attack it, ignorance may deride
it, but in the end; there it is.
-- Winston Churchill

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

Bug#781633: /usr/sbin/ipmiconsole: repeated text in man page

2015-03-31 Thread jasen

Package: freeipmi-tools
Version: 1.1.5-3
Severity: minor
File: /usr/share/man/man8/ipmiconsole.8.gz

Dear Maintainer,

the section "KNOWN ISSUES" in the ipmiconsole man page partially occurs twice.
(search for the string "KNOWN ISSUES" )


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

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

Versions of packages freeipmi-tools depends on:
ii  libc62.13-38+deb7u8
ii  libfreeipmi121.1.5-3
ii  libgcrypt11  1.5.0-5+deb7u3
ii  libipmiconsole2  1.1.5-3
ii  libipmidetect0   1.1.5-3

freeipmi-tools recommends no packages.

Versions of packages freeipmi-tools suggests:
pn  freeipmi-bmc-watchdog  
pn  freeipmi-ipmidetect

-- debconf-show failed


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

Bug#781524: fcgiwrap: socket is not created and service is not up, but it works after a reboot

2015-03-31 Thread Santiago Vila

On Wed, Apr 01, 2015 at 12:05:05AM +0200, Jordi Mallach wrote:
> On Mon, Mar 30, 2015 at 03:18:25PM +0200, Santiago Vila wrote:
> > On a qemu virtual machine with minimal packages installed I do this:
> > 
> > apt-get install fcgiwrap
> > ls -l /run/fcgiwrap.socket
> > ls: cannot access /run/fcgiwrap.socket: No such file or directory
> > 
> > service fcgiwrap restart
> > ls -l /run/fcgiwrap.socket
> > ls: cannot access /run/fcgiwrap.socket: No such file or directory
> > 
> > If I reboot:
> > 
> > ls -l /run/fcgiwrap.socket
> > srw-rw-rw- 1 root root 0 mar 30 14:56 /run/fcgiwrap.socket
> > 
> > but surely we will not tell our users in the release notes that they
> > have to reboot fot things to work as expected, so I'm setting
> > "serious" here in the hope that a fix for this is accepted in jessie.
> 
> Is this under systemd or sysvinit?

systemd.

Sorry for not using reportbug. The qemu virtual machine I talk about
in the report was precisely to be sure that this could be reproduced
on a freshly installed jessie machine without any customization or
special packages. Everything is in its default state, which means I'm
using systemd, of course.

(So I hope that you will be able to reproduce it easily too).

Thanks.


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

Bug#781024: quassel: Denial of service (no CVE yet)

2015-03-31 Thread Olly Betts

On Wed, Apr 01, 2015 at 12:07:12AM +0200, Steinar H. Gunderson wrote:
> On Tue, Mar 31, 2015 at 11:03:01PM +0200, Steinar H. Gunderson wrote:
> > I took the patch from upstream and backported it to the version in sid;
> > this was a fair amount of work as the patch uses C++11 lambdas heavily
> > (and the version in jessie is compiled in C++03 mode; I thought changing
> > this would be too intrusive), but not immediately tricky in itself.
> > There were also some other merge conflicts that I've fixed.
> 
> More eyes: The backported patch has been OKed by two upstream Quassel
> developers, including Michael Marley (original author of the patch).
> So all it needs is some testing from some volunteer and we should be good to
> go.

I use quassel - I'll test with the patch and NMU if it looks good (if
anyone else wants to test as well, that would be great.  Or if someone
else is particularly keen to NMU, that's fine by too - just let me
know).

Cheers,
Olly


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

Bug#781631: [Pkg-gnupg-maint] Bug#781631: gnupg2: provide packaging with debug symbols for gnupg2

2015-03-31 Thread Eric Dorland

* Daniel Kahn Gillmor (d...@fifthhorseman.net) wrote:
> Package: gnupg2
> Version: 2.1.2-2
> Severity: wishlist
> 
> It would be useful to be able to ship debug symbols for GnuPG2.

Agreed, but has policy on this changed? I thought binary packages
weren't supposed to ship -dbg packages?

-- 
Eric Dorland 
43CF 1228 F726 FD5B 474C  E962 C256 FBD5 0022 1E93


signature.asc
Description: Digital signature

Bug#781632: /usr/sbin/ipmiconsole: path wrong?

2015-03-31 Thread jasen

Package: freeipmi-tools
Version: 1.1.5-3
Severity: normal
File: /usr/sbin/ipmiconsole

ipmiconsole installis in /usr/sbin but it does not require root
permissions to use (possible work-arounds for this are obvious) but this
seems sub-optiomal

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

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

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


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

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

Versions of packages freeipmi-tools depends on:
ii  libc62.13-38+deb7u8
ii  libfreeipmi121.1.5-3
ii  libgcrypt11  1.5.0-5+deb7u3
ii  libipmiconsole2  1.1.5-3
ii  libipmidetect0   1.1.5-3

freeipmi-tools recommends no packages.

Versions of packages freeipmi-tools suggests:
pn  freeipmi-bmc-watchdog  
pn  freeipmi-ipmidetect

-- debconf-show failed


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

Bug#781631: gnupg2: provide packaging with debug symbols for gnupg2

2015-03-31 Thread Daniel Kahn Gillmor

Package: gnupg2
Version: 2.1.2-2
Severity: wishlist

It would be useful to be able to ship debug symbols for GnuPG2.

   --dkg

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

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

Versions of packages gnupg2 depends on:
ii  dpkg   1.17.24
ii  gnupg-agent2.1.2-2
ii  install-info   5.2.0.dfsg.1-6
ii  libassuan0 2.2.0-1
ii  libbz2-1.0 1.0.6-7+b3
ii  libc6  2.19-15
ii  libgcrypt201.6.3-2
ii  libgpg-error0  1.17-3
ii  libksba8   1.3.2-1
ii  libreadline6   6.3-8+b3
ii  zlib1g 1:1.2.8.dfsg-2+b1

Versions of packages gnupg2 recommends:
ii  dirmngr  2.1.2-2

Versions of packages gnupg2 suggests:
ii  gnupg-doc   2003.04.06+dak1-1
pn  parcimonie  
ii  xloadimage  4.1-23+b1

-- debconf-show failed


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

Bug#781615: systemd: Only boots in rescue mode

2015-03-31 Thread Christoph Egger

Hi!

Michael Biebl  writes:
> Am 31.03.2015 um 19:07 schrieb Michael Biebl:
>> Am 31.03.2015 um 17:45 schrieb Christoph Egger:
>> 
>> That looks odd: While the fsck is running, a reboot was scheduled.
>> Did you hit CTRL+ALT+DEL?
>> 
>
> Or is this caused by
>
> Job local-fs.target/sta[   12.366051] Copyright (C) 2004 MontaVista
> Software - IPMI Powerdown via sys_reboot.

I just let it do it's thing waiting. And I had this behaviour bevore
installing ipmi-foo

  Christoph

-- 
9FED 5C6C E206 B70A 5857  70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer


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

Bug#778987: closed by Sven Bartscher (Bug#778987: fixed in haskell-cabal-install 1.20.0.3-3)

2015-03-31 Thread Joey Hess

Seems a pity this is only being fixed in experimental. If Debian
releases with a cabal that does not even work in the default
configuration, I suspect this will increase the Haskell community's
general tendency to not use Debian's haskell infrastructure.

-- 
see shy jo


signature.asc
Description: Digital signature

Bug#740950: segmentation fault in libcurl-gnutls.so.4 if download speed limiting is enabled

Hello,
are you still able to replicate these frequent crashes with 2.84
uploaded in sid? If so, please run again gdb executing

bt
bt full
thread apply all bt

when it crashes, so that I'll be able to forward this info upstream

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


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

Bug#781630: unblock: musl/1.1.5-2

2015-03-31 Thread Anton Gladky

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

Please unblock package musl

this upload fixes an RC-bug #781497 (CVE-2015-1817).
Debdiff is attached.


unblock musl/1.1.5-2


Thanks

Anton
diff -Nru musl-1.1.5/debian/changelog musl-1.1.5/debian/changelog
--- musl-1.1.5/debian/changelog	2014-10-15 23:05:27.0 +0200
+++ musl-1.1.5/debian/changelog	2015-03-31 23:12:02.0 +0200
@@ -1,3 +1,9 @@
+musl (1.1.5-2) unstable; urgency=low
+
+  * Fixes possible stack-based buffer overflow CVE-2015-1817 (Closes: #781497)
+
+ -- Kevin Bortis   Tue, 31 Mar 2015 22:42:17 +0200
+
 musl (1.1.5-1) unstable; urgency=low
 
   [ Kevin Bortis ]
diff -Nru musl-1.1.5/debian/patches/cve-2015-1817.diff musl-1.1.5/debian/patches/cve-2015-1817.diff
--- musl-1.1.5/debian/patches/cve-2015-1817.diff	1970-01-01 01:00:00.0 +0100
+++ musl-1.1.5/debian/patches/cve-2015-1817.diff	2015-03-31 23:20:03.0 +0200
@@ -0,0 +1,36 @@
+Description: Fixes possible stack-based buffer overflow CVE-2015-1817
+Author: Kevin Bortis 
+Bug-Debian: http://bugs.debian.org/781497
+Last-Update: 2015-03-31
+
+--- a/src/network/inet_pton.c
 b/src/network/inet_pton.c
+@@ -39,14 +39,15 @@
+ 	for (i=0; ; i++) {
+ 		if (s[0]==':' && brk<0) {
+ 			brk=i;
+-			ip[i]=0;
++			ip[i&7]=0;
+ 			if (!*++s) break;
++			if (i==7) return 0;
+ 			continue;
+ 		}
+ 		for (v=j=0; j<4 && (d=hexval(s[j]))>=0; j++)
+ 			v=16*v+d;
+ 		if (j==0) return 0;
+-		ip[i] = v;
++		ip[i&7] = v;
+ 		if (!s[j] && (brk>=0 || i==7)) break;
+ 		if (i==7) return 0;
+ 		if (s[j]!=':') {
+--- a/src/regex/regcomp.c
 b/src/regex/regcomp.c
+@@ -847,7 +847,7 @@
+ 			} else {
+ /* extension: accept unknown escaped char
+    as a literal */
+-node = tre_ast_new_literal(ctx->mem, *s, *s, ctx->position);
++goto parse_literal;
+ 			}
+ 			ctx->position++;
+ 		}
diff -Nru musl-1.1.5/debian/patches/series musl-1.1.5/debian/patches/series
--- musl-1.1.5/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ musl-1.1.5/debian/patches/series	2015-03-31 23:11:32.0 +0200
@@ -0,0 +1 @@
+cve-2015-1817.diff

Bug#732793: open-iscsi stop works now with systemd

2015-03-31 Thread Gilles Mocellin

Just try now with up to date SID, and it works :
mars 31 23:52:19 guitare umountiscsi.sh[11219]: Unmounting iscsi-backed
filesystems: Unmounting all devices marked _netdev.
mars 31 23:52:19 guitare open-iscsi[11225]: Disconnecting iSCSI
targets:iscsiadm: No matching sessions found
mars 31 23:52:19 guitare open-iscsi[11225]: .
mars 31 23:52:19 guitare iscsid[1099]: iscsid shutting down.
mars 31 23:52:19 guitare open-iscsi[11225]: Stopping iSCSI initiator
service:.

Versions involved:
systemd: 215-14
open-iscsi: 2.0.873+git0.3b4b4500-8

iThis bug can be closed, thanx.


signature.asc
Description: Digital signature

Bug#781524: fcgiwrap: socket is not created and service is not up, but it works after a reboot

2015-03-31 Thread Jordi Mallach

On Mon, Mar 30, 2015 at 03:18:25PM +0200, Santiago Vila wrote:
> On a qemu virtual machine with minimal packages installed I do this:
> 
> apt-get install fcgiwrap
> ls -l /run/fcgiwrap.socket
> ls: cannot access /run/fcgiwrap.socket: No such file or directory
> 
> service fcgiwrap restart
> ls -l /run/fcgiwrap.socket
> ls: cannot access /run/fcgiwrap.socket: No such file or directory
> 
> If I reboot:
> 
> ls -l /run/fcgiwrap.socket
> srw-rw-rw- 1 root root 0 mar 30 14:56 /run/fcgiwrap.socket
> 
> but surely we will not tell our users in the release notes that they
> have to reboot fot things to work as expected, so I'm setting
> "serious" here in the hope that a fix for this is accepted in jessie.

Is this under systemd or sysvinit?

> However, if for whatever reason there is not an easy fix for this,
> then please feel free to downgrade severity, I don't want this package
> to be removed from jessie.
> 
> Ok, after a little bit more of testing, I found that this works just
> after installing the package:
> 
> service fcgiwrap start
> 
> but then one might wonder:
> 
> 1. If the service is started after a reboot, why it is not started
> after installing it for the first time, as every sane package usually
> does?
> 
> 2. If "service fcgiwrap restart" does not work, why an error message
> is not shown? (even a message just saying "sorry, restart not
> supported" would be orders of magnitude better than not saying
> anything).

This should be supported. But let's try to find out what codepath is being
called, depending on your init system (reportbug would have given us that
info!)

-- 
Jordi Mallach Pérez  --  Debian developer http://www.debian.org/
jo...@sindominio.net jo...@debian.org http://www.sindominio.net/
GnuPG public key information available at http://oskuro.net/


signature.asc
Description: Digital signature

Bug#781024: quassel: Denial of service (no CVE yet)

2015-03-31 Thread Steinar H. Gunderson

On Tue, Mar 31, 2015 at 11:03:01PM +0200, Steinar H. Gunderson wrote:
> I took the patch from upstream and backported it to the version in sid;
> this was a fair amount of work as the patch uses C++11 lambdas heavily
> (and the version in jessie is compiled in C++03 mode; I thought changing
> this would be too intrusive), but not immediately tricky in itself.
> There were also some other merge conflicts that I've fixed.

More eyes: The backported patch has been OKed by two upstream Quassel
developers, including Michael Marley (original author of the patch).
So all it needs is some testing from some volunteer and we should be good to
go.

/* Steinar */
-- 
Homepage: http://www.sesse.net/


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

Bug#747973: transmission does not capture the url of the file which i want to download

Hello,
can you please clarify what you mean with "transmission does not
capture the url"? do you mean that transmission is not invoked when
you click on the torrent/magnet link in the browser? If so, what
browser do you use? have you tried with other browsers?

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


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

Bug#748978: transmission-daemon: segfaults in libgnutls.so.28 due to offending tracker

Hello,
are you still able to replicate this situation with the latest version
of transmission-daemon in sid? If so, could you please install
transmission-dbg and run the daemon under gdb, and once it crashes run
these gbd command

bt
bt full
thread apply all bt

?

This way I will be able to forward this info upstream for investigation.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


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

Bug#723943: transmission-qt: Open_file_dialog unexpected increase in the size and going beyond screen

Hello,
can you please try to replicate it with the latest version of
transmission in sid? it would be quite complicated for us to replicate
it otherwise ;)

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


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

Bug#781221: opensc: "New" beid card not working anymore

2015-03-31 Thread Eric Dorland

* Laurent Bigonville (bi...@debian.org) wrote:
> tag 781221 + patch
> thanks
> 
> Hello,
> 
> A patch that fix this issue has been merged upstream, see
> https://github.com/OpenSC/OpenSC/commit/5149dd3e62594eb2477f699d834584991ab54d5f.patch
> 
> Could this patch be applied before the jessie release?

I'm not opposed to carrying the patch for Jessie but given the
announced release date release team might not be on board. Want to
make the case to them?

-- 
Eric Dorland 
43CF 1228 F726 FD5B 474C  E962 C256 FBD5 0022 1E93


signature.asc
Description: Digital signature

Bug#781567: libgps22: upgrade failure

2015-03-31 Thread Bernd Zeimetz


forcemerge 779286 781567
thanks

hi pabs,

libgpsd will be gone in one of the next uploads, so I do not bother for 
now.
People who want to use stuff from experimental should be able to install 
it anyway :)


cheers,

Bernd

On 31.03.2015 05:18, Paul Wise wrote:

Package: libgps22
Version: 3.12-1
Severity: serious
Usertags: upgrade

When upgrading to gpsd to experimental, I get an upgrade failure 
because
both libgps and libgpsd are in the same package but their ABIs change 
at

different times. I would suggest splitting the package into two.

# aptitude upgrade
...
Selecting previously unselected package libgps22:amd64.
Preparing to unpack .../libgps22_3.12-1_amd64.deb ...
Unpacking libgps22:amd64 (3.12-1) ...
dpkg: error processing archive
/var/cache/apt/archives/libgps22_3.12-1_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libgpsd.so.22.0.0',
which is also in package libgps21:amd64 3.11-3
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
...
Preparing to unpack .../archives/gpsd_3.12-1_amd64.deb ...
Warning: Stopping gpsd.service, but it can still be activated by:
  gpsd.socket
Unpacking gpsd (3.12-1) over (3.11-3) ...
...
Errors were encountered while processing:
 /var/cache/apt/archives/libgps22_3.12-1_amd64.deb
...
E: Sub-process /usr/bin/dpkg returned an error code (1)
Failed to perform requested operation on package.  Trying to recover:
...
dpkg: dependency problems prevent configuration of gpsd:
 gpsd depends on libgps22 (= 3.12-1); however:
  Package libgps22:amd64 is not installed.

dpkg: error processing package gpsd (--configure):
 dependency problems - leaving unconfigured
...
Errors were encountered while processing:
 gpsd
# dpkg -i --force-all /var/cache/apt/archives/libgps22_3.12-1_amd64.deb
(Reading database ... 769509 files and directories currently 
installed.)

Preparing to unpack .../libgps22_3.12-1_amd64.deb ...
Unpacking libgps22:amd64 (3.12-1) ...
dpkg: warning: overriding problem because --force enabled:
dpkg: warning: trying to overwrite
'/usr/lib/x86_64-linux-gnu/libgpsd.so.22.0.0', which is also in
package libgps21:amd64 3.11-3
dpkg: warning: overriding problem because --force enabled:
dpkg: warning: trying to overwrite
'/usr/lib/x86_64-linux-gnu/libgpsd.so.22', which is also in package
libgps21:amd64 3.11-3
dpkg: warning: overriding problem because --force enabled:
dpkg: warning: trying to overwrite
'/usr/lib/x86_64-linux-gnu/libgpsd.so.22.0', which is also in package
libgps21:amd64 3.11-3
Setting up libgps22:amd64 (3.12-1) ...
Processing triggers for libc-bin (2.21-0experimental0) ...
# apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 78 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up gpsd (3.12-1) ...
Creating/updating gpsd user account...

-- System Information:
Debian Release: 8.0
  APT prefers experimental
  APT policy: (1400, 'experimental'), (1300, 'unstable'), (1200, 
'testing')

Architecture: amd64 (x86_64)
Foreign Architectures: armel, i386

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


--
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F


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

Bug#618426: transmission: Stops torrents which have no tracker

Hello,
I suspect this has been fixed a long ago, can you confim?

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


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

Bug#608830: transmission-cli: Segmentation fault

Hello,
can you please verify if this bug still applies with the latest
version of transmission?

Thanks,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


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

Bug#760314: Zoneminder in Debian

2015-03-31 Thread Dmitry Smirnov

Hi Zoneminder fans,

I'm writing to you because once you've expressed interest to help maintaining 
Zoneminder in Debian. As you may already know recently we've lost zoneminder 
from "unstable" due to lack of effort because nobody cared enough:

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

I've just took over zoneminder maintenance in Debian from Peter Howard and re-
introduced latest Zoneminder release 1.28.1 to "unstable".

Packaging is fully refurbished so it should be easier to maintain.
Now the moment is here -- let's all work together, test, answer bugs, share 
patches, forward fixes upstream and do all what is necessary to never let 
Zoneminder fell behind again. I can't do it alone as I'm not even an active 
user of Zoneminder.

From my short interaction with upstream I can tell that they answer bugs 
promptly and merge patches reasonably. It should be a positive experience to 
maintain Zoneminder with upstream like this. So please, pretty please let's
work together and have fun in progress. :)

What "zoneminer" needs now is testing, little polishing and more importantly 
staying on top of all issues.

Here is zoneminder's PTS page where you can subscribe to updates and follow 
updates:

https://packages.qa.debian.org/z/zoneminder.html

TODO: fix kFreeBSD FTBFS.
 
https://github.com/ZoneMinder/ZoneMinder/issues/771

Finally please do not rely on me regarding long-term Zoneminder maintenance.
I do not have my strategic interests with Zoneminder, just helping. ;)

-- 
Regards,
 Dmitry Smirnov
 GPG key : 4096R/53968D1B

---

It is a mistake to try to look too far ahead. The chain of destiny can only
be grasped one link at a time.
-- Winston Churchill

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

Bug#781024: quassel: Denial of service (no CVE yet)

2015-03-31 Thread Steinar H. Gunderson

tags 781024 + patch
thanks

On Tue, Mar 31, 2015 at 10:48:08AM +0200, Thomas Müller wrote:
> NMU upload is more then welcome - I lack the time to take care of this at
> the moment.

I took the patch from upstream and backported it to the version in sid;
this was a fair amount of work as the patch uses C++11 lambdas heavily
(and the version in jessie is compiled in C++03 mode; I thought changing
this would be too intrusive), but not immediately tricky in itself.
There were also some other merge conflicts that I've fixed.

The patch compiles and has had a second pair of eyes for review, but I've
never used Quassel in my life, so I can't say if it works or not. In any case
it ought to help whoever ends up doing the NMU.

/* Steinar */
-- 
Homepage: http://www.sesse.net/
>From b5e38970ffd55e2dd9f706ce75af9a8d7730b1b8 Mon Sep 17 00:00:00 2001
From: Michael Marley 
Date: Sat, 21 Feb 2015 07:33:57 -0500
Subject: [PATCH] Improve the message-splitting algorithm for PRIVMSG and CTCP

This introduces a new message splitting algorithm based on
QTextBoundaryFinder.  It works by first starting with the entire
message to be sent, encoding it, and checking to see if it is over
the maximum message length.  If it is, it uses QTBF to find the
word boundary most immediately preceding the maximum length.  If no
suitable boundary can be found, it falls back to searching for
grapheme boundaries.  It repeats this process until the entire
message has been sent.

Unlike what it replaces, the new splitting code is not recursive
and cannot cause stack overflows.  Additionally, if it is unable
to split a string, it will give up gracefully and not crash the
core or cause a thread to run away.

This patch fixes two bugs.  The first is garbage characters caused
by accidentally splitting the string in the middle of a multibyte
character.  Since the new code splits at a character level instead
of a byte level, this will no longer be an issue.  The second is
the core crash caused by sending an overlength CTCP query ("/me")
containing only multibyte characters.  This bug was caused by the
old CTCP splitter using the byte index from lastParamOverrun() as
a character index for a QString.
---
 src/core/corebasichandler.cpp |  3 ++
 src/core/corebasichandler.h   |  1 +
 src/core/corenetwork.cpp  | 86 +++
 src/core/corenetwork.h|  5 +++
 src/core/coreuserinputhandler.cpp | 72 +++-
 src/core/coreuserinputhandler.h   |  2 +-
 src/core/ctcpparser.cpp   | 26 +++-
 7 files changed, 124 insertions(+), 71 deletions(-)

Index: quassel-0.10.0/src/core/corebasichandler.cpp
===
--- quassel-0.10.0.orig/src/core/corebasichandler.cpp
+++ quassel-0.10.0/src/core/corebasichandler.cpp
@@ -33,6 +33,9 @@ CoreBasicHandler::CoreBasicHandler(CoreN
 connect(this, SIGNAL(putCmd(QString, const QList &, const QByteArray &)),
 network(), SLOT(putCmd(QString, const QList &, const QByteArray &)));
 
+connect(this, SIGNAL(putCmd(QString, const QList > &, const QByteArray &)),
+network(), SLOT(putCmd(QString, const QList > &, const QByteArray &)));
+
 connect(this, SIGNAL(putRawLine(const QByteArray &)),
 network(), SLOT(putRawLine(const QByteArray &)));
 }
Index: quassel-0.10.0/src/core/corebasichandler.h
===
--- quassel-0.10.0.orig/src/core/corebasichandler.h
+++ quassel-0.10.0/src/core/corebasichandler.h
@@ -55,6 +55,7 @@ public:
 signals:
 void displayMsg(Message::Type, BufferInfo::Type, const QString &target, const QString &text, const QString &sender = "", Message::Flags flags = Message::None);
 void putCmd(const QString &cmd, const QList ¶ms, const QByteArray &prefix = QByteArray());
+void putCmd(const QString &cmd, const QList > ¶ms, const QByteArray &prefix = QByteArray());
 void putRawLine(const QByteArray &msg);
 
 protected:
Index: quassel-0.10.0/src/core/corenetwork.cpp
===
--- quassel-0.10.0.orig/src/core/corenetwork.cpp
+++ quassel-0.10.0/src/core/corenetwork.cpp
@@ -283,6 +283,16 @@ void CoreNetwork::putCmd(const QString &
 }
 
 
+void CoreNetwork::putCmd(const QString &cmd, const QList > ¶ms, const QByteArray &prefix)
+{
+QListIterator > i(params);
+while (i.hasNext()) {
+QList msg = i.next();
+putCmd(cmd, msg, prefix);
+}
+}
+
+
 void CoreNetwork::setChannelJoined(const QString &channel)
 {
 _autoWhoQueue.prepend(channel.toLower()); // prepend so this new chan is the first to be checked
@@ -979,3 +989,82 @@ void CoreNetwork::requestSetNetworkInfo(
 }
 }
 }
+
+
+CoreNetwork::SplitGenerator::~SplitGenerator() {}
+
+
+QList > CoreNetwork::splitMessage(const QString &cmd, const QString &message, SplitGenerator *cmdGenerator)
+{
+QString wrkMsg(message);
+QList > msgs

Bug#781629: mate-panel: help not finding document

2015-03-31 Thread Alessandro Barbieri

Package: mate-panel
Version: 1.8.1+dfsg1-3
Severity: normal

Dear Maintainer,



   * What led up to the situation?

Clicking help on the clock/calendar applet

   * What was the outcome of this action?

Yelp telling me that the URI <>  points to a 
non valid page

   * What outcome did you expect instead?

Reading the help.



-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable'), (500, 'testing-updates'), 
(500, 'testing-proposed-updates'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages mate-panel depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.22.0-1
ii  libatk1.0-0  2.14.0-1
ii  libc62.19-15
ii  libcairo21.14.0-2.1
ii  libcanberra-gtk0 0.30-2.1
ii  libcanberra0 0.30-2.1
ii  libdbus-1-3  1.8.16-1
ii  libdbus-glib-1-2 0.102-1
ii  libdconf10.22.0-1
ii  libfontconfig1   2.11.0-6.3
ii  libfreetype6 2.5.2-3
ii  libgdk-pixbuf2.0-0   2.31.1-2+b1
ii  libglib2.0-0 2.42.1-1
ii  libgtk2.0-0  2.24.25-3
ii  libice6  2:1.0.9-1+b1
ii  libmate-desktop-2-17 1.8.1+dfsg1-2
ii  libmate-menu21.8.0-5
ii  libmate-panel-applet-4-1 1.8.1+dfsg1-3
ii  libmateweather1  1.8.0-2
ii  libpango-1.0-0   1.36.8-3
ii  libpangocairo-1.0-0  1.36.8-3
ii  libpangoft2-1.0-01.36.8-3
ii  librsvg2-2   2.40.5-1
ii  libsm6   2:1.2.2-1+b1
ii  libstartup-notification0 0.12-4
ii  libwnck222.30.7-2
ii  libx11-6 2:1.6.2-3
ii  libxau6  1:1.0.8-1
ii  libxrandr2   2:1.4.2-1+b1
ii  mate-desktop 1.8.1+dfsg1-2
ii  mate-menus   1.8.0-5
ii  mate-panel-common1.8.1+dfsg1-3
ii  mate-polkit  1.8.0+dfsg1-4
ii  menu-xdg 0.5
ii  python   2.7.9-1

mate-panel recommends no packages.

mate-panel 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#781628: mikutter: Mikutter not using proper avatars

2015-03-31 Thread Arthur Marsh

Package: mikutter
Version: 3.2.2+dfsg-1
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?

I noticed that some user avatars were not the regular ones, so I backed up
my .mikutter directory and restarted with no .mikutter directory.

All the user avatars were apparently mikutter-supplied and not the users'
proper avatars.

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

I expected to see the users' own avatars displayed.

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


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

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

Versions of packages mikutter depends on:
ii  ruby  1:2.1.5
ii  ruby-addressable  2.3.6-1
ii  ruby-cairo1.12.9-1
ii  ruby-delayer  0.0.2-2
ii  ruby-gettext  3.1.2-1
ii  ruby-gtk2 2.2.0-5+b2
ii  ruby-hmac 0.4.0-4
ii  ruby-httpclient   2.3.3-3.1
ii  ruby-json 1.8.1-1+b2
ii  ruby-locale   2.1.0-3
ii  ruby-memoize  1.3.1-3
ii  ruby-moneta   0.7.20-2.2
ii  ruby-nokogiri 1.6.3.1+ds-1
ii  ruby-oauth0.4.7-2
ii  ruby-text 1.3.0-1
ii  ruby-typed-array  0.1.2-3
ii  ruby1.9.1 [ruby-interpreter]  1.9.3.484-2
ii  ruby2.1 [ruby-interpreter]2.1.5-1

Versions of packages mikutter recommends:
ii  alsa-utils 1.0.28-1
ii  libnotify-bin  0.7.6-2

mikutter suggests no packages.

-- debconf-show failed


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

Bug#779503: support gccgo, at least on architectures where golang is not available

2015-03-31 Thread Tianon Gravi

On 31 March 2015 at 14:36, Matthias Klose  wrote:
> Does your testing goes beyond docker.io?  If no, I would claim your testing is
> dubious at best ;)  There are certainly still issues, but to me it starts to
> look usable.  There are other dubious things like how golang-gotools is built 
> in
> Debian ...

I apologise for how harsh my tone here was -- re-reading, it was way
more coarse than it should've been; I was frustrated at the time of
writing and too much of that came out in my response.

I did test beyond Docker (several other Go projects, and all directly
via the Go toolchain "go get", "go build", etc); I don't have lots of
extra time especially since gccgo isn't involved in my day-to-day
work.

Generally, I'm concerned that gccgo claims to be language-compatible
but not necessarily toolchain-compatible (compiler flags come to mind,
since that's what the Docker build system ended up needing changes to
build under gccgo).

Separate from that, it concerns me a great deal that Docker's
integration tests fail (and the daemon itself segfaults) when I
compile it via gccgo.  I'm not saying this is necessarily
representative, but it's an important point to consider IMO, since I
don't think it's going to be the only package that has runtime issues
when compiled with a completely different buildchain.

> I appreciate the testing you do, and I'm interested to see gccgo specific bug
> reports, if these are reproducible with Go 1.4.2. And yes, I would appreciate 
> a
> golang-gotools built from the 1.4 branch in experimental too (golang is 
> outdated
> in experimental, so I updated myself to 1.4.2 and uploaded a package to the
> Launchpad PPA ~doko/toolchain).

We did push Go 1.4.1 to experimental in Jan, but I'll try to find some
cycles to get 1.4.2 up there too; thanks for the prod.

I'll see if I can get the IBM Docker folks to do some testing on their
side, too.  Last I asked, they couldn't reproduce failures with a
gccgo-built daemon, but I'll see if they've specifically run
upstream's test-integration-cli suite against it (since that's the
workload that gets me a segfaulting daemon within just a few tests).

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

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

Bug#781510: Consider using a tool like VirtualDub or avidemux to fix it.

2015-03-31 Thread Andreas Cadhalpun

Hi Mathieu,

On 31.03.2015 09:48, Mathieu Malaterre wrote:
> On Tue, Mar 31, 2015 at 9:17 AM, Mathieu Malaterre  wrote:
>> On Mon, Mar 30, 2015 at 9:36 PM, Andreas Cadhalpun
>>  wrote:
>>> Do you know of an alternative in Debian that could be suggested?
>>
>> I did not realize there was nothing else that could be suggested. I've
>> added a block on avidemux bug in the meantime.

The alternative would be to mark it forwarded to the upstream feature request
for the bitstream filter. I don't know, if avidemux will be packaged before
that is added.

>> Thanks for the clarification (upstream bug).
> 
> I discover that:
> 
> http://ffmpeg.org/pipermail/ffmpeg-devel/2008-November/054385.html
> 
> [...]
> 4. will cause hell to break loose if copied into a standard container like
>mp4 or mpeg-ps/ts (thats because of 1. above, i mean its not mpeg4 so
>no mpeg4 decoder will know what to do with it)
> [...]
> 
> However:

However?

> $ cd /tmp
> $ wget http://samples.mplayerhq.hu/V-codecs/MPEG4/pegasus-1958-chiptune.avi
> $ ffmpeg -i pegasus-1958-chiptune.avi -codec copy test.mp4
[...]
> AFAIK the generated `test.mp4` is invalid, right ?

Yes, because even the input is not really valid.

Best regards,
Andreas


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

Bug#781586: fixed in Jessie

2015-03-31 Thread Jonathan Lane

Dear Maintainer,

There are no 3.2.x kernels available in Jessie, and this bug is no longer 
present with the default 3.16 kernel from Jessie-main.  Please remove this
as an RC bug for Jessie.

Thanks,

Jonathan Lane


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

Bug#779503: support gccgo, at least on architectures where golang is not available

2015-03-31 Thread Matthias Klose

> The "go" implementation bundled there is not fully-baked.  For
> example, using "go get" to download a project didn't bother
> downloading the dependencies like it should, thus causing the build to
> fail really hard with a screen-full of errors.

GCC 5 is not yet released. That's why it is in experimental.  The specific issue
here is https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65462 which is meanwhile
fixed in experimental.

Yes, unfortunately I had to find out myself about that one ...

> > ... claims to be compatible with Go 1.4.
>
> In my own testing, this claim is dubious at best.  The language
> support itself may be compatible (I didn't test it thoroughly enough
> to say for sure), but the tooling certainly isn't yet.

Does your testing goes beyond docker.io?  If no, I would claim your testing is
dubious at best ;)  There are certainly still issues, but to me it starts to
look usable.  There are other dubious things like how golang-gotools is built in
Debian ...

I appreciate the testing you do, and I'm interested to see gccgo specific bug
reports, if these are reproducible with Go 1.4.2. And yes, I would appreciate a
golang-gotools built from the 1.4 branch in experimental too (golang is outdated
in experimental, so I updated myself to 1.4.2 and uploaded a package to the
Launchpad PPA ~doko/toolchain).

Matthias


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

Bug#610911: KPassGen

2015-03-31 Thread simon

Hi,

I started to develop this, if anyone want join me, please write mail at 
simon.baro...@gmail.com

Bug#781529: release.debian.org: unblock noweb 2.11b-9

2015-03-31 Thread Hubert Chathi

tags 781529 - moreinfo
thanks

On Tue, 31 Mar 2015 07:41:56 +0100, "Adam D. Barratt" 
 said:

> Please go ahead, and remove the "moreinfo" tag once the package is in
> unstable.

Done.  (Hopefully I did that right.)

Thanks

-- 
Hubert Chathi  -- Jabber: hub...@uhoreg.ca
PGP/GnuPG key: 1024D/124B61FA http://www.uhoreg.ca/
Fingerprint: 96C5 012F 5F74 A5F7 1FF7  5291 AF29 C719 124B 61FA


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

Bug#775501: noweb: does not fail to build when it should

2015-03-31 Thread Hubert Chathi

On Fri, 16 Jan 2015 13:14:53 +, James Cowgill  
said:

> When building noweb on mips64el, I encountered an error when compiling
> the noweave (the error itself turned out to be a bug on my end).
>> for i in shell lib xdoc tex; do (cd $i; make all); done make[2]:
>> Entering directory '/«PKGBUILDDIR»/src/shell' notangle -Rnoweave
>> noweave.nw > noweave /bin/sh: 1: notangle: not found make[2]: ***
>> [noweave] Error 127 Makefile:21: recipe for target 'noweave' failed
>> make[2]: Leaving directory '/«PKGBUILDDIR»/src/shell' make[2]:
>> Entering directory '/«PKGBUILDDIR»/src/lib'

> However after that happened, the build continued on successfully and I
> got an empty noweave executable. The only reason I realised was that
> nbibtex then failed to build because of it.

[...]

FYI, I've created a new package to fix your other bug, but I will leave
this bug unfixed for now, since it would involve bigger changes to the
package and more investigation.  I'll get it fixed before jessie+1,
though.

> Or even better, rewrite the code to use make implicit make rules so
> that parallel compilation works on it. The same suggestions also apply
> to the other for loops in that makefile.

My make-fu is weak right now.  Can you explain more, or point me in the
right direction?

-- 
Hubert Chathi  -- Jabber: hub...@uhoreg.ca
PGP/GnuPG key: 1024D/124B61FA http://www.uhoreg.ca/
Fingerprint: 96C5 012F 5F74 A5F7 1FF7  5291 AF29 C719 124B 61FA


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

Bug#755202: [Pkg-utopia-maintainers] Bug#755202: network-manager: keeps creating and using new connection "eth0" that does not work

2015-03-31 Thread Fitzcarraldo

 Original Message 
*Subject: *Re: [Pkg-utopia-maintainers] Bug#755202: network-manager:
keeps creating and using new connection "eth0" that does not work
*From: *Michael Biebl 
*To: *Fitzcarraldo , 755...@bugs.debian.org
*Date: *31/03/15 07:49
> Am 19.03.2015 um 18:59 schrieb Fitzcarraldo:
>> Mar 18 22:17:33 localhost NetworkManager[8346]:   new connection
>> /etc/NetworkManager/system-connections/eth0
> Can you attach this file /etc/NetworkManager/system-connections/eth0?
>

As requested, I attach the file
/etc/NetworkManager/system-connections/eth0. Its contents are also
listed below:

[ethernet]
mac-address=70:5A:B6:3E:C1:8A
mac-address-blacklist=

[connection]
id=eth0
uuid=cb3d5786-f947-44b8-92f7-8471fc94c568
type=ethernet
permissions=user:fitzcarraldo:;
secondaries=

[ipv6]
method=ignore
dns-search=

[ipv4]
method=auto
dns-search=
may-fail=false

My current situation is as follows, and no invalid second eth0
connection is created:

IPv6 is enabled in aliases.conf
IPv6 is disabled in avahi-daemon.conf
[ipv6] method=ignore
[ipv4] method=auto
[ipv4] may-fail=false

If I make the situation as follows, no invalid second eth0 connection is
created either (which is not surprising given that IPv6 is disabled
system-wide):

IPv6 is disabled in aliases.conf
IPv6 is enabled in avahi-daemon.conf
[ipv6] method=ignore
[ipv4] method=auto
[ipv4] may-fail=true

When the situation is as follows an invalid second eth0 connection is
usually (i.e. more often than not) created:

IPv6 is enabled in aliases.conf
IPv6 is enabled in avahi-daemon.conf
[ipv6] method=ignore
[ipv4] method=auto
[ipv4] may-fail=true

Bug#533267: release-notes: Purging uninstalled packages

On 2014-11-24 19:37, Karl O. Pinc wrote:
> On 11/24/2014 12:28:14 PM, Niels Thykier wrote:
>> On 2014-11-24 16:00, Karl O. Pinc wrote:
>>> [...]
>> I am not particular concerned with the kernel.  Due the to check you
>> mentioned yourself, you have to manually approve of removing the
>> running
>> kernel.  If the user removes the running kernel, it is not like
>> purging
>> it will make it much worse.
> 
> FYI:  Removing the running kernel does not remove anything from
> /boot.  Purging does.
> 

Noted.  Still, if the user does not heed the first warning, I doubt they
will pay attention to the warning from the release-notes.


> 
>> That said, we could move this to a "pre-upgrade" text.  From my point
>> of
>> view, the primary idea with this, is to ensure that people do not 
>> have
>> old broken init.d scripts lying around on the system (that breaks the
>> boot).
> 
> Pre-upgrade would work, to address your concerns.
> 
> But I also
> think there should be a note to purge in post-upgrade (per
> the original bug request).  Post-upgrade is when somebody's
> likely to be most familiar with what's being purged, rather
> than years later when it's time for the next upgrade.
> 
> Jessie is sort of a special case since the boot system changes.
> After jessie you might not need to purge pre-upgrade.
> 
> Karl 
> [...]

Okay, I have now moved the section into 4.8 ("Preparing for the next
release") and linked to it from various other places as deemed necessary
for the Wheezy to Jessie release.

Please note that it may be a couple of hours before it is live on the
website.

Thanks,
~Niels


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

Bug#779503: support gccgo, at least on architectures where golang is not available

2015-03-31 Thread Tianon Gravi

On 31 March 2015 at 14:10, Matthias Klose  wrote:
> There is a deficiency in dh-golang, which doesn't make things verbose at all,
> even when setting DH_VERBOSE=1.  You can get more information about invoked
> commands by using -x. Maybe there are more things to pass, but I'm not a 
> golang
> maintainer.  The dh-golang bug is filed as #780077.

This was all with "go build -v" directly -- no debhelper involved (and
docker.io only uses dh-golang very lightly anyhow).

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


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

Bug#533267: release-notes: Purging uninstalled packages

On 2014-11-24 17:03, Hendrik Boom wrote:
> On Mon, Nov 24, 2014 at 08:01:10AM +0100, Niels Thykier wrote:
>> +It is generally advisable to purge removed packages.  This is
>> +especially true, if these have been removed in an earlier release
>   ^
> English does not use a comma here, though some other languages do.
> 
>> +upgrade (e.g. from the upgrade to &oldreleasename;) or from
>> +third-party vendors.  In particular, old init.d scripts have been
>> +known to cause issues.
> 
> -- hendrik
> 

Thanks I have corrected this now.  Sorry for the delay. :)

~Niels


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

Bug#781607: [Pkg-freeipa-devel] Bug#781607: freeipa: please package new upstream version

2015-03-31 Thread Timo Aaltonen

On 31.03.2015 17:31, Holger Levsen wrote:
> package: freeipa
> severity: wishlist
> 
> Hi Timo,
> 
> as you'll undoubtly know, freeipa 4.1.3 is out - do you have any estimate 
> when 
> you'll get around packaging it? And, do you happen to know if it will be 
> sufficient to upgrade just the freeipa source package or are there other 
> packages which need to be updated (or newly packaged?) too?

It needs at least bind 9.10 or up and softhsm 2.0.0b2 (see bug #780354).
Could be others too, didn't really bother checking further.


-- 
t


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

Bug#779503: support gccgo, at least on architectures where golang is not available

2015-03-31 Thread Matthias Klose

> Worse yet, I tried building the newly-merged-upstream[1] docker gccgo
> support using it, and the "go build" invocation failed to produce a
> binary at the location specified by "-o", but did so with a zero exit
> code indicating success, which is much more alarming.  Even adding
> "-v" to the build flags didn't produce any extra output to help narrow
> down the issue.

There is a deficiency in dh-golang, which doesn't make things verbose at all,
even when setting DH_VERBOSE=1.  You can get more information about invoked
commands by using -x. Maybe there are more things to pass, but I'm not a golang
maintainer.  The dh-golang bug is filed as #780077.

Matthias


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

Bug#781627: synaptics docs

2015-03-31 Thread Matt Taggart

Package: xorg
Version: 20150331
Severity: wishlist

I recently did a jessie install on a new laptop, an ASUS UX305FA, and
the install was nearly perfect, everything just worked, yay!

This laptop has a touchpad and I had some minor issues figuring it out
and I have some small suggestions for the documentation at

  http://pkg-xorg.alioth.debian.org/howto/configure-input.html

(and maybe the wiki page at https://wiki.debian.org/SynapticsTouchpad)

1) I couldn't emulate a middle button click by clicking left+right.
Eventually I read in the synaptics(4) man page that,

  "ClickPads do not support middle mouse  button  emulation."

It might be good to mention that and alternatives, maybe something like

  "Touchpads with a button integrated in the touchpad surface (called
  'ClickPad') do not support emulating a middle button click by
  clicking the left and right buttons at the same time. On these
  devices alternatives are using '3 finger click' or setting up a
  dedicated area of the touchpad for middle button using the
  'SoftButtonAreas' option."

2) After typing there is a delay before the touchpad becomes active.
I learned this is controlled by the syndaemon program, which was
already running as

  'syndaemon -i 2.0 -K -R'

with a 2 second delay. But I can't find where those settings are
configured or how syndaemon is even launched. ppid is 1 so init must
be launching it but I can't find anything in /etc/init.d/, /etc/X11,
/etc/default. Compounding the problem is that if you touch the pad
before the 2.0s is up, the pointer won't respond until you lift your
finger and set it back down. 2.0s was too much for me, I have it turned
down to 0.1. So A) document how to adjust it and B) consider turning it
down.

3) The bottom of the configure-input page says:

  "Warning: it becomes quite difficult to use things like Ctrl+click
  in a browser, or Alt+drag to move windows."

I think this is what the syndaemon -K flag is for? (which is on by
default). So maybe the example could be adjusted and that line removed?


Thanks,

-- 
Matt Taggart
tagg...@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#779503: please communicate with the community, not the bug trackers

2015-03-31 Thread Matthias Klose

Hi Tianon,

Paul Tag* pointed out your replies to these bug reports and to the launchpad
report #1392094.  I didn't see these until now, so it would be better to
communicate with the community, and not the bug trackers.  For the future, 
please

 - always CC the bug submitter in debian, if you want that the
   bug submitter sees you replies.  You can do that using either
   the original mail, or by mailing -submit...@bugs.debian.org.

 - the launchpad report #1392094 is a closed report. Usually these
   reports get even less attention than open reports.  Feel free to
   open a new one (using the gccgo-5 package for gccgo specific things).

 - please don't mix things in bug reports.  Is there a go specific ML
   in Debian? If not, feel free to suggest one. In the meantime, you
   can reach the Debian GCC maintainers at debian-...@lists.debian.org,
   or you may want to use use debian-toolch...@lists.debian.org until
   you found a new home.

I'll reply to various issues in follow-up emails.

Matthias


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

Bug#546936: ITP: r-cran-igraph -- GNU R package for igraph

2015-03-31 Thread Andreas Tille

Hi Alba,

On Tue, Mar 31, 2015 at 05:53:19PM +0200, Alba Crespi wrote:
> I am currently working on packages for r-cran-phangorn and its
> dependencies, and I saw that you already have an ITP for r-cran-igraph.
> What is the status? Do you have something ready, or is there something
> blocking a package?

I think I simply lost interest.  Its in SVN and I think ready for upload.
If you are interested I could do.  Any further predependencies?

Kind regards

Andreas.

-- 
http://fam-tille.de


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

Bug#781610: python-requests: ships CA certificate bundle

2015-03-31 Thread Thorsten Glaser

tags 781610 - moreinfo
thanks

Daniele Tricoli dixit:

>> python-requests_2.4.3-6_all.deb/deb://CONTENTS/usr/lib/python2.7/dist-packag
>> es/requests/certs.py should be a symbolic link to
   
>> /etc/ssl/certs/ca-certificates.crt
>
>requests.certs is not a CA bundle, it's a module that permits downstream

Yes… sorry, obvious (now) pasto.

It’s /usr/lib/python2.7/dist-packages/requests/cacert.pem ofc.

bye,
//mirabilos
-- 
15:39⎜«mika:#grml» mira|AO: "mit XFree86® wär’ das nicht passiert" - muhaha
15:48⎜ also warum machen die xorg Jungs eigentlich alles
kaputt? :)15:49⎜ thkoehler: weil sie als Kinder nie den
gebauten Turm selber umschmeissen durften?  -- ~/.Xmodmap wonders…


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

Bug#766812: spurious library link

2015-03-31 Thread Kevin Bortis

The link is needed for various tools that expect a link or the real
libc.so be available in the same location as the includes and other
resources. One prominent member is musl-gcc from the musl-tools
package, which would fail to dynamic link to the correct libc.so.


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

Bug#780259: perl: please make the output of Pod::Man reproducible

2015-03-31 Thread Niko Tyni

On Wed, Mar 11, 2015 at 10:01:07AM +, Chris Lamb wrote:

> While working on the "reproducible builds" effort [1], we have noticed
> that Pod::Man generates output that varies depending on the current
> timezone.
> 
> The attached patch fixes this by using GMT (~UTC) dates instead

Thanks. Unlike Axel, I'm not very worried about this creating confusion
for users far away from UTC, given that only the date part is embedded.
However, I agree that modifying TZ in the build environment would be a
more general (and probably sufficient) fix.

However, I have other concerns. Sorry for taking so long to voice them.

I'd like to note that there are two somewhat separate issues
with building reproducible packages involving Pod::Man. Both of these
derive from its longstanding feature of embedding the date part of the
mtime stamp of its source file.

A) the local time zone affects the mtime -> date conversion (this bug)

B) source files patched by the Debian packaging will have their
   mtime set to the current time when the package is extracted, and
   therefore the date in the manual page headers will vary with the
   build date

While the provided patch fixes A) but not B), I expect the fix for B)
would fix A) as well.

According to codesearch.debian.net, we have 819 packages in sid that patch
*.pm or *.pod files (my search was "\+\+\+ .*\.(pm|pod) path:debian/patches").
I would expect that most of these generate manual pages with Pod::Man.

I think the current reproducible builds test setup hasn't found these
yet because it is not comparing packages built on different days.

So B) seems worth fixing.

After trying unsuccessfully to get dpkg-source to set the mtime stamp
of patched files to the last debian/changelog entry (see #759404), we
ended up with a change in Pod::Man where it honours the POD_MAN_DATE
environment variable and uses that as the header rather than anything
based on mtime stamps (or timezones, for that matter.) This is properly
upstream and available in sid and jessie, see #759405.

A downside of this is that POD_MAN_DATE will affect all the manual pages
generated by Pod::Man and remove the potentially useful indications of
their recency. I can't really see how to avoid that, but possibly we
should set POD_MAN_DATE to something that isn't really a timestamp at
all, so as not to mislead readers. Given the check for a true value in
devise_date(), an empty string isn't an option, but a space or 'N/A'
come to mind.

So I argue that the best way to fix this bug in the long term is to
somehow set POD_MAN_DATE based on debian/changelog, as that fixes both A)
and B).  The patch provided in this bug seems more like an interim fix,
but I'm certainly glad that it helps the current testbed deployment.

As Holger noted in the TZ discussion, one problem is where to set such
environment variables. I think debhelper is the easier and most natural
place, particularly as it has already collected other patches related
to reproducible builds. The few packages (like perl itself) not using
debhelper can perfectly well set POD_MAN_DATE themselves.

(As an aside,I'm wondering if it would make sense to standardize on
 DEB_BUILD_OPTIONS=reproducible or something to trigger tweaks like this.)
-- 
Niko Tyni   nt...@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#775541: NFS mounts from /etc/fstab works for me

2015-03-31 Thread Paul van der Vlis

Hello,

I don't see real problems with NFS mounts from /etc/fstab, I am using it
with homedirs on about 14 clients with NFS4 and MIT Kerberos.

NFS is not needed for booting. After booting /home is mounted.

Maybe NFS comes up before the network is accessabel, it does not wait.

The only point is an ugly red error during boot.

With regards,
Paul van der Vlis.


-- 
Paul van der Vlis Linux systeembeheer, Groningen
http://www.vandervlis.nl


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

Bug#775812: base: HP EliteBook 840 G1 laptop fails to halt/poweroff after 15/12/2015 upgrade

2015-03-31 Thread Tim

Hi all,

First of all, thank you for your time investigating the bug.

I ran a few tests today, trying to help pinpointing the exact cause of
the bug.

On Mon, 2015-03-30 at 16:55 -0300, Henrique de Moraes Holschuh wrote:
> For those affected (i.e. if your HP Elitebook 840 G1 DOES have
> halt/poweroff issues right now), please do this:
> [...]

My HP Elitebook 840 G1 did not shutdown (but kept on rebooting) so I
purged 'intel-microcode', ran 'update-initramfs -u' to be sure,
validated that '/lib/firmware/intel-ucode' was removed from the system,
rebooted the system, and finally tried to power off the system. The
notebook did not power off properly, but rebooted instead—just as
before. Like you said, I think we can now conclude it is not
intel-microcode's fault.

On Mon, 2015-03-30 at 18:54 +0200, Samuel Thibault wrote:
> > I would like to add that I also didn't succeed in halting the
> > notebook by using the GRUB command 'halt', it just rebooted after
> > entering this command.
> 
> Is this after a cold reboot (thus no uploaded microcode) or only after
> a hot reboot?
> 
> Also, just to make sure: with systemd the "halt" command doesn't power
> off, "poweroff" needs to be used instead.

Next, I tried to power off the system with the GRUB command 'halt'.
There is no GRUB command 'poweroff' so I had to use 'halt'. The problem
still persisted and the notebook rebooted instead of powering off.
Next I tried to 'cold reboot': I powered off the notebook by hitting the
power button at the GRUB boot menu, started the notebook (hitting the
power button again), and entered the GRUB command 'halt'. Now the
notebook did properly power off. I started the notebook again, let it
boot al the way to the GNOME desktop and shut it down again from there.
I was able to properly power down the system three times in a row.

I had the idea the network connection (similar to Miguel) was cosing
trouble, since I was not always able to reliably replicate the bug when
I used the wired ethernet connection. For clarity, I had the suspicion
that switching between wired and wireless network connections sometimes
caused the bug to occur again.

Continuing with my tests, I installed 'intel-microcode' again, switched
wireless on—hoping to trigger the bug again. However, I shutdown and
started the notebook four times, enabling and disabling the wireless
network, but I did not succeed in triggering the bug to happen again.

On Tue, 2015-03-31 at 08:11 -0300, Henrique de Moraes Holschuh wrote:
> Please also attach the output of "lspci -v -v" (run as root).

I can send you this next time when I'm using the notebook again. I
forgot to check it last time!

Hope this extensive description of what I've tried helps!

Cheers,
Tim

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

Bug#513106: dbconfig-common: provide a script to check sql schemas

2015-03-31 Thread Paul Gevers

Control: tags -1 moreinfo

Hi Thomas,

I have taken over maintenance of dbconfig-common from Sean.

On Mon, 16 Mar 2009 22:26:47 +0100 sean finney  wrote:
> On Mon, Jan 26, 2009 at 02:39:57PM +0100, Thomas Koch wrote:
> > Unfortunately at least MySQL does not provide any means to syntax check
> > a sql script. But the script could create a temporary database and try
> > to install the given schema (and data).
> 
> i'm not sure what it is you want that dbconfig-common doesn't already do.
> 
> in the initial bootstrap i don't think this gets us any advantage over
> simply "doing it", since it would be doing the same operation twice,
> dbconfig-common already checks for errors in the process, and we're starting
> from nothing so there's no risk in failure.  
> 
> for upgrades, this would test that the sql is correct, but not know how
> it behaved on the real data.  what you really want is a transaction
> so that if there's a failure a rollback can occur.  no new feature in
> dbconfig-common is needed for this, the package maintainer simply needs
> to add a transaction start/commit to the existing upgrade code.
> 
> is there some other use case i'm missing, or is it okay to close this bug?

Can you please comment? Else I am going to close this bug in a month or so.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#750837: ITP: moarvm -- virtual machine for Rakudo Perl 6 and NQP

2015-03-31 Thread Daniel Dehennin

Dominique Dumont  writes:

> Hello Daniel

Hello,

> I've used moarvm package as a test case for 'cme update dpkg-copyright'. 
>
> Turns out that some copyright entries from 3rdparty directories were missing.
> There were also some minor mistakes in the copyright owners. There's a better 
> chance of having moarvm go through ftp-masters without missing entries in 
> copyright file...

Great, I was looking for a tool to manage this, it's quite cumbersome to
do it by hand.

> I've also added a 'fix.scanned.copyright' file in debian to work around some 
> limitations (or bugs) of licensecheck command.
>
> Last but not least: your previous work on debian/copyright is not wasted: 
> some files cannot be scanned and 'cme update' did reuse the data you've 
> created. 
> The fix.scanned.copyright file [1] is needed for files where licensecheck 
> returns 
> bogus data.
>
> I've pushed the new debian copyright file [2] to copyright-cme-update branch 
> on 
> pkg-moarvm repo. Feel free to pick up what you want from this file or simply 
> merge it on master. 

Ok, I merged it.

I remove the “author variant” license paragraphes “BSD-2-clause~author”
and “BSD-3-clause~Google” and manually fix the remaining
“BSD-3-clause~author”.

> I also found (manually, cme is not that magic ;-p ) that the license you 
> flagged as "Other" is a MIT variant. This update is pushed on master. [3]
>
> Once the copyright is done, I don't see any other issue to upload moarvm.

I added the Upstream-Contact pointing to the “contribution” web page
since it groups GitHub and IRC informations.

Everything pushed.

Regards.
-- 
Daniel Dehennin
Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF
Fingerprint: 3E69 014E 5C23 50E8 9ED6  2AAD CC1E 9E5B 7A6F E2DF


signature.asc
Description: PGP signature

Bug#781609: sponsorship-requests: RFS: noweb 2.11b-9 (Fixes #781099, unblock #781529)

2015-03-31 Thread Eriberto

2015-03-31 15:40 GMT-03:00 Hubert Chathi :
> On Tue, 31 Mar 2015 12:44:49 -0300, Eriberto Mota  said:
>
>> Hi Hubert, I can upload. Can you sign this message?
>
> Thanks.  If it works properly, this message should be signed with both
> my old 1024D and my new 4096R key.


I think that we have 1024D only. No problem.


> I just noticed that I forgot to post the download location for my
> package (though you'll obviously want to rebuild it yourself).  You can
> download the packages that I built at:
> https://debian.uhoreg.ca/experimental/noweb/


Ah, ok. Before, I applied your patch to test the package. Now, I
uploaded the version gotten from your site.

Call me if you need more help.

Cheers,

Eriberto


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

Bug#773369: Jessie grub background overlaps with text

2015-03-31 Thread Ralf Jung

Hi,

I can confirm the problem on my system, with the German locale.
I guess it's not necessary to attach another picture ;-)

Kind regards,
Ralf


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

Bug#781609: sponsorship-requests: RFS: noweb 2.11b-9 (Fixes #781099, unblock #781529)

2015-03-31 Thread Hubert Chathi

On Tue, 31 Mar 2015 12:44:49 -0300, Eriberto Mota  said:

> Hi Hubert, I can upload. Can you sign this message?

Thanks.  If it works properly, this message should be signed with both
my old 1024D and my new 4096R key.

I just noticed that I forgot to post the download location for my
package (though you'll obviously want to rebuild it yourself).  You can
download the packages that I built at:
https://debian.uhoreg.ca/experimental/noweb/

> Cheers,

> Eriberto


> 2015-03-31 11:55 GMT-03:00 Hubert Chathi :
>> Package: sponsorship-requests Severity: wishlist
>> 
>> (Cc: TeX team, since noweb is somewhat TeX-related)
>> 
>> I've updated noweb to fix bug #781099, which has already been
>> unblocked by the release team (#781529), but I am unable to upload
>> because I no longer have a key in the keyring, due to my 1024D being
>> disabled and my 4096R not being connected enough.  So I'm looking for
>> someone to sponsor this upload.  The package is in otherwise good
>> shape, and will hopefully I will have my 4096R key enabled before
>> another upload is needed.
>> 
>> The diff is just a one-line change (not including changelog):
>> 
>> diff -u noweb-2.11b/debian/changelog noweb-2.11b/debian/changelog ---
>> noweb-2.11b/debian/changelog +++ noweb-2.11b/debian/changelog @@ -1,3
>> +1,10 @@ +noweb (2.11b-9) unstable; urgency=low + + *
>> debian/patches/99_touch.dpatch: Add src/shell/noweave to the list of
>> touched + files. (Closes: #781099) + + -- Hubert Chathi
>>  Fri, 27 Mar 2015 22:06:25 -0400 + noweb (2.11b-8)
>> unstable; urgency=low
>> 
>> * debian/control: diff -u noweb-2.11b/debian/patches/99_touch.dpatch
>> noweb-2.11b/debian/patches/99_touch.dpatch ---
>> noweb-2.11b/debian/patches/99_touch.dpatch +++
>> noweb-2.11b/debian/patches/99_touch.dpatch @@ -12,6 +12,7 @@ -patch)
>> sleep 1 # so that we have at least a second difference in timestaps
>> for x in src/shell/tmac.w \ + src/shell/noweave \ src/shell/noroff \
>> src/shell/toroff \ src/xdoc/notangle.1 \
>> 
>> Thanks,
>> 
>> Hubert
>> 
>> -- System Information: Debian Release: 7.2 APT prefers stable APT
>> policy: (990, 'stable'), (500, 'stable-updates'), (500, 'unstable'),
>> (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64)
>> Foreign Architectures: i386
>> 
>> Kernel: Linux 3.17-1-amd64 (SMP w/4 CPU cores) Locale:
>> LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh
>> linked to /bin/dash
>> 
>> 
>> -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
>> with a subject of "unsubscribe". Trouble? Contact
>> listmas...@lists.debian.org Archive:
>> https://lists.debian.org/87zj6tush1@desiato.home.uhoreg.ca
>> 

-- 
Hubert Chathi  -- Jabber: hub...@uhoreg.ca
PGP/GnuPG key: 1024D/124B61FA http://www.uhoreg.ca/
Fingerprint: 96C5 012F 5F74 A5F7 1FF7  5291 AF29 C719 124B 61FA


signature.asc
Description: PGP signature

Bug#610910: grub-pc: LC_MESSAGES env value is not used

2015-03-31 Thread Ralf Jung

Dear grub Maintainers,

four years after being reported (with a patch!), this bug is still open.
I would appreciate if you could kindly review the provided patch, which
looks like a simple enough fix to make grub follow common practice on
Linux wrt. the locale (in particular, LC_MESSAGES overriding LANG for,
well, messages).

Kind regards,
Ralf


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

Bug#780096: RFS: dyfi/1.2.0-1 [ITP #779708]

2015-03-31 Thread Antti Järvinen

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 > There is no if statement in d/config. Did you mean one in d/postinst?
 > It is needed to run only at the package configuration phase.

Ok, actually, according to
http://www.fifi.org/doc/debconf-doc/tutorial.html it seems like the
options for $1 are "configure" and "reconfigure" so in your case it is
quite ok to do all actions in both cases. I've myself run into 
surprises somehow if I've not conditioned..

 > Thanks for comments,

My pleasure,

- --
Antti

-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: Processed by Mailcrypt 3.5.8 

iD8DBQFVGu6UUTdja+nNMWMRAtsTAKCHnaW7eQ6KNjoAuDCKfkXGvr46TACfaHp/
+Zj1dQ9obhPGu2Sh7RvJhu4=
=Z7K9
-END PGP SIGNATURE-


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

Bug#749887: Retitle

2015-03-31 Thread Andreas Noteng

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Control: retitle -1 ITP: syncthing -- decentralized file synchronization tool
thanks

I will continue Teemus work and try to get this into Debian. Teemu gave
me permission to take over his work and use the collab-maint repo he
started.

Cheers
Andreas Noteng

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJVGufyAAoJELRG7qgympRauIcP/0sLStttXonzDr2EAfCPD8aV
jLfXOWnkclUq5kLYju4DCw7S8kN6DEmm9TyniBahAQqSGUPmmop1Xddfeu0w6Kqa
jPtsbPFxzpU3GeT7Pshr72g66E5HaoWSVi6LB5995Wd5FWXJj40Gp8pSCGcJTLCr
AXyZpc/0XZ1G7pgbZ2hEyq5hBwLJa9kd2rwABOnmqvEhrr54wzjLEieMuSgqlmt6
PHlwi99q7bQoqY52soQMTRAW1cAWJQDe4/vC77uJcQLLqah78uJmZisHXzBvMrMR
LfWjFOly2T25f904lMOpdUN/ZTO+JqERqHIMX+CDF5ti5nO+Qq4cv5VzVth3S4Gw
8RWiFno50DSxYXVBTtoxDxvpC1l/TWagUFSzMEsSqJ7jIrm+i8B5Yy+eWrU+S5c4
V2oFX5yShEH2CRZiI3eAeRfdrB7VHSyaoyPGWdMuCRdWFBKKE5zGS4GTge08K7JS
XnUbxFO/vPIm8xpAWGVFOPUA2mVmS5ti9kmrNSPXFyi7MHvGyDYIUD6AwobLWvG5
DzCfnq2CHfBsckeZXlaXixq2itUQiViMcKmAYuEIiYPW2E5dnt+ec//eyPN/KWOo
jvp+yO/fdxyoIuYCRHRuAh09n3R0PmQl56LAUHOQfHYsZe9gX0xDojdWY345j5P6
Uyv1OZm4FVjhon8ApMwT
=lWEG
-END PGP SIGNATURE-


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

Bug#781626: mailman: CVE-2015-2775: Path traversal vulnerability

2015-03-31 Thread Salvatore Bonaccorso

Source: mailman
Version: 1:2.1.18-1
Severity: important
Tags: security patch upstream fixed-upstream

Hi,

the following vulnerability was published for mailman.

CVE-2015-2775[0]:
Path traversal vulnerability

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2015-2775
[1] https://bugs.launchpad.net/mailman/+bug/1437145
[2] https://mail.python.org/pipermail/mailman-announce/2015-March/000209.html

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore


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

Bug#781355: python-docker: New upstream version

2015-03-31 Thread Tianon Gravi

On 27 March 2015 at 16:30, Felipe Sateler  wrote:
> docker-py is already at version 1.1. The current version is too old to
> package the new fig/docker-compose :(

I looked into putting a bumped version (1.1.0) into experimental, but
ran into two minor problems.

The first is that I don't know the "proper" branch format for
experimental in debian-python's SVN tree (it looks like it's just keep
going forward in trunk and create a branch when/if a new sid/jessie
upload is required, but I can't find any documentation to confirm or
deny that).

The second is that we need a bump of python-requests too (2.5.3+).

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

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

Bug#781610: python-requests: ships CA certificate bundle

2015-03-31 Thread Daniele Tricoli

tags 781610 +moreinfo
thanks

Hi Thorsten,
thanks for the report.

On Tuesday 31 March 2015 17:24:06 Thorsten Glaser wrote:
> python-requests_2.4.3-6_all.deb/deb://CONTENTS/usr/lib/python2.7/dist-packag
> es/requests/certs.py should be a symbolic link to
> /etc/ssl/certs/ca-certificates.crt

requests.certs is not a CA bundle, it's a module that permits downstream 
developers to specify where the CA bundle is:

❯ cat /usr/lib/python2.7/dist-packages/requests/certs.py
#!/usr/bin/env python
# -*- coding: utf-8 -*-

"""
certs.py

This module returns the preferred default CA certificate bundle.

If you are packaging Requests, e.g., for a Linux distribution or a managed
environment, you can change the definition of where() to return a separately
packaged CA bundle.
"""
import os.path

try:
from certifi import where
except ImportError:
def where():
"""Return the preferred certificate bundle."""
# On Debian systems use ca-certificates
return '/etc/ssl/certs/ca-certificates.crt'

if __name__ == '__main__':
print(where())

So, it's just a function that returns a path. On Debian it's patched to 
return: /etc/ssl/certs/ca-certificates.crt.

upstream requests use certifi[¹] but is not used on Debian because we have 
already ca-certificates.

You can also see my reply on #779528 (it's a request to package certifi):
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779528#10

Am I missing something else? 

Kind regards,

[¹] https://pypi.python.org/pypi/certifi

-- 
 Daniele Tricoli 'Eriol'
 http://mornie.org

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

Bug#780096: RFS: dyfi/1.2.0-1 [ITP #779708]

2015-03-31 Thread Eugene Zhukov

On Tue, Mar 31, 2015 at 8:42 PM, Antti Järvinen
 wrote:
[...]
> So, the comments:
> about debian/config:
>  - Is it necessary to have condition
>if [ $1 = "configure" ]; then
>..
>fi
>around db_input/db_go -commands? I'm under impression that this
>config-script might be run also on other situations than config ;
>or is this intentional?
There is no if statement in d/config. Did you mean one in d/postinst?
It is needed to run only at the package configuration phase.

> about debian/copyright:
>  - According to
>https://lists.debian.org/debian-devel-announce/2006/03/msg00023.html
>you should have, among other things in the copyright file the authors
>name and year of the copyright. Year is missing for "Files: *"
>and then I'm not sure if "dy.fi admins" count as name of
>author ; I understand that there may be real organization of
>human behind dy.fi that have developed the sw but .. naming
>a person, a company or other entity that may be recognized
>by rule of law (in Finland?) might be a jolly good idea?
>  - There are "Files-Excluded" mentioned in copyright ; it might be
>required to explicitly state that they may be distributed anyway,
>for example using "permissive" license, if the files fall into
>such category.
Thanks, I'll try to address these issues.

> about debian/po/templates.pot Minor whining:
>When username is queried, would it be nice to indicate that
>this is exactly "dy.fi system username" and not just "username"
>or is this going to be very clear in advance to person doing
>the installation? I understood that the user account needs to
>exists beforehand..
> about debian/postinst
>What is going to be file permission of /etc/dyfi-update.conf ?
>It may contain user account + password to remote box?
Restricted to dyfi user, but true it can be accessed by others.

>
> general:
>There is no documentation of any kind. Maybe a short manpage might
>be in order?
>
Well, it's not really a binary, it's a daemon so you can only check it's state.

Thanks for comments,
Eugene


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

Bug#780940: hdparm freeze's bug information

On 2015-03-31 19:50, Niels Thykier wrote:
> [...]
> The list of changes between the Debian version and the Ubuntu version is
> fairly short.  I have attached the diff (minus d/changelog) here and we
> are down to:
> 
> [...]
> 
> Given you suggest that compiling the new upstream also works for you, I
> am suspecting it could be this change:
> 
> """
> +  * hdparm.c, identify.c, sgio.h: import patch from
> +http://sourceforge.net/p/hdparm/patches/35/ to add support to
> 'hdparm -I'
> +for reporting DevSleep information.  LP: #1031173.
> """
> 
> [...]

I just checked hdparm-9.45 and it does *not* have that change AFAICT.
Sorry, it was likely a red herring.

Upstream's changelog does mention the following:


"""
hdparm-9.45:
   - fixed blocksize handling in fibmap code to use result from
 FIGETBSZ in more places (Anton Altaparmakov).
   - fixed divide by zero exception in geom.c
   - tidying up formatting in sgio.c
hdparm-9.44:
   - changed reg_flags struct to more closely match kernel
 definition (Lucas Magasweran).
   - added fwdownload mode "E" support (Rusty Carruth).
   - fix timeouts for security-erase (again!)
   - change display of security "supported" to handle ambiguous
 reporting from drives
   - don't rely upon C-library for byte-swapping
   - added --dco-setmax support, courtesy of Geoff Papilion.
"""

(Assuming it rings any bells).

> 
> Failing that, Ubuntu also removed the "hdparm-resync.lock".  Assuming
> what we exactly see is a deadlock and "timeout" killing hdparm to
> workaround said deadlock.  But at this point, I am guessing!
> 
> 
> Thanks,
> ~Niels
> 
> https://bugs.launchpad.net/intel/+bug/1031173
> 

Thanks,
~Niels


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

Bug#741464: grub-pc-bin: hangs after displaying boot menu

2015-03-31 Thread Marco Gamberoni

In data lunedì 23 marzo 2015 15:17:56, Colin Watson ha scritto:
> On Sun, Feb 01, 2015 at 11:16:59PM +0100, Marco Gamberoni wrote:
> > Having read
> > 
> > http://web.archive.org/web/20040604041507/http://panda.cs.ndsu.nodak.edu/~achapwes/PICmicro/keyboard/atkeyboard.html
> > it is obvious what's going on: at_keyboard is using scankey set 1 but
> > the keyboard is using set 2 and the keyboard controller is not
> > translating.
> > The cause of the mismatch is the XLAT bit in the keyboard controller
> > command byte that transitions from 1 to 0 while grub executes
> > terminal_input at_keyboard. 
> [...]
> 
> Thanks for the debugging.  Would you be able to try with this upstream
> patch, which looks somewhat promising for this?
> 
>   
> http://git.savannah.gnu.org/gitweb/?p=grub.git;a=commitdiff;h=3c058332499f6c0185c167a7faf37afa808136b7
> 
> Thanks,
> 
> 

Have been away, seeing the message now.
I am willing to test the patch.
The patch does not look as I would expect, perhaps I am not understanding it 
(just read it, not applied).

But I have a job, with urgencies that won't allow free time for one or two 
weeks.

Be patient, if you decide to wait for me to test the patch.

Bye

Marco Gamberoni

_

PGP Fingerprint: 945C CE09 7D11 E1A0 5D8D  306E DAE1 C4A6 0BB3 7A16


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

Bug#780940: hdparm freeze's bug information

On Mon, 30 Mar 2015 22:25:17 -0300
=?ISO-8859-1?Q?V=EDctor_Cana_Ben=EDtez?=  wrote:
> Dear maintainers,
> 
> I have installed the hdparm package version 9.43-1ubuntu3 from ubuntu "vivid" 
> repository and it works fine. The package is the following:
> http://packages.ubuntu.com/vivid/hdparm
> 
> Regards.
> 
> 

Victor: Do you have a "SATA DEVSLP" / "DevSleep" disk?

The list of changes between the Debian version and the Ubuntu version is
fairly short.  I have attached the diff (minus d/changelog) here and we
are down to:

"""
 debian/95hdparm-apm |5 +++--
 debian/control  |5 +++--
 debian/hdparm.init  |5 -
 debian/hdparm.udev  |4 ++--
 debian/rules|3 +--
 hdparm.c|   42 ++
 identify.c  |8 
 sgio.h  |1 +
 8 files changed, 56 insertions(+), 17 deletions(-)
"""

Given you suggest that compiling the new upstream also works for you, I
am suspecting it could be this change:

"""
+  * hdparm.c, identify.c, sgio.h: import patch from
+http://sourceforge.net/p/hdparm/patches/35/ to add support to
'hdparm -I'
+for reporting DevSleep information.  LP: #1031173.
"""

Which brings us to the DevSleep disk.  Sadly, I am not sure I see how
the actual change matters (unless hdparm handles "unknown" disks
differently from "known" disks) - or the code does something beyond what
I can trivially guess from the changes.

Failing that, Ubuntu also removed the "hdparm-resync.lock".  Assuming
what we exactly see is a deadlock and "timeout" killing hdparm to
workaround said deadlock.  But at this point, I am guessing!

Thanks,
~Niels

https://bugs.launchpad.net/intel/+bug/1031173

hdparm-ubuntu.diff
Description: application/mbox

Bug#780096: RFS: dyfi/1.2.0-1 [ITP #779708]

2015-03-31 Thread Antti Järvinen

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello Eugene,

I noticed your RFS ticket and made a short review about the package. 
I'm not a DD so I can't sponsor your package but hopefully this 
is useful for someone considering sponsorship.

So, the comments:
about debian/config:
 - Is it necessary to have condition 
   if [ $1 = "configure" ]; then
   ..
   fi
   around db_input/db_go -commands? I'm under impression that this 
   config-script might be run also on other situations than config ; 
   or is this intentional? 
about debian/copyright:
 - According to  
   https://lists.debian.org/debian-devel-announce/2006/03/msg00023.html
   you should have, among other things in the copyright file the authors 
   name and year of the copyright. Year is missing for "Files: *"
   and then I'm not sure if "dy.fi admins" count as name of 
   author ; I understand that there may be real organization of
   human behind dy.fi that have developed the sw but .. naming
   a person, a company or other entity that may be recognized 
   by rule of law (in Finland?) might be a jolly good idea?
 - There are "Files-Excluded" mentioned in copyright ; it might be
   required to explicitly state that they may be distributed anyway,
   for example using "permissive" license, if the files fall into
   such category. 
about debian/po/templates.pot Minor whining: 
   When username is queried, would it be nice to indicate that 
   this is exactly "dy.fi system username" and not just "username"
   or is this going to be very clear in advance to person doing
   the installation? I understood that the user account needs to
   exists beforehand..
about debian/postinst
   What is going to be file permission of /etc/dyfi-update.conf ? 
   It may contain user account + password to remote box? 

general:
   There is no documentation of any kind. Maybe a short manpage might
   be in order? 

The perl-script itself seems to start and start doing its job (I could not 
really verify as I do not have dy.fi user account), also the daemon
is stopped upon uninstall (that is going to happen to a lot of users
who install this and then notice that service is available in finland only..).

- --
Antti Järvinen

-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: Processed by Mailcrypt 3.5.8 

iD8DBQFVGtyNUTdja+nNMWMRAoT7AJ46cYaIve87oib+T9YDeZWKPU6rzwCfQyL0
fHf3Hs2owx9VKKalPym6RTo=
=wzro
-END PGP SIGNATURE-


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

Bug#781625: arduino-mk should depend or recommend screen

2015-03-31 Thread Baruch Even

Subject: arduino-mk: missing dependency on screen
Package: arduino-mk
Version: 1.3.4-1
Severity: normal

Dear Maintainer,

Using "make monitor" tries to fire up screen and that failed since
screen wasn't installed for me (new system). arduino-mk should depend or
at least recommend on screen to hint to the user that he should install
something else.

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

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

Versions of packages arduino-mk depends on:
ii  arduino-core   2:1.0.5+dfsg2-4
ii  python 2.7.9-1
ii  python-serial  2.6-1.1

arduino-mk recommends no packages.

arduino-mk 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#750837: ITP: moarvm -- virtual machine for Rakudo Perl 6 and NQP

2015-03-31 Thread Dominique Dumont

Hello Daniel

I've used moarvm package as a test case for 'cme update dpkg-copyright'.

Turns out that some copyright entries from 3rdparty directories were missing.
There were also some minor mistakes in the copyright owners. There's a better
chance of having moarvm go through ftp-masters without missing entries in
copyright file...

I've also added a 'fix.scanned.copyright' file in debian to work around some
limitations (or bugs) of licensecheck command.

Last but not least: your previous work on debian/copyright is not wasted:
some files cannot be scanned and 'cme update' did reuse the data you've
created.
The fix.scanned.copyright file [1] is needed for files where licensecheck
returns
bogus data.

I've pushed the new debian copyright file [2] to copyright-cme-update branch on
pkg-moarvm repo. Feel free to pick up what you want from this file or simply
merge it on master.

I also found (manually, cme is not that magic ;-p ) that the license you
flagged as "Other" is a MIT variant. This update is pushed on master. [3]

Once the copyright is done, I don't see any other issue to upload moarvm.

All the best

[1]
https://anonscm.debian.org/cgit/pkg-rakudo/pkg-moarvm.git/tree/debian/fix.scanned.copyright?h=copyright-cme-update
[2]
https://anonscm.debian.org/cgit/pkg-rakudo/pkg-moarvm.git/tree/debian/copyright?h=copyright-cme-update
[3] https://anonscm.debian.org/cgit/pkg-rakudo/pkg-moarvm.git/commit/

--
https://github.com/dod38fr/ -o- http://search.cpan.org/~ddumont/
http://ddumont.wordpress.com/ -o- irc: dod at irc.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#781623: harminv: new upstream version (1.4)

2015-03-31 Thread Steven G. Johnson

Package: harminv
Severity: normal

A new upstream version of harminv (1.4) is now available; please consider
updating as it fixes a bug that prevented some features of harminv from
working on non-x86 architectures.

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

Kernel: Linux 2.6.32-5-amd64 (SMP w/16 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash


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

Bug#781624: meep: new upstream version (1.3)

2015-03-31 Thread Steven G. Johnson

Package: meep
Severity: normal

Version 1.3 of Meep is now available upstream.  It corrects a couple of
minor problems and adds one major new feature (near-to-far-field transforms).

It also supports the latest version (1.4) of harminv, which you should also
consider updating in order to improve compatibility with non-x86 arches.

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

Kernel: Linux 2.6.32-5-amd64 (SMP w/16 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash


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

Bug#781622: RFS: opentyrian/2.1.20130907-1 [ITP]

2015-03-31 Thread Etienne Millon

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

 * Package name: opentyrian
   Version : 2.1.20130907-1
   Upstream Author : The OpenTyrian Development Team
 * URL : https://bitbucket.org/opentyrian/opentyrian/wiki/Home
 * License : GPL-2+
   Section : games

It builds those binary packages:

opentyrian - open-source port of the DOS shoot-em-up Tyrian

OpenTyrian (ITP #553035) is a free engine for non-free game tyrian,
whose assets are downloaded by game-data-packager.

I uploaded a package on mentors and it is dgettable at the following
URL:

dget -x 
http://mentors.debian.net/debian/pool/contrib/o/opentyrian/opentyrian_2.1.20130907-1.dsc

Alternatively, you may access the git repository at:

git+ssh://git.debian.org/git/pkg-games/opentyrian.git

I'm happy to hear your remarks about this package. Also, please note
that I'm a Debian Maintainer, so once this clears NEW I'm interested
in uploading the next revisions myself. Thanks!

-- 
Etienne Millon


signature.asc
Description: Digital signature

Bug#781579: unblock (pre-approval): postgis/2.1.4+dfsg-3

2015-03-31 Thread Adam D. Barratt

Control: tags -1 + confirmed moreinfo

On Tue, 2015-03-31 at 11:14 +0200, Markus Wanner wrote:
> I would like to upload postgis-2.1.4+dfsg-3 for jessie via unstable.
> This applies a minimally invasive upstream patch to fix a security issue.

Please go ahead, and remove the "moreinfo" tag once the package is in
unstable.

Regards,

Adam


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

Bug#781621: unblock: tiff/4.0.3-12.3

2015-03-31 Thread Moritz Muehlenhoff

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

Please unblock package tiff. It fixes the last missing bit of
CVE-2014-8128.

unblock tiff/4.0.3-12.3

Cheers,
Moritz

debdiff:

diff -Nru tiff-4.0.3/debian/changelog tiff-4.0.3/debian/changelog
--- tiff-4.0.3/debian/changelog 2015-03-13 23:56:01.0 +0100
+++ tiff-4.0.3/debian/changelog 2015-03-23 19:25:35.0 +0100
@@ -1,3 +1,10 @@
+tiff (4.0.3-12.3) unstable; urgency=medium
+
+  * Add another (final) patch for CVE-2014-8128 (Bug #2499). Thanks to
+Petr Gajdos
+
+ -- Moritz Muehlenhoff   Mon, 23 Mar 2015 18:26:40 +0100
+
 tiff (4.0.3-12.2) unstable; urgency=medium
 
   * Add another patch for CVE-2014-8128 (Bug #2501)
diff -Nru tiff-4.0.3/debian/patches/CVE-2014-8128-5.patch 
tiff-4.0.3/debian/patches/CVE-2014-8128-5.patch
--- tiff-4.0.3/debian/patches/CVE-2014-8128-5.patch 1970-01-01 
01:00:00.0 +0100
+++ tiff-4.0.3/debian/patches/CVE-2014-8128-5.patch 2015-03-23 
19:25:03.0 +0100
@@ -0,0 +1,14 @@
+Patches by Petr Gajdos (pgaj...@suse.cz) from
+http://bugzilla.maptools.org/show_bug.cgi?id=2499
+
+--- tiff-4.0.3.orig/libtiff/tif_dirinfo.c
 tiff-4.0.3/libtiff/tif_dirinfo.c
+@@ -141,6 +141,8 @@ tiffFields[] = {
+   { TIFFTAG_FAXDCS, -1, -1, TIFF_ASCII, 0, TIFF_SETGET_ASCII, 
TIFF_SETGET_ASCII, FIELD_CUSTOM, TRUE, FALSE, "FaxDcs", NULL },
+   { TIFFTAG_STONITS, 1, 1, TIFF_DOUBLE, 0, TIFF_SETGET_DOUBLE, 
TIFF_SETGET_UNDEFINED, FIELD_CUSTOM, 0, 0, "StoNits", NULL },
+   { TIFFTAG_INTEROPERABILITYIFD, 1, 1, TIFF_IFD8, 0, 
TIFF_SETGET_UNDEFINED, TIFF_SETGET_UNDEFINED, FIELD_CUSTOM, 0, 0, 
"InteroperabilityIFDOffset", NULL },
++  { TIFFTAG_CONSECUTIVEBADFAXLINES, 1, 1, TIFF_LONG, 0, 
TIFF_SETGET_UINT32, TIFF_SETGET_UINT32, FIELD_CUSTOM, TRUE, FALSE, 
"ConsecutiveBadFaxLines", NULL },
++{ TIFFTAG_PREDICTOR, 1, 1, TIFF_SHORT, 0, TIFF_SETGET_UINT16, 
TIFF_SETGET_UINT16, FIELD_CUSTOM, FALSE, FALSE, "Predictor", NULL },
+   /* begin DNG tags */
+   { TIFFTAG_DNGVERSION, 4, 4, TIFF_BYTE, 0, TIFF_SETGET_C0_UINT8, 
TIFF_SETGET_UNDEFINED, FIELD_CUSTOM, 0, 0, "DNGVersion", NULL },
+   { TIFFTAG_DNGBACKWARDVERSION, 4, 4, TIFF_BYTE, 0, TIFF_SETGET_C0_UINT8, 
TIFF_SETGET_UNDEFINED, FIELD_CUSTOM, 0, 0, "DNGBackwardVersion", NULL },
diff -Nru tiff-4.0.3/debian/patches/series tiff-4.0.3/debian/patches/series
--- tiff-4.0.3/debian/patches/series2015-03-13 23:57:19.0 +0100
+++ tiff-4.0.3/debian/patches/series2015-03-23 19:24:49.0 +0100
@@ -18,3 +18,5 @@
 CVE-2014-8129.patch
 CVE-2014-9655.patch
 CVE-2014-8128-4.patch
+
+CVE-2014-8128-5.patch


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

Kernel: Linux 3.16.0-4-amd64 (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
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#781612: libglib2.0-0: segfault in xfdesktop

Control: reassign -1 xfdesktop4

Am 31.03.2015 um 17:36 schrieb Christian Knoke:
> Package: libglib2.0-0
> Version: 2.33.12+really2.32.4-5
> Severity: normal
> 
> xfdesktop[3612]: segfault at ffa6 ip b6c7e4a7 sp bffe15c8 error 4 in 
> libgobject-2.0.so.0.3200.4[b6c4c000+5]
> 

More likely a bug in xfdesktop, therefor re-assigning.


-- 
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#781602: systemd: Invalid DBus call causes systemd to stop responding to DBus alltogether

Control: fixed -1 219-5
Control: tags -1 fixed-upstream

Am 31.03.2015 um 17:46 schrieb Christian Seiler:
> On 03/31/2015 04:44 PM, Michael Biebl wrote:

>> Hm, that's indeed nasty. Have you tried if v219 is affected by this as
>> well? If so, it would be worth raising this upstream.
> 
> I don't have anything here running Debian experimental, but I still have
> a VM with Fedora Rawhide (systemd-219) and there I get the following error:
> 
> Error org.freedesktop.DBus.Error.InvalidArgs: Incorrect parameters for
> property 'LogLevel', expected 's', got ''.
> (which is what I would have expected, so v219 doesn't appear to be
> affected by this bug)

Thanks for testing, marking as fixed for that version.

> So it appears this is fixed upstream already. Unfortunately, I don't
> have time to investigate right now (maybe next week).


-- 
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#781620: CVE-2015-2751 CVE-2015-2752 CVE-2015-2756

2015-03-31 Thread Moritz Muehlenhoff

Source: xen
Severity: important
Tags: security

Please see
http://xenbits.xen.org/xsa/advisory-125.html
http://xenbits.xen.org/xsa/advisory-126.html
http://xenbits.xen.org/xsa/advisory-127.html

Cheers,
Moritz


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

Bug#781615: systemd: Only boots in rescue mode

Am 31.03.2015 um 17:45 schrieb Christoph Egger:
> Package: systemd
> Version: 215-14
> Severity: important
> 
> Hi!
> 
> This system boots only in rescue mode (and sometimes with
> break=premount mount rootfs +Ctrl-D) but never "normally". I have a
> full bootlog in debug mode attached.
> 

Hi Christoph,


[   12.306905] systemd-fsck[171]: Executing: /lib/systemd/systemd-fsck
[   12.332491] systemd-fsck[171]: Info: Fix the reported corruption.
Trying to enqueue job reboot.target/start/replace
Fixing conflicting jobs reboot.target/stop,reboot.target/start by
deleting job reboot.target/stop
Deleting job systemd-reboot.service/stop as dependency of job
reboot.target/stop
Deleting job shutdown.target/stop as dependency of job
systemd-reboot.service/stop
Deleting job systemd-update-utmp-runlevel.service/start as dependency of
job shutdown.target/stop
Installed new job reboot.target/start as 126
Installed new job systemd-reboot.service/start as 127
Installed new job shutdown.target/start as 128


That looks odd: While the fsck is running, a reboot was scheduled.
Did you hit CTRL+ALT+DEL?

-- 
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#781615: systemd: Only boots in rescue mode

Am 31.03.2015 um 19:07 schrieb Michael Biebl:
> Am 31.03.2015 um 17:45 schrieb Christoph Egger:
>> Package: systemd
>> Version: 215-14
>> Severity: important
>>
>> Hi!
>>
>> This system boots only in rescue mode (and sometimes with
>> break=premount mount rootfs +Ctrl-D) but never "normally". I have a
>> full bootlog in debug mode attached.
>>
> 
> Hi Christoph,
> 
> 
> [   12.306905] systemd-fsck[171]: Executing: /lib/systemd/systemd-fsck
> [   12.332491] systemd-fsck[171]: Info: Fix the reported corruption.
> Trying to enqueue job reboot.target/start/replace
> Fixing conflicting jobs reboot.target/stop,reboot.target/start by
> deleting job reboot.target/stop
> Deleting job systemd-reboot.service/stop as dependency of job
> reboot.target/stop
> Deleting job shutdown.target/stop as dependency of job
> systemd-reboot.service/stop
> Deleting job systemd-update-utmp-runlevel.service/start as dependency of
> job shutdown.target/stop
> Installed new job reboot.target/start as 126
> Installed new job systemd-reboot.service/start as 127
> Installed new job shutdown.target/start as 128
> 
> 
> That looks odd: While the fsck is running, a reboot was scheduled.
> Did you hit CTRL+ALT+DEL?
> 

Or is this caused by

Job local-fs.target/sta[   12.366051] Copyright (C) 2004 MontaVista
Software - IPMI Powerdown via sys_reboot.

-- 
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#755202: network-manager: keeps creating and using new connection "eth0" that does not work