Bug#465012: newbiedoc: bashism in /bin/sh script

[Raphael Geissert]

Package: newbiedoc
Severity: important
Version: 0.6.0-3
User: [EMAIL PROTECTED]
Usertags: goal-dash

Hello maintainer,

While performing an archive wide checkbashisms (from the 'devscripts' package) 
check I've found your package containing a /bin/sh script making 
use of a bashism.

checkbashisms' output:
> possible bashism in ./usr/bin/newbiedoc line 8 (should be >word 2>&1):
> if ! (which $BROWSER &> /dev/null); then
> possible bashism in ./usr/bin/newbiedoc line 32 (should be >word 2>&1):
>   if ! (which $BROWSER &> /dev/null); then


Not using bash as /bin/sh would lead to errors. Please be aware that although 
bash is currently the default /bin/sh there's a release goal for Lenny to 
make dash the default /bin/sh[1].

If you want more information about dash as /bin/sh, you can read:
http://lists.debian.org/debian-release/2008/01/msg00189.html
https://wiki.ubuntu.com/DashAsBinSh

[1]http://release.debian.org/lenny/goals.txt

Thank you,
-- 
Atomo64 - Raphael

Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html



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

Processed (with 2 errors): ifplugd bug triage

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 407093 normal
Bug#407093: ifplugd: causes high system load
Severity set to `normal' from `important'

> severity 360464 important
Bug#360464: ifplugd: leaves file after upgraded from sarge and purged
Severity set to `important' from `normal'

> merge 360464 461395
Bug#360464: ifplugd: leaves file after upgraded from sarge and purged
Bug#461395: Does not remove ifplugd.hotplug on package upgrades
Merged 360464 461395.

> merge 432612 407349
Bug#407349: ifplugd: should start earlier
Bug#432612: ifplugd: needs to start sooner
Merged 407349 432612.

> serverity 213910 normal
Unknown command or malformed arguments to command.

> merge 213910 319727
Bug#213910: Debconf question about options points to possibly not-yet-existing 
documentation sources
Bug#319727: debconf questions are not useful
Mismatch - only Bugs in same state can be merged:
Values for `severity' don't match:
 #213910 has `minor';
 #319727 has `normal'

> 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: ifplugd bug triage

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 213910 normal
Bug#213910: Debconf question about options points to possibly not-yet-existing 
documentation sources
Severity set to `normal' from `minor'

> merge 213910 319727
Bug#213910: Debconf question about options points to possibly not-yet-existing 
documentation sources
Bug#319727: debconf questions are not useful
Merged 213910 319727.

> 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]

Processing of quiteinsanegimpplugin_0.3-9_i386.changes

[Archive Administrator]

quiteinsanegimpplugin_0.3-9_i386.changes uploaded successfully to localhost
along with the files:
  quiteinsanegimpplugin_0.3-9.dsc
  quiteinsanegimpplugin_0.3-9.diff.gz
  gimp2.0-quiteinsane_0.3-9_i386.deb

Greetings,

Your Debian queue daemon


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

quiteinsanegimpplugin_0.3-9_i386.changes ACCEPTED

[Debian Installer]

Accepted:
gimp2.0-quiteinsane_0.3-9_i386.deb
  to pool/main/q/quiteinsanegimpplugin/gimp2.0-quiteinsane_0.3-9_i386.deb
quiteinsanegimpplugin_0.3-9.diff.gz
  to pool/main/q/quiteinsanegimpplugin/quiteinsanegimpplugin_0.3-9.diff.gz
quiteinsanegimpplugin_0.3-9.dsc
  to pool/main/q/quiteinsanegimpplugin/quiteinsanegimpplugin_0.3-9.dsc


Override entries for your package:
gimp2.0-quiteinsane_0.3-9_i386.deb - optional graphics
quiteinsanegimpplugin_0.3-9.dsc - source graphics

Announcing to [EMAIL PROTECTED]
Closing bugs: 464860 


Thank you for your contribution to Debian.


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

Bug#464860: marked as done (quiteinsanegimpplugins: Build depends on ancient libqt3-compat-headers)

[Debian Bug Tracking System]

Your message dated Sun, 10 Feb 2008 11:02:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#464860: fixed in quiteinsanegimpplugin 0.3-9
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

--- Begin Message ---
Package: quiteinsanegimpplugins
Version: 0.3-8
Severity: normal
User: [EMAIL PROTECTED]
Usertag: libqt3-compat-headers

Hi,

We are currently attempting to remove the antiquated libqt3-compat-headers from 
the archive.

Since this package is orphaned, I will do a QA upload to fix this issue.

Thank you,

Barry deFreese



--- End Message ---
--- Begin Message ---
Source: quiteinsanegimpplugin
Source-Version: 0.3-9

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

gimp2.0-quiteinsane_0.3-9_i386.deb
  to pool/main/q/quiteinsanegimpplugin/gimp2.0-quiteinsane_0.3-9_i386.deb
quiteinsanegimpplugin_0.3-9.diff.gz
  to pool/main/q/quiteinsanegimpplugin/quiteinsanegimpplugin_0.3-9.diff.gz
quiteinsanegimpplugin_0.3-9.dsc
  to pool/main/q/quiteinsanegimpplugin/quiteinsanegimpplugin_0.3-9.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.
Barry deFreese <[EMAIL PROTECTED]> (supplier of updated quiteinsanegimpplugin 
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, 09 Feb 2008 08:23:48 -0500
Source: quiteinsanegimpplugin
Binary: gimp2.0-quiteinsane
Architecture: source i386
Version: 0.3-9
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group <[EMAIL PROTECTED]>
Changed-By: Barry deFreese <[EMAIL PROTECTED]>
Description: 
 gimp2.0-quiteinsane - A Qt based SANE plugin for GIMP 2.0
Closes: 464860
Changes: 
 quiteinsanegimpplugin (0.3-9) unstable; urgency=low
 .
   * QA upload.
   * Build without libqt3-compat-headers. (Closes: #464860).
 + Update header includes appropriately.
   * Move Homepage field from package description to control header.
   * Remove author from package description.
   * Remove unused debhelper commands from rules.
   * debian/copyright:
 + Add Copyright holders.
 + Add GPL preamble and fix link to approriate license - GPL-2.
   * Bump debhelper build-dep and compat to 5.
   * Bump Standards Version to 3.7.3. (No changes needed).
Files: 
 b89b741b006d55775cf494460bd55cb2 773 graphics optional 
quiteinsanegimpplugin_0.3-9.dsc
 398556b6c01da0ea086508c4fcec196c 4605 graphics optional 
quiteinsanegimpplugin_0.3-9.diff.gz
 fa35e3accbbe99c0290475b3e0c5d7cb 207514 graphics optional 
gimp2.0-quiteinsane_0.3-9_i386.deb

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

iD8DBQFHrte4riZpaaIa1PkRAi54AJwKdlfo/1ZZmdZPB4VPoSYKgBci7ACgyEUn
eo2BnzrDD6nEQSSAquXA7cI=
=Z8Ej
-END PGP SIGNATURE-


--- End Message ---

Processed: ifplugd bug triage

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> fixed 418918 0.28-2.1
Bug#418918: ifplugd.rules executable
Bug marked as fixed in version 0.28-2.1.

> 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#439235: marked as done (cmail: startup modifies load-path directly)

[Debian Bug Tracking System]

Your message dated Sun, 10 Feb 2008 22:05:05 +0900 (JST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs of cmail
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

--- Begin Message ---
Package: cmail
Version: 2.62-5
Severity: serious

cmail package's emacsen-startup file modifies the load-path
variable directly.  According to debian-emacs-policy, please use
the debian-pkg-add-load-path-item function instead of setq.

Thanks,
--
Tatsuya Kinoshita


pgpt8S2ulARUk.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
The cmail pacakge was removed from testing/unstable.
Closing the bugs.

Thanks,
--
Tatsuya Kinoshita


pgpJek4GnmhgA.pgp
Description: PGP signature
--- End Message ---

Bug#291284: marked as done (cmail doc in Japanese)

[Debian Bug Tracking System]

Your message dated Sun, 10 Feb 2008 22:05:05 +0900 (JST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs of cmail
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

--- Begin Message ---
Package: cmail
Version: 2.62-3

Most if not all of the variable and function descriptions are showing
up in Japanese characters rather than English text.

Example: describe-var: cmail-new-arrivals-buffer

*cmail-new-arrivals-buffer's value is
" *cmail-new-arrivals*"

Documentation:
¿·¤·¤¤¥á¥¤¥ë(·²)¤òÃù¤á¤ë¥Ð¥Ã¥Õ¥¡(ºî¶ÈÍÑ).

Other stuff:
Emacs: Emacs21, 21.2-1

--- End Message ---
--- Begin Message ---
The cmail pacakge was removed from testing/unstable.
Closing the bugs.

Thanks,
--
Tatsuya Kinoshita


pgpiMnWOgU82k.pgp
Description: PGP signature
--- End Message ---

Bug#439234: marked as done (cmail: FTBFS: "emacs: Command not found" with xemacs21)

[Debian Bug Tracking System]

Your message dated Sun, 10 Feb 2008 22:05:05 +0900 (JST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs of cmail
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

--- Begin Message ---
Package: cmail
Version: 2.62-5
Severity: serious

cmail's Build-Depends-Indep is

  emacs21|xemacs21-mule-canna-wnn|xemacs21-mule

However, when xemacs21-mule is installed and emacs21 is not
installed, cmail fails to build from the source, because the source
uses the `emacs' command which is not provided by xemacs21-mule.


[...]
 debian/rules build
dh_testdir
# Add here commands to compile the package.
[ ! -f debian/patched ] && patch bbdb-cmail.el debian/bbdb-cmail.diff && touch 
debian/patched
patching file bbdb-cmail.el
/usr/bin/make
make[1]: Entering directory `/tmp/buildd/cmail-2.62'
emacs -batch -q -no-site-file -l CMAIL-MK -f compile-cmail \
NONE NONE NONE NONE
make[1]: emacs: Command not found
make[1]: *** [elc] Error 127
make[1]: Leaving directory `/tmp/buildd/cmail-2.62'
make: *** [build-stamp] Error 2


To fix this bug, please use `emacs' or `emacs | emacs22 | emacs21'
in Build-Depends-Indep.

Thanks,
--
Tatsuya Kinoshita


pgpH1ASH6kqwm.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
The cmail pacakge was removed from testing/unstable.
Closing the bugs.

Thanks,
--
Tatsuya Kinoshita


pgp3BJ1mt9OJv.pgp
Description: PGP signature
--- End Message ---

Bug#348515: marked as done (cmail: Fails to install)

[Debian Bug Tracking System]

Your message dated Sun, 10 Feb 2008 22:05:05 +0900 (JST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs of cmail
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

--- Begin Message ---
Package: cmail
Version: 2.62-3
Severity: normal

Cmail fails to install.

It puts up the "byte-compiling" message, then complains about not being
able to move *.elc files, and fails.




-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-rc5
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)

Versions of packages cmail depends on:
ii  apel   10.6+0.20050606-1 portable library for emacsen
ii  emacs2121.4a-3   The GNU Emacs editor

Versions of packages cmail recommends:
ii  semi 1.14.6+0.20050510-1 library to provide MIME feature fo

-- no debconf information

--- End Message ---
--- Begin Message ---
The cmail pacakge was removed from testing/unstable.
Closing the bugs.

Thanks,
--
Tatsuya Kinoshita


pgpFge0KGk92I.pgp
Description: PGP signature
--- End Message ---

Processed: 418918 not fixed

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> notfixed 418918 0.28-2.1
Bug#418918: ifplugd.rules executable
Bug no longer marked as fixed in version 0.28-2.1.

> 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#418918: ifplugd.rules executable

[Y Giridhar Appaji Nag]

On 07/04/12 14:50 -0400, Joey Hess said ...
> Version: 0.28-2.3
> 
> The udev rules file is executable, and shouldn't be.

The file is being installed with -m 644 since 0.28-2.1 but changes were
not made to postinst.  I am updating the package and will include a fix
for this.

Giridhar

-- 
Y Giridhar Appaji Nag | http://www.appaji.net/


signature.asc
Description: Digital signature

Processed: Re: ifplugd.rules executable

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Bcc: control
> tags 418918 + patch
Bug#418918: ifplugd.rules executable
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#418918: ifplugd.rules executable

[Y Giridhar Appaji Nag]

# Bcc: control
tags 418918 + patch
thanks

On 08/02/10 19:29 +0530, Y Giridhar Appaji Nag said ...
> The file is being installed with -m 644 since 0.28-2.1 but changes were
> not made to postinst.  I am updating the package and will include a fix
> for this.

Doing this in the preinst file, on upgrade.  Does this look OK?

$ svn diff debian/ifplugd.preinst
Index: debian/ifplugd.preinst
===
--- debian/ifplugd.preinst  (revision 7805)
+++ debian/ifplugd.preinst  (working copy)
@@ -23,6 +23,10 @@
mv /etc/apm/script.d/ifplugd /etc/apm/script.d/ifplugd.dpkg-old
fi
 
+   # change permissions of the old /etc/udev/ifplugd.rules
+   if [ -f /etc/udev/ifplugd.rules ] ; then
+   chmod 644 /etc/udev/ifplugd.rules
+   fi
;;
 # install|abort-upgrade)

-- 
Y Giridhar Appaji Nag | http://www.appaji.net/


signature.asc
Description: Digital signature

Processed: Bugs fixed in svn

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # ifplugd bugs fixes in svn
> tags 213910 + pending
Bug#213910: Debconf question about options points to possibly not-yet-existing 
documentation sources
There were no tags set.
Bug#319727: debconf questions are not useful
Tags added: pending

> tags 418918 + pending
Bug#418918: ifplugd.rules executable
Tags were: patch
Tags added: pending

> tags 393185 + pending
Bug#393185: ifplugd.8.gz: name of default file wrong
There were no tags set.
Tags added: pending

> 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]

Processing of lineakd_0.9-4_i386.changes

[Archive Administrator]

lineakd_0.9-4_i386.changes uploaded successfully to localhost
along with the files:
  lineakd_0.9-4.dsc
  lineakd_0.9-4.diff.gz
  lineakd_0.9-4_i386.deb
  liblineak-0.9-0_0.9-4_i386.deb
  liblineak-dev_0.9-4_i386.deb

Greetings,

Your Debian queue daemon


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

lineakd_0.9-4_i386.changes ACCEPTED

[Debian Installer]

Accepted:
liblineak-0.9-0_0.9-4_i386.deb
  to pool/main/l/lineakd/liblineak-0.9-0_0.9-4_i386.deb
liblineak-dev_0.9-4_i386.deb
  to pool/main/l/lineakd/liblineak-dev_0.9-4_i386.deb
lineakd_0.9-4.diff.gz
  to pool/main/l/lineakd/lineakd_0.9-4.diff.gz
lineakd_0.9-4.dsc
  to pool/main/l/lineakd/lineakd_0.9-4.dsc
lineakd_0.9-4_i386.deb
  to pool/main/l/lineakd/lineakd_0.9-4_i386.deb


Override entries for your package:
liblineak-0.9-0_0.9-4_i386.deb - optional libs
liblineak-dev_0.9-4_i386.deb - optional libdevel
lineakd_0.9-4.dsc - source x11
lineakd_0.9-4_i386.deb - optional x11

Announcing to [EMAIL PROTECTED]
Closing bugs: 417373 


Thank you for your contribution to Debian.


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

Bug#417373: marked as done (FTBFS with GCC 4.3: missing #includes)

[Debian Bug Tracking System]

Your message dated Sun, 10 Feb 2008 16:02:06 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#417373: fixed in lineakd 1:0.9-4
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

--- Begin Message ---
Package: lineakd
Version: 1:0.9-3
Usertags: ftbfs-gcc-4.3
Tags: patch

Your package fails to build with GCC 4.3.  Version 4.3 has not been
released yet but I'm building with a snapshot in order to find errors
and give people an advance warning.  In GCC 4.3, the C++ header
dependencies have been cleaned up.  The advantage of this is that
programs will compile faster.  The downside is that you actually
need to directly #include everything you use (but you really should
do this anyway, otherwise your program won't work with any compiler
other than GCC).  Some background of this can be found at
http://gcc.gnu.org/PR28080

You can reproduce this problem with gcc-snapshot (20070326-1 or higher)
from unstable.

> Automatic build of lineakd_1:0.9-3 on coconut0 by sbuild/ia64 0.49
...
> ../lineak/lbutton.h:46: warning: type qualifiers ignored on function return 
> type
> xmgr.cpp: In constructor 'Xmgr::Xmgr(std::string)':
> xmgr.cpp:46: warning: cast from 'const char*' to '*' 
> increases required alignment of target type
> xmgr.cpp: In member function 'void Xmgr::openXkbDisplay(std::string)':
> xmgr.cpp:78: error: 'malloc' was not declared in this scope
> xmgr.cpp:82: error: 'free' was not declared in this scope
> xmgr.cpp: In member function 'void Xmgr::commitXKBChanges(int)':
> xmgr.cpp:126: warning: conversion to 'KeyCode' from 'int' may alter its value
> xmgr.cpp: In member function 'void Xmgr::setXKBKey(int, KeySym)':
> xmgr.cpp:172: warning: conversion to 'KeyCode' from 'int' may alter its value
> xmgr.cpp: At global scope:
> xmgr.cpp:194: warning: unused parameter 'theDisplay'
> xmgr.cpp: In member function 'bool Xmgr::getModifiers()':
> xmgr.cpp:235: warning: conversion to 'unsigned int' from 'int' may alter its 
> value
> xmgr.cpp:237: warning: conversion to 'unsigned int' from 'int' may alter its 
> value
> xmgr.cpp: In member function 'bool Xmgr::initialize(LKbd&)':
> xmgr.cpp:285: warning: conversion to 'long int' from 'long unsigned int' may 
> alter its value
> xmgr.cpp:322: error: 'exit' was not declared in this scope

--- lineak/xmgr.cpp~2007-04-02 13:17:31.0 +
+++ lineak/xmgr.cpp 2007-04-02 13:17:39.0 +
@@ -21,6 +21,7 @@
 #include 
 
 extern "C" {
+   #include 
#include 
#include 
#include 
--- lineak/defloader.h~ 2007-04-02 13:20:35.0 +
+++ lineak/defloader.h  2007-04-02 13:20:47.0 +
@@ -23,6 +23,7 @@
 #   endif
 
 #   include 
+#   include 
 #   include 
 
 class LDef;

-- 
Martin Michlmayr
http://www.cyrius.com/

--- End Message ---
--- Begin Message ---
Source: lineakd
Source-Version: 1:0.9-4

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

liblineak-0.9-0_0.9-4_i386.deb
  to pool/main/l/lineakd/liblineak-0.9-0_0.9-4_i386.deb
liblineak-dev_0.9-4_i386.deb
  to pool/main/l/lineakd/liblineak-dev_0.9-4_i386.deb
lineakd_0.9-4.diff.gz
  to pool/main/l/lineakd/lineakd_0.9-4.diff.gz
lineakd_0.9-4.dsc
  to pool/main/l/lineakd/lineakd_0.9-4.dsc
lineakd_0.9-4_i386.deb
  to pool/main/l/lineakd/lineakd_0.9-4_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.
Frank Lichtenheld <[EMAIL PROTECTED]> (supplier of updated lineakd 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: Sun, 10 Feb 2008 15:04:22 +0100
Source: lineakd
Binary: lineakd liblineak-0.9-0 liblineak-dev
Architecture: source i386
Version: 1:0.9-4
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group <[EMAIL PROTECTED]>
Changed-By: Frank Lichtenheld <[EMAIL PROTECTED]>
Description: 
 liblineak-0.9-0 - LinEAK development files
 liblineak-dev - LinEAK development files
 lineakd- Linux support for Easy Access and Internet Keyboards
Closes: 417373
Changes: 
 lineakd (1:0.9-4) unstable; urgency=low
 .
   * QA Upload
   * Build-depend on automake i

Processed: bloub

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> clone 460797 -1
Bug#460797: libgtk-perl: your package depends from gnome-libs that is scheduled 
for removal
Bug 460797 cloned as bug 465097.

> reassign -1 ftp.debian.org
Bug#465097: libgtk-perl: your package depends from gnome-libs that is scheduled 
for removal
Bug reassigned from package `libgtk-perl' to `ftp.debian.org'.

> retitle -1 RM: libgtk-perl -- RoQA; obsolete, gnome 1.x
Bug#465097: libgtk-perl: your package depends from gnome-libs that is scheduled 
for removal
Changed Bug title to `RM: libgtk-perl -- RoQA; obsolete, gnome 1.x' from 
`libgtk-perl: your package depends from gnome-libs that is scheduled for 
removal'.

> severity -1 normal
Bug#465097: RM: libgtk-perl -- RoQA; obsolete, gnome 1.x
Severity set to `normal' from `serious'

> reassign 460787 ftp.debian.org
Bug#460787: libglade: your package depends from gnome-libs that is scheduled 
for removal
Bug reassigned from package `libglade' to `ftp.debian.org'.

> retitle 460787 RM: libglade -- RoQA; obsolete, gnome 1.x
Bug#460787: libglade: your package depends from gnome-libs that is scheduled 
for removal
Changed Bug title to `RM: libglade -- RoQA; obsolete, gnome 1.x' from 
`libglade: your package depends from gnome-libs that is scheduled for removal'.

> severity 460787 normal
Bug#460787: RM: libglade -- RoQA; obsolete, gnome 1.x
Severity set to `normal' from `serious'

> block 460787 by 460786
Bug#460786: gtkgrepmail: your package depends from gnome-libs that is scheduled 
for removal
Bug#460787: RM: libglade -- RoQA; obsolete, gnome 1.x
Was not blocked by any bugs.
Blocking bugs of 460787 added: 460786

> block -1 by 460786
Bug#460786: gtkgrepmail: your package depends from gnome-libs that is scheduled 
for removal
Bug#465097: RM: libgtk-perl -- RoQA; obsolete, gnome 1.x
Was not blocked by any bugs.
Blocking bugs of 465097 added: 460786

>
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: blob

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> clone 460782 -1
Bug#460782: gnome-print: your package depends from gnome-libs that is scheduled 
for removal
Bug 460782 cloned as bug 465098.

> severity -1 normal
Bug#465098: gnome-print: your package depends from gnome-libs that is scheduled 
for removal
Severity set to `normal' from `serious'

> reassign -1 ftp.debian.org
Bug#465098: gnome-print: your package depends from gnome-libs that is scheduled 
for removal
Bug reassigned from package `gnome-print' to `ftp.debian.org'.

> retitle -1 RM: gnome-print -- RoQA; obsolete
Bug#465098: gnome-print: your package depends from gnome-libs that is scheduled 
for removal
Changed Bug title to `RM: gnome-print -- RoQA; obsolete' from `gnome-print: 
your package depends from gnome-libs that is scheduled for removal'.

> block -1 by 460791
Bug#460791: terraform: your package depends from gnome-libs that is scheduled 
for removal
Bug#465098: RM: gnome-print -- RoQA; obsolete
Was not blocked by any bugs.
Blocking bugs of 465098 added: 460791, 464337

>
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#408366: marked as done (ifplugd: doesn't pass iwconfig arguments to wifi card and avoids ifup to work)

[Debian Bug Tracking System]

Your message dated Sun, 10 Feb 2008 23:45:37 +0530
with message-id <[EMAIL PROTECTED]>
and subject line Close bug #408366
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

--- Begin Message ---

Package: ifplugd
Version: 0.28-2.2
Severity: important

*** Please type your report below this line ***
Hi All,

after upgrading ifplugd I have found impossible to connect 
on my
wireless LAN even giving the command ifup eth1 in the 
console. I've tried previous version of the rt2500 driver 
and other things, just to be sure that the bug it's not 
related to other software/driver.
I've tried to use iwconfig directly and it works (same 
options in the
/etc/network/interface file). Then I've tried the testing 
package of
ifplugd and it works and ifup eth1 works too. Removing the 
package also
makes to work ifup eth1 command. Installing the unstable 
version of

ifplugd reproduces the same problems.

This is my /etc/network/interface:
# This file describes the network interfaces available on 
your system
# and how to activate them. For more information, see 
interfaces(5).


# The loopback network interface
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

# This is a list of hotpluggable network interfaces.
# They will be activated automatically by the hotplug 
subsystem.


mapping hotplug
script grep
map eth0
map eth1

iface eth0 inet dhcp


iface eth1 inet dhcp
wireless-ap 00:14:A9:9C:F2:91
wireless-key s:X open

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (700, 'unstable'), (600, 'testing'), (1, 
'experimental')

Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.19.2
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] 
(charmap=ISO-8859-15)


Versions of packages ifplugd depends on:
ii  debconf [debconf-2.0]   1.5.11   Debian 
configuration management sy
ii  libc6   2.3.6.ds1-10 GNU C 
Library: Shared libraries
ii  libdaemon0  0.10-1   lightweight C 
library for daemons


Versions of packages ifplugd recommends:
ii  ifupdown  0.6.8  high level 
tools to configure netw


-- debconf information:
* ifplugd/interfaces: eth0
* ifplugd/hotplug_interfaces: eth1
* ifplugd/args: -q -f -u0 -d10 -w -I
  ifplugd/suspend_action: stop

--- End Message ---
--- Begin Message ---
On 07/03/05 12:55 +0100, Valerio Passini said ...
> I've found that this bug is experienced by many owners of wireless cards 
> based upon the chipset Ralink and the latest versions of its drivers, see 
> these bug reports on rt2500-source:
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=411703
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=413158
>
> Sorry for the mistake, I suggest to close this bug or to merge with the 
> above mentioned bugs.

Hence closing this bug.

Giridhar

-- 
Y Giridhar Appaji Nag | http://www.appaji.net/


signature.asc
Description: Digital signature
--- End Message ---

Bug#348698: marked as done (ifplugd: does not correctly run if-up / if-down when network links go up / down)

[Debian Bug Tracking System]

Your message dated Sun, 10 Feb 2008 23:52:02 +0530
with message-id <[EMAIL PROTECTED]>
and subject line Information update
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

--- Begin Message ---
Package: ifplugd
Version: 0.26-2.1
Severity: important


If have a laptop with 2 network interfaces: eth0 (realtek Ethernet), 
and eth1 (ipw2200). 

I dist-upgraded from sarge to testing (etch). Everything seemed to work right 
after upgrade. Then, I installed ifplugd.

After several trials, I have configured ifplugd to manage eth0 eth1 as 
"HOTPLUG_INTERFACES". The reason is ifplugd cannot detect link beat for eth1 
(although the wireless network is properly configured, wpa_supplicant, etc...
may be that is another bug...). Interface eth0 is correctly detected if I use 
"INTERFACES", all this bug request comes from wanting eth1 to be detected.

I have also added the required "allow-hotplug eth0" "allow-hotplug eth1" lines 
to my /etc/network/interfaces.


Well, the point is with that if-up / if-down never get called when a link
goes up/down. In fact, they become "up" at boot time and remain in that state 
unless I directly perform if-up / if-down. Link beats get correctly detected
though (now including eth1 --> that's why I want this "hotplug" config). 

If I configure eth0 to be in "INTERFACES" and eth1 to be in 
"HOTPLUG_INTERFACES" the problem remains, now only for eth1 (if-up / if-down 
never called on eth1).

I have read bug 334876, and it seems this may be related to that (I suspect 
ifplugd script for hotplug - now udev - never gets called). However, it seems
my current version of ifplugd includes patch to solve that bug?

Therefore, I have no clue about this behaviour. Any ideas?



-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages ifplugd depends on:
ii  debconf   1.4.67 Debian configuration management sy
ii  libc6 2.3.5-8GNU C Library: Shared libraries an
ii  libdaemon00.10-1 lightweight C library for daemons

Versions of packages ifplugd recommends:
ii  ifupdown  0.6.7  high level tools to configure netw

-- debconf information:
* ifplugd/interfaces:
* ifplugd/hotplug_interfaces: eth0 eth1
* ifplugd/args: -q -f -u0 -d10 -w -I
* ifplugd/suspend_action: stop

--- End Message ---
--- Begin Message ---
On 06/03/10 00:32 +0100, Daniel Rodriguez Garcia said ...
> Now I must inform ifplugd works correctly for me (I only had problem
> with my eth1 wireless lan interface - ipw2200).

[snip...]

> Summarizing, I include my current configuration (which is working
> correctly):
> 
> --- /etc/default/ifplugd:
> 
> INTERFACES="eth0 eth1"
> HOTPLUG_INTERFACES=""
> ARGS="-q -f -u0 -d10 -w -I"
> SUSPEND_ACTION="stop"
> 
> ---
> --- /etc/default/wpasupplicant:
> 
> ENABLED=1
> DRIVER=wext
> INTERFACE=eth1
> CONFIG=/etc/wpa_supplicant.conf
> OPTIONS="-w -i ${INTERFACE} -D ${DRIVER} -c ${CONFIG}"
> 
> ---
> ^^ Note that the -w option is IMPORTANT

-- 
Y Giridhar Appaji Nag | http://www.appaji.net/


signature.asc
Description: Digital signature
--- End Message ---

Processed: bugs fixed in svn

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> tags 404955 + pending
Bug#404955: ifplugd: Starts daemon even for non-existing static interfaces
Tags were: patch
Tags added: pending

> tags 368797 + pending
Bug#368797: /etc/init.d/ifplugd should shebang /bin/sh
Tags were: patch
Tags added: pending

> 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#328117: marked as done (Typo in debconf screen ifplugd/suspend_action)

[Debian Bug Tracking System]

Your message dated Mon, 11 Feb 2008 00:03:24 +0530
with message-id <[EMAIL PROTECTED]>
and subject line Typo in debconf screen ifplugd/suspend_action
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

--- Begin Message ---
Package: ifplugd
Version: 0.26-2
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Hi there,

ifconfd mentions the package 'gueesnet' in ifplugd/suspend_action.

This should be 'guessnet'.

Cheers,
Neil
- -- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-686
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)

Versions of packages ifplugd depends on:
ii  debconf   1.4.58 Debian configuration management sy
ii  libc6 2.3.5-6GNU C Library: Shared libraries an
ii  libdaemon00.8-1  lightweight C library for daemons

Versions of packages ifplugd recommends:
ii  ifupdown  0.6.7  high level tools to configure netw

- -- debconf information excluded

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

iD8DBQFDJweu97LBwbNFvdMRAk9mAJ90DMDiNBFq/uJmV75F7jKd9gfVjACeJsZd
U2Ls6+mTBGVQGvGDBmT8MC8=
=MUtf
-END PGP SIGNATURE-

--- End Message ---
--- Begin Message ---
On 05/09/13 17:09 +, Neil McGovern said ...
> mentions the package 'gueesnet' in ifplugd/suspend_action.
> 
> This should be 'guessnet'.

This was fixed (I don't know which version -- most likely in one of the
three 0.28-2.X NMUs).  But the bug was not marked as done.

Giridhar

-- 
Y Giridhar Appaji Nag | http://www.appaji.net/


signature.asc
Description: Digital signature
--- End Message ---

Bug#454212: megahal segfaults as soon as it's launched

[Niko Tyni]

> Confirmed using etch i386 (though an amd64 processor). Attached output
> of megahal and strace.

The attached patch fixes a stack corruption issue on 64-bit architectures
(reading 8 bytes into a 4-byte buffer) and an off-by-one sprintf overflow
in the error and status file name initialization code.

The stack corruption makes megahal reliably crash for me on amd64 every
time it tries to load a saved dictionary.

However, the original problem is on i386 and happens earlier in the
initialization code. I can't reproduce it myself, but I think it might
well be caused by the sprintf overflow. Note that Neil's strace in

 
http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=27;filename=megahal.trace.log;att=1;bug=454212

has

 open("/home/nmcgovern/.megahal/megahal.logi", O_WRONLY|O_APPEND|O_CREAT, 0666) 
= 3

and

-rw-r--r--  1 nmcgovern users  380 2007-12-19 11:37 megahal.logi?

while the intended filename is "megahal.log". So there's definitely at
least some corruption happening here.

Could somebody (Neil?) try if the bug persists with this patch?

Cheers,
-- 
Niko Tyni   [EMAIL PROTECTED]
diff --git a/megahal.c b/megahal.c
index 9d4b3ae..cfb1bbc 100644
--- a/megahal.c
+++ b/megahal.c
@@ -417,7 +417,7 @@ void megahal_initialize(void)
 errorfp = stderr;
 statusfp = stdout;
 
-filenamebuff = (char *) malloc (strlen (directory) + 12);
+filenamebuff = (char *) malloc (strlen (directory) + strlen(SEP) + 12);
 
 sprintf(filenamebuff, "%s%s%s", directory, SEP, errorfilename);
 initialize_error(filenamebuff);
@@ -1384,7 +1384,7 @@ void save_dictionary(FILE *file, DICTIONARY *dictionary)
 void load_dictionary(FILE *file, DICTIONARY *dictionary)
 {
 register int i;
-int size;
+BYTE4 size;
 
 fread(&size, sizeof(BYTE4), 1, file);
 progress("Loading dictionary", 0, 1);

Bug#465098: fixed

[Debian Archive Maintenance]

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

gnome-print |0.37-14 | source
libgnomeprint-bin |0.37-14 | alpha, amd64, arm, armel, hppa, hurd-i386, 
i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc
libgnomeprint-data |0.37-14 | all
libgnomeprint-dev |0.37-14 | alpha, amd64, arm, armel, hppa, hurd-i386, 
i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc
libgnomeprint15 |0.37-14 | alpha, amd64, arm, armel, hppa, hurd-i386, i386, 
ia64, m68k, mips, mipsel, powerpc, s390, sparc

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

Packages are never removed from testing by hand.  Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED]

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[EMAIL PROTECTED]

Debian distribution maintenance software
pp.
Joerg Jaspert (the ftpmaster behind the curtain)

Bug#454212: megahal: Confirmed in etch

[Giuliani Vito, Ivan]

On Fri, Jan 25, 2008 at 02:58:01PM +0100, Laurent Fousse wrote:
> Hello,
> 
> * Neil McGovern [Wed, Dec 19, 2007 at 11:42:23AM +]:
> > Package: megahal
> > Version: 9.1.1a-1
> > Followup-For: Bug #454212
> > 
> > Confirmed using etch i386 (though an amd64 processor). Attached output
> > of megahal and strace.
> 
> Could you try a version with debugging symbols included and give me the
> backtrace? You can download one from
> 
> http://komite.net/laurent/tmp/megahal_9.1.1a-1_i386.deb
> 
> Thanks,
> 
> Laurent.

The backtrace is attached.

The megahal.brn file that it tries to open doesn't exists. Maybe it is
trying to make some read/write operation on it without checking if it
has been correctly opened?

-- 
Giuliani Vito, Ivan
http://zeta-puppis.com
[EMAIL PROTECTED]:~$ gdb megahal
GNU gdb 6.7.1-debian
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(gdb) run
Starting program: /usr/bin/megahal 
++
||
|  ##  ##    ####### |
|  ##  ##  #   ##   #  #   ##   #  #   #   ###   |
|  # ## #  #   #   ##  ##  ##  #  #   #  |
|  ##  #   #  ###  ##  ##  ##  #   #   #   ###   |
|  ##  #   ##  ##  ##  ##  ## #   #   #  |
|  ##  ##      ##  ##  ##  ### ###r6 |
||
|Copyright(C) 1998 Jason Hutchens|
++

Program received signal SIGSEGV, Segmentation fault.
0xb7e33cf6 in malloc_consolidate () from /lib/i686/cmov/libc.so.6
(gdb) bt
#0  0xb7e33cf6 in malloc_consolidate () from /lib/i686/cmov/libc.so.6
#1  0xb7e3571e in _int_free () from /lib/i686/cmov/libc.so.6
#2  0xb7e39380 in free () from /lib/i686/cmov/libc.so.6
#3  0xb7e24c50 in __fopen_internal () from /lib/i686/cmov/libc.so.6
#4  0xb7e24c8c in fopen@@GLIBC_2.1 () from /lib/i686/cmov/libc.so.6
#5  0x0804b8a2 in load_model (filename=0x8051238 
"/home/kratorius/.megahal/megahal.brn", model=0x8051268) at megahal.c:2008
#6  0x0804debc in load_personality (model=0x805086c) at megahal.c:3301
#7  0x0804e16a in change_personality (command=0x0, position=0, model=0x805086c) 
at megahal.c:3350
#8  0x08048fd0 in megahal_initialize () at megahal.c:454
#9  0x0804e49f in main (argc=1, argv=0xbfad3d94) at main.c:161
(gdb) quit
The program is running.  Exit anyway? (y or n) y

briquolo REMOVED from testing

[Debian testing watch]

FYI: The status of the briquolo source package
in Debian's testing distribution has changed.

  Previous version: 0.5.6-2
  Current version:  (not in testing)
  Hint: 
# 20080209
Bug #455784: briquolo: segfaults with new kernel

The script that generates this mail tries to extract removal
reasons from comments in the britney hint files. Those comments
were not originally meant to be machine readable, so if the
reason for removing your package seems to be nonsense, it is
probably the reporting script that got confused. Please check the
actual hints file before you complain about meaningless removals.

-- 
This email is automatically generated; [EMAIL PROTECTED] is responsible.
See http://people.debian.org/~henning/trille/ for more information.


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

astrolog REMOVED from testing

[Debian testing watch]

FYI: The status of the astrolog source package
in Debian's testing distribution has changed.

  Previous version: 5.40-3
  Current version:  (not in testing)
  Hint: 
# 20080209
Bug #444061: astrolog: Placalc code not distributable

The script that generates this mail tries to extract removal
reasons from comments in the britney hint files. Those comments
were not originally meant to be machine readable, so if the
reason for removing your package seems to be nonsense, it is
probably the reporting script that got confused. Please check the
actual hints file before you complain about meaningless removals.

-- 
This email is automatically generated; [EMAIL PROTECTED] is responsible.
See http://people.debian.org/~henning/trille/ for more information.


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