salut
[EMAIL PROTECTED] voici le site des carte virtuelle dont je t\'ai parlé: http://www.allopass.com/check/red.php4?CA=X212863LRBR56A -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#357927: ITP: freepbx -- web based management tool for asterisk, replacement for amp
Package: wnpp Severity: wishlist Owner: Stephen Birch [EMAIL PROTECTED] * Package name: freepbx Version : 2.0.1 Upstream Author : jason_d_becker, rcourtna, tcourtna, etc * URL : http://sourceforge.net/projects/amportal/ * License : GPS Description : web management tool for Asterisk VoIP PBX, replacement for AMP Coalescent Systems Inc. launched the freePBX (formerly Asterisk Management Portal, AMP) project to bring together best-of-breed applications to produce a standardized implementation of Asterisk complete with web-based administrative interface. This is a web based tool used to manage an Asterisk installation, setting up extensions, call routes, answering services etc. -- System Information: Debian Release: etch Architecture: All Kernel: Linux 2.6.8-2-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: The problem with killfiles, and other musings [Was: Re: removal of svenl from the project]
On Sun, Mar 19, 2006 at 12:28:14PM +0100, Sven Luther wrote: I was going to make a large answer where i was going to denouse the inexactitudes and false claims of this clearly inflamatory mail, but i will refrain from doing so. I wonder if Steve, and others of the 'esteemed' DDs, is following his own advice, and rereading the mails he writes, and if so, why did he need to add such a great amount of ad-hominem attacks again, and what was the added value it did bring to his point. So Sven is going to continue to be used here as an illustrative example, not because I want to pick on Sven, but because I want to demonstrate the plausibility of the problem I'm talking about. This was *not about you*. I was not expressing support for expelling you from the project, I was addressing the fallacious claim that killfiling people we don't get along with is a fix for conflict. I'm sorry if you felt attacked by my mail, but not only was it not ad-hominem (since you were not making an argument, I could hardly be trying to undercut a non-argument by attacking your character!), it wasn't a criticism of you *at all*. It was only an enumeration of people in the project that I know you have (or have had) an antagonistic relationship with, and a brief explanation of the source of those conflicts. It is a list of people in the project that, if we were playing by Jonas's rules, I think *might* wish to killfile you. I don't see why you should be mad at *me* that I'm able to think of so many people to put in that category. There are others in the project people have a difficult time working with, including some of the respected and eminent guys, but nobody would dare expulse them for it, or even critic. We weren't talking about expulsions or criticism, we were talking about killfiling. I guess I could use myself as an example here instead of you, and hypothesize about a group of developers killfiling me in response to the Vancouver proposal; but killfiling someone just because of a technical decision you disagree with is even more absurd, and I don't think even Jonas was suggesting that. I mean, Steve mentioned the debian-legal thing, but failed to mention that part of my involvement with debian-legal (over the ocaml issue, but previously the XFree86 licence mess), made me the receiving end of a irc-witch-hunt from branden assufield and a few others i don't remember, which would have made andres have an heart attack had he seen it. Er... how exactly does that invalidate my point about who might want to killfile you in Jonas's world? Do you think that your suffering on IRC negates others' feelings about whether they find you difficult to work with? Do you think it would be an improvement if, before sending my mail, I had gotten affidavits from each of the people mentioned, stating how they feel towards you? And aren't your follow-ups here a perfect example of why people complain about you personalizing all discussions? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
one binary package created by different source packages, will the old source package disappear?
Hi, assume the following scenario: - Source package foo creates binary packages libfoo1 and libfoo-dev - source package foo2 creates binary packages libfoo2 and libfoo2-dev Since both versions are API-compatible, libfoo2-dev is renamed to foo-dev, replacing the old binary package from source package foo. Will the complete source package foo have to disappear, or will foo and the binary package libfoo1 continue to be available? TIA, Frank -- Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX)
Re: one binary package created by different source packages, will the old source package disappear?
On Mon, Mar 20, 2006 at 12:03:13PM +0100, Frank Küster [EMAIL PROTECTED] wrote: Hi, assume the following scenario: - Source package foo creates binary packages libfoo1 and libfoo-dev - source package foo2 creates binary packages libfoo2 and libfoo2-dev Since both versions are API-compatible, libfoo2-dev is renamed to foo-dev, replacing the old binary package from source package foo. Will the complete source package foo have to disappear, or will foo and the binary package libfoo1 continue to be available? Everything will be available until you ask removal to ftp masters. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
library for imap (client)
Hello *, Currently I am starting a new project and want to know, if someone know the existence if an imapclient library for C programing? I do not realy want to reinvent the wheel. Or should I steal the routines from other IMAP clients? Greetings Michelle Konzack -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ # Debian GNU/Linux Consultant # Michelle Konzack Apt. 917 ICQ #328449886 50, rue de Soultz MSM LinuxMichi 0033/3/8845235667100 Strasbourg/France IRC #Debian (irc.icq.com) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: library for imap (client)
On Sat, Mar 18, 2006 at 03:49:07PM +0100, Michelle Konzack wrote: Currently I am starting a new project and want to know, if someone know the existence if an imapclient library for C programing? libc-client with some limitations... -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: library for imap (client)
On 18-Mar-06, 08:49 (CST), Michelle Konzack [EMAIL PROTECTED] wrote: Currently I am starting a new project and want to know, if someone know the existence if an imapclient library for C programing? Michelle, please meet http://www.google.com. Google, meet Michelle. Steve -- Steve Greenland The irony is that Bill Gates claims to be making a stable operating system and Linus Torvalds claims to be trying to take over the world. -- seen on the net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: one binary package created by different source packages, will the old source package disappear?
Scripsit Frank Küster [EMAIL PROTECTED] - Source package foo creates binary packages libfoo1 and libfoo-dev - source package foo2 creates binary packages libfoo2 and libfoo2-dev Since both versions are API-compatible, libfoo2-dev is renamed to foo-dev, replacing the old binary package from source package foo. Will the complete source package foo have to disappear, It absolutely _should_, or be reuploaded with new control and rules files to create only libfoo1. Otherwise an attempt to recompile source package foo (say, for a security fix) risks replacing the new libfoo-dev with an older one. Probably a better solution would be to rename libfoo-dev to libfoo1-dev such that if packages that link to libfoo1 reach stable there will still be a way to rebuild them for security updates without adding the new-bug risks of switching to a new implementation of the library. -- Henning MakholmIt's kind of scary. Win a revolution and a bunch of lawyers pop out of the woodwork. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: one binary package created by different source packages, will the old source package disappear?
On Mon, Mar 20, 2006 at 12:03:13PM +0100, Frank Küster wrote: Hi, assume the following scenario: - Source package foo creates binary packages libfoo1 and libfoo-dev - source package foo2 creates binary packages libfoo2 and libfoo2-dev Since both versions are API-compatible, libfoo2-dev is renamed to foo-dev, replacing the old binary package from source package foo. Will the complete source package foo have to disappear, or will foo and the binary package libfoo1 continue to be available? If foo2 didn't exist yet, you'd most likely want to start your transition by having a new 'foo' instead, creating libfoo2 and libfoo-dev. (ABI/SONAME change, but no API change, so -dev remains named the same). Transition can be done mostly/totally via binnmu's, and libfoo1 will be semi-automatically dropped. If foo2 already exists, I'd still go for that solution, but you'll then need to ask for foo2 removal via a bug to ftp.debian.org. Because there is API compatibility, I'm assuming here it makes not much sense to keep both libraries in at the same time. If you want to keep libfoo1 available (would need a somewhat decent reason, ideally), you'll need separate source package names (indeed foo2 then), and will need to make a new upload of 'foo' stopping to provide a -dev package. Otherwise, ít'll be impossible to do security uploads without making those changes at that time -- however, libfoo1 will remain available, even lacking such upload. N.B.: Such questions are easier to answer (less guessing needed w.r.t. missing information) given a real example. --Jeroen -- Jeroen van Wolffelaar [EMAIL PROTECTED] (also for Jabber MSN; ICQ: 33944357) http://Jeroen.A-Eskwadraat.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: library for imap (client)
Hi Michelle! You wrote: Currently I am starting a new project and want to know, if someone know the existence if an imapclient library for C programing? I do not realy want to reinvent the wheel. I've used libetpan[1] in the past for some small projects. It's rather nice, as it has a single abstract interface to pop, imap, maildir, mbox, etc. I don't know how well it scales to large mail collections, though. [1] http://libetpan.sourceforge.net/ -- Kind regards, ++ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: one binary package created by different source packages, will the old source package disappear?
Jeroen van Wolffelaar [EMAIL PROTECTED] wrote: N.B.: Such questions are easier to answer (less guessing needed w.r.t. missing information) given a real example. I've noticed that. I thought it was a simple question regarding the infrastructure setup, but it turns out not to be... foo in reality is tetex-bin, and last autumn we created a stripped-down version of the tetex-bin_2.0.2 source package which only builds the old binary packages libkpathsea3 and libkpathsea-dev. foo2 is tetex-bin_3.0 with binary packages tetex-bin, libkpathsea4 and libkpathsea4-dev. On Mon, Mar 20, 2006 at 12:03:13PM +0100, Frank Küster wrote: Hi, assume the following scenario: - Source package foo creates binary packages libfoo1 and libfoo-dev - source package foo2 creates binary packages libfoo2 and libfoo2-dev Since both versions are API-compatible, libfoo2-dev is renamed to foo-dev, replacing the old binary package from source package foo. Will the complete source package foo have to disappear, or will foo and the binary package libfoo1 continue to be available? If foo2 didn't exist yet, you'd most likely want to start your transition by having a new 'foo' instead, creating libfoo2 and libfoo-dev. (ABI/SONAME change, but no API change, so -dev remains named the same). Back then, we decided against that solution, because we wanted the new upstream tetex (especially the tetex-bin package) to be able to migrate to testing without initiating an other library transition (which was forbidden back then). If foo2 already exists, I'd still go for that solution, but you'll then need to ask for foo2 removal via a bug to ftp.debian.org. That's not possible, I think, unfortunately - we don't want teTeX which currently provides libkpathsea4 in a source package named foo, err, libkpathsea3. We now have tetex-bin_3.0*, libkpathsea4_3.0* and libkpathsea4-dev_3.0 in testing and would like to get rid of libkpathsea3. In order to make that easier, it was suggested to rename libkpathsea4-dev to libkpathsea-dev and request binNMUs of the affected packages. However, I was concerned whether that would make the libkpathsea3 binary package disappear, and make all package uninstallable. Because there is API compatibility, I'm assuming here it makes not much sense to keep both libraries in at the same time. If you want to keep libfoo1 available (would need a somewhat decent reason, ideally), Just as long as there are still packages that link against it. you'll need separate source package names (indeed foo2 then), and will need to make a new upload of 'foo' stopping to provide a -dev package. Otherwise, ít'll be impossible to do security uploads without making those changes at that time -- however, libfoo1 will remain available, even lacking such upload. So I guess it would be acceptable to leave the old packages as they are, wait until all packages have been recompiled and migrated to testing, and then request removal of the libkpathsea3 binary package? Regards, Frank -- Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX)
shared libraries dependecy problem.
Hi. I have problem with dependecies on shared libraries in my package (tleenx2). Linda complains that: W: tleenx2; A binary links against a library that is not depended on. (By the way - shoudn't it be error rather than warning ?) I have checked binary with objdump and ldd and i got ... simillar but not the same results. ldd output shows four more entries than objdump. That is: [EMAIL PROTECTED]:~/devel/tlen/deb/problem$ diff objdump.output ldd.output 1d0 51a51,61 libc6: /lib/ld-linux.so.2 libpango1.0-0: /usr/lib/libpangoft2-1.0.so.0.1003.1 libpango1.0-0: /usr/lib/libpangoft2-1.0.so.0 libfreetype6: /usr/lib/libfreetype.so.6 libfreetype6: /usr/lib/libfreetype.so.6.3.8 zlib1g: /usr/lib/libz.so.1 zlib1g: /usr/lib/libz.so.1.2.3 libexpat1: /usr/lib/libexpat.so.1 libexpat1: /usr/lib/libexpat.so.1.0.0 libpng12-0: /usr/lib/libpng12.so.0.1.2.8 libpng12-0: /usr/lib/libpng12.so.0 [EMAIL PROTECTED]:~/devel/tlen/deb/problem$ objdump.output and ldd.ouput files are attached (created using simple script and dpkg -S). I don't know if I missed something and it is just my mistake, but it looks strange. This can probably affect linda check results or even generate invalid package dependecies (what is worse). But of course I can be wrong. Can, please, somebody explain what is goin on ?;) Best regards, Grzegorz Bizon -- [ ,''`. [EMAIL PROTECTED] // [EMAIL PROTECTED] ] [ : :' : GG: 830398 // JID: verdan(at)chrome.pl ] [ `. `' [EMAIL PROTECTED] //GPG: 0xDF32F531 ] [ `- 1A6F A0A1 01D1 3033 332A 60FE 4C7B 8037 DF32 F531 ] ldd.output Description: Binary data objdump.output Description: Binary data pgpGS3kqbvO33.pgp Description: PGP signature
Bug last active indicator?
I am wondering if it would be possible to modify the code for bugs.debian.org to show one additional bit of information. The last item of information shown for a bug summary on a b.d.o page is the age of the bug (that is, how long it has been since the bug was first opened). Would it be possible to show, after the age, how long it has been since the *last* activity? For example, if you go to http://bugs.debian.org/wnpp, you will see that one of the first bugs listed is: #138873: RFA: isdnbutton -- Start and Stop ISDN connections and display status Package: wnpp; Reported by: Roland Rosenfeld [EMAIL PROTECTED]; 4 years and 3 days old. Following the link for it shows that after the initial RFA was made, there was no other activity. What I am suggesting is that the summary then look like is this: #138873: RFA: isdnbutton -- Start and Stop ISDN connections and display status Package: wnpp; Reported by: Roland Rosenfeld [EMAIL PROTECTED]; Age: 4 years and 3 days old; Last active: 4 years and 3 days ago. On the other hand, another bug looks like this: #141693: RFA: gmod -- Module player for Ultrasound and SB AWE soundcards Package: wnpp; Reported by: Riku Voipio [EMAIL PROTECTED]; 3 years and 347 days old. However, the bug has had some activity a few months ago and would look like this: #141693: RFA: gmod -- Module player for Ultrasound and SB AWE soundcards Package: wnpp; Reported by: Riku Voipio [EMAIL PROTECTED]; Age: 3 years and 347 days old; Last active: 197 days ago. I think this would help provide additional information at a glance. Additionally, since the bugs are usually sorted by category and then by age, it might be worthwhile to add the option to sort by category and by last active date, or something like that. If the consensus is that this is generally a good idea, then I intend to file a bug against bugs.debian.org to request the feature. Though, looking at the list of bugs (and their ages) filed against bugs.debian.org I would welcome any suggestions on how I can help to get this implemented. -Roberto -- Roberto C. Sanchez http://familiasanchez.net/~roberto signature.asc Description: OpenPGP digital signature
Re: dicussion about patches ... ignoring patches make motivation to provide them fall
Russ Allbery wrote: Whenever this topic comes up on debian-devel, the conversation seems to focus on the small minority of maintainers who don't respond to bugs, are still active on their packages, resist any attempt at co-maintainership, and can't be dealt with through the MIA process. Yes, these are the most frustrating cases. Such people, to the extent that they exist, are frustrating; they're also such a small minority of the problem that if they were all we had to worry about, Debian would be in awesome shape. [...] If you run into a maintainer who doesn't want your help, move on and try another maintainer. It might not be so simple. Suppose I have taken it upon myself to push change Foo through Debian. The Foo project requires cooperation from several DDs and at the beginning I can't tell whether I will get that cooperation from all of them. After having devoted many hours to project Foo and after the passage of some months I find that progress is blocked by needed changes to package P. I write to the maintainer of P but get no reply. After repeating this a few times I (finally!) get a message from the P maintainer... about his having more important things to do than deal with my patch. Time goes by and the patch is never spoken of again. Of course I move on and do something else. But I have wasted a lot of time, Foo never gets done, and I have learned not to undertake any more projects like Foo in the future. Not within Debian, anyway. Purely hypothetical case, but it could happen. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: library for imap (client)
Am 2006-03-20 14:33:30, schrieb Bas Zoetekouw: Hi Michelle! I've used libetpan[1] in the past for some small projects. It's rather nice, as it has a single abstract interface to pop, imap, maildir, mbox, etc. I don't know how well it scales to large mail collections, though. [1] http://libetpan.sourceforge.net/ Great, I will check it out. Oops... ist in Debian allready... Greetings Michelle Konzack -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ # Debian GNU/Linux Consultant # Michelle Konzack Apt. 917 ICQ #328449886 50, rue de Soultz MSM LinuxMichi 0033/3/8845235667100 Strasbourg/France IRC #Debian (irc.icq.com) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: library for imap (client)
On Mon, 20 Mar 2006 14:33:30 +0100 Bas Zoetekouw [EMAIL PROTECTED] wrote: Hi Michelle! You wrote: Currently I am starting a new project and want to know, if someone know the existence if an imapclient library for C programing? I do not realy want to reinvent the wheel. I've used libetpan[1] in the past for some small projects. It's rather nice, as it has a single abstract interface to pop, imap, maildir, mbox, etc. I don't know how well it scales to large mail collections, though. [1] http://libetpan.sourceforge.net/ It's already used in at least 2 MUAs (packages: sylpheed-claws-gtk2 and etpan-ng). Using claws I've regularly handled IMAP inboxes of 20k mails without trouble. I don't know for larger values of large though. regards, -- Ricardo Mones. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dicussion about patches ... ignoring patches make motivation to provide them fall
On Monday 20 March 2006 16:04, Thomas Hood wrote: It might not be so simple. Suppose I have taken it upon myself to push change Foo through Debian. The Foo project requires cooperation from several DDs and at the beginning I can't tell whether I will get that cooperation from all of them. After having devoted many hours to project Foo and after the passage of some months I find that progress is blocked by needed changes to package P. I write to the maintainer of P but get no reply. After repeating this a few times I (finally!) get a message from the P maintainer... about his having more important things to do than deal with my patch. Alternative conclusion to this saga... I discuss on d-devel if the Foo project is a worthwhile goal and how I've gotten stuck. There is general agreement that Foo is worth pushing for the next release. I ask for a review of/help with my patches to the packages that block progress, deal with the comments that come back and NMU them (after mailing the maintainer one last time). Foo makes it into the next release. pgp1tkwhNPe0c.pgp Description: PGP signature
Bug#358003: ITP: ttf-dzongkha -- TrueType fonts for Dzongkha language
Package: wnpp Severity: wishlist Owner: Christian Perrier [EMAIL PROTECTED] * Package name: ttf-dzongkha Version : 0.1 Upstream Author : Chris Fynn [EMAIL PROTECTED] * URL : http://sourceforge.net/project/showfiles.php?group_id=115503 * License : GPL Description : TrueType fonts for Dzongkha language This package includes fonts that are suitable for the display of the Dzongkha language. PS: the listed upstream author is the author of the only font currently available to be included in the package. More fonts could come up later, the upstream package being managed by the Department of Informati�onTechnology, Timphu, Bhutan. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_FR.UTF-8)
Bug#358009: ITP: rcov -- a code coverage tool for Ruby
Package: wnpp Severity: wishlist Owner: Ari Pollak [EMAIL PROTECTED] * Package name: rcov Version : 0.2.0 Upstream Author : Mauricio Fernandez [EMAIL PROTECTED] * URL : http://eigenclass.org/hiki.rb?rcov * License : Dual GPL/Ruby license, includes a modified BSD-style licensed library Description : a code coverage tool for Ruby rcov is a code coverage tool for Ruby. It improves on the better known coverage tool, Ruby Coverage, in a number of points: * 20-300 times faster: typically, the program being inspected runs only ~3 times slower than without rcov (i.e. not 200 times slower as with previous tools) * more accurate coverage information through code linkage inference using simple heuristics * more convenient interface * additional features like bogo-profile mode, colorblind-friendliness... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#349693: ITP: gst-fluendo-mp3 -- MP3 decoder plugin for GStreamer
* Josselin Mouette: There is no difference between decoders and encoders. Both require patent licenses. But as I understand it, only the encoding patents are enforceable. I've never seen a compelling argument why this should be the case. The arguments looked more or less like wishful thinking to me. If we start to remove software from main just because some random companies claim they have patents covering it, we can stop to distribute Debian entirely. Sure, but these aren't random companies. Some of the patents aren't obviously invalid (except for the general software patents are illegal in Europe stance), so it's not exactly like the JPEG situation. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#349693: ITP: gst-fluendo-mp3 -- MP3 decoder plugin for GStreamer
* Russell Coker: This factor makes it significantly different from the other programs which are afflicted with patent claims. If Thomson has made clear statements about a common use case of software based on their patents in Debian then it's quite different to a battle between Adobe and Macromedia. Apparently, it is, because you can still download several free encoders. Furthermore, nobody's got a strategic MP3 encoder project, I guess. Things could go wild only if the entertainment industry realizes that better encoders are a prerequisite to efficient content distribution, and puts pressure on the patent owners to enforce their patents. 8-P (Adobe and Macromedia? Hmm, maybe I should answer my mail more quickly.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: First AMD64 Binary Uploaded
* Goswin von Brederlow: Anything that runs from current amd64.debian.net or its mirrors. Both debian-amd64 and debian-pure64? Great, thanks. They are just aliases for the same thing since always. Oh, this wasn't clear from the FAQ. Fortunately, all this is now OBE. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Question about cdrecord developement
Hi, I've been trying to retrieve from a cdrom as much vendor's info as possible. Thanks of cdrecord source code I can retrieve some of it. However, and although I've been looking where to ask (including any related mailing list within the debian project), haven't seen it. I just wanted to ask whether it would be possible to retrieve some sort of serial number for a cdrom that would be unique, either because it's got such info on it, or playing with some data, some static data. Any clues? Please cc me, as I'm not subscribed. Thanks a lot.
Re: DPL Debate prepared questions list [Debian Policy Sucks]
On Tuesday 21 March 2006 00:08, Adrian von Bidder wrote: On Saturday 18 March 2006 17:32, Roland Mas wrote: Thaddeus H. Black, 2006-03-18 16:00:11 +0100 : It appears that to have a Enterprise Grade Debian Distribution, we need a SPOC [ed.: Single Point of Contact?] team which can address Enterprise demands quickly. Yeah, and its members should have pointy ears and a puzzled raised eyebrow. Nah, a fancy letterhead, a certfied logo program and very high fees should suffice. You guys are good at making fun. But is that all ?? Forgive me if I've not done my homework but IMO Debian Policy sucks. I had installed Debian Sarge at one of my client's location. The machine serves as a NAT and does Web Content Filtering. The machine has Intel 1000MT NIC. Now, there was a known issue with those cards with e1000 driver upto kernel 2.6.11, IIRC. Sarge shipped with 2.6.8. Now the Debian policy says _only_ security updates are allowed to Debian Stable. Fixes like Feature Enhancement of Hardware Bug Fix aren't part of Debian Stable. So what do you people suggest in such cases: 1) Intel 1000MT NIC sucks, throw it away ? 2) Unh! Why don't you change to Debian Unstable ? 3) Buddy! We are all volunteers. Go and roll your own kernel with the patches ? 4) Wait! That hardware isn't officially supported by us. Build only machines which are known to work with Debian Stable? I ended up going with point number 2. But really, next time I might think of another distribution before deployment. Thanks, Ritesh -- Ritesh Raj Sarraf RESEARCHUT -- http://www.researchut.com Necessity is the mother of invention. Stealing logic from one person is plagiarism, stealing from many is research. pgpxvx92MDTJI.pgp Description: PGP signature
Re: Bug#358003: ITP: ttf-dzongkha -- TrueType fonts for Dzongkha language
Package: wnpp Severity: wishlist Owner: Christian Perrier [EMAIL PROTECTED] This package includes fonts that are suitable for the display of the Dzongkha language. May I suggest for rare languages like this that you also mention in the description where the language comes from? (Bhutan in this case, isn't it?) Thanks, Drew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: shared libraries dependecy problem.
On Mon, Mar 20, 2006 at 03:59:04PM +0100, Grzegorz Bizon wrote: I have problem with dependecies on shared libraries in my package (tleenx2). Linda complains that: W: tleenx2; A binary links against a library that is not depended on. (By the way - shoudn't it be error rather than warning ?) I have checked binary with objdump and ldd and i got ... simillar but not the same results. ldd output shows four more entries than objdump. It's normal for ldd to show more than objdump: ldd is recursive, listing all the objects that are actually loaded, and objdump is not recursive. I don't know which one linda uses in its checks, though I would hope it's objdump. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Re: DPL Debate prepared questions list [Debian Policy Sucks]
Ritesh Raj Sarraf wrote: So what do you people suggest in such cases: 1) Intel 1000MT NIC sucks, throw it away ? 2) Unh! Why don't you change to Debian Unstable ? 3) Buddy! We are all volunteers. Go and roll your own kernel with the patches ? 4) Wait! That hardware isn't officially supported by us. Build only machines which are known to work with Debian Stable? 5) etch beta 2 was released last week with support for your hardware -- see shy jo signature.asc Description: Digital signature
Re: question on hurd-i386 Debian architecture
Em Sáb, 2006-03-18 às 23:17 +0100, Pjotr Kourzanov escreveu: Yes. However, I think that 'setting up buildd' is the least difficult of those tasks. It is by far more difficult to produce patches for all 'standard debian packages' that make them first of all, cross-compile correctly, and (only) then make them uClibc-friendly. Sorry, I don't get it. Debian has support for several architectures, why a sub-arch would be harder? Many packages will just work. Remember that in such sub-arch, we can have uclibc-dev replacing libc6-dev, solving the builddeps... Have you ever seen uwoody[1]? there are not so many patches as you're claiming to be necessary... I'm really lost about what are you talking about... [1] http://people.debian.org/~andersee/uwoody/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dicussion about patches ... ignoring patches make motivation toprovide them fall
Petter Reinholdtsen wrote: So yes, I believe we need to work on the long-term ignored bugs. :) Those are essentially all I work on. It's a good thing I have a thick skin. Some maintainers are genuinely grateful for the assistance, and they're a pleasure to work with. (This includes the X Strike Force, although they are really a bit snowed under and so you have to push a bit to get a bug addressed.) Some maintainers are basically MIA, but won't give up their packages, and they're more annoying, but they usually accede to reality eventually, and are OK to work with. Some few maintainers are obnoxious and anti-helpful. All of these have bugs which have had a patch attached to them for a long time without mantainer comment (not even 'no, this patch doesn't work because X'). However, not all such bugs reflect anti-helpful maintainers; many reflect MIA, busy, or distracted maintainers, so one has to poke them to find out whether one gets a rude reply, no reply, or a thank you reply. Sorry about the thread-breaking again. Can't help it on this machine; will try not to post from here again. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
automatically install -dev packages
Is there a setting somewhere I can set to cause apt-get and aptitude to always install corresponding -dev packages? The default behavior of not installing them is particularly annoying when dealing with libraries that are installed when the OS itself is installed. -- David Griffith [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cross-compiling Debian packages
I hope that my patches (#357629, mailto:[EMAIL PROTECTED] #357658 mailto:[EMAIL PROTECTED], #357661 mailto:[EMAIL PROTECTED]) are proper enough:-) This is incomplete: not only libgcc does not provide -dcv1, but libstdc++ and -dev and -dbg. Would you be so kind to post undeted patches to these bugs? pgpil8U2ddq9a.pgp Description: PGP signature
e1000 support in Debian [Was: Re: DPL Debate prepared questions list [Debian Policy Sucks]]
On Mon, Mar 20, 2006 at 03:39:45PM -0500, Joey Hess wrote: Ritesh Raj Sarraf wrote: So what do you people suggest in such cases: 1) Intel 1000MT NIC sucks, throw it away ? 2) Unh! Why don't you change to Debian Unstable ? 3) Buddy! We are all volunteers. Go and roll your own kernel with the patches ? 4) Wait! That hardware isn't officially supported by us. Build only machines which are known to work with Debian Stable? 5) etch beta 2 was released last week with support for your hardware If this is the issue I think it is, sarge does support the hardware but the kernel isn't configured to support large frames on it in GigE mode. I'm not aware that this issue has been resolved yet in the kernels for etch either; the issue had earlier been clouded by concerns over the reliability of this kernel configure option, owing to confusion with a similarly named option for a different card. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Re: DPL Debate prepared questions list [Debian Policy Sucks]
On Tuesday 21 March 2006 02:09, Joey Hess wrote: Ritesh Raj Sarraf wrote: So what do you people suggest in such cases: 1) Intel 1000MT NIC sucks, throw it away ? 2) Unh! Why don't you change to Debian Unstable ? 3) Buddy! We are all volunteers. Go and roll your own kernel with the patches ? 4) Wait! That hardware isn't officially supported by us. Build only machines which are known to work with Debian Stable? 5) etch beta 2 was released last week with support for your hardware So my question is: I discovered it today. But there might have been many Debian Users who might have discovered this issue earlier. What choice are they given ? Is the choice: Wait till etch gets released ? RHEL and SLES do a damn good job of Hardware Bug Fixing and Feature Enhancement for the software they ship. Why can't we do it ? Is it just because our policy doesn't allow it ? Can't we revise the policy ? Thanks, Ritesh -- Ritesh Raj Sarraf RESEARCHUT -- http://www.researchut.com Necessity is the mother of invention. Stealing logic from one person is plagiarism, stealing from many is research. pgpi1LEuZDQ7c.pgp Description: PGP signature
Re: DPL Debate prepared questions list [Debian Policy Sucks]
On Mar 20, Ritesh Raj Sarraf [EMAIL PROTECTED] wrote: So what do you people suggest in such cases: If you need a distribution which supports modern hardware, then you should switch to Ubuntu. -- ciao, Marco signature.asc Description: Digital signature
Re: shared libraries dependecy problem.
Grzegorz Bizon wrote: Hi. I have problem with dependecies on shared libraries in my package (tleenx2). Linda complains that: W: tleenx2; A binary links against a library that is not depended on. (By the way - shoudn't it be error rather than warning ?) Linda seems to be doing this with all packages with ELF binaries for me. Random sample from /var/cache/apt/archives: W: bash; A binary links against a library that is not depended on. W: bsdutils; A binary links against a library that is not depended on. W: cdparanoia; A binary links against a library that is not depended on. W: coreutils; A binary links against a library that is not depended on. W: cron; A binary links against a library that is not depended on. W: curl; A binary links against a library that is not depended on. signature.asc Description: OpenPGP digital signature
Re: DPL Debate prepared questions list [Debian Policy Sucks]
On Tue, 21 Mar 2006, Ritesh Raj Sarraf wrote: On Tuesday 21 March 2006 02:09, Joey Hess wrote: 5) etch beta 2 was released last week with support for your hardware But there might have been many Debian Users who might have discovered this issue earlier. What choice are they given ? They could have used an Etch nightly, or any number of other methods to get a kernel that supports their hardware running... it's not all that difficult to do.[1] [And if it's a problem, there are consultants available to do it for you.] Why can't we do it? Want to release faster? There are RC bugs that need patches, and transitions that need planning. Want to make sure that the next release supports your hardware? Help test your hardware with the newest d-i nightlies and assist the d-i team. Don Armstrong 1: I suppose it may be considered cheating for any of us to declare that something is easy to do when we can just do an install using debootstrap... -- It's not Hollywood. War is real, war is primarily not about defeat or victory, it is about death. I've seen thousands and thousands of dead bodies. Do you think I want to have an academic debate on this subject? -- Robert Fisk http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: question on hurd-i386 Debian architecture
On Mon, Mar 20, 2006 at 05:41:26PM -0300, Daniel Ruoso wrote: Em S?b, 2006-03-18 ?s 23:17 +0100, Pjotr Kourzanov escreveu: Yes. However, I think that 'setting up buildd' is the least difficult of those tasks. It is by far more difficult to produce patches for all 'standard debian packages' that make them first of all, cross-compile correctly, and (only) then make them uClibc-friendly. Sorry, I don't get it. Debian has support for several architectures, why Supported architectures, yes. But what about un-supported ones, such as i386-uclibc? a sub-arch would be harder? Many packages will just work. Remember that in such sub-arch, we can have uclibc-dev replacing libc6-dev, solving the builddeps... Yeah, hopefully this will just work. From my experience, however, some minimal but still significant amount of patching will be needed. Have you ever seen uwoody[1]? there are not so many patches as you're claiming to be necessary... I'm really lost about what are you talking about... [1] http://people.debian.org/~andersee/uwoody/ I've heard that uwoody is abandoned by its originator... which is the reason I stopped looking at that. Is there BTW any comparable effort for sarge/etch? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Release Date Update
Guys, you know putting the first freeze date before the end of the summer is foolish. Many people do their best coding during the summer. Debian should make sure The freeze begins after a whole summer of good coding and adding new features, like at the end of August or the begginnig of September. Then the summer could be devoted to the coding of new and exciting features while it is most convienient. Then you can spend the rest of the year and the begging of next year debugging. Then you have a few months off before the summer major code fest. This would give Debian a good one year release cycle wher you maximize your time over the summer to add new features. -- Mark -- ubuntu-announce mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-announce _ FREE pop-up blocking with the new MSN Toolbar get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Release Date Update
On Mon, Mar 20, 2006 at 02:51:25PM -0800, Mark Shuttleworh wrote: [...] Before anybody gets to reply to the body, this is a fake. Mark Shuttleworth doesn't use a hotmail adress to send mail to lists. YHBT, HAND, Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DPL Debate prepared questions list [Debian Policy Sucks]
* Ritesh Raj Sarraf [EMAIL PROTECTED] [060320 22:14]: RHEL and SLES do a damn good job of Hardware Bug Fixing and Feature Enhancement for the software they ship. Why can't we do it ? Is it just because our policy doesn't allow it ? Can't we revise the policy ? Of course policies can be revisited. Stable could also be abolished and only unstable be shipped, if that gets decided. Fixes to stable releases are always tricky as they are supposed to be stable. Important bugs fixes are always a good goal, but they always have to be balanced against possible unintended damages any change can have. I haven't looked at this case, but in the general case possibly suddenly no longer supporting something that was supported before in that stable release is much worse than not adding support for new cases, as things that worked are likely to be in production new, things that did not work are annoying and sad, but only annoying and not hurting people relying on a something advertised as stable keeping stable. Hochachtungsvoll, Bernhard R. Link -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Release Date Update
On Mon, Mar 20, 2006 at 02:51:25PM -0800, Mark Shuttleworh wrote: (In case it wasn't clear, this wasn't Mark Shuttlewor*t*h posting. Please don't feed the troll.) -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DPL Debate prepared questions list [Debian Policy Sucks]
On Tue, 21 Mar 2006 02:43:38 +0530, Ritesh wrote in message [EMAIL PROTECTED]: On Tuesday 21 March 2006 02:09, Joey Hess wrote: Ritesh Raj Sarraf wrote: So what do you people suggest in such cases: 1) Intel 1000MT NIC sucks, throw it away ? 2) Unh! Why don't you change to Debian Unstable ? 3) Buddy! We are all volunteers. Go and roll your own kernel with the patches ? 4) Wait! That hardware isn't officially supported by us. Build only machines which are known to work with Debian Stable? 5) etch beta 2 was released last week with support for your hardware So my question is: I discovered it today. But there might have been many Debian Users who might have discovered this issue earlier. What choice are they given ? Is the choice: Wait till etch gets released ? RHEL and SLES do a damn good job of Hardware Bug Fixing and Feature Enhancement for the software they ship. Why can't we do it ? Is it just because our policy doesn't allow it ? Can't we revise the policy ? ..we can't? I (not yet a DD) thought this was a simple case of 6) Somebody Volonteer Patches! ;o) -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Release Date Update
someone claiming to be Mark Shuttleworh wrote: Guys, you know putting the first freeze date before the end of the summer is foolish. Many people do their best coding during the summer. Nice troll, but you need to work on your headers. -- see shy jo signature.asc Description: Digital signature
I like the new Release
It make be fake but is it a bad idea? A release every year and afterr a good summer of work? Does anybody have a better idea? _ On the road to retirement? Check out MSN Life Events for advice on how to get there! http://lifeevents.msn.com/category.aspx?cid=Retirement -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Release Date Update
On Mon, 2006-03-20 at 23:15 +, Colin Watson wrote: On Mon, Mar 20, 2006 at 02:51:25PM -0800, Mark Shuttleworh wrote: (In case it wasn't clear, this wasn't Mark Shuttlewor*t*h posting. Please don't feed the troll.) Even so, are his points valid? -- - Ron Johnson, Jr. Jefferson, LA USA Passivity is one of the tools of authoritarianism. Pope John Paul 2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Release Date Update
On Mon, Mar 20, 2006 at 05:39:23PM -0600, Ron Johnson wrote:
On Mon, 2006-03-20 at 23:15 +, Colin Watson wrote:
On Mon, Mar 20, 2006 at 02:51:25PM -0800, Mark Shuttleworh wrote:
(In case it wasn't clear, this wasn't Mark Shuttlewor*t*h posting.
Please don't feed the troll.)
Even so, are his points valid?
Questionable... For starters, there is no global Summer, so what
hemisphere would Debian choose to favor? Seems a little silly to me.
--
{ IRL(Jeremy_Stanley); PGP(9E8DFF2E4F5995F8FEADDC5829ABF7441FB84657);
SMTP([EMAIL PROTECTED]); IRC([EMAIL PROTECTED]); ICQ(114362511);
AIM(dreadazathoth); YAHOO(crawlingchaoslabs); FINGER([EMAIL PROTECTED]);
MUD([EMAIL PROTECTED]:6669); WWW(http://fungi.yuggoth.org/); }
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: automatically install -dev packages
On 20-Mar-06, 14:37 (CST), David Griffith [EMAIL PROTECTED] wrote: Is there a setting somewhere I can set to cause apt-get and aptitude to always install corresponding -dev packages? The default behavior of not installing them is particularly annoying when dealing with libraries that are installed when the OS itself is installed. Nope, there's no such option. If you're (re-)building Debian packages, there's an option to apt-get source that also grabs the build dependencies. For some of the bigger suites (Gnome, KDE, etc.) look for a high-level blah-devel package that brings in pretty much everything you need to do development for that suite. Or at least there used to be such packages... Otherwise, your best bet may be to fire up aptitude and step through the libdevel section, picking out the ones you want. Note that you don't have to pick all of them, just the ones you explicitly want, and let the dependency system pull in anything they need. Steve -- Steve Greenland The irony is that Bill Gates claims to be making a stable operating system and Linus Torvalds claims to be trying to take over the world. -- seen on the net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: I like the new Release
Greg Conner [EMAIL PROTECTED] writes: It make be fake but is it a bad idea? A release every year and afterr a good summer of work? Does anybody have a better idea? FWIW: According to the headers, this mail is sent from the same machine as the original fake. -- ilmari -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: e1000 support in Debian [Was: Re: DPL Debate prepared questions list [Debian Policy Sucks]]
On 3/20/06, Steve Langasek [EMAIL PROTECTED] wrote: On Mon, Mar 20, 2006 at 03:39:45PM -0500, Joey Hess wrote: Ritesh Raj Sarraf wrote: So what do you people suggest in such cases: 1) Intel 1000MT NIC sucks, throw it away ? 2) Unh! Why don't you change to Debian Unstable ? 3) Buddy! We are all volunteers. Go and roll your own kernel with the patches ? 4) Wait! That hardware isn't officially supported by us. Build only machines which are known to work with Debian Stable? 5) etch beta 2 was released last week with support for your hardware If this is the issue I think it is, sarge does support the hardware but the kernel isn't configured to support large frames on it in GigE mode. I'm not aware that this issue has been resolved yet in the kernels for etch either; the issue had earlier been clouded by concerns over the reliability of this kernel configure option, owing to confusion with a similarly named option for a different card. Would that really be *the* issue for a NAT box?
Re: I like the new Release
Dagfinn Ilmari Mannsåker wrote: Greg Conner [EMAIL PROTECTED] writes: It make be fake but is it a bad idea? A release every year and afterr a good summer of work? Does anybody have a better idea? FWIW: According to the headers, this mail is sent from the same machine as the original fake. $ host 128.187.0.165 165.0.187.128.in-addr.arpa domain name pointer tmcb-u110-3N1E-CE2.byu.edu. It must be SCO. They have cleverly disguised themselves as BYU students. :-) -Roberto -- Roberto C. Sanchez http://familiasanchez.net/~roberto signature.asc Description: OpenPGP digital signature
Re: DPL Debate prepared questions list [Debian Policy Sucks]
On 20 Mar 2006, Ritesh Raj Sarraf said this: So what do you people suggest in such cases: 1) Intel 1000MT NIC sucks, throw it away ? 2) Unh! Why don't you change to Debian Unstable ? 3) Buddy! We are all volunteers. Go and roll your own kernel with the patches ? 4) Wait! That hardware isn't officially supported by us. Build only machines which are known to work with Debian Stable? 5) Set up a site for backports where people can go to. You know, you don't have to be a DD to do that. I ended up going with point number 2. But really, next time I might think of another distribution before deployment. That is always a wise move -- you should always see what fits you best. No distribution is for everyone. manoj -- It shall be unlawful for any suspicious person to be within the municipality. Local ordinance, Euclid Ohio Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/%7Esrivasta/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: e1000 support in Debian [Was: Re: DPL Debate prepared questions list [Debian Policy Sucks]]
On Tue, Mar 21, 2006 at 01:01:28AM +0100, Olaf van der Spek wrote: On 3/20/06, Steve Langasek [EMAIL PROTECTED] wrote: On Mon, Mar 20, 2006 at 03:39:45PM -0500, Joey Hess wrote: Ritesh Raj Sarraf wrote: So what do you people suggest in such cases: 1) Intel 1000MT NIC sucks, throw it away ? 2) Unh! Why don't you change to Debian Unstable ? 3) Buddy! We are all volunteers. Go and roll your own kernel with the patches ? 4) Wait! That hardware isn't officially supported by us. Build only machines which are known to work with Debian Stable? 5) etch beta 2 was released last week with support for your hardware If this is the issue I think it is, sarge does support the hardware but the kernel isn't configured to support large frames on it in GigE mode. I'm not aware that this issue has been resolved yet in the kernels for etch either; the issue had earlier been clouded by concerns over the reliability of this kernel configure option, owing to confusion with a similarly named option for a different card. Would that really be *the* issue for a NAT box? No, probably not. I guess this is about some unrelated issue specific to a particular e1000 model. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Re: DPL Debate prepared questions list [Debian Policy Sucks]
Ritesh Raj Sarraf wrote: Now, there was a known issue with those cards with e1000 driver upto kernel 2.6.11, IIRC. Hmmm, and 2.6.12 panics (bug #327355 mailto:[EMAIL PROTECTED]) when I try and use the tape drive on my machine. New versions not only fix bugs, but introduce new ones, too. [PS: Which e1000 bug are you referring to?] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DPL Debate prepared questions list [Debian Policy Sucks]
* Anthony DeRobertis [EMAIL PROTECTED] [2006-03-20 20:04]: Hmmm, and 2.6.12 panics (bug #327355 mailto:[EMAIL PROTECTED]) when I try and use the tape drive on my machine. New versions not only Anthony, do you still see this bug with 2.6.15 or (better yet) 2.6.16? (will be uploaded tomorrow). -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
So we got caught, so what? But we did the right thing.
It must be SCO. They have cleverly disguised themselves as BYU students. :-) -Roberto So we got caught trying to br BYU students. You guys win that battle. But you have to admit at least we care enough about Debian that we are willing to make suggestions. We don't want to offend anyone in particular, but you guys have a talent for computers, but your leadership is failing in the bright ideas department. Besides programming issues, what great ideas has any leadership put forth to keep bring Debian to levels and hieghts not even imagined by anyone. The real reason Ubuntu does so well is they have not only programming skills but a leader with incredible vision and new ideas, something DPLs and others seem to not. As evidence where are the constant DPL's great ideas for the future of Debian? All the voting issues and debated issues are over things like GFDL position or throwing people out of Debian. Nobdoy ever posts anything concerning a vision for the future. NOBODY! except non DDs. YOu all just don't seem to care. WITH THE PROGRAMMING SKILLS YOU ALL HAVE, IF YOU WOULD TRY TO PUT THE BIGGEST VISIONARY AS DPL, HE/SHE WILL TAKE YOU TO LEVELS NOT EXPERIENCED. ALL ~970 OF YOU. I know you will ignore this or say don't feed the troll, but the man/woman developer with enough guts to say to the rest of the DDs, Debain could do so much better, here's some ideas is the DD we will have so much respect for. PS.. For further evidence on how poor your leadership is, I refer you to how much caos there is on your mailing lists. You can't keep your release managers: http://lists.debian.org/debian-devel-announce/2006/03/msg8.html You have no control over your ftpmasters who act like they run the world. You do nothing but put each other down. I refere top all the posts about svenl. You all don't know how to work together at all. You have the biggest reputation of all distros as being jerks to others. Then pawn off your cowardice by saying we're all just volunteers You lose half your Developer wannabies, NMs, because your mentor program is lousy and you are more worried about making people suffer through the buracracy allowing people who honestly want to help Debian to do so. See http://lists.debian.org/debian-newmaint/2005/12/msg4.html You say it takes you guys a long time to release packages because you want them bug free. HA!!! Things like gnome 2.12 come out and it isn't in Unstable for like 3 months. It would take less time to get packages ready for stable if you would put them in Unstable. You talk about how much care you put into finding good developers, but you can't even get them to work for you: http://lists.debian.org/debian-devel-announce/2006/01/msg4.html YOu have to threaten them to work, and yet the bugs are still there. etc... we could keep going but there is not enough time in the day. In short, get a new Leadership,(WE are aware of new DPL Elections), but who are you going to elect? And there are more to your leadership problems than the DPL. Our advice to you all is get some control of yourselves, and some leadership with good ideas and clear goals that are revolutionary. Or start working for Ubuntu, at least they have leadership with the right quality. _ Is your PC infected? Get a FREE online computer virus scan from McAfee® Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DPL Debate prepared questions list [Debian Policy Sucks]
UBUNTU realy works, and is stable. I've instaled it on a few servers now, and i'm quite happy with it.but my question is. Why don't you just build your own kernel from source. download the vannilla souces and do it. it's not that hard on debian. it's easier on gentoo, but in debian it's almost equaly easy why don't you try .:)Since debian is build thru volunteer, why don't you contribute whith something... build your kernel, build it with lot's of options and post the .deb on a website. help yourself an help debian at the same timeRUI SILVAOn 3/20/06, Marco d'Itri [EMAIL PROTECTED] wrote:On Mar 20, Ritesh Raj Sarraf [EMAIL PROTECTED] wrote: So what do you people suggest in such cases:If you need a distribution which supports modern hardware, then youshould switch to Ubuntu. --ciao,Marco-BEGIN PGP SIGNATURE-Version: GnuPG v1.4.2.2 (GNU/Linux)iD8DBQFEHyW1FGfw2OHuP7ERAvvEAJ0aDMtkykFLxxp1UO8QLjMtzS0keQCfanpLrelsQMj37tIRTHXqqXnPQfk==zRQu -END PGP SIGNATURE--- Rui SilvaPowered by Gentoo Linux under :CELERON 1000 - Stage1 install with nptlPentium M 1800GHz - Stage1 install with NPTL http://rukinhas.no-ip.org
Re: DPL Debate prepared questions list [Debian Policy Sucks]
* Rui Silva [EMAIL PROTECTED] [2006-03-21 01:02]: Since debian is build thru volunteer, why don't you contribute whith something... FWIW, kmuto-san has prepated sarge d-i images with a modern kernel: http://kmuto.jp/b.cgi/debian/d-i-2615.htm And backports.org has modern kernels for sarge. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DPL Debate prepared questions list [Debian Policy Sucks]
Martin Michlmayr wrote: Anthony, do you still see this bug with 2.6.15 or (better yet) 2.6.16? (will be uploaded tomorrow). 2.6.15, yes. I'll check 2.6.16 when it hits unstable (I'm guessing, though I still need to test, that the ide-tape cleanup in 2.6.9 borked it) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Release Date Update
On Mon, 2006-03-20 at 23:45 +, Jeremy Stanley wrote: On Mon, Mar 20, 2006 at 05:39:23PM -0600, Ron Johnson wrote: On Mon, 2006-03-20 at 23:15 +, Colin Watson wrote: On Mon, Mar 20, 2006 at 02:51:25PM -0800, Mark Shuttleworh wrote: (In case it wasn't clear, this wasn't Mark Shuttlewor*t*h posting. Please don't feed the troll.) Even so, are his points valid? Questionable... For starters, there is no global Summer, so what hemisphere would Debian choose to favor? Seems a little silly to me. Well, true. I confess to northernhemisphereoentrism. Still, even though Brazil, ANZ South Africa are down under, the vast bulk of the world population lives in the Northern Hemisphere. -- - Ron Johnson, Jr. Jefferson, LA USA Basically, I got on the plane with a bomb. Basically, I tried to ignite it. Basically, yeah, I intended to damage the plane. RICHARD REID, tried to blow up American Airlines Flight 63 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: one binary package created by different source packages, will the old source package disappear?
On Mon, Mar 20, 2006 at 03:33:22PM +0100, Frank Küster wrote: If foo2 already exists, I'd still go for that solution, but you'll then need to ask for foo2 removal via a bug to ftp.debian.org. That's not possible, I think, unfortunately - we don't want teTeX which currently provides libkpathsea4 in a source package named foo, err, libkpathsea3. We now have tetex-bin_3.0*, libkpathsea4_3.0* and libkpathsea4-dev_3.0 in testing and would like to get rid of libkpathsea3. In order to make that easier, it was suggested to rename libkpathsea4-dev to libkpathsea-dev and request binNMUs of the affected packages. However, I was concerned whether that would make the libkpathsea3 binary package disappear, and make all package uninstallable. It will not make libkpathsea3 disappear or make it uninstallable. It will make the libkpathsea3 source package RC buggy, since it will not be possible to do further uploads of the package (for, e.g, security fixes) without either a) overwriting the new libkpathsea-dev that you want to keep, or b) resulting in a rejected upload due to the out-of-date version of libkpathsea-dev. Since (AIUI) you want to drop libkpathsea3 completely for etch, though, that doesn't seem like a problem. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Re: Release Date Update
On 20 Mar 2006, Ron Johnson said: Well, true. I confess to northernhemisphereoentrism. Still, even though Brazil, ANZ South Africa are down under, the vast bulk of the world population lives in the Northern Hemisphere. The premise is also weak. Man, in the summer, I want to be out. Day trips. Picnics. Sports. County fairs. Winter is when one hunkers down in the warmth of the house and codes. With a global project, made of diverse contributors, any statement like witer is better! No, Summer is better! is sily, naive, shallow, and probably incorrect. manoj -- PEGGY FLEMMING is stealing BASKET BALLS to feed the babies in VERMONT. Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/%7Esrivasta/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: I like the new Release
On 20 Mar 2006, Greg Conner outgrape: It make be fake but is it a bad idea? A release every year and afterr a good summer of work? Does anybody have a better idea? Go for it. Good luck on that. Let us know how it goes. manoj -- VMS must die! Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/%7Esrivasta/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: I like the new Release
Lol...if you're going to impersonate someone...sign up for a free php host and use Hee-Haw PHP mailer...it spoofs the email address and IP...;-) XDOn 3/20/06, Manoj Srivastava [EMAIL PROTECTED] wrote: On 20 Mar 2006, Greg Conner outgrape: It make be fake but is it a bad idea?A release every year and afterr a good summer of work?Does anybody have a better idea?Go for it. Good luck on that. Let us know how it goes. manoj--VMS must die!Manoj Srivastava [EMAIL PROTECTED]http://www.debian.org/%7Esrivasta/ 1024D/BF24424C print 4966 F272 D093 B493 410B924B 21BA DABB BF24 424C--To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: So we got caught, so what? But we did the right thing.
On 20 Mar 2006, Greg Conner told this: It must be SCO. They have cleverly disguised themselves as BYU students. :-) -Roberto So we got caught trying to br BYU students. You guys win that battle. Not much of a battle. Y'all were pretty pathetic at forgery. But thanks for the laughs. manoj -- GIVE UP Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/%7Esrivasta/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#358080: ITP: pygaim -- python plugin support for gaim
Package: wnpp Severity: wishlist Owner: Michael Spang [EMAIL PROTECTED] * Package name: pygaim Version : 1.5.0 * URL : http://pygaim.sf.net * License : GPL Description : python bindings and plugin loader for gaim PyGaim allows the Gaim Instance Messaging client to be extended with the Python programming language. Python bindings for all of the functions in Gaim's plugin API are provided. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DPL Debate prepared questions list [Debian Policy Sucks]
(dropping -curiosathe raised issue is a real issue) which are known to work with Debian Stable? 5) etch beta 2 was released last week with support for your hardware I'm not sure that many people are seriously considering an etch beta to install as a client's firewall solution. The guarantee bringed by the work on stable is still recognized as one of Debian's most strong arguments. So are the (sometimes overestimated?) good work on security updates for stablethis is easy to sell to clients. Despite the excellent work on testing security (hint hint), I'm not sure that recommending testing would be something I would do if I were a Debian consultant. PS: I hope that everyone has noticed the nice formulation of Joey. He said etch beta 2 and not etch installer beta 2 and I know he did this on purpose..:-) signature.asc Description: Digital signature
Re: shared libraries dependecy problem.
[Grzegorz Bizon] Linda complains that: W: tleenx2; A binary links against a library that is not depended on. (By the way - shoudn't it be error rather than warning ?) No, because it's sometimes hard to fix and often harmless. We don't like it but error is too strong. I have checked binary with objdump and ldd and i got ... simillar but not the same results. As others have already explained, ldd resolves recursive dependencies, so it will usually give more output than 'objdump -p $f | grep NEEDED'. The point is that you probably don't need to link to, e.g., -lX11, unless you directly use functions like XOpenDisplay or XBeep. Typically if you are using GTK, you won't be using any of those low-level functions. signature.asc Description: Digital signature
Re: Bug#358003: ITP: ttf-dzongkha -- TrueType fonts for Dzongkha language
Quoting Drew Parsons ([EMAIL PROTECTED]): Package: wnpp Severity: wishlist Owner: Christian Perrier [EMAIL PROTECTED] This package includes fonts that are suitable for the display of the Dzongkha language. May I suggest for rare languages like this that you also mention in the description where the language comes from? (Bhutan in this case, isn't it?) Well, I have one very little argument against doing so: why do it for Dzongkha and why not do it for, say, French...:-) I guess you may see the point: I don't want at all that Debian may seem too condescendant towards Bhutan and/or Dzongkha native speakers by feeling it's needed to explain what their language is while we don't feel that need for other languages. One may feel that's political overcorrectness, but experience shows that respecting peoples feelings about their culture or language is one of the key points for success in i18n. On the other hand, it is pretty much obvious that most of the Debian contributors and users don't actually know where Dzongkha is spoken (yes, this is the national language of Bhutan). signature.asc Description: Digital signature
Re: Bruce Perens hosts party at OSCON Wednesday night
On Sat, Aug 06, 2005 at 07:38:47PM +0100, Andrew Suffield wrote: On Thu, Aug 04, 2005 at 01:58:15PM -0300, Humberto Massa Guimar?es wrote: And to boot, an e-mail calling for curriculae for a recruiting party is on-topic to a DEVELOPERS list No. This is why the debian-jobs list exists. Andrew is right - there was perhaps a more appropriate list. Sadly - yet again, the real problem was the approach Adam took. Instead of a gentle friendly prod towards using the right list, Adam replied with a public antagonistic slapping. I suspect Bruce will probably not bother offering invitations to DD's in the future... Sad really. Why are we so quick to point fingers and wind each other (and outsiders) up. Will a new DPL be able to break through this barrier of arrogant selfish one-up-manship? Will all Debian devs ever be able to encourage and build each other up instead of bickering over their preferred method and style of protocol? I'm not hopeful - human nature is overwhelmingly self-centered and self-absorbed. I'd love to be surprised. -- Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted octave-epstk 2.1-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 20 Mar 2006 08:33:24 +0100 Source: octave-epstk Binary: octave-epstk Architecture: source all Version: 2.1-2 Distribution: unstable Urgency: low Maintainer: Debian Octave Group [EMAIL PROTECTED] Changed-By: Rafael Laboissiere [EMAIL PROTECTED] Description: octave-epstk - GNU Octave encapsulated postscript toolkit Closes: 347665 Changes: octave-epstk (2.1-2) unstable; urgency=low . [ Thomas Weber ] * Update FSF postal address in copyright file * Bumped standards version to 3.6.2. No changes needed. * Bumped debhelper compat version to 5. * Switch to CDBS. * Add 50_fix_legend_scaling.dpatch (Closes: #347665) . [ Rafael Laboissiere ] * debian/rules: - Use CDBS' simple-patchsys instead of dpatch - Added call to octave-depends in post-install action - Clean patched files m/*-center.psd * debian/patches/*.patch: Renamed from *.dpatch * debian/patches/README: Description of the patches. This information used to be in the headers of the old dpatches. Files: 57b1c013217a7cdbfda913249a2892c4 694 math optional octave-epstk_2.1-2.dsc 3028fcaf5e9c7e30bfadbbc023953d35 6016 math optional octave-epstk_2.1-2.diff.gz b9fdfb8c81673e602f55dd007e26ff32 2066814 math optional octave-epstk_2.1-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFEHl6Zk3oga0pdcv4RAo8eAJ9zwEwzQd4Ibca+ufaJDLKqFKZQxgCgicjy 1vjc3aUr871voJd2pO4RD0c= =ZZCd -END PGP SIGNATURE- Accepted: octave-epstk_2.1-2.diff.gz to pool/main/o/octave-epstk/octave-epstk_2.1-2.diff.gz octave-epstk_2.1-2.dsc to pool/main/o/octave-epstk/octave-epstk_2.1-2.dsc octave-epstk_2.1-2_all.deb to pool/main/o/octave-epstk/octave-epstk_2.1-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted python-f2py 2.45.241+1926-3 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 20 Mar 2006 11:13:09 +0100 Source: python-f2py Binary: python-f2py python2.4-f2py python-f2py-doc python2.3-f2py Architecture: source all Version: 2.45.241+1926-3 Distribution: unstable Urgency: low Maintainer: José Fonseca [EMAIL PROTECTED] Changed-By: Alexandre Fayolle [EMAIL PROTECTED] Description: python-f2py - Fortran to Python interface generator python-f2py-doc - Fortran to Python interface generator python2.3-f2py - Fortran to Python interface generator python2.4-f2py - Fortran to Python interface generator Closes: 357782 Changes: python-f2py (2.45.241+1926-3) unstable; urgency=low . * Updated standards version to 3.6.2 * Use debhelper 5.0 or later * Added debian/watch for DEHS * Added versioned build dependency on docutils and use rst2html instead of rest2html in debian/rules (closes: #357782 Files: a7f380e681e505bdd19ec191dab83071 1186 python extra python-f2py_2.45.241+1926-3.dsc cdb26da83bbf2ffbbd37f2fd43b189da 27680 python extra python-f2py_2.45.241+1926-3.diff.gz 54fa4a4041c250d141df0f66d48b2347 28258 python extra python-f2py-doc_2.45.241+1926-3_all.deb 747b9cb4cbce1b2b1f80bd42486a6a50 106534 python extra python2.3-f2py_2.45.241+1926-3_all.deb 1abc339f1a1390b673b74f42e8b9e39b 106530 python extra python2.4-f2py_2.45.241+1926-3_all.deb 299d1d099c32c2bb884c7969b7e013c5 20458 python extra python-f2py_2.45.241+1926-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iQEVAwUBRB6DOV6T+PKoJ87eAQK6EggAouTMtlKfRt+r/enO51g6jH9xXMcMTzOt LVHiqkYNdWBTgjW7fb965mZ+DVJtx6kc28xoeVTkf3FPecMwIgzSr72kTAVu43Dg fMbP0b/DuS4JKEYiE9Ibc0dN+EOpVVNLXa837gNhrohz3whFXPXa72eW/ROybYJX bWOEJFnFxQA2fzxoXFJqpAVSEi8EOFAhK16X+qy0TxXA2/awt/r7jd4qycLKZURp a2RksRL1KYEAMz1d4OWq4GOq3Uy43AY/P/irOEylM3VCWl23dX+MOqWEpGHuvCkG 6Z7Gq7etustdCIviSpIjls593okzFr13CN1Hc8he7eLPQ7cse70h8A== =ED4N -END PGP SIGNATURE- Accepted: python-f2py-doc_2.45.241+1926-3_all.deb to pool/main/p/python-f2py/python-f2py-doc_2.45.241+1926-3_all.deb python-f2py_2.45.241+1926-3.diff.gz to pool/main/p/python-f2py/python-f2py_2.45.241+1926-3.diff.gz python-f2py_2.45.241+1926-3.dsc to pool/main/p/python-f2py/python-f2py_2.45.241+1926-3.dsc python-f2py_2.45.241+1926-3_all.deb to pool/main/p/python-f2py/python-f2py_2.45.241+1926-3_all.deb python2.3-f2py_2.45.241+1926-3_all.deb to pool/main/p/python-f2py/python2.3-f2py_2.45.241+1926-3_all.deb python2.4-f2py_2.45.241+1926-3_all.deb to pool/main/p/python-f2py/python2.4-f2py_2.45.241+1926-3_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted wengophone 0.99+svn4511-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 20 Mar 2006 10:48:01 +0100 Source: wengophone Binary: wengophone Architecture: source i386 Version: 0.99+svn4511-2 Distribution: unstable Urgency: low Maintainer: Marco Nenciarini [EMAIL PROTECTED] Changed-By: Marco Nenciarini [EMAIL PROTECTED] Description: wengophone - SIP-based software telephone with video and chat features Closes: 357519 357866 Changes: wengophone (0.99+svn4511-2) unstable; urgency=low . * Added implicit-pointer-conversion patch. This patch fixes problem that will cause wengophone to segfault on architectures where the size of a pointer is greater than the size of an integer, such as ia64. Thanks to Dann Frazier [EMAIL PROTECTED] for the patch. (Closes: #357519) * Added gcc41 patch. This patch allow wengophone to be built with gcc-4.1 suite. Thanks to Martin Michlmayr [EMAIL PROTECTED] for the patch. (Closes: #357866) Files: c5efb87aea2a231a15e60f2ec83fcf9d 828 net optional wengophone_0.99+svn4511-2.dsc b2ab2db71ad22770ee6d9d05a69890b1 6891 net optional wengophone_0.99+svn4511-2.diff.gz d6679b6e249180139f9c056cb8f79a70 3461034 net optional wengophone_0.99+svn4511-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEHoJbaGRzDfCV5eQRArSgAJ9bxv0/3Ea8Y/WUa9wJjO0nIy4yugCdEeu2 tlpEsJpB57r/5TUweHk= =QMYU -END PGP SIGNATURE- Accepted: wengophone_0.99+svn4511-2.diff.gz to pool/main/w/wengophone/wengophone_0.99+svn4511-2.diff.gz wengophone_0.99+svn4511-2.dsc to pool/main/w/wengophone/wengophone_0.99+svn4511-2.dsc wengophone_0.99+svn4511-2_i386.deb to pool/main/w/wengophone/wengophone_0.99+svn4511-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fox1.4 1.4.31-1 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 20 Mar 2006 10:56:59 +0100 Source: fox1.4 Binary: libfox1.4-doc libfox1.4-dev libfox1.4 Architecture: source i386 all Version: 1.4.31-1 Distribution: unstable Urgency: low Maintainer: Torsten Landschoff [EMAIL PROTECTED] Changed-By: Torsten Landschoff [EMAIL PROTECTED] Description: libfox1.4 - The FOX C++ GUI Toolkit libfox1.4-dev - Development files for the FOX C++ GUI Toolkit libfox1.4-doc - Documentation of the FOX C++ GUI Toolkit Closes: 355998 357888 Changes: fox1.4 (1.4.31-1) unstable; urgency=low . * New upstream release (closes: #357888). * Apply patch by Martin Michlmayer to fix building with gcc 4.1 (closes: #355998). Kudos for the patch, Martin! Files: a00833edff0d33f81058f33f2d7ec127 776 - optional fox1.4_1.4.31-1.dsc 8b8c9d7adcca81da40f874d021ce2e41 4021871 - optional fox1.4_1.4.31.orig.tar.gz e7f2511b63f203ebde7fd90e1dd55acb 27538 - optional fox1.4_1.4.31-1.diff.gz adfdfe7df10f67371ae331d61313724d 2042334 doc optional libfox1.4-doc_1.4.31-1_all.deb 0e562e1e464f6263f44113ffee63d446 1011556 libs optional libfox1.4_1.4.31-1_i386.deb 305a4be0d4a8f591cd8890422f700555 1487080 libdevel optional libfox1.4-dev_1.4.31-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEHoGedQgHtVUb5EcRApeyAJ9cP0MGco/WimitUBvtS2WqRvjjKQCdEVqu ad93H4oFW6o0havjtNfprJI= =54aU -END PGP SIGNATURE- Accepted: fox1.4_1.4.31-1.diff.gz to pool/main/f/fox1.4/fox1.4_1.4.31-1.diff.gz fox1.4_1.4.31-1.dsc to pool/main/f/fox1.4/fox1.4_1.4.31-1.dsc fox1.4_1.4.31.orig.tar.gz to pool/main/f/fox1.4/fox1.4_1.4.31.orig.tar.gz libfox1.4-dev_1.4.31-1_i386.deb to pool/main/f/fox1.4/libfox1.4-dev_1.4.31-1_i386.deb libfox1.4-doc_1.4.31-1_all.deb to pool/main/f/fox1.4/libfox1.4-doc_1.4.31-1_all.deb libfox1.4_1.4.31-1_i386.deb to pool/main/f/fox1.4/libfox1.4_1.4.31-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libgnomecanvas 2.14.0-1 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 20 Mar 2006 11:16:50 +0100 Source: libgnomecanvas Binary: libgnomecanvas2-doc libgnomecanvas2-common libgnomecanvas2-0 libgnomecanvas2-dev Architecture: source all i386 Version: 2.14.0-1 Distribution: unstable Urgency: low Maintainer: OndÅej Surý [EMAIL PROTECTED] Changed-By: OndÅej Surý [EMAIL PROTECTED] Description: libgnomecanvas2-0 - A powerful object-oriented display - runtime files libgnomecanvas2-common - A powerful object-oriented display - common files libgnomecanvas2-dev - A powerful object-oriented display - development files libgnomecanvas2-doc - A powerful object-oriented display - documentation files Changes: libgnomecanvas (2.14.0-1) unstable; urgency=low . [ Oystein Gisnas ] * New upstream release * debian/watch: -- updated version to 2.14 * debian/control.in: -- Bumped debhelper dependency to = 4.1.0 * debian/libgnomecanvas2-doc.doc-base: -- Corrected path to index.sgml.gz . [ OndÅej Surý ] * Upload to unstable Files: 5d200e6ff26e3a8c84058ed12c8725e7 1785 devel optional libgnomecanvas_2.14.0-1.dsc d6e72907dbb24d10e67c4c19ef178b3f 845644 devel optional libgnomecanvas_2.14.0.orig.tar.gz 94ec74ec379b84fab3cff231d0cec320 4460 devel optional libgnomecanvas_2.14.0-1.diff.gz 8a7eed42677cd74ad620ff25588d6d9e 130968 x11 optional libgnomecanvas2-common_2.14.0-1_all.deb 07c988dc4da32540d46e6f32820aa9a7 76980 doc optional libgnomecanvas2-doc_2.14.0-1_all.deb 20e312939361e7ec1b48505bd3538606 106240 libs optional libgnomecanvas2-0_2.14.0-1_i386.deb a81daef63ebc1d6155ac60b2bfdfdacd 129622 libdevel optional libgnomecanvas2-dev_2.14.0-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEHoPR9OZqfMIN8nMRAk0hAJ4xUPKSWpS/sUIz2lludutR8hyvZgCdE1VC ltqGgyNbQ0E3nfulSrYfVXs= =5ktX -END PGP SIGNATURE- Accepted: libgnomecanvas2-0_2.14.0-1_i386.deb to pool/main/libg/libgnomecanvas/libgnomecanvas2-0_2.14.0-1_i386.deb libgnomecanvas2-common_2.14.0-1_all.deb to pool/main/libg/libgnomecanvas/libgnomecanvas2-common_2.14.0-1_all.deb libgnomecanvas2-dev_2.14.0-1_i386.deb to pool/main/libg/libgnomecanvas/libgnomecanvas2-dev_2.14.0-1_i386.deb libgnomecanvas2-doc_2.14.0-1_all.deb to pool/main/libg/libgnomecanvas/libgnomecanvas2-doc_2.14.0-1_all.deb libgnomecanvas_2.14.0-1.diff.gz to pool/main/libg/libgnomecanvas/libgnomecanvas_2.14.0-1.diff.gz libgnomecanvas_2.14.0-1.dsc to pool/main/libg/libgnomecanvas/libgnomecanvas_2.14.0-1.dsc libgnomecanvas_2.14.0.orig.tar.gz to pool/main/libg/libgnomecanvas/libgnomecanvas_2.14.0.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted spambayes 1.0.4-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 20 Mar 2006 11:36:54 +0100 Source: spambayes Binary: spambayes Architecture: source all Version: 1.0.4-1 Distribution: unstable Urgency: low Maintainer: Alexandre Fayolle [EMAIL PROTECTED] Changed-By: Alexandre Fayolle [EMAIL PROTECTED] Description: spambayes - Python-based spam filter using statistical analysis Changes: spambayes (1.0.4-1) unstable; urgency=low . * New upstream release * Use 3.6.2 standards * Use debhelper 5.0 * Added watch file for DEHS Files: 1a3df332de84f3f60cb592c333a03bae 895 mail optional spambayes_1.0.4-1.dsc 78c33e79888d410711ff3c7dd7e98d79 697781 mail optional spambayes_1.0.4.orig.tar.gz c866c09ea989367abb352025d73e0f71 4112 mail optional spambayes_1.0.4-1.diff.gz 378fd4cd61b8db6461aac3d0f098041f 347174 mail optional spambayes_1.0.4-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iQEVAwUBRB6IG16T+PKoJ87eAQL3WAf/Y27QvVHEqpJwPpL6vzmkuHmJp6bl2tou uzZq5K8l5zvuG51RaVqWyCJ4a1bXeX0vlO6vHLDimJT49d96oOlpn5R5A7WdN5uM OUts7346A6D13DHWSOrNmlhNQtzthC8JGTXBO4I4BFMLmxPdeORjzCg9UUeVrDxt iIPsqgEa4J/vk6YcrT0Ou0w4d5jChlITFzt9wNh9x0VDH+MbCRbLKq8WYLllRJ9k xg8LjGCcGe76bvtglkpdr5A8fRdusyGhFSpyEyyaER0BqlHyJAfzJD8tGMXTKiec RJbOBcCdJE570Ra9Ykx6XcK7mfuPtDvLhxl2L0hmkgEPD+y5YBFpOA== =ckTV -END PGP SIGNATURE- Accepted: spambayes_1.0.4-1.diff.gz to pool/main/s/spambayes/spambayes_1.0.4-1.diff.gz spambayes_1.0.4-1.dsc to pool/main/s/spambayes/spambayes_1.0.4-1.dsc spambayes_1.0.4-1_all.deb to pool/main/s/spambayes/spambayes_1.0.4-1_all.deb spambayes_1.0.4.orig.tar.gz to pool/main/s/spambayes/spambayes_1.0.4.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted phpmyadmin 4:2.8.0.2-3 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 20 Mar 2006 11:06:09 +0100 Source: phpmyadmin Binary: phpmyadmin Architecture: source all Version: 4:2.8.0.2-3 Distribution: unstable Urgency: low Maintainer: Piotr Roszatycki [EMAIL PROTECTED] Changed-By: Piotr Roszatycki [EMAIL PROTECTED] Description: phpmyadmin - set of PHP-scripts to administrate MySQL over the WWW Closes: 357579 357743 357840 Changes: phpmyadmin (4:2.8.0.2-3) unstable; urgency=low . * Add missing javascript files. Closes: #357743, #357579. * Updated Brazilian Portuguese debconf templates translation, thanks Andre Luis Lopes. Closes: #357840. Files: 09934c540308b427e92469e818ffe3c6 642 web extra phpmyadmin_2.8.0.2-3.dsc a61ce9a06b9449722440ac6f5518fa60 36018 web extra phpmyadmin_2.8.0.2-3.diff.gz 01bf2519b13b7b2250e4c95777f3f367 3619618 web extra phpmyadmin_2.8.0.2-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEHoP2hMHHe8CxClsRAncyAJ9GFIrBOOvpuCbk0vugFmkQg/fUgACgsHdR 0a3HPCrWFGy/aiKCJ/zOHgE= =QVe5 -END PGP SIGNATURE- Accepted: phpmyadmin_2.8.0.2-3.diff.gz to pool/main/p/phpmyadmin/phpmyadmin_2.8.0.2-3.diff.gz phpmyadmin_2.8.0.2-3.dsc to pool/main/p/phpmyadmin/phpmyadmin_2.8.0.2-3.dsc phpmyadmin_2.8.0.2-3_all.deb to pool/main/p/phpmyadmin/phpmyadmin_2.8.0.2-3_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted postfix-policyd 1.73-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 20 Mar 2006 11:09:56 +0100 Source: postfix-policyd Binary: postfix-policyd Architecture: source i386 Version: 1.73-1 Distribution: unstable Urgency: low Maintainer: OndÅej Surý [EMAIL PROTECTED] Changed-By: OndÅej Surý [EMAIL PROTECTED] Description: postfix-policyd - anti-spam plugin for Postfix Closes: 354945 Changes: postfix-policyd (1.73-1) unstable; urgency=low . * New upstream release. * Remove bashisms from maintainer scripts. (Closes: #354945) Files: 11d25b3c9e9bedc4f7f080e0934f9d8a 645 mail optional postfix-policyd_1.73-1.dsc 25965546d9e54aee6d0d8f05674bf9d0 61381 mail optional postfix-policyd_1.73.orig.tar.gz 451086babc3e400c9b2463f0e2bcf2b5 10132 mail optional postfix-policyd_1.73-1.diff.gz fd03cb8d2c14e8cfdeb5c0887547f13c 65632 mail optional postfix-policyd_1.73-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEHoq19OZqfMIN8nMRAkwUAJ96P9raIsWk3a/xF+GJOybX0G4KkACdF0OS /V4VA/uDUdDz5yyTmgvS8P4= =9ETY -END PGP SIGNATURE- Accepted: postfix-policyd_1.73-1.diff.gz to pool/main/p/postfix-policyd/postfix-policyd_1.73-1.diff.gz postfix-policyd_1.73-1.dsc to pool/main/p/postfix-policyd/postfix-policyd_1.73-1.dsc postfix-policyd_1.73-1_i386.deb to pool/main/p/postfix-policyd/postfix-policyd_1.73-1_i386.deb postfix-policyd_1.73.orig.tar.gz to pool/main/p/postfix-policyd/postfix-policyd_1.73.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted curl 7.15.3-1 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 20 Mar 2006 11:46:25 +0100 Source: curl Binary: libcurl3-dbg libcurl3 libcurl3-dev libcurl3-gnutls-dev libcurl3-openssl-dev libcurl3-gnutls curl Architecture: source i386 all Version: 7.15.3-1 Distribution: unstable Urgency: high Maintainer: Domenico Andreoli [EMAIL PROTECTED] Changed-By: Domenico Andreoli [EMAIL PROTECTED] Description: curl - Get a file from an HTTP, HTTPS, FTP or GOPHER server libcurl3 - Multi-protocol file transfer library libcurl3-dbg - libcurl compiled with debug symbols libcurl3-dev - Transitional package to libcurl3-openssl-dev libcurl3-gnutls - Multi-protocol file transfer library libcurl3-gnutls-dev - Development files and documentation for libcurl libcurl3-openssl-dev - Development files and documentation for libcurl Closes: 357388 Changes: curl (7.15.3-1) unstable; urgency=high . * New upstream release: - fixed TFTP packet buffer overflow vulnerability [lib/tftp.c, CVE-2006-1061]. - improved curl_getenv.3 manpage grammar (closes: #357388). Files: 54b2a37d4d210aec6926c29b44cdbcbc 940 web optional curl_7.15.3-1.dsc fd119618f7d657a90efb76678e3f9da7 1818520 web optional curl_7.15.3.orig.tar.gz 2a153ed079a6c00c6098679dc3d34575 17500 web optional curl_7.15.3-1.diff.gz 8d83a6e9c750d2b030444192b1b1f01e 175480 web optional curl_7.15.3-1_i386.deb a2b2d7bb3041f0371347371341cbb159 177122 libs optional libcurl3_7.15.3-1_i386.deb 326d4729081fa72f03981236415dba03 172020 libs optional libcurl3-gnutls_7.15.3-1_i386.deb 2523714439265902029c56fbc05ff9f5 738340 libdevel optional libcurl3-openssl-dev_7.15.3-1_i386.deb 6d9982ec9ed3cb8804953553f045fd6c 732098 libdevel optional libcurl3-gnutls-dev_7.15.3-1_i386.deb c10fcb429c2b019d4caebd5c54f3ccf8 34676 libdevel optional libcurl3-dev_7.15.3-1_all.deb d4dd5685db992728f6c3907ef70f6283 762808 libdevel extra libcurl3-dbg_7.15.3-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEHotQBneQM6IOvFARAg/dAKDfbkLjhuIYoTfblzCH0hCPlOT4dACfc7SB 1WzV++YircQ0fN6T8ai+nAo= =JtB8 -END PGP SIGNATURE- Accepted: curl_7.15.3-1.diff.gz to pool/main/c/curl/curl_7.15.3-1.diff.gz curl_7.15.3-1.dsc to pool/main/c/curl/curl_7.15.3-1.dsc curl_7.15.3-1_i386.deb to pool/main/c/curl/curl_7.15.3-1_i386.deb curl_7.15.3.orig.tar.gz to pool/main/c/curl/curl_7.15.3.orig.tar.gz libcurl3-dbg_7.15.3-1_i386.deb to pool/main/c/curl/libcurl3-dbg_7.15.3-1_i386.deb libcurl3-dev_7.15.3-1_all.deb to pool/main/c/curl/libcurl3-dev_7.15.3-1_all.deb libcurl3-gnutls-dev_7.15.3-1_i386.deb to pool/main/c/curl/libcurl3-gnutls-dev_7.15.3-1_i386.deb libcurl3-gnutls_7.15.3-1_i386.deb to pool/main/c/curl/libcurl3-gnutls_7.15.3-1_i386.deb libcurl3-openssl-dev_7.15.3-1_i386.deb to pool/main/c/curl/libcurl3-openssl-dev_7.15.3-1_i386.deb libcurl3_7.15.3-1_i386.deb to pool/main/c/curl/libcurl3_7.15.3-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted surfraw 2.1.4 (source all)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Fri, 17 Mar 2006 22:26:37 +
Source: surfraw
Binary: surfraw
Architecture: source all
Version: 2.1.4
Distribution: unstable
Urgency: low
Maintainer: Debian surfraw maintainers [EMAIL PROTECTED]
Changed-By: Ian Beckwith [EMAIL PROTECTED]
Description:
surfraw- a fast unix command line interface to WWW
Closes: 354737
Changes:
surfraw (2.1.4) unstable; urgency=low
.
* Ian Beckwith [EMAIL PROTECTED]:
+ changed elvi:
- debsec: fix tabbing (Closes: #354737).
- debbugs: updated search options.
+ new elvi:
- ixquick (Thanks to Aparna Jaitly).
- ctan.
- fsfdir.
- gutenberg.
- wayback.
+ Makefile.include: changed sed invocation to work with
both old and new make(1).
+ debian/rules install: removed spurious mkdir.
+ removed debian/{prerm,postinst}.
+ Switched to debhelper compat level 4.
+ HACKING: corrected appendix 1.
Files:
44c63476a392c8b959a89d9d3ce4a494 648 web optional surfraw_2.1.4.dsc
7195bd3051098d074c041cbf26d88342 139981 web optional surfraw_2.1.4.tar.gz
d19d0b35841eaa8a13a4cf712983f3bf 74858 web optional surfraw_2.1.4_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.2 (GNU/Linux)
iD8DBQFEHo53Xm3vHE4uyloRAvqIAKDY1zgASSL5hKWB92TRo3r0GwCqAwCgi5oR
ElIpLPGnmqfbGyhrRllaHaY=
=T7q7
-END PGP SIGNATURE-
Accepted:
surfraw_2.1.4.dsc
to pool/main/s/surfraw/surfraw_2.1.4.dsc
surfraw_2.1.4.tar.gz
to pool/main/s/surfraw/surfraw_2.1.4.tar.gz
surfraw_2.1.4_all.deb
to pool/main/s/surfraw/surfraw_2.1.4_all.deb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted desktop-profiles 1.4.11 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 14 Mar 2006 18:38:59 +0100 Source: desktop-profiles Binary: desktop-profiles Architecture: source all Version: 1.4.11 Distribution: unstable Urgency: low Maintainer: Bart Cornelis (cobaco) [EMAIL PROTECTED] Changed-By: Bart Cornelis (cobaco) [EMAIL PROTECTED] Description: desktop-profiles - framework for setting up desktop profiles Changes: desktop-profiles (1.4.11) unstable; urgency=low . * Added shell-specific fix for the 'ssh -X' bug for psh shell. * psh version 1.8-6 and zoidberg 0.96-1 modularized their system-wide on-login file, so we now apply the 'ssh -X' fix automatically for these two shells. * Set debhelper compatibility level to 5 Files: 059ff20b0c3717b8a6519420fed87a9a 620 x11 optional desktop-profiles_1.4.11.dsc db9f75c990054fe877307b95a0613119 70994 x11 optional desktop-profiles_1.4.11.tar.gz 7e5470cc1087d788b6dd51ecf5d61fd1 63678 x11 optional desktop-profiles_1.4.11_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEHo+Ph0XdeHWCwhoRAgWOAJwN/cayVWhHyT6NVZGdF/d/JRlOmwCferYY q1v+Z73a58AYJNyfPYVjGpI= =8gUJ -END PGP SIGNATURE- Accepted: desktop-profiles_1.4.11.dsc to pool/main/d/desktop-profiles/desktop-profiles_1.4.11.dsc desktop-profiles_1.4.11.tar.gz to pool/main/d/desktop-profiles/desktop-profiles_1.4.11.tar.gz desktop-profiles_1.4.11_all.deb to pool/main/d/desktop-profiles/desktop-profiles_1.4.11_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted python-ldap 2.0.11-2 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 20 Mar 2006 12:29:57 +0100 Source: python-ldap Binary: python2.4-ldap python2.3-ldap python-ldap-doc python-ldap Architecture: source i386 all Version: 2.0.11-2 Distribution: unstable Urgency: low Maintainer: Matej Vela [EMAIL PROTECTED] Changed-By: Matej Vela [EMAIL PROTECTED] Description: python-ldap - An LDAP interface module for Python. [dummy package] python-ldap-doc - Documentation for the Python LDAP interface module python2.3-ldap - An LDAP interface module for Python 2.3 python2.4-ldap - An LDAP interface module for Python 2.4 Closes: 357932 Changes: python-ldap (2.0.11-2) unstable; urgency=low . * debian/patches/result3_tuple_size.diff: Fix tuple size in result3(). Thanks to Alessandro Ogier for the patch (SF#1368108; fixed in CVS). Closes: #357932. Files: df219e3b3dc71b5ecf2be75f42e0c607 705 python optional python-ldap_2.0.11-2.dsc 62872db9e95e882200f0aa30cb607adb 5207 python optional python-ldap_2.0.11-2.diff.gz 11e180d9800e89c6801660f1e3ba997d 986 python optional python-ldap_2.0.11-2_all.deb 4deb3f98a110a9d174adbeb8ac6268d3 48720 doc optional python-ldap-doc_2.0.11-2_all.deb a8201218fd70c67b97f55def1dcea74a 66328 python optional python2.3-ldap_2.0.11-2_i386.deb d3c98a4f2380253747d5ed10cfbab50c 66318 python optional python2.4-ldap_2.0.11-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEHpJkxBYivKllgY8RAgBRAJ9n+LPGVtsZXtc+qdHL3UjrDl3/hACgh2Ib zhoiG75Uad4I8LbgKypNLp8= =bYam -END PGP SIGNATURE- Accepted: python-ldap-doc_2.0.11-2_all.deb to pool/main/p/python-ldap/python-ldap-doc_2.0.11-2_all.deb python-ldap_2.0.11-2.diff.gz to pool/main/p/python-ldap/python-ldap_2.0.11-2.diff.gz python-ldap_2.0.11-2.dsc to pool/main/p/python-ldap/python-ldap_2.0.11-2.dsc python-ldap_2.0.11-2_all.deb to pool/main/p/python-ldap/python-ldap_2.0.11-2_all.deb python2.3-ldap_2.0.11-2_i386.deb to pool/main/p/python-ldap/python2.3-ldap_2.0.11-2_i386.deb python2.4-ldap_2.0.11-2_i386.deb to pool/main/p/python-ldap/python2.4-ldap_2.0.11-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted beagle 0.2.3-1 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 19 Mar 2006 17:20:49 +0100 Source: beagle Binary: beagle python-beagle beagle-dev beagle-backend-evolution libbeagle0 Architecture: source i386 all Version: 0.2.3-1 Distribution: unstable Urgency: low Maintainer: Jose Carlos Garcia Sogo [EMAIL PROTECTED] Changed-By: Jose Carlos Garcia Sogo [EMAIL PROTECTED] Description: beagle - indexing and search tool for your personal data beagle-backend-evolution - evolution data backend for beagle beagle-dev - library for accessing beagle (development files) libbeagle0 - library for accessing beagle (development files) python-beagle - python bindings for beagle Closes: 341387 355831 356732 357102 357392 Changes: beagle (0.2.3-1) unstable; urgency=low . * New upstream release. * debian/patches: + beagle-status_watch: don't check for local beagle-info (Closes: #357392) * debian/beagle.dirs: + create /usr/share/doc/beagle/mozilla-extension in order to install there beagle.xpi file for mozilla extension. (Closes: #357102) * debian/control: + make beagle bin package to depend on gnome-icon-theme (Closes: #355831) * relibtoolize.dpatch: + remake configure script to avoid checking for libxt (Closes: #356732) * README.Debian: + state that XFS and JFS has extended attributes enabled by default. Thanks to Jesper Louis Andersen for pointing me this. + talk about BEAGLE_STORAGE option, which will allows to change default path for storing index files. (Closes: #341387) Files: 80bcefcf1a51c42837b8c4f203bdcafe 1022 gnome optional beagle_0.2.3-1.dsc 061e973f7b7ce3daf4613b1a11eecdad 1703932 gnome optional beagle_0.2.3.orig.tar.gz f0821a20d515cb081f0249f158c49436 16246 gnome optional beagle_0.2.3-1.diff.gz b78e17ba6edf25b11ce59f84c736af12 1334698 gnome optional beagle_0.2.3-1_i386.deb d12c515afea712969e4f8a2e4f1af2dd 57766 gnome optional beagle-backend-evolution_0.2.3-1_all.deb 140d4c3876f43f7b0377d9ddeb5b0a5d 54742 gnome optional libbeagle0_0.2.3-1_i386.deb cefc0377588b56afc9931f38d1e6d8b0 68572 gnome optional beagle-dev_0.2.3-1_i386.deb 0a83a6637812293818830a7e7a8b626a 41336 gnome optional python-beagle_0.2.3-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEHb1fS+BYJZB4jhERAm6eAJ499W7Xq4K6Cz5odGeLYSCDE/ZDxQCggt4a FgYqn4N0aXFpUe0S83BZBwE= =nbZb -END PGP SIGNATURE- Accepted: beagle-backend-evolution_0.2.3-1_all.deb to pool/main/b/beagle/beagle-backend-evolution_0.2.3-1_all.deb beagle-dev_0.2.3-1_i386.deb to pool/main/b/beagle/beagle-dev_0.2.3-1_i386.deb beagle_0.2.3-1.diff.gz to pool/main/b/beagle/beagle_0.2.3-1.diff.gz beagle_0.2.3-1.dsc to pool/main/b/beagle/beagle_0.2.3-1.dsc beagle_0.2.3-1_i386.deb to pool/main/b/beagle/beagle_0.2.3-1_i386.deb beagle_0.2.3.orig.tar.gz to pool/main/b/beagle/beagle_0.2.3.orig.tar.gz libbeagle0_0.2.3-1_i386.deb to pool/main/b/beagle/libbeagle0_0.2.3-1_i386.deb python-beagle_0.2.3-1_i386.deb to pool/main/b/beagle/python-beagle_0.2.3-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libmodule-install-perl 0.61-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 20 Mar 2006 12:35:42 +0100 Source: libmodule-install-perl Binary: libmodule-install-perl Architecture: source all Version: 0.61-1 Distribution: unstable Urgency: low Maintainer: Debian Perl Group [EMAIL PROTECTED] Changed-By: Krzysztof Krzyzaniak (eloy) [EMAIL PROTECTED] Description: libmodule-install-perl - A Cornucopiaelig of Module::Install Recipes Changes: libmodule-install-perl (0.61-1) unstable; urgency=low . * New upstream release Files: 289ad6017b261689efdcd4655f47f801 916 perl optional libmodule-install-perl_0.61-1.dsc 1af1f0c4a9ae33433d1f5563f08e1d3a 73362 perl optional libmodule-install-perl_0.61.orig.tar.gz 682c5885cbf95dd99823823ef8624c36 2293 perl optional libmodule-install-perl_0.61-1.diff.gz 16980cd1e062d366e215e99536388cba 102820 perl optional libmodule-install-perl_0.61-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEHpf/+NMfSd6w7DERAouJAJ9XlEu+V2rthuYShUZvLwk2wGpfZACgsQ9e 9OqvEc6+zDjz4exkYKL2C7E= =lpJI -END PGP SIGNATURE- Accepted: libmodule-install-perl_0.61-1.diff.gz to pool/main/libm/libmodule-install-perl/libmodule-install-perl_0.61-1.diff.gz libmodule-install-perl_0.61-1.dsc to pool/main/libm/libmodule-install-perl/libmodule-install-perl_0.61-1.dsc libmodule-install-perl_0.61-1_all.deb to pool/main/libm/libmodule-install-perl/libmodule-install-perl_0.61-1_all.deb libmodule-install-perl_0.61.orig.tar.gz to pool/main/libm/libmodule-install-perl/libmodule-install-perl_0.61.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted zlibc 0.9k-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 20 Mar 2006 11:59:35 +0100 Source: zlibc Binary: zlibc Architecture: source i386 Version: 0.9k-1 Distribution: unstable Urgency: high Maintainer: Francesco Paolo Lovergine [EMAIL PROTECTED] Changed-By: Francesco Paolo Lovergine [EMAIL PROTECTED] Description: zlibc - Uncompressing C Library Closes: 298607 353780 Changes: zlibc (0.9k-1) unstable; urgency=high . The 'Better now than never' release. . * New upstream release (closes: #353780, #298607) * Policy updated to 3.6.2 (no changes) * Added hand-built manpages, due to obsolete texi2roff missing. * Overall changes: - debian/rules revised for changes in configuration and other stuff. - debian/links removed - debian/manpages (new) - debian/dirs (new) * Added a NEWS file to inform about changes in the upstream product. * Removed -O4 optimization in configure.in * Rebuilt configure once by autoconf2.13 Files: 3d78ceba108b81f4ed7440be4e340bcf 597 libs optional zlibc_0.9k-1.dsc f385aa826cd1cf741dd49998d706d2f5 111773 libs optional zlibc_0.9k.orig.tar.gz bb1c53f3001a133d34b5ac89ab6492ff 75789 libs optional zlibc_0.9k-1.diff.gz 96f98a6b8b61d0b2c8795d5127d0a79c 69698 libs optional zlibc_0.9k-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEHpr4pFNRmenyx0cRAvidAJ9N400DbrYAEhF9FQZBw+UhumydRACgto0e RtdB71GiIKYZNul/vqJyEdg= =pkbw -END PGP SIGNATURE- Accepted: zlibc_0.9k-1.diff.gz to pool/main/z/zlibc/zlibc_0.9k-1.diff.gz zlibc_0.9k-1.dsc to pool/main/z/zlibc/zlibc_0.9k-1.dsc zlibc_0.9k-1_i386.deb to pool/main/z/zlibc/zlibc_0.9k-1_i386.deb zlibc_0.9k.orig.tar.gz to pool/main/z/zlibc/zlibc_0.9k.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted pango1.0 1.12.0-1 (source all powerpc)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 19 Mar 2006 12:11:29 +0100 Source: pango1.0 Binary: libpango1.0-dev libpango1.0-0 libpango1.0-doc libpango1.0-udeb libpango1.0-dbg libpango1.0-common Architecture: source powerpc all Version: 1.12.0-1 Distribution: unstable Urgency: low Maintainer: Jordi Mallach [EMAIL PROTECTED] Changed-By: Jordi Mallach [EMAIL PROTECTED] Description: libpango1.0-0 - Layout and rendering of internationalized text libpango1.0-common - Modules and configuration files for the Pango libpango1.0-dbg - The Pango library and debugging symbols libpango1.0-dev - Development files for the Pango libpango1.0-doc - Documentation files for the Pango libpango1.0-udeb - Layout and rendering of internationalized text (udeb) Changes: pango1.0 (1.12.0-1) unstable; urgency=low . * New upstream release. * debian/control.in: Bump glib build and runtime dependencies again. * debian/watch: use download.gnome.org and look in the 2.12 directory. Files: fa3e1e18493ac879ab75c1a40d6d14f2 1885 libs optional pango1.0_1.12.0-1.dsc 59e10e514a3de5db9723e93e1379a88f 1625346 libs optional pango1.0_1.12.0.orig.tar.gz 2b4f44672a1ba0b74e09061970fa6c8f 33562 libs optional pango1.0_1.12.0-1.diff.gz f084992d788d03e33a7133636fe54fb3 202860 doc optional libpango1.0-doc_1.12.0-1_all.deb aac5ec1d2816bc889a63ebe460a6269d 193960 debian-installer optional libpango1.0-udeb_1.12.0-1_powerpc.udeb b85fa1161ee96afb71462b7dd2dd2bdc 308510 libs optional libpango1.0-0_1.12.0-1_powerpc.deb e71e8a4c8eb3167e2eab3ffadb5e2eae 36108 misc optional libpango1.0-common_1.12.0-1_powerpc.deb f4bc236bd33aeff34bdb6c4d606bb694 348984 libdevel optional libpango1.0-dev_1.12.0-1_powerpc.deb 569e049be374195c170939d458b79b61 715164 libdevel extra libpango1.0-dbg_1.12.0-1_powerpc.deb Package-Type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEHqeFJYSUupF6Il4RAquUAJ4+3HgoyNMweRF4JKIFV46Z20vslgCg8V1p K/9cp1LZT9ua7Fs2llMgvH0= =H+IS -END PGP SIGNATURE- Accepted: libpango1.0-0_1.12.0-1_powerpc.deb to pool/main/p/pango1.0/libpango1.0-0_1.12.0-1_powerpc.deb libpango1.0-common_1.12.0-1_powerpc.deb to pool/main/p/pango1.0/libpango1.0-common_1.12.0-1_powerpc.deb libpango1.0-dbg_1.12.0-1_powerpc.deb to pool/main/p/pango1.0/libpango1.0-dbg_1.12.0-1_powerpc.deb libpango1.0-dev_1.12.0-1_powerpc.deb to pool/main/p/pango1.0/libpango1.0-dev_1.12.0-1_powerpc.deb libpango1.0-doc_1.12.0-1_all.deb to pool/main/p/pango1.0/libpango1.0-doc_1.12.0-1_all.deb libpango1.0-udeb_1.12.0-1_powerpc.udeb to pool/main/p/pango1.0/libpango1.0-udeb_1.12.0-1_powerpc.udeb pango1.0_1.12.0-1.diff.gz to pool/main/p/pango1.0/pango1.0_1.12.0-1.diff.gz pango1.0_1.12.0-1.dsc to pool/main/p/pango1.0/pango1.0_1.12.0-1.dsc pango1.0_1.12.0.orig.tar.gz to pool/main/p/pango1.0/pango1.0_1.12.0.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted toppler 1.1.2a-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 20 Mar 2006 11:45:10 +0100 Source: toppler Binary: toppler Architecture: source i386 Version: 1.1.2a-2 Distribution: unstable Urgency: low Maintainer: Bill Allombert [EMAIL PROTECTED] Changed-By: Bill Allombert [EMAIL PROTECTED] Description: toppler- clone of the Nebulus game on old 8 and 16 bit machines Closes: 356091 Changes: toppler (1.1.2a-2) unstable; urgency=low . * Fix toppler path in .desktop file. Thanks Sebastien Montagne. Closes: #356091 * Fix inaccurate comments in debian/rules. Files: 9c6499bcc913a76e86f04cb29310ba62 665 games optional toppler_1.1.2a-2.dsc c14c119aa6f2306ff9838498fe9dda8d 5426 games optional toppler_1.1.2a-2.diff.gz 402a67c61f96e26bfdf835fb1d12497f 1012556 games optional toppler_1.1.2a-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEHo+keDPs8bVESBURAvOLAJwKfONmQiKaURn9kzBFBrF3Cg17hACgmqIb OB/YKD8jiwTUEAGJL2Y9kIk= =yW7x -END PGP SIGNATURE- Accepted: toppler_1.1.2a-2.diff.gz to pool/main/t/toppler/toppler_1.1.2a-2.diff.gz toppler_1.1.2a-2.dsc to pool/main/t/toppler/toppler_1.1.2a-2.dsc toppler_1.1.2a-2_i386.deb to pool/main/t/toppler/toppler_1.1.2a-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted zlibc 0.9k-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 20 Mar 2006 14:16:25 +0100 Source: zlibc Binary: zlibc Architecture: source i386 Version: 0.9k-2 Distribution: unstable Urgency: high Maintainer: Francesco Paolo Lovergine [EMAIL PROTECTED] Changed-By: Francesco Paolo Lovergine [EMAIL PROTECTED] Description: zlibc - Uncompressing C Library Changes: zlibc (0.9k-2) unstable; urgency=high . * Bah, really adding NEWS to released doc. Files: f11d095c9bd9cc546e2aa631f5ab7620 597 libs optional zlibc_0.9k-2.dsc 8a161a9085fa18275d45c2bd65f1f135 75829 libs optional zlibc_0.9k-2.diff.gz a8d7bd0625594d1078e37204d5f3ae38 70114 libs optional zlibc_0.9k-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEHquApFNRmenyx0cRAs7QAKDDTOy3fSHslaqccVOGCc3j2RxeJgCbBqI8 b+nUIM3kxMfqwLEZdBZnS2w= =aQSh -END PGP SIGNATURE- Accepted: zlibc_0.9k-2.diff.gz to pool/main/z/zlibc/zlibc_0.9k-2.diff.gz zlibc_0.9k-2.dsc to pool/main/z/zlibc/zlibc_0.9k-2.dsc zlibc_0.9k-2_i386.deb to pool/main/z/zlibc/zlibc_0.9k-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gmetadom 0.2.3-6 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 20 Mar 2006 00:21:07 -0500 Source: gmetadom Binary: libgdome2-cpp-smart0c2a libgdome2-cpp-smart-dev libgdome2-ocaml-dev libgdome2-ocaml Architecture: source i386 Version: 0.2.3-6 Distribution: unstable Urgency: low Maintainer: Stefano Zacchiroli [EMAIL PROTECTED] Changed-By: Stefano Zacchiroli [EMAIL PROTECTED] Description: libgdome2-cpp-smart-dev - C++ bindings for GDome2 DOM implementation libgdome2-cpp-smart0c2a - C++ bindings for GDome2 DOM implementation libgdome2-ocaml - OCaml bindings for GDome2 DOM implementation libgdome2-ocaml-dev - OCaml bindings for GDome2 DOM implementation Closes: 357600 Changes: gmetadom (0.2.3-6) unstable; urgency=low . * Added patch 11_g++41, which fixes FTBFS with g++ 4.1 (closes: #357600) Files: 49b2a4d3d29c10a5e47127659ec7a39e 747 devel optional gmetadom_0.2.3-6.dsc 94d33550dc459317e33b39afabd6a7a4 7218 devel optional gmetadom_0.2.3-6.diff.gz 7645935874b9e5cc032a223ff5059232 45894 libs optional libgdome2-cpp-smart0c2a_0.2.3-6_i386.deb 96044094942a856a78e5e8da6885012c 61548 libdevel optional libgdome2-cpp-smart-dev_0.2.3-6_i386.deb 50e465eb69c95f7cac1871ae33da7394 27600 libs optional libgdome2-ocaml_0.2.3-6_i386.deb 5063f2239536e548daf653176ea3eb1b 226384 libdevel optional libgdome2-ocaml-dev_0.2.3-6_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEHrZ01cqbBPLEI7wRAu5FAKCFPeJhw2yUQfoQ4iBMI9TudACgtheo Gx5aODXq1/PwpzwaAh0KmKc= =7h+i -END PGP SIGNATURE- Accepted: gmetadom_0.2.3-6.diff.gz to pool/main/g/gmetadom/gmetadom_0.2.3-6.diff.gz gmetadom_0.2.3-6.dsc to pool/main/g/gmetadom/gmetadom_0.2.3-6.dsc libgdome2-cpp-smart-dev_0.2.3-6_i386.deb to pool/main/g/gmetadom/libgdome2-cpp-smart-dev_0.2.3-6_i386.deb libgdome2-cpp-smart0c2a_0.2.3-6_i386.deb to pool/main/g/gmetadom/libgdome2-cpp-smart0c2a_0.2.3-6_i386.deb libgdome2-ocaml-dev_0.2.3-6_i386.deb to pool/main/g/gmetadom/libgdome2-ocaml-dev_0.2.3-6_i386.deb libgdome2-ocaml_0.2.3-6_i386.deb to pool/main/g/gmetadom/libgdome2-ocaml_0.2.3-6_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mesa 6.4.1-0.4 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 6 Mar 2006 21:46:18 -0500 Source: mesa Binary: libgl1-mesa-swx11-dev libgl1-mesa-glx libosmesa6-dev libgl1-mesa-dev libosmesa6 mesa-swx11-source libglu1-mesa-dev mesa-common-dev libglu1-mesa libgl1-mesa-dri libgl1-mesa-directfb-dev libgl1-mesa-swx11-dbg libgl1-mesa-swx11 libgl1-mesa-directfb Architecture: source i386 all Version: 6.4.1-0.4 Distribution: unstable Urgency: low Maintainer: Mesa package maintainers [EMAIL PROTECTED] Changed-By: David Nusinow [EMAIL PROTECTED] Description: libgl1-mesa-dev - A free implementation of the OpenGL API -- GLX development suppor libgl1-mesa-directfb - A free implementation of the OpenGL API -- DirectFB runtime libgl1-mesa-directfb-dev - A free implementation of the OpenGL API -- DirectFB development s libgl1-mesa-dri - A free implementation of the OpenGL API -- DRI modules libgl1-mesa-glx - A free implementation of the OpenGL API -- GLX runtime libgl1-mesa-swx11 - A free implementation of the OpenGL API -- runtime libgl1-mesa-swx11-dbg - A free implementation of the OpenGL API -- debugging package libgl1-mesa-swx11-dev - A free implementation of the OpenGL API -- development support fi libglu1-mesa - The OpenGL utility library (GLU) libglu1-mesa-dev - The OpenGL utility library -- development support files libosmesa6 - Mesa Off-screen rendering extension libosmesa6-dev - Mesa Off-screen rendering extension -- development support files mesa-common-dev - Developer documentation for Mesa mesa-swx11-source - Mesa software rasteriser source -- development support files Changes: mesa (6.4.1-0.4) unstable; urgency=low . * NMU * Add versioned conflict between libgl1-mesa-dri and xlibmesa-dri so that the xlibmesa-dri transitional upgrade package works Files: 9d40846f5ea629b26b5c46b4f1642bd6 1058 graphics optional mesa_6.4.1-0.4.dsc 91492adf77d88fe621839a14634bc2f4 62687 graphics optional mesa_6.4.1-0.4.diff.gz 451d227d4f5ba448f3133152643b68e8 166104 devel optional mesa-common-dev_6.4.1-0.4_all.deb 9894ab3a6eaad88eab818beb20203508 1107924 libdevel optional mesa-swx11-source_6.4.1-0.4_all.deb 061b32961806a71ef2267c62a4db349d 1765854 libs optional libgl1-mesa-swx11_6.4.1-0.4_i386.deb 3e3d7c63b08f284dd86a607b149221b5 2084302 libdevel optional libgl1-mesa-swx11-dev_6.4.1-0.4_i386.deb a6d3c5d01bbc422750ce2a85ef904705 196 libs optional libgl1-mesa-swx11-dbg_6.4.1-0.4_i386.deb cddb043617033f0f14379a68a759b9fe 164934 libs optional libgl1-mesa-glx_6.4.1-0.4_i386.deb 4fde8e6ca66da72f89cdb692e44bcc43 12283504 libs optional libgl1-mesa-dri_6.4.1-0.4_i386.deb 2789d80e75d956790d4fc7695edba967 45356 libs optional libgl1-mesa-dev_6.4.1-0.4_i386.deb 3fb033f880dfdeb2027a0427483ad5e3 761352 libs optional libgl1-mesa-directfb_6.4.1-0.4_i386.deb 3a4eea573398d51915cefc6540baee36 34502 libs optional libgl1-mesa-directfb-dev_6.4.1-0.4_i386.deb cb1a70cdae7e277e21e937563c741a47 1471048 libs optional libosmesa6_6.4.1-0.4_i386.deb 1a41b38937815ca78f1a3415bbe14bfa 1711602 devel optional libosmesa6-dev_6.4.1-0.4_i386.deb e8e24f82ccacb11f79840e685ce13c63 238432 libs optional libglu1-mesa_6.4.1-0.4_i386.deb 69d322c103bb8311363692ee4afb34b1 270332 libdevel optional libglu1-mesa-dev_6.4.1-0.4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEHq3yyLfpNdY0ad8RAofJAJwP62BixPVhw43rV9f5SAzU1qui2wCdG69q zqvC/F5V4Y/FucUZXL9UwQ0= =Dq1v -END PGP SIGNATURE- Accepted: libgl1-mesa-dev_6.4.1-0.4_i386.deb to pool/main/m/mesa/libgl1-mesa-dev_6.4.1-0.4_i386.deb libgl1-mesa-directfb-dev_6.4.1-0.4_i386.deb to pool/main/m/mesa/libgl1-mesa-directfb-dev_6.4.1-0.4_i386.deb libgl1-mesa-directfb_6.4.1-0.4_i386.deb to pool/main/m/mesa/libgl1-mesa-directfb_6.4.1-0.4_i386.deb libgl1-mesa-dri_6.4.1-0.4_i386.deb to pool/main/m/mesa/libgl1-mesa-dri_6.4.1-0.4_i386.deb libgl1-mesa-glx_6.4.1-0.4_i386.deb to pool/main/m/mesa/libgl1-mesa-glx_6.4.1-0.4_i386.deb libgl1-mesa-swx11-dbg_6.4.1-0.4_i386.deb to pool/main/m/mesa/libgl1-mesa-swx11-dbg_6.4.1-0.4_i386.deb libgl1-mesa-swx11-dev_6.4.1-0.4_i386.deb to pool/main/m/mesa/libgl1-mesa-swx11-dev_6.4.1-0.4_i386.deb libgl1-mesa-swx11_6.4.1-0.4_i386.deb to pool/main/m/mesa/libgl1-mesa-swx11_6.4.1-0.4_i386.deb libglu1-mesa-dev_6.4.1-0.4_i386.deb to pool/main/m/mesa/libglu1-mesa-dev_6.4.1-0.4_i386.deb libglu1-mesa_6.4.1-0.4_i386.deb to pool/main/m/mesa/libglu1-mesa_6.4.1-0.4_i386.deb libosmesa6-dev_6.4.1-0.4_i386.deb to pool/main/m/mesa/libosmesa6-dev_6.4.1-0.4_i386.deb libosmesa6_6.4.1-0.4_i386.deb to pool/main/m/mesa/libosmesa6_6.4.1-0.4_i386.deb mesa-common-dev_6.4.1-0.4_all.deb to pool/main/m/mesa/mesa-common-dev_6.4.1-0.4_all.deb mesa-swx11-source_6.4.1-0.4_all.deb to pool/main/m/mesa/mesa-swx11-source_6.4.1-0.4_all.deb mesa_6.4.1-0.4.diff.gz to pool/main/m/mesa/mesa_6.4.1-0.4.diff.gz mesa_6.4.1-0.4.dsc to pool/main/m/mesa/mesa_6.4.1-0.4.dsc -- To UNSUBSCRIBE, email to [EMAIL
Accepted denyhosts 2.2-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 20 Mar 2006 13:30:34 +0100 Source: denyhosts Binary: denyhosts denyhosts-python2.3 denyhosts-common denyhosts-python2.4 Architecture: source all Version: 2.2-1 Distribution: unstable Urgency: low Maintainer: Marco Bertorello [EMAIL PROTECTED] Changed-By: Marco Bertorello [EMAIL PROTECTED] Description: denyhosts - an utility to help sys admins thwart ssh hackers denyhosts-common - an utility to help sys admins thwart ssh hackers denyhosts-python2.3 - an utility to help sys admins thwart ssh hackers denyhosts-python2.4 - an utility to help sys admins thwart ssh hackers Closes: 356731 Changes: denyhosts (2.2-1) unstable; urgency=low . * New upstream release * Changed description of denyhosts package from dummy package to dependency package (Closes: #356731) * Added default mail destination to [EMAIL PROTECTED] Files: 62dceb4e66bf11123e69d9d7c4b4c943 663 net optional denyhosts_2.2-1.dsc feba0e9a48dbf1fa9cbd2b5b8907f349 40972 net optional denyhosts_2.2.orig.tar.gz f5a8b52e45457c856d340faeb938f49e 5179 net optional denyhosts_2.2-1.diff.gz 518374e39c271706fa93dbfe9772d594 19210 net optional denyhosts-common_2.2-1_all.deb 86f8b40443be2e92d8ab13cbcaf5e78b 8318 net optional denyhosts_2.2-1_all.deb 5092f0a2ad232727e37eaaf54d4a56bf 29922 net optional denyhosts-python2.3_2.2-1_all.deb d6885449e3d160661c9f6a1da49cbdcb 29640 net optional denyhosts-python2.4_2.2-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEHrT9aGRzDfCV5eQRAlQBAJ91d9+ipPEO0SM8Kp0l6NJvuVy+wgCgjFCz YpMyN7lsvI3VyhRtOT4cxCo= =uLxO -END PGP SIGNATURE- Accepted: denyhosts-common_2.2-1_all.deb to pool/main/d/denyhosts/denyhosts-common_2.2-1_all.deb denyhosts-python2.3_2.2-1_all.deb to pool/main/d/denyhosts/denyhosts-python2.3_2.2-1_all.deb denyhosts-python2.4_2.2-1_all.deb to pool/main/d/denyhosts/denyhosts-python2.4_2.2-1_all.deb denyhosts_2.2-1.diff.gz to pool/main/d/denyhosts/denyhosts_2.2-1.diff.gz denyhosts_2.2-1.dsc to pool/main/d/denyhosts/denyhosts_2.2-1.dsc denyhosts_2.2-1_all.deb to pool/main/d/denyhosts/denyhosts_2.2-1_all.deb denyhosts_2.2.orig.tar.gz to pool/main/d/denyhosts/denyhosts_2.2.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libimage-librsvg-perl 0.07-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 20 Mar 2006 14:59:42 +0100 Source: libimage-librsvg-perl Binary: libimage-librsvg-perl Architecture: source i386 Version: 0.07-2 Distribution: unstable Urgency: low Maintainer: Debian Perl Group [EMAIL PROTECTED] Changed-By: Krzysztof Krzyzaniak (eloy) [EMAIL PROTECTED] Description: libimage-librsvg-perl - Perl binding for librsvg Changes: libimage-librsvg-perl (0.07-2) unstable; urgency=low . * Drop dependencies from experimental Files: 76638edd0d9d63bfbc1202a0f582234b 818 libdevel optional libimage-librsvg-perl_0.07-2.dsc bc50e119cc58bc008e3df0b071ad804f 1985 libdevel optional libimage-librsvg-perl_0.07-2.diff.gz 7d9db5efffa159d1e6b032f09ce306d3 107660 libdevel optional libimage-librsvg-perl_0.07-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEHrhX+NMfSd6w7DERAvChAKDFOupukOLHHsWPXtkdCmANdUR1wgCgrQCd 1w0rvKO3T91c+g3TcsEvdZE= =Cye2 -END PGP SIGNATURE- Accepted: libimage-librsvg-perl_0.07-2.diff.gz to pool/main/libi/libimage-librsvg-perl/libimage-librsvg-perl_0.07-2.diff.gz libimage-librsvg-perl_0.07-2.dsc to pool/main/libi/libimage-librsvg-perl/libimage-librsvg-perl_0.07-2.dsc libimage-librsvg-perl_0.07-2_i386.deb to pool/main/libi/libimage-librsvg-perl/libimage-librsvg-perl_0.07-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted pbuilder 0.150 (source all)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 20 Mar 2006 23:31:26 +0900
Source: pbuilder
Binary: pbuilder
Architecture: source all
Version: 0.150
Distribution: unstable
Urgency: low
Maintainer: Debian pbuilder maintenance team [EMAIL PROTECTED]
Changed-By: Junichi Uekawa [EMAIL PROTECTED]
Description:
pbuilder - personal package builder for Debian packages
Closes: 287477 341553
Changes:
pbuilder (0.150) unstable; urgency=low
.
* chown logfiles so that logfiles are not owned by root all the time
(Closes: #341553).
* Bug fix: [changes default behavior] Fix logfile name to have .log
appended if using --pkg-logfile, thanks to Christian Hammers
(Closes: #287477).
Note that the default is changed to '_{ARCH}.build' to match debuild.
Files:
7103b0982c9483b0e086e8d24c42c81a 673 devel extra pbuilder_0.150.dsc
8c69e88d3b12e1a18cac3a4c6e2fc49a 418755 devel extra pbuilder_0.150.tar.gz
708bd3e31c86391e2aa80cb4095e7b3a 75814 devel extra pbuilder_0.150_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFEHrzv2Dd9TugeVcERApNxAJ4xDedVueKDS2re7+m6tqoGwbhRhwCgi6po
iWov1tucyf7utHp333dgf1U=
=VRUu
-END PGP SIGNATURE-
Accepted:
pbuilder_0.150.dsc
to pool/main/p/pbuilder/pbuilder_0.150.dsc
pbuilder_0.150.tar.gz
to pool/main/p/pbuilder/pbuilder_0.150.tar.gz
pbuilder_0.150_all.deb
to pool/main/p/pbuilder/pbuilder_0.150_all.deb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libsigsegv 2.2-4 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 20 Mar 2006 14:50:21 +0100 Source: libsigsegv Binary: libsigsegv-dev Architecture: source i386 Version: 2.2-4 Distribution: unstable Urgency: low Maintainer: Peter Van Eynde [EMAIL PROTECTED] Changed-By: Peter Van Eynde [EMAIL PROTECTED] Description: libsigsegv-dev - Library for handling page faults in a portable way Changes: libsigsegv (2.2-4) unstable; urgency=low . * Changed section of libsigsegv-dev to libdevel as per override. * Included gcc-4 fix from Joerg Hoehle * Build again with gcc 4 by default Files: c6f58b0ef7d71c979c1044c7aee23b38 637 libdevel optional libsigsegv_2.2-4.dsc 051434d94fb3d54287c7fe932c911870 6321 libdevel optional libsigsegv_2.2-4.diff.gz 51db6acd55f88e55ac40ce74d6741086 18402 libdevel optional libsigsegv-dev_2.2-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEHr5C11ldN0tyliURAr86AJ0VbjwB1HFjwjyMSxx+nzbeu3PCJACfZ9I0 spsk4qSJXlH5rtfx4cOgbsM= =hJ6T -END PGP SIGNATURE- Accepted: libsigsegv-dev_2.2-4_i386.deb to pool/main/libs/libsigsegv/libsigsegv-dev_2.2-4_i386.deb libsigsegv_2.2-4.diff.gz to pool/main/libs/libsigsegv/libsigsegv_2.2-4.diff.gz libsigsegv_2.2-4.dsc to pool/main/libs/libsigsegv/libsigsegv_2.2-4.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted user-mode-linux 2.6.15-1um-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 17 Feb 2006 20:40:54 +0100 Source: user-mode-linux Binary: user-mode-linux Architecture: source i386 Version: 2.6.15-1um-1 Distribution: unstable Urgency: low Maintainer: Stefano Melchior [EMAIL PROTECTED] Changed-By: Stefano Melchior [EMAIL PROTECTED] Description: user-mode-linux - User-mode Linux (kernel) Changes: user-mode-linux (2.6.15-1um-1) unstable; urgency=low . * New upstream release Files: 98f85c11c278cb985605d4e70b548a4e 731 misc extra user-mode-linux_2.6.15-1um-1.dsc 409bbeca57a8fbc61c29de680ce4da2c 18177 misc extra user-mode-linux_2.6.15-1um.orig.tar.gz e411c1ef04d1c4fab6747603ce03792f 1249 misc extra user-mode-linux_2.6.15-1um-1.diff.gz f6e3e90fbc2e8e87ab3fb32e8d8b0a32 1904662 misc extra user-mode-linux_2.6.15-1um-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFEHszv8g+sC3uDV+URAlSCAJoCspgHS3adxpQsh6RzbmdAySZ2tgCfY83c f8AGaf5MwSN0NOyPQX0GFSk= =0msV -END PGP SIGNATURE- Accepted: user-mode-linux_2.6.15-1um-1.diff.gz to pool/main/u/user-mode-linux/user-mode-linux_2.6.15-1um-1.diff.gz user-mode-linux_2.6.15-1um-1.dsc to pool/main/u/user-mode-linux/user-mode-linux_2.6.15-1um-1.dsc user-mode-linux_2.6.15-1um-1_i386.deb to pool/main/u/user-mode-linux/user-mode-linux_2.6.15-1um-1_i386.deb user-mode-linux_2.6.15-1um.orig.tar.gz to pool/main/u/user-mode-linux/user-mode-linux_2.6.15-1um.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted zsh-beta 4.3.2-dev-1+20060317-1 (source sparc all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 19 Mar 2006 21:20:37 -0500 Source: zsh-beta Binary: zsh-beta-static zsh-beta-doc zsh-beta Architecture: source sparc all Version: 4.3.2-dev-1+20060317-1 Distribution: unstable Urgency: medium Maintainer: Clint Adams [EMAIL PROTECTED] Changed-By: Clint Adams [EMAIL PROTECTED] Description: zsh-beta - A shell with lots of features (dev tree) zsh-beta-doc - zsh beta documentation - info/HTML format Changes: zsh-beta (4.3.2-dev-1+20060317-1) unstable; urgency=medium . * Update to HEAD. Files: 07cba576cf86f1056248d03e29d1cfbc 747 shells optional zsh-beta_4.3.2-dev-1+20060317-1.dsc d7dbe9108e5c556d2fcc03676604ad7c 2292110 shells optional zsh-beta_4.3.2-dev-1+20060317.orig.tar.gz d98f64466de038fed38345e8081ce9ee 687933 shells optional zsh-beta_4.3.2-dev-1+20060317-1.diff.gz 53f96bdd200e7aa887bcc9e56187910f 690820 doc optional zsh-beta-doc_4.3.2-dev-1+20060317-1_all.deb 045f8c3807222a2cd0df624e9de53397 2176466 shells optional zsh-beta_4.3.2-dev-1+20060317-1_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Debian! iD8DBQFEHtq05m0u66uWM3ARAnUsAJ9ymxNXPeqcy3BGYSHsMnRphhuLQACffJFH iiTtjue6vx9GlILXdjUmOAA= =91lW -END PGP SIGNATURE- Accepted: zsh-beta-doc_4.3.2-dev-1+20060317-1_all.deb to pool/main/z/zsh-beta/zsh-beta-doc_4.3.2-dev-1+20060317-1_all.deb zsh-beta_4.3.2-dev-1+20060317-1.diff.gz to pool/main/z/zsh-beta/zsh-beta_4.3.2-dev-1+20060317-1.diff.gz zsh-beta_4.3.2-dev-1+20060317-1.dsc to pool/main/z/zsh-beta/zsh-beta_4.3.2-dev-1+20060317-1.dsc zsh-beta_4.3.2-dev-1+20060317-1_sparc.deb to pool/main/z/zsh-beta/zsh-beta_4.3.2-dev-1+20060317-1_sparc.deb zsh-beta_4.3.2-dev-1+20060317.orig.tar.gz to pool/main/z/zsh-beta/zsh-beta_4.3.2-dev-1+20060317.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fail2ban 0.6.1-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 18 Mar 2006 23:11:53 -0500 Source: fail2ban Binary: fail2ban Architecture: source all Version: 0.6.1-1 Distribution: unstable Urgency: low Maintainer: [EMAIL PROTECTED] Changed-By: Yaroslav Halchenko [EMAIL PROTECTED] Description: fail2ban - bans IPs that cause multiple authentication errors Closes: 357164 Changes: fail2ban (0.6.1-1) unstable; urgency=low . * New upstream release * In config file added fwchain to ease switching to another input chain (closes: #357164) Files: 5988baaa559bbb6b6896b45a26971bce 657 net optional fail2ban_0.6.1-1.dsc 92487a84975d1f5a5d161d467828139c 25972 net optional fail2ban_0.6.1.orig.tar.gz ce6400032a2e48b690c3b4d76dfc24da 15124 net optional fail2ban_0.6.1-1.diff.gz bfc279d3c962e759237eccbe1d41babf 48496 net optional fail2ban_0.6.1-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFEHs31Lz4Gnv7CP7IRAi7NAJ4l+JKgvY8UbFHUwIR+pvVZyuuI2gCg006h mXDD8YOburqHssseNTJ9F7Q= =g+/K -END PGP SIGNATURE- Accepted: fail2ban_0.6.1-1.diff.gz to pool/main/f/fail2ban/fail2ban_0.6.1-1.diff.gz fail2ban_0.6.1-1.dsc to pool/main/f/fail2ban/fail2ban_0.6.1-1.dsc fail2ban_0.6.1-1_all.deb to pool/main/f/fail2ban/fail2ban_0.6.1-1_all.deb fail2ban_0.6.1.orig.tar.gz to pool/main/f/fail2ban/fail2ban_0.6.1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted firebird2 1.5.3.4870-3 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 20 Mar 2006 11:55:19 +0200 Source: firebird2 Binary: firebird2-utils-classic libfbclient1 firebird2-super-server libfbembed1 firebird2-dev firebird2-server-common firebird2-utils-super firebird2-examples firebird2-classic-server Architecture: source i386 Version: 1.5.3.4870-3 Distribution: unstable Urgency: high Maintainer: Damyan Ivanov [EMAIL PROTECTED] Changed-By: Damyan Ivanov [EMAIL PROTECTED] Description: firebird2-classic-server - Firebird Classic Server - an RDBMS based on InterBase 6.0 code firebird2-dev - Development files for Firebird - an RDBMS based on InterBase 6.0 firebird2-examples - Examples for Firebird - an RDBMS based on InterBase 6.0 code firebird2-server-common - Common files for Firebird - an RDBMS based on InterBase 6.0 code firebird2-super-server - Firebird Super Server - an RDBMS based on InterBase 6.0 code firebird2-utils-classic - Utilities for Firebird - an RDBMS based on InterBase 6.0 code firebird2-utils-super - Utilities for Firebird - an RDBMS based on InterBase 6.0 code libfbclient1 - Firebird client library libfbembed1 - Firebird embedded client/server library Closes: 357580 Changes: firebird2 (1.5.3.4870-3) unstable; urgency=high . * Urgency high due to fixed remote security vulnerability . * [security] Plumb remote pre-authetication crash. Possible code execution as user firebird. [src/jrd/unix.cpp] Closes: #357580 Files: 219bd2b3c26157399a06222addc3dcf7 1161 misc optional firebird2_1.5.3.4870-3.dsc 923c903aa70996641f7706e499cec38a 504176 misc optional firebird2_1.5.3.4870-3.diff.gz 59d6a06c73d6449e0557b9192b39c716 126 misc optional firebird2-super-server_1.5.3.4870-3_i386.deb cd081822afe202e18395ee648fc517ec 380444 misc optional firebird2-classic-server_1.5.3.4870-3_i386.deb 0e3987deb975d3194167b8646ffe02c5 379952 libs optional libfbclient1_1.5.3.4870-3_i386.deb 10c9bdeda041841e68bccd2bbe5a43de 1060356 libs optional libfbembed1_1.5.3.4870-3_i386.deb c6100f181e5131a619591e7485a87429 579978 misc optional firebird2-server-common_1.5.3.4870-3_i386.deb 25837348b40824f03f5bd14f4c1c17f6 1064060 utils optional firebird2-utils-super_1.5.3.4870-3_i386.deb 3537b65636a8f3531d272e918d631c62 1037282 utils optional firebird2-utils-classic_1.5.3.4870-3_i386.deb 1ea89de40a3e045be2da6683961d0c52 271718 libdevel optional firebird2-dev_1.5.3.4870-3_i386.deb f18adcc4952ecbd8fbae315e92ccfcfe 342920 doc optional firebird2-examples_1.5.3.4870-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEHtEjpFNRmenyx0cRArTmAKCgHA8EXMGEOdpeSVMkNqyPYCkEkACg25k7 TlXinfqhO+GuBj/+IDuhARI= =tg6L -END PGP SIGNATURE- Accepted: firebird2-classic-server_1.5.3.4870-3_i386.deb to pool/main/f/firebird2/firebird2-classic-server_1.5.3.4870-3_i386.deb firebird2-dev_1.5.3.4870-3_i386.deb to pool/main/f/firebird2/firebird2-dev_1.5.3.4870-3_i386.deb firebird2-examples_1.5.3.4870-3_i386.deb to pool/main/f/firebird2/firebird2-examples_1.5.3.4870-3_i386.deb firebird2-server-common_1.5.3.4870-3_i386.deb to pool/main/f/firebird2/firebird2-server-common_1.5.3.4870-3_i386.deb firebird2-super-server_1.5.3.4870-3_i386.deb to pool/main/f/firebird2/firebird2-super-server_1.5.3.4870-3_i386.deb firebird2-utils-classic_1.5.3.4870-3_i386.deb to pool/main/f/firebird2/firebird2-utils-classic_1.5.3.4870-3_i386.deb firebird2-utils-super_1.5.3.4870-3_i386.deb to pool/main/f/firebird2/firebird2-utils-super_1.5.3.4870-3_i386.deb firebird2_1.5.3.4870-3.diff.gz to pool/main/f/firebird2/firebird2_1.5.3.4870-3.diff.gz firebird2_1.5.3.4870-3.dsc to pool/main/f/firebird2/firebird2_1.5.3.4870-3.dsc libfbclient1_1.5.3.4870-3_i386.deb to pool/main/f/firebird2/libfbclient1_1.5.3.4870-3_i386.deb libfbembed1_1.5.3.4870-3_i386.deb to pool/main/f/firebird2/libfbembed1_1.5.3.4870-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libcatalyst-modules-perl 0.11 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 9 Mar 2006 16:25:28 +0100 Source: libcatalyst-modules-perl Binary: libcatalyst-modules-perl Architecture: source all Version: 0.11 Distribution: unstable Urgency: low Maintainer: Debian Catalyst Maintainers [EMAIL PROTECTED] Changed-By: Krzysztof Krzyzaniak (eloy) [EMAIL PROTECTED] Description: libcatalyst-modules-perl - Modules for Catalyst Changes: libcatalyst-modules-perl (0.11) unstable; urgency=low . * Added Catalyst::Model::DBIC::Schema 0.08, updated dependencies * Catalyst::Plugin::Authentication::Store::DBIC updated to 0.05002 * Catalyst::Plugin::StackTrace updated to 0.03 * Catalyst::Plugin::Authentication updated to 0.07 Files: 358097ec1bb82a2c15537a39cf4e4cfb 1387 perl optional libcatalyst-modules-perl_0.11.dsc 4e8941aa75061449c8e5d7e56ce3949e 142129 perl optional libcatalyst-modules-perl_0.11.tar.gz e94d13f4fce3e7ff5302a9c93d335c8c 158970 perl optional libcatalyst-modules-perl_0.11_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEHs76+NMfSd6w7DERAgSVAKC/0NyHs2NItBHG8j0W65dXzV1sdACfZW71 wI5Uqv6cgdwKm9R1QIHze4U= =jwW6 -END PGP SIGNATURE- Accepted: libcatalyst-modules-perl_0.11.dsc to pool/main/libc/libcatalyst-modules-perl/libcatalyst-modules-perl_0.11.dsc libcatalyst-modules-perl_0.11.tar.gz to pool/main/libc/libcatalyst-modules-perl/libcatalyst-modules-perl_0.11.tar.gz libcatalyst-modules-perl_0.11_all.deb to pool/main/libc/libcatalyst-modules-perl/libcatalyst-modules-perl_0.11_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libcli 1.8.6-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 20 Mar 2006 16:47:49 + Source: libcli Binary: libcli-dev libcli1 Architecture: source i386 Version: 1.8.6-1 Distribution: unstable Urgency: low Maintainer: Jonathan McDowell [EMAIL PROTECTED] Changed-By: Jonathan McDowell [EMAIL PROTECTED] Description: libcli-dev - emulates a cisco style telnet command-line interface (dev files) libcli1- emulates a cisco style telnet command-line interface Changes: libcli (1.8.6-1) unstable; urgency=low . * New upstream release. Files: 97da581d945d84d721520574208f4e37 576 libs optional libcli_1.8.6-1.dsc fde7103a3771f550bfd366ee3ca1ef53 29473 libs optional libcli_1.8.6.orig.tar.gz c0e8c1fcdebb6093fe781086a4784db5 1922 libs optional libcli_1.8.6-1.diff.gz 819e17b6e0c85a07a4b83c78bc25c2a1 10726 libdevel optional libcli-dev_1.8.6-1_i386.deb 4d95e9ff058efe15bd5644436d9338b5 14754 libs optional libcli1_1.8.6-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEHtzZ8b1L5FtDA2cRAhqnAJwL4QhgJytuzSldlDB3pe+qCutkPgCfS6+1 ShkrYWrNE2vdriIjY671uFY= =ljH+ -END PGP SIGNATURE- Accepted: libcli-dev_1.8.6-1_i386.deb to pool/main/libc/libcli/libcli-dev_1.8.6-1_i386.deb libcli1_1.8.6-1_i386.deb to pool/main/libc/libcli/libcli1_1.8.6-1_i386.deb libcli_1.8.6-1.diff.gz to pool/main/libc/libcli/libcli_1.8.6-1.diff.gz libcli_1.8.6-1.dsc to pool/main/libc/libcli/libcli_1.8.6-1.dsc libcli_1.8.6.orig.tar.gz to pool/main/libc/libcli/libcli_1.8.6.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
