Question sur les bugs
Bonjour, une question certainement idiote : pourquoi, y'a-t-il de nombreux très vieux bugs non fermés, concernant des versions de logiciels tellement anciennes qu'ils ne semblent plus applicables (paquets plus disponibles dans la version du bug rapporté) ? J'ai trouvé quelques débats là dessus, des propositions d'archivages, de scripts, ... mais pas d'avis de mainteneurs sur le pourquoi du comment. Peut-on proposer, de façon raisonnable, la fermeture de certains de ces bugs ? Je sais que c'est techniquement possible, ce qui m'intéresse, c'est vos avis de mainteneurs. Quelles assurances doit-on prendre avant de proposer la fermeture d'un vieux bug de ce type ? exemple : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=108678 qui concerne kdevelop 1.4 avec qt 2.2 du 14 août 2001 (je fais joujou avec kdevelop qui vient de planter 4 fois d'affilée sur le même problème d'où mon intérêt pour ses bugs :-) note : ce n'est qu'un exemple, je ne demande pas d'aide pour kdevelop.) merci d'avance pour vos réponses, -- = Alain Cabiran -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Question sur les bugs
Christian Perrier wrote: Quoting Alain Cabiran ([EMAIL PROTECTED]): Bonjour, une question certainement idiote : pourquoi, y'a-t-il de nombreux très vieux bugs non fermés, concernant des versions de logiciels tellement anciennes qu'ils ne semblent plus applicables (paquets plus disponibles dans la version du bug rapporté) ? Une des raisons essentielles est souvent la manque de ressources de la part du mainteneur pour maintenir la base de bogues dans un état de propreté correct. OK... J'en déduis que c'est pour cela qu'apt-listbugs me ressort souvent de faux bugs - genre un problème de sécurité que justement la MAJ corrige ou qui ne concerne qu'une architecture/version (je suis en Sid et les pbs affectant l'installation sur woody ou Sarge me concernent assez peu ;) La plupart apprécieront donc certainement de l'aide sur ce sujet et c'est d'ailleurs un des domaines où les non DD peuvent le plus facilement aider (avec la traduction...). Aïe ! Je n'ai déjà malheureusement même plus le temps d'aider aux relectures des traductions, alors l'examen des vieux bogues et leur fermeture... :( Une autre raison sont souvent les bogues corrigés dans testing et unstable, mais pas dans woody. Ceux-ci doivent être marqués woody mais pas fermés, en toute logique. Cela peut expliquer de très nombreux bogues ouverts qui seront fermés dès que sarge sera publiée (ce coup là, on y est...). Comme je ne suis pas du tout programmeur, j'énonce peut-être une énormité, mais ne serait-il pas possible qu'apt-listbugs ne ressorte que les bugs pour l'architecture/version qu'on utilise ? (grosso modo, il suffirait d'un tag architecture : i386/mipsel/sparc etc. et d'un autre pour Woody, Sarge, Sid - ce dernier semblant déjà exister). Cela pourrait permettre un certain gain en bande passante sur les serveurs et miroirs, je pense : actuellement, on télécharge les paquets puis apt-lisbugs annonce la couleur et on choisit ou non d'installer le paquet. Mais à ce moment-là, on l'a déjà téléchargé (sauf erreur grossière de ma part ;) Ceci étant, je suis bien conscient que ce n'est certainement pas si simple que cela à réaliser :-D Mais, en résumé, une aide aux mainteneurs pour faire ce genre de tri peut être très appréciée. Fais gaffe, c'est pile comme ça qu'on se retrouve co-mainteneur...:-) Ah, si j'avais un peu de temps libre... :) -- Amicalement, Claude Thomassin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Question sur les bugs
Le Sat, 04 Jun 2005 13:24:18 +0200, claude a écrit : Christian Perrier wrote: Quoting Alain Cabiran ([EMAIL PROTECTED]): Comme je ne suis pas du tout programmeur, j'énonce peut-être une énormité, mais ne serait-il pas possible qu'apt-listbugs ne ressorte que les bugs pour l'architecture/version qu'on utilise ? (grosso modo, il suffirait d'un tag architecture : i386/mipsel/sparc etc. et d'un autre pour Woody, Sarge, Sid - ce dernier semblant déjà exister). C'est possible et probablement pas difficile ... mais pas prioritaire. Il est prévu de s'occuper du bts d'abord (il est incapable de trier les bugs par distributions ) après la sortie de sarge. Par contre je ne voie pas de rapport de bug sur ce sujet pour pat-listbugs, cela pourrait être une contribution utile et rapide. Bon weekend Alban -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Pas d'entrée dans le menu debian
Bonjour la liste, Ceci est mon premier message sur cette liste et je ne sais pas si c'est le bon endroit pour cette question. Si ce n'est pas le cas je me rabattrai sur la liste debian-user-french :) Voici donc mon problème : Je maintiens (pas en tant que mainteneur debian officiel hein) un paquet pour le gestionnaire de fenêtres pekwm (http://pekwm.org) et je rencontre un problème : j'ai bien créé le fichier pekwmdev.menu contenant ceci : ?package(pekwmdev):needs=wm \ section=WindowManagers title=Pekwm \ command=/usr/bin/pekwm mais lorsque j'installe mon paquet rien n'est ajouté dans le menu (je teste avec le menu d'openbox) Aurais-je oublié quelquechose ? Un bug ? (je ne pense pas :D) Merci d'avoir lu :) Nico -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Qui va a Debconf?
On Mon, May 23, 2005 at 08:39:46PM +0200, Jérôme Marant wrote: Christian Perrier [EMAIL PROTECTED] writes: EN discutant avec Nicolas François qui me mentionnait ses intentions d'aller à Debconf, je me suis dit que ce serait peut-être bien de commencer à savoir qui des développeurs francophones prévoit d'aller à la Debconf d'Helsinki. Pour l'instant, je sais que veulent y aller: Denis Barbier Sven Luther Nicolas François moi-même J'ai comme l'intuition que Sam Hocevar va bien réussir à venir, mais qui d'autre encore? Comment y allez-vous at à quel prix ? Air france de strasbourg, vol a 350 euro, depuis le site web. C'est encore moins cher que la solution train jusqu'a cologne puis German Wings, wui debute a 150 euros pour l'allee et 100 euros pour le retour + frais divers. cher, mais tous n'avait pas la possibilite d'acheter leur billet en janvier :) Amicalement, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Pas d'entrée dans le menu debian
Le samedi 04 juin 2005 16:18 +0200, Nico a crit : [...] Voici donc mon problme : Je maintiens (pas en tant que mainteneur debian officiel hein) un paquet pour le gestionnaire de fentres pekwm (http://pekwm.org) et je rencontre un problme : j'ai bien cr le fichier pekwmdev.menu contenant ceci : ?package(pekwmdev):needs=wm \ section=WindowManagers title=Pekwm \ command=/usr/bin/pekwm mais lorsque j'installe mon paquet rien n'est ajout dans le menu (je teste avec le menu d'openbox) Bien fait ! :p Aurais-je oubli quelquechose ? Un bug ? (je ne pense pas :D) tout hasard, as-tu bien pens appeler dh_installmenu dans ton debian/rules ? Comme indiqu dans la page de manuel de menufile, La section WindowManagers n'existe pas, il s'agit de Window-managers. -- Cdric Delfosse, http://cdelfosse.free.fr Jabber ID: [EMAIL PROTECTED] Get a free backup server: http://lrs.linbox.org ! Linbox: http://linbox.com signature.asc Description: This is a digitally signed message part
unsubscribe
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian Java in Sarge
[Adam Heath] I agree. A java policy should talk about how java packages should interact once installed. But stay the hell away from how they are built. I disagree. It should give recommodations on how they should be built, to make it easier for the java developers to maintain the java packages. Consistency reduce the work maintaining packages, and using a common system for building java packages make it easier to improve all java build systems by doing a modification only once, in the build system. But it should probably not be a requirement, to avoid endless flame wars with maintainers who fail to see the gain of standardizing the build system for java packages. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
notes on deckit WAP phone simulator
sir, can u please give me the information bout the decik WAP phone simulator.i.e., the brief description about the phone simulator. thanking you Too much spam in your inbox? Yahoo! Mail gives you the best spam protection for FREE!http://in.mail.yahoo.com
Re: notes on deckit WAP phone simulator
On Saturday 04 June 2005 07.50, venkat prasad wrote: sir, can u please give me the information bout the decik WAP phone simulator.i.e., the brief description about the phone simulator. As far as I can tell, Debian does not ship the decit WAP phone simulator, so I don't know what information we should be able to give you. thank you -- vbi -- OpenPGP encrypted mail welcome - my key: http://fortytwo.ch/gpg/92082481 pgpqg1oUmiNRy.pgp Description: PGP signature
important vorbis-tools bug solved. possible accept for sarge? please, Accept if.
Dear Release Team!:-) I think: it is a Grave usability bug in Sarge, but, THX 2 Adeodato Sim, it is now solved. Please, Accept this important bugfix for Sarge. THX!! On Sat, 4 Jun 2005, Adeodato Sim wrote: Please, help 2 solve this problem!! Will do, but sorry, not for sarge. Nobody able or interested in fixing noticed earlier. :( Changes: vorbis-tools (1.0.1-1.4) unstable; urgency=low . * Authorized NMU. . * Restore speex support (closes: #306809). This had been lost in the previous upload due to speex 1.1 having moved its include files from /usr/include to /usr/include/speex. . + debian/rules: add -I/usr/include/speex to CFLAGS (and export it too). THX!
Re: Debian as Google summer of code mentor?
El Viernes 03 Junio 2005 01:57, Adam Heath escribió: On Thu, 2 Jun 2005, Matthijs Kooijman wrote: Hey, as you've probably heard, Google has a summer of code initiative to stimulate open source coding. They are looking for mentors to support the coders. Shouldn't Debian be on that list? Matthijs http://groups-beta.google.com/group/summer-discuss/browse_thread/thread/279 642a09050c7f2/a667a3122c21bdc2#a667a3122c21bdc2 Basically a screw you kind of reply. If some Debian developer wants to get sponsorized for his project, I think it would be more productive to write the list of requeriments and contact Branden Robinson and Google, instead of complaining. Regards, Cesar
Re: ITP: cl-rfc2388 -- an implementation of RFC 2388 in Common Lisp
Hello! On Wed 25 May 2005 07:17 +0200, Peter Van Eynde wrote: * Package name: cl-rfc2388 Version : x.y.z 0.9 Upstream Author : Name [EMAIL PROTECTED] Janis Dzerins [EMAIL PROTECTED] * URL : http://www.example.org/ http://common-lisp.net/project/rfc2388/ * License : (GPL, LGPL, BSD, MIT/X, etc.) BSD The only problem with this package is that the source contains the rfc2388 text, which cannot be included in a free package. As the rfc2388 text is already included in the doc-rfc-std-proposed package (which is in not-free), IMO the cl-rfc2388 should suggest the doc-rfc-std-proposed package. BTW, the CVS source already contains a debian/ folder, as the author accepted to let rfc2388 become a Debian native package :-) Thx, bye, Gismo / Luca pgpKIbHx2mrcJ.pgp Description: PGP signature
Every man must have a sex! MUST!!!
Security - we offer more consumer guarantees than any other website http://tswary.kznd632vzcka63k.solicsol8.com There are two rules for success: 1) Never tell everything you know. [Time is] the most valuable thing a man can spend. What we anticipate seldom occurs: but what we least expect generally happens. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian Java in Sarge
On Sat, Jun 04, 2005 at 08:59:30AM +0200, Petter Reinholdtsen wrote: [Adam Heath] I agree. A java policy should talk about how java packages should interact once installed. But stay the hell away from how they are built. I disagree. It should give recommodations on how they should be built, to make it easier for the java developers to maintain the java packages. Consistency reduce the work maintaining packages, and using a common system for building java packages make it easier to improve all java build systems by doing a modification only once, in the build system. But it should probably not be a requirement, to avoid endless flame wars with maintainers who fail to see the gain of standardizing the build system for java packages. FULL ACK. Michael -- Escape the Java Trap with GNU Classpath! http://www.gnu.org/philosophy/java-trap.html Join the community at http://planet.classpath.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Is Ubuntu a debian derivative or is it a fork?
On Thu, Jun 02, 2005 at 12:18:50AM -0700, Russ Allbery wrote: Matt Zimmerman [EMAIL PROTECTED] writes: Regarding your specific example, I know of no reason why Debian couldn't use Ubuntu's X.org packages when Debian is ready to make the transition, but in the end that will be the XSF's decision, not Ubuntu's. There appears to be a bunch of work going on around this right now, without a ton of fanfare. (Pretty much the ideal situation, as far as I'm concerned. It's usually a good sign when matters get to the point that people are committing things rather than talking about what to commit.) I'm working very hard to minimize the delta between the Ubuntu and Debian packages in this particular case. This will be problematic so since there are essentially two re-packaging efforts planned for the future, and they are almost completely different. In a lot of ways, this particular codebase is a worst-case scenario, but it's not dissimilar to the problem that started this thread: collision between completely different efforts between Debian and Ubuntu packagers. For something like wifi-radar this isn't a big problem, but for X.org this is potentially a huge issue. While I'm happy that Canonical has done the work on X.org and made it available to Debian, Debian can not become beholden to Canonical for such work in any way. If we do, we become like Fedora. The same goes for any other Debian-derivative (spork?). I, for one, refuse to let that happen, which is one reason why I'm working on minimizing that delta in every way I can and hopefully I can get both the Ubuntu X folk(s) and Debian X folks hacking on the exact same source tree. I can't play politics forever though, and at a certain point there needs to be some more coherent statement of policy (if just for practical purposes) than what we've seen so far. - David Nusinow -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#311795: ITP: rast -- A full text search system
Le vendredi 03 juin 2005 à 21:14 +0900, Taku YASUI a écrit : Package: wnpp Severity: wishlist * Package name: rast Version : 0.1.1 Upstream Author : Name [EMAIL PROTECTED] * URL : http://www.netlab.jp/rast/ * License : GPL Description : N-gram based full text search system library Rast is N-gram based full text search system library. it has following features. * N-gram based indexing; No dictionaries are needed * Support many types of documents; e.g. HTML, MS Word * Includes library for some programming languages * Add text incrementally Could you please explain what is N-gram and what is this package useful for? -- .''`. Josselin Mouette/\./\ : :' : [EMAIL PROTECTED] `. `'[EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom signature.asc Description: This is a digitally signed message part
Re: Bug#311795: ITP: rast -- A full text search system
Le vendredi 03 juin 2005 à 21:14 +0900, Taku YASUI a écrit : Package: wnpp Severity: wishlist * Package name: rast Version : 0.1.1 Upstream Author : Name [EMAIL PROTECTED] * URL : http://www.netlab.jp/rast/ * License : GPL Description : N-gram based full text search system library Rast is N-gram based full text search system library. it has following features. * N-gram based indexing; No dictionaries are needed * Support many types of documents; e.g. HTML, MS Word * Includes library for some programming languages * Add text incrementally Could you please explain what is N-gram and what is this package useful for? -- .''`. Josselin Mouette/\./\ : :' : [EMAIL PROTECTED] `. `'[EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom signature.asc Description: This is a digitally signed message part
Re: Bug#311795: ITP: rast -- A full text search system
Le vendredi 03 juin 2005 à 21:14 +0900, Taku YASUI a écrit : Package: wnpp Severity: wishlist * Package name: rast Version : 0.1.1 Upstream Author : Name [EMAIL PROTECTED] * URL : http://www.netlab.jp/rast/ * License : GPL Description : N-gram based full text search system library Rast is N-gram based full text search system library. it has following features. * N-gram based indexing; No dictionaries are needed * Support many types of documents; e.g. HTML, MS Word * Includes library for some programming languages * Add text incrementally Could you please explain what is N-gram and what is this package useful for? -- .''`. Josselin Mouette/\./\ : :' : [EMAIL PROTECTED] `. `'[EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom signature.asc Description: This is a digitally signed message part
Re: Is Ubuntu a debian derivative or is it a fork?
OK, here is idea/solution for problems with packaging. All new Ubuntu packages should have ITP on Debian lists. For example, if I package app that isn't in Debian, and I package it for Ubuntu, I will fill ITP for that package on Debian list. That package will or will not be accepted to Debian, but any other Debian developer who would like to work on that package, will contact me and we would cooperate. Same package will enter Ubuntu and it would be safe. There would be no posibility that same package will apear in Debian without my knowledge. This way we would have one big source repository for both distributions. Any comments? -- Ante Karamatic|--|ivoks(@)grad.hr|--|PGP: D3BDA225 http://master.grad.hr/~ivoks/|--|ICQ: 64631782 May, 15. herve we're fixing the universe, it's not an easy duty! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Is Ubuntu a debian derivative or is it a fork?
On Thu, 2 Jun 2005 00:25:01 -0400
Joey Hess [EMAIL PROTECTED] wrote:
(To answer the thread leader, I consider Ubuntu to be more and more of a
fork and less and less a derivative distribution. If Ubuntu doesn't
start to re-converge with Debian significantly after sarge is released,
and we end up with two sets of X.org packaging, etc, then I will give up
and just consider it purely a fork.)
From the first CD I installed, I realized it was a fork...and a disapointing
one at that. (Pretty desktop on live CD didn't install from installation CD,
but the fact that their archives only hold their limited package set, found
on the CDs, made it apparent that they were a separate distro, based on
Debian but not necessarily compatible with Debian.)
Knoppix is much better about using Debian packages and adding configuration
integration of a much wider range of Debian packages. as well as installing
on hard drive ready to modify and upgrade. (Although these days I'm using
Bonzi to install Debian, with great success. The autoconfiguration of USB
is quite useful, almost as good as DLS{another Debian derivative})
However, the coolest thing I have seen that uses Debian is the NOKIA 770
Wi-Fi tablet available in September of this year. Their argument for using
Debian was that apt-get would keep the machine upgraded for life. Yes, their
Internet Tablet 2005 sofware edition is probably a fork, the implication
on Hack-a-Day is that other packages and applications can be added to this
machine. Their own web site doesn't say a thing about Debian, but their
developers site (maemo.org makes it clearer under Building and installing
Debian packages). This could be a fun hack, and the solution to some
hardware problems I have been trying to resolve ;-)
Luck,
Dwarf
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Is Ubuntu a debian derivative or is it a fork?
[Ante Karamati?] All new Ubuntu packages should have ITP on Debian lists. For example, if I package app that isn't in Debian, and I package it for Ubuntu, I will fill ITP for that package on Debian list. This is not going to work for all packages, as some package maintainers are not too happy about Debian, and would only like to maintain packages in Ubuntu. We need a procedure for this case as well. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
New Debian Package Customization HOWTO
Greeting lists, Today Kevin Mark poitned out[0] that I should turn a brief outline I gave[1] on how to customize Debian pacakges into a full blown HOWTO. I have done that and the result [2] is now available to the public. I would like to announce it in the hopes that new and experienced Debian developers and users will review it and provide some feedback. After a week or so, I will probably submit it to some Debian-related wikis and websites. But, I first want to make sure that it is in reasonable shape before I *really* present it to the world :-) -Roberto [0] http://lists.debian.org/debian-user/2005/06/msg00362.html [1] http://lists.debian.org/debian-user/2005/06/msg00175.html [2] http://familiasanchez.net/~sanchezr/?page=debcustomize -- Roberto C. Sanchez http://familiasanchez.net/~sanchezr pgpoVhwYf2yAA.pgp Description: PGP signature
Re: Debian Java in Sarge
On Sat, Jun 04, 2005 at 08:59:30AM +0200, Petter Reinholdtsen wrote: I disagree. It should give recommodations on how they should be built, to make it easier for the java developers to maintain the java packages. Consistency reduce the work maintaining packages, and using a common system for building java packages make it easier to improve all java build systems by doing a modification only once, in the build system. can you give an example of anywhere else in debian where developers are forced to use a specific build tool/system for their packages? instead of trying to force people to do things your way, i would suggest that you come up with an infrastructure for making these packages that really is easier and consistant, and then say something like packages built with java must follow these guidelines. we've made this easy to do if you use these build tools. i think you'll find most people will gravitate towards doing so (debhelper is a good example of this), and those who don't probably have a good reason (either because the tool can't do what they want or maybe they've found a better way). sean -- signature.asc Description: Digital signature
Re: Is Ubuntu a debian derivative or is it a fork?
Hi Petter, Am Samstag, den 04.06.2005, 18:38 +0200 schrieb Petter Reinholdtsen: This is not going to work for all packages, as some package maintainers are not too happy about Debian, and would only like to maintain packages in Ubuntu. We need a procedure for this case as well. Do you have a particular case in mind? Have a nice day, Daniel signature.asc Description: This is a digitally signed message part
doctor
Your medicine source: http://yfoluwzgefjkxe60uiiyxgpwufhw.sheavemanjj.com/ arcsine
Re: Debian Java in Sarge
[Sean Finney] can you give an example of anywhere else in debian where developers are forced to use a specific build tool/system for their packages? Hard to tell, I haven't spend time looking. But I can give an example of a person unable to discover that I didn't suggest forcing anyone to do anything. I formulated a 'recommend and not require' suggestion in my mail. What did you read? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Is Ubuntu a debian derivative or is it a fork?
Hello Dale, Am Samstag, den 04.06.2005, 11:29 -0400 schrieb Dale C. Scheetz: From the first CD I installed, I realized it was a fork...and a disapointing one at that. (Pretty desktop on live CD didn't install from installation CD, but the fact that their archives only hold their limited package set, found on the CDs, made it apparent that they were a separate distro, based on Debian but not necessarily compatible with Debian.) this is not quite true. The CD only holds packages from the main component, but there are Universe, Multiverse (the non-free section) and restricted as well. Apart from that, I really can't see this as an indication for a fork. Have a nice day, Daniel signature.asc Description: This is a digitally signed message part
Perl or Java project
Where could I find out about projects that still need developers. I could code in perl and java. Please tell me where I can read the resources regarding to the available projects in debian. Thxn in advance -- Blog: http://jroller.com/page/defkewl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian Java in Sarge
On Sat, Jun 04, 2005 at 07:13:57PM +0200, Petter Reinholdtsen wrote: Hard to tell, I haven't spend time looking. But I can give an example of a person unable to discover that I didn't suggest forcing anyone to do anything. I formulated a 'recommend and not require' suggestion in my mail. What did you read? guess that's what i get for jumping into a conversation without reading a bit further back. i read part of a mail quoted in another email that seemed to imply otherwise and guess i took that out of context. my bad. sean -- signature.asc Description: Digital signature
Bug#311986: ITP: scim-input-pad -- on-screen input pad IM engine module for SCIM
Package: wnpp Severity: wishlist Owner: Ming Hua [EMAIL PROTECTED] * Package name: scim-input-pad Version : 0.1.0 Upstream Author : James Su [EMAIL PROTECTED] * URL : http://www.scim-im.org/ * License : GPL Description : on-screen input pad IM engine module for SCIM SCIM (Smart Common Input Method) is an input method (IM) platform. This package provides the on-screen input pad IM engine module for SCIM. Using the input pad users can see a group of symbols and choose from them as input. The symbol groups included in this package are basic symbols (technical symbols, punctuation symbols, etc.), Chinese numbers and radicals, Japanese Katakana and Hiragana symbols, and special key events (dead keys, compose keys, etc.). For details about SCIM, please see the description of package scim. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-2-k7 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Is Ubuntu a debian derivative or is it a fork?
On Sat, 04 Jun 2005 19:16:50 +0200 Daniel Holbach [EMAIL PROTECTED] wrote: Hello Dale, Am Samstag, den 04.06.2005, 11:29 -0400 schrieb Dale C. Scheetz: From the first CD I installed, I realized it was a fork...and a disapointing one at that. (Pretty desktop on live CD didn't install from installation CD, but the fact that their archives only hold their limited package set, found on the CDs, made it apparent that they were a separate distro, based on Debian but not necessarily compatible with Debian.) this is not quite true. The CD only holds packages from the main component, but there are Universe, Multiverse (the non-free section) and restricted as well. When using apt-get on a system installed from the installation CD (not the live CD) apt-get points to the Ubuntu archives, which only contain a very limited subset of Debian's main archives. I had limited success in pointing apt at a real Debian archives and getting additional packages to install. This is why I said it looked like a fork from the biginnig. This is a desktop distribution with a specific philosphy that dictates looking at global configuration of packages in a different way than the Debian developers may... Apart from that, I really can't see this as an indication for a fork. Even as a fork, there are useful ideas to be gleaned from them, and their open source policy seems to make that possible, dispite the technical problems... Luck, Dwarf -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New Debian Package Customization HOWTO
Roberto C. Sanchez [EMAIL PROTECTED] wrote: would like to announce it in the hopes that new and experienced Debian developers and users will review it and provide some feedback. After a [2] http://familiasanchez.net/~sanchezr/?page=debcustomize The official Debian packages are built by a buildd, also called build daemon, which makes use of pbuilder to ensure that every package is built in a clean environment. IIRC I read 2 or 3 weeks ago on d-d, that this is not the case. As the buildds keeps installed dependencies for performance reason and can't be used to check for build-dependencies. Sorry I didn't have the link at hands, but maybe someone competent can confirm/correct this. Christoph -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#311997: ITP: gaim-latex -- gaim plugin wich translate LaTeX code into image in conversation
Package: wnpp Severity: wishlist Owner: Martin Braure de Calignon [EMAIL PROTECTED] -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 * Package name: gaim-latex Version : 0.3 Upstream Author : Nicolas Schoonbroodt * URL : http://sourceforge.net/projects/gaim-latex * License : GPL Description : gaim plugin wich translate LaTeX code into image in conversation Provides the use of LaTeX code in conversation in gaim. The code is converted in image by tex2im script (imagemagick) and the image is sent to your contact. - -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (950, 'unstable'), (200, 'testing'), (25, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11-1-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCoegkcHEx8cor214RAl/eAJ994oHvvC7VO82CkTpuf4SdsIZCvgCbBlj8 NmDSgOGKG0JerwYCNEpG5VQ= =zNQ4 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Is Ubuntu a debian derivative or is it a fork?
On Sat, Jun 04, 2005 at 06:38:54PM +0200, Petter Reinholdtsen wrote: [Ante Karamati?] All new Ubuntu packages should have ITP on Debian lists. For example, if I package app that isn't in Debian, and I package it for Ubuntu, I will fill ITP for that package on Debian list. This is not going to work for all packages, as some package maintainers are not too happy about Debian, and would only like to maintain packages in Ubuntu. We need a procedure for this case as well. Should Ubuntu encourage such behaviour ? Cheers, -- Bill. [EMAIL PROTECTED] Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Is Ubuntu a debian derivative or is it a fork?
Hey Dale, Am Samstag, den 04.06.2005, 12:33 -0400 schrieb Dale C. Scheetz: When using apt-get on a system installed from the installation CD (not the live CD) apt-get points to the Ubuntu archives, which only contain a very limited subset of Debian's main archives. I had limited success in pointing apt at a real Debian archives and getting additional packages to install. This is why I said it looked like a fork from the biginnig. This is a desktop distribution with a specific philosphy that dictates looking at global configuration of packages in a different way than the Debian developers may... Maybe I didn't make myself clear enough: The Ubuntu main component is a limited subset, where Canonical is willing to support packages for a timespan of 18 months (3 releases). Ubuntu Universe/Multiverse is a community maintained section, which has to be enabled in /etc/apt/sources.lists. You were right with your observation that Debian main != Ubuntu main, but that's only half of the truth. ;-) Have a nice day, Daniel signature.asc Description: This is a digitally signed message part
Re: Is Ubuntu a debian derivative or is it a fork?
[Bill Allombert] Should Ubuntu encourage such behaviour ? Is it? I doubt they do. Not all package maintainers in Ubuntu are paid by Canonical, and thus fairly out of control of the corporate Ubuntu policies. Just as in Debian, I guess, were several package maintainers demonstrate questionable cooperation skills. :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Is Ubuntu a debian derivative or is it a fork?
[Daniel Holbach] Do you have a particular case in mind? I'm not going to provide examples, no. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Is Ubuntu a debian derivative or is it a fork?
Hi Bill, Am Samstag, den 04.06.2005, 11:47 -0500 schrieb Bill Allombert: This is not going to work for all packages, as some package maintainers are not too happy about Debian, and would only like to maintain packages in Ubuntu. We need a procedure for this case as well. Should Ubuntu encourage such behaviour ? I have no idea, where Petter made up this opinion. Ok, there are a couple of maintainers who are not DDs, so they won't be able to maintain them in both, Ubuntu an Debian, but I think everybody is perfectly happy to group-maintain packages in both worlds. Have a nice day, Daniel signature.asc Description: This is a digitally signed message part
Re: Bug#311997: ITP: gaim-latex -- gaim plugin wich translate LaTeX code into image in conversation
Le Samedi 4 Juin 2005 19:43, Martin Braure de Calignon a écrit : [...] Provides the use of LaTeX code in conversation in gaim. The code is converted in image by tex2im script (imagemagick) and the image is sent to your contact. [...] Just a little mistake : according to the author of gaim-latex, the image is not sent to your contact, just the LaTeX code, and your contact have to had gaim-latex (or kopetex ?) to translate the LaTeX code in image. -- Florent Bayle pgpi2CK1U4upl.pgp Description: PGP signature
Re: Is Ubuntu a debian derivative or is it a fork?
On Sat, Jun 04, 2005 at 08:14:45PM +0200, Petter Reinholdtsen wrote: [Daniel Holbach] Do you have a particular case in mind? I'm not going to provide examples, no. Would it be possible to provide some general description of the sorts of problem they see? -- You grabbed my hand and we fell into it, like a daydream - or a fever. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Is Ubuntu a debian derivative or is it a fork?
Hi Petter, Am Samstag, den 04.06.2005, 20:14 +0200 schrieb Petter Reinholdtsen: [Daniel Holbach] Do you have a particular case in mind? I'm not going to provide examples, no. I'm very unhappy, about your answers and this whole thread in general. Don't get me wrong, I'm not accusing you of anything. But the atmosphere in the thread is tense and full of misunderstandings. With every mail it becomes clearer that we're all miles away from actually making plans and discussing concrete specifications of what's to happen. One thing I always loved about the Open Source world is, if there was a problem (and no matter what type of it): it didn't exist for long: people always found a way to make great things happen. So can we try to get back to the topic? What are we precisely discussing at the moment? * The handling of NEW packages and in which cases to file an ITP. * How to retrieve patches in the easiest way. * How to start group maintenance. Maybe there are other issues, I missed in the thread. Can you believe it? Just those three bullet points? It should be easy to draft specs about exactly these issues. I'm aware of the fact that it may take longer to implement them and even if we regard all the corner cases, there will be people arguing, complaining and bickering, but ... so what? I was at the Ubuntu Conference in Sydney and one thing I loved completely, was the way how we discussed specifications and how we tackled problems. Shouldn't it be possible to think of solutions in the same way? I can feel that we all can take incredible benefit out of this, so let's go! Let's make it happen! :) Have a nice day, Daniel signature.asc Description: This is a digitally signed message part
Re: Bug#311997: ITP: gaim-latex -- gaim plugin wich translate LaTeX code into image in conversation
Le samedi 04 juin 2005 à 20:18 +0200, Florent Bayle a écrit : Le Samedi 4 Juin 2005 19:43, Martin Braure de Calignon a écrit : [...] Provides the use of LaTeX code in conversation in gaim. The code is converted in image by tex2im script (imagemagick) and the image is sent to your contact. [...] Just a little mistake : according to the author of gaim-latex, the image is not sent to your contact, just the LaTeX code, and your contact have to had gaim-latex (or kopetex ?) to translate the LaTeX code in image. Yes you're true, it's a misunderstood of me. I'll change it in few hours. Thank you very much :-) -- Martin Braure de Calignon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Is Ubuntu a debian derivative or is it a fork?
[Daniel Holbach] Hi Petter, Hi. But the atmosphere in the thread is tense and full of misunderstandings. With every mail it becomes clearer that we're all miles away from actually making plans and discussing concrete specifications of what's to happen. I'm not that pessimistic. Perhaps I lack a clear understanding of the current concensus. I do not know. So can we try to get back to the topic? Yes, lets do that. What are we precisely discussing at the moment? I believe we are discussing how to keep the packages in Debian and Ubuntu as synchronized as possible, to hopefully reduce the maintainence cost and improve the package quality in Ubuntu, and hopefully improve the package quality and reduce the maintenence cost in Debian. And more specificly, we are discussing how to make sure (new/not in debian) packages in Ubuntu also make it into Debian. I suspect we are under the assumtion that packages are placed in Ubuntu because they are useful, and thus would be useful in Debian as well. * The handling of NEW packages and in which cases to file an ITP. * How to retrieve patches in the easiest way. * How to start group maintenance. Maybe there are other issues, I missed in the thread. Can you believe it? Just those three bullet points? There is also the issue on how to handle lack of communication and lack of interest on one side or the other of working together with the other side, but I guess we could ignore that for now. To start with your list. - Handling NEW packages (in Ubuntu, I guess, or do anyone want something changed in how Debian handle new packages?) I believe it would be best if Canonical encouraged the people maintaining packages in Ubuntu to also submit an RFP/ITP into Debian as well, and also encourage people to try to find a DD sponsor to upload the packages both into Debian and into Ubuntu. - Exchanging patches Not sure how to best handle this. If Ubuntu accept the Debian packages as upstream, all relevant patches should be submitted into Debian BTS, and followed up there to reduce the diff between the packages in Debian and Ubuntu. This might be a bit work intense (it is/was for debian-edu at least), so it might not be the best way to spend the limited time available. - Group maintenance Good idea. I suspect the ideal situation for packages available both in Debian and Ubuntu would be if there is a group consisting of both the Debian and Ubuntu package maintainers co-maintaining the package together. But it is a bit hard to get this going, when I see efforts in Ubuntu (UbuntuGIS, UbuntuJava) where the effort start without first coordinating with the already existing and relevant Debian efforts (Debian GIS, Debian Java). This seem to improve, but we are not there yet. I'm not sure how we can improve this, as the priorities of the two efforts might be different, and the deadlines not aligned either. I would be willing to co-maintain my packages with the maintainer in Ubuntu, and hope more people in Debian would consider this as well. I also check out interesting Ubuntu packages at random times, and try to get them included into Debian as well. But it would be better if this wasn't left to random people looking at random packages, but instead was more organized and consistent. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: notes on deckit WAP phone simulator
http://lists.debian.org/debian-devel/2000/11/msg01345.html http://lists.debian.org/debian-devel/2000/11/msg01347.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Is Ubuntu a debian derivative or is it a fork?
On Sat, Jun 04, 2005 at 11:29:02AM -0400, Dale C. Scheetz wrote: From the first CD I installed, I realized it was a fork...and a disapointing one at that. (Pretty desktop on live CD didn't install from installation CD, Can you explain what you mean by this statement about the CD? Did the installation fail? but the fact that their archives only hold their limited package set, found on the CDs, made it apparent that they were a separate distro, based on Debian but not necessarily compatible with Debian.) A few minutes' more exploration (a peek at /etc/apt/sources.list) would have revealed that in fact everything you would expect to find is available in the archives, though only a subset of it is presented by default. -- - mdz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Is Ubuntu a debian derivative or is it a fork?
On Sat, Jun 04, 2005 at 06:38:54PM +0200, Petter Reinholdtsen wrote: [Ante Karamati?] All new Ubuntu packages should have ITP on Debian lists. For example, if I package app that isn't in Debian, and I package it for Ubuntu, I will fill ITP for that package on Debian list. This is not going to work for all packages, as some package maintainers are not too happy about Debian Is this judgement based on some experience you had with an Ubuntu developer? I'd like to hear about it, because this is certainly not the common case, and there is an unfortunate amount of myth and rumour on this subject. , and would only like to maintain packages in Ubuntu. We need a procedure for this case as well. As Ante pointed out, this is applicable regardless of the packages' presence or maintainership in Debian, and was suggested as a way to improve communication. -- - mdz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Is Ubuntu a debian derivative or is it a fork?
On Sat, Jun 04, 2005 at 08:13:35PM +0200, Petter Reinholdtsen wrote: [Bill Allombert] Should Ubuntu encourage such behaviour ? Is it? I doubt they do. Certainly not. Quite the opposite, in fact. Not all package maintainers in Ubuntu are paid by Canonical, and thus fairly out of control of the corporate Ubuntu policies. As a matter of fact, a minority of Ubuntu developers are employed by Canonical. The reality of how this works out in practice is sometimes not obvious, especially to those who have not been involved with the Ubuntu community first-hand, but in this case the distinction, and the policies of Canonical Ltd., are entirely irrelevant. The behavior of members of the Ubuntu community, regardless of their affiliation, is governed by the Code of Conduct: http://www.ubuntulinux.org/community/conduct -- - mdz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Is Ubuntu a debian derivative or is it a fork?
Hi Petter, thank you very much for that mail. Am Samstag, den 04.06.2005, 21:01 +0200 schrieb Petter Reinholdtsen: And more specificly, we are discussing how to make sure (new/not in debian) packages in Ubuntu also make it into Debian. I suspect we are under the assumtion that packages are placed in Ubuntu because they are useful, and thus would be useful in Debian as well. Every package in Debian makes its way into Ubuntu - only if it should collide with other ones, can't be build at all or isn't sensible at all, it is removed. Those are very rare corner cases. There is also the issue on how to handle lack of communication and lack of interest on one side or the other of working together with the other side, but I guess we could ignore that for now. Of course. I just tried to adress the technical issues first, because they can more easily be pushed into specifications and give a framework, which makes it easier to act. I believe it would be best if Canonical encouraged the people maintaining packages in Ubuntu to also submit an RFP/ITP into Debian as well, and also encourage people to try to find a DD sponsor to upload the packages both into Debian and into Ubuntu. I will take this into the next MOTU Meeting [1], where the issues, ideas and plans of the MOTUs (community maintainers) are discussed. [1] http://wiki.ubuntu.com/MOTUMeeting Not sure how to best handle this. If Ubuntu accept the Debian packages as upstream, all relevant patches should be submitted into Debian BTS, and followed up there to reduce the diff between the packages in Debian and Ubuntu. This might be a bit work intense (it is/was for debian-edu at least), so it might not be the best way to spend the limited time available. This needs to be adressed in a broader forum. Everbody will have an opinion on solutions like mass-bts-ing, mass-mailing or rss feeds. - Group maintenance ... I'm not sure how we can improve this, as the priorities of the two efforts might be different, and the deadlines not aligned either. I will adress this in the next MOTU meeting as well. If there's a new team evolving (we're just 20 people yet), we will make sure this is on debian-devel@ as well so we can get things going closely together. I would be willing to co-maintain my packages with the maintainer in Ubuntu, and hope more people in Debian would consider this as well. I also check out interesting Ubuntu packages at random times, and try to get them included into Debian as well. But it would be better if this wasn't left to random people looking at random packages, but instead was more organized and consistent. Thanks for your confidence, this give me hope. As I pointed out: the developer base is still quite small and there are (apart from some examples) no fixed maintainers for packages, although everybody respects the area of expertise of another one. If we can make up processes and discuss specifics, we'll get there, definitely. Have a nice day, Daniel signature.asc Description: This is a digitally signed message part
Re: Is Ubuntu a debian derivative or is it a fork?
[Matt Zimmerman] Is this judgement based on some experience you had with an Ubuntu developer? The observation (judgement is stretching it too far) is based on my very limited experience with packages in Ubuntu which are/were missing in Debian. I'd like to hear about it, because this is certainly not the common case, and there is an unfortunate amount of myth and rumour on this subject. Oh, it is definitely not the common case. My sample set is ~5 packages, and for most of them the maintainer of the Ubuntu package were very interested in cooperation and co-maintenance. My point is just that we should be aware of the border cases, and try to find procedures to handle those as well. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Linux / Debian / Ubuntu
Could you point me at a RealPlayer for each and every platform Debian supports? No, but real player's core (Helix Player) is open source. The codecs are use restricted to personal use, and the codec source is available *for porting only*, under a a binding contract. (This they label a Eula, but you must print it, sign it, and send it in, so there is no doubt that it is legally binding.) RealMedia is apparently even kind enough to offer the RealPlayer branded version of the Helix player under (GPL|| RPSL). THE POINT: Therefore it is theoreticly possible to obtain or make a realplayer branded player with full support for the RealVideo and RealAudio for any playform Debian is available on. Note: RealPlayer 10 branded helix player + RealCodecs 10 != RealPlayer 10 Linux. The difference is that Realplayer 10 Linux includes a few additional components. (Flash, Mp3, etc.) Summary: Helix: (GPL||RPSL) RealPlayer branded Helix Player: (GPL||RPSL) [TRADEMARK restrictions would apply] RealPlayer's Codecs: Non-Libre, Gratis personal use [EULA] RealPlayer Codec Sources: Non-Libre [Gratis binding EULA/NDA] See https://helixcommunity.org/content/licenses -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Is Ubuntu a debian derivative or is it a fork?
On Sat, 4 Jun 2005, Ante [iso-8859-2] Karamati? wrote: All new Ubuntu packages should have ITP on Debian lists. For example, if I package app that isn't in Debian, and I package it for Ubuntu, I will fill ITP for that package on Debian list. Great! I would tell this idea quite natural and I would love if you would do so. I guess Ubuntu will have reasons to package software for a wider user base and thus it should be no problem to find a sponsor. That package will or will not be accepted to Debian, but any other Debian developer who would like to work on that package, will contact me and we would cooperate. Thank you very much for this suggestion. Same package will enter Ubuntu and it would be safe. There would be no posibility that same package will apear in Debian without my knowledge. This way we would have one big source repository for both distributions. Any comments? Go for it Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Is Ubuntu a debian derivative or is it a fork?
On Sat, 4 Jun 2005, Dale C. Scheetz wrote: Knoppix is much better about using Debian packages and adding configuration integration of a much wider range of Debian packages. Sure. Knoppix is basically builded by a single person. Didn't I said that just using what Debian provides is quite effective? Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Is Ubuntu a debian derivative or is it a fork?
On Sat, 4 Jun 2005, Daniel Holbach wrote: Ok, there are a couple of maintainers who are not DDs, so they won't be able to maintain them in both, Ubuntu an Debian, but I think everybody is perfectly happy to group-maintain packages in both worlds. It might be not very hard to find a sponsor for a good and useful package so I see no problem to maintain a package in both. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian Java in Sarge
Le vendredi 03 juin 2005 à 18:41 -0500, Adam Heath a écrit : I agree. A java policy should talk about how java packages should interact once installed. But stay the hell away from how they are built. As an example, debhelper, while being very useful for maintainers, is not mandated. That doesn't make not using it less stupid. The few times I saw a package not using debhelper, it was broken in some way. -- .''`. Josselin Mouette/\./\ : :' : [EMAIL PROTECTED] `. `'[EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom signature.asc Description: This is a digitally signed message part
Re: Is Ubuntu a debian derivative or is it a fork?
On Sat, 4 Jun 2005, Daniel Holbach wrote: But the atmosphere in the thread is tense and full of misunderstandings. You are right here and I love if we could solve this. With every mail it becomes clearer that we're all miles away from actually making plans and discussing concrete specifications of what's to happen. I'll try to come back to this. So can we try to get back to the topic? What are we precisely discussing at the moment? I'll try the answers of my point of view. which is: The most effective way to derive a distribution with low effort is to keep the diff small. * The handling of NEW packages and in which cases to file an ITP. File an ITP / RFP for any package you want to see in *your* distribution. (this would probably lead to group maintainance or at least sponsoring which is in principle also a group maintainance, because at least four eyes are looking in the case the Ubuntu maintainer is no Debian developer) * How to retrieve patches in the easiest way. In Debian we have a defined way to provide patches: The BTS. * How to start group maintenance. Easy: The maintainers should just start talking about their packages in private or blog common problems in BTS. Again: This is *my* point of view for most effective work. It seems to work in several cases wuite fine. In some case it is an oversimplification of the problem but a discussion in a common list would help drastically. If somebody thinks the way I described is not optimal it is fine for me and I have no trouble with it. If we can not accomplis the things I described above for the majority of packages I would consider Ubuntu mor as a fork than a derivative. This is absolutely not problem for me, but it would be less effective than it could be - but I might be wrong. Maybe there are other issues, I missed in the thread. Can you believe it? Just those three bullet points? I think you reduced the thread to the basic points, yes. I was at the Ubuntu Conference in Sydney and one thing I loved completely, was the way how we discussed specifications and how we tackled problems. So you had just statements to the bullets above? Which are these? Shouldn't it be possible to think of solutions in the same way? I can feel that we all can take incredible benefit out of this, so let's go! Let's make it happen! :) Thanks for the clear words Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Perl or Java project
On Sat, 4 Jun 2005, Joshua Jackson wrote: Where could I find out about projects that still need developers. I could code in perl and java. Please tell me where I can read the resources regarding to the available projects in debian. Please take a look at http://webmin.alioth.debian.org/ particularly the todo list and the open bugs. webmin is almost entirely perl. -- Jaldhar H. Vyas [EMAIL PROTECTED] La Salle Debain - http://www.braincells.com/debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Is Ubuntu a debian derivative or is it a fork?
Am Samstag, den 04.06.2005, 23:50 +0200 schrieb Andreas Tille: On Sat, 4 Jun 2005, Daniel Holbach wrote: But the atmosphere in the thread is tense and full of misunderstandings. You are right here and I love if we could solve this. Nice you say that. :) I was at the Ubuntu Conference in Sydney and one thing I loved completely, was the way how we discussed specifications and how we tackled problems. So you had just statements to the bullets above? Which are these? I don't quite understand your question. If you referred to the conference at Sydney, we discussed quite a lot of issues and ideas there, for full coverage have a look at http://udu.wiki.ubuntu.com If you rather referred to the bullet points, I clarified my statements to those on: http://lists.debian.org/debian-devel/2005/06/msg00264.html Thanks for your mail. Have a nice day, Daniel signature.asc Description: This is a digitally signed message part
Re: Debian Java in Sarge
On Sat, 4 Jun 2005, Josselin Mouette wrote: Le vendredi 03 juin 2005 à 18:41 -0500, Adam Heath a écrit : I agree. A java policy should talk about how java packages should interact once installed. But stay the hell away from how they are built. As an example, debhelper, while being very useful for maintainers, is not mandated. That doesn't make not using it less stupid. The few times I saw a package not using debhelper, it was broken in some way. Of course. That doesn't mean it should be mandated.
Re: Bug#311997: ITP: gaim-latex -- gaim plugin wich translate LaTeX code into image in conversation
On Sat, Jun 04, 2005 at 07:43:00PM +0200, Martin Braure de Calignon wrote: Package: wnpp Severity: wishlist Owner: Martin Braure de Calignon [EMAIL PROTECTED] * Package name: gaim-latex Version : 0.3 Upstream Author : Nicolas Schoonbroodt * URL : http://sourceforge.net/projects/gaim-latex * License : GPL Description : gaim plugin wich translate LaTeX code into image in conversation Provides the use of LaTeX code in conversation in gaim. The code is converted in image by tex2im script (imagemagick) and the image is sent to your contact. This totally rocks! Please get this in soon. -Roberto -- Roberto C. Sanchez http://familiasanchez.net/~sanchezr pgpoP5ofdewUy.pgp Description: PGP signature
attention! hidden college camera Ernie
Do you want to see real amateurs who have webcams on their computers in their dorm rooms? This is not one of those sites with professional girls who get paid to do this in front of the camera, these are the average girls next door, at college, trying to make money and meet guys! Get free access to a huge database of hot college girls, unlimited cam shows with LIVE CHAT and there are no Pay-Per-Minute charges! http://correctspeling.com/co25/ abbas you la me accent you anecdote me cowlick you adams me wrathful you burgess me hay you franciscan me shasta you installation me -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Perl or Java project
Joshua Jackson: Where could I find out about projects that still need developers. I could code in perl and java. Please tell me where I can read the resources regarding to the available projects in debian. Aside from Debian, you could browse the Sourceforge.net project list sorted by programming language and look for something you are interested in: http://sourceforge.net/softwaremap/trove_list.php?form_cat=160 There is also a Help wanted section at http://sourceforge.net/people/ where you can directly find projects seeking help. A lot of Debian's packages are hosted upstream at Sourceforge, so you would help Debian, too. J. -- If I could travel through time I would go back to yesterday and apologise. [Agree] [Disagree] http://www.slowlydownward.com/NODATA/data_enter2.html signature.asc Description: Digital signature
Re: New Debian Package Customization HOWTO
On Sat, Jun 04, 2005 at 12:56:33PM -0400, Roberto C. Sanchez wrote: Greeting lists, Today Kevin Mark poitned out[0] that I should turn a brief outline I gave[1] on how to customize Debian pacakges into a full blown HOWTO. I have done that and the result [2] is now available to the public. I would like to announce it in the hopes that new and experienced Debian developers and users will review it and provide some feedback. After a week or so, I will probably submit it to some Debian-related wikis and websites. But, I first want to make sure that it is in reasonable shape before I *really* present it to the world :-) -Roberto Hi Roberto, I read it and it seems great! Haven't had a change to build anything yet but I'm sure it will help me when I do. a minor typo, search for 'since'. As someone commented, I believe pbuilder does not clean the chroot. for slow archs like arm and m68k, it would be inefficient to rebuild all the dependencies for building KDE on arm after every change, as an example. And I dont think someone making a personal packages would want to waste the time to clean it. Keep up the great work, you'll be a DD before Etch (at least I hope so) is released! Cheers, Kev -- counter.li.org #238656 -- goto counter.li.org and be counted! `$' $' $ $ _ ,d$$$g$ ,d$$$b. $,d$$$b`$' g$b $,d$$b ,$P' `$ ,$P' `Y$ $$' `$ $ ' `$ $$' `$ $$ $ $$g$ $ $ $ ,$P $ $$ `$g. ,$$ `$$._ _. $ _,g$P $ `$b. ,$$ $$ `Y$$P'$. `YP $$$P' ,$. `Y$$P'$ $. ,$. signature.asc Description: Digital signature
Re: New Debian Package Customization HOWTO
Roberto C Sanchez [EMAIL PROTECTED] writes: Today Kevin Mark poitned out[0] that I should turn a brief outline I gave[1] on how to customize Debian pacakges into a full blown HOWTO. I have done that and the result [2] is now available to the public. I would like to announce it in the hopes that new and experienced Debian developers and users will review it and provide some feedback. After a week or so, I will probably submit it to some Debian-related wikis and websites. But, I first want to make sure that it is in reasonable shape before I *really* present it to the world :-) [2] http://familiasanchez.net/~sanchezr/?page=debcustomize Eep, please don't tell people to give themselves full privileges with sudo unless they know what they're doing. The sudo configuration here is just to run pbuilder, right? If so, just recommend something like: bob ALL = NOPASSWD: /usr/sbin/pbuilder bob ALL = NOPASSWD: /usr/lib/pbuilder/pbuilder-satisfydepends This is sufficient in my experience. Also, note that your sample pbuilder script looks like it was miswrapped; the script is showing up on the same line as the #!/bin/sh line. -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New Debian Package Customization HOWTO
Kevin Mark [EMAIL PROTECTED] writes: I read it and it seems great! Haven't had a change to build anything yet but I'm sure it will help me when I do. a minor typo, search for 'since'. As someone commented, I believe pbuilder does not clean the chroot. pbuilder does always clean the chroot. buildd doesn't always, but it does try to do so (it just doesn't care if it fails). for slow archs like arm and m68k, it would be inefficient to rebuild all the dependencies for building KDE on arm after every change, as an example. The build logs seem to indicate that buildd is generally being that inefficient, unless I'm misreading something. -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New Debian Package Customization HOWTO
On Sat, Jun 04, 2005 at 05:58:18PM -0700, Russ Allbery wrote: Roberto C Sanchez [EMAIL PROTECTED] writes: Today Kevin Mark poitned out[0] that I should turn a brief outline I gave[1] on how to customize Debian pacakges into a full blown HOWTO. I have done that and the result [2] is now available to the public. I would like to announce it in the hopes that new and experienced Debian developers and users will review it and provide some feedback. After a week or so, I will probably submit it to some Debian-related wikis and websites. But, I first want to make sure that it is in reasonable shape before I *really* present it to the world :-) [2] http://familiasanchez.net/~sanchezr/?page=debcustomize Eep, please don't tell people to give themselves full privileges with sudo unless they know what they're doing. The sudo configuration here is just to run pbuilder, right? If so, just recommend something like: bob ALL = NOPASSWD: /usr/sbin/pbuilder bob ALL = NOPASSWD: /usr/lib/pbuilder/pbuilder-satisfydepends This is sufficient in my experience. It won't provide you with any additional security though, so it will only give a false sense of security. If you can run pbuilder with any argument, you can specify an arbitrary configfile, and that way have any arbitrary command run as root. Even if it's only in the chroot, which I didn't check right now, as root in a chroot you can break out and be root on the host system. --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: Is Ubuntu a debian derivative or is it a fork?
On Sat, Jun 04, 2005 at 09:24:54PM +0200, Petter Reinholdtsen wrote: [Matt Zimmerman] Is this judgement based on some experience you had with an Ubuntu developer? The observation (judgement is stretching it too far) is based on my very limited experience with packages in Ubuntu which are/were missing in Debian. I'd like to hear about it, because this is certainly not the common case, and there is an unfortunate amount of myth and rumour on this subject. Oh, it is definitely not the common case. My sample set is ~5 packages, and for most of them the maintainer of the Ubuntu package were very interested in cooperation and co-maintenance. That's the response I'd expect from all of them, so if you could fill me in on the details of the situations where this was *not* the case, please let me know (privately). My point is just that we should be aware of the border cases, and try to find procedures to handle those as well. As always, we should be equipped to cope with border cases if we encounter them, but in this particular scenario, there's no reason for them to exist. -- - mdz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
need help to solve celestia bug#303860
Hi I'm trying to solve bug #303860 but I need some help. The problem is that the configure script errors on sparc because it can't find the KDE libraries. All other architechtures build fine. linda complained that the libtool files were pretty old, so my sponsor suggested to update libtool and pointed me to [1]. Unfortunately, the result after the update is just the same. configure is not able to find the KDE libs. I've asked several people for help now, but even together we weren't able to track the problem down. Best regards Mathias Weyland [1] http://people.debian.org/~keybuk/libtool-updating.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian Java in Sarge
On Sat, 04 Jun 2005 23:49:17 +0200, Josselin Mouette [EMAIL PROTECTED] said: Le vendredi 03 juin 2005 à 18:41 -0500, Adam Heath a écrit : I agree. A java policy should talk about how java packages should interact once installed. But stay the hell away from how they are built. As an example, debhelper, while being very useful for maintainers, is not mandated. That doesn't make not using it less stupid. Right. We can't possible build Debian packages without crutches, hence not using said crutches is stupid. Since, you know, building packages is really really rocket science. The few times I saw a package not using debhelper, it was broken in some way. Ooh. Generalizations. Gotta love 'em. Well, none of my 40-or-so packages use debhelper. This includes stuff like make and flex, which are not exactly obscure and unknown packages. If these are broken in someway, and people know about them, I would appreciate bug reports. If you want to know which packages to look for, here are the links: http://arch.debian.org/arch/private/srivasta/ manoj -- Man is demolishing nature ... We are killing things that keep us alive. Thor Heyerdahl Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/%7Esrivasta/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New Debian Package Customization HOWTO
Jeroen van Wolffelaar [EMAIL PROTECTED] writes: On Sat, Jun 04, 2005 at 05:58:18PM -0700, Russ Allbery wrote: Eep, please don't tell people to give themselves full privileges with sudo unless they know what they're doing. The sudo configuration here is just to run pbuilder, right? If so, just recommend something like: bob ALL = NOPASSWD: /usr/sbin/pbuilder bob ALL = NOPASSWD: /usr/lib/pbuilder/pbuilder-satisfydepends This is sufficient in my experience. It won't provide you with any additional security though, so it will only give a false sense of security. If you can run pbuilder with any argument, you can specify an arbitrary configfile, and that way have any arbitrary command run as root. Even if it's only in the chroot, which I didn't check right now, as root in a chroot you can break out and be root on the host system. Hm, yes, good point. I would still argue for listing the specific commands just for general sudo sanity, but the NOPASSWD is probably a bad idea. I hadn't thought that all the way through. Given that, it's worth a big note on the page that configuring things this way gives that account full root access, meaning that if someone breaks into it, they also have root. That may not be obvious to someone who hasn't done this before. -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New Debian Package Customization HOWTO
On Sat, Jun 04, 2005 at 08:53:06PM -0400, Kevin Mark wrote: Hi Roberto, I read it and it seems great! Haven't had a change to build anything yet but I'm sure it will help me when I do. a minor typo, search for 'since'. As someone commented, I believe pbuilder does not clean the chroot. for slow archs like arm and m68k, it would be inefficient to rebuild all the dependencies for building KDE on arm after every change, as an example. And I dont think someone making a personal packages would want to waste the time to clean it. Keep up the great work, you'll be a DD before Etch (at least I hope so) is released! Cheers, Kev Thanks for the feedback. Someone cleared it up for me in IRC in #debian-devel. I have updated the HOWTO. As far as for building personal packages, you are right. But, as the default pbuilder behavior is to wipe out the temporary chroot after every session, that should work for most people. I haven't read far enough into the docs to find out how to get it preserve the installed packages, but that is because I like being able to build in a clean environment every time and don't have an inclination to change it. But, your point is taken. -Roberto -- Roberto C. Sanchez http://familiasanchez.net/~sanchezr pgp28BT9u5Iu2.pgp Description: PGP signature
Re: New Debian Package Customization HOWTO
* Christoph Wegscheider [Sat, 04 Jun 2005 19:37:46 +0200]: The official Debian packages are built by a buildd, also called build daemon, which makes use of pbuilder to ensure that every package is ^^^ That bit is wrong, buildd/buildds use 'sbuild'. built in a clean environment. -- Adeodato Simó EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621 Capitalism is the extraordinary belief that the nastiest of men, for the nastiest of reasons, will somehow work for the benefit of us all. -- John Maynard Keynes -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New Debian Package Customization HOWTO
On Sat, Jun 04, 2005 at 05:58:18PM -0700, Russ Allbery wrote: Roberto C Sanchez [EMAIL PROTECTED] writes: Today Kevin Mark poitned out[0] that I should turn a brief outline I gave[1] on how to customize Debian pacakges into a full blown HOWTO. I have done that and the result [2] is now available to the public. I would like to announce it in the hopes that new and experienced Debian developers and users will review it and provide some feedback. After a week or so, I will probably submit it to some Debian-related wikis and websites. But, I first want to make sure that it is in reasonable shape before I *really* present it to the world :-) [2] http://familiasanchez.net/~sanchezr/?page=debcustomize Eep, please don't tell people to give themselves full privileges with sudo unless they know what they're doing. The sudo configuration here is just to run pbuilder, right? If so, just recommend something like: bob ALL = NOPASSWD: /usr/sbin/pbuilder bob ALL = NOPASSWD: /usr/lib/pbuilder/pbuilder-satisfydepends This is sufficient in my experience. OK. Done. Also, note that your sample pbuilder script looks like it was miswrapped; the script is showing up on the same line as the #!/bin/sh line. Good call. I missed a br / at the end of the line. -Roberto -- Roberto C. Sanchez http://familiasanchez.net/~sanchezr pgpF9uaolqMvl.pgp Description: PGP signature
Re: New Debian Package Customization HOWTO
On Sun, Jun 05, 2005 at 04:32:39AM +0200, Adeodato Simó wrote: * Christoph Wegscheider [Sat, 04 Jun 2005 19:37:46 +0200]: The official Debian packages are built by a buildd, also called build daemon, which makes use of pbuilder to ensure that every package is ^^^ That bit is wrong, buildd/buildds use 'sbuild'. built in a clean environment. OK. Thanks. Updated: The official Debian packages are built by a buildd, also called build daemon, which make use of sbuild (a package similar in function to pbuilder) to ensure that every package is built in a clean environment (note: some slower architectures do not actually clean after every package build, but the concept is the same). -Roberto -- Roberto C. Sanchez http://familiasanchez.net/~sanchezr pgpfelO3unE7Y.pgp Description: PGP signature
kernel security bug #307900
Hello, Whats the deal with bug #307900? As far as I can tell from reading the bug report, the bug has not been fixed in sarge, will not be fixed for the release, but the bug has been closed. Have we come to the point where making a release is more important then fixing known security bugs? Does this mean people who want secure pre-compiled kernels have to resort to unstable until the issue is fixed? -- Brian May [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Is Ubuntu a debian derivative or is it a fork?
* Petter Reinholdtsen [Sat, 04 Jun 2005 21:01:58 +0200]: [Daniel Holbach] Hello Petter, Daniel, let me pop in. It's my intention to be constructive. I believe we are discussing how to keep the packages in Debian and Ubuntu as synchronized as possible, Specifically, packages in universe. and also encourage people to try to find a DD sponsor to upload the packages both into Debian and into Ubuntu. This will work great if the person has a strong interest both in Debian and in Ubuntu. I have very limited knowledge of the MOTU effort, but I think it is increasingly gaining collaborators that do not have a Debian background, and who start in the packaging world directly via Ubuntu. For them, finding a Debian sponsor and uploading to our archive may be: (a) completely uninteresting, (b) a painful experience. Plus it may not be the ideal situation for Debian either, since uploading a package should imply that bug reports will be taken care of, and other Debian specific bits. For these cases, I believe a co-maintainership scenario would be really best (as Peter mentioned under Group maintenance): a Debian person and an Ubuntu person work together, each taking care of the issues specific to their distribution (e.g. bugs), but on the packaging side they work as closely as possible: common VCS repository and whatever. But, alas, there will not always be an interested DD for each new package that Ubuntu/universe gets, and the difficulty to find a sponsor, specially for non-experienced packagers, doesn't help here either (correct me if I'm wrong, but it seems that getting a sponsored upload to universe happens faster and more easily than a sponsored upload to sid). For that reason, it could make sanse to keep a list of packages that exist in Ubuntu but not in Debian. This could be a Wiki page, or (perhaps even makes more sense) in the RFP/ITP itself, as in (please give feedback on this): - Ubuntu packagers are encouraged to file a RFP/ITP bug against wnnp on bugs.debian.org for each new package they upload - an ITP is filed if they intend to search a for a Debian sponsor and maintain the Debian package themselves, otherwise a RFP is submitted - these ITPs and RFPs carry somewhere in the subject the [Ubuntu] (*) string, so that the set of packages in Ubuntu and not in Debian can be easily found. (*) Or a generic label could be used, e.g. [from-derived-dist]. Cheers, -- Adeodato Simó EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621 Don't ask the barber whether you need a haircut. -- Daniel S. Greenberg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Sex is a play, and you must win!
Little magic. Perfect weekends. http://mwofk.iflb410tfa08m1i.walepiececc.com Imagination is more important than knowledge. I think, therefore Descartes exists. We must become the change we want to see. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New Debian Package Customization HOWTO
In article [EMAIL PROTECTED] you wrote: The official Debian packages are built by a buildd, also called build daemon, which make use of sbuild (a package similar in function to pbuilder) to ensure that every package is built in a clean environment (note: some slower architectures do not actually clean after every package build, but the concept is the same). Which is not true for binary uploads (especially on i386). Those are unfortunatelly official packages without rebuilding and without a clean environment. Gruss Bernd -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted atokx 1.0-17 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 4 Jun 2005 14:56:16 +0900 Source: atokx Binary: atokx Architecture: source i386 Version: 1.0-17 Distribution: experimental Urgency: low Maintainer: Taku YASUI [EMAIL PROTECTED] Changed-By: Taku YASUI [EMAIL PROTECTED] Description: atokx - Kana-Kanji translation system ATOKX for Linux (Installer) Changes: atokx (1.0-17) experimental; urgency=low . * Delete conflict files * Fix dependency - Add Depends: iiimf-htt-server - Add Suggests: iiim-htt-xbe, iiimgcf, iiimecf * Change postinst, prerm, postrm script to delete atokx iiimf * Delete htt_server startup script * dangerous version; upload to experimental Files: 93735817264263cb16e37da51474b338 500 contrib/utils optional atokx_1.0-17.dsc b4ed22b11dbc45271ae2a1390d99b9d9 12366 contrib/utils optional atokx_1.0-17.tar.gz 9787beddc88a954ea367bea410a7474f 11414 contrib/utils optional atokx_1.0-17_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCoUKVFwU5DuZsm7ARAn6WAJ0b3zHASef90IWSt9aG0TYE3DkuqgCgt0nx WxouQs4AQEI8j4tt/WGWNcs= =/IH/ -END PGP SIGNATURE- Accepted: atokx_1.0-17.dsc to pool/contrib/a/atokx/atokx_1.0-17.dsc atokx_1.0-17.tar.gz to pool/contrib/a/atokx/atokx_1.0-17.tar.gz atokx_1.0-17_i386.deb to pool/contrib/a/atokx/atokx_1.0-17_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted liblogkit-java 1.2.2-3 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 4 Jun 2005 08:44:16 +0200 Source: liblogkit-java Binary: liblogkit-java Architecture: source all Version: 1.2.2-3 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers [EMAIL PROTECTED] Changed-By: Arnaud Vandyck [EMAIL PROTECTED] Description: liblogkit-java - Lightweight and fast designed logging toolkit for Java Closes: 311055 Changes: liblogkit-java (1.2.2-3) unstable; urgency=low . * build system to cdbs, thanks to Jan Alonzo (closes: #311055) * added myself as an uploader * added a debian/watch file Files: d71ceeb9df7e83584601b520b57e8967 805 libs optional liblogkit-java_1.2.2-3.dsc 44c2bf6d1b56a993cca37c2485ad3867 4249 libs optional liblogkit-java_1.2.2-3.diff.gz 198018f86cb2aad5b06e4ab6bcc95f15 61196 libs optional liblogkit-java_1.2.2-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCoU6v4vzFZu62tMIRAjuPAJ9E55SA6St9yMZSokyl6LqQi2yk4ACfW9TW wy9G4LwYkgrLXyqIC0OpK98= =zDe3 -END PGP SIGNATURE- Accepted: liblogkit-java_1.2.2-3.diff.gz to pool/main/libl/liblogkit-java/liblogkit-java_1.2.2-3.diff.gz liblogkit-java_1.2.2-3.dsc to pool/main/libl/liblogkit-java/liblogkit-java_1.2.2-3.dsc liblogkit-java_1.2.2-3_all.deb to pool/main/libl/liblogkit-java/liblogkit-java_1.2.2-3_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fdutils 5.5-20050303-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 04 Jun 2005 18:15:35 +1000 Source: fdutils Binary: fdutils Architecture: source i386 Version: 5.5-20050303-1 Distribution: unstable Urgency: low Maintainer: Anibal Monsalve Salazar [EMAIL PROTECTED] Changed-By: Anibal Monsalve Salazar [EMAIL PROTECTED] Description: fdutils- Linux floppy utilities Closes: 311097 311647 311693 Changes: fdutils (5.5-20050303-1) unstable; urgency=low . * New upstream release. * Added Vietnamese debconf translation, closes: #311647. Patch by Clytie Siddall [EMAIL PROTECTED]. * Added French debconf translation, closes: #311693. Patch by Steve [EMAIL PROTECTED]. * Added Czech debconf translation, closes: #311097. Patch by Martin Sín [EMAIL PROTECTED]. Files: 5e290f6b6d114bdb59d2225d5a406ce9 631 base optional fdutils_5.5-20050303-1.dsc 2b8b65f52378158a4a21e455566b456d 222801 base optional fdutils_5.5-20050303.orig.tar.gz 46b1ce03c9adc2c346c8cf0597a29fd9 18700 base optional fdutils_5.5-20050303-1.diff.gz 551ce58ad6e19a0987a1138f9e70be40 346582 base optional fdutils_5.5-20050303-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCoW4JgY5NIXPNpFURApQ0AJ9fJFY9WpB3z7K7bHn7M8GYNyWGfwCgyqrE k5r5hwQl/RUULdbt0Y0H03s= =3+fq -END PGP SIGNATURE- Accepted: fdutils_5.5-20050303-1.diff.gz to pool/main/f/fdutils/fdutils_5.5-20050303-1.diff.gz fdutils_5.5-20050303-1.dsc to pool/main/f/fdutils/fdutils_5.5-20050303-1.dsc fdutils_5.5-20050303-1_i386.deb to pool/main/f/fdutils/fdutils_5.5-20050303-1_i386.deb fdutils_5.5-20050303.orig.tar.gz to pool/main/f/fdutils/fdutils_5.5-20050303.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted xpad 2.7-1 (sparc source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 4 Jun 2005 09:11:45 +0200 Source: xpad Binary: xpad Architecture: source sparc Version: 2.7-1 Distribution: experimental Urgency: low Maintainer: Søren Boll Overgaard [EMAIL PROTECTED] Changed-By: Søren Boll Overgaard [EMAIL PROTECTED] Description: xpad - sticky note application for X Changes: xpad (2.7-1) experimental; urgency=low . * New upstream release Files: 52b3df7dc33e37793d79be462df5a81c 605 x11 optional xpad_2.7-1.dsc 99cf2383b0152693dabe55fdb867fc1d 236757 x11 optional xpad_2.7.orig.tar.gz 75d1288906c0c861d268e4aec7b47427 87013 x11 optional xpad_2.7-1.diff.gz 822beccc121ea184e741f512c408d9d1 63364 x11 optional xpad_2.7-1_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCoXFsPHuHUx6y3mYRArjJAKC/2UEIBs0x+K4XHdNjQ8+hYCeWeQCgmw64 3XVLkOohefTsjPyOBdYH1bM= =gZ8o -END PGP SIGNATURE- Accepted: xpad_2.7-1.diff.gz to pool/main/x/xpad/xpad_2.7-1.diff.gz xpad_2.7-1.dsc to pool/main/x/xpad/xpad_2.7-1.dsc xpad_2.7-1_sparc.deb to pool/main/x/xpad/xpad_2.7-1_sparc.deb xpad_2.7.orig.tar.gz to pool/main/x/xpad/xpad_2.7.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted discover1 1.7.8 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 3 Jun 2005 22:20:49 -0700 Source: discover1 Binary: libdiscover1 discover1 libdiscover1-pic discover1-udeb libdiscover1-dev Architecture: source i386 Version: 1.7.8 Distribution: unstable Urgency: low Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Joshua Kwan [EMAIL PROTECTED] Description: discover1 - hardware identification system discover1-udeb - hardware identification library (udeb) (udeb) libdiscover1 - hardware identification library libdiscover1-dev - hardware identification library development files libdiscover1-pic - hardware identification library - static PIC version Closes: 195971 196011 196016 223816 255103 268255 270290 270674 273824 286000 295431 295505 307163 Changes: discover1 (1.7.8) unstable; urgency=low . * Translations - Updated Romanian programs translation, thanks Eddy. closes: #295431 - Updated Polish programs translation, thanks Marek. closes: #295505 - Removed broken vi_VN.VISCII translation - Added (indeed replaced) Vietnamese translation. Closes: #307163 - Updated Greek programs translation, thanks Konstantinos. - Spell-checked the French translation. * Rip out CD-ROM mountpoint detection, pointless and always broken. (Consequently, we no longer need a debconf script, template translation or configuration file at all.) closes: #255103, #268255, #270290, #270674, #273824, #286000, #223816 * Rip out initrd support, pointless and always broken. closes: #196011, #195971, #196016 * David Nusinow - Update my email address Files: 466513ce582f1447074558973f1e0091 1456 admin optional discover1_1.7.8.dsc faa2ee57c89abc2b07b0da926ce84eaa 593866 admin optional discover1_1.7.8.tar.gz 69f39eb0803b877de33daba1f02031fe 65796 admin optional discover1_1.7.8_i386.deb 0e762adf330ca6d8e7002ea998a06e14 95084 libs optional libdiscover1_1.7.8_i386.deb a9fdbb914466ff618551d03bb3105c7c 58090 libdevel optional libdiscover1-dev_1.7.8_i386.deb dd594507e18df688bb598b665db88468 56694 libs extra libdiscover1-pic_1.7.8_i386.deb b209f617eb6090cf68f119bce2fcfd4c 34570 debian-installer extra discover1-udeb_1.7.8_i386.udeb package-type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: http://triplehelix.org/~joshk/pubkey_gpg.asc iQIVAwUBQqFwMKOILr94RG8mAQKn8g/8Cs9pxua+4TPoqPyvU3DaK36eM3h8780J azPPFN1LpHzHqDiTbdsuOP+lw5xuCzWAQgaOnYr9NycuFgbo9ChFNFcAEc9aDKsd GVj2smUvNgsK6uFJCiX7vDk4gpX6O571NWMBONH+uwuwzWITiYR81Y1Mp66DMK7u M99mT/+Tk9n1Bua1C6eDKRlgEf1UWx2J3P/ZxhQylk5TCqZDanSGmbEubFOz3Mcn TgQmGzotDZEPHNOlw2ML5XCxaaiAKT6icJwWze5ofKahauP0a1325sWzJCEh0cA5 QbmYePQ0NzyF5j1Rzwbx8koTfaNXBnuRdwXzIVC/n+kPDXsOFXl0Tbxbmh8qg7+p jWVgP3sT1b2K47gOtRxeoNaKmj+EwtYCLNcibzVKyhg87lh8444sKQO1wxh8szSN E5glcQKv107VgE4HxjQPt/p4rOOZKttI3yetQgNG8v4280IjEYm5QZM8odxanFqk pm0Ep8qxI7B/OIEY8UYHF0TQXyKWTZx3X447nIY6UxcOQPogXYjYMqAr4zjlKoX0 uqiBBd/mSGDMsvw5NYSvui6Cvyn9sxujRswrOjhM1l/jmOSmJeey5YPw/+/6jZ/0 7M9ckkxXEZyyWYoyShmPcfoFRyZamnP8x7ONXTluhn4rf5p3+fDhZxWd2G/DBRFI 5E5Zp14d6E8= =AFo6 -END PGP SIGNATURE- Accepted: discover1-udeb_1.7.8_i386.udeb to pool/main/d/discover1/discover1-udeb_1.7.8_i386.udeb discover1_1.7.8.dsc to pool/main/d/discover1/discover1_1.7.8.dsc discover1_1.7.8.tar.gz to pool/main/d/discover1/discover1_1.7.8.tar.gz discover1_1.7.8_i386.deb to pool/main/d/discover1/discover1_1.7.8_i386.deb libdiscover1-dev_1.7.8_i386.deb to pool/main/d/discover1/libdiscover1-dev_1.7.8_i386.deb libdiscover1-pic_1.7.8_i386.deb to pool/main/d/discover1/libdiscover1-pic_1.7.8_i386.deb libdiscover1_1.7.8_i386.deb to pool/main/d/discover1/libdiscover1_1.7.8_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gauche 0.8.4-1 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 3 Jun 2005 21:14:37 +0900 Source: gauche Binary: gauche-dev gauche-doc gauche-gdbm gauche Architecture: source all i386 Version: 0.8.4-1 Distribution: unstable Urgency: low Maintainer: Hatta Shuzo [EMAIL PROTECTED] Changed-By: YAEGASHI Takeshi [EMAIL PROTECTED] Description: gauche - A Scheme implementation designed for script writing gauche-dev - Development files for Gauche gauche-doc - Reference manual of Gauche gauche-gdbm - gdbm binding for Gauche Changes: gauche (0.8.4-1) unstable; urgency=low . * New upstream release. * Build in build-tree extracted from the upstream tarball. * debian/patches/02_arm_double_fix.patch: Removed. * debian/watch: s/cognet/cogent/. Files: b268c16f98f82ed25a0ef0c153e1c7cd 699 interpreters optional gauche_0.8.4-1.dsc dd17db92c7fd168cf8925c098c9fc149 2766244 interpreters optional gauche_0.8.4.orig.tar.gz eda69156f6b23f1671bc6e81b909fd17 8100 interpreters optional gauche_0.8.4-1.diff.gz 4d8c7515ac0b55fb50046bd8331a07f6 1337186 interpreters optional gauche_0.8.4-1_i386.deb 621ce6b2e4c4de26d179937cfb0121c9 94564 interpreters optional gauche-gdbm_0.8.4-1_i386.deb eafdf95ad1ac9ac37944a1efa7c3d04a 165740 devel optional gauche-dev_0.8.4-1_i386.deb 28e3f6d6fc3a693cf6d415700b11ec90 748506 doc optional gauche-doc_0.8.4-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCoXdSb+p+JlbwbQERAj77AJwP6R2bgPlquJFqSN5h768rm1jliACeLnhc U6UDZFUYB7MFxk4RMyJ1bcU= =jE2m -END PGP SIGNATURE- Accepted: gauche-dev_0.8.4-1_i386.deb to pool/main/g/gauche/gauche-dev_0.8.4-1_i386.deb gauche-doc_0.8.4-1_all.deb to pool/main/g/gauche/gauche-doc_0.8.4-1_all.deb gauche-gdbm_0.8.4-1_i386.deb to pool/main/g/gauche/gauche-gdbm_0.8.4-1_i386.deb gauche_0.8.4-1.diff.gz to pool/main/g/gauche/gauche_0.8.4-1.diff.gz gauche_0.8.4-1.dsc to pool/main/g/gauche/gauche_0.8.4-1.dsc gauche_0.8.4-1_i386.deb to pool/main/g/gauche/gauche_0.8.4-1_i386.deb gauche_0.8.4.orig.tar.gz to pool/main/g/gauche/gauche_0.8.4.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted wiliki 0.5.1-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 3 Jun 2005 21:47:24 +0900 Source: wiliki Binary: wiliki Architecture: source all Version: 0.5.1-1 Distribution: unstable Urgency: low Maintainer: YAEGASHI Takeshi [EMAIL PROTECTED] Changed-By: YAEGASHI Takeshi [EMAIL PROTECTED] Description: wiliki - Yet another Wiki clone written in Scheme Changes: wiliki (0.5.1-1) unstable; urgency=low . * New upstream release. Files: b9f23a9fde6b5d88d2394bc1c02fd322 588 web optional wiliki_0.5.1-1.dsc e11631eb5388b64dea3966695d7b0502 108329 web optional wiliki_0.5.1.orig.tar.gz f1460cdaa501f2f37cf408d61f3e217c 4559 web optional wiliki_0.5.1-1.diff.gz 8abd5a40d05c007409c99873090cfa4b 51590 web optional wiliki_0.5.1-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCoXabb+p+JlbwbQERAmDYAJ4uF9O4iJCJsVMXp5gS0IuWxBEJFACfY6vT l1jfbgnIr/tNFf4SFm/O4wk= =WUWg -END PGP SIGNATURE- Accepted: wiliki_0.5.1-1.diff.gz to pool/main/w/wiliki/wiliki_0.5.1-1.diff.gz wiliki_0.5.1-1.dsc to pool/main/w/wiliki/wiliki_0.5.1-1.dsc wiliki_0.5.1-1_all.deb to pool/main/w/wiliki/wiliki_0.5.1-1_all.deb wiliki_0.5.1.orig.tar.gz to pool/main/w/wiliki/wiliki_0.5.1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gauche-gtk 0.4.1-3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 4 Jun 2005 01:52:48 +0900 Source: gauche-gtk Binary: gauche-gtk Architecture: source i386 Version: 0.4.1-3 Distribution: unstable Urgency: low Maintainer: NIIBE Yutaka [EMAIL PROTECTED] Changed-By: NIIBE Yutaka [EMAIL PROTECTED] Description: gauche-gtk - Gauche bindings for GTK+ GUI Toolkit Changes: gauche-gtk (0.4.1-3) unstable; urgency=low . * Build with newer gauche. Files: 143d805016833b2ae6de7d7182291743 698 interpreters optional gauche-gtk_0.4.1-3.dsc ad072a8f7f3194d0dc3888601a68738a 32915 interpreters optional gauche-gtk_0.4.1-3.diff.gz 89fa62fc062a6d0e9fa7c15107c0026b 573876 interpreters optional gauche-gtk_0.4.1-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCoXsnb+p+JlbwbQERAjKAAJ4tqZeJAEY9JwoUVTPBSENjZ6dCVwCfRu4M XKLlPdI0jEJv6swJjhHZvV0= =jKbv -END PGP SIGNATURE- Accepted: gauche-gtk_0.4.1-3.diff.gz to pool/main/g/gauche-gtk/gauche-gtk_0.4.1-3.diff.gz gauche-gtk_0.4.1-3.dsc to pool/main/g/gauche-gtk/gauche-gtk_0.4.1-3.dsc gauche-gtk_0.4.1-3_i386.deb to pool/main/g/gauche-gtk/gauche-gtk_0.4.1-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gauche-gl 0.3.1-8 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 4 Jun 2005 03:47:13 +0900 Source: gauche-gl Binary: gauche-gl Architecture: source i386 Version: 0.3.1-8 Distribution: unstable Urgency: low Maintainer: NIIBE Yutaka [EMAIL PROTECTED] Changed-By: NIIBE Yutaka [EMAIL PROTECTED] Description: gauche-gl - Gauche bindings for OpenGL Changes: gauche-gl (0.3.1-8) unstable; urgency=low . * Build with newer gauche. Files: 4fad3f3ee7df8fee0b23bfe2515f8ebc 640 interpreters optional gauche-gl_0.3.1-8.dsc 3e01250f7fcf0d409245af7e0b547697 30805 interpreters optional gauche-gl_0.3.1-8.diff.gz c1dafc4699af222b271612ebb0fc3f33 169884 interpreters optional gauche-gl_0.3.1-8_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCoXtcb+p+JlbwbQERAh3YAJ9nS+3TOkvWfxG88tguLsEetdto9wCfRWGU EWLwNZ28Yn8OxkXtlxsUd1Y= =IRfr -END PGP SIGNATURE- Accepted: gauche-gl_0.3.1-8.diff.gz to pool/main/g/gauche-gl/gauche-gl_0.3.1-8.diff.gz gauche-gl_0.3.1-8.dsc to pool/main/g/gauche-gl/gauche-gl_0.3.1-8.dsc gauche-gl_0.3.1-8_i386.deb to pool/main/g/gauche-gl/gauche-gl_0.3.1-8_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted tramp 1:2.0.49-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 28 May 2005 14:32:27 +0200 Source: tramp Binary: tramp Architecture: source all Version: 1:2.0.49-1 Distribution: unstable Urgency: low Maintainer: Jerome Marant [EMAIL PROTECTED] Changed-By: Jerome Marant [EMAIL PROTECTED] Description: tramp - remote file access in Emacs Changes: tramp (1:2.0.49-1) unstable; urgency=low . * New upstream release. Files: b46f99d4bc6ca2ab414cd091dbb4fe9d 601 editors optional tramp_2.0.49-1.dsc fc502b963658f50d2daf3ac40e0b1a95 295674 editors optional tramp_2.0.49.orig.tar.gz c1aa0c4b5e85852dfb60de65125039a3 7077 editors optional tramp_2.0.49-1.diff.gz 5ef81fc3897e28c5f80668285deccb68 256860 editors optional tramp_2.0.49-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD4DBQFCoYCC3JE9mF3wMWcRAhQcAJjiStP6zQm/G2xA3X6AyupNW1/KAJ9cWM4J yPR0EUYlZ7p8zQcmcyWpww== =UbPY -END PGP SIGNATURE- Accepted: tramp_2.0.49-1.diff.gz to pool/main/t/tramp/tramp_2.0.49-1.diff.gz tramp_2.0.49-1.dsc to pool/main/t/tramp/tramp_2.0.49-1.dsc tramp_2.0.49-1_all.deb to pool/main/t/tramp/tramp_2.0.49-1_all.deb tramp_2.0.49.orig.tar.gz to pool/main/t/tramp/tramp_2.0.49.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted ocamlsdl 0.7.2-2 (powerpc source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 4 Jun 2005 12:15:52 +0200 Source: ocamlsdl Binary: libsdl-ocaml-dev libsdl-ocaml Architecture: source powerpc Version: 0.7.2-2 Distribution: unstable Urgency: low Maintainer: Jerome Marant [EMAIL PROTECTED] Changed-By: Jerome Marant [EMAIL PROTECTED] Description: libsdl-ocaml - OCaml bindings for SDL - runtime files libsdl-ocaml-dev - OCaml bindings for SDL - development files Closes: 311121 Changes: ocamlsdl (0.7.2-2) unstable; urgency=low . * debian/libsdl-ocaml-dev.doc-base: move documentation from `Devel' to `Apps/Programming' section. Closes: Bug#311121. Files: 634dcb6bb4c6decd519bfd2514dbc34b 775 devel optional ocamlsdl_0.7.2-2.dsc 7fe6f9c7addabe8290553cbbe3e6ed2a 5602 devel optional ocamlsdl_0.7.2-2.diff.gz 7a03669ca59346aa8e13ddc1fa08e4e9 157664 libdevel optional libsdl-ocaml-dev_0.7.2-2_powerpc.deb ac70632c06a0863dff634e24e9ee0689 35262 libs optional libsdl-ocaml_0.7.2-2_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCoX/Z3JE9mF3wMWcRAgJ8AJ9wWR8QUC0Tc15mwBotvF/8/aZZZACfft3t UzlUyPtYbv8i+LYNdJb8wEE= =+i3z -END PGP SIGNATURE- Accepted: libsdl-ocaml-dev_0.7.2-2_powerpc.deb to pool/main/o/ocamlsdl/libsdl-ocaml-dev_0.7.2-2_powerpc.deb libsdl-ocaml_0.7.2-2_powerpc.deb to pool/main/o/ocamlsdl/libsdl-ocaml_0.7.2-2_powerpc.deb ocamlsdl_0.7.2-2.diff.gz to pool/main/o/ocamlsdl/ocamlsdl_0.7.2-2.diff.gz ocamlsdl_0.7.2-2.dsc to pool/main/o/ocamlsdl/ocamlsdl_0.7.2-2.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted rsync 2.6.5-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 3 Jun 2005 19:17:28 +0200 Source: rsync Binary: rsync Architecture: source i386 Version: 2.6.5-1 Distribution: unstable Urgency: low Maintainer: Paul Slootman [EMAIL PROTECTED] Changed-By: Paul Slootman [EMAIL PROTECTED] Description: rsync - fast remote file copy program (like rcp) Changes: rsync (2.6.5-1) unstable; urgency=low . * new upstream version. Contains the patches previously applied in 2.6.4-3 from CVS. * Now should handle locale-specific characters better in logging output (i.e. the correct chars should be displayed, not '?'). Files: ac5400324493ebc2c0c1d28b125cd866 543 net optional rsync_2.6.5-1.dsc 3691cdf1540d0649ba679edce6bae8fc 643388 net optional rsync_2.6.5.orig.tar.gz 65fab3f70f45d0af320cb9c38db36ea7 52328 net optional rsync_2.6.5-1.diff.gz b85e9a5aef22386f2eed08550f729455 207664 net optional rsync_2.6.5-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFCoYn5utvvqbTW3hMRAlKJAJsFDfvnQqUlat2+IpGRcI4ihYTS5QCcD4AC oKAJh7cSwmRfTNbwR6a5J5s= =rySK -END PGP SIGNATURE- Accepted: rsync_2.6.5-1.diff.gz to pool/main/r/rsync/rsync_2.6.5-1.diff.gz rsync_2.6.5-1.dsc to pool/main/r/rsync/rsync_2.6.5-1.dsc rsync_2.6.5-1_i386.deb to pool/main/r/rsync/rsync_2.6.5-1_i386.deb rsync_2.6.5.orig.tar.gz to pool/main/r/rsync/rsync_2.6.5.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted scponly 4.0-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 3 Jun 2005 16:44:29 +0200 Source: scponly Binary: scponly Architecture: source i386 Version: 4.0-2 Distribution: unstable Urgency: low Maintainer: Thomas Wana [EMAIL PROTECTED] Changed-By: Thomas Wana [EMAIL PROTECTED] Description: scponly- Restricts the commands available to scp- and sftp-users Closes: 289861 290671 295910 301129 Changes: scponly (4.0-2) unstable; urgency=low . * Changed ssh dependency to ssh | openssh-server (Closes: #290671) * Fixed compilation error with certain configuration flags (Closes: #289861) * Added the equal sign '=' to the list of allowed characters (Closes: #301129) * Fixed spelling error in man page (Closes: #295910) Files: 963a678d236cf0f4c2a0bf29b813792d 588 utils optional scponly_4.0-2.dsc f2c704af247e4dc1d70c5401914c4923 26774 utils optional scponly_4.0-2.diff.gz 6e0bc730b5a58912f5ce19fd5d689d2d 29350 utils optional scponly_4.0-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCoY7eQyJdaY/AMSgRAipxAJ0eLNz8Tkn3rgBSBZTJO0jvNTUAGQCfS7XM yHc9k6W2Y1cenZ0cMc9kQtY= =SDyp -END PGP SIGNATURE- Accepted: scponly_4.0-2.diff.gz to pool/main/s/scponly/scponly_4.0-2.diff.gz scponly_4.0-2.dsc to pool/main/s/scponly/scponly_4.0-2.dsc scponly_4.0-2_i386.deb to pool/main/s/scponly/scponly_4.0-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mysql-dfsg-4.1 4.1.12-1 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 4 Jun 2005 05:49:11 +0200 Source: mysql-dfsg-4.1 Binary: libmysqlclient14-dev mysql-common-4.1 libmysqlclient14 mysql-server-4.1 mysql-client-4.1 Architecture: source i386 all Version: 4.1.12-1 Distribution: unstable Urgency: low Maintainer: Christian Hammers [EMAIL PROTECTED] Changed-By: Christian Hammers [EMAIL PROTECTED] Description: libmysqlclient14 - mysql database client library libmysqlclient14-dev - mysql database development files mysql-client-4.1 - mysql database client binaries mysql-common-4.1 - mysql database common files (e.g. /etc/mysql/my.cnf) mysql-server-4.1 - mysql database server binaries Closes: 310197 310263 310526 Changes: mysql-dfsg-4.1 (4.1.12-1) unstable; urgency=low . * Christian Hammers: - New upstream release. - Disabled BerkeleyDB finally. It has been obsoleted by InnoDB. * Sean Finney: - Updated French translation from Christian Perrier (Closes: #310526). - Updated Japanese translation from Hideki Yamane (Closes: #310263). - Updated Russian translation from Yuriy Talakan (Closes: #310197). Files: 00c2cc149bcdf63074e4c1bb10136876 1014 misc optional mysql-dfsg-4.1_4.1.12-1.dsc c7b83a19bd8a4f42d5d64c239d05121f 15921909 misc optional mysql-dfsg-4.1_4.1.12.orig.tar.gz d2d8506fa00d540d7ce656cfbcafc10b 160226 misc optional mysql-dfsg-4.1_4.1.12-1.diff.gz 56538a59261a5043091b9cdfcbf2492c 35516 misc optional mysql-common-4.1_4.1.12-1_all.deb d29859bf3d8e0ab32362d94cc12de7de 1498798 libs optional libmysqlclient14_4.1.12-1_i386.deb 87a167500014ffd93559563da76d8a68 5393718 libdevel optional libmysqlclient14-dev_4.1.12-1_i386.deb 7170879a3a235ecdc2c32b653b4483bc 874212 misc optional mysql-client-4.1_4.1.12-1_i386.deb 950da58a425cc059a3d884928c48207e 15021850 misc optional mysql-server-4.1_4.1.12-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iEYEARECAAYFAkKhjrcACgkQkR9K5oahGOYsPgCfc0W9vmBooh+j7FPbk0YrkggB 9OoAnR17MgZTbNjFIB6RWaQ9Y5ohP4hn =ABGM -END PGP SIGNATURE- Accepted: libmysqlclient14-dev_4.1.12-1_i386.deb to pool/main/m/mysql-dfsg-4.1/libmysqlclient14-dev_4.1.12-1_i386.deb libmysqlclient14_4.1.12-1_i386.deb to pool/main/m/mysql-dfsg-4.1/libmysqlclient14_4.1.12-1_i386.deb mysql-client-4.1_4.1.12-1_i386.deb to pool/main/m/mysql-dfsg-4.1/mysql-client-4.1_4.1.12-1_i386.deb mysql-common-4.1_4.1.12-1_all.deb to pool/main/m/mysql-dfsg-4.1/mysql-common-4.1_4.1.12-1_all.deb mysql-dfsg-4.1_4.1.12-1.diff.gz to pool/main/m/mysql-dfsg-4.1/mysql-dfsg-4.1_4.1.12-1.diff.gz mysql-dfsg-4.1_4.1.12-1.dsc to pool/main/m/mysql-dfsg-4.1/mysql-dfsg-4.1_4.1.12-1.dsc mysql-dfsg-4.1_4.1.12.orig.tar.gz to pool/main/m/mysql-dfsg-4.1/mysql-dfsg-4.1_4.1.12.orig.tar.gz mysql-server-4.1_4.1.12-1_i386.deb to pool/main/m/mysql-dfsg-4.1/mysql-server-4.1_4.1.12-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gsoap 2.7.0d-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 4 Jun 2005 13:29:49 +0200 Source: gsoap Binary: gsoap Architecture: source i386 Version: 2.7.0d-2 Distribution: unstable Urgency: low Maintainer: Thomas Wana [EMAIL PROTECTED] Changed-By: Thomas Wana [EMAIL PROTECTED] Description: gsoap - SOAP stub and skeleton compiler for C and C++ Closes: 310582 Changes: gsoap (2.7.0d-2) unstable; urgency=low . * Package now includes header files needed for soapcpp2 to work with files generated from wsdl2h (Closes: #310582) Files: 536a72b1d33cc3cbb9afc1af8687a075 592 devel optional gsoap_2.7.0d-2.dsc 78ed0833905440ba538758ec031ae026 36914 devel optional gsoap_2.7.0d-2.diff.gz dacdcfd25b3bf2ea9e45e46ed21131ea 1282908 devel optional gsoap_2.7.0d-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCoZI2QyJdaY/AMSgRAp/WAKCm6hpiRh3JOwQyI2qHGhKCPQXEZQCgly8h 0Sw5Xn6qUcgmQqdgnJscyVo= =l6YB -END PGP SIGNATURE- Accepted: gsoap_2.7.0d-2.diff.gz to pool/main/g/gsoap/gsoap_2.7.0d-2.diff.gz gsoap_2.7.0d-2.dsc to pool/main/g/gsoap/gsoap_2.7.0d-2.dsc gsoap_2.7.0d-2_i386.deb to pool/main/g/gsoap/gsoap_2.7.0d-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted quagga 0.99.1-2 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 4 Jun 2005 14:04:01 +0200 Source: quagga Binary: quagga quagga-doc Architecture: source i386 all Version: 0.99.1-2 Distribution: unstable Urgency: low Maintainer: Christian Hammers [EMAIL PROTECTED] Changed-By: Christian Hammers [EMAIL PROTECTED] Description: quagga - unoff. successor of the Zebra BGP/OSPF/RIP routing daemon quagga-doc - documentation files for quagga Closes: 306840 Changes: quagga (0.99.1-2) unstable; urgency=low . * Fixed SNMP enabled command in debian/rules (thanks to Christoph Kluenter). Closes: #306840 Files: 0daf04ba0c39a1fb083331a4beb9725e 721 net optional quagga_0.99.1-2.dsc ff86d73e91f5789a651a78c30b61199a 24379 net optional quagga_0.99.1-2.diff.gz e82fc851da25340ae0d8252406a9af46 579748 net optional quagga-doc_0.99.1-2_all.deb eaa5c4e07ad48d9d1ce1208e959d0680 1240172 net optional quagga_0.99.1-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iEYEARECAAYFAkKhm6QACgkQkR9K5oahGOb+VACcDdHlC1aPGW2aMJZam9DBVBX5 K1kAoNKPcvcb82SbTU2o+uqFxmrZCQLT =h2yX -END PGP SIGNATURE- Accepted: quagga-doc_0.99.1-2_all.deb to pool/main/q/quagga/quagga-doc_0.99.1-2_all.deb quagga_0.99.1-2.diff.gz to pool/main/q/quagga/quagga_0.99.1-2.diff.gz quagga_0.99.1-2.dsc to pool/main/q/quagga/quagga_0.99.1-2.dsc quagga_0.99.1-2_i386.deb to pool/main/q/quagga/quagga_0.99.1-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted httrack 3.33.16-1 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 4 Jun 2005 14:12:13 +0200 Source: httrack Binary: libhttrack1 httrack httrack-doc libhttrack-dev webhttrack Architecture: source i386 all Version: 3.33.16-1 Distribution: unstable Urgency: medium Maintainer: Xavier Roche [EMAIL PROTECTED] Changed-By: Xavier Roche [EMAIL PROTECTED] Description: httrack- Copy websites to your computer (Offline browser) httrack-doc - Httrack website copier additional documentation libhttrack-dev - Httrack website copier includes and development files libhttrack1 - Httrack website copier library webhttrack - Copy websites to your computer, httrack with a Web interface Changes: httrack (3.33.16-1) unstable; urgency=medium . * Updated to 3.33.16 (added security network limiter) Files: 141e2462fabb1ff0d3a37c0737851d6f 641 web optional httrack_3.33.16-1.dsc cd21a49afb9630a49d042936ccff3c0b 1432715 web optional httrack_3.33.16.orig.tar.gz 7728a53038286ac552d1f9a813f790bb 5770 web optional httrack_3.33.16-1.diff.gz 7e8043d77c4e4aa0e288a40a8494a333 493402 doc optional httrack-doc_3.33.16-1_all.deb 9640d51576cbe8c1b6a7dc75c1944da5 31172 web optional httrack_3.33.16-1_i386.deb 180b9bc19d4c4e1061ac57d228cc3fa2 418630 web optional webhttrack_3.33.16-1_i386.deb b9bdc4116491285f1b6d4e9339379dde 392286 libs optional libhttrack1_3.33.16-1_i386.deb f0f33dcd8158c18fce9d42a4ebe9ac24 539180 libdevel optional libhttrack-dev_3.33.16-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFCoZ613PjWWwPzWYgRAg8JAJ9kg4XaAbd0vPONZeTGytRmypfjxQCfZgzG czbrfrfOuXr7HML6EiaGoIE= =E92M -END PGP SIGNATURE- Accepted: httrack-doc_3.33.16-1_all.deb to pool/main/h/httrack/httrack-doc_3.33.16-1_all.deb httrack_3.33.16-1.diff.gz to pool/main/h/httrack/httrack_3.33.16-1.diff.gz httrack_3.33.16-1.dsc to pool/main/h/httrack/httrack_3.33.16-1.dsc httrack_3.33.16-1_i386.deb to pool/main/h/httrack/httrack_3.33.16-1_i386.deb httrack_3.33.16.orig.tar.gz to pool/main/h/httrack/httrack_3.33.16.orig.tar.gz libhttrack-dev_3.33.16-1_i386.deb to pool/main/h/httrack/libhttrack-dev_3.33.16-1_i386.deb libhttrack1_3.33.16-1_i386.deb to pool/main/h/httrack/libhttrack1_3.33.16-1_i386.deb webhttrack_3.33.16-1_i386.deb to pool/main/h/httrack/webhttrack_3.33.16-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted bglibs 1.020-3 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 4 Jun 2005 12:31:39 + Source: bglibs Binary: bglibs-doc bglibs-dev Architecture: all source Version: 1.020-3 Distribution: unstable Urgency: low Maintainer: Gerrit Pape [EMAIL PROTECTED] Changed-By: Gerrit Pape [EMAIL PROTECTED] Description: bglibs-dev - Bruce Guenter's one stop library package bglibs-doc - Bruce Guenter's one stop library package (documentation) Changes: bglibs (1.020-3) unstable; urgency=low . * debian/diff/va_foo.diff: new (fixes build failure on ia64, ppc). * debian/rules: apply diff. Files: 73d920dde4e164609e2573610da090cf 634 - optional bglibs_1.020-3.dsc 1474efe24f5e20cb2d3fb253e72709c5 5191 - optional bglibs_1.020-3.diff.gz 65f5f879a4548d180531ef43e8a39d4b 149498 doc optional bglibs-doc_1.020-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCoaQ8GJoyQbxwpv8RApniAJ9wib1p+XLW0MmR6EdknDg++teNFwCfTqrB FMsXGRQOJwco403C57xRY9g= =xzJa -END PGP SIGNATURE- Accepted: bglibs-doc_1.020-3_all.deb to pool/main/b/bglibs/bglibs-doc_1.020-3_all.deb bglibs_1.020-3.diff.gz to pool/main/b/bglibs/bglibs_1.020-3.diff.gz bglibs_1.020-3.dsc to pool/main/b/bglibs/bglibs_1.020-3.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted holotz-castle 1.3.6-1 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 11 May 2005 00:37:00 +0100 Source: holotz-castle Binary: holotz-castle-editor holotz-castle holotz-castle-data Architecture: source i386 all Version: 1.3.6-1 Distribution: unstable Urgency: low Maintainer: Miriam Ruiz [EMAIL PROTECTED] Changed-By: Miriam Ruiz [EMAIL PROTECTED] Description: holotz-castle - platform game with high doses of mystery holotz-castle-data - platform game with high doses of mystery - data files holotz-castle-editor - platform game with high doses of mystery - level editor Closes: 304715 Changes: holotz-castle (1.3.6-1) unstable; urgency=low . * New Upstream Version. * Solves endianess problems and works in PowerPCs now. Closes: #304715. Files: cb92e7b5402c8679874835af6d03bdfe 705 games optional holotz-castle_1.3.6-1.dsc 61b97f12f5ca5d67c4db7418b2f6f166 3581401 games optional holotz-castle_1.3.6.orig.tar.gz 3f1023c5d6fa537985d8ea54bddc849b 3384 games optional holotz-castle_1.3.6-1.diff.gz bcd4263e9d84251fc6b11f88ab0279fd 3381976 games optional holotz-castle-data_1.3.6-1_all.deb 0d97f45d5f60e7716dc706ca8a69ab2e 109072 games optional holotz-castle_1.3.6-1_i386.deb 34fe006cb2c105e7b4eb3417a4198413 116470 games optional holotz-castle-editor_1.3.6-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCoa4xgY5NIXPNpFURAnUiAJwLyn6k8toFDZe6TL2PzymM44KY3gCgutz1 Grp4L2gVS/msmGxSFFmrh24= =GLGz -END PGP SIGNATURE- Accepted: holotz-castle-data_1.3.6-1_all.deb to pool/main/h/holotz-castle/holotz-castle-data_1.3.6-1_all.deb holotz-castle-editor_1.3.6-1_i386.deb to pool/main/h/holotz-castle/holotz-castle-editor_1.3.6-1_i386.deb holotz-castle_1.3.6-1.diff.gz to pool/main/h/holotz-castle/holotz-castle_1.3.6-1.diff.gz holotz-castle_1.3.6-1.dsc to pool/main/h/holotz-castle/holotz-castle_1.3.6-1.dsc holotz-castle_1.3.6-1_i386.deb to pool/main/h/holotz-castle/holotz-castle_1.3.6-1_i386.deb holotz-castle_1.3.6.orig.tar.gz to pool/main/h/holotz-castle/holotz-castle_1.3.6.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted postgresql-common 13 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 4 Jun 2005 15:44:40 +0200 Source: postgresql-common Binary: postgresql-common Architecture: source all Version: 13 Distribution: experimental Urgency: low Maintainer: Martin Pitt [EMAIL PROTECTED] Changed-By: Martin Pitt [EMAIL PROTECTED] Description: postgresql-common - manager for PostgreSQL database clusters Closes: 311546 Changes: postgresql-common (13) experimental; urgency=low . * pg_createcluster: Add option --start to start the new cluster right after creating it. * tests/000_existing_clusters: Check for stale postmaster and pg_autovacuum processes. * testsuite: - Temporarily stop existing servers and move away existing files before executing the tests. - Restore the original files after the tests. * pg_upgradecluster: Check return value of pg_dumpall and psql and fail if they are not successful. * pg_createuser: Fix indentation of socket warning. * pg_upgradecluster: Check if cluster is running, exit with an error if not. * pg_createcluster: Added option --encoding to override detection from locale. * pg_createcluster: Guess default encoding from locale for clusters older than 8.0 to get the same behaviour as for 8.0. * debian/control: Conflict to postgresql-7.4 1:7.4.8-5 since earlier versions do not support non-ASCII encodings (due to missing pg_encoding). * pg_ctlcluster: Check that the cluster owner uid/gid really exist. Closes: #311546 * pg_lsclusters: Ensure that there is at least one space between the colums. * Added tests/100_encodings which checks cluster creation and updates for different encodings and locales. * pg_upgradecluster: Preserve socket directory, locales, and encoding. * tests/100_encodings: Check the locale the postmaster is running under. Files: 86ebd694a6257a31ced7c31db169289b 578 misc optional postgresql-common_13.dsc e8ea98cd41888e447faec100281141dd 36281 misc optional postgresql-common_13.tar.gz 970747dd59d8aee7c0ff846684ec78ac 49638 misc optional postgresql-common_13_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCobFrDecnbV4Fd/IRAuV1AJ9ERZBbwqLz4nU/agSWEnI24IoiWwCgxnzX ochtarpGB2gb9IpBMDuxYCQ= =YcJ0 -END PGP SIGNATURE- Accepted: postgresql-common_13.dsc to pool/main/p/postgresql-common/postgresql-common_13.dsc postgresql-common_13.tar.gz to pool/main/p/postgresql-common/postgresql-common_13.tar.gz postgresql-common_13_all.deb to pool/main/p/postgresql-common/postgresql-common_13_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted pyblosxom 1.2.1-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 3 Jun 2005 08:58:51 +0200 Source: pyblosxom Binary: pyblosxom Architecture: source all Version: 1.2.1-1 Distribution: unstable Urgency: low Maintainer: Tollef Fog Heen [EMAIL PROTECTED] Changed-By: Tollef Fog Heen [EMAIL PROTECTED] Description: pyblosxom - simple weblog (blog) written in Python Closes: 274224 298587 303942 310499 Changes: pyblosxom (1.2.1-1) unstable; urgency=low . * New upstream release, minor changes only. * Remove powered by image, since some people feel it may be a privacy concern. (closes: #274224) * Only read from stdin if we're getting a POST, not if it's a GET. (closes: #303942) * Add L to bigger-than-int constants in Pyblosxom/tools.py. This is just to get python2.3 to shut up about it returning a positive value, the code is just used on windows so we won't have to care about whether it works or not. (closes: #310499) * Apply patch to look for config in same directory as the file exists in. This makes it a lot easier to use packaged pyblosxom on vhosts with multiple users and customised installations. (closes: #298587) Files: fc79b1ae731ce11ac8e04972b37f04b2 639 web optional pyblosxom_1.2.1-1.dsc c59e2cb44a9e72ba5e46e265ed23f0ad 46580 web optional pyblosxom_1.2.1.orig.tar.gz 48f0f8dceed7804b1cf49a98766b175c 6820 web optional pyblosxom_1.2.1-1.diff.gz 95a500cc529f42cea629d3ce8993345d 66552 web optional pyblosxom_1.2.1-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCobt+QSseMYF6mWoRAoTbAJwJCPWGqfBukg5ySgT0ahSyOtaDEgCghgQ0 pcOhInyQj0OBBWeTGTCgBqo= =Ewbs -END PGP SIGNATURE- Accepted: pyblosxom_1.2.1-1.diff.gz to pool/main/p/pyblosxom/pyblosxom_1.2.1-1.diff.gz pyblosxom_1.2.1-1.dsc to pool/main/p/pyblosxom/pyblosxom_1.2.1-1.dsc pyblosxom_1.2.1-1_all.deb to pool/main/p/pyblosxom/pyblosxom_1.2.1-1_all.deb pyblosxom_1.2.1.orig.tar.gz to pool/main/p/pyblosxom/pyblosxom_1.2.1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted balsa 2.3.2-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 4 Jun 2005 00:27:02 +1000 Source: balsa Binary: balsa Architecture: source i386 Version: 2.3.2-2 Distribution: unstable Urgency: medium Maintainer: Andrew Lau [EMAIL PROTECTED] Changed-By: Andrew Lau [EMAIL PROTECTED] Description: balsa - An e-mail client for GNOME Changes: balsa (2.3.2-2) unstable; urgency=medium . * Fix IMAP folder scanning segfault on 64-bit platforms. + [debian/patches/01_imap-folders.patch] Files: 2ce25e09061014f84a5483538a8d912d 1692 gnome optional balsa_2.3.2-2.dsc bcbc0b09e00c89a3d9268c8648bb8e1c 37962 gnome optional balsa_2.3.2-2.diff.gz 6674a8276c668b0ab922381795186324 2313572 gnome optional balsa_2.3.2-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCob+RrSla4ddfhTMRAtVpAJ444dKZVDUqUoda6dOYC+Gk8T63RgCaA7gm DteUOn1bL3YGgNDBAyhAUPE= =rxhS -END PGP SIGNATURE- Accepted: balsa_2.3.2-2.diff.gz to pool/main/b/balsa/balsa_2.3.2-2.diff.gz balsa_2.3.2-2.dsc to pool/main/b/balsa/balsa_2.3.2-2.dsc balsa_2.3.2-2_i386.deb to pool/main/b/balsa/balsa_2.3.2-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
