Re: greylisting on debian.org?
Le mar 18 juillet 2006 00:08, Magnus Holmgren a écrit : On Monday 17 July 2006 23:41, Pierre Habouzit took the opportunity to write: Le lun 17 juillet 2006 19:53, Adrian von Bidder a écrit : So the question is, imho, not if we should potentially lock out users of big mail pools - those are in the default whitelists anyway by now. The question is: can we temporarily (until they can be whitelisted) lock out users of standards?-who-needs-standards? systems that don't implement sensible queueing. Many of these sites are small - but there are also a few bigger names: Yahoo groups, Amazon, Roche, Motorola. (According to postgrey's default whitelist. Some of these are from 2004 or earlier, and AFAIK nobody tries to verify if these systems are still stupid in that way.) OTOH those systems are not listed on RBL's (or it does not last) and you won't greylist them. Which RBL's do you have in mind? I mean, some RBL's, like XBL/SBL, are high-quality enough that you can outright reject. Others, like SpamCop, are likely to include some of the bigger names from time to time. DUL lists might be good candidates. I personnaly use DUL, rfc-ignorant and XBL/SBL. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpgIScRRQMZr.pgp Description: PGP signature
Re: Bits from the Package Tracking System
On Mon, 17 Jul 2006, Stefano Zacchiroli wrote: Is an archive of those mails available somewhere? This way the small patches will be available even for packages of people not subscribed to the PTS. Or for people who subscribe after some version has been uploaded to ubuntu. There's only the mailing list archive on the Ubuntu side for now. I agree that the PTS should have a web archive for all the content that is generated mainly for it and that is not simply relayed via it (like the BTS mails). Nobody has implemented that yet though, and it will also be quite expensive on disk size... (it shouldn't be a big worry however given the disk size that recent Debian servers tend to have) A dumb way to implement that is of course set up a mail account subscribed to all packages with the derivative keyword. I can set up such an account, but I guess there exists an easier solution for setting up the archive on the PTS side. Could you comment on that? Please don't go to the quick dirty route. With the scale of the PTS you would simply create unnecessary load for the mail processing that master.debian.org really doesn't need. The PTS scripts receive the mail directly, they can be patched to store a copy for the web frontend. Someone just needs to do it prperly... (cf my call for help at the of the announce ;-)). Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Blocking my transition
Processing commands for [EMAIL PROTECTED]: block 322762 by 378646 Bug#322762: /usr/doc still exists (transition tracking bug) Was blocked by: 189856 190020 203278 254800 254913 254924 255590 302504 319726 320084 320103 321926 322749 322769 322772 322776 322778 322779 322781 322782 322783 322784 322785 322786 322787 322788 322789 322790 322791 322792 322793 322794 322795 322797 322798 322799 322800 322801 322803 322804 322805 322806 322807 322808 322809 322810 322811 322812 322813 322814 322815 322816 322817 322818 322819 322820 322828 322829 322830 322831 322832 322833 322834 322835 322837 322838 322839 352893 352894 353569 355341 359358 359359 359361 359362 359363 359364 359365 359366 359367 359368 359369 359370 359371 359372 359374 359375 359376 359377 359378 359379 359380 359381 359382 359383 359384 359385 359386 359387 359388 359389 359390 359391 359392 359393 359394 359395 359396 359399 359400 359401 359403 359405 359406 359407 359408 359409 359410 359411 359412 359413 359414 359417 359418 359419 359420 359421 359422 359423 359424 359425 359426 359427 359428 359429 359430 359431 359432 359433 359434 359435 359436 359437 359439 359440 359441 359442 359443 359444 359445 359446 359447 359448 359449 359450 359451 359452 359453 359454 359455 359456 359457 359458 359459 359460 359461 359462 359463 359464 359465 359466 359467 359468 359469 359470 359471 359472 359473 359474 359475 359476 359477 359478 359479 359480 359481 359482 359483 359484 359485 359486 359487 359488 359489 359490 359491 359492 359493 359494 359495 359496 359497 359498 359499 359500 359501 359502 359503 359504 359505 359506 359507 359508 359509 359510 359511 359512 359513 359514 359515 359516 359517 359518 359519 359520 359521 359522 359523 359524 359526 359527 359528 359529 359530 359531 359532 359533 359534 359535 359536 359537 359538 359539 359540 359541 359542 359543 359544 359545 359546 359547 359548 359549 359550 359551 359552 359553 359554 359555 359556 359557 359558 359559 359560 359561 359562 359563 359564 359566 359567 359568 359569 359570 359571 359572 359573 359574 359575 359576 359577 359578 359579 359580 359581 359582 359583 359584 359585 359586 359587 359588 359589 359590 359591 359592 359593 359594 359595 359596 359597 359598 359599 359600 359601 359602 359603 359604 359605 359606 359607 359608 359609 359610 359611 359612 Blocking bugs of 322762 added: 378646 block 322762 by 378648 Bug#322762: /usr/doc still exists (transition tracking bug) Was blocked by: 189856 190020 203278 254800 254913 254924 255590 302504 319726 320084 320103 321926 322749 322769 322772 322776 322778 322779 322781 322782 322783 322784 322785 322786 322787 322788 322789 322790 322791 322792 322793 322794 322795 322797 322798 322799 322800 322801 322803 322804 322805 322806 322807 322808 322809 322810 322811 322812 322813 322814 322815 322816 322817 322818 322819 322820 322828 322829 322830 322831 322832 322833 322834 322835 322837 322838 322839 352893 352894 353569 355341 359358 359359 359361 359362 359363 359364 359365 359366 359367 359368 359369 359370 359371 359372 359374 359375 359376 359377 359378 359379 359380 359381 359382 359383 359384 359385 359386 359387 359388 359389 359390 359391 359392 359393 359394 359395 359396 359399 359400 359401 359403 359405 359406 359407 359408 359409 359410 359411 359412 359413 359414 359417 359418 359419 359420 359421 359422 359423 359424 359425 359426 359427 359428 359429 359430 359431 359432 359433 359434 359435 359436 359437 359439 359440 359441 359442 359443 359444 359445 359446 359447 359448 359449 359450 359451 359452 359453 359454 359455 359456 359457 359458 359459 359460 359461 359462 359463 359464 359465 359466 359467 359468 359469 359470 359471 359472 359473 359474 359475 359476 359477 359478 359479 359480 359481 359482 359483 359484 359485 359486 359487 359488 359489 359490 359491 359492 359493 359494 359495 359496 359497 359498 359499 359500 359501 359502 359503 359504 359505 359506 359507 359508 359509 359510 359511 359512 359513 359514 359515 359516 359517 359518 359519 359520 359521 359522 359523 359524 359526 359527 359528 359529 359530 359531 359532 359533 359534 359535 359536 359537 359538 359539 359540 359541 359542 359543 359544 359545 359546 359547 359548 359549 359550 359551 359552 359553 359554 359555 359556 359557 359558 359559 359560 359561 359562 359563 359564 359566 359567 359568 359569 359570 359571 359572 359573 359574 359575 359576 359577 359578 359579 359580 359581 359582 359583 359584 359585 359586 359587 359588 359589 359590 359591 359592 359593 359594 359595 359596 359597 359598 359599 359600 359601 359602 359603 359604 359605 359606 359607 359608 359609 359610 359611 359612 378646 Blocking bugs of 322762 added: 378648 block 322762 by 378649 Bug#322762: /usr/doc still exists (transition tracking bug) Was blocked by: 189856 190020 203278 254800 254913 254924 255590 302504 319726 320084 320103 321926 322749 322769
Re: greylisting on debian.org?
On Mon, Jul 17, 2006 at 11:48:21PM +0200, Pierre Habouzit wrote: Le lun 17 juillet 2006 22:29, Lionel Elie Mamane a écrit : Here is one: I am strongly opposed to greylisting (on mail sent to me or that I send), for the reason that it delays legitimate mail. which shows that you didn't read the discussion Wrong. Disagreeing with you is not the same as not reading your arguments. Sorry that you were not convincing. that was about enabling greylisting on *certain* *specificaly* *suspicious* hosts. I know. a suspicious host is: * either listed on some RBL's (rbl listing dynamic blocks are a good start usually) * either having no reverse DNS set * either having curious EHLO lines (that one may catch too much good mail sadly, so it's to handle with care). * ... This will still include legitimate mail. I apply greylisting on the two first criteriums on a quite used mail server (around 300.k mails per week, which is not very big, but should be representative enough). there is less than 50 mails a week over those that *may* be legitimate mails that are actually slowed down. Bingo: Legitimate mail slowed down. You think the price is worth it, which is a valid opinion. I happen not to think so. Usually when mail I send gets greylisted, it is because the software thinks I am suspicious. so *please* do me a favour, read the thread you are answering to, I did. because you really really answer miles away from the debate. No, I'm not. I'm expressing an opinion after reading all of the debate, from the points of it I remember. and if you never actually realized, there *IS* such a slowdown on debian mail lists, it's called crossassassin, it kills master on a regular basis, and is *REALLY* less effective than greylisting. I don't remember the master cannot cope under mail load, we need desperate measures point being brought up before. I may have missed it. Best Regards, -- Lionel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: greylisting on debian.org?
On Tue, Jul 18, 2006 at 12:47:49AM +0200, Josselin Mouette wrote: Le lundi 17 juillet 2006 à 22:29 +0200, Lionel Elie Mamane a écrit : On Sun, Jul 16, 2006 at 08:36:31AM +0200, Christian Perrier wrote: Quoting Wolfgang Lonien ([EMAIL PROTECTED]): Do we use greylisting on the @debian.org domain and especially on @lists.debian.org? So, up to now, we've found Thomas Bushnell who seems really hardly voting against greylisting on Debian hosts, (...). So far and unless I forget someone, I haven't seen much other people being strongly opposed to greylisting on Debian hosts, Here is one: I am strongly opposed to greylisting (on mail sent to me or that I send), for the reason that it delays legitimate mail. I have refused greylisting for a long time for that exact reason. However the setup Pierre Habouzit describes does not delay most of legitimate mail. That is the crux of the disagreement. You guys think that as long as most of the legitimate mail is not delayed, the price is worth it. I don't think so. Frankly, the remaining delays are sporadic and one can live with them. Knowing that most legitimate mail doesn't get delayed doesn't make me feel better when mail I sit waiting for gets delayed. Obviously, for most mail I don't care as I don't sit waiting for it, I batch-treat it a fez times per day or per week. So a half-hour delay on it, I don't even see it. For *most* mail. I'm applying greylisting if one of these conditions is met: * the incoming IP is listed in a DUL; Bingo! You hit a hot button of mine. * Exim sender/callout fails with a fatal error. Fatal means not temporary? -- Lionel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: greylisting on debian.org?
* Stephen Gran [EMAIL PROTECTED] [2006-07-17 18:43]: It's not uncommon for big sites to have pools of high throughput machines that don't have qrunners, and larger pools of machines that do. The first group gets a message, and tries to deliver immediately, and any temporary failure gets the messages shunted to the secondary pool. Once in the secondary pool, it can be bounced from machine to machine to load balance queue size and so on. That being said, the original query about this was a strawman argument designed specifically to find a problem, and I would say fairly confidently we don't need to worry about this. I have analyzed the logs on mail servers I have access to, and I cannot find any site which passes a message between more than a half dozen or at most a dozen IP addresses before delivery. This is two or three orders of magnitude less than the kind of thing Thomas and others are concerned about. By the time sites big enough to use pools that big exist (which I actually doubt - scalability might just be too hard to manage to be worth it), greylisting will be another dead tool in the arms race with spammers. So far, all the arguments against the idea have just been assertions and strawmen. Unless someone can present a serious argument, can we consider this thread done? I've been using greylisting with postgrey and whitelists for some time now (more than a year to be precise) and I still do get mail from gmail, yahoo and msn accounts. And if one is so concerned about them one could contact their postmasters asking for a list of IPs for whitelisting. After all we are talking about developers @debian.org email addresses not abouts lists.debian.org. yours Martin -- [EMAIL PROTECTED] Debian GNU/Linux - The Universal Operating System * Myon wirft noch ein paar 'f' zum Verteilein in den Channel -!- florolf is now known as fflorolff
Re: greylisting on debian.org?
Le mardi 18 juillet 2006 à 09:47 +0200, Lionel Elie Mamane a écrit : That is the crux of the disagreement. You guys think that as long as most of the legitimate mail is not delayed, the price is worth it. I don't think so. If too much spam gets through, *all* legitimate mail gets delayed. It gets delayed by the additional filters it has to get through thereafter, and it gets delayed by having to dig it out of a mailbox full of spam. * Exim sender/callout fails with a fatal error. Fatal means not temporary? It means either the domain doesn't exist, or the server explicitly replied the user doesn't exist. -- .''`. Josselin Mouette/\./\ : :' : [EMAIL PROTECTED] `. `'[EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom
Re: greylisting on debian.org?
Le mar 18 juillet 2006 09:34, Lionel Elie Mamane a écrit : This will still include legitimate mail. something like 50 over 300k is less than 0.016%. which is also really less than the usual number of false positives of your bayesian mail filter. see end of mail. and if you never actually realized, there *IS* such a slowdown on debian mail lists, it's called crossassassin, it kills master on a regular basis, and is *REALLY* less effective than greylisting. I don't remember the master cannot cope under mail load, we need desperate measures point being brought up before. I may have missed it. these days master has a high load on a regular basis: load average: 239.68, 299.68, 326.84 from IRC a couple of days ago, What I experience as a debian developer is that: * 80% of the overall spam that eventually comes into my inbox went through my debian.org account, that renders the read of such a mailbox really hard, and I'm pretty sure that I miss more than 0.016% of legitimate mail in my readings. * my @debian.org address has considerable slowdowns due to our MXs beeing overloaded from time to time. 80% of the time, it's because of crossassassin becoming mad, or some spam attack. Just take some factual numbers: I receive sth like 300 mails a day (top, I think the mean value is more around 150). that makes 109.500 mails a year. I know for a fact that my bayesian filter makes sth like 4 to 5 errors per year. And yes I know how to train one. So my bayesian mail filter has at least a 0.05% false positive rate, and I'm really convinced in fact it's more like 0.1% (maybe even more). SA is used extensively on debian hosts, I'm also quite sure it also has worse rates than a 0.1%. So you are claiming that greylisting is a really bad method ? come on ! currently, I receive so many spams from debian, that I just CANT sort them. it's sth like 90spams a *day* sometimes. How do you find the time to look at the good mails in there ? I can't. So by not delaying 0.016% of the legitimate mails, you make a lot of people *LOOSE* for real way more than that. please, your point is only made of impressions, now you have numbers. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpG5ojNkr7dX.pgp Description: PGP signature
Measuring should I greylist? false positive rate [was: greylisting on debian.org?]
On Mon, Jul 17, 2006 at 11:48:21PM +0200, Pierre Habouzit wrote: Le lun 17 juillet 2006 22:29, Lionel Elie Mamane a écrit : the discussion (...) was about enabling greylisting on *certain* *specificaly* *suspicious* hosts. a suspicious host is: * either listed on some RBL's (rbl listing dynamic blocks are a good start usually) * either having no reverse DNS set * either having curious EHLO lines (that one may catch too much good mail sadly, so it's to handle with care). * ... I apply greylisting on the two first criteriums on a quite used mail server (around 300.k mails per week, which is not very big, but should be representative enough). there is less than 50 mails a week over those that *may* be legitimate mails that are actually slowed down. On second thought, I'm very interested in how you measured this false positive rate. Do all the recipients of the 300k mails per week check for every mail if it was greylisted (that means you would put a header or something like that saying this mail was greylisted?), and they _always_ check on _every_ legitimate mail and _always_ report false positives to you? Probably not. So, are these 50 mails a week all the mail that undergoes greylisting but *still* goes through (i.e. gets retried, roughly)? Something else? -- Lionel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: greylisting on debian.org?
* Lionel Elie Mamane [EMAIL PROTECTED] [2006-07-17 22:32]: On Sun, Jul 16, 2006 at 08:36:31AM +0200, Christian Perrier wrote: So far and unless I forget someone, I haven't seen much other people being strongly opposed to greylisting on Debian hosts, Here is one: I am strongly opposed to greylisting (on mail sent to me or that I send), for the reason that it delays legitimate mail. Greylisting is among the minor causes for mail delays in my experience. Most delays when it comes to debian.org mails are caused by the load on the servers from what I see. With other companies mails the main delays are caused by their ISPs smarthosts as they always have queue times of up to 30 minutes while greylisting only delays once. yours Martin -- [EMAIL PROTECTED] Debian GNU/Linux - The Universal Operating System yath lol, mein feuermelder ist dausicher yath im batteriefach unter der batterie steht yath WARNUNG: BATTERIE ENTFERNT -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Getting the buildds to notice new architectures in a package
Wouter Verhelst [EMAIL PROTECTED] writes: On Mon, Jul 17, 2006 at 02:40:28PM -0400, Joe Smith wrote: Wouter Verhelst [EMAIL PROTECTED] wrote in message There is no such general solution. See http://www.debian.org/devel/buildd/wanna-build-states#not-for-us That says: However, wanna-build does not look at the control file of a package when creating its database; only at the packages' name and section, its urgency, and its priority. Shouldn't wanna-build use the control file? Perhaps. The issue is that wanna-build needs to know whether a package has already been built for its architecture; one can only find that out by looking at the Packages file, and comparing that with the Sources file. Since the Packages and Sources files contain all the information wanna-build needs (except for the architectures for which a build should be attempted), and since fetching the control files is a _lot_ more work than to write a parser for Packages and Sources files which can just be piped into wanna-build, it isn't done. Also, such a thing would probably require quite some I/O, so I'm not entirely sure it's worth it. But if you could write some patch which does not ever break and which allows to read the control file, I'm sure it'll be welcome. (I'm not sure why it still listed upload urgency as a criterion there -- that's a bug in the documentation that I introduced, but it's never been true. I've just committed a fix) It would then mean that the lists of packages-arch-specific would not be needed, except in the case of a single version override in the event that a package's control file accidentally listed an architecture on which it is not supported, or failed to list an architecture on which it is supported. The latter wouldn't work anyway -- if it isn't supported, dpkg-buildpackage refuses to build the package. Two things: - control files are part of the source. w-b would have to download and unpack every source package to get that file. - control files can be auto generated during build (e.g. glibc) and might not even list the packages and architectures If you want to get rid of the P-a-s file then I suggest you work on fixing the Architecture field in the Sources file to truely reflect the architectures the source should be build for. What you have to worry about is the case of architecture specific sources that also have architecture independent packages. In those cases the Architecture field lists any instead of e.g. i386 amd64 all. If you fix that and allow sources to override the Architecture field (for autogenerated control files like glibc) then the Sources.gz file would have all the right information in the normal case. This would cut down the P-a-s list seriously. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Measuring should I greylist? false positive rate [was: greylisting on debian.org?]
Le mar 18 juillet 2006 10:00, Lionel Elie Mamane a écrit : On Mon, Jul 17, 2006 at 11:48:21PM +0200, Pierre Habouzit wrote: Le lun 17 juillet 2006 22:29, Lionel Elie Mamane a écrit : the discussion (...) was about enabling greylisting on *certain* *specificaly* *suspicious* hosts. a suspicious host is: * either listed on some RBL's (rbl listing dynamic blocks are a good start usually) * either having no reverse DNS set * either having curious EHLO lines (that one may catch too much good mail sadly, so it's to handle with care). * ... I apply greylisting on the two first criteriums on a quite used mail server (around 300.k mails per week, which is not very big, but should be representative enough). there is less than 50 mails a week over those that *may* be legitimate mails that are actually slowed down. On second thought, I'm very interested in how you measured this false positive rate. Do all the recipients of the 300k mails per week check for every mail if it was greylisted (that means you would put a header or something like that saying this mail was greylisted?), and they _always_ check on _every_ legitimate mail and _always_ report false positives to you? Probably not. So, are these 50 mails a week all the mail that undergoes greylisting but *still* goes through (i.e. gets retried, roughly)? Something else? it's the number of mails that are beeing resubmited per week with my system. so in fact, in them, there is 49 spams. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgprK1lXgWxgo.pgp Description: PGP signature
Re: Getting the buildds to notice new architectures in a package
Wouter Verhelst [EMAIL PROTECTED] writes: On Mon, Jul 17, 2006 at 05:53:25AM +0200, Goswin von Brederlow wrote: The buildd package could just be a central hub where two or three knowlegable people sift through the bug reports and then distribute it to the affected/responsible person. Who would you suggest would do that? I know it's not going to be me. Make a job description, sign it and post it to debian-devel-announce and the jobs page. If there is no volunteer that is it. Otherwise you have your person. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Measuring should I greylist? false positive rate [was: greylisting on debian.org?]
Le mar 18 juillet 2006 10:03, Pierre Habouzit a écrit : Le mar 18 juillet 2006 10:00, Lionel Elie Mamane a écrit : On Mon, Jul 17, 2006 at 11:48:21PM +0200, Pierre Habouzit wrote: Le lun 17 juillet 2006 22:29, Lionel Elie Mamane a écrit : the discussion (...) was about enabling greylisting on *certain* *specificaly* *suspicious* hosts. a suspicious host is: * either listed on some RBL's (rbl listing dynamic blocks are a good start usually) * either having no reverse DNS set * either having curious EHLO lines (that one may catch too much good mail sadly, so it's to handle with care). * ... I apply greylisting on the two first criteriums on a quite used mail server (around 300.k mails per week, which is not very big, but should be representative enough). there is less than 50 mails a week over those that *may* be legitimate mails that are actually slowed down. On second thought, I'm very interested in how you measured this false positive rate. Do all the recipients of the 300k mails per week check for every mail if it was greylisted (that means you would put a header or something like that saying this mail was greylisted?), and they _always_ check on _every_ legitimate mail and _always_ report false positives to you? Probably not. So, are these 50 mails a week all the mail that undergoes greylisting but *still* goes through (i.e. gets retried, roughly)? Something else? it's the number of mails that are beeing resubmited per week with my system. so in fact, in them, there is 49 spams. oh and as a matter of a fact, I just happen to see that you Cc-ed me on the exchanges, I just received the first mail you sent. Just see by yourself how fast and furious master runs: Received: from master.debian.org (master.debian.org [70.103.162.30]) by mx1.polytechnique.org (Postfix) with ESMTP id 7512D33176 for [EMAIL PROTECTED]; Tue, 18 Jul 2006 10:05:31 +0200 (CEST) Received: from 5.xs4all.nl ([213.84.114.29] helo=capsaicin.mamane.lu) by master.debian.org with esmtp (Exim 4.50) id 1G2k5n-0007ft-48; Tue, 18 Jul 2006 02:34:07 -0500 Yeah, master took 31 minutes to deliver the mail to the next SMTP server, and I'm an admin on it (that's the mail server I was speaking of earlier in the thread) and it was its first submission. so maybe it's time you revise your jugements on how efficient debian.org mails servers are recently. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpRFeDq5zoAC.pgp Description: PGP signature
Re: greylisting on debian.org?
(afaik, it's very obvious that I'm subscribed to -devel and, unless I'm wrong, I never requeted for being CC'ed in private) Lionel Elie Mamane a écrit : Wrong. Disagreeing with you is not the same as not reading your arguments. Sorry that you were not convincing. I'm afraid you failed to make it clear. Glad that you cleared this out. This will still include legitimate mail. Sure...just like legitimate mail is very likely to be slowed...or lost on DD machines because most of us *have* to use anti-spam measures on our own machines (most often without the needed complete knowledge, /me being the first). Or, even without this, slowing down because our @debian.org addresses are overspammed and we may be likely to jst miss one important mail. Or (already happened to me) losing information because a legitimate mail, lost in a bunch of spam crap, was infortunate enough to just appear like spam...and be discarded or not read. There is a price to pay and slowing down (not losing...slowing down) a very small portion of legitimate mail is a small part of it. Bingo: Legitimate mail slowed down. You think the price is worth it, which is a valid opinion. I happen not to think so. The question becomes: aren't you in a small minority? We certainly all know that it's perfectly impossible to reach a 100% consensus on such a topic. But what would be your point if a strong majority of DD agrees with the use of greylisting (as described by Pierre) I don't remember the master cannot cope under mail load, we need desperate measures point being brought up before. I may have missed it. Well, given the way I received debian lists mail last day, there has probably been something somewhere..:) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Measuring should I greylist? false positive rate [was: greylisting on debian.org?]
On Tue, Jul 18, 2006 at 10:03:59AM +0200, Pierre Habouzit wrote: Le mar 18 juillet 2006 10:00, Lionel Elie Mamane a écrit : On Mon, Jul 17, 2006 at 11:48:21PM +0200, Pierre Habouzit wrote: Le lun 17 juillet 2006 22:29, Lionel Elie Mamane a écrit : the discussion (...) was about enabling greylisting on *certain* *specificaly* *suspicious* hosts. a suspicious host is: * either listed on some RBL's (rbl listing dynamic blocks are a good start usually) * either having no reverse DNS set * either having curious EHLO lines (that one may catch too much good mail sadly, so it's to handle with care). * ... I apply greylisting on the two first criteriums on a quite used mail server (around 300.k mails per week, which is not very big, but should be representative enough). there is less than 50 mails a week over those that *may* be legitimate mails that are actually slowed down. On second thought, I'm very interested in how you measured this false positive rate. it's the number of mails that are beeing resubmited per week with my system. so in fact, in them, there is 49 spams. Fascinating. Which RBL's do you use for that? Or do you have atypical mail patterns? Exactly two of my 50-or-so mail users use greylisting, based on RBLs *only*. They are kinda high-traffic mail users, but still, they, on their own, push the greylisting this triplet is allowed database entries to the thousands. The this triplet tried once, but not more, in the alloted time database entries are more numerous only by about an order of magnitude. -- Lionel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: greylisting on debian.org?
On Tue, Jul 18, 2006 at 10:22:41AM +0200, Christian Perrier wrote: Lionel Elie Mamane a écrit : Bingo: Legitimate mail slowed down. You think the price is worth it, which is a valid opinion. I happen not to think so. The question becomes: aren't you in a small minority? That may very well be. A message was sent saying only Thomas disagrees, I just wanted to say that if we go the voice-counting way, I have one, too. We certainly all know that it's perfectly impossible to reach a 100% consensus on such a topic. But what would be your point if a strong majority of DD agrees with the use of greylisting (as described by Pierre) Then it would be OK to implement it. The very best would be to do the same I do on my mail server, where users can individually choose greylisting or not for personal mail to them, by a settings file in their home directory. But if a strong majority wants greylisting, it is OK to just do it on all mail (except postmaster@, maybe). I don't remember the master cannot cope under mail load, we need desperate measures point being brought up before. I may have missed it. Well, given the way I received debian lists mail last day, there has probably been something somewhere..:) I meant in this thread. I do not read all threads, nor all mailing lists. -- Lionel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Recent sid amd64 rpath oddity?
Hi, On the 3rd May I built libxfce4util and generated libxfce4util2_4.3.90.1-1_amd64.deb. This is in the archive exactly as I built it. It has a couple of lintian failures that I missed and have since been fixed in our SVN. Upstream have released recently and whilst checking these packages more thoroughly I've fixed up the lintian errors but I've also built the new package and I noticed that it's defining an rpath. So I rooted around and tried to work out why but couldn't really work it out. Upstream's libtool and autotools looked recent to me. If I relibtoolize though this does go away. Out of curiousity I rebuilt the previous package i.e. 4.3.90.1-1 again from the same source files as before but with current sid and this time it fails with two extra lintian warnings: W: libxfce4util2: binary-or-shlib-defines-rpath ./usr/lib/libxfce4util.so.2.1.0 /usr/lib W: libxfce4util2: binary-or-shlib-defines-rpath ./usr/sbin/xfce4-kiosk-query /usr/lib If I rebuild the same package on i386 current sid then I don't get the rpath installed. I guess I have several questions: - how can the same source package over a few months build differently in this way? - am I really going to have to relibtoolize every xfce package before I upload or make them do it themselves? :-/ - how evil is an rpath on /usr/lib anyway? I'd welcome any testers on amd64 or not and on recent sid or not to narrow this down. Or any clues as to how on earth this can happen. If you do want to relibtoolize then install xfce4-dev-ools and run xdt-autogen in the package dirrectory. Thanks. Simon. heh, good sigmonster. -- oOoOo Open source is about letting go of complete control. Accept oOoOo oOoOo the fact that other people are wonderful resources tooOoOo oOoOo fixing problems, and let them help you. - Linus Torvalds oOoOo htag.pl 0.0.22 ::: http://www.earth.li/~huggie/ signature.asc Description: Digital signature
Re: Measuring should I greylist? false positive rate [was: greylisting on debian.org?]
Le mar 18 juillet 2006 10:27, Lionel Elie Mamane a écrit : On Tue, Jul 18, 2006 at 10:03:59AM +0200, Pierre Habouzit wrote: it's the number of mails that are beeing resubmited per week with my system. so in fact, in them, there is 49 spams. Fascinating. Which RBL's do you use for that? Or do you have atypical mail patterns? Exactly two of my 50-or-so mail users use greylisting, based on RBLs *only*. They are kinda high-traffic mail users, but still, they, on their own, push the greylisting this triplet is allowed database entries to the thousands. The this triplet tried once, but not more, in the alloted time database entries are more numerous only by about an order of magnitude. I already told before what I use for my personnal setup. on those servers it's: rbl: cbl.abuseat.org rbl: dynablock.njabl.org we used to use dul.dnsbl.sorbs.net, but it recently got mad and took ages to answer, making us greylist the whole planet. The 50 resubmitted mails are what we have now that the 'postgrey' database is trained. it was a bit higher during the earlier days. and the efficiency is remarkable: http://madism.org/~madcoder/pub/glist.png (it's only one of the MX's) the green area is the amount of accepted mails. the red/blue/orange curves are what our bayesian filter thinks of those mails. the grey curve is unrelated to the others, and is the amount of mails we temporarily refused. Like said, very few are resubmited after. sadly we don't draw them, we should... since we have that setup, our servers rarely have a load over 0.8 (only when a big mail list delivers), whereas it was over 3 to 4 frequently due to spam before. mails are always delivered in less than 3 seconds (against sth up to the minute before). -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpPxRD01nBHD.pgp Description: PGP signature
Re: greylisting on debian.org?
Then it would be OK to implement it. The very best would be to do the same I do on my mail server, where users can individually choose greylisting or not for personal mail to them, by a settings file in their home directory. But if a strong majority wants greylisting, it is OK to just do it on all mail (except postmaster@, maybe). Well, if per-user settings are possible, then it would be a *very* valuable feature to have. That would certainly allow avoiding concerns like yours (or minimize them as much as possible). Dunno if that is possible with Pierre Habouzit greylisting system...Pierre? --
Bug#378671: ITP: jpnevulator - Serial sniffer
Package: wnpp Severity: wishlist Owner: Freddy Spierenburg [EMAIL PROTECTED] * Package name: jpnevulator Version : 1.2.2 Upstream Author : Freddy Spierenburg * URL : http://jpnevulator.snarl.nl/ * License : GPL Programming Lang: C Description : Serial sniffer jpnevulator is a handy serial sniffer. You can use it to send data on a serial device too. You can read or write from/to one or more serial devices at the same time. . In write mode data to be send on the serial device(s) is read from a file or stdin in hexadecimal notation. Data is send on the serial device(s) line by line. . In read mode data to be read from the serial device(s) is written to a file or stdout in hexadecimal notation. Several options enhance the way the data is displayed. -- $ cat ~/.signature Freddy Spierenburg [EMAIL PROTECTED] http://freddy.snarl.nl/ GnuPG: 0x7941D1E1=C948 5851 26D2 FA5C 39F1 E588 6F17 FD5D 7941 D1E1 $ # Please read http://www.ietf.org/rfc/rfc2015.txt before complain! signature.asc Description: Digital signature
Re: greylisting on debian.org?
Le mar 18 juillet 2006 11:51, Christian Perrier a écrit : Then it would be OK to implement it. The very best would be to do the same I do on my mail server, where users can individually choose greylisting or not for personal mail to them, by a settings file in their home directory. But if a strong majority wants greylisting, it is OK to just do it on all mail (except postmaster@, maybe). Well, if per-user settings are possible, then it would be a *very* valuable feature to have. That would certainly allow avoiding concerns like yours (or minimize them as much as possible). Dunno if that is possible with Pierre Habouzit greylisting system...Pierre? it is, and it's not. the historical way to perform greylist is to do it on a per user basis, answering your 200/400 answers to each RCPT TO command. so basically, the greylister could know he should not greylist some recipients. *but*: (1) many broken MTA do not understand that you give a 400 to some RCPT's and not others, and have erratic behaviours that may result in: - many resents of the same mail for the people that do not use greylisting - delay even for the one that do not user greylisting (2) modern greylisting usually do it at DATA now (I mean at the DATA command, where the smtpd usually anser sth like: 321 please end your command with CRLF.CRLF or sth similar), because it makes checks beeing done only once. but basically, what I've suggested alread some time ago, is not to refine the greylisting method, here you can use whatever greylister you want, with whatever customization you need/want. I just suggested to do conditionnal greylisting, the rest is up to the greylister you use, really. everything is possible. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpgGNtDYLpPw.pgp Description: PGP signature
Re: Bits from the Package Tracking System
On Mon, Jul 17, 2006 at 10:39:18PM +0200, Raphael Hertzog wrote: Changing keyword on all subscriptions - The control bot has been expanded to support new commands to add/remove keyword on all subscriptions. People who are subscribed to packages with the cvs keyword and which do not wish to receive the mails sent to the new derivatives keyword can send one of those commands to [EMAIL PROTECTED] to deactivate this last keyword in all their subscriptions: keywordall - derivatives keywordall [EMAIL PROTECTED] - derivatives On the contrary people who want to have the derivatives keyword on all their subscriptions can use one of those commands: keywordall + derivatives keywordall [EMAIL PROTECTED] + derivatives This is so cool that I immediately went and did this... ... only to find out that it did this for debian-installer only (for which I'm subscribed to the 'cvs' keyword) rather than all my own packages (as I'd expected). Now of course I could go through all my packages and manually subscribe to the derivatives keyword for each, but that's going to require me to remember to set the derivatives keyword for any future package that I start maintaining. Would it be possible to implement something like a 'keywordmaint' command to set the keyword subscriptions for any current and future packages maintained by a given maintainer? -- Fun will now commence -- Seven Of Nine, Ashes to Ashes, stardate 53679.4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Getting the buildds to notice new architectures in a package
On Tue, Jul 18, 2006 at 09:56:22AM +0200, Goswin von Brederlow wrote: Two things: - control files are part of the source. w-b would have to download and unpack every source package to get that file. Exactly. - control files can be auto generated during build (e.g. glibc) and might not even list the packages and architectures Well, yeah, but if that changes anything about the control file that is of importance (like supported architectures or package names), then this information is quite blatantly ignored. And the build may fail. -- Fun will now commence -- Seven Of Nine, Ashes to Ashes, stardate 53679.4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: greylisting on debian.org?
On Tue, Jul 18, 2006 at 09:47:13AM +0200, Lionel Elie Mamane wrote: On Tue, Jul 18, 2006 at 12:47:49AM +0200, Josselin Mouette wrote: * Exim sender/callout fails with a fatal error. Fatal means not temporary? Yes. It means exim did this to one of the MX hosts listed for the domain: EHLO hostname MAIL FROM: RCPT TO:address to be tested QUIT and received a 5xx error in reply to the RCPT TO: line (not 4xx). -- Fun will now commence -- Seven Of Nine, Ashes to Ashes, stardate 53679.4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bits from the Package Tracking System
(btw, why was there a Mail-Followup-To: d-d-a?) Raphael Hertzog [EMAIL PROTECTED] wrote: The maintainer can thus subscribe to this specific keyword and be informed when Ubuntu introduces changes to their Debian package. Is there any documentation about which keywords the address in the Maintainer field of a package is subscribed to by default? Is it the same set that is described as default in http://www.debian.org/doc/manuals/developers-reference/ch-resources.en.html#s-pkg-tracking-system, in other words the maintainer has to explicitly subscribe to the services upload-binary, cvs, ddtp and derivatives? TIA, Frank -- Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive)
Re: Bits from the Package Tracking System
On Mon, Jul 17, 2006 at 06:59:41PM -0300, Gustavo Franco wrote: Is an archive of those mails available somewhere? This way the small patches will be available even for packages of people not subscribed to the PTS. Or for people who subscribe after some version has been uploaded to ubuntu. https://lists.ubuntu.com/archives/ubuntu-patches/ I think having those patches sorted by per-package would be more usefull. Thus there could be a link on the packages.qa.debian.org/source page to these patches. But this is a great start. Now we just need to pressure Linspire, Xandros and friends to produce similar feeds. (Or write a big-brother script to monitor them ;) Cheers, Riku -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bits from the Package Tracking System
also sprach Wouter Verhelst [EMAIL PROTECTED] [2006.07.18.1157 +0200]: Would it be possible to implement something like a 'keywordmaint' command to set the keyword subscriptions for any current and future packages maintained by a given maintainer? The keywords are actually more a filter, so if you have derivatives on for an email and you subscribe with that email to a new package, you'll get the derivatives mails. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system health? what good is your health when you're otherwise an idiot? -- theodor w. adorno signature.asc Description: Digital signature (GPG/PGP)
Re: Bits from the Package Tracking System
On Tue, Jul 18, 2006 at 01:04:06PM +0200, martin f krafft wrote: also sprach Wouter Verhelst [EMAIL PROTECTED] [2006.07.18.1157 +0200]: command to set the keyword subscriptions for any current and future packages maintained by a given maintainer? The keywords are actually more a filter, so if you have derivatives on for an email and you subscribe with that email to a new package, you'll get the derivatives mails. This doesn't seem to answer Wouter question, or ... I'm misreading the PTS documentation. Each subscription subscribe you to a given (source) package. Keywords are actually a filter, but filter notification for a given package. Wouter was asking about a subscription that let you subscribe to all packages of a given maintainer e-mail address (of course with late-binding of the set of packages). This is something I'm very interested to have as well, but I don't think it is actually implemented. Cheers. -- Stefano Zacchiroli -*- Computer Science PhD student @ Uny Bologna, Italy [EMAIL PROTECTED],debian.org,bononia.it} -%- http://www.bononia.it/zack/ If there's any real truth it's that the entire multidimensional infinity of the Universe is almost certainly being run by a bunch of maniacs. -!- signature.asc Description: Digital signature
Greylisting: discussion should stop here, for now (Re: greylisting on debian.org?)
Apart from the fact that the opinions seem to be set (and haven't really changed since the last time the discussion came up IIRC, so we really can stop arguing - nothing new for quite some time...): am I correct in my observation that nobody who has participated in this discussion up to now is involved in Debian email administration? I had a quick look at http://www.debian.org/intro/organization, but I didn't really check all names. So even if the discussion leans in favor of greylisting on RBL (SBL+XBL? Or also DUL, spamcop, ...?): is there any chance of this getting anywhere? cheers -- vbi -- Computer programmers don't byte, they nibble a bit. pgp9ga3YUdUgE.pgp Description: PGP signature
Re: Bits from the Package Tracking System
also sprach Stefano Zacchiroli [EMAIL PROTECTED] [2006.07.18.1318 +0200]: Each subscription subscribe you to a given (source) package. Keywords are actually a filter, but filter notification for a given package. No, you can have filters per email and filters per email/package tuple to override the former. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system it isn't pollution that's harming the environment. it's the impurities in our air and water that are doing it. - dan quayle signature.asc Description: Digital signature (GPG/PGP)
Re: Greylisting: discussion should stop here, for now (Re: greylisting on debian.org?)
Le mar 18 juillet 2006 13:20, Adrian von Bidder a écrit : Apart from the fact that the opinions seem to be set (and haven't really changed since the last time the discussion came up IIRC, so we really can stop arguing - nothing new for quite some time...): am I correct in my observation that nobody who has participated in this discussion up to now is involved in Debian email administration? I had a quick look at http://www.debian.org/intro/organization, but I didn't really check all names. For the record (it was already said in the thread IIRC), the setup we are discussing is in production on alioth since sth like 4 or 5 monthes now (maybe a bit less) on my idea, and thanks to Raphael Hertzog for actually using his alioth admin hat to put it together. so as a matter of a fact, yes, I've already worked in a way so that such solutions can be implemented where there is reachable and listening people to work with. So even if the discussion leans in favor of greylisting on RBL (SBL+XBL? Or also DUL, spamcop, ...?): is there any chance of this getting anywhere? I'm not sure the DSA team is a very open one, if I'm mistaken, then take that mail as an official application request, either for a temporary delegation (or for a more permanent thing) to work on implementing more efficient mail delivery on debian MX'es. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpzougW7nRbL.pgp Description: PGP signature
Re: Bits from the Package Tracking System
On Tue, Jul 18, 2006 at 01:36:47PM +0200, martin f krafft wrote:
also sprach Stefano Zacchiroli [EMAIL PROTECTED] [2006.07.18.1318 +0200]:
Each subscription subscribe you to a given (source) package. Keywords
are actually a filter, but filter notification for a given package.
No, you can have filters per email and filters per email/package
tuple to override the former.
I think you're referring to the following commands of the PTS email
interface:
keyword [email] {+|-|=} list of keywords
keyword sourcepackage [email] {+|-|=} list of keywords
You're right in stating that you can filter both per email and
email/package, but the subscriptions are per-package.
If I'm wrong, could you please point me to where is documented where I
can subscribe to all packages with Maintainer: [EMAIL PROTECTED] so that
when I upload a new package to the archive I will be subscribed to it
without having to chat again with the PTS? That's what was asked by
Wouter at the beginning of this thread, I believe.
Cheers.
--
Stefano Zacchiroli -*- Computer Science PhD student @ Uny Bologna, Italy
[EMAIL PROTECTED],debian.org,bononia.it} -%- http://www.bononia.it/zack/
If there's any real truth it's that the entire multidimensional infinity
of the Universe is almost certainly being run by a bunch of maniacs. -!-
signature.asc
Description: Digital signature
flash drive automount.
Dear Debian Developers, I have a 512MB DataTraveller Flash Disk. It is automounted under ubuntu but fails to automount under debian. Has ubuntu patched things up to get this result? Can this not be achieved under debian? There is no problem automounting other kinds to flash/thumb drivers! 90% of them work/automount. I get a little strange kind of log (as follows) when debian fails to automont flash drives. $ /sbin/fdisk -l -- --- Disk /dev/sda: 513 MB, 513802240 bytes 16 heads, 32 sectors/track, 1960 cylinders Units = cylinders of 512 * 512 = 262144 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 1960 501744 e W95 FAT16 (LBA) Disk /dev/sda1: 2082.3 GB, 2082317979648 bytes 16 heads, 32 sectors/track, 7943412 cylinders Units = cylinders of 512 * 512 = 262144 bytes Device Boot Start End Blocks Id System /dev/sda1p1 * 1 1960 501744 e W95 FAT16 (LBA) --- $ tail -f /var/log/messages --- Jul 14 16:45:29 localhost kernel: usb 5-8: new high speed USB device using ehci_hcd and address 6 Jul 14 16:45:29 localhost kernel: scsi6 : SCSI emulation for USB Mass Storage devices Jul 14 16:45:34 localhost kernel: Vendor: Kingston Model: DataTraveler 2.0 Rev: 1.04 Jul 14 16:45:34 localhost kernel: Type: Direct-Access ANSI SCSI revision: 00 Jul 14 16:45:34 localhost kernel: SCSI device sda: 1003520 512-byte hdwr sectors (514 MB) Jul 14 16:45:34 localhost kernel: sda: Write Protect is off Jul 14 16:45:34 localhost kernel: SCSI device sda: 1003520 512-byte hdwr sectors (514 MB) Jul 14 16:45:34 localhost kernel: sda: Write Protect is off Jul 14 16:45:34 localhost kernel: sda: [CUMANA/ADFS] sda15sd 6:0:0:0: Attached scsi removable disk sda ___ Please suggest. Regards Basanta [EMAIL PROTECTED]
Re: Recent sid amd64 rpath oddity?
Simon Huggins [EMAIL PROTECTED] writes: Hi, On the 3rd May I built libxfce4util and generated libxfce4util2_4.3.90.1-1_amd64.deb. This is in the archive exactly as I built it. It has a couple of lintian failures that I missed and have since been fixed in our SVN. Upstream have released recently and whilst checking these packages more thoroughly I've fixed up the lintian errors but I've also built the new package and I noticed that it's defining an rpath. So I rooted around and tried to work out why but couldn't really work it out. Upstream's libtool and autotools looked recent to me. If I relibtoolize though this does go away. Out of curiousity I rebuilt the previous package i.e. 4.3.90.1-1 again from the same source files as before but with current sid and this time it fails with two extra lintian warnings: W: libxfce4util2: binary-or-shlib-defines-rpath ./usr/lib/libxfce4util.so.2.1.0 /usr/lib W: libxfce4util2: binary-or-shlib-defines-rpath ./usr/sbin/xfce4-kiosk-query /usr/lib If I rebuild the same package on i386 current sid then I don't get the rpath installed. I guess I have several questions: - how can the same source package over a few months build differently in this way? - am I really going to have to relibtoolize every xfce package before I upload or make them do it themselves? :-/ - how evil is an rpath on /usr/lib anyway? I'd welcome any testers on amd64 or not and on recent sid or not to narrow this down. Or any clues as to how on earth this can happen. If you do want to relibtoolize then install xfce4-dev-ools and run xdt-autogen in the package dirrectory. Your package, or more likely libtool, has different ideas about what amd64 system library dirs are to what debian has. Other distributions use /usr/lib64 and debian has /usr/lib. That confuses libtool into adding a rpath. The fix is to force libtool to never ever use rpath. If you can't get libtool to leave well enough alone then use 'chrpath -d'. With rpath your package will afaik break when the library moves, e.g. to /usr/lib64 for biarch systems as we use at my workplace, or the multiarch /usr/lib/x86_64-linux-gnu directory. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Getting the buildds to notice new architectures in a package
Wouter Verhelst [EMAIL PROTECTED] writes: On Tue, Jul 18, 2006 at 09:56:22AM +0200, Goswin von Brederlow wrote: Two things: - control files are part of the source. w-b would have to download and unpack every source package to get that file. Exactly. - control files can be auto generated during build (e.g. glibc) and might not even list the packages and architectures Well, yeah, but if that changes anything about the control file that is of importance (like supported architectures or package names), then this information is quite blatantly ignored. And the build may fail. Aeh, the only part that MUST not change is the source entry in debian/control. Any binary entry is afaik only used by tools forked from debian/rules (usualy dh_*). If you create the binary entries before you use them then everything works. Look at glibc for an example. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: flash drive automount.
Basanta Shrestha wrote: Dear Debian Developers, I have a 512MB DataTraveller Flash Disk. It is automounted under ubuntu but fails to automount under debian. Has ubuntu patched things up to get this result? Can this not be achieved under debian? There is no problem automounting other kinds to flash/thumb drivers! 90% of them work/automount. Automounting of fat/vfat formatted usb drives is disabled in Debian. See the comments at the top of /etc/usbmount for the reasons. Colin -- Colin Tuckley | [EMAIL PROTECTED] | PGP/GnuPG Key Id +44(0)1903 236872 | +44(0)7799 143369 | 0x1B3045CE Heisenberg may have slept here -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: flash drive automount.
Le mercredi 19 juillet 2006 à 00:36 +0545, Basanta Shrestha a écrit : Dear Debian Developers, I have a 512MB DataTraveller Flash Disk. It is automounted under ubuntu but fails to automount under debian. Has ubuntu patched things up to get this result? Can this not be achieved under debian? If it happens only with some drives and not others, this is most probably a kernel issue. Every new version includes workarounds for more or less broken hardware. You can get a more recent kernel for sarge at backports.org. -- .''`. Josselin Mouette/\./\ : :' : [EMAIL PROTECTED] `. `'[EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom
Re: These new diffs are great, but...
On Fri 30 Jun 2006, Martin Schulze wrote:
You know that you can easily turn off this feature by adjusting apt.conf:
Acquire::Pdiffs { false; };
Ah, great :)
After not having done aptitude update for a month or so, after
downloading all the hunderds (!) of diffs, I got the following dreaded
message again:
E: Dynamic MMap ran out of room
E: Read error - read (14 Bad address)
E: The package lists or status file could not be parsed or opened.
E: Dynamic MMap ran out of room
E: Read error - read (14 Bad address)
E: The package lists or status file could not be parsed or opened.
I thought that this was something from bygone days... pretty dismal,
having such a fixed limit on an amd64 with 2GB of memory.
After adding APT::Cache-Limit 2000; in /etc/apt/apt.conf
(the old example of 8MB wasn't enough) it proceeded, and now I don't
need that anymore. The high memory need was apparently related to
processing all those diffs.
Paul Slootman
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#378734: ITP: axtls -- TLSv1 SSL library designed for embedded platforms
Package: wnpp Severity: wishlist Owner: Roberto Lumbreras [EMAIL PROTECTED] * Package name: axtls Version : 1.01 Upstream Author : Cameron Rich [EMAIL PROTECTED] * URL : http://www.axtls.co.nr/ * License : LGPL Description : TLSv1 SSL library designed for embedded platforms axTLS is a highly configurable client/server TLSv1 SSL library designed for embedded platforms. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-k7 Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#378746: ITP: chameleon-cursor-theme -- a modern but not gaudy X11 mouse theme
Package: wnpp
Severity: wishlist
Owner: Adam Borowski [EMAIL PROTECTED]
* Package name: chameleon-cursor-theme [1]
Version : 0.5-1
Upstream Author : Giuseppe Benigno ebengio (at) gmail.com
* URL :
http://www.{gnome,kde,xfce[2]}-look.org/content/show.php?content=38459
* License : GPL
Description : a modern but not gaudy X11 mouse theme
Package comes with 15 different mouse themes for X11.
5 colors (anthracite, sky blue, dark sky blue, white, pearl)
3 different sizes (small, regular and large)
.
Preview: http://www.kde-look.org/content/show.php?content=38459
The default, industrial-cursor-theme, comes in just one size. The two
other good themes we have, comixcursors and crystalcursors are really
compatible only with desktop themes matching .*k.*. xcursor-themes
are only so-so, so adding one more package won't hurt...
Speaking from a more complete point of view, the only themes worth
being packaged left on http://www.foo-look.org are perhaps silver and
yellowdot -- the rest is either redundant or ugly. Of course, you do
know that my opinion is the highest authority in the realm of
aesthethics.
[1]. Should I stick to *-cursor-theme or *cursors? Or keep the
upstream name, chameleon Xcursors?
[2]. Alas, they don't seem to support WindowMaker or BlackBox :p
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bits from the Package Tracking System
also sprach Stefano Zacchiroli [EMAIL PROTECTED] [2006.07.18.1452 +0200]: If I'm wrong, could you please point me to where is documented where I can subscribe to all packages with Maintainer: [EMAIL PROTECTED] so that when I upload a new package to the archive I will be subscribed to it without having to chat again with the PTS? That's what was asked by Wouter at the beginning of this thread, I believe. Ah, then I misunderstood. However, what you are trying to do will hopefully soon be unnecessary as there are plans to auto-subscribe maintainers to the PTS and redirecting @packages.d.o mail there. Raphael has more details, but some are here: http://wiki.debian.org/qa.debian.org/pts -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system it usually takes more than three weeks to prepare a good impromptu speech. -- mark twain signature.asc Description: Digital signature (GPG/PGP)
Re: Bits from the Package Tracking System
Re: Wouter Verhelst 2006-07-18 [EMAIL PROTECTED] On the contrary people who want to have the derivatives keyword on all their subscriptions can use one of those commands: keywordall + derivatives keywordall [EMAIL PROTECTED] + derivatives This is so cool that I immediately went and did this... ... only to find out that it did this for debian-installer only (for which I'm subscribed to the 'cvs' keyword) rather than all my own packages (as I'd expected). This was fixed by Raphaël earlier today; try again. It will now also update the default list of keywords for packages you haven't specified any keywords for when you subscribed. (For the details, look in master:/org/packages*/db/*.db) Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: greylisting on debian.org?
Josselin Mouette [EMAIL PROTECTED] writes: I have refused greylisting for a long time for that exact reason. However the setup Pierre Habouzit describes does not delay most of legitimate mail. Frankly, the remaining delays are sporadic and one can live with them. What bothers me is that we hear it never delays legitimate mail! and then well, ok, it delays some. If the anti-spam advocates consistently said our measures impose such-and-such a cost, but we think it's worth it, I would be delighted. But what I seem to hear is not that. It's hey, this imposes no costs! or spam is evil, so any cost is worth bearing to fight it! Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: greylisting on debian.org?
Stephen Gran [EMAIL PROTECTED] writes: This one time, at band camp, Thomas Bushnell BSG said: And finally, if we don't care about standards conformance, I have said that a good second-best is to document exactly what our requirements are, rather than burying them in apparent secrecy. What standards, exactly? Can you be specific? I have seen you assert this several times, but I see nothing in the RFCs preventing a site from saying it has a temporary local problem when it doesn't. You've been asked this before in response to your assertion, and haven't answered. So the meaning of 4xx is temporary local problem. Sending that when you don't have a temporary local problem is a violation, right there. Must the standard repeat after every sentence, oh, and don't lie. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: greylisting on debian.org?
Adam Borowski [EMAIL PROTECTED] writes: Even worse, there's nothing preventing a site from saying it has a temporary local problem when it _does_. Thus, if your mail server can't handle retrying, it will drop mail every time something is not in perfect working order. And hardware or network failures are something to be expected. Any legitimate server must support retrying. For any reason. Yes, and this is not the point. The point is that the standard does *not* say that the retry must come from the same place, or even anything like the same place. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: greylisting on debian.org?
[EMAIL PROTECTED] (Marco d'Itri) writes: On Jul 17, Thomas Bushnell BSG [EMAIL PROTECTED] wrote: Still, if you think it's just nitpicking, then why not ask the IETF to amend the standard to clearly permit this practice? Because there is no reason to do this, this is not a standard issue but plain operations. Really? So you think the IETF would happily issue a statement agreeing? Of course, the facts are that the IETF regards graylisting as a violation of the email protocols and not to be implemented. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Greylisting: discussion should stop here, for now (Re: greylisting on debian.org?)
Pierre Habouzit [EMAIL PROTECTED] writes: For the record (it was already said in the thread IIRC), the setup we are discussing is in production on alioth since sth like 4 or 5 monthes now (maybe a bit less) on my idea, and thanks to Raphael Hertzog for actually using his alioth admin hat to put it together. Can you document on the relevant web page exactly how the graylisting works and what specific things get blocked and when? Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: greylisting on debian.org?
On Tue, Jul 18, 2006, Thomas Bushnell BSG wrote: If the anti-spam advocates consistently said our measures impose such-and-such a cost, but we think it's worth it, I would be delighted. the measures impose a cost, but we think it's worth it Can we get greylisting now? -- Loïc Minier [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: greylisting on debian.org?
On Jul 18, Thomas Bushnell BSG [EMAIL PROTECTED] wrote: Because there is no reason to do this, this is not a standard issue but plain operations. Really? So you think the IETF would happily issue a statement agreeing? Yes. Of course, the facts are that the IETF regards graylisting as a violation of the email protocols and not to be implemented. When (and how?) did the IETF express such an opinion? -- ciao, Marco signature.asc Description: Digital signature
Re: greylisting on debian.org?
On Jul 18, Thomas Bushnell BSG [EMAIL PROTECTED] wrote: Yes, and this is not the point. The point is that the standard does *not* say that the retry must come from the same place, or even anything like the same place. The point is that in the real world nobody cares that this is not specified in a standard. -- ciao, Marco signature.asc Description: Digital signature
Re: greylisting on debian.org?
Loïc Minier [EMAIL PROTECTED] writes: On Tue, Jul 18, 2006, Thomas Bushnell BSG wrote: If the anti-spam advocates consistently said our measures impose such-and-such a cost, but we think it's worth it, I would be delighted. the measures impose a cost, but we think it's worth it Can you detail what the cost is for the specific procedures in use on Debian's servers? No, because you are apparently unaware it exists already. But yet, without knowing the cost, you are sure it's worth it. Bah. Can we get greylisting now? We have it, duh. Have you not been paying attention? Thomas
Re: Bits from the Package Tracking System
On Mon, Jul 17, 2006 at 10:39:18PM +0200, Raphael Hertzog wrote: Hello everybody, here are some news about the latest changes made to the Package Tracking System. New derivatives keyword --- The PTS will be used to relay informations from derivative distributions. Therefore, a new keyword derivatives has been implemented. By default, a PTS subscriber won't receive the messages associated to this keyword unless he has already manually activated the cvs keyword (i.e. the set of users having the derivatives keyword has been initialized as the set of users having the cvs keyword because those people can read patches and are most probably interested in them). So by default it is assumed that I should make Ubuntu's work and dig into these patches to see if some pieces should be applied into Debian? No thanks, I am getting tired of all those Debian developers who are more interested in improving Ubuntu than Debian, and just added the following rules to my .procmailrc: :0 * ^From.*(ubuntu|canonical).com /dev/null Denis, pissed off PS: No, I am not joking -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bits from the Package Tracking System
On 7/18/06, Denis Barbier [EMAIL PROTECTED] wrote: On Mon, Jul 17, 2006 at 10:39:18PM +0200, Raphael Hertzog wrote: Hello everybody, here are some news about the latest changes made to the Package Tracking System. New derivatives keyword --- The PTS will be used to relay informations from derivative distributions. Therefore, a new keyword derivatives has been implemented. By default, a PTS subscriber won't receive the messages associated to this keyword unless he has already manually activated the cvs keyword (i.e. the set of users having the derivatives keyword has been initialized as the set of users having the cvs keyword because those people can read patches and are most probably interested in them). So by default it is assumed that I should make Ubuntu's work and dig into these patches to see if some pieces should be applied into Debian? No thanks, I am getting tired of all those Debian developers who are more interested in improving Ubuntu than Debian, and just added the following rules to my .procmailrc: [...] No, this is just a service. If you want to dig into these patches, you need to subscribe, otherwise you can live without them like you did until now, didn't you? Please, think before replying my message and who you're hitting with your anger. regards, -- stratus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Greylisting: discussion should stop here, for now (Re: greylisting on debian.org?)
Le mar 18 juillet 2006 21:26, Thomas Bushnell BSG a écrit : Pierre Habouzit [EMAIL PROTECTED] writes: For the record (it was already said in the thread IIRC), the setup we are discussing is in production on alioth since sth like 4 or 5 monthes now (maybe a bit less) on my idea, and thanks to Raphael Hertzog for actually using his alioth admin hat to put it together. Can you document on the relevant web page exactly how the graylisting works and what specific things get blocked and when? I've already gived numbers in the thread (even graphs), for a similar setup. I don't have access to alioth logs, but the setup is world readable, log on alioth and read it ;) Moreover, as there is quite few valid aliases, alioth greylist do not takes care of the recipient in account for the greylisting, but only the MAIL FROM + SENDER IP, which a good trade off for alioth, but may not be true for DD accounts. that's the sole deviation of what has been discussed here, and is not very relevant to the discussion anyway. Technically, I don't know what you want me to say more than what is explained on my blog and in that thread (or in alioth's world readable exim.conf). Moreover I don't see what value the 6 or 7 mails that you posted less than 1 hour ago, in the same quarter, answering to at least half of the most recents posts in the thread, have made the discussion make any progress. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgp2b0E7CPZll.pgp Description: PGP signature
Re: Bits from the Package Tracking System
On Tue, Jul 18, 2006 at 05:33:45PM -0300, Gustavo Franco wrote: On 7/18/06, Denis Barbier [EMAIL PROTECTED] wrote: On Mon, Jul 17, 2006 at 10:39:18PM +0200, Raphael Hertzog wrote: Hello everybody, here are some news about the latest changes made to the Package Tracking System. New derivatives keyword --- The PTS will be used to relay informations from derivative distributions. Therefore, a new keyword derivatives has been implemented. By default, a PTS subscriber won't receive the messages associated to this keyword unless he has already manually activated the cvs keyword (i.e. the set of users having the derivatives keyword has been initialized as the set of users having the cvs keyword because those people can read patches and are most probably interested in them). So by default it is assumed that I should make Ubuntu's work and dig into these patches to see if some pieces should be applied into Debian? No thanks, I am getting tired of all those Debian developers who are more interested in improving Ubuntu than Debian, and just added the following rules to my .procmailrc: [...] No, this is just a service. If you want to dig into these patches, you need to subscribe, otherwise you can live without them like you did until now, didn't you? No, I have to unsubscribe, this is exactly what upsets me. There are also cases where messages will be sent to lists, like http://lists.debian.org/debian-dpkg/2006/07/msg00021.html So my procmail rule is the best option. Denis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bits from the Package Tracking System
Denis Barbier [EMAIL PROTECTED] wrote: So by default it is assumed that I should make Ubuntu's work and dig into these patches to see if some pieces should be applied into Debian? No thanks, I am getting tired of all those Debian developers who are more interested in improving Ubuntu than Debian, and just added the following rules to my .procmailrc: How does dropping potentially useful patches improve Debian? -- Matthew Garrett | [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Congrats to the ftpmasters
The NEW queue is down to *22* packages, which is totally unheard of. Only three packages have been waiting longer than a month -- so Javier's package is no longer in the 'endless wait' state. At the same time, the RM bugs are in fairly good shape, and clearly removals are also being processed pretty well. Meanwhile, infrastructure work appears to still be progressing. (The substantial bugs are all very new.) Impressive. :-) As an aside, bug 248043 looks fixed to me, so I closed it. :-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bits from the Package Tracking System
On 7/18/06, Denis Barbier [EMAIL PROTECTED] wrote: On Tue, Jul 18, 2006 at 05:33:45PM -0300, Gustavo Franco wrote: On 7/18/06, Denis Barbier [EMAIL PROTECTED] wrote: On Mon, Jul 17, 2006 at 10:39:18PM +0200, Raphael Hertzog wrote: Hello everybody, here are some news about the latest changes made to the Package Tracking System. New derivatives keyword --- The PTS will be used to relay informations from derivative distributions. Therefore, a new keyword derivatives has been implemented. By default, a PTS subscriber won't receive the messages associated to this keyword unless he has already manually activated the cvs keyword (i.e. the set of users having the derivatives keyword has been initialized as the set of users having the cvs keyword because those people can read patches and are most probably interested in them). So by default it is assumed that I should make Ubuntu's work and dig into these patches to see if some pieces should be applied into Debian? No thanks, I am getting tired of all those Debian developers who are more interested in improving Ubuntu than Debian, and just added the following rules to my .procmailrc: [...] No, this is just a service. If you want to dig into these patches, you need to subscribe, otherwise you can live without them like you did until now, didn't you? No, I have to unsubscribe, this is exactly what upsets me. There are also cases where messages will be sent to lists, like http://lists.debian.org/debian-dpkg/2006/07/msg00021.html So my procmail rule is the best option. I think you were subscribed using the 'cvs' keyword, right? cvs CVS commit notifications, if the package has a CVS repository and the maintainer has set up forwarding commit notifications to the PTS. Source: http://www.debian.org/doc/developers-reference/ch-resources.en.html#s-pkg-tracking-system If it's ok for you dig into these patches that you or somebody else (other maintainer) is forwarding to the PTS but not dig into patches coming from derivatives, i'm sorry but you will need to unsubscribe. The intention was the best possible, really. regards, -- stratus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Congrats to the ftpmasters
On Tue, 2006-07-18 at 16:57 -0400, Nathanael Nerode wrote: The NEW queue is down to *22* packages, which is totally unheard of. Only three packages have been waiting longer than a month -- so Javier's package is no longer in the 'endless wait' state. Agreed, I've uploaded three new packages in the last fortnight, and all of them were in the archive by the next day. Yay ftpmasters! Ross -- Ross Burton mail: [EMAIL PROTECTED] jabber: [EMAIL PROTECTED] www: http://www.burtonini.com./ PGP Fingerprint: 1A21 F5B0 D8D0 CFE3 81D4 E25A 2D09 E447 D0B4 33DF signature.asc Description: This is a digitally signed message part
Re: Congrats to the ftpmasters
On 7/18/06, Nathanael Nerode [EMAIL PROTECTED] wrote: The NEW queue is down to *22* packages, which is totally unheard of. Only three packages have been waiting longer than a month -- so Javier's package is no longer in the 'endless wait' state. At the same time, the RM bugs are in fairly good shape, and clearly removals are also being processed pretty well. Meanwhile, infrastructure work appears to still be progressing. (The substantial bugs are all very new.) Impressive. :-) As an aside, bug 248043 looks fixed to me, so I closed it. :-) Yes, i blogged about this a week ago. Congrats to the ftpmaster, assistants and the other people involved in this again! thanks, -- stratus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
lilypond and python
I have been criticized for not uploading the new lilypond packages and being quite a bit behind the public releases. Unfortunately, the current lilypond requires python 2.4, and expects to call it as python, not just in the build process, but at run time. I had been assuming that the python team was telling me the truth when they said that python-defaults would be updated to 2.4 very soon. Indeed, the relevant wishlist bug on python 2.4 has been marked pending for some time now, which seems to be not quite the truth. Perhaps it's not a lie, but I have no way to judge and have been stymied by the utter lack of responsiveness by the python team in response to queries. If the python team had told me, months ago, that it would be months before python-defaults was updated, I would have then begun work on a workaround for lilypond. But I was trusting that it was really a quick matter, at least, that's what people told me. Unfortunately, the python-defaults maintainer ignores all mail on the subject. So, let me make plain: I am entirely happy to accept a workaround patch for lilypond's current upstream stable release that will make it build and use python 2.4 even when that is not installed as python. If such a functional patch appears and is mailed to the appropriate lilypond bug, it would immediately become a high priority matter for me to upload it. I have wanted to do so for months. But I don't alas, have the time to spend on a workaround patch myself, which will (supposedly) become obselete very quickly. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
minimizing downtime of a daemon
One of the template NM questions is about how to minimize the downtime of a daemon during package upgrade (in maintainer scripts). ssh does an /etc/init.d/ssh restart in postinstall, which (with luck) means that there will be *no* downtime. This doesn't seem to be necessary for allowing ssh upgrades, since running /etc/init.d/ssh stop over an ssh connection doesn't disconnect existing ssh connections, but only prevents establishing new connections until the next start. This is different from how everybody else seems to do it, but does accomplish the goal. But, Debian doesn't seem to do actively persue this goal. Of course, apt-get install daemon-package should always work, and really minimize the downtime, but doesn't solve the general problem for the dist-upgrade case, or for apt-get install many-packages, where it would be a small pain to have to figure out which packages are running daemons. The service isn't actually guaranteed to work during the upgrade anyway, even if it isn't stopped, due to the potential for inconsistencies between files on disk (eg. changed config file format, reread at each connection by a daemon child process, or interrelated files). Packages using debhelper dh_installinit end up with an /etc/init.d/foo stop in prerm and an /etc/init.d/foo start in postinst . During eg. a dist-upgrade, a maximal number of packages are dpkg --unpacked, and afterwards are dpkg --configured. This decidedly does *not* minimize daemon downtime, since it allows an arbitrarily large number of packages to be unpacked and configured before the daemon is restarted. debhelper intends to do what's needed with a simple interface. If it was acceptable to require more package-specific information, it would be possible to only stop the service if it wasn't provided by the new version of the package. (Since binary packages with multiple daemons are uncommon, it is more realistic to think of the same scenario with info documents, which also get registered in postinst, and deregistered in prerm). debhelper would then need an interface to specify that a daemon was included in certain previous versions of the package, and removed at some critical versions. Or, versions in which a daemon is removed (and versions between that version and the next stable release) could be required to have custom, not-generated maintscripts. This is an uncommon problem for daemons, but removal of info documents is much more frequent, and presents the same trouble. The implementation would involve the following in preinst (*not* prerm, since it may not be known in advance that those files/daemons would be removed): ver_removed=1.2-3 ( [ $1 = install ] || [ $1 = upgrade ] ) dpkg --compare-versions $2 lt $ver_removed deregister_info stop_server ... # postrm abort-[install|upgrade] should re-register them, and restart # the server. With this code, the info document and server will always be available *during* upgrades of earlier versions, since dpkg uses an atomic rename(). Upgrading to the critical version correctly stops the server and deregisters the document *before* it is removed. I'm particularly interested in this question since I'm writing a document about dpkg, and, in particular, about use of maintainer scripts. I'm going through NM, and (so far) haven't been asked about this. If you don't want to spoil the fun for other NM's, you might reply to me personally, or think of the same question phrased in terms of info documents and dh_installdocs instead of daemon's and dh_installinit. Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: greylisting on debian.org?
This one time, at band camp, Thomas Bushnell BSG said: Loïc Minier [EMAIL PROTECTED] writes: On Tue, Jul 18, 2006, Thomas Bushnell BSG wrote: If the anti-spam advocates consistently said our measures impose such-and-such a cost, but we think it's worth it, I would be delighted. the measures impose a cost, but we think it's worth it Can you detail what the cost is for the specific procedures in use on Debian's servers? No, because you are apparently unaware it exists already. But yet, without knowing the cost, you are sure it's worth it. Bah. The specific cost right now is that we have load averages on master in excess of 300. Fairly consistently. Greylisting promises to ease that load by quite a bit. It imposes a small cost: some legitimate mail that doesn't meet whatever criteria is decided on (rDNS, RBL, whatever) will be delayed. None will be rejected by this measure, unless the sending site itself can't be bothered with RFC compliance. That doesn't bother me that much. If it bothers you, use your non-Debian email address for all your package related work, and hardly any of your mail will pass through master. And I notice you still haven't been able to come up with anything resembling a link for your earlier assertions. Can we take it as read that they were, in fact, unfounded? Can we get greylisting now? We have it, duh. Have you not been paying attention? We don't have it yet. Have you not been paying attention? The only delay we have now is due to spam clogged queues and load. -- - | ,''`.Stephen Gran | | : :' :[EMAIL PROTECTED] | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
gnucash on alpha
There is a grave bug (#378346) filed against gnucash on alpha which seems to be quite arch specific. Mail to the debian-alpha team for assistance has not been answered (though I have been told that the team is very small). Is there someone with access to an alpha that will look at this bug, and perhaps provide a stack trace? AFAICT there is no developer alpha machine available at present. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: greylisting on debian.org?
This one time, at band camp, Thomas Bushnell BSG said: So the meaning of 4xx is temporary local problem. Sending that when you don't have a temporary local problem is a violation, right there. Must the standard repeat after every sentence, oh, and don't lie. Actually, that's just the error message most MTA's give out. The RFC has finer grained meanings for the range of 4xx messages. Would you be happier if greylisting gave back a 451 (error in processing)? This is factually true - processing began, but one of the preconditions failed. That is not a lie. You might want to go back and reread the RFCs about all of this. Most of what you are saying isn't actually in the RFCs, but is part of the mythology that has grown up around them. Try to find 'be liberal in what you accept ... ' in RFC 2821. Notice also that local site policy _always_ trumps the RFC, but with a note to the effect that you _should_ (not must) take care to not violate interoperability when implementing site policy. I would argue greylisting doesn't violate interoperability. But maybe you have another assertion. -- - | ,''`.Stephen Gran | | : :' :[EMAIL PROTECTED] | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Accepted adduser 3.95 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Jul 2006 05:33:02 + Source: adduser Binary: adduser Architecture: source all Version: 3.95 Distribution: unstable Urgency: low Maintainer: Debian Adduser Developers [EMAIL PROTECTED] Changed-By: Marc Haber [EMAIL PROTECTED] Description: adduser- Add and remove users and groups Closes: 378539 Changes: adduser (3.95) unstable; urgency=low . * Apply Tobias' last patch correctly. This again Closes: #378539 Files: 4f396eedebe33a06d891e93f60d8df4a 645 admin important adduser_3.95.dsc 4fd93daa8ebbf97627a081c4f293618a 220441 admin important adduser_3.95.tar.gz f5390858a466511e076c6a6ced1bfb16 141650 admin important adduser_3.95_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEvHQOgZalRGu6PIQRAns7AKCxTr5J+Tl83ZUGphm+2UKCOIuz0wCdGqM7 JetDKNs4V3dpdwlxqGc39HY= =Jh7c -END PGP SIGNATURE- Accepted: adduser_3.95.dsc to pool/main/a/adduser/adduser_3.95.dsc adduser_3.95.tar.gz to pool/main/a/adduser/adduser_3.95.tar.gz adduser_3.95_all.deb to pool/main/a/adduser/adduser_3.95_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mdadm 2.5.2-7 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Jul 2006 07:15:35 +0200 Source: mdadm Binary: mdadm mdadm-udeb Architecture: source amd64 Version: 2.5.2-7 Distribution: unstable Urgency: low Maintainer: Debian mdadm maintainers [EMAIL PROTECTED] Changed-By: martin f. krafft [EMAIL PROTECTED] Description: mdadm - tool to administer Linux MD device arrays (software RAID) mdadm-udeb - tool to administer Linux MD device arrays (software RAID) (udeb) Changes: mdadm (2.5.2-7) unstable; urgency=low . * Release to unstable. Files: fa0b41eb2e31f27c242d907ac6db1b77 712 admin optional mdadm_2.5.2-7.dsc 3f561f892839d29cb4090d90ad503901 64927 admin optional mdadm_2.5.2-7.diff.gz b390d5eb65f300f498997b758f71d82d 157872 admin optional mdadm_2.5.2-7_amd64.deb 04ef49bbad1284b4d1521237502ca4f0 70218 debian-installer optional mdadm-udeb_2.5.2-7_amd64.udeb Package-Type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEvHuHIgvIgzMMSnURArYyAJ9doTYSfYkGQRLgtIV+AFxdLpDW5QCeK7kk HdNMHHlScHsQDge1LiSS0po= =i1S4 -END PGP SIGNATURE- Accepted: mdadm-udeb_2.5.2-7_amd64.udeb to pool/main/m/mdadm/mdadm-udeb_2.5.2-7_amd64.udeb mdadm_2.5.2-7.diff.gz to pool/main/m/mdadm/mdadm_2.5.2-7.diff.gz mdadm_2.5.2-7.dsc to pool/main/m/mdadm/mdadm_2.5.2-7.dsc mdadm_2.5.2-7_amd64.deb to pool/main/m/mdadm/mdadm_2.5.2-7_amd64.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted python-qt4 4.0.1-1 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 16 Jul 2006 12:15:35 +0200 Source: python-qt4 Binary: python-qt4-gl pyqt4-dev-tools python-qt4-dev python-qt4-doc python-qt4-sql python-qt4 Architecture: source all i386 Version: 4.0.1-1 Distribution: unstable Urgency: low Maintainer: Torsten Marek [EMAIL PROTECTED] Changed-By: Torsten Marek [EMAIL PROTECTED] Description: pyqt4-dev-tools - Development tools for PyQt4 python-qt4 - Python bindings for Qt4 python-qt4-dev - Development files for PyQt4 python-qt4-doc - Documentation and examples for PyQt4 python-qt4-gl - Python bindings for Qt4's OpenGL module python-qt4-sql - Python bindings for Qt4's SQL module Closes: 378086 Changes: python-qt4 (4.0.1-1) unstable; urgency=low . * New upstream release (Closes: #378086) Files: bd5eeae276e31aae356a0448720b07b2 794 python optional python-qt4_4.0.1-1.dsc a85e8b9074a4c3b135142caaaf0804a6 4656786 python optional python-qt4_4.0.1.orig.tar.gz 43ce4152b06aeb67919f8b12971e9417 5680 python optional python-qt4_4.0.1-1.diff.gz 981fe72dc1fc0b5196e02a2f979a4a58 3039874 python optional python-qt4_4.0.1-1_i386.deb 0dc464e87fdf10bae6723dac6cb94415 107764 python optional python-qt4-gl_4.0.1-1_i386.deb 9148cdffeb3963deefe71d9fbdb6dfb9 194670 python optional python-qt4-sql_4.0.1-1_i386.deb 8ae57a68ce8534c13d26acf58dcf759c 127524 python optional pyqt4-dev-tools_4.0.1-1_i386.deb a28ac78ea1d102017473e771fc7b5302 194692 python optional python-qt4-dev_4.0.1-1_all.deb 28fcfbb14370987d793ece8045b2e897 698068 doc optional python-qt4-doc_4.0.1-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEvJOBfMVFHqJEyFgRAo6EAJ9XpK4WZSCVyUF6qF4iKzfL3NIungCgpthI VARzmS7HYDxA8pm50Eq4cmI= =6xha -END PGP SIGNATURE- Accepted: pyqt4-dev-tools_4.0.1-1_i386.deb to pool/main/p/python-qt4/pyqt4-dev-tools_4.0.1-1_i386.deb python-qt4-dev_4.0.1-1_all.deb to pool/main/p/python-qt4/python-qt4-dev_4.0.1-1_all.deb python-qt4-doc_4.0.1-1_all.deb to pool/main/p/python-qt4/python-qt4-doc_4.0.1-1_all.deb python-qt4-gl_4.0.1-1_i386.deb to pool/main/p/python-qt4/python-qt4-gl_4.0.1-1_i386.deb python-qt4-sql_4.0.1-1_i386.deb to pool/main/p/python-qt4/python-qt4-sql_4.0.1-1_i386.deb python-qt4_4.0.1-1.diff.gz to pool/main/p/python-qt4/python-qt4_4.0.1-1.diff.gz python-qt4_4.0.1-1.dsc to pool/main/p/python-qt4/python-qt4_4.0.1-1.dsc python-qt4_4.0.1-1_i386.deb to pool/main/p/python-qt4/python-qt4_4.0.1-1_i386.deb python-qt4_4.0.1.orig.tar.gz to pool/main/p/python-qt4/python-qt4_4.0.1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted countrycodes 1.0.5-1.1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Jul 2006 10:23:41 +0200 Source: countrycodes Binary: countrycodes Architecture: source i386 Version: 1.0.5-1.1 Distribution: unstable Urgency: low Maintainer: Ola Lundqvist [EMAIL PROTECTED] Changed-By: Amaya Rodrigo Sastre [EMAIL PROTECTED] Description: countrycodes - ISO 3166 country code finder Closes: 378646 Changes: countrycodes (1.0.5-1.1) unstable; urgency=low . * Non-maintainer upload. * Get rid of the /usr/doc link in postinst (Closes: #378646). Files: 93afc39d49ee34e2c9868900e53f13ad 582 utils optional countrycodes_1.0.5-1.1.dsc 6f393a5137ec41e5e9846216bcc82f8f 3301 utils optional countrycodes_1.0.5-1.1.diff.gz 9d3557cc0b2b9bf21880ddd065b176d7 15016 utils optional countrycodes_1.0.5-1.1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEvJriNFDtUT/MKpARAo3vAKDTrCALOzHMKY8SgOYYqD0Q3GnjLgCg1o68 dRCWG+j5AgteqkqL3bSBIUo= =yCpC -END PGP SIGNATURE- Accepted: countrycodes_1.0.5-1.1.diff.gz to pool/main/c/countrycodes/countrycodes_1.0.5-1.1.diff.gz countrycodes_1.0.5-1.1.dsc to pool/main/c/countrycodes/countrycodes_1.0.5-1.1.dsc countrycodes_1.0.5-1.1_i386.deb to pool/main/c/countrycodes/countrycodes_1.0.5-1.1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted less 394-3 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Jul 2006 11:16:11 +0200 Source: less Binary: less Architecture: source i386 Version: 394-3 Distribution: unstable Urgency: low Maintainer: Thomas Schoepf [EMAIL PROTECTED] Changed-By: Thomas Schoepf [EMAIL PROTECTED] Description: less - Pager program similar to more Closes: 358704 Changes: less (394-3) unstable; urgency=low . * Print a message when catdoc or isoinfo are not installed. Closes: #358704: lesspipe: treat catdoc and isoinfo like other helper programs * debian/control: Updated Standards-Version to 3.7.2. No changes needed. Files: 9a6fb1b1fabd028e834f69d11724d438 570 text standard less_394-3.dsc ff30f83f37e721395ba3a7b13bfa6f4e 15554 text standard less_394-3.diff.gz e4502b6b48348fa9f2d23e9e26f91113 111066 text standard less_394-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iEYEARECAAYFAkS8p00ACgkQBL31vrD6T0lYFgCdHvymr9SNR7W+8p3NY8phoSpb IjEAoJwF59GOtVbP0JVkyvBVnnOWnsfV =jpBv -END PGP SIGNATURE- Accepted: less_394-3.diff.gz to pool/main/l/less/less_394-3.diff.gz less_394-3.dsc to pool/main/l/less/less_394-3.dsc less_394-3_i386.deb to pool/main/l/less/less_394-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gmp 2:4.2.1+dfsg-2.2 (source all amd64 i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Jul 2006 02:06:44 +0200 Source: gmp Binary: libgmp3-dev libgmp3-doc libgmp3c2 libgmpxx4 Architecture: source all amd64 i386 Version: 2:4.2.1+dfsg-2.2 Distribution: unstable Urgency: high Maintainer: Steve M. Robbins [EMAIL PROTECTED] Changed-By: Steinar H. Gunderson [EMAIL PROTECTED] Description: libgmp3-dev - Multiprecision arithmetic library developers tools libgmp3-doc - Multiprecision arithmetic library example code libgmp3c2 - Multiprecision arithmetic library libgmpxx4 - Multiprecision arithmetic library (C++ bindings) Changes: gmp (2:4.2.1+dfsg-2.2) unstable; urgency=high . * Non-maintainer upload. * Don't replace i386 by i486 in DEB_HOST_ARCH. Doh; fixes FTBFS on i386. Files: e8061c84a585c5eec04ad74b118329d6 665 libs optional gmp_4.2.1+dfsg-2.2.dsc d4b97b020e2532e0f1c518ea111b2ca4 118724 libs optional gmp_4.2.1+dfsg-2.2.diff.gz 1ea906abd38614701007ce5e8c8f0cf7 339460 doc optional libgmp3-doc_4.2.1+dfsg-2.2_all.deb 9a246c5e4b8e55c31e7515c67c418825 404464 libs optional libgmp3c2_4.2.1+dfsg-2.2_amd64.deb 60f67e3f47ad8b548c4cf68a993766c0 217192 libs optional libgmpxx4_4.2.1+dfsg-2.2_amd64.deb 377f6029709ae7b700279eee66d0 493338 libdevel optional libgmp3-dev_4.2.1+dfsg-2.2_amd64.deb ffd5136454f2e7842fc46f5ba1446948 429566 libs optional libgmp3c2_4.2.1+dfsg-2.2_i386.deb 611523f2e79c78b755de1d8e02b9f8b8 216986 libs optional libgmpxx4_4.2.1+dfsg-2.2_i386.deb 7600658c867c27431426bee8af4f68ed 510834 libdevel optional libgmp3-dev_4.2.1+dfsg-2.2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEvKbtXKRQ3lK3SH4RAhoSAKCkilNEv94uVy9P1y4fQGwpCXV1HQCg6e0I HnoW7ABdNYuBau6wIG6sp8c= =N1N/ -END PGP SIGNATURE- Accepted: gmp_4.2.1+dfsg-2.2.diff.gz to pool/main/g/gmp/gmp_4.2.1+dfsg-2.2.diff.gz gmp_4.2.1+dfsg-2.2.dsc to pool/main/g/gmp/gmp_4.2.1+dfsg-2.2.dsc libgmp3-dev_4.2.1+dfsg-2.2_amd64.deb to pool/main/g/gmp/libgmp3-dev_4.2.1+dfsg-2.2_amd64.deb libgmp3-dev_4.2.1+dfsg-2.2_i386.deb to pool/main/g/gmp/libgmp3-dev_4.2.1+dfsg-2.2_i386.deb libgmp3-doc_4.2.1+dfsg-2.2_all.deb to pool/main/g/gmp/libgmp3-doc_4.2.1+dfsg-2.2_all.deb libgmp3c2_4.2.1+dfsg-2.2_amd64.deb to pool/main/g/gmp/libgmp3c2_4.2.1+dfsg-2.2_amd64.deb libgmp3c2_4.2.1+dfsg-2.2_i386.deb to pool/main/g/gmp/libgmp3c2_4.2.1+dfsg-2.2_i386.deb libgmpxx4_4.2.1+dfsg-2.2_amd64.deb to pool/main/g/gmp/libgmpxx4_4.2.1+dfsg-2.2_amd64.deb libgmpxx4_4.2.1+dfsg-2.2_i386.deb to pool/main/g/gmp/libgmpxx4_4.2.1+dfsg-2.2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted python-apt 0.6.18-0.2 (source i386)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 18 Jul 2006 11:39:52 +0200
Source: python-apt
Binary: python-apt
Architecture: source i386
Version: 0.6.18-0.2
Distribution: unstable
Urgency: low
Maintainer: APT Development Team deity@lists.debian.org
Changed-By: Christoph Berg [EMAIL PROTECTED]
Description:
python-apt - Python interface to libapt-pkg
Closes: 377615
Changes:
python-apt (0.6.18-0.2) unstable; urgency=low
.
* Non-maintainer upload.
* Add ${shlibs:Depends} and ${misc:Depends} (Closes: #377615).
Files:
a479c17e5cdf7d37acbf63be64542716 691 python optional python-apt_0.6.18-0.2.dsc
bd8864c0977d1cf5b44428ce960ed491 61503 python optional
python-apt_0.6.18-0.2.tar.gz
c5c62d81379ee9da598d8f80066c7f5e 133360 python optional
python-apt_0.6.18-0.2_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFEvK9vxa93SlhRC1oRAqmfAKCAY+GszfLmA7FdRwvCV3bOHAnAGQCcCdPA
cviaOMn+248D5Biey8Jm5D8=
=gVOh
-END PGP SIGNATURE-
Accepted:
python-apt_0.6.18-0.2.dsc
to pool/main/p/python-apt/python-apt_0.6.18-0.2.dsc
python-apt_0.6.18-0.2.tar.gz
to pool/main/p/python-apt/python-apt_0.6.18-0.2.tar.gz
python-apt_0.6.18-0.2_i386.deb
to pool/main/p/python-apt/python-apt_0.6.18-0.2_i386.deb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted hwinfo 13.0-4 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Jul 2006 11:23:17 +0200 Source: hwinfo Binary: libhd13-dev libhd13 hwinfo Architecture: source i386 Version: 13.0-4 Distribution: unstable Urgency: low Maintainer: Morten Werner Olsen [EMAIL PROTECTED] Changed-By: Morten Werner Olsen [EMAIL PROTECTED] Description: hwinfo - Hardware identification system libhd13- Hardware identification system library libhd13-dev - Hardware identification system library and headers Closes: 378653 Changes: hwinfo (13.0-4) unstable; urgency=low . * Patch src/hd/kbd.c to not include asm/kbio.h or use KIOC* defines (thanks to Clint Adams). (Closes: #378653) Files: af133bda4147d9727ad3150497b68c75 679 admin optional hwinfo_13.0-4.dsc 86481141f48b6539e6b4cbb3eca6a50e 10308 admin optional hwinfo_13.0-4.diff.gz d61a27bcec577ba4a77042489cfa0fe2 39822 admin optional hwinfo_13.0-4_i386.deb add218cc48ee831992ce37b146cb294f 557910 libs optional libhd13_13.0-4_i386.deb 90bd4c06d079e1b80babfcfb701c06af 642918 libdevel optional libhd13-dev_13.0-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD4DBQFEvK/Dw951rgNrq40RAjgEAKDVkSnosR86Ub0E90IV22FU61fn9ACXSx/o X8Qs4BT9UMVb3J7R1Kf18Q== =Wk81 -END PGP SIGNATURE- Accepted: hwinfo_13.0-4.diff.gz to pool/main/h/hwinfo/hwinfo_13.0-4.diff.gz hwinfo_13.0-4.dsc to pool/main/h/hwinfo/hwinfo_13.0-4.dsc hwinfo_13.0-4_i386.deb to pool/main/h/hwinfo/hwinfo_13.0-4_i386.deb libhd13-dev_13.0-4_i386.deb to pool/main/h/hwinfo/libhd13-dev_13.0-4_i386.deb libhd13_13.0-4_i386.deb to pool/main/h/hwinfo/libhd13_13.0-4_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libtexttools 2.0.3-3.1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Jul 2006 11:54:12 +0200 Source: libtexttools Binary: libtexttools2 libtexttools-dev Architecture: source i386 Version: 2.0.3-3.1 Distribution: unstable Urgency: high Maintainer: Ludovic Brenta [EMAIL PROTECTED] Changed-By: Steinar H. Gunderson [EMAIL PROTECTED] Description: libtexttools-dev - Ada and C++ library for writing console applications libtexttools2 - Ada and C++ library for writing console applications Closes: 377721 Changes: libtexttools (2.0.3-3.1) unstable; urgency=high . * Non-maintainer upload. * Rebuild with gnat-4.1. (Closes: #377721) * Remove build-dependency on gnat ( 3.16). * Set CFLAGS to -O2 -g. * Remove obsolete local variables from the bottom of the changelog. Files: 75afee228d148d0b700df321b4d62d60 720 - optional libtexttools_2.0.3-3.1.dsc a576663ff074d28bf91ab8ff7e8342f7 4111 - optional libtexttools_2.0.3-3.1.diff.gz f26e615b21c6f494ef4464725bb1d29a 776778 libdevel optional libtexttools-dev_2.0.3-3.1_i386.deb dc38ede53bbe15616e5c9083cff1f66e 205578 libs optional libtexttools2_2.0.3-3.1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEvLLpXKRQ3lK3SH4RArLKAJ9ESY6Qze7Jwxe+ZbggFTmosjC3VgCfTbTP eNLmgZsdWrlaKo94TpClkM4= =fox0 -END PGP SIGNATURE- Accepted: libtexttools-dev_2.0.3-3.1_i386.deb to pool/main/libt/libtexttools/libtexttools-dev_2.0.3-3.1_i386.deb libtexttools2_2.0.3-3.1_i386.deb to pool/main/libt/libtexttools/libtexttools2_2.0.3-3.1_i386.deb libtexttools_2.0.3-3.1.diff.gz to pool/main/libt/libtexttools/libtexttools_2.0.3-3.1.diff.gz libtexttools_2.0.3-3.1.dsc to pool/main/libt/libtexttools/libtexttools_2.0.3-3.1.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libapache2-mod-ifier 0.7-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Jul 2006 11:11:43 + Source: libapache2-mod-ifier Binary: libapache2-mod-ifier Architecture: source i386 Version: 0.7-1 Distribution: unstable Urgency: low Maintainer: Steve Kemp [EMAIL PROTECTED] Changed-By: Steve Kemp [EMAIL PROTECTED] Description: libapache2-mod-ifier - Filter and reject incoming client requests Changes: libapache2-mod-ifier (0.7-1) unstable; urgency=low . * New upstream release. - No longer convert 404 responses to 200. - Added documentation in the mod_ifier-handler output page. Files: daacedd1a3e892ac1b13817c3cea71bd 614 web optional libapache2-mod-ifier_0.7-1.dsc 8285e152c3640858392d94d836537119 18908 web optional libapache2-mod-ifier_0.7.orig.tar.gz c40a9e8aa07eccdf1033e9938ef94d9a 5716 web optional libapache2-mod-ifier_0.7-1.diff.gz 521ae19c5ee24994a7d6a04bae04b95a 18446 web optional libapache2-mod-ifier_0.7-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD4DBQFEvLQwwM/Gs81MDZ0RAkWFAJdjqim5HKECTlrIM4Duq7RhhoUrAJ9os8mY Fk7O/Kcn+7a5ZBDfZ+gqMQ== =fz6C -END PGP SIGNATURE- Accepted: libapache2-mod-ifier_0.7-1.diff.gz to pool/main/liba/libapache2-mod-ifier/libapache2-mod-ifier_0.7-1.diff.gz libapache2-mod-ifier_0.7-1.dsc to pool/main/liba/libapache2-mod-ifier/libapache2-mod-ifier_0.7-1.dsc libapache2-mod-ifier_0.7-1_i386.deb to pool/main/liba/libapache2-mod-ifier/libapache2-mod-ifier_0.7-1_i386.deb libapache2-mod-ifier_0.7.orig.tar.gz to pool/main/liba/libapache2-mod-ifier/libapache2-mod-ifier_0.7.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted xboard 4.2.7-6.1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Jul 2006 12:46:49 +0200 Source: xboard Binary: xboard Architecture: source i386 Version: 4.2.7-6.1 Distribution: unstable Urgency: low Maintainer: Alexander L. Belikoff [EMAIL PROTECTED] Changed-By: Amaya Rodrigo Sastre [EMAIL PROTECTED] Description: xboard - An X Window System Chess Board Closes: 378649 Changes: xboard (4.2.7-6.1) unstable; urgency=low . * Non-maintainer upload. * Get rid of the /usr/doc link in postinst (Closes: #378649). * Upgraded config.guess and config.sub Files: ee0d568a156fabdac4b8ee156b6dacbd 629 games optional xboard_4.2.7-6.1.dsc e2425adf215c729503926aca84ce65e5 12358 games optional xboard_4.2.7-6.1.diff.gz 8d3a500d37ea7b3a3ce4fa4eee703191 519320 games optional xboard_4.2.7-6.1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEvLx+NFDtUT/MKpARAoJOAJ9Oh1bxmu3NvGveX4DKEXq0pnAIBgCfVkwE BwmzXXUg+oTJJSa4eZFJzXw= =2VyL -END PGP SIGNATURE- Accepted: xboard_4.2.7-6.1.diff.gz to pool/main/x/xboard/xboard_4.2.7-6.1.diff.gz xboard_4.2.7-6.1.dsc to pool/main/x/xboard/xboard_4.2.7-6.1.dsc xboard_4.2.7-6.1_i386.deb to pool/main/x/xboard/xboard_4.2.7-6.1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted redhat-cluster 1.02.00-7.1 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Jul 2006 12:35:01 +0200 Source: redhat-cluster Binary: libmagma-dev libcman-dev ccs gnbd-server libdlm1 libiddev-dev fence magma-plugin-sm libcman1 magma-plugin-gulm cman gulm redhat-cluster-source libgulm-dev gfs-tools libgulm1 gnbd-client libmagma1 libdlm-dev libccs-dev Architecture: source i386 all Version: 1.02.00-7.1 Distribution: unstable Urgency: high Maintainer: Bastian Blank [EMAIL PROTECTED] Changed-By: Steinar H. Gunderson [EMAIL PROTECTED] Description: ccs- Cluster configuration system cman - Cluster manager fence - I/O fencing system gfs-tools - Global File System - management tools gnbd-client - Global network block device - client tools gnbd-server - Global network block device - server tools gulm - Server-based unified cluster/lock manager for GFS libccs-dev - Cluster configuration system - development files libcman-dev - Cluster manager - development files libcman1 - Cluster manager - library libdlm-dev - Distributed lock manager - development files libdlm1- Distributed lock manager - library libgulm-dev - Server-based unified cluster/lock manager for GFS libgulm1 - Server-based unified cluster/lock manager for GFS libiddev-dev - Device identification libmagma-dev - Cluster abstraction - development files libmagma1 - Cluster abstraction - development files magma-plugin-gulm - Cluster abstraction - gulm plugin magma-plugin-sm - Cluster abstraction - sm plugin redhat-cluster-source - Redhat cluster suite - kernel module source Closes: 377791 Changes: redhat-cluster (1.02.00-7.1) unstable; urgency=high . * Non-maintainer upload. * Add versioned dependency on libsysfs-dev, as we need at least upstream version 2.0.0 (set to and test with the version currently in testing to be sure); fixes FTBFS. (Closes: #377791) Files: 4baf851022345542f2bb28894ea8987a 935 admin optional redhat-cluster_1.02.00-7.1.dsc 41e782b422c87a0553bb7c9579ea84bd 8157 admin optional redhat-cluster_1.02.00-7.1.diff.gz c878337ffcb8630005699eba5203c366 51996 admin optional ccs_1.02.00-7.1_i386.deb d11f3df060aaa8911e79c34ec27e0db5 5498 libdevel optional libccs-dev_1.02.00-7.1_i386.deb c36173fca49b98bd92a0c57ea19fc386 23192 admin optional cman_1.02.00-7.1_i386.deb 887c15885cea8d801761a9d1694dc490 6026 admin optional libcman1_1.02.00-7.1_i386.deb bc4efc2873cc33136894ebbd0d4ea662 8694 libdevel optional libcman-dev_1.02.00-7.1_i386.deb c129d412c0567c4401c2a6077a89441a 10850 libs optional libdlm1_1.02.00-7.1_i386.deb 5b0c69b685672ca533c2631c8c44214f 12302 libdevel optional libdlm-dev_1.02.00-7.1_i386.deb 6501eec7cffc8f374002c23d7ec7909d 93550 admin optional fence_1.02.00-7.1_i386.deb c10cd2def3f63545fefef42ba9d9c8f8 220868 admin optional gfs-tools_1.02.00-7.1_i386.deb ef288e42ae557374ee51854b522be85f 40572 admin optional gnbd-client_1.02.00-7.1_i386.deb eaad8fae85304f8e36c2f2a62c575fef 40256 admin optional gnbd-server_1.02.00-7.1_i386.deb f5cda7c131c15da29cea894b793192cf 100038 admin optional gulm_1.02.00-7.1_i386.deb d16d5c6948488f1b95989473de5aedb5 11460 admin optional libgulm1_1.02.00-7.1_i386.deb a43937d4b9c16a47545433b463a9789f 13474 admin optional libgulm-dev_1.02.00-7.1_i386.deb 2ca51e2febd964ea74308aa0249285ec 5050 libdevel optional libiddev-dev_1.02.00-7.1_i386.deb adb7d4a142722df15c5be11da1bb 19630 libdevel optional libmagma1_1.02.00-7.1_i386.deb 2ea9e0e17ccf0928acd93cda9c8a7b7b 23366 libdevel optional libmagma-dev_1.02.00-7.1_i386.deb 79188b137490aab057285fcd3589dd24 7548 admin optional magma-plugin-gulm_1.02.00-7.1_i386.deb 4208291cd11c1076f81ca67ff5170348 9172 admin optional magma-plugin-sm_1.02.00-7.1_i386.deb 3e44ca33d260e0a896a50cf32a8b4f69 354858 admin optional redhat-cluster-source_1.02.00-7.1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEvLqNXKRQ3lK3SH4RAhS2AJwMDCg2TLAmfS8vnz4ODfwkw/psXACgriIM wX0UynNwvW52+Z3S7dj13xA= =x3yZ -END PGP SIGNATURE- Accepted: ccs_1.02.00-7.1_i386.deb to pool/main/r/redhat-cluster/ccs_1.02.00-7.1_i386.deb cman_1.02.00-7.1_i386.deb to pool/main/r/redhat-cluster/cman_1.02.00-7.1_i386.deb fence_1.02.00-7.1_i386.deb to pool/main/r/redhat-cluster/fence_1.02.00-7.1_i386.deb gfs-tools_1.02.00-7.1_i386.deb to pool/main/r/redhat-cluster/gfs-tools_1.02.00-7.1_i386.deb gnbd-client_1.02.00-7.1_i386.deb to pool/main/r/redhat-cluster/gnbd-client_1.02.00-7.1_i386.deb gnbd-server_1.02.00-7.1_i386.deb to pool/main/r/redhat-cluster/gnbd-server_1.02.00-7.1_i386.deb gulm_1.02.00-7.1_i386.deb to pool/main/r/redhat-cluster/gulm_1.02.00-7.1_i386.deb libccs-dev_1.02.00-7.1_i386.deb to pool/main/r/redhat-cluster/libccs-dev_1.02.00-7.1_i386.deb libcman-dev_1.02.00-7.1_i386.deb to pool/main/r/redhat-cluster/libcman-dev_1.02.00-7.1_i386.deb libcman1_1.02.00-7.1_i386.deb to pool/main/r/redhat-cluster/libcman1_1.02.00-7.1_i386.deb
Accepted phpmyadmin 4:2.8.2-0.1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Jul 2006 12:52:19 +0200 Source: phpmyadmin Binary: phpmyadmin Architecture: source all Version: 4:2.8.2-0.1 Distribution: unstable Urgency: high Maintainer: Piotr Roszatycki [EMAIL PROTECTED] Changed-By: Steinar H. Gunderson [EMAIL PROTECTED] Description: phpmyadmin - set of PHP-scripts to administrate MySQL over the WWW Closes: 377748 Changes: phpmyadmin (4:2.8.2-0.1) unstable; urgency=high . * Non-maintainer upload. * New upstream release. * Fixes cross-site-scripting issues. [CVE-2006-3388] (Closes: #377748) Files: ce8b2d6d3ee90b00c00faacddc0df880 638 web extra phpmyadmin_2.8.2-0.1.dsc 9397ee05642ce16c95a556c08b57983d 3455642 web extra phpmyadmin_2.8.2.orig.tar.gz a953a755d254e1e89bd6a5c64a70ca12 39051 web extra phpmyadmin_2.8.2-0.1.diff.gz 8a7bc99e6ce39bdc0dd922928a62506c 3607104 web extra phpmyadmin_2.8.2-0.1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEvL5WXKRQ3lK3SH4RAmYcAJ44LlW+EO7RGbdMzAZftur9bNsIvQCg57fJ wJ88DA9Hn9pvBwOyMZbRXlw= =0Fzb -END PGP SIGNATURE- Accepted: phpmyadmin_2.8.2-0.1.diff.gz to pool/main/p/phpmyadmin/phpmyadmin_2.8.2-0.1.diff.gz phpmyadmin_2.8.2-0.1.dsc to pool/main/p/phpmyadmin/phpmyadmin_2.8.2-0.1.dsc phpmyadmin_2.8.2-0.1_all.deb to pool/main/p/phpmyadmin/phpmyadmin_2.8.2-0.1_all.deb phpmyadmin_2.8.2.orig.tar.gz to pool/main/p/phpmyadmin/phpmyadmin_2.8.2.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted xmms-wma 1.0.5-3 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Jul 2006 11:24:26 +0800 Source: xmms-wma Binary: xmms-wma beep-media-player-wma Architecture: source i386 Version: 1.0.5-3 Distribution: unstable Urgency: low Maintainer: Wei Mingzhi [EMAIL PROTECTED] Changed-By: Wei Mingzhi [EMAIL PROTECTED] Description: beep-media-player-wma - WMA input plugin for Beep Media Player xmms-wma - WMA input plugin for XMMS Closes: 378370 Changes: xmms-wma (1.0.5-3) unstable; urgency=low . * patches/01-ffmpeg-arch.dpatch: Added to fix compiling issue on non-x86 architectures. (closes: #378370) Files: b14f98676f672c927a1a74d839895e1a 634 sound optional xmms-wma_1.0.5-3.dsc f61f2085684910c0a8128fc6eb80bf43 2364 sound optional xmms-wma_1.0.5-3.diff.gz d3473b03c8b972e2fba5e4f20940abe8 67636 sound optional xmms-wma_1.0.5-3_i386.deb efef5744cd88ed3ef294f36ab96a978b 67910 sound optional beep-media-player-wma_1.0.5-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEvMGD+C5cwEsrK54RAreGAJ9ZzvWkMAL1onPk13/GZwZP2SWaLgCeK9c6 fm5E8xg786ulVUSw3ndX2hc= =TxqM -END PGP SIGNATURE- Accepted: beep-media-player-wma_1.0.5-3_i386.deb to pool/main/x/xmms-wma/beep-media-player-wma_1.0.5-3_i386.deb xmms-wma_1.0.5-3.diff.gz to pool/main/x/xmms-wma/xmms-wma_1.0.5-3.diff.gz xmms-wma_1.0.5-3.dsc to pool/main/x/xmms-wma/xmms-wma_1.0.5-3.dsc xmms-wma_1.0.5-3_i386.deb to pool/main/x/xmms-wma/xmms-wma_1.0.5-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted redhat-cluster 1.02.00-8 (source all s390)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Jul 2006 13:54:31 +0200 Source: redhat-cluster Binary: libmagma-dev libcman-dev ccs gnbd-server libdlm1 libiddev-dev fence magma-plugin-sm libcman1 magma-plugin-gulm cman gulm redhat-cluster-source libgulm-dev gfs-tools libgulm1 gnbd-client libmagma1 libdlm-dev libccs-dev Architecture: source s390 all Version: 1.02.00-8 Distribution: unstable Urgency: low Maintainer: Bastian Blank [EMAIL PROTECTED] Changed-By: Bastian Blank [EMAIL PROTECTED] Description: ccs- Cluster configuration system cman - Cluster manager fence - I/O fencing system gfs-tools - Global File System - management tools gnbd-client - Global network block device - client tools gnbd-server - Global network block device - server tools gulm - Server-based unified cluster/lock manager for GFS libccs-dev - Cluster configuration system - development files libcman-dev - Cluster manager - development files libcman1 - Cluster manager - library libdlm-dev - Distributed lock manager - development files libdlm1- Distributed lock manager - library libgulm-dev - Server-based unified cluster/lock manager for GFS libgulm1 - Server-based unified cluster/lock manager for GFS libiddev-dev - Device identification libmagma-dev - Cluster abstraction - development files libmagma1 - Cluster abstraction - development files magma-plugin-gulm - Cluster abstraction - gulm plugin magma-plugin-sm - Cluster abstraction - sm plugin redhat-cluster-source - Redhat cluster suite - kernel module source Closes: 378677 Changes: redhat-cluster (1.02.00-8) unstable; urgency=low . * NACK NMU (closes: #378677) * Port to 2.6.17 Files: a564a0c855365d64ea31b8311e55d2df 926 admin optional redhat-cluster_1.02.00-8.dsc ecf018b3918556c91b89b4e48fc07ae8 9408 admin optional redhat-cluster_1.02.00-8.diff.gz 6b9a8366b80591e1582d2ca0c2a1adc2 54458 admin optional ccs_1.02.00-8_s390.deb f465114baee900f70a4074a5e1a8f27c 5676 libdevel optional libccs-dev_1.02.00-8_s390.deb cf80345018bd35ea00293522efa08814 24462 admin optional cman_1.02.00-8_s390.deb 84ae8a1a6dcc5522b5b1b4fd55f4ea50 6294 libs optional libcman1_1.02.00-8_s390.deb beaca09081e539afde28a550e6a29a83 8914 libdevel optional libcman-dev_1.02.00-8_s390.deb 6572b6e7a62ecf8cd3247d0fb5950b9e 11630 libs optional libdlm1_1.02.00-8_s390.deb cfcbe89b824580ea89c4ac0b780a958a 13288 libdevel optional libdlm-dev_1.02.00-8_s390.deb aec7674269cfd87192262faf86512143 96948 admin optional fence_1.02.00-8_s390.deb 58815919f499a795b3840827ddf952d4 264952 admin optional gfs-tools_1.02.00-8_s390.deb 0ebb8ed502a9dde5e01e5ec0965d0ec3 44470 admin optional gnbd-client_1.02.00-8_s390.deb bacc00f02dfa3fddf42f16b10b1c3d35 42958 admin optional gnbd-server_1.02.00-8_s390.deb 316373049de1c928bd9611d1a20251bd 110008 admin optional gulm_1.02.00-8_s390.deb fb054d8159453b92ee04e292079e12a5 12422 libs optional libgulm1_1.02.00-8_s390.deb e963295f7e795976c6ea036f14a08fce 14584 libdevel optional libgulm-dev_1.02.00-8_s390.deb c6f6c0e3a8fa241fdf6a79713e444730 4936 libdevel optional libiddev-dev_1.02.00-8_s390.deb 9c0adf7c526f5c03a1d57781ead44ed8 24396 libdevel optional libmagma1_1.02.00-8_s390.deb 04483db9ff909c721467fde9b2bef4de 34410 libdevel optional libmagma-dev_1.02.00-8_s390.deb 048f7d5d0bc01fa0af77970565dc044d 9110 admin optional magma-plugin-gulm_1.02.00-8_s390.deb ceaa58a996271f4a203d54fd30a5d6e2 10538 admin optional magma-plugin-sm_1.02.00-8_s390.deb 160e479b9775b3221824819ebec3b8a4 354712 admin optional redhat-cluster-source_1.02.00-8_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iEYEARECAAYFAkS8ziYACgkQLkAIIn9ODhF16ACeNJkvUH9CcLD+OurO5rNC3nVz va0AmwV2yb/7kI9+WP1AS5eqLmJV7G/H =CIOQ -END PGP SIGNATURE- Accepted: ccs_1.02.00-8_s390.deb to pool/main/r/redhat-cluster/ccs_1.02.00-8_s390.deb cman_1.02.00-8_s390.deb to pool/main/r/redhat-cluster/cman_1.02.00-8_s390.deb fence_1.02.00-8_s390.deb to pool/main/r/redhat-cluster/fence_1.02.00-8_s390.deb gfs-tools_1.02.00-8_s390.deb to pool/main/r/redhat-cluster/gfs-tools_1.02.00-8_s390.deb gnbd-client_1.02.00-8_s390.deb to pool/main/r/redhat-cluster/gnbd-client_1.02.00-8_s390.deb gnbd-server_1.02.00-8_s390.deb to pool/main/r/redhat-cluster/gnbd-server_1.02.00-8_s390.deb gulm_1.02.00-8_s390.deb to pool/main/r/redhat-cluster/gulm_1.02.00-8_s390.deb libccs-dev_1.02.00-8_s390.deb to pool/main/r/redhat-cluster/libccs-dev_1.02.00-8_s390.deb libcman-dev_1.02.00-8_s390.deb to pool/main/r/redhat-cluster/libcman-dev_1.02.00-8_s390.deb libcman1_1.02.00-8_s390.deb to pool/main/r/redhat-cluster/libcman1_1.02.00-8_s390.deb libdlm-dev_1.02.00-8_s390.deb to pool/main/r/redhat-cluster/libdlm-dev_1.02.00-8_s390.deb libdlm1_1.02.00-8_s390.deb to pool/main/r/redhat-cluster/libdlm1_1.02.00-8_s390.deb libgulm-dev_1.02.00-8_s390.deb to pool/main/r/redhat-cluster/libgulm-dev_1.02.00-8_s390.deb
Accepted flexml 1.5.2-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Jul 2006 14:06:50 +0200 Source: flexml Binary: flexml Architecture: source i386 Version: 1.5.2-1 Distribution: unstable Urgency: low Maintainer: Martin Quinson [EMAIL PROTECTED] Changed-By: Martin Quinson [EMAIL PROTECTED] Description: flexml - generate fast validating XML processors and applications Changes: flexml (1.5.2-1) unstable; urgency=low . * Bug fix: do find the skeleton file in installed distributions Files: f4079a1b283d34d9cb18fc911c9feb82 703 devel optional flexml_1.5.2-1.dsc e93a027785c2595e1aec927f513ad7ed 71272 devel optional flexml_1.5.2.orig.tar.gz 815a6cdb9c0df1f968b0b2acac78273d 3982 devel optional flexml_1.5.2-1.diff.gz efb0bd989c8c9f45bb5f6af323cc5a4c 68096 devel optional flexml_1.5.2-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEvNJVIiC/MeFF8zQRAjj0AJ9GVXT0e3CUxcJV4saoehLI+BoDkACgr1YM AxV9ywPQwjhQgOpqD9QxvDo= =EVha -END PGP SIGNATURE- Accepted: flexml_1.5.2-1.diff.gz to pool/main/f/flexml/flexml_1.5.2-1.diff.gz flexml_1.5.2-1.dsc to pool/main/f/flexml/flexml_1.5.2-1.dsc flexml_1.5.2-1_i386.deb to pool/main/f/flexml/flexml_1.5.2-1_i386.deb flexml_1.5.2.orig.tar.gz to pool/main/f/flexml/flexml_1.5.2.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted xaralx 0.6r1442-3 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Jul 2006 12:07:52 +0200 Source: xaralx Binary: xaralx Architecture: source i386 Version: 0.6r1442-3 Distribution: unstable Urgency: low Maintainer: Joachim Breitner [EMAIL PROTECTED] Changed-By: Joachim Breitner [EMAIL PROTECTED] Description: xaralx - versatile vector graphic program Changes: xaralx (0.6r1442-3) unstable; urgency=low . * Added automake-1.9-dependecy, to avoid dangling symlinks Files: bef4f328b4367b23a00e0e366bf26e1a 849 non-free/graphics optional xaralx_0.6r1442-3.dsc 3da5a476f77b8fd412ef9b0217ec59a1 5330 non-free/graphics optional xaralx_0.6r1442-3.diff.gz 9ec460bcc649691901de82e424946579 8812612 non-free/graphics optional xaralx_0.6r1442-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iQCVAwUBRLzQvL8Zfhn2SkeXAQJ2hgQApgj0Sqig1Qtl2rUE0ISahAET3+LX/tDM RJhZSmt/LFmb9BA8OOFYQ9TLyyz9mejh4q8XjD22ltTlPr6wJlNEG+7LebycSFeE YfGitoBCyjapSkJRs5qlC70e3eROcYhvRKXNFFEe9gL/OYM3xJHvGtH2Ti+x+wM2 m+30QAOM5qQ= =M0co -END PGP SIGNATURE- Accepted: xaralx_0.6r1442-3.diff.gz to pool/non-free/x/xaralx/xaralx_0.6r1442-3.diff.gz xaralx_0.6r1442-3.dsc to pool/non-free/x/xaralx/xaralx_0.6r1442-3.dsc xaralx_0.6r1442-3_i386.deb to pool/non-free/x/xaralx/xaralx_0.6r1442-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted xruskb 1.15.3-3 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Jul 2006 14:31:29 +0200 Source: xruskb Binary: xruskb Architecture: source i386 Version: 1.15.3-3 Distribution: unstable Urgency: low Maintainer: Debian QA Group [EMAIL PROTECTED] Changed-By: Amaya Rodrigo Sastre [EMAIL PROTECTED] Description: xruskb - An X localized keyboard switch and autolock Closes: 378650 Changes: xruskb (1.15.3-3) unstable; urgency=low . * QA upload. * Get rid of the /usr/doc link in postinst (Closes: #378650). Files: 35603069d68aba64411d868473c34754 589 x11 extra xruskb_1.15.3-3.dsc ddf42322f96ce324ef1e95651234dee3 4437 x11 extra xruskb_1.15.3-3.diff.gz 4deed3bd47da5ad3ac119603ce35b377 91296 x11 extra xruskb_1.15.3-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEvNT4NFDtUT/MKpARAs2QAKCT0ajpn8akfLA7BpssAqCJonJxRQCgp5PV cZZ36wQ84dxyfVDj2a4l5bA= =pvCI -END PGP SIGNATURE- Accepted: xruskb_1.15.3-3.diff.gz to pool/main/x/xruskb/xruskb_1.15.3-3.diff.gz xruskb_1.15.3-3.dsc to pool/main/x/xruskb/xruskb_1.15.3-3.dsc xruskb_1.15.3-3_i386.deb to pool/main/x/xruskb/xruskb_1.15.3-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted aide 0.11.99.20060718-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Jul 2006 15:10:22 + Source: aide Binary: aide aide-config-zg2 Architecture: source i386 Version: 0.11.99.20060718-1 Distribution: experimental Urgency: low Maintainer: Aide Maintainers [EMAIL PROTECTED] Changed-By: Marc Haber [EMAIL PROTECTED] Description: aide - Advanced Intrusion Detection Environment Closes: 244917 247685 369242 370312 377383 378438 Changes: aide (0.11.99.20060718-1) experimental; urgency=low . * NOT RELEASED YET * New post-0.12-rc1 CVS snapshot. * No extra No such file or directory error messages any more. Closes: #247685. * No longer segfaults on --config-check and @@ifnhost. Thanks to Andy Spiegl. Closes: #244917. * Adapt 10-manpages.dpatch * remove all other patches (incorporated upstream) * Update French (fr) debconf translation. Thanks to Christian Perrier. (mh) Closes: #369242 * Update Czech (cs) debconf translation. Thanks to Miroslav Kure. (mh) Closes: #370312 * Fix/Remove paths in FILES section of aide.1 man page. Thanks to Dr. Markus Waldeck. Closes: #377383 * Fix typo in README.Debian. Thanks to Richard van den Berg. Closes: #378438 * Fix syslog rules. Thanks to Richard van den Berg. Files: 205f496d09e33428b2b32f3c64ba8b0f 837 admin optional aide_0.11.99.20060718-1.dsc 2db442d0ba1021c33205fc820b6ec361 279737 admin optional aide_0.11.99.20060718.orig.tar.gz 79dbb96b24b4480e4af9f133f448268f 42790 admin optional aide_0.11.99.20060718-1.diff.gz d2bc0db636734dbd848b81db02153d14 537626 admin optional aide_0.11.99.20060718-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEvQQtgZalRGu6PIQRAvvQAKCdz9Iplt/hFNx+6bCc096LckJDDwCfboUA lZgjM/GwVQlHx/TouwMflTs= =goD1 -END PGP SIGNATURE- Accepted: aide_0.11.99.20060718-1.diff.gz to pool/main/a/aide/aide_0.11.99.20060718-1.diff.gz aide_0.11.99.20060718-1.dsc to pool/main/a/aide/aide_0.11.99.20060718-1.dsc aide_0.11.99.20060718-1_i386.deb to pool/main/a/aide/aide_0.11.99.20060718-1_i386.deb aide_0.11.99.20060718.orig.tar.gz to pool/main/a/aide/aide_0.11.99.20060718.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mpfr 2.2.0.dfsg.1-8 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Jul 2006 15:35:53 +0200 Source: mpfr Binary: libmpfr-dev libmpfr1 Architecture: source i386 Version: 2.2.0.dfsg.1-8 Distribution: unstable Urgency: low Maintainer: Laurent Fousse [EMAIL PROTECTED] Changed-By: Laurent Fousse [EMAIL PROTECTED] Description: libmpfr-dev - multiple precision floating-point computation developers tools libmpfr1 - multiple precision floating-point computation Closes: 378356 Changes: mpfr (2.2.0.dfsg.1-8) unstable; urgency=low . * Newer gcc should be able to compile mpfr on m68k, so drop the dependancy on gcc-3.4 (closes: #378356). Thanks Stephen R Marenka for testing. * Don't try to use GMP's internal header files anymore: we didn't have them all anyway, and they're not strictly needed. * Upgraded Standards-Version to 3.7.2, no change needed. Files: 8a435bcae326ef09d2999f1304a26428 703 math optional mpfr_2.2.0.dfsg.1-8.dsc 35f845cd51a9bc607906db25060763af 70689 math optional mpfr_2.2.0.dfsg.1-8.diff.gz 419c64a09f950925f2e228f66cf00b40 213368 libs optional libmpfr1_2.2.0.dfsg.1-8_i386.deb 2699b34e615b3cc83bbcaa01692c255f 237904 libdevel optional libmpfr-dev_2.2.0.dfsg.1-8_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEvOfgRoAVF6FpbSsRApQLAKCDkPbzufYKYjZhp/hog2BX5xPtdwCgmzcY e67DoMH86RLcTbGZwqt3rb8= =SE0g -END PGP SIGNATURE- Accepted: libmpfr-dev_2.2.0.dfsg.1-8_i386.deb to pool/main/m/mpfr/libmpfr-dev_2.2.0.dfsg.1-8_i386.deb libmpfr1_2.2.0.dfsg.1-8_i386.deb to pool/main/m/mpfr/libmpfr1_2.2.0.dfsg.1-8_i386.deb mpfr_2.2.0.dfsg.1-8.diff.gz to pool/main/m/mpfr/mpfr_2.2.0.dfsg.1-8.diff.gz mpfr_2.2.0.dfsg.1-8.dsc to pool/main/m/mpfr/mpfr_2.2.0.dfsg.1-8.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted console-data 2:1.0-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Jul 2006 14:44:36 +0100 Source: console-data Binary: console-keymaps-dec console-keymaps-mac console-data console-keymaps-usb console-keymaps-at console-keymaps-atari console-keymaps-sun console-keymaps-acorn console-keymaps-amiga Architecture: source all Version: 2:1.0-1 Distribution: unstable Urgency: low Maintainer: Alastair McKinstry [EMAIL PROTECTED] Changed-By: Alastair McKinstry [EMAIL PROTECTED] Description: console-data - Keymaps, fonts, charset maps, fallback tables for console-tools console-keymaps-acorn - Keymaps for Acorn RISC-PC keyboards (udeb) console-keymaps-amiga - Keymaps for Amiga keyboards (udeb) console-keymaps-at - Keymaps for PC-style (PS/2 and AT) keyboards (udeb) console-keymaps-atari - Keymaps for Atari keyboards (udeb) console-keymaps-dec - Keymaps for Dec keyboards (udeb) console-keymaps-mac - Keymaps for Apple keyboards (udeb) console-keymaps-sun - Keymaps for Sun keyboards (udeb) console-keymaps-usb - Keymaps for USB keyboards (udeb) Closes: 375137 375635 378369 378624 Changes: console-data (2:1.0-1) unstable; urgency=low . [ Christian Perrier ] * Translations - Thai corrected. Closes: #375137 - Hungarian updated. Closes: #378369 . [ Alastair McKinstry ] * Change epoch, and make a non-native package again. The date-related version maked a package look old (its not supposed to change much). Making it a non-Debian package isolates the Debian-only changes: translations done to names, etc. * Move to Standards-Version: 3.7.2: no changes required. * Move unicode data into new package unicode-data, which console-data Suggests:, for upgrade simplicity. This trims some MBs from console-data. Closes: #378624. * New console-data source tarball, with the following changes: - Build with Unicode data from unicode-data package, rather than obsolete data provided in tarball. - Fix for regression: re-added handling for missing consolefonts to consolefonts/Makefile*. Closes: #375635. * Add Build-Depends: on unicode-data, which now provides /usr/share/unidata that console-data-20060918 tarball requires. * Build-Depends: rather than Build-Indep-Depends: on dbs and debhelper, as per lintian warning. Files: 212512bfd8b31c48cad8f14be3914f0c 951 utils optional console-data_1.0-1.dsc 38addcb3940b5ba5ebdbbf3369521a56 604208 utils optional console-data_1.0.orig.tar.gz 7fa4a3e0058488e7d0c35c605f1d3838 103601 utils optional console-data_1.0-1.diff.gz b897d890aa989132bce248054dba3252 901444 utils optional console-data_1.0-1_all.deb b38383d2806c08f5d90e6a8e68f1fed0 99456 debian-installer optional console-keymaps-at_1.0-1_all.udeb 0eaae1d0dade8d3474db50c82df7bc78 16238 debian-installer extra console-keymaps-mac_1.0-1_all.udeb ab33184ada914ab02c57f617e5a19fa8 34504 debian-installer extra console-keymaps-sun_1.0-1_all.udeb 91de58b10a327fcd911c27c011727f38 88304 debian-installer extra console-keymaps-acorn_1.0-1_all.udeb ac00786242d5721eeb0d7137ba74a6fd 14720 debian-installer extra console-keymaps-atari_1.0-1_all.udeb cf160da73420a7551f2d71cd76c17d7e 21170 debian-installer extra console-keymaps-amiga_1.0-1_all.udeb 70f0cfbae9a044ec1f95e135ee4c15e3 19552 debian-installer extra console-keymaps-usb_1.0-1_all.udeb 2194ba444a54c912de1ef2c01a59abff 5574 debian-installer extra console-keymaps-dec_1.0-1_all.udeb Package-Type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEvPIEQTK/kCo4XFcRAvwGAJ0W4jxznfO+N+R1/e28SMLkuH9o/QCeLzHB 8zFUazBYDTvUT5NNv+DrokY= =5RWD -END PGP SIGNATURE- Accepted: console-data_1.0-1.diff.gz to pool/main/c/console-data/console-data_1.0-1.diff.gz console-data_1.0-1.dsc to pool/main/c/console-data/console-data_1.0-1.dsc console-data_1.0-1_all.deb to pool/main/c/console-data/console-data_1.0-1_all.deb console-data_1.0.orig.tar.gz to pool/main/c/console-data/console-data_1.0.orig.tar.gz console-keymaps-acorn_1.0-1_all.udeb to pool/main/c/console-data/console-keymaps-acorn_1.0-1_all.udeb console-keymaps-amiga_1.0-1_all.udeb to pool/main/c/console-data/console-keymaps-amiga_1.0-1_all.udeb console-keymaps-at_1.0-1_all.udeb to pool/main/c/console-data/console-keymaps-at_1.0-1_all.udeb console-keymaps-atari_1.0-1_all.udeb to pool/main/c/console-data/console-keymaps-atari_1.0-1_all.udeb console-keymaps-dec_1.0-1_all.udeb to pool/main/c/console-data/console-keymaps-dec_1.0-1_all.udeb console-keymaps-mac_1.0-1_all.udeb to pool/main/c/console-data/console-keymaps-mac_1.0-1_all.udeb console-keymaps-sun_1.0-1_all.udeb to pool/main/c/console-data/console-keymaps-sun_1.0-1_all.udeb console-keymaps-usb_1.0-1_all.udeb to pool/main/c/console-data/console-keymaps-usb_1.0-1_all.udeb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted codespeak-lib 0.7-svn20060621-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Jul 2006 8:44:23 -0300 Source: codespeak-lib Binary: python-codespeak-lib Architecture: source i386 Version: 0.7-svn20060621-1 Distribution: unstable Urgency: low Maintainer: Guilherme Salgado [EMAIL PROTECTED] Changed-By: Guilherme Salgado [EMAIL PROTECTED] Description: python-codespeak-lib - The pylib library containing py.test, greenlets and other nicetie Changes: codespeak-lib (0.7-svn20060621-1) unstable; urgency=low . * New upstream version. * Split the patches inside debian/patches/ and use dpatch. Files: 019d64118a5515fb8deab3dcac4db617 718 python optional codespeak-lib_0.7-svn20060621-1.dsc 70da6173c749f2aa1cb0b0a2c85b4c7a 349737 python optional codespeak-lib_0.7-svn20060621.orig.tar.gz 75855e714bb522aca1b5104b27a3b3ee 4697 python optional codespeak-lib_0.7-svn20060621-1.diff.gz aa4d43685d098824562859eb3f71167f 366840 python optional python-codespeak-lib_0.7-svn20060621-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEvPkiStlRaw+TLJwRAvaLAJ9QvpYKl4a2ew290fC/JRVcEk+sogCfUJhs A5ytSKY6eLrcXnVyLS6yXDM= =hyub -END PGP SIGNATURE- Accepted: codespeak-lib_0.7-svn20060621-1.diff.gz to pool/main/c/codespeak-lib/codespeak-lib_0.7-svn20060621-1.diff.gz codespeak-lib_0.7-svn20060621-1.dsc to pool/main/c/codespeak-lib/codespeak-lib_0.7-svn20060621-1.dsc codespeak-lib_0.7-svn20060621.orig.tar.gz to pool/main/c/codespeak-lib/codespeak-lib_0.7-svn20060621.orig.tar.gz python-codespeak-lib_0.7-svn20060621-1_i386.deb to pool/main/c/codespeak-lib/python-codespeak-lib_0.7-svn20060621-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted console-tools 1:0.2.3dbs-64 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Jul 2006 17:11:34 +0100 Source: console-tools Binary: kbd-compat console-tools-dev libconsole console-tools Architecture: source all i386 Version: 1:0.2.3dbs-64 Distribution: unstable Urgency: low Maintainer: Alastair McKinstry [EMAIL PROTECTED] Changed-By: Alastair McKinstry [EMAIL PROTECTED] Description: console-tools - Linux console and font utilities console-tools-dev - Development files for Linux console and font manipulation kbd-compat - Wrappers around console-tools for backward compatibility with `kb libconsole - Shared libraries for Linux console and font manipulation Closes: 364797 Changes: console-tools (1:0.2.3dbs-64) unstable; urgency=low . * Use less permissive regexp in console-screen.sh to avoid misreading /etc/default/locale. Closes: #364797. * Added LSB information to console-screen.sh Files: edac938f0d1c986dc5d3004b30adb5b3 641 base optional console-tools_0.2.3dbs-64.dsc f8ee9bee69b5f68ea6d3b4a096c7974c 1490249 base optional console-tools_0.2.3dbs-64.tar.gz 59f3b9a8c99b0b8d0c09199b14ad602c 43526 utils optional kbd-compat_0.2.3dbs-64_all.deb a482d8a40879075f62595a709d4c3b40 296484 utils optional console-tools_0.2.3dbs-64_i386.deb 93a05673e9e011230168f2d953bb6291 129490 libs optional libconsole_0.2.3dbs-64_i386.deb ca861ef296ea4b0520bdbf4834030c50 86140 devel optional console-tools-dev_0.2.3dbs-64_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEvQjHQTK/kCo4XFcRAiEPAJ9zTrCZk+YGPQ/ErxhZ92ik095OnACgkufS dLaah9gKcUOPs25YXWg4B8s= =gprP -END PGP SIGNATURE- Accepted: console-tools-dev_0.2.3dbs-64_i386.deb to pool/main/c/console-tools/console-tools-dev_0.2.3dbs-64_i386.deb console-tools_0.2.3dbs-64.dsc to pool/main/c/console-tools/console-tools_0.2.3dbs-64.dsc console-tools_0.2.3dbs-64.tar.gz to pool/main/c/console-tools/console-tools_0.2.3dbs-64.tar.gz console-tools_0.2.3dbs-64_i386.deb to pool/main/c/console-tools/console-tools_0.2.3dbs-64_i386.deb kbd-compat_0.2.3dbs-64_all.deb to pool/main/c/console-tools/kbd-compat_0.2.3dbs-64_all.deb libconsole_0.2.3dbs-64_i386.deb to pool/main/c/console-tools/libconsole_0.2.3dbs-64_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted linux-kernel-di-i386-2.6 1.33 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Jul 2006 17:59:31 +0200 Source: linux-kernel-di-i386-2.6 Binary: crc-modules-2.6.16-2-486-di acpi-modules-2.6.16-2-486-di nic-shared-modules-2.6.16-2-486-di kernel-image-2.6.16-2-486-di irda-modules-2.6.16-2-486-di jfs-modules-2.6.16-2-486-di ide-core-modules-2.6.16-2-486-di fb-modules-2.6.16-2-486-di pcmcia-modules-2.6.16-2-486-di scsi-common-modules-2.6.16-2-486-di crypto-modules-2.6.16-2-486-di nic-usb-modules-2.6.16-2-486-di ide-modules-2.6.16-2-486-di scsi-core-modules-2.6.16-2-486-di nic-pcmcia-modules-2.6.16-2-486-di cdrom-core-modules-2.6.16-2-486-di usb-storage-modules-2.6.16-2-486-di fat-modules-2.6.16-2-486-di md-modules-2.6.16-2-486-di serial-modules-2.6.16-2-486-di nic-modules-2.6.16-2-486-di firmware-modules-2.6.16-2-486-di cdrom-modules-2.6.16-2-486-di plip-modules-2.6.16-2-486-di usb-serial-modules-2.6.16-2-486-di firewire-core-modules-2.6.16-2-486-di ppp-modules-2.6.16-2-486-di ntfs-modules-2.6.16-2-486-di reiserfs-modules-2.6.16-2-486-di mouse-modules-2.6.16-2-486-di ipv6-modules-2.6.16-2-486-di ext3-modules-2.6.16-2-486-di sata-modules-2.6.16-2-486-di input-modules-2.6.16-2-486-di scsi-modules-2.6.16-2-486-di ufs-modules-2.6.16-2-486-di usb-modules-2.6.16-2-486-di scsi-extra-modules-2.6.16-2-486-di qnx4-modules-2.6.16-2-486-di parport-modules-2.6.16-2-486-di nic-extra-modules-2.6.16-2-486-di floppy-modules-2.6.16-2-486-di pcmcia-storage-modules-2.6.16-2-486-di loop-modules-2.6.16-2-486-di xfs-modules-2.6.16-2-486-di Architecture: source i386 Version: 1.33 Distribution: unstable Urgency: low Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Frans Pop [EMAIL PROTECTED] Description: acpi-modules-2.6.16-2-486-di - ACPI support modules (udeb) cdrom-core-modules-2.6.16-2-486-di - CDROM support (udeb) cdrom-modules-2.6.16-2-486-di - Esoteric CDROM drivers (udeb) crc-modules-2.6.16-2-486-di - CRC modules (udeb) crypto-modules-2.6.16-2-486-di - crypto modules (udeb) ext3-modules-2.6.16-2-486-di - EXT3 filesystem support (udeb) fat-modules-2.6.16-2-486-di - FAT filesystem support (udeb) fb-modules-2.6.16-2-486-di - Frame buffer support (udeb) firewire-core-modules-2.6.16-2-486-di - Core FireWire drivers (udeb) firmware-modules-2.6.16-2-486-di - Firmware request modules (udeb) floppy-modules-2.6.16-2-486-di - Floppy driver (udeb) ide-core-modules-2.6.16-2-486-di - IDE support (udeb) ide-modules-2.6.16-2-486-di - IDE drivers (udeb) input-modules-2.6.16-2-486-di - Input devices support (udeb) ipv6-modules-2.6.16-2-486-di - IPv6 driver (udeb) irda-modules-2.6.16-2-486-di - Infrared devices support (udeb) jfs-modules-2.6.16-2-486-di - JFS filesystem support (udeb) kernel-image-2.6.16-2-486-di - Linux kernel binary image for the Debian installer (udeb) loop-modules-2.6.16-2-486-di - Loopback filesystem support (udeb) md-modules-2.6.16-2-486-di - RAID and LVM support (udeb) mouse-modules-2.6.16-2-486-di - Mouse support (udeb) nic-extra-modules-2.6.16-2-486-di - Rare NIC drivers (udeb) nic-modules-2.6.16-2-486-di - Common NIC drivers (udeb) nic-pcmcia-modules-2.6.16-2-486-di - Common PCMCIA NIC drivers (udeb) nic-shared-modules-2.6.16-2-486-di - Shared NIC drivers (udeb) nic-usb-modules-2.6.16-2-486-di - USB NIC drivers (udeb) ntfs-modules-2.6.16-2-486-di - NTFS filesystem support (udeb) parport-modules-2.6.16-2-486-di - Parallel port support (udeb) pcmcia-modules-2.6.16-2-486-di - Common PCMCIA drivers (udeb) pcmcia-storage-modules-2.6.16-2-486-di - PCMCIA storage drivers (udeb) plip-modules-2.6.16-2-486-di - PLIP drivers (udeb) ppp-modules-2.6.16-2-486-di - PPP drivers (udeb) qnx4-modules-2.6.16-2-486-di - QNX4 filesystem support (udeb) reiserfs-modules-2.6.16-2-486-di - Reiser filesystem support (udeb) sata-modules-2.6.16-2-486-di - SATA drivers (udeb) scsi-common-modules-2.6.16-2-486-di - Very common SCSI drivers (udeb) scsi-core-modules-2.6.16-2-486-di - Core SCSI subsystem (udeb) scsi-extra-modules-2.6.16-2-486-di - Uncommon SCSI drivers (udeb) scsi-modules-2.6.16-2-486-di - SCSI drivers (udeb) serial-modules-2.6.16-2-486-di - Serial drivers (udeb) ufs-modules-2.6.16-2-486-di - UFS filesystem support (udeb) usb-modules-2.6.16-2-486-di - USB support (udeb) usb-serial-modules-2.6.16-2-486-di - USB serial drivers (udeb) usb-storage-modules-2.6.16-2-486-di - USB storage support (udeb) xfs-modules-2.6.16-2-486-di - XFS filesystem support (udeb) Changes: linux-kernel-di-i386-2.6 (1.33) unstable; urgency=low . * Updated to 2.6.16-17. Files: 060fff5c212044b59a5e55dad5da72fa 2054 debian-installer optional linux-kernel-di-i386-2.6_1.33.dsc f49300228882f058fa480cdfcdfe88b2 7288 debian-installer optional linux-kernel-di-i386-2.6_1.33.tar.gz e2c90fcb942e064408281d32d55e05de 1356300 debian-installer extra kernel-image-2.6.16-2-486-di_1.33_i386.udeb 587e38dc6131d3ee483b550f103b653f 151580 debian-installer standard
Accepted linux-kernel-di-hppa-2.6 1.10 (source hppa)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Jul 2006 17:39:53 +0200 Source: linux-kernel-di-hppa-2.6 Binary: ext3-modules-2.6.16-2-parisc64-di usb-modules-2.6.16-2-parisc-di cdrom-core-modules-2.6.16-2-parisc-di kernel-image-2.6.16-2-parisc-di scsi-modules-2.6.16-2-parisc64-di input-modules-2.6.16-2-parisc-di ppp-modules-2.6.16-2-parisc64-di nic-modules-2.6.16-2-parisc64-di nic-modules-2.6.16-2-parisc-di usb-storage-modules-2.6.16-2-parisc64-di ide-modules-2.6.16-2-parisc64-di md-modules-2.6.16-2-parisc-di xfs-modules-2.6.16-2-parisc-di scsi-modules-2.6.16-2-parisc-di md-modules-2.6.16-2-parisc64-di loop-modules-2.6.16-2-parisc64-di ppp-modules-2.6.16-2-parisc-di usb-storage-modules-2.6.16-2-parisc-di ide-modules-2.6.16-2-parisc-di ext3-modules-2.6.16-2-parisc-di ipv6-modules-2.6.16-2-parisc64-di cdrom-core-modules-2.6.16-2-parisc64-di crypto-modules-2.6.16-2-parisc64-di crypto-modules-2.6.16-2-parisc-di loop-modules-2.6.16-2-parisc-di input-modules-2.6.16-2-parisc64-di kernel-image-2.6.16-2-parisc64-di xfs-modules-2.6.16-2-parisc64-di usb-modules-2.6.16-2-parisc64-di ipv6-modules-2.6.16-2-parisc-di Architecture: source hppa Version: 1.10 Distribution: unstable Urgency: low Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Frans Pop [EMAIL PROTECTED] Description: cdrom-core-modules-2.6.16-2-parisc-di - CDROM support (udeb) cdrom-core-modules-2.6.16-2-parisc64-di - CDROM support (udeb) crypto-modules-2.6.16-2-parisc-di - crypto modules (udeb) crypto-modules-2.6.16-2-parisc64-di - crypto modules (udeb) ext3-modules-2.6.16-2-parisc-di - EXT3 filesystem support (udeb) ext3-modules-2.6.16-2-parisc64-di - EXT3 filesystem support (udeb) ide-modules-2.6.16-2-parisc-di - IDE drivers (udeb) ide-modules-2.6.16-2-parisc64-di - IDE drivers (udeb) input-modules-2.6.16-2-parisc-di - Input devices support (udeb) input-modules-2.6.16-2-parisc64-di - Input devices support (udeb) ipv6-modules-2.6.16-2-parisc-di - IPv6 driver (udeb) ipv6-modules-2.6.16-2-parisc64-di - IPv6 driver (udeb) kernel-image-2.6.16-2-parisc-di - Linux kernel binary image for the Debian installer (udeb) kernel-image-2.6.16-2-parisc64-di - Linux kernel binary image for the Debian installer (udeb) loop-modules-2.6.16-2-parisc-di - Loopback filesystem support (udeb) loop-modules-2.6.16-2-parisc64-di - Loopback filesystem support (udeb) md-modules-2.6.16-2-parisc-di - RAID and LVM support (udeb) md-modules-2.6.16-2-parisc64-di - RAID and LVM support (udeb) nic-modules-2.6.16-2-parisc-di - Common NIC drivers (udeb) nic-modules-2.6.16-2-parisc64-di - Common NIC drivers (udeb) ppp-modules-2.6.16-2-parisc-di - PPP drivers (udeb) ppp-modules-2.6.16-2-parisc64-di - PPP drivers (udeb) scsi-modules-2.6.16-2-parisc-di - SCSI drivers (udeb) scsi-modules-2.6.16-2-parisc64-di - SCSI drivers (udeb) usb-modules-2.6.16-2-parisc-di - USB support (udeb) usb-modules-2.6.16-2-parisc64-di - USB support (udeb) usb-storage-modules-2.6.16-2-parisc-di - USB storage support (udeb) usb-storage-modules-2.6.16-2-parisc64-di - USB storage support (udeb) xfs-modules-2.6.16-2-parisc-di - XFS filesystem support (udeb) xfs-modules-2.6.16-2-parisc64-di - XFS filesystem support (udeb) Changes: linux-kernel-di-hppa-2.6 (1.10) unstable; urgency=low . * Update to 2.6.16-17 (2.6.16-2) kernels. Files: b9b5198b68621aabd72f05cc4cc9f820 1773 debian-installer optional linux-kernel-di-hppa-2.6_1.10.dsc 2279e18f69ce05afa853e6a5ee751deb 15399 debian-installer optional linux-kernel-di-hppa-2.6_1.10.tar.gz 7ccae153f9de0b14eca434a952130f69 1846834 debian-installer extra kernel-image-2.6.16-2-parisc-di_1.10_hppa.udeb 19c4bab174e23cde57a956d1627ae792 106052 debian-installer standard nic-modules-2.6.16-2-parisc-di_1.10_hppa.udeb 5bacb1e3665df95a3d9fc27fab8d906d 58758 debian-installer optional ppp-modules-2.6.16-2-parisc-di_1.10_hppa.udeb 4af1c1076f7b702413b584c57dd8bf3f 165238 debian-installer standard ide-modules-2.6.16-2-parisc-di_1.10_hppa.udeb 4c02f9dcd6ade9b654af4302d423e2ad 141876 debian-installer standard cdrom-core-modules-2.6.16-2-parisc-di_1.10_hppa.udeb 20b7c7dcc4b1f404a02ffb916acf799f 24 debian-installer standard scsi-modules-2.6.16-2-parisc-di_1.10_hppa.udeb bdc83c3b05b805bf3f0a6204d5504d69 11284 debian-installer standard loop-modules-2.6.16-2-parisc-di_1.10_hppa.udeb 779a0a26aecdde04932bbf9619ccf116 12 debian-installer extra ipv6-modules-2.6.16-2-parisc-di_1.10_hppa.udeb ad02259bf9440a2d669ddbd5745209d8 119176 debian-installer standard ext3-modules-2.6.16-2-parisc-di_1.10_hppa.udeb 6f80f07dda1e947242fce2808e666d0d 325672 debian-installer standard xfs-modules-2.6.16-2-parisc-di_1.10_hppa.udeb ce23243f21a9ebd167401868ada00428 160392 debian-installer extra md-modules-2.6.16-2-parisc-di_1.10_hppa.udeb 61c3187193ccac884c20fa22e8d74dd1 123168 debian-installer extra usb-modules-2.6.16-2-parisc-di_1.10_hppa.udeb b4042696c37619726c257943125e0b05 30038
Accepted db4.2 4.2.52+dfsg-0.1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Jul 2006 17:23:57 +0200 Source: db4.2 Binary: db4.2-util libdb4.2-tcl libdb4.2-java libdb4.2 libdb4.2-dev libdb4.2++c2 libdb4.2-java-dev libdb4.2++-dev Architecture: source i386 Version: 4.2.52+dfsg-0.1 Distribution: unstable Urgency: high Maintainer: Debian Berkeley DB Maintainers [EMAIL PROTECTED] Changed-By: Steinar H. Gunderson [EMAIL PROTECTED] Description: db4.2-util - Berkeley v4.2 Database Utilities libdb4.2 - Berkeley v4.2 Database Libraries [runtime] libdb4.2++-dev - Berkeley v4.2 Database Libraries for C++ [development] libdb4.2++c2 - Berkeley v4.2 Database Libraries for C++ [runtime] libdb4.2-dev - Berkeley v4.2 Database Libraries [development] libdb4.2-java - Berkeley v4.2 Database Libraries for Java libdb4.2-java-dev - Berkeley v4.2 Database Libraries for Java [development] libdb4.2-tcl - Berkeley v4.2 Database Libraries for TCL [module] Closes: 256332 357528 Changes: db4.2 (4.2.52+dfsg-0.1) unstable; urgency=high . * Non-maintainer upload. * Remove non-DFSG-free documentation from upstream package; do not ship the db4.2-doc package anymore. (Closes: #256332, #357528) Files: bb98bfb86053c8e4c8b3e67c44649d83 968 libs standard db4.2_4.2.52+dfsg-0.1.dsc 297392b1cdc5c97f22dc133858eccf29 2772681 libs standard db4.2_4.2.52+dfsg.orig.tar.gz c47012e17b926c4c29b39e248609f4a2 95049 libs standard db4.2_4.2.52+dfsg-0.1.diff.gz e279012795906dcaac755948b1b6f2c4 390568 libs standard libdb4.2_4.2.52+dfsg-0.1_i386.deb b7d70b9533538f83b7e0a832c628a96a 462844 libdevel extra libdb4.2-dev_4.2.52+dfsg-0.1_i386.deb a6ea15675b6794e05b952e311610c367 416154 libs optional libdb4.2++c2_4.2.52+dfsg-0.1_i386.deb 9fe4b31fca67445c5d309059ef645407 937114 libdevel extra libdb4.2++-dev_4.2.52+dfsg-0.1_i386.deb d4d033812beff8ed73546e57da8024c1 947174 interpreters extra libdb4.2-tcl_4.2.52+dfsg-0.1_i386.deb 2fa0955fd52ef9ff3f06d798b655fbf1 60628 utils optional db4.2-util_4.2.52+dfsg-0.1_i386.deb 96a9f657a47e84ed11b64d7e99ce1a42 561462 libs optional libdb4.2-java_4.2.52+dfsg-0.1_i386.deb 5cbfdcb501605a60e9045683357f21ef 465708 libs optional libdb4.2-java-dev_4.2.52+dfsg-0.1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEvQgsXKRQ3lK3SH4RAq29AJ9XJkH5jQ+X/ZDaVTGE5D2nD9ZMqQCbBGmJ 6sgDOeig0BbttDwyZMTdid0= =76YI -END PGP SIGNATURE- Accepted: db4.2-util_4.2.52+dfsg-0.1_i386.deb to pool/main/d/db4.2/db4.2-util_4.2.52+dfsg-0.1_i386.deb db4.2_4.2.52+dfsg-0.1.diff.gz to pool/main/d/db4.2/db4.2_4.2.52+dfsg-0.1.diff.gz db4.2_4.2.52+dfsg-0.1.dsc to pool/main/d/db4.2/db4.2_4.2.52+dfsg-0.1.dsc db4.2_4.2.52+dfsg.orig.tar.gz to pool/main/d/db4.2/db4.2_4.2.52+dfsg.orig.tar.gz libdb4.2++-dev_4.2.52+dfsg-0.1_i386.deb to pool/main/d/db4.2/libdb4.2++-dev_4.2.52+dfsg-0.1_i386.deb libdb4.2++c2_4.2.52+dfsg-0.1_i386.deb to pool/main/d/db4.2/libdb4.2++c2_4.2.52+dfsg-0.1_i386.deb libdb4.2-dev_4.2.52+dfsg-0.1_i386.deb to pool/main/d/db4.2/libdb4.2-dev_4.2.52+dfsg-0.1_i386.deb libdb4.2-java-dev_4.2.52+dfsg-0.1_i386.deb to pool/main/d/db4.2/libdb4.2-java-dev_4.2.52+dfsg-0.1_i386.deb libdb4.2-java_4.2.52+dfsg-0.1_i386.deb to pool/main/d/db4.2/libdb4.2-java_4.2.52+dfsg-0.1_i386.deb libdb4.2-tcl_4.2.52+dfsg-0.1_i386.deb to pool/main/d/db4.2/libdb4.2-tcl_4.2.52+dfsg-0.1_i386.deb libdb4.2_4.2.52+dfsg-0.1_i386.deb to pool/main/d/db4.2/libdb4.2_4.2.52+dfsg-0.1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted zope-cmfphoto 0.5.0-8 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Jul 2006 18:37:33 +0200 Source: zope-cmfphoto Binary: zope-cmfphoto Architecture: source all Version: 0.5.0-8 Distribution: unstable Urgency: low Maintainer: Debian/Ubuntu Zope Team [EMAIL PROTECTED] Changed-By: Fabio Tranchitella [EMAIL PROTECTED] Description: zope-cmfphoto - photo module for zope content management framework Closes: 378729 Changes: zope-cmfphoto (0.5.0-8) unstable; urgency=low . * debian/control: depends on zope-cmf1.6 | zope-cmf1.5 | zope-cmf1.4 | zope-cmf. (Closes: #378729) * debian/dzproduct: as above, and add zope 2.9 to the supported list. Files: 3e1eff8f8a19e12ac4a5b11806291b4b 727 web optional zope-cmfphoto_0.5.0-8.dsc 58c8f402983df6d1af6c59ed6e03 3449 web optional zope-cmfphoto_0.5.0-8.diff.gz 4228e68220f7f2df7e855650eb5737d2 31990 web optional zope-cmfphoto_0.5.0-8_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEvQ6eK/juK3+WFWQRAirtAKCbvwjJosBxXpeqi5XMxN3eXrRpHQCeOev+ gKM21KokOzGkhQZ8sj3uLYM= =+690 -END PGP SIGNATURE- Accepted: zope-cmfphoto_0.5.0-8.diff.gz to pool/main/z/zope-cmfphoto/zope-cmfphoto_0.5.0-8.diff.gz zope-cmfphoto_0.5.0-8.dsc to pool/main/z/zope-cmfphoto/zope-cmfphoto_0.5.0-8.dsc zope-cmfphoto_0.5.0-8_all.deb to pool/main/z/zope-cmfphoto/zope-cmfphoto_0.5.0-8_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted zope-cps 3.4.0-4 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Jul 2006 18:25:27 +0200 Source: zope-cps Binary: cps-site zope-cps Architecture: source all Version: 3.4.0-4 Distribution: unstable Urgency: low Maintainer: Debian/Ubuntu Zope Team [EMAIL PROTECTED] Changed-By: Fabio Tranchitella [EMAIL PROTECTED] Description: cps-site - preconfigured zope instance containing a cps site zope-cps - extensive collaborative web content management system (CMS) Closes: 376876 Changes: zope-cps (3.4.0-4) unstable; urgency=low . * debian-control: suggests python-pydot instead of recommends, it is not (yet) part of Debian. (Closes: #376876) Files: aedc326d3ccf781717d3d3d6bd8c3675 712 web optional zope-cps_3.4.0-4.dsc 3882b74b9030613376ed3b896dbade5d 4937 web optional zope-cps_3.4.0-4.diff.gz 9ec7bf6f6e739ac720dee3c99371f5f6 4438036 web optional zope-cps_3.4.0-4_all.deb 09f387d176f3469951b16b749bda81ca 3832 web optional cps-site_3.4.0-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD4DBQFEvQv1K/juK3+WFWQRAtwcAJipXfnnXMw8ILYzLIWc2E9QuCGfAJ9X6zsD b8jqbDNqYlrgqDeUFR73aw== =DqsZ -END PGP SIGNATURE- Accepted: cps-site_3.4.0-4_all.deb to pool/main/z/zope-cps/cps-site_3.4.0-4_all.deb zope-cps_3.4.0-4.diff.gz to pool/main/z/zope-cps/zope-cps_3.4.0-4.diff.gz zope-cps_3.4.0-4.dsc to pool/main/z/zope-cps/zope-cps_3.4.0-4.dsc zope-cps_3.4.0-4_all.deb to pool/main/z/zope-cps/zope-cps_3.4.0-4_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted at-spi 1.7.7-2.1 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Jul 2006 18:22:14 +0200 Source: at-spi Binary: libatspi-dev libatspi1.0-0 at-spi at-spi-doc libatspi-dbg Architecture: source i386 all Version: 1.7.7-2.1 Distribution: unstable Urgency: medium Maintainer: Akira TAGOH [EMAIL PROTECTED] Changed-By: Bas Zoetekouw [EMAIL PROTECTED] Description: at-spi - Assistive Technology Service Provider Interface at-spi-doc - Documentation files of at-spi for GNOME Accessibility libatspi-dbg - at-spi libraries and debugging symbols libatspi-dev - Development files of at-spi for GNOME Accessibility libatspi1.0-0 - C binding libraries of at-spi for GNOME Accessibility Closes: 377157 Changes: at-spi (1.7.7-2.1) unstable; urgency=medium . * Non-Maintainer Upload * Fix link failures (closes: #377157) Files: 53d8c4befeb528cdbe0c8302ce4caf80 1799 libs optional at-spi_1.7.7-2.1.dsc 2ad24597c7d923ddaf6101f2391807e1 8385 libs optional at-spi_1.7.7-2.1.diff.gz 7b7bd50c0dc0c48fba53f53ea484bc4a 157528 doc optional at-spi-doc_1.7.7-2.1_all.deb 6e7103c78b2f545c22dc4afb991b77d8 180440 gnome optional at-spi_1.7.7-2.1_i386.deb 76abeee2d52f8602fd9424a3f436b4d9 196310 libs optional libatspi1.0-0_1.7.7-2.1_i386.deb 85198e6aa56dcc00b5412726ab1d5ea8 142744 libdevel optional libatspi-dev_1.7.7-2.1_i386.deb 0ef543664275e27636ba5cd5cf317555 341026 libdevel extra libatspi-dbg_1.7.7-2.1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEvQ3tK67kHwZE+rcRAqHIAJ4+KVMT6GPJPibjxrsIf4G4n03/ewCdHsAu gw774VWEv+Rh60yIATVRWEs= =JyQo -END PGP SIGNATURE- Accepted: at-spi-doc_1.7.7-2.1_all.deb to pool/main/a/at-spi/at-spi-doc_1.7.7-2.1_all.deb at-spi_1.7.7-2.1.diff.gz to pool/main/a/at-spi/at-spi_1.7.7-2.1.diff.gz at-spi_1.7.7-2.1.dsc to pool/main/a/at-spi/at-spi_1.7.7-2.1.dsc at-spi_1.7.7-2.1_i386.deb to pool/main/a/at-spi/at-spi_1.7.7-2.1_i386.deb libatspi-dbg_1.7.7-2.1_i386.deb to pool/main/a/at-spi/libatspi-dbg_1.7.7-2.1_i386.deb libatspi-dev_1.7.7-2.1_i386.deb to pool/main/a/at-spi/libatspi-dev_1.7.7-2.1_i386.deb libatspi1.0-0_1.7.7-2.1_i386.deb to pool/main/a/at-spi/libatspi1.0-0_1.7.7-2.1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted linux-kernel-di-amd64-2.6 1.11 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Jul 2006 18:10:59 +0200 Source: linux-kernel-di-amd64-2.6 Binary: pcmcia-modules-2.6.16-2-amd64-generic-di firmware-modules-2.6.16-2-amd64-generic-di usb-storage-modules-2.6.16-2-amd64-generic-di ufs-modules-2.6.16-2-amd64-generic-di jfs-modules-2.6.16-2-amd64-generic-di loop-modules-2.6.16-2-amd64-generic-di ipv6-modules-2.6.16-2-amd64-generic-di cdrom-core-modules-2.6.16-2-amd64-generic-di qnx4-modules-2.6.16-2-amd64-generic-di serial-modules-2.6.16-2-amd64-generic-di fb-modules-2.6.16-2-amd64-generic-di ntfs-modules-2.6.16-2-amd64-generic-di kernel-image-2.6.16-2-amd64-generic-di ext3-modules-2.6.16-2-amd64-generic-di ide-modules-2.6.16-2-amd64-generic-di crc-modules-2.6.16-2-amd64-generic-di scsi-core-modules-2.6.16-2-amd64-generic-di irda-modules-2.6.16-2-amd64-generic-di md-modules-2.6.16-2-amd64-generic-di plip-modules-2.6.16-2-amd64-generic-di acpi-modules-2.6.16-2-amd64-generic-di crypto-modules-2.6.16-2-amd64-generic-di floppy-modules-2.6.16-2-amd64-generic-di scsi-common-modules-2.6.16-2-amd64-generic-di parport-modules-2.6.16-2-amd64-generic-di nic-extra-modules-2.6.16-2-amd64-generic-di xfs-modules-2.6.16-2-amd64-generic-di nic-shared-modules-2.6.16-2-amd64-generic-di usb-serial-modules-2.6.16-2-amd64-generic-di mouse-modules-2.6.16-2-amd64-generic-di firewire-core-modules-2.6.16-2-amd64-generic-di scsi-extra-modules-2.6.16-2-amd64-generic-di ppp-modules-2.6.16-2-amd64-generic-di usb-modules-2.6.16-2-amd64-generic-di nic-pcmcia-modules-2.6.16-2-amd64-generic-di pcmcia-storage-modules-2.6.16-2-amd64-generic-di sata-modules-2.6.16-2-amd64-generic-di nic-usb-modules-2.6.16-2-amd64-generic-di nic-modules-2.6.16-2-amd64-generic-di scsi-modules-2.6.16-2-amd64-generic-di reiserfs-modules-2.6.16-2-amd64-generic-di input-modules-2.6.16-2-amd64-generic-di fat-modules-2.6.16-2-amd64-generic-di ide-core-modules-2.6.16-2-amd64-generic-di Architecture: source amd64 Version: 1.11 Distribution: unstable Urgency: low Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Frederik Schüler [EMAIL PROTECTED] Description: acpi-modules-2.6.16-2-amd64-generic-di - ACPI support modules (udeb) cdrom-core-modules-2.6.16-2-amd64-generic-di - CDROM support (udeb) crc-modules-2.6.16-2-amd64-generic-di - CRC modules (udeb) crypto-modules-2.6.16-2-amd64-generic-di - crypto modules (udeb) ext3-modules-2.6.16-2-amd64-generic-di - EXT3 filesystem support (udeb) fat-modules-2.6.16-2-amd64-generic-di - FAT filesystem support (udeb) fb-modules-2.6.16-2-amd64-generic-di - Frame buffer support (udeb) firewire-core-modules-2.6.16-2-amd64-generic-di - Core FireWire drivers (udeb) firmware-modules-2.6.16-2-amd64-generic-di - Firmware request modules (udeb) floppy-modules-2.6.16-2-amd64-generic-di - Floppy driver (udeb) ide-core-modules-2.6.16-2-amd64-generic-di - IDE support (udeb) ide-modules-2.6.16-2-amd64-generic-di - IDE drivers (udeb) input-modules-2.6.16-2-amd64-generic-di - Input devices support (udeb) ipv6-modules-2.6.16-2-amd64-generic-di - IPv6 driver (udeb) irda-modules-2.6.16-2-amd64-generic-di - Infrared devices support (udeb) jfs-modules-2.6.16-2-amd64-generic-di - JFS filesystem support (udeb) kernel-image-2.6.16-2-amd64-generic-di - Linux kernel binary image for the Debian installer (udeb) loop-modules-2.6.16-2-amd64-generic-di - Loopback filesystem support (udeb) md-modules-2.6.16-2-amd64-generic-di - RAID and LVM support (udeb) mouse-modules-2.6.16-2-amd64-generic-di - Mouse support (udeb) nic-extra-modules-2.6.16-2-amd64-generic-di - Rare NIC drivers (udeb) nic-modules-2.6.16-2-amd64-generic-di - Common NIC drivers (udeb) nic-pcmcia-modules-2.6.16-2-amd64-generic-di - Common PCMCIA NIC drivers (udeb) nic-shared-modules-2.6.16-2-amd64-generic-di - Shared NIC drivers (udeb) nic-usb-modules-2.6.16-2-amd64-generic-di - USB NIC drivers (udeb) ntfs-modules-2.6.16-2-amd64-generic-di - NTFS filesystem support (udeb) parport-modules-2.6.16-2-amd64-generic-di - Parallel port support (udeb) pcmcia-modules-2.6.16-2-amd64-generic-di - Common PCMCIA drivers (udeb) pcmcia-storage-modules-2.6.16-2-amd64-generic-di - PCMCIA storage drivers (udeb) plip-modules-2.6.16-2-amd64-generic-di - PLIP drivers (udeb) ppp-modules-2.6.16-2-amd64-generic-di - PPP drivers (udeb) qnx4-modules-2.6.16-2-amd64-generic-di - QNX4 filesystem support (udeb) reiserfs-modules-2.6.16-2-amd64-generic-di - Reiser filesystem support (udeb) sata-modules-2.6.16-2-amd64-generic-di - SATA drivers (udeb) scsi-common-modules-2.6.16-2-amd64-generic-di - Very common SCSI drivers (udeb) scsi-core-modules-2.6.16-2-amd64-generic-di - Core SCSI subsystem (udeb) scsi-extra-modules-2.6.16-2-amd64-generic-di - Uncommon SCSI drivers (udeb) scsi-modules-2.6.16-2-amd64-generic-di - SCSI drivers (udeb) serial-modules-2.6.16-2-amd64-generic-di - Serial drivers (udeb) ufs-modules-2.6.16-2-amd64-generic-di -
Accepted linux-kernel-di-s390-2.6 0.05 (source s390)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Jul 2006 18:45:57 +0200 Source: linux-kernel-di-s390-2.6 Binary: md-modules-2.6.16-2-s390-di crypto-modules-2.6.16-2-s390-di scsi-modules-2.6.16-2-s390-di kernel-image-2.6.16-2-s390-di scsi-core-modules-2.6.16-2-s390-di nic-modules-2.6.16-2-s390-di xfs-modules-2.6.16-2-s390-di fat-modules-2.6.16-2-s390-di dasd-modules-2.6.16-2-s390-di Architecture: source s390 Version: 0.05 Distribution: unstable Urgency: low Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Frans Pop [EMAIL PROTECTED] Description: crypto-modules-2.6.16-2-s390-di - crypto modules (udeb) dasd-modules-2.6.16-2-s390-di - dasd modules (udeb) fat-modules-2.6.16-2-s390-di - FAT filesystem support (udeb) kernel-image-2.6.16-2-s390-di - Linux kernel binary image for the Debian installer (udeb) md-modules-2.6.16-2-s390-di - RAID and LVM support (udeb) nic-modules-2.6.16-2-s390-di - Common NIC drivers (udeb) scsi-core-modules-2.6.16-2-s390-di - Core SCSI subsystem (udeb) scsi-modules-2.6.16-2-s390-di - SCSI drivers (udeb) xfs-modules-2.6.16-2-s390-di - XFS filesystem support (udeb) Changes: linux-kernel-di-s390-2.6 (0.05) unstable; urgency=low . * Update to 2.6.16-17. Files: 01489ba1ed6591b0321539d5105aeacf 931 debian-installer optional linux-kernel-di-s390-2.6_0.05.dsc b5e591bbd82b8ba7f22e433f680cd6c6 1910 debian-installer optional linux-kernel-di-s390-2.6_0.05.tar.gz 4d07940776be44cb44dffa102f2fcd25 1771312 debian-installer extra kernel-image-2.6.16-2-s390-di_0.05_s390.udeb b28b359d4eaa55fb70eb7a0a3e6c5ede 168376 debian-installer standard nic-modules-2.6.16-2-s390-di_0.05_s390.udeb 988e7ae96de90456bb87c3d9e6ee2985 95056 debian-installer standard scsi-core-modules-2.6.16-2-s390-di_0.05_s390.udeb 5d49806d1dc5f65ec2d29352c5e9f596 104532 debian-installer standard scsi-modules-2.6.16-2-s390-di_0.05_s390.udeb 117967bd43772a741429ec4bb0ffb188 342544 debian-installer standard xfs-modules-2.6.16-2-s390-di_0.05_s390.udeb 82ff99396b7d7da290ac3e872170de60 46532 debian-installer extra fat-modules-2.6.16-2-s390-di_0.05_s390.udeb 8e5950a57194f3159a585ac72400425c 168058 debian-installer extra md-modules-2.6.16-2-s390-di_0.05_s390.udeb 7ea00bc85051bc5c5b7fddc5114d5b89 103374 debian-installer extra crypto-modules-2.6.16-2-s390-di_0.05_s390.udeb a81e790230cfbfa904f3e1e850a5fa39 76518 debian-installer standard dasd-modules-2.6.16-2-s390-di_0.05_s390.udeb Package-Type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFEvRWQgm/Kwh6ICoQRArANAJ9LQ6DLl68XQDBS/kByQP3nFPg6EgCfeEcG 44HF8DLfVxHjARa8D5v/Tgc= =rc38 -END PGP SIGNATURE- Accepted: crypto-modules-2.6.16-2-s390-di_0.05_s390.udeb to pool/main/l/linux-kernel-di-s390-2.6/crypto-modules-2.6.16-2-s390-di_0.05_s390.udeb dasd-modules-2.6.16-2-s390-di_0.05_s390.udeb to pool/main/l/linux-kernel-di-s390-2.6/dasd-modules-2.6.16-2-s390-di_0.05_s390.udeb fat-modules-2.6.16-2-s390-di_0.05_s390.udeb to pool/main/l/linux-kernel-di-s390-2.6/fat-modules-2.6.16-2-s390-di_0.05_s390.udeb kernel-image-2.6.16-2-s390-di_0.05_s390.udeb to pool/main/l/linux-kernel-di-s390-2.6/kernel-image-2.6.16-2-s390-di_0.05_s390.udeb linux-kernel-di-s390-2.6_0.05.dsc to pool/main/l/linux-kernel-di-s390-2.6/linux-kernel-di-s390-2.6_0.05.dsc linux-kernel-di-s390-2.6_0.05.tar.gz to pool/main/l/linux-kernel-di-s390-2.6/linux-kernel-di-s390-2.6_0.05.tar.gz md-modules-2.6.16-2-s390-di_0.05_s390.udeb to pool/main/l/linux-kernel-di-s390-2.6/md-modules-2.6.16-2-s390-di_0.05_s390.udeb nic-modules-2.6.16-2-s390-di_0.05_s390.udeb to pool/main/l/linux-kernel-di-s390-2.6/nic-modules-2.6.16-2-s390-di_0.05_s390.udeb scsi-core-modules-2.6.16-2-s390-di_0.05_s390.udeb to pool/main/l/linux-kernel-di-s390-2.6/scsi-core-modules-2.6.16-2-s390-di_0.05_s390.udeb scsi-modules-2.6.16-2-s390-di_0.05_s390.udeb to pool/main/l/linux-kernel-di-s390-2.6/scsi-modules-2.6.16-2-s390-di_0.05_s390.udeb xfs-modules-2.6.16-2-s390-di_0.05_s390.udeb to pool/main/l/linux-kernel-di-s390-2.6/xfs-modules-2.6.16-2-s390-di_0.05_s390.udeb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted zope-cmfforum 1.0-11 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Jul 2006 18:32:11 +0200 Source: zope-cmfforum Binary: zope-cmfforum Architecture: source all Version: 1.0-11 Distribution: unstable Urgency: low Maintainer: Debian/Ubuntu Zope Team [EMAIL PROTECTED] Changed-By: Fabio Tranchitella [EMAIL PROTECTED] Description: zope-cmfforum - forum module for zope content management framework Closes: 378723 Changes: zope-cmfforum (1.0-11) unstable; urgency=low . * debian/control: depends on zope-cmf1.6 | zope-cmf1.5 | zope-cmf1.4 | zope-cmf. (Closes: #378723) * debian/dzproduct: as above, and add zope 2.9 to the supported list. Files: e03d7e2ca5ebec1828865d08c62f8bbb 723 web optional zope-cmfforum_1.0-11.dsc 1dcd8e4ab098a98e6411cd5b699e3e25 5335 web optional zope-cmfforum_1.0-11.diff.gz f8a42ca72617360d3a8bd25dc1ff2f60 25538 web optional zope-cmfforum_1.0-11_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEvQ36K/juK3+WFWQRAmOuAKCAkP9jLhWXrC3qQt850CaiOfZfBACeM/7p BUZjHcgrH2p6jdvXaRxgDH8= =wq1O -END PGP SIGNATURE- Accepted: zope-cmfforum_1.0-11.diff.gz to pool/main/z/zope-cmfforum/zope-cmfforum_1.0-11.diff.gz zope-cmfforum_1.0-11.dsc to pool/main/z/zope-cmfforum/zope-cmfforum_1.0-11.dsc zope-cmfforum_1.0-11_all.deb to pool/main/z/zope-cmfforum/zope-cmfforum_1.0-11_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted partman-crypto 8 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Jul 2006 17:52:02 +0200 Source: partman-crypto Binary: partman-crypto-dm partman-crypto partman-crypto-loop Architecture: source i386 all Version: 8 Distribution: unstable Urgency: low Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Max Vozeler [EMAIL PROTECTED] Description: partman-crypto - Add to partman support for block device encryption (udeb) partman-crypto-dm - Add to partman support for dm-crypt encryption (udeb) partman-crypto-loop - Add to partman support for loop-AES encryption (udeb) Closes: 378687 Changes: partman-crypto (8) unstable; urgency=low . [ David Härdeman ] * Rename some files to make their purpose clearer. * Depend on base-installer to install cryptsetup when necessary before the initramfs is generated (requires base-installer 1.61). . [ Max Vozeler ] * Add loop-AES ciphers to /etc/modules. Closes: #378687 . [ Updated translations ] * Estonian (et.po) by Siim Põder * Gujarati (gu.po) by Kartik Mistry * Japanese (ja.po) by Kenshi Muto * Panjabi; Punjabi (pa.po) by A S Alam * Swedish (sv.po) by Daniel Nylander * Ukrainian (uk.po) by Eugeniy Meshcheryakov Files: 272f9b978eaa6e5246439cf0cb6c0e9e 607 debian-installer standard partman-crypto_8.dsc f8c836e4dbba3e8ff73e5021711b167a 222068 debian-installer standard partman-crypto_8.tar.gz 1bfbdafd2e0351815abaf79ce229fef0 1364 debian-installer standard partman-crypto-dm_8_all.udeb 38d146df39381b51897aa88a7e9ca7d8 1220 debian-installer standard partman-crypto-loop_8_all.udeb 79ddb6ded4710a792d67ff5a89a98082 156400 debian-installer standard partman-crypto_8_i386.udeb Package-Type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEvQaanVvVEbfNotwRAsKWAJ9r+uV3+iKvmsMWosMJcF01OJcGFgCfTbwF yHvhT1mqeuBquSpt5ogkW+Y= =QE4r -END PGP SIGNATURE- Accepted: partman-crypto-dm_8_all.udeb to pool/main/p/partman-crypto/partman-crypto-dm_8_all.udeb partman-crypto-loop_8_all.udeb to pool/main/p/partman-crypto/partman-crypto-loop_8_all.udeb partman-crypto_8.dsc to pool/main/p/partman-crypto/partman-crypto_8.dsc partman-crypto_8.tar.gz to pool/main/p/partman-crypto/partman-crypto_8.tar.gz partman-crypto_8_i386.udeb to pool/main/p/partman-crypto/partman-crypto_8_i386.udeb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted linux-kernel-di-sparc-2.6 1.12 (source sparc)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 19 Jul 2006 05:36:43 +0200 Source: linux-kernel-di-sparc-2.6 Binary: kernel-image-2.6.16-2-sparc64-di reiserfs-modules-2.6.16-2-sparc64-di ppp-modules-2.6.16-2-sparc32-di fat-modules-2.6.16-2-sparc32-di scsi-common-modules-2.6.16-2-sparc64-di reiserfs-modules-2.6.16-2-sparc32-di ipv6-modules-2.6.16-2-sparc64-di scsi-core-modules-2.6.16-2-sparc64-di nic-modules-2.6.16-2-sparc64-di usb-modules-2.6.16-2-sparc64-di cdrom-core-modules-2.6.16-2-sparc64-di cdrom-core-modules-2.6.16-2-sparc32-di kernel-image-2.6.16-2-sparc32-di jfs-modules-2.6.16-2-sparc64-di nic-modules-2.6.16-2-sparc32-di plip-modules-2.6.16-2-sparc64-di ipv6-modules-2.6.16-2-sparc32-di plip-modules-2.6.16-2-sparc32-di xfs-modules-2.6.16-2-sparc64-di sata-modules-2.6.16-2-sparc64-di scsi-common-modules-2.6.16-2-sparc32-di crypto-modules-2.6.16-2-sparc64-di scsi-extra-modules-2.6.16-2-sparc64-di ext3-modules-2.6.16-2-sparc32-di ext3-modules-2.6.16-2-sparc64-di ppp-modules-2.6.16-2-sparc64-di scsi-core-modules-2.6.16-2-sparc32-di md-modules-2.6.16-2-sparc32-di ide-modules-2.6.16-2-sparc64-di xfs-modules-2.6.16-2-sparc32-di md-modules-2.6.16-2-sparc64-di crypto-modules-2.6.16-2-sparc32-di fat-modules-2.6.16-2-sparc64-di Architecture: source sparc Version: 1.12 Distribution: unstable Urgency: low Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Frans Pop [EMAIL PROTECTED] Description: cdrom-core-modules-2.6.16-2-sparc32-di - CDROM support (udeb) cdrom-core-modules-2.6.16-2-sparc64-di - CDROM support (udeb) crypto-modules-2.6.16-2-sparc32-di - crypto modules (udeb) crypto-modules-2.6.16-2-sparc64-di - crypto modules (udeb) ext3-modules-2.6.16-2-sparc32-di - EXT3 filesystem support (udeb) ext3-modules-2.6.16-2-sparc64-di - EXT3 filesystem support (udeb) fat-modules-2.6.16-2-sparc32-di - FAT filesystem support (udeb) fat-modules-2.6.16-2-sparc64-di - FAT filesystem support (udeb) ide-modules-2.6.16-2-sparc64-di - IDE drivers (udeb) ipv6-modules-2.6.16-2-sparc32-di - IPv6 driver (udeb) ipv6-modules-2.6.16-2-sparc64-di - IPv6 driver (udeb) jfs-modules-2.6.16-2-sparc64-di - JFS filesystem support (udeb) kernel-image-2.6.16-2-sparc32-di - Linux kernel binary image for the Debian installer (udeb) kernel-image-2.6.16-2-sparc64-di - Linux kernel binary image for the Debian installer (udeb) md-modules-2.6.16-2-sparc32-di - RAID and LVM support (udeb) md-modules-2.6.16-2-sparc64-di - RAID and LVM support (udeb) nic-modules-2.6.16-2-sparc32-di - Network card modules for Sparc kernels (udeb) nic-modules-2.6.16-2-sparc64-di - Network card modules for Sparc kernels (udeb) plip-modules-2.6.16-2-sparc32-di - PLIP drivers (udeb) plip-modules-2.6.16-2-sparc64-di - PLIP drivers (udeb) ppp-modules-2.6.16-2-sparc32-di - PPP drivers (udeb) ppp-modules-2.6.16-2-sparc64-di - PPP drivers (udeb) reiserfs-modules-2.6.16-2-sparc32-di - Reiser filesystem support (udeb) reiserfs-modules-2.6.16-2-sparc64-di - Reiser filesystem support (udeb) sata-modules-2.6.16-2-sparc64-di - SATA drivers (udeb) scsi-common-modules-2.6.16-2-sparc32-di - Very common SCSI drivers (udeb) scsi-common-modules-2.6.16-2-sparc64-di - Very common SCSI drivers (udeb) scsi-core-modules-2.6.16-2-sparc32-di - Core SCSI subsystem (udeb) scsi-core-modules-2.6.16-2-sparc64-di - Core SCSI subsystem (udeb) scsi-extra-modules-2.6.16-2-sparc64-di - Uncommon SCSI drivers (udeb) usb-modules-2.6.16-2-sparc64-di - USB support (udeb) xfs-modules-2.6.16-2-sparc32-di - XFS filesystem support (udeb) xfs-modules-2.6.16-2-sparc64-di - XFS filesystem support (udeb) Changes: linux-kernel-di-sparc-2.6 (1.12) unstable; urgency=low . * Rebuild against linux-image 2.6.16-17 (2.6.16-2). Files: 075e6a24d7f807b16d31a090a4eedfb7 1935 debian-installer optional linux-kernel-di-sparc-2.6_1.12.dsc 237b7d86ab5d6871e34dab33f3ea8b9b 4927 debian-installer optional linux-kernel-di-sparc-2.6_1.12.tar.gz a8cb0c47ff27feb68dc02914f43fe557 1560494 debian-installer extra kernel-image-2.6.16-2-sparc64-di_1.12_sparc.udeb 3cf229e5b9a41cffc5e414fea742474d 753612 debian-installer standard nic-modules-2.6.16-2-sparc64-di_1.12_sparc.udeb 1afffa41255fd055b4cad7ec652c2b0a 53686 debian-installer optional ppp-modules-2.6.16-2-sparc64-di_1.12_sparc.udeb 6d9ffe8325a26e5b3fde7ac331b357ce 73734 debian-installer standard ide-modules-2.6.16-2-sparc64-di_1.12_sparc.udeb f192746efa7370cf3a010adff015e6e6 52688 debian-installer standard cdrom-core-modules-2.6.16-2-sparc64-di_1.12_sparc.udeb aa866d49eb1d04d7745d560c6a34e55d 91872 debian-installer standard scsi-core-modules-2.6.16-2-sparc64-di_1.12_sparc.udeb 09152953b0a8ffec0e2acd87023d2e05 420478 debian-installer standard scsi-common-modules-2.6.16-2-sparc64-di_1.12_sparc.udeb 7cd6430de8886ed7cf1d220127d8b675 478060 debian-installer standard scsi-extra-modules-2.6.16-2-sparc64-di_1.12_sparc.udeb 36abf2e711d450a07b5f884a69da6aa2 25770
