Bug#468751: aptitude update fails with improperly formed Recommends entry in lists files

[Warren Turkal]

Package: aptitude
Version: 0.4.10-1+b2
Severity: critical
Justification: root security hole
Tags: security

When a Recommends line in the package lists files does not have any packages
recommended, aptitude will not update the package lists.

For instance,
# aptitude update

# vi 

# aptitude update
E: Problem parsing dependency Recommends
E: Error occurred while processing acx100-source (NewVersion1)
E: Problem with MergeList
/var/lib/apt/lists/mirrors.kernel.org_debian_dists_unstable_contrib_binary-i386_Packages
E: The package lists or status file could not be parsed or opened.
Segmentation fault
#

It seems to me that this shouldn't cause a failure to update the package lists.
This behaviour also causes packages like adept to not be able to perform updates
potentially leaving users vulnerable to security problems since packages can't
be updated. This bug might be too high priority. I just wanted to make sure that
the security implications were taken into consideration by the maintainers.

Apt-get update works in this case, and I think aptitude update should work also.

Thanks,
wt

-- Package-specific info:
Terminal: xterm
$DISPLAY is set.

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

Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages aptitude depends on:
ii  apt [libapt-pkg-libc6.7 0.7.11   Advanced front-end for dpkg
ii  libc6   2.7-9GNU C Library: Shared libraries
ii  libcwidget1 0.5.6.1-3high-level terminal interface libr
ii  libgcc1 1:4.3-20080227-1 GCC support library
ii  libncursesw55.6+20080203-1   Shared libraries for terminal hand
ii  libsigc++-2.0-0c2a  2.0.17-2 type-safe Signal Framework for C++
ii  libstdc++6  4.3-20080227-1   The GNU Standard C++ Library v3

Versions of packages aptitude recommends:
ii  aptitude-doc-en [aptitude-doc 0.4.10-1   English manual for aptitude, a ter
pn  libparse-debianchangelog-perl  (no description available)

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#468494: Day view in Calendar not working for users, only for groups

[Ralf Becker]

Hi Stefan,

thanks for the bug report.

The bug (and other ones related to newer postgres versions) are fixed in
the current release 1.4. The old version 1.2 is no longer supported by
the egroupware project.

Committing the fix is of cause easy, thought there would be no new 1.2
release, as 1.2 also has other security, php5 and postgres related problems.

I can only recommend to update eGroupWare version 1.4, which is still in
testing in debian afaik.

Ralf

Stefan Bellon schrieb:
> Package: egroupware-infolog
> Version: 1.2.107-2.dfsg-2
> Severity: serious
> Tags: patch
> 
> --- Please enter the report below this line. ---
> 
> After upgrading to egroupware version 1.2.107, the day view in the
> calendar does not work for single users anymore, only for groups. Week
> and month views still work for single users. The error message one gets
> when visiting a person's day view is the following:
> 
> 
> Database error: Invalid SQL: SELECT main.info_id FROM egw_infolog main
> WHERE ( ((info_owner=6 AND info_responsible=0 OR
> ','||info_responsible||',' LIKE '%,6,%') AND (info_owner=6 OR
> (','||info_responsible||',' LIKE '%,6,%' AND info_access='public') OR
> info_owner IN (6) OR (info_access='public' AND info_owner
> IN(-11,6,12,7,9,-1,8,-10))) ) AND NOT (info_status IN
> ('done','billed','cancelled')) AND info_startdate < '1204326000' )
> pgsql Error: -1 (ERROR: operator does not exist: character varying =
> integer LINE 1: ... main WHERE ( ((info_owner=6 AND info_responsible=0
> OR ','|... ^ HINT: No operator matches the given name and argument
> type(s). You might need to add explicit type casts.)
> 
> File: /usr/share/egroupware/infolog/inc/class.soinfolog.inc.php
> Line: 590
> Function: soinfolog::search / boinfolog::search /
> boinfolog::cal_to_include /
> ExecMethod(infolog.boinfolog.cal_to_include) / hooks::single /
> hooks::process / uiviews::get_todos / uiviews::day /
> ExecMethod(calendar.uiviews.day)
> 
> Session halted.
> 
> 
> Having looked at the database schema of egw_infolog I verified that
> postgresql is correct here as the info_responsible column is of type
> character varying but gets compared to integer. Having looked
> inside /usr/share/egroupware/infolog/inc/class.soinfolog.inc.php I
> indeed spotted the problem in line 167 where info_responsible=0 is
> missing the quotation marks to make the 0 a string literal. After
> replacing it with info_responsible='0', the day view works again.
> 
> 
> 
> --- System information. ---
> Architecture: i386
> Kernel:   Linux 2.6.16
> 
> Debian Release: lenny/sid
>   500 unstablewww.debian-multimedia.org 
>   500 unstableftp.debian.org 
> 
> --- Package information. ---
> Depends (Version) | Installed
> =-+-=
> egroupware-core  (= 1.2.107-2.dfsg-2) | 1.2.107-2.dfsg-2
> egroupware-etemplate (= 1.2.107-2.dfsg-2) | 1.2.107-2.dfsg-2
> 
> 

-- 
Ralf Becker
eGroupWare Training & Support ==> http://www.egroupware-support.de
Outdoor Unlimited Training GmbH [www.outdoor-training.de]
Handelsregister HRB Kaiserslautern 3587
Geschäftsführer Birgit und Ralf Becker
Leibnizstr. 17, 67663 Kaiserslautern, Germany
Telefon +49 (0)631 31657-0

Processed: severity of 468644 is important

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.10.16
> severity 468644 important
Bug#468644: fvwm-crystal: should this package be orphaned or removed?
Severity set to `important' from `serious'

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: severity of 468643 is important

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.10.16
> severity 468643 important
Bug#468643: gnump3d: should this package be removed?
Severity set to `important' from `serious'

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#466796: has no business starting a server by default; existing implementation massively insecure; debconf used incorrectly and throws away passwords

[Kartik Mistry]

On Sun, Feb 24, 2008 at 8:17 AM, Kartik Mistry <[EMAIL PROTECTED]> wrote:
> On Thu, Feb 21, 2008 at 9:59 AM, Kumar Appaiah <[EMAIL PROTECTED]> wrote:
>  >  > See e.g. http://wiki.debian.org/DpkgConffileHandling
>  >
>  >  So, based on this, I have prepared a packages which does the
>  >  needful. Please do give me suggestions and things to fix.
>  >
>  >  
> http://mentors.debian.net/debian/pool/main/f/festival/festival_1.96~beta-7.dsc

Dear Joey,

Can you please review and upload the festival given at above link?
Since, Jaldhar is busy and package has critical bug to fix, so I am
requesting you.

Thanks in advance.

-- 
 Cheers,
 Kartik Mistry | 0xD1028C8D | IRC: kart_
 Blogs: {ftbfs,kartikm}.wordpress.com



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: found 468676 in 3:3.3.8b-1

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.10.18.1
> found 468676 3:3.3.8b-1
Bug#468676: FTBFS on arm, (armel) ,mips, mipsel
Bug marked as found in version 3:3.3.8b-1.

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: reopening 468676

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.10.18.1
> reopen 468676
Bug#468676: FTBFS on arm, (armel) ,mips, mipsel
Bug reopened, originator not changed.

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: reassign 468676 to libqt3-mt-dev

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.10.18.1
> reassign 468676 libqt3-mt-dev
Bug#468676: FTBFS on arm, (armel) ,mips, mipsel
Bug reassigned from package `kdesvn' to `libqt3-mt-dev'.

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#464665: marked as done (undefined references on arm)

[Debian Bug Tracking System]

Your message dated Sat, 01 Mar 2008 01:47:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#464665: fixed in maloc 0.2-2
has caused the Debian Bug report #464665,
regarding undefined references on arm
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 [EMAIL PROTECTED]
immediately.)


-- 
464665: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464665
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: libmaloc1
Version: 0.2-1
Severity: grave

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Not sure of grave is correct here, but it causes an FTBFS. Adjust the
severity if necessary.

The build of apbs fails on arm because of undefined references in
libmaloc.so.1.0.0. Quoting the build log:

/usr/lib/libmaloc.so: undefined reference to `readline'
/usr/lib/libmaloc.so: undefined reference to `add_history'
/usr/lib/libmaloc.so: undefined reference to `rl_bind_key'

full log is available at
http://buildd.debian.org/fetch.cgi?pkg=apbs;ver=0.5.1-1.1;arch=arm;stamp=1201659906

Seems it must be linked with libreadline on arm (just a guess).

Regards, Daniel


- -- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.22-3-k7 (SMP w/1 CPU core)
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages libmaloc1 depends on:
ii  libc6 2.7-6  GNU C Library: Shared libraries

libmaloc1 recommends no packages.

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

iD8DBQFHq893m0bx+wiPa4wRAvmNAJ9HUfWDu857L4FPWS6p11qV8bcnKgCeL4a/
FONg5dKz9M0Llh9pVGS8gGo=
=fpFB
-END PGP SIGNATURE-


--- End Message ---
--- Begin Message ---
Source: maloc
Source-Version: 0.2-2

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

libmaloc-dev_0.2-2_i386.deb
  to pool/main/m/maloc/libmaloc-dev_0.2-2_i386.deb
libmaloc1_0.2-2_i386.deb
  to pool/main/m/maloc/libmaloc1_0.2-2_i386.deb
maloc_0.2-2.diff.gz
  to pool/main/m/maloc/maloc_0.2-2.diff.gz
maloc_0.2-2.dsc
  to pool/main/m/maloc/maloc_0.2-2.dsc



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 [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Banck <[EMAIL PROTECTED]> (supplier of updated maloc 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 [EMAIL PROTECTED])


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sat, 01 Mar 2008 02:30:40 +0100
Source: maloc
Binary: libmaloc1 libmaloc-dev
Architecture: source i386
Version: 0.2-2
Distribution: unstable
Urgency: low
Maintainer: Michael Banck <[EMAIL PROTECTED]>
Changed-By: Michael Banck <[EMAIL PROTECTED]>
Description: 
 libmaloc-dev - Object-oriented Abstraction Layer for C (development files)
 libmaloc1  - Object-oriented Abstraction Layer for C
Closes: 464665
Changes: 
 maloc (0.2-2) unstable; urgency=low
 .
   * debian/control (Build-Conflicts): Added libreadline5-dev;
 Closes: #464665.
   * debian/control (Standards-Version): Bumped to 3.7.3.
   * debian/copyright: Updated FSF address.
   * debian/control (libmaloc-dev): Use ${binary:Version} rather than
 ${Source:Version} as substvar.
Files: 
 26b9ecfc02423e62b0ca3a1270e38dfb 614 devel optional maloc_0.2-2.dsc
 0b7106190785102daeba72a04df4010c 2184 devel optional maloc_0.2-2.diff.gz
 4879b5ff8004a56f14e5975f469d95e3 54416 devel optional libmaloc1_0.2-2_i386.deb
 edd71f5834de999c85c94598d1d6f181 102552 libdevel optional 
libmaloc-dev_0.2-2_i386.deb

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

iD8DBQFHyLLYmHaJYZ7RAb8RAnoVAJ0QjkVTWsFy0Dk24v8eruMB46YB0gCdF+OR
CqXBlmda/wjS1GdePa6jQ8s=
=IoYT
-END PGP SIGNATURE-


--- End Message ---

Processed: Re: Bug#468664: claws-mail: SEGFAULTs causing a kernel Oops

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> tags 468664 unreproducible
Bug#468664: claws-mail: SEGFAULTs causing a kernel Oops
There were no tags set.
Tags added: unreproducible

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#468664: claws-mail: SEGFAULTs causing a kernel Oops

[Ricardo Mones]

tags 468664 unreproducible
thanks

On Fri, 29 Feb 2008 22:55:00 +0100
David Paleino <[EMAIL PROTECTED]> wrote:

> This happens also with a fresh configuration (still with 3.3.1).
> 
> I'll try to reproduce with other versions.
> 
> (I know my kernel is tainted -- see that "G" in the message I pasted
> before -- but I currently don't have any non-free module loaded. I'll
> investigate if this tainting might cause the Oops)

  As you see I'm running 3.3.1 in a i386 up-to-date chroot without problems.

  Have you tried to reinstall the package? Disk corruption happens and may
have trashed some bytes on the binary.

  regards,
-- 
 Ricardo Mones
 http://people.debian.org/~mones
 «Never send a human to do a machine's job. -- Agent Smith»

Bug#450455: marked as done (gengameng: FTBFS: mv: cannot stat `/build/user/gengameng-4.1/debian/tmp/usr/include/gengameng/*.h': No such file or directory)

[Debian Bug Tracking System]

Your message dated Sat, 1 Mar 2008 12:43:42 +1300
with message-id <[EMAIL PROTECTED]>
and subject line gengameng removed from the archive
has caused the Debian Bug report #450455,
regarding gengameng: FTBFS: mv: cannot stat 
`/build/user/gengameng-4.1/debian/tmp/usr/include/gengameng/*.h': No such file 
or directory
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 [EMAIL PROTECTED]
immediately.)


-- 
450455: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=450455
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: gengameng
version: 4.1-8
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20071106 qa-ftbfs
Justification: FTBFS on i386

Hi,

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

Relevant part:
make[3]: Entering directory `/build/user/gengameng-4.1'
/bin/sh ./mkinstalldirs /build/user/gengameng-4.1/debian/tmp//usr/bin
mkdir /build/user/gengameng-4.1/debian/tmp/usr/bin
 /usr/bin/install -c gengameng-config 
/build/user/gengameng-4.1/debian/tmp//usr/bin/gengameng-config
make[3]: Nothing to be done for `install-data-am'.
make[3]: Leaving directory `/build/user/gengameng-4.1'
make[2]: Leaving directory `/build/user/gengameng-4.1'
make[1]: Leaving directory `/build/user/gengameng-4.1'
mv /build/user/gengameng-4.1/debian/tmp/usr/include/gengameng/*.h 
/build/user/gengameng-4.1/debian/libgengameng-dev/usr/include/gengameng/
mv: cannot stat 
`/build/user/gengameng-4.1/debian/tmp/usr/include/gengameng/*.h': No such file 
or directory
make: *** [install] Error 1
dpkg-buildpackage: failure: /usr/bin/fakeroot debian/rules binary gave error 
exit status 2

The full build log is available from
http://people.debian.org/~lucas/logs/2007/11/06

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot containing a sid i386
environment.  Internet was not accessible from the build systems.

-- 
| Lucas Nussbaum
| [EMAIL PROTECTED]   http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |


--- End Message ---
--- Begin Message ---
gengameng has been removed from the archive, therefore I am closing all of
the old bug reports related to it.

Francois

--- End Message ---

Bug#468202: openoffice.org-writer2latex: still occurring with 0.5-6

[Hamish Moffatt]

On Fri, Feb 29, 2008 at 08:00:58PM +0100, Rene Engelhard wrote:
> Hi,
> 
> Hamish Moffatt wrote:
> > Thanks. The manual says that if the old prerm fails, dpkg should try the
> > same operation with the new prerm, which you said is fixed. I didn't see
> > it try to do this.
> 
> The problem here might be that the prerm didn't actually fail in
> the sense that it returned an exitcode != 0... But it failed to do its
> job.
> 
> unopkg often returns 0 even if it failed..

So, the new postinst fails because the old prerm failed to do its work
(although it returned success)? In that case can't you simply deal with
this in the new postinst?


Thanks,
Hamish
-- 
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: pyxmms-remote removal

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 461974 normal
Bug#461974: pyxmms: Should this package be removed?
Severity set to `normal' from `serious'

> reassign 461974 ftp.debian.org
Bug#461974: pyxmms: Should this package be removed?
Bug reassigned from package `pyxmms-remote' to `ftp.debian.org'.

> retitle 461974 RM: pyxmms-remote -- RoQA; out of date, depends on xmms
Bug#461974: pyxmms: Should this package be removed?
Changed Bug title to `RM: pyxmms-remote -- RoQA; out of date, depends on xmms' 
from `pyxmms: Should this package be removed?'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: Re: Pressing return while configuring does not accept defaults

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> tags 407761 + patch
Bug#407761: Pressing return while configuring does not accept defaults
There were no tags set.
Tags added: patch

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#407761: Pressing return while configuring does not accept defaults

[Barry deFreese]

tags 407761 + patch
thanks

Hi,

Here is an NMU to fix this bug as well as update the build depends for
postgresql-dev.

Thanks,

Barry deFreese


diff -Nru dak-1.0/debian/changelog dak-1.0/debian/changelog
--- dak-1.0/debian/changelog	2007-01-21 23:54:55.0 -0500
+++ dak-1.0/debian/changelog	2008-02-29 17:55:10.0 -0500
@@ -1,3 +1,12 @@
+dak (1.0-8.5) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Replace postgresql-dev build-dependency with libpq-dev.
++ (Closes: #409761,#429973).
+  * Don't translate debconf defaults. (Closes: #407761).
+
+ -- Barry deFreese <[EMAIL PROTECTED]>  Fri, 29 Feb 2008 17:15:26 -0500
+
 dak (1.0-8.4) unstable; urgency=low
 
   * Non-maintainer upload.
diff -Nru /tmp/I8K2EtdgKf/dak-1.0/debian/control /tmp/2f1I8o8Rds/dak-1.0/debian/control
--- dak-1.0/debian/control	2007-01-18 00:58:02.0 -0500
+++ dak-1.0/debian/control	2008-02-29 17:15:20.0 -0500
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Joerg Jaspert <[EMAIL PROTECTED]>
 Uploaders: James Troup <[EMAIL PROTECTED]>
-Build-Depends: debhelper (>= 4.1.65), postgresql-dev, python-dev (>= 2.3-1), libapt-pkg-dev, sp, docbook, docbook-utils, python-central, po-debconf
+Build-Depends: debhelper (>= 4.1.65), libpq-dev, python-dev (>= 2.3-1), libapt-pkg-dev, sp, docbook, docbook-utils, python-central, po-debconf
 XS-Python-Version: >= 2.3
 Standards-Version: 3.6.1
 
diff -Nru /tmp/I8K2EtdgKf/dak-1.0/debian/po/cs.po /tmp/2f1I8o8Rds/dak-1.0/debian/po/cs.po
--- dak-1.0/debian/po/cs.po	2007-01-18 00:59:22.0 -0500
+++ dak-1.0/debian/po/cs.po	2008-02-29 17:28:45.0 -0500
@@ -3,8 +3,8 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: dak\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2007-01-18 06:58+0100\n"
+"Report-Msgid-Bugs-To: [EMAIL PROTECTED]"
+"POT-Creation-Date: 2008-02-29 17:28-0500\n"
 "PO-Revision-Date: 2005-12-29 09:51+0100\n"
 "Last-Translator: Martin Sin <[EMAIL PROTECTED]>\n"
 "Language-Team: Czech <[EMAIL PROTECTED]>\n"
@@ -13,20 +13,14 @@
 "Content-Transfer-Encoding: 8bit\n"
 
 #. Type: string
-#. Default
-#: ../templates:1001
-msgid "/opt/dak"
-msgstr "/opt/dak"
-
-#. Type: string
 #. Description
-#: ../templates:1002
+#: ../templates:1001
 msgid "Where to put the base directory for dak?"
 msgstr "Kam umístit hlavní adresář pro dak?"
 
 #. Type: string
 #. Description
-#: ../templates:1002
+#: ../templates:1001
 msgid ""
 "It is best to use the dak-suite with a single base directory and not to "
 "split it up all over the filesystems. Makes life easier. This setup will "
@@ -61,20 +55,14 @@
 "usr/share/doc/dak a to včetně konfigurace, kterou program používá. "
 
 #. Type: string
-#. Default
-#: ../templates:3001
-msgid "localhost"
-msgstr "localhost"
-
-#. Type: string
 #. Description
-#: ../templates:3002
+#: ../templates:3001
 msgid "What is the hostname for the archive host?"
 msgstr "Jaké je jméno počítače pro hostitelský archiv?"
 
 #. Type: string
 #. Description
-#: ../templates:3002
+#: ../templates:3001
 msgid ""
 "For proper function dak needs a hostname in different places in its "
 "configuration. The entered value will be used in email addresses and mails "
@@ -85,20 +73,14 @@
 "programem dak."
 
 #. Type: string
-#. Default
-#: ../templates:4001
-msgid "local archive"
-msgstr "místní archiv"
-
-#. Type: string
 #. Description
-#: ../templates:4002
+#: ../templates:4001
 msgid "The name of your archive."
 msgstr "Jméno vašeho archivu."
 
 #. Type: string
 #. Description
-#: ../templates:4002
+#: ../templates:4001
 msgid ""
 "Please give your archive a descriptive name, so your Users see what it is "
 "about."
@@ -107,20 +89,14 @@
 "uživatele."
 
 #. Type: string
-#. Default
-#: ../templates:5001
-msgid "deb-dak"
-msgstr "deb-dak"
-
-#. Type: string
 #. Description
-#: ../templates:5002
+#: ../templates:5001
 msgid "The name of your dak user."
 msgstr "Jméno vašeho uživatele daku."
 
 #. Type: string
 #. Description
-#: ../templates:5002
+#: ../templates:5001
 msgid ""
 "You can choose the user which gets created for the dak package. The default "
 "should be fine, but maybe you prefer something different here."
@@ -129,19 +105,28 @@
 "výchozí hodnota, ale možná si přejete použít někoho jiného."
 
 #. Type: string
-#. Default
-#: ../templates:6001
-msgid "debadmin"
-msgstr "debadmin"
-
-#. Type: string
 #. Description
-#: ../templates:6002
+#: ../templates:6001
 msgid "The name of your dak group."
 msgstr "Jméno vaší skupiny dak."
 
 #. Type: string
 #. Description
-#: ../templates:6002
+#: ../templates:6001
 msgid "You can choose the groupname which gets created for the dak package."
 msgstr "Můžete zvolit skupinu, která bude vytvořena pro potřeby balíčku dak."
+
+#~ msgid "/opt/dak"
+#~ msgstr "/opt/dak"
+
+#~ msgid "localhost"
+#~ msgstr "localhost"
+
+#~ msgid "local archive"
+#~ msgstr "místní archiv"
+
+#~ msgid "deb-dak"
+#~ msgstr "deb-dak"
+
+#~ msgid "debadmin"
+#~ msgstr "debadmin"
diff -Nru /tm

Bug#468676: marked as done (FTBFS on arm, (armel) ,mips, mipsel)

[Debian Bug Tracking System]

Your message dated Fri, 29 Feb 2008 23:40:22 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#468676: FTBFS on arm, (armel) ,mips, mipsel
has caused the Debian Bug report #468676,
regarding FTBFS on arm, (armel) ,mips, mipsel
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 [EMAIL PROTECTED]
immediately.)


-- 
468676: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468676
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: kdesvn
Version: 0.14.2-2
Severity: serious

-snip-
[ 67%] Building CXX object
src/svnfrontend/CMakeFiles/svnfrontend.dir/editpropsdlg.o
/build/buildd/kdesvn-0.14.2/obj-arm-linux-gnu/src/svnfrontend/editpropsdlg.cpp:123:42:
warning: no newline at end of file
/build/buildd/kdesvn-0.14.2/obj-arm-linux-gnu/src/svnfrontend/editpropsdlg.cpp:123:
error: expected `}' at end of input
/build/buildd/kdesvn-0.14.2/obj-arm-linux-gnu/src/svnfrontend/editpropsdlg.cpp:123:
error: expected ',' or ';' at end of input
make[3]: *** [src/svnfrontend/CMakeFiles/svnfrontend.dir/editpropsdlg.o]
Error 1
-snip-

On mips logs there is also mention of unsupported -fstack-protector
call.

http://buildd.debian.org/fetch.cgi?pkg=kdesvn&arch=arm&ver=0.14.2-2&stamp=1204082636&file=log&as=raw

http://buildd.debian.org/fetch.cgi?pkg=kdesvn&arch=armel&ver=0.14.2-2&stamp=1204321305&file=log&as=raw

http://buildd.debian.org/fetch.cgi?pkg=kdesvn&arch=mips&ver=0.14.2-2&stamp=1204207848&file=log&as=raw

http://buildd.debian.org/fetch.cgi?pkg=kdesvn&arch=mipsel&ver=0.14.2-2&stamp=1204102099&file=log&as=raw

-- 
"rm -rf" only sounds scary if you don't have backups


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Riku Voipio schrieb:
> Package: kdesvn
> Version: 0.14.2-2
> Severity: serious

That's not a bug in kdesvn but qt3. Several other kde applications also
ftbfs at the moment.

This issue is known, so I'm closing this bug report.

Cheers,
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
--- End Message ---

Bug#465036: marked as done (ski: FTBFS: checking for pkg-config... no)

[Debian Bug Tracking System]

Your message dated Fri, 29 Feb 2008 22:17:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#465036: fixed in ski 1.3.2-2
has caused the Debian Bug report #465036,
regarding ski: FTBFS: checking for pkg-config... no
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 [EMAIL PROTECTED]
immediately.)


-- 
465036: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465036
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: ski
Version: 1.3.2-1
Severity: serious

Hi,

Your package is failing to build with the following error:
checking for X... no
checking for pkg-config... no
checking for GSKI... configure: error: The pkg-config script could not be found 
or is too old.  Make sure it
is in your PATH or set the PKG_CONFIG environment variable to the full
path to pkg-config.

Alternatively, you may set the environment variables GSKI_CFLAGS
and GSKI_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

To get pkg-config, see .
See `config.log' for more details.
make: *** [config.status] Error 1


It's missing atleast a build dependency on pkg-config.


Kurt



--- End Message ---
--- Begin Message ---
Source: ski
Source-Version: 1.3.2-2

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

ski_1.3.2-2.diff.gz
  to pool/main/s/ski/ski_1.3.2-2.diff.gz
ski_1.3.2-2.dsc
  to pool/main/s/ski/ski_1.3.2-2.dsc
ski_1.3.2-2_i386.deb
  to pool/main/s/ski/ski_1.3.2-2_i386.deb



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 [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ian Wienand <[EMAIL PROTECTED]> (supplier of updated ski 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 [EMAIL PROTECTED])


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Fri, 29 Feb 2008 13:56:55 -0800
Source: ski
Binary: ski
Architecture: source i386
Version: 1.3.2-2
Distribution: unstable
Urgency: low
Maintainer: Ian Wienand <[EMAIL PROTECTED]>
Changed-By: Ian Wienand <[EMAIL PROTECTED]>
Description: 
 ski- ia64 instruction simulator
Closes: 465036
Changes: 
 ski (1.3.2-2) unstable; urgency=low
 .
   * Actually, we missed a whole bunch of depends, add them back in
 (Closes: #465036)
   * Openmotif is still in non-free, disable x11
   * Thanks to Kurt Roeckx <[EMAIL PROTECTED]> for helping out
Files: 
 3318c9411420a9931e18567fd108b841 781 misc optional ski_1.3.2-2.dsc
 d0203a1994e093610037d2b6e080a367 5654 misc optional ski_1.3.2-2.diff.gz
 adfdecea781e9cc8b0cfacd2d6924118 1278518 devel optional ski_1.3.2-2_i386.deb

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

iD8DBQFHyIHuWDlSU/gp6ecRAgnzAJ0TRLhBYobBGMlwF2mtaXc/H6rE1gCgvX3g
o6PABfKGH20tL0R/Kkee+f8=
=zaH+
-END PGP SIGNATURE-


--- End Message ---

Processed: submitter 468184

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.10.16
> submitter 468184 [EMAIL PROTECTED]
Bug#468184: installation-reports
Changed Bug submitter from Magnus Berg <[EMAIL PROTECTED]> to [EMAIL PROTECTED]
(By the way, that Bug is currently marked as done.)

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#468404: iodine_0.4.1-2(hppa/unstable): FTBFS: test failure

[gregor herrmann]

On Fri, 29 Feb 2008 02:12:02 +0100, Frank Lichtenheld wrote:

> > Do you happen to have any idea what's going on here? AFAICS it's
> > something hppa specific ...
> No specific idea, no. If you want to debug this I can offer you SSH
> access to my HPPA machine.

Thanks for the offer, I'll contact you in private mail for arranging
the details.

Cheers,
gregor 
-- 
 .''`.   http://info.comodo.priv.at/ | gpg key ID: 0x00F3CFE4
 : :' :  debian: the universal operating system - http://www.debian.org/
 `. `'   member of https://www.vibe.at/ | how to reply: http://got.to/quote/
   `-NP: Tom Waits: Christmas Card From A Hooker In Minneapolis


signature.asc
Description: Digital signature

Bug#464013: libghc6-missingh-dev: Fails to install.

[John Goerzen]

On Fri February 29 2008 1:59:34 pm Kurt Roeckx wrote:

>
> I want to repeat that request.  Atleast make sure that packages end up
> in such a state that they can be removed.
>
>
> Kurt



I have forwarded this, and an explanation, to the debian-haskell list so we 
can discuss that and see if we can come up with a better solution.  I will 
also upload a new MissingH shortly.  Thanks,

-- John



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#468676: FTBFS on arm, (armel) ,mips, mipsel

[Riku Voipio]

Package: kdesvn
Version: 0.14.2-2
Severity: serious

-snip-
[ 67%] Building CXX object
src/svnfrontend/CMakeFiles/svnfrontend.dir/editpropsdlg.o
/build/buildd/kdesvn-0.14.2/obj-arm-linux-gnu/src/svnfrontend/editpropsdlg.cpp:123:42:
warning: no newline at end of file
/build/buildd/kdesvn-0.14.2/obj-arm-linux-gnu/src/svnfrontend/editpropsdlg.cpp:123:
error: expected `}' at end of input
/build/buildd/kdesvn-0.14.2/obj-arm-linux-gnu/src/svnfrontend/editpropsdlg.cpp:123:
error: expected ',' or ';' at end of input
make[3]: *** [src/svnfrontend/CMakeFiles/svnfrontend.dir/editpropsdlg.o]
Error 1
-snip-

On mips logs there is also mention of unsupported -fstack-protector
call.

http://buildd.debian.org/fetch.cgi?pkg=kdesvn&arch=arm&ver=0.14.2-2&stamp=1204082636&file=log&as=raw

http://buildd.debian.org/fetch.cgi?pkg=kdesvn&arch=armel&ver=0.14.2-2&stamp=1204321305&file=log&as=raw

http://buildd.debian.org/fetch.cgi?pkg=kdesvn&arch=mips&ver=0.14.2-2&stamp=1204207848&file=log&as=raw

http://buildd.debian.org/fetch.cgi?pkg=kdesvn&arch=mipsel&ver=0.14.2-2&stamp=1204102099&file=log&as=raw

-- 
"rm -rf" only sounds scary if you don't have backups


signature.asc
Description: Digital signature

Bug#468664: claws-mail: SEGFAULTs causing a kernel Oops

[David Paleino]

This happens also with a fresh configuration (still with 3.3.1).

I'll try to reproduce with other versions.

(I know my kernel is tainted -- see that "G" in the message I pasted
before -- but I currently don't have any non-free module loaded. I'll
investigate if this tainting might cause the Oops)

David

-- 
 . ''`.  Debian maintainer | http://wiki.debian.org/DavidPaleino
 : :'  : Linuxer #334216 --|-- http://www.hanskalabs.net/
 `. `'`  GPG: 1392B174 | http://snipr.com/qa_page
   `-   2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174



signature.asc
Description: Questa è una parte del messaggio	firmata digitalmente

Bug#468673: libmlt-data: fails to replace files from libmlt0.2.4

[Yann Dirson]

Package: libmlt-data
Version: 0.2.4-1
Severity: serious

Unpacking libmlt-data (from .../libmlt-data_0.2.4-1_all.deb) ...
dpkg: error processing /var/cache/apt/archives/libmlt-data_0.2.4-1_all.deb 
(--unpack):
 trying to overwrite `/usr/share/mlt/profiles/svcd_ntsc_wide', which is also in 
package libmlt0.2.4
dpkg-deb: subprocess paste killed by signal (Broken pipe)


-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (90, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.23.8-smp (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=french (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#468184: marked as done (installation-reports)

[Debian Bug Tracking System]

Your message dated Fri, 29 Feb 2008 21:18:07 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#465737: fixed in xfsprogs 2.9.7-1
has caused the Debian Bug report #465737,
regarding installation-reports
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 [EMAIL PROTECTED]
immediately.)


-- 
465737: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465737
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---

Package: installation-reports

The problem in a few words: XFS filesystem fails to mount during install.

Boot method: CD

Image version: Modified "27-Feb-2008 10:10" at 
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso


Date: 27-Feb-2008 15:00 local Swedish time

Machine: Mainboard MSI K9N SLI Platinium
Processor: AMD Athlon 64 X2 6400+ Black Edition
Memory: 4 GB
Hard disk: Western Digital Caviar SE16 500GB SATA2

Partitions:
Filsystem  Typ1K-blockAnvänt Tillgängl Anv% Monterat på
/dev/sdb3  xfs 9757248   2604888   7152360  27% /
tmpfstmpfs 2026012 0   2026012   0% /lib/init/rw
udev tmpfs   10240   144 10096   2% /dev
tmpfstmpfs 2026012 0   2026012   0% /dev/shm
/dev/sdb6  xfs   456508488  4256 456504232   1% /backup
/dev/sda3  xfs   455086720  64910400 390176320  15% /home
/dev/sdb1  xfs 9757248  4256   9752992   1% /xtra1
/dev/sdb2  xfs 9757280  4256   9753024   1% /xtra2

lspci -nn
00:00.0 RAM memory [0500]: nVidia Corporation MCP55 Memory Controller 
[10de:0369] (rev a2)
00:01.0 ISA bridge [0601]: nVidia Corporation MCP55 LPC Bridge 
[10de:0360] (rev a3)

00:01.1 SMBus [0c05]: nVidia Corporation MCP55 SMBus [10de:0368] (rev a3)
00:02.0 USB Controller [0c03]: nVidia Corporation MCP55 USB Controller 
[10de:036c] (rev a1)
00:02.1 USB Controller [0c03]: nVidia Corporation MCP55 USB Controller 
[10de:036d] (rev a2)
00:04.0 IDE interface [0101]: nVidia Corporation MCP55 IDE [10de:036e] 
(rev a1)
00:05.0 IDE interface [0101]: nVidia Corporation MCP55 SATA Controller 
[10de:037f] (rev a3)
00:05.1 IDE interface [0101]: nVidia Corporation MCP55 SATA Controller 
[10de:037f] (rev a3)
00:05.2 IDE interface [0101]: nVidia Corporation MCP55 SATA Controller 
[10de:037f] (rev a3)
00:06.0 PCI bridge [0604]: nVidia Corporation MCP55 PCI bridge 
[10de:0370] (rev a2)
00:06.1 Audio device [0403]: nVidia Corporation MCP55 High Definition 
Audio [10de:0371] (rev a2)
00:08.0 Bridge [0680]: nVidia Corporation MCP55 Ethernet [10de:0373] 
(rev a3)
00:0a.0 PCI bridge [0604]: nVidia Corporation MCP55 PCI Express bridge 
[10de:0376] (rev a3)
00:0b.0 PCI bridge [0604]: nVidia Corporation MCP55 PCI Express bridge 
[10de:0374] (rev a3)
00:0c.0 PCI bridge [0604]: nVidia Corporation MCP55 PCI Express bridge 
[10de:0374] (rev a3)
00:0d.0 PCI bridge [0604]: nVidia Corporation MCP55 PCI Express bridge 
[10de:0378] (rev a3)
00:0e.0 PCI bridge [0604]: nVidia Corporation MCP55 PCI Express bridge 
[10de:0375] (rev a3)
00:0f.0 PCI bridge [0604]: nVidia Corporation MCP55 PCI Express bridge 
[10de:0377] (rev a3)
00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] K8 
[Athlon64/Opteron] HyperTransport Technology Configuration [1022:1100]
00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] K8 
[Athlon64/Opteron] Address Map [1022:1101]
00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] K8 
[Athlon64/Opteron] DRAM Controller [1022:1102]
00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] K8 
[Athlon64/Opteron] Miscellaneous Control [1022:1103]
01:00.0 Multimedia video controller [0400]: Brooktree Corporation Bt878 
Video Capture [109e:036e] (rev 11)
01:00.1 Multimedia controller [0480]: Brooktree Corporation Bt878 Audio 
Capture [109e:0878] (rev 11)
07:00.0 VGA compatible controller [0300]: nVidia Corporation GeForce 
8800 GT [10de:0611] (rev a2)


lspci -vnn
00:00.0 RAM memory [0500]: nVidia Corporation MCP55 Memory Controller 
[10de:0369] (rev a2)

Subsystem: Micro-Star International Co., Ltd. Unknown device [1462:7250]
Flags: bus master, 66MHz, fast devsel, latency 0
Capabilities: 

00:01.0 ISA bridge [0601]: nVidia Corporation MCP55 LPC Bridge 
[10de:0360] (rev a3)

Subsystem: Micro-Star International Co., Ltd. Unknown device [1462:7250]
Flags: bus master, 66MHz, fast devsel, latency 0
I/O ports at 2f00 [size=128]

00:01.1 SMBus [0c05]: nVidia Corporation MCP55 SMBus [10de:0368] (rev a3)
Subsystem: Micro-Star International Co., Ltd. Unknown device [1462:7250]
Flags: 66MHz, fast devsel, IRQ 11
I/O

Bug#465737: marked as done (Can't mount XFS partition on "/")

[Debian Bug Tracking System]

Your message dated Fri, 29 Feb 2008 21:18:07 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#468184: fixed in xfsprogs 2.9.7-1
has caused the Debian Bug report #468184,
regarding Can't mount XFS partition on "/"
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 [EMAIL PROTECTED]
immediately.)


-- 
468184: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468184
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: installation-reports

Boot method: CD
Image version: 
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-businesscard.iso
Date:  14-Feb-2008 10:07

Machine:Desktop PC - Clone
Processor:  Intel 2.4 ghz
Memory: 1 gb
Partitions:

/dev/sda1   ---> 21 gb XFS defined as / ( format and boot flag )
/dev/sda3   ---> 5 gb  XFS  defined as /home ( keep data )
/dev/sda5   ---> 2 gb XFS   defined as swap ( format )
/dev/sda6   ---> 53 gb XFS  defined as /data ( keep data )

Output of lspci -nn and lspci -vnn:

Base System Installation Checklist: E

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

Comments/Problems:

After doing the manual partitioning as indicated above, the system
can't mount the "/" ( /dev/sda1 ) as XFS.  But if I define that
partition as JFS it worked ok.


   Regards.
   Facundo.
   Buenos Aires - Argentina


--- End Message ---
--- Begin Message ---
Source: xfsprogs
Source-Version: 2.9.7-1

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

xfslibs-dev_2.9.7-1_amd64.deb
  to pool/main/x/xfsprogs/xfslibs-dev_2.9.7-1_amd64.deb
xfsprogs-udeb_2.9.7-1_amd64.udeb
  to pool/main/x/xfsprogs/xfsprogs-udeb_2.9.7-1_amd64.udeb
xfsprogs_2.9.7-1.dsc
  to pool/main/x/xfsprogs/xfsprogs_2.9.7-1.dsc
xfsprogs_2.9.7-1.tar.gz
  to pool/main/x/xfsprogs/xfsprogs_2.9.7-1.tar.gz
xfsprogs_2.9.7-1_amd64.deb
  to pool/main/x/xfsprogs/xfsprogs_2.9.7-1_amd64.deb



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 [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nathan Scott <[EMAIL PROTECTED]> (supplier of updated xfsprogs 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 [EMAIL PROTECTED])


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sat, 01 Mar 2008 06:24:21 +1100
Source: xfsprogs
Binary: xfsprogs-udeb xfslibs-dev xfsprogs
Architecture: source amd64
Version: 2.9.7-1
Distribution: unstable
Urgency: high
Maintainer: Nathan Scott <[EMAIL PROTECTED]>
Changed-By: Nathan Scott <[EMAIL PROTECTED]>
Description: 
 xfslibs-dev - XFS filesystem-specific static libraries and headers
 xfsprogs   - Utilities for managing the XFS filesystem
 xfsprogs-udeb - A stripped-down version of xfsprogs, for debian-installer 
(udeb)
Closes: 289665 463810 465737 468184
Changes: 
 xfsprogs (2.9.7-1) unstable; urgency=high
 .
   * New upstream release.
   * Add -y fsck option (closes: #463810)
   * Lazy superblock counters not yet mkfs default (closes: #465737, #468184)
   * xfs_repair memory requirements significantly reduced (closes: #289665)
Files: 
 d8dfc709175932e234756265839d9849 578 admin optional xfsprogs_2.9.7-1.dsc
 02477b99e3c825f8bf5c85523d18b3cc 958400 admin optional xfsprogs_2.9.7-1.tar.gz
 e4d565a28d7ab19122b1d4e793c9ad5f 1360750 admin optional 
xfsprogs_2.9.7-1_amd64.deb
 175952075ac87cd258cf46dad0830870 302360 libdevel extra 
xfslibs-dev_2.9.7-1_amd64.deb
 ee3c8ab703c63f6244d46a1462ec8707 131924 debian-installer optional 
xfsprogs-udeb_2.9.7-1_amd64.udeb
Package-Type: udeb

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

iD8DBQFHyF/km8fl3HSIa2MRAg60AJ0ZynLn4zxgwSKHCtSxF0ESPRODNACfZZ2u
qhBaOpTrLNUik0TpketR9rA=
=l3fw
-END PGP SIGNATURE-


--- End Message ---

Bug#465737: marked as done (Can't mount XFS partition on "/")

[Debian Bug Tracking System]

Your message dated Fri, 29 Feb 2008 21:18:07 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#465737: fixed in xfsprogs 2.9.7-1
has caused the Debian Bug report #465737,
regarding Can't mount XFS partition on "/"
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 [EMAIL PROTECTED]
immediately.)


-- 
465737: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465737
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: installation-reports

Boot method: CD
Image version: 
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-businesscard.iso
Date:  14-Feb-2008 10:07

Machine:Desktop PC - Clone
Processor:  Intel 2.4 ghz
Memory: 1 gb
Partitions:

/dev/sda1   ---> 21 gb XFS defined as / ( format and boot flag )
/dev/sda3   ---> 5 gb  XFS  defined as /home ( keep data )
/dev/sda5   ---> 2 gb XFS   defined as swap ( format )
/dev/sda6   ---> 53 gb XFS  defined as /data ( keep data )

Output of lspci -nn and lspci -vnn:

Base System Installation Checklist: E

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

Comments/Problems:

After doing the manual partitioning as indicated above, the system
can't mount the "/" ( /dev/sda1 ) as XFS.  But if I define that
partition as JFS it worked ok.


   Regards.
   Facundo.
   Buenos Aires - Argentina


--- End Message ---
--- Begin Message ---
Source: xfsprogs
Source-Version: 2.9.7-1

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

xfslibs-dev_2.9.7-1_amd64.deb
  to pool/main/x/xfsprogs/xfslibs-dev_2.9.7-1_amd64.deb
xfsprogs-udeb_2.9.7-1_amd64.udeb
  to pool/main/x/xfsprogs/xfsprogs-udeb_2.9.7-1_amd64.udeb
xfsprogs_2.9.7-1.dsc
  to pool/main/x/xfsprogs/xfsprogs_2.9.7-1.dsc
xfsprogs_2.9.7-1.tar.gz
  to pool/main/x/xfsprogs/xfsprogs_2.9.7-1.tar.gz
xfsprogs_2.9.7-1_amd64.deb
  to pool/main/x/xfsprogs/xfsprogs_2.9.7-1_amd64.deb



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 [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nathan Scott <[EMAIL PROTECTED]> (supplier of updated xfsprogs 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 [EMAIL PROTECTED])


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sat, 01 Mar 2008 06:24:21 +1100
Source: xfsprogs
Binary: xfsprogs-udeb xfslibs-dev xfsprogs
Architecture: source amd64
Version: 2.9.7-1
Distribution: unstable
Urgency: high
Maintainer: Nathan Scott <[EMAIL PROTECTED]>
Changed-By: Nathan Scott <[EMAIL PROTECTED]>
Description: 
 xfslibs-dev - XFS filesystem-specific static libraries and headers
 xfsprogs   - Utilities for managing the XFS filesystem
 xfsprogs-udeb - A stripped-down version of xfsprogs, for debian-installer 
(udeb)
Closes: 289665 463810 465737 468184
Changes: 
 xfsprogs (2.9.7-1) unstable; urgency=high
 .
   * New upstream release.
   * Add -y fsck option (closes: #463810)
   * Lazy superblock counters not yet mkfs default (closes: #465737, #468184)
   * xfs_repair memory requirements significantly reduced (closes: #289665)
Files: 
 d8dfc709175932e234756265839d9849 578 admin optional xfsprogs_2.9.7-1.dsc
 02477b99e3c825f8bf5c85523d18b3cc 958400 admin optional xfsprogs_2.9.7-1.tar.gz
 e4d565a28d7ab19122b1d4e793c9ad5f 1360750 admin optional 
xfsprogs_2.9.7-1_amd64.deb
 175952075ac87cd258cf46dad0830870 302360 libdevel extra 
xfslibs-dev_2.9.7-1_amd64.deb
 ee3c8ab703c63f6244d46a1462ec8707 131924 debian-installer optional 
xfsprogs-udeb_2.9.7-1_amd64.udeb
Package-Type: udeb

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

iD8DBQFHyF/km8fl3HSIa2MRAg60AJ0ZynLn4zxgwSKHCtSxF0ESPRODNACfZZ2u
qhBaOpTrLNUik0TpketR9rA=
=l3fw
-END PGP SIGNATURE-


--- End Message ---

Bug#468184: marked as done (installation-reports)

[Debian Bug Tracking System]

Your message dated Fri, 29 Feb 2008 21:18:07 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#468184: fixed in xfsprogs 2.9.7-1
has caused the Debian Bug report #468184,
regarding installation-reports
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 [EMAIL PROTECTED]
immediately.)


-- 
468184: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468184
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---

Package: installation-reports

The problem in a few words: XFS filesystem fails to mount during install.

Boot method: CD

Image version: Modified "27-Feb-2008 10:10" at 
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso


Date: 27-Feb-2008 15:00 local Swedish time

Machine: Mainboard MSI K9N SLI Platinium
Processor: AMD Athlon 64 X2 6400+ Black Edition
Memory: 4 GB
Hard disk: Western Digital Caviar SE16 500GB SATA2

Partitions:
Filsystem  Typ1K-blockAnvänt Tillgängl Anv% Monterat på
/dev/sdb3  xfs 9757248   2604888   7152360  27% /
tmpfstmpfs 2026012 0   2026012   0% /lib/init/rw
udev tmpfs   10240   144 10096   2% /dev
tmpfstmpfs 2026012 0   2026012   0% /dev/shm
/dev/sdb6  xfs   456508488  4256 456504232   1% /backup
/dev/sda3  xfs   455086720  64910400 390176320  15% /home
/dev/sdb1  xfs 9757248  4256   9752992   1% /xtra1
/dev/sdb2  xfs 9757280  4256   9753024   1% /xtra2

lspci -nn
00:00.0 RAM memory [0500]: nVidia Corporation MCP55 Memory Controller 
[10de:0369] (rev a2)
00:01.0 ISA bridge [0601]: nVidia Corporation MCP55 LPC Bridge 
[10de:0360] (rev a3)

00:01.1 SMBus [0c05]: nVidia Corporation MCP55 SMBus [10de:0368] (rev a3)
00:02.0 USB Controller [0c03]: nVidia Corporation MCP55 USB Controller 
[10de:036c] (rev a1)
00:02.1 USB Controller [0c03]: nVidia Corporation MCP55 USB Controller 
[10de:036d] (rev a2)
00:04.0 IDE interface [0101]: nVidia Corporation MCP55 IDE [10de:036e] 
(rev a1)
00:05.0 IDE interface [0101]: nVidia Corporation MCP55 SATA Controller 
[10de:037f] (rev a3)
00:05.1 IDE interface [0101]: nVidia Corporation MCP55 SATA Controller 
[10de:037f] (rev a3)
00:05.2 IDE interface [0101]: nVidia Corporation MCP55 SATA Controller 
[10de:037f] (rev a3)
00:06.0 PCI bridge [0604]: nVidia Corporation MCP55 PCI bridge 
[10de:0370] (rev a2)
00:06.1 Audio device [0403]: nVidia Corporation MCP55 High Definition 
Audio [10de:0371] (rev a2)
00:08.0 Bridge [0680]: nVidia Corporation MCP55 Ethernet [10de:0373] 
(rev a3)
00:0a.0 PCI bridge [0604]: nVidia Corporation MCP55 PCI Express bridge 
[10de:0376] (rev a3)
00:0b.0 PCI bridge [0604]: nVidia Corporation MCP55 PCI Express bridge 
[10de:0374] (rev a3)
00:0c.0 PCI bridge [0604]: nVidia Corporation MCP55 PCI Express bridge 
[10de:0374] (rev a3)
00:0d.0 PCI bridge [0604]: nVidia Corporation MCP55 PCI Express bridge 
[10de:0378] (rev a3)
00:0e.0 PCI bridge [0604]: nVidia Corporation MCP55 PCI Express bridge 
[10de:0375] (rev a3)
00:0f.0 PCI bridge [0604]: nVidia Corporation MCP55 PCI Express bridge 
[10de:0377] (rev a3)
00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] K8 
[Athlon64/Opteron] HyperTransport Technology Configuration [1022:1100]
00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] K8 
[Athlon64/Opteron] Address Map [1022:1101]
00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] K8 
[Athlon64/Opteron] DRAM Controller [1022:1102]
00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] K8 
[Athlon64/Opteron] Miscellaneous Control [1022:1103]
01:00.0 Multimedia video controller [0400]: Brooktree Corporation Bt878 
Video Capture [109e:036e] (rev 11)
01:00.1 Multimedia controller [0480]: Brooktree Corporation Bt878 Audio 
Capture [109e:0878] (rev 11)
07:00.0 VGA compatible controller [0300]: nVidia Corporation GeForce 
8800 GT [10de:0611] (rev a2)


lspci -vnn
00:00.0 RAM memory [0500]: nVidia Corporation MCP55 Memory Controller 
[10de:0369] (rev a2)

Subsystem: Micro-Star International Co., Ltd. Unknown device [1462:7250]
Flags: bus master, 66MHz, fast devsel, latency 0
Capabilities: 

00:01.0 ISA bridge [0601]: nVidia Corporation MCP55 LPC Bridge 
[10de:0360] (rev a3)

Subsystem: Micro-Star International Co., Ltd. Unknown device [1462:7250]
Flags: bus master, 66MHz, fast devsel, latency 0
I/O ports at 2f00 [size=128]

00:01.1 SMBus [0c05]: nVidia Corporation MCP55 SMBus [10de:0368] (rev a3)
Subsystem: Micro-Star International Co., Ltd. Unknown device [1462:7250]
Flags: 66MHz, fast devsel, IRQ 11
I/O

Bug#468664: claws-mail: SEGFAULTs causing a kernel Oops

[David]

Package: claws-mail
Version: 3.3.1-1
Severity: grave
Justification: renders package unusable

Hi,
today, suddenly [1], claws-mail started hanging, outputting a strange
message on the console:

---8<---
Feb 29 21:15:54 pingu kernel: BUG: unable to handle kernel NULL
pointer dereference at virtual address 003c
Feb 29 21:15:54 pingu kernel:  printing eip:
Feb 29 21:15:54 pingu kernel: c016fd4d
Feb 29 21:15:54 pingu kernel: *pde = 
Feb 29 21:15:54 pingu kernel: Oops:  [#4]
Feb 29 21:15:54 pingu kernel: SMP
Feb 29 21:15:54 pingu kernel: Modules linked in: i915 drm ipv6
coretemp loop snd_hda_intel snd_pcm_oss snd_mixer_oss snd_pcm
snd_timer snd_page_alloc
snd_hwdep battery container ac video output button snd tsdev evdev
soundcore intel_agp agpgart psmouse joydev serio_raw rtc pcspkr
reiserfs ide_cd
cdrom usbhid hid piix generic sd_mod usb_storage ide_core ata_generic
ahci uhci_hcd ehci_hcd libata scsi_mod e1000 usbcore thermal processor
fan
Feb 29 21:15:54 pingu kernel: CPU:0
Feb 29 21:15:54 pingu kernel: EIP:
0060:[loop:vfs_getattr+0x30/0x15ef7]Tainted: G  D VLI
Feb 29 21:15:54 pingu kernel: EFLAGS: 00010246   (2.6.23-1-686 #1)
Feb 29 21:15:54 pingu kernel: EIP is at vfs_getattr+0x30/0x53
Feb 29 21:15:54 pingu kernel: eax:    ebx: c000fe60   ecx:
c0337180   edx: c0363c6c
Feb 29 21:15:54 pingu kernel: esi: c0363c6c   edi: e59fff04   ebp:
e59fff64   esp: e59ffee8
Feb 29 21:15:54 pingu kernel: ds: 007b   es: 007b   fs: 00d8  gs: 0033  ss: 0068
Feb 29 21:15:54 pingu kernel: Process claws-mail (pid: 10965,
ti=e59fe000 task=f3140070 task.ti=e59fe000)
Feb 29 21:15:54 pingu kernel: Stack: dfff18c0  e59fff64
e59fff04 e59fe000 c016fe34 e59fff04 c0363c6c
Feb 29 21:15:54 pingu kernel:dfff18c0 03e8 
 0001 0001  1000
Feb 29 21:15:54 pingu kernel:0008  47c092b2
 46f688a4  478a772a 
Feb 29 21:15:54 pingu kernel: Call Trace:
Feb 29 21:15:54 pingu kernel:  [vfs_stat_fd+0x2e/0x40] vfs_stat_fd+0x2e/0x40
Feb 29 21:15:54 pingu kernel:
[request_standard_resources+0x258/0x306]
request_standard_resources+0x258/0x306
Feb 29 21:15:54 pingu kernel:  [sys_stat64+0xf/0x23] sys_stat64+0xf/0x23
Feb 29 21:15:54 pingu kernel:  [shrink_page_list+0x3c8/0x4e8]
shrink_page_list+0x3c8/0x4e8
Feb 29 21:15:54 pingu kernel:  [snd_pcm:getnstimeofday+0x30/0x7d5f]
getnstimeofday+0x30/0xb6
Feb 29 21:15:54 pingu kernel:  [sys_time+0xa/0x2e] sys_time+0xa/0x2e
Feb 29 21:15:54 pingu kernel:  [sysenter_past_esp+0x6b/0xa1]
sysenter_past_esp+0x6b/0xa1
Feb 29 21:15:54 pingu kernel:  ===
Feb 29 21:15:54 pingu kernel: Code: 89 d6 53 83 ec 04 89 04 24 8b 5a
0c f6 83 41 01 00 00 02 75 10 8b 0d 84 cf 3c c0 ff 91 c4 00 00 00 85
c0 75 23 8b
83 94 00 00 00 <8b> 78 3c 85 ff 74 0b 8b 04 24 89 e9 89 f2 ff d7 eb 0b 89 d8 89
Feb 29 21:15:54 pingu kernel: EIP: [loop:vfs_getattr+0x30/0x15ef7]
vfs_getattr+0x30/0x53 SS:ESP 0068:e59ffee8
--->8---

(this is what appears in /var/log/syslog)

I've then installed claws-mail-dbg, and ran `gdb claws-mail'. Here I got quite
the same messages, with no additional information available :( :

---8<---
(gdb) run
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: /usr/bin/claws-mail
[Thread debugging using libthread_db enabled]
[New Thread 0xb6c01740 (LWP 11784)]

Message from [EMAIL PROTECTED] at Fri Feb 29 21:24:55 2008 ...
pingu kernel: Oops:  [#8]

Message from [EMAIL PROTECTED] at Fri Feb 29 21:24:55 2008 ...
pingu kernel: SMP

Message from [EMAIL PROTECTED] at Fri Feb 29 21:24:55 2008 ...
pingu kernel: CPU:0

Message from [EMAIL PROTECTED] at Fri Feb 29 21:24:55 2008 ...
pingu kernel: EIP:0060:[loop:vfs_getattr+0x30/0x15ef7]Tainted:
G  D VLI

Message from [EMAIL PROTECTED] at Fri Feb 29 21:24:55 2008 ...
pingu kernel: EFLAGS: 00010246   (2.6.23-1-686 #1)

Message from [EMAIL PROTECTED] at Fri Feb 29 21:24:55 2008 ...
pingu kernel: EIP is at vfs_getattr+0x30/0x53

Message from [EMAIL PROTECTED] at Fri Feb 29 21:24:55 2008 ...
pingu kernel: eax:    ebx: c000fe60   ecx: c0337180   edx: c0363c6c

Message from [EMAIL PROTECTED] at Fri Feb 29 21:24:55 2008 ...
pingu kernel: esi: c0363c6c   edi: e5073f04   ebp: e5073f64   esp: e5073ee8

Message from [EMAIL PROTECTED] at Fri Feb 29 21:24:55 2008 ...
pingu kernel: ds: 007b   es: 007b   fs: 00d8  gs: 0033  ss: 0068

Message from [EMAIL PROTECTED] at Fri Feb 29 21:24:55 2008 ...
pingu kernel: Process claws-mail (pid: 11784, ti=e5072000
task=e7d44750 task.ti=e5072000)

Message from [EMAIL PROTECTED] at Fri Feb 29 21:24:55 2008 ...
pingu kernel:dfff18c0 03e8   0001
0001  1000

Message from [EMAIL PROTECTED] at Fri Feb 29 21:24:55 2008 ...
pingu kernel:0008  47c092b2  46f688a4
 478a772a 

Message from [EMAIL PROTECTED] at Fri Feb 29 21:24:55 2008 ...
pingu kernel: Call Tra

Bug#406986: Upgrade B2evolution 0.9.2 to 1.10.2

[Arnaud Guiton]

Hi,


Emilio wrote:

> In fact, I guess the package should be orphaned and removed from Debian
> if a new maintainer doesn't step up, as Xavier Luthi (the original
> maintainer) is not around (I didn't see him in mentors either).

While I agree that the package is in a pretty bad shape, I think
completely removing it from Debian would be a pity :-/

I maintained the first versions of this package but had to let Xavier
take it over because I hadn't enough time to work on it.
However, if Xavier does not respond and/or nobody wants to take care of
packaging a new version (to be in sync with upstream), I'd agree to do
it. I would not be able to do that before the end of April, though, so
that could be a problem...


Cheers,

-- 
Arnaud


signature.asc
Description: Digital signature

Processed: your mail

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 465733 important
Bug#465733: xfsprogs: xfs_check SEGV
Severity set to `important' from `critical'

> tags 465733 upstream
Bug#465733: xfsprogs: xfs_check SEGV
There were no tags set.
Tags added: upstream

> tags 303388 upstream
Bug#303388: xfs_growfs: Errors on a AMD64 machine running i386 sarge
There were no tags set.
Tags added: upstream

> close 303388
Bug#303388: xfs_growfs: Errors on a AMD64 machine running i386 sarge
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug closed, send any further explanations to Matthias Julius <[EMAIL PROTECTED]>

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#464013: libghc6-missingh-dev: Fails to install.

[Kurt Roeckx]

found 464013 1.0.0.1
thanks

On Mon, Feb 04, 2008 at 06:53:34PM +0100, Kurt Roeckx wrote:
> Package: libghc6-missingh-dev
> Version: 1.0.0.0
> Severity: serious
> 
> Hi,
> 
> Your package is failing to install with the following error:
> Setting up libghc6-missingh-dev (1.0.0.0) ...
> Reading package info from 
> "/usr/lib/haskell-packages/ghc6/lib/MissingH-1.0.0/installed-pkg-config" ... 
> done.
> ghc-pkg: dependency regex-compat-0.91 doesn't exist (use --force to override)
> dpkg: error processing libghc6-missingh-dev (--configure):
>  subprocess post-installation script returned error exit status 1
> Errors were encountered while processing:
>  libghc6-missingh-dev
> E: Sub-process /usr/bin/dpkg returned an error code (1)

Now it's failing to install with:
Setting up libghc6-missingh-dev (1.0.0.1) ...
Reading package info from 
"/usr/lib/haskell-packages/ghc6/lib/MissingH-1.0.0/installed-pkg-config" ...  
done.
ghc-pkg: dependency hslogger-1.0.4 doesn't exist (use --force to override)
dpkg: error processing libghc6-missingh-dev (--configure):
 subprocess post-installation script returned error exit status 1

> And then fail to remove with:
> Removing libghc6-missingh-dev ...
> ghc-pkg: cannot find package MissingH-1.0.0
> dpkg: error processing libghc6-missingh-dev (--purge):
>  subprocess pre-removal script returned error exit status 1
> Reading package info from 
> "/usr/lib/haskell-packages/ghc6/lib/MissingH-1.0.0/installed-pkg-config" ... 
> done.
> ghc-pkg: dependency regex-compat-0.91 doesn't exist (use --force to override)
> dpkg: error while cleaning up:
>  subprocess post-installation script returned error exit status 1

And fails to remove with:
Removing libghc6-hslogger-dev ...
Saving old package config file... done.
Writing new package config file... done.
Removing libghc6-hunit-dev ...
Saving old package config file... done.
Writing new package config file... done.
Removing libghc6-missingh-dev ...
ghc-pkg: cannot find package MissingH-1.0.0
dpkg: error processing libghc6-missingh-dev (--purge):
 subprocess pre-removal script returned error exit status 1
Reading package info from 
"/usr/lib/haskell-packages/ghc6/lib/MissingH-1.0.0/installed-pkg-config" ...  
done.
ghc-pkg: dependency HUnit-1.2.0.0 doesn't exist (use --force to override)
dpkg: error while cleaning up:
 subprocess post-installation script returned error exit status 1


> Pretty please make some kind of policy to avoid such errors in the
> future.  I had to file too many bugs for such problems.

I want to repeat that request.  Atleast make sure that packages end up
in such a state that they can be removed.


Kurt




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: Re: libghc6-missingh-dev: Fails to install.

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> found 464013 1.0.0.1
Bug#464013: libghc6-missingh-dev: Fails to install.
Bug marked as found in version 1.0.0.1 and reopened.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#465733: Updating bug status

[nscott]

Hi,

Just a quick note to say I'll be downgrading the severity on this bug - as
per
the previous email on the bug, xfs_repair can fix the FS damage.  In the long
run, theres also discussion (upstream) of replacing xfs_check entirely by an
"xfs_repair -n" wrapper, which would resolve this issue entirely (xfs_check
has other issues beyond this one, in particular its memory footprint can be
extreme compared to current xfs_repair).   But, thats not on the immediate
horizon as yet.

cheers.

Bug#468429: slime: Error on startup

[Luca Capello]

forcemerge 468087 468429
thanks

Hello!

On Thu, 28 Feb 2008 22:54:56 +0100, Liam Healy wrote:
> I have found that the latest version of slime will not start up.  I
> posted to the slime mailing list and got this response from Helmut
> Eller:

Liam, as I already suggested you at [1], before submitting new bugs can
you check if they aren't already present in the Debian Bug Tracking
System (BTS), please?

This is a duplicate for bug #468087 [2]: merging the two, then.

Thx, bye,
Gismo / Luca

Footnotes: 
[1] http://common-lisp.net/pipermail/slime-devel/2008-February/007123.html
[2] http://bugs.debian.org/468087



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#404001: file conflict between perftools0_tau and libgoogle

[Michael Mende]

Sorry, one changed file was forgotten:
- debian/libgoogle-perftools0.manpages

On Fri, Feb 29, 2008 at 08:02:23PM +0100, Michael Mende wrote:
> Tags: + patch
> 
> Hello Daigo,
> 
> My package pound depends on libgoogle-perftools0. For entering lenny it
> is necessary that you fix this bug.
> 
> Attached are the suggested changed/new files:
> - debian/libgoogle-perftools0.docs
> - debian/README.Debian
> - debian/rules

-- 
Kind Regards,
 Michael Mende

http://www.menole.net/
debian/tmp/usr/share/man/man1/google-pprof.1

Bug#468087: [slime-devel] Re: Debian unstable version broken

[Luca Capello]

Hello!

On Thu, 28 Feb 2008 15:47:33 +0100, Helmut Eller wrote:
> * Liam Healy [2008-02-27 23:26+0100] writes:
>
>> Before I file a bug report with Debian I thought I'd ask here to see
>> if anybody knew about this, if there is a workaround etc.

Liam: please, either directly report it to Debian first [1] or, better,
check if it hasn't been reported yet: it's bug #468087 [2] (cc:ing the
submitter and the bug report as well).

> This seems to be Debian specific.  The missing function
> UNIQUE-DIRECTORY-NAME is now called UNIQUE-DIR-NAME.

Indeed, thank you for having checked that.  However, it seems that
nothing about this change is in the ChangeLog nor in the CVS commit for
slime/swank-loader.lisp [3]:

=
revision 1.78
date: 2008-02-16 20:26:22 +0100;  author: heller;  state: Exp;  lines: +54 -60
Split loading and initialization (again).

* swank-loader.lisp (init): New.  Delete old packages only if
explicitly requested.  Also, if the swank package already exists
don't load swank again.
(setup): New function.

* swank.lisp (setup): New function.  Moved over here from
swank-loader.lisp.

* slime.el (slime-init-command): Call swank-loader:init.

In the REPL, mark the trailing newline also as input.

* slime.el (slime-repl-send-input): Mark the newline with
the 'slime-repl-old-input property.
(slime-repl-grab-old-input): Strip the newline.
=

> Peter Van Eynde should probably set *FASL-DIRECTORY* instead of
> hard-coding the paths.

Thank you for the advice, I'll check later about that (FWIW, SLIME is
now in team maintenance [4]).  For the moment, the fix is easy and,
obviously, Debian specific:

--8<---cut here---start->8---
--- swank-loader.lisp.ORG   2008-02-28 18:28:21.0 +0100
+++ swank-loader.lisp   2008-02-28 18:30:21.0 +0100
@@ -123,7 +123,7 @@
   (let ((cfp (compile-file-pathname src-pathname)))
 (merge-pathnames (make-pathname 
   :directory
-  `(:relative "swank" "fasl" ,(unique-directory-name))
+  `(:relative "swank" "fasl" ,(unique-dir-name))
   :name (pathname-name cfp)
   :type (pathname-type cfp))
  (clc:calculate-fasl-root
--8<---cut here---end--->8---

Thx, bye,
Gismo / Luca

Footnotes: 
[1] http://bugs.debian.org
[2] http://bugs.debian.org/468087
[3] 
http://common-lisp.net/cgi-bin/viewcvs.cgi/slime/swank-loader.lisp?root=slime&r1=1.77&r2=1.78
[4] http://pkg-common-lisp.alioth.debian.org



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#468431: marked as done (depends on gnustep-core which you dropped)

[Debian Bug Tracking System]

Your message dated Fri, 29 Feb 2008 19:17:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#468431: fixed in meta-gnustep 7.1
has caused the Debian Bug report #468431,
regarding depends on gnustep-core which you dropped
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 [EMAIL PROTECTED]
immediately.)


-- 
468431: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468431
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---

Package: gnustep-games
Severity: grave
Version: 7
Justification: uninstallable

Hi,

gnustep-games depends on gnustep-core, which used to be built from  
meta-gnustep but was dropped and thus is not in the archive anymore.

Please fix it one way or the other.

Kind regards

T.


--- End Message ---
--- Begin Message ---
Source: meta-gnustep
Source-Version: 7.1

We believe that the bug you reported is fixed in the latest version of
meta-gnustep, which is due to be installed in the Debian FTP archive:

gnustep-core-devel_7.1_all.deb
  to pool/main/m/meta-gnustep/gnustep-core-devel_7.1_all.deb
gnustep-core-doc_7.1_all.deb
  to pool/main/m/meta-gnustep/gnustep-core-doc_7.1_all.deb
gnustep-devel_7.1_all.deb
  to pool/main/m/meta-gnustep/gnustep-devel_7.1_all.deb
gnustep-games_7.1_all.deb
  to pool/main/m/meta-gnustep/gnustep-games_7.1_all.deb
gnustep_7.1_all.deb
  to pool/main/m/meta-gnustep/gnustep_7.1_all.deb
meta-gnustep_7.1.dsc
  to pool/main/m/meta-gnustep/meta-gnustep_7.1.dsc
meta-gnustep_7.1.tar.gz
  to pool/main/m/meta-gnustep/meta-gnustep_7.1.tar.gz



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 [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Hubert Chathi <[EMAIL PROTECTED]> (supplier of updated meta-gnustep 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 [EMAIL PROTECTED])


-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160

Format: 1.7
Date: Fri, 29 Feb 2008 13:30:09 -0500
Source: meta-gnustep
Binary: gnustep-games gnustep gnustep-devel gnustep-core-doc gnustep-core-devel
Architecture: source all
Version: 7.1
Distribution: unstable
Urgency: low
Maintainer: Debian GNUstep maintainers <[EMAIL PROTECTED]>
Changed-By: Hubert Chathi <[EMAIL PROTECTED]>
Description: 
 gnustep- The GNUstep Development Environment -- user applications
 gnustep-core-devel - The GNUstep Development Environment -- core development
 gnustep-core-doc - The GNUstep Development Environment -- core documentation
 gnustep-devel - The GNUstep Development Environment -- development tools
 gnustep-games - The GNUstep Development Environment -- games
Closes: 468431
Changes: 
 meta-gnustep (7.1) unstable; urgency=low
 .
   * debian/control (gnustep-games): Drop dependency on gnustep-core, which
 was removed. (closes: #468431)
   * debian/README.Debian: Update package descriptions.  Add gnustep-core-doc.
Files: 
 8ee8e88cb87bead778e035144932eec0 687 x11 optional meta-gnustep_7.1.dsc
 78e26a1d205ca8693a300583a74cbdaa 3550 x11 optional meta-gnustep_7.1.tar.gz
 5444ee22078786fc51ee2e68df1ef3d3 3210 x11 optional 
gnustep-core-devel_7.1_all.deb
 2aed1fe68593629afcbe57f4ee5b1b78 2800 doc optional gnustep-core-doc_7.1_all.deb
 152e264480d27cd7fb8bd05c95d7949a 3042 x11 optional gnustep_7.1_all.deb
 8c4a47843922cac4e36b03c43229af73 2772 x11 optional gnustep-games_7.1_all.deb
 00d6fb8bda9fd78906c82a9c525a80a6 2876 x11 optional gnustep-devel_7.1_all.deb

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

iD8DBQFHyFgbrynHGRJLYfoRA0t7AJ9C0QJJOSvht5iVGzqIx6oEVyA7PgCdEKLb
noQxZgcMAdgJVWJZv5z3qC0=
=WWk4
-END PGP SIGNATURE-


--- End Message ---

Processed: Re: file conflicts between libgoogle-perftools0 and tau

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> tags 404001 + patch
Bug#404001: file conflict between perftools0_tau and libgoogle
There were no tags set.
Tags added: patch

> thankyou
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#404001: file conflict between perftools0_tau and libgoogle

[Michael Mende]

Tags: + patch

Hello Daigo,

My package pound depends on libgoogle-perftools0. For entering lenny it
is necessary that you fix this bug.

Attached are the suggested changed/new files:
- debian/libgoogle-perftools0.docs
- debian/README.Debian
- debian/rules

-- 
Kind Regards,
 Michael Mende

http://www.menole.net/
debian/README.Debian
#!/usr/bin/make -f
# -*- makefile -*-
# Sample debian/rules that uses debhelper.
# This file was originally written by Joey Hess and Craig Small.
# As a special exception, when this file is copied by dh-make into a
# dh-make output file, you may use that output file without restriction.
# This special exception was added by Craig Small in version 0.37 of dh-make.

# Uncomment this to turn on verbose mode.
#export DH_VERBOSE=1

include /usr/share/cdbs/1/rules/debhelper.mk
include /usr/share/cdbs/1/class/autotools.mk
include /usr/share/cdbs/1/rules/simple-patchsys.mk

DEB_DH_INSTALL_SOURCEDIR := $(DEB_DESTDIR)
DEB_INSTALL_CHANGELOGS_ALL := ChangeLog

install/libgoogle-perftools0::
mv $(DEB_DESTDIR)/usr/bin/pprof $(DEB_DESTDIR)/usr/bin/google-pprof
mv $(DEB_DESTDIR)/usr/share/man/man1/pprof.1 
$(DEB_DESTDIR)/usr/share/man/man1/google-pprof.1
sed -i -e "s/pprof/google-pprof/g" 
$(DEB_DESTDIR)/usr/share/man/man1/google-pprof.1
Because of a file conflict between tau and libgoogle-perftools [1]
the binary pprof is renamed as google-pprof,
its manpage in Debian is /usr/share/man/man1/google-pprof.1.gz.

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=404001.


signature.asc
Description: Digital signature

Bug#468202: openoffice.org-writer2latex: still occurring with 0.5-6

[Rene Engelhard]

Hi,

Hamish Moffatt wrote:
> Thanks. The manual says that if the old prerm fails, dpkg should try the
> same operation with the new prerm, which you said is fixed. I didn't see
> it try to do this.

The problem here might be that the prerm didn't actually fail in
the sense that it returned an exitcode != 0... But it failed to do its
job.

unopkg often returns 0 even if it failed..

Regards,

Rene

> 
> 
> Hamish
> -- 
> Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
> 
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#468644: fvwm-crystal: should this package be orphaned or removed?

[Barry deFreese]

Package: fvwm-crystal
Version: 3.0.3.dfsg1-0.1
Severity: serious
User: [EMAIL PROTECTED]
Usertags: proposed-orphan

Dear Maintainer,

While reviewing some packages, your package came up as a possible
candidate for orphan or removal from Debian, because:

* buggy.
* Maintainer appears inactive.  Last maintainer upload was 2006-06-02.
* Recommends xmms which is scheduled for removal.
* Relatively low popcon.

If you think that it should be removed from Debian instead of being
orphaned, please reply to this bug and tell so.

If you disagree and want to continue to maintain this package, please
close this bug and do an upload also fixing the other issues.
Also, you can study the possibility of taking co-maintainers.

If you agree that it should be orphaned, send the following commands
to [EMAIL PROTECTED] (replace nn with this bug's number):

severity nn normal
reassign nn wnpp
retitle nn O:  -- 
thanks

If you think it should be removed, send the following commands instead:

severity nn normal
reassign nn ftp.debian.org
retitle nn RM:  -- RoM; 
thanks

For more information, see
http://www.debian.org/doc/developers-reference/ch-pkgs.en.html#s-archive-manip
http://www.debian.org/devel/wnpp/

Thank you,

Barry deFreese





--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#468643: gnump3d: should this package be removed?

[Barry deFreese]

Package: gnump3d
Version: 3.0-2
Severity: serious
User: [EMAIL PROTECTED]
Usertags: proposed-removal

Dear Maintainer,

While reviewing some packages, your package came up as a possible
candidate for removal from Debian, because:

* buggy.
* no maintainer.
* Upstream has stopped development.
* Plenty of other alternatives.
* Relatively low popcon.

If you think that it should be orphaned instead of being removed from
Debian, please reply to this bug and tell so.

If you disagree and want to continue to maintain this package, please
just close this bug and do an upload also fixing the other issues.

If you agree that it should be removed, send the following commands to 
[EMAIL PROTECTED] (replace nn with this bug's number):


severity nn normal
reassign nn ftp.debian.org
retitle nn RM:  -- RoM;  
thanks


For more information, see
http://wiki.debian.org/ftpmaster_Removals
http://ftp-master.debian.org/removals.txt

Thank you,

Barry deFreese




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#462701: 462701: grub: savedefault menu.lst option results in unbootable system

[Ross Boylan]

I saw the note about this in the changelog, but can't find many other
signs of it.  My menu.lst doesn't have a savedefault variable (the
changelog says it exists), perhaps because that only appears in newly
generated ones?  And I don't see an indication in README.Debian.gz or
NEWS.Debian.gz about what the implications of using savedefault are.
Beyond the fact that it sometimes breaks, I still don't understand what
the issue is.

It might be helpful to put a few lines in README.Debian, and perhaps the
news too.

Ross



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#468642: runit: fails to install/upgrade

[Larry Doolittle]

Package: runit
Version: 1.8.0-4
Severity: critical
Justification: breaks unrelated software


Upgrading from runit 1.8.0-2 to 1.8.0-4 fails.
It seems to restart user processes, including the
one that is doing the upgrade.  The first time it
kicked me out of X.  It leaves dpkg/apt in an unusable
and unrecoverable state.

Symptom:

# apt-get upgrade
E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct 
the problem.
# dpkg --configure -a
Setting up runit (1.8.0-4) ...

Debian GNU/Linux lenny/sid recycle tty5

recycle login:

First, I would respectfully request advice on how to recover
apt/dpkg state.  Do you think downgrading to 1.8.0-2 will work?
Hmm, I left a non-runit-managed console around, maybe I can
try dpkg --configure -a from there.

Second, if there are any experiments I can do to isolate the
problem, let me know.  Nothing showed up in dmesg from the
process shown above.

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

Kernel: Linux 2.6.24-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

runit depends on no packages.

Versions of packages runit recommends:
pn  fgetty (no description available)

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#406986: Upgrade B2evolution 0.9.2 to 1.10.2

[Emilio Jesús Gallego Arias]

"Thijs Kinkhorst" <[EMAIL PROTECTED]> writes:

> Hi Emilio,
>
>> I would also consider removing it from stable, as I think the security
>> team cannot support it.
>
> The security team for stable often supports versions that are upstream
> abandoned. The question is whether such a thing is feasible for a package.
> In this case I see just one open security issue in the tracker, for which
> a patch is available. I therefore see no immediate need to remove the
> package from stable.

I think the problem with this package is that the version in
stable/testing is old enough so recent advisories about b2evolution
don't ever bother to check if the problem exists in 0.9.2. So then it is
a lot of work for the security team/users to check if any new advisory
applies to such and old version of the packages and then write/adapt a
patch. Who knows, security by obsolescence sometimes works. :)

I asked the removal from stable because IMVHO installing b2evolution as
is now in Etch is just asking for [security] trouble. The package is 9
major versions behind upstream! (0.9 -> 1.6 -> 1.8 -> 1.9 -> 1.10 ->
2.0 -> 2.1 -> 2.2 -> 2.3 -> 2.4)

I'm getting a lot of attacks in the logs for b2evolution, ATM none
didn't work as they targeted to higher versions of the software, but it
wouldn't surprise me if one day one of them works, given that
b2evolution is written in php and the attack patterns are similar. I
just switched all my installs.

In fact, I guess the package should be orphaned and removed from Debian
if a new maintainer doesn't step up, as Xavier Luthi (the original
maintainer) is not around (I didn't see him in mentors either).

Thanks a lot for your work,

Emilio



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#464096: poster: easy fix for KDE

[Daniel Hermann]

Hi Jim,

see this bug:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=379378

cheers,

Daniel

-- 
-
Daniel Hermann,  Institut fuer Theoretische Festkoerperphysik
Universitaet Karlsruhe  Tel: ++49 (0)721 608-7328
Postfach 6980   Fax: ++49 (0)721 608-7779
76128 Karlsruhe, Germany  email: [EMAIL PROTECTED]
-



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: gdancer removal

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 456681 normal
Bug#456681: gdancer: Should this package be removed?
Severity set to `normal' from `serious'

> reassign 456681 ftp.debian.org
Bug#456681: gdancer: Should this package be removed?
Bug reassigned from package `gdancer' to `ftp.debian.org'.

> retitle 456681 RM: gdancer -- RoQA; out of date, depends on xmms
Bug#456681: gdancer: Should this package be removed?
Changed Bug title to `RM: gdancer -- RoQA; out of date, depends on xmms' from 
`gdancer: Should this package be removed?'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: gkrellmms removal

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 456684 normal
Bug#456684: gkrellmms: Should this package be removed?
Severity set to `normal' from `serious'

> reassign 456684 ftp.debian.org
Bug#456684: gkrellmms: Should this package be removed?
Bug reassigned from package `gkrellmms' to `ftp.debian.org'.

> retitle 456684 RM: gkrellmms -- RoQA; out of date, depends on xmms
Bug#456684: gkrellmms: Should this package be removed?
Changed Bug title to `RM: gkrellmms -- RoQA; out of date, depends on xmms' from 
`gkrellmms: Should this package be removed?'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: libxmms-perl removal

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 456689 normal
Bug#456689: libxmms-perl: Should this package be removed?
Severity set to `normal' from `serious'

> reassign 456689 ftp.debian.org
Bug#456689: libxmms-perl: Should this package be removed?
Bug reassigned from package `libxmms-perl' to `ftp.debian.org'.

> retitle 456689 RM: libxmms-perl -- RoQA; out of date, depends on xmms
Bug#456689: libxmms-perl: Should this package be removed?
Changed Bug title to `RM: libxmms-perl -- RoQA; out of date, depends on xmms' 
from `libxmms-perl: Should this package be removed?'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: libxmms-ruby removal

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 456690 normal
Bug#456690: libxmms-ruby: Should this package be removed?
Severity set to `normal' from `serious'

> reassign 456690 ftp.debian.org
Bug#456690: libxmms-ruby: Should this package be removed?
Bug reassigned from package `libxmms-ruby' to `ftp.debian.org'.

> retitle 456690 RM: libxmms-ruby -- RoQA; out of date, depends on xmms
Bug#456690: libxmms-ruby: Should this package be removed?
Changed Bug title to `RM: libxmms-ruby -- RoQA; out of date, depends on xmms' 
from `libxmms-ruby: Should this package be removed?'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: pyxmms removal

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 456692 normal
Bug#456692: pyxmms: Should this package be removed?
Severity set to `normal' from `serious'

> reassign 456692 ftp.debian.org
Bug#456692: pyxmms: Should this package be removed?
Bug reassigned from package `pyxmms' to `ftp.debian.org'.

> retitle 456692 RM: pyxmms -- RoQA; out of date, depends on xmms
Bug#456692: pyxmms: Should this package be removed?
Changed Bug title to `RM: pyxmms -- RoQA; out of date, depends on xmms' from 
`pyxmms: Should this package be removed?'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#464530: marked as done (libghc6-ftphs-dev: postinst failure (regex-compat-0.71.0.1 not found))

[Debian Bug Tracking System]

Your message dated Fri, 29 Feb 2008 16:02:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#464530: fixed in ftphs 1.0.4.1
has caused the Debian Bug report #464530,
regarding libghc6-ftphs-dev: postinst failure (regex-compat-0.71.0.1 not found)
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 [EMAIL PROTECTED]
immediately.)


-- 
464530: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464530
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: libghc6-ftphs-dev
Version: 1.0.4.0
Severity: grave
Justification: renders package unusable


Hi,

here is the problem:

Setting up libghc6-ftphs-dev (1.0.4.0) ...
Reading package info from 
"/usr/lib/haskell-packages/ghc6/lib/ftphs-1.0.4/installed-pkg-config" ... done.
ghc-pkg: dependency regex-compat-0.71.0.1 doesn't exist (use --force to 
override)
dpkg: error processing libghc6-ftphs-dev (--configure):

Those packages are installed on the system:

ii  libghc6-regex-base-dev  0.93.1-3
GHC 6 library providing an API for regular e
ii  libghc6-regex-compat-dev0.91-1  
GHC 6 library provinding old Text.Regex infe
ii  libghc6-regex-posix-dev 0.93.1-1
GHC 6 library of the POSIX regex backend for

(this is probably a case of missing dependency).


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

Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libghc6-ftphs-dev depends on:
ii  ghc6  6.8.2-1GHC - the Glasgow Haskell Compilat
ii  libghc6-hslogger-dev  1.0.4  The Haskell Logging Framework, GHC
ii  libghc6-missingh-dev  1.0.0.1Library of utility functions for H
ii  libghc6-network-dev   2.1.0.0-1  Haskell network library for GHC

libghc6-ftphs-dev recommends no packages.

-- no debconf information

-- 
Laurent Bonnaud.
http://www.lis.inpg.fr/pages_perso/bonnaud/




--- End Message ---
--- Begin Message ---
Source: ftphs
Source-Version: 1.0.4.1

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

ftphs-doc_1.0.4.1_all.deb
  to pool/main/f/ftphs/ftphs-doc_1.0.4.1_all.deb
ftphs_1.0.4.1.dsc
  to pool/main/f/ftphs/ftphs_1.0.4.1.dsc
ftphs_1.0.4.1.tar.gz
  to pool/main/f/ftphs/ftphs_1.0.4.1.tar.gz
libghc6-ftphs-dev_1.0.4.1_i386.deb
  to pool/main/f/ftphs/libghc6-ftphs-dev_1.0.4.1_i386.deb



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 [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
John Goerzen <[EMAIL PROTECTED]> (supplier of updated ftphs 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 [EMAIL PROTECTED])


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Fri, 29 Feb 2008 09:54:08 -0600
Source: ftphs
Binary: ftphs-doc libghc6-ftphs-dev
Architecture: source all i386
Version: 1.0.4.1
Distribution: unstable
Urgency: low
Maintainer: John Goerzen <[EMAIL PROTECTED]>
Changed-By: John Goerzen <[EMAIL PROTECTED]>
Description: 
 ftphs-doc  - FTP Client and Server Library for Haskell, documentation
 libghc6-ftphs-dev - FTP Client and Server Library for Haskell, GHC package
Closes: 464530
Changes: 
 ftphs (1.0.4.1) unstable; urgency=low
 .
   * Rebuild to grab newer regex deps.  Closes: #464530.
Files: 
 ce91cfdd219c3154dc3d92ad7fe54ac4 800 devel optional ftphs_1.0.4.1.dsc
 410291b1c9889a74bc843b1b3ac84b60 49037 devel optional ftphs_1.0.4.1.tar.gz
 7bffd92df848aca879c507cc5f3ca2da 8116 doc optional ftphs-doc_1.0.4.1_all.deb
 0b274bbd6d459a6fcf1da11c6954c164 162046 devel optional 
libghc6-ftphs-dev_1.0.4.1_i386.deb

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

iD8DBQFHyCrhthyt9Q6V7ksRAsmBAJ0UYxOuNeqCbxIzLjL2k+sYJQjTwACeMXRQ
vVik1YHA8TZrPmcBMbdtkGA=
=Aj91
-END PGP SIGNATURE-


--- End Message ---

Bug#444375: marked as done (Broken on amd64 environment)

[Debian Bug Tracking System]

Your message dated Fri, 29 Feb 2008 16:02:05 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#444375: fixed in libunicode-japanese-perl 0.45-1
has caused the Debian Bug report #444375,
regarding Broken on amd64 environment
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 [EMAIL PROTECTED]
immediately.)


-- 
444375: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=444375
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: libunicode-japanese-perl
Version: 0.23-1
Severity: grave

 Unicode::Japanese perl module does not work on amd64 environment.

 It was fixed on upstream version 0.27. It was released 2 years ago
(2005), but debian package is not updated since 2004.

 Please update package, it is too old and buggy. Current upstreem
release is 0.37 (released at Mon Jul  3 10:38:01 JST 2006).

 If you don't have enough time to maintain this package now, I
wish to take over this package or to be co-maintainer for it.

-- 
ISHIKAWA Mutsumi
 <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>


--- End Message ---
--- Begin Message ---
Source: libunicode-japanese-perl
Source-Version: 0.45-1

We believe that the bug you reported is fixed in the latest version of
libunicode-japanese-perl, which is due to be installed in the Debian FTP 
archive:

libunicode-japanese-perl_0.45-1.diff.gz
  to 
pool/main/libu/libunicode-japanese-perl/libunicode-japanese-perl_0.45-1.diff.gz
libunicode-japanese-perl_0.45-1.dsc
  to pool/main/libu/libunicode-japanese-perl/libunicode-japanese-perl_0.45-1.dsc
libunicode-japanese-perl_0.45-1_amd64.deb
  to 
pool/main/libu/libunicode-japanese-perl/libunicode-japanese-perl_0.45-1_amd64.deb
libunicode-japanese-perl_0.45.orig.tar.gz
  to 
pool/main/libu/libunicode-japanese-perl/libunicode-japanese-perl_0.45.orig.tar.gz



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 [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Tatsuki Sugiura <[EMAIL PROTECTED]> (supplier of updated 
libunicode-japanese-perl 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 [EMAIL PROTECTED])


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 27 Feb 2008 16:32:28 +0900
Source: libunicode-japanese-perl
Binary: libunicode-japanese-perl
Architecture: source amd64
Version: 0.45-1
Distribution: unstable
Urgency: medium
Maintainer: Taku YASUI <[EMAIL PROTECTED]>
Changed-By: Tatsuki Sugiura <[EMAIL PROTECTED]>
Description: 
 libunicode-japanese-perl - Perl module for convert japanese encodings
Closes: 444375 467113
Changes: 
 libunicode-japanese-perl (0.45-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #444375)
   * Fix build problem with perl 5.10 (Closes: #467113)
Files: 
 cdf571018eadd30f67df928ece2c25a2 647 perl optional 
libunicode-japanese-perl_0.45-1.dsc
 8cf3fa0c3af751087e31b4d22437c562 165325 perl optional 
libunicode-japanese-perl_0.45.orig.tar.gz
 b215439fc5e3637837d8967deed4bf60 2004 perl optional 
libunicode-japanese-perl_0.45-1.diff.gz
 766a522ce53ce74f199181d22781de33 179518 perl optional 
libunicode-japanese-perl_0.45-1_amd64.deb

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

iD4DBQFHyCmqFwU5DuZsm7ARAlUIAJiu00hTG3kpum9yWTrauvrOEbxOAKDCtpFr
RUNL2CoED4qsjp1m2tH5rA==
=L8gm
-END PGP SIGNATURE-


--- End Message ---

Processed: xmms-blursk removal

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 456746 normal
Bug#456746: xmms-blursk: should this package be removed?
Severity set to `normal' from `serious'

> reassign 456746 ftp.debian.org
Bug#456746: xmms-blursk: should this package be removed?
Bug reassigned from package `xmms-blursk' to `ftp.debian.org'.

> retitle 456746 RM: xmms-blursk -- RoQA; out of date, depends on xmms
Bug#456746: xmms-blursk: should this package be removed?
Changed Bug title to `RM: xmms-blursk -- RoQA; out of date, depends on xmms' 
from `xmms-blursk: should this package be removed?'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#431745: marked as done (opensync-plugin-google-calendar: Fails to sync with google calendar with DateTime exception)

[Debian Bug Tracking System]

Your message dated Fri, 29 Feb 2008 16:02:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#431745: fixed in libopensync-plugin-google-calendar 0.22-3
has caused the Debian Bug report #431745,
regarding opensync-plugin-google-calendar: Fails to sync with google calendar 
with DateTime exception
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 [EMAIL PROTECTED]
immediately.)


-- 
431745: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=431745
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: opensync-plugin-google-calendar
Version: 0.19-2
Severity: grave
Tags: patch
Justification: renders package unusable


(I believe this applies to anyone using this plugin hence the severity)

Any attempt to synchronise using the google-calendar plugin will fail
with an exception:
__main__.DateConversionError: Invalid date/time

e.g:

[EMAIL PROTECTED]:~$ msynctool --sync mysink
Synchronizing group "mysink"
The previous synchronization was unclean. Slow-syncing
Member 1 of type google-calendar just connected
Member 2 of type kdepim-sync just connected
All clients connected or error
Received an entry libkcal-744074169.903 with data of size 4 from member
2. Changetype ADDED
Member 2 of type kdepim-sync just sent all changes
Traceback (most recent call last):
  File "/usr/lib/opensync/google-cal-helper", line 402, in ?
sys.exit(main(sys.argv))
  File "/usr/lib/opensync/google-cal-helper", line 394, in main
return fn(argv)
  File "/usr/lib/opensync/google-cal-helper", line 286, in oper_get_all
data = e.dumpOsync()
  File "/usr/lib/opensync/google-cal-helper", line 200, in dumpOsync
self.addElementContent(doc, event, 'DateStarted',
xsdateToOsync(self.dtstart))
  File "/usr/lib/opensync/google-cal-helper", line 118, in xsdateToOsync
raise DateConversionError("Invalid date/time: %s" % (s))
__main__.DateConversionError: Invalid date/time:
Member 1 of type google-calendar had an error while getting changes:
Helper exited abnormally
Member 1 of type google-calendar just disconnected
Member 2 of type kdepim-sync just disconnected
All clients have disconnected
The sync failed: Unable to read from one of the members
Error synchronizing: Unable to read from one of the members
Pipe closed! Exiting.
Pipe closed! Exiting.


Investigation reveals this is a known bug with a patch available. See:

   http://opensync.gforge.punktart.de/ticket/18

..for details, or indeed:

   
http://www.nabble.com/-PATCH--google-calendar-recurrency-support-p9781043.html

...For a different source.


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (200, 'stable'), (50, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.16.30.2006110301 (PREEMPT)
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) (ignored: LC_ALL set to 
en_GB)
Shell: /bin/sh linked to /bin/bash

Versions of packages opensync-plugin-google-calendar depends on:
ii  libc6  2.5-11GNU C Library: Shared libraries
ii  libglib2.0-0   2.12.12-1 The GLib library of C routines
ii  libopensync0   0.19-1.2  Synchronisation framework for emai
ii  libxml22.6.29.dfsg-1 GNOME XML library
ii  python 2.4.4-6   An interactive high-level object-o
ii  python-httplib20.2.0-2   A comprehensive HTTP client librar
ii  python-xml 0.8.4-7   XML tools for Python

opensync-plugin-google-calendar recommends no packages.

-- no debconf information
--- src/google-cal-helper.py~	2007-04-01 14:51:03.0 -0400
+++ src/google-cal-helper.py	2007-04-01 14:51:05.0 -0400
@@ -138,6 +138,41 @@
 	sys.stderr.write("xs to osync: %s => %s\n" % (s, r))
 	return r
 
+GDEND_RE = re.compile("DTEND;[^:]*:(\S+)")
+def gdRecurToEnd(recur):
+m = GDEND_RE.search(recur)
+if m is None:
+raise DateConversionError("failed to find end in \"%s\"" % recur)
+start = m.group(1)
+year = start[0:4]
+month = start[4:6]
+day = start[6:8]
+hour = start[9:11]
+min = start[11:13]
+sec = start[13:15]
+return "%s-%2s-%2sT%2s:%2s:%2s" % (year, month, day, hour, min, sec)
+
+GDSTART_RE = re.compile("DTSTART;[^:]*:(\S+)")
+def gdRecurToStart(recur):
+m = GDSTART_RE.search(recur)
+if m is None:
+raise DateConversionError("failed to find start in \"%s\"" % recur)
+start = m.group(1)
+year = start[0:4]
+month = start[4:6]
+day = start[6:8]
+hour = sta

Processed: xmms-fmradio removal

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 456700 normal
Bug#456700: xmms-fmradio: Should this package be removed?
Severity set to `normal' from `serious'

> reassign 456700 ftp.debian.org
Bug#456700: xmms-fmradio: Should this package be removed?
Bug reassigned from package `xmms-fmradio' to `ftp.debian.org'.

> retitle 456700 RM: xmms-fmradio -- RoQA; out of date, depends on xmms
Bug#456700: xmms-fmradio: Should this package be removed?
Changed Bug title to `RM: xmms-fmradio -- RoQA; out of date, depends on xmms' 
from `xmms-fmradio: Should this package be removed?'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: lirc-xmms-plugin removal

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 456691 normal
Bug#456691: lirc-xmms-plugin: Should this package be removed?
Severity set to `normal' from `serious'

> reassign 456691 ftp.debian.org
Bug#456691: lirc-xmms-plugin: Should this package be removed?
Bug reassigned from package `lirc-xmms-plugin' to `ftp.debian.org'.

> retitle 456691 RM: lirc-xmms-plugin -- RoQA; out of date, depends on xmms
Bug#456691: lirc-xmms-plugin: Should this package be removed?
Changed Bug title to `RM: lirc-xmms-plugin -- RoQA; out of date, depends on 
xmms' from `lirc-xmms-plugin: Should this package be removed?'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: xmms-mad removal

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 456709 normal
Bug#456709: xmms-mad: Should this package be removed?
Severity set to `normal' from `serious'

> reassign 456709 ftp.debian.org
Bug#456709: xmms-mad: Should this package be removed?
Bug reassigned from package `xmms-mad' to `ftp.debian.org'.

> retitle 456709 RM: xmms-mad -- RoQA; out of date, depends on xmms
Bug#456709: xmms-mad: Should this package be removed?
Changed Bug title to `RM: xmms-mad -- RoQA; out of date, depends on xmms' from 
`xmms-mad: Should this package be removed?'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: modplugxmms removal

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 456731 normal
Bug#456731: modplugxmms: Please switch to an XMMS alternative
Severity set to `normal' from `serious'

> reassign 456731 ftp.debian.org
Bug#456731: modplugxmms: Please switch to an XMMS alternative
Bug reassigned from package `modplugxmms' to `ftp.debian.org'.

> retitle 456731 RM: modplugxmms -- RoQA; out of date, depends on xmms
Bug#456731: modplugxmms: Please switch to an XMMS alternative
Changed Bug title to `RM: modplugxmms -- RoQA; out of date, depends on xmms' 
from `modplugxmms: Please switch to an XMMS alternative'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: xmms-mpg123-ja removal

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 456710 normal
Bug#456710: xmms-mpg123-ja: Should this package be removed?
Severity set to `normal' from `serious'

> reassign 456710 ftp.debian.org
Bug#456710: xmms-mpg123-ja: Should this package be removed?
Bug reassigned from package `xmms-mpg123-ja' to `ftp.debian.org'.

> retitle 456710 RM: xmms-mpg123-ja -- RoQA; out of date, depends on xmms
Bug#456710: xmms-mpg123-ja: Should this package be removed?
Changed Bug title to `RM: xmms-mpg123-ja -- RoQA; out of date, depends on xmms' 
from `xmms-mpg123-ja: Should this package be removed?'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#468562: marked as done (Does not include google-cal-helper)

[Debian Bug Tracking System]

Your message dated Fri, 29 Feb 2008 15:32:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#468562: fixed in libopensync-plugin-google-calendar 0.22-2
has caused the Debian Bug report #468562,
regarding Does not include google-cal-helper
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 [EMAIL PROTECTED]
immediately.)


-- 
468562: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468562
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---

Package: opensync-plugin-google-calendar
Version: 0.22-1
Severity: grave

--- Please enter the report below this line. ---
Attempting to use package, sync dies with:

$ msynctool --sync test3
Synchronizing group "test3"
Member 1 of type google-calendar just connected
Member 2 of type kdepim-sync just connected
All clients connected or error
Cannot exec plugin helper (/usr/lib/opensync/google-cal-helper)
Received an entry KOrganizer-1346183308.844 with data of size 4 from 
member 2 (kdepim-sync). Changetype ADDED
Received an entry libkcal-1177780015.316 with data of size 4 from member 
2 (kdepim-sync). Changetype ADDED

Member 2 of type kdepim-sync just sent all changes
Member 1 of type google-calendar had an error while getting changes: 
Helper exited abnormally

Member 1 of type google-calendar just disconnected
Member 2 of type kdepim-sync just disconnected
All clients have disconnected
The sync failed: Unable to read from one of the members
Error while synchronizing: Unable to read from one of the members

Looks like the package needs the google-cal-helper file.

--- System information. ---
Architecture: i386
Kernel: Linux 2.6.24-1-686

Debian Release: lenny/sid
500 unstable ftp.us.debian.org

--- Package information. ---
Depends (Version) | Installed
===-+-
libc6 (>= 2.7-1) | 2.7-8
libglib2.0-0 (>= 2.12.0) | 2.14.6-1
libopensync0 (>= 0.22) | 0.22-1
libxml2 (>= 2.6.27) | 2.6.31.dfsg-1
python | 2.4.4-6
python-httplib2 | 0.2.0-2
python-xml | 0.8.4-10



--- End Message ---
--- Begin Message ---
Source: libopensync-plugin-google-calendar
Source-Version: 0.22-2

We believe that the bug you reported is fixed in the latest version of
libopensync-plugin-google-calendar, which is due to be installed in the Debian 
FTP archive:

libopensync-plugin-google-calendar_0.22-2.diff.gz
  to 
pool/main/libo/libopensync-plugin-google-calendar/libopensync-plugin-google-calendar_0.22-2.diff.gz
libopensync-plugin-google-calendar_0.22-2.dsc
  to 
pool/main/libo/libopensync-plugin-google-calendar/libopensync-plugin-google-calendar_0.22-2.dsc
opensync-plugin-google-calendar_0.22-2_i386.deb
  to 
pool/main/libo/libopensync-plugin-google-calendar/opensync-plugin-google-calendar_0.22-2_i386.deb



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 [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Banck <[EMAIL PROTECTED]> (supplier of updated 
libopensync-plugin-google-calendar 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 [EMAIL PROTECTED])


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Fri, 29 Feb 2008 16:12:49 +0100
Source: libopensync-plugin-google-calendar
Binary: opensync-plugin-google-calendar
Architecture: source i386
Version: 0.22-2
Distribution: unstable
Urgency: low
Maintainer: Michael Banck <[EMAIL PROTECTED]>
Changed-By: Michael Banck <[EMAIL PROTECTED]>
Description: 
 opensync-plugin-google-calendar - Opensync Google Calendar plugin
Closes: 468562
Changes: 
 libopensync-plugin-google-calendar (0.22-2) unstable; urgency=low
 .
   * src/Makefile.am: Fix building/installing of the helper program;
 Closes: #468562.
   * reran aclocal/automake.
Files: 
 ffa0fb953be1571b1fdb5f06fdc6cbb7 869 libs optional 
libopensync-plugin-google-calendar_0.22-2.dsc
 0caa8425ab3e6de93640081ddf6ebc2b 28613 libs optional 
libopensync-plugin-google-calendar_0.22-2.diff.gz
 d380b0cb9ece5f3f8773937ebfd256f0 12892 libs optional 
opensync-plugin-google-calendar_0.22-2_i386.deb

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

iD8DBQFHyCJOmHaJYZ7RAb8RAujYAKDFxwKPya34fPGkppb/NxSpGYmJnACgk+1k
EW7snwXb+tEjiKBjltMIvfg=
=A7OW
-END PGP SIGNATURE-


--- End Message ---

Processed: xmms-infopipe removal

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 456704 normal
Bug#456704: xmms-infopipe: Should this package be removed?
Severity set to `normal' from `serious'

> reassign 456704 ftp.debian.org
Bug#456704: xmms-infopipe: Should this package be removed?
Bug reassigned from package `xmms-infopipe' to `ftp.debian.org'.

> retitle 456704 RM: xmms-infopipe -- RoQA; out of date, depends on xmms
Bug#456704: xmms-infopipe: Should this package be removed?
Changed Bug title to `RM: xmms-infopipe -- RoQA; out of date, depends on xmms' 
from `xmms-infopipe: Should this package be removed?'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: xmms-ladspa removal

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 456752 normal
Bug#456752: xmms-ladspa: should this package be removed?
Severity set to `normal' from `serious'

> reassign 456752 ftp.debian.org
Bug#456752: xmms-ladspa: should this package be removed?
Bug reassigned from package `xmms-ladspa' to `ftp.debian.org'.

> retitle 456752 RM: xmms-ladspa -- RoQA; out of date, depends on xmms
Bug#456752: xmms-ladspa: should this package be removed?
Changed Bug title to `RM: xmms-ladspa -- RoQA; out of date, depends on xmms' 
from `xmms-ladspa: should this package be removed?'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: xmms-msa removal

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 456711 normal
Bug#456711: xmms-msa: Should this package be removed?
Severity set to `normal' from `serious'

> reassign 456711 ftp.debian.org
Bug#456711: xmms-msa: Should this package be removed?
Bug reassigned from package `xmms-msa' to `ftp.debian.org'.

> retitle 456711 RM: xmms-msa -- RoQA; out of date, depends on xmms
Bug#456711: xmms-msa: Should this package be removed?
Changed Bug title to `RM: xmms-msa -- RoQA; out of date, depends on xmms' from 
`xmms-msa: Should this package be removed?'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: xmms-goodnight removal

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 456701 normal
Bug#456701: xmms is going away
Severity set to `normal' from `serious'

> reassign 456701 ftp.debian.org
Bug#456701: xmms is going away
Bug reassigned from package `xmms-goodnight' to `ftp.debian.org'.

> retitle 456701 RM: xmms-goodnight -- RoQA; out of date, depends on xmms
Bug#456701: xmms is going away
Changed Bug title to `RM: xmms-goodnight -- RoQA; out of date, depends on xmms' 
from `xmms is going away'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: xmms-kde removal

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 456707 normal
Bug#456707: xmms-kde: Should this package be removed?
Severity set to `normal' from `serious'

> reassign 456707 ftp.debian.org
Bug#456707: xmms-kde: Should this package be removed?
Bug reassigned from package `xmms-kde' to `ftp.debian.org'.

> retitle 456707 RM: xmms-kde -- RoQA; out of date, depends on xmms
Bug#456707: xmms-kde: Should this package be removed?
Changed Bug title to `RM: xmms-kde -- RoQA; out of date, depends on xmms' from 
`xmms-kde: Should this package be removed?'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: xmms-musepack removal

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 456712 normal
Bug#456712: xmms-musepack: Should this package be removed?
Severity set to `normal' from `serious'

> reassign 456712 ftp.debian.org
Bug#456712: xmms-musepack: Should this package be removed?
Bug reassigned from package `xmms-musepack' to `ftp.debian.org'.

> retitle 456712 RM: xmms-musepack -- RoQA; out of date, depends on xmms
Bug#456712: xmms-musepack: Should this package be removed?
Changed Bug title to `RM: xmms-musepack -- RoQA; out of date, depends on xmms' 
from `xmms-musepack: Should this package be removed?'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: qbble removal

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 456693 normal
Bug#456693: qbble: Should this package be removed?
Severity set to `normal' from `serious'

> reassign 456693 ftp.debian.org
Bug#456693: qbble: Should this package be removed?
Bug reassigned from package `qbble' to `ftp.debian.org'.

> retitle 456693 RM: qbble -- RoQA; out of date, depends on xmms
Bug#456693: qbble: Should this package be removed?
Changed Bug title to `RM: qbble -- RoQA; out of date, depends on xmms' from 
`qbble: Should this package be removed?'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: xmms-rplay removal

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 456753 normal
Bug#456753: xmms-rplay: should this package be removed?
Severity set to `normal' from `serious'

> reassign 456753 ftp.debian.org
Bug#456753: xmms-rplay: should this package be removed?
Bug reassigned from package `xmms-rplay' to `ftp.debian.org'.

> retitle 456753 RM: xmms-rplay -- RoQA; out of date, depends on xmms
Bug#456753: xmms-rplay: should this package be removed?
Changed Bug title to `RM: xmms-rplay -- RoQA; out of date, depends on xmms' 
from `xmms-rplay: should this package be removed?'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: xmms-scrobbler removal

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 456754 normal
Bug#456754: xmms-scrobbler: should this package be removed?
Severity set to `normal' from `serious'

> reassign 456754 ftp.debian.org
Bug#456754: xmms-scrobbler: should this package be removed?
Bug reassigned from package `xmms-scrobbler' to `ftp.debian.org'.

> retitle 456754 RM: xmms-scrobbler -- RoQA; out of date, depends on xmms
Bug#456754: xmms-scrobbler: should this package be removed?
Changed Bug title to `RM: xmms-scrobbler -- RoQA; out of date, depends on xmms' 
from `xmms-scrobbler: should this package be removed?'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: xmms-shell removal

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 456729 normal
Bug#456729: xmms-shell: Please move to use bmpx
Severity set to `normal' from `serious'

> reassign 456729 ftp.debian.org
Bug#456729: xmms-shell: Please move to use bmpx
Bug reassigned from package `xmms-shell' to `ftp.debian.org'.

> retitle 456729 RM: xmms-shell -- RoQA; out of date, depends on xmms
Bug#456729: xmms-shell: Please move to use bmpx
Changed Bug title to `RM: xmms-shell -- RoQA; out of date, depends on xmms' 
from `xmms-shell: Please move to use bmpx'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: xmms-skins removal

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 461740 normal
Bug#461740: xmms-skins: xmms is going away
Severity set to `normal' from `serious'

> reassign 461740 ftp.debian.org
Bug#461740: xmms-skins: xmms is going away
Bug reassigned from package `xmms-skins' to `ftp.debian.org'.

> retitle 461740 RM: xmms-skins -- RoQA; out of date, depends on xmms
Bug#461740: xmms-skins: xmms is going away
Changed Bug title to `RM: xmms-skins -- RoQA; out of date, depends on xmms' 
from `xmms-skins: xmms is going away'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: xmms-speex removal

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 456717 normal
Bug#456717: xmms-speex: Should this package be removed?
Severity set to `normal' from `serious'

> reassign 456717 ftp.debian.org
Bug#456717: xmms-speex: Should this package be removed?
Bug reassigned from package `xmms-speex' to `ftp.debian.org'.

> retitle 456717 RM: xmms-speex -- RoQA; out of date, depends on xmms
Bug#456717: xmms-speex: Should this package be removed?
Changed Bug title to `RM: xmms-speex -- RoQA; out of date, depends on xmms' 
from `xmms-speex: Should this package be removed?'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#468476: marked as done (newsbeuter: segfaults at startup)

[Debian Bug Tracking System]

Your message dated Fri, 29 Feb 2008 14:32:06 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#468476: fixed in newsbeuter 0.7-4
has caused the Debian Bug report #468476,
regarding newsbeuter: segfaults at startup
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 [EMAIL PROTECTED]
immediately.)


-- 
468476: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468476
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: newsbeuter
Version: 0.7-3+b1
Severity: grave
Justification: renders package unusable


Hi,

newsbeuter dies after today's unstable dist-upgrade:

[EMAIL PROTECTED]:~]$ CHECK_MALLOC_=2 newsbeuter
Démarrage newsbeuter 0.7...
Chargement de la configuration...fait.
Vidage du cache...fait.
Chargement des URLs depuis /home/xav/.newsbeuter/urls...fait.
Chargement des articles depuis le cache...*** glibc detected *** newsbeuter: 
free(): invalid pointer: 0x080f4058 ***
=== Backtrace: =
/lib/i686/cmov/libc.so.6[0xb7c40564]
/lib/i686/cmov/libc.so.6(cfree+0x96)[0xb7c42766]
newsbeuter[0x804ecac]
newsbeuter[0x80510b9]
newsbeuter[0x806f0f0]
newsbeuter[0x804d915]
/lib/i686/cmov/libc.so.6(__libc_start_main+0xe6)[0xb7be8456]
newsbeuter(__gxx_personality_v0+0x3fd)[0x804d601]
=== Memory map: 
08048000-080ce000 r-xp  03:05 131742 /usr/bin/newsbeuter
080ce000-080d1000 rwxp 00086000 03:05 131742 /usr/bin/newsbeuter
080d1000-08115000 rwxp 080d1000 00:00 0  [heap]
b660-b6621000 rwxp b660 00:00 0 
b6621000-b670 ---p b6621000 00:00 0 
b677b000-b677c000 ---p b677b000 00:00 0 
b677c000-b6f7c000 rwxp b677c000 00:00 0 
b6f7c000-b6f7d000 ---p b6f7c000 00:00 0 
b6f7d000-b777d000 rwxp b6f7d000 00:00 0 
b777d000-b78b7000 r-xp  03:05 551073 /usr/lib/locale/locale-archive
b78b7000-b78ba000 rwxp b78b7000 00:00 0 
b78ba000-b792 r-xp  03:05 454273 /usr/lib/libgcrypt.so.11.4.3
b792-b7922000 rwxp 00065000 03:05 454273 /usr/lib/libgcrypt.so.11.4.3
b7922000-b7925000 r-xp  03:05 457395 /usr/lib/libgpg-error.so.0.3.0
b7925000-b7926000 rwxp 2000 03:05 457395 /usr/lib/libgpg-error.so.0.3.0
b7926000-b7934000 r-xp  03:05 453419 /usr/lib/libtasn1.so.3.0.14
b7934000-b7935000 rwxp e000 03:05 453419 /usr/lib/libtasn1.so.3.0.14
b7935000-b7937000 r-xp  03:05 522504 /lib/libkeyutils-1.2.so
b7937000-b7938000 rwxp 1000 03:05 522504 /lib/libkeyutils-1.2.so
b7938000-b7939000 rwxp b7938000 00:00 0 
b7939000-b794 r-xp  03:05 458699 /usr/lib/libkrb5support.so.0.1
b794-b7941000 rwxp 6000 03:05 458699 /usr/lib/libkrb5support.so.0.1
b7941000-b79b4000 r-xp  03:05 217200 /usr/lib/libgnutls.so.26.1.3
b79b4000-b79ba000 rwxp 00072000 03:05 217200 /usr/lib/libgnutls.so.26.1.3
b79ba000-b79d r-xp  03:05 453473 /usr/lib/libsasl2.so.2.0.22
b79d-b79d1000 rwxp 00015000 03:05 453473 /usr/lib/libsasl2.so.2.0.22
b79d1000-b79e1000 r-xp  03:05 521574 /lib/i686/cmov/libresolv-2.7.so
b79e1000-b79e3000 rwxp f000 03:05 521574 /lib/i686/cmov/libresolv-2.7.so
b79e3000-b79e5000 rwxp b79e3000 00:00 0 
b79e5000-b79f1000 r-xp  03:05 1878344/usr/lib/liblber-2.4.so.2.0.3
b79f1000-b79f2000 rwxp c000 03:05 1878344/usr/lib/liblber-2.4.so.2.0.3
b79f2000-b79f3000 rwxp b79f2000 00:00 0 
b79f3000-b7a64000 r-xp  03:05 453617 /usr/lib/libgnutls.so.13.9.1
b7a64000-b7a6a000 rwxp 0007 03:05 453617 /usr/lib/libgnutls.so.13.9.1
b7a6a000-b7a7e000 r-xp  03:05 1878277/usr/lib/libz.so.1.2.3.3
b7a7e000-b7a7f000 rwxp 00013000 03:05 1878277/usr/lib/libz.so.1.2.3.3
b7a7f000-b7a81000 r-xp  03:05 518355 /lib/libcom_err.so.2.1
b7a81000-b7a82000 rwxp 1000 03:05 518355 /lib/libcom_err.so.2.1
b7a82000-b7aa4000 r-xp  03:05 454834 /usr/lib/libk5crypto.so.3.1
b7aa4000-b7aa5000 rwxp 00022000 03:05 454834 /usr/lib/libk5crypto.so.3.1
b7aa5000-b7b31000 r-xp  03:05 458697 /usr/lib/libkrb5.so.3.3
b7b31000-b7b33000 rwxp 0008c000 03:05 458697 /usr/lib/libkrb5.so.3.3
b7b33000-b7b34000 rwxp b7b33000 00:00 0 
b7b34000-b7b5c000 r-xp  03:05 454493 /usr/lib/libgssapi_krb5.so.2.2
b7b5c000-b7b5d000 rwxp 00028000 03:05 454493 /usr/lib/libgssapi_krb5.so.2.2
b7b5d000-b7b9a000 r-xp  03:05 1878458/usr/lib/libldap_r-2.4.so.2.0.3
b7b9a000-b7b9c000 rwxp 0003d000 03:05 1878458/usr/lib/libldap_r-2.4.so.2.0.3
b7b9c000-b7b9d000 rwxp b7b9c000 00:00 0 
b7b9d000-b7bcd000 r-xp  03:05 453564 /usr/lib/libidn.so.11.5.33
b7bcd000-b7bce000 rwxp 0002f000 03:05 453564 /usr/

Processed: xmms-wmdiscotux removal

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 456757 normal
Bug#456757: xmms-wmdiscotux: should this package be removed?
Severity set to `normal' from `serious'

> reassign 456757 ftp.debian.org
Bug#456757: xmms-wmdiscotux: should this package be removed?
Bug reassigned from package `xmms-wmdiscotux' to `ftp.debian.org'.

> retitle 456757 RM: xmms-wmdiscotux -- RoQA; out of date, depends on xmms
Bug#456757: xmms-wmdiscotux: should this package be removed?
Changed Bug title to `RM: xmms-wmdiscotux -- RoQA; out of date, depends on 
xmms' from `xmms-wmdiscotux: should this package be removed?'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#468562: Does not include google-cal-helper

[xian]

Package: opensync-plugin-google-calendar
Version: 0.22-1
Severity: grave

--- Please enter the report below this line. ---
Attempting to use package, sync dies with:

$ msynctool --sync test3
Synchronizing group "test3"
Member 1 of type google-calendar just connected
Member 2 of type kdepim-sync just connected
All clients connected or error
Cannot exec plugin helper (/usr/lib/opensync/google-cal-helper)
Received an entry KOrganizer-1346183308.844 with data of size 4 from 
member 2 (kdepim-sync). Changetype ADDED
Received an entry libkcal-1177780015.316 with data of size 4 from member 
2 (kdepim-sync). Changetype ADDED

Member 2 of type kdepim-sync just sent all changes
Member 1 of type google-calendar had an error while getting changes: 
Helper exited abnormally

Member 1 of type google-calendar just disconnected
Member 2 of type kdepim-sync just disconnected
All clients have disconnected
The sync failed: Unable to read from one of the members
Error while synchronizing: Unable to read from one of the members

Looks like the package needs the google-cal-helper file.

--- System information. ---
Architecture: i386
Kernel: Linux 2.6.24-1-686

Debian Release: lenny/sid
500 unstable ftp.us.debian.org

--- Package information. ---
Depends (Version) | Installed
===-+-
libc6 (>= 2.7-1) | 2.7-8
libglib2.0-0 (>= 2.12.0) | 2.14.6-1
libopensync0 (>= 0.22) | 0.22-1
libxml2 (>= 2.6.27) | 2.6.31.dfsg-1
python | 2.4.4-6
python-httplib2 | 0.2.0-2
python-xml | 0.8.4-10




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: Remove xmms-liveice

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 456708 normal
Bug#456708: xmms-liveice: Should this package be removed?
Severity set to `normal' from `serious'

> reassign 456708 ftp.debian.org
Bug#456708: xmms-liveice: Should this package be removed?
Bug reassigned from package `xmms-liveice' to `ftp.debian.org'.

> retitle 456708 RM: xmms-liveice -- RoQA; out of date, depends on xmms
Bug#456708: xmms-liveice: Should this package be removed?
Changed Bug title to `RM: xmms-liveice -- RoQA; out of date, depends on xmms' 
from `xmms-liveice: Should this package be removed?'.

> thank you
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#468202: openoffice.org-writer2latex: still occurring with 0.5-6

[Hamish Moffatt]

On Fri, Feb 29, 2008 at 12:24:36PM +0100, Rene Engelhard wrote:
> Hamish Moffatt wrote:
> > On Fri, Feb 29, 2008 at 08:29:49AM +0100, Rene Engelhard wrote:
> > > Hamish Moffatt wrote:
> > > > > And you unregistered the extension manually to have a clean state if 
> > > > > it
> > > > > failed before? Read the buglog...
> > > > 
> > > > OK, I removed it (forgot the --shared in the last attempt), and now the
> > > > package configures.
> > > 
> > > Thanks, so I close this again.
> > 
> > Well, it isn't satisfactory that manual intervention is required for
> > anyone who installed 0.5-5. 
> > 
> > You said the problem is on the old postinst. Therefore, you can fix it
> 
> No, I didn't. Read again. I changed the *prerm*.

Sorry, my fault. 

> > http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html
> 
> Will have a look again, though.

Thanks. The manual says that if the old prerm fails, dpkg should try the
same operation with the new prerm, which you said is fixed. I didn't see
it try to do this.


Hamish
-- 
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#468482: marked as done (dlocate uninstallable in unstable)

[Debian Bug Tracking System]

Your message dated Fri, 29 Feb 2008 13:44:55 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#468482: dlocate uninstallable in unstable
has caused the Debian Bug report #468482,
regarding dlocate uninstallable in unstable
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 [EMAIL PROTECTED]
immediately.)


-- 
468482: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468482
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: dlocate
Version: 0.94
Severity: grave
Justification: renders package unusable

Hi,

dlocate actually depends on findutils (<< 4.2.31-2).

[EMAIL PROTECTED]:~ # apt-cache show dlocate
Package: dlocate
Priority: optional
Section: utils
Installed-Size: 88
Maintainer: Craig Sanders <[EMAIL PROTECTED]>
Architecture: all
Version: 0.94
Depends: dctrl-tools | grep-dctrl (>= 0.11), dpkg (>= 1.8.0), locate | 
findutils (<< 4.2.31-2), perl
Filename: pool/main/d/dlocate/dlocate_0.94_all.deb
Size: 16606
MD5sum: 8b3eb28d752136b527e2062b31b2d1f6
SHA1: 1454c9ba576aa97102898137d84ef85f194ee88b
SHA256: d74531e715bd0f262c9970152e83b2c99c070dcf5346240bd3fd44391f3b450b

The version in unstable/testing however is 4.2.33-1 resp. 4.2.32-1, which
makes your package uninstallable. No, findutils can't be removed, as it is
essential.

[EMAIL PROTECTED]:~ # dpkg --no-act --purge findutils
dpkg: error processing findutils (--purge):
 This is an essential package - it should not be removed.
Errors were encountered while processing:
 findutils

Thanks,
  Hilmar

P.S.: there are a lot of bugs on your package having the tag "fixed", but
were never closed.

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

Kernel: Linux 2.6.22-3-686 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages dlocate depends on:
ii  dctrl-tools [grep-dctrl]  2.12   Command-line tools to process Debi
ii  dpkg  1.14.16.6  package maintenance system for Deb
ii  findutils 4.2.31-1   utilities for finding files--find,
ii  perl  5.8.8-12   Larry Wall's Practical Extraction 

dlocate recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
On 29.02.08 Craig Sanders ([EMAIL PROTECTED]) wrote:

Hi,

> so, either the 'locate' package or 'findutils <<4.2.31-2' will
> satisfy the dependancy.
> 
Correct: I'm sorry! I was confused by the fact that an upgrade of
findutils deinstalled dlocate. However after doing this I could
re-install dlocate again. Was some weirdness by apt -> closing. If
you think this is a bug in apt, feel free to open a bug there.

Have a nice weekend!

[EMAIL PROTECTED]:~ # apt-get install findutils
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
  mlocate locate slocate
The following packages will be REMOVED
  dlocate
The following packages will be upgraded:
  findutils
1 upgraded, 0 newly installed, 1 to remove and 2 not upgraded.
Need to get 356kB of archives.
After this operation, 254kB disk space will be freed.
Do you want to continue [Y/n]? y
Get: 1 http://ftp.de.debian.org unstable/main findutils 4.2.33-1
[356kB]
Fetched 356kB in 1s (210kB/s)
Reading package fields... Done
Reading package status... Done
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
(Reading database ... 98230 files and directories currently
installed.)
Removing dlocate ...
(Reading database ... 98215 files and directories currently
installed.)
Preparing to replace findutils 4.2.31-1 (using
.../findutils_4.2.33-1_i386.deb) ...
generating /etc/updatedb.findutils.cron.local from user modified
/etc/updatedb.conf
Saving /etc/updatedb.conf as /etc/updatedb.conf.dpkg-bak ...
Removing obsolete conffile /etc/cron.daily/find ...
Unpacking replacement findutils ...
dpkg: warning - unable to delete old directory `/var/cache/locate':
Directory not empty
Setting up findutils (4.2.33-1) ...
[EMAIL PROTECTED]:~ # apt-get install dlocate
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  locate
The following NEW packages will be installed
  dlocate locate
0 upgraded, 2 newly installed, 0 to remove and 2 not upgraded.
Need to get 129kB of archives.
After this operation, 360kB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get: 1 http://ftp.de.debian.org unstable/main locate 4.2.

Processed: Re: Bug#468476: newsbeuter: segfaults at startup

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> tags 468476 + confirmed
Bug#468476: newsbeuter: segfaults at startup
There were no tags set.
Tags added: confirmed

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#468476: newsbeuter: segfaults at startup

[Nico Golde]

tags 468476 + confirmed
thanks

Hi Xavier,
* Xavier Bestel <[EMAIL PROTECTED]> [2008-02-29 12:33]:
> Package: newsbeuter
> Version: 0.7-3+b1
> Severity: grave
> Justification: renders package unusable
> 
> newsbeuter dies after today's unstable dist-upgrade:
> 
> [EMAIL PROTECTED]:~]$ CHECK_MALLOC_=2 newsbeuter
> Démarrage newsbeuter 0.7...
> Chargement de la configuration...fait.
[...] 
I can reproduce this and aah what in hell happened 
again... I am heading of to the Chemnitzer LinuxTag now but 
I try to find some time to debug this during the event.
Kind regards
Nico
-- 
Nico Golde - http://www.ngolde.de - [EMAIL PROTECTED] - GPG: 0x73647CFF
For security reasons, all text in this mail is double-rot13 encrypted.


pgpr6OggSUBep.pgp
Description: PGP signature

Bug#468494: Day view in Calendar not working for users, only for groups

[Stefan Bellon]

Package: egroupware-infolog
Version: 1.2.107-2.dfsg-2
Severity: serious
Tags: patch

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

After upgrading to egroupware version 1.2.107, the day view in the
calendar does not work for single users anymore, only for groups. Week
and month views still work for single users. The error message one gets
when visiting a person's day view is the following:


Database error: Invalid SQL: SELECT main.info_id FROM egw_infolog main
WHERE ( ((info_owner=6 AND info_responsible=0 OR
','||info_responsible||',' LIKE '%,6,%') AND (info_owner=6 OR
(','||info_responsible||',' LIKE '%,6,%' AND info_access='public') OR
info_owner IN (6) OR (info_access='public' AND info_owner
IN(-11,6,12,7,9,-1,8,-10))) ) AND NOT (info_status IN
('done','billed','cancelled')) AND info_startdate < '1204326000' )
pgsql Error: -1 (ERROR: operator does not exist: character varying =
integer LINE 1: ... main WHERE ( ((info_owner=6 AND info_responsible=0
OR ','|... ^ HINT: No operator matches the given name and argument
type(s). You might need to add explicit type casts.)

File: /usr/share/egroupware/infolog/inc/class.soinfolog.inc.php
Line: 590
Function: soinfolog::search / boinfolog::search /
boinfolog::cal_to_include /
ExecMethod(infolog.boinfolog.cal_to_include) / hooks::single /
hooks::process / uiviews::get_todos / uiviews::day /
ExecMethod(calendar.uiviews.day)

Session halted.


Having looked at the database schema of egw_infolog I verified that
postgresql is correct here as the info_responsible column is of type
character varying but gets compared to integer. Having looked
inside /usr/share/egroupware/infolog/inc/class.soinfolog.inc.php I
indeed spotted the problem in line 167 where info_responsible=0 is
missing the quotation marks to make the 0 a string literal. After
replacing it with info_responsible='0', the day view works again.



--- System information. ---
Architecture: i386
Kernel:   Linux 2.6.16

Debian Release: lenny/sid
  500 unstablewww.debian-multimedia.org 
  500 unstableftp.debian.org 

--- Package information. ---
Depends (Version) | Installed
=-+-=
egroupware-core  (= 1.2.107-2.dfsg-2) | 1.2.107-2.dfsg-2
egroupware-etemplate (= 1.2.107-2.dfsg-2) | 1.2.107-2.dfsg-2


-- 
Stefan Bellon



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#468487: marked as done (allows unauthorized remote arbitrary code execution (CVE-2007-5689))

[Debian Bug Tracking System]

Your message dated Fri, 29 Feb 2008 06:39:54 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Close
has caused the Debian Bug report #468487,
regarding allows unauthorized remote arbitrary code execution (CVE-2007-5689)
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 [EMAIL PROTECTED]
immediately.)


-- 
468487: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468487
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: sun-java6
Version: 6-00-2
Severity: critical
Tags: security, upstream

The sun-java6 version in testing is vulnerable to CVE-2007-5689 :
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-5689

From http://nvd.nist.gov/nvd.cfm?cvename=CVE-2007-5689 :

Overview

 The Java Virtual Machine (JVM) in Sun Java Runtime Environment (JRE) in SDK 
and JRE 1.3.x through 1.3.1_20 and 1.4.x through 1.4.2_15, and JDK and JRE 
5.x through 5.0 Update 12 and 6.x through 6 Update 2, allows remote attackers 
to execute arbitrary programs, or read or modify arbitrary files, via applets 
that grant privileges to themselves. 
 
Impact

 CVSS Severity (version 2.0):
 CVSS v2 Base score: 10.0 (High) (AV:N/AC:L/Au:N/C:C/I:C/A:C) (legend) 
 Impact Subscore: 10.0
 Exploitability Subscore: 10.0 

This is fixed in the unstable version, which is waiting a missing ia64 build 
or to be forced to migrate.


--- End Message ---
--- Begin Message ---
Version: 6-03-1

--- End Message ---

Bug#463501: Nokia Award Notification !!!!!!

[2008 NOKIA N'SERIES AWARD PROMOTIO]

NOKIA N'SERIES PROMOTION
TICKET NO: 1110008342
Ref : NKN/UK 110241/01
Batch: 4-13-7-37-1

We are delighted to inform you of your prize
release on the 23rd February, 2008 from the
NOKIA 'N' SERIES PROGRAM. Your e-mail was
attached to serial number 6028808.Your Email have won the
Sum of You hereby have been approved a lump sum
of GBP £1,000,000.00(ONE MILLION GREAT
BRITISH POUNDS)

Contact Mr James Keegan for claims :
Email:  [EMAIL PROTECTED]
Tel: +44 703 190 9354
Fax: +44 707 500 4877

Bug#468482: dlocate uninstallable in unstable

[Craig Sanders]

On Fri, Feb 29, 2008 at 11:50:19AM +0100, Hilmar Preusse wrote:
> dlocate actually depends on findutils (<< 4.2.31-2).

no, it depends on 'locate | findutils (<< 4.2.31-2)'

> [...]
> Depends: dctrl-tools | grep-dctrl (>= 0.11), dpkg (>= 1.8.0), locate | 
> findutils (<< 4.2.31-2), perl
> [...]
> 
> The version in unstable/testing however is 4.2.33-1 resp. 4.2.32-1, which
> makes your package uninstallable. No, findutils can't be removed, as it is
> essential.

could you show an example?

dlocate depends on either 'locate' or 'findutils (<< 4.2.31-2)'. that
was changed recently (Dec 2007) because locate & frcode were split out
from the findutils package into a separate package called 'locate'.

to put it another way: dlocate actually depends on the frcode program.
frcode used to be in findutils package (<< 4.2.31-2), but is now in the
locate package.


so, either the 'locate' package or 'findutils <<4.2.31-2' will satisfy
the dependancy.

see Bug #453952 for more details.


btw, what are you using? apt-get? aptitude? if you're describing an
actual event rather than just theory, try with the other one. if that
works, then i'd suspect that there might be a bug in the dependancy
resolution of the other.




BTW, in case you're worried about incompatibility with mlocate, that
package does not conflict with the locate packagealthough you do
have to take steps to stop both locate and mlocate from indexing the
filesystems. see Bug #454471 for more details. see also Bug #454106, one
of the messages contains a useful method for generating the locate db
from the mlocate db.




> P.S.: there are a lot of bugs on your package having the tag "fixed", but
> were never closed.

hmmm. i guess i've just assumed all along that Fixed is equivalent to
Closed, and they don't actually need to be closed. i've adopted all the
NMU changes, so i'll just close all the Fixed bugs next time i upload an
update.


craig

-- 
craig sanders <[EMAIL PROTECTED]>



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#468202: openoffice.org-writer2latex: still occurring with 0.5-6

[Rene Engelhard]

Hi,

Hamish Moffatt wrote:
> On Fri, Feb 29, 2008 at 08:29:49AM +0100, Rene Engelhard wrote:
> > Hamish Moffatt wrote:
> > > > And you unregistered the extension manually to have a clean state if it
> > > > failed before? Read the buglog...
> > > 
> > > OK, I removed it (forgot the --shared in the last attempt), and now the
> > > package configures.
> > 
> > Thanks, so I close this again.
> 
> Well, it isn't satisfactory that manual intervention is required for
> anyone who installed 0.5-5. 
> 
> You said the problem is on the old postinst. Therefore, you can fix it

No, I didn't. Read again. I changed the *prerm*.

> http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html

Will have a look again, though.

Regards,

Rene



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#468487: allows unauthorized remote arbitrary code execution (CVE-2007-5689)

[Philippe Cloutier]

Package: sun-java6
Version: 6-00-2
Severity: critical
Tags: security, upstream

The sun-java6 version in testing is vulnerable to CVE-2007-5689 :
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-5689

From http://nvd.nist.gov/nvd.cfm?cvename=CVE-2007-5689 :

Overview

 The Java Virtual Machine (JVM) in Sun Java Runtime Environment (JRE) in SDK 
and JRE 1.3.x through 1.3.1_20 and 1.4.x through 1.4.2_15, and JDK and JRE 
5.x through 5.0 Update 12 and 6.x through 6 Update 2, allows remote attackers 
to execute arbitrary programs, or read or modify arbitrary files, via applets 
that grant privileges to themselves. 
 
Impact

 CVSS Severity (version 2.0):
 CVSS v2 Base score: 10.0 (High) (AV:N/AC:L/Au:N/C:C/I:C/A:C) (legend) 
 Impact Subscore: 10.0
 Exploitability Subscore: 10.0 

This is fixed in the unstable version, which is waiting a missing ia64 build 
or to be forced to migrate.

Bug#468482: dlocate uninstallable in unstable

[Hilmar Preusse]

Package: dlocate
Version: 0.94
Severity: grave
Justification: renders package unusable

Hi,

dlocate actually depends on findutils (<< 4.2.31-2).

[EMAIL PROTECTED]:~ # apt-cache show dlocate
Package: dlocate
Priority: optional
Section: utils
Installed-Size: 88
Maintainer: Craig Sanders <[EMAIL PROTECTED]>
Architecture: all
Version: 0.94
Depends: dctrl-tools | grep-dctrl (>= 0.11), dpkg (>= 1.8.0), locate | 
findutils (<< 4.2.31-2), perl
Filename: pool/main/d/dlocate/dlocate_0.94_all.deb
Size: 16606
MD5sum: 8b3eb28d752136b527e2062b31b2d1f6
SHA1: 1454c9ba576aa97102898137d84ef85f194ee88b
SHA256: d74531e715bd0f262c9970152e83b2c99c070dcf5346240bd3fd44391f3b450b

The version in unstable/testing however is 4.2.33-1 resp. 4.2.32-1, which
makes your package uninstallable. No, findutils can't be removed, as it is
essential.

[EMAIL PROTECTED]:~ # dpkg --no-act --purge findutils
dpkg: error processing findutils (--purge):
 This is an essential package - it should not be removed.
Errors were encountered while processing:
 findutils

Thanks,
  Hilmar

P.S.: there are a lot of bugs on your package having the tag "fixed", but
were never closed.

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

Kernel: Linux 2.6.22-3-686 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages dlocate depends on:
ii  dctrl-tools [grep-dctrl]  2.12   Command-line tools to process Debi
ii  dpkg  1.14.16.6  package maintenance system for Deb
ii  findutils 4.2.31-1   utilities for finding files--find,
ii  perl  5.8.8-12   Larry Wall's Practical Extraction 

dlocate recommends no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#463360: marked as done (proxy-suite: ldap_init, ldap_get_values implicitly converted to pointers)

[Debian Bug Tracking System]

Your message dated Fri, 29 Feb 2008 10:17:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#463360: fixed in proxy-suite 1.9.2.4-5
has caused the Debian Bug report #463360,
regarding proxy-suite: ldap_init, ldap_get_values implicitly converted to 
pointers
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 [EMAIL PROTECTED]
immediately.)


-- 
463360: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=463360
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: proxy-suite
Version: 1.9.2.4-4
Severity: important
Tags: patch
Usertags: implicit-pointer-conversion

Our automated buildd log filter[1] detected a problem that is likely to
cause your package to segfault on architectures where the size of a
pointer is greater than the size of an integer, such as ia64 and amd64.

This is often due to a missing function prototype definition.
For more information, see [2].

[1] http://people.debian.org/~dannf/check-implicit-pointer-functions
[2] http://wiki.debian.org/ImplicitPointerConversions

  Function `ldap_init' implicitly converted to pointer at ftp-ldap.c:212
  Function `ldap_get_values' implicitly converted to pointer at ftp-ldap.c:927

The libldap API has been updated and many functions used by the ldap
plugin are now deprecated. This package should either update to the
new API or define LDAP_DEPRECATED to continue using the deprecated
interfaces.

This patch implements the lazy solution.

--- proxy-suite-1.9.2.4/ftp-proxy/ftp-ldap.c~   2005-01-10 04:30:49.0 
-0700
+++ proxy-suite-1.9.2.4/ftp-proxy/ftp-ldap.c2008-01-30 22:48:42.0 
-0700
@@ -70,6 +70,7 @@
 #  if defined(HAVE_LDAP_UMICH)
 #include 
 #  endif
+#  define LDAP_DEPRECATED   1
 #  include 
 #  if !defined(LDAP_PORT)
 #define LDAP_PORT  389



--- End Message ---
--- Begin Message ---
Source: proxy-suite
Source-Version: 1.9.2.4-5

We believe that the bug you reported is fixed in the latest version of
proxy-suite, which is due to be installed in the Debian FTP archive:

ftp-proxy-doc_1.9.2.4-5_all.deb
  to pool/main/p/proxy-suite/ftp-proxy-doc_1.9.2.4-5_all.deb
ftp-proxy_1.9.2.4-5_i386.deb
  to pool/main/p/proxy-suite/ftp-proxy_1.9.2.4-5_i386.deb
proxy-suite_1.9.2.4-5.diff.gz
  to pool/main/p/proxy-suite/proxy-suite_1.9.2.4-5.diff.gz
proxy-suite_1.9.2.4-5.dsc
  to pool/main/p/proxy-suite/proxy-suite_1.9.2.4-5.dsc



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 [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Roberto Lumbreras <[EMAIL PROTECTED]> (supplier of updated proxy-suite 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 [EMAIL PROTECTED])


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Fri, 29 Feb 2008 10:37:25 +0100
Source: proxy-suite
Binary: ftp-proxy ftp-proxy-doc
Architecture: source all i386
Version: 1.9.2.4-5
Distribution: unstable
Urgency: low
Maintainer: Roberto Lumbreras <[EMAIL PROTECTED]>
Changed-By: Roberto Lumbreras <[EMAIL PROTECTED]>
Description: 
 ftp-proxy  - application level proxy for the FTP protocol
 ftp-proxy-doc - documentation for ftp-proxy
Closes: 463360
Changes: 
 proxy-suite (1.9.2.4-5) unstable; urgency=low
 .
   * Define LDAP_DEPRECATED until a better fix is available. (Closes: #463360)
   * Updated standards.
   * Move docs to -doc directory.
Files: 
 8f84757215b9e36500b799026ce89676 696 net optional proxy-suite_1.9.2.4-5.dsc
 1c100c59a906cc2443fbf7882303edd8 6249 net optional 
proxy-suite_1.9.2.4-5.diff.gz
 6a4974a9ee623056886d093b0abcb86e 108104 doc optional 
ftp-proxy-doc_1.9.2.4-5_all.deb
 64527edbfed304e69193cc19532d64dd 62130 net optional 
ftp-proxy_1.9.2.4-5_i386.deb

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

iD8DBQFHx9hAfIEQE/XJcI0RApyBAJ98dfO6YCUjBJT/+9rH2oPV0OEmMgCg+axN
JTiAP7MiJDoh2jaObI+1HfY=
=aGo5
-END PGP SIGNATURE-


--- End Message ---

Processed: setting package to libgmp-ocaml libgmp-ocaml-dev mlgmp, tagging 464312

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.10.16
> package libgmp-ocaml libgmp-ocaml-dev mlgmp
Ignoring bugs not assigned to: mlgmp libgmp-ocaml-dev libgmp-ocaml

> tags 464312 + pending
Bug#464312: mlgmp: FTBFS: dh_movefiles: 
debian/libgmp-ocaml-dev/usr/lib/ocaml/3.10.0/stublibs/ not found (supposed to 
put it in libgmp-ocaml)
There were no tags set.
Tags added: pending

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#406986: Upgrade B2evolution 0.9.2 to 1.10.2

[Thijs Kinkhorst]

Hi Emilio,

> I would also consider removing it from stable, as I think the security
> team cannot support it.

The security team for stable often supports versions that are upstream
abandoned. The question is whether such a thing is feasible for a package.
In this case I see just one open security issue in the tracker, for which
a patch is available. I therefore see no immediate need to remove the
package from stable.

We should be conservative with removing things from stable, because upon
release we made the "promise" to (security) support stable until one year
after a new release comes out and people should be able to count on that
as much as reasonably possible.


Thijs

Bug#467518: git-core: builds defective package under umask 077

[Gerrit Pape]

tags 467518 + patch
quit

On Tue, Feb 26, 2008 at 04:45:05AM +0100, Florian Zumbiehl wrote:
> Well, when starting the build from a umask 077 environment, numerous
> files in the resulting package are 0600, which makes it mostly unusable.
> 
> I have not explicitly tested whether this applies to the non-backport
> version, too, but I don't see any reason why that should differ for
> a backported package.

Yes, thanks for spotting this.  Here's a patch
 http://git.kernel.org/?p=git/git.git;a=commitdiff;h=990772

Regards, Gerrit.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: Re: Bug#467518: git-core: builds defective package under umask 077

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> tags 467518 + patch
Bug#467518: git-core: builds defective package under umask 077
There were no tags set.
Tags added: patch

> quit
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#468476: newsbeuter: segfaults at startup

[Xavier Bestel]

Package: newsbeuter
Version: 0.7-3+b1
Severity: grave
Justification: renders package unusable


Hi,

newsbeuter dies after today's unstable dist-upgrade:

[EMAIL PROTECTED]:~]$ CHECK_MALLOC_=2 newsbeuter
Démarrage newsbeuter 0.7...
Chargement de la configuration...fait.
Vidage du cache...fait.
Chargement des URLs depuis /home/xav/.newsbeuter/urls...fait.
Chargement des articles depuis le cache...*** glibc detected *** newsbeuter: 
free(): invalid pointer: 0x080f4058 ***
=== Backtrace: =
/lib/i686/cmov/libc.so.6[0xb7c40564]
/lib/i686/cmov/libc.so.6(cfree+0x96)[0xb7c42766]
newsbeuter[0x804ecac]
newsbeuter[0x80510b9]
newsbeuter[0x806f0f0]
newsbeuter[0x804d915]
/lib/i686/cmov/libc.so.6(__libc_start_main+0xe6)[0xb7be8456]
newsbeuter(__gxx_personality_v0+0x3fd)[0x804d601]
=== Memory map: 
08048000-080ce000 r-xp  03:05 131742 /usr/bin/newsbeuter
080ce000-080d1000 rwxp 00086000 03:05 131742 /usr/bin/newsbeuter
080d1000-08115000 rwxp 080d1000 00:00 0  [heap]
b660-b6621000 rwxp b660 00:00 0 
b6621000-b670 ---p b6621000 00:00 0 
b677b000-b677c000 ---p b677b000 00:00 0 
b677c000-b6f7c000 rwxp b677c000 00:00 0 
b6f7c000-b6f7d000 ---p b6f7c000 00:00 0 
b6f7d000-b777d000 rwxp b6f7d000 00:00 0 
b777d000-b78b7000 r-xp  03:05 551073 /usr/lib/locale/locale-archive
b78b7000-b78ba000 rwxp b78b7000 00:00 0 
b78ba000-b792 r-xp  03:05 454273 /usr/lib/libgcrypt.so.11.4.3
b792-b7922000 rwxp 00065000 03:05 454273 /usr/lib/libgcrypt.so.11.4.3
b7922000-b7925000 r-xp  03:05 457395 /usr/lib/libgpg-error.so.0.3.0
b7925000-b7926000 rwxp 2000 03:05 457395 /usr/lib/libgpg-error.so.0.3.0
b7926000-b7934000 r-xp  03:05 453419 /usr/lib/libtasn1.so.3.0.14
b7934000-b7935000 rwxp e000 03:05 453419 /usr/lib/libtasn1.so.3.0.14
b7935000-b7937000 r-xp  03:05 522504 /lib/libkeyutils-1.2.so
b7937000-b7938000 rwxp 1000 03:05 522504 /lib/libkeyutils-1.2.so
b7938000-b7939000 rwxp b7938000 00:00 0 
b7939000-b794 r-xp  03:05 458699 /usr/lib/libkrb5support.so.0.1
b794-b7941000 rwxp 6000 03:05 458699 /usr/lib/libkrb5support.so.0.1
b7941000-b79b4000 r-xp  03:05 217200 /usr/lib/libgnutls.so.26.1.3
b79b4000-b79ba000 rwxp 00072000 03:05 217200 /usr/lib/libgnutls.so.26.1.3
b79ba000-b79d r-xp  03:05 453473 /usr/lib/libsasl2.so.2.0.22
b79d-b79d1000 rwxp 00015000 03:05 453473 /usr/lib/libsasl2.so.2.0.22
b79d1000-b79e1000 r-xp  03:05 521574 /lib/i686/cmov/libresolv-2.7.so
b79e1000-b79e3000 rwxp f000 03:05 521574 /lib/i686/cmov/libresolv-2.7.so
b79e3000-b79e5000 rwxp b79e3000 00:00 0 
b79e5000-b79f1000 r-xp  03:05 1878344/usr/lib/liblber-2.4.so.2.0.3
b79f1000-b79f2000 rwxp c000 03:05 1878344/usr/lib/liblber-2.4.so.2.0.3
b79f2000-b79f3000 rwxp b79f2000 00:00 0 
b79f3000-b7a64000 r-xp  03:05 453617 /usr/lib/libgnutls.so.13.9.1
b7a64000-b7a6a000 rwxp 0007 03:05 453617 /usr/lib/libgnutls.so.13.9.1
b7a6a000-b7a7e000 r-xp  03:05 1878277/usr/lib/libz.so.1.2.3.3
b7a7e000-b7a7f000 rwxp 00013000 03:05 1878277/usr/lib/libz.so.1.2.3.3
b7a7f000-b7a81000 r-xp  03:05 518355 /lib/libcom_err.so.2.1
b7a81000-b7a82000 rwxp 1000 03:05 518355 /lib/libcom_err.so.2.1
b7a82000-b7aa4000 r-xp  03:05 454834 /usr/lib/libk5crypto.so.3.1
b7aa4000-b7aa5000 rwxp 00022000 03:05 454834 /usr/lib/libk5crypto.so.3.1
b7aa5000-b7b31000 r-xp  03:05 458697 /usr/lib/libkrb5.so.3.3
b7b31000-b7b33000 rwxp 0008c000 03:05 458697 /usr/lib/libkrb5.so.3.3
b7b33000-b7b34000 rwxp b7b33000 00:00 0 
b7b34000-b7b5c000 r-xp  03:05 454493 /usr/lib/libgssapi_krb5.so.2.2
b7b5c000-b7b5d000 rwxp 00028000 03:05 454493 /usr/lib/libgssapi_krb5.so.2.2
b7b5d000-b7b9a000 r-xp  03:05 1878458/usr/lib/libldap_r-2.4.so.2.0.3
b7b9a000-b7b9c000 rwxp 0003d000 03:05 1878458/usr/lib/libldap_r-2.4.so.2.0.3
b7b9c000-b7b9d000 rwxp b7b9c000 00:00 0 
b7b9d000-b7bcd000 r-xp  03:05 453564 /usr/lib/libidn.so.11.5.33
b7bcd000-b7bce000 rwxp 0002f000 03:05 453564 /usr/lib/libidn.so.11.5.33
b7bce000-b7bd r-xp  03:05 519705 /lib/i686/cmov/libdl-2.7.so
b7bd-b7bd2000 rwxp 1000 03:05 519705 /lib/i686/cmov/libdl-2.7.so
b7bd2000-b7d27000 r-xp  03:05 519702 /lib/i686/cmov/libc-2.7.so
b7d27000-b7d28000 r-xp 00155000 03:05 519702 /lib/i686/cmov/libc-2.7.so
b7d28000-b7d2a000 rwxp 00156000 03:05 519702 /lib/i686/cmov/libc-2.7.so
b7d2a000-b7d2d000 rwxp b7d2a000 00:00 0 
b7d2d000-b7d39000 r-xp  03:05 522529 /lib/libgcc_s.so.1
b7d39000-b7d3a000 rwxp b000 03:05 522529 /lib/libgcc_s.so.1
b7d3a000-b7d3b000 rwxp b7d3a000 00:00 0 
b7d3b000-b7d5f000 r-xp  03:05 519707 /lib/i686/cmov/libm-2.7.so
b7d5f000-b7d61000 rwxp 00023000 03:05 519707 /lib/i686/cmov/libm-2.7.so
b7d61000-b7e44000 r-xp  03:

Bug#468202: openoffice.org-writer2latex: still occurring with 0.5-6

[Hamish Moffatt]

On Fri, Feb 29, 2008 at 08:29:49AM +0100, Rene Engelhard wrote:
> Hamish Moffatt wrote:
> > > And you unregistered the extension manually to have a clean state if it
> > > failed before? Read the buglog...
> > 
> > OK, I removed it (forgot the --shared in the last attempt), and now the
> > package configures.
> 
> Thanks, so I close this again.

Well, it isn't satisfactory that manual intervention is required for
anyone who installed 0.5-5. 

You said the problem is on the old postinst. Therefore, you can fix it
in the new preinst. Either prepare for it, or remove the script, or
whatever. See the policy manual section:
http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html


Hamish
-- 
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#468465: FTBFS: make: execvp: ./configure: Permission denied

[Vincent Bernat]

Package: libgpmg1
Version: 1.20.3~pre3-1
Severity: serious
Tags: patch
Justification: FTBFS

Hi !

When building gpm from source, I get:

autoconf
./configure --prefix=/usr --sysconfdir=/etc
make: execvp: ./configure: Permission denied

Building again solves the problem. Attached a very simple patch to
solve the problem.

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

Kernel: Linux 2.6.24-1-amd64 (SMP w/1 CPU core)
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages libgpmg1 depends on:
ii  libc6 2.7-9  GNU C Library: Shared libraries

libgpmg1 recommends no packages.

-- no debconf information
--- gpm-1.20.3~pre3/debian/rules~   2008-02-29 09:40:30.0 +0100
+++ gpm-1.20.3~pre3/debian/rules2008-02-29 09:40:50.0 +0100
@@ -19,6 +19,7 @@
autoconf
 
 config.status: configure
+   chmod +x configure
./configure --prefix=/usr --sysconfdir=/etc
 
 build: config.status