Quando rilasceranno Sarge stable?
Ok, la risposta è: Rilasceranno Sarge come stable quando sarà pronta, questo già lo so. Ma la mia domanda è: come fanno a decidere che è pronta? Nuove versioni dei software continuano a farsi strada in Sarge, si vedono arrivare anche nuovi pacchetti che prima non c'erano. Questo mi fa pensare che l'obiettivo da raggiungere non è solo assenza di bugs noti, altrimenti non introdurrebbero nuovi pacchetti che si portano appresso certamente nuovi bugs. Immagino che, per rilasciare Sarge come stable, debbano raggiungere prima un obiettivo che si sono prefissati. Qual è questo obiettivo? P.S.: Questo è un cross-post da debian.user.italian dove non ho ricevuto risposte, ma solo il suggerimento, via email privata, di postare la domanda qui. Mi scuso se qualcuno si trova a leggerla due volte. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Quando rilasceranno Sarge stable?
On Tue, Feb 15, 2005 at 01:14:25PM +0100, Lucio Crusca wrote: Immagino che, per rilasciare Sarge come stable, debbano raggiungere prima un obiettivo che si sono prefissati. Qual è questo obiettivo? Se leggi d-d-a, c'e' l'update dai RMs in merito allo stato della release. Da li' sai anche quali sono gli aspetti da sistemare. Gli RC bugs sono solo un aspetto. -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Quando rilasceranno Sarge stable?
Francesco P. Lovergine ha scritto: Se leggi d-d-a, c'e' l'update dai RMs Scusa l'ignoranza: cos'è d-d-a e chi (o cosa) sono gli RMs? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Quando rilasceranno Sarge 'stable'?
Lucio Crusca disse: Francesco P. Lovergine ha scritto: Se leggi d-d-a, c'e' l'update dai RMs Scusa l'ignoranza: cos'è d-d-a e chi (o cosa) sono gli RMs? d = Debian d = developer a = announce R = Release M = Manager Ciao sc -- Stefano Canepa e-mail: [EMAIL PROTECTED] To follow the path: look at the master, follow the master, walk with the master, see through the master, become the master. http://www.stefanocanepa.it -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [Webb.it 2005] Partecipazione di Debian GNU/Linux
Il giorno mar, 15-02-2005 alle 20:07 +0100, SteX ha scritto: On Tue, Feb 15, 2005 at 10:02:54AM +0100, Francesco P. Lovergine wrote: Ciao Frankie, Qualcuno ha intenzione di partecipare? Si sta gia' organizzando qualcosa in particolare? Uhm, che io sappia quest'anno il webbit non avra' community di sorta ma solo vendor (quindi paganti), causa cronico passivo... Mi sbaglio? ebbene si', cito la mia frase e la risposta di Stefano Canepa: Io cmq pensavo di prendermi qualche di' di ferie per Milano e Padova e preparare i miei talk. Ora posso dare una amno per Debian. Purtroppo e' anche vero che la manifestazione ha assunto toni contradditori, rispetto allo spirito con cui era nata. Questo ad appannaggio delle comunita'. (SteX) Su questo punto hai ragione ma dalla telefonata che ho avuto con Silvia risulta che lo spazio a disposizione della comunit? ci saranno comunque tanto a Milano quanto a Padova per cui sta a noi occuparlo a dovere. (Stefano Canepa) Quindi c'e' posto (anche se piccolo) anche per le comunita' :)) Vi devo qualche aggiornamento. Ho sentito Paolo Didon, che in qualche maniera partecipa all'organizzazione del Webbit e mi ha detto che : 1) lo spazio gratuito per le comunit ci sar 2) che gli piacerebbe che tutte le varie realt del software libero si coordinassero per fare un mega stand tutti assieme: Debian, ILS, traduttori GNOME, sviluppatori di altre distro, assoli, LUG ecc... Diciamo webbit ci ha tenuto una porta aperta tocca a noi sfruttarla, coordinandoci e presentandoci agli organizzatori belli organizzati. Che ne dite? Ciao sc -- Stefano Canepa - email: [EMAIL PROTECTED] - www: http://www.stefanocanepa.it Three great virtues of a programmer: laziness, impatience and hubris. Le tre grandi virt di un programmatore: pigrizia, impazienza e arroganza. (Larry Wall) signature.asc Description: Questa parte del messaggio =?ISO-8859-1?Q?=E8?= firmata
Re: mplayer, the time has come
Ken Bloom wrote: On Mon, 14 Feb 2005 11:46:38 +0100, A Mennucc wrote: There have been two main problems keeping mplayer out of Debian: licenses and copyrights. Licenses: the upstream code contains some code that is protected by (more or less) actively enforced licenses: DeCSS code to decode encrypted dvd; ffmpeg and OpenDivx code to en/decode MPEG4. Solution: the DeCSS is deleted from the package proposed for Debian What functionality do we lose by doing this? my packaging of mplayer will play DVDs using libdvdread3 (exactly as xine does) the DeCSS code inside mplayer is (considered by the upstream authors to be) more optimized and faster ; but including it is troublesome, so the upstream mplayer allows for the deletion of it and the fallback on libdvdread3 a. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mplayer, the time has come
MJ Ray wrote: Andrea Mennucc wrote: I have uploaded a new version of the 'mplayer' package for Debian, namely version 1.0pre6-1 I have reviewed this package, but I've not tried building it. Here are my first comments, split under your headings. --- HISTORY and CURRENT STATUS=20 The README.Debian refers to diffs on a site tonelli.sns.it but I couldn't find them. Would running the cvs-changelog and storing the output help to comply with the letter as well as spirit of the GPL? debianizer - isn't there a debian/rules way to do this now? no way at all suppose that I do this: $ tar xjf MPlayer-1.0pre6.tar.bz2 $ mv MPlayer-1.0pre6 mplayer-1.0pre6 $ tar czf mplayer_1.0pre6.orig.tar.gz at this point I am dead: the file mplayer_1.0pre6.orig.tar.gz will contain DeCSS code, and nothing in debian/rules can delete this code from mplayer_1.0pre6.orig.tar.gz libmpcodecs - missing copyright or are these all but one mplayer creations? they are mplayer creations (at the best of my knowledge) TOOLS - all of this is deleted in response to a reply about one file, or do they really intend them all to be non-free? when I looked in it 2 years ago, I saw that many files did not have proper copyright statements in them. Since I am not packaging anything from TOOLS, I took the radical step to delete them debian/scripts/win32codecs.sh - does this depend on non-free software? nope it will download and install codecs that are non-free; but it is the user choice (and responsibility) to do that. This is no different than what libdvdread3 proposed wrt decss librari --- POPULAR SUPPORT While it's nice to see that developers are so keen for mplayer to be worked on, I hope that someone is directing them towards the historical record and the work which still needs to be done. I only saw it happen in one of the cited threads. I think that explaining this to everyone is one of the main challenges for the mplayer package maintainers and you should add a bit more about it to README.Debian, mentioning investigation_0.90 (does that get included in the /usr/share/doc?) investigation_0.90 is outdated: after 0.90 the upstream authors did their own investigation and prepared the 'Copyright' file --- HISTORY Is it really necessary to fan dead flames by calling them such in the README.Debian? Let bygones be bygones? you sure are right a.
Re: mplayer, the time has come
Henning Makholm wrote: Scripsit [EMAIL PROTECTED] (A Mennucc) Solution: the DeCSS is deleted from the package proposed for Debian (for this reason, I upload mplayer as a native package); That is not a valid reason to pretend it is a native package. The correct thing to do is to create a new .orig.tar.gz with the offending files removed from it, but keep the rest of the .orig.tar.gz unchanged. Debian changes and package infrastructure should still go in a .diff.gz, and the package version should consist of an upstream version with a separate Debian revision. I object to this a file mplayerorig.tar.gz is, as the name says, the original distributed source distributing my modified tar.gz disguising it as the upstream original one would be cause of confusion a.
Re: First line in /etc/hosts
On Sun, Feb 13, 2005 at 11:21:09AM -0600, John Hasler wrote: Every machine with more than one interface has at least two hostnames: localhost on network 127 and something else on the external networks. Nitpicking: every machine have exactly one hostname, that is contained in /proc/sys/kernel/hostname. The host _may_ have one or more network interfaces, every network interface _may_ have one or more addresses, and those addresses _may_ resolve to domain names (which are also called hostnames, but are completely independent from /proc/sys/kernel/hostname). I think there are two problems here: some packages make assumptions about *the* IP number and/or *the* hostname, and /etc/hosts gets misconfigured either by buggy software or the admin. Well, there is a quite sensible default for desktop machines with just one physical network interface. You just have to realize that this may not work for an increasing number of machines (think about laptops with both a wireless and a TP interface, connected to two different DHCP-managed networks at the same time). The biggest mistake people are used to make is thinking that the contents of /proc/sys/kernel/hostname has _anything_ to do with any address on any network interface, and just blindly use the output of `hostname`. Gabor -- - MTA SZTAKI Computer and Automation Research Institute Hungarian Academy of Sciences - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: all new Debian diagram - now with less chaos!
Hi Kev, list! On Tuesday 15 February 2005 08:27, Kevin Mark wrote: after my initial work on a diagram, and the comments and the work of madduck, I had some time to redo my diagram to produce a totally new concept. any comment appreciated. Really nice and clean. Great to see such fundamental processes documented properly! Some things though, perhaps someone can help me out here: * buildd: there is more than one of them and I always thought the results are checked (and signed) manually by the buildd admins? * propagation from experimental to unstable: I always thought that required a re-upload? * testing packages propagate to stable is perhaps better called release: testing becomes new-stable? Regards, David
Re: mplayer, the time has come
A Mennucc wrote: I object to this a file mplayerorig.tar.gz is, as the name says, the original distributed source distributing my modified tar.gz disguising it as the upstream original one would be cause of confusion All of the kernel-source packages that need it have an orig.tar.gz without non-free bits. Look at the 'prune' target in kernel-source-2.6.8 for example. It's just as wrong to make it Debian native as it is to say it's an upstream original that in reality lacks some non-free bits. And in practice, the latter is the lesser of two evils. -- Joshua Kwan signature.asc Description: OpenPGP digital signature
Re: Request for Help: apt 0.6
martin f krafft wrote: also sprach Martin Schulze [EMAIL PROTECTED] [2005.02.14.1851 +0100]: We need help by competent developers who work on apt 0.6 with the goal to get it supported properly and eventually enter sid and sarge. Thank you, Joey! For the record, I am too strung up right now to be any use in coordinating this. However, I will help out. Thanks. - take into account that the archive key is rotated yearly Why? What argument is there against a per-release key, including keys for security, testing, unstable, and experimental? It would certainly make things a little easier... See what I wrote in the line above the one you quoted: | - design and discuss this with the release team I didn't make this decision. It has been common practice on the Debian archive for a number of years though. There are pros and cons for using a yearly key and a key that lasts for an entire release. However, - if anything should be changed from the current situation, the ftpmaster (and release team) need to be involved and - if not a solution needs to be established to distribute the key other than by aj sending a mail to debian-devel with the location of the new key. Regards, Joey -- Open source is important from a technical angle. -- Linus Torvalds Please always Cc to me when replying to me on the lists. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mplayer, the time has come
A Mennucc [EMAIL PROTECTED] wrote: [please, please repair your quoting mechanism. Done that for you in this mail]. Henning Makholm wrote: That is not a valid reason to pretend it is a native package. The correct thing to do is to create a new .orig.tar.gz with the offending files removed from it, but keep the rest of the .orig.tar.gz unchanged. Debian changes and package infrastructure should still go in a .diff.gz, and the package version should consist of an upstream version with a separate Debian revision. I object to this a file mplayerorig.tar.gz is, as the name says, the original distributed source No, it isn't there are lots of packages that have removed non-free files from their orig.tar.gz files that way. There might even be packages for which no upstream archive in tar.gz form exists. Please see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=278524 and the discussions referenced therein. I wrote this bug report in order to enforce a policy that orig.tar.gz files *should* be pristine as possible. But the fact that this is necessary clearly shows that it is not a requirement. distributing my modified tar.gz disguising it as the upstream original one would be cause of confusion That's why you have to document this in debian/README.Debian or debian/README.Debian-source. But an orig.gar.gz file is just one technical part of a Debian source package, it doesn's say anything about pristine or repackaged. Regards, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer
Re: all new Debian diagram - now with less chaos!
Hi Kevin, Great work! I am glad to see you got down with dia; I love that tool. Here are some comments: a. I am not sure what the process realm is. b. Developers do not tag bugs, they sign packages. Is that what you meant? Also, note that at the moment, most only sign source packages and binary uploads, not the binary packages themselves. c. Upstream is not really a repository, is it? d. I am missing the link between buildd and unstable. They get the orig.tar.gz from unstable for any uploads in incoming that do not include the tarball. e. I think it's M. Schulze, not Shultze. f. Sven's name has an Umlaut; here, to cut-n-paste: Müller g. users processes should be users' processes, though I think you may want to use another word. Like plain users or user systems may be better. h. There are more rules as to when packages migrate from unstable to testing. i. You use both meanings of priority (changelog and control) without making it clear which one is meant. j. updates propagate, not updates propagates. I know you are talking about the collection, but it sounds weird. That's it for now. To get our graphs onto www.debian.org, I assume we file bugs against that pseudo-package. Let me know when you are ready, then we can submit one bug report together. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer, admin, user, and author `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver! signature.asc Description: Digital signature
Re: Request for Help: apt 0.6
Florian Weimer wrote: * Henrique de Moraes Holschuh: You still need to deal with key revocation and a new key being needed, anyway. Yearly changes will not make it more difficult, it will make sure those codepaths are tested (and used at least once an year). I can understand that in an ideal world, there would be a master key stored off-line which would be used to sign (and revoke) the release keys. In case of a compromise, the master key can be used to introduce a new release key (without intervention by the system administrator). But I doubt this is really necessary. If the release key is compromised, a DSA would have to be released anyway. This advisory would include the necessary steps to remove the compromised key from the system. Do we really need to automate this? You could even argue that the scheme without a master key is more secure because the number of trusted parties is smaller, and no one can introduce a new release key in a covert manner. It boils down to what we are trying to secure. AFAICS, the main risks are network layer attacks on the user and mirror breaches. Easy recovery from a compromised archive infrastructure shouldn't be a top priority, and it might well be impossible if the attack was successful (the single point of ownership problem). Even though this will probably work well on a small scale, it won't on a large scale. Just think about the installations of 500 or 1000 Debian machines that also have security support. This is not hypothetical. These installations do exist. You don't want to install a new key manually on them. Regards, Joey -- Open source is important from a technical angle. -- Linus Torvalds Please always Cc to me when replying to me on the lists. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mplayer, the time has come
On Tue, 15 Feb 2005, A Mennucc wrote: Henning Makholm wrote: Scripsit [EMAIL PROTECTED] (A Mennucc) That is not a valid reason to pretend it is a native package. The I object to this a file mplayerorig.tar.gz is, as the name says, the original distributed source Stop with the weed. We have been removing non-free stuff from .orig tarbals since ever. distributing my modified tar.gz disguising it as the upstream original one would be cause of confusion That's what the debian/copyright file is for. Or a debian/README.Source, and so on. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Request for Help: apt 0.6
* Martin Schulze: Even though this will probably work well on a small scale, it won't on a large scale. Just think about the installations of 500 or 1000 Debian machines that also have security support. This is not hypothetical. These installations do exist. You don't want to install a new key manually on them. In this context, manual means invoke apt-key to remove the old key and add the new one. This isn't much different from invoking apt-get (or pushing any other scripted change to the machines). Do you think it's still a problem, even if you take apt-key into account? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: all new Debian diagram - now with less chaos!
On Tue, Feb 15, 2005 at 10:29:37AM +0100, David Schmitt wrote: Hi Kev, list! On Tuesday 15 February 2005 08:27, Kevin Mark wrote: after my initial work on a diagram, and the comments and the work of madduck, I had some time to redo my diagram to produce a totally new concept. any comment appreciated. Really nice and clean. Great to see such fundamental processes documented properly! Some things though, perhaps someone can help me out here: Thanks! * buildd: there is more than one of them and I always thought the results are checked (and signed) manually by the buildd admins? someone just emailed me about this. * propagation from experimental to unstable: I always thought that required a re-upload? see above. * testing packages propagate to stable is perhaps better called release: testing becomes new-stable? see above. cheers, Kev -- counter.li.org #238656 -- goto counter.li.org and be counted! (__) (oo) /--\/ / ||| * /\---/\ ~~ ~~ Have you mooed today?... signature.asc Description: Digital signature
Bug#295328: general: Help messages to stderr should be banned
On Feb 15, Justin Pryzby [EMAIL PROTECTED] wrote: I suppose I will start filing minor bugs against packages that do this. I'd like to hear other people's opinions, though. (It occurs to me that help output to stderr is arguably appropriate if an invalid option is given). Part of the problem is that its fairly depressing WTF? This is a long-time UNIX tradition, I'd summarily close such a bug opened on one of my packages. -- ciao, Marco signature.asc Description: Digital signature
Re: Bug#295328: general: Help messages to stderr should be banned
On Tue, Feb 15, 2005 at 10:19:12AM +0100, Marco d'Itri wrote: On Feb 15, Justin Pryzby [EMAIL PROTECTED] wrote: I suppose I will start filing minor bugs against packages that do this. I'd like to hear other people's opinions, though. (It occurs to me that help output to stderr is arguably appropriate if an invalid option is given). Part of the problem is that its fairly depressing WTF? This is a long-time UNIX tradition, So your best rebuttal is It's tradition!? Strong argument you've got there. I'd summarily close such a bug opened on one of my packages. Good for you. - Matt signature.asc Description: Digital signature
Re: Request for Help: apt 0.6
Martin Schulze [EMAIL PROTECTED] writes: | - key management, - are able to review the key management part and - design and discuss this with the release team - (re-)design and discuss package updates and security updates - take into account that the archive key is rotated yearly Hi, I just wanted to mention that the key management affects more than just apt. Some partial mirror scripts also do Release.gpg verification to guard against intrusion. To name two: reprepro maintained by Bernhard R. Link currently in queue/NEW and debmirror which I maintain. It would be nice if they could also get key updates from the same management system. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Package xxx has broken dep on yyy: normal?
Dan Jacobson [EMAIL PROTECTED] writes: Upon apt-get, is it normal to every so often see Package xxx has broken dep on yyy? However the next day the problem is gone. Yes. If normal, then can't whatever intermediate stage not be split across the mirror push? Somehow can consistent versions of xxx and yyy either be made sure to go out this mirror run together, or both wait for the next run? No and yes. There are some packages with a strict version depend (=) between a arch:any and arch:all package. The maintainers upload will update the arch:all package to the new version while leaving most archs without the arch:any package. Some time after the upload the buildd will fill in the missing arch:any debs but not necessarily before the daily dinstall run. Those cases can't be avoided with the current DAK implementation but they should be. Patches are surely welcome. Other things are strict versioned depends between different source packages. Even with a coordinated upload of both source packages the buildds can (and will often) build them out of order so you see only one of them for a short while. But those cases should be uncommon and nothing can be done there. Thats just how unstable works. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#295328: general: Help messages to stderr should be banned
On Tue, 15 Feb 2005 10:19:12 +0100 [EMAIL PROTECTED] (Marco d'Itri) wrote: On Feb 15, Justin Pryzby [EMAIL PROTECTED] wrote: I suppose I will start filing minor bugs against packages that do this. I'd like to hear other people's opinions, though. (It occurs to me that help output to stderr is arguably appropriate if an invalid option is given). Part of the problem is that its fairly depressing WTF? This is a long-time UNIX tradition, I'd summarily close such a bug opened on one of my packages. Indeed, that's the only way people bothers to learn the 21|pager mantra ;-) -- Ricardo Mones Lastra - [EMAIL PROTECTED] Centro de Inteligencia Artificial, Universidad de Oviedo en Gijon 33271 Asturias, SPAIN. - http://www.aic.uniovi.es/mones -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#295328: marked as done (general: Help messages to stderr should be banned)
Your message dated Tue, 15 Feb 2005 11:05:34 + with message-id [EMAIL PROTECTED] and subject line Bug#295328: general: Help messages to stderr should be banned has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 15 Feb 2005 04:07:01 + From [EMAIL PROTECTED] Mon Feb 14 20:07:01 2005 Return-path: [EMAIL PROTECTED] Received: from mx2.stlawu.edu [199.0.76.10] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1D0tzJ-0002aD-00; Mon, 14 Feb 2005 20:07:01 -0800 Received: from localhost (localhost.localdomain [127.0.0.1]) by dummy.domain.name (Postfix) with ESMTP id 28ED9122E10; Mon, 14 Feb 2005 23:06:31 -0500 (EST) Received: from mx2.stlawu.edu ([127.0.0.1]) by localhost (mx1.stlawu.edu [127.0.0.1]) (amavisd-new, port 10025) with ESMTP id 20894-19; Mon, 14 Feb 2005 23:06:31 -0500 (EST) Received: from cyberia.stlawu.edu (cyberia.stlawu.edu [10.32.122.39]) by mx2.stlawu.edu (Postfix) with ESMTP id 054D4122DC6; Mon, 14 Feb 2005 23:06:31 -0500 (EST) Received: from pryzbyj by cyberia.stlawu.edu with local (Exim 3.36 #1 (Debian)) id 1D0tyo-0001pC-00; Mon, 14 Feb 2005 23:06:30 -0500 Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Justin Pryzby [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Subject: general: Help messages to stderr should be banned X-Mailer: reportbug 3.2 Date: Mon, 14 Feb 2005 23:06:30 -0500 Message-Id: [EMAIL PROTECTED] Sender: Justin Pryzby [EMAIL PROTECTED] X-Virus-Scanned: by amavisd-new at stlawu.edu Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: general Severity: wishlist I occasionally install a program and need to know how to use it as quickly as possible; for example, while reading through bug reports. So, I run foo --help. Sometimes, the help screen is more than 25 lines long, and it scrolls on past. So, I run foo --help |less. Occasionally, though, foo writes its help output to stderr, and I'm left with an empty less buffer. So, I try again: foo --help 21 |less. This is a pretty obnoxious command to have to type just to see what the required commands are, and in what order they are taken (and, I guess csh doesn't even allow it). I already know that I can use the video buffer with shift-pageup. And I know that help output is supposed to fit on a single page, but I also know that sometimes it doesn't. I suppose I will start filing minor bugs against packages that do this. I'd like to hear other people's opinions, though. (It occurs to me that help output to stderr is arguably appropriate if an invalid option is given). Part of the problem is that its fairly depressing when investigation into one bug leads to filing of another bug:) --- Received: (at 295328-done) by bugs.debian.org; 15 Feb 2005 11:05:46 + From [EMAIL PROTECTED] Tue Feb 15 03:05:46 2005 Return-path: [EMAIL PROTECTED] Received: from 83-216-134-182.neilsu339.adsl.metronet.co.uk (cyclone.suffields.me.uk) [83.216.134.182] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1D10WX-0007V3-00; Tue, 15 Feb 2005 03:05:46 -0800 Received: from asuffield by cyclone.suffields.me.uk with local (Exim 3.36 #1 (Debian)) id 1D10WM-0008PL-00 for [EMAIL PROTECTED]; Tue, 15 Feb 2005 11:05:34 + Date: Tue, 15 Feb 2005 11:05:34 + From: Andrew Suffield [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Bug#295328: general: Help messages to stderr should be banned Message-ID: [EMAIL PROTECTED] References: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol=application/pgp-signature; boundary=YiEDa0DAkWCtVeE4 Content-Disposition: inline In-Reply-To: [EMAIL PROTECTED] X-No-CC: I subscribe to this list; do not CC me on replies. User-Agent: Mutt/1.5.6+20040907i Sender: Andrew Suffield [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no
Re: all new Debian diagram - now with less chaos!
martin f krafft [EMAIL PROTECTED] wrote: h. There are more rules as to when packages migrate from unstable to testing. i. You use both meanings of priority (changelog and control) without making it clear which one is meant. Furthermore, for testing propagation i'ts urgency that matters, isn't it? And I've never read ITO as a tag for orphaning bug. Either one mails to -devel (or wherever) saying that they intend to give away or orphan some packages, but this isn't a bug, just conversation. In the BTS, I think the tag is simply O. Regards, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer
unsubscribe
-- [---] [ Carli Samuele [ [ E-mails: [[EMAIL PROTECTED] [[EMAIL PROTECTED] [[EMAIL PROTECTED] [ [ [ Icq: 60401601 - WohThaN K0mm4nd3R [ [---] [ Link utili: [ [ PLUG -- Prato Linux User Group -- http://www.prato.linux.it [ Debian GNU/Linux -- http://www.debian.org [ Blender -- http://www.blender.org -- http://www.blender.it -- http://www.kino3d.com [ Yafray -- http://www.yafray.org [ RudiMathematici -- http://www.rudimathematici.com/ [ The Linux Game Tome -- http://www.happypenguin.org [ [ Linux user #350178 -- http://counter.li.org [---] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#295328: general: Help messages to stderr should be banned
ti, 2005-02-15 kello 10:19 +0100, Marco d'Itri kirjoitti: On Feb 15, Justin Pryzby [EMAIL PROTECTED] wrote: I suppose I will start filing minor bugs against packages that do this. I'd like to hear other people's opinions, though. (It occurs to me that help output to stderr is arguably appropriate if an invalid option is given). Part of the problem is that its fairly depressing WTF? This is a long-time UNIX tradition, I'd summarily close such a bug opened on one of my packages. In my opinion, if you give a wrong option (or do some other syntax error on the command line), the proper thing to do is to give an error message, preferably short, saying what the error was and how to get the full help text. This is an error message, so it should go to the standard error output. When the user explicitly requests for a help text, it is not an error and should go to the standard output. GNU tools work like this already, and have, to the best of my knowledge, worked like this for well over a decade. Tools that behave differently are also fairly common, so I guess tradition isn't clearcut here. I do claim that the GNU way is the right way here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian-policy: Virtual package: change mp3-encoder with music-encoder
On Mon, Feb 14, 2005 at 12:31:18PM +, Colin Watson wrote: In that case, one would simply depend on that, and the shell wrapper would depend on an |-ed list of the encoders it understood. I still don't see that the virtual package could be useful. Well, I dont see why mp3-encoder is useful, since no package in main provides it and only one package suggests it. On the other hand, the shell wrapper seems to be a good idea. I will try to implement it. -- Jesus Climent info:www.pumuki.org Unix SysAdm|Linux User #66350|Debian Developer|2.6.10|Helsinki Finland GPG: 1024D/86946D69 BB64 2339 1CAA 7064 E429 7E18 66FC 1D7F 8694 6D69 We seem to be made to suffer. It's our lot in life. --C-3PO (Star Wars) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#295328: general: Help messages to stderr should be banned
Francesco P. Lovergine writes: It depends on programs, sometimes the same usage function is used for either --help or invalid options. Sure, but the output should still be directed correctly. -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#295328: general: Help messages to stderr should be banned
On Tue, Feb 15, 2005 at 07:38:08AM -0600, John Hasler wrote: Francesco P. Lovergine writes: It depends on programs, sometimes the same usage function is used for either --help or invalid options. Sure, but the output should still be directed correctly. Quite difficult if the function is the same. In both cases it uses stderr. -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#295328: general: Help messages to stderr should be banned
On Tue, Feb 15, 2005 at 03:06:19PM +0100, Francesco P. Lovergine wrote: On Tue, Feb 15, 2005 at 07:38:08AM -0600, John Hasler wrote: Francesco P. Lovergine writes: It depends on programs, sometimes the same usage function is used for either --help or invalid options. Sure, but the output should still be directed correctly. Quite difficult if the function is the same. In both cases it uses stderr. So you change the program to take a file descriptor into the help-printing function, or provide some other means of determining where to send the output. - Matt signature.asc Description: Digital signature
Re: Bug#295328: general: Help messages to stderr should be banned
On Tue, Feb 15, 2005 at 03:06:19PM +0100, Francesco P. Lovergine wrote: On Tue, Feb 15, 2005 at 07:38:08AM -0600, John Hasler wrote: Francesco P. Lovergine writes: It depends on programs, sometimes the same usage function is used for either --help or invalid options. Sure, but the output should still be directed correctly. Quite difficult if the function is the same. In both cases it uses stderr. A computer can technically do anything; difficulty results from (an) incorrect decision(s) by (a) programmer(s). -- 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#295328: general: Help messages to stderr should be banned
Francesco P. Lovergine [EMAIL PROTECTED] schrieb:
On Tue, Feb 15, 2005 at 07:38:08AM -0600, John Hasler wrote:
Francesco P. Lovergine writes:
It depends on programs, sometimes the same usage function is used for
either --help or invalid options.
Sure, but the output should still be directed correctly.
Quite difficult if the function is the same. In both cases it uses stderr.
#!/bin/sh
usage(){
if [ $1 = STDERR ]; then
EXITCODE=1
exec 2;
else
EXITCODE=0
fi
echo bla...
exit $EXITCODE
}
case $1 in
--help|-h|-help)
usage;;
--foo)
...
*)
usage STDERR;;
esac
Translation to Perl, Python, C, whatever, and to multiple arguments is
left to the reader as an afternoon exercise.
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
Re: Bug#295328: general: Help messages to stderr should be banned
Francesco Paolo Lovergine [EMAIL PROTECTED] writes: It depends on programs, sometimes the same usage function is used for either --help or invalid options. Not always GNU rules are followed appropriately. Right, and in that case, it's a bug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#295328: general: Help messages to stderr should be banned
Francesco P. Lovergine [EMAIL PROTECTED] writes: Quite difficult if the function is the same. In both cases it uses stderr. Oh good grief. Add an argument to the function saying where to direct the output. How hard is this? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#295328: general: Help messages to stderr should be banned
On Mon, Feb 14, 2005 at 11:06:30PM -0500, Justin Pryzby wrote: [...] I occasionally install a program and need to know how to use it as quickly as possible; for example, while reading through bug reports. So, I run foo --help. Sometimes, the help screen is more than 25 lines long, and it scrolls on past. So, I run foo --help |less. Occasionally, though, foo writes its help output to stderr, and I'm left with an empty less buffer. So, I try again: foo --help 21 |less. This is a pretty obnoxious command to have to type just to see what the required commands are, and in what order they are taken (and, I guess csh doesn't even allow it). [...] Actually, in csh/tcsh it's very un-obnoxious: foo --help | less This is one of the things I wish bash supports, so that I can switch to bash. (I use csh/tcsh as my primary shell.) FWIW. T -- Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -- Brian W. Kernighan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mirror the Packages files _after_ the packages!
S You've been told this before -- *debian-devel does not control the mirroring S implementation used by arbitrary Debian mirrors*. Either talk to the mirror S team and give them enough information to track this down, or -- since you S know him well enough to be kept in the loop about his vacation schedule -- S talk to your local mirror operator directly and get him to stop using broken S mirroring scripts. I'm saying that bug 6786 has the potential to turn the current perhaps two hour per day down time for apt-get, aptitude, etc. into a several day long down time. D Failed to fetch http://xx.linux.org.xx/debian/pool/main/x S Yeah, real helpful of you to blot out the only potentially useful bit of S information in your post... No. The root of the problem is bug 6786. Indeed if 6786 were fixed, the mirror process could break at any time and users could still apt-get upgrade with yesterdays state instead of not being to apt-get upgrade at all (if the mirror process happen to break during the 2 hour dark period each day.) Indeed, no 2 hour dark period necessary too. Please double check 6786 to see if it is merely a local problem. Would you close it? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#295328: general: Help messages to stderr should be banned
On Tue, 15 Feb 2005, Frank Küster wrote:
Francesco P. Lovergine [EMAIL PROTECTED] schrieb:
On Tue, Feb 15, 2005 at 07:38:08AM -0600, John Hasler wrote:
Francesco P. Lovergine writes:
It depends on programs, sometimes the same usage function is used for
either --help or invalid options.
Sure, but the output should still be directed correctly.
Quite difficult if the function is the same. In both cases it uses stderr.
#!/bin/sh
usage(){
if [ $1 = STDERR ]; then
EXITCODE=1
exec 2;
else
EXITCODE=0
fi
echo bla...
exit $EXITCODE
}
case $1 in
--help|-h|-help)
usage;;
--foo)
...
*)
usage STDERR;;
esac
Translation to Perl, Python, C, whatever, and to multiple arguments is
left to the reader as an afternoon exercise.
What's with all this complexity? Just redirect stdout to stderr when you call
the function. Geez.
==
usage() {
if [ $# -gt 0 ]; then
echo $@
fi
echo foo
echo baz
}
case $1 in
(-h)usage; exit 0;;
(*) usage Unknown option($1) 12; exit 1;;
esac
==
Re: mirror the Packages files _after_ the packages!
On Tue, Feb 15, 2005 at 11:51:10PM +0800, Dan Jacobson wrote: S You've been told this before -- *debian-devel does not control the mirroring S implementation used by arbitrary Debian mirrors*. Either talk to the mirror S team and give them enough information to track this down, or -- since you S know him well enough to be kept in the loop about his vacation schedule -- S talk to your local mirror operator directly and get him to stop using broken S mirroring scripts. I'm saying that bug 6786 has the potential to turn the current perhaps two hour per day down time for apt-get, aptitude, etc. into a several day long down time. How mirrors do their mirroring is up to the local mirror administrator, not to the general debian developer's community. Debian could promote this two-phase mirroring a bit more maybe, and/or provide nice scripts, that's probably why #6786 is still open. BUT DEBIAN CANNOT IN ANY WAY FORCE/CONTROL HOW MIRRORS OPERATE, especially not the secundary mirrors. D Failed to fetch http://xx.linux.org.xx/debian/pool/main/x S Yeah, real helpful of you to blot out the only potentially useful bit of S information in your post... No. The root of the problem is bug 6786. Indeed if 6786 were fixed, #6786 doesn't need to be fixed for this, the mirror admin of xx.linux.org.xx just needs to implement two-phase mirroring, something that anyone with a bit shell/rsync foo can implement on his/her own, and ttbomk, already a lot of mirrors actually _do_. As numerous people have told you before, bugger your local mirror admin, especially since he seems to have slow bandwidth and therefore the 'dark period' takes long. --Jeroen -- Jeroen van Wolffelaar [EMAIL PROTECTED] (also for Jabber MSN; ICQ: 33944357) http://Jeroen.A-Eskwadraat.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#295328: general: Help messages to stderr should be banned
On Tue, 15 Feb 2005 09:19:35 -0800
H. S. Teoh [EMAIL PROTECTED] wrote:
On Mon, Feb 14, 2005 at 11:06:30PM -0500, Justin Pryzby wrote:
[...]
I occasionally install a program and need to know how to use it as
quickly as possible; for example, while reading through bug reports.
So, I run foo --help. Sometimes, the help screen is more than 25
lines long, and it scrolls on past. So, I run foo --help |less.
Occasionally, though, foo writes its help output to stderr, and I'm
left with an empty less buffer. So, I try again: foo --help 21
|less. This is a pretty obnoxious command to have to type just to
see what the required commands are, and in what order they are taken
(and, I guess csh doesn't even allow it).
[...]
Actually, in csh/tcsh it's very un-obnoxious: foo --help | less
This is one of the things I wish bash supports, so that I can switch
to bash. (I use csh/tcsh as my primary shell.)
bash can be easily forced to be even more un-obnoxious, put:
function helpof()
{
$1 --help 21|pager
}
in your ~/.bashrc, then helpof command gives you all.
Shorten function name to your likings and probably you have to type less
than with command --help.
--
Ricardo Mones Lastra - [EMAIL PROTECTED]
Centro de Inteligencia Artificial, Universidad de Oviedo en Gijon
33271 Asturias, SPAIN. - http://www.aic.uniovi.es/mones
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Moria, as in the Author of
Not sure why people are looking for me, but I received an e-mail containing a conversation thread claiming I am unreachable. Last I checked I was pretty easy to reach through [EMAIL PROTECTED]. Moria is a game I wrote some 20 years ago. Hard to believe anyone would still be playing it. Anyway, if someone is trying to reach me please pass along my e-mail address. If you dont know what this e-mail is about then perhaps it was a prank on me so delete it.
Re: Moria, as in the Author of
On Tue, Feb 15, 2005 at 11:23:19PM +0430, Robert Koeneke wrote: Not sure why people are looking for me, but I received an e-mail containing a conversation thread claiming I am unreachable. Last I checked I was pretty easy to reach through [EMAIL PROTECTED] Moria is a game I wrote some 20 years ago. Hard to believe anyone would still be playing it. Anyway, if someone is trying to reach me please pass along my e-mail address. If you don't know what this e-mail is about then perhaps it was a prank on me so delete it. Hi Robert! The package is still part of Debian. It was the Debian maintainer that lost interest in the package. See: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=274472 Apparantly, people still use it, see: http://qa.debian.org/developer.php?popcon=moria I'm cc'ing this mail to bug#274472, so that it can be considered by people wanting to do something with it. Do you think moria still has a place in Debian? Or do you gather it might be better removed? --Jeroen -- Jeroen van Wolffelaar [EMAIL PROTECTED] (also for Jabber MSN; ICQ: 33944357) http://Jeroen.A-Eskwadraat.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mplayer, the time has come
Scripsit A Mennucc [EMAIL PROTECTED] debianizer - isn't there a debian/rules way to do this now? no way at all Yes way. See debian/rules get-orig-source in policy. Rest of reply in debian-legal. Why are you posting the same thing separately to two different lists? -- Henning Makholm However, the fact that the utterance by Epimenides of that false sentence could imply the existence of some Cretan who is not a liar is rather unsettling. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mirror the Packages files _after_ the packages!
Hi Jeroen, How mirrors do their mirroring is up to the local mirror administrator, not to the general debian developer's community. Debian could promote this two-phase mirroring a bit more maybe, and/or provide nice scripts, that's probably why #6786 is still open. BUT DEBIAN CANNOT IN ANY WAY FORCE/CONTROL HOW MIRRORS OPERATE, especially not the secundary mirrors. But Debian could at least offer an updated rsync-script. Its over a month ago, i posted an updated script to [EMAIL PROTECTED] but noone yet cared and updated it. Greetings Martin -- What's done to children, they will do to society. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#295430: ITP: cpufrequtils -- Tools to access to the Linux kernel cpufreq subsystem
Package: wnpp Severity: wishlist Owner: Javier Setoain [EMAIL PROTECTED] * Package name: cpufrequtils Version : 0.2-pre1 Upstream Author : Dominik Brodowski [EMAIL PROTECTED] * URL : http://www.example.org/ * License : GPL Description : Tools to access the Linux kernel cpufreq subsystem To make access to the Linux kernel cpufreq subsystem easier for users and cpufreq userspace tools, a cpufrequtils package was created. It contains command line tools to determine current CPUfreq settings and to modify them (cpufreq-info and cpufreq-set). -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.10 Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to es_ES.UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#295328: general: Help messages to stderr should be banned
H. S. Teoh [EMAIL PROTECTED] writes: Actually, in csh/tcsh it's very un-obnoxious: foo --help | less zsh too. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Moria, as in the Author of
Do you think moria still has a place in Debian? Or do you gather it might be better removed? A better question is whether Mr. Koeneke is willing to relicense his code under a free software license so that moria and angband and derivatives can finally be free. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Moria, as in the Author of
On Tue, 15 Feb 2005, Robert Koeneke wrote: Moria is a game I wrote some 20 years ago. Hard to believe anyone would still be playing it. Please drop by: http://www.thangorodrim.net to have an idea of how much people still play Moria and games based on it. And also see what was done with your code, and just how much people liked it: http://www.thangorodrim.net/history/version.txt -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: all new Debian diagram - now with less chaos!
On Tue, 2005-02-15 at 02:27 -0500, Kevin Mark wrote: Hi debianista, after my initial work on a diagram, and the comments and the work of madduck, I had some time to redo my diagram to produce a totally new concept. any comment appreciated. http://kmark.home.pipeline.com/newdebian.png http://kmark.home.pipeline.com/newdebian.dia Not to find fault with something that will clear up much confusion in the Debian Sphere of Being, but I am wonder where the contributions back to upstream are in this picture? Where should it go? I don't know. Debian is one of the largest contributors to upstream(s), with bug-fixes, feature adds and improvements in code cleanliness. As well as being upstream for many things. Also, shouldn't it also be noted the distributions that are based on Debian that give-back to upstream (like Ubuntu and the plugin-dev and pmount thing). Given I don't know if it warrants, as it would be a user submission with patch to the DBTS. Other than that, I think its very good looking, I don't have the knowledge to judge whether it is accurate of not. -- greg, [EMAIL PROTECTED] The technology that is Stronger, better, faster: Linux signature.asc Description: This is a digitally signed message part
Re: Moria, as in the Author of
On Tue, Feb 15, 2005 at 11:23:19PM +0430, Robert Koeneke wrote: Moria is a game I wrote some 20 years ago. Hard to believe anyone would still be playing it. Good software (and concepts) never dies. If you google for Moria variant you will actually see that not only people are still playing it, but there are variants abound: Angband, Druid, and Boss and it has been ported to quite a number of platforms not just Linux (see [1]). Regards Javier PS: I'm actually a Nethack, not a Moria, player myself :-) [1] http://www.piratehaven.org/~beej/moria/mirror/Games/Moria/ (Atari, Amiga, PC and other ports) or http://roguelike-palm.sourceforge.net/kMoria/index.php (PalmOS) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Moria, as in the Author of
On Tuesday, 15 de February de 2005 19:53, Robert Koeneke wrote: Not sure why people are looking for me, but I received an e-mail containing a conversation thread claiming I am unreachable. Last I checked I was pretty easy to reach through [EMAIL PROTECTED] Moria is a game I wrote some 20 years ago. Hard to believe anyone would still be playing it. Well, just another one to say that Moria was great, and that I've spent *lots* of hours during several years playing Moria, Angband and ZAngband. And I've used Angband code for some home projects too :) It would be great if you can relicense your code under the GPL or some other free license, others Angband developers like Ben Harrison have already done that. Best regards and thank you for creating Moria pgpHCX2dCVmJv.pgp Description: PGP signature
Re: Bug#295328: general: Help messages to stderr should be banned
This one time, at band camp, Matthew Palmer said: On Tue, Feb 15, 2005 at 03:06:19PM +0100, Francesco P. Lovergine wrote: On Tue, Feb 15, 2005 at 07:38:08AM -0600, John Hasler wrote: Francesco P. Lovergine writes: It depends on programs, sometimes the same usage function is used for either --help or invalid options. Sure, but the output should still be directed correctly. Quite difficult if the function is the same. In both cases it uses stderr. So you change the program to take a file descriptor into the help-printing function, or provide some other means of determining where to send the output. I just recently sent a patch upstream for hdparm for exactly this, implemented exactly this way, since his previous implementation was a single function that was reused. It is trivial to do so, and it is also the Right Thing, IMHO. -- - | ,''`.Stephen Gran | | : :' :[EMAIL PROTECTED] | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - pgpW0bNWMNDvh.pgp Description: PGP signature
Re: Package xxx has broken dep on yyy: normal?
Well OK, but please be aware of the cases where a kid leaves his village for a trip to the big city and his single chance to do an apt-get dist-upgrade. He can't just try again tomorrow if things don't work out. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Package xxx has broken dep on yyy: normal?
On Wed, 16 Feb 2005, Dan Jacobson wrote: Well OK, but please be aware of the cases where a kid leaves his village for a trip to the big city and his single chance to do an apt-get dist-upgrade. He can't just try again tomorrow if things don't work out. Unstable is definitely not for people who can't try again. Try this if you don't understand: awk 'NR = 258 NR = 278' /usr/share/common-licenses/GPL -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Looking for an NPTL porting project
Ahoy! Any developers on this list interested in some help porting an application from LinuxThreads to NPTL? As part of a research project, I need to work through these details, and figure I might as well make myself useful on a real app rather than mock up some braindead multithreaded hello world for the occasion. In particular, I'm looking for something that attempts to handle signals or work with PIDs under LinuxThreads, and which will break under NPTL unless proper conversion is done. Something non-graphical is preferable, but not necessary. Any takers? Pointers to other lists / development projects equally appreciated. -Blunt Jackson -- -:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: all new Debian diagram - now with less chaos!
On Tue, Feb 15, 2005 at 11:24:18AM +0100, martin f krafft wrote: Hi Kevin, Great work! I am glad to see you got down with dia; I love that tool. Here are some comments: Its cool that it exports to xfig as a way to use both tools. a. I am not sure what the process realm is. ACK. renamed it. b. Developers do not tag bugs, they sign packages. Is that what you meant? Also, note that at the moment, most only sign source packages and binary uploads, not the binary packages themselves. NACK. you lost me. this is a gap in my knowlege. differentiate source package, binary upload, and binary package. where do they go? what do developers do? who creates source package, binary uploads and binary pacakges? c. Upstream is not really a repository, is it? ACK. changed it. d. I am missing the link between buildd and unstable. They get the orig.tar.gz from unstable for any uploads in incoming that do not include the tarball. e. I think it's M. Schulze, not Shultze. ACK. f. Sven's name has an Umlaut; here, to cut-n-paste: Müller ACK. I still dont know how to fiddle with keymaps, input methods or such things to get these! g. users processes should be users' processes, though I think you may want to use another word. Like plain users or user systems may be better. ACK. h. There are more rules as to when packages migrate from unstable to testing. ACK. I'm not familar with all possibilities and also not sure how much space it would take to include it. maybe a 'subprocess' box? i. You use both meanings of priority (changelog and control) without making it clear which one is meant. NACK. I only used this word once in referense to high, medium, low migration of packages from unstable to testing. j. updates propagate, not updates propagates. I know you are talking about the collection, but it sounds weird. ACK. That's it for now. To get our graphs onto www.debian.org, I assume we file bugs against that pseudo-package. there is an existing package that could include these? or to make an ITP? Someone in the 'eyecatcher' project said these may be helpful. Let me know when you are ready, then we can submit one bug report together. Cool! Kev -- counter.li.org #238656 -- goto counter.li.org and be counted! (__) (oo) /--\/ / ||| * /\---/\ ~~ ~~ Have you mooed today?... signature.asc Description: Digital signature
Re: Bug#295328: general: Help messages to stderr should be banned
[EMAIL PROTECTED] (Marco d'Itri) writes: I suppose I will start filing minor bugs against packages that do this. I'd like to hear other people's opinions, though. (It occurs to me that help output to stderr is arguably appropriate if an invalid option is given). Part of the problem is that its fairly depressing WTF? This is a long-time UNIX tradition, I'd summarily close such a bug opened on one of my packages. It's not clear what you're talking about here. It's certainly correct (and tradition) for _error messages_ to go to stderr. However, --help output _is not an error message_. It is program output, produced in response to an explicit user request. Programs that send --help output to stderr are annoying for any user, and doubly so for inexperienced users that may not know how to redirect stderr (e.g., with 21). These are the reasons that the GNU standards specify that --help output should go to stdout, not stderr. [There are many non-GNU programs (and some GNU programs that don't follow the standards properly) that send --help output to stderr, but there seems to be no particular tradition about it -- basically prior to GNU, people didn't seem to think very hard about this issue, and it was pretty random whether stderr or stdout was used.] -Miles -- /\ /\ (^.^) ()) *This is the cute kitty virus, please copy this into your sig so it can spread. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: all new Debian diagram - now with less chaos!
On Tue, Feb 15, 2005 at 01:11:33PM +0100, Frank Küster wrote: martin f krafft [EMAIL PROTECTED] wrote: h. There are more rules as to when packages migrate from unstable to testing. i. You use both meanings of priority (changelog and control) without making it clear which one is meant. Furthermore, for testing propagation i'ts urgency that matters, isn't it? Hi Frank, isnt that addressed by the tag Urgency: Low|Medium|High? And I've never read ITO as a tag for orphaning bug. Either one mails to -devel (or wherever) saying that they intend to give away or orphan some packages, but this isn't a bug, just conversation. In the BTS, I think the tag is simply O. so, there is no 'bug' to the bts to orphan a package, simply a note to debian-devel? So folks are expected to troll it to pickup packages? ok. I will change the ITO to 'read about orphanded package on debian-devel'. -Kev -- counter.li.org #238656 -- goto counter.li.org and be counted! (__) (oo) /--\/ / ||| * /\---/\ ~~ ~~ Have you mooed today?... signature.asc Description: Digital signature
Re: all new Debian diagram - now with less chaos!
On Tue, Feb 15, 2005 at 05:34:38PM -0500, Greg Folkert wrote: On Tue, 2005-02-15 at 02:27 -0500, Kevin Mark wrote: Hi debianista, after my initial work on a diagram, and the comments and the work of madduck, I had some time to redo my diagram to produce a totally new concept. any comment appreciated. http://kmark.home.pipeline.com/newdebian.png http://kmark.home.pipeline.com/newdebian.dia Not to find fault with something that will clear up much confusion in the Debian Sphere of Being, but I am wonder where the contributions back to upstream are in this picture? Hi Greg, in my original diagram (http://kmark.home.pipeline.com/debian.png), I included an indication of that. I will be including it in this one, but have not done so yet. Where should it go? I don't know. Debian is one of the largest contributors to upstream(s), with bug-fixes, feature adds and improvements in code cleanliness. As well as being upstream for many things. Also, shouldn't it also be noted the distributions that are based on Debian that give-back to upstream (like Ubuntu and the plugin-dev and pmount thing). woun't that be out of the scope of my diagram? Given I don't know if it warrants, as it would be a user submission with patch to the DBTS. Other than that, I think its very good looking, I don't have the knowledge to judge whether it is accurate of not. -- thanks for the input. cheers, Kev -- counter.li.org #238656 -- goto counter.li.org and be counted! (__) (oo) /--\/ / ||| * /\---/\ ~~ ~~ Have you mooed today?... signature.asc Description: Digital signature
Re: RFC: graph of Debian package cycle
martin f krafft dijo [Sat, Feb 12, 2005 at 04:47:27PM +0100]: Based on the work of Kevin Mark (URL not available, sorry), I have made a graph of the life cycle of a Debian package for inclusion in my forthcoming book (http://debianbook.info). You can find the sources and generated files at http://people.debian.org/~madduck/graphs/package-cycle/en/ Good! I do hope to be soon near a graphics-capable display ;-) I have always liked this stuff. PS: right now it's really big in size. Sorry about that. If someone tells me how to reliably scale a dia diagram down, I will do so, gladly. I do it this way: dia -nt png -s800 diagram.dia This will output a 800 pixel wide diagram. Of course, this will be only as reliable as the selected resolution allows. Greetings, -- Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)1451-2244 / 5554-9450 PGP key 1024D/8BB527AF 2001-10-23 Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Ubuntu for packaging for Debian
I'd recently adquire a little laptop (p3 900, 256 MB RAM). I'm been thinking to install Ubuntu in it cause Ubuntu is optimized for desktop, but I'd like to package some stuff for Debian. Is it advisable to use a pure Debian instead ? Regards, mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Package xxx has broken dep on yyy: normal?
Dan Jacobson [EMAIL PROTECTED] writes: Well OK, but please be aware of the cases where a kid leaves his village for a trip to the big city and his single chance to do an apt-get dist-upgrade. He can't just try again tomorrow if things don't work out. I'm inclined to think that people should not do apt-get dist-upgrade on unstable. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Package xxx has broken dep on yyy: normal?
Dan Jacobson [EMAIL PROTECTED] writes: Well OK, but please be aware of the cases where a kid leaves his village for a trip to the big city and his single chance to do an apt-get dist-upgrade. He can't just try again tomorrow if things don't work out. So what? Then they don't have the bleading edge version of the package but their old non upgrade one. Big deal. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Package xxx has broken dep on yyy: normal?
Goswin von Brederlow [EMAIL PROTECTED] writes: Dan Jacobson [EMAIL PROTECTED] writes: Well OK, but please be aware of the cases where a kid leaves his village for a trip to the big city and his single chance to do an apt-get dist-upgrade. He can't just try again tomorrow if things don't work out. So what? Then they don't have the bleading edge version of the package but their old non upgrade one. Big deal. I think the point is that dist-upgrade can sometimes do the Wrong Thing in cases like this. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Ubuntu for packaging for Debian
On Wed, Feb 16, 2005 at 02:04:17AM -0400, Maykel Moya wrote: I'd recently adquire a little laptop (p3 900, 256 MB RAM). I'm been thinking to install Ubuntu in it cause Ubuntu is optimized for desktop, but I'd like to package some stuff for Debian. Is it advisable to use a pure Debian instead ? You can use Ubuntu and do Debian development in a chroot, or use Debian and do Ubuntu development in a chroot. So, you're free to pick whichever you prefer, but it will be more convenient to run the system where you will do (more of) your development. -- - mdz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: all new Debian diagram - now with less chaos!
* Kevin Mark [Tue, 15 Feb 2005 21:09:03 -0500]: And I've never read ITO as a tag for orphaning bug. Either one mails to -devel (or wherever) saying that they intend to give away or orphan some packages, but this isn't a bug, just conversation. In the BTS, I think the tag is simply O. so, there is no 'bug' to the bts to orphan a package, simply a note to debian-devel? So folks are expected to troll it to pickup packages? ok. I will change the ITO to 'read about orphanded package on debian-devel'. Please compare [1], [2], and [3]. Basically: 1. maintainer writes -devel 2. maintainer writes -devel and files RFAs 3. maintainer submits O: bug against wnnp and CC's -devel [1] http://lists.debian.org/debian-devel/2005/02/msg00346.html [2] http://lists.debian.org/debian-devel/2005/02/msg00534.html [3] http://lists.debian.org/debian-devel/2005/02/msg00676.html But orphaning bugs can be filed without sending mail to -devel, though this makes them less effective. HTH, -- Adeodato Simó EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621 Arguing with an engineer is like wrestling with a pig in mud: after a while, you realize the pig is enjoying it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: all new Debian diagram - now with less chaos!
also sprach Kevin Mark [EMAIL PROTECTED] [2005.02.15.1314 +0100]: b. Developers do not tag bugs, they sign packages. Is that what you meant? Also, note that at the moment, most only sign source packages and binary uploads, not the binary packages themselves. NACK. you lost me. this is a gap in my knowlege. differentiate source package, binary upload, and binary package. source package: dsc + (diff) + orig.tar.gz binary package: deb source upload: changes + list of files therein where do they go? all to incoming. what do developers do? twiddle our thumbs? nah, we turn software into debian packages by debianising them, and then using dpkg-genchanges to create the changes file. Please read its manpage, in particular about the -sa, -sd, and -si options to see which files the changes file will list. the upload consists of the source package and the binary package, unless the debian revision is greater than 1, in which case the orig.tar.gz file is not included. h. There are more rules as to when packages migrate from unstable to testing. ACK. I'm not familar with all possibilities and also not sure how much space it would take to include it. maybe a 'subprocess' box? you could just say meets requirements for testing i. You use both meanings of priority (changelog and control) without making it clear which one is meant. NACK. I only used this word once in referense to high, medium, low migration of packages from unstable to testing. yes, and as someone else pointed out, this should be urgency. sorry, i thought you used it elsewhere too. To get our graphs onto www.debian.org, I assume we file bugs against that pseudo-package. there is an existing package that could include these? or to make an ITP? www.debian.org is a pseudo package: http://www.debian.org/Bugs/pseudo-packages -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer, admin, user, and author `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver! signature.asc Description: Digital signature
help needed with mips build failure
Can someone with mips and/or libtool expertise examine the build failure for gnucash below, and see if they can diagnose the problem? http://buildd.debian.org/fetch.php?pkg=gnucashver=1.8.10-5arch=mipsstamp=1107337123file=logas=raw -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: help needed with mips build failure
On Tue, Feb 15, 2005 at 11:22:01PM -0800, Thomas Bushnell BSG wrote: Can someone with mips and/or libtool expertise examine the build failure for gnucash below, and see if they can diagnose the problem? http://buildd.debian.org/fetch.php?pkg=gnucashver=1.8.10-5arch=mipsstamp=1107337123file=logas=raw checking how to recognise dependant libraries... file_magic ELF [0-9][0-9]*-bit [LM]SB (shared object|dynamic lib ) You're using an old (and broken) version of libtool. C.f. http://lists.debian.org/debian-qa-packages/2003/09/msg00023.html for Ryan's boilerplate explanation for fixing this problem. Thanks, -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: Ubuntu for packaging for Debian
[Matt Zimmerman] You can use Ubuntu and do Debian development in a chroot, or use Debian and do Ubuntu development in a chroot. So, you're free to pick whichever you prefer, but it will be more convenient to run the system where you will do (more of) your development. Yes, and use pbuilder to build the package, please. :) (If only Ubuntu would do an effort to get their home-made packages like xresprobe into Debian. :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: all new Debian diagram - now with less chaos!
In article [EMAIL PROTECTED] you wrote: And I've never read ITO as a tag for orphaning bug. This would be RFA? Greetings Bernd -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Please make Moria free (was: Moria, as in the Author of)
Hi all! Clint Adams [EMAIL PROTECTED]: Do you think moria still has a place in Debian? Or do you gather it might be better removed? A better question is whether Mr. Koeneke is willing to relicense his code under a free software license so that moria and angband and derivatives can finally be free. That would be nice and increase the chance that anybody adopt the Debian package, I think. Kindly regards, Erik -- www.ErikSchanze.de * Bitte keine HTML-E-Mails! No HTML mails, please! Limit: 100 kB * * Linux-Info-Tag in Dresden, am 29. Oktober 2005 * Info: http://www.linux-info-tag.de * pgpKPH07Pvk2S.pgp Description: PGP signature
Re: /etc under svk
On Sat, 12 Feb 2005 23:16:31 +0100, Florian Weimer [EMAIL PROTECTED] wrote: * Torsten Landschoff: Wanted to do that - but! Does svk handle symlinks? Thinking of /etc/rc?.d and /etc/alternatives... Wrote my own scripts to handle svn for /etc but they are still quite hackish... Subversion 1.1 and svk 0.18 both support symlinks natively. Another topic that needs to be addressed with putting /etc under version control is file modes and owner/group. cvs doesn't handle that well at all. Also, the repository needs to be protected as /etc itself is, as it contains passwords and other system confidential data. 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
Accepted snort 2.3.0-4 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Format: 1.7 Date: Tue, 15 Feb 2005 08:33:34 +0100 Source: snort Binary: snort-mysql snort-doc snort-rules-default snort-common snort-pgsql snort Architecture: source i386 all Version: 2.3.0-4 Distribution: experimental Urgency: low Maintainer: Javier Fernandez-Sanguino Pen~a [EMAIL PROTECTED] Changed-By: Javier Fernandez-Sanguino Pen~a [EMAIL PROTECTED] Description: snort - Flexible Network Intrusion Detection System snort-common - Flexible Network Intrusion Detection System [common files] snort-doc - Documentation for the Snort IDS [documentation] snort-mysql - Flexible Network Intrusion Detection System [MySQL] snort-pgsql - Flexible Network Intrusion Detection System [PostgreSQL] snort-rules-default - Flexible Network Intrusion Detection System ruleset Closes: 294755 295228 Changes: snort (2.3.0-4) experimental; urgency=low . * Call dh_installdocs with -i or -a depending on target, rename (Closes: #295228, #294755) * NEWS.Debian file to NEWS Files: ab56cdbe833ccb155b355f060ad15e96 960 net optional snort_2.3.0-4.dsc 0e9c3eb5c2681efc4a63fd31cb5badfc 229268 net optional snort_2.3.0-4.diff.gz 03ad6fc6242c665b753eff8ed875c062 88460 net optional snort-common_2.3.0-4_all.deb 5187b54eeae92e641ec1d8f339e93cca 1100034 doc optional snort-doc_2.3.0-4_all.deb 3f69e4fd9f008206eaea96d4e1634d26 216500 net optional snort-rules-default_2.3.0-4_all.deb a9f4912667d11fd54ea266df04867211 392216 net optional snort_2.3.0-4_i386.deb 99f177f345fcf59ecc5025fadd63291b 396998 net extra snort-mysql_2.3.0-4_i386.deb c74e3e947a84b4d3bea2aea76e062a06 396934 net optional snort-pgsql_2.3.0-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iQCVAwUBQhGo+ftEPvakNq0lAQH51gP+JB+/OiNB3/BhNgccNcdNHby2hkEt8y7C mLER8o6Yw/GB5pLYfZPUVYXC8NISBY7AMD8I0uiy619PQzDZr8r8LGditMhsd6H0 Oyqe3iGGXJtgZMaMixoblAPqkEdXTkRkBdaNn8JqhNZisId2iZIulUo3ZKL84dyn Hcx86nvekK8= =azt9 -END PGP SIGNATURE- Accepted: snort-common_2.3.0-4_all.deb to pool/main/s/snort/snort-common_2.3.0-4_all.deb snort-doc_2.3.0-4_all.deb to pool/main/s/snort/snort-doc_2.3.0-4_all.deb snort-mysql_2.3.0-4_i386.deb to pool/main/s/snort/snort-mysql_2.3.0-4_i386.deb snort-pgsql_2.3.0-4_i386.deb to pool/main/s/snort/snort-pgsql_2.3.0-4_i386.deb snort-rules-default_2.3.0-4_all.deb to pool/main/s/snort/snort-rules-default_2.3.0-4_all.deb snort_2.3.0-4.diff.gz to pool/main/s/snort/snort_2.3.0-4.diff.gz snort_2.3.0-4.dsc to pool/main/s/snort/snort_2.3.0-4.dsc snort_2.3.0-4_i386.deb to pool/main/s/snort/snort_2.3.0-4_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted farpd 0.2-7 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Format: 1.7 Date: Tue, 18 Jan 2005 16:50:55 +0100 Source: farpd Binary: farpd Architecture: source i386 Version: 0.2-7 Distribution: unstable Urgency: low Maintainer: Javier Fernandez-Sanguino Pen~a [EMAIL PROTECTED] Changed-By: Javier Fernandez-Sanguino Pen~a [EMAIL PROTECTED] Description: farpd - Fake ARP user space daemon Closes: 294398 Changes: farpd (0.2-7) unstable; urgency=low . * Recompile against latest libevent-dev (1.0b) and libdumbnet-dev (1.8) (Closes: #294398) * Build-Depend against libpcap0.8-dev | libpcap-dev Files: 98a5615d9dc18b9b466c24ab8b38803d 733 net optional farpd_0.2-7.dsc 063a2cf4ce64a7cfd5d5035d85f740ff 64880 net optional farpd_0.2-7.diff.gz 417e8cb474844101eb7945c2f8c6fc1b 10916 net optional farpd_0.2-7_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iQCVAwUBQhGnyPtEPvakNq0lAQH0bwP9FE06ye+9x2eBRKmLq6fGmmD0By9x4BVY ntzuhj26qIR0rOB/YpQsCZgcMjI8gexoEZyoea9OVvMB5YKw/eL3PaqXN3CPKw6y SwdsjVeMmd8p6+JbgVXVyoGV6T0a1URcrPq/7VEbEphOCkh8KI1wZt5tU61GYKn5 t2lXYyaQIRU= =5zY6 -END PGP SIGNATURE- Accepted: farpd_0.2-7.diff.gz to pool/main/f/farpd/farpd_0.2-7.diff.gz farpd_0.2-7.dsc to pool/main/f/farpd/farpd_0.2-7.dsc farpd_0.2-7_i386.deb to pool/main/f/farpd/farpd_0.2-7_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mpfr 2.1.0-6 (powerpc source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 15 Feb 2005 10:33:40 +0100 Source: mpfr Binary: libmpfr-dev Architecture: source powerpc Version: 2.1.0-6 Distribution: unstable Urgency: low Maintainer: Steve M. Robbins [EMAIL PROTECTED] Changed-By: Laurent Fousse [EMAIL PROTECTED] Description: libmpfr-dev - multiple precision floating-point computation Changes: mpfr (2.1.0-6) unstable; urgency=low . * Applied upstream patch #14, fixes possible computation error. Files: 9404106f34cdf6396476df2f71a5e644 669 math optional mpfr_2.1.0-6.dsc b666e1abd2ddbd95ac947f92c1be9399 24412 math optional mpfr_2.1.0-6.diff.gz 021333c12fffdabc4423bd6652d3d74d 232532 libdevel optional libmpfr-dev_2.1.0-6_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCEcQ1RoAVF6FpbSsRAr5IAJ4/3DgIj+ciDuUHcsIkeqXiD+g8pgCfYP8x a7+sESkiBct2Xio6q1FzjNE= =RfZP -END PGP SIGNATURE- Accepted: libmpfr-dev_2.1.0-6_powerpc.deb to pool/main/m/mpfr/libmpfr-dev_2.1.0-6_powerpc.deb mpfr_2.1.0-6.diff.gz to pool/main/m/mpfr/mpfr_2.1.0-6.diff.gz mpfr_2.1.0-6.dsc to pool/main/m/mpfr/mpfr_2.1.0-6.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted rng-tools 2-unofficial-mt.9-3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 15 Feb 2005 08:15:48 -0200 Source: rng-tools Binary: rng-tools Architecture: source i386 Version: 2-unofficial-mt.9-3 Distribution: experimental Urgency: low Maintainer: Henrique de Moraes Holschuh [EMAIL PROTECTED] Changed-By: Henrique de Moraes Holschuh [EMAIL PROTECTED] Description: rng-tools - Daemon to use a Hardware TRNG Closes: 295321 Changes: rng-tools (2-unofficial-mt.9-3) experimental; urgency=low . * Sync with 2-unofficial-mt.8-5 * Fix initscript to be POSIX-compliant and remove typo (closes: #295321) * Fix bad off-by-one error on the FIFO queue allocation that has been in the unofficial versions since forever. I really need to use valgrind more often. Files: 3fcb26f6e04acc29a6cf4526f147d4a5 628 utils optional rng-tools_2-unofficial-mt.9-3.dsc 9b970ac5a808b3421aca92f8588188b1 17633 utils optional rng-tools_2-unofficial-mt.9-3.diff.gz bd7429762a31e71e381e776e67e3571e 43648 utils optional rng-tools_2-unofficial-mt.9-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCEcwy7iXePxzbD+MRAqOiAJ0aqAW5hzlzeYu1yMDy18kN7KbLDACeLbnw wD7Ia5l/KIP4tICboltKqu0= =HTtU -END PGP SIGNATURE- Accepted: rng-tools_2-unofficial-mt.9-3.diff.gz to pool/main/r/rng-tools/rng-tools_2-unofficial-mt.9-3.diff.gz rng-tools_2-unofficial-mt.9-3.dsc to pool/main/r/rng-tools/rng-tools_2-unofficial-mt.9-3.dsc rng-tools_2-unofficial-mt.9-3_i386.deb to pool/main/r/rng-tools/rng-tools_2-unofficial-mt.9-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted redland-bindings 1.0.0.1-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 12 Feb 2005 10:23:10 + Source: redland-bindings Binary: python2.3-librdf python2.2-librdf librdf-ruby librdf-perl Architecture: source i386 Version: 1.0.0.1-1 Distribution: unstable Urgency: low Maintainer: Dave Beckett [EMAIL PROTECTED] Changed-By: Dave Beckett [EMAIL PROTECTED] Description: librdf-perl - Perl language bindings for the Redland RDF library librdf-ruby - Ruby 1.8 language bindings for the Redland RDF library python2.2-librdf - Python 2.2 language bindings for the Redland RDF library python2.3-librdf - Python 2.3 language bindings for the Redland RDF library Changes: redland-bindings (1.0.0.1-1) unstable; urgency=low . * New upstream release Files: 549f5f201635880739de11d6ffc77498 781 devel optional redland-bindings_1.0.0.1-1.dsc 36a492eb233809b8f8a5e73d8b97677a 671589 devel optional redland-bindings_1.0.0.1.orig.tar.gz ebeecfb7cea0e294a3108aa54d7bdc54 7675 devel optional redland-bindings_1.0.0.1-1.diff.gz 70553ce529582b56179cb97ac47dacdb 149672 perl optional librdf-perl_1.0.0.1-1_i386.deb f60a37005c68f0268ba5497820ae9177 79394 python optional python2.2-librdf_1.0.0.1-1_i386.deb cf9d56834a2d5b467d6cc4b5b922303a 79398 python optional python2.3-librdf_1.0.0.1-1_i386.deb d65a65c8c65ca57fcce0bbc30fb8b4bb 75760 interpreters optional librdf-ruby_1.0.0.1-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCEdTNQ+ySUE9xlVoRAiMJAKCHrFr2I87IIbHItTjxtN3mvDvgbACfY7Yw nWyi6z4Lz3bRNRXmCnpkJ5M= =oVoi -END PGP SIGNATURE- Accepted: librdf-perl_1.0.0.1-1_i386.deb to pool/main/r/redland-bindings/librdf-perl_1.0.0.1-1_i386.deb librdf-ruby_1.0.0.1-1_i386.deb to pool/main/r/redland-bindings/librdf-ruby_1.0.0.1-1_i386.deb python2.2-librdf_1.0.0.1-1_i386.deb to pool/main/r/redland-bindings/python2.2-librdf_1.0.0.1-1_i386.deb python2.3-librdf_1.0.0.1-1_i386.deb to pool/main/r/redland-bindings/python2.3-librdf_1.0.0.1-1_i386.deb redland-bindings_1.0.0.1-1.diff.gz to pool/main/r/redland-bindings/redland-bindings_1.0.0.1-1.diff.gz redland-bindings_1.0.0.1-1.dsc to pool/main/r/redland-bindings/redland-bindings_1.0.0.1-1.dsc redland-bindings_1.0.0.1.orig.tar.gz to pool/main/r/redland-bindings/redland-bindings_1.0.0.1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted bgoffice 3.0-3 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 7 Feb 2005 09:47:27 +0200 Source: bgoffice Binary: myspell-bg ibulgarian wbulgarian aspell-bg Architecture: source all i386 Version: 3.0-3 Distribution: unstable Urgency: low Maintainer: Anton Zinoviev [EMAIL PROTECTED] Changed-By: Anton Zinoviev [EMAIL PROTECTED] Description: aspell-bg - Bulgarian dictionary for aspell ibulgarian - The Bulgarian dictionary for ispell myspell-bg - The Bulgarian dictionary for myspell wbulgarian - The Bulgarian dictionary words for /usr/share/dict Closes: 295013 Changes: bgoffice (3.0-3) unstable; urgency=low . * Update for aspell ver 0.60. Closes: #295013. * bulgarian.kbd: convert to UTF-8, remove unnecessary couples qw-wq * Use affix compression for aspell. The new aspell dictionary is 24 Meg (8.5 compressed), the old was 32 Meg (12,6 compressed). * Update Standards-Version: 3.6.1. Files: 0376d2ccac5b7306cabe6068f8974bcc 705 text optional bgoffice_3.0-3.dsc 3559bdbdf1bb649e4c6831b2590402c6 21057 text optional bgoffice_3.0-3.diff.gz 29d7dc6b470b661981e81eead3b86319 249462 text optional myspell-bg_3.0-3_all.deb f0f2488bf1c9d1a4a6c8fddd75467321 1994298 text optional wbulgarian_3.0-3_all.deb 9575039e8dc4428018738678e0cd8181 8483952 text optional aspell-bg_3.0-3_i386.deb 2b29e7aadf59e9dc95c22ba316e72c9b 672792 text optional ibulgarian_3.0-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCEZSYJP1eZJv0KwcRAuLbAJ0W6HGbQm+GkEEuZ3s40Wqes6MpegCfRRWB r/zc7WtzGaCmFm6B2UfXRYI= =itbn -END PGP SIGNATURE- Accepted: aspell-bg_3.0-3_i386.deb to pool/main/b/bgoffice/aspell-bg_3.0-3_i386.deb bgoffice_3.0-3.diff.gz to pool/main/b/bgoffice/bgoffice_3.0-3.diff.gz bgoffice_3.0-3.dsc to pool/main/b/bgoffice/bgoffice_3.0-3.dsc ibulgarian_3.0-3_i386.deb to pool/main/b/bgoffice/ibulgarian_3.0-3_i386.deb myspell-bg_3.0-3_all.deb to pool/main/b/bgoffice/myspell-bg_3.0-3_all.deb wbulgarian_3.0-3_all.deb to pool/main/b/bgoffice/wbulgarian_3.0-3_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted php4-ps 1.3.1-4 (powerpc source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 15 Feb 2005 11:59:47 +0100 Source: php4-ps Binary: php4-ps Architecture: source powerpc Version: 1.3.1-4 Distribution: unstable Urgency: low Maintainer: Uwe Steinmann [EMAIL PROTECTED] Changed-By: Uwe Steinmann [EMAIL PROTECTED] Description: php4-ps- An extension to create PostScript files Changes: php4-ps (1.3.1-4) unstable; urgency=low . * full support for po-debconf, took over translations from php4-pgsql Files: 5cbca1787d508a144558ccd51dc54904 636 web optional php4-ps_1.3.1-4.dsc a127cce6f2f5ab8be5d256fdab226151 7668 web optional php4-ps_1.3.1-4.diff.gz afcd47e569eb2935508564080616 142098 web optional php4-ps_1.3.1-4_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCEdf5ih2Zvw18pwERAob1AJ9vVkHFBDUpYLjKjodApwt955h14QCbBG+n tMceNELXQ1Vrz+xezGtoSsA= =gQly -END PGP SIGNATURE- Accepted: php4-ps_1.3.1-4.diff.gz to pool/main/p/php4-ps/php4-ps_1.3.1-4.diff.gz php4-ps_1.3.1-4.dsc to pool/main/p/php4-ps/php4-ps_1.3.1-4.dsc php4-ps_1.3.1-4_powerpc.deb to pool/main/p/php4-ps/php4-ps_1.3.1-4_powerpc.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted hal 0.4.7-2 (powerpc all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 15 Feb 2005 11:51:34 +0100 Source: hal Binary: libhal-dev hal-doc libhal-storage-dev libhal-storage0 libhal0 hal hal-device-manager Architecture: source powerpc all Version: 0.4.7-2 Distribution: unstable Urgency: low Maintainer: Sjoerd Simons [EMAIL PROTECTED] Changed-By: Sjoerd Simons [EMAIL PROTECTED] Description: hal- Hardware Abstraction Layer hal-device-manager - Hardware Abstraction Layer user interface hal-doc- Hardware Abstraction Layer libhal-dev - Hardware Abstraction Layer - development files libhal-storage-dev - Hardware Abstraction Layer - development files libhal-storage0 - Hardware Abstraction Layer - shared library for storage devices libhal0- Hardware Abstraction Layer - shared library Closes: 292644 292661 293630 294033 Changes: hal (0.4.7-2) unstable; urgency=low . * debian/patches/storage-policy-debian.patch + Updated. Enable the quiet option for vfat volumes. (Closes: #292661) * debian/hal.dbus.init + Show a warning message when trying to start with an unsupported kernel. (Closes: #292644) * debian/patches/no_sysdevice.path + Don't die when a device doesn't have a sysfs path when finalizing the class device. (Closes: #293630) * debian/patches/storage-policy-zip.patch + Added. Correctly name partitioned zip mountpoints. Patch from Daniel Serpell. (Closes: #294033) Files: 7ef8507a013da668753e973313e2f35d 824 admin optional hal_0.4.7-2.dsc f2280c1be9e828ee94fbe3e16c48c29e 20880 admin optional hal_0.4.7-2.diff.gz 265550f3b0eb853586c94f915d2a4419 153258 admin optional hal-device-manager_0.4.7-2_all.deb e37309dd7995d08ed11364a9da961b90 140914 doc optional hal-doc_0.4.7-2_all.deb efa5545a980c6eee1ded6d676eeca322 225406 admin optional hal_0.4.7-2_powerpc.deb d49b032257532b69b06877d888c02a81 89836 libs optional libhal0_0.4.7-2_powerpc.deb 13bcbea551c477a95a9a385022b102be 90874 libs optional libhal-storage0_0.4.7-2_powerpc.deb 78f1ba53be8dde3a799000503d09513c 93122 libdevel optional libhal-dev_0.4.7-2_powerpc.deb 27b354487acc2071f7a16861ad867ab1 91692 libdevel optional libhal-storage-dev_0.4.7-2_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCEdjkgTd+SodosdIRAp8sAKCO+uitjwbK/e6wR/fRJnkwqxHnIgCcDXje SOYfgWbR1GBxHL/8TxNcstc= =9NCR -END PGP SIGNATURE- Accepted: hal-device-manager_0.4.7-2_all.deb to pool/main/h/hal/hal-device-manager_0.4.7-2_all.deb hal-doc_0.4.7-2_all.deb to pool/main/h/hal/hal-doc_0.4.7-2_all.deb hal_0.4.7-2.diff.gz to pool/main/h/hal/hal_0.4.7-2.diff.gz hal_0.4.7-2.dsc to pool/main/h/hal/hal_0.4.7-2.dsc hal_0.4.7-2_powerpc.deb to pool/main/h/hal/hal_0.4.7-2_powerpc.deb libhal-dev_0.4.7-2_powerpc.deb to pool/main/h/hal/libhal-dev_0.4.7-2_powerpc.deb libhal-storage-dev_0.4.7-2_powerpc.deb to pool/main/h/hal/libhal-storage-dev_0.4.7-2_powerpc.deb libhal-storage0_0.4.7-2_powerpc.deb to pool/main/h/hal/libhal-storage0_0.4.7-2_powerpc.deb libhal0_0.4.7-2_powerpc.deb to pool/main/h/hal/libhal0_0.4.7-2_powerpc.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted rasqal 0.9.6-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 15 Feb 2005 12:30:23 + Source: rasqal Binary: rasqal-utils librasqal0-dev librasqal0 Architecture: source i386 Version: 0.9.6-2 Distribution: unstable Urgency: low Maintainer: Dave Beckett [EMAIL PROTECTED] Changed-By: Dave Beckett [EMAIL PROTECTED] Description: librasqal0 - Rasqal RDF query library librasqal0-dev - Rasqal RDF query library development libraries and headers rasqal-utils - Rasqal RDF Query utilities Changes: rasqal (0.9.6-2) unstable; urgency=low . * Patch from CVS to tidy up resources when query results are not all fully read. Files: b971681ef0d20e6d0d8aaef6c00bbed7 652 devel optional rasqal_0.9.6-2.dsc ff84ce6e4f54345ef1271e34a6a1f03f 28791 devel optional rasqal_0.9.6-2.diff.gz c45e470cb2c5742ce7d63b1afdcb3921 114992 libdevel optional librasqal0-dev_0.9.6-2_i386.deb a3bd0ea051a75c6807452c4493e1fbda 93048 libs optional librasqal0_0.9.6-2_i386.deb 2c75f9ad72282a2b00d553281a29a3d3 51558 text optional rasqal-utils_0.9.6-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCEevCQ+ySUE9xlVoRAm3nAKCIc0/S5eqIqgI0x818vE0uHUyx/wCeMBMc xqTROe8pB1uyc2x13jAgbjM= =4oXr -END PGP SIGNATURE- Accepted: librasqal0-dev_0.9.6-2_i386.deb to pool/main/r/rasqal/librasqal0-dev_0.9.6-2_i386.deb librasqal0_0.9.6-2_i386.deb to pool/main/r/rasqal/librasqal0_0.9.6-2_i386.deb rasqal-utils_0.9.6-2_i386.deb to pool/main/r/rasqal/rasqal-utils_0.9.6-2_i386.deb rasqal_0.9.6-2.diff.gz to pool/main/r/rasqal/rasqal_0.9.6-2.diff.gz rasqal_0.9.6-2.dsc to pool/main/r/rasqal/rasqal_0.9.6-2.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted blootbot 1.1.0-6 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 15 Feb 2005 13:34:14 + Source: blootbot Binary: blootbot Architecture: source all Version: 1.1.0-6 Distribution: unstable Urgency: low Maintainer: Debian QA Group [EMAIL PROTECTED] Changed-By: Stephen Quinney [EMAIL PROTECTED] Description: blootbot - a severely modified infobot for IRC Changes: blootbot (1.1.0-6) unstable; urgency=low . * QA Upload * Changed Maintainer to Debian QA Group [EMAIL PROTECTED] Files: 39b384716386043d709269afef1d5d5c 579 net optional blootbot_1.1.0-6.dsc f9fc3962119f8ea5ea0c0428907689be 18835 net optional blootbot_1.1.0-6.diff.gz 8acdac30007d3d44872e818023dd9a4c 241594 net optional blootbot_1.1.0-6_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCEfveITGblEwaW+URAm6GAJ9FUug9d9GMJidEVh5U8RLOoyPB5QCeLuOq 4L28CrUWQAsGVZd66wEqxwM= =1zgp -END PGP SIGNATURE- Accepted: blootbot_1.1.0-6.diff.gz to pool/main/b/blootbot/blootbot_1.1.0-6.diff.gz blootbot_1.1.0-6.dsc to pool/main/b/blootbot/blootbot_1.1.0-6.dsc blootbot_1.1.0-6_all.deb to pool/main/b/blootbot/blootbot_1.1.0-6_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted beecrypt 2.2.0-pre1-4 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 15 Feb 2005 13:42:55 + Source: beecrypt Binary: beecrypt2-dev beecrypt2 Architecture: source i386 Version: 2.2.0-pre1-4 Distribution: unstable Urgency: low Maintainer: Debian QA Group [EMAIL PROTECTED] Changed-By: Stephen Quinney [EMAIL PROTECTED] Description: beecrypt2 - An open source C library of cryptographic algorithms. beecrypt2-dev - Header files for beecrypt, a library of cryptographic algorithms. Changes: beecrypt (2.2.0-pre1-4) unstable; urgency=low . * QA Upload * Changed Maintainer to Debian QA Group [EMAIL PROTECTED] Files: e3224bca25f2fb34c950e993ba9929c9 624 devel optional beecrypt_2.2.0-pre1-4.dsc b26a6ee6dccec50099a40562a734b165 17726 devel optional beecrypt_2.2.0-pre1-4.diff.gz c7f504c26fda89a69c07382a351808f4 103288 devel optional beecrypt2-dev_2.2.0-pre1-4_i386.deb 0f0e81121aa0046e7b5e6cfa000ee6ab 67536 devel optional beecrypt2_2.2.0-pre1-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCEf0yITGblEwaW+URAofLAKC7U6fgyZjFiWLIU5O+GdF6REWpPgCggeUk biMycI/nf8+UpgFBLVox+dE= =kOtQ -END PGP SIGNATURE- Accepted: beecrypt2-dev_2.2.0-pre1-4_i386.deb to pool/main/b/beecrypt/beecrypt2-dev_2.2.0-pre1-4_i386.deb beecrypt2_2.2.0-pre1-4_i386.deb to pool/main/b/beecrypt/beecrypt2_2.2.0-pre1-4_i386.deb beecrypt_2.2.0-pre1-4.diff.gz to pool/main/b/beecrypt/beecrypt_2.2.0-pre1-4.diff.gz beecrypt_2.2.0-pre1-4.dsc to pool/main/b/beecrypt/beecrypt_2.2.0-pre1-4.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted avifile 1:0.7.42.20050215-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 10 Jul 2003 13:40:44 +0200 Source: avifile Binary: avifile-divx-plugin libavifile-0.7c102 avifile-utils avifile-mad-plugin libavifile-0.7-dev avifile-vorbis-plugin avifile-win32-plugin avifile-xvid-plugin avifile-mjpeg-plugin avifile-player Architecture: source i386 Version: 1:0.7.42.20050215-1 Distribution: unstable Urgency: low Maintainer: Zdenek Kabelac [EMAIL PROTECTED] Changed-By: Zdenek Kabelac [EMAIL PROTECTED] Description: avifile-divx-plugin - Divx4Linux video encoding plugin avifile-mad-plugin - MAD - MPEG audio plugin avifile-mjpeg-plugin - MJPEG video plugin avifile-player - Video player for AVI/ASF/WMF files avifile-utils - Utility programs using the avifile library avifile-vorbis-plugin - Vorbis audio plugin avifile-win32-plugin - Win32 audio/video plugin avifile-xvid-plugin - XviD video encoding plugin libavifile-0.7-dev - Development header files libavifile-0.7c102 - Shared libraries for AVI read/writing Closes: 202627 228072 245653 253504 264543 267807 285677 294473 Changes: avifile (1:0.7.42.20050215-1) unstable; urgency=low . * fix libmad compilation for X86_64 (Closes: 253504) * quoted AM_PATH_AVIFILE (Closes: 267807) * unless I'm proven with buggy compiler output I'm closing this bug report as it compiles fine with current gcc-4.0 (Closes: 294473, 285677, 264543) * compiles fine with freetype2 (Closes: 228072) * removed compilation with qt2 (Closes: 245653) * name change fixed (Closes: 202627) Files: a5c9efca91b7c7a3a61911a032e71c30 1113 graphics optional avifile_0.7.42.20050215-1.dsc 864ce9c7d18ba93e1c4d433fad18961d 3180326 graphics optional avifile_0.7.42.20050215-1.tar.gz aa50597d5b6d0e177a33af76c289863d 1827630 libs optional libavifile-0.7c102_0.7.42.20050215-1_i386.deb 629fb75026481e0c35fcb044043e2ec6 48756 devel optional libavifile-0.7-dev_0.7.42.20050215-1_i386.deb 8ac8460286a147220da642d2b73b3222 64526 libs optional avifile-mad-plugin_0.7.42.20050215-1_i386.deb a046fa35abacd1d784879a9d356033d4 874 libs optional avifile-mjpeg-plugin_0.7.42.20050215-1_i386.deb 72b6c9121de28bb882395e80a918e01f 7260 libs optional avifile-vorbis-plugin_0.7.42.20050215-1_i386.deb dfc10b1d4a32116f5e33ad4f9de3d85a 93796 contrib/libs optional avifile-win32-plugin_0.7.42.20050215-1_i386.deb 69390327ea6256094d12f3a56c5c5506 896 contrib/libs optional avifile-xvid-plugin_0.7.42.20050215-1_i386.deb 303bdc1c9dc9c7b3ff151440926eac45 12726 contrib/libs optional avifile-divx-plugin_0.7.42.20050215-1_i386.deb 514ebb8bf4e288e858a6d868036ad7cf 110154 graphics extra avifile-player_0.7.42.20050215-1_i386.deb e76faaa0825a96ab6f7de1f11443549d 318452 graphics extra avifile-utils_0.7.42.20050215-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iQCVAwUBQhH+V1WWyMLXq+m5AQJL6QP+KTsnIqYNjckmSY5FW3RvgWETg6oslZfv 2upQFj3qxOYAKNq5iwE/tySCXWZD1a+BAACE9qftWIP1Z4eMloB1V1HLBuwN6xuh EOzjkRQoxU1J+xRUdTzZ/Gv70zH7q/7eAM44tKOcA+N91CO6cWFsFEgtRXbxB7/W HgqzRISCptg= =X4i/ -END PGP SIGNATURE- Accepted: avifile-divx-plugin_0.7.42.20050215-1_i386.deb to pool/contrib/a/avifile/avifile-divx-plugin_0.7.42.20050215-1_i386.deb avifile-mad-plugin_0.7.42.20050215-1_i386.deb to pool/main/a/avifile/avifile-mad-plugin_0.7.42.20050215-1_i386.deb avifile-mjpeg-plugin_0.7.42.20050215-1_i386.deb to pool/main/a/avifile/avifile-mjpeg-plugin_0.7.42.20050215-1_i386.deb avifile-player_0.7.42.20050215-1_i386.deb to pool/main/a/avifile/avifile-player_0.7.42.20050215-1_i386.deb avifile-utils_0.7.42.20050215-1_i386.deb to pool/main/a/avifile/avifile-utils_0.7.42.20050215-1_i386.deb avifile-vorbis-plugin_0.7.42.20050215-1_i386.deb to pool/main/a/avifile/avifile-vorbis-plugin_0.7.42.20050215-1_i386.deb avifile-win32-plugin_0.7.42.20050215-1_i386.deb to pool/contrib/a/avifile/avifile-win32-plugin_0.7.42.20050215-1_i386.deb avifile-xvid-plugin_0.7.42.20050215-1_i386.deb to pool/contrib/a/avifile/avifile-xvid-plugin_0.7.42.20050215-1_i386.deb avifile_0.7.42.20050215-1.dsc to pool/main/a/avifile/avifile_0.7.42.20050215-1.dsc avifile_0.7.42.20050215-1.tar.gz to pool/main/a/avifile/avifile_0.7.42.20050215-1.tar.gz libavifile-0.7-dev_0.7.42.20050215-1_i386.deb to pool/main/a/avifile/libavifile-0.7-dev_0.7.42.20050215-1_i386.deb libavifile-0.7c102_0.7.42.20050215-1_i386.deb to pool/main/a/avifile/libavifile-0.7c102_0.7.42.20050215-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted x10-automate 1.00-7 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 15 Feb 2005 13:50:51 + Source: x10-automate Binary: x10-automate Architecture: source all Version: 1.00-7 Distribution: unstable Urgency: low Maintainer: Debian QA Group [EMAIL PROTECTED] Changed-By: Stephen Quinney [EMAIL PROTECTED] Description: x10-automate - GUI interface for x10 power line control utility Changes: x10-automate (1.00-7) unstable; urgency=low . * QA Upload * Changed Maintainer to Debian QA Group [EMAIL PROTECTED] * debian/menu - Fixed quoting of values * debian/copyright - Added a pointer to the GPL2 license file. Files: 3a358da49bf2a594737b292c2aa56d3b 585 electronics optional x10-automate_1.00-7.dsc c79b13fce480d0c2b194d543fb037615 3593 electronics optional x10-automate_1.00-7.diff.gz 0d21b6478a39fa875110897ef3064d8b 101088 electronics optional x10-automate_1.00-7_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCEgB2ITGblEwaW+URAgbiAKCuu5gxwTCkrzEfWp125Wp/nXmCdwCgo6W1 m+r8YJ4aIBBsKRcxCNzb4YI= =waJL -END PGP SIGNATURE- Accepted: x10-automate_1.00-7.diff.gz to pool/main/x/x10-automate/x10-automate_1.00-7.diff.gz x10-automate_1.00-7.dsc to pool/main/x/x10-automate/x10-automate_1.00-7.dsc x10-automate_1.00-7_all.deb to pool/main/x/x10-automate/x10-automate_1.00-7_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted transcriber 1.5.1-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 15 Feb 2005 15:39:49 +0100 Source: transcriber Binary: transcriber Architecture: source i386 Version: 1.5.1-1 Distribution: unstable Urgency: low Maintainer: David A. van Leeuwen [EMAIL PROTECTED] Changed-By: David A. van Leeuwen [EMAIL PROTECTED] Description: transcriber - Transcribe speech data using an integrated editor Closes: 295314 Changes: transcriber (1.5.1-1) unstable; urgency=low . * Added Build-depends to libx11-dev, hopefully now (closes: #295314) Files: 5af6bbb269e1c59f9a5fb20889a00848 585 sound extra transcriber_1.5.1-1.dsc 67048339ce645a33935440dd09acfc9a 1100373 sound extra transcriber_1.5.1-1.tar.gz 63b20d07f230c23dc14d14b542102341 1074028 sound extra transcriber_1.5.1-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCEguuJrPWgQLzcTwRAkOnAJ4rDj3SB/sndxk/5AgbTxc3TiMmfACfSYxs X24RxMC+khPchvfVoL/ouzQ= =Gzbh -END PGP SIGNATURE- Accepted: transcriber_1.5.1-1.dsc to pool/main/t/transcriber/transcriber_1.5.1-1.dsc transcriber_1.5.1-1.tar.gz to pool/main/t/transcriber/transcriber_1.5.1-1.tar.gz transcriber_1.5.1-1_i386.deb to pool/main/t/transcriber/transcriber_1.5.1-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted t-prot 1.96-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 15 Feb 2005 15:12:57 +0100 Source: t-prot Binary: t-prot Architecture: source all Version: 1.96-1 Distribution: unstable Urgency: low Maintainer: Gerfried Fuchs [EMAIL PROTECTED] Changed-By: Gerfried Fuchs [EMAIL PROTECTED] Description: t-prot - display filter for RFC822 messages Changes: t-prot (1.96-1) unstable; urgency=low . * New upstream release: v2.0 pre-release, uses Locale::gettext from now on. Added a note to NEWS.Debian.gz about this. * debconf removed from Depends, forgotten. * Change long description a bit. Files: 4c26c9f107b9b65e70f7343395f7030a 552 mail extra t-prot_1.96-1.dsc 60deca8af7c9dc074289bfd653445fd9 36490 mail extra t-prot_1.96.orig.tar.gz 20693aa3d9725bb2fb1c5b2f0aebcb71 8397 mail extra t-prot_1.96-1.diff.gz 0108f694674053a0d521bcc290029df0 46976 mail extra t-prot_1.96-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iEYEARECAAYFAkISCdoACgkQELuA/Ba9d8Z3fwCfbcK7zUDde7iNzpkeI8sDFhZC mgIAn0s3NDfLMDaHFjE5zYorbrom+wV0 =zcF1 -END PGP SIGNATURE- Accepted: t-prot_1.96-1.diff.gz to pool/main/t/t-prot/t-prot_1.96-1.diff.gz t-prot_1.96-1.dsc to pool/main/t/t-prot/t-prot_1.96-1.dsc t-prot_1.96-1_all.deb to pool/main/t/t-prot/t-prot_1.96-1_all.deb t-prot_1.96.orig.tar.gz to pool/main/t/t-prot/t-prot_1.96.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted tla-tools 2005.0.patch.4-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 15 Feb 2005 08:59:49 -0600 Source: tla-tools Binary: tla-tools Architecture: source all Version: 2005.0.patch.4-1 Distribution: unstable Urgency: low Maintainer: John Goerzen [EMAIL PROTECTED] Changed-By: John Goerzen [EMAIL PROTECTED] Description: tla-tools - Utilities to make life with GNU Arch (tla) easier Closes: 277509 Changes: tla-tools (2005.0.patch.4-1) unstable; urgency=low . * New upstream release. Closes: #277509. Files: 8906e593ca773efd860828aa53a4f897 636 devel optional tla-tools_2005.0.patch.4-1.dsc baf7ec9a0fcc7eb7d5f0d3fdfb41fabe 62457 devel optional tla-tools_2005.0.patch.4.orig.tar.gz 6aaaf917ee80cf1fcbc57356c7546fc4 26423 devel optional tla-tools_2005.0.patch.4-1.diff.gz b65286ac893642ee4569d0c53eac3161 46218 devel optional tla-tools_2005.0.patch.4-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCEg+h7B2mSKdID5ERAgZqAJ9bs8YfpteTB9VUZ5Nh9zwLKZ/20wCgn6dU E1KDxRNMYAU5nYirWEp4cag= =tylh -END PGP SIGNATURE- Accepted: tla-tools_2005.0.patch.4-1.diff.gz to pool/main/t/tla-tools/tla-tools_2005.0.patch.4-1.diff.gz tla-tools_2005.0.patch.4-1.dsc to pool/main/t/tla-tools/tla-tools_2005.0.patch.4-1.dsc tla-tools_2005.0.patch.4-1_all.deb to pool/main/t/tla-tools/tla-tools_2005.0.patch.4-1_all.deb tla-tools_2005.0.patch.4.orig.tar.gz to pool/main/t/tla-tools/tla-tools_2005.0.patch.4.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cassbeam 1.0-5 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 12 Feb 2005 14:22:03 -0500 Source: cassbeam Binary: cassbeam Architecture: source i386 Version: 1.0-5 Distribution: unstable Urgency: low Maintainer: Brian R Furry [EMAIL PROTECTED] Changed-By: Brian R Furry [EMAIL PROTECTED] Description: cassbeam - A program for Cassegrain antenna modelling Closes: 294261 Changes: cassbeam (1.0-5) unstable; urgency=low . * Added more useful information to the package description; Closes: #294261 * Added 'dh_install' to install target of the debian/rules file instead of using '$(MAKE) install prefix=$$(pwd)/debian/cassbeam/usr' Files: db294a800d373c5dfd8c52dee35e 630 science optional cassbeam_1.0-5.dsc 02ca24432bca1419483ec6594c28a153 42150 science optional cassbeam_1.0-5.diff.gz 9644ac94b1d4e6f2385971fb6209f150 294024 science optional cassbeam_1.0-5_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCEhkF7qLvonfc4IMRAvcjAKCUjCHtRLtQIpINiv9tbnZN+346DwCgk4OH 6mGG2gdavh4q5p82677mOe4= =/bEe -END PGP SIGNATURE- Accepted: cassbeam_1.0-5.diff.gz to pool/main/c/cassbeam/cassbeam_1.0-5.diff.gz cassbeam_1.0-5.dsc to pool/main/c/cassbeam/cassbeam_1.0-5.dsc cassbeam_1.0-5_i386.deb to pool/main/c/cassbeam/cassbeam_1.0-5_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted aspell 0.60.2-1 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 13 Feb 2005 10:12:39 -0800 Source: aspell Binary: libpspell-dev libaspell15 aspell libaspell-dev aspell-doc aspell-bin Architecture: source i386 all Version: 0.60.2-1 Distribution: unstable Urgency: low Maintainer: Brian Nelson [EMAIL PROTECTED] Changed-By: Brian Nelson [EMAIL PROTECTED] Description: aspell - GNU Aspell spell-checker aspell-bin - GNU Aspell standalone spell-check utilities aspell-doc - Documentation for GNU Aspell spell-checker libaspell-dev - Development files for applications with GNU Aspell support libaspell15 - The GNU Aspell spell-checker runtime toolkits libpspell-dev - Development files for applications with pspell support Closes: 131328 170458 228237 236823 261589 274514 Changes: aspell (0.60.2-1) unstable; urgency=low . * New upstream release (Closes: #274514) - support for UTF-8 and other encodings (Closes: #131328, #170458) - affix compression support - manual converted to texinfo - loadable filter support - fixes --conf and --per-conf options (Closes: #228237) - fixes abort when --extra-dicts is used (Closes: #236823) - fixes infinite loop when trying to replace a word with the identical text (Closes: #261589) * debian/rules: converted to use cdbs * debian/control: added build-dep on cdbs * debian/control: removed Build-Depends-Indep because the manual no longer needs to be generated * Removed Debian-specific manpages, as these have now been included upstream. * debian/control: Depend on aspell-en | aspell6-dictionary, since the dictionary format has changed again. Made libaspell15 conflict with aspell-dictionary, since dictionaries in that format are no longer usable. * Removed doc-base support since only the texinfo manuals are installed now. Upstream still includes html documentation, though it's not installed in the install target, so it would be possible to resurrect if there's demand for it. * Eased the shlibs dependency tightness on libaspell15 by specifying a dependency of = 0.60, instead of the full 0.60.x version. Upstream uses proper versioning and won't change the API in 0.60.x releases, so this should be a safe setting. Files: bf9f15b86495b100522b4bcf372cbd1c 677 text optional aspell_0.60.2-1.dsc d067596a1d9029d127d85e5040bab0ab 1577570 text optional aspell_0.60.2.orig.tar.gz 970deaf0987c0c5137db4eb93bc8cc2c 15948 text optional aspell_0.60.2-1.diff.gz 7b165be1ac5a0bc6c6f2875c5c316c03 15516 text optional aspell_0.60.2-1_all.deb 294352d2d91167e817569721c59d0b21 127210 doc optional aspell-doc_0.60.2-1_all.deb 8987994ae0aa6c1f6842e7f05abb4b10 213490 text optional aspell-bin_0.60.2-1_i386.deb e8a112f64ea99ab44b07e4661e2574d8 666590 libs optional libaspell15_0.60.2-1_i386.deb 61fb3c3d03b7525ed63b670d05e98aff 20706 libdevel optional libaspell-dev_0.60.2-1_i386.deb 298c37a924166108d2327ab290672055 17756 libdevel optional libpspell-dev_0.60.2-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCD52R1Ng1YWbyRSERAik3AJ4+Vrcb2jGfxIa3dWiFfkizLWOwUACeN4bl 9YOZeepyInw01VPXTj8xLl0= =UQB6 -END PGP SIGNATURE- Accepted: aspell-bin_0.60.2-1_i386.deb to pool/main/a/aspell/aspell-bin_0.60.2-1_i386.deb aspell-doc_0.60.2-1_all.deb to pool/main/a/aspell/aspell-doc_0.60.2-1_all.deb aspell_0.60.2-1.diff.gz to pool/main/a/aspell/aspell_0.60.2-1.diff.gz aspell_0.60.2-1.dsc to pool/main/a/aspell/aspell_0.60.2-1.dsc aspell_0.60.2-1_all.deb to pool/main/a/aspell/aspell_0.60.2-1_all.deb aspell_0.60.2.orig.tar.gz to pool/main/a/aspell/aspell_0.60.2.orig.tar.gz libaspell-dev_0.60.2-1_i386.deb to pool/main/a/aspell/libaspell-dev_0.60.2-1_i386.deb libaspell15_0.60.2-1_i386.deb to pool/main/a/aspell/libaspell15_0.60.2-1_i386.deb libpspell-dev_0.60.2-1_i386.deb to pool/main/a/aspell/libpspell-dev_0.60.2-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted aspell-br 0.50-2-4 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 21 Jan 2005 10:39:02 -0800 Source: aspell-br Binary: aspell-br Architecture: source i386 Version: 0.50-2-4 Distribution: unstable Urgency: low Maintainer: Brian Nelson [EMAIL PROTECTED] Changed-By: Brian Nelson [EMAIL PROTECTED] Description: aspell-br - Breton dictionary for GNU Aspell Changes: aspell-br (0.50-2-4) unstable; urgency=low . * Support Aspell 0.60 - debian/control: build-depend on aspell-bin ( 0.60) - debian/control: provide aspell6-dictionary Files: d72c4b6ec885131dcfbe5f56328e957d 607 text optional aspell-br_0.50-2-4.dsc 94c034535e33575b28f2ecd8d714e9b4 1215 text optional aspell-br_0.50-2-4.diff.gz bc6e66b17c62502278fea1070ebe33be 394028 text optional aspell-br_0.50-2-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCC58Y1Ng1YWbyRSERAsNOAJ9MRsJRPC8uUv0MhnMsOq45rSmpbwCeJYgR 40xHZqgfYq3GV1dsXjdUhsk= =eqzF -END PGP SIGNATURE- Accepted: aspell-br_0.50-2-4.diff.gz to pool/main/a/aspell-br/aspell-br_0.50-2-4.diff.gz aspell-br_0.50-2-4.dsc to pool/main/a/aspell-br/aspell-br_0.50-2-4.dsc aspell-br_0.50-2-4_i386.deb to pool/main/a/aspell-br/aspell-br_0.50-2-4_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted aspell-cy 0.50-3-4 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 21 Jan 2005 10:39:49 -0800 Source: aspell-cy Binary: aspell-cy Architecture: source i386 Version: 0.50-3-4 Distribution: unstable Urgency: low Maintainer: Brian Nelson [EMAIL PROTECTED] Changed-By: Brian Nelson [EMAIL PROTECTED] Description: aspell-cy - Welsh dictionary for GNU Aspell Changes: aspell-cy (0.50-3-4) unstable; urgency=low . * Support Aspell 0.60 - debian/control: build-depend on aspell-bin ( 0.60) - debian/control: provide aspell6-dictionary Files: 4a12373e3de41f444f75741c9540e3c4 608 text optional aspell-cy_0.50-3-4.dsc 83f85941d926e67eae1cb9c3907c215f 1213 text optional aspell-cy_0.50-3-4.diff.gz ebbca1c97e050c96d8a1e7090d95ec46 2332446 text optional aspell-cy_0.50-3-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCC58h1Ng1YWbyRSERApdqAJoCEWghxG1tSuExzpkQp6zW/CiJxgCfeeD3 Sjdp87OHyPvEKcEA+IlFzo8= =l0TY -END PGP SIGNATURE- Accepted: aspell-cy_0.50-3-4.diff.gz to pool/main/a/aspell-cy/aspell-cy_0.50-3-4.diff.gz aspell-cy_0.50-3-4.dsc to pool/main/a/aspell-cy/aspell-cy_0.50-3-4.dsc aspell-cy_0.50-3-4_i386.deb to pool/main/a/aspell-cy/aspell-cy_0.50-3-4_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted autofs 4.1.3+4.1.4beta2-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 15 Feb 2005 17:32:59 +0100 Source: autofs Binary: autofs-hesiod autofs-ldap autofs Architecture: source i386 Version: 4.1.3+4.1.4beta2-1 Distribution: unstable Urgency: high Maintainer: Steinar H. Gunderson [EMAIL PROTECTED] Changed-By: Steinar H. Gunderson [EMAIL PROTECTED] Description: autofs - A kernel-based automounter for Linux autofs-hesiod - Hesiod map support for autofs autofs-ldap - LDAP map support for autofs Closes: 292762 Changes: autofs (4.1.3+4.1.4beta2-1) unstable; urgency=high . * Urgency=high as previous versions were broken with regard to upgrading (ie. a non-reported RC bug; see below). * New upstream release, includes and thus obsoletes almost all Debian-specific patches. (Thanks! :-) ) For reference, patches that were not deleted: - 020_auto_net_path_sortlocale_mountoptions: changed (removed last bugfixes as they are already there, kept option changes). - 037_let_debian_rules_decide_on_CFLAGS: kept. - 042_default_auto_master_all_commented_out: kept, adapted so it applies against new version. * Update debian/script/vars to reflect the new upstream version. * New patch 052_292762_dont_lsmod_on_monolithic_kernels: Init script now works properly on monolithic kernels. (Closes: #292762) * build_dir/TODO doesn't exist anymore, remove from debian/docs. * There is now a README.gentoo, so don't include README* in debian/docs, include each element by itself. * Stop autofs in prerm again, so upgrades actually work cleanly even if the inode of /usr/sbin/automount was changed; there is now a new flag AUTOFS_DONT_RESTART_ON_UPGRADES you can set in /etc/default/autofs to suppress the restart on upgrade if you need manual treatment of this. * If upgrading from 4.1.3-[56789], which had the broken behaviour of not stopping in prerm, stop autofs in preinst. Unfortunately, if there has been more than one of these versions installed without reboot (e.g. installed -8, upgraded to -9), /etc/init.d/autofs stop might be broken, so we'll display a debconf notice and let the administrator clean up. (Add dh_installdebconf to debian/rules for this.) * lintian (and Tollef) complained that the debconf note was not properly internationalized, so add dependency on po-debconf and run debconf-gettextize so it is internationalizable. Files: fc36e3cca5272bbe8dd2668727dcc5e0 673 utils extra autofs_4.1.3+4.1.4beta2-1.dsc 1a2907d385368a07b04bec25af4717ee 261133 utils extra autofs_4.1.3+4.1.4beta2.orig.tar.gz 65d1fabe6c40e09fae9bf8a2a554bc6b 28400 utils extra autofs_4.1.3+4.1.4beta2-1.diff.gz c261c9d8f49309b15599c69bf6178196 103952 utils extra autofs_4.1.3+4.1.4beta2-1_i386.deb 3411df23d4d13c21f321e0256656b348 22654 utils extra autofs-hesiod_4.1.3+4.1.4beta2-1_i386.deb e7bc1ddca42e7dfa0952592a3d69b97b 34736 utils extra autofs-ldap_4.1.3+4.1.4beta2-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCEic/XKRQ3lK3SH4RAmx4AKCcDD/Io8ixCwWM+m3EDdLjTFKejACcCNC4 7khpDESyEitwN8bti/40fn4= =DzVc -END PGP SIGNATURE- Accepted: autofs-hesiod_4.1.3+4.1.4beta2-1_i386.deb to pool/main/a/autofs/autofs-hesiod_4.1.3+4.1.4beta2-1_i386.deb autofs-ldap_4.1.3+4.1.4beta2-1_i386.deb to pool/main/a/autofs/autofs-ldap_4.1.3+4.1.4beta2-1_i386.deb autofs_4.1.3+4.1.4beta2-1.diff.gz to pool/main/a/autofs/autofs_4.1.3+4.1.4beta2-1.diff.gz autofs_4.1.3+4.1.4beta2-1.dsc to pool/main/a/autofs/autofs_4.1.3+4.1.4beta2-1.dsc autofs_4.1.3+4.1.4beta2-1_i386.deb to pool/main/a/autofs/autofs_4.1.3+4.1.4beta2-1_i386.deb autofs_4.1.3+4.1.4beta2.orig.tar.gz to pool/main/a/autofs/autofs_4.1.3+4.1.4beta2.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted aspell-pt 0.50-2-4 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 22 Jan 2005 14:56:26 +0100 Source: aspell-pt Binary: aspell-pt aspell-pt-common Architecture: source i386 Version: 0.50-2-4 Distribution: unstable Urgency: low Maintainer: Rafael Laboissiere [EMAIL PROTECTED] Changed-By: Rafael Laboissiere [EMAIL PROTECTED] Description: aspell-pt - European Portuguese dictionary for GNU Aspell aspell-pt-common - Portuguese dictionary for GNU Aspell (common files) Changes: aspell-pt (0.50-2-4) unstable; urgency=low . * Built against aspell 0.60.2. * debian/control: - Changed the build-depends to aspell-bin ( 0.60). - Changed the aspell-pt provides from aspell-dictionary to aspell6-dictionary. Dropped provides from aspell-pt-common. - Removed the word The at the beginning of the short descriptions, as per Section 6.2.2 of the Debian Developer's Reference. * debian/aspell-pt.files: Adjusted new library directory to /usr/lib/aspell-0.60 Files: e008e4e3a56b5212b0b21376103d80b2 617 text optional aspell-pt_0.50-2-4.dsc e49dc677ad8453e17b331f41b22ef65c 2200 text optional aspell-pt_0.50-2-4.diff.gz 055940d792f37907427ca6c31632f4c0 1353064 text optional aspell-pt-common_0.50-2-4_i386.deb 28db2acdabf1f5be565497522d1fc214 1296878 text optional aspell-pt_0.50-2-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFCDbs6k3oga0pdcv4RApFlAJ4uOoIGaACKypuom3kci1AeiphCvgCeOZMg lfNwyZaEs3QR9hvjA+rdImc= =CCGT -END PGP SIGNATURE- Accepted: aspell-pt-common_0.50-2-4_i386.deb to pool/main/a/aspell-pt/aspell-pt-common_0.50-2-4_i386.deb aspell-pt_0.50-2-4.diff.gz to pool/main/a/aspell-pt/aspell-pt_0.50-2-4.diff.gz aspell-pt_0.50-2-4.dsc to pool/main/a/aspell-pt/aspell-pt_0.50-2-4.dsc aspell-pt_0.50-2-4_i386.deb to pool/main/a/aspell-pt/aspell-pt_0.50-2-4_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted aspell-ga 0.50-4-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 21 Jan 2005 10:45:23 -0800 Source: aspell-ga Binary: aspell-ga Architecture: source i386 Version: 0.50-4-2 Distribution: unstable Urgency: low Maintainer: Brian Nelson [EMAIL PROTECTED] Changed-By: Brian Nelson [EMAIL PROTECTED] Description: aspell-ga - Irish (Gaeilge) dictionary for GNU Aspell Changes: aspell-ga (0.50-4-2) unstable; urgency=low . * Support Aspell 0.60 - debian/control: build-depend on aspell-bin ( 0.60) - debian/control: provide aspell6-dictionary Files: 1569fd322d1b1db4bf24f8dda31a04bf 608 text optional aspell-ga_0.50-4-2.dsc 48d53471381a9e5af2597c297bda7851 1342 text optional aspell-ga_0.50-4-2.diff.gz cfe0eb3fb3f4a71626c65575e91ff8a6 2740916 text optional aspell-ga_0.50-4-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCC5881Ng1YWbyRSERAhJJAJ9jttTzjIITvj4JA+DhkF9iszxOVwCgl8eE MNGz34kve11d0ispaY3osik= =7JL4 -END PGP SIGNATURE- Accepted: aspell-ga_0.50-4-2.diff.gz to pool/main/a/aspell-ga/aspell-ga_0.50-4-2.diff.gz aspell-ga_0.50-4-2.dsc to pool/main/a/aspell-ga/aspell-ga_0.50-4-2.dsc aspell-ga_0.50-4-2_i386.deb to pool/main/a/aspell-ga/aspell-ga_0.50-4-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted aspell-en 6.0-0-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 12 Feb 2005 12:37:03 -0800 Source: aspell-en Binary: aspell-en Architecture: source i386 Version: 6.0-0-1 Distribution: unstable Urgency: low Maintainer: Brian Nelson [EMAIL PROTECTED] Changed-By: Brian Nelson [EMAIL PROTECTED] Description: aspell-en - English dictionary for GNU Aspell Changes: aspell-en (6.0-0-1) unstable; urgency=low . * New upstream version * debian/control: provide aspell6-dictionary, and build-depend on aspell ( 0.60). This transitions the package to the new Aspell 0.60. * debian/rules: remove the generated Makefile in the clean target * Added support for dictionary registration in dictionaries-common. * debian/control: added a corresponding build dependency on dictionaries-common-dev and a runtime dependency on dictionaries-common. Files: f3a6dea177be58afe1d11a7d6c893a00 641 text optional aspell-en_6.0-0-1.dsc 3eaf6620a09622fad1cfe2d93c68ea4a 230563 text optional aspell-en_6.0-0.orig.tar.gz cc5f7a17793c4a691f4dcb5a3e43271f 5048 text optional aspell-en_6.0-0-1.diff.gz 820d381ca60981de1713c25ecd516ba9 1616956 text optional aspell-en_6.0-0-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD4DBQFCDmoE1Ng1YWbyRSERAu8EAKCHD1fRn518KOUKwpWMRHqFnTGRoACXYyYg uDYcSnjlfMi9qZJhSyK7TA== =J39w -END PGP SIGNATURE- Accepted: aspell-en_6.0-0-1.diff.gz to pool/main/a/aspell-en/aspell-en_6.0-0-1.diff.gz aspell-en_6.0-0-1.dsc to pool/main/a/aspell-en/aspell-en_6.0-0-1.dsc aspell-en_6.0-0-1_i386.deb to pool/main/a/aspell-en/aspell-en_6.0-0-1_i386.deb aspell-en_6.0-0.orig.tar.gz to pool/main/a/aspell-en/aspell-en_6.0-0.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted aspell-el 0.50-3-4 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 21 Jan 2005 10:41:30 -0800 Source: aspell-el Binary: aspell-el Architecture: source i386 Version: 0.50-3-4 Distribution: unstable Urgency: low Maintainer: Brian Nelson [EMAIL PROTECTED] Changed-By: Brian Nelson [EMAIL PROTECTED] Description: aspell-el - Greek dictionary for GNU Aspell Changes: aspell-el (0.50-3-4) unstable; urgency=low . * Support Aspell 0.60 - debian/control: build-depend on aspell-bin ( 0.60) - debian/control: provide aspell6-dictionary Files: 10d308b2a26722a4b05e5ee8901ad45c 608 text optional aspell-el_0.50-3-4.dsc 27862a2b7d22bfb9bc9063ba3208e6e8 1224 text optional aspell-el_0.50-3-4.diff.gz 4d27677ad136452c79955cc1f8b2 4694686 text optional aspell-el_0.50-3-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCC58q1Ng1YWbyRSERAqZCAJ0YtiwNi0A9XP2TW9qKDkkxdTv36wCfRlYu cBCgJePRjAYb9rixq7s9PdU= =x4gu -END PGP SIGNATURE- Accepted: aspell-el_0.50-3-4.diff.gz to pool/main/a/aspell-el/aspell-el_0.50-3-4.diff.gz aspell-el_0.50-3-4.dsc to pool/main/a/aspell-el/aspell-el_0.50-3-4.dsc aspell-el_0.50-3-4_i386.deb to pool/main/a/aspell-el/aspell-el_0.50-3-4_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted aspell-sk 0.52-0-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 21 Jan 2005 10:46:27 -0800 Source: aspell-sk Binary: aspell-sk Architecture: source i386 Version: 0.52-0-2 Distribution: unstable Urgency: low Maintainer: Brian Nelson [EMAIL PROTECTED] Changed-By: Brian Nelson [EMAIL PROTECTED] Description: aspell-sk - Slovak dictionary for GNU Aspell Changes: aspell-sk (0.52-0-2) unstable; urgency=low . * Support Aspell 0.60 - debian/control: build-depend on aspell-bin ( 0.60) - debian/control: provide aspell6-dictionary Files: 805e49b680a8b8658a3d0840cef1379d 608 text optional aspell-sk_0.52-0-2.dsc 5370f3d2b4f8d95c911fd52cef996d84 1726 text optional aspell-sk_0.52-0-2.diff.gz 43d17249a3311787dd8f8462b05b9898 5960468 text optional aspell-sk_0.52-0-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCC59E1Ng1YWbyRSERAi/YAJ45aCCEVov/TrfAwfFkFcCYqHJ5rQCghLCB 0xY1v1bXUPx70D+T3KbXxvY= =1jc/ -END PGP SIGNATURE- Accepted: aspell-sk_0.52-0-2.diff.gz to pool/main/a/aspell-sk/aspell-sk_0.52-0-2.diff.gz aspell-sk_0.52-0-2.dsc to pool/main/a/aspell-sk/aspell-sk_0.52-0-2.dsc aspell-sk_0.52-0-2_i386.deb to pool/main/a/aspell-sk/aspell-sk_0.52-0-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted aspell-ukr 0.51-0-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 21 Jan 2005 10:47:31 -0800 Source: aspell-ukr Binary: aspell-ukr Architecture: source i386 Version: 0.51-0-2 Distribution: unstable Urgency: low Maintainer: Brian Nelson [EMAIL PROTECTED] Changed-By: Brian Nelson [EMAIL PROTECTED] Description: aspell-ukr - Ukrainian dictionary for GNU Aspell Changes: aspell-ukr (0.51-0-2) unstable; urgency=low . * Support Aspell 0.60 - debian/control: build-depend on aspell-bin ( 0.60) - debian/control: provide aspell6-dictionary Files: 07e0936b287338d00fe895f38b7783cd 612 text optional aspell-ukr_0.51-0-2.dsc 64bd55832df5280b30432d853a85dafb 1329 text optional aspell-ukr_0.51-0-2.diff.gz e1934684aedf46dc11a682022826d6f1 6012130 text optional aspell-ukr_0.51-0-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCC59O1Ng1YWbyRSERAlCIAJ4xOqDbC2MyUl1t5QHFQhQ+XieyAwCfQ/F2 aqRp2hgT0kBin0L8FXGhVHA= =Uhyz -END PGP SIGNATURE- Accepted: aspell-ukr_0.51-0-2.diff.gz to pool/main/a/aspell-ukr/aspell-ukr_0.51-0-2.diff.gz aspell-ukr_0.51-0-2.dsc to pool/main/a/aspell-ukr/aspell-ukr_0.51-0-2.dsc aspell-ukr_0.51-0-2_i386.deb to pool/main/a/aspell-ukr/aspell-ukr_0.51-0-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
