Processed: found 709967 in None, found 709967 in sun-java5-doc/1.5.0-22-0lenny1 ..., found 709967 in wheezy/None ...

[Debian Bug Tracking System]

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

> found 709967 None
Bug #709967 [sun-java5-doc,sun-java6-doc] sun-java[56]-doc: download location 
no longer available
Warning: Unknown package 'sun-java5-doc'
Warning: Unknown package 'sun-java6-doc'
There is no source info for the package 'sun-java5-doc' at version 'None' with 
architecture ''
There is no source info for the package 'sun-java6-doc' at version 'None' with 
architecture ''
Unable to make a source version for version 'None'
Marked as found in versions None.
Warning: Unknown package 'sun-java5-doc'
Warning: Unknown package 'sun-java6-doc'
> found 709967 sun-java5-doc/1.5.0-22-0lenny1
Bug #709967 [sun-java5-doc,sun-java6-doc] sun-java[56]-doc: download location 
no longer available
Warning: Unknown package 'sun-java5-doc'
Warning: Unknown package 'sun-java6-doc'
The source sun-java5-doc and version 1.5.0-22-0lenny1 do not appear to match 
any binary packages
Marked as found in versions sun-java5-doc/1.5.0-22-0lenny1.
Warning: Unknown package 'sun-java5-doc'
Warning: Unknown package 'sun-java6-doc'
> found 709967 sun-java6-doc/6-26-0lenny1
Bug #709967 [sun-java5-doc,sun-java6-doc] sun-java[56]-doc: download location 
no longer available
Warning: Unknown package 'sun-java5-doc'
Warning: Unknown package 'sun-java6-doc'
The source sun-java6-doc and version 6-26-0lenny1 do not appear to match any 
binary packages
Marked as found in versions sun-java6-doc/6-26-0lenny1.
Warning: Unknown package 'sun-java5-doc'
Warning: Unknown package 'sun-java6-doc'
> found 709967 squeeze/None
Bug #709967 [sun-java5-doc,sun-java6-doc] sun-java[56]-doc: download location 
no longer available
Warning: Unknown package 'sun-java5-doc'
Warning: Unknown package 'sun-java6-doc'
The source squeeze and version None do not appear to match any binary packages
Marked as found in versions squeeze/None.
Warning: Unknown package 'sun-java5-doc'
Warning: Unknown package 'sun-java6-doc'
> found 709967 wheezy/None
Bug #709967 [sun-java5-doc,sun-java6-doc] sun-java[56]-doc: download location 
no longer available
Warning: Unknown package 'sun-java5-doc'
Warning: Unknown package 'sun-java6-doc'
The source wheezy and version None do not appear to match any binary packages
Marked as found in versions wheezy/None.
Warning: Unknown package 'sun-java5-doc'
Warning: Unknown package 'sun-java6-doc'
> found 709967 jessie/None
Bug #709967 [sun-java5-doc,sun-java6-doc] sun-java[56]-doc: download location 
no longer available
Warning: Unknown package 'sun-java5-doc'
Warning: Unknown package 'sun-java6-doc'
The source jessie and version None do not appear to match any binary packages
Marked as found in versions jessie/None.
Warning: Unknown package 'sun-java5-doc'
Warning: Unknown package 'sun-java6-doc'
> close 709967
Bug #709967 [sun-java5-doc,sun-java6-doc] sun-java[56]-doc: download location 
no longer available
Warning: Unknown package 'sun-java5-doc'
Warning: Unknown package 'sun-java6-doc'
Marked Bug as done
Warning: Unknown package 'sun-java5-doc'
Warning: Unknown package 'sun-java6-doc'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
709967: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709967
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#709173:

[Juerg Haefliger]

Patch to add missing sysvinit scripts:


diff --git a/cloud-init-0.7.1/debian/cloud-init.cloud-config.init
b/cloud-init-0.7.1/debian/cloud-init.cloud-config.init
new file mode 100644
index 000..23d050b
--- /dev/null
+++ b/cloud-init-0.7.1/debian/cloud-init.cloud-config.init
@@ -0,0 +1,55 @@
+#! /bin/sh
+### BEGIN INIT INFO
+# Provides:  cloud-config
+# Required-Start:cloud-init cloud-init-local
+# Required-Stop:
+# Default-Start: 2 3 4 5
+# Default-Stop:  0 1 6
+# Short-Description: Cloud init modules --mode config
+# Description:   Cloud configuration initialization
+### END INIT INFO
+
+# Authors: Julien Danjou 
+#  Juerg Haefliger 
+
+PATH=/sbin:/usr/sbin:/bin:/usr/bin
+DESC="Cloud service"
+NAME=cloud-init
+DAEMON=/usr/bin/$NAME
+DAEMON_ARGS="modules --mode config"
+SCRIPTNAME=/etc/init.d/$NAME
+
+# Exit if the package is not installed
+[ -x "$DAEMON" ] || exit 0
+
+# Read configuration variable file if it is present
+[ -r /etc/default/$NAME ] && . /etc/default/$NAME
+
+# Load the VERBOSE setting and other rcS variables
+. /lib/init/vars.sh
+
+# Define LSB log_* functions.
+# Depend on lsb-base (>= 3.2-14) to ensure that this file is present
+# and status_of_proc is working.
+. /lib/lsb/init-functions
+
+case "$1" in
+start)
+   log_daemon_msg "Starting $DESC" "$NAME"
+   $DAEMON ${DAEMON_ARGS}
+   case "$?" in
+   0|1) log_end_msg 0 ;;
+   2) log_end_msg 1 ;;
+   esac
+   ;;
+stop|restart|force-reload)
+echo "Error: argument '$1' not supported" >&2
+exit 3
+;;
+*)
+   echo "Usage: $SCRIPTNAME {start}" >&2
+   exit 3
+   ;;
+esac
+
+:
diff --git a/cloud-init-0.7.1/debian/cloud-init.cloud-final.init
b/cloud-init-0.7.1/debian/cloud-init.cloud-final.init
new file mode 100644
index 000..7de5c83
--- /dev/null
+++ b/cloud-init-0.7.1/debian/cloud-init.cloud-final.init
@@ -0,0 +1,55 @@
+#! /bin/sh
+### BEGIN INIT INFO
+# Provides:  cloud-final
+# Required-Start:$all cloud-config
+# Required-Stop:
+# Default-Start: 2 3 4 5
+# Default-Stop:  0 1 6
+# Short-Description: Cloud init modules --mode final
+# Description:   Cloud configuration initialization
+### END INIT INFO
+
+# Authors: Julien Danjou 
+#  Juerg Haefliger 
+
+PATH=/sbin:/usr/sbin:/bin:/usr/bin
+DESC="Cloud service"
+NAME=cloud-init
+DAEMON=/usr/bin/$NAME
+DAEMON_ARGS="modules --mode final"
+SCRIPTNAME=/etc/init.d/$NAME
+
+# Exit if the package is not installed
+[ -x "$DAEMON" ] || exit 0
+
+# Read configuration variable file if it is present
+[ -r /etc/default/$NAME ] && . /etc/default/$NAME
+
+# Load the VERBOSE setting and other rcS variables
+. /lib/init/vars.sh
+
+# Define LSB log_* functions.
+# Depend on lsb-base (>= 3.2-14) to ensure that this file is present
+# and status_of_proc is working.
+. /lib/lsb/init-functions
+
+case "$1" in
+start)
+   log_daemon_msg "Starting $DESC" "$NAME"
+   $DAEMON ${DAEMON_ARGS}
+   case "$?" in
+   0|1) log_end_msg 0 ;;
+   2) log_end_msg 1 ;;
+   esac
+   ;;
+stop|restart|force-reload)
+echo "Error: argument '$1' not supported" >&2
+exit 3
+;;
+*)
+   echo "Usage: $SCRIPTNAME {start}" >&2
+   exit 3
+   ;;
+esac
+
+:
diff --git a/cloud-init-0.7.1/debian/cloud-init.cloud-init-local.init
b/cloud-init-0.7.1/debian/cloud-init.cloud-init-local.init
new file mode 100644
index 000..4331525
--- /dev/null
+++ b/cloud-init-0.7.1/debian/cloud-init.cloud-init-local.init
@@ -0,0 +1,55 @@
+#! /bin/sh
+### BEGIN INIT INFO
+# Provides:  cloud-init-local
+# Required-Start:$local_fs $remote_fs
+# Required-Stop:
+# Default-Start: 2 3 4 5
+# Default-Stop:  0 1 6
+# Short-Description: Cloud init local
+# Description:   Cloud configuration initialization
+### END INIT INFO
+
+# Authors: Julien Danjou 
+#  Juerg Haefliger 
+
+PATH=/sbin:/usr/sbin:/bin:/usr/bin
+DESC="Cloud service"
+NAME=cloud-init
+DAEMON=/usr/bin/$NAME
+DAEMON_ARGS="init --local"
+SCRIPTNAME=/etc/init.d/$NAME
+
+# Exit if the package is not installed
+[ -x "$DAEMON" ] || exit 0
+
+# Read configuration variable file if it is present
+[ -r /etc/default/$NAME ] && . /etc/default/$NAME
+
+# Load the VERBOSE setting and other rcS variables
+. /lib/init/vars.sh
+
+# Define LSB log_* functions.
+# Depend on lsb-base (>= 3.2-14) to ensure that this file is present
+# and status_of_proc is working.
+. /lib/lsb/init-functions
+
+case "$1" in
+start)
+   log_daemon_msg "Starting $DESC" "$NAME"
+   $DAEMON ${DAEMON_ARGS}
+   case "$?" in
+   0|1) log_end_msg 0 ;;
+   2) log_end_msg 1 ;;
+   esac
+   ;;
+stop|restart|force-reload)
+echo "Error: argument '$1' not supported" >&2
+exit 3
+;;
+*)
+   echo "Usage: $SCRIPTNAME {start}" >&2
+   exit 3
+   ;;
+esac
+
+:
diff --git a/cloud-init-0.7.1/debian/cloud-init.init
b/clo

Bug#709967: sun-java[56]-doc: download location no longer available

[Andreas Beckmann]

Package: sun-java5-doc,sun-java6-doc
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

the lenny sun-java[56]-doc installer packages are no longer useful. The
download location has changed and I failed to find a new location for
these ancient versions.

This bug report is only for marking this fact in a way recognizable by
piuparts-analyze.

>From the attached log:

  Selecting previously deselected package sun-java5-doc.
  (Reading database ... 6033 files and directories currently installed.)
  Unpacking sun-java5-doc (from .../sun-java5-doc_1.5.0-22-0lenny1_all.deb) ...
  Can not write log, openpty() failed (/dev/pts not mounted?)
  Setting up sun-java5-doc (1.5.0-22-0lenny1) ...
  This package is an installer package, it does not actually contain the
  J2SDK documentation.  You will need to go download one of the
  archives:
  
  jdk-1_5_0-doc.zip jdk-1_5_0-doc-ja.zip
  
  (choose the non-update version if this is the first installation).
  Please visit
  
  http://java.sun.com/j2se/1.5.0/download.html
  
  now and download.  The file should be owned by root.root and be copied
  to /tmp.
  
  [Press RETURN to try again, 'no' + RETURN to abort] dpkg: error processing 
sun-java5-doc (--configure):
   subprocess post-installation script returned error exit status 1
  Errors were encountered while processing:
   sun-java5-doc

  Selecting previously deselected package sun-java6-doc.
  (Reading database ... 6033 files and directories currently installed.)
  Unpacking sun-java6-doc (from .../sun-java6-doc_6-26-0lenny1_all.deb) ...
  Can not write log, openpty() failed (/dev/pts not mounted?)
  Setting up sun-java6-doc (6-26-0lenny1) ...
  This package is an installer package, it does not actually contain the
  JDK documentation.  You will need to go download one of the
  archives:
  
  jdk-6u12-docs.zip jdk-6u12-docs-ja.zip
  
  (choose the non-update version if this is the first installation).
  Please visit
  
  http://java.sun.com/javase/downloads/
  
  now and download.  The file should be owned by root.root and be copied
  to /tmp.
  
  [Press RETURN to try again, 'no' + RETURN to abort] dpkg: error processing 
sun-java6-doc (--configure):
   subprocess post-installation script returned error exit status 1
  Errors were encountered while processing:
   sun-java6-doc


Cheers,

Andreas


sun-java5-doc_1.5.0-22-0lenny1.log.gz
Description: GNU Zip compressed data

Bug#708584: versioning system/package name allows for binary incompatible libraries

[Anton Gladky]

Hi Scott,

I have uploaded the 3.7.0-5 version into DELAYED/5 queue. Feel free
to cancel/reschedule or just let me know, if you find some issues in
this version.

Best regards,

Anton

2013/5/22 Scott Howard :
> On Fri, May 17, 2013 at 1:47 AM, Anton Gladky  wrote:
>> Hi,
>>
>> I have done this upload, sorry if I broke something or offended somebody.
>
> I'm the one that should apologize, I saw that you did contact me on
> April 26, but I failed to respond.
>
>>
>> Ok, if you want, I will create libalglib3.7.0. But I do not know, whether it
>> is necessary for
>> the package, having just qtiplot in build-rdeps and with popcon 33. But you
>> are the
>> main maintainer, you should decide.
>
> qtiplot's popcon is 1091, libalglib-2.6.0 popcon was several hundred,
> libalglib3's popcon is 33.
> In the past we had a problem where people did uploads to alglib that
> broke alglib because they don't follow reasonable versioning. In fact,
> alglib used to have a blurb on their website about how they don't
> believe in build systems and everyone should hardcode their code into
> projects.
>
>
>> Why, actually, the version 2.6.0 has  been uploaded into Debian on "06 Mar
>> 2011",
>> if it was half a year obsolete and unsupported by upstream? The version
>> 3.3.0 was
>> already available [1].
>
> the only depending package in Debian required version 2.6.0, newer
> versions broke that package, so we kept it until someone needed a
> newer version (which is now, apparently).
>
>>> Does another package need it?
>>
>>
>> Yes, not (yet) uploaded into Debian.
>
> this is a good reason to work it out.
>
>>
>>>
>>> 2) Why did a team upload switch from autotools to cmake?
>>
>>
>> 3-versions are completely different from 2-vesions. It was rewritten from
>> scratch.
>> And yes, personal preferences. Why did you ask about that after uploading
>> the
>> package?
>
> Personal preference is ok, it is just something you avoid doing on NMU
> and team uploads without checking with the maintainers first (which
> you tried to do, but I missed the email)
> I'm OK with cmake, could we set the "release" ldflag instead of
> "version" as to not set the SONAME? I know how to do this in autotools
> but not with cmake. This would be similar to how libalglib-2.6.0 did
> it.
>
>>
>>>
>>> 3) Why did 1 and 2 happen without consulting with the current uploaders of
>>> alglib or the depending package?
>>>
>> That is not true and I am surprised, that you decided to discuss it here:
>>   1) I sent you and your co-maintainer an email with patches on alglib on
>> April 26th.
>>   2) May 5th the package has been uploaded into experimental.
>>   3) May 15th, the package has been uploaded into unstable.
>>
>> The first communication with you was on May 16th.
>>
>> So I think, the second part of the bug is not RC.
>> Again, sorry, if I broke something. I will try to be careful next time and
>> ready for co-maintaining.
>
> Yes, I'm sorry I missed your email on the 26th. If I didn't turn you
> off already, you're more than welcome to become an uploader/maintainer
> of this package.
>
> I appreciate your work, sorry about the miscommunication.
>
> Regarding the RC part - we should consider how to future proof the
> versioning. I prefer the "release" flag for alglib since they don't
> use sane versioning [1]. We could set the SONAME to 3.7.0, like you
> suggested, as well. In my opinion both are acceptable. If you'd like
> to add yourself as an uploader and can choose which way you prefer.
>
> [1] http://www.sourceware.org/autobook/autobook/autobook_91.html
>
> Regards,
> Scott


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

Processed: tags 707938 + patch

[Debian Bug Tracking System]

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

> tags 707938 + patch
Bug #707938 [gup] gup: fails to install, purge, and install again: 
gup.postinst: 11: cd: can't cd to /var/lib/gup/
Added tag(s) patch.
> stop
Stopping processing here.

Please contact me if you need assistance.
-- 
707938: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707938
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#709964: python2.7-minimal: purging deletes /etc/python2.7/sitecustomize.py (owned by libpython2.7-minimal)

[Andreas Beckmann]

Package: python2.7-minimal
Version: 2.7.5-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package removes files that
were installed by another package.
The removed files were already present before the package was installed,
they may have been shipped or created by a dependency.

This could be a violation of policy 10.7.4 ("Sharing configuration
files"), see
http://www.debian.org/doc/debian-policy/ch-files.html#s10.7.4
or policy chapter 6 ("Package maintainer scripts..."), see
http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html
or policy 7.6 ("Overwriting files..."), see
http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

0m23.1s ERROR: FAIL: debsums reports modifications inside the chroot:
  debsums: missing file /etc/python2.7/sitecustomize.py (from 
libpython2.7-minimal package)


This test more or less did

  apt-get install python2.7-minimal
  dpkg --purge python2.7-minimal
  debsums -a -c


cheers,

Andreas


python2.7-minimal_2.7.5-4.log.gz
Description: GNU Zip compressed data

Bug#709960: dotclear: deletes conffiles (policy 10.7.3): /etc/dotclear/{apache, lighttpd}.conf

[Andreas Beckmann]

Package: dotclear
Version: 2.5+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

10.7.3: "[...] The easy way to achieve this behavior is to make the
configuration file a conffile. [...] This implies that the default
version will be part of the package distribution, and must not be
modified by the maintainer scripts during installation (or at any
other time)."

Note that once a package ships a modified version of that conffile,
dpkg will prompt the user for an action how to handle the upgrade of
this modified conffile (that was not modified by the user).

Further in 10.7.3: "[...] must not ask unnecessary questions
(particularly during upgrades) [...]"

If a configuration file is customized by a maintainer script after
having asked some debconf questions, it may not be marked as a
conffile. Instead a template could be installed in /usr/share and used
by the postinst script to fill in the custom values and create (or
update) the configuration file (preserving any user modifications!).
This file must be removed during postrm purge.
ucf(1) may help with these tasks.
See also http://wiki.debian.org/DpkgConffileHandling

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

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

0m44.4s ERROR: FAIL: debsums reports modifications inside the chroot:
  debsums: missing file /etc/dotclear/apache.conf (from dotclear package)
  debsums: missing file /etc/dotclear/lighttpd.conf (from dotclear package)


cheers,

Andreas


dotclear_2.5+dfsg-1.log.gz
Description: GNU Zip compressed data

Bug#709747: marked as done (frescobaldi: the sip module implements API v9.0 to v9.2 but the popplerqt4 module requires API v8.1)

[Debian Bug Tracking System]

Your message dated Mon, 27 May 2013 03:53:33 +
with message-id 
and subject line Bug#709747: fixed in python-poppler-qt4 0.16.3-2
has caused the Debian Bug report #709747,
regarding frescobaldi: the sip module implements API v9.0 to v9.2 but the 
popplerqt4 module requires API v8.1
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.)


-- 
709747: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: frescobaldi
Version: 2.0.8+ds1-1
Severity: grave
Justification: renders package unusable

There is a conflict of versions, here's the console output:

Traceback (most recent call last):
  File "/usr/bin/frescobaldi", line 3, in 
import frescobaldi_app.main
  File "/usr/lib/python2.7/dist-packages/frescobaldi_app/main.py", line 162, in 

main()
  File "/usr/lib/python2.7/dist-packages/frescobaldi_app/main.py", line 143, in 
main
win = mainwindow.MainWindow()
  File "/usr/lib/python2.7/dist-packages/frescobaldi_app/mainwindow.py", line 
110, in __init__
self.createMenus()
  File "/usr/lib/python2.7/dist-packages/frescobaldi_app/mainwindow.py", line 
777, in createMenus
menu.createMenus(self)
  File "/usr/lib/python2.7/dist-packages/frescobaldi_app/menu.py", line 67, in 
createMenus
m.addMenu(f(mainwindow))
  File "/usr/lib/python2.7/dist-packages/frescobaldi_app/menu.py", line 87, in 
menu_file
m.addMenu(snippet.menu.TemplateMenu(mainwindow))
  File "/usr/lib/python2.7/dist-packages/frescobaldi_app/snippet/menu.py", line 
140, in __init__
self.addAction(self.tool().actionCollection.templates_manage)
  File "/usr/lib/python2.7/dist-packages/frescobaldi_app/snippet/menu.py", line 
60, in tool
return panelmanager.manager(self.mainwindow()).snippettool
  File "/usr/lib/python2.7/dist-packages/frescobaldi_app/panelmanager.py", line 
34, in manager
return PanelManager.instance(mainwindow)
  File "/usr/lib/python2.7/dist-packages/frescobaldi_app/plugin.py", line 85, 
in instance
result.__init__(obj)
  File "/usr/lib/python2.7/dist-packages/frescobaldi_app/panelmanager.py", line 
49, in __init__
self.loadPanel("musicview.MusicViewPanel")
  File "/usr/lib/python2.7/dist-packages/frescobaldi_app/panelmanager.py", line 
73, in loadPanel
__import__(module_name)
  File 
"/usr/lib/python2.7/dist-packages/frescobaldi_app/musicview/__init__.py", line 
55, in 
from . import documents
  File 
"/usr/lib/python2.7/dist-packages/frescobaldi_app/musicview/documents.py", line 
33, in 
import popplerqt4
RuntimeError: the sip module implements API v9.0 to v9.2 but the popplerqt4 
module requires API v8.1


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

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

Versions of packages frescobaldi depends on:
ii  lilypond2.16.2-2
ii  python  2.7.3-5
ii  python-poppler-qt4  0.16.2-2
ii  python-pypm 0.0.7-7
ii  python-qt4  4.10.1-1
ii  tango-icon-theme0.8.90-5

frescobaldi recommends no packages.

Versions of packages frescobaldi suggests:
pn  hyphen-hyphenation-patterns  
ii  lilypond-doc 2.16.2-2

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: python-poppler-qt4
Source-Version: 0.16.3-2

We believe that the bug you reported is fixed in the latest version of
python-poppler-qt4, 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 709...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ryan Kavanagh  (supplier of updated python-poppler-qt4 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: SHA512

Format: 1.8
Date: Sun, 26 May 2013 12:13:12 -0400
Source: python-poppler-qt4
Binary: python-poppler-qt4
Architecture: source amd64
Version: 0.16.3-2
Distribution: unstable
Urgency: low
Maintainer: Ryan Kavanagh 
Changed-By: Ryan Kavanagh 
Description: 
 python-poppler-qt4 - Python binding to Poppler Qt4 C++ library
Closes: 709747
Changes: 
 python-p

Bug#701513: marked as done (FTBFS: Fails to find python config dir)

[Debian Bug Tracking System]

Your message dated Mon, 27 May 2013 03:55:11 +
with message-id 
and subject line Bug#701513: fixed in vim 2:7.3.923-2
has caused the Debian Bug report #701513,
regarding FTBFS: Fails to find python config dir
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.)


-- 
701513: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701513
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vim
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

$ ./debian/rules build
[snip]  
checking --enable-pythoninterp argument... yes
checking for python2... /usr/bin/python2
checking Python version... 2.7
checking Python is 1.4 or better... yep
checking Python's install prefix... /usr
checking Python's execution prefix... /usr
checking Python's configuration directory... 
can't find it!
configure: error: could not configure python
make: *** [configure-stamp-vim-gtk] Error 1
rm configure-stamp-vim-tiny

Fixed with attached patch.

Thanks,
Gerardo

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

Kernel: Linux 3.7-trunk-amd64 (SMP w/8 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- debian/rules.old	2013-02-22 12:59:51.997473331 -0400
+++ debian/rules	2013-02-22 12:09:55.217366175 -0400
@@ -107,7 +107,7 @@
 ALLINTERPFLAGS:=--enable-luainterp
 ALLINTERPFLAGS+=--disable-mzschemeinterp
 ALLINTERPFLAGS+=--enable-perlinterp
-ALLINTERPFLAGS+=--enable-pythoninterp
+ALLINTERPFLAGS+=--enable-pythoninterp --with-python-config-dir=$(shell python-config --configdir)
 ALLINTERPFLAGS+=--disable-python3interp
 ALLINTERPFLAGS+=--enable-rubyinterp
 ALLINTERPFLAGS+=--enable-tclinterp
--- End Message ---
--- Begin Message ---
Source: vim
Source-Version: 2:7.3.923-2

We believe that the bug you reported is fixed in the latest version of
vim, 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 701...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
James McCoy  (supplier of updated vim 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: Sun, 26 May 2013 22:18:36 -0400
Source: vim
Binary: vim-common vim-gui-common vim-runtime vim-doc vim-tiny vim vim-dbg 
vim-gtk vim-nox vim-athena vim-lesstif vim-gnome
Architecture: source all amd64
Version: 2:7.3.923-2
Distribution: unstable
Urgency: low
Maintainer: Debian Vim Maintainers 
Changed-By: James McCoy 
Description: 
 vim- Vi IMproved - enhanced vi editor
 vim-athena - Vi IMproved - enhanced vi editor - with Athena GUI
 vim-common - Vi IMproved - Common files
 vim-dbg- Vi IMproved - enhanced vi editor (debugging symbols)
 vim-doc- Vi IMproved - HTML documentation
 vim-gnome  - Vi IMproved - enhanced vi editor - with GNOME2 GUI
 vim-gtk- Vi IMproved - enhanced vi editor - with GTK2 GUI
 vim-gui-common - Vi IMproved - Common GUI files
 vim-lesstif - Vi IMproved - enhanced vi editor (transitional package)
 vim-nox- Vi IMproved - enhanced vi editor - with scripting languages suppo
 vim-runtime - Vi IMproved - Runtime files
 vim-tiny   - Vi IMproved - enhanced vi editor - compact version
Closes: 701513
Changes: 
 vim (2:7.3.923-2) unstable; urgency=low
 .
   * Fix FTBFS with M-A Python.  (Closes: #701513)
Checksums-Sha1: 
 f146cb103ccda62405653fee87af4637eaa47574 1982 vim_7.3.923-2.dsc
 092cbaeff9a44d4315d04b292650034c22755a22 188874 vim_7.3.923-2.debian.tar.gz
 e35bc16963a5b2f7687f1f55ed42cf45d2860bca 143232 
vim-gui-common_7.3.923-2_all.deb
 d397040695d14d39aaeed11edcc5f16f1b3d1355 4764854 vim-runtime_7.3.923-2_all.deb
 b1cda8c1f38db6f3b2031ea6b7fddbd049d32dc9 1671316 vim-doc_7.3.923-2_all.deb
 0c87e8b91631a962351aa4e6b1492e393898d144 87700 vim-lesstif_7.3.923-2_all.deb
 1102c194bb5ca1fd17a3ba2992b684bc9148197b 357412 vim-tiny_7.3.923-2_amd64.deb
 cedb177bc041c36296826484ff58529df7733214 1041188 vim-gtk_7.3.923-2_amd64.deb
 145e3089e836f57a38b17066716a44c7531fcb65 1043088 vim-gnome_7.3

Bug#709959: python-gsw: fails to upgrade from testing: unable to install new version of `/usr/lib/python2.7/dist-packages/gsw-3.0.1.egg-info/dependency_links.txt': No such file or directory

[Andreas Beckmann]

Package: python-gsw
Version: 3.0.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails.

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

  Preparing to replace python-gsw 3.0.1-1 (using 
.../python-gsw_3.0.1-2_all.deb) ...
  Unpacking replacement python-gsw ...
  dpkg: error processing /var/cache/apt/archives/python-gsw_3.0.1-2_all.deb 
(--unpack):
   unable to install new version of 
`/usr/lib/python2.7/dist-packages/gsw-3.0.1.egg-info/dependency_links.txt': No 
such file or directory
  Errors were encountered while processing:
   /var/cache/apt/archives/python-gsw_3.0.1-2_all.deb

A fresh installation in sid works fine.


cheers,

Andreas


python-gsw_3.0.1-2.log.gz
Description: GNU Zip compressed data

Bug#709957: icinga-cgi: postinst uses /usr/share/doc content (Policy 12.3)

[Andreas Beckmann]

Package: icinga-cgi
Version: 1.9.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package uses files from
/usr/share/doc in its maintainer scripts which is a violation of
Policy 12.3: "Packages must not require the existence of any files in
/usr/share/doc/ in order to function."
http://www.debian.org/doc/debian-policy/ch-docs.html#s12.3

These files must be moved to /usr/share/$PACKAGE and may be symlinked
from /usr/share/doc/$PACKAGE.

This piuparts tests prevents the installation of (most) files into
/usr/share/doc with 'dpkg --path-exclude=...'.

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

  Selecting previously unselected package icinga-cgi.
  (Reading database ... 8203 files and directories currently installed.)
  Unpacking icinga-cgi (from .../icinga-cgi_1.9.1-1_amd64.deb) ...
  Setting up icinga-cgi (1.9.1-1) ...
  Error: The new file /usr/share/doc/icinga-cgi/examples/apache2.conf does not 
exist!
  dpkg: error processing icinga-cgi (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   icinga-cgi


Cheers,

Andreas


icinga-cgi_1.9.1-1.log.gz
Description: GNU Zip compressed data

Bug#709956: nagvis: postinst uses /usr/share/doc content (Policy 12.3)

[Andreas Beckmann]

Package: nagvis
Version: 1:1.6.6+dfsg.1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package uses files from
/usr/share/doc in its maintainer scripts which is a violation of
Policy 12.3: "Packages must not require the existence of any files in
/usr/share/doc/ in order to function."
http://www.debian.org/doc/debian-policy/ch-docs.html#s12.3

These files must be moved to /usr/share/$PACKAGE and may be symlinked
from /usr/share/doc/$PACKAGE.

This piuparts test prevents the installation of (most) files into
/usr/share/doc with 'dpkg --path-exclude=...'.

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

  Selecting previously unselected package nagvis.
  (Reading database ... 10238 files and directories currently installed.)
  Unpacking nagvis (from .../nagvis_1%3a1.6.6+dfsg.1-3_all.deb) ...
  Setting up nagvis (1:1.6.6+dfsg.1-3) ...
  gzip: /usr/share/doc/nagvis/nagvis.ini.php-sample.gz: No such file or 
directory
  
  Creating config file /etc/nagvis/nagvis.ini.php with new version
  /var/lib/dpkg/info/nagvis.postinst: 49: /var/lib/dpkg/info/nagvis.postinst: 
cannot open /usr/share/doc/nagvis/apache2-nagvis.conf-sample: No such file
  dpkg: error processing nagvis (--configure):
   subprocess installed post-installation script returned error exit status 2
  Errors were encountered while processing:
   nagvis


Cheers,

Andreas


nagvis_1:1.6.6+dfsg.1-3.log.gz
Description: GNU Zip compressed data

Bug#709955: tvtime: postinst uses /usr/share/doc content (Policy 12.3)

[Andreas Beckmann]

Package: tvtime
Version: 1.0.2-10
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package uses files from
/usr/share/doc in its maintainer scripts which is a violation of
Policy 12.3: "Packages must not require the existence of any files in
/usr/share/doc/ in order to function."
http://www.debian.org/doc/debian-policy/ch-docs.html#s12.3

These files must be moved to /usr/share/$PACKAGE and may be symlinked
from /usr/share/doc/$PACKAGE.

This piuparts tests prevents the installation of (most) files into
/usr/share/doc with 'dpkg --path-exclude=...'.

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

  Selecting previously unselected package tvtime.
  (Reading database ... 8539 files and directories currently installed.)
  Unpacking tvtime (from .../tvtime_1.0.2-10_amd64.deb) ...
  Setting up tvtime (1.0.2-10) ...
  cp: cannot stat '/usr/share/doc/tvtime/examples/default.tvtime.xml': No such 
file or directory
  dpkg: error processing tvtime (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   tvtime


Cheers,

Andreas


tvtime_1.0.2-10.log.gz
Description: GNU Zip compressed data

Processed: fixed 709747 in 0.16.3-1

[Debian Bug Tracking System]

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

> fixed 709747 0.16.3-1
Bug #709747 [python-poppler-qt4] frescobaldi: the sip module implements API 
v9.0 to v9.2 but the popplerqt4 module requires API v8.1
Marked as fixed in versions python-poppler-qt4/0.16.3-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
709747: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709747
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

Processed (with 1 errors): Re: Bug#709747: frescobaldi: the sip module implements API v9.0 to v9.2 but the popplerqt4 module requires API v8.1

[Debian Bug Tracking System]

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

> reassign 709747 python-poppler-qt4 0.16.2-2
Bug #709747 [frescobaldi] frescobaldi: the sip module implements API v9.0 to 
v9.2 but the popplerqt4 module requires API v8.1
Bug reassigned from package 'frescobaldi' to 'python-poppler-qt4'.
No longer marked as found in versions frescobaldi/2.0.8+ds1-1.
Ignoring request to alter fixed versions of bug #709747 to the same values 
previously set
Bug #709747 [python-poppler-qt4] frescobaldi: the sip module implements API 
v9.0 to v9.2 but the popplerqt4 module requires API v8.1
Marked as found in versions python-poppler-qt4/0.16.2-2.
> fixed 709747 python-poppler-qt4 0.16.3-1
Unknown command or malformed arguments to command.
> affects 709747 frescobaldi
Bug #709747 [python-poppler-qt4] frescobaldi: the sip module implements API 
v9.0 to v9.2 but the popplerqt4 module requires API v8.1
Added indication that 709747 affects frescobaldi
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
709747: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709747
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#709747: frescobaldi: the sip module implements API v9.0 to v9.2 but the popplerqt4 module requires API v8.1

[Ryan Kavanagh]

reassign 709747 python-poppler-qt4 0.16.2-2
fixed 709747 python-poppler-qt4 0.16.3-1
affects 709747 frescobaldi
thanks

This is a bug in python-poppler-qt4, which will get fixed as soon as the
sip4 transition clears and I upload the version from experimental to
unstable.

Best wishes,
Ryan

-- 
|_)|_/  Ryan Kavanagh   | Debian Developer
| \| \  http://ryanak.ca/   | GPG Key 4A11C97A


signature.asc
Description: Digital signature

Bug#699707: marked as done (bzflag-client: fails to upgrade from 'sid' - trying to overwrite /usr/share/pixmaps/bzflag-48x48.png)

[Debian Bug Tracking System]

Your message dated Mon, 27 May 2013 01:03:11 +
with message-id 
and subject line Bug#699707: fixed in bzflag 2.4.2+ds1-2
has caused the Debian Bug report #699707,
regarding bzflag-client: fails to upgrade from 'sid' - trying to overwrite 
/usr/share/pixmaps/bzflag-48x48.png
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.)


-- 
699707: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699707
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bzflag-client
Version: 2.4.2+ds1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to replace bzflag-client 2.0.16.20100405+nmu1 (using 
.../bzflag-client_2.4.2+ds1-1_amd64.deb) ...
  Unpacking replacement bzflag-client ...
  dpkg: error processing 
/var/cache/apt/archives/bzflag-client_2.4.2+ds1-1_amd64.deb (--unpack):
   trying to overwrite '/usr/share/pixmaps/bzflag-48x48.png', which is also in 
package bzflag-data 2.0.16.20100405+nmu1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/bzflag-client_2.4.2+ds1-1_amd64.deb


cheers,

Andreas


bzflag-client_2.4.2+ds1-1.log.gz
Description: GNU Zip compressed data
--- End Message ---
--- Begin Message ---
Source: bzflag
Source-Version: 2.4.2+ds1-2

We believe that the bug you reported is fixed in the latest version of
bzflag, 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 699...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ryan Kavanagh  (supplier of updated bzflag 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: SHA512

Format: 1.8
Date: Sun, 26 May 2013 18:51:55 -0400
Source: bzflag
Binary: bzflag bzflag-client bzflag-data bzflag-server
Architecture: source all amd64
Version: 2.4.2+ds1-2
Distribution: unstable
Urgency: low
Maintainer: Debian Games Team 
Changed-By: Ryan Kavanagh 
Description: 
 bzflag - 3D first person tank battle game
 bzflag-client - BZFlag client
 bzflag-data - BZFlag data file
 bzflag-server - bzfs - BZFlag game server
Closes: 600307 699707
Changes: 
 bzflag (2.4.2+ds1-2) unstable; urgency=low
 .
   * Uploading to unstable now that wheezy has been released
   * Readd Tim Riker to Uploaders
   * Use proper Breaks/Replaces in bzflag-client against bzflag (Closes: 
#699707)
   * Install data files under /usr/share/games (Closes: #600307)
   * libglew1.5-dev no longer exists, drop it from Build-Depends
   * Bump Standards-Version to 3.9.4
   * Override false positive of hardening-no-fortify-functions in flagStay.so
 and logDetail.so
   * Update years in copyright file
   * Remove debian/changelog.in, originally used by upstream
Checksums-Sha1: 
 93e8eef3e4c068d1de0e872efa49acc53b8e8847 3305 bzflag_2.4.2+ds1-2.dsc
 5d03083b7e9225682433b9b1fdb72bbe10da41f8 16189 bzflag_2.4.2+ds1-2.debian.tar.gz
 3bcef2b0674268c33226bf0ea8c70987e1338a22 53982 bzflag_2.4.2+ds1-2_all.deb
 e305c2efd7aaa7f183e068cbdc1db68a98221a10 1141292 
bzflag-client_2.4.2+ds1-2_amd64.deb
 9867a22be0ac2feb812094c1ae9559a64b09c7e6 10309242 
bzflag-data_2.4.2+ds1-2_all.deb
 c2d26708526b2cd5637a941a28316d39cea86de8 1280902 
bzflag-server_2.4.2+ds1-2_amd64.deb
Checksums-Sha256: 
 a47d9e4b696976b39d1ed6bc9a68848e063e3e1f5ebc7740ce29c26543a92cec 3305 
bzflag_2.4.2+ds1-2.dsc
 ef4cc4fd638e909110245fe897fb03938a0ae8f39cade6522aeeb9d70e0762d7 16189 
bzflag_2.4.2+ds1-2.debian.tar.gz
 7f3e3867bc3c868787483b0f52662d03f00a4d67043f1f4f97f385e3e7520728 53982 
bzflag_2.4.2+ds1-2_all.deb
 8384f100908364e249023aeb534e13546848a854d12668ad9adcab32d9985c48 1141292 
bzflag-client_2.4.2+ds1-2_amd64.deb
 20e42e50fb05da81e9ba6b3237b3b377b9cfb573fcc1a3df69315cc3e77fed42 10309242 
bzflag-data_2.4.2+ds1-2_all.deb
 9ee7aa859f44683732f2e5cce90fabdeca

Bug#709953: marked as done (network-manager: /etc/network/interfaces could not be parsed and gdm3 did not work after uninstall)

[Debian Bug Tracking System]

Your message dated Mon, 27 May 2013 02:47:41 +0200
with message-id <51a2ad2d.1060...@debian.org>
and subject line Re: [Pkg-utopia-maintainers] Bug#709953: network-manager: 
/etc/network/interfaces could not be parsed and gdm3 did not work after 
uninstall
has caused the Debian Bug report #709953,
regarding network-manager: /etc/network/interfaces could not be parsed and gdm3 
did not work after uninstall
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.)


-- 
709953: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709953
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: network-manager
Version: 0.9.4.0-10
Severity: critical
Justification: breaks unrelated software

I uninstalled network-manager from a fresh install of Wheezy
(with Gnome 3) to replace it with wicd.

The uninstall was done after I had taken care of the gnome
meta-package and stopped network-manager.

After this, I couldn't get wlan0 to work with wicd because it
was soft blocked. I didn't try anything else.

On next reboot I noticed that /etc/network/interfaces could
not be read. Then gdm3 froze.

I rebooted in rescued mode and fixed the interfaces file.
This fixed the "could not read /etc/network/interfaces"
message on starting, but gdm3 kept freezing.

gdm3 behaviour was quite erratic as sometimes it would
freeze a few seconds after the cursor had appeared (on a
black screen) sometimes it would display the usual screen.
Moreover, it rebooted after ~15 seconds due to "kernel panic",
but only twice (out of maybe 10-15 tries).

I tried purging and reinstalling gdm3, as well as every package
I thought could be involved. It didn't work.

Since removing network-manager was one of the only things I
had done to the system and since it had apparently cause some
trouble, I eventually reinstalled it. This immediately fixed
the problem.


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

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

Versions of packages network-manager depends on:
ii  adduser3.113+nmu3
ii  dbus   1.6.8-1
ii  dpkg   1.16.10
ii  isc-dhcp-client4.2.2.dfsg.1-5+deb70u3
ii  libc6  2.13-38
ii  libdbus-1-31.6.8-1
ii  libdbus-glib-1-2   0.100.2-1
ii  libgcrypt111.5.0-5
ii  libglib2.0-0   2.33.12+really2.32.4-5
ii  libgnutls262.12.20-6
ii  libgudev-1.0-0 175-7.2
ii  libnl-3-2003.2.7-4
ii  libnl-genl-3-200   3.2.7-4
ii  libnl-route-3-200  3.2.7-4
ii  libnm-glib40.9.4.0-10
ii  libnm-util20.9.4.0-10
ii  libpolkit-gobject-1-0  0.105-3
ii  libuuid1   2.20.1-5.3
ii  lsb-base   4.1+Debian8
ii  udev   175-7.2
ii  wpasupplicant  1.0-3+b2

Versions of packages network-manager recommends:
ii  crda  1.1.2-1
ii  dnsmasq-base  2.62-3+deb7u1
ii  iptables  1.4.14-3.1
ii  modemmanager  0.5.2.0-2
ii  policykit-1   0.105-3
ii  ppp   2.4.5-5.1+b1

Versions of packages network-manager suggests:
ii  avahi-autoipd  0.6.31-2

-- Configuration Files:
/etc/polkit-1/localauthority/10-vendor.d/org.freedesktop.NetworkManager.pkla 
[Errno 13] Permission non accordée: 
u'/etc/polkit-1/localauthority/10-vendor.d/org.freedesktop.NetworkManager.pkla'

-- no debconf information
--- End Message ---
--- Begin Message ---
Am 27.05.2013 02:32, schrieb François Bienvenu:
> Package: network-manager
> Version: 0.9.4.0-10
> Severity: critical
> Justification: breaks unrelated software
> 
> I uninstalled network-manager from a fresh install of Wheezy
> (with Gnome 3) to replace it with wicd.
> 
> The uninstall was done after I had taken care of the gnome
> meta-package and stopped network-manager.
> 
> After this, I couldn't get wlan0 to work with wicd because it
> was soft blocked. I didn't try anything else.
> 
> On next reboot I noticed that /etc/network/interfaces could
> not be read. Then gdm3 froze.
> 
> I rebooted in rescued mode and fixed the interfaces file.
> This fixed the "could not read /etc/network/interfaces"
> message on starting, but gdm3 kept freezing.
> 
> gdm3 behaviour was quite erratic as sometimes it would
> freeze a few seconds after the cursor had appeared (on a
> black screen) sometimes it would display the usual screen.
> Moreover, it rebooted after ~15 seconds due to "kerne

Bug#709953: network-manager: /etc/network/interfaces could not be parsed and gdm3 did not work after uninstall

[François Bienvenu]

Package: network-manager
Version: 0.9.4.0-10
Severity: critical
Justification: breaks unrelated software

I uninstalled network-manager from a fresh install of Wheezy
(with Gnome 3) to replace it with wicd.

The uninstall was done after I had taken care of the gnome
meta-package and stopped network-manager.

After this, I couldn't get wlan0 to work with wicd because it
was soft blocked. I didn't try anything else.

On next reboot I noticed that /etc/network/interfaces could
not be read. Then gdm3 froze.

I rebooted in rescued mode and fixed the interfaces file.
This fixed the "could not read /etc/network/interfaces"
message on starting, but gdm3 kept freezing.

gdm3 behaviour was quite erratic as sometimes it would
freeze a few seconds after the cursor had appeared (on a
black screen) sometimes it would display the usual screen.
Moreover, it rebooted after ~15 seconds due to "kernel panic",
but only twice (out of maybe 10-15 tries).

I tried purging and reinstalling gdm3, as well as every package
I thought could be involved. It didn't work.

Since removing network-manager was one of the only things I
had done to the system and since it had apparently cause some
trouble, I eventually reinstalled it. This immediately fixed
the problem.


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

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

Versions of packages network-manager depends on:
ii  adduser3.113+nmu3
ii  dbus   1.6.8-1
ii  dpkg   1.16.10
ii  isc-dhcp-client4.2.2.dfsg.1-5+deb70u3
ii  libc6  2.13-38
ii  libdbus-1-31.6.8-1
ii  libdbus-glib-1-2   0.100.2-1
ii  libgcrypt111.5.0-5
ii  libglib2.0-0   2.33.12+really2.32.4-5
ii  libgnutls262.12.20-6
ii  libgudev-1.0-0 175-7.2
ii  libnl-3-2003.2.7-4
ii  libnl-genl-3-200   3.2.7-4
ii  libnl-route-3-200  3.2.7-4
ii  libnm-glib40.9.4.0-10
ii  libnm-util20.9.4.0-10
ii  libpolkit-gobject-1-0  0.105-3
ii  libuuid1   2.20.1-5.3
ii  lsb-base   4.1+Debian8
ii  udev   175-7.2
ii  wpasupplicant  1.0-3+b2

Versions of packages network-manager recommends:
ii  crda  1.1.2-1
ii  dnsmasq-base  2.62-3+deb7u1
ii  iptables  1.4.14-3.1
ii  modemmanager  0.5.2.0-2
ii  policykit-1   0.105-3
ii  ppp   2.4.5-5.1+b1

Versions of packages network-manager suggests:
ii  avahi-autoipd  0.6.31-2

-- Configuration Files:
/etc/polkit-1/localauthority/10-vendor.d/org.freedesktop.NetworkManager.pkla 
[Errno 13] Permission non accordée: 
u'/etc/polkit-1/localauthority/10-vendor.d/org.freedesktop.NetworkManager.pkla'

-- 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#709949: libarchive: FTBFS on mips and powerpc: test_read_disk_directory_traversals atime mismatches

[Aaron M. Ucko]

Source: libarchive
Version: 3.1.2-7
Severity: serious
Justification: fails to build from source (but built successfully in the past)

The latest builds of libarchive on mips and powerpc failed with errors
from test_read_disk_directory_traversals, which reported atime mismatches:

115: test_read_disk_directory_traversals
libarchive/test/test_read_disk_directory_traversals.c:1160: File at has atime 
1369518519.0, expected 3808012493914112.1159668743880045816
   Description: Atime should be restored
libarchive/test/test_read_disk_directory_traversals.c:1162: File at/f1 has 
atime 1369518519.0, expected 3807918004633600.1159668743880045816
   Description: Atime should be restored
libarchive/test/test_read_disk_directory_traversals.c:1164: File at/f2 has 
atime 1369518519.0, expected 3807965249273856.1159668743880045816
   Description: Atime should be restored
libarchive/test/test_read_disk_directory_traversals.c:1209: File at has atime 
1369518519.0, expected 3808012493914112.1159668743880045816
   Description: Atime should be restored
libarchive/test/test_read_disk_directory_traversals.c:1263: File at has atime 
1369518519.0, expected 3808012493914112.1159668743880045816
   Description: Atime should be restored

(The absurdly high "expected" values apparently stem from a reporting
error that could stand fixing as well, though I won't bother filing a
separate bug report: assertion_file_time in libarchive/test/main.c
uses %lld for t and nsec even though they have type long, not long
long.)

Could you please take a look?

Thanks!


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

Bug#707346: marked as done (edbrowse: FTBFS: jsdom.c:174:55: error: 'JS_FinalizeStub' undeclared here (not in a function))

[Debian Bug Tracking System]

Your message dated Sun, 26 May 2013 23:33:04 +
with message-id 
and subject line Bug#707346: fixed in edbrowse 3.4.9-1
has caused the Debian Bug report #707346,
regarding edbrowse: FTBFS: jsdom.c:174:55: error: 'JS_FinalizeStub' undeclared 
here (not in a function)
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.)


-- 
707346: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707346
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: edbrowse
Version: 3.4.8-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130509 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> cc -I/usr/include/mozjs -DXP_UNIX -DXP_UNIX -DX86_LINUX -I/usr/include/js  -c 
> -o jsdom.o jsdom.c
> jsdom.c:174:55: error: 'JS_FinalizeStub' undeclared here (not in a function)
> jsdom.c:178:29: error: unknown type name 'uintN'
> jsdom.c:205:26: error: unknown type name 'uintN'
> jsdom.c:216:30: error: unknown type name 'uintN'
> jsdom.c:223:31: error: unknown type name 'uintN'
> jsdom.c:230:30: error: unknown type name 'uintN'
> jsdom.c:237:30: error: unknown type name 'uintN'
> jsdom.c:252:29: error: unknown type name 'uintN'
> jsdom.c:268:27: error: unknown type name 'uintN'
> jsdom.c:278:27: error: unknown type name 'uintN'
> jsdom.c:295:28: error: unknown type name 'uintN'
> jsdom.c:339:29: error: unknown type name 'uintN'
> jsdom.c:391:12: error: unknown type name 'uintN'
> jsdom.c:462:25: error: unknown type name 'uintN'
> jsdom.c:470:26: error: unknown type name 'uintN'
> jsdom.c:478:15: error: 'win_alert' undeclared here (not in a function)
> jsdom.c:479:16: error: 'win_prompt' undeclared here (not in a function)
> jsdom.c:480:17: error: 'win_confirm' undeclared here (not in a function)
> jsdom.c:481:20: error: 'win_sto' undeclared here (not in a function)
> jsdom.c:482:21: error: 'win_intv' undeclared here (not in a function)
> jsdom.c:483:14: error: 'win_open' undeclared here (not in a function)
> jsdom.c:484:15: error: 'win_close' undeclared here (not in a function)
> jsdom.c:485:15: error: 'nullFunction' undeclared here (not in a function)
> jsdom.c:495:5: error: initializer element is not constant
> jsdom.c:495:5: error: (near initialization for 'doc_class.finalize')
> jsdom.c:509:9: error: unknown type name 'uintN'
> jsdom.c:526:27: error: unknown type name 'uintN'
> jsdom.c:565:29: error: unknown type name 'uintN'
> jsdom.c:574:5: error: initializer element is not constant
> jsdom.c:574:5: error: (near initialization for 'doc_methods[0].call.op')
> jsdom.c:575:5: error: initializer element is not constant
> jsdom.c:575:5: error: (near initialization for 'doc_methods[1].call.op')
> jsdom.c:576:5: error: initializer element is not constant
> jsdom.c:576:5: error: (near initialization for 'doc_methods[2].call.op')
> jsdom.c:577:5: error: initializer element is not constant
> jsdom.c:577:5: error: (near initialization for 'doc_methods[3].call.op')
> jsdom.c:578:15: error: 'doc_write' undeclared here (not in a function)
> jsdom.c:578:5: error: initializer element is not constant
> jsdom.c:578:5: error: (near initialization for 'doc_methods[4].call.op')
> jsdom.c:579:17: error: 'doc_writeln' undeclared here (not in a function)
> jsdom.c:579:5: error: initializer element is not constant
> jsdom.c:579:5: error: (near initialization for 'doc_methods[5].call.op')
> jsdom.c:587:5: error: initializer element is not constant
> jsdom.c:587:5: error: (near initialization for 'element_class.finalize')
> jsdom.c:591:5: error: initializer element is not constant
> jsdom.c:591:5: error: (near initialization for 'element_methods[0].call.op')
> jsdom.c:592:5: error: initializer element is not constant
> jsdom.c:592:5: error: (near initialization for 'element_methods[1].call.op')
> jsdom.c:600:5: error: initializer element is not constant
> jsdom.c:600:5: error: (near initialization for 'form_class.finalize')
> jsdom.c:604:29: error: unknown type name 'uintN'
> jsdom.c:613:28: error: unknown type name 'uintN'
> jsdom.c:622:16: error: 'form_submit' undeclared here (not in a function)
> jsdom.c:622:5: error: initializer element is not constant
> jsdom.c:622:5: error: (near initialization for 'form_methods[0].call.op')
> jsdom.c:623:15: error: 'form_reset' undeclared here (not in a function)
> jsdom.c:623:5: error: initializer element is not constant
> jsdom.c:623:5: error: (near initialization for 'form_methods[1].call.op')
> jsdom.c:631:5: error: initializer element is not constant
> jsdom.c:631:5: er

Bug#709947: fsck.ext3 links against library in /usr

[Peter Palfrader]

Package: e2fsprogs
Version: 1.42.5-1.1
Severity: grave

Hi,

on wheezy/ia64:

| weasel@alkman:~$ ldd /sbin/fsck.ext3  | grep -i usr
| libunwind.so.7 => /usr/lib/libunwind.so.7 (0x20080019c000)

This breaks systems such as merulo where /usr is not on the root
filesystem:

} Checking root file system...fsck from util-linux 2.20.1
} fsck.ext3: error while loading shared libraries: libunwind.so.7: cannot open 
shared object file: No such file or directory
} fsck died with exit status 127
} failed (code 127).
} An automatic file system check (fsck) of the root filesystem failed. A manual 
fsck must be performed, then the system restarted. The fsck should be performed 
in maintenance mode with the root filesystem mounted in read-only mode. ... 
failed!
} The root filesystem is currently mounted in read-only mode. A maintenance 
shell will now be started. After performing system maintenance, press CONTROL-D 
to terminate the maintenance shell and restart the system. ... (warning).
} Give root password for maintenance

Cheers,


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

Bug#708806: Can't reproduce

[Emilio Pozuelo Monfort]

Hi Daniel,

On 25/05/13 12:33, Daniel Espinosa wrote:

I'm trying to reproduce this bug, but I can't.

I'm using a Debian 7 virtual box, download libgda from git, checked out
branch  and tag for 5.0.3 version, but build works with --enable-gda-gi
switch. No build problems.

How can I get same environment?


Get the necessary packages (the ones we depend on while building libgda)

apt-get build-dep libgda5


Then build with this flags:

--with-postgres \
--with-mysql\
--with-libsoup  \
--without-bdb   \
--without-oracle\
--without-ldap  \
--without-firebird  \
--without-mdb   \
--without-java  \
--without-gnome-keyring \
--without-ui\
--enable-system-sqlite  \
--enable-introspection  \
--disable-crypto\
--enable-gtk-doc

Or build the Debian way:

apt-get source libgda5
cd libgda5-5.0.3
dpkg-buildpackage -us -uc


Have you try with development version 5.0.4 from git repository? Or you
just can work with tarballs?


I saw the 5.0 branch hadn't had commits for more than a year and thought it was 
abandoned, but I have just seen that there are commits that may fix this. I will 
check this week.


Cheers,
Emilio


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

Bug#666796: marked as done (libapache2-mod-python: sourceful transition towards Apache 2.4)

[Debian Bug Tracking System]

Your message dated Sun, 26 May 2013 22:18:37 +
with message-id 
and subject line Bug#666796: fixed in libapache2-mod-python 3.3.1-10
has caused the Debian Bug report #666796,
regarding libapache2-mod-python: sourceful transition towards Apache 2.4
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.)


-- 
666796: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666796
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libapache2-mod-python
Severity: important
User: debian-apa...@lists.debian.org
Usertags: apache24transition

Dear maintainer,

your package libapache2-mod-python is provding an Apache2 web server module.
We're upgrading Apache to the new upstream version 2.4 [1] (tracked
as transition bug #661958). This requires all modules to be rebuilt
due to ABI changes.  Thus, you need to rebuild and reupload your
Apache2 module package in a version compatible to our new package
available in experimental [2].  Please note it is not enough to
simply rebuild the module - it needs some adaptions in the module
package metadata. We have written packaging guidelines for our
reverse dependencies [3]. Please read it carefully, it should be able
to answer most of your questions. Do also look at dh_apache2
(available through the dh-apache2 package) which can simplify
packaging Apache2 modules.  In short, we want to highlight these
changes you need to be aware of.

* APIs changed for some cases [3]. Chances are your module needs some
  adaptions, please get in touch with upstream or us if you need help
  to port your module to Apache 2.4.

* MPM packages are gone. You cannot depend or conflict with a
  particular MPM anymore. If your module does not work with a
  particular module, make sure to make it abort with an error if
  loaded together with an incompatible MPM. You can use our
  apache2-maintscript-helper [4] to switch to the MPM of your choice
  in your maintainer scripts. 

* Do not build-depend on apache2-threaded-dev or apache2-prefork-dev
  anymore. Just like MPMs are gone, are our MPM -dev packages as
  well. All modules need to simply build-depend on apache2-dev. 

* Do NOT depend on apache2, apache2-common or any other real apache2
  package in your binary module package. Depend on our virtual
  apache2-api-20120211 package only!

* Do NOT call a2enmod/a2dismod in your maintainer scripts. Use our
  apache2-maintscript-helper [3] instead. This is required to get a
  uniform and stateful handling of all Apache2 modules.


You can look at our Apache 2.4 packaging hints [5] for hands-on
tutorials.  Please note: This bug is filed as "important" for now. As
the time goes by we plan make it a release critical severity. In the
consequences your module either needs an update or is going to be
removed from Wheezy. For the time being please tag the bug as pending
as soon as you have a package ready. We strongly recommend that at
least maintainers of complex module packages make an upload to
experimental as well. Of course, uploading simple modules to
experimental is welcome, too.

[1] https://lists.debian.org/debian-devel-announce/2012/03/msg00013.html
[2] 
http://packages.debian.org/search?keywords=apache2&searchon=sourcenames&exact=1&suite=all§ion=all
[3] 
http://anonscm.debian.org/gitweb/?p=pkg-apache/apache2.git;a=blob;f=debian/PACKAGING;hb=next
[4] http://httpd.apache.org/docs/2.4/developer/new_api_2_4.html
[5] http://wiki.debian.org/Apache/PackagingFor24




--- End Message ---
--- Begin Message ---
Source: libapache2-mod-python
Source-Version: 3.3.1-10

We believe that the bug you reported is fixed in the latest version of
libapache2-mod-python, 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 666...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Arthur de Jong  (supplier of updated libapache2-mod-python 
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: Sun, 26 May 2013 23:48:10 +0200
Source: libapache2-mod-python
Binary: libapache2-mod-python libapache2-mod-python-doc
Architecture: source i386 all
Version: 3.3.1-10
Distribution: experimental
Urgency: low
Maintainer: Debian Python Modules Team 

Changed-By

Bug#666796: Apache 2.4 upload date scheduled for May 30

[Arthur de Jong]

On Thu, 2013-05-23 at 13:13 +0200, Arno Töll wrote:
> we are ready to upload Apache2 2.4 to Debian Sid now. This means the
> transition is effectively starting now, and going to break your modules.

I have been working on getting mod_python into shape (somewhat). I have
cleaned up the packaging (switch to dh_python2, dh sequencer, quilt 3.0
source format, etc. I also tried to clean up a little (removing code for
upgrades from ancient versions, etc.).

As a last step I've upgraded to the code to build using Apache 2.4 and
switch the maintainer scripts to use apache2-maintscript-helper
(actually using dh_apache2 resulted in the removal of all maintainer
scripts).

In the patch (20_apach24.patch) I only made the absolute minimal number
of changes to allow mod_python to be buildable and loadable by Apache
(breaking some functionality in the process, see the patch). This is far
from a nice solution. I only did minimal testing (that the module
loads).

I've uploaded the updated package to experimental.

I don't know yet if I'm 100% comfortable with uploading this to
unstable. If someone can do more thorough testing, that would be very
welcome. I don't think I can upload the package to unstable in a
specific time slot.

Packages is in DPMT repository: 
Vcs-Svn: 
svn://anonscm.debian.org/python-modules/packages/libapache2-mod-python/trunk/
Vcs-Browser: 
http://anonscm.debian.org/viewvc/python-modules/packages/libapache2-mod-python/trunk/

In any case, if no-one steps up, removing mod_python from testing to get
Apache 2.4 in is probably the best option. The number of users of
mod_python should be limited (everyone should be using mod_wsgi).

-- 
-- arthur - adej...@debian.org - http://people.debian.org/~adejong --


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

Bug#708807: pspp: diff for NMU version 0.7.9+git20120620-1.2

[Ben Pfaff]

On Sun, May 26, 2013 at 01:36:38PM +0200, Sebastian Ramacher wrote:
> Control: tags -1 + patch pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for pspp (versioned as 0.7.9+git20120620-1.2) and
> uploaded it to DELAYED/1. Please feel free to tell me if I
> should delay it longer.

The NMU is in fact much appreciated.  Thank you!


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

Bug#698104: marked as done (Patch to fix FTBFS on non-long-double ARM and MIPS)

[Debian Bug Tracking System]

Your message dated Sun, 26 May 2013 22:03:54 +
with message-id 
and subject line Bug#698104: fixed in goffice 0.10.2-1
has caused the Debian Bug report #698104,
regarding Patch to fix FTBFS on non-long-double ARM and MIPS
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.)


-- 
698104: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698104
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: goffice
Version: 0.10.0-1
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu raring ubuntu-patch



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

  * long_double_logic.patch: Fix ifdef logic around LONG_DOUBLE in
goffice/math/go-cspline.c to fix FTBFS on ARM and MIPS arches.
  * long_double_logic.patch: Also remove LONG_DOUBLE-only symbols
from docs/reference/goffice-0.10.types and wrap their header
declarations with __GTK_DOC_IGNORE__ magic to fix doc builds.
  * Move some more LONG_DOUBLE-only symbols to symbols.longdouble.

I suspect that what the patch does is reasonably self-explanatory, as
it's just removing two long-double-only types from the doc generation,
inverting a broken ifdef in go-spline.c, and moving some symbols from
one file to another, but if you have any questions, do holler.

This now builds on all arches in Ubuntu just fine (where it previously
failed on armhf), so I suspect it should DTRT on armel, armhf, mips,
and mipsel on Debian, where they all failed with the same errors.

... Adam

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

Kernel: Linux 3.8.0-0-generic (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru goffice-0.10.0/debian/changelog goffice-0.10.0/debian/changelog
diff -Nru goffice-0.10.0/debian/libgoffice-0.10-10.symbols goffice-0.10.0/debian/libgoffice-0.10-10.symbols
--- goffice-0.10.0/debian/libgoffice-0.10-10.symbols	2012-12-19 05:28:58.0 -0700
+++ goffice-0.10.0/debian/libgoffice-0.10-10.symbols	2013-01-13 21:17:54.0 -0700
@@ -57,7 +57,6 @@
  go_ascii_strcase_equal@Base 0.9.0
  go_ascii_strcase_hash@Base 0.9.0
  go_ascii_strtod@Base 0.9.0
- go_ascii_strtold@Base 0.9.0
  go_atk_setup_label@Base 0.9.0
  go_basename_from_uri@Base 0.9.0
  go_bezier_spline_destroy@Base 0.9.0
@@ -159,7 +158,6 @@
  go_complex_real_p@Base 0.9.0
  go_complex_scale_real@Base 0.9.0
  go_complex_sin@Base 0.9.0
- go_complex_sinl@Base 0.9.0
  go_complex_sqrt@Base 0.9.0
  go_complex_sub@Base 0.9.0
  go_complex_tan@Base 0.9.0
@@ -414,7 +412,6 @@
  go_error_system@Base 0.9.0
  go_exponential_regression@Base 0.9.0
  go_exponential_regression_as_log@Base 0.9.0
- go_exponential_regressionl@Base 0.9.0
  go_fake_ceil@Base 0.9.0
  go_fake_floor@Base 0.9.0
  go_fake_round@Base 0.9.0
@@ -737,7 +734,6 @@
  go_matrix3x3_to_euler@Base 0.9.0
  go_matrix3x3_transform@Base 0.9.0
  go_matrix_determinant@Base 0.9.0
- go_matrix_determinantl@Base 0.9.0
  go_matrix_invert@Base 0.9.0
  go_mem_chunk_alloc0@Base 0.9.0
  go_mem_chunk_alloc@Base 0.9.0
@@ -1014,7 +1010,6 @@
  go_string_unref@Base 0.9.0
  go_strsplit_to_slist@Base 0.9.0
  go_strtod@Base 0.9.0
- go_strtold@Base 0.9.0
  go_strunescape@Base 0.9.0
  go_style_apply_theme@Base 0.9.0
  go_style_assign@Base 0.9.0
diff -Nru goffice-0.10.0/debian/libgoffice-0.10-10.symbols.longdouble goffice-0.10.0/debian/libgoffice-0.10-10.symbols.longdouble
--- goffice-0.10.0/debian/libgoffice-0.10-10.symbols.longdouble	2012-10-28 10:52:39.0 -0600
+++ goffice-0.10.0/debian/libgoffice-0.10-10.symbols.longdouble	2013-01-13 21:18:16.0 -0700
@@ -8,6 +8,7 @@
  go_accumulator_startl@Base 0.9.0
  go_accumulator_valuel@Base 0.9.0
  go_add_epsilonl@Base 0.9.0
+ go_ascii_strtold@Base 0.9.0
  go_complex_addl@Base 0.9.0
  go_complex_angle_pil@Base 0.9.0
  go_complex_anglel@Base 0.9.0
@@ -27,6 +28,7 @@
  go_complex_real_pl@Base 0.9.0
  go_complex_reall@Base 0.9.0
  go_complex_scale_reall@Base 0.9.0
+ go_complex_sinl@Base 0.9.0
  go_complex_sqrtl@Base 0.9.0
  go_complex_subl@Base 0.9.0
  go_complex_tanl@Base 0.9.0
@@ -53,6 +55,7 @@
  go_dnorml@Base 0.9.0
  go_dweibulll@Base 0.9.0
  go_exponential_regression_as_logl@Base 0.9.0
+ go_exponential_regressionl@Base 0.9.0
  go_fake_ceill@Base 0.9.0
  go_fake_floorl@Base 0.9.0
  go_fake_roundl@Base 0.9.0
@@ -66,6 +69,7 @@

Bug#708366: marked as done (pike7.8: FTBFS due to conflicting REG_* definitions)

[Debian Bug Tracking System]

Your message dated Sun, 26 May 2013 21:50:25 +
with message-id 
and subject line Bug#708366: fixed in pike7.8 7.8.700-4
has caused the Debian Bug report #708366,
regarding pike7.8: FTBFS due to conflicting REG_* definitions
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.)


-- 
708366: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pike7.8
Version: 7.8.700-2
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu saucy

pike7.8 fails to build in unstable as follows:

Compiling pikecode.c
In file included from /«PKGBUILDDIR»/src/pikecode.c:25:0:
/«PKGBUILDDIR»/src/code/ia32.c:22:16: error: redeclaration of enumerator 
'REG_EAX'
In file included from /usr/include/signal.h:360:0,
 from /usr/include/i386-linux-gnu/sys/param.h:28,
 from /«PKGBUILDDIR»/src/pike_macros.h:14,
 from /«PKGBUILDDIR»/src/program.h:12,
 from /«PKGBUILDDIR»/src/pikecode.c:15:
/usr/include/i386-linux-gnu/sys/ucontext.h:180:3: note: previous definition of 
'REG_EAX' was here
In file included from /«PKGBUILDDIR»/src/pikecode.c:25:0:
/«PKGBUILDDIR»/src/code/ia32.c:22:29: error: redeclaration of enumerator 
'REG_EBX'
In file included from /usr/include/signal.h:360:0,
 from /usr/include/i386-linux-gnu/sys/param.h:28,
 from /«PKGBUILDDIR»/src/pike_macros.h:14,
 from /«PKGBUILDDIR»/src/program.h:12,
 from /«PKGBUILDDIR»/src/pikecode.c:15:
/usr/include/i386-linux-gnu/sys/ucontext.h:174:3: note: previous definition of 
'REG_EBX' was here
In file included from /«PKGBUILDDIR»/src/pikecode.c:25:0:
/«PKGBUILDDIR»/src/code/ia32.c:22:42: error: redeclaration of enumerator 
'REG_ECX'
In file included from /usr/include/signal.h:360:0,
 from /usr/include/i386-linux-gnu/sys/param.h:28,
 from /«PKGBUILDDIR»/src/pike_macros.h:14,
 from /«PKGBUILDDIR»/src/program.h:12,
 from /«PKGBUILDDIR»/src/pikecode.c:15:
/usr/include/i386-linux-gnu/sys/ucontext.h:178:3: note: previous definition of 
'REG_ECX' was here
In file included from /«PKGBUILDDIR»/src/pikecode.c:25:0:
/«PKGBUILDDIR»/src/code/ia32.c:22:55: error: redeclaration of enumerator 
'REG_EDX'
In file included from /usr/include/signal.h:360:0,
 from /usr/include/i386-linux-gnu/sys/param.h:28,
 from /«PKGBUILDDIR»/src/pike_macros.h:14,
 from /«PKGBUILDDIR»/src/program.h:12,
 from /«PKGBUILDDIR»/src/pikecode.c:15:
/usr/include/i386-linux-gnu/sys/ucontext.h:176:3: note: previous definition of 
'REG_EDX' was here
WARNING: Compiler failure! Trying without optimization!
In file included from /«PKGBUILDDIR»/src/pikecode.c:25:0:
/«PKGBUILDDIR»/src/code/ia32.c:22:16: error: redeclaration of enumerator 
'REG_EAX'
In file included from /usr/include/signal.h:360:0,
 from /usr/include/i386-linux-gnu/sys/param.h:28,
 from /«PKGBUILDDIR»/src/pike_macros.h:14,
 from /«PKGBUILDDIR»/src/program.h:12,
 from /«PKGBUILDDIR»/src/pikecode.c:15:
/usr/include/i386-linux-gnu/sys/ucontext.h:180:3: note: previous definition of 
'REG_EAX' was here
In file included from /«PKGBUILDDIR»/src/pikecode.c:25:0:
/«PKGBUILDDIR»/src/code/ia32.c:22:29: error: redeclaration of enumerator 
'REG_EBX'
In file included from /usr/include/signal.h:360:0,
 from /usr/include/i386-linux-gnu/sys/param.h:28,
 from /«PKGBUILDDIR»/src/pike_macros.h:14,
 from /«PKGBUILDDIR»/src/program.h:12,
 from /«PKGBUILDDIR»/src/pikecode.c:15:
/usr/include/i386-linux-gnu/sys/ucontext.h:174:3: note: previous definition of 
'REG_EBX' was here
In file included from /«PKGBUILDDIR»/src/pikecode.c:25:0:
/«PKGBUILDDIR»/src/code/ia32.c:22:42: error: redeclaration of enumerator 
'REG_ECX'
In file included from /usr/include/signal.h:360:0,
 from /usr/include/i386-linux-gnu/sys/param.h:28,
 from /«PKGBUILDDIR»/src/pike_macros.h:14,
 from /«PKGBUILDDIR»/src/program.h:12,
 from /«PKGBUILDDIR»/src/pikecode.c:15:
/usr/include/i386-linux-gnu/sys/ucontext.h:178:3: note: previous definition of 
'REG_ECX' was here
In file included from /«PKGBUILDDIR»/src/pikecode.c:25:0:
/«PKGBUILDDIR»/src/code/ia32.c:22:55: error: redeclaration of enumerator 
'REG_EDX'
In file included from /usr/include/signal.h:360:0,
 from /usr/include/i386-linux-g

Processed: your mail

[Debian Bug Tracking System]

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

> tag 666796 + pending
Bug #666796 [libapache2-mod-python] libapache2-mod-python: sourceful transition 
towards Apache 2.4
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
666796: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666796
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

Processed: limit source to val-and-rick, tagging 617194, tagging 707274

[Debian Bug Tracking System]

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

> #val-and-rick (0.1a.dfsg1-4) UNRELEASED; urgency=low
> #
> #  * Ported to D language version 2 (closes: #707274)
> #  * Added English translation of the readme file (closes: #617194)
> #- Translated by Christopher Cramer, thanks!
> #
> limit source val-and-rick
Limiting to bugs with field 'source' containing at least one of 'val-and-rick'
Limit currently set to 'source':'val-and-rick'

> tags 617194 + pending
Bug #617194 [val-and-rick] English translation of readme
Added tag(s) pending.
> tags 707274 + pending
Bug #707274 [val-and-rick] val-and-rick: convert package to D v2, or remove the 
package from unstable
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
617194: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617194
707274: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707274
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

Processed: limit source to tumiki-fighters, tagging 707273

[Debian Bug Tracking System]

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

> #tumiki-fighters (0.2.dfsg1-6) UNRELEASED; urgency=low
> #
> #  * Ported to D language version 2 (closes: #707273)
> #
> limit source tumiki-fighters
Limiting to bugs with field 'source' containing at least one of 
'tumiki-fighters'
Limit currently set to 'source':'tumiki-fighters'

> tags 707273 + pending
Bug #707273 [tumiki-fighters] tumiki-fighters: convert package to D v2, or 
remove the package from unstable
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
707273: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707273
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

Processed: limit source to torus-trooper, tagging 707272, tagging 602808

[Debian Bug Tracking System]

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

> #torus-trooper (0.22.dfsg1-9) UNRELEASED; urgency=low
> #
> #  * Ported to D language version 2 (closes: #707272)
> #- Dropped the torus-trooper-pure variant
> #  * Keep level display visible in title screen (closes: #602808)
> #- Thanks to Thomas Preud'homme
> #
> limit source torus-trooper
Limiting to bugs with field 'source' containing at least one of 'torus-trooper'
Limit currently set to 'source':'torus-trooper'

> tags 707272 + pending
Bug #707272 [torus-trooper] torus-trooper: convert package to D v2, or remove 
the package from unstable
Added tag(s) pending.
> tags 602808 + pending
Bug #602808 [torus-trooper] torus-trooper: Level display disappears at screen 
bottom
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
602808: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602808
707272: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707272
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

Processed: limit source to titanion, tagging 707271

[Debian Bug Tracking System]

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

> #titanion (0.3.dfsg1-5) UNRELEASED; urgency=low
> #
> #  * Ported to D language version 2 (closes: #707271)
> #
> limit source titanion
Limiting to bugs with field 'source' containing at least one of 'titanion'
Limit currently set to 'source':'titanion'

> tags 707271 + pending
Bug #707271 [titanion] titanion: convert package to D v2, or remove the package 
from unstable
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
707271: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707271
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

Processed: limit source to tatan, tagging 707270

[Debian Bug Tracking System]

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

> #tatan (1.0.dfsg1-4) UNRELEASED; urgency=low
> #
> #  * Ported to D language version 2 (closes: #707270)
> #
> limit source tatan
Limiting to bugs with field 'source' containing at least one of 'tatan'
Limit currently set to 'source':'tatan'

> tags 707270 + pending
Bug #707270 [tatan] tatan: convert package to D v2, or remove the package from 
unstable
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
707270: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707270
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

Processed: limit source to projectl, tagging 680279, tagging 707269

[Debian Bug Tracking System]

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

> #projectl (1.001.dfsg1-5) UNRELEASED; urgency=low
> #
> #  * Ported to D language version 2. Restarted from scratch, dropping the
> #dubious old 'fixes.patch' (closes: #707269, #680279)
> #
> limit source projectl
Limiting to bugs with field 'source' containing at least one of 'projectl'
Limit currently set to 'source':'projectl'

> tags 680279 + pending
Bug #680279 [projectl] projectl: does not display seven-segment alphabet
Added tag(s) pending.
> tags 707269 + pending
Bug #707269 [projectl] projectl: convert package to D v2, or remove the package 
from unstable
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
680279: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680279
707269: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707269
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

Processed: limit source to parsec47, tagging 707267

[Debian Bug Tracking System]

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

> #parsec47 (0.2.dfsg1-5) UNRELEASED; urgency=low
> #
> #  * Ported to D language version 2 (closes: #707267)
> #
> limit source parsec47
Limiting to bugs with field 'source' containing at least one of 'parsec47'
Limit currently set to 'source':'parsec47'

> tags 707267 + pending
Bug #707267 [parsec47] parsec47: convert package to D v2, or remove the package 
from unstable
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
707267: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707267
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

Processed: limit source to mu-cade, tagging 707266

[Debian Bug Tracking System]

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

> #mu-cade (0.11.dfsg1-7) UNRELEASED; urgency=low
> #
> #  * Ported to D language version 2 (closes: #707266)
> #
> limit source mu-cade
Limiting to bugs with field 'source' containing at least one of 'mu-cade'
Limit currently set to 'source':'mu-cade'

> tags 707266 + pending
Bug #707266 [mu-cade] mu-cade: convert package to D v2, or remove the package 
from unstable
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
707266: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707266
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

Processed: limit source to ii-esu, tagging 707265

[Debian Bug Tracking System]

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

> #ii-esu (1.0a.dfsg1-5) unstable; urgency=low
> #
> #  * Add patch to build with D v2. (Closes: #707265)
> #- Remove -d (deprecated) flag.
> #
> limit source ii-esu
Limiting to bugs with field 'source' containing at least one of 'ii-esu'
Limit currently set to 'source':'ii-esu'

> tags 707265 + pending
Bug #707265 [ii-esu] ii-esu: convert package to D v2, or remove the package 
from unstable
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
707265: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707265
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

Processed: limit source to gunroar, tagging 707264

[Debian Bug Tracking System]

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

> #gunroar (0.15.dfsg1-6) UNRELEASED; urgency=low
> #
> #  * Ported to D language version 2 (closes: #707264)
> #- No longer includes patch for 'Gunroar hot iron' variant
> #
> limit source gunroar
Limiting to bugs with field 'source' containing at least one of 'gunroar'
Limit currently set to 'source':'gunroar'

> tags 707264 + pending
Bug #707264 [gunroar] gunroar: convert package to D v2, or remove the package 
from unstable
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
707264: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707264
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

Processed: limit source to a7xpg, tagging 707263

[Debian Bug Tracking System]

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

> #a7xpg (0.11.dfsg1-8) unstable; urgency=low
> #
> #  * Patch to build with gdc v2. (Closes: #707263)
> #
> limit source a7xpg
Limiting to bugs with field 'source' containing at least one of 'a7xpg'
Limit currently set to 'source':'a7xpg'

> tags 707263 + pending
Bug #707263 [a7xpg] a7xpg: convert package to D v2, or remove the package from 
unstable
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
707263: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707263
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#707862: referencer moved to launchpad

[Denis Laxalde]

Emilio Pozuelo Monfort wrote:

However, referencer now build depends on gtkmm-utils
 which is not in Debian. There
has been an RFP (#492480) and it's available Ubuntu. What's the way
forward in such situations?


This probably belongs in pkg-gnome, I'll look at it.


I've had a quick look and the project seems pretty dead, so I won't
include it
in pkg-gnome. You can of course package and maintain it yourself.


Scratch that, there's no reason to add more cruft to Debian, we already
have too much.


I agree.


What does referencer need gtkmm-utils for? If it's just one utility
function, it could just copy it...


I've asked upstream: https://bugs.launchpad.net/referencer/+bug/1184423.

Cheers,
Denis


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

Processed: tagging 666857

[Debian Bug Tracking System]

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

> tags 666857 - pending
Bug #666857 [libapache-mod-layout] libapache-mod-layout: sourceful transition 
towards Apache 2.4
Removed tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
666857: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666857
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#709934: libchewing: FTBFS on sparc

[Aron Xu]

Package: src:libchewing
Version: 0.3.4-1
Severity: serious

libchewing currently FTBFS on sparc due to test case failures, and
this has been preventing it from migrating to testing.

Build log: 
https://buildd.debian.org/status/fetch.php?pkg=libchewing&arch=sparc&ver=0.3.4-1&stamp=1360996940

Tail of log for libchewing on sparc:

ok 364 check function returned `1' shall be `1'
ok 365 string function returned `�' shall be `�'
PASS: test-special-symbol
ok 1 ueStrLen
ok 2 ueStrLen
ok 3 ueStrNCpy
ok 4 ueStrSeek
ok 5 ueStrSeek
PASS: test-utf8
===
4 of 13 tests failed
Please report to chewing-de...@googlegroups.com
===
make[3]: Leaving directory
`/build/buildd-libchewing_0.3.4-1-sparc-HSEujM/libchewing-0.3.4/test'
make[2]: Leaving directory
`/build/buildd-libchewing_0.3.4-1-sparc-HSEujM/libchewing-0.3.4/test'


-- 
Regards,
Aron Xu


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

Bug#709499: Documentation is non free

[Lorenzo Bettini]

Oh, this modification is already in the git repository

On 05/24/2013 05:36 PM, Bastien ROUCARIÈS wrote:
> Le vendredi 24 mai 2013 10:56:22, Lorenzo Bettini a écrit :
>> On 05/23/2013 06:07 PM, Bastien ROUCARIÈS wrote:
>>> Package: source-highlight
>>> Severity: serious
>>> user: debian...@lists.debian.org
>>> usertags: gfdl-invariant
>>> severity: serious
>>>
>>> The documentation of your package is non free under gfdl with invariants
>>> sections.
>>>
>>> Please ask upstream about relicense, remove or repackage
>>
>> Hi
>>
>> what should be done to fix this?
>> I'm the author of source-highlight
> 
> You have set documentation license to:
>  Permission is granted to copy, distribute and/or modify this
>  document under the terms of the GNU Free Documentation License,
>  Version 1.1 or any later version published by the Free Software
>  Foundation; with no Invariant Sections, with the Front-Cover Texts
>  being "A GNU Manual," and with the Back-Cover Texts as in (a)
>  below.  A copy of the license is included in the section entitled
>  "GNU Free Documentation License."
> 
>  (a) The FSF's Back-Cover Text is: "You have freedom to copy and
>  modify this GNU Manual, like GNU software.  Copies published by
>  the Free Software Foundation raise funds for GNU development."
> 
> If you set the license to:
> Permission is granted to copy, distribute and/or modify this document
> under the terms of the GNU Free Documentation License, Version 1.1
> or any later version published by the Free Software Foundation;
> with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
> A copy of the license is included in the section entitled "GNU
> Free Documentation License".
> 
> It is ok for us
> 
> Bastien
>
>>
>> Lorenzo
> 


-- 
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it


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

Bug#701414: recutils: diff for NMU version 1.5-1.1

[Sebastian Ramacher]

Control: tags -1 + patch pending
thanks

Dear maintainer,

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

Regards
-- 
Sebastian Ramacher
diff -Nru recutils-1.5/debian/changelog recutils-1.5/debian/changelog
--- recutils-1.5/debian/changelog	2012-01-21 23:10:45.0 +0100
+++ recutils-1.5/debian/changelog	2013-05-26 22:59:46.0 +0200
@@ -1,3 +1,11 @@
+recutils (1.5-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * debian/patches/eglibc2.17.patch: Fix FTBFS with eglibc 2.17. (Closes:
+#701414)
+
+ -- Sebastian Ramacher   Sun, 26 May 2013 22:59:45 +0200
+
 recutils (1.5-1) unstable; urgency=low
 
   * New upstream release
diff -Nru recutils-1.5/debian/patches/eglibc2.17.patch recutils-1.5/debian/patches/eglibc2.17.patch
--- recutils-1.5/debian/patches/eglibc2.17.patch	1970-01-01 01:00:00.0 +0100
+++ recutils-1.5/debian/patches/eglibc2.17.patch	2013-05-26 22:59:42.0 +0200
@@ -0,0 +1,23 @@
+Description: Fix FTBFS with eglibc 2.17
+Author: Sebastian Ramacher 
+Bug-Debian: http://bugs.debian.org/701414
+Last-Update: 2013-05-26
+
+--- recutils-1.5.orig/lib/stdio.in.h
 recutils-1.5/lib/stdio.in.h
+@@ -711,11 +711,15 @@ _GL_CXXALIAS_RPL (gets, char *, (char *s
+ _GL_CXXALIAS_SYS (gets, char *, (char *s));
+ #  undef gets
+ # endif
++# if defined gets
+ _GL_CXXALIASWARN (gets);
++# endif
+ /* It is very rare that the developer ever has full control of stdin,
+so any use of gets warrants an unconditional warning.  Assume it is
+always declared, since it is required by C89.  */
++# if defined gets
+ _GL_WARN_ON_USE (gets, "gets is a security hole - use fgets instead");
++# endif
+ #endif
+ 
+ 
diff -Nru recutils-1.5/debian/patches/series recutils-1.5/debian/patches/series
--- recutils-1.5/debian/patches/series	2012-01-21 23:28:32.0 +0100
+++ recutils-1.5/debian/patches/series	2013-05-26 22:59:14.0 +0200
@@ -1 +1,2 @@
 mdbtools-0.7-fix
+eglibc2.17.patch


signature.asc
Description: Digital signature

Processed: recutils: diff for NMU version 1.5-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch pending
Bug #701414 [src:recutils] recutils: ftbfs with eglibc-2.17
Added tag(s) pending and patch.

-- 
701414: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701414
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#683502: jedit: Refreshed patch

[James Page]

Package: jedit
Version: 5.0.0+dfsg-1
Followup-For: Bug #683502
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu saucy ubuntu-patch

Dear Maintainer,

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

  * Merge from Debian unstable.  Remaining changes:
- d/control: Switch to using default-jdk for build, don't use BDI's.

Thanks for considering the patch.


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

Kernel: Linux 3.8.0-22-generic (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
diff -Nru jedit-5.0.0+dfsg/debian/changelog jedit-5.0.0+dfsg/debian/changelog
diff -Nru jedit-5.0.0+dfsg/debian/control jedit-5.0.0+dfsg/debian/control
--- jedit-5.0.0+dfsg/debian/control	2013-03-24 20:34:07.0 +
+++ jedit-5.0.0+dfsg/debian/control	2013-05-26 22:04:12.0 +0100
@@ -9,6 +9,7 @@
bsh,
bsh-src (>= 2.0b4-11),
debhelper (>= 7.0.50~),
+   default-jdk,
docbook-xml,
docbook-xsl,
docbook-xsl-saxon,
@@ -20,7 +21,6 @@
libjsr305-java,
quilt (>= 0.46-7~),
xsltproc
-Build-Depends-Indep: openjdk-6-jdk | sun-java6-jdk
 Standards-Version: 3.9.3
 DM-Upload-Allowed: yes
 Vcs-Git: git://git.debian.org/pkg-java/jedit.git

Bug#701405: mtbl: diff for NMU version 0.2-1.1

[Sebastian Ramacher]

Control: tags -1 + patch pending

Dear maintainer,

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

Regards.
-- 
Sebastian Ramacher
diff -Nru mtbl-0.2/debian/changelog mtbl-0.2/debian/changelog
--- mtbl-0.2/debian/changelog	2012-05-30 04:37:01.0 +0200
+++ mtbl-0.2/debian/changelog	2013-05-26 22:52:56.0 +0200
@@ -1,3 +1,11 @@
+mtbl (0.2-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * debian/patches/eglibc2.17.patch: Rename timespec_get to prevent name
+clashes with timespec_get provided by eglibc 2.17 (Closes: #701405)
+
+ -- Sebastian Ramacher   Sun, 26 May 2013 22:52:55 +0200
+
 mtbl (0.2-1) unstable; urgency=low
 
   * New upstream release.
diff -Nru mtbl-0.2/debian/patches/eglibc2.17.patch mtbl-0.2/debian/patches/eglibc2.17.patch
--- mtbl-0.2/debian/patches/eglibc2.17.patch	1970-01-01 01:00:00.0 +0100
+++ mtbl-0.2/debian/patches/eglibc2.17.patch	2013-05-26 22:52:53.0 +0200
@@ -0,0 +1,35 @@
+Description: Rename timespec_get
+ Prevent name clashes with timespec_get provided by eglibc 2.17.
+Author: Sebastian Ramacher 
+Bug-Debian: http://bugs.debian.org/701405
+Last-Update: 2013-05-26
+
+--- a/src/mtbl_merge.c
 b/src/mtbl_merge.c
+@@ -64,7 +64,7 @@
+ }
+ 
+ static void
+-timespec_get(struct timespec *now) {
++mtbl_timespec_get(struct timespec *now) {
+ 	struct timeval tv;
+ 	(void) gettimeofday(&tv, NULL);
+ 	now->tv_sec = tv.tv_sec;
+@@ -92,7 +92,7 @@
+ 	struct timespec dur;
+ 	double t_dur;
+ 
+-	timespec_get(&dur);
++	mtbl_timespec_get(&dur);
+ 	timespec_sub(&start_time, &dur);
+ 	t_dur = timespec_to_double(&dur);
+ 
+@@ -268,7 +268,7 @@
+ 	}
+ 
+ 	/* do merge */
+-	timespec_get(&start_time);
++	mtbl_timespec_get(&start_time);
+ 	merge();
+ 
+ 	/* cleanup readers */
diff -Nru mtbl-0.2/debian/patches/series mtbl-0.2/debian/patches/series
--- mtbl-0.2/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ mtbl-0.2/debian/patches/series	2013-05-26 22:49:52.0 +0200
@@ -0,0 +1 @@
+eglibc2.17.patch


signature.asc
Description: Digital signature

Processed: mtbl: diff for NMU version 0.2-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch pending
Bug #701405 [src:mtbl] mtbl: ftbfs with eglibc-2.17
Added tag(s) pending and patch.

-- 
701405: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701405
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

Processed: Re: Bug#709923: lesstif-bin and uil: error when trying to install together

[Debian Bug Tracking System]

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

> reassign 709923 uil
Bug #709923 [uil,lesstif-bin] lesstif-bin and uil: error when trying to install 
together
Bug reassigned from package 'uil,lesstif-bin' to 'uil'.
Ignoring request to alter found versions of bug #709923 to the same values 
previously set
Ignoring request to alter fixed versions of bug #709923 to the same values 
previously set
> affects 709923 lesstif-bin
Bug #709923 [uil] lesstif-bin and uil: error when trying to install together
Added indication that 709923 affects lesstif-bin
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
709923: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709923
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#709923: lesstif-bin and uil: error when trying to install together

[Paul Gevers]

reassign 709923 uil
affects 709923 lesstif-bin
thanks

> This bug has been filed against both packages. If you, the
> maintainers of the two packages in question, have agreed on which of
> the packages will resolve the problem please reassign the bug to that
> package. You may then also register in the BTS that the other package
> is affected by the bug.

As uploader of both source packages, I suggest we fix this in motif. We
want to get rid of lesstif2, and we want a solution that is valid even
after removal of lesstif2 from Debian so that upgrades and such go well.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#707862: referencer moved to launchpad

[Emilio Pozuelo Monfort]

On 26/05/13 21:51, Emilio Pozuelo Monfort wrote:

On 26/05/13 21:46, Emilio Pozuelo Monfort wrote:

On 26/05/13 21:30, Denis Laxalde wrote:

Hi,

Emilio Pozuelo Monfort wrote:

Turns out referencer moved to launchpad.net and is still maintained.
There's even a new upstream release that ports referencer away from
gnome-vfs, gnomeuimm and gnomemm.

It'd be great to get that uploaded so we can remove those three libs
for which referencer is the only remaining user.


I can help packaging this release, unless Michael plans to work on this.

However, referencer now build depends on gtkmm-utils
 which is not in Debian. There
has been an RFP (#492480) and it's available Ubuntu. What's the way
forward in such situations?


This probably belongs in pkg-gnome, I'll look at it.


I've had a quick look and the project seems pretty dead, so I won't include it
in pkg-gnome. You can of course package and maintain it yourself.


Scratch that, there's no reason to add more cruft to Debian, we already have too 
much.


What does referencer need gtkmm-utils for? If it's just one utility function, it 
could just copy it...


FWIW gtkmm-utils has no rdeps in Ubuntu and it's removal has been requested, 
see: https://bugs.launchpad.net/ubuntu/+source/gtkmm-utils/+bug/1184413


Cheers,
Emilio


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

Bug#709906: texi2html: Missing dependency on libtext-unidecode-perl

[Ralf Treinen]

On Sun, May 26, 2013 at 12:18:46PM -0700, Daniel Schepler wrote:
> On Sunday, May 26, 2013 08:58:07 PM Ralf Treinen wrote:
> > On Sun, May 26, 2013 at 08:47:38AM -0700, Daniel Schepler wrote:
> > > Package: texi2html
> > > Version: 1.82+dfsg1-2
> > > Severity: serious
> > > 
> > > >From my pbuilder log of diffutils:
> > > ...
> > > 
> > >dh_install
> > >debian/rules override_dh_installdocs
> > > 
> > > make[1]: Entering directory `/tmp/buildd/diffutils-3.2'
> > > cd doc && texi2html -split_chapter diffutils.texi
> > > Can't locate Text/Unidecode.pm in @INC (@INC contains: /etc/perl
> > > /usr/local/lib/perl/5.14.2 /usr/local/share/perl/5.14.2 /usr/lib/perl5
> > > /usr/share/perl5 /usr/lib/perl/5.14 /usr/share/perl/5.14
> > > /usr/local/lib/site_perl .) at /usr/bin/texi2html line 12577. make[1]:
> > > *** [override_dh_installdocs] Error 2
> > > make[1]: Leaving directory `/tmp/buildd/diffutils-3.2'
> > > make: *** [binary] Error 2
> > > dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit
> > > status 2
> > I just tried to compile texi2html 1.82+dfsg1-2 with pbuilder, and it
> > compiles just fine on my machine (amd64/sid).
> > 
> > Can you make the complete log of your failed build available?
> 
> texi2html builds fine for me, too.  The bug I'm reporting is missing binary 
> dependencies in the resulting package, which is causing build failures in 
> other packages (also confirmed in a clean pbuilder chroot using the official 
> binary packages).  The example above is from the failure of diffutils.

Thanks for the explanation. -Ralf.


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

Processed: tagging 709906

[Debian Bug Tracking System]

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

> tags 709906 - unreproducible
Bug #709906 [texi2html] texi2html: Missing dependency on libtext-unidecode-perl
Removed tag(s) unreproducible.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
709906: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709906
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#707862: referencer moved to launchpad

[Emilio Pozuelo Monfort]

On 26/05/13 21:46, Emilio Pozuelo Monfort wrote:

On 26/05/13 21:30, Denis Laxalde wrote:

Hi,

Emilio Pozuelo Monfort wrote:

Turns out referencer moved to launchpad.net and is still maintained.
There's even a new upstream release that ports referencer away from
gnome-vfs, gnomeuimm and gnomemm.

It'd be great to get that uploaded so we can remove those three libs
for which referencer is the only remaining user.


I can help packaging this release, unless Michael plans to work on this.

However, referencer now build depends on gtkmm-utils
 which is not in Debian. There
has been an RFP (#492480) and it's available Ubuntu. What's the way
forward in such situations?


This probably belongs in pkg-gnome, I'll look at it.


I've had a quick look and the project seems pretty dead, so I won't include it 
in pkg-gnome. You can of course package and maintain it yourself.


Emilio


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

Bug#707862: referencer moved to launchpad

[Emilio Pozuelo Monfort]

On 26/05/13 21:30, Denis Laxalde wrote:

Hi,

Emilio Pozuelo Monfort wrote:

Turns out referencer moved to launchpad.net and is still maintained.
There's even a new upstream release that ports referencer away from
gnome-vfs, gnomeuimm and gnomemm.

It'd be great to get that uploaded so we can remove those three libs
for which referencer is the only remaining user.


I can help packaging this release, unless Michael plans to work on this.

However, referencer now build depends on gtkmm-utils
 which is not in Debian. There
has been an RFP (#492480) and it's available Ubuntu. What's the way
forward in such situations?


This probably belongs in pkg-gnome, I'll look at it.

Emilio


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

Bug#707862: referencer moved to launchpad

[Denis Laxalde]

Hi,

Emilio Pozuelo Monfort wrote:
> Turns out referencer moved to launchpad.net and is still maintained.
> There's even a new upstream release that ports referencer away from
> gnome-vfs, gnomeuimm and gnomemm.
> 
> It'd be great to get that uploaded so we can remove those three libs
> for which referencer is the only remaining user.

I can help packaging this release, unless Michael plans to work on this.

However, referencer now build depends on gtkmm-utils
 which is not in Debian. There
has been an RFP (#492480) and it's available Ubuntu. What's the way
forward in such situations?

Regards.

-- 
Denis Laxalde


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

Bug#701413: marked as done (proxychains: ftbfs with eglibc-2.17)

[Debian Bug Tracking System]

Your message dated Sun, 26 May 2013 19:19:06 +
with message-id 
and subject line Bug#701413: fixed in proxychains 3.1-6
has caused the Debian Bug report #701413,
regarding proxychains: ftbfs with eglibc-2.17
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.)


-- 
701413: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701413
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:proxychains
Version: 3.1-5
Severity: important
Tags: sid jessie
User: debian-gl...@lists.debian.org
Usertags: ftbfs-glibc-2.17

The package fails to build in a test rebuild on at least amd64 with
eglibc-2.17, but succeeds to build with eglibc-2.13. The
severity of this report may be raised before the jessie release.

The test rebuild was done together with GCC-4.8, so some issues
might be caused by the updated GCC as well.

  libproxychains.c:337:5: error: conflicting types for 'getnameinfo'

The full build log can be found at:
http://people.debian.org/~doko/logs-20130217/gcc48/proxychains_3.1-5_unstable_gcc48.log
The last lines of the build log are at the end of this report.

To install eglibc from experimental,

  apt-get -t experimental install libc6-dev

To build with GCC 4.8, either set CC=gcc-4.8 CXX=g++-4.8 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t experimental install g++ g++-4.7 g++-4.8 libc6-dev


[...]
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating proxychains/Makefile
config.status: creating proxychains/docs/Makefile
config.status: creating proxychains/docs/en/Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
make[1]: Leaving directory `/«PKGBUILDDIR»'
   dh_auto_build -a
make[1]: Entering directory `/«PKGBUILDDIR»'
make  all-recursive
make[2]: Entering directory `/«PKGBUILDDIR»'
Making all in proxychains
make[3]: Entering directory `/«PKGBUILDDIR»/proxychains'
Making all in docs
make[4]: Entering directory `/«PKGBUILDDIR»/proxychains/docs'
Making all in en
make[5]: Entering directory `/«PKGBUILDDIR»/proxychains/docs/en'
make[5]: Nothing to be done for `all'.
make[5]: Leaving directory `/«PKGBUILDDIR»/proxychains/docs/en'
make[5]: Entering directory `/«PKGBUILDDIR»/proxychains/docs'
make[5]: Nothing to be done for `all-am'.
make[5]: Leaving directory `/«PKGBUILDDIR»/proxychains/docs'
make[4]: Leaving directory `/«PKGBUILDDIR»/proxychains/docs'
make[4]: Entering directory `/«PKGBUILDDIR»/proxychains'
/bin/bash ../libtool --tag=CC   --mode=compile x86_64-linux-gnu-gcc 
-DHAVE_CONFIG_H -I. -I..   -D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector 
--param=ssp-buffer-size=4 -Wformat -Werror=format-security -MT 
libproxychains.lo -MD -MP -MF .deps/libproxychains.Tpo -c -o libproxychains.lo 
libproxychains.c
libtool: compile:  x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. 
-D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat 
-Werror=format-security -MT libproxychains.lo -MD -MP -MF 
.deps/libproxychains.Tpo -c libproxychains.c  -fPIC -DPIC -o 
.libs/libproxychains.o
libproxychains.c:337:5: error: conflicting types for 'getnameinfo'
 int getnameinfo (const struct sockaddr * sa,
 ^
In file included from libproxychains.c:26:0:
/usr/include/netdb.h:677:12: note: previous declaration of 'getnameinfo' was 
here
 extern int getnameinfo (const struct sockaddr *__restrict __sa,
^
make[4]: *** [libproxychains.lo] Error 1
make[4]: Leaving directory `/«PKGBUILDDIR»/proxychains'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/«PKGBUILDDIR»/proxychains'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/«PKGBUILDDIR»'
make[1]: *** [all] Error 2
dh_auto_build: make -j1 returned exit code 2
make[1]: Leaving directory `/«PKGBUILDDIR»'
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
--- End Message ---
--- Begin Message ---
Source: proxychains
Source-Version: 3.1-6

We believe that the bug you reported is fixed in the latest version of
proxychains, 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 t

Processed: tagging 698104

[Debian Bug Tracking System]

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

> tags 698104 + pending
Bug #698104 [goffice] Patch to fix FTBFS on non-long-double ARM and MIPS
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
698104: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698104
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

Processed: owner 698104

[Debian Bug Tracking System]

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

> owner 698104 !
Bug #698104 [goffice] Patch to fix FTBFS on non-long-double ARM and MIPS
Owner recorded as Dmitry Smirnov .
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
698104: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698104
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#709906: texi2html: Missing dependency on libtext-unidecode-perl

[Daniel Schepler]

On Sunday, May 26, 2013 08:58:07 PM Ralf Treinen wrote:
> On Sun, May 26, 2013 at 08:47:38AM -0700, Daniel Schepler wrote:
> > Package: texi2html
> > Version: 1.82+dfsg1-2
> > Severity: serious
> > 
> > >From my pbuilder log of diffutils:
> > ...
> > 
> >dh_install
> >debian/rules override_dh_installdocs
> > 
> > make[1]: Entering directory `/tmp/buildd/diffutils-3.2'
> > cd doc && texi2html -split_chapter diffutils.texi
> > Can't locate Text/Unidecode.pm in @INC (@INC contains: /etc/perl
> > /usr/local/lib/perl/5.14.2 /usr/local/share/perl/5.14.2 /usr/lib/perl5
> > /usr/share/perl5 /usr/lib/perl/5.14 /usr/share/perl/5.14
> > /usr/local/lib/site_perl .) at /usr/bin/texi2html line 12577. make[1]:
> > *** [override_dh_installdocs] Error 2
> > make[1]: Leaving directory `/tmp/buildd/diffutils-3.2'
> > make: *** [binary] Error 2
> > dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit
> > status 2
> I just tried to compile texi2html 1.82+dfsg1-2 with pbuilder, and it
> compiles just fine on my machine (amd64/sid).
> 
> Can you make the complete log of your failed build available?

texi2html builds fine for me, too.  The bug I'm reporting is missing binary 
dependencies in the resulting package, which is causing build failures in 
other packages (also confirmed in a clean pbuilder chroot using the official 
binary packages).  The example above is from the failure of diffutils.
-- 
Daniel Schepler


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

Bug#709770: marked as done (libjs-prototype: broken symlinks)

[Debian Bug Tracking System]

Your message dated Sun, 26 May 2013 19:04:07 +
with message-id 
and subject line Bug#709770: fixed in prototypejs 1.7.1-2
has caused the Debian Bug report #709770,
regarding libjs-prototype: broken symlinks
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.)


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

Package: libjs-prototype
Version: 1.7.1-1
Severity: grave
Justification: renders package (mostly) unusable
User: debian...@lists.debian.org
Usertags: adequate

Symlinks shipped by this package are broken:

$ file /usr/share/javascript/prototype/*
/usr/share/javascript/prototype/prototype-1.7.1.js: HTML document, ASCII text
/usr/share/javascript/prototype/prototype-1.7.js:   broken symbolic link to 
`prototype-1.7.0.js'
/usr/share/javascript/prototype/prototype-1.js: broken symbolic link to 
`prototype-1.7.0.js'
/usr/share/javascript/prototype/prototype.js:   broken symbolic link to 
`prototype-1.7.0.js'

--
Jakub Wilk
--- End Message ---
--- Begin Message ---
Source: prototypejs
Source-Version: 1.7.1-2

We believe that the bug you reported is fixed in the latest version of
prototypejs, 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 709...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Frank Habermann  (supplier of updated prototypejs 
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: Sun, 26 May 2013 20:55:00 +0200
Source: prototypejs
Binary: libjs-prototype
Architecture: source all
Version: 1.7.1-2
Distribution: unstable
Urgency: low
Maintainer: Frank Habermann 
Changed-By: Frank Habermann 
Description: 
 libjs-prototype - JavaScript Framework for dynamic web applications
Closes: 709770
Changes: 
 prototypejs (1.7.1-2) unstable; urgency=low
 .
   * fixed wrong symlinks to prototypejs (Closes: #709770)
Checksums-Sha1: 
 433d9cfc36cbd1ab547d2a6abf8a719cc5f60e74 1713 prototypejs_1.7.1-2.dsc
 43376cc479e55996a7de6d35741ca63ba41c0ad2 2394 prototypejs_1.7.1-2.diff.gz
 b004cfd2d36ea158f812b1e7d4f8a426bbe83f69 44186 libjs-prototype_1.7.1-2_all.deb
Checksums-Sha256: 
 52b9a70c7dbde7749537202b44521ed87bef79a7409993147a90c69931044ee5 1713 
prototypejs_1.7.1-2.dsc
 c056f194e9781986eb75006e229b40de55ba688269d714f7c41db39722a4b295 2394 
prototypejs_1.7.1-2.diff.gz
 4fed1e206a01702cc0f81775bdd26a306e1ef87f0486749bd42081f6e9cb2503 44186 
libjs-prototype_1.7.1-2_all.deb
Files: 
 0325d42f8e5f9e8330564227a06b3ef0 1713 web optional prototypejs_1.7.1-2.dsc
 61218782219fa08afa6ebe903257c64b 2394 web optional prototypejs_1.7.1-2.diff.gz
 764247358019282aefa3841e5d28c1db 44186 web optional 
libjs-prototype_1.7.1-2_all.deb

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

iQIcBAEBAgAGBQJRolrPAAoJECnja5oB7TrHj8sP/Rps9jMm2uAdBWvzec4CcsL2
hZk32WcyJl1ehkyEI2UFL7T5ej+JYxljXq6ZZplTL3cYgYOFB+Xroc57pW5D9PtA
RVTaRtizUkEXpi3YSS80ZuG0NECeu4HiSWf/31O/1127O+RjBYPy07mbYFhvROuT
u82jHBpdgEi9/1YvmZ68+yriqDqoi/SC1uAjXszc5iYGrbTLxgmC1RDb2m2Dgx2d
T9iSrSuuMIZoY6T8lAbGFAqVMp3DB68QTj60e1JTJMdvhYA+tCvRbjy6XXhYUMNM
3Tl0Uu98MtUnLFi3YxuS++a6u4V/3bIV6TsDMgC9zfaIVSAjyQRkf7IeEAoGqLeK
58NYuNkAgVX/xg6/v/54cbu+sIYiQzOPBrQiqpJVgo8gWKvNFgctIM4qH7oaqO46
SYgnDe1UQTvxdK7u0nMGXLZQMPlfKTMmbkaYeoiH3YKwEUqvqM2GA7l8xSjNnpLA
88nn7Ar3zYDHzyzsJqOiQxhA+nrjuGTjwF7t0gTzQp8KQ7QskrLckLfT9+Yhs2PC
l2vhzxW6qKkWJ+zkxvcdU6eVORJFIzqsBltxlAEwTpbNbWB9Zn8VV4xyuT2F8auF
K3AmeSZ3xMzZzYCKEgW39vfWYro6wcqAH40VLEWkutV9TWykmjeALy9dmd5IY6kw
yD6qZkBFcG6sEgaLPEch
=hcXs
-END PGP SIGNATURE End Message ---

Bug#708739: xfe: FTBFS on non-linux archs

[Joachim Wiedorn]

Hello!

I have seen it and already know the right patches.
I will do an update in the next weeks.


---
Have a nice day.

Joachim (Germany)


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

Processed: tagging 709906

[Debian Bug Tracking System]

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

> tags 709906 + unreproducible
Bug #709906 [texi2html] texi2html: Missing dependency on libtext-unidecode-perl
Added tag(s) unreproducible.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
709906: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709906
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#709906: texi2html: Missing dependency on libtext-unidecode-perl

[Ralf Treinen]

On Sun, May 26, 2013 at 08:47:38AM -0700, Daniel Schepler wrote:
> Package: texi2html
> Version: 1.82+dfsg1-2
> Severity: serious
> 
> >From my pbuilder log of diffutils:
> 
> ...
>dh_install
>debian/rules override_dh_installdocs
> make[1]: Entering directory `/tmp/buildd/diffutils-3.2'
> cd doc && texi2html -split_chapter diffutils.texi
> Can't locate Text/Unidecode.pm in @INC (@INC contains: /etc/perl 
> /usr/local/lib/perl/5.14.2 /usr/local/share/perl/5.14.2 /usr/lib/perl5 
> /usr/share/perl5 /usr/lib/perl/5.14 /usr/share/perl/5.14 
> /usr/local/lib/site_perl .) at /usr/bin/texi2html line 12577.
> make[1]: *** [override_dh_installdocs] Error 2
> make[1]: Leaving directory `/tmp/buildd/diffutils-3.2'
> make: *** [binary] Error 2
> dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 
> 2

I just tried to compile texi2html 1.82+dfsg1-2 with pbuilder, and it
compiles just fine on my machine (amd64/sid).

Can you make the complete log of your failed build available?

Cheers -Ralf.


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

Bug#709923: lesstif-bin and uil: error when trying to install together

[Ralf Treinen]

Package: uil,lesstif-bin
Version: uil/2.3.4-2
Version: lesstif-bin/1:0.95.2-1.1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2013-05-26
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


WARNING: The following packages cannot be authenticated!
  libfreetype6 x11-common libice6 libsm6 libxau6 libxdmcp6 libxcb1 libx11-data
  libx11-6 libxext6 libxp6 libxt6 lesstif2 libexpat1 ucf fonts-dejavu-core
  ttf-dejavu-core fontconfig-config libfontconfig1 libjpeg8 libmotif-common
  libpng12-0 libxrender1 libxft2 libxmu6 libxm4 libmrm4 libuil4 lesstif-bin
  uil
Preconfiguring packages ...
Authentication warning overridden.
Can not write log, openpty() failed (/dev/pts not mounted?)
Selecting previously unselected package libfreetype6:amd64.
(Reading database ... 10806 files and directories currently installed.)
Unpacking libfreetype6:amd64 (from .../libfreetype6_2.4.9-1.1_amd64.deb) ...
Selecting previously unselected package x11-common.
Unpacking x11-common (from .../x11-common_1%3a7.7+3_all.deb) ...
Selecting previously unselected package libice6:amd64.
Unpacking libice6:amd64 (from .../libice6_2%3a1.0.8-2_amd64.deb) ...
Selecting previously unselected package libsm6:amd64.
Unpacking libsm6:amd64 (from .../libsm6_2%3a1.2.1-2_amd64.deb) ...
Selecting previously unselected package libxau6:amd64.
Unpacking libxau6:amd64 (from .../libxau6_1%3a1.0.7-1_amd64.deb) ...
Selecting previously unselected package libxdmcp6:amd64.
Unpacking libxdmcp6:amd64 (from .../libxdmcp6_1%3a1.1.1-1_amd64.deb) ...
Selecting previously unselected package libxcb1:amd64.
Unpacking libxcb1:amd64 (from .../libxcb1_1.8.1-2+deb7u1_amd64.deb) ...
Selecting previously unselected package libx11-data.
Unpacking libx11-data (from .../libx11-data_2%3a1.5.0-1+deb7u1_all.deb) ...
Selecting previously unselected package libx11-6:amd64.
Unpacking libx11-6:amd64 (from .../libx11-6_2%3a1.5.0-1+deb7u1_amd64.deb) ...
Selecting previously unselected package libxext6:amd64.
Unpacking libxext6:amd64 (from .../libxext6_2%3a1.3.1-2+deb7u1_amd64.deb) ...
Selecting previously unselected package libxp6:amd64.
Unpacking libxp6:amd64 (from .../libxp6_1%3a1.0.1-2+deb7u1_amd64.deb) ...
Selecting previously unselected package libxt6:amd64.
Unpacking libxt6:amd64 (from .../libxt6_1%3a1.1.3-1+deb7u1_amd64.deb) ...
Selecting previously unselected package lesstif2:amd64.
Unpacking lesstif2:amd64 (from .../lesstif2_1%3a0.95.2-1.1_amd64.deb) ...
Selecting previously unselected package libexpat1:amd64.
Unpacking libexpat1:amd64 (from .../libexpat1_2.1.0-3_amd64.deb) ...
Selecting previously unselected package ucf.
Unpacking ucf (from .../archives/ucf_3.0027_all.deb) ...
Moving old data out of the way
Selecting previously unselected package fonts-dejavu-core.
Unpacking fonts-dejavu-core (from .../fonts-dejavu-core_2.33+svn2514-3_all.deb) 
...
Selecting previously unselected package ttf-dejavu-core.
Unpacking ttf-dejavu-core (from .../ttf-dejavu-core_2.33+svn2514-3_all.deb) ...
Selecting previously unselected package fontconfig-config.
Unpacking fontconfig-config (from .../fontconfig-config_2.9.0-7.1_all.deb) ...
Selecting previously unselected package libfontconfig1:amd64.
Unpacking libfontconfig1:amd64 (from .../libfontconfig1_2.9.0-7.1_amd64.deb) ...
Selecting previously unselected package libjpeg8:amd64.
Unpacking libjpeg8:amd64 (from .../libjpeg8_8d-1_amd64.deb) ...
Processing triggers for man-db ...
Can not write log, openpty() failed (/dev/pts not mounted?)
Setting up x11-common (1:7.7+3) ...
invoke-rc.d: policy-rc.d denied execution of start.
Can not write log, openpty() failed (/dev/pts not mounted?)
Selecting previously unselected package libmotif-common.
(Reading database ... 11321 files and directories currently installed.)
Unpacking libmotif-common (from .../libmotif-common_2.3.4-2_all.deb) ...
Selecting previously unselected package libpng12-0:amd64.
Unpacking libpng12-0:amd64 (from .../libpng12-0_1.2.49-4_amd64.deb) ...
Selecting previously unselected package libxrender1:amd64.
Unpacking libxrender1:amd64 (from .../libxrender1_1%3a0.9.7-1+deb7u1_amd64.deb) 
...
Selecting previously unselected package libxft2:amd64.
Unpacking libxft2:amd64 (from .../libxft2_2.3.1-1_amd64.deb) ...
Selecting previously unselected package libxmu6:amd64.
Unpacking libxmu6:amd64 (from .../libxmu6_2%3a1.1.1-1_amd64.deb) ...
Selecting previously unselected package libxm4:amd64.
Unpacking libxm4:amd64 (from .../libxm4_2.3.4-2_amd64.deb) ...
Selecting previously unselected package libmrm4:amd64.
Unpacking libmrm4:amd64 (from .../libmrm4_2.3.4-2_amd64.deb) ...
Selecting previously unselected package libuil4:amd64.
Unpacking libuil4:amd64 (from .../libuil4_2.3.4-2_amd64.deb) ...
Selecting previously unselected package lesstif-bin.
Unpacking lesstif-bin (from .../lesstif-bin_1%3a0.95.2-1.1_amd64.de

Bug#709921: im-config: cannot detect IM module files correctly

[Aron Xu]

Package: im-config
Version: 0.21
Severity: serious

The problem is that im-config quits when trying to detect IM module
files that is written in data/??_*.rc, so no IM module is set
correctly and all are falling back to XIM.

For example in data/22_fcitx.rc at line 16 and 17, there are two lines
to cover files in both MultiArch and non-MultiArch paths, and one of
them will match nothing. The line that matches nothing will lead the
script to quit because the script itself is set -e, causing the
trouble described before. The problem is valid for the detection code
of GTK2, GTK3, Qt4, and Clutter IM modules.

 16 for IM_CONFIG_MARKER in /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so \
 17 /usr/lib/gtk-2.0/*/immodules/im-fcitx.so ; do

A working solution is to use ls command and ignore its output to
stderr, which means something looks like:
 16 for IM_CONFIG_MARKER in `ls
/usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so 2>/dev/null` \
 17 `ls
/usr/lib/gtk-2.0/*/immodules/im-fcitx.so 2>/dev/null` ; do

I also recommend to push a stable release update for this bug.

Thanks,
Aron


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

Bug#709636: puppet has deprecated activerecord, and does not work with new version in unstable

[Stig Sandbeck Mathisen]

The "puppetmaster-common" package currently has a Suggests: for "rails".
The dependency is _really_ for activerecord, which is part of rails, so
it has been a bit too wide. 

(The puppet-testsuite package also has a dependency, but this is less
important)

When testing with ruby-activerecord-3.2, puppet master fails compilation
of manifests for a connecting node with the following error:

,
| Error: stack level too deep
| /usr/lib/ruby/vendor_ruby/active_record/dynamic_finder_match.rb:14
`

When testing with ruby-activerecord-2.3, it works well.

Puppet's Gemfile specifies a dependency on activerecord ~> 3.0.7, which
means any version greater than 3.0.7, and lesser than 3.1. Debian does
not provide that.

Activerecord is used for storeconfigs in puppet. 

Storeconfigs using activerecord in puppet was deprecated in puppet 3.x,
and I speculate that it will be removed in puppet 4.x, since they use
semantic versioning.

Puppet Labs provide a "puppetdb" package. This is by far superior to the
stored configuration functionality which used activerecord.
Unfortunately, "puppetdb" is not packaged yet (ITP at #673515), but
upstream has working .deb packages for several Debian releases.

I think it may be best to to simply drop the "rails" dependency from
puppet. Puppet has deprecated activerecord storeconfigs, the new
activerecord 3.2 does not work, and the old activerecord 2.x will be
removed from debian.

-- 
Stig Sandbeck Mathisen


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

Processed: severity of 666844 is important

[Debian Bug Tracking System]

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

> # temporarily lower severity so libembperl-perl can migrate to testing and be 
> backported
> severity 666844 important
Bug #666844 [libembperl-perl] libembperl-perl: sourceful transition towards 
Apache 2.4
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
666844: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666844
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#666844: advice on backporting libembperl-perl

[Florian Schlichting]

Hi,

On Sun, May 26, 2013 at 06:39:01PM +0200, Arno Töll wrote:
> If you feel the need, you can downgrade this bug's severity, and "cheat"
> libembperl-perl into Testing before we're going to actually break Sid. I
> do not expect an Apache 2.4 stack in Testing anytime soon so that will
> give you some time.

ok thanks, I'll go ahead in that direction then

> Having that said, keep in mind, that your package may migrate at some
> point in a 2.4 enabled version to Testing, which is highly unlikely to
> be considered backport material. Thus, a backport of the "last version
> before you upload a 2.4 version" would be an isolated backport, which
> diverges from the actual package in Testing at some point.

I'm primarily concerned with the upgrade path from squeeze. Embperl is
in maintenance mode and has had a hard time keeping up with new versions
of Perl and mod_perl in the past, so not too much in the way of new
upstream versions / features that would be missed. Providing any - even
an isolated - version that works on wheezy is an improvement on the
current state.

Florian


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

Bug#666844: advice on backporting libembperl-perl

[Arno Töll]

Hi,

On 26.05.2013 18:24, Ondřej Surý wrote:
> Just fix the transition bug and make the package buildable with both Apache 
> 2.2 and 2.4.

That's easily doable for web-applications only. Modules, are more
complicated. If you really want, I guess we could find some
configuration which pleases Apache 2.2 and 2.4, but frankly I doubt it's
worth the effort.

If you feel the need, you can downgrade this bug's severity, and "cheat"
libembperl-perl into Testing before we're going to actually break Sid. I
do not expect an Apache 2.4 stack in Testing anytime soon so that will
give you some time.

Having that said, keep in mind, that your package may migrate at some
point in a 2.4 enabled version to Testing, which is highly unlikely to
be considered backport material. Thus, a backport of the "last version
before you upload a 2.4 version" would be an isolated backport, which
diverges from the actual package in Testing at some point.


-- 
with kind regards,
Arno Töll
IRC: daemonkeeper on Freenode/OFTC
GnuPG Key-ID: 0x9D80F36D



signature.asc
Description: OpenPGP digital signature

Bug#666844: advice on backporting libembperl-perl

[Ondřej Surý]

Just fix the transition bug and make the package buildable with both Apache 2.2 
and 2.4.

The Apache 2.4 have some hints how to accomplish that.

Ondřej Surý

On 26. 5. 2013, at 18:22, Florian Schlichting  wrote:

> Hi Arno,
> 
> On Sun, May 26, 2013 at 05:33:47PM +0200 on debian-backports, Micha 
> Lenk wrote:
>> Couldn't you also explain your situation in #666844, and (with consent
>> of Arno and who else might have a say) lower the severity of #666844
>> until libembperl-perl hits testing, and then raise its severity back to RC?
> 
> so here we go:
> 
> libembperl-perl was removed from wheezy in 2011 because it failed to
> build with current versions of Perl and mod_perl for a long time. This
> was eventually fixed upstream late last year, but of course couldn't be
> included in the wheezy release any more. I promised to provide a
> backport once wheezy is released.
> 
> However, before the first dinstall after the wheezy release, you
> upgraded #666844 (sourceful transition towards Apache 2.4) to RC, and
> thus libembperl-perl won't migrate to testing.
> 
> In order to provide users of libembperl-perl in squeeze with an upgrade
> path to wheezy, and considering that the Apache 2.4 transition is not
> going to affect wheezy, would it be acceptable from the point of view of
> the Apache maintainers planning the 2.4 transition to lower the severity
> of #666844 for a day or so until libembperl-perl has entered testing?
> 
> Florian
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-backports-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/20130526162230.gi831...@zedat.fu-berlin.de
> 


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

Bug#666844: advice on backporting libembperl-perl

[Florian Schlichting]

Hi Arno,

On Sun, May 26, 2013 at 05:33:47PM +0200 on debian-backports, Micha 
Lenk wrote:
> Couldn't you also explain your situation in #666844, and (with consent
> of Arno and who else might have a say) lower the severity of #666844
> until libembperl-perl hits testing, and then raise its severity back to RC?

so here we go:

libembperl-perl was removed from wheezy in 2011 because it failed to
build with current versions of Perl and mod_perl for a long time. This
was eventually fixed upstream late last year, but of course couldn't be
included in the wheezy release any more. I promised to provide a
backport once wheezy is released.

However, before the first dinstall after the wheezy release, you
upgraded #666844 (sourceful transition towards Apache 2.4) to RC, and
thus libembperl-perl won't migrate to testing.

In order to provide users of libembperl-perl in squeeze with an upgrade
path to wheezy, and considering that the Apache 2.4 transition is not
going to affect wheezy, would it be acceptable from the point of view of
the Apache maintainers planning the 2.4 transition to lower the severity
of #666844 for a day or so until libembperl-perl has entered testing?

Florian


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

Bug#709911: ghc-doc: postinst uses /usr/share/doc content (Policy 12.3)

[Andreas Beckmann]

Package: ghc-doc
Version: 7.6.3-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package uses files from
/usr/share/doc in its maintainer scripts which is a violation of
Policy 12.3: "Packages must not require the existence of any files in
/usr/share/doc/ in order to function."
http://www.debian.org/doc/debian-policy/ch-docs.html#s12.3

These files must be moved to /usr/share/$PACKAGE and may be symlinked
from /usr/share/doc/$PACKAGE.

This piuparts tests prevents the installation of (most) files into
/usr/share/doc with 'dpkg --path-exclude=...'.

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

  Selecting previously unselected package ghc-doc.
  (Reading database ... 11179 files and directories currently installed.)
  Unpacking ghc-doc (from .../ghc-doc_7.6.3-2_all.deb) ...
  Setting up ghc-doc (7.6.3-2) ...
  haddock: internal error: /usr/share/doc/ghc-doc/html/libraries/prologue.txt: 
openFile: does not exist (No such file or directory)
  dpkg: error processing ghc-doc (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   ghc-doc


Cheers,

Andreas


ghc-doc_7.6.3-2.log.gz
Description: GNU Zip compressed data

Bug#709910: squid: postinst uses /usr/share/doc content (Policy 12.3)

[Andreas Beckmann]

Package: squid
Version: 2.7.STABLE9-4.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package uses files from
/usr/share/doc in its maintainer scripts which is a violation of
Policy 12.3: "Packages must not require the existence of any files in
/usr/share/doc/ in order to function."
http://www.debian.org/doc/debian-policy/ch-docs.html#s12.3

These files must be moved to /usr/share/$PACKAGE and may be symlinked
from /usr/share/doc/$PACKAGE.

This piuparts tests prevents the installation of (most) files into
/usr/share/doc with 'dpkg --path-exclude=...'.

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

  Selecting previously unselected package squid.
  (Reading database ... 10332 files and directories currently installed.)
  Unpacking squid (from .../squid_2.7.STABLE9-4.1_amd64.deb) ...
  Setting up squid (2.7.STABLE9-4.1) ...
  cp: cannot stat '/usr/share/doc/squid/examples/squid.conf': No such file or 
directory
  dpkg: error processing squid (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   squid


Cheers,

Andreas


squid_2.7.STABLE9-4.1.log.gz
Description: GNU Zip compressed data

Bug#709548: libgtk-3-0: most recent gtk upload breaks.... (nearly) everything (in GNOME)

[Michael Biebl]

Am 26.05.2013 00:34, schrieb Loïc FAVORY:
> Yes, i don't know how to do it, but it seems a good idea... ;)

Loic, please file a bug against the relevant themes. They need to be
updated for the changes in GTK3.

Please report back with the bug number so we can track this and
eventually add a Breaks against the fixed version.

Michael


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



signature.asc
Description: OpenPGP digital signature

Bug#709906: texi2html: Missing dependency on libtext-unidecode-perl

[Daniel Schepler]

Package: texi2html
Version: 1.82+dfsg1-2
Severity: serious

>From my pbuilder log of diffutils:

...
   dh_install
   debian/rules override_dh_installdocs
make[1]: Entering directory `/tmp/buildd/diffutils-3.2'
cd doc && texi2html -split_chapter diffutils.texi
Can't locate Text/Unidecode.pm in @INC (@INC contains: /etc/perl 
/usr/local/lib/perl/5.14.2 /usr/local/share/perl/5.14.2 /usr/lib/perl5 
/usr/share/perl5 /usr/lib/perl/5.14 /usr/share/perl/5.14 
/usr/local/lib/site_perl .) at /usr/bin/texi2html line 12577.
make[1]: *** [override_dh_installdocs] Error 2
make[1]: Leaving directory `/tmp/buildd/diffutils-3.2'
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
-- 
Daniel Schepler


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

Bug#709905: gdbm: FTBFS: texinfo errors

[Daniel Schepler]

Source: gdbm
Version: 1.8.3-11
Severity: serious

>From my pbuilder build log:

...
/bin/bash ./libtool --mode=link gcc -g -O2 -fstack-protector 
--param=ssp-buffer-size=4 -Wformat -Werror=format-security -O2 -g -Wall 
-D_REENTRANT -Wl,-z,relro -o libgdbm_compat.la -rpath /usr/lib/x86_64-linux-gnu 
\
-version-info 3 0 0 dbminit.lo delete.lo fetch.lo store.lo 
seq.lo close.lo dbmopen.lo dbmdelete.lo dbmfetch.lo dbmstore.lo dbmseq.lo 
dbmclose.lo dbmdirfno.lo dbmpagfno.lo dbmrdonly.lo -lgdbm
libtool: link: gcc -shared  -fPIC -DPIC  .libs/dbminit.o .libs/delete.o 
.libs/fetch.o .libs/store.o .libs/seq.o .libs/close.o .libs/dbmopen.o 
.libs/dbmdelete.o .libs/dbmfetch.o .libs/dbmstore.o .libs/dbmseq.o 
.libs/dbmclose.o .libs/dbmdirfno.o .libs/dbmpagfno.o .libs/dbmrdonly.o   
-Wl,-rpath -Wl,/tmp/buildd/gdbm-1.8.3/.libs 
/tmp/buildd/gdbm-1.8.3/.libs/libgdbm.so  -O2 -O2 -Wl,-z -Wl,relro   -Wl,-soname 
-Wl,libgdbm_compat.so.3 -o .libs/libgdbm_compat.so.3.0.0
libtool: link: (cd ".libs" && rm -f "libgdbm_compat.so.3" && ln -s 
"libgdbm_compat.so.3.0.0" "libgdbm_compat.so.3")
libtool: link: (cd ".libs" && rm -f "libgdbm_compat.so" && ln -s 
"libgdbm_compat.so.3.0.0" "libgdbm_compat.so")
libtool: link: ar cru .libs/libgdbm_compat.a  dbminit.o delete.o fetch.o 
store.o seq.o close.o dbmopen.o dbmdelete.o dbmfetch.o dbmstore.o dbmseq.o 
dbmclose.o dbmdirfno.o dbmpagfno.o dbmrdonly.o
libtool: link: ranlib .libs/libgdbm_compat.a
libtool: link: ( cd ".libs" && rm -f "libgdbm_compat.la" && ln -s 
"../libgdbm_compat.la" "libgdbm_compat.la" )
make[1]: Leaving directory `/tmp/buildd/gdbm-1.8.3'
/usr/bin/make gdbm.info
make[1]: Entering directory `/tmp/buildd/gdbm-1.8.3'
makeinfo ./gdbm.texinfo
./gdbm.texinfo:42: unknown command `null'
./gdbm.texinfo:56: unknown command `null'
./gdbm.texinfo:549: warning: Up pointer `top' (for node `Options') different 
from node name `Top'
make[1]: *** [gdbm.info] Error 1
make[1]: Leaving directory `/tmp/buildd/gdbm-1.8.3'
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
-- 
Daniel Schepler


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

Bug#709903: automake1.11: FTBFS: texinfo errors

[Daniel Schepler]

Source: automake1.11
Version: 1:1.11.6-1
Severity: serious

>From my pbuilder build log:

...
Making all in doc
make[2]: Entering directory `/tmp/buildd/automake1.11-1.11.6/doc'
Updating ./version.texi
restore=: && backupdir=".am$$" && \
am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd . && \
rm -rf $backupdir && mkdir $backupdir && \
if (/bin/bash /tmp/buildd/automake1.11-1.11.6/lib/missing --run makeinfo 
--version) >/dev/null 2>&1; then \
  for f in automake.info automake.info-[0-9] automake.info-[0-9][0-9] 
automake.i[0-9] automake.i[0-9][0-9]; do \
if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
  done; \
else :; fi && \
cd "$am__cwd"; \
if /bin/bash /tmp/buildd/automake1.11-1.11.6/lib/missing --run makeinfo   -I . \
 -o automake.info automake.texi; \
then \
  rc=0; \
  CDPATH="${ZSH_VERSION+.}:" && cd .; \
else \
  rc=$?; \
  CDPATH="${ZSH_VERSION+.}:" && cd . && \
  $restore $backupdir/* `echo "./automake.info" | sed 's|[^/]*$||'`; \
fi; \
rm -rf $backupdir; exit $rc
automake.texi:13092: @itemx must follow @item
automake.texi:13109: @itemx must follow @item
automake.texi:13115: @itemx must follow @item
make[2]: *** [automake.info] Error 1
make[2]: Leaving directory `/tmp/buildd/automake1.11-1.11.6/doc'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/buildd/automake1.11-1.11.6'
dh_auto_build: make -j1 returned exit code 2
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
-- 
Daniel Schepler


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

Bug#709902: automake1.10: FTBFS: texinfo errors

[Daniel Schepler]

Source: automake1.10
Version: 1:1.10.3-3
Severity: serious

>From my pbuilder build log:

...
Making all in doc
make[2]: Entering directory `/tmp/buildd/automake1.10-1.10.3/doc'
Updating ./version.texi
restore=: && backupdir=".am$$" && \
am__cwd=`pwd` && cd . && \
rm -rf $backupdir && mkdir $backupdir && \
if (/bin/bash /tmp/buildd/automake1.10-1.10.3/lib/missing --run makeinfo 
--version) >/dev/null 2>&1; then \
  for f in automake.info automake.info-[0-9] automake.info-[0-9][0-9] 
automake.i[0-9] automake.i[0-9][0-9]; do \
if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
  done; \
else :; fi && \
cd "$am__cwd"; \
if /bin/bash /tmp/buildd/automake1.10-1.10.3/lib/missing --run makeinfo   -I . \
 -o automake.info automake.texi; \
then \
  rc=0; \
  cd .; \
else \
  rc=$?; \
  cd . && \
  $restore $backupdir/* `echo "./automake.info" | sed 's|[^/]*$||'`; \
fi; \
rm -rf $backupdir; exit $rc
automake.texi:11638: @itemx must follow @item
automake.texi:11655: @itemx must follow @item
automake.texi:11661: @itemx must follow @item
make[2]: *** [automake.info] Error 1
make[2]: Leaving directory `/tmp/buildd/automake1.10-1.10.3/doc'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/buildd/automake1.10-1.10.3'
dh_auto_build: make -j1 returned exit code 2
make: *** [build] Error 2
-- 
Daniel Schepler


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

Bug#709779: marked as done ([synfigstudio] Segment Violation after Synfig core update)

[Debian Bug Tracking System]

Your message dated Sun, 26 May 2013 17:06:03 +0200
with message-id <51a224db.7000...@gmail.com>
and subject line Done: [synfigstudio] Segment Violation after Synfig core update
has caused the Debian Bug report #709779,
regarding [synfigstudio] Segment Violation after Synfig core update
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.)


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

Package: synfigstudio
Version: 0.63.05-1
Severity: grave

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

After the update of Synfig core to 0.64, Synfigstudio break down with a 
segmentation fault.


---
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb0affb40 (LWP 6437)]
0x083a42f9 in studio::WorkAreaTarget::next_tile(int&, int&) ()
---

I've clean and recreate ~/.synfig.

I've seen that a synfigstudio update to 0.64 is imminent in testing. 
Maybe it fix the problem... but would be Synfigstudio depend of core 
0.63 as maximum and not permit to update to 0.64?




--- System information. ---
Architecture: i386
Kernel:   Linux 2.6.38-2-686

Debian Release: jessie/sid
  500 testing security.debian.org
  500 testing ftp.de.debian.org
  500 testing debian-multimedia.informatik.uni-erlangen.de
  500 stable  dl.google.com

--- Package information. ---
Depends(Version) | Installed
-+-==
libatkmm-1.6-1   (>= 2.22.1) | 2.22.6-1
libc6   (>= 2.8) | 2.17-3
libcairo2 (>= 1.2.4) | 1.12.14-4
libcairomm-1.0-1  (>= 1.6.4) | 1.10.0-1
libgcc1 (>= 1:4.1.1) | 1:4.8.0-7
libglib2.0-0 (>= 2.12.0) | 2.36.1-2build1
libglibmm-2.4-1c2a  (>= 2.31.22) | 2.32.1-1
libgtk2.0-0   (>= 2.8.0) | 2.24.10-2
libgtkmm-2.4-1c2a  (>= 1:2.24.0) | 1:2.24.2-1
libpangomm-1.4-1 (>= 2.27.1) | 2.28.4-1
libsigc++-2.0-0c2a(>= 2.0.2) | 2.2.10-0.2
libstdc++6  (>= 4.6) | 4.8.0-7
libsynfig0   | 0.64.0-1


Recommends   (Version) | Installed
==-+-===
synfig-examples| 0.64.0-1


Package's Suggests field is empty.
--- End Message ---
--- Begin Message ---

Package: synfigstudio
Version: 0.64.0-1

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

Fixed with 0.64.0-1 update.--- End Message ---

Processed: owner 709896

[Debian Bug Tracking System]

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

> owner 709896 pkg-xfce-de...@lists.alioth.debian.org
Bug #709896 [squeeze] squeeze: depends on obsolete thunar-vfs
Owner recorded as pkg-xfce-de...@lists.alioth.debian.org.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
709896: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709896
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#709897: thunar-vfs: keep thunar-vfs out of Jessie

[Yves-Alexis Perez]

Source: thunar-vfs
Severity: serious
Owner: pkg-xfce-de...@lists.alioth.debian.org

Since thunar-vfs is obsolete, we would like to keep it out of Jessie. We
don't remove it completely for now since Squeeze still depends on it,
but we'll ask for a removal from testing and add an RC bug so it doesn't
migrate anymore.

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

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


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

Bug#709896: squeeze: depends on obsolete thunar-vfs

[Yves-Alexis Perez]

Package: squeeze
Version: 0.2.3-12
Severity: serious

Squeeze currently uses thunar-vfs. It should be ported to Gio/Gvfs and
in the meanwhile should be kept off Jessie, so adding an RC bug before
asking for removal.

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

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

Versions of packages squeeze depends on:
ii  exo-utils   0.10.2-2
ii  libatk1.0-0 2.8.0-2
ii  libc6   2.17-3
ii  libcairo2   1.12.14-4
ii  libdbus-1-3 1.6.10-1
ii  libdbus-glib-1-20.100.2-1
ii  libexo-1-0  0.10.2-2
ii  libfontconfig1  2.9.0-7.1
ii  libfreetype62.4.9-1.1
ii  libgdk-pixbuf2.0-0  2.28.1-1
ii  libglib2.0-02.36.1-2build1
ii  libgtk2.0-0 2.24.18-1
ii  libpango1.0-0   1.32.5-5
ii  libthunar-vfs-1-2   1.2.0-3+b1
ii  libxfce4util4   4.8.2-2
ii  multiarch-support   2.17-3

squeeze recommends no packages.

squeeze 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#708983: closed by Hideki Yamane (Bug#708983: fixed in net-snmp 5.7.2~dfsg-6)

[Tom Nicholls]

On 25/05/13 13:57, Adam D. Barratt wrote:


Ah, I see. This is a side-effect of the fact that hplip hasn't been
rebuilt against libsnmp30 yet.


Ah, thanks - I wasn't aware that libsnmp15 was being deprecated. That 
makes sense.


> This will sort itself out as the

transition progresses, but in the meantime keeping the old version of
the net-snmp packages installed would be the right thing to do in this
case.


Thanks.


Unfortunately this sort of thing will happen sometimes in unstable,
particularly for packages involved in a transition.


Sure. A certain amount of package breakage is inevitable when tracking 
unstable. It just looked to me as if the fix on this bug was designed to 
prevent this particular dependency issue. Clearly not :-)


T


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

Bug#700389: libtimbl3-dev: Broken dependencies make other packages FTBFS (needs ticcutils/StringOps.h from libticcutils1-dev)

[peter green]

This bug was filed against libtimbl3-dev and the discussion in this bug 
claims it's an issue in that package but the bug was closed with an 
upload of frog.


Closing a bug in one package with an upload of another leaves the bug in 
a somewhat confusing state. The bug is "closed" but it's still 
considered to affect the versions of the original package. That in turn 
means that britney is refusing to migrate timbl to testing which in turn 
means that frog is not buildable in testing (which is a rc issue in it's 
own right).


If you belive that fixing this bug in libtimbl3-dev is needed then 
please do so so that timbl can migrate. Otherwise please fixup the bug 
so it's filed against and closed by the same package.



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

Bug#701417: marked as done (rush: ftbfs with eglibc-2.17)

[Debian Bug Tracking System]

Your message dated Sun, 26 May 2013 13:48:48 +
with message-id 
and subject line Bug#701417: fixed in rush 1.7+dfsg-3
has caused the Debian Bug report #701417,
regarding rush: ftbfs with eglibc-2.17
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.)


-- 
701417: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701417
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:rush
Version: 1.7+dfsg-1
Severity: important
Tags: sid jessie
User: debian-gl...@lists.debian.org
Usertags: ftbfs-glibc-2.17

The package fails to build in a test rebuild on at least amd64 with
eglibc-2.17, but succeeds to build with eglibc-2.13. The
severity of this report may be raised before the jessie release.

The test rebuild was done together with GCC-4.8, so some issues
might be caused by the updated GCC as well.

  ./stdio.h:434:1: error: 'gets' undeclared here (not in a function)

The full build log can be found at:
http://people.debian.org/~doko/logs-20130217/gcc48/rush_1.7+dfsg-1_unstable_gcc48.log
The last lines of the build log are at the end of this report.

To install eglibc from experimental,

  apt-get -t experimental install libc6-dev

To build with GCC 4.8, either set CC=gcc-4.8 CXX=g++-4.8 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t experimental install g++ g++-4.7 g++-4.8 libc6-dev


[...]
config.status: creating etc/Makefile
config.status: creating po/Makefile.in
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing po-directories commands
config.status: creating po/POTFILES
config.status: creating po/Makefile
make[1]: Leaving directory `/«BUILDDIR»/rush-1.7+dfsg'
   dh_auto_build -a
make[1]: Entering directory `/«BUILDDIR»/rush-1.7+dfsg'
make  all-recursive
make[2]: Entering directory `/«BUILDDIR»/rush-1.7+dfsg'
Making all in gnu
make[3]: Entering directory `/«BUILDDIR»/rush-1.7+dfsg/gnu'
  GENalloca.h
  GENarg-nonnull.h
  GENc++defs.h
  GENconfigmake.h
  GENwarn-on-use.h
  GENlanginfo.h
  GENstdio.h
  GENstdlib.h
  GENstring.h
  GENtime.h
  GENunistd.h
  GENwchar.h
  GENwctype.h
make  all-recursive
make[4]: Entering directory `/«BUILDDIR»/rush-1.7+dfsg/gnu'
make[5]: Entering directory `/«BUILDDIR»/rush-1.7+dfsg/gnu'
  CC c-ctype.o
  CC exitfail.o
  CC localcharset.o
In file included from localcharset.c:30:0:
./stdio.h:434:1: error: 'gets' undeclared here (not in a function)
 _GL_WARN_ON_USE (gets, "gets is a security hole - use fgets instead");
 ^
make[5]: *** [localcharset.o] Error 1
make[5]: Leaving directory `/«BUILDDIR»/rush-1.7+dfsg/gnu'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/«BUILDDIR»/rush-1.7+dfsg/gnu'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/«BUILDDIR»/rush-1.7+dfsg/gnu'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/«BUILDDIR»/rush-1.7+dfsg'
make[1]: *** [all] Error 2
dh_auto_build: make -j1 returned exit code 2
make[1]: Leaving directory `/«BUILDDIR»/rush-1.7+dfsg'
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
--- End Message ---
--- Begin Message ---
Source: rush
Source-Version: 1.7+dfsg-3

We believe that the bug you reported is fixed in the latest version of
rush, 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 701...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mats Erik Andersson  (supplier of updated rush 
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: Sat, 25 May 2013 01:28:25 +0200
Source: rush
Binary: rush
Architecture: source amd64
Version: 1.7+dfsg-3
Distribution: unstable
Urgency: low
Maintainer: Mats Erik Andersson 
Changed-By: Mats Erik Andersson 
Description: 
 rush   - restricted user shell
Closes: 701417 708935
Changes: 
 rush (1.7+dfsg-3) unstable; urgency=low
 .
   * debian/control: Standards 3.9.4, no changes needed.
 + Provide a better link for the field Homepage.
   * debian/rules: Add '--disable-silent-rules.'
   * Security of chrooted execution:
 + debian/patches

Bug#707938: gup.postinst: 11: cd: can't cd to /var/lib/gup/

[Prach Pongpanich]

Hi,

I attach a patch to fix this bug.
In debian/gup.postrm is only remove directories but user already exists.

diff -Nru gup-0.5.14/debian/gup.postinst gup-0.5.14.1/debian/gup.postinst
--- gup-0.5.14/debian/gup.postinst  2013-04-01 10:59:34.0 +0700
+++ gup-0.5.14.1/debian/gup.postinst2013-05-26 20:04:14.0 +0700
@@ -5,6 +5,10 @@
 if ! getent passwd gup >/dev/null; then
   adduser --system --home /var/lib/gup/ --ingroup news \
 --disabled-password --gecos "Group Update Program" gup
+else
+  delgroup --quiet --system gup
+  adduser --system --home /var/lib/gup/ --ingroup news \
+--disabled-password --gecos "Group Update Program" gup
 fi

 if [ ! -d /var/lib/gup/default ]; then
diff -Nru gup-0.5.14/debian/gup.postrm gup-0.5.14.1/debian/gup.postrm
--- gup-0.5.14/debian/gup.postrm2013-04-01 12:41:51.0 +0700
+++ gup-0.5.14.1/debian/gup.postrm  2013-05-26 19:53:07.0 +0700
@@ -2,6 +2,7 @@

 if [ "$1" = purge ]; then
   rm -rf /var/lib/gup/ /etc/gup.conf /var/log/gup/ >/dev/null
+  delgroup --quiet --system gup
 fi

 #DEBHELPER#

Regrads,

-- 
 ปรัชญ์ พงษ์พานิช
 Prach Pongpanich


fix-707938.diff
Description: Binary data

Bug#708807: pspp: diff for NMU version 0.7.9+git20120620-1.2

[Sebastian Ramacher]

Control: tags -1 + patch pending

Dear maintainer,

I've prepared an NMU for pspp (versioned as 0.7.9+git20120620-1.2) and
uploaded it to DELAYED/1. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
Sebastian Ramacher
diff -Nru pspp-0.7.9+git20120620/debian/changelog pspp-0.7.9+git20120620/debian/changelog
--- pspp-0.7.9+git20120620/debian/changelog	2013-02-05 00:25:40.0 +0100
+++ pspp-0.7.9+git20120620/debian/changelog	2013-05-26 12:37:56.0 +0200
@@ -1,3 +1,13 @@
+pspp (0.7.9+git20120620-1.2) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * debian/patches/fix_ftbfs_gets: Apply patch from Ubuntu to fix FTBFS with
+eglibc 2.17. (Closes: #708807)
+  * debian/patches/texinfo-5: Apply patch from upstream to fix FTBFS with
+texinfo 5.
+
+ -- Sebastian Ramacher   Sun, 26 May 2013 12:37:54 +0200
+
 pspp (0.7.9+git20120620-1.1) unstable; urgency=low
 
   * Non-maintainer upload.
diff -Nru pspp-0.7.9+git20120620/debian/patches/fix_ftbfs_gets pspp-0.7.9+git20120620/debian/patches/fix_ftbfs_gets
--- pspp-0.7.9+git20120620/debian/patches/fix_ftbfs_gets	1970-01-01 01:00:00.0 +0100
+++ pspp-0.7.9+git20120620/debian/patches/fix_ftbfs_gets	2013-05-24 13:15:11.0 +0200
@@ -0,0 +1,23 @@
+Description: Fix FTBFS with eglibc 2.17
+Origin: vendor
+Bug-Debian: http://bugs.debian.org/708807
+Last-Update: 2013-05-24
+
+--- a/gnulib/lib/stdio.in.h
 b/gnulib/lib/stdio.in.h
+@@ -711,11 +711,15 @@
+ _GL_CXXALIAS_SYS (gets, char *, (char *s));
+ #  undef gets
+ # endif
++# if defined gets
+ _GL_CXXALIASWARN (gets);
++# endif
+ /* It is very rare that the developer ever has full control of stdin,
+so any use of gets warrants an unconditional warning.  Assume it is
+always declared, since it is required by C89.  */
++# if defined gets
+ _GL_WARN_ON_USE (gets, "gets is a security hole - use fgets instead");
++# endif
+ #endif
+ 
+ 
diff -Nru pspp-0.7.9+git20120620/debian/patches/series pspp-0.7.9+git20120620/debian/patches/series
--- pspp-0.7.9+git20120620/debian/patches/series	2013-02-04 23:07:56.0 +0100
+++ pspp-0.7.9+git20120620/debian/patches/series	2013-05-24 13:14:34.0 +0200
@@ -1,2 +1,4 @@
 fix_paths_in_manpage
 699263
+fix_ftbfs_gets
+texinfo-5
diff -Nru pspp-0.7.9+git20120620/debian/patches/texinfo-5 pspp-0.7.9+git20120620/debian/patches/texinfo-5
--- pspp-0.7.9+git20120620/debian/patches/texinfo-5	1970-01-01 01:00:00.0 +0100
+++ pspp-0.7.9+git20120620/debian/patches/texinfo-5	2013-05-24 13:15:51.0 +0200
@@ -0,0 +1,25 @@
+Description: Fix FTBFS with texinfo 5.x
+Origin: upstream,
+ http://git.savannah.gnu.org/cgit/pspp.git/commit/doc/utilities.texi?id=ac9ad68f886cc67c0f2ec144c2bfcb148031d452
+Last-Update: 2013-05-24
+
+--- pspp-0.7.9+git20120620.orig/doc/utilities.texi
 pspp-0.7.9+git20120620/doc/utilities.texi
+@@ -721,7 +721,7 @@ If @subcmd{TNUMBERS} is set to @subcmd{L
+ If the a value has no label, then it will be displayed using its literal value.
+ If @subcmd{TNUMBERS} is set to @subcmd{BOTH}, then values will be displayed with both their label
+ (if any) and their literal value in parentheses.
+-@itemx TVARS
++@item TVARS
+ The @subcmd{TVARS} option sets the way in which variables are displayed in output tables.
+ The valid settings are @subcmd{NAMES}, @subcmd{LABELS} and @subcmd{BOTH}.
+ If @subcmd{TVARS} is set to @subcmd{NAMES}, then all variables are displayed using their names.
+@@ -861,7 +861,7 @@ parameters.  Parameters that can be chan
+ with the same name.  @cmd{SHOW} supports the following additional
+ subcommands:
+ 
+-@table @bullet
++@table @asis
+ @item @subcmd{ALL}
+ Show all settings.
+ @item @subcmd{CC}


signature.asc
Description: Digital signature

Processed: pspp: diff for NMU version 0.7.9+git20120620-1.2

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch pending
Bug #708807 [src:pspp] pspp: FTBFS: ./stdio.h:1030:1: error: 'gets' undeclared 
here (not in a function)
Added tag(s) pending and patch.

-- 
708807: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708807
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

Processed: Re: Bug#708366: marked as done (pike7.8: FTBFS due to conflicting REG_* definitions)

[Debian Bug Tracking System]

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

> found 708366 7.8.700-3
Bug #708366 {Done: Magnus Holmgren } [pike7.8] pike7.8: 
FTBFS due to conflicting REG_* definitions
Marked as found in versions pike7.8/7.8.700-3; no longer marked as fixed in 
versions pike7.8/7.8.700-3 and reopened.
> stop
Stopping processing here.

Please contact me if you need assistance.
-- 
708366: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708366
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#708366: marked as done (pike7.8: FTBFS due to conflicting REG_* definitions)

[Magnus Holmgren]

found 708366 7.8.700-3
stop

Oops, that didn't work. Apparently I only tested building the package on i386 
in my mind.

-- 
Magnus Holmgrenholmg...@debian.org
Debian Developer 


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

Bug#707891: llvm-toolchain-3.2 FTBFS on most architectures.

[Sylvestre Ledru]

On 24/05/2013 00:26, peter green wrote:
> Recent uploads have changed things round a bit. The package still FTBFS
> on most architectures but it does so in a different way.
>> make[1]: Leaving directory
>> `/build/buildd-llvm-toolchain-3.2_3.2repack-6-s390x-gQ5TrE/llvm-toolchain-3.2-3.2repack'
>>
>>dh_install -a
>> cp: cannot stat 'debian/tmp/usr/bin/lldb-3.2': No such file or directory
>> dh_install: cp -a debian/tmp/usr/bin/lldb-3.2
>> debian/lldb-3.2//usr/bin/ returned exit code 1
>> make: *** [binary-arch] Error 2
>>   
> This looks like you need to set the architecture list for lldb-3.2 in
> debian/control to match the list of architectures that you are building
> lldb on.
> 
I am in vac this week. I will have a look next week.

Sylvestre


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

Processed: found 709749 in 2.0.2-1, severity of 709749 is serious, affects 689121, found 708111 in 2.1.0~rc1-1

[Debian Bug Tracking System]

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

> found 709749 2.0.2-1
Bug #709749 [vdr] vdr: postinst uses /usr/share/doc content (Policy 12.3)
Marked as found in versions vdr/2.0.2-1.
> severity 709749 serious
Bug #709749 [vdr] vdr: postinst uses /usr/share/doc content (Policy 12.3)
Severity set to 'serious' from 'normal'
> affects 689121 + spark
Bug #689121 {Done: Євгеній Мещеряков } [swi-prolog-nox] 
swi-prolog-nox: should not ship /usr/lib/swi-prolog/library/INDEX.pl
Added indication that 689121 affects spark
> found 708111 2.1.0~rc1-1
Bug #708111 [libgd2-xpm-dev,libgd2-noxpm-dev] libgd2-xpm-dev, libgd2-noxpm-dev: 
copyright file missing after upgrade (policy 12.5)
Marked as found in versions libgd2/2.1.0~rc1-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
689121: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689121
708111: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708111
709749: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709749
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#709771: marked as done (libghc-quickcheck2-doc and libghc-quickcheck1-doc: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Sun, 26 May 2013 09:26:19 +
with message-id 
and subject line Bug#709771: fixed in haskell-quickcheck1 1.2.0.1-6
has caused the Debian Bug report #709771,
regarding libghc-quickcheck2-doc and libghc-quickcheck1-doc: error when trying 
to install together
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.)


-- 
709771: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709771
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libghc-quickcheck1-doc,libghc-quickcheck2-doc
Version: libghc-quickcheck1-doc/1.2.0.1-5
Version: libghc-quickcheck2-doc/2.5.1.1-2
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2013-05-25
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


WARNING: The following packages cannot be authenticated!
  gcc-4.8-base libgcc1 libstdc++6 libbsd0 libgmp10 libgmpxx4ldbl libppl12
  libppl-c4 libcloog-ppl1 libffi6 libgomp1 libitm1 libmpfr4 libquadmath0
  libmpc3 gcc-4.7-base binutils cpp-4.7 cpp libgcc-4.7-dev gcc-4.7 gcc
  libbsd-dev libc-dev-bin linux-libc-dev libc6-dev libffi-dev libgmp-dev ghc
  ghc-haddock libghc-quickcheck1-doc libghc-quickcheck2-doc

Extracting templates from packages: 93%
Extracting templates from packages: 100%
Authentication warning overridden.
Can not write log, openpty() failed (/dev/pts not mounted?)
Selecting previously unselected package gcc-4.8-base:amd64.
(Reading database ... 10806 files and directories currently installed.)
Unpacking gcc-4.8-base:amd64 (from .../gcc-4.8-base_4.8.0-7_amd64.deb) ...
Can not write log, openpty() failed (/dev/pts not mounted?)
Setting up gcc-4.8-base:amd64 (4.8.0-7) ...
Can not write log, openpty() failed (/dev/pts not mounted?)
(Reading database ... 10813 files and directories currently installed.)
Preparing to replace libgcc1:amd64 1:4.7.2-5 (using 
.../libgcc1_1%3a4.8.0-7_amd64.deb) ...
Unpacking replacement libgcc1:amd64 ...
Can not write log, openpty() failed (/dev/pts not mounted?)
Setting up libgcc1:amd64 (1:4.8.0-7) ...
Can not write log, openpty() failed (/dev/pts not mounted?)
(Reading database ... 10813 files and directories currently installed.)
Preparing to replace libstdc++6:amd64 4.7.2-5 (using 
.../libstdc++6_4.8.0-7_amd64.deb) ...
Unpacking replacement libstdc++6:amd64 ...
Can not write log, openpty() failed (/dev/pts not mounted?)
Setting up libstdc++6:amd64 (4.8.0-7) ...
Can not write log, openpty() failed (/dev/pts not mounted?)
Selecting previously unselected package libbsd0:amd64.
(Reading database ... 10813 files and directories currently installed.)
Unpacking libbsd0:amd64 (from .../libbsd0_0.4.2-1_amd64.deb) ...
Selecting previously unselected package libgmp10:amd64.
Unpacking libgmp10:amd64 (from .../libgmp10_2%3a5.1.2+dfsg-1_amd64.deb) ...
Selecting previously unselected package libgmpxx4ldbl:amd64.
Unpacking libgmpxx4ldbl:amd64 (from 
.../libgmpxx4ldbl_2%3a5.1.2+dfsg-1_amd64.deb) ...
Selecting previously unselected package libppl12:amd64.
Unpacking libppl12:amd64 (from .../libppl12_1%3a1.0-7_amd64.deb) ...
Selecting previously unselected package libppl-c4:amd64.
Unpacking libppl-c4:amd64 (from .../libppl-c4_1%3a1.0-7_amd64.deb) ...
Selecting previously unselected package libcloog-ppl1:amd64.
Unpacking libcloog-ppl1:amd64 (from .../libcloog-ppl1_0.16.1-2_amd64.deb) ...
Selecting previously unselected package libffi6:amd64.
Unpacking libffi6:amd64 (from .../libffi6_3.0.13-4_amd64.deb) ...
Selecting previously unselected package libgomp1:amd64.
Unpacking libgomp1:amd64 (from .../libgomp1_4.8.0-7_amd64.deb) ...
Selecting previously unselected package libitm1:amd64.
Unpacking libitm1:amd64 (from .../libitm1_4.8.0-7_amd64.deb) ...
Selecting previously unselected package libmpfr4:amd64.
Unpacking libmpfr4:amd64 (from .../libmpfr4_3.1.1-1_amd64.deb) ...
Selecting previously unselected package libquadmath0:amd64.
Unpacking libquadmath0:amd64 (from .../libquadmath0_4.8.0-7_amd64.deb) ...
Selecting previously unselected package libmpc3:amd64.
Unpacking libmpc3:amd64 (from .../libmpc3_1.0.1-1_amd64.deb) ...
Preparing to replace gcc-4.7-base:amd64 4.7.2-5 (using 
.../gcc-4.7-base_4.7.3-4_amd64.deb) ...
Unpacking replacement gcc-4.7-base:amd64 ...
Selecting previously unselected package binutils.
Unpacking binutils (from .../binutils_2.22-8_amd64.deb) ...
Selecting previously unselected package cpp-4.7.
Unpacking cpp-4.7 (from .../cpp-4.7_4.7.3-4_amd64.deb) ...
Selecting previously un

Bug#708800: marked as done (enblend-enfuse: FTBFS: [../../doc/enblend.info] Error)

[Debian Bug Tracking System]

Your message dated Sun, 26 May 2013 09:18:32 +
with message-id 
and subject line Bug#708800: fixed in enblend-enfuse 4.0+dfsg-5
has caused the Debian Bug report #708800,
regarding enblend-enfuse: FTBFS: [../../doc/enblend.info] Error
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.)


-- 
708800: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708800
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: enblend-enfuse
Version: 4.0+dfsg-4
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130517 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[3]: Entering directory 
> `/«BUILDDIR»/enblend-enfuse-4.0+dfsg/build-tree-mp/doc'
> restore=: && backupdir=".am$$" && \
>   am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd ../../doc && \
>   rm -rf $backupdir && mkdir $backupdir && \
>   if (/bin/bash /«BUILDDIR»/enblend-enfuse-4.0+dfsg/missing --run 
> makeinfo --version) >/dev/null 2>&1; then \
> for f in ../../doc/enblend.info ../../doc/enblend.info-[0-9] 
> ../../doc/enblend.info-[0-9][0-9] ../../doc/enblend.i[0-9] 
> ../../doc/enblend.i[0-9][0-9]; do \
>   if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
> done; \
>   else :; fi && \
>   cd "$am__cwd"; \
>   if /bin/bash /«BUILDDIR»/enblend-enfuse-4.0+dfsg/missing --run makeinfo 
> -I .. -I ../../doc --css-include=../../doc/default.css  -I ../../doc \
>-o ../../doc/enblend.info ../../doc/enblend.texi; \
>   then \
> rc=0; \
> CDPATH="${ZSH_VERSION+.}:" && cd ../../doc; \
>   else \
> rc=$?; \
> CDPATH="${ZSH_VERSION+.}:" && cd ../../doc && \
> $restore $backupdir/* `echo "./../../doc/enblend.info" | sed 
> 's|[^/]*$||'`; \
>   fi; \
>   rm -rf $backupdir; exit $rc
> ../../doc/enblend.texi:11: warning: undefined flag: VERSION
> ../../doc/auxmac.texi:23: warning: redefining Texinfo language command: @geq
> ../../doc/auxmac.texi:37: warning: redefining Texinfo language command: @leq
> ../../doc/enblend.texi:353: warning: @ifinfo should only appear at a line 
> beginning (possibly involving @classictimes)
> ../../doc/enblend.texi:353: warning: unknown @end texheight (possibly 
> involving @classictimes)
> ../../doc/enblend.texi:408: bad syntax for @value
> ../../doc/enblend.texi:409: bad syntax for @value
> ../../doc/enblend.texi:411: @item outside of table or list
> ../../doc/enblend.texi:412: @itemx outside of table or list
> ../../doc/enblend.texi:417: bad syntax for @value
> ../../doc/enblend.texi:417: misplaced {
> ../../doc/enblend.texi:417: misplaced }
> ../../doc/enblend.texi:421: bad syntax for @value
> ../../doc/enblend.texi:423: @item outside of table or list
> ../../doc/enblend.texi:424: @itemx outside of table or list
> ../../doc/enblend.texi:461: bad syntax for @value
> ../../doc/enblend.texi:463: @item outside of table or list
> ../../doc/enblend.texi:464: @itemx outside of table or list
> ../../doc/enblend.texi:473: @item outside of table or list
> ../../doc/enblend.texi:474: @itemx outside of table or list
> ../../doc/enblend.texi:676: @item outside of table or list
> ../../doc/enblend.texi:680: `@end' expected `tex', but saw `table'
> ../../doc/enblend.texi:785: warning: @ifinfo should only appear at a line 
> beginning (possibly involving @semilog)
> ../../doc/enblend.texi:787: warning: @ifinfo should only appear at a line 
> beginning (possibly involving @semilog)
> ../../doc/enblend.texi:789: warning: @ifinfo should only appear at a line 
> beginning (possibly involving @semilog)
> ../../doc/enblend.texi:801: warning: @ifinfo should only appear at a line 
> beginning (possibly involving @semilog)
> ../../doc/enblend.texi:803: warning: @ifinfo should only appear at a line 
> beginning (possibly involving @semilog)
> ../../doc/enblend.texi:805: warning: @ifinfo should only appear at a line 
> beginning (possibly involving @semilog)
> ../../doc/enblend.texi:827: warning: @ifinfo should only appear at a line 
> beginning (possibly involving @semilog)
> ../../doc/enblend.texi:829: warning: @ifinfo should only appear at a line 
> beginning (possibly involving @semilog)
> ../../doc/enblend.texi:831: warning: @ifinfo should only appear at a line 
> beginning (possibly involving @semilog)
> ../../doc/enblend.texi:839: warning: @ifinfo should only appear at a line 
> beginning (possibly involving @classictimes)
> ../../doc/enblend.texi:839: warning: unknown @end texHEIGHT (po

Bug#709877: spotweb: fails to install, purge, and install again

[Andreas Beckmann]

Package: spotweb
Version: 20111002+dfsg-4.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install,
remove+purge, and install again.

Like a plain failure on initial install this makes the package too buggy
for a release, thus the severity.

This is often a problem with the home directory of a system user:
the user is not deleted during purge (which is fine), but the home
directory is removed. Since the user already exists on the next
installation, adduser won't recreate the home.

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

  Selecting previously unselected package spotweb.
  (Reading database ... 11023 files and directories currently installed.)
  Unpacking spotweb (from .../spotweb_20111002+dfsg-4.1_all.deb) ...
  Setting up spotweb (20111002+dfsg-4.1) ...
  dbconfig-common: writing config to /etc/dbconfig-common/spotweb.conf
  
  Creating config file /etc/dbconfig-common/spotweb.conf with new version
  
  Creating config file /etc/spotweb/dbconfig.php with new version
  granting access to database spotweb for spotweb@localhost: already exists.
  creating database spotweb: already exists.
  dbconfig-common: flushing administrative password
  
  Creating config file /etc/spotweb/nntpconfig.php with new version
  Updating schema..(mysql)
  Database schema of settings upgrade mislukt:
 Unable to connect to MySQL server: Access denied for user 
'spotweb'@'localhost' (using password: YES)
  
  
  #0 /usr/share/spotweb/lib/SpotDb.php(59): dbeng_mysql->connect()
  #1 /usr/share/spotweb/lib/SpotUpgrader.php(9): SpotDb->connect()
  #2 /usr/share/spotweb/scripts/upgrade-db.php(21): 
SpotUpgrader->__construct(Array)
  #3 {main}dpkg: error processing spotweb (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   spotweb


cheers,

Andreas


spotweb_20111002+dfsg-4.1.log.gz
Description: GNU Zip compressed data

Bug#709841: iceweasel: spurious out of memory + crash (segmentation fault)

[Vincent Lefevre]

On 2013-05-26 08:52:24 +0200, Mike Hommey wrote:
> Without a crash backtrace, there's nothing this bug report is going to
> achieve.

Here is it.

xvii:~> gdb =iceweasel core
GNU gdb (GDB) 7.6-debian
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
...
Reading symbols from /usr/lib/iceweasel/iceweasel...Reading symbols from 
/usr/lib/debug/usr/lib/iceweasel/iceweasel...done.
done.
[...]
warning: .dynamic section for "/usr/lib/x86_64-linux-gnu/libX11.so.6" is not at 
the expected address (wrong library or version mismatch?)

warning: .dynamic section for "/usr/lib/x86_64-linux-gnu/libX11-xcb.so.1" is 
not at the expected address (wrong library or version mismatch?)

warning: .dynamic section for 
"/usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so" is not at the expected 
address (wrong library or version mismatch?)

warning: .dynamic section for "/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so" 
is not at the expected address (wrong library or version mismatch?)

warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

warning: no loadable sections found in added symbol-file system-supplied DSO at 
0x7fffeaffe000
Core was generated by `iceweasel'.
Program terminated with signal 11, Segmentation fault.
#0  0x7fc1e040e0eb in raise (sig=11)
at ../nptl/sysdeps/unix/sysv/linux/pt-raise.c:38
38  ../nptl/sysdeps/unix/sysv/linux/pt-raise.c: No such file or directory.
(gdb) set pagination off
(gdb) bt full
#0  0x7fc1e040e0eb in raise (sig=11) at 
../nptl/sysdeps/unix/sysv/linux/pt-raise.c:38
resultvar = 0
pid = 
#1  0x7fc1dcc0f371 in nsProfileLock::FatalSignalHandler (signo=11, 
info=, context=) at 
/tmp/buildd/iceweasel-21.0/build-xulrunner/toolkit/profile/nsProfileLock.cpp:180
unblock_sigs = {__val = {1024, 0 }}
oldact = 
#2  
No locals.
#3  mozalloc_abort (msg=msg@entry=0x7fc1deb55124 "out of memory") at 
/tmp/buildd/iceweasel-21.0/memory/mozalloc/mozalloc_abort.cpp:30
No locals.
#4  0x7fc1deb550e2 in mozalloc_handle_oom (size=size@entry=32768) at 
/tmp/buildd/iceweasel-21.0/memory/mozalloc/mozalloc_oom.cpp:27
No locals.
#5  0x7fc1deb54f21 in moz_xmalloc (size=32768) at 
/tmp/buildd/iceweasel-21.0/memory/mozalloc/mozalloc.cpp:56
ptr = 
#6  0x7fc1dd80bcff in nsSegmentedBuffer::AppendNewSegment 
(this=this@entry=0x7fc197c05aa8) at 
/tmp/buildd/iceweasel-21.0/xpcom/io/nsSegmentedBuffer.cpp:71
seg = 
#7  0x7fc1dd809d57 in nsPipe::GetWriteSegment (this=0x7fc197c05a00, 
segment=@0x7fc1c49f4c38: 0x7fc1c49f4c80 "N0\310\334\301\177", 
segmentLen=@0x7fc1c49f4c30: 1563529216) at 
/tmp/buildd/iceweasel-21.0/xpcom/io/nsPipe3.cpp:463
seg = 
mon = {mReentrantMonitor = 0x7fc197c05aa0}
#8  0x7fc1dd80a6d5 in nsPipeOutputStream::WriteSegments 
(this=0x7fc197c05a60, reader=0x7fc1dcc8b796 
, closure=0x7fc1c4072010, count=32768, 
writeCount=0x7fc1c49f4cbc) at 
/tmp/buildd/iceweasel-21.0/xpcom/io/nsPipe3.cpp:1086
readCount = 32705
originalLen = 
rv = 
segment = 0x7fc1c49f4c80 "N0\310\334\301\177"
segmentLen = 1563529216
#9  0x7fc1dcc89481 in WriteSegments (countWritten=, 
count=, writer=, this=) at 
/tmp/buildd/iceweasel-21.0/netwerk/protocol/http/nsHttpTransaction.cpp:636
rv = 
#10 nsHttpTransaction::WriteSegments (this=0x7fc1c4072010, writer=, count=, countWritten=) at 
/tmp/buildd/iceweasel-21.0/netwerk/protocol/http/nsHttpTransaction.cpp:626
No locals.
#11 0x7fc1dcc7cf54 in nsHttpConnection::OnSocketReadable 
(this=0x7fc13706b800) at 
/tmp/buildd/iceweasel-21.0/netwerk/protocol/http/nsHttpConnection.cpp:1404
rv = 
now = 595297492
delta = 
k400ms = 400
n = 0
again = true
#12 0x7fc1dcc7dc8e in nsHttpConnection::OnInputStreamReady 
(this=0x7fc13706b800, in=) at 
/tmp/buildd/iceweasel-21.0/netwerk/protocol/http/nsHttpConnection.cpp:1525
rv = 
#13 0x7fc1dcc315e3 in nsSocketInputStream::OnSocketReady 
(this=this@entry=0x7fc166a15558, condition=condition@entry=NS_OK) at 
/tmp/buildd/iceweasel-21.0/netwerk/base/src/nsSocketTransport2.cpp:226
callback = { = {mRawPtr = 0x7fc13706b810}, }
#14 0x7fc1dcc31816 in nsSocketTransport::OnSocketReady 
(this=0x7fc166a15420, fd=0x7fc19b2ca040, outFlags=1) at 
/tmp/buildd/iceweasel-21.0/netwerk/base/src/nsSocketTransport2.cpp:1565
No locals.
#15 0x7fc1dcc33fce in nsSocketTransportService::DoPollIteration 

Bug#676134: /usr/bin/evolution: Evolution does not start at all

[Thomas Wegner]

Package: evolution
Version: 3.4.4-3
Followup-For: Bug #676134

Dear Maintainer,

Evolution crashes immediately with segmentationfault.
I dist-upgraded my system today. After restarting,
I have to resign in into my google-account. Gnome-online-accounts and libgoa
are upgraded during dist-upgrade.



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

Kernel: Linux 3.9-4.towo-siduction-amd64 (SMP w/6 CPU cores; PREEMPT)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages evolution depends on:
ii  dbus 1.6.10-1
ii  debconf [debconf-2.0]1.5.50
ii  evolution-common 3.4.4-3
ii  evolution-data-server3.4.4-3
ii  gconf-service3.2.5-1+build1
ii  gconf2   3.2.5-1+build1
ii  gnome-icon-theme 3.4.0-2
ii  libatk1.0-0  2.8.0-2
ii  libc62.17-3
ii  libcairo-gobject21.12.14-4
ii  libcairo21.12.14-4
ii  libcamel-1.2-33  3.4.4-3
ii  libclutter-gtk-1.0-0 1.2.0-2
ii  libdbus-glib-1-2 0.100.2-1
ii  libebackend-1.2-23.4.4-3
ii  libebook-1.2-13  3.4.4-3
ii  libecal-1.2-11   3.4.4-3
ii  libedataserver-1.2-163.4.4-3
ii  libedataserverui-3.0-1   3.4.4-3
ii  libenchant1c2a   1.6.0-10
ii  libevolution 3.4.4-3
ii  libgail-3-0  3.8.2-1
ii  libgconf-2-4 3.2.5-1+build1
ii  libgdata13   0.13.3-2
ii  libgdk-pixbuf2.0-0   2.28.1-1
ii  libglib2.0-0 2.36.1-2build1
ii  libgnome-desktop-3-2 3.4.2-2
ii  libgtk-3-0   3.8.2-1
ii  libgtkhtml-4.0-0 4.4.4-1
ii  libgtkhtml-editor-4.0-0  4.4.4-1
ii  libgweather-3-0  3.4.1-1+build1
ii  libical0 0.48-2
ii  libmx-1.0-2  1.4.6-1
ii  libnotify4   0.7.5-2
ii  libnspr4 2:4.9.6-1
ii  libnspr4-0d  2:4.9.6-1
ii  libnss3  2:3.14.3-1
ii  libnss3-1d   2:3.14.3-1
ii  libpango1.0-01.32.5-5
ii  libsoup2.4-1 2.42.2-3
ii  libsqlite3-0 3.7.17-1
ii  libxml2  2.8.0+dfsg1-7+nmu1
ii  psmisc   22.20-1

Versions of packages evolution recommends:
pn  bogofilter | spamassassin  
pn  evolution-plugins  
ii  evolution-webcal   2.32.0-2+b1
ii  yelp   3.4.2-1+b1

Versions of packages evolution suggests:
pn  evolution-dbg   
pn  evolution-exchange  
pn  evolution-plugins-experimental  
ii  gnupg   1.4.12-7
ii  network-manager 0.9.8.0-5

-- debconf information:
  evolution/kill_processes:
  evolution/needs_shutdown:


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

Bug#708802: pion-net: FTBFS: PionScheduler.cpp:105:40: error: expected unqualified-id before numeric constant

[Andrey Rahmatullin]

On Fri, May 24, 2013 at 12:53:16PM -0500, Steve M. Robbins wrote:
> > > > PionScheduler.cpp:105:40: error: expected unqualified-id before numeric 
> > > > constant
> > The code:
> > boost::xtime_get(&wakeup_time, boost::TIME_UTC);
> > 
> > According to https://bugzilla.redhat.com/show_bug.cgi?id=825039 it's a
> > problem in boost which is fixed in boost 1.50 by renaming the enum to
> > boost::TIME_UTC_.
> 
> Note this renaming has been backported and fixed in Debian's boost 1.49.0-4, 
> which
> is what was used for the rebuild.  So there is some other issue at play, here.
But renaming the symbol in boost headers is not enough, you need to use
the new name in the source.

-- 
WBR, wRAR


signature.asc
Description: Digital signature