Talks at DebConf in Oslo
I invite everyone to take a look at this years schedule for the talks and events at DebConf in Oslo. http://www.debconf.org/debconf3/schedule.php If you come to Oslo, take a look around the website. We hope to provide all the info you need. If you miss something, please contact [EMAIL PROTECTED] If you can't come to Oslo, take a look at the site and feel sorry for yourself and what you are missing out on. Hope to see you there, the DebConf Team pgpwaUoiQmrbf.pgp Description: PGP signature
Re: Essayez debconf avec l'interface Gnome
Quoting Christian Perrier ([EMAIL PROTECTED]): Petit conseil perso aux mainteneurs de paquets : essayez d'utiliser Infiniment désolé pour les fôtes de frappe qui constellent ce message... :-)
Re: Debconf or not debconf : Conclusion
On Sat, Jul 05, 2003 at 02:28:33PM -0500, Steve Langasek wrote: Yet another reasons for wanting to decouple installation and configuration is if some hardware company (such as VA^H^H Emperor Linux) wishes to ship Debian pre-installed on the system. In that case, installation happens at the factory, and not when the user receives it in his/her hot little hands. Given the number of config questions today that have to do with available hardware, I have a hard time believing that a strict split between installation and configuration tasks really addresses the needs of such vendors. It also seems that all of the above are achievable within the framework debconf currently provides You've just contradicted yourself. If it's possible to achieve all of the above within the framework debconf currently provides, then a strict split between installation (preinst, unpack and postinst) and configuratin (config and templates) really addresses the needs of such vendors. If, on the other hand, it doesn't, then it's not. Cheers, aj -- Anthony Towns [EMAIL PROTECTED] http://azure.humbug.org.au/~aj/ I don't speak for anyone save myself. GPG signed mail preferred. ``Is this some kind of psych test? Am I getting paid for this?'' pgpF56X8iIXPj.pgp Description: PGP signature
Re: Debconf or not debconf : Conclusion
On Sun, Jul 06, 2003 at 03:24:57PM +1000, Anthony Towns wrote: On Sat, Jul 05, 2003 at 02:28:33PM -0500, Steve Langasek wrote: Yet another reasons for wanting to decouple installation and configuration is if some hardware company (such as VA^H^H Emperor Linux) wishes to ship Debian pre-installed on the system. In that case, installation happens at the factory, and not when the user receives it in his/her hot little hands. Given the number of config questions today that have to do with available hardware, I have a hard time believing that a strict split between installation and configuration tasks really addresses the needs of such vendors. It also seems that all of the above are achievable within the framework debconf currently provides You've just contradicted yourself. If it's possible to achieve all of the above within the framework debconf currently provides, then a strict split between installation (preinst, unpack and postinst) and configuratin (config and templates) really addresses the needs of such vendors. If, on the other hand, it doesn't, then it's not. Sorry, all of the above was meant to refer to the three different modes of invoking the dpkg-configure command. I believe it's possible to provide such a split today using debconf, but I don't believe this split addresses the needs of vendors trying to provide pre-installed systems. -- Steve Langasek postmodern programmer pgp6ByR9Pyttt.pgp Description: PGP signature
VIRUS EN SU CORREO
A L E R T V I R U S Nuestro antivirus ha encontrado W32/Sobig.E virus(es) en su correo dirigido a los siguientes destinatario(s): - [EMAIL PROTECTED] La entrega del mensaje ha sido detenida! Por favor, compruebe la presencia de virus en sus sistema o pida a su administrador que lo haga. Para su referencia estas son las cabeceras de su mensaje: - BEGIN HEADERS - Received: from MAT (185.Red-80-37-98.pooles.rima-tde.net [80.37.98.185]) by artemisa.servinetred.com (Postfix) with ESMTP id AB9E252143 for [EMAIL PROTECTED]; Sun, 6 Jul 2003 07:21:55 +0200 (CEST) From: debian-devel@lists.debian.org To: [EMAIL PROTECTED] Subject: Re: Movie Date: Sun, 6 Jul 2003 7:22:34 +0200 Importance: Normal X-Mailer: Microsoft Outlook Express 6.00.2600. X-MSMail-Priority: Normal X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=CSmtpMsgPart123X456_000_01C78799 Message-Id: [EMAIL PROTECTED] -- END HEADERS --
Re: Juridical prosecution
On Sat, 05 Jul 2003 17:57:07 +0200, Martin Sobek wrote: You place your page on address www.sobek-sobek.com unlawfully! Remove it immediately or you risk juridical prosecution. And the cluelessness Oscar this year goes too... Mr Sobek! -- _ / \ Leandro Guimares Faria Corsetti Dutra +41 (21) 648 11 34 \ / http://br.geocities.com./lgcdutra/ +41 (78) 778 11 34 / \ Answer to the list, not to me directly!+55 (11) 5686 2219 Rate this post if helpful: http://svcs.affero.net/rm.php?r=leandro
Re: eicar.com installer in Debian, and pre-upload interface to ftpmaster
* Thomas Viehmann ([EMAIL PROTECTED]) [030705 23:50]: So why is the recommendation against skipping the ITP to aviod problems in ftpmaster review not right? A (strong) recommendation for doing ITPs right is right and usefull. But - all foreseeable problems should be handeled at ITP-time, and that's not the case. So the recommendation is right, but it doesn't solve the problem Marc spoke of. Cheers, Andi -- http://home.arcor.de/andreas-barth/ PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C
Re: eicar.com installer in Debian, and pre-upload interface to ftpmaster
Andreas Barth wrote: * Thomas Viehmann ([EMAIL PROTECTED]) [030705 23:50]: So why is the recommendation against skipping the ITP to aviod problems in ftpmaster review not right? A (strong) recommendation for doing ITPs right is right and usefull. But - all foreseeable problems should be handeled at ITP-time, and that's not the case. So the recommendation is right, but it doesn't solve the problem Marc spoke of. I doubt that an eicar-installer ITP would have survived the scrutiny of devel. So it may not solve the general problem Marc about but it solves a very good share of it, most likely *including* the very specific instance he had problems with. If you can't come up with a case where the ITP review was positive and ftpmaster rejected the package in itself with a unforseeable reason (regarding a problem that cannot be fixed), I fail to see any merit in your argument. There's no point in establishing VIP review for people who are think they are too important for undergoing peer review. *Look* at #198311 and search for debian-devel and then ask yourself why Marc thinks that -devel should only be used as a forum to discredit ftpmasters work, and not as a place where ITPs should be reviewed. Cheers T. pgp0n7r2FptNY.pgp Description: PGP signature
Re: Resolvconf -- a package to manage /etc/resolv.conf
On Sat, 2003-07-05 at 22:40, Simon Hürlimann wrote: I'd prefer update-resolv like update-alternatives update-initrd update-catalog update-ispell-dictionary update-default-aspell update-menus update-default-ispell update-mime to name just a few. Resolvconf isn't really comparable to the update-* utilities. Unlike them, resolvconf takes information on its standard input. And unlike them, it run during normal use of the machine, not at administration time. The update-* programs usually modify files in /etc/, whereas one of the reasons for creating resolvconf is to avoid modifying files in /etc/. -- Thomas Hood
Re: Resolvconf -- a package to manage /etc/resolv.conf
On Sun, 2003-07-06 at 01:00, Goswin Brederlow wrote: You should think of a mechanism for daemons to get notified about changes in resolv.conf. There is already such a mechanism. See below. Like providing a function to register a script and a list of arguments (like the PID of the program to notify). Whenever the resolv.conf changes all currently registered scripts would be called with their respective arguments. The simplest form would be: resolv.conf-register /etc/init.d/squid reload That would make squid to reload its config each time a nameserver is added or removed. Currently, scripts in /etc/resolvconf/update.d/ get run when resolver information changes. So, would it suffice to create /etc/resolvconf/update.d/squid containing the following? #!/bin/sh /etc/init.d/squid reload -- Thomas Hood
Re: Resolvconf -- a package to manage /etc/resolv.conf
On Sun, 2003-07-06 at 01:32, Marco d'Itri wrote: On Jul 05, Thomas Hood [EMAIL PROTECTED] wrote: * Before entering the Debian archive it would be nice if resolvconf were supported by all packages that currently futz with /etc/resolv.conf, including pump and bind. If you mean that if should be mandatory to install this package on every name server, then it would not be nice at all. No, I meant that before entering the Debian archive it would be nice if resolvconf were supported by all packages that currently futz with /etc/resolv.conf, including pump and bind. -- Thomas Hood
Re: Please remove RFCs from the documentation in Debian packages
On Fri, Jul 04, 2003 at 07:30:56PM +0100, Andrew Suffield wrote: On Fri, Jul 04, 2003 at 07:47:32PM +0200, Thomas Viehmann wrote: Andrew Suffield wrote: people to http://www.debian.org/doc/manuals/ddp-policy/ch-common.en.html. This claims the GNU FDL is acceptable, so it's worse than useless. It claims that GNU FDL sans cover texts and invariant sections is acceptable. Which is grossly out of date (read: wrong). This has been discussed to death on -legal. Could you please point to the discussion you mention that makes that content out of date? I thought I pretty much cover all the -legal discussions to date at http://www.debian.org/doc/manuals/ddp-policy/footnotes.en.html#f3. But maybe the status from december to current date has changed. Branden said back then: The GNU FDL, version 1.2, is not necessarily DFSG-non-free when applied to a work, but it can be employed in ways that are DFSG-non-free. (http://lists.debian.org/debian-legal/2002/debian-legal-200211/msg00285.html) However, you (as well as any other DD), of course, know you have CVS r/w access to the DDP Policy document to update it as needed. Don't you? That would be _much_ more useful than saying so it's worse than useless, mind you. It's hard to make a proper document regarding documentation licensing if a) debian-legal consensus switches mindset every other day b) people at debian-legal do not keep people at debian-doc up-to-date to latest consensus wrt to documentation licensing (yes, until somebody who is at -doc says please RTFM and somebody at -legal says TFM is worthless) Regards Javi PS: Notice that, as far as I see, Aj's post on debian-legal (is that the current consensus?) implies that GFDL documents _can_ be DFSG-free http://lists.debian.org/debian-legal/2003/debian-legal-200304/msg00246.html pgpEdfyVYzwme.pgp Description: PGP signature
Re: A success story with apt and rsync
On Sun, 2003-07-06 at 09:27, Goswin Brederlow wrote: 4. (and this is the knockout) rsync support for apt-get is NO WANTED. rsync uses too much resources (cpu and more relevant IO) on the server side and a widespread use of rsync for apt-get would choke the rsync mirrors and do more harm than good. One way to alleviate this would be to only generate the deltas once on server-side when first requested, then cache them on disk to be served out like any other static file for reconstruction of the new package on the client-side using rsync. I've been thinking for a while about trying to build this into Apt-cacher. Jonathan
Re: Resolvconf -- a package to manage /etc/resolv.conf
#include hallo.h * Thomas Hood [Sat, Jul 05 2003, 09:51:56PM]: Summary ~~~ Resolvconf is a proposed standard framework for updating the system's information about currently available nameservers. Most importantly, it manages /etc/resolv.conf , but it does a bit more than that. The Idea is great, it would solve the long outstanding dispute between me (pppoeconf) and pppconfig maintainer. Please, would you consider to add another feature: priorising some entries depending on the source. That means: pppoeconf's and pppconfig's script run the tool with parameter --class dialup, dhcp clients with --class dynamic and the default class would be static. In some config file, the user defines that dialup gets priority one, dynamic two and static three (for example), and resolvconf merges the existing dns entries in the appropriate order. Please also note that it would (IMHO) be a good idea to manage the search list with a similar priority table, so the provider's domain is appended or prepended (as user wishes it). MfG, Eduard. -- housetier isga: versuch mal 'apt-cache search girl friend' :-) du wirst überrascht sein
Re: Resolvconf -- a package to manage /etc/resolv.conf
On Sun, 2003-07-06 at 12:13, Thomas Hood wrote: No, I meant that before entering the Debian archive it would be nice if resolvconf were supported by all packages that currently futz with /etc/resolv.conf, including pump and bind. Which other packages? I guess I need to explain more clearly. First. Currently, making certain packages work with resolvconf requires some manual changes to configuration files. The changes are not large: just adding a couple of lines to initscripts and such. Still, I think it would be nice if such packages worked with resolvconf -- if resolvconf happens to be installed -- without requiring any manual changes. I won't explain here how this can be done; please see the announcement and bug reports #194204 and #199255 for details. At the moment, the only packages I know of that need some adaptation are pump and bind. There are probably others. Someone has mentioned squid, so I will investigate squid later today, but at first glance it looks as if no changes to squid will be required. Second, resolvconf's usefulness in allowing the relocation of variable files out of /etc/ will be greatest if packages that currently write resolver information into files in /etc/ , such as pump, are changed so that when resolvconf is installed they send that information to resolvconf instead. Again, please see #194204. My aim is not to make resolvconf mandatory; it is to have packages work properly with resolvconf *if* resolvconf is installed. When resolvconf is not installed, other packages should continue to do what they did before. -- Thomas Hood
Re: Resolvconf -- a package to manage /etc/resolv.conf
On Sun, 2003-07-06 at 12:42, Eduard Bloch wrote: Please, would you consider to add another feature: priorising some entries depending on the source. That means: pppoeconf's and pppconfig's script run the tool with parameter --class dialup, dhcp clients with --class dynamic and the default class would be static. In some config file, the user defines that dialup gets priority one, dynamic two and static three (for example), and resolvconf merges the existing dns entries in the appropriate order. Let me start by saying that resolv.conf is generated by /etc/resolvconf/update.d/libc , which, being a conffile, can be customized by the admin. Your idea strikes me as a good one. It would add some complexity to the system, but it would provide more information for /etc/resolvconf/update.d/libc to use when it generates the resolv.conf file. Currently the script discriminates only on the basis of interface type (i.e., lo, ppp or eth). However, I would only want to add this feature if we were certain that it was needed. -- Thomas Hood
Re: eicar.com installer in Debian, and pre-upload interface to ftpmaster
On Sun, 06 Jul 2003 11:03:37 +0200, Thomas Viehmann [EMAIL PROTECTED] wrote: *Look* at #198311 and search for debian-devel and then ask yourself why Marc thinks that -devel should only be used as a forum to discredit ftpmasters work, and not as a place where ITPs should be reviewed. That was indeed an omission, caused by the fact that I filed an RFP first and later retitled the bug to ITP. Surely you never make any mistakes. Greetings Marc -- -- !! No courtesy copies, please !! - Marc Haber |Questions are the | Mailadresse im Header Karlsruhe, Germany | Beginning of Wisdom | Fon: *49 721 966 32 15 Nordisch by Nature | Lt. Worf, TNG Rightful Heir | Fax: *49 721 966 31 29
Re: eicar.com installer in Debian, and pre-upload interface to ftpmaster
Marc Haber wrote: On Sun, 06 Jul 2003 11:03:37 +0200, Thomas Viehmann [EMAIL PROTECTED] wrote: *Look* at #198311 and search for debian-devel and then ask yourself why Marc thinks that -devel should only be used as a forum to discredit ftpmasters work, and not as a place where ITPs should be reviewed. That was indeed an omission, caused by the fact that I filed an RFP first and later retitled the bug to ITP. Surely you never make any mistakes. I make a lot of mistakes. (That's why I prefer working on computers/math over things like medicine.) In fact, I made a similar mistake with the ITP of libchipcard (IIRC) because the X-Debbugs-CC got lost because I usually call reportbug -p and copy stuff into my mailclient when reporting bugs. (And it might be a reasonable idea to investigate posting ITPs on debian-devel by other means than the X-Debbug-CC-Header so such obmissions are impossible). However, I sincerely believe that without this obmission, the ITP might have been shot down (or held reasonable) before the upload (and possibly before the creation) of the package. Thus (leaving the style issue that upset you aside) I think that the (technical) merit of your complaint is somewhat limited. As far as the eicar license is concerned: Is it really that difficult to obtain a statement from eicar on whether or not they believe that the test file is copyrightable and maybe a general permission to distribute the file? From your comment I guess you tried, but quite possibly they understand better Debian's concern about licensing with all the publicity the SCO lawsuit has. That said, I see additional issues with the inclusion of the eicar file (aside from the obvious point that probably it'd rest just as well in another package containing a virus scanner): Debian mirrors and CDs will be quite possibly be identified as carrying virii. Quite possibly, it's reasonable to obfuscate (in a documented way) the file (e.g. xor it and provide a program for decryption) or include a script or download instructions rather than the file itself. Possibly, even the original installer package looks a lot less silly on second thought. Cheers T. pgpIIa5GHxRAZ.pgp Description: PGP signature
Re: A success story with apt and rsync
On Sun, Jul 06, 2003 at 12:37:00PM +1200, Corrin Lakeland wrote: 4. (and this is the knockout) rsync support for apt-get is NO WANTED. rsync uses too much resources (cpu and more relevant IO) on the server side and a widespread use of rsync for apt-get would choke the rsync mirrors and do more harm than good. When I was looking into this I heard about some work into caching the rolling checksums to eliminate server load. I didn't find any code. That would be because the checksums would take at least 8 times the space of the original files. You need the backward-rsync which was patented last I heard. -- Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/ the West won the world not by the superiority of its ideas or values or religion but rather by its superiority in applying organized violence. Westerners often forget this fact, non-Westerners never do. - Samuel P. Huntington pgpMZ4tlXA1It.pgp Description: PGP signature
Re: Resolvconf -- a package to manage /etc/resolv.conf
On Sun, 2003-07-06 at 01:52, Nick Phillips wrote: Actually I think the simplest form would be to have /etc/resolvconf/notify.d and run all scripts in there at the relevant times, with any necessary arguments (which would be standard). Please take a look at how resolvconf runs the scripts in /etc/resolvconf/update.d/ and let me know if you think anything else is needed. Alioth was down for a while but I just checked and the deb is once again available (in the resolvconf section of the update-resolv project). http://alioth.debian.org/project/showfiles.php?group_id=1227 -- Thomas
Re: eicar.com installer in Debian, and pre-upload interface to ftpmaster
On Sun, 06 Jul 2003 15:00:18 +0200, Thomas Viehmann [EMAIL PROTECTED] wrote: As far as the eicar license is concerned: Is it really that difficult to obtain a statement from eicar on whether or not they believe that the test file is copyrightable and maybe a general permission to distribute the file? From your comment I guess you tried, Actually, I tried three times. Once via the official contacts listed on the eicar web page, and once via the domain contacts for eicar.com. In both cases, my e-mail was completely ignored. Greetings Marc -- -- !! No courtesy copies, please !! - Marc Haber |Questions are the | Mailadresse im Header Karlsruhe, Germany | Beginning of Wisdom | Fon: *49 721 966 32 15 Nordisch by Nature | Lt. Worf, TNG Rightful Heir | Fax: *49 721 966 31 29
Re: Bug#200153: ITP: e2tools -- utilities for manipulating files in an ext2/ext3 filesystem
On Sat, Jul 05, 2003 at 11:35:29PM +0200, Ralf Treinen wrote: On Sat, Jul 05, 2003 at 05:24:21PM +0200, Robert Millan wrote: E2tools is a simple set of GPL'ed utilities to read, write, and manipulate files in an ext2/ext3 filesystem. please excuse my ignorance - what would be the advantage of these tools over the core file utilities which use the VFS layer? The problem is that for monolithic kernels the filesystem code lies in kernelspace, hence for security reasons filesystems can only be attached (via mount) by root. (This isn't applicable to the GNU system, though, since Hurd's ext2fs is implemented as a userspace server that normal users can run) With this utils, normal users still can't use standard filesystem C library calls over their custom ext2fs image, but may use commands like e2cp or e2mkdir for basic manipulation. Btw, I need this to integrate grub-disk into the grub package (see #190392). -- Robert Millan
Re: NEWS.Debian support is here
On Fri, 2003-07-04 at 06:01, Joey Hess wrote: The file format is the same as a debian changelog file, but we leave off the asterisks generally, and use bigger paragraphs explaining news items when necessary. It might be a good idea to run your file through dpkg-parsechangelog to check its formatting as it will not be automatically checked during build as the changelog is. I expect there will be a lintian check eventually. Here's a real life example of a NEWS.Debian file: libinline-perl (0.43-5) unstable; urgency=low Is there any particular reason to keep the unstable; urgency=low there? It's duplication of information in the changelog, and nearly every developer will probably forget to change the information in NEWS.Debian when they change the urgency or distribution in changelog. Would this work just as well? libinline-perl (0.43-5) Note that when you upgrade from perl 5.6 to 5.8, binaries built with libinline (this may include compiled objects cached in .Inline/_Inline directories) will fail to work with the new version of perl. This is because perl's ABI for binaries changed between perl 5.6 and 5.8. The solution is the delete and regenerate any such binaries you might have. I have not tried to automate this in the Debian package. -- Joey Hess [EMAIL PROTECTED] Wed, 11 Sep 2002 21:37:56 -0400 ? Scott -- Who would forget every time :-) signature.asc Description: This is a digitally signed message part
Re: Please remove RFCs from the documentation in Debian packages
On Sun, Jul 06, 2003 at 12:23:16PM +0200, Javier Fernández-Sanguino Peña wrote: Could you please point to the discussion you mention that makes that content out of date? I thought I pretty much cover all the -legal discussions to date at http://www.debian.org/doc/manuals/ddp-policy/footnotes.en.html#f3. But maybe the status from december to current date has changed. Branden said back then: The GNU FDL, version 1.2, is not necessarily DFSG-non-free when applied to a work, but it can be employed in ways that are DFSG-non-free. (http://lists.debian.org/debian-legal/2002/debian-legal-200211/msg00285.html) I've changed my mind about that, thanks in no small measure to the observations of a lot of other people. However, you (as well as any other DD), of course, know you have CVS r/w access to the DDP Policy document to update it as needed. Don't you? That would be _much_ more useful than saying so it's worse than useless, mind you. It's hard to make a proper document regarding documentation licensing if a) debian-legal consensus switches mindset every other day We don't change mindset every other day. We've changed it after six months. b) people at debian-legal do not keep people at debian-doc up-to-date to latest consensus wrt to documentation licensing (yes, until somebody who is at -doc says please RTFM and somebody at -legal says TFM is worthless) Perhaps debian-legal needs its own document, to which the DDP document can merely refer. PS: Notice that, as far as I see, Aj's post on debian-legal (is that the current consensus?) implies that GFDL documents _can_ be DFSG-free http://lists.debian.org/debian-legal/2003/debian-legal-200304/msg00246.html That summary is correct as far as it goes, but it does not enumerate all of the problems that have been found with the GNU FDL. If and only if: 1) there are no Invariant Sections 2) there are no Cover Texts 3) there are no Acknowledgements 4) there are no Dedications 5) the restrictions on copying in quantity are waived ...and that's not even a complete list. -- G. Branden Robinson|I must confess to being surprised Debian GNU/Linux |by the magnitude of incompatibility [EMAIL PROTECTED] |with such a minor version bump. http://people.debian.org/~branden/ |-- Manoj Srivastava pgpP4aqnYcyDI.pgp Description: PGP signature
Re: Debconf and XFree86 X servers
On Sun, Jul 06, 2003 at 01:09:21AM +0200, Goswin Brederlow wrote: Branden Robinson [EMAIL PROTECTED] writes: [Please direct any XFree86-specific followup to debian-x.] On Sat, Jul 05, 2003 at 08:46:00AM -0400, Theodore Ts'o wrote: Yet another reasons for wanting to decouple installation and configuration is if some hardware company (such as VA^H^H Emperor Linux) wishes to ship Debian pre-installed on the system. In that case, installation happens at the factory, and not when the user receives it in his/her hot little hands. So they should just provide a setup.sh script that calls dpkg-reconfigure for relevant packages again. Otherwise just type in dpkg-reconfigure --all and spend hours configuring your system as much as you like. 1) Why did you follow-up to a message of mine, but not include *any* of my quoted text? 2) Why did you follow-up with a non-XFree86-specific message to debian-x? Please be more judicious in your use of your MUA. -- G. Branden Robinson| I suspect Linus wrote that in a Debian GNU/Linux | complicated way only to be able to [EMAIL PROTECTED] | have that comment in there. http://people.debian.org/~branden/ | -- Lars Wirzenius pgpOavO8WHD4D.pgp Description: PGP signature
Re: Juridical prosecution
On Sat, Jul 05, 2003 at 09:52:06PM +0200, Leandro Guimarães Faria Corsetti Dutra wrote: On Sat, 05 Jul 2003 17:57:07 +0200, Martin Sobek wrote: You place your page on address www.sobek-sobek.com unlawfully! Remove it immediately or you risk juridical prosecution. And the cluelessness Oscar this year goes too... Mr Sobek! But the competition is always so fierce, and the year isn't over yet... -- G. Branden Robinson| It just seems to me that you are Debian GNU/Linux | willfully entering an arse-kicking [EMAIL PROTECTED] | contest with a monstrous entity http://people.debian.org/~branden/ | that has sixteen legs and no arse. pgpBryv81Muln.pgp Description: PGP signature
Re: eicar.com installer in Debian, and pre-upload interface to ftpmaster
Marc Haber wrote: On Sun, 06 Jul 2003 15:00:18 +0200, Thomas Viehmann [EMAIL PROTECTED] wrote: As far as the eicar license is concerned: Is it really that difficult to obtain a statement from eicar on whether or not they believe that the test file is copyrightable and maybe a general permission to distribute the file? From your comment I guess you tried, Actually, I tried three times. Once via the official contacts listed on the eicar web page, and once via the domain contacts for eicar.com. In both cases, my e-mail was completely ignored. How about phoning them? [0] There's a German phone number for the executive secretary. If nothing else, he might be able to point you in the correct directions. You could also try phoning Urs Gattiker... (I've had bad experiences with phoning via 01024 to Denmark though.) Cheers T. 0. http://www.eicar.org/inside.htm#office pgpKpZ7BkTdTV.pgp Description: PGP signature
Re: Juridical prosecution
Leandro Guimares Faria Corsetti Dutra wrote: On Sat, 05 Jul 2003 17:57:07 +0200, Martin Sobek wrote: You place your page on address www.sobek-sobek.com unlawfully! Remove it immediately or you risk juridical prosecution. And the cluelessness Oscar this year goes too... Mr Sobek! Oh, that's why sun always has this indemnification thing in their licenses. Maybe Debian should... Cheers T. pgpyyKTs2ZUYq.pgp Description: PGP signature
Re: NEWS.Debian support is here
On Sun, Jul 06, 2003 at 07:13:23PM +0100, Scott James Remnant wrote: On Fri, 2003-07-04 at 06:01, Joey Hess wrote: The file format is the same as a debian changelog file, but we leave off the asterisks generally, and use bigger paragraphs explaining news items when necessary. It might be a good idea to run your file through dpkg-parsechangelog to check its formatting as it will not be automatically checked during build as the changelog is. I expect there will be a lintian check eventually. Here's a real life example of a NEWS.Debian file: libinline-perl (0.43-5) unstable; urgency=low Is there any particular reason to keep the unstable; urgency=low there? It's duplication of information in the changelog, and nearly every developer will probably forget to change the information in NEWS.Debian when they change the urgency or distribution in changelog. Would this work just as well? [example without distribution and urgency] It would work just as well. The changelog format was used unmodified for purposes of simplicity. Tools already know how to parse it, and its format is already reasonably specified in the documentation. Scott -- Who would forget every time :-) You don't type changelog headers by hand, do you? -- - mdz
Re: A success story with apt and rsync
On Sun, 6 Jul 2003, Andrew Suffield wrote: It should put them in the package in the order they came from readdir(), which will depend on the filesystem. This is normally the order in which they were created, and should not vary when rebuilding. As such, sorting the list probably doesn't change the network traffic, but will slow dpkg-deb down on packages with large directories in them. Yes, when saying random order I obviously ment in the order readdir() returns them. It's random for me. :-))) It can easily be different on different filesystems, or even on same type of filesystems with different parameters (e.g. blocksize). I even think it can be different after a simple rebuild on exactly the same environment. For example configure and libtool like to create files with the PID in their name, which can take from 3 to 5 digits. If you create the file X and then Y, remove X and then create Z then it is most likely that if Z's name is shorter than or equal to the length of filename X, then it will be returned first by readdir(), while if its name is longer, then Y will be returned first and Z afterwards. So I can imagine situations where the order of the files depend on the PIDs of the build processes. However, I guess or goal is not only to produce similar packages from exactly the same source. It's quite important to produce similar package even after a version upgrade. For example you have a foobar-0.9 package, and now upgrade to foobar-1.0. The author may have completely rewritten Makefile which yields in nearly the same executable, the same data files, but completely different random order. However, I think sorting the files costs really nothing. My system is not a very new one, 375MHz Celeron, IDE disks, 384MB RAM etc... However: /usr/lib$ du -s . 1,1G. /usr/lib$ find . -type f | wc -l # okay, it's now in memory cache 18598 /usr/lib$ time find . /dev/null 21 real0m0.285s user0m0.100s sys 0m0.150s [EMAIL PROTECTED]:/usr/lib$ time sortdir find . /dev/null 21 real0m1.683s user0m1.390s sys 0m0.250s IMHO a step which takes one and a half seconds before compressing 18000 files of more than 1 gigabytes shouldn't be a problem. cheers, Egmont
Re: NEWS.Debian support is here
On Sun, Jul 06, 2003 at 04:31:22PM -0400, Matt Zimmerman wrote: On Sun, Jul 06, 2003 at 07:13:23PM +0100, Scott James Remnant wrote: Would this work just as well? [example without distribution and urgency] It would work just as well. The changelog format was used unmodified for purposes of simplicity. Tools already know how to parse it, and its format is already reasonably specified in the documentation. To clarify, I meant that such a format would meet the need of NEWS.Debian. However, the existing tools would not understand it. I do not see the extra unused information as a problem, and it lets us use existing tools for creating and editing NEWS.Debian (debchange, dpkg-dev-el, etc.) -- - mdz
Re: A success story with apt and rsync
On Sun, Jul 06, 2003 at 10:28:07PM +0200, Koblinger Egmont wrote: On Sun, 6 Jul 2003, Andrew Suffield wrote: It should put them in the package in the order they came from readdir(), which will depend on the filesystem. This is normally the order in which they were created, and should not vary when rebuilding. As such, sorting the list probably doesn't change the network traffic, but will slow dpkg-deb down on packages with large directories in them. Yes, when saying random order I obviously ment in the order readdir() returns them. It's random for me. :-))) It can easily be different on different filesystems, or even on same type of filesystems with different parameters (e.g. blocksize). I can't think of any reason why changing the blocksize would affect this. Most filesystems return files in the sequence in which they were added to the directory. ext2, ext3, and reiser all do this; xfs is the only one likely to be used on a Debian system which doesn't. I even think it can be different after a simple rebuild on exactly the same environment. For example configure and libtool like to create files with the PID in their name, which can take from 3 to 5 digits. If you create the file X and then Y, remove X and then create Z then it is most likely that if Z's name is shorter than or equal to the length of filename X, then it will be returned first by readdir(), while if its name is longer, then Y will be returned first and Z afterwards. So I can imagine situations where the order of the files depend on the PIDs of the build processes. This lengthly bit of handwaving has no connection with reality. However, I think sorting the files costs really nothing. My system is not a very new one, 375MHz Celeron, IDE disks, 384MB RAM etc... However: /usr/lib$ du -s . 1,1G. /usr/lib$ find . -type f | wc -l # okay, it's now in memory cache 18598 /usr/lib$ time find . /dev/null 21 real0m0.285s user0m0.100s sys 0m0.150s [EMAIL PROTECTED]:/usr/lib$ time sortdir find . /dev/null 21 real0m1.683s user0m1.390s sys 0m0.250s IMHO a step which takes one and a half seconds before compressing 18000 files of more than 1 gigabytes shouldn't be a problem. This test only shows that you don't understand what is going on; it has no relation to the problems that can occur. On ext2, as an example, stat()ting or open()ing a directory of 1 files in the order returned by readdir() will be vastly quicker than in some other sequence (like, say, bytewise lexicographic) due to the way in which the filesystem looks up inodes. This has caused significant performance issues for bugs.debian.org in the past. -- .''`. ** Debian GNU/Linux ** | Andrew Suffield : :' : http://www.debian.org/ | Dept. of Computing, `. `' | Imperial College, `- -- | London, UK pgp5SqrSYg0gQ.pgp Description: PGP signature
Re: NEWS.Debian support is here
On Sun Jul 06, 04:58pm -0400, Matt Zimmerman wrote: On Sun, Jul 06, 2003 at 04:31:22PM -0400, Matt Zimmerman wrote: On Sun, Jul 06, 2003 at 07:13:23PM +0100, Scott James Remnant wrote: Would this work just as well? [example without distribution and urgency] It would work just as well. The changelog format was used unmodified for purposes of simplicity. Tools already know how to parse it, and its format is already reasonably specified in the documentation. To clarify, I meant that such a format would meet the need of NEWS.Debian. However, the existing tools would not understand it. I do not see the extra unused information as a problem, and it lets us use existing tools for creating and editing NEWS.Debian (debchange, dpkg-dev-el, etc.) If you can make apt-listchanges understand the pared-down format, perhaps the others will support it eventually too. I don't care a whole lot about it myself, but it *does* look a lot nicer :)
Re: Bug#200153: ITP: e2tools -- utilities for manipulating files in an ext2/ext3 filesystem
On Sat, Jul 05, 2003 at 11:57:35PM +0200, Falk Hueffner wrote: Ralf Treinen [EMAIL PROTECTED] writes: E2tools is a simple set of GPL'ed utilities to read, write, and manipulate files in an ext2/ext3 filesystem. please excuse my ignorance - what would be the advantage of these tools over the core file utilities which use the VFS layer? You don't need root. Useful for example to build rescue floppy images. Actually, you can do this with debugfs. That's how Real Men (tm) build their initial bootstrap images. (i.e., Linus Torvalds, when he was first bootstrapping the Alpha port.) That being said, the e2tools does have an easier to use user interface than debugfs, and reduces the chance that user will harm himself; sort of like the difference between using an Exacto knife and one of those scissors with rounded ends that gets handed out to pre-schoolers. :-) That's not a bad thing, and certainly I'm not saying it shouldn't be packaged. In fact, I think it's a good thing, just as like the mtools suite is useful even though we have the msdos filesystem in the kernel. However, I've taken a quick look at it, and I do have some warnings: *) It looks like upstream hasn't released a new version since July or August 2002. Before that, releases were happening regularly. Is the author Keith Sheffield (cc'ed on this note), still maintaining the package? *) It badly needs to be autoconfiscated. *) Currently it hardcodes the path to static libraries in ../e2fsprogs-1.27/lib/...; it should use the shared version of the libraries. *) It's missing man pages *) It needs testing against a variety of newer versions of ext2fs to make sure the code actually works well with filesystems with htree filesystems and extended attributes. Upon brief inspection, I can see that it's not dropping the refcount on the extended attribute block when deleting a file, and freeing the extended attribute block when the refcount goes to zero. This is no shame; it merely shows the age of the code, and to be honest, the rm function in debugfs doesn't do this correctly either --- I'll put that on my to fix list. However, there is the implicit promise thatuserland packages such as e2tools will work correctly, whereas debugfs sets a much lower level of expectations, since it's assumed to be a wizard-level tool, with sharp pointy edges upon which naive users can hurt themselves if they are not careful. What it *does* show is that e2tools badly needs a test suite, which takes a bunch of filesystems, does various e2tools operations on it, and then runs e2fsck on the filesystem to make sure the resulting filesystem is still valid. I have not run any tests on it, so I can't be sure the extended attribute block handling is the only issue. I *think* it should be just fine with htree directories, since the libext2fs library handles a lot of the issues automatically. But until you run tests --- preferably automated test suites --- you can never be sure. The bottom-line is that e2tools shows a lot of promise, but there's also a lot of work that could be put into it in order to improve its quality. Perhaps upstream could be convinced to tackle some of the work, or at the very least, accept patches that you feed back to him. - Ted
Re: A success story with apt and rsync
Hi, On 6 Jul 2003, Goswin Brederlow wrote: 2. most of the time you have no old file to rsync against. Only mirrors will have an old file and they already use rsync. This is definitely true if you install your system from CD's and then upgrade it. However, if you keep on upgrading from testing/unstable then you'll have more and more packages under /var/cache/apt/archives so it will have more and more chance that an older version is found there. Or, alternatively, if you are sitting behind a slow modem and apt-get upgrade says it will upgrade extremely-huge-package, then you can still easily insert your CD and copy the old version of extremely-huge-package to /var/cache/apt/archives and hit ENTER to apt-get afterwards. 3. rsyncing against the previous version is only possible via some dirty hack as apt module. apt would have to be changed to provide modules access to its cache structure or at least pass any previous version as argument. Some mirror scripts alreday use older versions as templaes for new versions. Yes, this is what I've hacked together based on other people's great work. It is (as I've said too) a dirty hack. If a more experienced apt-coder can replace my hard-coded path with a mechanism that tells this path to the module, then this hack won't even be dirty. 4. (and this is the knockout) rsync support for apt-get is NO WANTED. rsync uses too much resources (cpu and more relevant IO) on the server side and a widespread use of rsync for apt-get would choke the rsync mirrors and do more harm than good. It might be no wanted for administrators, however, I guess it is wanted to many of the users (at least for me :-)) I don't see the huge load of the server (since I'm the only one rsyncing from it), but I see the huge difference in the download time. If my download wasn't faster because of an overloaded server, I would switch back to FTP or anything which is better to me as an end user. I understand that rsync causes a high load on the server when several users are connected, and so it is not suitable as a general replacement for ftp, however I think it is suitable as an alternative. I also don't expect the Debian team itself to set up a public rsync server for the packages. However, some mirrors might want to set up an rsync server either for the public or for example a university for its students. Similar hack could be simply used by people who have account to a machine with high bandwidth. For example if I used Debian and Debian had rsyncable packages, but no public rsync server was available, I'd personally mirror Debian to a machine at the university using FTP and would use rsync from that server to my home machine to save traffic where the bandwidth is a bottleneck. So I don't think it's a bad idea to set up some public rsync servers worldwide. The maximum number of connections can be set up so that cpu usage is limited somehow. It's obvious that if a user often gets the connection refused then he will switch back to ftp or http. Hence I guess that the power of the public rsync servers and the users using rsync would somehow be automatically balanced, it doesn't have to be coordinated centrally. So IMHO let anybody set up an rsync server if he wants to, and let the users use rsync if they want to (but don't put an rsync:// line in the default sources.list). All together I think a extended bittorrent module for apt-get is by far the better sollution but it will take some more time and designing before it can be implemented. It is very promising and I really hope that it will be a good protocol with a good implementation and integration to apt. But until this is realized, we still could have rsync as an alternative, if Debian packages were packed in a slightly different way. bye, Egmont
Re: A success story with apt and rsync
On Sun, Jul 06, 2003 at 10:12:03PM +0100, Andrew Suffield wrote: On Sun, Jul 06, 2003 at 10:28:07PM +0200, Koblinger Egmont wrote: Yes, when saying random order I obviously ment in the order readdir() returns them. It's random for me. :-))) It can easily be different on different filesystems, or even on same type of filesystems with different parameters (e.g. blocksize). I can't think of any reason why changing the blocksize would affect this. Most filesystems return files in the sequence in which they were added to the directory. ext2, ext3, and reiser all do this; xfs is the only one likely to be used on a Debian system which doesn't. Err, no. If the htree (hash tree) indexing feature is turned on for ext2 or ext3 filesystems, they will returned sorted by the hash of the filename --- effectively a random order. (Since the hash also includes a secret, random, per-filesystem secret in order to avoid denial of service attacks by malicious users who might otherwise try to create huge numbers of files containing hash collisions.) I would be very, very surprised if reiserfs returned files in creation order. The fundamental problem is that the readdir()/telldir()/seekdir() API is fundamentally busted. Yes, Dennis Ritchie and Ken Thompson do make mistakes, and have made many; in this particular case, they made a whopper. Seekdir()/telldir() assumes a linear directory structure which you can seek into, such that the results of readdir() are repeatable. Posix only allows files which are created or deleted in the interval to be undefined; all other files must be returned in the same order as the original readdir() stream, even if days or weeks elapse between the readdir(), telldir(), and seekdir() calls. Any filesystem which tries to use a B-tree like system, where leaf nodes can be split, is going to have extreme problems trying to keep these guarantees. For this reason, most filesystem designers choose to return files in b-tree order, and *not* the order in which files were added to the directory. It is really, really bad assumption to assume that files will be returned in the same order as they were created. On ext2, as an example, stat()ting or open()ing a directory of 1 files in the order returned by readdir() will be vastly quicker than in some other sequence (like, say, bytewise lexicographic) due to the way in which the filesystem looks up inodes. This has caused significant performance issues for bugs.debian.org in the past. If you are using HTREE, and want to do a readdir() scan followed by something which opens or stat's all of the files, you very badly will want to sort the returned directory inodes by the inode number (de-d_inode). Otherwise, the order returned by readdir() will be effectively random, with the resulting loss of performance which you alluded to because the filesystem needs to randomly seek and ready all around the inode table. Why can't this be done in the kernel? Because if the directory is 200 megabytes, then kernel would need to allocate and hold on to 200 megabytes until the userspace called closedir(). There is simply no lightweight way to work around the problems caused by the broken API which Ken Thompson and Dennis Ritchie designed. The good news is that this particular optimization of sorting by inode number should work for all filesystems, and should speed up xfs as well as ext2/3 with HTREE. - Ted
Bug#200268: general: .dpkg-dist and .dpkg-old files in cron.* and modutils dirs
Package: general Version: unavailable; reported 2003-07-06 Severity: normal Hi! Problem: I have a laptop system, I recently upgraded to sarge (from woody) and I noticed the following problem: I moved some script from /etc/cron.daily to /etc/cron.weekly (to save power) But when dpkg asked me whether I want to install the new version of it's config file I answered no. Now a new file package.dpkg-dist appears and if i answered yes the old one will be renamed to package.dpkg-old (This is fine for normal dirs but not for these which are parsed by *simple* scripts) This is not the expected behaviour because now I have scripts which I already removed, and the same applies to /etc/modutils, if a new package makes an upgrade here, there can be duplicated entries in /etc/modules.conf How to solve: If you move a new config file to a new directory it will be harder find those files. So dpkg should explicitly tell the user that this directory must be checked after the upgrade or you should tell that the original/new files will be moved to this and this directory. -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux notebook 2.4.21-rc2-laptopmode2 #2 2003. máj. 23., péntek, 12.20.04 CEST i586 Locale: LANG=hu_HU, LC_CTYPE=hu_HU
Re: Please remove RFCs from the documentation in Debian packages
On Sun, Jul 06, 2003 at 02:07:14PM -0500, Branden Robinson wrote: b) people at debian-legal do not keep people at debian-doc up-to-date to latest consensus wrt to documentation licensing (yes, until somebody who is at -doc says please RTFM and somebody at -legal says TFM is worthless) Perhaps debian-legal needs its own document, to which the DDP document can merely refer. Fine by me. I don't like too much digging into debian-legal :-) It would be very nice to have a document in the DDP detailing which licenses have been analised by the debian-legal mailing list and what the results have been (DFSG-free or otherwise). Regards Javi pgpA02IqnJNSY.pgp Description: PGP signature
Re: A success story with apt and rsync
On Sun, 6 Jul 2003, Andrew Suffield wrote: On ext2, as an example, stat()ting or open()ing a directory of 1 files in the order returned by readdir() will be vastly quicker than in some other sequence (like, say, bytewise lexicographic) due to the way in which the filesystem looks up inodes. This has caused significant performance issues for bugs.debian.org in the past. You're right, I didn't get the point in the story when I simply ran find using the sortdir wrapper, but now I understand the problem. However I'm still unsure if this good to keep files unsorted, especially if we consider effective syncing of packages. On my home computer I've never heard the sound of my disk at package creating phase (even though we've beein using sortdir for more than a half year, and I've compiled hundreds of packages), but I hear it when e.g. the source is decompressed. At the 'dpkg-deb --build' phase only the processor is the bottleneck. This might vary under different circumstances. I'm unaware of them in case of Debian, e.g. I have no information about what hardware your packages are created on, whether there are any other cpu-intensive or disk-intensive applications running on these machines etc. I can easily imagine that using sortdir can drastically decrease performance if another disk-intensive process is running. However my experiences didn't show a noticeable performance decrease if this was the only process accessing the disk... But hey, let's stop for a minute :-) Building the package only uses the memory cache for most of the packages, doesn't it? The files it packs together have just recently been created and there are not so many packages whose uncompressed size is close to or bigger than the amount of RAM in today's machines... And for the large packages the build itself might take thousands as much time as reading the files in sorted order. Does anyone know what RPM does? I know that listing the contents of a package always produces alphabetical order but I don't know whether the filelist is sorted on the fly or the files really appear alphabetically in the cpio archive. So I guess we've already seen pros and cons of sorting the files. (One thing is missing: we still don't know how efficient rsync is if two rsyncable tar.gz files contain the same files but in different order.) The decision is clearly not mine but the Debian developers'. However, if you ask me, I still vote for sorting the files :-)) bye, Egmont
Re: A success story with apt and rsync
On Sun, Jul 06, 2003 at 05:48:24PM -0400, Theodore Ts'o wrote: On Sun, Jul 06, 2003 at 10:12:03PM +0100, Andrew Suffield wrote: On Sun, Jul 06, 2003 at 10:28:07PM +0200, Koblinger Egmont wrote: Yes, when saying random order I obviously ment in the order readdir() returns them. It's random for me. :-))) It can easily be different on different filesystems, or even on same type of filesystems with different parameters (e.g. blocksize). I can't think of any reason why changing the blocksize would affect this. Most filesystems return files in the sequence in which they were added to the directory. ext2, ext3, and reiser all do this; xfs is the only one likely to be used on a Debian system which doesn't. Err, no. If the htree (hash tree) indexing feature is turned on for ext2 or ext3 filesystems, they will returned sorted by the hash of the filename --- effectively a random order. (Since the hash also includes a secret, random, per-filesystem secret in order to avoid denial of service attacks by malicious users who might otherwise try to create huge numbers of files containing hash collisions.) I can only presume this is new or obscure, since everything I tried had the traditional behaviour. Can't see how to turn it on, either. I would be very, very surprised if reiserfs returned files in creation order. Some trivial testing indicates that it does. Heck if I know how or why. It is really, really bad assumption to assume that files will be returned in the same order as they were created. However, there's no real need to - that was just an example. As long as the sequence is more or less stable (which it should be, for btrees; don't know about htree) then rsync won't be perturbed. On ext2, as an example, stat()ting or open()ing a directory of 1 files in the order returned by readdir() will be vastly quicker than in some other sequence (like, say, bytewise lexicographic) due to the way in which the filesystem looks up inodes. This has caused significant performance issues for bugs.debian.org in the past. If you are using HTREE, and want to do a readdir() scan followed by something which opens or stat's all of the files, you very badly will want to sort the returned directory inodes by the inode number (de-d_inode). Otherwise, the order returned by readdir() will be effectively random, with the resulting loss of performance which you alluded to because the filesystem needs to randomly seek and ready all around the inode table. Hmm, that's going to cause some trouble if htree becomes common. Is there any way to test for this at runtime? The good news is that this particular optimization of sorting by inode number should work for all filesystems, and should speed up xfs as well as ext2/3 with HTREE. What about ext[23] without htree? Mucking with the order returned by readdir() has historically caused problems there... -- .''`. ** Debian GNU/Linux ** | Andrew Suffield : :' : http://www.debian.org/ | Dept. of Computing, `. `' | Imperial College, `- -- | London, UK pgpbFXtT67wbT.pgp Description: PGP signature
Re: Juridical prosecution
Please, please, please: mention this post on debian weekly news. Is really worth the effort! -- Stefano Zacchiroli -- Master in Computer Science @ Uni. Bologna, Italy [EMAIL PROTECTED],debian.org,bononia.it} - http://www.bononia.it/zack/ I know you believe you understood what you think I said, but I am not sure you realize that what you heard is not what I meant! -- G.Romney pgpmHIcLeXVtP.pgp Description: PGP signature
Re: Close old RFP/ITPs?
[Andreas Barth] So I think this is fair enough and if neither the original requester nor any reader of debian-wnpp sees need for a package it really doesn't need to be packaged any more. I have several packages which I am interested in getting packaged, but I am neither the requester nor a reader of debian-wnpp. Your assertion is thus wrong in at least one case. I believe it would be a bad idea to close RFPs just because no one responds when you ask for it. I use a script to keep track of the progress of the packages I am missing, and it will not detect new comments in the BTS entry. So, please do not in general close old RFPs unless the package is uploaded into Debian. Some of them should probably be closed as the package is dead upstream and there are better alternatives available, but that is independent of the age of the RFP.
Re: A success story with apt and rsync
On Sun, Jul 06, 2003 at 11:36:34PM +0100, Andrew Suffield wrote: On Sun, Jul 06, 2003 at 05:48:24PM -0400, Theodore Ts'o wrote: Err, no. If the htree (hash tree) indexing feature is turned on for ext2 or ext3 filesystems, they will returned sorted by the hash of the filename --- effectively a random order. (Since the hash also includes a secret, random, per-filesystem secret in order to avoid denial of service attacks by malicious users who might otherwise try to create huge numbers of files containing hash collisions.) I can only presume this is new or obscure, since everything I tried had the traditional behaviour. Can't see how to turn it on, either. I believe htree == dir_index, so tune2fs(8) and mke2fs(8) have the answer. -- - mdz
Re: NEWS.Debian support is here
Scott James Remnant wrote: Is there any particular reason to keep the unstable; urgency=low there? It's duplication of information in the changelog, and nearly every developer will probably forget to change the information in NEWS.Debian when they change the urgency or distribution in changelog. It may be that apt-listchanges could use the info in the future to sort news items. It doesn't have to match the value in the changelog. One nice thing about using standard changelog format is that if someone wants to they could add another format, specialised for news information, and another parser in /usr/lib/dpkg/parsechangelog/. Of course apt-listchanges does its own parsing, so anyone who does that would probably be well served by redesigning the parser interface to something that apt-listchanges can use. Anyway, it's nice to keep that option open. -- see shy jo pgpn3oMnK1I7e.pgp Description: PGP signature
Re: A success story with apt and rsync
On Sun, Jul 06, 2003 at 07:28:09PM -0400, Matt Zimmerman wrote: On Sun, Jul 06, 2003 at 11:36:34PM +0100, Andrew Suffield wrote: On Sun, Jul 06, 2003 at 05:48:24PM -0400, Theodore Ts'o wrote: Err, no. If the htree (hash tree) indexing feature is turned on for ext2 or ext3 filesystems, they will returned sorted by the hash of the filename --- effectively a random order. (Since the hash also includes a secret, random, per-filesystem secret in order to avoid denial of service attacks by malicious users who might otherwise try to create huge numbers of files containing hash collisions.) I can only presume this is new or obscure, since everything I tried had the traditional behaviour. Can't see how to turn it on, either. I believe htree == dir_index, so tune2fs(8) and mke2fs(8) have the answer. My /home has that enabled and readdir() returns files in creation order. -- .''`. ** Debian GNU/Linux ** | Andrew Suffield : :' : http://www.debian.org/ | Dept. of Computing, `. `' | Imperial College, `- -- | London, UK pgpNA07l53T5F.pgp Description: PGP signature
Re: NEWS.Debian support is here
On Sun, Jul 06, 2003 at 08:01:38PM -0400, Joey Hess wrote: Scott James Remnant wrote: Is there any particular reason to keep the unstable; urgency=low there? It's duplication of information in the changelog, and nearly every developer will probably forget to change the information in NEWS.Debian when they change the urgency or distribution in changelog. It may be that apt-listchanges could use the info in the future to sort news items. It doesn't have to match the value in the changelog. When merging Joe Drew's patch, I started to add support for sorting the news items by urgency. That much, at least, would be useful. The distribution is pretty unimportant in the NEWS context, though. One nice thing about using standard changelog format is that if someone wants to they could add another format, specialised for news information, and another parser in /usr/lib/dpkg/parsechangelog/. Of course apt-listchanges does its own parsing, so anyone who does that would probably be well served by redesigning the parser interface to something that apt-listchanges can use. Anyway, it's nice to keep that option open. I filed a wishlist bug about this quite a long time ago (#95579), but got no response. -- - mdz
Re: A success story with apt and rsync
On Sun, Jul 06, 2003 at 11:36:34PM +0100, Andrew Suffield wrote: I can only presume this is new or obscure, since everything I tried had the traditional behaviour. Can't see how to turn it on, either. It's new for 2.5. Backports to 2.4 are available here: http://thunk.org/tytso/linux/extfs-2.4-update/extfs-update-2.4.21 For those who are interested, the broken out patches can be found here: http://thunk.org/tytso/linux/extfs-2.4-update/broken-out-2.4.21/to-apply Once you have a htree-enabled kernel, you enable a filesystem to use the feature by using the following command: tune2fs -O dir_index /dev/hdXX Optionally, you can reorganize all of the directories to use btrees by using the command e2fsck -fD /dev/hdXX. Otherwise, only directories that are expanded beyond a single block after you set the dir_index flag will use htrees. The dir_index is a fully compatible extension, so it's perfectly safe to mount a filesystem with htrees on a non-htree kernel. A non-htree kernel will just ignore the b-tree information, and if it attempts to modify a hash-tree directory, it will just invalidate the htree interior node information, so that the directory becomes unindexed until e2fsck -fD is run over the filesystem to which optmizes all of the directories by reindexing them all. Why would you want to use htrees? Because they speed up large directories. A lot. Try creating 400,000 zero-length files in a single directory. It will take under 30 seconds with htree enabled, and well over an hour without. The good news is that this particular optimization of sorting by inode number should work for all filesystems, and should speed up xfs as well as ext2/3 with HTREE. What about ext[23] without htree? Mucking with the order returned by readdir() has historically caused problems there... It'll be fine; in fact, in some cases you'll see a slight speed up. The key is that you'll get the best performance by reading/modifying the inode data structures in sorted order by inode number. This way, you make a single sweep through the inode table, without needing any extraneous seeks. Using the natural sort order of readdir() on non-htree ext2/3 systems mostly approximated this --- although if files are deleted and created from the directory, this is not guaranteed. So sorting by inode number will never hurt, and may help. - Ted
Re: A success story with apt and rsync
On Mon, Jul 07, 2003 at 01:01:34AM +0100, Andrew Suffield wrote: I believe htree == dir_index, so tune2fs(8) and mke2fs(8) have the answer. My /home has that enabled and readdir() returns files in creation order. Then you don't have a htree-capable kernel or the directory isn't indexed. Directories that fit in a block are not indexed, as are directories larger than a block that were created before directory indexing was enabled, or if they were modified by a non-htree capable kernel. You can use the lsattr command to see if the indexed (I) flag is set on a particular directory: % lsattr -d /home/tytso --I-- /home/tytso - Ted
Re: Debconf or not debconf : Conclusion
On Thu, Jul 03, 2003 at 02:36:24PM -0500, Steve Langasek wrote: [...] This upstream change makes no sense from a usability standpoint; this new stunnel package would be pretty useless to me, and I wouldn't want to have it automatically installed on my systems if I were using the previous, working version. By the time a debconf note is sent, it's too late. the new version of stunnel is much better than the old one. i got bitten by the upgrade to 4.0-4 (when the init.d script didn't start stunnel unless ENABLED=1 in /etc/default/stunnel). big deal. i noticed it quickly enough and it took me less than a minute to scan the docs and discover that i should edit /etc/default/stunnel. the worst that happened was that my uucp-over-tcp clients weren't able to connect for a while. IMO, anyone who does an upgrade without bothering to check that important services are still running correctly afterwards is just plain sloppy and deserves whatever their negligence causes. the same applies to anyone who doesn't test upgrades of critical services on another, unimportant machine first...and for really important packages, it's a good idea to make sure you have a backup copy of the old version of the package before upgrading (dpkg-repack is useful here if it has been cleaned out of your local /var/cache/apt/archives)if the new version proves to be broken, revert to the old version. debian packages aren't a substitute for a competent and careful system admin, they're just a tool to make the sysadmin's job easier. craig
Re: Debconf or not debconf : Conclusion
On Thu, Jul 03, 2003 at 04:49:19PM -0400, Joey Hess wrote: If I ever add filtering to the notes debconf allows to be displayed, notes that refer the user to README.Debian will be at the top of the list to never be displayed. Of course, I am much more likely to bow to the pressure of notes like the one you're apparently adding, and completly disable all notes at some point, rather than adding filtering. I don't like arms races. how about a configuration option so that debconf notes get sent to an email address rather than to the screen? craig
Re: Woody KDE 3 packages
Yes! Thanks. I didn't know of the apt-cache policy command. Because the Release file was broken upstream, apt assigned it a priority of -1. I added the following lines to apt/preferences: Package: * Pin: origin download.kde.org Pin-Priority: 951 Thanks, Shaun Blind shot: $ apt-cache policy $ man apt_preferences And doesn't this question belong to users? -towo
Accepted tsclient 0.116-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 5 Jul 2003 00:19:52 +1000 Source: tsclient Binary: tsclient Architecture: source i386 Version: 0.116-1 Distribution: unstable Urgency: medium Maintainer: Andrew Lau [EMAIL PROTECTED] Changed-By: Andrew Lau [EMAIL PROTECTED] Description: tsclient - Windows Terminal Services (RDP) client for GNOME 2 Closes: 180797 Changes: tsclient (0.116-1) unstable; urgency=medium . * New upstream release. - Fix segfault on close - Further HIG compliance. (closes: #180797) * Debian Standards-Version: 3.5.10 * Switch from Debhelper to Common Build System. Files: 304a176fd99d067d1a0a91a54528b557 617 gnome optional tsclient_0.116-1.dsc 0cb1d7f00537bfa5883e9cf86b97480c 301653 gnome optional tsclient_0.116.orig.tar.gz 29a629dda87e41f0003987d17d6042b5 5953 gnome optional tsclient_0.116-1.diff.gz 15a378c988e35257b48dc69fee71aeb7 172900 gnome optional tsclient_0.116-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/B7SZOIkJWWp2WGURAvwuAJ4hDA8pBXjaDJ70TLV8gmAFMcWiXgCePgnm rW6Jzd1CBSUft4/GAF8Q5Xo= =H8ib -END PGP SIGNATURE- Accepted: tsclient_0.116-1.diff.gz to pool/main/t/tsclient/tsclient_0.116-1.diff.gz tsclient_0.116-1.dsc to pool/main/t/tsclient/tsclient_0.116-1.dsc tsclient_0.116-1_i386.deb to pool/main/t/tsclient/tsclient_0.116-1_i386.deb tsclient_0.116.orig.tar.gz to pool/main/t/tsclient/tsclient_0.116.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted usermin 1.020-3 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 6 Jul 2003 01:53:43 -0400 Source: usermin Binary: usermin Architecture: source all Version: 1.020-3 Distribution: unstable Urgency: low Maintainer: Jaldhar H. Vyas [EMAIL PROTECTED] Changed-By: Jaldhar H. Vyas [EMAIL PROTECTED] Description: usermin- A web interface for user tasks Closes: 199794 Changes: usermin (1.020-3) unstable; urgency=low . * The like wiping your arse on silk release. * Yes I know 1.030 is out. Be patient. I actually try to test this stuff before uploading you know. * Updated French .po file for debconf. Thanks again to Michel Grentzinger (Closes: #199794) Files: 5235b9eaa797caf1586c624ccad4fb19 573 admin optional usermin_1.020-3.dsc 210fff7796eff258ffa3a0b4b851fb56 20146 admin optional usermin_1.020-3.diff.gz 0fd5184d5289d0d12c76e4cc0ecb913b 433712 admin optional usermin_1.020-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/B73S2kYOR+5txmoRAi9yAJ4+yoN3mC3Y/UZ+R2PoTAl+P4holgCdH4Nm viy5mdWfWRNq7bEoufHFJgo= =VWlW -END PGP SIGNATURE- Accepted: usermin_1.020-3.diff.gz to pool/main/u/usermin/usermin_1.020-3.diff.gz usermin_1.020-3.dsc to pool/main/u/usermin/usermin_1.020-3.dsc usermin_1.020-3_all.deb to pool/main/u/usermin/usermin_1.020-3_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted make 3.80-2 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 5 Jul 2003 15:38:10 -0500 Source: make Binary: make-doc make Architecture: source i386 all Version: 3.80-2 Distribution: unstable Urgency: low Maintainer: Manoj Srivastava [EMAIL PROTECTED] Changed-By: Manoj Srivastava [EMAIL PROTECTED] Description: make - The GNU version of the make utility. make-doc - Documentation for the GNU version of the make utility. Closes: 197886 Changes: make (3.80-2) unstable; urgency=low . * *** virtual memory exhausted fixed in mainline CVS. Backported thanks to Samium Gromoff. The fix involves saving and restoring varible buffer contexts around eval'd code. closes: Bug#197886 Files: d628d43cc2932006cc0978f7274ab03f 623 devel standard make_3.80-2.dsc ce440d4eb1fb4bf5c1e211ee9986fe68 21502 devel standard make_3.80-2.diff.gz f5e5c267b61dd5834f6a7d75fb55887c 532890 doc optional make-doc_3.80-2_all.deb 3a79633c834cd280bf3d3be8ae8a60ac 357268 devel standard make_3.80-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/B79PIbrau78kQkwRAnoGAKDyhItYPWmVkGg6EzcExZXdrB6WdgCgr66F CtNWSEOTOipYaxlmXG6Nmhg= =ZlL1 -END PGP SIGNATURE- Accepted: make-doc_3.80-2_all.deb to pool/main/m/make/make-doc_3.80-2_all.deb make_3.80-2.diff.gz to pool/main/m/make/make_3.80-2.diff.gz make_3.80-2.dsc to pool/main/m/make/make_3.80-2.dsc make_3.80-2_i386.deb to pool/main/m/make/make_3.80-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted freetds 0.61-5 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 6 Jul 2003 01:19:49 -0500 Source: freetds Binary: libct1 libsybdb3 freetds-dev Architecture: source i386 Version: 0.61-5 Distribution: unstable Urgency: low Maintainer: Steve Langasek [EMAIL PROTECTED] Changed-By: Steve Langasek [EMAIL PROTECTED] Description: freetds-dev - MS SQL and Sybase client library (static libs and headers) libct1 - libraries for connecting to MS SQL and Sybase SQL servers libsybdb3 - libraries for connecting to MS SQL and Sybase SQL servers Closes: 198523 Changes: freetds (0.61-5) unstable; urgency=low . * Since we depend on the odbcinst package, always ask about ODBC support at configure time. Also, allow dpkg-reconfigure to change the ODBC handling preference. (Closes: #198523) Files: 6e02b76f3d1e93d1c2b0a42e126f66a6 615 libs optional freetds_0.61-5.dsc 62aaf75c6cbe7b3f95d4f2fa920293e5 133034 libs optional freetds_0.61-5.diff.gz b44fa0d30494a6bdebcc7f4247075a66 305234 libs optional libct1_0.61-5_i386.deb 1e551dd8b71023d2b012a15f25d049e0 81228 libs optional libsybdb3_0.61-5_i386.deb b7b57d91502391d3b0adc2c85cfe40aa 444340 devel optional freetds-dev_0.61-5_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/B8KMKN6ufymYLloRAlbYAKCjgePvjDUvDo1M9xy2DPLIujsM8gCfQGHZ KPO86tmMQtuDkQ8GdCawyNs= =zwAV -END PGP SIGNATURE- Accepted: freetds-dev_0.61-5_i386.deb to pool/main/f/freetds/freetds-dev_0.61-5_i386.deb freetds_0.61-5.diff.gz to pool/main/f/freetds/freetds_0.61-5.diff.gz freetds_0.61-5.dsc to pool/main/f/freetds/freetds_0.61-5.dsc libct1_0.61-5_i386.deb to pool/main/f/freetds/libct1_0.61-5_i386.deb libsybdb3_0.61-5_i386.deb to pool/main/f/freetds/libsybdb3_0.61-5_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted psgml 1.3.1-3 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 6 Jul 2003 01:38:54 -0500 Source: psgml Binary: psgml Architecture: source all Version: 1.3.1-3 Distribution: unstable Urgency: low Maintainer: Manoj Srivastava [EMAIL PROTECTED] Changed-By: Manoj Srivastava [EMAIL PROTECTED] Description: psgml - An Emacs major mode for editing SGML documents. Closes: 198150 Changes: psgml (1.3.1-3) unstable; urgency=low . * Added suggestions for packages that provide the html DTD's -- namely, w3c-dtd-xhtml and w3-dtd-mathml.closes: Bug#198150 Files: 8e1ddaf149285dd71cb1a4f12b4d1695 556 text optional psgml_1.3.1-3.dsc a84fa487ea35d07c2f66cb2121589503 61300 text optional psgml_1.3.1-3.diff.gz 2f42f4367c77abb4b4f84958a624dc63 284184 text optional psgml_1.3.1-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/B9iBIbrau78kQkwRAiwEAJ0XWNblNbrlTqWF8bGRgWQ2P1f99ACgrAFa Fcpllz42+dHUt8zH3n0Cjbo= =nFwI -END PGP SIGNATURE- Accepted: psgml_1.3.1-3.diff.gz to pool/main/p/psgml/psgml_1.3.1-3.diff.gz psgml_1.3.1-3.dsc to pool/main/p/psgml/psgml_1.3.1-3.dsc psgml_1.3.1-3_all.deb to pool/main/p/psgml/psgml_1.3.1-3_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted flex 2.5.31-12 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 6 Jul 2003 03:41:58 -0500 Source: flex Binary: flex-doc flex Architecture: source i386 all Version: 2.5.31-12 Distribution: unstable Urgency: low Maintainer: Manoj Srivastava [EMAIL PROTECTED] Changed-By: Manoj Srivastava [EMAIL PROTECTED] Description: flex - A fast lexical analyzer generator. flex-doc - Documentation for flex (a fast lexical analyzer generator) Closes: 198200 Changes: flex (2.5.31-12) unstable; urgency=low . * changed the implementation of the yy_scan_string function to use yy_str, as stated in the declaration, so as to allow users access to the string str in #defines. I am not completely happy with this fix, since there are other variables that may also pollute the #define name space, but going through and modifying them all would be a significant departure from upstream code; and I'm going to wait until someone complains.closes: Bug#198200 * Added a reference to flex-old in the package description, mentioning the changes in this version of flex. * Added a warning and a question in the preinst if upgrading from an old version of flex. Files: 539cabc361d74d9a2b122a47c1dcefe5 627 devel standard flex_2.5.31-12.dsc b6775d449883d0bdf82868af1c109470 23604 devel standard flex_2.5.31-12.diff.gz b1e29ca7958604912cf2273636a218db 133938 doc optional flex-doc_2.5.31-12_all.deb 8cf92ea4bb9b5cf2f66213d0a97db65b 255114 devel standard flex_2.5.31-12_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/B+bpIbrau78kQkwRAkT6AKCwEWBXiW+x9xdInv0+qNsa8hXRuwCg0E8J DUP9TshSQXBiUrstv4S7BGk= =/Pff -END PGP SIGNATURE- Accepted: flex-doc_2.5.31-12_all.deb to pool/main/f/flex/flex-doc_2.5.31-12_all.deb flex_2.5.31-12.diff.gz to pool/main/f/flex/flex_2.5.31-12.diff.gz flex_2.5.31-12.dsc to pool/main/f/flex/flex_2.5.31-12.dsc flex_2.5.31-12_i386.deb to pool/main/f/flex/flex_2.5.31-12_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted guile-1.6 1.6.4-2.1 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 6 Jul 2003 13:20:13 +0200 Source: guile-1.6 Binary: guile-1.6-slib libguile-ltdl-1 guile-1.6-libs guile-1.6-dev guile-1.6 libqthreads-12 guile-1.6-doc Architecture: source all i386 Version: 1.6.4-2.1 Distribution: unstable Urgency: low Maintainer: Rob Browning [EMAIL PROTECTED] Changed-By: Sam Hocevar (Debian packages) [EMAIL PROTECTED] Description: guile-1.6 - the GNU extension language and Scheme interpreter guile-1.6-dev - development files for Guile 1.6 guile-1.6-doc - reference and tutorial documentation for Guile 1.6 guile-1.6-libs - main Guile libraries guile-1.6-slib - Guile SLIB support libguile-ltdl-1 - Guile's patched version of libtool's libltdl libqthreads-12 - QuickThreads library for Guile Closes: 193868 193870 198896 Changes: guile-1.6 (1.6.4-2.1) unstable; urgency=low . * NMU. * libguile/continuations.c: + Applied a patch from upstream that diverts getcontext to fix the IA64 build (Closes: #193868). * libguile/smob.c: + Worked around gcc's weird code generation to fix the m68k build (Closes: #193870). * libguile/gc.c: + Fixed the garbage collector so that the subroutine table remains consistent during reallocations (Closes: #198896). * debian/control: + Set policy to 3.5.10. + Uncapitalised short descriptions (Developer's Reference 6.2.2). Files: 9885bac0feaeb329fd6fcdb9784a745b 747 - optional guile-1.6_1.6.4-2.1.dsc 42d46ae58fc4351e8cc766ece5adaa9c 5720 - optional guile-1.6_1.6.4-2.1.diff.gz 4d87ae0fff6bdb9175429670e214efca 377312 doc optional guile-1.6-doc_1.6.4-2.1_all.deb c8d40fa116471010b5e8f99332b17b2a 3282 devel optional guile-1.6-slib_1.6.4-2.1_all.deb 8601437473eec0723be77f4c8dcbe92e 31050 interpreters optional guile-1.6_1.6.4-2.1_i386.deb dca828768533f35a741e01eb3dab5821 448014 devel optional guile-1.6-dev_1.6.4-2.1_i386.deb 75af11dccb61116b4c3dda7a509300a1 547596 libs optional guile-1.6-libs_1.6.4-2.1_i386.deb 2e4b4c65e6e75262d1e020514c7eca29 5222 libs optional libqthreads-12_1.6.4-2.1_i386.deb f3637456d1cfbc916e434160334fd2df 14066 libs optional libguile-ltdl-1_1.6.4-2.1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/CAnCfPP1rylJn2ERAo8UAKCp2iScPaOQtY3oLcF3odumJp7J3wCfZR4g xbrDJU5zQSAbSx5ZA0uIjvg= =94CD -END PGP SIGNATURE- Accepted: guile-1.6-dev_1.6.4-2.1_i386.deb to pool/main/g/guile-1.6/guile-1.6-dev_1.6.4-2.1_i386.deb guile-1.6-doc_1.6.4-2.1_all.deb to pool/main/g/guile-1.6/guile-1.6-doc_1.6.4-2.1_all.deb guile-1.6-libs_1.6.4-2.1_i386.deb to pool/main/g/guile-1.6/guile-1.6-libs_1.6.4-2.1_i386.deb guile-1.6-slib_1.6.4-2.1_all.deb to pool/main/g/guile-1.6/guile-1.6-slib_1.6.4-2.1_all.deb guile-1.6_1.6.4-2.1.diff.gz to pool/main/g/guile-1.6/guile-1.6_1.6.4-2.1.diff.gz guile-1.6_1.6.4-2.1.dsc to pool/main/g/guile-1.6/guile-1.6_1.6.4-2.1.dsc guile-1.6_1.6.4-2.1_i386.deb to pool/main/g/guile-1.6/guile-1.6_1.6.4-2.1_i386.deb libguile-ltdl-1_1.6.4-2.1_i386.deb to pool/main/g/guile-1.6/libguile-ltdl-1_1.6.4-2.1_i386.deb libqthreads-12_1.6.4-2.1_i386.deb to pool/main/g/guile-1.6/libqthreads-12_1.6.4-2.1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mp3rename 0.6-7 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 6 Jul 2003 21:49:04 +1000 Source: mp3rename Binary: mp3rename Architecture: source i386 Version: 0.6-7 Distribution: unstable Urgency: low Maintainer: Mark Purcell [EMAIL PROTECTED] Changed-By: Mark Purcell [EMAIL PROTECTED] Description: mp3rename - Rename mp3 files based on id3tags Closes: 91906 130459 Changes: mp3rename (0.6-7) unstable; urgency=low . * Apply ID3v2 patch from Niki K.-M. Hansche (Closes: Bug#130459, Bug#91906) * lintian cleanup copyright-lists-upstream-authors-with-dh_make- boilerplate Files: 0644126d41860c257a7a29fd4fbfc37d 568 sound optional mp3rename_0.6-7.dsc ea309b3f45adddcd6aca34341c822fb1 4435 sound optional mp3rename_0.6-7.diff.gz 29f3144591f0f2e621de18eae64eef9d 8292 sound optional mp3rename_0.6-7_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/CAzdoCzanz0IthIRAlbxAJ4g2UP55HXIg7EAnCk03SNTWEMpyACeLv5Y xzNSBOrv1GBLeotQTrEZd14= =umcb -END PGP SIGNATURE- Accepted: mp3rename_0.6-7.diff.gz to pool/main/m/mp3rename/mp3rename_0.6-7.diff.gz mp3rename_0.6-7.dsc to pool/main/m/mp3rename/mp3rename_0.6-7.dsc mp3rename_0.6-7_i386.deb to pool/main/m/mp3rename/mp3rename_0.6-7_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted panorama 0.13.2-3.1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 6 Jul 2003 12:30:09 +0100 Source: panorama Binary: panorama Architecture: source i386 Version: 0.13.2-3.1 Distribution: unstable Urgency: low Maintainer: Marcelo E. Magallon [EMAIL PROTECTED] Changed-By: Colin Watson [EMAIL PROTECTED] Description: panorama - A framework for 3D graphics production Closes: 197232 Changes: panorama (0.13.2-3.1) unstable; urgency=low . * Non-maintainer upload at maintainer's request. * Fix link failure with g++-3.3 by including plugin headers only in static mode (thanks, Daniel Schepler; closes: #197232). Files: 8566421a6af8f6abc0588787f19e8901 727 graphics optional panorama_0.13.2-3.1.dsc 82c449233b66aac9c077f51e9e96 37085 graphics optional panorama_0.13.2-3.1.diff.gz 371aa89941e2572c16c1becffceba7ad 537820 graphics optional panorama_0.13.2-3.1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Colin Watson [EMAIL PROTECTED] -- Debian developer iD8DBQE/CA2B9t0zAhD6TNERAoyxAKCDN3VvJuQ//Db0FF3QWGZ1yYNOfQCfTe40 PEv7FswxSwUnAKdjWJthB+w= =pMqP -END PGP SIGNATURE- Accepted: panorama_0.13.2-3.1.diff.gz to pool/main/p/panorama/panorama_0.13.2-3.1.diff.gz panorama_0.13.2-3.1.dsc to pool/main/p/panorama/panorama_0.13.2-3.1.dsc panorama_0.13.2-3.1_i386.deb to pool/main/p/panorama/panorama_0.13.2-3.1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted xmule 1.5.4-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 6 Jul 2003 09:12:00 +0200 Source: xmule Binary: xmule Architecture: source i386 Version: 1.5.4-1 Distribution: unstable Urgency: low Maintainer: Noel Koethe [EMAIL PROTECTED] Changed-By: Noel Koethe [EMAIL PROTECTED] Description: xmule - a eMule client Changes: xmule (1.5.4-1) unstable; urgency=low . * new upstream release from 2003-07-06 Files: d2c1e2eee48e169cd0af9b755b0a3f4e 658 net optional xmule_1.5.4-1.dsc 1ee38c7c9c0ea0642921c533f5834360 1703044 net optional xmule_1.5.4.orig.tar.gz f9c241cdbf943f524bc5376278148f48 5016 net optional xmule_1.5.4-1.diff.gz 7ce983c53c4e0011e53daa9ebb39e574 1347270 net optional xmule_1.5.4-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/B9AU9/DnDzB9Vu0RAqdZAJ9d+r1kVnhK6PLn5l5dRxQAv58JHACfR56r xwGfSO+SqicABwmWSAH0deQ= =jXRS -END PGP SIGNATURE- Accepted: xmule_1.5.4-1.diff.gz to pool/main/x/xmule/xmule_1.5.4-1.diff.gz xmule_1.5.4-1.dsc to pool/main/x/xmule/xmule_1.5.4-1.dsc xmule_1.5.4-1_i386.deb to pool/main/x/xmule/xmule_1.5.4-1_i386.deb xmule_1.5.4.orig.tar.gz to pool/main/x/xmule/xmule_1.5.4.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted galculator 1.1.2-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 6 Jul 2003 14:07:18 +0200 Source: galculator Binary: galculator Architecture: source i386 Version: 1.1.2-1 Distribution: unstable Urgency: low Maintainer: Sebastien Bacher [EMAIL PROTECTED] Changed-By: Sebastien Bacher [EMAIL PROTECTED] Description: galculator - A GTK+ 2.0 based calculator Closes: 199298 Changes: galculator (1.1.2-1) unstable; urgency=low . * New upstream release. - Fixed typing problem in bin, hex and oct modes (Closes: #199298). Files: be11e825f51479f998109376e831be0d 619 math optional galculator_1.1.2-1.dsc f725d33adca5e1d94ae98fc79a9550d4 161378 math optional galculator_1.1.2.orig.tar.gz 2b3f998b6c673ec9c3a91aaf029aaebd 22462 math optional galculator_1.1.2-1.diff.gz 985a1fbcf7f625ac9f63e6cb4d8f6458 56792 math optional galculator_1.1.2-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/CBH5Qxo87aLX0pIRAqO6AJ9Ou+MD//D0qaFoxWc8/CXiL93lhgCfX5+F G0VGikTKo1z6m15cpVi1qQ8= =HlQ1 -END PGP SIGNATURE- Accepted: galculator_1.1.2-1.diff.gz to pool/main/g/galculator/galculator_1.1.2-1.diff.gz galculator_1.1.2-1.dsc to pool/main/g/galculator/galculator_1.1.2-1.dsc galculator_1.1.2-1_i386.deb to pool/main/g/galculator/galculator_1.1.2-1_i386.deb galculator_1.1.2.orig.tar.gz to pool/main/g/galculator/galculator_1.1.2.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted bastille 1:2.1.1-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Format: 1.7 Date: Tue, 24 Jun 2003 10:26:53 +0200 Source: bastille Binary: bastille Architecture: source i386 Version: 1:2.1.1-1 Distribution: unstable Urgency: low Maintainer: Javier Fernandez-Sanguino Pen~a [EMAIL PROTECTED] Changed-By: Javier Fernandez-Sanguino Pen~a [EMAIL PROTECTED] Description: bastille - Security hardening tool Closes: 147153 158918 184767 185951 193906 194355 Changes: bastille (1:2.1.1-1) unstable; urgency=low . * The It's been a while since I tinkered with Bastille release (many of the changes in this package need to be pushed upstream). * New upstream version. - This upstream version works properly wrt to syslog settings (Closes: #158918) - UndoBastille no longer exists (Closes: #194355) * Removed the Credits file from /usr/share/bastille (it's already under the documentation) and replace it with a symlink * Added the *config files to the examples dir. * Modified debian/rules to create a symbolic link for UndoBastille since it's no longer there. Also, the UndoBastille manpage has been modified to be used for RevertBastille and all manpages point to RevertBastille. * Added find_bastille_affected_files.pl to the examples. * Added docs/bastille.1m to the manpages * Moved the documentation calls in debian/rules to debian/docs so that it's easier to follow. * Modified the chroot script for makejail to use coreutils instead of fileutils. * Fixed the bastille-ipchains script as described by Henrik Johansson and have the package recommend bind9-host or host. Notice that I cannot add a dependancy since not all users will be setting up a local firewall (Closes: #184767) * Modified API/Bastille.pm so that chkconfig_off in Debian also removes the 'S' links. Notice that not _all_ rc files are removed since this would mean that on upgrade all the files would be recreated. Also the chkconfig_on code has been modified to work with Debian even if it's not used (calls to it from Firewall.pm and PSAD.pm have been disabled since the packages provide already init.d scripts and their rc.d links) (Closes: #193906) * Modified the installation of the bastille-firewall so that it runs on the system at priority 20 which means that it should be started before any network services, it is also stopped at level 89. * Reapplied the changes to Bastille/IOLoader.pm to add new DebugLogs. * Modified Questions.txt to fit Debian specific stuff. * Modified docs/bastille.1m to include some of the undocumented options as well as the Debian-specific information. Also modified all trailing '.C' to '.B' * Changed 'LINUX' to refer also to 'DB' * Added /var/log/Bastille/revert/backup to the directories to remove stuff from if we purge the package (Closes: #185951) * Fixed API.pm so that /var/log/Bastille/revert is used instead of /var/log/Bastillerevert (missing '/') * Modified Bastille/PSAD.pm so that it does not attempt to install PSAD, also the location of the PSAD init script has been modified for Debian. Modified also Questions.txt to add a dependancy for the 'psad' file so that it will only run if the PSAD package has been installed. With this changes bastille now configures PSAD properly if available (Closes: #147153) Files: d29368a4c647c566ae5162c50135c665 686 admin optional bastille_2.1.1-1.dsc 85d8c12c389ff3ff986fda02c079f239 429687 admin optional bastille_2.1.1.orig.tar.gz 594489b1a86acf07b8a21c3c3af3c0f0 29070 admin optional bastille_2.1.1-1.diff.gz 93b7edefa23ecec62f2aa40d2658c1de 363374 admin optional bastille_2.1.1-1_i386.deb -BEGIN PGP SIGNATURE- Version: 2.6.3ia Charset: noconv iQCVAwUBPwggAvtEPvakNq0lAQF3UQP/ecXJeggK2OIr+krOH8D/TvoSLLCtFFpB PfuMvV+aNRU2EzuCH05Z99ozJK8KH8r9kpej0wf8SV59a07Fbq8SdmPLKbIw0FIc zjWJKPXAhEFyt6N0/c2Vicxms4wWk0emEjWekXimyAppPbauAlZSdKaRMyrYDd3T A8sfMv9yJEM= =0LN1 -END PGP SIGNATURE- Accepted: bastille_2.1.1-1.diff.gz to pool/main/b/bastille/bastille_2.1.1-1.diff.gz bastille_2.1.1-1.dsc to pool/main/b/bastille/bastille_2.1.1-1.dsc bastille_2.1.1-1_i386.deb to pool/main/b/bastille/bastille_2.1.1-1_i386.deb bastille_2.1.1.orig.tar.gz to pool/main/b/bastille/bastille_2.1.1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted allegro-demo-data 3.9.36-5 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 6 Jul 2003 14:14:12 +0200 Source: allegro-demo-data Binary: allegro-demo-data Architecture: source all Version: 3.9.36-5 Distribution: unstable Urgency: low Maintainer: Sam Hocevar (Debian packages) [EMAIL PROTECTED] Changed-By: Sam Hocevar (Debian packages) [EMAIL PROTECTED] Description: allegro-demo-data - graphics and audio data for allegro-demo Changes: allegro-demo-data (3.9.36-5) unstable; urgency=low . * debian/control: + Fixed a typo in the Maintainer: field. + Rephrased the description to match other -data packages. Files: b78f02c86ca0e7b92e821b583404c9aa 625 devel optional allegro-demo-data_3.9.36-5.dsc ca234ea09ef8a567c0be63696b54 2041 devel optional allegro-demo-data_3.9.36-5.diff.gz abbf965b7fb6d96ce874fdce089ad1d2 368946 devel optional allegro-demo-data_3.9.36-5_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/CBMSfPP1rylJn2ERAhsiAJ9aYsOmJbKQsHk6ufY2iw9Yw3fXPQCdGoCW iB6INVpVvf6PssefSx/5iWM= =OU3p -END PGP SIGNATURE- Accepted: allegro-demo-data_3.9.36-5.diff.gz to pool/main/a/allegro-demo-data/allegro-demo-data_3.9.36-5.diff.gz allegro-demo-data_3.9.36-5.dsc to pool/main/a/allegro-demo-data/allegro-demo-data_3.9.36-5.dsc allegro-demo-data_3.9.36-5_all.deb to pool/main/a/allegro-demo-data/allegro-demo-data_3.9.36-5_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted smstools 1.12-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 6 Jul 2003 22:20:22 +1000 Source: smstools Binary: smstools Architecture: source i386 Version: 1.12-1 Distribution: unstable Urgency: low Maintainer: Mark Purcell [EMAIL PROTECTED] Changed-By: Mark Purcell [EMAIL PROTECTED] Description: smstools - SMS Server Tools for GSM modems Changes: smstools (1.12-1) unstable; urgency=low . * New upstream release Files: f3d6265f9e5a8b060a151f41d4ef3ccc 592 comm optional smstools_1.12-1.dsc 0a0bc9f8d69cdd2133b965e2513a40c3 146687 comm optional smstools_1.12.orig.tar.gz 2159ad422b5f30aca760c3fe4ca02a01 4107 comm optional smstools_1.12-1.diff.gz 75bb1dd30527929fc64c35c1b04438c4 152464 comm optional smstools_1.12-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/CBRroCzanz0IthIRAvQWAJ0Rh9kpRxpQmx/IYXJLUbQFXMY2agCfY+ga tsJxXJMrUZTqkzpDaoN+URo= =Dyxr -END PGP SIGNATURE- Accepted: smstools_1.12-1.diff.gz to pool/main/s/smstools/smstools_1.12-1.diff.gz smstools_1.12-1.dsc to pool/main/s/smstools/smstools_1.12-1.dsc smstools_1.12-1_i386.deb to pool/main/s/smstools/smstools_1.12-1_i386.deb smstools_1.12.orig.tar.gz to pool/main/s/smstools/smstools_1.12.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted localepurge 0.0.56 (all source)
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Sun, 06 Jul 2003 15:22:38 +0200
Source: localepurge
Binary: localepurge
Architecture: source all
Version: 0.0.56
Distribution: unstable
Urgency: low
Maintainer: Paul Seelig [EMAIL PROTECTED]
Changed-By: Paul Seelig [EMAIL PROTECTED]
Description:
localepurge - Automagically removing unnecessary locale data
Closes: 200197
Changes:
localepurge (0.0.56) unstable; urgency=low
.
* Changed localepurge/{showfreedspace,quickndirtycalc,verbose}
debconf priorities from medium to low again. Too much questions
asked for David B Harris, and i do agree. (Closes: #200197)
Files:
997aaec46ab6e0f813fad009baa3da7c 603 admin optional localepurge_0.0.56.dsc
130a0ec21469a90d2c04976818a6dd03 19466 admin optional localepurge_0.0.56.tar.gz
e58bc0e193a669fccb23dbba420e046d 22814 admin optional localepurge_0.0.56_all.deb
-BEGIN PGP SIGNATURE-
Version: 2.6.3ia
Charset: latin1
iQCVAwUBPwgi1ugqiw1XE3/lAQEKmQQAidjCvTQRKwD8siz0sEliI/gvM3Jdm8W2
rAJCa8g1PYGhW1RfcY239wjTay+XMO9zHK+qngQJ3NGSBN5H4evoR+Mi9qNztQek
9d2k5bnF9M5J2kxgqiTn5rSA0QM/aWrFoZlXfldLSYRaEBlgZfbiOhsrEjkIz1Qt
iUSAuuyBvg4=
=7HyL
-END PGP SIGNATURE-
Accepted:
localepurge_0.0.56.dsc
to pool/main/l/localepurge/localepurge_0.0.56.dsc
localepurge_0.0.56.tar.gz
to pool/main/l/localepurge/localepurge_0.0.56.tar.gz
localepurge_0.0.56_all.deb
to pool/main/l/localepurge/localepurge_0.0.56_all.deb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted amavisd-new 20030616p3-1 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 6 Jul 2003 11:15:21 -0300 Source: amavisd-new Binary: amavisd-new amavisd-new-milter Architecture: source all i386 Version: 20030616p3-1 Distribution: unstable Urgency: high Maintainer: Brian May [EMAIL PROTECTED] Changed-By: Henrique de Moraes Holschuh [EMAIL PROTECTED] Description: amavisd-new - Interface between MTA and virus scanner/content filters amavisd-new-milter - Interface between sendmail-milter and amavisd-new Closes: 199479 199947 Changes: amavisd-new (20030616p3-1) unstable; urgency=high . * New upstream version (closes: #199947) + Fixes LMTP delivery problem with fake-sender viruses (closes: #199479) + Many documentation updates + Some antivirus definition updates + Huge lot of bugfixes (see RELEASE_NOTES) + Much better behaviour when aborting SMTP sessions + Work around several perl 5.8 bugs that allowed a few DoS attacks * Update clam* package names in suggests: * Add cpio to suggests, and when it is available, use it instead of Archive::Tar to unpack tar files, to avoid loading the entire tar file in memory(!) * Add lzop to suggests, since we now support it * Bumped standards version to 3.5.10, no changes needed * Fix helper-progs to use amavis user (instead of amavisd) Files: 88a2d2f08066646eb1e1b1e8a932144d 678 mail extra amavisd-new_20030616p3-1.dsc 4b9d574fc9391d3840f608c2a534848d 274874 mail extra amavisd-new_20030616p3.orig.tar.gz 7f9c131678a2881908ee4cb61765116b 44827 mail extra amavisd-new_20030616p3-1.diff.gz c6d4e852545de9083337d712f1ce9b2f 253984 mail extra amavisd-new_20030616p3-1_all.deb 4113e8d399124ee319855f3f6be762dc 24870 mail extra amavisd-new-milter_20030616p3-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/CDiL7iXePxzbD+MRAkUoAJ0YCW4sGt2pB7vQVDIS52fBa1t7rACglNTj GAa4szkasS5cfIjRx6dLWdc= =mhiD -END PGP SIGNATURE- Accepted: amavisd-new-milter_20030616p3-1_i386.deb to pool/main/a/amavisd-new/amavisd-new-milter_20030616p3-1_i386.deb amavisd-new_20030616p3-1.diff.gz to pool/main/a/amavisd-new/amavisd-new_20030616p3-1.diff.gz amavisd-new_20030616p3-1.dsc to pool/main/a/amavisd-new/amavisd-new_20030616p3-1.dsc amavisd-new_20030616p3-1_all.deb to pool/main/a/amavisd-new/amavisd-new_20030616p3-1_all.deb amavisd-new_20030616p3.orig.tar.gz to pool/main/a/amavisd-new/amavisd-new_20030616p3.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted webalizer 2.01.10-18 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 6 Jul 2003 16:17:49 +0200 Source: webalizer Binary: webalizer Architecture: source i386 Version: 2.01.10-18 Distribution: unstable Urgency: low Maintainer: Remco van de Meent [EMAIL PROTECTED] Changed-By: Remco van de Meent [EMAIL PROTECTED] Description: webalizer - Web server log analysis program Closes: 199640 199980 Changes: webalizer (2.01.10-18) unstable; urgency=low . * Fix trailing space error in cron job (closes: #199640) * Added French translation of the debconf templates, thanks to Michel Grentzinger (closes: #199980) * Add gettext support for webalizer, thanks to Cyril Bouthors and Johan Poirier Files: 923ba646ef0621c0f16f83712030dd5f 687 web optional webalizer_2.01.10-18.dsc 13847d300a84e2b5abd61e0cd1be2355 154974 web optional webalizer_2.01.10-18.diff.gz b1ba8db67035ac9c94496bfec78ddd4e 289662 web optional webalizer_2.01.10-18_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/CECR2tWnGbzBMd4RAgcHAJsEQZNbCEHVHbo2tHn22TCUVvIltwCdFu5P /znQ6DhKUY6d41TVnSc0q6Y= =X0ie -END PGP SIGNATURE- Accepted: webalizer_2.01.10-18.diff.gz to pool/main/w/webalizer/webalizer_2.01.10-18.diff.gz webalizer_2.01.10-18.dsc to pool/main/w/webalizer/webalizer_2.01.10-18.dsc webalizer_2.01.10-18_i386.deb to pool/main/w/webalizer/webalizer_2.01.10-18_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted bogofilter 0.13.7.2-1 (source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 6 Jul 2003 11:49:35 -0400 Source: bogofilter Binary: bogofilter Architecture: source Version: 0.13.7.2-1 Distribution: unstable Urgency: medium Maintainer: Clint Adams [EMAIL PROTECTED] Changed-By: Clint Adams [EMAIL PROTECTED] Description: bogofilter - a fast Bayesian spam filter Closes: 199921 Changes: bogofilter (0.13.7.2-1) unstable; urgency=medium . * New upstream stable release. * Move tuning stuff to saner locations. closes: #199921. Files: b724ea6a8b85de11dedc1e3619d8b278 589 mail optional bogofilter_0.13.7.2-1.dsc 77dee50af4eb37a3099345fc6ccb530a 555856 mail optional bogofilter_0.13.7.2.orig.tar.gz 08c7a3e0ad00b036f1cff5410c605c09 5956 mail optional bogofilter_0.13.7.2-1.diff.gz -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Debian! iD8DBQE/CE5Y5m0u66uWM3ARAnJWAKDH8DyTL3fotPFtzrGMhe3sZPfYcwCgqdqi ULkyeSf8QjvL93FC15PSFi0= =wGWs -END PGP SIGNATURE- Accepted: bogofilter_0.13.7.2-1.diff.gz to pool/main/b/bogofilter/bogofilter_0.13.7.2-1.diff.gz bogofilter_0.13.7.2-1.dsc to pool/main/b/bogofilter/bogofilter_0.13.7.2-1.dsc bogofilter_0.13.7.2.orig.tar.gz to pool/main/b/bogofilter/bogofilter_0.13.7.2.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted atftp 0.6.2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 15 Jun 2003 16:26:13 -0400 Source: atftp Binary: atftp atftpd Architecture: source i386 Version: 0.6.2 Distribution: unstable Urgency: low Maintainer: Remi Lefebvre [EMAIL PROTECTED] Changed-By: Remi Lefebvre [EMAIL PROTECTED] Description: atftp - Advanced TFTP client. atftpd - Advanced TFTP server. Closes: 196304 Changes: atftp (0.6.2) unstable; urgency=low . * Fixed local and remote buffer overflow (Closes: #196304) Files: 841dee245ef5d22b70f6743714e7dfa7 523 net optional atftp_0.6.2.dsc 92d41593fc523d71a50f3e9e95320f01 124297 net optional atftp_0.6.2.tar.gz 38eb456dbd65f56bb114c6cc7a2fe9bf 18602 net optional atftp_0.6.2_i386.deb d3e5c02e383c97d069a750722667c9ab 48348 net optional atftpd_0.6.2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE/CFyhpUCqpBDx5zQRAgqRAJ4rd4YGj8qofP83uoxOoPoh+GjUXACggepy 16X10DwujSoezB9CFi8UcI8= =8Qpt -END PGP SIGNATURE- Accepted: atftp_0.6.2.dsc to pool/main/a/atftp/atftp_0.6.2.dsc atftp_0.6.2.tar.gz to pool/main/a/atftp/atftp_0.6.2.tar.gz atftp_0.6.2_i386.deb to pool/main/a/atftp/atftp_0.6.2_i386.deb atftpd_0.6.2_i386.deb to pool/main/a/atftp/atftpd_0.6.2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gcc-snapshot 20030706-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 6 Jul 2003 10:29:35 +0200 Source: gcc-snapshot Binary: gcc-snapshot Architecture: source i386 Version: 20030706-1 Distribution: unstable Urgency: low Maintainer: Debian GCC maintainers [EMAIL PROTECTED] Changed-By: Matthias Klose [EMAIL PROTECTED] Description: gcc-snapshot - A SNAPSHOT of the The GNU Compiler Collection. Closes: 195899 199782 Changes: gcc-snapshot (20030706-1) unstable; urgency=low . * CVS 20030706, taken from HEAD. * Set STAGE1_CFLAGS to -g -O2 on mips/mipsel (closes: #195899). * Call make with -jnumber of CPU's, if USE_NJOBS is set and non-empty in the environment (closes: #199782). Files: b0d70d4cefd2867895c45e8107ddc9de 1442 devel extra gcc-snapshot_20030706-1.dsc 73cc528f0d37d0d824f4064a7367719e 21901194 devel extra gcc-snapshot_20030706.orig.tar.gz a83c0d0c71d4d7b0b24f37da2a40d196 64730 devel extra gcc-snapshot_20030706-1.diff.gz b6c1488be82e793ce14f254323600680 38336644 devel extra gcc-snapshot_20030706-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/CBZdStlRaw+TLJwRAlqGAKCi2UvfNZh9S1bOKkN+rXzq/OMydgCgxV9f EDlJ32/UsrweCGQavVPnUxo= =inbK -END PGP SIGNATURE- Accepted: gcc-snapshot_20030706-1.diff.gz to pool/main/g/gcc-snapshot/gcc-snapshot_20030706-1.diff.gz gcc-snapshot_20030706-1.dsc to pool/main/g/gcc-snapshot/gcc-snapshot_20030706-1.dsc gcc-snapshot_20030706-1_i386.deb to pool/main/g/gcc-snapshot/gcc-snapshot_20030706-1_i386.deb gcc-snapshot_20030706.orig.tar.gz to pool/main/g/gcc-snapshot/gcc-snapshot_20030706.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mcvs 1.0.8-3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 6 Jul 2003 13:36:28 -0100 Source: mcvs Binary: mcvs Architecture: source i386 Version: 1.0.8-3 Distribution: unstable Urgency: low Maintainer: Robin Verduijn [EMAIL PROTECTED] Changed-By: Robin Verduijn [EMAIL PROTECTED] Description: mcvs - Meta-CVS is a version control system built around CVS Changes: mcvs (1.0.8-3) unstable; urgency=low . * Create stamp dir properly. Files: 4776dfa27748ab70dcc659a1fc489835 675 devel optional mcvs_1.0.8-3.dsc c5eb2c0f7942907c3d78d215ffda0225 20156 devel optional mcvs_1.0.8-3.diff.gz 0634da6fba36d05b6f880698c09f44cf 1459774 devel optional mcvs_1.0.8-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/CDUczog/I2psrrURAqUaAJwJ1Xg7ALvzB3pEwMIJQi4Q4hGN8gCgmrYG RysrC9CFqibQTbHRjf4L5Ks= =/dW1 -END PGP SIGNATURE- Accepted: mcvs_1.0.8-3.diff.gz to pool/main/m/mcvs/mcvs_1.0.8-3.diff.gz mcvs_1.0.8-3.dsc to pool/main/m/mcvs/mcvs_1.0.8-3.dsc mcvs_1.0.8-3_i386.deb to pool/main/m/mcvs/mcvs_1.0.8-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted kernel-patch-2.4-lowlatency 20030706-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 06 Jul 2003 15:21:45 -0400 Source: kernel-patch-2.4-lowlatency Binary: kernel-patch-2.4-lowlatency kernel-patch-lowlatency-2.4 Architecture: source all Version: 20030706-1 Distribution: unstable Urgency: low Maintainer: Simon Law [EMAIL PROTECTED] Changed-By: Simon Law [EMAIL PROTECTED] Description: kernel-patch-2.4-lowlatency - Reduces the latency of the Linux kernel kernel-patch-lowlatency-2.4 - Dummy package providing kernel-patch-2.4-lowlatency Closes: 198822 198823 Changes: kernel-patch-2.4-lowlatency (20030706-1) unstable; urgency=low . * Added low-latency to the package description. (Closes: Bug#198822) * New upstream version to support kernel-source-2.4.21. (Closes: Bug#198823) Files: a7e07f18e149a872ca7a6fbc56dfc4f9 605 devel extra kernel-patch-2.4-lowlatency_20030706-1.dsc 058ca63d3c4af16b457f98e13bd1c607 71038 devel extra kernel-patch-2.4-lowlatency_20030706-1.tar.gz ead71af15fa4efe324626d0882054a80 3212 devel extra kernel-patch-lowlatency-2.4_20030706-1_all.deb c14afcc536b04d22c8961606e5ec7ac6 78088 devel extra kernel-patch-2.4-lowlatency_20030706-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/CHrULiz2e3eWpgsRAjpoAKDeHr2Z52+7sCDUBJjML615RCO8QwCaAkWi p7qykXmOPU9RgLXp5Fxu3IM= =OkMb -END PGP SIGNATURE- Accepted: kernel-patch-2.4-lowlatency_20030706-1.dsc to pool/main/k/kernel-patch-2.4-lowlatency/kernel-patch-2.4-lowlatency_20030706-1.dsc kernel-patch-2.4-lowlatency_20030706-1.tar.gz to pool/main/k/kernel-patch-2.4-lowlatency/kernel-patch-2.4-lowlatency_20030706-1.tar.gz kernel-patch-2.4-lowlatency_20030706-1_all.deb to pool/main/k/kernel-patch-2.4-lowlatency/kernel-patch-2.4-lowlatency_20030706-1_all.deb kernel-patch-lowlatency-2.4_20030706-1_all.deb to pool/main/k/kernel-patch-2.4-lowlatency/kernel-patch-lowlatency-2.4_20030706-1_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted haskell98-report 20030706-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 06 Jul 2003 18:02:49 + Source: haskell98-report Binary: haskell98-report Architecture: source all Version: 20030706-1 Distribution: unstable Urgency: low Maintainer: Ian Lynagh (wibble) [EMAIL PROTECTED] Changed-By: Ian Lynagh (wibble) [EMAIL PROTECTED] Description: haskell98-report - The Haskell 98 Language and Libraries Revised Report addenda Closes: 198247 Changes: haskell98-report (20030706-1) unstable; urgency=low . * New upstream source. * Add FFI and hierarchical module addenda. Closes: #198247. Files: 5de40eba93d27ab638c138a8645f6425 705 doc optional haskell98-report_20030706-1.dsc 3d5915a81a229e8d928e460c625f2bcb 476437 doc optional haskell98-report_20030706.orig.tar.gz a3bd327c9c19dacc00a165c6d8183baf 5033 doc optional haskell98-report_20030706-1.diff.gz b6727b628ac94435a8a9bd11bdc9b18d 1728962 doc optional haskell98-report_20030706-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/CH8h63y6poDIPo4RAhvPAJ43y03lbg4UYxBJe6K9CyaqgFljiwCdGqQp 8FCwcmTweeQUtJh3IzF/0YI= =8prp -END PGP SIGNATURE- Accepted: haskell98-report_20030706-1.diff.gz to pool/main/h/haskell98-report/haskell98-report_20030706-1.diff.gz haskell98-report_20030706-1.dsc to pool/main/h/haskell98-report/haskell98-report_20030706-1.dsc haskell98-report_20030706-1_all.deb to pool/main/h/haskell98-report/haskell98-report_20030706-1_all.deb haskell98-report_20030706.orig.tar.gz to pool/main/h/haskell98-report/haskell98-report_20030706.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted wl 2.10.1-1 (all source)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sun, 6 Jul 2003 22:19:31 +0900
Source: wl
Binary: wl
Architecture: source all
Version: 2.10.1-1
Distribution: unstable
Urgency: low
Maintainer: Tatsuya Kinoshita [EMAIL PROTECTED]
Changed-By: Tatsuya Kinoshita [EMAIL PROTECTED]
Description:
wl - Yet Another Message Interface on Emacsen
Closes: 199676
Changes:
wl (2.10.1-1) unstable; urgency=low
.
* New upstream release
* Change default value of the wl-summary-weekday-name-lang variable.
On Japanese environment, ja is used by default.
(reject Debian patch for wl-vars.el)
* Rewrite Info files installation.
- Fix duplicate menuentry. (closes: #199676)
* Don't reject xemacs21-nomule. (reject Debian patch for WL-MK)
* Cleanup installation scripts.
* Ready for xemacs21-{mule,nomule} flavors.
* debian/emacsen-install: Recompile mhc for mhc-wl.
* debian/emacsen-startup: Cleanup.
* debian/control: Conflict with xbase ( 3.3.2.3a-2).
* debian/rules: Don't leave install-stamp when `debuild clean'.
* debian/rules: Use binary-indep instead of binary-arch.
* debian/rules: Install changelog.utils.
* debian/control: Use Build-Depends-Indep instead of Build-Depends.
* debian/control: Build-depend on emacs20 instead of emacs21.
* debian/docs: Don't contain install documentation.
* debian/docs: Add doc/TODO.
* debian/docs: Remove doc/wl-ja.texi.
* debian/prerm: Removed.
* debian/control (Depends): Prefer emacs21 instead of emacs20.
* debian/control (Depends): semi (= 1.14) - (= 1.14.3).
* debian/control (Suggests): Add bbdb and im.
* debian/control (Standards-Version): 3.5.2 - 3.5.10.
* debian/control (Description): Revised.
* debian/copyright: Revised.
* debian/env.el: Use prefer-coding-system instead of
set-default-coding-systems.
* debian/README.Debian: Removed.
* New maintainer. (with previous maintainer's consent)
Files:
b8c462a6b6c394ede5bc05c877422586 572 mail optional wl_2.10.1-1.dsc
80cb1a4e3c76025284bf7eaa23faf1d6 967205 mail optional wl_2.10.1.orig.tar.gz
81c930bd605daf694b48ecb08b2e469d 9262 mail optional wl_2.10.1-1.diff.gz
c52259e0e248056a15c7de137dad630d 787512 mail optional wl_2.10.1-1_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/CHJR9D5yZjzIjAkRAu8QAKCxXOzAj4Z1idGOTJcSpWUNRaQ12gCePkio
pth1Svs9s2O+S1Wxeit4Jt8=
=YAOf
-END PGP SIGNATURE-
Accepted:
wl_2.10.1-1.diff.gz
to pool/main/w/wl/wl_2.10.1-1.diff.gz
wl_2.10.1-1.dsc
to pool/main/w/wl/wl_2.10.1-1.dsc
wl_2.10.1-1_all.deb
to pool/main/w/wl/wl_2.10.1-1_all.deb
wl_2.10.1.orig.tar.gz
to pool/main/w/wl/wl_2.10.1.orig.tar.gz
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted ghc5 5.04.3-3 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 06 Jul 2003 16:03:12 + Source: ghc5 Binary: ghc5-prof ghc5 ghc5-doc ghc5-hopengl Architecture: source all i386 Version: 5.04.3-3 Distribution: unstable Urgency: low Maintainer: Ian Lynagh (wibble) [EMAIL PROTECTED] Changed-By: Ian Lynagh (wibble) [EMAIL PROTECTED] Description: ghc5 - GHC - the Glasgow Haskell Compilation system ghc5-doc - Documentation for the Glasgow Haskell Compilation system ghc5-hopengl - HOpenGL libraries for the Glasgow Haskell Compilation system ghc5-prof - Profiling libraries for the Glasgow Haskell Compilation system Changes: ghc5 (5.04.3-3) unstable; urgency=low . * Don't symlink book1.html to the first HTML page - behaviour seems to have changed so it was just overwriting the page with a dangling symlink. Files: b0173cb56db7f248e9f26eb6bbefa4e2 843 devel optional ghc5_5.04.3-3.dsc 951cf736cb716f07a3003a423214a7de 27315 devel optional ghc5_5.04.3-3.diff.gz 64b27ea894f9c16cc96488477437451d 12726072 devel optional ghc5_5.04.3-3_i386.deb 850ed974154db6eeab5965874d13963f 762152 devel optional ghc5-hopengl_5.04.3-3_i386.deb fc9b4bd44f820d99732b839ef4c1a059 7060166 devel optional ghc5-prof_5.04.3-3_i386.deb 466fe1e1c8967556acd78b815703d7cb 1404084 doc optional ghc5-doc_5.04.3-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/CIGu63y6poDIPo4RAuXqAJ44CN2WwZVlg879Wgj2PpixgO3KuQCbBaca uYXYKSj0YggCM9kCIo5DrX8= =/fmd -END PGP SIGNATURE- Accepted: ghc5-doc_5.04.3-3_all.deb to pool/main/g/ghc5/ghc5-doc_5.04.3-3_all.deb ghc5-hopengl_5.04.3-3_i386.deb to pool/main/g/ghc5/ghc5-hopengl_5.04.3-3_i386.deb ghc5-prof_5.04.3-3_i386.deb to pool/main/g/ghc5/ghc5-prof_5.04.3-3_i386.deb ghc5_5.04.3-3.diff.gz to pool/main/g/ghc5/ghc5_5.04.3-3.diff.gz ghc5_5.04.3-3.dsc to pool/main/g/ghc5/ghc5_5.04.3-3.dsc ghc5_5.04.3-3_i386.deb to pool/main/g/ghc5/ghc5_5.04.3-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted kvirc 2:2.1.2-18 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 6 Jul 2003 13:20:00 -0100 Source: kvirc Binary: kvirc-doc kvirc-dev kvirc Architecture: source i386 all Version: 2:2.1.2-18 Distribution: unstable Urgency: low Maintainer: Robin Verduijn [EMAIL PROTECTED] Changed-By: Robin Verduijn [EMAIL PROTECTED] Description: kvirc - Fully scriptable graphical IRC client with plugin support kvirc-dev - Development files for KVIrc kvirc-doc - Help files for KVIrc Closes: 199806 Changes: kvirc (2:2.1.2-18) unstable; urgency=low . * Remove RFCs from the kvirc-doc package. (Closes: #199806) Files: 53202cbd4b45feb6d21b4bc7ad3c11f9 814 net optional kvirc_2.1.2-18.dsc 8c8cf60166c59fa91b1c65a583da4e9a 210949 net optional kvirc_2.1.2-18.diff.gz 5bd1ece631d6402eb2cc9b4653ca4def 1910822 net optional kvirc_2.1.2-18_i386.deb 5c364ba3233dcac6ba02e626f5748ade 199506 devel optional kvirc-dev_2.1.2-18_i386.deb b9a67ddc90c279173da64d0ec90716ba 183930 doc optional kvirc-doc_2.1.2-18_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/CFPKzog/I2psrrURAs0/AKCEiQXqyKVcfqaH5gwqv5wKd8+OhgCaA3i6 hz9/MuJ6DUcHL/Q6WhgjDa0= =UU5d -END PGP SIGNATURE- Accepted: kvirc-dev_2.1.2-18_i386.deb to pool/main/k/kvirc/kvirc-dev_2.1.2-18_i386.deb kvirc-doc_2.1.2-18_all.deb to pool/main/k/kvirc/kvirc-doc_2.1.2-18_all.deb kvirc_2.1.2-18.diff.gz to pool/main/k/kvirc/kvirc_2.1.2-18.diff.gz kvirc_2.1.2-18.dsc to pool/main/k/kvirc/kvirc_2.1.2-18.dsc kvirc_2.1.2-18_i386.deb to pool/main/k/kvirc/kvirc_2.1.2-18_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted eep24c 0.1.1-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 6 Jul 2003 18:31:11 -0300 Source: eep24c Binary: eep24c Architecture: source i386 Version: 0.1.1-2 Distribution: unstable Urgency: low Maintainer: Pedro Zorzenon Neto [EMAIL PROTECTED] Changed-By: Pedro Zorzenon Neto [EMAIL PROTECTED] Description: eep24c - read and write serial I2C eeprom devices Changes: eep24c (0.1.1-2) unstable; urgency=low . * Changed debian/control file. Included new eeprom type 24xx515. Files: a194119215c3283531a44b204ffc0443 603 electronics extra eep24c_0.1.1-2.dsc 62a3761d842a02f78f7e4de4f7e55490 2551 electronics extra eep24c_0.1.1-2.diff.gz 8d8485c409bfff69324e2850644d6836 85948 electronics extra eep24c_0.1.1-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE/CJbFOcl5Y3J0qgcRAoIrAJ9c/KtPw8Qw9km6yPr6BlbBQHRgSwCdEJ00 nZDLOFABPoSFkbfC/SD8PGE= =qncK -END PGP SIGNATURE- Accepted: eep24c_0.1.1-2.diff.gz to pool/main/e/eep24c/eep24c_0.1.1-2.diff.gz eep24c_0.1.1-2.dsc to pool/main/e/eep24c/eep24c_0.1.1-2.dsc eep24c_0.1.1-2_i386.deb to pool/main/e/eep24c/eep24c_0.1.1-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted interchange 4.9.8.20030706-1 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 6 Jul 2003 19:31:34 +0200 Source: interchange Binary: interchange-cat-foundation interchange-ui interchange libapache-mod-interchange Architecture: source i386 all Version: 4.9.8.20030706-1 Distribution: unstable Urgency: low Maintainer: Stefan Hornburg (Racke) [EMAIL PROTECTED] Changed-By: Stefan Hornburg (Racke) [EMAIL PROTECTED] Description: interchange - e-commerce and general HTTP database display system interchange-cat-foundation - Foundation Store, a sample Interchange catalog interchange-ui - Interchange administration interface (UI) libapache-mod-interchange - Integration of the Interchange link protocol with Apache Closes: 198675 Changes: interchange (4.9.8.20030706-1) unstable; urgency=low . * release from upstream CVS (uses custom module instead of SQL::Statement now) * don't stop short on 'Unknown host' in interchange-cat-foundation postinst * set MINIVEND_FORCE_THREADS in the wrapper instead of the init script (Closes: #198675) Files: 52990c3b78a1b4a6b10f91bf1026a8da 777 web optional interchange_4.9.8.20030706-1.dsc a5e93982cd169e65f2f3f68f2ea592f5 1985240 web optional interchange_4.9.8.20030706.orig.tar.gz 9e82635ea12cc76bf9a8e1018d3eafbf 20 web optional interchange_4.9.8.20030706-1.diff.gz e779bb660593c415063a473d2e95839b 819568 web optional interchange-cat-foundation_4.9.8.20030706-1_all.deb 747e4402944ea4eeb6bd4f46a8fa071a 527168 web optional interchange-ui_4.9.8.20030706-1_all.deb 22c0aeaecf3f486cb3471b050e7e39e3 787834 web optional interchange_4.9.8.20030706-1_i386.deb 4ddd67bebed9c5ab9c843eafcae6f56b 18340 web optional libapache-mod-interchange_4.9.8.20030706-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/CJaejgVfE5tya3ERAu8jAKCoyAizi2Sc81vkLh40qcTHMK+yVgCgnJIy ycLA3QCx1PoBvwpFjGwXXy0= =lEcd -END PGP SIGNATURE- Accepted: interchange-cat-foundation_4.9.8.20030706-1_all.deb to pool/main/i/interchange/interchange-cat-foundation_4.9.8.20030706-1_all.deb interchange-ui_4.9.8.20030706-1_all.deb to pool/main/i/interchange/interchange-ui_4.9.8.20030706-1_all.deb interchange_4.9.8.20030706-1.diff.gz to pool/main/i/interchange/interchange_4.9.8.20030706-1.diff.gz interchange_4.9.8.20030706-1.dsc to pool/main/i/interchange/interchange_4.9.8.20030706-1.dsc interchange_4.9.8.20030706-1_i386.deb to pool/main/i/interchange/interchange_4.9.8.20030706-1_i386.deb interchange_4.9.8.20030706.orig.tar.gz to pool/main/i/interchange/interchange_4.9.8.20030706.orig.tar.gz libapache-mod-interchange_4.9.8.20030706-1_i386.deb to pool/main/i/interchange/libapache-mod-interchange_4.9.8.20030706-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted file-roller 2.3.3-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 6 Jul 2003 21:30:52 +0200 Source: file-roller Binary: file-roller Architecture: source i386 Version: 2.3.3-1 Distribution: unstable Urgency: low Maintainer: Sebastien Bacher [EMAIL PROTECTED] Changed-By: Sebastien Bacher [EMAIL PROTECTED] Description: file-roller - An archiver for GNOME Closes: 181075 193478 197770 198909 Changes: file-roller (2.3.3-1) unstable; urgency=low . * New upstream release. - Default format for new archive (Closes: #181075). * Fixed error in /usr/lib/mime/packages/file-roller (Closes: #193478). * Use dh_scrollkeep (Closes: #197770, #198909). * Updated to standards-version 3.5.10.0. Files: 5d6e604e02cd042132c89966f3ec1ec6 688 x11 optional file-roller_2.3.3-1.dsc a4443d571a8262a17789ba2c492f12aa 1166978 x11 optional file-roller_2.3.3.orig.tar.gz 11287ef281f6f548165d4dc7c7fb3258 3450 x11 optional file-roller_2.3.3-1.diff.gz 0f3126449589671a14ddc397f4fa33e9 655626 x11 optional file-roller_2.3.3-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/CJkDQxo87aLX0pIRAvTTAJ9LcRrdHsMnVblcC8I9pXZj+lkKSgCgurEd 0MRRaNtSNZzNWIr3bi39uEM= =KEVT -END PGP SIGNATURE- Accepted: file-roller_2.3.3-1.diff.gz to pool/main/f/file-roller/file-roller_2.3.3-1.diff.gz file-roller_2.3.3-1.dsc to pool/main/f/file-roller/file-roller_2.3.3-1.dsc file-roller_2.3.3-1_i386.deb to pool/main/f/file-roller/file-roller_2.3.3-1_i386.deb file-roller_2.3.3.orig.tar.gz to pool/main/f/file-roller/file-roller_2.3.3.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted drivel 0.9.1-3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 5 Jul 2003 18:37:45 +0100 Source: drivel Binary: drivel Architecture: source i386 Version: 0.9.1-3 Distribution: unstable Urgency: low Maintainer: Neil McGovern [EMAIL PROTECTED] Changed-By: Neil McGovern [EMAIL PROTECTED] Description: drivel - A LiveJournal client for the GNOME desktop Changes: drivel (0.9.1-3) unstable; urgency=low . * Updated drivel.desktop.in to use livejournal.png as opposed to livejournal.xpm so desktop icon is in color. Files: 5d9726b2f4ef6561c70ee1aa58b1df77 871 net optional drivel_0.9.1-3.dsc ac261d7971a45ea26ff46bf714ce87b2 95109 net optional drivel_0.9.1-3.diff.gz 2420a05e56efc372435551cf2bfe8f42 145968 net optional drivel_0.9.1-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/CJtDDzQFd9CXomERAleCAKCHmkZYe9kM1iH0Wg7ycSIMB0WeygCgoy+5 hUcaRtAaUcnB80eGggwnRZ4= =M9NV -END PGP SIGNATURE- Accepted: drivel_0.9.1-3.diff.gz to pool/main/d/drivel/drivel_0.9.1-3.diff.gz drivel_0.9.1-3.dsc to pool/main/d/drivel/drivel_0.9.1-3.dsc drivel_0.9.1-3_i386.deb to pool/main/d/drivel/drivel_0.9.1-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mozilla 2:1.4-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 3 Jul 2003 14:16:19 +0900 Source: mozilla Binary: mozilla mozilla-dom-inspector libnspr4 mozilla-js-debugger mozilla-browser libnss3 libnspr-dev mozilla-chatzilla mozilla-psm mozilla-mailnews libnss-dev mozilla-xft mozilla-dev Architecture: source i386 Version: 2:1.4-1 Distribution: unstable Urgency: low Maintainer: Takuo KITAME [EMAIL PROTECTED] Changed-By: Takuo KITAME [EMAIL PROTECTED] Description: libnspr-dev - Netscape Portable Runtime library - development files libnspr4 - Netscape Portable Runtime Library libnss-dev - Network Security Service Libraries - development libnss3- Network Security Service Libraries - runtime mozilla- Mozilla Web Browser - dummy package mozilla-browser - Mozilla Web Browser - core and browser mozilla-chatzilla - Mozilla Web Browser - irc client mozilla-dev - Mozilla Web Browser - development files mozilla-dom-inspector - A tool for inspecting the DOM of pages in Mozilla. mozilla-js-debugger - JavaScript debugger for use with Mozilla mozilla-mailnews - Mozilla Web Browser - mail and news support mozilla-psm - Mozilla Web Browser - Personal Security Manager (PSM) mozilla-xft - Mozilla Web Browser - Xft support files Closes: 198415 199634 Changes: mozilla (2:1.4-1) unstable; urgency=low . * New upstream release * fix postinst, preserve local changes (closes: #198415) * s390 and hppa build-fix patch have been temporary moved out. (patch FAILED) * ln -s /usr/lib/mozilla/libxpcom.so /usr/lib/libxpcom.so (closes: #199634) Files: 3ba977eb1aab4029037aea8c6523f790 976 web optional mozilla_1.4-1.dsc 067c291167747edda68a7443c2d5fd33 31999484 web optional mozilla_1.4.orig.tar.gz beaeffd9eef83564639003c4f88f0488 920176 web optional mozilla_1.4-1.diff.gz edc046516daff7d886eff2ff2da4561d 1024 web optional mozilla_1.4-1_i386.deb 87333d50cbf184eb1173523b6a906c55 10017098 web optional mozilla-browser_1.4-1_i386.deb 97e2d509f31df8de261b7345b0e395cf 175910 web optional mozilla-xft_1.4-1_i386.deb c3109b688223153723a3f4ef01dc7996 3114428 devel optional mozilla-dev_1.4-1_i386.deb a36ccfd7c5950f2cbf6578805a5b6491 1958100 mail optional mozilla-mailnews_1.4-1_i386.deb 690793de276c207cd4a4c0b7757477b7 112128 net optional mozilla-chatzilla_1.4-1_i386.deb 1ee1b3c4670e2d4da4b172555f17915c 179802 web optional mozilla-psm_1.4-1_i386.deb 821fab3dd20a83c58aec713eedc129c5 149620 web optional mozilla-dom-inspector_1.4-1_i386.deb fbfc063ba8e870010e595883b424fad3 202866 devel optional mozilla-js-debugger_1.4-1_i386.deb 426c1ad450d09c910cd77a0778d731de 117330 libs optional libnspr4_1.4-1_i386.deb d826dfb56070661fe6b752c24abc8ea6 166430 libdevel optional libnspr-dev_1.4-1_i386.deb e88de52e52f060335aab5795a3883827 580826 libs optional libnss3_1.4-1_i386.deb 06e089a5815946c5318e5763555a3e17 187226 libdevel optional libnss-dev_1.4-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/CKDSU+WZW1FVMwoRAm5VAJ9aM56foFEmiA4MUmbSNU69ZhjHBACeJo4h BGbZxst7litgXooKzXxr8X4= =V4Gv -END PGP SIGNATURE- Accepted: libnspr-dev_1.4-1_i386.deb to pool/main/m/mozilla/libnspr-dev_1.4-1_i386.deb libnspr4_1.4-1_i386.deb to pool/main/m/mozilla/libnspr4_1.4-1_i386.deb libnss-dev_1.4-1_i386.deb to pool/main/m/mozilla/libnss-dev_1.4-1_i386.deb libnss3_1.4-1_i386.deb to pool/main/m/mozilla/libnss3_1.4-1_i386.deb mozilla-browser_1.4-1_i386.deb to pool/main/m/mozilla/mozilla-browser_1.4-1_i386.deb mozilla-chatzilla_1.4-1_i386.deb to pool/main/m/mozilla/mozilla-chatzilla_1.4-1_i386.deb mozilla-dev_1.4-1_i386.deb to pool/main/m/mozilla/mozilla-dev_1.4-1_i386.deb mozilla-dom-inspector_1.4-1_i386.deb to pool/main/m/mozilla/mozilla-dom-inspector_1.4-1_i386.deb mozilla-js-debugger_1.4-1_i386.deb to pool/main/m/mozilla/mozilla-js-debugger_1.4-1_i386.deb mozilla-mailnews_1.4-1_i386.deb to pool/main/m/mozilla/mozilla-mailnews_1.4-1_i386.deb mozilla-psm_1.4-1_i386.deb to pool/main/m/mozilla/mozilla-psm_1.4-1_i386.deb mozilla-xft_1.4-1_i386.deb to pool/main/m/mozilla/mozilla-xft_1.4-1_i386.deb mozilla_1.4-1.diff.gz to pool/main/m/mozilla/mozilla_1.4-1.diff.gz mozilla_1.4-1.dsc to pool/main/m/mozilla/mozilla_1.4-1.dsc mozilla_1.4-1_i386.deb to pool/main/m/mozilla/mozilla_1.4-1_i386.deb mozilla_1.4.orig.tar.gz to pool/main/m/mozilla/mozilla_1.4.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted lilo-installer 0.0.16 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 7 Jul 2003 00:29:06 +0200 Source: lilo-installer Binary: lilo-installer Architecture: source i386 Version: 0.0.16 Distribution: unstable Urgency: low Maintainer: Debian Install System Team [EMAIL PROTECTED] Changed-By: Petter Reinholdtsen [EMAIL PROTECTED] Description: lilo-installer - Install LILO on a hard disk (udeb) Closes: 199955 Changes: lilo-installer (0.0.16) unstable; urgency=low . * Pierre Machard: - Update French po-debconf template * Petter Reinholdtsen - Change template name from lilo-installer/activate_part to lilo-installer/activate-part to match the script. Patch from Joe Nahmias. (Closes: #199955) Files: 2ef1e6bbe1a27b981bea9a5787d8354d 681 debian-installer standard lilo-installer_0.0.16.dsc d1fb0bc394eee0ecc1e0518c7dc529d7 10950 debian-installer standard lilo-installer_0.0.16.tar.gz 7e299ba080f594428d973f854dcc0fc9 4316 debian-installer standard lilo-installer_0.0.16_i386.udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/CKML20zMSyow1ykRAsTBAKDNVyDhCPfmEMH15t/lopS4Px5T7ACeK2NH NEQbCN0/yLbX4Cmb1/51Lcs= =S0Ys -END PGP SIGNATURE- Accepted: lilo-installer_0.0.16.dsc to pool/main/l/lilo-installer/lilo-installer_0.0.16.dsc lilo-installer_0.0.16.tar.gz to pool/main/l/lilo-installer/lilo-installer_0.0.16.tar.gz lilo-installer_0.0.16_i386.udeb to pool/main/l/lilo-installer/lilo-installer_0.0.16_i386.udeb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted ghc6 6.0-2 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 06 Jul 2003 14:42:40 + Source: ghc6 Binary: ghc6-prof ghc6-hopengl ghc6 ghc6-doc Architecture: source all i386 Version: 6.0-2 Distribution: unstable Urgency: low Maintainer: Ian Lynagh (wibble) [EMAIL PROTECTED] Changed-By: Ian Lynagh (wibble) [EMAIL PROTECTED] Description: ghc6 - GHC - the Glasgow Haskell Compilation system ghc6-doc - Documentation for the Glasgow Haskell Compilation system ghc6-hopengl - HOpenGL libraries for the Glasgow Haskell Compilation system ghc6-prof - Profiling libraries for the Glasgow Haskell Compilation system Closes: 199786 Changes: ghc6 (6.0-2) unstable; urgency=low . * Fix GET_PROC_ADDRESS properly so opengl libraries can be used (from upstream CVS) * GLUT libraries are also installed in the hopengl deb * Update build-depends and depends to libglut3-dev, xlibmesa-gl-dev and xlibmesa-glu-dev from glutg3-dev and xlibmesa-dev. * Require at least version 0.4.0 of haddock. * Fix doc-base control file links. * Policy 3.5.10 compliant. * Create the hp2ps-ghc6.1 manpage correctly. Closes: #199786. * Change glActiveTexture to glActiveTextureARB. ghci now loads with the OpenGL and GLUT packages. * Update build-depend on debhelper to = 4. * Correct GHC5 to GHC6 in the doc-base title. Files: 270498da0100900358f9049463672b4f 866 devel optional ghc6_6.0-2.dsc e23d9f899249c2ae0105306bf2d7ad15 17079 devel optional ghc6_6.0-2.diff.gz 15d9dfa24508f9d133d5b8c2ec96352a 1738342 doc optional ghc6-doc_6.0-2_all.deb 4436c7d84b6c86e0f163b097b2046779 10819288 devel optional ghc6_6.0-2_i386.deb 58d3f4454cc66bfaff83b18846433fea 3037596 devel optional ghc6-hopengl_6.0-2_i386.deb cd4cb045011473177d4d3bec348ffc9f 7292844 devel optional ghc6-prof_6.0-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/CKWh63y6poDIPo4RAv5zAKCEwl8/qyI0mU187njTuNE1vSbLQgCeKL/G vm77dUdmiHt7bhBFEboFzk8= =qEmw -END PGP SIGNATURE- Accepted: ghc6-doc_6.0-2_all.deb to pool/main/g/ghc6/ghc6-doc_6.0-2_all.deb ghc6-hopengl_6.0-2_i386.deb to pool/main/g/ghc6/ghc6-hopengl_6.0-2_i386.deb ghc6-prof_6.0-2_i386.deb to pool/main/g/ghc6/ghc6-prof_6.0-2_i386.deb ghc6_6.0-2.diff.gz to pool/main/g/ghc6/ghc6_6.0-2.diff.gz ghc6_6.0-2.dsc to pool/main/g/ghc6/ghc6_6.0-2.dsc ghc6_6.0-2_i386.deb to pool/main/g/ghc6/ghc6_6.0-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted snort 2.0.0-3.2 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 29 Jun 2003 19:23:24 +0200 Source: snort Binary: snort-mysql snort-doc snort-rules-default snort-common snort-pgsql snort Architecture: source i386 all Version: 2.0.0-3.2 Distribution: unstable Urgency: low Maintainer: Sander Smeenk [EMAIL PROTECTED] Changed-By: Christian Perrier [EMAIL PROTECTED] Description: snort - Flexible Network Intrusion Detection System snort-common - Flexible Network Intrusion Detection System snort-doc - Documentation for the Snort IDS snort-mysql - Flexible Network Intrusion Detection System snort-pgsql - Flexible Network Intrusion Detection System snort-rules-default - Flexible Network Intrusion Detection System Closes: 192952 Changes: snort (2.0.0-3.2) unstable; urgency=low . * NMU * French debconf templates translation * Untranslatable strings are unmarked for translation in debconf templates Closes: #192952 Files: 3f31d1bd824e89898292d46fc0db8cab 746 net optional snort_2.0.0-3.2.dsc 87cf55d5c57e4502dc72588d1be713f3 75180 net optional snort_2.0.0-3.2.diff.gz 77986aa6740d00be4f4c328a2d067e26 194854 net optional snort_2.0.0-3.2_i386.deb 2acc7f00339393e7d4d8c8bed50b5127 62678 net optional snort-common_2.0.0-3.2_i386.deb a1a5d128052a796a2414a229c0b484d9 547048 doc optional snort-doc_2.0.0-3.2_all.deb c11321aaff63f5bf3e6a6f268b9eab68 199710 net extra snort-mysql_2.0.0-3.2_i386.deb 513f94ac296b66517f8238764cadae80 199616 net optional snort-pgsql_2.0.0-3.2_i386.deb eee462eed2deb1ce75d6f8398536ce13 139264 net optional snort-rules-default_2.0.0-3.2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+/yuBiONoszDJNIoRAsXQAJ4jBSn0nAfODhupLn7Dz75AhzrGTQCeJE6F /y3MO9A7CCDu3hQb0Ezk8CY= =sH5V -END PGP SIGNATURE- Accepted: snort-common_2.0.0-3.2_i386.deb to pool/main/s/snort/snort-common_2.0.0-3.2_i386.deb snort-doc_2.0.0-3.2_all.deb to pool/main/s/snort/snort-doc_2.0.0-3.2_all.deb snort-mysql_2.0.0-3.2_i386.deb to pool/main/s/snort/snort-mysql_2.0.0-3.2_i386.deb snort-pgsql_2.0.0-3.2_i386.deb to pool/main/s/snort/snort-pgsql_2.0.0-3.2_i386.deb snort-rules-default_2.0.0-3.2_all.deb to pool/main/s/snort/snort-rules-default_2.0.0-3.2_all.deb snort_2.0.0-3.2.diff.gz to pool/main/s/snort/snort_2.0.0-3.2.diff.gz snort_2.0.0-3.2.dsc to pool/main/s/snort/snort_2.0.0-3.2.dsc snort_2.0.0-3.2_i386.deb to pool/main/s/snort/snort_2.0.0-3.2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gnutls7 0.8.9-2 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 4 Jul 2003 16:35:39 +0200 Source: gnutls7 Binary: libgnutls-doc gnutls-bin libgnutls7 libgnutls7-dev Architecture: source i386 all Version: 0.8.9-2 Distribution: unstable Urgency: high Maintainer: Ivo Timmermans [EMAIL PROTECTED] Changed-By: Ivo Timmermans [EMAIL PROTECTED] Description: gnutls-bin - GNU TLS library - commandline utilities libgnutls-doc - GNU TLS library - documentation and examples libgnutls7 - GNU TLS library - runtime library libgnutls7-dev - GNU TLS library - development files Closes: 200013 Changes: gnutls7 (0.8.9-2) unstable; urgency=high . * debian/control: Added Build-Conflicts for libgnutls-dev. (Closes: #200013) Files: 3606385c1cc7ae1a2371d23799414e44 778 devel optional gnutls7_0.8.9-2.dsc 60642f2782781a40bc6eb8100fb75fbe 26513 devel optional gnutls7_0.8.9-2.diff.gz 4fea43c513ee980139565f5543813017 426066 doc optional libgnutls-doc_0.8.9-2_all.deb e94158864998d44adb0c17247961eafb 203224 libdevel optional libgnutls7-dev_0.8.9-2_i386.deb cec190bdf934cc86bbf29a61b3d5530c 182476 libs standard libgnutls7_0.8.9-2_i386.deb 03e10d2ced45a8420bbb4ad55bb1f52d 110772 net optional gnutls-bin_0.8.9-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/CKmNbTEMl+oVcvERAicOAKCpMoZJnkc6hVsHcxmHmtothm6RawCgh5CY RTgql4LlFtaw+O3+hivB5ag= =enBJ -END PGP SIGNATURE- Accepted: gnutls-bin_0.8.9-2_i386.deb to pool/main/g/gnutls7/gnutls-bin_0.8.9-2_i386.deb gnutls7_0.8.9-2.diff.gz to pool/main/g/gnutls7/gnutls7_0.8.9-2.diff.gz gnutls7_0.8.9-2.dsc to pool/main/g/gnutls7/gnutls7_0.8.9-2.dsc libgnutls-doc_0.8.9-2_all.deb to pool/main/g/gnutls7/libgnutls-doc_0.8.9-2_all.deb libgnutls7-dev_0.8.9-2_i386.deb to pool/main/g/gnutls7/libgnutls7-dev_0.8.9-2_i386.deb libgnutls7_0.8.9-2_i386.deb to pool/main/g/gnutls7/libgnutls7_0.8.9-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cppopt 0.0.2-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Format: 1.7 Date: Sun, 6 Jul 2003 18:33:11 -0500 Source: cppopt Binary: libcppopt0 libcppopt-dev Architecture: source i386 Version: 0.0.2-1 Distribution: unstable Urgency: low Maintainer: Zed Pobre [EMAIL PROTECTED] Changed-By: Zed Pobre [EMAIL PROTECTED] Description: libcppopt-dev - C++ option parsing library header files libcppopt0 - C++ option parsing library Closes: 174964 Changes: cppopt (0.0.2-1) unstable; urgency=low . * New upstream release * Compiled with g++-3.3 (closes: #174964) * Standards-Version 3.5.10 * Specify GPL version 2, exactly, in debian/copyright * Fix Author(s) to Author in debian/copyright Files: db2ecc9701fbc46822ed2a938e7bdf32 805 devel optional cppopt_0.0.2-1.dsc 350149cc412c3b1580bd7615224eed89 25502 devel optional cppopt_0.0.2-1.tar.gz 3d31daac0835207a350d6b8b7322e90d 29498 devel optional libcppopt-dev_0.0.2-1_i386.deb 1c6d6968a926793df75e55e5ea72f1bd 29570 devel optional libcppopt0_0.0.2-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iQEVAwUBPwi1FB0207zoJUw5AQGZ7Af/T5bD/9V3JHhBEy2dCQQvX3EZZFvLxwkR XDKgktoviQD9fbkX7aq0J+4y5XFxMJtjrCTCMuVDR2WW9cQlfNmLHjfKWQv670eg 4EWNhQboX/Kj8JuWwfzvHhVjm2myVsevSk2yp5gNnVSBKfXw80shiCg9avW4RZPk bbvujWQ3AqduLrLVdUEW3a7fsP8z7xsJR75qH2VKwi5k0JyNtAuCNaIjm4sIwZf1 xt4vunaKjNdK1cMeoa1sOC5EYN3zaTFT8cEWBgPvjo9n3auvJ6OcSIsr+CFH3srF RoSkVNWnrAB2efNX4xPzDHwi7mFOFloNPVlkUFsJxY6NHHz4FuUcNA== =gNft -END PGP SIGNATURE- Accepted: cppopt_0.0.2-1.dsc to pool/main/c/cppopt/cppopt_0.0.2-1.dsc cppopt_0.0.2-1.tar.gz to pool/main/c/cppopt/cppopt_0.0.2-1.tar.gz libcppopt-dev_0.0.2-1_i386.deb to pool/main/c/cppopt/libcppopt-dev_0.0.2-1_i386.deb libcppopt0_0.0.2-1_i386.deb to pool/main/c/cppopt/libcppopt0_0.0.2-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libgnome 2.2.2-2 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 5 Jul 2003 10:28:33 +0200 Source: libgnome Binary: libgnome2-common libgnome2-0 libgnome2-doc libgnome2-dev Architecture: source all i386 Version: 2.2.2-2 Distribution: unstable Urgency: low Maintainer: Christian Marillat [EMAIL PROTECTED] Changed-By: Christian Marillat [EMAIL PROTECTED] Description: libgnome2-0 - The GNOME 2 library - runtime files libgnome2-common - The GNOME 2 library - common files libgnome2-dev - The GNOME 2 library - development files libgnome2-doc - The GNOME 2 library - documentation files Closes: 199197 Changes: libgnome (2.2.2-2) unstable; urgency=low . * Use x-terminal-emulator in schemas file as default (Closes: #199197) Files: 56874de08c171a4d501799ebedbcc6ea 952 devel optional libgnome_2.2.2-2.dsc a8602699fc2a8a894416e0838f49a1a2 6014 devel optional libgnome_2.2.2-2.diff.gz 84a98a023cda971d6f449fed5ae2a8e7 414448 libs optional libgnome2-common_2.2.2-2_all.deb 303b4b7597ccc88029da5499795baf1a 84194 doc optional libgnome2-doc_2.2.2-2_all.deb fea0358205cebeca5c35f80f81e73660 123034 libs optional libgnome2-0_2.2.2-2_i386.deb ac3c76925f570b51a95a38271bf8dcb0 88624 libdevel optional libgnome2-dev_2.2.2-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/CLLlB9xWPR9BuQcRAmryAJ43KguGOO/rZkmLSqdrwBhKDTkIbwCcCJi4 2vemDXZJo63yicGyspEisag= =7hbm -END PGP SIGNATURE- Accepted: libgnome2-0_2.2.2-2_i386.deb to pool/main/libg/libgnome/libgnome2-0_2.2.2-2_i386.deb libgnome2-common_2.2.2-2_all.deb to pool/main/libg/libgnome/libgnome2-common_2.2.2-2_all.deb libgnome2-dev_2.2.2-2_i386.deb to pool/main/libg/libgnome/libgnome2-dev_2.2.2-2_i386.deb libgnome2-doc_2.2.2-2_all.deb to pool/main/libg/libgnome/libgnome2-doc_2.2.2-2_all.deb libgnome_2.2.2-2.diff.gz to pool/main/libg/libgnome/libgnome_2.2.2-2.diff.gz libgnome_2.2.2-2.dsc to pool/main/libg/libgnome/libgnome_2.2.2-2.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted alien 8.33 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 6 Jul 2003 19:49:25 -0400 Source: alien Binary: alien Architecture: source all Version: 8.33 Distribution: unstable Urgency: low Maintainer: Joey Hess [EMAIL PROTECTED] Changed-By: Joey Hess [EMAIL PROTECTED] Description: alien - install non-native packages with dpkg Changes: alien (8.33) unstable; urgency=low . * Added a new j2sdk patch that does not rename the package. Files: 78c91f253e4e73f9c58d86d7b314073e 503 admin optional alien_8.33.dsc f96e7b7ecd68aa264e9cec2871268d61 84965 admin optional alien_8.33.tar.gz b3ae20a80d1cfd550c6de97ec25fdd46 115026 admin optional alien_8.33_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/CLXr2tp5zXiKP0wRArOCAJ9zhZvs/ZNg92B5On/e+vx4pd+EMgCfaeNq Aw0/im/LuRFJsmIvN1D/Cbg= =0LU1 -END PGP SIGNATURE- Accepted: alien_8.33.dsc to pool/main/a/alien/alien_8.33.dsc alien_8.33.tar.gz to pool/main/a/alien/alien_8.33.tar.gz alien_8.33_all.deb to pool/main/a/alien/alien_8.33_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted sawfish 1:1.3-3 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 7 Jul 2003 01:42:37 +0200 Source: sawfish Binary: sawfish-gnome sawfish sawfish-lisp-source Architecture: source i386 all Version: 1:1.3-3 Distribution: unstable Urgency: low Maintainer: Christian Marillat [EMAIL PROTECTED] Changed-By: Christian Marillat [EMAIL PROTECTED] Description: sawfish- A window manager for X11 sawfish-gnome - Dummy package providing sawfish-gnome sawfish-lisp-source - Sawfish lisp files Closes: 197718 Changes: sawfish (1:1.3-3) unstable; urgency=low . * New patch: restart sawfish when he crash. This work only with gnome-session and you need to edit your session configuration to change the style option to restart (Closes: #197718) Files: 685ed4fdefeeb69f9ed239e171fdf6c7 801 x11 optional sawfish_1.3-3.dsc 6669059bdeed106f302b9c103aeee804 33977 x11 optional sawfish_1.3-3.diff.gz 1755c96e662bb6988b36af42ec4f075f 222064 x11 optional sawfish-lisp-source_1.3-3_all.deb 899a38dba955365b1f290e6b91825e8e 40324 gnome optional sawfish-gnome_1.3-3_all.deb bb206e74148ab900f921d58167ad7800 1352782 x11 optional sawfish_1.3-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/CLUjB9xWPR9BuQcRAkWnAJ9V//gGARhhX327Ouawq5TOdQyRcACfXI7B 3kreDDQIJeOeEJHwe+2Jarg= =dYRi -END PGP SIGNATURE- Accepted: sawfish-gnome_1.3-3_all.deb to pool/main/s/sawfish/sawfish-gnome_1.3-3_all.deb sawfish-lisp-source_1.3-3_all.deb to pool/main/s/sawfish/sawfish-lisp-source_1.3-3_all.deb sawfish_1.3-3.diff.gz to pool/main/s/sawfish/sawfish_1.3-3.diff.gz sawfish_1.3-3.dsc to pool/main/s/sawfish/sawfish_1.3-3.dsc sawfish_1.3-3_i386.deb to pool/main/s/sawfish/sawfish_1.3-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gnome-libs 1.4.2-14 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 5 Jul 2003 22:59:08 +0200 Source: gnome-libs Binary: libgnomeui32 libgtkxmhtml-dev gnome-dev-doc libgtkxmhtml1 libzvt2 libgnome32 libgnomesupport0 libart2 libgnorbagtk0 gnome-libs-data libgnorba-dev libgnorba27 libzvt-dev gnome-bin libart-dev libgnome-dev Architecture: source all i386 Version: 1.4.2-14 Distribution: unstable Urgency: low Maintainer: Christian Marillat [EMAIL PROTECTED] Changed-By: Christian Marillat [EMAIL PROTECTED] Description: gnome-bin - Miscellaneous binaries used by GNOME gnome-dev-doc - GNOME developers documentation gnome-libs-data - Data for GNOME libraries libart-dev - The GNOME canvas widget - development files libart2- The GNOME canvas widget - runtime files libgnome-dev - The GNOME libraries -- development package libgnome32 - The GNOME libraries libgnomesupport0 - The GNOME libraries (Support libraries) libgnomeui32 - The GNOME libraries (User Interface) libgnorba-dev - GNOME CORBA services -- development package libgnorba27 - GNOME CORBA services libgnorbagtk0 - GNOME CORBA services (Gtk bindings) libgtkxmhtml-dev - The GNOME gtkxmhtml (HTML) widget -- development package libgtkxmhtml1 - The GNOME gtkxmhtml (HTML) widget libzvt-dev - The GNOME zvt (zterm) widget -- development package libzvt2- The GNOME zvt (zterm) widget Closes: 193344 199165 Changes: gnome-libs (1.4.2-14) unstable; urgency=low . * Move libraries packages to oldlibs section * Add -lutil in patch 11_libzvt2 (Closes: #199165) * New patch 14_mime-magic to add more audio entries in /etc/mime-magic (Closes: #193344) Files: 0b87e285f9e60ce813aecf660fe7c8d2 1148 oldlibs optional gnome-libs_1.4.2-14.dsc 8005414fe28b91e237e7cd14be8ac29c 21215 oldlibs optional gnome-libs_1.4.2-14.diff.gz 46e2ebd803c531edd7c4cfa4c1fc0299 322086 gnome optional gnome-libs-data_1.4.2-14_all.deb 5df7e6ff5b8fd2a0e698cc089ceea570 520880 doc optional gnome-dev-doc_1.4.2-14_all.deb 0d8282427c34d334deb27f55967fcc21 77928 oldlibs optional libgnome32_1.4.2-14_i386.deb 25a3542c2986cf2e7cd28933e617db90 432082 oldlibs optional libgnomeui32_1.4.2-14_i386.deb 4ab92da0b58ee9a9cda3c140144d2ff6 24824 oldlibs optional libgnomesupport0_1.4.2-14_i386.deb a80eea1a83f4f69a5749d414bf310b67 565610 libdevel optional libgnome-dev_1.4.2-14_i386.deb 01630fd7289fad0b9e141c43ee5ab4d1 47010 oldlibs optional libart2_1.4.2-14_i386.deb da108ed8463f9047629949747269dad2 44822 libdevel optional libart-dev_1.4.2-14_i386.deb 311af40175af4ee71fcfdc90fac3d22d 53462 oldlibs optional libgnorba27_1.4.2-14_i386.deb 2e7045ea35053317dad321ddc1acc121 43904 oldlibs optional libgnorbagtk0_1.4.2-14_i386.deb 5a8dd207684e826a88ebf5848baac801 34432 libdevel optional libgnorba-dev_1.4.2-14_i386.deb 9e287d82817c932ad26209d905f3394e 95042 oldlibs optional libzvt2_1.4.2-14_i386.deb a048ba23262b2e5e7bd533f25b43f306 49284 libdevel optional libzvt-dev_1.4.2-14_i386.deb 7b5e604546538e9607fce626cea855d1 179640 oldlibs optional libgtkxmhtml1_1.4.2-14_i386.deb f64697f36abe58f0d62dfaad71d0d485 239698 libdevel optional libgtkxmhtml-dev_1.4.2-14_i386.deb 90a3354b41d616cffd90969de0cc15b5 92984 gnome optional gnome-bin_1.4.2-14_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/CLkKB9xWPR9BuQcRAlZDAJ9+Ky3x7Jcd/u8jZ1Ie97oQZuqm7wCeL3h5 sGyWPzZKDbQckXmKbkLir4E= =5CJb -END PGP SIGNATURE- Accepted: gnome-bin_1.4.2-14_i386.deb to pool/main/g/gnome-libs/gnome-bin_1.4.2-14_i386.deb gnome-dev-doc_1.4.2-14_all.deb to pool/main/g/gnome-libs/gnome-dev-doc_1.4.2-14_all.deb gnome-libs-data_1.4.2-14_all.deb to pool/main/g/gnome-libs/gnome-libs-data_1.4.2-14_all.deb gnome-libs_1.4.2-14.diff.gz to pool/main/g/gnome-libs/gnome-libs_1.4.2-14.diff.gz gnome-libs_1.4.2-14.dsc to pool/main/g/gnome-libs/gnome-libs_1.4.2-14.dsc libart-dev_1.4.2-14_i386.deb to pool/main/g/gnome-libs/libart-dev_1.4.2-14_i386.deb libart2_1.4.2-14_i386.deb to pool/main/g/gnome-libs/libart2_1.4.2-14_i386.deb libgnome-dev_1.4.2-14_i386.deb to pool/main/g/gnome-libs/libgnome-dev_1.4.2-14_i386.deb libgnome32_1.4.2-14_i386.deb to pool/main/g/gnome-libs/libgnome32_1.4.2-14_i386.deb libgnomesupport0_1.4.2-14_i386.deb to pool/main/g/gnome-libs/libgnomesupport0_1.4.2-14_i386.deb libgnomeui32_1.4.2-14_i386.deb to pool/main/g/gnome-libs/libgnomeui32_1.4.2-14_i386.deb libgnorba-dev_1.4.2-14_i386.deb to pool/main/g/gnome-libs/libgnorba-dev_1.4.2-14_i386.deb libgnorba27_1.4.2-14_i386.deb to pool/main/g/gnome-libs/libgnorba27_1.4.2-14_i386.deb libgnorbagtk0_1.4.2-14_i386.deb to pool/main/g/gnome-libs/libgnorbagtk0_1.4.2-14_i386.deb libgtkxmhtml-dev_1.4.2-14_i386.deb to pool/main/g/gnome-libs/libgtkxmhtml-dev_1.4.2-14_i386.deb libgtkxmhtml1_1.4.2-14_i386.deb to pool/main/g/gnome-libs/libgtkxmhtml1_1.4.2-14_i386.deb libzvt-dev_1.4.2-14_i386.deb to pool/main/g/gnome-libs/libzvt-dev_1.4.2-14_i386.deb libzvt2_1.4.2-14_i386.deb to
Accepted python-qt3 3.7-1 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 6 Jul 2003 19:53:05 +0100 Source: python-qt3 Binary: python-qt3-doc python2.2-qt3c102 python2.1-qtext python-qt-dev python-qtext pyuic3 python2.2-qtext python-qt3 python2.1-qt3c102 pyqt-tools Architecture: source all i386 Version: 3.7-1 Distribution: unstable Urgency: low Maintainer: Ricardo Javier Cardenes Medina [EMAIL PROTECTED] Changed-By: Ricardo Javier Cardenes Medina [EMAIL PROTECTED] Description: pyqt-tools - pyuic and pylupdate for Qt3 python-qt-dev - Qt bindings for Python - Development files python-qt3 - Qt3 bindings for Python (default version) python-qt3-doc - Qt bindings for Python - Documentation and examples python-qtext - Qt extensions for PyQt (default version) python2.1-qt3c102 - Qt3 bindings for Python python2.1-qtext - Qt extensions for PyQt python2.2-qt3c102 - Qt3 bindings for Python python2.2-qtext - Qt extensions for PyQt pyuic3 - pyuic for Qt3 - dummy package Closes: 198930 Changes: python-qt3 (3.7-1) unstable; urgency=low . * New upstream release. Closes: Bug#198930 * Modified to comply with Debian Policy v3.5.10 * Use of dpatch for some arch-specific build-time changes Files: 802f28d35dd3a275f16b84d37a5925ee 1055 interpreters optional python-qt3_3.7-1.dsc 33be307332bb5fadafbf426f824e5213 734515 interpreters optional python-qt3_3.7.orig.tar.gz e494479f3ddb93ea9c68a4f0e03f7e4d 10910 interpreters optional python-qt3_3.7-1.diff.gz a0b51e991cae42eee5121c4b672d0fae 33358 interpreters optional python-qt3_3.7-1_all.deb 8d2c1cd95eb2d2bd4f1a4af3e3769164 22536 interpreters optional python-qtext_3.7-1_all.deb 879fb6e9f68c0d9660b511e9717958e0 22768 interpreters optional pyuic3_3.7-1_all.deb 1f7efa5f7725cee4bb811b592bfbce20 208076 interpreters optional python-qt-dev_3.7-1_all.deb 81fb3ad46cf2918cd78dc201572242ee 189470 doc optional python-qt3-doc_3.7-1_all.deb 918b96cd6945d476d0b17888552466a6 2010302 interpreters optional python2.1-qt3c102_3.7-1_i386.deb 70d0c0376eb595e3e5fd6be183f31a69 2011826 interpreters optional python2.2-qt3c102_3.7-1_i386.deb 9201cb728d343741bfb48bfe5d5861b2 140720 interpreters optional python2.1-qtext_3.7-1_i386.deb 62b43ec74cd07c9af42fee944cee72d0 140846 interpreters optional python2.2-qtext_3.7-1_i386.deb 73f2b1d6f6d44efe0571688d0a9baeaf 125712 interpreters optional pyqt-tools_3.7-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/CLbuHkQIZYcutOURAhnuAKCXfhVgCyUMhrOCcfAdIPm8GVxNYwCcDK18 joQ+LZhQF3Kfl8PkHdPXCYo= =SqRi -END PGP SIGNATURE- Accepted: pyqt-tools_3.7-1_i386.deb to pool/main/p/python-qt3/pyqt-tools_3.7-1_i386.deb python-qt-dev_3.7-1_all.deb to pool/main/p/python-qt3/python-qt-dev_3.7-1_all.deb python-qt3-doc_3.7-1_all.deb to pool/main/p/python-qt3/python-qt3-doc_3.7-1_all.deb python-qt3_3.7-1.diff.gz to pool/main/p/python-qt3/python-qt3_3.7-1.diff.gz python-qt3_3.7-1.dsc to pool/main/p/python-qt3/python-qt3_3.7-1.dsc python-qt3_3.7-1_all.deb to pool/main/p/python-qt3/python-qt3_3.7-1_all.deb python-qt3_3.7.orig.tar.gz to pool/main/p/python-qt3/python-qt3_3.7.orig.tar.gz python-qtext_3.7-1_all.deb to pool/main/p/python-qt3/python-qtext_3.7-1_all.deb python2.1-qt3c102_3.7-1_i386.deb to pool/main/p/python-qt3/python2.1-qt3c102_3.7-1_i386.deb python2.1-qtext_3.7-1_i386.deb to pool/main/p/python-qt3/python2.1-qtext_3.7-1_i386.deb python2.2-qt3c102_3.7-1_i386.deb to pool/main/p/python-qt3/python2.2-qt3c102_3.7-1_i386.deb python2.2-qtext_3.7-1_i386.deb to pool/main/p/python-qt3/python2.2-qtext_3.7-1_i386.deb pyuic3_3.7-1_all.deb to pool/main/p/python-qt3/pyuic3_3.7-1_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted debhelper 4.1.52 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 6 Jul 2003 20:28:27 -0400 Source: debhelper Binary: debhelper Architecture: source all Version: 4.1.52 Distribution: unstable Urgency: low Maintainer: Joey Hess [EMAIL PROTECTED] Changed-By: Joey Hess [EMAIL PROTECTED] Description: debhelper - helper programs for debian/rules Changes: debhelper (4.1.52) unstable; urgency=low . * dh_clean: Clean the *.debhelper temp files on a per-package basis, in case dh_clean is run on one package at a time. * Removed the debian/substvars removal code entirely. It was only there to deal with half-built trees built with debhelper 3.0.30 Files: 15d83b0726b243cab9d02f11b70d172d 573 devel optional debhelper_4.1.52.dsc c5e079a253d5d6890240df6964708219 102574 devel optional debhelper_4.1.52.tar.gz 6eceddf253ccdbc5bddc4b619deca2e8 214986 devel optional debhelper_4.1.52_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/CL8X2tp5zXiKP0wRAjOTAKDAwAcn4cFEEKRuDLsUOMKj1ipjmQCgw0BE cbw7hwc77lNlkB++uxotKMY= =Rs4P -END PGP SIGNATURE- Accepted: debhelper_4.1.52.dsc to pool/main/d/debhelper/debhelper_4.1.52.dsc debhelper_4.1.52.tar.gz to pool/main/d/debhelper/debhelper_4.1.52.tar.gz debhelper_4.1.52_all.deb to pool/main/d/debhelper/debhelper_4.1.52_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted postfix 2.0.13-20030706-1 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 6 Jul 2003 18:46:07 -0600 Source: postfix Binary: postfix-tls postfix-pcre postfix postfix-pgsql postfix-doc postfix-ldap postfix-dev postfix-mysql Architecture: source all i386 Version: 2.0.13-20030706-1 Distribution: experimental Urgency: low Maintainer: LaMont Jones [EMAIL PROTECTED] Changed-By: LaMont Jones [EMAIL PROTECTED] Description: postfix- A high-performance mail transport agent postfix-dev - Postfix loadable modules development environment postfix-doc - Postfix documentation postfix-ldap - LDAP map support for Postfix postfix-mysql - MYSQL map support for Postfix postfix-pcre - PCRE map support for Postfix postfix-pgsql - PGSQL map support for Postfix postfix-tls - TLS and SASL support for Postfix Changes: postfix (2.0.13-20030706-1) experimental; urgency=low . * New upstream version Files: 8f3450f07db23ff528d87f541bc42084 862 mail extra postfix_2.0.13-20030706-1.dsc 81faeac4c0514183f335506f36b8edce 1449131 mail extra postfix_2.0.13-20030706.orig.tar.gz cbebc8934919daa8c5f9a5d2a4b5ea22 485060 mail extra postfix_2.0.13-20030706-1.diff.gz 43d6af7437acef1295b3bd56f7b39215 620298 mail extra postfix_2.0.13-20030706-1_i386.deb 0d56e4d612e128d9769c12007d83a9ed 29908 mail extra postfix-ldap_2.0.13-20030706-1_i386.deb 7ff50b8518edc3fdfef26441c3b3a2f4 27482 mail extra postfix-pcre_2.0.13-20030706-1_i386.deb 5a7fbf08ef5a9a4ea3a2f8f595fafcae 27542 mail extra postfix-mysql_2.0.13-20030706-1_i386.deb 2714e6466aa1583fc786bf043bd62807 27844 mail extra postfix-pgsql_2.0.13-20030706-1_i386.deb fc3f2653087ed692dc191cdb367e8c89 135838 mail extra postfix-tls_2.0.13-20030706-1_i386.deb f7ae1f2e3ae4416f512db79a56fa90a7 89872 devel extra postfix-dev_2.0.13-20030706-1_all.deb 986fddea046e3c1093359795684a8360 619694 doc extra postfix-doc_2.0.13-20030706-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/CMR8zN/kmwoKyScRAq1JAJ9xJMrfKClHBH3eLUSSyvfUxIVyjQCeO39u NTDIZ380dhp2cvFExQMf0Ms= =oyag -END PGP SIGNATURE- Accepted: postfix-dev_2.0.13-20030706-1_all.deb to pool/main/p/postfix/postfix-dev_2.0.13-20030706-1_all.deb postfix-doc_2.0.13-20030706-1_all.deb to pool/main/p/postfix/postfix-doc_2.0.13-20030706-1_all.deb postfix-ldap_2.0.13-20030706-1_i386.deb to pool/main/p/postfix/postfix-ldap_2.0.13-20030706-1_i386.deb postfix-mysql_2.0.13-20030706-1_i386.deb to pool/main/p/postfix/postfix-mysql_2.0.13-20030706-1_i386.deb postfix-pcre_2.0.13-20030706-1_i386.deb to pool/main/p/postfix/postfix-pcre_2.0.13-20030706-1_i386.deb postfix-pgsql_2.0.13-20030706-1_i386.deb to pool/main/p/postfix/postfix-pgsql_2.0.13-20030706-1_i386.deb postfix-tls_2.0.13-20030706-1_i386.deb to pool/main/p/postfix/postfix-tls_2.0.13-20030706-1_i386.deb postfix_2.0.13-20030706-1.diff.gz to pool/main/p/postfix/postfix_2.0.13-20030706-1.diff.gz postfix_2.0.13-20030706-1.dsc to pool/main/p/postfix/postfix_2.0.13-20030706-1.dsc postfix_2.0.13-20030706-1_i386.deb to pool/main/p/postfix/postfix_2.0.13-20030706-1_i386.deb postfix_2.0.13-20030706.orig.tar.gz to pool/main/p/postfix/postfix_2.0.13-20030706.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted zsh 4.0.7-4 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 6 Jul 2003 16:47:16 -0400 Source: zsh Binary: zsh zsh-static zsh-doc Architecture: source all Version: 4.0.7-4 Distribution: unstable Urgency: medium Maintainer: Clint Adams [EMAIL PROTECTED] Changed-By: Clint Adams [EMAIL PROTECTED] Description: zsh- A shell with lots of features zsh-doc- zsh documentation - info/HTML format zsh-static - A shell with lots of features (static link) Closes: 199638 200257 Changes: zsh (4.0.7-4) unstable; urgency=medium . * Fix from Oliver to make subversion completion suck less. closes: #199638. * New completion function for debsign from Matt Zimmerman. closes: #200257. Files: 1a30809635aa4789a84639c68af049db 668 shells optional zsh_4.0.7-4.dsc 19717b9fad82127ced8e94c9df941d52 50235 shells optional zsh_4.0.7-4.diff.gz 34b65fb7d296d042e857457e540eb649 570212 shells optional zsh-doc_4.0.7-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Debian! iD8DBQE/CN2G5m0u66uWM3ARAqr7AKCHrpSoDOtGVFoiZpYlUBZNHZF/XACeNFbS 3B1qr/xVejDgf8TPqjllKh4= =m028 -END PGP SIGNATURE- Accepted: zsh-doc_4.0.7-4_all.deb to pool/main/z/zsh/zsh-doc_4.0.7-4_all.deb zsh_4.0.7-4.diff.gz to pool/main/z/zsh/zsh_4.0.7-4.diff.gz zsh_4.0.7-4.dsc to pool/main/z/zsh/zsh_4.0.7-4.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted ftpgrab 0.1.2r-6 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 4 Jul 2003 16:43:57 -0400 Source: ftpgrab Binary: ftpgrab Architecture: source i386 Version: 0.1.2r-6 Distribution: unstable Urgency: low Maintainer: Christian T. Steigies [EMAIL PROTECTED] Changed-By: Christian T. Steigies [EMAIL PROTECTED] Description: ftpgrab- file mirroring utility Changes: ftpgrab (0.1.2r-6) unstable; urgency=low . * rebuild with gcc-3.3 * add install target to upstream Makefile * use cdbs * updated Standards-Version Files: 850ce617c2cbe8f4b74b9702191270d8 575 net optional ftpgrab_0.1.2r-6.dsc 36c3b6c128dd53306c20543bf9646d3b 4927 net optional ftpgrab_0.1.2r-6.diff.gz ab6a66e78174a5f6c30b430ab300c757 42930 net optional ftpgrab_0.1.2r-6_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/CNwchWcuXd2lEoARAvm+AKDQECU8aMVLUMFNJh2H4U0kTUoAjACgvm0i kdr5A57P4VLn3dmp/MrtD/8= =ZIbO -END PGP SIGNATURE- Accepted: ftpgrab_0.1.2r-6.diff.gz to pool/main/f/ftpgrab/ftpgrab_0.1.2r-6.diff.gz ftpgrab_0.1.2r-6.dsc to pool/main/f/ftpgrab/ftpgrab_0.1.2r-6.dsc ftpgrab_0.1.2r-6_i386.deb to pool/main/f/ftpgrab/ftpgrab_0.1.2r-6_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fftw3 3.0.1-1 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Format: 1.7 Date: Sun, 6 Jul 2003 17:14:38 -0400 Source: fftw3 Binary: fftw3 fftw3-doc fftw3-dev Architecture: source i386 all Version: 3.0.1-1 Distribution: unstable Urgency: low Maintainer: James A. Treacy [EMAIL PROTECTED] Changed-By: James A. Treacy [EMAIL PROTECTED] Description: fftw3 - Library for computing Fast Fourier Transforms fftw3-dev - Library for computing Fast Fourier Transforms fftw3-doc - Documentation for fftw version 3 Closes: 197637 Changes: fftw3 (3.0.1-1) unstable; urgency=low . * New upstream source. * fftw3-dev depends on pkg-config. Closes: #197637 Files: 083188d5c8d48db5dffa150847ed5149 683 - optional fftw3_3.0.1-1.dsc 76cd21ecc9a7bed6343566c473c36477 1946361 - optional fftw3_3.0.1.orig.tar.gz 55d8031081ed19614caa8c675296e0fe 162348 - optional fftw3_3.0.1-1.diff.gz db611a73f2b1ea6a907c7c72eb9a44c4 217920 doc optional fftw3-doc_3.0.1-1_all.deb bb950bc615bc1b544ec1349ebea933d8 936634 libs optional fftw3_3.0.1-1_i386.deb 0dde80d136722d9b6c6417d05d4c6205 1249720 libdevel optional fftw3-dev_3.0.1-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iQCVAwUBPwjGSw9y7Te6Cn61AQHEdQQAl1npQ4tqUlhtWrnL7FOmE/Slk8loGuGU qhqDWn2tq6u63Iy6/5ctuqyFQgk/QR4827ut+dO+7Nr4vevNH4TKWEF2zFa6pqkm FniBUbXkUyoQ5L4siSp77M1zccExq9mIL9PAUFHC9l3k0zkeLb3iRQEAytbHfVat xxfwKZZtUgs= =fErC -END PGP SIGNATURE- Accepted: fftw3-dev_3.0.1-1_i386.deb to pool/main/f/fftw3/fftw3-dev_3.0.1-1_i386.deb fftw3-doc_3.0.1-1_all.deb to pool/main/f/fftw3/fftw3-doc_3.0.1-1_all.deb fftw3_3.0.1-1.diff.gz to pool/main/f/fftw3/fftw3_3.0.1-1.diff.gz fftw3_3.0.1-1.dsc to pool/main/f/fftw3/fftw3_3.0.1-1.dsc fftw3_3.0.1-1_i386.deb to pool/main/f/fftw3/fftw3_3.0.1-1_i386.deb fftw3_3.0.1.orig.tar.gz to pool/main/f/fftw3/fftw3_3.0.1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted grub 0.93+cvs20030624-3 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 7 Jul 2003 14:03:21 +1000 Source: grub Binary: grub grub-doc Architecture: source i386 all Version: 0.93+cvs20030624-3 Distribution: unstable Urgency: low Maintainer: Jason Thomas [EMAIL PROTECTED] Changed-By: Jason Thomas [EMAIL PROTECTED] Description: grub - GRand Unified Bootloader grub-doc - Documentation for GRand Unified Bootloader Closes: 200282 Changes: grub (0.93+cvs20030624-3) unstable; urgency=low . * Updated mkbimage, from upstream plus patch from Robert Millan (closes: #200282) Files: 20861bac279705c31613b0be6dd10e15 646 admin optional grub_0.93+cvs20030624-3.dsc 6dd720f3d37d77387074d7c9d0f905d3 25678 admin optional grub_0.93+cvs20030624-3.diff.gz 8c4ae270103af0598855d2b9c596 243548 doc optional grub-doc_0.93+cvs20030624-3_all.deb 443a95bbb34bf3dae163fdbee62c76f2 276216 admin optional grub_0.93+cvs20030624-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/CPFk7cYwRJJSiL4RAitiAJ0Ye+szg1ZwHA8XJJQfn4kv2lG2aQCfZpGf QE4cxliUnYbBBi5uGPmx2CM= =Wmu+ -END PGP SIGNATURE- Accepted: grub-doc_0.93+cvs20030624-3_all.deb to pool/main/g/grub/grub-doc_0.93+cvs20030624-3_all.deb grub_0.93+cvs20030624-3.diff.gz to pool/main/g/grub/grub_0.93+cvs20030624-3.diff.gz grub_0.93+cvs20030624-3.dsc to pool/main/g/grub/grub_0.93+cvs20030624-3.dsc grub_0.93+cvs20030624-3_i386.deb to pool/main/g/grub/grub_0.93+cvs20030624-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted yaz 2.0.2-3 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 6 Jul 2003 22:27:00 -0600 Source: yaz Binary: yaz-doc libyaz-dev yaz libyaz Architecture: source all i386 Version: 2.0.2-3 Distribution: unstable Urgency: low Maintainer: Eric Schwartz [EMAIL PROTECTED] Changed-By: Eric Schwartz [EMAIL PROTECTED] Description: libyaz - Z39.50 runtime libraries libyaz-dev - Z39.50 development files and header files yaz- Utility programs for Z39.50 toolkit yaz-doc- Documentation for YAZ Closes: 198977 Changes: yaz (2.0.2-3) unstable; urgency=low . * Fixed debian/yaz-doc.doc-base to reflect reality (closes: #198977) Files: c504523ce14fe150a697e0665ad109f5 671 devel optional yaz_2.0.2-3.dsc 024bd2efc038bea8204404e0f2fdac22 247184 devel optional yaz_2.0.2-3.diff.gz 85ebb4e9ff841dcb46cd1f78cb6af264 112356 devel optional yaz_2.0.2-3_i386.deb b7007fa2aac58be5a18cb4a1d1c0645a 192576 libs optional libyaz_2.0.2-3_i386.deb d6541750c3ecf031662e604360a64959 353084 devel optional libyaz-dev_2.0.2-3_i386.deb 8ef10e02165d89248a3063ab1627cff8 348948 doc optional yaz-doc_2.0.2-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/CPfDXXfiXWfzb/IRAnWNAJ9+hsAt56ctr2S4uDOjxit/YaHQWwCfRop2 /8DxSJD1K+h+MSMSpjgGVBQ= =jpvX -END PGP SIGNATURE- Accepted: libyaz-dev_2.0.2-3_i386.deb to pool/main/y/yaz/libyaz-dev_2.0.2-3_i386.deb libyaz_2.0.2-3_i386.deb to pool/main/y/yaz/libyaz_2.0.2-3_i386.deb yaz-doc_2.0.2-3_all.deb to pool/main/y/yaz/yaz-doc_2.0.2-3_all.deb yaz_2.0.2-3.diff.gz to pool/main/y/yaz/yaz_2.0.2-3.diff.gz yaz_2.0.2-3.dsc to pool/main/y/yaz/yaz_2.0.2-3.dsc yaz_2.0.2-3_i386.deb to pool/main/y/yaz/yaz_2.0.2-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Camisetas
On Sun, Jul 06, 2003 at 12:57:21PM +0200, Ismael Briones wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hola: Me gustaría comprar algunas de las camisetas (grises y negras) de la tanda anterior, de las que sobraron. Me gustaría poder comprarlas mañana Lunes en Madrid (7 Julio). Yo me desplazaría donde hiciese falta para comprarlas, eso no es problema. Las camisetas se van a poner a la venta a través del portal de hispalinux.net. Aún no las tienen allí pero, cuando las tengan, podrás pedir que te las envíen a donde quieras. También se venderan (si quedan) en el Congreso de Hispalinux en septeimbre. Alguein disponde ellas en Madrid para la venta. No hay nadie que tenga camisetas en Madrid (que yo sepa), lo siento. Un saludo Javi pgpF0x9fRKyKJ.pgp Description: PGP signature
