ftp-master.d.o, db.d.o down due to relocation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, As previously mentioned[1], newraff and newsamosa have lost their existing hosting and are being relocated. They've now been shutdown and are in the process of being FedEx-ed back to HP. Because a) that shouldn't take long and b) our inability to have a completely up-to-date backup[2], we've no plan to re-activate these services on other hosts in the mean time. This means that until Saturday (at the earliest) or Monday (at the latest), ftp-master and db will be unavailable. Thanks to all the offers of hosting we've received so far and I apologize for not having had the opportunity to reply to you all individually yet. Now that the machines have actually left, we'll be moving forward in terms of making a decision about where they'll end up. - -- James [1] http://lists.debian.org/debian-devel-announce/2005/06/msg00016.html [2] Due to various uninteresting and hysterical reasons, we weren't sure when exactly they were going to be shutdown. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.8 http://mailcrypt.sourceforge.net/ iQIVAwUBQuAjZdfD8TGrKpH1AQI6ChAAve3ea/2OWm6kjDiDiO1XvKg1eah2BEXq c8qT7wWLJM0yf54E0YZzy7gUB0uuQ8qeWAb1Y4iuPFWUYK8yc3AUV3KoSgIINVyd /Xff9T0ZnJWoUj3qS+rcjagBArRa+lh1oidv4qXgkvdu+6mNOVjzCPEgRRIrHsUO 0SCBVcYEv0IUEA82Zlk5wfxA7qXAA3vuk+cOtnWl2MLx1+iqO1hRFRJGEXa6JnlS 77lZO7Y6kSbah+eYO6erZdcUto94IUsNlWA9K7An9JwSFC97GkJj2godRPywfZ/U o6hf8fzXdrF7CXk04942HzynUKxPQPR+7/etGIKmOAez8cnyhCSI7hmma1XdLxi/ RRCilFMFB8gVmJ84FrmmSpex1pLRpcMlJeemkLcyYVwSe9LbbBA5ALsDBPNuJAV4 jnWOFq+hg2i6R5DnPAO43ulGkVu0kIanpM5Q33am5ypGbGs/72Yuc5UW60RDyIW+ Y3O+96ME5rG4BlJ/t47TfIo0Bhxm72UojJOu4AVK2Nzf71JY8fJFb4sYdhMOsS5E hm2JAocV2zB+GyxEU8d31NpuuiVTLIOVgMNQGy8DEgEBAvIyc+yof9pye9MPD8of D0ALhwTI9AUfwFJY6dgI1/FQeuMjI1tw2ww5jvd9SWmilOtIsFb4zqkASFQUcy8b ++x2CLHFU6s= =uZdR -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: aspell upgrade woes
On Tue, Jul 19, 2005 at 11:52:51PM -0700, Brian Nelson wrote: Steve Langasek [EMAIL PROTECTED] writes: On Tue, Jul 19, 2005 at 09:39:23PM -0700, Brian Nelson wrote: It's a C++ library and the ABI changed due to being compiled with GCC 4.0. [Actually, although it's written in C++, AFAIK it only exports a C interface so the transition may not have been necessary. I only realized this yesterday though and I'm not entirely sure a non-transition would be safe.] Heh. I've just confirmed this... As with libGLU, libaspell is used in enough places that there's a definite benefit to not breaking package compatibility unnecessarily. Since libaspell15c2's shlibs refer to libaspell15c2 (= 0.60), the only way to provide full compatibility is with two real packages. I would suggest restoring libaspell15, and creating a dummy libaspell15c2 package that depends on libaspell15 and can be dropped once everything has been rebuilt to use libaspell15 again; that would minimize the disruption caused by the flip-flopping of the lib name. Brian, if you agree, I'm happy to prepare a patch. Reintroducing the libaspell15 could cause problems with /usr/bin/aspell, since it actually goes outside the C API of libaspell and uses C++ linkage to some symbols. I fixed this bug (#307481) by making aspell-bin (or now just aspell) depend on the Source-Version of libaspell. However, that fix is not in the stable package of aspell. In stable, aspell-bin just depends on libaspell15 (= 0.60), so a partial upgrade of just libaspell15 would break aspell-bin. I suppose I could make the new libaspell15 conflict with the old aspell-bin, but that's rather clumsy and could make upgrades even more awkward. I'm not sure what the best thing to do would be. I'm sort of inclined to just stick with the transitioned libaspell15c2... Well, using libaspell15c2 will definitely cause some complexity on the upgrade path from sarge to etch. I don't know how much having libaspell15 conflict with aspell-bin ( $version) would do so. I suspect that it would be substantially less since there are only four packages in sarge which depend directly on aspell-bin or aspell, vs. 61 packages which depend on libaspell15 -- at a minimum, the worst-case scenario when conflicting with aspell-bin ( $version) looks substantially better. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: aspell upgrade woes
On Wed, Jul 20, 2005 at 09:52:13AM +0200, Goswin von Brederlow wrote: Reintroducing the libaspell15 could cause problems with /usr/bin/aspell, since it actually goes outside the C API of libaspell and uses C++ linkage to some symbols. I fixed this bug (#307481) by making aspell-bin (or now just aspell) depend on the Source-Version of libaspell. However, that fix is not in the stable package of aspell. In stable, aspell-bin just depends on libaspell15 (= 0.60), so a partial upgrade of just libaspell15 would break aspell-bin. I suppose I could make the new libaspell15 conflict with the old aspell-bin, but that's rather clumsy and could make upgrades even more awkward. Why? This is exactly what a versioned conflict is for. That doesn't mean the packaging tools handle the case gracefully (by user standards). Most of the upgrade problems people saw with woody-sarge had to do precisely with these conflicts that policy counter-recommends. The packages have to be upgraded as pair and apt/dpkg will hapily do that. Or, apt will happily *remove* the conflicted-with package instead... But anyway, see my previous message for why the conflict with aspell may be less problematic on upgrades. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: aspell upgrade woes
On Wed, Jul 20, 2005 at 09:28:22AM -0400, David Nusinow wrote: On Tue, Jul 19, 2005 at 09:39:23PM -0700, Brian Nelson wrote: Uh... no... http://lists.debian.org/debian-devel-announce/2005/07/msg1.html It's a C++ library and the ABI changed due to being compiled with GCC 4.0. [Actually, although it's written in C++, AFAIK it only exports a C interface so the transition may not have been necessary. I only realized this yesterday though and I'm not entirely sure a non-transition would be safe.] Christ, not another one. Is there any sort of automated way that we can check for these sorts of libraries before messing things up again? I won't be doing it again for libGLU obviously, but some sort of script or large-scale automated check of the archive would potentially go a long way. The best heuristic I can come up with so far is dpkg -x $package tmpdir \ grep -rE '\b(use|class|template)\b|::|#include[[:space:]]+[a-zA-Z_/]+' tmpdir/usr/include That may turn up false positives due to the use of common English words, but I can't think of a way it could turn up false negatives. At any rate, libGLU is still a false positive by this standard, so it really takes someone who understands the ABI stuff to examine the occurrences of these terms in each header. It also doesn't address the possible problem of packages accessing private symbols from the library. If we could get library authors/maintainers to start using gcc -Wl,--version-script,file with list of symbols to export, then we'd be able to use the much more reliable method of feeding the list of symbols defined in the lib to c++filt and looking for '::' in the output. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: aspell upgrade woes
On Thu, Jul 21, 2005 at 01:15:55AM -0700, Steve Langasek wrote: The best heuristic I can come up with so far is dpkg -x $package tmpdir \ grep -rE '\b(use|class|template)\b|::|#include[[:space:]]+[a-zA-Z_/]+' tmpdir/usr/include That may turn up false positives due to the use of common English words, but I can't think of a way it could turn up false negatives. At any rate, libGLU is still a false positive by this standard, so it really takes someone who understands the ABI stuff to examine the occurrences of these terms in each header. What is this 'use'? C++ doesn't have that as a keyword. Do you mean 'using'? -- Petri Latvala signature.asc Description: Digital signature
Re: aspell upgrade woes
On Thu, Jul 21, 2005 at 11:30:58AM +0300, Petri Latvala wrote: On Thu, Jul 21, 2005 at 01:15:55AM -0700, Steve Langasek wrote: The best heuristic I can come up with so far is dpkg -x $package tmpdir \ grep -rE '\b(use|class|template)\b|::|#include[[:space:]]+[a-zA-Z_/]+' tmpdir/usr/include That may turn up false positives due to the use of common English words, but I can't think of a way it could turn up false negatives. At any rate, libGLU is still a false positive by this standard, so it really takes someone who understands the ABI stuff to examine the occurrences of these terms in each header. What is this 'use'? C++ doesn't have that as a keyword. Do you mean 'using'? Sorry, yes. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: Reopening bug closed due to SPAM
Javier Fernández-Sanguino Peña [EMAIL PROTECTED] writes: reopen 209891 thanks If spam e-mail is going to start closing our Bugs in the BTS then we should start thinking about implementing authentication checks in the BTS... like for example: do not allow control messages or -close messages with no attached (valid) GPG/PGP signatures (from a valid developer?) Regards Javier NMs and most submitters aren't in the keyring so they would have a hard time managing bugs if a DD signature is required. And don't forget the DAK closing bugs on uploads. The archive key would have to be allowed to sign too. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Reopening bug closed due to SPAM
On 7/21/05, Javier Fernández-Sanguino Peña [EMAIL PROTECTED] wrote: If spam e-mail is going to start closing our Bugs in the BTS then we should start thinking about implementing authentication checks in the BTS... like for example: do not allow control messages or -close messages with no attached (valid) GPG/PGP signatures (from a valid developer?) As it was already requested, please don't make this a DD specific thing. GPG signing is not that bad, but making it DD specific is really a BAD thing. (keep in mind, there are non-DD maintainers, who wouldn't be able to close their own bugs!!) -- Besos, Marga
Re: Reopening bug closed due to SPAM
* Javier Fernández-Sanguino Peña [Thu, 21 Jul 2005 00:31:48 +0200]: If spam e-mail is going to start closing our Bugs in the BTS then we should start thinking about implementing authentication checks in the BTS... like for example: do not allow control messages or -close messages with no attached (valid) GPG/PGP signatures (from a valid developer?) I see much more feasible to require a pseudo-header: less cumbersome, higher probability of getting implemented, and more in accordance with the philosophy of our BTS. And such header is now needed to make a versioned closes, so it doesn't sound too disruptive to require it for every mail to -done (at least the Source: one, Source-Version could be optional). Cheers, -- Adeodato Simó EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621 Hanlon's Razor: Never attribute to malice that which is adequately explained by stupidity. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Reopening bug closed due to SPAM
On Thu, Jul 21, 2005 at 12:31:48AM +0200, Javier Fernández-Sanguino Peña wrote: If spam e-mail is going to start closing our Bugs in the BTS then we Start? It used to happen a lot; it's much less common nowadays. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Reopening bug closed due to SPAM
On Thu, Jul 21, 2005 at 11:36:15AM +0200, Adeodato Simó wrote: And such header is now needed to make a versioned closes, so it doesn't sound too disruptive to require it for every mail to -done (at least the Source: one, Source-Version could be optional). It's possible this may happen in the future, but I don't want to do it immediately; such changes are better made gradually so that people don't have to get used to too many new things at once. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Reopening bug closed due to SPAM
On 21/07/05, Adeodato Simó [EMAIL PROTECTED] wrote: * Javier Fernández-Sanguino Peña [Thu, 21 Jul 2005 00:31:48 +0200]: If spam e-mail is going to start closing our Bugs in the BTS then we should start thinking about implementing authentication checks in the BTS... like for example: do not allow control messages or -close messages with no attached (valid) GPG/PGP signatures (from a valid developer?) I see much more feasible to require a pseudo-header: less cumbersome, higher probability of getting implemented, and more in accordance with the philosophy of our BTS. And such header is now needed to make a versioned closes, so it doesn't sound too disruptive to require it for every mail to -done (at least the Source: one, Source-Version could be optional). And how about a nice header for -done which is something to the effect of 'mark as spam archive now prevent replies etc unless reopened', or let us tag bugs as 'spam' (which would also be an alias for close) and on the bug summary pages instead of all the spam bugs on package pages (mainly 'general' i'd say) it'd appear in it's own little section, and can autoarchive in 28 days without mixing with other bugs... My two cents Cheers, -- Adeodato Simó EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621 Hanlon's Razor: Never attribute to malice that which is adequately explained by stupidity. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- N Jones Blogging @ http://nigelj.blogspot.com Proud Debian FOSS User Debian Maintainer of: html2ps ipkungfu
Bug#319330: ITP: mipe -- [Biology] Tools for storing data on PCR experiments
Package: wnpp Severity: wishlist Owner: Steffen Moeller [EMAIL PROTECTED] * Package name: mipe Version : 1.1 Upstream Author : Jan Aerts [EMAIL PROTECTED] * URL : http://mipe.sourceforge.net * License : LGPL Description : [Biology] Tool to store data on PCR-derived experiments To provide a standard format to exchange and/or storage of all information associated with PCR experiments using a flat text file. This will: * allow for exchange of PCR data between researchers/laboratories * enable traceability of the data * prevent problems when submitting data to dbSTS or dbSNP * enable the writing of standard scripts to extract data (e.g. * provide a list of PCR primers, SNP positions or haplotypes for different animals) . Although this tool can be used for data storage, it's primary focus should be data exchange. For larger reporisitories, relational databases are more appropriate for storage of these data. The MIPE format could then be used as a standard format to import into and/or export from these databases. . Homepage: http://mipe.sourceforge.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Reopening bug closed due to SPAM
On Thu, Jul 21, 2005 at 11:16:45PM +1200, Nigel Jones wrote: And how about a nice header for -done which is something to the effect of 'mark as spam archive now prevent replies etc unless reopened', I think that's far more prone to abuse than spams closing bugs. Archiving is deliberately irreversible except by [EMAIL PROTECTED], so it should not be so easy to cause immediate archiving. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#319334: ITP: ng-spice -- Mixed-level/mixed-signal electronic circuit simulator
Package: wnpp Severity: wishlist Owner: Gerasimos Melissaratos [EMAIL PROTECTED] There may be a licence problem, so I'm pasting from the package's licence: Permission to use, copy, modify, and distribute this software and its documentation for educational, research and non-profit purposes, without fee, and without a written agreement is hereby granted, provided that the above copyright notice, this paragraph and the following three paragraphs appear in all copies. If it's ok, even for the non-free section, I'd like to get on with it. PS: I submitted yesterday the same, but I got no response due to serious disk failure of the eexi.gr mailserver. Sorry for that. * Package name : ng-spice Version : x.y.z Upstream Author : Name [EMAIL PROTECTED] * URL : http://www.example.org/ * License : (GPL, LGPL, BSD, MIT/X, etc.) Description : Mixed-level/mixed-signal electronic circuit simulator (Include the long description here.) -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11-1-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian mentors ubuntu
On Tue, Jul 19, 2005 at 01:09:05PM +0200, Nico Golde wrote: Hello Martin, * Martin Pitt [EMAIL PROTECTED] [2005-07-19 12:37]: Nico Golde [2005-07-19 12:21 +0200]: Heyho, why is mentors.debian.net powered by Ubuntu? This gave me a good laugh, and it's certainly way better than SuSE or Micro$$$ IIS :-), but still a bit embarrasing... I don't undestand what has ubuntu to do with a site which is mainly used by new debian maintainers and their packages? please explain. regards nico This one's obvious. mentors.debian.net is a site relating to people who are _not_ Debian Developers, but may strongly resemble such. And so it runs Ubuntu, which is _not_ Debian, but may strongly resemble such. (With shouts to the boys and girls on #debian) -- --- Paul TBBle Hampson, MCSE 8th year CompSci/Asian Studies student, ANU The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361) [EMAIL PROTECTED] No survivors? Then where do the stories come from I wonder? -- Capt. Jack Sparrow, Pirates of the Caribbean License: http://creativecommons.org/licenses/by/2.1/au/ --- pgpsT2gwOybGv.pgp Description: PGP signature
Mass-filing bugs based on piuparts?
I'm running piuparts, my package installation, upgrading, and removal tester, against etch. It takes a while, and produces a fairly large number of error logs that need to be investigated manually. This sometimes reveals a bug in piuparts, and sometimes in the package, or a depency of the package. When there are problems in packages, I would like to file bugs. This is potentially a large number of bugs, up to hundreds. I want to file them one by one, not all at once, since it will take weeks or months to go through the entire archive. A few bugs a day, in other words, not hundreds all at once. I will verify the existence of every bug manually, and will attempt to use the best possible taste in deciding whether something is a bug in the package or not. For this first run, I will concentrate on the clear cases: if a package leaves /usr/bin/foo on the filesystem after purging, it is pretty clearly a bug. Is this acceptable to everyone? Suggestions on how to do this better? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Mass-filing bugs based on piuparts?
On Thu, Jul 21, 2005 at 03:41:10PM +0300, Lars Wirzenius wrote: I'm running piuparts, my package installation, upgrading, and removal tester, against etch. It takes a while, and produces a fairly large number of error logs that need to be investigated manually. This sometimes reveals a bug in piuparts, and sometimes in the package, or a depency of the package. When there are problems in packages, I would like to file bugs. This is potentially a large number of bugs, up to hundreds. I want to file them one by one, not all at once, since it will take weeks or months to go through the entire archive. A few bugs a day, in other words, not hundreds all at once. I will verify the existence of every bug manually, and will attempt to use the best possible taste in deciding whether something is a bug in the package or not. For this first run, I will concentrate on the clear cases: if a package leaves /usr/bin/foo on the filesystem after purging, it is pretty clearly a bug. Is this acceptable to everyone? Suggestions on how to do this better? I say Go ahead!. I suggest you start with our base system; hopefully it's already correct, but you never know, and fixing such bugs as early in the release cycle as possible is important. Also, branch packages (for instance perl/php/python/apache/mysql) seems more important to test at an early stage than leaf packages (applications that use those packages). Regards: David -- /) David Weinehall [EMAIL PROTECTED] /) Rime on my window (\ // ~ // Diamond-white roses of fire // \) http://www.acc.umu.se/~tao/(/ Beautiful hoar-frost (/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Reopening bug closed due to SPAM
attached (valid) GPG/PGP signatures (from a valid developer?) -- valid GPG signature present on public servers, not necessarily from a valid DD seems to be a valid scheme. I haven't seen any spam GPG signed yet -- another idea would be to use the same authentication as used by most of the mailing list servers -- verification of intent: confirmation email sent to the originating email address and reply to it keeping subject with a key code intact would verify that it was a valid request. Otherwise original request expires in a day or two if it doesn't get confirmed. Then anyone who wants automate this process writes a 2 liner procmail rule ;-) My 2 kopeyki (ie cents) -- .-. =-- /v\ = Keep in touch// \\ (yoh@|www.)onerussian.com Yaroslav Halchenko /( )\ ICQ#: 60653192 Linux User^^-^^[17] pgpP61H8uv0XZ.pgp Description: PGP signature
Re: Reopening bug closed due to SPAM
Le Jeu 21 Juillet 2005 15:22, Yaroslav Halchenko a écrit : attached (valid) GPG/PGP signatures (from a valid developer?) -- valid GPG signature present on public servers, not necessarily from a valid DD seems to be a valid scheme. I haven't seen any spam GPG signed yet that sucks, I want to be able to close bugs, even if I'm using a M$ computer with no gpg plugin on it (on from an unsecure machine where I don't want to unlock my gpg key). -- another idea would be to use the same authentication as used by most of the mailing list servers -- verification of intent: confirmation email sent to the originating email address and reply to it keeping subject with a key code intact would verify that it was a valid request. Otherwise original request expires in a day or two if it doesn't get confirmed. Then anyone who wants automate this process writes a 2 liner procmail rule ;-) that's way better. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpJk6OcNgxkb.pgp Description: PGP signature
Re: Usability: Technical details in package descriptions?
On Wed, Jul 20, 2005 at 08:48:46PM +0200, Andreas Tille wrote: On Wed, 20 Jul 2005, W. Borgert wrote: Foo is a Perl-based program that... libBar is written in C... libBang is written in only 42 lines of source code... Baz has been written by me... Do such descriptions justify bug reports of severity=minor? Well, I would guess wishlist is the right way to go and the language should go into debtags information as suggested by others. The language a program is written in is completely irrelevant for user applications and might more confuse user than beeing helpful. For librarie-dev packages it might be helpful because it is relevent developer information. Thanks for pointing this out It seems to me that WB and Andreas make a valid point. Why should the user care what language a program is written in, so long as the program works right? Functionality is the important thing. I see another side to it, however. At least seven reasons occur to me why a user might care what language a program is written in. 1. Compiled programs (C, C++, Fortran 77, Ada, ...) usually run leaner and faster than do interpreted ones (Perl, Python, Ruby, ...). 2. Programs written in obscure languages may prove unmaintainable if the original developer disappears. Besides threatening obsolescence, this can be a security issue. 3. Programs written in widely used languages (C, C++, Perl, Python, ...) may work better simply because the programmer had adequate access during development to high-quality modules and library bindings. 4. With a language come a mindset, an aesthetic and a development culture. Although one cannot speak in absolutes, generally speaking, which program would you expect to be more focused and reliable: a program written in C++ or an alternative written in Perl? (On the other hand, which of the two programs would you expect to be available sooner?) 5. Some languages are inherently more debuggable (or less bug-prone) than others. C++ is more debuggable than C, which itself is more debuggable than Fortran 77. Python is more debuggable than Perl. Programs written in the more debuggable languages may rationally be expected to suffer fewer bugs. 6. Some languages enjoy not only free compilers or interpreters, but also well written, complete free documentation. It may not seem like much, but a limited ideological motive may exist to promote programs written in such languages. 7. Some users may want to be able to read parts of the source of the programs they use---even if they have no intention of contributing to development. This is Debian, after all. Programs written in obscure languages may be vaguely deprecated for this reason. If it matters, the languages I personally use most on a daily basis are Perl, Fortran 77, Octave and Bash (also occasionally C, C++ or Python)---some of which do not rank very well by my own criteria. However, I do tend to avoid publishing things written in Perl, because I use Perl often and know Perl's nature. As a user, I tend to prefer software compiled from C/C++. Hence the language in which a program is implemented is somewhat relevant, at least to me. -- Thaddeus H. Black 508 Nellie's Cave Road Blacksburg, Virginia 24060, USA +1 540 961 0920, [EMAIL PROTECTED], [EMAIL PROTECTED] pgpNj11HIQWzj.pgp Description: PGP signature
Re: Usability: Technical details in package descriptions?
On 7/21/05, Thaddeus H. Black [EMAIL PROTECTED] wrote: I see another side to it, however. At least seven reasons occur to me why a user might care what language a program is written in. A 'normal' user doesn't know what C, C++ and Perl are.
Re: Mass-filing bugs based on piuparts?
Lars Wirzenius writes: Is this acceptable to everyone? It's fine with me. -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Reopening bug closed due to SPAM
On Thu, Jul 21, 2005 at 03:34:43PM +0200, Pierre Habouzit wrote: that sucks, I want to be able to close bugs, even if I'm using a M$ computer with no gpg plugin on it (on from an unsecure machine where I don't want to unlock my gpg key). Well - we need to give up something so it becomes 1 click harder for the spammers ;-) indeed it would make it tricky to close bugs while working from cell phones, some pdas, wrist watchers and kitchen sinks. As for M$ Windows, for any kinds of emails really a nice solution is Thunderbird+Enigmamail+keys on a USB flash drive (ie it can be your ipod or iriver) so you have all your privates with you at any moment ;-) not that I'm forcing you to accept it in any way -- I'm just giving an alternative solution ;-) -- .-. =-- /v\ = Keep in touch// \\ (yoh@|www.)onerussian.com Yaroslav Halchenko /( )\ ICQ#: 60653192 Linux User^^-^^[17] pgpwCv8AYx16T.pgp Description: PGP signature
Re: Reopening bug closed due to SPAM
Thunderbird+Enigmamail+keys on a USB flash drive (ie it can be your ipod just a link FYI http://dev.weavervsworld.com/projects/ptbirdeniggpg/ -- .-. =-- /v\ = Keep in touch// \\ (yoh@|www.)onerussian.com Yaroslav Halchenko /( )\ ICQ#: 60653192 Linux User^^-^^[17] pgpkseH5iT4Ul.pgp Description: PGP signature
Re: Usability: Technical details in package descriptions?
Hello, I started a page on the Debian wiki for this project http://wiki.debian.net/?PackagesDescriptionsReview Feel free to edit any part of it. If everyone agrees, I intend to add some thoughts about the organization details we could set up (code to track the work and ease the work of the reviewers). Regards, -- Clément -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Usability: Technical details in package descriptions?
On Thu, Jul 21, 2005 at 01:45:55PM +, Thaddeus H. Black wrote: 4. With a language come a mindset, an aesthetic and a development culture. Although one cannot speak in absolutes, generally speaking, which program would you expect to be more focused and reliable: a program written in C++ or an alternative written in Perl? (On the other hand, which of the two programs would you expect to be available sooner?) I think you are expecting people to say C++, and on the other hand, Perl: However, I think perl for both :-) -- Jon Dowland http://jon.dowland.name/ PGP fingerprint: 7032F238 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Reopening bug closed due to SPAM
On Thu, 21 Jul 2005, Yaroslav Halchenko wrote: On Thu, Jul 21, 2005 at 03:34:43PM +0200, Pierre Habouzit wrote: that sucks, I want to be able to close bugs, even if I'm using a M$ computer with no gpg plugin on it (on from an unsecure machine where I don't want to unlock my gpg key). Well - we need to give up something so it becomes 1 click harder for the spammers ;-) [...] The only reason it is easy for spammers to close a bug is that the bug has been already closed before (and reopened again) and the spammers have harvested the -done address for that bug from the web pages. So if the BTS people decided to make it more difficult to close a bug, it would be more than enough to make it just minimally more difficult, for example, require that the address is [EMAIL PROTECTED] or -done2 for the second time a bug is closed (instead of the usual -done), and so on. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Usability: Technical details in package descriptions?
On Thu, 21 Jul 2005, Thaddeus H. Black wrote: I see another side to it, however. At least seven reasons occur to me why a user might care what language a program is written in. 1. Compiled programs (C, C++, Fortran 77, Ada, ...) usually run leaner and faster than do interpreted ones (Perl, Python, Ruby, ...). This could be expressed by caracterizing the runtime behaviour verbal (if necessary - I guess no package description will contain: this program runs slowly because it is written in an interpreted language). Moreover the users we talk about in this thread might not have the necessary knowledge to draw these conclusions. 2. Programs written in obscure languages may prove unmaintainable if the original developer disappears. Besides threatening obsolescence, this can be a security issue. Security issues should be sorted out by the maintainer / security team and not by users who need a certain knowledge about a programming language. 3. Programs written in widely used languages (C, C++, Perl, Python, ...) may work better simply because the programmer had adequate access during development to high-quality modules and library bindings. If there are competing packages with same functionality this might be a minor point. In the end the decision pro or contra is done on the usability side, not based upon the programming language. 4. With a language come a mindset, an aesthetic and a development culture. Although one cannot speak in absolutes, generally speaking, which program would you expect to be more focused and reliable: a program written in C++ or an alternative written in Perl? (On the other hand, which of the two programs would you expect to be available sooner?) Our target users will probably not do such consideratione. 5. Some languages are inherently more debuggable (or less bug-prone) than others. C++ is more debuggable than C, which itself is more debuggable than Fortran 77. Python is more debuggable than Perl. Programs written in the more debuggable languages may rationally be expected to suffer fewer bugs. Also more a developers consideration. 6. Some languages enjoy not only free compilers or interpreters, but also well written, complete free documentation. It may not seem like much, but a limited ideological motive may exist to promote programs written in such languages. Ditto. 7. Some users may want to be able to read parts of the source of the programs they use---even if they have no intention of contributing to development. This is Debian, after all. Programs written in obscure languages may be vaguely deprecated for this reason. They might find it out from Debtags. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Mass-filing bugs based on piuparts?
On Thu, Jul 21, 2005 at 03:41:10PM +0300, Lars Wirzenius wrote: Is this acceptable to everyone? Suggestions on how to do this better? Any possibility of producing a nice web report on a per package basis? It could be useful to re-run periodically and your tester could probably have the same role of lintian/linda by this point of view. Filling BTS reports could be not so appropriate. Disclosure: I do not know piuparts at all :) -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Usability: Technical details in package descriptions?
Jon Dowland writes: I think you are expecting people to say C++, and on the other hand, Perl: However, I think perl for both :-) I agree. -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#319334: ITP: ng-spice -- Mixed-level/mixed-signal electronic circuit simulator
On Thu, Jul 21, 2005 at 10:44:27AM +, Gerasimos Melissaratos wrote: Package: wnpp Severity: wishlist Owner: Gerasimos Melissaratos [EMAIL PROTECTED] There may be a licence problem, so I'm pasting from the package's licence: Permission to use, copy, modify, and distribute this software and its documentation for educational, research and non-profit purposes, without I don't think it can be distributed at all. Debian does not limit users of its distributed files in any way. If it limited all but distribution/copy it could be fine for non-free AFAIK. But that one poses too many limitations. -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Reopening bug closed due to SPAM
On Thu, Jul 21, 2005 at 09:22:10AM -0400, Yaroslav Halchenko wrote: -- another idea would be to use the same authentication as used by most of the mailing list servers -- verification of intent: confirmation email sent to the originating email address and reply to it keeping A slightly better modification of this scheme I think would be taken from some FIDONet newsgroups -- to verify sender's email address. so algorithm is check sender in DB and get his Keyword from DB if it is there if sender is not in DB then add email to DB, generate Keyword fi if email includes Keyword anywhere (X-Keyword field in the header or just a line in the body) then strip the lines containing keyword and post email else send a verification email to the sender where provide his Keywords for future postings fi this way it is one time job for anyone to adjust their .muttrc or whatever to include X-Keyword header in their emails to *debian.org -- .-. =-- /v\ = Keep in touch// \\ (yoh@|www.)onerussian.com Yaroslav Halchenko /( )\ ICQ#: 60653192 Linux User^^-^^[17] pgp2cutljQHuD.pgp Description: PGP signature
Re: Reopening bug closed due to SPAM
The only reason it is easy for spammers to close a bug is that the bug has been already closed before (and reopened again) and the spammers have harvested the -done address for that bug from the web pages. A very valid point... I took the task more general - to infiltrate bug reports (and may be give ideas for even mailing lists) from SPAM. crawlers get all [EMAIL PROTECTED] emails and then bug reports get spammed as well as the relevant dudes. BTW - why it has to be iff scheme - why it can't be a pipeline if signed with a valid GPG signature -- permit else if spamassassin gives negative score -- permit else send a verification letter Indeed - it is more load on the server but 1st step doesn't require much of load, mostly waiting time for the transaction. We would get to spamassassin quite rarely if most of people (and DD) start signing their submissions, and 3rd one will hit with probably 1% false positives... -- .-. =-- /v\ = Keep in touch// \\ (yoh@|www.)onerussian.com Yaroslav Halchenko /( )\ ICQ#: 60653192 Linux User^^-^^[17] pgpZ8cjo4aJDv.pgp Description: PGP signature
Re: Usability: Technical details in package descriptions?
On Thu, 2005-07-21 at 13:45 +, Thaddeus H. Black wrote: 1. Compiled programs (C, C++, Fortran 77, Ada, ...) usually run leaner and faster than do interpreted ones (Perl, Python, Ruby, ...). In general, algorithm choice is much more important than language. Also, the language the main program is written in may be of little significance to the program's overall performance if the grunt work is done in libraries written in a compiled language. In the end, the user wants to know if the program's speed and size is acceptable for their needs. The language that the program is written in does not directly answer these questions, and sometimes is even misleading. 2. Programs written in obscure languages may prove unmaintainable if the original developer disappears. Besides threatening obsolescence, this can be a security issue. You've furnished a reason *not* to put the language in the description (if I wrote a package in an obscure language and took your point to heart, I'd not want to advertise the fact). Besides, what is obscure? Ruby? Ocaml? Snobol? Fortran? Scheme? How is a user to assess whether these are up-and-coming languages, less popular but still well supported, or completely obsolete? I doubt if most users know the difference. 3. Programs written in widely used languages (C, C++, Perl, Python, ...) may work better simply because the programmer had adequate access during development to high-quality modules and library bindings. A false sense of security at best. You could argue conversely that the more popular the language, the more likely a novice programmer has chosen it to dash off their first programming project and has managed to get it into Debian. And perhaps using an obscure language could be viewed as a filter, weeding out the less-motivated and less-skilled programmers. Again, the user cannot use implementation language as a reliable indicator of quality. 4. With a language come a mindset, an aesthetic and a development culture. Although one cannot speak in absolutes, generally speaking, which program would you expect to be more focused and reliable: a program written in C++ or an alternative written in Perl? (On the other hand, which of the two programs would you expect to be available sooner?) Now we're *really* getting touchy-feely. I think we're losing sight of the goal: the user, reading the description, should get a sense of what the package does, whether it is likely to meet their needs, and whether it offers distinct advantages over any of the alternatives. While I can appreciate that some small minority of users out their are aware of the mindset, aesthetic and development culture of an implementation language, and therefore have some mild bias towards packages implemented in it, it certainly isn't a primary indicator of whether the package is suitable for a particular use or not. 5. Some languages are inherently more debuggable (or less bug-prone) than others. C++ is more debuggable than C, which itself is more debuggable than Fortran 77. Python is more debuggable than Perl. Programs written in the more debuggable languages may rationally be expected to suffer fewer bugs. A more direct measure of this can be determined by a bit of research by the user first: check the Debian bug database, the changelogs, the upstream bug database, the support development mailing lists. Ask your friends. Is this a good program, or is it a buggy piece of waste product? 6. Some languages enjoy not only free compilers or interpreters, but also well written, complete free documentation. It may not seem like much, but a limited ideological motive may exist to promote programs written in such languages. We're getting further and further from real user concerns. See my answer to 5. 7. Some users may want to be able to read parts of the source of the programs they use---even if they have no intention of contributing to development. This is Debian, after all. Programs written in obscure languages may be vaguely deprecated for this reason. apt-get source packagename and look it over if you're an aspiring developer. There isn't any better way to get acquainted with the source than to actually look at it. If it matters, the languages I personally use most on a daily basis are Perl, Fortran 77, Octave and Bash (also occasionally C, C++ or Python)---some of which do not rank very well by my own criteria. Octave, what's that? Hm, I guess it must be one of those shoddy deprecated languages. I'll make sure to avoid anything you've written in it. ;) However, I do tend to avoid publishing things written in Perl, because I use Perl often and know Perl's nature. As a user, I tend to prefer software compiled from C/C++. Hence the language in which a program is implemented is somewhat relevant, at least to me. And somewhat relevant is exactly what the debtags aspect implemented-in is for, as mentioned earlier. Ben -- To
Re: Bug#319334: ITP: ng-spice -- Mixed-level/mixed-signal electronic circuit simulator
On Jul 21, Francesco P. Lovergine [EMAIL PROTECTED] wrote: Permission to use, copy, modify, and distribute this software and its documentation for educational, research and non-profit purposes, without I don't think it can be distributed at all. Debian does not limit users of its distributed files in any way. If it limited all but distribution/copy it could be fine for non-free AFAIK. But that one poses too many limitations. Wrong. Such a license it totally acceptable for non-free, and a lot of software in non-free has a similar license. -- ciao, Marco signature.asc Description: Digital signature
Re: Bug#319334: ITP: ng-spice -- Mixed-level/mixed-signal electronic circuit simulator
Francesco P. Lovergine writes: I don't think it can be distributed at all. Debian does not limit users of its distributed files in any way. If it limited all but distribution/copy it could be fine for non-free AFAIK. But that one poses too many limitations. Anything Debian can distribute can go in non-free. Users of non-free are expected to read the licenses. -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Mass-filing bugs based on piuparts?
Francesco P. Lovergine writes: Any possibility of producing a nice web report on a per package basis? ... Filling BTS reports could be not so appropriate. I'd prefer bug reports. -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Usability: Technical details in package descriptions?
On Thu, 2005-07-21 at 13:45 +, Thaddeus H. Black wrote: Hence the language in which a program is implemented is somewhat relevant, at least to me. The conclusion is clear: the programming language is relevant to some users, but not to others (who are presumed to be large in quantity). So it's perfectly ok to mention the programming language, but not at the start of the description. nstead of putting it in the first sentence, the second paragraph would be a fine place to mention details like this, satisfying both novice and advanced users. Regards, Thijs signature.asc Description: This is a digitally signed message part
Re: Usability: Technical details in package descriptions?
On Thu, 2005-07-21 at 19:58 +0200, Thijs Kinkhorst wrote: nstead of putting it in the first sentence, the second paragraph would be a fine place to mention details like this, satisfying both novice and advanced users. But why bother, when debtags does implemented-in does the job better? Extra verbiage in the long description that adds no value for most users is best simply left out. It will just make the description a longer read (not to mention introducing possible false hits in an apt-cache search) which is a net negative effect on the users that don't need or want this information. Ben -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: aspell upgrade woes
Steve Langasek [EMAIL PROTECTED] writes: On Tue, Jul 19, 2005 at 11:52:51PM -0700, Brian Nelson wrote: Reintroducing the libaspell15 could cause problems with /usr/bin/aspell, since it actually goes outside the C API of libaspell and uses C++ linkage to some symbols. I fixed this bug (#307481) by making aspell-bin (or now just aspell) depend on the Source-Version of libaspell. However, that fix is not in the stable package of aspell. In stable, aspell-bin just depends on libaspell15 (= 0.60), so a partial upgrade of just libaspell15 would break aspell-bin. I suppose I could make the new libaspell15 conflict with the old aspell-bin, but that's rather clumsy and could make upgrades even more awkward. I'm not sure what the best thing to do would be. I'm sort of inclined to just stick with the transitioned libaspell15c2... Well, using libaspell15c2 will definitely cause some complexity on the upgrade path from sarge to etch. I don't know how much having libaspell15 conflict with aspell-bin ( $version) would do so. I suspect that it would be substantially less since there are only four packages in sarge which depend directly on aspell-bin or aspell, vs. 61 packages which depend on libaspell15 -- at a minimum, the worst-case scenario when conflicting with aspell-bin ( $version) looks substantially better. OK, very well then, I'll undo the GCC 4 transition for libaspell15. BTW, does anyone familiar with gettext want to send me a patch for RC bug #31? Upstream said he plans to make a new release with an upgrade to gettext 0.14.5 sometime this week, but I haven't heard anything else from him. -- Society is never going to make any progress until we all learn to pretend to like each other. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: is it a bug to not depend on a library package needed for some binary?
On Sunday 17 July 2005 10.14, Karl Chen wrote: Suppose package P contains files /usr/bin/B1 and /usr/bin/B2. B1 is the important program, and B2 is not as important. Is it OK for the declared package dependencies to not satisfy all the run-time shared library dependencies of B2? What if they are listed in Suggests? I have found many such packages. This is what Recommends: is for. I'd say a Suggests: is too weak (except if the helper program B2 is really, really unimportant - perhaps it should not be installed, or just put to /usr/share/doc/contrib or so? But as soon as B2 is something that actually is used by many people, a hard dependency would make sense. And, of course, for not-so-small B2, Goswin's suggestion to split it out into its own package makes sense, too. cheers -- vbi -- Today is Boomtime, the 56th day of Confusion in the YOLD 3171 pgpzjgiQHqyrp.pgp Description: PGP signature
Bug#319383: ITP: minised -- a smaller, cheaper, faster SED implementation
Package: wnpp Severity: wishlist Owner: Michael Prokop [EMAIL PROTECTED] * Package name: minised Version : 1.5 Upstream Author : Rene Rebe [EMAIL PROTECTED] * URL : http://www.exactcode.de/oss/minised/ * License : GPL Description : a smaller, cheaper, faster SED implementation This sed implementation is based on the one by Eric S. Raymond. It is a very small and fast implementation of sed. Statically compiled against the dietlibc the binary has less than 35kB. . Homepage: http://www.exactcode.de/oss/minised/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Please confirm (conf#1ce969f7398dbe523f2f81436bb3412d)
IMPORTANT INFORMATION!
This is an automated message.
The message you sent (attached below) requires confirmation
before it can be delivered. To confirm that you sent the
message below, just hit the Reply button and send this
message back (you don't need to edit anything). Once this is
done, no more confirmations will be necessary.
INFORMAÇÃO IMPORTANTE
Esta é uma mensagem automática
A mensagem que você enviou (em anexo) requer confirmação
antes de ser entregue. Para confirmar o envio basta
pressionar o botão de Reply e enviar esta mensagem de
volta (não é necessário editar). Uma vez que isto seja
feito, novas confirmações não serão necessárias.
This email account is protected by:
Active Spam Killer (ASK) V2.5.0 - (C) 2001-2002 by Marco Paganini
For more information visit http://www.paganini.net/ask
--- Original Message Follows ---
From: debian-devel@lists.debian.org
To: [EMAIL PROTECTED]
Subject: omuxucutbpmajzge
Date: Thu, 21 Jul 2005 13:35:29 -0500
This is a multi-part message in MIME format.
--=_NextPart_000_0011_3B59FAAF.40318ED4
Content-Type: text/plain;
charset=us-ascii
Content-Transfer-Encoding: 7bit
RÐG8Ëaù¿Ú\{h/nJ#àÇ º
/³W°eóØ¢KÙ#Ò;êbHG
ÑWB®ZètìÜ`cmosW-R¦Üðt¼B
:ÞsæhðFêÚ|
~´|Òõ(lÔi]׺¬[UÐÕÇÐBbß«ïCC×ÔGÞi#ú¿à/üq
tîÅn/Ú9à/gWî5åºßÊpÐåÆ8xLk9-ÄNuÁZðnéÜcOÚLµR¶-3p{bíÃîåDn] 1Sn8YEee1°.HÒ
ýàViЧ¥eò½»ûw¯ÞK®^DSNÁ¡ûÑÚMôþ1-3¡å[¨ÎæÂÃRöt#(Ó¬z.I»
Á¥
×ù].
Î#fÐû¦äiRÐñòC`ßJÄÁfzÅg,8
¶rE®ÌÚ%`|ù?(è
3lJÅùþzHkAxXNUúÛåõtÚ9Fu Û
[ÓQÓyElµAyé¢gLÅ/»Ëò8[廾ãZÓ#ö¥EDvS
±/cÐÏ
æz¿BÁîHë`%iWh?o2O7}!þø;%OTJNÖ#3Ëï¹gÄ©¯ÑÕ·õ0UQ¡UBÁg¯*»}0?ø£·Xý±«Õ)pDJ!ÓиXYÁî.öOäu^ñöF!Z¨[hQ»ßÎïßà[®Á*0Â.ìgY£íP$$©-%cÙé¾[¢wmæ,H¨ÌþNå2;/Sµ²ôcZ
P©J»hÊÁ¼£ú}pM
ªxÞ/ÈZzØ úEpÁyíHWSÍLvÞIÃÇÙræ¯2¦ºza-Xß½9JÑZªÉ^N«CÀ[ÛIô×ùÖÎe:9`ܤçý³.¾KPy^õ®Xøê²
à¬LCÍØLH §7Ź6ézpO%Í8ËÐ9Vô/Æ8ظ$siÍ%[óë²á[cBaâ±Ãv0ÁÉÝXo¶ v´
EªÕÇȾE
°8_DÌ°þÖ}JÈT÷NMAj}]Ø ó¢t¢ïéá´H³ç
;;ì3¯Ò¤Åg
ZîÀo¦¶×}s7'þ¢U{¸§Å¥$ÓÕÂWÆûï4ÓÒ½Q¢9Ëü¸ÒO¡-_S¥¨MÖlåü¸BW%æÞì è|m¸ûéä°
)¢2}¾ÈÚòJ]¨-\ÉqjûMwè'kHòDä¢ý¤-Z
Âì4¾ýwKDI[«Ø4ÉÀc^Ò6#pOQu§ghh4
eA EIøÃ]ÏvdFäûwr}B±¯
^#TX.^©ÃpàJ«R-ñ%0Ìef¢9ÓÌ2ä)XBk¶~zF/¼ùN.¹3AQh kô~ÄÂÊøWÁG
ìâîtæ#ÈyÒvßÖ½ÀWéêTñøFèùï^·s
?äÇëíVmmn6
ø$ì¢ÞlH¯Ñr^YõÔ`ø5Ë.Uef.C/®àp4C¨5´©Ém,t¼Wí£kJ9 Ò?kÙñh¿Ìh¶°ÆÛðƪĿ·g©¼ðþV
Ò箺Àò`ÌN
Üòcûvª/½¼3Jæ6Ô5ìç,;ùí~Põ¿£øiÏÙ¶{:Øf
Яû?v9ÊulÔÅ6S,Îü¾}ÆáI»ÀÙq VܤH¦¾hý;£s
8¶±fX.÷¤zUÅë»6ÌÊ0BÀYÉìöOÐ5/BôñúAÝÒjßç õHÕPãÉdþ;hµ{©sÆ¡¨XüGCÏ(S.QìöZ%ð¬â½Ä.ûL;ÝRgêû'h´òmò7îvù!s}âR
-[.¿§æÖNá0ɪ¦Q}(f.ïå?s7ô÷hÄóvf-ÁòjY±²Ú-à?ô.^ýP¹c¼Û`]§]Å×AUÃó·~N2i8*(ç{ëd
2¦XÜC%ö)[áïè:»{c7Cuvî_¡SòÅSd$dy
°bDˤ²µ]æV9¦u£¥SnÙ8²2O¸hצ[X5Ì°dìTÉ2¨þ
NLr}fXoîBóÇ^Væ§ã
ïÆóC9\iÒìeiÉÝFçQèûàªÔ(h¤Nsûc5ÌàÈD³Ù÷w* »¼ìg[BÛëé(1iÑ)îj6Ýøª^Î^:Û¨ô:]w°âÍ,ý7ÓP¾`®]S¹ÂµQuê8B®«×I«ÝH¡
ÙÅù}.²÷¿än1ÑݤOÐOýqû`·sÞIu.ÄG´uÙ{¯d$i×I¦
iMò4ÔvÈùŽ
}ö'¸çÔ9Ïñ8,8kîvº0õô$?þ©Ëa*'Ø8sÊ3USQø#WÙæ̧ûàÎÕS±©'ÂZgú}°
½kÞxr¨Þ#1¹a¥t4Y(msûî¹jjÐ]øÂ]ê;zßtÕöÌ°]'Fé8Þ,8Ã|õh
æÔø$¼m±jÈ®µ0âýA¬³UÝ
¶ToÚÉ
i®LW
Þ_3Óitn1a0Ng
*ST{#ÅÊ:ÚZIçîúIHÎ÷ôSÂHúq1m1üDûuèØõè4CêhÔÚ³q¨LXØi¿r6ð;`Ò¤©kGhömÍ
ÇÁ¼F¨R³a`º
ÊãBe:Ïbý?~©N宩Hì g#ü:i¨«q
(Original message truncated)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Usability: Technical details in package descriptions?
On Wed, 2005-07-20 at 18:13 +0200, Nico Golde wrote: I think one reason could be that some poeple would rather install a programm in a language they know and they are able to debug. Just a guess. On Wed, Jul 20, 2005 at 01:41:31PM -0300, Ben Armstrong wrote: Debtags facets[0] are better for this. Descriptions are supposed to help *ordinary* users decide which programs to install. (Hint: most of the world doesn't know how to debug in *any* language.) I *love* this idea, and it can be one good first use of Debtags, now that we have the data readily accessible in the Packages file. On Wed, Jul 20, 2005 at 06:42:42PM +0200, Steinar H. Gunderson wrote: You might want to look into the implemented-in debtags facet instead, then; it's probably more reliable :-) Note: due to recent refactoring, the implemented-in facet has been merged into the broader made-of facet. Thanks Ben and Steinar for the idea: it's the first application of Debtags as pure information that's been pointed to me. I've always only thought of tags as data to use for smarter package searches. That quite broadens my view. Ciao, Enrico -- GPG key: 1024D/797EBFAB 2000-12-05 Enrico Zini [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: Removal of transitional dummy packages
On Sunday 17 July 2005 23.28, Joerg Jaspert wrote: On 10353 March 1977, Santiago Vila wrote: we need to remove from the archive all the Woody-to-Sarge transition dummy packages. No, that's not true, we don't *need* to remove woody-to-sarge dummy packages, as they are also woody-to-etch dummy packages. We do not support that. No. So yes, woody-sarge packages should be removed, there is no reason to keep them. Upgrades from woody go via sarge and then to etch. Support and test woody - etch upgrades? No. Knowingly (and on purpose) break woody - etch upgrades where keeping the support is as cheap as keeping a simple arch:all dummy package? I vote no. (Based on a recollection that potato - sarge transitions worked reasonably, with a little hand holding, quite a long time into sarge's testing cycle.) No, I don't think dummy packages should be kept around forever, traces of potato-etch support, IMHO, is certainly not anything worth to keep. cheers -- vbi -- this email is protected by a digital signature: http://fortytwo.ch/gpg pgpkot62CxlH5.pgp Description: PGP signature
Re: Mass-filing bugs based on piuparts?
On Thursday 21 July 2005 14.41, Lars Wirzenius wrote: [piuparts] Go ahead - if you, as you say, investigate the bugs manually, it doesn't matter how you discovered the bug. Just curious: what kind of bugs can piuparts help discover? cheers -- vbi -- The jig's up, Elman. Which jig? -- Jeff Elman pgpYpSaumNCys.pgp Description: PGP signature
Re: aspell upgrade woes
Brian Nelson [EMAIL PROTECTED] writes: Steve Langasek [EMAIL PROTECTED] writes: On Tue, Jul 19, 2005 at 11:52:51PM -0700, Brian Nelson wrote: Reintroducing the libaspell15 could cause problems with /usr/bin/aspell, since it actually goes outside the C API of libaspell and uses C++ linkage to some symbols. I fixed this bug (#307481) by making aspell-bin (or now just aspell) depend on the Source-Version of libaspell. However, that fix is not in the stable package of aspell. In stable, aspell-bin just depends on libaspell15 (= 0.60), so a partial upgrade of just libaspell15 would break aspell-bin. I suppose I could make the new libaspell15 conflict with the old aspell-bin, but that's rather clumsy and could make upgrades even more awkward. I'm not sure what the best thing to do would be. I'm sort of inclined to just stick with the transitioned libaspell15c2... Well, using libaspell15c2 will definitely cause some complexity on the upgrade path from sarge to etch. I don't know how much having libaspell15 conflict with aspell-bin ( $version) would do so. I suspect that it would be substantially less since there are only four packages in sarge which depend directly on aspell-bin or aspell, vs. 61 packages which depend on libaspell15 -- at a minimum, the worst-case scenario when conflicting with aspell-bin ( $version) looks substantially better. OK, very well then, I'll undo the GCC 4 transition for libaspell15. BTW, does anyone familiar with gettext want to send me a patch for RC bug #31? Upstream said he plans to make a new release with an upgrade to gettext 0.14.5 sometime this week, but I haven't heard anything else from him. I just run gettextize, aclocal, automake (version 1.7 is needed irrc), autoconf and recompiled. That seemed to have fixed it for me. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Mass-filing bugs based on piuparts?
to, 2005-07-21 kello 16:44 +0200, Francesco P. Lovergine kirjoitti: On Thu, Jul 21, 2005 at 03:41:10PM +0300, Lars Wirzenius wrote: Is this acceptable to everyone? Suggestions on how to do this better? Any possibility of producing a nice web report on a per package basis? It could be useful to re-run periodically and your tester could probably have the same role of lintian/linda by this point of view. Filling BTS reports could be not so appropriate. Disclosure: I do not know piuparts at all :) Something like this is planned by the QA team, and I'll do my best to help with that. Before that is created, I still want to run piuparts on the entire archive, if only to make sure we can deal with the all the weird things that packages do in postinst scripts and so (such as forcefully redirecting their stdin/stdout to /dev/tty and then asking question, despite DEBIAN_FRONTEND being set to noninteractive). As with lintian reports, when the tools find real bugs in the packages, bugs should be filed. However, since the tools are not infallible, bugs should not be filed automatically. (Ideally, of course, the maintainer will use the tools themselves and find and fix all such automatically found problems before uploading.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Mass-filing bugs based on piuparts?
to, 2005-07-21 kello 21:11 +0200, Adrian von Bidder kirjoitti: On Thursday 21 July 2005 14.41, Lars Wirzenius wrote: [piuparts] Go ahead - if you, as you say, investigate the bugs manually, it doesn't matter how you discovered the bug. Just curious: what kind of bugs can piuparts help discover? The way I'm running it now, it installs and purges each package (plus dependencies), and then compares the state of the filesystem (the chroot) before and after and reports files that have been modified, removed, or created. Quite simplistic, really, but good enough to find a number of problems already. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Usability: Technical details in package descriptions?
On Wed, Jul 20, 2005 at 02:47:22PM -0500, Steve Greenland wrote: On 20-Jul-05, 10:47 (CDT), W. Borgert [EMAIL PROTECTED] wrote: what do you think about the usefulness of technical (and other strange) details in package description? While mostly agreeing with the other comments (libbar is a C library is useful/appropriate; foo is a perl program is not.), I'd guess this is a symptom of a more general problem: far too many package descriptions are taken verbatim from the upstream website/whatever. This leads to the irrelevant technical details you noted, as well as unfounded hyperbola (Foo is the world's best baz mangler) and generally bad writing. Most of these are probably worth a wishlist bug, but ONLY if accompanied by a suggested improvement. Most such phrases I have seen can be 'improved' merely by deleting them. They're content-free. I guess you could provide patches reducing the description to one or two lines, but it seems kinda like a waste of effort. -- .''`. ** Debian GNU/Linux ** | Andrew Suffield : :' : http://www.debian.org/ | `. `' | `- -- | signature.asc Description: Digital signature
Re: Yet another g++ transition page
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Steve Langasek wrote: Nice. :) Wishlist request: could you have it tally the total number of packages whose transition depends on each package in the list, and print that number next to the source package name? Better yet, could the list be sorted by this number? :) Done. Also, adjacent packages in the dependency graph which are part of the same source package do not increase the level a package lies in (as suggested by Jochen Voss). The script also generates the broken package list that I emailed earlier and this is posted there too. Now that I finally got around to finishing these changes, the pages should update regularly again. Cheers, - -Mike -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC4A1s7ZPKKRJLJvMRAp5EAKC1VcTlnGPV14/esZUtZmqDYlgIUwCfX4UH 3kk6tjKaBfs6/DEyO2yPn3I= =k2p0 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Yet another g++ transition page
Hello Mike, On Thu, Jul 21, 2005 at 05:02:38PM -0400, Mike Furr wrote: Done. Also, adjacent packages in the dependency graph which are part of the same source package do not increase the level a package lies in (as suggested by Jochen Voss). Very nice. I am happy to see that the depth is down to 4 now. Thank yoy very much, Jochen -- http://seehuhn.de/ signature.asc Description: Digital signature
ITP: doomsday - greatly improved engine to play doom, doom2, heretic and hexen
Package: wnpp Severity: wishlist URL: http://www.doomsdayhq.com/index.php License: GPL (see http://sourceforge.net/projects/deng) Description: About The Doomsday Engine The Doomsday Engine is an enhanced and extended version of DOOM, Heretic, and Hexen. It was originally based on the Hexen source code but parts of it have later been completely rewritten. Doomsday is only an engine; you will need a Game DLL if you want to play anything. Three such DLLs are being developed alongside the engine: jDoom, jHeretic and jHexen. Doomsday features: * Runs in Windows, Mac OS X, and Linux. * Supports OpenGL and Direct3D for crisp, hardware accelerated graphics. * 3D models (Quake's MD2 format) can be used instead of sprites. * Object and camera movement smoothing. * Simple shadows for objects. * Dynamic light effects and lens flares. * Particle effects. * 3D sound effects with DirectSound3D and EAX 2.0 or A3D 3.0. Also supports EAX's and A3D's environmental sound effects. * High-resolution textures (PNG, TGA, PCX) and detail textures. * 16-player client/server networking via TCP/IP, IPX, modem and serial link. * Easy to use Control Panel for configuration, accessed quickly with Shift-Esc. * Console for modifying settings and giving commands. * Utilizes FMOD to play a wide variety of music files, for example MP3, MOD and IT. * Uses plain text definition files for some game data such as thing types and states, sound and music information, level configuration (sky, fog, gravity) and text strings. Additional to that engine the new free high resolution textures and high quality music is a must have (http://www.doomsdayhq.com/files.php?class=4)! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ITP: doomsday - greatly improved engine to play doom, doom2, heretic and hexen
On Fri, Jul 22, 2005 at 12:20:45AM +0200, Alexander Fieroch wrote: License: GPL (see http://sourceforge.net/projects/deng) [...] * Utilizes FMOD to play a wide variety of music files, for example MP3, MOD and IT. Won't these two crash? /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Button voting can't be implemented anyway
The web interface to the BTS is read-only. You couldn't have button voting anyway (and of course that would be a mess without requiring registration, which isn't implemented neither...). ---Rant--- I guess the way to go with the BTS is to switch to Bugzilla/other packaged BTS. That doesn't mean the recent implementation of version tracking wasn't a good idea. As long as there are people to work on doing all the rest... :/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Button voting can't be implemented anyway
On Thu, 21 Jul 2005, Filipus Klutiero wrote: The web interface to the BTS is read-only. You couldn't have button voting anyway (and of course that would be a mess without requiring registration, which isn't implemented neither...). None of these are insurmountable if the actual proposal is worthwhile. However, there are a whole host of features that will actually help people fix bugs that are more useful to implement; especially since the subscription information can be used to do this anyway. Don Armstrong -- Taxes are not levied for the benefit of the taxed. -- Robert Heinlein _Time Enough For Love_ p250 http://www.donarmstrong.com http://rzlab.ucr.edu signature.asc Description: Digital signature
Re: Re: Reopening bug closed due to SPAM
On Thu, Jul 21, 2005 at 12:31:48AM +0200, Javier Fernández-Sanguino Peña wrote: If spam e-mail is going to start closing our Bugs in the BTS then we Start? It used to happen a lot; it's much less common nowadays. Well, it's the first time I've seen spam closing one bug reported by me. I often see spam to [EMAIL PROTECTED] addresses, however [1]. irony mode one I wonder if we can get spammers to add *debian* to the blacklist of keywords _not_ to spam, just like they currently do with *postmaster*, *abuse*, *spam* and, even, *linux* (ever seen a spammer bot? scary stuff) /irony mode off Regards Javier [1] Too much, in fact, for me to dedicate enough time to report it, counting 409 distinct mails since I implemented the filter a year ago. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apt 0.6 downloads from second archive?
On Thu, Jul 21, 2005 at 07:12:29AM +1000, Graham Williams wrote: Since installing apt 0.6 on an otherwise up-to-date unstable (except for anything depending on the aspell libraries...) packages on my local archive are being overlooked even though this archive is listed before others in my apt/sources.list. Downgrading to apt 0.5 and things work again as expected (i.e., most is downloaded from localhost). Huge (uninformed) guess, but apt may be preferring packages from repositories it can verify the contents of. Besides, if the versions are the same, then the contents should be the the same too, and (modulo bandwidth charges) which one you get from shouldn't matter. BTW, the new (twisted-based) apt-proxy rocks hard, if it's your traffic allowances you're worried about (and who wouldn't be in Australia, given what we get charged). - Matt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Mass-filing bugs based on piuparts?
On Thu, Jul 21, 2005 at 03:41:10PM +0300, Lars Wirzenius wrote: Is this acceptable to everyone? Suggestions on how to do this better? Hi Lars, by all means, proceed! Who say FLOSS lacks 'innovation'! Debian devs seem to comeup with good ideas all the time! Also, have you determined if any patterns have emerged in terms of error output. May be a summary mail of related bugs and associated packages so that folks can see what is happening and then a possible fix for each class. This could be a list of things of which to be aware during developement of upgrade scripts. Next stop, Mexico(not HEL)! Kev -- counter.li.org #238656 -- goto counter.li.org and be counted! `$' $' $ $ _ ,d$$$g$ ,d$$$b. $,d$$$b`$' g$b $,d$$b ,$P' `$ ,$P' `Y$ $$' `$ $ ' `$ $$' `$ $$ $ $$g$ $ $ $ ,$P $ $$ `$g. ,$$ `$$._ _. $ _,g$P $ `$b. ,$$ $$ `Y$$P'$. `YP $$$P' ,$. `Y$$P'$ $. ,$. signature.asc Description: Digital signature
Re: Reopening bug closed due to SPAM
On Thu, Jul 21, 2005 at 11:25:09AM -0400, Yaroslav Halchenko wrote: The only reason it is easy for spammers to close a bug is that the bug has been already closed before (and reopened again) and the spammers have harvested the -done address for that bug from the web pages. A very valid point... I took the task more general - to infiltrate bug reports (and may be give ideas for even mailing lists) from SPAM. crawlers get all [EMAIL PROTECTED] emails and then bug reports get spammed as well as the relevant dudes. BTW - why it has to be iff scheme - why it can't be a pipeline if signed with a valid GPG signature -- permit else if spamassassin gives negative score -- permit else send a verification letter Indeed - it is more load on the server but 1st step doesn't require much of load, mostly waiting time for the transaction. We would get to spamassassin quite rarely if most of people (and DD) start signing their submissions, and 3rd one will hit with probably 1% false positives... Sending verification letters like that is a rather bad idea. We're talking in the 10,000 to 100,000 verification emails a day here. Pasc -- Pascal Hakim 0403 411 672 Do Not Bend signature.asc Description: Digital signature
Accepted caps 0.2.3-3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Jul 2005 00:48:19 +0200 Source: caps Binary: caps Architecture: source i386 Version: 0.2.3-3 Distribution: unstable Urgency: low Maintainer: Mario Lang [EMAIL PROTECTED] Changed-By: Mario Lang [EMAIL PROTECTED] Description: caps - C* Audio Plugin Suite Changes: caps (0.2.3-3) unstable; urgency=low . * Rebuild for C++ ABI transition. Files: 8cf4edaf600bcf27a21954bf15b002c4 563 sound optional caps_0.2.3-3.dsc a265a8d782e2d7ce675db8769cd52428 1675 sound optional caps_0.2.3-3.diff.gz 047f74f47ee21527985bf06a652b848a 151616 sound optional caps_0.2.3-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFC30h83/wCKmsRPkQRAu1+AJ9XKBVcsTdeG7P/Kp5LvZuuqBrk4ACfZv+d LZpwjJ3ACouHxpuZ/hNinCE= =+kjs -END PGP SIGNATURE- Accepted: caps_0.2.3-3.diff.gz to pool/main/c/caps/caps_0.2.3-3.diff.gz caps_0.2.3-3.dsc to pool/main/c/caps/caps_0.2.3-3.dsc caps_0.2.3-3_i386.deb to pool/main/c/caps/caps_0.2.3-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted aspell-en 6.0-0-5 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Jul 2005 00:03:32 -0700 Source: aspell-en Binary: aspell-en Architecture: source all Version: 6.0-0-5 Distribution: unstable Urgency: low Maintainer: Brian Nelson [EMAIL PROTECTED] Changed-By: Brian Nelson [EMAIL PROTECTED] Description: aspell-en - English dictionary for GNU Aspell Changes: aspell-en (6.0-0-5) unstable; urgency=low . * Converted to use aspell-autobuildhash to build the dictionary hashes at install time, thus allowing the package to become Arch: all. * debian/control: removed the build-dependency on aspell since it's no longer needed Files: 0626ca997a9c3789f5011ac52bf8644c 619 text optional aspell-en_6.0-0-5.dsc 9c9e05fef9ae66f0b0efe475f2350fd4 5548 text optional aspell-en_6.0-0-5.diff.gz ad1801711ebce836b52a2dfc8af8e4be 249380 text optional aspell-en_6.0-0-5_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC30uX1Ng1YWbyRSERAp5YAJ48x1Cp74Y7vGbUmMg/geVBc/vMrQCfWlOS eiH6cWoTD8icvb/ReCUQeac= =ZFL6 -END PGP SIGNATURE- Accepted: aspell-en_6.0-0-5.diff.gz to pool/main/a/aspell-en/aspell-en_6.0-0-5.diff.gz aspell-en_6.0-0-5.dsc to pool/main/a/aspell-en/aspell-en_6.0-0-5.dsc aspell-en_6.0-0-5_all.deb to pool/main/a/aspell-en/aspell-en_6.0-0-5_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted feh 1.3.3-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Jul 2005 03:11:29 -0400 Source: feh Binary: feh Architecture: source i386 Version: 1.3.3-1 Distribution: unstable Urgency: low Maintainer: Laurence J. Lane [EMAIL PROTECTED] Changed-By: Laurence J. Lane [EMAIL PROTECTED] Description: feh- imlib2 based image viewer Closes: 265178 292020 310686 317601 Changes: feh (1.3.3-1) unstable; urgency=low . * New upstream release * Closes: #317601, EXIF corruption, fixed upstream * Closes: #292020, crash without r/w access to ~/.fehbg, fixed upstream * Closes: #265178, lossless jpeg rotation, fixed upstream in 1.3.2 * Closes: #310686, wrong URL in README, fixed upstream Files: 6af5a34925e56af879e35c4a178ebf7a 615 graphics optional feh_1.3.3-1.dsc d2aead74629fd04f26928f6af74b993b 377159 graphics optional feh_1.3.3.orig.tar.gz ff920745d9c96848fd5e7f087bd1935c 131253 graphics optional feh_1.3.3-1.diff.gz 6bea2b6eb4cee2bcfaea755821e3a6de 280032 graphics optional feh_1.3.3-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC31GFxJBkNlXToekRAuWdAJ9aDRZW9GHXIncg/2A/NdaHfqsF0wCfassU rrNVebU8HkwqnLit0lAbhuM= =4y5e -END PGP SIGNATURE- Accepted: feh_1.3.3-1.diff.gz to pool/main/f/feh/feh_1.3.3-1.diff.gz feh_1.3.3-1.dsc to pool/main/f/feh/feh_1.3.3-1.dsc feh_1.3.3-1_i386.deb to pool/main/f/feh/feh_1.3.3-1_i386.deb feh_1.3.3.orig.tar.gz to pool/main/f/feh/feh_1.3.3.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fidogate 4.4.7-3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Jul 2005 08:46:39 +0100 Source: fidogate Binary: fidogate Architecture: source i386 Version: 4.4.7-3 Distribution: unstable Urgency: low Maintainer: Jonathan McDowell [EMAIL PROTECTED] Changed-By: Jonathan McDowell [EMAIL PROTECTED] Description: fidogate - Gateway Fido - Internet Closes: 285936 Changes: fidogate (4.4.7-3) unstable; urgency=low . * Change priority to extra to match override file. * Fix compilation under GCC4.0 (closes: #285936) Files: 387303f86aaa4f4550c5b328e0f9d133 557 mail extra fidogate_4.4.7-3.dsc ca4cf502df892c570b645cf469917241 14197 mail extra fidogate_4.4.7-3.diff.gz a6e6211ef64dc57d8d195cda1d58e273 894628 mail extra fidogate_4.4.7-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC31QK8b1L5FtDA2cRApgJAJwKga7joAh8XJQICD16eWjeNrNAcQCeLbVQ sCm96XydIYmlrSh+CRMd2cY= =SsTO -END PGP SIGNATURE- Accepted: fidogate_4.4.7-3.diff.gz to pool/main/f/fidogate/fidogate_4.4.7-3.diff.gz fidogate_4.4.7-3.dsc to pool/main/f/fidogate/fidogate_4.4.7-3.dsc fidogate_4.4.7-3_i386.deb to pool/main/f/fidogate/fidogate_4.4.7-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted asciidoc 7.0.1-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Jul 2005 09:34:51 +0200 Source: asciidoc Binary: asciidoc Architecture: source all Version: 7.0.1-1 Distribution: unstable Urgency: low Maintainer: Fredrik Steen [EMAIL PROTECTED] Changed-By: Fredrik Steen [EMAIL PROTECTED] Description: asciidoc - Highly configurable text format for writing documentation Closes: 308331 318495 Changes: asciidoc (7.0.1-1) unstable; urgency=low . * New upstream release * Fix for typo in debian/rules Closes:#318495 * Changed package description, I agree with Mr. Wirzenius (Closes:#308331) Files: 97f1a72cd4e26806f670d09ed7e6c50b 651 text optional asciidoc_7.0.1-1.dsc b117387a6f6293c8a78fb0459564d060 722488 text optional asciidoc_7.0.1.orig.tar.gz c6632dd28480827074f2ff8481bbfed6 2580 text optional asciidoc_7.0.1-1.diff.gz 5948765635146da841eb799c1a58ee75 712212 text optional asciidoc_7.0.1-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC31h92pHue6WOFk8RAgoVAJ4mofrpGsnBt14pX/OkltsUCSMqWwCglOfQ 7EbbVAJle4lZ234arKOJvwY= =ixgs -END PGP SIGNATURE- Accepted: asciidoc_7.0.1-1.diff.gz to pool/main/a/asciidoc/asciidoc_7.0.1-1.diff.gz asciidoc_7.0.1-1.dsc to pool/main/a/asciidoc/asciidoc_7.0.1-1.dsc asciidoc_7.0.1-1_all.deb to pool/main/a/asciidoc/asciidoc_7.0.1-1_all.deb asciidoc_7.0.1.orig.tar.gz to pool/main/a/asciidoc/asciidoc_7.0.1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted aspell-br 0.50-2-6 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Jul 2005 01:24:00 -0700 Source: aspell-br Binary: aspell-br Architecture: source all Version: 0.50-2-6 Distribution: unstable Urgency: low Maintainer: Brian Nelson [EMAIL PROTECTED] Changed-By: Brian Nelson [EMAIL PROTECTED] Description: aspell-br - Breton dictionary for GNU Aspell Changes: aspell-br (0.50-2-6) unstable; urgency=low . * Converted to use aspell-autobuildhash to build the dictionary hashes at install time, thus allowing the package to become Arch: all. * debian/control: removed the build-dependency on aspell since it's no longer needed * Added support for dictionary registration in dictionaries-common Files: 8bba07705f25b48f5a99195285acb357 621 text optional aspell-br_0.50-2-6.dsc 63cf5796e6ade7b37790700ed73cde16 1715 text optional aspell-br_0.50-2-6.diff.gz facbf7353be2ba8dee9ca8c0b99cf2d6 66216 text optional aspell-br_0.50-2-6_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC31y11Ng1YWbyRSERAu+IAKCmPW/kG+OfMmcRlyHlMgbyVJp2LwCcDu4w zLcuwsAAE0J6PcJlrkDujl8= =WOKl -END PGP SIGNATURE- Accepted: aspell-br_0.50-2-6.diff.gz to pool/main/a/aspell-br/aspell-br_0.50-2-6.diff.gz aspell-br_0.50-2-6.dsc to pool/main/a/aspell-br/aspell-br_0.50-2-6.dsc aspell-br_0.50-2-6_all.deb to pool/main/a/aspell-br/aspell-br_0.50-2-6_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted boost 1.32.0+1.33.0-cvs20050720-2 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Jul 2005 10:08:48 +0200 Source: boost Binary: libboost-regex1.33.0 libboost-signals1.33.0 libboost-test-dev libboost-serialization-dev libboost-program-options1.33.0 libboost-thread1.33.0 libboost-python1.33.0 libboost-filesystem1.33.0 libboost-graph-dev libboost-dev libboost-test1.33.0 libboost-python-dev libboost-dbg libboost-doc libboost-date-time-dev libboost-program-options-dev libboost-regex-dev libboost-date-time1.33.0 libboost-signals-dev libboost-thread-dev libboost-filesystem-dev libboost-graph1.33.0 Architecture: source i386 all Version: 1.32.0+1.33.0-cvs20050720-2 Distribution: unstable Urgency: low Maintainer: Steve M. Robbins [EMAIL PROTECTED] Changed-By: Domenico Andreoli [EMAIL PROTECTED] Description: libboost-date-time-dev - set of date-time libraries based on generic programming concepts libboost-date-time1.33.0 - set of date-time libraries based on generic programming concepts libboost-dbg - Boost.org libraries with debug symbols libboost-dev - Boost.org libraries development files libboost-doc - Boost.org libraries documentation libboost-filesystem-dev - filesystem operations (portable paths, iteration over directories libboost-filesystem1.33.0 - filesystem operations (portable paths, iteration over directories libboost-graph-dev - generic graph components and algorithms in C++ libboost-graph1.33.0 - generic graph components and algorithms in C++ libboost-program-options-dev - program options library for C++ libboost-program-options1.33.0 - program options library for C++ libboost-python-dev - Boost.Python Library development files libboost-python1.33.0 - Boost.Python Library libboost-regex-dev - regular expression library for C++ libboost-regex1.33.0 - regular expression library for C++ libboost-serialization-dev - serialization library for C++ libboost-signals-dev - managed signals and slots library for C++ libboost-signals1.33.0 - managed signals and slots library for C++ libboost-test-dev - components for writing and executing test suites libboost-test1.33.0 - components for writing and executing test suites libboost-thread-dev - portable C++ multi-threading libboost-thread1.33.0 - portable C++ multi-threading Changes: boost (1.32.0+1.33.0-cvs20050720-2) unstable; urgency=low . * Added build dependency on libbz2-dev. Files: 5a4cde7e5c08a168a39e7f098709c2ed 1201 libs optional boost_1.32.0+1.33.0-cvs20050720-2.dsc e4fb394e7d635bab92bbcd1c87bc0ebd 38066 libs optional boost_1.32.0+1.33.0-cvs20050720-2.diff.gz 55b6d0b82517d09206e67363dcc3adb5 744 doc optional libboost-doc_1.32.0+1.33.0-cvs20050720-2_all.deb de641d5331996b6b4f5c6ed3bc5fc12a 4413732 libdevel optional libboost-dbg_1.32.0+1.33.0-cvs20050720-2_i386.deb e82f894f1bfd5416b55a54e1b80f4f7c 1841856 libdevel optional libboost-dev_1.32.0+1.33.0-cvs20050720-2_i386.deb 01e600dc3042986c5fb36fa06bd22879 30216 libs optional libboost-date-time1.33.0_1.32.0+1.33.0-cvs20050720-2_i386.deb ae809808fe250824bfb2c4b490da038c 154540 libdevel optional libboost-date-time-dev_1.32.0+1.33.0-cvs20050720-2_i386.deb e89587e8bfdec2fea211a95e226f0833 39328 libs optional libboost-filesystem1.33.0_1.32.0+1.33.0-cvs20050720-2_i386.deb 58889a7860c7ee1f9c348a1239afaec3 53748 libdevel optional libboost-filesystem-dev_1.32.0+1.33.0-cvs20050720-2_i386.deb 1161fb6bdd2be02211ed4d9d8372a060 139602 libs optional libboost-graph1.33.0_1.32.0+1.33.0-cvs20050720-2_i386.deb 3fda754c27a7eaa614b531b516f6d436 305576 libdevel optional libboost-graph-dev_1.32.0+1.33.0-cvs20050720-2_i386.deb 47a2310194a7a760853691bafaab4a03 104516 libs optional libboost-program-options1.33.0_1.32.0+1.33.0-cvs20050720-2_i386.deb 16063b16531d0f21c4d0150fa150636c 33668 libdevel optional libboost-program-options-dev_1.32.0+1.33.0-cvs20050720-2_i386.deb ef8cff692b8681e0abc9492f70b59a45 113536 python optional libboost-python1.33.0_1.32.0+1.33.0-cvs20050720-2_i386.deb c60e0cc4135fafb86256d85293a8dc0a 137128 libdevel optional libboost-python-dev_1.32.0+1.33.0-cvs20050720-2_i386.deb be64ece041ba78ec7d560afd948001a2 291098 libs optional libboost-regex1.33.0_1.32.0+1.33.0-cvs20050720-2_i386.deb 04954feda964f934c94604c6f0a04a56 633288 libdevel optional libboost-regex-dev_1.32.0+1.33.0-cvs20050720-2_i386.deb 9e88710996a2ba05cff3ea30636871e6 400132 libdevel optional libboost-serialization-dev_1.32.0+1.33.0-cvs20050720-2_i386.deb 50f66488129089cf47765f18e3fe3a58 42966 libs optional libboost-signals1.33.0_1.32.0+1.33.0-cvs20050720-2_i386.deb c50b4d55fe93ca9ecddeb04e0aa1684e 68650 libdevel optional libboost-signals-dev_1.32.0+1.33.0-cvs20050720-2_i386.deb 3521702eec45ba1bc0ff6aa674a8c703 190168 libs optional libboost-test1.33.0_1.32.0+1.33.0-cvs20050720-2_i386.deb 11a0b59f3c03c3e91005928374b22d2f 399792 libdevel optional libboost-test-dev_1.32.0+1.33.0-cvs20050720-2_i386.deb 2a3bf3e6f60f0ced5ff7cfb9e3084a65 43904 libs optional
Accepted devscripts 2.9.1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Jul 2005 09:51:17 +0100 Source: devscripts Binary: devscripts Architecture: source i386 Version: 2.9.1 Distribution: unstable Urgency: low Maintainer: Julian Gilbey [EMAIL PROTECTED] Changed-By: Julian Gilbey [EMAIL PROTECTED] Description: devscripts - Scripts to make the life of a Debian Package maintainer easier Closes: 319271 319289 Changes: devscripts (2.9.1) unstable; urgency=low . [ Julian Gilbey ] * annotate - annotate-output renaming, removing package conflict (closes: #319271, #319289) * debcommit: Apply Colin Watson's arch patch (see #319072) . [ Joey Hess ] * debchange: Fix parsing of --release-heuristic switch. Files: 4622a160e5ed82b4e5497cabc4e4a0a2 660 devel optional devscripts_2.9.1.dsc 72b9751c96d9d2e9d799017d00e4783b 197293 devel optional devscripts_2.9.1.tar.gz e8da9c27e9555648a84355246ec28417 217894 devel optional devscripts_2.9.1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC32QsDU59w/205FkRAobCAJ0aMy/fgASq6uAofLN5chsbh2dOLACbB6SN PqM0v70xqxuz1+2jnCqdsLE= =I8eg -END PGP SIGNATURE- Accepted: devscripts_2.9.1.dsc to pool/main/d/devscripts/devscripts_2.9.1.dsc devscripts_2.9.1.tar.gz to pool/main/d/devscripts/devscripts_2.9.1.tar.gz devscripts_2.9.1_i386.deb to pool/main/d/devscripts/devscripts_2.9.1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted soundtouch 1.2.1-8 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Jul 2005 11:09:37 +0200 Source: soundtouch Binary: libsoundtouch1-dev libsoundtouch1c2 Architecture: source i386 Version: 1.2.1-8 Distribution: unstable Urgency: low Maintainer: Guenter Geiger (Debian/GNU) [EMAIL PROTECTED] Changed-By: Guenter Geiger (Debian/GNU) [EMAIL PROTECTED] Description: libsoundtouch1-dev - development files for sound stretching library libsoundtouch1c2 - sound stretching library Closes: 318971 Changes: soundtouch (1.2.1-8) unstable; urgency=low . * Update libtool (closes: #318971) Files: 66c5866e45668323e77f6f6d463571c6 660 libs optional soundtouch_1.2.1-8.dsc 7b4d293639acd6864375b5479b7bcfb1 251153 libs optional soundtouch_1.2.1-8.diff.gz 05f102fa0b8f6d0e3757483178f499a4 72062 devel optional libsoundtouch1-dev_1.2.1-8_i386.deb a30446f5508b17ac05a22c6a449e9d0c 43672 libs optional libsoundtouch1c2_1.2.1-8_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC32fJ1pbKhmC2uVgRAgzKAJ451EE1ig+YZoV+Kg+UAjTNjvldNgCeO0+f 2t5L4a18ZTkB6K1RXNrMNzk= =Lfjj -END PGP SIGNATURE- Accepted: libsoundtouch1-dev_1.2.1-8_i386.deb to pool/main/s/soundtouch/libsoundtouch1-dev_1.2.1-8_i386.deb libsoundtouch1c2_1.2.1-8_i386.deb to pool/main/s/soundtouch/libsoundtouch1c2_1.2.1-8_i386.deb soundtouch_1.2.1-8.diff.gz to pool/main/s/soundtouch/soundtouch_1.2.1-8.diff.gz soundtouch_1.2.1-8.dsc to pool/main/s/soundtouch/soundtouch_1.2.1-8.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted dx 1:4.3.2-5 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 19 Jul 2005 11:51:00 +0200 Source: dx Binary: libdx4 dx libdx4-dev dx-doc Architecture: source all i386 Version: 1:4.3.2-5 Distribution: unstable Urgency: low Maintainer: Daniel Kobras [EMAIL PROTECTED] Changed-By: Daniel Kobras [EMAIL PROTECTED] Description: dx - OpenDX (IBM Visualization Data Explorer) - main package dx-doc - OpenDX (IBM Visualization Data Explorer) - documentation libdx4 - OpenDX (IBM Visualization Data Exploror) - shared libraries libdx4-dev - OpenDX (IBM Visualization Data Explorer) - development files Changes: dx (1:4.3.2-5) unstable; urgency=low . * debian/control: Tighten libglu1-xorg-dev dependencies to version providing sane shlibs. Files: cd3c11c738468708750e539b3b69f15c 1001 science optional dx_4.3.2-5.dsc 9bf31f80ab2f37b7143fcaffc4d8cfdf 95575 science optional dx_4.3.2-5.diff.gz c80a219c4fbb05d0a0db2b4d0321a8ac 4140044 doc optional dx-doc_4.3.2-5_all.deb 4ff5cf090ab996e44d9317c4b1806511 4078266 science optional dx_4.3.2-5_i386.deb 78e9d95cd5dae8e06286a3bc679f76ab 3683452 libs optional libdx4_4.3.2-5_i386.deb c430c511443962250f40399969906aa1 4720806 libdevel optional libdx4-dev_4.3.2-5_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC32ZwpOKIA4m/fisRAupMAJ9y7NINv0FRuTdT4eSla70jL99KfgCfegNf /NfiKN/CLrevKDeiOdtNztY= =VxO6 -END PGP SIGNATURE- Accepted: dx-doc_4.3.2-5_all.deb to pool/main/d/dx/dx-doc_4.3.2-5_all.deb dx_4.3.2-5.diff.gz to pool/main/d/dx/dx_4.3.2-5.diff.gz dx_4.3.2-5.dsc to pool/main/d/dx/dx_4.3.2-5.dsc dx_4.3.2-5_i386.deb to pool/main/d/dx/dx_4.3.2-5_i386.deb libdx4-dev_4.3.2-5_i386.deb to pool/main/d/dx/libdx4-dev_4.3.2-5_i386.deb libdx4_4.3.2-5_i386.deb to pool/main/d/dx/libdx4_4.3.2-5_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libdbd-sybase-perl 1.00-3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 6 Jun 2005 02:03:42 -0700 Source: libdbd-sybase-perl Binary: libdbd-sybase-perl Architecture: source i386 Version: 1.00-3 Distribution: unstable Urgency: low Maintainer: Steve Langasek [EMAIL PROTECTED] Changed-By: Steve Langasek [EMAIL PROTECTED] Description: libdbd-sybase-perl - Sybase/MS SQL database driver for the DBI module Closes: 319269 Changes: libdbd-sybase-perl (1.00-3) unstable; urgency=low . * Rebuild against freetds 0.63-1 (closes: #319269). Files: 70c2b7433a7cbc164545c8dd28f822b6 660 perl optional libdbd-sybase-perl_1.00-3.dsc 6c32727257c2a527d2d5376f547cd53c 2984 perl optional libdbd-sybase-perl_1.00-3.diff.gz 47f2bf74c15e2d98509c33df25d4eea7 116974 perl optional libdbd-sybase-perl_1.00-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC326nKN6ufymYLloRAusIAJ0cVDdvBTBMrYJ9fPO03ZTpBrKWrwCeNSkA 9bsIMAbgnyQM+vgxKFoO3fQ= =U0Cj -END PGP SIGNATURE- Accepted: libdbd-sybase-perl_1.00-3.diff.gz to pool/main/libd/libdbd-sybase-perl/libdbd-sybase-perl_1.00-3.diff.gz libdbd-sybase-perl_1.00-3.dsc to pool/main/libd/libdbd-sybase-perl/libdbd-sybase-perl_1.00-3.dsc libdbd-sybase-perl_1.00-3_i386.deb to pool/main/libd/libdbd-sybase-perl/libdbd-sybase-perl_1.00-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted p3nfs 5.18-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Jul 2005 11:03:27 +0200 Source: p3nfs Binary: p3nfs Architecture: source i386 Version: 5.18-2 Distribution: unstable Urgency: low Maintainer: Geert Stappers [EMAIL PROTECTED] Changed-By: Geert Stappers [EMAIL PROTECTED] Description: p3nfs - to mount the file systems on the Psion/Symbian PDA/Phone Closes: 95747 312838 Changes: p3nfs (5.18-2) unstable; urgency=low . * New maintainer (Closes: #95747,312838) . * Added Psion/Symbian in the short description . * debian/control: switch to dh_installman, removed dh_ comment lines Files: e04e5e78a4bed35b363195ee7e899a26 554 otherosfs extra p3nfs_5.18-2.dsc 53fdaa75e59042f0d87507fefc2adb9b 4973 otherosfs extra p3nfs_5.18-2.diff.gz 4aced4ad857a15a12da52fcf0ef472c2 139026 otherosfs extra p3nfs_5.18-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFC32ytOSINbgwa/7sRAlD4AJ4/Y+RU158AXvy0zq0qpA4DihPDPwCfVBkF sEAPlNevZBhU8x9sjP2fAcM= =F1Lb -END PGP SIGNATURE- Accepted: p3nfs_5.18-2.diff.gz to pool/main/p/p3nfs/p3nfs_5.18-2.diff.gz p3nfs_5.18-2.dsc to pool/main/p/p3nfs/p3nfs_5.18-2.dsc p3nfs_5.18-2_i386.deb to pool/main/p/p3nfs/p3nfs_5.18-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gnutls12 1.2.5-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Changed-By: Matthias Urlichs [EMAIL PROTECTED] Date: Thu, 21 Jul 2005 08:27:22 +0200 Version: 1.2.5-2 Distribution: unstable Source: gnutls12 Urgency: medium Maintainer: Matthias Urlichs [EMAIL PROTECTED] Binary: gnutls-bin libgnutls-dev libgnutls12 libgnutls12-dbg Architecture: i386 source Changes: gnutls12 (1.2.5-2) unstable; urgency=medium . * Did not depend on libgnutls12 -- not picked up by dh_shlibdeps. Added an explicit dependency as a stopgap fix. Description: libgnutls12 - the GNU TLS library - runtime library gnutls-bin - the GNU TLS library - commandline utilities libgnutls12-dbg - GNU TLS library - debugger symbols libgnutls-dev - the GNU TLS library - development files Files: 16c8d4e87677c918cd2e8daba5ea05a4 263204 net optional gnutls-bin_1.2.5-2_i386.deb 00b593614ae6feb6e6c005a6b642f37d 293179 devel optional gnutls12_1.2.5-2.diff.gz 1c848c524c7aa08f1350e47461b75d88 357104 libs important libgnutls12_1.2.5-2_i386.deb c1f7e4b81c255f69110ce29af0f6525b 773 devel optional gnutls12_1.2.5-2.dsc bbc024ad5adae8d1d91297bb5d8bfc25 733190 devel optional libgnutls12-dbg_1.2.5-2_i386.deb fa367ffdc80f8cad58bb4270549487a2 425568 libdevel optional libgnutls-dev_1.2.5-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC33ml8+hUANcKr/kRAg8SAJ96f2jAVh4PGx5qzlqN6CvC6WdR+ACcCylR DoS9sA9tQrqx2MyQwjINBMI= =Wz1+ -END PGP SIGNATURE- Accepted: gnutls-bin_1.2.5-2_i386.deb to pool/main/g/gnutls12/gnutls-bin_1.2.5-2_i386.deb gnutls12_1.2.5-2.diff.gz to pool/main/g/gnutls12/gnutls12_1.2.5-2.diff.gz gnutls12_1.2.5-2.dsc to pool/main/g/gnutls12/gnutls12_1.2.5-2.dsc libgnutls-dev_1.2.5-2_i386.deb to pool/main/g/gnutls12/libgnutls-dev_1.2.5-2_i386.deb libgnutls12-dbg_1.2.5-2_i386.deb to pool/main/g/gnutls12/libgnutls12-dbg_1.2.5-2_i386.deb libgnutls12_1.2.5-2_i386.deb to pool/main/g/gnutls12/libgnutls12_1.2.5-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted boost 1.32.0+1.33.0-cvs20050720-3 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Jul 2005 12:34:37 +0200 Source: boost Binary: libboost-regex1.33.0 libboost-signals1.33.0 libboost-test-dev libboost-serialization-dev libboost-program-options1.33.0 libboost-thread1.33.0 libboost-python1.33.0 libboost-filesystem1.33.0 libboost-graph-dev libboost-dev libboost-test1.33.0 libboost-python-dev libboost-dbg libboost-doc libboost-date-time-dev libboost-program-options-dev libboost-regex-dev libboost-date-time1.33.0 libboost-signals-dev libboost-thread-dev libboost-filesystem-dev libboost-graph1.33.0 Architecture: source i386 all Version: 1.32.0+1.33.0-cvs20050720-3 Distribution: unstable Urgency: low Maintainer: Steve M. Robbins [EMAIL PROTECTED] Changed-By: Domenico Andreoli [EMAIL PROTECTED] Description: libboost-date-time-dev - set of date-time libraries based on generic programming concepts libboost-date-time1.33.0 - set of date-time libraries based on generic programming concepts libboost-dbg - Boost.org libraries with debug symbols libboost-dev - Boost.org libraries development files libboost-doc - Boost.org libraries documentation libboost-filesystem-dev - filesystem operations (portable paths, iteration over directories libboost-filesystem1.33.0 - filesystem operations (portable paths, iteration over directories libboost-graph-dev - generic graph components and algorithms in C++ libboost-graph1.33.0 - generic graph components and algorithms in C++ libboost-program-options-dev - program options library for C++ libboost-program-options1.33.0 - program options library for C++ libboost-python-dev - Boost.Python Library development files libboost-python1.33.0 - Boost.Python Library libboost-regex-dev - regular expression library for C++ libboost-regex1.33.0 - regular expression library for C++ libboost-serialization-dev - serialization library for C++ libboost-signals-dev - managed signals and slots library for C++ libboost-signals1.33.0 - managed signals and slots library for C++ libboost-test-dev - components for writing and executing test suites libboost-test1.33.0 - components for writing and executing test suites libboost-thread-dev - portable C++ multi-threading libboost-thread1.33.0 - portable C++ multi-threading Changes: boost (1.32.0+1.33.0-cvs20050720-3) unstable; urgency=low . * Added build dependency on zlib1g-dev. Files: 339be25b79226343b98d60aa6c5f1a2e 1213 libs optional boost_1.32.0+1.33.0-cvs20050720-3.dsc 366c2c86612e017b3606450b081f5ea4 42446 libs optional boost_1.32.0+1.33.0-cvs20050720-3.diff.gz 7ba5d5fdaa322fabac88cc34b0be645d 7466684 doc optional libboost-doc_1.32.0+1.33.0-cvs20050720-3_all.deb fa44b56c7d6163b1eaa1d8ef383a0d35 4413862 libdevel optional libboost-dbg_1.32.0+1.33.0-cvs20050720-3_i386.deb cd91a54c195041b5778c3c1332f98369 1841776 libdevel optional libboost-dev_1.32.0+1.33.0-cvs20050720-3_i386.deb 89cacbe70caa56c55079300cb71d6a55 30234 libs optional libboost-date-time1.33.0_1.32.0+1.33.0-cvs20050720-3_i386.deb add286b55c881a709581f2ca8c1005be 154552 libdevel optional libboost-date-time-dev_1.32.0+1.33.0-cvs20050720-3_i386.deb bc4b7e2e6e25e377735cb701920001b7 39370 libs optional libboost-filesystem1.33.0_1.32.0+1.33.0-cvs20050720-3_i386.deb a609dd022eb167a2d910be789ed29e24 53772 libdevel optional libboost-filesystem-dev_1.32.0+1.33.0-cvs20050720-3_i386.deb e52a393901e1496cadf75c53771a8140 139620 libs optional libboost-graph1.33.0_1.32.0+1.33.0-cvs20050720-3_i386.deb d7b2011400f64de8873f27f1f003f12a 305602 libdevel optional libboost-graph-dev_1.32.0+1.33.0-cvs20050720-3_i386.deb 049efefcc404026ea9afde4ec128c0e6 104544 libs optional libboost-program-options1.33.0_1.32.0+1.33.0-cvs20050720-3_i386.deb 90fc11ad48115e3ef9ff301334130da1 33688 libdevel optional libboost-program-options-dev_1.32.0+1.33.0-cvs20050720-3_i386.deb 2665a6415c7a7ef6ef321aab030edcdd 113638 python optional libboost-python1.33.0_1.32.0+1.33.0-cvs20050720-3_i386.deb 5f38baf17d7ae3fb6a0aff7f4f18ef41 137146 libdevel optional libboost-python-dev_1.32.0+1.33.0-cvs20050720-3_i386.deb 159d0bf9b66ed82321ca5278f3965e93 291158 libs optional libboost-regex1.33.0_1.32.0+1.33.0-cvs20050720-3_i386.deb efc8062b3166b5c84360e6bb18f1f84e 633304 libdevel optional libboost-regex-dev_1.32.0+1.33.0-cvs20050720-3_i386.deb a77fc9267fc11a14788e8a553f7b30e1 400146 libdevel optional libboost-serialization-dev_1.32.0+1.33.0-cvs20050720-3_i386.deb c11104cbd5e97372566e1f27302d1c0d 42980 libs optional libboost-signals1.33.0_1.32.0+1.33.0-cvs20050720-3_i386.deb de7edfa96543db3e65d2ce814ae9bb21 68670 libdevel optional libboost-signals-dev_1.32.0+1.33.0-cvs20050720-3_i386.deb 4b925f356b46b7a458e521aef78c8fac 190208 libs optional libboost-test1.33.0_1.32.0+1.33.0-cvs20050720-3_i386.deb 260079f7a25fa3261011c46bdc53a518 399812 libdevel optional libboost-test-dev_1.32.0+1.33.0-cvs20050720-3_i386.deb 3fda29bcd9564420b1e6bd1f2e59ab41 43928 libs optional
Accepted jigdo 0.7.2-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Jul 2005 13:35:38 +0200 Source: jigdo Binary: jigdo jigdo-file Architecture: source i386 Version: 0.7.2-2 Distribution: unstable Urgency: high Maintainer: Richard Atterer [EMAIL PROTECTED] Changed-By: Richard Atterer [EMAIL PROTECTED] Description: jigdo - GTK+ download manager jigdo-file - Download Debian CD images from any Debian mirror Closes: 319327 Changes: jigdo (0.7.2-2) unstable; urgency=high . * High-urgency upload for RC bugfix. * Closes: #319327: jigdo_0.7.2-1: FTBFS (alpha/unstable): C++ prototype mismatch on 64-bit systems Thanks to Steve Langasek for the good work. * Build with gcc-3.4, not 4.0 due to problems on some arches (see #319327) Files: 1e170d168dcb4326c0c7ca9f198281d4 683 utils extra jigdo_0.7.2-2.dsc e5ca2ea98bbdc479375e21ac02ac6132 5003 utils extra jigdo_0.7.2-2.diff.gz 279af6a738b97096e58e083fcf8325c3 211824 utils extra jigdo_0.7.2-2_i386.deb 12a45b8eb028366087dd8b1bd1895002 233860 utils extra jigdo-file_0.7.2-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC34treeb23IiDVPcRAsTjAJ9ZoVlvbDJ21I8VfBMMXRjK+dzAOACfX5fI sFFHX3Ww3BOU+X0HathACrQ= =x7Qt -END PGP SIGNATURE- Accepted: jigdo-file_0.7.2-2_i386.deb to pool/main/j/jigdo/jigdo-file_0.7.2-2_i386.deb jigdo_0.7.2-2.diff.gz to pool/main/j/jigdo/jigdo_0.7.2-2.diff.gz jigdo_0.7.2-2.dsc to pool/main/j/jigdo/jigdo_0.7.2-2.dsc jigdo_0.7.2-2_i386.deb to pool/main/j/jigdo/jigdo_0.7.2-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libfilesys-diskspace-perl 0.05-8 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Jul 2005 07:36:05 -0400 Source: libfilesys-diskspace-perl Binary: libfilesys-diskspace-perl Architecture: source all Version: 0.05-8 Distribution: unstable Urgency: low Maintainer: Roderick Schertler [EMAIL PROTECTED] Changed-By: Roderick Schertler [EMAIL PROTECTED] Description: libfilesys-diskspace-perl - fetch filesystem size and usage information from Perl Closes: 319171 Changes: libfilesys-diskspace-perl (0.05-8) unstable; urgency=low . * Add magic for jfs, Anton Ivanov (closes: #319171). Files: 6412d3ee8abace862ebb97aa77f9c923 663 perl optional libfilesys-diskspace-perl_0.05-8.dsc 5118370ff488d052aff2c8fb8ea5d900 4809 perl optional libfilesys-diskspace-perl_0.05-8.diff.gz e81c353ac904690b13770b3c995b40ab 8716 perl optional libfilesys-diskspace-perl_0.05-8_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iEYEARECAAYFAkLfiQUACgkQ6QESpysFtzpOJACeP6yBiQ/kD53xeTFf7sVjE3GB J+YAoKSmJXfh2ZQHQ+8saccmyNPRt7/+ =gAQq -END PGP SIGNATURE- Accepted: libfilesys-diskspace-perl_0.05-8.diff.gz to pool/main/libf/libfilesys-diskspace-perl/libfilesys-diskspace-perl_0.05-8.diff.gz libfilesys-diskspace-perl_0.05-8.dsc to pool/main/libf/libfilesys-diskspace-perl/libfilesys-diskspace-perl_0.05-8.dsc libfilesys-diskspace-perl_0.05-8_all.deb to pool/main/libf/libfilesys-diskspace-perl/libfilesys-diskspace-perl_0.05-8_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jackeq 0.4.0-2 (powerpc source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Jul 2005 12:17:14 +0200 Source: jackeq Binary: jackeq Architecture: source powerpc Version: 0.4.0-2 Distribution: unstable Urgency: low Maintainer: Free Ekanayaka [EMAIL PROTECTED] Changed-By: Free Ekanayaka [EMAIL PROTECTED] Description: jackeq - routes and manipulates audio from/to multiple sources Closes: 299350 317200 Changes: jackeq (0.4.0-2) unstable; urgency=low . * Fixed broken watch file * Build depends on libjack0.100.0-dev (closes: #317200) * Using thai-gold as menu icon, not ideal but better than nothing (closes: #299350) * Added .desktop file for GNOME menus Files: 794474d03f0bea0df63a0d1712edf95e 636 sound optional jackeq_0.4.0-2.dsc 5d1f098b24949efd560a9e3b2e7b7876 18042 sound optional jackeq_0.4.0-2.diff.gz f69768e1b96d0779cfeda0e6781881b8 161262 sound optional jackeq_0.4.0-2_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC35PB2PLmgVuXpdIRAhd6AJ41TftiQB5t4xXHkee5tZPejl3jeACfXxw4 MUirLNxlsB/dcP3SWjHxI6s= =g+MK -END PGP SIGNATURE- Accepted: jackeq_0.4.0-2.diff.gz to pool/main/j/jackeq/jackeq_0.4.0-2.diff.gz jackeq_0.4.0-2.dsc to pool/main/j/jackeq/jackeq_0.4.0-2.dsc jackeq_0.4.0-2_powerpc.deb to pool/main/j/jackeq/jackeq_0.4.0-2_powerpc.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted clalsadrv 1.0.1-3 (powerpc source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Jul 2005 12:30:21 +0200 Source: clalsadrv Binary: libclalsadrv1 libclalsadrv-dev Architecture: source powerpc Version: 1.0.1-3 Distribution: unstable Urgency: low Maintainer: Free Ekanayaka [EMAIL PROTECTED] Changed-By: Free Ekanayaka [EMAIL PROTECTED] Description: libclalsadrv-dev - Development file for libclalsadrv libclalsadrv1 - ALSA driver C++ access library Changes: clalsadrv (1.0.1-3) unstable; urgency=low . * Fixed broken Depends line for libclalsadrv-dev depending on the old shared library name Files: c9e386e144880882b37e8802c92f9b97 615 - optional clalsadrv_1.0.1-3.dsc 610ca347c0c7398e70f2b2714970ca4c 3204 - optional clalsadrv_1.0.1-3.diff.gz 2f6b0882616353e637ad7a3e9fc85c8f 11702 devel optional libclalsadrv-dev_1.0.1-3_powerpc.deb 2661ffbb69572e6d4707b61d7ec4169c 12938 libs optional libclalsadrv1_1.0.1-3_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC35GZ2PLmgVuXpdIRAndJAJ9lrTQ/pS2i01nH3QOx1foYKntFAQCgs6+X odunqIGBFiEdgrLxF2D95Yg= =7c91 -END PGP SIGNATURE- Accepted: clalsadrv_1.0.1-3.diff.gz to pool/main/c/clalsadrv/clalsadrv_1.0.1-3.diff.gz clalsadrv_1.0.1-3.dsc to pool/main/c/clalsadrv/clalsadrv_1.0.1-3.dsc libclalsadrv-dev_1.0.1-3_powerpc.deb to pool/main/c/clalsadrv/libclalsadrv-dev_1.0.1-3_powerpc.deb libclalsadrv1_1.0.1-3_powerpc.deb to pool/main/c/clalsadrv/libclalsadrv1_1.0.1-3_powerpc.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted zsh-beta 4.3.0-dev-1+20050720-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Jul 2005 09:05:43 -0400 Source: zsh-beta Binary: zsh-beta-static zsh-beta-doc zsh-beta Architecture: source all Version: 4.3.0-dev-1+20050720-1 Distribution: unstable Urgency: low Maintainer: Clint Adams [EMAIL PROTECTED] Changed-By: Clint Adams [EMAIL PROTECTED] Description: zsh-beta - A shell with lots of features (dev tree) zsh-beta-doc - zsh beta documentation - info/HTML format Changes: zsh-beta (4.3.0-dev-1+20050720-1) unstable; urgency=low . * Update to HEAD. Files: 4ae43b96044ba53fc90ecf327985e0a0 745 shells optional zsh-beta_4.3.0-dev-1+20050720-1.dsc ccd1a276fec860287807c7c542c99e00 2143803 shells optional zsh-beta_4.3.0-dev-1+20050720.orig.tar.gz 0e588c6247d30702f835e11213b3e419 732184 shells optional zsh-beta_4.3.0-dev-1+20050720-1.diff.gz 4953fcc00b10361399dd628bc1509f7f 661060 shells optional zsh-beta-doc_4.3.0-dev-1+20050720-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Debian! iD8DBQFC36IR5m0u66uWM3ARAgujAJ9FTW7/KTC05YcBozW1E1dOtbpEbwCgo5PN 1U/qC+2QRLcYIOgScByDDvg= =TiSj -END PGP SIGNATURE- Accepted: zsh-beta-doc_4.3.0-dev-1+20050720-1_all.deb to pool/main/z/zsh-beta/zsh-beta-doc_4.3.0-dev-1+20050720-1_all.deb zsh-beta_4.3.0-dev-1+20050720-1.diff.gz to pool/main/z/zsh-beta/zsh-beta_4.3.0-dev-1+20050720-1.diff.gz zsh-beta_4.3.0-dev-1+20050720-1.dsc to pool/main/z/zsh-beta/zsh-beta_4.3.0-dev-1+20050720-1.dsc zsh-beta_4.3.0-dev-1+20050720.orig.tar.gz to pool/main/z/zsh-beta/zsh-beta_4.3.0-dev-1+20050720.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted xfe 0.84-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Jul 2005 09:10:41 +0200 Source: xfe Binary: xfe Architecture: source i386 Version: 0.84-2 Distribution: unstable Urgency: low Maintainer: Bastian Kleineidam [EMAIL PROTECTED] Changed-By: Bastian Kleineidam [EMAIL PROTECTED] Description: xfe- lightweight file manager for X11 Closes: 301125 Changes: xfe (0.84-2) unstable; urgency=low . * Use new watch file format and qa.debian SF redirector * Ignore mount points with missing (read) permission (Closes: #301125) Files: bac10b850c5407e57db4fada5ee323ae 634 x11 optional xfe_0.84-2.dsc 138525ea23fa9e032312d5cf06254df9 17813 x11 optional xfe_0.84-2.diff.gz c229cbef48b952f957d834f41e134a28 806254 x11 optional xfe_0.84-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC36gkeBwlBDLsbz4RAoxuAKCSjkMNB51WCcAll6wx6MF+uiGg2ACfXxlV 0OgSrEPgrGRFuRuFVEwkmfQ= =wgzX -END PGP SIGNATURE- Accepted: xfe_0.84-2.diff.gz to pool/main/x/xfe/xfe_0.84-2.diff.gz xfe_0.84-2.dsc to pool/main/x/xfe/xfe_0.84-2.dsc xfe_0.84-2_i386.deb to pool/main/x/xfe/xfe_0.84-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted sharutils 1:4.2.1-15 (powerpc all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Jul 2005 16:08:44 +0200 Source: sharutils Binary: sharutils-doc sharutils Architecture: source powerpc all Version: 1:4.2.1-15 Distribution: unstable Urgency: medium Maintainer: Santiago Vila [EMAIL PROTECTED] Changed-By: Santiago Vila [EMAIL PROTECTED] Description: sharutils - shar, unshar, uuencode, uudecode sharutils-doc - Documentation for GNU sharutils Closes: 319325 Changes: sharutils (1:4.2.1-15) unstable; urgency=medium . * Fixed mail-files call to the mail utility, which was broken in all archs except mine due to a missing build-dependency (Closes: #319325). Hardcode mail as the utility to be used (no need to add build-depends). * Added Suggests: mailx (you might want to use uuencode but not mail-files). * Removed way obsolete dependency on debianutils. Files: ff4190063276d21411db83005e1aaf92 626 utils standard sharutils_4.2.1-15.dsc 71cf9fada00fc6dfe11b5ade512c3b15 8633 utils standard sharutils_4.2.1-15.diff.gz 49c93498a2dd22660358c5d9f4f8ff12 28114 doc optional sharutils-doc_4.2.1-15_all.deb d0ebdbfbda971dd906620f649fb2b7f5 112990 utils standard sharutils_4.2.1-15_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC36zjd9Uuvj7yPNYRArnTAJ9Vi0BYXkF+IlbL+E+WkKqJdmNwNwCdGQ5F Bb0jfb8gbCzjT++flSkxEPE= =39p2 -END PGP SIGNATURE- Accepted: sharutils-doc_4.2.1-15_all.deb to pool/main/s/sharutils/sharutils-doc_4.2.1-15_all.deb sharutils_4.2.1-15.diff.gz to pool/main/s/sharutils/sharutils_4.2.1-15.diff.gz sharutils_4.2.1-15.dsc to pool/main/s/sharutils/sharutils_4.2.1-15.dsc sharutils_4.2.1-15_powerpc.deb to pool/main/s/sharutils/sharutils_4.2.1-15_powerpc.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gnutls12 1.2.5-3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Changed-By: Matthias Urlichs [EMAIL PROTECTED] Date: Thu, 21 Jul 2005 13:19:25 +0200 Version: 1.2.5-3 Distribution: unstable Source: gnutls12 Urgency: high Maintainer: Matthias Urlichs [EMAIL PROTECTED] Binary: gnutls-bin libgnutls-dev libgnutls12 libgnutls12-dbg Architecture: i386 source Closes: 319291 Changes: gnutls12 (1.2.5-3) unstable; urgency=high . * Updated libgnutls12.shlibs file. Thanks to Mike Paul [EMAIL PROTECTED]. Closes: #319291: libgnutls12: Wrong soversion in shlibs file; breaks dependencies on this library Description: libgnutls12 - the GNU TLS library - runtime library gnutls-bin - the GNU TLS library - commandline utilities libgnutls12-dbg - GNU TLS library - debugger symbols libgnutls-dev - the GNU TLS library - development files Files: 2935417e717e709f756977cad12f62cb 773 devel optional gnutls12_1.2.5-3.dsc c755b7021e565a9c6694e4560a6b8d40 357192 libs important libgnutls12_1.2.5-3_i386.deb ef7af22addfe5da5af9e5bd2453f9238 733292 devel optional libgnutls12-dbg_1.2.5-3_i386.deb 3cb41bac60c1653107d65bd5fa393b13 425694 libdevel optional libgnutls-dev_1.2.5-3_i386.deb e57112f3b48c489962104ac9dc24e472 263392 net optional gnutls-bin_1.2.5-3_i386.deb 6290a99c817dfcd61614f5d196fbfb97 293273 devel optional gnutls12_1.2.5-3.diff.gz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC37U88+hUANcKr/kRAoBBAJ41h1jLK4+kCQtW9H74/7AE/AbpXQCfflrA R/HvwXMT76+JelH58BGrYQc= =dUcm -END PGP SIGNATURE- Accepted: gnutls-bin_1.2.5-3_i386.deb to pool/main/g/gnutls12/gnutls-bin_1.2.5-3_i386.deb gnutls12_1.2.5-3.diff.gz to pool/main/g/gnutls12/gnutls12_1.2.5-3.diff.gz gnutls12_1.2.5-3.dsc to pool/main/g/gnutls12/gnutls12_1.2.5-3.dsc libgnutls-dev_1.2.5-3_i386.deb to pool/main/g/gnutls12/libgnutls-dev_1.2.5-3_i386.deb libgnutls12-dbg_1.2.5-3_i386.deb to pool/main/g/gnutls12/libgnutls12-dbg_1.2.5-3_i386.deb libgnutls12_1.2.5-3_i386.deb to pool/main/g/gnutls12/libgnutls12_1.2.5-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted 6tunnel 0.11rc1-1 (powerpc source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Jul 2005 16:26:46 +0200 Source: 6tunnel Binary: 6tunnel Architecture: source powerpc Version: 0.11rc1-1 Distribution: unstable Urgency: low Maintainer: Thomas Seyrat [EMAIL PROTECTED] Changed-By: Thomas Seyrat [EMAIL PROTECTED] Description: 6tunnel- TCP proxy for non-IPv6 applications Closes: 313193 Changes: 6tunnel (0.11rc1-1) unstable; urgency=low . * New upstream release (closes: #313193) * New upstream URL * Bumped Standards-Version to 3.6.2 Files: 1316ec40a43a37a2a1e4b343d137eb4a 568 net optional 6tunnel_0.11rc1-1.dsc b325fa9d238e32195fbb3fc3646b0d28 38126 net optional 6tunnel_0.11rc1.orig.tar.gz b10cb506fea70ef11cc9a074ff0d849e 1642 net optional 6tunnel_0.11rc1-1.diff.gz 11e640efe90539b8438799cd6319fb23 10844 net optional 6tunnel_0.11rc1-1_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC37GaG7q+HrSg3okRAioPAJ9OSiHQANLhenObTGwlEpg6YmV+XACeKE+j q9ZLJ6Cj6HEFzopkak/QUPU= =38ct -END PGP SIGNATURE- Accepted: 6tunnel_0.11rc1-1.diff.gz to pool/main/6/6tunnel/6tunnel_0.11rc1-1.diff.gz 6tunnel_0.11rc1-1.dsc to pool/main/6/6tunnel/6tunnel_0.11rc1-1.dsc 6tunnel_0.11rc1-1_powerpc.deb to pool/main/6/6tunnel/6tunnel_0.11rc1-1_powerpc.deb 6tunnel_0.11rc1.orig.tar.gz to pool/main/6/6tunnel/6tunnel_0.11rc1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted viewcvs 0.9.2+cvs.1.0.dev.2004.07.28-4 (all source)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 21 Jul 2005 17:15:21 +0200
Source: viewcvs
Binary: viewcvs-query viewcvs
Architecture: source all
Version: 0.9.2+cvs.1.0.dev.2004.07.28-4
Distribution: unstable
Urgency: low
Maintainer: David MartÃnez Moreno [EMAIL PROTECTED]
Changed-By: David MartÃnez Moreno [EMAIL PROTECTED]
Description:
viewcvs- view CVS Repositories via HTTP
viewcvs-query - view CVS (viewcvs-query.cgi)
Closes: 196975 239968 293426 293529 318953
Changes:
viewcvs (0.9.2+cvs.1.0.dev.2004.07.28-4) unstable; urgency=low
.
* File contents are now visible. Thanks, Marius Gedminas! (closes: #239968).
* debian/po/cs.po: Added Czech translation. Thanks, Miroslav Kure! (closes:
#318953).
* www/cgi/viewcvs.cgi: Added code to return response for robots in order to
not index the site. Thanks, Kai Hendry. Closes: #196975.
* templates/markup.ezt: Added a trivial patch to split log info from file
content. Thanks, Guillem Jover. Closes: #293426.
* viewcvs-install-debian: Include svndbadmin in the contents of the viewcvs
package (closes: #293529).
* debian/control:
- Update Standards-Version to 3.6.2.
- Added ${python:Depends} to viewcvs-query to shut up lintian.
- Build-Depends line was really Build-Depends-Indep.
- Added apache to Recommends, as Policy Manual says that it needs at least
one real package.
Files:
6cbd8ecae3a1c69cf4b5ad7a51fbe533 752 devel optional
viewcvs_0.9.2+cvs.1.0.dev.2004.07.28-4.dsc
a4e24c4db9610fd86c5a062f2c648244 46886 devel optional
viewcvs_0.9.2+cvs.1.0.dev.2004.07.28-4.diff.gz
80e3f2cece5c611c2e9927f453c3f9da 209828 devel optional
viewcvs_0.9.2+cvs.1.0.dev.2004.07.28-4_all.deb
8ef372eaa3e64f940fd386feecd9f96e 1750 devel optional
viewcvs-query_0.9.2+cvs.1.0.dev.2004.07.28-4_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFC37xOWs/EhA1iABsRAg5RAJ0WIH4rgoiUmeru0j7blYNjWfUCYQCg740l
7Z9Vx9VdoB45ijWMw/Bhsyc=
=sTN6
-END PGP SIGNATURE-
Accepted:
viewcvs-query_0.9.2+cvs.1.0.dev.2004.07.28-4_all.deb
to pool/main/v/viewcvs/viewcvs-query_0.9.2+cvs.1.0.dev.2004.07.28-4_all.deb
viewcvs_0.9.2+cvs.1.0.dev.2004.07.28-4.diff.gz
to pool/main/v/viewcvs/viewcvs_0.9.2+cvs.1.0.dev.2004.07.28-4.diff.gz
viewcvs_0.9.2+cvs.1.0.dev.2004.07.28-4.dsc
to pool/main/v/viewcvs/viewcvs_0.9.2+cvs.1.0.dev.2004.07.28-4.dsc
viewcvs_0.9.2+cvs.1.0.dev.2004.07.28-4_all.deb
to pool/main/v/viewcvs/viewcvs_0.9.2+cvs.1.0.dev.2004.07.28-4_all.deb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fml 4.0.3-2 (all source)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Fri, 22 Jul 2005 01:08:45 +0900
Source: fml
Binary: fml-doc fml
Architecture: source all
Version: 4.0.3-2
Distribution: unstable
Urgency: low
Maintainer: Fumitoshi UKAI [EMAIL PROTECTED]
Changed-By: Fumitoshi UKAI [EMAIL PROTECTED]
Description:
fml- Mailing List Server Package
fml-doc- Documentation of fml ML Server Package
Closes: 319225
Changes:
fml (4.0.3-2) unstable; urgency=low
.
* fix FTBFS on ppc64. apply patches of Andreas Jochens.
use config.{guess,sub} of autotools-dev
add build-depends on autotools-dev
closes: Bug#319225
Files:
82432a63bf8ee0f063c1ea84bd8c1479 567 mail extra fml_4.0.3-2.dsc
4ac767cf60c1dd4802ad819b847d9522 27293 mail extra fml_4.0.3-2.diff.gz
4ad2c3fce3fe1d3601f2303ae6a2cf90 1256994 mail extra fml_4.0.3-2_all.deb
15859eec3f1f59af88b9af78cba1b4c9 1463866 mail extra fml-doc_4.0.3-2_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFC38mG9D5yZjzIjAkRArA3AJ4gk3WLnwbNrLoEMaZiRvFOglkGEQCgr7yO
WIe2gYaGV+9rxEi0bREchoM=
=9unU
-END PGP SIGNATURE-
Accepted:
fml-doc_4.0.3-2_all.deb
to pool/main/f/fml/fml-doc_4.0.3-2_all.deb
fml_4.0.3-2.diff.gz
to pool/main/f/fml/fml_4.0.3-2.diff.gz
fml_4.0.3-2.dsc
to pool/main/f/fml/fml_4.0.3-2.dsc
fml_4.0.3-2_all.deb
to pool/main/f/fml/fml_4.0.3-2_all.deb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted liblivemedia 2005.07.21-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Jul 2005 16:36:47 +0200 Source: liblivemedia Binary: livemedia-utils liblivemedia-dev Architecture: source i386 Version: 2005.07.21-1 Distribution: unstable Urgency: low Maintainer: Sam Hocevar (Debian packages) [EMAIL PROTECTED] Changed-By: Sam Hocevar (Debian packages) [EMAIL PROTECTED] Description: liblivemedia-dev - multimedia RTSP streaming library livemedia-utils - multimedia RTSP streaming tools Changes: liblivemedia (2005.07.21-1) unstable; urgency=low . * New upstream release. Files: 5d956a38e283c946c1e38a347f71dccf 634 libs optional liblivemedia_2005.07.21-1.dsc dcd916fcb1e8b3292306edfb3b66e010 547123 libs optional liblivemedia_2005.07.21.orig.tar.gz 4b29c2d4f61164bf1309435cb793ef2f 29125 libs optional liblivemedia_2005.07.21-1.diff.gz b1d470bceaf70769b631e6c4d16047e7 821924 libdevel optional liblivemedia-dev_2005.07.21-1_i386.deb 8beff8b56d58d0d309b9c87e2d591e94 1309644 net optional livemedia-utils_2005.07.21-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC389+fPP1rylJn2ERAmr7AJ9blr+dn7FviayJxvEb5ynM8/G7ZgCfY9Mn GxQ423kepfA6WG8EyRmX9GI= =h5AH -END PGP SIGNATURE- Accepted: liblivemedia-dev_2005.07.21-1_i386.deb to pool/main/libl/liblivemedia/liblivemedia-dev_2005.07.21-1_i386.deb liblivemedia_2005.07.21-1.diff.gz to pool/main/libl/liblivemedia/liblivemedia_2005.07.21-1.diff.gz liblivemedia_2005.07.21-1.dsc to pool/main/libl/liblivemedia/liblivemedia_2005.07.21-1.dsc liblivemedia_2005.07.21.orig.tar.gz to pool/main/libl/liblivemedia/liblivemedia_2005.07.21.orig.tar.gz livemedia-utils_2005.07.21-1_i386.deb to pool/main/libl/liblivemedia/livemedia-utils_2005.07.21-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fetchmail 6.2.5-15 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Jul 2005 13:25:10 -0300 Source: fetchmail Binary: fetchmailconf fetchmail-ssl fetchmail Architecture: source i386 all Version: 6.2.5-15 Distribution: unstable Urgency: high Maintainer: Fetchmail Maintainers [EMAIL PROTECTED] Changed-By: Lucas Wall [EMAIL PROTECTED] Description: fetchmail - SSL enabled POP3, APOP, IMAP mail gatherer/forwarder fetchmail-ssl - SSL enabled POP3, APOP, IMAP mail gatherer/forwarder fetchmailconf - fetchmail configurator Closes: 212762 Changes: fetchmail (6.2.5-15) unstable; urgency=high . * Nico Golde: - fixed buffer overrun in pop3 UIDs handling CAN-2005-2335 http://fetchmail.berlios.de/fetchmail-SA-2005-01.txt (closes: #212762) Files: 8911c7350a00e2dfa9d4dd3a3a0b44c3 818 mail optional fetchmail_6.2.5-15.dsc c9cbcab2586b83f88e4c11017f018782 134079 mail optional fetchmail_6.2.5-15.diff.gz e6a55132dd5061695938ab12fe1c2444 101556 mail optional fetchmailconf_6.2.5-15_all.deb 9e26c70d872dee8d3f30470ce83174f5 42522 mail optional fetchmail-ssl_6.2.5-15_all.deb d7a27eacf72669ef78ba03b32a91d6b1 547014 mail optional fetchmail_6.2.5-15_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC39F4vJtHM4T7RtYRAq4DAKCj+/9QitI2FdNx6fOQ1gO4uN+O1wCeJ1ix UdMdbMYp4WrszoQgeiMoLmo= =PJl0 -END PGP SIGNATURE- Accepted: fetchmail-ssl_6.2.5-15_all.deb to pool/main/f/fetchmail/fetchmail-ssl_6.2.5-15_all.deb fetchmail_6.2.5-15.diff.gz to pool/main/f/fetchmail/fetchmail_6.2.5-15.diff.gz fetchmail_6.2.5-15.dsc to pool/main/f/fetchmail/fetchmail_6.2.5-15.dsc fetchmail_6.2.5-15_i386.deb to pool/main/f/fetchmail/fetchmail_6.2.5-15_i386.deb fetchmailconf_6.2.5-15_all.deb to pool/main/f/fetchmail/fetchmailconf_6.2.5-15_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mftrace 1.1.12-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Jul 2005 17:35:58 +0100 Source: mftrace Binary: mftrace Architecture: source i386 Version: 1.1.12-2 Distribution: unstable Urgency: low Maintainer: Julian Gilbey [EMAIL PROTECTED] Changed-By: Julian Gilbey [EMAIL PROTECTED] Description: mftrace- Converts Metafont fonts into Type1 fonts Closes: 319341 Changes: mftrace (1.1.12-2) unstable; urgency=low . * Fix configure so it doesn't build-depend on potrace (closes: #319341) Files: 3bee0a2155d0c16a2765ee29ff19abaa 595 tex extra mftrace_1.1.12-2.dsc 9b347fbfe02521fc0a276177851bbaea 36615 tex extra mftrace_1.1.12-2.diff.gz 913d626c57a408aa17eaae8093d1e64a 43286 tex extra mftrace_1.1.12-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC39GTDU59w/205FkRAhTqAJ4zq65H4IU0w2GEPS1slyH3+z/ZbwCfSAE3 YX/1IPHXJtp8s60l0xBc1Pk= =W5n+ -END PGP SIGNATURE- Accepted: mftrace_1.1.12-2.diff.gz to pool/main/m/mftrace/mftrace_1.1.12-2.diff.gz mftrace_1.1.12-2.dsc to pool/main/m/mftrace/mftrace_1.1.12-2.dsc mftrace_1.1.12-2_i386.deb to pool/main/m/mftrace/mftrace_1.1.12-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted dvi2dvi 2.0alpha-5.1 (powerpc source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Jul 2005 19:40:53 +0100 Source: dvi2dvi Binary: dvi2dvi Architecture: source powerpc Version: 2.0alpha-5.1 Distribution: unstable Urgency: low Maintainer: Masayuki Hatta (mhatta) [EMAIL PROTECTED] Changed-By: Roger Leigh [EMAIL PROTECTED] Description: dvi2dvi- Tweak DVI files Closes: 285646 Changes: dvi2dvi (2.0alpha-5.1) unstable; urgency=low . * Non-maintainer upload. * debian/rules: Add -DSYSV -DANSI to CCFLAGS when building, to fix GCC 4.0 build errors due to old KR C syntax (Closes: #285646). * decompfont.c, fontdesc.c: Cast unsigned char * to char * to eliminate a number of compiler warnings when performing string operations on the byte data type. Files: 6a02206e5a5b87592e0611d2eaa44455 600 tex optional dvi2dvi_2.0alpha-5.1.dsc 3cfb9521d8b0d0babfabca93489e249b 5819 tex optional dvi2dvi_2.0alpha-5.1.diff.gz 61c03ba6ecf2540501a95d11a30489cb 38990 tex optional dvi2dvi_2.0alpha-5.1_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC39U2VcFcaSW/uEgRAlsEAJ4+Stx68bSa6aZxXhLjyjfecdTJNQCfe5aA q8BrokuI9aVBqgoCDSCjUe0= =aLQh -END PGP SIGNATURE- Accepted: dvi2dvi_2.0alpha-5.1.diff.gz to pool/main/d/dvi2dvi/dvi2dvi_2.0alpha-5.1.diff.gz dvi2dvi_2.0alpha-5.1.dsc to pool/main/d/dvi2dvi/dvi2dvi_2.0alpha-5.1.dsc dvi2dvi_2.0alpha-5.1_powerpc.deb to pool/main/d/dvi2dvi/dvi2dvi_2.0alpha-5.1_powerpc.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted linux-2.6 2.6.12-1 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Jul 2005 17:16:04 -0400 Source: linux-2.6 Binary: linux-image-2.6.12-1-k7 linux-headers-2.6.12-1-386 linux-headers-2.6.12-1-em64t-p4 linux-headers-2.6.12-1-s390x linux-image-2.6.12-1-itanium-smp linux-image-2.6.12-1-386 linux-headers-2.6.12-1-itanium linux-headers-2.6.12-1-amd64-generic linux-image-2.6.12-1-amd64-k8 linux-tree-2.6.12 linux-image-2.6.12-1-alpha-generic linux-doc-2.6.12 linux-headers-2.6.12-1-mckinley-smp linux-image-2.6.12-1-s390x linux-image-2.6.12-1-sparc64 linux-headers-2.6.12-1-sparc64-smp linux-headers-2.6.12-1-powerpc-smp linux-image-2.6.12-1-mckinley-smp linux-headers-2.6.12-1-k7 linux-image-2.6.12-1-k7-smp linux-headers-2.6.12-1 linux-image-2.6.12-1-alpha-smp linux-image-2.6.12-1-powerpc-smp linux-image-2.6.12-1-em64t-p4-smp linux-image-2.6.12-1-amd64-generic linux-image-2.6.12-1-amd64-k8-smp linux-image-2.6.12-1-mckinley linux-headers-2.6.12-1-em64t-p4-smp linux-headers-2.6.12-1-powerpc linux-image-2.6.12-1-sparc64-smp linux-image-2.6.12-1-powerpc linux-image-2.6.12-1-686-smp linux-headers-2.6.12-1-686 linux-headers-2.6.12-1-itanium-smp linux-headers-2.6.12-1-amd64-k8 linux-headers-2.6.12-1-alpha-smp linux-headers-2.6.12-1-alpha-generic linux-headers-2.6.12-1-sparc64 linux-headers-2.6.12-1-686-smp linux-headers-2.6.12-1-s390 linux-image-2.6.12-1-s390 linux-headers-2.6.12-1-k7-smp linux-image-2.6.12-1-em64t-p4 linux-headers-2.6.12-1-amd64-k8-smp linux-image-2.6.12-1-686 linux-source-2.6.12 linux-headers-2.6.12-1-mckinley linux-patch-debian-2.6.12 linux-image-2.6.12-1-itanium Architecture: source all i386 Version: 2.6.12-1 Distribution: unstable Urgency: low Maintainer: Debian Kernel Team debian-kernel@lists.debian.org Changed-By: Andres Salomon [EMAIL PROTECTED] Description: linux-doc-2.6.12 - Linux kernel specific documentation for version 2.6.12 linux-headers-2.6.12-1 - Common architecture-specific header files for Linux kernel 2.6.12 linux-headers-2.6.12-1-386 - Architecture-specific header files for Linux kernel 2.6.12 on 386 linux-headers-2.6.12-1-686 - Architecture-specific header files for Linux kernel 2.6.12 on PPr linux-headers-2.6.12-1-686-smp - Architecture-specific header files for Linux kernel 2.6.12 on mul linux-headers-2.6.12-1-k7 - Architecture-specific header files for Linux kernel 2.6.12 on AMD linux-headers-2.6.12-1-k7-smp - Architecture-specific header files for Linux kernel 2.6.12 on mul linux-image-2.6.12-1-386 - Linux kernel 2.6.12 image on 386-class machines linux-image-2.6.12-1-686 - Linux kernel 2.6.12 image on PPro/Celeron/PII/PIII/P4 machines linux-image-2.6.12-1-686-smp - Linux kernel 2.6.12 image on multi-processor PPro/Celeron/PII/PII linux-image-2.6.12-1-k7 - Linux kernel 2.6.12 image on AMD Duron/Athlon/AthlonXP machines linux-image-2.6.12-1-k7-smp - Linux kernel 2.6.12 image on multi-processor AMD Duron/Athlon/Ath linux-patch-debian-2.6.12 - Debian patches to version 2.6.12 of the Linux kernel linux-source-2.6.12 - Linux kernel source for version 2.6.12 with Debian patches linux-tree-2.6.12 - Linux kernel source tree for building Debian kernel images Closes: 250468 260003 318121 Changes: linux-2.6 (2.6.12-1) unstable; urgency=low . * New upstream release: - git rocks - address space randomization - conversion of ide driver code to the device model - restored Philips webcam driver - new Broadcom bcm5706 gigabit driver - new resource limits for the audio community - Multipath device mapper - Intel HD Audio alsa driver - fixes + arch updates.. - readdition of tg3 driver, as firmware license has been fixed . * Dropped the following patches: - patch-2.6.11.*.patch (merged) - powerpc-ppc64-ibmvscsi.patch (Christoph didn't like it, and it failed to build anyways) (Sven Luther) - doc-post_halloween.patch (unless someone can come up w/ a valid reason for carrying around rapidly bitrotting documentation...) (Andres Salomon) - sparc32-hypersparc-srmmu.patch (dropped until sparc32 is working again, and we can figure out whether it's necessary) - fix-alpha-ext3-oops.patch (no longer needed, fixed by compiler) - x86-i486_emu.patch (buggy and insecure 80486 instruction emulation for 80386; we're no longer supporting this) (closes: #250468) - amd64-outs.patch (according to http://www.ussg.iu.edu/hypermail/linux/kernel/0502.3/1095.html, this is unnecessary for us) (Andres Salomon) - sparc64-rtc-mostek.patch (merged) - sparc64-compat-nanoseconds.patch (merged) - sparc64-sunsu-init-2.6.11.patch (merged) - sunsab-uart-update-timeout.patch (merged) - alpha-read-trylock.patch (different version got merged) - powerpc-prep-motorola-irq-fix.patch (merged) - drivers-media-video-saa7134-update.patch (merged) - drivers-media-video-saa7134-update-2.patch (merged) -
Accepted devscripts 2.9.2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Jul 2005 12:57:47 -0400 Source: devscripts Binary: devscripts Architecture: source i386 Version: 2.9.2 Distribution: unstable Urgency: low Maintainer: Julian Gilbey [EMAIL PROTECTED] Changed-By: Joey Hess [EMAIL PROTECTED] Description: devscripts - Scripts to make the life of a Debian Package maintainer easier Closes: 319367 Changes: devscripts (2.9.2) unstable; urgency=low . [ Julian Gilbey ] * debcommit: fix recognition of cvs trees . [ Joey Hess ] * bts: Fix over-broad cgi url mangling to avoid mangling urls that are part of bug reports. * bts: fix retitle command, broken by extra param change in 2.9. Closes: #319367 Files: 447ff33ee3903c18a8cb6cf1ff1bafa9 660 devel optional devscripts_2.9.2.dsc 066e3c384d549c477a9d8b1af1a623aa 198518 devel optional devscripts_2.9.2.tar.gz 3fff12bd01c36eb437c338ecd8d1c3a7 217912 devel optional devscripts_2.9.2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC39TX2tp5zXiKP0wRAubOAKDELahG5DCnTC7Qh2qZa0X8YkoMzACgpJbf 9xy11skaBKC7i6ZZhCB102g= =vQP+ -END PGP SIGNATURE- Accepted: devscripts_2.9.2.dsc to pool/main/d/devscripts/devscripts_2.9.2.dsc devscripts_2.9.2.tar.gz to pool/main/d/devscripts/devscripts_2.9.2.tar.gz devscripts_2.9.2_i386.deb to pool/main/d/devscripts/devscripts_2.9.2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted tdiary 2.0.2-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Jul 2005 22:44:53 +0900 Source: tdiary Binary: tdiary-plugin tdiary tdiary-mode tdiary-contrib tdiary-theme Architecture: source all Version: 2.0.2-1 Distribution: unstable Urgency: high Maintainer: Taku YASUI [EMAIL PROTECTED] Changed-By: Daigo Moriwaki [EMAIL PROTECTED] Description: tdiary - a communication-friendly weblog system tdiary-contrib - Plugins of tDiary to add functionalities tdiary-mode - tDiary editing mode for Emacsen tdiary-plugin - Plugins of tDiary to add functionalities tdiary-theme - Themes of tDiary to change the design Closes: 319315 Changes: tdiary (2.0.2-1) unstable; urgency=high . * New upstream release * (urgency high) A 'Cross-Site Request Forgeries (CSRF)' vulnerability has been fixed (closes: #319315). * debian/rule: add lines to fix permissions. * debian/control: update Standards-Version to follow the latest The Debian Policy. Files: 8686b120ad5779b5c48d33969e607f68 688 web optional tdiary_2.0.2-1.dsc 45493d43ff8b784f889fc57cdefd21a4 2283487 web optional tdiary_2.0.2.orig.tar.gz 20d6f1c02406694dc64bae8cbf1574c5 20387 web optional tdiary_2.0.2-1.diff.gz b0e55fdfd5ae56eb380d0f8a443455c8 583466 web optional tdiary_2.0.2-1_all.deb 43296d72026a1dd0dc43b350f613360c 1510088 web optional tdiary-theme_2.0.2-1_all.deb 24322856e0c249181c3d5dfe6e897b00 156420 web optional tdiary-plugin_2.0.2-1_all.deb edf66942ea5c4b7a117253a48286fc5a 27308 web optional tdiary-mode_2.0.2-1_all.deb 9053ad0afde2563ffe20d9b3fc159461 137458 web optional tdiary-contrib_2.0.2-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC386HFwU5DuZsm7ARAv55AKCuWks28CAvRwQDpf4nIDD19YOVqwCfWZ2h B3kipCHckhK7cAA2vzYeIzQ= =6Ohw -END PGP SIGNATURE- Accepted: tdiary-contrib_2.0.2-1_all.deb to pool/main/t/tdiary/tdiary-contrib_2.0.2-1_all.deb tdiary-mode_2.0.2-1_all.deb to pool/main/t/tdiary/tdiary-mode_2.0.2-1_all.deb tdiary-plugin_2.0.2-1_all.deb to pool/main/t/tdiary/tdiary-plugin_2.0.2-1_all.deb tdiary-theme_2.0.2-1_all.deb to pool/main/t/tdiary/tdiary-theme_2.0.2-1_all.deb tdiary_2.0.2-1.diff.gz to pool/main/t/tdiary/tdiary_2.0.2-1.diff.gz tdiary_2.0.2-1.dsc to pool/main/t/tdiary/tdiary_2.0.2-1.dsc tdiary_2.0.2-1_all.deb to pool/main/t/tdiary/tdiary_2.0.2-1_all.deb tdiary_2.0.2.orig.tar.gz to pool/main/t/tdiary/tdiary_2.0.2.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted eagle 4.11-10 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Jul 2005 10:58:07 -0700 Source: eagle Binary: eagle-data eagle Architecture: source i386 all Version: 4.11-10 Distribution: unstable Urgency: low Maintainer: Shaun Jackman [EMAIL PROTECTED] Changed-By: Shaun Jackman [EMAIL PROTECTED] Description: eagle - Printed circuit board design tool eagle-data - Data files for Eagle Closes: 319373 Changes: eagle (4.11-10) unstable; urgency=low . * Add the Czech translation of the debconf messages. Closes: #319373. Thanks to Katarina Machalkova. Files: f15108efa3cc9a770e4a5033dfd87247 593 non-free/electronics optional eagle_4.11-10.dsc 6d04c6587116b44b330f27fcc39fc5c4 7979 non-free/electronics optional eagle_4.11-10.diff.gz f8d380802e611f1e4da9845daf72ae96 4056612 non-free/electronics optional eagle-data_4.11-10_all.deb 8b45fadfc9d42be7b02885a6d32dea7e 2764208 non-free/electronics optional eagle_4.11-10_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC3+RtvFdYF1IwUUoRAj9NAJ9gzYl0OKgmsLXcMN3GoLc/q60F8ACg1Ft4 Tvstn44TB9yxdtsHmGB5bTg= =+X6U -END PGP SIGNATURE- Accepted: eagle-data_4.11-10_all.deb to pool/non-free/e/eagle/eagle-data_4.11-10_all.deb eagle_4.11-10.diff.gz to pool/non-free/e/eagle/eagle_4.11-10.diff.gz eagle_4.11-10.dsc to pool/non-free/e/eagle/eagle_4.11-10.dsc eagle_4.11-10_i386.deb to pool/non-free/e/eagle/eagle_4.11-10_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted ocamlnet 1.0-3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Jul 2005 20:05:48 +0200 Source: ocamlnet Binary: libocamlnet-ocaml libocamlnet-ocaml-dev Architecture: source i386 Version: 1.0-3 Distribution: unstable Urgency: low Maintainer: Stefano Zacchiroli [EMAIL PROTECTED] Changed-By: Stefano Zacchiroli [EMAIL PROTECTED] Description: libocamlnet-ocaml - OCaml application-level Internet protocols and conventions librar libocamlnet-ocaml-dev - OCaml application-level Internet protocols and conventions librar Changes: ocamlnet (1.0-3) unstable; urgency=low . * fixed bug in preinst which inhibit clean up of old diversions Files: 4a67640e1294fe57f3b5e7c01dec0a04 666 devel optional ocamlnet_1.0-3.dsc f8d477abcdf0da6c61f14ea06ff47bda 5507 devel optional ocamlnet_1.0-3.diff.gz 6c9dda34e0ce73215f485635f2c79e8e 1452224 libdevel optional libocamlnet-ocaml-dev_1.0-3_i386.deb eec23f8e658749ae05c599869fadc79c 10438 libs optional libocamlnet-ocaml_1.0-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC3+mC1cqbBPLEI7wRAiRFAJ908U/y3eswukDz/rSWuZMi2P+lgwCdFmVS 2ACHnbkNsGf/HZF6fycGUb4= =C0UR -END PGP SIGNATURE- Accepted: libocamlnet-ocaml-dev_1.0-3_i386.deb to pool/main/o/ocamlnet/libocamlnet-ocaml-dev_1.0-3_i386.deb libocamlnet-ocaml_1.0-3_i386.deb to pool/main/o/ocamlnet/libocamlnet-ocaml_1.0-3_i386.deb ocamlnet_1.0-3.diff.gz to pool/main/o/ocamlnet/ocamlnet_1.0-3.diff.gz ocamlnet_1.0-3.dsc to pool/main/o/ocamlnet/ocamlnet_1.0-3.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gaim 1:1.4.0-3 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Format: 1.7 Date: Thu, 21 Jul 2005 06:59:18 -0400 Source: gaim Binary: gaim gaim-dev gaim-data Architecture: source i386 all Version: 1:1.4.0-3 Distribution: unstable Urgency: low Maintainer: Robert McQueen [EMAIL PROTECTED] Changed-By: Ari Pollak [EMAIL PROTECTED] Description: gaim - multi-protocol instant messaging client gaim-data - multi-protocol instant messaging client - data files gaim-dev - multi-protocol instant messaging client - development files Changes: gaim (1:1.4.0-3) unstable; urgency=low . * Build-depend on libxss-dev so X idle time support will actually get built * Remove build-depends on autotools-dev since it is no longer necessary * Change Suggests: evolution-data-server1.2 to evolution-data-server Files: 4d6f7134d6d38498fd1ad776d6d5 950 net optional gaim_1.4.0-3.dsc ec03bb906b664a5bc40dc08f3625976b 28959 net optional gaim_1.4.0-3.diff.gz 1ca1bc0605ed9b7cbea6bd924a19469b 3168896 net optional gaim-data_1.4.0-3_all.deb 152d3be0730b3b40bdafa3779829ff3b 844394 net optional gaim_1.4.0-3_i386.deb 6ca2745be474511239d93f8441ea1aae 103044 devel optional gaim-dev_1.4.0-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC3+YowO+u47cOQDsRA+BDAKCg2bud517zIVsZgqF1betEBnXXeACggu/z sprR6i/R+0mYfTh5ZgbPDRo= =KVmX -END PGP SIGNATURE- Accepted: gaim-data_1.4.0-3_all.deb to pool/main/g/gaim/gaim-data_1.4.0-3_all.deb gaim-dev_1.4.0-3_i386.deb to pool/main/g/gaim/gaim-dev_1.4.0-3_i386.deb gaim_1.4.0-3.diff.gz to pool/main/g/gaim/gaim_1.4.0-3.diff.gz gaim_1.4.0-3.dsc to pool/main/g/gaim/gaim_1.4.0-3.dsc gaim_1.4.0-3_i386.deb to pool/main/g/gaim/gaim_1.4.0-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted dctrl-tools 2.8 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Jul 2005 21:32:42 +0300 Source: dctrl-tools Binary: dctrl-tools grep-dctrl Architecture: source i386 all Version: 2.8 Distribution: experimental Urgency: low Maintainer: Antti-Juhani Kaijanaho [EMAIL PROTECTED] Changed-By: Antti-Juhani Kaijanaho [EMAIL PROTECTED] Description: dctrl-tools - Command-line tools to process Debian package information grep-dctrl - Grep Debian package information - transition package Closes: 191144 Changes: dctrl-tools (2.8) experimental; urgency=low . * Merge 2.6.7 (no po/ merge). * New program tbl-dctrl. Closes: #191144 (Would be great if it could print desired field values all in one line, per package) [Reported by Carlos Sousa] * tbl-dctrl.1: New manpage. * Give FSAF objects knowledge of the file name, so that we know which file each paragraph came from. * para_bundle.c (bundle_slurp): The correct error sentinel for file descriptors is -1, not 0. Files: 67c923d3c64871afe0c7389710d3e197 529 utils optional dctrl-tools_2.8.dsc 11b90f23f63b246c1291aad63d3b0c82 77740 utils optional dctrl-tools_2.8.tar.gz c8af3de5cad1ac43b766d5503c9d2238 1318 utils optional grep-dctrl_2.8_all.deb b06f3b4906185f4f5623b300ebbfdfc2 72352 utils optional dctrl-tools_2.8_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC3+1QHsI32VNFhOgRAv/aAJ94eS/ulA24D8rphJYJdd1vIH8eFACfYncr ivro5eJqlCx48IeiPxVMdkI= =o8pz -END PGP SIGNATURE- Accepted: dctrl-tools_2.8.dsc to pool/main/d/dctrl-tools/dctrl-tools_2.8.dsc dctrl-tools_2.8.tar.gz to pool/main/d/dctrl-tools/dctrl-tools_2.8.tar.gz dctrl-tools_2.8_i386.deb to pool/main/d/dctrl-tools/dctrl-tools_2.8_i386.deb grep-dctrl_2.8_all.deb to pool/main/d/dctrl-tools/grep-dctrl_2.8_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libgdchart-gd1 0.10.1dev-10.1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Jul 2005 20:33:52 +0200 Source: libgdchart-gd1 Binary: libgdchart-gd1-xpm libgdchart-gd1-noxpm-dev libgdchart-gd1-noxpm libgdchart-gd1-xpm-dev Architecture: source i386 Version: 0.10.1dev-10.1 Distribution: unstable Urgency: low Maintainer: Jonas Smedegaard [EMAIL PROTECTED] Changed-By: Matthias Klose [EMAIL PROTECTED] Description: libgdchart-gd1-noxpm - Generate graphs using the GD library libgdchart-gd1-noxpm-dev - Generate graphs using the GD library (development version) libgdchart-gd1-xpm - Generate graphs using the GD library libgdchart-gd1-xpm-dev - Generate graphs using the GD library (development version) Closes: 260416 Changes: libgdchart-gd1 (0.10.1dev-10.1) unstable; urgency=low . * NMU * Fix FTBFS with gcc-3.4 / gcc-4.0 (closes: #260416). Files: 80beed8ef853afced3376b021ae422b7 731 oldlibs optional libgdchart-gd1_0.10.1dev-10.1.dsc 6bd1473cf6c4b577f1cbdc8912832f9d 4785 oldlibs optional libgdchart-gd1_0.10.1dev-10.1.diff.gz abddc2246f66f37b4a94409329a585ce 53044 oldlibs optional libgdchart-gd1-noxpm-dev_0.10.1dev-10.1_i386.deb a6ddf8c213cc8740a7b63de8e149f3a6 52452 oldlibs optional libgdchart-gd1-xpm-dev_0.10.1dev-10.1_i386.deb 2e853f6a18cd4d6a38ccb0e64255b5d3 41870 oldlibs optional libgdchart-gd1-noxpm_0.10.1dev-10.1_i386.deb 9626310c9ed4f3e6b5cd7578df86e1a3 41916 oldlibs optional libgdchart-gd1-xpm_0.10.1dev-10.1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC3+w4StlRaw+TLJwRAoFYAJ0ZVVN4ke1BU0BJgox3qF8YwhRgvACgiC43 lUW/uymCyteoxI8mvEK18FE= =Edt1 -END PGP SIGNATURE- Accepted: libgdchart-gd1-noxpm-dev_0.10.1dev-10.1_i386.deb to pool/main/libg/libgdchart-gd1/libgdchart-gd1-noxpm-dev_0.10.1dev-10.1_i386.deb libgdchart-gd1-noxpm_0.10.1dev-10.1_i386.deb to pool/main/libg/libgdchart-gd1/libgdchart-gd1-noxpm_0.10.1dev-10.1_i386.deb libgdchart-gd1-xpm-dev_0.10.1dev-10.1_i386.deb to pool/main/libg/libgdchart-gd1/libgdchart-gd1-xpm-dev_0.10.1dev-10.1_i386.deb libgdchart-gd1-xpm_0.10.1dev-10.1_i386.deb to pool/main/libg/libgdchart-gd1/libgdchart-gd1-xpm_0.10.1dev-10.1_i386.deb libgdchart-gd1_0.10.1dev-10.1.diff.gz to pool/main/libg/libgdchart-gd1/libgdchart-gd1_0.10.1dev-10.1.diff.gz libgdchart-gd1_0.10.1dev-10.1.dsc to pool/main/libg/libgdchart-gd1/libgdchart-gd1_0.10.1dev-10.1.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libsdl-sound1.2 1.0.1-6 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Format: 1.7 Date: Thu, 21 Jul 2005 18:26:20 + Source: libsdl-sound1.2 Binary: libsdl-sound1.2 libsdl-sound1.2-dev Architecture: source i386 Version: 1.0.1-6 Distribution: unstable Urgency: low Maintainer: Ari Pollak [EMAIL PROTECTED] Changed-By: Ari Pollak [EMAIL PROTECTED] Description: libsdl-sound1.2 - Decoder of several sound file formats for SDL libsdl-sound1.2-dev - Development files for SDL_sound Changes: libsdl-sound1.2 (1.0.1-6) unstable; urgency=low . * Bump build-depends on libsmpeg-dev for C++ ABI transition Files: ff04d4ef2e4d0eefc3d6a431aec4dd94 800 sound optional libsdl-sound1.2_1.0.1-6.dsc 389f4d8875d2c176a3a1cc01d11f1325 397077 sound optional libsdl-sound1.2_1.0.1-6.diff.gz 1fd5fcaf08db8e0e323afb0097e7302a 109670 libdevel optional libsdl-sound1.2-dev_1.0.1-6_i386.deb 394c8096a81426041bb623dfd16dfa68 92044 libs optional libsdl-sound1.2_1.0.1-6_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC3+vKwO+u47cOQDsRA843AJ9/5avTvnLmIgfqbYYdmkcTvNmEPACcCoIK J7vBlgAOKBpbr4OQEGppDkc= =+57V -END PGP SIGNATURE- Accepted: libsdl-sound1.2-dev_1.0.1-6_i386.deb to pool/main/libs/libsdl-sound1.2/libsdl-sound1.2-dev_1.0.1-6_i386.deb libsdl-sound1.2_1.0.1-6.diff.gz to pool/main/libs/libsdl-sound1.2/libsdl-sound1.2_1.0.1-6.diff.gz libsdl-sound1.2_1.0.1-6.dsc to pool/main/libs/libsdl-sound1.2/libsdl-sound1.2_1.0.1-6.dsc libsdl-sound1.2_1.0.1-6_i386.deb to pool/main/libs/libsdl-sound1.2/libsdl-sound1.2_1.0.1-6_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted sms-pl 1.9.2m-3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Jul 2005 20:59:18 +0200 Source: sms-pl Binary: sms-pl Architecture: source i386 Version: 1.9.2m-3 Distribution: unstable Urgency: low Maintainer: Marcin Owsiany [EMAIL PROTECTED] Changed-By: Marcin Owsiany [EMAIL PROTECTED] Description: sms-pl - Send SMs via Polish GSM operators Changes: sms-pl (1.9.2m-3) unstable; urgency=low . * Rebuilt with GCC 4 * Standards-version bump to 3.6.2 (no changes needed) Files: 1d2654bd241076e9f02337e54e55ac92 571 net optional sms-pl_1.9.2m-3.dsc 5594335396c4a394d0b680d8dd71c3e4 6049 net optional sms-pl_1.9.2m-3.diff.gz e2989c6f083d07133b4230a9b0505498 58358 net optional sms-pl_1.9.2m-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC3/dOOg2KoGD0EhYRAr/GAJ4zmkjasH8RTAagNcvJlckCpR8V0wCdENIA 4KY8QSzdidlqTZ8Pfda71jo= =6r6q -END PGP SIGNATURE- Accepted: sms-pl_1.9.2m-3.diff.gz to pool/main/s/sms-pl/sms-pl_1.9.2m-3.diff.gz sms-pl_1.9.2m-3.dsc to pool/main/s/sms-pl/sms-pl_1.9.2m-3.dsc sms-pl_1.9.2m-3_i386.deb to pool/main/s/sms-pl/sms-pl_1.9.2m-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
