Debian Project Leader Election 2005
Hi, The nomination period is at an end, with six candidates standing forth to be counted. We are now in the campaigning period. The candidates are: o Matthew Garrett [EMAIL PROTECTED] o Andreas Schuldei [EMAIL PROTECTED] o Angus Lees [EMAIL PROTECTED] o Anthony Town [EMAIL PROTECTED] o Jonathan Walther [EMAIL PROTECTED] o Branden Robinson [EMAIL PROTECTED] The page at http://www.debian.org/vote/2005/ shall be updated soon. The platforms for these candidates shall be published as soon as they are available. (For the candidates who have not yet sent in their platforms: please do so as soon as possible). Time Line: Nomination period: February 7th, 2005 -- February 28th, 2005 Campaigning period: February 28th, 2005 -- March21st, 2005 Voting period: March 21st, 2005 -- April 11th, 2005 manoj -- Q: How do you stop an elephant from charging? A: Take away his credit cards. Debian Project Secretary [EMAIL PROTECTED] http://www.debian.org/vote/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C pgpaXKvIDtoBL.pgp Description: PGP signature
Re: Looking for someone to adopt pdftohtml
Hi, On Sun, Feb 27, 2005 at 10:09:15PM +0100, Frederic Peters wrote: So, if anyone uses or cares about pdftohtml, please step up, otherwise I will work out an arrangement with the maintainer of the depending package mentioned above. I use pdftohtml in a private project (actually only pdftohtml -xml for its XML output) and will adopt pdftohtml if nobody steps up. Please do, it definitely needs attentions. Thanks. -- Søren O. ,''`. : :' : GPG key id: 0x1EB2DE66`. `' GPG signed mail preferred. `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [OT] maildir (was Re: procmail and Large File Support)
Am 2005-02-27 18:19:45, schrieb sean finney: can't help but chime in here :) On Mon, Feb 28, 2005 at 09:22:30AM +1100, Brian May wrote: Not every situation warrants using maildir, it uses a large number of inodes, is slow to scan (yes, mbox isn't very good either), Mailbox is MUCH slower as Maildir, because it must be scaned entierly, but with maildir, most you can spead up the searches while scaning only the Headers. inefficient at storing large number of very small files (due to block size limitations of file system), and more complicated to transfer/move/share. What is complicate ? You need only the right programs... it does use a large number of inodes, but i've found that even on large filesystems with many users, there's not a real risk of starving the fs of inodes. ymmv. i'm not sure about the transferring/moving/sharing though. figuring the average email is about 13-15k, i believe an ext2/ext3 filesystem created with default options would fill up before running out of inodes. I have striped the Messages by Received: Headers and the most Messages are under 4 kByte now. I have a Mailarchive from around 130 Mailinglists with 5,3 Million Messages and my ext3 Filesystem has up to 18.000.000 Inodes and a blocksize of 1 kByte. I had never problems with it. Also I have only one Mailfolder per Mailinglist (linux-kernel has for example more then 190.000 Messges in it.) Of course, all of these factors depend on the file system used. I am confident somebody could point out a file-system that eliminates many of these disadvantages. recent versions of kernel/ext2/ext3 have built-in dirent hashing, which cuts heavily on the many-files penalty. another benefit of maildir is that when you modify a single message, you only need to modify the individual file, as opposed to the entire mailbox. in some of the sloppier imap servers (*cough* uw-imap *cough* *cough*), this can cause huge, grind-your-server-to-a-halt performance hits as deleting, or merely reading a new message necessates a huge amount of i/o. Right. I use courier and it works perfectly with Maildir... No blocking or high load, even if I open m linux-kernel Mailbox sean Greetings Michelle -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ Michelle Konzack Apt. 917 ICQ #328449886 50, rue de Soultz MSM LinuxMichi 0033/3/8845235667100 Strasbourg/France IRC #Debian (irc.icq.com) signature.pgp Description: Digital signature
Re: [OT] maildir
Am 2005-02-27 20:42:03, schrieb Ron Johnson: Ah. Maildir distinguishes new and already read by whether an email is in the new/ or cur/ folder. Doing a select all, and mark as read on a multi-GB mbox file sounds painful. This is, why I never will use mailbox Fortunatly I have converted all Eudora lite mailboxes to Maildir :-) Greetings Michelle -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ Michelle Konzack Apt. 917 ICQ #328449886 50, rue de Soultz MSM LinuxMichi 0033/3/8845235667100 Strasbourg/France IRC #Debian (irc.icq.com) signature.pgp Description: Digital signature
Re: [OT] maildir
Am 2005-02-28 04:34:41, schrieb Bernd Eckenfels: You mark a message as new by moving it to the new directory, and mark it as seen with the cur directory. Flags are normally added to the file name (by mutt for example). However some MUA-Servers need more info, which is then stored in extra files (imap is a pathological example for excessiv additional state) You forget, that they are NEW messages which you have not looked at and they are marked with O for Old-Unseen. These files are moved to /cur. Greetings Bernd Greetings Michelle -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ Michelle Konzack Apt. 917 ICQ #328449886 50, rue de Soultz MSM LinuxMichi 0033/3/8845235667100 Strasbourg/France IRC #Debian (irc.icq.com) signature.pgp Description: Digital signature
Re: [OT] maildir (was Re: procmail and Large File Support)
Am 2005-02-27 20:19:09, schrieb Ron Johnson: Sure, for those *20* GB mbox files. Who has 20 GByte mailboxes ? - It is realy braindamaged... Even on xfs, open a 20 GByte Mailbox will eat up all resources on the System Greetings Michelle -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ Michelle Konzack Apt. 917 ICQ #328449886 50, rue de Soultz MSM LinuxMichi 0033/3/8845235667100 Strasbourg/France IRC #Debian (irc.icq.com) signature.pgp Description: Digital signature
Re: [OT] maildir (was Re: procmail and Large File Support)
On Mon, 2005-02-28 at 09:25 +0100, Michelle Konzack wrote: Am 2005-02-27 20:19:09, schrieb Ron Johnson: Sure, for those *20* GB mbox files. Who has 20 GByte mailboxes ? - It is realy braindamaged... The same person with the 2GB mbox that started this thread, after s/he neglected it for a few more months. Even on xfs, open a 20 GByte Mailbox will eat up all resources on the System Guess you'd better use Maildir, then, huh? ;) -- - Ron Johnson, Jr. Jefferson, LA USA PGP Key ID 8834C06B I prefer encrypted mail. LUKE: Is Perl better than Python? YODA: No... no... no. Quicker, easier, more seductive. LUKE: But how will I know why Python is better than Perl? YODA: You will know. When your code you try to read six months from now. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [OT] maildir (was Re: procmail and Large File Support)
Am 2005-02-28 02:43:45, schrieb Ron Johnson: On Mon, 2005-02-28 at 09:25 +0100, Michelle Konzack wrote: Who has 20 GByte mailboxes ? - It is realy braindamaged... The same person with the 2GB mbox that started this thread, after s/he neglected it for a few more months. :-/ Oh yes, the SPAM/Virus folder. Then try to check it for false-positives... :-) Even on xfs, open a 20 GByte Mailbox will eat up all resources on the System Guess you'd better use Maildir, then, huh? ;) I have no problems with my huge Maildir :-) 'mutt' open the 187.000 Messages in around 47 seconds local (/home mounted via nfs v3) and via courier-imap-ssl in around 30 seconds. I know the avantages of Maildir. Greetings Michelle -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ Michelle Konzack Apt. 917 ICQ #328449886 50, rue de Soultz MSM LinuxMichi 0033/3/8845235667100 Strasbourg/France IRC #Debian (irc.icq.com) signature.pgp Description: Digital signature
Re: Automatic building of (parts of) the archive
On Sat, Feb 26, 2005 at 10:00:32PM +0100, Goswin von Brederlow wrote: Its buildd specific. If its queue is empty it contacts wanna-build and puts the new packages into the queue. I can't remeber the filename but that should be easy to see from the source. ~buildd/build/REDO Format: source package name_version suite If there's a file like that when buildd starts, it will call sbuild with those packages. It is safe to edit the file when sbuild is running, or to create it if buildd is running and the file isn't there (that's what buildd-mail does if you send a failed reply with retry, or a should-build reply with ok as the command) -- EARTH smog | bricks AIR -- mud -- FIRE soda water | tequila WATER -- with thanks to fortune -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#297218: ITP: radeontool -- utility to control ATI Radeon backlight functions on laptops
Hi Luigi! You wrote: You can find (and review) a preliminary package at http://people.debian.org/~luigi/radeontool Tahnks for packaging this! Any chance you could make it suid safe and executable bij users in the video group? And maybe you could add support for setting the compaq m300/m500 backlight luminosity (although I'm not sure if that is Compaq specific or genral for radeon), as implemented in the m300bl[1] program? [1] http://wwwbode.cs.tum.edu/~acher/m300/ -- 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: mplayer, the time has come
Sebastien NOEL wrote: I have some questions about your package: * Why the --disable-mencoder in debian/rules ? my original thought was : since LAME is not in Debian , then 'mencoder' will not be very useful but then some people pointed out that there are many interesting things that can be done with mencoder that do not need LAME so my next packaging will have 'mencoder' * Why the --disable-aa ? Ok caca is better than aa but it's not enabled either. I received some e-mail from upstream authors suggesting that AA was a nice trick but it may be removed from my packaging anyway it seems that '-vo sdl:aa ' will work as well * You build libavcodec and libavformat but that seems to me a waste of time. FFmpeg is already in main, why not only link mplayer with libavcodec.a (libavcodec-dev) and libavformat.a (libavformat-dev) ? choice of upstream : AFAICR a monolithic 'mplayer' improves performances offtopic btw: this is what Linus Torvalds decided with the kernel; methinks that a smaller kernel with a stable API for loading other minor services (ham radio, USB gadgets , etc) would be much better, but thats another (long) story. And, yes , I know that linux has modules, no, I dont think that they satisfy the above requisite: currently linux is too big and too complex for my tastes: it takes ages to download it, configure it and compile it. It forces distributions to: either offer a complete kernel that will satisfy all tastes, and that is huge; or have people recompile it (and this means, understand its myriad of options). /offtopic Qestion to all DD: Without decss, faad, lame xvid, mplayer insn't really mplayer. answer of 1 DD: on the other hand, without any kind of mplayer, Debian is at a loss and there are wonderful feats that 'mplayer' that do not need : decss, faad, lame xvid bye a. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: self-depending packages
Nicolas Boullis [EMAIL PROTECTED] wrote: Trying to upgrade a woody system to sarge, I experienced problems upgrading libgtk2.0-0, and discovered that this packages was self-depending. Afetr forcing the upgrade with dpkg -i --force-depends, everything went smoothly. So I filed a bug against libgtk2.0-0. Then I discovered that I could upgrade this package from woody to sarge with no trouble in a clean pbuilder chroot. So the problem might me more complex. However, from this bug report began a discussion with Loic Minier about self-dependencies and circular dependencies. What's the bug number? Regards, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer
Re: self-depending packages
On 20050227T214242+0100, Nicolas Boullis wrote: My understanding is that a self-depending package must be configured before it can be configured, which makes it unconfigurable, and hence uninstallable. And I think the same reasoning can be applied to circular dependencies. But Loic disagrees. Self-dependencies are harmless but ugly. Circular dependencies are sometimes (though very seldom) necessary (most of the time the same effect can be got from a -common package). Dpkg tries to break the cycle at the least problemous point, for example configuring a package with no postinst first. Should a bug be filed against those packages? Minor severity at most, IMHO. -- Antti-Juhani Kaijanaho, Debian developer http://kaijanaho.info/antti-juhani/blog/en/debian signature.asc Description: Digital signature
Re: Let's remove mips, mipsel, s390 ... [or have strict arch: control? ]
[Goswin von Brederlow] Which also avoids that packages will be unavailable on every new architecture debian introduces because the maintainer has to adjust the Architecture: line. I suppose it'd be nice to be able to use !foo in the Architecture: line for cases where something is known not to be supportable on a particular small subset of arches, through toolchain bugs or whatever. This smells like something dpkg/dpkg-source would have to support directly, probably by substituting the list of arches into the field at dpkg-source -b time. Even so, I wonder if any external tools would have a problem with the Architecture: line inside debian/control not being the same as in the .dsc.. signature.asc Description: Digital signature
Re: mplayer, the time has come
On Mon, Feb 28, 2005 at 10:19:37AM +0100, A Mennucc wrote:
Sebastien NOEL wrote:
I have some questions about your package:
* You build libavcodec and libavformat but that seems to me a waste of
time.
FFmpeg is already in main, why not only link mplayer with
libavcodec.a (libavcodec-dev) and libavformat.a (libavformat-dev) ?
choice of upstream : AFAICR a monolithic 'mplayer' improves performances
You've missed the point. If you use the libavcodec-dev and
libavformat-dev packages in Debian, you _get_ a monolithic
mplayer. Those packages only contain the static libraries,
which are linked in at compile time, since the packager has
chosen to not produce dynamic libraries for these two libraries
(for a different reason, I suspect, to do with the fluidity of
the libraries' APIs)
And even if libav{codec,format} had shared libraries in Debian,
the static versions in the -dev could be linked in, and I
understand that's the default way mplayer's configure script
accesses external libav{codec,format}.
If you use the ones in Debian, that's one less thing people
need to recompile to rebuild mplayer, like using external
libflac, libsdl etc, and it's easier to rebuild a local
mplayer with the latest lib{avcodec,format} versions, assuming
the packager of those is tracking CVS closely.
--
---
Paul TBBle Hampson, MCSE
8th year CompSci/Asian Studies student, ANU
The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361)
[EMAIL PROTECTED]
No survivors? Then where do the stories come from I wonder?
-- Capt. Jack Sparrow, Pirates of the Caribbean
This email is licensed to the recipient for non-commercial
use, duplication and distribution.
---
signature.asc
Description: Digital signature
Re: self-depending packages
On Mon, 28 Feb 2005 11:51:13 +0200, Antti-Juhani Kaijanaho [EMAIL PROTECTED] wrote: Dpkg tries to break the cycle at the least problemous point, for example configuring a package with no postinst first. Does it? The last time I was faced with that issue, the starting point chosen was random and unpredictable. Greetings Marc -- -- !! No courtesy copies, please !! - Marc Haber |Questions are the | Mailadresse im Header Mannheim, Germany | Beginning of Wisdom | http://www.zugschlus.de/ Nordisch by Nature | Lt. Worf, TNG Rightful Heir | Fon: *49 621 72739834
Re: self-depending packages
On Mon, Feb 28, 2005 at 11:58:14AM +0100, Marc Haber wrote: Does it? The last time I was faced with that issue, the starting point chosen was random and unpredictable. It does. (I've hacked the code.) /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Let's remove mips, mipsel, s390 ... [or have strict arch: control? ]µ
On Sun, Feb 27, 2005 at 11:08:14AM -0500, Rudy Godoy wrote: On 22/02/2005 at 10:11 Wouter Verhelst wrote... snip I agree that we should not continue to provide software for outdated hardware platforms just for the sake of it; but as it is, there are still people interested in m68k (some hobbyists, some embedded developers, some who just use their old trusty hardware as their home firewall, etc) and, I'm sure, other currently less-used hardware, so as long as a port doesn't continually stall the release (which none currently does; there are occasionally problems, but that happens in every major undertaking), I see no reason to drop any port. Regarding this issue I was thinking about it since I've faced in a situation where a package[0] I maintain does have high hardware requirements, which led me to think if it is really wise to have it with arch: any since probably in some arches it would not ever be installed/used, or even if case it will run really slow or even crash and the user will not enjoy the software as was intended by upstream, [...] I don't know much about buildd infrastructure[1], if such thing was proposed or commented before (didn't check archives), It has been brought up before a few times on the m68k mailinglists (and perhaps others too, but I don't follow those). The answer is pretty complex. In short: don't remove an architecture from your Architecture: line unless it * crashes, * is something that requires so much CPU time that using it on hardware of which a 100Mhz variant does not exist /will/ make the system trash and be generally unusable until you hit the reset button, or * does not compile I once wrote the long story in my blog; you can find it at http://www.livejournal.com/users/wouterverhelst/2742.html (it being a rant in reply to people shouting 'we should drop foo from Debian/m68k!', it doesn't entirely fit into this thread, but apart from that, it explains it). -- EARTH smog | bricks AIR -- mud -- FIRE soda water | tequila WATER -- with thanks to fortune -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Let's remove mips, mipsel, s390 ... [or have strict arch: control? ]
On Mon, Feb 28, 2005 at 04:42:54AM -0600, Peter Samuelson wrote: [Goswin von Brederlow] Which also avoids that packages will be unavailable on every new architecture debian introduces because the maintainer has to adjust the Architecture: line. I suppose it'd be nice to be able to use !foo in the Architecture: line for cases where something is known not to be supportable on a particular small subset of arches, through toolchain bugs or whatever. Congratulations, you've just found #112325 :-) -- EARTH smog | bricks AIR -- mud -- FIRE soda water | tequila WATER -- with thanks to fortune -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mplayer, the time has come
On Mon, 28 Feb 2005 10:19:37 +0100 A Mennucc [EMAIL PROTECTED] wrote: * Why the --disable-mencoder in debian/rules ? my original thought was : since LAME is not in Debian , then 'mencoder' will not be very useful but then some people pointed out that there are many interesting things that can be done with mencoder that do not need LAME so my next packaging will have 'mencoder' ok, thanks you * Why the --disable-aa ? Ok caca is better than aa but it's not enabled either. I received some e-mail from upstream authors suggesting that AA was a nice trick but it may be removed from my packaging anyway it seems that '-vo sdl:aa ' will work as well ok, but can you take a look at libcaca support please ? * You build libavcodec and libavformat but that seems to me a waste of time. FFmpeg is already in main, why not only link mplayer with libavcodec.a (libavcodec-dev) and libavformat.a (libavformat-dev) ? choice of upstream : AFAICR a monolithic 'mplayer' improves performances Paul Hampson was faster than me for this point. (but finally, i don't know if it is a good idea because ffmpeg was configured with '--disable-mmx') answer of 1 DD: on the other hand, without any kind of mplayer, Debian is at a loss [agree] Regards, Sebastien NOEL pgpt9Cfm3CvAJ.pgp Description: PGP signature
Re: dehs will stop
On Mon, 2005-02-28 at 03:32 +0100, Bluefuture wrote: snip I'm not a debian developer, so i could not post on dda mailing list. I had opened many thread over this months on debian-qa debian-devel about dehs issues. The only reply are: snip If you're not a developer and you want to post on d-d-a, you need to find a sponsor just like with packages. As long as the message is signed by someone in the keyring, it should go through. Cheers, Pasc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mplayer, the time has come
On Thu, 24 Feb 2005 19:40:35 -0500, you wrote: (according to /usr/share/doc/ffmpeg/patents.txt.gz) I hope that isn't a file with descriptions of patents--anyone who reads such a thing would risk increased patent liability. I'd rather not look for myself to find out, though. omfg. it's not possible. you're a fake, you don't really exist ? I put a pointer to you where you will be able to find more information and the only reaction is you are stupid, i'm not going to read this and i don't want to know more about that whow That said, are the patents supposedly affecting libfaad2 actively being enforced? Read The Fucking File I don't know how many times this can be said: non-us is *not a solution* to patents affecting the US, and never has been. and what now ? ok non-us is not the solution. but does it mean that there is no solution at all ? Sebastien NOEL signature.asc Description: Digital signature
Re: Bug#297233: ITP: wmansied -- An ANSI/ASCII editor.
Re: Nelson A. de Oliveira in [EMAIL PROTECTED] * Package name: wmansied Version : 0.4 Upstream Author : Walter Schreppers [EMAIL PROTECTED] * URL : http://www.win.ua.ac.be/~wschrep/ansied/ * License : GNU General Public Licence version 2 Description : An ANSI/ASCII editor. Re: Nelson A. de Oliveira in [EMAIL PROTECTED] * Package name: duhdraw Version : 2.7.7 Upstream Author : Walt Stoneburner [EMAIL PROTECTED] * URL : http://www.cs.helsinki.fi/u/penberg/duhdraw/ * License : GNU Copyleft Description : A ANSI Editor for Linux similar to TheDraw. What's the difference between the two? Do we really need both? Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: [OT] maildir
In article [EMAIL PROTECTED] you wrote: That's for a maildir. It won't help you for mbox folders. Which kind of was the point, as I understand it. Well, the comment that a file is immutable applies to maildir but not mbox (obviously - how would you add new mails?). Thats why I responded, there is not really a need to modify maildir files, and therefore you need no locking - which was the reason for the comment in the first place. Greetings Bernd -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mplayer, the time has come
A Mennucc wrote: and there are wonderful feats that 'mplayer' that do not need : decss, faad, lame xvid Why should Debian's mplayer be unable to support XVID? The MPEG4 codec from libavcodec will play any XVID just fine and libavcodec is already part of Debian in xine-lib and ffmpeg. Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mplayer, the time has come
On Mon, Feb 28, 2005 at 01:29:03PM +0100, Sebastien NOEL wrote: I don't know how many times this can be said: non-us is *not a solution* to patents affecting the US, and never has been. and what now ? ok non-us is not the solution. but does it mean that there is no solution at all ? Wait for sarge to become stable and discuss later, juste like xorg, amd64... Cédric De Wilde -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: self-depending packages
On Mon, Feb 28, 2005 at 12:06:06PM +0100, Steinar H. Gunderson wrote: On Mon, Feb 28, 2005 at 11:58:14AM +0100, Marc Haber wrote: Does it? The last time I was faced with that issue, the starting point chosen was random and unpredictable. It does. (I've hacked the code.) Unfortunately apt breaks the code. If you use dpkg directly it'll work. If you use apt it'll pick a random and unpredictable starting point. -- .''`. ** Debian GNU/Linux ** | Andrew Suffield : :' : http://www.debian.org/ | `. `' | `- -- | signature.asc Description: Digital signature
Re: Bug#297235: Bug#297233: ITP: wmansied -- An ANSI/ASCII editor.
Hi Christoph, On Mon, 28 Feb 2005, Christoph Berg wrote: * Package name: wmansied Version : 0.4 Upstream Author : Walter Schreppers [EMAIL PROTECTED] * URL : http://www.win.ua.ac.be/~wschrep/ansied/ * License : GNU General Public Licence version 2 Description : An ANSI/ASCII editor. * Package name: duhdraw Version : 2.7.7 Upstream Author : Walt Stoneburner [EMAIL PROTECTED] * URL : http://www.cs.helsinki.fi/u/penberg/duhdraw/ * License : GNU Copyleft Description : A ANSI Editor for Linux similar to TheDraw. What's the difference between the two? Do we really need both? I was using duhdraw, and since there was no package of it available, I have decided to package. Duh Draw is a text mode only editor. It uses ncurses. When searching for a graphical ANSI editor, I found wmansied. It uses QT libraries. Since some people don't like text mode utilities, I thought that would be good to package it too. If you think that only one is necessary, let me know, please. Thank you Nelson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#297218: ITP: radeontool -- utility to control ATI Radeon backlight functions on laptops
Il giorno lun, 28-02-2005 alle 10:15 +0100, Bas Zoetekouw ha scritto: Any chance you could make it suid safe and executable bij users in the video group? It would be difficult, radeontool need write access to /dev/mem, which on my 'sid' is crw-r- 1 root kmem so only root can change that. I could do a SETUID binary executable only by root and video group, but I'm not sure we could trust it. And, btw, you can do it yourself with dpkg-statoverride. And maybe you could add support for setting the compaq m300/m500 backlight luminosity (although I'm not sure if that is Compaq specific or genral for radeon), as implemented in the m300bl[1] program? [1] http://wwwbode.cs.tum.edu/~acher/m300/ This is not related, since it's an utility that control the backlight level via the on-board SuperIO chip, while radeontool uses the internal controls to switch the backlight on and off. Regards, -- Luigi Gangitano -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] GPG: 1024D/924C0C26: 12F8 9C03 89D3 DB4A 9972 C24A F19B A618 924C 0C26 signature.asc Description: Questa parte del messaggio =?ISO-8859-1?Q?=E8?= firmata
Re: Any reason why I'm not CCed by bugs of my packages?
On Fri, Feb 25, 2005 at 04:43:06PM -0600, John Hasler wrote: Andreas Tille writes: but got no mail notification about #296197 - just have seen it via web interface. Any idea what went wrong here. (If I'm not absolutely wrong this is not the first case for this package.) I have no idea what causes it but the same thing happens to me a couple of times a year. AOL/ I just make it a regular habit to scan my packages via the web interface, if only to remind myself about the wishlist bugs sitting on some of them. Nothing's perfect. -- Joel Aelwyn [EMAIL PROTECTED] ,''`. : :' : `. `' `- signature.asc Description: Digital signature
Re: Let's remove mips, mipsel, s390 ... [or have strict arch: control? ]
Peter Samuelson [EMAIL PROTECTED] writes: [Goswin von Brederlow] Which also avoids that packages will be unavailable on every new architecture debian introduces because the maintainer has to adjust the Architecture: line. I suppose it'd be nice to be able to use !foo in the Architecture: line for cases where something is known not to be supportable on a particular small subset of arches, through toolchain bugs or whatever. As a sidenote, wanna-build and buildd completly ignore the architecture line (apart from arch:all) and build packages anyway. Anything in the control file is purely informative to the buildd admin at this point. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [SoftwareSuspend-devel] 2.1-final for 2.6.8.1
Hi, SElinux is not supported by debian. the grsecurity situation isn't much different. For SELinux. the kernel has the code; the archive has the user-space tools. Believe me, I'm running SELinux on a couple of sarge boxes. Debian SELinux support is incomplete. You need a patched init, for example. rjc has a separate repository for these. You don't want a libselinux dependency from sysvinit for mainstream in Debian was the reasoning. So no way to run SElinux with 100% sarge. And you better take the rules from CVS, too. I don't see how this is any different to what I propose with swsusp2. I will package it. If you oppose to have this patch in stable, please discuss it on debian-devel. [Added CC: to debian-devel] Yes. I claim that it doesn't make any sense to have software-suspend2 patches in Debian stable, because of all the driver issues remaining with 2.6.8.1. I've been running swsusp2 for a long time now, and I'm sponsoring the hibernate script debian packages. Believe me, I have considered doing a patch package. It requires the USB modules to be unloaded before suspend. This implies you must not compile them statically into the kernel. Similar things apply to other drivers. I see no problem with this on Debian kernels, which are modular. The patch will not be included in Debian kernels, but will be used by the user to build his own kernel. Which will likely be not pure modular, but maybe just break swsusp. As soon as Pavel merges swsusp2 into 2.6 ... Which will not be in 2.6.8.1 But those who build their own kernel will either go for a more recent kernel, or will likely change some options and end up with a non-working suspend due to driver problems. and this will reflect back badly on both debian and swsusp2. Debian assumes that those who compile their own kernels know what they are doing. I don't see a point in trying to nanny them and prevent them from screwing up their systems. There are plenty of other ways to do so too. Heck, just let them get a recent kernel and be much better off! Put the kernel and the swsusp patch into volatile. Gruß, Erich Schubert -- erich@(mucl.de|debian.org) -- GPG Key ID: 4B3A135C(o_ To understand recursion you first need to understand recursion. //\ Wo befreundete Wege zusammenlaufen, da sieht die ganze Welt für V_/_ eine Stunde wie eine Heimat aus. --- Herrmann Hesse
Re: self-depending packages
On 20050228T164806+, Andrew Suffield wrote: Unfortunately apt breaks the code. If you use dpkg directly it'll work. If you use apt it'll pick a random and unpredictable starting point. Doesn't apt usually unpack all packages first and then configure them in one run, so that shouldn't matter? (Of course, essential packages and stuff like that break this but...) -- Antti-Juhani Kaijanaho, Debian developer http://kaijanaho.info/antti-juhani/blog/en/debian signature.asc Description: Digital signature
Re: Debian Sarge Support
Can you folks at Debian tell me whether we are supported in Sarge? Thanks, Hans Ben Pont wrote: I am preparing to install Debian Sarge on my computer and am debating whether to partition Reiser4 or Ext3. I know Lindows supports Reiser4, Lindows being Debian based, but do you know if Sarge explicitly supports your format? Since Debian is a pain in the ass to install in the first place, I'd really like to get things right the first time and not have to repartition / reinstall if I discover Reiser4 isn't supported by Debian. Yes, I have tried getting answers from the Debian folks directly, but have gotten mixed messages. Any info from your side would be greatly appreciated. Thanks. Ben __ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo debi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: self-depending packages
On Mon, Feb 28, 2005, Frank Küster wrote: What's the bug number? http://bugs.debian.org/296175 -- Loïc Minier [EMAIL PROTECTED] Neutral President: I have no strong feelings one way or the other. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: splitting a source package into 2 source packages
El Sábado 26 Febrero 2005 21:47, sean finney escribió: istr the same thing, and was thinking that this might be the case. since i don't suppose the ftp-master illuminati are going to come out of hiding just to answer this question, i guess i'll upload, find out, and report back :/ sean Please, do it (report back). I'm interested in the same question. César
Re: Debian Sarge Support
On Mon, Feb 28, 2005 at 01:47:18PM -0800, Hans Reiser wrote: Can you folks at Debian tell me whether we are supported in Sarge? Thanks, Hans Last time I installed sarge (ages ago, about November last year) I did make some ReiserFS partitions and they ended up being 3.6 not 4. Things could have changed of course, but I don't really expect so. Hope this helps Floris Ben Pont wrote: I am preparing to install Debian Sarge on my computer and am debating whether to partition Reiser4 or Ext3. I know Lindows supports Reiser4, Lindows being Debian based, but do you know if Sarge explicitly supports your format? Since Debian is a pain in the ass to install in the first place, I'd really like to get things right the first time and not have to repartition / reinstall if I discover Reiser4 isn't supported by Debian. Yes, I have tried getting answers from the Debian folks directly, but have gotten mixed messages. Any info from your side would be greatly appreciated. Thanks. Ben __ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo debi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Debian GNU/Linux -- The power of freedom www.debian.org | www.gnu.org | www.kernel.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian Sarge Support
Le lundi 28 fvrier 2005 13:47 -0800, Hans Reiser a crit : Can you folks at Debian tell me whether we are supported in Sarge? As far as I know, there is no reiser4 support in the Debian stock kernel. -- .''`. Josselin Mouette/\./\ : :' : [EMAIL PROTECTED] `. `'[EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom signature.asc Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=
Re: Debian Sarge Support
As far as I can see - Debian Sarge / Debian testing / Debian GNU/Linux 3.1 - now has support both for Reiserfs [?? 3.6.19??] and Reiser4 [?? 1.0.3 ??]. There is a kernel patch against version 2.6.8 for Reiser4. Hope this helps - everyone feel free to correct me if I'm wrong :) Andy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: self-depending packages
On Mon, Feb 28, 2005 at 09:49:41PM +0200, Antti-Juhani Kaijanaho wrote: On 20050228T164806+, Andrew Suffield wrote: Unfortunately apt breaks the code. If you use dpkg directly it'll work. If you use apt it'll pick a random and unpredictable starting point. Doesn't apt usually unpack all packages first and then configure them in one run, so that shouldn't matter? dpkg does the same thing -- .''`. ** Debian GNU/Linux ** | Andrew Suffield : :' : http://www.debian.org/ | `. `' | `- -- | signature.asc Description: Digital signature
Re: Debian Project Leader Election 2005
Hi, * Debian Project Secretary [EMAIL PROTECTED] [2005-02-28 21:36]: The nomination period is at an end, with six candidates standing forth to be counted. We are now in the campaigning period. The candidates are: o Matthew Garrett [EMAIL PROTECTED] ^^ Is the email address wrong? There is no entry for http://qa.debian.org/[EMAIL PROTECTED] Regards Nico -- Nico Golde - [EMAIL PROTECTED] | GPG: 1024D/73647CFF http://www.ngolde.de | mutt-ng.berlios.de | grml.org VIM has two modes - the one in which it beeps and the one in which it doesn't -- encrypted mail preferred pgpVN7mx1bRQw.pgp Description: PGP signature
Re: Debian Project Leader Election 2005
On 10214 March 1977, Nico Golde wrote: o Matthew Garrett [EMAIL PROTECTED] ^^ Is the email address wrong? There is no entry for http://qa.debian.org/[EMAIL PROTECTED] No, as you are free to use whatever email as a maintainer. Look at db.d.o if you want to look for logins. -- bye Joerg _DeadBull_ ohne speicher, tastatur, mouse, pladde, monitor, also nur die Hardware... pgpRbHBdnh6Ui.pgp Description: PGP signature
Re: Bug#297233: ITP: wmansied -- An ANSI/ASCII editor.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nelson A. de Oliveira [EMAIL PROTECTED] writes: WMAnsiEd is an ANSI editor with functions like line drawing, ellipse, box, etc., written in Qt. All IBM ANSI and ASCII characters are ANSI is pretty meaningless as a standard, since ANSI standardised many different things. Perhaps you mean it implements ISO-6429 (ECMA-48) SGR control sequences, or maybe something entirely different? Either way, it would help if you were much more specific. (This applies equally to the other ITP.) Regards, Roger - -- Roger Leigh Printing on GNU/Linux? http://gimp-print.sourceforge.net/ Debian GNU/Linuxhttp://www.debian.org/ GPG Public Key: 0x25BFB848. Please sign and encrypt your mail. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.8 http://mailcrypt.sourceforge.net/ iD8DBQFCI4z3VcFcaSW/uEgRArPXAJwJbg6I4N13wcQs6z1tlH86YfWcFACfaCDa MMcd8DXdCXZgoI9b1ZlUCf0= =I6+Y -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Why are you guys using user space utilities not written by us that seem to not work? Could you change who is the debian maintainer for us?
I can volunteer [EMAIL PROTECTED], the guy who writes our utilities (which work), for the task. This is the second time that Ed has broken Reiserfs support in Debian, and each time it breaks Namesys looks bad, because users have no idea it is not us who broke our code. Thanks to Cliff we now have an idea where some mysterious reports of things breaking have their source. Who is jltallon? adv-solutions.net has no information on its web page explaining about who they are. Is Debian intending to code fork ReiserFS? Are you guys that nuts? Vitaly, please pursue this matter with Debian. Hans ---BeginMessage--- Well, I have some new info this morning. We attributed the errors to hard drive problems to start with as well, but the errors were too consistent and appeared on too many machines simultaneously. Over the weekend we have collected many reports of people being unable to install using reiser3, but succeeding with reiser4. This eliminates both bad CD burns and hard drive errors, so I went looking for another cause. Recently we included qtparted which pulls in a Debian package called ``progsreiserfs'' instead of ``reiserfsprogs.'' We are investigating this as the cause of the problems right now. We are seeing a behavior with the ``progsreiserfs'' tools that one install will generate errors, another will succeed but take a long time, and a third will succeed in the normal amount of time. Same machine, same hard disk, same CDROM. I'm including Debian's description of these packages below. Package: reiserfsprogs Status: install ok installed Priority: optional Section: admin Installed-Size: 1072 Maintainer: Ed Boraas [EMAIL PROTECTED] Architecture: i386 Version: 1:3.6.19-1 Depends: libc6 (= 2.3.2.ds1-4), libuuid1 Description: User-level tools for ReiserFS filesystems This package contains utilities to create, check, resize, and debug ReiserFS filesystems. . NOTE: Releases of Linux prior to 2.4.1 do not support ReiserFS on their own. Thus, these tools will only be useful with Linux 2.4.1 or later, or if your kernel has been built with the ReiserFS patch applied. This patch can be found in the appropriate kernel-patch-version-reiserfs packages. . Homepage: http://www.namesys.com/ zz:~# apt-cache show progsreiserfs Package: progsreiserfs Version: 0.3.0.4-4 Architecture: i386 Priority: extra Section: admin Maintainer: Jose Luis Tallon [EMAIL PROTECTED] Depends: libc6 (= 2.3.2.ds1-4), libreiserfs0.3-0 (= 0.3.0), libuuid1 Conflicts: reiserfsprogs Provides: reiserfsprogs Size: 34236 Installed-Size: 156 MD5sum: 57feec6fc2b48d125e755e0a2ab31bb0 Description: Tools for manipulating ReiserFS filesystems progsreiserfs is a collection of tools for manipulating ReiserFS filesystems. There are tools to create, check, resize, tune and copy ReiserFS filesystems. . These tools differ from the standard Namesys ReiserFS tools in that they use libreiserfs to do their work. Filename: pool/p/progsreiserfs/progsreiserfs_0.3.0.4-4_i386.deb Hans Reiser wrote: Clifford Beshers wrote: We recently rewrote our installer to use a custom program that can stream a compressed iso9660 image file and unpack it to disk. Previously it used rsync. Everything seemed to be fine, but when we started running it on many machines, we started encountering errors like the ones shown below, the output of dmesg. At first I suspected it might be that the kernel hadn't re-read the partition table, but on several installs we did not create or modify that table. Anyone have any guesses as to what is going wrong? Again, this is reiser3. hda1: rw=0, want=116654088, limit=50058477 attempt to access beyond end of device hda1: rw=0, want=116916232, limit=50058477 attempt to access beyond end of device hda1: rw=0, want=117178376, limit=50058477 ReiserFS: hda1: warning: sh-2029: reiserfs read_bitmaps: bitmap block (#6258688) reading failed ReiserFS: hda1: warning: jmacd-8: reiserfs_fill_super: unable to read bitmap The above look like hardware errors from the disk drive. There have been rsync related emails on this list, but let's start with a working disk drive, ok? It is remotely possible that the above could be a failure to reboot after using fsync NTFS volume version 1.2. NTFS-fs warning (device hda2): load_system_files(): Volume is dirty. Will not be able to remount read-write. Run chkdsk and mount in Windows. ReiserFS: hda1: found reiserfs format 3.6 with standard journal ReiserFS: hda1: using ordered data mode ReiserFS: hda1: journal params: device hda1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 ReiserFS: hda1: checking transaction log (hda1) ReiserFS: hda1: Using r5 hash to sort names ReiserFS: hda1: warning: Created .reiserfs_priv on hda1 - reserved for xattr storage. Adding 1049592k swap on /mnt/install/boot/linux-swap.swp. Priority:-1 extents:215 ReiserFS: warning: is_leaf: item location seems wrong (second one): *3.6* [7 32 0x1
Re: Debian Project Leader Election 2005
Hello Joerg, * Joerg Jaspert [EMAIL PROTECTED] [2005-02-28 21:54]: On 10214 March 1977, Nico Golde wrote: o Matthew Garrett [EMAIL PROTECTED] ^^ Is the email address wrong? There is no entry for http://qa.debian.org/[EMAIL PROTECTED] No, as you are free to use whatever email as a maintainer. Look at db.d.o if you want to look for logins. Ok thanks. I thought that would be his maintainer email address. Regards Nico -- Nico Golde - [EMAIL PROTECTED] | GPG: 1024D/73647CFF http://www.ngolde.de | mutt-ng.berlios.de | grml.org VIM has two modes - the one in which it beeps and the one in which it doesn't -- encrypted mail preferred pgpUsMnezWAJU.pgp Description: PGP signature
Re: Why are you guys using user space utilities not written by us that seem to not work? Could you change who is the debian maintainer for us?
Hans, On Mon, Feb 28, 2005 at 03:22:17PM -0800, Hans Reiser wrote: This is the second time that Ed has broken Reiserfs support in Debian, and each time it breaks Namesys looks bad, because users have no idea it is not us who broke our code. Thanks to Cliff we now have an idea where some mysterious reports of things breaking have their source. I can't see from the message below that this breakage has anything to do with Ed's work. The progsreiserfs package has a separate maintainer; it also has a release-critical bug open on it due to these known (to us) problems, and will not be included in the upcoming sarge release. It also has not been available in the Debian testing suite for some time, nor is it included with the Debian installer: anyone who pulls packages from Debian unstable without looking at any of these issues does so at their own risk. Incidentally, aside from having had its reiserfs resize support pulled because it depended on the buggy progsreiserfs implementation, qtparted has itself also been dropped from testing due to an unrelated RC bug. Thanks, -- Steve Langasek postmodern programmer Date: Mon, 28 Feb 2005 12:12:38 -0800 From: Clifford Beshers [EMAIL PROTECTED] To: Hans Reiser [EMAIL PROTECTED] Cc: reiserfs-list@namesys.com Subject: Re: Install errors, reiser3 messages X-Lindows-Footer: yes X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on thebsh.namesys.com X-Spam-DCC: : X-Spam-Status: No, hits=0.0 required=2.0 tests=none autolearn=no version=2.60 Well, I have some new info this morning. We attributed the errors to hard drive problems to start with as well, but the errors were too consistent and appeared on too many machines simultaneously. Over the weekend we have collected many reports of people being unable to install using reiser3, but succeeding with reiser4. This eliminates both bad CD burns and hard drive errors, so I went looking for another cause. Recently we included qtparted which pulls in a Debian package called ``progsreiserfs'' instead of ``reiserfsprogs.'' We are investigating this as the cause of the problems right now. We are seeing a behavior with the ``progsreiserfs'' tools that one install will generate errors, another will succeed but take a long time, and a third will succeed in the normal amount of time. Same machine, same hard disk, same CDROM. I'm including Debian's description of these packages below. Package: reiserfsprogs Status: install ok installed Priority: optional Section: admin Installed-Size: 1072 Maintainer: Ed Boraas [EMAIL PROTECTED] Architecture: i386 Version: 1:3.6.19-1 Depends: libc6 (= 2.3.2.ds1-4), libuuid1 Description: User-level tools for ReiserFS filesystems This package contains utilities to create, check, resize, and debug ReiserFS filesystems. . NOTE: Releases of Linux prior to 2.4.1 do not support ReiserFS on their own. Thus, these tools will only be useful with Linux 2.4.1 or later, or if your kernel has been built with the ReiserFS patch applied. This patch can be found in the appropriate kernel-patch-version-reiserfs packages. . Homepage: http://www.namesys.com/ zz:~# apt-cache show progsreiserfs Package: progsreiserfs Version: 0.3.0.4-4 Architecture: i386 Priority: extra Section: admin Maintainer: Jose Luis Tallon [EMAIL PROTECTED] Depends: libc6 (= 2.3.2.ds1-4), libreiserfs0.3-0 (= 0.3.0), libuuid1 Conflicts: reiserfsprogs Provides: reiserfsprogs Size: 34236 Installed-Size: 156 MD5sum: 57feec6fc2b48d125e755e0a2ab31bb0 Description: Tools for manipulating ReiserFS filesystems progsreiserfs is a collection of tools for manipulating ReiserFS filesystems. There are tools to create, check, resize, tune and copy ReiserFS filesystems. . These tools differ from the standard Namesys ReiserFS tools in that they use libreiserfs to do their work. Filename: pool/p/progsreiserfs/progsreiserfs_0.3.0.4-4_i386.deb Hans Reiser wrote: Clifford Beshers wrote: We recently rewrote our installer to use a custom program that can stream a compressed iso9660 image file and unpack it to disk. Previously it used rsync. Everything seemed to be fine, but when we started running it on many machines, we started encountering errors like the ones shown below, the output of dmesg. At first I suspected it might be that the kernel hadn't re-read the partition table, but on several installs we did not create or modify that table. Anyone have any guesses as to what is going wrong? Again, this is reiser3. hda1: rw=0, want=116654088, limit=50058477 attempt to access beyond end of device hda1: rw=0, want=116916232, limit=50058477 attempt to access beyond end of device hda1: rw=0, want=117178376, limit=50058477 ReiserFS: hda1: warning: sh-2029: reiserfs read_bitmaps: bitmap block (#6258688) reading failed ReiserFS: hda1: warning: jmacd-8: reiserfs_fill_super: unable to read bitmap
Re: [OT] maildir (was Re: procmail and Large File Support)
On Monday 28 February 2005 01:51, Ron Johnson wrote: On Sun, 2005-02-27 at 18:19 -0500, sean finney wrote: [snip] figuring the average email is about 13-15k, i believe an ext2/ext3 That seems awfully huge. In my (Maildir) archive of d-u, the average size is 4,959 bytes. Of course, there are no html mails. Though, even in my Evolution list archive, where there are many more html-mails, the average size is only 6,097. I ran statistics on maildirs of the university (of arts) mailserver I administer: ~90k per mail. Regards, David -- - hallo... wie gehts heute? - *hust* gut *rotz* *keuch* - gott sei dank kommunizieren wir ber ein septisches medium ;) -- Matthias Leeb, Uni f. angewandte Kunst, 2005-02-15
Re: Why are you guys using user space utilities not written by us that seem to not work? Could you change who is the debian maintainer for us?
Hans Reiser wrote: I can volunteer [EMAIL PROTECTED], the guy who writes our utilities (which work), for the task. This is the second time that Ed has broken Reiserfs support in Debian, and each time it breaks Namesys looks bad, because users have no idea it is not us who broke our code. Thanks to Cliff we now have an idea where some mysterious reports of things breaking have their source. Who is jltallon? adv-solutions.net has no information on its web page explaining about who they are. Is Debian intending to code fork ReiserFS? Are you guys that nuts? Vitaly, please pursue this matter with Debian. Hi Hans, I think we met in Max's once after a BALUG meeting. Anyway, let me try to clear up some misconceptions you seem to have: - progreiserfs is not the default reiserfs toolset used by Debian. See thread starting at http://lists.debian.org/debian-boot/2004/09/msg01142.html. - Since progreiserfs is known to cause data loss, it has not even been available in Debian testing for a long time, and is unlikely to be part of a Debian release. See http://bugs.debian.org/244169. - progsreiserfs was not developed by Debian, so accusing us of forking reiserfs is a fairly strange thing to say. It was written by Yury Umanets [EMAIL PROTECTED]. See http://reiserfs.linux.kiev.ua/. - Ed Boraas has, AFAIK, nothing to do with progsreiserfs. He maintains reiserfsprogs, from namesys. See the mail you forwarded to this list. - Jose Luis Tallon is a prospective new Debian developer who, with the help of Debian developer Roberto Lumbreras, has been (trying to) maintain progsreiserfs after the developer who previously added it to the Debian distribution in 2002 resigned. See http://bugs.debian.org/249837. All of the above information can be obtained publically online; indeed that's where I obtained it, with only a few minutes searching. Maybe doing a bit more research before posting messages that are so likely to result in flames would be a good idea in the future. This message contains information which may be confidential and privileged. Unless you are the addressee (or authorized to receive for the addressee), you may not use, copy or disclose to anyone the message or any information contained in the message. If you have received the message in error, please advise the sender and delete the message. Thank you. Please do not post mails to the debian mailing lists with signature blocks that are so obviously unenforceable. All mails posted to Debian mailing lists, with the exception of debian-private, are made available publically without exception. Thanks. -- see shy jo signature.asc Description: Digital signature
Re: [OT] maildir (was Re: procmail and Large File Support)
On Mon, 2005-02-28 at 22:55 +0100, David Schmitt wrote: On Monday 28 February 2005 01:51, Ron Johnson wrote: On Sun, 2005-02-27 at 18:19 -0500, sean finney wrote: [snip] figuring the average email is about 13-15k, i believe an ext2/ext3 That seems awfully huge. In my (Maildir) archive of d-u, the average size is 4,959 bytes. Of course, there are no html mails. Though, even in my Evolution list archive, where there are many more html-mails, the average size is only 6,097. I ran statistics on maildirs of the university (of arts) mailserver I administer: ~90k per mail. Art majors passing around scanned pictures of croissants? ;) -- - Ron Johnson, Jr. Jefferson, LA USA PGP Key ID 8834C06B I prefer encrypted mail. When asked to name the chief qualification a politician should have. It's the ability to foretell what will happen tomorrow, next month, and next year --- and to explain afterward why it didn't happen. Sir Winston Churchill -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [OT] maildir
Michelle == Michelle Konzack [EMAIL PROTECTED] writes: inefficient at storing large number of very small files (due to block size limitations of file system), and more complicated to transfer/move/share. Michelle What is complicate ? You need only the right Michelle programs... Perhaps I should elaborate on this point. If I want to allow people to download a mbox folder (consider mailing list archive), all I do is put in under a HTTP accessible directory. People only need to download one file, and IIRC, there is a standard (or defacto standard) MIME type for mbox files. I believe a browser will automatically start mutt. In fact, I believe this will work even if the file is gzipped. Now take Maildirs... Sure, I could tar.gz the entire directory, but this means the recipient must manually untar it before accessing it. I don't believe there is a standard MIME type to distinguish these files either. As far as your browser is concerned, it isn't Maildir format, it is gzipped tar format. Also, all mailing list software I have seen so far exclusively uses mbox files. Sure, these are implementation issues that could be solved, but currently mbox wins. -- Brian May [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Why are you guys using user space utilities not written by us that seem to not work? Could you change who is the debian maintainer for us?
Hans Reiser wrote: I can volunteer [EMAIL PROTECTED], the guy who writes our utilities (which work), for the task. Sorry, but this is the first thing i hear anything about this :-? This is the second time that Ed has broken Reiserfs support in Debian, and each time it breaks Namesys looks bad, because users have no idea it is not us who broke our code. Thanks to Cliff we now have an idea where some mysterious reports of things breaking have their source. Progsreiserfs are *not* in testing and have Release Critical bugs for a reason, and that is to avoid giving the impression that they are stable packages. In fact, they are even categorized under extra instead of optional, because they are lower priority. Who is jltallon? adv-solutions.net has no information on its web page explaining about who they are. Well, José Luis Tallón (that's me). Currently finishing the NM process at Debian and maintainer of some packages. Adv-solutions.net has no web page. It is one of my personal domains, with no commercial interests attached. Is Debian intending to code fork ReiserFS? Are you guys that nuts? Vitaly, please pursue this matter with Debian. Well, i would sincerely appreciate that somebody explained the full thing to me. I have been intending to upgrade progsreiserfs for quite some time now, but lacked the necessary time. And since they are not in testing, i really needed not worry. From what i read below, there is somebody actually using QtParted for their installer. This means i now have some incentive to devote work to this... i will try to have it upgraded as soon as possible, but i can't guarantee anything. I will try to keep you posted. Any additional feedback would be appreciated. Hans Subject: Re: Install errors, reiser3 messages From: Clifford Beshers [EMAIL PROTECTED] Date: Mon, 28 Feb 2005 12:12:38 -0800 To: Hans Reiser [EMAIL PROTECTED] To: Hans Reiser [EMAIL PROTECTED] CC: reiserfs-list@namesys.com Return-Path: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Received: (qmail 14707 invoked by uid 85); 28 Feb 2005 20:12:56 - Received: from [EMAIL PROTECTED] by thebsh.namesys.com by uid 82 with qmail-scanner-1.15 (spamassassin: 2.43-cvs. Clear:SA:0(0.0/2.0 tests=none autolearn=no version=2.60):. Processed in 8.523853 secs); 28 Feb 2005 20:12:56 - Received: from mail.linspire.com (HELO mail.lindows.com) (130.94.123.204) by thebsh.namesys.com with SMTP; 28 Feb 2005 20:12:47 - Received: by mail.lindows.com (Postfix, from userid 8) id 17AEC15C6D20; Mon, 28 Feb 2005 12:14:02 -0800 (PST) Received: from linspireinc.com (unknown [207.67.194.2])by mail.lindows.com (Postfix) with ESMTPid CC40A15C6CF3; Mon, 28 Feb 2005 12:14:01 -0800 (PST) Message-ID: [EMAIL PROTECTED] User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20041006 Debian/1.6-5.1.0.50.linspire0.38 X-Accept-Language: en-us, en MIME-Version: 1.0 References: [EMAIL PROTECTED] [EMAIL PROTECTED] In-Reply-To: [EMAIL PROTECTED] Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Lindows-Footer: yes X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on thebsh.namesys.com X-Spam-DCC: : X-Spam-Status: No, hits=0.0 required=2.0 tests=none autolearn=no version=2.60 Well, I have some new info this morning. We attributed the errors to hard drive problems to start with as well, but the errors were too consistent and appeared on too many machines simultaneously. Over the weekend we have collected many reports of people being unable to install using reiser3, but succeeding with reiser4. This eliminates both bad CD burns and hard drive errors, so I went looking for another cause. Recently we included qtparted which pulls in a Debian package called ``progsreiserfs'' instead of ``reiserfsprogs.'' We are investigating this as the cause of the problems right now. We are seeing a behavior with the ``progsreiserfs'' tools that one install will generate errors, another will succeed but take a long time, and a third will succeed in the normal amount of time. Same machine, same hard disk, same CDROM. I'm including Debian's description of these packages below. Package: reiserfsprogs Status: install ok installed Priority: optional Section: admin Installed-Size: 1072 Maintainer: Ed Boraas [EMAIL PROTECTED] Architecture: i386 Version: 1:3.6.19-1 Depends: libc6 (= 2.3.2.ds1-4), libuuid1 Description: User-level tools for ReiserFS filesystems This package contains utilities to create, check, resize, and debug ReiserFS filesystems. . NOTE: Releases of Linux prior to 2.4.1 do not support ReiserFS on their own. Thus, these tools will only be useful with Linux 2.4.1 or later, or if your kernel has been built with the ReiserFS patch applied. This patch can be found in the appropriate kernel-patch-version-reiserfs packages. . Homepage: http://www.namesys.com/ zz:~# apt-cache show
Re: Debian Sarge Support
On Mon, Feb 28, 2005 at 01:47:18PM -0800, Hans Reiser wrote: Can you folks at Debian tell me whether we are supported in Sarge? The stock kernels support Reiser3, but not Reiser4. Reiser4 support packages are available, however. -- EARTH smog | bricks AIR -- mud -- FIRE soda water | tequila WATER -- with thanks to fortune -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Let's remove mips, mipsel, s390 ... [or have strict arch: control? ]
On Mon, Feb 28, 2005 at 08:18:56PM +0100, Goswin von Brederlow wrote: Peter Samuelson [EMAIL PROTECTED] writes: [Goswin von Brederlow] Which also avoids that packages will be unavailable on every new architecture debian introduces because the maintainer has to adjust the Architecture: line. I suppose it'd be nice to be able to use !foo in the Architecture: line for cases where something is known not to be supportable on a particular small subset of arches, through toolchain bugs or whatever. As a sidenote, wanna-build and buildd completly ignore the architecture line (apart from arch:all) and build packages anyway. Well, somewhat :-) they /attempt/ the build. sbuild will detect that it is not actually a package for this architecture, and will break it off right when the source package is extracted. Anything in the control file is purely informative to the buildd admin at this point. No, sbuild does check more things. -- EARTH smog | bricks AIR -- mud -- FIRE soda water | tequila WATER -- with thanks to fortune -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: splitting a source package into 2 source packages
On Sat, Feb 26, 2005 at 02:47:51PM -0500, sean finney wrote: On Sat, Feb 26, 2005 at 02:18:19PM -0500, Josh Metzler wrote: I seem to recall hearing that NEW processing is based solely on binary packages, so that the new source package would not need to go through NEW if it creates a binary package that is already in the archive. I couldn't find anything about this through google, though, so it may be best to upload to experimental first and see if your new packages go right in or not. istr the same thing, and was thinking that this might be the case. since i don't suppose the ftp-master illuminati are going to come out of hiding just to answer this question, i guess i'll upload, find out, and report back :/ Given that some people might find offensive to be compared to illuminati, I don't think this is the best way to engage the ftp-master. YMMV. IIUC, the override file only contains binary packages names, so renaming/splitting a source package without altering the binaries packages produced should not need changes to the override file. Cheers, -- Bill. [EMAIL PROTECTED] Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [OT] maildir
On Tue, Mar 01, 2005 at 09:03:06AM +1100, Brian May wrote: Also, all mailing list software I have seen so far exclusively uses mbox files. Sure, these are implementation issues that could be solved, but currently mbox wins. if the use of your stored mail is append-only and read-only, then mbox is the best way to go, for reasons you mentioned. it sucks for just about anything else though. sean -- signature.asc Description: Digital signature
Re: splitting a source package into 2 source packages
On Tue, Mar 01, 2005 at 12:29:09AM +0100, Bill Allombert wrote: Given that some people might find offensive to be compared to illuminati, I don't think this is the best way to engage the ftp-master. YMMV. perhaps i should have made it a bit more apparent that my tongue was slightly in-cheek when i said that. it was also slightly not in-cheek, as i do feel that the world of ftp-master is often shrouded in a veil of secrecy. however, i by no means meant to offend anyone personally and if i have i withdraw the comparison. sean -- signature.asc Description: Digital signature
Re: Debian Project Leader Election 2005
On Mon, Feb 28, 2005 at 09:48:49PM +0100, Nico Golde wrote: The candidates are: o Matthew Garrett [EMAIL PROTECTED] ^^ Is the email address wrong? There is no entry for http://qa.debian.org/[EMAIL PROTECTED] But there is such entry in http://db.debian.org/ Noone force you to use [EMAIL PROTECTED] to maintain your packages, although it's AFAIR recommended. Matthew uses the following: http://qa.debian.org/[EMAIL PROTECTED] regards fEnIo -- ,''`. Bartosz Fenski | mailto:[EMAIL PROTECTED] | pgp:0x13fefc40 | irc:fEnIo : :' : 32-050 Skawina - Glowackiego 3/15 - w. malopolskie - Poland `. `' phone:+48602383548 | proud Debian maintainer and user `- http://skawina.eu.org | jid:[EMAIL PROTECTED] | rlu:172001 signature.asc Description: Digital signature
Re: [OT] maildir
Scripsit Bernd Eckenfels [EMAIL PROTECTED] Thats why I responded, there is not really a need to modify maildir files, That depends. I sometimes want to archive the text people wrote to me without wasting disk space (and performance when I search my mail archive) on attachments that I don't need anymore. Mutt provides a nice UI for removing attachments, which involves modifying the message file. -- Henning Makholm ... and that Greek, Thucydides -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [OT] maildir
Scripsit Brian May [EMAIL PROTECTED] Sure, these are implementation issues that could be solved, but currently mbox wins. Who says you have to use either one or the other for everything? I use maildir for incoming mail but mbox files for most of my old saved mail. Works nice and seamlessly. -- Henning Makholm `Update' isn't a bad word; in the right setting it is useful. In the wrong setting, though, it is destructive... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Why are you guys using user space utilities not written by us that seem to not work? Could you change who is the debian maintainer for us?
On Mon, Feb 28, 2005 at 11:45:11PM +0100, José Luis Tallón wrote: From what i read below, there is somebody actually using QtParted for their installer. Someone who has a 4-month-old (or older) fork of the parted packages. (The Debian parted package stopped build-depending on libreiserfs at the beginning of November). Not much of a reason to hurry, if you ask me... -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: Bug#297233: ITP: wmansied -- An ANSI/ASCII editor.
On Mon, 2005-02-28 at 21:28 +, Roger Leigh wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nelson A. de Oliveira [EMAIL PROTECTED] writes: WMAnsiEd is an ANSI editor with functions like line drawing, ellipse, box, etc., written in Qt. All IBM ANSI and ASCII characters are ANSI is pretty meaningless as a standard, since ANSI standardised many different things. Perhaps you mean it implements ISO-6429 (ECMA-48) SGR control sequences, or maybe something entirely different? Either way, it would help if you were much more specific. (This applies equally to the other ITP.) For most of us who grew up on IBM PC systems in the DOS days, ANSI was a character set / graphics style first, and an organization second. I don't know what the official standards for the character set and terminal specifications are, but people who are interested are going to be looking for ANSI or ANSI graphics, not a standards document number. (Compare the usage of ISOs to refer to CD images regardless of their status as ISO-9660 filesystems and ISO's other standards.) -- Joe Wreschnig [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part
Re: [OT] maildir
On Tue, 2005-03-01 at 09:03 +1100, Brian May wrote: Michelle == Michelle Konzack [EMAIL PROTECTED] writes: inefficient at storing large number of very small files (due to block size limitations of file system), and more complicated to transfer/move/share. Michelle What is complicate ? You need only the right Michelle programs... Perhaps I should elaborate on this point. If I want to allow people to download a mbox folder (consider mailing list archive), all I do is put in under a HTTP accessible directory. People only need to download one file, and IIRC, there is a standard (or defacto standard) MIME type for mbox files. I believe a browser will automatically start mutt. In fact, I believe this will work even if the file is gzipped. Now take Maildirs... Sure, I could tar.gz the entire directory, but this means the recipient must manually untar it before accessing it. I don't believe there is a standard MIME type to distinguish these files either. As far as your browser is concerned, it isn't Maildir format, it is gzipped tar format. You mean you don't gzip mbox files before putting them out there for public access? Besides, there's always maildir2mbox, or a wrapper around whatever library call that any MUA (like Evo KMail) uses when it moves things from a Maildir folder to an mbox folder. Also, all mailing list software I have seen so far exclusively uses mbox files. Sure, since all it does is append. Sure, these are implementation issues that could be solved, but currently mbox wins. In certain narrow cases. Any time, though, that you have the MUA updating a big mbox at the same time an MTA is writing to it, issues will occur. And then there's NFS. If $USER is mounting $HOME, then mbox files could get corrupted, but Maildir won't. -- - Ron Johnson, Jr. Jefferson, LA USA PGP Key ID 8834C06B I prefer encrypted mail. You don't want give people a reason to not invite you to the hot parties. Pat Sajak, on being a Republican in Hollywood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [OT] maildir
On Mon, 2005-02-28 at 23:46 +, Henning Makholm wrote: Scripsit Brian May [EMAIL PROTECTED] Sure, these are implementation issues that could be solved, but currently mbox wins. Who says you have to use either one or the other for everything? I use maildir for incoming mail but mbox files for most of my old saved mail. Works nice and seamlessly. Exactly. -- - Ron Johnson, Jr. Jefferson, LA USA PGP Key ID 8834C06B I prefer encrypted mail. Whatever may be the moral ambiguities of the so-called demoratic nations and however serious may be their failure to conform perfectly to their democratic ideals, it is sheer moral perversity to equate the inconsistencies of a democratic civilization with the brutalities which modern tyrannical states practice. Reinhold Nieburhr, ca. 1940 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Let's remove mips, mipsel, s390 ... [or have strict arch: control? ]
Wouter Verhelst [EMAIL PROTECTED] writes: On Mon, Feb 28, 2005 at 08:18:56PM +0100, Goswin von Brederlow wrote: Peter Samuelson [EMAIL PROTECTED] writes: [Goswin von Brederlow] Which also avoids that packages will be unavailable on every new architecture debian introduces because the maintainer has to adjust the Architecture: line. I suppose it'd be nice to be able to use !foo in the Architecture: line for cases where something is known not to be supportable on a particular small subset of arches, through toolchain bugs or whatever. As a sidenote, wanna-build and buildd completly ignore the architecture line (apart from arch:all) and build packages anyway. Well, somewhat :-) they /attempt/ the build. sbuild will detect that it is not actually a package for this architecture, and will break it off right when the source package is extracted. It does? How does that work for packages with only a minimal control file that generate a full contol file during build? I see the Arch check of the dsc file in line 742-484 but that is very unreliable. Anything I missed? I believe the dpkg behaviour to set Architecture: any for sources that build arch dependent and independent packages (as opposed to e.g. Architecture: all i386 powerpc) makes it impossible to reliably decide if a package should be build for an arch. Anything in the control file is purely informative to the buildd admin at this point. No, sbuild does check more things. Ok, slightly exagerated, but a lot of packages would get build by sbuild wrongfully if it weren't for packages-arch-specific in wanna-build. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#297487: ITP: eleven -- programming language for creating reliable, scalable web applications
Package: wnpp Severity: wishlist Owner: Miriam Ruiz [EMAIL PROTECTED] * Package name: eleven Version : 1.0 Upstream Author : Joseph Morrison [EMAIL PROTECTED] * URL : http://eleven.sourceforge.net/ * License : GPL Description : programming language for creating reliable, scalable web applications Eleven is a programming language for creating reliable, scalable web applications. Applications are expressed in a high-level language with a simple, C-like syntax, from which the Eleven compiler generates complete, ready-to-run implementions in PHP or mod_perl. Eleven is designed for applications in which rapid development, high performance, and stability are critical - but total control over the look and feel is not (since Eleven generates most of the user interface automatically). Good examples are online exams and surveys, electronic voting, and business workflow applications. The program is already packaged and is temporarily at http://156.35.156.136/inniyah/eleven/ -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (900, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.9-2-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#297233: ITP: wmansied -- An ANSI/ASCII editor.
Joe Wreschnig writes: I don't know what the official standards for the character set and terminal specifications are... Whatever IBM said they were. I believe they are in the IBM PC Technical Reference Manual: I've got one around here somewhere. -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#297218: ITP: radeontool -- utility to control ATI Radeon backlight functions on laptops
Luigi Gangitano wrote: * Package name: radeontool Version : 1.5 Upstream Author : Frederick Dean [EMAIL PROTECTED] * URL : http://fdd.com/software/radeon/ * License : zlib license Description : utility to control ATI Radeon backlight functions on laptops Aside from the fact that this doesn't support older ATI chipsets, does this package supersede atitvout? Package: atitvout Priority: optional Section: misc Installed-Size: 48 Maintainer: Ola Lundqvist [EMAIL PROTECTED] Architecture: i386 Version: 0.4-3 Depends: libc6 (= 2.3.2.ds1-4) Filename: pool/main/a/atitvout/atitvout_0.4-3_i386.deb Size: 19616 MD5sum: 2cdbb42f45d0722522defb2c202a447c Description: ATI TV Out Support Program This utility program may be used for executing several configuration commands for the TV Out connector of ATI Rage Mobility P/M graphics boards under GNU/Linux on i386. Primarily it is intended to enable TV Out support after bootup and for switching the used TV standard from NTSC to PAL. -- Joshua Kwan signature.asc Description: OpenPGP digital signature
Re: Any reason why I'm not CCed by bugs of my packages?
On Mon, 28 Feb 2005, Joel Aelwyn wrote: I just make it a regular habit to scan my packages via the web interface, if only to remind myself about the wishlist bugs sitting on some of them. Sure, that's why I detected the bug just in time, but this personal habit is no excuse that a function of the BTS might work or might work not. Nothing's perfect. Sure - but arent we here to report and fix bugs - also the bugs of the BTS? I do not understand your posting. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Let's remove mips, mipsel, s390 ... [or have strict arch: control? ]
On Tue, Mar 01, 2005 at 01:28:58AM +0100, Goswin von Brederlow wrote: Wouter Verhelst [EMAIL PROTECTED] writes: On Mon, Feb 28, 2005 at 08:18:56PM +0100, Goswin von Brederlow wrote: Peter Samuelson [EMAIL PROTECTED] writes: [Goswin von Brederlow] Which also avoids that packages will be unavailable on every new architecture debian introduces because the maintainer has to adjust the Architecture: line. I suppose it'd be nice to be able to use !foo in the Architecture: line for cases where something is known not to be supportable on a particular small subset of arches, through toolchain bugs or whatever. As a sidenote, wanna-build and buildd completly ignore the architecture line (apart from arch:all) and build packages anyway. Well, somewhat :-) they /attempt/ the build. sbuild will detect that it is not actually a package for this architecture, and will break it off right when the source package is extracted. It does? How does that work for packages with only a minimal control file that generate a full contol file during build? Such packages need to make sure their initial control file contains enough information about the architectures a package can be built on anyway if they want dpkg-buildpackage to run successfully. I see the Arch check of the dsc file in line 742-484 but that is very unreliable. Anything I missed? Haven't looked at the source, only know the behaviour when a foreign architecture's package's build is attempted. Something like Architecture not in control file: i386 -- skipped or so. Anything in the control file is purely informative to the buildd admin at this point. No, sbuild does check more things. Ok, slightly exagerated, but a lot of packages would get build by sbuild wrongfully if it weren't for packages-arch-specific in wanna-build. 'some', rather than 'a lot'; but apart from that, correct. -- EARTH smog | bricks AIR -- mud -- FIRE soda water | tequila WATER -- with thanks to fortune -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
pyblosxom up for adoption
Anyone using pyblosxom and would like to adopt it? I'm not using pyblosxom anymore and would like to give it away to more caring hands. -- .''`. Fredrik Steen, [EMAIL PROTECTED] : :' : 2CD6 C838 BE77 795F 5EF1 3E5B DA91 EE7B A58E 164 `. `' http://www.stone.nu/ `-- http://www.debian.org/ signature.asc Description: Digital signature
Accepted gcc-snapshot 20050227-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 27 Feb 2005 03:32:34 +0100 Source: gcc-snapshot Binary: gcc-snapshot Architecture: source i386 Version: 20050227-1 Distribution: unstable Urgency: low Maintainer: Debian GCC maintainers debian-gcc@lists.debian.org Changed-By: Matthias Klose [EMAIL PROTECTED] Description: gcc-snapshot - A SNAPSHOT of the GNU Compiler Collection Changes: gcc-snapshot (20050227-1) unstable; urgency=low . * CVS 20050227, taken from HEAD (gcc-4.0). Files: 81ad96f5ba264f717cd99ecee623154a 1334 devel extra gcc-snapshot_20050227-1.dsc d17194b478448b8ef066ea2e97d6d475 29329863 devel extra gcc-snapshot_20050227.orig.tar.gz c0fcb35d5f9369c4011676ddbc2dc0ae 83476 devel extra gcc-snapshot_20050227-1.diff.gz 36521bbf22f29e843835b133943e8e08 44161024 devel extra gcc-snapshot_20050227-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCIsvdStlRaw+TLJwRAh0TAJ0QzvmR56uEpQCnHhdtFLuh08m3vgCfa8mB mbpdxydvDbbNf0Fmi6oD4Pk= =QUIx -END PGP SIGNATURE- Accepted: gcc-snapshot_20050227-1.diff.gz to pool/main/g/gcc-snapshot/gcc-snapshot_20050227-1.diff.gz gcc-snapshot_20050227-1.dsc to pool/main/g/gcc-snapshot/gcc-snapshot_20050227-1.dsc gcc-snapshot_20050227-1_i386.deb to pool/main/g/gcc-snapshot/gcc-snapshot_20050227-1_i386.deb gcc-snapshot_20050227.orig.tar.gz to pool/main/g/gcc-snapshot/gcc-snapshot_20050227.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted getmail 3.2.5-3 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 28 Feb 2005 10:30:21 +0100 Source: getmail Binary: getmail Architecture: source all Version: 3.2.5-3 Distribution: unstable Urgency: low Maintainer: Fredrik Steen [EMAIL PROTECTED] Changed-By: Fredrik Steen [EMAIL PROTECTED] Description: getmail- POP3, APOP mail gatherer/forwarder (obsolete) Closes: 296429 Changes: getmail (3.2.5-3) unstable; urgency=low . * This package is obsolete use getmail4 instead. * Added information about getmail4 in description (Closes:#296429) Files: d1e1356950d8ff480b0a31fcfc7228da 595 mail optional getmail_3.2.5-3.dsc 978eefa21ab62df94741d7c725378ddb 6843 mail optional getmail_3.2.5-3.diff.gz c37674593197f320507d9fe84af8eec1 73908 mail optional getmail_3.2.5-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCIuVo2pHue6WOFk8RAmngAKCRJIcn5dVIJhtZYJUH2uNLpZVrWwCbB3SB FdvZOFvYzQd3o4WV/XbVty4= =z3jt -END PGP SIGNATURE- Accepted: getmail_3.2.5-3.diff.gz to pool/main/g/getmail/getmail_3.2.5-3.diff.gz getmail_3.2.5-3.dsc to pool/main/g/getmail/getmail_3.2.5-3.dsc getmail_3.2.5-3_all.deb to pool/main/g/getmail/getmail_3.2.5-3_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted tex4ht 20050216.2023-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 18 Feb 2005 08:11:44 +0530 Source: tex4ht Binary: tex4ht Architecture: source i386 Version: 20050216.2023-1 Distribution: unstable Urgency: low Maintainer: Kapil Hari Paranjape [EMAIL PROTECTED] Changed-By: Kapil Hari Paranjape [EMAIL PROTECTED] Description: tex4ht - LaTeX and TeX for Hypertext (HTML) Closes: 219346 219726 229362 229569 234678 244276 254049 256834 268126 Changes: tex4ht (20050216.2023-1) unstable; urgency=low . * New maintainer. Closes: #268126. * New upstream version (2005-02-16 20:23). Closes: #256834, #234678, #229362, #219726. * Organisation of files in the source package has changed somewhat; e.g. literate source files are included; see /usr/share/doc/tex4ht/README.src for details. Closes: #244276 * Added CFLAG to the Makefile to fix default graphics type to PNG. Closes: #219346. * Fixed typo in package description. Closes: #254049. * Added dvipng method for conversion. The ghostscript method depends on version = 8.14. The dvipng method is now the default as it was my suggestion :-). Closes: #229569. * Changed the file copyright to include LPPL v1.3 in place of v1.0. This is the new upstream license. * Changed erroneous execute permissions on data files under /usr/share/texmf. * Fixed some typos in the html documentation. * Added a symlink to the html documentation under the doc directory. * Fixed the #! line in script /usr/bin/mk4ht. Also modified temp/Makefile to handle this perl script. * Bumped standards version to 3.6.1 (no changes required). * Included the validation scripts from upstream in /usr/share/tex4ht. The relevant instructions are in README.validate. * Upload sponsored by Frank Küster [EMAIL PROTECTED] Files: 472cffe8936dafd4ba6aebadf7883053 603 tex optional tex4ht_20050216.2023-1.dsc 6e56c93cfbd22347d088a41f1df95f78 2446126 tex optional tex4ht_20050216.2023.orig.tar.gz dd475c520f1faa227f7206405188ca71 24686 tex optional tex4ht_20050216.2023-1.diff.gz 37b48c3af08d41debda955830647f458 1151918 tex optional tex4ht_20050216.2023-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCHbm5+xs9YyJS+hoRAm9jAKCYSRvpywFqHXMs8cFVx/rJ42RCwwCfZiU0 3kpIvztbUsn67A2STO4W3k8= =WCgu -END PGP SIGNATURE- Accepted: tex4ht_20050216.2023-1.diff.gz to pool/main/t/tex4ht/tex4ht_20050216.2023-1.diff.gz tex4ht_20050216.2023-1.dsc to pool/main/t/tex4ht/tex4ht_20050216.2023-1.dsc tex4ht_20050216.2023-1_i386.deb to pool/main/t/tex4ht/tex4ht_20050216.2023-1_i386.deb tex4ht_20050216.2023.orig.tar.gz to pool/main/t/tex4ht/tex4ht_20050216.2023.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted pdksh 5.2.14-17 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 27 Feb 2005 18:36:55 +0100 Source: pdksh Binary: pdksh Architecture: source i386 Version: 5.2.14-17 Distribution: unstable Urgency: low Maintainer: Robert Luberda [EMAIL PROTECTED] Changed-By: Robert Luberda [EMAIL PROTECTED] Description: pdksh - A public domain version of the Korn shell Closes: 296446 Changes: pdksh (5.2.14-17) unstable; urgency=low . * Fix job control bug in non-interactive scripts (closes: #296446) Many thanks to Paul Stroud [EMAIL PROTECTED] for the patch. * lex.c: Don't expand aliases if there's an opening bracket just after the token. Fixes unreported problem with pdksh reporting syntax error on the init scripts that define function named `stop' (clashing with an built-in alias.) Files: 90009d5f4f32fc895b5d5a8ac1fa9314 561 shells optional pdksh_5.2.14-17.dsc 774e9cfcf64afd5ae5ff43a506292b7f 27351 shells optional pdksh_5.2.14-17.diff.gz 406088a8bbb761e13854fbbc399e311e 256706 shells optional pdksh_5.2.14-17_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCIgdTThh1cJ0wnDsRAshfAJ44lrNkhkJOxvHzt3GrWGGotUVuxACePNIA 5iUGMS+iezXVkWtBGgviEew= =QOLH -END PGP SIGNATURE- Accepted: pdksh_5.2.14-17.diff.gz to pool/main/p/pdksh/pdksh_5.2.14-17.diff.gz pdksh_5.2.14-17.dsc to pool/main/p/pdksh/pdksh_5.2.14-17.dsc pdksh_5.2.14-17_i386.deb to pool/main/p/pdksh/pdksh_5.2.14-17_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted solid-pop3d 0.15-13 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 27 Feb 2005 18:47:50 +0100 Source: solid-pop3d Binary: solid-pop3d Architecture: source i386 Version: 0.15-13 Distribution: unstable Urgency: low Maintainer: Robert Luberda [EMAIL PROTECTED] Changed-By: Robert Luberda [EMAIL PROTECTED] Description: solid-pop3d - POP3 server supporting Maildir, PAM, vhosting Closes: 290462 Changes: solid-pop3d (0.15-13) unstable; urgency=low . * 14_gcc_4.0_amd64.dpatch: fix FTBFS on amd64 with gcc-4.0 (closes: #290462). Files: 4c5de8aae1b4662f41303581fe3ec8a5 669 mail extra solid-pop3d_0.15-13.dsc 4ef17c9538f865d5f3d530537a4f59ca 27239 mail extra solid-pop3d_0.15-13.diff.gz 5531539632913e33de533acb5d8f5fb7 54618 mail extra solid-pop3d_0.15-13_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCIggIThh1cJ0wnDsRAjERAJ4leXTfovE/WSgYFM+t0naADz3FvgCfSlIg ISHJ2/GqPyeicv4f/HOpmeM= =2MwA -END PGP SIGNATURE- Accepted: solid-pop3d_0.15-13.diff.gz to pool/main/s/solid-pop3d/solid-pop3d_0.15-13.diff.gz solid-pop3d_0.15-13.dsc to pool/main/s/solid-pop3d/solid-pop3d_0.15-13.dsc solid-pop3d_0.15-13_i386.deb to pool/main/s/solid-pop3d/solid-pop3d_0.15-13_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted flow-tools 1:0.67-7 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Feb 2005 17:36:58 +0200 Source: flow-tools Binary: libcflow-perl flow-tools Architecture: source i386 Version: 1:0.67-7 Distribution: unstable Urgency: low Maintainer: Anibal Monsalve Salazar [EMAIL PROTECTED] Changed-By: Radu Spineanu [EMAIL PROTECTED] Description: flow-tools - collects and processes NetFlow data libcflow-perl - perl module for analyzing raw IP flow files written by cflowd Closes: 244161 245097 278858 285948 Changes: flow-tools (1:0.67-7) unstable; urgency=low . * New co-maintainers * Added patch that enables flow-tools to build on amd64 with gcc4 (thanks to Andreas Jochens) (closes: #285948) * Added postgresql support to flow-export (thanks to Chris Stromsoe) (closes: #244161, #245097) * Included a patch that enables filtering based on exporter address in flow-filter. This patch is needed by Stager (closes: #278858) * Changed the init script to properly shutdown flow-capture Files: cf86e41900b2756f50641b71d5975e99 833 net optional flow-tools_0.67-7.dsc e79720157a1c08edc37796b67d3d6541 11382 net optional flow-tools_0.67-7.diff.gz 1e03293e465d0739f0192e5bdaab8ddd 1085706 net optional flow-tools_0.67-7_i386.deb bed35865a300722a2aa17971e4c2fe35 50430 perl optional libcflow-perl_0.67-7_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFCIu0mgY5NIXPNpFURAp5rAKCYNR5reKVQzSYTtEM66LLL/WNd9gCdG2+m RPtxV+9J3TDyseA1ggTA2CY= =TXSv -END PGP SIGNATURE- Accepted: flow-tools_0.67-7.diff.gz to pool/main/f/flow-tools/flow-tools_0.67-7.diff.gz flow-tools_0.67-7.dsc to pool/main/f/flow-tools/flow-tools_0.67-7.dsc flow-tools_0.67-7_i386.deb to pool/main/f/flow-tools/flow-tools_0.67-7_i386.deb libcflow-perl_0.67-7_i386.deb to pool/main/f/flow-tools/libcflow-perl_0.67-7_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted inkscape 0.41-2 (powerpc source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 24 Feb 2005 19:58:32 +0100 Source: inkscape Binary: inkscape Architecture: source powerpc Version: 0.41-2 Distribution: unstable Urgency: low Maintainer: Wolfram Quester [EMAIL PROTECTED] Changed-By: Wolfram Quester [EMAIL PROTECTED] Description: inkscape - vector based drawing program Closes: 288946 294930 295341 Changes: inkscape (0.41-2) unstable; urgency=low . * grab patch from upstream to fix segfault on cmd-line export to png (Closes: #295341) * include file for bash-completion contributed by Julien Allali allali at univ-mlv.fr. Many thanks to him! * Move dia, libwmf-bin, pstoedit, sketch, imagemagick, and perlmagick to Recommends: instead of Suggests: to avoid the warning about not initialized extensions and get the functionality they provide into a default install. Explain that these packages are needed in the package description (Closes: #294930) * Fix wording in the german translation of the Could not load extensions dialogue (I really should use dpatch). * add an additional hunk to inkscape-0.41_amd64.diff. This was sent in by Andreas Jochens. Again thanks to him. I hope this is really fixed now. (Closes: #288946) Files: 7045d5f910c14773d93e837c4c988dc6 869 graphics optional inkscape_0.41-2.dsc 0276faf35c9f4f689811711ed2c11561 14804 graphics optional inkscape_0.41-2.diff.gz 7aca266f2efe81693f40c25a299e3992 5572286 graphics optional inkscape_0.41-2_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCIuupn88szT8+ZCYRAuSSAJ98+YD1iS3Ljfjm9TgYGRJdmksOKwCfbrSj 9FsPniQTBDPt7wHj/aSi4fM= =rBQA -END PGP SIGNATURE- Accepted: inkscape_0.41-2.diff.gz to pool/main/i/inkscape/inkscape_0.41-2.diff.gz inkscape_0.41-2.dsc to pool/main/i/inkscape/inkscape_0.41-2.dsc inkscape_0.41-2_powerpc.deb to pool/main/i/inkscape/inkscape_0.41-2_powerpc.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libcommons-codec-java 1.3-2 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 28 Feb 2005 11:39:51 +0100 Source: libcommons-codec-java Binary: libcommons-codec-java Architecture: source all Version: 1.3-2 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers [EMAIL PROTECTED] Changed-By: Arnaud Vandyck [EMAIL PROTECTED] Description: libcommons-codec-java - encoder and decoders such as Base64 and hexadecimal codec Closes: 288456 Changes: libcommons-codec-java (1.3-2) unstable; urgency=low . * javadoc is now generated, thanks to gjdoc (closes: #288456). Files: 97a52b6c958e15b34572fd7b1f08bc7b 763 libs optional libcommons-codec-java_1.3-2.dsc fd5b72c3f0b5ab4d7095f8e7d7dcdbbc 3146 libs optional libcommons-codec-java_1.3-2.diff.gz 55311ee55652558f18583fb1469b77e6 124814 libs optional libcommons-codec-java_1.3-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCIvaI4vzFZu62tMIRAlIfAKCbvwbznwHIeHYXMo4xCWqEqGvJ/ACggFpj nvUWvwneeCcFOz70X317CxA= =rC5+ -END PGP SIGNATURE- Accepted: libcommons-codec-java_1.3-2.diff.gz to pool/main/libc/libcommons-codec-java/libcommons-codec-java_1.3-2.diff.gz libcommons-codec-java_1.3-2.dsc to pool/main/libc/libcommons-codec-java/libcommons-codec-java_1.3-2.dsc libcommons-codec-java_1.3-2_all.deb to pool/main/libc/libcommons-codec-java/libcommons-codec-java_1.3-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libcommons-dbcp-java 1.2.1-2 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 28 Feb 2005 11:50:22 +0100 Source: libcommons-dbcp-java Binary: libcommons-dbcp-java Architecture: source all Version: 1.2.1-2 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers [EMAIL PROTECTED] Changed-By: Arnaud Vandyck [EMAIL PROTECTED] Description: libcommons-dbcp-java - Database Connection Pooling Services Closes: 234640 Changes: libcommons-dbcp-java (1.2.1-2) unstable; urgency=low . * built with kaffe * now build the javadoc (closes: #234640). Files: d85628b724eedf92562514813c1e3ad9 801 libs optional libcommons-dbcp-java_1.2.1-2.dsc 2af4ebce9ca90ef75734674a16ca160a 9899 libs optional libcommons-dbcp-java_1.2.1-2.diff.gz e5384a2a66ef5039c4fef14bd488dbdf 215462 libs optional libcommons-dbcp-java_1.2.1-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCIvq/4vzFZu62tMIRAmvUAKCX5rAyMJ8llezNa4zHTvEp4sRqjwCgoll+ iZAy/cWzcSW+JI42sjfbcRY= =u8GA -END PGP SIGNATURE- Accepted: libcommons-dbcp-java_1.2.1-2.diff.gz to pool/main/libc/libcommons-dbcp-java/libcommons-dbcp-java_1.2.1-2.diff.gz libcommons-dbcp-java_1.2.1-2.dsc to pool/main/libc/libcommons-dbcp-java/libcommons-dbcp-java_1.2.1-2.dsc libcommons-dbcp-java_1.2.1-2_all.deb to pool/main/libc/libcommons-dbcp-java/libcommons-dbcp-java_1.2.1-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted revelation 0.4.0-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 9 Feb 2005 20:15:07 +0100 Source: revelation Binary: revelation Architecture: source i386 Version: 0.4.0-1 Distribution: unstable Urgency: low Maintainer: Stefan Voelkel [EMAIL PROTECTED] Changed-By: Stefan Voelkel [EMAIL PROTECTED] Description: revelation - GNOME2 Password manager Closes: 255419 275161 275162 294259 Changes: revelation (0.4.0-1) unstable; urgency=low . * New upstream release (Closes: #275162, #275161, #255419, #294259) Files: 9e43c70caf0c1b1f3705f232a9c3ade6 754 gnome optional revelation_0.4.0-1.dsc 6af97f5635ace151902226294f3ee9e0 197133 gnome optional revelation_0.4.0.orig.tar.gz 48699f22727cea46605c6722e4238d5b 3673 gnome optional revelation_0.4.0-1.diff.gz b9711de0350c1bd4ac44765a70b1b00d 80364 gnome optional revelation_0.4.0-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCHeUKzgQIDpRWreIRAiMgAJ9HCCJgbBfr/yJ4bl4uzNDzu+AJYwCfQ39L p9mbRkyjKAbhWdVP+ZUjcRE= =B4jB -END PGP SIGNATURE- Accepted: revelation_0.4.0-1.diff.gz to pool/main/r/revelation/revelation_0.4.0-1.diff.gz revelation_0.4.0-1.dsc to pool/main/r/revelation/revelation_0.4.0-1.dsc revelation_0.4.0-1_i386.deb to pool/main/r/revelation/revelation_0.4.0-1_i386.deb revelation_0.4.0.orig.tar.gz to pool/main/r/revelation/revelation_0.4.0.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libextractor 0.4.2-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Feb 2005 14:09:00 +0100 Source: libextractor Binary: extract libextractor1-dev libextractor1 Architecture: source i386 Version: 0.4.2-1 Distribution: unstable Urgency: high Maintainer: Daniel Baumann [EMAIL PROTECTED] Changed-By: Daniel Baumann [EMAIL PROTECTED] Description: extract- displays meta-data from files of arbitrary type libextractor1 - extracts meta-data from files of arbitrary type libextractor1-dev - extracts meta-data from files of arbitrary type Closes: 296051 Changes: libextractor (0.4.2-1) unstable; urgency=high . * New upstream release. * debian/* redone. * disabled glib related plugins on powerpc, read README.Debian for more information. * debian/control: added conflicts/replaces for old version (Closes: #296051). Files: 82b7beeac7bd39ca53543510ec8ecf6b 774 devel optional libextractor_0.4.2-1.dsc d99e1b13a017d39700e376a0edbf7ba2 5887095 devel optional libextractor_0.4.2.orig.tar.gz d385bb0816b68472d983ff37e2951b29 4934 devel optional libextractor_0.4.2-1.diff.gz 555d379fe35659672c899e2cd793cf53 18174 utils optional extract_0.4.2-1_i386.deb d4159501f50e285b33503b53820011ed 5715882 libs optional libextractor1_0.4.2-1_i386.deb 36b34405c959750b8594f7ba0f205d0e 17082 libdevel optional libextractor1-dev_0.4.2-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iEYEARECAAYFAkIi/28ACgkQELuA/Ba9d8aovwCeM+YMj2Ai4ho8dSgQ+z6OsQaE JdgAoIt6TFgBZidr15Rfx/t2xJm+YcNb =mmSR -END PGP SIGNATURE- Accepted: extract_0.4.2-1_i386.deb to pool/main/libe/libextractor/extract_0.4.2-1_i386.deb libextractor1-dev_0.4.2-1_i386.deb to pool/main/libe/libextractor/libextractor1-dev_0.4.2-1_i386.deb libextractor1_0.4.2-1_i386.deb to pool/main/libe/libextractor/libextractor1_0.4.2-1_i386.deb libextractor_0.4.2-1.diff.gz to pool/main/libe/libextractor/libextractor_0.4.2-1.diff.gz libextractor_0.4.2-1.dsc to pool/main/libe/libextractor/libextractor_0.4.2-1.dsc libextractor_0.4.2.orig.tar.gz to pool/main/libe/libextractor/libextractor_0.4.2.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libcommons-validator-java 1:1.1.4-2 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 28 Feb 2005 12:26:04 +0100 Source: libcommons-validator-java Binary: libcommons-validator-java Architecture: source all Version: 1:1.1.4-2 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers [EMAIL PROTECTED] Changed-By: Arnaud Vandyck [EMAIL PROTECTED] Description: libcommons-validator-java - ease and speed development and maintenance of validation rules Changes: libcommons-validator-java (1:1.1.4-2) unstable; urgency=low . * generate the javadoc Files: 798598fd45d8818cab1b3d1a1d12e638 975 libs optional libcommons-validator-java_1.1.4-2.dsc 1103d516b60aac7041ca7fceb872 9111 libs optional libcommons-validator-java_1.1.4-2.diff.gz 6d4ed6c176c05abb228659686e0dd3e7 175302 libs optional libcommons-validator-java_1.1.4-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCIwdL4vzFZu62tMIRAtJeAKCBAlLlaWHyOrg3LDTxpdS+AzNphwCbBUMA fFHfybplnXRXut+8I+qIA+M= =Vb0/ -END PGP SIGNATURE- Accepted: libcommons-validator-java_1.1.4-2.diff.gz to pool/main/libc/libcommons-validator-java/libcommons-validator-java_1.1.4-2.diff.gz libcommons-validator-java_1.1.4-2.dsc to pool/main/libc/libcommons-validator-java/libcommons-validator-java_1.1.4-2.dsc libcommons-validator-java_1.1.4-2_all.deb to pool/main/libc/libcommons-validator-java/libcommons-validator-java_1.1.4-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gosa 2.3-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 1 Feb 2005 15:42:36 +0100 Source: gosa Binary: gosa-schema gosa Architecture: source all Version: 2.3-1 Distribution: unstable Urgency: low Maintainer: Cajus Pollmeier [EMAIL PROTECTED] Changed-By: Cajus Pollmeier [EMAIL PROTECTED] Description: gosa - Web Based LDAP Administration Program gosa-schema - LDAP schema for GOsa Closes: 284716 293148 293444 Changes: gosa (2.3-1) unstable; urgency=low . * New upstream release * Added array_uniq to remove double entries in uid selectbox (Closes:#293444) * Adjusted shadow attributes to be days since 1970, not seconds. (Closes: #293148) * Corrected option to allow user password changes from samba clients (Closes: #284716) Files: 7779367f10c08138313edc25e44746ca 564 web optional gosa_2.3-1.dsc e3aa67514ace73bcf1e921a43984e706 2256213 web optional gosa_2.3.orig.tar.gz 90bb95bc3c71d006fe0ac50451d0efba 20 web optional gosa_2.3-1.diff.gz 61a7b70ab6741da80490a5c78d35c048 1116922 web optional gosa_2.3-1_all.deb 78d88f59b6fca7f179cfc77fafc5d94b 9984 web optional gosa-schema_2.3-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCIw56tyibJ/7Y+CYRAmq6AKCcJNlPd6fMSzk8aHEWhl19hkIrvQCgwZ+Q p5BlYQvqKw2Uzycdmll0kgk= =XJOZ -END PGP SIGNATURE- Accepted: gosa-schema_2.3-1_all.deb to pool/main/g/gosa/gosa-schema_2.3-1_all.deb gosa_2.3-1.diff.gz to pool/main/g/gosa/gosa_2.3-1.diff.gz gosa_2.3-1.dsc to pool/main/g/gosa/gosa_2.3-1.dsc gosa_2.3-1_all.deb to pool/main/g/gosa/gosa_2.3-1_all.deb gosa_2.3.orig.tar.gz to pool/main/g/gosa/gosa_2.3.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted wordpress 1.5.0-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Feb 2005 07:11:47 +0200 Source: wordpress Binary: wordpress Architecture: source all Version: 1.5.0-1 Distribution: unstable Urgency: high Maintainer: Kai Hendry [EMAIL PROTECTED] Changed-By: Kai Hendry [EMAIL PROTECTED] Description: wordpress - a semantic personal publishing platform or weblog manager Closes: 275814 287086 288613 Changes: wordpress (1.5.0-1) unstable; urgency=high . * Closes: #275814: New version fixes security flaws http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-1559 * Closes: #288613: /usr/share/wordpress/readme.html missing * Closes: #287086: new upstream 1.2.2 * Added some NEWS that users will find helpful in the upgrade Files: aa46802f5b52ffed6f58b8b006831bee 565 web optional wordpress_1.5.0-1.dsc df6dc18a7a0d93fa6bb187eb48b41612 280251 web optional wordpress_1.5.0.orig.tar.gz 0923b639ad71e07c45d9bc16d0675377 3955 web optional wordpress_1.5.0-1.diff.gz db1f2d48db2ea3ef8cbb2b5f1490fe94 283602 web optional wordpress_1.5.0-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCIYrlPIEVjnLS4AcRAiKTAJwJs004BnxFl9qrKkQfGLzfITXzzQCeKSzE 1wDGZvYiDuoNDBIdh4Me1ws= =Cbyn -END PGP SIGNATURE- Accepted: wordpress_1.5.0-1.diff.gz to pool/main/w/wordpress/wordpress_1.5.0-1.diff.gz wordpress_1.5.0-1.dsc to pool/main/w/wordpress/wordpress_1.5.0-1.dsc wordpress_1.5.0-1_all.deb to pool/main/w/wordpress/wordpress_1.5.0-1_all.deb wordpress_1.5.0.orig.tar.gz to pool/main/w/wordpress/wordpress_1.5.0.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted kernel-package 8.124.1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 28 Feb 2005 11:02:18 +0100 Source: kernel-package Binary: kernel-package Architecture: source all Version: 8.124.1 Distribution: unstable Urgency: low Maintainer: Manoj Srivastava [EMAIL PROTECTED] Changed-By: Sven Luther [EMAIL PROTECTED] Description: kernel-package - A utility for building Linux kernel related Debian packages. Closes: 296450 Changes: kernel-package (8.124.1) unstable; urgency=low . * NMU for release management reasons and d-i rc3 (deadline today) schedule. * Adds nubus support, thus allowing an upload of the new 2.4.27 powerpc packages. (Closes: #296450) Files: a93a8e31b207ae1c8f21e24c23b696a1 487 misc optional kernel-package_8.124.1.dsc 230d5b2af6ebb79eb6d69b46a82b980a 499420 misc optional kernel-package_8.124.1.tar.gz 7e8b3fa5dd0a7bb1a6627dc1f9146383 352022 misc optional kernel-package_8.124.1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCIxF92WTeT3CRQaQRArM4AJ9pmLu6y3nu7sV0jN7f+IB8tJU7pQCdFYpu zqMaIYKTrgdGEq0wZ0soboY= =7nvS -END PGP SIGNATURE- Accepted: kernel-package_8.124.1.dsc to pool/main/k/kernel-package/kernel-package_8.124.1.dsc kernel-package_8.124.1.tar.gz to pool/main/k/kernel-package/kernel-package_8.124.1.tar.gz kernel-package_8.124.1_all.deb to pool/main/k/kernel-package/kernel-package_8.124.1_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libapache-mod-limitipconn 0.04-3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 28 Feb 2005 13:27:59 +0100 Source: libapache-mod-limitipconn Binary: libapache-mod-limitipconn Architecture: source i386 Version: 0.04-3 Distribution: unstable Urgency: low Maintainer: Piotr Roszatycki [EMAIL PROTECTED] Changed-By: Piotr Roszatycki [EMAIL PROTECTED] Description: libapache-mod-limitipconn - module for Apache which limits simultaneous connections per IP Closes: 295089 Changes: libapache-mod-limitipconn (0.04-3) unstable; urgency=low . * Adaptated to new apache-modconf. Closes: #295089. * Adds a LocalIP directive to exempt a designated IP address from download limits. * Adds limiting by user, vhost, or load average. Files: d6691331c55e83bd255f287ce56e1cb3 649 web extra libapache-mod-limitipconn_0.04-3.dsc 609fc5ce5999fa3dcd4e442a4aa7bb63 7080 web extra libapache-mod-limitipconn_0.04-3.diff.gz 0b1ccd067d473137656d423860f1dac7 11058 web extra libapache-mod-limitipconn_0.04-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCIxZjhMHHe8CxClsRAvC8AJ0XY6U+tCPS9rDB6O6uA5ZUF56fUgCdFRNq 4XRyPdan0CckKeYKDZnXy40= =MuQ9 -END PGP SIGNATURE- Accepted: libapache-mod-limitipconn_0.04-3.diff.gz to pool/main/liba/libapache-mod-limitipconn/libapache-mod-limitipconn_0.04-3.diff.gz libapache-mod-limitipconn_0.04-3.dsc to pool/main/liba/libapache-mod-limitipconn/libapache-mod-limitipconn_0.04-3.dsc libapache-mod-limitipconn_0.04-3_i386.deb to pool/main/liba/libapache-mod-limitipconn/libapache-mod-limitipconn_0.04-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libapache2-mod-auth-pam 1.1.1-5 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 28 Feb 2005 14:08:26 +0100 Source: libapache2-mod-auth-pam Binary: libapache2-mod-auth-sys-group libapache2-mod-auth-pam Architecture: source i386 Version: 1.1.1-5 Distribution: unstable Urgency: low Maintainer: Piotr Roszatycki [EMAIL PROTECTED] Changed-By: Piotr Roszatycki [EMAIL PROTECTED] Description: libapache2-mod-auth-pam - module for Apache2 which authenticate using PAM libapache2-mod-auth-sys-group - Module for Apache2 which checks user against system group Closes: 281100 Changes: libapache2-mod-auth-pam (1.1.1-5) unstable; urgency=low . * Uses common-auth and common-account for PAM configuration. Closes: #281100. Files: d800fe9b34c71e5a899d85aa6cc93b80 702 web extra libapache2-mod-auth-pam_1.1.1-5.dsc 12aaed29806e08277cca405cc58c96ff 5542 web extra libapache2-mod-auth-pam_1.1.1-5.diff.gz ad5a27657a08479d52087748145bc299 5558 web extra libapache2-mod-auth-sys-group_1.1.1-5_i386.deb a5b52122be5b1825ad5dd0c750e17962 8376 web extra libapache2-mod-auth-pam_1.1.1-5_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCIxnQhMHHe8CxClsRAjRAAKCQJdCwIdJi0qgVdMRMZSt66eb3TwCfSc0b pr5PrSxSoPQgVkH2/PuRRa4= =8S78 -END PGP SIGNATURE- Accepted: libapache2-mod-auth-pam_1.1.1-5.diff.gz to pool/main/liba/libapache2-mod-auth-pam/libapache2-mod-auth-pam_1.1.1-5.diff.gz libapache2-mod-auth-pam_1.1.1-5.dsc to pool/main/liba/libapache2-mod-auth-pam/libapache2-mod-auth-pam_1.1.1-5.dsc libapache2-mod-auth-pam_1.1.1-5_i386.deb to pool/main/liba/libapache2-mod-auth-pam/libapache2-mod-auth-pam_1.1.1-5_i386.deb libapache2-mod-auth-sys-group_1.1.1-5_i386.deb to pool/main/liba/libapache2-mod-auth-pam/libapache2-mod-auth-sys-group_1.1.1-5_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted netstat-nat 1.4.5-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 28 Feb 2005 13:47:37 + Source: netstat-nat Binary: netstat-nat Architecture: source i386 Version: 1.4.5-2 Distribution: unstable Urgency: low Maintainer: Andrés Roldán [EMAIL PROTECTED] Changed-By: Andrés Roldán [EMAIL PROTECTED] Description: netstat-nat - A tool that display NAT connections Closes: 297108 Changes: netstat-nat (1.4.5-2) unstable; urgency=low . * Build-Depends on libc6-dev | libc6.1-dev. Fixes FTBFS bug on some archs. (Closes: #297108) Files: 7c76240d6d43178f9e62da2ec5f8c11e 699 net optional netstat-nat_1.4.5-2.dsc 7cec0081065c0fda2f4e910f67f2a939 19529 net optional netstat-nat_1.4.5-2.diff.gz 25db3d3d270d816bfa386bcddf1a81f9 11532 net optional netstat-nat_1.4.5-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCIyGi2OByS7KTlusRArcIAJ49cw2zZCMIjFvBtR7dqzPhqNGIwQCgr+zL fBFeWf25RgZGEX3TAY7QrpI= =/X12 -END PGP SIGNATURE- Accepted: netstat-nat_1.4.5-2.diff.gz to pool/main/n/netstat-nat/netstat-nat_1.4.5-2.diff.gz netstat-nat_1.4.5-2.dsc to pool/main/n/netstat-nat/netstat-nat_1.4.5-2.dsc netstat-nat_1.4.5-2_i386.deb to pool/main/n/netstat-nat/netstat-nat_1.4.5-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted monit 1:4.4-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 28 Feb 2005 12:26:38 +0100 Source: monit Binary: monit Architecture: source i386 Version: 1:4.4-1 Distribution: unstable Urgency: low Maintainer: Stefan Alfredsson [EMAIL PROTECTED] Changed-By: Stefan Alfredsson [EMAIL PROTECTED] Description: monit - A utility for monitoring and managing daemons or similar programs Closes: 169439 247226 258148 268530 277252 287659 Changes: monit (1:4.4-1) unstable; urgency=low . * New maintainer (Stefan Alfredsson, adoption agreed on IRC channel #kuf) * New upstream release * AMD64 compiles are fixed by upstream (please verify) (Closes: #287659) * Added dependency on 'coreutils' because of stat-usage (Closes: #247226) * Syntax checking from initscript, thanks to [EMAIL PROTECTED] (Closes: #258148) * Fixed spelling (Closes: #268530, #277252) * buildd logs indicate good arm/ppc/s390 builds (Closes: #169439) Files: 5040cd17ab73267c08b87eced10d54d0 648 admin extra monit_4.4-1.dsc 671e1882ae342118a2138a3468589967 458083 admin extra monit_4.4.orig.tar.gz 8a0b8732b71259b9166e35023077e879 6833 admin extra monit_4.4-1.diff.gz ba32e5abb2450a393a0b2fff4de587ff 219966 admin extra monit_4.4-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQFCIx8d7WvuLRx04LcRArwgAJ9Um6a0+Q42px/Dgb+LFVHO4k5eJgCdERGP hBN1NIareKcIBtWIRf9prJI= =6ord -END PGP SIGNATURE- Accepted: monit_4.4-1.diff.gz to pool/main/m/monit/monit_4.4-1.diff.gz monit_4.4-1.dsc to pool/main/m/monit/monit_4.4-1.dsc monit_4.4-1_i386.deb to pool/main/m/monit/monit_4.4-1_i386.deb monit_4.4.orig.tar.gz to pool/main/m/monit/monit_4.4.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libapache2-mod-auth-pam 1.1.1-6 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 28 Feb 2005 14:37:20 +0100 Source: libapache2-mod-auth-pam Binary: libapache2-mod-auth-sys-group libapache2-mod-auth-pam Architecture: source i386 Version: 1.1.1-6 Distribution: unstable Urgency: low Maintainer: Piotr Roszatycki [EMAIL PROTECTED] Changed-By: Piotr Roszatycki [EMAIL PROTECTED] Description: libapache2-mod-auth-pam - module for Apache2 which authenticate using PAM libapache2-mod-auth-sys-group - Module for Apache2 which checks user against system group Changes: libapache2-mod-auth-pam (1.1.1-6) unstable; urgency=low . * Added postinst/prerm scripts. Files: 0201f57a09f8e581631fb1a7d70ef78c 702 web extra libapache2-mod-auth-pam_1.1.1-6.dsc 67a9b0ba76920f1a5fbeadab5d8824c8 5863 web extra libapache2-mod-auth-pam_1.1.1-6.diff.gz 913ba08ea65cb4be7d632b811742042b 6046 web extra libapache2-mod-auth-sys-group_1.1.1-6_i386.deb 38324a6abde662368bb613096bba87b5 8862 web extra libapache2-mod-auth-pam_1.1.1-6_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCIyLqhMHHe8CxClsRArdjAJ9D30Xjgx+GuIAobg6lKDtXLx3cyACeLxyI Kv5fFeeiQR4m9RLUPQMScXc= =fgCR -END PGP SIGNATURE- Accepted: libapache2-mod-auth-pam_1.1.1-6.diff.gz to pool/main/liba/libapache2-mod-auth-pam/libapache2-mod-auth-pam_1.1.1-6.diff.gz libapache2-mod-auth-pam_1.1.1-6.dsc to pool/main/liba/libapache2-mod-auth-pam/libapache2-mod-auth-pam_1.1.1-6.dsc libapache2-mod-auth-pam_1.1.1-6_i386.deb to pool/main/liba/libapache2-mod-auth-pam/libapache2-mod-auth-pam_1.1.1-6_i386.deb libapache2-mod-auth-sys-group_1.1.1-6_i386.deb to pool/main/liba/libapache2-mod-auth-pam/libapache2-mod-auth-sys-group_1.1.1-6_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted kdelibs 4:3.3.2-3 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 28 Feb 2005 14:05:30 +0100 Source: kdelibs Binary: kdelibs4 kdelibs-bin kdelibs kdelibs4-doc kdelibs-data kdelibs4-dev Architecture: source i386 all Version: 4:3.3.2-3 Distribution: unstable Urgency: high Maintainer: Debian Qt/KDE Maintainers debian-qt-kde@lists.debian.org Changed-By: Debian Qt/KDE Maintainers debian-qt-kde@lists.debian.org Description: kdelibs- KDE core libraries metapackage kdelibs-bin - KDE core binaries kdelibs-data - KDE core shared data kdelibs4 - KDE core libraries kdelibs4-dev - KDE core libraries (development files) kdelibs4-doc - KDE core library documentation Closes: 292085 294204 294271 297095 Changes: kdelibs (4:3.3.2-3) unstable; urgency=high . * Urgency high as it closes a security RC bug . +++ Changes by Isaac Clerencia: . * Fix syntax error in dcopidlng, closes: #297095 (was causing kdepim an others to FTBFS). . * Apply patch from KDE 3.4 to fix CAN-2005-0237 (spoofing using IDN), closes: #294271, #294204. IDN is now disabled in all KDE apps unless the environment variable KDE_USE_IDN is set. . * Christopher Cheney has kindly relicensed man pages written by him from GDFL to GPL, update the license statement accordingly. Closes: #292085. Files: f7eb7e75e030f3df1053e9a1250c739c 1302 libs optional kdelibs_3.3.2-3.dsc ee097e54514e5524d18bf8a4600e1a69 443362 libs optional kdelibs_3.3.2-3.diff.gz f03e9ee4f79db9662b1a3e123cfee4d6 855214 libs optional kdelibs-bin_3.3.2-3_i386.deb 1b5e317c639495e5d802ddd5d94d8142 8187008 libs optional kdelibs4_3.3.2-3_i386.deb bbf8f638a6be032355aa2e0eb1315e4a 1231442 libdevel optional kdelibs4-dev_3.3.2-3_i386.deb bd726963e48162feadd5d2e4da22a6bf 18878 kde optional kdelibs_3.3.2-3_all.deb 099ad360bda1852b227e63f7e4c31d11 7084088 libs optional kdelibs-data_3.3.2-3_all.deb c0119c932f491560d9d30debfc5d5ed8 11570728 doc optional kdelibs4-doc_3.3.2-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Signed by Isaac Clerencia [EMAIL PROTECTED] iD8DBQFCIyPAQET2GFTmct4RAskjAKCILG7ab/ww/lpB3ZjqWTx/nzPRLQCdEGdd GcsTZW2fm6wN4lugq0UGBww= =VAQa -END PGP SIGNATURE- Accepted: kdelibs-bin_3.3.2-3_i386.deb to pool/main/k/kdelibs/kdelibs-bin_3.3.2-3_i386.deb kdelibs-data_3.3.2-3_all.deb to pool/main/k/kdelibs/kdelibs-data_3.3.2-3_all.deb kdelibs4-dev_3.3.2-3_i386.deb to pool/main/k/kdelibs/kdelibs4-dev_3.3.2-3_i386.deb kdelibs4-doc_3.3.2-3_all.deb to pool/main/k/kdelibs/kdelibs4-doc_3.3.2-3_all.deb kdelibs4_3.3.2-3_i386.deb to pool/main/k/kdelibs/kdelibs4_3.3.2-3_i386.deb kdelibs_3.3.2-3.diff.gz to pool/main/k/kdelibs/kdelibs_3.3.2-3.diff.gz kdelibs_3.3.2-3.dsc to pool/main/k/kdelibs/kdelibs_3.3.2-3.dsc kdelibs_3.3.2-3_all.deb to pool/main/k/kdelibs/kdelibs_3.3.2-3_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted dbus 0.23.2-3 (powerpc all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 28 Feb 2005 15:05:19 +0100 Source: dbus Binary: dbus-glib-1 dbus-1-doc python2.3-dbus dbus-glib-1-dev dbus-1-utils dbus-1 dbus-1-dev Architecture: source powerpc all Version: 0.23.2-3 Distribution: unstable Urgency: low Maintainer: D-Bus Maintainance Team [EMAIL PROTECTED] Changed-By: Sjoerd Simons [EMAIL PROTECTED] Description: dbus-1 - simple interprocess messaging system dbus-1-dev - simple interprocess messaging system (development headers) dbus-1-doc - simple interprocess messaging system (documentation) dbus-1-utils - simple interprocess messaging system (utilities) dbus-glib-1 - simple interprocess messaging system (GLib-based shared library) dbus-glib-1-dev - simple interprocess messaging system (GLib interface) python2.3-dbus - simple interprocess messaging system (Python interface) Closes: 297020 Changes: dbus (0.23.2-3) unstable; urgency=low . * debian/patches/dbus-abi-api.patch - Fix dbus api and abi breakage between 0.23.1 and 0.23.2 (Closes: #297020) Files: 43186a82cd210faf3061ab5fbb5ae44b 933 devel optional dbus_0.23.2-3.dsc a17adf4262f2e1c89241c01ab1c4cc3b 14965 devel optional dbus_0.23.2-3.diff.gz 4df95718fe3278548bb0a8ad5a08afcc 839870 doc optional dbus-1-doc_0.23.2-3_all.deb e4997fade2f8fd1a7d12261b30472b83 334050 devel optional dbus-1_0.23.2-3_powerpc.deb c7f273ef9745b506f6c2a19b5e522dbc 109628 libs optional dbus-glib-1_0.23.2-3_powerpc.deb e9130279619b1658afe5fd70339209f4 109082 utils optional dbus-1-utils_0.23.2-3_powerpc.deb fb49539c825c6e3f27d240083db1a16a 254308 libdevel optional dbus-1-dev_0.23.2-3_powerpc.deb dab5b65c241ef0c2defd29a46fa612db 115806 libdevel optional dbus-glib-1-dev_0.23.2-3_powerpc.deb 15d98110b17aa7ed956610873c840a89 153328 python optional python2.3-dbus_0.23.2-3_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCIyrhgTd+SodosdIRAsdPAKCCMDBMYig/trFGDI3/16UbYP7eNgCgwB68 wRFbeFp4youhtAPWKGwR9+0= =Nd0o -END PGP SIGNATURE- Accepted: dbus-1-dev_0.23.2-3_powerpc.deb to pool/main/d/dbus/dbus-1-dev_0.23.2-3_powerpc.deb dbus-1-doc_0.23.2-3_all.deb to pool/main/d/dbus/dbus-1-doc_0.23.2-3_all.deb dbus-1-utils_0.23.2-3_powerpc.deb to pool/main/d/dbus/dbus-1-utils_0.23.2-3_powerpc.deb dbus-1_0.23.2-3_powerpc.deb to pool/main/d/dbus/dbus-1_0.23.2-3_powerpc.deb dbus-glib-1-dev_0.23.2-3_powerpc.deb to pool/main/d/dbus/dbus-glib-1-dev_0.23.2-3_powerpc.deb dbus-glib-1_0.23.2-3_powerpc.deb to pool/main/d/dbus/dbus-glib-1_0.23.2-3_powerpc.deb dbus_0.23.2-3.diff.gz to pool/main/d/dbus/dbus_0.23.2-3.diff.gz dbus_0.23.2-3.dsc to pool/main/d/dbus/dbus_0.23.2-3.dsc python2.3-dbus_0.23.2-3_powerpc.deb to pool/main/d/dbus/python2.3-dbus_0.23.2-3_powerpc.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gnome-vfs2 2.8.4-2 (powerpc source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 28 Feb 2005 12:53:34 +0100 Source: gnome-vfs2 Binary: libgnomevfs2-dev libgnomevfs2-0 libgnomevfs2-common Architecture: source powerpc Version: 2.8.4-2 Distribution: unstable Urgency: high Maintainer: Takuo KITAME [EMAIL PROTECTED] Changed-By: Sjoerd Simons [EMAIL PROTECTED] Description: libgnomevfs2-0 - The GNOME virtual file-system library (runtime files) libgnomevfs2-common - The GNOME virtual file-system library (common files) libgnomevfs2-dev - The GNOME virtual file-system library (development files) Closes: 295775 Changes: gnome-vfs2 (2.8.4-2) unstable; urgency=high . * Remove howl depends from control.in instead of just control. All howl depends are now really gone (Closes: #295775) Files: 34ec1ff9fc7a7311edd911f9ae7b4305 1724 libs optional gnome-vfs2_2.8.4-2.dsc 656ed1ffbfc84829fd1f9bafb0ebb76e 35686 libs optional gnome-vfs2_2.8.4-2.diff.gz 65ceb15f7f1b6c72ab81c2955d6facca 1100014 devel optional libgnomevfs2-common_2.8.4-2_powerpc.deb 28fec78dbd74ce2545029adbb8f3ed7e 402170 libs optional libgnomevfs2-0_2.8.4-2_powerpc.deb dac1c98aed932f99a483fe1910d88ca6 509526 libdevel optional libgnomevfs2-dev_2.8.4-2_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCIw0ngTd+SodosdIRAoEaAJoCrOBavZHe7FL5EkGcF1qv+q1u+wCgkY85 89Zq6w529msDgivMXGMlulY= =MUKD -END PGP SIGNATURE- Accepted: gnome-vfs2_2.8.4-2.diff.gz to pool/main/g/gnome-vfs2/gnome-vfs2_2.8.4-2.diff.gz gnome-vfs2_2.8.4-2.dsc to pool/main/g/gnome-vfs2/gnome-vfs2_2.8.4-2.dsc libgnomevfs2-0_2.8.4-2_powerpc.deb to pool/main/g/gnome-vfs2/libgnomevfs2-0_2.8.4-2_powerpc.deb libgnomevfs2-common_2.8.4-2_powerpc.deb to pool/main/g/gnome-vfs2/libgnomevfs2-common_2.8.4-2_powerpc.deb libgnomevfs2-dev_2.8.4-2_powerpc.deb to pool/main/g/gnome-vfs2/libgnomevfs2-dev_2.8.4-2_powerpc.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mkvmlinuz 13 (powerpc source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Feb 2005 14:47:52 +0100 Source: mkvmlinuz Binary: mkvmlinuz Architecture: source powerpc Version: 13 Distribution: unstable Urgency: high Maintainer: Debian Kernel Team debian-kernel@lists.debian.org Changed-By: Sven Luther [EMAIL PROTECTED] Description: mkvmlinuz - create a kernel to boot a PowerPC machine from Open Firmware Changes: mkvmlinuz (13) unstable; urgency=high . * Added debconf magic to kernel-image postinst/postrm hooks. Files: 705c8f7dfb11bb4899d859d65312738c 607 devel optional mkvmlinuz_13.dsc daa06f94dd29c7964022faf7ea4eb556 8594 devel optional mkvmlinuz_13.tar.gz 020c9777b3b33e1490e590d50f145670 9326 devel optional mkvmlinuz_13_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCIzQP2WTeT3CRQaQRAplcAJ0WPIEYAE3gtKHpc5uI1iJ0XjxwMACbBdGt ErLwSc1ZXQgdOnvNE1aEvM8= =x6/w -END PGP SIGNATURE- Accepted: mkvmlinuz_13.dsc to pool/main/m/mkvmlinuz/mkvmlinuz_13.dsc mkvmlinuz_13.tar.gz to pool/main/m/mkvmlinuz/mkvmlinuz_13.tar.gz mkvmlinuz_13_powerpc.deb to pool/main/m/mkvmlinuz/mkvmlinuz_13_powerpc.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted secvpn 2.19 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 23 Feb 2005 15:03:58 +0100 Source: secvpn Binary: secvpn Architecture: source all Version: 2.19 Distribution: unstable Urgency: low Maintainer: Bernd Schumacher [EMAIL PROTECTED] Changed-By: Bernd Schumacher [EMAIL PROTECTED] Description: secvpn - Secure Virtual Private Network Closes: 274981 Changes: secvpn (2.19) unstable; urgency=low . * sudo patch from Yaroslav Halchenko [EMAIL PROTECTED] added, to let pppd and its secvpnmon run via sudo. Closes: #274981 Files: 5b46cf51229ce4d78815853ce4f2a468 529 net optional secvpn_2.19.dsc 4e661aecc6f43437bc201711b9faa288 217832 net optional secvpn_2.19.tar.gz 757ba47c0f41f4e36313961e6503dba1 223308 net optional secvpn_2.19_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCI0fyINZoglnvXbwRAriPAJ91wQquoF6tykNbx7eoWBgJc61eZACdGDfx a+DfHrftl27JRfKhu71SPTE= =1LV0 -END PGP SIGNATURE- Accepted: secvpn_2.19.dsc to pool/main/s/secvpn/secvpn_2.19.dsc secvpn_2.19.tar.gz to pool/main/s/secvpn/secvpn_2.19.tar.gz secvpn_2.19_all.deb to pool/main/s/secvpn/secvpn_2.19_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted lineakd 1:0.8.2-4 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 28 Feb 2005 17:18:23 +0100 Source: lineakd Binary: lineakd lineak-dev Architecture: source i386 Version: 1:0.8.2-4 Distribution: unstable Urgency: low Maintainer: Aurelien Jarno [EMAIL PROTECTED] Changed-By: Aurelien Jarno [EMAIL PROTECTED] Description: lineak-dev - LinEAK development files lineakd- Linux support for Easy Access and Internet Keyboards Closes: 297304 Changes: lineakd (1:0.8.2-4) unstable; urgency=low . * Pulled 64-bit fixes from CVS (closes: bug#297304). Files: d5c9411ab13ba4bceb1c8f30c057c4b2 623 x11 optional lineakd_0.8.2-4.dsc 84d9d1bea4b6ae44d89247bb3e286587 9241 x11 optional lineakd_0.8.2-4.diff.gz e1ba8ac61efc6807a40449a1cdd06e13 171592 x11 optional lineakd_0.8.2-4_i386.deb 3f79eeac5cb94f3246d6be8dd069153a 166784 libdevel optional lineak-dev_0.8.2-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCI06Nw3ao2vG823MRAgPQAJwMbbWPsoVjSzWKIr00K+K0iDaHlACfRuvd 2/8H1PFjrqyhIm+tdPFNNTg= =hgDD -END PGP SIGNATURE- Accepted: lineak-dev_0.8.2-4_i386.deb to pool/main/l/lineakd/lineak-dev_0.8.2-4_i386.deb lineakd_0.8.2-4.diff.gz to pool/main/l/lineakd/lineakd_0.8.2-4.diff.gz lineakd_0.8.2-4.dsc to pool/main/l/lineakd/lineakd_0.8.2-4.dsc lineakd_0.8.2-4_i386.deb to pool/main/l/lineakd/lineakd_0.8.2-4_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted classpath 2:0.14-1 (powerpc all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Feb 2005 14:29:53 + Source: classpath Binary: classpath-doc classpath-common-unzipped classpath-common classpath jikes-classpath Architecture: source all powerpc Version: 2:0.14-1 Distribution: unstable Urgency: low Maintainer: John Leuner [EMAIL PROTECTED] Changed-By: Michael Koch [EMAIL PROTECTED] Description: classpath - clean room standard Java libraries classpath-common - architecture independent files classpath-common-unzipped - architecture independent files classpath-doc - free Java API documentation jikes-classpath - wrapper for jikes using classes from Classpath package Changes: classpath (2:0.14-1) unstable; urgency=low . * New upstream release * debian/control: Depend on gjdoc * debian/rules: Generate javadocs Files: 72c8bf7d83fd1b8e6ce9745ec2bfaf50 871 libs optional classpath_0.14-1.dsc d3485efddc4a9ced341bb0f6b6fb1eda 5408514 libs optional classpath_0.14.orig.tar.gz 227a7e730d15a8671e610c5aad20354a 34337 libs optional classpath_0.14-1.diff.gz c19c1c4448ca220e44968322d3830c05 4353174 libs optional classpath-common_0.14-1_all.deb cb86101824a3c9348422f4c12e009be0 3148462 libs optional classpath-common-unzipped_0.14-1_all.deb feac81fcc9b16fced8230bedd97de5b2 271688 doc optional classpath-doc_0.14-1_all.deb 624c8a7d5e31d704a0fbde6b127a0e8a 38968 libs optional jikes-classpath_0.14-1_all.deb 937def11ed3632475b6c1b0a1ee95089 185786 libs optional classpath_0.14-1_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCI1FW4vzFZu62tMIRAhV8AJ4vT9WOxgkccLShfEeDkLow56vJRACghHhg Dx7uUt//1bR1mzk8XgLzLXA= =8p6J -END PGP SIGNATURE- Accepted: classpath-common-unzipped_0.14-1_all.deb to pool/main/c/classpath/classpath-common-unzipped_0.14-1_all.deb classpath-common_0.14-1_all.deb to pool/main/c/classpath/classpath-common_0.14-1_all.deb classpath-doc_0.14-1_all.deb to pool/main/c/classpath/classpath-doc_0.14-1_all.deb classpath_0.14-1.diff.gz to pool/main/c/classpath/classpath_0.14-1.diff.gz classpath_0.14-1.dsc to pool/main/c/classpath/classpath_0.14-1.dsc classpath_0.14-1_powerpc.deb to pool/main/c/classpath/classpath_0.14-1_powerpc.deb classpath_0.14.orig.tar.gz to pool/main/c/classpath/classpath_0.14.orig.tar.gz jikes-classpath_0.14-1_all.deb to pool/main/c/classpath/jikes-classpath_0.14-1_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted glib2.0 2.6.3-1 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 28 Feb 2005 09:38:38 +0100 Source: glib2.0 Binary: libglib2.0-0-dbg libglib2.0-udeb libglib2.0-data libglib2.0-dev libglib2.0-doc libglib2.0-0 Architecture: source i386 all Version: 2.6.3-1 Distribution: unstable Urgency: low Maintainer: Sebastien Bacher [EMAIL PROTECTED] Changed-By: Sebastien Bacher [EMAIL PROTECTED] Description: libglib2.0-0 - The GLib library of C routines libglib2.0-0-dbg - The GLib libraries and debugging symbols libglib2.0-data - Common files for GLib library libglib2.0-dev - Development files for the GLib library libglib2.0-doc - Documentation files for the GLib library libglib2.0-udeb - The GLib library of C routines (udeb) Changes: glib2.0 (2.6.3-1) unstable; urgency=low . * New upstream release. Files: e82489a3ad527005ff65009e61ce419f 1570 libs optional glib2.0_2.6.3-1.dsc 0778f22c3121dc2b7d6ae138129752fa 3047554 libs optional glib2.0_2.6.3.orig.tar.gz 94b57c492e3e1f5dda25843130b8f339 13145 libs optional glib2.0_2.6.3-1.diff.gz fe1c25a18f1096e44b02fcc1f20d77ad 196438 misc optional libglib2.0-data_2.6.3-1_all.deb 928ec870d9be57210b10bc7b9d0950ba 504298 doc optional libglib2.0-doc_2.6.3-1_all.deb ee52aa03d6043f2b3f2c9e28d3df9384 483552 debian-installer optional libglib2.0-udeb_2.6.3-1_i386.udeb 0c110eab8bf3602f3d71863cbe24ce21 446858 libs optional libglib2.0-0_2.6.3-1_i386.deb efa1062edb9c365f1bbc62aaeb089f0c 801178 libdevel optional libglib2.0-dev_2.6.3-1_i386.deb 776bcf6a3329eba90cb51fcd057e6030 768438 libdevel extra libglib2.0-0-dbg_2.6.3-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCI1VxQxo87aLX0pIRAtCPAJsF4+MMxm0JBGy1UlKp7SuyEYhWqgCeOt/w mroKWBzdiPq3riVxl0zayWk= =qqnQ -END PGP SIGNATURE- Accepted: glib2.0_2.6.3-1.diff.gz to pool/main/g/glib2.0/glib2.0_2.6.3-1.diff.gz glib2.0_2.6.3-1.dsc to pool/main/g/glib2.0/glib2.0_2.6.3-1.dsc glib2.0_2.6.3.orig.tar.gz to pool/main/g/glib2.0/glib2.0_2.6.3.orig.tar.gz libglib2.0-0-dbg_2.6.3-1_i386.deb to pool/main/g/glib2.0/libglib2.0-0-dbg_2.6.3-1_i386.deb libglib2.0-0_2.6.3-1_i386.deb to pool/main/g/glib2.0/libglib2.0-0_2.6.3-1_i386.deb libglib2.0-data_2.6.3-1_all.deb to pool/main/g/glib2.0/libglib2.0-data_2.6.3-1_all.deb libglib2.0-dev_2.6.3-1_i386.deb to pool/main/g/glib2.0/libglib2.0-dev_2.6.3-1_i386.deb libglib2.0-doc_2.6.3-1_all.deb to pool/main/g/glib2.0/libglib2.0-doc_2.6.3-1_all.deb libglib2.0-udeb_2.6.3-1_i386.udeb to pool/main/g/glib2.0/libglib2.0-udeb_2.6.3-1_i386.udeb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted ispell-tl 0.02-5 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 23 Feb 2005 22:16:25 +1100 Source: ispell-tl Binary: aspell-tl itagalog Architecture: source i386 Version: 0.02-5 Distribution: unstable Urgency: low Maintainer: Jan Alonzo [EMAIL PROTECTED] Changed-By: Jan Alonzo [EMAIL PROTECTED] Description: aspell-tl - Tagalog dictionary for GNU Aspell itagalog - A Tagalog dictionary for Ispell Closes: 295425 Changes: ispell-tl (0.02-5) unstable; urgency=low . * Transition to Aspell 0.60 (closes: #295425) * debian/control: + Provide aspell6-dictionary. + Depend on libaspell15 (= 0.60) * debian/rules: + Removed usr/lib/aspell and usr/share/aspell. The new aspell path is usr/lib/aspell-0.60 * debian/tl_affix.dat: New Aspell 0.60 affix format for aspell-tl. Files: f4df826a078c1bd7b7a40eb59476089c 693 text optional ispell-tl_0.02-5.dsc 86f18b04b425b1075aafe91ef554ad34 3063 text optional ispell-tl_0.02-5.diff.gz ecfbb72be9f4fac7bfb7304c2be032e0 110236 text optional itagalog_0.02-5_i386.deb 91057f097b968b0e69a110796b7f0adf 121658 text optional aspell-tl_0.02-5_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCI1gU1Ng1YWbyRSERAj6KAJ4/Oxj4r7EcCNlAx18HmRktONOftwCbBAQG zlXA29AF+Bg+EZlv+JxmEtc= =0psA -END PGP SIGNATURE- Accepted: aspell-tl_0.02-5_i386.deb to pool/main/i/ispell-tl/aspell-tl_0.02-5_i386.deb ispell-tl_0.02-5.diff.gz to pool/main/i/ispell-tl/ispell-tl_0.02-5.diff.gz ispell-tl_0.02-5.dsc to pool/main/i/ispell-tl/ispell-tl_0.02-5.dsc itagalog_0.02-5_i386.deb to pool/main/i/ispell-tl/itagalog_0.02-5_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted epm 3.7-0.1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 23 Feb 2005 22:25:09 +0100 Source: epm Binary: epm Architecture: source i386 Version: 3.7-0.1 Distribution: unstable Urgency: low Maintainer: Jeff Licquia [EMAIL PROTECTED] Changed-By: Rene Engelhard [EMAIL PROTECTED] Description: epm- Cross-platform package builder by Easy Software Products Closes: 188348 207252 Changes: epm (3.7-0.1) unstable; urgency=low . * Non-maintainer upload. * New upstream release (closes: #188348, #207252) Files: 425a44b21e57199a2b1b4691a3f0ca14 567 devel optional epm_3.7-0.1.dsc 3ade8cfe7e59ca8e65052644fed9fca4 463264 devel optional epm_3.7.orig.tar.gz 92ad0545b6bfb2566a9ae3d9cd229c64 25088 devel optional epm_3.7-0.1.diff.gz 9521c357467ef83ea39cf9509d4cb401 457652 devel optional epm_3.7-0.1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCI2Fw+FmQsCSK63MRAhgMAJ4p5zlu6liSlnmtuSGDOZAIe0ankQCdHVjn 41GaVlbPCLeWi2XLWa0SciY= =U1wN -END PGP SIGNATURE- Accepted: epm_3.7-0.1.diff.gz to pool/main/e/epm/epm_3.7-0.1.diff.gz epm_3.7-0.1.dsc to pool/main/e/epm/epm_3.7-0.1.dsc epm_3.7-0.1_i386.deb to pool/main/e/epm/epm_3.7-0.1_i386.deb epm_3.7.orig.tar.gz to pool/main/e/epm/epm_3.7.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
