Re: Adopting base-passwd
On Fri, Nov 29, 2002 at 01:49:50PM +, Colin Watson wrote: Since it's an essential package I figured I should mention this before acting: Wichert and I have agreed that I will be taking over maintenance of base-passwd. An upload will be in incoming by this weekend. Cheers, -- Colin Watson [EMAIL PROTECTED] I'd like to wish you the best of luck getting it right first go. = ) Yours sincerely, Andrew Netsnipe Lau -- --- * Andrew Netsnipe LauComputer Science Student Representaive, UNSW * * # apt-get into it Debian GNU/Linux Package Maintainer * * netsnipe(+)debianplanet.org\0 alau(+)cse.unsw.edu.au\0 * * GnuPG 1024D/2E8B68BD 0B77 73D0 4F3B F286 63F1 9F4A 9B24 C07D 2E8B 68BD * --- pgpCeuANwrjwY.pgp Description: PGP signature
Re: New maintainer behaviour with NMU and LogJam's hijacking
Firstly, I don't think this is a matter for debian-devel as it doesn't involve the project as a whole and would best be dealt with privately. I usually consult debian-devel or other mailing lists before jumping on to do NMUs... well, sometimes :P Private mail do get lost, and there might be other people who are interested in the exact same package, so it is better to do coordination where it is possible. It's not just a problem between you and the maintainer, but you and the whole Debian Project, because anybody within Debian Project has the power to NMU that specific package. regards, junichi
Re: KDEE3 question
#include hallo.h * Colin Watson [Fri, Nov 29 2002, 02:14:35PM]: to see a good reason for not compiling KDE3 on gcc 2.95 as this definitely works or else there wouldn't be a single KDE3 for woody package on kde.org. The good reason is that all the KDE library sonames have to be changed when switching to gcc 3.2. The KDE developers rightly wish to avoid this disruption. What's the problem with a such change? Sure, the amount of work needed for the whole gcc-3.2 transition would grow a bit. But what will happen when they upload new, gcc-3.2 based packages with the package names of existing inofficial packages? I expect lots of users whinning about temporar breakage. So it would be good to change them anyways. And looking so, the existing KDE3 packages could also go into Sid _now_. Gruss/Regards, Eduard. -- If Bill Gates had a dime for every time a Windows box crashed... ...Oh, wait a minute, he already does.
Re: KDEE3 question
temporar breakage. So it would be good to change them anyways. And looking so, the existing KDE3 packages could also go into Sid _now_. You're right. Packages from kde.org are very stable, and I think - correctly created, I'm using them for long time (about three months), and I didn't notice any problems with them. IMO waiting for full gcc transition in Sid, which will take very much time, isn't good idea for KDE3. Regards, -- Mati ([EMAIL PROTECTED]) Sounds like a Windows problem, try calling Microsoft support
Re: Are we losing users to Gentoo?
On Fri, Nov 29, 2002 at 03:58:51PM -0500, Joey Hess wrote: and behind netbsd in the sory state of our cdrom mirror network. I'm with Joey on this; last time I tried to find Debian .iso images, it was a nightmare. In fact I couldn't find an official woody iso anywhere. As he also said, many of the mirrors are hopelessly out-of-date. Joy (or any of the rest of the www team) - where do you get the data to put into the mirror pages on www.d.o? I'd suggest that a simple method for mirror admins to let us know what they plan to mirror, and for us to test its availability on a regular basis, would be a good idea. (In fact I might even just do it). Cheers, Nick -- Nick Phillips -- [EMAIL PROTECTED] Live in a world of your own, but always welcome visitors.
Re: [Agnubis] Packaging Agnubis for Debian GNU/Linux
On Fri, Nov 29, 2002 at 04:20:09PM +0100, Amaya wrote: Condider that his ITP has been there for two months. He's either not that motivated or simply busy. And NM is much more time consuming than closing an ITP. Offer your help, whatever help you are willing or able to give. If he is too busy to package whatever was that depended so heavily on Agnubis, offer to retitle the bug to a RFP. It's the other way around. Agnubis depends on DiaCanvas2 which he has ITPed. Agnubis doesn't have any releases yet, but I was hoping to start doing CVS snapshots in preparations for their eventual release. So if I were to release Agnubis (still impossible since they taking a brief break from development and their CVS src is currently not building), I'd have to package DiaCanvas2 as well, and thus rudely hijacking the poor bloke's ITP. That why I hope he can show me to committed, otherwise I will have no choice but to hijack it in order to release Agnubis .deb packages. Yours sincerely, Andrew Netsnipe Lau -- --- * Andrew Netsnipe LauComputer Science Student Representaive, UNSW * * # apt-get into it Debian GNU/Linux Package Maintainer * * netsnipe(+)debianplanet.org\0 alau(+)cse.unsw.edu.au\0 * * GnuPG 1024D/2E8B68BD 0B77 73D0 4F3B F286 63F1 9F4A 9B24 C07D 2E8B 68BD * --- pgpMoaBroihcM.pgp Description: PGP signature
Re: Are we losing users to Gentoo?
On Fri, Nov 29, 2002 at 04:58:30PM -0500, David B Harris wrote: On Fri, 29 Nov 2002 15:58:51 -0500 Joey Hess [EMAIL PROTECTED] wrote: The comparison is only fair with organizations that *want* you do do so(so not redhat, probably not openbsd, or mandrake, or others whose principal developers try to sell cds). Strictly speaking, given the ISO mirroring situation, we've never wanted people to use full 640M ISOs when we knew that 99% of people downloading would use a couple hundreds megs, at most. Given the ISO mirroring situation? Care to elucidate? I seem to remember seeing several offers of machines and bandwidth recently. It would seem to make sense to at least make it relatively easy for mirror admins who *do* have the available resources to provide ISO images. Even a single, reliable, possibly rate-limited, source for ISOs would be an improvement on what we currently have. Rate-limiting the source would, if necessary, provide a disincentive to people who would otherwise just jump in and download ISOs rather than using Jigdo. Cheers, Nick -- Nick Phillips -- [EMAIL PROTECTED] Fine day for friends. So-so day for you.
Re: New maintainer behaviour with NMU and LogJam's hijacking
On Fri, Nov 29, 2002 at 06:36:06PM -0500, Colin Walters wrote: On Fri, 2002-11-29 at 17:50, Ari Pollak wrote: Didn't you sponsor the upload? No, that was me... This Colin Colin confusion has been quite contagious this season, hasn't it? = P Yours sincerely, Andrew Netsnipe Lau -- --- * Andrew Netsnipe LauComputer Science Student Representaive, UNSW * * # apt-get into it Debian GNU/Linux Package Maintainer * * netsnipe(+)debianplanet.org\0 alau(+)cse.unsw.edu.au\0 * * GnuPG 1024D/2E8B68BD 0B77 73D0 4F3B F286 63F1 9F4A 9B24 C07D 2E8B 68BD * --- pgpVMkwT8ti2o.pgp Description: PGP signature
Re: Are we losing users to Gentoo?
On Sat, Nov 30, 2002 at 11:23:23PM +1300, Nick Phillips wrote: Joy (or any of the rest of the www team) - where do you get the data to put into the mirror pages on www.d.o? Well, we get it from the Internet :) Please rephrase the question, I don't understand. I'd suggest that a simple method for mirror admins to let us know what they plan to mirror, and for us to test its availability on a regular basis, would be a good idea. We already have that, but notice how the mirrors of the two archives aren't in the least bit of distress like the problem at hadn: the structure and contents of those is well defined, we have mirror checking scripts and we regularly monitor the output of that for any major problems. (I would suggest that you have a look at http://www.debian.org/mirror/) The CD image mirrors don't even have a primary site -- *cdimage.d.o includes only jigdo files now. Those image mirrors are one big improvization. -- 2. That which causes joy or happiness.
Bug#171237: ITP: tinycdb -- a package for creating and reading constant databases
Package: wnpp Version: unavailable; reported 2002-11-30 Severity: wishlist * Package name: tinycdb Version : 0.73 Upstream Author : Michael J. Tokarev [EMAIL PROTECTED] * URL : ftp://ftp.corpit.ru/pub/tinycdb * License : Public Domain [1] Description : a package for creating and reading constant databases tinycdb is a small, fast and reliable utility set and subroutine library for creating and reading constant databases. The database structure is tuned for fast reading: . - Successful lookups take normally just two disk accesses. - Unsuccessful lookups take only one disk access. - Small disk space and memory size requirements; a database uses 2048 bytes for the header and 24 bytes per record, plus the space for keys and data. - Maximum database size is 4GB; individual record size is not otherwise limited. - Portable file format. - Fast creation of new databases. - No locking, updates are atomical. . tinycdb implements almost all API as found in cdb-0.75 written by D.J. Bernstein, so it should be source-compatible. It also implements the query interface as found in earlier versions of cdb (0.6x) and freecdb. It also contains some enhancements, like allowing to check existance of a record in a yet-to-be-created cdb database file. . This package contains both the utility to manipulate constant databases and the development files. [1] This is the complete license text for it: |You can do whatever you like with this package. The code is placed |at the public domain. | |This package is distributed in a hope it will be useful, but |WITHOUT ANY WARRANTY; without even the implied warranty of |MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Both, the upstream author and I believe that this contains no legal problem and is acceptable as DSFG-free license. If there's any problem with the license, please inform me about the problem and a suggested change. -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux salem 2.4.20-rc2 #1 Sun Nov 17 10:28:49 CET 2002 i586 Locale: LANG=POSIX, [EMAIL PROTECTED] -- Free yourself from negative influence. Negative thoughts are the old habits that gnaw at the roots of the soul. Moses Shongo, (Seneca)
Re: gpg-agent?
On Nov 29, martin f krafft [EMAIL PROTECTED] wrote: from the current packager i had to hear that it's largely unstable. many bugs and such. we'll have to wait... I have been using it for weeks without any problem, so I'd say it should be packaged. (No, I'm not going to do it.) -- ciao, Marco pgpiXAv6EGYd5.pgp Description: PGP signature
qa.debian.org: attributes revoked GnuPG keys to maintainers
Package: qa.debian.org Version: unavailable; reported 2002-11-30 Severity: normal developer.php on http://qa.debian.org seems to be too agressive in attributing keys to maintainers. It's even listing revoked keys on the Packages overview pages. Take a look at my Packages overview page [1]. It lists two GPG key ids for myself, 2E8B68BD DCFEDB00. The first is valid [2], but notice that the latter key, DCFEDB00 was revoked almost two years ago [3]. I've never even signed a package to Debian using that key either. I believe this a is a bug since it would incorrectly imply to the viewer of the page that the said developer is still using that GnuPG key even though it has been revoked. Yours sincerely, Andrew Netsnipe Lau [1] http://qa.debian.org/developer.php?login=netsnipe%40debianplanet.org [2] http://pgp.dtype.org:11371/pks/lookup?search=0x2E8B68BDop=vindex [3] http://pgp.dtype.org:11371/pks/lookup?search=0xDCFEDB00op=vindex -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux espresso 2.4.19 #1 Tue Nov 12 23:32:34 EST 2002 i686 Locale: LANG=C, LC_CTYPE=C -- --- * Andrew Netsnipe LauComputer Science Student Representaive, UNSW * * # apt-get into it Debian GNU/Linux Package Maintainer * * netsnipe(+)debianplanet.org\0 alau(+)cse.unsw.edu.au\0 * * GnuPG 1024D/2E8B68BD 0B77 73D0 4F3B F286 63F1 9F4A 9B24 C07D 2E8B 68BD * --- pgp1tlapCLsir.pgp Description: PGP signature
subject
--
Bug#171253: ITP: libdjbdns -- DNS client library designed to replace the BIND res_*/dn_* library
Package: wnpp Severity: wishlist DNS client library designed to replace the old BIND res_*/dn_* library[0] High-level lookups: The dns library provides several easy-to-use DNS lookup routines: dns_ip4, dns_ip4_qualify, dns_name4, dns_mx, and dns_txt. dns_ip4_qualify supports the traditional configuration mechanisms for hostname rewriting: $LOCALDOMAIN, /etc/resolv.conf, and gethostname. It also supports a powerful new user-controlled rewriting mechanism. The functions that read /etc/resolv.conf automatically reread it every ten minutes, so system administrators don't have to kill long-running programs. Low-level lookups: The dns_domain_* and dns_packet_* functions make it easy to safely parse DNS packets. The dns_transmit_* functions send DNS queries of arbitrary types to arbitrary servers. These are the functions used in the dnscache program. License: Bernstein has put the .[ch] files (dns.h, dns_dfd.c, dns_domain.c, dns_dtda.c, dns_ip.c, dns_ipq.c, dns_mx.c, dns_name.c, dns_nd.c, dns_packet.c, dns_random.c, dns_rcip.c, dns_rcrw.c, dns_resolve.c, dns_sortip.c, dns_transmit.c, dns_txt.c) and all necessary lower-level .[ch] files into the public domain[1]. I do not plan to make any changes to those files, so Bernstein's djbdns security guarantee[2] applies. My additions to the package will be licensed under a BSD compatible license. Regards, Gerrit. [0] http://cr.yp.to/djbdns/blurb/library.html [1] http://cr.yp.to/djbdns/res-disaster.html [2] http://cr.yp.to/djbdns/guarantee.html pgpq6I8WAk5XI.pgp Description: PGP signature
Re: Are we losing users to Gentoo?
Nick Phillips wrote: I'd suggest that a simple method for mirror admins to let us know what they plan to mirror, and for us to test its availability on a regular basis, would be a good idea. (In fact I might even just do it). I'm in the process of doing that, see the debian-cd list. -- see shy jo pgplp49gJlr8v.pgp Description: PGP signature
Re: New maintainer behaviour with NMU and LogJam's hijacking
On Sat, Nov 30, 2002 at 09:31:46PM +1100, Andrew Lau wrote: On Fri, Nov 29, 2002 at 06:36:06PM -0500, Colin Walters wrote: On Fri, 2002-11-29 at 17:50, Ari Pollak wrote: Didn't you sponsor the upload? No, that was me... This Colin Colin confusion has been quite contagious this season, hasn't it? = P ... season? :-) -- Colin Watson [EMAIL PROTECTED]
Fwd: Please confirm your message
I believe that it is inappropriate to use such an email system that does this when sending messages to the BTS. Also anyone who wants to use such a system when posting to a popular mailing list (such as debian-devel) should first put in place a white-list of people who regularly post to the list (such as me). For reference, I will not reply to such a message, but I will consider putting the entire domain in my spam filter if such messages continue. -- Forwarded Message -- Subject: Please confirm your message Date: 30 Nov 2002 15:45:19 - From: The qconfirm program [EMAIL PROTECTED] To: [EMAIL PROTECTED] Hello, this is the qconfirm mail-handling program at [EMAIL PROTECTED]. One or more messages from you are being held because your address was not recognized. To release your pending message(s) for delivery, please reply to this request. Your reply will not be read, so an empty message is fine. If you do not reply to this request, your message(s) will eventually be returned to you, and will never be delivered to the envelope recipient. This confirmation verifies that your message(s) are legitimate and not junk-mail. Regards, the qconfirm program, http://smarden.org/qconfirm/ --- Below this line is the top of a message from you. Received: (qmail 11395 invoked from network); 30 Nov 2002 15:45:18 - Received: from tsv.sws.net.au (203.36.46.2) by 0 with SMTP; 30 Nov 2002 15:45:18 - Received: from lyta.coker.com.au (localhost [127.0.0.1]) by tsv.sws.net.au (Postfix) with ESMTP id 83FC292668; Sun, 1 Dec 2002 02:44:48 +1100 (EST) Received: from lyta (localhost [127.0.0.1]) by lyta.coker.com.au (Postfix) with ESMTP id 1E1FA908E; Sat, 30 Nov 2002 16:44:40 +0100 (CET) Content-Type: text/plain; charset=iso-8859-1 From: Russell Coker [EMAIL PROTECTED] Reply-To: Russell Coker [EMAIL PROTECTED] To: Gerrit Pape [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: Bug#171253: ITP: libdjbdns -- DNS client library designed to replace the BIND res_*/dn_* library Date: Sat, 30 Nov 2002 16:44:39 +0100 User-Agent: KMail/1.4.3 References: [EMAIL PROTECTED] In-Reply-To: [EMAIL PROTECTED] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: [EMAIL PROTECTED] On Sat, 30 Nov 2002 15:34, Gerrit Pape wrote: License: Bernstein has put the .[ch] files (dns.h, dns_dfd.c, dns_domain.c, dns_dtda.c, dns_ip.c, dns_ipq.c, dns_mx.c, dns_name.c, dns_nd.c, dns_packet.c, dns_random.c, dns_rcip.c, dns_rcrw.c, dns_resolve.c, dns_sortip.c, dns_transmit.c, dns_txt.c) and all necessary lower-level .[ch] files into the public domain[1]. I do not plan to make any changes to those files, so Bernstein's djbdns security guarantee[2] applies. My additions to the package will be licensed under a BSD compatible license. The URL did not make this license adequately clear to me. Does this specifically differ from the license of Qmail? --- -- http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/Postal SMTP/POP benchmark http://www.coker.com.au/~russell/ My home page
Re: Bug#171116: ITP: tsclient -- GNOME2 frontend for rdesktop
On Thu, Nov 28, 2002 at 10:22:01PM -0500, Colin Walters wrote: On Thu, 2002-11-28 at 21:09, Andrew Lau wrote: Package: wnpp Version: N/A; reported 2002-11-29 Severity: wishlist * Package name: tsclient Version : 0.56 Upstream Author : Erick Woods [EMAIL PROTECTED] * URL : http://www.gnomepro.com/tsclient/ * License : GPL Description : GNOME2 frontend for rdesktop How about: Windows Terminal Services (RDP) client for GNOME 2 how about: Windows Terminal Services (RDP) client for GNOME? gnome 1 probably is not going to be in sarge, so the difference between gnome 1 and gnome 2 arent going to matter to someone installing sarge. and for someone who really wants to know they can look at the dependencies. -- gram pgpYpiigjMyYC.pgp Description: PGP signature
Kernel 2.4.19 and wanpipe.o
Hello, I have a Sangoma Wanpipe and need to compile a new Kernel which support it. I have tried to compile the module and compiled into the kernel. But I get every time I compile it many error messages about 'symboles' or something like this. Sorry, I can not give you better informations, because curently I have NO internet access at home and I am writing this E-Mail in a cyber-center. Please can anyone help me out ? I need the module urgently, becaue I must install it at a client. Many thanks in advance Michelle
/proc/cpuinfo is false
Hello, I have a nfs-server at home and it was running SLINK r5. All was working fine. Now I have installed WOODY r0 on it, and linux_logo give me only 117 MHz. The BogoMIPS are right with 233.47. I have a AMD K5 with 166 MHz and /proc/cpuinfo give me: If I use another Harddisk (I have IDE-Racks) with POTATO or SLINK, the /proc/cpuinfo is right. processor : 0 vendor_id : AuthenticAMD cpu family : 5 model : 2 model name : AMD-K5(tm) Processor stepping: 4 cpu MHz : 116.933 cache size : 24 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr mce cx8 pge bogomips: 233.47 I think, this is a bug or ??? Thanks for your Help Michelle
Re: location of UnicodeData.txt
On Fri, Nov 29, 2002 at 11:37:41AM +0100, Bernhard R. Link wrote: * Jim Penny [EMAIL PROTECTED] [021128 03:35]: So, according to Branden, international standards are supposed to allow debian the right to modify them and to distribute the modified versions. Absent said permission, which is hardly ever going to be given, they must be considered non-free. (This is, of course, logically forthright.) Moreover, according to the non-free removal proponents, we should not even distribute the un-modified copies of these files. Yet, unicode is supposed to be the canonical character encoding scheme for debian. Does this mean every unicode text editor belongs in contrib (depends on something non-free)? I think you are missing the points here. First of all, DFSG applied to the standard does not want to change the standard, but wants all to be able to change the text of the standard. Huh? If I change the text of the standard, I have changed the standard! For example, if I have : 0332;COMBINING LOW LINE;Mn;220;NSM;N;NON-SPACING UNDERSCORE and change this to 0332;NON-COMBINING LOW LINE;Mn;220;NSM;N;SPACING UNDERSCORE Then the standard has been changed! That is, this file is line after line of character number assignment, followed by character name, (and other information). There is no possible change that does not change the standard! Hint: (from standard writer's viewpoint) - A standard that can be changed by anyone, at anytime, without notice and consultation is not a standard, especially if it is a contentious standard that has some people seriously upset (i.e, Russian and XJK users). This is a good thing, the text of standards should be modifiable. How else shall someone write the following standard without having written the first or having to write all from scratch? The text of every standard that I know of is modifiable. However, it normally takes the consent of the standards body and is issued under its aegis. Again, Jim Penny's unicode standard has no value, and even debian unicode has very limited appeal. On the other hand, if you wish to create a competitor to the unicode standard, say the debicode standard, I see no moral right that you have to incorporate, without permission, the unicode standard. You should expect to start from scratch! Secondly: What has a unicode editor have to do with the unicode standard? It should only implement it. If it would contain parts of the standard-text (tables or whatever) that were protected by copyright law and the standard would allow no modifications, then noone would be allowed to copy the editor. (No special problem with debian) A unicode editor must know certain properties of the character set (note, I am not talking about font properties here, unicode does not deal with fonts.) Examples might be langauge, combining marks, bidirectionality, input methods, surrogates, Hangul syllables. These are things that an editor must know, and that pretty much, must be looked up in the unicode table. Now, the unicode license happens to be fairly clear, and fairly permissive. See: http://www.unicode.org/Public/UNIDATA/UnicodeCharacterDatabase.html It specifically gives permission for redistibution, without fee, providing a statement of copyright, and a disclaimer are preserved. It also specifically allows incorporation into programs under the same terms. But those terms happen to be non-DSFG free. They fail 3 and 8. Now, IANAL, but I suspect that any unicode editor that reproduced enough information from the unicode standard to be useful would be considered a derived work. More importantly, I think that is is arguable that this table is, in the terms of the Debian Social Contract, necessary for the execution of a full unicode editor. (The language of the debian Social Contract is even more general and vague than copyright law! In either case, the social contract would place the unicode table into non-free; and any editor that depended on the table, or information derived from the table (in a copyright sense) in either non-free or contrib. I have no problem with this result. But saying that the unicode character table cannot be distributed by debian, in spite of specific language permitting us to do so, seems a bit extreme. And the consequences of this decision will probably seem extreme to many people. This example just happens to be particularly cogent; there is no doubt it is non-free, there is no doubt it is copyrightable, there is little doubt that it is necessary for the execution of a substantial corpus of programs which are otherwise DFSG free. These program would certainly include unicode editors, and would probably include python, perl and ruby. Jim Penny Hochachtungsvoll, Bernhard R. Link -- gEistiO sagen wir mal...ich hab alle sourcen in /lost+found/waimea me gEistiO: [...] Warum lost+found? gEistiO wo haette ich es denn sonst hingeben solln?
Re: Pick a name, any name...
Georg == Georg Lehner [EMAIL PROTECTED] writes: Georg ... What would be wrong with multiple A records in this Georg case? The fact that forwrd DNS != reverse DNS. That is, the PTR record won't necessarily match the name that produced the A record. While not broken, it can have consequences for systems trying to avoid MITM attacks. -- Stephen To Republicans, limited government means not assisting people they would sooner see shoveled into mass graves. -- Kenneth R. Kahn
Re: Are we losing users to Gentoo?
On Sat, 30 Nov 2002 23:27:33 +1300 Nick Phillips [EMAIL PROTECTED] wrote: Given the ISO mirroring situation? Care to elucidate? There being an order of magnitude more package mirrors than ISO mirrors. Completely ignoring the web site organisation, mind you, it's been common for a long time for people to encourage network-based installs, or anything other than downloading full 640M ISOs. Part of it, of course, is to enhance the user experience - users will rightfully go with full 640M ISOs because it's been their experience in the past that a) it was required, and b) shit broke often enough that they needed to reinstall. Almost everybody I got to do a 'net install never had any problems whatsoever, and they were EXTREMELY delighted. Had they gone wish the full 640M ISO, they'd have been happy, but they wouldn't have had as good an idea as to how things *can* work, when it's done right :) pgpZo7vImmMrN.pgp Description: PGP signature
Re: [Agnubis] Packaging Agnubis for Debian GNU/Linux
Andrew Lau dijo: It's the other way around. God... I feel dumb :-) I'd have to package DiaCanvas2 as well, and thus rudely hijacking the poor bloke's ITP. That why I hope he can show me to committed, otherwise I will have no choice but to hijack it in order to release Agnubis .deb packages. Just go ahead. Already notified, talked about it in this list... Follow-up to his ITP stating you are planning to hijack it. Upload both packages. -- .''`.I'd like to fly, but my wings have been so denied... : :' :Sand rains down and here I sit - Alice in Chains `. `'Proudly running Debian GNU/Linux (Sid + 2.4.19 + Ext3) `-www.amayita.com www.malapecora.com www.chicasduras.com
Re: /proc/cpuinfo is false
On Sat, 30 Nov 2002, Michelle Konzack wrote: Hello, I have a nfs-server at home and it was running SLINK r5. All was working fine. Now I have installed WOODY r0 on it, and linux_logo give me only 117 MHz. The BogoMIPS are right with 233.47. Indeed, that speed IS right. AMD did the whole PR rating thing back then, they only needed to run their 166 at 117 to get the equivalent of a pentium 166. http://www.incisive.com/used/voltage.htm The K6/166 actually ran at 166, k5 was 117. You'll see in that table that some of the cyrix's did the same thing. Mike
Bug#171270: ITP: ulog -- xsession equivalent of commands such as who or last
Package: wnpp Version: unavailable; reported 2002-11-30 Severity: wishlist * Package name: ulog Version : 0.3.0 Upstream Author : Hervé Eychenne [EMAIL PROTECTED] * URL : http://www.ulog.org * License : GPL Description : xsession equivalent of commands such as who or last Ulog enables you to find currently opened X sessions. It is the X equivalent of commands such as who or last. A ulogd daemon records the start and the end of X sessions. Then it is possible to know which users are currently logged in, according to several search criteria. New logins/logouts can also be notified instantaneously by the server in real-time mode. Mainly this program is ideal for real big enviroments with hundreds of X users, several terminal servers / workstations. The administrator can easily track down the user to a machine in order to support them, make statistics etc. -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux dell 2.4.20-rc1 #1 Wed Nov 27 20:30:52 CET 2002 i686 Locale: LANG=C, LC_CTYPE=C (ignored: LC_ALL set)
Bug#171276: ITP: kernel-patch-systrace -- Systrace kernel patch
Package: wnpp Version: unavailable; reported 2002-11-30 Severity: wishlist * Package name: kernel-patch-systrace Version : 1.0 Upstream Author : Niels Provos [EMAIL PROTECTED] * URL : http://www.citi.umich.edu/u/provos/systrace/ * License : BSD Description : Systrace kernel patch Systrace enforces system call policies for applications by constraining the application's access to the system. The policy is generated interactively. Operations not covered by the policy raise an alarm and allow an user to refine the currently configured policy. In order to use systrace this kernel patch is needed to include systrace functionality into the kernel. Testing packages can be found here (ready for upload): http://www.sauter-online.de/debian/ -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux jacky 2.4.18sar #2 SMP Don Aug 22 17:58:16 CEST 2002 i686 Locale: LANG=de_DE, LC_CTYPE=de_DE
Bug#171274: ITP: xsystrace -- Systrace frontend invoked by systrace
Package: wnpp Version: unavailable; reported 2002-11-30 Severity: wishlist * Package name: xsystrace Version : 0.1 Upstream Author : Niels Provos [EMAIL PROTECTED] * URL : http://www.citi.umich.edu/u/provos/systrace/ * License : BSD Description : Systrace frontend invoked by systrace Systrace enforces system call policies for applications by constraining the application's access to the system. The policy is generated interactively. Operations not covered by the policy raise an alarm and allow an user to refine the currently configured policy. This program will be execute if systrace runs in interactive mode and create the rules based on the inputs and selections in this frontend. It is also a gui to help createing permit or deny rules for systrace templates. Testing packages can be found here (ready for upload): http://www.sauter-online.de/debian/ -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux jacky 2.4.18sar #2 SMP Don Aug 22 17:58:16 CEST 2002 i686 Locale: LANG=de_DE, LC_CTYPE=de_DE
Bug#171273: ITP: systrace -- Enforce system call policies for applications
Package: wnpp Version: unavailable; reported 2002-11-30 Severity: wishlist * Package name: systrace Version : 1.0 Upstream Author : Niels Provos [EMAIL PROTECTED] * URL : http://www.citi.umich.edu/u/provos/systrace/ * License : BSD Description : Enforce system call policies for applications Systrace enforces system call policies for applications by constraining the application's access to the system. The policy is generated interactively. Operations not covered by the policy raise an alarm and allow an user to refine the currently configured policy. This requires a special kernel patch, provided by kernels compiled with the kernel-patch-systrace patch. Testing packages can be found here (ready for upload): http://www.sauter-online.de/debian/ Systrace is currently include in the main source tree of NetBSD and OpenBSD and is now ported to Linux. I have splitted it into tree packages: systrace, xsystrace, kernel-patch-systrace -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux jacky 2.4.18sar #2 SMP Don Aug 22 17:58:16 CEST 2002 i686 Locale: LANG=de_DE, LC_CTYPE=de_DE
Re: New maintainer behaviour with NMU and LogJam's hijacking
Ari == Ari Pollak [EMAIL PROTECTED] writes: IIRC Ari has caused upset with NMUs before; xscreensaver, I believe. (I express no opinion about whether that upload was a good idea or not.) Ari Didn't you sponsor the upload? Um, so? While yes the sponsor is at fault, it seems that you should also take responsibility for your actions. It seems that after that incident you would have had significant desire to learn and follow the NMU policy. So, I'd like to formally ask: have you read and do you plan to follow generally accepted procedures for future NMUs?
Re: New maintainer behaviour with NMU and LogJam's hijacking
Andrew Lau [EMAIL PROTECTED] writes: On Fri, Nov 29, 2002 at 06:36:06PM -0500, Colin Walters wrote: On Fri, 2002-11-29 at 17:50, Ari Pollak wrote: Didn't you sponsor the upload? No, that was me... This Colin Colin confusion has been quite contagious this season, hasn't it? = P Just wait until the two Brian Michael Nelson's get off the NM queue... -- Curse my natural showmanship! pgp8YIRgnMNVR.pgp Description: PGP signature
Re: New maintainer behaviour with NMU and LogJam's hijacking
I had been taking the full brunt of the responsibility for the xscreensaver NMU, but since I was a pre-NM at the time and sponsors of uploads are supposed to follow Debian policy as well, he ended up taking most of the responsibility. This was a similar situation; however, I felt it was necessary at the time considering the circumstances of the package having not being updated in over a year and a half despite new versions being out which fixed bugs, and the lack of any response from the package maintainer until after the NMU. I still doubt that I would have gotten any response from the maintainer at all had it not been for the actual package upload. Regardless, I will try to follow Debian policy in the future in this capacity. I would also like to extend apologies and a suggestion to Christian, in that if you do not have time to keep up with maintenance of a package, it would be much appreciated if it was put up for adoption or orphaned so that another developer with the proper resources to maintain the package will to so. If you wish to continue working on logjam, I would be happy to volunteer as a backup maintainer if he is backlogged for some time, so that the package is properly kept up-to-date and bug-free. Also, I would like to make a note of part of the Developer's reference in regards to NMUs, section 5.2.5: In any case, you should not be upset by the NMU. An NMU is not a personal attack against the maintainer. It is a proof that someone cares enough about the package and that they were willing to help you in your work, so you should be thankful. I did not make the NMU to circumvent Christian's responsibilities nor did I make it as an insult to him or the Debian project. I hope that this can be put behind us and continue development as normal. On Sat, Nov 30, 2002 at 02:45:19PM -0500, Sam Hartman wrote: Um, so? While yes the sponsor is at fault, it seems that you should also take responsibility for your actions. It seems that after that incident you would have had significant desire to learn and follow the NMU policy. So, I'd like to formally ask: have you read and do you plan to follow generally accepted procedures for future NMUs? pgpabzTObsYS5.pgp Description: PGP signature
Re: Bug#171116: ITP: tsclient -- GNOME2 frontend for rdesktop
[ No need to CC me ] On Sat, 2002-11-30 at 11:36, Graham Wilson wrote: how about: Windows Terminal Services (RDP) client for GNOME? gnome 1 probably is not going to be in sarge, so the difference between gnome 1 and gnome 2 arent going to matter to someone installing sarge. You're right; I agree.
Re: Are we losing users to Gentoo?
David B Harris wrote: There being an order of magnitude more package mirrors than ISO mirrors. Completely ignoring the web site organisation, mind you, it's been common for a long time for people to encourage network-based installs, or anything other than downloading full 640M ISOs. Part of it, of course, is to enhance the user experience - users will rightfully go with full 640M ISOs because it's been their experience in the past that a) it was required, and b) shit broke often enough that they needed to reinstall. Almost everybody I got to do a 'net install never had any problems whatsoever, and they were EXTREMELY delighted. Had they gone wish the full 640M ISO, they'd have been happy, but they wouldn't have had as good an idea as to how things *can* work, when it's done right :) The problem with the net installs isos is mainly that they are unofficial and there are several varying cd's produced by different folks, and of varying quality (though quality is overall good; I've used them happily in the past). If we really want to promote them more it would be good to set things up so they can be generated from the debian-cd package, and make them official debian isos. Of course debian-installer should support 1.4 mb net install floppies too. But still if someone wants a whole debian CD, for whatever reasons, I'd rather they could easily find it, especially if they are a newcomer to debian. -- see shy jo pgpIsa8jgM5sM.pgp Description: PGP signature
Re: New maintainer behaviour with NMU and LogJam's hijacking
Ari == Ari Pollak [EMAIL PROTECTED] writes: Ari I had been taking the full brunt of the responsibility for Ari the xscreensaver NMU, but since I was a pre-NM at the time Ari and sponsors of uploads are supposed to follow Debian policy Ari as well, he ended up taking most of the responsibility. This Ari was a similar situation; however, I felt it was necessary at Ari the time considering the circumstances of the package having Ari not being updated in over a year and a half despite new Ari versions being out which fixed bugs, and the lack of any Ari response from the package maintainer until after the NMU. I Ari still doubt that I would have gotten any response from the Ari maintainer at all had it not been for the actual package Ari upload. Do you specifically agree it was wrong in this instance to upload directly to incoming and not to a delayed queue? In future will you agree to include NMU patches in a bug report to the patch and unless there is a strong reason to do otherwise to upload to a delayed queue? I'm asking you these things in hope of making sure we're on the same page. If you don't agree then I'll try to convince you that you're wrong, but if we are both understanding the best practice the same way, then there's really no more to say.
Re: Are we losing users to Gentoo?
On Sat, 30 Nov 2002 16:06:40 -0500 Joey Hess [EMAIL PROTECTED] wrote: The problem with the net installs isos is mainly that they are unofficial and there are several varying cd's produced by different folks, and of varying quality (though quality is overall good; I've used them happily in the past). If we really want to promote them more it would be good to set things up so they can be generated from the debian-cd package, and make them official debian isos. Of course debian-installer should support 1.4 mb net install floppies too. But still if someone wants a whole debian CD, for whatever reasons, I'd rather they could easily find it, especially if they are a newcomer to debian. Agreed, on all counts :) pgpLK5R1aKajL.pgp Description: PGP signature
Re: Pick a name, any name...
Stephen Zander [EMAIL PROTECTED] wrote:
The fact that forwrd DNS != reverse DNS. That is, the PTR record
Nobody should be checking forward == reverse(forward), it is
reverse == forward(reverse) that is important.
--
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmVHI~} [EMAIL PROTECTED]
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Re: location of UnicodeData.txt
On Sat, Nov 30, 2002 at 12:35:25PM -0500, Jim Penny wrote: I think you are missing the points here. First of all, DFSG applied to the standard does not want to change the standard, but wants all to be able to change the text of the standard. Huh? If I change the text of the standard, I have changed the standard! No you haven't, only the standards body in question can do that. There are all sorts of reasons why you might wish to create derivative works based on the standard -- a new standard for a different purpose, for example. Or helpful documentation of the standard for people who are intimidated by the 'dry' nature of the original... On the other hand, if you wish to create a competitor to the unicode standard, say the debicode standard, I see no moral right that you have to incorporate, without permission, the unicode standard. You should expect to start from scratch! Engage brain. Do you think that if I want to create a competitor to, say, GNU Emacs, that I should expect to have to start from scratch? Or fetchmail? Or any one of the thousands of DFSG-free packages that are in main? Cheers, Nick -- Nick Phillips -- [EMAIL PROTECTED] Tomorrow will be cancelled due to lack of interest.
Re: Are we losing users to Gentoo?
On Sat, Nov 30, 2002 at 11:56:59AM +0100, Josip Rodin wrote: On Sat, Nov 30, 2002 at 11:23:23PM +1300, Nick Phillips wrote: Joy (or any of the rest of the www team) - where do you get the data to put into the mirror pages on www.d.o? Well, we get it from the Internet :) Please rephrase the question, I don't understand. Well, do the admins just send you a mail, do you list any that you happen to come across when randomly surfing around, do you have any more structured way for admins to tell you what they plan to mirror...? We already have that, but notice how the mirrors of the two archives aren't in the least bit of distress like the problem at hadn: the structure and contents of those is well defined, we have mirror checking scripts and we regularly monitor the output of that for any major problems. (I would suggest that you have a look at http://www.debian.org/mirror/) Hmmm... the link to Debian mirrors that include the debian-cd archive actually takes me to a useful-ish list... at least, some of the sites listed do have iso images. It's not terribly helpful if it's not linked to in such a way that it will be found by someone looking for CD images, though. The CD image mirrors don't even have a primary site -- *cdimage.d.o includes only jigdo files now. Those image mirrors are one big improvization. Doesn't matter whether there's a primary site that is only accessible to official mirrors, or whether they all have to get the images in some other way, so long as it is simple for them to automate keep up to date. And so long as the directory structure of all the mirrors is the same, for the parts that they mirror... Cheers, Nick -- Nick Phillips -- [EMAIL PROTECTED] You will soon forget this.
Re: Are we losing users to Gentoo?
On Sun, Dec 01, 2002 at 11:20:10AM +1300, Nick Phillips wrote: Joy (or any of the rest of the www team) - where do you get the data to put into the mirror pages on www.d.o? Well, we get it from the Internet :) Please rephrase the question, I don't understand. Well, do the admins just send you a mail, do you list any that you happen to come across when randomly surfing around, do you have any more structured way for admins to tell you what they plan to mirror...? All three. :) But mostly the third, via http://www.debian.org/mirror/submit Note s/plan to//. We already have that, but notice how the mirrors of the two archives aren't in the least bit of distress like the problem at hadn: the structure and contents of those is well defined, we have mirror checking scripts and we regularly monitor the output of that for any major problems. (I would suggest that you have a look at http://www.debian.org/mirror/) Hmmm... the link to Debian mirrors that include the debian-cd archive actually takes me to a useful-ish list... at least, some of the sites listed do have iso images. It's not terribly helpful if it's not linked to in such a way that it will be found by someone looking for CD images, though. It's the HTTP/FTP link on the CD pages... The CD image mirrors don't even have a primary site -- *cdimage.d.o includes only jigdo files now. Those image mirrors are one big improvization. Doesn't matter whether there's a primary site that is only accessible to official mirrors, or whether they all have to get the images in some other way, so long as it is simple for them to automate keep up to date. When there's nothing official in the US, it's understandable that the secondary mirror maintainers in the US will be reluctant to mirror from elsewhere. And so long as the directory structure of all the mirrors is the same, for the parts that they mirror... There isn't really a site to dictate the standard directory structure, so the best thing we could do is proclaim one of the existing ones standard. Heck, not even the directory name is standardized, there's debian-cd, debian-iso, debian-cdimage, ... -- 2. That which causes joy or happiness.
Re: [Agnubis] Packaging Agnubis for Debian GNU/Linux
Le sam 30/11/2002 à 11:27, Andrew Lau a écrit : On Fri, Nov 29, 2002 at 04:20:09PM +0100, Amaya wrote: Condider that his ITP has been there for two months. He's either not that motivated or simply busy. And NM is much more time consuming than closing an ITP. Offer your help, whatever help you are willing or able to give. If he is too busy to package whatever was that depended so heavily on Agnubis, offer to retitle the bug to a RFP. It's the other way around. Agnubis depends on DiaCanvas2 which he has ITPed. Agnubis doesn't have any releases yet, but I was hoping to start doing CVS snapshots in preparations for their eventual release. So if I were to release Agnubis (still impossible since they taking a brief break from development and their CVS src is currently not building), I'd have to package DiaCanvas2 as well, and thus rudely hijacking the poor bloke's ITP. That why I hope he can show me to committed, otherwise I will have no choice but to hijack it in order to release Agnubis .deb packages. This is a mistake. I don't want to block packaging of Agnubis or DiaCanvas2 but, I've already make some jobs about DiaCanvas2. If you want to make yours from scratch, it's your choice after all. However, this is avaible on this apt's uri: deb http://debian.linuxfr.net/ ./ deb-src http://debian.linuxfr.net/ ./ I've started diacanvas2 but I've got a new job so I'm busy a lot. That's all. I'm just thinking we can make this job you and me... Cheers, -- Raphaël Bordet [EMAIL PROTECTED]
Re: debian jabber packages
On Wed, Nov 27, 2002 at 01:35:23AM +0100, Bernd Eckenfels wrote: I will send the latest jabber diff with some comments to Jamin and ask him to quickly make an upload with changed maintainer field. After that he can start to work on the new Version. Jamin, I have an (yet unused) CVS repository access on the jabber server for a debian sub repository. I will hand that over to you if I can find the details :) I hope there will be an upgrade path from the jabberd 1.x versions to the jabberd 2.x versions, as the 2.0 version still lacks support for xdb userfiles (currently supported are db and anon) and all the migration scripts are yet to be written.. also the db fileformat is now (since alpha 2) dependant of libdb4.1 which is yet to be packaged.. This is just a heads up and all. Sami -- - Sami Haahtinen - -[ Notify immediately if you do not receive this message ]- - 2209 3C53 D0FB 041C F7B1 F908 A9B6 F730 B83D 761C -
Re: Are we losing users to Gentoo?
* Joey Hess | Of course debian-installer should support 1.4 mb net install floppies | too. s/should support/supports/ -- Tollef Fog Heen,''`. UNIX is user friendly, it's just picky about who its friends are : :' : `. `' `-
Re: Pick a name, any name...
On Sun, Dec 01, 2002 at 08:56:37AM +1100, Herbert Xu wrote: Nobody should be checking forward == reverse(forward), it is reverse == forward(reverse) that is important. s/is important/was important/ Mike Stone
Re: Are we losing users to Gentoo?
On Sat, Nov 30, 2002 at 04:06:40PM -0500, Joey Hess wrote: The problem with the net installs isos is mainly that they are unofficial and there are several varying cd's produced by different folks, and of varying quality (though quality is overall good; I've used Yeah. The i386 all work afaik, but the last ppc install I tried with mini-iso's failed horribly because important things (like the appropriate boot kernel) were missing. The official iso's worked great. :) Mike Stone
Re: free alternative to povray?
On Mon, Nov 18, 2002 at 11:33:30PM +, Stephen Stafford wrote: /usr/share/povray/ in the povray-doc package. Does this mean that blender uses the same file format as blender? (that was the original question). Are there any DFSG examples for blender? -- Brian May [EMAIL PROTECTED]
Re: Are we losing users to Gentoo?
On Nov 30, Nick Phillips [EMAIL PROTECTED] wrote: I'm with Joey on this; last time I tried to find Debian .iso images, it was a nightmare. In fact I couldn't find an official woody iso anywhere. This is the way of mirror operators to tell you that you should really use jigdo or even better the mini-images. -- ciao, Marco pgpQyjrl63F3k.pgp Description: PGP signature
Re: free alternative to povray?
On Sun, Dec 01, 2002 at 11:30:45AM +1100, Brian May wrote: On Mon, Nov 18, 2002 at 11:33:30PM +, Stephen Stafford wrote: /usr/share/povray/ in the povray-doc package. Does this mean that blender uses the same file format as blender? (that was the original question). Blender definitely does not use the same file format as Povray. Blender uses a binary format that stores everything in one file, and is triangle-oriented (mostly). Blender is really fundimentally different from Povray, it is a zbuffer renderer, whereas povray is a raytracer. For a raytracer that DOES use the same file format as Povray, I'd recommend zrcube. It isn't packaged yet, but looks very nice overall, and is more advanced than Povray in some ways, especially in that it adds radiosity for realistic lighting. http://zrcube.sf.net/ Incidently, the other raytracer mentioned in this thread, yafray, has a plugin for Blender to export to the Yafray format on their site. Its pretty simplistic, but its something. Yafray uses an XML-based format. Yafray boasts some really outstanding radiosity output. Yafray is also not packaged. http://www.coala.uniovi.es/~jandro/noname Are there any DFSG examples for blender? Well, the best examples are in the form of tutorials, which abound online. Its not really meaningful to have the files themselves, when in blender's case its the process that is important. HTH nick -- -- Nick Rusnov -- http://nick.industrialmeats.com -- [EMAIL PROTECTED]/[EMAIL PROTECTED]
Re: Bug#171116: ITP: tsclient -- GNOME2 frontend for rdesktop
On Sat, Nov 30, 2002 at 10:36:02AM -0600, Graham Wilson wrote: gnome 1 probably is not going to be in sarge, so the difference between gnome 1 and gnome 2 arent going to matter to someone installing sarge. But some people do deliberately apt-cache search GNOME 2 to find new GTK+2.0 based software that they want to try out. A lot of software that was originally written for GNOME 1.x, but still have no GNOME 2 equivalent are more often than not no longer maintained by upstream, and thus avoided by some. It's psychology, I'm afraid. Almost every other GNOME 2 application is doing this as well. Yours sincerely, Andrew Netsnipe Lau -- --- * Andrew Netsnipe LauComputer Science Student Representaive, UNSW * * # apt-get into it Debian GNU/Linux Package Maintainer * * netsnipe(+)debianplanet.org\0 alau(+)cse.unsw.edu.au\0 * * GnuPG 1024D/2E8B68BD 0B77 73D0 4F3B F286 63F1 9F4A 9B24 C07D 2E8B 68BD * --- pgpMFQwuncjEt.pgp Description: PGP signature
Re: Bug#171116: ITP: tsclient -- GNOME2 frontend for rdesktop
I agree with this logic. Generally if I search for a GTK 2.x theme engine with apt-cache, I search for gtk2-blah, not gtk-blah, since by convention gtk- strictly means gtk 1.x only. Andrew Lau wrote: But some people do deliberately apt-cache search GNOME 2 to find new GTK+2.0 based software that they want to try out. A lot of software that was originally written for GNOME 1.x, but still have no GNOME 2 equivalent are more often than not no longer maintained by upstream, and thus avoided by some. It's psychology, I'm afraid. Almost every other GNOME 2 application is doing this as well.
Cost Effective Product Documentation
Re: reliable streams over UDP
Shyamal Prasad wrote: Russell Surely someone must have written something similar to TCP Russell but implemented on top of UDP. Too many people have tried this ;-) Try SCTP, a recent attempt to deal with the reliable UDP solution: The 2.5.50 kernel has a SCTP implementation. Dunno how well/if it works, but the option is there. Steve [EMAIL PROTECTED]
Re: [RFH] The need for signed packages and signed Releases (long, long)
Andrew Suffield wrote: On Sun, Nov 17, 2002 at 03:24:15AM +0100, Bernd Eckenfels wrote: Yes, and avoiding binary uploads by maintainers can make the system a bit more transparently auditable. Not to mention making it break a lot more. Quit beating that horse, it's already been buried. reference to thread(s), please (general time frame and applicable list(s) should be good enough. i hate attempting blind searches through the debian archives) -john
Re: Are we losing users to Gentoo?
On Sat, Nov 30, 2002 at 09:23:43PM +0100, Marco d'Itri wrote: On Nov 30, Nick Phillips [EMAIL PROTECTED] wrote: I'm with Joey on this; last time I tried to find Debian .iso images, it was a nightmare. In fact I couldn't find an official woody iso anywhere. This is the way of mirror operators to tell you that you should really use jigdo or even better the mini-images. If there are to be no .iso images anywhere (which would suck), then it should say in big letters that there are no iso images anywhere. There are times when a .iso really is what you need, and when those times come, it really sucks badly to force people to search through a whole list of mirrors that are in reality nothing of the sort and most of which don't have what you need (and what our pages say they have). :-/ But joeyh appears to be on the case, so I am confident that the situation will be rectified before too long... :) Cheers, Nick -- Nick Phillips -- [EMAIL PROTECTED] It may or may not be worthwhile, but it still has to be done.
Accepted subversion 0.15.0-1 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 29 Nov 2002 10:19:14 -0800 Source: subversion Binary: libsvn0 python2.2-subversion subversion-server subversion-tools libapache2-dav-svn libsvn0-dev subversion Architecture: source all i386 Version: 0.15.0-1 Distribution: unstable Urgency: low Maintainer: David Kimdon [EMAIL PROTECTED] Changed-By: David Kimdon [EMAIL PROTECTED] Description: libapache2-dav-svn - Apache module for Subversion - in development, alpha libsvn0- Subversion shared libraries - in development, alpha libsvn0-dev - Subversion development files - in development, alpha python2.2-subversion - Python modules for Subversion interface subversion - Advanced version control system - in development, alpha subversion-server - Tools for creating and maintaining a Subversion repository subversion-tools - Tools for Subversion Closes: 169796 169797 Changes: subversion (0.15.0-1) unstable; urgency=low . * New upstream release. * Add dependancy on libdb4.0-util for subversion and libapache2-dav-svn packages. In case a repository gets wedged we want db4.0_recover available. Fix paths in hot-backup.py (closes: #169797, #169796) * Doc install cleanup thanks to Jon Middleton [EMAIL PROTECTED] * aprutl version checking hack, thanks to Jon Middleton [EMAIL PROTECTED] * Include a statically linked svnadmin that we can copy to svnadmin-$(VERSION) on upgrade if the repository format changes. This facilitates a repository dump/reload. Files: 5304fc39943068c7d15e958118b220fc 899 devel extra subversion_0.15.0-1.dsc f8f408364f993bfb83382e709b74312f 4061263 devel extra subversion_0.15.0.orig.tar.gz 120b180dd1e4cfb843e8a3a1553ce75d 112877 devel extra subversion_0.15.0-1.diff.gz 58df0056c528b8c972ce84c76d8248cb 838158 devel extra subversion_0.15.0-1_i386.deb 9b641a38a2da1d27c64895d5465b80fd 261720 libs extra libsvn0_0.15.0-1_i386.deb 107142150c1724a402aaaf0ef8e2bd10 388040 devel extra libsvn0-dev_0.15.0-1_i386.deb 89ae1b7606e4b51b7bbf6bcb7a18828f 34532 net extra libapache2-dav-svn_0.15.0-1_i386.deb c5733381b1f426524d5445979559a07b 91452 libs extra python2.2-subversion_0.15.0-1_i386.deb 2eb6ddb9119137bc26e625418389a2d5 32486 admin extra subversion-tools_0.15.0-1_all.deb 0fd1f360645bbc561e9c406ea1b46473 6734 admin extra subversion-server_0.15.0-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE96GFfST1m+6jv1gMRAuQBAJ9wmOPeQLcFSpp1lxS9lybtgTNz/ACfc+v1 nnNj/TRSa20233ROrly7y1E= =3nLE -END PGP SIGNATURE- Accepted: libapache2-dav-svn_0.15.0-1_i386.deb to pool/main/s/subversion/libapache2-dav-svn_0.15.0-1_i386.deb libsvn0-dev_0.15.0-1_i386.deb to pool/main/s/subversion/libsvn0-dev_0.15.0-1_i386.deb libsvn0_0.15.0-1_i386.deb to pool/main/s/subversion/libsvn0_0.15.0-1_i386.deb python2.2-subversion_0.15.0-1_i386.deb to pool/main/s/subversion/python2.2-subversion_0.15.0-1_i386.deb subversion-server_0.15.0-1_all.deb to pool/main/s/subversion/subversion-server_0.15.0-1_all.deb subversion-tools_0.15.0-1_all.deb to pool/main/s/subversion/subversion-tools_0.15.0-1_all.deb subversion_0.15.0-1.diff.gz to pool/main/s/subversion/subversion_0.15.0-1.diff.gz subversion_0.15.0-1.dsc to pool/main/s/subversion/subversion_0.15.0-1.dsc subversion_0.15.0-1_i386.deb to pool/main/s/subversion/subversion_0.15.0-1_i386.deb subversion_0.15.0.orig.tar.gz to pool/main/s/subversion/subversion_0.15.0.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted lesstif1-1 1:0.93.36-5 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Format: 1.7 Date: Sat, 30 Nov 2002 19:32:21 +1100 Source: lesstif1-1 Binary: lesstif-bin lesstif-dev lesstif2-dev lesstif1 lesstif-doc lesstif2 Architecture: source i386 all Version: 1:0.93.36-5 Distribution: unstable Urgency: low Maintainer: Herbert Xu [EMAIL PROTECTED] Changed-By: Herbert Xu [EMAIL PROTECTED] Description: lesstif-bin - User binaries for LessTif. lesstif-dev - Development library and header files for LessTif 1.2. lesstif-doc - Documentation for LessTif. lesstif1 - OSF/Motif 1.2 implementation released under LGPL. lesstif2 - OSF/Motif 2.1 implementation released under LGPL. lesstif2-dev - Development library and header files for LessTif 2.1. Closes: 171220 Changes: lesstif1-1 (1:0.93.36-5) unstable; urgency=low . * Conflict and replace various libmotif packages (closes: #171220). Files: a54e332e8c85dad9758cd9b77973f606 843 libs optional lesstif1-1_0.93.36-5.dsc 08c2d47f80163560e448779ba2971042 14816 libs optional lesstif1-1_0.93.36-5.diff.gz 5e9104d423659189d8308e321c3e2e68 340312 doc optional lesstif-doc_0.93.36-5_all.deb 691131b0d9f24a1a3050c0966877339c 606644 libs optional lesstif2_0.93.36-5_i386.deb 99213ee680a920720c2526ad0221d135 542088 oldlibs optional lesstif1_0.93.36-5_i386.deb 0cf12b78b3057a2254b801a155cdbabd 858188 devel optional lesstif2-dev_0.93.36-5_i386.deb 1f0ec6fb92d4b536269970d718ce14a8 745642 devel extra lesstif-dev_0.93.36-5_i386.deb 46971542563660f6ec6620c5ab7423f8 149616 x11 optional lesstif-bin_0.93.36-5_i386.deb -BEGIN PGP SIGNATURE- Version: PGPfreeware 5.0i for non-commercial use Charset: noconv iQCVAwUBPeh8JofMnsf5AzQhAQGBMwP8CxjjVWmm3d7uzsS2OZHSmWrJatGQd7ix GZUEBXAr0SHTHa2LoRfMjGeIojI7v2ORx4v9msoPac/ga264nWxtpGHpVfSCEQZj sdw5p9YA5kKonh27ykJ6ZC5jrxKRUOCN7ZxN4KDUVB+YkG3Nkq/sPZ97kxoJRi+t nWpj2m30DPk= =94cX -END PGP SIGNATURE- Accepted: lesstif-bin_0.93.36-5_i386.deb to pool/main/l/lesstif1-1/lesstif-bin_0.93.36-5_i386.deb lesstif-dev_0.93.36-5_i386.deb to pool/main/l/lesstif1-1/lesstif-dev_0.93.36-5_i386.deb lesstif-doc_0.93.36-5_all.deb to pool/main/l/lesstif1-1/lesstif-doc_0.93.36-5_all.deb lesstif1-1_0.93.36-5.diff.gz to pool/main/l/lesstif1-1/lesstif1-1_0.93.36-5.diff.gz lesstif1-1_0.93.36-5.dsc to pool/main/l/lesstif1-1/lesstif1-1_0.93.36-5.dsc lesstif1_0.93.36-5_i386.deb to pool/main/l/lesstif1-1/lesstif1_0.93.36-5_i386.deb lesstif2-dev_0.93.36-5_i386.deb to pool/main/l/lesstif1-1/lesstif2-dev_0.93.36-5_i386.deb lesstif2_0.93.36-5_i386.deb to pool/main/l/lesstif1-1/lesstif2_0.93.36-5_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted nullmailer 1.00RC5-23 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 23 Nov 2002 16:15:00 +0100 Source: nullmailer Binary: nullmailer Architecture: source i386 Version: 1.00RC5-23 Distribution: unstable Urgency: low Maintainer: Martin A. Godisch [EMAIL PROTECTED] Changed-By: Martin A. Godisch [EMAIL PROTECTED] Description: nullmailer - Simple relay-only mail transport agent Closes: 170079 Changes: nullmailer (1.00RC5-23) unstable; urgency=low . * Let sendmail exit with failure when -bs is requested, closes: #170079. * Updated Debian standards version. Files: fcf6c31f88aec6514756e71e0cd27f85 598 mail optional nullmailer_1.00RC5-23.dsc de668683bf55e93a937d7ea1e6f6d242 10763 mail optional nullmailer_1.00RC5-23.diff.gz 0ed32ac7e30b6823089c4569cd6c9765 66232 mail optional nullmailer_1.00RC5-23_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE96H13FgAj91iLfZwRAsUxAJwL9TU0T2E8HrsxQNjC53BBN0GvigCfeMKN 8HDUgyhVoGRT0cyiBLFZ/B8= =zeup -END PGP SIGNATURE- Accepted: nullmailer_1.00RC5-23.diff.gz to pool/main/n/nullmailer/nullmailer_1.00RC5-23.diff.gz nullmailer_1.00RC5-23.dsc to pool/main/n/nullmailer/nullmailer_1.00RC5-23.dsc nullmailer_1.00RC5-23_i386.deb to pool/main/n/nullmailer/nullmailer_1.00RC5-23_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted aumix 2.8-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 30 Nov 2002 11:46:34 +0100 Source: aumix Binary: aumix aumix-gtk Architecture: source i386 Version: 2.8-2 Distribution: unstable Urgency: medium Maintainer: Bas Zoetekouw [EMAIL PROTECTED] Changed-By: Bas Zoetekouw [EMAIL PROTECTED] Description: aumix - Simple text-based mixer control program aumix-gtk - Simple mixer control program with GUI and text interfaces Closes: 171225 Changes: aumix (2.8-2) unstable; urgency=medium . * Explicitly mkdir the stampdir (closes: #171225) * Removed build-dependency on autoconf, automake Files: d78b1717f018de5362254164375f940d 898 sound optional aumix_2.8-2.dsc fb8b79ef71fbecff7ae432d503cfdcb1 16101 sound optional aumix_2.8-2.diff.gz 2e24cba18f3cde2a29367f1ef8e59227 73164 sound extra aumix_2.8-2_i386.deb dd1c97567400d09e551921a738a8c3bb 81806 sound optional aumix-gtk_2.8-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iQEXAwUBPeiZLJ6S+2TcVAFTFAIT8gP/YbZKhRe3aNq0gvSP5/IlEzJ2TizAfaZV 9npCUhEC/j4Gtwd9AyiQWU9ctr1EH7S8eM7HzbRXW+5G3mrckvWJ7QyzKEbHJovd 2d19wnkuFk/0Z+lwcSUPv4mZIWN941nkDHt1ot/+2eIoCE4WxN8IfB+srS8ksGQf odvcARSZjbUD/0cmlXr6Yb2LwYbczUfKksEusUvlM85+fiemoZKIRk1Qk1hOV2x+ cq568LIu10QBFgprSLG9OjUmHsGh89SuO25PI2BbEFU5q5D1iPnph0SRkJANzneT o9+xEZ0CKtqALUr2HFOMWhwVGrF+vTYZFo4KzcZ8ca/XJ61PZplSSYpH =Q2LZ -END PGP SIGNATURE- Accepted: aumix-gtk_2.8-2_i386.deb to pool/main/a/aumix/aumix-gtk_2.8-2_i386.deb aumix_2.8-2.diff.gz to pool/main/a/aumix/aumix_2.8-2.diff.gz aumix_2.8-2.dsc to pool/main/a/aumix/aumix_2.8-2.dsc aumix_2.8-2_i386.deb to pool/main/a/aumix/aumix_2.8-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted muttprint 0.63a-5 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 30 Nov 2002 12:00:50 +0100 Source: muttprint Binary: muttprint Architecture: source all Version: 0.63a-5 Distribution: unstable Urgency: low Maintainer: Rene Engelhard [EMAIL PROTECTED] Changed-By: Rene Engelhard [EMAIL PROTECTED] Description: muttprint - Pretty printing of mails with Mutt Closes: 170658 170821 Changes: muttprint (0.63a-5) unstable; urgency=low . * Description: s/XFMail and PINE//, s/Netscape Messenger/Mozilla/ and restructured the lines (closes: #170658) * do not specify PAPER; let muttprint get that from /etc/papersize (closes: #170821) Files: 6cfc4924bf842f91d13b7673782babe3 622 mail optional muttprint_0.63a-5.dsc e04eb162eb4ba695c4c4282ec09ccfe7 7510 mail optional muttprint_0.63a-5.diff.gz 1257d02e73b7f6ab59d7581fb37c94a4 684334 mail optional muttprint_0.63a-5_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE96JxR+FmQsCSK63MRApuHAJ45pMsGE2coiQ+dRDUx3PTPF9jKgQCdEMkK M05yDeyaPMjKNKUm39fCmck= =iDg7 -END PGP SIGNATURE- Accepted: muttprint_0.63a-5.diff.gz to pool/main/m/muttprint/muttprint_0.63a-5.diff.gz muttprint_0.63a-5.dsc to pool/main/m/muttprint/muttprint_0.63a-5.dsc muttprint_0.63a-5_all.deb to pool/main/m/muttprint/muttprint_0.63a-5_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gpsdrive 1.30-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 30 Nov 2002 12:18:33 +0100 Source: gpsdrive Binary: gpsdrive Architecture: source i386 Version: 1.30-1 Distribution: unstable Urgency: low Maintainer: Frank Kirschner [EMAIL PROTECTED] Changed-By: Frank Kirschner [EMAIL PROTECTED] Description: gpsdrive - Car navigation system. Closes: 170823 Changes: gpsdrive (1.30-1) unstable; urgency=low . * new upstream release. (closes: #170823) Files: d836ba55e83b4d99f75883ac2e393f71 678 utils optional gpsdrive_1.30-1.dsc 5bf9c3247348e6d65f30318f9d3326fd 821758 utils optional gpsdrive_1.30.orig.tar.gz 8c63bd915fcc3982954ae70a68aa 2016 utils optional gpsdrive_1.30-1.diff.gz c8044984963a0906ce2d6f252a212814 579550 utils optional gpsdrive_1.30-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE96KPS8UXMXiC+9cQRAt76AKDYOsXDrzTfscoGtsIq9YTfzRYV4ACdF5s5 i2DgD3B8Bem77/YTv3J3xYQ= =w7kd -END PGP SIGNATURE- Accepted: gpsdrive_1.30-1.diff.gz to pool/main/g/gpsdrive/gpsdrive_1.30-1.diff.gz gpsdrive_1.30-1.dsc to pool/main/g/gpsdrive/gpsdrive_1.30-1.dsc gpsdrive_1.30-1_i386.deb to pool/main/g/gpsdrive/gpsdrive_1.30-1_i386.deb gpsdrive_1.30.orig.tar.gz to pool/main/g/gpsdrive/gpsdrive_1.30.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted wmcoincoin 2.4.2a-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 30 Nov 2002 12:39:46 +0100 Source: wmcoincoin Binary: wmcoincoin Architecture: source i386 Version: 2.4.2a-1 Distribution: unstable Urgency: low Maintainer: Josselin Mouette [EMAIL PROTECTED] Changed-By: Josselin Mouette [EMAIL PROTECTED] Description: wmcoincoin - Funny dockapp for browsing DaCode sites news and board Changes: wmcoincoin (2.4.2a-1) unstable; urgency=low . * New upstream release * Standards version is 3.5.8. * Use debhelper mode 4 and dh_install. Files: 450cea5052991b650a86a538957c67bc 614 x11 extra wmcoincoin_2.4.2a-1.dsc 12fd581579175581f70bf62f3daff22e 656883 x11 extra wmcoincoin_2.4.2a.orig.tar.gz aa0f4cac7ce6d3eb8aebb6cdb448f96b 3586 x11 extra wmcoincoin_2.4.2a-1.diff.gz 75f1fd7ed23f809fda394ab65e5c0b87 306116 x11 extra wmcoincoin_2.4.2a-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE96LMIrSla4ddfhTMRApWjAKCRX6bir9UkNifz754pTIXylsoayACg+gtO g8mV/sAM/3Mb2DM9nNFIJRo= =OqCk -END PGP SIGNATURE- Accepted: wmcoincoin_2.4.2a-1.diff.gz to pool/main/w/wmcoincoin/wmcoincoin_2.4.2a-1.diff.gz wmcoincoin_2.4.2a-1.dsc to pool/main/w/wmcoincoin/wmcoincoin_2.4.2a-1.dsc wmcoincoin_2.4.2a-1_i386.deb to pool/main/w/wmcoincoin/wmcoincoin_2.4.2a-1_i386.deb wmcoincoin_2.4.2a.orig.tar.gz to pool/main/w/wmcoincoin/wmcoincoin_2.4.2a.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cqcam 0.91-3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 10 Oct 2002 22:17:00 -0400 Source: cqcam Binary: libcqcam-dev cqcam Architecture: source i386 Version: 0.91-3 Distribution: unstable Urgency: low Maintainer: Daniel Martin [EMAIL PROTECTED] Changed-By: Daniel Martin [EMAIL PROTECTED] Description: cqcam - Color QuickCam (PC/Parallel) control program libcqcam-dev - Color QuickCam (PC/Parallel) control library Closes: 40986 164095 Changes: cqcam (0.91-3) unstable; urgency=low . * Added Build-Depends on tk8.3-dev; this causes the control console to appear with xcqcam (closes: Bug#40986) * Added fourth argument to AC_CHECK_HEADER in configure.in; this makes autoconf 2.54 happy. (closes: Bug#164095) Files: 44f4c1fc44050bd98d50e6343f94a3ff 948 - extra cqcam_0.91-3.dsc 223266441fa59ce8475c776deb950f17 25301 - extra cqcam_0.91-3.diff.gz 8b9d6612808d009c31292872b3aae874 98612 graphics extra cqcam_0.91-3_i386.deb 147438d73b3239bbf87506cedd5a15c9 21234 devel extra libcqcam-dev_0.91-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iQEXAwUBPejH6+R45Q7FWKyMFAItoAP/YHQMPLgMAvhc9tNHlxaZF24tJnWXlN/X /+kK5+es3MpQJDoE7mjgm4UBYzW5/jLWYJE0a8h+FV0WsvkefGeeLbCGULaUbFGC z95N8oJNg6hY8v+72pyd/nIB2XQuKGddaYHIrLdfYfWZMb1Hck/84BYrAu3lcupu 0rZwDfyGp3MD/j7h42laYYX7TwAQo6UEjf4VANoSvHLO5OHEsQG1YqqKrmjQc+BE +J/2UtE+Gnen1PCFM+fmCs/EYh8lwIkCF2Yz0V91kbTj2puZ44BlJpw4K44efye2 LKSPQhhiH2J4GYhn0SCTvPjTl8lhaz9phoVjmYqxiRUVlTPcsyLF9Q+P =WuY3 -END PGP SIGNATURE- Accepted: cqcam_0.91-3.diff.gz to pool/main/c/cqcam/cqcam_0.91-3.diff.gz cqcam_0.91-3.dsc to pool/main/c/cqcam/cqcam_0.91-3.dsc cqcam_0.91-3_i386.deb to pool/main/c/cqcam/cqcam_0.91-3_i386.deb libcqcam-dev_0.91-3_i386.deb to pool/main/c/cqcam/libcqcam-dev_0.91-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted speedy-cgi-perl 2.21-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 30 Nov 2002 16:02:51 +0100 Source: speedy-cgi-perl Binary: libapache-mod-speedycgi speedy-cgi-perl Architecture: source i386 Version: 2.21-2 Distribution: unstable Urgency: low Maintainer: Jose Carlos Garcia Sogo [EMAIL PROTECTED] Changed-By: Jose Carlos Garcia Sogo [EMAIL PROTECTED] Description: libapache-mod-speedycgi - apache module to speed up perl scripts by making them persistent. speedy-cgi-perl - speed up perl scripts by making them persistent. Closes: 166672 Changes: speedy-cgi-perl (2.21-2) unstable; urgency=low . * Added support for both apache and apache-ssl packages. (Closes: #166672) Files: da12739d321ea9d7222e597021cf5abb 657 interpreters optional speedy-cgi-perl_2.21-2.dsc 15836f7963657f4990ee53d70e28c5d1 5558 interpreters optional speedy-cgi-perl_2.21-2.diff.gz fc30f74b3dbf21a688c4c45e51948ad5 96382 interpreters optional speedy-cgi-perl_2.21-2_i386.deb 18bc660babc1ba323a1d36b9681c0d6a 28660 web optional libapache-mod-speedycgi_2.21-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE96NQSS+BYJZB4jhERArDpAJ4h83oQ+dZFHfjCxktVrmbPW18tbQCgsF34 fJrB/hv3GrieZQ8v9mK9QlI= =bKmc -END PGP SIGNATURE- Accepted: libapache-mod-speedycgi_2.21-2_i386.deb to pool/main/s/speedy-cgi-perl/libapache-mod-speedycgi_2.21-2_i386.deb speedy-cgi-perl_2.21-2.diff.gz to pool/main/s/speedy-cgi-perl/speedy-cgi-perl_2.21-2.diff.gz speedy-cgi-perl_2.21-2.dsc to pool/main/s/speedy-cgi-perl/speedy-cgi-perl_2.21-2.dsc speedy-cgi-perl_2.21-2_i386.deb to pool/main/s/speedy-cgi-perl/speedy-cgi-perl_2.21-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted yardradius 1.0.20-5 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 30 Nov 2002 17:39:31 +0100 Source: yardradius Binary: yardradius Architecture: source i386 Version: 1.0.20-5 Distribution: unstable Urgency: low Maintainer: Francesco Paolo Lovergine [EMAIL PROTECTED] Changed-By: Francesco Paolo Lovergine [EMAIL PROTECTED] Description: yardradius - YARD Radius Auth/Acct Server Closes: 170895 Changes: yardradius (1.0.20-5) unstable; urgency=low . * Added french template. (closes: #170895) * Added a versioned debconf dependency in order to be lintian clean. Files: 46b1aa9a74de8d1d0fb808828a08cdd6 619 net optional yardradius_1.0.20-5.dsc 839cb6eebbc9563e52d781287ca2fa56 8870 net optional yardradius_1.0.20-5.diff.gz 574b0943cc4916d0de66f5d947de10cc 296876 net optional yardradius_1.0.20-5_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE96OoRpFNRmenyx0cRApEJAKDfXjX/okVRY8bUXS5z350/TcVJjQCfVujD /fNTmeQ2qOPq7O5+w/eQUK8= =gGCr -END PGP SIGNATURE- Accepted: yardradius_1.0.20-5.diff.gz to pool/main/y/yardradius/yardradius_1.0.20-5.diff.gz yardradius_1.0.20-5.dsc to pool/main/y/yardradius/yardradius_1.0.20-5.dsc yardradius_1.0.20-5_i386.deb to pool/main/y/yardradius/yardradius_1.0.20-5_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted octave-forge 2002.11.30-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 30 Nov 2002 11:48:27 -0600 Source: octave-forge Binary: octave-forge Architecture: source i386 Version: 2002.11.30-1 Distribution: unstable Urgency: low Maintainer: Dirk Eddelbuettel [EMAIL PROTECTED] Changed-By: Dirk Eddelbuettel [EMAIL PROTECTED] Description: octave-forge - Contributed functions for GNU Octave from http://octave.sf.net Changes: octave-forge (2002.11.30-1) unstable; urgency=low . * Upgraded to new upstream release Files: c4ebcc17a5ad9274c7f8ecd39366b160 899 math optional octave-forge_2002.11.30-1.dsc b750c8d1e9911e92360306a8d8a9b79f 2198829 math optional octave-forge_2002.11.30.orig.tar.gz fae15057d9729a10525f3341fe50297d 16831 math optional octave-forge_2002.11.30-1.diff.gz 6fbf9fa4037e1a6722aa5b61fc06eaaf 1119200 math optional octave-forge_2002.11.30-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE96PsMCZSR95Gw07cRAviGAJsGC6xRaQ+alIhIxoDt+sucpgp8IgCfVWNx LaumiTR87MqEJGjzvHNzVsk= =pEiU -END PGP SIGNATURE- Accepted: octave-forge_2002.11.30-1.diff.gz to pool/main/o/octave-forge/octave-forge_2002.11.30-1.diff.gz octave-forge_2002.11.30-1.dsc to pool/main/o/octave-forge/octave-forge_2002.11.30-1.dsc octave-forge_2002.11.30-1_i386.deb to pool/main/o/octave-forge/octave-forge_2002.11.30-1_i386.deb octave-forge_2002.11.30.orig.tar.gz to pool/main/o/octave-forge/octave-forge_2002.11.30.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libabz 0.0.4 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 30 Nov 2002 20:11:03 +0200 Source: libabz Binary: libabz0-dev libabz0 Architecture: source i386 Version: 0.0.4 Distribution: unstable Urgency: low Maintainer: Abraham vd Merwe [EMAIL PROTECTED] Changed-By: Abraham vd Merwe [EMAIL PROTECTED] Description: libabz0- Miscellaneous useful routines libabz0-dev - Development files for the abz library Changes: libabz (0.0.4) unstable; urgency=low . * Updated the version (I screwed it up in 0.0.3). Files: 9e1d8384353f7fa3149df70f73033f44 570 devel optional libabz_0.0.4.dsc d6e5efaccfc134aa78e7d9b85da8239c 30877 devel optional libabz_0.0.4.tar.gz 2bde55d144d3f98ffc84adb97d2b26f1 9050 libs optional libabz0_0.0.4_i386.deb bd8ab9ebdb9b236c427145ef5ff17453 38304 devel optional libabz0-dev_0.0.4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.5 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE96P+VzvVjZitVWu4RAkG7AJwPaPJxBMEGWvO6nGOu9tFYDlGuhQCdErsm Aw7toD2l8K3RcPZGAIAzC6w= =I7c+ -END PGP SIGNATURE- Accepted: libabz0-dev_0.0.4_i386.deb to pool/main/liba/libabz/libabz0-dev_0.0.4_i386.deb libabz0_0.0.4_i386.deb to pool/main/liba/libabz/libabz0_0.0.4_i386.deb libabz_0.0.4.dsc to pool/main/liba/libabz/libabz_0.0.4.dsc libabz_0.0.4.tar.gz to pool/main/liba/libabz/libabz_0.0.4.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libabz 0.0.3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 30 Nov 2002 19:54:58 +0200 Source: libabz Binary: libabz0-dev libabz0 Architecture: source i386 Version: 0.0.3 Distribution: unstable Urgency: low Maintainer: Abraham vd Merwe [EMAIL PROTECTED] Changed-By: Abraham vd Merwe [EMAIL PROTECTED] Description: libabz0- Miscellaneous useful routines libabz0-dev - Development files for the abz library Closes: 170104 Changes: libabz (0.0.3) unstable; urgency=low . * Don't build shlibs with non-PIC code (Closes: #170104) Files: 7c49144bfbbfff27465986cb366807af 570 devel optional libabz_0.0.3.dsc 3758482947c487183ed848d2e4c5d075 27238 devel optional libabz_0.0.3.tar.gz 4398dcafe330e315f21ebabced715632 9014 libs optional libabz0_0.0.3_i386.deb ce59db022e0bb1caaab506197c788061 38272 devel optional libabz0-dev_0.0.3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.5 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE96P5RzvVjZitVWu4RAiG+AJ9kc5RTDBRBntC857yr9MH5PQ8pLACdGTWn 94IxxfHwik+DEjeOddDaO8o= =dih7 -END PGP SIGNATURE- Accepted: libabz0-dev_0.0.3_i386.deb to pool/main/liba/libabz/libabz0-dev_0.0.3_i386.deb libabz0_0.0.3_i386.deb to pool/main/liba/libabz/libabz0_0.0.3_i386.deb libabz_0.0.3.dsc to pool/main/liba/libabz/libabz_0.0.3.dsc libabz_0.0.3.tar.gz to pool/main/liba/libabz/libabz_0.0.3.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted vdkbuilder 1.2.5-11 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 30 Nov 2002 19:29:02 +0100 Source: vdkbuilder Binary: vdkbuilder libvdkbuilder-dev libvdkbuilder Architecture: source i386 Version: 1.2.5-11 Distribution: unstable Urgency: low Maintainer: Michael Vogt [EMAIL PROTECTED] Changed-By: Michael Vogt [EMAIL PROTECTED] Description: libvdkbuilder - Plugin libraries bundled with VDKBuilder libvdkbuilder-dev - Header files and static libraries for VDKBuilder plugins vdkbuilder - RAD for VDK Closes: 170203 170231 Changes: vdkbuilder (1.2.5-11) unstable; urgency=low . * removed xlib6g-dev from dependencies (closes: #170231, #170203) Files: 44bcf48b2d97bf9ce45374e9f40bdb56 730 - optional vdkbuilder_1.2.5-11.dsc d6088ceb10274acef67d81ef00777c40 22622 - optional vdkbuilder_1.2.5-11.diff.gz 71e16bab56e9361f0e83feaf1126ce9e 28652 devel optional libvdkbuilder-dev_1.2.5-11_i386.deb 75636ccf8a7f4a8821b0cac88e654067 25492 libs optional libvdkbuilder_1.2.5-11_i386.deb e6f0dbc426b11e40536145b693038c17 1370600 devel optional vdkbuilder_1.2.5-11_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE96QY1liSD4VZixzQRAqrXAJsEZzyHWbBOFRtIHaQ9daQiV/J+rQCbBQ0J Mm+81UIA1+gOZcr24hafRcg= =IZkL -END PGP SIGNATURE- Accepted: libvdkbuilder-dev_1.2.5-11_i386.deb to pool/main/v/vdkbuilder/libvdkbuilder-dev_1.2.5-11_i386.deb libvdkbuilder_1.2.5-11_i386.deb to pool/main/v/vdkbuilder/libvdkbuilder_1.2.5-11_i386.deb vdkbuilder_1.2.5-11.diff.gz to pool/main/v/vdkbuilder/vdkbuilder_1.2.5-11.diff.gz vdkbuilder_1.2.5-11.dsc to pool/main/v/vdkbuilder/vdkbuilder_1.2.5-11.dsc vdkbuilder_1.2.5-11_i386.deb to pool/main/v/vdkbuilder/vdkbuilder_1.2.5-11_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted lp-solve 3.99-4.0beta1-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Format: 1.7 Date: Mon, 25 Nov 2002 20:38:02 -0500 Source: lp-solve Binary: lp-solve Architecture: source i386 Version: 3.99-4.0beta1-1 Distribution: unstable Urgency: low Maintainer: James R. Van Zandt [EMAIL PROTECTED] Changed-By: James R. Van Zandt [EMAIL PROTECTED] Description: lp-solve - Solve (mixed integer) linear programming problems Closes: 170395 Changes: lp-solve (3.99-4.0beta1-1) unstable; urgency=low . * New upstream release (Closes:Bug#170395) * debian/rules: install new example files, install fortify.h, don't call suidregister * README.examples: run program with -S3 to print constraints * test-1: add -S3 flag * lp_solve.1: describe new options Files: dde5b45f67ae10bd86ead27f828a85c0 744 math optional lp-solve_3.99-4.0beta1-1.dsc e73a6b35f1a6793ec5f7b521fa255902 309256 math optional lp-solve_3.99-4.0beta1.orig.tar.gz 47bccff9c37fcb03248872e2f1908e17 13235 math optional lp-solve_3.99-4.0beta1-1.diff.gz 406ab4464c2cf57044a6e77bbd1bb619 259046 math optional lp-solve_3.99-4.0beta1-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.5 (GNU/Linux) Comment: For info see http://www.gnupg.org iQCVAwUBPekoNjHnPxTimJZtAQEArQP9E7dxYWPqSjf/IvUisSPvL52I4ss1tC8l Zg3EeOHO7ZUEKOoXqWIgJlwhv6PuQow+lqiQLTiANyHGgOVVpT5YqqLcGzn5pgzS j6P0qC/pSB2CwwL+RwqytNdbjbqquIYl23FoLD9XR6rEOQVUc//J97lsmte5YNHs 7goUzQj088w= =Iddp -END PGP SIGNATURE- Accepted: lp-solve_3.99-4.0beta1-1.diff.gz to pool/main/l/lp-solve/lp-solve_3.99-4.0beta1-1.diff.gz lp-solve_3.99-4.0beta1-1.dsc to pool/main/l/lp-solve/lp-solve_3.99-4.0beta1-1.dsc lp-solve_3.99-4.0beta1-1_i386.deb to pool/main/l/lp-solve/lp-solve_3.99-4.0beta1-1_i386.deb lp-solve_3.99-4.0beta1.orig.tar.gz to pool/main/l/lp-solve/lp-solve_3.99-4.0beta1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted chaksem 1.6a-2 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 1 Dec 2002 13:09:33 +1100 Source: chaksem Binary: chaksem Architecture: source all Version: 1.6a-2 Distribution: unstable Urgency: low Maintainer: Jamie Wilkinson [EMAIL PROTECTED] Changed-By: Jamie Wilkinson [EMAIL PROTECTED] Description: chaksem- a LaTeX class for presentations Changes: chaksem (1.6a-2) unstable; urgency=low . * Bumped standards-version to 3.5.8.0. * Set DH_COMPAT to 4. Files: 9636185a05bf008b3e23603e84c00276 563 tex optional chaksem_1.6a-2.dsc ec4fa7eba393509cb246c02679f6d17b 2209 tex optional chaksem_1.6a-2.diff.gz 8db6d5bcb97a21e659227951a1d29ad2 6066 tex optional chaksem_1.6a-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE96W+A5u9oNyz9HDgRAjILAJ9naUxqkYTzHlbyNoHxfyu0bpHpZQCfTweZ EdmrOsALkXudU8E1J6PC5xk= =En8C -END PGP SIGNATURE- Accepted: chaksem_1.6a-2.diff.gz to pool/main/c/chaksem/chaksem_1.6a-2.diff.gz chaksem_1.6a-2.dsc to pool/main/c/chaksem/chaksem_1.6a-2.dsc chaksem_1.6a-2_all.deb to pool/main/c/chaksem/chaksem_1.6a-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted hotkeys 0.5.6 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Nov 2002 23:27:29 +0800 Source: hotkeys Binary: hotkeys Architecture: source i386 Version: 0.5.6 Distribution: unstable Urgency: low Maintainer: Anthony Wong [EMAIL PROTECTED] Changed-By: Anthony Wong [EMAIL PROTECTED] Description: hotkeys- A hotkeys daemon for your Internet/multimedia keyboard in X Closes: 109007 116820 126334 127987 127987 135440 136326 144659 145028 145041 146029 149124 158843 162274 162398 163212 164821 Changes: hotkeys (0.5.6) unstable; urgency=low . * The one-version-to-merge-them-all, aka maintainer-is-now-back, release . * These account for NMU patches that I've merged: - acinclude.m4: check for libxml2 instead of libxml (Closes: #127987) - src/Makefile.am: added more SOURCES, put hotkeys.conf and splash.xpm to EXTRA_DIST, use LIBXOSD variables in build - src/conf.c: initialize dbenv to NULL (Closes: #127987) - src/conf.c: changed action of Play from 'xmms --play' to 'xmms --play-pause' (Closes: #162398, #136326) - src/hotkeys.c: modified function setKbdType such that user's definition file is preferred over the global one (Closes: #135440) - configure.in: added AM_MAINTAINER_MODE, use AM_PATH_LIBXOSD (provided by libxosd-dev) instead of my own AM_CHECK_LIBXOSD, so disable configure arguments --with-xosd-inc and --with-xosd-lib, check for libpthread - debian/control: Build-Depends: libxosd-dev (= 1.0.3-1), Conflicts: xmms ( 1.2.6-1) - debian/rules: in clean target, remove debian/debian and and make distclean instead of make clean, should be more policy compliant now - def/Makefile.am: add *.def to EXTRA_DIST - New key defs: hp5181 (Closes: #146029), logitech-cfo (renamed from logitec-cho) (Closes: #149124), kb9930 (Closes: #163212), orktekusb.def - Updated sk2500.def, leave keycode 151 untouched (Closes: #126334) - src/hotkeys.1 updated/corrected - src/hotkeys.conf: changed 'xmms --play' to 'xmms --play-pause' - Fixed all XOSD related bugs (Closes: #109007, #116820, #144659, #145041, #158843) - Thanks Junichi Uekawa (Closes: #162274, #164821), Bastian Blank, Michael Beattie and all bug reporters and patchers for your help and support =) . * These are my changes and additions: - debian/control: autoconf (= 2.56) - New gtk+ code for the splash screen, modified Makefile.am and configure.in accordingly. (As gnome-utils in Gnome2 no longer contain the splash program, Closes: #145028) - Added contributor node in all *.def, modified src/kbddef.c accordingly. - New key defs: ibook, pb5140w Files: 69347040842eb93031a282274a8e9019 583 x11 optional hotkeys_0.5.6.dsc 92fd2c782df823808b7d2efd49114c00 505124 x11 optional hotkeys_0.5.6.tar.gz e962aef6d3b423ba86e678c5e5dae599 141864 x11 optional hotkeys_0.5.6_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE95jT0NLOpoHvSL3QRAm/vAKDJEAONuZgyKPRnUAFtLJLb+6Kj5ACgvql/ E46ro+Fdl4KuOFXN4+B350A= =OO3K -END PGP SIGNATURE- Accepted: hotkeys_0.5.6.dsc to pool/main/h/hotkeys/hotkeys_0.5.6.dsc hotkeys_0.5.6.tar.gz to pool/main/h/hotkeys/hotkeys_0.5.6.tar.gz hotkeys_0.5.6_i386.deb to pool/main/h/hotkeys/hotkeys_0.5.6_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted x-symbol 4.43-5 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 2 Nov 2002 10:38:49 -0800 Source: x-symbol Binary: x-symbol Architecture: source all Version: 4.43-5 Distribution: unstable Urgency: low Maintainer: Steve Dunham [EMAIL PROTECTED] Changed-By: Steve Dunham [EMAIL PROTECTED] Description: x-symbol - WYSIWYG TeX mode for XEmacs Closes: 167385 Changes: x-symbol (4.43-5) unstable; urgency=low . * Fix font initialization on xemacs-gnome * Make global enabling of x-symbol a debconf option * Closes: #167385 Files: ceda6db658073a13f6d5741c7b5ea85e 574 editors optional x-symbol_4.43-5.dsc 03675e5ab493cdd791367028187e3649 12536 editors optional x-symbol_4.43-5.diff.gz e509e35065838174c67119caa59e419f 503106 editors optional x-symbol_4.43-5_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE96aF/iPgEjVqvb1kRApylAJ95VbYBhvnbXyanszot40i8YMniVQCfZuAn 8/cDMzCfNveFxQ/wJe7RKok= =SSk6 -END PGP SIGNATURE- Accepted: x-symbol_4.43-5.diff.gz to pool/main/x/x-symbol/x-symbol_4.43-5.diff.gz x-symbol_4.43-5.dsc to pool/main/x/x-symbol/x-symbol_4.43-5.dsc x-symbol_4.43-5_all.deb to pool/main/x/x-symbol/x-symbol_4.43-5_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
