Bug#685351: Help: Please seek for sources of some JS files in GNUmed [Was: Bug#685351: src:gnumed-client: Missing source code for *.js files]

[Andreas Tille]

Hi Sebastian,

first I want to say that I will check later which JS we are really using
- I remember that I injected Debian replacements and so we can safely drop
the sources.  Need to check this when I find some couple of minutes spare
time.

On Fri, Sep 07, 2012 at 06:29:26AM +0200, Sebastian Hilbert wrote:
> I was not aware those js files are somehow compressed. I was under the 
> impression these files are pure source files.

These are for sure ASCII files which you might be able to edit but it is
not considered as "source" because comments and blanks are removed and
probably some other optimisations.  If you have time you might like to
read the longish thread about this on debian-devel list (I only browsed
a small amount of it).

> If not please drop the js files as 
> the doc packge will work without them. Output will just look a bit uglier but 
> I don't care. So before dropping content please consider dropping styling.

OK, message taken.  I hope to have this ready at beginning of next week.

Kind regards

   Andreas. 

-- 
http://fam-tille.de


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

Bug#685351: Help: Please seek for sources of some JS files in GNUmed [Was: Bug#685351: src:gnumed-client: Missing source code for *.js files]

[Sebastian Hilbert]

Hi Andreas,

On Thursday, September 06, 2012 09:53:19 PM Andreas Tille wrote:

> Hi Sebastian,
> 
> On Mon, Aug 27, 2012 at 08:20:14PM +0200, Sebastian Hilbert wrote:
> > > after reading the bug report twice I noticed that the problem is
> > > actually not comparable to the issue discussed currently on
> > > debian-devel@l.d.o, because the files are actually used in the
> > > package and not replaced.  So if you want to help Debian Med you
> > > can do some research and find the sources of the following files
> > > 
> > > inside the gnumed-doc package:
> > >   user-manual/rsrc/System/JSTreeContrib/jquery.jstree.js
> > 
> > http://www.jstree.com/documentation
> > MIT or GPL2
> > 
> > >   user-manual/rsrc/System/JQueryPlugin/plugins/foswiki/jquery.foswiki.js
> > 
> > http://foswiki.org/Extensions/JQueryPlugin
> > GPL
> > 
> > >   user-manual/rsrc/System/PatternSkin/pattern.js
> > 
> > http://trac.foswiki.org/browser/trunk/PatternSkin/lib/Foswiki/Contrib/Patt
> > ernSkin.pm?rev=14650
> > 
> > part of PatterSkin
> > 
> > GPL
> 
> I tried to check these links.  I think it needs some clarification:
> There is no real doubt that the code is GPL.  The main problem is that
> we need to have the source code of the files that were used and which
> could be used to reproduce the compressed *.js files.  I did not found
> those very files which we could include as copy into the package.
> 
> > >   user-manual/rsrc/System/JavascriptFiles/foswikiForm.js
> > 
> > http://www.koders.com/javascript/fid7DAA754986238FA7FE093BDE7031C706AB24FB
> > E2.aspx?s=form#L6
> > 
> > Apache Version 2
> > 
> > >   user-manual/rsrc/System/JavascriptFiles/foswikiString.js
> > 
> > http://trac.foswiki.org/browser/trunk/core/pub/System/JavascriptFiles/fosw
> > ikiString_src.js
> > 
> > GPL
> > 
> > >   user-manual/rsrc/System/JavascriptFiles/foswikiPref.js
> > 
> > http://trac.foswiki.org/browser/trunk/core/pub/System/JavascriptFiles/fosw
> > ikiPref_src.js
> > 
> > GPL
> > 
> > All files stem from a default install of Foswiki
> 
> It seems these *.js files could be fetched from VCS and these are OK.
> 
> In short:  If we do not find the real source files of the part above
> we should probably remove them from the gnumed-client tarball and
> drop the gnumed-doc package (which would be a shame IMHO).
>

I was not aware those js files are somehow compressed. I was under the 
impression these files are pure source files. If not please drop the js files 
as 
the doc packge will work without them. Output will just look a bit uglier but 
I don't care. So before dropping content please consider dropping styling.

Regards,
Sebastian
 
> Kind regards
> 
>   Andreas.


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

Bug#686356: unblock: aspcud/2011.03.17.dfsg-6

[Ralf Treinen]

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

Please unblock aspcud_2011.03.17.dfsg-6. The version currently in testing
(-4) has an RC bug #686356 which is fixed in version (-5) of the package,
but that package had some accidential changes which are fixed in (-6).

About bug #686356: this fixes an incompatibility with clasp 2.1 which
is in sid, while the version (-4) currently in testing works fine with
the version 2.0 of clasp currently in testing. However, this may cause
trouble in future upgrades from wheezy. The solution adopted is a patch
provided by upstream which makes aspcud work with both versions of
clasp (2.0 and 2.1). 

Debdiff between (-6) and (-4) is attached. Besides the mentionend patch it
contains minor fixes to debian/copyright.

Cheers -Ralf.
-- 
Ralf Treinen
Laboratoire Preuves, Programmes et Systèmes
Université Paris Diderot, Paris, France.
http://www.pps.univ-paris-diderot.fr/~treinen/
=> New email address: trei...@pps.univ-paris-diderot.fr <=
diff -Nru aspcud-2011.03.17.dfsg/debian/changelog 
aspcud-2011.03.17.dfsg/debian/changelog
--- aspcud-2011.03.17.dfsg/debian/changelog 2012-05-15 04:09:42.0 
+0900
+++ aspcud-2011.03.17.dfsg/debian/changelog 2012-09-07 10:43:31.0 
+0900
@@ -1,3 +1,24 @@
+aspcud (2011.03.17.dfsg-6) unstable; urgency=low
+
+  * Restored build-dependency on libboost-dev which was accidentially
+changed in the last upload.
+  * Restored changelog-entry of version 2011.03.17.dfsg-4 that was 
+accidentially mangled in the upload of 2011.03.17.dfsg-5.
+
+ -- Ralf Treinen   Fri, 07 Sep 2012 10:33:50 +0900
+
+aspcud (2011.03.17.dfsg-5) unstable; urgency=low
+
+  * Patch clasp-2.1-apichange: make aspcud work both with clasp 2.0 and
+clasp 2.1. Thanks a lot to Roland Kaminski for the patch
+(closes: #686356).
+  * debian/copyright:
+- Fixed typo (Licence -> License)
+- separate paragraph for the GPL3 license
+- text of the "public domain" license.
+  
+ -- Ralf Treinen   Sun, 02 Sep 2012 22:54:51 +0900
+
 aspcud (2011.03.17.dfsg-4) unstable; urgency=low
 
   * Replace build-dependency on libboost1.46-dev by libboost-dev (closes:
diff -Nru aspcud-2011.03.17.dfsg/debian/copyright 
aspcud-2011.03.17.dfsg/debian/copyright
--- aspcud-2011.03.17.dfsg/debian/copyright 2012-05-15 04:15:26.0 
+0900
+++ aspcud-2011.03.17.dfsg/debian/copyright 2012-09-07 10:37:22.0 
+0900
@@ -3,7 +3,7 @@
 Upstream-Contact: Roland Kaminski 
 Source: https://potassco.svn.sourceforge.net/svnroot/potassco/trunk/aspcud/
 Copyright: 2010, Roland Kaminski 
-Licence: GPL-3+
+License: GPL-3+
 Comment: cmake/macros.cmake has been removed from the tarball since it
   has a BSD licence.
 
@@ -12,9 +12,8 @@
 License: GPL-3+
 
 Files: lemon/*
-Copyright: disclaimed by the author
 License: public-domain
- The author of this program disclaims copyright.
+ The author disclaims copyright to this source code.
 
 Files: libprogram_opts/*
 Copyright: 2006-2007, Benjamin Kaufmann
@@ -44,6 +43,3 @@
  On Debian systems, the full text of the GNU General Public
  License version 3 can be found in the file
  `/usr/share/common-licenses/GPL-3'.
-
-
-
diff -Nru aspcud-2011.03.17.dfsg/debian/patches/clasp-2.1-apichange 
aspcud-2011.03.17.dfsg/debian/patches/clasp-2.1-apichange
--- aspcud-2011.03.17.dfsg/debian/patches/clasp-2.1-apichange   1970-01-01 
09:00:00.0 +0900
+++ aspcud-2011.03.17.dfsg/debian/patches/clasp-2.1-apichange   2012-09-02 
16:17:08.0 +0900
@@ -0,0 +1,16 @@
+diff -rup aspcud_2011.03.17.dfsg.orig/scripts/aspcud.sh 
aspcud_2011.03.17.dfsg/scripts/aspcud.sh
+--- aspcud_2011.03.17.dfsg.orig/scripts/aspcud.sh  2011-03-14 
17:52:27.0 +0100
 aspcud_2011.03.17.dfsg/scripts/aspcud.sh   2012-09-01 13:00:35.0 
+0200
+@@ -62,7 +62,11 @@ base="$(dirname "$(readlink -f "$0")")"
+ PATH=".:$base:$base/../build/release/bin:$PATH"
+ 
+ # default options
+-clasp_opts_def=( "--opt-he=1" "--sat" "--restarts=32" "--heu=VSIDS" 
"--restart-o" "--opt-hi=2" )
++if clasp -v | grep -q "clasp 2.0"; then
++clasp_opts_def=( "--opt-he=1" "--sat" "--restarts=32" "--heu=VSIDS" 
"--restart-o" "--opt-hi=2" )
++else
++clasp_opts_def=( "--opt-he=1" "--sat" "--restarts=L,32" "--heu=VSIDS" 
"--restart-o" "--opt-hi=2" )
++fi
+ gringo_opts_def=( "$(enc configuration.lp)" "$(enc optimize-define.lp)" )
+ 
+ cudf_opts=( )
diff -Nru aspcud-2011.03.17.dfsg/debian/patches/series 
aspcud-2011.03.17.dfsg/debian/patches/series
--- aspcud-2011.03.17.dfsg/debian/patches/series2011-05-04 
05:21:50.0 +0900
+++ aspcud-2011.03.17.dfsg/debian/patches/series2012-09-02 
16:18:30.0 +0900
@@ -1,3 +1,4 @@
 pathes
 no-cmake-macros
 gcc4.6
+clasp-2.1-apichange

Bug#685726: linux-image-3.2.0-3-amd64: return error when trying to format image file (mkfs -t ext4 file.img)

[Ben Hutchings]

On Wed, 2012-08-29 at 14:11 -0400, Theodore Ts'o wrote:
> On Tue, Aug 28, 2012 at 04:09:05PM -0700, Ben Hutchings wrote:
> > As discussed, Linux 3.2.y needs a backport of the fixes for this, which
> > I think are:
> > 
> > 968dee7 ext4: fix hole punch failure when depth is greater than 0
> > 89a4e48 ext4: fix kernel BUG on large-scale rm -rf commands
> 
> I have a backport of these patches rebased onto 3.2.28.  They pass the
> full set of ext4 regression tests.  However, for some reason I wasn't
> able to reproduce the problem on 3.2.28, even though I thought:
> 
>  mke2fs -t ext4 /dev/vdd
>  mount -t ext4 /dev/vdd /vdd
>  dd if=/dev/zero of=/vdd/test.img bs=1M count=200
>  mke2fs -t ext4 -F /vdd/test.img
> 
> should have been a reliable reproduction with the problem.  I'm pretty
> sure it worked to trigger the problem before, but for some reason it's
> not working for me.
> 
> Anyway, here are the patches.  If someone could confirm wheterh this
> resolve your problem, I would really appreciate it.  Thanks!!

Please can you test the patches from the previous email?  There are
instructions for building a patched kernel package at
.

Ben.

-- 
Ben Hutchings
Usenet is essentially a HUGE group of people passing notes in class.
  - Rachel Kadel, `A Quick Guide to Newsgroup Etiquette'


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

Processed: tagging 685726

[Debian Bug Tracking System]

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

> tags 685726 - moreinfo
Bug #685726 [src:linux] linux-image-3.2.0-3-amd64: return error when trying to 
format image file (mkfs -t ext4 file.img)
Removed tag(s) moreinfo.
> thanks
Stopping processing here.

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


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

Bug#686894: npm: please run under nodejs, not node

[Aaron M. Ucko]

"Aaron M. Ucko"  writes:

> lines in /usr/bin/node and /usr/share/npm/bin/npm-cli.js to

That first should have been /usr/bin/npm, of course.

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


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

Processed: Updated da,es,fi,ko,pl,ro,vi debconf translations

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #686037 [gdm3] Out of date debconf translation
Severity set to 'serious' from 'normal'

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


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

Bug#686901: node-tilelive: please run under nodejs, not node

[Aaron M. Ucko]

Package: node-tilelive
Version: 4.2.1-3
Severity: grave
Justification: renders package unusable (uninstallable)

As you may have heard, nodejs's main executable is now /usr/bin/nodejs
rather than /usr/bin/node to avoid clashing with the unrelated "node"
package.  To accommodate that change, please update the

#!/usr/bin/env node

lines in /usr/bin/tilelive and /usr/bin/tilelive-copy

#!/usr/bin/env nodejs

or better yet

#!/usr/bin/nodejs

and version node-tilelive's dependency on nodejs to (>= 0.6.19~dfsg-1-3~).

Thanks!

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

Kernel: Linux 3.2.0-3-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


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

Bug#686900: node-mbtiles: please run under nodejs, not node

[Aaron M. Ucko]

Package: node-mbtiles
Version: 0.2.3-1
Severity: grave
Justification: renders package unusable (uninstallable)

As you may have heard, nodejs's main executable is now /usr/bin/nodejs
rather than /usr/bin/node to avoid clashing with the unrelated "node"
package.  To accommodate that change, please update /usr/bin/mb*'s

#!/usr/bin/env node

lines to

#!/usr/bin/env nodejs

or better yet

#!/usr/bin/nodejs

and version node-mbtiles's dependency on nodejs to (>= 0.6.19~dfsg-1-3~).

Thanks!

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

Kernel: Linux 3.2.0-3-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


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

Bug#686899: node-mapnik: please run under nodejs, not node

[Aaron M. Ucko]

Package: node-mapnik
Version: 0.6.7-2
Severity: grave
Justification: renders package unusable (uninstallable)

As you may have heard, nodejs's main executable is now /usr/bin/nodejs
rather than /usr/bin/node to avoid clashing with the unrelated "node"
package.  To accommodate that change, please update the

#!/usr/bin/env node

lines in /usr/bin/mapnik-inspect and /usr/bin/mapnik-render to

#!/usr/bin/env nodejs

or better yet

#!/usr/bin/nodejs

and version node-mapnik's dependency on nodejs to (>= 0.6.19~dfsg-1-3~).

Thanks!

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

Kernel: Linux 3.2.0-3-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


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

Bug#686898: node-get: please run node-get-file.js under nodejs, not node

[Aaron M. Ucko]

Package: node-get
Version: 1.1.5+ds1-1
Severity: grave
Justification: renders package unusable (uninstallable)

As you may have heard, nodejs's main executable is now /usr/bin/nodejs
rather than /usr/bin/node to avoid clashing with the unrelated "node"
package.  To accommodate that change, please update the

#!/usr/bin/env node

line in /usr/share/doc/node-get/examples/node-get-file.js to

#!/usr/bin/env nodejs

or better yet

#!/usr/bin/nodejs

and version node-get's dependency on nodejs to (>= 0.6.19~dfsg-1-3~).

Thanks!

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

Kernel: Linux 3.2.0-3-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


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

Bug#686897: carto: please run under nodejs, not node

[Aaron M. Ucko]

Package: carto
Version: 0.4.6+ds1-1
Severity: grave
Justification: renders package unusable (uninstallable)

As you may have heard, nodejs's main executable is now /usr/bin/nodejs
rather than /usr/bin/node to avoid clashing with the unrelated "node"
package.  To accommodate that change, please update the

#!/usr/bin/env node

lines in /usr/bin/carto and /usr/bin/mml2json to

#!/usr/bin/env nodejs

or better yet

#!/usr/bin/nodejs

and version carto's dependency on nodejs to (>= 0.6.19~dfsg-1-3~).

Thanks!

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

Kernel: Linux 3.2.0-3-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


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

Bug#686896: buddycloud-server: please run under nodejs, not node

[Aaron M. Ucko]

Package: buddycloud-server
Version: 0.3.1-1
Severity: grave
Justification: renders package unusable (uninstallable)

As you may have heard, nodejs's main executable is now /usr/bin/nodejs
rather than /usr/bin/node to avoid clashing with the unrelated "node"
package.  To accommodate that change, please update the

exec env node /usr/share/buddycloud-server/main.js $@

line in /usr/sbin/buddycloud-server to

exec nodejs /usr/share/buddycloud-server/main.js "$@"

(I made two other formal improvements there: env is redundant in this
context, and $@ works properly only when quoted.)

Also, please version buddycloud-server's dependency on nodejs to
(>= 0.6.19~dfsg-1-3~) to ensure that a nodejs executable will exist.

Thanks!

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

Kernel: Linux 3.2.0-3-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


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

Bug#686260: [LCFC] templates://mathematica-fonts/{templates,control}

[Atsuhito Kohda]

Hi David,

On Thu, 06 Sep 2012 07:23:17 -0400, David Prévot wrote:

>>> I think the "licesne itself" should not be translated
> 
> Sure, that's already covered by the “#flag:translate!:3-5”: starting

Thanks for your clarification!  It seems po-debconf becomes
smarter than before without notifying it to me ;-)

Best regards, 2012-9-7(Fri)

-- 
 Debian Developer - much more I18N of Debian
 Atsuhito Kohda 
 Department of Math., Univ. of Tokushima

Bug#686894: npm: please run under nodejs, not node

[Aaron M. Ucko]

Package: npm
Version: 1.1.4~dfsg-1
Severity: grave
Justification: renders package unusable

As you may have heard, nodejs's main executable is now /usr/bin/nodejs
rather than /usr/bin/node to avoid clashing with the unrelated "node"
package.  To accommodate that change, please update the

#!/usr/bin/env node

lines in /usr/bin/node and /usr/share/npm/bin/npm-cli.js to

#!/usr/bin/env nodejs

or better yet

#!/usr/bin/nodejs

and version npm's dependency on nodejs to (>= 0.6.19~dfsg-1-3~).  I'd
suggest additionally updating the .../bin/node references in
/usr/share/npm/doc/cli/folders.md and
/usr/share/doc/npm/doc/folders.html, but that's less critical.

Thanks!

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

Kernel: Linux 3.2.0-3-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 npm depends on:
ii  node-abbrev   1.0.3-1
ii  node-fstream  0.1.13-1
ii  node-graceful-fs  1.1.8-1
ii  node-ini  1.0.2-1
ii  node-minimatch0.2.0-1
ii  node-mkdirp   0.3.1-2
ii  node-node-uuid1.3.3-1
ii  node-nopt 1.0.10-2
ii  node-request  2.9.153-1
ii  node-rimraf   2.0.1-1
ii  node-semver   1.0.13-1
ii  node-tar  0.1.13-1
ii  node-which1.0.5-1
ii  nodejs0.6.19~dfsg1-2
ii  nodejs-dev0.6.19~dfsg1-2

npm recommends no packages.

npm suggests no packages.

-- no debconf information


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

Bug#640939: [Pkg-cups-devel] Bug#640939: Raising severity of 640939

[brian m. carlson]

On Wed, Sep 05, 2012 at 04:12:34PM +0100, Brian Potkin wrote:
> On Fri 29 Jun 2012 at 03:04:03 +, brian m. carlson wrote:
> 
> > # Default authentication type, when authentication is required...
> > DefaultAuthType Negotiate
> 
> You are using Kerberos? This could be a consequence of #663995. The
> original Red Hat report is at:
> 
>https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=837602
> 
> I tested this conjecture after installing and setting up Kerberos.

Well, yes, and no.  I have it set up for Kerberos, but I'm not actually
using it for anything at the moment.  I don't ever remotely administer
the cups server; I just SSH into it if I need to mess with the print
queues.

> 5. The error_log contained 12 lines of the form:
> 
>Authorized using Basic, expected Negotiate

My logs don't go back far enough for me to see whether this message
appeared.

> Progressing to the end of the install was a matter of pressing the Enter
> key each time the root password was asked for.

Yeah, that's it.  It looks like the issue here is that cups prompts to
use Basic authentication when there's no chance that will work.  So once
it stops doing that, the upgrade issue will go away automatically.

-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187


signature.asc
Description: Digital signature

Bug#686874: marked as done (cp2k: segfaults on i386 due to not aligning FFT arrays to 16 bytes for SSE2 and reusing them)

[Debian Bug Tracking System]

Your message dated Fri, 07 Sep 2012 00:02:41 +
with message-id 
and subject line Bug#686874: fixed in cp2k 2.2.426-6
has caused the Debian Bug report #686874,
regarding cp2k: segfaults on i386 due to not aligning FFT arrays to 16 bytes 
for SSE2 and reusing them
to be marked as done.

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

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


-- 
686874: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686874
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cp2k
Version: 2.2.426-1
Severity: serious

Since some months ago, fftw3 is using SSE2 instructions for fast fourier
transforms if the CPU supports it.  One requirement for this is that the
incoming arrays must be aligned to 16 bytes for the SIMD instructions.
This is the case on amd64 by default, but not on i386.

Usually, fftw3 will detect unaligned arrays and not use SSE2.  However,
if the same plan is originally executed with a properly aligned array
and then re-executed  with another, unaligned array, a segfault will
occur, see e.g. 
https://buildd.debian.org/status/fetch.php?pkg=cp2k&arch=i386&ver=2.2.426-5&stamp=1346699763

xxx
/build/buildd-cp2k_2.2.426-5-i386-rUGkvz/cp2k-2.2.426/tools/..//TEST-Linux-i686-gfortran-popt-2012-09-03T19:08:13+/QS/regtest-nmr-1/H2O-NMR-12.inp.out
max_diis:  4

eps_scf:1.00E-05
eps_scf_history:0.00E+00
eps_diis:   1.00E-01
eps_eigval: 1.00E-05

level_shift [a.u.]: 0.00

Mixing method:   DIRECT_P_MIXING

No outer SCF

Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

Backtrace for this error:
#0  0x56A8FF6B
#1  0x56A905AC
#2  0x555733FF
#3  0x55FE3C0B
#4  0x55F2008B
#5  0x55F22E9B
#6  0x55F23402
#7  0x55F22E9B
#8  0x55FC558B
#9  0x9666567 in fftw33d_ at fftw3_lib.F:196
#10  0x966195B in fft_3d_ at fft_lib.f90:135
#11  0x80C77D3 in __fft_tools_MOD_fft3d_s at fft_tools.F:441
#12  0x8340A58 in __pw_methods_MOD_fft_wrap_pw1pw2 at pw_methods.F:1462
#13  0x8EABD6D in __qs_collocate_density_MOD_density_rs2pw at 
qs_collocate_density.F:3433
#14  0x8EC0EF2 in __qs_collocate_density_MOD_calculate_rho_elec at 
qs_collocate_density.F:1392
#15  0x849ADDE in __qs_rho_methods_MOD_qs_rho_update_rho at qs_rho_methods.F:391
#16  0x84A1E30 in __qs_scf_MOD_scf_env_initial_rho_setup at qs_scf.F:2277
#17  0x84A9F28 in __qs_scf_MOD_init_scf_run at qs_scf.F:1810
#18  0x84B53A7 in __qs_scf_MOD_scf at qs_scf.F:368
#19  0x836FA1C in __qs_energy_MOD_qs_energies_scf at qs_energy.F:231
#20  0x80CD15C in __force_env_methods_MOD_force_env_calc_energy_force at 
force_env_methods.F:231
#21  0x8054D39 in __cp2k_runs_MOD_cp2k_run at cp2k_runs.F:403
#22  0x8058C1D in __cp2k_runs_MOD_run_input at cp2k_runs.F:1143
#23  0x804E2C5 in cp2k at cp2k.F:285
xxx

This problem is common enough (1/3 of the test cases segfaulted on the
autobuilder) that it makes cp2k pretty much unusable on i386.


Michael
--- End Message ---
--- Begin Message ---
Source: cp2k
Source-Version: 2.2.426-6

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

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

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

Debian distribution maintenance software
pp.
Michael Banck  (supplier of updated cp2k package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 07 Sep 2012 00:27:39 +0200
Source: cp2k
Binar

Bug#686893: node-vows: please run under nodejs, not node

[Aaron M. Ucko]

Package: node-vows
Version: 0.6.3-1
Severity: grave
Justification: renders package unusable (uninstallable)

As you may have heard, nodejs's main executable is now /usr/bin/nodejs
rather than /usr/bin/node to avoid clashing with the unrelated "node"
package.  To accommodate that change, please update /usr/bin/vows's

#!/usr/bin/env node

line to

#!/usr/bin/env nodejs

or better yet

#!/usr/bin/nodejs

and version node-vows's dependency on nodejs to (>= 0.6.19~dfsg-1-3~).

Thanks!

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

Kernel: Linux 3.2.0-3-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 node-vows depends on:
ii  node-eyes  0.1.7-1
ii  nodejs 0.6.19~dfsg1-2

Versions of packages node-vows recommends:
ii  coffeescript  1.3.3-1

node-vows suggests no packages.

-- no debconf information


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

Bug#686892: node-optimist: please run examples under nodejs, not node

[Aaron M. Ucko]

Package: node-optimist
Version: 0.3.1-1
Severity: grave
Justification: renders package unusable (uninstallable)

As you may have heard, nodejs's main executable is now /usr/bin/nodejs
rather than /usr/bin/node to avoid clashing with the unrelated "node"
package.  To accommodate that change, please update the

#!/usr/bin/env node

lines in /usr/share/doc/node-optimist/examples/*.js to

#!/usr/bin/env nodejs

or better yet

#!/usr/bin/nodejs

and version node-optimist's dependency on nodejs to (>= 0.6.19~dfsg-1-3~).

Thanks!

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

Kernel: Linux 3.2.0-3-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 node-optimist depends on:
ii  node-wordwrap  0.0.2-2
ii  nodejs 0.6.19~dfsg1-2

node-optimist recommends no packages.

node-optimist suggests no packages.

-- no debconf information


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

Bug#686891: node-jake: please run under nodejs, not node

[Aaron M. Ucko]

Package: node-jake
Version: 0.2.32-1
Severity: grave
Justification: renders package unusable (uninstallable)

As you may have heard, nodejs's main executable is now /usr/bin/nodejs
rather than /usr/bin/node to avoid clashing with the unrelated "node"
package.  To accommodate that change, please update /usr/bin/jake's

#!/usr/bin/env node

line to

#!/usr/bin/env nodejs

or better yet

#!/usr/bin/nodejs

and version node-jake's dependency on nodejs to (>= 0.6.19~dfsg-1-3~).

Thanks!

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

Kernel: Linux 3.2.0-3-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 node-jake depends on:
ii  nodejs  0.6.19~dfsg1-2

Versions of packages node-jake recommends:
ii  coffeescript  1.3.3-1
ii  node-glob 3.1.9-1

node-jake suggests no packages.

-- no debconf information


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

Bug#686890: node-express: please run under nodejs, not node

[Aaron M. Ucko]

Package: node-express
Version: 2.5.9-1
Severity: grave
Justification: renders package unusable (uninstallable)

As you may have heard, nodejs's main executable is now /usr/bin/nodejs
rather than /usr/bin/node to avoid clashing with the unrelated "node"
package.  To accommodate that change, please update /usr/bin/express's

#!/usr/bin/env node

line to

#!/usr/bin/env nodejs

or better yet

#!/usr/bin/nodejs

and version node-express's dependency on nodejs to (>= 0.6.19~dfsg-1-3~).

Thanks!

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

Kernel: Linux 3.2.0-3-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 node-express depends on:
ii  node-connect  1.7.3-1
ii  node-mime 1.2.5-1
ii  node-mkdirp   0.3.1-2
ii  node-qs   0.4.2-1
ii  nodejs0.6.19~dfsg1-2

node-express recommends no packages.

node-express suggests no packages.

-- no debconf information


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

Bug#686889: node-cli: please update examples to run nodejs, not node

[Aaron M. Ucko]

Package: node-cli
Version: 0.4.2~20120411-1
Severity: grave
Justification: renders package unusable (uninstallable)

As you may have heard, nodejs's main executable is now /usr/bin/nodejs
rather than /usr/bin/node to avoid clashing with the unrelated "node"
package.  To accommodate that change, please update the

#!/usr/bin/env node

lines in /usr/share/doc/node-cli/examples/*.js to

#!/usr/bin/env nodejs

or better yet

#!/usr/bin/nodejs

and version node-cli's dependency on nodejs to (>= 0.6.19~dfsg-1-3~).

Thanks!

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

Kernel: Linux 3.2.0-3-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 node-cli depends on:
ii  nodejs  0.6.19~dfsg1-2

node-cli recommends no packages.

node-cli suggests no packages.

-- no debconf information


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

Bug#666775: failing beanstalkd tests (was: Beanstalkd 1.5 .deb package)

[Keith Rarick]

On Thu, Aug 30, 2012 at 1:43 AM, Serafeim Zanikolas  wrote:
> Going back to the subject of the bug report, please let me know when you have
> a potential fix for the failing tests, and I'll test it on whatever arches you
> don't have access to.

Will do.


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

Bug#686188: [BTS#686188] templates://jffnms/{templates,control}

[David Prévot]

Control: tags -1 patch

Dear Debian maintainer,

On Wednesday, August 29, 2012, I notified you of the beginning of a
review process concerning debconf templates for jffnms.

The debian-l10n-english contributors have now reviewed these templates,
and the final proposed changes are attached to this update to the
original bug report.

Please review the suggested changes, and if you have any objections, let
me know in the next 3 days.

However, please try to avoid uploading jffnms with these changes right now.

The second phase of this process will begin on Sunday, September 8,
2012, when I will coordinate updates to translations of debconf templates.

The existing translators will be notified of the changes: they will
receive an updated PO file for their language.

Simultaneously, a general call for new translations will be sent to
the debian-i18n mailing list.

Both these calls for translations will request updates to be sent as
individual bug reports. That will probably trigger a lot of bug
reports against your package, but these should be easier to deal with.

The call for translation updates and new translations will run until
about Tuesday, September 18, 2012. Please avoid uploading a package with
fixed or changed debconf templates and/or translation updates in the
meantime. Of course, other changes are safe.

Please note that this is an approximative delay, which depends on my
own availability to process this work and is influenced by the fact
that I simultaneously work on many packages.

Around Wednesday, September 19, 2012, I will contact you again and will
send a final patch summarizing all the updates (changes to debconf
templates, updates to debconf translations and new debconf translations).

Again, thanks for your attention and cooperation.

Regards

David


diff -Nru --exclude po jffnms-0.9.3/debian/changelog jffnms-0.9.3/debian/changelog
--- jffnms-0.9.3/debian/changelog	2012-06-11 02:23:14.0 -0400
+++ jffnms-0.9.3/debian/changelog	2012-09-06 18:41:54.0 -0400
@@ -1,3 +1,10 @@
+jffnms (0.9.3-3) UNRELEASED; urgency=low
+
+  * Review templates and package description by the debian-l10n-english team.
+(Closes: #686188)
+
+ -- David Prévot   Thu, 06 Sep 2012 18:40:50 -0400
+
 jffnms (0.9.3-2) unstable; urgency=low
 
   * Fixed db upgrade scripts Closes: #675279
diff -Nru --exclude po jffnms-0.9.3/debian/control jffnms-0.9.3/debian/control
--- jffnms-0.9.3/debian/control	2012-06-11 02:22:09.0 -0400
+++ jffnms-0.9.3/debian/control	2012-09-06 18:29:49.0 -0400
@@ -16,17 +16,17 @@
 Recommends: ntp, nmap, fping
 Suggests: tac-plus, snmpd, syslog-ng, tftpd, smsclient
 Pre-Depends: debconf | debconf-2.0
-Description: web-based Network Management System (NMS) for IP networks
- JFFNMS is a Network Management System designed to maintain an IP SNMP, Syslog
- and/or  Tacacs+  Network. It can be used to monitor any standards compliant 
- SNMP device, Server, TCP port or Custom Poller, also it has some Cisco 
- oriented features. 
+Description: PHP Network Management System
+ JFFNMS is a Network Management System designed to help maintain a network
+ running SNMP, syslog, and/or TACACS+. It can monitor any standards-compliant
+ SNMP device, server, TCP port or custom poller, and also has some
+ Cisco-oriented features.
  .
- Features Summary
-  * Written in PHP (works in PHP5)
-  * PHP/cron scripts for polling, analizing and consolidating data
-  * Database Backend MySQL or PostgreSQL
-  * Configurable Event Types and Severity Levels
-  * Modular and Extensible
-  * Advanced Event Filter
-  * Interface & Host/Network Autodiscovery
+ Its features include:
+  * written in PHP;
+  * PHP/cron scripts for polling, analyzing, and consolidating data;
+  * MySQL or PostgreSQL database back-end;
+  * configurable event types and severity levels;
+  * modular and extensible;
+  * advanced event filter;
+  * interface, host, and network autodiscovery.
diff -Nru --exclude po jffnms-0.9.3/debian/templates jffnms-0.9.3/debian/templates
--- jffnms-0.9.3/debian/templates	2012-03-03 23:31:45.0 -0400
+++ jffnms-0.9.3/debian/templates	2012-09-06 18:40:47.0 -0400
@@ -1,40 +1,48 @@
+# These templates have been reviewed by the debian-l10n-english
+# team
+#
+# If modifications/additions/rewording are needed, please ask
+# debian-l10n-engl...@lists.debian.org for advice.
+#
+# Even minor modifications require translation updates and such
+# changes should be coordinated with translators and reviewers.
+
 Template: jffnms/erroruid
 Type: error
 _Description: jffnms user already exists
- The preinstall script for JFFNMS tried to create a JFFNMS user but there
- was already a user of that name so it has aborted installation.  Please
- read /usr/share/doc/jffnms/README.Debian for more information.
+ The installation has been aborted because there is already a user
+ with the name "jffnms". See /usr/share/doc/jffnms/README.Debian.
 
 Template: jffnms/errorgid
 Type: error
 _Description: jf

Processed: [BTS#686188] templates://jffnms/{templates,control}

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #686188 [jffnms] Please allow translation of all debconf templates
Added tag(s) patch.

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


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

Bug#686883: node-bones: please run nodejs, not node (in simple example)

[Aaron M. Ucko]

Package: node-bones
Version: 2.0.1+ds1-1
Severity: grave
Justification: renders package unusable (uninstallable)

As you may have heard, nodejs's main executable is now /usr/bin/nodejs
rather than /usr/bin/node to avoid clashing with the unrelated "node"
package.  To accommodate that change, please update the

#!/usr/bin/env node

line in /usr/share/doc/node-bones/examples/simple/index.js to

#!/usr/bin/env nodejs

or better yet

#!/usr/bin/nodejs

and version node-bones's dependency on nodejs to (>= 0.6.19~dfsg-1-3~).

Thanks!

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

Kernel: Linux 3.2.0-3-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 node-bones depends on:
ii  libjs-backbone   0.5.3-2
ii  node-express 2.5.9-1
ii  node-jquery  1.6.3-1
ii  node-mirror  0.3.3-2
ii  node-optimist0.3.1-1
ii  node-underscore  1.3.3-1
ii  nodejs   0.6.19~dfsg1-2

node-bones recommends no packages.

node-bones suggests no packages.

-- no debconf information


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

Processed: java-package: diff for NMU version 0.50+nmu1

[Debian Bug Tracking System]

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

> tags 685082 + patch
Bug #685082 [java-package] debconf abuse
Added tag(s) patch.
> tags 685082 + pending
Bug #685082 [java-package] debconf abuse
Added tag(s) pending.
> thanks
Stopping processing here.

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


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

Bug#685082: java-package: diff for NMU version 0.50+nmu1

[David Prévot]

tags 685082 + patch
tags 685082 + pending
thanks

Dear maintainer,

I've prepared an NMU for java-package (versioned as 0.50+nmu1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

It's almost a cherry-pick of 262a79a and 0851561 from your repository.

I'll take care of the unblock request.

Regards.

David
diff -Nru java-package-0.50/debian/changelog java-package-0.50+nmu1/debian/changelog
--- java-package-0.50/debian/changelog	2012-02-19 14:13:36.0 -0400
+++ java-package-0.50+nmu1/debian/changelog	2012-09-06 18:38:09.0 -0400
@@ -1,3 +1,10 @@
+java-package (0.50+nmu1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Drop installation debconf note. Closes: #685082
+
+ -- David Prévot   Thu, 06 Sep 2012 18:38:03 -0400
+
 java-package (0.50) unstable; urgency=low
 
   * Java-package reset for reintroduction in debian (removal of all
diff -Nru java-package-0.50/debian/control java-package-0.50+nmu1/debian/control
--- java-package-0.50/debian/control	2012-02-19 13:54:57.0 -0400
+++ java-package-0.50+nmu1/debian/control	2012-09-06 18:38:27.0 -0400
@@ -10,8 +10,7 @@
 
 Package: java-package
 Architecture: all
-Depends:  ${misc:Depends}, debhelper, fakeroot, unzip, libx11-6, libasound2,
- debconf (>= 0.5) | debconf-2.0
+Depends: ${misc:Depends}, debhelper, fakeroot, unzip, libx11-6, libasound2
 Recommends: dpkg-dev, gcc
 Suggests: openjdk-6-jre, openjdk-7-jre
 Description: Utility for creating Java Debian packages
diff -Nru java-package-0.50/debian/postinst java-package-0.50+nmu1/debian/postinst
--- java-package-0.50/debian/postinst	2012-02-19 13:45:36.0 -0400
+++ java-package-0.50+nmu1/debian/postinst	1969-12-31 20:00:00.0 -0400
@@ -1,14 +0,0 @@
-#!/bin/sh
-
-set -e
-
-if [ "$1" = "configure" ]
-then
-	. /usr/share/debconf/confmodule
-	db_input high java-package/postinst-note || true
-	db_go
-fi
-
-#DEBHELPER#
-
-exit 0
diff -Nru java-package-0.50/debian/prerm java-package-0.50+nmu1/debian/prerm
--- java-package-0.50/debian/prerm	2012-02-19 13:45:45.0 -0400
+++ java-package-0.50+nmu1/debian/prerm	1969-12-31 20:00:00.0 -0400
@@ -1,13 +0,0 @@
-#!/bin/sh
-
-set -e
-
-if [ "$1" = "purge" ]
-then
-	. /usr/share/debconf/confmodule
-	db_purge
-fi
-
-#DEBHELPER#
-
-exit 0
diff -Nru java-package-0.50/debian/rules java-package-0.50+nmu1/debian/rules
--- java-package-0.50/debian/rules	2012-02-19 13:52:07.0 -0400
+++ java-package-0.50+nmu1/debian/rules	2012-09-06 18:23:37.0 -0400
@@ -28,7 +28,6 @@
 	dh_testroot
 	dh_clean -k
 	dh_installdirs
-	dh_installdebconf
 	install -m 755 make-jpkg.out $(B)/usr/bin/make-jpkg
 	cp lib/*.sh $(B)/usr/share/java-package/
 	find $(B) -type d -name .svn | xargs -r rm -r
diff -Nru java-package-0.50/debian/templates java-package-0.50+nmu1/debian/templates
--- java-package-0.50/debian/templates	2012-02-08 19:52:45.0 -0400
+++ java-package-0.50+nmu1/debian/templates	1969-12-31 20:00:00.0 -0400
@@ -1,13 +0,0 @@
-Template: java-package/postinst-note
-Type: note
-Description: Java-package is now installed - You can invoke make-jpkg to build Java Debian packages
- To use it:
-   1) download one of the java binary archive listed below
-   2) invoke make-jpkg  to build a Debian package from the downloaded archive-
-   3) install the generated package using dpkg
- .
- Supported Java binary distributions currently include:
-   * Oracle :
- - The J2SE Development Kit (JDK), version 6 (update >= 10), 7
- - The J2SE Runtime Environment (JRE), version 6 (update >= 10), 7
- - The J2SE API Javadoc, version 6 (update >= 10), 7


signature.asc
Description: Digital signature

Bug#526878: marked as done (egroupware-core sets open_basedir which disables hook_config_validate.inc.php (egroupware-wiki) sanity check)

[Debian Bug Tracking System]

Your message dated Thu, 6 Sep 2012 23:20:49 +0100
with message-id 

and subject line Closing orphan/obsolete bugs (egroupware and phpgroupware)
has caused the Debian Bug report #526878,
regarding egroupware-core sets open_basedir which disables 
hook_config_validate.inc.php (egroupware-wiki) sanity check
to be marked as done.

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

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


-- 
526878: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=526878
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: egroupware-wiki
Version: 1.4.004-2.dfsg-4.1
Severity: grave
Justification: renders package unusable


Package: egroupware-core (1.4.004-2.dfsg-4.1)
 Version: 1.4.004-2.dfsg-4.1

 therein the file apache.conf
 
http://svn.debian.org/viewsvn/collab-maint/ext-maint/egroupware/trunk/debian/etc/apache.conf?revision=10687&view=markup

 An Installation of the egroupware-suite brings up a problem in the
setup of an upload-dir for the wiki:

 Package: egroupware-wiki (1.4.004-2.dfsg-4.1)
 Version: 1.4.004-2.dfsg-4.1

 therein is the sanity check:

   if ($settings['upload_dir'])
   {
   if (!is_dir($_SERVER['DOCUMENT_ROOT'].$settings['upload_dir']) ||
!file_exists($_SERVER['DOCUMENT_ROOT'].$settings['upload_dir'].'/.'))
   {
   $GLOBALS['config_error'] = 'Directory does not exist, is 
not
readable by the webserver or is not relative to the document root!';
   }
   }


 which always puts an error out, for the $_SERVER['DOCUMENT_ROOT'] is
(always) outside of the open_basedir settings in the apache.conf (ln
-fs ../../egroupware/apache.conf /etc/apache2/conf.d/egroupware).

from the apache.conf:

>>>
php_admin_value open_basedir
/usr/share/egroupware:/var/lib/egroupware:/tmp:/usr/share/php
>>>


workaround: adding the actual SERVER DocumentRoot to the
.../egroupware/apache.conf

>>
php_admin_value open_basedir
/usr/share/egroupware:/var/lib/egroupware:/tmp:/usr/share/php:{$_SERVER['DOCUMENT_ROOT']}
>>

in our case /var/www



best regards,


--- End Message ---
--- Begin Message ---
Hello,

Thanks for your interest in Debian, and sorry that the bugs were not
attended in due time.

egroupware and phpgroupware were removed from Debian unstable a long
time ago [1][2], 2+ years, and they are only present in "oldstable" at
this point, already unsupported and which is going to be replaced soon
when the new stable is released.

[1] http://packages.qa.debian.org/e/egroupware/news/20100317T153845Z.html
[2] http://packages.qa.debian.org/p/phpgroupware/news/20100608T182550Z.html

The bugs are thus now orphan (no maintainer assigned), so they are not
going to be noticed by anybody nor dealt with.  It seems unlikely that
the packages are resurrected soon, and indeed in the time elapsed
probably many of these bug reports are invalid.  I am thus closing
them now.

If you think that they should be kept open for some reason, or that
they should be reassigned to other packages offering similar
functionality, please feel free to reopen these bugs.

Regards.
-- 
Manuel A. Fernandez Montecelo --- End Message ---

Bug#686874: cp2k: segfaults on i386 due to not aligning FFT arrays to 16 bytes for SSE2 and reusing them

[Michael Banck]

Package: cp2k
Version: 2.2.426-1
Severity: serious

Since some months ago, fftw3 is using SSE2 instructions for fast fourier
transforms if the CPU supports it.  One requirement for this is that the
incoming arrays must be aligned to 16 bytes for the SIMD instructions.
This is the case on amd64 by default, but not on i386.

Usually, fftw3 will detect unaligned arrays and not use SSE2.  However,
if the same plan is originally executed with a properly aligned array
and then re-executed  with another, unaligned array, a segfault will
occur, see e.g. 
https://buildd.debian.org/status/fetch.php?pkg=cp2k&arch=i386&ver=2.2.426-5&stamp=1346699763

xxx
/build/buildd-cp2k_2.2.426-5-i386-rUGkvz/cp2k-2.2.426/tools/..//TEST-Linux-i686-gfortran-popt-2012-09-03T19:08:13+/QS/regtest-nmr-1/H2O-NMR-12.inp.out
max_diis:  4

eps_scf:1.00E-05
eps_scf_history:0.00E+00
eps_diis:   1.00E-01
eps_eigval: 1.00E-05

level_shift [a.u.]: 0.00

Mixing method:   DIRECT_P_MIXING

No outer SCF

Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

Backtrace for this error:
#0  0x56A8FF6B
#1  0x56A905AC
#2  0x555733FF
#3  0x55FE3C0B
#4  0x55F2008B
#5  0x55F22E9B
#6  0x55F23402
#7  0x55F22E9B
#8  0x55FC558B
#9  0x9666567 in fftw33d_ at fftw3_lib.F:196
#10  0x966195B in fft_3d_ at fft_lib.f90:135
#11  0x80C77D3 in __fft_tools_MOD_fft3d_s at fft_tools.F:441
#12  0x8340A58 in __pw_methods_MOD_fft_wrap_pw1pw2 at pw_methods.F:1462
#13  0x8EABD6D in __qs_collocate_density_MOD_density_rs2pw at 
qs_collocate_density.F:3433
#14  0x8EC0EF2 in __qs_collocate_density_MOD_calculate_rho_elec at 
qs_collocate_density.F:1392
#15  0x849ADDE in __qs_rho_methods_MOD_qs_rho_update_rho at qs_rho_methods.F:391
#16  0x84A1E30 in __qs_scf_MOD_scf_env_initial_rho_setup at qs_scf.F:2277
#17  0x84A9F28 in __qs_scf_MOD_init_scf_run at qs_scf.F:1810
#18  0x84B53A7 in __qs_scf_MOD_scf at qs_scf.F:368
#19  0x836FA1C in __qs_energy_MOD_qs_energies_scf at qs_energy.F:231
#20  0x80CD15C in __force_env_methods_MOD_force_env_calc_energy_force at 
force_env_methods.F:231
#21  0x8054D39 in __cp2k_runs_MOD_cp2k_run at cp2k_runs.F:403
#22  0x8058C1D in __cp2k_runs_MOD_run_input at cp2k_runs.F:1143
#23  0x804E2C5 in cp2k at cp2k.F:285
xxx

This problem is common enough (1/3 of the test cases segfaulted on the
autobuilder) that it makes cp2k pretty much unusable on i386.


Michael


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

Bug#686872: python-urllib3 should default to verifying certificates

[Jamie Strandboge]

Package: python-urllib3
Version: 1.3-2
Severity: grave
Tags: patch security
Justification: user security hole
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu quantal ubuntu-patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * debian/patches/02_require-cert-verification.patch: verify SSL certificates
by default (LP: #1047054)

urllib3 does not set cert_req or ca_certs by default, so certificates are not
checked and MITM is trivial. Ie, it has in connectionpool.py:
def __init__(self, host, port=None,
 strict=False, timeout=None, maxsize=1,
 block=False, headers=None,
 key_file=None, cert_file=None,
 cert_reqs='CERT_NONE', ca_certs=None):

This should be changed to:
def __init__(self, host, port=None,
 strict=False, timeout=None, maxsize=1,
 block=False, headers=None,
 key_file=None, cert_file=None,
 cert_reqs='CERT_REQUIRED', 
ca_certs='/etc/ssl/certs/ca-certificates.crt')

Attached is a patch to do the above. It has been verified to check
certificates by default, allows for disabling certificate verification,
and the testsuite passes without modification.

Thanks for considering the patch.


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

Kernel: Linux 3.5.0-13-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
diff -Nru python-urllib3-1.3/debian/changelog python-urllib3-1.3/debian/changelog
diff -Nru python-urllib3-1.3/debian/patches/02_require-cert-verification.patch python-urllib3-1.3/debian/patches/02_require-cert-verification.patch
--- python-urllib3-1.3/debian/patches/02_require-cert-verification.patch	1969-12-31 18:00:00.0 -0600
+++ python-urllib3-1.3/debian/patches/02_require-cert-verification.patch	2012-09-06 16:15:25.0 -0500
@@ -0,0 +1,18 @@
+Author: Jamie Strandboge 
+Description: require SSL certificate validation by default by using
+ CERT_REQUIRED and using the system /etc/ssl/certs/ca-certificates.crt
+Bug-Ubuntu: https://launchpad.net/bugs/1047054
+
+Index: python-urllib3-1.3/urllib3/connectionpool.py
+===
+--- python-urllib3-1.3.orig/urllib3/connectionpool.py	2012-09-06 16:03:50.0 -0500
 python-urllib3-1.3/urllib3/connectionpool.py	2012-09-06 16:08:59.0 -0500
+@@ -463,7 +463,7 @@
+  strict=False, timeout=None, maxsize=1,
+  block=False, headers=None,
+  key_file=None, cert_file=None,
+- cert_reqs='CERT_NONE', ca_certs=None):
++ cert_reqs='CERT_REQUIRED', ca_certs='/etc/ssl/certs/ca-certificates.crt'):
+ 
+ super(HTTPSConnectionPool, self).__init__(host, port,
+   strict, timeout, maxsize,
diff -Nru python-urllib3-1.3/debian/patches/series python-urllib3-1.3/debian/patches/series
--- python-urllib3-1.3/debian/patches/series	2012-02-10 16:46:21.0 -0600
+++ python-urllib3-1.3/debian/patches/series	2012-09-06 16:03:57.0 -0500
@@ -1 +1,2 @@
 01_do-not-use-embedded-python-six.patch
+02_require-cert-verification.patch

Bug#686138: QA upload for bzr-stats

[Andrew Starr-Bochicchio]

Koichi Akabe,

I prepared a QA upload of bzr-stats in order to close the RC bug
#686138. I've pushed the changes to:

bzr.debian.org/bzr/pkg-bazaar/bzr-stats/unstable/

It wasn't until after uploading the package to mentors.debian.net for
sponsorship that I noticed that you intend to adopt this package. Is
there any progress on this? Should I go ahead and close this bug, or
are you already preparing an upload?

I notice now that you also intent to adopt bzr-search and bzr-upload.
You should consider joining the pkg-bazaar-maint team.

Thanks,

-- Andrew Starr-Bochicchio

   Ubuntu Developer 
   Debian Maintainer

   PGP/GPG Key ID: D53FDCB1


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

Processed: bug 686833 is forwarded to https://github.com/visionmedia/git-extras/issues/137

[Debian Bug Tracking System]

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

> forwarded 686833 https://github.com/visionmedia/git-extras/issues/137
Bug #686833 [git-extras] git-extras - git-gh-pages - removes all files
Set Bug forwarded-to-address to 
'https://github.com/visionmedia/git-extras/issues/137'.
> thanks
Stopping processing here.

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


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

Bug#685149: missing source for included Windows libraries

[Andreas Tille]

Hi,

ping?
I wonder whether I should upload a fixed package to contrib or main.

Kind regards

 Andreas.

On Fri, Aug 17, 2012 at 02:54:56PM +0200, Andreas Tille wrote:
> Hi Ansgar,
> 
> thanks for checking.  When looking into the packaging I noticed that
> this package can easily be moved from contrib to main because the only
> dependency (Recommends: clustalw) now can be fullfilled in main Debian.
> I would just set
> 
>Recommends: clustalw (>= 2.1+lgpl)
> 
> Would you (with your ftpmaster hat on) and the release team accept this
> move once the new source package has to be builded anyway?
> 
> Kind regards
> 
> Andreas.
> 
> On Fri, Aug 17, 2012 at 01:50:14PM +0200, Ansgar Burchardt wrote:
> > Package: src:gentle
> > Version: 1.9+cvs20100605+dfsg-1
> > Severity: serious
> > 
> > The source package includes libraries for Win32 in binary form only, for
> > example libmySQL.* and sqlite*.dll.  As far as I know the former is also
> > released under the GPL.
> > 
> > Please either include the source or remove the binary-only libraries
> > from the source package.
> 
> -- 
> http://fam-tille.de

-- 
http://fam-tille.de


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

Bug#686867: jruby: CVE-2011-4838

[Moritz Muehlenhoff]

Package: jruby
Severity: grave
Tags: security
Justification: user security hole

Hi,
jruby in Wheezy is still affected by 
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-4838 
   
http://www.nruns.com/_downloads/advisory28122011.pdf



Since Wheezy already has 1.6.5, updating to 1.6.5.1 seems like a good idea?

Cheers,
Moritz


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

Bug#685351: Help: Please seek for sources of some JS files in GNUmed [Was: Bug#685351: src:gnumed-client: Missing source code for *.js files]

[Andreas Tille]

Hi Sebastian,

On Mon, Aug 27, 2012 at 08:20:14PM +0200, Sebastian Hilbert wrote:
> > after reading the bug report twice I noticed that the problem is
> > actually not comparable to the issue discussed currently on
> > debian-devel@l.d.o, because the files are actually used in the
> > package and not replaced.  So if you want to help Debian Med you
> > can do some research and find the sources of the following files
> > inside the gnumed-doc package:
> > 
> >   user-manual/rsrc/System/JSTreeContrib/jquery.jstree.js
> 
> http://www.jstree.com/documentation
> MIT or GPL2
> 
> >   user-manual/rsrc/System/JQueryPlugin/plugins/foswiki/jquery.foswiki.js
> 
> http://foswiki.org/Extensions/JQueryPlugin
> GPL
> 
> >   user-manual/rsrc/System/PatternSkin/pattern.js
> 
> http://trac.foswiki.org/browser/trunk/PatternSkin/lib/Foswiki/Contrib/PatternSkin.pm?rev=14650
> 
> part of PatterSkin
> 
> GPL

I tried to check these links.  I think it needs some clarification:
There is no real doubt that the code is GPL.  The main problem is that
we need to have the source code of the files that were used and which
could be used to reproduce the compressed *.js files.  I did not found
those very files which we could include as copy into the package.
 
> >   user-manual/rsrc/System/JavascriptFiles/foswikiForm.js
> 
> http://www.koders.com/javascript/fid7DAA754986238FA7FE093BDE7031C706AB24FBE2.aspx?s=form#L6
> 
> Apache Version 2
> 
> >   user-manual/rsrc/System/JavascriptFiles/foswikiString.js
> 
> http://trac.foswiki.org/browser/trunk/core/pub/System/JavascriptFiles/foswikiString_src.js
> 
> GPL
> 
> >   user-manual/rsrc/System/JavascriptFiles/foswikiPref.js
> > 
> 
> http://trac.foswiki.org/browser/trunk/core/pub/System/JavascriptFiles/foswikiPref_src.js
> 
> GPL
> 
> All files stem from a default install of Foswiki

It seems these *.js files could be fetched from VCS and these are OK.

In short:  If we do not find the real source files of the part above
we should probably remove them from the gnumed-client tarball and
drop the gnumed-doc package (which would be a shame IMHO).

Kind regards

  Andreas.

-- 
http://fam-tille.de


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

Bug#684885: marked as done (update-guestfs-appliance fails for wheezy because it looks for 'diff' instead of 'diffutils')

[Debian Bug Tracking System]

Your message dated Thu, 06 Sep 2012 19:47:54 +
with message-id 
and subject line Bug#684885: fixed in libguestfs 1:1.18.1-1+deb7u1
has caused the Debian Bug report #684885,
regarding update-guestfs-appliance fails for wheezy because it looks for 'diff' 
instead of 'diffutils'
to be marked as done.

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

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


-- 
684885: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684885
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libguestfs0
Version: 1:1.18.1-1
Severity: serious

Hi,

as the title says, update-guestfs-appliance fails when trying to install
wheezy as it will try to install "diff" while it has been replaced by
"diffutils".

Furthermore, as this initially fails, after modifying
/usr/lib/guestfs/packagelist , the download restart from scratch.
update-guestfs-appliance should use /var/cache/apt/archives if possible.

Cheers,

OdyX

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

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

Versions of packages libguestfs0 depends on:
ii  binutils   2.22-6.1
ii  bsdmainutils   9.0.3
ii  btrfs-tools0.19+20120328-7
ii  cpio   2.11-8
ii  cryptsetup 2:1.4.3-2
ii  debconf [debconf-2.0]  1.5.44
ii  diffutils  1:3.2-6
ii  dosfstools 3.0.13-1
ii  febootstrap3.17-1
ii  file   5.11-2
ii  icoutils   0.29.1-5
ii  iproute20120521-3
ii  jfsutils   1.1.15-2
ii  libaugeas0 0.10.0-1
ii  libc6  2.13-33
ii  libhivex0  1.3.6-2
ii  libmagic1  5.11-2
ii  libpcre3   1:8.30-5
ii  libvirt0   0.9.12-4
ii  libxml22.8.0+dfsg1-5
ii  lsof   4.86+dfsg-1
ii  lvm2   2.02.95-4
ii  module-init-tools  8-2
ii  net-tools  1.60-24.1
ii  netpbm 2:10.0-15+b1
ii  ntfs-3g1:2012.1.15AR.5-2.1
ii  parted 2.3-10
ii  procps 1:3.3.3-2
ii  qemu-kvm   1.1.0+dfsg-3
ii  reiserfsprogs  1:3.6.21-1
ii  scrub  2.4.1-1
ii  strace 4.5.20-2.3
ii  udev   175-3.1
ii  vim-tiny   2:7.3.547-4
ii  xfsprogs   3.1.7+b1
ii  xz-utils   5.1.1alpha+20120614-1
ii  zerofree   1.0.2-1
ii  zfs-fuse   0.7.0-8

libguestfs0 recommends no packages.

libguestfs0 suggests no packages.

-- debconf information:
* libguestfs/update-appliance: true
--- End Message ---
--- Begin Message ---
Source: libguestfs
Source-Version: 1:1.18.1-1+deb7u1

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

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

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

Debian distribution maintenance software
pp.
Hilko Bengen  (supplier of updated libguestfs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 06 Sep 2012 11:44:14 +0200
Source: libguestfs
Binary: guestfish guestfsd libguestfs-dev libguestfs0 guestmount 
libguestfs-tools libguestfs0-dbg python-guestfs libguestfs-perl 
libguestfs-ocaml libguestfs-ocaml-dev erlang-guestfs libguestfs-java 
ruby-guestfs libguestfs-gobject-1.0-0 libguestfs-gobject-dev gir1.2-guestfs-1.0
Architecture: source amd64
Version: 1:1.18.1-1+deb7u1
Distribution: testing
Urgency: low
Maintainer: Hilko Bengen 
Changed-By: Hilko Bengen 
Description: 
 erlang-guestfs - guest disk image management system - Erlang bindings
 gir1.2-guestfs-1.0 - guest disk image management system - GObject 
introspection files
 guestfish  - guest disk image management system - file system shell
 guestfsd   - Daemon to access to guest virtual machine through virtio serial
 guestmount - guest disk image management system - FUSE mount utility
 libguestfs-dev - guest 

Bug#681587: marked as done (python-guestfs: missing dependency on python)

[Debian Bug Tracking System]

Your message dated Thu, 06 Sep 2012 19:47:54 +
with message-id 
and subject line Bug#681587: fixed in libguestfs 1:1.18.1-1+deb7u1
has caused the Debian Bug report #681587,
regarding python-guestfs: missing dependency on python
to be marked as done.

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

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


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

Package: python-guestfs
Version: 1:1.18.5-1
Severity: serious
Justification: Policy 3.5

python-guestfs doesn't depend on python. Perhaps is has something to do 
with this part of the build log:


dpkg-gencontrol: warning: Depends field of package python-guestfs: unknown 
substitution variable ${python:Depends}


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

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

--
Jakub Wilk


--- End Message ---
--- Begin Message ---
Source: libguestfs
Source-Version: 1:1.18.1-1+deb7u1

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

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

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

Debian distribution maintenance software
pp.
Hilko Bengen  (supplier of updated libguestfs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 06 Sep 2012 11:44:14 +0200
Source: libguestfs
Binary: guestfish guestfsd libguestfs-dev libguestfs0 guestmount 
libguestfs-tools libguestfs0-dbg python-guestfs libguestfs-perl 
libguestfs-ocaml libguestfs-ocaml-dev erlang-guestfs libguestfs-java 
ruby-guestfs libguestfs-gobject-1.0-0 libguestfs-gobject-dev gir1.2-guestfs-1.0
Architecture: source amd64
Version: 1:1.18.1-1+deb7u1
Distribution: testing
Urgency: low
Maintainer: Hilko Bengen 
Changed-By: Hilko Bengen 
Description: 
 erlang-guestfs - guest disk image management system - Erlang bindings
 gir1.2-guestfs-1.0 - guest disk image management system - GObject 
introspection files
 guestfish  - guest disk image management system - file system shell
 guestfsd   - Daemon to access to guest virtual machine through virtio serial
 guestmount - guest disk image management system - FUSE mount utility
 libguestfs-dev - guest disk image management system - development headers
 libguestfs-gobject-1.0-0 - guest disk image management system - GObject 
bindings
 libguestfs-gobject-dev - guest disk image management system - GObject 
development headers
 libguestfs-java - guest disk image management system - Java bindings
 libguestfs-ocaml - guest disk image management system - OCaml bindings
 libguestfs-ocaml-dev - guest disk image management system - OCaml development 
files
 libguestfs-perl - guest disk image management system - Perl bindings
 libguestfs-tools - guest disk image management system - tools
 libguestfs0 - guest disk image management system - shared library
 libguestfs0-dbg - guest disk image management system - debug symbols
 python-guestfs - guest disk image management system - Python bindings
 ruby-guestfs - guest disk image management system - Ruby bindings
Closes: 681587 684885
Changes: 
 libguestfs (1:1.18.1-1+deb7u1) testing; urgency=low
 .
   * [3ad62ed] Removed useless dh_python* overrides (Closes: #681587)
   * [c43317d] Removed useless, unused patches that were included in the
 package by accident. Added patch that replaces diff with diffutils in
 package list (Closes: #684885)
Checksums-Sha1: 
 f55b0e35f1f67a6f9c74e078e5dd8a47a848b5f5 3042 libguestfs_1.18.1-1+deb7u1.dsc
 3977c64556d52dd429c43b32b260445ba3abe3e4 54336 
libguestfs_1.18.1-1+deb7u1.debian.tar.gz
 b17d65f8d8c2980b316347c2589508c07efc9756 461160 
guestfish_1.18.1-1+deb7u1_amd64.deb
 021a36ba8f4a8f6af7ea8d7ae7da8415c1cb0c5f 355896 
guestfsd_1.18.1-1+deb7u1_amd64.deb
 bdec7406a008bf861f1c5cee569afe5ca727e562 628278 
libguestfs-dev_1.18.1-1+deb7u1_amd64.deb
 c1e86ed2b6d46fbb2277d62ab430703ee3c6a494 1107000 
libguestfs0_1.18.1-1+deb7u1_amd64.deb
 f7e4b6c711e688ad97065d4b16d

Processed: Re: Bug#686818: When given an "" as security mirror, it use the default security mirror

[Debian Bug Tracking System]

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

> severity 686818 wishlist
Bug #686818 [simple-cdd] When given an "" as security mirror, it use the 
default security mirror
Severity set to 'wishlist' from 'serious'
> tags 686818 wontfix
Bug #686818 [simple-cdd] When given an "" as security mirror, it use the 
default security mirror
Added tag(s) wontfix.
> thanks
Stopping processing here.

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


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

Bug#682351: git-annex: build fails because of failing tests

[gregor herrmann]

On Thu, 06 Sep 2012 15:08:07 -0400, Joey Hess wrote:

> gregor herrmann wrote:
> > Solution: set GIT_AUTHOR_NAME _and_ GIT_COMMITTER_NAME in test.hs
> > (additionally to EMAIL; or GIT_AUTHOR_EMAIL and GIT_COMMITTER_EMAIL
> > instead of EMAIL).
> I've applied that patch, thanks.

Thank you.
 
> I don't know that this is actually RC, is building on pbuilder some kind
> of release requirement? 

I'm not sure about the severity either; and p/cowbuilder itself
probably doesn't make it RC. On the other hand the same could
probably happen in other environments where the user the build is
running under has incomplete data in /etc/passwd.

> Any upload to fix this in wheezy would need to
> go through t-p-u.

Maybe ask the release team for advice?


Cheers,
gregor 
 
-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer  -  http://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Paul McCartney & Wings: So Bad


signature.asc
Description: Digital signature

Bug#682351: git-annex: build fails because of failing tests

[Joey Hess]

gregor herrmann wrote:
> Solution: set GIT_AUTHOR_NAME _and_ GIT_COMMITTER_NAME in test.hs
> (additionally to EMAIL; or GIT_AUTHOR_EMAIL and GIT_COMMITTER_EMAIL
> instead of EMAIL).

I've applied that patch, thanks.

I don't know that this is actually RC, is building on pbuilder some kind
of release requirement? Any upload to fix this in wheezy would need to
go through t-p-u.

-- 
see shy jo


signature.asc
Description: Digital signature

Bug#686861: debian-installer: kfreebsd requires larger MFS_ROOT

[Steven Chamberlain]

Package: src:debian-installer
Version: 20120712
Severity: grave
Tags: wheezy sid
User: debian-...@lists.debian.org
Usertags: kfreebsd
X-Debbugs-Cc: debian-...@lists.debian.org

Hi,

Graphical install of kfreebsd-amd64 fails when processing
netcfg.templates and/or writing to /var/lib/debconf/templates.dat, with
error "Failed to load installer component: netcfg".

The ramdisk has insufficient space for something, the main-menu process
then crashes, and also core dumps (absolutely exhausting all remaining
space) and gets stuck in a loop trying to restart itself.

On 17/08/12 11:43, Robert Millan wrote:
> 2012/8/10 Steven Chamberlain :
>> In the second screenshot it says "/: write failed, filesystem is full"
>> [...]
> 
> Probably a bigger mfsroot (see MFSROOT_LIMIT in 
> debian-installer/build/Makefile)

The current limit for kfreebsd-amd64 is 64m;  I'm not sure yet how large
this will need to be, but probably no more than 128m.

I imagine the limit also needs increasing for kfreebsd-i386 (untested
yet).  I guess this problem has been triggered by new debconf
translations being added.

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


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

Bug#686848: [Pkg-xen-devel] Bug#686848: CVE-2007-0998: Qemu monitor can be used to access host resources

[Bastian Blank]

On Fri, Sep 07, 2012 at 01:30:21AM +0800, Thomas Goirand wrote:
> NOTE REGARDING CVE
> ==
> 
> This issue was previously reported in a different context, not to Xen
> upstream, and assigned CVE-2007-0998 and fixed in a different way.  We
> have requested a new CVE for XSA-19 but it is not yet available.

CVE-2007-0998 is _not_ the correct identifier.

Bastian

-- 
The face of war has never changed.  Surely it is more logical to heal
than to kill.
-- Surak of Vulcan, "The Savage Curtain", stardate 5906.5


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

Bug#686495: libpcre3: Very large value for re_nsub

[Mark Baker]

The patch has now been accepted by upstream and will be in the next release.

http://bugs.exim.org/show_bug.cgi?id=1287

I'm happy to include it in the debian package before that, and will do when I 
get time in the next week.


On 2 Sep 2012, at 12:35, Patrick Häcker wrote:

> Package: libpcre3
> Version: 1:8.30-5
> Severity: grave
> Tags: patch
> Justification: causes non-serious data loss
> 
> Dear Maintainer,
> 
> when compiling the regular expression
> 
> regex_t rx;
> regcomp(&rx, "^(\\(\\))? *(.*)$", 0)
> 
> I get the large value 140733193388034 for rx.re_nsub. As this value is often
> used afterwards in malloc this normally leads to the termination of the
> programm (either because of the segfault or due to the assumption of no free
> memory), so unsaved data gets lost.
> 
> The problem is well known
> (http://www.exim.org/lurker/message/20120822.143744.147fd5d2.de.html)
> and a patch exists (http://bugs.exim.org/attachment.cgi?id=586). I can
> confirm that the patch works.
> 
> Please consider applying the patch.
> 
> Cheers
> Patrick
> 
> -- System Information:
> Debian Release: wheezy/sid
>  APT prefers testing
>  APT policy: (900, 'testing'), (500, 'testing-proposed-updates'), (500, 
> 'stable-updates'), (400, 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 3.2.0-3-amd64 (SMP w/6 CPU cores)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> 
> Versions of packages libpcre3 depends on:
> ii  libc6  2.13-35
> ii  multiarch-support  2.13-35
> 
> libpcre3 recommends no packages.
> 
> libpcre3 suggests no packages.
> 
> -- no debconf information


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

Processed: Re: Bug#682351: git-annex: build fails because of failing tests

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + confirmed patch
Bug #682351 [git-annex] git-annex: build fails because of failing tests
Bug #682350 [git-annex] git-annex: build fails because of failing tests
Added tag(s) confirmed and patch.
Added tag(s) confirmed and patch.

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


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

Bug#682351: git-annex: build fails because of failing tests

[gregor herrmann]

Control: tag -1 + confirmed patch

On Sat, 21 Jul 2012 23:47:36 +0200, Motiejus Jakštys wrote:

> Package: git-annex
> Version: 3.20120614~bpo60+1
> Severity: serious
> Justification: fails to build from source
> 
> 
> Building git-annex in pbuilder on squeeze having backports.debian.org
> repository enabled yields this error:

FWIW: I tried with the current version from backports
(3.20120629~bpo60+1) in a cowbuilder squeeze+backports chroot, and
the tests also fail for me.

If I then run "debian/rules build" or "make test" in the chroot
manually, the tests pass.

I can only guess that the difference is that p/cowbuilder use the
fancy user/id pbuilder/1234 for building?!


The version in unstable (3.20120825) in a sid cowbuilder chroot fails
too, with slightly different errors but also between blackbox init and blackbox 
add:

#v+
Testing 1:blackbox:0:git-annex init   
Testing 1:blackbox:1:git-annex add:0  
Testing 1:blackbox:1:git-annex add:1  
Cases: 54  Tried: 16  Errors: 0  Failures: 0
*** Please tell me who you are.

Run

  git config --global user.email "y...@example.com"
  git config --global user.name "Your Name"

to set your account's default identity.
Omit --global to set the identity only in this repository.

fatal: empty ident  > not allowed
### Failure in: 1:blackbox:1:git-annex add:1
git annex init failed
Testing 1:blackbox:1:git-annex add:2  
Cases: 54  Tried: 17  Errors: 0  Failures: 1
#v-
[and so on ...]


The version in testing (3.20120629) in a wheezy cowbuilder chroot
fails like 3.20120825.


Long debugging session told short: p/cowbuilder don't set a name for
their builduser, which makes git explode (the "fatal: empty ident"
errors).


Solution: set GIT_AUTHOR_NAME _and_ GIT_COMMITTER_NAME in test.hs
(additionally to EMAIL; or GIT_AUTHOR_EMAIL and GIT_COMMITTER_EMAIL
instead of EMAIL).

Or run dh_auto_test with GIT_AUTHOR_NAME and GIT_COMMITTER_NAME set
in d/rules.


Both solutions tested with the version in sid.
(And attached.)


Cheers,
gregor

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer  -  http://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Ludwig Hirsch: Der Turm
diff -Nru git-annex-3.20120825/debian/rules git-annex-3.20120825.fixored/debian/rules
--- git-annex-3.20120825/debian/rules	2012-07-17 19:54:56.0 +0200
+++ git-annex-3.20120825.fixored/debian/rules	2012-09-06 19:41:46.070734988 +0200
@@ -2,6 +2,11 @@
 %:
 	dh $@
 
+override_dh_auto_test:
+	GIT_AUTHOR_NAME="git-annex test" \
+	GIT_COMMITTER_NAME="git-annex test" \
+	dh_auto_test
+
 # Not intended for use by anyone except the author.
 announcedir:
 	@echo ${HOME}/src/git-annex/doc/news
diff -Nru git-annex-3.20120825/test.hs git-annex-3.20120825.fixored/test.hs
--- git-annex-3.20120825/test.hs	2012-08-25 15:59:46.0 +0200
+++ git-annex-3.20120825.fixored/test.hs	2012-09-06 19:45:20.822727310 +0200
@@ -881,8 +881,11 @@
 	setEnv "PATH" (cwd ++ ":" ++ p) True
 	setEnv "TOPDIR" cwd True
 	-- Avoid git complaining if it cannot determine the user's email
-	-- address.
-	setEnv "EMAIL" "git-annex test " True
+	-- address, or exploding if it doesn't know the user's name.
+	setEnv "GIT_AUTHOR_EMAIL" "t...@example.com" True
+	setEnv "GIT_AUTHOR_NAME" "git-annex test" True
+	setEnv "GIT_COMMITTER_EMAIL" "t...@example.com" True
+	setEnv "GIT_COMMITTER_NAME" "git-annex test" True
 
 changeToTmpDir :: FilePath -> IO ()
 changeToTmpDir t = do


signature.asc
Description: Digital signature

Bug#686836: marked as done (telepathy-mission-control-5: can't delete old passwords from gnome-keyring)

[Debian Bug Tracking System]

Your message dated Thu, 06 Sep 2012 17:32:45 +
with message-id 
and subject line Bug#686836: fixed in telepathy-mission-control-5 1:5.12.1-3
has caused the Debian Bug report #686836,
regarding telepathy-mission-control-5: can't delete old passwords from 
gnome-keyring
to be marked as done.

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

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


-- 
686836: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686836
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: telepathy-mission-control-5
Version: 1:5.12.1-2
Severity: serious
Justification: maintainer's opinion: poor user experience during upgrade
Tags: patch upstream
Forwarded: https://bugs.freedesktop.org/show_bug.cgi?id=42088

Telepathy upstream has moved from storing passwords in Mission Control
(which stores them in gnome-keyring if available, or in plain-text)
to querying for them interactively at connection (which, in practice, means
they come from gnome-keyring for Empathy users, or KWallet for kde-telepathy
users).

While upgrading from the version of Empathy in squeeze to the version in
wheezy, Empathy is meant to migrate passwords from Mission Control's storage
to its own separate storage in gnome-keyring. It does this in the obvious
way, described by this pseudocode:

   foreach account:
   if the account's connection manager can get passwords interactively:
   try:
   get the password from Mission Control
   copy it to a different item in gnome-keyring, which Empathy uses
   delete the item that Mission Control would have used
   except:
   log a warning and move on

Unfortunately, Mission Control has a long-standing bug that means it cannot
delete passwords from gnome-keyring, which I've recently fixed upstream.
This means you end up with two copies of the password: one that MC will
use, and one that Empathy would use if given the chance (but because MC
thinks it knows the password, it will never ask Empathy).

This is particularly annoying if you change your password. Changing the
password in Empathy will change Empathy's gnome-keyring item, which
has no effect on the leftover MC gnome-keyring item, which is the one
that is actually used!

I believe my upstream patches from fd.o #42088 should fix this. I have a
virtual machine image in which I'm going to test it, copied after
installing squeeze, adding a couple of IM test accounts and upgrading to
wheezy in a text console, but before logging in to the wheezy GUI for the
first time and triggering the automatic migration.

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

Kernel: Linux 3.2.0-3-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

Versions of packages telepathy-mission-control-5 depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.12.1-2
ii  libc62.13-35
ii  libdbus-1-3  1.6.4-1
ii  libdbus-glib-1-2 0.100-1
ii  libglib2.0-0 2.32.3-1
ii  libgnome-keyring03.4.1-1
ii  libmission-control-plugins0  1:5.12.1-2
ii  libnm-glib4  0.9.4.0-5
ii  libtelepathy-glib0   0.19.3-1
ii  libupower-glib1  0.9.17-1

telepathy-mission-control-5 recommends no packages.

Versions of packages telepathy-mission-control-5 suggests:
ii  telepathy-haze  0.6.0-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: telepathy-mission-control-5
Source-Version: 1:5.12.1-3

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

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

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated 
telepathy-mission-control-5 package)

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

Bug#686835: marked as done (telepathy-mission-control-5: squeeze -> wheezy upgrade makes MSN accounts disappear)

[Debian Bug Tracking System]

Your message dated Thu, 06 Sep 2012 17:32:45 +
with message-id 
and subject line Bug#686835: fixed in telepathy-mission-control-5 1:5.12.1-3
has caused the Debian Bug report #686835,
regarding telepathy-mission-control-5: squeeze -> wheezy upgrade makes MSN 
accounts disappear
to be marked as done.

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

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


-- 
686835: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686835
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: telepathy-mission-control-5
Version: 1:5.12.1-2
Severity: grave
Tags: upstream
Justification: causes non-serious data loss

Mission Control 5.12 automatically migrates MSN accounts from
telepathy-butterfly to telepathy-haze. However, the migration process doesn't
actually work if telepathy-butterfly is not installed. Instead, the
butterfly account gets disabled and marked as invalid. Empathy doesn't
display accounts that are marked as invalid (which I think is a bug -
it should present account editing UI for them so they can be resurrected -
but that's unlikely to happen before wheezy).

Because telepathy-butterfly depends on papyon which depends on Farsight
which conflicts with Farstream, is removed during the upgrade from squeeze
to wheezy. The practical result is that all MSN accounts from squeeze
disappear. It is possible to get them back, but only if you're a Telepathy
expert.

I hope to be able to fix this upstream.

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

Kernel: Linux 3.2.0-3-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

Versions of packages telepathy-mission-control-5 depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.12.1-2
ii  libc62.13-35
ii  libdbus-1-3  1.6.4-1
ii  libdbus-glib-1-2 0.100-1
ii  libglib2.0-0 2.32.3-1
ii  libgnome-keyring03.4.1-1
ii  libmission-control-plugins0  1:5.12.1-2
ii  libnm-glib4  0.9.4.0-5
ii  libtelepathy-glib0   0.19.3-1
ii  libupower-glib1  0.9.17-1

telepathy-mission-control-5 recommends no packages.

Versions of packages telepathy-mission-control-5 suggests:
ii  telepathy-haze  0.6.0-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: telepathy-mission-control-5
Source-Version: 1:5.12.1-3

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

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

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated 
telepathy-mission-control-5 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 06 Sep 2012 17:06:32 +0100
Source: telepathy-mission-control-5
Binary: telepathy-mission-control-5 telepathy-mission-control-5-dbg 
libmission-control-plugins0 libmission-control-plugins-dev 
libmission-control-plugins-doc
Architecture: source amd64 all
Version: 1:5.12.1-3
Distribution: unstable
Urgency: low
Maintainer: Debian Telepathy maintainers 

Changed-By: Simon McVittie 
Description: 
 libmission-control-plugins-dev - management daemon for Telepathy (headers for 
plugins)
 libmission-control-plugins-doc - management daemon for Telepathy 
(documentation for plugins)
 libmission-control-plugins0 - management daemon for Telepathy (library for 
plugins)
 telepathy-mission-control-5 - management daemon for Telepathy real-time 
communication framework
 telepathy-mission-control-5-dbg - management daemon for Telepathy (debug 
symbols)
Closes: 686835 686836
Changes: 
 telepathy-mission-control-5 (1:5.12.1-3) unstable; urgency=low
 .
   * Add patches from upstream stable release 5.12.2 to fix deletion of
 passwords from gnome-keyring,

Bug#686848: CVE-2007-0998: Qemu monitor can be used to access host resources

[Thomas Goirand]

Package: xen-qemu-dm-4.0
Version: 4.0.1-2+squeeze1
Severity: grave
Tags: squeeze

Copying the Xen Security Advisory:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 Xen Security Advisory XSA-19

 guest administrator can access qemu monitor console


ISSUE DESCRIPTION
=

A guest administrator who is granted access to the graphical console
of a Xen guest can access the qemu monitor.  The monitor can be used
to access host resources.

IMPACT
==

A malicious guest administrator can access host resources (perhaps
belonging to other guests or the underlying system) and may be able to
escalate their privilege to that of the host.

VULNERABLE SYSTEMS
==

Installations where guest administrators do not have access to a
domain's graphical console, or containing only PV domains configured
without a graphical console, are not vulnerable.

Installations where all guest administrators are trustworthy are not
vulnerable, even if the guest operating systems themselves are
untrusted.

Systems using xend/xm: At least all versions since Xen 4.0 are
affected.  Systems are vulnerable even if "monitor=no" is specified in
the xm domain configuration file - this configuration option is not
properly honoured in the vulnerable versions.

Systems using libxl/xl: All versions are affected.  The "monitor="
option is not understood, and is therefore ignored, by xl.  However,
systems using the experimental device model version based on upstream
qemu are NOT vulnerable; that is, Xen 4.2 RC systems with
device_model_version="qemu_xen" specified in the xl domain config
file.

Systems using libvirt are vulnerable.  For "xen:" URIs, see xend/xm,
above.  For "libxl:" URIs, all versions are affected.

Systems based on the Xen Cloud Platform are NOT vulnerable.

CONFIRMING VULNERABILITY


Connect to the guest's VNC (or SDL) graphical display and make sure
your focus is in that window.  Hold down CTRL and ALT and press 2.
You will see a black screen showing one of "serial0", "parallel0" or
"QEMU  monitor".  Repeat this exercise for other digits 3 to
6.  CTRL+ALT+1 is the domain's normal graphical console.  Not all
numbers will have screens attached, but note that you must release and
re-press CTRL and ALT each time.

If one of the accessible screens shows "QEMU  monitor" then
you are vulnerable.  Otherwise you are not.

MITIGATION
==

With xl in Xen 4.1 and later, supplying the following config
option in the VM configuration file will disable the monitor:
   device_model_args=["-monitor","null"]

With xend the following config option will disable the monitor:
   monitor_path="null"
Note that with a vulnerable version of the software specifying
"monitor=0" will NOT disable the monitor.

We are not currently aware of the availability of mitigation for
systems using libvirt.

NOTE REGARDING EMBARGO
==

This issue was publicly discussed online by its discoverer.
There is therefore no embargo.

NOTE REGARDING CVE
==

This issue was previously reported in a different context, not to Xen
upstream, and assigned CVE-2007-0998 and fixed in a different way.  We
have requested a new CVE for XSA-19 but it is not yet available.

RESOLUTION
==

The attached patch against qemu-xen-traditional
(qemu-xen-4.*-testing.git) resolves this issue.

$ sha256sum xsa19-qemu-all.patch
19fc5ff9334e7e7ad429388850dc6e52e7062c21a677082e7a89c2f2c91365fa  
xsa19-qemu-all.patch
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAEBAgAGBQJQSMr3AAoJEIP+FMlX6CvZ2O8H/2cZuOEMQd6ELDSmgj2fVaYl
qpev3Ux50+wHsBf2JS4XMW+f6wwNWa8IBP1GL+SUvOLVr0PGYb8cbISy+zp6z+ku
mAF1T19iaAMNc/feSYwgtLfYE9H25SbB4cuPg6YkyLf6dQn0KnEyf9GIJxHy0xir
nU5XKEwhhJHw17cXZyagTBheXqrIRtIhgMNv3oQKg60NDc+2sMYwMmv7lgPVIvTZ
5+rkY7RX34hBCw08qt/CEyI9OXKHL1jDjPM8QtCKuwDzaWI10yQxtLjWJCYEhGkH
QqMHU6D8Q3DptCSZj/9urs7+oWGwb3TKR7rUc5v7NbiHlliEX5njDKrhxZpxvJg=
=21pO
-END PGP SIGNATURE-


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

Bug#686152: xorg server 1.12.3: xf86UnloadSubModule() hangs, patch proposal

[Julien Cristau]

On Thu, Sep  6, 2012 at 18:31:52 +0200, Stephan Schreiber wrote:

> 
> A patch proposal.
> 
Please check if this is still an issue in xorg-server 1.13.  For 1.12 I
think I'll just revert the commit that made UnloadSubModule do
something.

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#686846: sympa: upgrade script continues to provide fodder for kafka novel

[Clint Adams]

Package: sympa
Version: 6.1.11~dfsg-4
Severity: grave

When upgrading from squeeze with SQLite3, after fudging the exclusion_table
by hand, this happens:

err Upgrade::probe_db() Table 'list_table' not found in database 
'/var/lib/dbconfig-common/sqlite3/sympa/sympa' ; you should create it with 
create_db.SQLite script

There is no list_table in any of the create_db scripts.


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

Processed: your mail

[Debian Bug Tracking System]

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

> tags 686152 + patch
Bug #686152 [src:xorg-server] xorg server 1.12.3: xf86UnloadSubModule() hangs
Added tag(s) patch.
>
End of message, stopping processing here.

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


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

Bug#686845: upgrade fails when using sympa with sqlite3

[Clint Adams]

Package: sympa
Version: 6.1.11~dfsg-4
Severity: grave

When upgrading from squeeze, the postinst fails because exclusion_table
does not exist.

err Upgrade::probe_db() Table 'exclusion_table' not found in database 
'/var/lib/dbconfig-common/sqlite3/sympa/sympa' ; you should create it with 
create_db.SQLite script

After creating that table with create_db.SQLite, it STILL fails, due to

info Upgrade::probe_db() Field 'robot_exclusion' (table 'exclusion_table' ; 
database '/var/lib/dbconfig-common/sqlite3/sympa/sympa') was NOT found. 
Attempting to add it...
DBD::SQLite::db do failed: Cannot add a NOT NULL column with default value NULL 
at /usr/share/sympa/lib/Upgrade.pm line 1271.
err Upgrade::probe_db() Could not add field 'robot_exclusion' to 
table'exclusion_table'.

This renders sympa unusable after upgrading to wheezy.


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

Bug#686152: xorg server 1.12.3: xf86UnloadSubModule() hangs, patch proposal

[Stephan Schreiber]

A patch proposal.

The unpatched code is (hw/xfree86/loader/loadmod.c):

static void
UnloadModuleOrDriver(ModuleDescPtr mod)
{
if (mod == (ModuleDescPtr) 1)
return;

if (mod == NULL || mod->name == NULL)
return;

if (mod->parent)
xf86MsgVerb(X_INFO, 3, "UnloadSubModule: \"%s\"\n", mod->name);
else
xf86MsgVerb(X_INFO, 3, "UnloadModule: \"%s\"\n", mod->name);

if (mod->TearDownData != ModuleDuplicated) {
if ((mod->TearDownProc) && (mod->TearDownData))
mod->TearDownProc(mod->TearDownData);
LoaderUnload(mod->name, mod->handle);
}

if (mod->child)
UnloadModuleOrDriver(mod->child);
if (mod->sib)
UnloadModuleOrDriver(mod->sib);
free(mod->path);
free(mod->name);
free(mod);
}

void
UnloadSubModule(pointer _mod)
{
ModuleDescPtr mod = (ModuleDescPtr) _mod;

/* Some drivers are calling us on built-in submodules, ignore them */
if (mod == (ModuleDescPtr) 1)
return;
RemoveChild(mod);
UnloadModuleOrDriver(mod);
}

static void
RemoveChild(ModuleDescPtr child)
{
ModuleDescPtr mdp;
ModuleDescPtr prevsib;
ModuleDescPtr parent;

if (!child->parent)
return;

parent = child->parent;
if (parent->child == child) {
parent->child = child->sib;
return;
}

prevsib = parent->child;
mdp = prevsib->sib;
while (mdp && mdp != child) {
prevsib = mdp;
mdp = mdp->sib;
}
if (mdp == child)
prevsib->sib = child->sib;
child->sib = NULL;
return;
}


The UnloadSubModule() function is called by xf86UnloadSubModule() as  
you can see in my first report.
UnloadSubModule() first calls RemoveChild(), finally  
UnloadModuleOrDriver() for the submodule pointer to unload it.


As you can see, each ModuleDescPtr instance maintains its childs:
ptr->child is the first child,
ptr->child->sib is the second child,
prt->child->sib->sib is the third child
as long as ->child or ->sib isn't NULL.

The idea seems to be that UnloadSubModule() deals with modules that  
didn't unload their childs - in the TearDownProc that  
UnloadModuleOrDriver() calls.
Thus, UnloadModuleOrDriver() has the code lines which unload all  
childs and grand childs etc. recursively:

if (mod->child)
UnloadModuleOrDriver(mod->child);
if (mod->sib)
UnloadModuleOrDriver(mod->sib);

Note that the call of UnloadModuleOrDriver(mod->sib) is needed for  
that recursive unload.


The top-level instance of UnloadModuleOrDriver() gets the module  
pointer which UnloadSubModule() had.
The UnloadModuleOrDriver() function must not unload mod->sib for that  
top-level module pointer because it is a sibling of the module but not  
a child.
The call of UnloadModuleOrDriver(mod->sib) can't be removed because it  
would break the mentioned recursive unload.


Thus, RemoveChild() sets ->sib to NULL for the module pointer that it gets.

When UnloadSubModule() calls RemoveChild(), then  
UnloadModuleOrDriver() for the submodule to unload, everything works  
fine, because UnloadModuleOrDriver() detects the NULL ->sib pointer  
and won't call UnloadModuleOrDriver() in recursive manner for it.



The real bug is in RemoveChild() - it doesn't set ->sib to NULL if the  
module is the first child of its parent. This causes wrong and  
multiple unload attempts for particular submodules what hangs up the  
xorg server.



The patch corrects the RemoveChild() function:

static void
RemoveChild(ModuleDescPtr child)
{
ModuleDescPtr mdp;
ModuleDescPtr prevsib;
ModuleDescPtr parent;

if (!child->parent)
return;

parent = child->parent;
if (parent->child == child) {
parent->child = child->sib;
}
else {
prevsib = parent->child;
mdp = prevsib->sib;
while (mdp && mdp != child) {
prevsib = mdp;
mdp = mdp->sib;
}
if (mdp == child)
prevsib->sib = child->sib;
}
child->sib = NULL;
}




I built the xorg-xserver package with the patch (and the ones of  
bug#685750 and 686153).


It works; the resulting Xorg.0.log is:

[31.839]
X.Org X Server 1.12.3
Release Date: 2012-07-09
[31.839] X Protocol Version 11, Revision 0
[31.839] Build Operating System: Linux 3.2.0-3-mckinley ia64 Debian
[31.839] Current Operating System: Linux itanic 3.2.0-3-mckinley  
#1 SMP Sat Aug 18 20:50:43 UTC 2012 ia64
[31.839] Kernel command line: BOOT_IMAGE=scsi0:/EFI/debian/vmlinuz  
root=/dev/sdb5  ro

[31.839] Build Date: 05 September 2012  06:41:52PM
[31.839] xorg-server 2:1.12.3-1 (Julien Cristau )
[31.839] Current version of pixman: 0.26.0
[31.839]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[31.840] Markers: (--) probed, (**) from config file, (==) default  
setting,

(++) from command line, (!!) notice, (II) informational,
(WW) warning

Bug#685542: d-push: diff for NMU version 2.0-1.1

[gregor herrmann]

tags 685542 + patch
tags 685542 + pending
thanks

Dear maintainer,

I've prepared an NMU for d-push (versioned as 2.0-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer  -  http://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Pogues: If I Should Fall From The Grac
diff -u d-push-2.0/debian/changelog d-push-2.0/debian/changelog
--- d-push-2.0/debian/changelog
+++ d-push-2.0/debian/changelog
@@ -1,3 +1,14 @@
+d-push (2.0-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Fix "Error when using https://myserver/Microsoft-Server-ActiveSync":
+add missing trailing slash to STATE_DIR in
+0005-set-proper-default-config.patch.
+Thanks to nb for the bug report and the pointer to the solution.
+(Closes: #685542)
+
+ -- gregor herrmann   Thu, 06 Sep 2012 17:38:49 +0200
+
 d-push (2.0-1) unstable; urgency=low
 
   * [817397a] Imported Upstream version 2.0
diff -u d-push-2.0/debian/patches/0005-set-proper-default-config.patch d-push-2.0/debian/patches/0005-set-proper-default-config.patch
--- d-push-2.0/debian/patches/0005-set-proper-default-config.patch
+++ d-push-2.0/debian/patches/0005-set-proper-default-config.patch
@@ -2,6 +2,9 @@
 Date: Sun, 17 Apr 2011 16:05:40 +0200
 Subject: set proper default config
 
+Reviewed-by: gregor herrmann 
+Last-Update: 2012-09-06
+
 ---
  config.php |   17 +++--
  1 file changed, 11 insertions(+), 6 deletions(-)
@@ -15,7 +18,7 @@
   *  Default FileStateMachine settings
   */
 -define('STATE_DIR', '/var/lib/z-push/');
-+define('STATE_DIR', '/var/lib/d-push/state');
++define('STATE_DIR', '/var/lib/d-push/state/');
  
  
  /**


signature.asc
Description: Digital signature

Processed: d-push: diff for NMU version 2.0-1.1

[Debian Bug Tracking System]

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

> tags 685542 + patch
Bug #685542 [d-push] d-push: Error when using 
https://myserver/Microsoft-Server-ActiveSync
Added tag(s) patch.
> tags 685542 + pending
Bug #685542 [d-push] d-push: Error when using 
https://myserver/Microsoft-Server-ActiveSync
Added tag(s) pending.
> thanks
Stopping processing here.

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


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

Bug#686836: telepathy-mission-control-5: can't delete old passwords from gnome-keyring

[Simon McVittie]

Package: telepathy-mission-control-5
Version: 1:5.12.1-2
Severity: serious
Justification: maintainer's opinion: poor user experience during upgrade
Tags: patch upstream
Forwarded: https://bugs.freedesktop.org/show_bug.cgi?id=42088

Telepathy upstream has moved from storing passwords in Mission Control
(which stores them in gnome-keyring if available, or in plain-text)
to querying for them interactively at connection (which, in practice, means
they come from gnome-keyring for Empathy users, or KWallet for kde-telepathy
users).

While upgrading from the version of Empathy in squeeze to the version in
wheezy, Empathy is meant to migrate passwords from Mission Control's storage
to its own separate storage in gnome-keyring. It does this in the obvious
way, described by this pseudocode:

   foreach account:
   if the account's connection manager can get passwords interactively:
   try:
   get the password from Mission Control
   copy it to a different item in gnome-keyring, which Empathy uses
   delete the item that Mission Control would have used
   except:
   log a warning and move on

Unfortunately, Mission Control has a long-standing bug that means it cannot
delete passwords from gnome-keyring, which I've recently fixed upstream.
This means you end up with two copies of the password: one that MC will
use, and one that Empathy would use if given the chance (but because MC
thinks it knows the password, it will never ask Empathy).

This is particularly annoying if you change your password. Changing the
password in Empathy will change Empathy's gnome-keyring item, which
has no effect on the leftover MC gnome-keyring item, which is the one
that is actually used!

I believe my upstream patches from fd.o #42088 should fix this. I have a
virtual machine image in which I'm going to test it, copied after
installing squeeze, adding a couple of IM test accounts and upgrading to
wheezy in a text console, but before logging in to the wheezy GUI for the
first time and triggering the automatic migration.

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

Kernel: Linux 3.2.0-3-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

Versions of packages telepathy-mission-control-5 depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.12.1-2
ii  libc62.13-35
ii  libdbus-1-3  1.6.4-1
ii  libdbus-glib-1-2 0.100-1
ii  libglib2.0-0 2.32.3-1
ii  libgnome-keyring03.4.1-1
ii  libmission-control-plugins0  1:5.12.1-2
ii  libnm-glib4  0.9.4.0-5
ii  libtelepathy-glib0   0.19.3-1
ii  libupower-glib1  0.9.17-1

telepathy-mission-control-5 recommends no packages.

Versions of packages telepathy-mission-control-5 suggests:
ii  telepathy-haze  0.6.0-1

-- no debconf information


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

Bug#681269: marked as done (does not install alternatives correctly if only openjdk-7-jre is installed)

[Debian Bug Tracking System]

Your message dated Thu, 06 Sep 2012 14:47:51 +
with message-id 
and subject line Bug#681269: fixed in icedtea-web 1.3-1
has caused the Debian Bug report #681269,
regarding does not install alternatives correctly if only openjdk-7-jre is 
installed
to be marked as done.

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

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


-- 
681269: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681269
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: icedtea-netx
Version: 1.2-2
Severity: serious

When only 7 version of openjdk is installed on the system
(which should be fine according to dependencies), icedtea-netx
still tries to do something with openjdk-6.  Namely, the
only two alternaitves/links/scripts this package provides,
javaws and itweb-settings, both does not work:

$ javaws
/usr/bin/javaws: line 66: /usr/lib/jvm/java-6-openjdk-i386/jre/bin/java: No 
such file or directory

And indeed, /usr/lib/jvm/java-6-openjdk-i386/jre/bin/java does
not exist, it is in /usr/lib/jvm/java-7-openjdk-i386/jre/bin/java
instead.

So, either the dependency is not right (the second alternative,
openjdk-6-jre (>= 6b23~pre10~) | openjdk-7-jre), or the
update-alternatives in the postinst is not correct.

I suspect it is the latter, but the postinst script should
check for the java binary presence (which is provided by
another package), not javaws or itweb-settings, which both
are provided by this package -- so the logic in the
postinst script makes no sense.

Thanks,

/mjt

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

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

Versions of packages icedtea-netx depends on:
ii  icedtea-netx-common  1.2-2
ii  openjdk-7-jre7~u3-2.1.1-1

icedtea-netx recommends no packages.

icedtea-netx suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: icedtea-web
Source-Version: 1.3-1

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

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

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated icedtea-web package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 06 Sep 2012 15:15:52 +0200
Source: icedtea-web
Binary: icedtea-netx icedtea6-plugin icedtea-plugin icedtea-netx-common 
icedtea-6-plugin icedtea-7-plugin
Architecture: source amd64 all
Version: 1.3-1
Distribution: unstable
Urgency: high
Maintainer: OpenJDK Team 
Changed-By: Matthias Klose 
Description: 
 icedtea-6-plugin - web browser plugin based on OpenJDK and IcedTea to execute 
Java a
 icedtea-7-plugin - web browser plugin based on OpenJDK and IcedTea to execute 
Java a
 icedtea-netx - NetX - implementation of the Java Network Launching Protocol 
(JNL
 icedtea-netx-common - NetX - implementation of the Java Network Launching 
Protocol (JNL
 icedtea-plugin - web browser plugin to execute Java applets (dependency 
package)
 icedtea6-plugin - web browser plugin to execute Java applets (dependency 
package)
Closes: 681269
Changes: 
 icedtea-web (1.3-1) unstable; urgency=high
 .
   * IcedTea-Web 1.3 release.
   * Security updates:
 - CVE-2012-3422: Potential read from an uninitialized memory location.
 - CVE-2012-3423: Incorrect handling of not 0-terminated strings.
   * NetX fixes:
 - PR898: signed applications with big jnlp-file doesn't start (webstart
   affect like "frozen").
 - PR811: javaws is not handling urls with spaces (and other characters
   needing encoding) correctly.
   * Plugin fixes:
 - PR820: IcedTea-Web 1.1.3 crashing Firefox when loading Citrix XenApp.
 - PR863: Error passing strings to applet methods in Chromium.
 - PR895: IcedTea-Web searches for missing classes on each loadClass or
   findClass.
 - PR861: Allow loading from non codebase hosts. Allow code to connect
   to hostin

Bug#686835: telepathy-mission-control-5: squeeze -> wheezy upgrade makes MSN accounts disappear

[Simon McVittie]

Package: telepathy-mission-control-5
Version: 1:5.12.1-2
Severity: grave
Tags: upstream
Justification: causes non-serious data loss

Mission Control 5.12 automatically migrates MSN accounts from
telepathy-butterfly to telepathy-haze. However, the migration process doesn't
actually work if telepathy-butterfly is not installed. Instead, the
butterfly account gets disabled and marked as invalid. Empathy doesn't
display accounts that are marked as invalid (which I think is a bug -
it should present account editing UI for them so they can be resurrected -
but that's unlikely to happen before wheezy).

Because telepathy-butterfly depends on papyon which depends on Farsight
which conflicts with Farstream, is removed during the upgrade from squeeze
to wheezy. The practical result is that all MSN accounts from squeeze
disappear. It is possible to get them back, but only if you're a Telepathy
expert.

I hope to be able to fix this upstream.

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

Kernel: Linux 3.2.0-3-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

Versions of packages telepathy-mission-control-5 depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.12.1-2
ii  libc62.13-35
ii  libdbus-1-3  1.6.4-1
ii  libdbus-glib-1-2 0.100-1
ii  libglib2.0-0 2.32.3-1
ii  libgnome-keyring03.4.1-1
ii  libmission-control-plugins0  1:5.12.1-2
ii  libnm-glib4  0.9.4.0-5
ii  libtelepathy-glib0   0.19.3-1
ii  libupower-glib1  0.9.17-1

telepathy-mission-control-5 recommends no packages.

Versions of packages telepathy-mission-control-5 suggests:
ii  telepathy-haze  0.6.0-1

-- no debconf information


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

Bug#672616: FTBFS: Binary files - and ./test/coretest.out differ

[Peter Pentchev]

tags 672616 + pending
thanks

On Thu, Aug 02, 2012 at 03:23:15AM +0200, Tobias Hansen wrote:
> tags 672616 patch
> thanks
> 
> The package builds fine here with gcc-4.7 on wheezy and sid with the
> attached patch.
> 
> Best regards,
> Tobias

Tobias, thanks a lot for this patch, and sorry that it took me some time
to actually get around to working on this GForth RC bug!

I have now prepared a minimal-changes upload to unstable:
- include this patch
- temporarily add gforth to Build-Depends to allow it to bootstrap
  itself after patching a core file; from what Anton Ertl said in the
  bug discussion I gather that with the next upstream version the stock
  kernels will include this change and then we won't need to pull
  ourselves out of the swamp by our own bootstraps :)
- stash and restore two affected files

I have uploaded the updated package to mentors.d.n:
http://mentors.debian.net/debian/pool/main/g/gforth/gforth_0.7.0+ds1-7.dsc

Nicholas, Luk, Patrick (the three DDs who have sponsored my recent GForth
uploads), could any of you find a couple of minutes to take a look and
possibly upload this update and fix the RC bug?  Thanks in advance!

G'luck,
Peter

-- 
Peter Pentchev  r...@ringlet.net r...@freebsd.org pe...@packetscale.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint FDBA FD79 C26F 3C51 C95E  DF9E ED18 B68D 1619 4553
If I had finished this sentence,


signature.asc
Description: Digital signature

Processed: Re: FTBFS: Binary files - and ./test/coretest.out differ

[Debian Bug Tracking System]

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

> tags 672616 + pending
Bug #672616 [gforth] FTBFS: Binary files - and ./test/coretest.out differ
Added tag(s) pending.
> thanks
Stopping processing here.

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


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

Bug#686833: git-extras - git-gh-pages - removes all files

[Jesús Espino]

Hi Jonas:

I have sended it to the upstream. And i will try to send a patch if I
have some time to it.

Thanks.

On Thu, Sep 6, 2012 at 3:55 PM, Jonas Genannt
 wrote:
> Package: git-extras
> Severity: grave
> Version: 1.7.0-1
>
> Hello,
>
> thanks for maintaining git-extras in Debian.
>
> git-gh-pages is _really_ dangerous - If you run git-gh-pages in your
> git directory it will delete all files (also uncommited!).
>
> git-gh-pages should confirm that operation and also use stash to stash
> that uncommited changes.
>
> Thanks,
> Jonas


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

Bug#686833: git-extras - git-gh-pages - removes all files

[Jonas Genannt]

Package: git-extras
Severity: grave
Version: 1.7.0-1

Hello,

thanks for maintaining git-extras in Debian.

git-gh-pages is _really_ dangerous - If you run git-gh-pages in your
git directory it will delete all files (also uncommited!).

git-gh-pages should confirm that operation and also use stash to stash
that uncommited changes.

Thanks,
Jonas


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

Bug#683021: marked as done (FTBFS on arm*: multiple definition of `typeinfo for FunctionParserBase::FunctionWrapper')

[Debian Bug Tracking System]

Your message dated Thu, 6 Sep 2012 09:46:26 -0400
with message-id 

and subject line fparser removed from archive
has caused the Debian Bug report #683021,
regarding FTBFS on arm*: multiple definition of `typeinfo for 
FunctionParserBase::FunctionWrapper'
to be marked as done.

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

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


-- 
683021: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683021
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fparser
Version: 4.5-0.1
Severity: serious
Justification: fails to build from source


fparser fails to build from source on arm*, but built in the past:

/bin/bash ./libtool --tag=CXX   --mode=link g++  -g -O2 -release 4.3  -o 
libfparser.la -rpath /usr/lib fparser.lo fpoptimizer.lo  
libtool: link: g++  -fPIC -DPIC -shared -nostdlib 
/usr/lib/gcc/arm-linux-gnueabi/4.6/../../../arm-linux-gnueabi/crti.o 
/usr/lib/gcc/arm-linux-gnueabi/4.6/crtbeginS.o  .libs/fparser.o 
.libs/fpoptimizer.o   -L/usr/lib/gcc/arm-linux-gnueabi/4.6 
-L/usr/lib/gcc/arm-linux-gnueabi/4.6/../../../arm-linux-gnueabi 
-L/usr/lib/gcc/arm-linux-gnueabi/4.6/../../.. -L/lib/arm-linux-gnueabi 
-L/usr/lib/arm-linux-gnueabi -lstdc++ -lm -lc -lgcc_s 
/usr/lib/gcc/arm-linux-gnueabi/4.6/crtendS.o 
/usr/lib/gcc/arm-linux-gnueabi/4.6/../../../arm-linux-gnueabi/crtn.o  -O2   
-Wl,-soname -Wl,libfparser-4.3.so -o .libs/libfparser-4.3.so
.libs/fpoptimizer.o:(.rodata+0x1b0c): multiple definition of `typeinfo name for 
FunctionParserBase::FunctionWrapper'
.libs/fparser.o:(.rodata+0x1e8): first defined here
.libs/fpoptimizer.o:(.data.rel.ro+0x0): multiple definition of `typeinfo for 
FunctionParserBase::FunctionWrapper'
.libs/fparser.o:(.data.rel.ro+0x0): first defined here
collect2: ld returned 1 exit status
make[1]: *** [libfparser.la] Error 1
make[1]: Leaving directory 
`/build/buildd-fparser_4.5-0.1-armel-aHWgBY/fparser-4.5'
dh_auto_build: make -j1 returned exit code 2
make: *** [build-arch] Error 2

https://buildd.debian.org/status/fetch.php?pkg=fparser&arch=armel&ver=4.5-0.1&stamp=1338356252
https://buildd.debian.org/status/fetch.php?pkg=fparser&arch=armhf&ver=4.5-0.1&stamp=1338357033
--- End Message ---
--- Begin Message ---
fparser removed from archive
See:
http://packages.qa.debian.org/f/fparser/news/20120904T152959Z.html


We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

   fparser |  4.3-4 | source
   fparser |4.5-0.1 | source
libfparser-4.3 |  4.3-4 | armel, armhf
libfparser-4.3 |4.5-0.1 | amd64, hurd-i386, i386, ia64,
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x,
sparc
libfparser-4.3-dbg |  4.3-4 | armel, armhf
libfparser-4.3-dbg |4.5-0.1 | amd64, hurd-i386, i386, ia64,
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x,
sparc
libfparser-dev |  4.3-4 | armel, armhf
libfparser-dev |4.5-0.1 | amd64, hurd-i386, i386, ia64,
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x,
sparc

--- Reason ---
ROM; RC buggy, no more rdepends
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors (ftp.debian.org
included) until the next dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 686...@bugs.debian.org.

The full log for this bug can be viewed at http://bugs.debian.org/686577

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@debian.org.

Debian distribution maintenance software
pp.
Alexander Reichle-Schmehl (the ftpmaster behind the curtain)--- End 

Bug#683021: fparser removed from archive

[Scott Howard]

fparser removed from archive
See:
http://packages.qa.debian.org/f/fparser/news/20120904T152959Z.html


We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

   fparser |  4.3-4 | source
   fparser |4.5-0.1 | source
libfparser-4.3 |  4.3-4 | armel, armhf
libfparser-4.3 |4.5-0.1 | amd64, hurd-i386, i386, ia64,
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x,
sparc
libfparser-4.3-dbg |  4.3-4 | armel, armhf
libfparser-4.3-dbg |4.5-0.1 | amd64, hurd-i386, i386, ia64,
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x,
sparc
libfparser-dev |  4.3-4 | armel, armhf
libfparser-dev |4.5-0.1 | amd64, hurd-i386, i386, ia64,
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x,
sparc

--- Reason ---
ROM; RC buggy, no more rdepends
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors (ftp.debian.org
included) until the next dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 686...@bugs.debian.org.

The full log for this bug can be viewed at http://bugs.debian.org/686577

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@debian.org.

Debian distribution maintenance software
pp.
Alexander Reichle-Schmehl (the ftpmaster behind the curtain)


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

Bug#675971: #675971 -- are you willing to help?

[Chris Knadle]

Ron --- I know you'd like the celt 0.7.1 library to be removed from Wheezy.  
Are you willing to help put together an upload a new mumble package containing 
embedded celt 0.7.1 (as the tech-ctte has outlined) so that can happen?  What 
version of mumble do you think is appropriate for this purpose?

-- 

  -- Chris

Chris Knadle
chris.kna...@coredump.us


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

Bug#686260: [LCFC] templates://mathematica-fonts/{templates,control}

[David Prévot]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,

Le 06/09/2012 04:06, Jonathan Nieder a écrit :

>> I think the "licesne itself" should not be translated

Sure, that's already covered by the “#flag:translate!:3-5”: starting
with “WRI licenses Mathematica fonts to individual users [...]” until
the end is not translatable. The only part translatable for this last
screen boils down to “License for Mathematica fonts” and the following
paragraph “Read this agreement carefully before proceeding. It is an
agreement [...] below, you are accepting the terms of this agreement”.
If that paragraph shouldn't be translated either, we can tweak the
configuration too.

> I think po-debconf has a way of marking some lines as untranslatable.
> Could that or something like
> 
>  # TRANSLATORS: please include the untranslated license
>  # in addition to your translation if you translate it.

No: it will only show up a comment in gettext PO files. As documented in
po-debconf(7), the debconf way to do that is using “#flag:comment:1” as
already existing in this file, but better directly not show up the
untranslatable text to translators as already set.

Regards

David

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iQIcBAEBCAAGBQJQSIegAAoJELgqIXr9/gnyJGoP/Rf6x+yWyr7nofmr4sOrK2JP
137DguGg737IGeypglm5kGSazhajnx3Z5FU0wbHG9EHCCD2JbyNqr8cRzO6D2iVP
wA7mspkulB2HdbIuHX5mu+Rsgbxux2vKp9nFUiLqmTcfLV92pbxqQhlS8ayEgUyX
+Fa9es8lmBS8xP2Ys7VUMo3ELq60LYGfRfqcAkXs5362qMeHO72IRGKNsMAp16np
IaBg+GXcywh4q8CYLZwP5hSqap4y6/onQ0ZGxx66ar3TuUmgv+9p3w0FM5ktr0YZ
X+dWOXTJC7VnAEcb/cYsmGyN7IHHHJ5DTp3D8BNIxAGh8rgrSJ1mBUaOXjb1i+/p
Yn4VB6MzmElwIzbM+kIxFNyQZwQOgY4KiBJ1IGSM7TcgyvjFquZLQx6WZ0+sB5go
1f4LXywJsszeGVOVyf4+2P5WtxRp9mvrGcK72f86gG7uDYkjSq8LZywNt0c754n1
KB4+mZsURiOl1tcTuxPorYTF5E2Zve2U+0WkjCSkFStVvcM5pDimz9GY71ptPkBi
P+xsZ2/5FZchpy4qSEQc+Kxdn2+pkiylbxpAHsNSE4yEyGjdrPSRpxZzPDNjHaT6
beiVTFjnLgLT3d0WbLY+de8n4wAMgCWS4uAlj63/ng3jJ6vxFEQNnrmX6aVvjuHR
9a2GRjYhqDLGupB2rpJ8
=6lG4
-END PGP SIGNATURE-


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

Bug#684923: fontconfig-config: Please stop messing with my /etc

[Fabian Greffrath]

Am 06.09.2012 12:37, schrieb Cyril Brulebois:

(A) The filename is wrong.


Yes, I am sorry I mixed up the file names.


(B) Removing the symlink is documented and not honored.


It's another symlink than the one you changed. Compare 
"70-yes-bitmaps.conf" vs. "30-debconf-no-bitmaps.conf".


But in the end, it's documented what fontconfig expects from its users 
in order to change this setting and explicit instructions are given. 
You tried to solve it differently and it failed on you.


 - Fabian


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

Bug#684923: fontconfig-config: Please stop messing with my /etc

[Cyril Brulebois]

Fabian Greffrath  (06/09/2012):
> Am 05.09.2012 10:32, schrieb Cyril Brulebois:
> >Says which doc? None AFAICT. Does conf.d/README talk about debconf at
> >all? Hell no.
> 
> No, but it says
> 
>  If you wish to enable bitmapped fonts manually, either reconfigure
>  this package (with dpkg-reconfigure fontconfig-config), or remove
>  the symbolic link /etc/fonts/conf.d/30-debconf-no-bitmaps.conf
> 
> which you did not follow, either.

Verbatim copy of said file:
| conf.d/README
| 
| Each file in this directory is a fontconfig configuration file.  Fontconfig
| scans this directory, loading all files of the form [0-9][0-9]*.conf.
| These files are normally installed in ../conf.avail and then symlinked here,
| allowing them to be easily installed and then enabled/disabled by adjusting
| the symlinks.
| 
| The files are loaded in numeric order, the structure of the configuration
| has led to the following conventions in usage:
| 
|  Files begining with:   Contain:
| 
|  00 through 09  Font directories
|  10 through 19  system rendering defaults (AA, etc)
|  20 through 29  font rendering options
|  30 through 39  family substitution
|  40 through 49  generic identification, map family->generic
|  50 through 59  alternate config file loading
|  60 through 69  generic aliases, map generic->family
|  70 through 79  select font (adjust which fonts are available)
|  80 through 89  match target="scan" (modify scanned patterns)
|  90 through 99  font synthesis

Let's assume you were talking about fontconfig's README.Debian instead;
it has:
| If you wish to enable bitmapped fonts manually, either reconfigure this
| package (with dpkg-reconfigure fontconfig-config), or remove the
| symbolic link /etc/fonts/conf.d/30-debconf-no-bitmaps.conf

(A) The filename is wrong.
(B) Removing the symlink is documented and not honored.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Processed: Re: Bug#686817: grub-pc: Add option to change keyboard layout

[Debian Bug Tracking System]

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

> severity 686817 important
Bug #686817 [grub-pc] grub-pc: Add option to change keyboard layout
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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


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

Bug#686817: grub-pc: Add option to change keyboard layout

[Colin Watson]

severity 686817 important
thanks

On Thu, Sep 06, 2012 at 11:36:03AM +0200, Paul Menzel wrote:
> in my opinion it should be possible for the user to easily change the
> keyboard layout for the boot loader. Especially in 2012. So I put the
> severity to serious as I think this should be solved for Wheezy.

While I would like to get this fixed, I don't consider it RC.  Please
note that the "unsuitable for release" case for "serious" is "in the
package maintainer's or release manager's opinion" - feel free to appeal
to the release team.

In particular, this is not a regression from any previous version of
Debian, and there are so many other things to do in GRUB that actually
stop people booting, which is clearly worse than having the wrong
keyboard layout.

We're far enough along that advanced users can at least set this up
themselves, which is better than the previous situation.

> As far as my tests and my online search goes, that is currently not
> possible in Debian [1]. Fedora seems to offer that possibility and GRUB
> too [2].

Could you support your comment about Fedora with a reference to some
code or documentation?  While Fedora installs the grub-kbdcomp tool (as
grub2-kbdcomp), I don't see anything in their spec file that actually
makes use of it; so unless there's some configuration in a separate
package, they appear to be no further along than Debian.

> Probably #686815 [3] needs to be resolved for that first.

I don't see why; GRUB could reasonably offer keyboard layout
configuration only if console-setup is installed.

-- 
Colin Watson   [cjwat...@debian.org]


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

Bug#686818: When given an "" as security mirror, it use the default security mirror

[YunQiang Su]

Package: simple-cdd
Version: 0.3.14
Severity: serious
Tags: patch

In /usr/bin/build-simple-cdd, the line 171

if [ -n "$security_mirror" ] && [ "true" = "$use_security_mirror" ]; then

the -z should be -n


-- 
YunQiang Su


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

Bug#686817: grub-pc: Add option to change keyboard layout

[Paul Menzel]

Package: grub-pc
Version: 1.99-22.1
Severity: serious

Dear Debian folks,


in my opinion it should be possible for the user to easily change the
keyboard layout for the boot loader. Especially in 2012. So I put the
severity to serious as I think this should be solved for Wheezy.

As far as my tests and my online search goes, that is currently not
possible in Debian [1]. Fedora seems to offer that possibility and GRUB
too [2].

Probably #686815 [3] needs to be resolved for that first.

Additionally an option should be added to `/etc/default/grub` like
discussed on the Talk page in the ArchWiki [2].

GRUB_TERMINAL_INPUT=at_keyboard
KEYBOARD_LAYOUT=de

Lastly `/etc/grub.d/05_keyboard_layout` needs to be created with

insmod keylayouts
keymap /boot/grub/$KEYBOARD_LAYOUT.gkb

where the last line should ideally be also read from `/etc/default/grub`
and `update-grub` should take care of generating the keymap file using
`grub-kbdcomp`.

If that is not possible a big section should be added to the release
notes.

Currently Debian Wheezy does not support to easily change the
keyboard layout for its default boot loader GRUB 2 (grub-pc).
Please read the page  in the Debian Wiki on
how to do that manually.

Please note that when Debian GNU/Linux starts, it uses an
initial RAM file system which can set the used keyboard layout
for entering for example the LUKS password for encrypted
devices. You need to install the package `console-setup` to
configure that.


Thanks,

Paul


[1] http://debianforum.de/forum/viewtopic.php?f=12&t=116672
[2] https://wiki.archlinux.org/index.php/Talk:GRUB2#Custom_keyboard_layout
[3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686815

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

Kernel: Linux 3.2.0-3-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/bash

Versions of packages grub-common depends on:
ii  gettext-base0.18.1.1-9
ii  libc6   2.13-35
ii  libdevmapper1.02.1  2:1.02.74-4
ii  libfreetype62.4.9-1
ii  libfuse22.9.0-5
ii  zlib1g  1:1.2.7.dfsg-13

Versions of packages grub-common recommends:
ii  os-prober  1.55

Versions of packages grub-common suggests:
ii  desktop-base   7.0.3
pn  grub-emu   
pn  multiboot-doc  
ii  xorriso1.2.2-2

-- no debconf information


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

Bug#686812: marked as done (swift: CVE-2012-4406)

[Debian Bug Tracking System]

Your message dated Thu, 06 Sep 2012 09:03:00 +
with message-id 
and subject line Bug#686812: fixed in swift 1.4.8-2
has caused the Debian Bug report #686812,
regarding swift: CVE-2012-4406
to be marked as done.

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

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


-- 
686812: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686812
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: swift
Severity: grave
Tags: security
Justification: user security hole

This was assigned CVE-2012-4406:
https://bugs.launchpad.net/swift/+bug/1006414

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: swift
Source-Version: 1.4.8-2

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

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

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated swift package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 06 Sep 2012 08:40:18 +
Source: swift
Binary: python-swift swift swift-proxy swift-object swift-container 
swift-account swift-doc
Architecture: source all
Version: 1.4.8-2
Distribution: unstable
Urgency: high
Maintainer: PKG OpenStack 
Changed-By: Thomas Goirand 
Description: 
 python-swift - OpenStack Object Storage - libraries
 swift  - OpenStack Object Storage - common files
 swift-account - OpenStack Object Storage - account server
 swift-container - OpenStack Object Storage - container server
 swift-doc  - OpenStack Object Storage - documentation
 swift-object - OpenStack Object Storage - object server
 swift-proxy - OpenStack Object Storage - proxy server
Closes: 686812
Changes: 
 swift (1.4.8-2) unstable; urgency=high
 .
   * CVE-2012-4406: Do not use pickle for serialization in memcache, but JSON
   (Closes: #686812).
Checksums-Sha1: 
 8eb4306e03af91b02b7460b5b7bf56b1bcb7b896 1803 swift_1.4.8-2.dsc
 a0bcebc9c8394c6db123c9963407fe8e66f05b61 16404 swift_1.4.8-2.debian.tar.gz
 5ab786eacb09038e3163c6d07379af15a216a012 165356 python-swift_1.4.8-2_all.deb
 948dc7f6ddb9f48c32b51c339f91f4337c21 42818 swift_1.4.8-2_all.deb
 85c90fedc1d8551394b5c7767751d6eda9698b37 12546 swift-proxy_1.4.8-2_all.deb
 e24a66913dc6b01ff21b5868bda790e2b57df6c3 12894 swift-object_1.4.8-2_all.deb
 9f3c10343dfa0259ed3741f6b936dd1964d4eed4 11242 swift-container_1.4.8-2_all.deb
 69a68a16d345d3aca0943f1bb05e0f04e5317293 11366 swift-account_1.4.8-2_all.deb
 e73e41ecc684a873c231bf7dfe37fe59b05e1c55 255616 swift-doc_1.4.8-2_all.deb
Checksums-Sha256: 
 a648bb1f05ea89a3580f251f56ba81e67c47f93728981a4f09bdb195e59b3beb 1803 
swift_1.4.8-2.dsc
 656b793df9d27ae30c5617b27464c8559a4c2f0264de4b532771521b71d908ac 16404 
swift_1.4.8-2.debian.tar.gz
 cf6452e259d60d61a8b3e404f22d230e47fd28078ec7deeab388b0fbe58b5621 165356 
python-swift_1.4.8-2_all.deb
 8e282689ee6e391d8c2469c94edb67d752452b5f261b78f2e2f39a90c4c9d951 42818 
swift_1.4.8-2_all.deb
 84a543210847d8c3f33f3d8dc5b57c261bc6e3ce7361f9d14fda9f55028ca9f7 12546 
swift-proxy_1.4.8-2_all.deb
 a1d3a3a8d0cb3580e97306b3f1c8238467e287b0f4be225f5eb7f3c61d16bfee 12894 
swift-object_1.4.8-2_all.deb
 e9df54859d80b0fb18bd853aa09c09379ed565eccb5b79b45fcd001fb7910564 11242 
swift-container_1.4.8-2_all.deb
 347e4a1c710652c97d49c0cc699fee4b98b81585c1bd78e6173c4f05089b0266 11366 
swift-account_1.4.8-2_all.deb
 9c573c25f4ffeb2898b1a168999297069c53e2d8399b260c13e41c545ca02467 255616 
swift-doc_1.4.8-2_all.deb
Files: 
 e704b2379b4e967c0b41fe606ab923ea 1803 net optional swift_1.4.8-2.dsc
 923f045213a3762f01203088923d23b7 16404 net optional swift_1.4.8-2.debian.tar.gz
 c7bbce63d1ebef5eebf2ed53b3d34fc2 165356 python optional 
python-swift_1.4.8-2_all.deb
 57b777a5a246f3c73d43a4dc9aa9c3a6 42818 net optional swift_1.4.8-2_all.deb
 9a9b69a4136d4eac7c52891d51de1e56 12546 net optional swift-proxy_1.4.8-2_all.deb
 791d01bae18c2a8c249b1f3f8f1b72ce 12894 net optional 
swift-object_1.4.8-2_all.deb
 6fa744f0aca5882c0519a530a125f2b3 11242 net optional 
swift-container_1.4.8-2_all.deb
 49926bedbddb9a981fbc3f7a894ed7f7 11366 net optional 
swift-account_1.4.8-2_all.deb
 d9b372191a6b55a0555485fec0fabdb0 255616 doc optional swift-doc_1.4.8-2_a

Bug#686260: [LCFC] templates://mathematica-fonts/{templates,control}

[Jonathan Nieder]

Hi,

Atsuhito Kohda wrote:

> I think the "licesne itself" should not be translated

I think po-debconf has a way of marking some lines as untranslatable.
Could that or something like

 # TRANSLATORS: please include the untranslated license
 # in addition to your translation if you translate it.

work?

Thanks for an interesting example,
Jonathan


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

Bug#684923: fontconfig-config: Please stop messing with my /etc

[Fabian Greffrath]

Am 05.09.2012 10:32, schrieb Cyril Brulebois:

Says which doc? None AFAICT. Does conf.d/README talk about debconf at
all? Hell no.


No, but it says

 If you wish to enable bitmapped fonts manually, either reconfigure
 this package (with dpkg-reconfigure fontconfig-config), or remove
 the symbolic link /etc/fonts/conf.d/30-debconf-no-bitmaps.conf

which you did not follow, either.

 - Fabian


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

Bug#686260: [LCFC] templates://mathematica-fonts/{templates,control}

[Atsuhito Kohda]

Hi all,

thanks for your contributions.
I'd like to ask you one point.

On Thu, 30 Aug 2012 12:27:43 -0400, David Prévot wrote:

> A small typo in one of the templates (missing prepending underscore)
> prevent one screen to be translated. 

I think the "licesne itself" should not be translated
so missing underscore for 
Description: License for Mathematica fonts
was intentional.  If your intention is to translate
the license itself, please let me know the reason for it.

If your intention is to translate only "License for 
Mathematica fonts" but not to translate the license itself, 
I doubt prepending underscore achieve it.
If I'm wrong please let me know.
Thanks again.  

Best regards.   2012-9-6(Thu)

-- 
 Debian Developer - much more I18N of Debian
 Atsuhito Kohda 
 Department of Math., Univ. of Tokushima


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

Bug#685060: marked as done (corosync: fails to install: postinst fails on update-rc.d call)

[Debian Bug Tracking System]

Your message dated Thu, 06 Sep 2012 07:32:55 +
with message-id 
and subject line Bug#685060: fixed in corosync 1.4.4-2
has caused the Debian Bug report #685060,
regarding corosync: fails to install: postinst fails on update-rc.d call
to be marked as done.

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

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


-- 
685060: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685060
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: corosync
Version: 1.4.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Setting up corosync (1.4.4-1) ...
  invoke-rc.d: policy-rc.d denied execution of start.
  usage: update-rc.d [-n] [-f]  remove
 update-rc.d [-n]  defaults [NN | SS KK]
 update-rc.d [-n]  start|stop NN runlvl [runlvl] [...] .
 update-rc.d [-n]  disable|enable [S|2|3|4|5]
-n: not really
-f: force
  
  The disable|enable API is not stable and might change in the future.
  dpkg: error processing corosync (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of piuparts-depends-dummy:
   piuparts-depends-dummy depends on corosync (>= 1.4.1) | heartbeat (>= 3.0); 
however:
Package corosync is not configured yet.
Package heartbeat is not installed.
  
  dpkg: error processing piuparts-depends-dummy (--configure):
   dependency problems - leaving unconfigured

cheers,

Andreas


pacemaker_1.1.7-1.log.gz
Description: GNU Zip compressed data
--- End Message ---
--- Begin Message ---
Source: corosync
Source-Version: 1.4.4-2

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

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

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

Debian distribution maintenance software
pp.
Guido Günther  (supplier of updated corosync package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 06 Sep 2012 09:10:31 +0200
Source: corosync
Binary: corosync corosync-dbg corosync-dev libcorosync4 libcorosync-dev libcfg4 
libconfdb4 libcoroipcc4 libcoroipcs4 libcpg4 libevs4 liblogsys4 libpload4 
libquorum4 libsam4 libtotem-pg4 libvotequorum4 libcfg-dev libconfdb-dev 
libcoroipcc-dev libcoroipcs-dev libcpg-dev libevs-dev liblogsys-dev 
libpload-dev libquorum-dev libsam-dev libtotem-pg-dev libvotequorum-dev
Architecture: source i386 all
Version: 1.4.4-2
Distribution: unstable
Urgency: low
Maintainer: Debian HA Maintainers 

Changed-By: Guido Günther 
Description: 
 corosync   - Standards-based cluster framework (daemon and modules)
 corosync-dbg - Standards-based cluster framework (debugging symbols)
 corosync-dev - Standards-based cluster framework (generic devel files)
 libcfg-dev - Standards-based cluster framework, Cfg devel files
 libcfg4- Standards-based cluster framework, Cfg library
 libconfdb-dev - Standards-based cluster framework, Confdb devel files
 libconfdb4 - Standards-based cluster framework, Confdb library
 libcoroipcc-dev - Standards-based cluster framework, CoroIPCC devel files
 libcoroipcc4 - Standards-based cluster framework, Coroipcc library
 libcoroipcs-dev - Standards-based cluster framework, CoroIPCS devel files
 libcoroipcs4 - Standards-based cluster framework, Coroipcs library
 libcorosync-dev - Standards-based cluster framework (transitional package)
 libcorosync4 - Standards-based cluster framework (transitional package)
 libcpg-dev - Standards-based cluster framework, Cpg devel files
 libcpg4- Standards-based cluster framework, Cpg library
 libevs-dev - Standards-based cluster framework, Evs devel files
 libevs4- Standards-based cluster framework, Evs library
 liblogsys-dev - Standards-based cluster framework, Logsys devel files
 liblogsys4 - Standards-based cluster framework, Logsys library
 libpload-dev - Standards-based cluster framework, Pload devel files
 libpload4  - Standards-based cluster fram

Processed: fixed 651225 in 1:1.8.9-1

[Debian Bug Tracking System]

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

> # These four CVEs are fixed in 1.8.9 or earlier.
> fixed 651225 1:1.8.9-1
Bug #651225 {Done: Christoph Haas } [zabbix] Security 
vulnerabilities (CVE-2011-2904, CVE-2011-3263, CVE-2011-3265, CVE-2011-4674)
There is no source info for the package 'zabbix' at version '1:1.8.9-1' with 
architecture ''
Unable to make a source version for version '1:1.8.9-1'
Marked as fixed in versions 1:1.8.9-1.
> thanks
Stopping processing here.

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


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

Bug#686812: swift: CVE-2012-4406

[Moritz Muehlenhoff]

Package: swift
Severity: grave
Tags: security
Justification: user security hole

This was assigned CVE-2012-4406:
https://bugs.launchpad.net/swift/+bug/1006414

Cheers,
Moritz


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

Processed: found 651225 in 1:1.8.2-1, found 683273 in 1:1.8.2-1

[Debian Bug Tracking System]

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

> found 651225 1:1.8.2-1
Bug #651225 {Done: Christoph Haas } [zabbix] Security 
vulnerabilities (CVE-2011-2904, CVE-2011-3263, CVE-2011-3265, CVE-2011-4674)
There is no source info for the package 'zabbix' at version '1:1.8.2-1' with 
architecture ''
Unable to make a source version for version '1:1.8.2-1'
Marked as found in versions 1:1.8.2-1.
> # mark as found not only in upload to squeeze, but also in earlier upload to 
> unstable
> found 683273 1:1.8.2-1
Bug #683273 {Done: Dmitry Smirnov } [zabbix] 
CVE-2012-3435
There is no source info for the package 'zabbix' at version '1:1.8.2-1' with 
architecture ''
Unable to make a source version for version '1:1.8.2-1'
Marked as found in versions 1:1.8.2-1.
> thanks
Stopping processing here.

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


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