Deeper penetrator!
Super-size dreams come true! http://gbjaz.positionself.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of python-oss_0.0.0.20010624-5_i386.changes
python-oss_0.0.0.20010624-5_i386.changes uploaded successfully to localhost along with the files: python-oss_0.0.0.20010624-5.dsc python-oss_0.0.0.20010624-5.diff.gz python-oss_0.0.0.20010624-5_i386.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
python-oss_0.0.0.20010624-5_i386.changes ACCEPTED
Accepted: python-oss_0.0.0.20010624-5.diff.gz to pool/main/p/python-oss/python-oss_0.0.0.20010624-5.diff.gz python-oss_0.0.0.20010624-5.dsc to pool/main/p/python-oss/python-oss_0.0.0.20010624-5.dsc python-oss_0.0.0.20010624-5_i386.deb to pool/main/p/python-oss/python-oss_0.0.0.20010624-5_i386.deb Override entries for your package: python-oss_0.0.0.20010624-5.dsc - source python python-oss_0.0.0.20010624-5_i386.deb - optional python Announcing to [EMAIL PROTECTED] Closing bugs: 468996 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#468996: marked as done (python-oss: may use different memory API for a given memory block)
Your message dated Tue, 04 Mar 2008 17:02:11 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#468996: fixed in python-oss 0.0.0.20010624-5
has caused the Debian Bug report #468996,
regarding python-oss: may use different memory API for a given memory block
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.)
--
468996: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468996
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: python-oss
Source-Version: 0.0.0.20010624-5
We believe that the bug you reported is fixed in the latest version of
python-oss, which is due to be installed in the Debian FTP archive:
python-oss_0.0.0.20010624-5.diff.gz
to pool/main/p/python-oss/python-oss_0.0.0.20010624-5.diff.gz
python-oss_0.0.0.20010624-5.dsc
to pool/main/p/python-oss/python-oss_0.0.0.20010624-5.dsc
python-oss_0.0.0.20010624-5_i386.deb
to pool/main/p/python-oss/python-oss_0.0.0.20010624-5_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.
Thomas Viehmann <[EMAIL PROTECTED]> (supplier of updated python-oss 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: Tue, 04 Mar 2008 17:21:29 +0100
Source: python-oss
Binary: python-oss
Architecture: source i386
Version: 0.0.0.20010624-5
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group <[EMAIL PROTECTED]>
Changed-By: Thomas Viehmann <[EMAIL PROTECTED]>
Description:
python-oss - Open Sound System (OSS) interface for Python
Closes: 468996
Changes:
python-oss (0.0.0.20010624-5) unstable; urgency=low
.
* QA upload
* Fix memory management. Closes: #468996
* Fix debian/substvars overwriting after dpkg-shlibs in debian/rules.
* Fix description (python -> Python).
Files:
75c445937b6024c7563cbb9f746350bf 654 python optional
python-oss_0.0.0.20010624-5.dsc
a11dbcb882b542b14d4ad571575e343d 5307 python optional
python-oss_0.0.0.20010624-5.diff.gz
f0b7905e4926d3ce735ae8232639a9b5 39614 python optional
python-oss_0.0.0.20010624-5_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHzX25riZpaaIa1PkRAkC2AJsE7aZl4v5UbiTNQYsineHzfn4HqQCg+Drl
CGriWtItvqcyH1ikW6hyRSA=
=WYHn
-END PGP SIGNATURE-
--- End Message ---
c-sig 3.8-12 MIGRATED to testing
FYI: The status of the c-sig source package in Debian's testing distribution has changed. Previous version: 3.8-11 Current version: 3.8-12 -- 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]
Processed: Re: Bug#455154: FTBFS with GCC 4.3: missing #includes
Processing commands for [EMAIL PROTECTED]: > tag 455154 patch Bug#455154: FTBFS with GCC 4.3: missing #includes 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#455154: FTBFS with GCC 4.3: missing #includes
tag 455154 patch thanks Martin Michlmayr <[EMAIL PROTECTED]> (08/12/2007): > Package: pouetchess > Version: 0.2.0-1 > Usertags: ftbfs-gcc-4.3 Hi, please find attached a patch to fix this FTBFS. Cheers, -- Cyril Brulebois --- a/src/sxmlgui/XMLUtils.h +++ b/src/sxmlgui/XMLUtils.h @@ -56,6 +56,8 @@ #define TIXML_ISTREAM std::istream #define TIXML_OSTREAM std::ostream +#include + class TiXmlDocument; class TiXmlElement; class TiXmlComment; signature.asc Description: Digital signature
Processed: Re: Bug#455178: FTBFS with GCC 4.3: missing #includes
Processing commands for [EMAIL PROTECTED]: > tag 455178 patch Bug#455178: FTBFS with GCC 4.3: missing #includes 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#455178: FTBFS with GCC 4.3: missing #includes
tag 455178 patch thanks Martin Michlmayr <[EMAIL PROTECTED]> (09/12/2007): > Package: unalz > Version: 0.55-4 > Usertags: ftbfs-gcc-4.3 Hi, please find attached a patch for this FTBFS. Cheers, -- Cyril Brulebois --- a/UnAlz.h +++ b/UnAlz.h @@ -98,6 +98,7 @@ #include #include +#include using namespace std; signature.asc Description: Digital signature
Bug#335744: ifplugd breaks IPW2200
Hi Hadmut, The submitter Email ID on this bug is bouncing, can you look at my previous comment on this bug and respond? Giridhar On 08/03/05 11:09 +0530, Y Giridhar Appaji Nag said ... > guessing you would still be able to reproduce this bug, can you help me > triage this with more information? -- Y Giridhar Appaji Nag | http://www.appaji.net/ signature.asc Description: Digital signature
Bug#374253: ifplugd: Annoying "dpkg --compare-versions" warnings upon installation
Hi Sukant, On 06/06/18 01:21 -0500, Sukant Hajra said ... > the output of an installation. The problem seems to be the postinst > script which has some "dpkg --compare-versions" calls. I briefly looked > at the script, but didn't figure out what exactly is wrong. The script looks OK to me too. I wonder if this was a minor bug in the dpkg version in use then (I did not dig deeper). Are you still able to reproduce this problem? > Preconfiguring packages ... > dpkg: --compare-versions takes three arguments: > > Setting up ifplugd (0.28-2) ... > dpkg: --compare-versions takes three arguments: I was reading Debian policy (6.7 Details of configuration) and noticed this: "When we configure a package (this happens with dpkg --install and dpkg --configure), we first update any conffiles and then call: postinst configure most-recently-configured-version No attempt is made to unwind after errors during configuration. If the configuration fails, the package is in a "Failed Config" state, and an error message is generated. If there is no most recently configured version dpkg will pass a null argument. [41]" And we are checking 'if [ -z "$2" ]' which would be true in case of a fresh install (which is what your scenario is). I recently took up maintenance of ifplugd and since this is a fairly old bug, if you are not able to reproduce to it, I would be inclined to close it. Please do let me know :) Cheers, Giridhar -- Y Giridhar Appaji Nag | http://www.appaji.net/ signature.asc Description: Digital signature
Bug#335744: ifplugd breaks IPW2200
Hi Hadmut, On 05/10/25 20:07 +0200, Hadmut Danisch said ... > I have a notebook with a centrino 54 MBit WLAN device and use the > IPW2200 driver. I am using ifplugd on a IBM T43 and use the ipw2200 driver. > Association does not work if I use the ifplugd (while it works on a > different Notebook with IPW2100). Can you please explain what you mean by association not working? Are you using waproamd / wpasupplicant for configuring wireless? Can you send across the configuration of that too along with the configuration of ifplugd that you use (/etc/default/ifplugd and any other config files that you may have modified). > I saw that ifplugd 0.28 is available, maybe it already solved the > problem. What about updating the debian package? 0.28 has an extra --no-startup and build fixes over 0.26, so I am guessing you would still be able to reproduce this bug, can you help me triage this with more information? Cheers, Giridhar -- Y Giridhar Appaji Nag | http://www.appaji.net/ signature.asc Description: Digital signature
Bug#437406: marked as done (list /etc/default/ifplugd)
Your message dated Wed, 5 Mar 2008 10:59:30 +0530 with message-id <[EMAIL PROTECTED]> and subject line Re: list /etc/default/ifplugd has caused the Debian Bug report #437406, regarding list /etc/default/ifplugd 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.) -- 437406: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=437406 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: ifplugd Version: 0.28-2.3 Severity: wishlist As opposed to other files in /etc/default/, dlocate cannot find /etc/default/ifplugd. --- End Message --- --- Begin Message --- On 07/08/12 17:34 +0800, Dan Jacobson said ... > As opposed to other files in /etc/default/, dlocate cannot find > /etc/default/ifplugd. I am afraid this is true for all configuration files that are handled by debconf. For example see /etc/default/portmap from the portmap package. And from what I understand, dlocate uses the information from /var/lib/dpkg/info/ and files created by debconf are not listed in there. $ dpkg -S /etc/default/ifplugd dpkg: /etc/default/ifplugd not found. I haven't looked deeper into this, but I am not sure if this can be fixed globally (maybe something can be done in debconf to assist this?). Hence marking this as done. Cheers, Giridhar -- Y Giridhar Appaji Nag | http://www.appaji.net/ signature.asc Description: Digital signature --- End Message ---
Bug#381675: marked as done (Pb ifplugd + NFS mount in fstab)
Your message dated Wed, 5 Mar 2008 12:08:35 +0530 with message-id <[EMAIL PROTECTED]> and subject line Re: Pb ifplugd + NFS mount in fstab has caused the Debian Bug report #381675, regarding Pb ifplugd + NFS mount in fstab 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.) -- 381675: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=381675 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: ifplugd Version: 0.28-2 Severity: normal Hi, ifplugd works well on my pc! thx for that! but I have a pb with NFS mount in /etc/fstab. I don't have "auto eth0" in my /etc/network/interfaces, so the mount of my NFS exports fails at boot. I know I can use autofs (it works), but I prefer the mount at boot. Do you have any idea to solve that? Thx a lot Guillaume -- 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.17.7-1 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Versions of packages ifplugd depends on: ii debconf [debconf-2.0] 1.5.3 Debian configuration management sy ii libc6 2.3.6-18 GNU C Library: Shared libraries 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: eth0 eth1 * ifplugd/hotplug_interfaces: * ifplugd/args: ifplugd/suspend_action: stop --- End Message --- --- Begin Message --- Hi Guillaume, On 06/08/06 14:52 +0200, giggz said ... > in /etc/fstab. I don't have "auto eth0" in my /etc/network/interfaces, so > the mount of my NFS exports fails at boot. I know I can use autofs > (it works), but I prefer the mount at boot. Do you have any idea to solve > that? When an interface is plugged in, ifplugd does an "ifup " on it. ifup runs the scripts in /etc/network/if-up.d, and you could do what you want there. Hope this helps, Giridhar PS: There is a mountnfs script provided by the initscripts package that probably does this. -- Y Giridhar Appaji Nag | http://www.appaji.net/ signature.asc Description: Digital signature --- End Message ---
Intent to NMU ifplugd to fix pending po-debconf l10n bugs
(CC'ing Y Giridhar Appaji Nag who seems to be intending to take this package over) Dear Debian maintainer, The ifplugd Debian package, which you are the maintainer of, has pending bug report(s) which include translation updates or fixes for po-debconf, namely bug number 414760 (and maybe other similar bugs). Even if we're still far from the release of the next Debian version, letting such bugs sleep in the BTS is simply lowering the chances that your package interaction with its users may be done in something else than the English language. It is also not encouraging for translators. I have the intention, as part of a more general action of the Debian i18n Task Force to build and possibly upload a non-maintainer upload for ifplugd in order to fix this as well as all pending translations for the debconf templates. Of course, an upload made by you would even be better...:-) Such changes are always harmless, which explains why I safely consider building NMU's for such issues even though they're obviously non critical. The schedule for the NMU (in case it happens, that is if you agree with it or if I don't receive any answer in 14 days) is roughly the following: Wednesday, March 05, 2008 : send this notice Wednesday, March 19, 2008 : post a NMU announcement to debian-i18n with you (maintainer) CC'ed Saturday, March 29, 2008 : deadline for receiving translation updates Sunday, March 30, 2008 : build the package and upload it to DELAYED/0-day send the NMU patch to the BTS Monday, March 31, 2008 : NMU uploaded to incoming If you intent to upload yourself, please notify me so that I interrupt the process on my side. In case I upload an NMU, I will subscribe to the Package Tracking System for ifplugd and follow its life for 60 days after my NMU in order to fix any issue potentially introduced by my upload. Let me know, as soon as possible, if you have any kind of objection to this process. If you'd rather do the fix yourself, I will of course leave the package alone. Same if you have reasons not to do the update now. -- signature.asc Description: Digital signature
