Re: intend to adopt calc, so does someone else--need advice

2003-05-05 Thread Luis Bustamante
Hi, Craig. > "Craig" == Craig P Steffen <[EMAIL PROTECTED]> writes: Craig> Greetings, I'm an avid Linux user and programmer, and I'd Craig> like to become a Debian Developer. As the first step in Craig> this process, I'd like to take the calc source package and Craig> maintai

Bug#80888: bug #80888: dnrd: Multiple buffer overflows

2003-05-05 Thread Drew Scott Daniels
Sorry for the crosspost, but I wanted to include everyone potentially interested in this bug. The home page for dnrd [1] seems to indicate that it is intended for use for a single computer or an internal network. The typical user will likely only want to allow input to dnrd from trusted sources [2

Processing of leksbot_1.2-3.1woody1_i386.changes

2003-05-05 Thread Archive Administrator
leksbot_1.2-3.1woody1_i386.changes uploaded successfully to localhost along with the files: leksbot_1.2-3.1woody1.dsc leksbot_1.2.orig.tar.gz leksbot_1.2-3.1woody1.diff.gz leksbot_1.2-3.1woody1_i386.deb Greetings, Your Debian queue daemon

leksbot_1.2-3.1woody1_i386.changes ACCEPTED

2003-05-05 Thread Debian Installer
Mapping stable-security to proposed-updates. Warning: ignoring leksbot_1.2.orig.tar.gz, since it's already in the archive. Accepted: leksbot_1.2-3.1woody1.diff.gz to pool/main/l/leksbot/leksbot_1.2-3.1woody1.diff.gz leksbot_1.2-3.1woody1.dsc to pool/main/l/leksbot/leksbot_1.2-3.1woody1.dsc lek

Bug#187667: jade: gcc/g++ 3.2 is broken on m68k for jade, avoid

2003-05-05 Thread Goswin Brederlow
Package: jade Version: 1.2.1-29.2 (not installed) Followup-For: Bug #187667 Below is a patch for jade to use gcc-2.95 and g++-2.95 on m68k which makes it functional again. I build, installed and tested it on newts tutorial.sgml. The woody version works, the sid version fails. The woody version co

Processed: severity of 191880 is grave

2003-05-05 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > severity 191880 grave Bug#191880: jade: fails to build tutorial.sgml from newt without error code Severity set to `grave'. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator

Processed: merging 187667 191880

2003-05-05 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > merge 187667 191880 Bug#187667: jade: completely unusable on m68k Bug#191880: jade: fails to build tutorial.sgml from newt without error code Merged 187667 191880. > End of message, stopping processing here. Please contact me if you need assistance.

jade_1.2.1-29.3_i386.changes ACCEPTED

2003-05-05 Thread Debian Installer
Accepted: jade_1.2.1-29.3.diff.gz to pool/main/j/jade/jade_1.2.1-29.3.diff.gz jade_1.2.1-29.3.dsc to pool/main/j/jade/jade_1.2.1-29.3.dsc jade_1.2.1-29.3_i386.deb to pool/main/j/jade/jade_1.2.1-29.3_i386.deb libsp1-dev_1.3.4-1.2.1-29.3_i386.deb to pool/main/j/jade/libsp1-dev_1.3.4-1.2.1-29

jade override disparity

2003-05-05 Thread Debian Installer
There are disparities between your recently accepted upload and the override file for the following file(s): libsp1-dev_1.3.4-1.2.1-29.3_i386.deb: package says section is devel, override says libdevel. Either the package or the override file is incorrect. If you think the override is correct an

Bug#191880: marked as done (jade: fails to build tutorial.sgml from newt without error code)

2003-05-05 Thread Debian Bug Tracking System
Your message dated Mon, 05 May 2003 22:02:16 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#187667: fixed in jade 1.2.1-29.3 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 yo

Bug#187667: marked as done (jade: completely unusable on m68k)

2003-05-05 Thread Debian Bug Tracking System
Your message dated Mon, 05 May 2003 22:02:16 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#187667: fixed in jade 1.2.1-29.3 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 yo