Bug Squashing Party on the coming weekend -- August, 5th - 7th
Hi. Due to numerous transitions, many new upstream versions and rapid development of native packages we had a big jump in the numbers of RC bugs since the sarge release. To not causing a delay down the road when we try to stabilise for the next release we need to work on them ASAP. In the past weeks I refrained from trying to coordinate these efforts due to Debconf and the unavailability of ftp-master.d.o. But there are no real excuses left. Therefor I announce the first post-sarge Bug Squashing Party (BSP) for the next weekend, August 5th until August 7th. Coordination will happen over IRC channel #debian-bugs on irc.debian.org as usual. Unlike shortly before sarge release there should be plenty of bugs for all levels of complexity, programming language skills and time requirements. So if you never attended to a BSP before and want to help, _now_ is the right time to start. The RC Bug Squashing HOWTO[0] by Steve Langasek gives a good introduction and is probably a must-read for beginners. But don't hesitate to ask questions in #debian-bugs, we will be eager to get you to do some work :) Sponsoring of uploads should be no problem, the fastest way is probably to send the complete NMU patch to the BTS, making the full source package available for download somewhere, and then asking for sponsoring on #debian-bugs. See also the end of this mail for a list of useful links. [0] http://people.debian.org/~vorlon/rc-bugsquashing.html Procedures: During the BSP we should use a 0-Day NMU policy again, that means uploads that fix RC bugs that are more than a week old can be uploaded directly. This worked reasonably well during the sarge release process so I see no reason not to use it again. If you feel unsure about a patch and/or if the patch is rather invasive, please consider asking on #debian-bugs for review and/or giving the maintainer some time to react by uploading to the DELAYED queue[1]. [1] http://lists.debian.org/debian-devel/2004/02/msg00887.html and http://people.debian.org/~djpig/delayed.html Everyone should consider reading the two announcements by Matthias Klose and Steve Langasek about the C++ transition ([2],[3]) and the mails by Colin Watson and Pascal Hakim about the latest BTS features ([4],[5]) before attending the BSP. [2] http://lists.debian.org/debian-devel-announce/2005/07/msg1.html [3] http://lists.debian.org/debian-devel-announce/2005/07/msg7.html [4] http://lists.debian.org/debian-devel-announce/2005/07/msg00010.html [5] http://lists.debian.org/debian-devel-announce/2005/07/msg00014.html Other useful links: (taken from http://people.debian.org/~vorlon/rc-bugsquashing-urls.txt) where to find available RC bugs: http://bts.turmzimmer.net/details.php?ignore=sidignnew=onnew=7 build logs for failed builds: http://buildd.debian.org/ Explanations for missing binaries: http://people.debian.org/~igloo/status.php List of open RC bugs for a given source package: http://bugs.debian.org/src:sourcepackagename Information on opening new bug reports: http://bugs.debian.org/ Debian Policy: http://www.debian.org/doc/debian-policy/ Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ signature.asc Description: Digital signature
Re: fresh blood gets congested: long way to become DD
On Mon, Aug 01, 2005 at 10:42:17PM +0100, Roger Leigh wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Moreno Garza [EMAIL PROTECTED] writes: I have been in the whole NM process for more than 13 months now. I spent around 6 months with my AM, around another 6 to be approved by the DAM and I'm waiting now, since a month ago, for my account to be created. Yes, I also know some people have had longer times. The thing that makes me feel uncomfortable is how Debian cannot encourage people for helping the project with this. Motivation probably just leaves with the long time waiting (in my case, there is nothing else on my hands to do). People just loses faith. It is sad to see the process is more a matter of time, than capacity or work done, experience. And well, right now I feel so close but also so far, because of the uncertainty, to conclude my process. A Debian account isn't that essential. I had packages in Debian for at least a year before I was invited to join the project. The additional 11 months I waited in the NM queue didn't stop me doing useful work. Hi Roger, you seem to be aware of facts that have eluded other NMs. Can you point to how you aquired this info and how other have missed it. Many folks dont RFTM. If is not stated clearly in say a NM FAQ, should it? just asking. 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: fresh blood gets congested: long way to become DD
On 02/08/05, Kevin Mark [EMAIL PROTECTED] wrote: On Tue, Aug 02, 2005 at 03:31:36PM +1200, Nigel Jones wrote: On 02/08/05, Stepan Golosunov [EMAIL PROTECTED] wrote: On Mon, Aug 01, 2005 at 08:24:30PM +0200, Laszlo Boszormenyi wrote: Nothing. It was just a question, as Nikita sounds to be a female name, but as I'm not sure about it, I was just interested. At least for me, a Hungarian, it sounds like a female name. In Russia, Nikita is (exclusively) male name. Hmmm, can we maybe get back to the ON Topic part of this? Personally I think get a couple of active developers that have been around a little while that maintain a few packages and get them into the AM role, and move some of the AMs into a DAM role... Also: say that if an AM/DAM does not process x applications a month (reasonably fair amount (say 5) and allow for vaccations/sickness etc) then they may face removal, as Yaroslav Halchenko said, there are ~61 Hi Nigel, would it be helpful to have some kind of status check every 6mo. to ask the AM's if they have the available time to process N apps. Something like 'no time','vacation','accepting N applicants'. If folks know who is 'open for business', it eliminates the confusion as who to ask. Then again, I just realized that I have no idea how NM and AM get 'connected'. So maybe someone can point me to the DOCS on this. That sounds way better than what I suggested, but yeah. 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'$ $. ,$. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC7wveRp+kG4Nu//URAu7jAJ4ib989xVtl7kHpY23eayZMcV19WwCdFBR8 rHlabRo1mYSKM32falSIcH8= =CZqP -END PGP SIGNATURE- -- N Jones Blogging @ http://nigelj.blogspot.com Proud Debian FOSS User Debian Maintainer of: html2ps ipkungfu
Re: I need to know how to create and use Driver Update Disks
On Mon, Aug 01, 2005 at 01:51:10PM -0700, Allyn, MarkX A wrote: Hello: I will be needing to create driver update disks for some device drivers that we have in development. I also need to know how to use them. Can anyone please provide me with a pointer on where I can get instructions on creating and using driver update disks? Or are they simply a collection of .deb files for device drivers? Thank you Mark Allyn Hi Mark, In the windows words, 'Devices' need 'Device drivers' (maybe dlls). In the uni*x world we have a kernel that uses kernel modules for 'hardware' devices. If you have a piece of hardware that is not functioning, it needs the correct kernel modules and the kernel modules has to be compatible with the kernel. If you give details of what hardware you need supported, someone can suggest which kernel you need and what kernel modules are needed to support it. 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: fresh blood gets congested: long way to become DD
On Tue, Aug 02, 2005 at 02:03:09AM -0400, Kevin Mark wrote: A Debian account isn't that essential. I had packages in Debian for at least a year before I was invited to join the project. The additional 11 months I waited in the NM queue didn't stop me doing useful work. you seem to be aware of facts that have eluded other NMs. Can you point to how you aquired this info and how other have missed it. Many folks dont RFTM. If is not stated clearly in say a NM FAQ, should it? Hi Kevin, Sorry for the intrusion, I just want to support Roger's opinion and give a few hints as you requested. I think that NM FAQ would be of limited importance because all possible FAQ to appear in it are covered either in Debian policy or mentors FAQ and sponsor section is of particular interest http://people.debian.org/~mpalmer/debian-mentors_FAQ.html#sponsored_packages Indeed to do THE WORK it is not necessary to be a DD. It is just that for upload of packages into debian non-DD needs to interact with a sponsor. Also administrativa like voting can't be done by non-DD. Besides that I don't see any difficulties as to do packaging and to interact_with/influence the debian community P.S. I brought up the topic because I think the path to become DD should not be done in burocratic way which is characterized by a high ratio of waiting time to processing time. -- .-. =-- /v\ = Keep in touch// \\ (yoh@|www.)onerussian.com Yaroslav Halchenko /( )\ ICQ#: 60653192 Linux User^^-^^[17] pgpcZb7pahUsU.pgp Description: PGP signature
Bug#320918: ITP: clex -- CLEX is a file manager with a full-screen user interface.
Package: wnpp Severity: wishlist Owner: r00t [EMAIL PROTECTED] * Package name: clex Version : 3.12 Upstream Author : Gabriel Puliatti (predius) [EMAIL PROTECTED] * URL : http://www.predius.org/ * License : GPL Description : CLEX is a file manager with a full-screen user interface. CLEX is a file manager with a full-screen user interface. It displays directory contents (including file status details) and provides features like command history, filename insertion, or name completion in order to help the user to construct commands to be executed by the shell (there are no built-in commands). -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-2-686 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: fresh blood gets congested: long way to become DD
* Nigel Jones ([EMAIL PROTECTED]) [050802 05:31]: Also: say that if an AM/DAM does not process x applications a month (reasonably fair amount (say 5) and allow for vaccations/sickness etc) then they may face removal I don't know if you've every worked as AM, but if you have other duties in Debian and perhaps even a life, then it is next to impossible to work on 5 applicants per month. And, BTW, is it not our problem to have too few AMs and you propose reducing their numbers even more? Even an AM that processes only one applicant at each time reduces the load of the queue in total (perhaps not as much as an AM that processes more than one, but that's still better than nothing). Now I'm not sure exactly how hard an AM's work is Yes, one could see that. Cheers, Andi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: fresh blood gets congested: long way to become DD
Kevin Mark [EMAIL PROTECTED] writes: On Tue, Aug 02, 2005 at 03:31:36PM +1200, Nigel Jones wrote: Also: say that if an AM/DAM does not process x applications a month (reasonably fair amount (say 5) and allow for vaccations/sickness etc) then they may face removal, as Yaroslav Halchenko said, there are ~61 Hi Nigel, would it be helpful to have some kind of status check every 6mo. to ask the AM's if they have the available time to process N apps. Something like 'no time','vacation','accepting N applicants'. If folks know who is 'open for business', it eliminates the confusion as who to ask. That's not a problem at the moment and is worse than the current state. AMs can simply go to nm.d.o and use the Change Profile page to say how many applicants they want to have. It's nice that you want to help, but please don't make proposals to solve problems that don't exist. If I don't answer these mails here, I'll have to face accusations that I'm not communicative enough and that the NM process needs to be more transparent - OTOH, I had plans to work trough my AM backlog for ... errr ... right now. Marc -- Fachbegriffe der Informatik - Einfach erklärt 248: Virenwarnung MS Outlock wird mal wieder getestet. (Manfred Worm Schäfer) pgp7McciOiiIm.pgp Description: PGP signature
Re: fresh blood gets congested: long way to become DD
Nigel Jones [EMAIL PROTECTED] writes: Personally I think get a couple of active developers that have been around a little while that maintain a few packages and get them into the AM role, and move some of the AMs into a DAM role... Right, because these people normally have loads of time to kill. Also: say that if an AM/DAM does not process x applications a month (reasonably fair amount (say 5) and allow for vaccations/sickness etc) then they may face removal, Sorry, but that's bullshit. Most applicants are not able to complete their application in less than two months, simply because they have other stuff to do. There are *very* few cases where people had the time to finish everything in less than four weeks. as Yaroslav Halchenko said, there are ~61 AM's, ... we have about 20 active AMs, no matter what the statistic page says. if each processed 3-4 applications a month (fairly) the queue could drop by 180+ in just a month, and that is only really 1 a week... Now I'm not sure exactly how hard an AM's work is, so lets make it 1 a fortnight, You have obviously no idea how much time is sucked up by AM work. Marc -- BOFH #140: LBNC (luser brain not connected) pgpdsn5Ac7R1Z.pgp Description: PGP signature
Bug#320931: ITP: lttoolbox -- Apertium lexical processing modules and tools
Package: wnpp Severity: wishlist Owner: Sergio Talens-Oliag [EMAIL PROTECTED] Package name: lttoolbox Version : 0.8.0 Upstream Author : Universitat d'Alacant URL : http://apertium.sourceforge.net/ License : GPL Description : Apertium lexical processing modules and tools The lttoolbox contains the augmented letter transducer tools for natural language processing used by the apertium system. -- Sergio Talens-Oliag [EMAIL PROTECTED] http://people.debian.org/~sto/ Key fingerprint = 29DF 544F 1BD9 548C 8F15 86EF 6770 052B B8C1 FA69 signature.asc Description: Digital signature
Bug#320930: ITP: apertium -- Machine translation engine for related languages
Package: wnpp Severity: wishlist Owner: Sergio Talens-Oliag [EMAIL PROTECTED] Package name: apertium Version : 0.8.1 Upstream Author : Universitat d'Alacant URL : http://apertium.sourceforge.net/ License : GPL Description : Machine translation engine for related languages Apertium is an open-source shallow-transfer machine translation engine, initially aimed at related-language pairs. . It uses finite-state transducers for lexical processing, hidden Markov models for part-of-speech tagging, and finite-state based chunking for structural transfer. . The system is largely based upon systems already developed by the Transducens group at the Universitat d'Alacant, such as interNOSTRUM (Spanish-Catalan, http://www.internostrum.com/welcome.php) and Traductor Universia (Spanish-Portuguese, http://traductor.universia.net). . It will be possible to use Apertium to build machine translation systems for a variety of related-language pairs simply providing the linguistic data needed in the right format. . There is a non-free package (apertium-ca-es) that provides the data needed to translate between Spanish and Catalan. -- Sergio Talens-Oliag [EMAIL PROTECTED] http://people.debian.org/~sto/ Key fingerprint = 29DF 544F 1BD9 548C 8F15 86EF 6770 052B B8C1 FA69 signature.asc Description: Digital signature
Re: fresh blood gets congested: long way to become DD
On Tue, Aug 02, 2005 at 10:28:08AM +0200, Andreas Barth wrote: on 5 applicants per month. And, BTW, is it not our problem to have too Well, I can just say such AMs a big Thank you :-) few AMs and you propose reducing their numbers even more? Even an AM Now I'm not sure exactly how hard an AM's work is Yes, one could see that. So, Andreas is making the point that it is good to keep silent AMs on the list with hope that some of them can get at least 1 NM on-board and work with him/her... Then I have a better idea... It seems to me that any DD-professional is capable of performing AM duties, isn't it? Then I would say it might make sense to send an announcement to any DD with experience over X month and Y packages maintained if they want to be just considered for AM process. After that, any such DD would be informed about fresh meat NM which comes in the queue. To interest/intrigue any particular DD I would suggest to include a short (up to 100 words) resume from NM covering his interests/experience. Debian is a community project after all and personally, I get excited when I get in touch with people having similar interests. That is why I think that a short resume (after NM was advocated) + wider range of AMs can help to resolve the congestion. To get it more standardized it can be a simple form to fill in with interest/experience options to be marked. That might interest AMs/DDs in considering a specific applicant. -- .-. =-- /v\ = Keep in touch// \\ (yoh@|www.)onerussian.com Yaroslav Halchenko /( )\ ICQ#: 60653192 Linux User^^-^^[17] pgpM5RswflAVw.pgp Description: PGP signature
Bug#320934: ITP: apertium-es-ca -- Apertium linguistic data to translate between Spanish and Catalan
Package: wnpp Severity: wishlist Owner: Sergio Talens-Oliag [EMAIL PROTECTED] Package name : apertium-es-ca Version : 20050729 Upstream Authors : Universitat d'Alacant, Universitat Politècnica de Catalunya URL : http://apertium.sourceforge.net/ License : Creative Commons Attribution-NonCommercial-ShareAlike 2.5 License (http://creativecommons.org/licenses/by-nc-sa/2.5/) Description : Spanish-Catalan language-pair package for apertium This package contains the linguistic data needed by apertium to translate between Spanish and Catalan. This package will go to non-free, as the CC license used is not DFSG free. -- Sergio Talens-Oliag [EMAIL PROTECTED] http://people.debian.org/~sto/ Key fingerprint = 29DF 544F 1BD9 548C 8F15 86EF 6770 052B B8C1 FA69 signature.asc Description: Digital signature
Re: fresh blood gets congested: long way to become DD
Yaroslav Halchenko [EMAIL PROTECTED] writes: On Tue, Aug 02, 2005 at 10:28:08AM +0200, Andreas Barth wrote: Now I'm not sure exactly how hard an AM's work is Yes, one could see that. So, Andreas is making the point that it is good to keep silent AMs on the list with hope that some of them can get at least 1 NM on-board and work with him/her... No, the point is that an AM who processes one applicant still helps, as you don't need to get someone else to do it. It's not as if we have a limit for the number of AMs. Then I have a better idea... It seems to me that any DD-professional is capable of performing AM duties, isn't it? More or less. Then I would say it might make sense to send an announcement to any DD with experience over X month and Y packages maintained if they want to be just considered for AM process. Right, because *new* developers have no idea about the NM process and just need the reminder that it exists to jump up and help. Sorry, the whole thing doesn't work this way: You need to invest a lot of time into AM work, so you need to care about it. Just asking every new developer will not help. Marc -- Fachbegriffe der Informatik - Einfach erklärt 9: GUI Ein Hintergrundbild und 12 Xterms (Kristian Köhntopp) pgpow4lMCqq4G.pgp Description: PGP signature
Re: fresh blood gets congested: long way to become DD
Then I would say it might make sense to send an announcement to any DD with experience over X month and Y packages maintained if they want to be just considered for AM process. Right, because *new* developers have no idea about the NM process and just need the reminder that it exists to jump up and help. Sorry, the whole thing doesn't work this way: You need to invest a lot of time into AM work, so you need to care about it. Just asking every new developer will not help. I'm sorry to clarify myself. I gratefully respect time spent by any DD working on the project and tenfold time of any AM interfacing with NM -- NMs (like me probably :-)) can be pain in the butt to deal with. I was talking about X=12 and Y=5 which wouldn't name any such developer as *new* under my classification. My idea is just to delegate AM duties to the DDs mature enough and able/willing to help. Then all of the AMs who has the ability to perform AM duties and who are for some probably truly respectful reason are having 0 NM assigned with more than 50 NMs in the queue wouldn't look a bit awkward. /Sorry for the long and probably unparsable sentence.../ -- .-. =-- /v\ = Keep in touch// \\ (yoh@|www.)onerussian.com Yaroslav Halchenko /( )\ ICQ#: 60653192 Linux User^^-^^[17] pgplzeuygFPcU.pgp Description: PGP signature
Bug#320939: ITP: blosxom-plugins -- various plugins for the blosxom blog tool
Package: wnpp Severity: wishlist Owner: Gerfried Fuchs [EMAIL PROTECTED] * Package name: blosxom-plugins Version : 0.5 (propably) Upstream Author : Various * URL : http://www.blosxom.com/plugins/ * License : GPL, BSD, ... Description : various plugins for the blosxom blogging tool This package contains various helpful plugins for the blosxom blogging tool. They are meant to be a useful extension to the basic functionality. Included you also find a (de)activate script for easy maintenance. About the maintenance script I think of something along the a2ensite and a2dissite scripts, together with some dpkg-reconfigure hooks, too. The integration of the latter will mark version 1.0 for me. I'm open for suggestions of plugins to integrate, I am thinking at least of the atom, calendar, seemore, debtags and entries_cache. So long, Alfie -- Wieso gibt's kan sync Befehl fürs Hirn? Wieso steh i jetzt? -- 2002-12-04, in der Arbeit aufgeschnappt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: fresh blood gets congested: long way to become DD
On Tue, August 2, 2005 10:28, Andreas Barth wrote: And, BTW, is it not our problem to have too few AMs While I can agree that there are too few AMs, the whole process itself seems pretty bureaucratic with room for improvement. Once you've completed the AM stage, this still has to happen: - AM checks application. - Front Desk checks application. - DAM checks application. - DAM creates account. (Source: nm.debian.org) So, once the AM, who has done a thorough review of the candidate, then you still need to pass three steps. Why? Once you've reached the AM-approved stage, you've already got: - a good review by an existing developer (advocate) - an assurance from a person very experienced with Debian and with handling new developers - a proof of identity Well, I could understand that it's desired to have one last check by a third person at the end of the whole process. But why do the FD and DAM have to check separately? And why is approval by DAM not equal to account creation? It seems to me that the account creation step could be fully automated: checking the box approved by DAM could trigger an insert into the LDAP database thereby creating the account. Thijs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: fresh blood gets congested: long way to become DD
Yaroslav Halchenko [EMAIL PROTECTED] writes: Then I would say it might make sense to send an announcement to any DD with experience over X month and Y packages maintained if they want to be just considered for AM process. Right, because *new* developers have no idea about the NM process and just need the reminder that it exists to jump up and help. Sorry, the whole thing doesn't work this way: You need to invest a lot of time into AM work, so you need to care about it. Just asking every new developer will not help. I'm sorry to clarify myself. I gratefully respect time spent by any DD working on the project and tenfold time of any AM interfacing with NM -- NMs (like me probably :-)) can be pain in the butt to deal with. I was talking about X=12 and Y=5 which wouldn't name any such developer as *new* under my classification. My idea is just to delegate AM duties to the DDs mature enough and able/willing to help. That wasn't my point. Not everybody with a few packages and a few months old account is a good AM, so you can't ping anybody. These people need to be interested and care about the NM process. Marc -- BOFH #88: Boss' kid fucked up the machine pgpDkDMfTVKZd.pgp Description: PGP signature
Re: fresh blood gets congested: long way to become DD
* Thijs Kinkhorst ([EMAIL PROTECTED]) [050802 12:19]: And why is approval by DAM not equal to account creation? It seems to me that the account creation step could be fully automated: checking the box approved by DAM could trigger an insert into the LDAP database thereby creating the account. because that would mean that the php-script has root access to the ldap database, which is equivalent to be root on all debian.org-machines. Also, the nm.d.o-pages don't have all necessary information for the account. Actually creating the account in the LDAP is BTW not taking as much time as you might consider, it is just that only very few persons have the privilege to change such information in the ldap database for obvious reasons. Cheers, Andi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: fresh blood gets congested: long way to become DD
Thijs Kinkhorst [EMAIL PROTECTED] writes: On Tue, August 2, 2005 10:28, Andreas Barth wrote: And, BTW, is it not our problem to have too few AMs While I can agree that there are too few AMs, the whole process itself seems pretty bureaucratic with room for improvement. Once you've completed the AM stage, this still has to happen: - AM checks application. - Front Desk checks application. - DAM checks application. - DAM creates account. (Source: nm.debian.org) So, once the AM, who has done a thorough review of the candidate, then you still need to pass three steps. Why? Once you've reached the AM-approved stage, you've already got: - a good review by an existing developer (advocate) It would be nice if all advocates would actually check that the applicant is apt to become a developer: The high number of rejections (by the AM) shows that this doesn't work. - an assurance from a person very experienced with Debian and with handling new developers Right, because all AMs are very experienced with new developers, as they have all processed like 20 applicants or so in 4 months. Well, I could understand that it's desired to have one last check by a third person at the end of the whole process. But why do the FD and DAM have to check separately? Because the FD checks that the report is formally OK (and also gives a bit of feedback to the AM and applicant), while the DAM checks from a Do we want to give a security hole to this applicant point of view. And why is approval by DAM not equal to account creation? It seems to me that the account creation step could be fully automated: checking the box approved by DAM could trigger an insert into the LDAP database thereby creating the account. (1) Account creation needs a bit more than that, as the applicant's key needs to be added to the keyring (2) WTF? You want to give LDAP write access to a PHP script? Marc -- BOFH #149: Dew on the telephone lines. pgpfyCd8eNzQ8.pgp Description: PGP signature
Re: Bug#320918: ITP: clex -- CLEX is a file manager with a full-screen user interface.
On Tue, Aug 02, 2005 at 01:59:48AM -0500, r00t wrote: Package: wnpp Severity: wishlist Owner: r00t [EMAIL PROTECTED] Could we have bugs from real names please? Hamish -- Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: fresh blood gets congested: long way to become DD
On Tue, August 2, 2005 13:11, Marc 'HE' Brockschmidt wrote: - a good review by an existing developer (advocate) It would be nice if all advocates would actually check that the applicant is apt to become a developer: The high number of rejections (by the AM) shows that this doesn't work. This is more of an education question then: how do we make sure advocates know what they're doing? Maybe an advocate has to give some proof, e.g. I've co-maintained package x with this candidate for months and he did a good job or I've sponsored quite some uploads and all these packages were well done. Is there feedback provided to those advocates who approve bad prospects? - an assurance from a person very experienced with Debian and with handling new developers Right, because all AMs are very experienced with new developers, as they have all processed like 20 applicants or so in 4 months. I don't see how you can think that I ever claimed that. Well, I could understand that it's desired to have one last check by a third person at the end of the whole process. But why do the FD and DAM have to check separately? Because the FD checks that the report is formally OK (and also gives a bit of feedback to the AM and applicant), while the DAM checks from a Do we want to give a security hole to this applicant point of view. I don't see how this explains that these tasks can't be done by a single group of people. If you're checking a report out, you could either check some points and leave other points to be checked by another part of the process, or just check the whole thing at once. The last one makes more sense to me. And why is approval by DAM not equal to account creation? It seems to me that the account creation step could be fully automated: checking the box approved by DAM could trigger an insert into the LDAP database thereby creating the account. (1) Account creation needs a bit more than that, as the applicant's key needs to be added to the keyring (2) WTF? You want to give LDAP write access to a PHP script? You don't have to give the script write access to accomplish that. You could also use a pull system that periodically (nightly?) checks which new developers have been approved and add them from that side. And even then, appearently the DAM works like this: I approve person X, let's check his box, but I'll add the account at some point later on (this takes weeks on average). When you check the box you might add the account aswell when you're at it, right? Or what about this: as DAM, I've checked his application, everything OK, so I create the account. The NM-system will then show DAM-approved for this candidate. Thijs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: fresh blood gets congested: long way to become DD
* Thijs Kinkhorst ([EMAIL PROTECTED]) [050802 13:41]: And even then, appearently the DAM works like this: I approve person X, let's check his box, but I'll add the account at some point later on (this takes weeks on average). When you check the box you might add the account aswell when you're at it, right? Just that the person who checks the reports is not root in Debian's ldap system. So, one person checks the reports, and then marks it on the web pages and sends mail to another person who then adds the accounts. Cheers, Andi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: fresh blood gets congested: long way to become DD
i tried once or twice to volunteer, but i failed... i don't remember why just my two cents -- Fred On 8/2/05, Andreas Barth [EMAIL PROTECTED] wrote: * Thijs Kinkhorst ([EMAIL PROTECTED]) [050802 13:41]: And even then, appearently the DAM works like this: I approve person X, let's check his box, but I'll add the account at some point later on (this takes weeks on average). When you check the box you might add the account aswell when you're at it, right? Just that the person who checks the reports is not root in Debian's ldap system. So, one person checks the reports, and then marks it on the web pages and sends mail to another person who then adds the accounts. Cheers, Andi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- -- Fred
Re: fresh blood gets congested: long way to become DD
On Tue, August 2, 2005 13:44, Andreas Barth wrote: * Thijs Kinkhorst ([EMAIL PROTECTED]) [050802 13:41]: And even then, appearently the DAM works like this: I approve person X, let's check his box, but I'll add the account at some point later on (this takes weeks on average). When you check the box you might add the account aswell when you're at it, right? Just that the person who checks the reports is not root in Debian's ldap system. So, one person checks the reports, and then marks it on the web pages and sends mail to another person who then adds the accounts. Is this a bug or a feature? THijs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: fresh blood gets congested: long way to become DD
Em Ter, 2005-08-02 às 04:46 -0400, Yaroslav Halchenko escreveu: Then I have a better idea... It seems to me that any DD-professional is capable of performing AM duties, isn't it? Then I would say it might make sense to send an announcement to any DD with experience over X month and Y packages maintained if they want to be just considered for AM process. I think I have an even better idea! It would be very nice if people would only voice their opinions on a problem after getting in touch with the affected part of Debian for some time, having felt this way its real problems and needs. The amount of non-feasible and non-helpful ideas being thrown in the air these days just seems to be very big. That certainly makes debian-devel a PITA to read. Nothing personal, nothing specific about you, this is just a random selected message to reply with my small suggestion. See ya, -- [EMAIL PROTECTED]: Gustavo Noronha http://people.debian.org/~kov Debian: http://www.debian.org * http://www.debian-br.org signature.asc Description: This is a digitally signed message part
Re: fresh blood gets congested: long way to become DD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andreas Barth skrev: * Thijs Kinkhorst ([EMAIL PROTECTED]) [050802 13:41]: And even then, appearently the DAM works like this: I approve person X, let's check his box, but I'll add the account at some point later on (this takes weeks on average). When you check the box you might add the account aswell when you're at it, right? Just that the person who checks the reports is not root in Debian's ldap system. There is delegation and group access available in OpenLDAP. So, one would not need to have write access to the whole directory tree, only to the necessary branches. Also, this could very well be handled the same way as .commands on ftp-master.d.o, that is, by requiring valid signatures of ldap commands in ldif format from a limited number of people operating on a restricted part of the ldap tree. Just a thought, no flames please :) // Tomas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFC726ywYdzVZ/o1QQRAv8tAJ9gBsOJ6j+xqL1wR1ezmtsnnzFxvgCfaKFE zy5shd7inv3al0LliXc6XcY= =hUtq -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: fresh blood gets congested: long way to become DD
Yaroslav Halchenko wrote: Indeed to do THE WORK it is not necessary to be a DD. It is just that for upload of packages into debian non-DD needs to interact with a sponsor. Also administrativa like voting can't be done by non-DD. Besides that I don't see any difficulties as to do packaging and to interact_with/influence the debian community This is free software. Personally, my kicks come from knowing people use what I've done. The long delays involved with sponsored uploads, and even more when new packages are involved, are hurting the fun, and ultimately, the incentive to contribute. Don't get me wrong. I am not in the least bit resentful to my sponsor when things get slow. I realize full well he is also busy, and has other things to do. Isn't that just the point, though? I wish to become a DD, not because I don't think I can get my packages into Debian otherwise, but because I want to help the project. It seems that the lack of time everybody has is a self aggravating problem. No time - Longer time to approve new DDs - People have no time. Shachar -- Shachar Shemesh Lingnu Open Source Consulting ltd. http://www.lingnu.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#320918: ITP: clex -- CLEX is a file manager with a full-screen user interface.
Hamish Moffatt wrote: On Tue, Aug 02, 2005 at 01:59:48AM -0500, r00t wrote: Package: wnpp Severity: wishlist Owner: r00t [EMAIL PROTECTED] Could we have bugs from real names please? The ITP submitter did actually include his name in the original message -- as the upstream author: Upstream Author : Gabriel Puliatti (predius) [EMAIL PROTECTED] * URL : http://www.predius.org/ regards, -- Kevin B. McCarty [EMAIL PROTECTED] Physics Department WWW: http://www.princeton.edu/~kmccarty/Princeton University GPG: public key ID 4F83C751 Princeton, NJ 08544 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: fresh blood gets congested: long way to become DD
It's a pretty theory but it fails to account for reality. On Tue, Aug 02, 2005 at 12:18:08PM +0200, Thijs Kinkhorst wrote: On Tue, August 2, 2005 10:28, Andreas Barth wrote: And, BTW, is it not our problem to have too few AMs While I can agree that there are too few AMs, the whole process itself seems pretty bureaucratic with room for improvement. Once you've completed the AM stage, this still has to happen: - AM checks application. - Front Desk checks application. - DAM checks application. - DAM creates account. (Source: nm.debian.org) So, once the AM, who has done a thorough review of the candidate, then you still need to pass three steps. Why? Once you've reached the AM-approved stage, you've already got: - a good review by an existing developer (advocate) Advocates are utterly useless. Anybody, absolutely *anybody*, no matter how much of a stupid MCSE-waving windows nutcase they might be, can get advocated, and people do routinely get advocated who have no hope of passing. The flaw in the system is simple and obvious: in order to get advocated, you must find precisely one developer in a thousand who thinks they should sent a brief fluffy mail about you. - an assurance from a person very experienced with Debian and with handling new developers AMs aren't much better, as a group. The FD checks their applications so as not to waste the DAM's time reviewing bogus ones, and the DAM checks them to filter out people who shouldn't get in. The reason why we need both these checks is most simply explained by pointing out that both of them reject a significant number of applicants - if we didn't have them, people would get in who shouldn't, or the DAM's already limited time would be wasted, slowing the process down more. -- .''`. ** Debian GNU/Linux ** | Andrew Suffield : :' : http://www.debian.org/ | `. `' | `- -- | signature.asc Description: Digital signature
Re: fresh blood gets congested: long way to become DD
[Andrew Suffield] AMs aren't much better, as a group. The FD checks their applications so as not to waste the DAM's time reviewing bogus ones, and the DAM checks them to filter out people who shouldn't get in. The reason why we need both these checks is most simply explained by pointing out that both of them reject a significant number of applicants - if we didn't have them, people would get in who shouldn't, or the DAM's already limited time would be wasted, slowing the process down more. You seem to assume that all rejections are correct, and get rid of some people which should not be accepted as debian developers, while all approvals are suspect and might let through a person which should have been rejected. Is this correct? Do you have any good arguments why it isn't the other way around, that some of the rejections get rid of people which could have done a great job as a debian developer? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#320967: ITP: kaya -- A Statically typed, imperative programming language
Package: wnpp Severity: wishlist Owner: Stuart Teasdale [EMAIL PROTECTED] * Package name: kaya Version : 0.1.24 Upstream Author : Edwin Brady [EMAIL PROTECTED] * URL : http://compsoc.dur.ac.uk/kaya/ * License : GPL Description : A Statically typed, imperative programming language Kaya is a compiled statically typed (ie, types are checked at compile time) imperative programming language; unlike other such languages, however, types are inferred rather than declared - there is no need for type declarations of local variables. Kaya has tagged union data structures, a powerful feature more commonly found in functional languages such as Ocaml and Haskell. . Kaya also has built-in abstractions for web application development, making it easy to write a CGI program without paying too much attention to low level details such as state management and form handling. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.7 Locale: LANG=en_GB.ISO-8859-15, LC_CTYPE=en_GB.ISO-8859-15 (charmap=ISO-8859-1) (ignored: LC_ALL set to en_GB) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: I need to know how to create and use Driver Update Disks
Thank you Rob. Here is the situation that I have: We have some patches that have already be open sourced (ICH7) and are in the 2.6.11 and above kernels. What we need to do is to provide a Driver Update Disk so that someone who is using the 2.6.8 kernel supplied by the stable release (Sarge) can do an install on a ICH7 based system. The current un-ICH7 patched 2.6.8 kernel on Sarge will not install on a ICH7 system. The kernel used by the installer, as well as the kernel that is installed, need to have the ICH7 patches applied. We fully understand that the patched files must be loadable modules that can be loaded into an already running kernel. We anticipate this to be a stopgap measure until the 2.6.11 kernel goes into production (when Etch takes the place of Sarge). At that point, this need should go away. Mark -Original Message- From: Rob Taylor [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 02, 2005 8:28 AM To: Allyn, MarkX A Cc: debian-devel@lists.debian.org Subject: Re: I need to know how to create and use Driver Update Disks On Mon, 2005-08-01 at 13:51 -0700, Allyn, MarkX A wrote: Hello: I will be needing to create driver update disks for some device drivers that we have in development. I also need to know how to use them. Can anyone please provide me with a pointer on where I can get instructions on creating and using driver update disks? Or are they simply a collection of .deb files for device drivers? can you be more specific? are you developing closed source kernel modules, or are these drivers open source? If you can open then (and I *heavily* recommend you do, otherwise you will spend many tens of thousands of dollars playing catchup with every kernel in every distribution), then you should inquire on the linux-kernel mailing list who the best person is to deal with your patches. If you are producing closed-source kernel modules, and have chosen which distros you wish to support - I presume you wish to support Debian Sarge - then you need to produce packages with that kernel module, compiled against the kernel(s) used by that distribution. For sarge, i suggest you investigate module-assistant and other packages that use module-assistant (can someone else help with a good example?) Thanks, Rob Taylor
Re: I need to know how to create and use Driver Update Disks
On Mon, 2005-08-01 at 13:51 -0700, Allyn, MarkX A wrote: Hello: I will be needing to create driver update disks for some device drivers that we have in development. I also need to know how to use them. Can anyone please provide me with a pointer on where I can get instructions on creating and using driver update disks? Or are they simply a collection of .deb files for device drivers? can you be more specific? are you developing closed source kernel modules, or are these drivers open source? If you can open then (and I *heavily* recommend you do, otherwise you will spend many tens of thousands of dollars playing catchup with every kernel in every distribution), then you should inquire on the linux-kernel mailing list who the best person is to deal with your patches. If you are producing closed-source kernel modules, and have chosen which distros you wish to support - I presume you wish to support Debian Sarge - then you need to produce packages with that kernel module, compiled against the kernel(s) used by that distribution. For sarge, i suggest you investigate module-assistant and other packages that use module-assistant (can someone else help with a good example?) Thanks, Rob Taylor -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: I need to know how to create and use Driver Update Disks
On Tuesday 02 August 2005 17:35, Allyn, MarkX A wrote: We have some patches that have already be open sourced (ICH7) and are in the 2.6.11 and above kernels. What we need to do is to provide a Driver Update Disk so that someone who is using the 2.6.8 kernel supplied by the stable release (Sarge) can do an install on a ICH7 based system. I think the best thing to do is to contact the Debian kernel team at debian-kernel@lists.debian.org and discuss the options for the stable kernels with them. The Debian package system does not really like packages (your driver update) replacing files that belong to another package (the official Debian kernel-image package). This means the best option would be to get the patches included in an update of the 2.6.8 kernel (which is being prepared at the moment). The other team that should be involved is the Debian Installer team (at debian-boot@lists.debian.org). Getting out a separate driver update does not mean it will automatically be usable by the installation system; again getting the patches into the offical Debian kernels would be best. The installer team is currently working on a new version of the installation system using the 2.6.12 kernel, but it is not yet sure if users will be able to use that to install Sarge. It very much depends on the nature of the patches if they will be accepted for Sarge. Your interest is very much appreciated though. Cheers, Frans Pop pgpAoFbrkVNlB.pgp Description: PGP signature
Re: fresh blood gets congested: long way to become DD
Petter Reinholdtsen [EMAIL PROTECTED] writes: [Andrew Suffield] AMs aren't much better, as a group. The FD checks their applications so as not to waste the DAM's time reviewing bogus ones, and the DAM checks them to filter out people who shouldn't get in. The reason why we need both these checks is most simply explained by pointing out that both of them reject a significant number of applicants - if we didn't have them, people would get in who shouldn't, or the DAM's already limited time would be wasted, slowing the process down more. You seem to assume that all rejections are correct, and get rid of some people which should not be accepted as debian developers, while all approvals are suspect and might let through a person which should have been rejected. Is this correct? Do you have any good arguments why it isn't the other way around, that some of the rejections get rid of people which could have done a great job as a debian developer? Have you read the reasons for holds and rejections at the FD and DAM stage? Really, folks, quite a bit of this information is public. I admit that, being in NM myself, I have had more reason to go poking around on the web site and reading up on various records, but it's worth spending some time on the site before participating in these sorts of threads. Like Andrew says, the three stages of checks are only pointless bureaucracy if the last two steps are rubber stamps. As you can see clearly from the NM site, they're not. Given that, you have to dig a little deeper and figure out why people may get all the way through the AM stage but still not get approved. Looking at the records on the site, you'll find that, of the three current front desk holds, two are for incomplete skills testing and one is for a key problem. Particularly given the rest of this thread and the desire to see more people jump in to be AMs, you do need this sort of check by a third party. Not all AMs are experienced; not all AMs are going to remember everything. Looking at the DAM holds, you'll see that most of them are for lack of activity. Now, you might argue (reasonably) that the current extended length of the process is partly to blame for that, but on the other hand, joining Debian really is a committment. While I wouldn't say that it's as easy to participate in Debian without being a DD as some of the other folks on this list, it most certainly is possible. I'll also point out that, for every other open source project I've been involved in, it's taken at *least* a year of steady activity on the project and regular patch submission before I got direct commit access. I wouldn't expect Debian to be that different. I do think that the amount of time NM takes at the moment is a bit too long, but I don't think it should be quick. I think it's important to verify that people really *want* to be DDs before approving them, and while sheer time lag isn't necessarily the most friendly way of doing this, it can still be rather effective. -- 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: I need to know how to create and use Driver Update Disks
On Tue, 2005-08-02 at 18:03 +0200, Frans Pop wrote: On Tuesday 02 August 2005 17:35, Allyn, MarkX A wrote: We have some patches that have already be open sourced (ICH7) and are in the 2.6.11 and above kernels. What we need to do is to provide a Driver Update Disk so that someone who is using the 2.6.8 kernel supplied by the stable release (Sarge) can do an install on a ICH7 based system. I think the best thing to do is to contact the Debian kernel team at debian-kernel@lists.debian.org and discuss the options for the stable kernels with them. The Debian package system does not really like packages (your driver update) replacing files that belong to another package (the official Debian kernel-image package). This means the best option would be to get the patches included in an update of the 2.6.8 kernel (which is being prepared at the moment). If he produces a new kernel module to add support for this hardware, there's absolutely no reason why it should conflict with linux-kernel. Given that it's not a security fix, would he really have much luck getting a patch into stable's kernel? Rob Taylor -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: fresh blood gets congested: long way to become DD
On Tue, 2005-08-02 at 15:24 +0100, Andrew Suffield wrote: The FD checks their applications so as not to waste the DAM's time reviewing bogus ones, and the DAM checks them to filter out people who shouldn't get in. Your statement rests on the assuption that somehow the DAM's time is more valuable than the FD's time. If we would just make everyone currently in FD a DAM, then then the check could be done by a single person. To be perfectly clear - I don't object to the checks per se, but rather to those checks being done by different institutions. Andreas Barth wrote in this thread: So, one person checks the reports, and then marks it on the web pages and sends mail to another person who then adds the accounts. Please explain how this isn't overly cumbersome. Currently a report passes through FD, then to DAM-not-authorised, and finally to DAM-authorised. What if these groups would be melted into one, and each member could take an incoming application, review it, and either reject or approve the account? Thijs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
ITP: conky -- Highly configurable system monitor that sits on your desktop
Package: wnpp Severity: wishlist Owner: Bjarke Bolding [EMAIL PROTECTED] Package name : conky Version : 1.2 Upstream Author : Brenden Matthews [EMAIL PROTECTED] URL : http://conky.rty.ca/ License : GPL2 Description : Highly configurable system monitor that sits on your desktop Conky is a system monitor for Linux that sits in the corner of your desktop. Conky renders itself on the root window (on the desktop) or to its own transparent window any special eyecandy. Conky can show lots of info about your system, including: . * kernel version * uptime * network interface information * memory and swap usage * hostname * machine, i686 for example * system name, Linux for example * temperatures from i2c-sensors -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12.3 Locale: LANG=en_DK, LC_CTYPE=en_DK (charmap=ISO-8859-1)
net-tools maintenance status
Hi, What's the maintenance status of the net-tools package? It has 88 bugs: Serious policy violations - outstanding (1 bug) Important bugs - outstanding (8 bugs) Normal bugs - outstanding (38 bugs) Minor bugs - outstanding (9 bugs) Wishlist items - outstanding (32 bugs) A lot older than a year, 17 with patch a lot even without a single response. I emailed a patch to Bernd two months ago but I'm still waiting for a response. http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=net-tools http://packages.qa.debian.org/n/net-tools.html
Re: fresh blood gets congested: long way to become DD
On 8/2/05, Thijs Kinkhorst [EMAIL PROTECTED] wrote: Currently a report passes through FD, then to DAM-not-authorised, and finally to DAM-authorised. What if these groups would be melted into one, and each member could take an incoming application, review it, and either reject or approve the account? Multiple persons often see more bugs/error/mistakes/whatever then one person. Won't this decrease 'quality'?
Re: How to use svn(-buildpackage) with pbuilder?
On Sun, Jul 31, 2005 at 07:03:14AM -0400, Yaroslav Halchenko wrote: borrowed from a nice minimalistic HOWTO http://workaround.org/moin/SvnBuildpackage That is indeed a very helpful HOWTO. Thanks! 3 and 5 just add them to --svn-postbuild as IT IS SAID IN THE MAN PAGE: :-) OK, thanks. One more question, I could not answer myself from reading the man page: If I have the complete upstream source in SVN, but not the .tar.gz, how do I create the .orig.tar.gz, when I have a new upstream version? Cheers, -- W. Borgert [EMAIL PROTECTED], http://people.debian.org/~debacle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to use svn(-buildpackage) with pbuilder?
Hello, If I have the complete upstream source in SVN, but not the .tar.gz, how do I create the .orig.tar.gz, when I have a new upstream version? Use svn export to create a dist of the svn tree, without the control folders. Regards, -- Clément -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Packages descriptions review
Hello, Sorry for not answering earlier. OK, I've summarized all (I think) of Policy's requirements on packages in the wiki page, together with a cite to the section it came from. Thanks Also, I've completed news, and would appreciate any feedback. Please see the webpage for comments ... This first review raises a question, IMHO. When several packages have more or less the same goal (in the news case, there are many news grabers and local servers), should their descriptions include a comparison to the other ones ? I don't think we can ask the maintainers to compare (and keep this comparisons up to date) their packages to the similar ones, but I agree that in some cases, it could be useful for the user. What do you think ? -- Clément Stenac -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
jigdo-search
Hello. After last talk about searching for packages on CDs Gaëtan Frenoy wrote some shell script along with PHP script for such purposes and sent me it todays morning. I made some modifications to it (support for DVDs and get rid of some temporary files), and it's now at my people.d.o page[1]. Any comments/requests are welcome. regards fEnIo [1] - http://people.debian.org/~fenio/jigdo-search.php -- ,''`. Bartosz Fenski | mailto:[EMAIL PROTECTED] | pgp:0x13fefc40 | irc:fEnIo : :' : 32-050 Skawina - Glowackiego 3/15 - w. malopolskie - Poland `. `' phone:+48602383548 | proud Debian maintainer and user `- http://skawina.eu.org | jid:[EMAIL PROTECTED] | rlu:172001 signature.asc Description: Digital signature
Re: fresh blood gets congested: long way to become DD
Olaf van der Spek [EMAIL PROTECTED] writes: On 8/2/05, Thijs Kinkhorst [EMAIL PROTECTED] wrote: Currently a report passes through FD, then to DAM-not-authorised, and finally to DAM-authorised. What if these groups would be melted into one, and each member could take an incoming application, review it, and either reject or approve the account? Multiple persons often see more bugs/error/mistakes/whatever then one person. Won't this decrease 'quality'? Yes, but it will obviously increase quantity. And that is, as we all know, a good thing! Marc -- Fachbegriffe der Informatik - Einfach erklärt 40: overdrive processor Prozessor mit übertriebenem Preis-Leistungsverhältnis (Holger Reif) pgpwZY4kI11n5.pgp Description: PGP signature
Re: fresh blood gets congested: long way to become DD
On Tue, Aug 02, 2005 at 04:36:28PM +0200, Petter Reinholdtsen wrote: Do you have any good arguments why it isn't the other way around, that some of the rejections get rid of people which could have done a great job as a debian developer? How about 'not second guessing people without cause'? I'm not going to argue that the rejections being made are bad ones. If you are, this is the wrong place to do it. If you're not, then you don't have a point here. -- .''`. ** Debian GNU/Linux ** | Andrew Suffield : :' : http://www.debian.org/ | `. `' | `- -- | signature.asc Description: Digital signature
Re: fresh blood gets congested: long way to become DD
[Andrew Suffield] How about 'not second guessing people without cause'? Sounds like a good idea. I am not sure how this comment is connected to the message you replied to. I tried to avoid second guessing you, by asking the following question: You seem to assume that all rejections are correct, and get rid of some people which should not be accepted as debian developers, while all approvals are suspect and might let through a person which should have been rejected. Is this correct? You choose to ignore it, so I am still not sure about your opinion. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: jigdo-search
On 02/08/2005 Bartosz Fenski aka fEnIo wrote: After last talk about searching for packages on CDs Gaëtan Frenoy wrote some shell script along with PHP script for such purposes and sent me it todays morning. I made some modifications to it (support for DVDs and get rid of some temporary files), and it's now at my people.d.o page[1]. Any comments/requests are welcome. great work. it would be a good idea to integrate this search into www.debian.org/CD/ or add at least a link there. bye jonas signature.asc Description: Digital signature
Re: How to use svn(-buildpackage) with pbuilder?
If I have the complete upstream source in SVN, but not the .tar.gz, how do I create the .orig.tar.gz, when I have a new upstream version? Look down the thread -- your question was answered: Date: Mon, 01 Aug 2005 16:03:03 +0200 From: Arjan Oosting [EMAIL PROTECTED] To: debian-mentors@lists.debian.org Subject: Re: How to use svn(-buildpackage) with pbuilder? X-Spam-Level: gpg: Signature made Mon Aug 1 10:03:03 2005 EDT using DSA key ID 962E3890 gpg: Can't check signature: public key not found [-- The following data is signed --] Op ma, 01-08-2005 te 13:44 +0200, schreef Matthijs Mohlmann: I don't want to have all revisions of the package that ever existed on my filesystem. Is it possible to make svn-buildpackage create the tarballs on build-time? AFAIK it isn't possible. It is, the orig.tar.gz is created if you do a FORCEEXPORT=yes svn-buildpackage It is not recommended to use this though because the resulting orig.tar.gz might be different (md5 checksum) from the upstream version which can complicate things substantially. Greetings Arjan Oosting [-- End of signed data --] Cheers, -- .-. =-- /v\ = Keep in touch// \\ (yoh@|www.)onerussian.com Yaroslav Halchenko /( )\ ICQ#: 60653192 Linux User^^-^^[17] pgpTmTM83TSDK.pgp Description: PGP signature
Steve Kemp [EMAIL PROTECTED] Please check your Debian E-Mail.
I was finally able to acquire an SSP Build Host for you. If you are still interest. Please contact me. -- greg, [EMAIL PROTECTED] For technology that is Strong, Better, Faster: Linux signature.asc Description: This is a digitally signed message part
Bug#321009: ITP: liblocale-ruby -- extension to the Ruby intepreter for supporting locales
Package: wnpp Severity: wishlist Owner: Antonio S. de A. Terceiro [EMAIL PROTECTED] * Package name: liblocale-ruby Version : 0.1 Upstream Author : Rob Blackbourn [EMAIL PROTECTED] * URL : http://sourceforge.net/projects/ruby-locale * License : GPL Description : extension to the Ruby intepreter for supporting locales This package provides an extension to Ruby, so Ruby programs can use locales for, say, formatting dates and all other locale-related stuff. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.7-ruby Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to use svn(-buildpackage) with pbuilder?
Op di, 02-08-2005 te 17:50 +, schreef W. Borgert: On Sun, Jul 31, 2005 at 07:03:14AM -0400, Yaroslav Halchenko wrote: borrowed from a nice minimalistic HOWTO http://workaround.org/moin/SvnBuildpackage That is indeed a very helpful HOWTO. Thanks! 3 and 5 just add them to --svn-postbuild as IT IS SAID IN THE MAN PAGE: :-) OK, thanks. One more question, I could not answer myself from reading the man page: If I have the complete upstream source in SVN, but not the .tar.gz, how do I create the .orig.tar.gz, when I have a new upstream version? svn-upgrade path/to/new-upstream.tar.gz Greetings Arjan Oosting -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: I need to know how to create and use Driver Update Disks
-Original Message- From: Rob Taylor [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 02, 2005 10:13 AM To: debian-devel@lists.debian.org Subject: Re: I need to know how to create and use Driver Update Disks The Debian package system does not really like packages (your driver update) replacing files that belong to another package (the official Debian kernel-image package). This means the best option would be to get the patches included in an update of the 2.6.8 kernel (which is being prepared at the moment). If he produces a new kernel module to add support for this hardware, there's absolutely no reason why it should conflict with linux-kernel. Given that it's not a security fix, would he really have much luck getting a patch into stable's kernel? This is what I anticipate doing. As there is a period of time between when I submit my patches against the Sarge 2.6.8 kernel and when (or if) the appear in Sarge; I will need something for customers to use so that then can still install the present Sarge onto a system that requires the drivers. In one case, the kernel that is used by the installer will need the patches; otherwise the installer will not be able to access the hard drive. Right now, I am doing tests to determine if the 2.6.11 kernel that I have found in Etch is capable of accessing the ICH7 devices in our equipment. If it doesn't, then I plan to come up with a patch for the 2.6.11 kernel in Etch for the kernel group. Mark
Re: RFC: allow new upstream into stable when it's the only way tofix security issues.
How about if it meets the folowing critieria: 1. it has been in testing for 10 days (been in sid at least 20 days) 2. the version is sid is the same as in testing (the maintainer has not found problems in the ten days since it entered testing) 3. and has no RC bugs (no rc bugs reported in the ten days it has been in testing) 4. It fixes security or stability bugs (whose fixes would normally be backported) that cannot reasonably be backported. Then (at the discretion of the maintainer) it can be: 1. uploaded to stable-proposed-updates (it will only get in to stable with stable RM's approval) OR 2. Iff it fixes a critical security problem, uploaded to security (This requires security team and/or stable RM approval). This makes sure it is fairly stable, yet allows bugs in programs like mozilla (when the new upstream version should only be fixing bugs anyway). -- I think the no new upstream versions is stable rule needs to be more flexible anyway. I have seen times where EVERY SINGLE change except for the version number have been backported. That is often the case where the new release consists of nothing but the desired changes. In those cases it is illogical not to just go with the new versions. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: net-tools maintenance status
On Tue, Aug 02, 2005 at 07:45:12PM +0200, Olaf van der Spek wrote: What's the maintenance status of the net-tools package? It is maintained. Patches are welcome. http://packages.qa.debian.org/n/net-tools.html Which patch are you talking about? Greetings Bernd -- (OO) -- [EMAIL PROTECTED] -- ( .. )[EMAIL PROTECTED],linux.de,debian.org} http://www.eckes.org/ o--o 1024D/E383CD7E [EMAIL PROTECTED] v:+497211603874 f:+49721151516129 (OO) When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#321022: ITP: msort -- utility for sorting records in complex ways
Package: wnpp Severity: wishlist Owner: Bartosz Fenski aka fEnIo [EMAIL PROTECTED] -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 * Package name: msort Version : 8.4 Upstream Author : William J. Poser [EMAIL PROTECTED] * URL : http://www.cis.upenn.edu/~wjposer/msort.html * License : GPL Description : utility for sorting records in complex ways msort is a program for sorting files in sophisticated ways. It was originally developed for alphabetizing dictionaries of exotic languages, for which it has been extensively used, but is useful for many other purposes. msort differs from typical sort utilities in providing greater flexibility in parsing the input into records and identifying key fields and greater control over the sort order. Its main distinctive features are: * Msort can be used as a command-line program or via a graphical user interface that is helpful not only to those who find a complicated command line difficult to deal with but also to those unfamiliar with the finer points of sorting. * Records need not be single lines of text but may be delimited in a number of ways. * Key fields may be selected either by position in the record (counting from the beginning or the end) or by matching a regular expression to a tag. * For each key an arbitrary sort order may be specified. * For each key an effectively unlimited number of multigraphs (sequences of characters to be treated as a single unit for purposes of sorting) of effectively unlimited length may be defined. * In addition to the usual lexicographic and numerical orderings, msort supports sorting by date, time, and string length. * For each key a distinct set of characters may be excluded from consideration when sorting in any combination of initial, final, and medial position in the key field. * Lexicographic keys may be reversed, allowing the construction of reverse dictionaries. * Any or all keys may be optional. For optional keys, the user may specify how records missing the key field should compare to records in which the key field is present. msort understands UTF-8 Unicode. Unicode may be used anywhere that text is entered: in the text to be sorted, in sort order and exclusion definitions, as a field or record separator, or as a field tag. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC7+LqhQui3hP+/EARAvygAJ4wj9WsxYMqmfIgekhRH+TZm44eGwCfTs3u 1KmBwuhy2RsgHqeZ+z2FCvc= =RaI+ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: fresh blood gets congested: long way to become DD
On Tue, Aug 02, 2005 at 09:35:24PM +0200, Petter Reinholdtsen wrote: [Andrew Suffield] How about 'not second guessing people without cause'? Sounds like a good idea. I am not sure how this comment is connected to the message you replied to. It was an answer to the quoted question. I tried to avoid second guessing you, by asking the following question: You seem to assume that all rejections are correct, and get rid of some people which should not be accepted as debian developers, while all approvals are suspect and might let through a person which should have been rejected. Is this correct? You choose to ignore it, so I am still not sure about your opinion. That question is irrelevant to my point and furthermore it's a distraction, so I will continue to ignore it. I have no interest in the tangent you are trying to redirect towards. -- .''`. ** Debian GNU/Linux ** | Andrew Suffield : :' : http://www.debian.org/ | `. `' | `- -- | signature.asc Description: Digital signature
Re: I need to know how to create and use Driver Update Disks
On Tuesday 02 August 2005 23:03, Allyn, MarkX A wrote: Right now, I am doing tests to determine if the 2.6.11 kernel that I have found in Etch is capable of accessing the ICH7 devices in our equipment. If it doesn't, then I plan to come up with a patch for the 2.6.11 kernel in Etch for the kernel group. I doubt that is really useful. The 2.6.11 kernel is unlikely to live long after the packaging for the 2.6.12 kernels is stabilized. As I suggested earlier, IMO you should really take this to the d-kernel list instead of d-devel. Cheers, Frans Pop pgpLUP1aJCX8Y.pgp Description: PGP signature
Re: net-tools maintenance status
On 8/2/05, Bernd Eckenfels [EMAIL PROTECTED] wrote: On Tue, Aug 02, 2005 at 07:45:12PM +0200, Olaf van der Spek wrote: What's the maintenance status of the net-tools package? It is maintained. Patches are welcome. http://packages.qa.debian.org/n/net-tools.html Which patch are you talking about? The one for --wide
Bruce Perens hosts party at OSCON Wednesday night
For those of you who are at OSCON, Wednesday night I'm hosting a recruiting party for Sourcelabs. If you bring your resume I'll buy you drinks and some food. Date: Wednesday, August 3 Time: 8:30-10:30pm Place: Kells Irish Restaurant Pub, Ulster Room, 2nd Floor 112 SW 2nd Ave., Portland, Oregon 97201 Thanks Bruce Perens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFC: allow new upstream into stable when it's the only way tofix security issues.
On Tue, 2005-08-02 at 17:19 -0400, Joe Smith wrote: I think the no new upstream versions is stable rule needs to be more flexible anyway. I have seen times where EVERY SINGLE change except for the version number have been backported. That is often the case where the new release consists of nothing but the desired changes. In those cases it is illogical not to just go with the new versions. But that's only possible when there were no releases in between. And those are probably rare cases anyway. Kind regards, Philipp Kern -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
mass bug filing on packages that are blocking use of cdebconf
I intend to eventually file bugs on packages in Debian which depend on debconf without an alternate of debconf-2.0, as all of these make it impossible to install cdebconf, which we would eventually like to replace debconf. debconf-2.0 was added to policy as a virtual package in 2002 and has been provided by debconf since 2003. In early 2004, dh_installdebconf began automatically adding it as an alternate to debconf in dependencies it generates for packages using debhelper. 303 packages use the virtual package correctly; the following 761 do not. Also, every single (!) package that pre-depends on debconf does not include the alternative of debconf-2.0. Since so many packages need to be fixed, I may resort to additional private mails (or d-d-a mail) before I begin filing bug reports. The following is a list by maintainer of packages that Depend or Pre-Depend on debconf without a | debconf-2.0. If your package is on this list, please fix it. If your package is on this list incorrectly (ie, if it really depends on debconf for some reason), please let me know. Wesley W. Terpstra (Debian) [EMAIL PROTECTED] bidentd Loic Dachary (OuoU) [EMAIL PROTECTED] poker-network poker3d Stefan Hornburg (Racke) [EMAIL PROTECTED] amavis-ng courier debaux dhelp interchange pure-ftpd sympa Maurizio Lemmo (Tannoiser) [EMAIL PROTECTED] mailreader Marco Presi (Zufus) [EMAIL PROTECTED] linesrv pointless Krzysztof Krzyzaniak (eloy) [EMAIL PROTECTED] popa3d Masayuki Hatta (mhatta) [EMAIL PROTECTED] gs-common gtktrain ndtpd Peter De Schrijver (p2) [EMAIL PROTECTED] libgcr410 Clint Adams [EMAIL PROTECTED] posh zsh Joel Aelwyn [EMAIL PROTECTED] zope-quotafolder OHASHI Akira [EMAIL PROTECTED] initz riece Jan Alonzo [EMAIL PROTECTED] ispell-tl Pierre Ancelot [EMAIL PROTECTED] hwtools Micah Anderson [EMAIL PROTECTED] bamboo Osamu Aoki [EMAIL PROTECTED] ipmasq Hakan Ardo [EMAIL PROTECTED] ftpwatch Ben Armstrong [EMAIL PROTECTED] xpilot Richard Atterer [EMAIL PROTECTED] udftools Julien BLACHE [EMAIL PROTECTED] sane-backends tilp Thomas Bushnell, BSG [EMAIL PROTECTED] miscfiles Sebastien Bacher [EMAIL PROTECTED] pango1.0 Jeff Bailey [EMAIL PROTECTED] diffmon Michael Banck [EMAIL PROTECTED] exult Denis Barbier [EMAIL PROTECTED] belocs-locales-data kbd Andreas Barth [EMAIL PROTECTED] mgetty Roland Bauerschmidt [EMAIL PROTECTED] colormake Christian Bayle [EMAIL PROTECTED] gforge-theme-starterpack php4-mcrypt Ian Beckwith [EMAIL PROTECTED] ckermit Cord Beermann [EMAIL PROTECTED] jove nn Bradley Bell [EMAIL PROTECTED] razzle Hilko Bengen [EMAIL PROTECTED] drupal mantis Edward Betts [EMAIL PROTECTED] joystick Adrian von Bidder [EMAIL PROTECTED] postgrey Michael Biebl [EMAIL PROTECTED] lksctp-tools partimage Kęstutis Biliūnas [EMAIL PROTECTED] ispell-lt Bastian Blank [EMAIL PROTECTED] zope-loginmanager Blars Blarson [EMAIL PROTECTED] hinfo Eduard Bloch [EMAIL PROTECTED] durep shfs sl-modem Jeremy T. Bouse [EMAIL PROTECTED] acidlab Cyril Bouthors [EMAIL PROTECTED] drbd Markus Braun [EMAIL PROTECTED] tpb Adrian Bridgett [EMAIL PROTECTED] tgif James Bromberger [EMAIL PROTECTED] libapache-mod-backhand Phil Brooke [EMAIL PROTECTED] yiff Mark Brown [EMAIL PROTECTED] leafnode nis Philip Brown [EMAIL PROTECTED] kdrill Luis Bustamante [EMAIL PROTECTED] acct Chris Butler [EMAIL PROTECTED] wu-ftpd Bruno Barrera C. [EMAIL PROTECTED] portsentry Rubén Porras Campo [EMAIL PROTECTED] manpages-es Devin Carraway [EMAIL PROTECTED] qpsmtpd Patrick Caulfield [EMAIL PROTECTED] dnprogs lvm10 mopd Petr Cech [EMAIL PROTECTED] ispell-czech Emmanuel le Chevoir [EMAIL PROTECTED] icecast-server xsmbrowser Pierre Chifflier [EMAIL PROTECTED] websvn Volker Christian [EMAIL PROTECTED] synce-serial Luk Claes [EMAIL PROTECTED] tripwire Ashley Clark [EMAIL PROTECTED] bottlerocket Jesus Climent [EMAIL PROTECTED] pconsole rssh David Coe [EMAIL PROTECTED] libsafe Ben Collins [EMAIL PROTECTED] libraw1394 Carlo Contavalli [EMAIL PROTECTED] wipl Jereme Corrado [EMAIL PROTECTED] faqomatic Matthew Danish [EMAIL PROTECTED] oftpd Julien Danjou [EMAIL PROTECTED] apt-build Frederik Dannemare [EMAIL PROTECTED] motion Vivek Dasmohapatra [EMAIL PROTECTED] dbishell Debian Apache Maintainers debian-apache@lists.debian.org apache apache2 Debian Hamradio Maintainers debian-hams@lists.debian.org ax25-apps Debian OCaml Maintainers debian-ocaml-maint@lists.debian.org ocaml-tools Debian Qt/KDE Maintainers debian-qt-kde@lists.debian.org kdebase kdenetwork Debian X Strike Force debian-x@lists.debian.org xorg-x11 Eric Delaunay [EMAIL PROTECTED] scsitools xtel Cédric Delfosse [EMAIL PROTECTED] darkstat Murat Demirten [EMAIL PROTECTED]
Re: mass bug filing on packages that are blocking use of cdebconf
On Tue, Aug 02, 2005 at 06:46:20PM -0400, Joey Hess wrote: Matt Zimmerman [EMAIL PROTECTED] apt-listchanges cricket flac I have no idea how or why flac ended up with a debconf dependency; it doesn't use it. I've removed it in CVS for my next upload; no bug is necessary. -- - mdz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bruce Perens hosts party at OSCON Wednesday night
On Tue, 2 Aug 2005, Bruce Perens wrote: For those of you who are at OSCON, Wednesday night I'm hosting a recruiting party for Sourcelabs. If you bring your resume I'll buy you drinks and some food. Date: Wednesday, August 3 Time: 8:30-10:30pm Place: Kells Irish Restaurant Pub, Ulster Room, 2nd Floor 112 SW 2nd Ave., Portland, Oregon 97201 Unsolicited Commercial Email. Please pay the standard $2000 fee for advertisments on Debian mailing lists. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: fresh blood gets congested: long way to become DD
On Tue, Aug 02, 2005 at 03:01:39PM +0200, Tomas Fasth wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andreas Barth skrev: * Thijs Kinkhorst ([EMAIL PROTECTED]) [050802 13:41]: And even then, appearently the DAM works like this: I approve person X, let's check his box, but I'll add the account at some point later on (this takes weeks on average). When you check the box you might add the account aswell when you're at it, right? Just that the person who checks the reports is not root in Debian's ldap system. There is delegation and group access available in OpenLDAP. So, one would not need to have write access to the whole directory tree, only to the necessary branches. I'm amused that you think there's anything in Debian's LDAP directory *besides the user accounts themselves that you're proposing to give people access to* that would warrant this level of granular access control. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: Bruce Perens hosts party at OSCON Wednesday night
On Tue, Aug 02, 2005 at 06:32:44PM -0500, Adam Heath wrote: On Tue, 2 Aug 2005, Bruce Perens wrote: For those of you who are at OSCON, Wednesday night I'm hosting a recruiting party for Sourcelabs. If you bring your resume I'll buy you drinks and some food. Date: Wednesday, August 3 Time: 8:30-10:30pm Place: Kells Irish Restaurant Pub, Ulster Room, 2nd Floor 112 SW 2nd Ave., Portland, Oregon 97201 Unsolicited Commercial Email. Please pay the standard $2000 fee for advertisments on Debian mailing lists. Y'know, it's fine if you think that Bruce's mail was inappropriate for the list, and there's nothing wrong with saying so; but claiming that a message that isn't selling anything is UCE, and attempting to enforce against a member of the community an advertising policy that daily goes unenforced against thousands of more deserving souls, just makes you sound like an asshole and an idiot. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: Bruce Perens hosts party at OSCON Wednesday night
Oh my goodness, Adam. If I wanted to advertise, I'd ask the DPL for some freebies. I must merit them by now. The fact is, some people there might really want to see me. Some of them are even my friends. And it happens that I have to be at this party for work, and my employer will pay for anyone who brings a resume. Free beer, as they say. But if the consensus of the other folks on debian-devel is that this message did not belong there, I will apologize and withdraw it. Thanks Bruce Adam Heath wrote: On Tue, 2 Aug 2005, Bruce Perens wrote: For those of you who are at OSCON, Wednesday night I'm hosting a recruiting party for Sourcelabs. If you bring your resume I'll buy you drinks and some food. Date: Wednesday, August 3 Time: 8:30-10:30pm Place: Kells Irish Restaurant Pub, Ulster Room, 2nd Floor 112 SW 2nd Ave., Portland, Oregon 97201 Unsolicited Commercial Email. Please pay the standard $2000 fee for advertisments on Debian mailing lists. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bruce Perens hosts party at OSCON Wednesday night
On Tue, 2 Aug 2005, Bruce Perens wrote: Oh my goodness, Adam. If I wanted to advertise, I'd ask the DPL for some freebies. I must merit them by now. If you had just said that you were hosting a dinner, that'd be one thing. But you solicted resumes. That's what pushed it into UCE land. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bruce Perens hosts party at OSCON Wednesday night
On Tue, 2 Aug 2005, Steve Langasek wrote: On Tue, Aug 02, 2005 at 06:32:44PM -0500, Adam Heath wrote: On Tue, 2 Aug 2005, Bruce Perens wrote: For those of you who are at OSCON, Wednesday night I'm hosting a recruiting party for Sourcelabs. If you bring your resume I'll buy you drinks and some food. Date: Wednesday, August 3 Time: 8:30-10:30pm Place: Kells Irish Restaurant Pub, Ulster Room, 2nd Floor 112 SW 2nd Ave., Portland, Oregon 97201 Unsolicited Commercial Email. Please pay the standard $2000 fee for advertisments on Debian mailing lists. Y'know, it's fine if you think that Bruce's mail was inappropriate for the list, and there's nothing wrong with saying so; but claiming that a message that isn't selling anything is UCE, and attempting to enforce against a member of the community an advertising policy that daily goes unenforced against thousands of more deserving souls, just makes you sound like an asshole and an idiot. C does not mean sell. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: I need to know how to create and use Driver Update Disks
On Tuesday 02 August 2005 09:03 am, Frans Pop wrote: The Debian package system does not really like packages (your driver update) replacing files that belong to another package (the official Debian kernel-image package). This means the best option would be to get the patches included in an update of the 2.6.8 kernel (which is being prepared at the moment). I think you could resolve the packaging issue with diverts if necessary. Daniel -- /--- Daniel Burrows [EMAIL PROTECTED] --\ | But what *does* kill me bloody well leaves me dead! | | -- Terry Pratchett, _Carpe Jugulum_ | \ Got APT? -- Debian GNU/Linux http://www.debian.org ---/ pgpbxRgWLF4gr.pgp Description: PGP signature
Re: Bruce Perens hosts party at OSCON Wednesday night
Steve Langasek [EMAIL PROTECTED] writes: On Tue, Aug 02, 2005 at 06:32:44PM -0500, Adam Heath wrote: Unsolicited Commercial Email. Please pay the standard $2000 fee for advertisments on Debian mailing lists. claiming that a message that isn't selling anything is UCE, and attempting to enforce against a member of the community an advertising policy that daily goes unenforced against thousands of more deserving souls, just makes you sound like an asshole and an idiot. I'm not sure what difference it makes though; he was just being obnoxious. Everybody will just ignore Adam, a few who need jobs will see Bruce, and we'll all continue on our merry way. -miles -- P.S. All information contained in the above letter is false, for reasons of military security. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bruce Perens hosts party at OSCON Wednesday night
On Tuesday 02 August 2005 18:13, Bruce Perens wrote: Oh my goodness, Adam. If I wanted to advertise, I'd ask the DPL for some freebies. I must merit them by now. The fact is, some people there might really want to see me. Some of them are even my friends. And it happens that I have to be at this party for work, and my employer will pay for anyone who brings a resume. Free beer, as they say. But if the consensus of the other folks on debian-devel is that this message did not belong there, I will apologize and withdraw it. FWIW, I didn't think it was out of line. I thought, wow, that'd be cool to go meet Bruce; too bad I'm not in that area. -- Wesley J. Landaker [EMAIL PROTECTED] OpenPGP FP: 4135 2A3B 4726 ACC5 9094 0097 F0A9 8A4C 4CD6 E3D2 pgpXJz7WCqEe4.pgp Description: PGP signature
Re: Bruce Perens hosts party at OSCON Wednesday night
On 8/2/05, Adam Heath [EMAIL PROTECTED] wrote: Unsolicited Commercial Email. Please pay the standard $2000 fee for advertisments on Debian mailing lists. Adam, I'm kind of curious what you mean by that. What, if any, actual or proposed statutory standard for UCE did you have in mind when you called Bruce's message UCE? What, if anything, are or should be the consequences if he doesn't pay $2000 to whomever you had in mind? How can I tell whether a message I'm thinking of sending will trigger the same penalties? How do people receive notice of this standard? Cheers, - Michael
Re: Usability: Technical details in package descriptions?
Hi all, Debtags shows great promise in covering the technical aspect of describing Debian packages. Debtags do a better job than Package Descriptions when it comes to precisely describing a package in a highly-technical, highly-searchable format (that is fully geek compliant). Wouldn't it make sense that debtags and Package Descriptions not do redundant work of each other? I propose that by a simple split in the use of the Package Description and debtags between the internal world (ie. relative to the computer) and external world (ie. relative to the end user's real life apart from their computer), respectively, I think we can make the best use of volunteer effort as they review the Package Descriptions and create debtags. I think that the Package Description should be (re)written using language intended at your grandma. This way she can intuitively find packages also without needing to learn about the debtags system. Learning how to use the search button in Synaptic is work enough for her, let alone learn and play with debtags to do wild and crazy searching (with logical operators no less). As debtags cater to the geek, I think the Package Description should cater to grandma. I think the package desription should state the purpose of the software as it relates to the real world, whenever possible: eg. helps you easily keep lists of contact information on people along with details like their birthdays. A description like this is useful to grandma. Anything more technical and you lose her to the likes of Ubuntu or Linspire. Come on, throw grandma a (less than 80 character) bone! Grandma can give back some day by helping to file a bug report or something. I therefore propose that ***the package description should explain how a package could be used for real-world usefulness for the end user***, giving an example or two for those with dimmer imaginations than hard core geeks. In my example above, mentioning tracking birthdays helps users start imagining the potential usefulness of the software. Note how mozilla.org has a screenshot of the craiglist website on the front page to help users *imagine* visiting a website like craigslist using the browser (albeit visually, not textually). Same idea. Imagining how some piece of software could be useful is hard work for most people, and you can help them tremendously by providing a simple and obvious-to-you example in the package description. Debtags will much better handle all the fine-grained, geeky details, like the language it was written in, and to which suite it belongs. Therefore ***I think debtags should aim to exclusively describe a package's relationship to the internal system it lives in, ie. relative to Debian.*** And on a related tangent, wouldn't it also make sense that all the volunteers who are going to examine all the package descriptions one at a time also create the appropriate debtags while they are at it? This could further help eliminate redundancy in what debtags and package descriptions explain. At the very least, wouldn't it make sense for there to be more coordination between the debtags effort, and the Packages Descriptions review campaign? Maybe the gui tool debtags-editor should/could be extended to *also* allow editing of package descriptions? Cheers, -- Dustin Harriman http://annexia.ca -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted aptitude 0.2.15.9-5 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 1 Aug 2005 18:17:18 -0700 Source: aptitude Binary: aptitude-doc-cs aptitude-doc-fr aptitude-doc-en aptitude Architecture: source all i386 Version: 0.2.15.9-5 Distribution: unstable Urgency: low Maintainer: Daniel Burrows [EMAIL PROTECTED] Changed-By: Daniel Burrows [EMAIL PROTECTED] Description: aptitude - terminal-based apt frontend aptitude-doc-cs - Czech manual for aptitude, a terminal-based apt frontend aptitude-doc-en - English manual for aptitude, a terminal-based apt frontend aptitude-doc-fr - French manual for aptitude, a terminal-based apt frontend Closes: 320859 Changes: aptitude (0.2.15.9-5) unstable; urgency=low . * Update gettext aclocals. (Closes: #320859) Files: aad67483b969232b51213f9012517655 787 admin optional aptitude_0.2.15.9-5.dsc 72cb1dfda88fc5b29c024ad8bd124d5d 162530 admin optional aptitude_0.2.15.9-5.diff.gz 71a63d0da782b6a4947c03a0fd56fb9c 365698 doc optional aptitude-doc-cs_0.2.15.9-5_all.deb 1bab34367d0c45c11fa3284a0b2b1daf 349584 doc optional aptitude-doc-en_0.2.15.9-5_all.deb eca2b00ada4499a3e58364b10c93d63c 361800 doc optional aptitude-doc-fr_0.2.15.9-5_all.deb 1a21595a06590cac0b641a416d6f5e5c 1026986 admin optional aptitude_0.2.15.9-5_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC7wYTch6xsM7kSXgRAt07AKDJiZfV40r72BlxGn+4bosj5K6XsACfeEdR iI+rqIjg6wCkdh+e3QVX4lc= =x8zM -END PGP SIGNATURE- Accepted: aptitude-doc-cs_0.2.15.9-5_all.deb to pool/main/a/aptitude/aptitude-doc-cs_0.2.15.9-5_all.deb aptitude-doc-en_0.2.15.9-5_all.deb to pool/main/a/aptitude/aptitude-doc-en_0.2.15.9-5_all.deb aptitude-doc-fr_0.2.15.9-5_all.deb to pool/main/a/aptitude/aptitude-doc-fr_0.2.15.9-5_all.deb aptitude_0.2.15.9-5.diff.gz to pool/main/a/aptitude/aptitude_0.2.15.9-5.diff.gz aptitude_0.2.15.9-5.dsc to pool/main/a/aptitude/aptitude_0.2.15.9-5.dsc aptitude_0.2.15.9-5_i386.deb to pool/main/a/aptitude/aptitude_0.2.15.9-5_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted aspell 0.60.3-5 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 1 Aug 2005 23:56:49 -0700 Source: aspell Binary: libpspell-dev libaspell15c2 libaspell15 aspell libaspell-dev aspell-doc Architecture: source all i386 Version: 0.60.3-5 Distribution: unstable Urgency: low Maintainer: Brian Nelson [EMAIL PROTECTED] Changed-By: Brian Nelson [EMAIL PROTECTED] Description: aspell - GNU Aspell spell-checker aspell-doc - Documentation for GNU Aspell spell-checker libaspell-dev - Development files for applications with GNU Aspell support libaspell15 - GNU Aspell spell-checker runtime library libaspell15c2 - GNU Aspell spell-checker runtime library [dummy] libpspell-dev - Development files for applications with pspell support Closes: 111929 Changes: aspell (0.60.3-5) unstable; urgency=low . * Moved the 01_autotools patch to 10_autotools . * debian/patches/01_debctrl: wrote a patch for a Debian packaging control file filter (Closes: #111929) . * debian/patches/10_autotools: reran autotools to update build system so that it builds the debctrl filter . * Updated aspell.1 manual to document the new debctrl filter Files: 93a1bb01ff85a77ef1c97535cc5283f7 690 text optional aspell_0.60.3-5.dsc ac8b43142fe536cacf42bc4f4175cd7a 110810 text optional aspell_0.60.3-5.diff.gz 6c7ff059b3c342459aede2e1a4b7e780 154492 doc optional aspell-doc_0.60.3-5_all.deb 6aa27057279c9c998d0fae49a69b9b24 40840 libs optional libaspell15c2_0.60.3-5_all.deb 6ef6f11ed8392f6403ea49c7b09b25e1 263508 text optional aspell_0.60.3-5_i386.deb ffbc38ad4cab55299586bc0d5dbfb4c7 689530 libs optional libaspell15_0.60.3-5_i386.deb 908bd8dd3cc41f6080032a9c8107127c 46898 libdevel optional libaspell-dev_0.60.3-5_i386.deb 11f393583c29058d7ee126b4da814621 44016 libdevel optional libpspell-dev_0.60.3-5_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC7xvp1Ng1YWbyRSERAk0iAJwPfdEYMBXc6xemzubf3Hf8SOrJNACfch1J 8DXpSI21O5FvnUr8IYvXYNw= =YGp6 -END PGP SIGNATURE- Accepted: aspell-doc_0.60.3-5_all.deb to pool/main/a/aspell/aspell-doc_0.60.3-5_all.deb aspell_0.60.3-5.diff.gz to pool/main/a/aspell/aspell_0.60.3-5.diff.gz aspell_0.60.3-5.dsc to pool/main/a/aspell/aspell_0.60.3-5.dsc aspell_0.60.3-5_i386.deb to pool/main/a/aspell/aspell_0.60.3-5_i386.deb libaspell-dev_0.60.3-5_i386.deb to pool/main/a/aspell/libaspell-dev_0.60.3-5_i386.deb libaspell15_0.60.3-5_i386.deb to pool/main/a/aspell/libaspell15_0.60.3-5_i386.deb libaspell15c2_0.60.3-5_all.deb to pool/main/a/aspell/libaspell15c2_0.60.3-5_all.deb libpspell-dev_0.60.3-5_i386.deb to pool/main/a/aspell/libpspell-dev_0.60.3-5_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted synaesthesia 2.3-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 2 Aug 2005 00:01:01 -0700 Source: synaesthesia Binary: synaesthesia Architecture: source i386 Version: 2.3-2 Distribution: unstable Urgency: low Maintainer: Devin Carraway [EMAIL PROTECTED] Changed-By: Devin Carraway [EMAIL PROTECTED] Description: synaesthesia - A program for representing sounds visually Changes: synaesthesia (2.3-2) unstable; urgency=low . * Rebuild for gcc4 ABI changes * Standards-Version 3.6.2 * Rearrange build-deps for xorg's new scheme Files: c9fc8205729a38559422a7a25e8357fd 683 sound optional synaesthesia_2.3-2.dsc 3720c9299d1e8920bcb27bda9492af6c 4359 sound optional synaesthesia_2.3-2.diff.gz 666c60c04738c01e427ccee23424b4c3 77122 sound optional synaesthesia_2.3-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC7x/fU5XKDemr/NIRAo45AKDmNcW/GaHjxenoGhVInR7wxDCROQCcDc+2 i09uDhZ5KUhPBCVKJHHT7eg= =/2j4 -END PGP SIGNATURE- Accepted: synaesthesia_2.3-2.diff.gz to pool/main/s/synaesthesia/synaesthesia_2.3-2.diff.gz synaesthesia_2.3-2.dsc to pool/main/s/synaesthesia/synaesthesia_2.3-2.dsc synaesthesia_2.3-2_i386.deb to pool/main/s/synaesthesia/synaesthesia_2.3-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mozilla-thunderbird 1.0.6-3 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 2 Aug 2005 17:00:00 +0100 Source: mozilla-thunderbird Binary: mozilla-thunderbird-dev mozilla-thunderbird-inspector mozilla-thunderbird mozilla-thunderbird-typeaheadfind mozilla-thunderbird-offline Architecture: source i386 Version: 1.0.6-3 Distribution: unstable Urgency: low Maintainer: Alexander Sack [EMAIL PROTECTED] Changed-By: Alexander Sack [EMAIL PROTECTED] Description: mozilla-thunderbird - Mozilla Thunderbird standalone mail client mozilla-thunderbird-dev - mozilla thunderbird development files mozilla-thunderbird-inspector - mozilla thunderbird dom inspector extension mozilla-thunderbird-offline - mozilla thunderbird offline extension mozilla-thunderbird-typeaheadfind - mozilla thunderbird typeaheadfind extension Closes: 320723 Changes: mozilla-thunderbird (1.0.6-3) unstable; urgency=low . * remove gcc-3.4 from amd64 build ... this time for sure (Closes: 320723) * remove special optimization flags for other archs too Files: c1eb52f95a96ee31ce393f01d9ada0ea 899 mail optional mozilla-thunderbird_1.0.6-3.dsc a7f32cdfc422ee97d0633b166a482b5b 95539 mail optional mozilla-thunderbird_1.0.6-3.diff.gz 9fd0b856282db44429f28a6957185951 10636960 mail optional mozilla-thunderbird_1.0.6-3_i386.deb d7c45e49081a087bafaf9a230169356f 27128 mail optional mozilla-thunderbird-offline_1.0.6-3_i386.deb 28c670d80ef7566a99566243a75fda97 139458 mail optional mozilla-thunderbird-inspector_1.0.6-3_i386.deb 0b0a28f3546da5b2d87703a2cfd47462 78270 mail optional mozilla-thunderbird-typeaheadfind_1.0.6-3_i386.deb 580814babd012aea099ce8edff0a9dbe 3563978 mail optional mozilla-thunderbird-dev_1.0.6-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC7ymUv8pLOKgkuT8RAjPzAJ9STzFiNwRjBK5ypU0elBzfg4VDcACfVRKW XfIQELMpKzAz/2DqlkKZRHQ= =g/a+ -END PGP SIGNATURE- Accepted: mozilla-thunderbird-dev_1.0.6-3_i386.deb to pool/main/m/mozilla-thunderbird/mozilla-thunderbird-dev_1.0.6-3_i386.deb mozilla-thunderbird-inspector_1.0.6-3_i386.deb to pool/main/m/mozilla-thunderbird/mozilla-thunderbird-inspector_1.0.6-3_i386.deb mozilla-thunderbird-offline_1.0.6-3_i386.deb to pool/main/m/mozilla-thunderbird/mozilla-thunderbird-offline_1.0.6-3_i386.deb mozilla-thunderbird-typeaheadfind_1.0.6-3_i386.deb to pool/main/m/mozilla-thunderbird/mozilla-thunderbird-typeaheadfind_1.0.6-3_i386.deb mozilla-thunderbird_1.0.6-3.diff.gz to pool/main/m/mozilla-thunderbird/mozilla-thunderbird_1.0.6-3.diff.gz mozilla-thunderbird_1.0.6-3.dsc to pool/main/m/mozilla-thunderbird/mozilla-thunderbird_1.0.6-3.dsc mozilla-thunderbird_1.0.6-3_i386.deb to pool/main/m/mozilla-thunderbird/mozilla-thunderbird_1.0.6-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted efax-gtk 3.0.3-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Jul 2005 00:01:20 +0300 Source: efax-gtk Binary: efax-gtk Architecture: source i386 Version: 3.0.3-1 Distribution: unstable Urgency: low Maintainer: Lior Kaplan [EMAIL PROTECTED] Changed-By: Lior Kaplan [EMAIL PROTECTED] Description: efax-gtk - front end in GTK+ for the efax program Closes: 267484 Changes: efax-gtk (3.0.3-1) unstable; urgency=low . * New upstream release. * Closes: #267484: need an option to hide calling-card code * Upgrade standards version to 3.6.2 (no changes needed) * Created man page for efax-gtk-socket-client. Files: 29edb1377b2adac8e1cf239e53519925 653 comm optional efax-gtk_3.0.3-1.dsc b85c209ede9e35f4cebfe22a2d4a7ce2 793184 comm optional efax-gtk_3.0.3.orig.tar.gz bc2ab4a1549de68875c253cb81c07678 22612 comm optional efax-gtk_3.0.3-1.diff.gz 0020ab7211483d83f40570966879330e 527526 comm optional efax-gtk_3.0.3-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC7yiNqeKiif08kWsRApFFAJ4yIcqA4eLTLq8fkXaSxr/CtXNgUQCffeBM bH66XLiJ3/0B3oTazeaA8Gg= =rtkT -END PGP SIGNATURE- Accepted: efax-gtk_3.0.3-1.diff.gz to pool/main/e/efax-gtk/efax-gtk_3.0.3-1.diff.gz efax-gtk_3.0.3-1.dsc to pool/main/e/efax-gtk/efax-gtk_3.0.3-1.dsc efax-gtk_3.0.3-1_i386.deb to pool/main/e/efax-gtk/efax-gtk_3.0.3-1_i386.deb efax-gtk_3.0.3.orig.tar.gz to pool/main/e/efax-gtk/efax-gtk_3.0.3.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted baobab 1.0.1-3 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 02 Aug 2005 10:52:45 +0200 Source: baobab Binary: baobab Architecture: source i386 Version: 1.0.1-3 Distribution: unstable Urgency: low Maintainer: Fabio Marzocca [EMAIL PROTECTED] Changed-By: Fabio Marzocca [EMAIL PROTECTED] Description: baobab - graphical tool to analyse directory trees Changes: baobab (1.0.1-3) unstable; urgency=low . * Changes to build on arch-dependent platforms Files: 71cca01ef47fc943cc02676a2e0632fd 604 x11 optional baobab_1.0.1-3.dsc 0440d6a046769d3a5679c7fc67ad302f 2225 x11 optional baobab_1.0.1-3.diff.gz 9866a5b7b18623f18a3b524f264514e9 38386 x11 optional baobab_1.0.1-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC7y7DKN6ufymYLloRAsbIAJ40FlFWwinty076TN/kk5soChwKHgCeLl// 2Vg65qTxv5wG4TxCiLxV4zw= =xqpE -END PGP SIGNATURE- Accepted: baobab_1.0.1-3.diff.gz to pool/main/b/baobab/baobab_1.0.1-3.diff.gz baobab_1.0.1-3.dsc to pool/main/b/baobab/baobab_1.0.1-3.dsc baobab_1.0.1-3_i386.deb to pool/main/b/baobab/baobab_1.0.1-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted adesklets 0.4.10-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 2 Aug 2005 10:03:53 +0200 Source: adesklets Binary: adesklets Architecture: source i386 Version: 0.4.10-2 Distribution: unstable Urgency: low Maintainer: Bartosz Fenski [EMAIL PROTECTED] Changed-By: Bartosz Fenski [EMAIL PROTECTED] Description: adesklets - interactive Imlib2 console for the X Window System Closes: 317489 318184 318186 319949 Changes: adesklets (0.4.10-2) unstable; urgency=low . * Fixes in configure patch partially based on Matt Kraai's patch. (Closes: #317489) * Added README.Debian file with some explanations about configuration of desklets. (Closes: #318184) * Including INSTALL file cause README refers to it. (Closes: #318186) * Bumped Standards-Version to 3.6.2 (no changes needed). * Moved menu file to /usr/share instead of /usr/lib. * Whole documentation is now released under GPL (Closes: #319949) Mail from author included to document this change. Files: 512bb93807c31b486ca3daa2790b6fc9 694 x11 optional adesklets_0.4.10-2.dsc 6a58dbd332f81d11350809f6415221e8 58413 x11 optional adesklets_0.4.10-2.diff.gz a67dd3cf487689dae94dc795db531628 308114 x11 optional adesklets_0.4.10-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC7yuXhQui3hP+/EARAlKPAJ9Sz/7pYAyu1nyfw3V+U9uSUD2WaQCePhEj FApQnbzZYNqiiNZZhQVeGXg= =jEP0 -END PGP SIGNATURE- Accepted: adesklets_0.4.10-2.diff.gz to pool/main/a/adesklets/adesklets_0.4.10-2.diff.gz adesklets_0.4.10-2.dsc to pool/main/a/adesklets/adesklets_0.4.10-2.dsc adesklets_0.4.10-2_i386.deb to pool/main/a/adesklets/adesklets_0.4.10-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted glibmm2.4 2.6.1-1.2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 2 Aug 2005 10:04:58 +0200 Source: glibmm2.4 Binary: libglibmm-2.4-dev libglibmm-2.4-1c2 Architecture: source i386 Version: 2.6.1-1.2 Distribution: unstable Urgency: medium Maintainer: Bradley Bell [EMAIL PROTECTED] Changed-By: Matthias Klose [EMAIL PROTECTED] Description: libglibmm-2.4-1c2 - C++ wrapper for the GLib toolkit (shared libraries) libglibmm-2.4-dev - C++ wrapper for the GLib toolkit (development files) Changes: glibmm2.4 (2.6.1-1.2) unstable; urgency=medium . * NMU. * Tighten the (build-)dependency on libsigc++2.0-dev to the first version built with g++-4.0. Files: cd83606eeabef94c795c20578461bbb6 657 libs optional glibmm2.4_2.6.1-1.2.dsc 310f191eb985db453148c6ff93d2bf0c 5952 libs optional glibmm2.4_2.6.1-1.2.diff.gz 2fa37c31e20ead10ce15e67d2d9f3c52 725448 libdevel optional libglibmm-2.4-dev_2.6.1-1.2_i386.deb dfc7da1db6700ad162b04db175243212 131742 libs optional libglibmm-2.4-1c2_2.6.1-1.2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC7ysmStlRaw+TLJwRArVXAKCgSaEk/5qvTHPbXNPrBJH2tiPAqgCgtCj+ 204s//22xRdw1GNwG2Q+JbI= =7/XK -END PGP SIGNATURE- Accepted: glibmm2.4_2.6.1-1.2.diff.gz to pool/main/g/glibmm2.4/glibmm2.4_2.6.1-1.2.diff.gz glibmm2.4_2.6.1-1.2.dsc to pool/main/g/glibmm2.4/glibmm2.4_2.6.1-1.2.dsc libglibmm-2.4-1c2_2.6.1-1.2_i386.deb to pool/main/g/glibmm2.4/libglibmm-2.4-1c2_2.6.1-1.2_i386.deb libglibmm-2.4-dev_2.6.1-1.2_i386.deb to pool/main/g/glibmm2.4/libglibmm-2.4-dev_2.6.1-1.2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gtkmm2.0 2.2.12-1.3 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 2 Aug 2005 09:42:00 +0200 Source: gtkmm2.0 Binary: libgtkmm2.0-doc libgtkmm2.0-dev libgtkmm2.0-1c2 Architecture: source all i386 Version: 2.2.12-1.3 Distribution: unstable Urgency: medium Maintainer: Bradley Bell [EMAIL PROTECTED] Changed-By: Matthias Klose [EMAIL PROTECTED] Description: libgtkmm2.0-1c2 - C++ wrappers for GTK+ 2.0 (shared libraries) libgtkmm2.0-dev - C++ wrappers for GTK+ 2.0 (development files) libgtkmm2.0-doc - C++ wrappers for GTK+ 2.0 (documentation) Changes: gtkmm2.0 (2.2.12-1.3) unstable; urgency=medium . * NMU. * Tighten the (build-)dependency on libsigc++1.2-dev to the first version built with g++-4.0. Files: bf3058070e15c75e985597bca6a5fcec 693 libs optional gtkmm2.0_2.2.12-1.3.dsc f8ebe27bb98a3312017766bd05c464c6 135949 libs optional gtkmm2.0_2.2.12-1.3.diff.gz cc98f6cb8f004597828947caf97af210 3320138 doc optional libgtkmm2.0-doc_2.2.12-1.3_all.deb ab53fe681b3efb2c646bb65c7782f437 1764350 libdevel optional libgtkmm2.0-dev_2.2.12-1.3_i386.deb 5f86c3883e0cab21c98de0080dd80b88 922938 libs optional libgtkmm2.0-1c2_2.2.12-1.3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC7yqWStlRaw+TLJwRAi79AJ41NpxXG/Mq5LBopjoROT+fHrXMgwCdEI2L uuIiiWksMAu/2v/b2wxPtsY= =amIb -END PGP SIGNATURE- Accepted: gtkmm2.0_2.2.12-1.3.diff.gz to pool/main/g/gtkmm2.0/gtkmm2.0_2.2.12-1.3.diff.gz gtkmm2.0_2.2.12-1.3.dsc to pool/main/g/gtkmm2.0/gtkmm2.0_2.2.12-1.3.dsc libgtkmm2.0-1c2_2.2.12-1.3_i386.deb to pool/main/g/gtkmm2.0/libgtkmm2.0-1c2_2.2.12-1.3_i386.deb libgtkmm2.0-dev_2.2.12-1.3_i386.deb to pool/main/g/gtkmm2.0/libgtkmm2.0-dev_2.2.12-1.3_i386.deb libgtkmm2.0-doc_2.2.12-1.3_all.deb to pool/main/g/gtkmm2.0/libgtkmm2.0-doc_2.2.12-1.3_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted kaffe 2:1.1.5-4 (source all powerpc)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 16 Jul 2005 13:32:59 +0200 Source: kaffe Binary: kaffe-dev kaffe-common jikes-kaffe kaffe-pthreads-profile kaffe-pthreads kaffe kaffe-doc kaffe-jthreads Architecture: source all powerpc Version: 2:1.1.5-4 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers [EMAIL PROTECTED] Changed-By: Wolfgang Baer [EMAIL PROTECTED] Description: jikes-kaffe - Wrapper for jikes using Kaffe classes kaffe - A JVM to run Java bytecode kaffe-common - Files shared between all Kaffe VM versions kaffe-dev - Header files and other resources for building against Kaffe kaffe-doc - Documentation for the Kaffe VM kaffe-jthreads - A green threads enabled version of the Kaffe VM kaffe-pthreads - A POSIX threads enabled version of the Kaffe VM Closes: 305608 317513 318511 318785 Changes: kaffe (2:1.1.5-4) unstable; urgency=low . * C++ transition (closes: #318511, #318785) + rebuilt against libgmp3-dev + debian/control + rules: removed gcc-3.4/g++-3.4 as compiler * Changed libpng3-dev (transitional package) to libpng12-dev * Removed shlibs.local - not needed anymore * Cleaned debian directory - removed unused files (still available in our cvs) * Added and installed lintian overrides file for pthreads-profile to fix lintian error unstripped-binary (which is explicitly excluded in dh_strip) . * Build pthreads-profile only on specific systems (closes: #305608) + Define SYSTEMS to include pthreads-profile in rules.i386 only + Reworked install target to iterate over defined systems in SYSTEMS . * Kaffe specific changes: + Reworked kaffe commands linking in alternatives system to reduce needed link dereferences - fixes too many levels of symbolic links (closes: #317513) + Only link (not copy) tools.jar/gmpjavamath.jar to the runtimes + Enabled --with-profiling --enable-xprofiling for pthreads-profile build + Removed duplicated --with-jikes flages in configure + Cleaned up debian/rules . * Standards-Version 3.6.2 - no changes * Added myself to uploaders . * Upload sponsored by Arnaud Vandyck Files: 5980c589df214fdd6e9b0cb092dfc98b 1114 interpreters optional kaffe_1.1.5-4.dsc 48ddca39f038d5191e12190083e70141 33789 interpreters optional kaffe_1.1.5-4.diff.gz a1ccd3c33375bca20fe0ebadcc5bd56e 25990 interpreters optional kaffe_1.1.5-4_all.deb 1195722635543919346bd5cc4a38a609 6463332 interpreters optional kaffe-common_1.1.5-4_all.deb 0ecc150f64fbab8ab105d9ba56f59522 42240 interpreters optional kaffe-dev_1.1.5-4_all.deb 83fa1911e4345e5d2ed91ca81d0d6a87 25014 interpreters optional jikes-kaffe_1.1.5-4_all.deb f83a7520d9ba305a2e063a0e638c9aca 106584 interpreters optional kaffe-doc_1.1.5-4_all.deb e35d0bcbbe78e4d1ec570c6acbdb3507 373776 interpreters optional kaffe-jthreads_1.1.5-4_powerpc.deb ebcb3af18a3750f253f9366907ce748c 482692 interpreters optional kaffe-pthreads_1.1.5-4_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC7xFX4vzFZu62tMIRAu/WAJ0fIrU94LYumEqMULX0icbWeBfZXgCfXOuU BZbWO+i1sOo/aePSQ9yM3n4= =Fq1h -END PGP SIGNATURE- Accepted: jikes-kaffe_1.1.5-4_all.deb to pool/main/k/kaffe/jikes-kaffe_1.1.5-4_all.deb kaffe-common_1.1.5-4_all.deb to pool/main/k/kaffe/kaffe-common_1.1.5-4_all.deb kaffe-dev_1.1.5-4_all.deb to pool/main/k/kaffe/kaffe-dev_1.1.5-4_all.deb kaffe-doc_1.1.5-4_all.deb to pool/main/k/kaffe/kaffe-doc_1.1.5-4_all.deb kaffe-jthreads_1.1.5-4_powerpc.deb to pool/main/k/kaffe/kaffe-jthreads_1.1.5-4_powerpc.deb kaffe-pthreads_1.1.5-4_powerpc.deb to pool/main/k/kaffe/kaffe-pthreads_1.1.5-4_powerpc.deb kaffe_1.1.5-4.diff.gz to pool/main/k/kaffe/kaffe_1.1.5-4.diff.gz kaffe_1.1.5-4.dsc to pool/main/k/kaffe/kaffe_1.1.5-4.dsc kaffe_1.1.5-4_all.deb to pool/main/k/kaffe/kaffe_1.1.5-4_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted openoffice.org 1.1.4-5 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 1 Aug 2005 11:48:00 +0200 Source: openoffice.org Binary: openoffice.org-l10n-el openoffice.org-l10n-en openoffice.org-l10n-ja openoffice.org-l10n-zu openoffice.org-l10n-fr openoffice.org-l10n-zh-cn openoffice.org-l10n-pt-br openoffice.org-l10n-es openoffice.org openoffice.org-l10n-af openoffice.org-l10n-zh-tw openoffice.org-l10n-ru openoffice.org-l10n-tr openoffice.org-dev openoffice.org-l10n-hi openoffice.org-l10n-de openoffice.org-l10n-pl openoffice.org-l10n-eu openoffice.org-l10n-gl openoffice.org-l10n-lt openoffice.org-thesaurus-en-us openoffice.org-l10n-kn openoffice.org-gtk-gnome openoffice.org-l10n-da openoffice.org-kde openoffice.org-l10n-hu openoffice.org-mimelnk openoffice.org-l10n-sk openoffice.org-l10n-pt openoffice.org-l10n-nn openoffice.org-l10n-it openoffice.org-java openoffice.org-l10n-nb openoffice.org-l10n-ca openoffice.org-l10n-he openoffice.org-l10n-sl openoffice.org-l10n-ar ttf-opensymbol openoffice.org-evolution openoffice.org-l10n-et openoffice.org-l10n-ko openoffice.org-gnomevfs openoffice.org-bin openoffice.org-l10n-fi openoffice.org-l10n-cy openoffice.org-l10n-nl openoffice.org-l10n-tn openoffice.org-l10n-sv openoffice.org-l10n-th openoffice.org-l10n-ns openoffice.org-l10n-cs Architecture: all i386 source Version: 1.1.4-5 Distribution: unstable Urgency: low Maintainer: Debian OpenOffice Team debian-openoffice@lists.debian.org Changed-By: Rene Engelhard [EMAIL PROTECTED] Description: openoffice.org - high-quality office productivity suite openoffice.org-bin - OpenOffice.org office suite binary files openoffice.org-dev - OpenOffice.org SDK - development files openoffice.org-evolution - Evolution 2 Addressbook support for OpenOffice.org openoffice.org-gnomevfs - GNOME VFS support for OpenOffice.org openoffice.org-gtk-gnome - Gtk UI Plugin and GNOME File Picker for OpenOffice.org openoffice.org-java - Java support for OpenOffice.org openoffice.org-kde - KDE UI Plugin and KDE File Picker for OpenOffice.org openoffice.org-l10n-af - Afrikaans language package for OpenOffice.org openoffice.org-l10n-ar - Arabic language package for OpenOffice.org openoffice.org-l10n-ca - Catalan language package for OpenOffice.org openoffice.org-l10n-cs - Czech language package for OpenOffice.org openoffice.org-l10n-cy - Welsh language package for OpenOffice.org openoffice.org-l10n-da - Danish language package for OpenOffice.org openoffice.org-l10n-de - German language package for OpenOffice.org openoffice.org-l10n-el - Greek language package for OpenOffice.org openoffice.org-l10n-en - English (US) language package for OpenOffice.org openoffice.org-l10n-es - Spanish language package for OpenOffice.org openoffice.org-l10n-et - Estonian language package for OpenOffice.org openoffice.org-l10n-eu - Basque language package for OpenOffice.org openoffice.org-l10n-fi - Finnish language package for OpenOffice.org openoffice.org-l10n-fr - French language package for OpenOffice.org openoffice.org-l10n-gl - Galician language package for OpenOffice.org openoffice.org-l10n-he - Hebrew language package for OpenOffice.org openoffice.org-l10n-hi - Hindi language package for OpenOffice.org openoffice.org-l10n-hu - Hungarian language package for OpenOffice.org openoffice.org-l10n-it - Italian language package for OpenOffice.org openoffice.org-l10n-ja - Japanese language package for OpenOffice.org openoffice.org-l10n-kn - Kannada language package for OpenOffice.org openoffice.org-l10n-ko - Korean language package for OpenOffice.org openoffice.org-l10n-lt - Lithuanian language package for OpenOffice.org openoffice.org-l10n-nb - Norwegian Bokmal language package for OpenOffice.org openoffice.org-l10n-nl - Dutch language package for OpenOffice.org openoffice.org-l10n-nn - Norwegian Nynorsk language package for OpenOffice.org openoffice.org-l10n-ns - Northern Sotho language package for OpenOffice.org openoffice.org-l10n-pl - Polish language package for OpenOffice.org openoffice.org-l10n-pt - Portuguese language package for OpenOffice.org openoffice.org-l10n-pt-br - Portuguese (Brazil) language package for OpenOffice.org openoffice.org-l10n-ru - Russian language package for OpenOffice.org openoffice.org-l10n-sk - Slovak language package for OpenOffice.org openoffice.org-l10n-sl - Slovenian language package for OpenOffice.org openoffice.org-l10n-sv - Swedish language package for OpenOffice.org openoffice.org-l10n-th - Thai language package for OpenOffice.org openoffice.org-l10n-tn - Tswana language package for OpenOffice.org openoffice.org-l10n-tr - Turkish language package for OpenOffice.org openoffice.org-l10n-zh-cn - Chinese Simplified language package for OpenOffice.org openoffice.org-l10n-zh-tw - Chinese Traditional language package for OpenOffice.org openoffice.org-l10n-zu - Zulu language package for OpenOffice.org openoffice.org-mimelnk - OpenOffice.org MIME bindings for KDE
Accepted sbcl 1:0.9.3.0-1 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 29 Jul 2005 12:36:30 +0200 Source: sbcl Binary: sbcl sbcl-common Architecture: source i386 all Version: 1:0.9.3.0-1 Distribution: unstable Urgency: low Maintainer: Peter Van Eynde [EMAIL PROTECTED] Changed-By: Peter Van Eynde [EMAIL PROTECTED] Description: sbcl - A development environment for Common Lisp sbcl-common - Architecture independent files for SBCL Changes: sbcl (1:0.9.3.0-1) unstable; urgency=low . * New upstream, kept the patches from Satoshi to have a fall-back encoding. * Added generated ChangeLog Files: 974c1dd6e832c82e57310be9744ca501 678 devel optional sbcl_0.9.3.0-1.dsc c0cfe156e3eefeac3864b30452b5fa0c 3749421 devel optional sbcl_0.9.3.0.orig.tar.gz a57c5ad79113d70d2a877bfd0db41781 22480 devel optional sbcl_0.9.3.0-1.diff.gz c3846b28ab91350e3d22ff26b98d3374 3891798 devel optional sbcl-common_0.9.3.0-1_all.deb f90351ed411166faa0d66469a59dbfaa 8428118 devel optional sbcl_0.9.3.0-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC6+g711ldN0tyliURAm99AKCpUsnc2xj/jN/SvdXeGn+bxid6dwCcCLBN XDAytmyNeDK4Qr81ss9q7I4= =9N3Z -END PGP SIGNATURE- Accepted: sbcl-common_0.9.3.0-1_all.deb to pool/main/s/sbcl/sbcl-common_0.9.3.0-1_all.deb sbcl_0.9.3.0-1.diff.gz to pool/main/s/sbcl/sbcl_0.9.3.0-1.diff.gz sbcl_0.9.3.0-1.dsc to pool/main/s/sbcl/sbcl_0.9.3.0-1.dsc sbcl_0.9.3.0-1_i386.deb to pool/main/s/sbcl/sbcl_0.9.3.0-1_i386.deb sbcl_0.9.3.0.orig.tar.gz to pool/main/s/sbcl/sbcl_0.9.3.0.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cmucl 19b-release-20050726-1 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 30 Jul 2005 22:26:40 +0200 Source: cmucl Binary: cmucl cmucl-source cmucl-clm cmucl-docs Architecture: source all i386 Version: 19b-release-20050726-1 Distribution: unstable Urgency: low Maintainer: Peter Van Eynde [EMAIL PROTECTED] Changed-By: Peter Van Eynde [EMAIL PROTECTED] Description: cmucl - The CMUCL lisp compiler and development system cmucl-clm - The Motif interface for CMUCL cmucl-docs - The CMUCL documentation cmucl-source - The CMUCL lisp sources Changes: cmucl (19b-release-20050726-1) unstable; urgency=low . * add remove-clc to cmucl.sh implementation script [from rvb] * Upstream decided to un-release this version and go back to a pre2 version. As it is not possible to remove the release I have included the changes to pre2 in this release. Files: 266a4c2cab87cb57870eb97acaf4e7ca 739 devel optional cmucl_19b-release-20050726-1.dsc f26f1007a494e5d6e395a783c83f7aee 4644273 devel optional cmucl_19b-release-20050726.orig.tar.gz bb742d9fef5cab5eb9f9229989b4f813 1504221 devel optional cmucl_19b-release-20050726-1.diff.gz ffcec18c075e6b1b7ad8ffb05146cc9b 10531208 devel optional cmucl_19b-release-20050726-1_i386.deb ed6a84fad98401f7a8f0e137fce57fdf 651840 devel optional cmucl-clm_19b-release-20050726-1_i386.deb 28da1041c6d5d9aaf6f12ac6ad5e9c85 2277106 doc optional cmucl-docs_19b-release-20050726-1_all.deb e0102e25a9c5377b8c81497438a017a2 5166390 devel optional cmucl-source_19b-release-20050726-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC6++L11ldN0tyliURAtLTAJ4wvbK/+bsgIPypp+Dk9uxfUpHDeQCfV0Tk NMdRNPlNKWO0fKW6VHXjRnA= =V8C6 -END PGP SIGNATURE- Accepted: cmucl-clm_19b-release-20050726-1_i386.deb to pool/main/c/cmucl/cmucl-clm_19b-release-20050726-1_i386.deb cmucl-docs_19b-release-20050726-1_all.deb to pool/main/c/cmucl/cmucl-docs_19b-release-20050726-1_all.deb cmucl-source_19b-release-20050726-1_all.deb to pool/main/c/cmucl/cmucl-source_19b-release-20050726-1_all.deb cmucl_19b-release-20050726-1.diff.gz to pool/main/c/cmucl/cmucl_19b-release-20050726-1.diff.gz cmucl_19b-release-20050726-1.dsc to pool/main/c/cmucl/cmucl_19b-release-20050726-1.dsc cmucl_19b-release-20050726-1_i386.deb to pool/main/c/cmucl/cmucl_19b-release-20050726-1_i386.deb cmucl_19b-release-20050726.orig.tar.gz to pool/main/c/cmucl/cmucl_19b-release-20050726.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cl-split-sequence 20050802-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 2 Aug 2005 05:30:55 +0200 Source: cl-split-sequence Binary: cl-split-sequence Architecture: source all Version: 20050802-1 Distribution: unstable Urgency: low Maintainer: Peter Van Eynde [EMAIL PROTECTED] Changed-By: Peter Van Eynde [EMAIL PROTECTED] Description: cl-split-sequence - Common Lisp package split a sequence of objects Changes: cl-split-sequence (20050802-1) unstable; urgency=low . * Now uses darcs * Updated standard version * Recovered original upstream sources, no real changes. Files: 7c236fa3cead09f6582a77aff8da09cd 620 devel optional cl-split-sequence_20050802-1.dsc f44b173d57d16857689a54ab14401f22 2611 devel optional cl-split-sequence_20050802.orig.tar.gz ce74d603a42c4052e0643c2d3ae78c47 2457 devel optional cl-split-sequence_20050802-1.diff.gz 8372d2ada92f3a539db04942772a061d 4790 devel optional cl-split-sequence_20050802-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC7xcV11ldN0tyliURAt2xAKCIQy3PopLqGjvbeF8ZXZkWTMS9zgCgkSsS hK8p80V4fXwJxGMPP1q1h0E= =F5a6 -END PGP SIGNATURE- Accepted: cl-split-sequence_20050802-1.diff.gz to pool/main/c/cl-split-sequence/cl-split-sequence_20050802-1.diff.gz cl-split-sequence_20050802-1.dsc to pool/main/c/cl-split-sequence/cl-split-sequence_20050802-1.dsc cl-split-sequence_20050802-1_all.deb to pool/main/c/cl-split-sequence/cl-split-sequence_20050802-1_all.deb cl-split-sequence_20050802.orig.tar.gz to pool/main/c/cl-split-sequence/cl-split-sequence_20050802.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cl-salza 0.7.2-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 1 Aug 2005 15:04:16 +0200 Source: cl-salza Binary: cl-salza Architecture: source all Version: 0.7.2-1 Distribution: unstable Urgency: low Maintainer: Peter Van Eynde [EMAIL PROTECTED] Changed-By: Peter Van Eynde [EMAIL PROTECTED] Description: cl-salza - Common Lisp package to write compressed data Changes: cl-salza (0.7.2-1) unstable; urgency=low . * Move to darcs-buildpackage * New upstream * Added watch file * Upgraded standard version * removed shlibs Files: 9e25dd6f2480776729e5b183e2d3a361 576 devel optional cl-salza_0.7.2-1.dsc 3406619257e5813c2b0dca5a1d617dd7 13783 devel optional cl-salza_0.7.2.orig.tar.gz e6c6c7f346004fda41b9764474063d4a 2677 devel optional cl-salza_0.7.2-1.diff.gz ae043578643e2732e1078a01876d1852 17488 devel optional cl-salza_0.7.2-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC7h3711ldN0tyliURAqYKAKDG5ukyHH793d3xojWiQ/v9r3yoLACeKhzd WTWpeDE7LkTofjk0xM8V4gI= =WHNb -END PGP SIGNATURE- Accepted: cl-salza_0.7.2-1.diff.gz to pool/main/c/cl-salza/cl-salza_0.7.2-1.diff.gz cl-salza_0.7.2-1.dsc to pool/main/c/cl-salza/cl-salza_0.7.2-1.dsc cl-salza_0.7.2-1_all.deb to pool/main/c/cl-salza/cl-salza_0.7.2-1_all.deb cl-salza_0.7.2.orig.tar.gz to pool/main/c/cl-salza/cl-salza_0.7.2.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cl-port 20050624-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 5 Jul 2005 07:51:41 +0200 Source: cl-port Binary: cl-port Architecture: source all Version: 20050624-1 Distribution: unstable Urgency: low Maintainer: Peter Van Eynde [EMAIL PROTECTED] Changed-By: Peter Van Eynde [EMAIL PROTECTED] Description: cl-port- Common Lisp Object Collections Port Package Changes: cl-port (20050624-1) unstable; urgency=low . * Now uses clocc version instead of dead cclan version * Now uses darcs-buildpackage * Increased policy version Files: 7cee71d106e0c2b7641edd6c8c445117 581 devel optional cl-port_20050624-1.dsc f2c9c3153f9b8baff598d5bb6cf7342b 33234 devel optional cl-port_20050624.orig.tar.gz 505ee2cf2160c3a06726b4efabc4f715 3290 devel optional cl-port_20050624-1.diff.gz deddcdcca9dd2b84e3200d385335c82f 24282 devel optional cl-port_20050624-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC7fa011ldN0tyliURAs/GAKCdErFqXQIkX6+SWvGJ7U+mk3eghQCeNgr4 1F3UHqhet6+N4MA619Di72s= =1Nju -END PGP SIGNATURE- Accepted: cl-port_20050624-1.diff.gz to pool/main/c/cl-port/cl-port_20050624-1.diff.gz cl-port_20050624-1.dsc to pool/main/c/cl-port/cl-port_20050624-1.dsc cl-port_20050624-1_all.deb to pool/main/c/cl-port/cl-port_20050624-1_all.deb cl-port_20050624.orig.tar.gz to pool/main/c/cl-port/cl-port_20050624.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cl-aima 20020509-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 5 Jul 2005 07:51:15 +0200 Source: cl-aima Binary: cl-aima Architecture: source all Version: 20020509-1 Distribution: unstable Urgency: low Maintainer: Peter Van Eynde [EMAIL PROTECTED] Changed-By: Peter Van Eynde [EMAIL PROTECTED] Description: cl-aima- Source code for Artificial Intelligence: A Modern Approach Changes: cl-aima (20020509-1) unstable; urgency=low . * Recovered original upstream, bumped version number to release date. * Removed libraries from depends * Increased policy version * Cannot add watch-file :-( * Now in darcs archive Files: b68a718f84dbc6115dec3b2ffb370857 583 devel optional cl-aima_20020509-1.dsc c2ad8d624771a896ce7a4999c55cae05 188615 devel optional cl-aima_20020509.orig.tar.gz f52e95301d31d3c59af15c7fa698c700 22683 devel optional cl-aima_20020509-1.diff.gz 2cf8e99b8b27fc4254ff060dceadd3e7 175952 devel optional cl-aima_20020509-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC7Q4z11ldN0tyliURAs/KAJ4u+siH9eTbFUWwTSMzpYHvBXAW2ACdGzcJ qZfoR3aOEjRmqLaiSP3Pplc= =dmnJ -END PGP SIGNATURE- Accepted: cl-aima_20020509-1.diff.gz to pool/main/c/cl-aima/cl-aima_20020509-1.diff.gz cl-aima_20020509-1.dsc to pool/main/c/cl-aima/cl-aima_20020509-1.dsc cl-aima_20020509-1_all.deb to pool/main/c/cl-aima/cl-aima_20020509-1_all.deb cl-aima_20020509.orig.tar.gz to pool/main/c/cl-aima/cl-aima_20020509.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cl-cil 1:20050701-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 2 Jul 2005 10:04:33 +0200 Source: cl-cil Binary: cl-cil Architecture: source all Version: 1:20050701-1 Distribution: unstable Urgency: low Maintainer: Peter Van Eynde [EMAIL PROTECTED] Changed-By: Peter Van Eynde [EMAIL PROTECTED] Description: cl-cil - Chess In Lisp. A chess library in Common Lisp Changes: cl-cil (1:20050701-1) unstable; urgency=low . * Now uses darcs * Updated standard version * Now debhelper v4 * Now no longer a native package Files: be483f5ee2bf084e84a11f370a270f90 576 doc optional cl-cil_20050701-1.dsc bb742bb982e7064f3ac6c2e179b41a3d 23517 doc optional cl-cil_20050701.orig.tar.gz 897aecc6fbcdfa91984b14aa09c7bd96 213 doc optional cl-cil_20050701-1.diff.gz 8d64041431c534588dceed194fe9d2e5 40458 doc optional cl-cil_20050701-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC7R9r11ldN0tyliURAmKNAKDKdIikPx9CjWEMoOGowWdjlFJ0RwCeIMxJ 424oMAHPLtQh1OpxFg5dag4= =C9KV -END PGP SIGNATURE- Accepted: cl-cil_20050701-1.diff.gz to pool/main/c/cl-cil/cl-cil_20050701-1.diff.gz cl-cil_20050701-1.dsc to pool/main/c/cl-cil/cl-cil_20050701-1.dsc cl-cil_20050701-1_all.deb to pool/main/c/cl-cil/cl-cil_20050701-1_all.deb cl-cil_20050701.orig.tar.gz to pool/main/c/cl-cil/cl-cil_20050701.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cl-ansi-tests 20050704-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 5 Jul 2005 08:45:09 +0200 Source: cl-ansi-tests Binary: cl-ansi-tests Architecture: source all Version: 20050704-1 Distribution: unstable Urgency: low Maintainer: Peter Van Eynde [EMAIL PROTECTED] Changed-By: Peter Van Eynde [EMAIL PROTECTED] Description: cl-ansi-tests - Conformance tests for ANSI Common Lisp Changes: cl-ansi-tests (20050704-1) unstable; urgency=low . * New upstream * New version numbering: don't refer to cvs anymore * Updated policy version * Cannot add watch file :-( * Now in darcs archives * Add generated cvs upstream changelog Files: 7e595870997fdb2e11b6341c60491042 606 devel optional cl-ansi-tests_20050704-1.dsc 77f1b91c59252d0a96515b429eb4a533 858835 devel optional cl-ansi-tests_20050704.orig.tar.gz a275fb96eda4e34d5d46c1f24d45df28 1992 devel optional cl-ansi-tests_20050704-1.diff.gz 7fa5d0b2b26e3f6593aa0c85d66e81b1 766634 devel optional cl-ansi-tests_20050704-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC7Rv411ldN0tyliURAk8OAJ0bWUykLQezDAKfXxRagur5VdHcAACeKCFY H7uOl5z2qsXGLT29wlgBm7w= =nlaU -END PGP SIGNATURE- Accepted: cl-ansi-tests_20050704-1.diff.gz to pool/main/c/cl-ansi-tests/cl-ansi-tests_20050704-1.diff.gz cl-ansi-tests_20050704-1.dsc to pool/main/c/cl-ansi-tests/cl-ansi-tests_20050704-1.dsc cl-ansi-tests_20050704-1_all.deb to pool/main/c/cl-ansi-tests/cl-ansi-tests_20050704-1_all.deb cl-ansi-tests_20050704.orig.tar.gz to pool/main/c/cl-ansi-tests/cl-ansi-tests_20050704.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cl-clue 20050523-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 5 Jul 2005 07:51:18 +0200 Source: cl-clue Binary: cl-clue clue Architecture: source all Version: 20050523-1 Distribution: unstable Urgency: low Maintainer: Peter Van Eynde [EMAIL PROTECTED] Changed-By: Peter Van Eynde [EMAIL PROTECTED] Description: cl-clue- Lisp package for clue/clio/pictures: X interfaces for lisp clue - Package to ease upgrading, delete me Changes: cl-clue (20050523-1) unstable; urgency=low . * New upstream release * Now no longer a native package * Now uses darcs-buildpackage Files: 6b7a340ad869f387ed2dd46b610dc38c 586 libs optional cl-clue_20050523-1.dsc 4bf26948cf519c1f402b22c4dcafe8c5 1120028 libs optional cl-clue_20050523.orig.tar.gz 486ac6f9556c89b0e47fe16bc7c4319c 747 libs optional cl-clue_20050523-1.diff.gz 8a7c34fec865b1736478bf3225092d24 1612826 libs optional cl-clue_20050523-1_all.deb 739aec5ef474b2a541125788bb1b57c2 4998 libs optional clue_20050523-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC7R/P11ldN0tyliURAqbhAJ9HlQruPtlwf3Bs2kgVrKbYuZCfoQCeJplo hJ5EjTTi5VIdubbj3xovuYI= =TaaY -END PGP SIGNATURE- Accepted: cl-clue_20050523-1.diff.gz to pool/main/c/cl-clue/cl-clue_20050523-1.diff.gz cl-clue_20050523-1.dsc to pool/main/c/cl-clue/cl-clue_20050523-1.dsc cl-clue_20050523-1_all.deb to pool/main/c/cl-clue/cl-clue_20050523-1_all.deb cl-clue_20050523.orig.tar.gz to pool/main/c/cl-clue/cl-clue_20050523.orig.tar.gz clue_20050523-1_all.deb to pool/main/c/cl-clue/clue_20050523-1_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cl-csv 1.12-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 2 Jul 2005 10:05:01 +0200 Source: cl-csv Binary: cl-csv Architecture: source all Version: 1.12-1 Distribution: unstable Urgency: low Maintainer: Peter Van Eynde [EMAIL PROTECTED] Changed-By: Peter Van Eynde [EMAIL PROTECTED] Description: cl-csv - Common Lisp utility to import CSV text files Changes: cl-csv (1.12-1) unstable; urgency=low . * New upstream * Updated policy standard * No watch file possible * Now uses darcs-buildarchive Files: 53c56482b1c08dd163c1075f9ce0f8e2 564 devel optional cl-csv_1.12-1.dsc 1bf86db95e1a3e1b9ea5548d07b89eab 2687 devel optional cl-csv_1.12.orig.tar.gz 9ec61ac652e9cc9838f6515770b52022 3449 devel optional cl-csv_1.12-1.diff.gz 1087f29bc9c03a156038027217f96cf7 6532 devel optional cl-csv_1.12-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC7SBe11ldN0tyliURAgGMAJ4gB7djaNfmH5GaXnYn2hpmma8pUACgv2WP IvAfyaZzKQIvZoBV0ChGvXU= =V5Pj -END PGP SIGNATURE- Accepted: cl-csv_1.12-1.diff.gz to pool/main/c/cl-csv/cl-csv_1.12-1.diff.gz cl-csv_1.12-1.dsc to pool/main/c/cl-csv/cl-csv_1.12-1.dsc cl-csv_1.12-1_all.deb to pool/main/c/cl-csv/cl-csv_1.12-1_all.deb cl-csv_1.12.orig.tar.gz to pool/main/c/cl-csv/cl-csv_1.12.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cl-environment 1.12 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 5 Jul 2005 16:31:11 +0200 Source: cl-environment Binary: cl-environment Architecture: source all Version: 1.12 Distribution: unstable Urgency: low Maintainer: Peter Van Eynde [EMAIL PROTECTED] Changed-By: Peter Van Eynde [EMAIL PROTECTED] Description: cl-environment - Object-Oriented Environment Encapsulation for Common Lisp Program Changes: cl-environment (1.12) unstable; urgency=low . * New upstream * Update policy standard * Now uses darcs-buildpackage * Removed shlibs:Depends Files: a76be981ed347163aa4964f23e3eb34c 521 devel optional cl-environment_1.12.dsc 9b0e930ec042b18e95170c669242fa89 24843 devel optional cl-environment_1.12.tar.gz c720b8ecf8581d1e29067837a3fccd5f 13130 devel optional cl-environment_1.12_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC7SHP11ldN0tyliURAuFyAKDNjuNuRO36IIYsxuMrBmkwEsFOIQCgm1H6 nNrI8DB+oLya17uPU7gOgWw= =l2A9 -END PGP SIGNATURE- Accepted: cl-environment_1.12.dsc to pool/main/c/cl-environment/cl-environment_1.12.dsc cl-environment_1.12.tar.gz to pool/main/c/cl-environment/cl-environment_1.12.tar.gz cl-environment_1.12_all.deb to pool/main/c/cl-environment/cl-environment_1.12_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cl-f2cl 20050619-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 2 Aug 2005 08:54:23 +0200 Source: cl-f2cl Binary: cl-f2cl Architecture: source all Version: 20050619-1 Distribution: unstable Urgency: low Maintainer: Peter Van Eynde [EMAIL PROTECTED] Changed-By: Peter Van Eynde [EMAIL PROTECTED] Description: cl-f2cl- Common Lisp package to convert Fortran 77 source code to Common L Changes: cl-f2cl (20050619-1) unstable; urgency=low . * New upstream * Updated policy version * No uses darcs-buildpackage * No longer a native package. * Remove CVS junk Files: 5ef6cf8fe0d88cc0f73f3c9175a3cc6d 582 devel optional cl-f2cl_20050619-1.dsc f63a3dc501754ef9483e242136be1754 1005042 devel optional cl-f2cl_20050619.orig.tar.gz 5e31b5bf62e3277c3e2933c242bbcd8e 628 devel optional cl-f2cl_20050619-1.diff.gz 6b49670f9ac096e84575290b0035f064 173454 devel optional cl-f2cl_20050619-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC7ydK11ldN0tyliURAn51AKCt2FtuAKM+gkUSG9mwoW/eCrj19QCfedw0 SQRE/MitZfR3KQPHvGgpjqQ= =dNvK -END PGP SIGNATURE- Accepted: cl-f2cl_20050619-1.diff.gz to pool/main/c/cl-f2cl/cl-f2cl_20050619-1.diff.gz cl-f2cl_20050619-1.dsc to pool/main/c/cl-f2cl/cl-f2cl_20050619-1.dsc cl-f2cl_20050619-1_all.deb to pool/main/c/cl-f2cl/cl-f2cl_20050619-1_all.deb cl-f2cl_20050619.orig.tar.gz to pool/main/c/cl-f2cl/cl-f2cl_20050619.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cl-defsystem3 3.5i+2005.07.01-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 2 Jul 2005 23:43:23 +0200 Source: cl-defsystem3 Binary: cl-defsystem3 Architecture: source all Version: 3.5i+2005.07.01-1 Distribution: unstable Urgency: low Maintainer: Peter Van Eynde [EMAIL PROTECTED] Changed-By: Peter Van Eynde [EMAIL PROTECTED] Description: cl-defsystem3 - Make system for Common Lisp Packages Changes: cl-defsystem3 (3.5i+2005.07.01-1) unstable; urgency=low . * New upstream release * Move to darcs * Updated policy standard * Now no longer a native package Files: aa9b46b95c97a364d9a49290c5743e4f 625 devel optional cl-defsystem3_3.5i+2005.07.01-1.dsc c610013cc083445f45860bda88ffdf02 2 devel optional cl-defsystem3_3.5i+2005.07.01.orig.tar.gz 7078fdbeb1dda6a2c0eb8adc77f4ff9d 283 devel optional cl-defsystem3_3.5i+2005.07.01-1.diff.gz 7633d83978d04212e651c9c5423a9205 85300 devel optional cl-defsystem3_3.5i+2005.07.01-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC7SEH11ldN0tyliURAtg7AJ4pRUKCrW9uqhekCWl2Mr9Goj2F+ACgyrF+ Ogf3U+A09ZGYjLn8AagyAKw= =vDyP -END PGP SIGNATURE- Accepted: cl-defsystem3_3.5i+2005.07.01-1.diff.gz to pool/main/c/cl-defsystem3/cl-defsystem3_3.5i+2005.07.01-1.diff.gz cl-defsystem3_3.5i+2005.07.01-1.dsc to pool/main/c/cl-defsystem3/cl-defsystem3_3.5i+2005.07.01-1.dsc cl-defsystem3_3.5i+2005.07.01-1_all.deb to pool/main/c/cl-defsystem3/cl-defsystem3_3.5i+2005.07.01-1_all.deb cl-defsystem3_3.5i+2005.07.01.orig.tar.gz to pool/main/c/cl-defsystem3/cl-defsystem3_3.5i+2005.07.01.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cl-html-template 0.3.0-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 5 Jul 2005 07:51:21 +0200 Source: cl-html-template Binary: cl-html-template Architecture: source all Version: 0.3.0-1 Distribution: unstable Urgency: low Maintainer: Peter Van Eynde [EMAIL PROTECTED] Changed-By: Peter Van Eynde [EMAIL PROTECTED] Description: cl-html-template - Common Lisp HTML Template processor Changes: cl-html-template (0.3.0-1) unstable; urgency=low . * New upstream * No watch file possible :-( * Updated policy version * Now uses darcs-buildpackage Files: 678ab98702167f9974e779a8d8fbb206 608 devel optional cl-html-template_0.3.0-1.dsc 93613a9c09a2e8c29ff2aa0bd6ec5f6a 25909 devel optional cl-html-template_0.3.0.orig.tar.gz fa6e7056a00089c15fabbc28251a 2703 devel optional cl-html-template_0.3.0-1.diff.gz 3a581359d384ccbf331cd348302ee678 28896 devel optional cl-html-template_0.3.0-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC7Sf/11ldN0tyliURAiKWAKCeDiEdbW4ufiDkBvmvExZSQxjbMgCgoivw jqoekA0kVv3dipgjIXqs0x4= =je9T -END PGP SIGNATURE- Accepted: cl-html-template_0.3.0-1.diff.gz to pool/main/c/cl-html-template/cl-html-template_0.3.0-1.diff.gz cl-html-template_0.3.0-1.dsc to pool/main/c/cl-html-template/cl-html-template_0.3.0-1.dsc cl-html-template_0.3.0-1_all.deb to pool/main/c/cl-html-template/cl-html-template_0.3.0-1_all.deb cl-html-template_0.3.0.orig.tar.gz to pool/main/c/cl-html-template/cl-html-template_0.3.0.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
