Be her hero in bed!
Title: deity jkc agate ltk amend rd helene rwf sykes frw chef re Advanced Penis Development more info here mph ls mulligatawny bmp tensional fe audiovisual ur ave zi cabin kfx monetarism nr sclerosis tss budget frx arctan nla emil oh janos go folksong pv flirt zhg rollick akj artillery jo toshiba gf socratic zru no -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 155949 is important, merging 171827 155949
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.8.10 > severity 155949 important Bug#155949: filename="..." Severity set to `important'. > merge 171827 155949 Bug#155949: filename="..." Bug#171827: metamail takes name="" instead of filename="" Merged 155949 171827. > 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#299939: gkdial
#299939 and #218014 likely have the same cause. Someone might
consider downgrading #299939 and/or merging them.
It seems that both are caused by a user-trigged disconnect event while
in a state when disconnect should be disallowed. A proper solution
probably requires glib synchronization, but I'll bet that the problems
can be visibly solved by something like:
/*
* runs the command the user defined to disconnect
*/
void
gk_disconnect (GtkWidget * button, gpointer data)
{
GkDial *gkdial = (GkDial *) data;
gchar *disconnect_cmd = DOWNCMD;
+
+ if (!disconnect_valid) return;
+ disconnect_valid=0;
/*
* this shows that gkdial was the responsible for the connection
* being
* closed
*/
gkdial->was_gkdial = FALSE;
gkdial_exec (gkdial, disconnect_cmd, DISCONNECTING);
}
where disconnect_valid is a global variable, set to TRUE at the
appropriate time, and set to FALSE above, and while redialing.
I'm having trouble testing this since I don't have a linmodem..
Justin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 301038
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.8.10 > tags 301038 confirmed Bug#301038: imagefs: segfaults on startup There were no tags set. Tags added: confirmed > 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#301409: imagefs: Manpage fails to document options
Package: imagefs Version: 1.03-4 Severity: minor The manpage only gives the same information as `imagefs` help output. In particular, I have no clue what `imagefs boot` does. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: imagefs crash
Processing commands for [EMAIL PROTECTED]: > tag 301038 patch Bug#301038: imagefs: segfaults on startup Tags were: confirmed 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#301038: imagefs crash
tag 301038 patch
thanks
It appears that the imagefs crash can be avoided by pre-creating the
file. It will crash if the file doesn't exist, but seems to succeed
if you /usr/bin/touch the file beforehand.
There's something wrong with the constructor CImage::CImage. When you
try to create a file, its boolean create parameters is true; but the
code is wrong somehow, and strace has:
open("z", O_RDWR) = -1 ENOENT (No such file or
directory)
instead of creat("z"). So, someone that actually knows something
about c++ needs to look at the code an either create the file
beforehand, or add a flag similar to O_CREAT.
There are other problems, too, but they seem to be caused only by lack
of input checking:
$ imagefs d a
Read directory from image file [a].
Fatal: could not open file a.
Directory listing:
Segmentation fault (core dumped)
$ imagefs r a c
Remove files from image file [a].
Fatal: could not open file a.
Segmentation fault (core dumped)
That's pretty simple to solve:
catch (...)
{
cout << "Fatal: could not open file " << pcImageFile << "." << endl;
+ return 1;
}
There are several instances of these. Probably there should be a
wrapper function which outputs "Fatal: %s" to stderr, and exit(1) (or
whatever the c++ification of exit is).
Justin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#301420: newspost: FTBFS (amd64/gcc-4.0): conflicting types for '_nntp_post'
Package: newspost
Severity: normal
Tags: patch
When building 'newspost' on amd64 with gcc-4.0,
I get the following error:
gcc -O2 -Wall -c -o nntp.o nntp.c
nntp.c: In function 'nntp_post':
nntp.c:81: warning: implicit declaration of function '_nntp_post'
nntp.c: At top level:
nntp.c:109: error: conflicting types for '_nntp_post'
nntp.c:109: note: an argument type that has a default promotion can't match an
empty parameter name list declaration
nntp.c:81: error: previous implicit declaration of '_nntp_post' was here
make[3]: *** [nntp.o] Error 1
make[3]: Leaving directory `/newspost-2.1.1/base'
With the attached patch 'newspost' can be compiled
on amd64 using gcc-4.0.
Regards
Andreas Jochens
diff -urN ../tmp-orig/newspost-2.1.1/base/nntp.c ./base/nntp.c
--- ../tmp-orig/newspost-2.1.1/base/nntp.c 2005-03-25 20:41:28.638247703
+0100
+++ ./base/nntp.c 2005-03-25 20:41:21.836522991 +0100
@@ -26,6 +26,10 @@
*** Public Routines
**/
+int _nntp_post(const char *subject, newspost_data *data,
+ const char *buffer, long length,
+ boolean no_ui_updates);
+
boolean nntp_logon(newspost_data *data) {
char buffer[STRING_BUFSIZE];
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of newspost_2.1.1-4_i386.changes
newspost_2.1.1-4_i386.changes uploaded successfully to localhost along with the files: newspost_2.1.1-4.dsc newspost_2.1.1-4.diff.gz newspost_2.1.1-4_i386.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
newspost_2.1.1-4_i386.changes ACCEPTED
Accepted: newspost_2.1.1-4.diff.gz to pool/main/n/newspost/newspost_2.1.1-4.diff.gz newspost_2.1.1-4.dsc to pool/main/n/newspost/newspost_2.1.1-4.dsc newspost_2.1.1-4_i386.deb to pool/main/n/newspost/newspost_2.1.1-4_i386.deb Announcing to debian-devel-changes@lists.debian.org Closing bugs: 301420 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#301420: marked as done (newspost: FTBFS (amd64/gcc-4.0): conflicting types for '_nntp_post')
Your message dated Fri, 25 Mar 2005 17:32:18 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#301420: fixed in newspost 2.1.1-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)
--
Received: (at submit) by bugs.debian.org; 25 Mar 2005 19:48:05 +
>From [EMAIL PROTECTED] Fri Mar 25 11:48:04 2005
Return-path: <[EMAIL PROTECTED]>
Received: from c158007.adsl.hansenet.de (localhost.localdomain) [213.39.158.7]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DEumq-00046W-00; Fri, 25 Mar 2005 11:48:04 -0800
Received: from aj by localhost.localdomain with local (Exim 4.50)
id 1DEumn-0007k5-F0; Fri, 25 Mar 2005 20:48:01 +0100
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
From: Andreas Jochens <[EMAIL PROTECTED]>
Subject: newspost: FTBFS (amd64/gcc-4.0): conflicting types for '_nntp_post'
Message-Id: <[EMAIL PROTECTED]>
Date: Fri, 25 Mar 2005 20:48:01 +0100
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: newspost
Severity: normal
Tags: patch
When building 'newspost' on amd64 with gcc-4.0,
I get the following error:
gcc -O2 -Wall -c -o nntp.o nntp.c
nntp.c: In function 'nntp_post':
nntp.c:81: warning: implicit declaration of function '_nntp_post'
nntp.c: At top level:
nntp.c:109: error: conflicting types for '_nntp_post'
nntp.c:109: note: an argument type that has a default promotion can't match an
empty parameter name list declaration
nntp.c:81: error: previous implicit declaration of '_nntp_post' was here
make[3]: *** [nntp.o] Error 1
make[3]: Leaving directory `/newspost-2.1.1/base'
With the attached patch 'newspost' can be compiled
on amd64 using gcc-4.0.
Regards
Andreas Jochens
diff -urN ../tmp-orig/newspost-2.1.1/base/nntp.c ./base/nntp.c
--- ../tmp-orig/newspost-2.1.1/base/nntp.c 2005-03-25 20:41:28.638247703
+0100
+++ ./base/nntp.c 2005-03-25 20:41:21.836522991 +0100
@@ -26,6 +26,10 @@
*** Public Routines
**/
+int _nntp_post(const char *subject, newspost_data *data,
+ const char *buffer, long length,
+ boolean no_ui_updates);
+
boolean nntp_logon(newspost_data *data) {
char buffer[STRING_BUFSIZE];
---
Received: (at 301420-close) by bugs.debian.org; 25 Mar 2005 22:56:48 +
>From [EMAIL PROTECTED] Fri Mar 25 14:56:48 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DExjU-0001ne-00; Fri, 25 Mar 2005 14:56:48 -0800
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1DExLm-0003y1-00; Fri, 25 Mar 2005 17:32:18 -0500
From: Anibal Monsalve Salazar <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#301420: fixed in newspost 2.1.1-4
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Fri, 25 Mar 2005 17:32:18 -0500
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Source: newspost
Source-Version: 2.1.1-4
We believe that the bug you reported is fixed in the latest version of
newspost, which is due to be installed in the Debian FTP archive:
newspost_2.1.1-4.diff.gz
to pool/main/n/newspost/newspost_2.1.1-4.diff.gz
newspost_2.1.1-4.dsc
to pool/main/n/newspost/newspost_2.1.1-4.dsc
newspost_2.1.1-4_i386.deb
to pool/main/n/newspost/newspost_2.1.1-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.
Anibal Monsalve Salazar <[EMAIL PROTECTED]> (supplier of updated newspost
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
Processed: tagging 301038
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.8.10 > tags 301038 - patch Bug#301038: imagefs: segfaults on startup Tags were: patch confirmed Tags removed: patch > 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]
