Results of the meeting in Helsinki about the Vancouver proposal
Hi all, Vancouver has gotten a very specific meaning in the Debian community: one of a visionary proposal[1] that received quite its share of flames from many Debian contributors, including myself. Since it appeared to many of us that the intentional result of this proposal would have been to essentially kill off many of our architectures, many of us weren't too happy with the proposal. In subsequent communication with some of the people present at the Vancouver meeting, however, it became apparent to me that this was not the idea; rather, the proposal tried to create a set of quality requirements for all of our ports, so that our users would be guaranteed to get, for example, a Debian/SPARC of the same quality as Debian/PowerPC. This in itself is a laudable goal; but as I felt that the requirements, as proposed, did not meet that goal, I called for a meeting at DebConf5 with all parties involved and present at the conference. This meeting has taken place on 2005-07-11[2], with the following people attending: * Bdale Garbee, DPL team member, has been involved with the startup of 5 ports; * Branden Robinson, DPL; * Wouter Verhelst, m68k porter; * Gerfried Fuchs, local admin to buildd machines; * Joey Hess, core d-i developer, present at the Vancouver meeting; * Kurt Roeckx, non-DD amd64 porter; * Anthony Towns, FTP-master, present at the Vancouver meeting; * Jeroen van Wolffelaar, DPL team member, FTP team member, present at the Vancouver meeting; * James Troup, arm and sparc buildd admin, DSA team member, FTP-master, present at the Vancouver meeting; * Florian Lohoff, mips/mipsel porter, local admin to buildd machines; * Andreas Barth, Release Assistant, present at the Vancouver meeting; * Guido Günther, mips/mipsel porter; * Robert Jordens, DD; * Steinar Gunderson, DD In addition, I have, beforehand, exchanged mail with Joey Schulze of the Debian Security team about this meeting, and he's provided me with his opinion on the matter. While I did my best to get a wide range of people to attend, two notable absentees are both our Release Managers. Since they couldn't be in Helsinki, they obviously couldn't be at this meeting either (although they've had the opportunity to review this text before it was sent out); therefore, while we've come up with all sorts of things, they're not to be seen as any sort of official release policy statement -- unless, of course, it is officially added to our release policy by the release team. Anyway. The problematic items we discussed at this meeting included the following four points: 1. The requirement that 'an architecture must be publically available to buy new'. It was explained that this requirement was not made to be applied retroactively to already existing ports; rather, it was designed to avoid new hardware which, as of yet, is only available under NDA, or to avoid things such as a Vax port of Debian. Older ports, such as m68k and arm, are expected to reach a natural end-of-life to a point where it no longer is possible for Debian and the port's porters to support it, at which point the port would then, of course, be dropped. With this explanation and rationale, nobody at the meeting no longer had any opposition to the requirement, and it was retained. 2. The requirement that any architecture needs to be able to keep up with unstable by using only two buildd machines. The rationale for this requirement was that there is a nontrivial cost to each buildd, which increases super-linearly; apparently, there have been cases in the past where this resulted in ports with many autobuilders slacking when updates were necessary (such as with the recent security autobuilder problems). On the flip side, it was argued that more autobuilders results in more redundancy; with a little overcapacity, there is a gain here over an architecture which has just one autobuilder, where then that single autobuilder goes down. This item was much debated, and we didn't reach an agreement; in the end, we decided to move on. We hope that after more debate, we will reach a solution that is acceptable to everyone, but in the mean time, the requirement remains (but see below). 3. The veto powers given to the DSA team, the Security team, and the Release team, on a release of any given port. Some of us feared for abuse of this veto power. All understood the problems that exist if any port is of such low quality that it would suck up the time of any of the three given teams; however, we felt that a nonspecific veto power as proposed would be too far-reaching. At first, a counter-proposal was made which would require the three teams to discuss a pending removal of a port together with the porters team, and require them to come to an agreement. This was dismissed, since a) this would move the problems to somewhere else, rather than fix them (by refusing to drop a port, a
Re: gcc et amd64
Alexandre Pineau [EMAIL PROTECTED] wrote:
Salut,
Je maintiens le paquet ire et celui-ci ne se compile pas correctement sur
amd64 avec gcc 4.
J'ai appliqué le patch qui m'a été transmis, mais j'aimerai etre sur de mon
coup avant de
demander un upoad à mon sponsor.
Il y a t'il un moyen de compiler pour une archi x86-64 en utilisant une archi
x86 classique?
J'ai essayé d'imposer l'archi avec -march=k8, mais sans résultat. En cas,
pourriez vous
essayer de compiler ire 0.92 (unstable) sur une archi amd64 pour moi?
Le fichier dif ire_0.92-2.diff.gz est dispo sur
http://alexandre.pineau.free.fr/fichiers/ire_0.92/
Ca compile sans problème, par contre ça vautre immédiatement.
= 8 snip 8 =
--- ire-0.92.orig/src/ithelib/debug.c
+++ ire-0.92/src/ithelib/debug.c
@@ -98,6 +98,7 @@
{
FILE *blt;
va_list ap;
+va_list ap2;
if(ilog_logoff)
return;
@@ -106,16 +107,18 @@
ithe_panic(ilog_text() - Missing call to ilog_start,NULL);
va_start(ap, msg);
+va_copy(ap2, ap);
vprintf(msg,ap);
blt=fopen(bootlog,a);
if(!blt)
ithe_panic(Could not append to log file,bootlog);
-vfprintf(blt,msg,ap);
+vfprintf(blt,msg,ap2);
fclose(blt);
va_end(ap);
+va_end(ap2);
}
/*
= 8 snip 8 =
Ne JAMAIS utiliser une va_list 2 fois de suite. Ca ne marche pas. Sauf
sur cette archi pourrie qu'est i386. Partout ailleurs, c'est garanti
de ne pas marcher. (pour les détails, man va_list)
Il y a sûrement d'autres endroits où ce problème existe, je n'ai pas
tout vérifié.
JB.
--
Julien BLACHE - Debian GNU/Linux Developer - [EMAIL PROTECTED]
Public key available on http://www.jblache.org - KeyID: F5D6 5169
GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: pbuilder status update
On Sun, Aug 21, 2005 at 02:48:31PM +0900, Junichi Uekawa wrote: Hi, Same here. With two sponsors, I doubt you'll have much of a latency trouble with your uploads :-) I'm looking for someone to upload the following packages canna_3.7p3-2_i386.changes: translation updates d-shlibs_0.26_i386.changes: error checking fix gamix_1.99.p14.debian1-3_i386.changes: translation updates update-cluster_0.41.5-1_i386.changes: translation updates whizzytex_1.2.3-1_i386.changes: new upstream release wysihtml_0.12-1_i386.changes: new upstream release available: http://www.netfort.gr.jp/~dancer/tmp/20050821/ All done. regards, junichi -- Junichi Uekawa, Debian Developer http://www.netfort.gr.jp/~dancer/ 183A 70FC 4732 1B87 57A5 CE82 D837 7D4E E81E 55C1 Anibal Monsalve Salazar -- .''`. Debian GNU/Linux : :' : Free Operating System `. `' http://debian.org/ `- http://v7w.com/anibal signature.asc Description: Digital signature
Re: Bug#323227: new list: debian-planet to distribute planet.debian.org postings; archive to enable searching
* Christoph Berg | I'd like to have a debian-planet list that would receive blog postings | from planet.debian.org. | | The main reason is that after postings expire on the planet website, | it's very hard to find old postings if you cannot remember who wrote | it. Think of there was some nice sh script snippet or someone | pointed to that great package. Now you have to manually browse all | feeds or hope for google. Having a regular list archive on | lists.debian.org would solve this. I would like this not to happen. Having your feed syndicated on planet.debian does not mean you want all your postings to end up in a public mail archive somewhere. -- Tollef Fog Heen,''`. UNIX is user friendly, it's just picky about who its friends are : :' : `. `' `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: arch, svn, cvs
* Roberto C. Sanchez | OK. Then please just name two or three. I am geniunely interested. | I switched from CVS to subversion exclusively for my own use when | Sarge went stable. I still use CVS occasionally since some projects | to which I contribute use CVS (e.g., on sourceforge). I just stumbled across one issue: it doesn't handle the case where you change your encoding without checking out the repository again: : [EMAIL PROTECTED] ~/svn/trunk LANG=en_US.UTF-8 svn st svn: Valid UTF-8 data (hex: 46) followed by invalid UTF-8 sequence (hex: f8 72 73 74) : [EMAIL PROTECTED] ~/svn/trunk LANG=en_US svn st [snip list of changes] : [EMAIL PROTECTED] ~/svn/trunk (The repository was checked out in a latin1 locale and includes files with some of the norwegian letters æøå in their names.) Yeah, and there's another error if you use LANG=C: : [EMAIL PROTECTED] ~/svn/trunk LANG=C svn st svn: Can't convert string from native encoding to 'UTF-8': svn: F?\248rste informasjonsskriv.doc -- Tollef Fog Heen,''`. UNIX is user friendly, it's just picky about who its friends are : :' : `. `' `-
Re: Release-critical Bugreport for August 19, 2005
* Piotr Roszatycki | The WNPP messages was dropped. The RC report are the only messages generated | automatically and flooding debian-devel-announces list. I suggest using a bigger mailbox for your d-d-a subscription if one mail a week is considering «flooding». Even when said mail is 4500 lines long. -- Tollef Fog Heen,''`. UNIX is user friendly, it's just picky about who its friends are : :' : `. `' `-
Re: Bug#323855: ITP: opencvs -- OpenBSD CVS implementation with special emphasis in security
On 8/19/05, Steinar H. Gunderson [EMAIL PROTECTED] wrote: I'd love to see people migrating to Arch Being a long-time Arch user, let me tell you that Arch has been orphaned upstream. Currently baz is the only version being developed, and it's unclear for how long, as Canonical has their eyes on bzr and hct. Myself, I'm moving my projects quickly to git/cogito. It's proving to be fast, and better designed than Arch by a garden mile. Currently writing an Arch to GIT conversion. Now, for an on-topic comment: CVS is going to be part of the FOSS infrastructure for a long time to come. OpenCVS sounds like a very good thing to use if you have to support CVS. Opposing the ITP because you're using shinier toys is... rude. You package your shiny toys, and Luciano packages his toy. cheers, martin
Re: Release-critical Bugreport for August 19, 2005
On Sun, Aug 21, 2005 at 12:04:34PM +0200, Tollef Fog Heen wrote: I suggest using a bigger mailbox for your d-d-a subscription if one mail a week is considering «flooding». Even when said mail is 4500 lines long. One of the things with d-d-a is that it's not a list where you want to have people deleting the majority (or even a large proportion) of the messages posted unread since that's likely to colour the way people respond to the rest of the messags. -- You grabbed my hand and we fell into it, like a daydream - or a fever. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#323855: ITP: opencvs -- OpenBSD CVS implementation with special emphasis in security
On Sun, Aug 21, 2005 at 10:05:43PM +1200, Martin Langhoff wrote: On 8/19/05, Steinar H. Gunderson [EMAIL PROTECTED] wrote: I'd love to see people migrating to Arch Being a long-time Arch user, let me tell you that Arch has been orphaned upstream. Correction: tla, an Arch frontend, has been orphaned upstream. Most of the interesting development work for the past 6 months or so has been on baz, another Arch frontend. Saying Arch has been orphaned upstream because of Tom Lord's announcement is roughly similar to saying that Linux has been orphaned because the 2.0 kernel series is no longer maintained... and it's unclear for how long, as Canonical has their eyes on bzr and hct. I'm quite confident that there will be an upgrade path from Arch archives to bzr archives. Canonical, amongst other people, have too much invested in Arch to just let that history fester. As for hct, I understand it is a wrapper frontend to baz/bzr to provide the sorts of functionality that package maintainers need, instead of being a general-purpose revision control tool. - Matt signature.asc Description: Digital signature
ITP: python-utidylib -- Python wrapper for TidyLib
retitle 244110 ITP: python-utidylib -- Python wrapper for TidyLib owner 244110 [EMAIL PROTECTED] thanks Hi all, thanks for a quick response, I'm taking over this ITP. Here's the final package description (just for the record): Package name: python-utidylib Version : 0.2 Upstream Author : Cory Dodt [EMAIL PROTECTED] URL : http://utidylib.berlios.de/ License : MIT/X Description : Python wrapper for TidyLib uTidylib is a Python wrapper for TidyLib, a library from the HTML Tidy project. This allows you to tidy HTML files through a Pythonic interface. Cheers, Igor -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#323855: ITP: opencvs -- OpenBSD CVS implementation with special emphasis in security
On Sun, Aug 21, 2005 at 09:11:20PM +1000, Matthew Palmer wrote: On Sun, Aug 21, 2005 at 10:05:43PM +1200, Martin Langhoff wrote: On 8/19/05, Steinar H. Gunderson [EMAIL PROTECTED] wrote: I'd love to see people migrating to Arch Being a long-time Arch user, let me tell you that Arch has been orphaned upstream. Correction: tla, an Arch frontend, has been orphaned upstream. Most of the interesting development work for the past 6 months or so has been on baz, another Arch frontend. Saying Arch has been orphaned upstream because of Tom Lord's announcement is roughly similar to saying that Linux has been orphaned because the 2.0 kernel series is no longer maintained... Oh, thanks for the news, I didn't know that. [snip] Regards: David -- /) David Weinehall [EMAIL PROTECTED] /) Rime on my window (\ // ~ // Diamond-white roses of fire // \) http://www.acc.umu.se/~tao/(/ Beautiful hoar-frost (/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#323855: ITP: opencvs -- OpenBSD CVS implementation with special emphasis in security
also sprach Florian Weimer [EMAIL PROTECTED] [2005.08.21.0306 +0200]: Uhm, CVS implements RCS, but exposes a different interface. I don't think this is accurate. CVS uses RCS internally, but provides its own implementation in case $RCSBIN/$PATH don't contain the RCS binaries. It does not advertise to support RCS features at all, nor does it export any of the RCS functionality to the user. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP (sub)keys? Use subkeys.pgp.net as keyserver! Most Intelligent Customers Realise Our Software Only Fools Them. signature.asc Description: Digital signature (GPG/PGP)
Bug#324296: ITP: ldapscripts -- Add and remove user and groups stored (using ldap)
Package: wnpp Severity: wishlist Owner: Pierre Habouzit [EMAIL PROTECTED] * Package name: ldapscripts Version : 1.2 Upstream Author : Ganaël LAPLANCHE [EMAIL PROTECTED] * URL : http://contribs.martymac.com/ * License : GPL Description : Add and remove user and groups stored (using ldap) Ldapscripts are shell scripts that allow to manage POSIX accounts (users, groups, machines) on an LDAP directory. They are similar to smbldap-tools but are written in shellscript, not in PERL. They only require OpenLDAP client commands (ldapadd, ldapdelete, ldapsearch, ldapmodify, slappasswd) and make administrator's work a lot easier avoiding him to configure PERL and each library dependencies (e.g. Net::LDAP). These scripts are very simple to configure by not requiring any Samba-related information (SID, profiles, homes, ...) : management of Samba attributes is entirely done by standard commands (net, smbpasswd et pdbedit) used together with the scripts. Moreover, most of the configuration is guessed from the one of libpam-ldap, and everything should work out from the box for most users. The scripts may be used independently - within command lines - or automatically by Samba (like smbldap-tools), to handle POSIX information within accounts before adding Samba information.
Re: Bug#324296: ITP: ldapscripts -- Add and remove user and groups stored (using ldap)
owner 324296 [EMAIL PROTECTED] submitter 324296 [EMAIL PROTECTED] thanks damned, why don't reportbug honour DEBEMAIL ? -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpWXjItWB3Q1.pgp Description: PGP signature
Re: Bug#324296: ITP: ldapscripts -- Add and remove user and groups stored (using ldap)
Package: reportbug Version: 3.15 Severity: important Le Dim 21 Août 2005 17:02, Benjamin Seidenberg a écrit : Pierre Habouzit wrote: owner 324296 [EMAIL PROTECTED] submitter 324296 [EMAIL PROTECTED] thanks damned, why don't reportbug honour DEBEMAIL ? Had same issue, check your ~/.reportbugrc, it sets variables in that file when you first run it. DEBBUGEMAIL will override it (or you can just change the file). I had 2 people jump on me from debian-devel, even though I had already fixed it. :-) I consider it a bug, an important one even. Reportbug never asked me for any information except the experience level I had, so if it was able to guess my information once, it should *NOT* store it. Such an information can change, and the user won't know that static settings have been set, and when he changes EMAIL, he won't receive mails from the maintainers back. Reportbug should : * either get EMAIL/DEBEMAIL/DEBBUGSEMAIL/... each time it is run * or ask the user to give such information (and then store it, since the user *KNOW* reportbug asked it to him) This bug really is important because it can result in a permanent lost communication between a reporter and a package maintainer. btw, I've not checked the reportbug man page, if such a behaviour is documented or not, but even if it is, since no normal user would ever need to read this manpage, such a behaviour still remains hidden, and thus is IMHO a bug. So *even* adding a note about such a behaviour in the manpage (or elsewhere) is not sufficient. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpjA2rHEvL75.pgp Description: PGP signature
Re: Bug#323855: ITP: opencvs -- OpenBSD CVS implementation with special emphasis in security
On Sat, 2005-08-20 at 14:20 -0700, Thomas Bushnell BSG wrote: Javier Fernández-Sanguino Peña [EMAIL PROTECTED] writes: On Thu, Aug 18, 2005 at 07:31:38PM -0400, Roberto C. Sanchez wrote: most popular open source revision control software. And among the most horrible ones. Agreed. Why anyone would bother to reimplement an already existing free tool is beyond me. For several reasons, one being that the BSD folks use CVS extensively, it's part of how the ports system (and upgrades) work. How does their extensive use of it explain why they would reimplement it? Maybe they like the tool, but think it was implemented poorly? -- - Ron Johnson, Jr. Jefferson, LA USA PGP Key ID 8834C06B I prefer encrypted mail. In politics, being ridiculous is more damaging than being extreme. Roy Hattersley signature.asc Description: This is a digitally signed message part
Re: Results of the meeting in Helsinki about the Vancouver proposal
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 21-08-2005 03:58, Wouter Verhelst wrote: We also came to the conclusion that some of the requirements proposed in Vancouver would make sense as initial requirements -- requirements that a port would need to fulfill in order to be allowed on the mirror network -- but not necessarily as an 'overall' requirement -- a requirement that a port will always need to fulfill if it wants to be part of a stable release, even if it's already on the mirror network. Those would look like this: [snip] Overall: [snip] - binaries must have been built and signed by official Debian Developers Currently, sponsored packages are only signed, not built, by official Debian Developers. Is that intended to change, or is it a typo in the proposal? Please cc me, as I am not subscribed to d-devel. - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er nær: http://www.shibumi.org/eoti.htm -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDCLnWn7DbMsAkQLgRAseqAJ0ZueM27PSaFXodL8KOtg0MQp7tzACgpm16 KrJIgM9u/LeAdulAN6/YdS4= =eir/ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Results of the meeting in Helsinki about the Vancouver proposal
Jonas Smedegaard a écrit : Currently, sponsored packages are only signed, not built, by official Debian Developers. Is that intended to change, or is it a typo in the proposal? I don't know what is the rule but personnally, I never upload a package I haven't build, I rebuild all packages I sponsor. I hope others developers do the same. Bye, Aurelien -- .''`. Aurelien Jarno | GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Results of the meeting in Helsinki about the Vancouver proposal
On Sun, 2005-08-21 at 19:28 +0200, Jonas Smedegaard wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 21-08-2005 03:58, Wouter Verhelst wrote: We also came to the conclusion that some of the requirements proposed in Vancouver would make sense as initial requirements -- requirements that a port would need to fulfill in order to be allowed on the mirror network -- but not necessarily as an 'overall' requirement -- a requirement that a port will always need to fulfill if it wants to be part of a stable release, even if it's already on the mirror network. Those would look like this: [snip] Overall: [snip] - binaries must have been built and signed by official Debian Developers Currently, sponsored packages are only signed, not built, by official Debian Developers. Is that intended to change, or is it a typo in the proposal? I have always rebuilt (with pbuilder) packages I sponsor before uploading them. This has accidentally broken a sponsored package once due to a misconfiguration, but it's also caught missing build-deps, builds against testing, etc, a dozen times. -- Joe Wreschnig [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part
Re: Results of the meeting in Helsinki about the Vancouver proposal
Hi Jonas! You wrote: - binaries must have been built and signed by official Debian Developers Currently, sponsored packages are only signed, not built, by official Debian Developers. Sponsors do build the packages they sponsor themselves. Or at least, they should. -- Kind regards, ++ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++ signature.asc Description: Digital signature
Bug#324354: ITP: libpathan -- open source implementation of the W3C XPath 2 specification
Package: wnpp Severity: wishlist Owner: Tomas Fasth [EMAIL PROTECTED] * Package name: libpathan Version : 2.0beta Upstream Author : DecisionSoft Limited [EMAIL PROTECTED] * URL : http://software.decisionsoft.com/pathan2Info.html * License : BSD Description : Open source implementation of the W3C XPath 2 specification Pathan 2 is a code library implemented in C. It uses the Xerces-C DOM XML parser by the Apache Foundation and hence can be used in concert with Xerces-C to provide Path functionality in 3rd party software. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.10-co-0.6.2 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Results of the meeting in Helsinki about the Vancouver proposal
On Sun, Aug 21, 2005 at 07:28:55PM +0200, Jonas Smedegaard wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 21-08-2005 03:58, Wouter Verhelst wrote: We also came to the conclusion that some of the requirements proposed in Vancouver would make sense as initial requirements -- requirements that a port would need to fulfill in order to be allowed on the mirror network -- but not necessarily as an 'overall' requirement -- a requirement that a port will always need to fulfill if it wants to be part of a stable release, even if it's already on the mirror network. Those would look like this: [snip] Overall: [snip] - binaries must have been built and signed by official Debian Developers Currently, sponsored packages are only signed, not built, by official Debian Developers. I don't know about others, but I never sign and upload packages built by others; I always rebuild packages when I sponsor someone. I really hope others do the same. Regards: David Weinehall -- /) David Weinehall [EMAIL PROTECTED] /) Rime on my window (\ // ~ // Diamond-white roses of fire // \) http://www.acc.umu.se/~tao/(/ Beautiful hoar-frost (/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Results of the meeting in Helsinki about the Vancouver proposal
On Sun, 21 Aug 2005, Jonas Smedegaard wrote: Currently, sponsored packages are only signed, not built, by official Debian Developers. They are supposed to be BUILT by the sponsor of non-DDs, not just signed. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Results of the meeting in Helsinki about the Vancouver proposal
On Sun, Aug 21, 2005 at 07:28:55PM +0200, Jonas Smedegaard wrote: Currently, sponsored packages are only signed, not built, by official Debian Developers. Ahem, no! As the sponsor, you should rebuild the package from source using the diff from the packager, and using the upstream sources, not the sources provided by the packager. See this page: http://www.debian.org/doc/developers-reference/ch-beyond-pkging.en.html#s-sponsoring Richard -- __ _ |_) /| Richard Atterer | GnuPG key: | \/¯| http://atterer.net | 0x888354F7 ¯ '` ¯ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Be sure you pack your bags yourself (was: Results of the meeting...)
On Sun, Aug 21, 2005 at 07:28:55PM +0200, Jonas Smedegaard wrote: Currently, sponsored packages are only signed, not built, by official Debian Developers. Be sure you pack your bags yourself. Keep your bags under your control at all times. Never carry a package with unknown contents for any reason. I hope, that no DD ever signs a package, unless created by a DD and already signed by them. Cheers, WB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Results of the meeting in Helsinki about the Vancouver proposal
On Sun, 21 Aug 2005 19:28:55 +0200, Jonas Smedegaard [EMAIL PROTECTED] said: Currently, sponsored packages are only signed, not built, by official Debian Developers. Can you share with us the list of developers merely signing sponsored packages, so action can be taken? Is that intended to change, or is it a typo in the proposal? It is a bug in any such maintainers. manoj -- Beer -- it's not just for breakfast anymore. Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/%7Esrivasta/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Sponsoring procedures
Scripsit Richard Atterer [EMAIL PROTECTED] As the sponsor, you should rebuild the package from source using the diff from the packager, and using the upstream sources, not the sources provided by the packager. See this page: http://www.debian.org/doc/developers-reference/ch-beyond-pkging.en.html#s-sponsoring I think that section may be phrased a little too harshly. It seems to be based on an assumption that a sponsoree is necessarily less trustworthy than a random upstream author. It is of course true that as part of the normal quality check one does as part of a sponsored upload, one should check that the .orig.tar.gz does not contain spurious changes. But the idea that a sponsor should expect only a .diff.gz from the sponsoree is unsound - you would be less sure that the upstream source you use is the same as the one the sponsoree created his diff against. Ideally a sponsoree should be produce a full Debian source package. The sponsor checks it (including a sanity check of the .orig.tar.gz in case of a new upstream version), removes the sponsoree's signature on the .dsc and adds his own, builds a binary package, and uploads. In practice it is acceptable for the sponsor to recompute the .diff.gz and .dsc using dpkg-buildpackage (which in any case ought to produce identical files). But I think the sponsoree should provide a .dsc nevertheless, if only to document the checksum of the .orig.tar.gz he used for packaging. -- Henning MakholmWhat a hideous colour khaki is. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
vancouver revisited
Hi, Some comments : Initial: - must be publically available to buy new Trivially true for any architecture, even VAX. - must be freely usable (without NDA) - must be able to run a buildd 24/7 without crashing - must have an actual, working buildd - must include basic UNIX functionality Whatever that may mean - 5 developers must send in a signed request for the addition - must demonstrate to have at least 50 users - must be able to keep up with unstable with 2 buildd machines, and must have one redundant buildd machine Bogus requirement. At the moment we have less then 1 s390 buildd for example. Overall: - must have successfully compiled 98% of the archive's source (excluding arch-specific packages) Useless requirement. Less then 98% of the archive may be useful for the architecture and it cannot be the porters problem that packages violate language rules and therefore fail to compile or work on some arch. - must have a working, tested installer Trivial. debootstrap does that. - security team, DSA, and release team must not veto inclusion Arbitrary veto power. This requirement is unacceptable for me. Noone should be allowed to just ignore other peoples work within the project. Cheers, Peter (p2). signature.asc Description: Digital signature
Re: Results of the meeting in Helsinki about the Vancouver proposal
On Sun, 2005-08-21 at 19:55 +0200, Aurelien Jarno wrote: Jonas Smedegaard a écrit : Currently, sponsored packages are only signed, not built, by official Debian Developers. Is that intended to change, or is it a typo in the proposal? I don't know what is the rule but personnally, I never upload a package I haven't build, I rebuild all packages I sponsor. I hope others developers do the same. I do rebuild them and more on this that I download the .orig.tar.gz for myself from the official upstream location and check the diff ofcourse. This may sound paranoid, but this is me. Regards, Laszlo/GCS -- BorsodChem Joint-Stock Company www.debian.org Linux Support Center Software engineerDebian Developer Developer +36-48-511211/23-85 +36-20-4441745 signature.asc Description: This is a digitally signed message part
Re: vancouver revisited
Hi, * Peter 'p2' De Schrijver ([EMAIL PROTECTED]) [050821 22:39]: Some comments : - must include basic UNIX functionality Whatever that may mean there are processes. there is dns name resolution. there is networking. there is chroot. etc. Just really basic things (and, of course, none of the ports currently in testing fails this). - 5 developers must send in a signed request for the addition - must demonstrate to have at least 50 users - must be able to keep up with unstable with 2 buildd machines, and must have one redundant buildd machine Bogus requirement. At the moment we have less then 1 s390 buildd for example. machine translates with partition btw - though the two different partitions should be in different physical locations, for obvious reasons. Yes, we want a redundancy for good reasons. Overall: - must have successfully compiled 98% of the archive's source (excluding arch-specific packages) Useless requirement. Less then 98% of the archive may be useful for the architecture (excluding arch-specific packages) that's there for a reason and it cannot be the porters problem that packages violate language rules and therefore fail to compile or work on some arch. well, if the package is bogus from the language usage, than that's not the porters problem (but how often did that hit exactly one arch?). If the arch can't e.g. use C++-packages because it doesn't have the toolchain for c++, I think that is the porters problem (just to give an possible example). - must have a working, tested installer Trivial. debootstrap does that. How do you boot the system to run debootstrap? (Note: the answer gentoo or Windows is not what I want to hear :) It is agreed that this isn't a too high barrier, but - well, we should still require it. If no (potential) port has an issue with that, it's even better. - security team, DSA, and release team must not veto inclusion Arbitrary veto power. This requirement is unacceptable for me. Noone should be allowed to just ignore other peoples work within the project. Please read Wouter's explanation. There was really very much discussion on exactly this. Cheers, Andi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Be sure you pack your bags yourself (was: Results of the meeting...)
On Sun, 2005-08-21 at 19:44 +, W. Borgert wrote: I hope, that no DD ever signs a package, unless created by a DD and already signed by them. There would be no reason to do it. If one of us already signed, then it is valid; if there are two (or maybe more) sign on a package, then it can not be accepted for uploading, believe me, once happened with me and katie rejected it immediately. Cheers, Laszlo/GCS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: vancouver revisited
Hi, Bogus requirement. At the moment we have less then 1 s390 buildd for example. machine translates with partition btw - though the two different partitions should be in different physical locations, for obvious reasons. Yes, we want a redundancy for good reasons. Which is very arbitrary to me, machine to me means physical box with hardware and software doing stuff. So this requirement is very much arbitrary and without any reasonable foundation. Overall: - must have successfully compiled 98% of the archive's source (excluding arch-specific packages) Useless requirement. Less then 98% of the archive may be useful for the architecture (excluding arch-specific packages) that's there for a reason Except that arch-specific package has always meant 'contains arch specific code', not 'does not make sense to run on this arch'. So this clause doesn't cover all cases. and it cannot be the porters problem that packages violate language rules and therefore fail to compile or work on some arch. well, if the package is bogus from the language usage, than that's not the porters problem (but how often did that hit exactly one arch?). If the arch can't e.g. use C++-packages because it doesn't have the toolchain for c++, I think that is the porters problem (just to give an possible example). I have seen multiple examples of builds failing because the testsuite or a buildtime generated tool crashed on a specific arch due to bad coding practices. - must have a working, tested installer Trivial. debootstrap does that. How do you boot the system to run debootstrap? (Note: the answer gentoo or Windows is not what I want to hear :) It is agreed that this isn't a too high barrier, but - well, we should still require it. If no (potential) port has an issue with that, it's even better. You boot from an existing rootfs image, just like you boot from your existing install media. - security team, DSA, and release team must not veto inclusion Arbitrary veto power. This requirement is unacceptable for me. Noone should be allowed to just ignore other peoples work within the project. Please read Wouter's explanation. There was really very much discussion on exactly this. I did. And I still consider it unacceptable. I see no reason for having this sort of far reaching veto powers. Cheers, Peter (p2). signature.asc Description: Digital signature
Team have veto rights, because they can just refuse the work anyway? (Was: Results of the meeting in Helsinki about the Vancouver proposal)
[Wouter Verhelst] b) the three beforementioned teams could already refuse to support a port anyhow, simply by not doing the work. This is not really a valid argument. If a team in debian refuses to accept decisions made by a majority of debian developers, or rejects democratic control, this team will just have to be replaced by the DPL. The fact that some team in debian are able to refuse democratic control in the short term do not mean that their refusal should be accepted, nor be allowed to block the will of the majority of the project. No-one in Debian are irreplacable, so I am sure we can find good people to take over if such team should ever appear in debian. I trust us all to behave with reason, so we never end up in a situation where we need to test such hostile replacement. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: vancouver revisited
On Sun, Aug 21, 2005 at 10:54:43PM +0200, Andreas Barth wrote: * Peter 'p2' De Schrijver ([EMAIL PROTECTED]) [050821 22:39]: - must have a working, tested installer Trivial. debootstrap does that. How do you boot the system to run debootstrap? (Note: the answer gentoo or Windows is not what I want to hear :) It is agreed that this isn't a too high barrier, but - well, we should still require it. If no (potential) port has an issue with that, it's even better. How do you boot to a system to run debian-installer when there is no bios or bootloader on the system yet? Should debian-installer support installing via JTAG? What happens on many embedded systems, debianish system is debootstrapped on a different machine and put into jffs2 image, which is then flashed to a pile of devices. Walking through d-i every time would be very clumsy, so there is no use for a working installer for those systems. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Results of the meeting in Helsinki about the Vancouver proposal
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 21-08-2005 21:42, Manoj Srivastava wrote: On Sun, 21 Aug 2005 19:28:55 +0200, Jonas Smedegaard [EMAIL PROTECTED] said: Currently, sponsored packages are only signed, not built, by official Debian Developers. Can you share with us the list of developers merely signing sponsored packages, so action can be taken? Is that intended to change, or is it a typo in the proposal? It is a bug in any such maintainers. Thanks to all of you who commented (similarly) to this. I must say that I favor your way of putting it, Manoj. You have a great sense of words :-) - Jonas Who does not sponsor packages but help new maintainers in other ways. P.S. Please cc me if responding to this: I am not subscribed to d-devel. - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er nær: http://www.shibumi.org/eoti.htm -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDCPgdn7DbMsAkQLgRAg8QAJ4n/evuckM+LUEamuV6jUhb0zrf5gCfZR+0 B6PVKECPd9IQlI7GcRO14hg= =+OfD -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Be sure you pack your bags yourself
Scripsit Laszlo Boszormenyi [EMAIL PROTECTED] On Sun, 2005-08-21 at 19:44 +, W. Borgert wrote: I hope, that no DD ever signs a package, unless created by a DD and already signed by them. There would be no reason to do it. If one of us already signed, then it is valid; It may be signed with a key on db.debian.org and still not be accepted by ftp-master because the latter's keyring is only updated by hand. -- Henning Makholm Punctuation, is? fun! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: version numbering
On Fri, 2005-08-19 at 00:52 +0200, martin f krafft wrote: also sprach Lars Bahner [EMAIL PROTECTED] [2005.08.18.2346 +0200]: Please CC: me as I am not on this list! Please consider setting Mail-Followup-To accordingly. Upstream names the betas for 0.7.3.3 as 0.7.3.3.b1-b30 - as you no doubt already guessed. This is why we now have the ~ operator. So now that there is no beta-versioning, the installer sees this as a lower number. I could of cource number the package as 0.7.3.3.c or 0.7.3.3.final, but I was wondering what The Right Thing To Do would be. I think you have to resort to an epoch. Using 0.7.3.3.final seems okay to me too. I don't think there is a Right Way. I think the ~ is the Right Way. 0.7.3.3~b1 0.7.3.3~b30 0.7.3.3 Cheers, Rob -- GPG key available at: http://www.robertcollins.net/keys.txt. signature.asc Description: This is a digitally signed message part
[PATCH] Simple parallellized boot sequence (and a plea for LSB complience)
Recently, I have been investigating how to speed up the boot process in Debian, and during this work, I found a simple way to change /etc/init.d/rc to run all init.d scripts with the same sequence number in parallell. Patch included below. For this change to work as it should, we need to make sure init.d-scripts are ordered according to dependency, so scripts needed by other scripts get a earlier sequence number. And to make it possible to generate such ordering, we need to know the dependencies of a given init.d script. The simple and standard-complient way to make these assumtions come true is to insert LSB 2.1 compilent init.d headers in all our init.d scripts. They are documented in URL:http://refspecs.freestandards.org/LSB_2.1.0/LSB-generic/LSB-generic/initscrcomconv.html and look like this: ### BEGIN INIT INFO # Provides: boot_facility_1 [ boot_facility_2 ...] # Required-Start: boot_facility_1 [ boot_facility_2 ...] # Required-Stop: boot_facility_1 [ boot_facility_2 ...] # Should-Start: boot_facility_1 [ boot_facility_2 ...] # Should-Stop: boot_facility_1 [ boot_facility_2 ...] # Default-Start: run_level_1 [ run_level_2 ...] # Default-Stop: run_level_1 [ run_level_2 ...] # Short-Description: short_description # Description: multiline_description ### END INIT INFO The important headers here are provides, required-* and should-*. Please add LSB compilant headers into your init.d scripts. If these headers are present in all init.d scripts, it is possible to make sure the order of init.d scripts fulfill the requiremets. There is even a tool available to do this for us. I found insserv in suse, and patched it to do what I wanted for the SysV rc#.d directories. Package available from URL:http://developer.skolelinux.no/~pere/debian/insserv_1.00.8-0.0.pere.1_i386.deb. During my investigation, I came across an old paper on the boot system in debian, which contain lots of useful info. Check out URL:http://alioth.debian.org/docman/view.php/30730/38/debconf2-initscripts-bkg.pdf. I promised you a patch. Here it is, without the indentation change (diff -uw) to make it easier to see the real change in the script. Any comments on this approach? I had a look at initng, but it does not seem to use the LSB headers, and I would rather keep using the normal init.d scripts instead of duplicating the code for initng. --- /etc/init.d/rc 2004-09-10 17:00:48.0 +0200 +++ /tmp/rc-parallell 2005-08-22 00:52:34.0 +0200 @@ -59,17 +59,35 @@ # First, run the KILL scripts. if [ $previous != N ] then - for i in /etc/rc$runlevel.d/K[0-9][0-9]* + # Run all scripts with the same level in parallell + for level in `ls /etc/rc$runlevel.d | \ + grep '^K[0-9][0-9]' | \ + cut -c2,3 | sort -u` ; do + pids= + for i in /etc/rc$runlevel.d/K$level* do # Check if the script is there. [ ! -f $i ] continue # Stop the service. - startup $i stop + startup $i stop + pids=$pids $! + done + # Wait for all pids. Does not matter which + # pid return first, as we need to wait for all + # of them + for pid in $pids ; do + wait $pid + done done fi # Now run the START scripts for this runlevel. - for i in /etc/rc$runlevel.d/S* + + # Run all scripts with the same level in parallell + for level in `ls /etc/rc$runlevel.d | grep '^S[0-9][0-9]' | \ + cut -c2,3 | sort -u` ; do + pids= + for i in /etc/rc$runlevel.d/S$level* do [ ! -f $i ] continue @@ -91,12 +109,20 @@ fi case $runlevel in 0|6) - startup $i stop + startup $i stop ;; *) - startup $i start + startup $i start ;; esac + pids=$pids $! + done + # Wait for all pids. Does not matter which + # pid return first, as we need to wait for all + # of them + for pid in $pids ; do + wait $pid + done done fi # eof /etc/init.d/rc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [PATCH] Simple parallellized boot sequence (and a plea for LSB complience)
also sprach Petter Reinholdtsen [EMAIL PROTECTED] [2005.08.22.0113 +0200]: Any comments on this approach? The place to discuss issues like this would be the initscripts-ng project on alioth. There's a mailing list... -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP (sub)keys? Use subkeys.pgp.net as keyserver! a woman is like your shadow; follow her, she flies; fly from her, she follows. -- sébastien-roch-nicolas chamfort signature.asc Description: Digital signature (GPG/PGP)
Re: version numbering
Robert Collins wrote: martin f krafft wrote: Lars Bahner wrote: Please CC: me as I am not on this list! Upstream names the betas for 0.7.3.3 as 0.7.3.3.b1-b30 - as you no doubt already guessed. ... So now that there is no beta-versioning, the installer sees this as a lower number. I could of cource number the package as 0.7.3.3.c or 0.7.3.3.final, but I was wondering what The Right Thing To Do would be. I think you have to resort to an epoch. Using 0.7.3.3.final seems okay to me too. I don't think there is a Right Way. I think the ~ is the Right Way. 0.7.3.3~b1 0.7.3.3~b30 0.7.3.3 It is too late for that. After the package has already been uploaded as 0.7.3.3.b1-b30 it is too late to rename it using a ~. That is only useful as learning for the future when uploading new beta packages. But now that 0.7.3.3.b1-b30 already exists the question was how to deal with the released version. I think 0.7.3.3.final or 0.7.3.3.released some such is best. Avoid using an epoc unless there is no other choice. After 0.7.3.4 is released this ugly version string will disappear into the archive of history. But an epoc would remain forever into the future and there would never be an escape outside of renaming the package. An example where an epoc would be needed would be if 0.7.3.3 was uploaded as 7.3.3 instead. The epoc is designed to handle this problem and allows 1:0.7.3.3 to be later than 7.3.3 to fix that situation. But that is not the case here and the epoc can be avoided. Bob signature.asc Description: Digital signature
how to fully replace another package
The (still not uploaded) coldplug package conflicts+depends+provides hotplug. The issue is that since all the important parts of hotplug are conffiles they are not deleted when the package is removed, and this is bad (as in the system will probably not boot bad). Does a way to force purging the package exist? Is there anything else I can do, other than deleting the files in the hotplug postinst? -- ciao, Marco signature.asc Description: Digital signature
Re: [PATCH] Simple parallellized boot sequence (and a plea for LSB complience)
On Aug 22, Petter Reinholdtsen [EMAIL PROTECTED] wrote: in parallell. Patch included below. For this change to work as it should, we need to make sure init.d-scripts are ordered according to dependency, so scripts needed by other scripts get a earlier sequence number. And to make it possible to generate such ordering, we need to know the dependencies of a given init.d script. I'm sure that a fair number of critical scripts (e.g. some dealing with networking) are not. (No, I do not remember which ones right now.) -- ciao, Marco signature.asc Description: Digital signature
Re: Team have veto rights, because they can just refuse the work anyway? (Was: Results of the meeting in Helsinki about the Vancouver proposal)
On Sun, Aug 21, 2005 at 11:29:51PM +0200, Petter Reinholdtsen wrote: [Wouter Verhelst] b) the three beforementioned teams could already refuse to support a port anyhow, simply by not doing the work. This is not really a valid argument. If a team in debian refuses to accept decisions made by a majority of debian developers, or rejects democratic control, this team will just have to be replaced by the DPL. It's a perfectly sensible thing to say here: from a purely practical point of view this *could* happen and all the proposal says here is that that isn't really on. Instead it says that people need to tell people why they don't want something to go ahead - discuss things rather than passively blocking them. That seems like a good starting point for dealing with the conflicts that are likely to occur if this happens both here and in other areas. -- You grabbed my hand and we fell into it, like a daydream - or a fever. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: version numbering
also sprach Robert Collins [EMAIL PROTECTED] [2005.08.22.0053 +0200]: I think the ~ is the Right Way. 0.7.3.3~b1 0.7.3.3~b30 0.7.3.3 This will not yet work with the Debian archive scripts. It will be the right way, but not yet. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP (sub)keys? Use subkeys.pgp.net as keyserver! 'this must be a thursday,' said arthur to himself, sinking low over his beer. 'i never could get the hang of thursdays.' -- hitchhiker's guide to the galaxy signature.asc Description: Digital signature (GPG/PGP)
Re: vancouver revisited
On Sun, Aug 21, 2005 at 11:24:48PM +0200, Peter 'p2' De Schrijver wrote: well, if the package is bogus from the language usage, than that's not the porters problem (but how often did that hit exactly one arch?). If I have seen multiple examples of builds failing because the testsuite or a buildtime generated tool crashed on a specific arch due to bad coding practices. That sounds like perfectly normal porting issues that ought to get fed back to the maintainer as they would for any other arch. Why on earth would that be a problem? -- You grabbed my hand and we fell into it, like a daydream - or a fever. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Team have veto rights, because they can just refuse the work anyway? (Was: Results of the meeting in Helsinki about the Vancouver proposal)
On Sun, Aug 21, 2005 at 11:29:51PM +0200, Petter Reinholdtsen wrote: [Wouter Verhelst] b) the three beforementioned teams could already refuse to support a port anyhow, simply by not doing the work. This is not really a valid argument. If a team in debian refuses to accept decisions made by a majority of debian developers, or rejects democratic control, this team will just have to be replaced by the DPL. I think the reality of this situation is that a team would refuse to do the work due to valid reasons. The easy ones I can imagine are the ones we've heard already, such as We don't have the people to do this or We don't have enough time. Simply replacing teams in this sort of case would be foolhearty, as all that is really required is someone to come along and do the work, at which point they join the team and are responsible for what they've taken on. If the teams themselves can't or won't do the work for good reasons and no one else is willing to do it as well, then the DPL can't force people to do the work. - David Nusinow -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Results of the meeting in Helsinki about the Vancouver proposal
Jonas Smedegaard [EMAIL PROTECTED] writes: - binaries must have been built and signed by official Debian Developers Currently, sponsored packages are only signed, not built, by official Debian Developers. I always build the packages before sponsor it since I usually check against trivial mistakes and every time I skiped this I experienced bad results. Now I don't upload packages without double check it. -- O T A V I OS A L V A D O R - E-mail: [EMAIL PROTECTED] UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://www.freedom.ind.br/otavio - Microsoft gives you Windows ... Linux gives you the whole house. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: version numbering
On Sun, Aug 21, 2005 at 05:31:34PM -0600, Bob Proulx wrote: An example where an epoc would be needed would be if 0.7.3.3 was uploaded as 7.3.3 instead. The epoc is designed to handle this problem and allows 1:0.7.3.3 to be later than 7.3.3 to fix that situation. But that is not the case here and the epoc can be avoided. Really, what's so bad about an epoch? It works. It's invented to fix SNAFU's like this one. Personally, I _very_ much prefer a clean epoch over a silly version number such as 1.3.8.2.1.really.1.3.8.0.1.though.I.mean.something.else-1 -- The amount of time between slipping on the peel and landing on the pavement is precisely one bananosecond -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#324179: ITP: quake3 -- a famous first person shooter by ID-Software
On Sun, Aug 21, 2005 at 02:42:18PM +1000, Paul TBBle Hampson wrote: But we've know about it for a week. That's plenty of time to register a source-forge project, knock up a coming-soon webpage, install a piece of webforum software and a blog, and maybe a wiki, produce a list of things that'd be cool to fix or add if ID hadn't been so lazy and a short treatise on why this port is better than the other two. (A commercial port would send the t-shirts to the printers here. ^_^) Gosh, a forum (yucks!), a blog and a wiki... there was a time, not so long ago, when a mailing list and some sort of repository for the source code was everything a group of programmers needed to get on hacking... /me waits for the compulsory both ways! uphill! remark... SCNR, Marcelo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [PATCH] Simple parallellized boot sequence (and a plea for LSB complience)
On Mon, Aug 22, 2005 at 01:13:08AM +0200, Petter Reinholdtsen wrote: +for pid in $pids ; do +wait $pid +done Isn't just: wait enough? -- Marcelo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#323855: ITP: opencvs -- OpenBSD CVS implementation with special emphasis in security
On Saturday 20 August 2005 02:20 pm, Thomas Bushnell BSG wrote: How does their extensive use of it explain why they would reimplement it? Is there anyone who's used CVS extensively and HASN'T thought about reimplementing it? Daniel -- /--- Daniel Burrows [EMAIL PROTECTED] --\ | DROP THE SCYTHE AND TURN AROUND SLOWLY. | |-- Terry Pratchett, Reaper Man | \ The Turtle Moves! -- http://www.lspace.org ---/ pgpzg6gR5lrKo.pgp Description: PGP signature
version numbering
On Aug 18, Lars Bahner ([EMAIL PROTECTED]) wrote: Hi, Please CC: me as I am not on this list! As I upgraded rscheme today to the final non-beta version I ran into problems with the version numbering. Eg: old version (0.7.3.3.b30-1) in unstable = new version (0.7.3.3-1) Upstream names the betas for 0.7.3.3 as 0.7.3.3.b1-b30 - as you no doubt already guessed. So now that there is no beta-versioning, the installer sees this as a lower number. I could of cource number the package as 0.7.3.3.c or 0.7.3.3.final, but I was wondering what The Right Thing To Do would be. In the future, if you modify upstream's name of 0.7.3.4.b1 to be 0.7.3.4b1 instead, then 0.7.3.4.0 will be treated as a later version. I think that is pretty clean, and no need to wait for the ~ capability. -- Neil Roeth -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Mindterm
On Sun, Aug 21, 2005 at 12:18:29AM -0400, Benjamin Seidenberg wrote: Many internet cafe's or kiosk computers (or school computers, *sigh* though they're a lot better than they used to be) prevent running executables from outside specific paths, and limit write access to those paths. Also, I've seen lots of kiosks that keep a browser in full screen mode, preventing access to anything other than the web. A java applet is the only viable solution in cases like these. I've hacked a lot of those kiosks to run putty on them. It's really, really hard to stop people from running arbitrary code on windows. Most people can't even do it to people who *don't* have terminal access. Not that mindterm isn't still useful. -- .''`. ** Debian GNU/Linux ** | Andrew Suffield : :' : http://www.debian.org/ | `. `' | `- -- | signature.asc Description: Digital signature
Re: Bug#323855: ITP: opencvs -- OpenBSD CVS implementation with special emphasis in security
On Sun, Aug 21, 2005 at 07:01:37PM -0700, Daniel Burrows wrote: On Saturday 20 August 2005 02:20 pm, Thomas Bushnell BSG wrote: How does their extensive use of it explain why they would reimplement it? Is there anyone who's used CVS extensively and HASN'T thought about reimplementing it? Judging by the number of revision control systems springing up out there, I'd say the answer to that question is No, and furthermore most of them have gone further than just thinking about it. OpenCVS is one of the few to not think and I can make it Suck Less, to boot. - Matt signature.asc Description: Digital signature
Bug#324422: ITP: quaneko -- An index tool of TXT, PDF, DOC, HTML and others
Package: wnpp Severity: wishlist Owner: LI Daobing [EMAIL PROTECTED] * Package name: quaneko Version : 1.0.0 Upstream Author : Thomas Jund, Andrew Mustun and Laurent Cohn * URL : http://quaneko.sourceforge.net/ * License : GPL Description : An index tool of TXT, PDF, DOC, HTML and others Quaneko is a tool that allows you to quickly search for keywords in the files and directories on the local hard disk. It creates indexes over the words in those files. For you, this means that a typical search query will only take seconds. . quaneko can not only search for words in plain text files but also in various other file formats, depending on its configuration (e.g. Word doc, pdf, html, xml,...) -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-686-smp Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: arch, svn, cvs
[Tollef Fog Heen] I just stumbled across one issue: it doesn't handle the case where you change your encoding without checking out the repository again: : [EMAIL PROTECTED] ~/svn/trunk LANG=en_US.UTF-8 svn st svn: Valid UTF-8 data (hex: 46) followed by invalid UTF-8 sequence (hex: f8 72 73 74) That's a design decision - to recode filenames to a user's locale. This enables users with different locales to all see the same filenames in their local checkouts. You can argue that it's good or bad, but the alternative is *not* to recode them, and that causes exactly the same problem, when users of the same repository use different locales. So when local filenames are in the wrong locale (for whatever reason), what *should* the software do? Or, another point: most software does not keep an internal database of the encoding used for its data filenames. Do you think subversion should? Yeah, and there's another error if you use LANG=C: : [EMAIL PROTECTED] ~/svn/trunk LANG=C svn st svn: Can't convert string from native encoding to 'UTF-8': svn: F?\248rste informasjonsskriv.doc Given the decision to store filenames in UTF-8 in the repository, I don't know what else svn could possibly do here. The filename in question is, after all, invalid in the C locale. Peter signature.asc Description: Digital signature
Re: Sponsoring procedures
On Sun, 21 Aug 2005, Henning Makholm wrote: In practice it is acceptable for the sponsor to recompute the .diff.gz and .dsc using dpkg-buildpackage (which in any case ought to produce identical files). But I think the sponsoree should provide a .dsc nevertheless, if only to document the checksum of the .orig.tar.gz he used for packaging. This won't produce identical files; timestamps will change. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: vancouver revisited
[Andreas Barth] machine translates with partition btw - though the two different partitions should be in different physical locations, for obvious reasons. Yes, we want a redundancy for good reasons. [p2] Which is very arbitrary to me, machine to me means physical box with hardware and software doing stuff. So this requirement is very much arbitrary and without any reasonable foundation. I don't think anyone ever said an official buildd cannot be used for any other purpose. The s390 box is used as a buildd, but is also used for other things - I don't see the problem. Of course, it's probably a bad idea to give out random shell access to the buildd's OS instance. The reasonable foundation for having a redundant buildd in a separate physical location is, I think, well-established. Any random facility can lose power, perform big router upgrades, burn down, etc. Debian machines also seem to be prone to bad RAM, bad power supplies, bad disk arrays, and the like, and these things can't always be fixed within a tight time window. Except that arch-specific package has always meant 'contains arch specific code', not 'does not make sense to run on this arch'. So this clause doesn't cover all cases. Packages can be confined to specific architectures even in cases where they're written portably. For example, I just looked at the isapnptools source and I don't see anything particularly non-portable in it. (It does require a concept of iopl().) But it's still useless on platforms that don't have ISA busses, so it claims Architecture: alpha amd64 arm i386. And I don't remembering seeing anyone wanting to change this, even before isapnptools was removed from unstable. Peter signature.asc Description: Digital signature
Re: arch, svn, cvs
On Sat, 2005-08-20 at 21:00 +0200, Florian Weimer wrote: Greg Hudson contributes an interesting viewpoint: http://web.mit.edu/ghudson/thoughts/bitkeeper.whynot Well written, but does it contribute to our discussion here? Arch and Baz can both be used centrally, and with a group of committers. It might not scale as well right now, but efforts in the direction of automated patch integration systems promise to close this gap. See for instance the patch queue manager project[0]. 0. http://web.verbum.org/arch-pqm/ arch-pqm still requires that people publish their own repositories. This is often a challenge for people behind firewalls. pqm supports mailing a unified diff straight into the repository. I.e. echo -e patch\\n$(baz diff) | mail -s 'fix foo-bar' [EMAIL PROTECTED] If arch-pqm took advantage of the GNU arch capabilities and accepted signed changesets instead of merge requests, things would be quite different. Such an option exists for darcs, but I haven't used it. It still doesn't provide the satisfaction of immediate feedback, I fear. I haven't implemented a changeset based option, it would be quite easy if someone wants to do it. Cheers, Rob -- GPG key available at: http://www.robertcollins.net/keys.txt. signature.asc Description: This is a digitally signed message part
Re: Bug#323855: ITP: opencvs -- OpenBSD CVS implementation withspecial emphasis in security
Thomas Bushnell BSG dijo [Sat, Aug 20, 2005 at 02:20:45PM -0700]: For several reasons, one being that the BSD folks use CVS extensively, it's part of how the ports system (and upgrades) work. How does their extensive use of it explain why they would reimplement it? The OBSD crowd have reimplemented many important subsystems because they do not consider GPL-like licenses to be free enough. Yes, also because of technical reasons, but in this case it seems to be about (their version of) freedom. Greetings, -- Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)1451-2244 / 5623-0154 PGP key 1024D/8BB527AF 2001-10-23 Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted qalculate-gtk 0.8.1-4 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 20 Aug 2005 19:47:10 +0200 Source: qalculate-gtk Binary: qalculate qalculate-gtk Architecture: source i386 all Version: 0.8.1-4 Distribution: unstable Urgency: low Maintainer: Martin Waitz [EMAIL PROTECTED] Changed-By: Martin Waitz [EMAIL PROTECTED] Description: qalculate - Powerful and easy to use desktop calculator - transitional qalculate-gtk - Powerful and easy to use desktop calculator - GTK version Closes: 323119 Changes: qalculate-gtk (0.8.1-4) unstable; urgency=low . * Build-Depend on libgmp3-dev (this finally closes: #323119 hopefully) Files: 0b6cc19a1fe796e419454086385dc711 743 math optional qalculate-gtk_0.8.1-4.dsc e2b8f4f6d498c92d5c0299cf69061fe4 3654 math optional qalculate-gtk_0.8.1-4.diff.gz 8ddb9eea41523ee648940b219aec0d27 23294 math optional qalculate_0.8.1-4_all.deb 25a7162d3206554bdb0c93f3ba758510 985820 math optional qalculate-gtk_0.8.1-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDCBXVj/Eaxd/oD7IRAu0cAJ9LaGa6qzmix8XA47PgoW/EA8BDmQCfR2W7 wtukObcR8GnTt5kPpeK3YmI= =AegJ -END PGP SIGNATURE- Accepted: qalculate-gtk_0.8.1-4.diff.gz to pool/main/q/qalculate-gtk/qalculate-gtk_0.8.1-4.diff.gz qalculate-gtk_0.8.1-4.dsc to pool/main/q/qalculate-gtk/qalculate-gtk_0.8.1-4.dsc qalculate-gtk_0.8.1-4_i386.deb to pool/main/q/qalculate-gtk/qalculate-gtk_0.8.1-4_i386.deb qalculate_0.8.1-4_all.deb to pool/main/q/qalculate-gtk/qalculate_0.8.1-4_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted tuxeyes 0.0.3-8 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 21 Aug 2005 08:20:22 +0200 Source: tuxeyes Binary: tuxeyes Architecture: source i386 Version: 0.0.3-8 Distribution: unstable Urgency: low Maintainer: Laszlo Boszormenyi (GCS) [EMAIL PROTECTED] Changed-By: Laszlo Boszormenyi (GCS) [EMAIL PROTECTED] Description: tuxeyes- a fancy version of xeyes Changes: tuxeyes (0.0.3-8) unstable; urgency=low . * Correct dependencies due to Xorg transition. Files: 73fbc59399c2a0796c71fdcf0b57baec 595 x11 optional tuxeyes_0.0.3-8.dsc 10afafdc1e5c9e4588c84b3e12794105 6757 x11 optional tuxeyes_0.0.3-8.diff.gz 70010d8001eec95e2d812fcd4599dabf 174560 x11 optional tuxeyes_0.0.3-8_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDCB2UMDatjqUaT90RAmq/AKCdxvojR8NqGyXc4TGFM1hQnCSdHwCglU/d tJceId3dXmv5WRUbp8xJBko= =H2xK -END PGP SIGNATURE- Accepted: tuxeyes_0.0.3-8.diff.gz to pool/main/t/tuxeyes/tuxeyes_0.0.3-8.diff.gz tuxeyes_0.0.3-8.dsc to pool/main/t/tuxeyes/tuxeyes_0.0.3-8.dsc tuxeyes_0.0.3-8_i386.deb to pool/main/t/tuxeyes/tuxeyes_0.0.3-8_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted wordpress 1.5.2-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 19 Aug 2005 10:58:17 +1000 Source: wordpress Binary: wordpress Architecture: source all Version: 1.5.2-1 Distribution: unstable Urgency: high Maintainer: Kai Hendry [EMAIL PROTECTED] Changed-By: Kai Hendry [EMAIL PROTECTED] Description: wordpress - an award winning weblog manager Closes: 323040 Changes: wordpress (1.5.2-1) unstable; urgency=high . * New upstream security fix release * Closes: #323040: CAN-2005-2612 * See: http://wordpress.org/development/2005/08/one-five-two/ Files: 67d3fc919c076569623ae2780f6c851a 564 web optional wordpress_1.5.2-1.dsc 680e6381c8111f555a2c7066ddafd575 298514 web optional wordpress_1.5.2.orig.tar.gz 09a0b1ed6a5073194aedae4294892b40 7575 web optional wordpress_1.5.2-1.diff.gz d0b3587aaf4d2931ce03a0af1c9aea22 303896 web optional wordpress_1.5.2-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDCCHq78o9R9NraMQRAlJWAJ90BYH4CkIe0sZVCfdKS0FcP4+IPwCfXDbg 2P7eGO+Mvl19+ugLQAXZvXY= =YBP6 -END PGP SIGNATURE- Accepted: wordpress_1.5.2-1.diff.gz to pool/main/w/wordpress/wordpress_1.5.2-1.diff.gz wordpress_1.5.2-1.dsc to pool/main/w/wordpress/wordpress_1.5.2-1.dsc wordpress_1.5.2-1_all.deb to pool/main/w/wordpress/wordpress_1.5.2-1_all.deb wordpress_1.5.2.orig.tar.gz to pool/main/w/wordpress/wordpress_1.5.2.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libpmount 0.0.7 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 21 Aug 2005 09:37:41 +0300 Source: libpmount Binary: libpmount0.0 libpmount-dev Architecture: source i386 Version: 0.0.7 Distribution: unstable Urgency: low Maintainer: Guillem Jover [EMAIL PROTECTED] Changed-By: Guillem Jover [EMAIL PROTECTED] Description: libpmount-dev - portable mount library - development files libpmount0.0 - portable mount library - shared library Closes: 323338 323339 Changes: libpmount (0.0.7) unstable; urgency=low . * Reintroduce missing symbols. (Closes: #323338) * Fix testsuite generation and generalize them by moving away from shell script files to a proper Makefile and a C source file. (Closes: #323339) * Use loop devices on linux if trying to mount a file image. * Make static internal functions __findloop, __getloop and __clrloop. * Switched to versioned symbols. * Now using Standars-Version 3.6.2 (no changes needed). Files: 0fbeead105aa304daa73490514b048af 514 libs optional libpmount_0.0.7.dsc b2cbce72ef9b694e0a3e9eda973f5957 9673 libs optional libpmount_0.0.7.tar.gz 27e5c4ba31db5fb7aa3625adac578257 5704 libdevel optional libpmount-dev_0.0.7_i386.deb 9b9deaadfdcb928e8439b9442a34676f 6302 libs optional libpmount0.0_0.0.7_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDCCVZuW9ciZ2SjJsRAss2AKC3y9ZCE2UOooysHVp95fgEN9np6gCfVZ++ 3XrWAYt3fErMWiF4wjhBkL4= =igx1 -END PGP SIGNATURE- Accepted: libpmount-dev_0.0.7_i386.deb to pool/main/libp/libpmount/libpmount-dev_0.0.7_i386.deb libpmount0.0_0.0.7_i386.deb to pool/main/libp/libpmount/libpmount0.0_0.0.7_i386.deb libpmount_0.0.7.dsc to pool/main/libp/libpmount/libpmount_0.0.7.dsc libpmount_0.0.7.tar.gz to pool/main/libp/libpmount/libpmount_0.0.7.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted d-shlibs 0.26 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 21 Aug 2005 14:00:02 +0900 Source: d-shlibs Binary: d-shlibs Architecture: source all Version: 0.26 Distribution: unstable Urgency: low Maintainer: Junichi Uekawa [EMAIL PROTECTED] Changed-By: Junichi Uekawa [EMAIL PROTECTED] Description: d-shlibs - Debian shared library package building helper scripts Closes: 306341 Changes: d-shlibs (0.26) unstable; urgency=low . * Check for objdump -p failure status, to check for error case when library is not where it should be. (closes: #306341) * Standards-Version: 3.6.2 Files: 70f867d7fbf2d1d97d8e74488843551d 498 utils optional d-shlibs_0.26.dsc 18f7a744600e24a8932ca2ccb352f8c4 41442 utils optional d-shlibs_0.26.tar.gz ac788bff4b8987e034d0688bbd6e6d52 11454 utils optional d-shlibs_0.26_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDCCo9gY5NIXPNpFURAkO9AJ9xX1Zfw9OABygrgmZKWjPtZ+0tcACgvAnS iq2QhCuN05zHrHaxvNPkP0U= =BVny -END PGP SIGNATURE- Accepted: d-shlibs_0.26.dsc to pool/main/d/d-shlibs/d-shlibs_0.26.dsc d-shlibs_0.26.tar.gz to pool/main/d/d-shlibs/d-shlibs_0.26.tar.gz d-shlibs_0.26_all.deb to pool/main/d/d-shlibs/d-shlibs_0.26_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted canna 3.7p3-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 21 Aug 2005 13:31:49 +0900 Source: canna Binary: canna-utils libcanna1g libcanna1g-dev canna Architecture: source i386 Version: 3.7p3-2 Distribution: unstable Urgency: low Maintainer: Junichi Uekawa [EMAIL PROTECTED] Changed-By: Junichi Uekawa [EMAIL PROTECTED] Description: canna - A Japanese input system (server and dictionary). canna-utils - A japanese input system (utility). libcanna1g - Canna Runtime Library libcanna1g-dev - Canna Static Library and Headers Closes: 308518 313201 Changes: canna (3.7p3-2) unstable; urgency=low . * add cs.po translation (closes: #308518) * add vi.po translation (closes: #313201) * Standards-Version: 3.6.2 * Remove the Build-conflicts against libc6 2.3.1, since 3.5b2-51; should no longer be necessary. * postinst: do not use [ .. -a ... ], use [ ] [ ] instead. Files: 9044169ad247243ea8ee879f9b782992 661 utils optional canna_3.7p3-2.dsc 79632411eeae670bfd423da8a6076521 25486 utils optional canna_3.7p3-2.diff.gz 56275fc6685f7cd83e40a9b071b1a1c5 938288 utils optional canna_3.7p3-2_i386.deb db732dcd8a886a90343e8e18401443f0 110034 utils optional canna-utils_3.7p3-2_i386.deb 69de0429bb3d8d9907b354c67761ba7d 498958 libs optional libcanna1g_3.7p3-2_i386.deb 0c5cf45f90522aba93a427e427c21ea5 569946 libdevel optional libcanna1g-dev_3.7p3-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDCCiVgY5NIXPNpFURAtTdAJ4w2V7i9cyAM7kmwp0FGNlRjA8ikQCgixZQ XEIat4gd5ttCUSXqSfPkrMc= =Z7Nh -END PGP SIGNATURE- Accepted: canna-utils_3.7p3-2_i386.deb to pool/main/c/canna/canna-utils_3.7p3-2_i386.deb canna_3.7p3-2.diff.gz to pool/main/c/canna/canna_3.7p3-2.diff.gz canna_3.7p3-2.dsc to pool/main/c/canna/canna_3.7p3-2.dsc canna_3.7p3-2_i386.deb to pool/main/c/canna/canna_3.7p3-2_i386.deb libcanna1g-dev_3.7p3-2_i386.deb to pool/main/c/canna/libcanna1g-dev_3.7p3-2_i386.deb libcanna1g_3.7p3-2_i386.deb to pool/main/c/canna/libcanna1g_3.7p3-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gamix 1.99.p14.debian1-3 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 21 Aug 2005 13:24:19 +0900 Source: gamix Binary: gamix Architecture: source i386 Version: 1.99.p14.debian1-3 Distribution: unstable Urgency: low Maintainer: Junichi Uekawa [EMAIL PROTECTED] Changed-By: Junichi Uekawa [EMAIL PROTECTED] Description: gamix - Graphical sound mixer for ALSA Closes: 313711 Changes: gamix (1.99.p14.debian1-3) unstable; urgency=low . * update de.po (closes: #313711) * remove build-dep to alsa-headers * Standards-Version: 3.6.2 * update debhelper compat level: 1-4. Files: 4dbfacaf13284a7d9ee9b1705074e0d4 643 sound extra gamix_1.99.p14.debian1-3.dsc c577b7e94c1b75081250f203fab6d91d 8398 sound extra gamix_1.99.p14.debian1-3.diff.gz deec2064bf72cf370d821b528e4ab397 38366 sound extra gamix_1.99.p14.debian1-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDCCtVgY5NIXPNpFURAscYAKCmi3gMR2EmgMEWWP19epTi1DXyxQCfS64D E12rSkTG/eNK3mbWWOyIbpA= =TLQW -END PGP SIGNATURE- Accepted: gamix_1.99.p14.debian1-3.diff.gz to pool/main/g/gamix/gamix_1.99.p14.debian1-3.diff.gz gamix_1.99.p14.debian1-3.dsc to pool/main/g/gamix/gamix_1.99.p14.debian1-3.dsc gamix_1.99.p14.debian1-3_i386.deb to pool/main/g/gamix/gamix_1.99.p14.debian1-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libqalculate 0.8.1.1-4 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 21 Aug 2005 09:07:56 +0200 Source: libqalculate Binary: qalc libqalculate-dev libqalculate0 Architecture: source i386 Version: 0.8.1.1-4 Distribution: unstable Urgency: low Maintainer: Martin Waitz [EMAIL PROTECTED] Changed-By: Martin Waitz [EMAIL PROTECTED] Description: libqalculate-dev - Powerful and easy to use desktop calculator - development libqalculate0 - Powerful and easy to use desktop calculator - library qalc - Powerful and easy to use command line calculator Changes: libqalculate (0.8.1.1-4) unstable; urgency=low . * debian-control: arg, -dev has to depend on the library Files: 3dd85f47745cbe5eaebadabc2e1b0ee4 718 math optional libqalculate_0.8.1.1-4.dsc df29d31b3efff9fb3d7c727a948ca520 34862 math optional libqalculate_0.8.1.1-4.diff.gz 5b419a17d2d08383072961d7ffcfd42f 148566 math optional qalc_0.8.1.1-4_i386.deb 4bef1cfb4a6e9ed81cd5d6d621997f37 691732 libs optional libqalculate0_0.8.1.1-4_i386.deb 944a01e0eaecf71a111047be216b8b59 887538 libdevel optional libqalculate-dev_0.8.1.1-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDCClrj/Eaxd/oD7IRApJ+AJoDaN2opLF9HQK9RmqU1yhWNnskIwCeNXzP TNrgBBMe+p1n69sMLNnFF9c= =QMQf -END PGP SIGNATURE- Accepted: libqalculate-dev_0.8.1.1-4_i386.deb to pool/main/libq/libqalculate/libqalculate-dev_0.8.1.1-4_i386.deb libqalculate0_0.8.1.1-4_i386.deb to pool/main/libq/libqalculate/libqalculate0_0.8.1.1-4_i386.deb libqalculate_0.8.1.1-4.diff.gz to pool/main/libq/libqalculate/libqalculate_0.8.1.1-4.diff.gz libqalculate_0.8.1.1-4.dsc to pool/main/libq/libqalculate/libqalculate_0.8.1.1-4.dsc qalc_0.8.1.1-4_i386.deb to pool/main/libq/libqalculate/qalc_0.8.1.1-4_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted tlf 0.9.23-6 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 21 Aug 2005 09:17:18 +0200 Source: tlf Binary: tlf Architecture: source i386 Version: 0.9.23-6 Distribution: unstable Urgency: low Maintainer: Joop Stakenborg [EMAIL PROTECTED] Changed-By: Joop Stakenborg [EMAIL PROTECTED] Description: tlf- Console mode purpose CW keyer, logging- and contest program Changes: tlf (0.9.23-6) unstable; urgency=low . * Build depends on automake1.4 in case it is needed during th build process. Files: e12dcddb4349c8241669f840a35cc714 616 hamradio optional tlf_0.9.23-6.dsc 4190b7e02ea62fc49fe071f6b61599de 28605 hamradio optional tlf_0.9.23-6.diff.gz 5f12c9889343daede7943879b598f5de 227178 hamradio optional tlf_0.9.23-6_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDCCvRnuUI/ps3DJoRAjW8AJ9R58kx93XkdWcOvu6XrXzaGvshNwCfcLrL 6SPnJcbCXBMU9uz26DgCIkQ= =NIps -END PGP SIGNATURE- Accepted: tlf_0.9.23-6.diff.gz to pool/main/t/tlf/tlf_0.9.23-6.diff.gz tlf_0.9.23-6.dsc to pool/main/t/tlf/tlf_0.9.23-6.dsc tlf_0.9.23-6_i386.deb to pool/main/t/tlf/tlf_0.9.23-6_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted wysihtml 0.12-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 21 Aug 2005 13:01:17 +0900 Source: wysihtml Binary: wysihtml-el Architecture: source i386 Version: 0.12-1 Distribution: unstable Urgency: low Maintainer: Junichi Uekawa [EMAIL PROTECTED] Changed-By: Junichi Uekawa [EMAIL PROTECTED] Description: wysihtml-el - Almost real-time previewing system for HTML and DocBook Changes: wysihtml (0.12-1) unstable; urgency=low . * New upstream version - Rewritten DocBookXML support. * Standards-version: 3.6.2 Files: a4c8a74c8a4e536bf520169a2060fc75 565 text optional wysihtml_0.12-1.dsc 7cbd5f409db7f11f8097a346b8317ab7 77565 text optional wysihtml_0.12.orig.tar.gz 5365430cac7e6a942a77a59639604ae7 3613 text optional wysihtml_0.12-1.diff.gz 2d086f3ec1b5bb0f8228bccfc4b85cbb 14758 text optional wysihtml-el_0.12-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDCDDYgY5NIXPNpFURAt52AKDCKhb/7WyDxRjadYl/Gdq8UICI9gCdEFCI 2QvSgnDQBY1wOLkoiNi9W6o= =nsFf -END PGP SIGNATURE- Accepted: wysihtml-el_0.12-1_i386.deb to pool/main/w/wysihtml/wysihtml-el_0.12-1_i386.deb wysihtml_0.12-1.diff.gz to pool/main/w/wysihtml/wysihtml_0.12-1.diff.gz wysihtml_0.12-1.dsc to pool/main/w/wysihtml/wysihtml_0.12-1.dsc wysihtml_0.12.orig.tar.gz to pool/main/w/wysihtml/wysihtml_0.12.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted soundmodem 0.9-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 20 Aug 2005 10:32:59 +0200 Source: soundmodem Binary: soundmodem Architecture: source i386 Version: 0.9-2 Distribution: unstable Urgency: low Maintainer: Debian Hamradio Maintainers debian-hams@lists.debian.org Changed-By: Joop Stakenborg [EMAIL PROTECTED] Description: soundmodem - Sound Card Amateur Packet Radio Modems Closes: 324050 Changes: soundmodem (0.9-2) unstable; urgency=low . * A fix for jumps into statement expressions. Patch by Matt Kraai, thanks! Closes: #324050. * Upload for the Debian Hamradio Maintainers Pool. Files: 511dfad6065820d26ce64c24823aa25f 881 hamradio optional soundmodem_0.9-2.dsc f77cd9af18b0597ca7fcf5d04475a246 30433 hamradio optional soundmodem_0.9-2.diff.gz 16b8fafaa358c3b50c4fec0c184be5a3 157134 hamradio optional soundmodem_0.9-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDCC5ynuUI/ps3DJoRAq7QAJ41CIEQebzyTzgIxOuo+TgVj7zu3QCeJq2/ y72l+Fu/YbPE5Oz8Z8VLgo0= =rPTO -END PGP SIGNATURE- Accepted: soundmodem_0.9-2.diff.gz to pool/main/s/soundmodem/soundmodem_0.9-2.diff.gz soundmodem_0.9-2.dsc to pool/main/s/soundmodem/soundmodem_0.9-2.dsc soundmodem_0.9-2_i386.deb to pool/main/s/soundmodem/soundmodem_0.9-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted update-cluster 0.41.5-1 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 21 Aug 2005 13:52:57 +0900 Source: update-cluster Binary: update-cluster-hosts update-cluster Architecture: source i386 all Version: 0.41.5-1 Distribution: unstable Urgency: low Maintainer: Junichi Uekawa [EMAIL PROTECTED] Changed-By: Junichi Uekawa [EMAIL PROTECTED] Description: update-cluster - System to update configuration files for clusters automatically update-cluster-hosts - System to update configuration files for clusters automatically Closes: 291569 311858 324065 Changes: update-cluster (0.41.5-1) unstable; urgency=low . * New upstream version - Document --domainsuffix option for update-cluster-maccollect (Closes: #291569). * [l10n:de] Updated German translation of the debconf templates, thanks to Erik Schanze (Closes: #311858). * add an example cluster.xml file. * INTL:vi Vietnamese translation for update-cluster (closes: #324065) * Standards-Version: 3.6.2 * debian/config: avoid using -a in 'test' and use Files: d7157d2806591e44ff229653ae79a80a 708 admin extra update-cluster_0.41.5-1.dsc 62f8b4549ab94c7bc113456b30ec20fd 170661 admin extra update-cluster_0.41.5.orig.tar.gz 4b4c265f2e4289f044bc53d4b34a84b2 10658 admin extra update-cluster_0.41.5-1.diff.gz 02ca37cf27d22ae0614771dc21810e87 1 admin extra update-cluster-hosts_0.41.5-1_all.deb 15fa1448c7804b7d8c995bffee99a413 46170 admin extra update-cluster_0.41.5-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDCC3SgY5NIXPNpFURAsRzAKCQXNINYRHDsSH00f8BxCZQJDrNsgCg2/Hv Topr3Jli5eTVnvSdKC2EvbA= =TW9v -END PGP SIGNATURE- Accepted: update-cluster-hosts_0.41.5-1_all.deb to pool/main/u/update-cluster/update-cluster-hosts_0.41.5-1_all.deb update-cluster_0.41.5-1.diff.gz to pool/main/u/update-cluster/update-cluster_0.41.5-1.diff.gz update-cluster_0.41.5-1.dsc to pool/main/u/update-cluster/update-cluster_0.41.5-1.dsc update-cluster_0.41.5-1_i386.deb to pool/main/u/update-cluster/update-cluster_0.41.5-1_i386.deb update-cluster_0.41.5.orig.tar.gz to pool/main/u/update-cluster/update-cluster_0.41.5.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted whizzytex 1.2.3-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 21 Aug 2005 12:04:00 +0900 Source: whizzytex Binary: whizzytex Architecture: source all Version: 1.2.3-1 Distribution: unstable Urgency: low Maintainer: Junichi Uekawa [EMAIL PROTECTED] Changed-By: Junichi Uekawa [EMAIL PROTECTED] Description: whizzytex - a WYSIWYG emacs environment for LaTeX Closes: 314476 Changes: whizzytex (1.2.3-1) unstable; urgency=low . * New upstream release * Set MULTIPLE=true by default (closes: #314476) - Pressing 'w' in advi window will toggle the 'current' view and 'whole' view. * 10_hevea_nosymb_dropped: -nosymb option is no longer accepted by hevea. - build-depend on hevea 1.08 or greater * Standards-Version 3.6.2: no change. * updated FAQ from http://pauillac.inria.fr/whizzytex/FAQ.html Files: c3aa132ec80cc148c7c63d93c222d013 621 tex optional whizzytex_1.2.3-1.dsc e42c45e18ef933111eedb57cb327317c 738160 tex optional whizzytex_1.2.3.orig.tar.gz 3757d16918010afdbe2a33cf90dcf519 16089 tex optional whizzytex_1.2.3-1.diff.gz c380692e33e0ea4a3a6139f6499f7d23 136252 tex optional whizzytex_1.2.3-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDCC/QgY5NIXPNpFURAhUwAKCueZRHcRh9kkcu4ZdK8B/X1tbvQwCgl8Zn tUJ/nWt6oG+yxYNYR5FbTrQ= =uRdK -END PGP SIGNATURE- Accepted: whizzytex_1.2.3-1.diff.gz to pool/main/w/whizzytex/whizzytex_1.2.3-1.diff.gz whizzytex_1.2.3-1.dsc to pool/main/w/whizzytex/whizzytex_1.2.3-1.dsc whizzytex_1.2.3-1_all.deb to pool/main/w/whizzytex/whizzytex_1.2.3-1_all.deb whizzytex_1.2.3.orig.tar.gz to pool/main/w/whizzytex/whizzytex_1.2.3.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted ipsec-tools 1:0.6.1-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 21 Aug 2005 13:24:15 +0530 Source: ipsec-tools Binary: racoon ipsec-tools Architecture: source i386 Version: 1:0.6.1-1 Distribution: unstable Urgency: low Maintainer: Ganesan Rajagopal [EMAIL PROTECTED] Changed-By: Ganesan Rajagopal [EMAIL PROTECTED] Description: ipsec-tools - IPsec tools for Linux racoon - IPsec IKE keying daemon Changes: ipsec-tools (1:0.6.1-1) unstable; urgency=low . * New upstream release Files: e6fbb9499124c6481ada291e7f7152fe 673 net extra ipsec-tools_0.6.1-1.dsc 3e5c52b2bf3a378f87e11b55885ff140 911229 net extra ipsec-tools_0.6.1.orig.tar.gz ce7af2e1ba65d99f9caaa9882623d74f 50495 net extra ipsec-tools_0.6.1-1.diff.gz c5522afd3df94b95a76f87df0303f71d 81634 net extra ipsec-tools_0.6.1-1_i386.deb 7bc6a7d02d7842f166c56683605454ec 315782 net extra racoon_0.6.1-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDCDZrFeACul2MEuoRAp8KAKDNIrKKB+BU9uufhlFgW6eFYmaJmgCfaldt 8afASlwtIGrcrHaeqBjB9k4= =zrJV -END PGP SIGNATURE- Accepted: ipsec-tools_0.6.1-1.diff.gz to pool/main/i/ipsec-tools/ipsec-tools_0.6.1-1.diff.gz ipsec-tools_0.6.1-1.dsc to pool/main/i/ipsec-tools/ipsec-tools_0.6.1-1.dsc ipsec-tools_0.6.1-1_i386.deb to pool/main/i/ipsec-tools/ipsec-tools_0.6.1-1_i386.deb ipsec-tools_0.6.1.orig.tar.gz to pool/main/i/ipsec-tools/ipsec-tools_0.6.1.orig.tar.gz racoon_0.6.1-1_i386.deb to pool/main/i/ipsec-tools/racoon_0.6.1-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libcommons-modeler-java 1.1-6 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 21 Aug 2005 10:12:56 +0200 Source: libcommons-modeler-java Binary: libcommons-modeler-java libcommons-modeler-java-doc Architecture: source all Version: 1.1-6 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers pkg-java-maintainers@lists.alioth.debian.org Changed-By: Arnaud Vandyck [EMAIL PROTECTED] Description: libcommons-modeler-java - A convenience library to use Java Management Extensions (JMX) libcommons-modeler-java-doc - Javadoc API documentation and examples for Commons Modeler Changes: libcommons-modeler-java (1.1-6) unstable; urgency=low . * libant1.6-java to ant transition Files: 07d3f6e36143f8973bbcb4abd4b87ba1 935 libs optional libcommons-modeler-java_1.1-6.dsc 078b1eaf50d3b5a55a67ba6bd9e50a4e 3808 libs optional libcommons-modeler-java_1.1-6.diff.gz c5527f06c79f6a175d76c08448b142a6 113772 libs optional libcommons-modeler-java_1.1-6_all.deb 248cb8a9aa4ca094170b7a53b1b34b4d 114936 libs optional libcommons-modeler-java-doc_1.1-6_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDCDx94vzFZu62tMIRAsAEAJ9w2ZIlkgxB+whjyklPp4thZIPqbQCeKu7v c9cG1GfjjCgKdn2reOOl44w= =6gn7 -END PGP SIGNATURE- Accepted: libcommons-modeler-java-doc_1.1-6_all.deb to pool/main/libc/libcommons-modeler-java/libcommons-modeler-java-doc_1.1-6_all.deb libcommons-modeler-java_1.1-6.diff.gz to pool/main/libc/libcommons-modeler-java/libcommons-modeler-java_1.1-6.diff.gz libcommons-modeler-java_1.1-6.dsc to pool/main/libc/libcommons-modeler-java/libcommons-modeler-java_1.1-6.dsc libcommons-modeler-java_1.1-6_all.deb to pool/main/libc/libcommons-modeler-java/libcommons-modeler-java_1.1-6_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libcommons-launcher-java 1.1-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 21 Aug 2005 10:20:37 +0200 Source: libcommons-launcher-java Binary: libcommons-launcher-java Architecture: source all Version: 1.1-2 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers pkg-java-maintainers@lists.alioth.debian.org Changed-By: Arnaud Vandyck [EMAIL PROTECTED] Description: libcommons-launcher-java - cross platform java application launcher Changes: libcommons-launcher-java (1.1-2) unstable; urgency=low . * libant1.6-java to ant transition Files: 09a14b750f31816b8b6ce3454847a0c9 811 libs optional libcommons-launcher-java_1.1-2.dsc 2f2341ffdf477d070491993fa6f1bf82 5740 libs optional libcommons-launcher-java_1.1-2.diff.gz acacda355b81b93e39b49d04bad99809 133484 libs optional libcommons-launcher-java_1.1-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDCDxm4vzFZu62tMIRAsj0AJwIQ5GV3MPIv8M1pPO222F26bUzewCePaoj Sw1u3af54LSDNimDjtBZ11s= =iIgU -END PGP SIGNATURE- Accepted: libcommons-launcher-java_1.1-2.diff.gz to pool/main/libc/libcommons-launcher-java/libcommons-launcher-java_1.1-2.diff.gz libcommons-launcher-java_1.1-2.dsc to pool/main/libc/libcommons-launcher-java/libcommons-launcher-java_1.1-2.dsc libcommons-launcher-java_1.1-2_all.deb to pool/main/libc/libcommons-launcher-java/libcommons-launcher-java_1.1-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libcommons-validator-java 1:1.1.4-3 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 21 Aug 2005 10:41:05 +0200 Source: libcommons-validator-java Binary: libcommons-validator-java Architecture: source all Version: 1:1.1.4-3 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers pkg-java-maintainers@lists.alioth.debian.org Changed-By: Arnaud Vandyck [EMAIL PROTECTED] Description: libcommons-validator-java - ease and speed development and maintenance of validation rules Changes: libcommons-validator-java (1:1.1.4-3) unstable; urgency=low . * libant1.6-java to ant transition * removed the '$' Id from the dtd files (they are not edited by us!) Files: b211939a07d87860a03fb499ed6709bb 947 libs optional libcommons-validator-java_1.1.4-3.dsc 43b66c0bc4419eff24305fe799380384 9154 libs optional libcommons-validator-java_1.1.4-3.diff.gz 223b01f691600e76ad2b60c34390ae03 169258 libs optional libcommons-validator-java_1.1.4-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDCD944vzFZu62tMIRAlElAKCTRvbBp8Ttxfd1H9PUcfC3wFTL/ACgsmhp zdMAV3mVzCuo/aHEwwm/+Q0= =wVkw -END PGP SIGNATURE- Accepted: libcommons-validator-java_1.1.4-3.diff.gz to pool/main/libc/libcommons-validator-java/libcommons-validator-java_1.1.4-3.diff.gz libcommons-validator-java_1.1.4-3.dsc to pool/main/libc/libcommons-validator-java/libcommons-validator-java_1.1.4-3.dsc libcommons-validator-java_1.1.4-3_all.deb to pool/main/libc/libcommons-validator-java/libcommons-validator-java_1.1.4-3_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libdtdparser-java 1.21a-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 21 Aug 2005 11:26:22 +0200 Source: libdtdparser-java Binary: libdtdparser-java Architecture: source all Version: 1.21a-1 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers pkg-java-maintainers@lists.alioth.debian.org Changed-By: Arnaud Vandyck [EMAIL PROTECTED] Description: libdtdparser-java - Java DTD parser library Changes: libdtdparser-java (1.21a-1) unstable; urgency=low . * libant1.6-java to ant transition * build with kaffe (no more libgnujaxp-java) * generate the documentation * regenerated tarball to get rid of generated documentation, compiled files and jar file * added a patch to find the manifestfile (no more in classes directory because I removed it bu in source directory) * added a patch to properly format Scanner.java Files: fa38ab1d7e3d5a9800682e7eb572b863 725 libs optional libdtdparser-java_1.21a-1.dsc 2818c7e2efe62469e67a1495b757d6f6 36450 libs optional libdtdparser-java_1.21a.orig.tar.gz 19def14d03701f3b2aed956a5bb4d4ee 12314 libs optional libdtdparser-java_1.21a-1.diff.gz 8d98f691753ba429fc886eeac04f4aff 77668 libs optional libdtdparser-java_1.21a-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDCEpp4vzFZu62tMIRAq+4AKCINH7QvTcSSFIPl7qHOe/D2OZdLACfb9EZ 5frNs50SQwpj24GZcOKuzJ0= =wPJw -END PGP SIGNATURE- Accepted: libdtdparser-java_1.21a-1.diff.gz to pool/main/libd/libdtdparser-java/libdtdparser-java_1.21a-1.diff.gz libdtdparser-java_1.21a-1.dsc to pool/main/libd/libdtdparser-java/libdtdparser-java_1.21a-1.dsc libdtdparser-java_1.21a-1_all.deb to pool/main/libd/libdtdparser-java/libdtdparser-java_1.21a-1_all.deb libdtdparser-java_1.21a.orig.tar.gz to pool/main/libd/libdtdparser-java/libdtdparser-java_1.21a.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted exim4 4.52-2 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 21 Aug 2005 11:44:27 +0200 Source: exim4 Binary: eximon4 exim4-daemon-custom exim4-daemon-heavy exim4-base exim4 exim4-daemon-light exim4-config Architecture: source i386 all Version: 4.52-2 Distribution: unstable Urgency: low Maintainer: Exim4 Maintainers [EMAIL PROTECTED] Changed-By: Andreas Metzler [EMAIL PROTECTED] Description: exim4 - metapackage to ease exim MTA (v4) installation exim4-base - support files for all exim MTA (v4) packages exim4-config - configuration for the exim MTA (v4) exim4-daemon-heavy - exim MTA (v4) daemon with extended features, including exiscan-ac exim4-daemon-light - lightweight exim MTA (v4) daemon eximon4- monitor application for the exim MTA (v4) (X11 interface) Closes: 212893 285371 317429 320231 323565 Changes: exim4 (4.52-2) unstable; urgency=low . * unpack/pack configs to get clear EDITME patches (mh) * Update ca (Catalan) translation. Thanks to Aleix Badia i Bosch. (mh) Closes: #317429 * Update mk (Macedonian) translation. Thanks to Georgi Stanojevski. (mh) Closes: #320231 * Use certtool from gnutls-bin in cron.daily to re-generate gnutls-params instead of only removing the file and letting exim4 re-generate it at SMTP time after receiving STARTTLS. The maximum runtime of certtool is limited to 2*1800 seconds per default by using timeout.pl by Piotr Roszatycki (checked and beautified by Marc 'HE' Brockschmidt). Add gnutls-bin to exim4-base' Suggests. (am) Closes: #285371 * Build-Depend on libgnutls-dev (from gnutls12) instead of libgnutls11. * Drop compability with debhelper in woody (am): - mv *.templates.master *.templates - update po/POTFILES.in accordingly. - no more manual invocation of po2debconf in debian/rules - use dh_installppp instead of manual dh_installdirs/dh_install. Closes: #212893 - Build-Depends: debhelper (= 4.1.68) * drop upgly passwd dependency introduced in 4.30-6. (am) * shorten Build-Depends by replacing libxfoo-dev|xlibs-dev' with just 'libxfoo-dev'. (am) * Do not try to authenticate to smarthost if smarthost offers AUTH LOGIN but passwd.client does not contain a matching entry. (am) Closes: #323565 Files: cf9d612c5f7d71aa20e45366fe313a14 1001 mail standard exim4_4.52-2.dsc b46b59506fade8081a275037e79a8404 314873 mail standard exim4_4.52-2.diff.gz c278f7cbc2c51d9cf145e32d80e3034d 842432 mail standard exim4-base_4.52-2_i386.deb 6bdb374cd8336ddd082df425d9a806fe 374912 mail standard exim4-daemon-light_4.52-2_i386.deb 45c36eb636e1f49fd48121c2499147a0 79170 mail optional eximon4_4.52-2_i386.deb 58f1fa4ccafee7b1fe54a76fe3845114 424636 mail optional exim4-daemon-heavy_4.52-2_i386.deb 34d23ecccd951f5f0c5346b90f5ae3c0 245710 mail standard exim4-config_4.52-2_all.deb 05c23498b2801ed2cb3bff365e2a7379 1132 mail standard exim4_4.52-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDCE/xHTOcZYuNdmMRAoiVAKCkqNJrYpLaLLbgBT/GHkKjlJZOLgCdH80N lJCc4tRspeSwbEsqo8UbBQc= =hALJ -END PGP SIGNATURE- Accepted: exim4-base_4.52-2_i386.deb to pool/main/e/exim4/exim4-base_4.52-2_i386.deb exim4-config_4.52-2_all.deb to pool/main/e/exim4/exim4-config_4.52-2_all.deb exim4-daemon-heavy_4.52-2_i386.deb to pool/main/e/exim4/exim4-daemon-heavy_4.52-2_i386.deb exim4-daemon-light_4.52-2_i386.deb to pool/main/e/exim4/exim4-daemon-light_4.52-2_i386.deb exim4_4.52-2.diff.gz to pool/main/e/exim4/exim4_4.52-2.diff.gz exim4_4.52-2.dsc to pool/main/e/exim4/exim4_4.52-2.dsc exim4_4.52-2_all.deb to pool/main/e/exim4/exim4_4.52-2_all.deb eximon4_4.52-2_i386.deb to pool/main/e/exim4/eximon4_4.52-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted ksimus-datarecorder 0.3.6-8 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 18 Aug 2005 11:28:20 +0200 Source: ksimus-datarecorder Binary: ksimus-datarecorder Architecture: source i386 Version: 0.3.6-8 Distribution: unstable Urgency: low Maintainer: Aurelien Jarno [EMAIL PROTECTED] Changed-By: Aurelien Jarno [EMAIL PROTECTED] Description: ksimus-datarecorder - KSimus datarecorder package Changes: ksimus-datarecorder (0.3.6-8) unstable; urgency=low . * C++ transition: build-depends on ksimus-dev (= 0.3.6-2-7). * Bumped Standards-Version to 3.6.2 (no changes). Files: f2c60a7db6208e513c7ef59af7fee841 732 electronics optional ksimus-datarecorder_0.3.6-8.dsc 46c179f7284d6add536ffb5dfbc694cf 4531 electronics optional ksimus-datarecorder_0.3.6-8.diff.gz f921f4fd0a46ddfa8c5c916a28f5ba00 118930 electronics optional ksimus-datarecorder_0.3.6-8_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDBFu8w3ao2vG823MRAjhzAJsEx6t/dkdNMMcURigKmRjQc4RKRQCeN1l3 R4TMsGj0y5OI/3bBqBVmDog= =l2Uz -END PGP SIGNATURE- Accepted: ksimus-datarecorder_0.3.6-8.diff.gz to pool/main/k/ksimus-datarecorder/ksimus-datarecorder_0.3.6-8.diff.gz ksimus-datarecorder_0.3.6-8.dsc to pool/main/k/ksimus-datarecorder/ksimus-datarecorder_0.3.6-8.dsc ksimus-datarecorder_0.3.6-8_i386.deb to pool/main/k/ksimus-datarecorder/ksimus-datarecorder_0.3.6-8_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted kipi-plugins 0.1+beta2-22 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 21 Aug 2005 10:48:53 +0100 Source: kipi-plugins Binary: kipi-plugins Architecture: source i386 Version: 0.1+beta2-22 Distribution: unstable Urgency: low Maintainer: Achim Bohnet [EMAIL PROTECTED] Changed-By: Mark Purcell [EMAIL PROTECTED] Description: kipi-plugins - image manipulation/handling plugins for KIPI aware programs Changes: kipi-plugins (0.1+beta2-22) unstable; urgency=low . * C++ transition package * Upgrade Build-Depends: kdelibs4-dev (= 3.4.2-1), libkexif1-dev (= 0.2.1-5), libkipi0-dev (= 0.1.1-3) Files: 0ae497a1bfea20af93d41f20354a069a 816 kde optional kipi-plugins_0.1+beta2-22.dsc fa22a835f9acf89e1e9d66b6e275e401 17221 kde optional kipi-plugins_0.1+beta2-22.diff.gz 279476a7b8406b70accd9ec15390375d 3164826 kde optional kipi-plugins_0.1+beta2-22_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDCFDMoCzanz0IthIRAvu7AKCaX34mvN+ZgkcgYtBCRU2L8rOt+ACfU0VO kaEAONhczpQSEFW8vEefP2k= =5hkb -END PGP SIGNATURE- Accepted: kipi-plugins_0.1+beta2-22.diff.gz to pool/main/k/kipi-plugins/kipi-plugins_0.1+beta2-22.diff.gz kipi-plugins_0.1+beta2-22.dsc to pool/main/k/kipi-plugins/kipi-plugins_0.1+beta2-22.dsc kipi-plugins_0.1+beta2-22_i386.deb to pool/main/k/kipi-plugins/kipi-plugins_0.1+beta2-22_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted x86info 1.14-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 21 Aug 2005 11:08:09 +0100 Source: x86info Binary: x86info Architecture: source i386 Version: 1.14-2 Distribution: unstable Urgency: low Maintainer: Mark Brown [EMAIL PROTECTED] Changed-By: Mark Brown [EMAIL PROTECTED] Description: x86info- Display diagnostic information about i386 compatible CPUs Closes: 324233 Changes: x86info (1.14-2) unstable; urgency=low . * Add vietnamese translation of debconf templates provided by Clytie Siddall [EMAIL PROTECTED] (closes: #324233). Files: ee9c75f6ea6091dfdd61c73423136d60 603 admin extra x86info_1.14-2.dsc abec8af31fab72f60276c11146f53fed 6780 admin extra x86info_1.14-2.diff.gz 42f80bbae74f608c3aaa3f59564c37f9 35910 admin extra x86info_1.14-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDCFVyJ2Vo11xhU60RAstmAKDwAn34N2MbsMI+rtqt7XfHFi9fEQCfTJCJ PZ8ONBS02cowZUxW/oOoI3o= =PIzW -END PGP SIGNATURE- Accepted: x86info_1.14-2.diff.gz to pool/main/x/x86info/x86info_1.14-2.diff.gz x86info_1.14-2.dsc to pool/main/x/x86info/x86info_1.14-2.dsc x86info_1.14-2_i386.deb to pool/main/x/x86info/x86info_1.14-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted vde 1.5.9-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 16 Aug 2005 17:42:39 +0200 Source: vde Binary: vde Architecture: source i386 Version: 1.5.9-1 Distribution: unstable Urgency: low Maintainer: Piotr Roszatycki [EMAIL PROTECTED] Changed-By: Piotr Roszatycki [EMAIL PROTECTED] Description: vde- virtual distributed ethernet Closes: 321999 Changes: vde (1.5.9-1) unstable; urgency=low . * Initial release. Closes: #321999. Files: 63132f186da1411404b6275e4240bd97 574 net optional vde_1.5.9-1.dsc 13337f2317a51a8c441503a0b0c908ac 437770 net optional vde_1.5.9.orig.tar.gz 47c62f9fb93a96a3cfb18b58334a0c01 5627 net optional vde_1.5.9-1.diff.gz a72679ee35d646ab3e610829e32f5905 60554 net optional vde_1.5.9-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDAg7ohMHHe8CxClsRAp3bAKDs4gbDFXTuQw+TLBCb29sbZ5J2NQCeKqMz TkCSjEQKravgtNlH/Ry/r0M= =Oeen -END PGP SIGNATURE- Accepted: vde_1.5.9-1.diff.gz to pool/main/v/vde/vde_1.5.9-1.diff.gz vde_1.5.9-1.dsc to pool/main/v/vde/vde_1.5.9-1.dsc vde_1.5.9-1_i386.deb to pool/main/v/vde/vde_1.5.9-1_i386.deb vde_1.5.9.orig.tar.gz to pool/main/v/vde/vde_1.5.9.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted wmacpi 2.1-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 21 Aug 2005 11:42:59 +0200 Source: wmacpi Binary: wmacpi Architecture: source i386 Version: 2.1-2 Distribution: unstable Urgency: low Maintainer: Sebastian Henschel [EMAIL PROTECTED] Changed-By: Sebastian Henschel [EMAIL PROTECTED] Description: wmacpi - An ACPI battery monitor for WindowMaker Closes: 320613 323456 Changes: wmacpi (2.1-2) unstable; urgency=low . * debian/watch: - Updated to reflect (not-so-)new download location. * debian/control: - Added amd64 to Architecture, closes: #323456. - Bumped Standards-Version to 3.6.2.0. * debian/menu: - Capitalised title to Wmacpi, closes: #320613. Files: a1d1d65d3b442f5c91f99ac0951b92a1 603 x11 extra wmacpi_2.1-2.dsc 06c21f8eee05d8e46a9336c7b5d8dd19 4020 x11 extra wmacpi_2.1-2.diff.gz cf2a774e5aa73dbcfa5273be235045b6 27416 x11 extra wmacpi_2.1-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDCFXNreHfL3pi+bQRApaYAKCQkOCFvnr/6Z0f8whL0IQFw4YhgACfUyfP X0CSBF4ES4xbM8/AvqGx3uc= =J6HS -END PGP SIGNATURE- Accepted: wmacpi_2.1-2.diff.gz to pool/main/w/wmacpi/wmacpi_2.1-2.diff.gz wmacpi_2.1-2.dsc to pool/main/w/wmacpi/wmacpi_2.1-2.dsc wmacpi_2.1-2_i386.deb to pool/main/w/wmacpi/wmacpi_2.1-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted liblocale-po-perl 0.14-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 16 Aug 2005 19:10:03 +0100 Source: liblocale-po-perl Binary: liblocale-po-perl Architecture: source all Version: 0.14-1 Distribution: unstable Urgency: low Maintainer: Alastair McKinstry [EMAIL PROTECTED] Changed-By: Alastair McKinstry [EMAIL PROTECTED] Description: liblocale-po-perl - Locale::PO perl module Changes: liblocale-po-perl (0.14-1) unstable; urgency=low . * Initial release * Reference /usr/share/common-licenses/Artistic in debian/copyright Files: 2d592aab636bc00c3b7dd8e3c7d22ff2 636 interpreters optional liblocale-po-perl_0.14-1.dsc 4c52ba120da8828969a0c5fbd2792b6b 24320 interpreters optional liblocale-po-perl_0.14.orig.tar.gz e5c743018b9b797ee277e0c4c950bdb2 946 interpreters optional liblocale-po-perl_0.14-1.diff.gz f15153edb7931978a7aa9dc1d6abb31c 9348 interpreters optional liblocale-po-perl_0.14-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDBJ1gQTK/kCo4XFcRArAhAJ9Ix+blncthava89VzBzaoBcJejrACfYCbA 7bSx9FEs01jJYqivE9lNHJY= =nWgd -END PGP SIGNATURE- Accepted: liblocale-po-perl_0.14-1.diff.gz to pool/main/libl/liblocale-po-perl/liblocale-po-perl_0.14-1.diff.gz liblocale-po-perl_0.14-1.dsc to pool/main/libl/liblocale-po-perl/liblocale-po-perl_0.14-1.dsc liblocale-po-perl_0.14-1_all.deb to pool/main/libl/liblocale-po-perl/liblocale-po-perl_0.14-1_all.deb liblocale-po-perl_0.14.orig.tar.gz to pool/main/libl/liblocale-po-perl/liblocale-po-perl_0.14.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted icc-profiles 1.0.1-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 6 Aug 2005 00:06:31 -0600 Source: icc-profiles Binary: icc-profiles Architecture: source all Version: 1.0.1-1 Distribution: unstable Urgency: low Maintainer: Oleksandr Moskalenko [EMAIL PROTECTED] Changed-By: Oleksandr Moskalenko [EMAIL PROTECTED] Description: icc-profiles - a collection of ICC color profiles Closes: 323537 Changes: icc-profiles (1.0.1-1) unstable; urgency=low . * Sponsored by Ross Burton [EMAIL PROTECTED] * First upload into Debian (Closes: #323537). * Added a sRGB profile. * debian/copyright: Added sRGB profile license. Files: 84d124dc83d50a560f43ad27a1c4004d 590 non-free/graphics optional icc-profiles_1.0.1-1.dsc 9f010b4bb8d1a7999d8ef903c6d9c798 5193710 non-free/graphics optional icc-profiles_1.0.1.orig.tar.gz 21d933019a78b58f5a123bfdccfd4060 3911 non-free/graphics optional icc-profiles_1.0.1-1.diff.gz 6fdea43e217c37ce427199a9413e325f 5185064 non-free/graphics optional icc-profiles_1.0.1-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFDBEwPLQnkR9C0M98RAuyQAJsHwuC3EtJQpeF800iqtzJjynyTygCcD3Sn mzFUEts3web+r9AOoxjSkWs= =ltNR -END PGP SIGNATURE- Accepted: icc-profiles_1.0.1-1.diff.gz to pool/non-free/i/icc-profiles/icc-profiles_1.0.1-1.diff.gz icc-profiles_1.0.1-1.dsc to pool/non-free/i/icc-profiles/icc-profiles_1.0.1-1.dsc icc-profiles_1.0.1-1_all.deb to pool/non-free/i/icc-profiles/icc-profiles_1.0.1-1_all.deb icc-profiles_1.0.1.orig.tar.gz to pool/non-free/i/icc-profiles/icc-profiles_1.0.1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jmagick 6.0.4-0-1 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 17 Aug 2005 14:27:52 -0500 Source: jmagick Binary: libjmagick6-jni jmagick6-docs libjmagick6-java Architecture: source all i386 Version: 6.0.4-0-1 Distribution: unstable Urgency: low Maintainer: Adam Heath [EMAIL PROTECTED] Changed-By: Adam Heath [EMAIL PROTECTED] Description: jmagick6-docs - A java interface to ImageMagick - api documentation libjmagick6-java - A java interface to ImageMagick - java classes libjmagick6-jni - A java interface to ImageMagick - native library Changes: jmagick (6.0.4-0-1) unstable; urgency=low . * Initial release. Files: f43ff385c9f466ce947e16a27fea71d6 671 graphics optional jmagick_6.0.4-0-1.dsc 439f7178ee8df95fe48e97c1baf2ed8e 261015 graphics optional jmagick_6.0.4-0.orig.tar.gz 9d53e9a120c5e20a38050af7b1d01b96 4710 graphics optional jmagick_6.0.4-0-1.diff.gz 9de44b4b740350d21602976ba2a0453c 20968 graphics optional libjmagick6-java_6.0.4-0-1_all.deb ba9449c1a7535007744b00122ea4f783 83332 graphics optional jmagick6-docs_6.0.4-0-1_all.deb 7fd8c28895bf0caebf5f0c495b593ef7 26020 graphics optional libjmagick6-jni_6.0.4-0-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDA49liix9wovUpIkRAi3OAKCCZrHrzJE+5lwgTXSJH3QJ+vhF5gCfVjQw 4ilznhv8kjZGfeEc8PfU8m4= =2LTq -END PGP SIGNATURE- Accepted: jmagick6-docs_6.0.4-0-1_all.deb to pool/main/j/jmagick/jmagick6-docs_6.0.4-0-1_all.deb jmagick_6.0.4-0-1.diff.gz to pool/main/j/jmagick/jmagick_6.0.4-0-1.diff.gz jmagick_6.0.4-0-1.dsc to pool/main/j/jmagick/jmagick_6.0.4-0-1.dsc jmagick_6.0.4-0.orig.tar.gz to pool/main/j/jmagick/jmagick_6.0.4-0.orig.tar.gz libjmagick6-java_6.0.4-0-1_all.deb to pool/main/j/jmagick/libjmagick6-java_6.0.4-0-1_all.deb libjmagick6-jni_6.0.4-0-1_i386.deb to pool/main/j/jmagick/libjmagick6-jni_6.0.4-0-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libquicktime 1:0.9.7-0.1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 17 Aug 2005 17:19:43 +0200 Source: libquicktime Binary: libquicktime0 quicktime-x11utils libquicktime-dev quicktime-utils Architecture: source i386 Version: 1:0.9.7-0.1 Distribution: unstable Urgency: low Maintainer: Gerd Knorr [EMAIL PROTECTED] Changed-By: Christian Marillat [EMAIL PROTECTED] Description: libquicktime-dev - Header files for developing applications with quicktime libquicktime0 - A library for reading and writing Quicktime files quicktime-utils - quicktime utilities quicktime-x11utils - quicktime utilities Changes: libquicktime (1:0.9.7-0.1) unstable; urgency=low . * Change the libquicktime1 package name to libquicktime0 du to libray * Soname change libquicktime1 is now libquicktime0. * Add libxv-dev in Build-Depends. Files: d173e6a9bb2c17d0b3f14d4a4aaaeecd 828 devel optional libquicktime_0.9.7-0.1.dsc e5c977567df59c876c50ac191bb1caf6 765719 devel optional libquicktime_0.9.7.orig.tar.gz 0da043c7f919441eab779116b3b5ecf6 8738 devel optional libquicktime_0.9.7-0.1.diff.gz 4a59fecf7e41907a403c10e246561f59 408326 libs optional libquicktime0_0.9.7-0.1_i386.deb b8e19f0b12b5534183f1835b43c94401 24842 libdevel optional libquicktime-dev_0.9.7-0.1_i386.deb ced8c36d69d9a7001d20da8ed16c3727 13910 utils extra quicktime-utils_0.9.7-0.1_i386.deb 9ce50fcffa108e143fc27471117dae76 29312 utils extra quicktime-x11utils_0.9.7-0.1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDA1pyB9xWPR9BuQcRAtOkAJ9gP7eaMvevkyfUkjq7eMHQq8AqrgCghvtG jyEel4GYA+ScOgoK7tcOrbc= =G6tv -END PGP SIGNATURE- Accepted: libquicktime-dev_0.9.7-0.1_i386.deb to pool/main/libq/libquicktime/libquicktime-dev_0.9.7-0.1_i386.deb libquicktime0_0.9.7-0.1_i386.deb to pool/main/libq/libquicktime/libquicktime0_0.9.7-0.1_i386.deb libquicktime_0.9.7-0.1.diff.gz to pool/main/libq/libquicktime/libquicktime_0.9.7-0.1.diff.gz libquicktime_0.9.7-0.1.dsc to pool/main/libq/libquicktime/libquicktime_0.9.7-0.1.dsc quicktime-utils_0.9.7-0.1_i386.deb to pool/main/libq/libquicktime/quicktime-utils_0.9.7-0.1_i386.deb quicktime-x11utils_0.9.7-0.1_i386.deb to pool/main/libq/libquicktime/quicktime-x11utils_0.9.7-0.1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted openafs-doc 1.3.87-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 16 Aug 2005 18:01:08 -0700 Source: openafs-doc Binary: openafs-doc Architecture: source all Version: 1.3.87-1 Distribution: unstable Urgency: low Maintainer: Russ Allbery [EMAIL PROTECTED] Changed-By: Russ Allbery [EMAIL PROTECTED] Description: openafs-doc - The AFS distributed filesystem- documentation Closes: 107930 160842 Changes: openafs-doc (1.3.87-1) unstable; urgency=low . * Initial release. (Closes: #107930) - Includes a CellAlias example. (Closes: #160842) Files: 1774696f4986fdd1c7862387f74fbf64 874 doc optional openafs-doc_1.3.87-1.dsc f9ccbeb2ae8423bfa2a3b8d2f33d519a 2994538 doc optional openafs-doc_1.3.87.orig.tar.gz 3a3dfa9f426aa332b502b0907d9320da 6950 doc optional openafs-doc_1.3.87-1.diff.gz 90a0183834ec6d926a7ce102cf484d33 2907826 doc optional openafs-doc_1.3.87-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iQEVAwUBQwNmX7f2jhx5fmQdAQKdxAf/XzNhmocuCovp632fX/KZhEUDSgjgkfN5 09tZZekai5pY2bEsPkgeZcXLFOkIgOd/8RTVbfcwMpprhIWduf+QBAUPFTi6QKcV mM+1n0EK8C9kuRAohZRloY0M4n14/yeTREU+RFloqZNdMS2cnUDgTEes0UpFkEmU Q63Vx7wpRJaLpSMUzyS9OgpjHuOqqi83u+3qgM3MJEHkh47V6IfTekJvXCWzqCcI 864mWRTYw5X3bQTbw5Xoad3HEU+YHbJZd5HoeHx1zHrBlljsajau0otD9LX8mL/K sy/uYmf5sg61283maGMG3rnCM/Ja3ngWnz7xiMqMg86MgZuNy9IeDg== =jS3c -END PGP SIGNATURE- Accepted: openafs-doc_1.3.87-1.diff.gz to pool/main/o/openafs-doc/openafs-doc_1.3.87-1.diff.gz openafs-doc_1.3.87-1.dsc to pool/main/o/openafs-doc/openafs-doc_1.3.87-1.dsc openafs-doc_1.3.87-1_all.deb to pool/main/o/openafs-doc/openafs-doc_1.3.87-1_all.deb openafs-doc_1.3.87.orig.tar.gz to pool/main/o/openafs-doc/openafs-doc_1.3.87.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gsetroot 1.0-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 5 Jul 2005 21:55:03 -0500 Source: gsetroot Binary: gsetroot Architecture: source i386 Version: 1.0-1 Distribution: unstable Urgency: low Maintainer: William Vera [EMAIL PROTECTED] Changed-By: William Vera [EMAIL PROTECTED] Description: gsetroot - a C/Gtk-based front-end for Esetroot Closes: 311953 Changes: gsetroot (1.0-1) unstable; urgency=low . * Initial release (Closes: #311953). Files: 488541d6f83d4751d92854e270cdf332 601 utils extra gsetroot_1.0-1.dsc 8abbb5cf0cae3128059d6a1151d29604 372516 utils extra gsetroot_1.0.orig.tar.gz 3f28233e6044a03ef6d6c45033fe7a95 2052 utils extra gsetroot_1.0-1.diff.gz 0777e44ec4e8ca73de70a0d71e760d8c 9620 utils extra gsetroot_1.0-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDAumJgY5NIXPNpFURAmLoAKCGpFxoj6CE+IYkWViTATNLpa30JgCgzMen sZJQ6egc6bNrHT+DTQAJBwk= =BOcz -END PGP SIGNATURE- Accepted: gsetroot_1.0-1.diff.gz to pool/main/g/gsetroot/gsetroot_1.0-1.diff.gz gsetroot_1.0-1.dsc to pool/main/g/gsetroot/gsetroot_1.0-1.dsc gsetroot_1.0-1_i386.deb to pool/main/g/gsetroot/gsetroot_1.0-1_i386.deb gsetroot_1.0.orig.tar.gz to pool/main/g/gsetroot/gsetroot_1.0.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted digikamimageplugins 0.7.4-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 21 Aug 2005 11:10:50 +0100 Source: digikamimageplugins Binary: digikamimageplugins Architecture: source i386 Version: 0.7.4-1 Distribution: unstable Urgency: low Maintainer: Achim Bohnet [EMAIL PROTECTED] Changed-By: Mark Purcell [EMAIL PROTECTED] Description: digikamimageplugins - digikam image editor plugins Changes: digikamimageplugins (0.7.4-1) unstable; urgency=low . [ Achim Bohnet ] * new upstream release: Upstream split code and docs into two tarballs. Handbooks and their translations are now in it's own digikamimageplugins-doc package. * long description: added the 10 new imageplugins * fix broken build-dep: use kdelibs epoche * license/copyright review . [ Mark Purcell ] * C++ transition package * Update Build-Depends: kdelibs4-dev (= 4:3.4.2-1), libdigikam (= 0.7.4-0), libkexif1-dev (= 0.2.1-5), libkipi0-dev (= 0.1.1-3) * Build-Depends: digikam (= 0.7.4) Files: c3b182cef2bbe961eb5f898236a05154 858 graphics optional digikamimageplugins_0.7.4-1.dsc 554ea403824c582844844eaba914d203 3198934 graphics optional digikamimageplugins_0.7.4.orig.tar.gz 57fef62168df019e858f5b48a77f2d8b 11624 graphics optional digikamimageplugins_0.7.4-1.diff.gz 2876bcb000c5f45b567eee3722304442 2794144 graphics optional digikamimageplugins_0.7.4-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDCFvxoCzanz0IthIRAjzhAJ40OeUOBiSvANbshC9wH/+y1oxykQCfZai5 R07W2Ow5or7wGJNHYVzDGYs= =6p1f -END PGP SIGNATURE- Accepted: digikamimageplugins_0.7.4-1.diff.gz to pool/main/d/digikamimageplugins/digikamimageplugins_0.7.4-1.diff.gz digikamimageplugins_0.7.4-1.dsc to pool/main/d/digikamimageplugins/digikamimageplugins_0.7.4-1.dsc digikamimageplugins_0.7.4-1_i386.deb to pool/main/d/digikamimageplugins/digikamimageplugins_0.7.4-1_i386.deb digikamimageplugins_0.7.4.orig.tar.gz to pool/main/d/digikamimageplugins/digikamimageplugins_0.7.4.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mozilla-firefox-webdeveloper 0.9.3-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 17 Aug 2005 15:05:53 -0400 Source: mozilla-firefox-webdeveloper Binary: mozilla-firefox-webdeveloper Architecture: source all Version: 0.9.3-2 Distribution: unstable Urgency: low Maintainer: Michael Spang [EMAIL PROTECTED] Changed-By: Michael Spang [EMAIL PROTECTED] Description: mozilla-firefox-webdeveloper - web developer extension for the Firefox web browser Closes: 323148 Changes: mozilla-firefox-webdeveloper (0.9.3-2) unstable; urgency=low . * Initial release (Closes: #323148) * Fixed cruft in copyright Files: 11d44827a2f5fe15d927626384e25dd0 654 devel optional mozilla-firefox-webdeveloper_0.9.3-2.dsc 8e0de7f802f3e610191239154819531e 1934 devel optional mozilla-firefox-webdeveloper_0.9.3-2.diff.gz e483d2a13a454b45f7e8d5a103a1c8b5 114952 devel optional mozilla-firefox-webdeveloper_0.9.3.orig.tar.gz 725efc11ffb945496f402b029a405980 109566 devel optional mozilla-firefox-webdeveloper_0.9.3-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDA4+wQbn06FtxPfARAv8sAKDWAXXvKGj2+VYDMSD3OvotvZRhcQCeKsP+ MyxHx98kARKchJ4+/29mdGE= =XQZM -END PGP SIGNATURE- Accepted: mozilla-firefox-webdeveloper_0.9.3-2.diff.gz to pool/main/m/mozilla-firefox-webdeveloper/mozilla-firefox-webdeveloper_0.9.3-2.diff.gz mozilla-firefox-webdeveloper_0.9.3-2.dsc to pool/main/m/mozilla-firefox-webdeveloper/mozilla-firefox-webdeveloper_0.9.3-2.dsc mozilla-firefox-webdeveloper_0.9.3-2_all.deb to pool/main/m/mozilla-firefox-webdeveloper/mozilla-firefox-webdeveloper_0.9.3-2_all.deb mozilla-firefox-webdeveloper_0.9.3.orig.tar.gz to pool/main/m/mozilla-firefox-webdeveloper/mozilla-firefox-webdeveloper_0.9.3.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted emacs-color-themes 6.5.4-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 4 Jul 2005 10:11:23 +0700 Source: emacs-color-themes Binary: emacs-color-themes Architecture: source all Version: 6.5.4-1 Distribution: unstable Urgency: low Maintainer: Basil Shubin [EMAIL PROTECTED] Changed-By: Basil Shubin [EMAIL PROTECTED] Description: emacs-color-themes - Color themes for Emacs Closes: 316814 Changes: emacs-color-themes (6.5.4-1) unstable; urgency=low . * Initial Release (Closes: #316814). Files: 4840b637bd54ee336e5e2d0801476395 608 editors optional emacs-color-themes_6.5.4-1.dsc 898e4b434eb958d156652aa35fdecf7b 109591 editors optional emacs-color-themes_6.5.4.orig.tar.gz 825734010a9b40497c8185672c838ae9 2535 editors optional emacs-color-themes_6.5.4-1.diff.gz 7a01880af1d13131c876ea349bd1d04a 112820 editors optional emacs-color-themes_6.5.4-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDBK8lLqiZQEml+FURAjS9AKCxWJOTmTiFk10qiC+63lioyqvFbQCdF7yK FebIijgG8DLaMPLzOpEFbKo= =SN+O -END PGP SIGNATURE- Accepted: emacs-color-themes_6.5.4-1.diff.gz to pool/main/e/emacs-color-themes/emacs-color-themes_6.5.4-1.diff.gz emacs-color-themes_6.5.4-1.dsc to pool/main/e/emacs-color-themes/emacs-color-themes_6.5.4-1.dsc emacs-color-themes_6.5.4-1_all.deb to pool/main/e/emacs-color-themes/emacs-color-themes_6.5.4-1_all.deb emacs-color-themes_6.5.4.orig.tar.gz to pool/main/e/emacs-color-themes/emacs-color-themes_6.5.4.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted sensors-applet 1.4a-3 (source powerpc)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 11 Aug 2005 13:16:47 +0100
Source: sensors-applet
Binary: sensors-applet
Architecture: source powerpc
Version: 1.4a-3
Distribution: unstable
Urgency: low
Maintainer: Sam Morris [EMAIL PROTECTED]
Changed-By: Sam Morris [EMAIL PROTECTED]
Description:
sensors-applet - Display readings from hardware sensors in your Gnome panel
Closes: 308437
Changes:
sensors-applet (1.4a-3) unstable; urgency=low
.
* Add Filippo Giunchedi (package sponsor) to Uploaders
* debian/rules: on clean, warn if debian/control is out of date
.
sensors-applet (1.4a-2) unstable; urgency=low
.
* Disable CDBS debian/control management
* Remove redundant CDBS-generated entries from build-depends
.
sensors-applet (1.4a-1) unstable; urgency=low
.
* New upstream release. Upstream didn't change the version number, so this
is version 1.4a.
.
sensors-applet (1.4-2) unstable; urgency=low
.
* Remove config.{guess,sub}.cdbs-orig cruft in clean
* correct_icon_path.diff: make the panel applet use the correct icon path
* offset_finegrain.diff: make multiplier value adjustments more granular
* First upload to unstable (closes: #308437)
.
sensors-applet (1.4-1) unstable; urgency=low
.
* New upstream release
.
sensors-applet (1.2-1) unstable; urgency=low
.
* New upstream release
.
sensors-applet (1.0-1) unstable; urgency=low
.
* New upstream release
* debian/control: use CDBS auto management
.
sensors-applet (0.7.3-1) unstable; urgency=low
.
* Initial Release.
Files:
f9fe0cdefefb67e734c4c124cc98cc5f 736 gnome optional sensors-applet_1.4a-3.dsc
e71ea9fe79cbc281293fa90857a92b04 154938 gnome optional
sensors-applet_1.4a.orig.tar.gz
4676eb56035db4839ed430a398895947 2614 gnome optional
sensors-applet_1.4a-3.diff.gz
fd57a30393769e4f35351e423fd61a60 40178 gnome optional
sensors-applet_1.4a-3_powerpc.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFDAe9jABzeamt51AERAmm7AKDSZWA+eCidsjiw2iHUSq+/TKAYtQCfRaE2
Mdos/gy1vUHgKj1fALNLhl0=
=u0BQ
-END PGP SIGNATURE-
Accepted:
sensors-applet_1.4a-3.diff.gz
to pool/main/s/sensors-applet/sensors-applet_1.4a-3.diff.gz
sensors-applet_1.4a-3.dsc
to pool/main/s/sensors-applet/sensors-applet_1.4a-3.dsc
sensors-applet_1.4a-3_powerpc.deb
to pool/main/s/sensors-applet/sensors-applet_1.4a-3_powerpc.deb
sensors-applet_1.4a.orig.tar.gz
to pool/main/s/sensors-applet/sensors-applet_1.4a.orig.tar.gz
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted workman 1.3.4-20 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 21 Aug 2005 12:30:00 +0200 Source: workman Binary: workman Architecture: source i386 Version: 1.3.4-20 Distribution: unstable Urgency: low Maintainer: Volker Ossenkopf [EMAIL PROTECTED] Changed-By: Volker Ossenkopf [EMAIL PROTECTED] Description: workman- Graphical tool for playing audio CDs on a CD-ROM drive Closes: 324136 Changes: workman (1.3.4-20) unstable; urgency=low . * added Vietnamese translation from Clytie Siddall. Closes: #324136 Files: 66a0eac3dc3510a5e781816cbcc9272f 591 sound optional workman_1.3.4-20.dsc 5326212b9bd9695532c1ec4887ffd93a 30227 sound optional workman_1.3.4-20.diff.gz 256595866553c7ca04ab75d6b438c76e 128272 sound optional workman_1.3.4-20_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDCFhSilantJo6v0gRAhAHAJ98azf5g27PwMpHoXQsXcSj0WK1jQCfW3Xl x2TlgkcgxnaDe9LD6V0hXzc= =Q+AP -END PGP SIGNATURE- Accepted: workman_1.3.4-20.diff.gz to pool/main/w/workman/workman_1.3.4-20.diff.gz workman_1.3.4-20.dsc to pool/main/w/workman/workman_1.3.4-20.dsc workman_1.3.4-20_i386.deb to pool/main/w/workman/workman_1.3.4-20_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted smarty-gettext 1.0b1-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 17 Aug 2005 19:50:43 +0300 Source: smarty-gettext Binary: smarty-gettext Architecture: source all Version: 1.0b1-1 Distribution: unstable Urgency: low Maintainer: Cyril Bouthors [EMAIL PROTECTED] Changed-By: Cyril Bouthors [EMAIL PROTECTED] Description: smarty-gettext - provides gettext support for smarty Closes: 323629 Changes: smarty-gettext (1.0b1-1) unstable; urgency=low . * Initial release Closes: #323629. Files: 50f6732a482e45f36eb3e1325813be6e 590 web optional smarty-gettext_1.0b1-1.dsc 4d5122e9ec7da7f1dc5ef283fb259dd4 13507 web optional smarty-gettext_1.0b1.orig.tar.gz 4f359e6b033789527b30c21d22b1efd3 1472 web optional smarty-gettext_1.0b1-1.diff.gz eaab35bd274bde5ea61cc78d982d3413 7660 web optional smarty-gettext_1.0b1-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDBCUeZ1SJHeqsYt8RAtJEAKCSDnhXQew+TdYRPDo4gwLf1pTlxQCfVFtW rw3iZx6j1vTqkLduN8jnDfI= =xg0B -END PGP SIGNATURE- Accepted: smarty-gettext_1.0b1-1.diff.gz to pool/main/s/smarty-gettext/smarty-gettext_1.0b1-1.diff.gz smarty-gettext_1.0b1-1.dsc to pool/main/s/smarty-gettext/smarty-gettext_1.0b1-1.dsc smarty-gettext_1.0b1-1_all.deb to pool/main/s/smarty-gettext/smarty-gettext_1.0b1-1_all.deb smarty-gettext_1.0b1.orig.tar.gz to pool/main/s/smarty-gettext/smarty-gettext_1.0b1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted haskell-hsql 1.6-1 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 17 Aug 2005 05:23:19 -0500 Source: haskell-hsql Binary: libghc6-hsql-mysql-dev libghc6-hsql-odbc-dev libghc6-hsql-sqlite3-dev libghc6-hsql-postgresql-dev libghc6-hsql-sqlite-dev haskell-hsql-doc libghc6-hsql-dev Architecture: source all i386 Version: 1.6-1 Distribution: unstable Urgency: low Maintainer: John Goerzen [EMAIL PROTECTED] Changed-By: John Goerzen [EMAIL PROTECTED] Description: haskell-hsql-doc - Multi-Database Interface System for Haskell libghc6-hsql-dev - Multi-Database Interface System for Haskell libghc6-hsql-mysql-dev - Multi-Database Interface System for Haskell libghc6-hsql-odbc-dev - Multi-Database Interface System for Haskell libghc6-hsql-postgresql-dev - Multi-Database Interface System for Haskell libghc6-hsql-sqlite-dev - Multi-Database Interface System for Haskell libghc6-hsql-sqlite3-dev - Multi-Database Interface System for Haskell Closes: 288234 Changes: haskell-hsql (1.6-1) unstable; urgency=low . * New upstream release. * Upstream now uses Cabal and splits modules into individual per-DB modules. Now do that here as well. Closes: #288234. Files: 9de8cc0be580270d92cab1d549380df9 1070 - optional haskell-hsql_1.6-1.dsc 1acb25d6b237ba2d9a9b360190073652 27954 - optional haskell-hsql_1.6.orig.tar.gz 0a27a53037ea6942099a99b56adbd9bd 4500 - optional haskell-hsql_1.6-1.diff.gz 0ece667381d984140388990db4e7e088 15010 devel optional haskell-hsql-doc_1.6-1_all.deb ae225af901d29d6b998aa3976c0dd2a2 70054 devel optional libghc6-hsql-dev_1.6-1_i386.deb 82696b41417802b9d3f30dd53110c59d 17920 devel optional libghc6-hsql-sqlite3-dev_1.6-1_i386.deb b0c57b16e3ad1131f9a4ade919ec6cb6 17852 devel optional libghc6-hsql-sqlite-dev_1.6-1_i386.deb 782575a4005408fbce9a3cc38043140f 36846 devel optional libghc6-hsql-odbc-dev_1.6-1_i386.deb d5246fe53dac4ea45a9679a9b1ff66f8 20672 devel optional libghc6-hsql-mysql-dev_1.6-1_i386.deb e5a79dc7c7d8868ada567f4ba4b62f51 28592 devel optional libghc6-hsql-postgresql-dev_1.6-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDA7Jr7B2mSKdID5ERAst4AJ9gN3k022bAujv5E02mT984e/oRtACeJMUD VCg5+TWwYG+Urpsh3t9lDCk= =Re/g -END PGP SIGNATURE- Accepted: haskell-hsql-doc_1.6-1_all.deb to pool/main/h/haskell-hsql/haskell-hsql-doc_1.6-1_all.deb haskell-hsql_1.6-1.diff.gz to pool/main/h/haskell-hsql/haskell-hsql_1.6-1.diff.gz haskell-hsql_1.6-1.dsc to pool/main/h/haskell-hsql/haskell-hsql_1.6-1.dsc haskell-hsql_1.6.orig.tar.gz to pool/main/h/haskell-hsql/haskell-hsql_1.6.orig.tar.gz libghc6-hsql-dev_1.6-1_i386.deb to pool/main/h/haskell-hsql/libghc6-hsql-dev_1.6-1_i386.deb libghc6-hsql-mysql-dev_1.6-1_i386.deb to pool/main/h/haskell-hsql/libghc6-hsql-mysql-dev_1.6-1_i386.deb libghc6-hsql-odbc-dev_1.6-1_i386.deb to pool/main/h/haskell-hsql/libghc6-hsql-odbc-dev_1.6-1_i386.deb libghc6-hsql-postgresql-dev_1.6-1_i386.deb to pool/main/h/haskell-hsql/libghc6-hsql-postgresql-dev_1.6-1_i386.deb libghc6-hsql-sqlite-dev_1.6-1_i386.deb to pool/main/h/haskell-hsql/libghc6-hsql-sqlite-dev_1.6-1_i386.deb libghc6-hsql-sqlite3-dev_1.6-1_i386.deb to pool/main/h/haskell-hsql/libghc6-hsql-sqlite3-dev_1.6-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted haskell-hsql 1.6-2 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 17 Aug 2005 21:53:02 -0500 Source: haskell-hsql Binary: libghc6-hsql-mysql-dev libghc6-hsql-odbc-dev libghc6-hsql-sqlite3-dev libghc6-hsql-postgresql-dev libghc6-hsql-sqlite-dev haskell-hsql-doc libghc6-hsql-dev Architecture: source all i386 Version: 1.6-2 Distribution: unstable Urgency: low Maintainer: John Goerzen [EMAIL PROTECTED] Changed-By: John Goerzen [EMAIL PROTECTED] Description: haskell-hsql-doc - Multi-Database Interface System for Haskell libghc6-hsql-dev - Multi-Database Interface System for Haskell libghc6-hsql-mysql-dev - Multi-Database Interface System for Haskell libghc6-hsql-odbc-dev - Multi-Database Interface System for Haskell libghc6-hsql-postgresql-dev - Multi-Database Interface System for Haskell libghc6-hsql-sqlite-dev - Multi-Database Interface System for Haskell libghc6-hsql-sqlite3-dev - Multi-Database Interface System for Haskell Changes: haskell-hsql (1.6-2) unstable; urgency=low . * Fixed failure to generate postinst/prerm scripts. * Fixed Postgres deps. Files: 12f5fe579799bc4dc5953e7228ddd7bd 1142 - optional haskell-hsql_1.6-2.dsc 30b258282c8afa26d441d74d54f3f2fe 4579 - optional haskell-hsql_1.6-2.diff.gz 39eb804555e1831839f6f6b8e68b5680 15066 devel optional haskell-hsql-doc_1.6-2_all.deb 3cb2b03bcf06305e10e17541eee1fa57 70514 devel optional libghc6-hsql-dev_1.6-2_i386.deb a7e29e1873263f536bbb0a55b1412538 18374 devel optional libghc6-hsql-sqlite3-dev_1.6-2_i386.deb 77d1e9b1b2887eca7b1571a7b1ef6042 18308 devel optional libghc6-hsql-sqlite-dev_1.6-2_i386.deb 17e4728476a51e334e0134f11811ce14 37308 devel optional libghc6-hsql-odbc-dev_1.6-2_i386.deb 20b7ca1e6aeb157a56e6eeada661df26 21124 devel optional libghc6-hsql-mysql-dev_1.6-2_i386.deb 0cc41017bd64fad00d10b352ee02efe0 29060 devel optional libghc6-hsql-postgresql-dev_1.6-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDA+6C7B2mSKdID5ERAoY6AJ43TtY9DaONJrvds6L7y4DRf0SfIQCfXx9+ tCSyl2LfasdhuET6UZA1p3I= =4Vfw -END PGP SIGNATURE- Accepted: haskell-hsql-doc_1.6-2_all.deb to pool/main/h/haskell-hsql/haskell-hsql-doc_1.6-2_all.deb haskell-hsql_1.6-2.diff.gz to pool/main/h/haskell-hsql/haskell-hsql_1.6-2.diff.gz haskell-hsql_1.6-2.dsc to pool/main/h/haskell-hsql/haskell-hsql_1.6-2.dsc libghc6-hsql-dev_1.6-2_i386.deb to pool/main/h/haskell-hsql/libghc6-hsql-dev_1.6-2_i386.deb libghc6-hsql-mysql-dev_1.6-2_i386.deb to pool/main/h/haskell-hsql/libghc6-hsql-mysql-dev_1.6-2_i386.deb libghc6-hsql-odbc-dev_1.6-2_i386.deb to pool/main/h/haskell-hsql/libghc6-hsql-odbc-dev_1.6-2_i386.deb libghc6-hsql-postgresql-dev_1.6-2_i386.deb to pool/main/h/haskell-hsql/libghc6-hsql-postgresql-dev_1.6-2_i386.deb libghc6-hsql-sqlite-dev_1.6-2_i386.deb to pool/main/h/haskell-hsql/libghc6-hsql-sqlite-dev_1.6-2_i386.deb libghc6-hsql-sqlite3-dev_1.6-2_i386.deb to pool/main/h/haskell-hsql/libghc6-hsql-sqlite3-dev_1.6-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted xvmount 3.7-8 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 21 Aug 2005 12:40:00 +0200 Source: xvmount Binary: xvmount Architecture: source i386 Version: 3.7-8 Distribution: unstable Urgency: low Maintainer: Volker Ossenkopf [EMAIL PROTECTED] Changed-By: Volker Ossenkopf [EMAIL PROTECTED] Description: xvmount- Small graphical utility for mounting devices by users Closes: 321483 Changes: xvmount (3.7-8) unstable; urgency=low . * Added Czech translation from Jakub Kasparec. Closes: #321483 Files: 212a04661f91a39c37b569b44e4f44b4 574 utils optional xvmount_3.7-8.dsc a98bdf08b00b8c28276491b740fe7d29 14441 utils optional xvmount_3.7-8.diff.gz 508474b510a3d1e7da7d73187fdf3c96 23078 utils optional xvmount_3.7-8_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDCFpJilantJo6v0gRAi7/AJ46avQzW9IgliEWPh47w48WqSup2wCgz8wY x5pFGuU67OAkVIVz2wRoIXM= =4qVY -END PGP SIGNATURE- Accepted: xvmount_3.7-8.diff.gz to pool/main/x/xvmount/xvmount_3.7-8.diff.gz xvmount_3.7-8.dsc to pool/main/x/xvmount/xvmount_3.7-8.dsc xvmount_3.7-8_i386.deb to pool/main/x/xvmount/xvmount_3.7-8_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted input-utils 0.0.20050727-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 28 Jul 2005 13:52:46 +0200 Source: input-utils Binary: input-utils Architecture: source i386 Version: 0.0.20050727-1 Distribution: unstable Urgency: low Maintainer: Marcus Better [EMAIL PROTECTED] Changed-By: Marcus Better [EMAIL PROTECTED] Description: input-utils - utilities for the input layer of the Linux kernel Closes: 321966 Changes: input-utils (0.0.20050727-1) unstable; urgency=low . * New upstream release. * Initial upload to Debian. Closes: #321966. Files: f03e9f7ff78f11132aefed7f9b7d5412 598 utils optional input-utils_0.0.20050727-1.dsc 386b0078e4133cdffcacc0dfd21e1784 27926 utils optional input-utils_0.0.20050727.orig.tar.gz fccad8ffa854bdad07f6515a241db761 2286 utils optional input-utils_0.0.20050727-1.diff.gz 592681150532dc8e00ad6482aa5ac749 15344 utils optional input-utils_0.0.20050727-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDBfv3d6lUs+JfIQIRAs/ZAJ9koFEqaflGHprBuNMzd/4nx/tGSwCgg2rD xp3QFmBszha7gS3vv7dWv/w= =JJxO -END PGP SIGNATURE- Accepted: input-utils_0.0.20050727-1.diff.gz to pool/main/i/input-utils/input-utils_0.0.20050727-1.diff.gz input-utils_0.0.20050727-1.dsc to pool/main/i/input-utils/input-utils_0.0.20050727-1.dsc input-utils_0.0.20050727-1_i386.deb to pool/main/i/input-utils/input-utils_0.0.20050727-1_i386.deb input-utils_0.0.20050727.orig.tar.gz to pool/main/i/input-utils/input-utils_0.0.20050727.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
