Re: dpatch
Le Sun, 15 Jun 2003 20:57:25 -0400, Peter S Galbraith a écrit : Sans être certain de comprendre ta question... Après avois fait ces étapes, tu insère cette ligne en haut de debian/rules : include /usr/share/dpatch/dpatch.make Puis tu peut faire (manuellement) : $ debian/rules patch et $ debian/rules unpatch Mais l'étape habituelle est de rajouter patch au target build, p.ex. build: patch configure-stamp build-stamp Merci beaucoup. En fait, je me suis rendu compte, en relisant, que le paquet en question n'était pas fait avec dpatch mais plutôt au format dbs... Donc, je ne comprenais pas ce qu'il attendait que je fasse... -- Raphaël SurcouF [EMAIL PROTECTED]
optional filtering and/or tagging is the perfect compromise
On Sun, Jun 15, 2003 at 09:22:08AM -0500, Manoj Srivastava wrote: As I have said before, as long as the default is to not cause data loss for everyone (since dropping emails may cause data loss), but allow people to opt in to have their mail filtered, I would have no objection. Opt in filtering is fine, and what other people do with their email is certainly no business of mine. this is a more than reasonable compromise - so please let's do it. craig
Re: Bug#196800: flex mustn't assume stdint.h is available on allplatforms
On Mon, 16 Jun 2003 13:22:24 +1000, Herbert Xu [EMAIL PROTECTED] said: Manoj Srivastava [EMAIL PROTECTED] wrote: I can understand the unease. But consider this: POSIX is already over a decade old; and it standardized practices that were SuSv3 aka POSIX was released one year ago. And changed nothing in the Lex definitions. As I said, we are dealing with decades old design. manoj -- Time flies like an arrow. Fruit flies like a banana. Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/%7Esrivasta/ 1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Re: Changelogs (Re: Bug#193497: marked as done (svtools: svsetup uses bashism echo -e))
On Mon, 16 Jun 2003 08:36:20 +1000, Herbert Xu [EMAIL PROTECTED] said: Manoj Srivastava [EMAIL PROTECTED] wrote: Even if the bug is for upstream fixing a typo in a comment? :) If it caused a Debian bug to be closed, that is a significant change in status for the Debian package (it may not be for the upstream software being packaged, but it is for my package). What if the bug was reported after the new Debian package was uploaded? Why does it suddenly stop being a significant change? Good point. Shall we mandate that all bug closures be adequately documented in the ChangeLog? I would be quite happy with that. Indeed, the rationale would be that closing bugs is an important event for the Package, and needs be thus documented. I thank you for pointing out this defect in our ChangeLog standards. manoj -- If all the world is a stage, where is the audience sitting? George Carlin Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/%7Esrivasta/ 1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Re: Every spam is sacred
On Mon, 16 Jun 2003 12:43:48 +1000, Russell Coker [EMAIL PROTECTED] said: On Mon, 16 Jun 2003 12:11, Theodore Ts'o wrote: false positive rate of as high as 2 per day by some estimates, do we as a body consider it acceptable if some percentage of Debian developers: 1) Don't receive a mail message from a fellow Debian developer because they unfortunately got caught by a false-positive (perhaps they got renumbered onto a bad SPAM address, or they were roaming on a wireless from a conference or during business travel) and important mail that related to Debian business gets lost? There is no excuse for this. Access to servers that are not in spam lists is well available to Debian developers. I tunnel my outgoing mail through a server in Melbourne no matter where I am, this avoids all issues of spam blocking by IP address. I offered accounts on a choice of machines to be used for such purposes for any Debian developers who have no better options, but so far no-one has taken me up on this offer. I refuse to allow spammers this victory. My machines are fully capable members of the internet, and I deliver my own email. My philosophy is that if people drop mail from me due to incompetence (since setting up machines to classify email from me as spam is indeed a misconfiguration), then I have no real desire to impose my musings on them. manoj -- I always had a repulsive need to be something more than human. David Bowie Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/%7Esrivasta/ 1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Dien dan dau tu va so huu tri tue
dien dan dau tu va so huu tri tue: http://www.luatgiapham.com
Dien dan dau tu va so huu tri tue
dien dan dau tu va so huu tri tue: http://www.luatgiapham.com
Re: Debian for x86-64 (AMD Opteron) and migration?
Ok, a bit late in this thread, but just a small remark on the future Opteron port : we have to take a *great* care of the migration process. The main difference betweek Intel-64 and AMD-64, if I am correct, is that administrators can unplug their ix86 disk from the server, and replug it on a opteron box, swicth the power button, and that's it. You'll get almost the same machine, and the you can start the upgrade process to 64-bit for all applications that needs them, and them finish the migration. This is a process that takes time (and for some servers that will take months or years) Therefore you can migrate smoothly machines from the 32-bit world to the 64-bit world witout having to do a painful migration from a 32-bit server to a full 64-bit one ; this is, IMHO, the greatest advantage of Opteron. Many people will not switch to Itanium for this reason: you have to break everything, including production application that sill are 32-bit. Then, a nice thing would be on Debian, for a regular user/administrator: - switch the disks to a Opteron box - update the APT sources to a Opteron source, or to a Opteron migration source - then, use something like : apt-get install base-64 to install the essential system files for 64-bit apt-get install libc6-64 .. essential libraries and elements for 64-bit code apt-get kernel-image..-64 64-bit kernel for Opteron I'm not sure that all remarks are wise, but I did not see this (migration) point clearly emerging from the Debian for x86-64 (AMD Opteron) previous discussion (My 2 euro cents remark)
Re: Every spam is sacred
On Mon, 16 Jun 2003 15:06, Manoj Srivastava wrote: There is no excuse for this. Access to servers that are not in spam lists is well available to Debian developers. I tunnel my outgoing mail through a server in Melbourne no matter where I am, this avoids all issues of spam blocking by IP address. I offered accounts on a choice of machines to be used for such purposes for any Debian developers who have no better options, but so far no-one has taken me up on this offer. I refuse to allow spammers this victory. My machines are fully capable members of the internet, and I deliver my own email. My philosophy is that if people drop mail from me due to incompetence (since setting up machines to classify email from me as spam is indeed a misconfiguration), then I have no real desire to impose my musings on them. If your machines are fully capable then they will have permanent IP addresses and no spam ever coming from them. In which case they will never get listed in a DNSBL (*) and there is nothing to be concerned about. (*) SPEWS level 2 and other excessively agressive DNSBL's may list you, but don't worry about that. No-one has suggested that we use such DNSBL's. We are talking about the simplest and most conservative ones that just list open relays etc. -- http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/Postal SMTP/POP benchmark http://www.coker.com.au/~russell/ My home page
Re: Every spam is sacred
In article [EMAIL PROTECTED] [EMAIL PROTECTED] writes: On Sun, Jun 15, 2003 at 11:45:17AM -0500, Steve Langasek wrote: If some number of Debian developers utilizing blocking that has a false positive rate of as high as 2 per day by some estimates, do we as a body consider it acceptable if some percentage of Debian developers: Alternativly, if Debian dosn't implement spam blocking, do we consider it acceptable that: Some developers stop reading any email, since the vast majority of it is spam. Developers delete messages unread because of spammy sounding subjects. Developers spend so much time reading spam they don't have time to fix bugs and do other useful work. People advocating not filtering spam based on some false positives seem to forget that being burried under the load of spam can cause more false postitives by the human forced to do the filtering. On my personal mailbox, I use some rather aggrasive lists that I wouldn't recomend to Debian at this time. (relays.osirusoft.com, which includes SPEWS and SBL, and block.blars.org that I run myself and don't recomend to others.) It still gets ten times as much spam as non-spam. Without the spam filters, I'd probably wind up not reading email at all. -- Blars Blarson [EMAIL PROTECTED] http://www.blars.org/blars.html Text is a way we cheat time. -- Patrick Nielsen Hayden
Re: Fun with python-apt
Anthony DeRobertis [EMAIL PROTECTED] wrote: [...] That could be. Somehow, the C++ ABI would have to be added to the Build-Dependency information. Either that, or C++ packages would have to use a specific C++ ABI compiler, e.g., (control) Build-Depends: c102, ... [...] Build-Depends: g++ (= 3:3.2.2-0) Many transitioned packages use(d) this to guarantee that the correct compiler was used. cu andreas
Re: Debian for x86-64 (AMD Opteron) and migration?
Hi, On Mon, Jun 16, 2003 at 07:33:35AM +0200, Xavier Roche wrote: Then, a nice thing would be on Debian, for a regular user/administrator: - switch the disks to a Opteron box - update the APT sources to a Opteron source, or to a Opteron migration source - then, use something like : apt-get install base-64 to install the essential system files for 64-bit apt-get install libc6-64 .. essential libraries and elements for 64-bit code apt-get kernel-image..-64 64-bit kernel for Opteron I'm not sure that all remarks are wise, but I did not see this (migration) point clearly emerging from the Debian for x86-64 (AMD Opteron) previous discussion Well, to some extent is was mentioned in the subthread by Wichert about dpkg being changed to allow multiple architectures at the same time, so that it's a matter of # echo x86-64 /etc/dpkg/legal-archs or, if ordering matters, # echo x86-64 /etc/dpkg/legal-archs.new # cat /etc/dpkg/legal-archs /etc/dpkg/legal-archs.new # mv /etc/dpkg/legal-archs.new /etc/dpkg/legal-archs and suddenly an # apt-get install fvwm2 will fetch pool/main/f/fvwm/fvwm_2.4.6-2_x86-64.deb from the archive, and pull in packages such as lib64c6, lib64readline4, lib64gtk1.2. In this example, only one version (32 or 64 bit) of an application such as fvwm can exist on the system (package name is the same, only architecture field is different), whereas both libreadline4 and lib64readline4 can exist (package name is different too, and one installs its files in /usr/lib, the other in /usr/lib64 as per the AMD64 ABI). Of course, this may be different for other programs, which do require the '64' in the package name because some other program explicitly depends on a 64 bit version. But in general, this will only be true for libraries because they go in the same address space. Interfaces between programs and other programs will hopefully mostly be 64-bit clean. The biggest objection that was raised is that it will be necessary to make the source package for libreadline4 generate two packages, libreadline4 and lib64readline4. Same for all other libraries. IOW, there's no automatic way to create all these lib64* packages from source. Have I summarised this correctly? Cheers, Emile. -- E-Advies - Emile van Bergen [EMAIL PROTECTED] tel. +31 (0)70 3906153 http://www.e-advies.nl pgp7VIRUBBmvE.pgp Description: PGP signature
Re: RFC: fewer vim variants
In message [EMAIL PROTECTED] you write: Hello people, I propose to restructure the vim package so that it builds fewer vim variants. I propose to have only the following: vim (aka vim-tiny; no interpreters, no docs) kvim (including all non-threaded interpreters; kde support; no docs) gvim (including all non-threaded interpreters; gtk2 support; no docs) vim-doc Let me know if this rubs you the wrong way. No, as long as I get gtk-vim without gnome. :-)
Re: Every spam is sacred: tagging mails because of their content or their supposed origin?
On Sun, Jun 15, 2003 at 11:19:10PM -0400, Duncan Findlay wrote: FWIW, the next version of spamassassin (2.60) will have no forgeable negatively scoring rules. (ETA early-mid July) Just out of curiosity, how will this be accomplished? -- 2. That which causes joy or happiness.
Re: Every spam is sacred
On Sun, Jun 15, 2003 at 10:11:22PM -0400, Theodore Ts'o wrote: Given that it's been pointed out that the MTA supports per-user bouncing of mail from open relays, and that it's very possible to use LDAP to provide easy management of per-user preferences, why is there any need to continue discussing what individual developers do or don't consider acceptable for collateral damage? I don't think it's as simple as that. When I worked for VA Linux systems, we consciously decided not to use any spam-blocking systems, and live with the spam, because the chance that we might lose one e-mail from a customer due to a false-positive was considered unacceptable. If some number of Debian developers utilizing blocking that has a false positive rate of as high as 2 per day by some estimates, do we as a body consider it acceptable if some percentage of Debian developers: Frankly, we as a body cannot possibly have a real say in this particular issue. Every developer can filter their mail for themselves -- and a lot of them already do (probably a vast majority). Even people who don't filter mail in a technical manner can perfectly well ignore mails for whatever reason. It's practically impossible to not leave this in the discretion of individual developers. Besides, mails get lost all the time, for a variety of reasons most of which are out of our control. The impact is never any more than negligible, otherwise there'd be much more fuss raised about it. but the debian mail system is run by the entire Debian project, and so it is appropriate that the decision be one which is taken by the entire project about whether or not supporting a service which has such a high potential false positive rate is something the Debian project as a whole should support. Now that's just silly. People are already allowed to use a myriad of filtering methods on Debian systems, none of which are intrinsically worse or better than those that aren't available systemwide (dnsbl, spamassassin, razor, ...). And if the method isn't available systemwide, they can run it from their home directory. Having stuff run in a more technically sane way (like by not having everyone maintain a duplicate copy of whatever software necessary in their $HOME, or having hundreds or thousands of DNS lookups get made per mail instead of just a few) is certainly something that any sysadmin would prefer. I'm getting tired of these red herrings. I guess it serves Santiago right -- he posted the issue on -devel in a flamebait-ish way and all he (and we) got was this useless flamewar. -- 2. That which causes joy or happiness.
Re: Changelogs (Re: Bug#193497: marked as done (svtools: svsetup uses bashism echo -e))
On Sun, Jun 15, 2003 at 11:42:44PM -0500, Manoj Srivastava wrote: On Mon, 16 Jun 2003 08:36:20 +1000, Herbert Xu [EMAIL PROTECTED] said: Manoj Srivastava [EMAIL PROTECTED] wrote: If it caused a Debian bug to be closed, that is a significant change in status for the Debian package (it may not be for the upstream software being packaged, but it is for my package). What if the bug was reported after the new Debian package was uploaded? Why does it suddenly stop being a significant change? Good point. Shall we mandate that all bug closures be adequately documented in the ChangeLog? I would be quite happy with that. Ai. Er, I hope you're not planning to encourage people to upload new versions of packages just to add bug numbers to the changelog? Because that would be most inefficient and wrong. My answer to Herbert would be it would be nice, but unfortunately time travel is not yet among our capabilities. -- Colin Watson [EMAIL PROTECTED]
Re: Every spam is sacred
On Thu, Jun 12, 2003 at 11:20:12PM +0200, Marcelo E. Magallon wrote: On Thu, Jun 12, 2003 at 02:18:57AM +0200, Santiago Vila wrote: How can they say no to using some of them in /warn mode ... ? Santiago holds that more than half of the spam could be eventually avoided. I'd very much like to see hard evidence against or in favor that assertion. Given the ammount of spam that I get delived to my account via Debian machines, I guess the reduction in bandwidth usage by master and murphy is not to be taken lightly. The bandwidth reduction will only happen if you decide to discard the mail, since the mail will always be accepted, scanned to find the IP which originated the message, the IP will be checked agains the database and then the mail will be tagged. The reduction happens in the output, but the load might increase in the server. mooch -- Jesus Climent | Unix SysAdm | Helsinki, Finland | pumuki.hispalinux.es GPG: 1024D/86946D69 BB64 2339 1CAA 7064 E429 7E18 66FC 1D7F 8694 6D69 -- Registered Linux user #66350 proudly using Debian Sid Linux 2.4.20 I say you are Lord, and I should know. I've followed a few. --Arthur (Life of Brian)
Re: Proposal for using SpamAssassin in master.d.o [Was: Re: Every spam is sacred]
On Sun, Jun 15, 2003 at 03:39:00PM +0200, Jesus Climent wrote: Hi. [...] I might thing I spoke BS on my proposal, since I have not heard any comments... mooch -- Jesus Climent | Unix SysAdm | Helsinki, Finland | pumuki.hispalinux.es GPG: 1024D/86946D69 BB64 2339 1CAA 7064 E429 7E18 66FC 1D7F 8694 6D69 -- Registered Linux user #66350 proudly using Debian Sid Linux 2.4.20 I never drink ... wine. --Dracula (Dracula)
Re: Every spam is sacred
On Sun, Jun 15, 2003 at 02:17:23PM +0200, Santiago Vila wrote: Read a previous message by Duncan Findlay. He said that 39.2668% of all the spam might be blocked by using the DSBL, but doing that you would block 0.0185% of ham. I just ran a quick test on my current email folders. At the moment I have very little email stored in my Debian folders (198 messages actually). I extracted IP addresses of machines connecting to master or murphy like this: $ cd path/to/debian/mail $ find -type f | while read f ; do formail -c -x Received $f done | egrep 'by (murphy|master).debian.org' | perl -lne '/\[([0-9.]+)\]/ print join(., reverse (split /\./, $1))' | sort -n -u | grep -v '1\.0\.0\.127' That outputs 103 IP addresses. Adding perl -pe 's/$/.list.dsbl.org/' | while read s ; do host $s ; done to that command I get a match for 175.90.65.4.list.dsbl.org Searching for the matchin message I get: Subject: Someone for you. Message-Id: [EMAIL PROTECTED] X-Spam-Status: No, hits=3.5 required=5.0 tests=HTML_30_40,HTML_MESSAGE,MIME_HTML_ONLY,REMOVE_PAGE,X_LOOP, X_MAILING_LIST version=2.55 I'm sure I don't have to show you the email to convince you that it's spam. Looking at my spam folder, I can extract 203 unique IP addresses (311 received emails) out of which 71 are *not* listed by list.dsbl.org. I call that impressive. Feel free to come up with your own numbers using your own received email. Now the question again: why does debian-admin and/or listmaster oppose to running this in warning mode? That'd be a much more accurate statistic since post-facto I can't tell if the IPs were added after observing the spam I'm testing with now, or if they were already present at the moment of reception. Marcelo
Red-Handed SCO ?
http://www.theinquirer.net/?article=9952 OK, it's the inquirer It it was proved to be true, shouldn't we *all* Linux users ( as well as Stallman plus the FSF as a whole ) sue SCO for copyright infringement ??? That could be *quite funny* g g Regards, J.L.
Re: Every spam is sacred
On Mon, Jun 16, 2003 at 11:37:00AM +0200, Jesus Climent wrote: The bandwidth reduction will only happen if you decide to discard the mail, since the mail will always be accepted, scanned to find the IP which originated the message, the IP will be checked agains the database and then the mail will be tagged. The IP that's checked in the DSBL is the one of the machine opening the connection to the MTA running at murphy/master. You don't actually scan the email headers. You are right that the bandwidth is decreased only if the mail is rejected instead of being just tagged, of course. The reduction happens in the output, but the load might increase in the server. Bandwidth is much more expensive than CPU time. The bandwidth required by the DNS lookups can also be reduced by maintaining a local cache. Marcelo
Re: Changelogs (Re: Bug#193497: marked as done (svtools: svsetup uses bashism echo -e))
Colin Watson [EMAIL PROTECTED] wrote:
On Sun, Jun 15, 2003 at 11:42:44PM -0500, Manoj Srivastava wrote:
What if the bug was reported after the new Debian package was
uploaded? Why does it suddenly stop being a significant change?
This is meant to be a rhetorical question.
My answer to Herbert would be it would be nice, but unfortunately time
travel is not yet among our capabilities.
Which just proves that listing things in the changelog on the basis of
bug reports is meaningless. Listing things that actually have changed
in Debian is what it was meant for in the first place.
--
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmVHI~} [EMAIL PROTECTED]
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Re: RFC: fewer vim variants
In article [EMAIL PROTECTED], Luca Filipozzi wrote: Hello people, I propose to restructure the vim package so that it builds fewer vim variants. I propose to have only the following: vim (aka vim-tiny; no interpreters, no docs) kvim (including all non-threaded interpreters; kde support; no docs) gvim (including all non-threaded interpreters; gtk2 support; no docs) vim-doc Let me know if this rubs you the wrong way. I think it's a good idea to merge the interpreters support. But concerning the gnome support I think it would be better to have a seperate package with gnome support as I did in the vim 6.2 patch (e.g., gvim-gnome ?) If I'm not mistaken, the vim gnome support adds mostly session management (when you login all your vim windows you had open on the previous logout appear in the same positions and the same files), which is something really handy. But of course, to add a dependency on gnome for the non-gnome users would be too much. Therefore two packages... José Fonseca PS: I tried to reply via the news gateway but it didn't fall through. Sorry if there's a dup.
Re: Bug#196800: flex mustn't assume stdint.h is available on allplatforms
Manoj Srivastava [EMAIL PROTECTED] wrote:
SuSv3 aka POSIX was released one year ago.
And changed nothing in the Lex definitions. As I said, we are
dealing with decades old design.
Hmm you must've missed section 1.1 :)
The entire document is aligned with ISO/IEC 9899: 1. There is no
requirement that lex generates code that is accepted by c89.
But of course this has no bearing on whether a particular implementation
chooses to be backwards compatible or not.
--
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmVHI~} [EMAIL PROTECTED]
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Re: Every spam is sacred
On Mon, 16 Jun 2003 19:37, Jesus Climent wrote: account via Debian machines, I guess the reduction in bandwidth usage by master and murphy is not to be taken lightly. The bandwidth reduction will only happen if you decide to discard the mail, since the mail will always be accepted, scanned to find the IP which originated the message, the IP will be checked agains the database and then the mail will be tagged. The usual implementation of DNSBL systems is to check the client IP address as soon as the TCP connection comes in, and disconnect with an appropriate error message if it's an IP address that you don't like. That saves a lot of bandwidth, and the mail is not discarded, it is left on the sending machine to be bounced in an appropriate manner back to the sender. -- http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/Postal SMTP/POP benchmark http://www.coker.com.au/~russell/ My home page
Re: Red-Handed SCO ?
[Please avoid posting messages that aren't about Debian development to -devel. Moved to -curiosa, although -project or -legal would probably be OK too.] On Mon, Jun 16, 2003 at 11:44:41AM +0200, Jos? Luis Tall?n wrote: http://www.theinquirer.net/?article=9952 OK, it's the inquirer It it was proved to be true, shouldn't we *all* Linux users ( as well as Stallman plus the FSF as a whole ) sue SCO for copyright infringement ??? That could be *quite funny* g g I can't see any basis for the Inquirer's claim that anyone with a copy of Linux could sue. If SCO copied GPLed code into UnixWare, then the GPL only requires them to provide the source to those to whom they distribute object code or executable form, not to the whole world. (It can't restrict those people from passing on the source either, but that's another step further on.) I'm not even sure that random UnixWare users could sue, although they could certainly write to SCO asking for the source. I would expect the litigants to be the copyright holders of misappropriated code. -- Colin Watson [EMAIL PROTECTED]
Re: Every spam is sacred
Russell Coker [EMAIL PROTECTED] a tapoté : On Mon, 16 Jun 2003 19:37, Jesus Climent wrote: account via Debian machines, I guess the reduction in bandwidth usage by master and murphy is not to be taken lightly. The bandwidth reduction will only happen if you decide to discard the mail, since the mail will always be accepted, scanned to find the IP which originated the message, the IP will be checked agains the database and then the mail will be tagged. The usual implementation of DNSBL systems is to check the client IP address as soon as the TCP connection comes in, and disconnect with an appropriate error message if it's an IP address that you don't like. That saves a lot of bandwidth, and the mail is not discarded, it is left on the sending machine to be bounced in an appropriate manner back to the sender. I think you missed the point: tagging mails is fine to everybody but not blocking/discarding/bouncing mails (that can be done later, by user, with their procmailrc). So as only tagging will be done, no bandwidth will be saved. -- Mathieu Roy Homepage: http://yeupou.coleumes.org Not a native english speaker: http://stock.coleumes.org/doc.php?i=/misc-files/flawed-english
Re: Red-Handed SCO ?
Le lun 16/06/2003 à 11:44, José Luis Tallón a écrit : http://www.theinquirer.net/?article=9952 OK, it's the inquirer It it was proved to be true, shouldn't we *all* Linux users ( as well as Stallman plus the FSF as a whole ) sue SCO for copyright infringement ??? That could be *quite funny* g g I think only the copyright holders could sue them. That still make a few hundred people and a few little companies like HP and IBM... -- .''`. Josselin Mouette/\./\ : :' : [EMAIL PROTECTED] `. `'[EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom signature.asc Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=
Re: Every spam is sacred
On Mon, Jun 16, 2003 at 11:37:00AM +0200, Jesus Climent wrote: Given the ammount of spam that I get delived to my account via Debian machines, I guess the reduction in bandwidth usage by master and murphy is not to be taken lightly. The reduction happens in the output, Which is secondary, insignificant, right? Here are some statistics for the BTS: 2003-04: mails received: 476 MB mails passed onto |receive: 66 MB 2003-05: mails received: 854 MB mails passed onto |receive: 79 MB 2003-06: mails received: 455 MB mails passed onto |receive: 36 MB but the load might increase in the server. Watch the oidentds and bugscans on master some time... there are much better ways to save machine load. -- 2. That which causes joy or happiness.
Re: Changelogs (Re: Bug#193497: marked as done (svtools: svsetup uses bashism echo -e))
On Mon, Jun 16, 2003 at 07:51:07PM +1000, Herbert Xu wrote: Which just proves that listing things in the changelog on the basis of bug reports is meaningless. No, it only shows that it is not possible under some circumstances: specifically, when there was no bug report at the time. To say that we should not document any bugs because of this is analogous to saying that since we cannot fix all of the bugs, we should not fix any of them. -- - mdz
Re: Fun with python-apt
On Mon, Jun 16, 2003 at 08:50:59AM +0200, Andreas Metzler wrote: Build-Depends: g++ (= 3:3.2.2-0) Many transitioned packages use(d) this to guarantee that the correct compiler was used. Which, of course, does not help with the situation he originally reported (building a woody package on testing with a newer compiler than was originally used). Time travel is still required there. :-) -- - mdz
Re: Status of Sarge Release Issues (Updated for June)
Hi, Marcelo E. Magallon wrote: On Sat, Jun 14, 2003 at 09:19:19PM +0200, Christoph Hellwig wrote: Stock OpenOffice seem to be able to embedd java applets into documents. RedHat nuked this. And we can't do the same because ... ??? We have done that (as Jan wrote.) Building needs Java anyhow... Regards, René -- .''`. René Engelhard -- Debian GNU/Linux Developer : :' : http://www.debian.org | http://people.debian.org/~rene/ `. `' [EMAIL PROTECTED] | GnuPG-Key ID: 248AEB73 `- Fingerprint: 41FA F208 28D4 7CA5 19BB 7AD9 F859 90B0 248A EB73 pgpd1WqgWzCoW.pgp Description: PGP signature
Re: Bug#196800: flex mustn't assume stdint.h is available on allplatforms
Herbert Xu [EMAIL PROTECTED] writes: SuSv3 aka POSIX was released one year ago. Huh? POSIX is the same as SUSv3 now? They used to be separate. -- Alan Shutko [EMAIL PROTECTED] - I am the rocks. Looking for a developer in St. Louis? http://web.springies.com/~ats/ Ten animals I slam in a net
Re: Debian for x86-64 (AMD Opteron) and migration?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 16 June 2003 09:12, Emile van Bergen wrote: # echo x86-64 /etc/dpkg/legal-archs or, if ordering matters, # echo x86-64 /etc/dpkg/legal-archs.new # cat /etc/dpkg/legal-archs /etc/dpkg/legal-archs.new # mv /etc/dpkg/legal-archs.new /etc/dpkg/legal-archs AFAICS, ordering should not matter for dpkg, it will simply install any legal package when asked to. I have currently hardcoded the check for i386 packages into my amd64 dpkg... The biggest objection that was raised is that it will be necessary to make the source package for libreadline4 generate two packages, libreadline4 and lib64readline4. Same for all other libraries. IOW, there's no automatic way to create all these lib64* packages from source. Currently, we are using a set of patches from Gerhard Tonn to build libraries on amd64 and on s390x that minimize the necessary source changes. Unfortunately, there has been no word about it from any dpkg or debhelper maintainer. See Bug #197117 and http://people.debian.org/~gt/lib64/. Arnd -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+7eql5t5GS2LDRf4RAkwZAKCPAzwoeCHpDdBTFlZKlKvExqy3gwCbBzzW qS7btl9/G/tJeH7sNmVmaJg= =PV0Q -END PGP SIGNATURE-
Re: Status of Sarge Release Issues (Updated for June)
On Sun, Jun 15, 2003 at 11:31:27PM +0200, Stefano Zacchiroli wrote: On Mon, Jun 02, 2003 at 02:38:47PM -0500, Drew Scott Daniels wrote: 2 ocaml status? http://lists.debian.org/debian-devel/2003/debian-devel-200304/msg00986.html and bug 187155. Done? Done! OCaml 3.06 has successfully entered testing with the whole set of correlated packages, including the Postgres bindings. That said, depending on the upstream release plans for 3.07 and the advancement of sarge, i have planes to ship sarge with ocaml 3.07. I don't know if this will be possible dependency-wise in time, but upstream is planning to release ocaml 3.07 in late july if everything goes well, and it should not take us more than a month to have everything testing-ready, but again, this would depend on the avancement of sarge, and if it doesn't work out like that, ocaml 3.06 is now in testing, and will not be replaced by 3.07 until 3.07 is ready to enter testing. Friendly, Sven Luther
Re: Red-Handed SCO ?
On Mon, 2003-06-16 at 12:36, Colin Watson wrote: I can't see any basis for the Inquirer's claim that anyone with a copy of Linux could sue. If SCO copied GPLed code into UnixWare, then the GPL only requires them to provide the source to those to whom they distribute object code or executable form, not to the whole world. (It can't restrict those people from passing on the source either, but that's another step further on.) I'm not even sure that random UnixWare users could sue, although they could certainly write to SCO asking for the source. I would expect the litigants to be the copyright holders of misappropriated code. It's funny that you mention it. This discussion has just been running on the kernel list regarding to embedded wlan routers and SAN solutions apparently based Linux. They have to provide the source or a written offer to obtain the source. The offer can be copied and given to anybody. So anybody that has got a copy of the written offer can go to SCO and require the Source, even if they didn't buy the Product. But these are actually only 2 options of the GNU GPL. There was more to it. Regards, Martin List-Petersen martin at list-petersen dot dk -- If God had wanted us to be concerned for the plight of the toads, he would have made them cute and furry. -- Dave Barry signature.asc Description: This is a digitally signed message part
Re: Every spam is sacred: tagging mails because of their content or their supposed origin?
On Mon, Jun 16, 2003 at 10:03:45AM +0200, Josip Rodin wrote: On Sun, Jun 15, 2003 at 11:19:10PM -0400, Duncan Findlay wrote: FWIW, the next version of spamassassin (2.60) will have no forgeable negatively scoring rules. (ETA early-mid July) Just out of curiosity, how will this be accomplished? The only negative rules will be: bayesian rules, bondedsender and habeas. Figuring how to autolearn ham (non-spam) is the only obstacle we still need to figure out. -- Duncan Findlay pgptieP4vqlZ2.pgp Description: PGP signature
Re: Red-Handed SCO ?
Martin List-Petersen writes: So anybody that has got a copy of the written offer can go to SCO and require the Source, even if they didn't buy the Product. However, if SCO fails to comply only the copyright owner can sue. -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill Elmwood, WI
Re: Fun with python-apt
On Mon, Jun 16, 2003 at 11:04:17AM -0400, Matt Zimmerman wrote: Which, of course, does not help with the situation he originally reported (building a woody package on testing with a newer compiler than was originally used). Time travel is still required there. :-) it works in this case if you build all the packages your package depends on, like the build is doing, because in that case apt wopuld habe been new abi, too. greetings bernd -- (OO) -- [EMAIL PROTECTED] -- ( .. ) [EMAIL PROTECTED],linux.de,debian.org} http://home.pages.de/~eckes/ o--o *plush* 2048/93600EFD [EMAIL PROTECTED] +497257930613 BE5-RIPE (OO) When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl!
gcc 3.3 - what problems should I expect?
Hello! I'm intending to move to SID from my woody box. I was wondering what problems should I expect while building packages using new gcc 3.3. Does kernel 2.4.21 build correctly? What about other progs like mplayer, mozilla etc? Can I install gcc 3.2 (f.egz. from testing)? regards cayco
Re: Red-Handed SCO ?
On Mon, 2003-06-16 at 20:14, John Hasler wrote: Martin List-Petersen writes: So anybody that has got a copy of the written offer can go to SCO and require the Source, even if they didn't buy the Product. However, if SCO fails to comply only the copyright owner can sue. That is correct .. And the first has allready said no no, as that article stated. It's also mentioned on Slashdot under Settling SCOres Regards, Martin List-Petersen martin at list-petersen dot dk -- We are MicroSoft. You will be assimilated. Resistance is futile. (Attributed to B.G., Gill Bates) signature.asc Description: This is a digitally signed message part
Re: Every spam is sacred
Mathieu Roy wrote: Manoj Srivastava [EMAIL PROTECTED] a tapoté : The 127th Ferengi rule of acquisition: Even if you got it for free, you paid too much. But the Rule 37th says otherwise: If it's free, take it and worry about hidden costs later. But the 96th confirms that For every Rule, there is an equal and opposite Rule, (except when there's not). interesting. i found this: http://www.dmwright.com/html/ferengi.htm Rule 127 » Stay neutral in conflict so that you can sell supplies to both sides. Manoj, perhaps you were thinking of this one: (same source) Rule 011 » Even if it's free, you can always buy it cheaper. -john
Scripts for plotting mailinglist statistics
Hi, I want to gain some insight in how well my bayesian spam filter [1,2] works over time and, hence, want to plot the trends of my regular inbox in comparison to my spambox (that is, the spam properly identified as spam) and the false negatives (not identified as spam). The statistics as generated on the Debian website [3] seems to already implement exactly what I want but I cannot find the scripts that generate them. Does anybody know who maintains them and/or if they are available some place? Thanks a lot, Auke 1. http://www.paulgraham.com/spam.html 2. http://pauillac.inria.fr/~xleroy/ 3. http://lists.debian.org/stats/debian-www.png -- PGP 0x4A34DD6D, http://bunny.sourceforge.net/
Re: Fun with python-apt
On Monday, Jun 16, 2003, at 02:50 US/Eastern, Andreas Metzler wrote: Build-Depends: g++ (= 3:3.2.2-0) Many transitioned packages use(d) this to guarantee that the correct compiler was used. That doesn't guarantee the correct compiler. It could, for example, use gcc 3.4 which could have yet another C++ ABI. Depending on c102 and then using g++-c102 would not allow that.
Re: Fun with python-apt
On Monday, Jun 16, 2003, at 14:59 US/Eastern, Bernd Eckenfels wrote: it works in this case if you build all the packages your package depends on, like the build is doing, because in that case apt wopuld habe been new abi, too. Yeah, but then again, its quite superfluous in that situation, too. Depending on gcc = 3.2 or gcc = 3.3 only makes sure the autobuilders don't build your supposedly new-ABI package with the old GCC.
Re: Fun with python-apt
On Monday, Jun 16, 2003, at 11:04 US/Eastern, Matt Zimmerman wrote: Which, of course, does not help with the situation he originally reported (building a woody package on testing with a newer compiler than was originally used). Time travel is still required there. :-) Agreed. To fix Woody requires time travel. [Or the ftpmasters going insane.] Now, if we changed sarge to use g++-c102 (as I briefly suggested), would that prevent this problem in sarge+1 or sarge+2 or whenever the ABI changes again?
Re: gcc 3.3 - what problems should I expect?
Quoting Krzysztof Kajkowski [EMAIL PROTECTED]: I'm intending to move to SID from my woody box. I was wondering what problems should I expect while building packages using new gcc 3.3. Does kernel 2.4.21 build correctly? What about other progs like mplayer, mozilla etc? Can I install gcc 3.2 (f.egz. from testing)? I've successfully built 2.4.20 with gcc 3.3 from unstable. I've been running it for about a week now with no problems. For an in-house C++ application, I had a bit of work to port it from 3.2 to 3.3. Most of the issues where concerned with better detection by gcc of non-standard usage. Once I fixed the code, the application compiled cleanly and ran without problems. -- Jean Pierre
Re: Fun with python-apt
On Mon, Jun 16, 2003 at 03:46:13PM -0400, Anthony DeRobertis wrote: Now, if we changed sarge to use g++-c102 (as I briefly suggested), would that prevent this problem in sarge+1 or sarge+2 or whenever the ABI changes again? no, because we WANT the packages beeing build with the new abi. We jus twant to make sure that lib providing pakcages are built with the same gcc as lib consuming ones. Using the latest gcc is the simplest solution, since this sooner or later will succeed, hopefully the packages with the unsatisfied dependencies are bug marked before they can break testing :) Greetings Bernd -- (OO) -- [EMAIL PROTECTED] -- ( .. ) [EMAIL PROTECTED],linux.de,debian.org} http://home.pages.de/~eckes/ o--o *plush* 2048/93600EFD [EMAIL PROTECTED] +497257930613 BE5-RIPE (OO) When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl!
Re: Every spam is sacred: tagging mails because of their content or their supposed origin?
On Mon, 16 Jun 2003, Duncan Findlay wrote: The only negative rules will be: bayesian rules, bondedsender and habeas. Figuring how to autolearn ham (non-spam) is the only obstacle we still need to figure out. Sure sounds like throwing the baby out with the bathwater... but I presume you all are running statistics on email distributions... Don Armstrong -- Any excuse will serve a tyrant. -- Aesop http://www.donarmstrong.com http://www.anylevel.com http://rzlab.ucr.edu pgpGEO5lz6saB.pgp Description: PGP signature
Re: Every spam is sacred
On Friday 13 June 2003 05:13 pm, Don Armstrong wrote: Oh, what the hell. This damn song won't get out of my head, so now you all get to be subjected to it to[1]: FWIW, the original version of this song has also been in my head for weeks. Thanks for digging up the full text :) 1: Misery loves company. Ad infinitum.
Re: Packages preventing other packages from going into testing (fwd)
J.H.M. Dassen (Ray) wrote: On Sun, Jun 15, 2003 at 18:44:12 +0200, Jacob Hallén wrote: I have written a little Python program that analyses http://ftp-master.debian.org/testing/update_excuses.html to find out where the bottlenecks are for packages going into testing. Essentially, it is a count of packages that directly and indirectly depend on a package with at least one RC bug before they can go into testing. Maybe I'm missing something, but it looks like you're reinventing http://bjorn.haxx.se/debian/ Yes, you are missing a small but important thing. Björns program is designed to answer the question Why is package X not in testing?. It does this very well and has lots of nifty features I didn't put into mine. My program answers the question Where will an extra effort produce drastic results? I'm sure I could have modified Björns program to yield this output, but I don't read and write Perl programs for pleasure. I think it is important to have a tool that answers my question and does so in a terse form that is pruned of all irrelevant data. If Testing is much closer to resleasable than it is now, it will be so much easier to make decisions about what to do with the few packages that are not ready for a release and so much easier to make a time plan for when to release. I know that releases are made when everything is ready, but this still means that some packages have to be dropped from the release and you have to make an extra effort for some time (bug squash parties etc) before a release is possible. Having luked on the Debian lists for many years, I think the next release will be more of a challenge than any of the earlier ones. Too few of the developers are really focused on what it takes to make a release. If there isn't change, I'm not sure there will ever be another stable release. Jacob Hallén
Re: Every spam is sacred
On Mon, 16 Jun 2003 16:18:49 +1000, Russell Coker [EMAIL PROTECTED] said: On Mon, 16 Jun 2003 15:06, Manoj Srivastava wrote: There is no excuse for this. Access to servers that are not in spam lists is well available to Debian developers. I tunnel my outgoing mail through a server in Melbourne no matter where I am, this avoids all issues of spam blocking by IP address. I offered accounts on a choice of machines to be used for such purposes for any Debian developers who have no better options, but so far no-one has taken me up on this offer. I refuse to allow spammers this victory. My machines are fully capable members of the internet, and I deliver my own email. My philosophy is that if people drop mail from me due to incompetence (since setting up machines to classify email from me as spam is indeed a misconfiguration), then I have no real desire to impose my musings on them. If your machines are fully capable then they will have permanent IP addresses and no spam ever coming from them. In which case they will never get listed in a DNSBL (*) and there is nothing to be concerned about. They are, when I send mail from home, or when I trael to the office. However, I often send mail from the road (or the internet cafe) where dhcp often rules. manoj -- The only way for a reporter to look at a politician is down. H.L. Mencken Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/%7Esrivasta/ 1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Re: Every spam is sacred: tagging mails because of their content or their supposed origin?
On Mon, Jun 16, 2003 at 04:43:53PM -0400, Don Armstrong wrote: On Mon, 16 Jun 2003, Duncan Findlay wrote: The only negative rules will be: bayesian rules, bondedsender and habeas. Figuring how to autolearn ham (non-spam) is the only obstacle we still need to figure out. Sure sounds like throwing the baby out with the bathwater... but I presume you all are running statistics on email distributions... Eventually, spammers will forge any test they can. (This of course presumes that spamassassin is a big problem for spammers.) It's extreme, but necessary. All the spamassassin scores are generated with a genetic algorithm using results from about 150k spam and 150k non-spam. The scores will naturally be adjusted to compensate for the lack of negative scoring rules. Anyways, this is quite OT for debian-devel (although so is the vast majority of this thread). -- Duncan Findlay pgpeCXv0A64y5.pgp Description: PGP signature
Re: Changelogs (Re: Bug#193497: marked as done (svtools: svsetup uses bashism echo -e))
On Mon, 16 Jun 2003 19:51:07 +1000, Herbert Xu [EMAIL PROTECTED] said: Colin Watson [EMAIL PROTECTED] wrote: On Sun, Jun 15, 2003 at 11:42:44PM -0500, Manoj Srivastava wrote: What if the bug was reported after the new Debian package was uploaded? Why does it suddenly stop being a significant change? This is meant to be a rhetorical question. It turned out to be closer to the mark than you suspected ;-) My answer to Herbert would be it would be nice, but unfortunately time travel is not yet among our capabilities. Which just proves that listing things in the changelog on the basis of bug reports is meaningless. Listing things that actually have changed in Debian is what it was meant for in the first place. I disagree. Changelogs for debian packages should document all changes that happened to the package -- and this include bugs that were closed, and the reaons thereof. No inconsistency. Thank you for helping me make my argument. manoj -- In any problem, if you find yourself doing an infinite amount of work, the answer may be obtained by inspection. Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/%7Esrivasta/ 1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Re: Changelogs (Re: Bug#193497: marked as done (svtools: svsetup uses bashism echo -e))
On Mon, 16 Jun 2003 09:36:24 +0100, Colin Watson [EMAIL PROTECTED] said: On Sun, Jun 15, 2003 at 11:42:44PM -0500, Manoj Srivastava wrote: On Mon, 16 Jun 2003 08:36:20 +1000, Herbert Xu [EMAIL PROTECTED] said: Manoj Srivastava [EMAIL PROTECTED] wrote: If it caused a Debian bug to be closed, that is a significant change in status for the Debian package (it may not be for the upstream software being packaged, but it is for my package). What if the bug was reported after the new Debian package was uploaded? Why does it suddenly stop being a significant change? Good point. Shall we mandate that all bug closures be adequately documented in the ChangeLog? I would be quite happy with that. Ai. Er, I hope you're not planning to encourage people to upload new versions of packages just to add bug numbers to the changelog? Because that would be most inefficient and wrong. *Sigh*. Has common sense totally escaped the world? I never indicated that one upload every other minute or whenever something is added to the changelog. I do think bug closures be documented in the ChangeLog (I shall attempt to do so from now on for every real bug that is closed for my packages). I shall not upload for every item in my changelog. And note this does not involve time travel; my changelog would document the bug was closed, and explain why: the fact that the change was made in the past is OK. manoj -- I owe the public nothing. J.P. Morgan Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/%7Esrivasta/ 1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
RECORD?
hey do you happen to know the world record for f1 2000...time trial at indianapolis
Re: Every spam is sacred
By the way some folks live in countries considered spam countries by other people, and they can't get a email in edgewise to the high class users. By the way how about my http://jidanni.org/comp/spam/spamdealer.html solution for the little guy, remote and without root. -- http://jidanni.org/ Taiwan(04)25854780
Re: Changelogs (Re: Bug#193497: marked as done (svtools: svsetup uses bashism echo -e))
On Mon, Jun 16, 2003 at 04:04:55PM -0500, Manoj Srivastava wrote: On Mon, 16 Jun 2003 09:36:24 +0100, Colin Watson [EMAIL PROTECTED] said: On Sun, Jun 15, 2003 at 11:42:44PM -0500, Manoj Srivastava wrote: Good point. Shall we mandate that all bug closures be adequately documented in the ChangeLog? I would be quite happy with that. Ai. Er, I hope you're not planning to encourage people to upload new versions of packages just to add bug numbers to the changelog? Because that would be most inefficient and wrong. *Sigh*. Has common sense totally escaped the world? I never indicated that one upload every other minute or whenever something is added to the changelog. I do think bug closures be documented in the ChangeLog (I shall attempt to do so from now on for every real bug that is closed for my packages). I shall not upload for every item in my changelog. And note this does not involve time travel; my changelog would document the bug was closed, and explain why: the fact that the change was made in the past is OK. At least don't use the Closes: syntax to do so, please. That will be a very good way to confuse attempts to track version information ... (By now I can't tell whether this is regarded as common sense or not, sorry.) Cheers, -- Colin Watson [EMAIL PROTECTED]
Re: Changelogs (Re: Bug#193497: marked as done (svtools: svsetup uses bashism echo -e))
Manoj Srivastava wrote: Good point. Shall we mandate that all bug closures be adequately documented in the ChangeLog? I would be quite happy with that. I do think bug closures be documented in the ChangeLog (I shall attempt to do so from now on for every real bug that is closed for my packages). I shall not upload for every item in my changelog. Like so? debhelper (4.1.48) unstable; urgency=low * Not adding ld.so.conf parsing code for libraries, if your library is not in a usual path, use the standard -X option to dh_makeshlibs to skip it. Closes: #122174 * No, I don't think that adding rm -rf /tmp to postinsts is a good idea. Closed: #201012 * Reasigned bugs #133949 and #123043 to dh-make, since dh_make is not in debhelper. When will people learn? * debhelper won't include a dh_installrootkit until I see more demand for such a program. Closes: #37337 * I fixed the debhelper overwrites libc bug back in 1999, why am I still getting reports about it? Sheesh. Closed: #393933, #209202, #384821 * Yes, debhelper and debconf do indeed have recursive build-depends. Deal. Closed: #197602 * In the last release I made a typo, and accidentially closed bug #196343, not #196344. I've reopened the former bug. Closes: #196344 * Trimmed the last 500k of the changelog; it was 90% of the entire package size since it recorded every dismissed feature request and dh-make bug for the past 6 years. * Fixed a typo in dh_python. Closes: #197679 -- Joey Hess [EMAIL PROTECTED] Mon, 16 Jun 2003 16:58:27 -0400 -- see shy jo pgpw7OVNsQEkU.pgp Description: PGP signature
Re: Every spam is sacred: tagging mails because of their content or their supposed origin?
Duncan Findlay wrote: The only negative rules will be: bayesian rules, bondedsender and habeas. Figuring how to autolearn ham (non-spam) is the only obstacle we still need to figure out. This is fairly off topic, but the other day I tired of downloading all my spam to check it for false positives, and so I whipped up a script to produce an index of a mailbox, with author and subject lines and sorted by SA score, and cronned it so I'd be mailed a daily summary to peruse. Today I noticed those summaries were getting spamassassing scores in the 30 range. I ended up whitelisting myself, though that doesn't feel like a good idea -- now SA might mislearn spam subjects as ham, and any spammer who forges mail from me will probably get through. Aside from bypassing SA entirely for local mail, is there any better approach? -- see shy jo pgpei9U6oNYFn.pgp Description: PGP signature
Re: Bug#196800: flex mustn't assume stdint.h is available on allplatforms
On Jun 13, Daniel Jacobowitz ([EMAIL PROTECTED]) wrote: On Fri, Jun 13, 2003 at 06:02:02PM -0500, Manoj Srivastava wrote: On Fri, 13 Jun 2003 18:20:37 -0400, Daniel Jacobowitz [EMAIL PROTECTED] said: On Thu, Jun 12, 2003 at 08:40:47PM -0500, Manoj Srivastava wrote: On Thu, 12 Jun 2003 15:22:17 -0400, Daniel Jacobowitz [EMAIL PROTECTED] said: You need to read up on your standards. The language called C is defined by only one authoritative standard. -- ISO/IEC 9899:1999 (E) (C)ISO/IEC Contents ix 5 This second edition cancels and replaces the first edition, ISO/IEC 9899:1990, as amended and corrected by ISO/IEC 9899/COR1:1994, ISO/IEC 9899/AMD1:1995, and ISO /IEC 9899/COR2:1996. -- Thus, I need have no such qualifiers when talking abouit conforming C implmentations. Given the real-world deployment of probably at least a dozen major OSs which were 9899:1990 conformant and predate the 9899:1999 standard, I'd say that's a pretty useless point of view. OOh, I am blinded by the cogency of your arguments. C99 is over 3 years old. And still not fully implemented. Unstable only switched to a compiler with minimal C99 support some months ago. GCC has no roadmap for implementing the remaining C99 features so it may be years before they are available on free operating systems. And? You seem to be implying (incorrectly), that flex requires more of C99 than is already present in Debian and a post 2.95 gcc. The new flex has been compiled, and has all the test suites succesfully compile, on all 11 architectures Debian supports. For ancient platforms, use flex-old. Anyway, you are certainly entitled to your opinion, and you can do whatever you want with your packages and your code. I am somewhat distressed that the version of flex provided with Debian (I am assuming from the discussion) will not be usable for cross-platform development without constant care to use flex-old instead. We've finally persuaded binutils and GCC to move into the era of C90 source. I don't think we'll see C99 widely enough supported to write portable software using it until 2008 at least. Again you raise a strawman. Flex comes with a plethora of tests, and all the tests have always been passed. Flex works with all 11 architectures that comprise debian (we have a mysterious test failure on the most recent m68k run, though I think it may have more to do with the new gcc there than anything else). Now, if you have any concrete objections as to why flex does not work in Debian, please feeel free to point them out. If you merely want to grumble about how flex may not work until 2008, without providing a basis for such grumplings, I am sure I can't help you there. You have missed my point. I am quite aware that flex-generated lexers will continue to work on all Debian platforms. But until C99 is much more mature than it is today, many other significant platforms will not have a C99-compatible compiler - even to the degree of including stdint.h. Therefore Debian becomes more awkward for cross-platform, portable development. Not useless, because of flex-old, but certainly more awkward; I will not be able to build Debian packages which require a recent flex in the same root in which I build cross-platform software. Certainly you have not broken Debian; but I maintain that this short-sightedness does damage Debian's usefulness as a development platform, for all those targets which many more practical developers must support in order to do their jobs. I think this is an excellent point. I can think of many times when I've done development work in Debian and ported the result to Solaris, IRIX or HPUX. It is, of course, not a requirement for Debian that this be easy, but the easier it is, the more convincing the argument for integrating Debian into a mixed *nix environment, for everyone from developers to CIOs. -- Neil Roeth
Accepted libgsf 1.8.1-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jun 2003 08:53:07 +0200 Source: libgsf Binary: libgsf-gnome-1 libgsf-1 libgsf-gnome-1-dev libgsf-1-dev Architecture: source i386 Version: 1.8.1-2 Distribution: unstable Urgency: high Maintainer: J.H.M. Dassen (Ray) [EMAIL PROTECTED] Changed-By: J.H.M. Dassen (Ray) [EMAIL PROTECTED] Description: libgsf-1 - Structured File Library - runtime version libgsf-1-dev - Structured File Library - development files (basic version) libgsf-gnome-1 - Structured File Library - runtime version for GNOME libgsf-gnome-1-dev - Structured File Library - development files for GNOME Changes: libgsf (1.8.1-2) unstable; urgency=high . * Try to work around a Jade bus error on m68k (#196730) by using OpenJade instead. * [doc/gtkdoc-mkhtml] New; based on the one from gtk-doc-tools 1.0-4. Changed to use OpenJade rather than Jade. * [debian/rules] Make doc/gtkdoc-mkhtml executable. * [doc/Makefile.am] Use local gtkdoc-mkhtml. * [debian/control] Added OpenJade build dependency. * [debian/control] Put libgsf-1-dev and libgsf-gnome-1-dev in section `libdevel'. Files: 819ad15ebcf70f436ce2b93ea1560336 1041 libs optional libgsf_1.8.1-2.dsc d327da1ca01978deeb0d1a6608c57a85 24312 libs optional libgsf_1.8.1-2.diff.gz 1072734c22a6adada37dad36dc0f57bf 31754 libdevel optional libgsf-gnome-1-dev_1.8.1-2_i386.deb b837dfc930b93a05168b1b438eee1bde 27232 libs optional libgsf-gnome-1_1.8.1-2_i386.deb 089070db94f69532f8987c099453136c 107698 libdevel optional libgsf-1-dev_1.8.1-2_i386.deb 4c9d7217ed8313bdb2338c00c3b689cb 73414 libs optional libgsf-1_1.8.1-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iQEXAwUBPu1q7wxJU8feGmjHFALcVgP+OUryhRtLeUZTLDeR61tqDC8eyC1DoVLm 0vg3Qyzz9fL31qVa4WmAFNZKNB8iAvf6ZIrsmpP7eaKTaEgLdb5pddW0J92huweg 0WKD6LG06oXtKJsu8ZN06ezXBZ7+wiM0/xTq8yqBWSBjQ5myPNG5+F7QiS28ZGFb ESSEcAnCuSED/21kVFZ6V9e3tKbbDXjsjd2skXdPcUmOT8sm538p2P+AQ2atiWUS dlCNj6WKO7UdmZNDgQTuo57ofHquopj95s6S9pIjdLLE2HDb6yzruV3DcqdktrAu 6llNMVFgUbZJRJNKeHKlpRuo4vWqO5PwtilPa3axhBAcV4CeLFwOW7zG =ksEw -END PGP SIGNATURE- Accepted: libgsf-1-dev_1.8.1-2_i386.deb to pool/main/libg/libgsf/libgsf-1-dev_1.8.1-2_i386.deb libgsf-1_1.8.1-2_i386.deb to pool/main/libg/libgsf/libgsf-1_1.8.1-2_i386.deb libgsf-gnome-1-dev_1.8.1-2_i386.deb to pool/main/libg/libgsf/libgsf-gnome-1-dev_1.8.1-2_i386.deb libgsf-gnome-1_1.8.1-2_i386.deb to pool/main/libg/libgsf/libgsf-gnome-1_1.8.1-2_i386.deb libgsf_1.8.1-2.diff.gz to pool/main/libg/libgsf/libgsf_1.8.1-2.diff.gz libgsf_1.8.1-2.dsc to pool/main/libg/libgsf/libgsf_1.8.1-2.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mol-drivers-macosx 0.9.69+20030616-1 (powerpc source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jun 2003 08:54:56 +0200 Source: mol-drivers-macosx Binary: mol-drivers-macosx Architecture: source powerpc Version: 0.9.69+20030616-1 Distribution: unstable Urgency: low Maintainer: Jens Schmalzing [EMAIL PROTECTED] Changed-By: Jens Schmalzing [EMAIL PROTECTED] Description: mol-drivers-macosx - The Mac-on-Linux emulator - drivers for Mac OS X Changes: mol-drivers-macosx (0.9.69+20030616-1) unstable; urgency=low . * Took a snapshot of the rsync tree. Files: c35b41685329aa5ff8bf1eb36a9ae494 641 non-free/otherosfs optional mol-drivers-macosx_0.9.69+20030616-1.dsc 0a0feb34faa8ea8a018e683fa91f16f0 163839 non-free/otherosfs optional mol-drivers-macosx_0.9.69+20030616.orig.tar.gz f7d6e26e4f33203936245126630b1fb2 9490 non-free/otherosfs optional mol-drivers-macosx_0.9.69+20030616-1.diff.gz 5a5c071c9a2260be86afa77a6377069d 173040 non-free/otherosfs optional mol-drivers-macosx_0.9.69+20030616-1_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+7XuTqYZgyBJFIH4RAmLhAJwODIMwcsQcn6GkJXGiEqk5mHr9RQCcD7Sn sjphpkLsJJdl2wTdZnNfQGw= =p2iz -END PGP SIGNATURE- Accepted: mol-drivers-macosx_0.9.69+20030616-1.diff.gz to pool/non-free/m/mol-drivers-macosx/mol-drivers-macosx_0.9.69+20030616-1.diff.gz mol-drivers-macosx_0.9.69+20030616-1.dsc to pool/non-free/m/mol-drivers-macosx/mol-drivers-macosx_0.9.69+20030616-1.dsc mol-drivers-macosx_0.9.69+20030616-1_powerpc.deb to pool/non-free/m/mol-drivers-macosx/mol-drivers-macosx_0.9.69+20030616-1_powerpc.deb mol-drivers-macosx_0.9.69+20030616.orig.tar.gz to pool/non-free/m/mol-drivers-macosx/mol-drivers-macosx_0.9.69+20030616.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mol-drivers-macos 0.9.69+20030616-1 (powerpc source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jun 2003 08:54:44 +0200 Source: mol-drivers-macos Binary: mol-drivers-macos Architecture: source powerpc Version: 0.9.69+20030616-1 Distribution: unstable Urgency: low Maintainer: Jens Schmalzing [EMAIL PROTECTED] Changed-By: Jens Schmalzing [EMAIL PROTECTED] Description: mol-drivers-macos - The Mac-on-Linux emulator - drivers for Mac OS 9 and earlier Changes: mol-drivers-macos (0.9.69+20030616-1) unstable; urgency=low . * Took a snapshot of the rsync tree. Files: aac6e1f4ac26742ee4e821f4802b77b7 636 contrib/otherosfs optional mol-drivers-macos_0.9.69+20030616-1.dsc 794b2fec7846e4942dadc28854d897f3 23263 contrib/otherosfs optional mol-drivers-macos_0.9.69+20030616.orig.tar.gz adb32d8d0538398be92a69909d571d9c 1917 contrib/otherosfs optional mol-drivers-macos_0.9.69+20030616-1.diff.gz 92edb2c1ae876a38f5ecfabc3caff9f8 25642 contrib/otherosfs optional mol-drivers-macos_0.9.69+20030616-1_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+7XuEqYZgyBJFIH4RAqZSAKDC5LPXJlTaDm3kSq5rh+SFWyu58ACfcENn xSu2ZKQeFZutLE6S8Ksjwlw= =bip5 -END PGP SIGNATURE- Accepted: mol-drivers-macos_0.9.69+20030616-1.diff.gz to pool/contrib/m/mol-drivers-macos/mol-drivers-macos_0.9.69+20030616-1.diff.gz mol-drivers-macos_0.9.69+20030616-1.dsc to pool/contrib/m/mol-drivers-macos/mol-drivers-macos_0.9.69+20030616-1.dsc mol-drivers-macos_0.9.69+20030616-1_powerpc.deb to pool/contrib/m/mol-drivers-macos/mol-drivers-macos_0.9.69+20030616-1_powerpc.deb mol-drivers-macos_0.9.69+20030616.orig.tar.gz to pool/contrib/m/mol-drivers-macos/mol-drivers-macos_0.9.69+20030616.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mol 0.9.69+20030616-1 (powerpc source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jun 2003 09:36:09 +0200 Source: mol Binary: mol mol-modules-2.4.20 mol-modules-source Architecture: source powerpc Version: 0.9.69+20030616-1 Distribution: unstable Urgency: low Maintainer: Jens Schmalzing [EMAIL PROTECTED] Changed-By: Jens Schmalzing [EMAIL PROTECTED] Description: mol- The Mac-on-Linux emulator mol-modules-2.4.20 - The Mac-on-Linux emulator - kernel modules for 2.4.20 mol-modules-source - The Mac-on-Linux emulator - source for kernel modules Changes: mol (0.9.69+20030616-1) unstable; urgency=low . * Took a snapshot of the rsync tree. . * `startmol --keyconfig' was broken in the previous version and is now functional again. Files: e26bf4bc2847b233fefa1a6d89217b52 730 otherosfs optional mol_0.9.69+20030616-1.dsc 37a094e3681b8d0dfe846c882466ecf0 1234024 otherosfs optional mol_0.9.69+20030616.orig.tar.gz 34219354ed5b134a5ac0173c54ccb48d 38524 otherosfs optional mol_0.9.69+20030616-1.diff.gz ef882e435974ec0161f9ccbc78f0f40a 938584 otherosfs optional mol_0.9.69+20030616-1_powerpc.deb eabbca000480e78cf4e3615c88fd2910 134932 otherosfs optional mol-modules-source_0.9.69+20030616-1_powerpc.deb bdf18b9f7e27cb1276c75d1e8cd9de2d 38520 otherosfs optional mol-modules-2.4.20_0.9.69+20030616-1_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+7Xt6qYZgyBJFIH4RApJqAKCS/W6cWOHcbbpGJSLRziNYCqShMACeNqpx gSNpVjrxtCad53z40aCUNtc= =b74I -END PGP SIGNATURE- Accepted: mol-modules-2.4.20_0.9.69+20030616-1_powerpc.deb to pool/main/m/mol/mol-modules-2.4.20_0.9.69+20030616-1_powerpc.deb mol-modules-source_0.9.69+20030616-1_powerpc.deb to pool/main/m/mol/mol-modules-source_0.9.69+20030616-1_powerpc.deb mol_0.9.69+20030616-1.diff.gz to pool/main/m/mol/mol_0.9.69+20030616-1.diff.gz mol_0.9.69+20030616-1.dsc to pool/main/m/mol/mol_0.9.69+20030616-1.dsc mol_0.9.69+20030616-1_powerpc.deb to pool/main/m/mol/mol_0.9.69+20030616-1_powerpc.deb mol_0.9.69+20030616.orig.tar.gz to pool/main/m/mol/mol_0.9.69+20030616.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted directory-administrator 1.5.1-3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jun 2003 10:49:37 +0200 Source: directory-administrator Binary: directory-administrator Architecture: source i386 Version: 1.5.1-3 Distribution: unstable Urgency: low Maintainer: Guido Trotter [EMAIL PROTECTED] Changed-By: Guido Trotter [EMAIL PROTECTED] Description: directory-administrator - LDAP POSIX user/group manager Changes: directory-administrator (1.5.1-3) unstable; urgency=low . * Added description to the patches. * Improved package long description. Files: 7bf8c817914c86ae059d75099088854c 696 gnome optional directory-administrator_1.5.1-3.dsc fe32d183c8058f0c167e2a92f4b96bcd 27170 gnome optional directory-administrator_1.5.1-3.diff.gz ce5a53d507119e52658a78f386b67e9e 332156 gnome optional directory-administrator_1.5.1-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+7YYWhImxTYgHUpsRAjgpAJ9TuruISkxjU39QJDbNVlrhKGDXeQCfabPT fFAqpgHYhnJ2XoclvVqDxiE= =kjSX -END PGP SIGNATURE- Accepted: directory-administrator_1.5.1-3.diff.gz to pool/main/d/directory-administrator/directory-administrator_1.5.1-3.diff.gz directory-administrator_1.5.1-3.dsc to pool/main/d/directory-administrator/directory-administrator_1.5.1-3.dsc directory-administrator_1.5.1-3_i386.deb to pool/main/d/directory-administrator/directory-administrator_1.5.1-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted stunnel 4.04-3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 9 Jun 2003 15:03:41 +0200 Source: stunnel Binary: stunnel Architecture: source i386 Version: 4.04-3 Distribution: unstable Urgency: low Maintainer: Julien LEMOINE [EMAIL PROTECTED] Changed-By: Julien LEMOINE [EMAIL PROTECTED] Description: stunnel- Universal SSL tunnel for network daemons Closes: 197566 Changes: stunnel (4.04-3) unstable; urgency=low . * comment ldap sample (Closes: #197566) Files: 26914dde057cc1dd1c023aa79912169a 592 net optional stunnel_4.04-3.dsc e7dbc0ce588c754a3a36a3eb0ef17f7c 5922 net optional stunnel_4.04-3.diff.gz 3cbb9c43912168bc38338089b16d41ab 60714 net optional stunnel_4.04-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+5IYNc29c8N2YKnURAg9IAJ90KgXncCrD5Hc3oWWmfA3riVtkawCeOqPO rSgn634IlpMb7C4tAXrjnUs= =eyt2 -END PGP SIGNATURE- Accepted: stunnel_4.04-3.diff.gz to pool/main/s/stunnel/stunnel_4.04-3.diff.gz stunnel_4.04-3.dsc to pool/main/s/stunnel/stunnel_4.04-3.dsc stunnel_4.04-3_i386.deb to pool/main/s/stunnel/stunnel_4.04-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted ccache 2.2-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jun 2003 10:52:50 +0100 Source: ccache Binary: ccache Architecture: source i386 Version: 2.2-2 Distribution: unstable Urgency: low Maintainer: Paul Russell [EMAIL PROTECTED] Changed-By: Paul Russell [EMAIL PROTECTED] Description: ccache - Compiler results cacher, for fast recompiles Closes: 197468 Changes: ccache (2.2-2) unstable; urgency=low . * Insert more symlinks in ccache dir (closes: #197468) Files: 6e67b056d2fcfaf5b19cc73a6cf9a661 548 devel optional ccache_2.2-2.dsc d7e40ed50312ea5ae75ab7f7e762fed9 23163 devel optional ccache_2.2-2.diff.gz 860408e1d18108b67bf9bc8c69cdc1d1 23192 devel optional ccache_2.2-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+7YcVEqpKZTfaTasRAgP3AKDD2zSpclSBKORJfBmiwqyAC2VNdgCgjUtl +f+6PSzCEbohuIlySMgQSuY= =5G+P -END PGP SIGNATURE- Accepted: ccache_2.2-2.diff.gz to pool/main/c/ccache/ccache_2.2-2.diff.gz ccache_2.2-2.dsc to pool/main/c/ccache/ccache_2.2-2.dsc ccache_2.2-2_i386.deb to pool/main/c/ccache/ccache_2.2-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted evolution 1.4.0-3 (i386 source)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 16 Jun 2003 12:18:36 +0900
Source: evolution
Binary: evolution-dev evolution
Architecture: source i386
Version: 1.4.0-3
Distribution: unstable
Urgency: low
Maintainer: Takuo KITAME [EMAIL PROTECTED]
Changed-By: Takuo KITAME [EMAIL PROTECTED]
Description:
evolution - The groupware suite
evolution-dev - Development library files for Evolution
Closes: 197213 197248 197314 197380 197561
Changes:
evolution (1.4.0-3) unstable; urgency=low
.
* Depends on scrollkeeper (${misc:Depends})(closes: #197380)
* Fix mozilla depenedency (closes: #197314)
* Build with -fPIC (closes: #197561)
* regenerate evolution.desktop (closes: #197213, #197248)
Files:
5e6adc9f7fb5780746a151acac35e1e0 945 gnome optional evolution_1.4.0-3.dsc
3bff3c9fea202ced074c2657f950db7c 15641 gnome optional evolution_1.4.0-3.diff.gz
e426fe8c72738f66a075fc83d1d2322b 9174634 gnome optional evolution_1.4.0-3_i386.deb
5dd935e9137df107379011cfeaf3ebb1 1412138 devel optional evolution-dev_1.4.0-3_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE+7UEaU+WZW1FVMwoRAqi8AJ9Tk2VkfC3pgPNy0njnzXnrDhQ6DQCdEAI3
afN2Ogt7sI6KYD9+fDWjBEg=
=O5Ny
-END PGP SIGNATURE-
Accepted:
evolution-dev_1.4.0-3_i386.deb
to pool/main/e/evolution/evolution-dev_1.4.0-3_i386.deb
evolution_1.4.0-3.diff.gz
to pool/main/e/evolution/evolution_1.4.0-3.diff.gz
evolution_1.4.0-3.dsc
to pool/main/e/evolution/evolution_1.4.0-3.dsc
evolution_1.4.0-3_i386.deb
to pool/main/e/evolution/evolution_1.4.0-3_i386.deb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted xmedcon 0.8.13-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jun 2003 10:33:23 +0200 Source: xmedcon Binary: xmedcon libmdc2 medcon libmdc2-dev Architecture: source i386 Version: 0.8.13-1 Distribution: unstable Urgency: low Maintainer: Roland Marcus Rutschmann [EMAIL PROTECTED] Changed-By: Roland Marcus Rutschmann [EMAIL PROTECTED] Description: libmdc2- Medical Image (DICOM, ECAT, ...) conversion tool libmdc2-dev - Medical Image (DICOM, ECAT, ...) conversion tool medcon - Medical Image (DICOM, ECAT, ...) conversion tool xmedcon- Medical Image (DICOM, ECAT, ...) conversion tool Changes: xmedcon (0.8.13-1) unstable; urgency=low . * New upstream release * Bumped to standards 3.5.10 (no changes needed) Files: f494fa85012301814aef46a9651fb27e 681 graphics optional xmedcon_0.8.13-1.dsc 34731a0b96c1c442329ed081acb11d41 803585 graphics optional xmedcon_0.8.13.orig.tar.gz 794917244b2d2293fa70cff0f5ec5a93 57933 graphics optional xmedcon_0.8.13-1.diff.gz 7f7fb49901f2ebe13fe00a9c88f2e957 212030 libs optional libmdc2_0.8.13-1_i386.deb eb0fb507ce1eb6504e654f52e4138a7a 302178 libdevel optional libmdc2-dev_0.8.13-1_i386.deb 13c20f932d5bca747fc00c6665c58ba6 27050 graphics optional medcon_0.8.13-1_i386.deb 9b77a7956fcb296e8f2e61f86d139eef 84490 graphics optional xmedcon_0.8.13-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+7ZD5YDBbMcCf01oRAuFtAKCGm2ZjSCFyKxtOwFe9WZWdtk0f9wCgsIU2 QNDCPKfVf5zwgUTEDXwtAF4= =ctYC -END PGP SIGNATURE- Accepted: libmdc2-dev_0.8.13-1_i386.deb to pool/main/x/xmedcon/libmdc2-dev_0.8.13-1_i386.deb libmdc2_0.8.13-1_i386.deb to pool/main/x/xmedcon/libmdc2_0.8.13-1_i386.deb medcon_0.8.13-1_i386.deb to pool/main/x/xmedcon/medcon_0.8.13-1_i386.deb xmedcon_0.8.13-1.diff.gz to pool/main/x/xmedcon/xmedcon_0.8.13-1.diff.gz xmedcon_0.8.13-1.dsc to pool/main/x/xmedcon/xmedcon_0.8.13-1.dsc xmedcon_0.8.13-1_i386.deb to pool/main/x/xmedcon/xmedcon_0.8.13-1_i386.deb xmedcon_0.8.13.orig.tar.gz to pool/main/x/xmedcon/xmedcon_0.8.13.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted developers-reference 3.3.3 (all source)
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Mon, 16 Jun 2003 04:08:29 -0400
Source: developers-reference
Binary: developers-reference-ja developers-reference-fr developers-reference
Architecture: source all
Version: 3.3.3
Distribution: unstable
Urgency: low
Maintainer: Adam Di Carlo [EMAIL PROTECTED]
Changed-By: Adam Di Carlo [EMAIL PROTECTED]
Description:
developers-reference - guidelines and information for Debian developers
developers-reference-fr - guidelines and information for Debian developers, in French
developers-reference-ja - guidelines and information for Debian developers, in
Japanese
Closes: 186605 189512 192417 195997 196516 196555
Changes:
developers-reference (3.3.3) unstable; urgency=low
.
* Frédéric Bothamy
- corrections by Michel Grentzinger
* Raphaël Hertzog
- updated documentation concerning the PTS
- added a paragraph about the PTS web interface
- documented how to add custom news item in the PTS
* Matt Zimmerman
- updates and clarifications to instructions for security bugs
- deprecate uploads to stable for security fixes, reference
section on security bugs; closes: #196516
- use dpkg-buildpackage -B to test binary-arch, not -b;
closes: #196555
* Adam Di Carlo
- Sec Managing sponsored packages: remove unnecessary 'debsign' cmd;
closes: #192417
- fix debconf-devel(7) man page section; closes: #189512
- Sec Responding to bugs: mention what FTBFS means; closes: #186605
- Sec Distribution directories renamed Distributions
- Sec The testing distribution moved under Sec Distribution
directories and renamed More information about the testing
distribution
- Secs Uploads to {stable,testing-proposed-updates} retitled to make
it clear these are special cases
- Sec Uploading to ftp-master: xref to Delayed incoming;
closes: #195997
- check compliance with Policy version 3.5.10
Files:
1b080f9ea2ce4695de78fd9be3e7949c 832 doc optional developers-reference_3.3.3.dsc
8e0613ab1f4f61a167dad8a95b7843ac 221717 doc optional developers-reference_3.3.3.tar.gz
74108ee3ffd1c5bac4795bf58141985c 486924 doc optional
developers-reference_3.3.3_all.deb
3956bf812ae5b30d4cb5edc26e336d47 532122 doc optional
developers-reference-fr_3.3.3_all.deb
5b973ba32de1f35551e5d58733b01610 90716 doc optional
developers-reference-ja_3.3.3_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)
iQCVAwUBPu2RfI/8QF79WmfNAQEQagQArdF0jr8NlzXKVdrLNSRxz7k7l2znCEmr
5IoiL97+gl+Dca+f4GqUCBT/lEyK0UAh7U6a4v14f/CVlbvgnyovaj9YgriT522B
qUKypjrdcFlMRNEcBiNx1YwKOHdK3i+UJwhQ1VQ6SA2ZjPqeu4DTNBxYdGxJA4UU
AtKJg4y+BNs=
=gpRq
-END PGP SIGNATURE-
Accepted:
developers-reference-fr_3.3.3_all.deb
to pool/main/d/developers-reference/developers-reference-fr_3.3.3_all.deb
developers-reference-ja_3.3.3_all.deb
to pool/main/d/developers-reference/developers-reference-ja_3.3.3_all.deb
developers-reference_3.3.3.dsc
to pool/main/d/developers-reference/developers-reference_3.3.3.dsc
developers-reference_3.3.3.tar.gz
to pool/main/d/developers-reference/developers-reference_3.3.3.tar.gz
developers-reference_3.3.3_all.deb
to pool/main/d/developers-reference/developers-reference_3.3.3_all.deb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libio-socket-inet6-perl 1.26-2 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jun 2003 20:03:11 +0900 Source: libio-socket-inet6-perl Binary: libio-socket-inet6-perl Architecture: source all Version: 1.26-2 Distribution: unstable Urgency: low Maintainer: Masahito Omote [EMAIL PROTECTED] Changed-By: Masahito Omote [EMAIL PROTECTED] Description: libio-socket-inet6-perl - Object interface for AF_INET6 domain sockets Closes: 196226 Changes: libio-socket-inet6-perl (1.26-2) unstable; urgency=low . * I forgot to close ITP. (closes: Bug#196226) * Fix speparation bug between address and port. * Fix to use getaddrinfo instead of inet_pton to work properly. * I have already sent these fixes to upstream. Files: 7e4f350e9bc79f1278f220e99c7c6f2f 565 perl optional libio-socket-inet6-perl_1.26-2.dsc 2d672ecb1b9bc70e34e461278d207787 5943 perl optional libio-socket-inet6-perl_1.26-2.tar.gz 9c9df1ccfe9b53d476df72c016e05de8 10378 perl optional libio-socket-inet6-perl_1.26-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+7aXZ4QYOB7JaXPERAqUFAKDJEr+odRW6jjJ5yCWJLaC73jX02wCdHxbO I+Pw+Erz32EtgUXOAefpgsw= =GnrX -END PGP SIGNATURE- Accepted: libio-socket-inet6-perl_1.26-2.dsc to pool/main/libi/libio-socket-inet6-perl/libio-socket-inet6-perl_1.26-2.dsc libio-socket-inet6-perl_1.26-2.tar.gz to pool/main/libi/libio-socket-inet6-perl/libio-socket-inet6-perl_1.26-2.tar.gz libio-socket-inet6-perl_1.26-2_all.deb to pool/main/libi/libio-socket-inet6-perl/libio-socket-inet6-perl_1.26-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted pingus 0.6.0-2 (powerpc all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 15 Jun 2003 18:13:17 +0200 Source: pingus Binary: pingus pingus-data Architecture: source powerpc all Version: 0.6.0-2 Distribution: unstable Urgency: low Maintainer: Simon Richter [EMAIL PROTECTED] Changed-By: Simon Richter [EMAIL PROTECTED] Description: pingus - Free Lemmings(TM) clone pingus-data - Data files for pingus, a free Lemmings(TM) clone Closes: 189969 Changes: pingus (0.6.0-2) unstable; urgency=low . * GCC 3.3 and 64 bit fixes (patch courtesy of John Lightsey, closes: #189969) Files: 0fcfcf3674a3be0fe07d9967f5156811 640 games optional pingus_0.6.0-2.dsc 50ab4f07d9a46f51e3ba8a2befc59f40 8840 games optional pingus_0.6.0-2.diff.gz 368a16f80dccaac41db96f4742753734 721312 games optional pingus_0.6.0-2_powerpc.deb 38a7566a9854bf30e1a68c22657a4f45 9394336 games optional pingus-data_0.6.0-2_all.deb url: http://pingus.seul.org/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+7YsqGKDMjVcGpLQRAtM8AJ96511YeE4DqB/kCsl1Iu/COX/EqQCg25v1 HUB7XPdWh8mAoQCx4OUlH7s= =briG -END PGP SIGNATURE- Accepted: pingus-data_0.6.0-2_all.deb to pool/main/p/pingus/pingus-data_0.6.0-2_all.deb pingus_0.6.0-2.diff.gz to pool/main/p/pingus/pingus_0.6.0-2.diff.gz pingus_0.6.0-2.dsc to pool/main/p/pingus/pingus_0.6.0-2.dsc pingus_0.6.0-2_powerpc.deb to pool/main/p/pingus/pingus_0.6.0-2_powerpc.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted nd 0.7.0-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jun 2003 21:41:54 +0900 Source: nd Binary: nd Architecture: source i386 Version: 0.7.0-2 Distribution: unstable Urgency: low Maintainer: Fumitoshi UKAI [EMAIL PROTECTED] Changed-By: Fumitoshi UKAI [EMAIL PROTECTED] Description: nd - Tiny little command line WebDAV interface Closes: 197614 Changes: nd (0.7.0-2) unstable; urgency=low . * fix FTBFS with gcc-3.3: Uses multiline strings (main.c:ND_USAGE) closes: Bug#197614 Files: e604e72065d99d63638bb496ad2a074b 554 net optional nd_0.7.0-2.dsc 283e24891cd58d235cc44522a89cba70 3028 net optional nd_0.7.0-2.diff.gz bcae45c2227084883351e8cbc2eec43b 17776 net optional nd_0.7.0-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+7b019D5yZjzIjAkRAr/DAJ9jg76DHtag3PJ5bcaNU4U83QqGzgCgkVne T9c27oITkWLnWS/JXFvhrJY= =hy1R -END PGP SIGNATURE- Accepted: nd_0.7.0-2.diff.gz to pool/main/n/nd/nd_0.7.0-2.diff.gz nd_0.7.0-2.dsc to pool/main/n/nd/nd_0.7.0-2.dsc nd_0.7.0-2_i386.deb to pool/main/n/nd/nd_0.7.0-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libdebug 0.2.3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jun 2003 14:23:22 +0200 Source: libdebug Binary: libdebug0-dev libdebug0 Architecture: source i386 Version: 0.2.3 Distribution: unstable Urgency: high Maintainer: Abraham vd Merwe [EMAIL PROTECTED] Changed-By: Abraham vd Merwe [EMAIL PROTECTED] Description: libdebug0 - Memory leak detection system and logging library libdebug0-dev - Development files for the debug library Closes: 194981 Changes: libdebug (0.2.3) unstable; urgency=high . * Changed libdebug0-dev section. * Removed multiline string test (Closes: #194981) Files: f96021c2d1fbf71bd3087920fb1cc786 552 devel optional libdebug_0.2.3.dsc 0e378f30f37c4645a68424a50d528892 12803 devel optional libdebug_0.2.3.tar.gz a1e3e7523dad7f3366c741babd202665 8876 devel optional libdebug0_0.2.3_i386.deb f3643b7e95ce91db863c6f9feb73b0a2 12092 libdevel optional libdebug0-dev_0.2.3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.5 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE+7biNzvVjZitVWu4RAiv4AJ9SDBH4u0oGCUBhfOFzIqYkLapFaQCfXDiu i4O9f/+XyyCiq8ccR+D8Tbw= =7nLk -END PGP SIGNATURE- Accepted: libdebug0-dev_0.2.3_i386.deb to pool/main/libd/libdebug/libdebug0-dev_0.2.3_i386.deb libdebug0_0.2.3_i386.deb to pool/main/libd/libdebug/libdebug0_0.2.3_i386.deb libdebug_0.2.3.dsc to pool/main/libd/libdebug/libdebug_0.2.3.dsc libdebug_0.2.3.tar.gz to pool/main/libd/libdebug/libdebug_0.2.3.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gprolog 1.2.18-1 (i386 source all)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 16 Jun 2003 13:28:54 +0100
Source: gprolog
Binary: gprolog gprolog-doc
Architecture: source i386 all
Version: 1.2.18-1
Distribution: unstable
Urgency: low
Maintainer: Salvador Abreu [EMAIL PROTECTED]
Changed-By: Salvador Abreu [EMAIL PROTECTED]
Description:
gprolog- GNU Prolog compiler
gprolog-doc - Documentation for the GNU Prolog compiler
Closes: 91 190636 191135
Changes:
gprolog (1.2.18-1) unstable; urgency=low
.
* New upstream release
* Wam2Ma/wam_parser.c: bump a limit to deal with larger source files.
* Rebuild fixes formatting problems (closes: #191135).
* Don't reference inexistant URL http://www.logic-programming.org/
(closes: #91).
* Include doc-base entry for gprolog-doc as well (closes: #190636).
* Bumped Standards-Version to 3.5.10
* Copied config.{sub,guess} from autotools-dev to get the latest.
Files:
6f15453d995a6f4e7b98f4bbc6fd1001 682 devel optional gprolog_1.2.18-1.dsc
66fed53a60729bd9a27749255bfa97f7 895657 devel optional gprolog_1.2.18.orig.tar.gz
ac21c32bf09db7b3ca4693fdc05c64ee 11962 devel optional gprolog_1.2.18-1.diff.gz
c8543448fa9cc53e5f4df6e6cc2b4343 1039064 doc optional gprolog-doc_1.2.18-1_all.deb
72956c3eda9d6bdc78d1309fbad1ed33 1228342 devel optional gprolog_1.2.18-1_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE+7cnPzoTo55Wk8dYRAmaRAKCbybMuWcYCF2pcpiMnJ7JpApZrkgCfU+SI
zg7O/kan1COv0Mkh/zRZV5U=
=9+Xv
-END PGP SIGNATURE-
Accepted:
gprolog-doc_1.2.18-1_all.deb
to pool/main/g/gprolog/gprolog-doc_1.2.18-1_all.deb
gprolog_1.2.18-1.diff.gz
to pool/main/g/gprolog/gprolog_1.2.18-1.diff.gz
gprolog_1.2.18-1.dsc
to pool/main/g/gprolog/gprolog_1.2.18-1.dsc
gprolog_1.2.18-1_i386.deb
to pool/main/g/gprolog/gprolog_1.2.18-1_i386.deb
gprolog_1.2.18.orig.tar.gz
to pool/main/g/gprolog/gprolog_1.2.18.orig.tar.gz
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted autorespond 2.0.3-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 17 Jun 2003 00:20:43 +1000 Source: autorespond Binary: autorespond Architecture: source i386 Version: 2.0.3-1 Distribution: unstable Urgency: low Maintainer: Sam Johnston [EMAIL PROTECTED] Changed-By: Sam Johnston [EMAIL PROTECTED] Description: autorespond - email autoresponder for qmail Changes: autorespond (2.0.3-1) unstable; urgency=low . * New upstream release Files: 333f6cc4039840296cc16a5655b03b60 574 contrib/net optional autorespond_2.0.3-1.dsc 21cbd765ab662c0553b309f7e412fcbf 7312 contrib/net optional autorespond_2.0.3.orig.tar.gz 649aa7c767d38932591b9841d5254ac6 2865 contrib/net optional autorespond_2.0.3-1.diff.gz ae72c12dac46eb7b05bb7602ef705435 8996 contrib/net optional autorespond_2.0.3-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+7dNWj4XJViLpTR0RAuC9AJ0claq9xumeIGO6oR8Db2qW+PFTkQCfQvA5 Owyslrnh0IhJvlsEXm5WdWs= =+v8Z -END PGP SIGNATURE- Accepted: autorespond_2.0.3-1.diff.gz to pool/contrib/a/autorespond/autorespond_2.0.3-1.diff.gz autorespond_2.0.3-1.dsc to pool/contrib/a/autorespond/autorespond_2.0.3-1.dsc autorespond_2.0.3-1_i386.deb to pool/contrib/a/autorespond/autorespond_2.0.3-1_i386.deb autorespond_2.0.3.orig.tar.gz to pool/contrib/a/autorespond/autorespond_2.0.3.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fetchmail 6.2.2-2 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jun 2003 17:01:41 +0200 Source: fetchmail Binary: fetchmailconf fetchmail Architecture: source i386 all Version: 6.2.2-2 Distribution: unstable Urgency: low Maintainer: Benjamin Drieu [EMAIL PROTECTED] Changed-By: Benjamin Drieu [EMAIL PROTECTED] Description: fetchmail - SSL enabled POP3, APOP, IMAP mail gatherer/forwarder fetchmailconf - fetchmail configurator Closes: 197631 Changes: fetchmail (6.2.2-2) unstable; urgency=low . * Do not croak if /usr/share/doc/fetchmail is missing (closes: #197631) Files: 39f2244942ee2d4c8d9d3cad005b32c5 718 mail optional fetchmail_6.2.2-2.dsc 43687f5bfa02c516a1bcd7ce66bc5edd 230116 mail optional fetchmail_6.2.2-2.diff.gz 9d7a1858dd8338d1d11ceea34889f75f 96670 mail optional fetchmailconf_6.2.2-2_all.deb 50e3ebcf03ec9e9eb110a53dd0bae5ff 497880 mail optional fetchmail_6.2.2-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+7d2mnDLqtZBL50ERAsXOAKC2B8il64Io/s1zmMigBM8vIvTGtQCgjC6L ezwar9MpzU99C7WhpwjTKmo= =irDA -END PGP SIGNATURE- Accepted: fetchmail_6.2.2-2.diff.gz to pool/main/f/fetchmail/fetchmail_6.2.2-2.diff.gz fetchmail_6.2.2-2.dsc to pool/main/f/fetchmail/fetchmail_6.2.2-2.dsc fetchmail_6.2.2-2_i386.deb to pool/main/f/fetchmail/fetchmail_6.2.2-2_i386.deb fetchmailconf_6.2.2-2_all.deb to pool/main/f/fetchmail/fetchmailconf_6.2.2-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted tipptrainer 0.4.1-3 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jun 2003 17:22:33 +0200 Source: tipptrainer Binary: tipptrainer-data-en tipptrainer tipptrainer-data-de Architecture: source i386 all Version: 0.4.1-3 Distribution: unstable Urgency: low Maintainer: Andreas Tille [EMAIL PROTECTED] Changed-By: Andreas Tille [EMAIL PROTECTED] Description: tipptrainer - A program to learn touch typing tipptrainer-data-de - German data for tipptrainer tipptrainer-data-en - English data for tipptrainer Closes: 197328 Changes: tipptrainer (0.4.1-3) unstable; urgency=low . * Standards-Version: 3.5.10 * Removed automake* and autoconf from Build-Depends * Fixed po/Makefile.in (Thanks to Andreas Metzler [EMAIL PROTECTED]) closes: #197328 Files: 3ff82f687ba3d5e9c39d7bb43dd281f7 747 games optional tipptrainer_0.4.1-3.dsc 65de133fceb73aa1093341d84ad041e1 4800 games optional tipptrainer_0.4.1-3.diff.gz deca3fde4abc612d8c446ade62cae4ad 494154 games optional tipptrainer-data-de_0.4.1-3_all.deb 3c8241e210ef07ecc2f74cd458c50660 110400 games optional tipptrainer-data-en_0.4.1-3_all.deb 5bce48de4a7d8456f9a0edbb1768bd65 170248 games optional tipptrainer_0.4.1-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+7eKvYDBbMcCf01oRAo4LAJ9ujFDvxnMNQ+YVXS5ZmSjdhvCGXgCfdVkR gNePJZ+Di6xyZSAqnT9Qxg8= =uhCt -END PGP SIGNATURE- Accepted: tipptrainer-data-de_0.4.1-3_all.deb to pool/main/t/tipptrainer/tipptrainer-data-de_0.4.1-3_all.deb tipptrainer-data-en_0.4.1-3_all.deb to pool/main/t/tipptrainer/tipptrainer-data-en_0.4.1-3_all.deb tipptrainer_0.4.1-3.diff.gz to pool/main/t/tipptrainer/tipptrainer_0.4.1-3.diff.gz tipptrainer_0.4.1-3.dsc to pool/main/t/tipptrainer/tipptrainer_0.4.1-3.dsc tipptrainer_0.4.1-3_i386.deb to pool/main/t/tipptrainer/tipptrainer_0.4.1-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted analog 2:5.32-4 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 15 Jun 2003 19:14:22 -0400 Source: analog Binary: analog Architecture: source i386 Version: 2:5.32-4 Distribution: unstable Urgency: low Maintainer: Joey Hess [EMAIL PROTECTED] Changed-By: Joey Hess [EMAIL PROTECTED] Description: analog - analyzes logfiles from web servers Closes: 197512 Changes: analog (2:5.32-4) unstable; urgency=low . * Add pt_BR debconf po translation. Closes: #197512 Files: 9672a47b60e66442a77ef3d55d756fd3 655 web optional analog_5.32-4.dsc 2f87303213d81bb2a7fd84a338bdedff 19731 web optional analog_5.32-4.diff.gz af097f0e28ea2dad9333d061c89c7d5e 1238052 web optional analog_5.32-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+7QBz2tp5zXiKP0wRAolJAJ9y8wRheDLAmKFPWhzajNGpeI/JVgCffmJu 8bc+ZJpODQdGKV0t7alIMRc= =DluD -END PGP SIGNATURE- Accepted: analog_5.32-4.diff.gz to pool/main/a/analog/analog_5.32-4.diff.gz analog_5.32-4.dsc to pool/main/a/analog/analog_5.32-4.dsc analog_5.32-4_i386.deb to pool/main/a/analog/analog_5.32-4_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fortune-mod 9708-29 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 17 Jun 2003 01:24:59 +1000 Source: fortune-mod Binary: fortunes-min fortune-mod fortunes-off fortunes Architecture: source all i386 Version: 9708-29 Distribution: unstable Urgency: low Maintainer: Pascal Hakim [EMAIL PROTECTED] Changed-By: Pascal Hakim [EMAIL PROTECTED] Description: fortune-mod - provides fortune cookies on demand fortunes - Data files containing fortune cookies fortunes-min - Data files containing fortune cookies fortunes-off - Data files containing offensive fortune cookies Closes: 95588 109167 157105 157171 159095 161741 165563 171114 178558 182613 191647 194346 195729 Changes: fortune-mod (9708-29) unstable; urgency=low . * datafile/linux: Added quote from debian-legal (closes: #194346) * fortune/fortune.c: Fixed copy to display proper paths in error messages. (Patch from William Steve Applegate [EMAIL PROTECTED]) (closes: #195729) * fortune/fortune.c: Search /usr/local/share/games for fortune files when a cookie file is specified. (Patch from Scott Wehrenberg [EMAIL PROTECTED]) (closes: #161741) * fortune/fortune.c: Exit cleanly on bad patterns instead of segfaulting. (Patch from Scott Wehrenberg [EMAIL PROTECTED]) (closes: #191647) * fortune/fortune.c: Don't search the local directory for languages (closes: #159095) * fortune/fortune.c: Changed the order in which LC_ALL and LC_MESSAGES are interpreted (closes: #157171) * fortune/fortune.c: Display a message when no appropriate fortunes have been found (closes: #165563) * datfiles/love:16: Removed duplicate entry (closes: #178558) * datfiles/translate-me: Added some translations. (Mostly thanks to Christian Kurz [EMAIL PROTECTED]) (closes: #182613) * datfiles/songs-poems:303: Fixed a typo in Gollum's riddle (closes: #157105) * datfiles/off/unrotated/limericks:5053: Removed a broken limeric. (closes: #171114) * fortune/fortune.c: New option: -c. Used to name the file from which the cookie came. (closes: #109167) * datfile/off/unrotated/atheism: Added new cookie file (closes: #95588) * Lintian changes: -Updated policy version -fixed description * Added some cookie files which weren't getting built to their directories makefile. Files: 39fb3cd4f67b4e4de1d58f5ac537ee7d 604 games optional fortune-mod_9708-29.dsc 3588f1e0bb73c841988f2496e4376d72 431431 games optional fortune-mod_9708-29.diff.gz 1052b766338270d327dddc64d7442371 68030 games optional fortunes-min_9708-29_all.deb 4736729d9746a68d86e70c689b5f1410 1085876 games optional fortunes_9708-29_all.deb 8c69fba9b6c6950788743eb67e9d649e 768570 games optional fortunes-off_9708-29_all.deb 4fc3b9201b2c43f1374f6a11b7ac6a33 41852 games optional fortune-mod_9708-29_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+7epv3+27IiW81b8RAgtFAKC5jGXwIVNGd4OK0Yb85zpMdSQbiACeKnOV oFlICPgsrgn5T9WQ5DKzqRs= =NOUY -END PGP SIGNATURE- Accepted: fortune-mod_9708-29.diff.gz to pool/main/f/fortune-mod/fortune-mod_9708-29.diff.gz fortune-mod_9708-29.dsc to pool/main/f/fortune-mod/fortune-mod_9708-29.dsc fortune-mod_9708-29_i386.deb to pool/main/f/fortune-mod/fortune-mod_9708-29_i386.deb fortunes-min_9708-29_all.deb to pool/main/f/fortune-mod/fortunes-min_9708-29_all.deb fortunes-off_9708-29_all.deb to pool/main/f/fortune-mod/fortunes-off_9708-29_all.deb fortunes_9708-29_all.deb to pool/main/f/fortune-mod/fortunes_9708-29_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted docbook-utils 0.6.13-2 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jun 2003 18:34:15 +0200 Source: docbook-utils Binary: docbook-utils Architecture: source all Version: 0.6.13-2 Distribution: unstable Urgency: low Maintainer: Christian Marillat [EMAIL PROTECTED] Changed-By: Christian Marillat [EMAIL PROTECTED] Description: docbook-utils - Convert Docbook files to other formats (HTML, RTF, PS, man, PDF) Closes: 197603 Changes: docbook-utils (0.6.13-2) unstable; urgency=low . * Remove my docbook hack, not necessary (Closes: #197603) Files: 61ba1ba75093d5861b4ca43f8fd5b007 636 text optional docbook-utils_0.6.13-2.dsc 78f3526ed54659d3030e5a8794881dea 5500 text optional docbook-utils_0.6.13-2.diff.gz effe946f17ef5ba2a9d1bb4e6d257736 71778 text optional docbook-utils_0.6.13-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+7fQxB9xWPR9BuQcRAvhlAKCI7Dxf/7UCQudFTZOZyeQlYCKFCwCeIG4S esisbNVWbjortFwt2dZexHs= =10KZ -END PGP SIGNATURE- Accepted: docbook-utils_0.6.13-2.diff.gz to pool/main/d/docbook-utils/docbook-utils_0.6.13-2.diff.gz docbook-utils_0.6.13-2.dsc to pool/main/d/docbook-utils/docbook-utils_0.6.13-2.dsc docbook-utils_0.6.13-2_all.deb to pool/main/d/docbook-utils/docbook-utils_0.6.13-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted db3 3.2.9-19 (all source ia64)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 16 Jun 2003 12:03:10 -0400
Source: db3
Binary: libdb3++c102 libdb3-util db3-doc libdb3++-dev libdb3-dev libdb3 libdb3-tcl
Architecture: source ia64 all
Version: 3.2.9-19
Distribution: unstable
Urgency: high
Maintainer: Matthew Wilcox [EMAIL PROTECTED]
Changed-By: Matthew Wilcox [EMAIL PROTECTED]
Description:
db3-doc- Berkeley v3 Database Documentation [html]
libdb3 - Berkeley v3 Database Libraries [runtime]
libdb3++-dev - Berkeley v3 Database Libraries for C++ [development]
libdb3++c102 - Berkeley v3 Database Libraries for C++ [runtime]
libdb3-dev - Berkeley v3 Database Libraries [development]
libdb3-tcl - Berkeley v3 Database Libraries for TCL [module]
libdb3-util - Berkeley v3 Database Utilities
Closes: 195049
Changes:
db3 (3.2.9-19) unstable; urgency=high
.
* Update config.{sub,guess}. Closes: #195049
Files:
bce97eaf43bc98950991fdb491bcbbf9 731 libs optional db3_3.2.9-19.dsc
935fb99d7cd4d2f419229b42b519ee8d 46490 libs optional db3_3.2.9-19.diff.gz
8ce1034548e2095901946c995e9f78d2 74028 utils optional libdb3-util_3.2.9-19_ia64.deb
f7469e947d2e7513ea5e291acdc475d6 438358 libs required libdb3_3.2.9-19_ia64.deb
948d8d4575e4741dd3c60da51783a779 560486 devel optional libdb3-dev_3.2.9-19_ia64.deb
fe916192198825e9e930c8318d107143 30146 libs optional libdb3++c102_3.2.9-19_ia64.deb
5ef74d4d4f8e47887db2309d567e6d1b 45626 devel optional libdb3++-dev_3.2.9-19_ia64.deb
8bdafd6e5a16fb1c9527307290887085 493288 interpreters extra
libdb3-tcl_3.2.9-19_ia64.deb
534f0c0b63450952f4e4f289cba8bb38 721696 doc extra db3-doc_3.2.9-19_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE+7fKsIhjIHo58A/8RAvtDAJ9eI7zapgJfdpAkI6rc9FWYQFG9uACePbH2
tkaMpjhUtv8ERxZYAHMdu5I=
=LBtZ
-END PGP SIGNATURE-
Accepted:
db3-doc_3.2.9-19_all.deb
to pool/main/d/db3/db3-doc_3.2.9-19_all.deb
db3_3.2.9-19.diff.gz
to pool/main/d/db3/db3_3.2.9-19.diff.gz
db3_3.2.9-19.dsc
to pool/main/d/db3/db3_3.2.9-19.dsc
libdb3++-dev_3.2.9-19_ia64.deb
to pool/main/d/db3/libdb3++-dev_3.2.9-19_ia64.deb
libdb3++c102_3.2.9-19_ia64.deb
to pool/main/d/db3/libdb3++c102_3.2.9-19_ia64.deb
libdb3-dev_3.2.9-19_ia64.deb
to pool/main/d/db3/libdb3-dev_3.2.9-19_ia64.deb
libdb3-tcl_3.2.9-19_ia64.deb
to pool/main/d/db3/libdb3-tcl_3.2.9-19_ia64.deb
libdb3-util_3.2.9-19_ia64.deb
to pool/main/d/db3/libdb3-util_3.2.9-19_ia64.deb
libdb3_3.2.9-19_ia64.deb
to pool/main/d/db3/libdb3_3.2.9-19_ia64.deb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted toshset 1.60-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jun 2003 18:18:45 +0200 Source: toshset Binary: toshset Architecture: source i386 Version: 1.60-1 Distribution: unstable Urgency: low Maintainer: Rene Engelhard [EMAIL PROTECTED] Changed-By: Rene Engelhard [EMAIL PROTECTED] Description: toshset- Access much of the Toshiba laptop hardware interface Closes: 196105 Changes: toshset (1.60-1) unstable; urgency=low . * new upstream release - updated machine ID description for 0xfc08 to display CDS/CDT (closes: #196105) * compile now with default g++ * include da.po for po-debconf from DDTP Files: 568ae6f8917d7fa4a6fb4ebbc64f7d74 594 admin optional toshset_1.60-1.dsc 86263362a828aaa27e7a81797d12364e 68099 admin optional toshset_1.60.orig.tar.gz 40b1e5eff83d89fa6a7d63ad5890e5d9 4875 admin optional toshset_1.60-1.diff.gz 2f119ddc758e8e06eb580c537216f2ad 44956 admin optional toshset_1.60-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+7fkH+FmQsCSK63MRAl7dAJ9oU31oIgFikdR/nYpcL3SePtRKAQCfY+0w jxKT64bnjDUPsttw2feMYcs= =ZhHf -END PGP SIGNATURE- Accepted: toshset_1.60-1.diff.gz to pool/main/t/toshset/toshset_1.60-1.diff.gz toshset_1.60-1.dsc to pool/main/t/toshset/toshset_1.60-1.dsc toshset_1.60-1_i386.deb to pool/main/t/toshset/toshset_1.60-1_i386.deb toshset_1.60.orig.tar.gz to pool/main/t/toshset/toshset_1.60.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gkrellm-mailwatch 2.4.2-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jun 2003 19:26:41 +0200 Source: gkrellm-mailwatch Binary: gkrellm-mailwatch Architecture: source i386 Version: 2.4.2-1 Distribution: unstable Urgency: low Maintainer: Sjoerd Simons [EMAIL PROTECTED] Changed-By: Sjoerd Simons [EMAIL PROTECTED] Description: gkrellm-mailwatch - GKrellM plugin to watch mailboxes in multiple panels Closes: 193380 Changes: gkrellm-mailwatch (2.4.2-1) unstable; urgency=low . * New upstream release - Fixes bug which caused new mailpanels not te be added (closes: Bug#193380) Files: 153b4e09f24f7fa576bded52fe74d608 624 mail optional gkrellm-mailwatch_2.4.2-1.dsc 6cda59b109cff38d83ac7fa9b187ba74 27121 mail optional gkrellm-mailwatch_2.4.2.orig.tar.gz 6239df8f7a7922183f378751d59900d9 2294 mail optional gkrellm-mailwatch_2.4.2-1.diff.gz df25a7b37d3bc8a15a728b04168ab969 19768 mail optional gkrellm-mailwatch_2.4.2-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+7f7fgTd+SodosdIRApYaAKClgl/P9Am64tvIzXBQjxePTKp3AACgtq7N 7jyLI1/DRyetYCfodVMxQlc= =1k1W -END PGP SIGNATURE- Accepted: gkrellm-mailwatch_2.4.2-1.diff.gz to pool/main/g/gkrellm-mailwatch/gkrellm-mailwatch_2.4.2-1.diff.gz gkrellm-mailwatch_2.4.2-1.dsc to pool/main/g/gkrellm-mailwatch/gkrellm-mailwatch_2.4.2-1.dsc gkrellm-mailwatch_2.4.2-1_i386.deb to pool/main/g/gkrellm-mailwatch/gkrellm-mailwatch_2.4.2-1_i386.deb gkrellm-mailwatch_2.4.2.orig.tar.gz to pool/main/g/gkrellm-mailwatch/gkrellm-mailwatch_2.4.2.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted toshset 1.60-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jun 2003 19:18:58 +0200 Source: toshset Binary: toshset Architecture: source i386 Version: 1.60-2 Distribution: unstable Urgency: low Maintainer: Rene Engelhard [EMAIL PROTECTED] Changed-By: Rene Engelhard [EMAIL PROTECTED] Description: toshset- Access much of the Toshiba laptop hardware interface Changes: toshset (1.60-2) unstable; urgency=low . * The Where-is-the-brown-papaer-bag release. * Build-Depend on gcc (= 3:3.0), g++ (= 3:3.0) as toshset does no compile with older ones anymore...; remove Build-Depends on gcc-2.95, g++-2.95 which were left over... * rm *-stamp in clean which was forgotten for the conversion to dpatch *sigh* Files: 8106c38d3a767cdca35b292b24f7471d 606 admin optional toshset_1.60-2.dsc c66f34debe58630505542f71c1042408 6740 admin optional toshset_1.60-2.diff.gz 56568145f0995b79fc654d31c9415e0b 44516 admin optional toshset_1.60-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+7f/i+FmQsCSK63MRAuJKAJwMCwqfwp7j1FJsUn+afIKqClY3vwCfVJkU 4DntRUObmrLX8khyqFLgWEQ= =2pxD -END PGP SIGNATURE- Accepted: toshset_1.60-2.diff.gz to pool/main/t/toshset/toshset_1.60-2.diff.gz toshset_1.60-2.dsc to pool/main/t/toshset/toshset_1.60-2.dsc toshset_1.60-2_i386.deb to pool/main/t/toshset/toshset_1.60-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted debhelper 4.1.47 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jun 2003 13:35:27 -0400 Source: debhelper Binary: debhelper Architecture: source all Version: 4.1.47 Distribution: unstable Urgency: low Maintainer: Joey Hess [EMAIL PROTECTED] Changed-By: Joey Hess [EMAIL PROTECTED] Description: debhelper - helper programs for debian/rules Closes: 196344 Changes: debhelper (4.1.47) unstable; urgency=low . * dh_install: recalculate automatic $dest eash time through the glob loop. It might change if there are multiple wildcards Closes: #196344 Files: a097299634ae7a4f1d192f462ba99194 573 devel optional debhelper_4.1.47.dsc d8dc0b931bea39665bc47256757e54f9 102190 devel optional debhelper_4.1.47.tar.gz 89d048d25503f52d2436acd22427e600 214674 devel optional debhelper_4.1.47_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+7ghn2tp5zXiKP0wRAvMcAKCw9ou+VPg6oV88vtdZBjNFCc65NwCgxSxr UGgbNi51aoObfFv45uWwDf4= =ezoe -END PGP SIGNATURE- Accepted: debhelper_4.1.47.dsc to pool/main/d/debhelper/debhelper_4.1.47.dsc debhelper_4.1.47.tar.gz to pool/main/d/debhelper/debhelper_4.1.47.tar.gz debhelper_4.1.47_all.deb to pool/main/d/debhelper/debhelper_4.1.47_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gkrellmms 2.1.11-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jun 2003 19:07:29 + Source: gkrellmms Binary: gkrellmms Architecture: source i386 Version: 2.1.11-1 Distribution: unstable Urgency: low Maintainer: Søren Boll Overgaard [EMAIL PROTECTED] Changed-By: Søren Boll Overgaard [EMAIL PROTECTED] Description: gkrellmms - GKrellM XMMS Plugin Changes: gkrellmms (2.1.11-1) unstable; urgency=low . * New upstream release Files: 77e4bbf6dcd297f4d745aec401b89ac3 635 sound optional gkrellmms_2.1.11-1.dsc 1d428e2e7ba77f5d18777dc1525a3db1 43998 sound optional gkrellmms_2.1.11.orig.tar.gz 995092e53f9d4e4dd0ec17f3a059f4f9 4028 sound optional gkrellmms_2.1.11-1.diff.gz 07a1130e51353a1bb4dd041e650db53b 53960 sound optional gkrellmms_2.1.11-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+7hZwPHuHUx6y3mYRAnCHAJ9kAWFZIQeafj5teQGCKO3TO+7YQwCfSupM tT6GcoXdScyEsElJ7A+dJ0o= =G/SN -END PGP SIGNATURE- Accepted: gkrellmms_2.1.11-1.diff.gz to pool/main/g/gkrellmms/gkrellmms_2.1.11-1.diff.gz gkrellmms_2.1.11-1.dsc to pool/main/g/gkrellmms/gkrellmms_2.1.11-1.dsc gkrellmms_2.1.11-1_i386.deb to pool/main/g/gkrellmms/gkrellmms_2.1.11-1_i386.deb gkrellmms_2.1.11.orig.tar.gz to pool/main/g/gkrellmms/gkrellmms_2.1.11.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted xbanner 1.31-22.1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 14 Jun 2003 09:03:06 +0200 Source: xbanner Binary: xbanner Architecture: source i386 Version: 1.31-22.1 Distribution: unstable Urgency: low Maintainer: Stephen Zander [EMAIL PROTECTED] Changed-By: Christian Perrier [EMAIL PROTECTED] Description: xbanner- Beautify your X login screen Closes: 186279 187300 Changes: xbanner (1.31-22.1) unstable; urgency=low . * NMU * Corrected typo in templates. Closes: #186279 * French debconf templates. Closes: #187300 Files: fb3db706c1fd621a252836d77d78e580 587 x11 optional xbanner_1.31-22.1.dsc 6ab5fc8838cdab279217cb31c7f85997 14289 x11 optional xbanner_1.31-22.1.diff.gz a9ceee8f6fd8dda0a8534754506869a9 138322 x11 optional xbanner_1.31-22.1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+7JZYiONoszDJNIoRAj7/AJ4yKipkonGL5cs7aRBkMsK4mr/U2QCfbt4m vR+hDCH/9vLJ7IdhwnlIzTU= =Y4AN -END PGP SIGNATURE- Accepted: xbanner_1.31-22.1.diff.gz to pool/main/x/xbanner/xbanner_1.31-22.1.diff.gz xbanner_1.31-22.1.dsc to pool/main/x/xbanner/xbanner_1.31-22.1.dsc xbanner_1.31-22.1_i386.deb to pool/main/x/xbanner/xbanner_1.31-22.1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted stunnel 4.04-4 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jun 2003 22:04:17 +0200 Source: stunnel Binary: stunnel Architecture: source i386 Version: 4.04-4 Distribution: unstable Urgency: low Maintainer: Julien LEMOINE [EMAIL PROTECTED] Changed-By: Julien LEMOINE [EMAIL PROTECTED] Description: stunnel- Universal SSL tunnel for network daemons Closes: 197615 197663 Changes: stunnel (4.04-4) unstable; urgency=low . * Added /etc/default/stunnel with a variable ENABLE. ENABLE=0 by default since stunnel segv on some computer when all lines are commented (Closes: #197663, #197615) Files: b9cebe4d42f643695cfeebb91bfea155 592 net optional stunnel_4.04-4.dsc e70cf5688615d5ff8e3acdfbe5e1c16e 6052 net optional stunnel_4.04-4.diff.gz deca83e5e3addc416917130b58bfe6f1 59858 net optional stunnel_4.04-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+7iVQc29c8N2YKnURAlFiAJ9KJaarRsiMrYv8RqUySEVRUbSe9gCfVYOq eVBxleN3gxRls4SeFZENthc= =P85Q -END PGP SIGNATURE- Accepted: stunnel_4.04-4.diff.gz to pool/main/s/stunnel/stunnel_4.04-4.diff.gz stunnel_4.04-4.dsc to pool/main/s/stunnel/stunnel_4.04-4.dsc stunnel_4.04-4_i386.deb to pool/main/s/stunnel/stunnel_4.04-4_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted newt 0.51.4-10 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jun 2003 20:54:30 +0100 Source: newt Binary: libnewt-dev libnewt-pic libnewt0.51 newt-tcl whiptail python-newt Architecture: source i386 Version: 0.51.4-10 Distribution: unstable Urgency: low Maintainer: Alastair McKinstry [EMAIL PROTECTED] Changed-By: Alastair McKinstry [EMAIL PROTECTED] Description: libnewt-dev - Developer's toolkit for newt windowing library libnewt-pic - Not Erik's Windowing Toolkit, shared library subset kit libnewt0.51 - Not Erik's Windowing Toolkit - text mode windowing with slang newt-tcl - A newt module for Tcl python-newt - A NEWT module for Python whiptail - Displays user-friendly dialog boxes from shell scripts Closes: 49352 49796 67356 196290 196570 Changes: newt (0.51.4-10) unstable; urgency=low . * libnewt0.51 replaces libnewt0, libnewt-utf8; whiptail can also use tcl8.4 Closes: #196570. * Add README.whiptail to document the purpose of whiptail. Closes: #67356. * --default-item option added to whiptail, whiptcl. Closes: #49352, #49796. * Added shlibs fix from Daniel Schepler for whiptail dependency on alpha. Closes: #196290. * malloc, realloc failures in whiptail, whiptcl now generate a DLG_ERROR return, not a segfault. Files: 4d0d75ebd4553fd0f0e9e98898275a69 741 devel optional newt_0.51.4-10.dsc 81230a5ba190977c42e520e631f2e5eb 62979 devel optional newt_0.51.4-10.diff.gz 0765daecf59dcfb5153affb4d2664697 44520 base standard libnewt0.51_0.51.4-10_i386.deb d3fbbb74b4c2d4febeab79f708bba8a7 67552 libdevel optional libnewt-dev_0.51.4-10_i386.deb 9ebab194fad4b33db3b7a14ea9e0d4a5 46360 libdevel extra libnewt-pic_0.51.4-10_i386.deb dda9b586f96dabc58aa30871405542c1 21864 interpreters extra newt-tcl_0.51.4-10_i386.deb c45d065033e2119dbff88cf8c45bb86f 29072 python standard python-newt_0.51.4-10_i386.deb b19dc6d6502096cb37d7a21dd4e1509e 26828 base standard whiptail_0.51.4-10_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+7iMZ+o43kJBROPQRAlehAJ9gi6xxzIfBR+1bIRBT7KujGC/GoACgs9Nj Su66bTgB4V2WZlg4Pk8n5jg= =75z8 -END PGP SIGNATURE- Accepted: libnewt-dev_0.51.4-10_i386.deb to pool/main/n/newt/libnewt-dev_0.51.4-10_i386.deb libnewt-pic_0.51.4-10_i386.deb to pool/main/n/newt/libnewt-pic_0.51.4-10_i386.deb libnewt0.51_0.51.4-10_i386.deb to pool/main/n/newt/libnewt0.51_0.51.4-10_i386.deb newt-tcl_0.51.4-10_i386.deb to pool/main/n/newt/newt-tcl_0.51.4-10_i386.deb newt_0.51.4-10.diff.gz to pool/main/n/newt/newt_0.51.4-10.diff.gz newt_0.51.4-10.dsc to pool/main/n/newt/newt_0.51.4-10.dsc python-newt_0.51.4-10_i386.deb to pool/main/n/newt/python-newt_0.51.4-10_i386.deb whiptail_0.51.4-10_i386.deb to pool/main/n/newt/whiptail_0.51.4-10_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cacti 0.6.8a-13.1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jun 2003 22:54:11 +0200 Source: cacti Binary: cacti Architecture: source all Version: 0.6.8a-13.1 Distribution: unstable Urgency: low Maintainer: Debian QA Group [EMAIL PROTECTED] Changed-By: Christian Perrier [EMAIL PROTECTED] Description: cacti - Frontend to rrdtool for monitoring systems and services Closes: 189401 197119 Changes: cacti (0.6.8a-13.1) unstable; urgency=low . * NMU * Rewrote debconf templates to more standard english with the help of debian-l10n-english. Former templates have been left for future reference Closes: #189401 * French debconf templates update. Closes: #197119 * More secure temp file handling in postrm. Thanks lintian. Files: 495787e1d109137e64d86bdc10d28244 590 web extra cacti_0.6.8a-13.1.dsc f6acaec65b7388e1df7b48ada646c1f2 35492 web extra cacti_0.6.8a-13.1.diff.gz 84d61cb48fe2129e90425ece73ca8508 215052 web extra cacti_0.6.8a-13.1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+7i6riONoszDJNIoRAksQAJ9yM3sdNXIWOvwyLnCgvDIsbl29QwCeJ4fw RNGCHp+g8wbGq6vz9cMZuuM= =OYQm -END PGP SIGNATURE- Accepted: cacti_0.6.8a-13.1.diff.gz to pool/main/c/cacti/cacti_0.6.8a-13.1.diff.gz cacti_0.6.8a-13.1.dsc to pool/main/c/cacti/cacti_0.6.8a-13.1.dsc cacti_0.6.8a-13.1_all.deb to pool/main/c/cacti/cacti_0.6.8a-13.1_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted caudium 2:1.2.27-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 3 Jun 2003 00:47:58 +0200 Source: caudium Binary: caudium-ultralog caudium-pixsl caudium-perl caudium caudium-dev caudium-modules Architecture: source i386 Version: 2:1.2.27-1 Distribution: unstable Urgency: low Maintainer: Marek Habersack [EMAIL PROTECTED] Changed-By: Marek Habersack [EMAIL PROTECTED] Description: caudium- An extensible WWW server written in Pike caudium-dev - Development files for Caudium caudium-modules - C modules for Caudium caudium-perl - Perl script support for Caudium caudium-pixsl - Pike XSLT module for Caudium caudium-ultralog - Log Parser module for Caudium Closes: 195890 197541 Changes: caudium (2:1.2.27-1) unstable; urgency=low . * Added the Brazilian Portuguese translation of the debconf templates provided by Andre Luis Lopes. Thank you. (closes: Bug#197541) * Updated and fixed the setools.pike module * Latest upstream version * Updated the French templates translation thanks to Philippe Batailler and the debian-l10n-french subscribers (closes: Bug#195890) Files: 6c28fb633ed785f524d4ed098344ac78 772 web optional caudium_1.2.27-1.dsc 0a186513b9df1f8d77f3bc810025cddb 3029368 web optional caudium_1.2.27.orig.tar.gz e427b98e17ce02750c5130102b6d0c7f 20 web optional caudium_1.2.27-1.diff.gz ae44046c56210bce3944e14c3dd90b40 2760342 web optional caudium_1.2.27-1_i386.deb 24e9847707ca7c79cfcae6941654cbee 31852 web optional caudium-modules_1.2.27-1_i386.deb b93c1fdf96c63821197d826d4aa7974e 28660 web optional caudium-pixsl_1.2.27-1_i386.deb 25ee575097614f18f1244b9b0a50d280 67128 web optional caudium-ultralog_1.2.27-1_i386.deb 245a626290b0a896f93248e6616df7bd 17270 devel optional caudium-dev_1.2.27-1_i386.deb 43b91d8210334df16f63d9c977d17e15 24658 web optional caudium-perl_1.2.27-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+7jB/q3909GIf5uoRAgTiAJ9qKI+LdqhDCxOKbs2CNuTPAqhbtgCbBQC7 MEsRGwY8JqdruA3fAPShulA= =RGK8 -END PGP SIGNATURE- Accepted: caudium-dev_1.2.27-1_i386.deb to pool/main/c/caudium/caudium-dev_1.2.27-1_i386.deb caudium-modules_1.2.27-1_i386.deb to pool/main/c/caudium/caudium-modules_1.2.27-1_i386.deb caudium-perl_1.2.27-1_i386.deb to pool/main/c/caudium/caudium-perl_1.2.27-1_i386.deb caudium-pixsl_1.2.27-1_i386.deb to pool/main/c/caudium/caudium-pixsl_1.2.27-1_i386.deb caudium-ultralog_1.2.27-1_i386.deb to pool/main/c/caudium/caudium-ultralog_1.2.27-1_i386.deb caudium_1.2.27-1.diff.gz to pool/main/c/caudium/caudium_1.2.27-1.diff.gz caudium_1.2.27-1.dsc to pool/main/c/caudium/caudium_1.2.27-1.dsc caudium_1.2.27-1_i386.deb to pool/main/c/caudium/caudium_1.2.27-1_i386.deb caudium_1.2.27.orig.tar.gz to pool/main/c/caudium/caudium_1.2.27.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libber 0.2.4 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jun 2003 18:57:25 +0200 Source: libber Binary: libber0-dev libber0 Architecture: source i386 Version: 0.2.4 Distribution: unstable Urgency: low Maintainer: Abraham vd Merwe [EMAIL PROTECTED] Changed-By: Abraham vd Merwe [EMAIL PROTECTED] Description: libber0- A Basic Encoding Rules (ITU X.690) implementation libber0-dev - Development files for the ber library Closes: 197629 Changes: libber (0.2.4) unstable; urgency=low . * Changed libber0-dev section. * Fixed integer encoding/decoding routines (Closes: #197629) Files: 0e53d3dceb88d39a2ca6209b7f5610d8 570 devel optional libber_0.2.4.dsc 7b8475ed7d763624d47044a5b347d859 12935 devel optional libber_0.2.4.tar.gz abaa76f986c01980608aa0ce225967c2 7278 libs optional libber0_0.2.4_i386.deb 81b0bcb3f16c52331cb5b58ef8879c73 12556 libdevel optional libber0-dev_0.2.4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.5 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE+7fdhzvVjZitVWu4RAoPOAJ4n67NAMcQRRr6pewHd5M26VMltUQCeMGbU Jhxji0tpdkF3N42qBeq9KyA= =F10G -END PGP SIGNATURE- Accepted: libber0-dev_0.2.4_i386.deb to pool/main/libb/libber/libber0-dev_0.2.4_i386.deb libber0_0.2.4_i386.deb to pool/main/libb/libber/libber0_0.2.4_i386.deb libber_0.2.4.dsc to pool/main/libb/libber/libber_0.2.4.dsc libber_0.2.4.tar.gz to pool/main/libb/libber/libber_0.2.4.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted tint 0.03a (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jun 2003 23:07:37 +0200 Source: tint Binary: tint Architecture: source i386 Version: 0.03a Distribution: unstable Urgency: low Maintainer: Abraham van der Merwe [EMAIL PROTECTED] Changed-By: Abraham van der Merwe [EMAIL PROTECTED] Description: tint - TINT Is Not Tetris(tm) ...at least the name isn't Changes: tint (0.03a) unstable; urgency=low . * Applied patch with some minor tweaks from Marcello Mamino which adds a dotted background. * Applied patches from Robert Lemmen which add support for user logins as default name and an interactive mode for specifying the start level. * Show player statistics. Files: 5c910c6d10e24b75ca9b0cc5ca22aa63 546 games optional tint_0.03a.dsc e89e47bafcd3be1184b3e334927a5a79 16781 games optional tint_0.03a.tar.gz bcaa4bf1675bda880cf3baeb262b9e25 14298 games optional tint_0.03a_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.5 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE+7jLKzvVjZitVWu4RAu3KAKCCKfO7WYjV+WoOU+FTv+RRls33ggCgsnmQ sJm2H2Pph/oMwg1+j9KIQPg= =vQ5G -END PGP SIGNATURE- Accepted: tint_0.03a.dsc to pool/main/t/tint/tint_0.03a.dsc tint_0.03a.tar.gz to pool/main/t/tint/tint_0.03a.tar.gz tint_0.03a_i386.deb to pool/main/t/tint/tint_0.03a_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gkrellmms 2.1.12-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jun 2003 21:34:21 + Source: gkrellmms Binary: gkrellmms Architecture: source i386 Version: 2.1.12-1 Distribution: unstable Urgency: low Maintainer: Søren Boll Overgaard [EMAIL PROTECTED] Changed-By: Søren Boll Overgaard [EMAIL PROTECTED] Description: gkrellmms - GKrellM XMMS Plugin Changes: gkrellmms (2.1.12-1) unstable; urgency=low . * New upstream release Files: 651985bb4b87760510bf3a327d5f205e 635 sound optional gkrellmms_2.1.12-1.dsc e4e6ed080d08ef9f5f7677becd01981d 46723 sound optional gkrellmms_2.1.12.orig.tar.gz 7dc6ab98f0c9c9f8cc4c38382f0ff5d0 3901 sound optional gkrellmms_2.1.12-1.diff.gz 52fa262bd1f6adc979ac8f0ae48310e2 54106 sound optional gkrellmms_2.1.12-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+7jilPHuHUx6y3mYRAkuhAJ9NYp2Xy/N/mVft3+sGoYzNu2ydFQCdEtvt FkhJc8FfkrTPvqiqLUGDi3s= =AzWe -END PGP SIGNATURE- Accepted: gkrellmms_2.1.12-1.diff.gz to pool/main/g/gkrellmms/gkrellmms_2.1.12-1.diff.gz gkrellmms_2.1.12-1.dsc to pool/main/g/gkrellmms/gkrellmms_2.1.12-1.dsc gkrellmms_2.1.12-1_i386.deb to pool/main/g/gkrellmms/gkrellmms_2.1.12-1_i386.deb gkrellmms_2.1.12.orig.tar.gz to pool/main/g/gkrellmms/gkrellmms_2.1.12.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted tinysnmp 0.5.1 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jun 2003 20:27:10 +0200 Source: tinysnmp Binary: tinysnmp-module-resources tinysnmp-module-mib2 tinysnmp-manager-dev trafficd tinysnmp-module-traffic tinysnmp-agent-dev tinysnmp-agent tinysnmp-tools tinysnmp-dev Architecture: source i386 all Version: 0.5.1 Distribution: unstable Urgency: low Maintainer: Abraham vd Merwe [EMAIL PROTECTED] Changed-By: Abraham vd Merwe [EMAIL PROTECTED] Description: tinysnmp-agent - A lightweight SNMPv1 implementation tinysnmp-agent-dev - Libraries and header files for developing TinySNMP plugins tinysnmp-dev - Files needed for developing TinySNMP programs and plugins tinysnmp-manager-dev - Libraries and header files for developing TinySNMP programs tinysnmp-module-mib2 - MIB-2 (RFC 1450) plugin for TinySNMP tinysnmp-module-resources - Frogfoot Networks Resources MIB plugin for TinySNMP tinysnmp-module-traffic - Frogfoot Networks Quality of Service plugin for TinySNMP tinysnmp-tools - TinySNMP Utilities trafficd - Frogfoot Networks Quality of Service daemon Closes: 188922 Changes: tinysnmp (0.5.1) unstable; urgency=low . * Compile static libraries with -fPIC (Closes: #188922) * Minor bugfix in snmp manager library. * Added max-rows option to snmp_get_table(). * snmp_table_t now contains the ObjectID's of each row. * Fixed Frogfoot MIBs (thanks to smilint). Files: e0830cfb5bc6b013a5237fbee27f71df 799 net optional tinysnmp_0.5.1.dsc 2a1cbc14a707abedcb4d5f0a71a336fa 86256 net optional tinysnmp_0.5.1.tar.gz 6303e11177e56807d8b8df8fe8f3b14f 7880 devel optional tinysnmp-agent-dev_0.5.1_all.deb 77ad8576ae6a3272dafffbbd50354cc2 9510 devel optional tinysnmp-dev_0.5.1_i386.deb 57763c485279966754c4b5989dada8ba 12128 devel optional tinysnmp-manager-dev_0.5.1_i386.deb ffa5e071e3f6038b3496dcde7bea971f 23952 net optional tinysnmp-tools_0.5.1_i386.deb da0700ee86ea8848bea28c7ea8a814e9 25624 net optional tinysnmp-agent_0.5.1_i386.deb ca3bc168ca53ab990189ac6a4cc62b61 12650 net optional tinysnmp-module-mib2_0.5.1_i386.deb d0afe0475931346c98fd8926f9ef23b5 9210 net optional tinysnmp-module-resources_0.5.1_i386.deb 4c825e8912e4737008cdfbe976ff6c07 13754 net optional tinysnmp-module-traffic_0.5.1_i386.deb a9ef6efb1622882b1ed6638bac7e4fde 24658 net optional trafficd_0.5.1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.5 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE+7jY2zvVjZitVWu4RAsTCAJ9gCJ6iZtwooUbY2KvxjzUXTg2aGACfbYzg luplX5nWLTopeD7dNqJggiw= =soN9 -END PGP SIGNATURE- Accepted: tinysnmp-agent-dev_0.5.1_all.deb to pool/main/t/tinysnmp/tinysnmp-agent-dev_0.5.1_all.deb tinysnmp-agent_0.5.1_i386.deb to pool/main/t/tinysnmp/tinysnmp-agent_0.5.1_i386.deb tinysnmp-dev_0.5.1_i386.deb to pool/main/t/tinysnmp/tinysnmp-dev_0.5.1_i386.deb tinysnmp-manager-dev_0.5.1_i386.deb to pool/main/t/tinysnmp/tinysnmp-manager-dev_0.5.1_i386.deb tinysnmp-module-mib2_0.5.1_i386.deb to pool/main/t/tinysnmp/tinysnmp-module-mib2_0.5.1_i386.deb tinysnmp-module-resources_0.5.1_i386.deb to pool/main/t/tinysnmp/tinysnmp-module-resources_0.5.1_i386.deb tinysnmp-module-traffic_0.5.1_i386.deb to pool/main/t/tinysnmp/tinysnmp-module-traffic_0.5.1_i386.deb tinysnmp-tools_0.5.1_i386.deb to pool/main/t/tinysnmp/tinysnmp-tools_0.5.1_i386.deb tinysnmp_0.5.1.dsc to pool/main/t/tinysnmp/tinysnmp_0.5.1.dsc tinysnmp_0.5.1.tar.gz to pool/main/t/tinysnmp/tinysnmp_0.5.1.tar.gz trafficd_0.5.1_i386.deb to pool/main/t/tinysnmp/trafficd_0.5.1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted coreutils 5.0-4 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Format: 1.7 Date: Mon, 16 Jun 2003 17:34:51 -0400 Source: coreutils Binary: shellutils coreutils fileutils textutils Architecture: source all i386 Version: 5.0-4 Distribution: unstable Urgency: medium Maintainer: Michael Stone [EMAIL PROTECTED] Changed-By: Michael Stone [EMAIL PROTECTED] Description: coreutils - The GNU core utilities fileutils - The GNU file management utilities (transitional package) shellutils - The GNU shell programming utilities (transitional package) textutils - The GNU text file processing utilities (transitional package) Closes: 197655 Changes: coreutils (5.0-4) unstable; urgency=medium . * upstream patch to prevent fd leak (Closes: #197655) Files: 1d89b996e6d881ef2bd49643a703ade9 803 base required coreutils_5.0-4.dsc bb4045f4d2db00c947d54cc482355864 22300 base required coreutils_5.0-4.diff.gz ec3edff75778febe7b606b131b0746e9 4298 oldlibs extra textutils_5.0-4_all.deb 1f0896d2d78caf8c5b4015c232a2e6b0 4296 oldlibs extra fileutils_5.0-4_all.deb c30d059a4a6aaa86fb0f79c940685625 4298 oldlibs extra shellutils_5.0-4_all.deb 12f43442e4046f27e8995c4db1d03ad9 2263174 base required coreutils_5.0-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iQCVAwUBPu4+9Q0hVr09l8FJAQEIDQQAlcfTa44nENBNpguA7tSUjeNf7kiQqqPx HKjlXL6x4Mit9sILBPuSRscp6LIwjk3m91JX+fA+P5nbuO8SapZiAxn5x5TgMJ7a 2mvojmXjF3XLVJN8lPWhLFkd8tkOCOG3CY54ake1w9NAE3c8SlkLVWm8WS+9M5PQ 5JZz5Wsd9Hg= =edS6 -END PGP SIGNATURE- Accepted: coreutils_5.0-4.diff.gz to pool/main/c/coreutils/coreutils_5.0-4.diff.gz coreutils_5.0-4.dsc to pool/main/c/coreutils/coreutils_5.0-4.dsc coreutils_5.0-4_i386.deb to pool/main/c/coreutils/coreutils_5.0-4_i386.deb fileutils_5.0-4_all.deb to pool/main/c/coreutils/fileutils_5.0-4_all.deb shellutils_5.0-4_all.deb to pool/main/c/coreutils/shellutils_5.0-4_all.deb textutils_5.0-4_all.deb to pool/main/c/coreutils/textutils_5.0-4_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted chrpath 0.10-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 17 Jun 2003 00:18:37 +0200 Source: chrpath Binary: chrpath Architecture: source i386 Version: 0.10-2 Distribution: unstable Urgency: low Maintainer: Tollef Fog Heen [EMAIL PROTECTED] Changed-By: Tollef Fog Heen [EMAIL PROTECTED] Description: chrpath- Tool to edit the rpath in ELF binaries Closes: 179923 197210 Changes: chrpath (0.10-2) unstable; urgency=low . * Fix description (closes: #179923). * Make chrpath work well on 64 bit arches. (closes: #197210) * Make build also run make check Files: aab23b39681ad76b013014da8b0f313a 559 utils optional chrpath_0.10-2.dsc b74bcd8610b58c646a7352081f97a2dc 2898 utils optional chrpath_0.10-2.diff.gz d0c496c6da001439c6d21dd373115eca 11202 utils optional chrpath_0.10-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+7kJcQSseMYF6mWoRAvI3AJ9n14Num70BqOCBJew0qltaGbDR2wCfQLUe 16UQTUvsqvH8OESZY+ii6UA= =Mufb -END PGP SIGNATURE- Accepted: chrpath_0.10-2.diff.gz to pool/main/c/chrpath/chrpath_0.10-2.diff.gz chrpath_0.10-2.dsc to pool/main/c/chrpath/chrpath_0.10-2.dsc chrpath_0.10-2_i386.deb to pool/main/c/chrpath/chrpath_0.10-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gtkmm2.0 2.2.3-1 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jun 2003 14:07:56 -0700 Source: gtkmm2.0 Binary: libgtkmm2.0-1c102 libgtkmm2.0-doc libgtkmm2.0-dev Architecture: source i386 all Version: 2.2.3-1 Distribution: unstable Urgency: low Maintainer: Bradley Bell [EMAIL PROTECTED] Changed-By: Bradley Bell [EMAIL PROTECTED] Description: libgtkmm2.0-1c102 - C++ wrappers for GTK+ 2.0 (shared libraries) libgtkmm2.0-dev - C++ wrappers for GTK+ 2.0 (development files) libgtkmm2.0-doc - C++ wrappers for GTK+ 2.0 (documentation) Changes: gtkmm2.0 (2.2.3-1) unstable; urgency=low . * New upstream release Files: 7e33d1ae9a7d2d36f6d9b1719990cb24 685 libs optional gtkmm2.0_2.2.3-1.dsc 856cb403530c3d8afab37c986fb81129 5178982 libs optional gtkmm2.0_2.2.3.orig.tar.gz d2b643b708cee0de625b03dad28b87df 249637 libs optional gtkmm2.0_2.2.3-1.diff.gz 0f4b7bc58ad0aae0491c78eaec0e81d7 3266922 doc optional libgtkmm2.0-doc_2.2.3-1_all.deb 0304a01a8d117257f0ae258642cd83ca 1547150 libdevel optional libgtkmm2.0-dev_2.2.3-1_i386.deb 037828f2a568a7bc71a2e39ceb140fdd 910626 libs optional libgtkmm2.0-1c102_2.2.3-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+7kMnteAcXeZ40aERAhm6AKDQx40VICpjwkDV3p3pDk6aT7ey8wCfSuH1 Nn2IeGS3MPo7ud/ees/ofnQ= =ciZD -END PGP SIGNATURE- Accepted: gtkmm2.0_2.2.3-1.diff.gz to pool/main/g/gtkmm2.0/gtkmm2.0_2.2.3-1.diff.gz gtkmm2.0_2.2.3-1.dsc to pool/main/g/gtkmm2.0/gtkmm2.0_2.2.3-1.dsc gtkmm2.0_2.2.3.orig.tar.gz to pool/main/g/gtkmm2.0/gtkmm2.0_2.2.3.orig.tar.gz libgtkmm2.0-1c102_2.2.3-1_i386.deb to pool/main/g/gtkmm2.0/libgtkmm2.0-1c102_2.2.3-1_i386.deb libgtkmm2.0-dev_2.2.3-1_i386.deb to pool/main/g/gtkmm2.0/libgtkmm2.0-dev_2.2.3-1_i386.deb libgtkmm2.0-doc_2.2.3-1_all.deb to pool/main/g/gtkmm2.0/libgtkmm2.0-doc_2.2.3-1_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
