Re: Re: (Was) [aspell-it] deb per la 0.60
Se trovate parole che mancano o parole errate potete spedirmi l'elenco direttamente a me. spero di ricordarlo; in ogni caso tieni sott'occhio la wordlist che e' archiviata in un repositorio SVN pubblicamente consultabile. Per quanto riguarda quelle riportare sulla pagina: * Tailandia - Nel dizionario è stato messo Thailandia perché è risultato il termine più corretto su alcune fonti che abbiamo consultato ... se avete altre fonti che riportano il contrario fatemele conoscere. confesso che la mia fonte consultata si chiama Google! Indeciso su quale versione utilizzare ho scelto la versione che mi sembrava più italiana. Ho appena tolto Tailandia dalla wordlist e corretto il it.po. * installabile - già presente nella mia versione interna ok, lo rimuovero' dalla wl non appena passero' alla nuova versione di aspell-it Ho segnato le altre parole e prossimamente vedrò quali inserire. ottimo Ciao Davide ciao, Davide -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [aspell-it] deb per la 0.60
Segmentation fault
Ho fatto un pochino di indagine
Se crei un file test2.txt contenente soltanto la parola malfunzionante
e lanci gdb
-- gdb aspell
GNU gdb 2002-04-01-cvs
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for details.
This GDB was configured as i386-linux...
(gdb) r --lang=it -c test
test2.txt test2.txt.new test_it.txt
(gdb) r --lang=it -c test2.txt
Starting program: /home/zino/tools_0.60.2/bin/aspell --lang=it -c test2.txt
Program received signal SIGSEGV, Segmentation fault.
0x1298 in ?? ()
(gdb) bt
#0 0x1298 in ?? ()
#1 0x400aad21 in aspeller::AffixMgr::affix_check (this=0x80a0560, [EMAIL
PROTECTED], word=
{str_ = 0x80c7218 malfunzionante, size_ = 4294967295}, [EMAIL
PROTECTED], gi=0x0)
at modules/speller/default/affix.cpp:843
#2 0x4008ee3e in aspeller::SpellerImpl::check_affix (this=0x8075510, word=
{str_ = 0x80c7218 malfunzionante, size_ = 4294967295}, [EMAIL
PROTECTED], gi=0x80756d0)
at modules/speller/default/speller_impl.cpp:147
#3 0x4008ef92 in aspeller::SpellerImpl::check (this=0x8075510, word=0x80c7218
malfunzionante,
word_end=0x80c7226 , try_uppercase=false, run_together_limit=0,
ci=0x80755b0, gi=0x80756d0)
at modules/speller/default/speller_impl.cpp:160
#4 0x400940f9 in aspeller::SpellerImpl::check (this=0x8075510, word=
{str = 0x80c7218 malfunzionante, size = 14}) at
modules/speller/default/speller_impl.hpp:104
#5 0x40066d7b in acommon::DocumentChecker::next_misspelling (this=0x80c71d8)
at common/document_checker.cpp:67
#6 0x0806fa96 in CheckerString::next_misspelling (this=0x80c70f8) at
prog/checker_string.cpp:113
#7 0x080552f3 in check () at prog/aspell.cpp:1039
#8 0x0804eae7 in main (argc=4, argv=0xb904) at prog/aspell.cpp:406
--
il problema è la lunghezza della parola malfunzionante (14 caratteri);
si scopre facilmente che 11 è il max numero di caratteri... se domani ho
tempo provo a capirci qualcosa di piu'
ciao,
d.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Clavier français et RC3 de l'installateur (noyau 2.6)
Le jeudi 07 avril 2005 à 19:35 +0200, Christian Perrier a écrit : Correction : ce vilain bogue affecte toutes les installations nouvelles en noyau 2.6 et clavier français mais seulement celles réalisées le 5/4/2005...:-) J'ai eu beau passer ma journée à tenter de reproduire ce bogue dans tous les sens, rien n'y a fait. À ce que me dit Julien sur IRC, ça continue de se produire, et ce sur moult configurations. Si le bug est identifié et le correctif connu, pourquoi ne pas le corriger, même si ce n'est pas toujours reproductible ? -- .''`. Josselin Mouette/\./\ : :' : [EMAIL PROTECTED] `. `'[EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom
Re: Clavier français et RC3 de l'installateur (noyau 2.6)
Quoting Josselin Mouette ([EMAIL PROTECTED]):
À ce que me dit Julien sur IRC, ça continue de se produire, et ce sur
moult configurations. Si le bug est identifié et le correctif connu,
pourquoi ne pas le corriger, même si ce n'est pas toujours
reproductible ?
Un contournement est connu, pas un correctifet, en fait, personne
n'a de certitude qu'il ne casse rien ensuite.
Et le channel de développement de l'installateur est #debian-boot, la
liste étant [EMAIL PROTECTED] Si c'est reproductible,
pourquoi n'en savons-nous rien ? Moi, je ne suis plus arrivé à le
reproduire et si je me mords les doigts c'est bien de n'avoir pas
gardé la trace de l'install où je l'ai rencontré (François Mescam, le
propriétaire de la machine en avait besoin...et n'a même pas réussi
ultérieurement à reproduire le problème à nouveau lui-même).
Si les développeurs et utilisateurs affectés comptent uniquement sur
le fait que, par divination, on puisse à la fois savoir que le
problème se produit encore (alors que je ne le reproduis plus sur des
installations réelles ou dans QEmu)et également faire le
nécessaire pour convaincre les développeurs de l'installateur que les
semaines nécessaires pour reconstruire un installateur sont
justifiées, ils se fourrent le doigt dans l'oeil, ça ne se produira
pas.
Le contournement suggéré implique de corriger prebaseconfig dans
languagechooser, de recompiler celui-ci, de le faire passer dans
testing, de reconstruire TOUS les initrd de tous les supports
possibles, de tester les fichiers construits (floppy, netboot, ISO
divers)donc plusieurs semaines de travail que pour l'instant
l'équipe de l'installateur ne voit pas de raison de mettre en branle
pour un bogue qu'on a même du mal à reproduire de manière fiable.
Les installations en français risquent d'en souffrir, oui, et j'en
serai le premier désolé. Nous aurons sûrement à nous mordre les doigts
qu'il n'y ait pas eu plus de développeurs et d'utilisateurs
fran{çais|cophones} impliqués régulièrement dans l'installateur que
les trois que j'ai vu régulièrement ces 2 dernières années (en
ajoutant les traducteurs, notamment Philippe Batailler qui s'est fait
la quasi-totalité du manuel d'installation).
Il est encore temps, au moins d'essayer de cerner ce damné bogue pour
trouver un contournement simple qu'on pourrait documenter dans les
Release Notes. Un élément précieux pour cela est le fichier
/etc/console/boottime.kmap.gz AVANT de faire la correction nécessaire
(cf mon mail d'origine).
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Clavier français et RC3 de l'installateur (noyau 2.6)
Christian Perrier [EMAIL PROTECTED] wrote: Et le channel de développement de l'installateur est #debian-boot, la liste étant [EMAIL PROTECTED] Si c'est reproductible, pourquoi n'en savons-nous rien ? Moi, je ne suis plus arrivé à le reproduire et si je me mords les doigts c'est bien de n'avoir pas gardé la trace de l'install où je l'ai rencontré (François Mescam, le propriétaire de la machine en avait besoin...et n'a même pas réussi ultérieurement à reproduire le problème à nouveau lui-même). Je pense que le bug n'est pas spécifique à cette histoire de clavier, et que c'est un problème plus général avec le 2.6 et le ramfs, étant donné ce que j'ai pu constater sur mon PE 750 ; malheureusement je n'ai pas eu le temps de me pencher sur le problème. En ce qui me concerne, ce problème de fichiers manquants était 100% reproductible, j'ai fait un install report qui a été réassigné par Joey au kernel, et je n'ai pas eu de nouvelles. Entre temps, j'ai vu passer d'autres histoires similaires. Maintenant, je n'ai pas accès à la machine pour les 2 semaines à venir, alors si je trouve du temps en rentrant, j'essayerai de voir ce qu'il se passe. Je terminerai en disant que s'il faut des semaines pour reconstruire les images de debian-installer avec un package bugfixé, il y a un très sérieux problème. On se plaignait des boot-floppies ... Enfin bon, bref. Pendant ce temps-là, ma todo-list ne descend pas. JB. -- Julien BLACHE - Debian GNU/Linux Developer - [EMAIL PROTECTED] Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Clavier français et RC3 de l'installateur (noyau 2.6)
Je terminerai en disant que s'il faut des semaines pour reconstruire les images de debian-installer avec un package bugfixé, il y a un très sérieux problème. On se plaignait des boot-floppies ... Où est le problème ? On parle d'une release, là. Pas d'une version construite quotidiennement. En deux ans, il a été fait quatre versions beta de l'installateur et trois release candidates. (Joey a déjà écrit que nous avons en fait releasé Debian trois, voire sept fois sans que personne ne s'en rende compte...:-))) Il ne faut pas des semaines pour construire les images, il faut des semaines pour construire un correctif quand il touche à l'initrd et le faire passer dans une release officielle T.E.S.T.E.E. Pour avoir une idée des tests actuellement effectués à chaque release, cf: http://svn.debian.org/wsvn/d-i/branches/d-i/sarge/installer/doc/devel/release-checklist?op=filerev=0sc=0 Certains sont automatisés, d'autres pas. Cela, ça prend beaucoup de temps et, ce problème en est la preuve, cela ne remplace pas les tests réguliers sur les images quotidiennes. Eux, très franchement, il n'y en a pas assez de faits, c'est très clair...et c'est très clairement parce qu'il n'y a pas assez de monde pour les faire. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: All GPL'ed programs have to go to non-free
On Thu, 14 Apr 2005, Adrian Bunk wrote: Therefore, all GPL'd programs will have to go to non-free. Q.E.D. Is this a correct interpretation of what will happen after the release of sarge or is there any mistake in my proof? The problem you have identified is not new, or unique to free software development. There is a type of apparently unanswerable question of the form: Does the barber shave every man in town who doesn't shave himself?, or more generally, Does the set of all sets which do not contain themselves, contain itself?. This is sometimes known as Russell's Paradox (Gödel's Incompleteness Theorem is its most general expression); in this case it is Is the requirement of freedom a restriction?. Wittgenstein claimed to have solved the paradox in Tractatus Logico Philosophicus; I read the proof but didn't get it - maybe you will be able to - but I think he took it back later. In short, we must accept that any system can only be justified from outside itself. In order to move our arms, they must be attached at the shoulder; in order to walk, we must stand on one leg, lean forward, and trust that we won't fall over. Meanwhile, keep on philosophizing and, especially, keep that beautiful Debian system growing. John O'Hagan
Re: Re: All GPL'ed programs have to go to non-free
May be, are we talking about this? http://en.wikipedia.org/wiki/Russell's_paradox Daniele -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.9.18 - Release Date: 19/04/2005 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Minimizing ld dependencies with --as-needed
Hi Tollef, Sorry for the high response latency. * Tollef Fog Heen wrote on Wed, Apr 13, 2005 at 09:45:03PM CEST: * Ralf Wildenhues | I would be much happier if someone with time would just help to put | this into libtool properly as an option (and possible adjust pkg-config, | FWIW). I'm pretty sure it would minimize the combined amount of work, | with increased benefit. pkg-config has the necessary patches now, but the support is disabled by default in Debian. It'll be enabled post-sarge. I think that is not enough. Unless libtool supports this properly, you will end up having weird, seemingly unrelated bug reports with things that broke by this change. It won't work at all unless Debian Libtool keeps its link_all_deplibs=no patch, which is unfortunate. I would like to see less variations in Distributions' libtool packages. Even with the patch I think you are not safe. At the very least, user compiling their own software might encounter needless trouble. We started some discussions on this issue[1], but no final conclusion nor patch has been proposed. It would be much nicer to solve the problem cleanly in libtool. To put it another way: Please don't blame libtool for failures caused by using --as-needed behind its back. Regards, Ralf [1] http://lists.gnu.org/archive/html/libtool/2004-11/msg00455.html http://lists.gnu.org/archive/html/libtool/2004-12/msg00029.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: All GPL'ed programs have to go to non-free
On Wed, Apr 20, 2005 at 01:22:06AM -0400, Glenn Maynard wrote: On Wed, Apr 20, 2005 at 06:24:51AM +0200, Adrian Bunk wrote: The nice thing about 3:1 majorities is, that once you've tricked something as Editorial amendments into it, a 25% minority is enough to block reverting it... Nobody was tricked. I believe this claim so laughable, and at the same time so insulting to Debian Developers (we forgot to read what we voted for! I want a do-over!), that I don't feel inclined to argue it further. Again, the SC is crystal clear; again, only a GR will change that. My belief, from experience of many discussions on these topics on these lists, is that a huge majority of Debian Developers agree that documentation must follow the DFSG, that a fringe minority who want GNU documentation in Debian at any and all cost are making ludicrous claims, and that nobody is falling for them. I'm willing to continue arguments pertaining to the GFDL, but these we didn't *really* want to require documentation to be free arguments are going nowhere and are a waste of time, so I'm dropping them. Only one month after GR2004-003, a two third majority of the Debian developers preferred in GR2004-004 reverting GR2004-003 over keeping the changes of GR2004-003. You do believe that two thirds are a fringe minority and less than one third is a huge majority? After the whole GR2004-003 mess it's hard to say what the majority of Debian developers really wants. Glenn Maynard cu Adrian -- Is there not promise of rain? Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. Only a promise, Lao Er said. Pearl S. Buck - Dragon Seed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: All GPL'ed programs have to go to non-free
On Wednesday 20 April 2005 12:24 am, Adrian Bunk wrote: In GR2004-004, Proposal D to revert GR2004-003 did get a 2.3:1 majority by the developers over the proposal to keep the changes of GR2004-003. That's a pretty clear statement. Adrian, I believe that you are misrepresenting the outcome of -004. The proposal to postpone the changes till after the release, then reinstate them, defeated option D (rescind -003) by a 2:1 majority. The only options I can see that D defeated by a 2.3:1 majority are option F (do nothing at all) and Further Discussion, which all the voters had been told would result in a further delay of the Sarge release. Daniel -- /--- Daniel Burrows [EMAIL PROTECTED] --\ | The problem with LaTeX is that your answers | | look so good, you think they *must* be right! | |-- Thomas Banchoff | \--- Be like the kid in the movie! Play chess! -- http://www.uschess.org --/ pgp5DwLX4Rmvq.pgp Description: PGP signature
Re: All GPL'ed programs have to go to non-free
On Wed, Apr 20, 2005 at 09:39:23AM -0400, Daniel Burrows wrote: Adrian, I believe that you are misrepresenting the outcome of -004. The proposal to postpone the changes till after the release, then reinstate them, defeated option D (rescind -003) by a 2:1 majority. The only options I can see that D defeated by a 2.3:1 majority are option F (do nothing at all) and Further Discussion, which all the voters had been told would result in a further delay of the Sarge release. A 2.3:1 majority preferred option D to revert -003 over option F to reaffirm -003. Rereading the results, I get your point about option B compared to D, making the whole issue even more mysterious. Could anyone give a definitive answer to the following questions: - Did -003 contain real changes [1] or didn't it change anything? - How is it possible to happen that only a small amount of the Debian developers (less than one out of four) participates in a GR vote, the consequences of this GR do not become widely known until after the GR, and one month later, corrections to this GR are widely accepted? - If -003 changed anything, were there Debian developers who mistakenly agreed to -003 because of it's obfuscated Editorial amendments title? If the intention of GRs was to express the opinion of the Debian developers, the whole -003 and -004 mess seems to be a way how to not do it. Daniel cu Adrian [1] as stated in the accepted option B of -004 -- Is there not promise of rain? Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. Only a promise, Lao Er said. Pearl S. Buck - Dragon Seed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: All GPL'ed programs have to go to non-free
On Wed, 20 Apr 2005 06:24:51 +0200, Adrian Bunk [EMAIL PROTECTED] said: On Tue, Apr 19, 2005 at 11:52:19PM -0400, Glenn Maynard wrote: ... (GR2004-004 didn't make any sense at all, nor does it make any sense that Sarge can ship with non-free documentation, and at the time I found the posts of the RM on the topic to make no sense at all, but I was satisfied with the results of GR2004-003 and am able to bear the strangeness of GR2004-004 for now, since it'll expire on its own.) (And if people really are voting for a GR after only reading the title, I'd be even more disappointed, but I just don't believe that.) It's funny that out of the five people seconding GR2004-003, the first three did either second or even propose one of the first two suggestions in GR2004-004. Right, the release sarge while we fix up the non-free stuff in the distribution. That is the pragmatic solution, Sarge was way overdue, and since we had been shipping non-free bits in Debian for a bit anyway, there is something to be said about releasing a something with stuff in it that we consider non-free, and then get our act together later. If even the Debian developers seconding a GR are supporting changes to the result of this GR only one month later... I guess English is not your first language, eh? That is the more charitable explanation for such a major lack of judgement in trying to judge motivations of these folks. They wanted to release Sarge, flawed though it is, not rescind the changes made. In any event, all of this is irrelevant: if people really think that non-free documentation should be allowed in Debian, propose a GR to allow it. Nothing short of that will make it so. If people really think they were tricked, fine--fix it with another GR. Unless and until that happens, Debian's position is very clear. In GR2004-004, Proposal D to revert GR2004-003 did get a 2.3:1 majority by the developers over the proposal to keep the changes of GR2004-003. That's a pretty clear statement. And was beaten by most other proposals. I guess it got some support from the -release-sarge-at-any-cost crowd, I think. Hell, people would have preferred to apolgize for Sarge not following the social contract rather than rescind the changes. == Put the recent changes made in the social contract in abeyance for a fixed time period Beats Rescinds the previous GR, reverting to the version 1.0 of the social contract. By 200 - 160 = 40 Puts the recent changes made in the social contract in abeyance for the next release of Debian. Beats Rescinds the previous GR, reverting to the version 1.0 of the social contract. By 257 - 122 = 135 Puts in an apology for the current release, code named sarge, for not following the social contract Beats Rescinds the previous GR, reverting to the version 1.0 of the social contract. By 180 -174 = 6 Rescinds the previous GR, reverting to the version 1.0 of the social contract. Beats Creates a foundation document to provide guidelines for handling changes in foundation documents. By 181 - 179 = 2 Rescinds the previous GR, reverting to the version 1.0 of the social contract. Beats Reaffirm the current social contract, and not compromise on future releases By 181 - 179 = 123 Rescinds the previous GR, reverting to the version 1.0 of the social contract. Beats Further Discussion By 255 - 110 = 145 == Indeed, option D only beat out Option E by 2 votes. So, since you have problems interpreting the results, here is a cluebat: inline: vote_004_results.png The nice thing about 3:1 majorities is, that once you've tricked something as Editorial amendments into it, a 25% minority is enough to block reverting it... How much credence should I lend to the views of people who vote for a change to a foundation document based on just the title, and do not read the actual change that was sent to their mail boxes at least thrice? Oh, I can't be bothered to read (or I can't read), and I screwed up, so give me another chance? Why should that not read I am too apathetic to read ballots sent to me but I voted anyway, so please remove my key from the Debian key ring? manoj -- broad-mindedness, n: The result of flattening high-mindedness out. Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/%7Esrivasta/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Re: All GPL'ed programs have to go to non-free
Le mercredi 20 avril 2005 à 05:06 +0200, Adrian Bunk a écrit : I've heard three different stories describing this GR: 1. it contained only Editorial amendments and didn't change anything 2. the Debian developers decided in this GR that documentation has to fulfill the full DFSG guidelines 3. many Debian mistakenly agreed with it because they mistakenly beliefed after reading the title that it only contained editorial and no actual changes Didn't you hear about 1.5? Many developers believed 1, a few developers believed 2. Sadly, among the few developers happened to be the release manager. -- .''`. Josselin Mouette/\./\ : :' : [EMAIL PROTECTED] `. `'[EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom
Re: {Arch,OCaml,Python,Mono} Packages for Adoption
On Tue, 19 Apr 2005, John Goerzen wrote: Hello, I'm going through the list of packages I'm maintainer for, and found several that I no longer use. Some I've tried to give away long ago, but for whatever reason, never were picked up. I've submitted orphaned versions of all of these and filed appropriate wnpp bugs. [Mono] nant ikvm I'll take these thanks. Maybe the Mono packaging group will want them but that's for later. Cheers Dave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: What do you win by moving things to non-free?
Glenn Maynard [EMAIL PROTECTED] wrote: And Debian has tried to work on reducing the impact, by trying to convince the FSF to fix their license. Not only have they not done so, they've completely stonewalled, refusing to discuss the issue at all. Debian has done more than its part in trying to fix this. It didn't work. It's time to remove the non-free stuff (or will be soon). The fact that the discussion has not been public does not mean that the FSF have refused to discuss the issue. -- Matthew Garrett | [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: All GPL'ed programs have to go to non-free
Le mercredi 20 avril 2005 à 16:10 +0200, Adrian Bunk a écrit : Could anyone give a definitive answer to the following questions: - Did -003 contain real changes [1] or didn't it change anything? It didn't change anything. - How is it possible to happen that only a small amount of the Debian developers (less than one out of four) participates in a GR vote, the consequences of this GR do not become widely known until after the GR, and one month later, corrections to this GR are widely accepted? Because *after* the vote, the release manager explained his beliefs about this GR actually changing something, and his will to change the release strategy because of that. -- .''`. Josselin Mouette/\./\ : :' : [EMAIL PROTECTED] `. `'[EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom
Re: All GPL'ed programs have to go to non-free
Wow, a civil discussion. I'll see if I can keep it up. On Wednesday 20 April 2005 10:10 am, Adrian Bunk wrote: Could anyone give a definitive answer to the following questions: - Did -003 contain real changes [1] or didn't it change anything? That basically depends on who you ask and on the more philosophical question of what a real change is. I think I'll skip this. - How is it possible to happen that only a small amount of the Debian developers (less than one out of four) participates in a GR vote, the consequences of this GR do not become widely known until after the GR, and one month later, corrections to this GR are widely accepted? Anecdotally, it seems that at least some of the people who voted for -003 felt we were already in violation of the SC, and hence there was no need to rush to change things (since it hadn't been a priority before the GR). Others thought that a substantive change was taking place, but weren't expecting the Release Manager to immediately incorporate the changes as a release goal -- they had simply assumed that a timetable would be laid out that took sarge into consideration. I believe you can find people expressing sentiments along these lines in last spring's list archives. I think there also were a few people who claimed to have been mislead about what the SC changes did, although I've seen many, many more individuals claiming that other (unspecified) people were mislead. - If -003 changed anything, were there Debian developers who mistakenly agreed to -003 because of it's obfuscated Editorial amendments title? If the intention of GRs was to express the opinion of the Debian developers, the whole -003 and -004 mess seems to be a way how to not do it. I don't think that anyone would do things exactly the same way with the benefit of hindsight. Daniel -- /--- Daniel Burrows [EMAIL PROTECTED] --\ | You are standing west of a white house. There is a mailbox here. | \- A duck! -- http://www.python.org / pgp79L0JLvVKw.pgp Description: PGP signature
Re: What do you win by moving things to non-free?
On 20-Apr-05, 09:34 (CDT), Matthew Garrett [EMAIL PROTECTED] wrote: Glenn Maynard [EMAIL PROTECTED] wrote: And Debian has tried to work on reducing the impact, by trying to convince the FSF to fix their license. Not only have they not done so, they've completely stonewalled, refusing to discuss the issue at all. Debian has done more than its part in trying to fix this. It didn't work. It's time to remove the non-free stuff (or will be soon). The fact that the discussion has not been public does not mean that the FSF have refused to discuss the issue. Oh, come on. It's been what, 15 months since the FSF requested comments on the draft GFDL? (Or was that 2003?) They then released it unchanged, and made no visible response to the many questions/concerns raised in those comments. Since then we've heard several Debian developers say We're talking to the FSF, but don't want to make public comments until the FSF says it's okay. (And that made sense, as it would to anyone whose been reading debian-devel (or -legal) for more than a week.) But we heard this last summer, and nothing ever came of it. And now you say it's *still* going on? I've got no doubts about the honesty and good intent of the Debian developers involved. I believe that they really think that the FSF will eventually make some sort of response. But you folks need to realize when you're being strung along, and get on with your lives. RMS has decided that it's more important to force people to distribute his essays than allow them share and reuse documentation. I think he's blown this decision, but it's fairly obvious at this point that he's not going to change his mind. All we can do is discourage use of the GFDL, and hope that the GPL3 isn't equally screwed up. Steve -- Steve Greenland The irony is that Bill Gates claims to be making a stable operating system and Linus Torvalds claims to be trying to take over the world. -- seen on the net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: All GPL'ed programs have to go to non-free
Adrian Bunk [EMAIL PROTECTED] writes: On Wed, Apr 20, 2005 at 09:39:23AM -0400, Daniel Burrows wrote: D defeated by a 2.3:1 majority are option F (do nothing at all) and Further Discussion, which all the voters had been told would result in a further delay of the Sarge release. A 2.3:1 majority preferred option D to revert -003 over option F to reaffirm -003. Rereading the results, I get your point about option B compared to D, making the whole issue even more mysterious. I don't think it's very mysterious. I think it's a pretty clear statement about priorities. The majority of the Debian developers participating in the vote do believe that documentation and other files need to be as free as software, but also believe that getting sarge out the door is much more important than doing anything about that immediately. That seems like a sensible and self-consistent position, and it doesn't seem surprising that a lot of people hold it. I tend to come down on the side of feeling that the two GRs really did clarify Debian's position on whether documentation is held to the same standards. Based on (lots and lots of) subsequent conversation, the part that still seems somewhat unclear is whether a similar binding majority would have agreed to take GFDL documentation out of main, something that wasn't actually asked directly in either GR. There seems to be some disagreement as to whether GFDL-covered works without invariant sections are really non-free. (I'm aware of all the arguments; I'm just saying that based on public postings, they don't seem to have convinced everyone. I think there's a much stronger consensus around the idea that works with invariant sections are non-free.) There also seems to be discomfort around the implications of the GFDL being non-free even among people who believe that it is. I think there's a fair bit of additional er, this doesn't feel right sentiment in addition to the people who really would argue that the GFDL without variant sections is a free license. This is an understandable feeling that I'd expect to see *even if removing the docs is the right decision*, since after all this action is probably the sharpest break with the FSF that Debian has made and removes a fair bit of useful documentation from main. I think a *lot* of people are feeling something like ugh, I don't have a really good argument against doing that, based on core principles, but man, it sucks a lot, and I'm really uncomfortable with it. - If -003 changed anything, were there Debian developers who mistakenly agreed to -003 because of it's obfuscated Editorial amendments title? I don't think this is really a productive line of worry, in that all voting results are suspect if we can't assume that the voters read the GR and at least some of the extensive e-mail threads about its implications. I think anyone who was following the Debian discussion mailing lists at all knew what the GR was about, given the amount of discussion there was about it at the time. -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ITP: spca5xx -- Device driver for USB webcams based on the spca5xx chips
Carlos C Soto wrote: Great! I use this module and wold be great to have it on debian. I was thinking on put a RFP bug for it. -- Carlos C Soto :: eclipxe I agree. I just built it again today against 2.6.11-1-686-smp (after using it for several months against 2.6.10-1-686-smp). I talked to the developer about getting it in the kernel, but he doesn't seem to care. If you want I would be willing to help get some people together to submit it into the main kernel sources. For now, I think it would be best to get it put together as a patch for the debian-kernel team so it will automagically get built for each new 2.6.x kernel. Otherwise, we would have to package it up for each kernel as a seperate patch. Have you already made it into such a patch for the debian kernel sources? If not, I'd be happy to help with that also. The driver works great on the built in z-micro USB camera on my portable. jcarr -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#304401: ITP: libstatgrab -- library providing interface to system statistics
On Thu, Apr 14, 2005 at 12:43:44PM +0200, Bartosz Fenski aka fEnIo wrote: It would be great, if you package pystatgrab (http://www.i-scream.org/pystatgrab/) as well. I'm packaging libstatgrab only because pystatgrab needs it ;) If someone is interested in new packages they're available at my homepage[1]. I think they're in overall good shape, but there are not manpages for utilities, thus I didn't uploaded it yet. Otherwise I think packages are in good shape to be included in Debian. I'll try to write manpages during weekend or so. regards fEnIo [1] - http://skawina.eu.org/libstatgrab/ -- ,''`. Bartosz Fenski | mailto:[EMAIL PROTECTED] | pgp:0x13fefc40 | irc:fEnIo : :' : 32-050 Skawina - Glowackiego 3/15 - w. malopolskie - Poland `. `' phone:+48602383548 | proud Debian maintainer and user `- http://skawina.eu.org | jid:[EMAIL PROTECTED] | rlu:172001 signature.asc Description: Digital signature
Bug#305563: ITP: pilotqof -- query Palm PDA data using SQL syntax and write to XML
Package: wnpp
Severity: wishlist
Owner: Neil Williams [EMAIL PROTECTED]
* Package name: pilotqof
Version : 0.0.3
Upstream Author : Neil Williams [EMAIL PROTECTED]
* URL : http://sourceforge.net/projects/pilot-qof/
* License : GPL
Description : query Palm PDA data using SQL syntax and write to XML
Write Palm PDA data - addresses, calendar, tasks and expenses -
as XML to a file or the terminal. Users can run SQL-type queries on
the live data or XML file and output the results of the query as XML.
XML written by pilot-qof can be imported into other applications
that use QOF, including GnuCash. SQL commands can be passed on the
command line or from a file.
pilot-qof uses libpisock (pilot-link) and QOF - the Query Object
Framework.
Homepage: http://pilot-qof.sourceforge.net/
End long description.
Build-Depends: debhelper (= 4.0.0), autotools-dev, libpopt-dev,
libglib1.2-dev, libqof-dev (= 0.5.1), libpisock-dev (= 0.12),
docbook-to-man
Depends: ${shlibs:Depends}, ${misc:Depends}, libqof-0.5.1, libpisock9
The CVS codebase is almost complete but packaging must wait until the
release of code for the two dependencies; QOF and libpisock. libpisock9
is to be released at the same time as pilot-link v0.12 and the code here
is complete. I've got some more code to finish in QOF and hope to make
a file release at the same time as pilot-link 0.12 and libpisock9.
Current pilotqof file release: v0.0.1, CVS v0.0.2
Expected Release at packaging: v0.0.3
More information:
http://code.neil.williamsleesmill.me.uk/pilot-qof/
CVS: http://cvs.sourceforge.net/viewcvs.py/pilot-qof/
Sample man page:
http://code.neil.williamsleesmill.me.uk/pilot-qof.html
Rationale: http://code.neil.williamsleesmill.me.uk/pilot-link.html
The XML format used by pilotqof is documented here:
http://code.neil.williamsleesmill.me.uk/qsf.html
and
http://code.neil.williamsleesmill.me.uk/doxygen/group__QSF.html
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.25-1-686
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: libsilc package policy violations (bug #273871)
Robert McQueen wrote: Tamas SZERB wrote: once upon a time, I closed this bug. then the submitter reopened it, so currently I don't give it a f*ck. Our opinion are different, so if you feel any ambition to get the both sides together, feel free to volunteer. :) This package's violation of Debian policy on the packaging of shared library packages is a fact, not an opinion. You have given no sound reasons why this package is not correctly versioned, or given any indication that you understand the issues at hand, such as how it is expected to retain compatibility with existing packages when the API or ABI undergoes changes (indeed, as it has just done upstream). I saw this email to debian-devel and thought I would take a look at it to try to resolve the problem. I must admit, I don't understand the problem with the versioning. Can you explain it to me further? The libsilc package seems to have similarly named lib* files as other gnome packages. Could you help explain to me more clearly what the problem is with this package against debian 8.1 guidelines? After reading the bug report at bugs.debian.org It's still not clear to me how the package should be changed. It seems quite subtle. I tried comparing it to some of the libgnome* packages to see if I could determine what was correct, but it still wasn't clear to me. Which one is a correct description of the problem? 1) the libsilc package should not contain /usr/lib/libsilc.so at all 2) the /usr/lib/libsilc* symlinks are not correct (wrong names or missing needed names) 3) /usr/lib/libsilcclient-1.0.so.2.1.0 is not the right name 4) the package itself is not the right name curiously, Jeff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Temporal Release Strategy
Adam M wrote: Why? Why is there RHEL 2.0, 3.0.. Why not just RHEL 2005-01-01, 2005-01-02, etc..? Because redhat makes money selling releases. The releases are there to provide interface stability. Everyone does this. Everyone being other distributions? I disagree. How many Fortune 500 customers have you deployed debian for? interface stablility? Anyone that cares looks at packages that matter specifically if it's being deployed commercially. It's much better for acceptance that you don't have to have conversations with managers because someone explains to them that you should be using redhat because you are using Debian unstable or Debian testing and it's *dangerous* and *unstable*. Get rid of these stupid symlinks; debian sid's been superior to fedora for years. Now, if you want to support snapshot of Debian with 36 month security, well, be my guest :) In the last 36-months, there were about 30 uploads of Apache to unstable. Excellent. Now, if only 15 such versions propagated to stable snapshots, then you find a remote hole, and suddenly you have to backport a security fix for 15 versions of Apache! What? Isn't the process: 1) make a patch 2) give it to the apache developers 3) new packaged apache versions have the patch 4) patch makes it upstream 5) patch no longer needed in debian package Also, try providing an efficient stable security build daemons! The chroots would have to be rebuilt for each package. ? I guess I don't understand enough about how the build process works for the packages in debian but that sounds funny to me. Or I just don't understand what you mean. I think this proposal could actually enhance the stability of Debian (where stability is defined as lack of bugs, not software that never changes except for security updates), as well as further enhance the reputation Debian maintains in the community. I totally agree with this a temporal release strategy. In many ways, current testing is your stable. No kidding, so what the heck is the point of having a stable symlink to woody. The stable, testing and unstable symlinks should be removed. They are just being used as FUD by people against debian. Extending the testing period from testing to your proposed candidate and then stable would do nothing about normals bugs. RC bugs are usually found quite quickly by people using unstable. Why not let people choose what they want to use woody sarge or sid and never change the names again. I think lots of people are happy with how things work now. No need to ever do a release again. Just remove the old/arcane symlinks. Almost everyone I know uses sid; I don't think anyone is going to switch to sarge once sid is out. Jeff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[no subject]
Senhores O que necessrio para fazer o curso? H como me enviar uma apostila? LINEAR CONST. E SERV. LTDAAdm. Cezario Ramos da Rocha(92) 656 8002 / 9128 5250
Re: libsilc package policy violations (bug #273871)
On Wed, Apr 20, 2005 at 01:40:14PM -0700, Jeff Carr wrote: Robert McQueen wrote: Tamas SZERB wrote: once upon a time, I closed this bug. then the submitter reopened it, so currently I don't give it a f*ck. Our opinion are different, so if you feel any ambition to get the both sides together, feel free to volunteer. :) This package's violation of Debian policy on the packaging of shared library packages is a fact, not an opinion. You have given no sound reasons why this package is not correctly versioned, or given any indication that you understand the issues at hand, such as how it is expected to retain compatibility with existing packages when the API or ABI undergoes changes (indeed, as it has just done upstream). Could you help explain to me more clearly what the problem is with this package against debian 8.1 guidelines? After reading the bug report at bugs.debian.org It's still not clear to me how the package should be changed. It seems quite subtle. I tried comparing it to some of the libgnome* packages to see if I could determine what was correct, but it still wasn't clear to me. Which one is a correct description of the problem? 1) the libsilc package should not contain /usr/lib/libsilc.so at all 2) the /usr/lib/libsilc* symlinks are not correct (wrong names or missing needed names) 3) /usr/lib/libsilcclient-1.0.so.2.1.0 is not the right name 4) the package itself is not the right name 4) is an approximation, but not actually a correct description (it's the same incorrect approximation used by Policy itself). The problem is that the package name is not being changed when the library soname changes, which means that silc's shlibs are completely useless for preventing breakage of packages depending on it. This is not a theoretical; I recall that when this bug was being discussed on IRC a week or so ago, there were cases of actual packages whose dependencies were satisfied but required a previous silc soname and were therefore completely broken. There is no reason to require any *particular* package name for a library, except that it should be unique; basing it on the soname is the best way to ensure that it's unique in a future-proofed manner. The following command gives the policy-recommended package name for any library: $ objdump -p /tmp/silc/usr/lib/libsilc-1.0.so.2 \ | sed -n -e's/^[[:space:]]*SONAME[[:space:]]*//p' \ | sed -e's/\([0-9]\)\.so\./\1-/; s/\.so\.//' libsilc-1.0-2 $ -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: What do you win by moving things to non-free?
Steve Greenland [EMAIL PROTECTED] wrote: And now you say it's *still* going on? Yes. For various reasons, I'm more hopeful now than I have been previously. -- Matthew Garrett | [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Temporal Release Strategy
On Wed, Apr 20, 2005 at 02:06:12PM -0700, Jeff Carr wrote: Adam M wrote: Why? Why is there RHEL 2.0, 3.0.. Why not just RHEL 2005-01-01, 2005-01-02, etc..? Because redhat makes money selling releases. The releases are there to provide interface stability. Everyone does this. Everyone being other distributions? I disagree. How many Fortune 500 customers have you deployed debian for? interface stablility? Anyone that cares looks at packages that matter specifically if it's being deployed commercially. It's much better for acceptance that you don't have to have conversations with managers because someone explains to them that you should be using redhat because you are using Debian unstable or Debian testing and it's *dangerous* and *unstable*. Get rid of these stupid symlinks; debian sid's been superior to fedora for years. There are at least three different comparisons: Debian sid is comparable to e.g. RedHat Fedora or Gentoo (which of these three is best is a different discussion). Debian sid is for experienced computer users who always want the latest software and who can live with a bug here or there. Debian stable is comparable to personal editions of other distributions like e.g. SuSE Professional. These distributions are for users with few experience who simply want a running system. Debian is a bit behind in terms of being up-to-date and of userfriendlyness, but it's far superior in it's stability. Debian stable is comparable to the enterprise products of e.g. RedHat or SuSE. These distributions are usually installed on servers that are installed and intensively tested once. Security fixes are a must but mustn't cause any breakages. Updates to new upstream versions which might break something Note that you can't cover the last use case without a long-living and non-changing stable. Now, if you want to support snapshot of Debian with 36 month security, well, be my guest :) In the last 36-months, there were about 30 uploads of Apache to unstable. Excellent. Now, if only 15 such versions propagated to stable snapshots, then you find a remote hole, and suddenly you have to backport a security fix for 15 versions of Apache! What? Isn't the process: 1) make a patch 2) give it to the apache developers 3) new packaged apache versions have the patch 4) patch makes it upstream 5) patch no longer needed in debian package Look at the third use case I explained above. For these users of Debian, long-living releases where the _only_ changes are security fixes are _very_ important. ... In many ways, current testing is your stable. No kidding, so what the heck is the point of having a stable symlink to woody. The stable, testing and unstable symlinks should be removed. They are just being used as FUD by people against debian. They are not (see above). Extending the testing period from testing to your proposed candidate and then stable would do nothing about normals bugs. RC bugs are usually found quite quickly by people using unstable. Why not let people choose what they want to use woody sarge or sid and never change the names again. I think lots of people are happy with how things work now. No need to ever do a release again. Just remove the old/arcane symlinks. Almost everyone I know uses sid; I don't think anyone is going to switch to sarge once sid is out. See above. Jeff cu Adrian -- Is there not promise of rain? Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. Only a promise, Lao Er said. Pearl S. Buck - Dragon Seed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Temporal Release Strategy
Adrian Bunk wrote: There are at least three different comparisons: Debian sid is comparable to e.g. RedHat Fedora or Gentoo (which of these three is best is a different discussion). Debian sid is for experienced computer users who always want the latest software and who can live with a bug here or there. I think you nailed that perfectly. This should be the text on the debian website that describes the release and points people to a CD image to install it. Debian stable is comparable to personal editions of other distributions like e.g. SuSE Professional. These distributions are for users with few experience who simply want a running system. Debian is a bit behind in terms of being up-to-date and of userfriendlyness, but it's far superior in it's stability. OK, I like this also, but s/stable/sarge/ and that would be perfect. No reason to alias stable to sarge. Just use the name and be done with it. Debian stable is comparable to the enterprise products of e.g. RedHat or SuSE. These distributions are usually installed on servers that are installed and intensively tested once. Security fixes are a must but mustn't cause any breakages. Updates to new upstream versions which might break something Well, that is wishful thinking, but I've deployed debian sid against RH enterprise and commercial dists. Sometimes sid, sometimes sarge. It really depends on the customer and the competance of their staff. In any case, you are thinking wishfully here and I'm not sure you have deployed debian to large clients. The primary problem is the poor impression that: woody == stable == old sarge/sid == testing/unstable == broken == pain == my servers crash Note that you can't cover the last use case without a long-living and non-changing stable. I think the debian community would be better served if never again the words stable were tied to a particular release. How can you really say woody is any more stable than sid anyway? There are things so broken in the old versions of packages in woody that they can not be used anymore in a modern enviornment. Sure, it might be stable in the sense that it doesn't crash, but useless vs stable is undesirable. Having woody == stable is giving the false impression to people that don't know better that: debian stable == old == obsolete == something is wrong with this picture It just makes it hard to build confidence with decision makers that sid/sarge is safe to use over RHEL. Look at the third use case I explained above. For these users of Debian, long-living releases where the _only_ changes are security fixes are _very_ important. Again, I don't think you ever built a commercial product around Linux based on your statements here. No offence if you have, maybe it's just corporate culture differences between the EU and US? No kidding, so what the heck is the point of having a stable symlink to woody. The stable, testing and unstable symlinks should be removed. They are just being used as FUD by people against debian. They are not (see above). I think I explained poorly what I meant by FUD. What I meant was that people that want other distributions to be used, use the FUD that sarge is dangerous and the only stable version of debian is ancient and too old to use. Enjoy, Jeff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
traduction de la description des paquets
bonjour connaissant debian depuis peu je souhaiterai contribuer à ce projet grace à des traductions d'anglais vers le francais et tout particulierement en ce quiconcerne la desription des paquets ; malheureusement les FAQ semblent obseletes http://lists.debian.org/debian-devel/2001/01/msg02162.html datant de 2001 : y at-il du nouveau? puis-je commencer la traduction des paquets les plus utilisés pour les postes de travail ? en quel format? mais surtout comme l'indique le liens ci-dessus est ce que une des 2 techniques permettant d'inclure la traduction a- t-elle été adoptée? je suis debutant sous linux-debian ( jardinier de metier ) et mes connaissances en informatique sont minimes ; malgré ceci il me tarde de pouvoir aider cet communauté! d'avance merci
Re: libsilc package policy violations (bug #273871)
Steve Langasek wrote: 4) the package itself is not the right name 4) is an approximation, but not actually a correct description (it's the same incorrect approximation used by Policy itself). The problem is that the package name is not being changed when the library soname changes, which means that silc's shlibs are completely useless for preventing breakage of packages depending on it. OK. This is not a theoretical; I recall that when this bug was being discussed on IRC a week or so ago, there were cases of actual packages whose dependencies were satisfied but required a previous silc soname and were therefore completely broken. OK. That's interesting. I wonder if the problem in this case is with the upstream sources. There is no reason to require any *particular* package name for a library, except that it should be unique; basing it on the soname is the best way to ensure that it's unique in a future-proofed manner. The following command gives the policy-recommended package name for any library: OK, thanks for the further enlightenment. I'm afraid I'm still being dense however. If I may, here are some other SONAME files from some other libraries in sid. objdump -p /usr/lib/libsilc-1.0.so.2.1.0 |grep SONAME SONAME libsilc-1.0.so.2 objdump -p /usr/lib/libgnomeui-2.so.0.800.1 |grep SONAME SONAME libgnomeui-2.so.0 objdump -p /usr/lib/libgnomeprint-2-2.so.0.1.0 |grep SONAME SONAME libgnomeprint-2-2.so.0 objdump -p /usr/lib/libgnomecups-1.0.so.1.0.0 |grep SONAME SONAME libgnomecups-1.0.so.1 To finally get understand this problem correctly then, is it that the libsilc-1.0.so.2.1.0 library was the SAME name as a previous version with an identical but incompatable SONAME? So, the problem with this package is that the debian/rules file does not correctly increment the SONAME for incompatable library releases? So, the SONAME in this latest release of the libsilc package should have been something like libsilc-1.0.so.2.1 or libsilc-1.0.so.3 instead of libsilc-1.0.so.2 so that other packages could correctly list the right version as a dependancy? I looked around in debian/* for this package trying to figure out how it might be fixed. Now it seems to me that the problem is more how the last few versions have been packaged versioned, not that this particular version is packaged incorrectly or needs to be changed. So what really needs to happen is future versions need to change the versions in a correct fashion if they are not binary compatible? Thanks for your explianation on this; as it's not clear to me. I'd like to know the correct method of doing things here. Does it sound like I almost understand it right now? Jeff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Temporal Release Strategy
Isn't the process: 1) make a patch 2) give it to the apache developers 3) new packaged apache versions have the patch 4) patch makes it upstream 5) patch no longer needed in debian package You know, there are security updates for stable releases. You have to patch those. If there are 15 versions of Apache in various stable releases, that means 15 packages to apply patches to. Well, let's just say it is less then realistic. Also, try providing an efficient stable security build daemons! The chroots would have to be rebuilt for each package. ? I guess I don't understand enough about how the build process works for the packages in debian but that sounds funny to me. Or I just don't understand what you mean. To build security patches, you need the same libraries, compilers, etc... for the release so the built package has the same ABI. In many ways, current testing is your stable. No kidding, so what the heck is the point of having a stable symlink to woody. The stable, testing and unstable symlinks should be removed. They are just being used as FUD by people against debian. Yes, it is mostly FUD. You can change the symlinks to stale, staging, bleedingedge or whatever. For more information of what is in Debian, and especially its FTP structures, see http://www.debian.org/doc/manuals/reference/ch-system.en.html#s-dists Also, I think you replied to this without even reading the thread. I said his definition of stable, not current stable. Extending the testing period from testing to your proposed candidate and then stable would do nothing about normals bugs. RC bugs are usually found quite quickly by people using unstable. Why not let people choose what they want to use woody sarge or sid and never change the names again. I think lots of people are happy with how things work now. No need to ever do a release again. Just remove the old/arcane symlinks. Almost everyone I know uses sid; I don't think anyone is going to switch to sarge once sid is out. These names will never change. You can still use Slink or Hamm if you want. Oh, and Sid will never release because it is always unstable. See above link for more details. Also, your the last statement shows your lack of understanding of the release process. Instigating needless flamewars, like you just did, is probably the main reason why Ubuntu was created. So, if you are going to rant about something you don't know about (and don't care about since you use Sid, not Sarge), take a break and then think if it's worth it. - Adam
Re: Key management using a USB key
On Tuesday 08 March 2005 10:46, David Härdeman [EMAIL PROTECTED] wrote: o Especially on laptops, it might be interesting to also encrypt all of /home and/or other parts of the harddrive to make the data unusuable without the USB key. But how to integrate this with the other requirements? It seems that this part of your message hasn't been addressed. The best thing to do regarding encryption (IMHO) is to have an encrypted root file system. Boot from a USB device and have an initrd use dm-crypt to decrypt the root file system. A password is not adequate on it's own (anything you can remember can be brute-forced). Get a key from /dev/random and maybe have a password as well. The root file system can contain keys for /home and other file systems. -- http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/Postal SMTP/POP benchmark http://www.coker.com.au/~russell/ My home page
Re: Temporal Release Strategy
On Wed, Apr 20, 2005 at 03:18:52PM -0700, Jeff Carr wrote: Adrian Bunk wrote: ... Debian stable is comparable to the enterprise products of e.g. RedHat or SuSE. These distributions are usually installed on servers that are installed and intensively tested once. Security fixes are a must but mustn't cause any breakages. Updates to new upstream versions which might break something Well, that is wishful thinking, but I've deployed debian sid against RH enterprise and commercial dists. Sometimes sid, sometimes sarge. It really depends on the customer and the competance of their staff. In any case, you are thinking wishfully here and I'm not sure you have deployed debian to large clients. The primary problem is the poor impression that: woody == stable == old sarge/sid == testing/unstable == broken == pain == my servers crash Note that you can't cover the last use case without a long-living and non-changing stable. I think the debian community would be better served if never again the words stable were tied to a particular release. How can you really say woody is any more stable than sid anyway? There are things so broken in the old versions of packages in woody that they can not be used anymore in a modern enviornment. Sure, it might be stable in the sense that it doesn't crash, but useless vs stable is undesirable. Having woody == stable is giving the false impression to people that don't know better that: debian stable == old == obsolete == something is wrong with this picture It just makes it hard to build confidence with decision makers that sid/sarge is safe to use over RHEL. ... Let my try to explain it: The debian stable == obsolete is a release management problem of Debian. One release every year and it would be suitable for most purposes. You say you've deployed Debian sarge and sid in server environments (even sarge, although months old security fixes might be missing???). Let me ask some questions: - How many thousand people can't continue working if the server isn't available? - How many million dollar does the customer lose every day the server is not available? - How many days without this server does it take until the company is bankrupt? If the mail server of a small company isn't running for a few hours it's not a problem - but there are also other environments. Regarding things broken in woody: In many environments, the important number is not the total number of bugs but the number of regressions. Doing intensive tests once when you install/upgrade the machine is acceptable, but requiring this every month because it's required for the security updates that bring new upstream releases is not acceptable. Look at the third use case I explained above. For these users of Debian, long-living releases where the _only_ changes are security fixes are _very_ important. Again, I don't think you ever built a commercial product around Linux based on your statements here. No offence if you have, maybe it's just corporate culture differences between the EU and US? There are reasons why companies pay several thousand dollars licence fees for every computer they run the enterprise version of some distribution on. E.g. RedHat supports each version of their enterprice edition for seven years. A few thousand dollars are _nothing_ compared to the support costs and man months that have to be put into setting up and testing the system. And I doubt these are only corporate culture differences between the EU and US: How many days does it take in the US until a bank is bankrupt after a critical part of their computer infrastructure is broken? No kidding, so what the heck is the point of having a stable symlink to woody. The stable, testing and unstable symlinks should be removed. They are just being used as FUD by people against debian. They are not (see above). I think I explained poorly what I meant by FUD. What I meant was that people that want other distributions to be used, use the FUD that sarge is dangerous and the only stable version of debian is ancient and too old to use. I'd say both is not FUD - it's true. Debian stable is ancient - but that's something you have to ask the Debian release management about. If the officially announced release date for sarge is now missed by more than one and a half years this is the issue where investigation should take place. Regarding sarge: I do personally know people who had serious mail loss due to #220983. At the time I reported this bug, it was present in sarge. This problem couldn't have happened in a Debian stable (because it would have been discovered before the release would have been declared stable). This kind of problems that can occur every day in sarge _are_ dangerous problems. Enjoy, Jeff cu Adrian -- Is there not promise of rain? Ling Tan asked suddenly out of the darkness. There had been
Re: Temporal Release Strategy
Adam M wrote: ? I guess I don't understand enough about how the build process works for the packages in debian but that sounds funny to me. Or I just don't understand what you mean. To build security patches, you need the same libraries, compilers, etc... for the release so the built package has the same ABI. Surely. I just thought there could be only one version of a package in the Packages.gz file. I didn't think each older package that might be in main/a/apache/ would be rebult with the enviornment that it was originally built in. If I understand you correctly and that is what happens, then I see that would be computing intensive. Yes, it is mostly FUD. You can change the symlinks to ... Well, I can't really change them; I was more just giving my point of view as a happy debian user. Also, I think you replied to this without even reading the thread. I said his definition of stable, not current stable. Sorry you are right, I didn't notice this distinction. These names will never change. You can still use Slink or Hamm if you want. Oh, and Sid will never release because it is always unstable. See above link for more details. Yes, I knew that, but tend to forget. It's been years since the last release. Also, your the last statement shows your lack of understanding of the release process. Instigating needless flamewars, like you just did, is Sorry; wasn't trying to do that. Just passing on results of working in a corporate enviornment and the kinds of complaints that have been used against debian deployment. Enjoy, Jeff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Temporal Release Strategy
In article [EMAIL PROTECTED], Jeff Carr [EMAIL PROTECTED] wrote: Why not let people choose what they want to use woody sarge or sid and never change the names again. I think lots of people are happy with how things work now. No need to ever do a release again. Just remove the old/arcane symlinks. Almost everyone I know uses sid; I don't think anyone is going to switch to sarge once sid is out. If almost everyone you know is a desktop user, then I can see your point. But no-one sane running production server systems is going to run sid. Sid aka unstable on a production system means either updating your production system every few days to keep up (sorry customer, we switched to php 6.8 with postgres 17, rewrite your apps and fix your sql or sorry boss, we switched to php 6.8 with postgres 17, the forced rewrite of the production system means the plant will be down for 3 weeks) or you don't upgrade unless needed for security reasons and at that point you have the same problem but then for 300 packages at the same time. That's why you need a stable supported release. No surprises but still security patches. I also think that running debian unstable-only will mean debian will get even less focused. Why update your packages, there's not going to be a release ever anyway. If we're not at that point already. Mike. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Temporal Release Strategy
Adrian Bunk wrote: Let me ask some questions: - How many thousand people can't continue working if the server isn't available? - How many million dollar does the customer lose every day the server is not available? - How many days without this server does it take until the company is bankrupt? These are interesting questions, but not really applicable. I've never seen a corporate enviornment where an upstream or outside distribution is deployed without being tested internally first. I don't think it's something that should be taken into account in the release process. Companies have internal methods for deployment that double check and verify a distribution before it is used. There are reasons why companies pay several thousand dollars licence fees for every computer they run the enterprise version of some distribution on. E.g. RedHat supports each version of their enterprice edition for seven years. I didn't know they had pledged to do that. Interesting. How many days does it take in the US until a bank is bankrupt after a critical part of their computer infrastructure is broken? I don't know. Maybe we should run a test :) Jeff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ITP: spca5xx -- Device driver for USB webcams based on the spca5xx chips
Jeff Carr wrote: I agree. I just built it again today against 2.6.11-1-686-smp (after using it for several months against 2.6.10-1-686-smp). I do not use the debian kernel, i always use the tarball from kernel.org, just because i like this way. I talked to the developer about getting it in the kernel, but he doesn't seem to care. If you want I would be willing to help get some people together to submit it into the main kernel sources. For now, I think it would be best to get it put together as a patch for the debian-kernel team so it will automagically get built for each new 2.6.x kernel. Otherwise, we would have to package it up for each kernel as a seperate patch. I agree, the better is to put it as a kernel-patch. Unfortunetly I have zero experience hacking the kernel or modules, just compiling and using it. Have you already made it into such a patch for the debian kernel sources? If not, I'd be happy to help with that also. No, I doesn't, I always compile the module appart. The only thing I did was little changes to the Makefile to be able to install / uninstall. The driver works great on the built in z-micro USB camera on my portable. Is working great on Creative PC-CAM 300 -- Carlos C Soto :: eclipxe
Re: Temporal Release Strategy
Adrian Bunk [EMAIL PROTECTED] writes: You say you've deployed Debian sarge and sid in server environments (even sarge, although months old security fixes might be missing???). Sure. Frankly, sarge has better security support than we ever got from Sun for commercial versions of Solaris. Don't run the things that aren't secure, pay attention to advisories, and be willing to grab something from sid in the case of dire emergencies, and sarge provides a perfectly acceptable security profile. Servers generally expose very few things to the network and one rarely cares about local exploits. Now, Debian stable is far *better* on security, and in fact I would say that Debian stable has better security support than any other operating system I've ever seen. I would *prefer* to have Debian stable's level of security support for servers. But if I have to have Apache 2.x or some other package that just isn't easily available for stable, going with sarge rather than backports is a reasonable decision and one that I'm quite comfortable with. Really, the worry about using sarge in production is not the security support, it's the fact that things keep changing all the time and in ways that may introduce bugs. The stability and the lack of change in anything other than security are the important bits for stable for me, and what I'm currently really missing in an environment where I'm mostly running sarge (mostly because we need Apache 2.x, partly because we also need a newer OpenLDAP). Regarding sarge: I do personally know people who had serious mail loss due to #220983. At the time I reported this bug, it was present in sarge. This problem couldn't have happened in a Debian stable (because it would have been discovered before the release would have been declared stable). This kind of problems that can occur every day in sarge _are_ dangerous problems. Yeah, this is more the thing that I'd worry about when running sarge on a server. -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ITP: spca5xx -- Device driver for USB webcams based on the spca5xx chips
On Wed, 20 Apr 2005, Carlos C Soto wrote: Jeff Carr wrote: [skipped] I agree, the better is to put it as a kernel-patch. Unfortunetly I have zero experience hacking the kernel or modules, just compiling and using it. If it just compiles separate modules, there is really no need to include it as a kernel patch. You can build a package containing the module sources and employ module-assistant to build them. For details see /usr/share/doc/module-assistant/HOWTO-DEVEL.gz Since it is becoming more and more a kernel topic, you might also want to move discussion to debian-kernel. Best regards, Jurij Smakov[EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Temporal Release Strategy
Miquel van Smoorenburg wrote: If almost everyone you know is a desktop user, Most everyone I know is an engineer :) then I can see your point. But no-one sane running production server systems is going to run sid. Well, I'd say no-one sane is running an unqualified/untested distribution. It doesn't matter when you get it from. Sid aka unstable on a production system means either updating your production system every few days to keep up (sorry customer, we switched to php 6.8 with postgres 17, rewrite your apps and fix your sql or sorry boss, we switched to php 6.8 with postgres 17, the forced rewrite of the production system means the plant will be down for 3 weeks) Yes, all these would clearly be stupid things to do :) I don't blindly deploy distributions to clients in any case; be it commercially released ones or snapshots of other once. (well they are all really snapshots anyway). you don't upgrade unless needed for security reasons and at that point you have the same problem but then for 300 packages at the same time. security is another thing altogether assessed normally via other considerations and needs. That's why you need a stable supported release. No surprises but still security patches. I wasn't trying to suggest that the releases should be unstable or insecure. But these terms are relative and come at a cost don't they? Maybe it's just better to have sarge sid, etc named releases with more complicated descriptions of the intent of the releases like Adrian Bunk wrote so well a few emails back? I also think that running debian unstable-only will mean debian will get even less focused. Ok, I'm not knowledgeable enough to understand all the issues. I just wanted to send encouraging words and feedback to the developers. debian (sid specifically) has, and I hope continues to be, spectacularly well done over the last 5 years. I really think it's the best distribution out there. Why update your packages, there's not going to be a release ever anyway. If we're not at that point already. I'm not sure I'm fully understanding what I sense is frustration with my comments/feedback/suggestions. I'm really just trying to complement everyone involved; mention that sarge and sid are really grand; and pass back the one bad think is that new users get worried when they hear testing and unstable. These are clearly not accurate; I can confidently say that sarge sid are as untested and unstable as mandrake or fedora over the last 5 years. I merely am suggesting that the bar has been raised so high; the standard and expectations set at such a lofty level that the general public might be better served by a more detailed explanation of the releases and the dangers. Again, like the text Adrian wrote a few emails back I think is perfect and might be better than calling them simply stable, testing and unstable. Warm regards, Jeff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Temporal Release Strategy
On Wed, Apr 20, 2005 at 04:23:02PM -0700, Jeff Carr wrote: Adrian Bunk wrote: Let me ask some questions: - How many thousand people can't continue working if the server isn't available? - How many million dollar does the customer lose every day the server is not available? - How many days without this server does it take until the company is bankrupt? These are interesting questions, but not really applicable. I've never seen a corporate enviornment where an upstream or outside distribution is deployed without being tested internally first. I don't think it's something that should be taken into account in the release process. Companies have internal methods for deployment that double check and verify a distribution before it is used. ... Yes, such companies do test all changes. But being sure that it's _very_ unlikely that a security update breaks something makes life much easier. And then there's the class of problems you could recently observe with PHP 4.3.10: PHP 4.3.10 fixed more than half a dozen known security problems, but it also contained a performance regression letting some scripts run slower by a factor of more than 50 (sic). If your distribution gives you PHP 4.3.10 to fix the security problems and you use PHP4 on a busy server you have a big problem in such a situation. Jeff cu Adrian -- Is there not promise of rain? Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. Only a promise, Lao Er said. Pearl S. Buck - Dragon Seed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
spca5xx -- Device driver for USB webcams based on the spca5xx chips
Jurij Smakov wrote: Since it is becoming more and more a kernel topic, you might also want to move discussion to debian-kernel. Could someone give us a simple rundown of how we would submit a patch to the debian kernel sources to add spca5xx support? The spca5xx driver adds support for a large number of USB cameras. Recently Carlos posted something about adding support to debian-devel and Jurij suggested we go here as it is a kernel issue. I've also been using the spca5xx driver for my USB camera against the standard 2.6.8+ kernels for a few months. I just built it against 2.6.11-1-686-smp today. Is the correct way to submit this to build a patch against the 2.6.11 sources, try it out and then post the patch here? Should the patch be just the kernel module, or also patches to the .config files. Just wondering what is easiest. The module dir is self contained and smart in that it uses `uname -r` to determine the kernel headers. So, one can just go into the dir and type make;make install and spca5xx.ko will automatically be loaded the next time the user boots. So I guess I should start by looking at the files in /usr/src/kernel-patches/all/2.6.11/debian/ ? Jeff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Temporal Release Strategy
On 4/20/05, Jeff Carr [EMAIL PROTECTED] wrote: Adam M wrote: ? I guess I don't understand enough about how the build process works for the packages in debian but that sounds funny to me. Or I just don't understand what you mean. To build security patches, you need the same libraries, compilers, etc... for the release so the built package has the same ABI. Surely. I just thought there could be only one version of a package in the Packages.gz file. I didn't think each older package that might be in main/a/apache/ would be rebult with the enviornment that it was originally built in. If I understand you correctly and that is what happens, then I see that would be computing intensive. Well, this is one problem with having automatic releases like this. There are much bigger problems though, like mirror space. The Vancouver proposal trying to address this. If you have a package with versions A for arch A', then maintainer uploads package version B but arch A' can't keep up building it, then the mirrors must have both, versions A and B of the source of the package. Vancouver proposal was trying to move some less popular and/or obsolete arches from the main mirror network to a voluntary one (ie. not trying to kill the ports or something). As you can see, having many overlapping releases like the Temporal Release Strategy would kill the current mirror network. Yes, it is mostly FUD. You can change the symlinks to ... Well, I can't really change them; I was more just giving my point of view as a happy debian user. ... Sorry; wasn't trying to do that. Just passing on results of working in a corporate enviornment and the kinds of complaints that have been used against debian deployment. I would suggest instead of saying you are installing testing, just tell them you are installing Debian Sarge, or Debian 3.1 and set up /etc/apt/sources.list to refer to sarge in place of stable/testing/unstable. There is no use telling people they are running unstable or testing if they don't know what it means in the first place (like telling people about building a nuclear power plant instead of a coal power plant - they'll rise up in protest without realising that coal power plants produce more radiation than a nuclear power plant). - Adam
Re: Bug#302138: incorrect Description line wrapping with bullet lists
On Wednesday 30 March 2005 09:56 am, Daniel Burrows wrote: We can also extend the description format in backwards-compatible ways. So, while a proper markup language would be nice, that doesn't preclude fixing the bullet problem, albeit in a slightly hacky way, NOW. What about this: This proposal is now mostly implemented in aptitude's experimental SVN branch, except that I decided to require exactly N+2 spaces of indentation for the contents of each entry in the list. It seems to work pretty well for most packages, although I haven't tested any packages that use sub-lists yet. (are there any?) A few packages that it can't figure out how to parse are displayed slightly worse -- usually a matter of indentation not quite lining up, so instead of * label: labelled lists are unfortunately not properly supported you get something like * label: labelled lists are unfortunately not properly supported In a quick scan of a few dozen packages, I only saw one (libcroco3) whose description was seriously damaged by the new formatting. Daniel -- /--- Daniel Burrows [EMAIL PROTECTED] --\ | A conclusion is the place | | where you got tired of thinking. | \--- Be like the kid in the movie! Play chess! -- http://www.uschess.org --/ pgp8mQs6MNTZA.pgp Description: PGP signature
Accepted nut 2.0.1-3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 15 Apr 2005 13:52:32 +0100 Source: nut Binary: nut nut-usb nut-dev nut-snmp nut-cgi Architecture: source i386 Version: 2.0.1-3 Distribution: unstable Urgency: low Maintainer: Arnaud Quette [EMAIL PROTECTED] Changed-By: Arnaud Quette [EMAIL PROTECTED] Description: nut- The core system of the nut - Network UPS Tools nut-cgi- A web interface sub system for the nut - Network UPS Tools nut-dev- Development files for the nut - Network UPS Tools nut-snmp - A meta SNMP Driver subsystem for the nut - Network UPS Tools nut-usb- USB Drivers subsystem for the nut - Network UPS Tools Closes: 301060 301184 302182 302902 Changes: nut (2.0.1-3) unstable; urgency=low . * debian/patches/01_cleanSourceFromlibupsclient.dpatch: removed as it has been fixed upstream in 2.0.1 * debian/patches/00list: re enabled for the below patch * debian/patches/01_upsstatsCgiNoHostCrash.dpatch: added while waiting for the upstream fix (closes: #302902) * debian/nut-cgi.templates: added nut-cgi/major_template_changes * debian/nut-cgi.config: use nut-cgi/major_template_changes (closes: #301184) * debian/nut-cgi.README.Debian: reworked, and mention upgrade and installation. * debian/nut.README.Debian: mention the missing UPGRADING file, and complete the upsmon.conf lines with the mandatory POWERDOWNFLAG and SHUTDOWNCMD (closes: #302182) * debian/nut.templates: add nut/2_0_upstream_changes to deal with the new changes * debian/nut.config: use the above nut/2_0_upstream_changes (closes: #301060) Files: 62012e3e41f543dd3c9b5bfde43ae9da 769 admin optional nut_2.0.1-3.dsc fe3de98dc9d88848f3ecbf18a145afba 36228 admin optional nut_2.0.1-3.diff.gz dd57f2201a84fb7a67ef1d80a43ddaa8 856446 admin optional nut_2.0.1-3_i386.deb 869d359b4a363cd29e684ac0144496db 89104 admin optional nut-cgi_2.0.1-3_i386.deb 2ad530fe20914e7aac00c003e93a22cf 68948 admin optional nut-snmp_2.0.1-3_i386.deb 9f2e2e2b9649d5c093ca899015d0a2c3 106926 admin optional nut-usb_2.0.1-3_i386.deb 6d467534e85ffdd8ffdcdca371be811d 75452 admin optional nut-dev_2.0.1-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCZRiY22QUyiBN3xsRAlp7AJ4xFIFFLhv57bn9NXe9AyNQMdHGcgCfeW1g 0tf36teaIafsj83VGi6r/OE= =bn7I -END PGP SIGNATURE- Accepted: nut-cgi_2.0.1-3_i386.deb to pool/main/n/nut/nut-cgi_2.0.1-3_i386.deb nut-dev_2.0.1-3_i386.deb to pool/main/n/nut/nut-dev_2.0.1-3_i386.deb nut-snmp_2.0.1-3_i386.deb to pool/main/n/nut/nut-snmp_2.0.1-3_i386.deb nut-usb_2.0.1-3_i386.deb to pool/main/n/nut/nut-usb_2.0.1-3_i386.deb nut_2.0.1-3.diff.gz to pool/main/n/nut/nut_2.0.1-3.diff.gz nut_2.0.1-3.dsc to pool/main/n/nut/nut_2.0.1-3.dsc nut_2.0.1-3_i386.deb to pool/main/n/nut/nut_2.0.1-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted childsplay 0.80.2-3 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 13 Apr 2005 08:54:41 +0200 Source: childsplay Binary: childsplay Architecture: source all Version: 0.80.2-3 Distribution: unstable Urgency: low Maintainer: Sergio Talens-Oliag [EMAIL PROTECTED] Changed-By: Sergio Talens-Oliag [EMAIL PROTECTED] Description: childsplay - Suite of educational games for young children Closes: 305378 Changes: childsplay (0.80.2-3) unstable; urgency=low . * Fixed the option processing, the wrapper script was not passing them (Closes: Bug#305378). Files: 1344ac2e8647d99e2eac75f07f047d5e 604 games optional childsplay_0.80.2-3.dsc e04c689d73a6df4bd9649e497ca4951b 2657 games optional childsplay_0.80.2-3.diff.gz 2ddcf8e0fd2bc00889f3618fd1f5507c 1182406 games optional childsplay_0.80.2-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCZhbRZ3AFK7jB+mkRAhUsAKCeufaBDS6TH9DNFWEgi0QZqc0ldwCguS9g MYRM4xcpVWo/tdZd5sKR+LM= =kvCt -END PGP SIGNATURE- Accepted: childsplay_0.80.2-3.diff.gz to pool/main/c/childsplay/childsplay_0.80.2-3.diff.gz childsplay_0.80.2-3.dsc to pool/main/c/childsplay/childsplay_0.80.2-3.dsc childsplay_0.80.2-3_all.deb to pool/main/c/childsplay/childsplay_0.80.2-3_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted rats 2.1-4 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 21 Apr 2005 10:21:30 + Source: rats Binary: rats Architecture: source i386 Version: 2.1-4 Distribution: unstable Urgency: medium Maintainer: Steve Kemp [EMAIL PROTECTED] Changed-By: Steve Kemp [EMAIL PROTECTED] Description: rats - Rough Auditing Tool for Security Closes: 288195 301422 305233 305240 Changes: rats (2.1-4) unstable; urgency=medium . * Fixed FTBFS bug on amd64/gcc-4.0. Patch from Andreas Jochens. (Closes: #301422) * Escape HTML in output, patch from Ulf Harnhammar (Closes: #305240) * Fixed typos in help output, patch from Ulf Harnhammar (Closes: #305233) * Updated broken homepage link in package description. (Closes: #288195) Files: 826b7e28dc6baec2886c18a7b2d89e0a 561 utils optional rats_2.1-4.dsc 2c4e753a1a98de0beb1cfd602f126ae6 63579 utils optional rats_2.1-4.diff.gz 80aa6943a559fe388d85cccbfebf7095 159192 utils optional rats_2.1-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCZh+4wM/Gs81MDZ0RAlWXAJ9ew0s1xwyaCPUr4vlGjEq71EGmWgCgvPVp 4jQ6I89dEI4KLM3p7kTHiWo= =LpHF -END PGP SIGNATURE- Accepted: rats_2.1-4.diff.gz to pool/main/r/rats/rats_2.1-4.diff.gz rats_2.1-4.dsc to pool/main/r/rats/rats_2.1-4.dsc rats_2.1-4_i386.deb to pool/main/r/rats/rats_2.1-4_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted vim-scripts 6-1 (all source)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Fri, 8 Apr 2005 17:39:18 +0200
Source: vim-scripts
Binary: vim-scripts
Architecture: source all
Version: 6-1
Distribution: unstable
Urgency: low
Maintainer: Michael Piefel [EMAIL PROTECTED]
Changed-By: Stefano Zacchiroli [EMAIL PROTECTED]
Description:
vim-scripts - plugins for vim, adding bells and whistles
Closes: 303587 303589 303592
Changes:
vim-scripts (6-1) unstable; urgency=low
.
* major review of shipped scripts
- added scripts: plugin/{EnhancedCommentify.vim,calendar.vim,
gnupg.vim,minibufexpl.vim,svncommand.vim,themes.vim,utl.vim,
vimspell.vim,winmanager.vim}, ftplugin/xml.vim
(Closes: Bug#303587, Bug#303589, Bug#303592)
- removed scripts: closetag.vim
- upgraded to latest version on vim.org scripts: ftplugin/po.vim,
plugin/{Align.vim, a.vim, bufexplorer.vim, cvscommand.vim,
cvsmenu.vim, taglist.vim, whatdomain.vim}
- replaced scripts: colors/* (by themes.vim above), plugin/thlnk.vim
(by utl.vim)
* ship webpages of scripts in html/; registered them to doc-base
* debian/rules
- install scripts in /usr/share/vim-scripts/ instead of
/usr/share/doc/vim-scripts/examples/. Symlink provided for
backward compatibility
- invokes dh_compress
- moved debhelper compatibility level to debian/compat
* use dpatch, changed debian/{control,rules,patches} as needed
* debian/control
- bumped debhelper dependency and Stadards-Version
- added me as an uploader
* debian/vim-scripts.pl
- added perl scripts which eases download of vim.org script web
pages and upstream version checks
* debian/copyright
- rewritten including copyright/license information about all
shipped script
* improved debian/README.Debian
* removed upstream README, now vim-scripts is a native package and
script descriptions are available in html/
Files:
84e1a026baf8ef4ae9f96a43a48add9c 564 editors optional vim-scripts_6-1.dsc
239c1a41652e588119198b2c73599f28 478781 editors optional vim-scripts_6-1.tar.gz
c905ac0b8908ac96f5fbb79272a73ccb 485666 editors optional
vim-scripts_6-1_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQFCZWzq1cqbBPLEI7wRAlgQAKC9V62HZIciZSXCHhPYpQ7a+FQ4qwCgo+78
4M5M94ZKCzmiu9w0+t/NQuc=
=nBn9
-END PGP SIGNATURE-
Accepted:
vim-scripts_6-1.dsc
to pool/main/v/vim-scripts/vim-scripts_6-1.dsc
vim-scripts_6-1.tar.gz
to pool/main/v/vim-scripts/vim-scripts_6-1.tar.gz
vim-scripts_6-1_all.deb
to pool/main/v/vim-scripts/vim-scripts_6-1_all.deb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted tiemu 1.99+svn1148-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Apr 2005 11:33:10 +0200 Source: tiemu Binary: tiemu Architecture: source i386 Version: 1.99+svn1148-1 Distribution: unstable Urgency: low Maintainer: Julien BLACHE [EMAIL PROTECTED] Changed-By: Julien BLACHE [EMAIL PROTECTED] Description: tiemu - Texas Instruments calculators emulator Changes: tiemu (1.99+svn1148-1) unstable; urgency=low . * New upstream snapshot. Files: adc3e1875fbcd741a656e67e092b1ddb 730 math optional tiemu_1.99+svn1148-1.dsc 5205cb74224e18d8123912fde49c5849 2324489 math optional tiemu_1.99+svn1148.orig.tar.gz 4c024fa5e9cc3a0e527ac27ebb419c4a 3613 math optional tiemu_1.99+svn1148-1.diff.gz d6ac909440d7e0a88c2c57f1fe3f5061 1494572 math optional tiemu_1.99+svn1148-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCZiYPzWFP1/XWUWkRAnrmAKCDQJqdOKnlO/sG5M6byGWrsQ8/0gCfYZbk DGJbLwql5MnMUCRNglYrV6s= =HkXU -END PGP SIGNATURE- Accepted: tiemu_1.99+svn1148-1.diff.gz to pool/main/t/tiemu/tiemu_1.99+svn1148-1.diff.gz tiemu_1.99+svn1148-1.dsc to pool/main/t/tiemu/tiemu_1.99+svn1148-1.dsc tiemu_1.99+svn1148-1_i386.deb to pool/main/t/tiemu/tiemu_1.99+svn1148-1_i386.deb tiemu_1.99+svn1148.orig.tar.gz to pool/main/t/tiemu/tiemu_1.99+svn1148.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted swami 0.9.2-5 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Apr 2005 12:08:40 +0200 Source: swami Binary: swami Architecture: source i386 Version: 0.9.2-5 Distribution: unstable Urgency: low Maintainer: Guenter Geiger (Debian/GNU) [EMAIL PROTECTED] Changed-By: Guenter Geiger (Debian/GNU) [EMAIL PROTECTED] Description: swami - SoundFont editor Changes: swami (0.9.2-5) unstable; urgency=low . * added replaces and conflicts fields for smurf Files: 53b36900f96e8b95f748f5b8e506b6d0 695 sound optional swami_0.9.2-5.dsc 925aa212d605aacba285965de4dfd71d 2154 sound optional swami_0.9.2-5.diff.gz 09499cbe74028145b6c657efb23f6e85 580350 sound optional swami_0.9.2-5_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCZitT1pbKhmC2uVgRApTpAJ9ET13zMHcGw12iXcmHoH6I3nEADACdHd2n +g6+uUjeNviCIytlde4Fnwc= =Udsm -END PGP SIGNATURE- Accepted: swami_0.9.2-5.diff.gz to pool/main/s/swami/swami_0.9.2-5.diff.gz swami_0.9.2-5.dsc to pool/main/s/swami/swami_0.9.2-5.dsc swami_0.9.2-5_i386.deb to pool/main/s/swami/swami_0.9.2-5_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted rezound 0.11.1beta-5 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Apr 2005 12:29:46 +0200 Source: rezound Binary: rezound Architecture: source i386 Version: 0.11.1beta-5 Distribution: unstable Urgency: low Maintainer: Guenter Geiger (Debian/GNU) [EMAIL PROTECTED] Changed-By: Guenter Geiger (Debian/GNU) [EMAIL PROTECTED] Description: rezound- Audio file editor Closes: 267985 299368 Changes: rezound (0.11.1beta-5) unstable; urgency=low . * Added icon (closes: #299368) * Checked the ugly font problem, seems to have been fixed outside the package (closes: #267985) Files: 3c9e68c4b761a4ac811462242e7f32e6 815 sound optional rezound_0.11.1beta-5.dsc e8ba4a975931d07b1b8a3446c67b8193 132906 sound optional rezound_0.11.1beta-5.diff.gz ae069b86c7bf4b7b29844912b5f53382 1392196 sound optional rezound_0.11.1beta-5_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCZj0V1pbKhmC2uVgRAnboAJ9iU4bxdee+36NDQ4KBVGzgnLjiHQCeITUp 8LukSKuEfTVTxw7EFqj+R0g= =H5oA -END PGP SIGNATURE- Accepted: rezound_0.11.1beta-5.diff.gz to pool/main/r/rezound/rezound_0.11.1beta-5.diff.gz rezound_0.11.1beta-5.dsc to pool/main/r/rezound/rezound_0.11.1beta-5.dsc rezound_0.11.1beta-5_i386.deb to pool/main/r/rezound/rezound_0.11.1beta-5_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cdbs 0.4.28-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Apr 2005 07:59:51 -0400 Source: cdbs Binary: cdbs Architecture: source all Version: 0.4.28-1 Distribution: unstable Urgency: low Maintainer: CDBS Hackers [EMAIL PROTECTED] Changed-By: Jeff Bailey [EMAIL PROTECTED] Description: cdbs - common build system for Debian packages Changes: cdbs (0.4.28-1) unstable; urgency=low . * Merge changes from Ubuntu (0.4.26-1ubuntu1): . Add cdbs-edit-patch script; similar to dpatch-edit-patch to edit an existing patch or create a new one. Does not yet work with tarball.mk, use dbs-edit-patch in this case for now. . Thanks to Martin Pitt for the script! Files: 5dc5bc98c231638cf9ebce4e18f19cb4 926 devel optional cdbs_0.4.28-1.dsc 092b5c8efab52bf3b1d8593cc098ffe8 239738 devel optional cdbs_0.4.28-1.tar.gz cb767f45a05119c03f734666ca2ae95c 66490 devel optional cdbs_0.4.28-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCZkNH5M5hmdCYCpkRAlmkAJ4wux0co92lPC/29uuiGwXVIUjGgACgln2r 714w3QqzcaYquBw2GDwIRcw= =y0LQ -END PGP SIGNATURE- Accepted: cdbs_0.4.28-1.dsc to pool/main/c/cdbs/cdbs_0.4.28-1.dsc cdbs_0.4.28-1.tar.gz to pool/main/c/cdbs/cdbs_0.4.28-1.tar.gz cdbs_0.4.28-1_all.deb to pool/main/c/cdbs/cdbs_0.4.28-1_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted hplip 0.9.2-1 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Apr 2005 10:05:59 -0300 Source: hplip Binary: hpijs hplip-data hplip Architecture: source i386 all Version: 0.9.2-1 Distribution: unstable Urgency: medium Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed-By: Henrique de Moraes Holschuh [EMAIL PROTECTED] Description: hpijs - HP Linux Printing and Imaging - gs IJS driver (hpijs) hplip - HP Linux Printing and Imaging System (hplip) hplip-data - HP Linux Printing and Imaging - data files Closes: 210449 291346 302828 Changes: hplip (0.9.2-1) unstable; urgency=medium . * New upstream version * HPIJS 2.1.2: + Added new print mode FastDraft Grayscale to DJGenericVIP + Put limit (max=5) on syslog messages when output device write() fails (closes: #210449) + Removed specified gcc options in hpijs configure.in + Fixed a 64-bit compile issue in ljjetready.cpp (closes: #302828) * HPLIP 0.9.2: + Fixed Invalid color calibration type error occurs when executing command colorcal in terminal + Fixed number of arguments error in hp-align + Made UI architectural change (removed hpguid.py, removed popup feature, etc) + Fixed a scanning issue with Laserjet flatbed scanners (PML scanners). Scan would fail at end of scan + Removed images.tgz after install + Fixed a problem when all function buttons are grayed out when toolbox is launched at the first time. + Fixed DJ450 battery check issue * Henrique de Moraes Holschuh: * Updated dpatch 11_fix-misc-gcc-warnings with many new hunks * Added 40_testmail_fix, to get hpssd and Test Email functionality to actually work (it was completely useless and hopelessly broken) (closes: #291346) * Updated README.Debian files for HPIJS and HPLIP Files: 869e5217941e4c782882be8a0d4ff7a6 1056 utils optional hplip_0.9.2-1.dsc 412b5af48fab81cac752f09b99dce035 8994468 utils optional hplip_0.9.2.orig.tar.gz f61e7199b851e8dcce0dcb3f1e52fdcf 63222 utils optional hplip_0.9.2-1.diff.gz 12b8de565aad38b0d5dd29bbf0811584 7075058 utils optional hplip-data_0.9.2-1_all.deb 2bdd0b30d3d87441a81aa80967491506 216108 utils optional hpijs_2.1.2+0.9.2-1_i386.deb 5ca1ab29a71e1aa794e673cde70507ac 385148 utils optional hplip_0.9.2-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iQEVAwUBQmZXUIjztdzjjnrPAQJmVQgAlqVnx0R2qatl3dAVR6AsuK4+gZkiMP4K aXf+7U0ahLh6bYdDCatz83ZUebfs3OJrUYXoTNfAkRwizlsJ10pOaSMK0fbXSQ5G rq3FLw05XHa6dtotMKIwmoyzKFmG2FnnjpgRGe6NB/vYh6Opkcz8p7I+JRA0A3nr LXlwmS6oJn5RN/AupOPVrTPd3dpxWYbAbn/zDqNZIDb+aU7I6vtyf2/iiUImkxGO 9xdnWqfUy1TWL1OVsOKgFeD+VBVtXqOoFy45bsogT90c5J5nXFCWAz+PN0i5WuJU 6cm7DoovRlird930ghIl/ckhX2IKLEpFJSd09EeaWGqf0VwNmgp5Ow== =Hw1d -END PGP SIGNATURE- Accepted: hpijs_2.1.2+0.9.2-1_i386.deb to pool/main/h/hplip/hpijs_2.1.2+0.9.2-1_i386.deb hplip-data_0.9.2-1_all.deb to pool/main/h/hplip/hplip-data_0.9.2-1_all.deb hplip_0.9.2-1.diff.gz to pool/main/h/hplip/hplip_0.9.2-1.diff.gz hplip_0.9.2-1.dsc to pool/main/h/hplip/hplip_0.9.2-1.dsc hplip_0.9.2-1_i386.deb to pool/main/h/hplip/hplip_0.9.2-1_i386.deb hplip_0.9.2.orig.tar.gz to pool/main/h/hplip/hplip_0.9.2.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted rmatrix 0.95.7-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Apr 2005 08:38:38 -0500 Source: rmatrix Binary: r-cran-matrix Architecture: source i386 Version: 0.95.7-1 Distribution: unstable Urgency: low Maintainer: Douglas Bates [EMAIL PROTECTED] Changed-By: Douglas Bates [EMAIL PROTECTED] Description: r-cran-matrix - GNU R package of classes for dense and sparse matrices Changes: rmatrix (0.95.7-1) unstable; urgency=low . * New upstream release Files: 51a25726266e95b2e7a604bff3b6ecc1 619 math optional rmatrix_0.95.7-1.dsc acd329c996c1a635448e4035be442560 670786 math optional rmatrix_0.95.7.orig.tar.gz 7e91047f164a348569bc206f550a3fd3 2400 math optional rmatrix_0.95.7-1.diff.gz 296003ed1adbf6a2ffef4517db573408 774738 math optional r-cran-matrix_0.95.7-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCZlvqhKhE9v5h4HkRAsQMAKC8u8loF378xe6nySC1w7fyQoQYewCdE+Ia tzM18C/h6Mp/a75fQSNCC+8= =XXJB -END PGP SIGNATURE- Accepted: r-cran-matrix_0.95.7-1_i386.deb to pool/main/r/rmatrix/r-cran-matrix_0.95.7-1_i386.deb rmatrix_0.95.7-1.diff.gz to pool/main/r/rmatrix/rmatrix_0.95.7-1.diff.gz rmatrix_0.95.7-1.dsc to pool/main/r/rmatrix/rmatrix_0.95.7-1.dsc rmatrix_0.95.7.orig.tar.gz to pool/main/r/rmatrix/rmatrix_0.95.7.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted lme4 0.95.6-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Apr 2005 08:50:10 -0500 Source: lme4 Binary: r-cran-lme4 Architecture: source i386 Version: 0.95.6-1 Distribution: unstable Urgency: low Maintainer: Douglas Bates [EMAIL PROTECTED] Changed-By: Douglas Bates [EMAIL PROTECTED] Description: r-cran-lme4 - GNU R package for linear mixed effects model fitting. Changes: lme4 (0.95.6-1) unstable; urgency=low . * New upstream release Files: d7fceb264e0e9b244c67ba40320cc6e0 640 math optional lme4_0.95.6-1.dsc 0f33cffc7e64b9787b3aa60f05ea0b64 263502 math optional lme4_0.95.6.orig.tar.gz c13ce7a8ff915f4bf32d0a027a914fdc 2359 math optional lme4_0.95.6-1.diff.gz 7132cae5cef8b937af2a97e908072955 383182 math optional r-cran-lme4_0.95.6-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCZl7XhKhE9v5h4HkRAhuqAKCdGnV7sCd9x/XtFw2byuV/tcF7jwCgtnhl LJ3BrZ9eKYkc3WZrmO6OPGA= =+5WH -END PGP SIGNATURE- Accepted: lme4_0.95.6-1.diff.gz to pool/main/l/lme4/lme4_0.95.6-1.diff.gz lme4_0.95.6-1.dsc to pool/main/l/lme4/lme4_0.95.6-1.dsc lme4_0.95.6.orig.tar.gz to pool/main/l/lme4/lme4_0.95.6.orig.tar.gz r-cran-lme4_0.95.6-1_i386.deb to pool/main/l/lme4/r-cran-lme4_0.95.6-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libticables3 3.8.9-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Apr 2005 15:49:28 +0200 Source: libticables3 Binary: libticables3 libticables3-dev Architecture: source i386 Version: 3.8.9-2 Distribution: unstable Urgency: low Maintainer: Julien BLACHE [EMAIL PROTECTED] Changed-By: Julien BLACHE [EMAIL PROTECTED] Description: libticables3 - support library for Texas Instruments link cables libticables3-dev - support library for Texas Instruments link cables [development fi Changes: libticables3 (3.8.9-2) unstable; urgency=low . * Replaced the hotplug script by a new hotplug hook. Files: 84356c693b6a3c80406906b43ec26f2e 694 libs optional libticables3_3.8.9-2.dsc 73d347f8ad059b161ea504ce91f1d8b0 4712 libs optional libticables3_3.8.9-2.diff.gz fb40fb3eb160b3feafc8499673744cd0 84550 libdevel optional libticables3-dev_3.8.9-2_i386.deb 29cb6619b492d57ca7c61d9c68ad3380 50634 libs optional libticables3_3.8.9-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCZl8SzWFP1/XWUWkRAs9JAKDHw9fFHTWbjcSALGgxrJ5WrKptkgCglWU9 BCCSOOkFoyQKSs4TLODtwEY= =SMd5 -END PGP SIGNATURE- Accepted: libticables3-dev_3.8.9-2_i386.deb to pool/main/libt/libticables3/libticables3-dev_3.8.9-2_i386.deb libticables3_3.8.9-2.diff.gz to pool/main/libt/libticables3/libticables3_3.8.9-2.diff.gz libticables3_3.8.9-2.dsc to pool/main/libt/libticables3/libticables3_3.8.9-2.dsc libticables3_3.8.9-2_i386.deb to pool/main/libt/libticables3/libticables3_3.8.9-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted nss-updatedb 3-2 (powerpc source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Apr 2005 15:53:55 +0200 Source: nss-updatedb Binary: nss-updatedb Architecture: source powerpc Version: 3-2 Distribution: unstable Urgency: low Maintainer: Guido Guenther [EMAIL PROTECTED] Changed-By: Guido Guenther [EMAIL PROTECTED] Description: nss-updatedb - Maintain local cache of a network directory Changes: nss-updatedb (3-2) unstable; urgency=low . * let main() return zero instead of NSS_UPDATE_SUCCESS Files: 8942aaf276b07e3f847dbeb0f57808ce 602 net optional nss-updatedb_3-2.dsc 33f2e2083321430d8360a748a9f7583e 15876 net optional nss-updatedb_3-2.diff.gz 6e5ea3626cd2d80807fd37988bd874e9 9502 net optional nss-updatedb_3-2_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCZmDsn88szT8+ZCYRApsIAJ4rsa070/XxiTzLHn6BHsATv41gVACbBCDX n/TW055O2I/4MFTEbmBWx6U= =5bmh -END PGP SIGNATURE- Accepted: nss-updatedb_3-2.diff.gz to pool/main/n/nss-updatedb/nss-updatedb_3-2.diff.gz nss-updatedb_3-2.dsc to pool/main/n/nss-updatedb/nss-updatedb_3-2.dsc nss-updatedb_3-2_powerpc.deb to pool/main/n/nss-updatedb/nss-updatedb_3-2_powerpc.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted d4x 2.5.0rel-4 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Apr 2005 16:41:35 +0200 Source: d4x Binary: d4x Architecture: source i386 Version: 2.5.0rel-4 Distribution: unstable Urgency: low Maintainer: Julien BLACHE [EMAIL PROTECTED] Changed-By: Julien BLACHE [EMAIL PROTECTED] Description: d4x- graphical download manager Closes: 304397 305157 Changes: d4x (2.5.0rel-4) unstable; urgency=low . * Added new .desktop file, courtesy of Dan Korostelev (closes: #304397). * New description and XPM icon, also courtesy of Dan Korostelev (closes: #305157). Files: 457af6aa2eb480a6751c815c959efb3f 655 net optional d4x_2.5.0rel-4.dsc 99023fe779b8927a4222c0d4cc606357 10367 net optional d4x_2.5.0rel-4.diff.gz 02eaf2aca3024871667d41151bfcb912 1196120 net optional d4x_2.5.0rel-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCZm9dzWFP1/XWUWkRAtG+AKCfJgKh7oVsPurtPjByU/BckBnwlgCeImiQ m6VJ/AGRjDvJhmBzxgpaCiI= =Iy88 -END PGP SIGNATURE- Accepted: d4x_2.5.0rel-4.diff.gz to pool/main/d/d4x/d4x_2.5.0rel-4.diff.gz d4x_2.5.0rel-4.dsc to pool/main/d/d4x/d4x_2.5.0rel-4.dsc d4x_2.5.0rel-4_i386.deb to pool/main/d/d4x/d4x_2.5.0rel-4_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted sane-backends 1.0.15-9 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Apr 2005 16:17:20 +0200 Source: sane-backends Binary: libsane-dev sane-utils libsane Architecture: source i386 Version: 1.0.15-9 Distribution: unstable Urgency: low Maintainer: Julien BLACHE [EMAIL PROTECTED] Changed-By: Julien BLACHE [EMAIL PROTECTED] Description: libsane- API library for scanners libsane-dev - API development library for scanners [development files] sane-utils - API library for scanners -- utilities Closes: 302334 302675 Changes: sane-backends (1.0.15-9) unstable; urgency=low . * debian/patches/22_dll_backend_conf.dpatch: + Process /etc/sane.d/dll.d first, so that those backends will be loaded last. This will prevent buggy extras backends to perturb other backends. * debian/patches/03_manpages_fixes.dpatch: + Fix a typo in sane(7), reported by A Costa (closes: #302675). + Fix 3 typos in scanimage(1), also reported by A Costa (closes: #302334). Files: 9069d2ac513e5fdc7ca05aa000798e37 828 graphics optional sane-backends_1.0.15-9.dsc 27a3793e0ebec4b1698fa80fefe2f7a2 64566 graphics optional sane-backends_1.0.15-9.diff.gz 6958f51d37a67878b390a9866b3f4ac6 113094 graphics optional sane-utils_1.0.15-9_i386.deb 4fc2ea8b7f5dbcc44d46ab72916356e4 2540712 libs optional libsane_1.0.15-9_i386.deb 1b6dbfddeca741e863e489dca6290b86 2090154 libdevel optional libsane-dev_1.0.15-9_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCZmfGzWFP1/XWUWkRAiFNAJ9K7I2hCXrJfOXk6B25V041/hRcbQCgtXqm oweEH1ehfcrt5LBMB15PJQQ= =CPpW -END PGP SIGNATURE- Accepted: libsane-dev_1.0.15-9_i386.deb to pool/main/s/sane-backends/libsane-dev_1.0.15-9_i386.deb libsane_1.0.15-9_i386.deb to pool/main/s/sane-backends/libsane_1.0.15-9_i386.deb sane-backends_1.0.15-9.diff.gz to pool/main/s/sane-backends/sane-backends_1.0.15-9.diff.gz sane-backends_1.0.15-9.dsc to pool/main/s/sane-backends/sane-backends_1.0.15-9.dsc sane-utils_1.0.15-9_i386.deb to pool/main/s/sane-backends/sane-utils_1.0.15-9_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted pavuk 0.9.32-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Apr 2005 15:48:34 + Source: pavuk Binary: pavuk Architecture: source i386 Version: 0.9.32-1 Distribution: unstable Urgency: high Maintainer: Petr Cech [EMAIL PROTECTED] Changed-By: Petr Cech [EMAIL PROTECTED] Description: pavuk - Multiprotocol file grabber with textual and graphic control Closes: 203089 304553 Changes: pavuk (0.9.32-1) unstable; urgency=high . * New upstream release (closes: #304553, #203089) * debian/rules: - s/dh_installmanpages/dh_installman/ - Don't install testing scripts. - Use --disable-gtk2 to force usage of gtk1.2 * debian/copyright: new upstream location Files: 7a68b85d9aaa39035b94f9ed870bc824 703 web optional pavuk_0.9.32-1.dsc 511d3a25917fb283d08f57c9e16b3a66 868264 web optional pavuk_0.9.32.orig.tar.gz f15915c49423f8007f0b99a18f04578d 5942 web optional pavuk_0.9.32-1.diff.gz edac6614ea34d1d0532a7576859bfbc4 678952 web optional pavuk_0.9.32-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCZn7j0VL/2tBqhlQRAp1iAJ9bNHC3XplsD3NFGGIiqYH2RWDUywCgsJ+z oGNP+FoW7hdkc6G13B+GulY= =+g8G -END PGP SIGNATURE- Accepted: pavuk_0.9.32-1.diff.gz to pool/main/p/pavuk/pavuk_0.9.32-1.diff.gz pavuk_0.9.32-1.dsc to pool/main/p/pavuk/pavuk_0.9.32-1.dsc pavuk_0.9.32-1_i386.deb to pool/main/p/pavuk/pavuk_0.9.32-1_i386.deb pavuk_0.9.32.orig.tar.gz to pool/main/p/pavuk/pavuk_0.9.32.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gnuradio-core 2.5-3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Apr 2005 22:04:13 +0530 Source: gnuradio-core Binary: gnuradio-doc libgnuradio-core0 python-gnuradio libgnuradio-core0-dev Architecture: source i386 Version: 2.5-3 Distribution: unstable Urgency: low Maintainer: Ramakrishnan Muthukrishnan [EMAIL PROTECTED] Changed-By: Ramakrishnan Muthukrishnan [EMAIL PROTECTED] Description: gnuradio-doc - Software Defined Radio libgnuradio-core0 - Software Defined Radio libgnuradio-core0-dev - Software Defined Radio python-gnuradio - Python bindings for GNURadio Changes: gnuradio-core (2.5-3) unstable; urgency=low . * libcppunit on my system was a bit old and had the bug #297026 open and so i386 build I uploaded was broken. Uploading with proper linking and with proper version in the build dependency. Files: 186300fd7624f57eabb4957d1c16ecdd 808 - optional gnuradio-core_2.5-3.dsc 9f527142132798aaa259add4c327c1d1 12692 - optional gnuradio-core_2.5-3.diff.gz 060e35566a0f30db637e96fb94014dc7 636912 libdevel optional libgnuradio-core0-dev_2.5-3_i386.deb 5b022ab76eadfffd4f5c006c8be597f8 366488 libs optional libgnuradio-core0_2.5-3_i386.deb f552a110d6ffef590a5e435b7eef721b 628228 doc optional gnuradio-doc_2.5-3_i386.deb 37e780a76c3d507811527bce6a8ae011 2268684 python optional python-gnuradio_2.5-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFCZonQFyn1hmqfPDgRAnGaAJ41iZ1mGbJDuyatmiq3NHPzrpLCMQCeInSz K5O5lUJOCcVxtUw4431tQ5M= =4T5P -END PGP SIGNATURE- Accepted: gnuradio-core_2.5-3.diff.gz to pool/main/g/gnuradio-core/gnuradio-core_2.5-3.diff.gz gnuradio-core_2.5-3.dsc to pool/main/g/gnuradio-core/gnuradio-core_2.5-3.dsc gnuradio-doc_2.5-3_i386.deb to pool/main/g/gnuradio-core/gnuradio-doc_2.5-3_i386.deb libgnuradio-core0-dev_2.5-3_i386.deb to pool/main/g/gnuradio-core/libgnuradio-core0-dev_2.5-3_i386.deb libgnuradio-core0_2.5-3_i386.deb to pool/main/g/gnuradio-core/libgnuradio-core0_2.5-3_i386.deb python-gnuradio_2.5-3_i386.deb to pool/main/g/gnuradio-core/python-gnuradio_2.5-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted kaffe 2:1.1.5-3 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Apr 2005 14:56:13 +0200 Source: kaffe Binary: kaffe-dev kaffe-common jikes-kaffe kaffe-pthreads-profile kaffe-pthreads kaffe kaffe-doc kaffe-jthreads Architecture: source all i386 Version: 2:1.1.5-3 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers [EMAIL PROTECTED] Changed-By: Jeroen van Wolffelaar [EMAIL PROTECTED] Description: jikes-kaffe - Wrapper for jikes using Kaffe classes kaffe - A JVM to run Java bytecode kaffe-common - Files shared between all Kaffe VM versions kaffe-dev - Header files and other resources for building against Kaffe kaffe-doc - Documentation for the Kaffe VM kaffe-jthreads - A green threads enabled version of the Kaffe VM kaffe-pthreads - A POSIX threads enabled version of the Kaffe VM kaffe-pthreads-profile - A POSIX threads and profiling enabled version of the Kaffe VM Changes: kaffe (2:1.1.5-3) unstable; urgency=low . * Added myself to uploaders * SIGKILL kaffe in testsuite when SIGTERM doesn't work, prevent timeouts during build. Also reduce timeout to 30 seconds to speed up build in case something is not working well * Added amd64 patch by Kurt to fix a 64bit issue in FileChannel (avdyk) Files: 91a010c9558058fc39982d643cc4c6a9 1165 interpreters optional kaffe_1.1.5-3.dsc 97b72e0e92b1094a32c4c71055e8d010 35118 interpreters optional kaffe_1.1.5-3.diff.gz 758b3980938ad4f24ca5d9418f5634bb 25352 interpreters optional kaffe_1.1.5-3_all.deb 7b6d2e61eb3203ba1a9b2ec348a28ed8 6351442 interpreters optional kaffe-common_1.1.5-3_all.deb 883641f7e5fe052aedbec22cd5e82db3 41754 interpreters optional kaffe-dev_1.1.5-3_all.deb 2400c2c7607eea2f177a644abe378a8c 24466 interpreters optional jikes-kaffe_1.1.5-3_all.deb 4caf4d1fb5382c0cfd6c716d135c994a 106226 interpreters optional kaffe-doc_1.1.5-3_all.deb 06b9b647a0e5dba9f522fef54e87f8fa 494468 interpreters optional kaffe-jthreads_1.1.5-3_i386.deb 37598398157ae7c47126c07c8b3b3e90 594636 interpreters optional kaffe-pthreads_1.1.5-3_i386.deb 16d8766d71f13ad107cfc828ac544d0b 3908354 interpreters optional kaffe-pthreads-profile_1.1.5-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Signed by Jeroen van Wolffelaar [EMAIL PROTECTED] iD8DBQFCZo/gl2uISwgTVp8RAvitAKDG/IULyqNj4+fME/318YjUsNkL5wCfeAa9 wLtBkG/j0LyiCpBSc5uv1aI= =v/bW -END PGP SIGNATURE- Accepted: jikes-kaffe_1.1.5-3_all.deb to pool/main/k/kaffe/jikes-kaffe_1.1.5-3_all.deb kaffe-common_1.1.5-3_all.deb to pool/main/k/kaffe/kaffe-common_1.1.5-3_all.deb kaffe-dev_1.1.5-3_all.deb to pool/main/k/kaffe/kaffe-dev_1.1.5-3_all.deb kaffe-doc_1.1.5-3_all.deb to pool/main/k/kaffe/kaffe-doc_1.1.5-3_all.deb kaffe-jthreads_1.1.5-3_i386.deb to pool/main/k/kaffe/kaffe-jthreads_1.1.5-3_i386.deb kaffe-pthreads-profile_1.1.5-3_i386.deb to pool/main/k/kaffe/kaffe-pthreads-profile_1.1.5-3_i386.deb kaffe-pthreads_1.1.5-3_i386.deb to pool/main/k/kaffe/kaffe-pthreads_1.1.5-3_i386.deb kaffe_1.1.5-3.diff.gz to pool/main/k/kaffe/kaffe_1.1.5-3.diff.gz kaffe_1.1.5-3.dsc to pool/main/k/kaffe/kaffe_1.1.5-3.dsc kaffe_1.1.5-3_all.deb to pool/main/k/kaffe/kaffe_1.1.5-3_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libgwenhywfar 1.11.0-2 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Apr 2005 19:55:03 +0200 Source: libgwenhywfar Binary: libgwenhywfar17 libgwenhywfar-doc libgwenhywfar17-dev libgwenhywfar-data Architecture: source all i386 Version: 1.11.0-2 Distribution: unstable Urgency: low Maintainer: Henning Glawe [EMAIL PROTECTED] Changed-By: Thomas Viehmann [EMAIL PROTECTED] Description: libgwenhywfar-data - OS abstraction layer libgwenhywfar-doc - OS abstraction layer (development files) libgwenhywfar17 - OS abstraction layer libgwenhywfar17-dev - OS abstraction layer (development files) Changes: libgwenhywfar (1.11.0-2) unstable; urgency=low . * Bump shlibs. Sorry, this is necessary for policy. Files: b2fea4ead2a7700233935bf1e8d6fe3e 846 libs optional libgwenhywfar_1.11.0-2.dsc d2c82fdfc3cd9f13bf951fc08848f653 28793 libs optional libgwenhywfar_1.11.0-2.diff.gz 76b3919a06ab9eb6d3a544131e8843bb 471378 doc optional libgwenhywfar-doc_1.11.0-2_all.deb 8e21fdfa9091068ec219ba7db7b2fbf2 96838 libs optional libgwenhywfar-data_1.11.0-2_all.deb cb3f0451e348d6a4a813e1dfd6f7c082 170852 libdevel optional libgwenhywfar17-dev_1.11.0-2_i386.deb c9fbc9983a4df5c87354534afb494ef6 395406 libs optional libgwenhywfar17_1.11.0-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) Comment: GnuPG key at http://thomas.viehmann.net/ iD8DBQFCZpjRriZpaaIa1PkRAhN9AJwO083Lu0/xazvzOmf6o1INqmwmvQCeK+5W psXOSHJpnfcXMCv3UK+XlD0= =5vSp -END PGP SIGNATURE- Accepted: libgwenhywfar-data_1.11.0-2_all.deb to pool/main/libg/libgwenhywfar/libgwenhywfar-data_1.11.0-2_all.deb libgwenhywfar-doc_1.11.0-2_all.deb to pool/main/libg/libgwenhywfar/libgwenhywfar-doc_1.11.0-2_all.deb libgwenhywfar17-dev_1.11.0-2_i386.deb to pool/main/libg/libgwenhywfar/libgwenhywfar17-dev_1.11.0-2_i386.deb libgwenhywfar17_1.11.0-2_i386.deb to pool/main/libg/libgwenhywfar/libgwenhywfar17_1.11.0-2_i386.deb libgwenhywfar_1.11.0-2.diff.gz to pool/main/libg/libgwenhywfar/libgwenhywfar_1.11.0-2.diff.gz libgwenhywfar_1.11.0-2.dsc to pool/main/libg/libgwenhywfar/libgwenhywfar_1.11.0-2.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libchipcard2 1.9.11.99+1.9.12beta-3 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Apr 2005 18:31:43 +0200 Source: libchipcard2 Binary: libchipcard2-dev libchipcard2-tools libchipcard2-data libchipcard2-0 Architecture: source i386 all Version: 1.9.11.99+1.9.12beta-3 Distribution: unstable Urgency: low Maintainer: Thomas Viehmann [EMAIL PROTECTED] Changed-By: Thomas Viehmann [EMAIL PROTECTED] Description: libchipcard2-0 - library for accessing smartcards libchipcard2-data - configuration files for libchipcard2-0 libchipcard2-dev - API for smartcard readers libchipcard2-tools - tools for libchipcard2 Closes: 303858 Changes: libchipcard2 (1.9.11.99+1.9.12beta-3) unstable; urgency=low . * Fix short description for libchipcard2-0. Thanks to Marcin Orlowski for pointing out the error. Closes: #303858. * Add note about automatic USB reader detection and Linux 2.4 to README.Debian. * Change priority to extra. Files: 925d13b153403b1222052e98f868be71 826 libs extra libchipcard2_1.9.11.99+1.9.12beta-3.dsc b457c2ebc080e0a6c9ad49cc68201db2 5591 libs extra libchipcard2_1.9.11.99+1.9.12beta-3.diff.gz 3797fa33eb9ac5844b20957480edcf03 39136 devel extra libchipcard2-dev_1.9.11.99+1.9.12beta-3_all.deb 13f4897b426f1f0fdc862a914079d2e6 43896 libs extra libchipcard2-data_1.9.11.99+1.9.12beta-3_all.deb b0ffbcbb8685f66ad5fb568d851382f4 184538 libs extra libchipcard2-0_1.9.11.99+1.9.12beta-3_i386.deb 0d4d7f945b3c7df9bce8caecb219dcf6 263548 misc extra libchipcard2-tools_1.9.11.99+1.9.12beta-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) Comment: GnuPG key at http://thomas.viehmann.net/ iD8DBQFCZobnriZpaaIa1PkRAuVLAKCcuBbbJKvlMihg4C3A87QY4YkqBACg4iRi hwOh55VnvtOeJmjeZuI+pkQ= =ysD6 -END PGP SIGNATURE- Accepted: libchipcard2-0_1.9.11.99+1.9.12beta-3_i386.deb to pool/main/libc/libchipcard2/libchipcard2-0_1.9.11.99+1.9.12beta-3_i386.deb libchipcard2-data_1.9.11.99+1.9.12beta-3_all.deb to pool/main/libc/libchipcard2/libchipcard2-data_1.9.11.99+1.9.12beta-3_all.deb libchipcard2-dev_1.9.11.99+1.9.12beta-3_all.deb to pool/main/libc/libchipcard2/libchipcard2-dev_1.9.11.99+1.9.12beta-3_all.deb libchipcard2-tools_1.9.11.99+1.9.12beta-3_i386.deb to pool/main/libc/libchipcard2/libchipcard2-tools_1.9.11.99+1.9.12beta-3_i386.deb libchipcard2_1.9.11.99+1.9.12beta-3.diff.gz to pool/main/libc/libchipcard2/libchipcard2_1.9.11.99+1.9.12beta-3.diff.gz libchipcard2_1.9.11.99+1.9.12beta-3.dsc to pool/main/libc/libchipcard2/libchipcard2_1.9.11.99+1.9.12beta-3.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted pptview 8.0-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Apr 2005 11:16:03 -0700 Source: pptview Binary: pptview Architecture: source i386 Version: 8.0-2 Distribution: unstable Urgency: low Maintainer: Shaun Jackman [EMAIL PROTECTED] Changed-By: Shaun Jackman [EMAIL PROTECTED] Description: pptview- view PowerPoint slide shows Closes: 305202 Changes: pptview (8.0-2) unstable; urgency=low . * Add a menu file. Closes: #305202. Files: 6fbb2646d3b175232f2ebf2ebf4b7b42 561 non-free/text optional pptview_8.0-2.dsc 37967d96eb6264dc8b289de31273dfe4 6500 non-free/text optional pptview_8.0-2.diff.gz a809a33b28fea534b7eb81419ad64f74 1793942 non-free/text optional pptview_8.0-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFCZp8zvFdYF1IwUUoRAj26AJ9fSQ6HVfPZGbBPyPNxzV31caYVKgCcD4TX /D3kkNjAiB3zau8gGJnmj3c= =GRBH -END PGP SIGNATURE- Accepted: pptview_8.0-2.diff.gz to pool/non-free/p/pptview/pptview_8.0-2.diff.gz pptview_8.0-2.dsc to pool/non-free/p/pptview/pptview_8.0-2.dsc pptview_8.0-2_i386.deb to pool/non-free/p/pptview/pptview_8.0-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted foomatic-db-hpijs 1.5-20050420-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Apr 2005 14:32:03 -0500 Source: foomatic-db-hpijs Binary: foomatic-db-hpijs Architecture: source all Version: 1.5-20050420-1 Distribution: unstable Urgency: low Maintainer: Chris Lawrence [EMAIL PROTECTED] Changed-By: Chris Lawrence [EMAIL PROTECTED] Description: foomatic-db-hpijs - linuxprinting.org printer support - database for HPIJS driver Closes: 305517 Changes: foomatic-db-hpijs (1.5-20050420-1) unstable; urgency=low . * New upstream release. * Adds support for FastDraft Grayscale option for various HP printers. (Closes: #305517) Files: 5ee095dc67bc9cce4f660397a4f6d7be 627 text optional foomatic-db-hpijs_1.5-20050420-1.dsc 4d69ac770c95df13693915b40ab53d7d 87220 text optional foomatic-db-hpijs_1.5-20050420.orig.tar.gz 458700d0c517c12bff792ef6d2f64515 25761 text optional foomatic-db-hpijs_1.5-20050420-1.diff.gz 853af918c28ac748e5805630898765f5 225766 text optional foomatic-db-hpijs_1.5-20050420-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCZq7D2wQKE6PXubwRApXMAJ4w0uEyGrQx++mEb2ddCJfrPPVE7QCdHw7e eRs1Qz/r3dXpU9GWW75zrw8= =YLeI -END PGP SIGNATURE- Accepted: foomatic-db-hpijs_1.5-20050420-1.diff.gz to pool/main/f/foomatic-db-hpijs/foomatic-db-hpijs_1.5-20050420-1.diff.gz foomatic-db-hpijs_1.5-20050420-1.dsc to pool/main/f/foomatic-db-hpijs/foomatic-db-hpijs_1.5-20050420-1.dsc foomatic-db-hpijs_1.5-20050420-1_all.deb to pool/main/f/foomatic-db-hpijs/foomatic-db-hpijs_1.5-20050420-1_all.deb foomatic-db-hpijs_1.5-20050420.orig.tar.gz to pool/main/f/foomatic-db-hpijs/foomatic-db-hpijs_1.5-20050420.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted foomatic-db 20050420-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Apr 2005 14:30:29 -0500 Source: foomatic-db Binary: foomatic-db Architecture: source all Version: 20050420-1 Distribution: unstable Urgency: low Maintainer: Chris Lawrence [EMAIL PROTECTED] Changed-By: Chris Lawrence [EMAIL PROTECTED] Description: foomatic-db - linuxprinting.org printer support - database Changes: foomatic-db (20050420-1) unstable; urgency=low . * New upstream release. Files: 5f9ffa0c12af2d88e5d4009247af872d 591 text optional foomatic-db_20050420-1.dsc ae15319e6044222e06629e69425f9d01 533351 text optional foomatic-db_20050420.orig.tar.gz acddc516333cd535ecf0ad11a345d70c 4497 text optional foomatic-db_20050420-1.diff.gz f0d988d5c9ace4cca9b9896b900db488 538090 text optional foomatic-db_20050420-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCZq7b2wQKE6PXubwRAncoAJ4tE0JlQ88T8WD852iYn2swY7YZuACfd4iY v5JVkzMpbKhUDf4MBiiHqCc= =Mpts -END PGP SIGNATURE- Accepted: foomatic-db_20050420-1.diff.gz to pool/main/f/foomatic-db/foomatic-db_20050420-1.diff.gz foomatic-db_20050420-1.dsc to pool/main/f/foomatic-db/foomatic-db_20050420-1.dsc foomatic-db_20050420-1_all.deb to pool/main/f/foomatic-db/foomatic-db_20050420-1_all.deb foomatic-db_20050420.orig.tar.gz to pool/main/f/foomatic-db/foomatic-db_20050420.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted stunnel4 2:4.090-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Apr 2005 21:07:50 +0200 Source: stunnel4 Binary: stunnel4 Architecture: source i386 Version: 2:4.090-1 Distribution: unstable Urgency: low Maintainer: Julien Lemoine [EMAIL PROTECTED] Changed-By: Julien Lemoine [EMAIL PROTECTED] Description: stunnel4 - Universal SSL tunnel for network daemons Closes: 305259 Changes: stunnel4 (2:4.090-1) unstable; urgency=low . * New upstream release * include better stunnel3 compability script from upstream, options like -cd can now be use instead of -c -d ... (closes: #305259) * Added depends on perl-modules to allow use of stunnel3 compatibilty script Files: 6ae72e8eff16d6582a257cd6c9b2d810 606 net optional stunnel4_4.090-1.dsc 7a9c053130e914d24b146133bf2c99b6 486920 net optional stunnel4_4.090.orig.tar.gz 304e6101edc89f0ef52cd85d958bd0dd 17067 net optional stunnel4_4.090-1.diff.gz 71bed409f55bfef5ac6b457e4db999e6 87340 net optional stunnel4_4.090-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCZqv+c29c8N2YKnURAqwTAJ0cFkwNf350tgvZdPw6fmNVnp/tVgCglzPU ebeG3FaCxXYuu+J/Fd+0DOM= =suoa -END PGP SIGNATURE- Accepted: stunnel4_4.090-1.diff.gz to pool/main/s/stunnel4/stunnel4_4.090-1.diff.gz stunnel4_4.090-1.dsc to pool/main/s/stunnel4/stunnel4_4.090-1.dsc stunnel4_4.090-1_i386.deb to pool/main/s/stunnel4/stunnel4_4.090-1_i386.deb stunnel4_4.090.orig.tar.gz to pool/main/s/stunnel4/stunnel4_4.090.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libplexus-utils 1.0alpha1-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 19 Aug 2005 00:26:30 +0100 Source: libplexus-utils Binary: libplexus-utils Architecture: source all Version: 1.0alpha1-1 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers [EMAIL PROTECTED] Changed-By: Trygve Laugstøl [EMAIL PROTECTED] Description: libplexus-utils - Common utilities used by the Plexus Container and components Changes: libplexus-utils (1.0alpha1-1) unstable; urgency=low . * Initial Release. Files: be8b24e8d34dd255992e0dbc849ebdc8 750 libs optional libplexus-utils_1.0alpha1-1.dsc 94f33324f32e348f5e2533fdb480664e 143435 libs optional libplexus-utils_1.0alpha1.orig.tar.gz f837e40da92852ae0dbd29ebaea68767 3014 libs optional libplexus-utils_1.0alpha1-1.diff.gz bac43f46dada0c2b12fca538c7355f93 109930 libs optional libplexus-utils_1.0alpha1-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCZXqo4vzFZu62tMIRAlRnAJ9zI9WaJSXfkjjXTQmhAXUyVYvnBgCgsLDQ lU/xf5xm6aTfB/h5E0WPygI= =PD+E -END PGP SIGNATURE- Accepted: libplexus-utils_1.0alpha1-1.diff.gz to pool/main/libp/libplexus-utils/libplexus-utils_1.0alpha1-1.diff.gz libplexus-utils_1.0alpha1-1.dsc to pool/main/libp/libplexus-utils/libplexus-utils_1.0alpha1-1.dsc libplexus-utils_1.0alpha1-1_all.deb to pool/main/libp/libplexus-utils/libplexus-utils_1.0alpha1-1_all.deb libplexus-utils_1.0alpha1.orig.tar.gz to pool/main/libp/libplexus-utils/libplexus-utils_1.0alpha1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cldump 0.8-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 19 Apr 2005 12:08:00 +0200 Source: cldump Binary: cldump Architecture: source i386 Version: 0.8-1 Distribution: unstable Urgency: low Maintainer: Julien BLACHE [EMAIL PROTECTED] Changed-By: Julien BLACHE [EMAIL PROTECTED] Description: cldump - Clarion database files extractor Closes: 305326 Changes: cldump (0.8-1) unstable; urgency=low . * Initial Release (closes: #305326). Files: e4937a67124cf796c019cecc9f85bba7 551 misc optional cldump_0.8-1.dsc c4a5b1095df698741762367772ae9e97 19652 misc optional cldump_0.8.orig.tar.gz 388790d1f93b78bcc82cd51629670999 1693 misc optional cldump_0.8-1.diff.gz 7abfb91236d325cf055145384a00d546 16328 misc optional cldump_0.8-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCZNkDzWFP1/XWUWkRAuC0AKCvto1/1u59bdweQWYx9q1TAauxrgCdHXuN zNRuiqDnYR/r7+7zn78vnMA= =fo8s -END PGP SIGNATURE- Accepted: cldump_0.8-1.diff.gz to pool/main/c/cldump/cldump_0.8-1.diff.gz cldump_0.8-1.dsc to pool/main/c/cldump/cldump_0.8-1.dsc cldump_0.8-1_i386.deb to pool/main/c/cldump/cldump_0.8-1_i386.deb cldump_0.8.orig.tar.gz to pool/main/c/cldump/cldump_0.8.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libmail-verp-perl 0.04-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 19 Apr 2005 11:50:08 +0200 Source: libmail-verp-perl Binary: libmail-verp-perl Architecture: source all Version: 0.04-1 Distribution: unstable Urgency: low Maintainer: Julien BLACHE [EMAIL PROTECTED] Changed-By: Julien BLACHE [EMAIL PROTECTED] Description: libmail-verp-perl - Variable Envelope Return Paths (VERP) address encoder/decoder Closes: 305324 Changes: libmail-verp-perl (0.04-1) unstable; urgency=low . * Initial Release (closes: #305324). Files: 98d80d67644842094ef69fdc6f15819d 621 perl optional libmail-verp-perl_0.04-1.dsc d7ffeaa400902242c48927079275de83 11724 perl optional libmail-verp-perl_0.04.orig.tar.gz 45feaac3b95679400d20d924d1841a36 1549 perl optional libmail-verp-perl_0.04-1.diff.gz 30bfbaccf8cf5d05f2bb230ba3b80083 7142 perl optional libmail-verp-perl_0.04-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCZNRxzWFP1/XWUWkRAnBZAJ0TN6xVpmsidE6aG01zeJLoxZPXFgCeJn6H MLkrVbV6SIPZVR7NVEM4aaA= =WF4O -END PGP SIGNATURE- Accepted: libmail-verp-perl_0.04-1.diff.gz to pool/main/libm/libmail-verp-perl/libmail-verp-perl_0.04-1.diff.gz libmail-verp-perl_0.04-1.dsc to pool/main/libm/libmail-verp-perl/libmail-verp-perl_0.04-1.dsc libmail-verp-perl_0.04-1_all.deb to pool/main/libm/libmail-verp-perl/libmail-verp-perl_0.04-1_all.deb libmail-verp-perl_0.04.orig.tar.gz to pool/main/libm/libmail-verp-perl/libmail-verp-perl_0.04.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted darcs-buildpackage 0.5.0 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 19 Apr 2005 18:55:10 -0500 Source: darcs-buildpackage Binary: darcs-buildpackage Architecture: source i386 Version: 0.5.0 Distribution: unstable Urgency: low Maintainer: John Goerzen [EMAIL PROTECTED] Changed-By: John Goerzen [EMAIL PROTECTED] Description: darcs-buildpackage - Suite to help with Debian packages in Darcs archives Closes: 305420 Changes: darcs-buildpackage (0.5.0) unstable; urgency=low . * Initial release. Closes: #305420. Files: 5199a5e2cf5422669e086f01950272ad 673 devel optional darcs-buildpackage_0.5.0.dsc 36b9cbf60c34e2221d13ffb6cf393af5 38893 devel optional darcs-buildpackage_0.5.0.tar.gz 2494b03a09c5b2532052507018097448 1423840 devel optional darcs-buildpackage_0.5.0_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCZcJU7B2mSKdID5ERAowLAJ4oUVb3t5M45d53G1lKsujvDYZvJgCcDKLW leIiguNvDTSaODLWcnWU1tw= =BF+y -END PGP SIGNATURE- Accepted: darcs-buildpackage_0.5.0.dsc to pool/main/d/darcs-buildpackage/darcs-buildpackage_0.5.0.dsc darcs-buildpackage_0.5.0.tar.gz to pool/main/d/darcs-buildpackage/darcs-buildpackage_0.5.0.tar.gz darcs-buildpackage_0.5.0_i386.deb to pool/main/d/darcs-buildpackage/darcs-buildpackage_0.5.0_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted webauth 3.2.6-1 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Format: 1.7 Date: Mon, 18 Apr 2005 23:06:23 -0700 Source: webauth Binary: webauth-utils webauth-tests libwebauth-perl libwebauth1 libwebauth1-dev libwebkdc-perl webauth-weblogin libapache2-webauth libapache2-webkdc Architecture: source all i386 Version: 3.2.6-1 Distribution: unstable Urgency: low Maintainer: Russ Allbery [EMAIL PROTECTED] Changed-By: Russ Allbery [EMAIL PROTECTED] Description: libapache2-webauth - Apache 2 modules for WebAuth authentication libapache2-webkdc - Apache 2 modules for a WebAuth authentication KDC libwebauth-perl - Perl library for WebAuth authentication libwebauth1 - Shared libraries for WebAuth authentication libwebauth1-dev - Development files for WebAuth authentication libwebkdc-perl - Perl library for WebAuth authentication webauth-tests - Tests for the WebAuth authentication modules webauth-utils - Command-line utilities for WebAuth authentication webauth-weblogin - Central login server for WebAuth authentication Closes: 304728 Changes: webauth (3.2.6-1) unstable; urgency=low . * Uploaded to Debian. (Closes: #304728) * New upstream release. - Renamed the WebAuth3 Perl bindings to WebAuth. - Renamed the libwebauth3-perl package to libwebauth-perl accordingly. * Add dependency on libwebauth-perl to webauth-weblogin. libwebkdc-perl will also pull it in, but this is more completely correct. * Add watch file. Files: 8c925a946f156764677ff0cd3c347ffe 1084 web optional webauth_3.2.6-1.dsc c4e687445db8dc8fade9ea945d7c2b0a 465671 web optional webauth_3.2.6.orig.tar.gz fd2061ea7f452784e64b9a3392fffdeb 11922 web optional webauth_3.2.6-1.diff.gz becc53e9662ebec46f0bced51e9a4a53 126324 web optional libapache2-webauth_3.2.6-1_i386.deb 2698b7ae57358d2c8239e44494e1ae8d 6 web optional libapache2-webkdc_3.2.6-1_i386.deb 9cd59c32efa27180df34bcaf5fdb0867 43258 perl optional libwebauth-perl_3.2.6-1_i386.deb 2ed3004e5e014cb17165d197b185a551 28528 libs optional libwebauth1_3.2.6-1_i386.deb 358858578ff71455bc00546c19814128 36342 libdevel extra libwebauth1-dev_3.2.6-1_i386.deb 4586adbc833b6bcee814f98e5dab78fc 16974 web optional webauth-utils_3.2.6-1_i386.deb 982edfd4848d16b56c73e599b2602ed1 30318 perl optional libwebkdc-perl_3.2.6-1_all.deb 3eaff7f1b14e3bb9cb39379441788672 17388 web optional webauth-tests_3.2.6-1_all.deb 415ef0183a3ba269159aab32dc71543e 39156 web optional webauth-weblogin_3.2.6-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iQEVAwUBQmX7F7f2jhx5fmQdAQFTUgf+MoumkDaRpo1/UA6CDFumH4XlsTiCFw2g ST52IuwzNVY3NDY+O3h8vKNTMN3txwjpNPZ1cXU8LhtcD8N4Mo9dT3tkEm0yQNCZ wgGn73LRFAG6T006l29Mt5mliTrW4RnivaqXHin3wwNMb/N0HyhgIbgunc2ZWV/Q rbiAv3N6klufOe325JG1KMdgrVb1P3iU462t8xOtlxhQH6p4B3YXRV94FKeqQBWn uJIIaJdPYhbVSdT5w1z8+IK/EMBY7DxNAmnWSjiw9U3+cIzn0Cejd0T40ZWyTxT1 U9d2SB0GndM73kzbqj5G4b/SFMpzxbXhXz2K/JqsqU+gMMPFN0EvwA== =dJii -END PGP SIGNATURE- Accepted: libapache2-webauth_3.2.6-1_i386.deb to pool/main/w/webauth/libapache2-webauth_3.2.6-1_i386.deb libapache2-webkdc_3.2.6-1_i386.deb to pool/main/w/webauth/libapache2-webkdc_3.2.6-1_i386.deb libwebauth-perl_3.2.6-1_i386.deb to pool/main/w/webauth/libwebauth-perl_3.2.6-1_i386.deb libwebauth1-dev_3.2.6-1_i386.deb to pool/main/w/webauth/libwebauth1-dev_3.2.6-1_i386.deb libwebauth1_3.2.6-1_i386.deb to pool/main/w/webauth/libwebauth1_3.2.6-1_i386.deb libwebkdc-perl_3.2.6-1_all.deb to pool/main/w/webauth/libwebkdc-perl_3.2.6-1_all.deb webauth-tests_3.2.6-1_all.deb to pool/main/w/webauth/webauth-tests_3.2.6-1_all.deb webauth-utils_3.2.6-1_i386.deb to pool/main/w/webauth/webauth-utils_3.2.6-1_i386.deb webauth-weblogin_3.2.6-1_all.deb to pool/main/w/webauth/webauth-weblogin_3.2.6-1_all.deb webauth_3.2.6-1.diff.gz to pool/main/w/webauth/webauth_3.2.6-1.diff.gz webauth_3.2.6-1.dsc to pool/main/w/webauth/webauth_3.2.6-1.dsc webauth_3.2.6.orig.tar.gz to pool/main/w/webauth/webauth_3.2.6.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mol-modules-2.6.11 1:0.9.70+2.6.11+1 (powerpc source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Apr 2005 01:23:33 +0200 Source: mol-modules-2.6.11 Binary: mol-modules-2.6.11-powerpc-smp mol-modules-2.6.11-powerpc Architecture: source powerpc Version: 1:0.9.70+2.6.11+1 Distribution: unstable Urgency: low Maintainer: Jens Schmalzing [EMAIL PROTECTED] Changed-By: Jens Schmalzing [EMAIL PROTECTED] Description: mol-modules-2.6.11-powerpc - The Mac-on-Linux emulator - kernel modules for 2.6.11-powerpc mol-modules-2.6.11-powerpc-smp - The Mac-on-Linux emulator - kernel modules for 2.6.11-powerpc-smp Changes: mol-modules-2.6.11 (1:0.9.70+2.6.11+1) unstable; urgency=low . * Rebuilt the package against the new kernel-build packages. Files: 32970c85ffebd275180cfcd61f345817 698 otherosfs optional mol-modules-2.6.11_0.9.70+2.6.11+1.dsc 04d026f2aa9f36147e5165d8b76c3fea 4246 otherosfs optional mol-modules-2.6.11_0.9.70+2.6.11+1.tar.gz 9ad1490fe3eba8f9344589bf2ad3b7c6 38508 otherosfs optional mol-modules-2.6.11-powerpc_0.9.70+2.6.11+1_powerpc.deb 8b60c00555c17a0fd9b96abf43f04c30 39524 otherosfs optional mol-modules-2.6.11-powerpc-smp_0.9.70+2.6.11+1_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCZucaqYZgyBJFIH4RArTrAJ9nPv4jQ6LLVQIHrWnfeEckS6k8iACaAlSF sqGqaK8/WUyAzfX/Gz+aBUk= =tXqi -END PGP SIGNATURE- Accepted: mol-modules-2.6.11-powerpc-smp_0.9.70+2.6.11+1_powerpc.deb to pool/main/m/mol-modules-2.6.11/mol-modules-2.6.11-powerpc-smp_0.9.70+2.6.11+1_powerpc.deb mol-modules-2.6.11-powerpc_0.9.70+2.6.11+1_powerpc.deb to pool/main/m/mol-modules-2.6.11/mol-modules-2.6.11-powerpc_0.9.70+2.6.11+1_powerpc.deb mol-modules-2.6.11_0.9.70+2.6.11+1.dsc to pool/main/m/mol-modules-2.6.11/mol-modules-2.6.11_0.9.70+2.6.11+1.dsc mol-modules-2.6.11_0.9.70+2.6.11+1.tar.gz to pool/main/m/mol-modules-2.6.11/mol-modules-2.6.11_0.9.70+2.6.11+1.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libaqbanking 1.0.8-2 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Apr 2005 20:55:35 +0200 Source: libaqbanking Binary: libaqbanking-data libaqbanking0-dev libaqbanking-plugins-libgwenhywfar17 libaqbanking-doc libaqbanking0 Architecture: source i386 all Version: 1.0.8-2 Distribution: unstable Urgency: low Maintainer: Micha Lenk [EMAIL PROTECTED] Changed-By: Thomas Viehmann [EMAIL PROTECTED] Description: libaqbanking-data - configuration files for libaqbanking libaqbanking-doc - library for online banking applications libaqbanking-plugins-libgwenhywfar17 - library for online banking applications plugins to libgwenhywfar libaqbanking0 - library for online banking applications libaqbanking0-dev - library for online banking applications Closes: 304914 Changes: libaqbanking (1.0.8-2) unstable; urgency=low . * Bump version in build-dependency on libgwenhywfar. Closes: #304914 Files: 6bfe804d19e849fef866d7fedd68f160 857 libs optional libaqbanking_1.0.8-2.dsc 8750656690d0c683a68dc3cc9f14bc68 3135 libs optional libaqbanking_1.0.8-2.diff.gz b0e13af5a3ea86141a04df35e004e73d 64136 libdevel optional libaqbanking0-dev_1.0.8-2_all.deb c02dac84158499a7a3ff1d5c8ecb3720 218892 doc optional libaqbanking-doc_1.0.8-2_all.deb 047f375dd5be9abbff1e32fd323623ae 28734 libs optional libaqbanking-data_1.0.8-2_all.deb 060e8c1b536e022cebac9dcbfb276d7a 172076 libs optional libaqbanking0_1.0.8-2_i386.deb 9626b6a6bf74c87ff16d41572e4d4a92 46968 libs optional libaqbanking-plugins-libgwenhywfar17_1.0.8-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) Comment: GnuPG key at http://thomas.viehmann.net/ iD8DBQFCZqsZriZpaaIa1PkRArKwAKCDJY61gEQ4+MVrdkx7nNuiCmpCHQCfVsXt HLsUs4PId2Yme9tL1J9ouUM= =z7El -END PGP SIGNATURE- Accepted: libaqbanking-data_1.0.8-2_all.deb to pool/main/liba/libaqbanking/libaqbanking-data_1.0.8-2_all.deb libaqbanking-doc_1.0.8-2_all.deb to pool/main/liba/libaqbanking/libaqbanking-doc_1.0.8-2_all.deb libaqbanking-plugins-libgwenhywfar17_1.0.8-2_i386.deb to pool/main/liba/libaqbanking/libaqbanking-plugins-libgwenhywfar17_1.0.8-2_i386.deb libaqbanking0-dev_1.0.8-2_all.deb to pool/main/liba/libaqbanking/libaqbanking0-dev_1.0.8-2_all.deb libaqbanking0_1.0.8-2_i386.deb to pool/main/liba/libaqbanking/libaqbanking0_1.0.8-2_i386.deb libaqbanking_1.0.8-2.diff.gz to pool/main/liba/libaqbanking/libaqbanking_1.0.8-2.diff.gz libaqbanking_1.0.8-2.dsc to pool/main/liba/libaqbanking/libaqbanking_1.0.8-2.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libtemplate-plugin-yaml-perl 1.22-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Apr 2005 15:13:35 +0100 Source: libtemplate-plugin-yaml-perl Binary: libtemplate-plugin-yaml-perl Architecture: source all Version: 1.22-1 Distribution: unstable Urgency: low Maintainer: Stephen Quinney [EMAIL PROTECTED] Changed-By: Stephen Quinney [EMAIL PROTECTED] Description: libtemplate-plugin-yaml-perl - simple Template Toolkit Plugin Interface to the YAML module Closes: 305421 Changes: libtemplate-plugin-yaml-perl (1.22-1) unstable; urgency=low . * Initial release, closes: #305421. Files: 1aada4f1e0e4be5fb64ba9a4dd35b785 690 perl optional libtemplate-plugin-yaml-perl_1.22-1.dsc 9822ac328401c77ee58d49fa04321c45 2552 perl optional libtemplate-plugin-yaml-perl_1.22.orig.tar.gz 8ff37f1a835372d8d7c4b18638823431 1795 perl optional libtemplate-plugin-yaml-perl_1.22-1.diff.gz ff64399df6320ad92bc7df283f44484f 6534 perl optional libtemplate-plugin-yaml-perl_1.22-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCZm+JITGblEwaW+URArONAKCiFRjizwTK+EgJVJP/iiv/HWAj/wCglhae bdlp0orKUXzeuy/9SXNXj5o= =8x/k -END PGP SIGNATURE- Accepted: libtemplate-plugin-yaml-perl_1.22-1.diff.gz to pool/main/libt/libtemplate-plugin-yaml-perl/libtemplate-plugin-yaml-perl_1.22-1.diff.gz libtemplate-plugin-yaml-perl_1.22-1.dsc to pool/main/libt/libtemplate-plugin-yaml-perl/libtemplate-plugin-yaml-perl_1.22-1.dsc libtemplate-plugin-yaml-perl_1.22-1_all.deb to pool/main/libt/libtemplate-plugin-yaml-perl/libtemplate-plugin-yaml-perl_1.22-1_all.deb libtemplate-plugin-yaml-perl_1.22.orig.tar.gz to pool/main/libt/libtemplate-plugin-yaml-perl/libtemplate-plugin-yaml-perl_1.22.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted centericq 4.20.0-3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Apr 2005 21:34:12 +0200 Source: centericq Binary: centericq-common centericq-utf8 centericq-fribidi centericq Architecture: source i386 Version: 4.20.0-3 Distribution: unstable Urgency: low Maintainer: Julien LEMOINE [EMAIL PROTECTED] Changed-By: Julien Lemoine [EMAIL PROTECTED] Description: centericq - A text-mode multi-protocol instant messenger client centericq-common - A text-mode multi-protocol instant messenger client (data files) centericq-fribidi - A text-mode multi-protocol instant messenger client (Hebrew) centericq-utf8 - A text-mode multi-protocol instant messenger client Closes: 303937 Changes: centericq (4.20.0-3) unstable; urgency=low . * Applied patch from Andreas Jochens [EMAIL PROTECTED] to fix amd64 buid problems (g++ 4.0 compilation errors) (Closes: #303937) Files: 37fd1ada640ac2c99dcb9d97c67c25f2 863 net optional centericq_4.20.0-3.dsc 012695196fc9e1d86b6a22b673ea3139 119107 net optional centericq_4.20.0-3.diff.gz ce15ef69fc055bd809af8ab8c56d7ecb 335582 net optional centericq-common_4.20.0-3_i386.deb cb09026e79e47bedecef9fde71a75799 1349808 net optional centericq_4.20.0-3_i386.deb f2e3dfeedb89ba0a6cfbac84b26a1f48 1349866 net optional centericq-utf8_4.20.0-3_i386.deb c75a95b4246f225de5eb33a8765ffe36 1350582 net optional centericq-fribidi_4.20.0-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCZrUvc29c8N2YKnURAmJLAKCURecrDo6i9WxdRZ6tEZked0Iz8wCfWa/K zHzWQ8IYIlKwmpB8fDvjK7I= =sapA -END PGP SIGNATURE- Accepted: centericq-common_4.20.0-3_i386.deb to pool/main/c/centericq/centericq-common_4.20.0-3_i386.deb centericq-fribidi_4.20.0-3_i386.deb to pool/main/c/centericq/centericq-fribidi_4.20.0-3_i386.deb centericq-utf8_4.20.0-3_i386.deb to pool/main/c/centericq/centericq-utf8_4.20.0-3_i386.deb centericq_4.20.0-3.diff.gz to pool/main/c/centericq/centericq_4.20.0-3.diff.gz centericq_4.20.0-3.dsc to pool/main/c/centericq/centericq_4.20.0-3.dsc centericq_4.20.0-3_i386.deb to pool/main/c/centericq/centericq_4.20.0-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cron-apt 0.3.0 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Apr 2005 22:00:31 +0200 Source: cron-apt Binary: cron-apt Architecture: source all Version: 0.3.0 Distribution: unstable Urgency: low Maintainer: Ola Lundqvist [EMAIL PROTECTED] Changed-By: Ola Lundqvist [EMAIL PROTECTED] Description: cron-apt - automatic update of packages using apt-get Closes: 298983 305474 Changes: cron-apt (0.3.0) unstable; urgency=low . * Applied patch from Marc Haber [EMAIL PROTECTED] that make it possible to create a file that make cron-apt silently exit. Useful for dial-up connections, closes: #305474. * Updated manpage with minor correction, closes: #298983. Files: b355654b7efd6e75ad7f28b0020fa1d5 513 admin optional cron-apt_0.3.0.dsc 12166139ac7f773bd49807536e197842 30399 admin optional cron-apt_0.3.0.tar.gz dfa49d0139ce5dabfba46b1beda8ac94 19286 admin optional cron-apt_0.3.0_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCZrfuGKGxzw/lPdkRAst+AJ9dgmXYwZZgehJ8BtrcNrkxhjDCVwCdEEUH g8As38xJQxF4FfzP2NqzsHk= =ecs6 -END PGP SIGNATURE- Accepted: cron-apt_0.3.0.dsc to pool/main/c/cron-apt/cron-apt_0.3.0.dsc cron-apt_0.3.0.tar.gz to pool/main/c/cron-apt/cron-apt_0.3.0.tar.gz cron-apt_0.3.0_all.deb to pool/main/c/cron-apt/cron-apt_0.3.0_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted vserver-debiantools 0.2.1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Apr 2005 22:25:54 +0200 Source: vserver-debiantools Binary: vserver-debiantools Architecture: source all Version: 0.2.1 Distribution: unstable Urgency: low Maintainer: Ola Lundqvist [EMAIL PROTECTED] Changed-By: Ola Lundqvist [EMAIL PROTECTED] Description: vserver-debiantools - Tools to manage debian virtual servers Closes: 264912 Changes: vserver-debiantools (0.2.1) unstable; urgency=low . * Fixed minor issue with package cache system, closes: #264912. Files: d21afad560a2346ba39535ae1a10ae2e 530 utils optional vserver-debiantools_0.2.1.dsc 7b07f3ff488dacf7134b92b62d8c3992 27904 utils optional vserver-debiantools_0.2.1.tar.gz 64dc8f817f6a3d0a6332c2be250e09a0 28172 utils optional vserver-debiantools_0.2.1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCZru7GKGxzw/lPdkRAuETAKCLEvrMiMEHS9w9yErlziEN0czp2ACgjY9/ 80CrDQsEt751z69698ONXbs= =unBC -END PGP SIGNATURE- Accepted: vserver-debiantools_0.2.1.dsc to pool/main/v/vserver-debiantools/vserver-debiantools_0.2.1.dsc vserver-debiantools_0.2.1.tar.gz to pool/main/v/vserver-debiantools/vserver-debiantools_0.2.1.tar.gz vserver-debiantools_0.2.1_all.deb to pool/main/v/vserver-debiantools/vserver-debiantools_0.2.1_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted prolog-el 1.3-3 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Apr 2005 22:50:28 +0200 Source: prolog-el Binary: prolog-el Architecture: source all Version: 1.3-3 Distribution: unstable Urgency: low Maintainer: Jorgen Schaefer [EMAIL PROTECTED] Changed-By: Jorgen Schaefer [EMAIL PROTECTED] Description: prolog-el - Emacs major mode for editing Prolog code Closes: 305546 Changes: prolog-el (1.3-3) unstable; urgency=low . * Added Build-Depends on dpatch (Closes: #305546). Files: 9aae01f5a804b8bd24c1a05c96797cdf 506 interpreters optional prolog-el_1.3-3.dsc 2b4d9dbe1ceac2cc9af667b88c6a9526 34242 interpreters optional prolog-el_1.3-3.tar.gz a19780aaf331294b151dbcc4aa8261e6 34476 interpreters optional prolog-el_1.3-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCZsDGZ+updwKK9jwRAly/AJ48b2CnZnq4mbRO8d6VtSJNAbTKQACeJCis CTbqT3451SSKzqNz3m+WEVU= =6Mmv -END PGP SIGNATURE- Accepted: prolog-el_1.3-3.dsc to pool/main/p/prolog-el/prolog-el_1.3-3.dsc prolog-el_1.3-3.tar.gz to pool/main/p/prolog-el/prolog-el_1.3-3.tar.gz prolog-el_1.3-3_all.deb to pool/main/p/prolog-el/prolog-el_1.3-3_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libpam-ccreds 1-1 (powerpc source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 7 Apr 2005 23:08:51 +0200 Source: libpam-ccreds Binary: libpam-ccreds Architecture: source powerpc Version: 1-1 Distribution: unstable Urgency: low Maintainer: Guido Guenther [EMAIL PROTECTED] Changed-By: Guido Guenther [EMAIL PROTECTED] Description: libpam-ccreds - Pam module to cache authentication credentials Closes: 303240 Changes: libpam-ccreds (1-1) unstable; urgency=low . * Initial release (Closes: #303240) * patch to use gcrypt11 instead of openssl Files: 80cd6850518cb38b274610ca6d2d20ca 655 net extra libpam-ccreds_1-1.dsc b076ff354f92e4a9d2d0fd549a2fcef7 94486 net extra libpam-ccreds_1.orig.tar.gz 96575a0426a3d0c548e11f027122ad78 62587 net extra libpam-ccreds_1-1.diff.gz ce8799c78a0e5869fcf8dde97fe0aa19 16214 net extra libpam-ccreds_1-1_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCZrrHn88szT8+ZCYRAryGAJ4+lJvTy5k+9vWE9QtKyDwdYRl2YgCfQwed Jd6XTldJova1RKNF6tjU2NI= =aUle -END PGP SIGNATURE- Accepted: libpam-ccreds_1-1.diff.gz to pool/main/libp/libpam-ccreds/libpam-ccreds_1-1.diff.gz libpam-ccreds_1-1.dsc to pool/main/libp/libpam-ccreds/libpam-ccreds_1-1.dsc libpam-ccreds_1-1_powerpc.deb to pool/main/libp/libpam-ccreds/libpam-ccreds_1-1_powerpc.deb libpam-ccreds_1.orig.tar.gz to pool/main/libp/libpam-ccreds/libpam-ccreds_1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted redland 1.0.0-3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Apr 2005 22:09:57 +0100 Source: redland Binary: librdf0-dev redland-utils librdf0 Architecture: source i386 Version: 1.0.0-3 Distribution: unstable Urgency: low Maintainer: Dave Beckett [EMAIL PROTECTED] Changed-By: Dave Beckett [EMAIL PROTECTED] Description: librdf0- Redland Resource Description Framework (RDF) library librdf0-dev - Redland RDF library development libraries and headers redland-utils - Redland Resource Description Framwork (RDF) Utility programs Changes: redland (1.0.0-3) unstable; urgency=low . * Added the redland-utils package for the rdfproc utility separate from the development package librdf0-dev Files: 9208a93cc1a9653afb04ad096cdc6688 812 devel optional redland_1.0.0-3.dsc e449a3fb88aca1930a76c340253ee884 8692 devel optional redland_1.0.0-3.diff.gz d91c8c9eae931cda0c444e1e5aba0414 355172 libdevel optional librdf0-dev_1.0.0-3_i386.deb b843a47381a156e2148031dcff0cdc2d 163730 libs optional librdf0_1.0.0-3_i386.deb cbddaecbfd2fd7c255a4ca95226bbc2e 128764 text optional redland-utils_1.0.0-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCZsdbQ+ySUE9xlVoRAjZ0AJ9AjOqAiP1w/l7I7eT5JRBRogKFRwCgqnpu RQuvUau186Wpvmt1oKPmc84= =LbsB -END PGP SIGNATURE- Accepted: librdf0-dev_1.0.0-3_i386.deb to pool/main/r/redland/librdf0-dev_1.0.0-3_i386.deb librdf0_1.0.0-3_i386.deb to pool/main/r/redland/librdf0_1.0.0-3_i386.deb redland-utils_1.0.0-3_i386.deb to pool/main/r/redland/redland-utils_1.0.0-3_i386.deb redland_1.0.0-3.diff.gz to pool/main/r/redland/redland_1.0.0-3.diff.gz redland_1.0.0-3.dsc to pool/main/r/redland/redland_1.0.0-3.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted system-tools-backends 1.2.0-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Apr 2005 23:07:33 +0200 Source: system-tools-backends Binary: system-tools-backends system-tools-backends-dev Architecture: source all Version: 1.2.0-1 Distribution: experimental Urgency: low Maintainer: Jose Carlos Garcia Sogo [EMAIL PROTECTED] Changed-By: Jose Carlos Garcia Sogo [EMAIL PROTECTED] Description: system-tools-backends - System Tools to manage computer configuration -- scripts system-tools-backends-dev - System Tools to manage computer configuration -- development file Changes: system-tools-backends (1.2.0-1) experimental; urgency=low . * Initial Release. * Marc Dequènes (Duck) did all the work for this release. Thanks! Files: 69442c86f617a62815e8b9368ae1e047 1531 admin optional system-tools-backends_1.2.0-1.dsc 6f7538a2e00e7115d3d4649256076685 738095 admin optional system-tools-backends_1.2.0.orig.tar.gz c2fc45a95da97069fa82591cb6036824 2268 admin optional system-tools-backends_1.2.0-1.diff.gz 59c435602b8a6dadde03fa354d6ed44d 564142 admin optional system-tools-backends_1.2.0-1_all.deb cbcc7dc644bf40dcc88ac9937ec822f8 57032 admin optional system-tools-backends-dev_1.2.0-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCZsUvS+BYJZB4jhERAsuhAKClgxNAep43KjPg/s981MK5SVx4FgCeKl7u d4sll/h4YTo6G9Z9BtpJDSM= =XDtX -END PGP SIGNATURE- Accepted: system-tools-backends-dev_1.2.0-1_all.deb to pool/main/s/system-tools-backends/system-tools-backends-dev_1.2.0-1_all.deb system-tools-backends_1.2.0-1.diff.gz to pool/main/s/system-tools-backends/system-tools-backends_1.2.0-1.diff.gz system-tools-backends_1.2.0-1.dsc to pool/main/s/system-tools-backends/system-tools-backends_1.2.0-1.dsc system-tools-backends_1.2.0-1_all.deb to pool/main/s/system-tools-backends/system-tools-backends_1.2.0-1_all.deb system-tools-backends_1.2.0.orig.tar.gz to pool/main/s/system-tools-backends/system-tools-backends_1.2.0.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted surfraw 2.1.0-1 (all source)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Wed, 20 Apr 2005 17:00:59 -0500
Source: surfraw
Binary: surfraw
Architecture: source all
Version: 2.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Christian Surchi [EMAIL PROTECTED]
Changed-By: Thomas Smith [EMAIL PROTECTED]
Description:
surfraw- a fast unix command line interface to WWW
Closes: 289498 289499 289502 289503 290032
Changes:
surfraw (2.1.0-1) unstable; urgency=medium
.
* Ian Beckwith [EMAIL PROTECTED]:
+ New elvi: dmoz, w3html, w3link, w3css, w3rdf.
+ New elvi: rae (by Ruben Pollan [EMAIL PROTECTED]).
+ surfraw.IN:w3_url_escape: escaped `(' and `)'.
+ Fixed elvi (Thanks to Justin B. Rye):
- sunsolve (Closes: #289502).
- altavista (Closes: #289503).
+ deblists: Updated list of debian mailing lists.
+ currency: Now a proper elvis.
+ Added appendix 2 to HACKING on preparing a release.
* Moritz Muehlenhoff [EMAIL PROTECTED]:
+ Switch rhymes search from Lycos to Rhymezone (by Justin B Rye)
(Closes: #289498)
+ Fix BBC News search (by Justin B Rye) (Closes: #289499)
+ New elvi by by Justin B Rye (Closes: #290032)
- cia Search for CIA documents
- deblogs Debian changelogs
- etym Search for word origins
- foldoc Free online dictionary of computing
+ New cve elvis for CAN assignment searches
+ Rewrite debian/copyright properly
Files:
fbb91c617ffe976ecbae13d3c83defc9 559 web optional surfraw_2.1.0-1.dsc
f58ed958545297879d571a1cde3224b2 137302 web optional surfraw_2.1.0-1.tar.gz
f17df27ecad9a3fab0fa445eb003d4e4 72712 web optional surfraw_2.1.0-1_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQFCZtRB/xuE/qyrqB4RAlTSAJ9+FTrhm1AjS6cZJyBvM6pAK676bgCfbOZ0
8vXURkz0atlvYpzeb0kMviU=
=Q9IH
-END PGP SIGNATURE-
Accepted:
surfraw_2.1.0-1.dsc
to pool/main/s/surfraw/surfraw_2.1.0-1.dsc
surfraw_2.1.0-1.tar.gz
to pool/main/s/surfraw/surfraw_2.1.0-1.tar.gz
surfraw_2.1.0-1_all.deb
to pool/main/s/surfraw/surfraw_2.1.0-1_all.deb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted docbook-xml 4.4-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Format: 1.7 Date: Wed, 20 Apr 2005 18:18:45 -0400 Source: docbook-xml Binary: docbook-xml Architecture: source all Version: 4.4-1 Distribution: unstable Urgency: low Maintainer: Adam Di Carlo [EMAIL PROTECTED] Changed-By: Adam Di Carlo [EMAIL PROTECTED] Description: docbook-xml - standard XML documentation system, for software and systems Closes: 268364 292689 301157 304057 Changes: docbook-xml (4.4-1) unstable; urgency=low . * new upstream version; closes: #292689 * debian/examples: add 4.4 examples * add FPI for htmltblx.mod to catalogs for DocBook 4.3; 4.4 already had this; closes: #268364 * add SYSTEM entries for DocBook 4.3: http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd and http://docbook.org/xml/4.3/docbookx.dtd; closes: #301157, #304057 Files: ed102035e05a28b12dd9a989704483cd 712 text optional docbook-xml_4.4-1.dsc 8d6ba38b258126440638aca6aae0445d 396919 text optional docbook-xml_4.4.orig.tar.gz b9aa5d6d79c1cfaf3e4a3c6bf0cb8c39 15551 text optional docbook-xml_4.4-1.diff.gz cb9b23d94092a6c51a4b6f0baa57bc03 337632 text optional docbook-xml_4.4-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iQCVAwUBQmbVh4/8QF79WmfNAQFPOAP+NzCujPP+ZwEWxh759m1yjZqJEITT3Wq0 t0OFwYnQQtZ9Ml5UgRCkzz1XgjQeIXzyFA/yuIFuA91h0KUTquxsN1cgDu+CTZj5 4/gFB/41kl/FyOqAFGxGJG8EKX6YXckhl3Mmmi0tkXOoTYICW3jh0PlrJvl5lhO3 MzjoGNcb59U= =eZ6F -END PGP SIGNATURE- Accepted: docbook-xml_4.4-1.diff.gz to pool/main/d/docbook-xml/docbook-xml_4.4-1.diff.gz docbook-xml_4.4-1.dsc to pool/main/d/docbook-xml/docbook-xml_4.4-1.dsc docbook-xml_4.4-1_all.deb to pool/main/d/docbook-xml/docbook-xml_4.4-1_all.deb docbook-xml_4.4.orig.tar.gz to pool/main/d/docbook-xml/docbook-xml_4.4.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted kbd 1.12-11 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Apr 2005 00:42:22 +0200 Source: kbd Binary: kbd Architecture: source i386 Version: 1.12-11 Distribution: unstable Urgency: medium Maintainer: Denis Barbier [EMAIL PROTECTED] Changed-By: Denis Barbier [EMAIL PROTECTED] Description: kbd- Linux console font and keytable utilities Closes: 305588 Changes: kbd (1.12-11) unstable; urgency=medium . * unicode_start/stop: Replace echo -e by printf commands. Closes: #305588 Thanks, Jan Braun * Update debian/watch file. Files: ccf3c6f10264d93e4bd2126d29eaeca2 598 utils extra kbd_1.12-11.dsc 9f713afe9b8f94ae3be150e73e902530 30086 utils extra kbd_1.12-11.diff.gz 0d1e92798105f3d4203e2d4b91794857 341946 utils extra kbd_1.12-11_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCZuHD8Ri1lR4WGvsRAohzAJ0fyX2o1alfeDuPxrHLSeqg+2azoQCfTKRO 17gSCdZCnmtyFYQTUHHbmOI= =hl/O -END PGP SIGNATURE- Accepted: kbd_1.12-11.diff.gz to pool/main/k/kbd/kbd_1.12-11.diff.gz kbd_1.12-11.dsc to pool/main/k/kbd/kbd_1.12-11.dsc kbd_1.12-11_i386.deb to pool/main/k/kbd/kbd_1.12-11_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted openldap2.2 2.2.23-3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Apr 2005 01:29:57 +0200 Source: openldap2.2 Binary: slapd ldap-utils libldap-2.2-7 Architecture: source i386 Version: 2.2.23-3 Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed-By: Torsten Landschoff [EMAIL PROTECTED] Description: ldap-utils - OpenLDAP utilities libldap-2.2-7 - OpenLDAP libraries slapd - OpenLDAP server (slapd) Closes: 265860 303243 304339 304549 304840 Changes: openldap2.2 (2.2.23-3) unstable; urgency=low . Steve Langasek [EMAIL PROTECTED] * libraries/libldap_r/Makefile.in: Code that uses pthreads *must* be linked with -pthread, even if it's a library; without this, the libldap_r library ends up with dangling unversioned reference to pthread_create() which gets resolved to a wrong version that causes segfaults on 64-bit platforms. Closes: #304549. * debian/rules: error out on build if an installed library has undefined symbols; future-proofing against a repeat of #304549. * debian/slapd.postinst: don't dump and reload directories unless we know we're upgrading from an incompatible version! Closes: #304840. * debian/slapd.scripts-common: don't use merge_logical_lines for functions that will be writing back to the config; the code is not as pretty now, but the output is much less ugly. Closes: #303243. * debian/slapd.examples, debian/slapd.scripts-common, debian/slapd.links, debian/move_files: install DB_CONFIG in /usr/share/slapd/ instead of /usr/share/doc/slapd/examples/; this simplifies the code, and ensures users who don't install /usr/share/doc aren't penalized. Create links for the DB_CONFIG and slapd.confg templates to /usr/share/doc/slapd/examples, since these are worthwhile examples as well. * Updated maintainer scripts to keep DB_CONFIG for LDAP databases over upgrades (closes: #265860). * Move slappasswd to the slapd package, since it's now a symlink and isn't actually useful without the slapd binary (closes: #304339). Files: 7c942ffec1c8d65ba0658fd26f7fa515 999 net optional openldap2.2_2.2.23-3.dsc 62b2bcb60d20dd01ed58994fccc8 478104 net optional openldap2.2_2.2.23-3.diff.gz f242a20d7673b377d8bb8d93d6ab0960 797980 net optional slapd_2.2.23-3_i386.deb d223b5b37666dcdb1ea8ca3e0de21c71 117314 net optional ldap-utils_2.2.23-3_i386.deb 46c7ac17ee7b4a24ea75941f8c8b859f 240602 libs important libldap-2.2-7_2.2.23-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCZugMdQgHtVUb5EcRAn14AJ4sbnxkvFoI/mQ4eHkWMi12APMAdQCffLLw 4Yidij2MCYjkXe1Up9trAC0= =xn9A -END PGP SIGNATURE- Accepted: ldap-utils_2.2.23-3_i386.deb to pool/main/o/openldap2.2/ldap-utils_2.2.23-3_i386.deb libldap-2.2-7_2.2.23-3_i386.deb to pool/main/o/openldap2.2/libldap-2.2-7_2.2.23-3_i386.deb openldap2.2_2.2.23-3.diff.gz to pool/main/o/openldap2.2/openldap2.2_2.2.23-3.diff.gz openldap2.2_2.2.23-3.dsc to pool/main/o/openldap2.2/openldap2.2_2.2.23-3.dsc slapd_2.2.23-3_i386.deb to pool/main/o/openldap2.2/slapd_2.2.23-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted ion3-scripts 20050418-3 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Apr 2005 00:13:01 +0200 Source: ion3-scripts Binary: ion3-scripts Architecture: source all Version: 20050418-3 Distribution: unstable Urgency: low Maintainer: Rene van Bevern (RvB) [EMAIL PROTECTED] Changed-By: Rene van Bevern (RvB) [EMAIL PROTECTED] Description: ion3-scripts - user-contributed add-ons to the Ion 3 window manager Changes: ion3-scripts (20050418-3) unstable; urgency=low . * priority from optional to extra (depends on Ion3, which is extra) . * Upload sponsored by Norbert Tretkowski [EMAIL PROTECTED] Files: eb0c4578eb832b536c7c642dc2bad083 596 misc extra ion3-scripts_20050418-3.dsc cf2c188c514fd288238b435cc6eb2427 4944 misc extra ion3-scripts_20050418-3.diff.gz 2ac71e1a9526f93eec17d13cfafe5cfc 32532 misc extra ion3-scripts_20050418-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCZuWyr/RnCw96jQERAm9dAKCVxk5Tk5PdecdleRZ6FY81fwffAwCfWA9H 2cReg1Z35eVezdk4XYi+0X0= =qhBm -END PGP SIGNATURE- Accepted: ion3-scripts_20050418-3.diff.gz to pool/main/i/ion3-scripts/ion3-scripts_20050418-3.diff.gz ion3-scripts_20050418-3.dsc to pool/main/i/ion3-scripts/ion3-scripts_20050418-3.dsc ion3-scripts_20050418-3_all.deb to pool/main/i/ion3-scripts/ion3-scripts_20050418-3_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted ion3-mod-ionflux 20050420-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Apr 2005 23:48:18 +0200 Source: ion3-mod-ionflux Binary: ion3-mod-ionflux Architecture: source i386 Version: 20050420-1 Distribution: unstable Urgency: low Maintainer: Rene van Bevern (RvB) [EMAIL PROTECTED] Changed-By: Rene van Bevern (RvB) [EMAIL PROTECTED] Description: ion3-mod-ionflux - remote control for the ion3 window manager Changes: ion3-mod-ionflux (20050420-1) unstable; urgency=low . * priority from optional to extra * provide upstream ChangeLog * recent snapshot * adapted manpage to upstream changes * added location of ion3 header files to include path . * Upload sponsored by Norbert Tretkowski [EMAIL PROTECTED] Files: d46bffab9e506639a2b170519fec57b3 691 libs extra ion3-mod-ionflux_20050420-1.dsc 25ab2ce50821ff97e838329b5b004feb 13459 libs extra ion3-mod-ionflux_20050420.orig.tar.gz 57dbbafc0c568523ec13e0b2d8d2f1ff 3461 libs extra ion3-mod-ionflux_20050420-1.diff.gz f2adf9ee7728d5c711f6c2fc3b644ba9 10068 libs extra ion3-mod-ionflux_20050420-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCZuXDr/RnCw96jQERAmHHAKCpUMY4QVIpWXqIp/5mIbvNtFlYrACfV9B0 4QjgIs1tu2L9z7FF43xnh9s= =wiR6 -END PGP SIGNATURE- Accepted: ion3-mod-ionflux_20050420-1.diff.gz to pool/main/i/ion3-mod-ionflux/ion3-mod-ionflux_20050420-1.diff.gz ion3-mod-ionflux_20050420-1.dsc to pool/main/i/ion3-mod-ionflux/ion3-mod-ionflux_20050420-1.dsc ion3-mod-ionflux_20050420-1_i386.deb to pool/main/i/ion3-mod-ionflux/ion3-mod-ionflux_20050420-1_i386.deb ion3-mod-ionflux_20050420.orig.tar.gz to pool/main/i/ion3-mod-ionflux/ion3-mod-ionflux_20050420.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted squid 2.5.9-6 (sparc source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Apr 2005 01:21:58 +0200 Source: squid Binary: squid squid-cgi squidclient squid-common Architecture: source sparc all Version: 2.5.9-6 Distribution: unstable Urgency: medium Maintainer: Luigi Gangitano [EMAIL PROTECTED] Changed-By: Luigi Gangitano [EMAIL PROTECTED] Description: squid - Internet Object Cache (WWW proxy cache) squid-cgi - Squid cache manager CGI program squid-common - Internet Object Cache (WWW proxy cache) - common file squidclient - Command line URL extractor that talks to (a) squid Closes: 305387 Changes: squid (2.5.9-6) unstable; urgency=medium . * Urgency still medium due to upstream fixes that should go into sarge . * debian/patches/09-enable-large-files - Updated again upstream patch, fixing failed assertion store_swapout.c:232: mem-inmem_lo == 0 (Closes: #305387) Files: 9b166a4a82f5e7f4448acaae68bdf3fd 645 web optional squid_2.5.9-6.dsc b9ceec70e39c1e649da976ca74482f90 327987 web optional squid_2.5.9-6.diff.gz bda5cc99782e01a87165633ee66178d3 194694 web optional squid-common_2.5.9-6_all.deb 3f83220706027b50668c727d5c7a4290 769394 web optional squid_2.5.9-6_sparc.deb 824dce0145b54b56166257898bd2bef5 75052 web optional squidclient_2.5.9-6_sparc.deb 890f1d4962fa0d841a7eca360505066a 92420 web optional squid-cgi_2.5.9-6_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCZujM8ZumGJJMDCYRAkzYAJ4pPxbkxb6iRDjOteVOxF5YabWRLACZAa/l cj5PdhCHjfFT1ewTWCs0PnY= =y3rM -END PGP SIGNATURE- Accepted: squid-cgi_2.5.9-6_sparc.deb to pool/main/s/squid/squid-cgi_2.5.9-6_sparc.deb squid-common_2.5.9-6_all.deb to pool/main/s/squid/squid-common_2.5.9-6_all.deb squid_2.5.9-6.diff.gz to pool/main/s/squid/squid_2.5.9-6.diff.gz squid_2.5.9-6.dsc to pool/main/s/squid/squid_2.5.9-6.dsc squid_2.5.9-6_sparc.deb to pool/main/s/squid/squid_2.5.9-6_sparc.deb squidclient_2.5.9-6_sparc.deb to pool/main/s/squid/squidclient_2.5.9-6_sparc.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mouseemu 0.15-2 (powerpc source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Apr 2005 01:46:24 +0200 Source: mouseemu Binary: mouseemu Architecture: source powerpc Version: 0.15-2 Distribution: unstable Urgency: medium Maintainer: Gaudenz Steinlin [EMAIL PROTECTED] Changed-By: Gaudenz Steinlin [EMAIL PROTECTED] Description: mouseemu - Emulate mouse buttons and mouse wheel Closes: 303883 304328 Changes: mouseemu (0.15-2) unstable; urgency=medium . * convert patches to dpatch * passthrough modifier keys (closes: #304328) * improve documentation about default behaviour (closes: #303883). * change default to not emulate mouse buttons on !powerpc * improve usage message * fix -nofork option Files: 93d877c1de99f810855aadb07ef44a8a 573 utils optional mouseemu_0.15-2.dsc cc716d542d02602c13c7d6da5647f687 5692 utils optional mouseemu_0.15-2.diff.gz 0088f5f1205537291266353bb71e131d 11848 utils optional mouseemu_0.15-2_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCZusY8rUqXQpftocRAot5AJ9yyoIlsDl10blwoqIji6Cpxm1AhgCg4Lzx prM86Oaa9laT+LNwrEgt8V0= =B833 -END PGP SIGNATURE- Accepted: mouseemu_0.15-2.diff.gz to pool/main/m/mouseemu/mouseemu_0.15-2.diff.gz mouseemu_0.15-2.dsc to pool/main/m/mouseemu/mouseemu_0.15-2.dsc mouseemu_0.15-2_powerpc.deb to pool/main/m/mouseemu/mouseemu_0.15-2_powerpc.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libembperl-perl 2.0rc3-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Apr 2005 19:25:44 +1000 Source: libembperl-perl Binary: libembperl-perl Architecture: source i386 Version: 2.0rc3-1 Distribution: unstable Urgency: low Maintainer: Angus Lees [EMAIL PROTECTED] Changed-By: Angus Lees [EMAIL PROTECTED] Description: libembperl-perl - A system for building dynamic websites with Perl Changes: libembperl-perl (2.0rc3-1) unstable; urgency=low . * New upstream release. Files: dac5e7760617d57a20b53cb215f7baf2 877 web optional libembperl-perl_2.0rc3-1.dsc b87ceabfb9c2bc46b9ffe3fdeba6046b 653154 web optional libembperl-perl_2.0rc3.orig.tar.gz 957a524bd25da1f697438c72deffc514 37007 web optional libembperl-perl_2.0rc3-1.diff.gz edca978b51e207f284bf881f7aba0f50 882714 web optional libembperl-perl_2.0rc3-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCZuWzg//Ie9Avh3MRAqaaAJ9g1GudyJSzC7uCRxegJD8nY2bPUQCfSSaa vbmhpo7eFx2F3FNVxJL4dvc= =bAEi -END PGP SIGNATURE- Accepted: libembperl-perl_2.0rc3-1.diff.gz to pool/main/libe/libembperl-perl/libembperl-perl_2.0rc3-1.diff.gz libembperl-perl_2.0rc3-1.dsc to pool/main/libe/libembperl-perl/libembperl-perl_2.0rc3-1.dsc libembperl-perl_2.0rc3-1_i386.deb to pool/main/libe/libembperl-perl/libembperl-perl_2.0rc3-1_i386.deb libembperl-perl_2.0rc3.orig.tar.gz to pool/main/libe/libembperl-perl/libembperl-perl_2.0rc3.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted debhelper 4.2.34 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Apr 2005 21:06:43 -0400 Source: debhelper Binary: debhelper Architecture: source all Version: 4.2.34 Distribution: unstable Urgency: low Maintainer: Joey Hess [EMAIL PROTECTED] Changed-By: Joey Hess [EMAIL PROTECTED] Description: debhelper - helper programs for debian/rules Closes: 305226 Changes: debhelper (4.2.34) unstable; urgency=low . * The infinite number of monkeys release. * dh_md5sums: don't crash if PWD contains an apostrophe. Closes: #305226 Files: 99045faf726c2a1044e869a9658742b7 566 devel optional debhelper_4.2.34.dsc 211a0a9e29e42bfc0f65cb9148413855 148668 devel optional debhelper_4.2.34.tar.gz 6e15947699a2175dad3ae0005a7381ad 362578 devel optional debhelper_4.2.34_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCZv7q2tp5zXiKP0wRAi/wAKCz4aRdq2oVpKlnTqXarAgBGttrRQCgz4ID QcNjED1G7PJkZZHckTzbgGI= =c39u -END PGP SIGNATURE- Accepted: debhelper_4.2.34.dsc to pool/main/d/debhelper/debhelper_4.2.34.dsc debhelper_4.2.34.tar.gz to pool/main/d/debhelper/debhelper_4.2.34.tar.gz debhelper_4.2.34_all.deb to pool/main/d/debhelper/debhelper_4.2.34_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted lucene 1.4.3-5 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Apr 2005 17:28:39 -0700 Source: lucene Binary: liblucene-java-doc liblucene-java Architecture: source all Version: 1.4.3-5 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers [EMAIL PROTECTED] Changed-By: Jeff Breidenbach [EMAIL PROTECTED] Description: liblucene-java - full-text search engine library for Java(TM) and demonstration pr liblucene-java-doc - demonstration programs and example code for Lucene Changes: lucene (1.4.3-5) unstable; urgency=low . * update documentation Files: ea7c144b49a54479ac68f3755c997e19 811 contrib/text optional lucene_1.4.3-5.dsc 9ce85d064be4a97a25163ce3578c94b7 8665 contrib/text optional lucene_1.4.3-5.diff.gz b7ca12f43703814e0d30b8aae14b196b 345806 contrib/text optional liblucene-java_1.4.3-5_all.deb 3492f9ccbe3073893c557a9b6f67a041 517118 contrib/text optional liblucene-java-doc_1.4.3-5_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCZvx9azfo3TSzaFYRAmS1AKCVPy6RArVF8UkwpCRkA2Jk9uz0FwCfSyMd +4dOyOx0wuORWErQCm10U1A= =WpAR -END PGP SIGNATURE- Accepted: liblucene-java-doc_1.4.3-5_all.deb to pool/contrib/l/lucene/liblucene-java-doc_1.4.3-5_all.deb liblucene-java_1.4.3-5_all.deb to pool/contrib/l/lucene/liblucene-java_1.4.3-5_all.deb lucene_1.4.3-5.diff.gz to pool/contrib/l/lucene/lucene_1.4.3-5.diff.gz lucene_1.4.3-5.dsc to pool/contrib/l/lucene/lucene_1.4.3-5.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted dmapi 2.2.1-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 29 Sep 2004 11:28:20 +1000 Source: dmapi Binary: libdm0 libdm0-dev Architecture: source i386 Version: 2.2.1-1 Distribution: unstable Urgency: low Maintainer: Nathan Scott [EMAIL PROTECTED] Changed-By: Nathan Scott [EMAIL PROTECTED] Description: libdm0 - Data Management API runtime environment libdm0-dev - Data Management API static libraries and headers Closes: 305055 Changes: dmapi (2.2.1-1) unstable; urgency=low . * New upstream release (closes: #305055) Files: 3883292f470fcdb32f947076d79aee68 531 admin optional dmapi_2.2.1-1.dsc 66e16cb052a5142229e9b8997589c2b3 47658 admin optional dmapi_2.2.1-1.tar.gz 1b995049fc5d6f98314f3dad3d26db72 15480 devel extra libdm0-dev_2.2.1-1_i386.deb 2d0c728f2a398f2477b870a67592b756 12322 libs optional libdm0_2.2.1-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCZv20m8fl3HSIa2MRAqTxAJ4t+xqW3qBAWXMtBG8eFIBRnw8l9wCdE1jB c9Tb34AXCg/EhC+YWZ6z9Tg= =dovR -END PGP SIGNATURE- Accepted: dmapi_2.2.1-1.dsc to pool/main/d/dmapi/dmapi_2.2.1-1.dsc dmapi_2.2.1-1.tar.gz to pool/main/d/dmapi/dmapi_2.2.1-1.tar.gz libdm0-dev_2.2.1-1_i386.deb to pool/main/d/dmapi/libdm0-dev_2.2.1-1_i386.deb libdm0_2.2.1-1_i386.deb to pool/main/d/dmapi/libdm0_2.2.1-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cdebconf 0.76 (powerpc all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Apr 2005 11:19:04 +1000 Source: cdebconf Binary: cdebconf-slang-udeb libdebconfclient0 cdebconf-priority cdebconf libdebconfclient0-dev cdebconf-udeb libdebconfclient0-udeb cdebconf-gtk-udeb cdebconf-text-udeb cdebconf-newt-udeb Architecture: source powerpc all Version: 0.76 Distribution: experimental Urgency: low Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Colin Watson [EMAIL PROTECTED] Description: cdebconf - Debian Configuration Management System (C-implementation) cdebconf-newt-udeb - Newt frontend for Debian Configuration Management System (udeb) cdebconf-priority - Change debconf priority (udeb) cdebconf-text-udeb - Plain text frontend for Debian Configuration Management System (udeb) cdebconf-udeb - Debian Configuration Management System (C-implementation) (udeb) libdebconfclient0 - Debian Configuration Management System (C-implementation) libdebconfclient0-dev - Development files for cdebconf libdebconfclient0-udeb - Debian Configuration Management System (C-implementation) (udeb) Closes: 183541 266898 281395 Changes: cdebconf (0.76) experimental; urgency=low . NOTE: Not for sarge. * Colin Watson - Add draft plugins specification. - Append '\n' to debug messages automatically when printing to stderr, so that they aren't needed in every string. - Tidy up libdebconfclient namespace: rename debconf_commandf to debconfclient_commandf and make it static. Doesn't seem to affect any current users, and if it does, they should have been using debconf-commandf() instead. - Sync from debconf (closes: #266898): + Change the shell confmodule to not construct functions on the fly. The new code is smaller, a bit faster, and simpler, but the important thing is that it does not clobber [EMAIL PROTECTED] The old version messed up $@ if parameters contained spaces. - Add config instances for the standard debconf databases in /target, so that we can do 'debconf-copydb -p foo/bar configdb target_configdb' once the base system is installed. - Remove src/cdebconf.conf-dist on distclean. - Fix some of the build issues with the corba frontend, although it still doesn't even remotely build or work. - Fix compiler warning in slang frontend. - Allocate choices, choices_translated, defaults, and selected dynamically in slang frontend, fixing a crash bug. - Set up slang select/multiselect windows so that the first selected option is always visible (closes: #183541). - Improve how titles are displayed in the text frontend: set titles off with an underline, and only display a title if it's different from the previous one (closes: #281395). * Matthias Urlichs: - Clarify ANS: lines in test.config output. - Set _cmdline::frontend rather than frontend::default::driver in response to 'debconf -f frontend', fixing that. Files: 3a3e03083e8369b628f3777c67224f6d 1060 utils optional cdebconf_0.76.dsc 833b40d96765907cb63bd6f370b5fa88 185495 utils optional cdebconf_0.76.tar.gz 8458ced01d25e1e927b9aeeeacb516f2 1926 debian-installer standard cdebconf-priority_0.76_all.udeb 134280c4ac3121e8730d5bfe578d9e16 127478 utils extra cdebconf_0.76_powerpc.deb 1cd10920995e05001cb063c2b90de407 24610 libs optional libdebconfclient0_0.76_powerpc.deb ccdddc31875258438878c5a2fe63705e 21724 libdevel optional libdebconfclient0-dev_0.76_powerpc.deb 80c3821e76ec1ed5255aff6bfc61211e 70242 debian-installer standard cdebconf-udeb_0.76_powerpc.udeb c01a1d219645c720ce2651e6a9a5a717 4982 debian-installer optional libdebconfclient0-udeb_0.76_powerpc.udeb 20e30107a2c38a6829c7e1f5819ff869 12680 debian-installer optional cdebconf-newt-udeb_0.76_powerpc.udeb 857f8c1b3058a72c2564b168284d672d 16286 debian-installer optional cdebconf-text-udeb_0.76_powerpc.udeb package-type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCZwAp9t0zAhD6TNERAvRCAJ4i7UfgLX/xYLDVZxNNbfQHvRTv/QCfUdj9 LXv8WPXL3cHiAiAY2vR+qa4= =WylU -END PGP SIGNATURE- Accepted: cdebconf-newt-udeb_0.76_powerpc.udeb to pool/main/c/cdebconf/cdebconf-newt-udeb_0.76_powerpc.udeb cdebconf-priority_0.76_all.udeb to pool/main/c/cdebconf/cdebconf-priority_0.76_all.udeb cdebconf-text-udeb_0.76_powerpc.udeb to pool/main/c/cdebconf/cdebconf-text-udeb_0.76_powerpc.udeb cdebconf-udeb_0.76_powerpc.udeb to pool/main/c/cdebconf/cdebconf-udeb_0.76_powerpc.udeb cdebconf_0.76.dsc to pool/main/c/cdebconf/cdebconf_0.76.dsc cdebconf_0.76.tar.gz to pool/main/c/cdebconf/cdebconf_0.76.tar.gz cdebconf_0.76_powerpc.deb to pool/main/c/cdebconf/cdebconf_0.76_powerpc.deb libdebconfclient0-dev_0.76_powerpc.deb to pool/main/c/cdebconf/libdebconfclient0-dev_0.76_powerpc.deb libdebconfclient0-udeb_0.76_powerpc.udeb to
Accepted mozilla-thunderbird-locale-ko 1.0.2.1-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 20 Apr 2005 20:10:54 +0900 Source: mozilla-thunderbird-locale-ko Binary: mozilla-thunderbird-locale-ko Architecture: source all Version: 1.0.2.1-1 Distribution: unstable Urgency: low Maintainer: Yooseong Yang [EMAIL PROTECTED] Changed-By: Yooseong Yang [EMAIL PROTECTED] Description: mozilla-thunderbird-locale-ko - Mozilla Thunderbird Korean Language/Region Package Changes: mozilla-thunderbird-locale-ko (1.0.2.1-1) unstable; urgency=low . * Modified rules in debian directory. Files: c1f9447abc690ad4133e1c244c5875b5 589 web optional mozilla-thunderbird-locale-ko_1.0.2.1-1.dsc f5f4c6231f574381fb078e6df5ce9ea0 368577 web optional mozilla-thunderbird-locale-ko_1.0.2.1-1.tar.gz c3f3c195008ab20233f1ba73097f685c 361730 web optional mozilla-thunderbird-locale-ko_1.0.2.1-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCZv7xChlkiyrnRE4RAvTOAKCX3LqxTek8wxOsRUy3b/4diG7RXQCgqN4e Crr6+rAQNVY0+UGHC9S0w2A= =HSyv -END PGP SIGNATURE- Accepted: mozilla-thunderbird-locale-ko_1.0.2.1-1.dsc to pool/main/m/mozilla-thunderbird-locale-ko/mozilla-thunderbird-locale-ko_1.0.2.1-1.dsc mozilla-thunderbird-locale-ko_1.0.2.1-1.tar.gz to pool/main/m/mozilla-thunderbird-locale-ko/mozilla-thunderbird-locale-ko_1.0.2.1-1.tar.gz mozilla-thunderbird-locale-ko_1.0.2.1-1_all.deb to pool/main/m/mozilla-thunderbird-locale-ko/mozilla-thunderbird-locale-ko_1.0.2.1-1_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted drawtiming 0.4-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Apr 2005 20:12:15 -0600 Source: drawtiming Binary: drawtiming Architecture: source i386 Version: 0.4-1 Distribution: unstable Urgency: low Maintainer: Wesley J. Landaker [EMAIL PROTECTED] Changed-By: Wesley J. Landaker [EMAIL PROTECTED] Description: drawtiming - tool for documenting hardware designs through timing diagrams Changes: drawtiming (0.4-1) unstable; urgency=low . * New upstream release * Reverted usage message patch; fixed upstream Files: 1ad7f907ac61e2f98b25b139f0968cc7 608 electronics optional drawtiming_0.4-1.dsc af843394b5733d0a802b9f11d4dea6d1 102125 electronics optional drawtiming_0.4.orig.tar.gz 22e9f9d686ab3e4c03f128ee094b332e 24126 electronics optional drawtiming_0.4-1.diff.gz a04e1a5bc4cb87ac46576a659e874ce0 43470 electronics optional drawtiming_0.4-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCZw2y8KmKTEzW49IRAv5HAJ9bYDfCOp+DRD0ZpoXt110wPa9xhQCeKLfZ dz2lkW9ZQa0iLRE/0I5Q8XI= =FgxL -END PGP SIGNATURE- Accepted: drawtiming_0.4-1.diff.gz to pool/main/d/drawtiming/drawtiming_0.4-1.diff.gz drawtiming_0.4-1.dsc to pool/main/d/drawtiming/drawtiming_0.4-1.dsc drawtiming_0.4-1_i386.deb to pool/main/d/drawtiming/drawtiming_0.4-1_i386.deb drawtiming_0.4.orig.tar.gz to pool/main/d/drawtiming/drawtiming_0.4.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
