Bug#468896: support allow-ifplugd in /e/n/interfaces
Package: ifplugd Version: 0.28-4 Severity: wishlist Here is better integration idea for ifplugd to ifupdown and other network scripts. Currently, ifplugd uses -i option to specify interfaces to control. Actually, debconf stores them for each occasion in /e/default/ifplugd as: INTERFACES="" HOTPLUG_INTERFACES="" Since recent ifupdown started using "allow-[CLASS]", it may be a good idea to support "allow-ifplugd-auto" stanza and "allow-ifplugd-hotplug" which specify interfaces for each types. (I think current debconf script needs to be changed though) Since these [CLASS] are not used by other programs, it means nothing to others and I think no new code need to be written for ifupdown. With this entry, you only need to see /e/n/interfaces to know which interfaces are controled by which program. * auto or allow-auto: boot script of ifupdown * allow-hotplug: hotplug script (probably run bu udev) * allow-ifplugd-auto: boot script of ifplugd * allow-ifplugd-hotplug": hotplug script (probably run bu udev) which invoke ifplugd I think similar idea can be deployed for waproamd too. Then configuration is much more clear. Please note this idea has not been fully tested. -- 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/2 CPU cores) 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 ifplugd depends on: ii debconf [debconf-2.0] 1.5.19 Debian configuration management sy ii libc6 2.7-9 GNU C Library: Shared libraries ii libdaemon00.12-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: * ifplugd/hotplug_interfaces: * ifplugd/args: -q -f -u0 -d10 -w -I * ifplugd/suspend_action: stop -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#447066: fixed
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: om |0.2.0-4 | source, armel, m68k om | 0.2.0-4+b1 | alpha, amd64, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc om-gtk |0.2.0-4 | armel, m68k om-gtk | 0.2.0-4+b1 | alpha, amd64, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc om-patches |0.2.0-4 | all 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#466123: fixed
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: ladder.app | 1.0-2 | hurd-i386 ladder.app | 1.0-2+b1 | m68k ladder.app | 1.0-4 | source, alpha, amd64, arm, hppa, i386, ia64, 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#466125: fixed
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: lapispuzzle.app | 1.0-2 | hurd-i386 lapispuzzle.app | 1.0-2+b1 | m68k lapispuzzle.app | 1.0-4 | source, alpha, amd64, arm, hppa, i386, ia64, 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)
Processed: fixed in svn and uploaded to mentors
Processing commands for [EMAIL PROTECTED]: > # ITA - uploaded to mentors > tags 452184 + pending Bug#452184: ITA: ifplugd -- A configuration daemon for ethernet devices There were no tags set. Tags added: pending > # Fixed in Debian SVN: collab-maint/ext-maint/ifplugd > tags 360464 + pending Bug#360464: ifplugd: leaves file after upgraded from sarge and purged There were no tags set. Bug#461395: Does not remove ifplugd.hotplug on package upgrades 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#468996: python-oss: may use different memory API for a given memory block
Package: python-oss
Severity: important
User: [EMAIL PROTECTED]
Usertags: goal-python2.5
The C API requires using the same memory API for a given memory block,
which will show up as a segfault, at least in python2.5. This code was
found by a search of all sources build-depending on python-dev, having
a PyObject_ function for allocation and a PyMem_ function for
deallocation in the same file. This may be a real problem, or a false
positive.
The most common error seen is of the form:
PyObject *
new_wadobject(WadFrame *f, int count) {
wadobject *self;
self = PyObject_NEW(wadobject, &WadObjectType);
[...]
}
static void
wadobject_dealloc(wadobject *self) {
PyMem_DEL(self);
}
This particular example can be fixed with replacing PyMem_DEL with
PyObject_Del.
For more information, see
http://docs.python.org/api/memory.html
http://docs.python.org/api/memoryExamples.html
Please set the severity of this report to "serious", if it is a real
problem, please close the report if it is a false positive. Ask
the [EMAIL PROTECTED] ML for help. Archive of the
search results: http://ftp-master.debian.org/~he/affected-files.tar.gz
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 243363 is grave
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.16 > severity 243363 grave Bug#243363: xcruise: speed goes wild and segfaults on keypress Severity set to `grave' from `important' > 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: tagging 345364
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.16 > tags 345364 - pending Bug#345364: usbmount fails if /var/run/usbmount does not exist Tags were: pending Tags removed: 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]
Processed: tagging 243363
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.16 > tags 243363 - unreproducible Bug#243363: xcruise: speed goes wild and segfaults on keypress Tags were: patch upstream help unreproducible Tags removed: unreproducible > 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#374107: fixed
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: debpartial | 0+20030508.1 | source, all 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. Thomas Viehmann (the ftpmaster behind the curtain)
Bug#399255: fixed
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: adduser-ng |0.1.2-3 | source, all adduser-ng-doc |0.1.2-3 | all adduser-ng-doc-devel |0.1.2-3 | all adduser-plugin-bkdinit |0.1.2-3 | all adduser-plugin-cvsaccess |0.1.2-3 | all adduser-plugin-eximconf |0.1.2-3 | all adduser-plugin-eximconf4 |0.1.2-3 | all adduser-plugin-notifyjabber |0.1.2-3 | all adduser-plugin-quota |0.1.2-3 | all adduser-ui-cdk |0.1.2-3 | all libadduser-pluginloader-perl |0.1.2-3 | all 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. Thomas Viehmann (the ftpmaster behind the curtain)
Bug#377923: fixed
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: cl-tclink |3.3.1-3 | hurd-i386 cl-tclink |3.3.1-4 | source, alpha, amd64, arm, armel, hppa, 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. Thomas Viehmann (the ftpmaster behind the curtain)
Bug#327667: fixed
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: isic | 0.06-1 | source, alpha, amd64, arm, armel, hppa, 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. Thomas Viehmann (the ftpmaster behind the curtain)
megahal 9.1.1a-5 MIGRATED to testing
FYI: The status of the megahal source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 9.1.1a-5 -- 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]
lineak-xosdplugin 1:0.9-5 MIGRATED to testing
FYI: The status of the lineak-xosdplugin source package in Debian's testing distribution has changed. Previous version: 1:0.9-4 Current version: 1:0.9-5 -- 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]
Bug#465349: metamail: bashism in /bin/sh script
Some others: > possible bashism in ./usr/bin/patch-metamail line 62 ($HOST(TYPE|NAME)): > echo from the host $HOSTNAME, in the directory $DIRNAME, > possible bashism in ./usr/bin/patch-metamail line 73 ($HOST(TYPE|NAME)): > open $HOSTNAME Cheers, -- 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]
